the distributer in a stock ls is set to 16 degrees advance.
now the map says at this point -6 degrees this will me retarded.

so is the real ingnition setting , set at 20 - 6 = 14 degrees total advance for the ignition block?

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by non-vtecAl &raquo;</TD></TR><TR><TD CLASS="quote">the distributer in a stock ls is set to 16 degrees advance.
now the map says at this point -6 degrees this will me retarded.

so is the real ingnition setting , set at 20 - 6 = 14 degrees total advance for the ignition block?

</TD></TR></TABLE>

no. your ignition will fire at 6 degrees after top dead center. thats what -6 means.

at idle your map should read around 16 degrees which is what the distributor should also be set to.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by falconGSR &raquo;</TD></TR><TR><TD CLASS="quote">

umm..hmm.. well.. on page 2 of that story they talk about listening to the knock sensor directly to hear knock - i am about to go try this! i have an audio preamp circuit and a fm modulator so i shouuld be able to pipe me knock sensor over my stereo :-p

i just need to know which wire the knock sensor signal is on in an obd1 P72 GSR plug. i'll have to crossreference it from my obd2 helms. hmm...excited i am..
</TD></TR></TABLE>

well i just installed an audio amp in my car and hooked it up to what i *think* was the knock sensor wire, which was red with a blue stripe.

no idea if that was the right one. i do hear lots of stuff most of it sounds RPM dependant and the engine gets noticably louder in VTEC....my map is conservative so i dont think i even heard detonation. i should go tap on the block somehow and listen in the headphones to make sure the thing is working and i hooked it up right...

 

Pin D3, red with either green or blue stripe.

That's a pretty interesting concept... to properly utilize KS input in electronics, you require a certain amount of signal processing to identify the frequencies you want to monitor. I never thought to see if the KS output was something that could be analyzed by the human ear.

Not bad, stunna.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by J. Davis &raquo;</TD></TR><TR><TD CLASS="quote">Pin D3, red with either green or blue stripe.

</TD></TR></TABLE>

yeah but i have obd2.5 or whatever. so the connector isnt in the helms...

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote &raquo;</TD></TR><TR><TD CLASS="quote">

That's a pretty interesting concept... to properly utilize KS input in electronics, you require a certain amount of signal processing to identify the frequencies you want to monitor. I never thought to see if the KS output was something that could be analyzed by the human ear.

Not bad, stunna.</TD></TR></TABLE>

yessir, the human brain is a good audio signal processor with its massively parallel but simple architecture. ****, i sound sober!

 

lol.. you are almost as crazy as j davis / me.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by falconGSR &raquo;</TD></TR><TR><TD CLASS="quote">

yeah but i have obd2.5 or whatever. so the connector isnt in the helms...
</TD></TR></TABLE>

C3 then, I lack the wiring color in my notebook for OBD2B. I guess I could look at these injector plugs here on the floor, but I am much too slack for that kind of activity. :&gt;

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by J. Davis &raquo;</TD></TR><TR><TD CLASS="quote">

C3 then, I lack the wiring color in my notebook for OBD2B. I guess I could look at these injector plugs here on the floor, but I am much too slack for that kind of activity. :&gt;</TD></TR></TABLE>

C3 sounds correct. i am confident it is. so i am hearing the knock sensor. one of the links said knock sensors are resonating around 2-12khz which just happens to be the upper range of hearing for the average person.

honestly i would prefer to monitor this on a DSO (digital oscilloscope) so i could really characterize it better. with this info, i think the most comprehensive solution would be using a TI DSP board and develop an adaptive algorithm for detonation detection. it would be a helluva project and overkill but it would be the best damn knock detector on the planet (with the right programmer).

 

you could probably use an i/o board and to input the KS signal and RPM signal into a computer- or through the joystick port. just need someone to write code to interpret it or maybe use that basic dataq software

 

THanks for all the help guys

 

Why not just dump the 66K processor on the existing Honduh KS boards and reverse engineer it?

Saves a lot of R+D time, and I'm sure there isn't very much code involved - the extra MCU was just used to keep from overburdening the central MCU.

 

maybe cause the honda knock boards suck *** for detonation detection in the first place? If reverse engineering was going to take place, I'd at least want to target a device that works better. Honda knock boards are designed for LOW END KNOCK. I.E. bad gas in a high comp motor. They do not work well for the high-RPM boost induced timing too far advanced knock that is universally hard to detect. This seems like my next project. My ex-roomie worked for TI's DSP group for his co-op and I'm sure I could get enough info out of him to get a good start...

 

I am pleased with my J&S works Great! I also use the output and datalog with my inovative WB