Property Tree/Web Server

From FlightGear wiki
Revision as of 04:29, 9 September 2009 by Ac001 (talk | contribs) (oops)
Jump to navigation Jump to search

FlightGear has a few network access protocols. These are started as a command line option.

Web Server

To view the PropertyTree with a web browser, start FlightGear with the following option:

fgfs --httpd=5480

where 5480 is the port number. You can pick any port number, but 5480 will probably work just fine.

On the same machine, fire up a web browser and open up the following url:


You can now browse the entire FG property tree "live" as the sim is running. You need to refresh the browser so see changes and you can even change values if you like. You could configure autopilot modes and even set control inputs so you can literally fly the airplane from your web browser, although it's maybe not the most convenient interface for doing that. ;-)

Telnet Server

FlightGear has a telnet server that can be used to read and set values of the PropertyTree. 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:

fgfs --telnet=5401

Using this server is covered in detail on the Telnet usage page.

Manipulate Properties

The cool thing is that you can easily write scripts to access the --telnet=<port#> interface.

//* psuedo code
conn = telnet.connect(, 5480)
gear_down = conn.get("/gear/state")
if gear_down:
  conn.set("/gear/state", "up")

Some links to source code example in various flavours:

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? twisted?

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. For that you need a PropertyTree:Socket.

Multi Servers

Note that you can setup as many of these servers 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 six network interfaces running that you can access from anywhere ;-) >> can I borrow your ipod please. why ?