Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
A condition affecting left low beam (dipped beam) or high beam (main beam) functionality has been detected - the left low beam or high beam may be degraded or disabled.
|
An internal condition affecting the low beam (dipped beam) or high beam (main beam) LEDs, pixels, or the headlamp ECU's LED drivers is detected.
|
Left low beam (dipped beam) or high beam (main beam) may be partially or fully disabled.
|
No
|
|
|
The vehicle controller is loadshedding due to a vehicle collision. Make sure the vehicle is safe to re-energize before using the Clear Post-Crash Loadshedding (PROC_VCFRONT_X_CLEAR-POST-CRASH-LOADSHEDDING) routine to resume all low voltage electrical system features and enable high voltage system again.
|
Vehicle collision is detected.
|
High voltage system is unavailable. Low voltage electrical system features are limited to conserve energy for essential functions.
|
No
|
|
|
Right headlamp powered off due to a short circuit detected on the right headlamp power rail
|
The headlamp current is above 9A for greater than 10s
|
All right headlamp lighting functions (low beam, high beam, turn signal, etc) may be degraded or unavailable
|
No
|
|
|
The low voltage (LV) battery type detected on startup is unknown. This usually happens the first time a controller is powered on, or after non-volatile memory (NVM) corruption, which will be indicated by another alert.
|
The LV battery type detected on startup is unknown.
|
LV battery performance may be limited. LV battery support for vehicle electrical systems may be limited or unavailable.
|
No
|
|
|
The low voltage (LV) battery is discharging, even though high voltage (HV) system support has been requested. Vehicle loadshedding will occur, and a separate alert will be present to indicate that condition.
|
LV battery is being discharged, even though the HV system should be supporting both the LV battery and the LV bus.
|
Vehicle loadshedding is triggered, and a separate alert will be present to indicate that condition and its impacts.
|
No
|
|
|
The vehicle controller detected that the compressor delivered much less refrigerant flow than nominal and discharge temperature was abnormally high.
|
The vehicle detects at least two of the following: refrigerant flow delivered by compressor is abnoramlly low by referring to EXV opening or cabin heating capacity, and discharge temperature is abnoramlly high.
|
The thermal system may not perform as expected and compressor has high risk of loss of isolation due to debris.
|
No
|
|
|
The Right Headlight Control Module (HCMR) detects an internal condition affecting the functionality of the right headlight, which is reported to the front vehicle controller (VCFRONT).
|
The pixel matrix manager detects non-functional pixels or has communication issues, or the voltage measured across the boost rail, Lowbeam, DRL, Side Marker, or Turn LEDs is out of range, or the LED drivers in the ECU have reported status flags, or certain values programmed in the matrix manager EEPROM are out of range.
|
Some headlight functions may be unavailable or may not function as expected. Headlight functionality may return after vehicle sleep.
|
No
|
|
|
An electrical error has been detected with the right fog light guide (white light pipe in front fascia that turns on along with fog light).
|
The high side driver (HSD) for the right fog light guide reports that an undercurrent or short circuit condition is present.
|
The right fog light guide may not be working.
|
No
|
|
|
Front trunk (frunk) latch status suggests that the frunk switches are not correctly reporting the latch status. Latch may require replecement.
|
Controller determines frunk latch switches are not reporting correctly based on recent frunk release and switch interactions.
|
The frunk latch switches may not report the correct status. The frunk latch switches may report closed when the latch is physically open.
|
No
|
|
|
The low voltage battery management system (LVBMS) reports it has detected the charge current is above the maximum limit for the low voltage (LV) battery cells in their present condition.
|
The LVBMS detects the charge current is above the maximum limit for the LV battery cells in their present condition for 1 second.
|
Exceeding charge current limits may shorten the life of LV battery cells, leading to accelerated degradation and replacement.
|
No
|
|
|
The vehicle controller has disabled communications over the bus that connects to the low voltage (LV) battery after detecting a condition (or conditions) that may cause the LV battery to become overdischarged. To avoid overdischarge that could make the LV battery unrecoverable, do not restore communications until the LV system is fully supported by the Power Conversion System (PCS).
|
The vehicle controller detects the LV battery may become overdischarged unless it sleeps, and also determines vehicle conditions are OK to disable LV battery communications.
|
The vehicle controller will have less information about the LV battery until it is serviced. Headlamps and windshield wipers may be unavailable, or may not function as expected.
|
No
|
|
|
The low voltage battery management system (LVBMS) reports the low voltage (LV) battery has a reduced state of charge (SOC), which may lead to the LVBMS opening the LV battery internal protection transistor (MOSFET).
|
The LVBMS detects the LV battery SOC is below 15% for 5 seconds.
|
The LV battery may be unable to support vehicle electrical systems.
|
No
|
|
|
The low voltage battery management system (LVBMS) reports it has detected a low voltage (LV) battery cell voltage imbalance.
|
The LVBMS detects that all LV battery cell voltages are not within 150mV of each other.
|
The LV battery may suddenly become unavailable and unable to support vehicle electrical systems. The LV battery may require replacement, and a separate alert should be present to indicate this condition if applicable.
|
No
|
|
|
The low voltage (LV) battery is not communicating as expected, indicating a potential disconnection with the vehicle controller.
|
Electronic connector position assurance (ECPA) state is signal not available (SNA), or the intelligent battery sensor (IBS) is not functioning as expected and the low voltage battery management system (LVBMS) is not communicating (MIA).
|
Loss of low voltage (LV) battery communication with vehicle controller, so the vehicle electrical system may only be supported via the power conversion system (PCS).
|
No
|
|
|
The compressor power index is lower than expected, which typically indicates a condition affecting the compressor. This can also indicate a condition affecting the discharge or suction pressure sensors. The compressor power index measures the ratio of estimated nominal compressor power consumption against electrical power the compressor actually consumes. A low index value indicates the compressor is drawing / consuming significantly more power than a nominal compressor would be expected to consume.
|
The compressor power index, which compares expected compressor power consumption against actual consumption, drops below expected levels.
|
Thermal system may show reduced effectiveness. Cabin climate control performance may be limited, with cabin heating / cooling not performing at expected levels.
|
No
|
|
|
Low Voltage hardware self-tests in progress, drive is blocked until complete.
|
A drive request is asserted while Low Voltage hardware self-tests are in progress.
|
The vehicle will not enter Drive state until self-tests complete.
|
No
|
|
|
Road grade is too steep to secure vehicle and trailer with Park Brake
|
Attempt to engage parking brake when vehicle with trailer is stopped on too steep a road grade for Electronic Parking Brake to secure the vehicle and trailer effectively
|
Car may not be secured by Electronic Parking Brake on the current road grade, may be free rolling
|
No
|
|
|
One Electronic Parking Brake (EPB) not applied, and road grade is too steep to secure vehicle and trailer with only one EPB
|
Only one Electronic Parking Brake (EPB) applied and grade too steep for one EPB to hold the vehicle with a trailer attached
|
Car may not be secured by Electronic Parking Brake on current road grade, may be free rolling
|
No
|
|
|
EPB calculate brake hw config and epb hw config independently and checks they are the same
|
All GTW config valid for EPB. Brake hw type and epb hw type do not resolve to same EPB config
|
EPB may be misconfigured for vehicle setup. Could result in caliper drag and insufficent clamp force
|
No
|
|
|
Brake temperature is above 200C and slope is greater than 10%
|
The max of the rear brake calipers is hotter than 200 C and slope is greater than 10%
|
Car may not be secured by Electronic Parking Brake on current road grade, may be free rolling
|
No
|