Wifi lost midprint

oliof

stub report because its late and I am midprint, will add M122 tomorrow...

about 4 hours into a 10 hour print, my Duet 3 mini 5+ running 3.5b2 fell off the home network. Usually network strength is excellent (I have a mesh wifi network with coordinated APs on ebery floor). Other clients on the same floor have continued connectivity. The printer does not react to pings and my home network system reports the printer as offline. Also pinging the reserved IP address is failing, so I am fairly confident this is an issue with the ESP having dropped off, and not a client / browser issue (I also tried accessing with varipus devices, none were able to connect).

oliof

Running M557 S0 and then M557 S1 via serial console reinstated WiFi.

M122 output via serial before restarting wifi below.

M122                                                                            
=== Diagnostics ===                                                             
RepRapFirmware for Duet 3 Mini 5+ version 3.5beta2 (2023-02-08 17:42:04) running
 on Duet 3 Mini5plus WiFi (standalone mode)                                     
Board ID: 20ZJU-P196U-D65J0-40KM6-KS03Z-ZD7N0                                   
Used output buffers: 1 of 40 (23 max)
=== RTOS ===                                                                    
Static ram: 103012                                                              
Dynamic ram: 125648 of which 384 recycled                                       
Never used RAM 11900, free system stack 120 words                               
Tasks: NETWORK(ready,16.5%,217) HEAT(notifyWait,0.4%,326) Move(notifyWait,19.1%,
252) CanReceiv(notifyWait,1.2%,771) CanSender(notifyWait,0.6%,325) CanClock(dela
ying,0.1%,340) TMC(notifyWait,9.2%,71) MAIN(running,36.5%,433) IDLE(ready,5.5%,3
0) AIN(delaying,10.8%,263), total 100.0%                                        
Owned mutexes: USB(MAIN)                                                        
=== Platform ===                                                                
Last reset 17:15:54 ago, cause: power up                                        
Last software reset at 2023-04-07 09:26, reason: User, Gcodes spinning, availabl
e RAM 12912, 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 62155833, completed 62155832, timed out 
0, errs 0                                                                       
Step timer max interval 1490                                                    
MCU temperature: min 14.9, current 31.0, max 42.8                               
Supply voltage: min 23.7, current 24.1, max 24.3, 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 21, reads 5
9390, writes 21, timeouts 0, DMA errors 0, CC errors 0                          
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 21, reads 5
9390, writes 21, timeouts 0, DMA errors 0, CC errors 0                          
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 21, reads 5
9390, writes 21, timeouts 0, DMA errors 0, CC errors 0                          
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 21, reads 5
9389, writes 21, timeouts 0, DMA errors 0, CC errors 0                          
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 21, reads 5
9390, writes 21, timeouts 0, DMA errors 0, CC errors 0                          
Driver 5: not present                                                           
Driver 6: not present                                                           
Date/time: 2023-04-11 07:37:00                                                  
Cache data hit count 4294967295                                                 
Slowest loop: 254.73ms; fastest: 0.09ms                                         
=== Storage ===                                                                 
Free file entries: 20                                                           
SD card 0 detected, interface speed: 22.5MBytes/sec                             
SD card longest read time 9.6ms, write time 134.2ms, max retries 0              
=== Move ===                                                                    
DMs created 83, segments created 32, maxWait 2881040ms, bed compensation in use:
 none, comp offset 0.000                                                        
