How to Use an OBD2 Scanner (Step by Step)
In this guide
- Before you start
- Step 1: Find the port
- Step 2: Connect with the ignition off
- Step 3: Read every code, and write them down
- Step 4: Save the freeze frame
- Step 5: Check readiness monitors
- Step 6: Look at live data (optional but useful)
- Step 7: Fix first, clear second
- Putting the results together
- Common mistakes
- Which scanner for these steps
Using an OBD2 scanner takes about five minutes: find the 16-pin port under the driver’s side of the dash, plug the scanner in with the ignition off, turn the key to on without starting the engine, read every code, save the freeze frame data, check readiness monitors, and only then decide whether to clear anything. The order matters more than the tool. Clearing first erases the evidence a mechanic, or you, will need. The steps below follow the standard OBD2 functions every 1996 and newer US car supports and the procedure printed in typical scanner manuals; your scanner’s manual and your vehicle’s service information win where they differ.
Disclosure: As an Amazon Associate I earn from qualifying purchases. Some brands featured below pay a bonus commission through Amazon Creator Connections. See /disclosure/.
Before you start
- Confirm the car has OBD2. EPA’s owner guidance is that all 1996 and newer cars and light trucks sold in the US use second-generation on-board diagnostics. Older cars need an OBD1 tool or a make-specific reader; see OBD2 vs OBD1.
- Note how the light is behaving. A steady check engine light means a fault has been detected. A flashing light, per EPA, means a severe problem such as a misfire that can damage the catalytic converter: minimize driving, avoid high speed and heavy loads, and get it diagnosed promptly. Federal rules require the light to blink once per second when catalyst-damaging misfire is occurring. See check engine light flashing.
- Check the gas cap. EPA’s brochure names a loose or missing gas cap as a common cause of a steady light. Tighten it, and if the light stays on after a few drives, scan it.
- Park safely. Flat ground, parking brake on, transmission in Park or neutral, and keep clear of belts and fans if you will run the engine.
Step 1: Find the port
The diagnostic connector is a 16-pin, trapezoid-shaped socket. Federal rules require it to meet SAE J1962, and scanner manuals describe the usual location as under the dashboard on the driver’s side, roughly a foot from the center of the instrument panel. The ANCEL AD310 manual adds that if it is not under the dash, a label should show where it is, and that some cars put it behind an ashtray or panel. If you still cannot find it, the owner’s manual lists it. OBD2 port location has a make-by-make list.
Step 2: Connect with the ignition off
Most corded scanner manuals say not to connect or disconnect the tool with the ignition on or the engine running. The sequence they print is:
- Ignition off.
- Plug the scanner firmly into the port.
- Turn the ignition to on (dash lights up) without starting the engine.
- Let the scanner power up and detect the protocol.
For a Bluetooth adapter, plug it in the same way, turn the ignition on, then pair it in the app (not always in the phone’s Bluetooth settings; follow the app’s instructions).
If the tool shows a link error, the AD310 manual’s checklist is a good general one: confirm the ignition is on, reseat the connector, confirm the car is OBD2 compliant, then turn the ignition off, wait about 10 seconds and try again.
Step 3: Read every code, and write them down
Select “Read codes” or “Diagnose”. A basic tool shows:
| Code type | What it means | Light on? |
|---|---|---|
| Stored (confirmed) | Fault detected and confirmed | Yes |
| Pending | Fault seen in the current or last drive cycle, not yet confirmed | Often not yet |
| Permanent (newer vehicles) | A record the scan tool cannot erase; clears after the car’s own monitor passes | Yes, until the repair is verified |
Write down every code with its exact letters and numbers, or take a photo of the screen. P codes are powertrain, B body, C chassis and U network; the format follows SAE J2012, which federal rules require. A code names the system and the condition the computer saw, not the part to replace. P0420, for example, reports catalyst efficiency below threshold, which can be a catalytic converter, an oxygen sensor or an exhaust leak. See P0420, P0300 and P0171 for the common ones.
Step 4: Save the freeze frame
Freeze frame is the snapshot the car stores when a fault first sets. Under 40 CFR 86.1806-05 it must include engine speed, open or closed loop status, fuel system commands, coolant temperature, calculated load, fuel pressure, vehicle speed, air flow and intake manifold pressure where the computer has them, and a later misfire or fuel system fault replaces an earlier snapshot. Those numbers tell you whether the fault set cold or hot, at idle or on the highway, which is often the fastest way to the cause. Save or photograph it. Freeze frame data explains how to read each value.
Step 5: Check readiness monitors
Readiness monitors show whether the car’s emission self-tests have completed since the last code clear or battery disconnect. Misfire, fuel system and comprehensive component monitors run continuously; catalyst, EVAP, oxygen sensor, oxygen sensor heater, EGR and secondary air run only under specific driving conditions, per the AD310 manual.
This step matters most before an emissions inspection. Under the federal OBD test procedure in 40 CFR 85.2222, a model year 1996 to 2000 vehicle may pass with two or fewer unset monitors and a 2001 or newer vehicle with no more than one; states can be stricter. California’s Bureau of Automotive Repair, for instance, currently allows only the EVAP monitor to be unset on 2000 and newer gasoline cars, as of its fall 2025 explainer. Readiness monitors and smog checks has the details.
Step 6: Look at live data (optional but useful)
With the engine running, live data shows sensors in real time: coolant temperature, short- and long-term fuel trims, oxygen sensor voltages, engine speed, load. A thermostat stuck open shows as coolant temperature that never reaches normal; a vacuum leak often shows as high positive fuel trims at idle that drop at higher speed. Watch, do not guess. Live data covers the PIDs worth knowing.
Step 7: Fix first, clear second
Clear codes only after the cause is fixed, or when a mechanic asks you to. Clearing on most tools is done with the key on and the engine off, and the AD310 manual says to retrieve and record codes before you erase them. What clearing does:
- turns off the light, until the computer sees the fault again;
- erases stored and pending codes and the freeze frame;
- resets non-continuous readiness monitors to incomplete.
That last point is why clearing just before an emissions test backfires. Monitors complete after a mix of highway and stop-and-go driving, often over several days with at least one overnight cold soak, per the AD310 manual; your owner’s or service manual may give a specific drive cycle. The car can also turn the light off itself: federal rules let it go out after three consecutive trips without the fault, and EPA notes that a light that goes out on its own usually needs no action. Clear the check engine light covers the trade-offs.
Putting the results together
A scan gives you four pieces of evidence, and the useful habit is to read them together rather than jumping on the first code:
| What you saw | What it usually tells you | Next move |
|---|---|---|
| One stored code, freeze frame at cold start | Fault appears before the engine warms up | Check sensors and components that matter most when cold (coolant temperature, thermostat, cold-start fueling) |
| Several codes at once, including U codes | Possible network, power or ground problem rather than many failed parts | Check battery voltage, grounds and connectors before parts |
| Pending code only, light off | Early warning; not yet confirmed | Note it, drive normally, rescan in a few days |
| No codes, light was on and went out | Fault stopped recurring; the car cleared the light itself | Usually nothing, per EPA; rescan if it returns |
| Monitors incomplete, no codes | Recently cleared or battery disconnected | Drive normally and recheck before an emissions test |
These are general patterns, not diagnoses. The service information for your vehicle, or a technician, is the authority on what a specific code means on your engine.
Common mistakes
- Replacing the part the code names. The code names a circuit or condition. Test before you buy.
- Clearing before recording. You lose the freeze frame for good.
- Clearing right before inspection. Monitors reset and the car may be turned away.
- Driving on a flashing light. That is the catalyst-damage warning.
- Leaving a Bluetooth dongle in a parked car. Unless the maker publishes a sleep mode, unplug it if the car will sit.
- Running resets you do not understand. Relearns and coding write to the car; read the procedure first.
Which scanner for these steps
Any OBD2 tool does steps 1 to 5 and 7. A corded reader with live data and an I/M readiness button, such as the FOXWELL NT301, is the simplest. A Bluetooth adapter like the OBDLink MX+ or BlueDriver adds graphing and logging for step 6. You only need a bidirectional tool for active tests and relearns; see best OBD2 scanner for DIY owners and OBD2 scanner types.
Frequently asked questions
Should the engine be running when I use an OBD2 scanner?
For reading codes, most scanner manuals say to plug in with the ignition off, then turn the key to on with the engine off. Live data is more useful with the engine running, and the federal emissions inspection reads the system with the key on and engine running. Clearing codes is normally done key on, engine off. Follow your scanner's manual.
Where is the OBD2 port?
On most vehicles the 16-pin port is under the dashboard on the driver's side, often within about a foot of the steering column. Scanner manuals note that some cars hide it behind a panel or ashtray, and that a label should show the location if it is not under the dash. Your owner's manual will say.
Is it safe to clear the check engine light with a scanner?
Clearing is safe for the car, but it erases the stored code and the freeze frame snapshot and resets readiness monitors, so record everything first. If the fault is still there the light will come back. And if the car is due for an emissions test, it may be rejected until the monitors have run again.
What is the difference between stored, pending and permanent codes?
A stored (confirmed) code has turned the check engine light on. A pending code is a fault the computer saw in the current or last drive cycle that has not yet been confirmed, so the light may still be off. Permanent codes, on vehicles that support them, are a separate list that a scan tool cannot erase; they clear only after the car's own monitor runs and passes.
Why won't my scanner connect to the car?
Check that the ignition is on, the connector is fully seated, and the vehicle is OBD2 compliant (1996 or newer in the US). Scanner manuals suggest turning the ignition off, waiting about 10 seconds and trying again. A blown fuse for the port's power circuit is another common cause; the owner's manual lists which fuse feeds it.
Keep planning
- OBD2 Scanner Vehicle Coverage: Check Before You Buy
OBD2 scanner vehicle coverage explained: what every 1996+ car supports, what varies by make, and how to check a scanner's coverage list before you buy.
Updated Oct 2026 - Readiness Monitors and Smog Checks: Will Your Car Pass?
Readiness monitors and smog checks explained: how many incomplete monitors each model year may have, why monitors reset, and how to check before you test.
Updated Oct 2026 - Best OBD2 Scanner for DIY Owners: Picks by Need
The best OBD2 scanner for DIY owners, picked by need: basic code reader, Bluetooth app, ABS/SRS handheld or bidirectional tool, compared on published specs.
Updated Oct 2026