ISO 15765-3-2004 Road vehicles - Diagnostics on Controller Area Networks (CAN) - Part 3 Implementation of unified diagnostic services (UDS on CAN)《道路车辆 控制器区域网络(.pdf

1、 Reference numberISO 15765-3:2004(E)ISO 2004INTERNATIONAL STANDARD ISO15765-3First edition2004-10-15Road vehicles Diagnostics on Controller Area Networks (CAN) Part 3: Implementation of unified diagnostic services (UDS on CAN) Vhicules routiers Diagnostic sur gestionnaire de rseau de communication (

2、CAN) Partie 3: Mise en uvre des services de diagnostic unifis (SDU sur CAN) Copyright International Organization for Standardization Reproduced by IHS under license with ISO Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO 15765-3:2004(E) PDF disclaimer This PDF

3、 file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein

4、the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PD

5、F-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO 2004 All rights reserved.

6、 Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester.

7、ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2004 All rights reservedCopyright International Organization for Standardization Reproduced by IHS under license with ISO Not fo

8、r ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO 15765-3:2004(E) ISO 2004 All rights reserved iiiContents Page Foreword. v Introduction . vi 1 Scope 1 2 Normative references . 1 3 Terms, definitions and abbreviated terms 2 4 Conventions 2 5 Unified diagnostic services

9、 (UDS) applicability to OSI model . 2 6 Application and session layers . 2 6.1 Application layer services 2 6.2 Application layer protocol 2 6.3 Application layer and diagnostic session management timing. 2 6.3.1 General. 2 6.3.2 Application layer timing parameter definitions . 4 6.3.3 Session layer

10、 timing parameter definitions . 6 6.3.4 Client and server timer resource requirements. 6 6.3.5 Detailed timing parameter descriptions . 9 6.3.6 Error handling . 27 7 Network layer interface. 29 7.1 General information 29 7.2 FlowControl N_PCI parameter definition29 7.3 Mapping of A_PDU onto N_PDU fo

11、r message transmission 29 7.4 Mapping of N_PDU onto A_PDU for message reception 29 8 Standardized diagnostic CAN identifiers .30 8.1 Legislated 11 bit OBD CAN identifiers 30 8.2 Legislated 29 bit OBD CAN identifiers 30 8.3 Enhanced diagnostics 29 bit CAN identifiers 30 8.3.1 General information 30 8

12、.3.2 Structure of 29 bit CAN identifier 31 8.3.3 Structure of address . 33 8.3.4 Message retrieval 35 8.3.5 Routing. 36 9 Diagnostic services implementation. 40 9.1 Unified diagnostic services overview . 40 9.2 Diagnostic and communication control functional unit . 42 9.2.1 DiagnosticSessionControl

13、(10 hex) service. 42 9.2.2 ECUReset (11 hex) service. 42 9.2.3 SecurityAccess (27 hex) service . 43 9.2.4 CommunicationControl (28 hex) service 43 9.2.5 TesterPresent (3E hex) service 43 9.2.6 SecuredDataTransmission (84 hex) service. 44 9.2.7 ControlDTCSetting (85 hex) service 44 9.2.8 ResponseOnEv

14、ent (86 hex) service 44 9.2.9 LinkControl (87 hex) service 47 9.3 Data transmission functional unit . 47 9.3.1 ReadDataByIdentifier (22 hex) service 47 9.3.2 ReadMemoryByAddress (23 hex) service 47 9.3.3 ReadScalingDataByIdentifier(24 hex) service 48 Copyright International Organization for Standard

15、ization Reproduced by IHS under license with ISO Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO 15765-3:2004(E) iv ISO 2004 All rights reserved9.3.4 ReadDataByPeriodicIdentifier (2A hex) service .48 9.3.5 DynamicallyDefineDataIdentifier (2C hex) service.54 9.3

16、.6 WriteDataByIdentifier (2E hex) service .54 9.3.7 WriteMemoryByAddress (3D hex) service54 9.4 Stored data transmission functional unit .54 9.4.1 ReadDTCInformation (19 hex) service 54 9.4.2 ClearDiagnosticInformation (14 hex) service .56 9.5 Input/Output control functional unit56 9.5.1 InputOutput

17、ControlByIdentifier (2F hex) service.56 9.6 Remote activation of routine functional unit56 9.6.1 RoutineControl (31 hex) service 56 9.7 Upload/Download functional unit 57 9.7.1 RequestDownload (34 hex) service.57 9.7.2 RequestUpload (35 hex) service57 9.7.3 TransferData (36 hex) service 57 9.7.4 Req

18、uestTransferExit (37 hex) service .57 10 Non-volatile server memory programming process58 10.1 General information 58 10.2 Detailed programming sequence.61 10.2.1 Programming phase #1 Download of application software and/or application data.61 10.2.2 Programming phase #2 Server configuration66 10.3

19、Server reprogramming requirements69 10.3.1 Programmable servers and their categories 69 10.3.2 Requirements for all servers to support programming.70 10.3.3 Requirements for programmable servers to support programming .70 10.3.4 Software, data identification and fingerprints74 10.3.5 Server routine

20、access .77 10.4 Non-volatile server memory programming message flow examples 78 10.4.1 General information 78 10.4.2 Programming phase #1 Pre-Programming step78 10.4.3 Programming phase #1 Programming step .79 10.4.4 Programming phase #1 Post-Programming step86 Annex A (normative) Network configurat

21、ion dataIdentifier definitions 87 Bibliography92 Copyright International Organization for Standardization Reproduced by IHS under license with ISO Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO 15765-3:2004(E) ISO 2004 All rights reserved vForeword ISO (the In

22、ternational 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 h

23、as 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

24、 standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC 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 bodi

25、es 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

26、or all such patent rights. ISO 15765-3 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment. ISO 15765 consists of the following parts, under the general title Road vehicles Diagnostics on Controller Area Networks (CAN): Part 1: General

27、 information Part 2: Network layer services Part 3: Implementation of unified diagnostic services (UDS on CAN) Part 4: Requirements for emissions-related systems Copyright International Organization for Standardization Reproduced by IHS under license with ISO Not for ResaleNo reproduction or network

28、ing permitted without license from IHS-,-,-ISO 15765-3:2004(E) vi ISO 2004 All rights reservedIntroduction This part of ISO 15765 has been established in order to enable the implementation of unified diagnostic services, as specified in ISO 14229-1, on controller area networks (UDS on CAN). To achie

29、ve this, it is based on the Open Systems Interconnection (OSI) Basic Reference Model specified in ISO/IEC 7498 and ISO/IEC 10731, which structures communication systems into seven layers. When mapped on this model, the services specified by ISO 15765 are divided into unified diagnostic services (lay

30、er 7), specified in this part of ISO 15765, network layer services (layer 3), specified in ISO 15765-2, CAN services (layers 1 and 2), specified in ISO 11898, in accordance with Table 1. Table 1 Enhanced and legislated OBD diagnostic specifications applicable to the OSI layers Open Systems Interconn

31、ection (OSI) layers Vehicle manufacturer enhanced diagnostics Legislated on-board diagnostics (OBD) Diagnostic application User defined ISO 15031-5 Application layer ISO 15765-3 ISO 15031-5 Presentation layer N/A N/A Session layer ISO 15765-3 N/A Transport layer N/A N/A Network layer ISO 15765-2 ISO

32、 15765-4 Data link layer ISO 11898-1 ISO 15765-4 Physical layer User defined ISO 15765-4 Copyright International Organization for Standardization Reproduced by IHS under license with ISO Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INTERNATIONAL STANDARD ISO 157

33、65-3:2004(E) ISO 2004 All rights reserved 1Road vehicles Diagnostics on Controller Area Networks (CAN) Part 3: Implementation of unified diagnostic services (UDS on CAN) 1 Scope This part of ISO 15765 specifies the implementation of a common set of unified diagnostic services (UDS), in accordance wi

34、th ISO 14229-1, on controller area networks (CAN) in road vehicles as specified in ISO 11898. It gives the diagnostic services and server memory programming requirements for all in-vehicle servers connected to a CAN network and external test equipment. It does not specify any requirement for the in-

35、vehicle CAN bus architecture. 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) appli

36、es. ISO 14229-1, Road vehicles Unified diagnostic services (UDS) Part 1: Specification and requirements ISO 11898-1, Road vehicles Controller area network (CAN) Part 1: Data link layer and physical signalling ISO 11898-2, Road vehicles Controller area network (CAN) Part 2: High-speed medium access u

37、nit ISO 11898-3, Road vehicles Controller area network (CAN) Part 3: Low-speed, fault-tolerant, medium dependent interface1)ISO 15031-6, Road vehicles Communication between vehicle and external equipment for emissions-related diagnostics Part 6: Diagnostic trouble code definitions1)ISO 15765-1, Road

