fly/flightgear
1
0
Fork 0
Code Activity
flightgear/src/Systems/system_mgr.cxx

30 lines
717 B
C++
Raw Normal View History

Started new module and sub-modules for aircraft systems, including an initial simplistic vacuum system that's not yet connected to anything.
2002-09-23 19:55:10 +00:00
// system_mgr.cxx - manage aircraft systems.
// Written by David Megginson, started 2002.
//
// This file is in the Public Domain and comes with no warranty.
#include "system_mgr.hxx"
Stub in a place holder for the electrical system model.
2002-09-24 15:24:04 +00:00
#include "electrical.hxx"
Added pitot system and new airspeed indicator.
2002-09-28 20:48:53 +00:00
#include "pitot.hxx"
Added static port system and a new altimeter model connected to it. The static port uses the /systems/static/ property subtree, and the altimeter uses the /instrumentation/altimeter/ property subtree.
2002-09-27 18:27:58 +00:00
#include "static.hxx"
Flattened src/Systems/ subtree. Added src/Instrumentation/ with partial stab at a vacuum-driven attitude indicator.
2002-09-24 14:51:37 +00:00
#include "vacuum.hxx"
David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
#include "submodel.hxx"
Started new module and sub-modules for aircraft systems, including an initial simplistic vacuum system that's not yet connected to anything.
2002-09-23 19:55:10 +00:00
FGSystemMgr::FGSystemMgr ()
{
- Added a redundant (left/right) vacuum pump. - Modified the rpm vs. suction formula to hit much more realistic numbers. We should be seeing just over 4 inhg at idle and approaching 5 inhg at full throttle.
2003-05-27 19:25:27 +00:00
set_subsystem( "electrical", new FGElectricalSystem );
set_subsystem( "pitot", new PitotSystem );
set_subsystem( "static", new StaticSystem );
set_subsystem( "vacuum-l", new VacuumSystem(0) );
set_subsystem( "vacuum-r", new VacuumSystem(1) );
Vivan Meazza: The maths, so far, is now correct. Roll and pitch are now both in the correct sense. The aircraft velocity is added correctly to the submodel velocity, and the submodel is now visible when instantiated. However, the velocity is measured at the aircraft centre. To be totally correct we ought to take into account the aircraft's rotational velocity. We have pitch rate and roll rate available, but not yaw rate (small anyway).
2004-09-14 08:27:55 +00:00
set_subsystem( "submodel", new SubmodelSystem() );
Started new module and sub-modules for aircraft systems, including an initial simplistic vacuum system that's not yet connected to anything.
2002-09-23 19:55:10 +00:00
}
FGSystemMgr::~FGSystemMgr ()
{
}
// end of system_manager.cxx
Copy permalink