- K+dcan Utility 2.0 Download Free
- K+dcan Utility 2.0 Download Full
- K Dcan Utility 2.0 Download Utorrent
If your cheap BMW INPA K+DCAN USB interface with FTDI chip failed to install drivers or the system prompt cannot locate the drivers. Here is a little write-up on how to fix it.
Disclaimer:
I am using Windows 8.1 system. No sure if it works on yours. You are on your own risk.
Pre-installation caution:
Here are the INPA driver & software, free download links. If the driver/software is working, then ignore the next part. Otherwise take a look at the following part for reference.
INPA Driver: http://www.obd2vip.com/download/inpa-driver.zip（Close antivirus software or set your browser to download success）
INPA software: http://www.obd2vip.com/download/inpa-2.zip
Procedure:
Ran the K+DCAN Utility 2.0 - set the COM port to COM1 - unplugged and plugged in my K+DCAN cable since the help says you can change the mode only within the 1st minute after plugging it in while the LED light on the cable is on - while the light on the cable is on, pressed the 500 kbit/s D-CAN & PT-CAN button and output was. K Dcan Utility 2.0 Download Pc. I use the DOS version of the DCAN utility. As mentioned if you only use the adapter on the e39, run the utility once and set the adapter to K CAN and leave it at that. With these K+DCAN cables there are two subtle different versions, one with pin. Also make sure to download / open and read the Application note regarding the backward compatibility of older, with K-Line equipped vehicles. Q: I have an rather new BMW with OBD2 Connector which uses D-CAN can't I use a simple (cheap) Interface?
1. Open your Device Manager. Control Panel–Hardware & Sound–Device Manager.
2. Connect the INPA K+DCAN cable with computer/PC-Double click
3. Locate USB Serial Converter->DetailsDropdown Menu->Hardware IDs. The PID number is the one you want. Will most likely be 0000.
4. Download CDM v2.08.30
http://www.ftdichip.com/Drivers/CDM/CDM%20v2.08.30%20for%20Windows%208.1.zip
5. Disable “Driver signature verification” Settings–Change PC Settings–Recovery–Advanced Startup–Restart.
This will restart your PC to Advanced settings. From there: Troubleshoot–Advanced Options–Startup Settings–Restart–F7
Follow these picture guides:
Your PC will then restart with signature verification disabled. You are now able to edit the INPA drivers.
6. Unzip the Drivers file that you just downloaded and open up
7. Open ftdibus.inf
8. Replace every PID_6001 with PID_0000 to match your hardware ID. Scan through the whole document. Then save it.
9. Then find ftdiport.inf. Do the same to ftdiport.inf
10. Back in your Device Manager double click on your OBDII cable again.
Locate USB Serial Convertor Properties->Driver->Update Driver-> Browse my computer.
Locate your driver and install. You will need to install it for both USB Serial Converter and Ports & COM.
11. Setup INPA cable as normal and run INPA software.
It seems that the white FTDI chip INPA cables have to be manually put into D-CAN mode. This file will take care of that. It is normal for the LED to go out.
http://www.mediafire.com/download/35fnrnd3q3dvf3w/D-CAN.exe
If you put the cable into DCAN mode, the LED goes off, and it says there is no adapter connected. Please connect it to the car and run the DCAN mode.
Who Viewed This Article Also Views:
This is the solution of error on K+DCAN INPA cable “vehicle could not be identified”
Error:
OS: Windows 8.1
K+DCAN Cable: http://www.obd2diy.fr/wholesale/bmw-inpa-k-can.html
Rheingold Standalone Version: 3.52.16
SQliteDBs : 3.52.12
installation process:
Installed Ediabas 7.3.0
Installed Java
Installed vcredist_x86_2010
Installed vcredist_x86_2013
Installed vs90_piaredist
Installed net framework 4.5.2 or higher
Plugged K+DCAN Cable into laptop and let it install the latest drivers on its own
Device Manager -> USB serial port properties -> port settings -> advanced -> change port number to com9 and latency timer to 1
Opened C:EDIABASBINEDIABAS.INI with notepad and checked for “Interface = STD:OBD” and in TCP settings set “Port=6801”
Opened C:EDIABASBINOBD.INI with notepad and checked for “Port=com9”
Installing Rheingold:
Unpacked to C: Rheingold, unzip and copy SQLiteDBs to Rheingold SQLiteDBs
Run C: Rheingold TesterGUI bin Release ISTAGUI.exe. If it asks for a license, copy from the file License.txt which is in the Rheingold directory. Enter the number 1 in the ISIS, ignore the error.
Ran INSTAGUI.exe
VCI Config tab and selected Ediabas standard settings (ediabas.ini)
Selected operations and then read out vehicle data and selected complete identification
Tested on 3 different cars:
2004 BMW 330ci
2010 BMW 328i
2008 BMW 328i
The same error:
The vehicle could not be identified. Please check the access to the vehicle and check whether the testing-analysis-diagnosis has been activated.
Solution:
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.
The main ISTA/D archive deploys a Rheingold directory which already contains a minimal Ediabas install (C:RheingoldEdiabas), 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.
The problem is then to know which of both version is actually used by ISTA/D when it starts.
Here’s what you can try :
– uninstall supplemental Ediabas altogether (right click/uninstall on Ediabas MSI file if it’s the one that’s currently installed)
– in your main ISTA/D deployment directory, rename C:RheingoldEdiabasBIN to C:RheingoldEdiabasOLD_BIN
– reinstall Ediabas MSI package, changing its install path to C:RheingoldEdiabas during installation
– this will create a new C:RheingoldEdiabasBIN directory containing all Ediabas binaries + DLLs + INI files
– the rest of Ediabas package (docs, helper files, sim files, etc ….) will be installed in C:EDIABAS as usual
– modify EcuPath parameter inside C:RheingoldEdiabasBINEDIABAS.INI to C:RheingoldEcu
Then, you can redo your other settings :
– C:RheingoldEdiabasBINEDIABAS.INI
Interface = STD:OBD
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).
K+dcan Utility 2.0 Download Free
– C:RheingoldEdiabasBINOBD.INI
[OBD]
Port=Com9
Hardware=OBD
You also don’t have to care about ifhsrv32, which is a network proxy for Ediabas. 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.
Guess it’s not the classic case for DIYers
K+dcan Utility 2.0 Download Full
Hope this will help solve your situation.
Original:(Solved) K+DCAN cable INPA: vehicle could not be identified