Code CP_a069 was reported by the “Charge port” controller in the car. The letter “a” in the middle places it among entries of the alert type.
The car's charge port — latch, connector lock, indicator light and proximity sensor. These codes typically appear when the connector will not lock or the car does not register that it is plugged in.
The most common type. The car logged the event and may have shown it on the screen. The range is wide — from something trivial that clears itself to something that needs attention.
This is how the fault is named inside the car's firmware. For codes without a description it is the most precise clue there is — the name itself says what the event is about.
The text below comes from Tesla's technical documentation. We leave it in the original English so that translation cannot shift its meaning.
Door inductive sensor conversion error
ONLY USED BY PLCRLY. Indicates lack of communication with CP component.
Messages from CP are not received within 10x their expected transmit rate.
Messages from CP are received.
North America PLCRLYs may not allow CCS charging above 370A.
The CP has detected that the CHAdeMO adapter has measured a temperature at which charging should stop
The CHAdeMO adapter reports a temperature that is too high to continue charging
EVSE faults and prevents AC charging
info from manualCP_A058
The charge port detects that the EVSE has faulted while AC charging too many times
The UHF receiver stops communicating to the CP ECU via SPI
The CP re-establishes communications with the UHF receiver
May be unable to open charge port door using Tesla charge handle button
The charge port does not have communications with the BLDC motor driver
Charge port attempts to communicate with BLDC motor driver, but fails
Charge port establishes communications with the BLDC motor driver
Charge port door will not behave as expected
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).
Charge port (CP) receives all expected controller area network (CAN) messages from the Battery Management System (BMS).
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.
info from manualCP_A054
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.
The charge port (CP) latch engages, or the cable is unplugged from the charge port.
GB DC supercharger faulted due to a connector issue
GB DC supercharger indicates via the communication channel that it has detected an issue with the connector
GB DC charging may not start or may be interrupted.
Expected CHG CAN messages are missing (S/X only)
CP has not received required network management messages
Failed to decode expected V2G message
The GTW configuration for PLC support does not match the hardware installed in the vehicle
Configuration of the GTW PLC support type does not match the Charge Port configuration
Configuration of the GTW PLC support type matches the Charge Port configuration
The GTW will not update the PLC modem and PIB during OTA updates
LED current lower than expected
The CP uses this to diagnose watchdog resets
V2G communication timer expired
Thermistor input is open or short circuit
Thermistor is less than the open circuit threshold or, if short circuit detection is supported, greater than the short circuit threshold for at least one second
Thermistor is greater than the open circuit threshold and, if short circuit detection is supported, less than the short circuit threshold for at least one second
Charging or heating functions may not work as expected
Door inductive sensor reporting irrational value
Unexpected proximity voltage sensed. Indicates issue with vehicle if alert is set with no charge cable connected.
info from manualCP_A004
Sensed proximity voltage enters an unexpected range
Sensed proximity voltage enters an expected range
Inability to charge if issue is on vehicle-side
Charging session not started due to communication failures during the EVSE discovery protocol (SDP) which occurs during CCS charging
The SDP failed an unexpected amount of time
Cleared when the cable is disconnected or if an SDP attempt succeeded
Vehicle unexpectedly lost digital communications with offboard charging equipment. Charging may be interrupted.
info from manualCP_A046
Any message required to control a charge session via digital communications goes missing unexpectedly.
The charge port (CP) detects a valid line charge pilot signal, the charge cable is unplugged, or the charge port attempts to re-establish digital communications.
Charging may be interrupted unexpectedly.
Charge port does not receive all expected CAN messages from the HVP
Charge port receives all expected CAN messages from the HVP
Vehicle is connected to an offboard charger that is not supported
The CP detects an unsupported EVSE
The CP detects the handle has been unplugged
Copy it exactly, letter and number included. Photographing the screen is safest — codes often differ by a single digit, and mixing them up leads somewhere else entirely.
Some codes clear after a screen restart or after the car sits locked for a few hours. If the code does not come back, it was usually a one-off glitch.
A one-off entry and a code that appears after every drive are two different things. It helps a service centre enormously if you know exactly when it shows up.
With airbags, brakes, steering and high voltage there is no point waiting it out. With the other groups you can watch and see whether the code returns at all.
Error codes are only part of the picture. For cars on TesList you also see battery health pulled straight from the vehicle, plus a price calculator that works out from current listings what a given car is actually worth today.