Um you can turn it off and still log knock. There was this post telling all about it:

https://www.evolutionm.net/forums/sh...4&postcount=27

it works great and you can still log knock

 

my point was that I'd like to disable knock control in that one RPM range and still be able to retain the ability to log knock.

 

94170015 please!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

No I understand totally, and thats what I am saying.

If you turned off the knock control via the Periphery 0x5650 for instance, you cant log anything at any RPM. By setting the knock retard to 0 counts ( or any value you want really) it cant pull any timing but you can still log it to see what its doing so in the upper RPM ranges you still have some idea.

I have turned knock control all the way off on some occasions in 1G's via Link but it was on C16 or better so no worries. Even in my own car I have done it but until this came about I had always wanted to know what the actual counts were and still not have it do anything.

If you did it via the periphery method I am sure you are aware that it kicks you into the low octane maps, this adjusting the timing pull leaves it on the high octane (not that its hard to tune one or the other).

aaron

 

I did it the old fashioned way, so there was no knock light with the tepra rom and no knock logged unfortunately which made me feel vulnerable but daily driving it I'm okay with that since I'm not into big boost anyway. Naturally when I'm racing I won't see 3500rpm (knock prone area) and I let the ECU see/log knock again.

Hopefully Tephra comes through with the ability to disable the ecu's reaction to knock in a user specified RPM range (3500rpm for me) while retaining the ability to log it.

 

Yes he has and it is currently in testing.

Knock % x RPM x Load and still have the ability to log KS and have CEL for KS #

 

I see, a knock "map" with 100% being full ecu knock control and 50% being half the timing pulled right? I have 96940011 the 05 bastard ECU with no memory so I've been waiting to see a flavor for the other model that supersedes it but If I remember correct there were other issues with the successor to my ECU something about 2-step not working and something else.

 

 

this map will only cut what the timing interpolation knocksum sees but you will log the full value. So if you log 6 counts of knock where the map says 50% it will only cut timing like 3 counts.

 

that's very cool, further blurring the lines between stock ecu and the aem ems...love it

 

Yeah but if you have a known bad area for phantom knock you can set it to "0", and it won't pull any timing. Those setting are just what Brian is testing, you can set it for whatever you need... I think.

 

Not exactly. It won't pull any timing for that piece of knock control, the 3 counts per 1* timing pull. But, it will still pull timing due to interpolation to the low octane timing map if the knocksum is 6 or more for prolonged periods and your low octane map has lowering timing values.

 

Ahhh...true, so maybe you would get old school and set the values in the high and low timing maps the same in your problem area.

 

Agreed...making my planned 2.2LR build looking a little more interesting now.

 

I personally think the octanenumber thing is bs anyways.

I have never seen it drop below 98% which means that its stil using high-octane by 98%...

anyways not so much of an issue

I will try and get a 94170015 out next week so more ppl can test