X-Virus-Scanned: clean according to Sophos on Logan.com X-SpamCatcher-Score: 10 [X] Return-Path: Received: from bay0-omc3-s16.bay0.hotmail.com ([65.54.246.216] verified) by logan.com (CommuniGate Pro SMTP 5.1.4) with ESMTP id 1724050 for flyrotary@lancaironline.net; Fri, 29 Dec 2006 12:24:26 -0500 Received-SPF: pass receiver=logan.com; client-ip=65.54.246.216; envelope-from=lors01@msn.com Received: from hotmail.com ([65.54.250.89]) by bay0-omc3-s16.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Fri, 29 Dec 2006 09:23:38 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 29 Dec 2006 09:23:38 -0800 Message-ID: Received: from 4.171.174.80 by BAY115-DAV17.phx.gbl with DAV; Fri, 29 Dec 2006 17:23:35 +0000 X-Originating-IP: [4.171.174.80] X-Originating-Email: [lors01@msn.com] X-Sender: lors01@msn.com From: "Tracy Crook" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: EC2 mixture changes Date: Fri, 29 Dec 2006 12:23:31 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0099_01C72B44.26ECEBA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: MSN 9 X-MimeOLE: Produced By MSN MimeOLE V9.50.0034.2000 Seal-Send-Time: Fri, 29 Dec 2006 12:23:31 -0500 X-OriginalArrivalTime: 29 Dec 2006 17:23:38.0350 (UTC) FILETIME=[13E4B0E0:01C72B6E] Return-Path: lors01@msn.com This is a multi-part message in MIME format. ------=_NextPart_000_0099_01C72B44.26ECEBA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Good suggestion from Al, Buly. I can't remember, do you have an EM2? = If so, check the MAP table with the EM2 and get familiar with what the = correction curves look like for your engine (no two are exactly alike). = Good idea to check it periodically for any signs of data corruption if = you think something is amiss. So far, Al's controller is the only one = that I know of that has had this problem. Not unit specific because it = has happened on 3 different EC2s in Al's plane so I have concluded that = it is something unique to his installation. I'd like to get to the = bottom of it and any other reports would be helpful. Al and two other composite aircraft have reported mixture changes when = transmitting on the radio. Sometimes the problem is frequency specific. = I have identified a fix for this and it should be implemented on any = EC2 that exhibits this problem. A .1 uF capacitor is added directly = across pins 1 and 2 of the A controller MAP sensor to eliminate this = problem (B controller is not affected). RFI problems are a bitch to = find sometimes. There is already a capacitor across these two pins on = both A & B controllers. The one on A is only a couple of inches away = from the sensor on the circuit board but that makes all the difference. = The part must be physically close to the sensor to eliminate this RFI = problem. All future EC2s will have this added capacitor installed. You can experience odd changes in the EC2 behavior for several other = reasons. For example, I have to change the mixture control from the = normal position when I do a hot start and take off because the air temp = sensor has been heat-soaked from heat in the engine room. As it cools = off on takeoff, the mixture gets richer and I then return the mixture = control to it's normal position. =20 Tracy (autopilot installation hell almost over)=20 ----- Original Message -----=20 From: Al Gietzen=20 To: Rotary motors in aircraft=20 Sent: Friday, December 29, 2006 9:58 AM Subject: [FlyRotary] Re: Yet another non-event story > >I noticed my mixture bar was going from lean to totally =20 > desapearing. Turning the knob to full rich was not enough. > I saw this a few times. Buly; It would be interesting to know if you had it previously tuned giving = you correct mixture. I have had on-going problems with spurious changes = to settings in the EC2. Carefully tune it one day, and find things have changed the next, and have had tuning changes occur during flight. I = have noted changes in the mixture table, stage point setting, injector = pulse width. Many, many hours spent trying to determine cause, but as yet no explanation. It has been assumed that it is specific to my = installation - composite pusher with EC control box at the firewall, EM2 acquisition = module at the firewall, display on the panel. The problem is primarily with controller A which communicates with the EM2. This may not be relevant to your installation, but it would be worth = paying close attention to getting it tuned correctly, and see if it stays = that way. Al -- Homepage: http://www.flyrotary.com/ Archive and UnSub: = http://mail.lancaironline.net/lists/flyrotary/ ------=_NextPart_000_0099_01C72B44.26ECEBA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Good suggestion from Al,  Buly.  I can't remember, do you = have an EM2?  If so, check the MAP table with the EM2 and get = familiar=20 with what the correction curves look like for your engine (no two=20 are exactly alike).  Good idea to check it periodically for = any signs=20 of data corruption if you think something is amiss. So far, Al's = controller=20 is the only one that I know of that has had this problem.  Not unit = specific because it has happened on 3 different EC2s in Al's plane so I = have=20 concluded that it is something unique to his installation.   = I'd like=20 to get to the bottom of it and any other reports would be helpful.
 
Al and two other composite aircraft have reported mixture changes = when=20 transmitting on the radio.  Sometimes the problem is frequency=20 specific.  I have identified a fix for this and it should be = implemented on=20 any EC2 that exhibits this problem.  A .1 uF capacitor is added = directly=20 across pins 1 and 2 of the A controller MAP sensor to eliminate this = problem (B=20 controller is not affected).    RFI problems are a bitch = to find=20 sometimes.  There is already a capacitor across these two pins on = both A=20 & B controllers.  The one on A is only a couple of inches away = from the=20 sensor on the circuit board but that makes all the difference.  The = part=20 must be physically close to the sensor to eliminate this RFI = problem.  All=20 future EC2s will have this added capacitor installed.
 
You can experience odd changes in the EC2 behavior for several = other=20 reasons.  For example,  I have to change the mixture = control from=20 the normal position when I do a hot start and take off because  the = air=20 temp sensor has been heat-soaked from heat in the engine = room.  =20 As it cools off on takeoff, the mixture gets richer and I then return = the=20 mixture control to it's normal position.  
 
Tracy (autopilot installation hell almost over) 
 
 
----- Original Message -----
From: Al Gietzen
To: Rotary motors in = aircraft
Sent: Friday, December 29, 2006 = 9:58=20 AM
Subject: [FlyRotary] Re: Yet = another=20 non-event story

> >I noticed my mixture bar was going from lean = to=20 totally 
> desapearing. Turning the knob to full rich was = not=20 enough.
> I saw this a few times.

Buly;

It would = be=20 interesting to know if you had it previously tuned giving = you
correct=20 mixture.  I have had on-going problems with spurious changes=20 to
settings in the EC2.  Carefully tune it one day, and find = things=20 have
changed the next, and have had tuning changes occur during=20 flight.  I have
noted changes in the mixture table, stage = point=20 setting, injector pulse
width. Many, many hours spent trying to = determine=20 cause, but as yet no
explanation.  It has been assumed that it = is=20 specific to my installation -
composite pusher with EC control box = at the=20 firewall, EM2 acquisition module
at the firewall, display on the=20 panel.  The problem is primarily with
controller A which = communicates=20 with the EM2.

This may not be relevant to your installation, = but it=20 would be worth paying
close attention to getting it tuned = correctly, and=20 see if it stays that way.

Al


--
Homepage:  = http://www.flyrotary.com/
Archi= ve and=20 UnSub:   http://mail.lanca= ironline.net/lists/flyrotary/
------=_NextPart_000_0099_01C72B44.26ECEBA0--