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:11, 7 December 2013
, 7 December 2013→Simulation within Simulation
| Line 201: | Line 201: | ||
It is foreseeable that we may need to modify and extend JSBSim, i.e. to add new components - unfortunately, the "Extending JSBSim" chapter in the JSBSim reference manual is still just a placeholder without any content, so here are some stubs to help lower the barrier to entry when extending JSBSim. | It is foreseeable that we may need to modify and extend JSBSim, i.e. to add new components - unfortunately, the "Extending JSBSim" chapter in the JSBSim reference manual is still just a placeholder without any content, so here are some stubs to help lower the barrier to entry when extending JSBSim. | ||
=== Status (12/2013) === | |||
* Get & Build JSBSim {{Done}} | |||
* Experiment with modifying JSBSim {{Done}} | |||
* Hook up JSBSim standalone to FlightGear {{Done}} | |||
* Modify the existing slave/child FDM capability to instantiate a full aircraft FDM {{progressbar|60}} | |||
* 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}} | |||
* 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) {{progress|30}} | |||
* Extend the systems/GNCUtilities.xml file to also support waypoints 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}} | |||
=== Simulation within Simulation === | === Simulation within Simulation === | ||