Updating a Duet2Wifi DuetWifiServer
-
Ok so that's promising. The firmware was updated successfully.
Can you now try the same sequence of commands?
M552
M552 S-1
M552 S0
M552 S1Have you tried adding an SSID with M587 yet? https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m587-add-wifi-host-network-to-remembered-list-or-list-remembered-networks
Not sure why your firmware folder didn't work before. I think you have something wrong with your SD card folder structure.
See here for details on what folders are required to be present on the SD card: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card
-
Unfortonatly something still went wrong, the error messages do not give me a clue to what it might be.
M552
WiFi module is disabled
ok
M552 S-1
ok
M552 S0
ok
WiFi module started
M552 S1
ok
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
M587 S"MyWifi" P"MyPW"
Error: M587: Failed to add SSID to remembered list: SPI timeout
ok
Error: failed to retrieve WiFi status message: SPI timeout
WiFi module is idle
Error: failed to change WiFi mode: SPI timeout"Error: WiFi module reported: no known networks found
WiFi module is idle"This message comes now quite often. Before today i never had this, but i read that it is not unusual.
I even did the reformating the 4 GB SD Card.
-
Well the module is responding now.
Can you send M122 again and share the results again?
Please send
M588 S"*"to clear out any saved networks and try adding again. -
Hello,
thats good to hear, that it is moving into the right direction.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J9FL-3S86M-KJSBX
Used output buffers: 1 of 26 (11 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 74792 of which 20 recycled
Never used RAM 13432, free system stack 193 words
Tasks: NETWORK(ready,8.6%,335) HEAT(notifyWait,0.0%,353) Move(notifyWait,0.0%,363) MAIN(running,91.3%,458) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:01:29 ago, cause: reset button or watchdog
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 32.6, current 32.8, max 33.7
Supply voltage: min 1.3, current 1.4, max 1.4, 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
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 3638083520
Slowest loop: 2.24ms; 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 0.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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: 99.91ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 3
Socket states: 0 0 0 0 0 0 0 0
okFor the other command:
M588 S""
Error: M588: Failed to reset the WiFi module to factory settings: WiFi module is disabled
ok
M552
WiFi module is disabled
ok
M552 S-1
ok
M552 S0
ok
WiFi module started
M588 S""
oki´m waiting for your response before trying to safe an other network again. Not that I undo something by accident
-
Can you send M552 S1 and then send M122?
@Milan-R said in Updating a Duet2Wifi DuetWifiServer:
M588 S""
There needs to be an
*between the quotes. -
weird it was in Yat but somehow got lost.
Well but i tried:
M588 S"*"
M552 S1
M122M588 S""
ok
M552 S1
ok
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J9FL-3S86M-KJSBX
Used output buffers: 1 of 26 (11 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 74792 of which 20 recycled
Never used RAM 13432, free system stack 193 words
Tasks: NETWORK(ready,7.6%,335) HEAT(notifyWait,0.0%,349) Move(notifyWait,0.0%,363) MAIN(running,92.4%,458) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:51:52 ago, cause: reset button or watchdog
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 32.5, current 36.3, max 36.5
Supply voltage: min 1.3, current 1.7, max 1.8, 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
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 99.50ms; 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 2.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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.35ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is changingMode
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
ok
Error: failed to retrieve WiFi status message: SPI timeout
WiFi module is idle
Error: failed to change WiFi mode: SPI timeout
M588 S""
Error: M588: Failed to reset the WiFi module to factory settings: WiFi module is disabled
ok -
@Milan-R said in Updating a Duet2Wifi DuetWifiServer:
Error: WiFi module reported: no known networks found
WiFi module is idleOk, so now let's try adding your SSID again.
-
i was confinced that it would work this time
I tried the steps: "Set WiFi to idle mode","Configure network SSID and password","Enable networking"
Error: WiFi module reported: no known networks found<LF>WiFi module is idle(...)
M552 S-1
WiFi module stopped<LF>ok<LF>
M552
WiFi module is disabled<LF>ok<LF>
M552 S0
ok<LF>WiFi module started<LF>
M552
WiFi module is idle<LF>ok<LF>
M587 S"OneDoesNotSimplyConnectToWifi2" P"BLANKED"
ok<LF>
M587
Remembered networks:<LF>OneDoesNotSimplyConnectToWifi2 IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0<LF>ok<LF>
M552 S1
ok<LF>Error: WiFi module reported: no known networks found<LF>WiFi module is idle(...)<LF>Error: WiFi module reported: no known networks f[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]I ran a M122 too:
Under the headline wifi something changed:
Network state is active
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address a0:20:a6:19:22:84
WiFi Vcc 3.29, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 28576
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
When and where did you purchase your Duet wifi?
-
i got it on ebay (kleinanzeigen) so not the online shop.
But as far as i could tell it is an original. I googled a little to dopple check.
But i´ll ask for the Bill so i can see when it was bought
-
@Milan-R said in Updating a Duet2Wifi DuetWifiServer:
M552
WiFi module is idle<LF>ok<LF>
M587 S"OneDoesNotSimplyConnectToWifi2" P"BLANKED"
ok<LF>
M587
Remembered networks:<LF>OneDoesNotSimplyConnectToWifi2 IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0<LF>ok<LF>
M552 S1
ok<LF>Error: WiFi module reported: no known networks foundCan you confirm that the wifi network you are using is 2.4ghz? The Duet cannot connect to 5ghz networks.
@Milan-R said in Updating a Duet2Wifi DuetWifiServer:
i got it on ebay
Unfortunately there would be no warranty in this case.
-
Hello,
wow ok that was my bad, but also i have to talk to my roommates
The Wifi name is slightly different between the 2,4 ghz and the 5 hgz. Just the F in wifi is caps or not.
Now i could connect.
So sorry to go to all this writing because of my supidity...
But now it seems to work THANKS once again.
i´m so embarresed
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
-
@Milan-R I'm glad you got it working. No need to be embarrassed, we all make this sort of mistake occasionally. Have fun!
