X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from outbound-mail-347.bluehost.com ([66.147.249.8] verified) by logan.com (CommuniGate Pro SMTP 5.2.14) with SMTP id 3741350 for flyrotary@lancaironline.net; Wed, 01 Jul 2009 09:37:48 -0400 Received-SPF: pass receiver=logan.com; client-ip=66.147.249.8; envelope-from=jslade@canardaviation.com Received: (qmail 12896 invoked by uid 0); 1 Jul 2009 13:37:11 -0000 Received: from unknown (HELO host296.hostmonster.com) (66.147.240.96) by outboundproxy7.bluehost.com.bluehost.com with SMTP; 1 Jul 2009 13:37:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=canardaviation.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=J48OFdPjCROYTB9tpH6LxrLf4JjmA2s5zMksz+KWK5EWKgs2/hpXadMclkNGjOke8Dm/GJYxkOJHIceH1fY7jqn4X+HykMustdazgeL47kACZ2TQt99d02JIycCLAm6i; Received: from c-76-108-115-200.hsd1.fl.comcast.net ([76.108.115.200] helo=[192.168.1.4]) by host296.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1MLzzr-0000AZ-7d for flyrotary@lancaironline.net; Wed, 01 Jul 2009 07:37:11 -0600 Message-ID: <4A4B6672.90004@canardaviation.com> Date: Wed, 01 Jul 2009 09:36:50 -0400 From: John Slade User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: Rotary motors in aircraft Subject: Re: [FlyRotary] frustrating couple of days References: In-Reply-To: Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Identified-User: {3339:host296.hostmonster.com:instanu1:canardaviation.com} {sentby:smtp auth 76.108.115.200 authed with jslade+canardaviation.com} >I'm back to where I was a year ago and I'm just about fed up with this thing.
I remember that feeling very well. I had the very same symptoms (among others). Finally I ripped out the EC2 and EM2 and took them to Tracy personally. He was gracious enough to check them out while I waited. I can't recall what he found and fixed, but I do remember that I was getting a bad connection at the EC2 connector. The male and female parts of the connector were of slightly different design (the EC2 body was upgraded and the cable not), and the pins weren't getting a consistent connection. A slight wiggle of the connector plug would recreate my symptoms. Once this was fixed the problem went away and never returned. The EC2 has performed flawlessly ever since, which is good because I don't think I could have made past another round of errors.
The problem is in there somewhere, Mike. Don't let it win.
Regards,
John Slade