Some of these do not work in windows 7 - do you have a link to the 1 that you bought?

 

this is the one

http://www.ebay.co.uk/itm/120836311612?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649


bugger i've just seen at the bottom of the ad in small writing it says "does not work with windows 7"

that'll be why then?!? doh!

 

right well i installed a windows XP virtual machine on my laptop, however i'm still getting the Kick Not Found messgae when i try and read the ecu

any ideas?

 

Win7

It does work with Windows 7 but only the 32bit version, I have configured my laptop as a dual boot (64 & 32bit) just to support KWP2000 and Digimoto (diagnostic)

 

nicpy has got it in one
autodata also only works with win7 32 bit
i found out the hard way and also had to install a dual boot system , works with lots of diagnostic tools now !!!!!

 

but running windows XP in a VM should work though shouldn't it?

 

You're right that its a software problem but your solution probably won't work.

The VM needs to communicate with Windows 7, and then Windows 7 with your KWP2000.

I don't 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. But these are both last ditch desperate efforts I fear because I suspect the driver has not been updated for Windows 7.

* shrug *

 

Ive tried running it as administrator and also in
compatibility mode but all to no avail

I'm going to try it on my mates xp laptop and see how we get on.

 

Any of these "old" tweak tools are not working in 64bit environment. 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. I recommend to download the same version of Win7 what you have but only in 32bit and install then use your license key. This way you still legal and genuine. 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.

 

cheers for the replies

i actually remembered my netbook was running xp so i installed the drivers on that fired up the application and bingo no "Kick Not Found!" error message

So i then went out and connected it up to the car

hit the data button, and it read back some info from the ECU displayed 3 lines of codes. result i thought!!

However i then clicked the Read button and the app said something like "waking ecu please wait" but would then return an error message of "Internal Hardware Error"

I've tried it repeatedly including changing the Speed from Fast to Slow but to no avail.

Any ideas? or is just not meant to be

 

cheers for the replies

i actually remembered my netbook was running xp so i installed the drivers on that fired up the application and bingo no "Kick Not Found!" error message

So i then went out and connected it up to the car

hit the data button, and it read back some info from the ECU displayed 3 lines of codes. result i thought!!

However i then clicked the Read button and the app said something like "waking ecu please wait" but would then return an error message of "Internal Hardware Error"

I've tried it repeatedly including changing the Speed from Fast to Slow but to no avail.

Any ideas? or is just not meant to be

Hmm! As I recall you have a diesel, so it should be able to read the ECU map from the DDE4.0 (EDC15C4) system with no problem.

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. This might be why it is bonging out.

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.

Otherwise it should like it could be a duff KWP2000.

Regards, Rob.

 

Some years have passed but...

Did you succeed reading it? I'm in the same situation with the identical error.

 

From what I can see, the KWP200 software, like many other things, will not work with 64 bit operating systems, some won't work with anything later than Windows XP, some won't even work with NT based operating systems.

I have found that the KWP2000 software works only with an older laptop running Xp that I have, having kept this laptop just for some tuning software that I have.

It may work with a Win 7 32 bit system however, but deffo NOT 64 bit versions.

 

works ok with windows Vista 32 bit..

 

...and that's the key, it must be 32 bit, none of the 64 bit systems support it!

 

I've succesfully read and written back to the EDC15C4 on the bench using a KWP2000+ on winXP, but not managed it in the car. I suspect it isn't a battery related issue. I get the same symptoms of waking the ECU and handshaking but not managing to read an image.

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 use a much more modern (genuine, not chinese!) version of the tool by the same developer as the kwp2000 for remapping cars, and I'm aware of a bug in the way security keys are handled for these ecu's which gives the appearance of being able to communicate with the ECU (get ID etc) but will not be able to authorise itself for access for reading/memory writing etc.

In these instances you get an 'ecu not found' or 'unable to establish communications' etc type error, despite having retreived the ecu details.

If this is whats causing greif here then I'd recommend trying a different (preferably not a chinese!) type of OBD tool. I use an alternative tool to do these by OBD.

It's also worth bearing in mind that mass produced clones like the KWP2000 aren't all made equal. 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!), it's not exactly uncommon for people to have to 'fix' their tool before use. It's also worth checking out the soldering too as it can sometimes be quite shocking and that can give weird issues.

Given the fact bad communications can leave a car ecu fully erased and unresponsive, I do have to end this post with an old fashioned warning of being careful:

Whilst permament damage to an ecu is unlikely (they can be restored), programming failures can render an ecu unresponsive (no engine start and no OBD communications at all) and you need more than a KWP2000 to do the restore operation on them (at this stage no OBD tool can effect a repair, all work has to be done at a PCB level).