Telnet usage: Difference between revisions

Telnet usage (view source)

573 bytes added , 26 March 2013

no edit summary

20,741

edits

@@ Line 2: / Line 2: @@
 FG has a low bandwidth "command" (aka telnet) interface where you can interactively (or automatically via an external program) examine and modify just about any internal variable in the sim. This gives you a great capability to do external scripting, external operater gui's, etc. For instance, if you have your own GUI for operating the sim and want to use it to set weather conditions, you can leverage the FG telnet interface to have your own program remotely configure the environmental settings in all your FG based visual channels.
+For past projects, I've used the --props= option to accept property configuration changes (things like weather effects and time of day.)  You can use this interface to read/write individual properties.  I setup a separate gui that was configured to know the ip addresses of all the slaves so it could update them appropriately when I wanted to make a change.  For the time of day, this presupposes that all the computer clocks are pretty closely in sync ... then you can send the same time offset to them (in seconds) so they all can display the same time of day effects.
 FlightGear can be configured to act like a telnet or even an http "server". It can watch a port for incoming connections and respond appropriately, these built-in daemons support multiple connections.