ADVi3pp icon indicating copy to clipboard operation
ADVi3pp copied to clipboard

Export and Import EEPROM settings from SD card

Open andrivet opened this issue 7 years ago • 3 comments

  • [x] This issue is NOT about support. This is not the right place for support (there is an ADVI3++ Facebook page for that)

Feature Request

  • [x] Your request is not specific to your setup but can benefit to many people
  • [x] You have checked that you are not creating a duplicate of an existing (maybe closed) request (use the search)
  • [x] You have provided a short but meaningful title
  • [x] You have provided enough information (such as links to web sites, blogs, technical description) so that anyone can understand what you are talking about. Just any only a title is not enough.
  • [x] You have provided objective facts, not your personal feelings, your personal preferences.

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

andrivet avatar Jun 03 '18 13:06 andrivet

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:

  • Be able to save on the SD card. A solution is to add a new parameter to the M503 command to indicate the destination (serial port or SD card). It will save with a name like SETTINGS.GCO
  • A UI to use this command. A solution is to add a button on the Settings panel, near the reset one image
  • To load the settings, you print the SETTINGS.GCO file

andrivet avatar Oct 22 '22 14:10 andrivet

It is better to use a GCODE for each setting and use M501.

andrivet avatar Jun 26 '23 16:06 andrivet

I am reconsidering implementing this feature.

andrivet avatar Dec 26 '24 15:12 andrivet