| DTC Data Sheet | |
| System | Powertrain |
| Standard | Manufacturer Specific |
| Fault type | General |
| Official meaning | Abnormal CP voltage |
| Definition source | BYD factory description · Autel MaxiSys Ultra & EV |
P1F60 means your BYD has detected an abnormal Control Pilot (CP) voltage during a charge-related check. In plain terms, the car may refuse to charge, stop charging early, or show a charging fault message. You might also find that the charger and vehicle will not “handshake,” even though the plug fits. According to BYD factory diagnostic data, this code indicates Abnormal CP voltage, which points to the CP signal used to coordinate safe AC charging. This is a manufacturer-specific BYD code, so the exact logic and enabling conditions can vary by BYD platform and software.
P1F60 Quick Answer
P1F60 on BYD points to a problem with the CP voltage used for AC charging communication. Start by verifying the charge cable/EVSE, then test the CP circuit integrity at the vehicle inlet before replacing parts.
What Does P1F60 Mean?
Official definition: “Abnormal CP voltage.” The charging control system sees the CP signal outside the expected range or pattern. In practice, that usually shows up as no charge start, an interrupted charge session, or a charging system warning while plugged in.
What the module checks and why it matters: The vehicle monitors the CP line at the charge inlet to confirm the EVSE handshake and permitted current level. The CP voltage and its change over time tell the vehicle when a connector is present and when charging is allowed. When CP looks wrong, the car blocks or stops charging to prevent unsafe energizing. For diagnosis, treat P1F60 as a pointer to the CP signal path. Confirm the CP signal quality, wiring, and connector condition before condemning the inlet, on-board charger, or a control module.
Theory of Operation
On BYD EVs, the CP circuit supports the AC charging handshake between the EVSE and the vehicle. The EVSE drives a control pilot signal to the car through the charge connector. The vehicle reads that signal at the inlet and uses it to decide when to close internal charging contactors and command the on-board charger.
P1F60 sets when the vehicle’s charging logic sees CP voltage behavior that does not match the required states. A damaged cable, a contaminated inlet, or a CP wire fault can distort the CP signal. The vehicle then treats the session as unsafe or invalid and prevents charging. You must confirm the CP signal at the inlet and along the harness to isolate whether the fault lives outside the car, at the inlet, or inside the vehicle.
Symptoms
P1F60 typically appears during plug-in events or while charging on AC equipment.
- Charge failure Charge session will not start after plugging in
- Charge interruption Charging stops early and may require unplug/replug
- Cluster message “Charging fault” or “Unable to charge” warning appears
- Port indicator Charge port light shows an error state or abnormal pattern
- Intermittent behavior Works on some EVSEs but fails on others
- Unlock issues Connector latch may stay locked due to aborted handshake
- Stored DTCs Additional charging-related codes may store in powertrain/charge control
Common Causes
- Charge port contamination or moisture: Water or conductive debris can distort the CP voltage and make the signal unstable during plug-in or charging.
- Charge port terminal fretting or corrosion: Light corrosion raises resistance and creates a distorted CP waveform that the BYD controller flags as abnormal.
- Loose or spread CP-related terminal fit: Poor pin tension causes intermittent contact, so the CP voltage jumps during vibration or cable movement.
- Open circuit in CP signal path: A broken wire or disconnected terminal prevents the controller from seeing the expected CP voltage behavior.
- Short to ground or short to power on the CP circuit: Insulation damage can clamp or pull up the CP voltage beyond expected limits.
- High-resistance ground on the charge control electronics: A weak ground shifts the controller’s reference, so the measured CP voltage looks wrong even when the EVSE works.
- Power supply disturbance to the charge control module: A weak 12 V supply, fuse issue, or relay contact drop can corrupt CP processing and trigger the DTC.
- EVSE/cable CP signal abnormality: A faulty home charger or damaged cable can output an incorrect control pilot signal that the vehicle correctly rejects.
- Connector damage between charge inlet and vehicle harness: Bent pins or cracked housings allow intermittents that appear as abnormal CP voltage during handshake.
Diagnosis Steps
Use a scan tool that can read BYD powertrain DTCs, freeze frame, and live data for charge status. Have a quality DMM, a back-probe kit, and a fused test light. Plan for a known-good EVSE and charge cable for A/B testing. Perform voltage-drop tests under load, not continuity checks alone.
- Confirm P1F60 and record all DTCs. Save freeze frame data, focusing on battery voltage, ignition state, charge request/charge status, and any charging-related state flags. Freeze frame shows the exact conditions when the fault set. Use a scan tool snapshot later to capture live CP-related data during a reproduced event.
- Check the simple causes first before meter work. Inspect the charge inlet area for water intrusion, dirt, bent pins, heat discoloration, and a loose inlet mounting. Verify the charge door area drains and seals. If the concern appears after rain or car washes, treat moisture as a prime suspect.
- Check fuses and 12 V power distribution feeding the charging control electronics. Do not go straight to the controller connector yet. Load-test the suspected fuses with a test light and confirm the fuse blades and sockets stay cool and tight. A fuse can pass continuity but fail under load.
- Verify module power and grounds under load with voltage-drop testing. Command a condition that powers the charging/related control circuits, when possible, and measure ground drop from the module ground pin to the 12 V battery negative. Keep ground drop under 0.1 V with the circuit operating. Then measure power-side drop from battery positive to the module power feed under the same load.
- Inspect harness routing from the charge inlet toward the body harness and control electronics. Look for pinch points, chafe marks, prior collision repairs, and areas where the harness flexes. Move the harness while watching live data and DTC status. An intermittent CP fault often appears during cable handling.
- Disconnect and inspect relevant connectors with careful terminal checks. Look for backed-out terminals, spread pins, corrosion trails, and signs of arcing. Clean only with approved electrical contact cleaner and allow full dry time. Do not scrape terminals aggressively, since you can remove plating and create repeat failures.
- Perform circuit integrity checks on the CP signal path with the system powered as required by BYD service information. Check for shorts to ground and shorts to power on the CP circuit. Then check for opens and high resistance from the inlet side toward the module. Use a loaded test method where possible, since a marginal strand can pass an ohmmeter test.
- A/B test with a known-good EVSE and cable. Attempt a charge session and monitor scan tool data for charge handshake state changes and any immediate pending faults. If P1F60 only occurs with one EVSE, focus on the external equipment. If it occurs with multiple EVSE units, focus on vehicle wiring, inlet, or control electronics.
- Differentiate pending versus confirmed behavior during retesting. Many OBD-II Type B faults need two consecutive trips to store a confirmed DTC and command a warning. In contrast, a hard circuit fault monitored continuously can return immediately on key-on or at plug-in. Use this behavior to separate intermittent contact issues from hard shorts or opens.
- After repairs, clear DTCs and perform a controlled plug-in test. Use a snapshot recording during plug-in and the first minutes of charging to capture any brief CP voltage abnormality. Confirm P1F60 does not return as pending or stored. Recheck for related charging DTCs and confirm the vehicle charges normally.
Professional tip: Do not condemn the charge inlet or a control module from the DTC text alone. Prove the power and ground quality first with voltage-drop under load. Then prove the CP circuit integrity and repeatability with a known-good EVSE. This code points to a suspected trouble area, not a failed part.
Need network wiring diagrams and module connector views?
Communication stop and network faults require module connector pinouts, bus wiring routes, and power/ground diagrams. A repair manual helps you trace the exact circuit path before replacing any ECU.
Possible Fixes
- Remove moisture/contamination from the charge inlet area and restore proper sealing after verifying no terminal damage.
- Repair CP circuit wiring faults, including opens, shorts to ground, or shorts to power, using proper splice methods and harness protection.
- Correct poor terminal fit by repairing connector damage or replacing terminals that fail retention and tension checks.
- Restore clean, low-resistance power and ground feeds by repairing fuse box tension issues, ground points, or corroded connections.
- Replace a damaged charge inlet assembly only after you confirm the inlet-side terminals or internal connections cause the abnormal CP voltage.
- Address EVSE or charge cable problems by using a known-good unit and advising repair or replacement of the faulty external equipment.
Can I Still Drive With P1F60?
You should treat P1F60 on a BYD as a charging-interface fault first, not a normal drivability code. “Abnormal CP voltage” points to the Control Pilot (CP) signal used for AC charging communication. The Atto 3 may drive normally, but charging can fail, stop mid-session, or derate. Do not keep attempting to charge if the connector heats, the charge port shows moisture, or the EVSE repeatedly trips. Avoid high-demand driving if the vehicle reports reduced power or limits HV functions after the fault. If the warning set during charging, disconnect safely, inspect the inlet for damage, and schedule diagnosis.
How Serious Is This Code?
P1F60 ranges from an inconvenience to a mobility problem. When the car drives fine and only AC charging fails, the impact stays moderate. The main risk becomes being unable to recharge. Severity increases if the fault also triggers a “charge system” warning, repeated charging interruptions, or HV system limiting messages. An abnormal CP signal can also result from water intrusion or overheated terminals at the charge inlet. Those conditions can escalate quickly. Address the root cause before regular charging resumes. If the vehicle limits power, or if charging hardware shows melting or discoloration, stop using the charge port and tow it.
Common Misdiagnoses
Technicians often jump to replacing the charge inlet, the charge port harness, or an onboard charger assembly without proving the CP circuit fault. That mistake happens when they treat the DTC text as a failed part, instead of a “suspected trouble area” per SAE J2012 diagnostic intent. Another common error involves ignoring basic checks at the EVSE and charge cable. A damaged EVSE pilot circuit can mimic a vehicle problem. Shops also miss intermittent connector faults because they back-probe with no load. Voltage-drop and wiggle testing under an active charging attempt finds high resistance, poor pin fit, or moisture paths faster.
Most Likely Fix
The most frequent confirmed repair directions for P1F60 involve correcting CP signal integrity at the charge inlet and its harness. Start with verified clean, dry, tight terminals and proper connector seating. Then confirm solid power and ground integrity for the charging control electronics using voltage-drop testing under load. If the wiring and terminals pass, focus on the CP circuit components inside the inlet assembly or the charging control module that monitors CP, but only after you prove the EVSE works on another vehicle and your scan tool shows consistent CP-related live data behavior during a charge request.
Repair Costs
Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.
| Repair Type | Estimated Cost |
|---|---|
| Basic DIY inspection | $0 – $50 |
| Professional diagnosis | $100 – $180 |
| Wiring / connector repair | $80 – $350+ |
| Component / module repair | $120 – $600+ |
Key Takeaways
- P1F60 is BYD-specific and the description “Abnormal CP voltage” drives the diagnosis.
- CP signal issues stop charging more often than they affect drivability.
- Verify the EVSE first so you do not misdiagnose a bad charger as a bad vehicle.
- Inspect the charge inlet closely for moisture, heat damage, and pin fit before replacing parts.
- Use loaded testing (active charge attempt) to catch resistance and intermittent opens.
FAQ
Does P1F60 mean my onboard charger is bad?
No. P1F60 only tells you the BYD system saw abnormal Control Pilot voltage behavior. That points to the CP signal path, not a confirmed failed onboard charger. Prove the basics first: EVSE works on another vehicle, inlet pins look normal, and the CP wire shows continuity and no short to ground or power. Then use live data during a charge request.
What quick checks can I do at home before booking service?
Use a different known-good EVSE and cable first. Inspect the charge inlet for moisture, dirt, bent pins, or signs of heat. Confirm the connector fully latches and does not feel loose. Do not spray lubricants into the inlet. If the fault appears only in rain or after washing, treat it as moisture intrusion and stop charging until a technician checks seals and terminals.
How can a shop confirm the root cause without guessing parts?
A shop should pull freeze-frame and charging-related live data, then reproduce the fault during an active charge attempt. Next, the tech should voltage-drop test power and ground feeds for the charging control circuitry under load. They should also check CP circuit continuity, shorts, and connector pin tension at the inlet and intermediate connectors. Wiggle testing during measurement helps catch intermittent opens.
How do I verify the repair is complete after fixing the issue?
Confirm stable charging over multiple start-stop cycles and at least one full session without interruption. Then re-scan for pending codes after a normal drive and a separate charging event. Enable criteria vary by BYD platform, so use service information to know when the charging diagnostics run. Clearing codes can reset readiness data on some platforms, so confirm all relevant monitors return to a normal completed state.
If my scan tool cannot talk to a charging-related module, what does that mean?
Loss of communication changes the diagnostic path. It can indicate a power, ground, or network issue feeding the charging control module that monitors CP behavior. First, check module wake-up, fuses, and ground integrity with voltage-drop under load. Next, check the network lines for shorts or an open. Restore communication before condemning the module or the inlet, because missing data can mask the real fault.
