Tuning Wiki

On-board diagnostics can report emissions-related faults and the status of the tests used to detect them. A scan result is evidence about what a controller has observed, not a complete diagnosis or proof that every system is healthy. Available services and terminology depend on the vehicle, market and scan tool.

Fault codes, the warning lamp and freeze-frame data

A diagnostic trouble code (DTC) identifies a fault condition detected by a monitor. It directs the investigation toward a circuit, system or operating condition; it does not automatically identify the failed part. Record the code, status, warning-lamp state and available freeze-frame data before clearing anything. Look for related codes and compare live data with the conditions under which the fault occurred.

A generic emissions scan may provide less information than the manufacturer-specific diagnostic system. Code definitions and operating criteria can differ: use the applicable service information and verify the vehicle and controller identity. Diagnostic communication protocols and diagnostic connector history provide the connection context.

What readiness means

Readiness describes whether a supported monitor has completed its required evaluation since the relevant reset; it is separate from a fault code. A monitor reported as not ready may not yet have seen the temperature, speed, fuel level or other conditions needed to run. It is not, by itself, proof of a failed component. Supported monitors and their enabling conditions vary by vehicle. The US EPA distinguishes readiness status from DTCs and notes that a scan tool can read both. US EPA: OBD system checks and readiness

Some checks run continuously when their conditions permit; others need a particular sequence of operating conditions. An individual manufacturer drive cycle is not a universal recipe. Clearing codes or disconnecting power may reset readiness and erase useful diagnostic context; record the evidence first and follow the applicable service procedure.

A practical sequence

  1. Identify the vehicle, engine, controller and symptom. Connect a compatible scanner and record all modules and codes relevant to the complaint.
  2. Save code status, freeze-frame information, readiness and related live data. Record which monitors are unsupported separately from those that are not ready.
  3. Use the vehicle-specific diagnostic procedure to test the likely circuit and mechanical system. Inspect connections, supplies and grounds where the procedure calls for them; do not replace a part solely because its name appears in a code description.
  4. After repair, clear codes only when appropriate, reproduce the operating conditions safely, and recheck codes, live data and readiness. Some intermittent faults require more than one trip to evaluate.

Inspection rules and permitted readiness states vary by jurisdiction, vehicle and test programme. Consult the current authority and applicable inspection procedure rather than assuming a US OBD rule applies to a UK or European vehicle.

For a practical example of interpreting a monitor without assuming a component has failed, see diagnosing an engine misfire.