X-Virus-Scanned: clean according to Sophos on Logan.com X-SpamCatcher-Score: 2 [X] Return-Path: Received: from fed1rmmtao09.cox.net ([68.230.241.30] verified) by logan.com (CommuniGate Pro SMTP 5.1.4) with ESMTP id 1724839 for flyrotary@lancaironline.net; Fri, 29 Dec 2006 18:08:52 -0500 Received-SPF: none receiver=logan.com; client-ip=68.230.241.30; envelope-from=alventures@cox.net Received: from fed1rmimpo01.cox.net ([70.169.32.71]) by fed1rmmtao09.cox.net (InterMail vM.6.01.06.03 201-2131-130-104-20060516) with ESMTP id <20061229230804.TUWD18767.fed1rmmtao09.cox.net@fed1rmimpo01.cox.net> for ; Fri, 29 Dec 2006 18:08:04 -0500 Received: from BigAl ([72.192.132.90]) by fed1rmimpo01.cox.net with bizsmtp id 4n7J1W00F1xAn3c0000000; Fri, 29 Dec 2006 18:07:18 -0500 From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: EC2 mixture changes Date: Fri, 29 Dec 2006 15:08:12 -0800 Message-ID: <000001c72b9e$36bafe00$6400a8c0@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C72B5B.289A2F00" 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.3028 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C72B5B.289A2F00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable So far, Al's controller is the only one that I know of that has had this problem. Not unit specific because it has happened on 3 different EC2s = in Al's plane so I have concluded that it is something unique to his installation. I'd like to get to the bottom of it and any other = reports would be helpful. Small point, Tracy, but we've actually seen the issues on just 2 EC2 = units; the original and the current. But even then it would certainly suggest = it is not specific a given 'box'. The one intermediate box in which you had switched the internal connection on the temp sensor, to save me the = trouble, never got past finding the transmit RFI problem, so never determined = whether there was corruption of settings. The connecting PCM and EM2 are still = the same. =20 The really puzzling (and frustrating) thing is that we have had the = scope on every pin on the EC2 connector, and, after eliminating a couple = potential noise issues, we saw nothing that could explain why it is happening. So = the investigation continues. If someone else sees similar behavior, it might provide a clue. =20 Al (perfect weather conditions today, and the plane was ready to go - = but at the last moment I decided I wasn't. Guess I'm fighting some holiday = bug. Bummer.) ------=_NextPart_000_0001_01C72B5B.289A2F00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

So far, Al's controller is the only one that I know of that has had this problem. Not unit specific because it has happened on 3 different = EC2s in Al's plane so I have concluded that it is something unique to his installation. I'd like to get to the bottom of it and any = other reports would be helpful.

Small point, Tracy, but = we’ve actually seen the issues on just 2 EC2 units; the original and the current. But = even then it would certainly suggest it is not specific a given = ‘box’. The one intermediate box in which you had switched the internal connection = on the temp sensor, to save me the trouble, never got past finding the transmit = RFI problem, so never determined whether there was corruption of settings. The = connecting PCM and EM2 are still the same.

The really puzzling (and = frustrating) thing is that we have had the scope on every pin on the EC2 connector, and, = after eliminating a couple potential noise issues, we saw nothing that could = explain why it is happening. So the investigation continues. If someone = else sees similar behavior, it might provide a clue.

Al (perfect weather conditions = today, and the plane was ready to go – but at the last moment I decided I = wasn’t. Guess I’m fighting some holiday bug. Bummer.)

------=_NextPart_000_0001_01C72B5B.289A2F00--