Centroid Community CNC Support Forum

Sword wrote: ↑Thu Jun 20, 2024 5:41 pm I will often run looping files where at the end of the file I have a M200 message to continue when ready followed by a GOTO 100. If you load one of those files, and graph it, you can't use cycle start to start the job and cycle cancel doesn't get you out of it, but Escape will. If you use RTG and run the same file, CNC12 will lock up tight and you have to end task on it. File for testing attached. This is not the case in the release version.

cncsnw wrote: ↑Mon Jul 01, 2024 1:17 pm Chris is completely correct about that, but...

I understood Scott to be reporting that, when RTG was drawing the preview, he could not interrupt it with ESC or Cycle Cancel.

Even when CNC12 is graphing a job that loops forever, ESC should interrupt it.

Allin1Chris wrote: ↑Mon Jul 01, 2024 9:38 am ;Prevent Graphing or searching from looping the Job
IF ![#4201 || #4202] THEN GOTO 100

Sword wrote: ↑Tue Jul 09, 2024 4:59 pm 5.18 RC1...

The previous MPG issues appear to be resolved.

On the Graphing and RTG loop issues, the following code added to my looping files appears to remedy the looping problems that weren't present without it in previous versions. I wonder if there may be any other trigger that could totally lock up CNC12 in RTG mode like the loop did since it didn't do that previously.

Allin1Chris wrote: ↑Mon Jul 01, 2024 9:38 am ;Prevent Graphing or searching from looping the Job
IF ![#4201 || #4202] THEN GOTO 100

There is what seems to be like a focus issue with graphing. Load a file, graph it, hit cycle start, nothing happens, hit cycle start again, and it starts this time. This also has happened without graphing, just load a file and sometimes it takes two clicks on cycle start to start it.

Cycle start with the ENTER key no longer works when in Graphing or RTG. The option to use the ENTER key is set in the wizard.

The ability to use ENTER as cycle start also doesn't work in some of the Set Part Zeros forms. Instead, it acts like a Tab key press.

ENTER for cycle start doesn't work with probing cycles after the first probe cycle message comes up.

Set Part Zeros - If using LASER, and offsets have been taught or set previously, should there not be a way to apply the saved offsets in this form (like option 1 when using the VCP Laser Set XY button)? Also, while the offsets are grayed, they can be inadvertently edited. I would think that once they have been taught in this form or with the VCP button (option #4), that they can't be edited in this form.

Set Part Zeros/Plate/Z Only - Perhaps some different header text for this one, and bit diameter and flute reminder aren't needed here. This is where the ENTER key tabs around the form (this is common among all similar new set part zero forms).

Warning messages for Probe, TT, and TP only show if you also have protection enabled. In other words, if you don't have protection enabled in the wizard, but you do have Display Warnings enabled, those warnings are not displayed. I sometimes like to trip either of these to see the messages for a quick check.

Set Part Zeros/Manual - Verify Touch Probe is functioning properly message is displayed twice. A double cycle start is needed to proceed.

Set Part Zeros/Graphics - This one is a one shot deal... If one of the new forms are open and has the left side graphic, and you think you want to use a VCP button or accidentally hit one, like GOTO WCS XY0 or PARK ETC., the left side graphic will vanish. Since you can only hit a VCP button once to make this happen, I assume that you shouldn't be able to activate it at all when in the Set Part Zeros forms.

While it's nice to have the three Touch Devices separated out, there might be one scenario that doesn't work as it did previously (actually a couple, but I'm dealing with the others). On a small benchtop router/laser, I have one of those spring loaded buttons that can be used as a movable touch plate would, and also a fixed tool touch off when stowed in a fixed location, where it was able to be connected to one input (as Probe). This would be the same for one of the wireless tool setters. Yes, custom macros would take care of it all, but as it is now with the checks for probe, tt, or tp, you would need another input connected to the same device. Might be looking at it wrong, but it's just the one scenario I came across.

cnckeith wrote: ↑Tue Jul 23, 2024 4:59 pm
Thanks for the feedback. RC2 is now available, please give this one a go!

https://centroid-support.filemail.com/d/iqwptuqnlawkyvf