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
Start Date
21-Jun-2022
Completion Date
08-Nov-2025
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
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 2017
© 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

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

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 .
...

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 17987-3:2025(Main)
Road vehicles — Local Interconnect Network (LIN) — Part 3: Protocol specification

This document specifies the LIN protocol including the signal management, frame transfer, schedule table handling, task behaviour, status management, and commander and responder node. It contains also OSI layer 5 properties according to ISO 14229-7 UDSonLIN-based node configuration and identification services (SID: B016 to B816) belonging to the core protocol specification. A node (normally a commander node) that is connected to more than one LIN network is handled by higher layers (i.e. the application) not within the scope of this document.

  • Standard
    74 pages
    English language
    sale 15% off
ISO
ISO 17987-2:2025(Main)
Road vehicles — Local Interconnect Network (LIN) — Part 2: Transport protocol and network layer services

This document specifies a transport protocol and network layer services tailored to meet the requirements of LIN‑based vehicle network systems on local interconnect networks. The protocol specifies an unconfirmed communication. The LIN protocol supports the standardized service primitive interface as specified in ISO 14229-2. This document provides the transport protocol and network layer services to support different application layer implementations such as: — normal communication messages, and — diagnostic communication messages. The transport layer defines transportation of data that is contained in one or more frames. The transport layer messages are transported by diagnostic frames. A standardized API is specified for the transport layer. Use of the transport layer is targeting systems where diagnostics are performed on the backbone bus (e.g. CAN) and where the system builder wants to use the same diagnostic capabilities on the LIN sub-bus clusters. The messages are in fact identical to ones in ISO 15765-2 and the PDUs carrying the messages are very similar. The goals of the transport layer are: — to have low load on commander node, — to provide full (or a subset thereof) diagnostics directly on the responder nodes, and — to target clusters built with powerful LIN nodes (not the mainstream low cost).

  • Standard
    75 pages
    English language
    sale 15% off
ISO
ISO 17987-4:2025(Main)
Road vehicles — Local Interconnect Network (LIN) — Part 4: Electrical physical layer (EPL) specification 12 V/24 V

This document specifies the 12 V and 24 V electrical physical layers (EPL) of the LIN communications system. The electrical physical layer for LIN is designed for low-cost networks with bit rates up to 20 kbit/s to connect automotive electronic control units (ECUs). The medium that is used is a single wire for each receiver and transmitter with reference to ground. Annex A provides recommendations on the LIN physical layer peripheral interface design of type UART and frame controller for commander and responder nodes. This document includes the definition of electrical characteristics of the transmission itself and also the documentation of basic functionality for bus driver devices. This document also provides the physical layer definitions for nodes with LIN AA capabilities according to one of the procedures C, D and E. All parameters in this document are defined for the ambient temperature range from −40 °C to 125 °C.

  • Standard
    43 pages
    English language
    sale 15% off
ISO
ISO 17987-7:2025(Main)
Road vehicles — Local Interconnect Network (LIN) — Part 7: Electrical physical layer (EPL) conformance test specification

This document specifies the conformance test for the electrical physical layer (EPL) of the LIN communications system. The purpose of this document is to provide a standardised way to verify whether a LIN bus driver conforms to ISO 17987-4. The primary motivation is to ensure a level of interoperability of LIN bus drivers from different sources in a system environment. This document provides all the necessary technical information to ensure that test results are consistent even on different test systems, provided that the particular test suite and the test system are conformant to the content of this document.

  • Standard
    195 pages
    English language
    sale 15% off
ISO
ISO 17987-6:2025(Main)
Road vehicles — Local Interconnect Network (LIN) — Part 6: Protocol conformance test specification

This document specifies the LIN protocol conformance test. This test verifies the conformance of LIN communication controllers with respect to ISO 17987-2 and ISO 17987-3. This document provides all necessary technical information to ensure that test results are identical even on different test systems, provided that the particular test suite and the test system are compliant to the content of this document. Annex A, Annex B and Annex C specify the protocol conformance test plans for responder nodes supporting auto addressing procedures according procedure C, procedure D or procedure E, see ISO 17987-3:2025, Annex C.

  • Standard
    104 pages
    English language
    sale 15% off
