iCarsoft diagnostic evidence guide
OBD2 freeze frame data is a saved snapshot of operating conditions associated with an emissions-related fault. Before clearing codes, preserve the associated trouble code, every available snapshot field and its units, and a separate record of code status and readiness. Those details help explain whether the fault appeared during a cold start, warm idle, or driving under load.
What Is OBD2 Freeze Frame Data?
OBD2 freeze frame is a limited record that the vehicle computer stores when its fault-monitoring strategy calls for a snapshot. The scan tool retrieves that record; connecting the scanner does not recreate the original event. A frame may include engine speed, vehicle speed, coolant temperature, calculated load, fuel-system status, and other supported parameters.
A parameter identifier, or PID, names a data item available through the diagnostic interface. A frame contains only the supported items the vehicle stored, not every sensor reading on the car. The iCarsoft OBDII function guide distinguishes Freeze Frame from DataStream and other diagnostic functions.
Think of freeze frame as a photograph of selected measurements, not a dashboard camera. The record does not necessarily include a calendar timestamp, the instant a driver first noticed the lamp, or the entire sequence leading to the fault. Some enhanced systems provide richer event records, but those should not be assumed to exist in generic OBD2.
How Is Freeze Frame Different From Live Data and Readiness?
Freeze frame describes stored fault conditions, live data describes the current session, and readiness describes whether supported emissions monitors have completed their checks. Save all three as separate evidence. A ready monitor is not a stored sensor snapshot, and a live-data recording is not automatically a copy of freeze frame.
Freeze frame
Question: What conditions were stored for this fault?
Use: Plan a condition-specific investigation.
Limit: Not a continuous history.
Live data
Question: What does the module report now?
Use: Observe change and compare signals.
Limit: Current conditions may differ.
Readiness
Question: Have supported monitors run?
Use: Record verification progress.
Limit: Not proof that every system is healthy.
For the wider first-scan sequence, use the beginner OBD2 scanner guide. After preserving the snapshot, the live-data interpretation guide explains how to compare related signals under controlled conditions.
What Should You Save Before Clearing Codes?
Save the complete available record, including labels and units, rather than copying a few numbers. Also record the vehicle identity, symptoms, code statuses, and readiness separately. A screenshot labeled “temperature 90” is much less useful than a complete screen identifying the parameter, unit, vehicle, and associated DTC.
Vehicle and complaint
VIN or exact vehicle configuration, engine, mileage, date of scan, warning lamps, recent work, and when the symptom occurs. Keep customer identifiers out of public screenshots.
DTC and frame identity
Exact associated code, description, module, menu path, frame number if shown, and every available code status. Do not assign the frame to a different code.
Speed and operating load
Engine RPM, vehicle speed, calculated load, throttle-related readings, and runtime if present. Preserve labels because similarly named values are not interchangeable.
Temperature and fuel control
Coolant and intake-air temperatures, fuel-system status, trims, and supported airflow or pressure readings. Record units and bank labels without converting the original file.
Other supported evidence
Capture every additional page: voltage, pressure, oxygen feedback, or manufacturer-specific event data when available. An unavailable field is not a zero reading.
Separate baseline records
Save the code list, readiness screen, and original scan report separately. Check whether the report actually contains freeze frame before relying on it as a backup.
How Do You Read and Preserve Freeze Frame With a Scanner?
Connect safely, read codes first, open the supported Freeze Frame function, and verify that your saved files contain the record. The sequence below is a general workflow, not a promise that every iCarsoft menu or vehicle uses the same buttons.
- Identify and connectPark safely, apply the parking brake, and follow the vehicle and tool instructions for connection and ignition state. Do not start the engine merely to retrieve an already stored record.
- Record the code listOpen generic OBD2/EOBD or the appropriate supported vehicle menu. Save exact DTCs and statuses before using any erase or reset function.
- Open Freeze FrameSelect the available snapshot function and read the associated code. If the tool offers multiple records or modules, record which one each screen belongs to.
- Capture every pageUse a supported save/export feature or clear photographs. Include field names, units, bank labels, and the associated code. Scroll through the entire record.
- Verify the backupOpen the export or enlarge each photo. Check for cropped values, glare, missing pages, and unreadable text before leaving the session.
- Keep an original copyStore the unedited files with vehicle and scan-date labels. Add interpretation in separate notes so a later technician can distinguish observations from conclusions.
Why Is Freeze Frame Missing, or Linked to Another Code?
Missing freeze frame does not automatically mean the scanner is faulty, and an available frame is not guaranteed for every code. The vehicle’s storage strategy, code type, selected menu, earlier clearing, and scanner coverage all affect what you can retrieve. Manufacturer-specific modules may use separate event-data functions.
Some applicable OBD strategies give fuel-system or misfire faults priority over an earlier record. For example, the historical federal provisions in 40 CFR §86.1806-05 describe such replacement behavior. This is not a universal storage-capacity rule for every modern module: check the service information for the particular model year and system.
If no record appears, note the exact message instead of writing “all values zero.” Confirm the vehicle selection and whether you are using generic OBD2 or an enhanced module menu. Ask about prior code clearing or battery work, then consult the tool manual and vehicle information. Do not deliberately create a new fault to force a snapshot.
How Do You Interpret Freeze Frame Without Guessing at Parts?
First reconstruct the operating condition, then identify the next test. Read RPM, speed, load, temperatures, and fuel-system state together before judging an individual value. Pass/fail limits must come from the correct vehicle procedure; one universal “normal freeze-frame chart” cannot diagnose every engine.
Example: A cold-start complaint
Illustrative scenario: The driver reports rough running after an overnight park. The stored frame instead suggests a warmed engine operating under road load.
Next step: Confirm the associated DTC and whether this is the relevant event. The mismatch may point to a different occurrence; it does not prove the driver’s account is wrong or that a temperature sensor failed.
Example: Fuel correction at idle
Illustrative scenario: A frame associated with a fuel-control code shows warm, stationary operation and positive supported fuel-trim readings.
Next step: Compare relevant live data under the prescribed conditions and follow the diagnostic procedure. The snapshot alone cannot distinguish unmetered air, fuel delivery, measurement error, or other causes.
Write a short evidence note: “The saved record suggests this condition; the associated code is this; the next check is this.” Separate observations from hypotheses. If a road test is appropriate, use a qualified passenger or secure recording; the driver must not operate or watch the scanner while moving.
When Is It Appropriate to Clear Codes?
Clear codes only after preserving evidence and when the repair or diagnostic procedure calls for it. Clearing is not a repair and may remove freeze-frame information and reset readiness. Do not clear as a substitute for diagnosis, to hide a fault from a buyer, or to make an emissions test appear ready.
The EPA’s OBD inspection guidance explains why codes and associated freeze-frame information matter to repair. Permanent emissions DTCs are different: California BAR’s OBD reference states that a scanner erase command or battery disconnection does not clear them; the vehicle must verify the relevant repair conditions.
After repair, follow the specified verification procedure and keep a second, clearly labeled scan. Compare the original evidence with the post-repair result. A lamp staying off during a brief idle period is not proof that the original monitor has completed successfully.
Which Scanner Features Matter for Freeze Frame?
Prioritize confirmed freeze-frame access for the required vehicle and a practical way to preserve the full record. A larger feature count does not guarantee a snapshot for every module. Ask specifically about generic OBD2 freeze frame, enhanced event data if needed, and whether saved reports include those fields.
CR Pro S: a compact workflow example
The CR Pro S product listing, checked September 23, 2026, lists freeze-frame access and a 5-inch touchscreen. It is one option to consider when you also want supported full-system diagnostics.
For basic emissions snapshots, a simpler compatible reader may be sufficient. Do not buy advanced coding or active-test capability solely to retrieve generic freeze frame.
Vehicle, engine, model year, module, and required record.
Compare the iCarsoft multi-brand diagnostic tools, then use the Before You Buy compatibility check. Describe the data you need, not just the vehicle brand. If an expected frame is missing, provide the tool model, software version, selected menu, exact DTC, and error message to support.
Frequently Asked Questions
Does every trouble code have freeze frame data?
No. Generic OBD2 freeze frame is not a guaranteed record for every code or module. Availability depends on the vehicle’s monitoring and storage strategy, the code type, previous clearing, selected menu, and scanner coverage. Enhanced modules may offer separate event records.
Will clearing codes erase freeze frame?
Clearing emissions-related diagnostic information can erase the associated freeze frame and reset readiness. Preserve all available pages and verify your backup before an erase command. Follow the vehicle’s service procedure rather than assuming the record will remain available.
Can a scanner recover freeze frame after it was erased?
Do not assume it can. Check for previously saved reports, photographs, or recordings that actually include the snapshot. A scanner cannot recreate deleted vehicle evidence simply by reconnecting, and a later fault may produce a different record.
Why does the snapshot show a different code?
The frame belongs to the DTC identified with that record, not necessarily the first code in the list. Some storage strategies prioritize particular faults or replace earlier frames. Keep the associated code attached and consult the model-specific diagnostic information.
Are freeze frame values supposed to change as I rev the engine?
No. A retrieved freeze frame is stored evidence, not current live data. Use the live-data function for changing readings, and do not rev the engine merely to make a snapshot update. Menu behavior and available records vary by vehicle and tool.
Can freeze frame prove which part needs replacement?
No. Freeze frame provides operating context for choosing the next test. A suspicious value can reflect a sensor, circuit, mechanical problem, another input, or a reporting limitation. Verify the interpretation with vehicle-specific procedures and appropriate direct tests.
