Specification

CAN, Log & Trigger ASC Logging Format

Author: Gianfranco Tinnirello

Version: 1.3.5 dated 2014-10-07
Status: released (in process / completed / inspected / released)

Number of Pages: 21
 Specification --- CAN, Log & Trigger ASC Logging Format II

Document Management
Release and Release History
Name Role Version Date
Stephan, Michael (Sn) PLD 1.1.0 2005-03-07
Tinnirello, Gianfranco (Gia) PLD 1.1.9 2009-03-27
Tinnirello, Gianfranco (Gia) PLD 1.2.0 2009-05-18
Tinnirello, Gianfranco (Gia) PLD 1.2.2 2010-12-23
Tinnirello, Gianfranco (Gia) PLD 1.2.3 2011-04-07
Tinnirello, Gianfranco (Gia) PLD 1.2.6 2011-10-24
Hesselmaier, Bodo (Hb) PLD 1.2.7 2012-04-20
Hesselmaier, Bodo (Hb) PLD 1.2.8 2012-04-23
Van Splunter, Ronald (Vrd) PLD 1.3.3 2014-04-16
Van Splunter, Ronald (Vrd) PLD 1.3.5 2014-10-07

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification --- CAN, Log & Trigger ASC Logging Format III

Revision list
Version Date Editor Section Changes, comments
1.0.0 2005-03-04 Gia All Creation
1.1.0 2005-03-07 Gia 3.4 Added Begin Triggerblock Event and End Trig-
gerblock Event
1.1.1 2006-11-10 Gia 3.3 Added CAN events with symbolic names >32
characters
1.1.2 2007-05-25 Nb 3.7 Macros: Record Signals
1.1.3 2007-07-10 Tn 3.3 CAN-DLC > 8
1.1.4 2007-10-04 Gia 3.3 Special flags for CAN messages (Spyflag, Wake-
Up & etc.)
1.1.5 2007-10-09 Sn 3.1.1 Added version number into header
1.1.6 2007-10-17 Nb 3.5, 3.6 Added system variables and environment varia-
bles
1.1.7 2008-06-18 Msc 3.1.2 Added split information into header
1.1.8 2008-09-08 Tn 3.8 GPS event added
1.1.9 2009-03-27 Gia 3.6 Correction in SystemVariableEvent
1.2.0 2009-05-18 Gia 1 Added Disclaimer
1.2.1 2010-10-26 Sha 3.3; 3.9 New fields added to CAN Messages
1.2.2 2010-11-29 Hb Changes in CAN message and CAN error frame
1.2.3 2011-04-07 Mp 3.9 Comment Event (for comments in Trace Win-
dow) added
1.2.4 2011-04-12 Sha 3.3 Hint 2 added
1.2.5 2011-09-08 Sha 3.10 Clarification to CAN frame message length and
message duration
1.2.6 2011-10-24 Mp 3.11 Event for Global Markers added
1.2.7 2012-04-20 Hb 3.3 CAN error frame description
1.2.8 2012-04-23 Hb 3.3 Numerical ID-field in CAN frame
1.2.9 2012-08-24 Chk 3.4, 3.12 Add CAN FD event description. Add symbol
description for CAN FD and modify CAN FD
specifics for some symbols
1.3.0 2013-04-11 Fsi New CAN FD message and error frame descrip-
tion with 64 byte support.
1.3.1 2013-10-15 Chk 3.4 Add chapter 3.4.1 and 3.4.2, for CAN message
logging on CAN FD channel
1.3.2 2014-03-13 Chk 3.3, 3.4.1 Format description for remote frames updated
Wrong channel description under 3.4.1 CAN
Extended Message Event changed
1.3.3 2014-04-15 Srj/Vrd 3.3.1, Added milliseconds to <FullTime> and update of
3.3.12 header section.
1.3.4 2014-05-12 Srj 3.3 Changed order of <MessageFlags> and ID for
CAN Events.

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification --- CAN, Log & Trigger ASC Logging Format IV

Revision list
Version Date Editor Section Changes, comments
1.3.5 2014-10-07 Vrd 3 Defined newline representation

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification --- CAN, Log & Trigger ASC Logging Format V

Table of contents
1 Disclaimer .................................................................................................................... 1

