Updating a Duet2Wifi DuetWifiServer
-
Hello @Phaedrux
i just tested it again to be sure it is the following error:
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found<LF>ok<LF>The .bin File is on the SD Card in a Folder "Firmware" that i created.
Is it Possible, that the folder should be created while the instalation of the newer Firmware?
And i read somewhere to rename or not rename the file. Do i have to give it a diverent name? But the Errorcode says it is searich for a file without the Version number.
I was wondering, if there are other files needed on the SD card.
-
Can you send M122 in the terminal and copy and paste the results here?
Can you send
M20 P"0:/"as well? This should list the contents of the root of the SD card. Then sendM20 P"0:/firmware/" -
Hello,
First the diagnose command:
M122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later<LF>Board ID: 08DDM-9FAM2-LW4S4-6J9FL-3S86M-KJSBX<LF>Used output buffers: 1 of 26 (1 max)<LF>=== RTOS ===<LF>Static ram: 23836<LF>Dynamic ram: 73384 of which 0 recycled<LF>Never used RAM 14860, free system stack 193 words<LF>Tasks: NETWORK(ready,7.2%,517) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,88.8%,619) IDLE(ready,3.9%,30), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:00:20 ago, cause: reset button or watchdog<LF>Last software reset details not available<LF>Error status: 0x00<LF>Step timer max interval 0<LF>MCU temperature: min 28.1, current 28.9, max 29.0<LF>Supply voltage: min 1.3, current 1.4, max 1.4, under voltage events: 0, over voltage events: 0, power good: no<LF>Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF>Events: 0 queued, 0 completed<LF>Driver 0: ok, SG min n/a<LF>Driver 1: ok, SG min n/a<LF>Driv[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.]M20 P"0:/"
Begin file list<LF>System Volume Information<LF>.dropbox.device<LF>firmware<LF>sys<LF>End file list<LF>ok<LF>M20 P"0:/firmware/"
Begin file list<LF>DuetWiFiServer.bin<LF>End file list<LF>ok<LF>So it seems to find the .bin file. hmm.
-
I noticed there was a warning, so i tried to increas the number of characters.
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later<LF>Board ID: 08DDM-9FAM2-LW4S4-6J9FL-3S86M-KJSBX<LF>Used output buffers: 1 of 26 (11 max)<LF>=== RTOS ===<LF>Static ram: 23836<LF>Dynamic ram: 73384 of which 0 recycled<LF>Never used RAM 14860, free system stack 193 words<LF>Tasks: NETWORK(ready,7.5%,517) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,92.5%,471) IDLE(ready,0.0%,30), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:07:54 ago, cause: reset button or watchdog<LF>Last software reset details not available<LF>Error status: 0x00<LF>Step timer max interval 0<LF>MCU temperature: min 28.5, current 29.4, max 29.8<LF>Supply voltage: min 1.3, current 1.3, max 1.4, under voltage events: 0, over voltage events: 0, power good: no<LF>Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF>Events: 0 queued, 0 completed<LF>Driver 0: ok, SG min n/a<LF>Driver 1: ok, SG min n/a<LF>Driver 2: ok, SG min n/a<LF>Driver 3: ok, SG min n/a<LF>Driver 4: ok, SG min n/a<LF>Driver 5: <LF>Driver 6: <LF>Driver 7: <LF>Driver 8: <LF>Driver 9: <LF>Driver 10: <LF>Driver 11: <LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 4294967295<LF>Slowest loop: 2.52ms; fastest: 0.14ms<LF>I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest read time 0.8ms, write time 0.0ms, max retries 0<LF>=== Move ===<LF>DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== AuxDDARing ===<LF>Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0<LF>=== GCodes ===<LF>Segments left: 0<LF>Movement lock held by null<LF>HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s) 0<LF>USB is ready with "M122" in state(s) 0<LF>Aux is idle in state(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>LCD is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty<LF>=== Network ===<LF>Slowest loop: 0.20ms; fastest: 0.00ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)<LF>HTTP sessions: 0 of 8<LF>= WiFi =<LF>Network state is disabled<LF>WiFi module is disabled<LF>Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>
-
@Milan-R said in Updating a Duet2Wifi DuetWifiServer:
[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.]
@Milan-R said in Updating a Duet2Wifi DuetWifiServer:
I noticed there was a warning, so i tried to increas the number of characters.
You need to change the line endings.
We need to see the end of the M122 report because that's where it reports the wifi module info.
-
I hope it is everything this time. But i can read something about Wifi at the end so i hope thats it.
M122<CR>
=== 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 (1 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 73384 of which 0 recycled
Never used RAM 14860, free system stack 184 words
Tasks: NETWORK(ready,7.5%,517) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,91.9%,620) IDLE(ready,0.6%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:13 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 0
MCU temperature: min 26.5, current 31.3, max 31.5
Supply voltage: min 0.5, 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 4294967295
Slowest loop: 2.22ms; 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 -1 -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: 0.18ms; 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 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
ok
-
Can you extract the full contents of this zip file into your firmware folder?
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip
Then try sending these commands and report back what they return.
M552
M552 S-1
M552 S0
M552 S1
M997 S1 -
M552
WiFi module is disabled
okM552 S-1
okM552 S0
okM552 S1
Turn off the current WiFi mode before selecting a new one
okM997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok
-
"WiFi module started
Error: failed to initialise WiFi module: bad reply format version"This Message Came after some secounds too.
Complete answer to the M997 S1:
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok
WiFi module started
Error: failed to initialise WiFi module: bad reply format version -
Do you have a new SD card to test with? Formatted as FAT32.
-
Hello @Phaedrux ,
The SD Card i used was FAT32 already, but i have a 32GB FAT 32 that i just tested, unfortunatly the result of the:
M552
M552 S-1
M552 S0
M552 S1
M997 S1Commands were the same:
M552
WiFi module is disabled
ok
M552 S-1
ok
M552 S0
ok
M552 S1
Turn off the current WiFi mode before selecting a new one
ok
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok
WiFi module started
Error: failed to initialise WiFi module: bad reply format version
-
Do you still have the wifi server bin file in the sys folder as well?
Try
M997 S1 P"0:/sys/DuetWiFiServer.bin" -
after the SD Card Swap there was only the files from the Zip file in the firmware folder.
But now i copied the firmware folder and called it sys.
I tried the command in YAT:
M997 S1 P"0:/sys/DuetWiFiServer.bin"
<LF>
Trying to connect at 230400 baud: success<LF>Erasing 8192 bytes...<LF>Erasing 269216 bytes...<LF>Uploading file...<LF>5% complete<LF>10% complete<LF>15% complete<LF>20% complete<LF>25% complete<LF>30% complete<LF>35% complete<LF>40% complete<LF>45% complete<LF>50% complete<LF>55% complete<LF>60% complete<LF>65% complete<LF>70% complete<LF>75% complete<LF>80% complete<LF>85% complete<LF>90% complete<LF>95% complete<LF>Upload successful<LF>ok<LF> -
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.
