ASC文件数据存储格式.pdf-资料库

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第1页.png

第1页 / 共26页

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第2页.png

第2页 / 共26页

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第3页.png

第3页 / 共26页

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第4页.png

第4页 / 共26页

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第5页.png

第5页 / 共26页

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第6页.png

第6页 / 共26页

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第7页.png

第7页 / 共26页

d6580967-ea9e-41ae-bb43-73f979be08be.pdf-第8页.png

第8页 / 共26页

CAN, Log & Trigger ASC Logging Format Specification Version 1.4.6 of 2016-11-30 Status Publisher Completed Vector Informatik GmbH © 2016 All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Note: Hardcopy documents are not subject to change management. CAN_LOG_TRIGGER_ASC_Format.docx

Document Management Revision list Version Date Editor Section Changes, comments 1.0.0 2005-03-04 1.1.0 2005-03-07 Gia Gia 1.1.1 2006-11-10 Gia 1.1.2 2007-05-25 1.1.3 2007-07-10 Nb Tn 1.1.4 2007-10-04 Gia 1.1.5 2007-10-09 1.1.6 2007-10-17 Sn Nb All 3.4 3.3 3.7 3.3 3.3 Creation Added Begin Triggerblock Event and End Triggerblock Event Added CAN events with symbolic names >32 characters Macros: Record Signals CAN-DLC > 8 Special flags for CAN messages (Spyflag, Wake-Up & etc.) 3.1.1 Added version number into header 3.5, 3.6 Added system variables and environment variables 1.1.7 2008-06-18 Msc 3.1.2 Added split information into header 1.1.8 2008-09-08 Tn 1.1.9 2009-03-27 1.2.0 2009-05-18 Gia Gia 3.8 3.6 1 GPS event added Correction in SystemVariableEvent 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 1.2.3 2011-04-07 Mp 1.2.4 2011-04-12 Sha 1.2.5 2011-09-08 Sha 1.2.6 2011-10-24 Mp 1.2.7 2012-04-20 1.2.8 2012-04-23 Hb Hb 3.9 3.3 3.10 3.11 3.3 3.3 Changes in CAN message and CAN error frame Comment Event (for comments Window) added in Trace Hint 2 added Clarification to CAN frame message length and message duration Event for Global Markers added CAN error frame description Numerical ID-field in CAN frame Vector Informatik GmbH Specification CAN, Log & Trigger ASC Logging Format 2 / 26

Version Date Editor Section Changes, comments 1.2.9 2012-08-24 Chk 3.4, 3.12 1.3.0 2013-04-11 Fsi 1.3.1 2013-10-15 Chk 3.4 1.3.2 2014-03-13 Chk 3.3, 3.4.1 1.3.3 2014-04-15 Srj/Vrd 3.3.1, 3.3.12 1.3.4 2014-05-12 Srj 1.3.5 2014-10-07 Vrd 1.3.6 2014-12-09 Vrd 3.3 3 3.3 Add CAN FD event description. Add symbol description for CAN FD and modify CAN FD specifics for some symbols New CAN FD message and error frame description with 64 byte support. Add chapter 3.4.1 and 3.4.2, message logging on CAN FD channel for CAN Format description for remote frames updated Wrong channel description under 3.4.1 CAN Extended Message Event changed Added milliseconds to and update of header section. Changed order of and ID for CAN Events. Defined newline representation Remote Frame DLC 1.3.7 2014-12-09 Hb 3.3, 3.4 Extended CAN FD frame- and error frame format 1.3.8 2015-01-26 Rue 1.3.9 2015-02-13 Chk 3.7 3.4 Documented flags in system variables Insert FLAG and CRC description 1.4.0 2015-04-07 Chk 3.4, 3.4.2 Add flag description for extFlags of CAN FD error frame, and replace EDL by FDF 1.4.1 2015-04-23 Lke 1.4.2 2015-06-22 Vrd 1.4.3 2015-09-01 Lke 3.12 3.13 3.12 Test structure events added Channel ranges Corrected description event fields execID, elementID. for Test structure 1.4.4 2015-11-24 Chk 3.3, 3.4 Change description for CAN Error Event 1.4.5 2016-11-30 Mom all CI and Layout 1.4.6 2017-03-07 Vrd 3.5, 3.13 Trigger Condition added Vector Informatik GmbH Specification CAN, Log & Trigger ASC Logging Format 3 / 26

