ISO 22900-2-2022 PDF

Full title and description

Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol data unit (D‑PDU API). This part of ISO 22900 defines the D‑PDU API: a protocol‑independent application programming interface for diagnostic and reprogramming applications to access modular vehicle communication interface (MVCI) protocol modules, enabling interchangeability of protocol module implementations between diagnostic tools and vehicles.

Abstract

Specifies the diagnostic protocol data unit application programming interface (D‑PDU API), including API function descriptions, abstraction of diagnostic protocols, handling and description of MVCI protocol module features, and example MVCI module description files. The goal is to provide a common software interface so diagnostic and reprogramming applications from any vehicle or tool manufacturer can operate on a shared basis.

General information

• Status: Published.
• Publication date: June 2022.
• Publisher: International Organization for Standardization (ISO).
• ICS / categories: 43.040.15 — Car informatics / On‑board computer systems.
• Edition / version: Edition 3 (ISO 22900‑2:2022).
• Number of pages: 434 pages.

Scope

Defines the D‑PDU API as a modular, protocol‑independent software interface between diagnostic/reprogramming applications and MVCI protocol modules. It covers API functions, protocol abstraction mechanisms, MVCI module feature descriptions and sample MVCI module description files, allowing diagnostic applications to load, exchange or extend protocol modules with minimal changes. The 2022 revision updates support for newer transport and protocol features used in modern vehicles.

Key topics and requirements

• Definition of the D‑PDU API functions and data structures for sending/receiving diagnostic PDUs.
• Abstraction of diagnostic protocols so the same API can be used across CAN, CAN‑FD, DoIP (Ethernet) and other transports.
• Mechanisms for describing and enumerating MVCI protocol module features and capabilities (module description files).
• Requirements for protocol module lifecycle management (load, unload, initialization, error handling).
• Interoperability and conformance guidance to allow diagnostic tools and protocol modules from different vendors to interoperate.
• 2022 updates: references and support for CAN‑FD (ISO 15765‑5), secured DoIP (TLS) and automatic DoIP reconnect handling; added ISOBUS protocol considerations.

Typical use and users

Used by diagnostic tool developers, MVCI/VCP (vehicle communication interface) and VCI hardware manufacturers, ECU and gateway suppliers, OEM diagnostic software teams, automotive aftermarket tool makers, and test labs. Typical use cases include diagnostic communication, ECU reprogramming/firmware updates, manufacturing test integration and multi‑brand aftermarket diagnostic tool interoperability.

Related standards

Part of the ISO 22900 MVCI series (see Parts 1, 2 and 3). Closely associated automotive diagnostic and transport standards include ISO 22900‑1 (MVCI hardware requirements), ISO 22900‑3 (D‑Server API), ISO 14229 (Unified Diagnostic Services — UDS), ISO 13400 (DoIP diagnostics over Ethernet) and ISO 15765 (Diagnostic communication over CAN / CAN‑FD transport).

Keywords

MVCI, D‑PDU API, diagnostic protocol, vehicle diagnostics, VCI, D‑Server, DoIP, CAN‑FD, ISO 22900, ECU reprogramming, diagnostic module description, interoperability.

FAQ

Q: What is this standard?

A: ISO 22900‑2:2022 specifies the Diagnostic Protocol Data Unit Application Programming Interface (D‑PDU API) as part of the MVCI framework, providing a common software interface for diagnostic and reprogramming applications to interact with protocol modules.

Q: What does it cover?

A: It covers API function definitions, protocol abstraction, module feature descriptions and sample module description files, plus guidance for module lifecycle and interoperability across transports such as CAN, CAN‑FD and DoIP. The 2022 edition added support and references for CAN‑FD, secured DoIP (TLS), automatic DoIP reconnect handling and ISOBUS where applicable.

Q: Who typically uses it?

A: Automotive OEM diagnostic teams, test‑equipment and VCI manufacturers, aftermarket diagnostic tool developers, ECU/gateway suppliers and test laboratories — basically anyone building diagnostic clients, servers or protocol modules that must interoperate across vehicle platforms.

Q: Is it current or superseded?

A: ISO 22900‑2:2022 is the current published edition (published June 2022) and replaces the previous ISO 22900‑2:2017 edition.

Q: Is it part of a series?

A: Yes — ISO 22900 is a multipart series (MVCI). Part 1 covers hardware requirements, Part 2 is the D‑PDU API, and Part 3 covers the D‑Server API; other related documents and parts in the diagnostic ecosystem (UDS, DoIP, ISO‑TP/CAN) are commonly used together with ISO 22900.

Q: What are the key keywords?

A: MVCI, D‑PDU API, diagnostic protocol data unit, DoIP, CAN‑FD, UDS, ECU reprogramming, protocol module, interoperability.