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 haven't even bothered with getting new ecuflash. Ever since I heard people were having issues 1.30. I am happy with my 1.29

 

Me too. I am very happy with my 1.29a. I tried 1.30 and it did not work on my laptop.

 

Tables for my VIII look ok. Haven't flashed with it yet though (it was this post that alerted me that 1.31 was out in the first place ).

 

It might be because you didnt put your old updated Xml in with it and it doesnt have the proper definitions maybe?

 

I put in my old definition and all the numbers were off, in the maps as far as rpm and load and things like that

 

Hmm I suppose it depends on the definition. I windiff'd the default xml definitions for my rom from 1.30 and 1.31 and they were identical.

Did you guys keep the original copy of your rom's xml def from 1.30? Hmm I didn't save evo7base.xml from 1.3...might be interesting to see if that has changed for 1.31.

 

No it's not that, I changed the metadata folder in the options to point to my xml file folder, and also copied my xml into the standard evo folder. Most of the maps display Ok, but the axis values display as gobeldygook, as is the def file is wrok. Re installing 1.30 restores the views to normality. Other users have also reported this problem on JDM IXs.

MB

 

yup same problem here...

looks like its getting the bytes stuffed up by 1...

0x0001 in my old rom now equals 0x0100

 

Maybe big and little endian are mixed up.

 

yeah I was thinking that as well - anyways im sure Colby will see this and rectify the issue

 

The values appear to be correct, it just looks like the cell blocks are too small to fit the value so you end up with 160... for something like 16000 (as seen in the MAF load)

My 1.31 Xml does not have level="1" in some of the tables also

 

yeah its an endian problem, from new evo9base:

<scaling name="Hex16" units="hex" toexpr="x" frexpr="x" format="%04X" min="0" max="65535" inc="1" storagetype="uint16" endian="big"/>

from old evo9base:
<scaling name="Hex16" units="hex" toexpr="x" frexpr="x" format="%04X" min="0" max="65535" inc="1" storagetype="uint16" endian="little"/>

 

My anti lag stop address is 1684 with 1.30, and 1682 with 1.31. What will this cause?

 

ive been having this problem as well reading the Evo IX. I have the -15 ROM. When it reads from my ECU, the load cells are all messed up, showing some wierd numbers...going from 212xx to 212xx.5 etc.

anyone have a version of 1.30?

this is what my evo9base looks like: