How to Use an OBD2 Scanner: Read and Clear Fault Codes Yourself
Every car sold in the US after 1996 has an OBD2 (On-Board Diagnostics II) port. Plug in a scanner and you can read the exact fault codes causing that check engine light — no dealership visit required. This guide covers everything from picking the right scanner to understanding what the codes mean.
What is OBD2?
OBD2 is a standardized diagnostic system built into every modern vehicle. When the ECU (engine control unit) detects a problem, it stores a Diagnostic Trouble Code (DTC) and lights the check engine warning. The OBD2 port lets you read these codes with a scanner.
Finding the OBD2 Port
The port is always a 16-pin trapezoid connector located within 3 feet of the steering wheel, usually under the dash to the left of the steering column. No need to search under the hood.
Types of Scanners
Bluetooth dongle + phone app (ELM327-based): $10–40. Works with apps like Torque Pro, OBD Fusion, or Car Scanner. Good for reading codes and basic live data. Avoid the cheapest clones — they often crash or disconnect. The recommended chipset is ELM327 v1.5 or vLinker.
Standalone handheld scanner: $50–200. Autel, Launch, Innova brands. No phone needed, stores code history, some support live data graphs and freeze frame data.
Professional bi-directional scanner: $500+. Can command actuators, run active tests, reset service intervals. Autel MaxiSys, Launch X431 series.
For most DIY use, a $30 Bluetooth dongle with OBD Fusion works well.
Reading Fault Codes
- Turn ignition to "on" position (not started, or engine running — both work)
- Plug scanner into OBD2 port
- For Bluetooth: pair to phone, open app, connect to adapter
- Navigate to "Read Codes" or "DTCs"
- Write down all codes before clearing anything
Understanding DTC Format
Every code is a letter + 4 digits:
- P = Powertrain (engine, transmission)
- B = Body (airbags, windows, mirrors)
- C = Chassis (ABS, traction control)
- U = Network (CAN bus communication)
Second digit: 0 = generic OBD2 standard, 1 = manufacturer-specific
Common examples:
| Code | Meaning |
|---|---|
| P0300 | Random/multiple cylinder misfire |
| P0420 | Catalyst efficiency below threshold (Bank 1) |
| P0171 | System too lean (Bank 1) |
| P0442 | Evaporative emission small leak |
| P0016 | Crankshaft/camshaft correlation (Bank 1) |
Live Data / Freeze Frame
Beyond codes, OBD2 provides live sensor readings: coolant temp, RPM, MAF sensor, O2 sensors, fuel trim, throttle position. Freeze frame data captures sensor values at the moment the fault was stored — invaluable for diagnosing intermittent issues.
Clearing Codes
Clearing codes erases the stored DTCs and turns off the check engine light. The codes will come back if the underlying problem isn't fixed. Before clearing: document all codes, note the freeze frame data, and make sure the repair is done.
After clearing, the monitors need to run before an emissions test will pass — usually requires 50–100 miles of mixed driving.
When Not to Clear Codes
- Before taking the car to a shop (they need the codes to diagnose)
- Before an inspection (cleared monitors may cause a fail)
- If the light is flashing (flashing = active misfire, stop driving immediately)