SAE J 2819-2008 TP2 0 Vehicle Diagnostic Protocol《TP2 0汽车诊断协议》.pdf

1、_ 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 suitability for any particular use, including any patent infringement arising there

2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions. Copyright 2008 SAE International All rights reserved. No part of this publication m

3、ay 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 A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: 724-776-4970 (outside USA)

4、 Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org J2819 FEB2008 SURFACE VEHICLE INFORMATION REPORT Issued 2008-02 TP2.0 Vehicle Diagnostic Protocol RATIONALE Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP2.0 proprieta

5、ry diagnostic communication protocol is implemented. This document is needed to specify the requirements necessary to implement the TP2.0 communication protocol in an SAE J2534 interface. TABLE OF CONTENTS 1. SCOPE 3 2. REFERENCES 3 2.1 Applicable Publications . 3 2.1.1 SAE Publications. 3 3. TERMS

6、AND ACRONYMS . 3 4. OVERVIEW. 4 5. CAN MESSAGE FORMAT . 5 5.1 CAN-Telegram Overview 5 5.1.1 Non-Broadcast Request Messages 5 5.1.2 Broadcast Messages 6 5.1.3 Dynamic Channel Structure Messages 7 5.1.4 Static CAN-Telegram parameters. 8 5.1.5 CAN-Telegram Error handling 9 5.1.6 CAN-Telegram Establishi

7、ng a Channel and Connection9 5.2 Transport Protocol Data Unit Telegrams on an Established Channel 10 5.2.1 Control Bytes. 11 5.2.2 Dynamic Transport Protocol Timing Parameters 12 5.2.3 Static Transport Protocol Parameters. 13 5.2.4 Transport Protocol Error Handling 13 6. EXAMPLES. 14 6.1 CAN-Telegra

8、m Examples . 14 6.1.1 Broadcast without re-trigger 14 6.1.2 Broadcast with re-trigger. 14 6.1.3 Channel Set-up with Ack. 15 6.1.4 Channel Set-up missing Ack. 15 6.1.5 Channel Set-up with Ack missing Transport Protocol Connection Set-up . 16 6.2 Transport Protocol Examples 16 6.2.1 Connection Set-up

9、with Ack 16 6.2.2 Connection Set-up missing Ack 17 SAE J2819 Issued FEB2008 - 2 - 6.2.3 Sending Data with Acknowledge request - ready response. 17 6.2.4 Sending Data with Acknowledge request not ready . 18 6.2.5 Sending Data with Acknowledge request with no Ack 18 6.2.6 Sending Data with Acknowledge

10、 request, Receiver not ready and retransmit block previous block. 19 6.2.7 Break in between Data telegrams without Ack request 19 6.2.8 Break in between Data telegrams with Ack request . 20 6.2.9 Connection Test telegram with Connection Ack. 20 6.2.10 Connection Test telegram missing Connection Ack

11、. 21 6.2.11 Disconnect telegram . 21 7. NOTES 22 7.1 Marginal Indicia. 22 SAE J2819 Issued FEB2008 - 3 - 1. SCOPE This Technical Information Report defines the diagnostic communication protocol TP2.0. This document should be used in conjunction with SAE J2534-2 in order to fully implement the commun

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

13、ation protocol in an SAE J2534 interface. 2. REFERENCES 2.1 Applicable Publications The following publications form a part of this specification to the extent specified herein. Unless otherwise specified, the latest issue of SAE publications shall apply. 2.1.1 SAE Publications Available from SAE Int

14、ernational, 400 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 Recommended Practice for Pass-Thru Vehicle Programming SAE J2534-1 Recommended Practice for Pass-Thru Vehicle Programming 3. TERMS AND ACRONY

15、MS Ack Acknowledge message AR Acknowledge request BR Break message BS Block size CA Connection acknowledge message CAN Telegram A CAN message with 11 address bits and up to 8 data bytes used to request, respond or establish a connection. CS Connection set-up message CT Connection test message DC Dis

16、connect message DT Data message ECU Electronic Control Module EOM End of message ID or Identifier Fixed CAN ID assigned to a module. Range 0x200 through 0x2EF MNCT Maximum value during connection test MNT Maximum value during communication MNTB Maximum value at Block repeat count MNTC Maximum value

17、with connection structure RBR Break RC_CT Repeat counter connection test RC_E Repeat counter opening RC_S Repeat counter sending machine RNR Receiver not ready RR Receiver ready RS Receiver state SID Service identifier SN Block counter T_CT Timer for connection test T_E Time-out for channel structur

18、e T_WAIT Delay timer for RNR SAE J2819 Issued FEB2008 - 4 - T1, T3 Parameter ECU (CS / CA) TP Transport protocol TPCI Transport protocol control information byte TPDU Transport protocol data unit “Re-triggered”: Service requests that are Re-triggered are Broadcast Messages service requests that are

19、sent continuously at an interval of T_BRT_INT until stopped by the user (application). “Active”: An active module is the module that is sending data to a passive module. “Passive”: A passive module is the module that is receiving data from an active module. “Identifier”: Each message in TP2.0 has an

