SAE J 2534 2-2010 Optional Pass-Thru Features《模块选件特征》.pdf

《SAE J 2534 2-2010 Optional Pass-Thru Features《模块选件特征》.pdf》由会员分享，可在线阅读，更多相关《SAE J 2534 2-2010 Optional Pass-Thru Features《模块选件特征》.pdf（112页珍藏版）》请在麦多课文档分享上搜索。

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 2010 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: +1 724-776-4970 (outside U

4、SA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedbackon this Technical Report, please visit http:/www.sae.org/technical/standards/J2534/2_201010SURFACEVEHICLERECOMMENDEDPRACTICEJ2534-2 OCT2010 Issued 2006-03 Revised 2010-10Su

5、perseding J2534-2 MAR2006 (R) Optional Pass-Thru Features RATIONALE The specification was expanded to provide the following enhancements: - Added ability to access multiple devices simultaneously - Added support for UART Echo Byte Protocol - Added support for Honda Diag-H Protocol - Added support fo

6、r Repeat Messaging - Added support for Extended Programming Voltage - Added support for SAE J1939 Protocol - Added support for SAE J1708 Protocol - Added support for Device Parameter configuration - Added support for TP2.0 Protocol - Added support for Fault-Tolerant CAN - Added Discovery Mechanism t

7、o discover the supported features - Other editorial changes TABLE OF CONTENTS 1. SCOPE 61.1 Purpose . 61.2 Documentation Convention . 62. REFERENCES 62.1 General References 62.2 References for Single Wire CAN 62.3 References for GM UART . 72.4 References for UART Echo Byte Protocol 72.4.1 SAE Public

8、ations . 72.4.2 ISO Documents . 72.5 References for Honda DIAG-H . 72.5.1 SAE Publications . 72.5.2 ISO Documents . 72.6 References for J1939 82.6.1 SAE Publications . 82.7 References for TP 2.0 . 82.8 References for Fault-Tolerant CAN 8Copyright SAE International Provided by IHS under license with

9、SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE J2534-2 Revised OCT2010 Page 2 of 1123. DEFINITIONS . 83.1 Definitions for Analog Inputs . 83.2 Definitions for Honda DIAG-H . 83.3 Definitions for TP 2.0 . 84. ACRONYMS . 84.1 Acronyms for Single wire CAN 84.2

10、 Acronyms for GM UART . 84.3 Acronyms for Analog Inputs 94.4 Acronyms for UART Echo Byte Protocol 94.5 Acronyms for J1939 94.6 Acronyms for TP 2.0 . 94.7 Acronyms for Fault-Tolerant CAN . 95. ENABLING SAE J2534-2 FEATURES AND ACCESSING MULTIPLE SAE J2534 DEVICES 96. PIN SELECTION . 96.1 Scope of the

11、 Pin Selection optional feature 96.2 Pass-Thru system requirements . 96.2.1 Pin Usage 96.3 Win32 Application Programming Interface 106.3.1 API Functions Overview . 106.3.2 API Functions - Detailed Information 116.3.3 IOCTL Section . 126.4 Discovery Support . 147. ACCESS TO ADDITIONAL CHANNELS 147.1

12、Discovery Support . 158. MIXED FORMAT FRAMES ON A CAN NETWORK 158.1 Scope of the Mixed Format Frames on a CAN Network optional feature . 158.2 Win32 Application Programming Interface 158.2.1 API Functions Overview . 158.2.2 API Functions - Detailed InformationPassThruReadMsgs . 188.2.3 IOCTL Section

13、 . 198.3 Message Structure 208.3.1 Elements . 208.4 Discovery Support . 209. SINGLE WIRE CAN 209.1 Scope of the Single Wire CAN optional feature 209.2 Pass-Thru System Requirements . 209.2.1 Pin Usage 209.3 Win32 Application Programming Interface 209.3.1 API Functions Overview . 209.3.2 API Function

14、s - Detailed Information 229.3.3 IOCTL Section . 229.4 Message Structure 259.4.1 Elements . 259.5 Discovery Support . 2610. ANALOG INPUTS . 2610.1 Scope of the Analog Inputs Optional Feature . 2610.2 Pass-Thru System Requirements . 2610.2.1 Analog Inputs 2610.2.2 Simultaneous Communication on Multip

15、le Protocols 2610.3 Win32 Application Programming Interface 2710.3.1 API Functions Overview . 2710.3.2 API Functions - Detailed Information 27Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE J2534

16、-2 Revised OCT2010 Page 3 of 11210.3.3 IOCTL Section . 2810.4 Message Structure 3210.4.1 Examples: . 3210.4.2 Message Flag and Status Definitions . 3310.4.3 DLL Installation and Registry 3410.5 Discovery Support . 3411. GM UART (SAE J2740) 3411.1 Scope of the GM UART optional feature 3411.2 Pass-Thr

17、u System Requirements . 3411.2.1 Pin Usage 3411.3 Win32 Application Programming Interface 3511.3.1 API Functions Overview . 3511.3.2 API Functions - Detailed Information 3611.3.3 IOCTL Section . 3611.4 Message Structure 3911.4.1 Elements . 3911.4.2 Message Data Formats . 3911.5 DLL Installation and

18、Registration 3911.6 Discovery Support . 3912. UART ECHO BYTE PROTOCOL . 3912.1 Scope of the UART Echo Byte protocol optional feature 3912.2 Pass-Thru system requirements . 3912.2.1 Simultaneous communication on multiple protocols . 3912.2.2 Pin Usage 4012.3 Win32 Application Programming Interface 40

19、12.3.1 API Functions Overview . 4012.3.2 API Functions - Detailed Information 4112.3.3 IOCTL Section . 4312.4 Message Structure 4512.4.1 C / C+ Definition 4512.4.2 Message Data Formats . 4512.4.3 Format checks for messages passed to the API 4512.4.4 Message Flag and Status Definitions . 4512.5 Retur

20、n Value Error Codes . 4612.6 Discovery Support . 4613. HONDA DIAG-H PROTOCOL 4613.1 Scope of the Honda DIAG-H optional feature . 4613.2 Pass-Thru System Requirements . 4613.2.1 Simultaneous Communication on Multiple Protocols 4613.2.2 Programmable power supply 4613.2.3 Pin Usage 4613.2.4 Honda Diagn

21、ostic Connectors 4613.2.5 Serial Communication Interface / Protocol 4913.2.6 Electrical Characteristics of Interface 5013.3 Win32 Application Programming Interface 5213.3.1 API Functions Overview . 5213.3.2 API Functions - Detailed Information 5313.3.3 IOCTL Section . 5313.4 Message Structure 5313.4

22、.1 C / C+ Definition 5313.4.2 Elements . 5413.4.3 Message Data Formats . 5413.4.4 Format checks for messages passed to the API 5413.4.5 Message Flag and Status Definitions . 5413.5 Discovery Support . 54Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction o

23、r networking permitted without license from IHS-,-,-SAE J2534-2 Revised OCT2010 Page 4 of 11214. REPEAT MESSAGING . 5414.1 Scope of the Repeat Messaging protocol optional feature . 5414.2 Win32 Application Programming Interface 5414.2.1 API Functions Overview . 5414.2.2 IOCTL Section . 5514.3 Discov

24、ery Support . 5815. EXTENDED PROGRAMMING VOLTAGE SUPPORT . 5915.1 Scope of the Extended Programming Voltage Feature 5915.2 Pass-Thru System Requirements . 5915.3 Win32 Application Programming Interface 5915.3.1 API Functions Overview . 5915.3.2 API Functions - Detailed Information 5915.4 Discovery S

25、upport . 5916. J1939 PROTOCOL . 6016.1 Scope of the J1939 protocol optional feature . 6016.2 Pass-Thru system requirements . 6016.2.1 Connection to Vehicle . 6016.2.2 Communication Protocol . 6016.2.3 Simultaneous communication on multiple protocols . 6016.3 Win32 Application Programming Interface 6

26、116.3.1 API Functions Overview . 6116.3.2 API Functions - Detailed Information 6116.3.3 IOCTL Section . 6216.4 Message Structure 6416.4.1 C / C+ Definition 6416.4.2 Elements . 6416.4.3 Message Data Formats . 6516.4.4 Format Checks for Messages Passed to the API . 6516.4.5 Conventions for Returning M

27、essages from the API 6516.4.6 Message Flag and Status Definitions . 6516.5 Return Value Error Codes . 6616.6 Discovery Support . 6617. J1708 PROTOCOL . 6617.1 Scope of the J1708 protocol optional feature . 6617.2 Pass-Thru System Requirements . 6617.2.1 Connection to Vehicle . 6617.2.2 Communication

28、 Protocol . 6717.2.3 Simultaneous Communication on Multiple Protocols 6717.3 Win32 Application Programming Interface 6717.3.1 API Functions Overview . 6717.3.2 API Functions - Detailed Information 6717.4 Message Structure 6817.4.1 C / C+ Definition 6817.4.2 Elements . 6817.4.3 Message Data Formats .

29、 6817.4.4 Conventions for Returning Messages from the API 6917.4.5 Message Flag and Status Definitions . 6917.5 Discovery Support . 6918. EXTENDED PASSTHRUIOCTL FOR DEVICE CONFIGURATION PARAMETERS . 6918.1 Scope of the Extended PassThruIoctl Optional Feature . 6918.2 Pass-Thru Concept . 6918.3 Win32

30、 Application Programming Interface 7018.3.1 API Functions Overview . 7018.4 IOCTL Section . 7018.4.1 GET_DEVICE_CONFIG . 7018.4.2 SET_DEVICE_CONFIG 71Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-S

31、AE J2534-2 Revised OCT2010 Page 5 of 11218.5 Discovery Support . 7319. TP2.0 PROTOCOL . 7319.1 Scope of the TP2.0 protocol optional feature . 7319.2 Pass-Thru system requirements . 7319.2.1 Simultaneous communication on multiple protocols . 7319.2.2 Pin Usage 7319.3 Win32 Application Programming Int

32、erface 7319.3.1 API Functions Overview . 7319.3.2 API Functions - Detailed Information 7519.3.3 IOCTL Section . 7619.4 Message Structure 7919.4.1 C / C+ Definition 7919.4.2 Message Data Formats . 8019.4.3 Format Checks for Messages Passed to the API . 8019.4.4 Message Flag and Status Definitions . 8

33、019.5 Return Values . 8219.6 Discovery Support . 8220. FAULT-TOLERANT CAN 8220.1 Scope of the Fault-Tolerant CAN Optional Feature 8220.2 Pass-Thru System Requirements . 8220.2.1 Pin Usage 8220.3 Win32 Application Programming Interface 8220.3.1 API Functions Overview . 8220.3.2 API Functions - Detail

34、ed Information 8320.4 Message Structure 8320.4.1 Elements . 8320.4.2 Message Flag and Status Definitions . 8320.5 Discovery Support . 8421. DISCOVERY MECHANISM 8421.1 Scope of the Discovery Mechanism Feature 8421.2 Pass-Thru System Requirements . 8421.3 Win32 Application Programming Interface 8421.3

35、.1 API Functions Overview . 8421.3.2 API Functions - Detailed Information 8522. SAE J2534-2 RESOURCE . 10422.1 Connect Flag Values . 10422.2 ProtocolID Values . 10522.3 Filter Type Values . 10722.4 Ioctl ID Values . 10722.5 IOCTL GET / SET CONFIG Parameter Details 10822.6 GET_DEVICE_CONFIG/ SET_DEVI

36、CE_CONFIG Parameter Details . 10922.7 GET_DEVICE_INFO Defines . 10922.8 GET_PROTOCOL_INFO Defines . 11122.9 Error Return Values 11122.10 TxFlags Bits 11222.11 RxStatus Bits . 11223. NOTES 11223.1 Marginal Indicia . 112Copyright SAE International Provided by IHS under license with SAENot for ResaleNo

37、 reproduction or networking permitted without license from IHS-,-,-SAE J2534-2 Revised OCT2010 Page 6 of 1121. SCOPE SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004

38、 model year as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 specification. It is not required for an interface to be fully compliant with SAE J2534-1 specification to implement some of the features specified in thi

39、s document. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1. 1.1 Pur

40、pose Each section included in this document specifies features that extend the SAE J2534-1 specification. The specific feature operation will be described directly or reference another existing specification. In each case the required calling structure,via the SAE J2534-1 API, will be documented and

41、 coordinated by this document. Extending the protocols supported by SAE J2534-1 this document adds two new types of ProtocolIDs. 1. ProtocolIDs with the suffix _PS for connecting to a vehicle, via the SAE J1962 connector using the technique outlined in the section titled Pin Selection. 2. Generic Pr

42、otocolIDs, with the suffixes _CH1 through _CH128 for protocols that terminate at a vendor specific connector on the device. See the section titled Access to Additional Channels. 1.2 Documentation Convention For each protocol defined in this document: Unless explicitly specified otherwise, all SAE J2

43、534-1 PassThru function calls will be supported. SAE J2534-1 ConnectFlags, RxStatus, TxFlags and Indications are not supported unless explicitly specified. 2. REFERENCES 2.1 General References Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (ins

44、ide USA and Canada) or 724-776-4970 (outside USA), www.sae.org.SAE J2534-1 Recommended Practice for Pass-Thru Vehicle Programming SAE J1962 Diagnostic Connector 2.2 References for Single Wire CAN The current published manufacturer specific documents for Single Wire CAN may be acquired from the follo

45、wing URL: http:/ GMLAN Single Wire CAN Physical and Data Link Layers Specification Definitions GMW3173 Architecture & Bus Wiring Requirements GMW3110 GMLAN Enhanced Diagnostics Test Mode Specifications Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or

46、 networking permitted without license from IHS-,-,-SAE J2534-2 Revised OCT2010 Page 7 of 1122.3 References for GM UART The current published manufacturer specific definition of GM UART may be acquired from SAE as an SAE Information Report from SAE International, 400 Commonwealth Drive, Warrendale, P

47、A 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.org.SAE J2740 General Motors UART Serial Data Communications 2.4 References for UART Echo Byte Protocol 2.4.1 SAE Publications Implementation of the optional feature requires reference to the following doc

48、uments which are available from SAE International, 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 J2809 Honda Diagnostic Serial Data Link Protocol - ABS / VSA System SAE J2818 Keyword Protocol 1281 2.4.2 ISO Documents Available from American National Standards Institute, 25 West 43rdStreet, New York, NY 10036-8002, Tel: 212-642-4900, www.ansi.org.ISO 9141:1989 Road Vehicles - Diagnostic Systems - Requirem