The lazy thing to do is create a "port" that points in a certain direction
and has the option of being blocked.  If facing forwards, it acts like
a pitot and, if facing sideways, it acts like a static port.  The systems
layer can connect (and disconnect) the pressure sources, noting that many
aircraft can connect and disconnect various combinations of these sources.


> I've just added a static port system and a new altimeter model to
> CVS.  Now, if you set the property
> 
>   /systems/static/serviceable
> 
> to false, the altimeter will freeze.  Otherwise, it displays the
> altitude based on the difference between outside air pressure (with a
> slight lag from the static port) and the altimeter setting, without
> any direct knowledge of the actual aircraft altitude.
> 
> When I have a chance, I'll write a new VSI model, also connected to
> the static port.  I'll also add a pitot system, then will write an ASI
> connected both to it and the static system.  I need to know more about
> the ram-air effects in the pitot tube first.
> 
> The static system itself needs a little more work, including support
> for multiple static ports, sideslip errors, and alternate air (from
> inside the cabin); those won't be hard to add, but if anyone (Alex?)
> wants to take a look at src/System/static.[ch]xx and add them in
> before I have a chance, feel free.  Note that any improvements to the
> static system automatically propagate themselves to the instruments.
> 
> 
> All the best,
> 
> 
> David
> 
> -- 
> David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
> 
> _______________________________________________
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 
> 

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to