BMW K+CAN / K+DCAN Connection Guide
1. What is the BMW K+CAN / K+DCAN cable
This is a universal diagnostic cable for BMW E-series vehicles.
It supports two communication protocols:
K-Line – for older BMWs up to ~2007
D-CAN (CAN interface) – for models after 2007
The adapter has a K-Line ↔ D-CAN switch - make sure it is set correctly depending on the car.
2. BMW Standard Tools Software
The package includes:
EDIABAS – the communication layer. All diagnostic programs (INPA, NCS, etc.) communicate with the car via EDIABAS.
INPA – diagnostics, reading error codes, test functions.
NCS Expert – coding of control modules.
WinKFP – flashing/programming of modules.
Recommendation: install a pre-configured BMW Standard Tools package where paths and settings are already properly configured.
3. Computer Requirements
Recommended: Windows 7 x64, but works on Windows 10/11 as well.
Sometimes you may need to disable driver signature enforcement to install adapter drivers.
4. Driver Installation for the Cable
Connect the adapter to a USB port.
If Windows does not install the driver automatically:
download and install FTDI VCP (Virtual COM Port) drivers.
After installation, the adapter should appear as:
USB Serial Converter
USB Serial Port (COMx)
Common issue:
If the device installs as CH340, your adapter uses a different chip - you will need CH340 drivers.
5. Configuring the COM Port
Why is this important?
EDIABAS and INPA use a specific COM port for communication, and it must match the one used by the adapter.
Steps:
Open Device Manager → Ports (COM & LPT).
Open USB Serial Port properties.
In the Advanced tab:
Set the port to COM9 (or any COM1–COM9).
Set Latency Timer = 1 ms.
Important: avoid using COM10 or higher - some EDIABAS versions cannot detect these.
6. Configuring EDIABAS
File obd.ini
Path: C:\EDIABAS\Bin\obd.ini
Check the line:
Port=Com9
This must match the COM port you assigned.
File ediabas.ini
Path: C:\EDIABAS\Bin\ediabas.ini
Main parameters:
Interface=STD:OBD
TcpPort=6801
Note: for ENET cables (F/G series), the interface must be OTHER:ENET.
For K+D-CAN keep STD:OBD.
7. Connecting to the Car
Plug the adapter into the vehicle’s OBD port.
Turn the ignition ON (position 2).
Launch INPA.
In the top-right corner you should see:
Battery = ON
Ignition = ON
If:
Battery is ON, Ignition is OFF → issue with the K-line contact.
Both are OFF → COM port mismatch, driver issue, or defective cable.
Tip: For older cars (before ~2007), you may need a 7–8 pin bridge inside the adapter.
8. Software-Specific Connection Notes
BMW DIS (Yellow Head/GT1)
DIS uses a virtual machine and the IFHSrv32 communication bridge.
Connection sequence:
Run ifhsrv32.exe (must show “running”).
Start DiagHead.
In VMware, configure the network as Host-only.
Common issue:
DIS cannot connect → IFHSrv32 was not running.
Rheingold ISTA+
In settings:
VCI Config → EDIABAS Standard Settings
ISTA uses EDIABAS for K+D-CAN communication, so ensure:
COM port is configured correctly
Interface=STD:OBD
Tip: Run ISTA as administrator - otherwise it may not detect EDIABAS.
9. Vehicle Compatibility
D-CAN support starts around 03/2007:
E60/E61 LCI
E90/E91/E92/E93
E83 facelift
E70/E71
E87 facelift
and other models equipped with CAS2/CAS3 modules.
For older cars using K-Line:
you need a 7–8 pin bridge
or
a cable with a K-Line / D-CAN switch.
10. Antivirus and Windows Protection
DIS and some BMW tools may be flagged as suspicious.
You may need to temporarily disable antivirus or add exceptions.
Windows 10 SmartScreen can block older executable files.
11. Common Errors and Fixes
1. INPA does not detect ignition
missing pin 8 (K-Line cars)
faulty cable
incorrect COM port
Latency Timer not set to 1 ms
2. INPA opens but modules do not respond
OBD pin issues in the car
wrong interface in ediabas.ini
damaged K-line for a specific ECU
3. ISTA cannot detect the car
incorrect EDIABAS path
another program is using the COM port
ISTA not run as administrator
4. DIS cannot connect
IFHSrv32 not running
incorrect VMware network configuration