LS Swap Tachometer or Speedometer Not Working: Signal, Wiring, and HP Tuners Diagnosis

Decide whether the controller, signal path, or gauge is wrong

An LS-swapped classic may have a dead tachometer, a needle that reads half or double, a speedometer that stays at zero, an erratic display, or a reading that is consistently off. The controller can have accurate rpm and vehicle speed while the dash receives the wrong pulse type or scaling. Alternatively, the controller itself may not see the crank, cam, or vehicle-speed information required for fueling, idle, transmission shifts, diagnostics, cruise control, and fan or torque strategies.

Do not start by multiplying values in the calibration or buying a converter. Identify the engine controller and operating system, transmission, vehicle-speed sensor, reluctor or tone-wheel arrangement, tire diameter, axle ratio, tachometer, speedometer, gauge interface, harness source, and every module that uses the signal. Save the current calibration and wiring documentation before changing anything.

• Record whether the fault began at first startup or after transmission, tire, axle, harness, gauge, or calibration work
• Compare dash rpm and speed with VCM Scanner, a known-good reference tachometer, and GPS speed where legal and safe
• Retrieve all controller and transmission codes, including pending and history status, before clearing them
• Test stationary functions with the vehicle secured; never watch a laptop or programming display while driving

Prove the engine-speed and vehicle-speed data in HP Tuners

Use VCM Scanner to log engine speed, vehicle speed, transmission output speed when supported, selected gear, commanded gear, input speed, throttle, brake state, system voltage, and relevant diagnostic channels. If scanner rpm is stable while the dashboard tach is dead or inaccurate, the crank signal and controller calculation are probably functioning and the diagnostic branch moves toward the configured tach output, wire, interface, ground, and gauge.

For vehicle speed, compare controller speed with a safe external reference at several steady speeds. If the controller remains at zero, inspect VSS type, sensor power and ground, twisted-pair routing, connector terminals, transmission compatibility, reluctor tooth count, signal polarity where applicable, and harness continuity. If controller speed is stable but inaccurate, verify tire rollout, axle ratio, transmission output arrangement, pulses per mile, and every module or converter that alters the signal.

Do not use a speedometer correction table to hide a missing, noisy, or incompatible sensor signal. Automatic-transmission shift timing and diagnostic logic can depend on the same data. Fix the primary signal before adjusting display scaling, and keep a baseline log so a calibration change can be reversed and verified.

Match pulse shape, voltage, frequency, and ground reference

A wire labeled tach or speed does not guarantee that the receiving gauge can interpret it. Determine whether the output is a low-voltage or 12-volt square wave, an alternating sensor signal, an open-collector output that needs a pull-up, a data-bus message, or a configurable controller output. Then confirm the receiving gauge's acceptable voltage, frequency, pulse count, cylinder setting, and input circuit from its manufacturer manual.

Dakota Digital's SGI-100BT documentation addresses speed and tach signal conversion and warns that the interface is not a noise filter. Its guidance also calls for a shared ECU or speedometer ground reference and separates one-wire ECU speed output from two-wire sensor connections. That illustrates why adding an interface cannot repair poor grounds, an open circuit, electromagnetic interference, or incorrect sensor wiring.

Measure power and ground under load, then inspect terminal tension, splices, shielding, pull-ups, connector pin locations, and harness routing. Keep speed and tach conductors away from coils, plug wires, injectors, alternator output, fan motors, relays, and other high-current or high-voltage wiring. Use a scope or frequency-capable meter only with the correct probing method so the test does not short or load the controller output.

Calibrate and validate the complete classic-car integration

Once the signal is clean and compatible, set the gauge or interface for the correct cylinder interpretation and pulses per mile, then correct tire and axle information in every controller that requires it. Chevrolet Performance controller-kit guides identify harness connections and supported system requirements for matched packages; use the guide for the exact kit rather than a generic online pinout. Preserve diagnostic, emissions, and transmission functions while configuring outputs.

Validate cold start, warm idle, gradual rpm sweep, electrical loads, road speed at several steady points, coastdown, transmission shifts, hot restart, and the bumps or heat that previously triggered the failure. Confirm that VCM Scanner, the dash, transmission behavior, cruise or accessory functions, and an external reference agree within the equipment's expected tolerance. Recheck for new codes after the drive.

For LS-powered classics from King George, Fredericksburg, Stafford, Spotsylvania, Dahlgren, Colonial Beach, the Northern Neck, and nearby Southern Maryland, send Ironwake the controller and operating-system IDs, engine and transmission, VSS and reluctor details, tire and axle measurements, gauge and interface manuals, harness pinout, calibration file, codes, scan log, voltage readings, and photos of the installed wiring.