Ensure that core WRover hardware is functional/connected prior to starting the main sequence of WRover code. Provide meaningful diagnostic messages to operators as to which subsystem is not working, potentially including some root-cause analyses
Anti-Goal
This is NOT to:
Create Unit Tests: POST is run at WRover launch time, unit tests should be run before software is deployed
Perform Actions with the WRover: POST is to make sure that things are connected/operational, which enables subsequent code to actuate the WRover
Required Actions
[ ] Create a software package containing POST tests, including:
Motor communication bus tests
Sensor tests (for sensors that are permanently connected to the chassis of the WRover)
Communication tests (talking to all daughterboards, remote systems)
Tzanccc
commented
11 months ago 
Rationale
Ensure that core WRover hardware is functional/connected prior to starting the main sequence of WRover code. Provide meaningful diagnostic messages to operators as to which subsystem is not working, potentially including some root-cause analyses
Anti-Goal
This is NOT to:
Required Actions