Radar Warning Editor (radarWarnRxEditor)

Table of Contents

• Adding Support for New Sim Components
• How to Run the Example
  • Usage
• Classes
• Plugin Entry Points

The Radar Warning Editor example demonstrates the following:

• How to register a new descriptor in the SOE for a new sim component type
• How to register an existing descriptor in the SOE for a new sim component type

Adding Support for New Sim Components

This example extends the Simuulation Object Editor to be able to support new sim components. This allows the SOE to recognize user created sim components and understand what descriptors are used to configure these components. This allows user created systems that utilize new sim components to be read and written by the SOE.

This example is related to the Radar Warn back-end example and registers the new sim components from that example with the SOE.

How to Run the Example

Usage

To load this plugin into the Simulation Object Editor, open a command prompt in the bin64 directory and run the following command:

   simulationObjectEditor --loadPlugin ../examples/radarWarnRx/radarWarnRxEditor/build64/RelWithDebInfo/radarWarnRxEditor

To view the new behavior:

1. Start Simulation Object Editor with the above command - to load the radarWarnRxEditor plugin.
2. Verify the plugin is loaded through the Help -> Plugins menu item. The Plug-ins dialog should be listing the radarWarnRx plugin
3. Search for and Select the EA-18G Growler entity
4. Wait for the aicraft visual model to load.
5. Select the Systems tab - to view the EA-18G Growler systems
6. The Sensors list should contain the Radar Warning Receiver created by the plugin.

Classes

DtRadarWarningReceiverDescriptor

The new radar receiver component descriptor.

Plugin Entry Points

/*******************************************************************************
** Copyright (c) 2013 MAK Technologies, Inc.
** All rights reserved.
*******************************************************************************/

// This file defines the generic DT_DLL_VRF_PLUGIN_EXPORT_MACRO.  Use that macro when
// you want to export symbols.  Also, in your CMakeLists.txt file, make sure to
// define the VRFPLUGIN_EXPORTS define to tell the compiler to define the macro as an
// export
#include <vrfGuiCore/vrfGuiExportPlugin.h>

#include "simulationObjectEditorImpl/simulationObjectEditorApplication.h"
#include "vrfobjparam/simComponentDescriptorTypes.h"
#include "../radarWarnRxSim/radarWarningReceiverDesc.h"

// Entry point that must be defined by all plugins, this is called as part of the process that loads the plugin, before the de
// is fully initialized
bool initDeModule(makVrv::DtDe* de)
{
   // The Simulation Object Editor needs to be informed of new component types, and what
   // type of descriptor they use.
   // When adding a new descriptor type in the plugin, the creator function for the 
   // descriptor must be specified as well.
   DtParameterAlteringApplication::app(*de)->addSensor("simple-radar-warning-receiver", DtRadarWarningReceiverDescriptorType, 
      DtRadarWarningReceiverDescriptor::creator);

   // If a descriptor that is already part of VRF is being used, then simply specifying
   // the type identifier string for it and leaving the creator function as the default
   // is sufficient.
   DtParameterAlteringApplication::app(*de)->addController("simple-radar-warning-response", DtBaseComponentDescriptorType);

   return true;
}

void DtPluginInformation(DtVrfPluginInformation& info)
{
   info.pluginName = "radarWarnRx Simulation Object Editor Plugin";
   info.pluginVersion = "1.1";
   info.pluginCreator = "MAK Technologies";
   info.pluginCreatorEmail = "sales@mak.com";
   info.pluginContactWebPage = "www.mak.com";
   info.pluginContactMailingAddress = "10 Fawcett Street, Suite 204, Cambridge, MA 02138 USA";
   info.pluginContactPhone = "(617) 876 8085";
}