Products
- VR-Link
- MÄK RTI
- MÄK Gateway
- VR-Exchange
- VR-Forces
- VR-Vantage
- MÄK Stealth
- MÄK Data Logger
- MÄK PVD
- Network Centric
Forces
VR-Exchange
Looking for DIS-HLA translation?
Looking for the MÄK Gateway?
The MÄK Gateway is now called VR-Exchange. It offers DIS-HLA translation and much more.
The Interoperability Portal
- FOM-to-FOM Translation
- RTI-to-RTI Bridging
- DIS or HLA-to-TENA Translation
- Supports "Federation of Federations" System Architecture
- Protocol-Independent Data Exchange in Shared Memory
- Open Architecture ― Custom Brokers Can Support Other Protocols
- LVC Integration
- HLA 1.3 and IEEE 1516 Support
Overview
VR-Exchange is a "universal translator" for distributed simulation. With VR-Exchange, you can link together simulations that use different HLA RTIs, different object models, and even different protocols.
The Need for Bridging
In some cases, this kind of bridging is necessary because it is not practical to get everyone to agree on a protocol, HLA FOM or RTI, or TENA LROM. In other cases, bridging is needed because a system architect wants to implement a hierarchical "federation of federations" design. Bridging is often needed to support large-scale LVC (Live, Virtual and Constructive) integration, or to support Simulation-to-C4I interoperability. For all of these cases, VR-Exchange can provide the solution.
A Federation of Federations:
VR-Exchange bridges each LAN’s federation to a central federation made up entirely of portals. The portals exchange data among the sites through the central federation.
Architecture
The VR-Exchange architecture consists of a protocol-independent Data Exchange, and a Broker for each supported protocol. Each Broker runs as a separate process, and trades data with the other Brokers through the Data Exchange ― a shared memory interface.
Built-in Translation
Currently, VR-Exchange includes Brokers for HLA 1.3, IEEE 1516, TENA, and DIS. The HLA and TENA Brokers leverage MÄK’s VR-Link® FOM and LROM Mapping infrastructure, allowing you to configure them for custom object models. The HLA Brokers can also be configured for different RTIs, simply by pointing at the appropriate shared libraries.
Extensibility
VR-Exchange’s open architecture means that you can also develop custom Brokers for C4I protocols or other data standards. We provide a documented interface (API) to the Data Exchange, as well as sample code that shows how to read and write to our protocol independent data format. Once you are able to translate your protocol to this lingua franca, your data can be read by any of the other VR-Exchange Brokers.
Download the VR-Exchange brochure.
