Knock sensor logging
1st Gear Member
Joined: Jul 2006
Posts: 101
From:
RE: Knock sensor logging
ORIGINAL: Justastockmustang
Anybody know if the SCT XCalibrator will log knock sensor activity?
Know of any other way to log knock activity other than smoke and flame?
Thanks!
Anybody know if the SCT XCalibrator will log knock sensor activity?
Know of any other way to log knock activity other than smoke and flame?
Thanks!
the options to choose from in this category are:
CYL_1_KNOCK_THRESHOLD
CYL_2_KNOCK_THRESHOLD
CYL_3_KNOCK_THRESHOLD
CYL_4_KNOCK_THRESHOLD
CYL_5_KNOCK_THRESHOLD
CYL_6_KNOCK_THRESHOLD
CYL_7_KNOCK_THRESHOLD
CYL_8_KNOCK_THRESHOLD
KNOCK_SENSOR_1_NOISE
KNOCK_SENSOR_2_NOISE
-howy
Thread Starter
2nd Gear Member
Joined: Feb 2006
Posts: 355
From: Maryland
RE: Knock sensor logging
Thanks!
Unfortunately that update rate would not be very useful for tracking real-time knock, my goal.
You can set knock threshhold on individual cylinders with only two knock sensors?
Unfortunately that update rate would not be very useful for tracking real-time knock, my goal.
You can set knock threshhold on individual cylinders with only two knock sensors?
ORIGINAL: howyhowy
I just fired up data logging for the first time tonight. Yes it does, but the values are only updated on a once - per second (or abouts) basis.
the options to choose from in this category are:
CYL_1_KNOCK_THRESHOLD
CYL_2_KNOCK_THRESHOLD
CYL_3_KNOCK_THRESHOLD
CYL_4_KNOCK_THRESHOLD
CYL_5_KNOCK_THRESHOLD
CYL_6_KNOCK_THRESHOLD
CYL_7_KNOCK_THRESHOLD
CYL_8_KNOCK_THRESHOLD
KNOCK_SENSOR_1_NOISE
KNOCK_SENSOR_2_NOISE
-howy
I just fired up data logging for the first time tonight. Yes it does, but the values are only updated on a once - per second (or abouts) basis.
the options to choose from in this category are:
CYL_1_KNOCK_THRESHOLD
CYL_2_KNOCK_THRESHOLD
CYL_3_KNOCK_THRESHOLD
CYL_4_KNOCK_THRESHOLD
CYL_5_KNOCK_THRESHOLD
CYL_6_KNOCK_THRESHOLD
CYL_7_KNOCK_THRESHOLD
CYL_8_KNOCK_THRESHOLD
KNOCK_SENSOR_1_NOISE
KNOCK_SENSOR_2_NOISE
-howy
3rd Gear Member
Joined: Jun 2006
Posts: 713
From:
RE: Knock sensor logging
ORIGINAL: Justastockmustang
Unfortunately that update rate would not be very useful for tracking real-time knock, my goal.
You can set knock threshhold on individual cylinders with only two knock sensors?
Unfortunately that update rate would not be very useful for tracking real-time knock, my goal.
You can set knock threshhold on individual cylinders with only two knock sensors?
So, they should know what should be firing at the moment and therefor which one must be pinging...
Can't say I have proof that this is what they did, but it seems logical enough...
If you set the threshold to "1" - do you care exactly which milli-second it occurs?
Thread Starter
2nd Gear Member
Joined: Feb 2006
Posts: 355
From: Maryland
RE: Knock sensor logging
Good point!
ORIGINAL: cekim
In theory, they have to "filter out" combustion noises to know what is a "knock" and what is not...
So, they should know what should be firing at the moment and therfore which one must be pinging...
Can't say I have proof that this is what they did, but it seems logical enough...
If you set the threshold to "1" - do you care exactly which mili-second it occurs?
ORIGINAL: Justastockmustang
Unfortunately that update rate would not be very useful for tracking real-time knock, my goal.
You can set knock threshhold on individual cylinders with only two knock sensors?
Unfortunately that update rate would not be very useful for tracking real-time knock, my goal.
You can set knock threshhold on individual cylinders with only two knock sensors?
So, they should know what should be firing at the moment and therfore which one must be pinging...
Can't say I have proof that this is what they did, but it seems logical enough...
If you set the threshold to "1" - do you care exactly which mili-second it occurs?
Thread
Thread Starter
Forum
Replies
Last Post
jwog666
Pipes, Boost & Juice
11
Dec 27, 2021 08:09 PM
nmra1965
Other Professional Racing
0
Sep 26, 2015 10:46 AM
