D-PDU API – Protocol Software for Diagnostic Interfaces

Standardized vehicle access via D-PDU API

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.

Areas of Application

Applications for diagnostics and flash programming
Test, manufacturing and service tester applications
Applications for vehicle communication over bus systems such as CAN (FD) or Ethernet
Direct access to hardware interfaces through the application or via a diagnostic server in accordance with ISO 22900-3
Parallel communication with several ECUs, also via a range of bus systems

Benefits

Powerful mechanisms for data communication with ECUs
Reducing the load on the application by handling the communication protocols within the D-PDU API software
Parallel communication with several ECUs, also via a range of bus systems
Standardized communication parameters enable simple application of test sequences
Scalability
High flexibility
Support of the D-PDU API interface by Softing SDE and the tools based on it

D-PDU API: Protocol Software for Diagnostic Interfaces

Overview

At a Glance

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.

Hardware

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.

Protocols

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.

Secure High-Performance Communication

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.

Do you have questions about our solutions or need support?

Please contact us. We are pleased about your interest.

Contact us!

Order Information

Buying D-PDU API

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.

► Diagnostics-VCIs

► CAN-VCIs

Order Numbers
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

Downloads

Download
Software	To get the latest D-PDU API version, please contact us at support.automotive[at]softing[dot]com

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Obsolete: Saves your consent to using cookies.	14 days	HTML	Website
menuState	Remebers the menu toggle state.	1 day	HTML	Website
PHPSESSID	Assigns your browser to a session on the server.	session	HTTP	Website
fe_typo_user	Assigns your browser to a session on the server.	session	HTTP	Website
adhoc	Saves the status that you have read the Ad-hoc message.	session	HTTP	Website

Name	Purpose	Lifetime	Type	Provider
wisepops	WisePops is a tool to serve pop up messages. It uses a cookie to prevent the same message being shown more than once. We do not capture personal data in the pop ups.	2 years	HTML	Wisepops
wisepops_visits	WisePops is a tool to serve pop up messages. It uses a cookie to prevent the same message being shown more than once. We do not capture personal data in the pop ups.	2 years	HTML	Wisepops
wisepops_session	WisePops is a tool to serve pop up messages. It uses a cookie to prevent the same message being shown more than once. We do not capture personal data in the pop ups.	session	HTML	Wisepops

Name	Purpose	Lifetime	Type	Provider
_ga	Used to distinguish users.	2 years	HTML	Google
_gid	Used to distinguish users.	1 day	HTML	Google
_gat	Used to throttle request rate.	1 minute	HTML	Google
visitor_idACCOUNTID	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.	10 years	HTML	Pardot
pi_opt_inACCOUNTID	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a true or false value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to true, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to false. The visitor cookie is disabled, and the visitor is not tracked.	10 years	HTML	Pardot
visitor_idACCOUNTID-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.	10 years	HTML	Pardot
lpvACCOUNTID	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.	30 minutes	HTML	Pardot
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.	10 years	HTML	Pardot
Prism_ACCOUNTID	Store and track interaction.	2 years	HTML	Active Campaign