KWP2000 CAN

CAN-based protocols for diagnostic services

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

KWP2000 on CAN (ISO 15765) describes layers 3 to 7 of the OSI reference model, it thus defines all higher protocol layers including the transport protocol and the diagnostic services.

Today, KWP2000 on CAN is implemented in an incredible number of vehicles. It is currently being replaced by UDS, but shares the transport protocol to a great extent.

Softing Experience

Softing played an active role in standardization from the very beginning, contributing its extensive communication expertise. As implementation and standardization ran concurrently, we have considerable experience that led to the implementation of the protocol for our diagnostic services.

In addition, we are familiar with the counterpart in detail thanks to our experience of implementing the diagnostic protocol in the ECU - a clear competitive edge.

KWP2000 CAN Solutions

Products
EDIC Family	All our EDIC diagnostic interfaces and the VCIs of the HS family feature KWP2000
CAN Family	For our CAN interfaces, we implemented KWP2000 on the PC
Softing DTS.cos	Protocol templates for KWP2000 are provided as a standard part of the package
TestCUBE₂	Implementation of diagnostic simulation for KWP2000
Customized solutions	Numerous customized implementations of the diagnostic stack in the ECU

Further Information

Softing's Training Program

Expertise through Training - Vehicle Diagnostics, ODX, OTX, Softing DTS & user-specific Trainings

Trainings & Seminars

External Links

For more information on the standard, please refer to the following sites:

ISO 15765-2 - Wikipedia

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

KWP2000 CAN

CAN-based protocols for diagnostic services

Softing Experience

KWP2000 CAN Solutions

Further Information

Softing's Training Program

External Links

Contact

Navigation

Newsletter

Connect

We are member of the following associations: