Duet keeps losing wifi connection

appjaws

I am running the following with web control running on windows 11
Duet 2 WiFi 2WiFi 3.5.0-rc.4
Duet WiFi Server n/a 2.1beta7
Duet Web Control DWC 3.5.0-rc.4

16/04/2024, 12:04:47 Connection established
16/04/2024, 12:04:33 Connection interrupted, attempting to reconnect...
HTTP request timed out
16/04/2024, 12:04:32 Failed to get file list
HTTP request timed out
16/04/2024, 12:04:24 Connection established
16/04/2024, 12:04:24 Connection interrupted, attempting to reconnect...
HTTP request timed out

this is happening quite often during a print. Any ideas on how to resolve this issue?

jay_s_uk

@appjaws can you post an output of M122 after it has occurred?
which firmware version were you running previously?
can you tell use a bit more about your wifi network?

appjaws

@jay_s_uk said in Duet keeps losing wifi connection:

M122
previous firmware version was 3.4.4
What information do you need ref wifi network?

16/04/2024, 12:24:33 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.4 (2024-04-09 09:47:24) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JTDL-3S86Q-18Z3F
Used output buffers: 3 of 26 (21 max)
Error in macro line 115 while starting up: Accelerometer not found on specified port
=== RTOS ===
Static ram: 23256
Dynamic ram: 77504 of which 0 recycled
Never used RAM 9072, free system stack 98 words
Tasks: NETWORK(2,nWait 6,257.6%,211) HEAT(3,nWait 5,1.5%,319) Move(4,nWait 5,34.8%,274) DUEX(5,nWait 5,0.0%,24) MAIN(1,running,1481.0%,677) IDLE(0,ready,0.5%,29), total 1775.4%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 01:20:54 ago, cause: power up
Last software reset at 2024-04-11 15:18, reason: User, Gcodes spinning, available RAM 12936, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU temperature: min 11.7, current 32.1, max 33.4
Supply voltage: min 24.1, current 24.6, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/3, heap memory allocated/used/recyclable 2048/1168/1104, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0
Driver 1: ok, SG min 0
Driver 2: ok, SG min 0
Driver 3: ok, SG min 0
Driver 4: ok, SG min 0
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: standstill, SG min 0
Driver 10:
Driver 11:
Date/time: 2024-04-16 12:24:32
Cache data hit count 4294967295
Slowest loop: 213.49ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 5.6ms, write time 36.3ms, max retries 0
=== Move ===
DMs created 83, segments created 19, maxWait 486507ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00
next step interrupt due in 55 ticks, disabled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 29673, completed 29633, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X145.237 Y92.406 F1000 U146 V93" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 1
Code queue 0 is empty
=== DueX ===
Read count 1, 0.01 reads/min
=== Network ===
Slowest loop: 204.76ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta7
MAC address 84:f3:eb:83:49:06
Module reset reason: Turned on by main processor, Vcc 3.37, flash size 2097152, free heap 42960
WiFi IP address 192.168.0.143
Signal strength -34dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

jay_s_uk

@appjaws one for @rechrtb I suspect

rechrtb

Hello @appjaws ,

Based on the logs you posted I can't see anything weird - particularly the M122 output.
Assuming the M122 output was taken after the "disconnections" have occured - the WiFi module
reports 0 reconnections which seems to indicate that the module itself is not losing the connection to the router - and maybe the issue occurs on the socket layer or DWC.

is it possible for you to turn on debugging by issuing commands:

M111 P14 S1
M111 P1 S1

