Spindle issue after using a gcode program

[TechyMind]

There is no need to assign VFDEnable_O to an output.
You would not do so if you choose to use SpinFWD and/or SpinREV instead.

SpindleEnableOut_M is a memory bit (MEM168), which is always in place.

I would open up PLC Detective (Ctrl-E from the CNC12 main screen), scroll down to around line #3745, and watch what is happening when the spindle starts normally, and when the spindle fails to start.

Ok, I found the difference between the starting => the variable ChuckOpenCloseComplete_M is set to 0 after I use a program.
I don't really know why and I'm not even using an ATC spindle

Here are the pictures.

I modified the PLC directly to remove everything blocking from ATC parts. Now it's working perfectly.
I checked in Wizard that I didn't check ATC also. So maybe there is something else that Centroid should check.

Anyway thank you for your help. I didn't know the PLC detective and it's great now because I'm a programer so I can check everything.

Thank you again

[cnckeith]

thanks, we updated related macros and committed to next release which will fix this issue.
no need to change plc to fix this issue.

[FlyingHaggis]

I have the same problem.
All was fine, until an update earlier this year and now, if I abort a program..no more spindle control.

so does 12.5.10 have this fix ?

[FlyingHaggis]

I can answer my own question.

12.5.10 does fix the issue.