TXT to CSV Decoder

The CSV decoder stores the decoded output as CSV files.

The CSV output format has wide tool support but is generally inefficient (slow and big).

Output

The CSV output data-schema always include an epoch-timestamp column named t. The remaining column names are constructed from the database used for decoding, as in the example below:

t,Speed,SpeedAccuracy,SpeedValid
1650636883.519250,0.010000,2.006000,1.000000
1650636884.090300,0.010000,2.152000,1.000000
1650636885.041350,0.010000,2.290000,1.000000
1650636886.090500,0.010000,2.419000,1.000000

Note

Output values are always formatted as decimal numbers with 6 decimal places.

If specific values exceed the MIN/MAX as defined in the database, they are included in the output as NaN, as in the example below:

t,Speed,SpeedAccuracy,SpeedValid
1650636883.519250,0.010000,NaN,1.000000
1650636884.090300,0.010000,NaN,1.000000
1650636885.041350,0.010000,NaN,1.000000
1650636886.090500,0.010000,NaN,1.000000

Warning

Output rows are skipped if all values are NaN.

Changelog

# Changelog

All notable changes to this project will be documented in this file.

## [24.10.17]

### Added

- Support for transport protocols (ISO-TP, J1939-21, NMEA-TP, MUX-TP)

### Changed

- Versioning schema from SemVer to CalVer
- Default verbosity level changed to 2
- Restriction on max 5 DBC-files per interface/channel removed

### Fixed

- Fix for order of messages with same timestamp

## [2.3.2]

### Fixed

- Issue with merge of PGN source/destination addresses sometimes resulting in invalid output files

Download

Windows AMD64 / x86-64 (64-bit)

Linux AMD64 / x86-64 (64-bit)

Linux ARM64 (64-bit)