2 Overview ...................................................................................................................... 1

3 Format.......................................................................................................................... 1
3.1 Header .................................................................................................................................... 1
3.1.1 Version number ........................................................................................................... 2
3.1.2 Split information.......................................................................................................... 2
3.2 Example ................................................................................................................................. 3
3.3 CAN Events ........................................................................................................................... 4
3.4 CAN FD Events ..................................................................................................................... 7
3.4.1 CAN Events on CAN FD channel ............................................................................... 7
3.4.2 CAN FD Events........................................................................................................... 8
3.5 Log and Trigger Events ......................................................................................................... 9
3.6 Environment variables ......................................................................................................... 10
3.7 System Variables ................................................................................................................. 10
3.8 Macros: Signalevents ........................................................................................................... 11
3.9 GPS events ........................................................................................................................... 11
3.10 Comment events .................................................................................................................. 12
3.11 Global marker events ........................................................................................................... 12
3.12 Symbols ............................................................................................................................... 13

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 1

1 Disclaimer
Severability clause - Restrictions for the usage of Vector logging data formats outside of Vector
products

The format specification / access functions for the Vector BLF and ASC logging data formats are
made available under the restrictions and conditions cited hereafter.
Please note that Vector Informatik neither gives any guarantee nor assumes any liability beyond
compulsory legal regulations for the BLF or ASC logging format respectively as well as for the
access functions to the single objects.
Vector Informatik disclaims all liability for errors which might be contained in the access functions
or the format specification itself.
Vector Informatik does neither provide support for the integration into your software nor for prob-
lems occurring inside your software on the customer side.
Beyond that Vector Informatik reserves the right to change the BLF or ASC data format respective-
ly anytime without prior notification. Therefore, the compatibility of the format is not ensured.

2 Overview
The document specifies the format of CAN, Log and Trigger events in the CANoe/CANalyzer
ASC logging.

3 Format
Newline is coded in the CR+LF representation.

3.1 Header
A log file in ASCII format starts with a header. The header contains general information about the
logging file. See also section 3.12 for an explanation of the symbols.
Format date <WeekDay> <Month> <Date> <Fulltime> <Year>
base <hex|dec> timestamps <absolute|relative>
<””|no> internal events logged
date Wed Apr 16 09:21:13.159 am 2014
Example base hex timestamps absolute
internal events logged

• base indicates the number system in which values are logged. It can be in hexadecimal or
decimal notation.
• timestamps indicates whether the timestamps are written absolute to the start of the meas-
urement or relative to the preceding event.
• internal events logged indicates whether internal events were logged or not.

Hint: Starting with CANalyzer/CANoe v8.2 SP2 the <Fulltime> is stored in milliseconds.
This can be disabled by setting the flag ASCII_Format_Milliseconds = 0 in section
[SYSTEM] of the CAN.INI file.

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 2

3.1.1 Version number

Starting with CANalyzer/CANoe v7.0 a version number is written after the header in form of a
comment:
Format // version <major>.<minor>.<patch>
Since
v7.0
Example // version 8.2.1

<major>.<minor> denotes the CANalyzer/CANoe version number excluding the build number
(e.g. v7.0, v7.1, etc…) and <patch> denotes changes version within a CANalyzer/CANoe main
release (e.g. changes made in a service pack).
The <major>.<minor> numbers are generally increased with each new main release of CANalyz-
er/CANoe regardless whether changes have been made to the ASCII format or not. The <patch>
number of the main release is always zero.
In service packs the <patch> number is increased if and only if changes and/or additions have been
made to the ASCII format.

3.1.2 Split information

Starting with CANalyzer/CANoe v7.1 split information is written in all subsequent files if a log-
ging block is configured to split ASCII files. It is written as comment after the version number.
Format // <time> previous log file: <filename>
since
v7.1
Example // 60.0000 previous log file: Inc_L1.asc

<time> is the last absolute time stamp of the previous log file and <filename> is the filename of the
previous log file without path information. This time stamp is always absolute even if the events
are logged with relative time stamps. With this information it is possible to restore the original time
stamps of events logged with relative time stamps if a subsequent file is replayed.

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 3

3.2 Example
The following logging contains CAN Message events, CAN Extended Message events, contains
CAN FD Message events, CAN FD Extended Message events, Errorframes, CAN Bus Statistic
descriptions, Log Trigger events, Log Direct Start events, CAN Status events, CAN Remote Frame
events and CAN Error events.
date Die Dez 21 11:29:01 2004
base hex timestamps absolute
internal events logged
// version 7.0.0
Begin Triggerblock Mon Mar 7 01:21:51 pm 2005
0.0000 Start der Messung
0.0006 CAN 1 Status:chip status error active
0.0006 CAN 2 Status:chip status error active
1.0100 1 Statistic: D 0 R 0 XD 0 XR 0 E 0 O 0 B 0.0%
1.0100 2 Statistic: D 0 R 0 XD 0 XR 0 E 0 O 0 B 0.0%
2.0000 log direct start (0ms)
2.0000 log trigger event
2.5009 1 64 Tx d 8 00 01 02 03 04 05 06 07
2.5010 2 C8x Rx d 8 09 08 07 06 05 04 03 02
2.5010 1 200 Tx r
0.010460 CANFD 1 101 Tx 1 0 d 8 8 F1 F1 F1 F1 F1 F1 F1 F1 Length = 209000 BitCount = 128 ID = 257
0.014165 CANFD 1 1C4D80A7x Tx 1 0 d 8 8 88 88 88 88 88 88 88 88 Length = 278000 BitCount = 140 ID =
474841255x
0.010235 CANFD 1 100 Tx 1 0 r 8 Length = 138000 BitCount = 57 ID = 256
2.5010 1 ErrorFrame
2.5010 CAN 1 Status:chip status error active - TxErr: 0 RxErr: 1
2.5010 CAN 2 Status:chip status error active - TxErr: 0 RxErr: 1
2.7000 log trigger event (this trigger was in post trigger time of last block)
3.0100 1 Statistic: D 1 R 0 XD 0 XR 0 E 1 O 0 B 0.2%
3.0100 2 Statistic: D 1 R 0 XD 0 XR 0 E 1 O 0 B 0.2%
4.0000 log direct stop (0ms)
4.0000 log trigger event
End TriggerBlock

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 4

3.3 CAN Events

The section lists all CAN events in CANoe/CANalyzer ASC logging. See section 3.12 for an ex-
planation of the symbols.

CAN Message Event

Simple CAN Message received or transmitted on a CAN channel.
Format <Time> <Channel> <ID> <Dir> d <DLC> <D0> <D1>...<D8> <MessageFlags>
up to
v7.2
Format <Time> <Channel> <ID> <Dir> d <DLC> <D0> <D1>...<D8> Length = <Mes-
sageDuration> BitCount = <MessageLength> <MessageFlags>
since
v7.5
Format <Time> <Channel> <ID> <Dir> d <DLC> <D0> <D1>...<D8> Length = <Mes-
sageDuration> BitCount = <MessageLength> ID = <IDnum> <MessageFlags>
since
v8.0
Example 0.003040 1 123 Tx d 2 00 00 Length = 768000 BitCount = 67 ID =
291

Hint 1: The format of <ID> differs when using symbolic logging. In this case the symbolic
names are written instead. In this form:
<Time> <Channel> <ID> <Dir> d <DLC> <D0> <D1>...<D8>

Symbolic logging is also valid for CAN Extended Message Events & CAN Remote
Frame Events.
Hint 2: The Length, BitCount, and numerical ID-fields can be suppressed by setting the flag
ASCII_Format_7_2=1 in section [CAN] of the CAN.INI file, which is located in the
Exec32 folder. This flag is available from CANoe/CANalyzer version 7.5 SP3.

CAN Extended Message Event

CAN Message with extended identifier received or transmitted on a CAN channel.
Format <Time> <Channel> <ID>x <Dir> d <DLC> <D0> <D1>...<D8> <MessageFlags>
up to
v7.2
Format <Time> <Channel> <ID>x <Dir> d <DLC> <D0> <D1>...<D8> Length = <Mes-
sageDuration> BitCount = <MessageLength> <MessageFlags>
since
v7.5
Format <Time> <Channel> <ID>x <Dir> d <DLC> <D0> <D1>...<D8> Length = <Mes-
sageDuration> BitCount = <MessageLength> ID = <IDnum>x <MessageFlags>
since
v8.0
Example 4.876870 1 54C5638x Tx d 8 00 00 00 00 00 00 00 00 Length
= 1704000 BitCount = 145 ID = 88888888x

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 5

CAN Remote Frame Event

A CAN Remote Frame received or transmitted on a CAN channel.
Format <Time> <Channel> <ID> <Dir> r
up to
v7.2
Format <Time> <Channel> <ID> <Dir> r Length = <MessageDuration> BitCount =
<MessageLength> ID = <IDnum>x
since
v7.5
Example 2.5010 1 200 Tx r Length = 1704000 BitCount = 145 ID = 88888888x

CAN Error Frame

A CAN Error Frame received on a CAN channel.
Format <Time> <Channel> ErrorFrame
up to
v7.2
Format CANcardXL, CANcaseXL, CANboardXL, and all other interfaces with
since SJA1000:
v7.5 <Time> <Channel> ErrorFrame ECC:<ECC>

Interfaces with CAN-Core:

<Time> <Channel> ErrorFrame Flags = <flags> CodeExt = <codeExt> Code =

<code> ID = <ID> DLC = <DLC> Position = <Position> Length = <Length>

Flags:
Bit field defining the validity of the parameters Code, CodeExt, ID, DLC, Position, and
Length.
Bit Meaning
0 SJA 1000 ECC is valid
1 Vector CAN Core Error Code is valid
2 Vector CAN Core Error Position is valid
4 Vector CAN Core Frame Length in ns is valid
Code:
Content of Philips SJA1000 Error Code Capture (ECC) register, or the Vector CAN-
Core error register (see also mFlags).
SJA1000-ECC
See documentation of Philips SJA1000 CAN Controller.
Vector CAN-Core
Bit Meaning
0-5 0: Bit Error
1: Form Error
2: Stuff Error
3: Other Error
4: CRC Error
5: Ack-Del-Error
6-7 0: RX-NAK-Error
1: TX-NAK-Error
2: RX-Error
3: TX-Error

CodeExt:

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 6

CAN Error Frame

Extended error flags (see also the remarks below the table).
Bit Meaning
0-4 Segment (only SJA1000)
5 Direction, 1=RX
6-11 Error Code
0 Bit Error
1 Form Error
2 Stuff Error
3 Other Error
4 CRC Error 1
5 ACK-DEL Error 1
12-13 Extended Direction 1
0 RX NAK
1 TX NAK
2 RX
3 TX
14 1 = The error frame was send from the application

Remarks
1 Only valid for interfaces with Vector CAN-Core (CANcardXLe, VN7600, VN16xx, VN89xx, and oth-
ers).

2 The validity of ID, DLC, and the data field depends on the type and position of the disturbance. Exam-
ple: If the message is disturbed in the ID-field, then only the first bits of the ID may be valid, but not
the DLC and the data field. The error position is not the position of the disturbance. Example: If the er-
ror position is located in the CRC-field, then the message may have been disturbed in any other field,
and the erroneous CRC is the result of that disturbance.

Examples 1.592186 1 ErrorFrame ECC: 10100010

1.592186 2 ErrorFrame Flags = 0xe CodeExt = 0x20a2 Code = 0x82

ID = 0 DLC = 0 Position = 5 Length = 11300

CAN Bus Statistics Event

CAN Statistic event, which contains statistic information about the CAN channels.
“D” stands for CAN Data Frames
“R” stands for CAN Remote Frames
“XD” stands for CAN Extended Data Frames
“XR” stands for CAN Extended Remote Frames
“E” stands for Error Frames
“O” stands for Overload Frames
“B” stands for Busload
Format <Time> <Channel> Statistic: D <StatNumber> R <StatNumber> XD <StatNum-
ber> XR <StatNumber> E <StatNumber> O <StatNumber> B <StatPercent>%
Example 1.0100 1 Statistic: D 1000 R 15 XD 0 XR 0 E 0 O 0 B 0.0%

CAN Error Event

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 7

An event that provides CAN error information.

Format <Time> CAN <Channel> Status:<Error>

Example 0.0006 CAN 2 Status:chip status error active

CAN Overload Frame Event

An Overload Frame received on a CAN channel.
Format <Time> <Channel> OverloadFrame

Example 2.5158 1 OverloadFrame

3.4 CAN FD Events

The section lists all CAN FD events in CANoe/CANalyzer ASC logging. See section 3.12 for an
explanation of the symbols.

Note:
<D1> … <D64> refer to the data fields of the CAN FD message, opposed to standard CAN log for-
mat, this field is not fixed to 8 bytes, instead the length is depending on the value of the
field <Datalength>. For example, when <Datalength> is 12, <D1> … <D12> is
logged. For CAN remote frames the <Datalength> is 0.
<BitTimingConfArb>, <BitTimingConfData> refer to the bit timing parameters used for arbitra-
tion and data phase. These fields can be interpreted 32 bit long bit fields:
Bit 0-7: Quartz Frequency
Bit 8-15: Prescaler
Bit 16-23: BTL Cycles
Bit 24-31: Sampling Point
These values are only available, if supported by the hardware/driver, otherwise <Bit-
TimingConfArb> and <BitTimingConfData> are 0.

3.4.1 CAN Events on CAN FD channel

CAN Message Event
Simple CAN Message received or transmitted on a CAN FD channel.
Format <Time> CANFD <Channel> <Dir> <ID> <SymbolicName> <BRS> <ESI> <DLC>
<DataLength> <D1> … <D8> <MessageDuration> <MessageLength> <Flags>
since <CRC> <BitTimingConfArb> <BitTimingConfData>
v8.1
Example 1.365572 CANFD 2 Rx 0 0 0
8 8 00 00 00 00 00 00 00 00 246015 127 200000 145b 46500250
500a0450

CAN Extended Message Event

CAN Message with extended identifier received or transmitted on a CAN FD channel.
See CAN-FD Message description for information about the individual fields.

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 8

CAN Extended Message Event

Format <Time> CANFD <Channel> <Dir> <ID> <SymbolicName> <BRS> <ESI> <DLC>
<DataLength> <D1> … <D8> <MessageDuration> <MessageLength> <Flags>
since <CRC> <BitTimingConfArb> <BitTimingConfData>
v8.1
Example 1.581796 CANFD 2 Rx 0x New_Message_1 0 0
f 8 00 00 00 00 00 00 00 00 292015 150 200000 28ac 46500250
500a0450

CAN Remote Frame Event

A CAN Remote Frame received or transmitted on a CAN channel. The <DataLength> is set to 0
and the data bytes <Dn> not available.
Format <Time> CANFD <Channel> <Dir> <ID> <SymbolicName> <BRS> <ESI> <DLC>
<DataLength> <MessageDuration> <MessageLength> <Flags> <CRC> <BitTim-
ingConfArb> <BitTimingConfData>
Example 0.844500 CANFD 2 Rx 0x New_Message_1 0 0
f 0 136015 72 200010 122f 46500250 500a0450

3.4.2 CAN FD Events

CAN FD Message Event
Simple CAN FD Message received or transmitted on a CAN FD channel.
Format <Time> CANFD <Channel> <Dir> <ID> <SymbolicName> <BRS> <ESI> <DLC>
<DataLength> <D1> … <D64> <MessageDuration> <MessageLength> <Flags>
since <CRC> <BitTimingConfArb> <BitTimingConfData>
v8.1
Example 1.862778 CANFD 2 Tx 0 0 0
f 64 01 02 03 04 05 06 07 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1340000 673
301040 17771a 46500250 500a0450

CAN FD Extended Message Event

CAN FDMessage with extended identifier received or transmitted on a CAN channel.
See CAN-FD Message description for information about the individual fields.
Format <Time> CANFD <Channel> <Dir> <ID> <SymbolicName> <BRS> <ESI> <DLC>
<DataLength> <D1> … <D64> <MessageDuration> <MessageLength> <Flags>
since <CRC> <BitTimingConfArb> <BitTimingConfData>
v8.1
Example 2.358646 CANFD 2 Tx 0x New_Message_1 0 0
f 64 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22
23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 1228000 617
301040 15300e 46500250 500a0450

CAN FD Error Frame

An Error Frame received on a CAN-FD channel with a dominant EDL bit. In case of certain errors
(NACK Error, CRC Error) the hardware/driver may provide further information (ID, DLC, Data
…) about the partial frame preceding the actual Error Frame, otherwise these values are 0. For fur-
ther restrictions regarding the validity of these fields and a detailed description of the <flags>,
<code> and <codeExt> fields, refer to the description of CAN Error Frame.

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 9

