Any idea if those figures are measured in metric/standard units? Also, if this table is used in open loop operation is it likely that it doesn't correct these figures based on air temp? Lastly, when does the ECU run open loop vs closed?

 

These are numbers only .. MrFred sees them as absolute where I see them as Gauge ..

whatever he defines and I define is OUR definition .. as in we try to explain to people what they mean in our own way ..

so saying .. the original programmer of the ROM may have different numbers

As for open/close loop .. there's another table that does this ..

 

Gotcha

It would be safe to say whatever make believe units mitsu uses would also match that of the figures generated by the MAS computations, right?

 

I have started disassembling EVOX , here comes first fruit of it:

52680018 handles it in sub_955AC

OBD Table = 00094B08

mrfred can you PM me Colby's script for those indirect RAM adresses?

 

I put fixfp on my ftp site. If you plan to use it on a non-Evo 10 ROM, it might be necessary to modify the script to point to the correct FP reference address.

What is the sub at 955AC? I don't see any refs to any subs that I've examined.

 

One could call it OBD_CODE_LOOKUP it does the same as 0003A05C in 88590015.

I know i have to find the base address, nevertheless I believe it is the same,
I haven't read the m32r manual completely yet, maybe I will figure out Colby's path.

 

Its pretty easy to find the FP ref. Just look at its location in the Evo 10 ROM, and you'll understand how to find it in other M32R ROMs.

 

Thread from the dead.

Did anyone figure out if the the sp reference (stack pointer) has any relevance in finding addresses and lookups?

Eg,

st R2, @(0xC, sp)


I can't find a specific base like the 80C000 for the frame pointer. Only commands that add, load or store to an immediate value.

I'm just finding code that loads from the stack pointer offset and then saves to the frame pointer offset.
ld R0, @(0x24, sp)
st R0, @(0x6524, fp)