Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
One or more of the messages the vehicle controller receives periodically from the Tire Pressure Monitoring System (TPMS) electronic control unit (ECU) is not received, indicating the TPMS ECU may be unavailable (MIA).
|
One or more of the expected messages from the TPMS ECU is not received.
|
Vehicle functionality depending on the TPMS ECU may be limited or unavailable.
|
|
|
One or more of the messages the vehicle controller receives periodically from the heat pump system compressor (CMPD) electronic control unit (ECU) is not received, indicating the CMPD ECU may be unavailable (MIA).
|
One or more of the expected messages from the CMPD ECU is not received.
|
The HVAC system 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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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 vehicle controller (VC) identified the PCS is MIA and may be in need of a power cycle to be recovered. This alert indicates the low voltage (LV) battery is in good state to support this.
|
The PCS is MIA when expected to be active on CAN, the LV battery is connected, the vehicle is not in service mode, and the vehicle is not being updated.
|
The PCS may be power cycled by the high voltage system.
|
|
|
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.
|
|
|
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.
|
|
|
A condition affecting left front turn signal functionality has been detected - the left front turn signal may be degraded or disabled, and remaining left side turn signals will fast blink.
|
The headlamp ECU is MIA on LIN (not responding to Local Interconnect Network traffic) while powered on, or an internal condition with the turn signal LEDs or the headlamp ECU's LED driver is detected.
|
Left side turn signals will fast blink
|
|
|
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
|
|
|
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 (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 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.
|
|
|
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.
|
|
|
GTW is detected to be MIA while in Drive Power State.
|
GTW is detected to be MIA while in Drive Power State
|
GTW may not function as expected
|
|
|
An electrical error has been detected with the left fog light guide (white light pipe in front fascia that turns on along with fog light).
|
The high side driver (HSD) for the left fog light guide reports that an undercurrent or short circuit condition is present.
|
The left fog light guide may not be working.
|