Use this guide to connect a diagnostic scanner to a car, retrieve and record fault codes, and check basic live data. It is for drivers with little or no diagnostic experience who want to understand a warning light before choosing a next step. Allow 15-30 minutes; the time depends on the scanner and the vehicle.
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 Professional Mechanic OBDII Diagnostic Code Reader Tool
- ✔ Model: NT301
- ✔ Display: 2.8-inch color screen
- ✔ Supported protocols: KWP2000, J1850 VPW, ISO9141, J1850 PWM, CAN
ANCEL AD410 Enhanced OBD2 Scanner
- ✔ Model: AD410
- ✔ Display: 2.4-inch color screen
- ✔ Supported protocols: CAN, ISO9141, KWP2000, J1850 VPW, J1850 PWM
ANCEL AD310 Classic Enhanced Universal OBD II Scanner – Car Engine Fault Code Reader with CAN Diagnostic Scan Tool (Black)
- ✔ Model: AD310
- ✔ Weight: 12 ounces
- ✔ Dimensions: 8.9 x 6.9 x 1.4 inches
Difficulty: Beginner | Time: 15-30 minutes
What You’ll Need
Tools & Materials:
- OBD-II diagnostic scanner compatible with the vehicle
- Vehicle owner’s manual
- Phone or notebook for recording codes and symptoms
Knowledge:
- Ability to locate the vehicle’s diagnostic connector
- Ability to follow scanner prompts and read displayed codes
Most gasoline cars sold in the United States from model year 1996 onward support OBD-II. Other regions and vehicle types may use different rules or connectors. Check the owner’s manual or scanner compatibility list before connecting. A basic scanner may read engine and emissions codes but may not access anti-lock brake, airbag, transmission, or manufacturer-specific systems.
FOXWELL NT301 OBD2 Scanner Live Data Professional Mechanic OBDII Diagnostic Code Reader Tool
The FOXWELL NT301 is the most capable all-around choice here for owners who want to look beyond a check-engine code. It reads and clears engine fault codes, but its real advantage over the AD310 is live sensor data shown as graphs. A graph can make changing readings easier to follow than a list of numbers, which is useful when we are trying to understand when a symptom occurs or whether a reading changes with engine operation. Its 2.8-inch color screen also gives the information more room than the AD410’s specified 2.4-inch display.For emissions preparation, the NT301 adds I/M readiness indicators and hotkeys, making it simpler to check whether a vehicle’s monitors report ready. That is a convenience, not a guarantee that the vehicle will pass an inspection: readiness status and actual inspection results are different things. Compared with the AD410, this model emphasizes graph-based data and readiness checks over a large built-in DTC lookup count. Buyers who primarily want a plain code definition may prefer the AD410’s stated 42,000-plus lookup library.The NT301 is still an engine and emissions scanner, not a full vehicle diagnostic platform. It does not provide dedicated ABS, SRS, TPMS, or battery-health diagnostics, and it is not described as supporting transmission systems or bidirectional controls. The stated compatibility includes 1996-and-newer gasoline cars, light trucks, and SUVs, many 2000-and-newer European and Asian models, and 12V diesel vehicles; we should verify support for our exact vehicle before relying on it. Choose it when engine data is the priority, and skip it if our warning light points to a system outside its coverage.
Pros:
- Graphs live sensor data to make changing readings easier to interpret.
- I/M readiness hotkeys and indicators simplify checking emissions-monitor status.
- 2.8-inch color screen offers a clear interface for reviewing scanner output.
- Supports major OBDII protocols and a broad stated range of compatible vehicles.
Cons:
- Does not provide dedicated ABS, SRS, TPMS, or battery-health diagnostics.
- Its engine-focused coverage cannot substitute for a full-system diagnostic tool.
- Vehicle compatibility and available functions can vary by make, model, and year.
Best for: Owners who want graph-based live engine data and a straightforward emissions-readiness check alongside basic code reading.
Not ideal for: Drivers who need ABS, airbag, TPMS, battery, or transmission diagnostics, or who want bidirectional control functions.
Bottom line: We rank the NT301 first because it combines useful graph-based live data with emissions readiness checks, while keeping its scope focused on OBD2 engine diagnostics.
“We rank the NT301 first because it combines useful graph-based live data with emissions readiness checks, while keeping its scope focused on OBD2 engine diagnostics.”
ANCEL AD410 Enhanced OBD2 Scanner
The ANCEL AD410 is a good middle ground for owners who want more explanation than a basic reader provides without depending on a phone app. Its standout feature is a stated library of 42,000-plus built-in DTC lookups, with multilingual on-screen code definitions. That can help us understand what a stored code refers to before researching a repair or speaking with a shop. Unlike the NT301, its appeal centers on built-in code help rather than a specifically described graphing interface.It also reads and clears engine and emission fault codes, streams live data such as RPM and coolant temperature, and checks I/M readiness for smog inspections. With a 2.4-inch color screen and no need for an external power source or phone app, it is designed for a self-contained workflow. Compared with the AD310, the AD410 gives buyers more on-screen interpretation and a color display; compared with the NT301, it offers a larger stated code lookup library but a smaller screen and less emphasis on graph-based analysis.Its coverage remains limited to OBD2 engine and emissions functions. The AD410 does not read ABS, SRS, transmission, or bidirectional control codes, so a warning outside the engine system may require a different scanner or a professional diagnostic session. Compatibility is described as most 1996-and-newer U.S. vehicles and many 2000-and-newer European and Asian models, but those broad categories are not a substitute for checking a specific vehicle. Choose this model when understandable code references matter; look to the NT301 if visual live-data analysis is more important.
Pros:
- Built-in DTC lookup library provides on-screen code definitions without a phone app.
- Streams live data including RPM and coolant temperature.
- I/M readiness function can help check emissions-monitor status.
- Color display and standalone operation keep basic checks self-contained.
Cons:
- Does not diagnose ABS, SRS, transmission, or bidirectional control systems.
- Specified display is smaller than the NT301’s 2.8-inch screen.
- Vehicle support varies, particularly across regional models and specific functions.
Best for: DIY owners who want code definitions directly on the scanner, plus basic live data and emissions-readiness checks.
Not ideal for: Users who need graph-focused sensor analysis, broad all-system coverage, or transmission and bidirectional functions.
Bottom line: We recommend the AD410 for owners who value built-in code explanations and standalone operation more than the NT301’s larger, graph-oriented presentation.
“We recommend the AD410 for owners who value built-in code explanations and standalone operation more than the NT301’s larger, graph-oriented presentation.”
ANCEL AD310 Classic Enhanced Universal OBD II Scanner – Car Engine Fault Code Reader with CAN Diagnostic Scan Tool (Black)
The ANCEL AD310 is the straightforward pick when our main goal is to read and clear an engine or emissions-related trouble code. It supports the major OBDII protocols listed for the other two models, including CAN, and works with compatible OBD2 vehicles from 1996 onward. It needs no batteries or external power, so we can keep it in a glove compartment or garage and connect it when the warning light appears. Its simple focus is the reason to choose it: we get essential code access without stepping up to the AD410’s built-in definitions or the NT301’s graph-based live-data presentation.The AD310 also reports live data, freeze-frame information, and vehicle information. Freeze-frame data can preserve a snapshot associated with a fault, giving us context beyond the code name itself. That makes it more useful than a code-only device, but its scope is still narrower in practical interpretation than the other picks. The NT301 is the stronger choice for graphing sensor readings, while the AD410 is better suited to buyers who want built-in code descriptions. The AD310 suits a basic check-and-clear workflow, provided we understand that a code identifies a system or condition rather than confirming which part to replace.Its limits are central to the buying decision. The AD310 handles emission-related diagnostics only; it does not scan ABS, SRS, or transmission systems, and an adapter cannot make it work with older OBDI ports. The supplied specifications list a 2.5-foot cable, which gives some reach from the diagnostic connector but may be less convenient depending on the vehicle’s port location. Pick it for routine engine-code checks on a compatible vehicle. Skip it if we want on-screen code explanations, deeper live-data interpretation, or access to non-engine systems.
Pros:
- Reads and clears emission-related trouble codes on compatible OBD2 vehicles.
- Displays live data, freeze frames, and vehicle information.
- Supports major OBDII protocols, including CAN.
- Requires no batteries or external power source.
Cons:
- Limited to emission-related diagnostics; it does not cover ABS, SRS, or transmission systems.
- Cannot scan older OBDI vehicles, even when used with an adapter.
- Offers less built-in interpretation than the AD410 and less graph-oriented analysis than the NT301.
Best for: Owners who want a compact, uncomplicated tool for reading and clearing engine or emissions codes on a compatible OBD2 vehicle.
Not ideal for: Buyers who need dedicated system diagnostics, built-in code definitions, or graph-based live sensor analysis.
Bottom line: We choose the AD310 for basic engine-code checks when simplicity matters more than code explanations or detailed live-data analysis.
“We choose the AD310 for basic engine-code checks when simplicity matters more than code explanations or detailed live-data analysis.”
As an Amazon Associate we earn from qualifying purchases.
Before You Start
Park on a level surface, select Park or Neutral, apply the parking brake, and switch off the engine. Keep the ignition off while plugging in the scanner unless its instructions say otherwise. Do not use a scanner while driving. If the check-engine light is flashing, the engine is overheating, or the car has severe power loss or unusual noises, stop driving when safe and seek qualified help; a code reading does not make continued driving safe.
Do not clear codes before recording them. Clearing can erase diagnostic information and reset emissions readiness monitors, making later diagnosis harder.
Step-by-Step Instructions
Step 1: Find the diagnostic connector
Check the owner’s manual for the OBD-II connector location. It is commonly beneath the dashboard near the steering column, but it may sit behind a small cover or in another nearby panel. Inspect the area without forcing trim or unplugging other connectors.
Tip: If you cannot find the port, search the manual’s index for “data link connector” or “OBD.”
Check: You can see a 16-pin trapezoid-shaped socket that matches the scanner plug.
Step 2: Connect the scanner
With the ignition off, align the scanner plug with the connector and push it in gently. Do not force it or bend the pins. If the scanner uses a phone app or wireless adapter, follow its pairing instructions and use the vehicle’s stationary state for setup.
Tip: A plug that does not fit may indicate the wrong connector, an adapter requirement, or an incompatible scanner. Stop and check compatibility instead of forcing it.
Check: The plug is fully seated and the scanner powers on, or the app recognizes its adapter.
Step 3: Turn on the ignition
Switch the ignition to the On position without starting the engine, if the vehicle permits this. For a push-button start, follow the owner’s manual for accessory or ignition-on mode; usually this means pressing the button without pressing the brake. The dashboard lights should illuminate. Some scanners ask you to start the engine for live data, so follow the prompt when it appears.
Tip: Do not guess with push-button controls; starting the engine can change the readings or the scanner’s connection state.
Check: The scanner displays a vehicle connection, system selection, or menu.
Step 4: Select the vehicle and scan for codes
Choose the vehicle’s make, model, year, and engine if the scanner requests them. Select the engine or OBD-II diagnostics option, then choose a function such as Read Codes or Scan. Wait for the scan to finish without unplugging the tool or switching off the ignition.
Tip: Some scanners identify the vehicle automatically, while others use generic OBD-II mode. Use the scanner’s manual if a menu label differs.
Check: The scanner reports that the scan is complete and shows codes, a no-code result, or the systems it could not access.
Step 5: Record the results before changing anything
Write down each code exactly as shown, including its letter and digits, and note whether it is stored, pending, or permanent. Record any displayed description, freeze-frame data, and the date. Also note when the warning appeared, how the car behaved, and recent events such as refueling or battery replacement.
Tip: A code description points to a circuit or condition; it does not prove that the named part has failed. Preserve the full code and context for diagnosis.
Check: You have a readable record of every code and the symptoms that occurred with it.
Step 6: Review available live data
If the scanner offers live data, select a few relevant values such as engine speed, coolant temperature, fuel trim, or oxygen-sensor readings. Compare readings only under the conditions the scanner or repair information specifies. Start the engine only if needed, keep the vehicle parked, and keep hands, clothing, and cables away from moving or hot parts.
Tip: Live readings vary with engine temperature, load, and vehicle design. Do not treat a single number as a diagnosis without vehicle-specific specifications.
Check: The scanner displays changing values, or clearly indicates that live data is unavailable on this tool or vehicle.
Step 7: Look up the code and choose a next action
Use the owner’s manual, a trusted repair reference, or a qualified technician to interpret the exact code for your vehicle. Check for safety-related symptoms and any manufacturer-specific information. Decide whether the issue needs prompt inspection, a targeted test, or routine follow-up; do not replace parts based only on a generic code description.
Tip: If the code involves brakes, airbags, steering, or a flashing engine warning, arrange professional diagnosis promptly.
Check: You have a documented code and a reasonable next diagnostic or repair step, rather than an unverified parts guess.
Step 8: Disconnect and store the scanner
Turn the ignition off and wait for the scanner to finish any operation. Unplug it by holding the connector body, not pulling the cable. Store the scanner and your notes together. Leave the codes uncleared unless a repair procedure calls for clearing them after the issue is addressed.
Tip: If the scanner or vehicle manual requires a different shutdown sequence, follow that sequence.
Check: The scanner is disconnected without damage, and your code record is saved.
Common Mistakes to Avoid
- Clearing codes as soon as they appear. — Record codes, status, freeze-frame details, and symptoms first. Clear codes only after diagnosis or repair when appropriate.
- Replacing a part named in the scanner’s code description. — Treat the code as a clue. Confirm the cause with vehicle-specific diagnostic tests before buying parts.
- Using a scanner that cannot access the needed system. — Check whether the tool supports the vehicle and the system you need; basic OBD-II readers may only cover engine and emissions.
- Leaving a scanner connected while driving or working near moving parts. — Take readings while parked and keep cables and hands clear of hot or moving components.
Troubleshooting
Problem: The scanner does not power on.
Solution: Check that the connector is fully seated and the ignition is in the required position. Consult the manual for scanner power requirements. If it still does not power on, the vehicle connector may lack power or have a fuse issue; avoid probing pins unless you know the correct procedure.
Problem: The scanner cannot communicate with the vehicle.
Solution: Turn the ignition off, reseat the plug, and retry in the specified ignition mode. Confirm vehicle compatibility and check whether the scanner needs a software update or vehicle selection. If communication still fails, seek a technician to inspect the connector or vehicle network.
Problem: The scanner shows no codes, but a warning light remains on.
Solution: Confirm you selected the engine or correct system and that the scanner supports it. Some warnings are stored in modules a basic reader cannot access. Use a capable scan tool or arrange a professional scan.
Problem: A code returns after being cleared or after a repair.
Solution: Record the returning code and note when it reappears. The underlying fault may remain, the repair may need verification, or a related issue may exist. Use the vehicle-specific diagnostic procedure or consult a qualified technician.
What Success Looks Like
You have completed the scan when the scanner has connected without damage, any available codes and their status are recorded exactly, relevant symptoms and readings are noted, and you have selected a sensible next diagnostic step. A no-code result is also a valid scan result, but it does not rule out every mechanical or electrical problem.
Next Steps
Keep your notes with the vehicle’s service records. After a confirmed repair, follow the repair instructions or technician’s advice about clearing codes and verifying the repair. Rescan if the warning returns or symptoms change. Arrange professional diagnosis if the scanner cannot reach the needed system, the code is unclear, or the vehicle shows serious symptoms.
Frequently Asked Questions
Can I use a diagnostic scanner while the engine is running?
Use the scanner while parked. Some live data requires the engine to run, so start it only when the tool requests it and the vehicle can remain safely stationary. Never handle the scanner while driving.
Will a basic scanner read airbag or ABS codes?
Often it will not. Many basic OBD-II scanners cover engine and emissions faults only. Check the tool’s supported systems for your specific vehicle before relying on it for ABS, airbag, transmission, or other module codes.
Does a fault code tell me which part to replace?
No. A code identifies a detected condition, circuit, or system. A sensor, wiring, connector, vacuum leak, or another fault may produce a similar code. Confirm the cause with appropriate tests.
Should I erase codes after reading them?
Usually, leave them stored until the cause has been diagnosed and repaired. Erasing codes can remove useful information and reset emissions readiness monitors. Follow the repair procedure or a technician’s advice.
What if the scanner says no codes are present?
Record that result and note the warning or symptom. The scanner may not support the affected system, the issue may be intermittent, or the problem may not set an OBD-II code. Seek a more capable scan or professional diagnosis if the symptom continues.
