Route manager: Difference between revisions

Jump to navigation Jump to search

Route manager (view source)

Revision as of 23:44, 18 October 2009

239 bytes removed ,  18 October 2009
→‎Flying a Route
Line 32: Line 32:
==Flying a Route==
==Flying a Route==


Flying a route depends partly on whether the aircraft includes a navigation computer system (for example, an INS or GPS), or not.  
When a route is activated, the GPS system enters 'leg' mode, and will automatically sequence waypoints as they are overflow. Note that all aircraft can use the default route-manager and GPS functions, even aircraft that would never (historically) has such systems. This is a convenience to casual users, testing, and so on.


===Aircraft without a navigation system===
In particular, the GPS drives some properties of the generic autopilot, so 'true heading hold' mode can be used to fly the route manager route (or any other GPS course).
A default GPS is provided for all aircraft; this is unrealistic but convenient for casual users and testing.


===Aircraft with a GPS, INS, FMS===
In aircraft with realistic navigation systems, or customised autopilots, the default behaviours above may not work; hopefully the aircraft author has provided alternative methods, such as panel instruments, to control things.
It is assumed the navigation system disables route-manager auto-sequencing (and some other automatic behaviours), and handles all navigation itself. In this case, the route manager is simply providing a library of waypoints; it's up to a specific navigation / autopilot system to follow courses, establish vertical navigation, and so on. Depending on the real-world system being modelled, fully automatic flight may be possible, controlling lateral and vertical navigation as well as speed - but equally, some real world GPS and INS units may not even be connected to the autopilot, and require manual intervention to command the aircraft.


==Properties==
==Properties==
When a route is active, the route-manage provides various pieces of information based upon current aircraft position / speed, and the route progress. These values would be calculated by the navigation computer in a real system, but are handled by route-manage in FG for convenience. Values logged include the takeoff time, estimated time enroute (ETE), distance remaining enroute, and so on - browse the property tree to see what's available.
When a route is active, the route-manage provides various pieces of information based upon current aircraft position / speed, and the route progress. These values would be calculated by the navigation computer in a real system, but are handled by route-manage in FG for convenience. Values logged include the takeoff time, estimated time enroute (ETE), distance remaining enroute, and so on - browse the property tree to see what's available.
Zakalawe
580

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/16462"

Navigation menu