VAG K+Can Commander instruction

Instructions for the VAG K+CAN COMMANDER device
VAG: Audi, Volkswagen, Skoda, Seat

To begin working with the VAG K+CAN COMMANDER device, you must:
Install “Dongle_Driver_USB” (“inf+inst”)
Install the USB driver
Install VAG K+CAN COMMANDER
If the screen shows “Interface found”, your interface should work. If “Interface not found” appears, or nothing is displayed, see the “Troubleshooting” section.

ATTENTION:
Launch the program only from the folder where the software was installed!

Diagnostics using “VAG K+CAN COMMANDER”
– Standard diagnostic functions: reading/clearing error codes, device identification, adaptation, measurement of parameters, etc.
– Special functions: odometer correction, login (PIN), EEPROM reading, etc.

All modules that can be installed in the vehicle are listed on the main screen, with their numbers. If you want to connect to one of them, double-click on it. VAG K+CAN COMMANDER will attempt to connect using the following protocols sequentially:
— KWP2000 over TP2.0 at 5000KB/s (CAN)
— KWP2000 over TP1.6 at 5000KB/s (CAN)
— KWP1281 or KWP2000 over K-Line (protocol is set by default)

You can select one of these protocols as described in the “Configuration” section.

Configuration

VAG K+CAN COMMANDER can be configured by pressing the “Options” button.
Changes to detection parameters and interface timing will be applied after restarting the application.

Used protocols

The checkbox values are as follows:
— CAN TP2.0 – connection with the device using the “KWP2000 over TP2.0 at 5000KB/s” protocol
— CAN TP1.6 – connection with the device using the “KWP2000 over TP1.6 at 5000KB/s” protocol
— K-Line — KWP2000/KWP1281 connection with the device using “KWP1281 or KWP2000 over K-Line”

The checkboxes switch the protocols used during standard diagnostic requests and are not applied during autodetection.

Interface detection

The VAG K+CAN COMMANDER USB interface is detected automatically, but it can also be set manually. If there are malfunctions, as described in “Troubleshooting”, set the port manually:
— Open “Device Manager” and check which COM port the USB interface is assigned to.
— Uncheck “Automatic” and set the port manually.

Selecting timing parameters

K-Line protocols require very precise timing. Sometimes communication with certain devices may be unstable or impossible. In such cases, you can try changing some parameters (the “Advanced” button).

Viewing devices

After startup, the main screen of VAG K+CAN COMMANDER displays a list of all possible devices with their numbers. To connect to a listed device, double-click on the desired entry.

Instead of viewing all possible units, you can select a device configuration corresponding to a specific vehicle model (chassis type). To do this, choose the type (for example, “1 — VW Touran”) in the “Chassis type” panel of the main window. Pressing “Display” will show all devices that may be installed on this vehicle type.

Pressing “Scan all” scans all devices in the list. Depending on the configuration, only the selected protocols will be used.

For all detected devices, detailed information is displayed on the main screen:
— Device number
— Device name
— Device identifier
— Description
— Coding
— Part number
— DTC – stored error codes

Instead of scanning all devices, to save time, you can scan only those needed. Configure the required device list using the “Gateway config list” button.

DTC reset is one of the main diagnostic operations. Errors can be cleared in all devices at once using the “Clear all DTCs” button in the “Auto scan devices” panel; the protocols used are determined in the configuration.

Broadcast requests

Broadcast requests are sent to all devices or a group of devices at once.
VAG K+CAN COMMANDER can send a broadcast request to all devices to set required modes, clear errors, or enable/disable devices — the corresponding button is in the “CAN Broadcast” panel.

Available functions:
[Transport Mode] – disabling/enabling devices to reduce battery discharge.
[Disable Normal Communication] – disabling inter-module communication to prevent issues during reprogramming.
[Enable Normal Communication] – restoring inter-module communication.
[Clear All DTC’s] – clearing errors in all devices.

Standard diagnostic requests

Double-click the desired device in the main “VAG Commander” window. The following window opens:

This window provides the following diagnostic options:

Identification
Displays the module number and software coding.

SW/HW version
Displayed if supported by the device’s SW/HW version (including all sub-modules).

Extended Identification / VIN
Shows flash date, status, flash attempt count, manufacturing date, VIN.

Reading diagnostic codes
“Read DTCs” shows all current errors in the device (including all sub-modules). Errors may be displayed with freeze-frame data depending on device capabilities.

