SAE J 3054-2015 TP1 6 Vehicle DIAGNOSTIC Protocol.pdf

《SAE J 3054-2015 TP1 6 Vehicle DIAGNOSTIC Protocol.pdf》由会员分享，可在线阅读，更多相关《SAE J 3054-2015 TP1 6 Vehicle DIAGNOSTIC Protocol.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、 SURFACE VEHICLE INFORMATION REPORT J3054 JAN2015 Issued 2015-01 TP1.6 Vehicle DIAGNOSTIC Protocol RATIONALE Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP1.6 proprietary diagnostic communication protocol is implemented. This document is needed to spe

2、cify the requirements necessary to implement the TP1.6 communication protocol in an SAE J2534 interface. TABLE OF CONTENTS 1. SCOPE 2 2. REFERENCES 2 2.1 Applicable Documents 2 3. TERMS AND ACRONYMS . 2 4. OVERVIEW . 5 5. CAN MESSAGE FORMAT 5 5.1 CAN-Telegram Overview for Channel Setup, Channel Ackn

3、owledge 5 5.2 Transport Protocol Data Unit Telegrams on an established channel . 10 6. EXAMPLES: 16 6.1 CAN-Telegram Examples . 16 6.2 Transport Protocol Examples 17 7. NOTES 22 7.1 Marginal Indicia . 22 Table 1 Tester source identifier 6 Table 2 ECU source identifier 6 Table 3 Destination target ad

4、dress range 7 Table 4 Channel setup channel IDS 7 Table 5 Channel acknowledge channel IDS 9 Table 6 Static CAN telegram parameters 9 Table 7 CAN telegram error handling 9 Table 8 General TPDU formats 11 Table 9 TPCI byte 0 . 12 Table 10 BS byte 1 . 12 Table 11 Sending priority . 12 Table 12 Static t

5、ransport protocol parameters . 14 Table 13 Transport protocol error handling 15 _ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and sui

6、tability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and sugg

7、estions. Copyright 2015 SAE International All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE

8、 A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-4970 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/J

9、3054_201501 SAE INTERNATIONAL J3054 Issued JAN2015 Page 2 of 22 1. SCOPE This Technical Information Report defines the diagnostic communication protocol TP1.6. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interfac

10、e. Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP1.6 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface.

11、 This Technical Information Report describes how a tester can be connected to a vehicle to perform diagnostics using the TP1.6 protocol. Details regarding ECU to ECU communication have been left out. 2. REFERENCES 2.1 Applicable Documents 2.1.1 SAE Publications Available from SAE International, 400

12、Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.org. SAE J2534-1 Recommended Practice for Pass-Thru Vehicle Programming OSEK Communication V1.0: Fault-Tolerant Communication 3. TERMS AND ACRONYMS 3.1 Ack Acknowledge mess

13、age 3.2 AR Acknowledge request 3.3 BS Block size 3.4 CA Connection acknowledge: Dynamic connection configuration response 3.5 CAN Telegram A CAN message with 11 address bits and up to 8 data bytes used to request, respond or establish a connection. 3.6 ChA Channel Acknowledge: Dynamic connection est

14、ablishment response 3.7 ChId Channel Identifier without offset SAE INTERNATIONAL J3054 Issued JAN2015 Page 3 of 22 3.8 ChS Channel Setup: Dynamic connection establishment request 3.9 CS Connection setup: Dynamic connection configuration request 3.10 DC Disconnect message 3.11 DDC Data direction chan

15、ge 3.12 DT Data message 3.13 ECU Electronic Control Module 3.14 EOM End of message 3.15 ID or Identifier Fixed CAN ID assigned to a module. 3.16 MNT Maximum value during communication 3.17 MNTC Maximum value with connection structure 3.18 OC OpCode 3.19 RNR Passive ECU (Receiver) not ready 3.20 RR P

16、assive ECU (Receiver) ready SAE INTERNATIONAL J3054 Issued JAN2015 Page 4 of 22 3.21 RS Receive status 3.22 SN Sequence number 3.23 TAa Target Address of Active module 3.24 TAp Target Address of Passive module 3.25 T_E Time-out for channel structure 3.26 T1, T3 Parameter ECU (CS / CA) 3.27 TP Transp

17、ort protocol 3.28 TPCI Transport protocol control information byte 3.29 TPDU Transport protocol data unit 3.30 “Active” An active module is the module that is sending data to a passive module. 3.31 “Passive” A passive module is the module that is receiving data from an active module. 3.32 “Identifie

18、r” Each message in TP1.6 has an identifier which is the 11 bit Address of the CAN message. Each module on the CAN bus has been assigned fixed Identifiers. The fixed Identifier is used to set-up a dynamic channel through which the data exchange can flow. 3.33 “Dynamic Channel” A Dynamic Channel uses

