Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
The charge port (CP) detects that the bed outlet door sensor is irrational, resulting in the bed outlets being permanently turned off.
|
The CP detects the bed outlet door sensor is reporting values outside the nominal range.
|
The bed outlets will not be functional.
|
|
|
The Power Line Communication (PLC) modem application for the Charge Port (CP) electronic control unit (ECU) does not load after a maximum number of automatic retries. DC fast charging will be unavailable at Combined Charging System (CCS) charge stations.
|
The Power Line Communication (PLC) modem application does not load after multiple consecutive attempts / maximum number of retries.
|
DC fast charging will be unavailable at Combined Charging System (CCS) charge stations.
|
|
|
A GB (Charging standard used in China) DC Supercharger reports an issue with the connector.
|
The GB DC Supercharger reports via the communication channel that it has detected an issue with the connector.
|
GB DC charging does not start or is interrupted.
|
|
|
The charge port (CP) receives multiple consecutive user requests to disengage the CP latch and still detects a charge cable connected, possibly indicating a condition affecting latch functionality. Using the charge port manual release cable may be required.
|
The CP detects a charge cable connected after receiving multiple consecutive user requests to disengage the CP latch.
|
Using the charge port manual release cable may be required to remove the charge cable.
|
|
|
DC charging is unavailable because the charge port (CP) electronic control unit (ECU) has detected that the high voltage (HV) back cover and/or CP AC charging connector are not present on the back of the CP inlet.
|
The CP ECU detects the HV back cover and/or charge port AC charging connector are not present.
|
DC charging will be unavailable.
|
|
|
The Charge Port (CP) Electronic Control Unit (ECU) is unable to detect the control pilot signal due to an internal condition on the CP ECU. AC charging may be unavailable.
|
The CP ECU is unable to receive the expected control pilot signal waveform due to an internal condition on the CP ECU.
|
AC charging may not be operational on the next attempt. DC fast charging should remain functional.
|
|
|
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.
|
|
|
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.
|
|
|
A CHAdeMO adapter communicating over single wire controller area network (SWCAN) reports that it has encountered an issue.
|
The CHAdeMO adapter reports via SWCAN that it has entered the faulted state.
|
Charging does not start or is interrupted.
|
|
|
A Supercharger post communicating over single wire controller area network (SWCAN) reports that it has encountered an issue.
|
The Supercharger reports via SWCAN that it has entered the faulted state.
|
Charging does not start or is interrupted.
|
|
|
An electric vehicle supply equipment (EVSE) using pulse width modulation (PWM) pilot reports that it has encountered an issue.
|
The EVSE sets the legacy pilot to the faulted state.
|
Charging does not start or is interrupted.
|
|
|
AC electric vehicle supply equipment (EVSE) communicating over single wire controller area network (SWCAN) reports that it has encountered an issue.
|
The EVSE reports via SWCAN that it has entered the faulted state.
|
Charging does not start or is interrupted.
|
|
|
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.
|
|
|
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.
|