Alerts

Alerts

Signal Name Description Condition Impact
One or more of the messages the vehicle controller receives periodically from the left Electronic Park Brake (EPBL) electronic control unit (ECU) is not received, indicating the EPBL ECU may be unavailable (MIA).
The vehicle controller does not receive one or more of the expected messages from the EPBL ECU within the expected time frame.
The parking brake may be unavailable or may not function as expected.
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.
The motor has detected an electrical fault (short, disconnect, or internal). Powertrain performance may be limited.
The LV8907 integrated circuit has detected a fault that requires a stop.
The radiator pump will not run. Powertrain performance may be limited. The circuit will be reset to attempt to clear the fault.
The Low Voltage (LV) battery needs to be replaced.
LV battery diagnosed as needing replacement to maintain full vehicle functionality
The LV battery may lack the power to support vehicle auxiliary systems. The vehicle may be unable to start and range loss may be experienced.
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.
One or more of the messages the vehicle controller receives periodically from the Restraint Control Module (RCM) is not received, indicating the RCM may be unavailable (MIA).
The vehicle controller does not receive one or more of the expected messages from the RCM within the expected time frame.
Vehicle functions that depend on the RCM may be unavailable or may not function as expected.
The vehicle controller was not able to go to sleep.
The vehicle controller started sleep sequence but was aborted.
Higher SoC loss than expected, higher 12V draw than expected, possible unexpected alerts.
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.
Warns if the processor has experienced a reset due to power loss.
Sudden power loss.
Controller is MIA for some time.
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 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.
One or more of the serial peripheral interface (SPI) messages the vehicle controller receives periodically from the Intelligent Battery Sensor (IBS) is not received, indicating the IBS may be unavailable (MIA).
The vehicle controller does not receive one or more of the expected SPI messages from the IBS within the expected time frame.
The vehicle may not sleep, and the low voltage (LV) battery may be overcharged or undercharged.
The low voltage (LV) battery type reported by the vehicle gateway (GTW) configuration is a battery type not supported by this controller / firmware.
The LV battery type indicated by the GTW configuration value is an LV battery type not supported by this controller / firmware.
The LV battery system will not be updated to support the new configuration reported by the GTW configuration value. LV battery performance may be limited. LV battery support for vehicle electrical systems may be limited or unavailable.
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.
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 expected CAN messages from iBooster were not received.
A message the local ECU expects to receive from the iBooster ECU has not been received within the expected timeout or the drop rate is too high while the iBooster is CAN active.
Brake boost functionality may be missing.
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 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.