WiFi module not working on Duet 2 WiFi 1.04c
-
@pjkruger pls post the result of M122
-
M122:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9D6-3SD6K-9UUBN
Used output buffers: 5 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72036 of which 0 recycled
Never used RAM 16584, free system stack 190 words
Tasks: NETWORK(ready,521) HEAT(blocked,366) MAIN(running,419) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:50 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 16548, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 20.1, current 20.8, max 21.0
Supply voltage: min 0.2, current 0.4, max 0.4, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 67293480
Slowest loop: 100.55ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/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 -1 -1, chamberHeaters = -1 -1 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.22ms; 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 starting2
WiFi module is disabled
Failed messages: pending 0, notready 1, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok
M589: (With all the other S, P, I parameters):
Error: M589: Failed to retrieve own SSID data: another SPI transfer is pending
ok
- WiFi -
-
@pjkruger said in WiFi module not working on Duet 2 WiFi 1.04c:
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
I'm not complete sure, but I think you have to install the DuetWiFiServer.bin from the RRF 3.2.2 to get wifi to work
-
Please try sending M997 S1 to initiate the wifi firmware flash. It seems to have not gone through previously.
-
I uploaded via SD card RRF 3.2.2 DuetWifiServer.bin to /sys and sent M997 S1, response as follows:
M997 S1
Trying to connect at 230400 baud: success
Erasing 4096 bytes...
Erasing 196608 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
Disconnected, reconnected, sent the following:
M552 S0
ok
M552
WiFi module is being started
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9D6-3SD6K-9UUBN
Used output buffers: 5 of 24 (10 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72036 of which 0 recycled
Never used RAM 16584, free system stack 192 words
Tasks: NETWORK(ready,521) HEAT(blocked,366) MAIN(running,492) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:44 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 16548, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 16.4, current 18.7, max 19.1
Supply voltage: min 0.3, current 0.5, max 0.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 60541246
Slowest loop: 5.27ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/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 -1 -1, chamberHeaters = -1 -1 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.02ms; 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 starting2
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok
Still no luck.
- WiFi -
-
How bout just sending m552 S1?
-
@pjkruger please try running M997 S1 again. Sometimes the firmware upload fails first time, and unfortunately the ESP flashing mechanism does not provide any error checking. After it reports successful completion, try M552 S0 again. If necessary, power the Duet down and up again.
If after that it still always reports "WiFi module is being started" when you send M552, and it's a genuine Duet, then I will approve a replacement under warranty.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
M552 S1
Turn off the current WiFi mode before selecting a new one
ok
M552 S-1
WiFi module stopped
ok
M552 S1
ok
M552
WiFi module is being started
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9D6-3SD6K-9UUBN
Used output buffers: 2 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72036 of which 0 recycled
Never used RAM 16584, free system stack 192 words
Tasks: NETWORK(ready,519) HEAT(blocked,366) MAIN(running,427) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:01:36 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 16548, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 20.7, current 21.6, max 21.7
Supply voltage: min 0.5, current 0.5, max 0.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 133944405
Slowest loop: 99.34ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/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 -1 -1, chamberHeaters = -1 -1 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.19ms; 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 starting2
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok
No Luck
- WiFi -
-
M997 S1
Trying to connect at 230400 baud: success
Erasing 4096 bytes...
Erasing 196608 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
Power off; on
M552 S0
ok
M552
WiFi module is being started
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-6J9D6-3SD6K-9UUBN
Used output buffers: 4 of 24 (9 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72036 of which 0 recycled
Never used RAM 16584, free system stack 192 words
Tasks: NETWORK(ready,521) HEAT(blocked,366) MAIN(running,524) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:45 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 16548, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 21.2, current 23.6, max 23.9
Supply voltage: min 0.3, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 62597900
Slowest loop: 5.28ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/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 -1 -1, chamberHeaters = -1 -1 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.19ms; 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 starting2
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok
Again seems to be no luck. I can confirm it is a genuine Duet, purchased from Da Vinci Labs in RSA (Graeme). You are most welcome to contact them to verify, they are aware of the situation and pointed me to this forum since they don't provide after-sale service.
- WiFi -
-
@pjkruger Please contact your vendor to initiate a warranty exchange. Include a link to this thread as authorization.
