X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao102.cox.net ([68.230.241.44] verified) by logan.com (CommuniGate Pro SMTP 5.2.14) with ESMTP id 3742287 for flyrotary@lancaironline.net; Thu, 02 Jul 2009 00:40:44 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.44; envelope-from=rv-4mike@cox.net Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao102.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090702044007.JBRK20976.fed1rmmtao102.cox.net@fed1rmimpo02.cox.net> for ; Thu, 2 Jul 2009 00:40:07 -0400 Received: from wills ([68.105.87.229]) by fed1rmimpo02.cox.net with bizsmtp id Asg51c00K4wtUdQ04sg7WM; Thu, 02 Jul 2009 00:40:07 -0400 X-VR-Score: 0.00 X-Authority-Analysis: v=1.0 c=1 a=JqIssJquC0YA:10 a=7g1VtSJxAAAA:8 a=Ia-xEzejAAAA:8 a=l-G5iGHqT5szc65mPWUA:9 a=MzZpccLkxjN6LL9G8_9v5tSUChoA:4 a=WrMfpB0aAAAA:8 a=eSijWdZYNYxVw2ePQOEA:9 a=50pemenvnR93fZ68GJ0A:7 a=rIGfa0m9I5IhWj4jH3gkkkdyt7AA:4 a=1Erk4P5SMDsA:10 a=EzXvWhQp4_cA:10 X-CM-Score: 0.00 Message-ID: <8DD76D9E72F54ACB8E831117D89E71C3@wills> From: "Mike Wills" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: frustrating couple of days Date: Wed, 1 Jul 2009 21:40:05 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007F_01C9FA94.7F9254D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 This is a multi-part message in MIME format. ------=_NextPart_000_007F_01C9FA94.7F9254D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable John, Thanks for the boost. I've been through the continuity test thing with = wiggling connectors and many hours with an ohmmeter. I'm confident its = not a faulty/intermittent connection issue but have another theory. See = my reply to Ed. Mike ----- Original Message -----=20 From: John Slade=20 To: Rotary motors in aircraft=20 Sent: Wednesday, July 01, 2009 6:36 AM Subject: [FlyRotary] Re: frustrating couple of days >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.=20 The problem is in there somewhere, Mike. Don't let it win. Regards, John Slade -- Homepage: http://www.flyrotary.com/ Archive and UnSub: = http://mail.lancaironline.net:81/lists/flyrotary/List.html ------=_NextPart_000_007F_01C9FA94.7F9254D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
John,
 
 Thanks for the boost. I've been = through the=20 continuity test thing with wiggling connectors and many hours with an = ohmmeter.=20 I'm confident its not a faulty/intermittent connection issue but have = another=20 theory. See my reply to Ed.
 
Mike
----- Original Message -----
From:=20 John Slade
Sent: Wednesday, July 01, 2009 = 6:36=20 AM
Subject: [FlyRotary] Re: = frustrating=20 couple of days

>I'm back to where I was = a year ago=20 and I'm just about fed up with this thing.
I remember that feeling = very=20 well. I had the very same symptoms (among others). Finally I ripped = out the=20 EC2 and EM2 and took them to Tracy personally. He was gracious enough = to check=20 them out while I waited. I can't recall what he found and fixed, but I = do=20 remember that I was getting a bad connection at the EC2 connector. The = male=20 and female parts of the connector were of slightly different design = (the EC2=20 body was upgraded and the cable not), and the pins weren't getting a=20 consistent connection. A slight wiggle of the connector plug would = recreate my=20 symptoms. Once this was fixed the problem went away and never = returned. The=20 EC2 has performed flawlessly ever since, which is good because I don't = think I=20 could have made past another round of errors.
The problem is in = there=20 somewhere, Mike. Don't let it win.
Regards,
John = Slade

--

Homepage:  http://www.flyrotary.com/

Archive and UnSub:   =
http://mail.lancaironline.net:81/lists/flyrotary/List.html
------=_NextPart_000_007F_01C9FA94.7F9254D0--