Was working, now can't connect to WiFi
-
Give me a minute and I'll try it connected to USB.
I can't do connected to WiFi since it will no longer connect.
-
@phaedruxm552 s1
m552
m552
WiFi module is disabled
ok
m552 s1
ok
WiFi module started
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3RC2 (2021-05-11 14:55:40) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: D79UH-2096U-D65J0-40KMU-0G03Z-R76Y7
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 102476
Dynamic ram: 104660 of which 420 recycled
Never used RAM 36148, free system stack 145 words
Tasks: NETWORK(ready,7.1%,520) HEAT(delaying,0.0%,390) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,341) TMC(notifyWait,0.0%,124) MAIN(running,91.3%,607) IDLE(ready,0.7%,29) AIN(delaying,0.8%,274), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:18 ago, cause: power up
Last software reset at 2021-12-31 14:04, reason: User, GCodes spinning, available RAM 35076, 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
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU revision 3, ADC conversions started 18852, completed 18852, timed out 0, errs 0
Step timer max interval 732
MCU temperature: min 16.0, current 19.8, max 19.8
Supply voltage: min 0.1, current 0.7, max 0.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 41054978
Slowest loop: 10.13ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, 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, 0], 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 = -1 -1, chamberHeaters = -1 -1
=== 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 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
Code queue is empty.
=== CAN ===
Messages queued 94, send timeouts 93, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
Last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 0.16ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8- WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
ok
- WiFi -
-
and to be clear, I've repeatedly used M552 with the S and P parameters for the SSID and password, and they worked fine until they didn't
I've also tried using M588 to delete the network and attempt to replace the parameters again with M587 (as well as M552)
If it means anything I think the last thing I tried to do before it quit working was use the M552 with the P, S, and I parameters to fix an IP address so I didn't have to sniff the network every time the router changed it.
-
@flyeyes said in Was working, now can't connect to WiFi:
Duet 3 Mini 5+ version 3.3RC2
Can you use this procedure to update your firmware?
https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Firmware#Section_Updating_firmware_via_USB
If that doesn't help, send M997 S1 to reflash the wifi server firmware as well. You may need to first manually place the wifi server bin file onto the SD card in a new folder called
firmwareon the root of the SD card if it doesn't already exist as that is where it will be looking in 3.3https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/DuetWiFiServer.bin
-
I've tried that now 3x. Can connect through serial as before, but no WiFi.
Removed MicroSD card, placed in computer and manually replaced the DuetWiFiServer.bin file 3x (twice on a Mac, once on a windows machine for grins) but M997 returns an error:
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
The file is in the sys directory, where I found it originally.
Quite frustrated, was chasing down the final hardware details and now can't run the printer.
I do have a Pi 4 available, should I just try that and give up on the Duet WiFi?
-
my bad, just realized it was in the wrong directory. moved it and now updated, but same problem: no WiFi connectivity
It was working fine until it wasn't, network is fine.
-
Ok so what does M122 return now?
How bout these commands
M552
M552 S-1
M552 S0
M552 S1
M588 S"*"
M587 -
m587
Remembered networks: none
ok
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: D79UH-2096U-D65J0-40KMU-0G03Z-R76Y7
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 104600 of which 464 recycled
Never used RAM 35916, free system stack 145 words
Tasks: NETWORK(ready,7.3%,520) HEAT(delaying,0.0%,420) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.0%,124) MAIN(running,91.4%,629) IDLE(ready,0.4%,29) AIN(delaying,0.8%,274), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:30 ago, cause: power up
Last software reset at 2021-12-31 14:04, reason: User, GCodes spinning, available RAM 35076, 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 30540, completed 30540, timed out 0, errs 0
Step timer max interval 731
MCU temperature: min 16.9, current 20.4, max 20.6
Supply voltage: min 0.2, current 0.7, max 0.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 66198261
Slowest loop: 9.62ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, 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, 0], 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 = -1 -1, chamberHeaters = -1 -1
=== 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 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
Code queue is empty.
=== CAN ===
Messages queued 153, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 153/0/0
Tx timeouts 0,0,152,0,0,0 last cancelled message type 30 dest 127=== Network ===
Slowest loop: 0.16ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8- WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
ok
- WiFi -
-
tried to send more, but "flagged as spam."
587 returns no remembered networks. Have tried reentering SSID and password probably 30+ times
-
@flyeyes said in Was working, now can't connect to WiFi:
tried to send more, but "flagged as spam."
Try again.
What error do you get when you try to enter the SSID?
What do these produce?
M552
M552 S-1
M552 S0
M552 S1
M588 S"*" -
All of those are in the above messages, but to recap:
M552 returns "no remembered networks"
M552 S1 returns many, many lines of no network available
M552 S0 works as expected
M588 S"*" erased all of the networks as expected, but I cannot add the SSID and password back. Have tried dozens of times (literally)
-
I did get it to work briefly (just now) while connected to serial (I've been doing the exact same thing dozens of times for days without success) but its still wonky. the WiFi will hook up while I'm connected to serial via USB, but I lose it and it won't connect if I unplug the USB and then power the board up normally.
I know documentation says to not use USB and an external power supply at the same time, but I did try briefly to get the WiFi going on USB, turn on the printer, and unplug WiFi.
This worked until I rebooted the board, and no connectivity after that. Got it going again with USB, but can't power cycle without losing connectivity
-
So does it have a saved SSID now or not?
Does your config.g have a M552 S1?
The last test would be to see if it will run in standalone WIFI access point mode.
-
Yes, it seems to be working now. I have no idea what I did differently, which bothers me a bit because it worked fine when I first configured it, then after a week quit working, and now it’s working fine as far as I can tell.
I haven’t done anything differently, but I will watch it for now. If it quits again I’m just going to plug it into the pi or start over with a different board.
-
Well if we can identify what's wrong or if there is something wrong and it's under warranty you can get it replaced.
-
I'm having this same problem.
I can save and forget networks as long as the wifi module has been set to active with m552 S0, but not with S-1 or S1 modifiers. When I try to check the status of the wifi module with M552 by itself, I consistently get "wifi module is changing modes" until there's an SPI timeout message like the one at the bottom of the excerpt below.
I've successfully reinstalled wifiserver.bin twice (i'm doing this over USB with pronterface and a 24vPSU for the board), but this has yielded no changes in anything. If I just let it sit, it'll eventually give me a bunch of these in a row:
WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed WiFi module is idle Error retrieving WiFi status message: SPI timeout Error retrieving WiFi status message: SPI timeout WiFi module is idle Failed to change WiFi mode: SPI timeoutOnce the SPI timeout message(s) come, m552 reports that the wifi module is disabled.
I know it's not a poor signal issue, as I've tried within a foot or two of the router.
Here's my m122 if it helps:
>>> M122 SENDING:M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: ZJ21Z-NV9RL-D65J0-40KMN-L3X2Z-HFGNV Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 102724 Dynamic ram: 106504 of which 0 recycled Never used RAM 34476, free system stack 157 words Tasks: NETWORK(ready,7.6%,328) HEAT(notifyWait,0.0%,364) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,1.1%,115) MAIN(running,90.4%,426) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 00:14:30 ago, cause: software Last software reset at 2022-01-09 18:47, reason: StuckInSpinLoop, Display spinning, available RAM 41956, slot 1 Software reset code 0x408f HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043380f BFAR 0xe000ed38 SP 0x20002a4c Task IDLE Freestk 43 ok Stack: 00087e75 000888a8 61000000 a5a5a5a5 00087e75 a5a5a5a5 a5a5a5a5 2000390c 0001676d 20019104 2002ec9c 20002a68 200190fc 00000004 2001e0dc 2001e0dc 20002a68 2001e0d4 00000001 20002ac4 4e49414d 00000000 00000000 00000001 00000001 17c2fb96 00000000 Error status: 0x04 Error status: 0x04 Aux0 errors 0,0,1 MCU revision 3, ADC conversions started 870849, completed 870849, timed out 0, errs 0 Step timer max interval 597 MCU temperature: min 26.1, current 33.1, max 33.3 Supply voltage: min 23.9, current 23.9, max 24.0, 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 Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0 Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0 Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0 Date/time: 1970-01-01 00:00:00 Cache data hit count 1789008195 Slowest loop: 99.69ms; fastest: 0.12ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, 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, 0], 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 === 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 idle in state(s) 0 USB is ready with "M122" in state(s) 0 Aux is assembling a command 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. === CAN === Messages queued 7836, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 4354/0/0 Tx timeouts 0,0,4353,0,0,3481 last cancelled message type 4514 dest 127 === Network === Slowest loop: 200.13ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 0 of 8 - WiFi - Network state is disabled WiFi module is disabled Failed messages: pending 0, notready 0, noresp 2 Socket states: 0 0 0 0 0 0 0 0 -
@terbospaghetti said in Was working, now can't connect to WiFi:
I can save and forget networks as long as the wifi module has been set to active with m552 S0, but not with S-1 or S1 modifiers.
That's normal.
The M587 command will fail if the WiFi module has not yet been taken out of reset. So if the WiFi module has not been started, send M552 S0 to put it in idle mode first.
https://duet3d.dozuki.com/Wiki/M587@terbospaghetti said in Was working, now can't connect to WiFi:
I consistently get "wifi module is changing modes"
Not normal.
@terbospaghetti said in Was working, now can't connect to WiFi:
I've successfully reinstalled wifiserver.bin twice
Have you been able to verify that the correct version is installed with a M122 when the wifi has connected?
-
@phaedrux said in Was working, now can't connect to WiFi:
Have you been able to verify that the correct version is installed with a M122 when the wifi has connected?
Not sure where I would look or what it should say, but the process was successful according to the console in pronterface
-
@terbospaghetti said in Was working, now can't connect to WiFi:
Not sure where I would look or what it should say,
In the M122 report at the end there is a section for wifi
- WiFi - Network state is disabled WiFi module is disabled Failed messages: pending 0, notready 0, noresp 2 Socket states: 0 0 0 0 0 0 0 0When it's active it would say what wifi server version it's running.
-
@flyeyes @terbospaghetti
This kind of thing happened to me and part of my resolution dance, along with a big chain of FW upgrades to current, was in discovering that my modem/router had smashed the 2.4ghz and 5ghz networks into one automode SSID. And the Duet doesn't like 5ghz I think. I had to dig into my router config and force the two networks to separate SSIDs, after which the Duet was much better about seeing the 2.4ghz network even after a restart or a few days switched off. Not perfect, but much better.Maybe looking into that could help.
