Hey guys,

This forum has given me a lot of knowledge. So, it’s my turn to give back. I will describe what you have to do in order to get two byte load working on a 94170014 EVO8 ROM. Please only do this if you are running this ROM because I cannot say whether this works on other ROM files or not!

I have not had a chance to test this on my own car yet (weather sucks in central PA right now, so car is in garage) but mchuang has and has verified it works perfect!

Before I begin big thanks to Bez Bashni, MalibuJack, mrfred, mchuang, jcbanks, burgers22, evo4mad, and many others I cannot remember right now.

IF ANY OF THIS IS WRONG PLEASE POST UP THE CORRECT WAY AS I DO NOT WANT TO POST WRONG INFORMATION!

1) Download this XML file that incorporates the new MUT_BAUDRATE (speed up logging) and MUT_TABLE from your ROM. This XML files define where the MUT_BAUDRATE is set at so you can speed it up to match you settings in Mitsulogger or EVOScan to getting more data plots for better and more detailed tuning numbers

XML File (Right click save as…)

2) Once downloaded set your user level in ECUFlash to developer (DO THIS AT YOUR OWN RISK! You now see tables you will not usually see!)



3) Now close and reopen your current flash. You will now see the MUT Table and BAUDRATE2_MUT (here is where you change what you want your BAUDRATE to be for logging, Bez has successfully logged at 62500! I would set it to that and not go any higher.)



4) What we need to change is the address to which the MUT0 and MUT1 address’s are pointing to so we can log the load address with these variables with our logging software.

5) To do this you have to open the MUT table and change the first to MUT address’s to 895C and 895D as shown below:



6) Once this is done flash the car and make sure you are logging MUT0 + MUT1 and this will give you your two-byte load value. (EVOScan v0.99 already has this defined and I believe Mitsulogger does as well)


Again, please let me know if any of this is wrong is something is missed so I can update it correctly for everyone.

Happy logging,
~Zach

 

glad you wrote that up, the 94170008 and the 94170014 seem to be pretty similar.

 

Does anyone know if my x and y reference points on my MUT table are correct, as shown in the picture above? Sometimes I see others with different rows and columns.

I don't think it really matters does it? If it does and mine are incorrect what would be correct?

~Zach

 

Are they the same address's?

I think the MUT table is starting at a different address but what about the load address, they are the same location right?

~Zach

 

Ill have to check on my laptop when I get home, at work right now.

 

So what about 70008? Anybody have the XML lines to add to get the mut table? I've seen it for lots of other ROMs but not for the most common, go figure.

 

I think it is documented in the disassembly section on www.aktivematrix.com. Maybe Malibu can help you out, he has that particular rom and actually is one of the main contributors to the ecu development process.

 

what about the 96940011 ROM? Is process the same? I would think it prolly isn't, but you never know.

I am currently using Logworks2 for all my datalogs, mainly because it doesn't have any bugs and samples my LC-1 Wideband at a very high rate(so i can see misfires ect. easily). I have EvoScan but don't use it at all right now. I wonder how hard it would be to have jfitzpat(innovate) write code for the openport 1.3m plugin for logworks to import 2 byte load into logworks after the ROM patch?

Any help regarding this issue would be greatly appreciated guys.

CJ

 

would you, could you post a picture of a graph with a misfire exposed?

 

Its already posted somewhere in this forum for logworks. But you still need to find your mut table for your rom.

 

i have searched and searched both here and aktivematrix and have found no answers for my rom..... What do i need to do to find it myself??

CJ

 

I just formated my HD on my laptop and did not save/backup old datalogs. I'm an idiot....because i have about 300 of them that have a lot of very useful info.

A misfire will show up as a very sharp and fast lean spike. You cannot see a spike like this unless you are logging at a very fast sample rate. The Innovate LC-1 WB has the fastest sample rate of any wideband, and in order for you to take advantage of this fast rate, you have to use Innovate's LogWorks2 software, which was designed to capture this WB at it's intended sample rate. Other loggers will not sample the WB this fast, so this is why i choose to use LW2, rather than another logger. You can import openport data into logworks, so this is my weapon of choice because WB readings are one of the most essential tools in tuning.

i wish i still had a log that i could screenshoot for you to see for yourself! Sorry about that.

CJ

 

Sorry guys I cannot help those out with the other ROM's. I got all this info from this forum and Aktivematrix. It was all in reference to 94170008 ROM, mchuang and others just helped us convert it to 94170014.

Below are the thread's that help me put this together:

https://www.evolutionm.net/forums/sh...d.php?t=261465

https://www.evolutionm.net/forums/sh...d.php?t=262021

https://www.evolutionm.net/forums/sh...d.php?t=234060

http://www.aktivematrix.com/forum/viewtopic.php?t=20

http://www.aktivematrix.com/forum/viewtopic.php?t=222

http://www.aktivematrix.com/forum/viewtopic.php?t=227

2 things need to be found in your ROM in order to do this mod:

1) MUT Table
2) Load address's

~Zach

 

Since I am a nice person here ya go. This is the thread https://www.evolutionm.net/forums/sh...d.php?t=234060

Look at post number 69 on page 5 if you have any questions about how to modify it ask jfitzpat he is the logworks king lol

 

Awesome..thanks for your kind help.

Now, if i could only figure out how to find what i need to find in my ROM!!!! I noticed not many people are using 96940011 at all....i wonder why that is? Arent all the usdm 05 evo 8's the same ROM?

CJ