X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao103.cox.net ([68.230.241.43] verified) by logan.com (CommuniGate Pro SMTP 5.2.14) with ESMTP id 3744945 for flyrotary@lancaironline.net; Sat, 04 Jul 2009 14:16:29 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.43; envelope-from=alventures@cox.net Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090704181548.LLJX2915.fed1rmmtao103.cox.net@fed1rmimpo02.cox.net> for ; Sat, 4 Jul 2009 14:15:48 -0400 Received: from BigAl ([72.192.133.78]) by fed1rmimpo02.cox.net with bizsmtp id BuFo1c0031hf1Cg04uFo5H; Sat, 04 Jul 2009 14:15:48 -0400 X-VR-Score: -50.00 X-Authority-Analysis: v=1.0 c=1 a=X4USj3ZiZboA:10 a=Ia-xEzejAAAA:8 a=vDOyT-y18MnaAmfd-9gA:9 a=AG86VaKA-o9SrKJDg7MA:7 a=BEqj5gmlE4-cgt3tt-C04f7jHWAA:4 a=EzXvWhQp4_cA:10 a=YXKIYKZ_iZm02vdn9zUA:9 a=X0WOP95HE8vOBxf_kO8A:7 a=dmH1hfD9nnPswD8E9K76e8Ue_p4A:4 a=8XSl6_4hpfkA:10 X-CM-Score: 0.00 From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Corruption of EC settings Date: Sat, 4 Jul 2009 11:16:23 -0800 Message-ID: <493D22B56C004DC1A4FF6F653EEFB44F@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002E_01C9FC98.DD654580" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6838 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: Importance: Normal Thread-Index: Acn8VwmWnY+dMEPPST6KtRikSCbnIwAg+HTg This is a multi-part message in MIME format. ------=_NextPart_000_002E_01C9FC98.DD654580 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike; Your experience of the problems is quite different than mine, so the ultimate cause is probably different as well. My B controller was = always more stable than A; so when things changed, I could switch to B. From = about hour 3 to about 15 I flew mostly using controller B while we tried to = figure out what was going on. =20 Al =20 -----Original Message----- From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Mike Wills Sent: Friday, July 03, 2009 7:24 PM To: Rotary motors in aircraft Subject: [FlyRotary] Re: Corruption of EC settings =20 Al, =20 No I was not aware that you went through similar problems. I was off = this forum for about 4 years during which time you completed your project and flew it. =20 Your experience seems similar to mine. If anything yours sounds more = severe. Looking back over the past year and a half since I had my first engine start, I've realized that I've gone through very long stretches without = any of these problems. In fact the first 20 hours of ground run time I had = all of the typical (many self induced) tuning issues, but no cases of = corrupt data that I could identify. It wasnt until after my first flight that I = had it happen. Three times and then I grounded the airplane. In the = subsequent 4 months and an additional 5 hours of run time on the ground there were no instances of corrupt data until this past weekend when I started = prepping to resume test flying. Since then in about 2 hours of ground running I've = had 4 instances of corrupt data. Three cases where it wouldnt run on B, but = since I have no way to know whats loaded in B I dont know what exactly is happening there. And one case of the staging point on the A controller changing to 12". =20 I could probably resume test flying as long as I remain over the = airport. But given my phase 1 test area and the terrain I'd have to cross to get = to something landable I wouldnt want to venture too far from Brown Field = with it like it is. Whats the point of having a backup controller if you have = no confidence in it? =20 My EC2 is also an early one. I've had it so long I cant recall when I = bought it! So as you say, newer units may not have similar issues. And of = course in my case since the problem is unresolved at this point, it may still be = an installation issue, though at this point I'm stumped as to what that = issue may be. I agree that the EC2 is the best option for the application. = When not having these problems, the engine runs great. Which of course is = part of the frustration - with it running so good why cant I go fly it and have confidence in it? =20 No opportunity to do any further testing today but hope to get back on = it tomorrow. I've sprung an oil leak (previously thought repaired) that I = need to fix before I can start the engine again. =20 Mike =20 ------=_NextPart_000_002E_01C9FC98.DD654580 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike;

Your experience of the problems = is quite different than mine, so the ultimate cause is probably different as = well.  My B controller was always more stable than A; so when things changed, I = could switch to B.  From about hour 3 to about 15 I flew mostly using = controller B while we tried to figure out what was going on.

 

Al

 

-----Original = Message-----
From: Rotary motors in = aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Mike Wills
Sent: Friday, July 03, = 2009 7:24 PM
To: Rotary motors in = aircraft
Subject: [FlyRotary] Re: Corruption of EC settings

 

Al,

 

No I was not aware that you = went through similar problems. I was off this forum for about 4 years during = which time you completed your project and flew it.

 

Your experience seems = similar to mine. If anything yours sounds more severe. Looking back over the past = year and a half since I had my first engine start, I've realized that I've gone = through very long stretches without any of these problems. In fact the first 20 = hours of ground run time I had all of the typical (many self induced) tuning = issues, but no cases of corrupt data that I could identify. It wasnt until = after my first flight that I had it happen. Three times and then I grounded = the airplane. In the subsequent 4 months and an additional 5 hours of run = time on the ground there were no instances of corrupt data until this past = weekend when I started prepping to resume test flying. Since then in about 2 hours of = ground running I've had 4 instances of corrupt data. Three cases where it = wouldnt run on B, but since I have no way to know whats loaded in B I dont know what exactly is happening there. And one case of the staging point on the A controller changing to 12".

 

I could probably resume = test flying as long as I remain over the airport. But given my phase 1 test area and = the terrain I'd have to cross to get to something landable I wouldnt want to venture too far from Brown Field with it like it is. Whats the point of = having a backup controller if you have no confidence in it?

 

My EC2 is also an early = one. I've had it so long I cant recall when I bought it! So as you say, newer = units may not have similar issues. And of course in my case since the problem is unresolved at this point, it may still be an installation issue, though = at this point I'm stumped as to what that issue may be. I agree that the EC2 is the best option for the application. When not having these problems, the engine runs great. Which of course is part of the frustration - with it running so good why cant I go fly it and have = confidence in it?

 

No opportunity to do any = further testing today but hope to get back on it tomorrow. I've sprung an oil = leak (previously thought repaired) that I need to fix before I can start the = engine again.

 

Mike

=

 

------=_NextPart_000_002E_01C9FC98.DD654580--