Intelery CAN Bus Analyzer – Logged Data

This guide explains how to get started with Intelery CAN Bus Analyzer in the use case of analyzing logged CAN data.

Step 1:  Import the CAN log file

About CAN Log file format

About the supported CAN Log file format to be uploaded is a semicolon-separated (‘;’) text file containing one CAN message per line.
This format is compatible with Microchip CAN Logs files and other common 3rd party tools.
If your format differs please contact us that will make sure we add support for other formats.

Field Descriptions:

  • Field 1: Timestamp in Unix format, or milliseconds from measurement start
  • Field 2: Label field. String 1 to 32 characters
  • Field 3: CAN id in hex or decimal, max is (2^29)-1
  • Field 4: Data length from 1 to 8
  • Field 5-13: Data byte. (0x00 to 0xFF) All bytes must be all either in dec or all hex. No mix.

Here’s an example of one message found in one line of a CAN Log file:

336540243;RX;0x1CFE5FFEx;8;0x00;0x01;0x02;0x03;0x04;0x05;0x06;0x07;

Live Data

Overview:

 

Log Viewer

Overview:

Map Editor

Overview:

Importer

Import Log File

 

About CAN Log file format

About the supported CAN Log file format to be uploaded is a semicolon-separated (‘;’) text file containing one CAN message per line.
This format is compatible with Microchip CAN Logs files and other common 3rd party tools.
If your format differs please contact us that will make sure we add support for other formats.

Field Descriptions:

  • Field 1: Timestamp in Unix format, or milliseconds from measurement start
  • Field 2: Label field. String 1 to 32 characters
  • Field 3: CAN id in hex or decimal, max is (2^29)-1
  • Field 4: Data length from 1 to 8
  • Field 5-13: Data byte. (0x00 to 0xFF) All bytes must be all either in dec or all hex. No mix.

Here’s an example of one message found in one line of a CAN Log file:

336540243;RX;0x1CFE5FFEx;8;0x00;0x01;0x02;0x03;0x04;0x05;0x06;0x07;

Import Map