Return-Path: Received: from [206.228.212.23] (HELO mail.statesville.net) by logan.com (CommuniGate Pro SMTP 4.2b6) with ESMTP id 241614 for flyrotary@lancaironline.net; Sat, 03 Jul 2004 08:53:00 -0400 Received: from TWJames [63.162.171.178] by mail.statesville.net with ESMTP (SMTPD32-8.12) id AC0E12C90154; Sat, 03 Jul 2004 08:52:30 -0400 From: "Tommy James" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: EC2 programming Date: Sat, 3 Jul 2004 08:52:31 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B3_01C460DB.13C92470" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcRf4Uj88lUK4EfsSGi1cGw2NbyWUABGaXSA In-Reply-To: Message-Id: <200407030852343.SM01192@TWJames> X-RBL-Warning: REVDNS: This E-mail was sent from a MUA/MTA 63.162.171.178 with no reverse DNS entry. X-RBL-Warning: SPAMHEADERS: This E-mail has headers consistent with spam [4000020e]. X-Declude-Sender: twjames@statesville.net [63.162.171.178] X-Note: Scanned for Spam This is a multi-part message in MIME format. ------=_NextPart_000_00B3_01C460DB.13C92470 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable John, Ed, et al. Let me echo Ed sage advice. A year or two ago, I had cross wired two = wires to the control module which caused problems similar to what John = discribed. Chase the wires. I hate chasing wires, and just do not want to do it. = So I do it last when I should have done it first.=20 Lot=92s of wires give many opportunites for errors and all on my many problems with tuning the engine have been the results my faulty = soldering, crimping or such. =20 =20 BTW. I just found a faulty crimp in a =BC=94 slip on connector. This = set the stage for insufficient/ intermittent voltage to get to the leading coil. This was the source of months of trouble which I tried to blame on the = EC2 and other stuff. This connector looked great and passed the tug-test, = but it was not making good contact internally and sent only 6.3 volts to the coil. Chase the wires and get rid of all suspect connectors. =93Solder = all connectors=94 is a good rule. Best Regards. Tommy James<>< (if I were not working, I=92d be flying) =20 =20 =20 If none of this has any affect, then I suggest you recheck your wiring = AND your connector pins. Check to make certain that none of those fine = strands of wire have cross over and touched another pin in the DIN connector. Either with a magnifying glass or at least run something around each pin = to make certain you don't have two connected that should not be. =20 =20 Ed. ------=_NextPart_000_00B3_01C460DB.13C92470 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

John, Ed, et al.

Let me echo Ed sage advice. A year = or two ago, I had cross wired two wires to the control module which caused = problems similar to what John discribed.=A0 Chase the wires.=A0 I hate chasing = wires, and just do not want to do it. So I do it last when I should have done it = first.

=A0Lot’s of wires give many opportunites for errors and all on my many problems with tuning the = engine have been the results my faulty soldering, crimping or such.=A0 =

BTW.=A0 I just found a faulty = crimp in a =BC” slip on connector. This set the stage for insufficient/ intermittent = voltage to get to the leading coil. This was=A0 the source of months of trouble = which I tried to blame on the EC2 and other stuff.=A0 This connector looked = great and passed the tug-test, but it was not making good contact internally and = sent only 6.3 volts to the coil.=A0 Chase the wires and get rid of all = suspect connectors.=A0 “Solder all connectors”=A0 is a good = rule.

Best Regards.

Tommy James<>< (if I were = not working, I’d be flying)

If none of this has any affect, then I suggest = you recheck your wiring AND your connector pins. Check to make certain = that none of those fine strands of wire have cross over and touched another = pin in the DIN connector. Either with a magnifying glass or at least run something around each pin to make certain you don't have two = connected that should not be.

Ed.

------=_NextPart_000_00B3_01C460DB.13C92470-- --- [Pre-scanned for viruses by Internet America.]