This document defines the links between the data we collect from our solar car to what data is displayed on the driver display. The table below goes through each piece of data in the driver display and describes how we collect that piece of data.
Driver Display Feature | Data from Vehicle |
|---|---|
Time | The time is pulled from the Raspberry Pi |
Speed | id: 19
source: STEERING
# target: DRIVER_DISPLAY, MOTOR_CONTROLLER
msg_name: "cruise_target"
can_data {
u8 {
field_name_2: "target speed"
}
}
|
Right / Left Signal | msg {
id: 24
source: STEERING
target: "LIGHTS"
msg_name: "lights"
can_data {
u8 {
field_name_1: "lights_id"
field_name_2: "state"
}
}
}
|
Battery Change | msg {
id: 47
source: CHARGER
# target: telemetry
msg_name: "charger info"
can_data {
u16 {
field_name_1: "current"
field_name_2: "voltage"
field_name_3: "status_bitset"
}
}
}
|
Cruise Control | id: 41
source: STEERING
# target: TELEMETRY
msg_name: "cruise control command"
can_data {
u8 {
field_name_1: "command"
}
}
|
Drive State | id: 22
source: MOTOR_CONTROLLER
# target:
msg_name: "drive state"
can_data {
u16 {
field_name_1: "drive_state"
}
}
|
Lights | id: 24
source: STEERING
# target: LIGHTS
msg_name: "lights"
can_data {
u8 {
field_name_1: "lights_id"
field_name_2: "state"
}
}
|
BPS Warning | id: 0
source: BMS_CARRIER
# target: CENTRE_CONSOLE
msg_name: "bps heartbeat"
is_critical: true
can_data {
u8 {
field_name_1: "status"
}
}
|
BMS Over Voltage | id: 33
source: BMS_CARRIER
# target: TELEMETRY
msg_name: "battery aggregate vc"
msg_readable_name: "battery aggregate voltage and current"
can_data {
u32 {
field_name_1: "voltage"
field_name_2: "current"
}
}
|
MCI Over Voltage | id: 34
source: CENTRE_CONSOLE
# target: TELEMETRY
msg_name: "state transition fault"
msg_readable_name: "motor controller voltage current"
can_data {
u16 {
field_name_1: "state_machine"
field_name_2: "fault_reason"
}
}
|