Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
The front vehicle controller (VCFRONT) detects an invalid coolant pump configuration. Powertrain thermal management and performance may be limited. A VCFRONT reset will typically clear the alert by correctly configuring the pump.
|
The coolant pump configuration detected does not match the configuration expected by VCFRONT.
|
The coolant pump may not work as expected, limiting powertrain thermal management and performance.
|
|
|
The front vehicle controller (VCFRONT) detects the electrical current flowing through the electronic stability program (ESP) eFuse has equaled or exceeded 100A during the previous 10 milliseconds.
|
The ESP eFuse current value equals or exceeds 100A during the previous 10 milliseconds.
|
The eFuse circuit may open (trip), interrupting power supply to ESP and making vehicle stability control limited.
|
|
|
The pack serial number (SN) is invalid and is not supported for tracking in non-volatile memory (NVM)
|
An invalid pack SN has been read
|
Pack data will not be tracked in NVM. Pack vitals, such as State of Charge, may be inaccurate after ECU resets
|
|
|
The front vehicle controller (VCFRONT) detects the electrical current flowing through the primary electronic power assisted steering (EPAS3P) eFuse has equaled or exceeded 100A during the previous 10 milliseconds.
|
The EPAS3P eFuse current value equals or exceeds 100A during the previous 10 milliseconds.
|
The eFuse circuit may open (trip), interrupting power supply to the EPAS3P and making power steering limited or unavailable.
|
|
|
The front vehicle controller (VCFRONT) detects the electrical current flowing through the secondary electronic power assisted steering (EPAS3S) eFuse has equaled or exceeded 100A during the previous 10 milliseconds.
|
The EPAS3S eFuse current value equals or exceeds 100A during the previous 10 milliseconds.
|
The eFuse circuit may open (trip), interrupting power supply to EPAS3S and making power steering limited or unavailable.
|
|
|
The front vehicle controller (VCFRONT) detects the electrical current flowing through the electromechanical brake booster (iBooster) eFuse has equaled or exceeded 100A during the previous 10 milliseconds.
|
The iBooster eFuse current value equals or exceeds 100A during the previous 10 milliseconds.
|
The eFuse circuit may open (trip), interrupting power supply to iBooster and making brake functionality limited.
|
|
|
A pack serial number (SN) change has been detected which requires an ECU reset to re-initialize data from non-volatile memory (NVM)
|
A valid pack SN has been read with does not match the pack SN associated with the NVM data used after ECU reset
|
The NVM data used during initialization may not match with the swapped pack. Pack vitals, such as State of Charge, may be inaccurate
|
|
|
The vehicle controller detects the front trunk (also known as the frunk) sensor requires service as a condition affecting functionality has been detected on one or more of the frunk latch switches.
|
May set due to any of the following: (1) one of the switches is pressed while the other is not pressed; (2) one or more of the frunk latch switches on the frunk sensor are shorted, disconnected, or in an indeterminate voltage range.
|
The frunk may not function as expected. For example, the user interface (UI) on the center display may show the frunk as open when it is actually closed.
|
|
|
An internal condition affecting left headlamp functionality has been detected - certain light functions or the headlamp fan may be degraded or disabled
|
The SSL100 pixel matrix detects non-functional pixels or has communication issues, or the voltage measured across the boost rail, Lowbeam Prefield, DRL1/2/3, or Turn LEDs is out of range, or the LED drivers in the ECU have reported status flags, or certain values programmed in the SSL100 EEPROM are out of range, or the fan current is out of range.
|
Certain light functions or the headlamp fan may be degraded or disabled. These functions will retry after the next headlamp power cycle (which occurs during sleep)
|
|
|
An internal condition affecting right headlamp functionality has been detected - certain light functions or the headlamp fan may be degraded or disabled
|
The SSL100 pixel matrix detects non-functional pixels or has communication issues, or the voltage measured across the boost rail, Lowbeam Prefield, DRL1/2/3, or Turn LEDs is out of range, or the LED drivers in the ECU have reported status flags, or certain values programmed in the SSL100 EEPROM are out of range, or the fan current is out of range.
|
Certain light functions or the headlamp fan may be degraded or disabled. These functions will retry after the next headlamp power cycle (which occurs during sleep)
|
|
|
The front vehicle controller (VCFRONT) detects the electrical current flowing through the left vehicle controller (VCLEFT) eFuse has equaled or exceeded 100A during the previous 10 milliseconds.
|
The VCLEFT eFuse current value equals or exceeds 100A during the previous 10 milliseconds.
|
The eFuse circuit may open (trip), interrupting power supply to VCLEFT and making VCLEFT unavailable.
|
|
|
The front vehicle controller (VCFRONT) detects the electrical current flowing through the right vehicle controller (VCRIGHT) eFuse has equaled or exceeded 100A during the previous 10 milliseconds.
|
The VCRIGHT eFuse current value equals or exceeds 100A during the previous 10 milliseconds.
|
The eFuse circuit may open (trip), interrupting power supply to VCRIGHT and making VCRIGHT unavailable.
|
|
|
The front vehicle controller (VCFRONT) detects the electrical current flowing through the power conversion system (PCS) eFuse has equaled or exceeded 200A during the previous 10 milliseconds.
|
The PCS eFuse current value equals or exceeds 200A during the previous 10 milliseconds.
|
The eFuse circuit may open (trip), interrupting low voltage power supply to the PCS. This could make PCS functions limited or unavailable, and may interrupt precharging of the high voltage (HV) bus .
|
|
|
The front vehicle controller (VCFRONT) detects there is voltage mismatch greater than 0.5V between the input power to the VCFRONT and the secondary power steering circuit for the secondary Electronic Power Assisted Steering (EPAS3S) electronic control unit (ECU).
|
The voltage mismatch is greater than 0.5V between the VCFRONT printed circuit board assembly (PCBA) input voltage and the eFuse output voltage.
|
Power steering may be limited or unavailable.
|
|
|
The front vehicle controller (VCFRONT) detects there is voltage mismatch greater than 0.5V between the input voltage to the VCFRONT printed circuit board assembly (PCBA) and the internally fused VCFRONT low voltage (LV) Battery Power (VBAT Fused) circuit (or eFuse) output voltage.
|
The voltage mismatch is greater than 0.5V between the VCFRONT PCBA input voltage and the eFuse output voltage.
|
Vehicle functions that rely on the VCFRONT may be limited or may not function as expected.
|
|
|
The vehicle cannot enter Drive state because the measured LV battery voltage is too low. This alert is intended to capture the LV battery conditions when drive blocking is activated and assist with diagnosis if primary alert drveBlckdVltgeTooLow cannot be logged by the vehicle Gateway (GTW) at time of initial occurrence due to LV undervoltage condition.
|
The measured LV battery voltage dropped below the level required for the drive state for 0.5 seconds, and vehicle GTW is reported as available for logging.
|
While this alert is primarily informational and intended for logging purposes, the vehicle may be unable to drive, or may take longer than expected to enter Drive state.
|
|
|
The Front Vehicle Controller (VCFRONT) sleep bypass did not raise the voltage to the target voltage in the expected amount of time.
|
The load voltage does not meet the power source voltage in the expected amount of time.
|
The load being precharged may not turn on. Vehicle functions relying on the load being precharged may not operate as expected.
|
|
|
After a Low Voltage (LV) Battery condition was identified that may prevent precharging the High Voltage (HV) Bus, the HV Bus successfully energized and will support the LV System to enable drive. The vehicle controller requests to keep the HV bus energized until the LV battery is replaced.
|
The failureToPrechargeRisk alert is set, and the HV Bus is energized.
|
The HV System will remain on to support vehicle functions, including drive, and the HV contactors will remain closed.
|
|
|
A Battery Monitoring Board (BMB) device detects a Hardware (HW) over current condition.
|
The BMB device detects an over current condition.
|
The eFuse may open, causing a loss of LV battery pack power and limiting LV battery support for vehicle electrical system.
|
|
|
Drive blocked by alcohol ignition interlock device.
|
A brake pedal press is detected when the vehicle is in Park (P) and the alcohol ignition interlock device has not yet allowed drive based on a successful alcohol test result.
|
The vehicle is unable to drive.
|