LS Swap Surging or High Idle: Use Fuel Trims and Scan Data Before Tuning

Separate a mechanical fault from a calibration problem

An LS-swapped classic that idles high, hunts, stalls when placed in gear, hangs between shifts, or needs throttle to stay running is not automatically asking for more idle airflow or different spark tables. Unmetered air, low or unstable fuel pressure, incorrect injector data, crossed oxygen-sensor wiring, exhaust leaks, weak grounds, throttle-body trouble, incorrect coolant-temperature input, camshaft overlap, and base-engine faults can produce similar behavior.

Record what changed and when the symptom occurs: cold start, fully warm, after a hot soak, air conditioning on, steering loaded, transmission in gear, deceleration, or only after a flash. Confirm the engine, controller, operating system, throttle type, injectors, sensor part numbers, fuel system, camshaft, and calibration actually belong together before editing tables.

Build a focused VCM Scanner log

HP Tuners documents that VCM Scanner channels are the data inputs used by its graphs, gauges, and charts, and that excessive polled channels can slow the scan. A useful idle log is focused enough to show cause and response at the same time. Save the original file, calibration, channel configuration, and the exact test conditions so each change can be compared against a repeatable baseline.

Channel availability varies by controller. A practical starting set may include engine speed and desired idle, throttle position or effective area, pedal position for electronic throttle, manifold pressure, mass airflow, intake-air and coolant temperature, battery voltage, short- and long-term fuel trims by bank, oxygen-sensor or lambda data, commanded equivalence ratio, ignition advance, injector pulse width, idle-control state, vehicle speed, gear or range, brake input, and diagnostic trouble codes. Use a properly integrated wideband only when its signal and transform have been verified.

• Capture cold start, warm idle in park, warm idle in gear, and the exact transition that produces the complaint
• Mark accessories, fan operation, steering load, brake input, gear changes, and throttle events in the log notes
• Avoid changing several tables between logs because the result will not identify which change mattered
• Do not disable diagnostic codes or emissions controls to make a warning or fault disappear

Read fuel-trim patterns as evidence, not instructions

Positive fuel trims mean the controller is adding fuel relative to its current calculation; negative trims mean it is subtracting fuel. The pattern matters more than one number. A concern strongest at idle that improves with rpm can support an unmetered-air investigation. Similar error at idle and cruise can point toward shared inputs such as fuel pressure, injector characterization, airflow measurement, or exhaust and oxygen-sensor integrity. A large difference between banks suggests a bank-specific leak, injector, sensor, exhaust, or mechanical issue.

Fuel trims do not prove which component failed, and closed-loop correction can temporarily mask the base error. Smoke testing must use equipment and pressure appropriate for the intake system. Inspect the intake, throttle body, brake-booster supply, PCV plumbing, purge circuit, manifold seals, injector seals, vacuum accessories, exhaust ahead of the sensors, sensor placement, and harness routing. Measure fuel pressure under the condition that produces the symptom rather than only with the key on.

Verify idle control before touching idle tables

For cable-throttle systems, confirm blade position, stop setting, idle-air-control passages, IAC behavior, linkage return, and that no cruise or kickdown hardware is holding the throttle open. For electronic throttle, verify pedal and throttle signals, connector and power integrity, learned position procedures, and that the throttle body and calibration are compatible. Check commanded idle against actual rpm before assuming the controller is requesting the speed you see.

Only after compression, ignition, air leaks, fuel delivery, sensors, wiring, grounds, exhaust integrity, and hardware identity pass should calibration work begin. Then change the smallest relevant set of supported parameters, log the result, and retain the known-good file. The objective is stable cold start, hot restart, idle in gear, accessory recovery, deceleration, and street operation—not one smooth moment in the shop.

Bring the log and the build record together

Classic LS-swap owners in King George, Fredericksburg, Stafford, Spotsylvania, Dahlgren, Colonial Beach, the Northern Neck, and nearby Southern Maryland should send the year and model of the classic; engine casting or crate-engine details; controller and harness; calibration source; throttle type; injectors; fuel pressure; camshaft; intake and exhaust; transmission and converter; axle ratio and tire size; codes; and the original HP Tuners log.

Ironwake evaluates the scan alongside the installed vehicle: grounds, power distribution, fuel system, intake plumbing, exhaust and oxygen sensors, cooling, transmission inputs, and calibration. That system-first process keeps a classic-car build from accumulating software workarounds for hardware that still needs correction.