I use to make a few changes to the printer.cfg file in order to have the power for my 24 V purifier. This works well until firmware 1.3.0
Now, when I save and restart after the change, the change is implemented and active (the 24V is ON), but after a power off, the printer.cfg file doesn’t have my settings anymore.
It looks like the changes are saved to memory, but not persisted to storage. Is this by design or am I missing a setting in Fluidd?
Maybe your update turned off “advanced mode” in the menu? (That’s what lifts the write protection for the configuration files)
Thanks for replying, but, no, you can only edit the cfg file in advanced mode and “Save and Restart” is only available in that mode.
Are we talking about the official 1.3.0 firmware? Because I’m using exactly that and I have edited idle timeout, a/b motor currents, and max z-acceleration in my printer.cfg and had no issues with the settings persisting.
Yes, it is the official firmware release, not the extended one. U1_1.3.0.168_20260414155825_upgrade.bin
If it works for you, it must be something with a fluidd setting?
When you update firmware, printer.cfg changes are overwritten.
I don’t want to offend you, but did you actually check that your printer.cfg file still has the changes after a power down? The reason why I am asking is that after clicking the “save and restart” button, the changes are effectively implemented, so you think “all is well”. The changes you made might not so visible as mine : I didn’t hear the fans humming anymore when I restarted the printer.
you’re right, but the printer.cfg changes happened after the installation of firmware 1.3.0
I unfortunately have to pay german electricity prices 
, therefore I always turn my printer off when I don’t use it. Even my comments are all still in my printer.cfg.
I’m wondering what’s different between our setups - you mentioned an upgrade .bin file; did you upgrade via USB? Did you do a factory reset afterwards?
I did the upgrade wirelessly via the printer’s menu, I have not done a factory reset since, and while I did have to re-apply my changes to printer.cfg once after the update, changing the config still works for me.
(I do have other issues with 1.3.0, but that’s not for this topic)
At this point, I can only recommend you open a ticket with Snapmaker - because writing the config clearly should work with Advanced Mode enabled (after all, that’s the only thing that mode is for).
Thank you. I will open a ticket with the support group. Have a nice evening further!
After receiving the swift answers from support, it may be useful to share the reply.
The difference between release 1.3.0 and the former ones is that changes to the printer.cfg are only kept as long as advanced mode is enabled. As soon as you power off your printer with advanced mode disabled, the file is overwritten at start up.
I can corroborate this.
I also implemented an exhaust fan on my hood for the U1, while we are waiting for the official version to become available. Changes to printer.cfg to add power to the fan and make it visible in the fluidd UI worked well - until I did the same thing and turned off advanced mode after editing and saving. Everything was fine till power-off with advanced mode turned off. Today, printer.cfg is back to the original,
This does not sound very helpful. Does anybody think it is a good idea??
I actually do: That way Snapmaker can ensure that every machine with advanced mode disabled runs on their configuration. Helpful for support cases etc. Also, for less experienced users, it’s a nicer way of going back to stock settings than having to re-flash the entire firmware.
And everyone wanting to adjust things can just leave advanced mode enabled (like I do).
I think it’s a good solution overall, easy enough for novices and open enough for advanced users.
If that is a reliable strategy, I suppose it is good enough. Anyone customising their .cfg ought to be keeping a backup as well.
What happens if you follow this sequence?:
I tried this scenario : the printer.cfg file is reset at the first startup with advanced mode disabled. Probably the file is flagged as updated and at startup this is checked, or startup always overwrites the cfg files when not in advanced mode.
The latter would be the simplest way, no checking required. What if you write-protect the .cfg (if there is a CLI to do that with)?