An OBD2 scanner can turn a Check Engine light into useful information: a trouble code, the conditions when the fault was detected, and the status of the vehicle’s emissions monitors. The key is to read and save the evidence before pressing “Erase.”
Quick answer
To use an OBD2 scanner: park safely, locate the 16-pin diagnostic connector under the dashboard, plug in the scanner, switch the ignition to the position requested by the tool, select OBD II or Engine, and read all available stored, pending, and permanent codes. Save the exact codes, descriptions, freeze-frame data, and readiness status before clearing anything. A code identifies a system or condition to investigate; it does not prove which part should be replaced.
This walkthrough applies to a basic handheld engine-code reader such as the OBD2 Scanner for Check Engine Codes & Live Data from Cargadgets. Menu names and supported data vary by vehicle and scanner, so use the vehicle owner’s manual and the tool’s manual together.
Before connecting: decide whether the car should be driven
A scanner is an information tool, not permission to keep driving. If the vehicle has a flashing Check Engine light, severe shaking, loss of power, overheating, low oil pressure, brake warnings, smoke, fuel odor, or any safety-related symptom, stop in a safe place and follow the owner’s manual. Seek qualified assistance instead of continuing a scan while driving.
Manufacturer instructions vary by vehicle. For example, Subaru’s owner guidance says a blinking Check Engine light can indicate a misfire that may damage the emissions system and advises reducing speed, avoiding hard acceleration and steep grades, and arranging prompt inspection. Use your own vehicle’s instructions as the authority. See Subaru’s Check Engine warning guidance for one manufacturer example.
For a steady Check Engine light with no urgent symptoms, scanning while parked can help you document the problem before deciding on the next step.
What a basic OBD2 scanner can—and cannot—tell you
The Cargadgets handheld scanner is designed for supported engine and emissions-related OBD II information. It can read and clear supported codes, show available live data and freeze-frame information, check emissions readiness, and display available vehicle information such as VIN, CIN, or CVN where the vehicle provides it. The tool receives power from the diagnostic port, so it does not need a separate battery.
Its confirmed coverage does not extend to every vehicle module. ABS, airbag/SRS, transmission, diesel, heavy-duty, hybrid, EV, and manufacturer-specific system coverage has not been confirmed. A generic reader may show no result for a warning controlled by one of those modules.
Before ordering or connecting any scanner, confirm that the vehicle is OBD II-compliant and uses a protocol supported by the tool. Compatibility can vary by year, make, model, engine, and sales market.
Understand the information you are about to read
| Scanner item | What it means | What to do |
|---|---|---|
| Stored or confirmed code | The vehicle has confirmed a fault according to its monitoring logic; it may be associated with the Check Engine light. | Record the code and related data, then diagnose the system using correct service information. |
| Pending code | A fault was detected but may not yet meet the vehicle’s criteria for a confirmed code. | Do not ignore it. Save it and look for patterns, symptoms, or repeated detection. |
| Permanent code | An emissions-related record that cannot be erased with a normal code-clear command or battery disconnect. | Repair the cause. The vehicle’s OBD system clears the record after it verifies the fault is no longer present. |
| Freeze frame | A snapshot of supported operating conditions when a fault was stored, which may include RPM, load, temperature, speed, or fuel-trim data. | Photograph or write down the values before clearing codes. |
| Readiness monitor | Shows whether a supported emissions self-test has completed since codes were cleared or power was interrupted. | Distinguish “complete/ready,” “incomplete/not ready,” and “not supported.” |
| Live data | Current values reported by supported sensors and calculated parameters. | Use specifications and a diagnostic plan; one unusual number is not automatically a failed sensor. |
California’s Bureau of Automotive Repair explains that permanent diagnostic trouble codes cannot be erased by clearing codes or disconnecting the battery; the OBD system must verify the repair through its own monitoring. Its OBD test reference also explains how readiness monitors are used in emissions inspections.
How to use an OBD2 scanner step by step
Step 1: park and prepare
Park on a level surface in a ventilated area, apply the parking brake, select Park or Neutral as appropriate, and switch off accessories. Keep the scanner cable away from the pedals and steering column. Do not attempt the initial setup while the vehicle is moving.
Have a phone or notebook ready. Record the vehicle year, make, model, engine, mileage, symptoms, warning-light behavior, and whether the problem started after refueling, a repair, a dead battery, or another event.
Step 2: find the diagnostic connector
Look for a trapezoid-shaped 16-pin connector under the dashboard within reach of the driver. Common locations include below the steering column, near the hood-release area, behind a small removable cover, or along the lower dash edge.
Use the owner’s manual if the connector is not obvious. Do not confuse it with another plug, force the scanner into the socket, or probe the pins with metal objects.
Step 3: inspect the connector and cable
With the ignition off, check for bent pins, damaged plastic, moisture, dirt, or a loose connector. Inspect the scanner plug and cable as well. If anything appears damaged, stop and correct the physical problem before connecting.
Step 4: plug in the scanner
Align the trapezoid shapes and push the connector in straight. The handheld scanner should power up from the vehicle’s port. Position it where the cable does not cross the brake or accelerator pedals.
If the tool does not power on, unplug it and consult the vehicle manual for the diagnostic-port or related fuse. Some vehicles share port power with another accessory circuit. Replace a fuse only with the specified type and rating; do not bypass the circuit.
Step 5: set the ignition as instructed
Many basic code-reading sessions begin with the ignition in the ON/RUN position and the engine off. Push-button vehicles may require pressing the start button without pressing the brake pedal. Some live-data tests require the engine to be running.
Follow the scanner and vehicle instructions. Do not start the engine in an enclosed garage, and never leave a running vehicle unattended.
Step 6: establish communication
Select the OBD II, EOBD, or Engine diagnostic menu. The scanner may automatically identify the communication protocol. If prompted, confirm vehicle information only when it matches the car.
A connection failure does not automatically mean the scanner is defective. Recheck ignition position, plug seating, port power, protocol support, and vehicle compatibility. Enhanced or non-engine modules may require a more advanced vehicle-specific scan tool.
Step 7: read every available code category
Open “Read Codes” and check each category the tool provides:
- Stored or confirmed codes
- Pending codes
- Permanent codes
- Historic codes, if supported
Write down the complete alphanumeric code exactly as shown, such as P followed by four characters. Record which category contained it and whether the Check Engine light was on, off, steady, or flashing.
Do not rely only on the short description displayed by the scanner. A generic description may name a circuit or performance condition without identifying the failed component.
Step 8: save freeze-frame data
Open the freeze-frame menu before clearing anything. Photograph all available pages, including engine speed, calculated load, coolant temperature, vehicle speed, fuel-system status, fuel trims, airflow, or other supported values.
The snapshot can reveal whether the fault occurred during a cold start, idle, acceleration, cruise, or high-load condition. Not every vehicle or code supplies the same data.
Step 9: check I/M readiness
Open the readiness or I/M menu and note three different states:
- Ready/Complete: the monitor has run.
- Not Ready/Incomplete: the monitor has not completed since a reset or because required conditions have not occurred.
- Not Supported: the monitor does not apply to that vehicle configuration.
Readiness rules for an emissions inspection vary by location and vehicle. Clearing codes immediately before an inspection can make monitors incomplete and does not prove a repair was successful.
Step 10: review live data carefully
Use live data only when the vehicle can be operated safely in a ventilated area. Select a small group of relevant values instead of scrolling through every parameter. Compare readings with the vehicle’s service information and the conditions under which the code set.
Live data is most useful for confirming a diagnostic hypothesis. A value that looks unusual may reflect operating conditions, a wiring issue, a mechanical problem, a vacuum leak, a calculation, or a sensor fault. Do not replace parts from one reading alone.
How to interpret an OBD2 code without guessing
A diagnostic trouble code is a direction for testing. For example, a code mentioning an oxygen-sensor circuit does not prove the sensor itself is bad. Wiring, connectors, exhaust leaks, fuel mixture problems, power supply, or another fault can produce related symptoms.
Use this sequence:
- Verify the exact code and status.
- Review freeze frame and symptoms.
- Check for related codes that may share a cause.
- Look up the correct service procedure for the exact vehicle and engine.
- Perform visual, electrical, mechanical, pressure, smoke, or other specified tests.
- Repair the verified cause rather than the part named in a generic description.
If the diagnosis requires electrical measurements, fuel-system work, lifting the vehicle, high-voltage hybrid/EV systems, or safety modules, use a qualified technician.
When should you clear codes?
Clear supported codes only after you have saved the evidence and addressed the underlying issue, or when a service procedure specifically instructs you to do so. The Cargadgets scanner can clear supported engine-related codes, but that command is not a repair.
Clearing codes may:
- Turn off the Check Engine light temporarily
- Erase stored and pending code information
- Remove available freeze-frame data
- Reset readiness monitors to incomplete
- Reset some learned values, depending on the vehicle
A permanent code normally remains until the vehicle’s OBD system runs the relevant monitor and confirms the malfunction is gone. Do not disconnect the battery simply to hide a warning light; that can erase useful evidence and affect other vehicle settings.
After a repair: verify the result
- Reconnect the scanner and confirm the code information was saved.
- Clear supported codes only if appropriate.
- Start the vehicle and check for immediate faults or warning lights.
- Follow the vehicle manufacturer’s specified drive cycle when available, or drive normally until the required monitors have had a chance to run.
- Re-scan stored, pending, and permanent codes.
- Check readiness status and confirm the original symptoms are gone.
A light that stays off for a few minutes is not enough to prove a repair. Some monitors need specific temperature, speed, load, fuel-level, or trip conditions before they can evaluate the system.
Common OBD2 scanner problems
The scanner does not power on
Turn the ignition off, unplug the tool, and inspect the connector. Check the correct fuse using the vehicle manual. Do not insert jumpers or power into unknown pins.
The scanner powers on but will not link
Confirm the required ignition position, reseat the plug, and verify that the vehicle is OBD II-compliant and uses a supported protocol. A generic engine reader may not communicate with every manufacturer-specific module.
The Check Engine light is on but no engine code appears
Make sure you selected the engine/OBD II menu and checked all code categories. The warning may be controlled by a system outside the scanner’s confirmed coverage, or the vehicle may require an enhanced scan tool.
A code returns immediately after clearing
The fault is likely still present, or the monitor detected it again. Save the new status and data, then continue diagnosis. Repeatedly erasing the code does not fix the condition.
The scanner says “Not Ready”
The monitor has not completed. This commonly happens after codes were cleared, the battery was disconnected, or the required operating conditions have not occurred. “Not Ready” is different from “Not Supported.”
Frequently asked questions
Can an OBD2 scanner tell me exactly what part to replace?
No. It identifies a fault code and supporting data. Diagnosis still requires confirming the circuit, operating conditions, wiring, mechanical system, and manufacturer procedure.
Can I use an OBD2 scanner with the engine running?
Some functions, especially live data, require a running engine. Initial code retrieval often uses ignition ON with the engine off. Follow the vehicle and scanner instructions, work in a ventilated area, and keep the cable away from pedals and moving parts.
What is the difference between pending and permanent codes?
A pending code reports a detected fault that may not yet be confirmed. A permanent emissions code remains as a record until the vehicle verifies through its own monitoring that the fault is no longer present; it cannot normally be erased with a basic clear command.
Will clearing codes reset emissions readiness?
Yes, clearing codes commonly resets readiness monitors to incomplete. Local inspection rules vary, so do not clear codes immediately before an emissions test.
Can a basic OBD2 scanner read ABS or airbag codes?
Not necessarily. The Cargadgets model’s confirmed coverage is engine and emissions-related OBD II diagnostics. ABS, airbag/SRS, transmission, and other enhanced module coverage has not been confirmed.
Does an OBD2 scanner need batteries?
The Cargadgets handheld scanner is powered by a compatible vehicle’s diagnostic port and does not require a separate battery.
Is it safe to leave the scanner plugged in?
For a basic handheld diagnostic session, disconnect it after use unless the scanner and vehicle manufacturer specifically approve continuous connection. Store the cable where it cannot interfere with driving controls.
Bottom line
The safest and most useful habit is simple: read first, record everything, diagnose the system, repair the verified cause, and clear codes last. That preserves the freeze-frame and readiness evidence that can make troubleshooting faster and more accurate.
Compare the OBD2 Scanner for Check Engine Codes & Live Data, or review our OBD2 scanner buying guide before choosing a tool for your vehicle.
