Closed andrivet closed 1 year ago
After some feedback of users, I have realised that there is no need to create a new format because there is already one: GCODE produced by M503. The only things missing are:
SETTINGS.GCO
SETTINGS.GCO
fileIt is better to use a GCODE for each setting and use M501.
Feature Request
Detailed description of the feature request:
Today, when the EEPROM settings are not compatible from one version to the other, they are lost (reset). This is due to the way EEPROM data are stored and verified: there is only one global CRC code. This FR proposes to be able to export those settings in a structured format (like yaml) onto the SD card and be able to reload them later in a smart way (i.e. setting by setting, new settings with their default value).