ETAS ProF Documentation Ver1.2.9: INCA软件与通讯协议详解

需积分: 0 28 浏览量更新于2024-06-16 2 收藏 1.29MB PDF 举报

《ProF Documentation - Ver1.2.9》是ETAS（易特驰）于2014年4月14日发布的关于INCA软件的详细开发文档，主要关注于通讯相关的配置和协议处理。INCA是一款强大的测试工具，适用于汽车电子系统中的诊断和测试，特别关注于KWP、CCP、UDS和XCP等关键通讯协议。文档涵盖了多个版本更新，每个版本都针对特定功能进行了改进和修正。其中，1.1.1版本介绍了UDS_ACCESS_TIMING，这是在CAN总线技术中用于控制数据交换时间的重要设置，但仅适用于CANTL（CAN Target Layer）环境。1.1.2版本提到了ETK_RESET的修正，可能涉及到系统的初始化或故障恢复功能。 ST_MIN参数在1.1.3版本的CNF文件（INCA配置文件）中得到了关注，这个参数可能与数据传输速率或最小通信周期有关。1.1.4和1.1.5涉及UDSX的功能，如文件上传和通过标识符读取数据，以及数据的缩放处理。后续的1.1.6和1.1.7版本可能记录了关于停止功能的修改，以及对细节描述的微调。在1.2版本中，重点在于1.2.1部分，该版本增加了对UDS压缩闪存的描述，这可能是为了优化数据传输效率，参考了TFS（Toolbox for System Integration）的解决方案编号335564。1.2.2版本则调整了OVERRULED_ST_MIN的描述，以适应INCA 7.1的新变化，可能涉及到性能优化或新功能的引入。 1.2.3版本由Woit在2013年3月22日更新，添加了CHECKSUM_BYTE_OR相关章节，这可能涉及到数据校验和一致性检查的实现，确保通信的可靠性和准确性。整个文档不仅提供了技术细节，还反映了INCA软件随着时间和ETAS技术发展而进行的持续改进，对于理解和使用INCA进行汽车电子系统测试的开发者来说，这是不可或缺的参考资料。

0010

($2x)

bitMappedReportedWithOutMask

Bit mapped encoding uses individual bits or small groups of bits to represent

status. For every bit which represents status, a corresponding mask bit is

required as part of the parameter definition. The mask indicates the validity of

the bit for particular applications. This type of bit mapped parameter does not

contain a second byte; which contains the validity mask.

Note: "Reported without mask" specifies, that during current data transmission

no mask byte is included in the current data stream.

U BMR

WOM

0011

($3x)

bitMappedReportedWithMask

Bit mapped encoding uses individual bits or small groups of bits to represent

status. For every bit which represents status, a corresponding mask bit is

required as part of the parameter definition. The mask indicates the validity of

the bit for particular applications. This type of bit mapped parameter contains

two bytes; one representing status and one containing the validity mask.

Note: "Reported with mask" specifies, that during current data transmission the

mask byte is included in the current data stream.

U BMR

0100**

($4x)

binaryCodedDecimal

Conventional Binary Coded Decimal encoding is used to represent two numeric

digits per byte. The upper nibble is used to represent the most significant digit (0

- 9), and the lower nibble the least significant digit (0 -9).

Note: Diagnostic Trouble Codes are of type BCD and described in SAE J2012.

U BCD

0101

($5x)

stateEncodedVariable (1 byte)

This encoding uses a binary weighting scheme to represent up to 256 distinct

states. An example is a parameter which represents the status of the Ignition

Switch. Codes "00", "01", and "03" may indicate ignition off, locked, run, and

start, respectively. The representation is always limited to one (1) byte.

U SEV

0110**

($6x)

ASCII (1 to 15 bytes for each scalingByte)

Conventional ASCII encoding is used to represent up to 128 standard

characters MSB = logic 0. An additional 128 custom characters may be

represented with the MSB = logic 1.

U ASCII

0111

($7x)

signedFloatingPoint (ANSI / IEEE Std 754 - 1985)

Floating point encoding is used for data that needs to be represented in floating

point or scientific notation. Standard IEEE formats shall be used.

U SFP

1000**

($8x)

packet

Packets contain multiple data values, usually related, each with unique scaling.

Scaling information is not included for the individual values.

