Difference between revisions of "Interfacing FlightGear"
(→Wiki articles: + Logging properties) |
(Moving up Property Tree Servers to a link under a new section "HTTP") |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 37: | Line 37: | ||
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. | ||
| + | |||
| + | == HTTP == | ||
| + | {{main article|Property Tree Servers}} | ||
| + | |||
| + | FlightGear have an built in web server which allow you to view and interact with the property tree through a web browser or through HTTP requests. | ||
== Scripted AI == | == Scripted AI == | ||
| Line 50: | Line 55: | ||
* [[Head tracking]] | * [[Head tracking]] | ||
* [[Logging properties]] | * [[Logging properties]] | ||
| + | * [[MATLAB]] | ||
* [[Professional and educational FlightGear users]] | * [[Professional and educational FlightGear users]] | ||
* [[Property tree]] | * [[Property tree]] | ||
| + | * [[Howto:Record, analyze and replay multiplayer flights with network tools]] | ||
* [[Howto:Use Arduino with FlightGear]] | * [[Howto:Use Arduino with FlightGear]] | ||
| Line 57: | Line 64: | ||
* {{readme file|IO}} | * {{readme file|IO}} | ||
| + | [[Category:Interfacing protocols| ]] | ||
[[Category:FlightGear]] | [[Category:FlightGear]] | ||
Latest revision as of 06:59, 8 September 2020
| 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
|
|
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
|
|
This uses a native protocol primarily when communicating with an external FDM.
Telnet
|
|
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.
HTTP
|
|
FlightGear have an built in web server which allow you to view and interact with the property tree through a web browser or through HTTP requests.
Scripted AI
Multiplayer
Flight recorder tapes
Related content
Wiki articles
- Howto:Build your own procedure trainer
- FlightGear I/O Considerations
- Head tracking
- Logging properties
- MATLAB
- Professional and educational FlightGear users
- Property tree
- Howto:Record, analyze and replay multiplayer flights with network tools
- Howto:Use Arduino with FlightGear