38、 vehicles Diagnostics on controller area network (CAN) Part 1: General information ISO 15765-2, Road vehicles Diagnostics on controller area network (CAN) Part 2: Network layer service1)ISO 15765-4, Road vehicles Diagnostics on controller area network (CAN) Part 4: Requirements for emissions-related

39、 systems1)SAE J1939-21, Recommended practice for a serial control and communications vehicle network Data link layer2)1) To be published. 2) Society of Automotive Engineers standard. Copyright International Organization for Standardization Reproduced by IHS under license with ISO Not for ResaleNo re

40、production or networking permitted without license from IHS-,-,-ISO 15765-3:2004(E) 2 ISO 2004 All rights reserved3 Terms, definitions and abbreviated terms For the purposes of this document, the terms and definitions given in ISO 14229-1, ISO 15765-1 and ISO 15765-2 and the following abbreviated te

41、rms apply. DA destination address ID identifier DLC data length code GW gateway LSB least significant bit MSB most significant bit NA network address SA source address SM subnet mask TOS type of service 4 Conventions This part of ISO 15765 is based on conventions defined in ISO 14229-1, which are gu

42、ided by OSI Service Conventions (see ISO/TR 8509) as they apply for diagnostic services. 5 Unified diagnostic services (UDS) applicability to OSI model See Figure 1. 6 Application and session layers 6.1 Application layer services This part of ISO 15765 uses the application layer services as defined

