Engine Problems

Can I do a car diagnostic myself?

Yes, you can run a basic car diagnostic yourself with an OBD-II scanner. Learn how to read and interpret codes, use live data, and know when to see a professional.

On this page
  1. What a car diagnostic actually is
  2. Does your car have OBD-II?
  3. Tools for diagnosing a car at home
  4. How to read codes yourself
  5. Understanding trouble codes
  6. Going beyond codes: freeze frame, live data and readiness
  7. Should you clear the codes?
  8. Hands-on checks that don’t need a scanner
  9. What DIY diagnostics can’t do
  10. When to see a professional

Short answer: yes. On most cars built from the mid-1990s onward, you can read the same basic trouble codes a shop reads using an inexpensive OBD-II scanner or a smartphone adapter. It takes a few minutes. There’s a catch, though. A code tells you what the computer noticed, not necessarily which part has failed. A DIY diagnostic is a very good starting point. Confirming the actual cause often takes more testing.

What a car diagnostic actually is

The engine control module, and other modules for the transmission, ABS, airbags and so on, constantly monitor sensors and systems. When a reading falls outside expected limits under certain conditions, the module stores a diagnostic trouble code (DTC). If the fault affects emissions, it may also switch on the check engine light.

A “diagnostic” can mean two different things:

  1. Reading the stored codes and data, which anyone can do with a scanner
  2. Diagnosing the fault: using the codes, data and physical tests to find the root cause. This is what skilled technicians charge for.

Does your car have OBD-II?

  • United States: OBD-II has been required on cars and light trucks since the 1996 model year. Some 1994 and 1995 vehicles have it too.
  • European Union: the equivalent, EOBD, applies to petrol cars from around 2001 and diesel cars from around 2004.
  • Other markets have their own timelines.

The port is a 16-pin connector, usually under the dashboard on the driver’s side. Older vehicles may use manufacturer-specific systems that need special tools or adapters.

Tools for diagnosing a car at home

  • Basic code reader: reads and clears generic engine codes. It’s inexpensive and enough for many owners.
  • Bluetooth or Wi-Fi OBD-II adapter with a phone app: often shows live data and freeze frames as well as codes. Features depend heavily on the app.
  • Mid-range scan tool: adds manufacturer-specific codes and other modules such as ABS, airbags and transmission, and sometimes service resets.
  • Bidirectional scan tool: can command components on and off, for example running a fuel pump, cycling a solenoid or performing relearns. This is closer to professional equipment.
  • Other useful tools:
    • A multimeter for battery, charging and circuit checks
    • A compression gauge
    • A spark tester
    • A flashlight and inspection mirror
    • An infrared thermometer
    • Jack stands, if you’ll go under the car. Never work under a vehicle supported only by a jack.

How to read codes yourself

  1. Locate the OBD-II port. Check the owner’s manual if you can’t find it.
  2. Plug in the scanner with the ignition off.
  3. Turn the ignition on. Some tools also work with the engine running, as instructed.
  4. Read the codes, and write down every one, including pending codes if your tool shows them.
  5. Save or note the freeze frame data if available.
  6. Look up each code’s description for your specific vehicle, plus any manufacturer technical service bulletins if you can access them.

Many large auto parts chains will also read codes for free, which is a reasonable option if you don’t own a scanner.

Understanding trouble codes

OBD-II codes have five characters, for example P0301:

  • First letter: the system. P is powertrain (engine and transmission), B is body, C is chassis, U is network communication.
  • First digit: 0 generally means a generic code defined by the standard. 1 generally means manufacturer-specific. Some ranges are more complex.
  • Remaining digits: the specific fault. P0301, for example, is “cylinder 1 misfire detected.”

How to treat a code:

  • It’s a clue, not a verdict. P0171 (system too lean, bank 1) can come from a vacuum leak, a dirty MAF sensor, a weak fuel pump, a clogged injector or an exhaust leak. Replacing the oxygen sensor because it “reported” the problem often won’t fix it.
  • Multiple codes can share one cause. Look for the common link.
  • Check whether it’s current or historic. A code from weeks ago may be intermittent.

Our engine misfire guide shows how this works in practice for misfire codes.

Going beyond codes: freeze frame, live data and readiness

  • Freeze frame: a snapshot of conditions (speed, RPM, temperature, load and so on) when the code was set. This tells you when the fault happens, which is often the key to finding it.
  • Live data: real-time sensor readings. Useful items include:
    • Coolant temperature, to check whether the thermostat is opening properly
    • Short- and long-term fuel trims, which show how much the computer is adding or removing fuel to correct the mixture
    • MAF readings
    • Oxygen sensor activity
    • Throttle position
  • Readiness monitors: self-tests the car runs on its emissions systems. They show “complete” or “incomplete,” and many emissions inspections check them.

A practical example: large positive fuel trims at idle that improve as RPM rises often point toward a vacuum leak. Large positive trims at all speeds point more toward a fuel delivery or airflow measurement problem.

Should you clear the codes?

Clearing codes turns off the check engine light. It also:

  • Erases the freeze frame data that would help diagnose the problem
  • Resets readiness monitors, which may mean the car fails an emissions inspection until it has been driven enough for them to complete again
  • Doesn’t fix anything. If the fault is still present, the light will come back.

Record everything before clearing. Clearing after a repair is reasonable, as a way to confirm the fix.

Hands-on checks that don’t need a scanner

A lot of diagnosis is still done by eye, ear and nose:

  • Fluid levels and condition: oil, coolant, brake fluid, transmission fluid where checkable
  • Leaks and their colors
  • Belts and hoses
  • Battery voltage: a fully charged 12-volt battery at rest commonly reads around 12.6 volts. With the engine running, the charging system usually brings it up into the high 13s or low 14s. Specifications vary.
  • Noises and where they come from
  • Exhaust smoke color

Our main guide on how to diagnose engine problems explains how to combine these with code data into a step-by-step diagnosis.

What DIY diagnostics can’t do

  • Faults that set no codes: many mechanical problems, such as worn bearings, a weak water pump or a slipping belt, don’t set codes.
  • Pinpointing a failed part: confirming it may need a fuel pressure gauge, smoke machine, oscilloscope, compression or leak-down tester, or pressure tester.
  • Some modules and functions: airbag, ABS, key programming and some relearns may need professional or dealer-level tools.
  • Safety systems: airbags and high-voltage hybrid or EV components carry real injury risks and are best left to trained technicians.

When to see a professional

Get professional help if:

  • The check engine light is flashing, or the car is overheating, losing oil pressure or running very badly
  • The fault involves brakes, steering, airbags or high-voltage systems
  • You’ve replaced parts based on a code and the problem has returned
  • The problem is intermittent and you can’t reproduce it
  • You need testing equipment you don’t have

Arriving at a shop with your codes, freeze frame data and a clear description of when the problem happens can make the professional diagnosis faster.

The complete guide to engine problems

How to Diagnose Engine Problems: Symptoms, Causes and Fixes
Read the guide

Keep exploring

Guides from other topics

All topics →