RAW Table dump for 2007 Outback 3.0R-AT CALID: D2UH001T

dschultz · **Posted:** Mon Aug 16, 2010 11:18 pm

The script I wrote only works on the 2D and 3D tables because they are mostly all bunched together in the ROM. The temp and MAF scalings, I believe are not grouped with the rest of the tables and the single element values are scattered throughout the ROM, so those you need to go searching for.
If you haven't changed injectors there's no need to change the injector values, just use the MAF scaling to fix up any AF error.

turbofied · **Joined:** Wed Aug 04, 2010 11:38 pm **Posts:** 41

Ahh well that makes sense, Yeah i wasn't planning on changing the injectors i was just interested in finding the table.

So todays update, car was tuned and it worked great afr's changed:
from 14.2:1 @3500-14.0:1 @ 6000
To 13.8:1@3500- 13.3@ 6000

50NM in torque gained across the whole graph and power up from 70 to 85awkw. Just from a bit of fuel.

nsfw · **Joined:** Thu Nov 23, 2006 2:23 am **Posts:** 2565

dschultz wrote:

NSFW wrote:

That's really cool!
Any chance you could make the default scalings for axes just be float values with no conversions?

There is no scaling applied to any axis. Axis in the 32bit ROM are all in float so what you see is the value from the ROM represented in decimal format. The only thing that is scaled is the unit8 and 16 bit table data. The scaling is straight out of the ROM, the same values used by the ECU, you can see the formula in the Table Properties window.
What you will see for instance with the ROM table axis is:
Temperature is in Celsius
Percentage is 0.0 - 1.0
Pressure is in mmHg
Time base might be in microseconds but I have not confirm that yet.

If I open the 3D table at 0x2C918 (5 x 8), the Y axis has a big random number in the first value, and zero in all of the rest of the values.

If I use EcuFlash to create a new scaling (call it "raw float") with a float data type, no conversions, and format of "%.1f" then the following series of numbers appears on the Y axis:

1.6
2.5
5
10
20
90
170
290

By 'scaling' I really meant data type. EcuFlash considers data type an attribute of the "scaling," so I was thinking in those terms. But, I was barking up the wrong tree anyway...

Here's the XML for the scaling that I created:

<scaling name="Raw Float" units="units" toexpr="x" frexpr="x" format="%.1f" min="-1000" max="1000" inc="0.01" storagetype="float" endian="big"/>

Here's a scaling from a randomly-selected 3D table:

<scaling name="UnknownX Axis 0xC061C" units="Unknown" toexpr="x" frexpr="x" format="%.2f" min="-2.14748e+09" max="2.14748e+09" inc="5" storagetype="float" endian="little"/>

The X axis of the table at 0xC061C had a bunch of random numbers in it when I opened the ROM, but the numbers look reasonable when I apply my "raw float" scaling to it.

Do those axes look reasonable for you guys when you just open the ROM?

dschultz · **Posted:** Tue Aug 17, 2010 1:42 pm

NSFW wrote:

If I open the 3D table at 0x2C918 ( 5 x 8 ), the Y axis has a big random number in the first value, and zero in all of the rest of the values.

If I use EcuFlash to create a new scaling (call it "raw float") with a float data type, no conversions, and format of "%.1f" then the following series of numbers appears on the Y axis:

1.6
2.5
5
10
20
90
170
290

I assume you mean 0xC2918?
If so this is what I have on my screen:

Attachment:

0xC2918.png [ 118.52 KiB | Viewed 4964 times ]

It looks like a temperature and load related compensation table.

Are you staying that the endness value is messing up the axis interpretation? All data in the ROM is big ended. I'll have to fix that in the def output (OP) as it never seemed to make a difference on my system.

nsfw · **Joined:** Thu Nov 23, 2006 2:23 am **Posts:** 2565

It might be related to me using EcuFlash and you using RomRaider - probably EcuFlash is just choosing the wrong default when the def doesn't include it. You should try EcuFlash for this stuff, if you haven't already... it opens ROMs way faster that RomRaider, which is handy when you're playing with definitions.

I'm guessing that's the IAT compensation table for the MAF sensor.

Sasha_A80 · **Posted:** Wed Aug 18, 2010 6:43 am

NSFW wrote:

I'm guessing that's the IAT compensation table for the MAF sensor.

You are quite correct...

Phoenix · **Joined:** Wed May 14, 2008 2:26 pm **Posts:** 195

Any further progress, with regards to Def File: D2UH001T...???

Thanks.

turbofied · **Joined:** Wed Aug 04, 2010 11:38 pm **Posts:** 41

It got done!

I didnt go all out but enough to complete the tune.

in the end i got all the fuel, throttle, MAF, avcs, and timing maps

there was about 8 fuel and timming maps each

Phoenix · **Joined:** Wed May 14, 2008 2:26 pm **Posts:** 195

turbofied wrote:

It got done!

I didnt go all out but enough to complete the tune.

in the end i got all the fuel, throttle, MAF, avcs, and timing maps

there was about 8 fuel and timming maps each

Any chance of you sharing all your hardwork with us...?
Pleeeease!

turbofied · **Joined:** Wed Aug 04, 2010 11:38 pm **Posts:** 41

Sure thing.

Few side notes

No responsibility with the definition.

It worked on a local car, check it in ecuflash before uploading, always keep a copy of factory rom!

On a tuning note they love the fuel! 50NM gain in power just from .8 of an afr in the top end!!

Pull some timing otherwise the H6 will continue to rattle its brains out like most of subarus fleet in 2010 :p

Phoenix · **Joined:** Wed May 14, 2008 2:26 pm **Posts:** 195

Thanks turbofied...

Much appreciated...

You mentioned you also found Throttle DWB parameters...
I can't view them with this definition file...

Your thoughts?

Phoenix · **Joined:** Wed May 14, 2008 2:26 pm **Posts:** 195

Also see that there is an Advance Timing Table...?

turbofied · **Joined:** Wed Aug 04, 2010 11:38 pm **Posts:** 41

It was a while since i done the def!

i did find them maybe i didnt do the xml for them...

do you need them?

last time i check the 3 modes sorted out the throttle quite well normal only uses about 50% throttle, sports and sports # use 100%.

Phoenix · **Joined:** Wed May 14, 2008 2:26 pm **Posts:** 195

turbofied wrote:

It was a while since i done the def!

i did find them maybe i didnt do the xml for them...

do you need them?

last time i check the 3 modes sorted out the throttle quite well normal only uses about 50% throttle, sports and sports # use 100%.

Well, the more detail I have the better...
If you can find them, and add them, that would be greatly appreciated...

Pity its such hard work to generate these def file...Errrr

boedz08 · **Posted:** Sat Mar 13, 2021 12:29 pm

Hi Guys..

I am in Indonesia..
I just got 2007 Outback 3.0R with ECU ID D2UH001T..
I have downloaded the hex file.. but using ECUFlash or OpenEcu that the definition is not there..

I know this thread is an old one, but anybody can help me..

Thanks,

RomRaider

RAW Table dump for 2007 Outback 3.0R-AT CALID: D2UH001T

Who is online