Quick answer please... Ecuflash version
Thread Starter
Evolved Member
iTrader: (37)
Joined: Sep 2003
Posts: 3,146
Likes: 2
From: Spec-Ops Motorsports, Fayetteville, NC
Quick answer please... Ecuflash version
Hey guys, i've searched but havent found a definitive answer... is ecuflash 1.3 working yet ? or is everyone still using 1.29 and 1.28 ? please let me know ... and if you can send me to a link to get the latest version... im going to openecu now... just hoping you guys can beat me to it
I'm using 1.3 with no issues. Well, unless you try to change the map color schemes ... then you get about 200 error pop ups and the Subaru maps don't load correctly ... but who cares about Subaru maps, right?
Trending Topics
I installed 1.3 after using 1.29a for several months. Did have issues, and not related to the drivers.
First backup your rommetafile directory from 1.29a and the backup001 directory
I did a full uninstall first, but the uninstall program does not remove the files and directories, even after a reboot. Reboot then remove the openecu directory by hand. I also uninstalled the FTDI drivers as they come bundled in 1.3 ( also 1.29a ) Perform the install and everything should install OK including the drivers. When you plug in the cable again it autodetects and finishes the driver install. Shows the openecu 1.3 cable in the box on the bottom line So no problem there
On to the problem
What happens is Ecuflash opens fine but cant find your ROM or definition properly, even after pasting in the files into \rommetafile etc and setting the options inside Ecuflash. Tells you unknown ROM definition and wants you to select from scratch, previous defintion or inherited from.... It will never work.
What is happening is it cant find the def and read files properly. Even after setting the options for the directories it still happens. You know you have the problem because when ecuflash opens it during the init it says O ROM....read..... on the third init line For some reason the backup files have to match the ones in current use. So here is the fix
You need to copy everything in the rometafile directories and subdirectories from ecuflash 1.3 to the backup001 directory backup001\rommetafile\
Then copy ALL the ROM def read files and .hex to the \ rom..\evo directory
Then double check to make sure you have the settings pointing to the correct directories. For Metafiles use \rommetafiles dont drill down farther
For the rom directory use \rommetafiles\mitsubishi\evo
This should fix it. During the init I then got 30 ROM.. read and it proceeded to open everything fine.
Milburn
First backup your rommetafile directory from 1.29a and the backup001 directory
I did a full uninstall first, but the uninstall program does not remove the files and directories, even after a reboot. Reboot then remove the openecu directory by hand. I also uninstalled the FTDI drivers as they come bundled in 1.3 ( also 1.29a ) Perform the install and everything should install OK including the drivers. When you plug in the cable again it autodetects and finishes the driver install. Shows the openecu 1.3 cable in the box on the bottom line So no problem there
On to the problem
What happens is Ecuflash opens fine but cant find your ROM or definition properly, even after pasting in the files into \rommetafile etc and setting the options inside Ecuflash. Tells you unknown ROM definition and wants you to select from scratch, previous defintion or inherited from.... It will never work.
What is happening is it cant find the def and read files properly. Even after setting the options for the directories it still happens. You know you have the problem because when ecuflash opens it during the init it says O ROM....read..... on the third init line For some reason the backup files have to match the ones in current use. So here is the fix
You need to copy everything in the rometafile directories and subdirectories from ecuflash 1.3 to the backup001 directory backup001\rommetafile\
Then copy ALL the ROM def read files and .hex to the \ rom..\evo directory
Then double check to make sure you have the settings pointing to the correct directories. For Metafiles use \rommetafiles dont drill down farther
For the rom directory use \rommetafiles\mitsubishi\evo
This should fix it. During the init I then got 30 ROM.. read and it proceeded to open everything fine.
Milburn
Last edited by wrcwannabe; May 17, 2007 at 03:03 AM.
Can anyone hook me up with a version besides.. 1.3 and 1.28..
Anybody got 1.29 or 1.27 that they can send me plz.. am begging you.. i need to try these versions b4 i blame the "unable to connect to vehicle interface" thingy on the tactrix cable..
Anybody got 1.29 or 1.27 that they can send me plz.. am begging you.. i need to try these versions b4 i blame the "unable to connect to vehicle interface" thingy on the tactrix cable..
Thread Starter
Evolved Member
iTrader: (37)
Joined: Sep 2003
Posts: 3,146
Likes: 2
From: Spec-Ops Motorsports, Fayetteville, NC
haha... if you go back and run the driver package, sometimes that helps. but, if you wanna try it out, when i get home i can shoot you 1.29 if someone doesnt beat me to it.