43、in ISO 14229-1 for client-server based systems to perform functions such as test, inspection, monitoring, diagnosis or programming of on-board vehicle servers. 6.2 Application layer protocol This part of ISO 15765 uses the application layer protocol as defined in ISO 14229-1. 6.3 Application layer a

44、nd diagnostic session management timing IMPORTANT Any N_USData.indication with not equal to N_OK that is generated in the server shall not result in a response message from the server application. 6.3.1 General The following specifies the application layer and session layer timing parameters and how

45、 they are handled for the client and the server. Copyright International Organization for Standardization Reproduced by IHS under license with ISO Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO 15765-3:2004(E) ISO 2004 All rights reserved 3Figure 1 Implementat

46、ion of UDS on CAN in OSI model The following communication scenarios shall be distinguished from one another: a) physical communication during 1) default session, and 2) non-default session session handling required; b) functional communication during 1) default session, and 2) non-default session s

47、ession handling required. For all cases, the possibility of requesting an enhanced response-timing window by the server via a negative response message, including a response code 78 hex, shall be considered. The network layer services as defined in ISO 15765-2 are used to perform the application lay

48、er and diagnostic session management timing in the client and the server. Copyright International Organization for Standardization Reproduced by IHS under license with ISO Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO 15765-3:2004(E) 4 ISO 2004 All rights reserved6.3.2 Application layer timing parameter definitions The application layer timing parameter values for the default diagnostic session shall be in accordance with Table 2. Table 2 Application layer timing parameter definitions for the defaultSession Timing paramete