Added 3D MUT TABLE code and instructions to the first post.

 

94170008

Here is what I have been using. Seems mine are in different addresses than are in the first post.

<table name="00 2 Byte Load High" category="MUT" address="38062" type="1D" level="1" scaling="uint16"/>

<table name="01 2 Byte Load Low" category="MUT" address="38066" type="1D" level="1" scaling="uint16"/>

<table name="02 2 Byte RPM High" category="MUT" address="3806a" type="1D" level="1" scaling="Hex16"/>

<table name="03 2 Byte RPM Low" category="MUT" address="3806e" type="1D" level="1" scaling="Hex16"/>

<table name="04 2 Byte AirFlow High" category="MUT" address="38072" type="1D" level="1" scaling="uint16"/>

<table name="05 2 Byte AirFlow Low" category="MUT" address="38076" type="1D" level="1" scaling="uint16"/>

 

I have 3 Evo 7 MUT table addresses for adding 3D MUT Table.

98640014 MUT 3d Table start 2E9E0

98640016 MUT 3d Table start 2EA9C

99860002 MUT 3d Table start 302D8

I'll post the 2 Byte load addresses when I get them for 98640016 and 99860002

MB

 

[quote=FuelsResearch;5321077]96420008

Load
MUT00- 8984
MUT01- 8985

Airflow
MUT04- 8BB9
MUT05- 8BDB

MUT Table- 39FA0

quote]

Huge mistake on post #29!!! Fix 1st post.

Airlfow
04-0x89E2
05-0x89E3


My airflow is on 02,03 which caused the error. My apologies, I will go back to lurking now.

 

Yours are for the individual addresses for each to be used in a 1D table. Mine is the address for the entire 3D table. Once you install the 3D map, you can see EVERY MUT address in the chart and adjust them that way.

I assume when you open that table in ecuflash you'd have to enter the DECIMAL value I have on the first post? If not, tell me what values you have in the ECUFLash Tables. The 3D MUT table uses HEX values so I can convert your numbers you have listed.

 

96530006 - MUT table address = 36200

 

Updated, thanks guys.

 

Can you tell me the values you have listed in your tables for each of these in ECUFlash? Then I can find out what to put on the list. I'm almost certain they will be the same as 94170014 anyways. I'm most concerned with the airflow values. Im pretty sure you'll have 893A and 893B listed for your 2 byte RPM's since you are scaled for HEX16 already.

 

Fixed thanks Jack

 

Change Evoscan formula to 1000*x/256

I added a note in the first post for future users.

 

2-byte rpm for 96420007 works for 96420008. Since these two roms are apparantly pretty much identical, I would guess that airflow, load and MUT are all the same.

This should be stickied in nj's ecu topics thread

 

[QUOTE=FuelsResearch;...I would guess that airflow, load and MUT are all the same.

This should be stickied in nj's ecu topics thread[/QUOTE]


I would rather not guess if I can get away with it. That would be cool to have it stickied in there.

 

By no means, don't guess. I was just suggesting the possibility that a 0007 owner could try if they wanted, if it doesn't work it just won't log correctly.
But the 2-byte rpm does work, I just tried it.

 

2byte RPM eval for evoscan for the blind guy? TIA

 

LOL 4 post above yours homey
1000*x/256