From: Paul Surgeon <[EMAIL PROTECTED]>
> > I'm an ASEL pilot (without glider training) but I was of the impression
> > that the variometer was a slightly modified pitot tube connected to a VSI.
> 
> That sounds about right.
> As far as I know one can hook up most variometers to any TE probe.

The easy non-software thing to do is to hook up a second VSI simulation
to the pitot simulation instead of the static simulation.  Then, take
the VSI instrument and change the artwork to look like a vario and add
a second rotation layer.  The first rotation layer watches the normal
VSI simulation, the second rotation layer watches the new pitot VSI
except that it is cumulative to the first and in the other direction.

> What also differs between some designs which use a TE probe is the inclusion 
> or exclusion of a flask that is used to average the reading out.

In the C++, I'd simply copy the altimeter code (which has both data sources)
and the VSI code (which has the low pass filter and the like) and merge them
into a new function.  Other than that, there isn't much coding needed.

> > Are you trying to simulate the aircraft instrument or are you trying to
> > provide the same value as an expensive air data computer would yield ?
> 
> I'm trying to simulate an aircraft instrument.

Do you have all the information you need, or should I ask for help ?

From: Dave Culp <[EMAIL PROTECTED]>
> >From what I've seen from googling this stuff it looks like the TE vario is 
> midway between a standard vario and a netto vario in capability.

http://www.borgeltinstruments.com/Gusts.html
> In flight the pressure at the TE Probe is the sum of the static pressure
> and the suction produced due to airspeed. At constant airspeed the TE
> probe acts like a static source and the variometer indicates the
> rate of change of static pressure converted to equivalent rate of
> climb or sink.



_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to