1、BRITISH STANDARDBS ISO 22900-1:2008Road vehicles Modular vehicle communication interface (MVCI) Part 1: Hardware design requirementsICS 43.040.15g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g
2、37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS ISO 22900-1:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 April 2008 BSI 2008ISBN 978 0 580 55416 2National forewordThis British Standard is the UK implementation of ISO 22900-1:2008.Th
3、e UK participation in its preparation was entrusted to Technical Committee AUE/16, Electrical 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 cont
4、ract. Users are responsible for its correct application.Compliance with a British Standard cannot confer immunity from legal obligations.Amendments/corrigenda issued since publicationDate CommentsReference numberISO 22900-1:2008(E)INTERNATIONAL STANDARD ISO22900-1First edition2008-03-15Road vehicles
5、 Modular vehicle communication interface (MVCI) Part 1: Hardware design requirements Vhicules routiers Interface de communication modulaire du vhicule (MVCI) Partie 1: Exigences de conception du matriel BS ISO 22900-1:2008ii iiiContents Page Foreword iv Introduction v 1 Scope . 1 2 Normative referen
6、ces . 1 3 Terms and definitions. 2 4 Abbreviated terms 2 5 Specification release version information . 3 5.1 Specification release version location . 3 5.2 Specification release version 3 6 Use cases 3 6.1 OEM merger. 3 6.2 Compatibility between VCIs from after-market tool suppliers. 3 6.3 Future ve
7、hicle technology and data link(s) 4 7 Modular VCI concept 4 7.1 Compliance levels. 4 7.2 Tier 1 Modular VCI software compliance (SC) . 4 7.3 Tier 2 Modular VCI electrical compliance (EC) 5 7.4 Tier 3 Modular VCI mechanical compliance (MC) 6 7.5 Difference between software (SC) and electrical complia
8、nt (EC) MVCI Protocol Modules 7 8 Modular VCI compliance levels, hardware configurations and design requirements. 8 8.1 General. 8 8.2 Modular VCI “minimum compatibility” requirement matrix . 8 8.3 Software compliance (SC) level design requirements 9 8.4 Electrical compliance (EC) level design requi
9、rements. 12 8.5 Mechanical compliance (MC) level design requirements. 16 8.6 Data Link Connector (DLC) cable and connector 21 9 Programmable power supply 26 10 General electrical requirements 27 11 General environmental durability requirements 27 Bibliography . 28 BS ISO 22900-1:2008iv Foreword ISO
10、(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 comm
11、ittee 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 electrote
12、chnical 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 memb
13、er 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 identifyi
14、ng any or all such patent rights. ISO 22900-1 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment. ISO 22900 consists of the following parts, under the general title Road vehicles Modular vehicle communication interface (MVCI): Part 1:
15、 Hardware design requirements Part 2: Diagnostic protocol data unit application programming interface (D-PDU API) Part 3: Diagnostic server application programming interface (D-Server API) BS ISO 22900-1:2008vIntroduction The ISO 22900 series of standards is applicable to diagnose and program vehicl
16、e electronic control modules with off-board applications through the vehicles communication interface. This part of ISO 22900 has been established in order to define the requirements of cascading multiple communication interfaces supporting current, future, and legacy standardized and original equip
17、ment manufacturer (OEM) proprietary protocols implemented by different tool manufacturers. Todays situation in the automotive after-market requires different vehicle communication interfaces for different vehicle OEMs. Many vehicle communication interfaces are incompatible with regard to their inter
18、connect ability because this was not a requirement when designed. The objective of this part of ISO 22900 is to specify the hardware design requirements to support a “plug and play” type concept of different vehicle communication interfaces from different tool manufacturers. The hardware design requ
19、irements are applicable to different levels of compliance, and they will address the inter-vendor operability at the vehicle diagnostic connector end as well as the test equipment end, which executes the applications (Electronic Control Unit diagnostics, programming, etc.). Implementation of the Mod
20、ular Vehicle Communication Interface (MVCI) server concept supports overall cost reduction to the end user because a single diagnostic or programming application will support many vehicle communication interfaces supporting different protocols. BS ISO 22900-1:2008blank1Road vehicles Modular vehicle
21、communication interface (MVCI) Part 1: Hardware design requirements 1 Scope This part of ISO 22900 provides the framework to allow diagnostic and reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle communication interfaces (VCI) from multi
22、ple tool suppliers. This system enables each vehicle manufacturer to support all vehicle communication interfaces to perform diagnostics and to control the programming sequence for electronic control units (ECUs) in their vehicles. This part of ISO 22900 describes the applicable use cases to justify
23、 the benefits of ISO 22900. It also specifies the design requirements to be followed by diagnostic and programming vehicle communication interface designers. The design requirements are categorized into different levels of conformance classes to provide: “software compliance”, a set of requirements
24、for existing VCIs, which are software but not hardware compliant; “electrical compliance”, defining all signals and electrical interfaces that allow a system integrator to connect more than one VCI Protocol Module to the vehicle diagnostic connector and the host system; “mechanical compliance”, defi
25、ning standard connectors on the VCI Protocol Module to interface to the vehicle Data Link Connector (DLC) and the host system, as well as defining a cabling concept to support interfacing more than one VCI Protocol Module. The technical requirements specified in this part of ISO 22900 have been infl
26、uenced by the requirements of legal authority with regard to “vehicle OBD and programming”. The Modular Vehicle Communication Interface hardware design requirements will provide appropriate development guidance for vehicle communication interface manufacturers to meet legal authority and automotive
27、manufacturer demands with regard to inter-vendor operability. 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
28、(including any amendments) applies. ISO 15031-3, Road vehicles Communication between vehicle and external equipment for emissions-related diagnostics Part 3: Diagnostic connector and related electrical circuits, specification and use BS ISO 22900-1:20082 3 Terms and definitions For the purposes of t
29、his document, the following terms and definitions apply. 3.1 Universal Serial Bus On-The-Go USB OTG supplement to the USB 2.0 specification that augments the capability of mobile devices and USB peripherals by adding host function for connection to USB peripherals 3.2 Ethernet physical network media
30、 type 4 Abbreviated terms API Application Programming Interface ASCII American Standard for Character Information Interchange DLC Data Link Connector DLL Dynamic Link Library D-PDU API Diagnostic Protocol Data Unit Application Programming Interface D-Server API Diagnostic Server Application Programm
31、ing Interface EC Electrical Compliance ECU Electronic Control Unit MC Mechanical Compliance MVCI Modular Vehicle Communication Interface ODX Open Diagnostic data eXchange OEM Original Equipment Manufacturer PC Personal Computer PDA Personal Digital Assistant PDU Protocol Data Unit PEC Protocol Expan
32、sion Connector PEM Protocol Expansion Module PES Protocol Expansion Slot SC Software Compliance USB Universal Serial Bus USB OTG Universal Serial Bus On-The-Go BS ISO 22900-1:200835 Specification release version information 5.1 Specification release version location Specification release version inf
33、ormation is contained in each Modular VCI release document specification under the same title “Specification release version information”. It is important to check for feature support between Modular VCI release specifications if the hardware and most recent API features shall be implemented. The D-
34、PDU-API supports the reading of version information by the API function call PDUGetVersion. Release version information is also contained in the following files: Root Description File (RDF); Module Description File (MDF); Cable Description File (CDF); D-PDU API Library File. 5.2 Specification releas
35、e version The specification release version of this part of ISO 22900 is: V2.2.0. 6 Use cases 6.1 OEM merger In the past, several OEMs in the automotive industry have merged into one company. All companies leverage existing (legacy) components and jointly develop new products, which are common acros
36、s different vehicle types and badges. OEMs specify requirements and design electronic systems to be implemented in multiple vehicle platforms in order to avoid re-inventing a system for different vehicles. The majority of design, normal operation, and diagnostic data of an electronic system are re-u
37、sed if installed in various vehicles. This may create situations where more than one OEM proprietary vehicle communication protocol needs to be supported by the off-board diagnostic and programming VCI. At least two possible solutions are available to address this scenario: a) each dealership of the
38、 newly formed company shall have all OEM proprietary VCIs to diagnose/program the new vehicle design with carry over components/ECUs from legacy vehicles; b) each dealership of the newly formed company shall have a Modular VCI which meets the “mechanical compliance” requirement. Solution b) is more
39、attractive to an after-market dealership because of the flexibility to enhance the communication capability at any time. 6.2 Compatibility between VCIs from after-market tool suppliers The after-market tool suppliers design VCIs according to protocol standards, which are referenced by legal authorit
40、ies or implemented by OEMs to diagnose and program vehicle servers. Each VCI behaves differently and requires individual support and maintenance. The Modular VCI concept provides different levels of compliance to provide compatibility between different Modular VCIs from different after-market tool s
41、uppliers. BS ISO 22900-1:20084 6.3 Future vehicle technology and data link(s) Vehicle technology is growing into faster and more complex data links. Legal authorities request industry to agree on a single solution data link, but do not limit the vehicle manufacturer to implement faster data busses,
42、which might be connected to the vehicle diagnostic connector manufacturer proprietary pins. Non Modular VCI compliant interfaces meet the communication requirements as specified for a particular model line, model year range, or a certain number of data links and protocols. In many cases, a VCI needs
43、 to be replaced if a new diagnostic data bus or protocol is implemented in the vehicle. In order to adapt to new vehicle technology and data links, the Modular VCI concept specifies different compliance levels, which accommodate various levels of compatibility to provide data link and protocol enhan
44、cement capabilities. 7 Modular VCI concept 7.1 Compliance levels This clause specifies three different compliance levels for the Modular VCI concept, as described in Table 1. Table 1 Modular VCI compliance levels Tier MVCI compliance levels Description 1 Software compliance (SC) Software compliance
45、defines a set of requirements for existing VCIs, which are software but not hardware compliant (e.g. software solution). 2 Electrical compliance (EC) Electrical compliance defines all signals and electrical interfaces that allow a system integrator to connect more than one VCI Protocol Module to the
46、 vehicle diagnostic connector and the host system. This compliance level includes Tier 1 Modular VCI software compliance. 3 Mechanical compliance (MC) Mechanical compliance defines standard connectors on the VCI Protocol Module to interface with the vehicle DLC and the host system. In addition, it d
47、efines a cabling concept to support interfacing more than one VCI Protocol Module. This compliance level includes Tier 1 Modular VCI software compliance and Tier 2 Modular VCI electrical compliance. 7.2 Tier 1 Modular VCI software compliance (SC) This compliance level neither requires compatibility
48、between vehicle communication interfaces nor scan tool. Compliance is required in software and specified in ISO 22900-2 and ISO 22900-3. Figure 1 shows software compliant VCI Protocol Module linked to the vehicle diagnostic connector utilizing the original cable D and diagnostic connector adapter C.
49、 The cable D is linked to the diagnostic connector adapter C via the connector B. The software compliant VCI Protocol Module uses the connection J to the host system. The host connection can be realized via cable or standard wireless technology. BS ISO 22900-1:20085Key A MVCI Protocol Module standardized DLC connector B DLC connector to plug-in diagnostic connector adapter C Diagnostic connector adapter D Data Link Cable (DLC) J MVCI Protocol Module host connector Figure 1 Use case of Modular VCI software compliance (SC) 7.3 Tier 2
