These should be separated by spaces, e.g. In practice, navaids with conflicting names are located far enough apart that this works automatically in practice.įrom Flightgear 2016.2.0 onwards, it is also possible to add a list of waypoints using the route manager dialog. Since navaid identifiers are not unique, the route-manager uses your departure airport or the previously defined waypoint to locate the identifier search. The simplest way to define a route is to add waypoints one at a time by identifier. In the FlightGear route manager, the active leg is from the previous waypoint to the current waypoint - i.e the current waypoint is where you're heading to at the moment. Many real-world devices deal in legs primarily, since each leg corresponds to a desired track, a distance and possibly an altitude to climb / descend. Normally, the route-manager moves automatically to the next waypoint after passing the current point (this is known as 'sequencing'), but if necessary the active waypoint can be manually adjusted.Īn important piece of terminology is a leg, which is a section of route between two waypoints. The route-manager maintains a current waypoint, which is shown in route-manager dialog, the GPS dialog (in LEG mode), on the default HUD, and potentially in cockpit displays in the aircraft. In the future, other data, especially speed restrictions, may also be associated with waypoints. Each waypoint may also have an altitude associated with it, for vertical navigation modes (VNAV). Route manager waypoints are entered as a navaid ident, an explicit latitude/longitude pair, or as an offset (bearing and distance) from another navaid. All information is currently optional, which is highly unrealistic, but convenient.
The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints. In general core features exist in whichever place seems the most natural, and it's up to instruments to aggregate the core modules as they require.
It's important to realize that the route-manager (and GPS) are pieces that a panel instrument might present as a single real world device - the mapping between C++ modules, generic user interface and in-panel instruments is very fluid, by design. The route-manager is also how a flight plan is made available to FlightGear - in the future this will hopefully permit better ATC and multi-player interactions, since ATC logic or controllers will be able to observe the filed plan associated with a pilot. Some panel instruments may provide access to the route manager via their own UI, but the route-manager is always available through a generic dialog box. The route-manager models part of the functionality found in real-world GPS and FMS devices, but is usable in any aircraft.
#FLIGHTGEAR ROUTE MANAGER MANUAL#
The httpd-option offers a similar interface as the props-option, but is more convenient for the manual assignment of state variables in FlightGear.(in the following sections, familiarity with basic IFR concepts, Autopilot usage and radio navigation is assumed) With a web browser on the same machine, one can browse the FlightGear property tree when opening the following url: PORT-A is the port used for communicating with Matlab. In order to communicate with the flight simulator, FlightGear has to be started with the following command line options:įgfs.exe -fg-root=SOME.PATH -fg-scenery=SOME.PATH -props=PORT-A -httpd=PORT-B Functions for other purposes can be easily implemented by using the same type of socket connection. The functions were written for the simulation of routing algorithms in Matlab. Speeds up FlightGear's simulation speed by a factor. Inserts waypoint/s (Latitude, Longitude, Altitude ) at certain position of current route. Reads number of remaining waypoints on the current route. Reads distance of aircraft from current waypoint in sea miles and converts it to meters. Reads FlightGear's simulation time in seconds. Reads aircraft position and orientation (Latitude, Longitude, Altitude, Ground elevation, Heading, Pitch, Yaw, Roll ). The ZIP-file contains a library of Matlab functions to remotely control an aircraft's path in FlightGear:Īctivates Autopilot and sets target speed.Īdds waypoint/s (Latitude, Longitude, Altitude ) after last entry of current route.ĭeletes all waypoints of the current route.
0 kommentar(er)
