Duet Mini 5+ wifi Dropping Connection
-
Not sure where this problem originated from, but it seems to have started with the last firmware update (3.5 RC1+). Printing operations are fine, but when I go into the input shaping plugin, and start viewing my old IS graphs, the internet connection will randomly drop, and it fails to reconnect. I end up having to reboot the printer to reconnect.
I pulled an M122 after rebooting this last time:
11/25/2023, 3:31:45 PM M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-03 17:18:21) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: GS9VZ-V296U-D65J0-40KMY-L713Z-RU7ZK Used output buffers: 3 of 40 (34 max) === RTOS === Static ram: 102812 Dynamic ram: 127364 of which 12 recycled Never used RAM 11228, free system stack 194 words Tasks: NETWORK(2,nWait,15.0%,201) HEAT(3,nWait,0.0%,371) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,799) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,350) TMC(4,delaying,0.7%,108) MAIN(1,running,82.5%,652) IDLE(0,ready,0.9%,29) AIN(4,delaying,0.8%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:19 ago, cause: power up Last software reset at 2023-11-20 18:38, reason: User, Gcodes spinning, available RAM 10740, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 79647, completed 79646, timed out 0, errs 0 MCU temperature: min 51.1, current 51.1, max 55.9 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 4155, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 4155, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 4155, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 4155, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 4155, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-25 15:31:42 Cache data hit count 146924191 Slowest loop: 29.18ms; fastest: 0.17ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.4ms, write time 5.8ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, 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 idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 718, received 1561, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6053, peak Tx sync delay 6, free buffers 26 (min 25), ts 398/397/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 67.00ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address f0:08:d1:03:80:d7 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 43056 WiFi IP address 192.168.1.135 Signal strength -29dBm, channel 3, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0``` -
@br7408 If you can it would be interesting to see what the M122 output is when you have lost the connection, you could obtain this by connecting via USB abd running the M122 in the USB console.
-
@br7408 said in Duet Mini 5+ wifi Dropping Connection:
Firmware version 2.1beta4
You could also try uploading the 1.27 wifi server version and see if the problem persists.
-
@Phaedrux said in Duet Mini 5+ wifi Dropping Connection:
@br7408 said in Duet Mini 5+ wifi Dropping Connection:
Firmware version 2.1beta4
You could also try uploading the 1.27 wifi server version and see if the problem persists.
I will try this first. Seems like it all started after I went to the newer firmware.
Also… any idea why I keep getting “disk almost full” messages? That started at the same time as the wifi drop issue.
I pulled the SD card and checked it and it is only halfway full.
-
@gloomyandy said in Duet Mini 5+ wifi Dropping Connection:
@br7408 If you can it would be interesting to see what the M122 output is when you have lost the connection, you could obtain this by connecting via USB abd running the M122 in the USB console.
Was hoping not to have to do that but I’ll run it tomorrow when it pops up again.
-
@br7408 SD cards supplied by Duet3D are split into two partitions, one for standalone (formatted FAT32), one for SBC (formatted for Linux), so you could be looking at the wrong partition. Check free space on the Duet by sending M39. You can reformat the SD card for one or the other to give yourself more space. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card
Ian
-
@droftarts That was it... I reformatted and now have over 7gb.
-
@Phaedrux Specifically, which file is the 1.27 server version?
I'm assuming it was packaged with the older 3.46 firmware, and I'm assuming it is compatible with the other newer firmware versions I'm running?
-
@br7408 Here you go: https://github.com/Duet3D/DuetWiFiSocketServer/releases/tag/1.27
It is compatible, but some features (like the Enterprise authentication and MQTT interface are not available).
-
Thanks!
