UDS messages
0
offline decoded request/response rows
Diagnostics
Diagnostic Decode
ActiveCurrent workspace: Diagnostics
Page usage manualManual
Diagnostic Decode guide
Use Diagnostic Decode to inspect offline ISO-TP, UDS, DTC, negative response, and diagnostic provenance output for a processed log.
What it provides
- Run summary for diagnostic messages, conversations, DTC events, freeze frames, and negative responses.
- UDS message evidence table with request/response status and bounded summaries.
- Safety and provenance panel that excludes live commands, DTC clearing, flashing, seed-key execution, and ECU writes.
How to use it
- 1. Run or re-run processing, then inspect offline ISO-TP, UDS, DTC, negative response, and diagnostic provenance output.
- 2. Select a project and diagnostic-capable log file.
- 3. Re-run processing if the summary says diagnostic evidence is missing.
- 4. Review UDS messages and then open DTC Review or Protocol Trace for deeper investigation.
Outcome: Stored log evidence is converted into offline diagnostic findings without creating any live ECU operation path.
Conversations
0
request and response correlation
DTC events
0
diagnostic trouble code observations
Negative responses
0
UDS NRC evidence
Offline Diagnostic Run
Select a processed diagnostic-capable log file.
- Source format
- -
- Parser
- -
- Parser version
- -
- Decoder profile
- -
- Safety boundary
- Offline Only No Live Commands
- Source records
- -
- CAN payloads
- -
- Freeze frames
- 0
- Transport rows
- 0
UDS Message Evidence
Offline request, positive response, negative response, and DTC payload summaries. Raw payload bytes are intentionally excluded from this UI.
| Time | Type | CAN ID | Service | Response | Status | Summary |
|---|
No diagnostic messages yet. Re-run processing for CSV, JSONL, DTC, or ASC ISO-TP diagnostic evidence.