no step interrupt scheduled                                                     
=== DDARing 0 ===                                                               
Scheduled moves 1586913, completed 1586913, hiccups 0, stepErrors 0, LaErrors 0,
 Underruns [0, 0, 1], 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 0 is on, I-accum = 0.2                                                   
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 ready with "M122" 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 0x0000807                              
Code queue 0 is empty                                                           
Q1 segments left 0, axes/extruders owned 0x0000000                              
Code queue 1 is empty                                                           
=== CAN ===                                                                     
Messages queued 1813561, received 2489129, lost 0, boc 0                        
Longest wait 2ms for reply type 6026, peak Tx sync delay 3108, free buffers 18 (
min 7), ts 310773/310772/0                                                      
Tx timeouts 0,0,0,0,0,0                                                         
=== Network ===                                                                 
Slowest loop: 254.63ms; fastest: 0.00ms                                         
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)      
HTTP sessions: 0 of 8                                                           
= WiFi =                                                                        
Network state is changingMode                                                   
WiFi module is idle                                                             
Failed messages: pending 0, notready 0, noresp 0                                
Failed to get WiFi status                                                       
Socket states: 0 0 0 0 0 0 0 0                                                  
ok

Next step for me will be to re-add the 12864 Display so I have the chance for an emergency stop when WiFi goes out again.

gloomyandy

@oliof Which version of the WiFi firmware are you running?

gloomyandy

@oliof Also I assume you mean M552 not M557?

oliof

@gloomyandy yes, M552. Printer is currently off, I will check wifi version later today.

oliof

@gloomyandy that was on Wifi version 1.27 (now updated to 2.1b3). I was pretty sure I had updated but looks like I was mistaken. I will observe further.

T3P3Tony

@oliof can you see if you still get this issue with 3.5b3 and 2.1b4 please

oliof

@T3P3Tony I will keep an eye out. There were no issues with a small number if shorter prints so far.

tas

I am testing 3.5b3 with 2.1b4 the past few days. I have noticed this issue on a Duet 2 Wifi in standalone mode.

It seems totally random. Sometimes it happens after 10 minutes other times the print completes before it happens and sometimes it doesn't happen at all.

There are no issues with the prints I just lose connection with DWC.

M552 S0 then M552 S1on the PanelDue normally re-establishes the connection. The last time I tried it however it said an SPI transfer was pending or something to that effect. I had to reboot the printer to get the connection back.

Hope that info is helpful.

oliof

@tas best to connect via serial and running M122 next time this happens.

tas

@oliof Had the printer idling this morning. After about 3 hours could not connect with DWC.

PanelDue showed no errors. M552 S0 idled WIFI and M552 S1 reconnected. Then DWC worked as normal.

M122 through YAT just after the issue was noticed and before M552:

The only possible issue I see is error status 0x08.
Printer is fully functional, PanelDue is fully functional. It just seems to be loss of wifi.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.3 (2023-04-14 11:27:37) running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9D8-3S46M-KVV3P
Used output buffers: 1 of 26 (23 max)
=== RTOS ===
Static ram: 22192
Dynamic ram: 78056 of which 0 recycled
Never used RAM 12896, free system stack 156 words
Tasks: NETWORK(ready,14.1%,216) ACCEL(nWait,0.0%,348) HEAT(nWait,0.0%,328) Move(nWait,0.0%,364) MAIN(running,85.8%,410) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 03:10:50 ago, cause: power up
Last software reset at 2023-04-19 16:33, reason: User, Gcodes spinning, available RAM 11912, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x08
Aux0 errors 0,0,0
MCU temperature: min 19.5, current 20.8, max 21.3
Supply voltage: min 23.8, current 24.1, max 24.3, under voltage events: 1, 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 n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-04-20 10:34:05
Cache data hit count 4294967295
Slowest loop: 5.18ms; fastest: 0.19ms
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 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
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
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" 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
=== Network ===
Slowest loop: 19.89ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
Firmware version 2.1beta4
MAC address 50:02:91:e5:55:22
Module reset reason: Turned on by main processor, Vcc 3.34, flash size 2097152, free heap 46352
WiFi IP address 192.168.50.202
Signal strength -46dBm, channel 10, mode 802.11n, reconnections 1
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

oliof

@tas you probably have rebooted the machine already, can you run a bare M552 the next time this happens?

tas

@oliof I made sure to reboot WIFI after I ran the M122 but I know it looks clean. I did not restart the printer, I just did M552 S0 M552 S1.

Next time I will get M122 then try just M552 and let you know. So far all is ok.

