Change to WOT Lambda Adjustment causes extended Closed Loop

[Gernby]

In order to test the linearity of my AF sensor, I created 1 calibration that had a flat AF curve of about 12.5 while the WOT Lambda adjustment table also had a flat 12.5 target. Then I made a second version of that calibration with the WOT Lambda adjustment table that targets an AF starting at 14.0 at 2600 RPMs then slowly enrichens at a linear rate to 12.0 at 8500 RPMs. The test went great, and my AF curve did show almost exactly that (AF sloping from 14 to 12). However, the really strange thing is that the ECU stays in closed loop all the way to about 6200 RPMs even though I'm at full throttle, and the STrim value goes up and down a bit during that same time. It seems that it's actually trying to use the primary O2 sensor to hit my target! Why would the ECU ignore the WOT determination settings just because I altered the WOT Lambda Adjustment tables?

I've attached both calibrations with datalogs.

FP-S2K-US-30040
Firmware 1.1.8.5
2008 S2000

[Gernby]

It turns out that this is just a cool Easter Egg, and there are 2 different modes of closed loop!
http://www.hondata.com/forum/viewtopic.php?f=29&t=13211