Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Not Available
|
Proactive sensors indicate obstacle.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Error from LIN.
|
Windows could be malfunctioning.
|
|
|
Not Available
|
Upper latch open when lower latch requested to open.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
NVRAM detected as uninitialized.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Unsuccessful communication with NVRAM.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Flash CRC is corrupted.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Any of the signals in message RCM are set.
|
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
|
|
|
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
|
|
|
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.
|
|
|
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
|