CarPort Docs

Software Documentation

💡 This documentation applies to CarPort version 3.2. Older or newer versions may differ in functionality.

Supported diagnostic adapters

CarPort supports VAG interfaces such as the AutoDia K509, J2534 pass-thru adapters, and the ELM327—here's how to find the right diagnostic adapter for your vehicle.

Which adapter is right for you?

Your choice of diagnostic interface largely determines which functions are available to you in CarPort. We distinguish between three basic categories:

  1. Natively supported adapters for VAG diagnostics: CarPort controls these adapters directly, without any additional software from the manufacturer. On every line the adapter provides, you get full VAG diagnostics—on the CAN bus, all protocols (KWP1281, KWP2000, UDS); on the K-Line, the older KWP1281 in addition to KWP2000. This lets you reach all ECUs (e.g., airbag, brakes, air conditioning, comfort system, infotainment) connected to a line the adapter provides. Which lines an adapter provides depends on the model, however: a pure KKL interface (e.g., AutoDia K409) only offers the K-Line and is therefore unsuitable for vehicles with CAN bus (from about 2005). Our hardware recommendation for K-Line and CAN bus: AutoDia K509, K+CAN Commander 1.4, CP compact

  2. SAE J2534 (“PassThru”) adapters: Full VAG diagnostics are also possible with a standard-compliant J2534 adapter—with one limitation on the K-Line (see Diagnostics with J2534 adapters). Since J2534 is a cross-manufacturer standard, you can also use the same adapter with other diagnostic programs. Tested by us: Tactrix Openport 2.0, Godiag GD101, TOPDON RLink J2534

  3. Generic OBD-2 adapters: Standard adapters such as the widely used ELM327 are suitable exclusively for emissions-related OBD-2 diagnostics of the engine ECU. Accessing other VAG-specific ECUs (e.g., ABS, central electrics, infotainment) is technically not possible with these adapters.

Decision guide:

Your situation Recommended adapter
Vehicle from about 2005 (CAN bus) J2534 adapter or natively supported adapter—both offer the full feature set
You already own a J2534 adapter Keep using it—CarPort detects it automatically as soon as its Windows driver is installed
You also use other diagnostic programs J2534 adapter—one adapter for all J2534-capable programs
Vehicle up to about 2004 (K-Line) Natively supported adapter with K-Line—the only way to also reach ECUs with KWP1281
You only want to check the check engine light and readiness Generic OBD-2 adapter (e.g., ELM327)

Adapter overview

The following tables show which lines each adapter provides and therefore which types of diagnostics it supports. Keep in mind that modern vehicles (from about 2005) strictly require CAN bus support.

Natively supported adapters:

Name K-Line CAN bus OBD-2
AutoDia K509 ✔️ ✔️ ✔️
K+CAN Commander 1.4 ✔️ ✔️ ✔️
CP compact ✔️ ✔️ ✔️
Menke Diag 1000 ✔️ ✔️ ✔️
AGV 4000 expert ✔️ ✔️ ✔️
DIAMEX DXM1 ✔️ ✔️ ✔️
KKL interface (e.g., AutoDia K409) ✔️ ✔️
Lawicel ✔️
TinyCAN ✔️

J2534 adapters:

Name K-Line¹ CAN bus OBD-2 Tested
All standard-compliant J2534 adapters ✔️ ✔️ ✔️
Tactrix Openport 2.0 ✔️ ✔️ ✔️ ✔️
Godiag GD101 ✔️ ✔️ ✔️ ✔️
TOPDON RLink J2534 ✔️ ✔️ ✔️ ✔️

¹ On the K-Line, only KWP2000 is possible via J2534, not KWP1281—see Diagnostics with J2534 adapters.

Generic OBD-2 adapters:

Name K-Line CAN bus OBD-2
ELM 327 (e.g., AutoDia E327) ✔️
DIAMEX DX35 ✔️
ElmScan 5 ✔️
mOByDic ✔️
OBDLink ✔️

💡 Note: The feature set of a J2534 adapter is defined by the standard and doesn't depend on the model—which is why the table shows the same entries for all J2534 devices. After hardware detection, CarPort shows you on the start page which functions your adapter actually offers.

Diagnostics with J2534 adapters

What was J2534 developed for? The SAE J2534 standard (“PassThru”) was created so that independent workshops can read out and reprogram ECUs without having to buy a separate scan tool for every vehicle brand—in the US and the EU, vehicle manufacturers are legally required to make their software usable this way. To achieve this, J2534 defines a uniform interface between the diagnostic software on the PC and the adapter on the vehicle: a single adapter is enough for any number of diagnostic programs.

Requirements. CarPort supports J2534 in the common version 04.04. You need a standard-compliant adapter whose Windows driver is installed and which—as the standard specifies—registers itself in the Windows registry in the process. CarPort evaluates these entries automatically during the hardware scan; you don't need to select a driver file or enter a path. Detected devices appear under their manufacturer's name.

Tested adapters. In principle, CarPort works with any standard-compliant J2534 adapter. We have tested the Tactrix Openport 2.0, Godiag GD101, and TOPDON RLink J2534 (see Overview). This doesn't rule out other adapters—but since the quality of manufacturer drivers varies widely, we can only vouch for these devices.

Feature set. What you can access depends on which line the ECU is connected to:

  • CAN bus: CarPort supports all protocols (KWP1281, KWP2000, UDS) as well as OBD-2. On vehicles with CAN bus—that is, from about 2005—a J2534 adapter therefore offers the full feature set, just like a natively supported adapter.
  • K-Line: Only KWP2000 is possible here, in addition to OBD-2. The older KWP1281 inherently can't be handled over the J2534 interface, because the standard doesn't provide for the byte-by-byte acknowledgment it requires.

💡 Note: ECUs that only speak KWP1281 are found mainly in older vehicles with K-Line (up to about 2004). For these vehicles, we recommend a natively supported adapter. Both K-Line protocols can occur side by side within one vehicle: with a J2534 adapter, you can reach the KWP2000 ECUs there, but not the KWP1281 ECUs.