The lambda values displayed after I complete a datalog change if I close/reopen the datalog.
The sample sizes, normal table values, and target lambda values stay the same.
I'm guessing that when Kmanager is reopened, the lambda values are being calculated a different way?
I've included the calibration, along with pictures comparing the different values displayed between exact same copies of calibration and datalogs.
If I close the initial Kmanager window that I did the datalog with, I'll never see those initial values again.
Datalog lambda values change when Kmanager is reopened
Datalog lambda values change when Kmanager is reopened
You do not have the required permissions to view the files attached to this post.
Re: Datalog lambda values change when Kmanager is reopened
The difference was from the way the short term fuel trim was used to adjust the lambda when loading a recording. We've changed this so that the loaded recording lambda records will be the same as the datalogged values.
Hondata