View Single Post
Old 12-05-2008   #2
scheides
flips McGee
 
scheides's Avatar
Re: Knock tables/routines unraveled (evo)

Interesting post, just for you Kracka:

Quote:
Originally Posted by jcbanks
The adaptive bit is pretty quick, one filter will be done after 16 ignition events, then the next one after 8, so it doesn't take long to completely clear out any memory effect. I can't see any long term memory involved at all.

Like many of us have noticed, you often get knock on the first pull more than subsequent ones, I think most people put this down to carbon embers in the combustion chamber that build up during cruise and then act as knock promoters. Doesn't sound like this entirely explains how it only happens after a flash in your observations, but knock is an unpredictable phenomenon and sometimes I know I look for patterns/predictability that simply isn't there.

Quote:
Originally Posted by dan l
Thanks for posting this. I like to know the "how's and whys" before I go editing code. This will really help the people who take the time to read it.

Since you mentioned the adaptive learning of the knock system, I have been studying my knock sums after a reflash which clears the ecu on a 9. The very first pull it knocks significantly (6 counts). Every pull theirafter it becomes less till I get 1-2 counts or none at all after a couple pulls or maybe just a long period of driving. Of course the logging isn't fast enough to pick up the spikes in knock sensor noise, but I can still pattern trends in my head with the info given above. I'm really glad I'm not only learning how to deal with this system, but how to manipulate it and retain the safety that it is intended to provide.

http://forums.evolutionm.net/showpos...&postcount=122
scheides is offline   Reply With Quote