Duet 2 WiFi not working

Jesterize

Newish. From December.

Phaedrux

Was it ever working?

What firmware version was on before?

Does the wifi firmware version install?

Can you provide the results of a M122?

Jesterize

No it was never working. Just got it installed last night.
Not certain. Jumped to 3.1.1. Then, reverted back to 2.05.1
Again, not certain.
As soon as I get home, I will post the results of an M122

Jesterize

M122 results

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SD-6JKD4-3SD6J-KUMHF
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 92704 of which 0 recycled
Exception stack ram used: 256
Never used ram: 12400
Tasks: NETWORK(ready,1876) HEAT(blocked,1232) MAIN(running,3864) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:01:28 ago, cause: power up
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11548 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 30.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 29.4, current 29.7, max 29.8
Supply voltage: min 0.9, current 0.9, max 1.0, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 132384348
Slowest loop: 99.43ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 0 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.15ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

WiFi -
Network state is starting
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok

Jesterize

That was after running a M552 S0 command

A Former User

@Jesterize said in Duet 2 WiFi not working:

Network state is starting
WiFi module is disabled

put a new DuetWiFiServer.bin in /sys on the sd card and try running M997 S1 (or say yes to let DWC upgrade, if uploaded through DWC)

connect a usb* cable and connect to the serial console if you cannot see the update status in the DWC console.

*) please note https://duet3d.dozuki.com/Wiki/USB_ground_loops

Jesterize

Thanks bearer. Did that, went through the upload process, restarted it, ran M552 S0 and still getting "WiFi module is being started". Running a M122 still says WiFi module is disabled.

A Former User

just to confirm; it went through 5%, 10% ... 100% and said it was done?

Jesterize

@bearer Yup

Jesterize

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?

A Former User

@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 S1 and M997 S1

should 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 0

edit:
if WiFi:ets Jan8 2013,rst cause:2, boot mode:(3,6) is different then most likely wifi or processor has failed

if WiFi: csum 0x2d and/or WiFi: v3fff168c is different, then most likely wrong firmware version (i.e. not v1.23) or corrupt binary

if it hangs after WiFi: ~ld then i'd wager something is broke, probably the wifi module, but could also be the processor.

Jesterize

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

Jesterize

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

A Former User

Nothing after ok?

try M552 S-1 followed byM552 S0 it should give you the output from the ESP8266 bootloader at least

Jesterize

It looks like it is hanging on the ~ld. something is broken

A Former User

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.

Phaedrux

@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

Jesterize

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.

A Former User

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

Phaedrux

Lets see what DC says before you take the torch to it.