> Hi all,
> Down here at DSTO we are developing the capability to use DAVE-ML as the native
> aircraft data format for our flight simulation activities. These activities
> cover performance estimation, flight dynamic, flight test and HIL simulation.
> The plan is to encapsulate the aircraft configuration properties, as well as
> the aerodynamics, propulsion, mass properties and weapons configurations in
> A report is being written detailing the Janus class, which I can forward draft
> of to those interested. I would also be interested in hearing from anyone about
> possible collaborative activities with developing the Janus class, especially
> if it helps reduce duplication of activities.
If I understand you correctly, it sounds as though you are crafting an aircraft
configuration file format similar to what JSBSim and the FlightGear project have had
some time, and are still developing (with an eye on DAVE-ML). For more information
JSBSim, see www.jsbsim.org.
We (JSBSim developers) are currently modifying our configuration file format to version
2.0. We have a sample representing the Cessna C-172 here:
This format is capable, but quite likely is far more "lightweight" than what you are
developing for military purposes. Still, you may find it interesting. In our
file format, we can specify (in addition to aerodynamic properties):
- mass properties
- flight control system and autopilot (using filters, switches, gains, etc.)
- ground reactions
- data logging
As for a parser, the FlightGear project has wrapped a C++ class around eXpat,
what is called "easyXML". It is (currently) a non-validating XML parser, though I am
looking at turning on that capability if possible. For JSBSim (which can also be run
standalone mode apart from FlightGear) I am extending the easyXML parser in a C++
parse our new aircraft config file format.
I would be interested in reading more about your project.
Chief Architect and Development Coordinator,
Open Source JSBSim Project, www.jsbsim.org