CAN FD Error Frame

Format <Time> CANFD <Channel> <Dir> ErrorFrame <ErrorText> <flags> <code>
<codeExt> <Phase> <Position> <ID> <BRS> <ESI> <DLC> <DataLength> <D1> …
<D64> <MessageDuration> <Flags> <CRC> <BitTimingConfArb> <BitTim-
ingConfData>
Examples 3.923364 CANFD 2 Tx ErrorFrame Not Acknowledge error, dominant er-
ror flag fffe c7 31ca Data 45 ff 1 0 f 64 aa aa aa aa
aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
aa aa aa aa aa aa aa aa aa aa aa aa 336484 3 0 51103250
460a0250

CAN FD Bus Statistics Event

Not defined yet, see CAN Statistics Event
Format
Example

CAN FD Overload Frame

Not defined yet, see CAN Overload Frame
Format
Example

3.5 Log and Trigger Events

The section lists all Log and Trigger events in CANoe/CANalyzer ASC logging. See section 3.12
for an explanation of the symbols.

Log Trigger Event

A Log Trigger event. There can be additional information appended at the end of the line, e.g. “
(this trigger was in post trigger time of last block)” or “ (ignored)”.
Format <Time> log trigger event

Example 2.0000 log trigger event

Log Direct Start Event

An event that is written if the logging was started directly by the button in the measurement
setup or by the CAPL function StartLogging().
Format <Time> log direct start (<PreTrigger>ms)

Example 2.1100 log direct start (2000ms)

Log Direct Stop Event

An event that is written if the logging was stopped directly by the buttons in the measurement
setup or by the CAPL function StopLogging().

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 10

Format <Time> log direct stop (<PostTrigger>ms)

Example 2.1100 log direct stop (1000ms)

Begin Triggerblock Event

An event that is written when a trigger block begins.
Format Begin Triggerblock <WeekDay> <Month> <Date> <FullTime> <Year>

Example Begin Triggerblock Mon Mar 7 01:21:51 pm 2005

End Triggerblock Event

An event that is written when a trigger block ends.
Format End TriggerBlock

Example End TriggerBlock

3.6 Environment variables

The section lists the environment variable event in CANoe/CANalyzer ASC logging. See section
3.12 for an explanation of the symbol <time>. See this chapter for an explanation of the other sym-
bols. The setting hex/dec affects the format of <value> for environment variables from type integer
and data.
Environment Variables Event
An event that is written if the value of a environment variable changed.
<evname>: a string which contains the environment variable name
<value>: the environment value as number, string or databytes (depend on variable type)
OR a string from the value description table (if exists; only for integer variable type)
Format <Time> <evname> := <value>
Int 2.130000 Int_Ev := 1
Float 2.567000 Float_Ev := -1.125
String 3.830000 String_Ev := “Radio SWR3”
Data 2.250000 Data_Ev := [ 41 41 41 41 ]

3.7 System Variables

The section lists the system variable event in CANoe/CANalyzer ASC logging. See section 3.12
for an explanation of the symbol <time> and symbol <svtype>. See this chapter for an explanation
of the other symbols. The setting hex/dec affects the format of <value> for system variables from
type integer.
System Variables Event
An event that is written if the value of a system variable changed.
<svtype>: a number which represents the variable data type
<flag>: two flags: Unused.
<path>: the full path (name with namespace) of the system variable
<value>: the value as number or string (depend on variable data type).
<valuetype>: (only for arrays) value type of elements: D: array of doubles, A: array of longs

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 11

<count>: (only for arrays) size of array

Format <Time> SV: <svtype> <flag> <flag> <path> = <value>
Format <Time> SV: <svtype> <flag> <flag> <path> = <valuetype><count> <value>
(Arrays)
Example 1.200000 SV: 2 0 0 ::NS1::IntVar = 4
int
Float 1.370000 SV: 1 0 0 ::NS1::FloatVar = 4.1
String 1.580000 SV: 3 0 0 ::NS1::StringVar = "Value: 4"
Int array 1.690000 SV: 5 0 0 ::NS1::IntArray = A3 4 5 2
Float array 2.000000 SV: 4 0 0 ::NS1::FloatArray = D3 4.1 2.9 6

