RomRaider

The "Commanded Fuel Final" is a fairly recent addition to the logger and affects the newer ECUs. If there are compensations on top of the fuel map then there would be an error if one tries to line up the tailpipe AFR to the fuel map. From what I have seen so far, the difference between the Commanded Fuel Final and the fuel map is mostly in the spool up region, some sort of acceleration enrichment. I tend to ignore that region when scaling MAF. Instead, I do part throttle runs to get to different MAF readings once the boost stabilizes.

Before to scaling OL, the Initial and Max WGDC must be set in 0 ??

i keep getting

run time error '11':

Division by zero on step 7

as soon as i press Interpolate AFR



any ideas?

Hi Leslie,

I've recently scaled my maf to a new higher flow intake and I've come accross an issue with learing in open loop...

Car = 2010 STI

When I reset the ecu or flash the car runs perfectly for about a day. Check the learning view and the tables A B C are within 3% and D is 0 but when I log something in open loop fueling I can see learning being applied in the log and its causing my maf scaling to run a bit lean.

I have the CL to OL transition set quite low at 50

Do you know the learning im refering too and can it be turned of?

Cheers

Dave

What is the difference, if you scale the maf to read the open loop table, or just adjust the values in open loop table to get the afr that you want without touching maf scaling? What is the good and bad with this?

Had similar issues on my 04 FSTI then found a maximum mass airflow limit (g/s) above which AF Learning is not applied. Assuming your rom is the 2010 USDM STi AZ1G701, this maximum air flow (g/s) limit would be at 0xC921C datatype float. The stock setting is 80. Try set Max Range C / Min Range D slightly higher at say 60g/s and then the Max Airflow Limit at 0xC921C just below 60g/s. Usual disclaimers apply
Doing this on my FSTI has resulted in a 0 AF Learning in OL and more consistent OL Fueling

anyone?

I used this utility because I was running leaner up top due to higher flow but after running it all the new values put lower g/s values up top and now it seems I am leaner then I was before. I used 3 WOT runs from 2k to redline and the input from my LC-1.

I'm not really sure what the hell is going on, it did account for the higher flow down low and helped smoothed it out but it screwed it up on the higher end :/

Anyone have any input?

bump for answers

You need to look at the AF Learning D range. If it was positive values when you did the values, it is adding fuel on boost. +5% is 0.735 AFR richer on boost so once you load in a new tune, it ends up running much leaner

A few people know I turn off the D range learning as it helps scale in the on boost fuel table for more accuracy.

I have a problem to import my cvs file that is made by romraider, because it pulls all information into one cell. Is there a quick fix for this?

I wanted to share my experience with a Full Exhaust and headers from Tomei and a perrin inlet pipe:

I had Problems that the Fueltrimms in LV looked ok (around 1%) but when i did a WOT i expirienced a much leaner mixture than in the Maps Stated (i was running the stock map!). I searched a lot for Vacum leaks. The only thing that would explain lean condition was a leak between the MAF and the Turbo. Because if it would suck more air than it messures it would be to lean. If a leak would be after the turbo, the air would escape in Boost, which would lead to richer mixtures at WOT. After some logs i saw that the Engine Load (g/rev) exceedet the Original Open Loop Table by far. The Table Maxed out at 2.53 ive hit 2.85 g/rev with just the Header, perrin inlet pipe and the Full 3" Exhaust system. The AFR where pretty correct until they exeed the MAP in the ECU. Iam Pretty sure it has something to do with that. Ive tried yesterday to use a map which goes up to 3.2 g/rev. Sadly my MAF Scaling still seems to be incorrect (Picture).

Hey Doriangrey.

First of all seeing your graph i would rather straight of the bat increase your Maf scaling by about 8% from the G/s at around 3k rpm to the end, just incase you start knocking, rather work from a richer base than a leaner one. In your fueling table you can also increase your g/rev columns and scale accordingly if you are going over max value there.

There are a couple of Ol Maf scaling utilities on here that you can use to get the corrections perfect, and smooth your maf g/s graph. Not sure if you using any.

In steps 4,5,6
I pasted the fuel table from ecuflash (not RR) in the bottom of "AFR Target" & it seems that the spreadsheet had interpreted the top row & first column of the AFR table as the y/x axis, rpm & load because they appear in white rather in colors as the rest of the AFR table!
Then I tried pasting a load row & an RPM column first & the I pasted the AFR table inside to no avail, when clicking 'align & move copied table' it would appear without load/rpm with the first row/column of AFR values showing in white!

What am I doing wrong? I'd appreciate your advice

I've successfully used this guide to tune my WOT open loop scaling, however I've been having trouble scaling the lower load regions of the MAF table. Since I'm using the Carberry ROM, my scaling table uses MAP instead of Load, which isn't a problem as I can just log MAP instead. What I'm wondering is if it's possible to enable full-time Open Loop and use my wideband to scale the entire MAF range and then just always run open loop. So far I've enabled full time open loop and logged while idling for a few minutes. Then I used Airboys sheet to get the new MAF values, flashed the new map, and my idle was on target. I've also scaled the WOT region of the MAF table. To scale the rest of the table should I just find a long stretch of road and hold the throttle steady at different MAFv regions? I'm guessing I can't just start the logger and drive around like normal because everytime decel-fuel cut or tip-in engages the values will be thrown off.

edit: Nevermind. Instead of trying to complicate things I just scaled it the normal way using closed-loop.