You would need to connect to the board via USB in order to monitor the output logs. Much better if you can capture and save the logs to a file during the duration of a print when these disconnections occur (I'm not sure what terminal emulator you use, but something like PuTTY can save the logs to a local file).

droftarts

@appjaws Is this new behaviour since updating the Duet board firmware and WiFi module firmware, or has this always been an issue?

Ian

appjaws

@droftarts
This has started since updating the firmware.
This morning I printed for 2.5 hrs and the WiFi disconnected 3 times.

appjaws

@appjaws Today, disconected twice
17/04/2024, 12:25:17 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.4 (2024-04-09 09:47:24) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JTDL-3S86Q-18Z3F
Used output buffers: 2 of 26 (26 max)
Error in macro line 115 while starting up: Accelerometer not found on specified port
=== RTOS ===
Static ram: 23256
Dynamic ram: 77480 of which 0 recycled
Never used RAM 9408, free system stack 118 words
Tasks: NETWORK(1,ready,14.5%,220) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,274) DUEX(5,nWait 5,0.0%,24) MAIN(1,running,85.4%,677) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:11:59 ago, cause: power up
Last software reset at 2024-04-11 15:18, reason: User, Gcodes spinning, available RAM 12936, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
MCU temperature: min 25.2, current 27.5, max 27.7
Supply voltage: min 24.1, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/600/548, gc cycles 1
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 0
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: standstill, SG min 0
Driver 10:
Driver 11:
Date/time: 2024-04-17 12:25:16
Cache data hit count 4294967295
Slowest loop: 15.58ms; fastest: 0.20ms
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 0.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 27176ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, 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 65, completed 65, 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 0 is on, I-accum = 0.6
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Movement locks 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== DueX ===
Read count 0, 0.00 reads/min
=== Network ===
Slowest loop: 21.18ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta7
MAC address 84:f3:eb:83:49:06
Module reset reason: Turned on by main processor, Vcc 3.37, flash size 2097152, free heap 42960
WiFi IP address 192.168.0.143
Signal strength -28dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
17/04/2024, 12:24:32 Test = 4
Auto calibration successful, Initial Deviation 0.004mm
Auto calibration successful, Final Deviation 0.000mm
17/04/2024, 12:24:25 M292 S9
Leadscrew adjustments made: 0.007 -0.009 0.014, points used 3, (mean, deviation) before (0.008, 0.004) after (-0.000, 0.000)
17/04/2024, 12:24:25 M292 S6
Leadscrew adjustments made: 0.007 -0.009 0.014, points used 3, (mean, deviation) before (0.008, 0.004) after (-0.000, 0.000)
17/04/2024, 12:24:08 Leadscrew adjustments made: -0.007 -0.018 0.033, points used 3, (mean, deviation) before (0.009, 0.013) after (-0.000, 0.000)
Test = 3
Repeating calibration because Initial Deviation (0.013mm) must be < 0.01
and Final Deviation (0.000mm) must be within 0.005 of initialDeviation
17/04/2024, 12:23:52 Leadscrew adjustments made: 0.008 0.041 -0.044, points used 3, (mean, deviation) before (-0.010, 0.019) after (-0.000, 0.000)
Test = 2
Repeating calibration because Initial Deviation (0.019mm) must be < 0.01
and Final Deviation (0.000mm) must be within 0.005 of initialDeviation
17/04/2024, 12:23:46 Error in start-up file macro line 115: Accelerometer not found on specified port
17/04/2024, 12:23:39 Failed to get file list
HTTP request timed out
17/04/2024, 12:23:36 Leadscrew adjustments made: -0.067 -0.010 -0.016, points used 3, (mean, deviation) before (-0.039, 0.017) after (-0.000, 0.000)
Test = 1
Repeating calibration because Initial Deviation (0.017mm) must be < 0.01
and Final Deviation (0.000mm) must be within 0.005 of initialDeviation
17/04/2024, 12:23:31 Connection established
17/04/2024, 12:23:18 Connection interrupted, attempting to reconnect...
Operation failed (Reason: Service Unavailable)
17/04/2024, 12:23:08 Error in start-up file macro line 115: Accelerometer not found on specified port
17/04/2024, 12:23:08 Connection established
17/04/2024, 12:23:02 Connection interrupted, attempting to reconnect...
HTTP request timed out
17/04/2024, 12:22:54 Connection established
17/04/2024, 12:22:48 Connection interrupted, attempting to reconnect...
HTTP request timed out
17/04/2024, 12:14:43 M111 P1 S1
Debugging enabled for modules: Network(1 - 0xffffffff) WiFi(14 - 0xffffffff)
Debugging disabled for modules: Platform(0) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unused(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Expansion(18)
17/04/2024, 12:14:22 M111 P14 S1
Debugging enabled for modules: WiFi(14 - 0xffffffff)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unused(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Expansion(18)

jay_s_uk

@appjaws you'll need to connect via USB to collect any data from M111

Phaedrux

3.5 has released now. Can you try uploading the full zip file? The wifi server has been updated.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0

If you're still having issues after that, can you try rolling the wifi server version back to 1.27?

https://github.com/Duet3D/DuetWiFiSocketServer/releases/download/1.27/DuetWiFiServer.bin

rechrtb

@appjaws Hi @appjaws, please try to upgrade first to the newest RRF and wifi firmware as suggested by @Phaedrux .
However, if issues persist, I think that we really need those network and module debug logs.

appjaws

@rechrtb after the updates the problem seems to be resolved.
Thank you for all your help

rechrtb

@appjaws Glad it's working for you now!