ISO 22900-1:2008
Road vehicles — Modular vehicle communication interface (MVCI) — Part 1: Hardware design requirements
Road vehicles — Modular vehicle communication interface (MVCI) — Part 1: Hardware design requirements
- Статус документа:
- Действующий
- Формат:
- Электронный (PDF)
- Количество страниц:
- 29
- Дата публикации:
- 4 марта 2008 г.
- Издание:
- ISO IS 22900 edition 1 version 1
- ICS:
- 43.040.15
ISO 22900-1:2008 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 multiple 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. ISO 22900-1:2008 describes the applicable use cases to justify 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 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”, defining 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 ISO 22900-1:2008 have been influenced 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 manufacturer demands with regard to inter-vendor operability.
Abstract
Overview
ISO 22900-1:2008 defines the hardware design requirements for a Modular Vehicle Communication Interface (MVCI). The standard creates a framework that lets diagnostic and ECU reprogramming applications work with multiple Vehicle Communication Interfaces (VCIs) from different tool suppliers. Its goal is inter-vendor operability, supporting diagnostics and controlled ECU programming across legacy, current and future vehicle data links.
Keywords: ISO 22900-1, MVCI, VCI, vehicle communication interface, ECU programming, diagnostic interface.
Key Topics
- Compliance levels (tiers):
- Software compliance (SC) - software-level interoperability (specified in ISO 22900-2/3).
- Electrical compliance (EC) - defines signals, electrical interfaces and a requirement (e.g., high‑impedance default state) to allow multiple protocol modules to be combined (e.g., via Y‑cable) without bus conflicts.
- Mechanical compliance (MC) - standard connectors, Data Link Connector (DLC) cabling concepts and mechanical interfaces for plug‑and‑play protocol modules.
- Modular VCI concept - protocol modules (PEM/PEC) that can be added/removed to expand supported data links and protocols.
- Use cases covered - OEM mergers, after‑market VCI compatibility, and adaptation to future vehicle data links.
- Version & metadata management - specification release versioning (V2.2.0) and version files: RDF, MDF, CDF and D‑PDU API library (PDUGetVersion API).
- Hardware design considerations - programmable power supply, electrical and environmental durability requirements, cabling and connector specifications for the vehicle DLC and host system.
Applications
- Designing next‑generation VCI hardware and protocol modules that are interoperable across multiple OEM toolchains.
- Enabling after‑market tool suppliers to create modular VCIs that reduce the need for multiple dedicated interfaces in workshops.
- Assisting OEMs, tier‑1 suppliers and system integrators to support diagnostic and ECU programming workflows spanning legacy and new vehicle networks.
- Ensuring compliance with legal/regulatory requirements related to OBD and ECU programming while improving cost efficiency via one‑tool support.
Who should use this standard
- VCI and Protocol Module hardware designers and manufacturers
- Diagnostic tool vendors and software developers (D‑PDU API / D‑Server API)
- Automotive OEMs, tier‑1 suppliers and service network integrators
- Regulatory and compliance engineers concerned with OBD/programming interfaces
Related standards
- ISO 22900-2 - Diagnostic Protocol Data Unit Application Programming Interface (D‑PDU API)
- ISO 22900-3 - Diagnostic Server Application Programming Interface (D‑Server API)
- ISO 15031-3 - Vehicle diagnostic connector and related electrical circuits
ISO 22900-1 is essential reading for anyone creating modular, multi‑vendor vehicle communication hardware that must remain adaptable as vehicle network technologies evolve.
Технические детали
- Технический комитет
- ISO/TC 22/SC 31 - Data communication
- SKU
- ISO 22900-1:2008
Похожие стандарты
Стандарты, упомянутые в описании