Skip to content

Create core WRover POST #63

@bennowotny

Description

@bennowotny

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:

  • 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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions