Automotive

Standardized Programming Interfaces (API)

Protocols – KWP2000 (ISO 14230 and ISO 15765), UDS (ISO 14229) and SAE J1939 in use

Standardized application programming interfaces (API) 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.

 

Service-Oriented Vehicle Diagnostics

The ASAM standard SOVD (Service-Oriented Vehicle Diagnostics) describes an API for a diagnostic system integrated in the vehicle. 

 

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 VCIs in the truck environment.

Products

Standards Products
D-Server (ISO 22900) Softing DTS.cos
Softing DTS.monaco API-RT
D-PDU API Vehicle Communication Interfaces (VCIs)
All tools with Softing DTS Base System have interfaces integrated in compliance with SAE J2534
«