Jon S. Berndt writes: > > From: Andy Ross > > > In fact, this is a good example: a "real" F-16A (Dunno about the C) > > flight control computer takes its input from a set of gyros and from > > the position of the stick, and that's it > > The F-16 DFCS (beginning with Block 40) - and I suspect to some degree also > the F-16A model - also requires the inputs of a rather lot of switch > positions (commonly referred to as "notes"), e.g. pitch switch position, > absolute value of phi greater than some value, WOW, roll switch position, > standby gains enabled, control stick steering force greater than some value, > other notes, etc. These are very aircraft specific. So, as you state below, > yes the FCS needs to know some very specific aircraft information.
That's actually a counter-example: this is all information that FlightGear will have to have by default, but FDMs like JSBSim will not (necessarily) -- since FlightGear owns the panel and the UI, it is the component that tracks the position of every switch, stick, and so on. > 1) The FCS is already being modeled. We want to do it. We like > doing it. I think that's harmless enough, but we might also want to consider adding an option to use an external FCS. All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
