ISO 14229-1-2013 最新版 UDS

所需积分/C币:9 2019-01-02 09:34:50 4.93MB PDF

ISO 14229-1-2013 最新版 非扫描版
lsO14229-1:2013(E) Contents Page Foreword Introduction v Scope.............................. 4. 1 Normative references Terms, definitions, symbols and abbreviated terms 3.1 Terms and definitions 3.2 Abbreviated terms 4 Conventions…5 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.mm........ …15 71 General definition 15 7.2 Protocol data unit specification 7.3 Application protocol control information 16 4 Negative response/confirmation service primitive 18 7.5 Server response implementation rules ∴18 Service description conventions 29 8.1 Service description 8.2 Request message 30 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 Diagnostic Session Control(0x10)service. 36 9.3 ECUReset(0x11) service 9.4 Security Access(0x27) service………… 47 9.5 Communication Control (0x28 )service. ∴53 9.6 Tester Present(0X3E)service...... 58 9.7 Access Timing Parameter(0x83 )service 面面面面面面面面面面面面面国面面面 61 9.8 Secured DataTransmission(0x84)service........ 66 9. 9 ControlDTCSetting(0x85)service.....-. 国面国面面面画面国面面面面面面国画面面日国量 9.10 ResponseOn Event(0x86)service 75 911 Link Control(0x87) service.……… 10 Data transmission functional un it 106 10.1 Overview .106 10.2 Read DataByldentifier(0x22) service…,,…… 106 10.3 ReadMemory By Address(Ox23 )service.... 113 10.4 ReadScalingDataByldentifier(0x24 )service 119 10.5 ReadDataBy Periodicldentifier(0x2A) service 126 10.6 Dynamically Define Dataldentifier(0x2c)service....... 140 10.7 Write DataByldentifier (0X2E) service.... 162 10.8 Write Memory By Address(0x3D) service…....,,.,,……………,,……………167 Iso 2013-All righ hts reserved so142291:2013(E) Stored data transmission function al unit 174 11.1。 verview, 174 11.2 ClearDiagnosticInformation(0x14) Service ∴175 11.3 ReadDTCInformation(0x19) Service 178 2 Inputoutput Control functional unit I000000000 n245 12.1。 vervet 22 Inputoutputcontro| Byldentifier(0X2F) service…....,…,… 245 13 Routine functional unit …259 13.1 Overview… 259 132 Routine control(0x31) service…,….,.,.,,…,,,….,…260 14 Upload D。 wnload functional unit,,,… 270 141 overview 270 14.2 RequestDownload(0x 34)service.......... 270 14.3 RequestUpload (0x35)service....... 275 14.4 TransferData(0X36)service.. ……………280 14.5 RequestTransferExit(0X37) service 285 146 RequestFile Transfer(0X38) service…,,,,…,… 295 15 Non- volatile server memory programming process……,,,,………,…,,………………303 15.1 General information 303 15.2 Detailed programming sequence 307 15.3 Server reprogramming requirements…,,,………,,…,……,, 315 154 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∴ 1 communicationType parameter definition……,…,…,…,…,…,…,…,…,………………333 B2 eventWindow Time parameter definition…,… B 3 ink ControlModeldentifier parameter definition 334 B4 nodeldentificationNumber parameter definition,,,……,…,,, 335 Annex c( normative) Data transmission functional unit data- parameter definitions…………337 C.1D| D parameter definitions….,…,…,,,… 337 C2 scaling Byte parameter definitions…… 343 C 3 scaling Byte Extension parameter definitions....nd 345 transmissionMode parameter definitions…,.,,.,,,…,,…,…,…,…,…,,…351 .5 Coding of UDs version number..meee. …352 Annex d(normative) Stored data transmission functional unit data-parameter definitions groupOfDTC parameter definition 353 D2 DTCStatusMask and statusofdtc bit definitions ∴53 D 3 DTc severity and class definition amen. 366 D,4 DTC Formatldentifier definition 量面 369 D.5 FunctionalGroupldentifier definition….,,,…,…,, 369 D6 DTCFaultDetection Counter operation implementation example D7 DTCAging Counter example 1画国B面 372 Annex E (normative)Input output control functional unit data-parameter definitions 374 E1 Inputoutput。 ntrolParameter definitions∴… 374 Annex F(normative) Routine functional unit data-parameter definitions 375 F1 Routineldentifier(RID)definition... ■重, 375 AnnexG (normative)Upload and download functional unit data-parameter 376 Definition of modeofOperation values 376 Annex H (informative)Examples for address AndLength Formatldentifier parameter values.mmm. 377 address AndLength Formatldentifier example values…,…,…,…,…,…,…,………,…377 Annex I (normative) Security access state chart 379 oIso 2013-All rights reserved lsO14229-1:2013(E) General 379 .2 Disjunctive normal form based state transition definitions…,…,……,,…,…,……379 Annex J( informative) Recommended implementation for multiple client environments………… 385 Introduction 385 J 2 Implementation specific 385 J 3 Use cases relevant for system design 386 J, 4 Use case Evaluation. 388 Multiple client server level implementation …389 Bibliography…………,…,,..,.,..,391 Iso 2013-All righ hts 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 nternational Electrotechnical Commission(IEC)on all matters of electrotechnical standardization International Standards are drafted in accordance with the rules given in the ISo/EC 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 Ights. sO shall not be held responsible for identifying any or all such patent rights 2 Attention is drawn to the possibility that some of the elements of this document may be the subject of patent Iso 14229-1 was prepared by Technical Committee ISo/TC 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(UD Son CAN) Part 4: Unified diagnostic services on FlexRay implementation(UDSonFR) Part 5: Unified diagnostic services on Internet Protocol implementation(UDSon/P) Part 6: Unified diagnostic services on K-Line implementation (UDSonK-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 (UD Sor oIso 2013-All rights reserved lsO14229-1:2013(E) Introduction ISo 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 Table 1 Application layer (layer 7), unified diagnostic services specified in ISo 14229-1, ISo 14229-3 UDSon can so 14229-4 UDSonFR so 14229-5 UDSonPso14229-6 UDSonk-Line, so14229-7 UDSonliN. 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 ISo 27145-4 WWH-OBD Physical layer(layer 1), specified in ISo 11898-1, Iso 11898-2, ISo 17458-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 towed 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 oSI seven WWH Applicability layer Enhanced diagnostics services OBD Application ISo14229-1IS0 14229-3 UDSon CAN. Iso14229-4 UDSonFR. ISo 14229-5 ISo (layer 7) UDSonlP, ISo 14229-6 UDSonK-Line, Iso 14229-7 UDSonLIN, further standards 27145-3 Presentation (layer 6) vehicle manufacturer specific 27145-2 Session So14229-2 Seven laver (layer 5) ccording to Transport SO/EC7498-1 further (layer 4) ISo Not ISo standards ISO/EC 1073 Network 157652106812134002 applicable179872 Data link SO 271454 IS( ISO ISO further (layer 2) 11898-1, 17458-2 13400-3, 14230-217987-3standards Physical IEEE furthe 11898-2 8023 (layer 1) 17458-4 14230-1 179874 standards Iso 2013-All righ hts reserved INTERNATIONAL STANDARD so142291:2013(E Road vehicles-Unified diagnostic services UDS) Part 1 Specifications and requirements 1 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 vehicles 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 vehicles 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 Iso 2013-All righ hts reserved so14229-1: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 applicatlon This area of memory is not erased during a normal programming sequence and must execute when the server NOTE is missing or otherwise deemed invalid to always ensure the capability to reprogram the server noTE 2 See also 3.11 and.1.17 3.1.4 client unction 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 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.1.7 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.1.8 diagnostic session state within the server in which a specific set of diagnostic services and functionality is enabled oIso 2013-All rights reserved

...展开详情
img
  • GitHub

    绑定GitHub第三方账户获取

关注 私信 TA的资源

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