OBD Data and Control Circuit Testing

OBD II Operation, DTC Types, and Readiness Monitors

OBD II primarily monitors emissions-related systems and may detect communication faults that affect them; diagnostics for other vehicle systems and networks may be manufacturer-specific. Whether an emissions fault illuminates the Malfunction Indicator Lamp (MIL) depends on exact detection and confirmation criteria. A Type A fault illuminates the MIL on the first qualifying failed trip; freeze-frame storage is subject to applicable requirements and fault-priority rules. In contrast, a two-trip (Type B) fault typically records a pending DTC on the first qualifying failed trip, turning on the MIL only when the fault is detected again on the next qualifying trip. A pending DTC indicates a detected fault that has not yet met full confirmation criteria, though it can coexist with an established confirmed DTC.

Freeze-frame data captures a snapshot of operating conditions when an emissions-related fault meets criteria, but it is not necessarily a recording of the precise instant the issue began. While OBD II mandates storing at least one freeze-frame record, higher-priority faults such as misfires and fuel trim errors can overwrite lower-priority data. Furthermore, permanent DTCs cannot be erased by clearing codes with a scan tool or disconnecting battery power; they clear only after the vehicle completes the required operating conditions and onboard diagnostic checks confirm the fault is absent.

A steady MIL indicates a detected emissions-related fault; a flashing MIL typically warns of a catalyst-damaging misfire, so reduce engine load immediately and, if flashing persists, stop driving when safe and diagnose the fault before further operation. For many faults, the MIL turns off after three consecutive qualifying trips without a fault, and stored DTCs often clear after 40 qualifying warm-up cycles without recurrence. A warm-up cycle requires engine coolant temperature to rise by a specified amount and reach a minimum operational threshold after starting. An OBD II trip requires vehicle operating conditions to meet specific enable criteria, meaning a simple key-on and key-off cycle alone may not qualify.

Readiness status indicates whether specified monitors have completed their evaluations since the last reset, but a ready status does not guarantee every component passed. Continuous monitors, including misfire, fuel trim, and comprehensive components, run whenever conditions permit. Non-continuous monitors, such as catalyst, evaporative emissions (EVAP), secondary air, and oxygen sensor monitors, require specific drive cycle conditions. Clearing DTCs or disconnecting the battery generally resets monitors to not ready. Enable criteria dictate these requirements; for instance, an EVAP leak monitor may require fuel tank levels within a specific range before running.