X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: <13brv3@bellsouth.net> Received: from imf17aec.mail.bellsouth.net ([205.152.59.65] verified) by logan.com (CommuniGate Pro SMTP 4.3c5) with ESMTP id 946710 for flyrotary@lancaironline.net; Mon, 16 May 2005 21:18:08 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.65; envelope-from=13brv3@bellsouth.net Received: from ibm57aec.bellsouth.net ([65.6.194.9]) by imf17aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20050517011722.RAGY12557.imf17aec.mail.bellsouth.net@ibm57aec.bellsouth.net> for ; Mon, 16 May 2005 21:17:22 -0400 Received: from rd ([65.6.194.9]) by ibm57aec.bellsouth.net (InterMail vG.1.02.00.01 201-2136-104-101-20040929) with ESMTP id <20050517011722.PRBH23538.ibm57aec.bellsouth.net@rd> for ; Mon, 16 May 2005 21:17:22 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: EC2 Problem suggestion Date: Mon, 16 May 2005 20:17:27 -0500 Message-ID: <000001c55a7e$30b0f610$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C55A54.47DAEE10" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C55A54.47DAEE10 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable John (Tracking Tracy through Arkansas)=20 =20 I hope he doesn't check the list, or he'll never come back :-) =20 I've read your latest tale of woe, and just can't point to any sort of smoking gun, though ignition is looking mighty suspicious. As much as I know you don't want to hear this, please consider having someone else = look at your wiring. The fact is that it worked with the old wiring, but = doesn't work now, which I'm afraid leads me to suspect there is still some sort = of error with the new wiring. =20 =20 I've told this tale before, but when I was an MRI specialist, I made = quite a few trips that turned out to be simple fixes. In these cases, it was = due to a simple oversight that the service guy made. Once the problem was = pointed out, in almost every case, they just couldn't believe they had done what they did. I equate this to some sort of practical joke our brains play = on us. No matter how many times you look, once you're convinced it's = right, you won't see it any other way. Sometimes you just need a fresh pair of eyes to look at things. =20 =20 Hang in there John. =20 =20 Cheers, Rusty =20 =20 ------=_NextPart_000_0001_01C55A54.47DAEE10 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
John=20 (Tracking Tracy through Arkansas) 
 
I hope he = doesn't check the=20 list, or he'll never come back=20 :-)
 
I've read your = latest tale=20 of woe, and just can't point to any sort of smoking gun, though ignition = is=20 looking mighty suspicious.  As much as I know you don't = want to=20 hear this, please consider having someone else look at your = wiring. =20 The fact is that it worked with the old wiring, but doesn't work = now, which=20 I'm afraid leads me to suspect there is still some sort of error with = the new=20 wiring.  
 
I've told this = tale before,=20 but when I was an MRI specialist, I made quite a few trips that = turned out=20 to be simple fixes.  In these cases, it was due to a simple = oversight that=20 the service guy made.  Once the problem was pointed out, in=20 almost every case, they just couldn't believe they had done what = they=20 did.  I equate this to some sort of practical joke our brains = play on=20 us.  No matter how many times you look, once you're convinced it's = right,=20 you won't see it any other way.  Sometimes you just need a fresh = pair of=20 eyes to look at=20 things.  
 
Hang in=20 there John.  
 
Cheers,<= /FONT>
Rusty
  
 
------=_NextPart_000_0001_01C55A54.47DAEE10--