P1F61 – Pulse-Width Modulation (PWM) fault (BYD)

P1F61 means your BYD has detected a problem with a PWM (pulse-width modulated) control signal. In plain terms, a module commanded something on and did not see the expected “on-off” signal behavior. The real-world effect can include reduced power, limited drive modes, or intermittent loss of a controlled function. According to BYD factory diagnostic data, this is a manufacturer-defined code indicating a “Pulse-Width Modulation (PWM) fault.” Because BYD uses manufacturer-specific logic for this code, the exact circuit or actuator involved depends on the platform and the module that set the DTC.

P1F61 Quick Answer

P1F61 on a BYD points to an abnormal PWM signal condition. Diagnose it as a control-signal integrity problem first (command, wiring, connector, and feedback), not as an automatic component failure.

What Does P1F61 Mean?

Official definition: BYD defines P1F61 as “Pulse-Width Modulation (PWM) fault.” That means a control module saw a PWM-controlled output or PWM-based input behave outside its expected pattern. In practice, the vehicle may protect itself by limiting torque or disabling a related function until the signal looks correct again.

What the module actually checks and why it matters: A BYD module monitors PWM by looking at signal presence, duty-cycle plausibility, switching activity, and sometimes circuit feedback. The module expects PWM to change when it commands a change. It also expects the signal to remain stable when loads and operating conditions stay steady. When the module sees a missing signal, stuck-high/stuck-low behavior, excessive noise, or a mismatch between command and observed response, it stores P1F61. That points you toward circuit integrity, power/ground quality, and load behavior under command.

Theory of Operation

BYD uses PWM to control many powertrain devices efficiently. The module switches the control line on and off rapidly. It varies the “on-time” ratio to regulate a motor, solenoid, valve, pump, or converter function. The receiving device averages that switching to produce smooth control.

P1F61 sets when the module cannot trust that PWM control or PWM feedback. Wiring resistance, poor grounds, connector fretting, or water intrusion can distort the waveform. A short to power or ground can pin the signal high or low. An internal driver can also shut down if it senses overcurrent. The DTC tells you the PWM signal did not meet the module’s expected behavior during a monitored test.

Symptoms

Drivers and technicians usually notice one or more of these issues when a BYD logs P1F61.

• Warning message Dashboard powertrain warning and possible “power limited” message
• Limp mode Reduced torque output or restricted acceleration
• Intermittent operation Affected function works sometimes, then drops out
• Harsh engagement Abrupt response when the function resumes or changes state
• Cooling behavior Unusual fan or thermal-management behavior if the PWM relates to heat control
• Charge/regen change Regenerative braking or charging behavior changes if the PWM relates to energy control
• Repeat DTC Code returns quickly after clearing, often during the same command event

Common Causes

• PWM signal wire open or high resistance: A broken conductor or spread terminal distorts duty-cycle information and the BYD controller flags a PWM fault.
• PWM signal short to ground or short to power: A hard short clamps the waveform low or high and the module cannot validate the commanded pulse train.
• Corrosion or moisture in a PWM-related connector: Corrosion increases resistance and creates intermittent contact, which causes unstable PWM frequency or duty cycle.
• Poor power or ground feed to the controlling module under load: Voltage drop at a fuse, splice, ground point, or connector can collapse the module’s output driver and corrupt the PWM pattern.
• Harness chafing near heat or sharp brackets: Insulation damage can intermittently short the PWM circuit when the motor moves or the vehicle vibrates.
• Failed load device on the PWM circuit: A shorted or internally open actuator can pull the circuit out of range and make a good controller appear faulty.
• Incorrect pin fit from prior repairs: Backed-out pins, poor crimping, or aftermarket terminals change circuit resistance and trigger signal plausibility faults.
• Control module output driver or internal monitoring fault: If the wiring and load test good, the module may mis-drive or mis-measure the PWM signal and set P1F61.

Diagnosis Steps

Use a scan tool that can read BYD manufacturer DTCs, freeze frame, and live data. A high-impedance DVOM and a lab scope help confirm PWM integrity. Use back-probing pins and a wiring diagram for the correct PWM circuit. Keep a fused jumper and a test light available for basic load checks.

