CAN Capture Analyzer
Import plain candump output or a candump -L log. The analyzer reads the file on this device and runs without uploading the capture.
Supported log formats and samples
Compact Classical CAN, CAN FD, remote and SocketCAN error records are supported. The compact format uses three hex digits for an 11-bit ID and eight for a 29-bit ID, for example (12.000001) can0 123#AABB, can0 00000123#R8 or can0 123##10102. Plain display records use [8] for Classical CAN and [08] for CAN FD, following can-utils’ width convention. DLC is inferred from length unless the record carries it explicitly. Plain display CAN FD omits flag values.
Use numeric absolute timestamps or seconds relative to a shared origin, with up to nine fractional digits. If your log uses per-record deltas, calendar dates or decorated output, recapture with candump -L. Records without timestamps still count. Limits are 10 MiB and 100,000 lines per import.
- Download periodic.log — eleven synthetic frames with a 10 ms median and a 0.25 ms excursion on either side.
- Download mixed.log — ten synthetic records and one deliberately malformed line. Includes a backwards timestamp, a tie and untimed traffic.
Formats are based on can-utils candump and its frame formatter. See the periodicity lab to record your own data.
Choose a capture file or load a teaching sample.
Three digits match a standard ID. Eight match an extended ID. Other widths match the numeric ID in either format. Filter by interface to compare timestamps from one clock.
Import diagnostics
Capture timeline
Timeline bin counts
| Bin start (ms) | Messages | Error records |
|---|
Message statistics by ID
Grouped by interface, ID format and frame type. TX and RX records in the same stream are counted together. Intervals use consecutive timestamped records in time order. Rate is interval count divided by the first-to-last timestamp span. Percentiles use nearest rank.
| Interface | ID | Frame | Count | Timed | Hz | Mean ms | Median ms | Min ms | Max ms | p95 ms | p99 ms | Backwards | Ties | Plot |
|---|
Inter-arrival jitter
Capture records
Records retain file order. SocketCAN error reports carry a class mask and controller-supplied diagnostic bytes. They are excluded from per-ID message statistics.
| Line | Timestamp (s) | Interface | ID or error token | Frame | DLC | Bytes | Payload | Details |
|---|
Observed gaps can reflect sender behavior, filtering, buffering or capture loss. Use controller and capture diagnostics to investigate. Physical bus utilization requires additional wire-level evidence.