Return-Path: Received: from fed1rmmtao06.cox.net ([68.230.241.33] verified) by logan.com (CommuniGate Pro SMTP 4.2) with ESMTP id 382944 for flyrotary@lancaironline.net; Sat, 28 Aug 2004 21:27:08 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.33; envelope-from=ALVentures@cox.net Received: from BigAl ([68.107.116.221]) by fed1rmmtao06.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040829012637.FFAX22016.fed1rmmtao06.cox.net@BigAl> for ; Sat, 28 Aug 2004 21:26:37 -0400 From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Engine run Date: Sat, 28 Aug 2004 18:26:50 -0700 Message-ID: <000601c48d67$4270e7a0$6400a8c0@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C48D2C.96120FA0" 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.2180 In-Reply-To: This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C48D2C.96120FA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Al, I don't understand your reluctance to switch to controller B just to check. I am not suggesting changing any thing if you had it set up on = the dyno, but it would elminate the possiblity that the problem is with controller A. Switching to controller B will not distrube your MAP settings that you have with controller A. They both have their = individual MAPs. =20 ED =20 Ed; =20 Not really reluctant - just hadn't gotten too that yet, and felt I was closer to where I wanted to be on controller A. Todays smooth run = suggests it is close. I'll probably adjust as necessary through the load curve = on A, and then transfer settings to B. Seems I recall there is a way to do = that, maybe with the EM2. =20 Al ------=_NextPart_000_0007_01C48D2C.96120FA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message


Al, I don't understand your = reluctance to switch to controller B just to check.  I am not suggesting = changing any thing if you had it set up on the dyno, but it would elminate the = possiblity that the problem is with  controller A.  Switching = to controller B  will not distrube your MAP settings that you have with = controller A.  They both have their individual = MAPs.

  
ED

 

Ed;

 

Not really reluctant – just = hadn’t gotten too that yet, and felt I was closer to where I wanted to be on controller A.  Todays smooth run suggests it is close.  = I’ll probably adjust as necessary through the load curve on A, and then = transfer settings to B.  Seems I recall there is a way to do that, maybe = with the EM2.

 

Al

------=_NextPart_000_0007_01C48D2C.96120FA0--