Knock Sum discussion
#1
Evolved Member
Thread Starter
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
Knock Sum discussion
Correct me if I am wrong but it seems to me Knock sum is actually ignition retard amount I will try to get it in correct scaling later.
It should be possible to log Knock Sensor Voltage. Once it is sampled at high rate and coverted to wave we should be able to hear the mike.
Has anyone tried to verify it is actually Knock sensor voltage?
Has anyone experienced Knock Sum higher than 36?
Is there any DSP chip within the ECU that processes the RAW Knock sensor input and what we have as Knock sensor ADC value is preprocessed FFT?
It should be possible to log Knock Sensor Voltage. Once it is sampled at high rate and coverted to wave we should be able to hear the mike.
Has anyone tried to verify it is actually Knock sensor voltage?
Has anyone experienced Knock Sum higher than 36?
Is there any DSP chip within the ECU that processes the RAW Knock sensor input and what we have as Knock sensor ADC value is preprocessed FFT?
#2
EvoM Guru
iTrader: (8)
36 is a actual cap in the ECU. You can change this number to whatever you want with:
05-06 - Address: 1782 , 1D, scaling = uint16
03-04 - Address: 1382, 1D, scaling = uint16
You can log raw voltage in the newer Evoscans.
As far as ignition retard amount. General rule of thumb is every 3 knock sum is -1* retard
05-06 - Address: 1782 , 1D, scaling = uint16
03-04 - Address: 1382, 1D, scaling = uint16
You can log raw voltage in the newer Evoscans.
As far as ignition retard amount. General rule of thumb is every 3 knock sum is -1* retard
#3
Evolved Member
iTrader: (30)
The knock voltage logging is just the 0-5v value and doesnt really show any rhyme nor reason since its noise not necessarily knock. If you are good with this form of logging (its the same as the AEM) you can interpret it for what would be real knock and what would be phantom, but I have seen 3.9v and no knock, and seen 10 counts and .9v.
#4
Evolved Member
Thread Starter
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
The knock voltage logging is just the 0-5v value and doesnt really show any rhyme nor reason since its noise not necessarily knock. If you are good with this form of logging (its the same as the AEM) you can interpret it for what would be real knock and what would be phantom, but I have seen 3.9v and no knock, and seen 10 counts and .9v.
#5
Evolved Member
Join Date: Apr 2008
Location: Sydney, Australia
Posts: 604
Likes: 0
Received 0 Likes
on
0 Posts
Maybe you should also be considering that maybe the knock voltage is not logged fast enough. We are not using a scope here, rather what the ECU is letting you see through its logging output.
Such as, you might get a 4V spike and a true knock, but in the logs only see a value around 1V. The ECU will detect it, but just not report the high voltage to you. What I have tended to notice is that sustained high amplitude knock voltage gets reported as knock sum. But as I was saying, it may be only showing this because it is not fast enough to show the spike inbetween.
Such as, you might get a 4V spike and a true knock, but in the logs only see a value around 1V. The ECU will detect it, but just not report the high voltage to you. What I have tended to notice is that sustained high amplitude knock voltage gets reported as knock sum. But as I was saying, it may be only showing this because it is not fast enough to show the spike inbetween.
#7
Evolved Member
iTrader: (23)
I've been logging raw knock voltage forever w/ my ECU+ and it is logging right off the sensor's output w/o going through the ECU and I can attest to the fact that magnitude of voltage by itself has very little to do with what the ECU determines is knock. Sometimes it is downright baffling.
Heck, I thought I'd just pull open a random log real quick.
You'll see below that 2.7V is not knock, yet a few seconds later 1V is 6 counts.
![](https://www.evolutionm.net/forums/attachments/ecu-flash/125472d1225732946-knock-sum-discussion-knock.png)
(sorry for the enormity... Shrinking the PNG actually increases the filesize over the limit)
Heck, I thought I'd just pull open a random log real quick.
You'll see below that 2.7V is not knock, yet a few seconds later 1V is 6 counts.
![](https://www.evolutionm.net/forums/attachments/ecu-flash/125472d1225732946-knock-sum-discussion-knock.png)
(sorry for the enormity... Shrinking the PNG actually increases the filesize over the limit)
Last edited by honki24; Nov 3, 2008 at 09:26 AM.
Trending Topics
#9
Account Disabled
remember in engineering that you can determing an unknown signal by doing a convolution integral. I have a feeling the analog knock sensor voltage probably gets put into a convolution integral with a Known mitsubishi signal. And this is were the magic determines real knock from false knock.
#13
Account Disabled
well the magic lies in the FFT of the convolution integral. Taking the %power of the FFT and if it get higher than that setpoint it is real knock. This is my guess on how to do it. its up to the Dis-assembly gurus to figure out the algorithm of this convolution integral.
im telling you this for sure, just looking at the waveform of the knock voltage will do you NOTHING.
im telling you this for sure, just looking at the waveform of the knock voltage will do you NOTHING.