Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
The charge port (CP) electronic control unit (ECU) detects that the latch has been manually disengaged.
|
The CP ECU detects that the latch transitions to the disengaged state from the engaged or blocking state without actuating it.
|
Charging is interrupted.
|
|
|
Vehicle is connected to an offboard CHAdeMO charging station, or CHAdeMO Electric Vehicle Supply Equipment (EVSE), that is not supported.
|
The CP detects a connection to unsupported CHAdeMO EVSE.
|
Charging will not start
|
|
|
The charge port (CP) has detected a missing control pilot signal while a charge cable is connected, which usually indicates the charge station does not have power. Charging may not start, and it may be necessary to try a different charge station.
|
Proximity is detected with no control pilot signal and no digital communications, and the vehicle is not charging.
|
Charging may not start.
|
|
|
The charge port (CP) electronic control unit (ECU) detects that the latch assembly is unplugged.
|
The CP ECU detects that the latch assembly is not connected.
|
Charge rate is reduced and DC charging is unavailable.
|
|
|
The charge port (CP) electronic control unit (ECU) detects multiple charge cables at the same time.
|
The CP ECU detects both AC and DC GB charging cables at the same time.
|
Charging does not start.
|
|
|
Charge port (CP) expects the cable to be secured, but the charge port latch has not secured the cable in place. AC charge rate may be reduced, and DC charging may be unavailable.
|
A charge cable is detected. The charge port (CP) latch position sensor indicates the latch is disengaged, either after the charge port has attempted to engage the latch or when the latch is already expected to be engaged.
|
AC charge rate may be reduced, and DC charging may be unavailable.
|
|
|
Expected user interface (UI) controller area network (CAN) messages are missing. Charge port door may not open when request is made via the user interface (UI) or mobile app.
|
Charge port (CP) does not receive all expected controller area network (CAN) messages from the user interface (UI).
|
Charge port (CP) door may not open with user interface (UI) or mobile app controls.
|
|
|
Vehicle unexpectedly lost digital communications with offboard charging equipment. Charging may be interrupted.
|
Any message required to control a charge session via digital communications goes missing unexpectedly.
|
Charging may be interrupted unexpectedly.
|
|
|
The charge port (CP) electronic control unit (ECU) loses communication with the high voltage processor (HVP).
|
The CP ECU does not receive all of the expected controller area network (CAN) messages from the HVP.
|
Charging does not start.
|
|
|
The charge port (CP) electronic control unit (ECU) detects an issue with the CP door potentiometer.
|
The CP ECU detects that the CP door potentiometer is behaving erratically, based on sensor readings.
|
The CP door does not open or close as designed.
|
|
|
The charge port (CP) electronic control unit (CPU) detects an issue with the charge port door assembly.
|
The CP door potentiometer reads greater than 90% for more than 2 seconds or the potentiometer reading wraps around.
|
The charge port door does not actuate as expected.
|
|
|
The charge port (CP) electronic control unit (ECU) detects that the charge port door sensor is unplugged.
|
The CP door potentiometer reads less than 1% for more than 2 seconds.
|
The CP door does not actuate properly.
|
|
|
Lost comms with VCFRONT
|
Charge port does not receive all expected CAN messages from the VCFRONT
|
Charging may not start, charge port door and latch may not actuate, charge port LED may not work
|
|
|
The charge port (CP) electronic control unit (ECU) detects that the latch has been manually disengaged.
|
The CP ECU detects that the latch transitions to the disengaged state from the engaged or blocking state without actuating it.
|
Charging is interrupted.
|
|
|
The charge port (CP) electronic control unit (ECU) detects that the latch is not in the blocking position when it is expected to be.
|
The latch position sensor indicates that the latch is disengaged after the CP attempts to engage the latch fully, or if the latch is expected to be blocking cable insertion.
|
The latch does not block cable insertion when it is expected to.
|
|
|
The charge port (CP) latch is expected to be engaged but is not engaged. AC charge rate may be reduced, and DC charging may be unavailable.
|
The charge port (CP) latch position sensor indicates the latch is disengaged, either after the charge port has attempted to engage the latch or when the latch is already expected to be engaged.
|
The charge port (CP) latch may not engage as expected. AC charge rate may be reduced, and DC charging may be unavailable.
|
|
|
Charge port (CP) latch is expected to be disengaged but remains engaged. Charge cable may become stuck, or user may be unable to insert charge cable.
|
The charge port (CP) latch position sensor indicates the latch is still engaged or blocked after the charge port has attempted to disengage the latch.
|
The charge port (CP) latch may not disengage, charge cable may become stuck, or user may be unable to insert charge cable.
|
|
|
The charge port (CP) electronic control unit (ECU) will delay an attempt to AC charge
|
The CP ECU detects that the electric vehicle supply equipment (EVSE) has encountered an issue too many times while AC charging.
|
Charging does not start or is interrupted.
|
|
|
Lost communication with VCSEC
|
Charge port does not receive all expected CAN messages from the VCSEC
|
Charge port may not unlock, mobile app charge port controls may not work
|
|
|
The charge port detected an unsupported charging adapter
|
An unsupported charging adapter was detected
|
Charging will not begin with the unsupported adapter
|