BS ISO 26021-2-2008 Road vehicles - End of-life activation of on-board pyrotechnic devices - Communication requirements《道路车辆 车载打火装置报废期的激活作用 通信要求》.pdf

1、BS ISO26021-2:2008ICS 43.040.80BRITISH STANDARDRoad vehicles End-of-life activation ofon-board pyrotechnicdevicesPart 2: Communication requirementsIncorporating corrigendumJanuary 2009g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g

2、3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58National forewordThis British Standard is the UK implementation of ISO 26021-2:2008, incorporating corrigendum January 2009.The UK participation in its preparation was entrusted to Technical Committee AUE/16, Electri

3、cal and electronic equipment.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application.Compliance with a British Standard

4、 cannot confer immunity from legal obligations.BS ISO 26021-2:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2008 BSI 2009Amendments/corrigenda issued since publicationDate Comments 31 October 2009 Implementation of ISO corrigend

5、um January 2009. Table B.1 and title of Table C.2 alteredISBN 978 0 580 66645 2Reference numberISO 26021-2:2008(E)INTERNATIONAL STANDARD ISO26021-2First edition2008-07-15Road vehicles End-of-life activation of on-board pyrotechnic devices Part 2: Communication requirements Vhicules routiers Activati

6、on de fin de vie des dispositifs pyrotechniques embarqus Partie 2: Exigences de communication ISO 2009BS ISO 26021-2:2008ISO 26021-2:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be ed

7、ited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a

8、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 PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member b

9、odies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,

10、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. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyright

11、iso.org Web www.iso.org Published in Switzerland ii BS ISO 26021-2:2008 ISO 2009 ISO 2009 All rights reservediiiContents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references . 1 3 Terms and definitions. 2 4 Symbols and abbreviated terms . 2 5 Conventions 3 6 Pyrotechnic device deployme

12、nt via on-board diagnostic architecture 3 6.1 Vehicle system description . 3 6.2 Example of in-vehicle hardware and software required . 4 6.3 Additional communication line (optional) 5 6.4 Requirements for the PDT . 5 7 Relationship to existing standards. 6 7.1 General. 6 7.2 Application layer. 6 7.

13、3 Session layer. 6 7.4 Application layer and diagnostic session management timing. 6 7.5 Network layer 7 7.6 Data link layer 7 7.7 Data link layer 9 7.8 Physical layer 9 8 Deployment process. 9 8.1 General information 9 8.2 System preconditions 9 8.3 Initiation of the communication between PDT and P

14、CU. 10 8.4 Deployment process description 11 8.5 Software provisions 19 8.6 Error handling and reaction. 20 9 Communication with diagnostic services 21 9.1 Unified diagnostic services overview. 21 9.2 Diagnostic session control (10 hex) service 21 9.3 EcuReset (11 hex) service . 22 9.4 Read data by

15、identifier (22 hex) service . 22 9.5 Write data by identifier (2E hex) service 29 9.6 Security access (27 hex) service. 30 9.7 RoutineControl (31 hex) service 31 9.8 TesterPresent (3E hex) service . 35 Annex A (normative) Specification of the data identifier used 36 Annex B (normative) Deployment lo

16、op parameter definitions 41 Annex C (normative) Routine control parameter definitions. 47 Bibliography . 49 ISO 2009 All rights reserved BS ISO 26021-2:2008ISO 26021-2:2008 (E)iv Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies

