Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
The combined charging system (CCS) charging session is not started due to communication failures during the electric vehicle supply equipment (EVSE) discovery protocol (SDP).
|
The CP ECU detects that the SDP failed an unexpected number of times.
|
Charging does not start.
|
No
|
|
|
The power line communication (PLC) modem establishes communication successfully when it is expected to be depopulated.
|
The PLC modem responded when verifying that it is not populated.
|
Combined charging system (CCS) charging does not work.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects that the charge cable proximity did not latch within the expected timeframe.
|
The CP ECU detects that the charge cable proximity remains unlatched for longer than expected.
|
Charging does not start.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects that the electric vehicle supply equipment (EVSE) is still in an authentication state.
|
The EVSE spends longer than expected in the authentication state.
|
Charging does not start.
|
No
|
|
|
Communication times out between the charge port (CP) electronic control unit (ECU) and the electric vehicle supply equipment (EVSE).
|
The EVSE and the CP ECU cannot establish communication within the set timeframe between being connected and starting to charge.
|
Charging does not start.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) was able to recover communication with the brushless DC (BLDC) motor driver.
|
The CP ECU communicates successfully with the BLDC motor driver after communication had failed previously.
|
None.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) loses communication with the brushless DC (BLDC) motor driver.
|
The CP ECU attempts to communicate with the BLDC motor driver, but fails.
|
The CP door will not open or close as expected.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) does not sense the presence of the high voltage (HV) charge port cover.
|
The CP ECU does not detect the HV cover.
|
Charging does not start.
|
No
|
|
|
AC charging is unavailable because the charge port (CP) electronic control unit (ECU) has detected that the CP AC charging connector is not present on the back of the CP inlet.
|
The CP ECU detects the charge port AC charging connector is not present.
|
AC charging will be unavailable.
|
No
|
|
|
Vehicle is connected to an unpowered Electric Vehicle Supply Equipment (EVSE) with an incompatible software version for Vehicle To Load (V2L).
|
The CP detects a mismatch on V2L capable EVSE protocol version and the EVSE has remained in a connected and unpowered state.
|
Vehicle to load functionality until EVSE is updated.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects proximity voltage in an unexpected range.
|
The CP ECU detects that proximity voltage is outside of the expected range.
|
If the issue is with the vehicle, it will not be able to charge.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) has detected that a GB (Charging standard used in China) CC1 or CC2 charger disconnected unexpectedly during charge.
|
The CP ECU detects that CC1 or CC2 is disconnected while in the active GB DC charging state.
|
Charging may be interrupted unexpectedly, and there could be damage to the charge inlet if the charge cable is disconnected while under load.
|
No
|
|
|
Expected Battery Management System (BMS) controller area network (CAN) messages are missing. Charging may not start.
|
Charge port (CP) does not receive all expected controller area network (CAN) messages from the Battery Management System (BMS).
|
Charging may not start.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects a memory error.
|
The CP ECU detects a memory error.
|
Charging may not start or may be interrupted.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) receives pilot sensor readings that are outside of the expected range.
|
The CP ECU senses pilot voltage, period, or a duty cycle outside of the expected range that cannot be categorized into a valid pilot state.
|
Charging does not start.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects an internal memory condition on the electrically erasable programmable read-only memory (EEPROM).
|
The CP ECU detects an internal EEPROM condition.
|
Charging may not start or may be interrupted.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects an issue with the LED driver.
|
The LED driver reports a fault.
|
The charge port LED may not display colors properly or at all.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects an over voltage condition on the external low voltage (LV) power supply.
|
The external LV power supply voltage measured by the CP ECU is above 16.5V.
|
Charging may not start or may be interrupted. If the voltage is too high, the CP ECU may become damaged.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects lower than expected voltage from the low voltage (LV) battery.
|
The CP ECU detects LV supply less than 8V.
|
Charging does not start.
|
No
|
|
|
The charge port (CP) electronic control unit (ECU) detects an over voltage condition on the internal 5V power supply.
|
The internal 5V power supply voltage measured by the CP ECU is above 5.5V.
|
The charge port may not function as expected.
|
No
|