ISO14229-1.pdf汽车诊断应用层协议 ISO14229-2013 ISO (the Int

文件名称: ISO14229-1.pdf

所属分类: 嵌入式

开发工具:

文件大小: 4mb

下载次数: 0

上传时间: 2019-09-02

提供者: dh1029******

下载 (4mb)

不能下载？报告错误

详细说明：汽车诊断应用层协议 ISO14229-2013 ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subjso142291:2013(E Contents P e Foreword Introduction Scope............ 面面面画 aaa.aaa品画国画 Normative references Terms, definitions, symbols and abbreviated terms 3.1 Terms and definitions 11114 3.2 Abbreviated terms ■ Document overview Application layer services 6.1 General 6.2 Format description of application layer services 6.3 Format description of service primitives......... 6. 4 Service data unit specification 12 Application layer protocol 15 General definition 15 2 Protocol data unit specification.. 16 7.3 Application protocol control information 16 Negative response/confirmation service primitive 18 7.5 Server response implementation rules 18 Service description conventions 8.1 Service description……… 8.2 Request message…… 8.3 Positive response message 33 8. 4 Supported negative response codes(nrc_) 8.5 Message flow examples 34 Diagnostic and Communication Management functional unit 35 Overview,,,… 35 9.2 DiagnosticSession Control 36 9.3 ECUReset(0x11) service 画面面翻面面国日 94 Security Access(0x27) serice……… 47 95 CommunicationControl(0x28) service.……… 面国 53 9.6 TesterPresent(0x3E) service…… 58 7 AccessTiming Parameter(0x83 service ................ 61 9.8 Secured DataTransmission(0x84)service.-. a-......aBB 66 9.9 ControlDTCSetting(0x85) service…… …171 9.10 ResponseOnEvent(0x86) service…… 75 911 Linkcontro(0x87) service.…… 99 10 Data transmission functional unit 106 10.1 Overview 106 10.2 Read DataByldentifier( 106 10.3 ReadMemory By Address(0x23)service 113 10.4 ReadScaling DataByldentifier(0x24 119 10.5 ReadDataBy Periodicldentifier(0X 2A) service 126 10.6 Dynamically Define Dataldentifier(Ox2C)service........ 140 10.7 Write DataByldentifier (0x2E) service.n …162 10.8 WriteMemory By Address (0x3D) service 167 o Iso 2013-All rights reserved III so142291:2013(E) 1 Stored Data Transmission functional unit 174 11.1 Overview 174 1.2 ClearDiagnosticInformation(0x14 175 11.3 ReadDTCInformation(Ox19) Service.. 178 12 Inputoutput Control functional unit. B1面日画面 245 12.1 Overview 245 12.2 InputoutputControlByldentifier(0x2F 245 13 Routine functional unit 259 13.1 Overview,……,, 国量面国■ 259 132 Routine contro|(0x31) service…,,...,,.,.,...,,.,,,260 14 Upload download functional unit.mmm.an 270 14.1 Overvi 270 14.2 RequestDownload(0x34) service... 270 143 RequestUpload(0X35) service…,,,,…,……,…,………275 144 TransferData(0X36) service…… ……280 14.5 RequestTransferExit (0X37) service........... 285 146 RequestFileTransfer(0X38) service…………… 295 15Non- volatile server memory programming process……… 303 15.1 General information…… 303 15.2 Detailed programming sequence.n …307 15.3 Server reprogramming requirements,,,,,,,,,…,,…,… 315 15.4 Non-volatile server memory programming message flow examples 319 Annex a (normative) Global parameter definitions ∴325 A1 Negative response codes…,,,,,…, 325 Annex B (normative)Diagnostic and communication management functional unit data-parameter definitions 333 B1c。 mmunication Type parameter definition……,,,…,…,…,…,…,…,…,……333 B2 eventWindow Time parameter definition ..aean. 334 B.3 nkControlModeldentifier parameter definition eemeren. 334 B4 nodeldentification Number parameter definition……,,,,,,…,…,… 335 AnnexC (normative)Data transmission functional unit data-parameter definitions.ma. 337 C1 DID parameter definitions. 337 C.2 scalingByte parameter definitions…,,,…,…,…, …43 C.3 scaling Byte Extension parameter definitions….………,…,…,……,,…,……………,345 C4 transmissionMode parameter definitions…,,………,,,,,…,…,…,",,…,,…351 C.5 Coding of UDs version number…,………,…,,…,…,…,,…,…,…,…,,…,"…,…,…,………352 Annex d(normative) Stored data transmission functional unit data- parameter definitions 353 D1 groupofDTC 353 D 2 DTCStatusMask and status ofdtc bit definitions 353 D3 DTC severity and class definition m......a.... 366 D, 4 dTCFormatldentifier definition 369 D5 Functional Groupldentifier definition........ 369 D6 DTCFaultDetection Counter operation implementation example.. 37 D7 DTCAging Counter example 372 Annex E(normative)Input output control functional unit data-parameter definitions 374 E1 InputoutputControlParameter definitions 374 Annex f( normative) Routine functional unit data- parameter definitions……,…,,…,……,…,375 F1 Routineldentifier(RID) definition ::日 375 Annex G(normative Upload and download functional unit data- parameter 376 G.1 Definition of modeOfOperation values…,…,…,…,…,…,…,…,…, 376 Annex H (informative) Examples for addressAnd Length Formatldentifier parameter values .mmm.amm. 377 H1 address AndLength Formatldentifier example valuese........mB..ann.. 377 Annex I (normative) Security access state chart 379 oIso 2013-All rights reserved so142291:2013(E Genera|,… 37 .2 Disjunctive normal form based state transition definitions.m..mane. 379 Annex J (informative) Recommended implementation for multiple client environments 385 Introduction.… 385 J.2 Implementation specific limitations…,,…,,…,",…,",…,…,…,…,,……………385 J3 Use cases relevant for system design 386 4 Use case evaluation. ■1面国日日画面a量画量画 388 J.5 Multiple client server level implementation ∴389 Bibliography….,......,.,.,….,…………391 O Iso 2013-All rights reserved so142291:2013(E) Foreword ISo(the International Organization for Standardization )is a worldwide federation of national standards bodies (ISo member bodies). The work of preparing International Standards is normally carried out through ISo technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee International organizations, governmental and non-governmental, in liaison with ISo, also take part in the work. ISo collaborates closely with the International Electrotechnical Commission(IEC)on all matters of electrotechnical standardization International standards are drafted in accordance with the rules given in the isonEc Directives, Part 2 The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 of the member bodies casting a vote Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISo shall not be held responsible for identifying any or all such patent rights Iso 14229-1 was prepared by Technical Committee ISO/C 22, Road vehicles, Subcommittee Sc 3 Electrical and electronic equipment This second edition cancels and replaces the first edition(Iso 14229-1: 2006), which has been technically revised Iso 14229 consists of the following parts, under the general title road vehicles- Unified diagnostic services (UDS Part 1: Specification and requirements Part 2: Session layer services -Part 3: Unified diagnostic services on CAN implementation (UDSon CAN) Part 4: Unified diagnostic services on FlexRay implementation(UDSonFR) Part 5: Unitied diagnostic services on Internet Protocol implementation(UDSon/P) Part 6: Unified diagnostic services on K-Line implementation (UD SonK-Line The following part is under preparation Part 7: Unified diagnostic services on Local Interconnect Network implementation(UDSonLIN The titles of future parts will be drafted as follows Part n: Unified diagnostic services on . implementation (UDSon oIso 2013-All rights reserved so142291:2013(E Introduction So 14229 has been established in order to define common requirements for diagnostic systems, whatever the serial data link is To achieve this, ISo 14229 is based on the Open Systems Interconnection(OSI) Basic Reference Model in accordance with iso 7498 -1 and iso/EC 10731 which structures communication systems into seven layers When mapped on this model, the services used by a diagnostic tester(client) and an Electronic Control Unit (ECU, server) are broken into the following layers in accordance with T able 1 Application layer (layer 7), unified diagnostic services specified in ISo 14229-1, ISo 14229-3 UDSon CaN. Iso14229-4 UDSonFR, iso14229-5 UDSoniP. Iso14229-6 UDSonK-Line, Iso14229-7 UDSonln. further standards and so 27145-3 WWH-OBD Presentation layer(layer 6), vehicle manufacturer specific, ISO27145-2 WWH-OBD Session layer services(layer 5)specified in ISo 14229-2 Transport layer services (layer 4), specified in Iso 15765-2 DOCAN, ISo 10681-2 Communication on FlexRay, Iso 13400-2 DolP, ISo 17987-2 LIN, ISo 27145-4 WWH-OBD Network layer services (layer 3 ), specified in ISo 15765-2 DoCAN, ISo 10681-2 Communication on FlexRay, Iso 13400-2 DolP, ISo 17987-2 LIN, ISO 27145-4 WWH-OBD Data link layer (layer 2), specified in ISo 11898-1, ISo 11898-2, ISo 17458-2, ISO 13400-3, IEEE 802.3 ISo 14230-2.Is017987-3 LIN and further standards. Iso27145-4 WWH-OBD Physical layer(layer 1), specified in ISo 11898-1, ISo 11898-2, ISo17458-4, ISo 13400-3, IEEE 802.3, Iso 14230-1so17987-4LIN and further standards, so 27145-4 WWH-OBD NOTE The diagnostic services in this standard are implemented in various applications e.g. Road vehicles Tachograph systems, Road vehicles Interchange of digital information on electrical connections between towing and owed vehicles, Road vehicles- Diagnostic systems, etc. It is required that future modifications to this standard provide long-term backward compatibility with the implementation standards as described above Table 1-Example of diagnostic/programming specifications applicable to the oSI layers Applicability os seven Enhanced diagnostics services WWH layer OBD Application ISo 14229-1.s0 14229-3 UDSon CaN. Iso14229-4 UDSonFR. ISo 14229-5 ISo (layer 7) UDSonlP, ISO 14229-6 UDSonK-Line, ISO 14229-7 UDSonLIN, further standards27145-3 Presentation (layer 6) vehicle manufacturer specific ISO 27145-2 ession Seven layer (layer 5) So142292 according to Transport SO/EC 7498-1(layer 4) further ISO ISo standards ISO/EC 1073 Network 157652106812134002 applicable179872 tandards Data link SO ISO ISO further 27145-4 (layer 2 11898-1, 17458-2 13400-3, 14230-2 17987-3 standards IEEE Physical (layer 1) 11898-2 17458-4 8023 142301179874 standards O Iso 2013-All rights reserved INTERNATIONAL STANDARD sO14229-1:2013(日 Road vehicles-Unified diagnostic services UDS) Part 1 Specifications and requirements Scope This part of Iso 14229 specifies data link independent requirements of diagnostic services, which allow a diagnostic tester(client) to control diagnostic functions in an on-vehicle Electronic Control Unit(ECU, server such as an electronic fuel injection, automatic gear box, anti-lock braking system, etc. connected to a serial data link embedded in a road vehicle It specifies generic services, which allow the diagnostic tester (client)to stop or to resume non-diagnostic message transmission on the data link This part of iso 14229 does not apply to non-diagnostic message transmission on the vehicle's communication data link between two Electronic Control Units. However, this part of iso 14229 does not restrict an in-vehicle on-board tester (client) implementation in an ECu in order to utilize the diagnostic services on the vehicle's communication data link to perform bidirectional diagnostic data exchange This part of iso 14229 does not specify any implementation requirements 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document(including any amendments )applies ISo 14229-2, Road vehicles- Unified diagnostic services(UDS)-Part 2: Session layer services 3 Terms, definitions, symbols and abbreviated terms 3.1 Terms and definitions For the purposes of this document, the following terms and definitions apply 3.1.1 boot manager part of the boot software that executes immediately after an ECU power on or reset whose primary purpose is to check whether a valid application is available to execute as compared to transferring control to the reprogramming software NOTE The boot manager may also take into account other conditions for transitioning control to the reprogramming software 3.12 boot memory partition area of the server memory in which the boot software is located o Iso 2013-All rights reserved so142291:2013(E) 3.13 boot software software which is executed in a special part of server memory which is used primarily to boot the ecu and perform server programming NOTE 1 This area of memory is not erased during a normal programming sequence and must execute when the server application is missing or otherwise deemed invalid to always ensure the capability to reprogram the server noTE 2 See also 3.1.1 and.1.17 3.14 client function that is part of the tester and that makes use of the diagnostic services NoTE A tester normally makes use of other functions such as data base management, specific interpretation human-machine interface 3.1.5 diagnostic data data that is located in the memory of an electronic control unit which may be inspected and/or possibly modified by the tester NOTE 1 Diagnostic data includes analogue inputs and outputs digital inputs and outputs, intermediate values and various status information NOTE 2 Examples of diagnostic data are vehicle speed, throttle angle, mirror position, system status, etc. Three types of values are defined for diagnostic data: the current value: the value currently used by(or resulting from) the normal operation of the electronic control unit; a stored value: an internal copy of the current value made at specific moments (e.g. when a malfunction occurs or periodically); this copy is made under the control of the electronic control unit; a static value: e.g. VIN The server is not obliged to keep internal copies of its data for diagnostic purposes, in which case the tester may only request the current value NOTE 3 Defining a repair shop or development testing session selects different server functionality(e.g. access to all memory locations may only be allowed in the development testing session) 3.1.6 diagnostic routine routine that is embedded in an electronic control unit and that may be started by a server upon a request from the client NOTE It could either run instead of a normal operating program, or could be enabled in this mode and executed with the normal operating program. In the first case, normal operation for the server is not possible. In the second case multiple diagnostic routines may be enabled that run while all other parts of the electronic control unit are functioning normally 3.17 diagnostic service information exchange initiated by a client in order to require diagnostic information from a server or/and to modify its behaviour for diagnostic purpose 3.18 diagnostic session state within the server in which a specific set of diagnostic services and functionality is enabled oIso 2013-All rights reserved

(系统自动生成,下载前可以参看下载内容)