Contents 1 Disclaimer ................................................................................................................................................... 5 2 Overview .................................................................................................................................................... 5 3.1 3.1.1 3.1.2 3.4.1 3.4.2 3.2 3.3 3.4 3 Format ........................................................................................................................................................ 6 Header ..................................................................................................................................................... 6 Version number ........................................................................................................................... 6 Split information .......................................................................................................................... 6 Example ................................................................................................................................................... 7 CAN Events on a Classic CAN bus ............................................................................................................ 8 CAN FD .................................................................................................................................................. 12 CAN Events on CAN FD channel ................................................................................................. 13 CAN FD Events............................................................................................................................ 14 Log and Trigger Events .......................................................................................................................... 17 3.5 Environment variables .......................................................................................................................... 18 3.6 3.7 System Variables ................................................................................................................................... 18 3.8 Macros: Signalevents ............................................................................................................................ 19 3.9 GPS events ............................................................................................................................................ 19 3.10 Comment events ................................................................................................................................... 21 3.11 Global marker events ............................................................................................................................ 21 3.12 Test structure events ............................................................................................................................ 22 3.13 Symbols ................................................................................................................................................. 23 Vector Informatik GmbH Specification CAN, Log & Trigger ASC Logging Format 4 / 26

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 problems occurring inside your software on the customer side. Beyond that Vector Informatik reserves the right to change the BLF or ASC data format respectively 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. Vector Informatik GmbH Specification CAN, Log & Trigger ASC Logging Format 5 / 26

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 0 for an explanation of the symbols. Format Example date base timestamps <””|no> internal events logged date Wed Apr 16 09:21:13.159 am 2014 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 measurement 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 is stored in milliseconds. This can be disabled by setting the flag ASCII_Format_Milliseconds = 0 in section [SYSTEM] of the CAN.INI file. 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 Since v7.0 // version .. Example // version 8.2.1 . denotes the CANalyzer/CANoe version number excluding the build number (e.g. v7.0, v7.1, etc…) and denotes changes version within a CANalyzer/CANoe main release (e.g. changes made in a service pack). The . numbers are generally increased with each new main release of CANalyzer/CANoe regardless whether changes have been made to the ASCII format or not. The number of the main release is always zero. In service packs the 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 logging block is configured to split ASCII files. It is written as comment after the version number. Format Since v7.1 // previous log file: Example // 60.0000 previous log file: Inc_L1.asc is the last absolute time stamp of the previous log file and 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. Vector Informatik GmbH Specification CAN, Log & Trigger ASC Logging Format 6 / 26

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 Vector Informatik GmbH Specification CAN, Log & Trigger ASC Logging Format 7 / 26

3.3 CAN Events on a Classic CAN bus The section lists all CAN events in CANoe/CANalyzer ASC logging. See section 0 for an explanation of the symbols. CAN Message Event Simple CAN Message received or transmitted on a CAN channel. Format up to v7.2 Format since v7.5 Format since v8.0 Example d ... d ... Length = BitCount = d ... Length = BitCount = ID = 0.003040 1 123 Tx d 2 00 00 Length = 768000 BitCount = 67 ID = 291 Hint 1: The format of differs when using symbolic logging. In this case the symbolic names are written instead. In this form: d ... 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. 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 up to v7.2 Format since v7.5 Format since v8.0 Example x d ... x d ... Length = BitCount = x d ... Length = BitCount = ID = x 4.876870 1 54C5638x Tx d 8 00 00 00 00 00 00 00 00 Length = 1704000 BitCount = 145 ID = 88888888x CAN Remote Frame Event A CAN Remote Frame received or transmitted on a CAN channel. Format up to v7.2 r Vector Informatik GmbH Specification CAN, Log & Trigger ASC Logging Format 8 / 26

资料库

ASC文件数据存储格式.pdf

相关推荐

硬件开发

热门标签

最新资料