Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Not Available
|
Failure of a software assertion.
|
These are the repercussions of the alert being set
|
No
|
|
|
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
|
|
|
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
|
|
|
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
|
|
|
BCFPM_w091_CrashStateMismatch
|
BDY_RCM_collision did not match BDY_BCCEN_collision
|
If any crash signal is active, crash behavior is active
|
No
|
|
|
BCFPM_w090_CrashUnlockError
|
Vehicle did not unlock after crash.
|
These are the repercussions of the alert being set
|
No
|
|
|
BCFPM_w086_badESPData
|
the ESP values are greater than 9.8 m/s
|
Engineering debug alert only
|
No
|
|
|
BCFPM_w085_ESPGyroUnstable
|
the ESP has shutdown before stable acceleration values could be captured
|
Engineering debug alert only
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
BCFPM_w080_CurrentDropOut
|
A significant drop in current is seen while actuator is being driven
|
Actuator will temporarily not respond to being driven
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Need to save PFD actuator-specific calibration values into NVRAM via Toolbox
|
Door brake data is using default values
|
The door brake hold force may be wrong
|
No
|
|
|
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.
|
No
|
|
|
BCFPM_w076_DoorIceBreakerFailure
|
Ice breaker has pulled home but the latch is not open
|
-
|
No
|
|
|
BCFPM_w075_DoorIceBreakerAttempt
|
In initial ice breaking state
|
-
|
No
|
|
|
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.
|
No
|
|
|
BCFPM_w073_UnexpectLatchOpen
|
Latch reported open or ajar but PFD is actually closed
|
-
|
No
|