Campaign icon

Knock sensor table discovery Fund

Earnings

Total
$1,560.00

Goals

  1. Campaign goal
    $1,560.00 of $2,000.00

Overview Donations Comments

Table discovery can be something that helps every member of the community so we've decided to take Jake Yamona up on his offer to muck through the work required to define the tables related to knock detection.

I'd be happy to work through the remaining knock tables (frequency, amplitude, windows, etc), logging params, and document how it all works. End result would be standalone levels of configuration of the knock detection system. However, as it is a very small end user market, it is not something MHD would likely fund. However, if enough built motor guys wanted to all pitch in, let me know.
Put a funding goal and we can start a board sanctioned fund. Always down to progress this kind of stuff.
For those who need a bit of background on why this is useful:

jyamona said:
A knock sensor is just a microphone. It listens and then sends what is picks up as a voltage. The DME has a very advanced DSP processor in it, specifically for processing knock signal. The voltage is converted into a sound wave and then it is analyzed...there are a ton of tables that play into this. The sound wave has a frequency (Hz) and amplitude. For a given listening window (crank begin and end angles), the sound wave is compared against the tables for what has been configured to be detected as knock vs. just engine noise. When you change any engine internal (or even as engines age), the pre calibrated frequencies, amplitudes, noise levels, etc per cyl are thrown off which causes the DME to think it is seeing knock when really it is just noise.
Click the "Donate" button at the top of the page!

Earnings

Total
$1,560.00

Goals

  1. Campaign goal
    $1,560.00 of $2,000.00
Top