vsTASKER 7 User Manual
×
Menu
Index

RTI

 
RTI
1

Using

1. Using
vsTASKER can generate code for various RTI.
Depending on the RTI you have licensed and intend to use, select it into the list.
 
Supported RTI are the following:
  • Pitch RTI 1.3
  • Pitch RTI 1516
  • Pitch RTI Evoled (1516e)
  • KD RTI
  • Mak RTI 1.3
  • Mak RTI 1516
 
2

Extra cpp

2. Extra cpp
If you need to add some extra modules that must be compiled with the generated files, it is a good place to specified them here and each module separated with a comma.
When the complete path is not used, it must be specified in the next field (Inc Path).
 
3

Inc Path

3. Inc Path
By default and according to the RTI chosen, vsTASKER will fill set the field with predefined values.
Check that you have the environment variables defined.
All paths must be separated with commas.
 
4

Options

4. Options
Here stand the compilation options (and mostly defines) requested by the RTI modules mainly.
 
5

Libs

5. Libs
List here all necessary libraries requested to link the application.
 
6

Lib Path

6. Lib Path
This field specifies the library path for the libraries listed above.
 
7

Ambassador

7. Ambassador
vsTASKER will generate a vsTaskerAmbassador class that will inherit from BaseFederateAmbassador defined in these files.
They are normally belonging to each RTI manufacturer and are compliant with the standard.
However, vsTASKER is using locally copied files that the user can replace with the latest ones from the manufacturer of their API.