96530006
2byte load
MUT 00 = 898a
MUT 01 = 898b

Note: as we know - there are several loads used within the ecu code - baro./temp compenstated, not compenstaed etc. ect. - the one above seems to match the load used for timing. Another address is 8984, 8985 which seems to be used as reference load for boost control.

 

Also note you're not required to log load on MUT00 and 01. You can log it from any MUT that isn't used. Same goes for any other parameter you want to log (RPM, airflow).

But setting a commonly used standard helps to avoid confusion.

I haven't confirmed this so maybe others can.

 

ROM ID # 88570008
2Byte Load
MUT 00= 6B12
MUT 01= 6B13

2Byte Airflow (Not Tried yet)
MUT 04=6B6A
MUT 05= 6B6B

 

Don't mind 2byte Airflow, it is wrong for both version. I tried and it keeps at 255. Looking at the code it *seems* to be octane number rather than airflow...

 

could you post your 2byte load 96530006 xml file?what must I do for to set ecuflash?

 

Attached is the zipped xml for 96530006 - remove all the other files beginning with 96530006 from the evo folder in Ecuflash.

I am attaching also a screenshot of what you need to have in the MUT table after opening and editing your ROM.

 

I use these because thats what Evoscan is already setup for, and always has been. One less step, ya know? It doesn't NEED to be those ID's but why have to edit 2 things?

 

2Byte RPM users, what improvements have you noticed with it, Particularily with logworks?

 

98640014

MUT00 885C
MUT01 885D

MUT00 location to change is at 2E9E2
MUT01 location to change is at 2E9E6

MB

 

So if you added the entire 3D MUT table, you would only need to edit the MUT00 and MUT01 locations correct? And if you added only a 1D MUT Table you'd need to edit the addresses you listed above? I've always used the 3D table so I'm just making sure I understand the process.

 

I think adding the whole table is better, its one copy/paste and one address change.. and it gets people in the "right frame of mind" when talking about MUTs

 

I agree, and I've also used multiple MUT locations for testing things out, such as the ALT MAP ADC signal which came in handy.

 

96940011 MUT table:

3f314

 

96420008

Load
MUT00- 8984
MUT01- 8985

Airflow
MUT04- 89E2
MUT05- 89E3

MUT Table- 39FA0

Bump for this question:
2Byte RPM users, what improvements have you noticed with it, Particularily with logworks?

 

I haven't used logworks but its just more accurate readings. To the naked eye it may not look like much but once you start calculating different values along with it, the improvements/accuracies are probably more noticeable.