X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.121] verified) by logan.com (CommuniGate Pro SMTP 5.2.14) with ESMTP id 3744495 for flyrotary@lancaironline.net; Fri, 03 Jul 2009 23:40:08 -0400 Received-SPF: pass receiver=logan.com; client-ip=75.180.132.121; envelope-from=eanderson@carolina.rr.com Received: from computername ([75.191.186.236]) by cdptpa-omta01.mail.rr.com with ESMTP id <20090704033931562.MXDL24657@cdptpa-omta01.mail.rr.com> for ; Sat, 4 Jul 2009 03:39:31 +0000 From: "Ed Anderson" To: "'Rotary motors in aircraft'" Subject: Ignition Check?? Re: frustrating couple of days Date: Fri, 3 Jul 2009 23:39:33 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0057_01C9FC37.84EF5CD0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: Acn8U3hy0xUKVct/S/qLGNpOn6lG1QABQFMw In-Reply-To: Message-Id: <20090704033931562.MXDL24657@cdptpa-omta01.mail.rr.com> This is a multi-part message in MIME format. ------=_NextPart_000_0057_01C9FC37.84EF5CD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mike, I could not help but wonder that when you were unsuccessfully attempting to replicate you B controller problem by switching back and forth - did you also try your ignition check while in B? You mentioned that you normally made an ignition check with controller B on in preparation for flight. However, you did not indicate that you were making such a check when you were trying to duplicate the problem. IF you did not, then I would suggest that you again try to duplicate the problem by switching from A to B, but include the ignition check while in B. Do it a few times and see whether or not B gets corrupted. Ed Ed Anderson Rv-6A N494BW Rotary Powered Matthews, NC eanderson@carolina.rr.com http://www.andersonee.com http://www.dmack.net/mazda/index.html http://www.flyrotary.com/ http://members.cox.net/rogersda/rotary/configs.htm#N494BW http://www.rotaryaviation.com/Rotorhead%20Truth.htm _____ From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Mike Wills Sent: Friday, July 03, 2009 10:59 PM To: Rotary motors in aircraft Subject: [FlyRotary] Re: frustrating couple of days Steve, My staging point is set at 18" which ends up being around 3300RPM. So far I still havent been able to prove for certain that the corruption is linked to switching A > B, much less determine that it only happens above or below the staging point. All 4 of my injectors are the same - checked them all with an ohmmeter. They are all of the type that does not require an external resistor. Mike ----- Original Message ----- From: Steven Boese To: Rotary motors in aircraft Sent: Friday, July 03, 2009 9:13 AM Subject: [FlyRotary] Re: frustrating couple of days Mike, Is 3000 rpm above your staging point? If the corruption of the controller only happens when changing from A to B above the staging point, check to see if one or both secondary injectors have lower resistance than specified. Steve Boese -----Original Message----- From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Mike Wills Sent: Friday, July 03, 2009 9:50 AM To: Rotary motors in aircraft Subject: [FlyRotary] Re: frustrating couple of days Dave, Thanks for the offer and the input. Swapping my EC into your plane would be a desperation last move due to all of the hassles involved. And as you say would not necessarily prove anything. I said it happens when I'm preparing to fly, but that isnt entirely accurate. It would be more accurate to say that in the past it has happened only when I have switched to the back-up controller which usually occurs in prep for flight. This past weekend I had fired it up and taxied down to EAA for lunch. After lunch I taxied back to my hangar and prior to shutting down I ran the engine up to about 3000 RPM and switched to the B controller. The engine died and I had to copy the A program to B to get it to run on B. Switching to B was the only pre takeoff checklist item I performed. I think about the only thing you hit on here that might be related is heat. But hard to say without more instances of failure and a way to link cause and effect. On saturday when the engine quit on B the engine was completely cowled. On sunday when I had the second instance of an engine quitting on B, the upper cowl was off but the lower was on. When the staging point was lost the upper was off, lower on. Yesterday when the engine quit on the first attempt at switching to B the engine was completely uncowled. Maybe I'll run it up a few more times today uncowled and if it works OK, try putting the cowl back on and see if I can induce failure. Doesnt seem likely though that anything under cowl could cause this sort of problem. This may all have to wait until Tracy weighs in with his opinion. I'm not inclined to make drastic changes until I hear from him. Thanks, Mike __________ Information from ESET NOD32 Antivirus, version of virus signature database 3267 (20080714) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ------=_NextPart_000_0057_01C9FC37.84EF5CD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike,

 

I could not help but wonder that = when you were  unsuccessfully attempting to replicate you B controller = problem by switching back and forth - did you also try your ignition check while in = B?   You mentioned that you normally made an ignition check with controller B = on in preparation for flight.  However, you did not indicate that you were making = such a check when you were trying to duplicate the problem. =  

 

IF you did not, then I would = suggest that you again try to duplicate the problem by switching from A to B, but = include the ignition check while in B.  Do it a few times and see whether = or not B gets corrupted.

 

Ed

 

From: = Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Mike Wills
Sent: Friday, July 03, = 2009 10:59 PM
To: Rotary motors in aircraft
Subject: [FlyRotary] Re: frustrating couple of days

 

Steve,

 

My staging point is set at 18" which ends up = being around 3300RPM. So far I still havent been able to prove for certain = that the corruption is linked to switching A > B, much less determine that it = only happens above or below the staging point.

 

All 4 of my injectors are the same - checked them all = with an ohmmeter. They are all of the type that does not require an external resistor.

 

Mike

----- Original Message ----- =

Sent: Friday, = July 03, 2009 9:13 AM

Subject: = [FlyRotary] Re: frustrating couple of days

 

Mike,

 

Is 3000 rpm above your staging = point?  If the corruption of the controller only happens when changing from A to B = above the staging point, check to see if one or both secondary injectors have = lower resistance than specified.

 

Steve = Boese

 

-----Original = Message-----
From: Rotary motors in aircraft = [mailto:flyrotary@lancaironline.net] On Behalf Of Mike Wills
Sent: Friday, July 03, 2009 9:50 AM
To: Rotary motors in aircraft
Subject: [FlyRotary] Re: frustrating couple of days

 

Dave,

 

Thanks for the offer and = the input. Swapping my EC into your plane would be a desperation last move due to = all of the hassles involved. And as you say would not necessarily prove = anything.

 

I said it happens when I'm = preparing to fly, but that isnt entirely accurate. It would be more accurate to = say that in the past it has happened only when I have switched to the = back-up controller which usually occurs in prep for flight. This past = weekend I had fired it up and taxied down to EAA for lunch. After lunch I taxied = back to my hangar and prior to shutting down I ran the engine up to about 3000 = RPM and switched to the B controller. The engine died and I had to copy the A = program to B to get it to run on B. Switching to B was the only pre takeoff checklist item I performed.

 

I think about the only = thing you hit on here that might be related is heat. But hard to say without more = instances of failure and a way to link cause and effect. On saturday when the = engine quit on B the engine was completely cowled. On sunday when I had the = second instance of an engine quitting on B, the upper cowl was off but the = lower was on. When the staging point was lost the upper was off, lower on. = Yesterday when the engine quit on the first attempt at switching to B the engine = was completely uncowled. Maybe I'll run it up a few more times today uncowled and if it = works OK, try putting the cowl = back on and see if I can induce failure. Doesnt seem likely though that anything = under cowl could cause this sort of problem.

 

This may all have to wait = until Tracy weighs in = with his opinion. I'm not inclined to make drastic changes until I hear from = him.

 

Thanks,

 

Mike 



__________ Information from ESET NOD32 Antivirus, version of virus = signature database 3267 (20080714) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

------=_NextPart_000_0057_01C9FC37.84EF5CD0--