Commanded air fuel not matching tables

[h2.4]

When logging and populating the air fuel error table, I have noticed my commanded air fuel is locked at .99 lambda, and when I got Wot on a boosted setup, it appears it is defaulting to the "Closed Loop Advanded"> "Full Load fuel Compensation" "fixed at .85 lambda or 12.5 a/f" Even when I deselect it, when I start logging, it is checked again. Is this a bug, or am I doing something wrong. Even in the logger, my Com lambda is reading .85 even when I have it setup as .80 in the target tables. So obviously the math is off in the logged data.

[Spunkster]

Datalogging cannot change a calibration. You need to make sure you are saving your calibration and opening that calibration. It sounds like you are opening a new calibration every time you want to see the calibration.

[h2.4]

I'm just reopening the last tune file from logging and making changes. Then uploading that saved tune to Kpro.

[Spunkster]

Post the files you are referring to.

[h2.4]

Here is the tune file I have been using. Granted it is not tuned yet, as I'm trying to get the Commanded to match while logging. I upload this file, and as soon as I hit the datalog button, it changes from no Wot compensation, to the default of 12.5. I'm not sure if that is what is causing it or not.

[Spunkster]

Post a datalog showing what you are describing.

[Hondata]

Repeat after me: WOT compensation is not the same as target lambda. WOT compensation is not the same as target lambda. WOT compensation is not the same as target lambda. ...

[h2.4]

I was not stating that Wot Compensation was the same as Commanded Lambda. That is the only thing that I can see that is listing a 12.5 or .85 lambda when at Wot. So I was asking if that somehow is causing my Commanded to not match what is in my Target Lambda tables. Spunkster, here is a log of the tune file above.

LamdaNoMatch.kdl

[Hondata]

In the calibration the compensation is fixed at 12.5. The datalog shows 12.46.

[h2.4]

When I graph the log it is flatlined at .85 which is .0015 lamda from being exactly 12.5 afr. And also doesn't follow the low cam test cruise section that is set at 1.08 lambda. It is Reading .99 as target, and .85 at Wot.

[h2.4]

No ideas on this?

[Hondata]

Do you have a KPro4? Do you have a wideband lambda, either stock or aftermarket? (I can't see a working lambda in the datalog).

[h2.4]

I think its a V1 or V2 serial # 05002865 I have an Aem Wideband installed through the Eld pin

Screenshot (2).png

. In my datalogs I am seeing Lambda being recorded in my logs.

[Spunkster]

Using an aftermarket wideband on a version 1, 2 or 3 K-pro will only allow you to datalog the wideband readings and not run closed loop or any protections from the wideband signal. We are aware of an issue in the current software with it correctly reading the wideband input for the ELD.

[h2.4]

But is the target lambda table the reference for Com Lambda? When I'm log compiling data in the fuel correction table, it is not matching what I have for Com Lambda. It's .99 throughout, and .85 Wot or boost. My lambda in the logger is matching my gauge, just not the commanded for some reason.