Constant "Network Error" on Duet3 6HC

e4d

Hello, I have a printer with a Duet3 6HC. I keep getting disconnection on the mainboard. It is every few seconds (as you can see here) and prevent me from doing anything on the board.

alt text

Here's the result of the M122 :

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-956L2-G43S8-6JTD6-3SS6K-KA1AH
Used output buffers: 3 of 40 (40 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 100624 of which 0 recycled
Never used RAM 94432, free system stack 200 words
Tasks: NETWORK(ready,37.6%,220) ETHERNET(notifyWait,1.2%,453) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,8.4%,91) MAIN(running,52.5%,925) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:03:52 ago, cause: power up
Last software reset at 2023-03-07 14:48, reason: User, GCodes spinning, available RAM 97104, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Step timer max interval 132
MCU temperature: min 36.1, current 42.4, max 42.6
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.0, under voltage events: 0
Heap OK, handles allocated/used 99/34, heap memory allocated/used/recyclable 2048/606/240, gc cycles 12
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 1, reads 37264, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 1, reads 37264, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 1, reads 37264, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 1, reads 37265, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 1, reads 37265, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 1, reads 37265, writes 14 timeouts 0
Date/time: 2023-03-15 17:09:07
Slowest loop: 11.41ms; fastest: 0.05ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 5.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is doing "G4 P200" in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 7230, received 11642, lost 0, boc 0
Longest wait 2ms for reply type 6029, peak Tx sync delay 90, free buffers 50 (min 49), ts 1162/1161/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 16.22ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 6 of 8
= Ethernet =
State: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 5 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

Do you have any idea to how I can solve this ?

Phaedrux

Is your DWC version matching the firmware at 3.4.5?
Is this a recent problem? Has it worked before?

e4d

@Phaedrux the firmaware is matching the DWC version at 3.4.5.
I worked like a charm before and it's getting worse. There is some phase where it's unusable as I can't even upload a file without getting disconnected constantly

Hugsy

Hi,

I have the same problem on multiple machines here. It's starting to be a real deal as our company is starting to produce 3D printers with Duet boards but this bug is still causing problems on all 6HC equipped prototypes internally.

@e4d I can see that in your M122 you have 6 connected clients, try reducing them, it definitely helps us here.

I'm currently trying to change some settings in the firmware but without any success so far.

Phaedrux

@e4d In order to rule out the local network, can you configure the printer to connect directly to a computer via ethernet and see if the problem is resolved?

As described here: https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#wired-direct-connection

Phaedrux

@Hugsy Do you have a thread on your issue already? If not, I suggest creating one so we can capture it and provide assistance.

Hugsy

@Phaedrux We were just thinking it's a hardware limitation so we didn't do a thread on it. But now that we struggle with just a few http clients maybe it's time to do a thread about it.

Connectivity always was really buggy with the 6HC between the mDNS not working and the Ethernet cutting off.
I'll make a thread about it right now

T3P3Tony

@e4d I notice that you have 6 out of 8 HTTP sessions in use, are you connecting to the board from multiple devices?

e4d

@T3P3Tony I am, multiple computers in the office. I have better result with deconnections using a shielded router. It still disconnect from time to time but way less that before

T3P3Tony

@e4d one theory is that you are running out of HTTP sessions can you restrict the number of connected devices to 2 or 3 as a test and see if that changes the problem.

dc42

@e4d another possibility is that the large number of http clients is causing RRF to run out of output buffers. On the 6HC we have enough spare RAM to increase the number of buffers.