fly/flightgear
1
0
Fork 0
Code Activity
flightgear/src/Instrumentation/dme.hxx

80 lines
1.8 KiB
C++
Raw Normal View History

New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
// dme.hxx - distance-measuring equipment.
// Written by David Megginson, started 2003.
//
// This file is in the Public Domain and comes with no warranty.
#ifndef __INSTRUMENTS_DME_HXX
#define __INSTRUMENTS_DME_HXX 1
This is step "1" of probably "many" in the process of separating out the scene management code and organizing it within simgear. My strategy is to identify the code I want to move, and break it's direct flightgear dependencies. Then it will be free to move over into the simgear package. - Moved some property specific code into simgear/props/ - Split out the condition code from fgfs/src/Main/fg_props and put it in it's own source file in simgear/props/ - Created a scene subdirectory for scenery, model, and material property related code. - Moved location.[ch]xx into simgear/scene/model/ - The location and condition code had dependencies on flightgear's global state (all the globals-> stuff, the flightgear property tree, etc.) SimGear code can't depend on it so that data has to be passed as parameters to the functions/methods/constructors. - This need to pass data as function parameters had a dramatic cascading effect throughout the FlightGear code.
2003-05-06 23:46:24 +00:00
#include <simgear/props/props.hxx>
Move FGEventMgr and FGSubsystemMgr over to SimGear, add SGEventMgr to FlightGear's globals structre and some small code cleanups
2003-09-24 17:20:55 +00:00
#include <simgear/structure/subsystem_mgr.hxx>
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
/**
* Model a DME radio.
*
* Input properties:
*
* /position/longitude-deg
* /position/latitude-deg
* /position/altitude-ft
* /systems/electrical/outputs/dme
Roy Vegard Ovesen: Instrumentation and systems are now configureable from xml files. The two generic configurations generic-systems.xml and generic-instrumentation.xml configures the systems and instrumentation as it was hardcoded. You can override the generic configurations in a similar way as you override the autopilot configuration.
2004-10-16 12:37:39 +00:00
* /instrumentation/"name"/serviceable
* /instrumentation/"name"/frequencies/source
* /instrumentation/"name"/frequencies/selected-mhz
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
*
* Output properties:
*
Roy Vegard Ovesen: Instrumentation and systems are now configureable from xml files. The two generic configurations generic-systems.xml and generic-instrumentation.xml configures the systems and instrumentation as it was hardcoded. You can override the generic configurations in a similar way as you override the autopilot configuration.
2004-10-16 12:37:39 +00:00
* /instrumentation/"name"/in-range
* /instrumentation/"name"/indicated-distance-nm
* /instrumentation/"name"/indicated-ground-speed-kt
* /instrumentation/"name"/indicated-time-kt
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
*/
Move FGEventMgr and FGSubsystemMgr over to SimGear, add SGEventMgr to FlightGear's globals structre and some small code cleanups
2003-09-24 17:20:55 +00:00
class DME : public SGSubsystem
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
{
public:
Roy Vegard Ovesen: Instrumentation and systems are now configureable from xml files. The two generic configurations generic-systems.xml and generic-instrumentation.xml configures the systems and instrumentation as it was hardcoded. You can override the generic configurations in a similar way as you override the autopilot configuration.
2004-10-16 12:37:39 +00:00
DME ( SGPropertyNode *node );
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
virtual ~DME ();
virtual void init ();
virtual void update (double delta_time_sec);
private:
void search (double frequency, double longitude_rad,
double latitude_rad, double altitude_m);
SGPropertyNode_ptr _longitude_node;
SGPropertyNode_ptr _latitude_node;
SGPropertyNode_ptr _altitude_node;
SGPropertyNode_ptr _serviceable_node;
SGPropertyNode_ptr _electrical_node;
SGPropertyNode_ptr _source_node;
SGPropertyNode_ptr _frequency_node;
SGPropertyNode_ptr _in_range_node;
SGPropertyNode_ptr _distance_node;
SGPropertyNode_ptr _speed_node;
SGPropertyNode_ptr _time_node;
double _last_distance_nm;
double _last_frequency_mhz;
double _time_before_search_sec;
bool _transmitter_valid;
Make more use of SGGeod
2006-06-15 19:16:21 +00:00
SGVec3d _transmitter;
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
double _transmitter_elevation_ft;
double _transmitter_range_nm;
This set of changes impliments the following: - FG now directly supports Robin's native nav database file format. - His latest data now separates out dme, gs, loc, and marker beacon transmitters rather than lumping them all into a single "ILS" record. - These new data structure changes prompted me to do some code restructuring so that internally these different types of navaids are all kept as separate lists and searched and handled separately. - This structural change had a cascading affect on any code that references or uses the nav databases. I've gone and "touched" a lot of nav related code in a lot of places. - As an added bonus, the new data (and code) adds DME bias so these will all now read as they do in real life. - Added Navaids/navdb.cxx and Navaids/navdb.hxx which provide a front end loaders for the nav data. - Added Navaids/navrecord.hxx which is a new "generic" nav data record. - Removed Navaids/ils.hxx, Navaids/ilslist.cxx, Navaids/ilslist.hxx, Navaids/mkrbeacons.cxx, and Navaids/mkrbeacons.hxx which are all now depricated.
2004-05-28 05:24:54 +00:00
double _transmitter_bias;
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
Roy Vegard Ovesen: - finish cleanup/optimization of instrumentation system (started by mfranz) - improve configuration of special properties by addressing them directly
2006-12-06 22:11:43 +00:00
string _name;
int _num;
Roy Vegard Ovesen: Instrumentation and systems are now configureable from xml files. The two generic configurations generic-systems.xml and generic-instrumentation.xml configures the systems and instrumentation as it was hardcoded. You can override the generic configurations in a similar way as you override the autopilot configuration.
2004-10-16 12:37:39 +00:00
New version of basic DME support. This can coexist with the old one for a little while, since it uses different properties. There are some improvements, especially with searching and range. It also has its own serviceable and in-range properties, independent of any coupled VOR.
2003-03-09 03:20:34 +00:00
};
#endif // __INSTRUMENTS_DME_HXX
Copy permalink