Message

Return-Path: <13brv3@bellsouth.net> Received: from imf21aec.mail.bellsouth.net ([205.152.59.69] verified) by logan.com (CommuniGate Pro SMTP 4.2b6) with ESMTP id 220782 for flyrotary@lancaironline.net; Mon, 21 Jun 2004 12:02:15 -0400 Received: from rad ([65.6.194.9]) by imf21aec.mail.bellsouth.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040621160145.EMPL5506.imf21aec.mail.bellsouth.net@rad> for ; Mon, 21 Jun 2004 12:01:45 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: smaller injectors, same idle Date: Mon, 21 Jun 2004 11:01:46 -0500 Message-ID: <021d01c457a9$0e1986e0$6001a8c0@rad> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_021E_01C4577F.25437EE0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: This is a multi-part message in MIME format. ------=_NextPart_000_021E_01C4577F.25437EE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable No, only A (primary) controller communicates with the EM2. The thought = was that A would be copied to B when everything was tuned correctly. I = have had a couple of reports that made me think the A to B copy function was = not working right on some units. I need to look into this and see if there = is a potential problem.=20 =20 =20 Thanks for the confirmation Tracy. I'm one of the people who reported = that the A to B copy didn't seem to work. I know there was some thought that older controllers might not have the link to allow the copy, but I = thought we determined that mine should have it. It sure would be nice if that function would work for me, and it would be nice to also have a copy B = to A option. That would really help with testing new configurations, like different size injectors and such. Whether the test results are good or not, you would have the option to copy either the new data, or the old = data to the other controller. =20 =20 Cheers, Rusty (Spaceshipone made it, but with no official altitude yet, CNN = really botched the coverage too) ------=_NextPart_000_021E_01C4577F.25437EE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

No, only A (primary) = controller=20 communicates with the EM2. The thought was that A would be = copied to=20 B when everything was tuned correctly. I have had a couple = of=20 reports that made me think the A to B copy function was not working = right on=20 some units. I need to look into this and see if there is a = potential=20 problem.

=

<= /SPAN>

Thanks for the confirmation = Tracy. =20 I'm one of the people who reported that the A to B copy didn't seem to=20 work. I know there was some thought that older controllers = might not=20 have the link to allow the copy, but I thought we determined that mine = should=20 have it. It sure would be nice if that function would work for me, = and it=20 would be nice to also have a copy B to A option. That would really = help=20 with testing new configurations, like different size injectors and = such. =20 Whether the test results are good or not, you would have the option to = copy=20 either the new data, or the old data to the other controller. =20

=

Cheers,=

Rusty (Spaceshipone made it, = but with no=20 official altitude yet, CNN really botched the coverage=20 too)

------=_NextPart_000_021E_01C4577F.25437EE0--