This guide shows beginner drivers how to connect a car diagnostic scanner, read and record trouble codes, and use the results to plan a repair or seek professional help. You will learn a safe process for a vehicle with an OBD-II port. Allow 15-30 minutes; the scan itself usually takes only a few minutes.
Get business pricing on garage and car supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Foxwell NT301 OBD2 Scanner – Live Data Diagnostic Code Reader
- ✔ Brand: FOXWELL
- ✔ Model: NT301
- ✔ Weight: 0.16 kg
ANCEL AD410 Enhanced OBD2 Scanner – Vehicle Code Reader for Check Engine Light (1996+), Black/Yellow
- ✔ Brand: ANCEL
- ✔ Model: AD410
- ✔ Weight: 10.56 ounces
ANCEL AD310 Classic Enhanced Universal OBD II Scanner – Black
- ✔ Brand: ANCEL
- ✔ Model: AD310
- ✔ 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 notepad to record codes and symptoms
Knowledge:
- Ability to locate the vehicle’s OBD-II port using the owner’s manual
- Ability to identify the ignition positions described in the manual
Most cars and light trucks sold in the United States from model year 1996 use OBD-II. Requirements and coverage differ in other regions, for diesel vehicles, and for some manufacturer-specific systems. Check the scanner’s compatibility list before connecting it. A basic scanner may read engine and emissions codes but may not access ABS, airbag, transmission, or other systems.
Foxwell NT301 OBD2 Scanner – Live Data Diagnostic Code Reader
The Foxwell NT301 earns our top spot because it goes beyond retrieving and clearing a check-engine code. Its live sensor graphs and code logging give us more context for following an engine issue than the ANCEL AD310’s stated read-and-clear functions. The color screen and one-click code controls also make the basic workflow approachable, while I/M readiness indicators can help us check whether the vehicle’s emissions monitors are ready for inspection.That added visibility is useful when we want to see changing sensor readings, but it does not turn the NT301 into a full vehicle diagnostic system. The listed limits exclude ABS, SRS, TPMS, and manufacturer-specific system scans, and its service-reset functions are limited. Compared with the ANCEL AD410, the Foxwell’s standout is graphing and logging; the AD410 counters with its advertised large DTC definition database and multilingual menus. We’d choose the NT301 when investigating engine data matters more than having that built-in library.
Pros:
- Graphs live sensor data to provide context beyond a stored code.
- Reads, clears, and logs engine fault codes.
- I/M readiness indicators help us check emissions monitor status.
- No battery or subscription is required according to the product description.
Cons:
- Does not scan ABS, SRS, TPMS, or other full-system modules.
- Service resets are limited, and it does not support key programming or battery health testing.
- The supplied information lists a 12-month warranty, so buyers should check coverage details for their needs.
Best for: DIY drivers who want to inspect live engine sensor readings, log codes, and check I/M readiness.
Not ideal for: Buyers who need ABS, airbag, TPMS, transmission, key-programming, or advanced service functions.
Bottom line: We recommend the Foxwell NT301 for DIY engine diagnosis when live graphs and code logging matter more than wider vehicle-system coverage.
“We recommend the Foxwell NT301 for DIY engine diagnosis when live graphs and code logging matter more than wider vehicle-system coverage.”
ANCEL AD410 Enhanced OBD2 Scanner – Vehicle Code Reader for Check Engine Light (1996+), Black/Yellow
The ANCEL AD410 is the better fit when we want more help interpreting a code on the scanner itself. Its built-in database of more than 42,000 DTC definitions is a practical advantage over the AD310, whose described role is limited to reading and clearing emission-related codes. The AD410 also displays live engine data and supports freeze-frame information, sensor tests, and I/M readiness, giving us several useful angles on an engine warning without relying on a phone app.Against the Foxwell NT301, the AD410’s clearest distinction is its code-definition library and multilingual menus; the Foxwell is the more explicit choice for graphing and logging live data. Either way, the scope remains engine and emissions diagnostics. The AD410 does not read ABS, SRS, or transmission codes and offers no bidirectional controls, so we should not buy it expecting a scan tool that can command vehicle components or reach every module. Its color display and standalone operation suit drivers who value on-device guidance, provided their needs stay within OBDII engine diagnostics.
Pros:
- Built-in database lists more than 42,000 diagnostic trouble code definitions.
- Displays live engine data and freeze-frame information.
- Supports I/M readiness and sensor tests.
- Operates without a battery, charger, or phone app.
Cons:
- Limited to engine and emission-related diagnostic codes.
- Does not support ABS, SRS, transmission codes, or bidirectional controls.
- Vehicle compatibility is broad but should be checked against the specific vehicle and required functions.
Best for: Drivers who want a standalone OBDII reader with live engine data, readiness checks, and built-in code definitions.
Not ideal for: Owners who need diagnostics or control functions for ABS, airbags, transmission, or other non-engine systems.
Bottom line: We’d choose the AD410 when built-in code explanations and a broad set of engine OBDII checks are more useful than the Foxwell’s emphasis on graphing and logging.
“We’d choose the AD410 when built-in code explanations and a broad set of engine OBDII checks are more useful than the Foxwell’s emphasis on graphing and logging.”
ANCEL AD310 Classic Enhanced Universal OBD II Scanner – Black
The ANCEL AD310 is the straightforward pick for drivers who mainly want to retrieve and clear emission-related trouble codes. Its large screen and labeled buttons keep the basic process simple, and support for major OBDII protocols—including CAN—helps it work across a wide range of compatible vehicles. Because it draws power from the OBDII port, we do not need to manage a separate battery or charger.Its simplicity also defines its place in this lineup. The Foxwell NT301 adds live sensor graphs, code logging, and readiness indicators; the ANCEL AD410 adds live data, tests, and a large code-definition database. The AD310’s described capability is narrower: emission-related code reading and clearing. That may be enough for a basic check-engine-light task, but it offers less diagnostic context when we need to understand what is happening beyond the stored code. It also cannot diagnose vehicles using an OBDI interface, so we should verify the vehicle’s model year and port before choosing it.
Pros:
- Supports major OBDII protocols, including CAN.
- Large screen and clearly labeled buttons simplify basic operation.
- Reads and clears emission-related trouble codes without a separate battery or charger.
- Compact, lightweight body with a 2.5-foot cable.
Cons:
- Limited to emission-related diagnostic trouble codes.
- Does not diagnose vehicles with an OBDI interface.
- Requires power from a compatible vehicle OBDII port.
Best for: Drivers who want a simple, corded reader for retrieving and clearing emission-related codes on a compatible OBDII vehicle.
Not ideal for: Buyers who want live data, detailed code interpretation, broad system scans, or diagnostics for an OBDI vehicle.
Bottom line: We recommend the AD310 for basic code retrieval and clearing, while drivers who want live engine context should move up to the AD410 or Foxwell NT301.
“We recommend the AD310 for basic code retrieval and clearing, while drivers who want live engine context should move up to the AD410 or Foxwell NT301.”
As an Amazon Associate we earn from qualifying purchases.
Before You Start
Park on level ground, select Park or Neutral as appropriate, apply the parking brake, and switch off accessories. Keep clear of moving parts and hot engine components. Do not scan while driving. If the check-engine light is flashing, the engine is running roughly, or the vehicle has a serious warning such as low oil pressure or overheating, stop driving when safe and seek qualified help. A scanner provides clues; a code alone does not identify a failed part.
Step-by-Step Instructions
Step 1: Check compatibility and gather vehicle details
Write down the vehicle’s year, make, model, engine type if known, and current symptoms. Compare those details with the scanner’s compatibility information. Read the scanner instructions to learn whether it uses a cable, Bluetooth, or Wi-Fi and whether it needs an app. Install any required app before going to the vehicle, and grant only the permissions it needs to connect.
Tip:Record when the warning appeared and what the vehicle was doing, such as starting cold, accelerating, or idling. These details can help a technician diagnose the cause.
Check: The scanner is listed as compatible, and any required app opens and is ready to connect.
Step 2: Locate the OBD-II port
Turn the vehicle off and consult the owner’s manual for the diagnostic connector location. It is commonly beneath the dashboard near the steering column, but the location varies. Use a flashlight to inspect the area. The port is a small, trapezoidal socket with 16 pin positions. Do not confuse it with an accessory socket or force a connector into an opening.
Tip:If you cannot find the port, check the manual’s index for “OBD,” “data link connector,” or “diagnostic connector.”
Check: You have identified the 16-pin diagnostic port without removing trim or forcing any parts.
Step 3: Connect the scanner with the vehicle off
Make sure the ignition is off. Align the scanner plug with the port and press it in firmly and straight. Do not rock the plug hard or push it at an angle. For a wireless scanner, plug in its adapter first, then follow the manufacturer’s pairing instructions. Keep cables clear of pedals and your feet.
Tip:If the plug will not seat, stop and check its orientation. Bent pins or a damaged port need attention; forcing the connector can cause more damage.
Check: The plug is seated securely, and the scanner or adapter powers on if its design draws power from the port.
Step 4: Switch the ignition to the correct position
Follow the scanner’s instructions for the ignition state. Most scans require the ignition on with the engine off. In a key-start vehicle, turn the key to the ON position without starting the engine. In a push-button vehicle, use the owner’s manual instructions to switch the ignition on without pressing the brake or clutch to start the engine. Start the engine only if the scanner specifically requests it and conditions are safe.
Tip:Dash lights may illuminate while the engine remains off. That is usually the correct state for reading stored codes.
Check: The scanner reports that it has power and can communicate with the vehicle, or displays a prompt to continue setup.
Step 5: Start a vehicle scan
Choose the option labeled “Read Codes,” “Scan,” or a similar term. Select the vehicle or system if prompted, then wait for the scan to finish. Do not disconnect the scanner or switch off the ignition while it is communicating. If the scanner offers a choice between stored, pending, and permanent codes, read each available category and keep the categories separate in your notes.
Tip:Pending codes can indicate a fault the vehicle has detected but has not confirmed over enough drive cycles. Permanent emissions codes may remain visible until the vehicle verifies that the fault is resolved.
Check: The scanner shows a completed scan or a results screen. A “no codes” message means no codes were available to that scanner in the systems it checked; it does not prove that every system is fault-free.
Step 6: Record codes and freeze-frame information
Write down every code exactly as shown, including its letter and digits, and note whether it is stored, pending, or permanent. Save or photograph the screen if useful. If the scanner provides freeze-frame data, record it too; this is a snapshot of conditions when a fault was logged, such as engine speed or coolant temperature. Also note warning lights and symptoms. Do not rely on memory or record only the code description.
Tip:Codes beginning with P commonly relate to the powertrain, but the description is only a starting point. Manufacturer-specific codes may require a capable scanner or service information for that vehicle.
Check: Your notes contain the complete code, its status, available freeze-frame details, and the symptoms you observed.
Step 7: Use the results to choose a safe next step
Look up the exact code for your year, make, model, and engine in a reliable repair reference or ask a qualified technician. Treat the code as evidence about a circuit or detected condition, not proof that the named component has failed. Compare it with the vehicle’s symptoms and any related codes. Arrange diagnosis or repair if the warning persists, the vehicle runs poorly, or the cause is unclear.
Tip:Stop driving and get professional help if the vehicle overheats, loses oil pressure, has a flashing check-engine light, or behaves unsafely. A basic scan cannot confirm that a vehicle is safe to drive.
Check: You have a documented code and a reasonable next action, such as monitoring a minor issue, arranging diagnosis, or stopping use of the vehicle.
Step 8: Disconnect the scanner and leave codes intact
Finish any scan or save operation, switch the ignition off, and then unplug the scanner by its connector rather than pulling on the cable. Close the app if you used one. Leave the codes in place until they have been recorded and the underlying problem has been addressed. If you later clear codes after a repair, follow the scanner and vehicle instructions and understand that readiness monitors may need time and driving cycles to run again.
Tip:Clearing codes can erase useful diagnostic clues and reset emissions readiness information. It does not repair the cause of a warning.
Check: The scanner is disconnected, your notes are saved, and the vehicle is left in its original diagnostic state.
Common Mistakes to Avoid
- Clearing codes as soon as they appear. — Record codes, status, symptoms, and freeze-frame data first. Clear codes only after diagnosis or repair when there is a clear reason to do so.
- Replacing a part because its name appears in a code description. — Treat the code as a diagnostic clue. Check wiring, connectors, related codes, and vehicle-specific service information before replacing parts.
- Starting the engine or driving while trying to scan. — Follow the scanner’s ignition instructions and keep the vehicle parked. Never operate a handheld scanner while driving.
- Assuming a basic scanner checks every vehicle system. — Check the scanner’s supported systems and protocols. Use a compatible advanced scanner or a repair shop for ABS, airbag, or manufacturer-specific faults.
Troubleshooting
Problem: The scanner does not power on.
Solution: Confirm the connector is seated and the ignition is in the required position. Check the manual for power requirements. If another compatible scanner also fails, the vehicle’s diagnostic port fuse or wiring may need inspection.
Problem: The scanner powers on but cannot communicate.
Solution: Check the vehicle compatibility list, select the correct vehicle or protocol if prompted, and confirm the ignition state. Inspect the port for visible damage. Do not bridge pins or probe the port with improvised tools.
Problem: A wireless scanner will not pair with the phone.
Solution: Turn on Bluetooth or Wi-Fi as the scanner instructions require, open the companion app, and follow its pairing sequence. Remove an old pairing if instructed, then retry with the vehicle ignition on.
Problem: The scanner shows no codes, but a warning light remains on.
Solution: Check whether the scanner supports the system that triggered the light and whether it can read pending or manufacturer-specific codes. Record the warning and symptoms, then arrange a scan with suitable equipment if the light persists.
What Success Looks Like
The scan is complete when you have recorded each available code exactly, noted its status and any freeze-frame data, and matched the results with the vehicle’s symptoms. You have not mistaken a code description for a confirmed failed part, and you know whether to seek diagnosis, monitor the vehicle, or stop driving for safety.
Next Steps
Keep your scan notes with the vehicle’s maintenance records and share them with the repair technician. After the cause is repaired, scan again if the warning returns or the repair instructions call for verification. If codes were cleared, allow the vehicle’s emissions monitors to complete their checks before an inspection; follow local inspection rules and the vehicle manual.
Frequently Asked Questions
Can a diagnostic scanner tell me exactly which part is broken?
Usually not. A trouble code points to a detected condition, circuit, or system. Testing is needed to identify the cause, which may be a component, wiring, a connection, or another problem.
Can I use a scanner while the engine is running?
Many basic code scans work with the ignition on and engine off. Some live-data functions require the engine to run. Follow the scanner instructions, keep the vehicle parked, and avoid reaching near moving or hot parts.
Will reading codes damage my car or erase them?
Reading codes through a compatible scanner normally does not erase them. Choosing “clear codes” or “erase codes” can remove stored information and reset readiness monitors, so avoid that option until you have recorded the results.
Why does my scanner show no code when a warning light is on?
The scanner may not support the system that raised the warning, may not access manufacturer-specific codes, or may not show pending codes. Check its coverage and ask a repair shop to scan the relevant system if the warning continues.
