Spindle CW and Spindle CCW do not call M3, M4, M5 macros

[sailorbob134280]

This is a bit of a continuation of https://www.forum.cncdrive.com/viewtopic.php?f=3&t=108, but given its age and the rather pointed words exchanged towards the end, I thought I'd start fresh with a new thread over it. My objective is the following: check the tool currently in the spindle, determine if it is a non-rotating tool (like a probe or drag engraver) and if it is, throw an error and don't turn on the spindle. I'm sure some of us have seen that NYC CNC video where they rapidly disassembled a Haimer by blitzing it at 5000 RPMs (turns out the spindle button is a little too close to other buttons in PathPilot) and I really don't want to make the same mistake. The way I'm checking for non-rotating tools is by specifying them in the detailed tool table under type. I came up with a little organization scheme where if the type is NR, it shouldn't spin.

Is there a good reason for this? If not, can we get the buttons to call the M3/M4/M5 macros instead of their compiled counterparts? And lastly, does anyone have a good suggestion for how to work around this but still have a safety system? Thanks in advance.

[dezsoe]

I have to agree with you. It was yesterday when I switched from CW to CCW on the screen and the spindle was not happy. The spin up/down delay is skipped when you switch to the other direction. Reading the other thread and your problems too, I think that those buttons should run the macros. And one more thing: the M5 and M9 macros should also run in stop and/or reset state, like the M99998 and M99999 macros do. (Of course, if they contain Code calls, then that should fail, but all other stuff should run.)