X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao105.cox.net ([68.230.241.41] verified) by logan.com (CommuniGate Pro SMTP 5.1.12) with ESMTP id 2392625 for flyrotary@lancaironline.net; Wed, 17 Oct 2007 20:09:54 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.41; envelope-from=alventures@cox.net Received: from fed1rmimpo03.cox.net ([70.169.32.75]) by fed1rmmtao105.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20071018000916.RQGK13814.fed1rmmtao105.cox.net@fed1rmimpo03.cox.net> for ; Wed, 17 Oct 2007 20:09:16 -0400 Received: from BigAl ([72.192.143.193]) by fed1rmimpo03.cox.net with bizsmtp id 1c9F1Y00E4AaN600000000; Wed, 17 Oct 2007 20:09:15 -0400 From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: EM2 tuning Date: Wed, 17 Oct 2007 17:10:39 -0800 Message-ID: <001501c81123$b253e7f0$6401a8c0@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C810E0.A43318F0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Importance: Normal In-Reply-To: This is a multi-part message in MIME format. ------=_NextPart_000_0016_01C810E0.A43318F0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: [FlyRotary] Re: EM2 tuning The blinking fuel used readout is a mystery. It doesn't even have an = upper or lower limit alarm. You seem to fine every possible anomoly Al. =20 Hi; Tracy. This one you should have guessed. The fuel timer function = was set to 'on', so after a certain number of gallons burned it started to = blink - just as it should. Changed that setting to a zero, and the blinking = went away. Figured this out a few weeks ago. Best, Al =20 =20 ------=_NextPart_000_0016_01C810E0.A43318F0 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Subject: [FlyRotary] Re: EM2 tuning

The blinking fuel used readout is a = mystery.  It doesn't even have an upper or lower limit alarm. You seem to fine every possible anomoly Al. 

Hi; Tracy.  This one you should have guessed.  The fuel = timer function was set to ‘on’, so after a certain number of = gallons burned it started to blink – just as it should. Changed that setting to a = zero, and the blinking went away.  Figured this out a few weeks = ago.

Best,

Al

 

 

------=_NextPart_000_0016_01C810E0.A43318F0--