openecu.org

Hi

I have install 1.31, but now on my Evo 7 lots of the X and Y scales on the maps show jumbled numbers, most odd as 1.30 was fine.

Anyone else have this problem.

MB

Must be a definitions problem. Can you post your ECU number so that we can check?

burgers wrote:Hi

I have install 1.31, but now on my Evo 7 lots of the X and Y scales on the maps show jumbled numbers, most odd as 1.30 was fine.

Anyone else have this problem.

MB

I'm having the same problems with all my Evo IX maps. I've also noticed that it displays the data in certain tables inaccurately. Apparently, the Rev Limit of my car is now 134 RPM - should be 7606!

These files inherit 'evo9base' and use the '88570008' definitions.

...on a positive note.

The intercooler waterspray tables make more sense than in 1.30!

Probably an endian mixup due to the fix in 1.31 where the endian attribute reversal was fixed. Find a table that has the issue and open your base xml file (ex. evo9base). Search for the table and find the scaling attribute for the axis is question. Look at the endian attribute. If it is "big" then change to "little" or vice versa. See if that fixes the issue.

yep Ive got the same problem all the x y values are screwed up on nearly all the tables ????
so its not just a case of changing one thing the whole definition needs to be changed, why???
btw thanks again for the H8 support

merchgod wrote:Probably an endian mixup due to the fix in 1.31 where the endian attribute reversal was fixed. Find a table that has the issue and open your base xml file (ex. evo9base). Search for the table and find the scaling attribute for the axis is question. Look at the endian attribute. If it is "big" then change to "little" or vice versa. See if that fixes the issue.

This suggestion seems to be working so far......but, it's taking sometime to go through all the attributes!

I'm struggling to get the Knock Sensor Filter Maps to make sense for the Evo IX.

They're OK for Evo VII maps......but for the 'IX', RPM alternates between 54547 and Zero all the way down the table.

Any suggestions?

Yeah I noticed this problem on Saturday but though something was wrong with my definitions files or if there was some changes in the elements or the scalings that needed to be done but seamed fine. Soon enough will have the bug fixed, just gotta give some time to cboles.

I know some people were looking for 1.30 so I said id post it up

merchgod wrote:Probably an endian mixup due to the fix in 1.31 where the endian attribute reversal was fixed. Find a table that has the issue and open your base xml file (ex. evo9base). Search for the table and find the scaling attribute for the axis is question. Look at the endian attribute. If it is "big" then change to "little" or vice versa. See if that fixes the issue.

That fixes the issue for all of the definitions I have. I always was puzzled why the endian order was reversed in older versions. I had just assumed it was ignored on the older versions.

Really easy to "touch up" I have to go through all my base defs and adjust them, but all the important ones are fixed..

will give it a try

ok you lot here are the new base definition files download them and put them into your program files/ open ecu/ecuflash/rommetadata/mitsubishi/evo, folder this will fix the problems with v1.31

Works a treat for me.

Cheers BarryC.