17、(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, g

18、overnmental 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 ISO/I

19、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 mem

20、ber 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 26021-2 was prepared by Technical Committee ISO/TC 22, Road vehicles,

21、Subcommittee SC 3, Electrical and electronic equipment. ISO 26021 consists of the following parts, under the general title Road vehicles End-of-life activation of on-board pyrotechnic devices: Part 1: General information and use case definitions Part 2: Communication requirements Part 3: Tool requir

22、ements Part 4: Additional communication line with bidirectional communication Part 5: Additional communication line with pulse width modulated signal NOTE Additional parts will be introduced as necessary to take into account requirements not yet covered by the standard. ISO 2009 All rights reservedB

23、S ISO 26021-2:2008ISO 26021-2:2008 (E)vIntroduction ISO 26021 describes a method for the in-vehicle deployment of pyrotechnically activated components (also referred to as pyrotechnic components or pyrotechnic devices) in cars. Worldwide, nearly all new vehicles are equipped with one or more safety

24、systems. Advanced protection systems using pyrotechnic actuators are becoming more common. All components which contain pyrotechnic substances should be handled in the same way. Recycling of these vehicles requires a new process which ensures that the deactivation of airbags will be safe and cost-ef

25、ficient. Based on the harmonization of the on-board diagnostics (OBD) interface, there is an opportunity to use this interface for on-board deployment, utilizing the same tools and processes. The representatives of the global automobile industry have decided the following: automobile manufacturers d

26、o not support reuse as an appropriate treatment method for pyrotechnic devices; automobile manufacturers believe treatment of pyrotechnic devices is required before shredding; automobile manufacturers support in-vehicle deployment as the preferred method. Based on this decision, the four major autom

27、obile manufacturer associations (ACEA, Alliance, JAMA and KAMA) started to develop a method for the in-vehicle deployment of pyrotechnic components in cars with the pyrotechnic device deployment tool (PDT). The vision is that, one day, a dismantler will need only one tool without any accessories in

28、order to deploy all the pyrotechnic devices inside an end-of-life vehicle (ELV). The target is to use an existing interface to the car. This part of ISO 26021 is applicable to the in-vehicle deployment of pyrotechnic devices in vehicles. It defines communication methods to be implemented by a pyrote

29、chnic control unit (PCU) to allow the PDT to successfully establish and maintain communication with the PCUs in the vehicle to deploy all of the pyrotechnic devices sequentially. ISO 2009 All rights reserved BS ISO 26021-2:2008ISO 26021-2:2008 (E)BS ISO 26021-2:2008ISO 26021-2:2008 (E)BS ISO 26021-2

30、:2008INTERNATIONAL STANDARD ISO 26021-2:2008(E )1Road vehicles End-of-life activation of on-board pyrotechnic devices Part 2: Communication requirements 1 Scope This part of ISO 26021 defines the deployment process, the system architecture, CAN-based communication methods and system preconditions wh

31、ich have to be implemented to fulfil the use cases defined in ISO 26021-1. Additionally, the relationship to and use with other existing standards are defined. This part of ISO 26021 also describes the technical details of the on-board deployment method. The way in which the pyrotechnic devices cont

32、ained in the vehicle function in conjunction with the PDT is the primary focus of this document. Under the provisions of this document, the design of the PDT or PCU can be implemented in accordance with specific functionality and hardware requirements. This part of ISO 26021 specifies the access to

33、the PCU. This includes communication as well as the logic sequences which are involved during the activation process. 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 re

34、ferences, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 10731, Information technology Open Systems Interconnection Basic Reference Model Conventions for the definition of OSI services ISO 11898-1, Road vehicles Controller area network (CAN) Part 1: Data li

35、nk layer and physical signalling ISO 14229-1, Road vehicles Unified diagnostic services (UDS) Part 1: Specification and requirements ISO 15031-3, Road vehicles Communication between vehicle and external equipment for emissions-related diagnostics Part 3: Diagnostic connector and related electrical c

36、ircuits, specification and use ISO 15765-2:2004, Road vehicles Diagnostics on Controller Area Networks (CAN) Part 2: Network layer services ISO 15765-3:2004, Road vehicles Diagnostics on Controller Area Networks (CAN) Part 3: Implementation of unified diagnostic services (UDS on CAN) ISO 15765-4, Ro

37、ad vehicles Diagnostics on Controller Area Networks (CAN) Part 4: Requirements for emissions-related systems ISO 26021-1, Road vehicles End-of-life activation of on-board pyrotechnic devices Part 1: General information and use case definitions ISO 26021-4, Road vehicles End-of-life activation of on-

38、board pyrotechnic devices Part 4: Additional communication line with bidirectional communication ISO 2009 All rights reserved 2 ISO 26021-5, Road vehicles End-of-life activation of on-board pyrotechnic devices Part 5: Additional communication line with pulse width modulated signal 3 Terms and defini

39、tions For the purposes of this document, the terms and definitions given in ISO 14229-1 and the following apply. 3.1 key data value sent from the external test equipment to the on-board controller in response to the seed in order to gain access to the locked services 3.2 pyrotechnic device deploymen

40、t tool tool designed to be plugged into the OBD interface in order to communicate via the internal computer network in an end-of-life vehicle with all control units which are able to activate pyrotechnic devices NOTE This tool will comprise e.g. a computer, a connection between the computer and the

41、diagnostic connector, and some software. 3.3 pyrotechnic control unit PCU electronic control unit in the vehicle network which controls the activation of pyrotechnic devices 3.4 safing mechanism whose primary purpose is to prevent an unintended functioning of the PCU processor prior to detection of

42、a crash situation 3.5 safing unit part of the PCU (e.g. an electromechanically operated switch or a separate processor) that allows the pyrotechnic component deployment microprocessor (P) to deploy the pyrotechnic devices via the driver stage 3.6 scrapping program module module responsible for firin

43、g the selected pyrotechnic device loops one by one 3.7 scrapping program module loader module responsible for converting the scrapping program module to an executable format 3.8 seed pseudo-random data value sent from the on-board controller to the external test equipment, which is processed by the

44、security algorithm to produce the key 4 Symbols and abbreviated terms ACL additional communication line CAN controller area network ELV end-of-life vehicle OBD on-board diagnostics ISO 2009 All rights reservedBS ISO 26021-2:2008ISO 26021-2:2008 (E)3PCU pyrotechnic control unit PDT pyrotechnic device

45、 deployment tool RAM random access memory SPL scrapping program module loader SPM scrapping program module SRS supplementary restraint system C microcontroller 5 Conventions ISO 26021 is based on the conventions for the definition of OSI services (see ISO/IEC 10731) as they apply to diagnostic servi

46、ces. 6 Pyrotechnic device deployment via on-board diagnostic architecture 6.1 Vehicle system description ISO 26021 is based on a vision of the diagnostic network architecture in combination with the PCU deployment architecture that is described below. The PCU is connected to the vehicle diagnostic c

47、onnector in accordance with ISO 15031-3. The PDT communicates with the PCU on CAN_H and CAN_L, which are the mandatory vehicle interfaces. Depending upon the specific architecture of the vehicle, the mandatory link of the PCU may be connected via a gateway to the diagnostic connector; thus a CAN int

48、erface in the PCU for the mandatory link may not be required. During the deployment procedure, the vehicle PCUs shall be powered by the vehicle battery or, if the battery is flat, by connecting an external power source to the battery terminals. This requires an undamaged electrical architecture for

49、the devices involved. Figure 1 Access to the vehicle via diagnostic connector ISO 2009 All rights reserved BS ISO 26021-2:2008ISO 26021-2:2008 (E)4 To interface the PCU with the vehicle, a PDT to diagnostic connector interface shall be used. The purpose of this interface is to provide the CAN bus interface and optional ACL interface with the vehicle; provide widely known standard wire interfaces like UART (RS232) or USB, or wireless interfaces like BLUETOOTH and WLAN. The P