Return-Path: <13brv3@bellsouth.net> Received: from imf23aec.mail.bellsouth.net ([205.152.59.71] verified) by logan.com (CommuniGate Pro SMTP 4.2) with ESMTP id 394728 for flyrotary@lancaironline.net; Sun, 05 Sep 2004 22:58:34 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.71; envelope-from=13brv3@bellsouth.net Received: from rd ([65.6.194.9]) by imf23aec.mail.bellsouth.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040906025804.JUGI1796.imf23aec.mail.bellsouth.net@rd> for ; Sun, 5 Sep 2004 22:58:04 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Rev 3.1 static tests Date: Sun, 5 Sep 2004 21:58:03 -0500 Message-ID: <000c01c493bd$53fa2160$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C49393.6B241960" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C49393.6B241960 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I never hear the rotary folks talk about filters - I think most are = using NO filter, so my comments above are N/A. Thanks David. I wish I could blame it on a filter, but I don't have = one. As I mentioned, it could simply be a bad reading from the TB port. =20 =20 As an odd note, all of my tests have shown the same MAP, but up to 500 = rpm difference. It's my understanding that it takes a significant amount of extra power to go from 5500 to 6000 rpm at full load, so I don't see how = the MAP reading can be accurate. Still thinking about how this all works though. =20 Rusty (I was just kidding Ed) =20 ------=_NextPart_000_000D_01C49393.6B241960 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

I never hear the rotary folks talk about filters - I = think most=20 are using NO filter, so my comments above are N/A.

Thanks = David.  I=20 wish I could blame it on a filter, but I don't have one.  As I = mentioned,=20 it could simply be a bad reading from the TB port.  =
 
As an = odd note, all=20 of my tests have shown the same MAP, but up to 500 rpm difference.  = It's my=20 understanding that it takes a significant amount of extra power to = go from=20 5500 to 6000 rpm at full load, so I don't see how the MAP reading can be = accurate.  Still thinking about how this all works=20 though.
 
Rusty (I = was just=20 kidding Ed)  



------=_NextPart_000_000D_01C49393.6B241960--