Alerts

Alerts

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.
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
The SBC CAN transceiver has faulted. Alert will be seen if the trasnceiver has recovered from the faulted condition.
The BDY CAN bus communication is not available.
Other ECUs may report this ECU as being MIA and behaviour will be impacted. This alert won't be seen until CAN communcation has returned.
Not Available
Failure of a software assertion.
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
Undervoltage detection by the CPU can set this alert.
Sudden power loss.
These are the repercussions of the alert being set
Can sometimes be remedied by pulling/replacing fuse 233 under the MCU.
Latch is not communicating over LIN
The latch may not work if it is of the cinching type
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 or power was connected before harness with door ID pins
The ECU may not respond to the desired signals and ECU should be reset
Check the alert log for the specific failure code.
The latch reports an error code over LIN
The latch may fail to operate properly
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
The linkage may have become detached at the ball joint. This alert is only present in factory mode.
A possible issue with the PFD acutator linkage was detected
The door shuts off all powered operation until closed and latched
latch feedback switches are most likely harnessed incorrectly.
OPEN switch is active and AJAR switch is not active
Door latch status is incorrectly reported and PFD operation becomes erratic
Check alertLog for more information. If resultingState is CLOSED_BRAKE, the latch's OPEN switch may be disconnected. If previousState is OPENED_BRAKE, the latch's switches and release motor may be all disconnected.
PFD transitions from LATCH_OPENING to CLOSED_BRAKE or OPENED_BRAKE
PFD cannot open automatically
BCFPM_w065_ratchetingDetected
If front door is releasing and braking continously
Worse user experience as the door
Not to be confused with a weak cinch. This alert does not imply problems with seal load or door alignment.
Latch cinches, reports closed briefly, and then ajar.
Front door may not be able to cinch closed
The body controller will automatically re-issue a short-drop command if a failure to drop is detected.
70-80 milliseconds pass after latch opening without window drop movement (if window is fully closed)
Window may briefly catch on body frame as door opens
The body controller will automatically re-issue an undrop command if a failure to undrop is detected.
~1000 milliseconds pass after latch closes without window undrop movement (if window is at the short drop position).
Window undrop will be delayed by about 1000 ms as the door closes.
This alert probably indicates that a firmware bug was encountered. Resetting the front door body controller will temporarily resolve the issue.
Front door latch reports OPEN when body controller reports that the latch is CLOSED, or vise versa.
Vehicle will not properly detect that the door is open or closing. May also trigger several other power front door alerts.
BCFPM_w070_LatchFailedToCinch
Latch was closing and now we are not closing but the latch is not closed
-