8,567
edits
Autopilot: Difference between revisions
Jump to navigation
Jump to search
m
little more cleanup/link fix
m (some cleanup and additions) |
m (little more cleanup/link fix) |
||
| Line 8: | Line 8: | ||
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. | 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. | ||
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 using JSBSim. 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 using [[JSBSim]]. 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. | ||
In real life, aircraft have specifically-programmed/customized autopilot system to cater for individual aircraft characteristics. | In real life, aircraft have specifically-programmed/customized autopilot system to cater for individual aircraft characteristics. | ||
To a certain extent, Flightgear has the possibility to simulate this as well. | To a certain extent, Flightgear has the possibility to simulate this as well. | ||
So it is possible to write a custom autopilot.xml to override the generic autopilot implementation. | So it is possible to write a custom <tt>autopilot.xml</tt> to override the generic autopilot implementation. | ||
This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both. | This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both. | ||
Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot-specific features. | Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot-specific features. | ||
Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots). | Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots). | ||
For example, the | For example, the [[Piper PA34-200T Seneca II|Seneca II]] and the [[Piper PA-24 Comanche|Piper Comanche]] autopilots can be only used from the virtual cockpit using custom panel hotspots. This is in fact increasingly the case, as new emulations of autopilot systems are implemented using the built-in scripting language [[Nasal scripting language|Nasal]] which provides for much more flexible system design and functionality, compared to the relatively static way of describing autopilot systems and their relevant and modes using only the XML-configurable autopilot system. In fact, to properly emulate more complex autoflight systems that provide support for more abstract flight modes, using a combination of XML-configurable PID controllers and Nasal is likely to be the most promising approach. | ||
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. | 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. | ||
| Line 27: | Line 27: | ||
In addition, JSBSim also features support for a standalone autopilot implementation, that works without any dependency to FlightGear/Nasal. | In addition, JSBSim also features support for a standalone autopilot implementation, that works without any dependency to FlightGear/Nasal. | ||
For further information about programing autopilots in FlightGear look at [http://www.flightgear.org/Docs/XMLAutopilot/ | For further information about programing autopilots in FlightGear look at [[Autopilot Tuning Resources]] and http://www.flightgear.org/Docs/XMLAutopilot/. | ||
==Autopilot Settings== | ==Autopilot Settings== | ||
| Line 50: | Line 50: | ||
==Route manager== | ==Route manager== | ||
The Route Manager in | The Route Manager in FlightGear is something like a very simple FMC- Flight Management Control/Computer. | ||
In FGFS you can input a list of waypoints like NAVAIDS, Fixes and Airports, which the aircrafts flies along. You can also add the altitude which the aircraft should have at | In FGFS you can input a list of waypoints like NAVAIDS, Fixes and Airports, which the aircrafts flies along. You can also add the altitude which the aircraft should have at a certain waypoint. So it is possible to let the aircraft fly along a certain route. | ||
At the moment, it is not possible to add velocities or other constraints. | At the moment, it is not possible to add velocities or other constraints. | ||