19、dynamic assigned CAN addresses which are set-up when a channel is established. The dynamic channel CAN IDs are used to send the data between nodes. SAE INTERNATIONAL J3054 Issued JAN2015 Page 5 of 22 4. OVERVIEW This document describes the transport protocol TP1.6 which is an exclusive connection be

20、tween two CAN (11 bit IDs only) participants for the transmission of large amounts of data. The CAN-transport protocol includes an agreement for the dynamic assignment of bi-directional transport channels between control modules. It is an extension of the transport protocol that was standardized in

21、the OSEK-communication V1.0. The generalization of the OSEK- connection is necessary to make dynamic assignments of identifiers to transport connections and to make a discontinuation of a running data transmission and additional timings possible. For the dynamic identifier a unique address was assig

22、ned to each control module for all vehicles and a firm question or answer address channel. By exchanging messages, the systems assign on these channels the transport channels that must then be used. The major attributes of the TP1.6 transport protocol are: Control bytes for channel structure, connec

23、tion structure, structure confirmation, connection control, data transfer and confirmation Half duplex channels Confirmation of each telegram or major block of telegrams including error correction Interruption of a running data transmission 5. CAN MESSAGE FORMAT 5.1 CAN-Telegram Overview for Channel

24、 Setup, Channel Acknowledge The first step in creating a Transport Protocol connection is to setup a channel. Two messages, the Channel Setup (ChS) message and Channel Acknowledge (ChA) message are used to setup a channel. Channel Setup and Channel Acknowledge messages have a fixed length of 3 data

25、bytes (CAN DLC = 3). The CAN-telegram for Channel Setup and Channel Acknowledge has the following structure: Identifier 1. Byte 2. Byte 3. Byte 4. Byte 5. Byte 6. Byte 7. Byte 11 bits Source Destination Opcode ChId Not used Source: Fixed Source address of the sending ECU. Destination: TAp for Channe

26、l Setup, TAa for Channel Acknowledge - target address of the recipient Opcode: Channel Set-up 0xC0 Channel Ack-Positive Reply 0xD0 Channel Ack-Negative Reply 0xD8 ChId: Channel ID, requested lower 8 bits of the CAN ID to be used for the dynamic communication channel. SAE INTERNATIONAL J3054 Issued J

27、AN2015 Page 6 of 22 5.1.1 Channel setup message structure Channel Setup messages are used to establish a data channel between 2 ECUs (or the tester and an ECU) for the purpose of sending large blocks of data. The Channel Setup message is sent from the active ECU to a passive ECU to see if it can sta

28、rt a Dynamic channel. The receiving passive ECU must send a positive or negative response to the message. The sending active ECU will wait for the response or time-out. The responding passive ECU must be able to accept the ChId sent by the requester as part of the CAN ID the responder will use to se

29、nd messages to the requester. The responding passive ECU must fill in the ChId in the Channel Acknowledge message when returning a Positive Reply. After receiving a Channel Acknowledge-Positive Reply, the sending and responding ECU use the Dynamic Channel to send and receive Transport Protocol Data

30、Unit Telegrams which will be used to send data and manage the Dynamic Channel. Each ECU, either active or passive, shall support multiple Dynamic channels simultaneously if it has the resources to do so. Each established Dynamic channel will have a unique ChId pair and will operate independently of

31、any other Dynamic channels established on the ECU. An ECU that does not have the resources to support additional Dynamic channels will reply to the Channel Setup message with Channel Acknowledge-Negative Reply. 5.1.2 Channel setup request 5.1.2.1 Source identifier Each ECU in a vehicle has been assi

32、gned a fixed Source identifier which must be used during the channel setup process. The default Channel Setup tester Source identifier for communicating with Drive ECUs is 0x200, for communicating with Comfort ECUs is 0x2D0 and for communicating with Infotainment ECUs is 0x2D0. The assigned fixed So

33、urce identifier is sometimes referred to as the “opening identifier”. Table 1 - Tester source identifier Tester Type Tester Setup offset Tester Target Address range Tester Source range Default Tester Target Address Default Tester Source Drive 0x200 0x00 0x1F 0x200 0x21F 0x00 0x200 Comfort 0x2D0 0x00

34、 0x0F 0x2D0 0x2DF 0x00 0x2D0 Infotainment 0x2D0 0x00 0x0F 0x2D0 0x2DF 0x00 0x2D0 Table 2 - ECU source identifier ECU Type ECU Setup offset ECU Target Address range ECU Identifier Range Drive 0x200 0x00 0x1F 0x200 0x21F Comfort 0x2E0 0x00 0x1F 0x2E0 0x2FF Infotainment 0x4A0 0x30 0x3F 0x4D0 0x4DF SAE

