P2CBC

Code

Generic P — Powertrain

Fan 3 Overspeed

Brand: Generic

Type: P — Powertrain

Views: UK: 18 EN: 31 RU: 20

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Faulty fan motor running above nominal speed
Short or fault in the fan tachometer/feedback circuit (false high signal)
Incorrect PWM/drive signal from fan control module or ECM
Faulty fan control module / body control module / engine control unit
Intermittent wiring short to battery or noise on the feedback line
Aftermarket or incorrect replacement fan with different tachometer characteristics

Symptoms

Cooling fan #3 running at full/high speed whenever commanded or unexpectedly
Loud fan noise or high-pitched whine from the fan area
Check Engine Light or MIL on with P2CBC stored
Possible lower-than-normal engine temperature or inconsistent cooling performance
Intermittent operation of HVAC or A/C cooling if fan behavior is abnormal

What to check

Scan for related freeze frame data and any other stored fan-related codes (P0480-P0483 family)
Visually inspect fan 3, connector, and wiring for damage, corrosion, or loose pins
With ignition on (engine off), command fan on/off with a scan tool and observe response
Measure supply voltage to the fan when commanded (should be battery voltage or PWM present)
Check tachometer/feedback signal at the fan connector with an oscilloscope or frequency-capable multimeter
Compare commanded drive (PWM duty/frequency) vs actual tach feedback to identify mismatch

Signal parameters

Battery supply voltage to fan: ~12–14.5 V when commanded
Control signal: PWM duty cycle and frequency (manufacturer-dependent; typically 100 Hz to several hundred Hz)
Tachometer/feedback: pulse frequency proportional to RPM (pulses per rev varies by design)
Over-speed threshold: tach feedback exceeds allowed RPM by manufacturer threshold (commonly >10–20% over expected or specific RPM limit)
Ground continuity: low resistance between fan ground and vehicle chassis

Diagnostic algorithm

Safety: park on level ground, ignition off, key out, and disconnect battery if required before wiring repairs. Observe fan blades—do not probe while spinning.
Read and record all stored codes, freeze frame and live data with a scan tool. Note conditions when code set.
Visually inspect Fan 3, mounting, wiring harness, and connector for damage, fluid contamination, or corrosion.
Using a scan tool, command Fan 3 on and off; observe whether the module command matches actual fan speed/operation.
Measure supply voltage to the fan while commanded on. Verify proper ground. Repair any low-voltage or poor-ground issues.
Probe the tachometer/feedback line with an oscilloscope or frequency meter while the fan is running. Confirm signal amplitude, frequency, and pulse shape match expected characteristics. Look for noise or multiple spurious pulses.
Probe the control/PWM output from the control module to ensure it is not providing an abnormal drive signal causing overspeed.
If wiring and control outputs are good, bench-test the fan by applying the correct supply and observing speed and feedback. Replace fan if it runs overspeed on bench test.
If fan is good, suspect control module. Check for software updates or known issues; replace or reprogram control module if confirmed faulty.
After repair, clear codes and perform a verification run to ensure the code does not return under normal operating conditions.

Likely causes

Failed fan assembly (most common)
Damaged or corroded connector or wiring on the tach/feedback line
Control module commanding improper drive frequency or stuck high
Open or shorted tachometer pickup creating spurious high-frequency pulses

Fault status

⚠️ Status

Fan 3 Overspeed (P2CBC) — the control module has detected that the feedback/tachometer signal from cooling fan #3 is above the allowed RPM threshold. This may be caused by a faulty fan, incorrect feedback signal, driver malfunction, or wiring fault. Diagnostic steps should verify power, ground, control signal, and feedback integrity before replacing components.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 0.5-2.0 hours