RomRaider

It means that your MAF < 50 g/s is almost dead on, but your MAF > 75 g/s is off.

The in between is almost impossible to scale with WOT. You'll need to do a high partial throttle log for that.

In Airboys spreadsheet it's showing AFR errors at 2.4V of -10% (in pic I posted) and in my ROM 2.4V is around 27g/s. Why doesn't learning view show -10% A/F Learning #1 C (7.5-37.5) instead of -0.98%?

I'll get some CL scaling over the next few days and try and get 38+ sorted, but I'm still a little baffled why learningview doesn't show -10% when Airboy's does?

2.4V is right where you stepped on the gas pedal so there will be tip-in enrichment. As for the rest of the range, what does your MAF table look like relative to the stock table?

Ah ok, so the initial rich spike is from tip-in, but from 2.6v on the MAF scale is out? Starting to make sense now, and since 2.6v = approx 41g/s it won't show in Learningview, is that correct?

Here is my current MAF scaling - sorry for the akwardness of posting it:

I thought you had the MAF and fueling sorted out a while back? What has changed since?

Here my results for a STI X EDM of 2008 collector APS and exhaust NVIDIA,
http://www.coplan.fr/daniel/cartos/Spreadsheet/Closed_Loop_Fueling_STI_X_EDM.zip

I have a problem. It is necessary to add 0.73 ms of latency in table "injector latency"? is big,no?

No.

You logged IPW and not IPW direct. IPW includes latency.

For STI X, there is not option IPW direct

IPW direct it's equal IPW - IPW Latency

And the size injector it's ok or not

Thanks

Can you post your rom or send me a link to where the stock rom is located?

Yes, IPW direct = IPW - latency. I believe the ecu calculates IPW direct and then adds latency to get the IPW that it applies to the injector solenoid.

Here my rom
http://www.coplan.fr/daniel/cartos/AZ1G202G.zip

it's better, I think now
Closed_Loop_Fueling_STI_X_EDM_V2.zip

Nothing on the intake side had changed - however I had to change back to 98RON fuel from E10 as the fuel station stopped selling it so and that is when things went a little crazy.

When the MAF was scaled originally, the car was running E10, which I think may have skewed the MAF scaling results somewhat. I prolly should have dropped my injector scaling down a fraction to compensate for the E10 (like the E85 guys do) and then scaled my MAF - but too late now.

I have left the injector scaling/latency alone and set as they should be for my DW750s and have just worked on MAF scaling now to get it sorted. My closed loop scaling seems spot on now (generally less than +/- 1%) so hopefully it is just open loop scaling as suggest that is causing the problem.

My car is in at the workshop at the moment (trying to bug track a cylinder 1 misfire) and so I'll have to wait until that is sorted until I start OL MAF scaling.

Sorry. I forgot that IPW direct was changed to IPW (4-byte). It looks like you found it correctly.

Did you modify your ecu defs to support your rom?

Yes

he would also have to modify the logger defs in order to access extended parameters since his ECU isn't currently supported.