Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
GTW_w024_chgsMia
|
|
-
|
|
|
The vehicle gateway (GTW) detects the Electronic Stability Program (ESP) electronic control unit (ECU) is running a firmware version that may not be compatible with the firmware installed on the rest of the vehicle.
|
The GTW detects the ESP ECU running a different firmware version than expected.
|
Vehicle is unable to drive until the firmware version mismatch is resolved, to make sure brake system functionality is not limited or unavailable due to firmware.
|
|
|
GTW_w023_chgMia
|
|
-
|
|
|
The vehicle gateway (GTW) detects the right Electronic Park Brake (EPBR) electronic control unit (ECU) is running a firmware version that may not be compatible with the firmware installed on the rest of the vehicle.
|
The GTW detects the EPBR ECU running a different firmware version than expected.
|
Vehicle is unable to drive until the firmware version mismatch is resolved, to make sure brake system functionality is not limited or unavailable due to firmware.
|
|
|
GTW_w022_dcdcMia
|
|
-
|
|
|
The vehicle gateway (GTW) detects the left Electronic Park Brake (EPBL) electronic control unit (ECU) is running a firmware version that may not be compatible with the firmware installed on the rest of the vehicle.
|
The GTW detects the EPBL ECU running a different firmware version than expected.
|
Vehicle is unable to drive until the firmware version mismatch is resolved, to make sure brake system functionality is not limited or unavailable due to firmware.
|
|
|
GTW_w021_thcMia
|
|
-
|
|
|
The vehicle gateway (GTW) detects the primary Electronic Power Assisted Steering (EPAS3P) electronic control unit (ECU) is running a firmware version that may not be compatible with the firmware installed on the rest of the vehicle.
|
The GTW detects the EPAS3P ECU running a different firmware version than expected.
|
Power steering may be limited or unavailable.
|
|
|
The vehicle gateway (GTW) has not received an expected state message from the Drive Inverter (DI) electronic control unit (ECU) via the controller area network (CAN) within the required time period.
|
The GTW does not receive the state CAN message from DI ECU at the expected frequency.
|
Gateway unable to monitor DI state
|
|
|
The vehicle gateway (GTW) detects the rear drive inverter (DIR) electronic control unit (ECU) is running a firmware version that may not be compatible with the firmware installed on the rest of the vehicle.
|
The GTW detects the DIR running a different firmware version than expected.
|
Vehicle is unable to drive until the firmware version mismatch is resolved, to make sure rear drive unit functionality is not limited or unavailable due to firmware. Inability to use waste heat to supplement high voltage battery heating may make charging at colder temperatures limited or unavailable.
|
|
|
GTW_w019_bmsMia
|
|
-
|
|
|
The Fast Charge (FC) Electronic Control Unit (ECU) has experienced a bus heavy condition. Messages sent by the Electric Vehicle Supply Equipment (EVSE) stay in queue or overflow, interrupting communication with the charging session.
|
FC ECU detects a full or overflowing queue when attempting to receive messages from EVSE.
|
Charging session may not start or may become interrupted.
|
|
|
The Fast Charge (FC) Electronic Control Unit (ECU) has detected a bus heavy condition when attempting to send messages to Electric Vehicle Supply Equipment (EVSE). Messages sent by the FC ECU stay in queue or overflow, interrupting communication with the charging session.
|
FC ECU detects the queue responsible for sending messages to EVSE is full or overflowing.
|
Charging session may not start or may become interrupted.
|
|
|
The Fast Charge (FC) Electronic Control Unit (ECU) has experienced a bus heavy condition. Messages received by the FC ECU stay in queue or overflow, interrupting communication with the charging session.
|
FC ECU detects the queue responsible for receiving messages is full or overflowing.
|
Charging session may not start or may become interrupted.
|
|
|
The Fast Charge (FC) Electronic Control Unit (ECU) has detected a bus heavy condition. Messages sent to the vehicle stay in queue or overflow, interrupting communication with the charging session.
|
FC ECU detects the queue responsible for sending messages to the vehicle is full or overflowing.
|
Charging session may not start or may become interrupted.
|
|
|
The vehicle is unable to begin GB (China) DC fast charging because the fast charge (FC) electronic control unit (ECU) detects that the electric vehicle supply equipment (EVSE) is unavailable (MIA).
|
The FC ECU does not receive the expected CAN messages from the EVSE within a certain time frame.
|
DC fast charging is unavailable.
|
|
|
The vehicle is unable to begin GB (China) DC fast charging because the fast charge (FC) electronic control unit (ECU) detects that the battery management system (BMS) is unavailable (MIA).
|
The FC ECU does not receive the expected CAN messages from the BMS within a certain time frame.
|
DC fast charging is unavailable.
|
|
|
The Fast Charge (FC) Electronic Control Unit (ECU) has detected timeout during waiting for EVSE connection lock.
|
FC ECU detects timeout during waiting for EVSE connection lock.
|
Charging session may not start or may become interrupted.
|
|
|
The Fast Charge (FC) Electronic Control Unit (ECU) has detected timeout during waiting for vehicle Fast Charge contactor opened.
|
FC ECU detects timeout during waiting for vehicle Fast Charge contactor opened.
|
Charging session may not normally shutdown.
|
|
|
The vehicle is unable to CHAdeMO DC fast charge (FC) because the vehicle is no longer reporting that it is ready to charge.
|
The vehicle reports that it is not ready to DC fast charge.
|
DC fast charging is unavailable.
|