VR-Exchange Capabilities

Protocol Translation & Bridging

MAK’s universal translator for distributed simulations. It performs FOM-to-FOM translation, RTI-to-RTI bridging, DIS or HLA-to-TENA translation, and can support simulation-to-C4I interoperability.

Learn all about VR-Exchange by clicking through the tabs below or download the VR-Exchange Capabilities document.

VR-Exchange Bridges Otherwise Incompatible Exercises

In general, bridging is necessary whenever it is not possible to achieve direct interoperability among a set of assets. Perhaps different federates have been developed to different FOMs, and were not developed using a FOM-Agile middleware toolkit like VR-Link. Bridging between the FOMs may be a more feasible solution than changing one set of federates to use the other federates' FOM. Perhaps one set of federates are using HLA 1.3 while others are using HLA 1516-2000, and you are not using an RTI that supports wire-compatibility between the two (such as the MAK RTI). Bridging may be a more feasible solution than upgrading the HLA 1.3 federates to IEEE 1516-2000. Perhaps different federate developers are used to running with specific RTI implementations, and are unwilling to switch to a common choice. Bridging may be a more politically palatable solution than arguing about whose RTI to use. Perhaps you have some HLA Federates and some TENA Federates that need to play in the same federation. Bridging may be the only way to achieve this goal.

ST Engineering

ST Engineering