coreDS™ supports all RTIs. The coreDS™ has been tested with the following RTI:
- pRTI 1.3, 1516 and 1516e from Pitch Technologies.
- MAK RTI 1.3, 1516 and 1516e from Mak Technologies
- RTI NG Pro 1.3, 1516 and 1516e from Raytheon
- OpenSource RTI Portico
- OpenSource RTI CERTI
Supported compiler and platforms
- (win) Visual Studio 2005 (32 bits)
- (win) Visual Studio 2008 (32 and 64 bits)
- (win) Visual Studio 2010 (32 and 64 bits)
- (win) Visual Studio 2013 (32 and 64 bits)
- (win) Visual Studio 2015 (32 and 64 bits)
- (mac) xCode 6 and up (64 bits)
- (linux) gcc 4.1 and up (32 and 64 bits)
Supported communication protocols
- HLA 1.3
- IEEE 1516
- IEEE 1516e
- DIS v4
- DIS v5
- DIS v6
- DIS v7
- TENA (Planned)
- DDS (Planned)
Supported FOM and PDUs
coreDS™ is FOM agile, meaning the product can be configuration using any FOM. The product has been tested with the RPR-FOM. The FOM file (and the corresponding data mapping) can be changed at run-time.
On the DIS side, coreDS™ supports all PDUs and is even compatible with custom PDU (the process is simple and can be done either by you or us).
Low level functions
coreDS™ all direct calls to all HLA 1.3, IEEE 1516 and IEEE 1516e calls and callbacks.
Integrated Scripting – LUA
LUA is a interpreted language providing great execution performances with an impressing facility to use. Scripting capabilities have been embedded in coreDS™ for data manipulation at run time (e.g.: coordinate conversation, scale factor, unit conversion, and more …), HLA callback implementation or to call HLA services through coreDS™. On the DIS side you can handle any received PDU.
Our LUA integration comes with editing and debugging capability. This is an end user functionality providing complete control over data exchange with other applications at run time.
Slick Interfaces make them match your style
coreDS™ provides out of the box configuration GUIs to properly configure your simulator for distributed interaction. Our documented interface greatly simplify your work and provide the necessary background information for those not so familiar with HLA/DIS.These are huge time saver: no need to handle saving, loading configuration or error handling.
When packaging our interface with your simulator, you can make them match the look and feel of your application simple by applying your own interface skins.
Preconfigured Mapping comes with your final solution
The mapping is the link between your simulator data and the wider simulation (federation) data. With coreDS™, mapping for a specific combination of standard and/or FOM modules can be created and distributed. For example, if you are using HLA, you can provide mapping information between you simulator and the RPR FOM (or any other FOM). These mapping can be distributed with your simulator, edited by the users or completely redefined by them. The same logic applies to DIS where you can map your data to any PDU.
Integrated Data Filtering minimizing data exchange
Using both HLA and DIS, coreDS™ provides means of filtering information exchange between your simulator and the federation. Data filtering is applicable to data type and frequency update. You get a better control over data transfer minimizing risk of network overflow.
Advanced HLA feature support
When using coreDS™, some HLA features are automatically supported:
Available edition and Licensing
coreDS™ comes in three editions, each with their own set of features and licensing.
If you want to deploy your simulator to your client (let’s say, you sell a Flight Simulator), you will need the “Developer edition”. For local development and deployment, you should go with either the “Standard” or “Professional” edition.
Our products support a wide range of licensing mechanisms:
- Node lock licence
- Network licence
- Floating licence
The “Developer Edition” provides Royalty free deployment!
What can be configured at run time
Short answer: Everything
Once your simulator has been compiled and linked with our libraries, the following configuration options can be changed at run time from your simulator through the coreDS™ GUI’s:
- FOM files or FOM modules;
- RTI provider and/or bindings;
- Connection settings (HLA or DIS);
- HLA or DIS standard version;
- HLA/DIS federate configuration parameters;
- coordinate conversion (common conversion included)
- data transformation
- HLA callback implementation
- HLA config through any HLA services
- and more …