Clearing device errors
“Clear DTCs” — clears stored DTCs.

Measured values
Displays measured values in different groups. Groups can be changed manually using “+” / “-”.
“Scan all” generates a file with all groups.

Access level

“Security Access” — grants access at various security levels.

Standard access levels:
• (Login) – commonly used in immobilizer systems
• (CS) – used during adaptation of various units/parts
• (System Specific) – differs from the two above and from programming authorization.

User-defined access level:
Using “Request SEED” / “Send KEY”, the necessary access level can be established.

Adaptation

“Adaptation” — allows reading adaptation parameters. Enter the adaptation channel number and value, press “Test”, and if accepted — press “Save”.
“Scan all” creates a file with adaptation channels and values for all devices.

Device coding

“Coding” – allows changing the coding value of the device (including all sub-modules). In the example only the main module is coded; secondary devices are not supported.

Basic settings

“Basic settings” – enabling/disabling basic settings.

Device reset

“Reset” — device reboot. In some modes and devices this function may be unavailable.

Actuator tests

Two test types: “Selective” and “Sequential”.
In selective mode, test codes may be entered manually or selected from a list. After choosing the test, press “Start”.

Custom requests

This function allows manually sending diagnostic requests to the selected device. The example shows instrument cluster identification.

VIN programming

Not all modules and not all modes support VIN modification.

Upload/Download

Direct reading from the device memory. Function available if enabled in configuration.
In most cases, enabling memory read/write access is required.

Component Security

This special function works with non-standard units (and immobilizers) to program PIN, SKC, BGW, MAC.
Functions use CAN — TP2.0.

Active diagnostic session

The standard diagnostic session after connecting to a device is “89”. Users may request entry into different diagnostic sessions unavailable in session “89”.
Most diagnostic sessions require access permission.

Special functions

Special functions include odometer correction, security access code reading, EEPROM read/write, flash reading, etc.
Accessible from the main program window.

A special function is opened via double click or the “Open” button.

Special functions with the “cluster tool”

Establishes a diagnostic session with the instrument cluster using KWP2000 over TP2.0.

Functions available:
• Read odometer
• Change odometer
• Read/write EEPROM (immobilizer)
• Read login/PIN
• Read/write immobilizer data

The immobilizer access code differs from the instrument cluster code!

Supported models:
VW Golf5, VW Caddy, VW Touran, VW EOS, VW Individual, Skoda Octavia II, Skoda Scout,
Seat Leon, Seat Altea, Seat Toledo, Audi A3, Audi A6, Audi A8, Audi Q7, Audi Allroad.

For Audi A6, Audi A8, Audi Q7, Audi Allroad odometer reading is unavailable — only modification.
One minute after change, the program will display updated mileage.

ATTENTION: Some Audi A3 and A8 models have blocked access to these functions. This may be detected if incorrect readings appear after reading the odometer.
The instrument cluster can be restored by removing its fuse (Audi A8 — fuse №5).
Cause of blocking: diagnostics with improper devices.

ATTENTION: VAG K+CAN COMMANDER is designed for odometers in kilometers. Consider this when working with dumps or confirming current mileage (Audi Q7, Audi A6, Audi Allroad).

For some vehicles it is possible to read/program and synchronize immobilizer data (“Read/Write Immo data”).

Pressing “Read” retrieves immobilizer data. “Write” programs all HEX data if “update dump” is unchecked, or only part if it is checked.

The same data can be written to the ECU.

Special function “EZS Kessy CAN”

VAG K+CAN Commander connects to “EZS-Kessy / Entry And Start Authorization” via KWP2000 over TP2.0.
This function retrieves the PIN code from Kessy on Q7 and A6 models.

Several attempts may be required; after each attempt ignition must be cycled OFF/ON.

Special functions using “K-Line”

Select the instrument cluster / immobilizer type, then read/write EEPROM (odometer correction, PIN reading, etc.).
Communication is via K-Line (KWP1281 or KWP2000), regardless of configuration.

For most clusters EEPROM data is read automatically (odometer/immobilizer).

For Magneti Marelli clusters see Appendix A.

Sometimes selecting an incorrect type may lock the cluster until reset (fuse removal or battery disconnect).
Example: Bosch clusters will lock if “VDO66/VDO86/Motometer” type is selected.

Be very careful when selecting “Instrument Cluster Audi A4 BOSCH RB4 CRYPTO 2001+” or “Audi A4 BOSCH RBx”.
EEPROM can be read with either type, but wrong type + data changes may damage the cluster.

