Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Interfacing FlightGear

From FlightGear wiki
Jump to: navigation, search
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

Screen shots

But we do provide png screenshots, too. Change the url from /screenshot?type=jpg to /screenshot?type=png

Video

We can do MJPEG stream, try to use /screenshot?stream=y as the screenshot url. MJPEG is ugly and a resource hog but works reasonable well for image sizes of probably 640x480. Scale down your FG window and give it a try.

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 PropertyList 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