Hondata

Just curious if anyone has noticed this before. I have dealt with a couple of cammed k20a3 motors in ep3 chassis recently that had an inactive K. Thres. That is to say, it was always zero on the graph display. K. Level was live. A lot of these cammed k20a3s have ridiculous knock counts and it's tough to determine whether the knock is real or phantom without a live K. Thres.

I have noticed that with k20a2 maps on EP3 ecus, the K. Thres is active. I have attached a calibration and datalog. Any input/comments?

Thanks.

No input? I've seen this happen on multiple a3 engines that i've tuned Using the latest version of kmanager, 1.2.3.3. I'm pretty sure this should be reapatable.

This is a known issue, it just has to do with datalogging.

Spunkster wrote:This is a known issue, it just has to do with datalogging.

I figured it was just with the logging. Everything else seems to work fine. Hopefully it will get fixed soon. Cammed k20a3s are becoming quite common now.