Kprov4 timing below knock calculation K.control 0%

[olarson117]

Good afternoon Hondata,

I'm diagnosing two issues, firstly: unexpected ignition retard on my 06 acura type s I got with kmanager 4.6.1 and kprov4, I am using stock knock control logic.
mods: skunk2 headers intake and exhaust, 50 degree vtc gear, edit: also DW 700cc injectors, mishimoto radiator, and mishimoto thermostat
there is an AEM wideband as well

In the WOT log attached (see end of log), the interpolated main ignition table should be around 27 degrees K.limit logged -3, K.control 0%, K.retard is 6 degrees, and logged ignition is 17 degrees. Using the equation in KManager docs, I would expect 23-24 degrees.

In another section previous, logged K.Limit and K.Control are both 0, but K.Retard rises to about 7° as IGN drops. The knock retard table value in that area was 12°. K.Level stays below K.Thres, and knock count does not increase.

Could you clarify what the logged K.Limit and K.Retard channels represent on KPro4, and what could account for the timing reduction when K.Control is 0%? IAT is roughly 100 degrees, so it should not be retarding timing by more than a degree.
I’ve attached the native datalog and the calibration used to record it.

I have since replaced the alternator, and will be replacing the wideband to attempt to solve a tip in fuel swing issue, which I would also greatly appreciate any advice on. I've seen AFR rise to ~16:1 before recovering to ~13 and then stabilizing, also happens when closed loop is off. What would you check for this kind of fuel response?

Thank you in advance