Recovery after "Emergency Stop"
-
I'm making good use of the "Emergency Stop" button as I sort out motor assignments and polarities on my new CoreXY. To recover, I have to press the reset button on the Duet Wifi, wait a few seconds, and refresh my browser.
Is that the normal procedure? Wasn't expecting to have to press reset, though it's hardly a big deal.
Firmware Version: 1.17e (2017-02-10)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.14a -
I had this issue until I upgraded the firmware to 1.18.
-
If you are hitting the emergency stop button on the web interface it sends the commands M112 and then M999 which causes a software reset. Refreshing the browser window (or pressing the connect button, top left) should connect back to the Duet without the hardware reset button needing to be pressed
-
I had this issue until I upgraded the firmware to 1.18.
Where'd you get 1.18? The latest on git (https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Stable) seems to be 1.17.
-
If you are hitting the emergency stop button on the web interface it sends the commands M112 and then M999 which causes a software reset. Refreshing the browser window (or pressing the connect button, top left) should connect back to the Duet without the hardware reset button needing to be pressed
Not for me. No matter how long I wait after an emergency stop, when I refresh the browser the interface says it's connected, but it isn't. Nothing happens when I try to Home an axis, and when I try to edit .g files it says "Connect to your Duet to display System files". Everything's fine after a reset. Running Chrome 56.0.2924.87 (64-bit) on Windows 10.
-
Odd that may be a difference between 1.17 and 1.18
-
Yeah mine doesn't always reset without a hardware reset buts not a big problem.
Yonkiman - try https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge
For edge firmware.
-
try https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge
That worked! After an emergency stop I just have to wait 5-10 seconds (no reset, no refresh) and everything is working normally.
Thanks!
-
Odd that may be a difference between 1.17 and 1.18
Yeah Tony. It just shows as halted in DWC with 1.17 latest for some reason. With 1.18 it works as it should.
-
Thanks for the clarification, I just never noticed that before!