1. Confirm P1F61 and record DTC status (pending vs confirmed/stored). Save freeze frame data, focusing on battery voltage, ignition state, gear state, vehicle speed, and any companion powertrain or voltage-related DTCs. Freeze frame shows the exact conditions when the fault set.
2. Check fuses, power distribution, and obvious circuit path issues before probing any control module pins. Inspect the underhood and cabin fuse areas for heat damage, loose fuse fit, or aftermarket taps. Perform a quick visual of the harness routing to the suspected PWM-driven device for rub-through or pinch points.
3. Verify the controlling module’s power and ground under load using voltage-drop testing. Load the circuit by turning the related system on, then measure ground drop from module ground to battery negative. Keep ground drop below 0.1 V with the circuit operating. Next, measure power feed drop from battery positive to the module power pin under load.
4. Inspect connectors at the module and at the PWM-controlled device. Look for bent pins, pushed-out terminals, moisture tracks, and green corrosion. Check terminal tension with a proper pin-fit tool or a known-good mating terminal. Repair pin fit problems before any deeper testing.
5. Use the scan tool to identify related data PIDs and run a functional test if available. Command the related actuator or output on and off, then watch for PID changes that indicate the module attempts PWM control. If the scan tool cannot identify the exact output, use service information to map P1F61 to the correct circuit.
6. Back-probe the PWM signal at the load connector and measure for a plausible changing signal while commanding the output. Prefer a lab scope so you can see duty-cycle stability and dropouts. A DVOM duty-cycle function can help, but it can miss glitches. If the waveform disappears during the fault, note whether the signal fails low, high, or becomes noisy.
7. Check the PWM circuit for shorts and opens with the system powered down as required by your test plan. Unplug both ends of the circuit, then test for short-to-ground and short-to-power on the harness side. Next, perform an end-to-end resistance check for opens or high resistance. Do not rely on continuity alone if you suspect an intermittent fault.
8. Load-test the PWM signal and ground return path at the load side. Use an appropriate test light or resistor load only when service information allows it. Watch for signal collapse or excessive voltage drop that indicates a weak connection. Repeat the test while flexing the harness and tapping suspected areas to reproduce the failure.
9. Isolate the load device if the waveform looks wrong. Disconnect the actuator or device and re-check the PWM output at the harness side. A shorted load often drags a good PWM driver out of range. If the PWM returns to normal unloaded, focus on the device and its local wiring.
10. Capture a scan tool snapshot during a road test or on-bay wiggle test if the concern is intermittent. A snapshot is technician-triggered and can catch the moment the PWM drops out. Compare it to freeze frame conditions to recreate the same state. Use this to decide whether vibration, temperature, or load triggers the fault.
11. After repairs, clear DTCs and run the same command tests and operating conditions that set P1F61. Confirm the code stays out and the PWM signal remains stable. Recheck for pending codes after one full drive cycle. If P1F61 returns immediately at key-on, treat it as a hard electrical fault and re-check power, ground, and shorts.

Professional tip: If you suspect a module fault, prove the circuit first. Document clean power and ground voltage-drop results, a stable harness resistance test, and a known-good load. A PWM driver can look failed when a corroded ground forces the output stage into protection. Fix the voltage drop, then retest before considering control module replacement or programming.

Possible Fixes

• Repair open/short in the PWM signal circuit: Restore conductor integrity and insulation where testing proves an open, short-to-ground, or short-to-power.
• Clean and restore connector terminal integrity: Remove corrosion, correct pin fit, and repair backed-out or damaged terminals at the module or load.
• Restore module power and ground quality: Repair fuse contact issues, splices, or ground points that fail voltage-drop testing under load.
• Repair harness routing damage: Correct chafing or pinched sections and secure the loom to prevent repeat faults from vibration.
• Replace the PWM-controlled device only after circuit proof: Replace the actuator or component when it fails isolation tests and drags the PWM signal out of range.
• Control module service after verification: If the circuit and load test good, follow BYD service information for module diagnostics, programming, or replacement.

Can I Still Drive With P1F61?

You can often drive a BYD with P1F61, but you should treat it as a “control signal integrity” warning. A PWM fault means a module does not trust a commanded output or feedback signal. That can change how the powertrain responds. If the vehicle shows reduced power, limited acceleration, warning messages, or unstable throttle response, stop driving and diagnose it. Avoid hard acceleration, towing, and high-speed merges until you confirm the cause. If the code appears with drivability symptoms, repeated limp mode, or multiple powertrain faults, arrange service. Continuing to drive can force protective strategies and create additional codes.

How Serious Is This Code?

P1F61 ranges from a nuisance to a real drivability problem, depending on which PWM-controlled circuit BYD flags on your platform. Some PWM issues only affect a supporting function, such as cooling fan control. Others affect torque management, converter control, or actuator control. In those cases, the module can limit power or disable certain functions to protect the system. Treat the code as more serious when you see overheating risk, frequent limp mode, harsh engagement, unstable idle, or warnings that restrict driving. Treat it as less urgent when the car drives normally and the fault records only as history, but still confirm wiring and connector integrity.

Common Misdiagnoses

Technicians often replace the “suspected actuator” because the code name says PWM fault. That wastes time when the real problem sits in the circuit. High resistance in a connector, water intrusion, or a partially broken wire can distort duty cycle and load feedback. Many also miss ground voltage-drop under load, which can mimic a bad module driver. Another common error involves scoping the signal with the wrong reference ground, which creates a false “noisy PWM” reading. Finally, people clear the code and road test without duplicating enable conditions. That hides an intermittent harness fault and leads to repeat repairs.

Most Likely Fix

The most common confirmed repair directions for a BYD P1F61 PWM fault involve circuit integrity, not immediate module replacement. Start by locating the exact PWM channel tied to the DTC in BYD service information. Then verify power, ground, and connector pin fit at the controlled device and the controller side. Repair corrosion, loose terminals, or harness damage that changes signal quality under load. If the wiring tests clean, confirm the actuator’s current draw and mechanical freedom. Only after those checks should you consider a failed actuator or a controller output driver fault, followed by any required programming.

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.

Last updated: March 30, 2026