6231
Mach4 General Discussion / Re: Mach4 Spindle At Speed, Spindle Zero Problem
« on: October 20, 2017, 03:02:55 PM »
Hi Hakan,
kool, that is very much what I had in mind for your machine.
Only a week or so ago you were convinced that you couldn't write or didn't want to write any Lua code now you're doing it on your own!
An alternative that you might wish to explore in the future is having another macro, m100 for instance, that when called does things like
record the name of the current G code file, the line number being executed.....and so on. All the features you might require in a shutdown script.
In the case of your m3, m4 or m5 scripts an unresponsive spindle might qualify as a shutdown event. If that were the case you'd substitute
mc.mcCntlGcodeExecuteWait(inst,'m100') for your current shutdown statement mc.mcCntlCycleStop(inst, 0).
Craig
kool, that is very much what I had in mind for your machine.
Only a week or so ago you were convinced that you couldn't write or didn't want to write any Lua code now you're doing it on your own!
An alternative that you might wish to explore in the future is having another macro, m100 for instance, that when called does things like
record the name of the current G code file, the line number being executed.....and so on. All the features you might require in a shutdown script.
In the case of your m3, m4 or m5 scripts an unresponsive spindle might qualify as a shutdown event. If that were the case you'd substitute
mc.mcCntlGcodeExecuteWait(inst,'m100') for your current shutdown statement mc.mcCntlCycleStop(inst, 0).
Craig