Updating from 3.0 to 3.3 gone wrong
-
Been setting up a new board. I was able to update the original 2.05.1 the board came with to 3.0, but when I attempted to update the 3.0 to 3.3 something went wrong and the update never seemed to complete. Never got an update successful message, but an M115 command shows that it's running 3.3 now, but I've been unable to connect and start the DWC like before. Wifi module is lit and showing connection. I've tried going thru the set up process again ,but get unsolvable error messages. diagnostics show wifi module is disabled, so I send an M552 S0 and get an 'okay'. Next, I send an M552 S1 and get a ' turn off current wifi before selecting a new one' error. Wherein lies my mistake? Thanks
-
Please share the results of M122
How did you attempt to update from 2.05 to 3.0?
How did you update from 3.0 to 3.3?Did you update the wifi server firmware as well?
Did you update the DWC files as well?
@gbusy24 said in Updating from 3.0 to 3.3 gone wrong:
but get unsolvable error messages
Such as?
-
@phaedrux I updated from 2.05 to 3.0 by downloading and installing the Duet 2 and 3 firmware 3.0 zip file. Same for going to 3.3 from 3.0. I downloaded and installed the Duet 2 and 3-3.3 zip file It's my understanding that everything is included in the zip files.
-
Yes, uploading the zip files through DWC is the recommended option.
If M115 shows you have 3.3 flashed, that's a good start.
It's possible that the wifi firmware didn't get updated correctly and cannot start. The solution is to reflash the wifi module. The files should already be there, so you can just send M997 S1 from the USB terminal or PanelDue to flash it again.
Sending M122 will give some information on the wifi module as well at the end of the report.
-
This post is deleted! -
I've tried sending M997 S1 several times and I keep getting ' Duet Wifi server .bin not found, even though I know that file is in fact on the SD card in the sys folder.......................................................................................................................................................................M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SN-6JKD2-3S46L-9VS3M
Used output buffers: 1 of 24 (11 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 73064 of which 124 recycled
Never used RAM 17352, free system stack 193 words
Tasks: NETWORK(ready,8.0%,521) HEAT(delaying,0.0%,386) Move(notifyWait,0.1%,338) MAIN(running,92.0%,475) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:36:55 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 0
MCU temperature: min 35.6, current 37.2, max 37.5
Supply voltage: min 1.7, 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
Driver 0: position 34982, ok, SG min/max not available
Driver 1: position 34982, ok, SG min/max not available
Driver 2: position 34982, 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 4294967295
Slowest loop: 4.74ms; fastest: 0.13ms
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.25ms; 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
- WiFi -
-
@gbusy24 said in Updating from 3.0 to 3.3 gone wrong:
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
Place it in the firmware folder on the SD card as that is where it's going to be looking in 3.3.
-
@gbusy24 note that you will need to create a firmware folder at the root level of the SD card, and move or copy the DuetWiFiServer.bin file into that. 3.3 expects to find firmware update files there, but only creates it when files are uploaded once 3.3 is running. You are trying to run the firmware update file uploaded by 3.0, which put the files in the sys folder.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@phaedrux It works now thank you
-
@droftarts It works now thanks for the help!
