Binary .dlt captures
Binary DLT captures are decoded as framed records, the same way a logcat file is parsed into rows you can filter and read.
Features / DLT viewer
A DLT viewer for macOS, Windows, and Linux.
Indagium opens Diagnostic Log and Trace (DLT) captures alongside Android logcat, so a desktop trace and a DLT capture from the same investigation can sit in the same workspace — filtered, folded, and annotated the same way, including on macOS where a native DLT viewer has been hard to find.
Supported DLT formats
Three ways a DLT trace reaches Indagium.
Indagium opens files — it does not connect to a DLT daemon or vehicle network to capture traffic itself. Bring the capture from your existing DLT tooling, then open it directly:
Binary
Raw DLT streams
A raw DLT stream — without a surrounding container — opens the same way as a saved .dlt file.
DLT Viewer text/CSV exports
Already exported a trace from DLT Viewer as text or CSV? Open that export directly in Indagium to filter, fold, and annotate it.
The same investigation tools
Level, tag, and message filters, sequence folding, thread maps, time deltas, compare view, and note export all apply to a DLT tab.
DLT protocol handling
Framed records, read safely.
Non-verbose DLT payloads are retained as safe text/hex rather than interpreted through FIBEX or ARXML definitions — so a capture opens and reads without needing project-specific description files on hand. An oversized DLT capture can be split like any other large log: binary captures are split frame-aware, so every resulting part is a valid standalone DLT stream, and DLT Viewer CSV parts repeat the header row so each part stays independently readable.
Compare the workspace to a plain viewer
Check the filter
See what your DLT filter hides.
The Unfiltered button splits one DLT tab vertically: the complete capture on one side, your filtered view on the other. Tag and message rules stay editable right above the filtered half, so you can narrow by ECU, application, or context and confirm nothing important dropped out — without opening a second copy of a large capture.
See every filter the analyzer offers
Stated plainly
What a DLT tab does not do.
These limits are worth knowing before you rely on Indagium for a DLT capture:
No FIBEX/ARXML decoding
Non-verbose payloads are shown as safe text/hex, not decoded through FIBEX or ARXML definitions — the raw payload is preserved, not reconstructed into typed fields.
No DLT protocol v2 support
DLT protocol v2 streams are not supported and cannot be split. Only DLT protocol v1 binary captures, raw streams, and DLT Viewer text/CSV exports are covered.
No live tailing on DLT tabs
Live tailing works on plain-text logs as they're written, but DLT tabs do not support live UTF-8 tailing — open a completed capture instead.
No capture from device
Indagium does not talk to a DLT daemon or vehicle network. Capture with your existing tooling, then open the resulting file here.
Frequently asked
Before you open a capture.
Does Indagium replace COVESA DLT Viewer?
Not for capturing or FIBEX/ARXML-based non-verbose decoding. Indagium opens .dlt captures, raw DLT streams, and DLT Viewer's own text/CSV exports as a desktop analysis workspace — you can bring an existing DLT Viewer export into Indagium for filtering, folding, and annotation.
Is there a good DLT log viewer for Mac?
Indagium runs natively on Apple Silicon Macs as a .dmg, alongside Windows (.msi) and Linux (.deb, AppImage, Flatpak) builds, so a DLT capture opens in the same desktop app regardless of platform.
Does Indagium decode non-verbose DLT payloads with FIBEX or ARXML files?
No. Binary captures are decoded into framed records, but non-verbose payloads stay as safe text/hex rather than being interpreted through FIBEX or ARXML definitions.
Can Indagium split a large DLT capture?
Yes, for DLT protocol v1: splitting is frame-aware, so every part is a valid standalone DLT stream, and DLT Viewer CSV exports repeat the header row in each part. DLT protocol v2 streams are not supported and cannot be split.
Is Indagium free, and is it open source?
Indagium is free to use. It's source-available under the PolyForm Perimeter License, not open source and free to use for commercial and non-commercial purposes.
Keep going