I have installed ECUflash 1.30 on my new-to-me laptop for garage use. No other versions of ECUflash have been previously installed.

Whenever I try to read the ROM on my '05 Evo 8, I get the following:

[07:25:42.500] Version 1.30.1095
[07:25:42.515] 8 memory models read.
[07:25:43.687] 145 ROM metadata models read.
[07:25:43.687] checksum module "subarudbw" loaded.
[07:25:43.687] flashing tool "wrx02" loaded.
[07:25:43.687] flashing tool "wrx04" loaded.
[07:25:43.687] flashing tool "sti04" loaded.
[07:25:43.687] flashing tool "sti05" loaded.
[07:25:43.687] flashing tool "mitsukernel" loaded.
[07:25:43.687] flashing tool "mitsukernelocp" loaded.
[07:25:43.687] flashing tool "mitsubootloader" loaded.
[07:26:15.765] unable to connect to vehicle interface. <--Grrrrrrrrrrrr!

In the lower RH corner, it is recognizing the cable: OpenPort 1.3 Mitsubishi EVOSCAN1. I do get the window asking the vehicle I am trying to connect to. I do not get a window saying to connect the cable and click OK.

EvoScan and MitsuLogger both connect and work like a charm, so I assume my cable, Windows XP, etc. are working properly. Good assumption? I have tried uninstalling, deleting the OpenECU folder, and reinstalling with the exact same result.

I have found plenty of posts with people complaining, but no resolutions except to go back to 1.29a. Maybe OpenECU.org should make this available, since some of us can't seem to get 1.30 to work.

So, has someone found why this is happening and what to do to fix it? Does someone have a copy of the ECUflash 1.29a installer they would be willing to send me?

Thanks for your time...Help if you can!

 

mine does the same thing. I have 1.29 though if you need a copy of it. just email me at jsnrchtr@aol and i will send it to you.

 

move all of the read xml files from

C:\Program Files\OpenECU\EcuFlash\rommetadata\read templates

to

C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

and it will work.

 

I'll have to give it a try.

 

Moved Read_Evo5.xml, Read_Evo7.xml, and Read_Evo9.xml as prescribed, and moved the Subaru ones to their respective folders, as I can see no reason to have Subaru .xml's in the Evo folder--correct me if I'm wrong here. There was no change with respect to ECUflash 1.30 being able to connect; this did not work for me.

How about you, mrfred?

 

Thanks! E-mail sent

 

Didn't work for me either. So much for that.

 

Strange, it worked for me. I've been using 1.30 since it came out.
Can you flash with 1.30? if not, it may be a driver issue.

 

I've tried re-installing drivers, and reinstalling ECUflash. If it was drivers, wouldn't I have problems with EVOscan and Mitsulogger? Don't they both use the same cable drivers?

 

I found that the tactrix drivers included in 1.3 are not necessarily compatible with the
cable that you can buy from evoscan (at least for me). There are some Tactrix drivers out there that try to help but my solution was and is to simply run ecuFlash 1.29 and it's driver set. You might need to uninstall the tactrix drivers that came with 1.3 along with 1.3 before installing 1.29. Oh i use version 1.29a and not 1.29 if there is a difference i do not know

Anyway this is how it ended working out for me YMMV

Good luck

 

1.29a works like a charm! I guess this is the resolution to the problem.

 

There's definitely some kind of flaw in the v1.30 software. EvoScan, ScanTech, and ECUFlash 1.29 all work fine with the Tactrix cable drivers included in ECUFlash 1.30. I thought it might be an issue with a conflict between v1.29 prefs and v1.30 prefs, so I deleted the custom pref entries for ECUFlash in the registry. That didn't help. I also tried changing some of the Tactrix cable driver settings. Also didn't help. v1.29 is apparently the solution for now.