iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO 22900-2:2017

(Main)

Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol data unit (D-PDU API)

Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol data unit (D-PDU API)

ISO 22900-2:2017 specifies the diagnostic protocol data unit application programming interface (D-PDU API) as a modular vehicle communication interface (MVCI) protocol module software interface and common basis for diagnostic and reprogramming software applications. ISO 22900-2:2017 covers the descriptions of the application programming interface (API) functions and the abstraction of diagnostic protocols, as well as the handling and description of MVCI protocol module features. Sample MVCI module description files accompany this document. The purpose of ISO 22900-2:2017 is to ensure that diagnostic and reprogramming applications from any vehicle or tool manufacturer can operate on a common software interface and can easily exchange MVCI protocol module implementations.

Véhicules routiers — Interface de communication modulaire du véhicule (MVCI) — Partie 2: Interface de programmation d'application d'unité de données du protocole de diagnostic (D-PDU API)

General Information

Status
Withdrawn
Publication Date
24-Jul-2017
ICS
43.040.15 - Car informatics. On board computer systems
Technical Committee
ISO/TC 22/SC 31 - Data communication
Drafting Committee
ISO/TC 22/SC 31/WG 5 - Test equipment/Data eXchange Formats
Current Stage
9599 - Withdrawal of International Standard
Completion Date
21-Jun-2022
Ref Project

Relations

Revised
ISO 22900-2:2022 - Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol data unit (D-PDU API)
Effective Date
23-Apr-2020
Revises
ISO 22900-2:2009 - Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol data unit application programming interface (D-PDU API)
Effective Date
21-Jul-2012
Consolidated By
ISO 12967-2:2020 - Health informatics — Service architecture (HISA) — Part 2: Information viewpoint
Effective Date
06-Jun-2022

Buy Standard

ISO 22900-2:2017 - Road vehicles -- Modular vehicle communication interface (MVCI)ISO 22900-2:2017 - Road vehicles -- Modular vehicle communication interface (MVCI)
PreviousNext
Standard
ISO 22900-2:2017 - Road vehicles -- Modular vehicle communication interface (MVCI)
English language
362 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 22900-2
Second edition
2017-06
Road vehicles — Modular vehicle
communication interface (MVCI) —
Part 2:
Diagnostic protocol data unit (D-PDU
API)
Véhicules routiers — Interface de communication modulaire du
véhicule (MVCI) —
Partie 2: Interface de programmation d’application d’unité de
données du protocole de diagnostic (D-PDU API)
Reference number
ISO 22900-2:2017(E)
©
ISO 2017

