Knock module for MS3

[piledriver]

Played with my existing setup more, by ignoring the "logical" sensor<>cylider pairing and letting the system "decide" by using the "works best sensor" (highest gain and widest knock window) I'm getting good results, or at least no false positives.

(The issue was when I switched sensors in software, the noise issue moved from (only)#1 to #3 and to a lesser extent #4

I'm slowly trying to work the window as wide/flat as possible and gain as high as possiblle (allowing for cyllinder balance)

Correct? Beats the hell out of me, but looks reasonable.

Next: decent shielded mic cables, run separate from main ECU harness, ~direct to knock module.(probably with XLR connectors near the ECU)

[phongshader]

Hi,
I've just installed this knock module on a v3.57 board per the instructions here http://www.msextra.com/doc/ms3/knock_module.html. After I finished installing the module with the input coming in through pin 11 on the DB15 I decided that the installation would be much cleaner if I ran the knock input through the main cable/DB37. I rewired the knock input to pin 31 on the main DB37 and ran a wire from the IAC2B pad on the v3.57 board to the K1 pad on the knock module. In both cases I got no response from the module with the engine running. The knock sensor is the stock 2 wire sensor that came with the engine in the stock position, I'm guessing it is a resonant sensor. The sensor is wired + to pin 31, - to pin 19 on the main DB37. I tested the knock sensor with a multi meter and it did respond to tapping it with a wrench, so hopefully that means its a functioning unit. So with all that said there is no kind of response from the module with the engine running or not, how would I go about trouble shooting it? This is all happening on a Ford 2.3 duratec, MS3/3X/V3.57, 1.3.0 firmware, TS v2.5.05

[nismoautoxr]

looking at your MSQ I see nothing there that should cause an inoperative condition as long as youa re testing inside the parameters that the knock module is active which is from 700 to 3500 RPM and below 70% map. I use the same knock module and the same sensors that you are using (stock ford) and they do work.
If you need a place to start testing then I guess Id start by checking for continuity between pad K1 and your knock sensor connector as well as from your knock sensor ground to the sensor ground pin .

[phongshader]

I've gone through all the connections and they're all good. I've gone from one extreme to the other, initially there was no response from the module now it's pegged at 102.3% knock input. I tried turning the gain down to the minimum but it had no affect, tried the 2nd and 3rd harmonic that had no affect on the knock input. I've seen some other posts where a resistor was put on the knock input to reduce the signal, could this be a possible fix, or does the problem lay somewhere else?

[nismoautoxr]

how bout your frequency setting? How did you calculate that ? You have to calculate that based on bore size . Did you do that ?

[phongshader]

how bout your frequency setting? How did you calculate that ? You have to calculate that based on bore size . Did you do that ?

the frequency was calculated from a bore diameter of 87.5mm, which is 6.6khz and the bandpass frequencies I used were 6.64 (1st harmonic), 13.14 (2nd harmonic), 19.98 (3rd harmonic). I think this correct.

[nismoautoxr]

good . I didnt actually know what numbers to plug in for the calculation so that is why i asked . i had issues early on with my stock GM resonant sensors in which they would indicate knock pretty much all the time due to my valvetrain being noisy. I switched to the ford sensors and they worked much better . That and the GM sensors mounted up high under the intake. The ford sensors I am using are mounted to the side of the engine block below the heads .

[jsmcortina]

I split off most of the PPP discussion into this topic: http://www.msextra.com/forums/viewtopic ... 31&t=55863

James