I'm actually starting to wonder if (as was suggessted) I saved a duplicate 88590015 originally, since it was the first one I was working with, and it had the original instructions and that was what was being referenced, since it would have been saved in the same directory. Sounds like you guys hit the nail on the head. Again, many thanks. I'm just baffled as to why I couldn't fix it by deleteing it. I even delted the so called "shadow copy" that Vista is known to store.

I hope I don't have problems every time I try to add code.

Any suggestions as to how to approach it?

No matter what, do I save any updates to the code in different locations and then move them as needed, like I did here, essentially - that being the moral of the story?

Anywho, off to enter MUT addy's.

Thanks again guys.

I have been running into this problem everytime I do it with vista. I have not tried it with a different opperating system. Good news is now that you have a good directry to put them into you can put new ones in the same and it should work. Let me know if you figure out how to get the changes to express with out playing with the dir.

MUT3D2byte up and running!

Thanks to everyone who has contributed to make these mods a reality!

Changing the directory seems to be as simple as putting it in a different folder. Future mods will confirm this, hopefully. I'll save anything new into that new folder and change the directory.

Out of necessity, I actually had to roll back to 1.34 because of the 2.0 cable driver causing issues - I use a 1.3 and simply cut the 2 updated xmls I desired and added them to the folder, using care not to include any of the 1.34 version Evo9base, nor the 1.34 88590015 non-MUT3d 2byte xml.

It's referencing only the 1.40 Evo9base with the updated xml as well as the 1.40 88590015, again with xml updated.

Thanks again to all! :mitsu:

Hello guys,

I gotta say I'm kinda lost with all that 2 byte stuff... :crap: I'm tuning an EVO 8 with a 96530006 ROM...modified with Tephra's latest V5 pack. And my main problem is to know which load value I should log to have the most accurate map tracing tables (to match ignition and fuel tables).

Beside that, it seems that the 2 byte load is needed in order to go above 255 in load value...as far as I have understood. Right?

So, using the Tephra pack, I've chosen a 2 byte to 1byte load factor of 1.2 which seems quite fine for what I need.

When I log with Evoscan, my "load MUT 2 byte mod" values are slightly lower than the "calculated load"...Nevertheless, is it the one I should rely on?
But anyway, both of those load values seem kinda low in regard to the boost I'm running... Is there a value/factor which needs to be changed in Evoscan to match the 2 byte load factor of the Tephra mods?

Thx for making things a little bit clearer... :helpme:

you can either use LoadMUT2Byte or 1byte load.

if you are using 1byte load you need to get the xml for evoscan from my thread...

Ok so I just need to paste the modifier 96530006 xml file in the evoscan directory (C:\Program Files\EvoScan\EvoScan v2.5\ROMS)? That's it?

And it will be ok to read the proper load value? Great...

Thx Tephra. {thumbup}

This load thing is driving me crazy... :crap:

Evo 8 fitted with several mods including an Evo 9 tubby, pushing 1.5bar up to 5,500rpm and then gently decreasing until 1.35 are reached at 7500rpm...and the max load reading I have on evoscan is 240 something!! :confused: It seems kinda low IMO...

Nevermind I rely on "load MUT 2 byte mod" or "load 11bit4", the reading are exactly the same...

Running with the AVC-R on "off", I have approx 1bar to 1.1bar boost and a max load of 200-210... which is ok when compared to the load value I have running more boost...but which still looks low.

What do you guys think about that? Am I expecting too big load values (hence my surprise) or is there really a problem in the readings I have? :helpme:

EDIT: changed the values in the 3D MUT table in order to have 2 byte load... Helped a little as the max load value I now have with my AVC-R off is 225... But I still can't go above 240-250 on B mode...
Should I change the load factor in the Tephra's options?

note: with std xml and non tephra modded bin, I was easily hitting 255 on load 11bit4...

96420011 MUT 3D address = 3a0bc.

anyone know the evo IX 88590013 mut address and 2 byte load? thanks in advance.

Honestly I think the newer 1 byte load from Tephra's version 5.10 patch makes life so much easier. It just combines the 2 MUT load bytes together into one loggable byte, then just add the extra definition into EvoScan and voila!

