RE: [Jsbsim-devel] Property list

[Tony P. <ap...@ea...>]

On Tue, 2003-01-07 at 21:21, Jon Berndt wrote:
> > This is a hacked up version of JSBSim.cpp, but it contains the code you
> > need.  See lines 211-221.
> >
> > Oh, you must link to the simgear libs sgmisc, sgxml, and probably
> > sgdebug too.   This brings in the XML reading and writing code,
> > which we don't use in JSBSim.
> 
> This seems to work, too:
> 
>  grep Untie *.cpp | cut -d\" -f2

This is not very reliable ... it will do a poor job of catching the
model specific properties, for example.  

> 
> There's got to be an easier way, perhaps to traverse the JSBSim property
> tree if a hypothetical option --properties is given?

You could write your own code to do it, but why?  David has already
provided for that in the properties code in simgear.

> 
> ==
> 
> I reworked the script/c1722.xml script to use the c172x instead of the
> c172r. This will prevent inadvertent mods during testing of the switching
> code. I noticed this in the autopilot section of the log output at
> startup:
> 
>  Loading Component "Roll A/P Aileron Command Normalizer" of type:
> PURE_GAIN
>    INPUT: roll-ap-error-summer
>    GAIN: -1.0000
>    OUTPUT: aileron_cmd
>    MIN: 0.0000
>    MAX: 0.0000
> 
> Then, further down, was this in the FCS section:
> 
>  Loading Component "Roll Trim Sum" of type: SUMMER
>    INPUTS:
>     aileron-cmd-norm
>     roll-trim-cmd-norm
>    CLIPTO: -1.0000, 1.0000
> 
> I suppose if I wanted the autopilot to control roll I would need to do one
> of two things:
> 
> 1) Add aileron_cmd as an input to the Roll Trim Sum component, or
> 2) Change the aileron-cmd-norm input in the Roll Trim Sum component to
> refer instead to aileron_cmd.
> 
> True?
-- 
Tony Peden <ap...@ea...>