Ran a datalog on my 2011 STi Sedan. Reviewed the data and at one part I had a Feedback Knock of -1.4 and Fine Knock of -0.35. Then droped to -1.05 Feedback Knock and -0.35 Fine Knock. This only showed for 1.5 seconds. The rest of the data log showed 0's in these boxes. Although there were about 2 other 1 second blips showing -0.35 Fine Knock and 0 feedback knock. Is this bad? What should I do about it? Thanks.
Robm129
Re: Help!! IS this Bade - Data Log showed -1.4 on Feedback Knock
In most cases a Knock value of 1.4 Degrees that only shows for a brief moment is phantom knock. I.E. sounds your engine sees as knock. The knock sensor is in the back side of the engine so hard shifts and other such noises can causes instances of false knock. When and what were you doing when you saw this instance of knock? Also Are you using a Cobb AP or Open source? You might also want to check and see if you have any saved values in the FLKC.
Re: Help!! IS this Bade - Data Log showed -1.4 on Feedback Knock
That noise is nothing more than vibrations in the air. So yes in essence it will detect "noise" say you drop a bolt while working on the car and it falls behind the engine and underneath the top mount. You say "what the heck it will be fine it will work its way out". More than a few people here on the board have done the same thing and then the car pulls massive amounts of timing since it keeps sensing false knock as the bolt bounces around.
Also FLKC stands for Fine Learning Knock Correction. Might be named something else in the AP. Feed Back Knock Correction (FBKC) detects knock under open loop fueling conditions (WOT and most cases of boost). If it keeps detecting knock in the same RPM range and load range that the FBKC table is unable to correct with small temporary reductions in timing, then it will jump to the FLKC table and decrees timing permanently in that RPM and load range (at least until you reset the ecu).
So if you have any negative values in the FLKC table saved you might have problems...... This is where it goes open to discussion. How much is too much reduction on the FLKC table that is unhealthy? At what point should you be worried? Personally I do my own tuning and I say any value what so ever is bad. I log at least once a month usually more than that.
WARNING: I am groslly understating and simplifing alot of this. If you want too learn more about tunning then I would sudgest going to both off these two forums:
Rom Raider
********.com
How A knock sensor works
That noise is nothing more than vibrations in the air. So yes in essence it will detect "noise" say you drop a bolt while working on the car and it falls behind the engine and underneath the top mount. You say "what the heck it will be fine it will work its way out". More than a few people here on the board have done the same thing and then the car pulls massive amounts of timing since it keeps sensing false knock as the bolt bounces around.
Also FLKC stands for Fine Learning Knock Correction. Might be named something else in the AP. Feed Back Knock Correction (FBKC) detects knock under open loop fueling conditions (WOT and most cases of boost). If it keeps detecting knock in the same RPM range and load range that the FBKC table is unable to correct with small temporary reductions in timing, then it will jump to the FLKC table and decrees timing permanently in that RPM and load range (at least until you reset the ecu).
So if you have any negative values in the FLKC table saved you might have problems...... This is where it goes open to discussion. How much is too much reduction on the FLKC table that is unhealthy? At what point should you be worried? Personally I do my own tuning and I say any value what so ever is bad. I log at least once a month usually more than that.
WARNING: I am groslly understating and simplifing alot of this. If you want too learn more about tunning then I would sudgest going to both off these two forums:
Rom Raider
********.com
¿por qué.......ninjaboy76 said:
Ahhh my bad you are right...... :bow:
I meant top back of motor......
Little tid bit of info: On the GR STI's there is a section of tables for separate cylinder timing advancement on top of base timing. Cylinders 2 and 4 (the back two cylinders) have increesed timing on stock and most stage 2 tunes. Reason for this is so the knock sensor which is located right by them can pick up knock faster and pull timing over all on the engine in an effort to save it....
Please feel free to ask any questions you have man. I check the forum here often so I will respond back as fast as I can. If I don't know the answer I can usually direct to the place where it resides.Robm129 said:
No way to see if you are having knock events more per cylinder unless you had a J&S Vampire knock control system or something of its ilk. As for how much knock will cause damage..... :notsure: . That depends on the severity of the knock along with a slew of other things. Needless to say it is advisable to have as few instances of knock possible."Little tid bit of info: On the GR STI's there is a section of tables for separate cylinder timing advancement on top of base timing. Cylinders 2 and 4 (the back two cylinders) have increesed timing on stock and most stage 2 tunes. Reason for this is so the knock sensor which is located right by them can pick up knock faster and pull timing over all on the engine in an effort to save it...."![Image]()
Is this the reason you will see more knock events in these cylinders when you are logging?
Also at what point do you have enough knock that you are sure there will be or is any internal damage?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
