Le vendredi 24 juin 2005 à 18:13 -0500, Jon Berndt a écrit :
> > Thanks, 

> > Both FDM ->YASim ->JSBSim with a different "philosophic" approach should
> > give the same end results.
> > > 
> > -- 
> > Gerard
> 
> See the FGPiston.h file in JSBSim. See the constructor in FGPiston.cpp for 
> exact specification in the new XML format (documentation pending). Here is 
> some data on what can be specified:
> 
>     Models Dave Luff's Turbo/Supercharged Piston engine model.
>     Additional elements are required for a supercharged engine.  These can be
>     left off a non-supercharged engine, ie. the changes are all backward
>     compatible at present.
> 
>     -..................................
>       power below the rated altitude.  When TAKEOFFBOOST is specified in the
>       config file (and is above RATEDBOOST1), then the throttle position is
>       interpreted as:
> 
>     - 0 to 0.95 : idle manifold pressure to rated boost (where attainable)
>     - 0.96, 0.97, 0.98 : rated boost (where attainable).
>     - 0.99, 1.0 : takeoff boost (where attainable).
> 
>     A typical takeoff boost for an earlyish Merlin was about 12psi, compared
>     with a rated boost of 9psi.
> 
>     It is quite possible that other boost control settings could have been 
> used
>     on some aircraft, or that takeoff/extra boost could have activated by 
> other
>     means than pushing the throttle full forward through a gate, but this will
>     suffice for now.
> 
>     Note that MAXMP is still the non-boosted max manifold pressure even for
>     boosted engines - effectively this is simply a measure of the pressure 
> drop
>     through the fully open throttle.
> 
> 
Thank
, that  is exactly, what i was looking for (i did not understood how it
could do with FG)
I must go further into it, and see how to build the property
relationship within the existing FG properties.
-- 
Gerard


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

Reply via email to