X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from ispmxmta09-srv.alltel.net ([166.102.165.170] verified) by logan.com (CommuniGate Pro SMTP 5.0.8) with ESMTP id 1025587 for flyrotary@lancaironline.net; Tue, 07 Mar 2006 10:51:59 -0500 Received-SPF: pass receiver=logan.com; client-ip=166.102.165.170; envelope-from=montyr2157@alltel.net Received: from Thorstwin ([162.39.148.78]) by ispmxmta09-srv.alltel.net with SMTP id <20060307155112.CMUN16513.ispmxmta09-srv.alltel.net@Thorstwin> for ; Tue, 7 Mar 2006 09:51:12 -0600 Message-ID: <001b01c641fe$fb0168b0$01fea8c0@Thorstwin> From: "M Roberts" To: Subject: flyrotary_Web_Archive Date: Tue, 7 Mar 2006 09:51:21 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C641CC.B0458E00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C641CC.B0458E00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The FBW RX-8 throttle body controller design is done and the inevitable = 'feature creep' has begun.=20 It occurred to me that since the throttle controller has access to all = the EC2 data that it could do a number of things. The two I have = adopted so far are manifold pressure hold and RPM hold. They hold the = respective parameter constant at the value it was at when the function = was engaged. Obviously the MP hold can only work up to the ambient or = turbo boost pressure available. They are disengaged by either hitting = the cancel button or sensing that the pilot is frantically trying to = regain control by moving the power lever. Any other ideas for this widget before I freeze the design? Tracy Crook How about Prop sync ;-) Monty ------=_NextPart_000_0018_01C641CC.B0458E00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The FBW RX-8 throttle body controller design is done and the=20 inevitable 'feature creep' has begun. 
 
It occurred to me that since the throttle controller has = access=20 to all the EC2 data that it could do a number of things.  The two I = have=20 adopted so far are manifold pressure hold and RPM hold.   They = hold=20 the respective parameter constant at the value it was at when the = function=20 was engaged.  Obviously the MP hold can only work up to the ambient = or=20 turbo boost pressure available.  They are disengaged by either = hitting the=20 cancel button or sensing that the pilot is frantically trying to regain = control=20 by moving the power lever.
 
Any other ideas for this widget before I freeze the design?
 
Tracy Crook
 
How about Prop sync ;-)
 
Monty
------=_NextPart_000_0018_01C641CC.B0458E00--