Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Undervoltage detection by the CPU can set this alert.
|
Sudden power loss.
|
These are the repercussions of the alert being set
|
No
|
|
|
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
|
No
|
|
|
A condition affecting switch functionality has been detected.
|
A condition is detected affecting switch functionality. Alert log signal data should provide more information on the switch affected and specific condition.
|
The switch may not function or may not function as expected.
|
No
|
|
|
A large voltage drop is detected in the input power to the vehicle controller, indicating the resistance on the input power feed to the vehicle controller is higher than expected.
|
Estimated resistance on the input power feed to the vehicle controller is higher than expected.
|
The vehicle controller may be unavailable due to lack of adequate input power, limiting vehicle functionality or making the vehicle inoperable, with at least one other alert specific to that condition present.
|
No
|
|
|
An issue is indicated from the non-volatile memory manager.
|
Non-volatile memory misconfiguration or underlying flash/filesystem error.
|
Non-volatile memory records may be incorrect or missing.
|
No
|
|
|
The vehicle controller detects the supply voltage from 1 or more components is outside of the expected range.
|
The vehicle controller detects the supply voltage from 1 or more components is < 7.31. Alert log signal data should provide more information on the specific condition(s) detected.
|
Features depending on the vehicle controller functionality may be unavailable or may not function as expected.
|
No
|
|
|
Warns if the processor has experienced a reset due to power loss.
|
Sudden power loss.
|
Controller is MIA for some time.
|
No
|
|
|
Warns if the processor has experienced a reset due to watchdog reset.
|
A watchdog (external or internal) was not serviced in time.
|
Controller is MIA for some time.
|
No
|
|
|
Check OTP region of DFLASH
|
Error reading from OTP.
|
Genealogy information may not be read.
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
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.
|
No
|
|
|
Log contains CPU load for each task.
|
CPU load exceeds 80%.
|
High CPU load can indicate ineffecient code.
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|