Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
One or more of the messages the vehicle controller receives periodically from the rear left drive inverter (DIREL) is not received, indicating the DIREL may be unavailable (MIA).
|
One or more of the expected messages from the DIREL is not received.
|
Vehicle speed and power may be limited.
|
|
|
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.
|
|
|
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.
|
|
|
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 onboard charger (CHG) electronic control unit (ECU) is not received, indicating the CHG ECU may be unavailable (MIA).
|
The vehicle controller does not receive one or more of the expected messages from the CHG ECU within the expected time frame.
|
Charging may not start or may be interrupted unexpectedly.
|
|
|
A condition affecting left daytime running light (DRL) functionality has been detected - the left daytime running light may be degraded or disabled
|
An internal condition with the daytime running light (DRL) LEDs or the headlamp ECU's LED driver is detected.
|
Left daytime running light (DRL) may be partially or fully disabled
|
|
|
The vehicle controller detects the supply voltage from 1 or more components is outside of the expected range.
|
The vehicle controller detects the supply voltage from 1 or more components is < 7.31. Alert log signal data should provide more information on the specific condition(s) detected.
|
Features depending on the vehicle controller functionality may be unavailable or may not function as expected.
|
|
|
An issue is indicated from the non-volatile memory manager.
|
Non-volatile memory misconfiguration or underlying flash/filesystem error.
|
Non-volatile memory records may be incorrect or missing.
|
|
|
The current measurement reported by the LV battery (LVBMS_packCurrent) does not match the current sensor on the vehicle controller LV battery feed (IBSCurrent).
|
The absolute value of current difference between LVBMS_packCurrent and IBSCurrent exceeds nominal expectations
|
Incorrect battery current data being used, resulting in sub-optimal LV battery management.
|
|
|
One or more of the expected messages the electronic control unit (ECU) receives periodically from the high voltage processor (HVP) ECU is not received, indicating the HVP may be unavailable (MIA).
|
One or more of the expected messages from the HVP ECU is not received.
|
Vehicle may be unable to drive. Charging may be limited or unavailable.
|
|
|
A condition affecting switch functionality has been detected.
|
A condition is detected affecting switch functionality. Alert log signal data should provide more information on the switch affected and specific condition.
|
The switch may not function or may not function as expected.
|
|
|
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.
|
|
|
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.
|
|
|
The Low Voltage Battery Management System (LVBMS) detects high temperature at the low voltage (LV) battery MOSFET (internal protection transistor).
|
The LVBMS MOSFET temperature has reached 100 deg C for 1 second.
|
The low voltage (LV) battery may show degraded performance or become unavailable due to high temperatures.
|
|
|
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.
|
|
|
The Low Voltage Battery Management System (LVBMS) detects that the low voltage (LV) battery pack is experiencing high temperatures.
|
The LVBMS module temperature has reached 60 deg C for 1 second.
|
The low voltage (LV) battery may show degraded performance or become unavailable due to high temperatures.
|
|
|
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.
|
|
|
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.
|
|
|
The vehicle battery controller (VCBATT) detects an eFuse overcurrent event (or a trip) on the left headlight power feed.
|
The VCBATT detects an eFuse overcurrent event on the left headlight power feed.
|
The left headlight may be unavailable or may not function as expected.
|
|
|
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.
|