Yes there are both "builds" of the 9653006 rom...

 

Guys the current values used for 2byte load for 96260009 -
MUT 00 = 0x8984
MUT 01 = 0x8985

I am wondering if these are the 2-byte LOAD_Raw (no temp compensation) values when we should infact be using 2-byte LOAD_Temp_and_Baro_Compensated -
MUT 00 = 0x898A
MUT 01 = 0x898B
....

 

MUT Table address="33A7c" - need to verify
AT MUT table address="7F784" - I think it's same as EVO 7.5 GTA

 

Thank you, will give it a try.

 

Does this look right?

 

Yes, but I hevn't any mods like 2 byte load, RPM ...

 

Any chance of getting 2 byte load for Evo6s?
ROM 24430002 or 25570000

It would defo be greaaaaaaaat!

 

need a little help here setting up my friends JDM IX (80920002) to log 2 byte load. I know that this romid is not very popular and I have to inherit from 88570008 but when I make the changes in the MUT table (00=0x6b12 and 01=0x6b13) 2 byte load reads in the 1000xs and my timing goes static and logs at -20.
Not sure how that affected logging timing because it looks up request id 06.
Not sure if this info is necessary but I'm using V1.29a, with evoscan v2.5
Anyone know whats going on here?

 

^^anyone know what the MUT values are for logging 2 byte load on 80920002??

 

2byte load for 89970010
MUT 00 = 0x8B0A
MUT 01 = 0x8B0B
need to check it

 

mut 00,01,02,03,04,05 works like in math where the first number is the x axis and the second number is the y axis right?

 

No, first is the Y axis and second number is the X axis. That's why "MUT0X" is the first scale in the y axis, it's for all MUT addresses that start with MUT0. After that replace the "X" with the number in the X axis for the cell you're looking at.

 

+1 need also

 

2byte airflow (working)

6B6E
6B6F

Taken from this thread:

http://www.lancerregister.com/showthread.php?t=134923

 

great info