What Common Problems Can an OBD2 Scanner Diagnose?

When a check engine light appears, my first question is simple: what did the vehicle’s computer actually detect? An OBD2 scanner helps answer that question before anyone starts replacing parts.

But there is an important difference between detecting a fault and diagnosing its root cause. I’ll explain which common problems a scanner can identify, what the codes mean, and when additional testing becomes necessary.

What Is an OBD2 Scanner, and How Does It Diagnose Problems?

An OBD2 scanner is a diagnostic tool that communicates with a vehicle’s on-board diagnostic system through a standardized connector. Its primary function is to retrieve information about monitored engine and emissions-system faults.

The vehicle’s control modules perform diagnostic checks while it operates. When a monitored system fails a defined test, the computer may store a diagnostic trouble code, or DTC.

• Diagnostic trouble codes: Identify monitored systems or conditions that failed a diagnostic test.
• Live data: Shows available readings such as engine speed, coolant temperature, and fuel trims.
• Freeze-frame data: Records selected operating conditions when a fault was detected.
• Readiness monitors: Indicate whether required emissions self-tests have completed.
• On-board test results: Some scanners display additional diagnostic monitor information through Mode 06.

For U.S.-market passenger cars and light trucks, OBD2 became standard starting with the 1996 model year. Other markets introduced comparable requirements on different schedules.

As of 2026, scanners range from basic code readers to advanced tools that communicate with multiple vehicle modules. Their diagnostic capabilities depend on both the scanner and the vehicle.

What Are the Most Common Problems an OBD2 Scanner Can Diagnose?

The most useful OBD2 diagnoses involve engine operation, fuel control, and emissions performance. These systems produce standardized trouble codes that many affordable scanners can retrieve.

1. Engine Misfires and Ignition Problems

An OBD2 scanner can detect engine misfire codes when the vehicle’s computer identifies abnormal combustion patterns. It may identify a specific cylinder or report misfires affecting multiple cylinders.

Misfires can cause shaking, hesitation, reduced power, and an illuminated check engine light.

• P0300: Random or multiple-cylinder misfire detected.
• P0301: Cylinder 1 misfire detected.
• P0302: Cylinder 2 misfire detected.
• P0303: Cylinder 3 misfire detected.
• P0304: Cylinder 4 misfire detected.

Potential causes include worn spark plugs, defective ignition coils, fuel injector problems, vacuum leaks, and mechanical compression issues. A code cannot reliably distinguish among those causes without further checks.

My preferred starting point is to record the affected cylinder and review freeze-frame data. That gives the diagnosis a direction without turning it into a guessing game.

Safety warning: A flashing check engine light can indicate a misfire severe enough to damage the catalytic converter. Reduce engine load, stop safely when necessary, and arrange prompt service rather than continuing to drive.

2. Oxygen Sensor and Air-Fuel Ratio Problems

An OBD2 scanner can report oxygen sensor circuit, heater, and response problems. Oxygen sensors help the engine computer evaluate exhaust conditions and manage fuel control.

Common codes include:

• P0130: Oxygen sensor circuit malfunction, Bank 1 Sensor 1.
• P0133: Oxygen sensor circuit slow response, Bank 1 Sensor 1.
• P0135: Oxygen sensor heater circuit malfunction, Bank 1 Sensor 1.
• P0141: Oxygen sensor heater circuit malfunction, Bank 1 Sensor 2.

A faulty sensor may contribute to poor fuel control or increased emissions. However, exhaust leaks, electrical faults, and engine operating problems can also trigger oxygen sensor-related codes.

Check the relevant wiring and sensor readings before buying a replacement. A sensor code describes a failed diagnostic test, not necessarily a failed sensor.

3. Catalytic Converter Efficiency Problems

An OBD2 scanner can identify when the vehicle’s catalyst monitoring system reports efficiency below its expected threshold. The familiar example is code P0420.

Another common code, P0430, reports catalyst efficiency below threshold on Bank 2, where applicable.

• P0420: Catalyst system efficiency below threshold, Bank 1.
• P0430: Catalyst system efficiency below threshold, Bank 2.

These codes do not automatically mean the catalytic converter must be replaced. Exhaust leaks, persistent misfires, incorrect fuel mixture, and sensor problems may affect catalyst monitoring.

I would check for accompanying misfire and fuel-control codes before considering an expensive converter replacement. Addressing an upstream engine problem is often necessary even when the converter itself is damaged.

4. Fuel System and Air-Fuel Mixture Problems

