Pre-defined calibrations need updating/cleaning?
Posted: Wed Mar 05, 2014 3:00 am
While browsing some of the pre-defined K20A/K20A2 JDM/EU/USA calibrations in the KManager 3.3.0 download package and comparing them to the actual calibration stored on my computer from my car (EU K20A2, Kmanager 3.3.0) I noticed that they have developed quite some differences. A lot of new features have been added over the course of time to the .kal files and this is visible in the data whenever you save a calibration but is missing in the pre-defined ones.
The pre-defined calibrations included in the KManager package are from, what looks to be, very old (ancient?) Kmanager versions, never updated, and are lacking a lot of tables and variables that the later versions do use/expose. I understand that the KManager software has built-in defaults for these 'missing' values so they get added/merged when you load a pre-defined calibration or a (much) older calibration from your car.
However.. Some of the templated/generated information is more than just basic/simple variables, which surprised me a bit.
The later KManager versions for instance also add complete tables for the high and low speed knock handling, knock sensitivity, etc. etc. The (to me at least) curious bit is that these extra tables seem to come from a single standard built-in template in the KManager executable and does not seem to vary between ECU/engine types.
This makes me wonder how accurate/correct for instance the generated or templated 'knock sensitivity' table in KManager really is for most engines or engine configurations..
Are these templated tables thought to be 'good enough' for all more-or-less stock engine purposes or should there really be differing tables for the differing engine configurations? (biggest difference probably between the JDM K20A and the EU/USA K20A2)
In any case: is perhaps an update for the pre-defined calibrations shipped with the KManager installation package in order so they are in sync with the type of .kal file that the KManager executable in the package expects and creates?
Just curious ;)
Oh yeah.. I know I'm not supposed to work with the .kal files directly, but I'm a geek who like to know how stuff works :D
Bye, Arno.
The pre-defined calibrations included in the KManager package are from, what looks to be, very old (ancient?) Kmanager versions, never updated, and are lacking a lot of tables and variables that the later versions do use/expose. I understand that the KManager software has built-in defaults for these 'missing' values so they get added/merged when you load a pre-defined calibration or a (much) older calibration from your car.
However.. Some of the templated/generated information is more than just basic/simple variables, which surprised me a bit.
The later KManager versions for instance also add complete tables for the high and low speed knock handling, knock sensitivity, etc. etc. The (to me at least) curious bit is that these extra tables seem to come from a single standard built-in template in the KManager executable and does not seem to vary between ECU/engine types.
This makes me wonder how accurate/correct for instance the generated or templated 'knock sensitivity' table in KManager really is for most engines or engine configurations..
Are these templated tables thought to be 'good enough' for all more-or-less stock engine purposes or should there really be differing tables for the differing engine configurations? (biggest difference probably between the JDM K20A and the EU/USA K20A2)
In any case: is perhaps an update for the pre-defined calibrations shipped with the KManager installation package in order so they are in sync with the type of .kal file that the KManager executable in the package expects and creates?
Just curious ;)
Oh yeah.. I know I'm not supposed to work with the .kal files directly, but I'm a geek who like to know how stuff works :D
Bye, Arno.