CDevices::SpatialConfig::AccelerationAxis | |
CViewport::ADAPTER_OBJECT | |
CBus::Afcs | (25) Automatic Flight Control System (AFCS) modes and engagement status, including autothrottle; |
CDevices::Analog | |
CDevices::AnalogConfig | |
CDevices::Apcupsd | C++ monitoring implementation of http://www.apcupsd.org |
CDevices::ApcupsdConfig | |
CDevices::ApcupsdParam | |
CDevices::JoystickConfig::Axis | |
▶CSystems::BaseComponent | |
▶CSystems::Component | |
CSystems::Battery | |
CSystems::Combustion | Combustion Chamber is very specific, on or off set, we get the pulses |
CSystems::Igniter | Igniter is very specific, on or off set, we get the pulses |
CSystems::N1 | N1 is very specific, load differential |
CSystems::N2 | N2 is very specific, load differential |
CSystems::Real | Real components simply take setState and apply it to currentState, they run their own fault states |
CSystems::Relay | |
CSystems::Starter | Starter is very specific, load differential |
CSystems::Switch | Switch is a direct-set (no control voltage, command from bus from physical switch) which takes a supply and propogates it, no load |
CSystems::TempSensor | Temperature sensor reads data from setState (or attached component?) and puts it on currentState assuming nothing is wrong with the sensor |
CSystems::Connector | |
CDevices::Bass | |
CDevices::BassConfig | |
CDevices::KeyboardConfig::Buffer | |
CBus | |
CDevices::JoystickConfig::Button | |
CDevices::AnalogConfig::Channel | |
CCommand | |
CComponent | |
CWatch::Condition | |
CCondition | |
CConfig | |
CSystems::Dependency | |
CDEVICE_OBJECT | |
CDevices::DeviceList | |
CElement | |
CDevices::Encoder | |
CDevices::EncoderConfig | |
CFont | |
▶CIMFSourceReaderCallback | |
CDevices::Webcam | |
CDevices::InterfaceKitConfig::Input | |
▶CInstrument | Abstract base class for instrumentation By definition, instruments don't do any of the work (they don't modify values) If you have something that takes data like VSI and AGL and then triggers GPWS that would be in a module This is presentation layer only - because we can have multiple copies of a particular instrument concurrently displayed What if we don't have data on the bus for the instrument, like FMS stores the waypoint order, waypoint locations? N1 and ITT are different, we are reading from sensors that could be flawed... not from FADEC directly |
CAlertMessageStack | Alert Message Stack (CAS) |
CAltitudeTape | Altitude |
CAttitudeIndicator | AI |
CDiagnostics | Diagnostics |
CFlightModeAnnunciator | FMA |
CHeadingIndicator | Heading |
CIndicatedAirSpeedTape | Forward definitions for the instruments are below |
CITTIndicator | ITT |
CMovingMap | MovingMap |
CN1Indicator | N1 |
CDevices::InterfaceKit | |
CDevices::InterfaceKitConfig | |
CDevices::Joystick | |
CDevices::JoystickConfig | |
CDevices::KeyboardConfig::Key | |
CDevices::Keyboard | |
CDevices::KeyboardConfig | |
CFcs::Location | |
CLogger | |
CLibrary::MathUtils | |
CMD5 | |
CMessage | |
▶CModule | Abstract base class for modules By definition, instruments don't do any of the work (they don't modify bus values) If you have something that takes data like VSI and AGL and then triggers GPWS that would be in a module It is a computer but not on the component level, it only has access to bus values from other modules |
CAfcs | Automatic Flight Control System |
CAse | Adaptive Scenario Engine |
CCas | Crew Alerting System |
CDoor | CUSTOM## Door module
|
CFadec | Full Authority Digital Engine Control |
CFcs | Flight Control System |
CFdr | Flight Data Recorder |
CFms | Flight Management System |
CGpws | Forward definitions for the modules are below |
CLogo | CUSTOM## Logo module
|
CMcu | Motion Control Unit |
CPfd | Primary Flight Display |
CRtu | Radio Tuning Unit |
CTcas | Traffic Collision Avoidance System |
CVmu | Voice Messaging Unit |
CNullable< T > | |
CNullable< bool > | |
CNullable< DWORD > | |
CNullable< float > | |
CNullable< Systems::Fault > | |
CNullable< SYSTEMTIME > | |
CDevices::InterfaceKitConfig::Output | |
CPage | |
CDevices::Printer | |
CDevices::YouTube::PublishParameters | |
CDevices::RakNet | |
CDevices::RakNetConfig | |
▶CSBasePacket | |
CSControlSurfaces | ID_USER_PACKET_ENUM + 0 |
CSEvents | ID_USER_PACKET_ENUM + 3 |
CSFromDisplay | ID_USER_PACKET_ENUM + 2 |
CSInitialData | ID_USER_PACKET_ENUM + 1 |
CAse::SCommand | |
CScreen | |
CDevices::InterfaceKitConfig::Sensor | |
CDevices::sentence | |
CPfd::SLight | |
CLibrary::Solar | |
CDevices::BassConfig::Sound | |
CSPacketSetting | |
CDevices::Spatial | |
CDevices::SpatialConfig | |
CSprite | |
CMcu::SSnap | |
CAse::SStep | |
CDevices::Apcupsd::STATUS | |
CLibrary::StringUtils | |
CAse::SVocalware | |
CAse::SVoice | |
CDevices::TeamSpeak | |
CDevices::TeamSpeakConfig | |
CText | |
CVehicle | |
CViewport | |
CSystems::Virtualization | |
CWatch | |
CWaypoint | |
CDevices::WebcamConfig | |
CWINDOW_OBJECT | |
CDevices::Xplane | |
CDevices::XplaneConfig | |
CDevices::YouTube | |
CDevices::YouTubeConfig | |