SOLUTION: Can't connect to Duet Web Control
-
I will sometimes leave my printer on pause for up to 24 hours, and when I get back, I can't connect to the Duet Web Control anymore. Here is my solution:
- Connect your computer to the Duet board via USB cable. I have a long USB cable right next to my computer always plugged into the Duet because this happens so often.
- Open YAT and connect. If you can't connect, try rebooting your computer.
- Send command M552 S-1. This will turn off the wifi chip.
- Wait around 10 to 30 seconds
- Send command M552 S1. This will turn the wifi chip back on and hopefully connect. You might get a ton of errors, but just wait, and it might give you the IP address at the end. If the IP address is 255.255.255.255, repeat steps 3-5.
- You should be able to connect to the Duet Web Control!
-
What are the firmware versions of the Duet and wifi module?
-
@Phaedrux Thank you for your reply. How would I find that out?
-
Please send M122 in the gcode console and copy and paste the resulting report here.
-
undefined Phaedrux referenced this topic
-
@Phaedrux === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 54FNS-WR6KL-K65J0-409N0-5Q02Z-RQFPY
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 102996
Dynamic ram: 125200 of which 20 recycled
Never used RAM 13840, free system stack 143 words
Tasks: NETWORK(1,ready,8.4%,329) HEAT(3,suspended,0.0%,327) TMC(4,nWait,1.2%,114) MAIN(1,running,89.3%,704) IDLE(0,ready,0.3%,29) AIN(4,delaying,0.8%,266), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:03:33 ago, cause: power up
Last software reset at 2024-02-02 20:03, reason: User, Gcodes spinning, available RAM 13840, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 213501, completed 213500, timed out 0, errs 0
MCU temperature: min 19.4, current 27.5, max 27.5
Supply voltage: min 24.1, current 24.2, 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: 7 queued, 7 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19341, writes 13, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x41
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 19345, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 19345, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 395592143
Slowest loop: 99.91ms; fastest: 0.17ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, 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
=== 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
=== 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 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
Extruder 0 sensor: no filament
=== CAN ===
Disabled
Longest wait 56ms for reply type 6041, peak Tx sync delay 21228, free buffers 18 (min 17), ts 1005/1004/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 14.99ms; 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 =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok -
@tylersuard If you can please capture and post the M122 output when the WiFi module is working.
-
@gloomyandy === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 54FNS-WR6KL-K65J0-409N0-5Q02Z-RQFPY
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 102996
Dynamic ram: 125200 of which 20 recycled
Never used RAM 13840, free system stack 150 words
Tasks: NETWORK(1,ready,11.0%,219) HEAT(3,nWait,0.0%,331) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,798) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,351) TMC(4,nWait,1.2%,108) MAIN(1,running,86.7%,704) IDLE(0,ready,0.2%,29) AIN(4,delaying,0.8%,266), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:04:50 ago, cause: power up
Last software reset at 2024-02-16 10:34, reason: User, Gcodes spinning, available RAM 12640, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00433000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 290481, completed 290480, timed out 0, errs 0
MCU temperature: min 18.8, current 29.0, max 29.2
Supply voltage: min 24.0, 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: 5 queued, 5 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 26354, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 26355, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-02-16 14:26:01
Cache data hit count 531164937
Slowest loop: 8.30ms; fastest: 0.17ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.7ms, write time 0.0ms, 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
=== 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 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 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 2840, received 5014, lost 0, boc 0
Longest wait 55ms for reply type 6041, peak Tx sync delay 21902, free buffers 18 (min 17), ts 1452/1451/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 15.37ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) 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, notready 0, noresp 0
Firmware version 1.26
MAC address e8:68:e7:e1:4d:67
Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 21256
WiFi IP address 10.0.0.115
Signal strength -52dBm, channel 0, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok -
@tylersuard said in SOLUTION: Can't connect to Duet Web Control:
3.5.0-beta.4
@tylersuard said in SOLUTION: Can't connect to Duet Web Control:
= WiFi =
Interface state: active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
Firmware version 1.26Your firmware is quite out of date and there is a new branch of wifi firmware that may work better for you. I suggest you update.
https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0-rc.3
You'll need Duet3Firmware_Mini5plus.uf2, and DuetWiFiServer.bin. And you'll need to manually replace the DWC files in the WWW folder with the files from DuetWebControl-SD.zip.
It would also be useful to know if you have the same issues with the 3.4.6 release.
