Signals

Protocol Trace Explorer

Active
Current workspace: Signals
Page usage manualManual

Protocol Trace guide

Use Protocol Trace to inspect persisted CAN-style frames, decoded messages, parser warnings, and decoder coverage for a selected log.

What it provides

  • Bounded frame rows with timestamp, channel, protocol, CAN ID, DLC, data bytes, message name, and decoded preview.
  • Filters for protocol, CAN ID, message, signal, decoded-only rows, and parser-warning-only rows.
  • Direct links back to Log Analysis Viewer and Decoder Results with the same project/log context.

How to use it

  1. 1. Open a processed log file to inspect raw frames, decoded messages, diagnostics, and parser warnings.
  2. 2. Select a processed project log.
  3. 3. Filter by protocol, CAN ID, decoded rows, or parser warnings.
  4. 4. Use the selected time or frame context to return to the viewer or downstream findings.

Outcome: Engineers can move from signal behavior to the source trace rows behind that evidence.

Open viewer
TimeChannelProtocolCAN IDDLCDataMessageDecoded previewWarning

No trace rows match this filter. ASC logs expose frame rows after processing.

Event Timeline Tracks

No timeline events available.