Jump to: navigation, search

Property Tree/Web Server

53 bytes removed, 18:14, 5 April 2015
no edit summary
{{Note|This feature received significant updates in FlightGear 3.1+: While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka webserver) to browse the property tree.It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart.  After a while, Torsten got disappointed by the functionality and the look&feel of the http property-browser, so he had a look at the code to see if it could be improved, he quickly realized, that the implementation was simple but not scalable, so he looked for something allready available on the GPL market. And he found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embedd that into FlightGear. What is ready so far and pushed to next is:* A single threaded httpd running in the main loop (should probably get its own thread soon)* Running as a replacement for the old httpd* Serving FGDATA/Docs as the document root* Serving the uri /props/ as a replacement for the old property browser (improved functionality, improved l&f, styling via css)* Serving the uri /run.cgi as a replacement for the old interface to run fg_commands* Serving the uri /json/ to return selected properties as JSON (read-only so far){{FGCquote |If your using fgrun, under Advanced (last tab)/ Network, check httpd and enter 5500. Then in a compatible browser use <code>http://localhost:5500/gui/</code> |{{cite web |url= |title=<nowiki>Re: Heaven or Hell? Phi sneak preview.</nowiki> |author=<nowiki>wlbragg</nowiki> |date=<nowiki>Sun Apr 05</nowiki> }}}}}} [[FlightGear]] has a few network access protocols. These are started as via a [[Command Line Parameters|command line option]]. And, just for fun we have an embedded web server you can activate which exposes the internal property tree via a web style interface that you can browse (and edit) with any web browser. You can literally fly the airplane remotely via your web browser. It's primarily there as an interactive remote debugging tool, but it could be used for many things. 
== Web Server ==
You can now browse the entire FG property tree "live" as the sim is running. You need to refresh the browser to see changes and you can even change values if you like. You can configure autopilot modes and even set control inputs so you could 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 Note that you can be used to read and set values setup as many of the [[PropertyTree]]. The telnet server is activated with the '''--telnet=port''' [[Command Line Parameters|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 usage|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 these as available telnet server use this command: fgfs --telnet=5401Using this server protocol 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#> interfacewant . //* psuedo code conn = telnet.connect( instance, 5480) gear_down = conn.get("/gear/state") if gear_down: conn.set("/gear/state", "up") Some links just to source code examples in various flavours:* Perl - [ /source/scripts/perl/examples].* Python - [ /source/scripts/python/]* Java - [ source/scripts/java/] You be obscene 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 TCP/IP network communication ... matlab? netcat? twisted? Also note that the downside to the telnet 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. If you need to track 100 different variables at 60hz, this isn't the interface for you.For that you need a '''[[PropertyTree:Sockets|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 * --telnetprops=5403 * --telnetprops=5404 * --telnetprops=5405
Now there are six you have 6 different network interfaces running that you can access from anywhere ;-) >> can I borrow your ipod please. why ?[Note: security issues if not used wisely.]
==== Links ====* httpd source - [http[Category:// source/src/Network/httpd.cxxProperty Tree]* telnet (props) source - [ source/src/Network/props.cxx]

Navigation menu