Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Diagnostics
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Vehicle diagnosis combines monitoring performed by electronic control units (ECUs) on the vehicle with tests and information used by a technician outside it. On-board monitoring can record a fault when it occurs; off-board equipment helps retrieve that evidence and establish the cause.

On-board diagnostics

On-board diagnostics describes the self-checking functions built into a vehicle's control systems. ECUs can monitor their own operation, connected sensors and actuators, communications and the behaviour of the systems they control. The checks available and the conditions under which they run depend on the vehicle and controller. Legislated OBD or EOBD is a standardised subset concerned primarily with emissions; manufacturer diagnostics can cover many other systems.

What the ECU checks

  • Internal checks: depending on the design, an ECU may check program memory integrity, RAM, internal supplies and conversion circuits. Do not assume every controller performs the same tests or checks every component continuously.
  • Sensor circuits and plausibility: a controller may detect an open circuit, a short to earth or supply, or a signal outside an expected range. It can also compare signals with other measurements or operating conditions. A value inside the electrical range can still be inaccurate.
  • Actuators and system response: some output drivers monitor electrical current or circuit voltage; some diagnostics also assess the response to a commanded change. An electrically sound circuit does not prove that a valve, motor or the controlled system is working mechanically.
  • Emissions monitors: supported checks may run continuously or only when enabling conditions are met. Readiness indicates whether a monitor has completed, not that every possible defect has been ruled out. EPA: definition of OBD readiness.

Fault memory, warnings and fallback

When a monitor detects a fault under its defined conditions, the ECU may record a diagnostic trouble code (DTC), its status and associated operating data. Freeze-frame or other snapshots can help reproduce an intermittent concern, although the data and storage rules vary. Codes can be pending, confirmed or historical depending on the system; the criteria for setting, clearing and retaining them are not universal. Record them before clearing. See OBD fault codes and readiness monitors.

A warning lamp or message can alert the driver. The malfunction indicator lamp (MIL) is associated with emissions-related OBD faults, while other systems may use their own warnings. In some cases a controller substitutes a default or calculated value, limits torque or changes operation to protect the vehicle or maintain limited mobility. Fallback strategies are vehicle and fault specific; see reduced power and limp-home diagnosis. The US EPA describes the MIL, fault codes and the role of OBD in emissions monitoring in its OBD overview.

A DTC identifies a condition detected by a monitor, not necessarily the failed component. Wiring, power supplies, mechanical faults or another system can produce the same code. No code also does not prove that a vehicle is fault-free: the relevant monitor may not exist, may not have run, or may not detect the particular fault.

Off-board diagnostics

Off-board diagnostics uses equipment and information outside the vehicle to investigate a complaint. This includes handheld scanners, tablet or laptop-based systems, vehicle communication interfaces and stationary workshop equipment. The distinction is functional rather than a strict division by size: a portable device can provide extensive manufacturer-specific functions, while a fixed workstation may connect to separate measuring instruments.

Tools and information

  • Scan tools: identify control units, read and record fault codes and live values, and, where supported, run actuator tests, service functions and guided routines. Generic emissions OBD access is narrower than full manufacturer-specific diagnosis; coverage varies by vehicle, software and licence.
  • Electrical test equipment: an automotive multimeter, oscilloscope or scopemeter and current clamp can check supplies, earths, voltage drops and waveforms independently of the ECU's reported values. Use the correct wiring information and approved test method.
  • Mechanical and emissions equipment: pressure and vacuum equipment, smoke machines and leak detectors, compression or leak-down equipment, borescopes and exhaust analysers can establish faults that a scanner alone cannot locate.
  • Technical information: current wiring diagrams, test procedures, specifications, service bulletins and software updates provide the context for interpreting results. Modern systems commonly supply this information electronically. Some protected diagnostic functions require authorised access or a subscription. Bosch ESI[tronic] diagnostic and workshop information.

Vehicle connections and protocols differ by age and manufacturer; a familiar 16-pin socket does not guarantee access to every module or function. See diagnostic ports before and after EOBD and diagnostic communication protocols.

A practical diagnostic sequence

  1. Confirm the customer's symptoms and operating conditions; identify the exact vehicle and system.
  2. Check battery condition and obvious power, earth, wiring and connector issues. Scan relevant modules and save codes, statuses and snapshots before clearing anything.
  3. Consult the applicable service information and compare live values with expected behaviour under the relevant conditions. Check whether a displayed value is measured or a substituted fallback where the tool identifies it.
  4. Form a testable cause and use suitable electrical, mechanical or functional tests to distinguish the component from its wiring and related systems. Follow the manufacturer's safety and actuator-test instructions.
  5. Repair the established cause, perform any required adaptations, clear codes when appropriate, and verify the repair under the conditions that produced the fault. Check relevant monitor readiness where applicable.

Clearing codes can erase useful snapshots and reset readiness monitors, so it is not a substitute for diagnosis. Take care around moving parts, hot exhausts, high-pressure fuel and high-voltage systems; use vehicle-specific procedures and suitably qualified personnel.

Sources and further reading

For a specific starting complaint, see diagnosing a petrol engine that cranks but will not start.