I kept 129 as well.. but when it came time to use 130 for the first time.. i went and deleted that version.. then i launched 130 and bam.. "unable to connect to vehicle"

I was like WTF..??

What do they mean by two openports at the same time.. cuz i have my mouse plugged in on USB port 1 and the tactrix on 2.. so you guys think its reading my mouse driver instead of my tactrix which is found on 2..?

 

The fact that 1.29a works fine is probably why this issue hasn't been examined more tenaciously.

 

If the mouse uses the same driver, then its possible if its the first device detected on the same driver chain.

One thing you should test if you upgraded from an earlier version..

Go into the openecu directory, BIN directory I think, for 1.3, if there is a FTD2xx.dll file in there, or the directory above it.. rename the file to something like FTD2xx.BAD for the time being..

Driver version differences CAN cause problems and I suspect that theres a 1.29a driver installed and its persistant, since it already works fine, then I'd leave the driver in place and remove the conflicting DLL in the new version of OpenECU

 

I had 1.29, but on a different laptop. i just recently installed 1.3 on a different laptop and could not connect to the ecu. ecuflash was detecting my cable and all the associated drivers were in place.

then i uninstalled 1.3 and installed 1.29 and now i can read my ecu.

i've also done the install/uninstall with 1.3 and still get "unable to connect to vehicle interface."

i will try the directory i saw earlier in this thread and see if that works...that's if i can find that directory coz i'm not that computer literate

 

solved. thanks.

 

I had problem with ver 1.3 same many thread above
ECUFlash recognizes the Tactrix cable being inserted/removed in the lower right corner.

But still get the message " unable to connect to vehicle interface. "

So I reverted back to 1.29a and it worked.


How to solved this problem?

 

I have never had any version at all installed and I get the " unable to connect to vehicle interface. " issue. If anyone has ver 1.29 , can you email it to me, please?

EDIT: nevermind @ dontemailme.com

Oh yeah, how do I get rid of the 1.3 drivers?

EDIT: vehicle in question is a 06 IX MR

 

OK, I just rebooted and retried to read. Everything seems to work properly, now.

This, " unable to connect to vehicle interface. " problem only seems to affect Evo IXs. hmm.

 

Was anyone ever able to resolve the "unable to connect to vehicle interface" issue ?