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
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
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.
|
|
|
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
|
NVRAM detected as corrupted.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
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
|
|
|
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
|
Failure of a software assertion.
|
These are the repercussions of the alert being set
|
|
|
Undervoltage detection by the CPU can set this alert.
|
Sudden power loss.
|
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
|
|
|
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.
|
|
|
Check OTP region of DFLASH.
|
Error reading from OTP.
|
Genealogy information may not be read.
|
|
|
Not Available
|
BDY_RCM_collision did not match BDY_BCCEN_collision
|
If any crash signal is active, crash behavior is active
|
|
|
Not Available
|
Vehicle did not unlock after crash.
|
These are the repercussions of the alert being set
|