OBD2协议规范SAEJ1979

所需积分/C币:49 2015-05-21 15:45:28 799KB PDF

This document supersedes SAE J1979 SEP1997, and is technically equivalent to ISO/DIS 15031-5:April 30, 2002, except for minor reorganisation of Paragraphs 1 and 2. Foreword—On-Board Diagnostic (OBD) regulations require passenger cars, and light and medium duty trucks, to support communication of a m
SAE J1979 Revised APr2002 Service $04 -Clear/Reset Emission-Related Diagnostic Information 37 5.4.1 Functional description 37 54.2 Message data bytes …37 54.3 Parameter Definition 37 5.4.4 Message Example 5.5 Service $05-Request Oxygen Sensor Monitoring Test Results 39 5.5.1 Functional Description 39 55.2 Message Data Bytes 9 5.5.3 Parameter Definition 40 5.54 Message Example………… 41 5.6 Service $06-Request On-Board Monitoring Test Results for Specific Monitored Systems 43 56.1 Functional description 5.6.2 Message data Bytes 43 56.3 Parameter Definition 44 5.6.4 Message EXample Service $O7-Request Emission-Related Diagnostic Trouble Codes detected 45 During Current or Last Completed Driving Cycle .47 5.7.1 Functional Description 47 5.7.2 Message Data Bytes…………,.,….,..,.,...,... 47 573 Parameter Definitⅰo∩. 48 5.74 Message Example 5.8 Service $08-Request Control of On-Board System, Test or Component 48 5.8.1 Functional Description lanai 48 58.2 Message Data Bytes… 48 5.8.3 Parameter definition 50 58.4 Message Example 50 5.9 Service $O9-Request Vehicle Information 5.9.1 Functional description 59.2 Message data Bytes 555 593 Parameter Definition 52 5.94 Message Example ......8I 53 Diagnostic Service Definition for ISo 15765-4 63 Service $01-Request Current Powertrain Diagnostic Data 63 6.1.1 Functional Description 63 6.12 Message Data Bytes………,……. .63 6.13 Parameter Definⅰtion 65 6.1.4 Message Example .65 6.2 Service $02-Request Powertrain Freeze Frame Data 69 6.2.1 Functional Description 69 6.2.2 Message Data Bytes …69 6.2.3 Parameter definition 6.2.4 Message Example∴ 71 6.3 Service S03-Request Emission-Related Diagnostic Trouble Codes.................74 6.3.1 Functional Description 74 6.3.2 Message Data Bytes.… 画1 6.3.3 Parameter definition .75 6.3.4 Message Example 75 6.4 Service$04- Clear/ Reset emission- Related Diagnostic Information…………… ..76 6.4.1 Functional Description .76 64.2 Message Data Bytes 64.3 Parameter Definition 77 644 Message Example 77 6.5 Service $05 -Request Oxygen Sensor Monitoring Test Results 78 SAE J1979 Revised APr2002 6.6 Service $06-Request On-Board Monitoring Test Results for Specific Monitored Systems 78 6.6.1 Functional description 78 6.6.2 Message data bytes ........ …78 6.6.3 Parameter Definition .80 6.6.4 Message Example 83 Service $07-Request Emission-Related Diagnostic Trouble Codes detected During Current or Last Completed Driving Cycle 85 6.7.1 Functional Description 85 6.7.2 Message Data Bytes ..86 6.73 Parameter definⅰtion 86 6.74 Message Example 86 6.8 Service $08 -Request Control of On-Board System, Test or Component 6.8.1 Functional Description anii aI 86 6.8.2 Message Data Bytes 87 6.8.3 Parameter Definition 88 6.8.4 Message EXample 88 6.9 Service $09 -Request Vehicle Information 90 6.9.1 Functional Description 90 692 Message Data Bytes….…,…,…,…,…,,…., 90 6.9.3 Parameter Definition :: 92 6.9.4 Message Example 92 Notes 98 7.1 Marginal Indicia 98 Appendix a(normative)PID(Parameter ID)OBDMID(On-Board Monitor ID)/ TD( Test D川/ NFOTYPE supported definition..… 99 Appendix B(normative)PIDs(Parameter ID)for Service $01 and $02 Scaling and Definition 100 Appendix C( normative)TDs( Test ID) for service$05 Scaling and definition…………… 122 Appendix d(normative) oBDMIDs(On-Board Diagnostic Monitor ID)Definition for Service $06 123 Appendix E(normative) Unit and Scaling id definition for service $06 127 Unsigned Unit and Scaling Identifiers Definition……… 127 E.2 Signed Unit and Scaling Identifiers Definition 144 Appendix F(normative) TIDs(Test ID)for Service $08 Scaling and Definition .152 Appendix G(normative)INFOTYPEs for Service $09 Scaling and Definition 153 1. Scope 1.1 Purpose-This document supersedes sAE J1979 SEP1997, and is technically equivalent to ISO/DIS 15031 5: April30,2002. This SAE Recommended Practice is intended to satisfy the data reporting requirements of On-Board Diagnostic(OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future. This document specifies a. Message formats for request and response messages b. Timing requirements between request messages from external test equipment and response messages from vehicles, and between those messages and subsequent request messages Behavior of both the vehicle and external test equipment if data is not available d. A set of diagnostic services, with corresponding content of request and response messages, to satisfy OBD regulations, SAE J1979 Revised APr2002 This document includes capabilities required to satisfy obd requirements for multiple regions, model years engine types, and vehicle types. Those regulations are not yet final for some regions, and are expected to change in the future. This document makes no attempt to interpret the regulations and does not include applicability of the included diagnostic services and data parameters for various vehicle applications. the user of this document is responsible to verify the applicability of each section of this document for a specific vehicle, engine, model year and region This document is based on the Open Systems Interconnection(OSI)Basic Reference Model in accordance with ISo/EC 7498 and Iso/Ec 107 31 which structures communication systems into seven layers as shown in the table below TABLE 1-APPLICABILITY AND RELATIONSHIP BETWEEN DOCUMENTS Applicability OSI 7 layer Emissions-related Applicability oSl 7 layer Emissions-related diagnostics diagnostics Physical(layer 1) SO9141-2 S14230-1 SAE J1850 So11898 lSo157654 Seven layer Data link(layer 2) so9141-2 so14230-2 SAE J1850 SO11898, according to 1so15765-4 ISO/EC 7498 Network(layer 3) lsO15765-2 and lSO15765-4 SO/EC10731 Transport(layer 4) Session(layer 5) 1SO15765-4 Presentation layer 6 Application (layer 7) SAE J1979/ SAE J1979/ SAE J1979/ SAE J1979/ S15031-5 SO15031-5 sO15031-5 SO15031-5 1.2 Differences from iso document- there are no technical differences between this document and iso/DIs 15031-5:Apri30,2002 NOTE- Both this document and the iso 15031-5 document are intended to satisfy the requirements of OBd requirements in the United States and Europe, and any other region that may adopt simila requirements in the future. Those regulations change with time, and often when a requirement is introduced in one region it will later also become a requirement in another region The iso task force responsible for Iso 15031-5 and the Sae task force work closely together to maintain consistency in diagnostic reporting requirements in these two documents, and to ensure usability of these documents for all regions. The goal is to maintain identical technical content in the two documents, but this document may need to change if additional capabilities are required for the U.s before the iso document can be modified to include those changes SAE J1979 Revised APr2002 2 References 2.1 Applicable Publications-The following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest version of SAE publications shall apply 2.1.1 SAE PUBLICATIONS-Available from SAE, 400 Commonwealth Drive, Warrendale, Pa15096-0001 SAE J1850: MAY2001-Class b Data Communications network Interface SAE J1930-ElectricalElectronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms Equivalent to ISO/TR 15031-2: April 30, 2002 SAE J1978--OBD lI Scan Tool - Equivalent to ISO/DIS 15031-4: December 14, 2001 SAE J2012-Diagnostic Trouble Code Definitions-Equivalent to ISO/DIS 15031-6: April 30, 2002 2.1.2 SO DOCUMENTS-Available from ansl 25 West 43rd street. New york, ny 10036-8002 Iso 9141-2:1994-Road vehicles- Diagnostic systems- Part 2: CARB requirements for interchange o digital information ISO 9141-2: 1994/ Amd 1: 1996-Road vehicles- Diagnostic systems-Part 2: CARB requirements for nterchange of digital information amendment 1 ISO 14230-4: 2000-Road vehicles- Keyword protocol 2000 for diagnostic systems-Part 4: Requirements for emissions-related systems ISO/DIS 15031-5: April 30, 2002--Road vehicles communication between vehicle and external test equipment for emissions-related diagnostics-Part 5: Emissions related diagnostic services ISo 15765-2-Road vehicles- Diagnostics on Controller Area Network(CAN)-Part 2: Network layer services Iso 15765-4-Road vehicles- Diagnostics on Controller Area Network(CAN)-Part 4: Requirements for emissions-related systems 2.2 Related Publications-The following publications are provided for information purposes only and are not a required part of this specification 2.2.1 SAE PUBLICATION-Available from SAe, 400 Common wealth drive Warrendale. Pa 15096-0001 SAE J1962-Diagnostic Connector-Equivalent to ISO/DIS 15031-3: December 14, 2001 2.2.2 ISO DOCUMENT Available from ansl. 25 West 43rd street, New york ny 10036-8002 so 15031-1: 2001-Road vehicles- Communication between vehicle and external test equipment for emissions-related diagnostics-Part 1: General information 3. Term(s)and Definition(s) 3.1 Absolute Throttle Position Sensor--This value is intended to represent the throttle opening NOTE- For systems where the output is proportional to the input voltage, this value is the percent of maximum input signal. For systems where the output is inversely proportional to the input voltage, this value is 100% minus the percent of maximum input signal. Throttle position at idle will usual indicate greater than 0%, and throttle position at wide open throttle will usually indicate less than 100% SAE J1979 Revised APr2002 3.2 Bank-Specific group of cylinders sharing a common control sensor, bank 1 always contains cylinder number 1, bank 2 is the opposite bank NotE- If there is only one bank, use bank #1 DTCs and the word bank may be omitted. With a single"bank system utilising multiple sensors, use bank #1 DTCs identifying the sensors as #1, #2, #3 in order as they move further away from the cylinder(s) 3.3 Base Fuel Schedule-The fuel calibration schedule programmed into the Powertrain Control Module or PROM When manufactured or when updated by some off-board source, prior to any learned on-board correction 3.4 Load-Typically Calculated Load Value for spark ignition engines, an indication of the current airflow divided by peak airflow, where peak airflow is corrected for altitude, if available NOTE- Peak airflow is typically represented as the maximum theoretical airflow possible(a single number) or is calculated as a function of engine RPM. Either method is acceptable. Mass airflow and barometric pressure sensors are not required for this calculation this definition provides a unit -less number, and provides the service technician with an indication of the percent engine capacity that is being used For diesel applications, the calculated load value shall be determined by the ratio of current measured or calculated output torque to maximum output torque at current engine speed 3.5 Client-The function that is part of the tester and that makes use of the diagnostic services. a tester normally makes use of other functions such as data base management, specific interpretation, man-machine interface 3.6 Continuous Monitoring-Sampling at a rate no less than two samples per second 3.7 Convention(Cvt)-The convention column is integrated in each message table and marks each parameter included NOTE- The following conventions are used: C Conditional: the parameter marked"C in a request/ response message is present only under a condition specified in the bottom row of the message table. M=Mandatory: the parameter marked"M"in a request/response message table shall always be present. U= User optional: the parameter marked"U"in a request/response message table shall or shall not be supplied, depending on dynamic usage by the manufacturer. The convention recommends a mnemonic, which might be used for implementation. In no case is the specified mnemonic a mandatory requirement for any implementation 3.8 ECM-Engine control Module 3. 9 ECU-Electronic Control Unit is a generic term for any electronic control unit 3.10 FT-Fuel Trim, feedback adjustments to the base fuel schedule NoTE Short-term fuel trim refers to dynamic or instantaneous adjustments. Long-term fuel trim refers to much more gradual adjustments to the fuel calibration schedule than short-term trim adjustments These long-term adjustments compensate for vehicle differences and gradual changes that occur over time SAE J1979 Revised APr2002 3.11 Negative Numbers signed binary-the most significant bit(MSB)of the binary number is used to indicate positive(0)/ negative(1) 2s complement -negative numbers are represented by complementing the binary number and then adding 1 EXAMPLE-0.99=8001hex=1000000000000001 binary 0=0000hex=0000000000000000 binary +0.99=7 Fff hex=0111111111111111 Inary NOTE 0.99)+(+0.99)=0 3.12 Number--Is expressed by this symbol# 3.13 P2, P3 Timing Parameter-Both parameters are application timing parameters for the ECu(s)and the external test equipment 3.14 PCM-Powertrain Control module 3.15 Server-A function that is part of an electronic control unit and that provides the diagnostic services otE- This document differentiates between the Server (i.e, the function) and the electronic control unit so that this document remains independent from the implementation 3.16 Service-An information exchange initiated by a client (external test equipment)in order to require diagnostic information from a server(ECU)orland to modify its behaviour for diagnostic purpose NOTE- This is also the equivalent of test mode or mode. 3.17 sI-Abbreviation for International System of Units 3.18 TCM-Transmission Control module 4. Technical Requirements 4.1 Diagnostic Service, General Requirements-The requirements specified in this section are necessary to ensure proper operation of both the external test equipment and the vehicle during diagnostic procedures External test equipment, when using messages specified, shall not affect normal operation of the emission control system 4.1.1 MULTIPLE RESPONSES TO A SINGLE DATA REQUEST-The request messages are functional messages, which means the external test equipment will request data without knowledge of which ECU(s)on the vehicle will respond In some vehicles, multiple ecus may respond with the information requested any external test equipment requesting information shall, therefore, have provisions for receiving multiple responses 4.1.2 APPLICATION TIMING PARAMETER DEF INIT ION-The definition of p2 and p3 is included in this section a subscript is added to each timing parameter to identify the protocol P2, P3 for Iso 9141-2 and ISo 14230-4 protocols -P2 M1850: P2 for SAE j1850 protocol P2CAN: P2 for ISo 15765-4 protocol -8 SAE J1979 Revised APr2002 4. 1.2. 1 Definition for iso9141-2For ISo 9141-2 interfaces, Data Link Layer response time requirements are specified in ISo 9141-2 The table below specifies the application timing parameter values for P2 and P3 TABLE 2-DEFINITION OF ISO 9141-2 APPLICATION TIMING PARAMETER VALUES Minimum Maximum Parameter value(ms) value(ms) Description P2K-Line 25 Time between external test equipment request message and the successful transmission of Key Bytes the ECu(s)response message(s). Each OBD ECU shall start sending its response message $08$08 within P2K-Line after the request message has been correctly received. Subsequent response One or more messages shall also be transmitted within P2K -Line of the previous response message for ECU(s) multiple message responses P2 K-Line Time between external test equipment request message and the successful transmission of Key Bytes the ECU response message(s). The OBD ECU shall start sending its response message $94$94 ithin P2K-Line after the request message has been correctly received. Subsequent response Only one messages shall also be transmitted within P2K- Line of the previous response message for ECU multiple message responses K-Line 5000 Time between the end of an ECU(s)successful transmission of response message (s)and start of new external test equipment request message. The external test equipment may send a new request message if all response messages related to the previously sent request message have been received and if P3K -Line minimum time expired 4. 1.2. 2 Definition for /So 14230-4--For ISo 14230-4 interfaces, Data Link Layer response time requirements are specified in ISo 14230-4 The table below specifies the application timing parameter values for P2 and P3 TABLE 3-DEFINITION OF SO 14230-4 APPLICATION TIMING PARAMETER VALUES Minimum Maximum Parameter value(ms) value(ms) Description K-Line 25 Time between external test equipment request message and the successful transmission of the ECu(s)response message (s). Each OBD ECU shall start sending its response message within P2 K-Line after the request message has been correctly received. Subsequent response messages shall also be transmitted within P2 K-Line of the previous response message fo multiple message responses. K-Line 5000 Time between the end of an ecu(s)successful transmission of response message(s)and start of new external test equipment request message. The external test equipment may send a new request message if all response messages related to the previously sent request message have been received and if P3K-Line minimum time expired -9 SAE J1979 Revised APr2002 4.1.2.3 Definition for SAE J1850-For SAE J1850 network interfaces, the on-board systems shall respond to a request within P2J1850 of a request or a previous response message. With multiple response messages possible from a single request message, this allows as much time as is necessary for all ECUs to access the data link and transmit their response message(s). If there is no response message within this time period, the external test equipment can either assume no response message will be received, or if a response message has already been received, that no more response messages will be received. The application timing parameter value P2 J1850 is specified in the table below TABLE 4-DEFINITION OF SAE J1850 APPLICATION TIMING PARAMETER VALUES Maximum Parameter value(m value(ms) Description 21850 100 Time between external test equipment request message and the successful transmission of the ECU(s)response message(s). Each OBD ECU shall attempt to send its response e (or at least the first of multiple response messages)within P2J1850 after the request message has been correctly received. Subsequent response messages shall also be transmitted within P2J1850 of the previous response message for multiple message responses 4.1.2. 4 Definition for /so 15765-4For can bus systems based on iso 15765-4, the(all)responding ECU(s)of the on-board system shall respond to a request message within P2CAN. The table below specifies the application timing parameter values for P2 TABLE 5-DEFINITION OF ISO 15765-4 APPLICATION TIMING PARAMETER VALUES Minimum Maximum Parameter value(ms) value(ms) Description P2cAN 50 Time between external test equipment request message and the receipt of all unsegmented response messages and all first frames of segmented response message(s). Each OBD ECU shall start sending its response message within P2cAN after the request message has been correctly received. P2 CAN 5000 $78 and the next response message (positive or negative message ge Time between the successful reception of a negative response message with response code 4.1.3 MINIMUM TIME BETWEEN REQUESTS FROM EXTERNAL TEST EQUIP MENT 4.1.3.1 So9141-2, 1so 14230-4-Minimum Time Between Requests from External Test EquipmentFor Iso 9141-2(K-Line)interfaces, the required times between request messages are specified in the iso 9141-2 For Iso 14230-4(K-Line)interfaces, the required times between request messages are specified in the sO14230-4 The figure below shows an example of a request message followed by four (4)response messages and another request message -10-

...展开详情

评论 下载该资源后可以进行评论 2

chenchongyong 基本都差不多
2017-10-10
回复
pinksword 还行吧,找了好多,基本都差不多
2015-12-03
回复
img
heshanxingzhe

关注 私信 TA的资源

上传资源赚积分,得勋章
    最新推荐