Page 1 of 1

Proximity sensor for tach input?

Posted: Sat Jun 08, 2013 4:50 pm
by bwgreen1
Vehicle: '76 Honda GL-1000 motorcycle (4-cylinder boxer-type engine)
Ignition is DYNO-S electronic, I believe CDI
I've built an MS-2 to use for fuel only, and was planning to use my ignition coil for the tach signal. Then I noticed the ignition coil couldn't be used for a signal source because it gets its signal from the DYNA S, which I think is a CDI system. Beside not understanding Hall effect sensors or VRs very well, they seem a bit too complicated for what I need. Please correct my misunderstanding, but I was assuming all I needed for tach signal was a pulse of some sort for every crankshaft revolution. I suspect I can get a 12V pulse per crank revolution with a two-trigger device on my right side camshaft with an inductive proximity sensor. Has this been done for Megasquirt? What kind of signal is needed when the MS-2 is set up for coil input?
Bruce G.

Re: Proximity sensor for tach input?

Posted: Sat Jun 08, 2013 5:34 pm
by DonTZ125
I can't find any info on 'Dyno-S', but if you mean a Dyna-S kit, then it is an inductive (Kettering) ignition and can be used for coil negative triggering.

Re: Proximity sensor for tach input?

Posted: Sat Jun 08, 2013 6:45 pm
by bwgreen1
Yes, it is the Dyna-S (duh, I must be getting sleepy). Well, that's good news. It will make my installation so much easier. Just take the signal from one of the Dyna-S connections to the coil. If I'd read the wiring diagram more carefully and remembered that points switch the ground line, I'd have realized it wouldn't make sense to send high voltage pulses to the negative terminals of the coils, which is where the Dyna-S is connected.
Thanks very much for the info.
Bruce

Re: Proximity sensor for tach input?

Posted: Sun Jun 23, 2013 10:29 am
by bwgreen1
I've decided to use a proximity sensor for tach input, since I can get a clean square wave input to the MS at any voltage I want. I have one question though. Can the MS take my signal off the camshaft and double it to get true RPM of the engine, or do I need to put a double trigger on the prox switch? I suppose another route to resolving this is to modify the table values to half the real RPM.