Diagnosing ABS Warning Light

What the ABS Light Actually Means

An illuminated ABS warning light means the ABS module has detected a fault and taken the anti-lock braking system offline. The vehicle still has normal hydraulic brakes — pressing the pedal still pushes fluid to the calipers and you can still stop the vehicle. But anti-lock braking, traction control, and electronic stability control are all disabled, because all three systems depend on the ABS hardware and wheel speed sensor data to function.

This is not a light you can drive around with indefinitely and plan to address eventually. A vehicle without ABS, traction control, and stability control behaves differently in emergency situations. In a panic stop, the wheels can lock and the vehicle goes straight — you lose the ability to steer around an obstacle. On slippery surfaces, you lose the electronic assists that prevent skids. These are real safety consequences, not hypothetical ones.

Some drivers mistake the flashing ABS light during normal driving for a fault. The ABS indicator flashing while the vehicle is in motion — during braking on a slippery surface or during hard braking — means the system is actively intervening. This is normal operation. The system is working. A steady illumination or a light that comes on and stays on means there is a fault. Make sure you and the customer are talking about the same behavior before you start the diagnosis.

Step One — Scan the Right Module

Connect a scan tool that communicates with the ABS module. This is not optional and it is not something you can skip. A code reader that only reads engine codes will show you nothing useful for an ABS diagnosis. The ABS module is a separate electronic control unit with its own communication bus, its own fault memory, and its own diagnostic data stream. Without a tool that can access it, you cannot read the codes that tell you what the module actually detected.

Professional scan tools with full vehicle coverage — the type used in professional shops — communicate with every module on the vehicle including ABS, airbag, body control, transmission, and more. When you connect to the ABS module, you can read stored fault codes, view live wheel speed sensor data for all four wheels simultaneously, and use bi-directional control functions to command ABS components on and off for testing.

Read every ABS code stored before clearing anything. Note the code number, the fault description, and whether the code is current (present fault) or stored (historical fault). A current code means the fault is happening right now. A stored code means it happened at some point since the last time codes were cleared. Both are useful. Do not clear codes before you have written down everything the module has stored — you may need that history to understand an intermittent concern.

Most Common Codes — Wheel Speed Sensors

The majority of ABS codes across all makes and models are wheel speed sensor related. The ABS system depends entirely on accurate wheel speed data from all four corners to calculate when a wheel is about to lock during braking. When a sensor fails, produces an erratic signal, or loses signal entirely, the ABS module disables the system to prevent incorrect anti-lock interventions based on bad data.

An erratic signal code for a specific wheel — where the sensor is producing a signal but it is not clean or consistent — points to the sensor, the tone ring, or the wiring. Inspect the tone ring at that wheel for missing teeth, rust buildup between teeth, or debris packed in the gaps. Inspect the sensor mounting for the correct air gap — too much gap between the sensor face and the tone ring reduces signal strength and causes erratic readings. Inspect the sensor wiring from the sensor to the harness connector for chafing damage — the wiring at each wheel is constantly flexing with suspension movement and eventually cracks near the sensor or near a rigid harness support point.

A no-signal code for a specific wheel means the sensor has lost signal completely. The wiring is open, the connector is corroded or disconnected, or the sensor has failed. Check the connector first — a disconnected or corroded connector at the wheel speed sensor is a two-minute fix. Check continuity of the wiring from the connector to the module connector. On passive sensors, test resistance across the two sensor terminals — an open reading means the sensor coil has failed. On active sensors, verify the module supply voltage at the connector with the ignition on, then scope the signal while rotating the wheel slowly.

Before replacing any wheel speed sensor for an erratic signal code, grab the tire at 12 and 6 o'clock and check for bearing play. Excessive wheel bearing play causes the tone ring to wobble relative to the sensor as the bearing moves under load. The sensor sees an erratic signal from the wobbling ring — not from a failed sensor. Replace the bearing and the erratic signal code will not return. Replace the sensor without checking the bearing and the new sensor will produce the same erratic signal code from day one.

ABS and Red Brake Light Together