yeah in addition 2byte rpm is pretty useless... just slows down logging, regular rpm is fine.

2byte airflow is a good one, and I dont plan on 1byting it anytime soon.

but i would still need to setup the mut table to get the 1byte load working right? so i would still need the address.

well there is no 5.10 for 88590013 :)

but in 88590015 the MUT (40 or 41) is already programmed with 1byte load, u just need a recent version of evoscan and it will *just work*

thanks. could i switch his rom from 88590013 to 88590015 without any issues?

should be fine.

just copy all your tuned maps inc immob

Thanks. ill try it out.{thumbup}

Does anyone know the MUT address and 2BYTE adresses for 97250001?

So we just buy evoscan and with your version 5.10 of the 88590015 rom, the load we be accurately logged? When does one have to change the 1byte mod number of 1.2 in the version 5.10 of the 88590015 rom?

yeah:

- run v5.10 or above of my mods
- get evoscan
- if evoscan hasn't already got the 1byte load entry then add it
- log accurately :)

the 1.2 needs to match it both evoscan formula and in the rom, it just is a multiplication factor that limits the maxload evoscan will see ie:
1.0 = 255 max load
1.1 = 280 mad load
1.2 = 306 max load
1.3 = 331 max load

1.2 should be good enough for 99% of users :)

Somebody please confirmm the right codes for 1 bite and 2bytes mut table for 88840017and for 88840013 also.

V6 seems to have others values than al\lupo confirm at the start pages of this thred.

Give me please correct values for stock rom for both rom versions

Thanks

Can someone assist me in finding 2byte load for 95850000. It's a 2004 JDM Evo 8 RS rom. My definition is included in the zip. Thanks for the assistance in advance

i'm not having any luck logging 2byte load on 96260009. it records 0. can someone confirm these are the correct MUT values for this rom.

MUT 00 = 0x8960
MUT 01 = 0x8961

they look wrong.

use 0x8984 and 0x8985

these were correct for the 96260009 rom. someone please add to first post if possible. thanks dave!

bump

what do you need to do in evoscan to log 2-byte airflow?
I dont see how just adding this 3d mut table makes evoscan log airflow?
you have to enter some table stuff right?

well seems like 2-byte airflow is logging.
my question is this though. because we are changing the MUT in the ecu. Will this change what airflow the ecu was using for its calculation for injection what not?

Does anyone know what the 2 byte load is of my ROM? I can find the 2 byte RPM

20030011

2byte RPM
MUT 02 = F0A8
MUT 03 = F0A9

but, the 2byte Load I find, is F008 and F009, but it seems incorrect.

Can anyone help me to find it out please? It's H8 CPU, and same as EVO 5/6.

anyone have the MUT address for 96260009?

Thanks

These don't seem to be working for me:

96940011
2byte load
MUT 00 = 899A
MUT 01 = 899B

Bump, anyone have luck with these?

I have been on 96530006 for a while now, but from what I remember, that worked fine for me on 96940011.

Agreed with l2r; while I haven't looked at 96940011 in a very long time, I don't believe I was using anything other than those two addresses. What I don't know is whether those addresses are temp and/or baro compensated, or whether they're a "raw" load value (see the wiki page for 96530006 for an example of the four possible two-byte load values).

Any reason you (well, I'm assuming your customer in this case ;)) can't just run 96530006?

I converted him to 96530006 but we were having a bunch of stalling issues so i was forced to go back to 969. but i attempted to get 2 byte load working and nothing. Not sure what the hell is going on. Sigh....

Edit: just for reference i have successfully converted 1 or 2 other '05s to 965 without issue. One was having a stalling issues but it may have been an intake issue. He has cams and we ended up dialing the idle up and has no problems now.

Are you setting the BISS when switching to 96530006? Usually, that's all you have to do with the idle/stalling issue.

No, i always read never to touch the BISS.

The stalling issue is VERY weird. The car idles file but if you are rolling and push in the clutch the car tries to die. Always seems to be when rolling but not all the time, only intermittent.

Use Evoscan's SAS mode and set the BISS. You need to have proper ISC steps at idle in order to give the ECU the proper adjustment range to catch idle, etc.

People who told you not to adjust the BISS were simply uninformed and didn't have the right tools/method of correctly setting the idle.

Thanks for the info, i will try that. What is the proper ISC steps at idle? Me thinks we need an official How To on converting to 9653 ROM. I will write it once i get everything working on this car

I'm going completely from memory here, but I think somewhere around 20 is where you want your ISC steps at idle.

is it documented anywhere? I could always try to match it with the stock rom or another evo to make sure it is equal.

its in the FSM...

but 20-30 sounds about right from memory... higher with AC on.. :)

