Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Not Available
|
Response timeout of a LIN node
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
After a record upgrade is successful, resetting the ECU should clear the alert.
|
Record not found, CRC mismatch, Version mismatch, Version upgrade.
|
Indicate the state of non-volatile data in the ECU.
|
|
|
The electronic control unit (ECU) detects that the supply voltages from 1 or more components are out of range.
|
The ECU detects the supply voltage is < 7.31V. Specific reason(s) should be available in alert log signal data.
|
The ECU may be unavailable.
|
|
|
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
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
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.
|
|
|
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
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Reasons to keep the controller awake have been the same for greater than one hour
|
The bus could not sleep causing significant range loss for the battery pack
|
|
|
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.
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
This message contains separate signals for each watchdog reset source.
|
A watchdog (external or internal) was not serviced in time.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
A signal is received 10% out of timing 3 times in a row.
|
These are the repercussions of the alert being set
|
|
|
The inward-facing Ultrasonic Sensor (USS) located on the left Falcon Door has encountered a hardware failure.
|
Alert log signal data should provide further information on specific condition(s) involved.
|
Malfunctioning hardware in the left Falcon Door's internal ultrasonic sensor can result in intermittent or total loss of functionality of the USS.
|
|
|
The inward-facing Ultrasonic Sensor (USS) located on the right Falcon Door has encountered a hardware failure.
|
Alert log signal data should provide further information on specific condition(s) involved.
|
Malfunctioning hardware in the right Falcon Door's internal ultrasonic sensor can result in intermittent or total loss of functionality of the USS.
|
|
|
The ultrasonic controller used by the Falcon doors is reported as OFF, or as FAULTED, while it is expected to be ON.
|
The ultrasonic controller used by the Falcon door is reported as OFF, or as FAULTED, for more than 500 milliseconds
|
The Falcon door ultrasonic sensors might not be powered on, which could limit the door obstacle detection capabilities
|
|
|
Undervoltage detection by the CPU can set this alert.
|
Sudden power loss.
|
These are the repercussions of the alert being set
|