Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
The low voltage battery management system (LVBMS) reports it has detected a low voltage (LV) battery cell voltage imbalance and is attempting to rebalance the cell voltages. The vehicle will be kept awake to support the LV battery until the rebalancing attempt is complete.
|
The LVBMS detects that all LV battery cell voltages are not within 100mV 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 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 (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
|
|
|
One or more of the messages the vehicle controller receives periodically from the right vehicle controller (VCRIGHT) is not received over the interprocessor controller area network (IPC), indicating the VCRIGHT may be unavailable (MIA).
|
One or more of the expected messages from the VCRIGHT is not received over the IPC.
|
Vehicle functions that depend on the VCRIGHT may be unavailable or may not function as expected.
|
No
|
|
|
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
|
|
|
One or more of the messages the vehicle controller receives periodically from the left vehicle controller (VCLEFT) is not received over the interprocessor controller area network (IPC), indicating the VCLEFT may be unavailable (MIA).
|
One or more of the expected messages from the VCLEFT is not received over the IPC.
|
Vehicle functions that depend on the VCLEFT may be unavailable or may not function as expected.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the rear right drive inverter (DIRER) is not received, indicating the DIRER may be unavailable (MIA).
|
One or more of the expected messages from the DIRER is not received.
|
Vehicle speed and power may be limited.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the Center Console Control Module (CCCM) electronic control unit (ECU) is not received, indicating the CCCM ECU may be unavailable (MIA).
|
One or more of the expected messages from the CCCM ECU is not received.
|
Vehicle functionality depending on the CCCM ECU may be limited or unavailable.
|
No
|
|
|
The electrical current flowing through the left vehicle controller (VCLEFT) eFuse is greater or equal to 100A. The VCLEFT eFuse circuit may open (trip) if the low voltage (LV) electrical system loads are not reduced. The vehicle controller requests the VCLEFT to shed vehicle electrical loads by cutting power to the less essential loads.
|
The VCLEFT eFuse current value equals or exceeds 100A for 100 milliseconds.
|
Some convenience features controlled by the VCLEFT will be unavailable as the vehicle controller limits the LV electrical system current draw by cutting power to some loads.
|
No
|
|
|
The low voltage battery management system (LVBMS) reports it has opened the low voltage (LV) battery internal protection transistor (MOSFET) after detecting a pack overvoltage condition.
|
The LVBMS detects a pack overvoltage condition affecting the LV battery.
|
The LV battery may be damaged and may be unable to support vehicle electrical systems.
|
No
|
|
|
Warns if the processor has experienced a reset due to power loss.
|
Sudden power loss.
|
Controller is MIA for some time.
|
No
|
|
|
The low voltage battery management system (LVBMS) reports it has opened the low voltage (LV) battery internal protection transistor (MOSFET) after detecting a cell overvoltage condition.
|
The LVBMS detects a cell overvoltage condition affecting the LV battery.
|
The LV battery may be damaged and may be unable to support vehicle electrical systems.
|
No
|
|
|
Vehicle will enter deep sleep to conserve energy in 10 minutes. It is possible to wake the vehicle up within the next 10 minutes by pressing the trunk button or applying external voltage to the front trunk (frunk) access posts.
|
The vehicle is in Transport Mode and the high voltage (HV) battery state of charge (SOC) is low.
|
Vehicle will only wake from deep sleep via a trunk button press or when external voltage is applied to the frunk access posts.
|
No
|
|
|
The eFuse application-specific integrated circuit (ASIC) on the vehicle controller has incorrect thresholds set.
|
The vehicle controller detects incorrect threshold values on its eFuse ASIC for 1 second.
|
The eFuse ASIC on the vehicle controller may not function as expected.
|
No
|
|
|
The vehicle is attempting to recover from a deep sleep. If the vehicle does not begin charging, the vehicle will reenter deep sleep after 10 minutes.
|
The vehicle is in Transport Mode, the high voltage (HV) battery state of charge (SOC) is low, and the user attempts to interact with the vehicle.
|
Vehicle requires charging before it can be recovered from deep sleep. Until adequately charged, the vehicle will only wake from deep sleep via a trunk button press or when external voltage is applied to the frunk access posts.
|
No
|
|
|
Vehicle will enter deep sleep to conserve energy in 10 minutes. It is possible to wake the vehicle up within the next 10 minutes by pressing the trunk button or applying external voltage to the front trunk (frunk) access posts.
|
The vehicle is in Transport Mode and the high voltage (HV) battery state of charge (SOC) is low.
|
Vehicle will only wake from deep sleep via a trunk button press or when external voltage is applied to the frunk access posts.
|
No
|
|
|
The low voltage battery management system (LVBMS) reports it has opened the low voltage (LV) battery internal protection transistor (MOSFET) after detecting a hardware overcurrent condition.
|
The LVBMS detects a hardware overcurrent condition affecting the LV battery.
|
The LV battery may be damaged and may be unable to support vehicle electrical systems.
|
No
|
|
|
A low voltage (LV) battery recovery attempt has timed out and has been aborted, and the internal protection transistor (MOSFET) has been opened. May occur because an external power supply is connected to the LV battery, or due to a high impedance connection between the power conversion system (PCS) and LV battery. The low voltage battery management system (LVBMS) reports a FAULT state.
|
The LVBMS reports an LV battery recovery attempt has timed out and has been aborted because 50 seconds have passed without the LVBMS detecting adequate current flow to the LV battery across the internal protection transistor (MOSFET).
|
The high voltage (HV) system will remain energized to continue supplying electrical power to the vehicle while the LV battery is unavailable. This may result in greater range loss than expected, increased HV system energy consumption when the vehicle is idle, and prevent the vehicle from sleeping. The vehicle will be unable to drive while this alert persists.
|
No
|
|
|
The low voltage (LV) battery internal protection transistor (MOSFET) is open, while the LV battery is at low state of charge and recovering the MOSFET is not being attempted. As a result, the low voltage battery management system (LVBMS) continues to draw power from the cells, which may make the LV battery unrecoverable if it is not disconnected soon.
|
The LV battery state of charge (SOC) is less than 30%, the LV battery internal protection transistor (MOSFET) is open, and there are no low voltage battery management system (LVBMS) communication or firmware mismatch issues.
|
The LV battery may become too deeply discharged and unrecoverable.
|
No
|