Anyone have 2byte info for 22580007 ?

Can you post the ROM? (There is a 100 kb limit on file size.)

...

I'm trying to load the 3D MUT TABLE and it's saying a can't save because of how the file ends with </rom>. Does that make any sense to anyone?

You did paste in the mut xml entry before the </rom> part at the end didn't you?

Yessir

The newest ecuflash version (1.42) I believe has mut tables done already.. Just opne your rom in ecuflash and change the correct adresses for your rom in the table..

OK... have version 1.41 ecuflash and my ROM number is 96420008. I installed the MUT 3D table just fine with the following codes on the first page, but how do I know it's working in Evoscan?

Should the 2 byte load, 2 byte RPM and the 2 byte Airflow show up in the list of stuff to log?

i opened up my evoscan and the boxes where there to check.. but i could swear it's 'cause i added something before...

or does the new version i downloaded come with it already? sorry. i haven't touched evoscan in a while.. 'been trying to get my ecuflash rom right.

anyway: it's listed as boxes i can check to log.

still trying to find what 2byte load for this rom ID needs to be changed to. Some help please...even willing to donate a little $ for the assistance.

attachment in this post

ill look it up for ya :)

try

0xFFFF8960 (and 61 obviously)

Thanks a lot Tephra...will test tomorrow and send a little something your way for the help.

yup no dramas.

let me know if it doesn't work!

Well damn, I must be doing it wrong then. I don't have boxes to check....In the MUT table I put the following in....right?

96420008<------------the ROM I have

2byte load
MUT 00 = 8984
MUT 01 = 8985

2byte RPM
MUT 02 = 8962
MUT 03 = 8963

2byte AirFlow
MUT 04 = 89E2
MUT 05 = 89E3


Attachment 295484

this seems correct. OP should update the first post with this new info.

So I cant do the load and airflow with my rom# 96420007..just rpm? Any help would be great


2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 = 8962
MUT 03 = 8963

2byte AirFlow
MUT 04 =
MUT 05 =

Too bad my name wasnt DB...I would have gotten tons of help!:lol:

it will be the same numbers as 96420008...

Thanks tephra

Any one with info for 89970010?

Can someone confirm all the 2byte formulas for Evoscan. I am getting some very weird, very high load values in the 2 byte column, like 100 points more that with the regular calc load, or ecu load. It is making tuning rather difficult. I have verified that the ROM 2byte load mut table addresses are correct, so that leaves evoscan miscalculating or reading the signal.
Here is what I have in EVOSCAN V2.5
EVOSCAN Formulas as follows:
2byte load 0.3125*x
2byte RPM 1000*x/256 (correct per post 1)
2Byte AIRFlow 6.29*x/64

Thanks in advance.

Hey guys, i just put the patch in for 2 byte and for some reason when i pull the mut table up in ecuflash to try to change the values for mut 00 to start it's not changing the value... I'm putting in '0x'6B42 for rom id 88590015 for mut 00 and the value is staying the same when i hit enter.. I am a newbie and tried everything to get the code changed.. Please help thanks!!!

you are right clicking with your mouse and selecting "set data =" or something similiar is the command. Should work. Also, make sure you are at the developer level.

Any one varify my formulas yet?

I am getting weird reading with these values on 2byte LOAD and RPM as well. :confused: I am using 88840016 ROM. Any help much appreciated. Shall I change something in Evoscan? I checked all the formulas and they are correct. I am running EvoScan v2.6. I am lost here....

Somebody can help me please with 88580015 2 byte addresses?

Mut table is into the same position with 88580013 and 14 (373c4) but the address for load 2byte or rpm2byte are not the same I think.

I get strange readings when I log 2byte

