Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
The Drive Inverter (DIx) has detected a quantity of torque production that indicates Drive Unit wear.
|
DIx has detected a quantity of torque production that indicates Drive Unit wear.
|
The Drive Unit may have wear resulting from torque production. The vehicle may enter launch mode torque.
|
|
|
The drive inverter (DIx) electronic control unit (ECU) detects that the left vehicle controller (VCLEFT) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the VCLEFT, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the VCLEFT.
|
|
|
The drive interface (DI) or drive inverter (DIx) electronic control unit (ECU) detects a Gateway configuration mismatch with the application currently running on the DI.
|
Set if any of the checked gateway config is not as expected.
|
The vehicle enters system limp mode and is unable to enter Drive.
|
|
|
The drive inverter (DIx) electronic control unit (ECU) detects that the Etherloop Generalized Gateway Right (EGGRIGHT3) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the EGGRIGHT3, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the EGGRIGHT3.
|
|
|
The Drive Inverter (DIx) has detected an error communicating with the Serial Peripheral Interface (SPI), which monitors the pedal monitor.
|
DIx has detected an error communicating with SPI, which monitors the pedal monitor. There may be a condition affecting SPI.
|
DIx may not be able to receive data from the Pedal Monitor. The vehicle's drive cycle may not function as expected.
|
|
|
The drive interface (DI) electronic control unit (ECU) receives irrational or missing data from a wheel speed sensor (WSS).
|
The DI ECU receives irrational or no data from the WSS.
|
This alert is primarily informational. If it persists, traction control may become unavailable.
|
|
|
The Drive Inverter (DIx) has detected the capacitor is over temperature.
|
DIx has detected the capacitor is over temperature. The pack contactors may have a condition affecting functionality.
|
The flow of current between the capacitors and DIx may not function as expected.
|
|
|
Drive Unit Graceful Power Off (GPO) has been triggered. The Drive Unit will lose current input from the High Voltage (HV) battery.
|
Drive Unit GPO has been triggered. The Drive Unit will lose current input from the HV battery.
|
The Drive Unit will ramp down all torque production. The Drive Unit may not function as expected.
|
|
|
Drive Inverter Warning: Unit limp mode triggered.
|
Abnormal condition detected within drive unit subsystem. Look at limpReason in alert for exact trigger.
|
Drive system performance severely reduced (torque/power limited)
|
|
|
Drive Inverter Warning: Motor control is out of regulation.
|
Motor regulation fails to meet command inputs
|
Drive unit enters unit limp mode (see DI_a126_limpMode)
|
|
|
The Drive Inverter (DIx) node is Missing in Action (MIA) on Controller Area Network (CAN) for one or more messages.
|
The DIx node is MIA on CAN for one or more messages. The DIx node or DIx may have a condition affecting functionality.
|
DIx may not be able to communicate with the High Voltage Processor (HVP).
|
|
|
Drive Inverter Warning: HVLINK CAN node MIA.
|
Any received HVLINK frame is MIA
|
Active discharge may turn ON
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that the high voltage processor (HVP) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the HVP, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the HVP, and active discharge may turn on.
|
|
|
Drive Inverter Warning: Loss of motor control.
|
Motors are not responding to DI commands
|
Unable to produce torque/power from drive unit
|
|
|
The Drive Inverter (DIx) Electrically Erasable Programmable Read-Only Memory (EEPROM) has reported phase sensor calibration is outside valid range.
|
The DIx EEPROM has reported phase sensor calibration is outside valid range.
|
This alert is primarily for logging purposes and appears in conjunction with other alerts.
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that the electronic parking brake (EPB) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the EPB, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the EPB.
|
|
|
The Drive Interface (DI) processor has detected an internal exception. This alert does not on its own indicate a symptom or root cause.
|
The DI processor detects an exception.
|
This alert is primarily informational and is used for logging purposes.
|
|
|
The Drive Unit resolver (motor speed sensor) has detected the motor exceeding typical speed.
|
The Drive Unit resolver has detected the motor exceeding typical speed. The rotor or rotor shaft may have a condition affecting functionality.
|
The motor is exceeding typical speed. The motor and Drive Unit may not function as expected.
|
|
|
The Drive Unit is not able to transition to Drive state. There may be a condition preventing the Drive Unit from transitioning states.
|
The Drive Unit is not able to transition to Drive state. There may be a condition preventing the Drive Unit from transitioning states.
|
The Drive Unit may not function as expected, including a reduction in vehicle power. The vehicle's drive cycle may not function as expected, or at all.
|
|
|
The Drive Inverter (DIx) has detected an error communicating with the Field Programmable Gate Array (FPGA).
|
DIx has detected an error communicating with FPGA. There may be a condition affecting the DIx control board functionality.
|
The DIx Gate Drive Unit may not be able to receive data from the Pedal Monitor. The vehicle's drive cycle may not function as expected.
|