fed up with knock control
Oct 16, 2008, 11:35 AM
#16
Account Disabled
iTrader: (38)
Join Date: Aug 2005
Location: Virginia Beach, Virginia
Posts: 9,319
Likes: 0
Received 1 Like
on
1 Post
I get some phantom knock at 3500 too...been that way for a very long time. It can be annoying as hell at times.
If knock could be ignored in an rpm range that would be fantastic. I would set it up to ignore knock from 0-4000, my turbo doesn't do much until 4500 on anyway.
If knock could be ignored in an rpm range that would be fantastic. I would set it up to ignore knock from 0-4000, my turbo doesn't do much until 4500 on anyway.
Oct 16, 2008, 03:36 PM
#19
A patch can definitely be made to do this. DSMLink did this for the DSM ECU.
Just nudge the patchers a little and give them a donation (mfred, tephra, jcsbanks, et al). I'm sure most of them are busy with other projects, but I know it can be done.
Eric
Just nudge the patchers a little and give them a donation (mfred, tephra, jcsbanks, et al). I'm sure most of them are busy with other projects, but I know it can be done.
Eric
Oct 16, 2008, 05:22 PM
#22
EFIxMR posted the xml to alter the knock count level that taps out timing pull. It can be set to 0 and then monitored or set to 10 counts is max pull and then monitor the rest of it from there.
Like Eric said though, making sure those with the skills and the time for the projects meet with a little compensation I assume would go a long way. I have been asking Tephra for this for a long time as well.
hopefully soon
Like Eric said though, making sure those with the skills and the time for the projects meet with a little compensation I assume would go a long way. I have been asking Tephra for this for a long time as well.
hopefully soon
Oct 16, 2008, 06:21 PM
#23
Hey guys I am looking at this today.
I have found (on 88580014) that locations 0x1384 and 0x1386 (default values are 0xA0 and 0x23) seem to control the time it takes for the KNOCK_SUM to be decremented.
Thus reducing these variables (probably in the same proportions) will speed up the KNOCK_SUM countdown.
I have found (on 88580014) that locations 0x1384 and 0x1386 (default values are 0xA0 and 0x23) seem to control the time it takes for the KNOCK_SUM to be decremented.
Thus reducing these variables (probably in the same proportions) will speed up the KNOCK_SUM countdown.
Oct 16, 2008, 06:25 PM
#25
Further to this - I have found (well it was fairly easy todo so with the disasm I have) the place where the knock sensor is read.
I am wondering if a simple patch that replaces this ADC_Read code with something like:
if (load > min_load_for_knock) {
ADC_Read
}
Would work..
OR would people prefer knock_sum to still be calculated, but not taken into account for timing reduction?
I am wondering if a simple patch that replaces this ADC_Read code with something like:
if (load > min_load_for_knock) {
ADC_Read
}
Would work..
OR would people prefer knock_sum to still be calculated, but not taken into account for timing reduction?
Oct 16, 2008, 06:34 PM
#26
Account Disabled
iTrader: (38)
Join Date: Aug 2005
Location: Virginia Beach, Virginia
Posts: 9,319
Likes: 0
Received 1 Like
on
1 Post
I'd like to continue to be able to log knock sum but have an option to ignore it at certain RPM ranges which could be user configurable or the ability to lessen the sensitivity at a certain RPM range.
