Recording formats

OBD Lens analysis JSON

Format identifier: com.obdlens.analysis-session, version 1. It contains source and session metadata, signal definitions, samples and DTC observations. Unknown versions and fields are rejected.

Download shared App-export synthetic example · Download missing-data example

The shared exporter example proves file-format interoperability. It does not demonstrate that a public mobile App release is available.

Signals CSV

Supported App filename: signals-long.csv. Underscored filenames are also accepted when their columns match. Required header:

timestamp_utc,timestamp_epoch_ms,elapsed_ms,signal_key,signal_name,value,unit,decimals,origin,legacy_role,ecu

Numeric values use a decimal point. Quoted CSV cells are accepted. Conflicting names or units and inconsistent clocks are rejected. The browser view retains signal origin and module identity; decimal-format hints and legacy_role are not interpreted.

DTC CSV

Supported App filename: dtc-events.csv. Required header:

timestamp_utc,timestamp_epoch_ms,elapsed_ms,dtc,status,ecu

Status, module and observation time are retained. An observation time does not prove when the fault began.

Limits and local processing

One file per import, at most 8 MiB and 50,000 samples. ZIP archives, PDFs, raw CAN logs and other CSV layouts are not supported. Extract a supported CSV from an App archive before importing it.

Only the current import is kept in this tab’s memory. Clear data removes the displayed recording. Closing or reloading the tab discards it.