CSS CANedge2 - Log File; Organization; Mdf

CANedge2 Docs, Release FW 01.04.02
0.6 Log file
This page documents the log files stored on the device SD-card.
0.6.1 Organization
Log files are organized by the following path structure:
LOG/[DEVICE_ID]/[SESSION_NUMBER]/[SPLIT_NUMBER].[FILE_EXTENSION]
The path is constructed from the following parts:
• LOG: Static directory name used to store log files
• DEVICE_ID: Globally unique device ID
• SESSION_NUMBER: Increased by one for each power cycle
1
• SPLIT_NUMBER: Reset to 1 on each power cycle and increased by one for each file split
• FILE_EXTENSION: The file extension selected in the configuration (MF4|MFC|MFE|MFM)
For details on log file splits and related limits, see the Logging Configuration section.
File extension
The default extension is MF4. With compression/encryption enabled the extension changes:
Compression enabled Encryption enabled File extension
.MF4
X .MFC
X .MFE
X X .MFM
With both compression and encryption enabled, the data is first compressed, then encrypted.
For details on compression and encryption, see the Logging Configuration section.
Path example
Example: Log file path: 3B912722/00000004/00000189.MF4
• 3B912722: The unique ID of the device which generated the log file
• 00000004: Generated during the 4th session / power cycle
• 00000189: Is log file number 189 of the session (since power cycle)
• MF4: File type
0.6.2 MDF
The CANedge logs data in the industry standard MDF4 format, standardized by ASAM. MDF4 is a
binary format which allows compact storage of huge amounts of measurement data. It is specifically
designed for bus frame logging accross e.g. CAN-bus, LIN-bus and Ethernet. MDF4 is widely adopted
by the industry and supported by many existing tools.
Specifically, the CANedge uses MDF version 4.11 (file extension: *.MF4).
1
The session number is also increased by one if the number of splits in one session exceeds 256
0.6. Log file 47