adding extra cells to get to 300 load
ROM:0002E9D8 mov r4, r0
ROM:0002E9DA rts
ROM:0002E9DC mov.l @r15+, r5
ROM:0002E9DC ; End of function sub_2E9B0
ROM:0002E9DC
ROM:0002E9DC ; ---------------------------------------------------------------------------
ROM:0002E9DE .data.b h'FF < start of MUT table >
ROM:0002E9DF .data.b h'FF
ROM:0002E9E0 unk_2E9E0: .data.b h'FF ; DATA XREF: ROM
ff_2E998oROM:0002E9E1 .data.b h'FF
ROM:0002E9E2 .data.b h'87 ; ç < Request ID 00 >
ROM:0002E9E3 .data.b h'B3 ; ¦
ROM:0002E9E4 .data.b h'FF
ROM:0002E9E5 .data.b h'FF
ROM:0002E9E6 .data.b h'87 ; ç < Request ID 01 >
ROM:0002E9E7 .data.b h'B2 ; ¦
ROM:0002E9E8 .data.b h'FF
ROM:0002E9E9 .data.b h'FF
Any pointers would be great.
MB
well the last couple of ROM's ive been looking at have several sections of 0xffffXYXY's before the real mut table.
sometimes its easy to think the first section is the mut table...
sometimes its easy to think the first section is the mut table...
No reason not to run 2 byte load Oracle, it won't mess anything up. It wouldn't have been any use on your original IX turbo setup with the scaling at 300 with your HKS induction that lowers your load values. As long as you're getting predictable ignition and knock sums I wouldn't bother, but I suppose it is all more data to gaze at if you are curious, and might reassure you that you're ignition isn't falling off the edge of the world and put you at risk of rediscovering America 

Hmmm Data...
one of evo guy in local showed me the very easy way to add additional column in ecu load.
first click on high or low octane/fuel map, click 'edit', scroll down to 'edit map definition'. then you will see 'data values...', 'x-axis load', and 'y-axis RPM'.
if you change 'elements' under 'x-axis load' then you will get additional column on load section. for example, my elements is 18, if change it to 20, then it will give me 2 more columns for additional load.
i don't know if this is covered in the past, i am not sure if this is the right way to do it. expert can comment on it.
thanks all.
first click on high or low octane/fuel map, click 'edit', scroll down to 'edit map definition'. then you will see 'data values...', 'x-axis load', and 'y-axis RPM'.
if you change 'elements' under 'x-axis load' then you will get additional column on load section. for example, my elements is 18, if change it to 20, then it will give me 2 more columns for additional load.
i don't know if this is covered in the past, i am not sure if this is the right way to do it. expert can comment on it.
thanks all.
So if you hit load values say 20 higher than the max, is there something like a fuel cut, I noticed when tuning that on one run I hit 322 load and it acted just like fuel cut, I have not rescaled yet. So my max is still 300.
That would make sense, I was working on my race gas tune, as well as playing with the HP/TQ logger and hit a little over 29.2 psi(JDM map) where the "Cut" seemed to happen and it recored 322.2 2 byte load.
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
I agree, I've had plenty of cars come to me going way over the 260kpa load on evo 8's and 300kpa load on evo9's without hitting fuel cut.









