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
- Attachments
-
- Datalog_B_Fuel_Adjustment_Values.png (61.9 KiB) Viewed 813 times
-
- Datalog_A_Fuel_Adjustment_Values.png (59.42 KiB) Viewed 813 times
-
- Datalog_B_Lambda_Values.png (67.93 KiB) Viewed 813 times
-
- Datalog_A_Lambda_Values.png (67.39 KiB) Viewed 813 times
-
- CalibrationA.kal
- (166.11 KiB) Downloaded 90 times
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