merlin.oz

My question for the dis-assemblers, is there a way of finding 2-byte Load without doing dis-assembly?

For example, is there a relationship in the ram location that is constant between ECU Load (MUT=1C) and 2-byte Load?

Or can it worked out from the fuel map scaling prefix, or some other positional relationship? This info would be a big help for people like me who are asked to tune Mitsubishis other than Evo 7-8-9.
Evo5-6 and the V6 boys with their VR4's and Legnums spring to mind here and I am sure ther would be others scattered around the globe.

acamus

Unfortunatelly no.
But it can be calculated from universal MUT_C0 * MAF Scale. Unfotunately you cannot use C0 request directly, but you have to hijack some < 0xBF.

merlin.oz

Acamus, do you mean MUT_C0 address minus hex BF = 2byte

Ceddy

The H8s do seem to have the same order for most of the memory locations.

MUT_1D + 3 = 2Byte Uncompensated Load

or MUT_1F + 7 or MUT_1B + 9.

All the MAF H8s I've looked at are like this, but they could add an extra memory location in there on some roms. Looking at the code is the best way to be sure.


For example in the above pic, MUT_1D is F2B1 in the MUT table.
So 2Byte Load would be: F2B1 + 3 = F2B4. (F2B4 and F2B5 would be added to MUT table)

merlin.oz

Thanks Ceddy and Acamus, I'm sure this will help me with the V6 Galants and Evo6s.

And compensated Load?

Ceddy

You can see the order of the Compensated Loads the the above pic. (16 = 2Byte)

merlin.oz

Got it, thanks. This is a great help.

acamus

No I mean MUT_C0 * MAF Scale = 2 byte.

You take address MUT_C0 from MUT table
Hijack some request ID that is less than BF e.g. AA
Place value of MUT_C0+1 at position of MUT_AA
Log MUT_AA with x *MAF_Scale scaling and you should be logging uncompensated 2 byte load.