High K.Count.3 on 2.8.2.0

[Lerlo]

Hi,

Is anyone experiencing high K.count.3 on 2.8.2?

I realised after the update, my k.count.3 is really high, like 30+ when the same map was 0-2 on the old version.

All the other cylinders read 0 though.

This has caused my knock control to be 90% on 98(RON)

[Hondata]

For what vehicle? In that release we did not change most of the calibrations apart from the 2016+ Civic.

[Lerlo]

Hi Hondata,

Thanks for your reply.
Ive got an FN2, I think its just coincidence that I had higher knock count upon update.

I back tracked datalogs 2 months ago and found high knock values as well. Its funny that it came and gone.


One question though:
I noticed everytime there is a K.count, knock control will increase and take forever to come down.
I also read in the manual that adjusting the knock sensitivity does not affect k.count.

So how do I desensitize the knock sensor such that less k.count is registered.

My k count is only 5-10 knocks for a 30min drive and mostly in low rpm (1500-2550) range. Im quite sure its a false knock.

[Hondata]

You need to isolate where the knock is occurring and adjust ignition timing if possible. The other thing is that the rate knock control will come down depends on the engine load and knock sensitivity, so if you have high load and high sensitivity without any knock, control will come down. At low load and/or low sensitivity knock control will not change.

[Lerlo]

Thanks Hondata,

My counts are all within 2000-3500 (high load, low rpm) so I will retard the ignition and give it a try.

My tappets are a little noisy so Ill get that adjusted as well.

I read you loud and clear on the knock control parameters you have explained.

So knock count will not change, however rate of change in knock control is based on load/sensitivity settings.

Thanks!