hey guys. im having a problem with the newer ecuflash versions. anything above 1.43.3xx crashes when trying to open up roms that were read from the ecu with older versions of ecuflash.

if i go into the xml file for my rom id and delete this line

<table name="MAF Hz" address="67d4"/>

it will work just fine and not crash.

that line is in this part of the xml

<table name="Airflow/Hz Baro and Air Temp Compensation" address="3351">
<table name="IAT_Comp/Baro_Bar" address="678e"/>
<table name="MAF Hz" address="67d4"/>
</table>

it will read just fine if i go back to an earlier version of ecuflash but the problem with that is that it will no longer see that i am connected to the ecu with the 2.0 cable so i cant read or write.

i have to go back to 1.43.3xx for the cable to be picked up and be able to read/write

iv read that it has something to do with the new drivers that come with newer versions that aren't backwards compatible. that doesnt really bother me though, i would like to stick with the newer versions of ecuflash.

my main problem is that it keeps crashing and closes right away unless i delete that line in the xml.

does anyone know what i could do? anyone experience this before? would it be fine it i just delete that line or is it important?

rom id is 96530006
2005 evo 8

 

bump....anyone?

 

check the base rom to see if it has a scaling associated with that line

 

would it be in the evo7base.xml? if so, i have 2 files.

evo7base
&
evo7base_20081101

evo7base does not have scaling.
evo7base_20081101 does have scaling

this is whats in the evo7base_20081101 xml

<table name="MAF Hz" type="Y Axis" elements="9" scaling="MAF Hz"/>

 

copy that scaling into the evo7base xml and you should be good to go

 

just tried it and ecuflash still crashes. is there a certain part that i should put the scaling in? or can it just go at the end?

 

it has to go it the same section ie in between the table tags for the maf hz in the base xml

 

hmm..well i dont have that part in the evo7base either. theres no maf hz section

any suggestions?

i also tried to copy

<table name="Airflow/Hz Baro and Air Temp Compensation" category="Fuel" type="3D" level="3" swapxy="true" scaling="AirTempBaroCorrection">
<table name="IAT_Comp/Baro_Bar" type="X Axis" elements="4" scaling="AirTempBaroFactor"/>
<table name="MAF Hz" type="Y Axis" elements="9" scaling="MAF Hz"/>
</table>

over to evo7base and also copied over

<scaling name="MAFHz" units="Hz" toexpr="6.29*x/64" frexpr="64/(6.29*x)" format="%.0f" min="0" max="5000" inc="1" storagetype="int16" endian="big" />

and still crashes.

so far the only way to get around the crashing is to go into my id xml and delete that one line

this is so frustrating

 

you need to either remove the space in the scaling="MAF Hz" to ="MAFHz" in the table part OR put a space in the scaling name="MAFHz" to ="MAF Hz"

and that should work

 

ok...seems to be running now with out crashing.

i left the evo7base alone. nothing added or changed to that.

i only modified evo7base_20081101
i took out the space from MAF Hz on this line
<table name="MAF Hz" type="Y Axis" elements="9" scaling="MAF Hz"/>
so its now
<table name="MAF Hz" type="Y Axis" elements="9" scaling="MAFHz"/>

ecuflash doesnt crash anymore. now i hope it doesnt crash because its been fixed and not because the line of code is screwed up or something.

any clue why i had to go through all his? all i did was installed the newest version of ecuflash. i did not change anything else

 

it should be fine now, as the main cause of the crash is the missing scalings

 

I know this thread is a little old but I just ran into this same issue. I don't how in the world you even thought to look at that scaling for the issue but thanks for figuring it out. It still think it's crazy that one little space in the wrong place can cause Ecuflash to crash.