Actually, the MUT table is at 374DC on the copy of 88580015 that I have here.

The 2-byte addresses all look the same as 88580013.

Are the 96531706 and 0706 the same as 96530006?

Yes, I believe so.

Yes there are both "builds" of the 9653006 rom...

Guys the current values used for 2byte load for 96260009 -
MUT 00 = 0x8984
MUT 01 = 0x8985

I am wondering if these are the 2-byte LOAD_Raw (no temp compensation) values when we should infact be using 2-byte LOAD_Temp_and_Baro_Compensated -
MUT 00 = 0x898A
MUT 01 = 0x898B
....

MUT Table address="33A7c" - need to verify
AT MUT table address="7F784" - I think it's same as EVO 7.5 GTA

Thank you, will give it a try.:)

Does this look right?

http://www.trccc.org.nz/images/MUT.jpg

Yes, but I hevn't any mods like 2 byte load, RPM ...

Any chance of getting 2 byte load for Evo6s?
ROM 24430002 or 25570000

It would defo be greaaaaaaaat! :)

need a little help here setting up my friends JDM IX (80920002) to log 2 byte load. I know that this romid is not very popular and I have to inherit from 88570008 but when I make the changes in the MUT table (00=0x6b12 and 01=0x6b13) 2 byte load reads in the 1000xs and my timing goes static and logs at -20.
Not sure how that affected logging timing because it looks up request id 06.
Not sure if this info is necessary but I'm using V1.29a, with evoscan v2.5
Anyone know whats going on here?

^^anyone know what the MUT values are for logging 2 byte load on 80920002??

2byte load for 89970010
MUT 00 = 0x8B0A
MUT 01 = 0x8B0B
need to check it

mut 00,01,02,03,04,05 works like in math where the first number is the x axis and the second number is the y axis right?

No, first is the Y axis and second number is the X axis. That's why "MUT0X" is the first scale in the y axis, it's for all MUT addresses that start with MUT0. After that replace the "X" with the number in the X axis for the cell you're looking at.

+1 need also

2byte airflow (working)

6B6E
6B6F

Taken from this thread:

http://www.lancerregister.com/showthread.php?t=134923

great info

With the addition of the MUT 3D table, I take it that this page -
Evo IX 2-byte Load & Lean Spool for Dummies - is now incorrect for enabling 2-byte load?

Some of the older threads are a little confusing for a newbie, especially if they contain information that is no longer relevant.

can anyone tell me what the original eval formula was for the Load MUT 2Byte ??

Thanks

feel so dumb posting this twice :crap:
0.3125*x

I was recently tuning an Ev08, with 94170015, at some considerable altitude and discovered that the 2-byte load address (895C,895D) was incorrect.
Or more likley, an un-compensated 2-byte load address.
The Load_IAT_BARO_16 address is at 8960, 8961.
Perhaps someone in Colorado might like to test this also and confirm/refute the result.

This got me wondering if any other addresses as listed in Jacks first post may in fact be un-compensated 2-byte.

lol, thank you twice {thumbup}

Does anyone have the 2 addresses for 2-byte load for 96260007...I tried searching and found this: but I just wanted to confirm what the second address is, 0xffff8985 right?

Anyone??

how can we log 2byte baro+temp compensated load with v7 9653 ? What to set in the Evoscan ?

bump please :)

I know that :

2-byte LOAD_Temp_and_Baro_Compensated
MUT00 = 898A
MUT01 = 898B

But how can I logging MUT00 and MUT01 request for load ?

Set request id : 00 and request id2 : 01 and for eval the 0.3125*x will be ok ?

bump for an answer to #291

bump ,I also so would like to know the eval formula i have tryed 0.3125*x and the numbers i get form that are incorrect

Yes it is uncompensated, I use the following evaluation formula in Evoscan

(x*0.3125)*([baro]/100) and it seems to log fine at 5000-7500 feet above sea level....

**************this is only for ROM 94170015***************

but I would think that it would work on others also....

George

So what would be the calc for air temp if we used the uncorrected load address? I'm aware I could just use the temp & baro corrected address but I haven't yet found it for my ROM.

Tried searching but didn't find the right answer...I'm looking for the 3D MUT table address for 96260009.