BS ISO 22900-2:2017
Superseded
A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.
View Superseded by
Road vehicles. Modular vehicle communication interface (MVCI) Diagnostic protocol data unit (D-PDU API)
Hardcopy , PDF
10-08-2022
English
11-10-2017
Important note : Users cannot be edited or removed once added to your Multi user PDF.
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
4 Specification release version information
5 Modular VCI use cases
6 Modular VCI software architecture
7 D-PDU API use cases
8 Diagnostic protocol data unit (D-PDU) API
9 Using the D-PDU API with existing applications
10 Data structures
Annex A (normative) - D-PDU API compatibility mappings
Annex B (normative) - D-PDU API standard ComParams
and protocols
Annex C (informative) - D-PDU API manufacturer-specific
ComParams and protocols
Annex D (normative) - D-PDU API constants
Annex E (normative) - Application defined tags
Annex F (normative) - RDF and MDF description files
Annex G (informative) - Resource handling scenarios
Annex H (informative) - D-PDU API partitioning
Annex I (informative) - Use case scenarios
Annex J (normative) - OBD protocol initialization
Annex K (normative) - DoIP implementation
Bibliography
Describes 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.
| Committee |
AUE/16
|
| DevelopmentNote |
Supersedes 06/30134245 DC. (03/2009) Supersedes 14/30291315 DC. (10/2017)
|
| DocumentType |
Standard
|
| Pages |
70
|
| PublisherName |
British Standards Institution
|
| Status |
Superseded
|
| SupersededBy | |
| Supersedes |
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.
| Standards | Relationship |
| ISO 22900-2:2017 | Identical |
| SAE J1939/81_201703 | Network Management |
| ISO 16750-2:2012 | Road vehicles — Environmental conditions and testing for electrical and electronic equipment — Part 2: Electrical loads |
| ISO/IEC 8859-1:1998 | Information technology 8-bit single-byte coded graphic character sets Part 1: Latin alphabet No. 1 |
| SAE J1708_201609 | Serial Data Communications Between Microcomputer Systems in Heavy-Duty Vehicle Applications |
| ISO 7637-2:2011 | Road vehicles Electrical disturbances from conduction and coupling Part 2: Electrical transient conduction along supply lines only |
| ISO 14229-1:2013 | Road vehicles Unified diagnostic services (UDS) Part 1: Specification and requirements |
| SAE J1939/73_201601 | Application Layer - Diagnostics |
| ISO 15031-4:2014 | Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 4: External test equipment |
| SAE J1587_201301 | Electronic Data Interchange Between Microcomputer Systems in Heavy-Duty Vehicle Applications |
| SAE J2190_199306 | Enhanced E/E Diagnostic Test Modes |
| SAE J2610_201501 | Serial Data Communication Interface |
| SAE J1962_201607 | Diagnostic Connector |
| ISO 22900-1:2008 | Road vehicles — Modular vehicle communication interface (MVCI) — Part 1: Hardware design requirements |
| SAE J2740_200512 | General Motors UART Serial Data Communications |
| SAE J1939_201308 | Serial Control and Communications Heavy Duty Vehicle Network - Top Level Document |
| SAE J2534/1_201510 | Recommended Practice for Pass-Thru Vehicle Programming |
| SAE J1939/21_201603 | Data Link Layer |
| ISO/IEC 8859-2:1999 | Information technology 8-bit single-byte coded graphic character sets Part 2: Latin alphabet No. 2 |
| SAE J1979_201702 | E/E Diagnostic Test Modes |
| ISO 15031-3:2016 | Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 3: Diagnostic connector and related electrical circuits: Specification and use |
| ISO 15031-5:2015 | Road vehicles Communication between vehicle and external equipment for emissions-related diagnostics Part 5: Emissions-related diagnostic services |
| ISO 15765-2:2016 | Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services |
| ISO 22900-3:2012 | Road vehicles — Modular vehicle communication interface (MVCI) — Part 3: Diagnostic server application programming interface (D-Server API) |
| ISO 22901-1:2008 | Road vehicles — Open diagnostic data exchange (ODX) — Part 1: Data model specification |
| SAE J1850_201510 | Class B Data Communications Network Interface |
| SAE J2411_200002 | Single Wire CAN Network for Vehicle Applications |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.