Hewitt McGaughey; Firmware; Catherine
- Catherine Burns
Left and right motor status??
A bunch of faults that the motor controller sends
Limit flags - whats limiting the speed of the motor (how much power its sending to the motors)
Maybe display the limit flags to see if the motor is being limited by power delivery
DISPLAY THE FAULTS - likely would be fatal (causing the motor to shut down)
How to display the warning messages?
If they are severe (smth that causes an immediate effect on the car) perhaps include a larger popup
For faults that are less critical, put them somewhere where it would be nice to know
Less critical ones
For some limit flags, there are faults which are expected in normal operation which aren’t concerning
Most faults relating to status will be “deal with now”
What approach worked in the past for displaying faults
The urgent information should be a major focus and should be very noticeable
Lots of status information is less critical but doesn’t need to cover any content or preempt something else
Most MCI faults should be dealt with immediately
How do bitsets work
There are enums
Fault bitset is 16 bits wide and each index in the enum corresponds to a specific bit
Whenever there’s a fault, the bit that it corresponds to is a 1 and when resolved returns to 0
Fault names
OV is over voltage
OC is over current
Some are self explanatory
Most names won’t need an explanation
Battery low may need some indication as to which battery is low
Race scenario
Say a fault occurs
Usually not much they can do immediately during the race
The faults aren’t too descriptive so in regards to power select
During pitstops or something they could look back on why this fault was happening
These faults are just indicative of some problem of AUX, DCDC, Power Supply, etc. but does not give an explanation as to why
Anything he’d like to see from the dashboard
Just focus on prioritizing the information users need
Good to know versus things that are actually actionable
Power distribution faults