Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Two window pinch events occured within 30 seconds of each other
|
Two window pinch events occur within 30 seconds of each other
|
Window pinch sensitivity will be greatly reduced
|
No
|
|
|
The Door Vehicle Controller (VCDOOR) self-test did not pass, as a condition affecting a load on the VCDOOR was detected during the self-test.
|
The VCDOOR undervoltage self-test does not succeed. If a stuck-on or stuck-off condition is present, specific information can be found in the undervoltage self-test stuck-on or stuck-off debugging alerts.
|
The vehicle may not allow drive or some loads may not turn on.
|
No
|
|
|
One or more loads did not turn on during the Door Vehicle Controller (VCDOOR) undervoltage self-test. Those loads will be inhibited from use while in Drive.
|
One or more loads did not turn on during the VCDOOR undervoltage self-test.
|
Impacted load(s) will not be usable in Drive.
|
No
|
|
|
Door presenter has stopped for unexpected reasons.
|
Door presenter experiences an unexpected stop.
|
Door presenter may require calibration or replacement.
|
No
|
|
|
Presenter did not reach the soft stalling state within the allotted wait time.
|
Presenter does not reach the soft stalling state within the timeout period.
|
Door will not present, making it difficult to open.
|
No
|
|
|
Door Presenter is not calibrated
|
Door presenter lost calibration or calibration routine is unable to complete successfully
|
Door will not present from the exterior button making it hard to open the door
|
No
|
|
|
Door Presenter has not learned or does not know where the body of the vehicle is
|
Door presenter lost the body position or the body find routine is unable to complete successfully
|
Door presenting will be slow from the exterior button
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the vehicle battery controller (VCBATT) is not received, indicating the VCBATT may be unavailable (MIA).
|
One or more of the expected messages from the VCBATT is not received.
|
Vehicle functionality depending on the VCBATT may be limited or unavailable.
|
No
|
|
|
Window thermal protection mode is activated and user input was attempted, but blocked
|
Repeated window cycling in a short period of time
|
User commands for window open or all user commands are ignored (depending on which thermal protection mode is set) until window motor cools
|
No
|
|
|
Window encoder ticks not seen while the front window motor is being driven: This suggests something is disconnected, shorted, or the controller voltage supply for the encoders is < 9V
|
Window motor is being driven and no encoder feedback is seen within 500 ms
|
Window motor is possibly disconnected or shorted
|
No
|
|
|
Window is not calibrated
|
Window Uncalibrated: calibration routine was never run, was unsuccessful, or the window recorded reaching an impossible position
|
May short drop and reverse at all positions, no anti-pinch detection
|
No
|
|
|
Window thermal protection mode engaged
|
Repeated window cycling in a short period of time
|
No user-initiated down/closing movement permitted in THERMAL_ALERT mode, no user-initiated movement permitted in THERMAL_CRITICAL mode
|
No
|
|
|
The vehicle controller has detected a condition affecting Inertial Measurement Unit (IMU) functionality, triggering the IMU recovery process.
|
The vehicle controller detects a condition affecting IMU functionality.
|
Vehicle functionality depending on the IMU may be limited or unavailable.
|
No
|
|
|
Window pinch event detected
|
Window pinch condition detected, see alert payload for pinch reason
|
Window will not complete actuation and reverse
|
No
|
|
|
Unexpected voltage seen on non-continuous device outputs
|
Voltage is above 10V for 200ms on at least one of the device outputs while none of them are being driven
|
Electrical loads for mirror tilt up/down, mirror tilt left/right, mirror fold out/in, and mirror motor control may be unavailable.
|
No
|
|
|
Window speed is too fast or in the wrong direction.
|
Vehicle controller detects window speed is too fast or in the wrong direction.
|
Windows may lose calibration.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the drive interface (DI) electronic control unit (ECU) is not received while the vehicle is in Drive, indicating the DI ECU may be unavailable (MIA).
|
One or more of the expected messages from the DI ECU is not received while the vehicle is in Drive.
|
Vehicle speed and power may be limited.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the Steering Column Control Module (SCCM) is not received, indicating the SCCM may be unavailable (MIA).
|
One or more of the expected messages from the SCCM is not received.
|
Vehicle may be unable to shift between drive modes.
|
No
|
|
|
Window pinch detection has been overriden by holding the auto-up window switch.
|
The vehicle controller detects window pinch detection has been overriden by holding auto-up switch.
|
Window pinch detection is unavailable while the condition persists, as pinch detection is not enabled when overriden by holding the auto-up switch.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the left vehicle controller (VCLEFT) is not received, indicating the VCLEFT may be unavailable (MIA).
|
The vehicle controller does not receive one or more of the expected messages from the VCLEFT within the expected time frame.
|
Vehicle functions that depend on the VCLEFT may be unavailable or may not function as expected.
|
No
|