Why do I occasionally get a config.g.bak file in the system directory? Is this written because the config.g file is invalid? Any way to tell if the system is reading from the config.g or config.g.bak?

Thanks.

Hardware: Duet v0.6

Firmware: 1.22 (2018-07-26b2)

DWC: 1.22.4

I have always assumed it is generated whenever config.g is edited.

Frederick

Hardware: Two custom deltas that started life as kits - all now equipped with DuetWiFi/Duex5. A Duet equipped FT-5 with all of the 713 upgrade bits is now working very well. My current project is a D-Bot CoreXY.

Ok, so it is DWC that uses it rather than the machine, and the machine never uses it? Feature request for DWC to clean it up after use to save confusion or themachine to delete it on startup if present?

Ok, so it is DWC that uses it rather than the machine, and the machine never uses it? Feature request for DWC to clean it up after use to save confusion or themachine to delete it on startup if present?

You can always delete it yourself but I think keeping a backup is a good idea - even if it only contains the contents of the previous config.g.

From time to time I use the DWC to download and save backups of all the various .G files needed for a complete configuration.

Frederick

Hardware: Two custom deltas that started life as kits - all now equipped with DuetWiFi/Duex5. A Duet equipped FT-5 with all of the 713 upgrade bits is now working very well. My current project is a D-Bot CoreXY.

@bot I think the reason it is done is to stop two processes accessing/modifying the same data at the same time. At a guess DWC is creating this file so you can read and modify it without potentially accessing it at the same time as the duet ie, mid build. The rename opperation it atomic, meaning that other processes can't interrupt it by accident. I doubt it is a user backup and as such it is pretty useless as the most likely thing to happen that will cause data loss is sd card failure.

If it is indeed the previous config when chanhes have been made then that needs to be more obvious.

If it is indeed the previous config when chanhes have been made then that needs to be more obvious.

It seems to be that - I just compared the two files on my machine.

Frederick

Hardware: Two custom deltas that started life as kits - all now equipped with DuetWiFi/Duex5. A Duet equipped FT-5 with all of the 713 upgrade bits is now working very well. My current project is a D-Bot CoreXY.