-
Notifications
You must be signed in to change notification settings - Fork 9
Closed
Description
Component Name
ModeManager
Issue Type
- Component State Management
Current Issues
Right now our use of SafeMode to return the satellite's radios to a known state may have unintended conflicting behavior with startup / reboots. The issue kind of goes as follows:
- Entering into SafeMode currently runs the
radio-enter-safe.seq, which sets the radio to a known good state but calling this during startup could override the behavior of thestartup.seqwhich tries to delay activation of the radio for 45 minutes - If the command loss timer triggers it is supposed to put the satellite in safe mode, but it also calls a
STOP_WATCHDOGwhich triggers a reboot. That reboot will then restore the satellite to compile time defaults rather than whatever behavior is defined in the safe mode sequence. With that in mind, maybe compile time defaults should just be the safe mode?