Firmware rollback or other solution

jens55

If you upgraded from RRF2 to RRF3 then things have changed quite a bit and the config.g files between the two are not compatible.
I would suggest you run the on-line configurator to build a new config.g file (make sure to keep a backup of the old one) and then fine tune the new file based on https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview together with your old config.g file.

There are lots of people here who can help you get over hurdles to get all the details worked out after you have set up the new config.g file.

Phaedrux

Or if your not ready to make that jump you can upload 2.05.1 to roll back.

deckingman

@dmbgo But before you make the jump back to an older firmware, try adding M140 H0 to your config.g. Earlier firmware used that as a default, later firmwares do not so you have to add it. That might be all that's wrong. Worth a try anyway.

A Former User

@dmbgo said in Firmware rollback or other solution:

I then proceeded to download and install what I thought was the latest firmware.

it would certainly help to know what you thought was the latest firmware, and what version you previously used. and if you upgraded all the various parts duet firmware, wifi firmware, duet web control etc.

but to answer the question you can always roll back the firmware, it just gets a little tricky if you need to downgrade to versions where files have changed names.

if you give up on the conventional methods you can always follow these two sections to recover (or you can provide some more background, and the config files; and odds are you'll get it working)
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_How_to_recover_if_the_main_firmware_and_WiFi_firmware_versions_get_out_of_step_on_your_Duet_2_WiFi

dmbgo

Thank you so much Jens, Phaedrux, deckingman and bearer for your replies / suggestions, it seems to be a very helpful forum.
Currently this is displayed in the settings part of the web interface under software information.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 3.0 (2020-01-03b3)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

I should have but didn't make a note of the old (working) firmware version, but given that nothing has physically changed on the machine, or within my settings etc, should be still there somewhere? Right?

dmbgo

@bearer said in Firmware rollback or other solution:

it would certainly help to know what you thought was the latest firmware, and what version you previously used. and if you upgraded all the various parts duet firmware, wifi firmware, duet web control etc.

I think I have only upgraded on part of the firmware, are there other parts I should have upgraded, or should I proceed and try to roll it back to an earlier version?

dmbgo

Here is my current config.g config.g file, I think it's the only copy I have.

dmbgo

Would the Config file have been altered by the new firmware?

Danal

@dmbgo said in Firmware rollback or other solution:

Would the Config file have been altered by the new firmware?

Nope. It literally can't.

Danal

@dmbgo said in Firmware rollback or other solution:

Firmware Version: 3.0 (2020-01-03b3)

V2 to V3 requires YOU to make fairly extensive changes to the config. If you are not ready to do that, install 2.05.1 from

https://github.com/dc42/RepRapFirmware/releases

using file Duet2CombinedFirmware.bin

Once that is in and running, install DWC 2 (Duet Web Control 2) from here:

https://github.com/chrishamm/DuetWebControl/releases

Using file DuetWebControl-SD.zip. Do NOT unzip it, just upload the whole thing via the "system" tab "upload system files" button. The web interface will refresh itself as soon as the upload finishes.

dmbgo

Thanks Danal
I tried uploading and installing firmware V2.03 just then, which didn't fix things.
Tool 0
T0
undefined
n/a
n/a
0
0
Bed
Heater 0
off
error
0

I'll try your suggestion and let you know what happens.

dmbgo

I downloaded both files that you suggested, then installed the firmware and web control. Voila! it seems to be fixed. My temperature values are as I'd expect, the error for the bed has gone and I am able to turn the heaters on and see their values change.
Thanks a million.

Danal

@dmbgo said in Firmware rollback or other solution:

I downloaded both files that you suggested, then installed the firmware and web control. Voila! it seems to be fixed. My temperature values are as I'd expect, the error for the bed has gone and I am able to turn the heaters on and see their values change.
Thanks a million.

dmbgo

Printing away nicely now....
Thanks again.
Dave

dmbgo

Should I now investigate / make the changes necessary to upgrade to firmware V3? What is involved, is there a tutorial? I'd better pay attention this time.

Phaedrux

@dmbgo https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview

This will give you a taste.

In general though, if you're content to just print, stick with 2.05. But if there is a feature of RRF3 that you need, or you like to experiment and test, then updating now might be worth it.

You can use the web configurator to get a base config for RRF3 to start with. Then you may need to change a few things here and there manually.

dmbgo

Thanks Phaedrux I'll have a look. I was thinking that in future firmware upgades may need whatever this version needs.

dmbgo

Thanks Phaedrux
Now that I have looked, and had a skim read of the requirements, I realize that to upgrade to V3 is not a task to be undertaken lightly. I think I'll wait until there is a definite reason to upgrade.
Thanks for the link.
Dave

Phaedrux

@dmbgo Yes RRF3 is going to be the future of the firmware. 2.05.1 is likely to be the last update for the 2.x versions. Which you can look at as being a long term stable release with no new features and maybe bug fixes. For the Duet 2 Wifi and Ethernet and Maestro boards that's not a bad thing since it's very feature rich already. But with things like conditional gcode in RRF3 it will open a lot of possibilities for doing some cool stuff with scripting and automation.

So for the time being, sticking with RRF2 is the sane thing to do if you just wanna print. RRF3 is you wanna mess around.