- 1 Property Server
- 2 Property Tree
- 2.1 accelerations/
- 2.2 ai/
- 2.3 autopilot/
- 2.4 command/
- 2.5 consumables/
- 2.6 controls/
- 2.7 devices/
- 2.8 engines/
- 2.9 environment/
- 2.10 fdm/
- 2.11 gear/
- 2.12 input/
- 2.13 instrumentation/
- 2.14 logging/
- 2.15 models/
- 2.16 nasal/
- 2.17 orientation/
- 2.18 position/
- 2.19 sim/
- 2.20 surface-positions/
- 2.21 systems/
- 2.22 velocities/
For instance, start FlightGear with the following option:
You can pick any port number, but 5400 will probably work just fine.
Now on the same machine, fire up a web browser and open up the following url:
Now you can browse the entire FG property tree "live" and even change values if you like. You can configure autopilot modes and even set control inputs so you can literally fly the airplane from your web browser, although it's not the most convenient interface for doing that. ;-)
There is a similar interface minus the html wrappings that you can enable with the following option:
Note that you can setup as many of these as you want ... for instance, just to be obscene you could do:
--httpd=5400 --httpd=5401 --httpd=5402 --props=5403 --props=5404 --props=5405
Now you have 6 different network interfaces running that you can access from anywhere. We can't find a wiki named Note.
If you have a 'props' inteface configured you can now "telnet localhost 5401" and interact with the property system (again live) and set and examine values using a 'command line' style interface.
The cool thing is that you can easily write scripts to access this --props=<port#> interface.
Take a look at:
Note that there is no requirement that you do this with perl. You could just as easily interact with FlightGear this way using perl, C, C++, java, probably even <ack> visual basic or anything else that can do tcpip network communication ... matlab? netcat?
Also note that the downside to this interface is that you can't blast a lot of data across it. It's fine if you want to monitor location and speed every second or 1/4 second and occasionally set some values (such as dump in a new weather configuration, reset the aircraft location, or read a set of values, etc.)
But if you need to track 100 different variables at 60hz, this isn't the interface for you.
A detailed list of all nodes within the property tree and their purpose, as well as possible values
The set of properties in orientation/ detail the orientation of the aircraft (pitch, yaw and roll).
The set of properties in position/ track the lat/lon location of the user's aircraft, as well as altitude and ground elevation immediately below the aircraft.
- longitude-deg -- Current longitude of the aircraft in degrees.
- latitude-deg -- Current latitude of the aircraft in degrees.
- altitude-ft -- Current altitude of the aircraft above mean sea level.
- ground-elev-m -- elevation of the ground below the aircraft, in meters. Note that for this property, ground structures are considered part of the ground. Thus, flying over any ground structure (a building, a sign, a radio tower, whatever) will raise the value of this property for as long as the aircraft is over the structure.
- altitude-agl-ft -- Current altitude of the aircraft above ground/ground structures below.
- aero --
- aircraft --
- aircraft-dir --
- aircraft-min-status --
- alarms --
- allow-toggle-cockpit --
- author --
- auto-coordination -- boolean (true/false) flag indicating whether auto-coordination is on or off.
- chase-distance-m --
- control-mode --
- description --
- flight-model --
- frame-rate --
- model-hz --
- speed-up --
- status --
- view-mode --
- number-views = '6' (int)
- sceneryloaded = 'true' (bool)
- virtual-cockpit = 'false' (bool)