Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export and Import EEPROM settings from SD card #135

Open
6 tasks done
andrivet opened this issue Jun 3, 2018 · 3 comments
Open
6 tasks done

Export and Import EEPROM settings from SD card #135

andrivet opened this issue Jun 3, 2018 · 3 comments
Labels
enhancement A feature request
Milestone

Comments

@andrivet
Copy link
Owner

andrivet commented Jun 3, 2018

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

Feature Request

  • Your request is not specific to your setup but can benefit to many people
  • You have checked that you are not creating a duplicate of an existing (maybe closed) request (use the search)
  • You have provided a short but meaningful title
  • 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.
  • 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 andrivet added the enhancement A feature request label Jun 3, 2018
@andrivet
Copy link
Owner Author

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
Copy link
Owner Author

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

@andrivet andrivet reopened this Dec 26, 2024
@andrivet
Copy link
Owner Author

I am reconsidering implementing this feature.

@andrivet andrivet added this to the 6.0.0 milestone Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A feature request
Projects
None yet
Development

No branches or pull requests

1 participant