[wpetering]

I have a K+DCAN INPA compatible USB cable for my 2009 328i. Using BMWLogger to register my new battery, i'm getting to the point where my device is detected but unable to contact DME. I'm stuck.

Here's my steps:

• I plug in my USB cable. In Device Manager, the cable shows up as "FT232R USB UART" in "Other Devices".
• I install the latest drivers from FTDIchip.com. The cable now shows up as "USB Serial Port (Com5)" under Ports.
• I start BMWLogger and the app shows "FT232R USB UART Detected. Ready to log".
• I then "select register battery" from "Special" menu where it reports "Attempting to connect to the interface".
• The final message from BMWLogger states, "Unable to contact the DME. Please make sure its properly powered"

Yes, the start button is pushed (without touching brake).
Not sure what else I'm missing???
Using BMWLOgger to install drivers never turns the "FT232R USB UART" into a Port.
I've tried also changing com5 to com1.

(Sorry, don't know how to embed images inside text)

[Sensible_]

In comport settings in device manager try setting the latency to 1.

If you click the drop down on that Connectivity -> Device menu, are there any other options there to choose from? While trying to register my battery with the software I couldn't get the car to connect either. After I went into that drop down and changed the Device to K+DCAN, or something similar, then it worked like a charm!

[wpetering]

Sensible: I'll try 1. I tried 8 but didn't make it to 1.
Cobra: My drop down only lists the "F232R USB UART". I was wondering if DEVICE had to say something about "Com port"??

Thanks for the inputs.

Hmm. With the yellow exclamation point within Device Manager your machine might not like the driver you have installed. I'd keep looking at trying to fix it from that angle maybe..??

[wpetering]

Originally Posted by FCobra94

Hmm. With the yellow exclamation point within Device Manager your machine might not like the driver you have installed. I'd keep looking at trying to fix it from that angle maybe..??

Cobra, the exclamation point comes up when I plug in the cable without any drivers installed. I then install the driver "ftdibus.inf" which turns the unknown device into a USB Serial converter. I then install driver "ftdiport.inf" which adds the cable as a COM device. I think you hit it on the head though, when you said some other device needs to be in the "device" dropdown in the preferences box in BMWLogger.

Can someone confirm/verify what device needs to be displayed in BMWLogger??

[Fed3]

I have exactly the same problem. Tried with a Mac OS, tried with Windows XP but no change. Did anybody figure it out? Is it just the cable not working properly?

[Jdub679]

Originally Posted by Fed3

I have exactly the same problem. Tried with a Mac OS, tried with Windows XP but no change. Did anybody figure it out? Is it just the cable not working properly?

Did you find a solution? I'm also using Mac OS.

[wdeerfield]

I am about to try this and noticed you have it on COM5. i thought it needed to be COM1 with a latency of 1. Let us know if you figure it out as I am going to register my battery this weekend with this software

[stormtrooper7]

Did this get resolved? I'm having the same issues. Wonder if it's a cable issue? But then I wouldn't be able to read the codes either...

[mys_iii]

I searched but couldn't find any useful information on this issue. Has anyone figured out the "Unable to contact DME" issue with the BMWLogger software? I am having the same issue right now.

Thanks

[wpetering]

Still same issue. My cable and software is from BMWLogger. I'm using Windows 10 as well.

Only change is that I can read codes from the DME but when I try to clear codes, I get a "packet failure unable to connect to DME".

I've re-installed software. Need to verify the license key is installed. And check drivers. I may go back to my Windows XP laptop and try it to rule out a bad cable.

Cheers.

[mys_iii]

Originally Posted by wpetering

Still same issue. My cable and software is from BMWLogger. I'm using Windows 10 as well.

Only change is that I can read codes from the DME but when I try to clear codes, I get a "packet failure unable to connect to DME".

I've re-installed software. Need to verify the license key is installed. And check drivers. I may go back to my Windows XP laptop and try it to rule out a bad cable.

Cheers.

In my case, it was my cable. I got a cable from bmwlogger and everything worked great. I was running on Windows XP though. I tried on Windows 7 as well but the ftdi USB drivers don't seem to work too well. When the cable is plugged in, it doesn't seem to be recognized correctly under device manage. That may be your issue.