X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fmailhost01.isp.att.net ([207.115.11.51] verified) by logan.com (CommuniGate Pro SMTP 5.2.16) with ESMTP id 3867219 for flyrotary@lancaironline.net; Sun, 27 Sep 2009 14:48:25 -0400 Received-SPF: none receiver=logan.com; client-ip=207.115.11.51; envelope-from=bbradburry@bellsouth.net Received: from desktop (adsl-157-211-223.mco.bellsouth.net[70.157.211.223]) by isp.att.net (frfwmhc01) with SMTP id <20090927184750H0100jh3u9e>; Sun, 27 Sep 2009 18:47:50 +0000 X-Originating-IP: [70.157.211.223] From: "Bill Bradburry" To: "'Rotary motors in aircraft'" References: In-Reply-To: Subject: RE: [FlyRotary] EC3 Controller Date: Sun, 27 Sep 2009 14:47:50 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0000_01CA3F81.7D132C20" X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aco/g5XNTFG5TbRDRG+/95uZtnXscgAGd08g X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005 This is a multi-part message in MIME format. ------=_NextPart_000_0000_01CA3F81.7D132C20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Rino, I just noticed that there is a service alert for EC-3s shipped prior to 6-1-08. When did you get yours? Surging could be caused by the EC-3 hunting for a map table address. Are you quite certain that this is not related to the map table? Bill B _____ From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Rino Sent: Sunday, September 27, 2009 11:02 AM To: Rotary motors in aircraft Subject: [FlyRotary] EC3 Controller Tracy, Anyone had a problem with the Renesis crank angle sensor and had to change it. I may have to get a new crank angle sensor, but first I want to check with you guys. Tracy is probably gone to Colorado, maybe someone got this problem before. I cannot get full power on my Renesis for takeoff on Controller A. Seems like controller B works OK. It is not the fuel mixture, I tried that. Actually, when the throttle is wide open the mixture display goes up and down rapidly, from full lean to full rich and the engine surge. I had a similar problem when I first installed and started the Renesis. I had the EC2 controller then and had to get the EC3 to fix the problem. Now it is coming back to me on the EC3, I think. The problem then was with the crank sensor, the EC2 could not handle the sensor signal at more than about 5000 rpm. I think the problem started progressively during the last few hours of flight, at first I thought it was a fuel mixture problem and was trying to ajust for that but now it is not a mixture problem. Since the controller B has NO temp. sensor and works ok, I wonder if it has anything to do with that problem on controller A. Rino Lacombe Renesis powered Glass Goose ------=_NextPart_000_0000_01CA3F81.7D132C20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Rino,

I just noticed that there is a service alert for = EC-3s shipped prior to 6-1-08.  When did you get = yours? 

Surging could be caused by the EC-3 hunting for a = map table address.  Are you quite certain that this is not related to the map = table?

Bill B

 

From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Rino
Sent: Sunday, September = 27, 2009 11:02 AM
To: Rotary motors in aircraft
Subject: [FlyRotary] EC3 Controller

Tracy,<= /p>

 

Anyone had a problem with the Renesis crank angle = sensor and had to change it.  I may have to get a new crank angle sensor, but = first I want to check with you guys.<= /p>

 

Tracy is probably gone to Colorado, maybe someone got this problem before.<= /p>

I cannot get full power on my Renesis for = takeoff on Controller A.  Seems like controller B works OK.<= /p>

It is not the fuel mixture, I tried that.  = Actually, when the throttle is wide open the mixture display goes up and down = rapidly, from full lean to full rich and the engine surge.<= /p>

 

I had a similar problem when I first installed and = started the Renesis.  I had the EC2 controller then and had to get the EC3 = to fix the problem.  Now it is coming back to me on the EC3, I = think.  The problem then was with the crank sensor, the EC2 could not handle the = sensor signal at more than about 5000 rpm.<= /p>

 

I think the problem started progressively during the = last few hours of flight, at first I thought it was a fuel mixture problem = and was trying to ajust for that but now it is not a mixture problem.  = Since the controller B has NO temp. sensor and works ok, I wonder if it has = anything to do with that problem on controller A.<= /p>

 

Rino Lacombe<= /p>

Renesis powered Glass Goose<= /p>

 

------=_NextPart_000_0000_01CA3F81.7D132C20--