Return-Path: Received: from ms-smtp-01.southeast.rr.com ([24.93.67.82] verified) by logan.com (CommuniGate Pro SMTP 4.1.3) with ESMTP id 2586567 for flyrotary@lancaironline.net; Sat, 20 Sep 2003 00:29:48 -0400 Received: from o7y6b5 (clt78-020.carolina.rr.com [24.93.78.20]) by ms-smtp-01.southeast.rr.com (8.12.5/8.12.2) with SMTP id h8K4MM0R003204 for ; Sat, 20 Sep 2003 00:22:24 -0400 (EDT) Message-ID: <001a01c37f2f$78b31aa0$1702a8c0@WorkGroup> From: "Ed Anderson" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: EC2 in-flight timing adjustment. Date: Sat, 20 Sep 2003 00:27:15 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01C37F0D.F0F9A1E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 This is a multi-part message in MIME format. ------=_NextPart_000_0017_01C37F0D.F0F9A1E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I think I will check with Tracy to make certain screwing with the = timing on one processor won't screw it up on the other. I am 99% = certain - buuuttttt want to be sure. Ed Anderson Yep, A & B controllers are 100% independent on programming. The proceedure I use in-flight is: 1. Establish normal cruise and get the plane *perfectly* trimmed in = zero turbulance air. 2. Lean engine for best economy. This is about 1525 - 1550 EGT on = mine. This varies with altitude & powersetting. 3. Put EC2 in mode 8 and advance timing 1 step (1.875 degrees) and = note change in rpm (a digital tach w/ <=3D 10 rpm resolution is a must). 4. If you got an increase at step 3, repeat until there is no = increase in rpm. 5. Retard the timing 1 step. Factors to keep in mind. My cruise is typically at 17 - 18" MAP = which is below the manifold pressure advance point (this point is = adjustable in Mode 6). The timing is advanced by 5.625 degrees more = than nominal timing which is typically 20 - 23 deg BTDC at rpm > 3600. =20 I think mine is advanced 1 or 2 steps from default setting. Tracy Thanks for the tips, Tracy One thing not certain I am clear on. When you set your timing as = above, is that just for your cruise flight and do you set it differently = say for take off and climb phase? Or just find the optimum as you do = and then leave it set at that for all else? Ed ------=_NextPart_000_0017_01C37F0D.F0F9A1E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I think I will = check with=20 Tracy to make certain screwing with the timing on one processor won't = screw it=20 up on the other. I am 99% certain - buuuttttt want to be=20 sure.

Ed Anderson

Yep, A & B controllers are 100% independent = on=20 programming.

The proceedure I use in-flight is:

1. Establish normal cruise and get the = plane=20 *perfectly* trimmed in zero turbulance air.

2. Lean engine for best economy. = This is about=20 1525 - 1550 EGT on mine. This varies with altitude &=20 powersetting.

3. Put EC2 in mode 8 and advance timing 1 = step=20 (1.875 degrees) and note change in rpm (a digital tach w/ <=3D 10 = rpm=20 resolution is a must).

4. If you got an increase at step 3, = repeat until=20 there is no increase in rpm.

5. Retard the timing 1 step.

Factors to keep in mind. My cruise is = typically at=20 17 - 18" MAP which is below the manifold pressure advance point = (this=20 point is adjustable in Mode 6). The timing is advanced by = 5.625=20 degrees more than nominal timing which is typically 20 - 23 deg BTDC = at rpm=20 > 3600.

I think mine is advanced 1 or 2 steps from = default=20 setting.

Tracy

Thanks for the tips, Tracy

One thing not certain I am clear on. When = you set=20 your timing as above, is that just for your cruise flight and do you = set it=20 differently say for take off and climb phase? Or just find the = optimum=20 as you do and then leave it set at that for all else?

Ed

------=_NextPart_000_0017_01C37F0D.F0F9A1E0--