An OBD2 scanner can detect when the engine’s fuel-control system reports excessively lean or rich conditions. These codes are particularly useful when a vehicle idles poorly or hesitates under acceleration.

• P0171: System too lean, Bank 1.
• P0174: System too lean, Bank 2.
• P0172: System too rich, Bank 1.
• P0175: System too rich, Bank 2.

A lean condition means the measured or inferred mixture contains too much air relative to fuel. Possible causes include unmetered air leaks, low fuel delivery, or inaccurate airflow measurements.

Rich conditions may involve excessive fuel delivery, sensor errors, or other engine-control problems. Live short-term and long-term fuel trims can help narrow the investigation.

5. Mass Airflow and Intake Sensor Problems

A scanner can retrieve trouble codes involving mass airflow sensors, manifold pressure sensors, and related intake measurements. These sensors help calculate engine load and required fuel delivery.

• P0100: Mass or volume airflow circuit malfunction.
• P0101: Mass or volume airflow circuit range/performance problem.
• P0102: Mass or volume airflow circuit low input.
• P0106: Manifold absolute pressure/barometric pressure circuit range/performance problem.

Common symptoms include sluggish acceleration, irregular idle speed, stalling, and increased fuel consumption. Some faults also trigger reduced-power operating modes.

Inspect intake ducts, connectors, and related vacuum hoses before condemning a sensor. A damaged intake hose can create symptoms similar to an incorrect airflow reading.

6. Evaporative Emissions System Leaks

An OBD2 scanner can detect leaks and control faults in the evaporative emissions system, commonly called EVAP. This system helps prevent gasoline vapors from escaping into the atmosphere.

• P0440: EVAP system malfunction.
• P0442: Small EVAP leak detected.
• P0455: Large or gross EVAP leak detected.
• P0456: Very small EVAP leak detected.
• P0441: Incorrect EVAP purge flow.

A loose or damaged fuel cap is one possible cause, although not every vehicle uses a conventional cap. Purge valves, vent valves, hoses, and canisters can also cause faults.

The scanner can identify the reported leak condition, but it generally cannot pinpoint the physical opening. Repair shops often use an appropriate smoke-testing procedure to locate difficult leaks.

7. Exhaust Gas Recirculation Problems

An OBD2 scanner can identify certain exhaust gas recirculation (EGR) faults. The EGR system controls exhaust-gas recirculation to help manage combustion temperatures and emissions.

• P0400: EGR flow malfunction.
• P0401: Insufficient EGR flow detected.
• P0402: Excessive EGR flow detected.

Depending on the vehicle, problems may involve carbon buildup, restricted passages, valves, sensors, or electrical connections. Rough running and reduced engine performance can accompany some EGR faults.

Vehicle-specific testing is important because EGR designs vary. Many newer engines use different emissions-control strategies than older vehicles.

8. Transmission and Powertrain Control Problems

Some transmission problems produce standard powertrain codes that a basic OBD2 scanner can read. However, detailed transmission diagnostics often require enhanced scanner access to the transmission control module.

• P0700: Transmission control system has requested the malfunction indicator light.
• P0715: Input/turbine speed sensor circuit malfunction.
• P0720: Output speed sensor circuit malfunction.
• P0740: Torque converter clutch circuit malfunction.

P0700 is especially important because it may simply indicate that the transmission controller stored additional information. A basic reader might not display those underlying manufacturer-specific codes.

If a vehicle shifts harshly, slips, or loses drive, avoid assuming a sensor is responsible. Fluid condition, wiring, hydraulic problems, and internal transmission damage may require professional diagnosis.

OBD2 Trouble Codes: Common Problems Compared

This comparison table summarizes common code examples and the diagnostic checks they suggest. None of these codes alone confirms a specific replacement part.

Problem Area	Example Code	Possible Causes	Useful Next Check
Engine misfire	P0301	Ignition, fuel, compression	Check affected cylinder
Lean fuel mixture	P0171	Air leak, fuel delivery, sensor error	Review fuel trims
Oxygen sensor circuit	P0135	Heater circuit, wiring, sensor	Inspect circuit and power supply
Catalyst efficiency	P0420	Converter, exhaust leak, engine fault	Check upstream problems
EVAP leak	P0455	Fuel cap, hose, valve, canister	Inspect seals and EVAP system
Airflow sensor	P0101	Airflow reading, intake, wiring	Inspect intake and live MAF data
EGR flow	P0401	Restricted passages, valve, control fault	Perform EGR-specific testing
Transmission control	P0700	Transmission controller reported a fault	Read enhanced TCM codes

