Use this guide to connect an OBD-II scanner, read your car’s diagnostic trouble codes, and save the results before deciding on a repair. It is for drivers with basic vehicle knowledge who want to understand a warning light or share useful information with a mechanic. Plan for 15-30 minutes. Reading a code identifies a system or condition the vehicle detected; it does not, by itself, confirm which part has failed.
Get business pricing on garage and car supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
EDIAG H361 Bidirectional OBD2 Diagnostic Scanner
- ✔ Diagnostic systems: Engine, transmission, ABS and SRS
- ✔ Maintenance functions: 16; availability varies by vehicle
- ✔ Display: 6-inch touchscreen with physical buttons
FOXWELL NT301 OBD2 Scanner with Live Data
- ✔ Brand and model: FOXWELL NT301
- ✔ Display: 2.8-inch color screen
- ✔ Functions: Engine codes, live data graphs and emissions readiness
ANCEL AD310 OBD II Car Code Reader
- ✔ Brand and model: ANCEL AD310
- ✔ Cable length: 2.5 ft
- ✔ Weight: 12 oz
Difficulty: Beginner | Time: 15-30 minutes
What You’ll Need
Tools & Materials:
- OBD-II diagnostic scanner compatible with your vehicle
- Vehicle owner’s manual
- Phone or paper for recording codes and symptoms
- A safe, level place to park
Knowledge:
- How to locate the ignition switch or start button
- How to apply the parking brake and shift the vehicle into Park or Neutral
Most cars and light trucks sold in the United States from model year 1996 onward use OBD-II. Rules and connector types can differ elsewhere, and some older vehicles need a manufacturer-specific scanner. Check your owner’s manual or the scanner’s compatibility list. Keep the vehicle stationary while using the scanner; never handle it while driving.
EDIAG H361 Bidirectional OBD2 Diagnostic Scanner
The EDIAG H361 earns the top position because it is the only scanner in this comparison that lists diagnostics for engine, transmission, ABS and SRS. That wider reach matters when a warning light points beyond the engine: the ANCEL AD310 and FOXWELL NT301 are confined to engine and emissions-related work, so they cannot fill the same role.Its bidirectional controls add another layer: supported component activation can help us check whether a part responds, rather than simply reading stored faults. The 16 maintenance functions, AutoVIN, live data graphs and saveable reports make it better suited to ongoing DIY troubleshooting than either basic reader. A 6-inch touchscreen and physical buttons provide a larger working interface than the NT301’s 2.8-inch screen.That breadth comes with a real compatibility caveat. Available system scans and resets vary by vehicle, so we should confirm support against the VIN and intended job before buying. FCA AutoAuth also requires a separate account and paid subscription. For buyers who only need engine codes and readiness status, the simpler FOXWELL or ANCEL may be easier to justify; the H361 makes most sense when its extra system access will be used.
Pros:
- Lists diagnostics for engine, transmission, ABS and SRS systems.
- Bidirectional controls can activate supported components during troubleshooting.
- Includes live data graphs, reports and 16 vehicle-dependent maintenance functions.
- Large touchscreen, physical buttons and lifetime free updates.
Cons:
- Functions and maintenance coverage vary by vehicle; verify support using the VIN.
- FCA AutoAuth requires a separate account and paid subscription.
- Its broader feature set is unnecessary for simple engine-code checks.
Best for: DIY owners who want to investigate multiple vehicle systems and use supported active tests or maintenance functions.
Not ideal for: Drivers who only need basic engine-code and emissions checks, or anyone who needs guaranteed functions without first checking vehicle compatibility.
Bottom line: Choose the H361 when multi-system access and active troubleshooting matter more than a basic, focused code reader.
“Choose the H361 when multi-system access and active troubleshooting matter more than a basic, focused code reader.”
FOXWELL NT301 OBD2 Scanner with Live Data
The FOXWELL NT301 is the stronger choice for buyers who want more help interpreting engine behavior without stepping up to a multi-system tool. It reads and clears engine fault codes, graphs live sensor data and checks emissions readiness. Compared with the ANCEL AD310, the NT301’s graphing and color screen make changing sensor readings easier to follow; compared with the EDIAG H361, it stays focused on engine and emissions diagnostics.Its one-click readiness check uses LED and audio indicators, giving us a quick status cue when preparing for an emissions inspection. The scanner draws power through the vehicle diagnostic port, so it does not need a separate power source for use. The 2.8-inch screen is daylight-readable, and plug-and-play operation keeps the basic workflow approachable.The limitation is firm: this is not a full-system scanner. It does not access ABS, SRS or TPMS modules, and it lacks manufacturer-specific full-system scans, service resets and key programming. Compatibility and available functions also vary by vehicle. We would pick it over the ANCEL when graphing and a more informative display matter, but buyers with transmission or airbag diagnostics in mind should look to the EDIAG and confirm coverage.
Pros:
- Reads and clears engine fault codes and graphs live sensor data.
- One-click emissions readiness checks use LED and audio indicators.
- Color screen is designed for daylight readability.
- Powered through the vehicle diagnostic port for plug-and-play use.
Cons:
- Does not diagnose ABS, SRS or TPMS systems.
- No manufacturer-specific full-system scans, service resets or key programming.
- Coverage and functions vary by vehicle.
Best for: Owners who primarily troubleshoot engine faults and want to watch or graph live sensor data while checking emissions readiness.
Not ideal for: Buyers who need ABS, SRS, TPMS, transmission, service-reset or key-programming functions.
Bottom line: The NT301 is the best fit for engine-focused users who value graphable data and clear readiness feedback over broader system access.
“The NT301 is the best fit for engine-focused users who value graphable data and clear readiness feedback over broader system access.”
ANCEL AD310 OBD II Car Code Reader
The ANCEL AD310 keeps the job narrow: it reads and clears emission-related engine trouble codes, shows live and freeze-frame data, and checks I/M monitor readiness. That is enough for a driver who wants to understand a check-engine light or see whether monitors are ready. Its compact, lightweight design and flexible 2.5-foot cable make it a practical basic reader.Against the FOXWELL NT301, the AD310 offers a more stripped-down presentation: it supplies live data, but the listed features do not include graphing or the FOXWELL’s LED and audio readiness indicators. The NT301 is therefore a better fit when we want more visual feedback while watching sensors. The ANCEL still covers the core code and readiness tasks, and it supports the same major OBD II protocol families listed for the FOXWELL.Its main drawback is scope. The AD310 cannot diagnose ABS, SRS, transmission or other non-emission issues, and it requires an OBD II interface, so it will not diagnose OBD I vehicles. The FOXWELL also lacks broader system access, while the EDIAG is the step up for multiple modules. Choose the AD310 when the goal is a compact, uncomplicated engine-code check, not a single tool for every dashboard warning.
Pros:
- Reads and clears emission-related trouble codes.
- Displays live data, freeze-frame data and I/M monitor readiness.
- Supports major OBD II protocols across compatible vehicles.
- Compact design with a flexible 2.5-foot cable.
Cons:
- Does not diagnose ABS, SRS, transmission or other non-emission issues.
- Requires an OBD II interface and cannot diagnose OBD I vehicles.
- Does not list the NT301’s live-data graphing or readiness indicators.
Best for: Drivers who want a compact reader for emission-related engine codes, freeze-frame information and I/M readiness status.
Not ideal for: Owners who need graphing, non-engine module diagnostics, OBD I support or service functions.
Bottom line: Pick the AD310 for essential emissions-related checks in a compact reader, provided its limited diagnostic scope matches your needs.
“Pick the AD310 for essential emissions-related checks in a compact reader, provided its limited diagnostic scope matches your needs.”
As an Amazon Associate we earn from qualifying purchases.
Before You Start
Park on level ground, switch off accessories, and apply the parking brake. Keep hands, cables, and clothing clear of moving parts. If the check-engine light is flashing, or the car is overheating, losing oil pressure, or running very roughly, stop driving and arrange professional help. Do not erase codes before recording them: clearing them can remove useful diagnostic information and reset emissions readiness monitors.
Step-by-Step Instructions
Step 1: Locate the diagnostic connector
Switch the ignition off and check your owner’s manual for the OBD-II connector location. It is usually beneath the dashboard near the steering column, though it may sit behind a small cover. Find the trapezoid-shaped socket and confirm that the scanner plug matches it. Do not force the plug into place.
Tip:Use a flashlight if the socket is tucked above the pedals. Avoid pulling on nearby wiring or trim.
Check: You can see the connector and the scanner plug fits its shape without force.
Step 2: Prepare the vehicle and scanner
Read the scanner’s quick-start instructions. With the vehicle still off, connect the scanner to the diagnostic socket. If it is a wireless model, follow its instructions to pair it with the phone or display unit. Keep the cable clear of the pedals and your feet.
Tip:Some scanners receive power through the connector; others need a charged phone or separate power. Check the screen or indicator before continuing.
Check: The scanner powers on or the wireless connection is ready, and the cable does not obstruct the driver’s controls.
Step 3: Switch the ignition to the correct position
Turn the ignition to ON without starting the engine if your scanner asks for ignition power. In a keyless car, press the start button without pressing the brake or clutch, following the vehicle manual. Keep the engine off unless the scanner specifically requests it for a live-data check.
Tip:Dashboard lights may illuminate in this position. That is normal. Do not leave the ignition on longer than needed, especially if the battery is weak.
Check: The scanner identifies the vehicle or offers menu choices, and the engine remains off for the initial code read.
Step 4: Run a code scan
Choose the scanner option labeled Read Codes, Scan, or a similar term. Select the vehicle make or model if prompted. Wait for the scan to finish, then review stored, pending, and permanent codes if the tool lists them. Record every code exactly, including letters and numbers, and note which category the scanner assigns it.
Tip:A code such as P0301 points to a detected condition—in this example, a misfire on cylinder 1. It does not prove the spark plug or any other single part is faulty.
Check: The scanner displays a result or states that no codes are present. You have copied each code and its status accurately.
Step 5: Record symptoms and freeze-frame details
Write down when the warning light appeared and what the car was doing: for example, starting, idling, accelerating, or cruising. If available, open Freeze Frame or Vehicle Snapshot and record the listed engine conditions, such as engine speed, coolant temperature, and vehicle speed. Save or photograph the screen before leaving the menu.
Tip:Freeze-frame data captures conditions around a fault. Keep its units and labels with the values so they are not misread later.
Check: Your notes include the exact codes, code status, symptoms, and any useful snapshot data.
Step 6: Check live data when useful
If you need more context and the scanner supports it, select Live Data. Read values with the engine off first. If the scanner calls for the engine to run, start it only in a well-ventilated outdoor area, keep the vehicle in Park or Neutral with the parking brake applied, and stay clear of moving parts. Watch only a few relevant readings at a time, such as coolant temperature or engine speed.
Tip:Live readings vary with engine temperature, load, and vehicle design. A value that looks unusual on its own is not a diagnosis; compare it with vehicle-specific service information.
Check: The scanner shows labeled readings, and you have recorded only values gathered under the stated conditions.
Step 7: Look up the codes and choose a next step
Use the scanner’s description as a starting point, then check a reliable repair reference for the exact code and vehicle. Compare the result with your symptoms and any service bulletins or vehicle-specific guidance. If the code needs electrical testing, specialist equipment, or access near hazardous components, give your notes to a qualified mechanic rather than replacing parts based only on the code.
Tip:Several faults can trigger similar codes. Diagnose the cause before buying parts.
Check: You have a documented result and a reasonable next action, such as monitoring a minor issue, arranging a repair, or stopping driving for urgent service.
Step 8: Disconnect the scanner
Turn the ignition off and wait for the scanner to finish communicating. Unplug it by holding the connector body, not pulling the cable. Close any connector cover, then store the scanner and your notes together.
Tip:Do not select Clear Codes as a cleanup step. Clear codes only when the cause has been addressed and you understand the effect on readiness monitors.
Check: The scanner is disconnected, the vehicle is off, and your code record is saved.
Common Mistakes to Avoid
- Clearing codes before writing them down. — Record all codes, statuses, symptoms, and freeze-frame information before using any clear function.
- Replacing a component based on the code description alone. — Treat the code as a clue, then verify the cause with vehicle-specific diagnostic information and appropriate tests.
- Using a scanner that does not support the vehicle or the needed system. — Check the model-year, make, and system compatibility list before connecting; basic OBD-II tools may not read ABS, airbag, or manufacturer-specific codes.
- Leaving the ignition on or running the engine in an enclosed space. — Follow the scanner’s instructions, limit ignition-on time, and run the engine only outdoors with the vehicle secured.
Troubleshooting
Problem: The scanner does not power on.
Solution: Confirm the plug is fully seated and the ignition position matches the scanner instructions. Check the vehicle manual for a fuse that supplies the diagnostic connector. Do not probe the socket with improvised metal tools.
Problem: The scanner cannot communicate with the vehicle.
Solution: Turn the ignition off, reseat the plug, then retry with ignition ON. Confirm the scanner supports the vehicle and protocol. If it still fails, a blown fuse, wiring issue, or vehicle fault may need professional diagnosis.
Problem: The scanner reports no codes, but a warning light is on.
Solution: Check whether the tool supports the system that triggered the light; a basic engine-code reader may not access ABS or airbag modules. Consult the vehicle manual or use a compatible professional scanner.
Problem: A code returns after repair or clearing.
Solution: Record the returning code and note when it reappears. The underlying cause may remain, the repair may need further checks, or the vehicle may require a drive cycle. Ask a mechanic to diagnose it rather than repeatedly clearing it.
What Success Looks Like
You have read the scanner’s results, recorded each code and status exactly, saved relevant symptoms or freeze-frame details, and disconnected the tool safely. You know whether the next step is further diagnosis, a repair appointment, or urgent help. A successful scan does not mean the fault itself is fixed.
Next Steps
Keep your scan notes with the vehicle’s service records and share them with the repair shop. After a confirmed repair, follow the technician’s guidance on clearing codes and completing any required drive cycle. If a warning returns or the vehicle’s behavior worsens, stop relying on repeated scans and arrange diagnosis.
Frequently Asked Questions
Can I use a diagnostic scanner while driving?
No. Connect and operate the scanner while parked. Do not read a handheld screen or handle a phone or cable while driving.
Will a basic scanner read ABS or airbag faults?
Often it will not. Many basic OBD-II readers cover emissions-related engine codes only. Check the tool’s system coverage for your exact vehicle before buying or using it.
Should I clear the code after I read it?
Usually not before diagnosis. Save the code and related data first. Clearing can erase evidence and reset emissions readiness monitors; clear it after a repair only when appropriate.
Does a trouble code tell me which part to replace?
No. A code describes a detected condition or affected circuit. Wiring, connectors, leaks, several components, or other conditions can produce similar codes, so verify the cause before replacing parts.