---------------------- Page: 1 ----------------------
ISO 22900-2:2017(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2017 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 22900-2:2017(E)
Contents
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms. 2
4 Specification release version information . 4
4.1 Specification release version location . 4
4.2 Specification release version . 5
5 Modular VCI use cases . 5
5.1 OEM merger . 5
5.2 OEM cross vehicle platform ECU(s) . 5
5.3 Central source diagnostic data and exchange during ECU development . 5
5.4 OEM franchised dealer and aftermarket service outlet diagnostic tool support . 6
6 Modular VCI software architecture . 6
6.1 Overview . 6
6.2 Modular VCI D-Server software . 7
6.3 Runtime format based on ODX . 7
6.4 MVCI protocol module software . 8
6.5 MVCI protocol module configurations . 8
7 D-PDU API use cases . 9
7.1 Overview . 9
7.2 Use case 1: Single MVCI protocol module . 9
7.3 Use case 2: Multiple MVCI protocol modules supported by same D-PDU API implementation . 10
7.4 Use case 3: Multiple MVCI protocol modules supported by different D-PDU API
implementations . 11
8 Diagnostic protocol data unit (D-PDU) API . 12
8.1 Software requirements . 12
8.1.1 General requirements . 12
8.1.2 Vehicle protocol requirements . 13
8.1.3 Timing requirements for protocol handler messages . 13
8.1.4 Serialization requirements for protocol handler messages . 14
8.1.5 Compatibility requirements . 16
8.1.6 Timestamp requirements . 16
8.2 API function overview and communication principles . 16
8.2.1 Terms used within the D-PDU API . 16
8.2.2 Function overview . 17
8.2.3 General usage . 18
8.2.4 Asynchronous and synchronous communication . 21
8.2.5 Usage of resource locking and resource unlocking . 21
8.2.6 Usage of ComPrimitives . 21
8.3 Tool integration . 36
8.3.1 Requirement for generic configuration . 36
8.3.2 Tool integrator — Use case . 36
8.4 API functions — Interface description . 38
8.4.1 Overview . 38
8.4.2 PDUConstruct . 38
8.4.3 PDUDestruct . 39
8.4.4 PDUIoCtl . 40
ii-1 © ISO 2017 – All rights reserved

---------------------- Page: 3 ----------------------
ISO 22900-2:2017(E)
8.4.5 PDUGetVersion . 42
8.4.6 PDUGetStatus . 42
8.4.7 PDUGetLastError . 43
8.4.8 PDUGetResourceStatus . 44
8.4.9 PDUCreateComLogicalLink . 45
8.4.10 PDUDestroyComLogicalLink . 48
8.4.11 PDUConnect . 49
8.4.12 PDUDisconnect . 51
8.4.13 PDULockResource . 52
8.4.14 PDUUnlockResource . 53
8.4.15 PDUGetComParam . 54
8.4.16 PDUSetComParam . 61
8.4.17 PDUStartComPrimitive. 63
8.4.18 PDUCancelComPrimitive . 67
8.4.19 PDUGetEventItem . 68
8.4.20 PDUDestroyItem . 69
8.4.21 PDURegisterEventCallback . 70
8.4.22 EventCallback prototype . 72
8.4.23 PDUGetObjectId . 73
8.4.24 PDUGetModuleIds . 74
8.4.25 PDUGetResourceIds . 76
8.4.26 PDUGetConflictingResources . 77
8.4.27 PDUGetUniqueRespIdTable . 78
8.4.28 PDUSetUniqueRespIdTable . 79
8.4.29 PDUModuleConnect . 84
8.4.30 PDUModuleDisconnect . 86
8.4.31 PDUGetTimestamp . 87
8.5 I/O control section . 88
8.5.1 IOCTL API command overview . 88
8.5.2 PDU_IOCTL_RESET . 90
8.5.3 PDU_IOCTL_CLEAR_TX_QUEUE . 91
8.5.4 PDU_IOCTL_SUSPEND_TX_QUEUE . 91
8.5.5 PDU_IOCTL_RESUME_TX_QUEUE . 92
8.5.6 PDU_IOCTL_CLEAR_RX_QUEUE . 92
8.5.7 PDU_IOCTL_CLEAR_TX_QUEUE_PENDING . 93
8.5.8 PDU_IOCTL_READ_VBATT . 93
8.5.9 PDU_IOCTL_SET_PROG_VOLTAGE . 94
8.5.10 PDU_IOCTL_READ_PROG_VOLTAGE . 95
8.5.11 PDU_IOCTL_GENERIC . 95
8.5.12 PDU_IOCTL_SET_BUFFER_SIZE . 96
8.5.13 PDU_IOCTL_GET_CABLE_ID . 96
8.5.14 PDU_IOCTL_START_MSG_FILTER . 97
8.5.15 PDU_IOCTL_STOP_MSG_FILTER . 98
8.5.16 PDU_IOCTL_CLEAR_MSG_FILTER . 99
8.5.17 PDU_IOCTL_SET_EVENT_QUEUE_PROPERTIES . 99
8.5.18 PDU_IOCTL_SEND_BREAK . 100
8.5.19 PDU_IOCTL_READ_IGNITION_SENSE_STATE . 101
8.5.20 PDU_IOCTL_VEHICLE_ID_REQUEST . 102
8.5.21 PDU_IOCTL_SET_ETH_SWITCH_STATE . 103
8.5.22 PDU_IOCTL_GET_ENTITY_STATUS . 104
8.5.23 PDU_IOCTL_GET_DIAGNOSTIC_POWER_MODE . 105
8.5.24 PDU_IOCTL_GET_ETH_PIN_OPTION . 105
8.6 API functions — Error handling . 106
8.6.1 Synchronous error handling . 106
8.6.2 Asynchronous error handling . 106
8.7 Installation . 106
8.7.1 Generic description . 106
8.7.2 Windows installation process . 107
© ISO 2017 – All rights reserved iii

---------------------- Page: 4 ----------------------
ISO 22900-2:2017(E)
8.7.3 Linux installation process . 108
8.7.4 Selecting MVCI protocol modules . 108
8.8 Application notes . 108
8.8.1 Interaction with the MDF . 108
8.8.2 Accessing additional hardware features for MVCI protocol modules . 108
8.8.3 Documentation and information provided by MVCI protocol module vendors . 109
9 Using the D-PDU API with existing applications . 109
9.1 SAE J2534-1 and RP1210a existing standards . 109
10 Data structures . 110
10.1 API functions — Data structure definitions . 110
10.1.1 Abstract basic data types . 110
10.1.2 Definitions . 111
10.1.3 Bit encoding for UNUM32 . 111
10.1.4 API data structures . 111
Annex A (normative) D-PDU API compatibility mappings . 125
A.1 Mapping of D-PDU API and D-Server API . 125
A.2 Mapping of D-PDU API and ODX . 125
Annex B (normative) D-PDU API standard ComParams and protocols . 126
B.1 Standardized protocols — Support and naming conventions . 126
B.1.1 General . 126
B.1.2 SAE J2534 and RP1210a standard protocol names . 126
B.1.3 Protocol names — Combination list . 126
B.1.4 Standard protocol naming guidelines . 128
B.1.5 Standard protocol short names. 128
B.1.6 D-PDU API optional OBD protocol short names. 129
B.2 Standard protocol pin types and short names . 129
B.3 Standard protocol communication parameters (ComParams) . 130
B.3.1 Protocol ComParam description method . 130
B.3.2 ComParam class . 131
B.3.3 ComParam data type. 132
B.3.4 ComParam support . 135
B.3.5 ComParam usage . 135
B.3.6 ComParam OSI layer reference . 136
B.4 ComParam summary tables . 136
B.4.1 Application layer . 136
B.4.2 Transport layer . 140
B.4.3 Physical layer . 148
B.4.4 CAN identifier format for ISO 15765 and ISO 11898 protocols . 150
B.4.5 Non-CAN ComParam examples . 159
B.4.6 29-bit CAN identifier data page bits . 160
B.5 ComParam detailed descriptions . 160
B.5.1 ComParam definitions for application layer . 160
B.5.2 ComParam definitions for transport layer . 176
B.5.3 ComParam definitions for physical layer . 199
Annex C (informative) D-PDU API manufacturer-specific ComParams and protocols . 203
C.1 Manufacturer-specific protocols — Support and naming conventions . 203
C.1.1 General . 203
C.1.2 Manufacturer protocol naming guidelines . 203
C.1.3 Manufacturer protocol communication parameters (ComParams) . 203
Annex D (normative) D-PDU API constants . 205
D.1 Constants . 205
D.1.1 D-PDU API item type values . 205
D.1.2 ComPrimitive type values . 205
D.1.3 Object type values . 206
D.1.4 Status code values . 206
iv © ISO 2017 – All rights reserved

---------------------- Page: 5 ----------------------
ISO 22900-2:2017(E)
D.1.5 Information event values . 207
D.1.6 Resource status values . 208
D.1.7 Resource lock values . 208
D.1.8 Event callback data values . 208
D.1.9 Reserved ID and handle values . 209
D.1.10 IOCTL filter types values . 209
D.1.11 IOCTL event queue mode type values . 209
D.2 Flag definitions . 210
D.2.1 TxFlag definition . 210
D.2.2 RxFlag definition .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO
ISO 23150:2023(Main)
Road vehicles — Data communication between sensors and data fusion unit for automated driving functions — Logical interface

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available. This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

  • Standard
    344 pages
    English language
    sale 15% off
  • Draft
    345 pages
    English language
    sale 15% off
  • Draft
    345 pages
    English language
    sale 15% off
ISO
ISO 11992-4:2023(Main)
Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 4: Diagnostic communication

This document specifies diagnostic application requirements and OSI-layer related communication profiles to ensure the interchange of digital information between towing and towed vehicles with a maximum authorized total mass greater than 3 500 kg. The conformance and interoperability test plans are not part of this document.

  • Standard
    30 pages
    English language
    sale 15% off
  • Draft
    30 pages
    English language
    sale 15% off
  • Draft
    30 pages
    English language
    sale 15% off
ISO
ISO 11992-2:2023(Main)
Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 2: Application layer for brakes and running gear

This document specifies the SAE J1939-based application layer, the payload of messages, and parameter groups for electronically controlled braking systems, including anti-lock braking systems (ABS), vehicle dynamics control systems (VDC), and running gears equipment, to ensure the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including communication between towed vehicles. Conformance and interoperability test plans are not part of this document.

  • Standard
    103 pages
    English language
    sale 15% off
  • Draft
    103 pages
    English language
    sale 15% off
  • Draft
    103 pages
    English language
    sale 15% off
ISO
ISO 13209-2:2022(Main)
Road vehicles — Open Test sequence eXchange format (OTX) — Part 2: Core data model specification and requirements

This document defines the OTX core requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in the requirements section. The data model specification aims at an exhaustive definition of all OTX core features implemented to satisfy the core requirements. Since OTX is designed for describing test sequences, which themselves represent a kind of program, the core data model follows the basic concepts common to most programming languages. Thus, this document establishes rules for syntactical entities like parameterised procedures, constant and variable declarations, data types, basic arithmetic, logic and string operations, flow control statements like loop, branch or return, simple statements like assignment or procedure call as well as exception handling mechanisms. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents are interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions. With respect to documentation use cases, special attention is paid to defining a specification/realisation concept (which allows for “hybrid” test sequences: human readable test sequences that are at the same time machine-readable) and so-called floating comments (which can refer to more than one node of the sequence). The core data model does not define any statements, expressions or data types that are dependent on a specific area of application. For the convenience of the user, the ISO 13209-2 OTX XML schema definition file (XSD) is published alongside this document.

  • Standard
    191 pages
    English language
    sale 15% off
ISO
ISO 22900-2:2022(Main)
Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol data unit (D-PDU API)

This document specifies the diagnostic protocol data unit application programming interface (D‑PDU API) as a modular vehicle communication interface (MVCI) protocol module software interface and common basis for diagnostic and reprogramming software applications. This document covers the descriptions of the application programming interface (API) functions and the abstraction of diagnostic protocols, as well as the handling and description of MVCI protocol module features. Sample MVCI module description files accompany this document. The purpose of this document is to ensure that diagnostic and reprogramming applications from any vehicle or tool manufacturer can operate on a common software interface and can easily exchange MVCI protocol module implementations.

  • Standard
    434 pages
    English language
    sale 15% off
ISO
ISO 13209-3:2022(Main)
Road vehicles — Open Test sequence eXchange format (OTX) — Part 3: Standard extensions and requirements

This document defines the Open Test sequence eXchange (OTX) extension requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in Clause 4. The data model specification aims at an exhaustive definition of all features of the OTX extensions which have been implemented to satisfy the requirements. This document establishes rules for the syntactical entities of each extension. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents containing extension features are to be interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions.

  • Standard
    228 pages
    English language
    sale 15% off
ISO
ISO 20078-1:2021(Main)
Road vehicles — Extended vehicle (ExVe) web services — Part 1: Content and definitions

This document states the minimum requirements, recommendations, permissions and possibilities for ensuring interoperable web services from an accessing party’s perspective. The document: — states requirements on the structure and format of resources; — defines the concept of resource identifiers (direct and correlated); — provides different resource categories (e.g. anonymous, pseudonymized, technical, and personal resources); — provides different approaches on how to bundle shareable resources (e.g. resource group or container); — contains guidelines on how to define the unique resources of an individual application; — defines the entities and roles, necessary for granting an accessing party access to resource owner’s resources; — states requirements on how an accessing party accesses resources, including requirements on how to use the defined and referenced technologies, see Table 1. See Annex A for additional information about roles and responsibilities covered by ISO 20078 series.

  • Standard
    19 pages
    English language
    sale 15% off
  • Draft
    19 pages
    English language
    sale 15% off
ISO
ISO 20078-3:2021(Main)
Road vehicles — Extended vehicle (ExVe) web services — Part 3: Security

This document defines how to authenticate users and accessing parties on a web-services interface. It also defines how a resource owner can delegate access to its resources to an accessing party. Within this context, this document also defines the necessary roles and required separation of duties between these in order to fulfil requirements stated on security, data privacy and data protection. All conditions and dependencies of the roles are defined towards a reference implementation using OAuth 2.0 compatible framework and OpenID Connect 1.0 compatible framework.

  • Standard
    24 pages
    English language
    sale 15% off
  • Draft
    25 pages
    English language
    sale 15% off
ISO
ISO 20078-2:2021(Main)
Road vehicles — Extended vehicle (ExVe) web services — Part 2: Access

This document defines how to access resources on a web-services interface of an offering party using the Hypertext Transfer Protocol Secure (HTTPS). Resources can be accessed through request/reply and/or requested to be pushed. The Representational State Transfer (REST) architectural pattern is chosen as a common way to format resource paths both for request/reply and push. Some specific extensions to this pattern are defined to allow for asynchronous resource requests, such as, for example, forcing readouts of data from a connected vehicle.

  • Standard
    66 pages
    English language
    sale 15% off
  • Draft
    66 pages
    English language
    sale 15% off
ISO
ISO/TR 20078-4:2021(Main)
Road vehicles — Extended vehicle (ExVe) web services — Part 4: Control

This document describes the processes of an offering party’s implementation to provide (ISO 20078‑2) access-controlled (ISO 20078-3) resources (ISO 20078‑1) to accessing parties. The processes are summarized as: registration of different stakeholder as well as granting, denying and revoking of access to resources. Those processes are held as examples of combining ISO 20078‑1, ISO 20078‑2 and ISO 20078‑3 and can vary depending on the actual implementation of the offering party.

  • Technical report
    21 pages
    English language
    sale 15% off
  • Draft
    21 pages
    English language
    sale 15% off