To understand the standardized diagnostic framework, consult the U.S. Environmental Protection Agency and the SAE International resources on vehicle diagnostics.

Can an OBD2 Scanner Diagnose ABS, Airbag, or Battery Problems?

A basic OBD2 scanner generally cannot diagnose every ABS, airbag, battery, or body-control problem. Access to these systems requires compatible vehicle-specific features that go beyond standard emissions diagnostics.

• ABS warning lights: Enhanced tools may read wheel-speed sensor and ABS module codes.
• Airbag warning lights: Compatible scanners may retrieve supplemental restraint system faults.
• Tire pressure monitoring: Dedicated TPMS or enhanced diagnostic functions may be necessary.
• Charging problems: Live voltage data may provide clues, but dedicated electrical tests are needed to confirm battery or alternator faults.
• Transmission modules: Enhanced coverage may unlock codes and data unavailable through generic OBD2.

An engine scanner showing no codes does not prove these systems are functioning correctly. It may simply lack access to the module storing the fault.

For comparison, a basic code reader usually focuses on standardized engine and emissions information. An advanced all-system scanner may support ABS, SRS, transmission, and body controllers on specified vehicles.

How Do You Diagnose a Car Problem With an OBD2 Scanner?

Start by retrieving all available diagnostic information before making repairs or clearing the memory. Following a consistent sequence helps preserve evidence and prevents unnecessary replacement costs.

1. Park safely: Switch off the engine and locate the diagnostic connector, usually beneath the driver’s dashboard.
2. Connect the scanner: Insert the OBD2 connector carefully without forcing it.
3. Turn on the ignition: Use the ignition-on, engine-off position unless your scanner directs otherwise.
4. Read all codes: Record stored, pending, and permanent codes where supported.
5. Save freeze-frame data: Capture engine speed, temperature, load, and other available fault conditions.
6. Review relevant live data: Check readings associated with the reported fault.
7. Inspect likely causes: Use the vehicle’s service information and appropriate diagnostic tests.
8. Confirm the repair: Recheck codes and operating behavior after correcting the actual problem.

For a more detailed workflow, read this guide on how to diagnose a check engine light with OBD2.

What Should You Do When the Scanner Shows Several Codes?

Multiple codes can come from a shared problem, so diagnosing each one independently may waste time. Start with symptoms, code status, and the conditions recorded when the faults occurred.

For example, a significant engine misfire may affect catalytic converter monitoring. Investigating the misfire first is more sensible than immediately replacing the converter.

• Record every code before clearing anything.
• Identify codes connected to the same operating system.
• Check whether a common wiring, air, fuel, or power-supply fault could explain several codes.
• Use manufacturer service information to choose the next diagnostic test.

Can Live OBD2 Data Help Find Problems Without a Trouble Code?

Yes, live OBD2 data can reveal suspicious operating conditions even when no diagnostic trouble code is stored. However, a scanner must support the required parameters, and unusual readings need careful interpretation.

Common live-data parameters include:

• Engine RPM: Shows reported engine speed.
• Coolant temperature: Helps evaluate engine warm-up and temperature sensor behavior.
• Short-term fuel trim: Shows the computer’s immediate fuel adjustments.
• Long-term fuel trim: Shows longer-term learned fuel corrections.
• Mass airflow: Reports measured airflow on vehicles equipped with that sensor.
• Throttle position: Shows the reported throttle opening or related position reading.

Suppose an engine idles roughly but has not stored a code. Comparing fuel trims, airflow, temperature, and operating symptoms may suggest which system deserves closer inspection.

There is no single normal reading for every vehicle or operating condition. Compare values against manufacturer specifications and the engine’s actual state.

What Can an OBD2 Scanner Not Diagnose Reliably?

An OBD2 scanner cannot directly diagnose every mechanical or electrical problem. It reports what supported control modules can monitor, not everything happening inside the vehicle.

• Mechanical wear: Worn bearings, damaged suspension bushings, and similar components may not generate codes.
• Physical fluid leaks: Oil and coolant leaks generally require visual inspection or pressure testing.
• Internal engine damage: Compression, leak-down, and other mechanical tests may be necessary.
• Brake pad wear: Many vehicles lack standardized diagnostic information for this condition.
• Intermittent wiring faults: Some problems require electrical measurements and controlled testing.
• Every module fault: Unsupported manufacturer-specific systems remain outside the scanner’s capabilities.

