> > However, the airspeed indication will be inconsistent and > > a full instrument scan will immediately identify the problem. > > When will you connect the ASI between the pitot and static ? > > I think I need a fresh day for that one -- it's a little complicated. > The TC will be easier as soon as I have a chance to look at Curt's new > electrical code.
Ignore the reference to the scan; it ain't relevant for the subsystem. The ASI is just a differential pressure sensor indicating the difference between the pitot line and the static line. We need a lookup table to generate IAS numbers from pressure to keep panel XML design simple. > It's going to be fun writing a randomized failure manager when > everything's ready. I can think of quite a bit, including things that > should be caught in the preflight but sometimes are not (like reversed > ailerons). Remember my suggestion for multiplayer, where each participant has a single failure at all times chosen from the list of survivable failures. The other players of the multi session get to choose which failure it is, and also change their choice at any time without notice. Grin. I think that would be much more fun than a boring random selection. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
