There should be 2 drivers...delete them, uninstall ecuflash.




install a new copy of ecuflash 1.34, the new tactrix drivers will be installed untill you connect the cable to the computer. When prompted, select the option that lets you tell windows where to look for the drivers. Use Browse button to go to the C:\Program Files>OpenEcu>EcuFlash>drivers>x86 directory click ok. It will ask you to do this 2 times to load the new drivers.

 

thanks! and yes i did have 4 drivers....ill test it out again tonight....

 

Haven't been able to get any versions after v1.29a to work. Just tried v1.34 today. Tried all the tricks, and couldn't get it to read/write to the ECU. I'm running the OpenPort 1.3 Mitsubishi TX14 cable. Guess its back to v1.29a yet again...

 

Interesting ... I'm starting to wonder if there are different cable firmware and/or hardware versions. Last weekend I could not read an ECU that was flashed with a cable newer than mine. And when I connected his cable on my computer it started recognizing as new hardware.

 

Its possible that ECUFlash is checking versions of the cable to prevent knockoff cables from being used with it.

The Openport cable is the revenue generator for the development of ECUFlash..

I have an early 1.3m cable (from his first or second batch of cables), and a newer 1.3u cable and both worked fine with every version of ECUFlash I have installed. I do know drivers can be a PITA at times and generally uninstall them when I can before I update the software.

 

I got my cable from Mynes, so that shouldn't be the cause in my case.

 

I haven't had and issue with any version of EcuFlash either, but it is also a second or third batch generation. Maybe it's a bug in the cable checking routine MJ mentions.

 

a little observation

ecuflash 1.34 downloaded and working fine on a never before ecuflash downloaded laptop.

the same program downloaded to a laptop that had 1.29 totally removed,(checked and checked again) using the same cable, gives an empty box from which I should choose car version.

rules out the cable, means there is something, someplace I'm not removing.

 

I have the same thing, somehow the set path is lost. I just go to options and change to the "read directory" but it's a hassle to have to go to options each time
I'm getting a laptop with a clean install of xp next week, I'll see what behaviour shows up.

 

It's not a fact of where you got the cable, it's when you got it and which one. The newer cable version was recently released.

As far as ECUFLASH version, if you have the older cable then what reason is there to upgrade the version? Now if there were some new defined tables then that would be worth upgrading cable and ECUFLASH version. Just seems that the software has taken a hard left turn to Subaru if you ask me

 

how bout 1.30?? 1.31 is when it became different.

 

That issue I've tracked down. ECUFlash stores the path for the ROM template files in the registry. If you know how to handle the registry file, that one is easy to fix.

 

The older version of ECUFlash takes down my entire computer on occasion. Its only annoyance, but its a big one. I usually have about 15 folders open and often have IDA Pro running at the same time. I loose all the folders and if IDA Pro gets taken down, I loose my place in the disassembly.

 

Same issue with those versions.

 

lol @ idapro... you know your in trouble when you have more than 8 windows of disasm open