Overview
ISO 22900-2:2022 - titled "Road vehicles - Modular vehicle communication interface (MVCI) - Part 2: Diagnostic protocol data unit (D‑PDU API)" - defines a standardized application programming interface (D‑PDU API) for MVCI protocol modules. The standard establishes a common software interface and abstraction layer so diagnostic and reprogramming applications from any vehicle OEM or tool vendor can interoperate with MVCI protocol module implementations. The document includes API function descriptions, protocol abstraction concepts, handling of MVCI module features, sample MVCI module description files, and a runtime format based on ODX.
Key Topics and Technical Requirements
- D‑PDU API functions: Detailed interface definitions (examples include PDUConstruct, PDUConnect, PDUStartComPrimitive, PDUIoCtl, PDUGetVersion, PDUGetStatus, PDUGetLastError, PDURegisterEventCallback, PDUDisconnect, etc.).
- Communication models: Support for synchronous and asynchronous communication, event callbacks, and ComPrimitives for sending/receiving diagnostic protocol data units.
- Resource management: Mechanisms for resource locking/unlocking, querying resource and module identifiers, and handling conflicting resources.
- IOCTL controls: Extensive I/O control commands for device and session management (e.g., reset, queue control, voltage/programming controls, message filters, TLS/DoIP options).
- Timing, serialization and timestamp requirements: Specifications for protocol handler timing, message serialization and timestamping to ensure deterministic diagnostic exchanges.
- Compatibility & installation: Compatibility mappings, recommended installation processes for Windows and Linux, and guidance for selecting MVCI protocol modules.
- Data structures & extensions: Standardized API data structures, ComParam definitions, manufacturer-specific mappings, and informative annexes for constants and tags.
- Use cases: Single and multiple MVCI protocol module scenarios and cross‑implementation integration strategies.
Practical Applications and Who Uses It
- Automotive tool vendors and diagnostic software developers implement the D‑PDU API to ensure their tools work with multiple MVCI modules and vehicle platforms.
- OEMs and Tier‑1 suppliers use the standard to enable consistent diagnostic/reprogramming workflows across ECU development, central diagnostic databases, and franchised dealer tooling.
- Aftermarket and garage diagnostic solution providers benefit by supporting a common API to access different MVCI hardware modules without per-device rework.
- Typical applications include ECU flashing/reprogramming, diagnostic trouble code (DTC) read/clear, live data streaming, and vehicle commissioning.
Related Standards
- Part of the ISO 22900 MVCI series; the standard also references integration and compatibility with existing industry interfaces such as SAE J2534‑1 and RP1210a for legacy tool interoperability.
Keywords: ISO 22900-2:2022, D-PDU API, MVCI, modular vehicle communication interface, diagnostic protocol data unit, vehicle diagnostics, ECU reprogramming, automotive software interface.
Open preview (PDF)Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol data unit (D-PDU API)
