LS Swap Electric Fans Not Turning On: Wiring, Commands, and HP Tuners Diagnosis

Separate an overheating problem from a fan-control problem

Before changing fan temperatures, confirm the complaint with trustworthy data. The dash gauge, ECU coolant-temperature value, infrared measurements at accessible metal surfaces, and actual coolant behavior may not agree. Stop the engine for steam, rapid coolant loss, severe pressure, abnormal noise, a collapsed hose, or a temperature that continues climbing toward the engine or controller manufacturer's limit. Never remove a pressure cap while hot.

Define whether neither fan runs, only one stage fails, a fan runs with direct power but not from the ECU, the fans run too late, they cycle rapidly, they work with air conditioning but not temperature, or they spin correctly while the engine still overheats. The last condition returns the diagnosis to radiator capacity, shrouding, airflow direction, coolant flow, trapped air, pressure control, ignition, fueling, combustion leakage, or vehicle aerodynamics rather than fan command alone.

• Record ECU coolant temperature, dash indication, vehicle speed, fan-command state, A/C request, battery voltage, and when the symptom begins
• Identify the ECU, operating system, harness, relay or fan-control module, fan part numbers, radiator, shroud, thermostat, and calibration source
• Confirm whether the system is designed for discrete low/high relays, two individual fans, series/parallel control, pulse-width control, or an aftermarket controller
• Do not command a fan continuously until its wiring, fuse, relay, conductor size, connector, and duty rating are known

Prove the high-current fan circuit before blaming calibration

Use the wiring diagram for the exact harness or controller. Verify the main fuse, fan fuse, relay terminal functions, battery feed, switched or constant relay-coil feed as designed, ECU low-side or high-side trigger strategy, motor ground, and connector condition. Many LS controllers ground a relay coil rather than supplying fan-motor power directly; applying motor current to an ECU control wire can damage the controller.

A fan that spins on the bench can still fail in the vehicle. Measure voltage at the motor and voltage drop across the complete positive and ground paths while the fan is loaded. Inspect crimp quality, terminal tension, heat damage, corrosion, undersized conductors, poor chassis grounds, fuse-holder resistance, and relays whose contacts close but cannot carry current. Confirm both fans rotate in the intended direction and move air through the radiator toward the engine on a conventional front-engine arrangement.

Use an appropriately fused test method only when the manufacturer procedure calls for it. Never bypass overcurrent protection, substitute a larger fuse to stop it from opening, or bridge unfamiliar relay terminals. Fan start-up current can be far higher than steady-state current, and a circuit that survives an unloaded test may overheat in normal operation.

Use scan data to follow request, command, and response

In VCM Scanner or the diagnostic platform appropriate to the installed ECU, log engine coolant temperature, intake-air temperature, system voltage, vehicle speed, A/C request and pressure if supported, fan requested or commanded states, related diagnostic trouble codes, and any output-control results. Plausibility comes first: a coolant sensor reading that is implausibly cold, hot, fixed, or intermittent can prevent the expected decision or create an unsafe one.

If the scanner can command fan outputs, follow HP Tuners and controller-specific instructions and keep the test brief. A successful commanded-output test proves more than a static relay click because it exercises the controller path, but it does not automatically prove full motor current, airflow, or correct temperature thresholds. If command state changes and the relay coil responds but the motor does not, remain in the power circuit. If the command never changes despite plausible temperature, inspect calibration, operating-system support, pin assignment, conditions that inhibit the output, and harness compatibility.

Air-conditioning behavior can add useful evidence. Some systems request a fan based on A/C pressure or state, while others need a discrete request input or separate controller. Do not assume the original classic-car A/C wiring and an LS ECU understand each other. Document the requested behavior before adding a pressure switch, trinary switch, relay logic, or calibration change.

Set thresholds only after the hardware and thermostat are matched

Fan-on and fan-off temperatures need intentional separation so the relays do not chatter and the fans have time to change coolant temperature. The correct values depend on the thermostat, sensor location, engine and controller strategy, radiator and shroud, fan capacity, A/C system, vehicle speed logic, and whether the calibration expresses temperatures directly or through tables. Copying a screenshot from another build can create constant fan operation without solving poor airflow.

After a change, validate from a cold start through thermostat opening, stationary heat soak, A/C operation, low-speed driving, highway operation, key-off behavior, and hot restart. Confirm stable charging voltage with both fans and other loads operating, no overheated terminals, correct fan direction, controlled temperature, and no new codes. Save the original file, record every change, and retain a recovery path.

For LS-powered classics around King George, Fredericksburg, Stafford, Spotsylvania, Dahlgren, Colonial Beach, the Northern Neck, and nearby Southern Maryland, Ironwake can test the cooling hardware, harness, relay strategy, sensor data, and calibration as one system. Send the engine and ECU identifiers, harness and fan part numbers, wiring diagram, radiator and thermostat details, current tune source, logs, codes, and the exact condition in which fan control fails.