General viewing data
In general: As a team member, I need to be able to access all of the data. Doing so doesn’t necessarily have to be effortless; I just need to be able to access and view it.
Finding/searching for data:
**Displaying values vs **booleans vs enums: **
Specific values: As a team member, I need to be able to view the specific value of each data point on the graphs
**Comparing data: As a team member, I need to be able to view and compare multiple graphs so I can see and compare how each graph changes relative to each other. This will allow me to pinpoint if a change in one set of data corresponds with a change in another (i.e. changes occur at the same time, or one changes after the other) and aid in issue triangulation.
I will often compare data sets that are closely related to each other, such as front battery voltage and rear battery voltage
I could also theoretically want to compare stuff like altitude and motor controller temperature (how does going up a hill affect the MCl temp?)
Connection errors: As a team member, I need to know if and when the telemetry dashboard went offline, so that I know a) that the connection needs to be fixed and b) what time the data that is currently on the dashboard is from
Faults
All faults: As a team member, I need to be able to see/access all faults easily and know exactly when they are happening as soon as possible, so I am able to address or debug them.
**Urgent faults: As a team member, I need to know which faults are urgent/critical, so I can stop and start investigating the solar car immediately.
Non-urgent faults: As a team member, I need to be able to see less-urgent faults from earlier in the day, so I am able to address or debug them at checkpoints or at the end of the day. **
Fault information: As a hardware team member, I need to have an idea of where the fault is originating from (which part of the car/which board/etc) so that I can quickly diagnose the problem, locate the fault physically in the car, and start working with the part.
**Historical data
Fault investigation: As a team member, I need to be able to find and see all the data at the time that a fault occurred, so I can figure out what went wrong.
Navigating historical data: As a team member, I need to be able to find and view all the data at a specific time (ie from hours earlier). For example, we may have gone up a hill at 4:35PM, and I am curious about how that affected x, y, and z.
Race time
Rapid context changes: As a team member that frequently rotates in and out of looking at the dashboard, I need to be able to decipher the dashboard and the state of the system quickly with limited context so that these rotations can happen efficiently.
Don’t overwhelm them with information
Fewer and larger graphs/pieces of information at the forefront
Logically grouped graphs/information
Better graph labelling where the information can be read and processed by non-firmware users (or anyone who may not be so familiar with the content).