3.8 Macros: Signalevents

The section lists all Signal events for macros in CANoe/CANalyzer ASC logging. See section 3.12
for an explanation of the symbol <time>. See this chapter for an explanation of the other symbols.
Macro Signal Event: CAN, LIN and FlexRay
An event that is written if the user change a signal value with a panel control, and the macro recording is on.
<bussystem>: F = FlexRay / L = Lin / nothing = CAN
<channel>: the number of the CAN/LIN/FlexRay channel
<node>: a string which contains the node name of the signal
<message>: a string which contains the message name of the signal
<signal>: a string which contains the signal name
<value>: the signal value as number OR a string from the value description table (if exists)
Format <Time> <bussystem> <channel> <node>::<message>::<signal> = <value>
CAN (value as number) 2.350000 1 Node::aCANMessage::aBitSignal = 1
CAN (symbolic value) 2.350000 1 Node::aCANMessage::aBitSignal = Eins
LIN 5.000000 L1 L_Slave::aLINMessage::aLINBitSignal = 0
FlexRay 1.110000 F1 FR_ECU::aFlexRayMessage::aFRSignal = 3

3.9 GPS events

The section lists the GPS event in CANoe ASC logging. See section 3.12 for an explanation of the
symbol <time>. See this chapter for an explanation of the other symbols.
GPS Event
An event that is written if an event is received on the GPS channel.
<channel>: the number of the GPS device on which the event is received
<latitude>: the latitude value of the GPS event
<longitude>: the longitude value of the GPS event
<altitude>: the altitude value of the GPS event
<speed>: the speed value of the GPS event
<course>: the course value of the GPS event
Format <Time> GPS device: <channel> La:<latitude> Lo: <longitude> Alt:
<altitude> Sp: <speed> Co: <course>
Example 2.097603 GPS-Device: 1 La: 48.825100 Lo: 9.091267 Alt:
325.399994 Sp: 29.686400 Co: 87.099998

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 12

3.10 Comment events

The section lists the Comment event in CANoe ASC logging. See section 3.12 for an explanation
of the symbol <time>.
Comment Event
A comment event that is written before another event that was commented in Trace Window. Commenting events is
supported only in Trace Window, so this event can be written only during the export from Trace window.
<type>: the type of the commented event
<comment text>: the text of the comment
Format <Time> Comment: <type> <comment text>
Example 1.593770 Comment: 105 testComment

3.11 Global marker events

The section lists the Global marker event in CANoe ASC logging. See section 3.12 for an explana-
tion of the symbol <time>.
Comment Event
A global marker event that is written if global marker is defined for a time stamp or for another event. If a
global marker event is assigned to another event (set in Trace Window) it has to be written before that
event. Global marker events can be written only during the export from Trace window.
<type>: the type of the commented event
<background color>: background color of the marker group
<foreground color>: foreground color of the marker group
<relocatable>: defines whether the marker can be moved
<group name>: the name of the marker group
<marker name>: the name of the marker
<description> marker description
Format <Time> <type> <background color> <foreground color> GMGroup: <group
name> GMMarker: <marker name> GMDescription: <description>
Example 2.200804 0 16777215 0 1 GMGroup: Marker Group GMMarker: [1]
GMDescription: description

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 13

3.12 Symbols
Symbol Width Width Meaning Range Example Special
in chars in chars
(hex) (dec)
<Time> >=9 absolute or relative time 1234.5678 usually 4
in seconds decimal
places
<Channel> 2 - 10 Number of the CAN [A-Za-z0-9] 1, CAN 1,
channel. {2,10} CAN FD
1
<ID> 15 15 Numeric identifier Normal mode: In extended
(numeric log- 0x0…0x7FF mode only a
ging) width of 14
Extended Mode: characters,
0x0…0x1FFFFF because of
‘x’ at the
end. CAN
FD represen-
tation only in
hex.
<ID> >= 32 >=32 Symbolic identifier
(symbolic log-
Differences to numeric
ging)
format:
1. Four spaces instead
of one after the Identifi-
er
2. Length of <ID> is
>=32. For short sym-
bolic names (<32) the
remaining positions are
filled with spaces.
<Dir> 4 direction of transmis- Rx, Tx, TxRq Rx
sion
<DLC> 1 2 data length code Hex: 0…F B CAN FD
Note: the DLC field is Dec: 0…15 12 representa-
written as one hex digit. tion is always
In case DLC is greater dec
8, there are max. 8 data
bytes written/read in.
<MessageFlags> 2 2 Some special message TE, WU, XX TE
flags that are written at
the end of a logging
line. Possible values
are:
- “TE”: Transmission
Error (NERR signal).
Indicates whether a line
has failed during a two-
wire operation. Espe-
cially available on Sin-
gle-Wire mode.
- “WU”: Wake-Up.

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 14

