KTuner wrote:If it's grey you don't have the option to manipulate it. If your ECU software doesn't have the monitor enabled by default it may be missing settings that would be needed to enable it and have it run properly anyway.
Focus on your knock control movement.
I understand to focus more on knock control movement in this platform. I suspected that the default setting in the ECU software doesn't have this monitor because it was also disabled by default in the other platform but this platform can enable/disable the OBD II sensor for misfire events/knock count. I am not sure how that platform did it.
My concern raised when I made some changes to my calibration. I used KTuner Starter Dual 21 PSI as basemap, which has more aggressive ignition base below 3000 RPM compare to my custom calibration.
In an instance, I saw 94% and 95% K.Cont and a few K.Cont higher than 79%. These were blips less than 1 second occurrence and they were no visible in the datalog playback. It was only visible when I read the CSV datalog.
In few instances, I saw weird K.Control went to 0%.
I accidentally deleted the kdlg datalog but still keep the CSV datalog.
Would you mind to take a look and advise if this is something that I need to worry about?
This is link to the datalog:
http://www.mediafire.com/file/83f1h5bpv ... 0.csv/file
Thank You.
