motion.digital-out-00 problem

I am on a train, but just remembered that I have a LinuxCNC virtual machine installed.

Unfortunately ON_ABORT_COMMAND isn't working on it, which is something that I really need to look at.
It seems to always output the message "Bad character '[' used" which doesn't make any sense.

Andy, Thank you for always helping me, you are a great support for me and my projects!!!

Before writing the post, I used an AND in Classiclader and it didn't work.

This project consists of 2 high-current inductors that melt metal with sprayed powder to integrate them into a single layer of hardened material.

The first inductor and the powder filler gun occupy me with the signals connected to M7-M8 and these are turned off with an emerogenic state.

The machine has a spindle that I turn on with M3 and also turns off in a state of emergency

The problem I have in the second inductor, which when using M64P0, I am active and never turns off no matter what happens and whatever the state of linuxcnc.

It is a machine with 5 axes, 3 linear and 2 rotary. I hope to try what you say, thank you very much again

The "And2" would be in HAL, not classic ladder.
(Sorry for the delayed response, I only seem to get to the forum when I am on a train at the moment)

I have this problem as well, when the M64 P05 is turned on, I press E-stop, it does not turn off the digital P5, the working status continues. How can this problem be solved?

I'm reading this

linuxcnc.org/docs/stable/html/remap/rema...g_dealing_with_abort

I have my eye on this, see github.com/LinuxCNC/linuxcnc/issues/2532

Until that change is implemented, you can do what you need (probably) in HAL.

The simplest approach is just to "and2" the digital output with the machine.is-on HAL pin before sending it to the destination.

This probably needs to be combined with a startup G-code which turns off the output, or it will go live at moment the machine comes back on again.

A more complex interaction could be set up with combinations of the flipflop, toggle and edge HAL components.

Or it might be best to construct a custom HAL component with the following behaviour:

If the machine is turned off the pin takes a settable default state
if the machine is turned on, the pins retain the default state (or take a different default state?)
If the input toggles from low to high and the machine is on - the output goes high
if the input toggles from high to low and the machine is on - the output goes low.

This is not entirely the same as the desired behaviour, as I think that if the output was set high before the machine-off it needs to be set off before setting on to trigger a change to the output described above.