Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
BCFPM_w073_UnexpectLatchOpen
|
Latch reported open or ajar but PFD is actually closed
|
-
|
|
|
The Body Controller Front Driver Door (BCFDM) or Body Controller Front Passenger Door (BCFPM) detects latch is not fully closed after ramping.
|
The BCFDM or BCFPM detects latch is not fully closed after ramping. The BCFPM detects latch is not fully closed after ramping.
|
Door will not close properly. If vehicle is locked, alarm may sound.
|
|
|
BCFPM_w075_DoorIceBreakerAttempt
|
In initial ice breaking state
|
-
|
|
|
BCFPM_w076_DoorIceBreakerFailure
|
Ice breaker has pulled home but the latch is not open
|
-
|
|
|
Often caused by a kinked release cable or damaged cable tubing.
|
Mechanical release is pulled while interior release button is not triggered
|
Front door may not properly close
|
|
|
The door zero position is cleared.
|
The door zero position was cleared due to latch closing while door angle is above threshold value, the angle reaching threshold negative value, or the door controller resetting while latch is not closed. Alert payload data should provide more information on specific condition(s) involved.
|
The door power operation is disabled.
|
|
|
Not Available
|
Response timeout of a LIN node
|
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
|
|
|
BCFPM_w080_CurrentDropOut
|
A significant drop in current is seen while actuator is being driven
|
Actuator will temporarily not respond to being driven
|
|
|
This alert helps to indicate if the latch has water ingress which has damaged or caused undesired behaviors for the vehicle.
|
While the vehicle is moving, latch status changes from CLOSED to OPENED.
|
Door may be unlatched while vehicle is in motion.
|
|
|
For engineering diagnoses only.
|
Front door just transitioned from unzeroed->zeroed
|
None
|
|
|
The door stopped unexpectedly while opening or closing.
|
The door controller detected a stopping condition while opening or closing. Alert payload data should provide more information on specific condition(s) involved.
|
Door opening or closing actuation did not complete.
|
|
|
BCFPM_w085_ESPGyroUnstable
|
the ESP has shutdown before stable acceleration values could be captured
|
Engineering debug alert only
|
|
|
BCFPM_w086_badESPData
|
the ESP values are greater than 9.8 m/s
|
Engineering debug alert only
|
|
|
BCFPM_w090_CrashUnlockError
|
Vehicle did not unlock after crash.
|
These are the repercussions of the alert being set
|
|
|
BCFPM_w091_CrashStateMismatch
|
BDY_RCM_collision did not match BDY_BCCEN_collision
|
If any crash signal is active, crash behavior is active
|
|
|
Check OTP region of DFLASH.
|
Error reading from OTP.
|
Genealogy information may not be read.
|
|
|
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.
|
|
|
Log contains CPU load for each task.
|
CPU load exceeds 80%.
|
High CPU load can indicate ineffecient code.
|