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 02:34, 8 December 2013
, 8 December 2013→Status (12/2013)
| Line 210: | Line 210: | ||
* 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) {{progressbar| | * Modify the route manager dialog to export flight plans into JSBSim/FGScript format {{done}} | ||
* Extend the route manager dialog to also export for info for each leg, including constraints (altitude, speeds) {{Not done}} | |||
* Extend the FGScript template to compute FPAs for each leg, and add a monitoring routine that tracks compliance {{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) {{progressbar|70}} (now automated via modified route manager/flight plan exports) | |||
* Extend the modified route manager dialog to show a the route {{Progressbar|70}} | |||
* Extend the route manager to also show a vertical profile using a canvas-driven altitude/distance graph {{Not done}} | |||
* Extend the systems/GNCUtilities.xml file to also support altitudes and compute required FPAs for each waypoint {{Not done}} | * Extend the systems/GNCUtilities.xml file to also support altitudes and compute required FPAs for each waypoint {{Not done}} | ||
* .... | * .... | ||