500 A Huntmar Park Drive ASTi Telestra v2.4 User Guide HLA Communications Environment Remote Management System High-Frequency (HF) Radio Server Automatic Link Establishment (ALE) Server Satellite Communications Server Panel State Machine Runtime Environment Terrain Server Document: DOC-01-TELS-UG-2 Advanced Simulation Technology inc.500A Huntmar Park Drive, Herndon, Virginia, 20170 USA Revision L.
Product Name: Telestra ASTi ASTi Telestra User Guide © Copyright ASTi 1999-2007. Restricted Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. This material may be reproduced by or for the U.S. Government pursuant to the copyright license under the clause at DFARS 252.227-7013 (1994).
TABLE OF CONTENTS Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Remote Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HLA Communications Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Model Documentation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7: RMS Software & Operation . . . . . . . . . . . . . . . . . . . . . . . . 17 DACS System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 A Tour of the RMS Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 6: RMS Frames Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 7: Sample RMS Screen Capture .
Chapter 13: Terrain Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Theory of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Figure 12: Functional Flow Diagram, ASTi Terrain Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 DACS System Requirements and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Terrain Status Window . . . . . . . . . . . . . . . .
Appendix A: Example Network Topologies . . . . . . . . . . . . . . . . . . . . 187 Figure 20: HLA/RMS Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Figure 21: Recommended Non-HLA Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Example RMS-Specific Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Figure 22: Example Installation Layout . . . . . . . . . . . . . . . . . . . .
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 1: Introduction ASTi's Telestra product line is a Linux-based platform that hosts a variety of ASTi software applications. These include the Remote Management System (RMS) software, multicast router software, HLA Communications Environment software, and Model Documentation Tool. Telestra version 2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Automatic Link Establishment (ALE) Server The ASTi ALE Server is used in conjunction with the ASTi HF Radio Propagation Server to realistically simulate the functionality of modern HF Automatic Link Establishment radios. The ALE Server allows a host computer to initiate the server with lists of radios and scan frequencies, and perform basic simulated ALE functions, such as soundings and calls.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 2: System Installation After unpacking the ASTi Telestra unit, connect power, network, keyboard and monitor to the system as described in Figure 1. Note: As technology evolves, the Telestra chassis will continue to change. Look for these objects on the rear of the chassis, and connect as appropriate.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Figure 2a. Ethernet locations on 1st gen. 1U Telestra chassis, no built-in CD-ROM onboard eth2 eth1 eth0 Host DACS HLA/RMS Figure 2b. Ethernet locations on 2nd gen. 1U Telestra chassis, built-in CD-ROM onboard eth2 eth1 Host DACS HLA/RMS eth0 Figure 2c. Ethernet locations on 3rd gen. 1U Telestra chassis, built-in CD-ROM Video onboard COM eth2 eth0 eth1 Host HLA/RMS DACS Figure 2d. Ethernet locations on 4th gen.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) onboard Network Interfaces See chassis label for ethernet assignments Figure 2e: Ethernet Port Physical Locations: 2U Telestra Chassis Telestra systems arrive with all necessary software pre-loaded. To rebuild the system’s hard disk, please see the Telestra Cold Start Procedure (DOC-01-TELS-CS-2). Turn on the Telestra system via the power switch on the front of the chassis. The system will then boot into the Linux operating system.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 3: Starting and Stopping the Telestra System Telestra runs the Linux operating system, and must be started—and more importantly shut down—in the correct manner. Starting Telestra To start the unit, apply power via the front mounted on/off switch. The unit will boot-up and run the Telestra software as background processes.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 4: System Accounts & Services Telestra System Accounts User Account ftpuser hlauser rmsuser Account Type Linux system Linux system RMS webserver Password astirules HLA!now! astirules Change Password? no yes (as hlauser) yes (only in RMS) Login no yes no Remote Login no yes no FTP yes yes no Table 2: Telestra System Accounts Note that “rmsuser” is not a Linux system user account, like the others.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 5: Initial Network Configuration Default Network Settings After initial software installation or system cold start, Telestra ethernet interface eth0 tries to obtain a network IP address and subnet mask using DHCP. In order to obtain these network settings, a DHCP server must exist on the network intended for use by eth0. If Telestra cannot contact a DHCP server using eth0, it will assign a meaningless IP address of 0.0.0.0 to that interface.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Telestra Configuration Utility Following system boot, the Telestra Configuration Utility screen will be displayed, as shown in Figure 3 below. Figure 3: Telestra Configuration Utility Press the key to move between elements (the current selection will be highlighted), or hold down the key, and press to reverse the toggle order.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Figure 4: Telestra Settings Screen Immediately after initial system installation or cold start, these settings represent eth0 information obtained by a DHCP server on the network, or will show an IP address of 0.0.0.0 with no subnet mask or gateway IP. Press the bar or key to select “OK”, or press the key to return to the main menu.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Figure 5: Change IP Settings Screen Note that this will only affect settings for ethernet card eth0. To change settings for eth1 or eth2, you must use the RMS web interface. Specifying network information on this screen will change eth0’s operational mode from “DHCP” to “fixed”. Specify the desired IP address, netmask, and gateway for the simulation network, pressing the key after each element.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 6: Telestra RMS Web Interface After Telestra’s eth0 interface is configured to the proper network settings, the system can be accessed via any standard web browser on that network through the RMS web interface. Browser Compatibility & System Configuration Tips ASTi has designed and extensively tested RMS on a number of different operating systems, using various popular web browsers to ensure compatibility.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Web Technology Security Issues The Telestra Remote Management System uses modern Internet client/server technology (like cookies and JavaScript) to extend its functionality, and enhance the quality of features offered to ASTi’s customers.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) When you specify your preferred refresh rate (in seconds), the RMS server will replace the previous cookie with another persistent cookie reflecting the new waiting period. The two persistent cookies mentioned above are the only bits of information that RMS writes to your computer’s hard disk, and are the only pieces of information that RMS can access on your computer. No information whatsoever is transmitted to ASTi, or anywhere else.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Pointing the Browser to RMS In order to access RMS using a web browser, the computer you use must be on the same network segment (LAN or WAN) as the RMS server itself. Contact your network administrator if you have any questions. Launch your web browser application. In the “Address” or “Location” field of the web browser’s display, type: http://xxx.xxx.xxx.xxx/ ... where “xxx.xxx.xxx.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) System Login: Factory Default User ID & Password The factory default user ID is: rmsuser The user ID is case-sensitive, and you cannot change it. The factory default password is: astirules The password is also case-sensitive, but you can change it through RMS’s “Preferences” interface. This procedure is outlined in Step 2 of the RMS Setup Tutorial.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 7: RMS Software & Operation DACS System Requirements To enable a DACS system for remote management via RMS, a few DACS configuration procedures must first be followed. Model Builder Software DACS systems must be running Model Builder version 4.07 or higher for remote management, although ASTi recommends running version 4.09 or higher.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The “default.cfg” File To allow remote management, the “default.cfg” file loaded by the Model Builder software should contain the following line: CELL=ON While you may find that the DACS system works with RMS without the “cell=on” directive, its inclusion is still recommended, since later releases of Model Builder may have different default settings.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The “config.sys” File The hardware settings for the DACS system’s ethernet cards are now specified in the “config.sys” file, along with a couple of other RMS-specific parameters. All of the settings listed here can be changed via RMS’ web-interface. The following information explains the individual settings; examples of properly configured “config.sys” files are included at the end of this section.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) [mbremote] This section of the “config.sys” file specifies two RMS parameters: the IP address of the managing RMS server, and which DACS directory to load on system boot. DACS system ethernet card settings are handled in the [common] section. DO NOT rename this “config.sys” heading. With the exception of those listed here, DO NOT alter any of the lines under this heading, unless specifically instructed by ASTi.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) [common] This section of “config.sys” handles the ethernet card hardware configurations for DACS systems. In Model Builder versions 4.07 and higher, the ethernet card settings listed below pertain to DACS systems running in remote mode (system default), and non-remote mode alike. Each of the parameters listed below can be changed via RMS. Remember, similar settings in the “default.cfg” file will override these “config.sys” parameters. DO NOT rename this “config.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Single Ethernet DACS “config.sys” Example In this example, the DACS system has one ethernet card. [menu] ... [mbremote] SET SYSTEM=DEFAULT SET MODELS=USER SET REMOTE=192.168.100.101 ... [common] SET LOCAL_IP=192.168.100.5 SET GATEWAY=192.168.100.100 SET SUBNET_MASK=255.255.255.0 ... Dual Ethernet DACS “config.sys” Example In this example, the DACS system has two ethernet cards; one is the host ethernet card, the other is the RMS/DIS/HLA ethernet card.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) A Tour of the RMS Layout The RMS renders information in a number of various locations. These are represented by your web browser as “frames”. Figure 6: RMS Frames Layout Header This section of the layout features the stylish ASTi logo. Click on it to access ASTi’s website, your source for the latest information about RMS and all of ASTi's products and services.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) RMS Server Frame The left-most portion of your browser displays all of the RMS servers on your network (as per their configuration settings). Move your mouse over any of the Telestra icons to view a pop-up note containing information about that individual system. Click on the icon to access that server’s RMS features. Server Info Frame This section details information about the RMS server that you are currently accessing.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Telestra Info Frame This is the main frame in which Telestra information (selected from the RMS Menu Bar) will be displayed. Here, the RMS Server Configuration screen is shown as an example. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS System Frame This section displays the DACS systems that are assigned to the RMS server that you’re accessing. DACS systems are selected for RMS monitoring via the RMS Configuration section, where their IP addresses are specified. As seen here, the system icons are accompanied by the “DACS Name” and IP address, as set up in RMS Configuration. DACS Menu Bar This frame displays your available DACS system options.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS Info Frame This is the main frame in which DACS information (selected from the DACS Menu Bar) will be displayed. Here, the DACS System Backup screen is shown as an example. All of the frames described here, when re-assembled, will look like Figure 7 below. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Figure 7: Sample RMS Screen Capture 28 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) STEP 1: Options File For new systems, ASTi installs the appropriate Telestra Options File prior to shipment. If your Telestra system does not yet have an Options File, the first thing you’ll want to do is give it one. Already got one? Skip ahead to STEP 2. In Telestra versions 2.2 and before, RMS will display an error message if it cannot locate your Options File. 1. Click on the “Click here to upload a Telestra Options File” link. A new window will pop up.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Starting in version 2.3, Telestra supports basic RMS functionality, even when no Options File is present. RMS will not present the error message shown above.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. On the main Management page, click the “Telestra Options File Management” link in the table at the top. 4. On the “Telestra Options File Management” page, click the “Start Upload” image; the upload window will then appear. Continue with upload instructions as outlined later in this step. 32 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) This is the Options File Upload window: 1. In the new window, click the “Browse...” button. This will open a standard system dialog box, asking you to locate the options file on your local computer (on the hard disk, or on a disk inserted in your computer’s floppy drive). 2. If you can’t find the file you’re looking for, click “Cancel” in the dialog box, and click the “Can’t Find It?” link in the upload window for help. 3.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) STEP 2: Change the Password The Telestra RMS comes with a pre-set User ID and Password. You can’t change the User ID, but you’ll want to change the Password to something that’s easy for you to remember. 1. Click the “Preferences” link in the RMS Menu. 2. This part requires a log in, so supply the pre-set User ID and Password (defaults are at the end of Chapter 6) in the slots provided in the pop-up window, and click “OK”. 3.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 4. Enter your new password into each of the fields provided, and click the “Change” button. That’s it! Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) STEP 3: Verify Network Setup When you first installed the Telestra system, you assigned its IP address for your network from the console (with keyboard & monitor attached to the chassis). What you didn’t see was that assigning this information actually altered the Telestra Configuration File. Now, you should verify that the network settings for Telestra are what you want. 1. Click the “Configuration” link in the RMS Menu.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. Refer to the image below. First, note the location of the RMS Help icons. Clicking any of these icons will launch a remote window containing detailed information about that specific setting. The “Auto-Discover Mode” and “Auto-Discover Address” are already configured (other settings may also be pre-configured) with default values. If you want to change any of the Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) values shown here, click the “Edit Settings” image. This will launch the RMS Configuration Edit Window. An example is shown here. Note that you can delete an RMS Configuration setting by clicking the checkbox next to its position in the list. After making your changes, click the “Add Changes to Config. 38 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Buffer” button. This will take you to a screen that displays the contents of the Configuration Buffer. An example is shown here. Making changes to certain settings in the Telestra Configuration file, because of their use in networking and/or other Telestra software, will require a software restart, or even a system reboot.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Any time there are pending changes contained in the Configuration Buffer, a notice will be displayed on the screens of the Configuration section. Click on the link to launch the Configuration Buffer window. 4. Okay, back to business. Remember the “Network” screen of the RMS Configuration section? Note the red arrow pointing to “ETH0”. Click this link to access the network settings for the ethernet card designated “eth0” by the Telestra system.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Again, note the locations of the RMS Help icons. Change the settings here in exactly the same way as previously described. Don’t forget to commit your changes in the Configuration Buffer when you’re ready. For HLA applications, use the links for “ETH1” and “ETH2” to configure those interfaces to match your DACS network and Host network, respectively. Non-HLA applications usually do not require changing eth1 or eth2 from their default settings.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) STEP 4: Setting Up DACS Systems One of the primary functions of the Telestra Remote Management System is to serve as a “DACS Portal” through which the system administrator can access DACS systems on the network. In order to do so, however, you have to tell the DACS system that it’s going to be remotely managed, then you have to tell RMS to look for it. 1. Make sure the DACS is configured properly, powered on, and hooked up to the network.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 4. Since there are no DACS systems configured yet, you will see only that you can add one. Click on the “DACS1” link to continue. 5. This is the DACS1 Configuration screen. Click on the “Edit Settings” image to proceed; the Edit window will pop up. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 6. This is the DACS1 Configuration Edit window. In order for RMS to recognize the DACS system on the network, you must at least specify the DACS system’s IP address here. For DACS systems with more than one ethernet card, specify the IP address of that system’s DIS interface, not the host interface. Since the DACS Name will be displayed in the DACS System frame later, ASTi recommends that you fill in this setting, as well.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) STEP 5: Adding RIUs For the purposes of the example, let’s assume that the DACS system you added in Step 4 is equipped with a TDM DSP card. Let’s also assume that there are going to be three (3) RIUs connected to the DACS via the TDM ring, and we want to assign descriptions to each of them, to help us keep them straight.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. This is the DACS1 Configuration screen. Note the links to the DSPs. Any DACS can have up to 3 DSPs, although you are more likely to have only one or two. The RMS Configuration section will always display 3 DSPs on any DACS Configuration screen, in order to handle the maximum “3 DSPs” scenario. In our example, DACS1 only has one DSP, and it’s a TDM card. Click on “DSP1” to go to the RIU Configuration screen.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 4. This is the DACS1/DSP1/RIU Configuration screen. For any single TDM card, you can have a total of 14 RIUs on its ring, and each RIU must have a unique hardware address, as set via a rotary switch on the RIU itself. The list shown here reflects that maximum limit. Please note: The RIU designations here are tied directly to the RIU’s physical address (RIU1 has hardware address “1”, RIU10 has hardware address “A”, and so on).
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 5. This is the DACS1/DSP1/RIU6 Configuration screen. Click the “Edit Settings” image to launch the Edit Configuration window. 6. This is the DACS1/DSP1/RIU6 Edit window. Note that the RIU Address setting is pre-configured for you, and you cannot change it. Enter the appropriate description, and click the “Add Changes to Config. Buffer” button. 48 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Please note: Adding RIUs to any DACS’ DSP does not require a software restart or reboot, so there is no waiting period for you. You can commit changes to the RMS Configuration File at will, or add numerous RIUs to the buffer, and commit their settings all at once. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) STEP 6: Finding DACS Systems & RIUs In Step 4, we added a DACS; in Step 5, we added one of the three RIUs that will be connected to the DACS via its TDM card. Here, we’ll locate the DACS over the network using RMS, and add descriptions to the other two RIUs. 1. Click the “Find DACS” link in the RMS Menu Bar. After a few seconds, the DACS Systems frame will appear, displaying the DACS system we added previously. 2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. This is the DACS Information screen. In the DACS Systems frame, note that the DACS system you just selected is now surrounded by a red box. This visual indication is applied to any DACS system you select from the DACS Systems frame. To view information about the system’s DSP card(s), you can either click the “Find System DSPs/RIUs” image in the DACS Info Frame, or click the “Find DSPs” option in the DACS Menu Bar.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 4. The RMS system will locate the DACS system’s DSPs, and display the DSP/RIU Info screen. The RIU we added in Step 5 with the physical address “6” appears to be properly connected to our TDM ring, as do two other RIUs. Click any of the RIU icons to view specific information about that RIU. An RIU does not have to be set up in the RMS Configuration file to appear on this page.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 5. The RMS Configuration Edit window will then pop up. As in the RMS Configuration section, the RIU Address is pre-configured, and you cannot change it. Enter the desired description, and click the “Add Changes to Config. Buffer” button. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) If you choose to “Commit Changes Later...” in the Configuration Buffer window, RMS will alert you to pending changes, again, just as in the Configuration section. Click the “Changes in Buffer” link to launch the Configuration Buffer window, and commit the changes. 6. The RIU you just added “from the field” now appears just as the RIU we added directly from the RMS Configuration section. Click the “add” link next to the last RIU to configure its description.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Again, click any of the RIU icons to view specific information about that RIU. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) STEP 7: Using the Model Builder Virtual Screen In Step 4, you learned how to successfully set up a DACS system for use with RMS. Once a DACS system has been added to the RMS Configuration File, you can access that DACS’ Model Builder software over the network using the Model Builder Virtual Screen (MBVS) functionality built into Telestra. Be sure to read the warning that concludes this step. 1.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Enter the IP addresses for the DACS systems you wish to access using MBVS in the slots provided, then click the “Make Changes” button. Please note: you can only set up IP addresses for DACS systems that have previously been added to the RMS Configuration File, as in Step 4.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 7. Now, you’re viewing Linux Virtual Console 3. Press the space bar on your keyboard to enter the Model Builder Virtual Screens system. 58 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 8. This is the Model Builder Virtual Screen system front page: Now, press ALT+F1 to access the Model Builder software for the DACS system that you specified in RMS as “Virtual Screen 1”. Through the Model Builder Virtual Screens, you can do everything in the Model Builder software, as if you’d connected a monitor and keyboard directly to the DACS system. All of the keyboard commands and shortcuts are the same.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 8: HLA Software & Operation DACS System Requirements Note: This guide is written with the assumption that the user is familiar with DACS operation, and DIS Radios in the DACS. The changes to the DACS Model Builder application are relatively straightforward to allow it to function in HLA mode. Note that all previous functionality in nonnetworked and DIS operational modes are retained, and are available in HLA mode.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) World Position objects have been changed to include the option of setting the Entity ID type to “HLA”. This is achieved using the “Entity ID” field and incrementing through the options. On selecting the “HLA” type, the line above changes from “Exercise No” to become “Federation No”. Federation numbers 1-8 are reserved for RTI communication. Please see ASTi Application Note 54: “Using Telestra Backchannels” (http://www.asti-usa.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) HLA Setup Tutorial As of Telestra version 2.0, HLA Communications Environment setup and configuration is handled through the RMS web interface. User manipulation of HLA settings is performed in the same manner as all other Configuration actions, outlined in the RMS Setup Tutorial, above. IMPORTANT: Other than uploading and installing an RTI, changes to all other HLA Configuration settings will require a restart of Telestra’s HLA Communications software.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 2. Then, click the “HLA Settings” link in the Online Configuration table. This will display the main HLA Configuration screen, shown below: Note the presence of the “HLA” link in the regular Configuration table (black arrow). This link will be shown on every Configuration screen if the system has an HLA-enabled Options File. The main HLA Configuration screen provides links to all HLA-specific areas.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. This is the RTI Upload/Install screen: Click the “Browse...” button to locate the desired RTI’s archive file on your local system. RTI archive files usually end in “.tar.gz”, “.tgz”, or “.sh” file extensions. ASTi’s HLA Communications Environment supports RTIs downloaded from DMSO’s (http:// www.dmso.mil/), MÄK Technologies (http://www.mak.com/), and VTC (http:// www.virtc.com/) websites.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 2: Configuring the RTI 1. Immediately after upload/installation of an RTI file, you’ll be transferred to the “Configure Current RTI” screen. This screen is also accessible by clicking on the “Configure Current RTI” link on the main HLA Configuration screen: 2. This is the “Configure Current RTI” screen: To change the RTI used by the HLA Communications Environment, click the “Edit Settings” image to launch the RTI Configuration Edit window.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. Here’s the RTI Configuration Edit window: Select the RTI you wish to use from the pull-down menu labeled “Active RTI” (red arrow). Note that a License Server Name and License Server IP address (black arrows) are required when using MÄK or VTC RTIs. Leave these fields blank when using a DMSO RTI. When you are done, click the “Add Changes to Config.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 3: Ethernet Remote Control Interfaces & DACS Settings The Remote Control Interface status (on/off) can be changed for all three ethernet interfaces at the same time by clicking the “Ethernet Remote Control Interfaces” link from the main HLA Configuration screen (red arrow). For each DACS system to take part in the HLA application (up to four DACS total), specify its Host Server IP address, Tactical Data Link Server IP address and Terrain Server IP address.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 4: HLA File Management Before you can configure individual Federates, the necessary RID, FED and convert files must first be transferred to the Telestra system. 1. On the main HLA Configuration screen, click the “Click here” link in the HLA File Management table. 68 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 2. That will take you to the HLA File Management screen: The HLA File Management screen is where you populate the Telestra filesystem with RID, FED and convert files that you’ll assign to individual Federates later. FED and convert files share a directory on Telestra (/usr/local/asti/fed), whereas RID files have their own directory (/usr/local/asti/rid). To upload files from your local system to Telestra, click the “Browse...
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. This step is required for customers with Telestra versions 2.1 through 2.3 who are using MÄK RTI version 1.3.7 or higher with an rtiexec process. As of Telestra release version 2.4, this workaround is no longer necessary; continue with “Step 5: Configuring Federates”, next page. The rtiexec process of MÄK RTI version 2.0 or higher looks for the FED file first in the current directory, and then in the directory specified by the RTI_CONFIG environment variable.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 5: Configuring Federates 1. Click the Federate ID in the Federate Settings table in the HLA Configuration screen. 2. This will open the Federate Settings screen for whichever Federate you selected. In this example, the “FED5” link was clicked. To change the settings for this Federate, click the “Edit Settings” image; this will open the Federate Edit window. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. This is the Federate Edit window. Configuring Federates differs slightly from the standard configuration procedure you’ve become used to. Note the “pick” links next to the RID File, Fed File, and Convert File settings (red arrows). Click on any “pick” link to launch a separate window that lists the existing files in that particular directory. For this example, we’ll click the “pick” link for Fed File.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 4. This pops up the list window. Simply click the name of the desired file in the list window. The list window will then close, and the Edit Federate form will update to reflect your choice. VERY IMPORTANT: If you’re going to use the pop-up list windows to select your RID, FED, and Convert files, the Federate Edit form has been designed to preserve your selections when it updates (after you click a file name from the list window).
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 6: Testing the HLA Software The HLA software that is run on the Telestra system is an HLA federate. This federate software, when combined with the DACS audio routing and processing node, implements a full radio simulation environment, based upon the data structures defined in the ASTi Radio SOM. From power on, an HLA-enabled Telestra system will start the Telestra federate application as a background process.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The MÄK RTI may also use an rtiexec application, although this is not necessary. To run the rtiexec application for the MÄK RTI, go the MÄK RTI directory (in /opt/rti) and type the following commands: cd bin ./rtiexec To stop the RTI, type CTRL+C. Please refer to the MÄK RTI Reference Manual for more information on the rtiexec application. The MÄK RTI requires a license server to run. See the MÄK documentation for more info.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Then, enter the command “join”: Wait for the federate software to return “JOIN OK” to indicate a successful join operation. If the software returns “JOIN FAIL”, double check the network configuration on each machine. 76 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The rtiexec should then indicate successful federate initialization: At this point, there is an “asti” Federation with two Federates joined. Note that the Federate name for each Telestra system was generated based on the Hostname and IP address of the individual machine. In order to properly destroy the federation, you must: • Resign each Federate by typing “resign” at the Telestra > prompt on both Telestra systems. • Stop the rtiexec process using CTRL+C.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The HLA Remote Control Interface The Telestra HLA federate software runs in the background upon system startup and may be accessed only through the remote control interface. The Telestra federate no longer runs on the first console. The user accesses the remote control interface through a TCP/IP connection to the appropriate control port. Each federate has its own control port as specified in RMS’ HLA Configuration section.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Host Emulation Utility The host emulation program (hostemu) that is shipped with Telestra HLA software allows the user to test the remote interface and verify that it is working correctly. To run the host emulator on the local platform, log in as “hlauser” on console 2, 4, 5, or 6 and enter the command: hostemu.pyc at the prompt. The specifies which of the eight Telestra federates will be controlled via this connection.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Remote Control Interface Commands and Responses The Telestra federate expects all command lines to be terminated with a newline character (“\n” to you C programmers). If two command lines come at once, they will be executed in order. A command will not be executed until the final newline (\n) is received. Commands are not case-sensitive; however, some data for the commands may be case-sensitive (for example, the fed file name must be in the correct case).
ASTi Telestra User Guide (Ver. 2, Rev. L.1) JOIN This command directs the Telestra federate to join the federation with the name specified. If no name is given, it will use the federation name specified for that federate in the Telestra Configuration file. If the federate is already joined to a federation, it will resign and attempt to join again. It will do this even if the federation name is unchanged.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) OBJECT When called with no arguments, the OBJECT command returns a list of objects that the Telestra federate has detected. The Telestra federate subscribes to Receiver, Transmitter, and Entity objects. The name, RTI handle, and type of the object is returned. Additionally, an object is designated as “local” if it is owned by the Telestra federate in question (for transmitters and receivers).
ASTi Telestra User Guide (Ver. 2, Rev. L.1) NAME When called with no parameters, the NAME command simply returns the names of the federate, the federation, the .fed file, the .rid file, and the conversion file. A typical response to this command is shown here: FEDERATION Federation1 FEDERATE Telestra1 FEDFILE /usr/local/asti/fed/asti3_2.fed RIDFILE /usr/local/asti/rid/rid1.mtl CONVERT /usr/local/asti/fed/convert3_2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) ACTIVITY This command returns activity counters from the Telestra system. If accessing the remote control interface through the host emulator utility on Telestra, this command may be initiated by simply pressing the key.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Backchannel (Telestra <=> DACS) tracks activity over the backchannel between the Telestra and the DACS. The Tx/Rx counters increment as the Telestra receives Tx and Rx PDUs from the DACS, or sends Tx and Rx PDUs to the DACS on the backchannel. The Audio counters increment as the Telestra receives signal PDUs from the DACS, or sends signal PDUs to the DACS on the backchannel.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Debugging the Remote Control Interface Debug messages are printed to the file /var/log/hla.messages. The HLA log file is also available for online viewing and downloading in the Management section of the RMS web interface. The level of detail within these messages may be set by entering the following command: debug from within the federate. The debug level parameter determines which combination of debug messages are printed to the file.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) HLA-Specific System File Structure When the user logs onto the Telestra system as “hlauser”, they are in the hlauser home directory (/home/hlauser). The following list describes the contents of the subdirectories in the latest version of Telestra. With the exception of the ~/run directory described below, the RMS web interface offers the user access to these locations through any standard web browser over the network (RMS login/authentication required).
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 9: Using the Model Documentation Tool The Telestra Model Documentation tool allows users to generate PDF documents from a model’s XML file, which is constructed automatically by the Model Builder software running on the DACS. The Model Documentation tool requires that candidate XML files be constructed by Model Builder version 4.09 and later.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Selecting an XML File Directly from a DACS In the DACS single-file transfer section of RMS, any XML file listed in a directory is tagged with a link to the Model Documentation tool. Note that this link will not be provided if the Model Documentation tool is processing an XML file at the time of viewing. Clicking on the “DOCTOOL” link beside an XML file will take you directly to the Document Information screen.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The Document Information Screen From this screen, the procedure is the same, regardless of how you got here. Provide document information in the slots provided. This information will be used on the cover page of the PDF, and in the header and footer of every page therein. Remember to verify whether you want to generate only the model’s ICD, or the full documentation (which takes longer). When ready, click the “Generate Model PDF” button.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The Progress screen will keep you informed as the Model Documentation tool processes the XML file and constructs the PDF report. The Progress screen will automatically refresh its information every ten (10) seconds. IMPORTANT: The “Parsing XML File” and “Building PDF File” steps will take the longest to complete. While it may appear that the Model Documentation Tool is not actually doing anything (e.g.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) When Model Document PDF generation is complete, RMS will display the PDF file management screen where you can download Model Document PDFs. All generated PDFs will remain on the Telestra system for later download. You can delete PDF files from this screen. 92 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 10: HF Radio Propagation Server The ASTi HF Server provides real-time, high-fidelity modeling of HF radios using the Model Builder virtual radio environment. The HF Server computes propagation effects between virtual radios, taking into account such things as transmitter-receiver global position, season, time of day (day-night terminator), and solar activity. Basic operation is as follows: 1.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS System Requirements There are two steps involved in configuring DACS systems to use the HF Server. • Modify the Model Builder configuration file (usually “default.cfg”) to include the statements detailed below. • Configure the radio modes within Model Builder for the radios that will use the HF Server. It is important to note that, to the Model Builder software, the HF Server operates in the same fashion as a terrain database server.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) terrain:rate_divider = xx This statement controls the maximum rate at which requests will be sent out, as a fraction of the master model rate. For example, if the model rate is 50 Hz, and rate_divider is set to 10, then the maximum rate at which the DACS will send requests to the HF Server is 5 Hz. See the Model Builder documentation (DOC-01-MB-RM-4) for more information about the master model rate.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Configuring Radios within Model Builder Configuring radios within Model Builder to use the HF Server is straightforward. Model Builder allows configuration of radios to either “Line-Of-Sight” or “Over-The-Horizon” radio mode. When set to “Over-The-Horizon”, this single parameter identifies the radio transceiver as an HF radio. Other radio parameters such as Transmit Power, Antenna Gain, modulation type, etc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) HF Server Host Interface To properly simulate solar activity and seasonal/circadian effects on the ionosphere—and HF radio signal propagation—the HF Server requires that the Smoothed Sunspot Number (SSN) and Time-Of-Day offset be provided by the simulation host computer. Typical values of the Smoothed Sunspot Number (SSN) range from 0 to 250, depending on past and current sunspot activity. The default value for this variable is 100.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) HF Server Utilities in RMS To access HF Server utilities via Telestra’s RMS web-based interface, click the “Servers” option in the RMS Menu. This menu option will only be available if either the HF or Satcom server software is installed on the Telestra platform. From the Servers page, click the “HF Server” link. This is the HF Server Information page: 98 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 1. Enter the exercise ID in the slot provided, and click the “Poll HF Server” button to perform a Quick Poll. This will ensure that the HF Server is operating, and will provide exercise-specific information, as set by the simulation host computer. The Quick Poll also returns server packet counters. An example of Quick Poll results is shown here. 2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) the altitudes, and click the “Poll HF Server” button to instantiate the query. The Complex Poll returns the total pathloss in dB between the specified radios in addition to the information returned by a Simple Poll. An example Complex Poll results screen is shown here: 3. View or download the Telestra server log by clicking the appropriate link from the HF Server Information page.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 11: ALE Server The ASTi ALE Server is used in conjunction with the ASTi HF Radio Propagation Server detailed in Chapter 10 to realistically simulate the functionality of modern HF Automatic Link Establishment radios. The ALE Server allows a host computer to initiate the server with lists of radios and scan frequencies, and perform basic simulated ALE functions, such as soundings and calls.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) a. The radios scan list includes the call frequency b. The radio is currently in ALE Scanning mode c. The radio is on the same DIS exercise ID as the calling radio 4. For those radios that meet the above three criteria, the ALE Server makes requests to the HF Server to compute an estimate of the Link Quality Assessment number. The LQA number is based on signal-to-noise ratio at the receiving radio, and is a number between 0 and 255. 5.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) ALE Server Utilities in RMS To access the ALE Server utilities via Telestra’s RMS web-based interface, click the “Servers” option in the RMS Menu. Note that this menu option will only be available if the HF, SATCOM, or ALE server software is installed on the Telestra platform. From the Servers page, click the “ALE Server” link. Counters showing the number of valid DIS radios set up by the host computer, number of ALE responses, etc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 12: Satellite Communications Server ASTi’s Telestra Satcom Server software, in combination with ASTi simulated radio objects, extends the simulated radio environment to include the effects of voice communications over satellite links.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Theory of Operation Functional system components include: 1. Uplink Transmitter. An ASTi simulated radio, configured to operate as a satellite transmitter. 2. Satcom Server. A Telestra uplink receiver, simulated satellite effects (voice delay), and downlink transmitter. 3. Downlink Receiver. An ASTi simulated radio, configured to operate as a satellite receiver.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Satcom Server Configuration 1. Each end-to-end satcom link is realized over a pair of unique uplink and downlink frequencies, through a single DIS port.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 5. The Satcom Server automatically instantiates a Downlink Transmitter. • The transmitter’s downlink frequency is set to a value calculated by the Satcom Server. a. The calculated value is based on: the tuned frequency of the originating Model Builder uplink transmitter and the configured Satcom Server uplink and downlink frequencies. b.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS System Requirements & Configuration DACS systems for use with the Satcom Server must be running Model Builder software version 4.09a or later, and be configured for RMS use (see Chapter 7). DACS Communications Model Precepts Standard RMS configuration commands are required in the “config.sys” and “default.cfg” files in order for the DACS to communicate with RMS. Additionally, communication with the Satcom Server requires these “default.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Communications Model Configuration Three parameters must be configured within the communications custom model: 1. Transmit Frequency: reference ASTi Radio Object, Page 2 of 9. • The value in the TxTune Freq control field must be within the Satcom Server’s range of uplink frequencies. • The Satcom Server range of uplink frequencies is set using the RMS configuration utility. See Chapter 16 for guidance on Satcom Server configuration. 2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. Radio Mode: reference ASTi Radio Object, Page 3 of 9. • The value in the Power / Mode field sets the operating mode of the radio. • An ASTi radio object can operate in up to one of 16 possible modes. Figure 11 shows the table that is used to set up Modes 1 through 8. • The Power / Mode value corresponds to modes in the table.
ASTi Telestra User Guide (Ver. 2, Rev. L.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Satcom Server Utilities in RMS To access Satcom Server utilities via Telestra’s RMS web-based interface, click the “Servers” option in the RMS Menu. This menu option will only be available if either the HF or Satcom server software is installed on the Telestra platform. From the Servers page, click the “Satcom Server” link. This is the Satcom Server Information page: 1.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. The Poll Server line provides three views of the local Satcom Server query: “Status”, “Counters”, and “Delays”. The Satellite DIS ID, Host Interface and Port number must be configured to enable server polling. Set these parameters through the standard RMS configuration utility. See also “RMS Setup Tutorial” in Chapter 7 for more information. a.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Satellite Tx/Rx Example Values are shown in MHz for clarity; Satcom settings should be specified in Hz. For the purposes of this example, assume the following settings: • Uplink Freq. = 300.000 MHz • Passband Width = 0.500 MHz • Downlink Freq. = 200.000 MHz Based on the Uplink Frequency and the Passband Width, the Satcom Server will accept transmissions from any DIS radio transmitting at any frequency between 300.000 and 300.500 MHz, inclusive.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 13: Terrain Server ASTi's Terrain Server software applies occulting and degradation effects to communication paths in the Model Builder radio environment. The Terrain Server interacts with Model Builder via Model Builder’s existing terrain database interface. For detailed information about this interface, please refer to Application Note 16: Using the Terrain Database Interface.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The flow diagram below describes the internal operation of the Terrain Server and its response to external inputs. The flow diagram uses the following conventions: • Numbers reference steps in the description. • Solid lines signify control and configuration routes. • For clarity, only one receiver-transmitter pair is described. The Terrain Server can process multiple receiver-transmitter links.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS System Requirements and Configuration To configure the DACS systems to use the Terrain Server, the terrain database interface must activated and configured in the Model Builder configuration file. By default, this file is located at C:\mbuilder\user\models\default.cfg and will hereafter be referred to as “default.cfg” for clarity. Note that Model Builder “default.cfg” commands and arguments are not case-sensitive.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Optional Configuration Commands The following commands allow the user to customize the terrain interface on the DACS but are not required. terrain:pdus_packet = x This command specifies the number of PDUs to be sent per UDP packet. The valid range of values is from 1 to 16. This effectively sets the maximum number of path loss information requests per packet. If more PDUs are ready in a frame than the number set, PDUs will be distributed in subsequent packets.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Terrain Status Window Model Builder provides a status window (shown below) for monitoring the terrain interface. The fields in the top portion of this window reflect the values network settings and terrain interface configuration parameters that were loaded from the configuration file. These values may be changed through this window; however, these changes are in effect only for the current session. For permanent changes, values should be changed in “default.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Terrain Server Utilities in RMS To access Terrain Server utilities via Telestra’s RMS web-based interface, click the “Servers” option in the RMS Menu. This menu option will only be available if server software (Terrain, HF, etc.) is installed on the Telestra platform. From the Servers page, click the “Terrain Server” link.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) The Terrain Poll returns the total pathloss in dB between the specified radios, and provides a twodimensional cross-section diagram of the intervening terrain profile: Note that the pathloss presented in RMS (in dB) is derived directly from the pathloss factor that would be inserted in the DACS’ terrain query PDU.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Installing Custom DTED Files To use a higher-fidelity terrain database, you must install that data from a CD-ROM using the RMS interface. 1. Click the “Install DTED Files” link in the Custom Data section of the Terrain server page: 2. Insert the CD-ROM containing the custom data to be installed in the drive tray of the Telestra system. DO NOT insert the CD into your local computer. After the drive has closed completely, click the “Read CD Contents” button.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 3. The Telestra system will then locate all DTED files on the CD-ROM. The next screen reports the number of DTED files found, and allows you to review them prior to installation. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 4. Click the “review the DTED contents” link to review the files to be installed in a new browser window. 124 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 5. Close the pop-up window to continue. To begin the installation, click the “Install DTED Info from CD” button in the original window. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 6. During the installation phase, RMS will display the total number of files to be installed, the number of files processed, percent and status indicators. It is imperative that the installation process not be interrupted for any reason. 126 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) 7. RMS will indicate that the installation is complete once all the DTED files have been processed. If you wish to install more data from another CD, click the link at the bottom of the screen and repeat the installation process as needed. Otherwise, click the “Terrain Home” link to return to the main page. Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Working with Custom DTED Files Back on the main screen, RMS will display the number of custom data files installed on the system. To review the coordinates and DTED level(s) of installed files, click the “View Files” link. By default, RMS will not display the DTED level of the installed files. To review the files’ DTED level, click the “Show Data Level” link. 128 Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) RMS may take a moment before displaying the DTED level information, as it must open and inspect each custom file to retrieve this information. Whenever custom DTED files are installed on the Telestra system, they can be “activated” or “deactivated” through RMS. After installation, Telestra “activates” the new data by default.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Note that when “inactive”, the previously-installed DTED files will still exist on the Telestra system, but they will not be used during terrain queries, regardless of their geographical coverage. While “inactive” all Terrain queries will use ASTi’s default DTED level 0 information. To begin using the custom data again, simply click the “Activate” link on the main page, and confirm your action on the subsequent screen.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Polling the Terrain server using custom data is identical to the procedure described on pp.120121. Make sure to include geodetic coordinates that fall within the geographical area covered by your custom data. Using the same coordinates, altitudes and frequency, a Terrain query using higher-fidelity data will yield more accurate results. Here are the results of the previous query, using DTED level 1 data: Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Note that, due to the higher-fidelity terrain database in use, the cross-section of the terrain profile provides more individual points, and is more detailed. To completely remove all custom-installed DTED files, click the “Delete All” link on the Terrain server page. You will be asked to confirm your action on the subsequent page. This will delete all custom files, and return the Terrain server to its default state, using DTED level 0 for all Terrain queries.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 14: Panel State Machine Runtime Environment ASTi’s Panel State Machine Runtime Environment (PSMRE) represents the phase 1 launch of the next generation ASTi Model Builder Visual (MBV) software product. Utilizing a highly-innovative distributed synchronous realtime operating system, MBV opens the door to a vastly flexible modeling environment.
ASTi Telestra User Guide (Ver. 2, Rev. L.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Theory of Operation At the simplest level, a single state machine instance will provide the control and logical operation to drive a single crew control panel. Typically, such a state machine would support three interfaces: one to the panel hardware itself (via an ASTi USB interface module), one to the simulation host computer (providing power status, for example), and one to an ASTi DACS platform providing the audio routing and processing capability.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS System Requirements & Configuration The Model Builder Application Configuration File (usually “default.cfg”) must contain the following commands: cell=on Telestra=on The System Configuration File “config.sys” must contain the following commands: SET TELESTRA=xxx.xxx.xxx.xxx ... where xxx.xxx.xxx.xxx is the Ethernet IP address of the Telestra system running the PSMRE for that particular DACS system.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) State Machine Utilities in RMS All Telestra system setup and configuration is performed via the ASTi RMS interface from a standard web-browser. Configuring Telestra State Machines for use requires three steps: 1. Upload and install a state machine package. 2. Specify DACS hardware that will utilize Telestra State Machines. 3. Specify USB interface device serial numbers that will be used to connect I/O devices (e.g., panels) to Telestra systems.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) This is the State Machine Administration page: 1. State machines are supplied by ASTi as a TGZ compressed file which must be uploaded to the Telestra before being run. Note: In some cases, a state machine and associated software may be supplied pre-loaded on some Telestra units. If a state machine package is already installed and running on the Telestra platform, details of the package will be displayed at the top of this screen. 2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) i. On the next screen, click the “Browse” button to locate the desired State Machine package on the local system. Then, click the “Upload SM Module Package” button to upload the file. ii. Information about all packages on the Telestra system will then be displayed for your review. The “Install” row includes information about the package just uploaded to Telestra. The “Preserve” row shows which package is currently installed.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Telestra system altogether, as the “Preserve” package will then be the un-installation target package. After new package installation, the running of modules in the “Remove” package will require that package to be uploaded anew. Click any of the package’s file name to download that package to the local system. Successful installation of a new package will be reflected at the top of the State Machine Administration page, section 1 here: b.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) erase the currently-installed package from the system, and install the package listed on the “Revert To” line. Use of the currently-installed package will require that package to be uploaded again at a later time. After package reversion, the only package that will exist on the Telestra system is that which was reverted to. Use of any other package (new or old) will require a file upload. 3.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Click the “Counters” link for any state machine to view cell counters for that particular state machine. b. View or download the Telestra State Machine log by clicking the appropriate link from the State Machine Administration page. This log will contain entries from the State Machine Modules, as well as other kernel-specific messages. c. Click the “Restart State Machines” link to force Telestra to stop currently-running state machines, and reload them anew. 4.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) This will display the IP addresses used in the model development as labels, and show any applied ‘alias’ to this label. From release, the IP address shown as the alias will be that used while the model was in development. The label field will usually be a meaningful name, such as “Simulation_Host” or similar. Click the “Edit Settings” button to enter the desired IP address.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 15: USB I/O Device Software Configuration Software Configuration See your system documentation for USB I/O device hardware specification, installation procedures, etc. The following software configuration is also included in that document.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Click any green or yellow USB icon on this page to view device-specific information. 4 Because the hardware configuration and mapping file is generated by the state machine model, you cannot add new USB I/O device configurations to it. You can only edit the USB I/O device serial number for pre-existing configurations, such as that for “Pilot” or “Copilot”. Click the “Edit” link for any USB I/O device to change its configuration in the hardware mapping file.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 16: Telestra Configuration Parameters All of Telestra’s RMS and HLA configuration can be performed via the web-browser interface, with the exception of initial network setup. The Telestra Configuration File is a text file that specifies the Telestra system’s overall setup, as well as DACS- and HLA-specific parameters. The Satellite Communications Server settings are also specified here.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Basic Settings Base: Description Class: Recommended The RMS system allows you to enter a short description for each RMS server on the network. This will help you (and others) differentiate between machines based on something other than their IP addresses alone. This description will be displayed in the pop-up note when a user moves their mouse over the RMS server's icon in the “RMS Servers” frame at left.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS Settings DACS: IP Address Class: Required This setting is required for each DACS system you wish to access via the Telestra RMS server. This is the IP address for a specific DACS system on the network. Each DACS system will have at least one network interface (but can have more), and each card will have its own IP address. For DACS with only one ethernet card, this is the IP address of that single card.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS: RIU Address Class: Convenience, Recommended This is the physical address for the RIU, as set via the blue hardware switch on the RIU itself. When adding RIUs to a DACS in the RMS configuration, click the number of the RIU corresponding to its hardware address, as this setting is NOT user-configurable, per se.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS Routing Settings These settings are no longer HLA-specific, as in Telestra/RMS release 2.0. Routing: DACS Host IP Address This is the IP address of the host computer associated with a DACS system. Contact your network administrator for more information. Routing: DACS Terrain Server IP Address This is the IP address of the server that supplies terrain data to a DACS system. This may or may not be different than the DACS host computer IP.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Network Settings Network: IP Address Class: Required This setting is required for network interface eth0 on the system for proper RMS server operation. Class: Required, Conditional For Telestra systems running in HLA mode, IP addresses for network interfaces eth1 and eth2 are also required. This is the IP address for a network interface card on the Telestra system. Each Telestra system will have at least one network interface, but may have more.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Network: Subnet Mask Class: Required This setting is required for network interface eth0 on the system for proper RMS server operation. Class: Required, Conditional For Telestra systems running in HLA mode, subnet masks for network interfaces eth1 and eth2 are also required. The subnet mask determines which network interfaces (e.g. ethernet cards) on a TCP/IP network can communicate, based on their IP addresses.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Network: Auto-Discover Address Class: Required, Conditional This setting is sometimes required for proper RMS server operation. When is it required? Only when the system’s Auto-Discover Mode is set to “Multicast”. This setting is user-configurable only if you have Auto-Discover Mode set to “Multicast”, and is also referred to as the “Multicast Group Address”. 1.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Network: Hostname Class: Convenience This field is not required for the RMS server to function properly. For use on networks utilizing the Domain Name System (DNS). Contact your network administrator to see if the network is configured to use DNS. The machine’s “hostname” is the first part of its DNS address. For example, in “www.astiusa.com”, “www” is the hostname.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) HLA Settings HLA: Active RTI The “Active RTI” setting selects which runtime libraries to use for HLA applications. If the desired RTI is not listed, you must first upload its archive. Note: If you are using libraries from MÄK or VTC, you must also specify a license server hostname to use. The license server IP address is optional, depending on your network setup. If your network supports DNS, a license server IP address is not necessary.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) HLA: Federate RID File The RID file provides control parameters for the RTI software. The specified RID file must be located in the “/usr/local/asti/rid” directory at runtime. You can select a RID file that was previously uploaded to the system by clicking the “pick” link next to the filename slot in the edit form. You can also simply type in the desired filename; this is helpful if you know the RID file name, but have not yet uploaded the RID file itself.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) HLA: Federate Control Port This field specifies the TCP/IP port number for the Remote Control Interface for the Telestra federate software. All control of the Federate occurs through this port. The Remote Control Interfaces must be enabled for this to work properly. HLA: Federate Audio Backchannel If this is set to “on”, the Telestra Federate sends audio over the HLA physical network, but bypasses the RTI.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Satellite Communications Server Settings Satcom: Number of Transponder Channels This setting specifies the maximum number of full-duplex connections that the Satcom server will establish between DIS transmitters and receivers. One channel is created for each DIS transmitter that successfully connects to the satellite server. Acceptable values are between 1 to 255 channels. This setting is not required for proper Satcom server operation, but is recommended.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Satcom: Modal Delay The satellite communications server supports seven radio modes, each with an individual delay (in milliseconds). Radio communication through the satellite transponder will be delayed by the amount of time specified for the corresponding mode. Defaults are as follows: Mode 1: 0 ms Mode 2: 1000 ms Mode 3: 9000 ms Mode 4: 0 ms Mode 5: 1000 ms Mode 6: 3000 ms Mode 7: 3000 ms The Fixed Delay (Override) parameter will override all Modal Delays.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Satcom: Transmit Port Specify the network port to use for sending UDP traffic. Acceptable values are from 1025 to 65535. The default is 23501. Satcom: Satellite DIS ID This parameter specifies the base DIS identifier for the satellite transponder in the DIS environment. It should be adhere to the standard site.host.entity.radio DIS format. The Satellite DIS ID, along with Uplink Freq., Passband Width, and Downlink Freq.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Satcom: DIS Network Port For each DIS Network, specify an IP Address and Port to use for DIS UDP socket creation. Since all DIS traffic uses the same port number to communicate between entities, you should enter the same port number for the Satcom channel as that used by the DACS systems for DIS radio communications.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Time (NTP) Server Settings Time: Server IP Address Telestra v.2.4 and later only. Some networks use an NTP (time) server to synchronize the time-of-day between separate systems. If your network features an NTP server, specify its IP address here. If your network also uses DNS, you may set the Time: Server Hostname instead of this IP address. Time: Server Hostname Telestra v.2.4 and later only.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Time: Maximum Poll Interval Telestra v.2.4 and later only. Used with Minimum Poll Interval to specify a range of acceptable intervals when the Telestra NTP client will synchronize with the NTP server. In the client, this translates into seconds: two to the power of this setting. The allowable range is 4 (16 s) to 17 (36.4 h) inclusive.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 17: Procedural Warnings General Guidelines • DO NOT create local files on the DACS system (e.g., recording soundfiles or saving models) while in remote mode. Remember, remote mode is the Model Builder default. If you wish to create local files on the DACS system, ASTi recommends loading Model Builder in non-RMS mode. This is choice #2 from the Startup Menu: “Normal Operation without RMS”, which is available on DACS system boot.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Uploading Files Various procedures in RMS require you to upload files to the RMS server. These include: • • • • • Uploading an Options File Uploading an RMS Configuration File Uploading a DACS backup file for restoration Uploading a file to a DACS’ file system Uploading an XML file for model documentation Selecting files for upload from shared network volumes (over Samba, NFS or Windows’ Network Neighborhood) may produce unexpected results.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS Backup • Only initiate a DACS backup if you are certain that nobody is using its Model Builder software. • DO NOT change the names of DACS backup files generated by RMS if you plan to later restore from them. Backup file names are based on the IP address of the DACS, and the date of the backup. For example, backing up a DACS system with IP address “192.168.10.10” on June 7th, 2001 will result in a backup file named “192.168.10.10_07Jun01.tgz”.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS Restoration • Only initiate a DACS restoration if you are certain that nobody is using its Model Builder software. • Uploading previous backup files for DACS restoration using certain OS/browser combinations may result in the dots of the file name being replaced by underscores (e.g., “192.168.10.10_07Jun01.tgz” may become “192_168_10_10_07Jun01.tgz”). This will not affect your ability to restore from the file.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Model Builder Virtual Screen Utility The Model Builder Virtual Screen (MBVS) utility consumes a considerable amount of network bandwidth. This happens because keyboard commands must be sent from Telestra to the DACS system, and screen information must be passed back... in real time, and over the network. Because MBVS runs as a higher-priority process on the Telestra system, the web-based Remote Management System (RMS) may be less responsive during MBVS operation.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Chapter 18: Troubleshooting Troubleshooting RMS This section includes possible solutions to some problems you may experience while using RMS. The information here includes topics from the RMS Online Help System, as well as more detailed troubleshooting suggestions. RMS Server is Not Responding 1. Verify that you are pointing your web browser to the proper IP address for the RMS server. 2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Cannot Reboot or Shutdown Telestra via RMS During DACS backup or restore, RMS will be placed in a “lock” state, blocking system reboot or shutdown. If a DACS backup or restoration process is interrupted due to network failure or some other unforeseen circumstance, the lock state may not be fully cleared by RMS. 1. Verify that neither you nor another user (perhaps from another browser) has initiated a DACS backup or restoration.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) RMS in Server Frame has Red “X” This indicates that there is a server on the network that, while responding to Auto-Discovery, does not return valid Telestra Options File information, or has an invalid IP address. 1. Contact the system’s administrator to assign valid IP address information to the server. If you are the administrator, reference Chapter 5 for instructions on setting the IP address using the Telestra Configuration Utility.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Cannot Initiate DACS Backup or Restore RMS will only allow one DACS system to be backed-up or restored at a time. During these processes, RMS will be placed in a “lock” state, blocking another backup or restoration process from being initiated. If a DACS backup or restoration process is interrupted due to network failure or some other unforeseen circumstance, the lock state may not be fully cleared by RMS. 1.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DSP Missing from DACS Information If there is a DSP card (either TDM or Waveform Synthesizer) in a DACS system that isn’t showing up on the “DACS Information” page after you click “Find DSPs”, there are a few things you’ll need to check. 1. Verify that the DACS options file supports multiple DSPs. To do this, click on the “DACS Info” option in the DACS Menu (blue blocks in frame). In the “Software Information” table, look for the line “Max. # DSPs Supported”.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Troubleshooting HLA Error Messages The following table lists the possible error messages that may be printed to the /var/log/hla.messages log file (also available through RMS in Telestra v2.0 or later) and their causes. Debug Error Message Cause Error Loading audiofederate library Could not open configuration file RTI library path not specified correctly in configuration file (Telestra v1.6) Configuration file telestra.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Troubleshooting the HF Server Model Builder has built-in diagnostic tools that can be extremely helpful in identifying problems with HF Server operation. Basic troubleshooting guidelines are presented here. Step 1: Verify the proper setup and configuration of any DACS system that will access the HF Server. See Chapter 10 for more information about setting the “default.cfg” file.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) • Once “terraiN” is selected, the Terrain Occulting Status Window should appear, as shown in Figure 14. Figure 16: Model Builder Terrain Occulting Status Window • If two Over-The-Horizon (OTH) radios in the communications model are in tune, Model Builder should be sending out path loss requests at regular intervals. • In this case, the “tx” field of the “Terrain Pdus” line should be non-zero (as in Figure 14), and incrementing.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 3: If the DACS is sending and receiving path loss packets, then the HF Server is functioning properly. • If communications debugging is needed, verify that the two radios in question are in-range. Check the path loss values being returned from the HF Server on the “Paths” page in Model Builder. Select the “Dis network” option from the main menu, then “Paths rx-tx”, as shown in Figure 15.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) • Once “Paths rx-tx” is selected, the DIS Network Local RX/TX Paths List should appear, as shown in Figure 16. This screen displays a list of transmitter-receiver paths. Figure 18: Model Builder DIS Network Local RX/TX Paths List • Select the appropriate path, and the path loss returned from the HF Server will be shown in the “Path Factor” field, as shown in Figure 17.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) • If no value is returned, or if the frequency of the radio is outside the HF regime, the Path Factor will be 1.0, or 0.0 dB. If a zero is returned, the Path Factor will be zero, or –300 dB. If a valid Path Factor number is returned, the result will be between these two extremes.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Troubleshooting the Satcom Server General Before beginning specific troubleshooting procedures, it is always advised to verify all main system components are operational. This is easy to do using RMS utilities: 1. Servers / Satcom Server. Verify Status: Running 2. Find DACS / Find DSPs and RIUs. Verify that DACS system components are operational. 3. MB Virtual / Virtual Screens.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 1: Ensure that a link between the uplink transmitter and the DIS network has been established. Inspect the DIS Status page (from the Main Menu: speedkey D - speedkey S). • There should be incrementing counts in the TX Byte Count and TX Good Count fields. • If these fields are not incrementing, and the TX Errors field is incrementing, the DIS Ethernet interface is not physically linked to the network. • Resolve network problems.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 7: Verify that the uplink transmitter is configured with the correct ASTi Satcom modulation type: • Highlight the uplink transmitter entry on the Freq of Xmitters list. • Press Enter to view the transmitter PDU settings. Ensure that the Modulation Type: Major and Detail are correct. • Compare the settings you see in the PDU list with those in Table 5. If necessary, correct the settings in the radio object.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 11: Verify that the Satcom Server is receiving from the DIS network. • Check the RMS / Satcom Server / Counters / UDP Packets In. Press the Refresh button a to verify that the count is changing. • If the count does not change, verify the Satcom Server’s DIS network settings, found on RMS / Satcom Server Configuration / DISNET. • The Satcom Server IP address must match the DACS IP Broadcast address.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Step 16: If the downlink receiver is present on the Local Receiver list (On), but is not receiving (not On_Rx), inspect the model to determine why the radio is not receiving. • The downlink receiver frequency must match the Satcom Server’s downlink frequency. This frequency is determined by: • Uplink transmitter frequency minus Satcom Server Uplink Frequency plus Satcom Server Downlink Frequency.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Troubleshooting State Machines General All basic troubleshooting operations are performed using the RMS utilities provided. If this level of faultfinding is not adequate, please contact ASTi for further guidance. Once Telestra has completed booting, the PSMRE should automatically load and run the state machine model. This will be indicated most obviously by normal operation of the communication panels being driven.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) DACS System Checks The DACS provides the audio routing and processing of signals selected on the crew communication panels. Therefore, selecting a particular audio asset and gaining the expected audio response should ascertain normal operation of the system.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Appendix A: Example Network Topologies connect eth2 ect n con DACS Systems DACS Network co nn ec te th 0 Host Network All other HLA machines 1 eth HLA Network Teles tr a RMS Access: any browserequipped PC Figure 20: HLA/RMS Network Topology Copyright © 1999-2006 Advanced Simulation Technology inc.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) ect n con 0 eth Network Teles tr a DACS Systems RMS Access: any browserequipped PC Figure 21: Recommended Non-HLA Network Topology Example RMS-Specific Network Configuration To provide an overview of proper RMS and DACS configuration concepts, we include the following example installation. The example demonstrates connecting multiple DACS and RMS servers in both local-area- and wide-area-network (LAN/WAN) architectures.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) telestra.conf RMS A network:eth0:ipAddress:192.168.20.10 network:eth0:netmask:255.255.255.0 network:eth0:gateway:192.168.20.100 dacs:dacs1:ipAddress:192.168.20.5 dacs:dacs2:ipAddress:192.168.20.6 dacs:dacs3:ipAddress:192.168.66.3 HOST A E'net (eth0) 192.168.20.10 config.sys Ethernet 192.168.1.1 DACS A1 [mbremote] SET MODELS=USER SET REMOTE=192.168.20.10 ••• [common] SET LOCAL_IP=192.168.1.2,192.168.20.5 SET GATEWAY=192.168.1.1,192.168.20.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) RMS A Configuration File (“telestra.conf”) network:eth0:ipAddress:192.168.20.10 network:eth0:netmask:255.255.255.0 network:eth0:gateway:192.168.20.100 dacs:dacs1:ipAddress:192.168.20.5 dacs:dacs2:ipAddress:192.168.20.6 dacs:dacs3:ipAddress:192.168.66.3 DACS A1 “config.sys” File [mbremote] SET MODELS=USER SET REMOTE=192.168.20.10 ... [common] SET LOCAL_IP=192.168.1.2,192.168.20.5 SET GATEWAY=192.168.1.1,192.168.20.100 SET SUBNET_MASK=255.255.255.0,255.255.255.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Appendix B: Telestra Version Compatibilities Telestra Version 2.4-5 Hardware Platform 2U2, 2U5, 6 2U Min. RAM 1024 MB ASTi Linux 2.4.30 Software Packages Supported HLA RTIs HF, HLA, RMS2, ! Satcom, Terrain Ability to verify CD contents DMSO 1.3NGv6†# MÄK 1.3.7† MÄK 2.0† MÄK 2.0.1† MÄK 2.02# MÄK 2.03# ASTi SOM 3.0, 3.1*, 3.2*, 3.2-XDR* DACS Model Builder 4.09 or higher * can be used with RPR 1.0 and RPR 2.0 FOMs VTC NG-Pro 2.0.2†# 2.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Telestra Version Hardware Platform Min. RAM ASTi Linux Software Packages Supported HLA RTIs ASTi SOM DACS Model Builder HLA 1.4** 1U3 HLA 1.2** 1U3 128MB 2.4.? HLA DMSO 1.3NGv3.X 3.0 4.06d or higher 128MB 2.4.? HLA DMSO 1.3NGv3.X 3.0 4.04e or higher HLA 1.1** 1U3 128MB 2.4.? HLA DMSO 1.3NGv2 3.0 4.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Identifying your System Depending on the system requirements there are various hard drive options used in the Telestra. To identify your hard drive look for a part number on your system on the bottom of the carrier. For Telestras with the Parallel IDE hard drive the part number on the bottom of the carrier is DE75i-CA100/B. The ASTi part number on top is HD3-TL-A-R. This part number will only appear on the drive if it is ordered as a spare drive, ie.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Appendix C: HF Server ICD This document provides the specification for the software interface between the HF Server and the simulation host computer. The HF Server is provided with certain configuration data, on a perexercise basis, via an ethernet packet. The host software provides the input data to the HF Server in the format specified in this ICD. Data are provided to the HF Server via an ethernet connection between the host computer and the HF Server.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Appendix D: ALE Server ICD Introduction This document provides the specification for the software interface between the ALE Server and the host computer. The ALE Server is provided with certain configuration data, on a per Exercise basis, via an Ethernet packet. The host software provides the input data to the ALE Server in the format specified in this ICD.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Initialize/Set Scan List Type Message (Type=1) For all messages, bytes 0 through 3 should be set to zero. Variable Type Message_type In_Uint DIS_site_id DIS_host_id DIS_entity_id DIS_radio_id Exercise_id Radio_mode In_Uint In_Uint In_Uint In_Uint In_Uint In_Uint Scan_freq_count Scan_freq[0] Scan_freq[1] ...
ASTi Telestra User Guide (Ver. 2, Rev. L.1) ALE TX Response Message (Type=4, from ALE Server to Host) For all messages, bytes 0 through 3 should be set to zero. Variable Type Message_type Out_Uint DIS_site_id DIS_host_id DIS_entity_id DIS_radio_id Exercise_id Transmit_freq Count_call Out_Uint Out_Uint Out_Uint Out_Uint Out_Uint Out_Uint Out_Uint DIS_site_id[0] DIS_host_id[0] DIS_entity_id[0] DIS_radio_id[0] LQA[0] Pad DIS_site_id[1] DIS_host_id[1] DIS_entity_id[1] DIS_radio_id[1] LQA[1] Pad ...
ASTi Telestra User Guide (Ver. 2, Rev. L.1) ALE Server Sync Type Message (Type=5) For all messages, bytes 0 through 3 should be set to zero.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Appendix E: Satellite Communications Server ICD This document provides the specification for the software interface between the Satcom Server and the host computer. The Satcom Server is provided with certain configuration data via an Ethernet packet. The host software provides the input data to the Satcom Server in the format specified in this ICD. Data are provided to the Satcom Server via an Ethernet connection between the host computer and the Satcom Server.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Notes & Errata Telestra Version 2.4-5, January, 2006 • New: Support for 945G 2U hardware platform and SATA hard drives. • New: Ability to verify CD-ROM contents. • Change: The network interface ethernet port physical locations for the 2U and 4U chassis. Each ethernet port will be labeled on the chassis. • Change: Removed support for 1U hardware platforms. • Change: Removed domain name from default network setup. • Update: Upgrade doctool to latest version 1.1-4.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Telestra version 2.4-3, August 2004 • New: RMS now supports installation and management of customer-furnished Digital Terrain Elevation Data (DTED) files for use by the Terrain server. • New: New Telestra kernel adds support for latest 865G chipset and gigabit ethernet. • Update: RMS’ interface with the Terrain server has better, more informative error handling for non-fatal terrain query errors.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Telestra version 2.3, September 2003 • New: The ALE server now accepts synchronization messages from the host computer(s). This message, described in “Appendix D: ALE Server ICD”, allows multiple host computers with separate sets of radio and scan frequency data to use the same ALE server, effectively sharing multiple data sets across disparate hosts. A “sync messages” counter was added to RMS’ ALE Server page.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Telestra version 2.1, September 2002 • New: Telestra 2.1 adds RMS support for the ASTi high-frequency (HF) radio propagation server with ALE support, satellite communications server, panel state machine runtime environment, and ASTi’s new USB I/O device for panel interface to state machines. • New: Telestra 2.1 adds HLA support for DMSO HLA RTI 1.3NGv6 and MÄK HLA RTI 1.3.7.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Older Release Notes & Errata 05/23/02 - The Telestra 2.0 release combines new versions of the previously-separate HLA Communications and Remote Management System (RMS) software. Telestra 2.0 supersedes HLA version 1.6 and RMS version 1.3. It is built on the Debian 3.0 GNU/Linux release, and features the Reiser journaling filesystem. 05/23/02 - HLA: The HLA Communications software is now configured through the RMS web interface.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Warranty and Repairs Warranty Information The equipment is warranted for a period of one (1) year following purchase. In the case of equipment upgrades, warranty applies to original date of shipment of individual components. Other commercial equipment purchased or provided such as monitors, amplifiers, speakers, fiber optic links, etc. are also covered under the one year warranty unless otherwise stated.
ASTi Telestra User Guide (Ver. 2, Rev. L.1) Disclaimer and Warnings • Connect only ASTi-approved devices to the USB ports. Attempted use of non-ASTi USB devices may result in equipment damage. • Do not use commercial extender cables with ASTi USB devices. • There are NO user serviceable components in this device. Opening the chassis will void the warranty. 206 Copyright © 1999-2006 Advanced Simulation Technology inc.
