Alerts

Alerts

Signal Name Description Condition Impact
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
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
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.
The door latch had to be rehomed because of an unexpected movement in the latch's release motor.
The latch is not performing a release but the home switch on the release actuator is deactivated.
Until this alert clears, the door latch may spontaneously release.
Window pinch event detected.
Window pinch condition detected, see alert payload for pinch reason
Window will not complete actuation and reverse
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.
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
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
The mechanical release was used to open the door.
The mechanical release was used to open the door.
Possible damage to window trim.
Window glass did not short drop while opening the door.
Door Vehicle Controller (VCDOOR) is unable to roll down the window when opening the door.
Window glass is fully open. User may cause bright damage and experience difficulty closing the door if window is not lowered before closing.
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.
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.
Lack of current and encoder ticks from the presenter indicates it is no longer connected to the controlller.
Current draw falls below the undercurrent threshold and no encoder counts are seen when a high enough voltage is applied to the presenter motor
Door will not present from an exterior button press and may get stuck out, preventing the door from closing
Door does not open when requested due to the latch not releasing when expected.
Latch state transitions from opening to closed
Door will not open
A large voltage drop is detected in the input power to the vehicle controller, indicating the resistance on the input power feed to the vehicle controller is higher than expected.
Estimated resistance on the input power feed to the vehicle controller is higher than expected.
The vehicle controller may be unavailable due to lack of adequate input power, limiting vehicle functionality or making the vehicle inoperable, with at least one other alert specific to that condition present.
One or more of the messages the vehicle controller receives periodically from the vehicle security controller (VCSEC) is not received, indicating the VCSEC may be unavailable (MIA).
The vehicle controller does not receive one or more of the expected messages from the VCSEC within the expected time frame.
Features depending on VCSEC functionality, including vehicle security and communication with authentication devices, may be limited or unavailable.
One or more expected Controller Area Network (CAN) messages from the Electronic Stability Program (ESP) electronic control unit (ECU) was not received. Stability and traction control functions may be unavailable, or their performance may be affected.
An expected CAN message from the Electronic Stability Program (ESP) electronic control unit (ECU) has not been received within the expected timeout, or the message drop rate is too high while the ESP is CAN active. The ESP is considered CAN active when VCFRONT_privateGoToSleep is 0 AND VCFRONT_espLVState is LV_ON.
Stability and traction control functions may be unavailable, or their performance may be affected.
One or more of the messages the vehicle controller receives periodically from the right vehicle controller (VCRIGHT) is not received, indicating the VCRIGHT may be unavailable (MIA).
The vehicle controller does not receive one or more of the expected messages from the VCRIGHT within the expected time frame.
Vehicle functions that depend on the VCRIGHT may be unavailable or may not function as expected.
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.
One or more expected Controller Area Network (CAN) messages from the vehicle gateway (GTW) was not received. Vehicle functions that depend on CAN messages from the GTW may be unavailable, or their performance may be affected.
An expected CAN message from the vehicle gateway (GTW) has not been received within the expected timeout, or the message drop rate is too high while the GTW is CAN active. The GTW is considered CAN active when VCFRONT_vehGoToSleep is 0.
Vehicle functions that depend on CAN messages from the vehicle gateway (GTW) may be unavailable, or their performance may be affected.