Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
The exact location of the key cannot be determined. Since the center and left antenna are most important for passive entry, these functions will probably still work. There is a chance that functions are reduced.
|
Sets when antenna error is detected by the BCCEN
|
Passive entry and key authentication functionality reduced
|
|
|
BCCEN_w109_LFBootloading
|
BCCEN is resetting the LF IC when the communication times out or if an error was reported
|
During the time of bootloading all LF functionality is disabled - location, authentication
|
|
|
This alert is for debug. It will indicate why the immobilizer was unable to mobilize.
|
Immobilizer was unable to respond to a DI mobilization request
|
If this alert is continuously set, the vehicle may not be able to drive
|
|
|
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.
|
|
|
Not Available
|
Rail value does not match GTW request value after 500ms. Rail state is unknown.
|
These are the repercussions of the alert being set
|
|
|
BCCEN reset should clear this alert and fault.
|
When UHF chip rejected to wake up or wakeup request did not reach the UHF chip
|
Temporary loss of chargeport radio opener functionality
|
|
|
No action required with regard to this alert.
|
When UHF chip rejected the request to sleep
|
No loss of functionality
|
|
|
If you see this alert active, BCCEN needs a reset to clear off this alert.
|
When UHF chip recalibration did not reach the UHF chip or could not be successfully done
|
Temporary/intermittent loss of chargeport radio detection. Could happen when there is BLE1 Heap alert
|
|
|
If you see this alert active, BCCEN needs a reset to clear off this alert.
|
When PLL is not locked before trying to go to RX mode
|
Loss of charge handle detection, BCCEN reset should clear this temporary fault
|
|
|
This alert simply tracks the occurrence and cause of an alarm, and does not indicate that the intrusion system is necessarily faulty.
|
A door or trunk latch was opened while the vehicle was locked. Or, the intrusion sensor, if equipped, detected motion in the vehicle.
|
No functional impact
|
|
|
The alert is evaluated at drive rail cycle. The session key is needed for transponder operation.
|
The key fob reports the transponder session key not set alert.
|
Transponder operation will not work until a successful drive rail cycle without this alert present (per key)
|
|
|
Check OTP region of DFLASH.
|
Error reading from OTP.
|
Genealogy information may not be read.
|
|
|
Not Available
|
The sensor value is out of range and the sensor may be disconnected or shorted.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
CH_RCM_collision did not match BDY_RCM_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
|
|
|
Not Available
|
Keyfob secure paired, major version is either 1 or 2.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
The desired state of the courtesy lighting could not be set or the current state is not the expected.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
The desired state of the front footwell illumination 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
|