Idiot's Guide To Upgrading Duet Firmware
-
@gbartsch
I guess a good starting point will be reading here. Especially the Migration from RRF2.x chapter.
It is a bit overwhelming, but the only thing you have to do manually is maybe pressing the reset button on the Duet or powercycle the PSU.
(and being able to bang your head against the wall or table can help, too
) -
@o_lampe Thanks. Yes, that's the document that intimidates me. My machine has a power switch I can operate so I'm glad to know I can reset the Duet by turning that off/on (one issue solved). And I have walls in my house so I'm good for the head banging part.
-
@o_lampe said in Idiot's Guide To Upgrading Duet Firmware:
It is a bit overwhelming, but the only thing you have to do manually is maybe pressing the reset button on the Duet or powercycle the PSU.
So that means I can get myself into, and possibly out of, trouble without physical assistance. That's concerning and encouraging at the same time.
-
@gbartsch said in Idiot's Guide To Upgrading Duet Firmware:
Downloaded my current config file from the DWC ('config - current.json' [attached])
Did you also get your config.g file? the .json file is used by the config tool to store it's settings for if you want to re-import your config and make changes there. Config.g is the file that RRF actually reads at startup. Any manual changes would happen to config.g. config.json is not user editable.
@gbartsch said in Idiot's Guide To Upgrading Duet Firmware:
@Phaedrux mentioned rebooting after certain operations:
When uploading the firmware zip file you will be prompted to install and restart automatically.
Do you have a USB cable ready to attach to the Duet in case you need to communicate with the board via terminal software like YAT? Or on the off chance that it must be flashed directly with Bossa?
-
@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:
Did you also get your config.g file?
Sorry. Yes one was generated but it's 14.8mb and I wasn't able to attach it here.
-
Your config.g file is 14mb?! It shouldn't be more than 14kb!
-
@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:
Do you have a USB cable ready to attach to the Duet in case you need to communicate with the board via terminal software like YAT? Or on the off chance that it must be flashed directly with Bossa?
Currently I don't have a USB cable ready to attach. I did have one when I set up the board and I do have YAT installed and ready.
I'll look for the cable.
-
@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:
Your config.g file is 14mb?! It shouldn't be more than 14kb!
I'm sorry. The config.zip file was 14.8mb; that's what I could not upload.
Here's the config.g file.
-
And this is the current config.g file.
-
I've loaded the two config.g files in Beyond Compare and am looking at the differences; I can understand some of this.
-
config.zip is larger because it probably contains the firmware and DWC update files as well.
I'll take a look at your config.g a little later.
-
undefined gbartsch referenced this topic
-
@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:
I'll take a look at your config.g a little later.
Thank you!
-
@gbartsch
Both config files are generated for the old firmware version.
You have to select "3.3 or later" in the general tab....
That does make a big difference in the result...... -
@DIY-O-Sphere said in Idiot's Guide To Upgrading Duet Firmware:
You have to select "3.3 or later" in the general tab....
Ah; oops! I'll do as you say and post the results.
-
Sorry, previously I neglected to choose an upgraded version of the firmware from the Configuration Tool. I've re-run the tool after choosing '3.3 or later'.
Here are the updated files:
-
Do you use an endstop or a bltouch for homing the Z axis?
Here's an updated config set that should serve you well. The config tool caught most things from your previous config, but either you had made manual changes along the way, or it didn't catch everything.
Either way, I've updated it a bit to better match. Only thing I am not sure about is the probe or endstop question. The homeall.g you shared uses an endstop, but your updated config doesn't have a z endstop defined.
-
@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:
Here's an updated config set that should serve you well. The config tool caught most things from your previous config, but either you had made manual changes along the way, or it didn't catch everything.
Thank you for modifying the file; I'm eager to look through it. I don't seem to see it though?
I had indeed made changes to the original file.
My machine uses an endstop for homing (at the top) so I'm not sure why the Configuration Tool didn't define one. I'm going to assume that is very important and will need to be resolved before trying to do the upgrade.
-
So no probe at all? Your old config does appear to have a bltouch defined.
-
@Phaedrux When my friend set up this extruder and installed the Duet board on my machine he installed the BLTouch. It worked and I ran a few bed mesh probing routines and saw the bed diagram but I never used ABL (I just tram the bed manually and am happy with that). Once a print failed and the BLTouch pin broke off when it dragged over the broken part so it's useless ATM and I don't want to use it going forward regardless. When someone can help me I want to remove it entirely.
-
I thought of a way to generate a pristine set of config files. I opened the RepRapFirmware Configuration Tool in two browsers on two separate PCs.
On PC1 I ran the Configuration Tool based on the current machine's config.g file and on PC2 I ran the Configuration Tool from a clear start.
I copied values from each page using settings from the current machine's and added their values to the Configuration Tool on PC2. I had to add a few things to PC2's config files, as well as delete some. I'm betting I achieved a clean set of config files. I altered the homing files too based on the current machine.
Here are the two config.g files:
CURRENT
config.gPRISTINE
config.g
