Duet Ethernet has disconnected and won't re-connect - help needed
-
As title. I started a print and about 5 to 10 minutes in, DWC disconnected and it won't re-connect. The print is running fine - just no DWC connection. This board has been running fine and it was one of the first Ethernet boards. It's been on for about 36 hours since the last power cycle.
The LED next to the Ethernet socket is flashing. The printer is connected to a 16 port switch and the LED next to the port on the switch is also flashing. I have a BT Smart Hub and the switch is connected to that (all Gigbit Ehernet and cat 5E or cat 6 cables). The BT hub manger shows that all other devices that are connected to this switch are functioning normally but the printer shows as disconnected. The IP address is DHCP but fixed so it will always use the same address. I've checked and the address hasn't changed in the hub manager.
PanelDue seems to be functioning normally. The console on PanelDue shows "Network running IP address = 192. etc etc and it is the same IP address that I've always used and which is fixed by the BT Hub Manager.
Entering M122 from the PanelDue shows used output buffers 2 of 32 then the platform as being "RepRap firmware for Duet Ethernet version 1.20RC2 running on Duet Ethernet 1.0 +Due."
I've tried closing FireFox and reopening it. I've tried a different cable and I've tried connecting it to a different port on the network switch.
Now I've run out of ideas. I can't cycle the printer power just yet as I'm in the middle of a print.
-
Update.
After the print had finished, I cycled the power to the printer and that has fixed the problem. So any ideas as to the cause?
-
I've had another report of a similar occurrence on more than on printer and it is on my list to investigate tomorrow. If it happens again, please send M552 S-1 from PanelDue to shut down the network, then M552 S1 to restart it, and see if that lets you connect again.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
Don't know if it helps the search at all, but that hasn't happened to me since I moved to 1.21RC4, though I've not been using the machine much in the last few weeks, I must have used it for about 10 prints since update.
It was happening regularly (most times I used the printer) under 1.20
Just moved the the 1.21 Release tonight, I will shout if I see problems again.Dave
-
@dc42 said in Duet Ethernet has disconnected and won't re-connect - help needed:
I've had another report of a similar occurrence on more than on printer and it is on my list to investigate tomorrow. If it happens again, please send M552 S-1 from PanelDue to shut down the network, then M552 S1 to restart it, and see if that lets you connect again.
Hi David,
This happened again, while the printer was idle but after having been on for about 22 hrs. I tried M552 S-1 followed by M552 S1 but it didn't fix it. I cycled the power and was able to connect straight away. HTH.
-
Hi Ian. If it happens again can you try a M122 to see if there is information about the reset reason in there.
-
@t3p3tony said in Duet Ethernet has disconnected and won't re-connect - help needed:
Hi Ian. If it happens again can you try a M122 to see if there is information about the reset reason in there.
Hi Tony,
I tried M122 the first time it happened - see my first post. Everything reported looks normal to me. It's not a huge problem - just a minor irritation really. Cycling the power on the machine restores the connection and web interface. Of course I can't do that in the middle of a print but the print itself all works as it should.
Cheers
-
@deckingman sure, but maybe next time it wont be normal
-
@t3p3tony said in Duet Ethernet has disconnected and won't re-connect - help needed:
@deckingman sure, but maybe next time it wont be normal
Oh sorry, I didn't make it clear that I tried M122 this time as well as the first time, with the same result - i.e nothing untoward reported but if I get the problem again, I'll make a habit of doing M122. Maybe if I do it quick enough after the disconnect, something might show up.....
