ASTi Application Note 96: Setting up HLA in T4 ACE
There are several steps to set up HLA in T4 ACE. This Application Note encapsulates the process for setting up the various HLA pieces. Note that this is a very high-level overview of what you need to setup and is meant as the roadmap. In other words, these are the 6 main steps you need to follow, however each step takes you off to a particular document, chapter or appendix that you need to reference for specific details.
Step 1
View the HLA RTI Compatibility List for ASTi supported HLA RTIs. If the RTI you want to run is not on this list contact ASTi support for further information.
Step 2
Install and activate the RTI via RMS under Network > HLA. See the Remote Management System 4 User Guide (DOC-01-TEL4-RMS-UG-4) section 6.7. for step-by-step instructions.
Step 3
Download the HLA Sample Project. This step is not required since a user can create and most likely will create a new project for a specific program. However, reviewing this example will assist during the first time you go through the setup and configuration as it provides a known working project. Note that the sample project contains a default configuration for the MAK RTI as well as the VTC RTI. RID file and other federation settings will likely require changes. See the later steps for details.
Download the HLA Sample Project (225 KB .tgz file).
Download the HLA Sample Project Customer Notes (4 KB .txt file).
Step 4
Configure the HLA Federation using the ACE Studio software. For step-by-step instructions see the ACE Studio Technical User Guide (DOC-01-TELAS-UG-4) section 8.4. HLA Configuration. Here is a high level of what is necessary:
ACE Studio Project Manager:
Step 5
In RMS under System > Status, set the Project and Layout as the default and reboot the Target. See the Remote Management System 4 User Guide (DOC-01-TEL4-RMS-UG-4) section 3.1.1. Setting a Default Project and Layout.
Step 6
You are now ready to join an HLA Federation. Typically this is performed on a host platform using the configured TCP/IP socket, however there is also a Host Emulator tool on the Target that allows you to join the Federation. This is useful in initial testing, proof-of-concept and debugging. See the Target Operation and Maintenance Manual (DOC-01-TEL4_TUG-1) section 5.3.1. for complete details.
View the HLA RTI Compatibility List for ASTi supported HLA RTIs. If the RTI you want to run is not on this list contact ASTi support for further information.
Step 2
Install and activate the RTI via RMS under Network > HLA. See the Remote Management System 4 User Guide (DOC-01-TEL4-RMS-UG-4) section 6.7. for step-by-step instructions.
Step 3
Download the HLA Sample Project. This step is not required since a user can create and most likely will create a new project for a specific program. However, reviewing this example will assist during the first time you go through the setup and configuration as it provides a known working project. Note that the sample project contains a default configuration for the MAK RTI as well as the VTC RTI. RID file and other federation settings will likely require changes. See the later steps for details.
Download the HLA Sample Project (225 KB .tgz file).
Download the HLA Sample Project Customer Notes (4 KB .txt file).
Step 4
Configure the HLA Federation using the ACE Studio software. For step-by-step instructions see the ACE Studio Technical User Guide (DOC-01-TELAS-UG-4) section 8.4. HLA Configuration. Here is a high level of what is necessary:
ACE Studio Project Manager:
- Set up the Domain with the Exercise ID = 1 and an HLA Configuration File.
- Set up the DIS Gateway.
- Add the DIS Gateway to the Layout.
- Radio name (This is the HLA Radio name.)
- Domain (Must match Domain from step 4.1 above.)
- Protocol ID
Step 5
In RMS under System > Status, set the Project and Layout as the default and reboot the Target. See the Remote Management System 4 User Guide (DOC-01-TEL4-RMS-UG-4) section 3.1.1. Setting a Default Project and Layout.
Step 6
You are now ready to join an HLA Federation. Typically this is performed on a host platform using the configured TCP/IP socket, however there is also a Host Emulator tool on the Target that allows you to join the Federation. This is useful in initial testing, proof-of-concept and debugging. See the Target Operation and Maintenance Manual (DOC-01-TEL4_TUG-1) section 5.3.1. for complete details.
