Improve Subsystems safety #10
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If no device command is received for 500 ms, the device is automatically stopped. This prevents a scenario where a program (such as autonomy) crashes, and the rover will continue driving since no additional commands are received.
Additionally, the last received rover status of
UpdateSetting
is cached, and no commands will be sent to firmware if the status is not manual or autonomous. This means that even if a command is somehow sent to subsystems while the dashboard is set to idle, the rover will not move.