Motion digital output value on stop

I'm using a motion.digital-out signal to control my dust collector from gcode. I got everything working well and got it all tied into my post.

I've run into one problem though. If I disable the machine or stop the program in the middle, the "M65 P3" is never run so the dust collector stays on.

Is there a way to ensure this runs or set a default value if a program is stopped or if the machine is disabled?

I know I could use an and2 component in my HAL to gate the signal if the machine is enabled but this wouldn't solve the stopped program problem. It would also start the dust collector back up if I re-enabled the machine.

You could gate it with a signal indicating motion
( maybe a near component looking at motion.current-vel )

Gating it doesn't solve the problem of it still being "on". For example, if I was running a program that used the dust collector but stopped it then started another program that didn't use the dust collector, the dust collector would turn on when the second program started.

Is there no way to "hook" into when a program is stopped or the machine is disabled to run a script?

You could change the default startup gcode to turn off the digital output
Or add this to you other programs

There is probably a way to launch a script maybe by monitoring 
halui.program-is-running
 

Is it possible to trigger a script or gcode when a HAL pin changes? I haven't seen anything in my search of the docs but I could be missing something.

If I gated the output with the machine enabled signal and was able to change the state of the motion.digital-out pin on the falling edge of halui.program.is-running I think it would do more or less everything I want.

Edit: My machine doesn't use flood coolant. Do you know if this automatically gets turned off when the program is stopped? I could repurpose this signal.

Edit again: This seems to have worked exactly as I wanted.

Have your dust collector output follow your spindle. No need to run the dust collector unless the spindle is running.

something like this maybe:

net spindle-enable <= spindle.0.on  => hm2_7i92.0.7i76.0.0.output-01

bevins wrote:

Have your dust collector output follow your spindle. No need to run the dust collector unless the spindle is running.

something like this maybe:

net spindle-enable <= spindle.0.on  => hm2_7i92.0.7i76.0.0.output-01

I like this approach. I don't know much about wood dust but perhaps you might want the fan to come on before the spindle so it gets up to speed. I guess it has some time to do that before the spindle is at speed but if needs a bit more time, you could add a timedelay component between spindle.0.on and your spindle relay

rodw wrote:

bevins wrote:

Have your dust collector output follow your spindle. No need to run the dust collector unless the spindle is running.

something like this maybe:

net spindle-enable <= spindle.0.on  => hm2_7i92.0.7i76.0.0.output-01
I like this approach. I don't know much about wood dust but perhaps you might want the fan to come on before the spindle so it gets up to speed. I guess it has some time to do that before the spindle is at speed but if needs a bit more time, you could add a timedelay component between spindle.0.on and your spindle relay



 

I dont think that will be an issue. The dust collector will come up faster than the spindle for sure. The only issue I had was the dust collector would stop during tool changes. That is expected behaviour though. I fixed that by putting a relay in parallel during a toolchange that kept the dust collector running.