FlightGear wiki - User contributions [en]

Howto talk:Configure camera view windows

2015-06-17T11:49:50Z

Biketool: /* Cockpit vs exterior */ new section

= Todo / Misc =
* Document the various threading models supported by FG (see http://flightgear.org/forums/viewtopic.php?f=11&t=7182)
:: done in [[Multi_core_and_Multi_GPU_support]]
:: [[User:Flughund|Flughund]] 11:30, 17 June 2011 (EDT)

= RFEs =
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26495.html

Why exactly is this article now named "in windows"?
How is this article windows specific?
It was never meant to be: A "window" is just a rectangular area on your screen, it is not necessarily specific to MS Windows.
:This article is renamed from "...in Windows" to "...in windows" because the article is not specific to the OS called Windows. It is dealing with graphics windows. When renaming the article from Configure Camera View In Windows (which is poor usage of capitals) I did not notice it was not about the OS. Until today, no-one complained, or fixed it him/herself ;)
:Cheers, [[User:Gijs|Gijs]] 17:36, 26 January 2010 (UTC)
:PS, please please sign your talk messages.
:: The original article is to be found at http://wiki.flightgear.org/index.php/Howto:_Configure_Camera_View_Windows
:: In other words, there is no "in Windows" to be found anywhere in the original URL.
:: So, this doesn't seem to be so much about "poor usage of capitals" as it is about lack of proper reading/comprehension in the first place?
:: However, please do feel free to rename this article any way you want - on the other hand, platform specific articles are probably better provided with a corresponding tag to put them into a corresponding category instead?
::--[[User:MILSTD|MILSTD]] 18:07, 26 January 2010 (UTC)

= Example Code=
*Does the example code for the two cams given in the article work for someone? I cannot get it working with this setup.
*I am in the process of reviewing this article, is MILSTD still around? Would prefer to talk to him before I upload my changes ;-).
:[[User:Flughund|Flughund]] 11:30, 17 June 2011 (EDT)

== Cockpit vs exterior ==

Is there an easy way to send instrument panel, or a view of the scan gauges(six pack, engine, electrical, vac, fuel, and radio navigation) to the main display and exterior view to a cheap HDMI projector?
If someone would put this into sample code, or to a quick tutorial it would be great, even better if it were a menu option in flightgear.[[User:Biketool|Biketool]] ([[User talk:Biketool|talk]]) 07:49, 17 June 2015 (EDT)

User talk:Biketool

2013-12-25T11:52:26Z

Biketool: /* Your GPS Edits (12/2013) */

== Your GPS Edits (12/2013) ==
Hi & welcome! Thanks for taking the time to contribute to the FlightGear wiki. However, please note that the edits you made are not exactly documenting existing features, also the article itself is not about feature requests. Obviously, it's great if you are working on these features already - if so, please state so. But if these are just feature requests without any intention to work on them, I suggest to check out the [http://flightgear-bugs.googlecode.com/ issue tracker] to file your feature requests there. Your ideas do sound useful, and I agree that these would be great additions to FlightGear. The GPS code is currently being actively developed and maintained - however, please keep in mind that things like bluetooth access are highly OS-specific, and thus not easily supported by cross-platform software like FlightGear. In fact, for the same reasons, FlightGear still is lacking [[USB HID Support]] too. Regarding the use-cases you mentioned, this can already be accomplished by using FlightGear's extensive I/O facilities and using it as a GPS sensor in other software (obviously, minus the bluetooth connectivity). Feel free to get in touch via the forums to discuss your ideas. HTH --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 09:43, 25 December 2013 (UTC)

: Thanks, I am using the Linux FLightgear and hope to build a quick and dirty module that will probably only work for Linux, so as I make my notes I thought I would drop it into the wiki. Perhaps [[GPS internals]] is a better location. I am currently working on creating the dummy 'device' I think GPS data follows the same NEMA protocol(rs-232 serial) as a cable but sent over bluetooth.[[User:Biketool|Biketool]] ([[User talk:Biketool|talk]]) 10:18, 25 December 2013 (UTC)