Correct type detection method:

Select “Audi A4 BOSCH RBx”.
Read EEPROM.
If odometer matches and login is accepted, the correct type is “RBx”; otherwise it is “RB4 CRYPTO”.

Most clusters require a reset after odometer change. You may try “Reset ECU”, or remove/replace the cluster fuse.

Special functions “ECU”

ECU functions include:
— Flash memory read/write
— Flash counters read/write
— EEPROM read/write
— Odometer correction (EDC15)
— PIN extraction
— Immobilizer ON/OFF (EDC15/ME7x)

Available after pressing “ECU” in the main window.

Before any operations, determine the ECU type!

Supported ECUs include:
VAG-EDC15x, VAG-ME7.1.1/7.5/7.8, Porsche 5.2/7.8, EDC16U1, EDC16U3x/CP, etc.

Example: 1.9 TDI — EDC15

Flash read/write notes:

For EDC15 remove fuse 11 to prevent communication with the cluster.
For ME7.x or Porsche ECU flash can be read like EEPROM — disable autodetection and set start address and length.
Always save the original flash!
For EDC16 flash is saved automatically in the “Flash” subfolder and can be used for recovery.
WARNING: The file is encrypted — do NOT write it directly! To restore flash after a failure you must enter boot mode and use “Custom Read/Write”.
Disable screen savers, power saving, and background apps during flash write.
Flash operations may take a long time. Weak batteries may discharge.

Special function “Kessy adaptation”

Used for adapting a new Kessy unit. Supported via CAN-TP2.0, K-KWP2000, and Porsche Cayenne.
Requires the old immobilizer security code (WFS) and the component security code of the new Kessy.

Special function “MMI TV activation”

Using this function you can change MMI speed limits or TV cutoff speed.

Supported vehicles include:
Audi A3/S3
Audi A6/S6 (MMI until July 2006)
Audi Allroad (MMI until July 2006)
Audi A8/S8 (MMI until July 2006)
Audi A6/S6 (MMI starting August 2006)
Audi Allroad (MMI starting August 2006)
Audi A8/S8 (MMI starting August 2006)

Rules:
— If the car is before 2007, try edition 1; if unsuccessful, wait 30 minutes with ignition ON and try edition 2.
— If the car is after 2007, try edition 2 first.

Special function “Custom memory access Download/Upload/ReadMemory”

Accessible from the special function list or main window.
Allows reading/programming memory in a device. Used for research or flash programming (e.g., internal flash of EDC16).
Example: reading part of flash EDC16CP.

Specify diagnostic session before operations.
In the example, session “86” is used.
To keep the current session, set it to “0”.

Special functions with “Airbag”

This function clears crash data from the Airbag module. Some modules also require clearing stored DTCs manually.
Standard DTC clearing will NOT remove crash data; EEPROM editing is required.

Supported modules include:
1C0 909 605 C, 8L0 959 655 A, 1J0 909 609, 6Q0 909 605 C/A/B, etc.

Special function “Key Learning”

Enter the immobilizer access code (retrieved using special functions) and the number of keys to learn.

General key learning procedure:

Enter access code and number of keys
Turn ignition ON (new or existing key)
Press “Learn”
Wait for “adaptation finished”
Remove the key and cycle ignition with remaining keys

For some vehicles, you must wait 5 minutes with ignition ON before learning (Fabia 2006+, Roomster 2006+, Superb 2007+, Polo 2006+, Ibiza 2006+).

If special steps are required, the software will notify you.

Some models allow learning aftermarket keys; some allow adding new keys while keeping old ones active.

Special function “Dump Tool”

This function can calculate access codes, correct odometer, etc.
It works using the EEPROM dump from the device.
After modifications, save the new file and write it into the device EEPROM.

VAG K+CAN CHECK

Self-diagnostic function for dongle and USB interface.

Two sections:
— Dongle check
— USB interface check

Pressing “Detect” in the dongle check section reads the dongle dump if the key is valid.
“Generate dump” saves dongle data.

In the USB interface check section, “Detect Interface” tests interface readiness, firmware version, and ID.
A K-Line test can also be performed (requires OBDII + 12V).
Results can be saved via “Generate dump” and sent to the manufacturer if there are detection problems.

VAG K+CAN UPDATE REQUEST

This function updates the VAG K+CAN software to resolve issues listed in the “Troubleshooting” section.

Catalog