20,741
edits
Implementing VNAV support in FlightGear: Difference between revisions
Jump to navigation
Jump to search
Implementing VNAV support in FlightGear (view source)
Revision as of 05:12, 7 December 2013
, 7 December 2013→Status (12/2013)
| Line 209: | Line 209: | ||
* Add a new FCS component (XML files) that instantiates a child FDM {{progressbar|70}} | * Add a new FCS component (XML files) that instantiates a child FDM {{progressbar|70}} | ||
* Expose child FDM parameters to the outer FDM and make them accessible for PID/FCS components {{Not done}} | * Expose child FDM parameters to the outer FDM and make them accessible for PID/FCS components {{Not done}} | ||
* Come up with a JSBSim script (FGScript) for a test flight with multiple waypoints (different altitudes) using the c310 in the KSFO area (default scenery) {{ | * Come up with a JSBSim script (FGScript) for a test flight with multiple waypoints (different altitudes) using the c310 in the KSFO area (default scenery) {{progressbar|30}} | ||
* Extend the systems/GNCUtilities.xml file to also support | * Extend the systems/GNCUtilities.xml file to also support altitudes and compute required FPAs for each waypoint {{Not done}} | ||
* .... | * .... | ||
* port the c310 example and use the 737 instead, because it better matches airliners available in FG (will also need AP work) {{Not done}} | * port the c310 example and use the 737 instead, because it better matches airliners available in FG (will also need AP work) {{Not done}} | ||
* look into adapting FlightGear accordingly {{Not done}} | |||
=== Simulation within Simulation === | === Simulation within Simulation === | ||