Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
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.
|
|
|
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
|
|
|
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.
|
|
|
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.
|
|
|
Verify that front lights are working correctly.
|
If any fault is reported over LIN this alert shall be set.
|
Any lighting function on that lamp may be malfunctioning.
|
|
|
Verify that front lights are working correctly.
|
If any fault is reported over LIN this alert shall be set.
|
Any lighting function on that lamp may be malfunctioning.
|
|
|
Log contains stack usage for each task.
|
Stack usage exceeds 80% for any task.
|
Stack overflow can occur if there is not enough stack space.
|
|
|
Log contains CPU load for each task.
|
CPU load exceeds 80%.
|
High CPU load can indicate ineffecient code.
|
|
|
Production vehicle should not have Debug Jumper in place. Remove jumper from ECU.
|
ECU Debug Jumper is set.
|
ECU Debug Jumper will disable SBC watchdog, preventing external watchdog reset protection.
|
|
|
Not Available
|
BDY_RCM_collision did not match BDY_BCCEN_collision
|
If any crash signal is active, crash behavior is active
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
The log data contains failure count and up to five init failure codes.
|
A task init function returns with an error.
|
If an init routine fails, software may not opperate correctly.
|
|
|
Not Available
|
Task could not be scheduled because it was already running or pending.
|
Failure to run tasks on schedule.
|
|
|
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
|
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
|
|
|
Not Available
|
A signal is received 10% out of timing 3 times in a row.
|
These are the repercussions of the alert being set
|