Offline diagnostics

Diagnostics

Active
Current workspace: Diagnostics
Page usage manualManual

Diagnostics guide

Use Diagnostics for offline UDS, DTC, negative-response, freeze-frame, provenance, and diagnostic evidence export workflows.

What it provides

  • Centralized access to Diagnostic Decode, DTC Review, Diagnostic Timeline, Protocol Trace, Diagnostics Data, Freeze Frames, and Evidence Export.
  • Offline-only diagnostic safety boundary: no live ECU commands, DTC clearing, flashing, seed-key execution, or writes.
  • Project-scoped evidence that can feed findings, reports, and controlled AI summaries.

How to use it

  1. 1. Open offline diagnostic decode, DTC review, timeline, freeze-frame, and evidence export workflows.
  2. 2. Select a project and diagnostic-capable processed log.
  3. 3. Review decode status, DTCs, negative responses, and timeline markers.
  4. 4. Export a diagnostic evidence bundle only after confirming provenance and technical context.

Outcome: Diagnostic observations become traceable offline evidence without exposing live vehicle control actions.

UDS messages

0

offline decoded rows

DTC events

0

diagnostic trouble code evidence

Negative responses

0

NRC markers

Freeze frames

0

stored diagnostic snapshots

Engineer6 assigned projects

Assigned project diagnostic workflow

Engineers use assigned project logs to decode offline UDS/DTC evidence, inspect timelines, and package diagnostic evidence for reports.

Diagnostic workflow map

Offline diagnostics are project-scoped and evidence-only. The platform does not expose live ECU commands, clearing, flashing, security access, calibration writes, or variant coding.

Offline Only

Current decode state

Status
Not Selected
Parser
-
Profile
-
Safety
Offline Only No Live Commands