Protocols for programming interfaces

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

Protocols have always been standardized whenever different test systems (e.g. in brand and independent repair shops) are to access vehicles or different ECUs have to be integrated into subsystems – requirements that are in fact always demanded nowadays!

UDS ISO 14229

UDS was developed with the goal of standardizing different implementations of the predecessor standards and new requirements to form one generally valid diagnostic protocol.

Further Information

OBD ISO 15031

The OBD ISO 15031 is used to read out emissions-relevant information in accordance with OBD (On Board Diagnostics) legislation.

Further Information

SAE J1939

SAE J1939 was developed last century as a higher protocol layer for CAN. The aim was to develop standard communication mechanisms for trucks regardless of the OEM, engine/transmission manufacturer and test system manufacturer.

Further Information

KWP2000 CAN

The experience with KWP2000 on the K-Line was already being transferred to CAN at the end of last century. For the first time, KWP2000 on CAN (ISO 15765) enabled the diagnostics and flash programming of a large number of ECUs via central diagnostic access.

Further Information

KWP2000 K-Line

KWP2000 on the K-Line was the first standardized diagnostic protocol used in Europe on a large scale. It defines all layers of the OSI reference model from physics through transport protocol to diagnostic services.

Further Information

DoIP ISO 13400

With Diagnostics over IP, diagnostic services introduced over UDS are used over TCP/IP and Ethernet. This makes considerably higher data rates available.

Further Information

WWH-OBD ISO 27145

Worldwide harmonized OBD consolidates the whole range of OBD specifications for cars and commercial vehicles to create one regulation valid worldwide.

Further Information

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

Protocols for programming interfaces

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

UDS ISO 14229

OBD ISO 15031

SAE J1939

KWP2000 CAN

KWP2000 K-Line

DoIP ISO 13400

WWH-OBD ISO 27145

Products

Contact

Navigation

Newsletter

Connect

We are member of the following associations: