Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
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
|
|
|
reseting the controller should fix the issue.
|
Driver side config stored in NVRAM does not match the config sent by GTW
|
controller may have behaviors that correspond with the wrong side of the car
|
|
|
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
|
|
|
Not Available
|
A passenger side shutface or exterior button (handle) is stuck pressed
|
passenger side shutface or exterior button (handle) input ignored
|
|
|
Not Available
|
A driver side shutface or exterior button (handle) is stuck pressed
|
Driver side shutface or exterior button (handle) input ignored
|
|
|
Not Available
|
The desired state of the reflector lamp could not be set, the current state is not the expected one or the light did time out
|
These are the repercussions of the alert being set
|
|
|
check occupancy sensor and harness, seat belt sensor and harness, damaged ECU.
|
2nd row center seat detects buckle switch is in the faulted or disconnected voltage range
|
Occupant safety is impacted
|
|
|
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.
|
|
|
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.
|
|
|
Overtemp, overload, current limitation, under voltage.
|
The latch motor is running and the status output pin becomes high
|
The latch motor will be disabled
|
|
|
Latch motor encountered obstruction or end stop not handled by app.
|
The latch motor reads an unreasonably high or stall current of greater than 3.5 amps for greater than 250 ms
|
The latch motor will be disabled
|
|
|
Check for damamged motor.
|
The latch motor reads an unreasonably low current of less than 0.1 amps for greater than 250 ms
|
The latch motor will be disabled
|
|
|
Not Available
|
Upper latch open when lower latch requested to open.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
The desired state of the shutface switch backlighting could not be set, the current state is not the expected one or the brightness adjustment did fail
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
The desired state of the ambient lighting could not be set, the current state is not the expected one or the brightness adjustment did fail
|
These are the repercussions of the alert being set
|