▶ TrainingGet Pro
All tools & lessonsAll toolsAllGet the appApp
Learning departments Music, Maths, Cookery, Programming and Art are open – explore →

On-board diagnostics: OBD and fault codes – Motor Vehicle Theory motor mechanics lesson

Lesson 110 of 131 in the Motor Vehicle Theory course (ages 16+)

UK version. UK spelling and words (tyre, petrol, bonnet) and UK rules such as the MOT. · US version

Find out how on-board diagnostics watch the engine and emissions systems, what the engine warning light and fault codes really mean, and why a code is the start of a diagnosis, not the answer.

Time
45 minutes + 10 min homework
Course
Motor Vehicle Theory (ages 16+)
You need
Paper, a pencil and this page. No tools and no vehicle
Marked
Instantly, with explanations

Education and interest only. Classfern teaches motor mechanics as a school subject. It is not a training course or a qualification, and nothing here replaces an IMI or City & Guilds course, an apprenticeship or a qualified technician. Never work on a real vehicle without a qualified adult, the right protective equipment and safe equipment. High-voltage parts of electric and hybrid vehicles are for trained technicians only. Rules and values on this page are given as of November 2026. Always check the current official source (GOV.UK and the DVSA MOT inspection manual) before relying on them.

How to use this lesson

This lesson explains on-board diagnostics and fault codes. Reading and clearing codes on a real vehicle is left to trained technicians; the activity is look-only with an adult. Every answer is marked straight away with a worked explanation.

  1. Read what you will learn and the big ideas.
  2. Press Start the lesson below for the teaching, worked examples and practice (Getting started, On track or Challenge).
  3. Finish with the exit ticket and the talk question: “Some drivers cover up the engine warning light or ignore it for months. What could the consequences be, for the car, the driver and the environment?”
  4. Later: the homework, then the practice test.

Watch out for

  • Thinking a fault code tells you which part to replace. A code shows where the control unit saw a problem. Wiring, connections or another system may be the real cause, so testing comes next.
  • Thinking clearing the code fixes the fault. Clearing only erases the record and resets the readiness monitors. The fault returns when the self-test runs again.
  • Thinking a flashing engine lamp is less serious than a steady one. A flashing light warns of a fault that could damage the catalytic converter, so it is more urgent.

Hands-on: With an adult, sit in a parked car and switch the ignition on without starting the engine. Watch the engine warning lamp light for its bulb check, then go out once the engine is started (if the adult starts it outdoors). Find the diagnostic socket's position in the vehicle handbook – look only, do not plug anything in. Then decode these made-up codes on paper: P0301, P0420, B1000, U0100.

What you will learn

  • I can explain what on-board diagnostics do and why they were introduced.
  • I can explain the difference between a steady and a flashing engine warning light.
  • I can read the structure of a standard fault code.
  • I can explain why a fault code points to an area to test rather than a part to replace.

Key words

on-board diagnostics (OBD)
Self-checking routines in a vehicle's control units that monitor parts affecting emissions and store information when something goes wrong.
malfunction indicator lamp (MIL)
The engine warning light on the dashboard, usually an engine symbol. It comes on when the system detects a fault.
fault code
A stored code, such as P0301, that tells a technician which system or circuit the control unit found a problem in.
readiness monitor
A record of whether each self-test has been completed since the codes were last cleared.
freeze frame
A snapshot of sensor values stored at the moment a fault was detected.

The big ideas

Modern engines are controlled so precisely that a small fault – a misfire, a failing sensor, a leaking fuel vapour hose – can raise emissions long before the driver notices anything. On-board diagnostics were introduced so the vehicle could watch itself.

The idea began in California. The California Air Resources Board explains that its first on-board diagnostic rules (OBD I, from the 1988 model year) monitored only a few emission-related parts, while OBD II monitors "virtually every component that can affect emission performance". Cars sold in Europe have a similar standardised system, and most use the same type of diagnostic socket and code format.

When the system finds a problem it lights the engine warning lamp and stores information so a technician can find and fix it. This lesson explains what that information means. Reading codes and diagnosing faults is work for a trained technician with the right equipment.

Read-through: the teaching steps

  1. What OBD watches

    The engine control unit runs self-tests ("monitors") on the parts that affect emissions, including:

    • misfire detection – watching crankshaft speed for the tiny slowdown a misfire causes;
    • the catalytic converter, using oxygen sensors before and after it;
    • the oxygen sensors themselves;
    • the fuel system and fuel trim;
    • the evaporative emission system that stops fuel vapour escaping;
    • exhaust gas recirculation, where fitted;
    • sensors and actuators that could affect emissions.

    Some monitors run all the time; others need particular driving conditions to complete.

  2. The engine warning lamp

    The malfunction indicator lamp (usually an engine symbol) tells the driver the system has found a fault. CARB's guidance explains the two signals:

    • Steady light – a malfunction has been detected; most manufacturers advise having it checked as soon as conveniently possible.
    • Flashing light – a malfunction is happening that could damage the catalytic converter (often a severe misfire); have it checked as soon as possible.

    A lit lamp does not only mean higher emissions: the fault can also affect fuel economy, performance or driveability.

  3. Reading a fault code

    Standard codes have five characters, for example P0301:

    • First letter – the system: P powertrain (engine and transmission), B body, C chassis, U network communication.
    • First digit – 0 for a generic code defined by the standard, 1 for a manufacturer-specific code.
    • Remaining digits – the sub-system and the particular fault. P0301, for example, is commonly a misfire detected in cylinder 1.

    The code is read with a scan tool plugged into the diagnostic socket, usually under the dashboard near the driver.

  4. A code is not a part number

    A code tells the technician where the control unit saw something wrong, not which part has failed. A code for an oxygen sensor signal could be caused by the sensor, its wiring, an exhaust leak, or the engine running genuinely rich or lean.

    So the technician uses the code as the start of a logical routine: look at freeze-frame data (the conditions when the fault was set), check live data, consult the manufacturer's test procedure for that code, and test before replacing anything.

  5. Readiness monitors and clearing codes

    Each monitor records whether its self-test has run since the codes were last cleared. CARB notes that a technician uses a scan tool to see which readiness monitors are incomplete.

    Clearing codes also resets the monitors to "not ready". That is why simply clearing a code does not fix anything: the fault returns when the monitor runs again, and the vehicle has to be driven in the right conditions before all monitors are complete.

  6. OBD and the wider vehicle

    Beyond the engine, modern vehicles store codes in many control units – brakes, airbags, body, gearbox – often in manufacturer-specific formats. Full diagnosis needs equipment and information that can talk to them all.

    Codes in safety systems such as airbags and brakes are always investigated by a trained technician with the manufacturer's procedures.

The lesson, step by step

45 minutes in 5 parts
PartTimeHow it is checked
Starter: warm up4 minMarked by Classfern
Teaching and hands-on task14 minNot assessed, self-checked
Worked examples and guided practice9 minMarked by Classfern
Independent practice (three levels)13 minMarked by Classfern
Exit ticket and talk question5 minMarked by Classfern, self-checked

Make my lesson plan Opens this lesson in the free Lesson Plan Maker, filled in and ready to change, print or save.

The lesson

It runs here on the page. No sign-up and no names – progress is kept only in this browser.

Homework

About 10 minutes: 6 questions and a one-line reflection, all marked instantly.

More practice

More Fault-finding lessons · Motor Vehicle Theory course · All motor mechanics practice tests · Motor Mechanics Department

Sources and curriculum

Facts in this lesson were checked against:

Our lessons and questions are our own. They are not written or endorsed by the DVSA, the IMI, City & Guilds, any college, testing agency or exam board.