Emergency Stop didn't reconnect RRF3.01 RC7

A Former User

See if you can use trigger 0 or 1 as is?

https://duet3d.dozuki.com/Wiki/Gcode#Section_M581_Configure_external_trigger

Trigger number 0 causes an emergency stop as if M112 had been received. Trigger number 1 causes the print to be paused as if M25 had been received. Any trigger number # greater than 1 causes the macro file sys/trigger#.g to be executed.

DavidHyper

@bearer

I have tried trigger0.
It looks like the same like my actual Setup.
In my opinion the M999 Gcode is not accepted.

At RRF2.05 it isn't a problem with exactly the same setup.

Maybe it has something to do with pullup resistors?

A Former User

@DavidHyper said in Emergency Stop didn't reconnect RRF3.01 RC7:

In my opinion the M999 Gcode is not accepted.

is not compatible with

@DavidHyper said in Emergency Stop didn't reconnect RRF3.01 RC7:

Maybe it has something to do with pullup resistors?

if there was a problem with pullups, it'd be all or nothing with the commands in the trigger. on the other hand if both m112 and m999 fail, then maybe.

the simplest is perhaps to post the parts of your old working config and some of the config wizzards will verify it in a jiffy.

DavidHyper

M574 E0 S0			; Set Emergency Stop active high

; Emergency Stop
M581 E0:S1 T2 C0                          	    ; Configure external trigger
                                                    ; When Z stop switch closes, execute sys/trigger2.g
                                                    ; Trigger on rising edge (S1, default), falling edge (S0), ignore input (S-1)
                                                    ; C0 = trigger at any time (default) C1 = only when printing a file from SD

M582 T2						    ; Check actual State

Thats my Config in RRF2.05

The trigger is exactly the same as above

A Former User

@DavidHyper said in Emergency Stop didn't reconnect RRF3.01 RC7:

M574 E0 S0

think that should translate to "!e0stop"in your M950 command. Not sure about the J parameter. J1 equals e1stop in the docs. Someone who knows that they're talking about can probably help you better..

c310

@DavidHyper said in Emergency Stop didn't reconnect RRF3.01 RC7:

c didn't reconnect until i make a second emergency stop at my panelDue
The emergency stop ist a normal NC Push Button and connected to the e0stop input.
It seems for me that the S

this is an issue in the DWC.

i have the same problem too: pressing external emergency stop button HALTS the printer, but does not restart it. This happens only in DWC.

Once you switch to old style web UI (http://printer_IP/reprap or find DWC1 link in DWC UI) and press your physical emergency stop button, printer halts and resets (with the UI prompt).
see my post here

first bug was resolved in DWC 2.1.2, however "auto reset" option is not implemented and i do hope that @wilriker or @chrishamm will fix it soon.

chrishamm

@c310 I'll try to squeeze this into DWC 2.1.3. If you are using an external E-stop button, perhaps it's a good idea to set up a trigger to reset the controller when you release it again.

DavidHyper

Thank you all!

c310

@chrishamm said in Emergency Stop didn't reconnect RRF3.01 RC7:

y to squeeze this into DWC 2.1.3. If you are using an external E-stop button, perhaps it's a good idea to set up a trigger to r

@chrishamm, thank you very much for the fix in 2.1.3. It works perfectly!

DavidHyper

@chrishamm
how do i set up a trigger the reset the controller when i release it again?
I don't understand that to get it working.

c310

@DavidHyper maybe here M581 and carefully look at your duet version. there are big differences in this command.

create file called trigger2.g and put there all you want.
assign this trigger to one of the pins
once you activate pin, than macro is executed.