X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.123] verified) by logan.com (CommuniGate Pro SMTP 5.2.15) with ESMTP id 3781004 for flyrotary@lancaironline.net; Sat, 25 Jul 2009 20:37:59 -0400 Received-SPF: pass receiver=logan.com; client-ip=75.180.132.123; envelope-from=eanderson@carolina.rr.com Received: from computername ([75.191.186.236]) by cdptpa-omta02.mail.rr.com with ESMTP id <20090726003720265.JNTH5845@cdptpa-omta02.mail.rr.com> for ; Sun, 26 Jul 2009 00:37:20 +0000 From: "Ed Anderson" To: "'Rotary motors in aircraft'" Subject: The times that test men was [FlyRotary] Just livid..... Date: Sat, 25 Jul 2009 20:37:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcoNhG4/M9uiiCuRSjG4AqDywgMyMQAAYylQ In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Message-Id: <20090726003720265.JNTH5845@cdptpa-omta02.mail.rr.com> Hi Chris, what's that old saying about "...If I didn't have bad luck, I would have no luck at all!....". Clearly, its dismaying to leave a fine running engine, do nothing but let some time pass and then find out the engine now has problems - have you ever heard of gremlins? It certainly difficult to say what may have cause the fuel puddle especially considering all your fuel plumbing has been checked with nothing found amiss. A couple of things come to mind - there was a leak - perhaps ambient heat caused a fitting to expand a bit causing it and contract in cooler temps (wild theory I know). Possibly you missed it - small leaks can be pretty hard to find. I take a piece of white paper and wipe down all fuel lines, if there is any fuel leaking it will show up on the paper. It could be fuel pumped out of the combustion chamber by repeated attempt to start the engine and out the exhaust - not a normal thing, but can happened. Another possibility is your injectors may not be seating properly in the fuel rail. Sometimes the "O" ring just doesn't seat properly, gets worn, had damage, etc. That can cause a leak. When the fuel pump is on and the pressure is high in the line, the pressure causes the "O" ring to seat - but, you turn off the pump the pressure decreases, the "O" ring unseats slightly and fuel leaks out. You turn on the pumps in an attempt to find the leak and nada - because the pressure is now causing the "O" ring to seal. What is even worst, the "O" ring may not unseat each time you turn the pump off - so it may not happen every time. I recall someone else having problems with one controller and it turned out the chip was not fully seated. I recently read a report sent to me by another member of this list that the PLLC type of chip socket used in the EC2 can (rarely but apparently happens often enough to have gotten diagnosed in some electronic applications) even force the chip off its connections through the build up of gas pockets in the plastic of the socket due to heat. This is undoubtedly pretty wild - but you said to include the wild {:>). Given that you found the ground wire to the EC2 broken is a pretty significant find. It first makes me wonder what routes the electrons took through the EC2 to a ground, if the proper ground was not available. Not certain but if it were operated without the designated ground, then that might explain why the A controller is causing problems. Always the potential that some current flowing where it shouldn't or in amounts that it shouldn't could corrupt memory cells. Again a bit wild, but it has happened. If you have an EM2, then I would examine the MCT (fuel map)to see if there is any evidence of it being corrupted. Good luck, Chris - you would do with a bit. 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 -----Original Message----- From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Behalf Of Christopher Barber Sent: Saturday, July 25, 2009 8:03 PM To: Rotary motors in aircraft Subject: [FlyRotary] Just livid..... I have not worked on my engine or electrics in over a week. Last time I ran the engine it ran so well, I wanted to taxi over and pull a first flight. NOT a good idea without wings or a canard. Since then, since the airport is about to force us onto the ramp out of our nice, comfortable hangar in order to repair the roof from damage from Hurricane Ike, I have been refinishing the strakes. I got them sealed up a while back, but I blew off the micro and primer finishing since I wanted to focus on the engine. Finished the UV primer yesterday and they look good and should be good enough to protect from the elements for a bit. So, I go out today and start the engine. I have NOT TOUCHED anything with the engine or electrics in more than a week, it is not starting. Crap. WHAT!!!!! The dreaded NOS!!! CRAP X 10. Whats up with that? Got out, looked under the engine and there was a big puddle of FUEL. Checked all lines. Turned on pumps, checked lines etc and could find nothing. I looked at the wires to the ECU and all was secure, EXCEPT, I notice my main (16gage) ground wire broke at the connector at the ECU. Repaired the wire. I moved the plane and for grins tried to start again. It begrudenly started and ran really badly. I switched to B and it ran much better. Back to A, terrible. I got out and cautiously checked for the leak. NONE found. I shut down and worked on other stuff in disgust. I HAVE NOT TOUCHED ANYTHING TO DO WITH THE ENGINE/ ELECTRICS since it ran well last week. WHATS UP? Thoughts, opinions and Wild a@$ guesses are sought and appreciated. Thanks. All the best, Chris Houston -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html __________ Information from ESET NOD32 Antivirus, version of virus signature database 3267 (20080714) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3267 (20080714) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com