Making M62/M63 codes failsafe

Is there a way to modify any settings to make M62 failsafe (revert to low) in the event of a program crash or emergency stop?  for example, a "following error" or something.

I'm using M62/M63 it to fire a laser and it works great until you manually stop motion or hangup.  Then the digital out stays high and the laser continues to fire.  Only after a deliberate (non zero) motion with M63 does it shut off.  For safety reasons, not ideal.

I'm using a 7i96 digital output pin if there's hardware solution someone is aware of

Thanks

 

Brilliant.  I'll give that a try.  Thanks

Not the correct forum, but since I started the topic here, I'll continue

The problem with wiring to "motion.motion-enabled" is that if you hit stop, motion is still enabled and the output continues to be high.  If i stop the program mid path, it continues to be high.

I think I need to do some digging and find a pin/signal to tie to that is only high when there is commanded motion.  It get more complicated because in this case I'd need to make sure it's motion in X OR Y (galvos).  Just in case it's a straight X or Y move.  Unless anyone can think of one?

I'm not sure what pin is "mode-is-auto".  Is that an "axis" pin?
 

I had the similar problem but a different application. Solved with a small component. net x-vel-cmd and net y-vel-cmd to this component, and check if there is any movement (non-zero). Or use 2 wcomp, out to or2 will do the same.
And have look at motion.motion-type 1: Traverse , 2: Linear feed, 3: Arc feed
 

Yeah, I spent some time thinking about bit banging the motion-type route.  That may be the way to go, but It had occured to me there may be a simpler solution.

NOT the motion-teleop-mode to flip the bit

AND2 motion.teleop-mode with motion.motion-enable

This protects against both conditions I'm worried about

1. "joint X following error" shut down
In this case motion.motion-enable = False and motion.teleop-mode = False (bit flipped to True)
AND2 function = False

2. Manual stop mid lasing path
In this case motion.motion-enable = True and motion.teleop-mode = True (bit flipped to False)
AND2 function = False

Under normal operation both motion.motion-enabled = True and motion.teleop-mode = False (bit flipped to True)
AND2 function = True

Seems like that should catch both of those conditions above with only 2 bitwise operations

Of course there's an additional AND2 with the M62 output pin for actual firing.  All 3 conditions need to be true in order to fire

Am I'm missing something?  Some condition I'm not covered for?  Since it's a laser and glavos, I'm not really doing any jogging.  Nor will I ever need to fire the laser when it's not running a program.  That's how deep holes are made
 

This might be helpful:
linuxcnc.org/docs/devel/html/remap/remap...g_dealing_with_abort