You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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
* To load the settings, you print the `SETTINGS.GCO` file
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).
The text was updated successfully, but these errors were encountered: