X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao102.cox.net ([68.230.241.44] verified) by logan.com (CommuniGate Pro SMTP 5.1.12) with ESMTP id 2336603 for flyrotary@lancaironline.net; Mon, 17 Sep 2007 20:56:07 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.44; envelope-from=alventures@cox.net Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao102.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20070918005530.HMJ6851.fed1rmmtao102.cox.net@fed1rmimpo02.cox.net> for ; Mon, 17 Sep 2007 20:55:30 -0400 Received: from BigAl ([72.192.143.193]) by fed1rmimpo02.cox.net with bizsmtp id pcvV1X00N4AaN600000000; Mon, 17 Sep 2007 20:55:29 -0400 From: "Al Gietzen" To: "Rotary motors in aircraft" Subject: EM2 tuning Date: Mon, 17 Sep 2007 17:55:45 -0800 Message-ID: <000001c7f997$073f37f0$6401a8c0@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C7F953.F91BF7F0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C7F953.F91BF7F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 = significant power. About the time I hit the mode switch to disable, I noted that = the mixture bar showed full rich - topped out. Clearly the O2 sensor was = not functioning. I manually "repaired" that table entry, and continued on an enjoyable flight. =20 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 = 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 the sensor, = I had not put any heat shrink strain relief on that connector. The = vibration broke it in about 10 hours of operation. Previously 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 overlooked, tie down that short = span, and that an open circuit will give you a max rich reading. =20 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 - even though I re-input all the same = calibration data I had used previously, I'm seeing some different values that I = wouldn't have expected to change. Maybe this is a 'Tracy' question; if he comes = out of hiding:-). =20 Al =20 =20 ------=_NextPart_000_0001_01C7F953.F91BF7F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 = significant power.  About the time I hit the mode switch to disable, I noted = that the mixture bar showed full rich – 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 broken at crimp splice I used to connect the O2 sensor lead to my = wiring. (I basically 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 the sensor, I had not put any heat shrink strain relief on that = connector.  The vibration broke it in about 10 hours of operation.  Previously = 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 overlooked, tie = down that short span, 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 – = even though I re-input all the same = calibration data I had used previously, I’m seeing some different values that = I wouldn’t have expected to change.  Maybe this is a = ‘Tracy’ question; if he comes out of hidingJ.

 

Al

 

 

------=_NextPart_000_0001_01C7F953.F91BF7F0--