Duets having network errors
-
We've recently noticed our Duet printers having connectivity issues. We've tried swapping in a fresh SD card, and also updating the RRF/DWC/Wifi Server Version to the latest to see if it would help, but we still seem to be having the same problem.
We have multiple printers that are all giving the same error. They're a mix of mini 5's and duet2 boards. Most of the time the printers will get through their prints but the odd time we've had a printer end up freezing/resetting mid print, which is when we noticed the string of network errors in the console.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JTDJ-3SD6K-9SXHF
Used output buffers: 3 of 24 (22 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93944 of which 44 recycled
Exception stack ram used: 264
Never used ram: 8840
Tasks: NETWORK(ready,356) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:49:00 ago, cause: power up
Last software reset at 2023-01-24 08:34, reason: User, spinning module GCodes, available RAM 8568 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 29.8, current 30.2, max 31.8
Supply voltage: min 26.6, current 26.8, max 27.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2023-01-24 10:06:49
Cache data hit count 4294967295
Slowest loop: 9.90ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.2ms, write time 4.6ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 1, completed moves: 1, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 247.06ms; fastest: 0.09ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address ec:fa:bc:25:b8:94
WiFi Vcc 3.41, reset reason Unknown
WiFi flash size 4194304, free heap 23720
WiFi IP address 192.168.0.214
WiFi signal strength -68dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0
- WiFi -
-
@Lamooth You should upgrade to RRF/DWC 3.4.5 and DuetWiFiServer 1.27. Also check out the WiFi troubleshooting guide.
-
@Lamooth Is it just on the Mac?
I remember having this problem for a long time - including duet resets midprint because of this. But this was in and before 3.2. Now it still happens every now and then, but never resets the Duet. At worst, I can't load the GUI at all, at best - I get a gray overlay over the GUI which prevents me from clicking stuff on the GUI, but at least I can see what's going on (this is much more often and worse when using BambuStudio-SoftFever edition).The errors, freezes and resets only happened on Mac (regardless of browser) - never on Windows.
The one thing that could help was disabling Eset's Firewall I had installed.
