The K+DCAN cable functions the same as the K-Line cable but it comes with an added feature to use the cable on BMW models from 2007 to the newer models. It normally has a switch to flip between the older models with the K-Line interface (1998-2007) and the newer models with the DCAN interface (2007-2018+). It can also be used with INPA, ISTA, ISTA+ (Rheingold or ISTA/D), DIS, EDIABAS, NCS Expert, Progman, Carly for BMW, and many other BMW diagnostic and coding software.

Solution: msflxgrd.ocx under c:\Ediabas\bin must be registered. To do this, select “Start” “Run…” and execute regsvr32: \ediabas\bin\msflxgrd.ocx in the window and confirm with “OK“. The following must be entered for Windows XP: “regsvr32 c:\ediabas\bin\ msflxgrd.ocx“ After driver installation, the next process is to make sure that the COM port settings in the Device Manager are properly configured. Here’s the process on how to do it. A: If you don‘t plan to use the cable on any cars that have DCAN(2007+) then you can pop open the case and solder a jumper between them. When you do this the DCAN functionality will no longer work though.A: You only need to run it when you are switching between modes. If you run it the first time you connect to a DCAN car, your computer will retain the settings. What is the reference on the small transistor, which was replaced on the white board with the big one? Perhaps the specs are out of limit... Capable of flashing: MS41, MS42 MS43, MS45, MSS52, MSS54, MSS54HP, MSS60, MSS65, MSS70, MSV70, MSD80, MSD81 DMEs (and corresponding modules) (E38, E39, E46, E83, E85, etc.) I verified that both pins 7 and 8 had voltage and that the connection from the chassis wires to the obd plug under the dash were solid. Tested and latest cable chip updates in house with highest level of reliability and ECU/Module compatibility! (As pictured above)

Thanks for the reply. I already read and tried everything. The cable consists of a microcontroller that implements the k+dcan protocol and has a rs232 interface for pc communication. This goes straight to the FTDI rs232 to usb converter. This is working fine, at least for me. The problem is with the communication to the microcontroller (atmel chip i think). I asume it is powered by the obd2 port and some component on the pcb is broken. SGBDs that begin with “_” (e.g. _LWS5), contain jobs that are only intended for development (e.g.: writing the ident data). These SGBDs are not used in production or in customer service. Installed the USB cable and set the COM port to 1. Latency is set to 1ms. There is no option to use FIFO buffer. Start Inpa using Inpaload.exe in C:\Inpa\Bin or alternatively C:\EC-Apps\Inpa\Bin or use Start All Programs EDIABAS INPA ELDI NCS NFS INPA(_.IPO) to start the general reworking programme. This corresponds to calling Inpaload.exe under smuc0900\sg\Inpa\Bin or alternatively C:\Inpa\Bin. When installing Windows 10, I suggest disabling as many of its controversial data collection tools as possible… caveat emptor !!Use an adapter (such as the one sold by One Stop Electronics) that internally bridges pins 7 & 8 or… this will create a new C:\Rheingold\Ediabas\BIN directory containing all Ediabas binaries + DLLs + INI files BMW INPA is used for BMW diagnostic & coding software, working with INPA/Ediabas K+DCAN USB interface for E-Chassis vehicles from 1998 to 2008. I verified that both pins 7 and 8 had voltage and that the connection from the chassis wires to the OBD plug under the dash was solid. Q: Is it necessary to do so every time I want to use DCAN or is the interface staying in DCAN mode once I ran DCAN.exe?

The reasons being that on DCAN cars one pin is used for a ethernet connection and the other to the K data line – on K line cars, both pins are connected to K data lines and that creating a switch mode circuit would cost more than the interface is worth. The 2 most sensible options are both hardware-related:- Solution: msflxgrd.ocx under c:Ediabasbin must be registered. To do this, select “Start” “Run…” and execute regsvr32: ediabasbinmsflxgrd.ocx in the window and confirm with “OK“. The following must be entered for Windows XP: “regsvr32 c:ediabasbin msflxgrd.ocx“Solution:msflxgrd.ocx under c:\Ediabas\bin must be registered. To do this, select “Start”“Run…” and execute regsvr32: \ediabas\bin\msflxgrd.ocx in the window and confirm with “OK“. The following must be entered for Windows XP: “regsvr32 c:\ediabas\bin\ msflxgrd.ocx“ For Coding, you need different Tools, NCS Expert / SP-Daten for E-Series and E-Sys / PSdZData for F-Series.