Thanks Charlie...I told you I was blind. I knew i was in here but I couldnt find it for the life of me.

 

<table name="00 2 Byte Load High" category="MUT" address="38062" type="1D" level="1" scaling="uint16"/> 35164 or 895C
<table name="01 2 Byte Load Low" category="MUT" address="38066" type="1D" level="1" scaling="uint16"/> 35165 or 895D
<table name="02 2 Byte RPM High" category="MUT" address="3806a" type="1D" level="1" scaling="Hex16"/> 893A
<table name="03 2 Byte RPM Low" category="MUT" address="3806e" type="1D" level="1" scaling="Hex16"/> 893B
<table name="04 2 Byte AirFlow High" category="MUT" address="38072" type="1D" level="1" scaling="uint16"/> 35258 or 89BA
<table name="05 2 Byte AirFlow Low" category="MUT" address="38076" type="1D" level="1" scaling="uint16"/> 35259 or 89BB

 

Beautiful, thanks man.

Question,

Has anyone ever seen a ROm that shared only ONE 2 byte address (i.e; Load,RPM or Airflow) but didn't share all 3????? If not, we can fill up a good amount of these with "possible" codes that just need to get confirmed.

 

Ok, found in asm the reference for unclipped airflow. Sorry for the first post but I found the address somewhere and didn't try it
Airflow is checked now; I have bolded the changes.

88840016 (and 99.9% 88840017):

2byte load
MUT 00 = 6B28
MUT 01 = 6B29

2byte RPM (scaling 1000x/256)
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow (scaling 6.29x/64)
MUT 04 = 6B7E
MUT 05 = 6B7F

 

Great info. Thanks for putting this together.

 

My pleasure, just trying to give back ;-) It'll take a while to get it filled but hopefully it will become a "one stop shop" for everyone.

 

I think we should also add in the logging program definitions for logging this stuff.

Here is the mitsulogger definitions for RPM and Load. I need the airflow equation. RPM is not tested as i have not flashed my car with the MUT reference yet.

2-byte RPM Mitsulogger:
<Request LogReference="RequestID02" RequestID="02" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="RequestID03" RequestID="03" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="RPM-2byte" RequestID="FF" Eval="((256*RequestID02)+RequestID03)*1000/256" Unit="2byteRPM" Logged="y" Response="2" />

2-byte Load Mitsulogger:
<Request LogReference="RequestID00" RequestID="00" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="RequestID01" RequestID="01" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="Load-2byte" RequestID="FF" Eval="((256*RequestID00)+RequestID01)*10/32" Unit="2byteLoad" Logged="y" Response="2" Notes="Log using this Load Value" />

 

and what should we add in the xml def for the 2byte AirFlow to show in the ecu flash?

 

No need to add to the xml when you have the MUT table. Add the MUT address to xml, then make changes there. Al\lupo what is the MUT address for 88840016? Mscorei, see first post, download MUT xml and add correct MUT address. Open ecuflash and you can add what you need.

 

Here are the addresses for 88840016 & 17:

88840016
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 =6B7F

MUT 3D TABLE ADDRESS = 377F8


88840017
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 = 6B7F

MUT 3D TABLE ADDRESS = 37944


I checked the values in asm for both, also airflow for 17 is the same of 16. MUT table are located in different places.

 

ok now I understand. 10x a lot. great help al\lupo!

 

Anyone feel like confirming that the MUT Table address for 94170008 is 38158 or 38150 for me? Someone listed it as 38158 but when I disassembled the ROM it seemed like 38150 was the MUT00 address to me. I'm still VERY new to disasm coding.

 

There is a typo in first post, RPM addresses for 88840016 are doubled.

 

Good lookin' out. All fixed,thanks.

 

Jack, thoughts on adding the logging definitions? I think it would be beneficial so we can log what 2-byte changes we make.