I don't know if this is correct or not. I started with 3ee84 since that is supposed to be MUT00. I set the x and y axis so that it is easy to find a certain MUT address easily. Just replace the "X" on the y axis with the label on the x axis. Someone tell me if this looks right:



Here's the .xml:

<table name="MUT table" category="Misc" address="3ee84" type="3D" level="1" scaling="Hex16">
<table name="X" type="Static X Axis" elements="32" scaling="Hex16">
<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="30">
<data>MUT0X</data>
<data>MUT1X</data>
<data>MUT2X</data>
<data>MUT3X</data>
<data>MUT4X</data>
<data>MUT5X</data>
<data>MUT6X</data>
<data>MUT7X</data>
<data>MUT8X</data>
<data>MUT9X</data>
<data>MUTAX</data>
<data>MUTBX</data>
<data>MUTCX</data>
<data>MUTDX</data>
<data>MUTEX</data>
<data>MUTFX</data>
<data>MUT10X</data>
<data>MUT11X</data>
<data>MUT12X</data>
<data>MUT13X</data>
<data>MUT14X</data>
<data>MUT15X</data>
<data>MUT16X</data>
<data>MUT17X</data>
<data>MUT18X</data>
<data>MUT19X</data>
<data>MUT1AX</data>
<data>MUT1BX</data>
<data>MUT1CX</data>
<data>MUT1DX</data>
</table>
</table>

 

Nice! Its much better than the single value tables I had been using.

 

Does it look right? Was the way I labeled the axis easy enough to understand?

I'm glad it helped you mrfred, especially after everything you've helped me with!

 

Yeah, I got it right away. Your choice of axis values was easy to understand.

 

don't think you can specific MUT100+...

 

Bez said somewhere on ActiveMatrix that the first portion of the MUT items are data values and the second portion are commands that can be issued to the ECU. I forget the transition ID though.

 

Okay.... need a little help here. I am attempting to make the 2-byte airflow mod to my ROM. I searched but couldn't turn up info specific to this ROM.

I've added the above code to my XML and the MUT table shows up. FYI the values aren't identical to those posted in the original post.

Can someone help my place the correct values into the MUT table for this mod?

 

Type 15 addresses are 3EE8E and 3EE92, change the values from 27177 and 27176 to 27550 and 27551 respectively.

Adding 2 byte airflow to USDM Evo IX type 13 and 14 (NOT 15) condensed. Thanks to JCSBanks, l2r99gst, MrFred, and Everyone else that contributed

Add 2 new tables to the xml:

Open Ecuflash and change these values to 27550 and 27551 respectively.

Add this to EvoScan:
Works perfect

 

Bump... maybe not.... I show the same code for 2 - byte RPM.

 

^^^ I got the info for two byte RPM from here:
https://www.evolutionm.net/forums/sh...0&postcount=23

But then there's this:

https://www.evolutionm.net/forums/sh...9&postcount=22

EDIT: Okay I believe the RPM info is whack..... I changed my code from hex to uint and entered the suggested values. Hopefully it will work.

Anyone have the code for 2-byte RPM on type 15?

 

Try this,
https://www.evolutionm.net/forums/sh...d.php?t=297483

 

Currently confused about the process of where to change the request ID so that I can log more 2 byte options. I have the MUT table and compare one modded for 2byte load and airflow against bone stock, but I dont see where the request change was calculated. I am sure there is a big piece of the puzzle I am missing still but any help would be greatly appreciated.

 

So this morning I went for a drive to try and use the Load+Baro and Load+Baro+temp 2 bytes. Since I didnt know any better I had initially tried using MUT0x requests 04/05 and 06/07. While it logged what I was after perfectly, it also fouled timing and Coolant temp (which uses these requests otherwise) when logging.

Question- Much as above, how does one determine which of the other MUTXx addresses can be used and how do you tell EvoScan? Or can you only log 2 at a time (2 byte requests) with it? Since 2 byte airflow is more a novelty than a need I am not using it currently to see what effect the cold temps are having on load. I would like to log all of them if possible though.

 

Look at the MUT IDs in the EvoScan Data.xml file. Whatever IDs are unused (i.e. not listed) are fair game.

 

So if I am looking at the table and see 1A does that mean the left axis, row 1, starting at address A?