This is why I treat the scanner as the beginning of a diagnostic process rather than the entire process. It can show where to investigate, but it cannot inspect a cracked hose or measure cylinder compression for you.

Can Clearing OBD2 Codes Fix the Problem?

No. Clearing an OBD2 trouble code erases eligible diagnostic information but does not repair the underlying mechanical or electrical fault.

The check engine light may turn off temporarily after clearing codes. If the monitored fault remains, the vehicle may detect it again once the relevant conditions occur.

Clearing emissions codes can also reset readiness monitors and remove useful freeze-frame information. That matters when a vehicle is approaching an emissions inspection.

For a closer explanation, see whether an OBD2 scanner can turn off the check engine light.

Practical tip: Save the codes and related diagnostic data before clearing anything. After a confirmed repair, allow the vehicle to complete the required self-tests and check that the problem does not return.

Can an OBD2 Scanner Help When Buying a Used Car?

Yes. A pre-purchase OBD2 scan can reveal stored powertrain faults, pending codes, and incomplete emissions readiness checks that might not be obvious during a short test drive.

A scanner cannot certify the condition of the engine, transmission, body, or safety systems. It is a useful supplement to a professional pre-purchase inspection.

• Check for stored and pending trouble codes.
• Review permanent codes if the vehicle supports them.
• Inspect readiness monitor status.
• Compare live data with the vehicle’s operating condition.
• Investigate warning lights that the basic scanner cannot access.

A vehicle with incomplete readiness monitors is not necessarily defective. The monitors may simply not have finished their tests after recent repairs or a diagnostic reset.

Learn how to interpret those results in this guide to checking readiness when buying a used car.

Which OBD2 Scanner Should You Choose for Common Car Problems?

For occasional check engine light diagnosis, a basic scanner that reads codes, freeze-frame data, live information, and readiness monitors is often enough. For multiple vehicles or advanced systems, consider enhanced diagnostic support.

Before buying, confirm compatibility with your exact year, make, model, and desired functions. Manufacturer resources from OBDLink and Autel can help clarify supported capabilities.

If you’re ready to choose a scanner, these three models suit different diagnostic needs.

Product ratings above are editorial suitability assessments for the stated use cases, not verified customer review averages or hands-on test scores. As an Amazon Associate, we earn from qualifying purchases.

Frequently Asked Questions

Can an OBD2 scanner diagnose a bad spark plug?

An OBD2 scanner can detect misfire conditions that may result from a worn or faulty spark plug. However, a misfire code cannot confirm that the spark plug is the cause, because ignition coils, fuel injectors, wiring, and mechanical faults can produce similar symptoms. Physical testing is needed.

Can an OBD2 scanner detect a bad fuel pump?

An OBD2 scanner may report lean fuel conditions, fuel-pressure faults, or performance problems related to inadequate fuel delivery. It generally cannot confirm a failed fuel pump by itself. A proper diagnosis may require measuring fuel pressure, checking electrical supply, and following manufacturer-specific tests.

Will an OBD2 scanner detect every check engine light problem?

A compatible scanner can retrieve many standardized emissions-related codes that trigger the check engine light. However, manufacturer-specific faults, communication failures, and unsupported systems may require a more advanced diagnostic tool. Even when a code is available, additional testing is often needed to identify the root cause.

Can I drive with an OBD2 trouble code?

That depends on the fault and the vehicle’s symptoms. Some emissions-related problems allow limited driving while arranging a repair, but a flashing check engine light, severe shaking, overheating, or substantial power loss requires prompt attention. Never judge driving safety from the code alone.

Is a cheap OBD2 scanner enough for home mechanics?

A basic scanner is useful for reading common engine codes, checking emissions readiness, and sometimes viewing live sensor data. It can handle the first stage of many home diagnostic tasks. For ABS, airbags, transmission modules, or active component tests, verify whether a more capable scanner is necessary.

Final Takeaway: What Problems Can an OBD2 Scanner Diagnose?

An OBD2 scanner can identify many common engine and emissions faults, including misfires, fuel mixture issues, oxygen sensor problems, catalytic converter efficiency faults, and EVAP leaks. More advanced scanners can also access additional vehicle systems when compatible.

The most important habit is to treat every trouble code as a diagnostic clue rather than a repair instruction. Record the code, examine supporting data, test likely causes, and confirm the repair.

Start with a scanner that fits your vehicle and diagnostic needs. It can make troubleshooting more focused and help you communicate clearly with a mechanic when professional testing is required.