Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Not Available
|
Flash CRC is corrupted.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Any of the signals in message RCM are set.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Check if DOOR_READ_EN is enabled (pulled low) at startup; check that the doorID pins are being set low in correspondence with the desired side; run UDS routine 204 on the bootloader to read and store the side config
|
The ECU did not read the door ID pins properly on reset
|
The ECU may not respond to the desired signals
|
No
|
|
|
The most common cause of this fault is the MISO line being held low on HSD U19
|
The Freescale HSD has been returned bad data on the MISO line from the microprocessor more than 10 times in a row.
|
HSD outputs could toggle endlessly causing lights to strobe forever.
|
No
|
|
|
Not Available
|
A signal is received 10% out of timing 3 times in a row.
|
These are the repercussions of the alert being set
|
No
|
|
|
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.
|
No
|
|
|
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
|
|
|
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.
|
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
|
BDY_RCM_collision did not match BDY_BCCEN_collision
|
If any crash signal is active, crash behavior is active
|
No
|
|
|
Not Available
|
Failure of a software assertion.
|
These are the repercussions of the alert being set
|
No
|