fly/fgdata
1
0
Fork 0
Code Activity

sync with some READMEs that originate in main CVS

Browse source
This commit is contained in:
j4strngs 2002-10-28 20:14:53 +00:00
parent fca24c0930
commit 964f140378
3 changed files with 108 additions and 29 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
Docs/README.IO
View file

@ -88,3 +88,26 @@ Moving Map Example:
your current location. Atlas is a really nifty program with many your current location. Atlas is a really nifty program with many
neat options such as the ability to generate and use background neat options such as the ability to generate and use background
bitmaps that show the terrain, cities, lakes, oceans, rivers, etc. bitmaps that show the terrain, cities, lakes, oceans, rivers, etc.
HTTP Server Example
You can now interact with a running copy of FlightGear using your
web browser. You can view all the key internal variables and even
change the ones that are writable. If you have support in your
favorite [scripting] language for interacting with an http server,
you should be able to use this as a mechanism to interface your
script with FlightGear.
Start up fgfs with the --httpd=<port#> option:
For example:
fgfs --httpd=5500
Now point your web browser to:
http://host.domain.name:5500/
When a value is displayed, you can click on it to bring up a form
to assign it a new value.

69
Docs/README.JSBsim
View file

@ -1,42 +1,53 @@
JSBSim JSBSim
JSBSim is an ongoing attempt at producing an OO Flight Dynamics Model (FDM) JSBSim is an ongoing attempt at producing an OO Flight Dynamics Model
to replace LaRCsim as the default FDM for FlightGear. It can also be used (FDM) to replace LaRCsim as the default FDM for FlightGear. It can
standalone. also be used standalone.
JSBSim uses config files to represent aircraft and engines. Also, the flight JSBSim uses config files to represent aircraft, engines, propellers,
control system is described in the config file. Normally, for use with etc. Also, the flight control system is described in the config
FlightGear, the config files are named this way: file. Normally, for use with FlightGear, the config files are named
<FG_ROOT>/Aircraft/<aircraft name>/<aircraft name>.cfg . Engines are named this way [case is significant]:
like this: <FG_ROOT>/Engines/<engine name>.dat .
Aircraft and engine config files are present in the FGFS-Base package which <FG_ROOT>/Aircraft/<aircraft name>/<aircraft name>.xml
must be downloaded from the FlightGear web site at www.flightgear.org or one
of the mirror sites listed there. Engines are named like this:
<FG_ROOT>/Engines/<engine name>.xml
Aircraft and engine config files are present in the FGFS Base package
which must be downloaded. See the FlightGear web site for more
information.
How to run FGFS using JSBSim How to run FGFS using JSBSim
All the various FDMs are currently compiled into FGFS. You can specify which All the various FDMs are currently compiled into FGFS. You can specify
FDM you want at run time. You can also specify which aircraft you want. which FDM you want at run time. You can also specify which aircraft
Currently, for JSBSim only the X-15 is available, and possibly the C-172. you want. Currently, for JSBSim only the X-15 and C-172 aircraft are
Here is an example command line used to start up FlightGear using JSBSim as available. Here is an example command line used to start up FlightGear
the FDM: using JSBSim as the FDM:
fgfs --fdm=jsb --aircraft=X15 --units-feet --altitude=60000 --uBody=2000 --wBody=120 fgfs --fdm=jsb --aircraft=X15 --units-feet --altitude=60000 --uBody=2000 --wBody=120
[Note: uBody is the forward velocity of the aircraft, wBody is the downward or,
velocity - from the aircraft point of view. This essentially means that the
aircraft is going forward fast and has an angle of attack of about 4 degrees
or so]
The above command line sets up the initial velocity and altitude to allow fgfs --fdm=jsb --aircraft=c172
the X15 to glide down. Note that if you fire up the engine, it will burn for
only about two minutes and then run out of fuel - but you will go very, very
fast!
Check out the JSBSim home page at www.hal-pc.org/~jsb/flightsim.html. Please [Note: uBody is the forward velocity of the aircraft, wBody is the
report any bugs to jsb@hal-pc.org, or apeden@earthlink.net, or post them to downward velocity - from the aircraft point of view. This essentially
the fgfs-devel mailing list. means that the aircraft is going forward fast and has an angle of
attack of about 4 degrees or so]
JSBSim is written by Jon S. Berndt and Tony Peden with contributions by The first command line sets up the initial velocity and altitude to
other FlightGear programmers, as well. allow the X15 to glide down. Note that if you fire up the engine, it
will burn for only about two minutes and then run out of fuel - but
you will go very, very fast! The second command line example will
start up the C172 on the end of the runway.
Check out the JSBSim home page at http://jsbsim.sf.net. Please report
any bugs to jsb@hal-pc.org, or apeden@earthlink.net, or post on the
jsbsim web site using the SourceForge bug tracking system for the
project.
JSBSim is written by Jon S. Berndt and Tony Peden with contributions
by other FlightGear programmers, as well.

45
Docs/README.fgjs Normal file
View file

@ -0,0 +1,45 @@
fgjs -- a small program for creating a basic FlightGear joystick
configuration
fgjs requires plib to be installed on your system. If you've
successfully installed and built FlightGear then you should be
all set
Build instructions
At this point, fgjs has only been built and tested under Linux,
so the makefile is a simple one. cd into the directory in which
the fgjs source resides and type 'make' and, if you are lucky,
all will go well. You can e-mail me (apeden@earthlink.net) any
changes needed to make it work on other systems. It's quite
possible that this program will become part of the regular
FlightGear package so
Running
Set up your joystick and make sure it works with js_demo from the
FlightGear distribution. Upon executing fgjs, it will prompt you
to move the control you wish to use for elevator, ailerons, etc.
Note that when being prompted for an analog control, you can skip
the current one by pressing any button and vice-versa when being
prompted for a button. You may want to do this if for, as an
example, rudder if you have only one joystick or your joystick
doesn't have as many analog axes as FlightGear supports.
Once you've run with this configuration, you may wish to tune
the dead-band a bit (see fgfsrc.js) as the default, 0.02, may
be too narrow for your particular hardware/taste.
And last, but not least, this thing needs a GUI!!!! Hopefully,
the joystick handling code and interface code are separate
enough that using that a GUI version could be built using this
source as a starting point.