Upgraded from 1.29 to 1.32 and now it doesnt connect. Is this a problem with the program? 1.29 still connects.
When i turn it on this is what comes up..
[11:48:04.671] Version 1.32.1399
[11:48:04.671] 11 memory models read.
[11:48:04.671] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[11:48:06.000] 218 ROM metadata models scanned.
[11:48:06.000] checksum module "subarudbw" loaded.
[11:48:06.000] flashing tool "wrx02" loaded.
[11:48:06.000] flashing tool "wrx04" loaded.
[11:48:06.000] flashing tool "sti04" loaded.
[11:48:06.000] flashing tool "sti05" loaded.
[11:48:06.000] flashing tool "mitsukernel" loaded.
[11:48:06.000] flashing tool "mitsukernelocp" loaded.
[11:48:06.000] flashing tool "shbootmode" loaded.
[11:51:03.437] Using interface OpenPort 1.3 Mitsubishi TX14sjXMcf8ff6c900000000000000000000000000000000
[11:51:03.453] unable to connect to vehicle interface.

 

Are trying to read or write?

 

Did you uninstall 1.29 and then install 1.32? Some people have been having problems running 1.30+ on there machines.

 

I get the same problem. I can write, but I can't read.

HELP ! !

 

If you can write but not read(and get a blank dialog box), try moving the read_evo7 and read_evo9 xmls to the EcuFlash\rommetadata\mitsubishi\evo directory.

 

I have yet to have any problems with 1.30+(knock on wood). Did you try re installing the drivers?

 

Had 1.29 (still using) then installed 1.32, Cant read frmo Ecu, but i can open the file and make changes from there. I even tried the uninstall, and install of 1.32. reinstalled the drivers. will try to move the rom flies around.
I even installed 1.32 on a different comp. still no joy.
And when i installed 1.32 my EvoScan stop working, but my mitsulogger is fine. Weird.

 

just tuned my friends car with this today and it said the same thing so i had to reopen ecuflash with the car on already and then it worked for some reason.

 

This is rather wierd that we are all having these problems. Hopefully the GuRue's will work out some patches to fix this.

 

Been having the same problem. It seems to lay in the older cables. It is compatable with the old versions 1.28, 1.29a, but not with the newer versions 1.30, 1.31, 1.32. I borrowed a couple cables from my friends. Their cables are a couple of months old. Both of there cables worked. Not sure y the older cables don't work. I have posted up a thread on openecu.org with little to no help on the subject. Here is a link to my thread clicky.

 

my cable is from the early versions back before ecuflash could flash the evo 9. it could only read the 9 and not flash. mine is working good so far with 1.32 no issues with evoscan or ecuflash

 

Then it could lay in the cables that start with an id of TX14........ Now my friends id's were TX34..... and TX36..... Not sure thou.

 

also you know what you could:
- uninstall the progam
- Delete the orignal folder by finding "OpenEcu" folder under C:\program files (if you made changes to any of your xml files back them up)
- reinstall the new verison of ecuflash

 

I've already done that a few times. Samething.