35、INTERNATIONAL J3054 Issued JAN2015 Page 7 of 22 5.1.2.2 Destination The Destination is the Target Address of the passive control unit being addressed (TAp). Target Address values are fixed for each ECU in the vehicle. The active requesters Target Address (TAa) can not equal the Destination Target Ad

36、dress (TAp). Table 3 - Destination target address range ECU Type Destination range Drive 0x00 0x1F Comfort 0x00 0x1F Infotainment 0x30 0x3F 5.1.2.3 OpCode For a Channel Setup request the OpCode is always 0xC0. 5.1.2.4 Channel ID The Channel ID is the ID of the Dynamic Channel being requested. The Ch

37、annel ID (ChId) is added to the Channel offset to yield the actual CAN ID used on the CAN network. Each ECU type has a different formula for generating the Channel ID. The Device sending the Channel Setup request uses its own Target Address plus a constant or range of constants to generate the Chann

38、el ID. The passive ECU will respond with a Channel Acknowledge message confirming the active ECUs Channel ID and specifying the passive ECUs Channel ID. Note: the Channel IDs from the active and passive devices will be added with the same offset to create the actual Dynamic CANID used to send data.

39、Table 4 - Channel setup channel IDs ECU Type ChId Formula Channel Setup (ChS) ChId offset CAN ID used if the communication channel is successfully established Drive (4 channels defined) 0x40 + Target Address, 0x60 + Target Address, 0x80 + Target Address, 0xA0 + Traget Address 0x700 0x700 + ChId Comf

40、ort Range of 0x00 0x1F 0x300 0x300 + ChId Infotainment (High priority) Range of 0xB0 0xCF 0x400 0x400 + ChId Infotainment (Low priority) Range of 0x60 0x7F 0x600 0x600 + ChId SAE INTERNATIONAL J3054 Issued JAN2015 Page 8 of 22 5.1.3 Channel acknowledge response The Channel Acknowledge message is sen

41、t in response to the Channel Setup request message. The ECU receiving the Channel Setup request will decide if it can support the Channel Setup request and respond with a positive acknowledgement if the resources are available to support the Dynamic Channel or respond with a negative acknowledgement

42、 if the resources are not available. 5.1.3.1 CAN messages criteria for receiving a channel setup request. An ECU or Tester will respond to a Channel Setup request when the CANID is in its correct range per the ECUs type and the Destination (byte 1) matches its Target Address. ECU Type Range of CANID

43、s to recieve messages Requesters Destination = Byte 1 Drive 0x200 0x21F Destination = Target Address Comfort 0x2D0 0x2DF 0x2E0 0x2FF Destination = Target Address Infotainment 0x2D0 0x2DF 0x4D0 0x4DF Destination = Target Address When the ECU sees a Channel Setup request that has a CAN ID in the corre

44、ct range and the Destination matches its Target Address then it will generate a Channel Acknowledge message. The Channel Acknowledge message uses the same CAN Telegram as the Channel Setup request described in 5.1 CAN-Telegram Overview for Channel Setup. 5.1.3.2 Source identifier The Source identifi

45、er used for the Channel Acknowledge message will be created as shown below. ECU Type Setup offset Requesters Destination Source identifier = Drive 0x200 N 0x200 + N Comfort 0x2E0 N 0x2E0 + N Infotainment 0x4A0 N 0x4A0 + N 5.1.3.3 Destination The Destination is the Target Address of the control unit

46、being addressed. The responders Destination (Target Address) is equal to the Requests Source identifier minus the offset. ECU Type Requesters Source identifer (CAN ID) Setup Offset Destination = Drive N 0x200 N - 0x200 Comfort N (in 0x2D0 0x2DF range) N (in 0x2E0 0x2FF range) 0x2D0 0x2E0 N - 0x2D0 N

47、 - 0x2E0 Infotainment N (in 0x2D0 0x2DF range) N (in 0x4D0 0x4DF range) 0x2D0 0x4A0 N - 0x2D0 N - 0x4A0 SAE INTERNATIONAL J3054 Issued JAN2015 Page 9 of 22 5.1.3.4 OpCode For a Channel Acknowledge response the OpCode can either be 0xD0 for a positive response, all resource available to open the comm

48、unication channel, or 0xD8 for a negative response, communication channel can not be opened. 5.1.3.5 Channel ID The Channel ID (ChId) is added to the Channel offset to yield the actual Channel identifier (CAN ID). Table 5 - Channel acknowledge channel IDs CAN ECU Type ChId offset ChId range Channel Setup (ChS) ChId range Channel Acknowledge (ChA) CAN ID used if the communication channel is successfully established Drive 0x700 0x40 0xBF 0x40 0xBF 0x700 + ChId Comfort 0x300 0x00 0x1F 0x20 0x3F 0x300 + ChId Infotainment (High priority) 0x400 0xE0 0xEF 0xF0 0xFF 0x400 + ChId Infotainm