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

Software in cars: updates and diagnostics – Vehicles and Technology motor mechanics lesson

Lesson 49 of 50 in the Vehicles and Technology course (ages 14+)

US version. US spelling and words (tire, gasoline, hood) and US rules such as state inspections. · UK version

Look inside the computers that run a modern car: what control units do, how the car diagnoses its own faults, and how software can now be updated over the air – safely.

Time
40 minutes + 10 min homework
Course
Vehicles and Technology (ages 14+)
You need
Paper, a pencil and this page. No tools and no vehicle
Graded
Instantly, with explanations

Education and interest only. Classfern teaches motor mechanics as a school subject. It is not a training program or a certification, and nothing here replaces an accredited automotive program, ASE certification 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.

How to use this lesson

This lesson is for curious learners of 14 and over. It links computing (inputs, processing, outputs, data rates and security) with vehicle engineering. Plugging tools into a real car is a job for a technician, not part of this lesson. Every answer is graded 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: “Should car makers be allowed to change how your car behaves with an update after you have bought it? What rules would you set?”
  4. Later: the homework, then the practice test.

Watch out for

  • Thinking a fault code tells you exactly which part to replace. A code points to a circuit or system that looks wrong. The real cause might be wiring, a connector or another part; a technician tests to find it.
  • Thinking that clearing a warning light fixes the fault. Clearing a code removes the message, not the problem. If the fault is still there, the code and the light come back.
  • Thinking over-the-air updates are just like phone apps with no safety concerns. Car software can control brakes and steering, so updates are protected with digital signatures and careful testing.

Hands-on: Design an ECU on paper. Choose a simple car system – automatic headlights, a rain-sensing wiper or a parking alarm. Draw three columns: Inputs (which sensors?), Process (write the rule, such as 'IF it is dark AND the engine is running THEN…'), Outputs (what switches on?). Then add a self-check: what should the system do if the sensor gives an impossible reading? Swap with someone and test each other's rules with made-up readings.

What you will learn

  • I can explain what an electronic control unit (ECU) does using the idea of inputs, processing and outputs.
  • I can describe how on-board diagnostics detects a fault, stores a code and lights a warning lamp.
  • I can explain what an over-the-air update is and why it must be protected.
  • I can calculate how long a software download takes from its size and the connection speed.

Key words

electronic control unit (ECU)
A small computer built into the car that controls one or more systems, such as the engine, brakes or airbags.
on-board diagnostics (OBD)
Self-checking software in the car's computers that watches for faults, especially ones that affect emissions.
diagnostic trouble code (DTC)
A short code stored by the computer when it detects a fault, which a technician reads with a scan tool.
scan tool
A diagnostic device a technician plugs into the car's diagnostic socket to read codes and live data.
over-the-air (OTA) update
New software sent to the car wirelessly, without a visit to the workshop.
digital signature
A code attached to software that proves it came from the maker and has not been changed.

The big ideas

A modern car is a network of computers on wheels. Small computers called electronic control units (ECUs) run the engine, transmission, brakes, airbags, lights and much more. NHTSA describes an ECU as an embedded system that provides a control function to a vehicle's electrical system, and notes that automotive software is distributed and complex.

Each ECU follows the same pattern: it reads inputs from sensors, processes them with its software, and sends outputs to actuators such as fuel injectors, motors and warning lamps. The Alternative Fuels Data Center describes the engine control module as controlling the fuel mixture, ignition timing and emissions, and monitoring, protecting and diagnosing the engine.

The same software also checks itself. On-board diagnostics watches for faults, stores a code and lights a warning lamp, so a technician can find the problem. And because so much of the car is now software, manufacturers can improve or fix it by sending updates – sometimes wirelessly, over the air.

Read-through: the teaching steps

  1. Input, process, output

    Every ECU works like this:

    • Inputs – sensors measure things: engine speed, air flow, coolant temperature, wheel speed, oxygen in the exhaust.
    • Processing – the software compares the readings with stored maps and rules.
    • Outputs – actuators do the work: injectors spray fuel, coils fire spark plugs, motors move throttles and valves, lamps warn the driver.

    This loop repeats many times a second.

  2. A network of computers

    ECUs are linked by data networks, so one sensor can serve many systems. The wheel speed sensors, for example, are used by the anti-lock brakes, the stability control, the speedometer and the driver assistance systems. Sharing data saves wiring and weight, but it also means a fault in one place can show up as a warning somewhere else – one reason fault-finding needs skill.

  3. How the car diagnoses itself

    On-board diagnostics constantly checks that sensor readings make sense and that systems respond as expected. The California Air Resources Board says OBD II, required on 1996 and newer cars and light trucks, monitors "virtually every component that can affect emission performance". When it detects a fault it:

    • stores a diagnostic trouble code, such as one beginning P (powertrain), B (body), C (chassis) or U (network);
    • lights the malfunction indicator light – usually "Check Engine" or an engine symbol;
    • may switch to a safe back-up mode.

    CARB says a steady light means a malfunction has been detected; a blinking light means a fault that could damage the catalytic converter.

  4. The technician and the scan tool

    A technician plugs a scan tool into the car's diagnostic connector to read the stored codes, check which readiness monitors have run, and watch live sensor data. A code is a clue, not an answer: it says which circuit or system looks wrong, and the technician then tests and reasons to find the real cause, using the manufacturer's information. Clearing a code without fixing the cause only hides the problem – and an emissions inspection checks the readiness monitors too.

  5. Updating the software

    Car makers improve software throughout a car's life: to fix faults, make a system work better or add features. Traditionally a technician loaded the update in the shop. NHTSA defines over-the-air (OTA) as a software update distribution method using wireless transmission; the software is downloaded and installed, often when the car is parked. This saves trips to the shop and lets a fault be fixed in many cars quickly.

  6. Keeping it secure

    If software can be changed remotely, it must be protected from people who should not change it. NHTSA's cybersecurity best practices say makers should maintain the integrity of OTA updates and the servers that send them, limit the ability to modify firmware, and may use digital signing so an ECU will not start up with modified or unauthorized software.

The lesson, step by step

40 minutes in 5 parts
PartTimeHow it is checked
Starter: warm up4 minGraded by Classfern
Teaching and hands-on task12 minNot assessed, self-checked
Worked examples and guided practice8 minGraded by Classfern
Independent practice (three levels)11 minGraded by Classfern
Exit ticket and talk question5 minGraded 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 graded instantly.

More practice

More Future and environment lessons · Vehicles and Technology 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 ASE, NHTSA, any state agency, any college, testing agency or exam board.