Solved Connection lost, attempting to reconnect
-
Everything has been working fine with our printer, we just changed out our extruder and noticed it was retracting when it should be extruding, made the change in the g code, the printer shut down like normal and restarted, but now just reads connecting on the Duet screen and the dashboard just reads connection lost, attempting to reconnect.
Printer is a Modex big 60
We are running Duet wifi and Duex 5 with the latest updates but cannot retrieve any info to give you exact versionsAny thoughts on what to try, besides turning off and unplugging power?
Thank you
-
@sculpt-fabricator said in Connection lost, attempting to reconnect:
Everything has been working fine with our printer, we just changed out our extruder and noticed it was retracting when it should be extruding, made the change in the g code, the printer shut down like normal and restarted, but now just reads connecting on the Duet screen and the dashboard just reads connection lost, attempting to reconnect.
Printer is a Modex big 60
We are running Duet wifi and Duex 5 with the latest updates but cannot retrieve any info to give you exact versionsAny thoughts on what to try, besides turning off and unplugging power?
Thank you
We tried M552 S1 on the PanelDue but get no response on the screen, we also noticed when we click on the SD card icon, it doesn't show anything on the card, but if we bring the card over to the computer we can verify everything is still on the card. this would be the sd card from the duet wifi board
-
To do some proper troubleshooting I think you'll need to remove the Duet from the enclosure and test it on the bench connected to a PC with USB. You can follow this guide to see how far you can get.
https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond
-
@phaedrux The lights look good
when connecting to the device we get
USB serial device (com4)
is this considered unknown device? -
@phaedrux we did get in and ran a M122, which comes back stuck in spinloop?
-
Can you copy and paste the full m122 response please?
-
@phaedrux we actually followed the
Fallback procedure #1 and got it back up and running again, thank you for your help -
-