X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Fri, 19 May 2006 07:47:20 -0400 Message-ID: X-Original-Return-Path: Received: from smtp108.sbc.mail.mud.yahoo.com ([68.142.198.207] verified) by logan.com (CommuniGate Pro SMTP 5.0.9) with SMTP id 1119417 for lml@lancaironline.net; Thu, 18 May 2006 22:05:21 -0400 Received-SPF: none receiver=logan.com; client-ip=68.142.198.207; envelope-from=elippse@sbcglobal.net Received: (qmail 21285 invoked from network); 19 May 2006 02:04:38 -0000 Received: from unknown (HELO Computerroom) (elippse@sbcglobal.net@75.15.119.78 with login) by smtp108.sbc.mail.mud.yahoo.com with SMTP; 19 May 2006 02:04:37 -0000 X-Original-Message-ID: <000501c67ae8$999a85c0$4e770f4b@Computerroom> From: "Paul Lipps" X-Original-To: "Marv Kaye" Subject: LSE rpm X-Original-Date: Thu, 18 May 2006 19:04:42 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0002_01C67AAD.EB4BC4A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 This is a multi-part message in MIME format. ------=_NextPart_000_0002_01C67AAD.EB4BC4A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Actually, LSE's rpm data is analog from the get-go. One way to turn = one-three pulses per rev to an rpm output is to have a multiplier and = counter. This can be done with a phase-lock-loop multiplier set to the = proper division rate, i.e. if you want a readout every second, a = one-pulse-per rev would have to be multiplied by 60 before being input = to a counter. Then you are faced with the choice of closed-loop = bandwidth that will have a fast enough response time to keep up with = motor acceleration, but slow enough to filter the crankshaft = angular-rate variations. You'd be amazed at how much the crank = accelerates and decelerates during one revolution! I know; I've built = several. I guess you might call that a digital approach. I flew with a = fellow that was trying a PLL tach I made on his 140, that had a one = second readout rate. At first he thought there was a problem with it as = it sometimes jumped aroud tens of rpm, until I pointed out it was smooth = until we had some turbulence. If you see stable rpm readout in your = digital display in turbulence, your tach's smoothing constant or = time-base rate is quite large. A u-processor-based system will count = time between pulses or the number of pulses in a fixed-length gate, then = calculate the rpm. That's still a multiplier. Any time you have a = harmonic relation between the pulse rate into a counter and the gate = rate, you can have gate opening and closing errors where pulses are = picked up or dropped. A lot of tachs start with a triggered pulse, at crank rate, to give = a fixed width and amplitude pulse, then filter that through a simple R-C = smoothing net for display on an analog meter of some sort, either DVM or = D'Arsonval movement. LSE's rpm is 100 uV / rev / min, so if you do not = have a good closed signal system from the LSE to the meter, common mode = noise injected into the wiring can cause errors. The 40-70 rpm error you = mention can be from 4mV to 7mV common mode error in the ground return; = that's 0.004V to 0.007V. LSE's MAP is 10mV / inchHg. Again, 6mV, 0.006V, = on the ground can give 0.6" MAP error + or -! Proper wiring and = grounding practices, as was much discussed on LML several weeks ago, is = critical with low-level signals of any kind. Whether digital or analog, = each approach has its own type of errors. ------=_NextPart_000_0002_01C67AAD.EB4BC4A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Actually, LSE's rpm data is = analog from=20 the get-go. One way to turn one-three pulses per rev to an rpm = output is to=20 have a multiplier and counter. This can be done with a phase-lock-loop=20 multiplier set to the proper division rate, i.e. if you want a readout = every=20 second, a one-pulse-per rev would have to be multiplied by 60 before = being input=20 to a counter. Then you are faced with the choice of closed-loop = bandwidth=20 that will have a fast enough response time to keep up with motor = acceleration,=20 but slow enough to filter the crankshaft angular-rate variations. You'd = be=20 amazed at how much the crank accelerates and decelerates during one = revolution!=20 I know; I've built several. I guess you might call that a digital = approach.=20 I flew with a fellow that was trying a PLL tach I made on his = 140,=20 that had a one second readout rate. At first he thought there was a = problem with=20 it as it sometimes jumped aroud tens of rpm, until I pointed out it was = smooth=20 until we had some turbulence. If you see stable rpm readout in=20 your digital display in turbulence, your tach's smoothing constant = or=20 time-base rate is quite large. A u-processor-based system will = count=20 time between pulses or the number of pulses in a fixed-length gate, then = calculate the rpm. That's still a multiplier. Any time you have a = harmonic=20 relation between the pulse rate into a counter and the gate rate, you = can have=20 gate opening and closing errors where pulses are picked up or=20 dropped.
    A lot of tachs start with a = triggered=20 pulse, at crank rate, to give a fixed width and amplitude pulse, then = filter=20 that through a simple R-C smoothing net for display on an analog meter = of some=20 sort, either DVM or D'Arsonval movement. LSE's rpm is 100 uV / rev / = min, so if=20 you do not have a good closed signal system from the LSE to the meter, = common=20 mode noise injected into the wiring can cause errors. The 40-70 rpm = error you=20 mention can be from 4mV to 7mV common mode error in the ground return; = that's=20 0.004V to 0.007V. LSE's MAP is 10mV / inchHg. Again, 6mV, 0.006V, on the = ground=20 can give 0.6" MAP error + or -! Proper wiring and grounding practices, = as was=20 much discussed on LML several weeks ago, is critical with low-level = signals=20 of any kind. Whether digital or analog, each approach has its own = type of=20 errors.
------=_NextPart_000_0002_01C67AAD.EB4BC4A0--