They ought to be, but if you take them apart and look inside they sometimes fit almost any value resistor in any place (for example the k-line pullup varies a lot - hmm), its not exactly uncommon for people to have to fix their tool before use. Its also worth bearing in mind that mass produced clones like the KWP2000 arent all made equal. If this is whats causing greif here then Id recommend trying a different (preferably not a chinese) type of OBD tool. In these instances you get an ecu not found or unable to establish communications etc type error, despite having retreived the ecu details. It was a while ago but I seem to remember you have to power the ECU then wake it up by touching another pin, not entirely sure but I coud look it up again. I would also try the BMW program on the KWP as well as the Rover one to see if it can read it that way.ĭid you succeed reading it Im in the same situation with the identical error. You need to remember that the battery voltage must be kept well up, so you will need a charger or booster on the battery whilst reading or writing to the ECU, something that can deliver 20-30 amps whilst you have the ignition on. #Kwp2000 usb to serial driver install#You can install the 32bit version beside the 64bit (make sure to put on different partition) and then you will have both and it will just work fine. #Kwp2000 usb to serial driver license#I recommend to download the same version of Win7 what you have but only in 32bit and install then use your license key. #Kwp2000 usb to serial driver windows 7#You can try in virtual XP (free for Windows 7 professional and ultimate just need to download from Microsoft) but I doubt that it will work as it is on 64bit base too. #Kwp2000 usb to serial driver driver#I dont know the software but if there is a part you can exit and launch, you could try running that part as Administrator (right click, run as administrator) Failing that, you could try running that part in a compatibility mode (right click and select properties to edit) and as administrator.īut these are both last ditch desperate efforts I fear because I suspect the driver has not been updated for Windows 7. The VM needs to communicate with Windows 7, and then Windows 7 with your KWP2000. Ive got the gut feeling the software cant 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. So Im wondering if anyones 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. 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. #Kwp2000 usb to serial driver drivers#So after a bit of Googling i found a site that recommended downloading the drivers directly from the FDTI site itself ( ) and modifying the.inf files to include the HardwareIds of the KWP2000 device thats been found.Įxcellent 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 ECUs. For a better experience, please enable JavaScript in your browser before proceeding.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |