Skip to content

Update EEPROM with More Fields and Customization #7

@Duncan-McD

Description

@Duncan-McD

We need to include more fields in EEPROM on PMB than we did with PAN. This is because if the satellite ever needs to reboot, we need to be able to store our full state so we don't have to completely start from scratch each boot. This will allow us to more effectively use our uplinks to diagnose and debug the satellite's behavior during flight if necessary.

Additionally, we need to make EEPROM customizable.

This means adding an additional boolean field for each of the states that we can uplink that sets whether the field should be restored from the EEPROM or not boot. This will give us the option to use a saved field or not on startup which will greatly expand the ability to debug the satellite if it becomes necessary. We will need to look into how adding these extra fields will effect the telemetry flows. Additionally, we need to make sure there is enough room in the EEPROM to save this data.

Another possible customization is If there are fields we know we will never want saved in eeprom unless in extreme instances we could make those always not saved in eeprom and then have a wild card eeprom field that can hold any of the telemetry fields that we have set to not be saved. (This is not necessary if we use the toggle booleans described above, but would add a layer of customization if we didn't).

Finally have an option to set the initial constructor values as the eeprom values as if it was a factory reset.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions