Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
DCDC feed has been tripped due to an encountered fault condition.
|
|
Increased load on the 12 Volt battery to power the rest of the feeds, 12 Volt battery will not recoup charge.
|
|
|
VBat Fused High Current feed has been tripped due to an encountered fault condition.
|
|
Air Suspension compressor will not be provided power in a trip scenario.
|
|
|
A condition affecting switch functionality has been detected.
|
A condition is detected affecting switch functionality. Alert log signal data should provide more information on the switch affected and specific condition.
|
The switch may not function or may not function as expected.
|
|
|
A large voltage drop is detected in the input power to the vehicle controller, indicating the resistance on the input power feed to the vehicle controller is higher than expected.
|
Estimated resistance on the input power feed to the vehicle controller is higher than expected.
|
The vehicle controller may be unavailable due to lack of adequate input power, limiting vehicle functionality or making the vehicle inoperable, with at least one other alert specific to that condition present.
|
|
|
Debug information for 10ms task errors
|
Task could not be scheduled because it was already running or pending.
|
Failure to run tasks on schedule.
|
|
|
Lockout malfunction encountered when requesting the drive rail.
|
|
Car will not be allowed to enter drive.
|
|
|
Cabin overcurrent condition has been encountered.
|
|
-
|
|
|
Debug information for 1000ms task errors.
|
Task could not be scheduled because it was already running or pending.
|
Failure to run tasks on schedule.
|
|
|
Debug information for 100ms task errors.
|
Task could not be scheduled because it was already running or pending.
|
Failure to run tasks on schedule.
|
|
|
Debug information for 1ms task errors.
|
Task could not be scheduled because it was already running or pending.
|
Failure to run tasks on schedule.
|
|
|
CPU under heavy load.
|
CPU load exceeds 80%.
|
High CPU load can indicate ineffecient code.
|
|
|
If a task failed to initialize.
|
A task init function returns with an error.
|
If an init routine fails, software may not opperate correctly.
|
|
|
If a task was not able to run at the appropriate time.
|
Task could not be scheduled because it was already running or pending.
|
Failure to run tasks on schedule.
|
|
|
An issue is indicated from a particular non-volatile memory record.
|
Non-volatile memory record not found, CRC mismatch, version mismatch, version upgrade.
|
The particular non-volatile memory record may be incorrect or missing.
|
|
|
An issue is indicated from the non-volatile memory manager.
|
Non-volatile memory misconfiguration or underlying flash/filesystem error.
|
Non-volatile memory records may be incorrect or missing.
|
|
|
Alert Manager encountered an internal processing error.
|
When an error occurs. For QueueFull, when the queue is full and no more alerts can be processed.
|
Alerts are not sent.
|
|
|
CPU detected a reset.
|
Reset can be caused by: Clock Error, Flash Error, Software Reset, Checkstop Reset, Debug Reset
|
Controller is MIA for some time.
|
|
|
The vehicle controller detects the supply voltage from 1 or more components is outside of the expected range.
|
The vehicle controller detects the supply voltage from 1 or more components is < 7.31. Alert log signal data should provide more information on the specific condition(s) detected.
|
Features depending on the vehicle controller functionality may be unavailable or may not function as expected.
|
|
|
An error has been detected with CAN transmission. Used by engineering to debug.
|
CAN configuration issues (invalid driver configuration), CAN driver issues (errors transmitting, queue full).
|
Failure to send messages.
|
|
|
An internal software assertion has failed.
|
Failure of a software assertion.
|
Unknown.
|