CNC12 V5.09 beta REV5 is now available for testing.

[cnckeith]

update. 4-5-24 RC#4 is here. https://centroidcncforum.com/viewtopic.php?f=67&t=9997

CNC12 V5.09 beta REV5 is now available for testing.

Release notes:

cnc12_v5.1_release_notes.pdf

(1.38 MiB) Downloaded 41 times

How to install beta software.

1.) make a back up of your existing cncm or cnct folder.

2.) create a fresh report.zip file with your existing cnc12 installation

3.) if acorn or acornsix open the wizard of your existing cnc12 installation and press <CTRL P> (CTRL key and the P key at the same time) and save as PDF to the desktop.

4.) download beta software, double click on installer .exe and install CNC12 https://centroid-support.filemail.com/d/ffztrdntuusuruy

5.) If Allin1DC, Oak or Hickory Choose a Centroid provided PLC program that matches your system ( If you do have a custom PLC program, install one of the Centroid provided PLC programs and edit it with your customizations) and then update any parameter values if necessary to match new or updated features of the new version of CNC12.

6.) If Acorn or AcornSix, open CNC12 and then the Wizard and hand enter the data from the PDF made in step 3.

7.) copy over any tool libraries, WCS locations, g code files, custom macros.

8.) edit the beta VCP with any custom buttons if you like. don't copy over an old VCP to the beta software, always start with a Centroid provided VCP skin and edit it with your custom changes.

detailed CNC12 install instructions are here.
https://www.centroidcnc.com/centroid_di ... ctions.pdf


Known issues with Rev 5

1.) Run time graphics tool indicator artifacts may appear with rotary jobs, work around is to press "trail on" "trail off" to clear them.

2.) Rotary G code backplot with CSR active does not display properly, work around, don't use CSR with rotary g code backplotting

[cncsnw]

Simplified PLC Diagnostic App: Added Ctrl+alt+r to the simple plc diagnostic App to auto restore any
user inverted/forced buttons back to the initial state when starting the App. Hopefully this will help
users that get themselves mixed up since they forgot to turn an output back to “normal” or forgot to
uninvert an input.

With all due respect, I don't think this is the best solution to the problem.

First, the type of user who will leave an output forced off, then post here "how come my spindle don't work anymore?", is not the type of user who will read about and use Ctrl-Alt-R before closing PLC Diagnostics.

Second, forcing and inversion have very different purposes. There are good reasons to invert inputs, and leave them inverted for long periods or indefinitely. In contrast, I can think of no good reasons to leave an output forced on or off beyond the immediate testing session.

So, to be effective, any solution needs to be proactive: prompt the user upon exit if they left any output forced on or off. But the feature should only apply to, and reset, output forcing. Input inversion should be left in place.

[cnckeith]

ok so, undo just the outputs but not the inputs? ...seems like then the same type of user would be wondering why the outputs now work but the inputs don't.
this is assuming they knew what they were doing with the inputs but not with the outputs.

The pop would have to address both.

Warning: "Output #X is forced off"
"Output #X is forced on"

press 1 to revert Outputs to Normal state
press 2 to revert Inputs to Previous state
press 3 to revert All to Previous state
press 4 to never show this message again.
ESC to cancel closing and return to the PLC Diagnostic App