Should we include a feature that stores certain machine-specific settings in EEPROM?
For instance, An M500 could store steps_per_unit, max speed, acceleration and others.
the data, if present and valid, is read at startup. if not present or valid, default data is used.
Care needs to be taken to make sure the data has some sort of version control, so firmware updates with different data sets don't read EEPROM data into the wrong set of variables.
I've done this before for another arduino project, can easily implement it using the code I have.
Should we include a feature that stores certain machine-specific settings in EEPROM? For instance, An M500 could store steps_per_unit, max speed, acceleration and others. the data, if present and valid, is read at startup. if not present or valid, default data is used.
Care needs to be taken to make sure the data has some sort of version control, so firmware updates with different data sets don't read EEPROM data into the wrong set of variables.
I've done this before for another arduino project, can easily implement it using the code I have.