X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from an-out-0708.google.com ([209.85.132.249] verified) by logan.com (CommuniGate Pro SMTP 5.1.12) with ESMTP id 2352978 for flyrotary@lancaironline.net; Wed, 26 Sep 2007 11:16:03 -0400 Received-SPF: pass receiver=logan.com; client-ip=209.85.132.249; envelope-from=rwstracy@gmail.com Received: by an-out-0708.google.com with SMTP id b2so305774ana for ; Wed, 26 Sep 2007 08:15:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=t8mtr6FV0dhbCFXfOjoroQHhELFLRAYSznr+lCysNus=; b=YncIitSi/QMaTmPIojoQ5c9h9EC3GA0/TAqUTv8iI3j+IYI/ut/yokyM3gNGRKI8yzJ/rcSewGLYykJ5Npnc5lBZPzkZ8zsyuSnsQN7+FJ1Nmgrpfw1fwJ0rUBTNmFZC4bQ6DHPeIjH1YOxt0GvZ/Mo2T3XA8G+m1SUibzPvAkM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=ni0qF1sqltn+7UGwrQcUpi6hPmxiqS9V5jpTFlCJ2fYlNXMVYGAytxH8Q/9aQGb6qsRIBR+oFfKQBlWMcU6s9kGrkPKichtBVpxAXvh0PTiLPOX1IUNwhWwLsI0Mwss0RpCirmC5WlnCU6x0jPEorYKtook69mpJv+EvTXoa/wA= Received: by 10.142.171.6 with SMTP id t6mr720345wfe.1190819723026; Wed, 26 Sep 2007 08:15:23 -0700 (PDT) Received: by 10.143.28.1 with HTTP; Wed, 26 Sep 2007 08:15:22 -0700 (PDT) Message-ID: <1b4b137c0709260815p7736bbe4pd56e4edd54781bbf@mail.gmail.com> Date: Wed, 26 Sep 2007 11:15:22 -0400 From: "Tracy Crook" Sender: rwstracy@gmail.com To: "Rotary motors in aircraft" Subject: Re: [FlyRotary] EM2 tuning In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8164_20951922.1190819722993" References: X-Google-Sender-Auth: 6a7ccc65513bac6c ------=_Part_8164_20951922.1190819722993 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Depends on which channels you saw the change on. The calibration on some functions has changed over the various versions (but most have remained the same). The blinking fuel used readout is a mystery. It doesn't even have an upper or lower limit alarm. You seem to fine every possible anomoly Al. I'll loo= k further into this to see if I made some slip-up in the latest code. As mos= t every programmer knows, everything can affect anything, but this one still surprises me. You might try reseting it to zero and see if it still blinks= . Tracy (way behind on most everything) On 9/17/07, Al Gietzen wrote: > > I was in the middle of auto-tuning the mixture in flight via the EM2 > auto-tune feature; when suddenly at a particular table entry the mixture > just kept going leaner and leaner, until the engine was losing significan= t > power. About the time I hit the mode switch to disable, I noted that the > mixture bar showed full rich =96 topped out. Clearly the O2 sensor was n= ot > functioning. I manually "repaired" that table entry, and continued on an > enjoyable flight. > > > > I later found that the copper wire from the sensor was broken at crimp > splice I used to connect the O2 sensor lead to my wiring. (I basically do= n't > like crimp splices, but in a moment of impatience . . )There is only abou= t > an 8" span that is unsupported, but when I recently changed the sensor, I > had not put any heat shrink strain relief on that connector. The vibrati= on > broke it in about 10 hours of operation. Previously I had soldered it an= d > covered it with heat shrink and it was fine for 50 hours. So I was remin= ded > that some strain relief should not be overlooked, tie down that short spa= n, > and that an open circuit will give you a max rich reading. > > > > I just got the latest updates in the EM2. A couple things that didn't > work before, work now. But I find that the "fuel used" readout is always > blinking. Is this normal? It also seems that the calibration on some of > the channels has changed =96 even though I re-input all the same calibrat= ion > data I had used previously, I'm seeing some different values that I would= n't > have expected to change. Maybe this is a 'Tracy' question; if he comes > out of hidingJ. > > > > Al > > > > > ------=_Part_8164_20951922.1190819722993 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Depends on which channels you saw the change on.  The calibration= on some functions has changed over the various versions (but most have rem= ained the same). 
 
The blinking fuel used readout is a mystery.  It doesn't even= have an upper or lower limit alarm. You seem to fine every possible anomol= y Al.  I'll look further into this to see if I made some slip-up i= n the latest code.  As most every programmer knows, everything can aff= ect anything, but this one still surprises me.  You might try reseting= it to zero and see if it still blinks.
 
Tracy  (way behind on most everything)

 
On 9/17/07, = Al Gietzen <ALVentures@cox.net= > wrote:

I was in the middle of auto-tuning the mixture in flight vi= a the EM2 auto-tune feature; when suddenly at a particular table entry the = mixture just kept going leaner and leaner, until the engine was losing sign= ificant power.  About the time I hit the mode switch to disable, I not= ed that the mixture bar showed full rich =96 topped out.  Clearly the = O2 sensor was not functioning. I manually "repaired" that table entry, and = continued on an enjoyable flight.

 

I later found that the copper wire from the sensor was brok= en at crimp splice I used to connect the O2 sensor lead to my wiring. (I ba= sically don't like crimp splices, but in a moment of impatience . . )There = is only about an 8" span that is unsupported, but when I recently changed t= he sensor, I had not put any heat shrink strain relief on that connector.&n= bsp; The vibration broke it in about 10 hours of operation.  Previousl= y I had soldered it and covered it with heat shrink and it was fine for 50 = hours.  So I was reminded that some strain relief should not be overlo= oked, tie down that short span, and that an open circuit will give you a ma= x rich reading.

 

I just got the latest updates in the EM2.  A couple th= ings that didn't work before, work now.  But I find that the "fuel use= d" readout is always blinking.  Is this normal?  It also seems th= at the calibration on some of the channels has changed =96 even though I re= -input all the=20 same calibration data= I had used previously, I'm seeing some different values that I wouldn't ha= ve expected to change.  Maybe this is a ' Tracy' question; if= he comes out of hiding J.

 

Al

 

 


------=_Part_8164_20951922.1190819722993--