Hello Guest it is May 08, 2021, 04:13:21 AM

Author Topic: M1 optional stop  (Read 1154 times)

0 Members and 1 Guest are viewing this topic.

M1 optional stop
« on: February 19, 2018, 01:07:08 PM »
It appears that m1 'optional stop' only works when running a gcode file.  It has no affect in the MDI, mcCntlGcodeExecute, mcCntlMDIExecute or mcCntlGcodeExecuteWait.

I assumed (silly me) that execution of gcode would be the same across all execute requests.  How would you recommend accomplishing the same effect in a macro or button script?