Standardized programming interfaces for automotive
Standardized programming interfaces are defined with two specific aims in mind: first of all consistent runtime responses of test and diagnostic systems regardless of use and secondly the consistent integration of VCIs (Vehicle Communication Interfaces) in test systems regardless of OEM and test system manufacturer.
|D-Server (ISO 22900)||The D-Server API (also called ASAM MCD-3D or diagnostic system API) describes a programming interface for symbolic access to vehicles and ECUs.|
|D-PDU API (ISO 22900)||The D-PDU API describes an API for accessing vehicle interfaces (VCIs).|
|PassThru (SAE J2534)||The J2534 defined by the Society of Automotive Engineers (SAE) describes a programming interface for the hexadecimal access of diagnostic protocols.|
|RP1210||The RP1210 is a programming interface classified as a “recommended practice” that, in particular, is used for accessing diagnostic interfaces in the truck environment.|
|D-Server (ISO 22900)||DTS COS, |
DTS Monaco API-RT
|D-PDU API||Vehicle Communication Interfaces (VCIs)|
All tools with DTS Base System have interfaces integrated in compliance with SAE J2534
|OEM & Lieferanten||Advantages of Using Current International Standards in Vehicle Diagnostics|
Vehicle diagnostics is now covered completely by the latest ODX and OTX standards.
|Automotive||Vehicle Diagnostics - From Nuisance to Necessity (Part 1+2)|
Diagnostics - From Engineering to Service