:: I would suggest to check out the [[USB HID Support]] discussion in the issue tracker. It may be a good idea to use a wrapper library like [http://www.signal11.us/oss/hidapi/ hidapi] here (also has BT support) to get started more quickly and to come up with a multi-platform implementation right from the beginning. For quick prototyping, you could use [[Nasal]]'s [[Nasal/CppBind|CppBind]] framework, which makes it straightforward to add scripting bindings to FlightGear (should only take 20 minutes to expose the most essential APIs for quick testing). However, ideally USB/HID (and Bluetooth) support would be added at the I/O layer in FG/SG, i.e. somewhere around [http://docs.freeflightsim.org/flightgear/classFGProtocol.html FGProtocol] or even better [http://docs.freeflightsim.org/simgear/classSGIOChannel.html SGIOChannel]. As can be seen in {{Issue|619}}, there's also the idea of mapping the API into the property tree using [http://docs.freeflightsim.org/simgear/classSGPropertyChangeListener.html SGPropertyChangeListener]. For detailed information on adding new subsystems or listener-based subsystems, check out [[Howto:Create new subsystems]]. Ultimately, it's obviously up to you - but these are the most relevant pointers. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:01, 25 December 2013 (UTC)

:::Thanks, better to start out doing it right and not have to rewrite. I need to find some information to create the simulated bluetooth device first.[[User:Biketool|Biketool]] ([[User talk:Biketool|talk]]) 11:52, 25 December 2013 (UTC)

User talk:Biketool

2013-12-25T10:18:10Z

Biketool: /* Your GPS Edits (12/2013) */ response to Hooray

User talk:Biketool

2013-12-25T09:53:20Z

Biketool: /* Your GPS Edits (12/2013) */ thanks, hoping to build a linux module for now

Global Positioning System

2013-12-25T09:29:55Z

Biketool: /* ADS-B */ small language tweaks

This pages discussed the generic GPS support in FlightGear, not any specific real-world device or operating procedure. Nevertheless, many similarities should exist. It is assumed the reader is familiar with radio navigation terminology and basic instrument flying procedures.

For background information on GPS usage itself, you may want to check out http://wiki.flightgear.org/index.php/Avionics_Development_Resources#GPS

'''Note''': the GPS is a work in progress, and under active development. If you encounter problems, please report them - and also suggest features. The [[GPS internals]] page mentions likely future enhancements and current limitations of code. Also note that panel instruments may extend or restrict access to the features below, depending on the specific device

== Basic Information ==

The GPS computes position, direction and velocity information independently of other instruments in FlightGear - for example the computed altitude is not related to any altimeter installed on the aircraft. GPS computed values are subject to different errors and precision as compared with other instruments. (In FG, the GPS is too accurate, and in the future some optional modelling of GPS reception will be added)

Useful information above includes true groundspeed (not airpseed) and ground track (different from heading), i.e the path the aircraft is taking over the ground, and the direction of movement.

== Active Waypoint ==

The GPS tracks an active waypoint, which can be an airport, VOR, NDB, fix or user-defined in various ways. Information about the active waypoint is provided - bearing, range, time to reach the waypoint, and so on.

== Modes ==

=== OBS ===
OBS mode makes the GPS behave like a nav-radio tuned to the active waypoint (which doesn't have to be a VOR). You select a desired radial, and the GPS will generate to/from-flags and a course deviation output, exactly like a VOR receiver. Since there's no radio reception involved, this works for NDBs or fixes too, and there is no issue with stations being out of range (or out of service).

The OBS radial can be adjusted via a dial at the bottom of the default GPS dialog - note the dial is only shown when in OBS mode, and hidden in DTO and LEG modes, to avoid confusion. Due to PLIB limitations, also note that the 0-degree radial is at the bottom, and the 180-degree radial is at the top - i.e the dial is upside down.

=== LEG ===
LEG mode is mostly used with an active route (defined in the route manager). In LEG mode, the active waypoint is the next waypoint on the current route, and the GPS calculates course deviation to fly the line between the previous waypoint and the active waypoint.

Upon reaching the active waypoint, the GPS automatically switches ('sequences') to the next waypoint, if one exists.

=== DTO ===
This mode is used to fly directly to a waypoint. When DTO mode is entered, the course deviation will be centred, and a bearing calculated to fly directly to the requested, active waypoint.

Upon reaching the waypoint, the GPS will continue flying the inbound bearing, *unless* the active waypoint is part of an active route. In this case, the GPS will automatically switch to LEG mode, and resume waypoint sequencing.

== Finding Waypoints ==

Waypoints can be selected in the following ways:

- searching by ident or name. Enter the full, or first few letters of a waypoint name, and search. The closest matching waypoint will be displayed, with successive results available, sorted by distance to the current GPS position.

- selecting the nearest waypoint (of a particular type). The closest ten waypoints can be loaded, and searched through

- loading waypoints from the active route (flight-plan)

== Turn Anticipation ==

... doesn't work yet ... but coming soon

== Reference Navaid ==

The GPS code automatically selects a reference navid, if one can be found nearby, and provides its location, range, bearing and frequency. This feature allows the pilot to cross-check the GPS indicated position against the reference navid.

== Common Procedures ==

=== Executing a ATC direct clearance ===

Commonly, ATC will clear an inbound or outbound aircraft to a waypoint in their area. Particularly for departures, various waypoints on a procedure (SID) may be skipped. In this case, simply load the active WPT, search forwards to the cleared waypoint, and press 'DTO'. The GPS will fly directly to the waypoint, and skip over any waypoints as necessary before resuming LEG mode.

=== Missed Approaches ===

The current GPS code lacks approach support, but it's still valuable to set the missed approach point as the active waypoint. Upon going missed, execute a direct-to, and you'll have one less thing to worry about when going missed.

== Future Functionality ==

===GPS===
It is possible for a the computer running Flightgear to create a dummy or simulated GPS module which will appear over Bluetooth as an external generic GPS device available to pair, simulating an actual external GPS receiver often used in the cockpit along with a tablet. Simulated GPS location information generated by Flightgear can be sent wirelessly over this simulated GPS device to a tablet, computer, or any other device allowing pilots and simulator users to seamlessly use the same hardware and GPS location aware software to navigate in both real world and in simulated flights without requiring any compatibility modifications on the tablet side. Most mobile devices have the option to use an alternative external bluetooth connected GPS device even if they also have an internal GPS/GLONASS receiver. This functionality is not yet supported in Flightgear.

===ADS-B===
Like GPS a simulated ADS-B bluetooth device which transmits either Flightgear simulated or possibly streamed in real world ADS-B information can be created by the computer running Flightgear to appear over bluetooth as an available device for a tablet or other device to pair with. This module will display Flightgear simulated status information to tablets that have the required software such as ForeFlight to use real world ADS-B wireless dongles without requiring any compatibility modifications to the hardware or software of the tablet. Information from ADS-B includes ADS-B weather, animated NEXRAD radar, METARs, TAFs, NOTAMs, TFRs and more. https://en.wikipedia.org/wiki/ADS-B This functionality is not yet supported in Flightgear.

[[Category:Aircraft instruments]]

Global Positioning System

2013-12-25T09:27:20Z

Biketool: /* GPS */ Most mobile devices have the option to use an alternative external bluetooth GPS device even if they also have an internal GPS/GLONASS receiver.

This pages discussed the generic GPS support in FlightGear, not any specific real-world device or operating procedure. Nevertheless, many similarities should exist. It is assumed the reader is familiar with radio navigation terminology and basic instrument flying procedures.

For background information on GPS usage itself, you may want to check out http://wiki.flightgear.org/index.php/Avionics_Development_Resources#GPS

'''Note''': the GPS is a work in progress, and under active development. If you encounter problems, please report them - and also suggest features. The [[GPS internals]] page mentions likely future enhancements and current limitations of code. Also note that panel instruments may extend or restrict access to the features below, depending on the specific device

== Basic Information ==

The GPS computes position, direction and velocity information independently of other instruments in FlightGear - for example the computed altitude is not related to any altimeter installed on the aircraft. GPS computed values are subject to different errors and precision as compared with other instruments. (In FG, the GPS is too accurate, and in the future some optional modelling of GPS reception will be added)

Useful information above includes true groundspeed (not airpseed) and ground track (different from heading), i.e the path the aircraft is taking over the ground, and the direction of movement.

== Active Waypoint ==

The GPS tracks an active waypoint, which can be an airport, VOR, NDB, fix or user-defined in various ways. Information about the active waypoint is provided - bearing, range, time to reach the waypoint, and so on.

== Modes ==

=== OBS ===
OBS mode makes the GPS behave like a nav-radio tuned to the active waypoint (which doesn't have to be a VOR). You select a desired radial, and the GPS will generate to/from-flags and a course deviation output, exactly like a VOR receiver. Since there's no radio reception involved, this works for NDBs or fixes too, and there is no issue with stations being out of range (or out of service).

The OBS radial can be adjusted via a dial at the bottom of the default GPS dialog - note the dial is only shown when in OBS mode, and hidden in DTO and LEG modes, to avoid confusion. Due to PLIB limitations, also note that the 0-degree radial is at the bottom, and the 180-degree radial is at the top - i.e the dial is upside down.

=== LEG ===
LEG mode is mostly used with an active route (defined in the route manager). In LEG mode, the active waypoint is the next waypoint on the current route, and the GPS calculates course deviation to fly the line between the previous waypoint and the active waypoint.

Upon reaching the active waypoint, the GPS automatically switches ('sequences') to the next waypoint, if one exists.

=== DTO ===
This mode is used to fly directly to a waypoint. When DTO mode is entered, the course deviation will be centred, and a bearing calculated to fly directly to the requested, active waypoint.

Upon reaching the waypoint, the GPS will continue flying the inbound bearing, *unless* the active waypoint is part of an active route. In this case, the GPS will automatically switch to LEG mode, and resume waypoint sequencing.

== Finding Waypoints ==

Waypoints can be selected in the following ways:

- searching by ident or name. Enter the full, or first few letters of a waypoint name, and search. The closest matching waypoint will be displayed, with successive results available, sorted by distance to the current GPS position.

- selecting the nearest waypoint (of a particular type). The closest ten waypoints can be loaded, and searched through

- loading waypoints from the active route (flight-plan)

== Turn Anticipation ==

... doesn't work yet ... but coming soon

== Reference Navaid ==

The GPS code automatically selects a reference navid, if one can be found nearby, and provides its location, range, bearing and frequency. This feature allows the pilot to cross-check the GPS indicated position against the reference navid.

== Common Procedures ==

=== Executing a ATC direct clearance ===

Commonly, ATC will clear an inbound or outbound aircraft to a waypoint in their area. Particularly for departures, various waypoints on a procedure (SID) may be skipped. In this case, simply load the active WPT, search forwards to the cleared waypoint, and press 'DTO'. The GPS will fly directly to the waypoint, and skip over any waypoints as necessary before resuming LEG mode.

=== Missed Approaches ===

The current GPS code lacks approach support, but it's still valuable to set the missed approach point as the active waypoint. Upon going missed, execute a direct-to, and you'll have one less thing to worry about when going missed.

== Future Functionality ==

===GPS===
It is possible for a the computer running Flightgear to create a dummy or simulated GPS module which will appear over Bluetooth as an external generic GPS device available to pair, simulating an actual external GPS receiver often used in the cockpit along with a tablet. Simulated GPS location information generated by Flightgear can be sent wirelessly over this simulated GPS device to a tablet, computer, or any other device allowing pilots and simulator users to seamlessly use the same hardware and GPS location aware software to navigate in both real world and in simulated flights without requiring any compatibility modifications on the tablet side. Most mobile devices have the option to use an alternative external bluetooth connected GPS device even if they also have an internal GPS/GLONASS receiver. This functionality is not yet supported in Flightgear.

===ADS-B===
Like GPS a dummy ADS-B bluetooth device which transmits either Flightgear simulated or possibly real world ADS-B traffic can be created by the computer running Flightgear to appear over bluetooth as an available device for a tablet or other device to pair with. This module will display Flightgear simulated status information to tablets that have the required software such as ForeFlight to use real world ADS-B wireless dongles without requiring any compatibility modifications to the hardware or software of the tablet. Information from ADS-B includes ADS-B weather, animated NEXRAD radar, METARs, TAFs, NOTAMs, TFRs and more. https://en.wikipedia.org/wiki/ADS-B This functionality is not yet supported in Flightgear.

[[Category:Aircraft instruments]]

Global Positioning System

2013-12-25T09:12:09Z

Biketool: /* ADS-B */ spelling, add foreflight as example

This pages discussed the generic GPS support in FlightGear, not any specific real-world device or operating procedure. Nevertheless, many similarities should exist. It is assumed the reader is familiar with radio navigation terminology and basic instrument flying procedures.

For background information on GPS usage itself, you may want to check out http://wiki.flightgear.org/index.php/Avionics_Development_Resources#GPS

'''Note''': the GPS is a work in progress, and under active development. If you encounter problems, please report them - and also suggest features. The [[GPS internals]] page mentions likely future enhancements and current limitations of code. Also note that panel instruments may extend or restrict access to the features below, depending on the specific device

== Basic Information ==

The GPS computes position, direction and velocity information independently of other instruments in FlightGear - for example the computed altitude is not related to any altimeter installed on the aircraft. GPS computed values are subject to different errors and precision as compared with other instruments. (In FG, the GPS is too accurate, and in the future some optional modelling of GPS reception will be added)

Useful information above includes true groundspeed (not airpseed) and ground track (different from heading), i.e the path the aircraft is taking over the ground, and the direction of movement.

== Active Waypoint ==

The GPS tracks an active waypoint, which can be an airport, VOR, NDB, fix or user-defined in various ways. Information about the active waypoint is provided - bearing, range, time to reach the waypoint, and so on.

== Modes ==

=== OBS ===
OBS mode makes the GPS behave like a nav-radio tuned to the active waypoint (which doesn't have to be a VOR). You select a desired radial, and the GPS will generate to/from-flags and a course deviation output, exactly like a VOR receiver. Since there's no radio reception involved, this works for NDBs or fixes too, and there is no issue with stations being out of range (or out of service).

The OBS radial can be adjusted via a dial at the bottom of the default GPS dialog - note the dial is only shown when in OBS mode, and hidden in DTO and LEG modes, to avoid confusion. Due to PLIB limitations, also note that the 0-degree radial is at the bottom, and the 180-degree radial is at the top - i.e the dial is upside down.

=== LEG ===
LEG mode is mostly used with an active route (defined in the route manager). In LEG mode, the active waypoint is the next waypoint on the current route, and the GPS calculates course deviation to fly the line between the previous waypoint and the active waypoint.

Upon reaching the active waypoint, the GPS automatically switches ('sequences') to the next waypoint, if one exists.

=== DTO ===
This mode is used to fly directly to a waypoint. When DTO mode is entered, the course deviation will be centred, and a bearing calculated to fly directly to the requested, active waypoint.

Upon reaching the waypoint, the GPS will continue flying the inbound bearing, *unless* the active waypoint is part of an active route. In this case, the GPS will automatically switch to LEG mode, and resume waypoint sequencing.

== Finding Waypoints ==

Waypoints can be selected in the following ways:

- searching by ident or name. Enter the full, or first few letters of a waypoint name, and search. The closest matching waypoint will be displayed, with successive results available, sorted by distance to the current GPS position.

- selecting the nearest waypoint (of a particular type). The closest ten waypoints can be loaded, and searched through

- loading waypoints from the active route (flight-plan)

== Turn Anticipation ==

... doesn't work yet ... but coming soon

== Reference Navaid ==

The GPS code automatically selects a reference navid, if one can be found nearby, and provides its location, range, bearing and frequency. This feature allows the pilot to cross-check the GPS indicated position against the reference navid.

== Common Procedures ==

=== Executing a ATC direct clearance ===

Commonly, ATC will clear an inbound or outbound aircraft to a waypoint in their area. Particularly for departures, various waypoints on a procedure (SID) may be skipped. In this case, simply load the active WPT, search forwards to the cleared waypoint, and press 'DTO'. The GPS will fly directly to the waypoint, and skip over any waypoints as necessary before resuming LEG mode.

=== Missed Approaches ===

The current GPS code lacks approach support, but it's still valuable to set the missed approach point as the active waypoint. Upon going missed, execute a direct-to, and you'll have one less thing to worry about when going missed.

== Future Functionality ==

===GPS===
It is possible for a the computer running Flightgear to create a dummy software GPS module which will appear on Bluetooth as an external GPS device available to pair simulating an actual GPS device often used in the cockpit. Simulated GPS location information from Flightgear can be sent wirelessly over this dummy GPS device to a tablet computer or any other device allowing pilots and simulator users to seamlessly use the same hardware and software to navigate in both real world and simulated flights without requiring any compatibility modifications on the tablet side. This functionality is not yet supported in Flightgear.

===ADS-B===
Like GPS a dummy ADS-B bluetooth device which transmits either Flightgear simulated or possibly real world ADS-B traffic can be created by the computer running Flightgear to appear over bluetooth as an available device for a tablet or other device to pair with. This module will display Flightgear simulated status information to tablets that have the required software such as ForeFlight to use real world ADS-B wireless dongles without requiring any compatibility modifications to the hardware or software of the tablet. Information from ADS-B includes ADS-B weather, animated NEXRAD radar, METARs, TAFs, NOTAMs, TFRs and more. https://en.wikipedia.org/wiki/ADS-B This functionality is not yet supported in Flightgear.

[[Category:Aircraft instruments]]

Global Positioning System

2013-12-25T08:55:20Z

Biketool: /* Future Functionality */ ADS-B

This pages discussed the generic GPS support in FlightGear, not any specific real-world device or operating procedure. Nevertheless, many similarities should exist. It is assumed the reader is familiar with radio navigation terminology and basic instrument flying procedures.

For background information on GPS usage itself, you may want to check out http://wiki.flightgear.org/index.php/Avionics_Development_Resources#GPS

'''Note''': the GPS is a work in progress, and under active development. If you encounter problems, please report them - and also suggest features. The [[GPS internals]] page mentions likely future enhancements and current limitations of code. Also note that panel instruments may extend or restrict access to the features below, depending on the specific device

== Basic Information ==

The GPS computes position, direction and velocity information independently of other instruments in FlightGear - for example the computed altitude is not related to any altimeter installed on the aircraft. GPS computed values are subject to different errors and precision as compared with other instruments. (In FG, the GPS is too accurate, and in the future some optional modelling of GPS reception will be added)

Useful information above includes true groundspeed (not airpseed) and ground track (different from heading), i.e the path the aircraft is taking over the ground, and the direction of movement.

== Active Waypoint ==

The GPS tracks an active waypoint, which can be an airport, VOR, NDB, fix or user-defined in various ways. Information about the active waypoint is provided - bearing, range, time to reach the waypoint, and so on.

== Modes ==

=== OBS ===
OBS mode makes the GPS behave like a nav-radio tuned to the active waypoint (which doesn't have to be a VOR). You select a desired radial, and the GPS will generate to/from-flags and a course deviation output, exactly like a VOR receiver. Since there's no radio reception involved, this works for NDBs or fixes too, and there is no issue with stations being out of range (or out of service).

The OBS radial can be adjusted via a dial at the bottom of the default GPS dialog - note the dial is only shown when in OBS mode, and hidden in DTO and LEG modes, to avoid confusion. Due to PLIB limitations, also note that the 0-degree radial is at the bottom, and the 180-degree radial is at the top - i.e the dial is upside down.

=== LEG ===
LEG mode is mostly used with an active route (defined in the route manager). In LEG mode, the active waypoint is the next waypoint on the current route, and the GPS calculates course deviation to fly the line between the previous waypoint and the active waypoint.

Upon reaching the active waypoint, the GPS automatically switches ('sequences') to the next waypoint, if one exists.

=== DTO ===
This mode is used to fly directly to a waypoint. When DTO mode is entered, the course deviation will be centred, and a bearing calculated to fly directly to the requested, active waypoint.

Upon reaching the waypoint, the GPS will continue flying the inbound bearing, *unless* the active waypoint is part of an active route. In this case, the GPS will automatically switch to LEG mode, and resume waypoint sequencing.

== Finding Waypoints ==

Waypoints can be selected in the following ways:

- searching by ident or name. Enter the full, or first few letters of a waypoint name, and search. The closest matching waypoint will be displayed, with successive results available, sorted by distance to the current GPS position.

- selecting the nearest waypoint (of a particular type). The closest ten waypoints can be loaded, and searched through

- loading waypoints from the active route (flight-plan)

== Turn Anticipation ==

... doesn't work yet ... but coming soon

== Reference Navaid ==

The GPS code automatically selects a reference navid, if one can be found nearby, and provides its location, range, bearing and frequency. This feature allows the pilot to cross-check the GPS indicated position against the reference navid.

== Common Procedures ==

=== Executing a ATC direct clearance ===

Commonly, ATC will clear an inbound or outbound aircraft to a waypoint in their area. Particularly for departures, various waypoints on a procedure (SID) may be skipped. In this case, simply load the active WPT, search forwards to the cleared waypoint, and press 'DTO'. The GPS will fly directly to the waypoint, and skip over any waypoints as necessary before resuming LEG mode.

=== Missed Approaches ===

The current GPS code lacks approach support, but it's still valuable to set the missed approach point as the active waypoint. Upon going missed, execute a direct-to, and you'll have one less thing to worry about when going missed.

== Future Functionality ==

===GPS===
It is possible for a the computer running Flightgear to create a dummy software GPS module which will appear on Bluetooth as an external GPS device available to pair simulating an actual GPS device often used in the cockpit. Simulated GPS location information from Flightgear can be sent wirelessly over this dummy GPS device to a tablet computer or any other device allowing pilots and simulator users to seamlessly use the same hardware and software to navigate in both real world and simulated flights without requiring any compatibility modifications on the tablet side. This functionality is not yet supported in Flightgear.

===ADS-B===
Like GPS a dummy ADS-B bluetooth device which transmits either Flightgear simulated or possibly real world ADS-B traffic can be created by the computer running FLightgear to appear over bluetooth as an available device for a tablet or other device to pair with. This module will display Flightgear simulated status information to tablets that have the required software to use real world ADS-B wireless dongles without requiring any compatibility modifications to the hardware or software of the tablet. Information from ADS-B includes ADS-B weather, animated NEXRAD radar, METARs, TAFs, NOTAMs, TFRs and more. https://en.wikipedia.org/wiki/ADS-B This functionality is not yet supported in Flightgear.

[[Category:Aircraft instruments]]

Global Positioning System

2013-12-25T06:39:40Z

Biketool: /* Future Functionality */ Simulated GPS for tablets and other external devices

This pages discussed the generic GPS support in FlightGear, not any specific real-world device or operating procedure. Nevertheless, many similarities should exist. It is assumed the reader is familiar with radio navigation terminology and basic instrument flying procedures.

For background information on GPS usage itself, you may want to check out http://wiki.flightgear.org/index.php/Avionics_Development_Resources#GPS

'''Note''': the GPS is a work in progress, and under active development. If you encounter problems, please report them - and also suggest features. The [[GPS internals]] page mentions likely future enhancements and current limitations of code. Also note that panel instruments may extend or restrict access to the features below, depending on the specific device

== Basic Information ==

The GPS computes position, direction and velocity information independently of other instruments in FlightGear - for example the computed altitude is not related to any altimeter installed on the aircraft. GPS computed values are subject to different errors and precision as compared with other instruments. (In FG, the GPS is too accurate, and in the future some optional modelling of GPS reception will be added)

Useful information above includes true groundspeed (not airpseed) and ground track (different from heading), i.e the path the aircraft is taking over the ground, and the direction of movement.

== Active Waypoint ==

The GPS tracks an active waypoint, which can be an airport, VOR, NDB, fix or user-defined in various ways. Information about the active waypoint is provided - bearing, range, time to reach the waypoint, and so on.

== Modes ==

=== OBS ===
OBS mode makes the GPS behave like a nav-radio tuned to the active waypoint (which doesn't have to be a VOR). You select a desired radial, and the GPS will generate to/from-flags and a course deviation output, exactly like a VOR receiver. Since there's no radio reception involved, this works for NDBs or fixes too, and there is no issue with stations being out of range (or out of service).

The OBS radial can be adjusted via a dial at the bottom of the default GPS dialog - note the dial is only shown when in OBS mode, and hidden in DTO and LEG modes, to avoid confusion. Due to PLIB limitations, also note that the 0-degree radial is at the bottom, and the 180-degree radial is at the top - i.e the dial is upside down.

=== LEG ===
LEG mode is mostly used with an active route (defined in the route manager). In LEG mode, the active waypoint is the next waypoint on the current route, and the GPS calculates course deviation to fly the line between the previous waypoint and the active waypoint.

Upon reaching the active waypoint, the GPS automatically switches ('sequences') to the next waypoint, if one exists.

=== DTO ===
This mode is used to fly directly to a waypoint. When DTO mode is entered, the course deviation will be centred, and a bearing calculated to fly directly to the requested, active waypoint.

Upon reaching the waypoint, the GPS will continue flying the inbound bearing, *unless* the active waypoint is part of an active route. In this case, the GPS will automatically switch to LEG mode, and resume waypoint sequencing.

== Finding Waypoints ==

Waypoints can be selected in the following ways:

- searching by ident or name. Enter the full, or first few letters of a waypoint name, and search. The closest matching waypoint will be displayed, with successive results available, sorted by distance to the current GPS position.

- selecting the nearest waypoint (of a particular type). The closest ten waypoints can be loaded, and searched through

- loading waypoints from the active route (flight-plan)

== Turn Anticipation ==

... doesn't work yet ... but coming soon

== Reference Navaid ==

The GPS code automatically selects a reference navid, if one can be found nearby, and provides its location, range, bearing and frequency. This feature allows the pilot to cross-check the GPS indicated position against the reference navid.

== Common Procedures ==

=== Executing a ATC direct clearance ===

Commonly, ATC will clear an inbound or outbound aircraft to a waypoint in their area. Particularly for departures, various waypoints on a procedure (SID) may be skipped. In this case, simply load the active WPT, search forwards to the cleared waypoint, and press 'DTO'. The GPS will fly directly to the waypoint, and skip over any waypoints as necessary before resuming LEG mode.

=== Missed Approaches ===

The current GPS code lacks approach support, but it's still valuable to set the missed approach point as the active waypoint. Upon going missed, execute a direct-to, and you'll have one less thing to worry about when going missed.

== Future Functionality ==

It is possible for a dummy software GPS module to appear on Bluetooth as an external GPS device. GPS information from Flightgear can be sent over this dummy GPS device to a tablet computer or any other device allowing pilots to use the same hardware and software to navigate in both real world and simulated flights without requiring any compatibility modifications. This functionality is not yet supported in Flightgear.

[[Category:Aircraft instruments]]