When both the amber ABS warning light and the red brake warning light illuminate simultaneously, the situation is potentially more serious than a simple sensor fault. The combination of both lights can indicate several distinct conditions.

Check the brake fluid reservoir level immediately. If the fluid is low — below the minimum mark — the reason is almost always that the front or rear brake pads have worn thin enough that the caliper pistons have extended significantly, displacing fluid from the reservoir into the caliper bores. Low fluid is a visual confirmation that brake pad inspection is urgent. The low fluid level sensor in the reservoir triggers the red brake light, and a pressure imbalance or loss of fluid can affect ABS module function.

Both lights can also indicate a more serious internal fault in the ABS hydraulic control unit or the module itself — a condition the module considers severe enough that it is not confident in the base hydraulic brake function. Scan the ABS module and look for pump motor codes, pressure switch codes, or solenoid circuit codes. These point to internal HCU faults rather than wheel sensor issues.

On some vehicles, a failing lateral accelerometer or yaw rate sensor sets both the ABS light and a separate stability control warning simultaneously — but the brake light may also be tied to stability control on certain platforms. Read every chassis module before concluding what set both lights.

Intermittent ABS Light

An ABS light that comes on during driving and then goes off — sometimes after a restart, sometimes on its own — is almost always a wiring or connection problem. The fault occurs when the wiring harness is in a specific position and clears when the harness moves back. Common triggers: turning left or right, going over bumps, acceleration or deceleration that shifts the harness position.

The ABS module stores the fault even when the light clears. Connect the scan tool and read stored codes. The code will name the specific wheel or circuit that faulted. That tells you which corner of the vehicle to focus on. Go to that wheel speed sensor and wiggle-test the wiring harness while watching live wheel speed data on the scan tool. Have someone watch the scan tool data while you flex and wiggle the harness from the sensor to the first rigid support point, and then from the support point up into the body harness. The sensor that drops signal or produces erratic data during the wiggle has the wiring fault.

Do not replace the sensor for an intermittent code without confirming the sensor itself is the problem. A cracked wire one inch away from the sensor connector causes the same code and the same behavior as a failed sensor — but replacing the sensor leaves the cracked wire in place and the customer returns with the same complaint in three weeks.

HCU and Pump Motor Faults

The ABS hydraulic control unit contains the solenoid valves that modulate brake pressure to each wheel during an ABS event, the pump motor that returns fluid during modulation, and the pressure switch or accumulator that monitors system pressure. Faults in any of these components produce ABS codes that are distinct from wheel speed sensor codes.

A pump motor code — motor circuit open or motor does not run during self-test — requires testing the motor circuit directly. The ABS module commands the pump motor on during its initial system self-test, usually as soon as the vehicle starts moving above a few miles per hour. If the motor does not run, check for power and ground at the pump motor connector during the self-test period. If power and ground are present and the motor does not run, the motor has failed. If power or ground is missing, trace the circuit back through the relay and module output.

Solenoid circuit codes — open or shorted solenoid circuits — usually indicate a wiring problem or a failed solenoid within the HCU. These are more complex to diagnose and often require resistance testing of each solenoid circuit at the HCU connector. An HCU with a failed internal solenoid typically requires replacement of the entire HCU assembly — individual solenoids are not serviceable on most modern systems.

Before condemning an HCU based on solenoid codes, always verify the wiring between the module and the HCU connector is intact. A corroded multi-pin connector at the HCU with intermittent continuity on a solenoid pin will set the same code as a failed solenoid inside the unit. Clean and inspect the HCU connector thoroughly before recommending an HCU replacement.

The Bottom Line

ABS diagnosis requires the right scan tool, the right module, and a systematic approach. Scan the ABS module first — every time. Read all stored codes. Most codes point to wheel speed sensors and most wheel speed sensor problems trace to wiring, connectors, tone rings, or bearings — not the sensors themselves. Check the bearing before replacing the sensor. Check the wiring before replacing anything. Both lights on means check the fluid and check for HCU-level faults. Intermittent light means stored codes and a wiggle test. Follow the code, follow the circuit, and do not replace parts the code did not point to.