20、 identifier which is the 11 bit Address of the CAN message. Each module on the CAN bus has been assigned fixed Identifier in the range of 0x200 through 0x2EF. Dynamic channels use dynamic assigned CAN addresses. 4. OVERVIEW This document describes the transport protocol and the broadcast services. T

21、he TP2.0 is an exclusive connection between two CAN (11 bit IDs only) participants for the transmission of large amounts of data. The broadcast services are used for the 1:n communication in the vehicle. The CAN-transport protocol includes an agreement for the dynamic assignment of bi- directional t

22、ransport channels between control modules. It is an extension of the transport protocol that was standardized in 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

23、 running data transmission and additional timings possible. For the dynamic identifier a unique address was assigned 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 th

24、en be used. The major attributes of these transport protocols are: Control bytes for channel structure, connection structure, structure confirmation, connection control, data transfer and confirmation, Pure bi-directional channels, Confirmation of each telegram or major block of telegrams including

25、error correction, Interruption of a running data transmission SAE J2819 Issued FEB2008 - 5 - 5. CAN MESSAGE FORMAT 5.1 CAN-Telegram Overview Each ECU in a vehicle has been assigned a TP-target address. The TP-target address range is from 0x00 to 0xEF. The Broadcast Addresses are TP-target addresses

26、in the range of 0xF0 through 0xFF. Each CAN-telegram has the following basic structure: Identifier 1. Byte 2. Byte 3. Byte 4. Byte 5. Byte 6. Byte 7. Byte 11 bits Destination Opcode Parameter Identifier: Fixed address of the sending (active) ECU. Range between 0x200 through 0x2EF. Destination: TP-ta

27、rget address of the recipient (lower 8 bits of the ECUs assigned Identifier) Opcode: Broadcast message Request 0x23 Response 0x24 Dynamic channel structure message Channel Set-up 0xC0 Channel Ack-Positive Reply 0xD0 Channel Ack-Negative Reply 0xD6: Application type not supported Channel Ack-Negative

28、 Reply 0xD7 : Application type temporarily not supported Channel Ack-Negative Reply 0xD8: Temporarily no resources are free Parameter: The Parameter data area is assigned according to the opcode. 5.1.1 Non-Broadcast Request Messages Non-Broadcast Request messages are defined as messages with a Desti

29、nation Byte less than 0xFx. Identifier 1. Byte 2. Byte 3. Byte 4. Byte 5. Byte 6. Byte 7. Byte 10 -0 7-0 7-0 7-0 7-0 7-0 7-0 7-0 11 bits Destination 4 x T3 SAE J2819 Issued FEB2008 - 13 - 5.2.3 Static Transport Protocol Parameters For all transport protocol connections the following parameters are s

30、tatically established: TABLE 7 - STATIC TRANSPORT PROTOCOL PARAMETERS Description Parameter Name Value Connection Test Active ECU Connection Test timeout (runs concurrent with other actions) T_CTa 1000 ms Passive ECU Connection Test timeout (time-out waiting for the Connection Test telegram) T_CTp 1

31、050 ms Maximum Repeats of the connection test telegram MNCT 5 Request / Response Maximum number acceptances of telegram not ready requests within a block size MNTB 5 Maximum repeats of acknowledge requests MNT 2 Acknowledge with Receiver not ready Delay timer used to delay next telegram if Receiver

32、Not Ready bit set in Ack Telegram T_Wait 100 ms Repetition Count of n means that the applicable telegram was sent n+1 in total. 5.2.4 Transport Protocol Error Handling TABLE 8 - TRANSPORT PROTOCOL ERROR HANDLING Condition Action Passive ECU receives a Data telegram with an unexpected SN Send Ack wit

33、h the SN that is expected. Active ECU receives Ack with request for previous SN telegram Send the asked for Data Telegram up to MNTB times then error by closing the channel (send Disconnect telegram). Active ECU time-out on T1 when expecting a Ack response Repeat the last Data Telegram for up to MNT

34、C times then error by closing the channel (send Disconnect telegram) Passive ECU T_CTp timeout waiting for Connection Test telegram Count each successive occurrence, when MNCT is exceeded, close the channel (send Disconnect telegram) SAE J2819 Issued FEB2008 - 14 - 6. EXAMPLES 6.1 CAN-Telegram Examp

35、les 6.1.1 Broadcast without re-trigger 6.1.2 Broadcast with re-trigger Module 1 (active)Module 2 (passive) T_BR_INT Broadcast msg Key = 0x5555T_BR_INT Broadcast msg Key=0xAAAAT_BR_INT Broadcast msg Key = 0x5555T_BR_INT Broadcast msg Key=0xAAAABroadcast msg Key = 0x5555T_BRT_INT Broadcast msg Key=0xA

36、AAAT_BRT_INT Broadcast msg Key = 0x5555T_BR_INT Broadcast msg Key = 0x5555T_BR_INT Broadcast msg Key=0xAAAAT_BR_INT Broadcast msg Key = 0x5555T_BR_INT Broadcast msg Key=0xAAAABroadcast msg Key = 0x5555Module 1 (active) Module 2 (passive) SAE J2819 Issued FEB2008 - 15 - 6.1.3 Channel Set-up with Ack