tas

@oliof Here you go.

*M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.3 (2023-04-14 11:27:37) running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9D8-3S46M-KVV3P
Used output buffers: 1 of 26 (23 max)
=== RTOS ===
Static ram: 22192
Dynamic ram: 78056 of which 0 recycled
Never used RAM 12896, free system stack 156 words
Tasks: NETWORK(ready,37.4%,216) ACCEL(nWait,0.0%,348) HEAT(nWait,0.1%,328) Move(nWait,0.0%,364) MAIN(running,62.5%,410) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 06:18:49 ago, cause: power up
Last software reset at 2023-04-19 16:33, reason: User, Gcodes spinning, available RAM 11912, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x08
Aux0 errors 0,0,0
MCU temperature: min 19.7, current 20.1, max 21.6
Supply voltage: min 23.8, current 24.0, max 24.3, under voltage events: 1, 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 n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-04-20 13:42:04
Cache data hit count 4294967295
Slowest loop: 11.23ms; fastest: 0.19ms
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.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
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
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" 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
=== Network ===
Slowest loop: 20.09ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
Firmware version 2.1beta4
MAC address 50:02:91:e5:55:22
Module reset reason: Turned on by main processor, Vcc 3.34, flash size 2097152, free heap 45028
WiFi IP address 192.168.50.202
Signal strength -46dBm, channel 10, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
*

M552 from PanelDue:
WiFi module is connected to access point AxF_24G, IP address 192.168.50.202

M552 S0 on PanelDue:
Wifi module is idle

M552 S1 on PanelDue:
WiFi module is connected to access point AxF_24G, IP address 192.168.50.202

Confirmed that DWC is connected again. I did not reboot the printer, just entered M552 commands at the PanelDue.

Hope that helps narrow things down. Let me know if you need any other info.

tas

@oliof Here is one mid-print.

*M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.3 (2023-04-14 11:27:37) running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9D8-3S46M-KVV3P
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 22192
Dynamic ram: 78056 of which 0 recycled
Never used RAM 11864, free system stack 114 words
Tasks: NETWORK(ready,55.9%,214) ACCEL(nWait,0.0%,348) HEAT(nWait,0.2%,307) Move(nWait,9.3%,291) MAIN(running,34.5%,410) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 07:58:52 ago, cause: power up
Last software reset at 2023-04-19 16:33, reason: User, Gcodes spinning, available RAM 11912, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x1c
Aux0 errors 0,1,0
MCU temperature: min 19.9, current 23.5, max 23.9
Supply voltage: min 23.5, current 24.1, max 24.3, under voltage events: 1, 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: ok, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: ok, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-04-20 15:22:08
Cache data hit count 4294967295
Slowest loop: 216.58ms; fastest: 0.16ms
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 1.8ms, write time 468.0ms, max retries 0
=== Move ===
DMs created 83, segments created 43, maxWait 23842725ms, bed compensation in use: none, comp offset 0.000
next step interrupt due in 842 ticks, disabled
=== DDARing 0 ===
Scheduled moves 126858, completed 126827, 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.2
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X265.556 Y182.206 E.03005" in state(s) 0
USB is ready with "M122" 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
=== Network ===
Slowest loop: 470.56ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
Firmware version 2.1beta4
MAC address 50:02:91:e5:55:22
Module reset reason: Turned on by main processor, Vcc 3.34, flash size 2097152, free heap 44616
WiFi IP address 192.168.50.202
Signal strength -55dBm, channel 10, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
*

M552 gives the same as before:
WiFi module is connected to access point AxF_24G, IP address 192.168.50.202

No issues with the print itself.

oliof

@tas your issue is different than mine because M552 didnt return connectivity info

tas

@oliof Sorry to confuse the issue.

oliof

@tas no worries. In your case I would have assumed bad signal, but your signal strength is pretty decent at -55dBm. Nonetheless, if your antenna is in an enclosure or close to a wall, consider reloacting it.