Bmw k dcan usb driver#
PT-CAN, K-CAN-fully switchable speed of magistral CAN - ou can diagnose driver without any car Protocol "BMW OBD interface" for older cars:ġ)from 1995 to 1998 (don't need K-line). (Diagnose, coding / programming).ġ)Fast magistral D-CAN and PT-CAN (500 kbit/s)ģ)Standard BMW protocol (BMW OBD interface).
![bmw k dcan usb bmw k dcan usb](https://ae01.alicdn.com/kf/HTB1sW4KXOnrK1RjSsziq6xptpXaY/New-Arrival-For-BMW-INPA-K-DCAN-USB-OBD2-Cable-For-BMW-INPA-Ediabas-K-Line.jpg)
Interface USB OBD2 for BMW - INPA/Ediabas - K+DCAN allows full diagnostic of BMW from 1998 (all functiosn as in OMNITEC interface). I'm not familiar with this.īMW INPA / Ediabas K+DCAN USB Interface D-CAN OBD OBD2 with 20 PIN My data link connection has 20 pin holes with 12 connections.Īlso on this thread I would like to learn what this thing can do for me. I ask the vendor it it would work on my Z3 but didn't get a reply. I need to make sure it will work on my 1998 Z3 roadster 2.8L prior to ordering. Hope this will help solve your situation.I want to order this soon. Guess it’s not the classic case for DIYers It’s used when ISTA (or any BMW diag software needing Ediabas to connect to car), is run from another PC than the one where Ediabas itself is installed, and “discusses” remotely with it over a network. You also don’t have to care about ifhsrv32, which is a network proxy for Ediabas. You don’t care about anything TCP or Ethernet here as you’ll be using an USB K+DCAN cable if I’m correct (=> nothing to do with a network connection). – modify EcuPath parameter inside C:\Rheingold\Ediabas\BIN\EDIABAS.INI to C:\Rheingold\Ecu – the rest of Ediabas package (docs, helper files, sim files, etc ….) will be installed in C:\EDIABAS as usual – this will create a new C:\Rheingold\Ediabas\BIN directory containing all Ediabas binaries + DLLs + INI files
Bmw k dcan usb install#
– reinstall Ediabas MSI package, changing its install path to C:\Rheingold\Ediabas\ during installation – in your main ISTA/D deployment directory, rename C:\Rheingold\Ediabas\BIN to C:\Rheingold\Ediabas\OLD_BIN – uninstall supplemental Ediabas altogether (right click/uninstall on Ediabas MSI file if it’s the one that’s currently installed) The problem is then to know which of both version is actually used by ISTA/D when it starts.
Bmw k dcan usb archive#
The main ISTA/D archive deploys a Rheingold directory which already contains a minimal Ediabas install (C:\Rheingold\Ediabas), and it’s that install that ISTA/D is configured to use, so the supplemental Ediabas install (from the Ediabas 7.3.0 MSI file) comes as a duplicate in my understanding, but adds some features as it’s a complete Ediabas version. I think you’ve installed the same kind of ISTA/D standalone package, so here’s what I’ve learnt wandering through the various directories. Please check the access to the vehicle and check whether the testing-analysis-diagnosis has been activated. Selected operations and then read out vehicle data and selected complete identification VCI Config tab and selected Ediabas standard settings (ediabas.ini) Enter the number 1 in the ISIS, ignore the error. If it asks for a license, copy from the file License.txt which is in the Rheingold directory.
![bmw k dcan usb bmw k dcan usb](https://www.dhresource.com/0x0/f2/albu/g7/M00/1F/91/rBVaSluHrEmAFR7oAAG8iT-UjWs835.jpg)
Run C: \ Rheingold \ TesterGUI \ bin \ Release \ ISTAGUI.exe. Unpacked to C: \ Rheingold, unzip and copy SQLiteDBs to Rheingold \ SQLiteDBs \ Opened C:\EDIABAS\BIN\OBD.INI with notepad and checked for “Port=com9” Opened C:\EDIABAS\BIN\EDIABAS.INI with notepad and checked for “Interface = STD:OBD” and in TCP settings set “Port=6801”
Bmw k dcan usb serial#
Plugged K+DCAN Cable into laptop and let it install the latest drivers on its ownĭevice Manager -> USB serial port properties -> port settings -> advanced -> change port number to com9 and latency timer to 1
![bmw k dcan usb bmw k dcan usb](https://alitools.io/en/showcase/image?url=https%3A%2F%2Fae01.alicdn.com%2Fkf%2FH914e539605aa4523a05dba269b4150d2n.jpg)
This is the solution of error on K+DCAN INPA cable “vehicle could not be identified”