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

81 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
#ifndef __cplusplus
# error This library requires C++
#endif
#include <simgear/math/point3d.hxx>
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
* /instrumentation/dme/serviceable
* /instrumentation/dme/frequencies/source
* /instrumentation/dme/frequencies/selected-mhz
*
* Output properties:
*
* /instrumentation/dme/in-range
* /instrumentation/dme/indicated-distance-nm
* /instrumentation/dme/indicated-ground-speed-kt
* /instrumentation/dme/indicated-time-kt
*/
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:
DME ();
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;
Point3D _transmitter;
double _transmitter_elevation_ft;
double _transmitter_range_nm;
};
#endif // __INSTRUMENTS_DME_HXX
Copy permalink