- Download Windows 7 Home Premium
- Kwp2000 Plus Drivers Windows 7 Download
- Download Windows 7 Free Software
![Free Free](https://sc01.alicdn.com/kf/HT1vKAbFPlcXXagOFbXe/221087141/HT1vKAbFPlcXXagOFbXe.jpg)
post #1 of 18 (permalink) Old06-01-2012, 21:38Thread Starter
Download Windows 7 Home Premium
https://mdheavy255.weebly.com/download-driver-cdma-1x-usb-wireless-modem.html. https://mdheavy255.weebly.com/download-wasapi-driver-windows-7.html. Does anyone have windows 7 drivers or do you have to use XP?
Here you see the selected files to the download. KWP2000 Plus ECU REMAP Flasher driver (Q00553) Size: 14.4 MB; The requested file is located on an external webpage. Kwp2000 plus driver download - File size: 2655 Kb Date added: 26 jun 2008 Price: Free Operating system: Windows XP/Vista/7/8 Total downloads: 924 Downloads last week: 277 Product ranking: 70/100 DOWNLOAD NOW Kwp2000 plus driver download Direct Links UltraShare 4shared EasySend Dropbox FastShare FileDropper MediaFire MegaFileUpload YourFileLink. https://mdheavy255.weebly.com/toshiba-satellite-c660-drivers-windows-xp-download.html. Jun 01, 2012 The VM needs to communicate with Windows 7, and then Windows 7 with your KWP2000. The driver has not been updated for. KWP2000 Plus Software Installation and Operating Instructions. Direct windows to the folder where you installed the driver package.
![Kwp2000 Plus Driver Download Windows 7 Kwp2000 Plus Driver Download Windows 7](/uploads/1/2/6/4/126454902/985948139.png)
Registered User
Kwp2000 Plus Drivers Windows 7 Download
Car: MG ZTT
Download Windows 7 Free Software
I've got hold of one of those KWP2000+ devices off ebay with the aim to read my ECU and get the map tweaked
My laptop is running 64bit Windows 7
On the disk came some new drivers for the FDTI chipset the KWP runs (CDM20814_Setup.exe)
So with those installed i tried to update the drivers for the 'USB to Serial device' that appeared when i plugged in the KWP2000+ box, however it didn't result in any success. ie no suitable drivers could be found.
So after a bit of Googling i found a site that recommended downloading the drivers directly from the FDTI site itself (http://www.ftdichip.com/Drivers/D2XX.htm) and modifying the .inf files to include the HardwareId's of the KWP2000+ device that's been found.
so the hardware id's i found on the device properties were
USBVID_0403&PID_FAD8
USBVID_0403&PID_FAD8&REV_0400
So i then edited the ftdibus.inf & ftdiport.inf files
ftdibus.inf
[FtdiHw]
%USBVID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB VID_0403&PID_6001
%USBVID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6010&MI_00
%USBVID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6010&MI_01
%USBVID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_00
%USBVID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_01
%USBVID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_02
%USBVID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_03
%USBVID_0403&PID_6014.DeviceDesc%=FtdiBus.NT,USB VID_0403&PID_6014
%USBVID_0403&PID_FAD8&REV_0400.DeviceDesc%=FtdiBu s.NT,USBVID_0403&PID_FAD8&REV_0400
%USBVID_0403&PID_FAD8.DeviceDesc%=FtdiBus.NT,USB VID_0403&PID_FAD8
[FtdiHw.NTamd64]
%USBVID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64 ,USBVID_0403&PID_6001
%USBVID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6010&MI_00
%USBVID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6010&MI_01
%USBVID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_00
%USBVID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_01
%USBVID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_02
%USBVID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_03
%USBVID_0403&PID_6014.DeviceDesc%=FtdiBus.NTamd64 ,USBVID_0403&PID_6014
%USBVID_0403&PID_FAD8&REV_0400.DeviceDesc%=FtdiBu s.NTamd64,USBVID_0403&PID_FAD8&REV_0400
%USBVID_0403&PID_FAD8.DeviceDesc%=FtdiBus.NTamd64 ,USBVID_0403&PID_FAD8
[Strings]
Ftdi='FTDI'
DESC='CDM Driver Package - Bus/D2XX Driver'
DriversDisk='FTDI USB Drivers Disk'
USBVID_0403&PID_6001.DeviceDesc='USB Serial Converter'
USBVID_0403&PID_6010&MI_00.DeviceDesc='USB Serial Converter A'
USBVID_0403&PID_6010&MI_01.DeviceDesc='USB Serial Converter B'
USBVID_0403&PID_6011&MI_00.DeviceDesc='USB Serial Converter A'
USBVID_0403&PID_6011&MI_01.DeviceDesc='USB Serial Converter B'
USBVID_0403&PID_6011&MI_02.DeviceDesc='USB Serial Converter C'
USBVID_0403&PID_6011&MI_03.DeviceDesc='USB Serial Converter D'
USBVID_0403&PID_6014.DeviceDesc='USB Serial Converter'
USBVID_0403&PID_FAD8.DeviceDesc='Serial To Kline Interface'
USBVID_0403&PID_FAD8&REV_0400.DeviceDesc='Serial To Kline Interface'
SvcDesc='USB Serial Converter Driver'
ClassName='USB'
I then updated the drivers on the device pointing them at these edited drivers and bingo they installed OK.
Excellent i thought!!!
However I tried connecting the device to the car but i just keep getting Kick Not Found! error message in the window that opens when you choose the Rover Bosch EDC15C DDE option from the list of ECU's.
The Green light comes on the box when connected to the USB cable and when its connected to the car aswell the red VBAT light comes on as well, so it would appear there is connectivity from both ends.
So I'm wondering if anyone's had any luck getting these to work?
Questions
a) If people have got it to work does the 'Kick Not Found' message disappear only when the device is connected to the ECU?
b) Which COM Port is your USB to Serial Device configured as? (mine was initially COM5 but i changed it to COM1 but with no luck.
I've got the gut feeling the software can't communicate with the KWP2000+ box rather than it failing to communicate with the car, but i could be wrong!
thanks in advance for any help
Matt
My laptop is running 64bit Windows 7
On the disk came some new drivers for the FDTI chipset the KWP runs (CDM20814_Setup.exe)
So with those installed i tried to update the drivers for the 'USB to Serial device' that appeared when i plugged in the KWP2000+ box, however it didn't result in any success. ie no suitable drivers could be found.
So after a bit of Googling i found a site that recommended downloading the drivers directly from the FDTI site itself (http://www.ftdichip.com/Drivers/D2XX.htm) and modifying the .inf files to include the HardwareId's of the KWP2000+ device that's been found.
so the hardware id's i found on the device properties were
USBVID_0403&PID_FAD8
USBVID_0403&PID_FAD8&REV_0400
So i then edited the ftdibus.inf & ftdiport.inf files
ftdibus.inf
[FtdiHw]
%USBVID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB VID_0403&PID_6001
%USBVID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6010&MI_00
%USBVID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6010&MI_01
%USBVID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_00
%USBVID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_01
%USBVID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_02
%USBVID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.N T,USBVID_0403&PID_6011&MI_03
%USBVID_0403&PID_6014.DeviceDesc%=FtdiBus.NT,USB VID_0403&PID_6014
%USBVID_0403&PID_FAD8&REV_0400.DeviceDesc%=FtdiBu s.NT,USBVID_0403&PID_FAD8&REV_0400
%USBVID_0403&PID_FAD8.DeviceDesc%=FtdiBus.NT,USB VID_0403&PID_FAD8
[FtdiHw.NTamd64]
%USBVID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64 ,USBVID_0403&PID_6001
%USBVID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6010&MI_00
%USBVID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6010&MI_01
%USBVID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_00
%USBVID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_01
%USBVID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_02
%USBVID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.N Tamd64,USBVID_0403&PID_6011&MI_03
%USBVID_0403&PID_6014.DeviceDesc%=FtdiBus.NTamd64 ,USBVID_0403&PID_6014
%USBVID_0403&PID_FAD8&REV_0400.DeviceDesc%=FtdiBu s.NTamd64,USBVID_0403&PID_FAD8&REV_0400
%USBVID_0403&PID_FAD8.DeviceDesc%=FtdiBus.NTamd64 ,USBVID_0403&PID_FAD8
[Strings]
Ftdi='FTDI'
DESC='CDM Driver Package - Bus/D2XX Driver'
DriversDisk='FTDI USB Drivers Disk'
USBVID_0403&PID_6001.DeviceDesc='USB Serial Converter'
USBVID_0403&PID_6010&MI_00.DeviceDesc='USB Serial Converter A'
USBVID_0403&PID_6010&MI_01.DeviceDesc='USB Serial Converter B'
USBVID_0403&PID_6011&MI_00.DeviceDesc='USB Serial Converter A'
USBVID_0403&PID_6011&MI_01.DeviceDesc='USB Serial Converter B'
USBVID_0403&PID_6011&MI_02.DeviceDesc='USB Serial Converter C'
USBVID_0403&PID_6011&MI_03.DeviceDesc='USB Serial Converter D'
USBVID_0403&PID_6014.DeviceDesc='USB Serial Converter'
USBVID_0403&PID_FAD8.DeviceDesc='Serial To Kline Interface'
USBVID_0403&PID_FAD8&REV_0400.DeviceDesc='Serial To Kline Interface'
SvcDesc='USB Serial Converter Driver'
ClassName='USB'
I then updated the drivers on the device pointing them at these edited drivers and bingo they installed OK.
Excellent i thought!!!
However I tried connecting the device to the car but i just keep getting Kick Not Found! error message in the window that opens when you choose the Rover Bosch EDC15C DDE option from the list of ECU's.
The Green light comes on the box when connected to the USB cable and when its connected to the car aswell the red VBAT light comes on as well, so it would appear there is connectivity from both ends.
So I'm wondering if anyone's had any luck getting these to work?
Questions
a) If people have got it to work does the 'Kick Not Found' message disappear only when the device is connected to the ECU?
b) Which COM Port is your USB to Serial Device configured as? (mine was initially COM5 but i changed it to COM1 but with no luck.
I've got the gut feeling the software can't communicate with the KWP2000+ box rather than it failing to communicate with the car, but i could be wrong!
thanks in advance for any help
Matt