High knock values
High knock values
Hello Hondata,
I have a Central American SI with the next mods: Injen CAI, Toruku cams stage1, ingalls powerstick, vibrant race header and catback and NST pulleys.
Today I installed my flashpro, everything ok, but when I started the datalogs I found very high knock values.
I know I have to work with fuel values, but I am worried about knock levels.
I attach two dataloggins: stock ECU and Injen, header MAP.
Is this because some of my mods?
I have a Central American SI with the next mods: Injen CAI, Toruku cams stage1, ingalls powerstick, vibrant race header and catback and NST pulleys.
Today I installed my flashpro, everything ok, but when I started the datalogs I found very high knock values.
I know I have to work with fuel values, but I am worried about knock levels.
I attach two dataloggins: stock ECU and Injen, header MAP.
Is this because some of my mods?
- Attachments
-
- stock.fpdl
- (180.01 KiB) Downloaded 456 times
-
- CAI sin tocar.fpdl
- (111.01 KiB) Downloaded 355 times
Knock can be caused by mechanical noise (usually a header or valvetrain), but given that your car shows less knock with the stock calibration, this does not seem to be the case.
You are going to need to identify what areas and causing knock, and retard ignition in those areas. Select 'Knock Count' for the sensor overlay, and use that to show you where on the ignition tables the knock is. It should be no more then 4-5 degrees to remove all the knock.
You are going to need to identify what areas and causing knock, and retard ignition in those areas. Select 'Knock Count' for the sensor overlay, and use that to show you where on the ignition tables the knock is. It should be no more then 4-5 degrees to remove all the knock.
Last edited by Hondata on Fri Feb 19, 2010 10:03 am, edited 1 time in total.
Hondata
Hello Hondata,
today I take dataloggins with the normal ignition timming, -10 degreess in all tables, -5 degrees and +5 degrees.
I dont see any change in knock values and knock retard.
Please help.
today I take dataloggins with the normal ignition timming, -10 degreess in all tables, -5 degrees and +5 degrees.
I dont see any change in knock values and knock retard.
Please help.
- Attachments
-
- normal.fpdl
- (13.57 KiB) Downloaded 254 times
-
- +5 degrees.fpdl
- (19.17 KiB) Downloaded 268 times
-
- -10% degrees.fpdl
- (31.53 KiB) Downloaded 242 times
-
- -5% degrees.fpdl
- (40.82 KiB) Downloaded 249 times
Knock retard is not related to the amount of noise the knock sensor gets - see the help file.
Your knock retard is fairly high, so I suspect that knock tables have been increased over stock.
Go back to the 'Civic-Si-RRB-1' Stock eqivilent and see what your knock values are. If they are normal, it is the calibration. If they are not, then it is engine modifications.
Your knock retard is fairly high, so I suspect that knock tables have been increased over stock.
Go back to the 'Civic-Si-RRB-1' Stock eqivilent and see what your knock values are. If they are normal, it is the calibration. If they are not, then it is engine modifications.
Hondata
I am having a similar issue on the same cams. I am starting to believe they are just noisy.
I want to clarify that the knock tables do NOT affect knock account. There is no knock retard in the datalogs (anymore) but 300-500 knock counts (still) over 40 minutes. The tune is basically completed but the counts are still on my mind.
Reducing the knock sensitivity appears to have no affect as these just affect the retard sensitivity. The knock counts appears false as AFR's and Ignition values are ideal when they occur.
Is there or will there be a way in the future to calibrate what counts as a knock count? I realize that the "knock count" may be a pre-defined noise limit or rather "rate of change in noise" in the Flash Pro Manager software but once the knock has been determined to be invalid/false/mechanical noise it would be nice to adjust the FPM count method, particular to that tune.
As in to make the .fpcal have a value in it that relates to FPM "count" sensitivity.
I did something similar for users that only have access to .csv files, by allowing them to change what determines a knock count from 3 variables. See attached.
Steve
I want to clarify that the knock tables do NOT affect knock account. There is no knock retard in the datalogs (anymore) but 300-500 knock counts (still) over 40 minutes. The tune is basically completed but the counts are still on my mind.
Reducing the knock sensitivity appears to have no affect as these just affect the retard sensitivity. The knock counts appears false as AFR's and Ignition values are ideal when they occur.
Is there or will there be a way in the future to calibrate what counts as a knock count? I realize that the "knock count" may be a pre-defined noise limit or rather "rate of change in noise" in the Flash Pro Manager software but once the knock has been determined to be invalid/false/mechanical noise it would be nice to adjust the FPM count method, particular to that tune.
As in to make the .fpcal have a value in it that relates to FPM "count" sensitivity.
I did something similar for users that only have access to .csv files, by allowing them to change what determines a knock count from 3 variables. See attached.
Steve
- Attachments
-
- Knock on stock engine
- stockknock.PNG (94.27 KiB) Viewed 9675 times