P0691 Code: Fan 1 Control Circuit Low Diagnosis
P0691 Diagnosis: Prove the Fan 1 Control Circuit
The controller detected a low electrical condition in the Fan 1 control path. Save the event, identify the architecture, and test before replacing parts.
P0691 means Fan 1 Control Circuit Low. The reporting controller saw an electrical result below the calibrated expectation in the primary cooling-fan control path.
P0691 does not prove that the fan motor is bad. Save the event, identify the fan architecture, then prove the circuit with OEM information and physical tools.
What Does the P0691 Code Mean?
P0691 is the standardized OBD-II description for Fan 1 Control Circuit Low. It concerns the electrical control path for the fan identified as Fan 1 by the exact vehicle—not coolant temperature performance by itself.
Low describes the monitored circuit result. It does not mean low fan speed, low coolant, or a universal voltage threshold. Ford documents one relay-based strategy in which P0691 can represent an open circuit or short to ground. A Volvo monitor example identifies a short-to-ground condition while the actuator is below full duty. Those rules cannot be transferred to every vehicle.
Vehicles may switch relays or command an electronic fan module. “Fan 1” can mean a control channel, not a visible fan position.
Prioritize overheating risk, high-current power, grounds, fuses, relays, module feed, and the control path.
A fail-safe response can coexist with a low control-circuit code; identify the command and feedback architecture.
Check system voltage, shared powers, grounds, connectors, and controller feeds before isolating one branch.
P0691 Symptoms, Severity, and Driving Safety
P0691 may be current, pending, history, or permanent, with a related controller storing better detail.
A low control-path fault can prevent the expected fan command from reaching a relay or module.
Some systems use full fan speed as a protective default when command or feedback is unreliable.
Airflow loss is often most visible in traffic, during a long idle, or under high thermal load.
Condenser airflow may fall when the fan cannot respond to an A/C-related demand.
An intermittent terminal or control wire can set P0691 before cooling performance changes.
Severity depends on fan operation and coolant temperature; highway airflow can mask an idle cooling problem.
Common Causes of the P0691 Code
These are diagnostic branches, not failure percentages. Start with stored evidence and shared electrical conditions.
Low System Voltage or Shared Feed/Ground Fault
Weak voltage, a poor main ground, or a disturbed controller feed can affect more than one monitored output.
How to prove it: Review companion codes, then load-test VIN-correct powers and grounds.
Check firstOpen or Shorted Relay-Control Circuit
A relay coil path, fuse-box terminal, socket, or control wire may be open or shorted to ground.
How to prove it: Map the exact relay logic and test the coil feed, control, terminal fit, and driver safely.
Check firstChafed, Corroded, or Loose Harness Connection
Heat, vibration, water, road damage, poor routing, or spread terminals can pull the command or feedback path low.
How to prove it: Inspect likely rub points and perform terminal-tension and loaded circuit tests.
Verify directlyFailed Relay or Electronic Fan-Control Module
Contacts, coil electronics, an integrated driver, or internal diagnostic circuitry can fail.
How to prove it: Compare command, control signal, module powers/grounds, and output under the OEM procedure.
Verify directlyFan Motor or High-Current Path Problem
A seized motor, excessive current, poor high-current connection, or damaged assembly may affect an integrated system.
How to prove it: Measure the load and voltage drop with rated tools; do not infer motor failure from P0691 alone.
Verify directlyPCM/ECM Driver, Connector, or Software Fault
A damaged driver, connector, feed, or application-specific calibration issue belongs late in the path.
How to prove it: Prove the circuit and load first, then follow VIN-specific module tests and service information.
Final branchRecent work changes the order. If P0691 began after radiator, fan, front-end, battery, fuse-box, A/C, engine, or harness work, inspect the disturbed connectors, grounds, routing, fasteners, and part identity first.
Can UR1000 Help Diagnose the P0691 Code?
The iCARZONE UR1000 Bidirectional Scan Tool with ECU Coding can preserve supported DTCs, freeze frame, live data, history, and reports. Compare the exact ECU's temperature, fan command, A/C demand, voltage, and feedback PIDs.
The official product page lists full-system diagnostics, live data, active bidirectional control, 50 service functions, CAN-FD/DoIP capability, and ECU coding. It also lists cooling-fan active tests among common component controls. Coverage varies by make, model, year, VIN, ECU, and software. Confirm the exact fan command, PID, or test before relying on it.
UR1000 cannot measure continuity, terminal tension, relay contacts, voltage drop, PWM waveform, fan current, motor drag, or coolant pressure. Those checks need the wiring diagram and suitable physical tools.
iCARZONE UR1000 Bidirectional Scan Tool with ECU Coding
Preserve the P0691 event, identify companion modules, and organize supported command-versus-response evidence before unplugging the fan circuit.
Price and availability checked August 26, 2026. Available for sale when checked; recheck price, stock, and exact VIN/function coverage before purchase.
How to Diagnose P0691 Code in 6 Steps
Work from the saved event to circuit identity, shared conditions, inspection, scan evidence, and loaded electrical proof.
P0691 Quick Diagnostic Path
-
1
Save the Complete P0691 Diagnostic Event
- Record P0691 status, all-module codes, freeze frame, battery voltage, coolant temperature, fan command, A/C state, speed, and a report where supported.
- Note overheating, full-speed or inoperative fans, weak idle A/C, recent repairs, and the exact condition that set the warning.
-
2
Identify Fan 1 and the Exact Control Architecture
- Use the VIN, engine, full OEM DTC text, wiring diagram, fuse/relay map, connector views, and controller identity.
- Determine whether Fan 1 uses a discrete relay, several speed relays, a PWM module, a communication line, or an integrated assembly.
-
3
Triage Overheating, Voltage, and Companion Codes
- Stop for an active overheat condition. Check coolant level only when safely cold, and inspect battery/charging state, fuses, shared feeds, and grounds.
- Prioritize P0480/P0483, P0692, system-voltage, ECT, A/C-pressure, communication, or second-fan codes according to the OEM tree.
-
4
Inspect Relays, Connectors, Harness Routing, and the Fan
- Check locks, seals, terminal fit, corrosion, heat, melting, water, rub-through, loose attachments, and previous splices.
- Inspect the fan for obstruction or damage with power isolated; never place hands near an automatic fan that could start.
-
5
Compare Supported Commands and Prove the Physical Circuit
- Graph supported temperature, fan command, feedback, A/C request, and voltage data; run a fan test only where the exact vehicle supports it.
- Use a meter, fused load, current clamp, or scope as the OEM procedure requires to test feeds, grounds, relay control, PWM/communication signal, voltage drop, and load current.
-
6
Repair the Proven Branch and Rerun the Monitor
- Repair only the confirmed terminal, wire, fuse-box connection, relay, module, motor/load, feed, ground, or controller cause.
- Clear eligible codes, repeat the original enable conditions, verify fan response and coolant control, and confirm P0691 does not return.
How to Fix P0691 and Confirm the Repair
Restore Shared Power and Ground Integrity
Correct proven battery, charging, fuse, high-current feed, controller-feed, or ground voltage-drop faults with rated connections.
Repair the Control Harness and Terminals
Repair confirmed opens, shorts to ground, chafing, corrosion, loose pins, melted sockets, or poor routing with sealed, strain-relieved methods.
Replace the Proven Relay, Module, or Fan Assembly
Match the exact architecture; some controls are separate while others are integrated with the fan and require assembly-level service.
Address the PCM/ECM or Software Last
Repair controller connections or apply validated module service/programming only after the command circuit, load, powers, and grounds pass.
Scan and Circuit Diagnosis
VIN-specific quoteFailure reproduction, wiring access, relay/module identification, loaded tests, waveform checks, and companion-code analysis.
Connector or Harness Repair
VIN-specific quoteRub-point location, terminal availability, fuse-box access, wire gauge, sealing, routing, and heat damage.
Relay, Module, or Fan Assembly
VIN-specific quoteSeparate versus integrated control, front-end access, refrigerant/radiator clearance, fan count, and calibration needs.
Controller or Programming Work
VIN-specific quoteModule access, stable power support, security authorization, programming, setup, and post-repair verification.
Costs vary by architecture. Ask for a quote naming the proven cause and verification plan.
After repair, reconnect every protective cover and connector, save a clean report, clear eligible codes, and reproduce the original command conditions. Confirm normal fan response, stable coolant temperature, working idle A/C where applicable, and no returning code.
P0691 Differences by Cooling-Fan Architecture
The OEM text and diagram control Fan 1 identity, relay position, wire function, and test values.
The controller may ground or power a relay coil and monitor the driver. An open coil path and a short-to-ground branch may share P0691 on some strategies.
A module may receive constant high-current power plus PWM or data command. Control-line condition, module power, and motor current are separate questions.
Fan 1 can be a control channel or primary function. Series/parallel relays and shared feeds change which physical fan responds.
Ford, Volvo, and Audi examples use the same label but different hardware and monitor logic. Follow current service information for the exact VIN.
- Save codes, freeze frame, and a diagnostic report before disconnecting anything.
- When cold and powered down, inspect visible fuses, grounds, connectors, routing, and rub points.
- Confirm the VIN-specific fan architecture and fuse/relay labels from reliable information.
- Graph supported temperature and fan-command data without unsafe distraction.
- Load-test high-current feeds/grounds and measure fan current with rated equipment.
- Back-probe PWM, communication, or controller-driver circuits without damage.
- Work near hot, pressurized cooling or A/C components and automatic fans safely.
- Diagnose a suspected controller driver and perform required programming or setup.
Frequently Asked Questions About P0691
What does the P0691 code mean?
Does P0691 mean the cooling fan motor is bad?
Can I drive with a P0691 code?
Why is the cooling fan running at full speed with P0691?
Can a blown fuse or bad relay cause P0691?
How is P0691 different from P0480 or P0483?
Can UR1000 help diagnose P0691?
Why did P0691 return after replacing the fan?
Sources and Technical Review Notes
- SAE J2012DA: Diagnostic Trouble Code Definitions — Maintains the standardized DTC vocabulary used for P0691.
- Ford 2017 Model-Year OBD System Operation — Documents one relay-based P0691 monitor and shows why open/short-to-ground logic is architecture-specific.
- NHTSA-Hosted Volvo Group 28 Monitor Documentation — Gives a different duty-dependent circuit-low monitor example.
- NHTSA-Hosted Audi TSB 2072000/1 — Shows a limited 2020–2024 Q7/Q8-family harness-chafe example; it is not a universal cause.
0 comments