Freeze frames
0
persisted diagnostic snapshots
Diagnostics
Use Freeze Frames to see whether diagnostic decode produced freeze-frame evidence and whether it has enough metadata for engineering interpretation.
Outcome: Engineers know whether freeze-frame evidence exists and what context is required before reporting it.
Freeze frames
0
persisted diagnostic snapshots
DTC events
0
available for freeze-frame context
Diagnostic artifacts
0
active context files
Negative responses
0
NRC review context
Freeze-frame records are counted from the latest offline decode. Value labels, units, and expected ranges depend on active DTC, ODX/PDX, CDD/CBF, or diagnostic specification context.
Re-run processing for a diagnostic-capable log to create offline diagnostic evidence.
No freeze frames were detected in the selected log.
Add DTC catalog or ODX/PDX style technical data before relying on semantic freeze-frame interpretation.
Persisted diagnostic snapshots from the latest offline decode run. Values are reported from stored log evidence only.
| Time | Label | Value | DID | Enrichment |
|---|---|---|---|---|
| No freeze-frame records are available for the selected log. Re-run processing for a diagnostic log that contains stored freeze-frame or extended diagnostic data. | ||||
Active artifacts available to enrich freeze-frame and DTC evidence.
| Artifact | Type | Status | Coverage |
|---|---|---|---|
| No diagnostic context artifacts are linked yet. | |||