CNC12 for Oak/allin1DC/mpu11 V4.18 Release candidate available for testing.

[cnckeith]

CNC12 for Oak/allin1DC/mpu11 V4.18 Release candidate available for testing.

https://fil.email/pWujvioR

Added back the DXF Intercon menu with improved DXF import library
Fixed issue where axis pairing was not available under any conditions.
Fixed issue where laser measurement was not working regardless of license type or trial code.
Fixed issue where the prompt "Press CYCLE START to continue" is not displayed when executing an M0 command if M0 jogging is available. When M0 jogging is enabled, the message "Press CYCLE START to continue (jogging enabled)" is now displayed.
Fixed issue where the 4th axis was being set to 'N' (disabling it) when entering the Motor Parameters menu. It does prompt for changes on exit, so one can discard those changes if they were just going into the menu to look at values. Otherwise, the workaround would be to make sure you set the label again before saving changes.
Re-enabled the setting of P500 = 1 to allow G43.3 and G43.4 to remain active when exiting MDI or running job.
Fixed bug in the VCP where PLC memory wasn't able to be used to set LED state.


if you download and test please only post results and comments about this version here in this thread and not other locations on the forum. thanks!

[cncsnw]

Is it too late to make VCP2 look in some more sensible location than W31 to learn the current feedrate override value?

For example, are there not SV_SKINNING_DATA_n word variables specifically for the purpose of exchanging data between the PLC program and skinning applications?

It is kind of ugly that, in order for a PLC program to work with both VCP1 and VCP2, it needs to reserve two different word variables (W4 and W31), and write the override value into both of them.

If VCP must use a regular word variable instead of an SV_SKINNING_DATA_n variable, then it should read MPU.PLC or MPU.SYM to find out which one to look at. That way, VCP2 could adapt to the PLC program, instead of requiring that all existing PLC programs be modified to adapt to VCP2.

[cnckeith]

we are always up for suggestions for improvement! thats one of the goals of the public beta.

did the rest of the install and testing go well? any problems/bugs to report?