Perhaps 1003 is feedhold and not stop?

1003 I believe is Stop and should really only be used when all motion has stopped, so likely better to use OEM 1001 (feedhold) first and have a
While IsMoving()
Wend
between the two

Hood

I found the problem, possibly an error with mach, when issueing 1003 controller goes into e-stop, therefore the only way to retrieve would be to "reset" since issueing 1003 a second time doesn't help. When the button is assigned directly as stop instead of via script then it stops only, doesn't go into estop.

HUM 1003 does not go into reset/estop here when used in a script.

So you want a script that will safely stop the program and then rewind and clear messages??

Hood is correct that you should do a Feedhold/pause and the While ISmoving Wend then issue the stop. Otherewise you can loose position.

I have a script that will do what you want I will look it up and test it.

Just a thought(;-) TP

Can you post teh code you tried so I can test it here?

Thanks (;-) TP

Don't mind losing position, however, "DoOEMButton(1003)" by itself causes estop to activate, even just that line by itself. Like I said before if I hit the button when it isn't coded and given function stop standard code 3 it works just fine, it stops, doesn't rewind though, but it stops without going into e-stop.

I've tried the code, still didn't work, even if the program is not executing, just by pressing the button with code 1003 causes e-stop to activate.

You can see the attached screen.

F10 is shortcut for start when in the auto section.

Do you have servos? Do they have a fault output that you have going to Mach? If yes then that will be why you are getting the E-Stop triggering when you do OEM1003

Hood

Just tested the 1003 here and it does not trip a reset here.

(;-) TP