G-Code to turn machine OFF

cmorley wrote: I would try something like:

Code:

#! /bin/bash halcmd setp halui.machine.off 0 halcmd setp halui.machine.off 1 exit 0

halui expects the pin to toggle.

Chris M

Booya, we have a winner !

Okay so tried that code, didn't work but it led me to the answer

M130 M129 M300
M129 effectively resets the Pin, but M129 then M130 straight after appears to try too quickly before the M129 has reset the pin and it doesn't work

M300 resets the pin, turns off coolant & spindle, waits 5 seconds for them to spin down then hits the E-Stop

I'm now one step closer to having it all set exactly how I want, thank you for the help

I am surprised that the G-code subroutine continues to execute through e-stop.

Try doing it all in the bash script, but re-set the pins afterwards.

I don't have bash here so can't test this, but the idea is to turn off spindle and coolant, wait 5 secs, toggle e-stop then poll the machine status until e-stop has activated.
Then all the halui pins are toggled back to zero for the next time round.

5-7 seconds of untrou states that is a real whear behavior even on e-stop

E-stop is e-stop
then user shoudt take action non Mcode state changes after this

Why at all shoudt the G-code trigger e-stop
this is mashine and safty issue non g-code related

im with you at M9 M5 M30

the Mashine off as on large printings 24+ hr is here a Realy that shuts the complete power down

g-code mashine issues behavior is real wheard

andypugh wrote: Try doing it all in the bash script, but re-set the pins afterwards.

I gave your code a try as it seemed a bit more elegant then my solution but for some reason the sleep command doesn't work in the bash script.

If I even try just then the code still runs but it seems to ignore the sleep command and just toggles it off straight away as if sleep wasn't there.

I also tried sleep 5s but no dice either.

Try "5s"
Maybe it defaults to nS or something?

get a
sleep --help

and somtimes the wrong bash sleep versions
sleep --version