Property Tree Servers
To view the Property Tree with a web browser, start FlightGear with the following option:
where 5400 is the port number. 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" (you'll need to refresh the browser) 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. ;-)
FlightGear comes with a internal telnet server that can be used to read end set values within the Property Tree structure. The telnet server is activated with the --telnet=port command line option, where port is the number of the listening port that will be opened.
A connection to the server can be done using a telnet client or opening a simple socket from any program. Multiple connections (more below) are possible at the same time. Too start FG and open the port 5401 as available telnet server use this command:
There's more on the Telnet usage page.
There is a similar interface minus the html wrappings that you can enable with the following option:
Once you have a 'props' interface 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. This is covered more on the Telnet page.
The cool thing is that you can easily write scripts to access this --props=<port#> interface.
Take a look at the link below (cvs) for some example perl scripts. FlightGear/source/scripts/perl/examples.
Note that there is no requirement that you do this with perl. You could just as easily interact with a running FlightGear instance using perl, C, C++, java, python, 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.
Note that you can setup as many of these as you want ... for instance, just to be obscene you could do:
fgfs --httpd=5400 --httpd=5401 --httpd=5402 --props=5403 --props=5404 --props=5405
Now there are 6 different network interfaces running that you can access from anywhere.