06 wrx g4+ CL Lambda issue

[rich]

Hi wondering if I'm being daft or short sighted but when I turn on closed loop lambda corrections on my wrx v10 plug in, the correction steadily removes fuel until the engine dies or it hits the percentage change cap. is this a bug or is there another table I need to set up to allow useful closed loop lambda correction? thanks a lot, lots more questions but I thought id start with a simple one hopefully.... 

[Simon]

Would need to check the lambda average reading, The lambda target table will also need to be set up to suit.

 

[rich]

Hi simon thanks for the quick reply, just to clarify A; does the closed loop correction work only on lambda average and B; the lambda target table being my afr/lambda target table?

 

[Simon]

Yes that is correct assuming you are not using the Dual channel mode available in Stoich Mode

[rich]

ok cool, no I'm not using dual channel mode. so if I check I have the lambda average pulling from the right source,as in my wideband rather than narrowband, it should work as intended? anything else I might have missed?

[Simon]

Firmware will need to be current as there were issues a while back around the Lambda average.

Next step would be to put a copy of the map up or email it with a log and we can take a look.

[rich]

just updated firmware tonight to latest version tonight so hope its not that. ill go have a play, I think itll have something to do with the lambda average being way out because of the narrow band, if I cant get anywhere ill post up me map and a log showing what I'm up against. thanks for the help, ill post me findings either way

[rich]

update for anyone who has this issue, it was exactly as said; narrow band oxygen sensor completely throwing off the lambda average, hence the steady fuel removal. removed the function from the narrowband and now I have a nice steady correction at idle, reacting to whatever target afr I chose using the average of one wideband sensor in the downpipe. thanks for the help again, I may be back with more questions very soon haha

[Adamw]

On 12/13/2017 at 10:37 AM, rich said:

update for anyone who has this issue, it was exactly as said; narrow band oxygen sensor completely throwing off the lambda average,

This is not correct, narrowband sensors have absolutely no impact on "Lambda average".  Lambda average is calculated directly from the "Lambda 1" "Lambda 2, 3, 4....8 parameters (and any that are reading zero are ignored).  You cant assign a narrowband to any of these.

The only other thought I have is you possibly had CLL set to narrowband mode so it was only looking at the narrowband sensor and not looking at the wideband at all.

[rich]

all sorted but thanks for clarification, i literally just turned the input off for my narrowband so maybe had it set up all kinds of wrong. thanks for the help anyways