580
edits
Route manager: Difference between revisions
Jump to navigation
Jump to search
→Flying a Route
| Line 39: | Line 39: | ||
===Aircraft with a GPS, INS, FMS=== | ===Aircraft with a GPS, INS, FMS=== | ||
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. | 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== | |||
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. | |||