MS3x Knock Module Settings Thread
#1
Thread Starter
DEI liberal femininity
iTrader: (8)
Joined: Jun 2005
Posts: 19,338
Total Cats: 574
From: Fake Virginia
MS3x Knock Module Settings Thread
Since my settings were requested by a couple people, I thought I'd start this.
I pulled some of the settings from msextra. I derived my own value for bandpass frequency based on something. I think it was either a formula Jason C posted or somewhere found on the internet.
Integrator time constant is the default I think.
Scaling is simply based on what range I thought "noise" looked appropriate. What I interpret as "obvious knock" are spikes at least 2-3x times taller than the "noise" in the chart at the end.
** PLEASE INCLUDE CAR, SENSOR, AND ENGINE MOD DATA WHEN YOU POST YOUR SETTINGS **
Car: 2001 Miata NB
Sensor: Stock 2001 miata NB sensor
Setup: big turbo, motor internals and head are stock .
I have not really touched the following values:
And those settings result in this:
I pulled some of the settings from msextra. I derived my own value for bandpass frequency based on something. I think it was either a formula Jason C posted or somewhere found on the internet.
Integrator time constant is the default I think.
Scaling is simply based on what range I thought "noise" looked appropriate. What I interpret as "obvious knock" are spikes at least 2-3x times taller than the "noise" in the chart at the end.
** PLEASE INCLUDE CAR, SENSOR, AND ENGINE MOD DATA WHEN YOU POST YOUR SETTINGS **
Car: 2001 Miata NB
Sensor: Stock 2001 miata NB sensor
Setup: big turbo, motor internals and head are stock .
I have not really touched the following values:
And those settings result in this:
#6
Thread Starter
DEI liberal femininity
iTrader: (8)
Joined: Jun 2005
Posts: 19,338
Total Cats: 574
From: Fake Virginia
Oh that. I set the maximums to round numbers or numbers that make the 50% line meaningful (for AFR the dotted line is 14.7). Note also my TPS goes to 101. And volume to 11.
I find that having the graph trace sit right up against the edge of the graph limits makes it hard to read.
I find that having the graph trace sit right up against the edge of the graph limits makes it hard to read.
#8
Thread Starter
DEI liberal femininity
iTrader: (8)
Joined: Jun 2005
Posts: 19,338
Total Cats: 574
From: Fake Virginia
a lot.
I haven't really spent much time tweaking on this thing. I suspect some improvement could be had by actually doing something with the windowing but... I haven't driven my car more than about 50 miles in the last month or two.
Here's a random example. I haven't decided if I should call these moderate spikes "noise" or "knock" or neither. I think the way to go would be to get a passenger with det cans and a computer to mark the logs as soon as he heard something and then match up the spike levels with the marks and adjust based on that.
Similarly, spending 5 minutes to look at the window settings and make some educated guesses where knock occurs in our motors would be good.
I haven't really spent much time tweaking on this thing. I suspect some improvement could be had by actually doing something with the windowing but... I haven't driven my car more than about 50 miles in the last month or two.
Here's a random example. I haven't decided if I should call these moderate spikes "noise" or "knock" or neither. I think the way to go would be to get a passenger with det cans and a computer to mark the logs as soon as he heard something and then match up the spike levels with the marks and adjust based on that.
Similarly, spending 5 minutes to look at the window settings and make some educated guesses where knock occurs in our motors would be good.
#9
How are you detecting individual cylinder knock? Is this just a setting that is listening for different frequencies that is cylinder dependent? I see the per cylinder settings, but what is the gain, and why are they all the same?
EDIT:
I'm an idiot, it would just be based on rpm and the time window in which the vibration is detected.
Is the gain supposed to be a factor that takes into account the latency of sound traveling through the block for the different cylinder distances? i.e. the furthest cylinder would need a higher gain so that the amplitude of the peak is the same as the amplitude of a peak in the closest cylinder for a knock event of the same magnitude???
EDIT:
I'm an idiot, it would just be based on rpm and the time window in which the vibration is detected.
Is the gain supposed to be a factor that takes into account the latency of sound traveling through the block for the different cylinder distances? i.e. the furthest cylinder would need a higher gain so that the amplitude of the peak is the same as the amplitude of a peak in the closest cylinder for a knock event of the same magnitude???
Last edited by miatauser884; 08-21-2012 at 07:08 PM.