Log file

This section documents the log file format.

An example log file is given below for reference.

# Logger type: CL1000
# HW rev: 6.xx
# FW rev: 5.31
# Logger ID: OPEL
# Session No.: 70
# Split No.: 1
# Time: 20000101T000000
# Value separator: ";"
# Time format: 4
# Time separator: ""
# Time separator ms: ""
# Date separator: ""
# Time and date separator: "T"
# Bit-rate: 500000
# Silent mode: false
# Cyclic mode: false
Timestamp;Type;ID;Data
01T000000683;8;7df;02010d5555555555
01T000000688;0;7e8;03410d00aaaaaaaa
01T000000693;8;7df;02010c5555555555
01T000000701;0;7e8;04410c0000aaaaaa
01T000000783;8;7df;02010d5555555555
01T000000788;0;7e8;03410d00aaaaaaaa
01T000000793;8;7df;02010c5555555555
01T000000801;0;7e8;04410c0000aaaaaa

File format

Log files are written in a CSV-like format using the reduced ASCII character set. The log files can be opened directly in most simple text editors. Log entries are formatted according to the settings in the configuration file (see Log and Data fields) and terminated by a single “line feed” character.

The configuration of the log file format is written to each log file header (e.g. the timestamp format used, the separators used, etc.).

Note

Note that some text editors do not recognise a single “line feed” character as a new line.


File name

The log file names are built using a unique sequential 7 digit number. Each time a new log file is created, the log file name number is increased by one. The log file extension is *.txt, e.g. 0000001.txt.

Note

Note that the log name number is not reset on a power-cycle.



Data fields

A column header is included before the first data record. This provides the names of each column and specifies the value separator used.

The interpretation of the columns are:

  • Timestamp: Timestamp in ms (1ms resolution)

  • Type: Message type indicator.

    • 0: Received standard ID message

    • 1: Received extended ID message

    • 8: Transmitted standard ID message

    • 9: Transmitted extended ID message

  • ID: CAN-bus message identifier (in HEX)

  • Length: The length in bytes of the CAN-message data field (in decimal)

  • Data: CAN-bus message data bytes[1] (0-8) (in HEX)

Note

Note that the timestamp for the CL1000 is relative to power-up.