Just digging through my last datalog and I ran across this



Ideas?

 

that's odd. hondata actually removed the knock retard on the k-pro. in a way it's good and bad.

if this were with flashpro, i would say it's pulling timing because it's detecting knock. hondata left the knock control tables present on the flashpro and one could modify those tables to their liking.

the thing is that the knock sensor can pick up noise from other things in the engine bay. turbo's, supercharger, aftermarket valvetrain etc. and in this case the knock retard can get in the way.

in your case you can tell it's false knock that's being recorded just by looking at the knock level and the knock threshold.

 

I realize you have a K-Pro, so this may be totally irrelivant, but I found that all of the FlashPro's canned calibrations had a spike in knock sensitivity between 2K and 3K RPMs, which caused a lot of ignition retard between 2K and 3K. What was strange was that it did NOT get reported as knock retard. It just showed up as a dip in timing. Below is a before / after datalog of ignition timing and knock retard after adjusting the knock sensitivity.

Does K-Pro not have ANY sort of knock control?

 

thats one reason hondata is retarded....

all k-pro's i have tuned seem to do what they want with timing, especially at part throttle and idle.

 

nope

 

No.

 

Only thing I can think of is if whoever tuned it for whatever reason instead of reducing the ignition timing on the map just put massive retards on the induvidual cylinder ingition trims. Worth checking them I guess.

 

Nope those are blank

 

Why do you think the K Level and K Threshold also dropped at the same time as the dip in ignition timing? Even when ignition timing went back up, the K Level and K Threshold stayed low.

 

there is no individual cylinder trim for ignition timing on the k-manager software. it is available on the flashpro manager software though.