U P

1001

($9x)

formula (1 byte)

The formulas referenced by the identifiers $00 - $7F are reserved by

Recommended Practice VDA 14230-3. The formulas referenced by the

identifiers $80 - $FF are vehicle manufacturer specific.

U F

1010 - 1111

($Ax - $Fx)

reservedByDocument

Reserved by Recommended Practice VDA 14230-3 for future definition.

M RBD

Encoding of low nibble of ScalingByte

Encoding of

low nibble

Description of low nibble Cvt

Mnemonic

0000 - 1111

($x0 - $xF)

numberOfBytesOfParameter in current data stream referenced by a

parameter identifier

This range of values specifies the number of data bytes in a data stream

referenced by a parameter identifier. The length of a parameter is specified

by the scaling byte(s) which is always preceded by a parameter identifier

(one or multiple bytes). If multiple scaling bytes follow a parameter identifier

the length of the data referenced by the parameter identifier is the

summation of the content of the low nibbles in the scaling bytes.

E.g. VIN is identified by a single byte parameter identifier and followed by

two scaling bytes. The length is calculated up to 17 data bytes. The content

of the two low nibbles may have any combination of values which add up to

17 data bytes.

U NROBOP

usable with parameter id_fmt

1.20 LOC_ROUTINE

If further local ECU routines are to be used in addition to the application areas above, their calling

parameters must be specified explicitly in the CNF file.

Format:

LOC_ROUTINE:, <Index>, <routine number>, <rnc code>, <direct result>, <count>,

<servicePara1[, <servicePara2>, ...];

Example:

LOC_ROUTINE:, 1, 0x00, 0x23, 0x00, 2, 0x88, 0x99;

The ‘index’ parameter is used as the link to the flow control to initialize up to 5 different local ECU

routines. The ‘count’ parameter only specifies the number of remaining bytes to be read in this line (for

the read routine).

Parameter

Description

Data Type

Value Range

Index Flow control index BYTE 1 ... 5

routine number Number of the routine in the control unit BYTE/

WORD

0 ... 255/65535

rnc code Error code with which the control unit indicates

that the routine is still busy

BYTE 0 ... 255

direct result Flag indicating whether the routine reports its

result directly or whether the result has to be

fetched

BYTE 0, 1

count Number of following data bytes BYTE 0 ... 64

servicePara1 Data for local ECU routine BYTE 0 ... 255

servicePara2 Data for local ECU routine BYTE 0 ... 255

...

1.21 SECURITY_ACCESS_MODE

Security Access Mode

Format:

SECURITY_ACCESS_MODE:, <Index>, <count>, <servicePara1[, <servicePara2>, ...];

Example:

SECURITY_ACCESS_MODE:, 1, 1, 0x01;

SECURITY_ACCESS_MODE:, 2, 2, 0x99, 0x82;

Use:

If the control unit requires access authorization for flash programming, the access mode to be sent can

be specified here. This keyword is optional.

The ‘index’ parameter is used as the link to the flow control to initialize up to 5 different security access

modes. The ‘count’ parameter only specifies the number of remaining bytes to be read in this line (for

the read routine).

Parameter

Description

Data Type

Value Range

Index Flow control index BYTE 1 ... 5

count Number of following data bytes BYTE 1 ... 64

servicePara1 Data for seed request BYTE 0 ... 255

...

1.22 MAX_LENGTH

Restricting Maximum Length of Data Transfer for KWP2000 and UDS Service ‘transferData’

剩余165页未读，继续阅读

THUNDAR_CSDN

粉丝: 1
资源: 8

ETAS ProF Documentation Ver1.2.9: INCA软件与通讯协议详解

ProF Documentation.chm

自用INCA-Prof资源-chm文档

Prof-XFCE-theme:GTK3XFWM4-theme 基于 Prof-Gnome-theme

Prof-UIS.rar_Prof-U_Prof-UIS_prof _profuisd_profuisdll

Prof Advisor-crx插件

ProF Documentation.pdf

超酷界面库profuis-v2.20_freeware

Prof-UIS.rar_prof _prof uis_prof-uis2.87_profuis_uis

Prof-UIS.rar_prof uis_prof-uis2.82

超酷界面库profuis-v2.20_freeware .rar

最新资源