Nov. 02, 2026
An OBD2 scan raises four practical questions: What fault has the vehicle recorded? What operating conditions existed when the fault was stored? Have the emissions-related self-tests completed? What values is the vehicle reporting now? Diagnostic trouble codes, freeze frame data, I/M readiness monitors and live data answer these questions in different ways.
This article explains what each OBD2 diagnostic function represents, how the four functions relate without becoming interchangeable, and why the information shown can vary by vehicle and scanner. The individual product page remains the source for model-specific function support.
| Function | What it represents | Typical information shown |
|---|---|---|
| Diagnostic trouble codes | Recorded identifiers associated with detected malfunctions | Code status and the system or component area connected to the code |
| Freeze frame data | A stored snapshot linked to a fault event | Selected engine and vehicle conditions captured when the code was set |
| I/M readiness | Completion status of emissions-related self-tests | Ready, not ready or not applicable monitor states |
| Live data | Current values reported by electronic control units | Parameters such as engine speed, vehicle speed or temperature when supported |
The four functions can appear together on one scanner display, yet each answers a different question about the diagnostic record.
A diagnostic trouble code, commonly shortened to DTC, is an identifier stored when the on-board diagnostic system detects a qualifying malfunction. It points to an affected system or component area, not necessarily the root cause, so supporting information may still be needed.
Code status also matters: scanners may distinguish pending, confirmed, permanent or malfunction-indicator-lamp-related states. A basic “reads codes” label does not confirm how each status is displayed.
Freeze frame data is a snapshot of selected operating conditions stored when a qualifying diagnostic trouble code is set. It may include values such as engine speed, vehicle speed, temperature, load or other supported parameters. The available fields depend on the vehicle and the diagnostic information it reports.
This snapshot differs from live data because it represents a stored event rather than continuously changing values. It connects a code with the conditions recorded at that time, giving the diagnostic record more context than the code identifier alone.
Clearing emissions-related diagnostic information may also erase freeze frame records and reset readiness information. For that reason, “read and clear codes” and “display freeze frame” remain separate product functions even when both appear on the same tool.
I/M readiness refers to the status of diagnostic monitors used for emissions inspection and maintenance programs. A readiness monitor is a self-test performed by the vehicle’s OBD system for a particular emissions-related system or component area.
A monitor can be reported as ready when the required diagnostic evaluation has completed, not ready when it has not yet completed, or not applicable when that monitor does not apply to the vehicle. Readiness is therefore a completion status. It is not the same as a diagnostic trouble code, and a ready result does not mean that every vehicle system has been checked by the scanner.
Readiness states may reset when diagnostic information is cleared or vehicle power is disconnected. Relevant monitoring conditions must then be completed before non-continuous monitors can return to ready status. Exact behavior depends on the vehicle and applicable requirements.
Live data consists of current diagnostic parameters reported by the vehicle’s electronic control units. These data points are commonly identified as PIDs, or parameter identifiers. Examples include engine speed, vehicle speed and engine temperature, along with other supported input, output and calculated values.
Unlike freeze frame data, live data changes as the vehicle reports new values. A scan tool may present the information as numbers, lists, graphs or real-time curves. The display format does not expand the underlying data: the vehicle must support and report a parameter before the scanner can show it.
Published support for “data stream” or “live curve” remains product-specific. Update rate, graphing, recording and displayed parameters can differ between scanners in the same category.
The four functions describe different parts of one diagnostic information set. A monitor reports readiness status; a qualifying malfunction can produce a DTC and related freeze frame; live data presents current supported parameters instead of stored event conditions.
Products in the OBD scanner and diagnostic tool range therefore list these functions separately. One feature does not establish support for the others.
OBD2 diagnostic functions depend on both the vehicle and connected tool. Protocol coverage, compatibility, supported test modes and software implementation affect what information appears.
Category descriptions summarize the range, but individual product pages control the published function list. Distinct terms prevent one capability from being extended across every OBD tool.
Previous Post
NoneNext Post
Car Jack Capacity and Lifting Height Terms ExplainedLatest Blog
Jun. 04, 2024
Contact us for more information
Can't find what you were looking for? We can customize according to your needs.
