How do I port my OPNET HLA Federate from the DMSO RTI 1.3 to the MAK RTI?

Categories:
Solution Number:
S20294
Last Modified:
2013-07-06
Issue

How do I port my OPNET HLA Federate from the DMSO RTI 1.3 to the MAK RTI?

Solution
  1. Verify that you are using MAK RTI version 2.0.3
  2. Refer to the MAK documentation for all MAK licensing questions
  3. In the rid.mtl file, make sure RTI_forceFullCompliance is set to 1
  4. Make the following changes to your system environment variables:

Windows:
set RTI_HOME = <path to RTI directory> (e.g., c:\mak\makRTI-2.0.3-ngc)

To the following system variables, add the corresponding MAK paths:
PATH     <RTI_HOME>\bin
LIB      <RTI_HOME>\lib
INCLUDE  <RTI_HOME>\include

Solaris:
set RTI_HOME = <path to RTI directory> (e.g., /usr/local/makRti2.0.3-ngc)

To the following system variables, add the corresponding MAK paths:
PATH             <RTI_HOME>/bin
LD_LIBRARY_PATH  <RTI_HOME>/lib

  1. If you are simply porting OPNET federates, you are done.  If you plan to create new federates, or need to rebuild the federates in OPNET 10.0, add the following to the OPNET environment variable comp_flags_common:

-I/<RTI_HOME>/include

Please note that there is an implementation difference between DMSO's and MAK's RTI whereby communications between a federate and the RTI is dependent on other federates having called tick().  Under the DMSO implementation, communication from the RTI to a particular federate is independent of other federates' having called tick().

Environment

DES Kernel , HLA, OPNET Modeling and Simulation, OPNET Modeler

Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case