Duet 2 Maestro -Random Connections loss
I know ,there are several threads similar to this one but after reading (as far as I can tell) ALL of them without finding a solution, I make a desperate attempt to get some help figuring this out...
Ever since I got my board I have had seemingly random problems with my ethernet connection. When it works it works perfectly but next time I power up my board I may get constant connection errors. Each "session" may last for 5 to 30 (tops) seconds.
Sending 100 pings gets about 30-40% lost packets.
Upgraded both firmware and Web, tried different SD-cards, tried 6 different ethernet cables (both shielded and non shielded) Tried two different routers (consumer grade) and one of my Cisco switches and a Cisco router (had them laying around since my time as a network admin)
Tried different network settings, dhcp and static makes no difference. Setting MAC on the board changes nothing, no conflicting IP's on my network.
Makes no difference if I am connected using USB and no 12v or no USB and only 12v.
WHEN it works and I just leave the printer on it works forever (but sometimes, after 10 days or so I might have to power down, not for connection issues but rather because it's pretty annoying to hear the fans 24/7 for 10 consecutive days when not printing JUST so that I won't loose my ethernet connection...
Web browser gives me either connection timout, host unreachable or connection_refused
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.02(RTOS) running on Duet Maestro 1.0
Board ID: 08D8M-9T8A2-MQNS0-7JTDG-3SW6P-17TGW
Used output buffers: 1 of 20 (10 max)
=== RTOS ===
Static ram: 19476
Dynamic ram: 92900 of which 0 recycled
Exception stack ram used: 212
Never used ram: 18484
Tasks: NETWORK(ready,672) HEAT(blocked,1356) MAIN(running,3940) IDLE(ready,204)
=== Platform ===
Last reset 00:22:21 ago, cause: power up
Last software reset at 2019-05-05 01:09, reason: User, spinning module GCodes, available RAM 18276 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 24.6, current 29.8, max 30.1
Supply voltage: min 0.0, current 12.2, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, read errors 0, write errors 0, ifcount 6, reads 53649, timeouts 0
Driver 1: standstill, read errors 0, write errors 0, ifcount 6, reads 53649, timeouts 0
Driver 2: standstill, read errors 0, write errors 0, ifcount 6, reads 53649, timeouts 0
Driver 3: standstill, read errors 0, write errors 0, ifcount 6, reads 53649, timeouts 0
Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 53649, timeouts 0
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 53655
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 53654
Date/time: 2019-05-10 14:26:07
Slowest loop: 3.35ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
lcd is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 5.72ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex
When having said connections issues with the Duet, it always effects the rest of the network, when pinging my router 100 pings I get around 15% packet loss and response times varying from 2-200ms
Veti last edited by
When having said connections issues with the Duet, it always effects the rest of the network, when pinging my router 100 pings I get around 15% packet loss and response
this indicates a problem with your network.
the duet should not effect the other part of your network.
(unless you have a hub instead of a switch and the duet would be blasting the network with 100% traffic)
@veti No hub.
I know, that's why it is a bit "weird", also it does not matter if the Duet is powered off or on after I start experiencing the connection problems with the board, as long as the ethernet cable is physically attached to the board and to the switch the whole network gets unstable but when I unplug the (powered off or on) Duet, the network is fine again.
What's extra frustrating is that I can't seem to reproduce the errors at will, it truly is random, the only constant is that:
a) When it works it does so indefinetly
b) When it doesn't it effects my entire network even if the Duet is powered off but the cable is still attached
Could there be some sort of short or loose connection on the ethernet connector on the Duet?
Veti last edited by
that sounds like a grounding problem.
i assume you have tried another network cable?
next time this happens pull the power plug on the duets psu rather than the network cable and see if the problem persists.
@veti Thanks, will try that! (having problems as of this moment, so I will get right to it!)
There seems to be in fact some grounding issue. I will order a new power supply (Was planning that upgrade anyway since I've had the same crappy one since 2014, will get a 24v Mean Well while I'm at it)
Will update when it arrives and verify that it solved the issue.
Thank you so much for the help!
that says that it has closed the connection to my board and if it happens again I should contact the author and share the error message. Should I start a new thread? Can all of this have something to do with the web UI?
Here is a screenshot of the error:
Can you confirm that you are still running main firmware 2.02, as shown in the M122 listing in your first post?
I can ask chrishamm to look into this message, but he will probably ask you to upgrade to Duet Web Control 2.0.0-RC6, available at https://github.com/chrishamm/DuetWebControl/releases.