Firmware bundle 3.2.2 released
-
Same error - "ERROR: Operation 3 failed after 5 retries" - Web page shows "Please wait while updates are being installed..."
-
@Foden what version of dwc is it showing installed?
-
"Operation 3" means the firmware flasher has initialised, unlocked, and erased the flash memory, but failed to write the new firmware. The failure could either happen when reading from SD card or when writing to flash memory. So it's worth trying a new SD card.
-
K, will try a new card
-
Not sure what happened - tried a different card but am now NOT able to connect to the DuetWifi via USB and Bossa. Laptop shows the Duet as Com5, Bossa sees Com5 but says "Cannot connect to device on Com5" -
@Phaedrux It did say 3.2.2 but now I can't get to it via Bossa at all
-
@Foden I'm an idiot - in the process of detailing the above it dawned on me I had NOT pressed Erase
Doing so allowed me to connect via Bossa to upload Duet2CombinedFirmware.bin
(deleted the large post with photos as it was redundant and in the way - sorry) -
@Foden Happy Days!!! Was able to apply the 3.2.2 upgrade and it applied OK. Wifi showed as connected but not able to connect to it just yet. Will reset and retry that shortly
-
@Foden Hmm. Duetwifi reports it is connected to Wifi, as does my router, but I cannot connect to it via it's IP address
Going to switch it all off and walk away for a bit as my brain was obviously in DFU mode earlier and may still be stuck there
Appreciate your help guys - as always
-
@Foden said in Firmware bundle 3.2.2 released:
Duetwifi reports it is connected to Wifi, as does my router, but I cannot connect to it via it's IP address
Double check the IP address. Clear the cache. Try a different browser. Verify that the /www folder contains the right files. If in doubt, replace the files in the /www folder with fresh ones from the DWC zip file.
-
@Phaedrux Hi
IP was correct, cache was cleared and tried different browser - also tried different PC completely - no go. Left everything switched off for a few hours then powered it up and left it alone for 15mins. Bingo - able to connect to it via the web - no idea what the hell that was all about. Powered it off/on a few times and each time all good.
-
Looks like something in 3.2.2. has broken pressure advance. Just tried my first print which is something that worked fine on an earlier firmware (3.1??) and there was about a 0.5mm gap between the infill and the perimeters and the ends of the infill lines were rough as hell. I disabled PA and the resultant print is fine again.
Either that, or there is some other random bug which caused the problem and which was cured by editing config.g and re-staring the machine..........
-
Hello, can I get back to version 3.2.0 quickly?
sudo apt-get upgrade duetsoftwareframework = 3.2.0 not working
-
sudo apt install \ duetsoftwareframework=3.2.0 \ duetcontrolserver=3.2.0 \ duetruntime=3.2.0 \ duetsd=1.1.0 \ duetsoftwareframework=3.2.0 \ duettools=3.2.0 \ duetwebcontrol=3.2.0 \ duetwebserver=3.2.0 \ reprapfirmware=3.2.0-1 \ --allow-downgrades -
It doesn't work
send the message: unable to locate package
-
@luis Perhaps try it with a singe line then:
sudo apt install duetsoftwareframework=3.2.0 duetcontrolserver=3.2.0 duetruntime=3.2.0 duetsd=1.1.0 duetsoftwareframework=3.2.0 duettools=3.2.0 duetwebcontrol=3.2.0 duetwebserver=3.2.0 reprapfirmware=3.2.0-1 --allow-downgradesWhy do you want to downgrade in the first place?
-
oooooh thanks.
I was making it bad.
I am making changes to rrf, and they are not in 3.2.2 yet.
-
Same here: I upgraded my Duet Wifi (v1.02) from 3.2.0 (my first v3 firmware) to 3.2.2 and the printer got stuck and required additional help to get WiFi running again. I had used the new update procedure for the PanelDue (5" v3.0) just before that, just to mention that in case it helps. SD card seems fine though, if I can trust Windows...
@dc42 While searching on how to do this, I found your wiki help section "Installing and Updating Firmware" seems a bit outdated. It is still talking about iape4e/iap4s.bin being needed. Thankfully the M997 command complained about the missing Duet2_SDiap... file instead of showing me obscure error codes as some other systems might do.
(thanks @T3P3Tony for getting my account running again btw, the Akismet spam tool drove me nuts... now I can at least post something again even if it still bugs me now and then...)
