Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Bridge faults are most likely due to configuration error.
|
An fault was reported by the bridge driver while initializing or controlling the bridge driver or a bridge channel.
|
Some or all bridge outputs may not opperate due to a bridge fault.
|
No
|
|
|
This alert is used to create the template for the raw alert log. Double check before this alert is used for something else.
|
Set condition
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Reset can be caused by: Clock Error, Flash Error, Software Reset, Checkstop Reset, Debug Reset
|
Potential issue with hardware or software caused the reset.
|
No
|
|
|
This message contains separate signals for Overvoltage and Undervoltage for each rail.
|
ECU 5V rail detected < 4.5V or > 5.5V, or 3.3V rail < 3.0V or > 3.6V for 100ms.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Response timeout of a LIN node
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
The SBC CAN transceiver has faulted. Alert will be seen if the trasnceiver has recovered from the faulted condition.
|
The BDY CAN bus communication is not available.
|
Other ECUs may report this ECU as being MIA and behaviour will be impacted. This alert won't be seen until CAN communcation has returned.
|
No
|
|
|
Not Available
|
Failure of a software assertion.
|
These are the repercussions of the alert being set
|
No
|
|
|
Replace battery on keyfob(s). This alert always clears upon drive rail turn off.
|
Keyfob battery too low, as seen a few seconds after drive rail turns on.
|
Keyfob may be unusable soon.
|
No
|
|
|
Not Available
|
NVRAM detected as uninitialized.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
The desired state of the rear footwell illumination could not be set, the current state is not the expected one or the brightness adjustment did fail.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Switch brake pressed != DI CAN message for 1000ms.
|
could indicate loss of communication with the drive inverter
|
No
|
|
|
Not Available
|
UHF firmware update failure. LF firmware update failure.
|
These are the repercussions of the alert being set
|
No
|
|
|
None
|
The transponder was used to open car/start car.
|
None. Purely informational. After this alert is set the car will be unlocked or will allow drive rail on (details in alert log)
|
No
|
|
|
Version 0.0 or 2.1 will cause the SE on the central controller to lock up in certain scenarios
|
If the SE version on Central Controller is not the latest one
|
-
|
No
|
|
|
Autopilot Processor Secondary (APS) received a frame from an unexpected Media Access Control (MAC) source. The payload has a 6 byte MAC address of an unknown source and the address is in the decimal number system. While this condition is present, APS may receive ethernet frames from an unknown sender.
|
APS received a frame from an unexpected MAC source.
|
APS may receive ethernet frames from an unknown sender.
|
No
|
|
|
The Autopilot electronic control unit (ECU) reports a graphic processing unit (GPU) hardware condition. Autopilot features are unavailable.
|
The Autopilot ECU experiences an unexpected GPU hardware condition caused due to an exception trigged by GPU.
|
Autopilot features are unavailable.
|
No
|