Hello,
I have a macro that has some JogOn commands called by my Gcode, each time I edit the Gcode and close/save it Mach3 regenerates the path and the macro runs, moving the tool around, but since the previous Gcode did not actually execute, it was just scanned for the path regen, the macro does weird/bad stuff.
Is there a way to inhibit the macro when the Gcode is just being scanned to regenerate the path? Is there a way to inhibit path regeneration?
Thanks,
Hobie