TKE Sweden AB
  • Services
    • Control system design
    • Testing
    • Research / Pre-Study
    • Product development
    • Training
  • IoE by TKE
    • Sensing Network
    • IoEX Gateway
    • Human as a Sensor
    • Analytics
  • Products
    • CANtrace
    • Accessories
    • Interfaces
    • Loggers
    • Sensors
    • Software
    • Switches
  • Articles
    • Case Studies
    • News
    • Research and publications
    • New products
  • Company
  • Contact us
  • Menu Menu
  • Shopping Cart Shopping Cart
    0Shopping Cart

CANtrace Help

A powerful CAN bus analyser software and diagnostic tool

  • CANtrace features
  • Knowledge base
  • Get CANtrace

13. Log File Description

This section describes the content of the log file which is supported in CANtrace.

13.1 Vector ASCII Log File

Tämä sivu on CANtrace help ja Log File Description. WordPress editori tekee jänniä juttuja…

  • The log file is compatible with Vector CANalyzer and CANoe.
  • The log file is logged in hexadecimal.
  • Timestamp contains 6 digits.
  • The content in the log file has different formats for different types of CAN messages.
  • The CAN message up to 8 bytes are logged. Any message larger than 8 bytes are discarded, e.g. for J1939 transport layer frames, the long frames displayed in CANtrace are not logged, only the multiple 8-bytes frames are logged. CANtrace will re-assemble and display the long frame when playing back the log file that contains the multiple frames.

CAN Interface Chip Status / Error information:

CAN Status :  - TxErr :
RxErr :

Comments:

//

13.1.1 Classical CAN Events on Classical CAN channel

CAN message with standard CAN – id:

  d  ...  

CAN message with extended CAN – id:

x    d  ...  

CAN Error Frame:

Error Frame ECC :

CAN Remote Frame:

 r

Figure 13.1.1 Log-file Example

13.1.2 CAN FD

Note:  is not shown in the trace when playing back a log file.

When CANtrace writes a CAN FD log file

  • is not written to the log file.
  • , , , , and are always set to 0.
  • Only bits 4, 6, 12, 13 and 14 are set in .
  • Only bit 31 is set in .

Classical CAN Events on CAN FD Channel

Classical CAN message with standard CAN – id:

CANFD
...

Classical CAN message with extended CAN – id (Indicated in red in the figure below):

  CANFD  x
...

Classical CAN Remote Frame (Indicated in magenta):

CANFDx

CAN FD Events ( Bit 12 set in )

CAN FD message with standard CAN – id:

CANFD
...

CAN FD message with extended CAN – id (Indicated in green):

CANFDx
...

CAN FD Error Frame:

CANFDErrorFrame

Figure 13.1.2 Log-file Example

13.2 Database Log File Description

The log file is logged in hexadecimal.
The log file is compatible with Excel/Matlab.
The database logger logs every CAN message in separate .csv file. All signals of each message is shown in the beginning of each file.

For example, in below figure, from row No. 1 to row No. 11, column explanation from left to right are :

,,,.

From row No. 12 to row No. 25, column explanation from left to right are :

,,,

Figure 13.2 DataBaseLogger example file

Content

  • CANtrace 4.1
  • Important
  • Getting Started
  • Database
  • CastorUSB Settings
  • Vector Settings
  • Kvaser Settings
  • Peak Settings
  • Softing Settings
  • Play Log File Settings
  • Tab Views – Trace Tab
  • Tab Views – Send Tab
  • Tab Views – Data Tab
  • Tab Views – Graph Tab
  • Tab Views – Statistic Tab
  • Tab Views – CANopen NodeScanner Tab
  • Tab Views – Scripting Tab
  • Log Settings
  • Database Log Settings
  • Log File Description
  • License
  • CANopen

TKE Sweden AB
Slöjdgatan 5
S-903 25 Umeå, Sweden

info@tkesweden.se

© Copyright - TKE Sweden AB Privacy and cookies policy
Scroll to top