Thanks for a great writeup

What do I need to add to the requestID.xml in order to log with Mitsulogger ?

 

The Addresses for the 94170014 rom are all blank:

2004 94170014 ----- ----- ----- -----

Is this because its the same as the 008 rom or no one knows what the addresses are just yet? I have the MUT Table mod done for my 2 byte load but i don't know exactly where i would enter in the 0x893a and 0x893b. Sorry, only been messing with the hex stuff for about a month, not sure how to breakdown the MUT Table yet. I threw up my MUT table for clarity.

EDIT:

So I tried adding the 893a and 893b in the locations I circled in my table but the readings were CRAZY high when trying to log with evoscan. They did respond to rpms though, not sure if its a scaling thing????

 

I thought MUT requestID 02 and 03 were 2-byte airflow and 04 and 05 was 2-byte rpm?

 

I hate that MUT XML, use this one (dont forget to update the hex address of the actual table (in red)

<table name="MUT Table" category="Advanced" address="373c4" type="3D" level="1" scaling="Hex16">
<table name="X" type="Static X Axis" elements="32">
<data>-</data>
<data>0</data>
<data>-</data>
<data>1</data>
<data>-</data>
<data>2</data>
<data>-</data>
<data>3</data>
<data>-</data>
<data>4</data>
<data>-</data>
<data>5</data>
<data>-</data>
<data>6</data>
<data>-</data>
<data>7</data>
<data>-</data>
<data>8</data>
<data>-</data>
<data>9</data>
<data>-</data>
<data>A</data>
<data>-</data>
<data>B</data>
<data>-</data>
<data>C</data>
<data>-</data>
<data>D</data>
<data>-</data>
<data>E</data>
<data>-</data>
<data>F</data>
</table>
<table name="Y" type="Static Y Axis" elements="16">
<data>0</data>
<data>1</data>
<data>2</data>
<data>3</data>
<data>4</data>
<data>5</data>
<data>6</data>
<data>7</data>
<data>8</data>
<data>9</data>
<data>A</data>
<data>B</data>
<data>C</data>
<data>D</data>
<data>E</data>
<data>F</data>
</table>
</table>

 

Well, all I know is that evoscan looks at requestID's 02 and 03 for 2 byte rpm
.

 

Nice! Thats a bit easier to translate haha. Thanks Dave, you rock. With that said, those were definitely the correct locations I added the codes and evoscan is still off the charts when trying to to read the 2 byte rpm. Do I need to edit the FUNCTION formula in evoscan??

 

someone should make things easy and post all of the 2byte mods into one place so everyone can just copy and paste everything into their xml and make the minor changes needed to each line to make them work.... just an idea. Id do it, but its well above my level of messing with the ECU

 

I updated the table in the first post with your ROM JackofallTrades.

I don't know the evaluation formula for 2-byte RPM. Can you post what your evoscan xml says?

 

My version of evoscan uses 3.125*x and lists it as "units". It definitely logs rpms alright, just not accurately with this particular multiplier.

 

Yeah it's not right if it's x. It should be some variable name like the 2-byte load one has. I don't have evoscan so I can't help unless you want to send an xml or post it here.

 

Here's 2 byte Load (which works just fine)

<DataListItem DataLog="N" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="00" RequestID2="01" Eval="0.3125*x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes=""/>

Here's 2 byte rpm (which doesn't log the correct values)

<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25*x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>

 

Can someone please post the XML code needed for Mitsulogger.

 

Is anyone successfully logging their 2 byte RPM with evoscan???????

 

yes you need to change the formula to 1000x/256

 

Yeah, I actually tracked that down on some honda forum late last night,lol. Thanks though :-)