X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from imf22aec.mail.bellsouth.net ([205.152.59.70] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with ESMTP id 984653 for flyrotary@lancaironline.net; Sat, 04 Jun 2005 15:41:31 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.70; envelope-from=sladerj@bellsouth.net Received: from ibm65aec.bellsouth.net ([68.215.26.154]) by imf22aec.mail.bellsouth.net with ESMTP id <20050604194046.OKBJ28885.imf22aec.mail.bellsouth.net@ibm65aec.bellsouth.net> for ; Sat, 4 Jun 2005 15:40:46 -0400 Received: from JSLADE ([68.215.26.154]) by ibm65aec.bellsouth.net with ESMTP id <20050604194045.WXYF2762.ibm65aec.bellsouth.net@JSLADE> for ; Sat, 4 Jun 2005 15:40:45 -0400 From: "John Slade" To: "Rotary motors in aircraft" Subject: EC2 problems - solved Date: Sat, 4 Jun 2005 15:40:43 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02BF_01C5691B.C4DEB3D0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal This is a multi-part message in MIME format. ------=_NextPart_000_02BF_01C5691B.C4DEB3D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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. ??? ------=_NextPart_000_02BF_01C5691B.C4DEB3D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Tracy and=20 others.
Following more than 12 months of battling with EC2 = issues I'm=20 pretty sure it's Eureka day!
After=20 rewiring and testing for almost 4 weeks I plugged the EC2 in last night, = and got=20 exactly the same symptoms as before. NOP flashing indicating no = communication. I=20 took the EC2 to Buly's plane and tried it in his installation. Same NOP, = so I=20 was thinking I'd fried it again. Before sending it back yet again I = decided to=20 install it my plane one more time and see if there was a spark.=20
 
To my=20 amazement it worked. No NOP, and I could bring up the EC2 data. The only = thing=20 that changed overnight was that I moved the cable to unplug it. I = climbed in the=20 back and found that I could make the NOP flash, or stop flashing, by = moving the=20 cable. I haven't taken the connector apart yet, but I'm expecting = to find a=20 broken wire inside the insulation, probably near a solder joint at the = pin.=20 Whenever I bent the connector outward for testing it made contact. = When I=20 bent it back to plug it in, contact was lost.
 
Bingo!
John
 
Just guessing, but maybe the = new EC2 can't=20 communicate with a pre-autotune EM2 like Buly's.=20 ???
------=_NextPart_000_02BF_01C5691B.C4DEB3D0--