A418t81

iTrader: (5)

Since the 70008 ROM is so prevalent, one would figure that with all the other "ROM mods for dummies" out there that there would be something of the sort for this one as well. There are "how-to's" but they are all wrapped in a layer of technogeek jargon that I had a hard time sifting through so I figured I might as well make a short and sweet example for other people on here like me that don't work on computers for a living, nor have all day to sit on here figuring stuff out (though "fun" at times).

While I wasn't able to rustle up the XML code for the actual MUT table like some other ROMS have, I do have the info to directly alter the important 2 things we are after as far as 2 byte load is concerned.

1. BACK UP your original XML file, save it in a safe place in case you screw something up. THIS DOES NOT MEAN SAVE IT IN THE SAME DIRECTORY AS THE ORIGINAL FILE WE ARE MODIFYING. Put it on your desktop or somewhere similar. Same goes for your ROM as well.

2. We need to add a bit of code to the XML definition file. If you didn't muck with the default installation location it will be found in program files\openecu\EcuFlash\rommetadata\mitsubishi\evo, right click on the 94170008 labled XML file and choose either: open with notepad, or open with wordpad. Either works, it doesn't matter.

3. Add this code to the very end of the existing code, after the last </table> entry and before the </rom> at the very bottom of the code :

<table name="00 2 byte load" address="38062" type="1D" level="1" scaling="uint16" />
<table name="01 2 byte load" address="38066" type="1D" level="1" scaling="uint16" />

A sample XML that works for ECUflash 1.32 and newer is available attached to the bottom of this post in .txt format, use it as an example if you are confused. You may save it as a .XML for direct use in the metadata directory if you like as well

4. Save changes to the XML and close. Now open ECUflash and your ROM. If you did everything correctly you will not have any errors and two new maps will appear under your "misc" group, 00 and 01 2 byte load. Please note you must have your user level set to "developer" to see these maps (user level is denoted under options at the top left of the ECUflash program ).

5. We need to change the numbers that appear in the new single cell maps created, 00 and 01. To alter an entry press the = key, a box will then pop up. For 00, change the number to 35164. For 01, change it to 35165. Save your ROM and then upload it to your ECU (please also note that the burn sequence will take significantly longer that you'd normally expect, don't be alarmed- I almost was). You must use a logger capable of logging 2 byte load, of which both the newest versions of EVOscan and Mitsulogger are.

It should end up looking like this:



*** All of you who update to 1.32 or newer need to modify your XML file again. The process is done in exactly the same manner. The new versions install new XML files which are not retroactively compatible.***


A sample XML that works for ECUflash 1.32 and newer is available attached to the bottom of this post in .txt format, use it as an example if you are confused.

Jorge T

iTrader: (18)

Thanks, Greyson

nothere

iTrader: (23)

Greyson, bless you

Mr. Evo IX

iTrader: (5)

Yea, thanks, I've done this for my IX but havent had the time to read for the VIII for a friend.

Ludikraut

iTrader: (17)

Thank you!!!

l8r)

VT Mitsu

iTrader: (3)

So, again, is this for quicker sampling rates?

Tom

chmodlf

iTrader: (19)

No this does not effect the baud rate (sample speed). It allows you to find out the load that the ecu calculates. This is because with the existing one byte (which consists of 8 bits) storage on the ECU the load value cannot go over 160.

Jeff_Jeske

iTrader: (66)

Is it okay to edit the map and rename the 00 and 01 to something more obvious?

mplspilot

iTrader: (7)

yes

Jorge T

iTrader: (18)

Ok, I followed directions above went out and logged, and got the freak spike. What did I do wrong?

I added this to Logworks openport 1.3 pluging protocols.xml

<datachannel id="#00" name="loadmsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>

<datachannel id="#01" name="loadlsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>

math channel formula used after log when reviewing chart.

MC(ECU_Load;%;0;350) = ((loadmsb * 256) + loadlsb)*10/32

BTW my 2byte and MJs calc load are very similar about 2-3 points apart

mchuang

iTrader: (11)

I have had it spike on me before too, not sure why. In ecu flash after a log it would be something like

Mut Load 2byte

238
240
242
350
241
240
238


On a side note, are you using logworks 3 beta? If so how is it? Is it pretty buggy

Jorge T

iTrader: (18)

dbl post

Jorge T

iTrader: (18)

Good to know need to do more...yep using LW3 still buggy, some features are not active and can't do multiple sessions 'cause it currupts the files. If i keep it simple works OK, if i try to save templates and do overlays it will crash.

Jorge T

iTrader: (18)

2 byte load vs. Calc load w/ MJ formula. In my case very close is it worth it for me, the spike really bugs me, what is it doing to the ECU?

C6C6CH3vo

iTrader: (9)

JorgeT,

I just got the 2byte mod loaded on to my ROM from ECUFLASH and works with evoscan, show me what you did to get it logging on LW (without map,psibar jdm thing) and I'll see if mine does this as well.

???

What load is that occurring at?