It is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot/aircraft-specific features (for examples, see the b1900d or Citation Bravo in Git/HEAD). NAV1 Glideslope: Tracks an ILS glideslope.AGL Hold: Acquire and hold the set altitude above ground level (sometimes known as "radio altitude").Altitude Hold: Acquire and hold the set altitude.FPA Hold: Hold a set flight path angle.Vertical Speed: Hold the set vertical speed in feet per minute.The mode selected here is ignored if "Speed with Pitch" is selected as it is in conflict.Mach mode tracking is possible, but the dialog does not contain a method to enable it at this time.The throttle will be unlocked and can be moved to adjust climb/descent rate. Speed with Pitch: Hold the set airspeed by adjusting pitch angle.Speed with Throttle: Hold the set airspeed by adjusting throttle.NAV1 CDI Course: Tracks a VOR or ILS localizer.This mode changes to GPS/FMS Heading if the Route Manager is activated. Heading Bug: Tracks the heading bug (magnetic heading).Some aircraft may re-use this mode to hold a set bank angle. Wings Level: Keeps the aircraft's wings level.The AP Settings dialog can be found at Autopilot > Autopilot Settings. In addition, JSBSim also features support for a standalone autopilot implementation, that works without any dependency to FlightGear/Nasal.įor further information about programing autopilots in FlightGear look at Autopilot Tuning Resources and. This may also apply to aircraft panels, that are seemingly offering functionality that may not yet be implemented. This may be due to an aircraft's completion status, but also due to technical limitations in certain aircraft/autopilot, so that only certain modes are provided. In general, it can be considered to be more complex to provide proper cockpit panel implementations than wiring up the autopilot properties to the standard autopilot GUI dialog, so if an aircraft's autopilot doesn't seem to work properly using cockpit panel hotspots, you may want to try using the standard GUI dialog instead.Īlso, please note that not all aircraft/autopilot combinations provide full support for all features offered by the standard autopilot dialog. This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both. So it is possible to write a custom autopilot.xml to override the generic autopilot implementation. To a certain extent, Flightgear has the possibility to simulate this as well. In real life, aircraft have specifically-programmed/customized autopilot system to cater for individual aircraft characteristics. You can enable it with the "Autopilot Settings" which you can open using the F11-key or in the menu bar using the "Autopilot" item. The generic one can be used for aircraft which don't have a custom autopilot implementation and seems to work reasonably well on most aircraft. We have a generic one and custom ones written for a certain aircraft, which are supposed to simulate particular autopilot types/models for a specific aircraft.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |