Hondata

Spunkster wrote:What directory are you pointing it to when you install the drivers?

C:\Program Files\KManager -- the directory where I installed KManager.

JohnyBlaze: Can you check again in the Device Manager what the Device Instance ID is? It should be something like USB\VID_0403&PID_F5F8\HD1000

We're going to release a beta version in the next day which has a function to test/repair the USB drivers.

Part of the problem is that Windows does its best to stop the drivers from working, at multiple levels. You really need to uninstall all the hidden USB device drivers, otherwise Windows, in its infinite wisdom, will keep loading a previous old driver when you plug in the KPro, no matter what you tell it to do.

To remove the unused hidden device drivers, you first need to add an environment variable DEVMGR_SHOW_NONPRESENT_DEVICES with a value 1 If you don't know how to do this, then don't go any further because you'll get in trouble. Reboot, then start the Device Manager. Check 'Show Hidden Devices'. Now you may notice that there are many more hardware devices, but some have a greyed out icon (it can be hard to spot). Anyhow, there are devices where drivers are installed but the hardware is not present. Under USB there is probably a bunch of 'Hondata K-Series ECU' entries.

Make sure the KPro is not plugged in, then first use the Control Panel 'Add/Remove Programs' to uninstall all the Hondata USB Drivers, and anything from FTDI or any USB/Serial devices. Then in the Device Manager, uninstall the drivers for anything that looks like an ECU or USB/Serial.

Reboot, plug in the KPro, and make sure that you 1. don't let windows look for the software on the internet. 2. don't let windows pick the best software 3. don't let windows look on the installation cd 4. search in the KManager installation directory and 5. accept the unsigned device driver, ignoring threats of the sky falling in.

Update: Version has been released with Test USB function. Try that.

Hi Hondata,

The Device Instance ID shows up as USB\VID_0403&PID_E8D0\5&164BB88E&0&1 -- not sure if this is helpful for debugging.

Thanks for the detailed advice/steps on how to completely unload the drivers! Exactly what I was looking for. Now, I also just updated my KManager from 1.2.1.7 (which wasn't working still) to 1.2.1.8. I see the new Help > Test USB function. Should I try that function first, before trying the manual steps that you listed for me?

Please confirm what I should try first.

Thanks so much!

Try the USB Test function first.

Hondata wrote:Try the USB Test function first.

I tried the Test USB function and got the error dialog stating:

No compatible USB devices have been found.

I guess this makes sense since the drivers are never actually installed and so how can we expect KManager to even detect that the KPro is plugged in (?).

I will try the manual removal of unused drivers from Device Manager as suggested, then try reinstalling. Hopefully that'll do the trick.

Thanks!

Okay, I have the Device Manager showing all hidden/unused, unplugged devices.

Indeed, there was a greyed-out entry under Other Devices -> Hondata K-Series ECU. I've uninstalled this item.

There are no other devices under the USB or Other Devices categories that resemble K-Series, Hondata, ECU, Serial->USB, FTDX*, etc.

Should I be looking at any other device categories beyond USB and Other Devices?

There are also no items in Add/Remove Programs to do with ECU drivers (makes sense since they've never fully installed).

Before I continue, please confirm that I need not look for relevant devices under other device categories beyond USB and Other Devices.

Thanks!

You'll have to send the EDU to us.

Hondata wrote:You'll have to send the UCE to us.

Really? You still suspect that this is a hardware problem with the ECU/KPro?

Like I said, it works fine with my tuner's laptop (who is running 1.2.1.5), and it also works fine when I installed 1.2.1.5 on a "virgin" machine (that never had any previous KManager installs, ever). It is only these two laptops where I incorrectly tried to upgrade from 1.2.1.3 to 1.2.1.5 where I am having problems ever since (now I am at 1.2.1.8, to no avail).

If it is just a software issue occuring on my two laptops, I can live with it. The most important thing is that it works on my tuner's laptop, and that my car is fully tuned and running well.

I can't imagine how this would appear to be a hardware issue, and justify a week or more of down-time to send in my ECU. Does it really sound like I need to send in my ECU?

I believe that it is a hardware issue. It's your call, but it is possible for us to look at one of the laptops as well to see if there is a software problem.

Hondata wrote:I believe that it is a hardware issue. It's your call, but it is possible for us to look at one of the laptops as well to see if there is a software problem.

Okay. Thanks for the great support Hondata. I will ponder this and e-mail/call to proceed.

Thanks again for the help.

BTW, if it is in fact a hardware issue, but everything is running fine right now (as far as the car goes), would you say that this is an urgent issue (e.g., the ECU might continue to deteriorate and completely fail), or can I delay further so long as I don't mind the symptoms (not being able to connect with my own laptops)?

The problem is that I am in Toronto, Canada, so I know to ship the ECU back and forth between here and California will mean at least 1 week of vehicle down-time (probably more like 2 weeks), something that I cannot easily arrange any time soon.