Message

Return-Path: <13brv3@bellsouth.net> Received: from imf08aec.mail.bellsouth.net ([205.152.59.56] verified) by logan.com (CommuniGate Pro SMTP 4.1.6) with ESMTP id 2708524 for flyrotary@lancaironline.net; Mon, 03 Nov 2003 19:33:59 -0500 Received: from rad ([68.212.11.237]) by imf20aec.mail.bellsouth.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20031103235435.GPTT1780.imf20aec.mail.bellsouth.net@rad> for ; Mon, 3 Nov 2003 18:54:35 -0500 From: "Russell Duffy" <13brv3@bellsouth.net> To: "Flyrotary List" Subject: Dual MAP table adjustment Date: Mon, 3 Nov 2003 17:54:36 -0600 Message-ID: <000001c3a265$d6a63800$6001a8c0@rad> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C3A233.8C0E3900" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C3A233.8C0E3900 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, =20 I took a shot at setting my dual map table today, and I'm not quite sure this is exactly how it's supposed to work (see log entry below). Has = anyone else done this yet? Tracy, is this what you would expect? =20 11-03-03 =20 =20 Removed the prop, and ran the engine today, so I could set the dual MAP table. This is supposed to be effective when the rpm is greater than = 2400, and the MAP is low. I noticed that the MAP doesn't really change, from = 2400 up to about 5500, which is as high as I went. The reading on my vacuum gauge was about 19", which I know to really be about 17" of vacuum on a calibrated gauge. This gives a MAP of 13", which is lower than I = believe Tracy expects it to be. When doing the mixture adjustment, I noticed = that the mixture never changes through the throttle range, which makes sense = I guess since the MAP doesn't change either. On the A controller, the = mixture was way lean, which is the same thing I see on descents, so I raised it = to about the first yellow bar on the mixture gauge. The B controller was = right on, so maybe the difference is temperature related. Anyway, I put the = prop back on, and will see how it does on the next flight.=20 =20 Rusty =20 PS- I measured 102 db at the left wing tip, with the engine running at = 2500 rpm, with no prop. The pipe from the turbo is pointing almost directly = at the db meter. I need to test a Lycosaur someday. =20 =20 =20 ------=_NextPart_000_0001_01C3A233.8C0E3900 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Greetings,

I = took a shot at=20 setting my dual map table today, and I'm not quite sure this is exactly = how it's=20 supposed to work (see log entry below). Has anyone else done this=20 yet? Tracy, is this what you would = expect?

11-03-03

Removed the=20 prop, and ran the engine today, so I could set the dual MAP table. This is supposed to be = effective when=20 the rpm is greater than 2400, and the MAP is low. I noticed that the MAP = doesn’t really=20 change, from 2400 up to about 5500, which is as high as I went. The reading on my vacuum gauge = was about=20 19”, which I know to really be about 17” of vacuum on a = calibrated gauge. This gives a MAP of 13”, = which is lower=20 than I believe Tracy expects = it to=20 be. When doing the = mixture=20 adjustment, I noticed that the mixture never changes through the = throttle range,=20 which makes sense I guess since the MAP doesn’t change = either. On the A controller, the = mixture was way=20 lean, which is the same thing I see on descents, so I raised it to about = the=20 first yellow bar on the mixture gauge. =20 The B controller was right on, so maybe the difference is = temperature=20 related. Anyway, I put = the prop=20 back on, and will see how it does on the next flight.

Rusty

PS- I measured 102 = db at the left=20 wing tip, with the engine running at 2500 rpm, with no = prop. The pipe=20 from the turbo is pointing almost directly at the db meter. I need = to test=20 a Lycosaur someday.

<= /DIV> ------=_NextPart_000_0001_01C3A233.8C0E3900--