X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao09.cox.net ([68.230.241.30] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with ESMTP id 984990 for flyrotary@lancaironline.net; Sat, 04 Jun 2005 23:22:38 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.30; envelope-from=dale.r@cox.net Received: from smtp.west.cox.net ([172.18.180.52]) by fed1rmmtao09.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with SMTP id <20050605032149.ZVUQ7275.fed1rmmtao09.cox.net@smtp.west.cox.net> for ; Sat, 4 Jun 2005 23:21:49 -0400 X-Mailer: Openwave WebEngine, version 2.8.15 (webedge20-101-1103-20040528) From: Dale Rogers To: "Rotary motors in aircraft" Subject: [FlyRotary] Re: EC2 problems - solved Date: Sat, 4 Jun 2005 23:21:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20050605032149.ZVUQ7275.fed1rmmtao09.cox.net@smtp.west.cox.net> FWIW, if you think you have such a problem, finding someone with a Time Domain Reflectometer (TDR) can save a lot of troubleshooting time. Check an open-circuit wire from each end. If the reading is different, you have a bad wire. The time signature can even tell you how far down the wire the break (or even partial break) is. Dale R. > From: Bob White > Date: 2005/06/04 Sat PM 07:27:31 EDT > To: "Rotary motors in aircraft" > Subject: [FlyRotary] Re: EC2 problems - solved > > Congratulations John, > > What a relief it must be to actually have an answer. A broken wire > under the insulation is sometimes one of the hardest problems to find. > It could have been worse. It could have worked till heat or vibration > made it quit in flight. > > Bob W. > > On Sat, 4 Jun 2005 15:40:43 -0400 > "John Slade" wrote: > >> Tracy and others. >> Following more than 12 months of battling with EC2 issues I'm pretty sure >> it's Eureka day! >> After rewiring and testing for almost 4 weeks I plugged the EC2 in last >> night, and got exactly the same symptoms as before. NOP flashing indicating >> no communication. I took the EC2 to Buly's plane and tried it in his >> installation. Same NOP, so I was thinking I'd fried it again. Before sending >> it back yet again I decided to install it my plane one more time and see if >> there was a spark. >> >> To my amazement it worked. No NOP, and I could bring up the EC2 data. The >> only thing that changed overnight was that I moved the cable to unplug it. I >> climbed in the back and found that I could make the NOP flash, or stop >> flashing, by moving the cable. I haven't taken the connector apart yet, but >> I'm expecting to find a broken wire inside the insulation, probably near a >> solder joint at the pin. Whenever I bent the connector outward for testing >> it made contact. When I bent it back to plug it in, contact was lost. >> >> Bingo! >> John >> >> Just guessing, but maybe the new EC2 can't communicate with a pre-autotune >> EM2 like Buly's. ???