Automotive Electronics

Softing TDX: ODX- and OTX-Based Diagnostic System Framework

October 17, 2016 · Product News

ODX (Open Diagnostic data eX-change) and OTX (Open Test sequence eXchange) standards are very well established description formats for diagnostics in the automotive and related vehicle industries. Especially OTX, which was invented and developed on behalf of OEMs, is now increasingly used in diagnostic systems and applications.

The driver for the standardization of diagnostic description formats is most definitely the exponentially growing complexity of modern and technologically advanced vehicles. Modern automobiles, trucks and especially agricultural and civil engineering machines can have up to 100 or even more electronic control units (ECU) on board.

These have to be covered by the functionality of a diagnostic system used by the technician in the service workshop or in the field. The diagnostic systems also play an important role during the vehicle development and validation process as well as in the production and post-production life cycle stages.

Read the entire technical article written by Softing product manager Marjan Hanc. The main topics are:

Diagnostic strategies for modern vehicles
Functional requirements for a modern diagnostic system
Softing TDX - the modular solution for current diagnostic requirements
Software architecture of Softing TDX
Softing TDX.studio Toolbox
Softing TDX.workshop - the individualized diagnostic system solution
The role model and protection of proprietary content
Maintenance of the diagnostic system in the field

Read Article

Blog Automotive · Product News

TDX · OTX · ODX · TDX.studio · TDX.workshop · service tester · aftersales service

This website uses cookies. Those have two functions: On the one hand they are providing basic functionality for this website. On the other hand they allow us to improve our content for you by saving and analyzing anonymized user data. You can redraw your consent to using these cookies at any time. Find more information regarding cookies on our Data Protection Declaration and regarding us on the Imprint.

Mandatory

These cookies are needed for a smooth operation of our website.

Name	Purpose	Lifetime	Type	Provider
CM-CookieConsent	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
CookieConsent	Obsolete: Saves your consent to using cookies.	1 year	HTML	Website

Marketing

With the help of these cookies we are able improve our offer for our users by providing them additional content and services.

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

Tracking

With the help of these cookies we strive to improve our offer for our users. By means of anonymized data of website users we can optimize the user flow. This enables us to improve ads and website content.

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

Softing TDX: ODX- and OTX-Based Diagnostic System Framework

Read the entire technical article written by Softing product manager Marjan Hanc. The main topics are:

Contact

Navigation

Newsletter

Connect

We are member of the following associations: