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.

 

What do the knock sensor filter maps do?

Can't you change the noise floor using those?

 

You guys hurry up and figure this out before I finish MY engine, it's nearly the same as the OP's.

^^^^ glad I made your signiture!

 

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

 

I requested this feature in Tehpra's thread, he's going to look into it today.

 

awesome

 

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

 

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.

 

well I donated to Tephra so he owes me

 

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'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.

 

^ me too

 

Yeah that would certainly be more ideal. However harder todo - unfortunately the IGNITION code that takes into account knock isn't as straightforwards as I had hoped.

Still pressing on thou

 

thanks for checking into this tephra you're going to make some people very happy and further blur the line between stock ecu/standalone

 

thats ok - just dont expect a result really soon ... some damn silly maths going on in this ECU