Our D-PDU API protocol software makes it easy to integrate Softing diagnostic and communication interfaces into diagnostic tools. In the case of the Softing diagnostic interfaces, the protocol stack is realized as embedded software, otherwise in the PC.
The D-PDU API makes it possible to integrate different Vehicle Communication Interfaces (VCI) in diagnostic applications. These are generally based on an MVCI server compliant with ISO 22900-3, although the direct use of the D-PDU API is possible. The diagnostic application can be implemented regardless of the protocol because all specifics are processed below the API. The protocol behavior can be controlled precisely with standardized protocol parameters.
The D-PDU API is generally used with different types of VCIs. It is part of the delivery scope with Softing diagnostic VCIs and with our CAN hardware. However, it is also possible to use it as an integration layer for other VCIs, whether for different CAN hardware, diagnostic VCIs from third-party manufacturers or for VCIs with a J2534 (PassThru) API. In diagnostic VCIs, the protocol is implemented in the firmware. This makes the runtime behavior very accurate and independent of the behavior of the PC operating system. For all other VCIs, protocols are implemented on the PC.
The normal delivery scope of the Softing D-PDU API comprises several standardized protocols for OEM diagnostics, such as UDS (ISO 14229) and Diagnostics over CAN (DoCAN, ISO 15765), and the diagnostics required by law (OBD, WWHOBD). Furthermore, Diagnostics over IP (DoIP, ISO 13400) is supported for VCIs with an Ethernet port. Softing’s long-term experience in implementation allows us to continue to implement proprietary protocols efficiently – for example for service tester projects.
The increasing scope of driver assistance and infotainment systems in modern vehicles is placing ever greater demands on the download time for flash programming. The Softing D-PDU API supports DoIP compliant with ISO 13400 and is thus perfectly equipped for current performance requirements. To ensure that communication via DoIP, which was explicitly developed for use in remote scenarios, is as secure as possible, DoIP is also implemented with TLS (Transport Layer Security). The integration of encrypted DoIP is currently the standard for secure data communication.
Please contact us. We are pleased about your interest.
D-PDU API is integrated in the delivery package of the Softing diagnostic VCIs. A D-PDU API can be purchased as an extra option for our CAN hardware. We can also implement a D-PDU API for VCIs from third-party providers on the basis of our extensive experience, for example to make a large base of existing VCIs fit for use with ODX data in an MVCI server.
|PDUAPI-EC||D-PDU API software license (ISO 22900-2) for use without DTS or OTX products for CAN and PassThru interfaces (SAE J2534) as well as for DoIP (ISO 13400) without VCI|
|PDUAPI-LIC||D-PDU API software license (ISO 22900-2) for use with DTS or OTX products for CAN and PassThru interfaces (SAE J2534) as well as for DoIP (ISO 13400) without VCI|
To get the latest D-PDU API version, please contact us at support.automotive[at]softing[dot]com