37、6.1.4 Channel Set-up missing Ack Module 1 (active)Module 2 (passive) Start timer T_E Channel Set-up msgChannel Ack msgStart timer T_E Connection Set-up msgModule 1 (active)Module 2 (passive) Start timer T_E Channel Set-up msgStart timer T_E Channel Set-up msgStart timer T_E Channel Set-up msgOn time

38、 out add 1 to retry count. If count less than MNTC then send again else fail SAE J2819 Issued FEB2008 - 16 - 6.1.5 Channel Set-up with Ack missing Transport Protocol Connection Set-up 6.2 Transport Protocol Examples 6.2.1 Connection Set-up with Ack Module 1 (active) Module 2 (passive) Start timer T_

39、E Channel Set-up msgChannel Ack msgStart timer T_E Channel Ack msgStart timer T_E On time out add 1 to retry count. If count is less than MNTC then send Ack again else fail Module 1 Module 2 (passive) Start timer T_E Connection Set-up telegram Connection Ack telegramStart timer T_CTp Data telegram S

40、N=1 (No Ack) Start timer T_CTa Data telegram SN=2 (No Ack)Timer T3 SAE J2819 Issued FEB2008 - 17 - 6.2.2 Connection Set-up missing Ack 6.2.3 Sending Data with Acknowledge request - ready response NOTE: The Connection Test timers T_CTa and T_CTp are running through all of the following diagrams. It i

41、s not shown in order to simplify the diagrams. Module 1 (active)Module 2 (passive) Start timer T_E Connection Set-up telegram Start timer T_E Connection Set-up telegram Start timer T_E Connection Set-up telegram On time out add 1 to retry count. If count less than MNT then send again else fail Modul

42、e 1 (active)Module 2 (passive) Data telegram SN=x (No Ack) Ack telegram SN=x+2 (Ready)Start timer T1 Data telegram SN = x+1 (Ack Req) Data telegram SN=x+2 (No Ack)Timer T3 Timer T3 Timer T3 SAE J2819 Issued FEB2008 - 18 - 6.2.4 Sending Data with Acknowledge request not ready 6.2.5 Sending Data with

43、Acknowledge request with no Ack Module 1 (active)Module 2 (passive) Data telegram SN=x (No Ack) Ack telegram SN=x+2 (Not Ready)Start timer T1 Data telegram SN = x+1 (Ack Req) Data telegram SN=x+2 (No Ack) Timer T3 Timer T3 Timer T_Wait Timer T3 Module 2 (passive) Module 1 (active)Data telegram SN=x

44、(No Ack) Start timer T1 Data telegram SN = x+1 (Ack Req) Timer T3 Timer T3 Data telegram SN = x+1 (Ack Req) Start timer T1 On time out add 1 to retry count. If count less than MNT then send again else fail SAE J2819 Issued FEB2008 - 19 - 6.2.6 Sending Data with Acknowledge request, Receiver not read

45、y and retransmit block previous block The “Not Ready” Ack cause the Insertion of the T_Wait delay. 6.2.7 Break in between Data telegrams without Ack request Module 1 (active)Module 2 (passive) Data telegram SN=x (No Ack) Ack telegram SN=x (Not Ready)Start timer T1 Data telegram SN = x+1 (Ack Req) Da

46、ta telegram SN=x (No Ack)Timer T3 Timer T3 Timer T_Wait Timer T3 Note: next Data telegram and subsequent telegrams are a retransmit of telegrams starting at SN = x. Module 1 (active)Module 2 (passive) Data telegram SN=x (No Ack) Break telegramStart timer T1 Data telegram SN = x+1 (Ack Req, EOM) Time

47、r T3Ack telegram SN = x+2 (Ready)SAE J2819 Issued FEB2008 - 20 - 6.2.8 Break in between Data telegrams with Ack request 6.2.9 Connection Test telegram with Connection Ack Module 1 (active)Module 2 (passive) Data telegram SN=x (No Ack) Ack telegram SN=x+2 (Ready)Start timer T1 Data telegram SN = x+1

48、(Ack Req) Data telegram SN=x+2 (Ack Req, EOM) Timer T3Timer T3Timer T3Break telegramStart timer T1 Ack telegram SN=x+3 (Ready)Timer T3 in Control Module Module 1 (active)Module 2 (passive) Start timer T_E Connection Set-up telegram Connection Ack telegramStart timer T_CTp Data telegram SN=1 (No Ack)

49、 Start timer T_CTa Data telegram SN=2 (Ack Req, EOM) Timer T3 Ack telegram SN=3Start timer T1 Connection Ack telegramConnection Test telegramRestart timer T_CTp Restart timer T_CTa Restart timer T_CTa SAE J2819 Issued FEB2008 - 21 - 6.2.10 Connection Test telegram missing Connection Ack 6.2.11 Disconnect telegram Module 1 (active)Module 2 (passive) Data telegram SN=x (No Ack) Ack telegram SN=x+2 (Ready)Start timer T1 Data telegram