X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fmailhost03.isp.att.net ([204.127.217.103] verified) by logan.com (CommuniGate Pro SMTP 5.2.16) with ESMTP id 3861032 for flyrotary@lancaironline.net; Mon, 21 Sep 2009 11:15:46 -0400 Received-SPF: none receiver=logan.com; client-ip=204.127.217.103; envelope-from=bbradburry@bellsouth.net Received: from desktop (adsl-157-63-231.mco.bellsouth.net[68.157.63.231]) by isp.att.net (frfwmhc03) with SMTP id <20090921151509H0300s7nrpe>; Mon, 21 Sep 2009 15:15:10 +0000 X-Originating-IP: [68.157.63.231] From: "Bill Bradburry" To: "'Rotary motors in aircraft'" References: In-Reply-To: Subject: RE: [FlyRotary] Re: Progress report from Houston Date: Mon, 21 Sep 2009 11:15:14 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01CA3AAC.CB2A1880" X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aco4BKCphj2mj6nwQkenKFMdRgrnDgCyN+Gw X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005 This is a multi-part message in MIME format. ------=_NextPart_000_0009_01CA3AAC.CB2A1880 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mark, I copied the below from an msg from you last Oct.. Which pin on the PCM did you connect to ground? The only pin I can find in the instructions for the PCM that is identified as ground is pin 1 which is called out to be connected to pin 16 on the Controller? Did you splice this wire to ground or did you connect a different pin on the PCM? " Keep in mind that I had some data corruption problems similar to Al Gietzen. It seems to be a problem with fiberglass airplanes, so don't be surprised if you experience this too. With me, it always happened while on the ground. Last time it happened, I looked at each of the 3 tables and saw that only one was actually corrupted, so it is possible that it may have happened in the air, but since I was running above 3800 rpm (and operating in the upper table), I didn't notice any difference. Nobody really knows what causes this problem, but I seem to have fixed it by running a separate ground from the PCM to the forest-of-tabs ground. The thought was that the sub-panel was mounted on a fiberglass frame and therefore was isolated from ground. I have not had an episode since I added the ground." Bill B ------=_NextPart_000_0009_01CA3AAC.CB2A1880 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 Mark,

I copied the below from an msg from you last Oct..  Which = pin on the PCM did you connect to ground?  The only pin I can find in the instructions for the PCM that is identified as ground is pin 1 which is = called out to be connected to pin 16 on the Controller?  Did you splice = this wire to ground or did you connect a different pin on the = PCM?

 

“  Keep in mind that I had some data corruption = problems similar to Al Gietzen.  It seems to be a problem with fiberglass airplanes, so don't be surprised if you experience this too.  With = me, it always  happened while on the ground.  Last time it happened, = I looked at each of the 3 tables and saw that only one was actually = corrupted, so it is possible that it may have happened in the air, but since I was = running above 3800 rpm (and operating in the upper table), I didn't notice any difference.  Nobody really knows what causes this problem, but I = seem to have fixed it by running a separate ground from the PCM to the = forest-of-tabs ground.  The thought was that the sub-panel was mounted on a = fiberglass frame and therefore was isolated from ground.  I have not had an = episode since I added the ground.”

 

Bill B

------=_NextPart_000_0009_01CA3AAC.CB2A1880--