Mailing List flyrotary@lancaironline.net Message #30550
From: Bob Perkinson <bobperk@bellsouth.net>
Subject: RE: [FlyRotary] Re: Fly-By-Wire controller
Date: Mon, 6 Mar 2006 20:54:07 -0600
To: Rotary motors in aircraft <flyrotary@lancaironline.net>
DATA LOGGING, to a mass storage device i.e. USB flash Memory }:>)
 

Bob Perkinson
Hendersonville, TN.
RV9 N658RP Reserved
If nothing changes
Nothing changes
 


 
Sounds Great, Tracy.  Appears you have covered the most significant features already.
 
1.  Lets see - how about a coolant/oil temperature hold - in otherwords say for a long climb modulate the rpm/manifold to see that coolant/oil temps are not exceeded by what ever you set, but otherwise pedal to the metal for a maximum best rate of climb short of melt-down. 
 
2.  How about tying it into your airspeed sensor to maintain a constant airspeed or could set in your Vne limits {:>) or maximum descent airspeed.
 
 3.  In fact, How about setting up so you can program in the parameters for certain flight regimes such as
     might could factor in such things as density altitude or certainly OAT, perhaps even have a "Light" and "Heavy" mode adjust these factors for aircraft gross weight.
 
  a.  Take off and initial Climbout
  b.  Cruise climb
  c.  Best economy cruise
  d.  Best Speed/economy combination (optimum best of both)
  e.  Descent
  f.  Eating your inflight snack
 
'bout all the hair brain ideas I can think of at the moment.  I am sure you will get more from others.
 
4.  What happens if power to the unit fails?? What default mode does it have - simply stays where power left it? Goes wide open (not likely in an automobile application).
 
Tell us more
 
Best Regards
 
Ed
----- Original Message -----
Sent: Monday, March 06, 2006 5:03 PM
Subject: [FlyRotary] Re: Fly-By-Wire controller

The FBW RX-8 throttle body controller design is done and the inevitable 'feature creep' has begun. 
 
 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
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster