Hello,
I probably missed some information.
Every time I perform a firmware update I lose the machine setup parameters (width, height, vertical or horizontal, etc.) and I lose all the parameters of the last calibration performed.
So after the update I have to set the machine parameters again and redo the very long calibration. Is it normal?
Marcello
This is correct, aside from needing to do a new calibration.
Calibration just determines the frame size, you can copy your frame size data from your current maslow.yaml file to the new one before uploading it. You just need to download the file. You only need to update the frame size entries in the new file.
If you do not do this, you will need to recalibrate.
The parameters to copy from the old file are the Maslow_* lines.
David Lang
Specifically, if you go to the FluidNC tab, and click on the folder icon, it should show you the files on your Maslow, which should include the Maslow.yaml file. One of the icons next to the file name will allow you to download that file.
This clears up a question I had. Having to run a calibration with new firmware. Is there a recommendation on how often to update the .gz and .yaml files? I’ve been doing it each firmware update, then re-configure and calibrate each time.
Generally you don’t need to update the .yaml file. It’s only if we add a new parameter to it that it needs to get updated which we did fairly often in the first couple weeks, but now not so much. I would say that unless the description for the new firmware version says to update the .yaml file you probably don’t need to.
Scott wrote:
This clears up a question I had. Having to run a calibration with new
firmware. Is there a recommendation on how often to update the .gz and .yaml
files? I’ve been doing it each firmware update, then re-configure and
calibrate each time.
you need to update index.html.gz every release, there are almost always changes
there.
the maslow.yaml doesn’t always need to be updated, but it’s not clear when you
can skip it, so you should update it.
but you don’t need to re-configure and calibrate if you copy the Maslow_* lines
from your old maslow.yaml file.
David Lang
Bar wrote:
Generally you don’t need to update the .yaml file. It’s only if we add a new
parameter to it that it needs to get updated which we did fairly often in the
first couple weeks, but now not so much. I would say that unless the
description for the new firmware version says to update the .yaml file you
probably don’t need to.
re: new maslow.yaml parameters, I think it would be a best practice to add code
to set new parameters to default values if they are not specified in the .yaml
file. That way we could almost always skip mandatory replacement of the file.
This is what I was attempting to do in the PR that added parameters re: belt
extensions and frame arms.
David Lang