Idiot's Guide To Upgrading Duet Firmware

Phaedrux

Your config.g file is 14mb?! It shouldn't be more than 14kb!

gbartsch

@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.

gbartsch

@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.

config.g

gbartsch

And this is the current config.g file.

config - current.g

gbartsch

I've loaded the two config.g files in Beyond Compare and am looking at the differences; I can understand some of this.

Phaedrux

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.

gbartsch

@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:

I'll take a look at your config.g a little later.

Thank you!

DIY-O-Sphere

@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......

gbartsch

@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.

gbartsch

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:

config_current.g
config_new.g

homeall.g
homex.g
homey.g
homez.g

Phaedrux

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.

gbartsch

@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.

Phaedrux

So no probe at all? Your old config does appear to have a bltouch defined.

gbartsch

@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.

gbartsch

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.g

PRISTINE
config.g

Phaedrux

Here is the config set I made for you based on what I understand of your printer and your existing configuration.

config.zip.TXT

You can remove the .TXT extension and it will be a zip file you can upload to your printer after updating the firmware.

And here are the relevant individual files.

homez.g homey.g homex.g homeall.g config.g

Give that a look over and see if I've missed anything.

gbartsch

Aside from the firmware switching method you described in my pressure advance thread (https://forum.duet3d.com/topic/30990/can-t-run-pressure-advance-g-code/16) is the easiest way to ensure I can restore the printer to a working state to simply put aside a MicroSD card with all the working files on it, and do the upgrade on a different card (after copying the working files onto it)? I'm assuming that putting that original card back in the Duet would restore the machine to a working state if something went wrong with the upgrade?

gbartsch

@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:

Here is the config set I made for you based on what I understand of your printer and your existing configuration.

Thank you! I'll look through these.

Phaedrux

No the firmware is flashed to the Duet board itself. The SD card only has the configuration.

I would suggest that to start with you upload the 2.05 zip file to see how it goes, since it is still RRF2 it doesn't require any config file changes.

gbartsch

@Phaedrux said in Idiot's Guide To Upgrading Duet Firmware:

Here is the config set I made for you based on what I understand of your printer and your existing configuration.

Fabulous! Thank you! Aside from a few settings most of the settings in the config.g file I made match yours. Where I knew I could, I moved your settings to my config.g file.

There are a few differences and I don't understand which to use. I've included the two files.

Should I disable bang-bang for the heater bed? I'm assuming yes as it is the old method?
Should I use your sensor values or mine? I'm going to run the Configuration Tool again inputting my thermistor values to see what numbers are generated.
Should I use your fan values or mine? I have the hotend fan and two part cooling fans (on on either side of the hotend).
And I've defined a second tool; is that another hotend? I have only one and wasn't sure what I was doing when I ran to the Configuration Tool so probably should not have added a second.

Crikey, I think we're almost there!!

[I'll look at the homing files soon.]

1675050410916-config.g

config.g