Received-SPF: none
 receiver=logan.com; client-ip=68.142.229.99; envelope-from=sladerj@sbcglobal.net
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=sbcglobal.net;
  h=Received:X-YMail-OSG:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
  b=30vTp/zc7iyQQDnmeLC2tpF5Gf4SpsaN9uPxKwzeVl5xgEQS6rF4FbA0Eo4cTH7TXqsa69Yx2PeMQR8N+VH72w8740r7apubUQBzERmL2PqTmelOZwNVWNwbkHIiejluzeGt7+Ttd9F14JTkHRHI2A0WUh4HdaHeMODeth28MBk=  ;
Message-ID: <4595A882.50200@sbcglobal.net>
Date: Fri, 29 Dec 2006 18:45:06 -0500
From: John Slade <sladerj@sbcglobal.net>
Reply-To:  sladerj@sbcglobal.net
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Rotary motors in aircraft <flyrotary@lancaironline.net>
Subject: Re: [FlyRotary] Re: Yet another non-event story
References: <list-1723949@logan.com>
In-Reply-To: <list-1723949@logan.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Yes, Jeff.
I had various problems with wiring, connections and internal EC2 issues 
(some of which were caused by inadvertent smoke release on my part). In 
my case the EC2 program A would simply reset at all zeros. I'd restore 
the defaults, run the engine for a while and bingo - back to the zeros. 
Program B was unaffected. I finally traced one problem to a bad 
connection at the DB36 connector on the EC2. The pins weren't going all 
the way in. I think this was because the male and female parts of the 
DB36 were not a matched pair. Each was of slightly different design. 
Perhaps Tracy changed suppliers somewhere between the original EC2 
release and the later one I upgraded to. One of the intermittent 
connections was the one to the EM2. I eventually found it by pulling on 
the cable. Tracy also replaced some of the chips in my EC2. I'm still 
not certain what was causing the programming changes. I'm just thankful 
I was dealing with RWS and not some company in Australia. On one 
occasion I took the EC2 and EM2 by hand to Tracy. Laura gave me an ice 
cream while I waited for him to fix them. You just can't beat that for 
service!
John
82.6 hrs and no more EC2 or EM2 problems.

Jeff Owen wrote:
> Al,
>
> I seem to recall John Slade had similar problems with the programming
> suddenly changing in an EC2.  I believe he ultimately traced the problem to
> intermittent connections between the EC2 and EM2.
>
> John,
>
> If you are listening, what was the root cause?
>
> Jeff Owen
>
> -----Original Message-----
> From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On
> Behalf Of Al Gietzen
> Sent: Friday, December 29, 2006 6:59 AM
> To: Rotary motors in aircraft
> Subject: [FlyRotary] Re: Yet another non-event story
>
>
>   
>>> I noticed my mixture bar was going from lean to totally
>>>       
>> desapearing. Turning the knob to full rich was not enough.
>> I saw this a few times.
>>     
>
> Buly;
>
> It would be interesting to know if you had it previously tuned giving you
> correct mixture.  I have had on-going problems with spurious changes to
> settings in the EC2.  Carefully tune it one day, and find things have
> changed the next, and have had tuning changes occur during flight.  I have
> noted changes in the mixture table, stage point setting, injector pulse
> width. Many, many hours spent trying to determine cause, but as yet no
> explanation.  It has been assumed that it is specific to my installation -
> composite pusher with EC control box at the firewall, EM2 acquisition module
> at the firewall, display on the panel.  The problem is primarily with
> controller A which communicates with the EM2.
>
> This may not be relevant to your installation, but it would be worth paying
> close attention to getting it tuned correctly, and see if it stays that way.
>
> Al
>
>
> --
> Homepage:  http://www.flyrotary.com/
> Archive and UnSub:   http://mail.lancaironline.net/lists/flyrotary/
>
>
>
> --
> Homepage:  http://www.flyrotary.com/
> Archive and UnSub:   http://mail.lancaironline.net/lists/flyrotary/
>
>