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 10:51, 4 December 2013
, 4 December 2013→Instancing another FDM
(→JSBSim) |
|||
| Line 485: | Line 485: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
== Instancing another FDM == | === Instancing another FDM === | ||
The whole VNAV effort would be greatly simplified if we could directly run and query the FDM for some future point in time. This isn't directly supported by JSBSim. However, as a workaround, we could run a "simulation inside the simulation" by instantiating the JSBSim FDM recursively: | The whole VNAV effort would be greatly simplified if we could directly run and query the FDM for some future point in time, for example to run a trajectory prediciton calculatoin. This isn't directly supported by JSBSim at the moment. | ||
However, as a workaround, we could run a "simulation inside the simulation" by instantiating the JSBSim FDM recursively: | |||
As in, run an independent instance of the FDM as part of the FCS, to solve for certain VNAV constraints (altitude, speed, time) via specific pitch/thrust settings. | As in, run an independent instance of the FDM as part of the FCS, to solve for certain VNAV constraints (altitude, speed, time) via specific pitch/thrust settings. | ||