Tachometer calibration

Here's a photo of the pin connectors:

So I took a digital signal/wave generator and tested the tacho. Here's what I found for this particular tacho:
My photo pin A connected to ground
My photo pin B connected to a square-wave source
My photo pin C connected to 12v
In the car, the tacho signal is coming from the ignition. Therefore, the correct reading for the tacho should be the 30/Hz of the input signal. I used 5v amplitude, 2.5v offset, 50% pulse width, and square wave. This is something not too different from what the EZK should give, right?
Here are my empirical measurements:
Hz multiplier true RPM gauge RPM
21.2 0.5 636 750
33.3 0.5 998 1100
41.1 0.5 1234 1350
69.5 0.5 2086 2100
84.8 0.5 2544 2575
117.2 0.5 3516 3425
122.3 0.5 3670 3500
169.6 0.5 5088 4800
222.6 0.5 6677 5450
244.7 0.5 7341 6000
245.9 0.5 7378 6000
In other words, very inaccurate after true 5000 rpm. After about 7400 true rpm, the gauge tilts and starts reading about 4000 rpm. Can't get it to read to the official red line. In other words, a driver relying on this tacho would never think he's overreving the engine, no matter what the rpm.
There are two trim pots in the tacho. Neither made much difference in the calibration range.
If this is a representative tacho, couldn't you read the 951 rpm from tea leaves near the redline with an accuracy comparable to that of the factory tacho? Or did I just buy an unusually defective unit from fleabay? Or did I test it wrong?
The 928 tacho appears to be very similar, so I wouldn't be shocked if many of our tachos as off by a lot, too.
Lifetime Rennlist
Member
Also--
Does the EZK send 5V squares? Might be worth sticking a 'scope on the factory tach signal (it's easy to get to at a couple CE panel connectors for test purposes) and see what's normally delivered. Considering that it's coming across on unshielded wiring, it may be a little higher peak voltage. I'd check that before condemning the part you found.
Gotta ask-- what's the need for the 951 tach? Curious...
My test procedure may also be off, I may have simply made some sort of error either with the formula or my test instruments. In fact this is the most likely explanation, and I just posted the procedure and results here to see if someone caught an obvious error in what I did.
Your point about people logging digital data being able to check their tachos is excellent. With this tacho, the error only started showing well after 5000 rpm, and I don't know if people doing over 5000 rpm on the road in their 928s will by default be simultaneously looking at the analog gauge and the data logger display. But if one just wants to do a quick check, it'll be easy to do if one has any digital rpm display driven off from say the ignition. All dynos have the display, too, so the dyno operator could easily check this.
I want to do what PorKen did, put a boost gauge in the 928 instrument cluster! Imitation is the sincerest form of flattery.
I also was planning to play with some of the adjustments in the tacho to see if one could get it to "go to 11" just by home-grown recalibration and printed face sticker.
Trending Topics
The Best Porsche Posts for Porsche Enthusiasts
Here's a scope picture of the tach signal and one of the ignition-module drives from the EZK in our S4.
Chan-B (the blue trace) is the tach signal, 0-12 volts (5V/div). The rising edge is TDC, and the signal is a square wave with two cycles per engine revolution. This was captured at idle, around 650 RPM (22 hz).
Chan-A (red trace) is the drive signal (0-5v) to the left-side ignition module, the spark fires on the negative-going edge.
Our tach's both read accurately according to the ST2 so yours is a personal problem

Try it with a 12v square-wave.
Cheers, Jim
Idle timing.PNG
Chan-B (the blue trace) is the tach signal, 0-12 volts (5V/div). The rising edge is TDC, and the signal is a square wave with two cycles per engine revolution. This was captured at idle, around 650 RPM (22 hz).
Our tach's both read accurately according to the ST2 so yours is a personal problem

Try it with a 12v square-wave.
* The good news is that is seemed to have hte math figured out with 30 rpm / Hz.
* The tacho that I tested yesterday was about ok all the way until 5,000 rpm, but fell on it's face after that. I'll have to test it again with 12v amplitude to see if there's some weird interaction with required amplitude and rpm.
* "a personal problem." Buying a gauge from Ebay and finding out that it's not correctly calibrated is as surprising and disappointing as receiving a mail order bride just to find out that she's not a virgin...
The tacho is still off significantly, but it doesn't tilt. Work continues...
- Make sure that you feed exactly the correct amplitude and offset square wave as signal. It's not like a modern digital computer, those parms actually impact the reading.
- If you have a function generator / oscilloscope with capture and replay functions, you may want to capture some actual signal from the car, compute the true rpm, and use that in claibration. I didn't do that.
- The top trim pot controls some weird mixture of gain and offset. The second trim pot seems to not control anything in the tacho, possibly it's for the boost gauge. Because of one degree of freedom, arbitrary calibration is not possible even if the instrument is linear. I take that back -- you can do an arbitrary calibration to a linear instrument if you're willing to take adjust the needle by taking it off and setting it to a little bit different position.
- It seems that the working tacho goes about accurately to about 7700 rpm. If you're interested in printing a face plate sticker, you can probably paint it from zero to 8000 rpm and make it still look the period. This would require no component changes. Mockup attached.
951Tach928Pod6.JPG