Symbol Width Width Meaning Range Example Special

in chars in chars
(hex) (dec)
Indicates whether a
message was transmit-
ted with overvoltage
with the purpose of
waking up the CAN
controller.
- “XX”: Both, “TE”
and “WU” occurred.
<StatNumber> 1-10 the number of received 0…4294967295 1056
statistic events
<StatPercent> 3-6 the busload in percent 0.0 … 100.0 11.94
<PreTrigger> 1-10 the pre trigger time in 0 … 1316134911 2000
ms
<PostTrigger> 1-10 the post trigger time in 0 … 1316134911 2000
ms
<Error> 0- the error message of the “rx queue
unde- CAN error event overrun”
fined
<Dx> 3 2 data byte x 0…255 1E CAN FD
only hex
representa-
tion
<WeekDay> 3 3 a string that represents a Mon, Tue, Wed, Mon Different
day of the week Thu, Fri, Sat, Sun range in
German
version:
Mon, Die,
Mit, Don,
Fre, Sam,
Son
<Month> 3 3 a string that represents a Jan, Feb, Mar, Nov Different
month Apr, May, Jun, range in
Jul, Aug, Sep, German
Oct, Nov, Dec version:
Jan, Feb,
Mär, Apr,
Mai, Jun, Jul,
Aug, Sep,
Okt, Nov,
Dez
<Date> 1-2 1-2 a number that repre- 1…31 15
sents the date.
<FullTime>1 15 15 a string that represents a 00:00:00.000 … 01:13:17.1 Different
time in the current for- 12:60:60.999 23 pm range in
mat. German

1
Starting with CANalyzer/CANoe 8.2 SP2 the <Fulltime> is stored in milliseconds. This can be disabled by setting the
flag ASCII_Format_Milliseconds = 0 in section [SYSTEM] of the CAN.INI file. In that case the string-width is 4
characters smaller.

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 15

Symbol Width Width Meaning Range Example Special

in chars in chars
(hex) (dec)
hh:mm:ss.ms am|pm version:
00:00:00.000
…
23:60:60.999
In German
version ‘am’
and ‘pm’ are
not used.
Therefore the
width is only
12 chars.
<Year> 4 4 a string that represents a 1999
year.
<svtype> 1 1 a number that repre- 1…5 2
sents the variable data
type of system variable:
1 = Float
2 = Integer
3 = String
4 = Array of Floats
5 = Array of Integers
<Mes- Message duration [in 768000
sageDuration> nanoseconds]. Not
including 3 Interframe
Space bit times and by
Rx-messages also not
including 1 End-Of-
Frame bit time
<Message- Total number of bits of 67
Length> the message including
EOF and Interframe
Space [in bits]
<BRS> 1 Bit rate switch flag for 0-1 0
CAN FD. Indicate bit
rate switch is enabled or
disabled.
<ESI> 1 Error state indicator 0-1 0
flag for CAN FD. Indi-
cate a transceiver is in
error active or error
passive mode.
<DataLength> 3 Valid length of the 0-64 20
message in bytes.
<BitTimingCon- 8 Bit timing information May be 0, if
fArb> for CAN-FD frames. not supported
by the CAN-
controller
<BitTim- 8 Bit timing information May be 0, if
ingConfData> for CAN-FD frames not supported
by the CAN-
controller

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07

 Specification CAN, Log & Trigger ASC Logging Format 16

2014 Vector Informatik GmbH CAN_LOG_TRIGGER_ASC_Format.doc Version 1.3.5 dated 2014-10-07