DWC is requiring multiple restarts to connect
-
I'm not sure if this is the appropriate category, or not, I can start a new thread elsewhere if its not.
I have a fairly new Duet 3 Mini 5+ (about a month old), and when I reset or power off the board I have to reboot it 3-4 times before I can get access to DWC. The board shows up as connected to my network, but going to the IP address returns an "unable to connect" message.
I am running RepRapFirmware 3.2.2 (2021-02-11), and Duet Wifi Server 1.25beta0 (if there is an updated wifi server ver I have not been able to find it easily)
Once things do get connected, the web interface works great, as does the printer generally.
Any ideas where to begin troubleshooting this? I don't even know if the issue is software, hardware, or my network.
-
The next time it's doing this would you be able to connect via USB terminal and send M122 and see what it says about the SD card? Also send M21 to see if it can reach the SD card.
-
Sorry for the delay, here is the output of M122:
M122<CR><LF> === Diagnostics ===<LF> RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (standalone mode)<LF> Board ID: 676VY-Y196U-D65J0-40KMJ-NF03Z-ZZSK0<LF> Used output buffers: 1 of 40 (13 max)<LF> === RTOS ===<LF> Static ram: 98732<LF> Dynamic ram: 107756 of which 40 recycled<LF> Never used RAM 38688, free system stack 148 words<LF> Tasks: NETWORK(ready,166) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,362) TMC(blocked,106) MAIN(running,440) IDLE(ready,20) AIN(blocked,264)<LF> Owned mutexes: WiFi(NETWORK) USB(MAIN)<LF> === Platform ===<LF> Last reset 19:50:32 ago, cause: power up<LF> Last software reset at 2021-04-22 12:58, reason: User, GCodes spinning, available RAM 38444, slot 2<LF> Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF> Error status: 0x00<LF> Aux0 errors 0,0,0<LF> Aux1 errors 0,0,0<LF> Supply voltage: min 0.0, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes<LF> Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 46488, writes 9, timeouts 0, DMA errors 0<LF> Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 46488, writes 9, timeouts 0, DMA errors 0<LF> Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 46488, writes 9, timeouts 0, DMA errors 0<LF> Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 46486, writes 9, timeouts 1, DMA errors 0, failedOp 0x6f<LF> Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 46488, writes 9, timeouts 0, DMA errors 0<LF> Driver 5: position 0, assumed not present<LF> Driver 6: position 0, assumed not present<LF> Date/time: 2021-04-23 14:48:24<LF> Cache data hit count 4294967295<LF> Slowest loop: 7.49ms; fastest: 0.12ms<LF> === Storage ===<LF> Free file entries: 10<LF> SD card 0 detected, interface speed: 22.5MBytes/sec<LF> SD card longest read time 3.9ms, write time 0.0ms, max retries 0<LF> === Move ===<LF> DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF> === MainDDARing ===<LF> Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF> === AuxDDARing ===<LF> Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF> === Heat ===<LF> Bed heaters = 0 -1, chamberHeaters = -1 -1<LF> === GCodes ===<LF> Segments left: 0<LF> Movement lock held by null<LF> HTTP is idle in state(s) 0<LF> Telnet is idle in state(s) 0<LF> File is idle in state(s) 0<LF> USB is ready with "M122" in state(s) 0<LF> Aux is idle in state(s) 0<LF> Trigger is idle in state(s) 0<LF> Queue is idle in state(s) 0<LF> LCD is idle in state(s) 0<LF> SBC is idle in state(s) 0<LF> Daemon is idle in state(s) 0<LF> Aux2 is idle in state(s) 0<LF> Autopause is idle in state(s) 0<LF> Code queue is empty.<LF> === Network ===<LF> Slowest loop: 85.01ms; fastest: 0.00ms<LF> Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions<LF> HTTP sessions: 0 of 8<LF> - WiFi -<LF> Network state is active<LF> WiFi module is connected to access point <LF> Failed messages: pending 0, notready 0, noresp 0<LF> WiFi firmware version 1.25beta0<LF> WiFi MAC address f4:cf:a2:6f:bd:8f<LF> WiFi Vcc 3.39, reset reason Power up<LF> WiFi flash size 2097152, free heap 24568<LF> WiFi IP address 255.255.255.255<LF> WiFi signal strength 31dBm, mode 802.11n, reconnections 0, sleep mode modem<LF> Clock register 00002002<LF> Socket states: 0 0 0 0 0 0 0 0<LF> === CAN ===<LF> Messages queued 642890, send timeouts 642888, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16<LF> ok<LF>And M21:
M21<LF> T0:22.3 /0.0 B:22.6 /0.0<LF> SDHC card mounted in slot 0, capacity 7.95Gb<LF> ok<LF>It does not appear that there is any error with the SD card
-
Just to be clear those results are from when you were having trouble loading DWC?
-
@phaedrux That is correct, those were done while the board would not connect to wifi. Down near the bottom you can see the the wifi IP address is 255.255.255.255.
Here is the output once it does connect:
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: 676VY-Y196U-D65J0-40KMJ-NF03Z-ZZSK0 Used output buffers: 3 of 40 (40 max) === RTOS === Static ram: 98732 Dynamic ram: 107964 of which 76 recycled Never used RAM 38444, free system stack 124 words Tasks: NETWORK(ready,192) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,438) IDLE(ready,20) AIN(blocked,264) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 02:00:18 ago, cause: power up Last software reset at 2021-04-22 12:58, reason: User, GCodes spinning, available RAM 38444, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Aux1 errors 0,0,0 Supply voltage: min 11.5, current 11.8, max 12.5, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 19800, standstill, SG min/max 0/18, read errors 0, write errors 0, ifcnt 12, reads 42939, writes 3, timeouts 0, DMA errors 0 Driver 1: position 12100, standstill, SG min/max 0/20, read errors 0, write errors 0, ifcnt 12, reads 42939, writes 3, timeouts 0, DMA errors 0 Driver 2: position 4020, standstill, SG min/max 0/56, read errors 0, write errors 0, ifcnt 18, reads 42933, writes 9, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 42942, writes 0, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 42942, writes 0, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-04-23 17:05:47 Cache data hit count 4294967295 Slowest loop: 16.03ms; fastest: 0.12ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.9ms, write time 4.6ms, max retries 0 === Move === DMs created 83, maxWait 5548851ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 8], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.3 Heater 1 is on, I-accum = 0.7 === 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 doing "M190 S65" 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 Code queue is empty. === Network === Slowest loop: 200.93ms; fastest: 0.08ms Responder states: HTTP(0) 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.25beta0 WiFi MAC address f4:cf:a2:6f:bd:8f WiFi Vcc 3.39, reset reason Power up WiFi flash size 2097152, free heap 21504 WiFi IP address 192.168.30.27 WiFi signal strength -41dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages queued 64640, send timeouts 64639, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16It doesn't make any sense, all I do is reboot another two times, and it just connects no problem.
-
@patrickwjoyce said in DWC is requiring multiple restarts to connect:
WiFi firmware version 1.25beta0
When you are connected can you please try uploading this zip file to the system tab in DWC? This should reflash the firmwares. Check M122 again after to see if the wifi firmware is 1.25 without the beta0.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
-
I had a simmilar behavior which seemed to be fixed by making sure to include the SSID within the M552 command.
-
@phaedrux The non-beta version of the wifi server appears to have solved the problem of requiring multiple reboots to connect to wifi. Thank you very much.
I will note that I spent a good amount of time, last month, searching for a non-beta wifi server firmware, but had no success finding it. I am fairly familar with Github, so I don't know why it was such a challenge to find that particular item. What is the best way to find specific wifi server updates?
-
@pixelpieper said in DWC is requiring multiple restarts to connect:
I had a simmilar behavior which seemed to be fixed by making sure to include the SSID within the M552 command.
I do have the SSID entered via the M552 command, but oddly enough, only one of my SSIDs would actually connect properly. Over the course of my trouble shooting I tried my 3 different SSIDs but the only one that would connect was my super isolated IOT subnet. I'm wondering if the new wifi server version might fix that issue as well.