ISO
ISO 17987-1:2025(Main)
Road vehicles — Local Interconnect Network (LIN) — Part 1: General information and use case definition

This document gives an overview of the structure and the partitioning of the ISO 17987 series. In addition, it outlines the use cases where the ISO 17987 series is used. The terminology defined in this document is common for all LIN communication systems and is used throughout the ISO 17987 series. This document has been established to define the use cases for LIN.

  • Standard
    8 pages
    English language
    sale 15% off
ISO
ISO 13209-4:2024(Main)
Road vehicles — Open Test sequence eXchange format (OTX) — Part 4: Expanded extensions interface definition

This document defines the Open Test sequence eXchange (OTX) additional 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 interpreted. The syntax rules are provided by UML[2] class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions.

  • Standard
    457 pages
    English language
    sale 15% off
ISO
ISO 11898-1:2024(Main)
Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical coding sublayer

This document specifies the controller area network (CAN) data link layer (DLL) and the physical coding sub-layer (PCS). The CAN DLL features data fields of up to 2048 byte when the CAN extended data field length (XL) frame format is used. This document divides the CAN DLL into the logical link control (LLC) and the medium access control (MAC) sub-layers. The DLL’s service data unit (SDU), which interfaces the LLC and the MAC, is implemented by means of the LLC frame. The LLC frame also features the service data unit type (SDT) and the virtual CAN channel identifier (VCID), which provide higher-layer protocol configuration and identification information. How the higher-layer functions are handled is not specified in this document. There are five implementation options: 1) support of the CAN classic frame format only, not tolerating the CAN flexible data rate (FD) frame format; 2) support of the CAN classic frame format and tolerating the CAN FD frame format; 3) support of the CAN classic frame format and the CAN FD frame format; 4) support of the CAN classic frame format, the CAN FD frame format and the CAN XL frame format; 5) support of the CAN FD frame format for CAN FD light responders (Annex A). NOTE Nodes of the first option can communicate with nodes of the third and fourth option when only the CAN classic frame format is used. Nodes of the first option cannot communicate with nodes of the fifth option: any attempt at communication generates error frames. Therefore, new designs implementing the fourth option can communicate with all other nodes.

  • Standard
    82 pages
    English language
    sale 15% off
ISO
ISO 15765-2:2024(Main)
Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services

This document specifies a transport and network layer protocol with transport and network layer services tailored to meet the requirements of CAN-based vehicle network systems on controller area networks as specified in ISO 11898-1. The diagnostic communication over controller area network (DoCAN) protocol supports the standardized abstract service primitive interface as specified in ISO 14229-2 (UDS). This document supports different application layer protocols such as: — enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics); — emissions-related on-board diagnostics (OBD) as specified in the ISO 15031 series and SAE J1979 series; — world-wide harmonized on-board diagnostics (WWH-OBD) as specified in the ISO 27145 series; and — end of life activation of on-board pyrotechnic devices (the ISO 26021 series). The transport protocol specifies an unconfirmed communication. NOTE This document does not determine whether CAN CC, CAN FD or both are recommended or required to be implemented by other standards referencing this document.

  • Standard
    47 pages
    English language
    sale 15% off
ISO
ISO 11898-2:2024(Main)
Road vehicles — Controller area network (CAN) — Part 2: High-speed physical medium attachment (PMA) sublayer

This document specifies physical medium attachment (PMA) sublayers for the controller area network (CAN). This includes the high-speed (HS) PMA without and with low-power mode capability, without and with selective wake-up functionality. Additionally, this document specifies PMAs supporting the signal improvement capability (SIC) mode and the FAST mode in Annex A. The physical medium dependent (PMD) sublayer is not in the scope of this document.

  • Standard
    64 pages
    English language
    sale 15% off