Difference between revisions of "Interfacing FlightGear"

From FlightGear wiki
Jump to navigation Jump to search
(Created page with "{{stub}} There are several different ways to '''interface FlightGear''' to either feed FlightGear with data, get data from FlightGear or both. There could be many different...")
 
m (add more interfacing mechanisms - need to search the forum for other common methods)
Line 7: Line 7:
 
* Using an external [[Flight Dynamics Model|FDM]]
 
* Using an external [[Flight Dynamics Model|FDM]]
 
* Feeding FlightGear properties when using FlightGear for visualization
 
* Feeding FlightGear properties when using FlightGear for visualization
* Interfacing FlightGear with external hardware, for example a home built autopilot control panel
+
* Feeding external traffic data using either the AI/MP systems, or a combination of both
 +
* Interfacing FlightGear with external hardware, for example a home-built autopilot control panel
  
 
== Generic protocol ==
 
== Generic protocol ==
Line 25: Line 26:
  
 
There is an interactive mode with a handful of commands that can be used for interacting with FlightGear's [[property tree]] and a data mode for connecting to FlightGear through a socket.
 
There is an interactive mode with a handful of commands that can be used for interacting with FlightGear's [[property tree]] and a data mode for connecting to FlightGear through a socket.
 +
 +
== Scripted AI ==
 +
 +
== Multiplayer ==
 +
 +
== Flight recorder tapes ==
  
 
== Related content ==
 
== Related content ==

Revision as of 07:24, 30 October 2015

This article is a stub. You can help the wiki by expanding it.

There are several different ways to interface FlightGear to either feed FlightGear with data, get data from FlightGear or both.

There could be many different reasons to interface FlightGear, for example:

  • Using an external FDM
  • Feeding FlightGear properties when using FlightGear for visualization
  • Feeding external traffic data using either the AI/MP systems, or a combination of both
  • Interfacing FlightGear with external hardware, for example a home-built autopilot control panel

Generic protocol

1rightarrow.png See Generic protocol for the main article about this subject.

Using a generic protocol you can use either an existing protocol or a protocol custom made for your need. The protocols are defined in property list XML files, and can both be used for reading from or to a file and to communicate through a serial connection.

Native protocol

1rightarrow.png See Property Tree/Sockets for the main article about this subject.

This uses a native protocol primarily when communicating with an external FDM.

Telnet

1rightarrow.png See Telnet usage for the main article about this subject.

FlightGear can be given command line arguments that will start FlightGear with a telnet server, --telnet=port.

There is an interactive mode with a handful of commands that can be used for interacting with FlightGear's property tree and a data mode for connecting to FlightGear through a socket.

Scripted AI

Multiplayer

Flight recorder tapes

Related content

Wiki articles

Readme files