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
Changing configuration variables is one of the safer ways to change the behavior of the satellite without having to inject new code into the runtime. This can include very simple changes like changing the critical_battery_voltage to a different value or more significant changes like changing the frequency that the radio is operating on.
One of the things to potentially consider when implementing this framework is thinking about how to handle safely updating configuration settings to ensure that there is a minimal risk that a user might accidentally push and update that will end up locking them out of the system. Thinking about how to architect that will probably be the bulk of the difficulty of this task.
Required Hardware
Any Version of the Flight Controller Board
The text was updated successfully, but these errors were encountered:
Story
Acceptance Criteria
cdh.py
that handles configuration updatescdh.py
that returns the current version and last modified date of the software and config filesconfig.py
a way to temporarily update a configuration variable (in RAM until the next reset)config.py
a way to permanently overwrite a configuration variable inconfig.json
(update that is persistent through resets)out of range
error handling to block configuration updates that could create unhandled exceptionsTechnical Details
Changing configuration variables is one of the safer ways to change the behavior of the satellite without having to inject new code into the runtime. This can include very simple changes like changing the
critical_battery_voltage
to a different value or more significant changes like changing thefrequency
that the radio is operating on.One of the things to potentially consider when implementing this framework is thinking about how to handle safely updating configuration settings to ensure that there is a minimal risk that a user might accidentally push and update that will end up locking them out of the system. Thinking about how to architect that will probably be the bulk of the difficulty of this task.
Required Hardware
The text was updated successfully, but these errors were encountered: