Duet 2 WiFi not working
-
just to confirm; it went through 5%, 10% ... 100% and said it was done?
-
@bearer Yup
-
Funny thing is that if I run a M587 command, I get this: M587: Failed to retrieve network list.
Why would it have trouble retrieving a list?
-
@Jesterize said in Duet 2 WiFi not working:
Why would it have trouble retrieving a list?
either the (wifi) firmware is corrupted, or something has failed.
you might be able to get some answers by enabling wifi debug and issuing the firmware update again (will only work with serial console)
M111 P14 S1andM997 S1should look something like
Debugging enabled for modules: WiFi(14) Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) LinuxInterface(16) Trying to connect at 230400 baud:success Erasing 4096 bytes... Erasing 212992 bytes... Uploading file... 5% complete 10% complete 15% complete 20% complete 25% complete 30% complete 35% complete 40% complete 45% complete 50% complete 55% complete 60% complete 65% complete 70% complete 75% complete 80% complete 85% complete 90% complete 95% complete Upload successful WiFi: WiFi:ets Jan8 2013,rst cause:2, boot mode:(3,6) WiFi: WiFi: load 0x4010f000, len 1384, room 16 WiFi: tail 8 WiFi: chksum 0x2d ok WiFi: csum 0x2d WiFi: v3fff168c WiFi: ~ld WiFi module started WiFi: mode : sta(84:f3:eb:42:b0:83) WiFi: add if0 WiFi: wifi evt: 8 WiFi: scandone WiFi: ../src/SocketServer.cpp(353): found network xxxxxxxxxxx WiFi: ../src/SocketServer.cpp(353): found network xxxxxxxxxxx WiFi: ../src/SocketServer.cpp(353): found network xxxxxxxxxxx WiFi: ../src/SocketServer.cpp(353): found network xxxxxxxxxxx WiFi: sleep enable,type: 2 WiFi: wifi evt: 2 WiFi: scandone WiFi: state: 0 -> 2 (b0) WiFi: state: 2 -> 3 (0) WiFi: state: 3 -> 5 (10) WiFi: add 0 WiFi: aid 10 WiFi: cnt WiFi: WiFi: connected with xxxxxxxxxxx, channel 13 WiFi: dhcp client start... WiFi: wifi evt: 0 WiFi: ip:10.10.0.196,mask:255.255.255.0,gw:10.10.0.3 WiFi module is connected to access point xxxxxxxxxxx, IP address 10.10.0.196 WiFi: wifi evt: 3 WiFi: pm open,type:2 0edit:
ifWiFi:ets Jan8 2013,rst cause:2, boot mode:(3,6)is different then most likely wifi or processor has failedif
WiFi: csum 0x2dand/orWiFi: v3fff168cis different, then most likely wrong firmware version (i.e. not v1.23) or corrupt binaryif it hangs after
WiFi: ~ldthen i'd wager something is broke, probably the wifi module, but could also be the processor. -
Did that and this is what I got:
M111 P14 S1
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) LinuxInterface(16)
M997 S1
Trying to connect at 230400 baud: success
Erasing 4096 bytes...
Erasing 212992 bytes...
Uploading file...
5% complete
10% complete
15% complete
20% complete
25% complete
30% complete
35% complete
40% complete
45% complete
50% complete
55% complete
60% complete
65% complete
70% complete
75% complete
80% complete
85% complete
90% complete
95% complete
Upload successful
ok -
Missed the M552 S0. Got this:
M552 S0
WiFi:
WiFi: ets Jan 8 2013,rst cause:2, boot mode:(3,7)
WiFi:
WiFi: load 0x4010f000, len 1384, room 16
WiFi: tail 8
WiFi: chksum 0x2d
WiFi: csum 0x2d
WiFi: v3fff168c
WiFi: ~ld
ok -
Nothing after
ok?try
M552 S-1followed byM552 S0it should give you the output from the ESP8266 bootloader at least -
It looks like it is hanging on the ~ld.
something is broken -
Ah, I might have done M552 S0 before M997 come to think of it.
Anyways, it shows the ESP is trying to boot into mode 3,7 instead of 3,6 - I don't recall the specifics around that issue but smarter people than me should have all the necessary information now at least.
-
@bearer said in Duet 2 WiFi not working:
but smarter people than me
I don't see anybody like that around at the moment. Will have to wait for DC to have a say.
Only things I can think of to try in the meantime:
-
redownload the wifi server bin file, check that the downloaded size matches, rename it and try flashing again
-
Use these commands to try and clear the saved list of SSIDs and then try starting it again.
M552 S0 ; Disable network module G4 S5 ; wait 5 seconds M588 S"*" ; Clear all saved wifi networks -
-
After doing all that, I get this "Error: M588: Failed to reset the WiFi module to factory settings"
Thanks for trying guys! Hopefully, DC has some good news. Fingers crossed.
-
while we wait for dc42 to take a look
@Jesterize said in Duet 2 WiFi not working:
After doing all that, I get this "Error: M588: Failed to reset the WiFi module to factory settings"
yeah, that was kinda expected as it seems the wifi module isn't starting its firmware properly.
descember puts you just shy of the 6 months warranty doesn't it? if you've got some hot air soldering tools, or people with tools nearby its quite doable to replace the wifi module, or depending on your location https://forum.duet3d.com/topic/13875/community-repairs?_=1593191305483
-
Lets see what DC says before you take the torch to it.
-
Alright <sadly putting torch away>.
-
I'm sorry, we see this type of problem reported occasionally, and we don't know the cause. The only solution we know of is to replace the WiFi module. Please ask your supplier to replace your Duet under warranty.
