ASTi Telestra 4 Remote Management System 4 User Guide ...

500 A Huntmar Park Drive

ASTiTelestra 4

Remote Management System 4User Guide

Document: DOC-01-TEL4-RMS4-UG-4

Advanced Simulation Technology inc. 500A Huntmar Park Drive, Herndon, Virginia, 20170 USARevision M (July, 2011)

Product Name: Telestra 4 Remote Management System 4

ASTi Telestra 4 Remote Management System 4 User Guide

© Copyright ASTi 2011.

Restricted Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in sub-paragraph (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).

ASTi

500-A Huntmar Park Drive

Herndon, VA 20170

i

Table of Contents1.0. RMS Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1. Browser Compatibility & System Configuration Tips . . . . . . . . . . . . . . . . . . 21.1.1. Browser Settings ........................................................................................ 2

1.2. Web Technology Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2.1. Cookies ...................................................................................................... 31.2.2. JavaScript .................................................................................................. 4

1.3. Secure Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4. Pointing the Browser to RMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.0. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1. System Log In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2. RMS User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.0. System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.1. System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.1.1. Setting a Default Project and Layout........................................................ 113.2. System Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3. System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.4. System Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.0. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.1. Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1.1. Edit Network Configuration ...................................................................... 174.1.2. Network Devices ...................................................................................... 18

4.2. Option Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.2.1. Uploading the Options Files ..................................................................... 20

4.3. System Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.3.1. Backup System Configuration.................................................................. 224.3.2. Restore System Backup........................................................................... 234.3.3. Backup Management ............................................................................... 24

4.4. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.5. Speech Recognition and Text-to-Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.6. Terrain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.7. Voisus Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.0. Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.1. Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.2.1. Local and Global Projects ........................................................................ 315.2.2. Clone and Copy Projects ......................................................................... 32

ii

6.0. Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.1. Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.2. ACENet Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6.2.1. Firmware Version ..................................................................................... 356.2.2. Device Number ........................................................................................ 36

6.3. ACE-RIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.3.1. Updating ACE-RIU Firmware ................................................................... 39

6.4. ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406.4.1. Setting ACU Channel Gains..................................................................... 426.4.2. Updating ACU Firmware .......................................................................... 43

6.5. ACU2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496.5.1. Setting ACU2 Channel Gains................................................................... 506.5.2. Updating ACU2 Firmware ........................................................................ 52

6.6. Crown Amp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536.7. HLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.7.1. RTI Management ..................................................................................... 546.7.2. RTI Configuration..................................................................................... 56

7.0. Audio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.1. Uploading Sound Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.2. Spectral Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597.3. Archive Recordings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

ASTi Telestra 4 Remote Management System User Guide (Ver. 1, Rev. M)

Copyright © 2011 Advanced Simulation Technology inc. 1

1.0. RMS Web InterfaceThe Remote Management System (RMS) is a specialized web server that provides complete sight and control of all ASTi devices on the simulation network, ranging from stand-alone to multi-site, exercise-wide network configurations. Users can configure the Target and other services using a standard web browser from anywhere on the network. Further, RMS offers a familiar point-and-click “web page” interface for controlling ASTi resources, status checking, and file and network management.

The system can be accessed via any standard web browser on that network through the Remote Management System (RMS) web interface. While most RMS actions are intended to be fairly intuitive, this document offers further guidance and information about the capabilities of the sys-tem.


2 Copyright © 2011 Advanced Simulation Technology inc.

1.1. Browser Compatibility & System Configuration Tips

Different operating systems and web browsers offer varying levels of support for “standard” Internet technologies, such as JavaScript, Cascading Style Sheets (CSS), and Extensible Hyper-text Markup Language (XHTML), all of which are used by RMS. While ASTi designed RMS with cross-platform compatibility in mind, certain combinations of OS and web browser may not render RMS’ web interface properly.

1.1.1. Browser SettingsThese are usually referred to as “Preferences” or “Internet Settings”.

In order to take full advantage of RMS’s features, you may have to change some of the settings for your web browser. Many of these are default settings, but ASTi recommends that you verify or configure your browser to perform the following functions:

• Automatically Load Images

• Enable JavaScript for web pages (enabling JavaScript for email is unnecessary, not to men-tion dangerous)

• Enable Style Sheets

• Accept Cookies (all cookies or those which are returned to originating servers)

• Disable Full Caching (set the browser to “compare page in cache to page on network” every time)

• Disable “Pop-Up” Blocking

Please refer to your browser’s documentation or help system for information regarding these set-tings.

If you are concerned about the information stored by RMS “cookies,” or the nature of JavaScript code used by RMS, please consult the “Web Technology Security Issues” section on the next page for more information.



1.2. Web Technology Security Issues

The 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 cus-tomers.

Unfortunately, due to less-than-well-meaning Internet users (and the media exposure their exploits elicit), much of the Internet’s “general public” has rightfully become wary, if not com-pletely paranoid, about these technologies. Here, ASTi will attempt to allay any concerns you may have about the use of these technologies in RMS.

1.2.1. CookiesWhat are “cookies”?

They are small bits of text that come from a web server, and are handled by your web browser. There are two types of cookies: “session” and “persistent.”

“Session” cookies only live as long as your web browser program is running. When you close the application, or shut down your computer, the information contained in the session cookie is then lost. “Persistent” cookies are stored on your local computer’s hard disk, in a “cookie list.” The information contained in persistent cookies will remain available to the web browser and web server until it expires, or is deleted.

How does RMS use cookies?

There are only a few ways that RMS employs cookie technology. The first time you attempt to access the RMS system, you are asked to log in with a user ID and password. Once you have suc-cessfully provided these two bits of information, a session cookie is passed back to your browser from the RMS server, allowing you to access any RMS page without having to log in again. Please note: ASTi recommends shutting down your browser application when you’ve finished accessing an RMS server. This will clear the session cookie, and RMS will force another log-in the next time someone (even you) tries to access the system.

RMS 4 uses only session cookies as described above, and writes nothing to your computer's hard disk. No information whatsoever is transmitted to ASTi, or anywhere else.



1.2.2. JavaScriptWhat is “JavaScript?”

It is a simple programming language that extends a web browser’s capabilities beyond that which is possible using only X/HMTL (the standard language for generating web pages).

How does RMS use JavaScript?

There are only a few ways that RMS employs JavaScript.

• Launching Remote Windows

At times, RMS will open remote windows to keep information separate from the “main window”.

• Simple Navigation Links

JavaScript is sometimes used to provide hypertext links to other pages within RMS. E.g., if there is an error when processing a user input form, RMS will commonly use JavaScript to display a “go back” link that functions exactly like your browser’s “Back” button.

• Input Form Manipulation

JavaScript is also used to change the display and behavior of user input forms based on your actions. E.g., when backing up the system configuration, JavaScript allows the click-ing of the “Check All” button to select all the configuration sections’ check boxes simulta-neously.

The JavaScript code in RMS will NOT attempt to access, change or manipulate any information on your local computer at any time. Again, no information whatsoever is transmitted to ASTi, or anywhere else.



1.3. Secure Connection

RMS has the ability to serve its web pages over a secure connection with the user’s web browser. This secure connection uses industry-standard, 128-bit strong encryption, like the vast majority of online banking and shopping sites.

Note: Secure operation is turned on by default for the systems shipped within the United States and Canada, and may be optional when shipped to other countries. Its availability is subject to export controls imposed by the Bureau of Industry and Security of the U.S. Department of Com-merce. Contact ASTi for more information.

When running over a secure connection, RMS will still handle requests to its web server over the standard HTTP port 80, but will automatically forward these requests to the secure HTTPS port 443.

Part of this secure operation relies on a certificate residing on the RMS server, which is passed to the user’s web browser as a form of identification. Basically, this certificate tells the web browser who the server is (i.e., “I am an ASTi Target system”).

This certificate will raise a security warning in the vast majority of contemporary web browsers.

Here’s why:

In publicly-available applications like an e-commerce site, the certificate is used to verify that the server is “trusted” by comparing it to a database provided by third-party companies called “Certif-icate Authorities” (e.g., Verisign et al) who have already verified that a certificate holder is who they claim to be. Conveniently, these Certificate Authorities also create the server certificates for businesses who pass the test and pay a fee.

For systems with secure capability, however, the certificate is created and issued by ASTi. In other words, ASTi is acting as the Certificate Authority in place of a professional registrar like Verisign. As such, the system’s certificate will not be in the database of “trusted” sites that the web browser will check against, so it will alert the user.

Another circumstance that may prompt your browser to issue an alert deals with the “hostname” information contained in the certificate. ASTi uses the name “telestra” for the hostname when the certificate is created. This is not a fully-qualified domain name(e.g., “server.domain.com”), so the browser may complain that it is invalid.

Since ASTi does not have access to every customer’s network to determine the ultimate, fully-qualified domain name (FQDN) used by the customer’s DNS server, it is impossible to tailor these certificates on an installation-by-installation basis. Further, if you access the RMS server by entering an IP address (e.g., 10.1.1.123) or a network-specific FQDN (e.g., telestra4.yourdo-main.com), neither of these will match the host name as specified in the certificate, and your browser will likely alert you with a security warning.

In any case, you should examine the certificate’s information to verify that the machine you are trying to access in your web browser is, in fact, an ASTi Target system. After that, it is safe to accept the certificate and continue connecting to and working with RMS.



Many web browsers allow the user to change the “trust settings’ for any individual certificate. If you opt to change the trust settings for the Target’s certificate, then that browser (on that com-puter) will no longer raise the security warning.

Important: When visiting “secure” web sites on the Internet, DO NOT treat any security warning as you would those coming from your Target system(s). When working in a public environment like the Internet, every security warning must be thoroughly examined and only disregarded at your own peril.



1.4. Pointing the Browser to RMS

In order to access RMS using a web browser, the computer must be on the same network segment (LAN or WAN) as the Target. Contact your network administrator if you have any questions.

To launch the web browser application, go to the “Address” or “Location” field of the web browser’s display and type:

http://xxx.xxx.xxx.xxx/

where “xxx.xxx.xxx.xxx” is the IP address previously assigned to eth0 using a DHCP server or by manually setting it. For more information on the initial network configuration, see the “Setting up the Telestra 4 Target” section in the Telestra 4 Quick Start Guide (DOC-01-TEL4-QSG-1).

After pointing the browser to the Target, RMS will respond by displaying the System Status screen, which displays general information about the system.



2.0. Getting Started2.1. System Log In

For the initial system log in use the following user name and password.

user name: admin

password: astirules

After initial log in, users can create new user accounts and passwords to meet system administra-tion requirements.

The timestamp located on every RMS page displays the time, according to Target’s internal clock, that the page was delivered. This is important in discerning the “freshness” of any screen. Many RMS pages will automatically refresh after a certain amount of time, but the user can also refresh manually using their browser’s controls.

The footer bar contains ASTi’s support email address and web site. Please note, these links may not operate properly if the workstation lacks an email client, or if the network does not have access to the external Internet.



2.2. RMS User Management

To create new user accounts, select the “Manage Users” link located in the top right corner on most RMS pages. The user must be logged in as admin and possess the admin password to create new user accounts.



3.0. System3.1. System Status

After opening the browser, RMS directs the user to the Target System Status page. The user can select the “Contact Settings” link to enter installation and contact information for the system. The ‘CPU Load’ displays the overall amount of space used with the model running. The ‘Memory Used’ displays the amount of space used by the programs that are currently running including projects, model storage, and the data the programs are operating on. The ‘SWAP Used’ is the vir-tual memory used when memory utilization percentage is too high, ideally this should remain at 0 percent.

The user can also view the Target’s software version. The Project, Branch and Topology names are displayed for the Project running on the system.

Note: The Topology name is synonymous to the Layout in ACE Studio.



3.1.1. Setting a Default Project and LayoutRMS allows the user to set a default project and layout. The selected project and layout will install automatically after rebooting the Target.

On the Status page, select “Change” next to Default Layout. On the next page, select the desired project and layout and select “Make Changes.” This project and layout will install automatically the next time the Target is powered on or rebooted.



3.2. System Health

The ACE System Health status page allows the user to verify that the software is running prop-erly. The health system is made of a tree-like structure. Each section has sub-sections and those sub-sections have sub-sections and so on.

For example, if you see a yellow question mark by ‘ASTi Realtime’ then that indicates that one or more of ASTi Realtime’s sub-sections may have an issue. Select ASTi Realtime to expand it and see it's subsections. Most often when there is a yellow question mark by ASTi Realtime and you select it, you will see a red ‘X’ by Model. This is simply displaying that the model is not running. If you select ‘Show Detail’ on the right of the page you can see that it says ‘Stopped’ next to model. This may or may not be the case with your system, but its a good example of how to find the root of the problem.

The System Health pages are provided for system debug and contain very low-level raw informa-tion, most of this information is to provide ASTi with informative, accurate debugging details.



3.3. System Logs

The System Log displays 100 of the most recent log entries. The user can download the log files to the local system and view the uploaded logs. Filter capabilities provide quick search capabili-ties for specific functions including debug, info, warnings, errors, etc.



3.4. System Actions

Select the System > Reset/Power to perform System Actions. System actions include restarting the Target’s software (e.g., multicast routing and other networking daemons, RMS web server software, etc.), rebooting or shutting down the system. After selecting an action, a confirmation screen will open warning the user about interrupting software services, as shown in the figure below.

Operational Warning: Instantiating any of these options will interrupt software that is cur-rently running on the Target system, especially model operation.

Note: After shutting the system down the user may also need to press the power button located on the rear panel of the chassis.



4.0. Configuration4.1. Network Configuration

All Target network settings can be accessed from the Networking tab.

The Network Interface sections allow the user to specify the IP address, card mode and subnet mask for each of Target’s three Ethernet interface cards.

The General Networking screen encompasses network-wide, interface-independent settings such as DNS nameserver and router gateway IP addresses.

The Time Server allows the user to specify and test connections to a network time server (NTP server) for synchronizing the Target’s internal clock. Other settings allow users to tweak the Tar-get’s NTP client variables.

The Ping Utility allows the user to enter another computer’s IP address to send five pings (echo requests) to it. Positive response indicates that the computer is reachable over the network, using any of Target’s three network interfaces.

Operational Warning: Making changes to the interface settings (especially eth0), such as chang-ing the manual IP address, or setting card mode to DHCP may result in not being able to access RMS at the original (previous) IP address. If these settings are changed these settings, you must then specify the new IP address in the browser’s address slot to access RMS at its new network location.





4.1.1. Edit Network ConfigurationSelect the “Edit eth# Config.” link to edit eth0, eth1, and eth2 configuration settings. Select the “Make Changes” button to commit the changes to the system.



4.1.2. Network DevicesNavigate to Network > Devices to change the network configuration without having to login. Edit the network Ethernet ports by selecting “Edit eth# Config.”



4.2. Option Files

The RMS Option files page allows the user to view and manage the Target Options files. The Options file is an encrypted file provided by ASTi that is used to activate certain software pack-ages on the Target system(s). The option file also enables the system’s credits which provide the upper limit of functionality for the user to build and run models.

The Options file is a program-specific file containing information about all of the Target systems delivered under that program. A single Options file may be installed on multiple Target platforms, but will only activate the appropriate software packages on each platform. Software functionality as defined by the Options file is linked directly to the Target system’s hardware configuration.

For example, say ASTi ships two Target systems with serial numbers 98001 and 98002. If Target 98001 is intended for use as an HLA and HF radio server, while Target 98002 is the network Ter-rain Propagation server, then a single Options file will activate only what has been ordered. HLA and HF software will be activated on 98001, and only Terrain software on 98002. The same Options file activates both systems.

If, however, that same Options file is installed on Target system 97123, then it will not activate any additional software, since it does not contain information for this system.

Note: As program requirements grow, and additional Target systems are added to the network, ASTi will re-issue the Options file to include all previously-delivered systems, as well as any new ones. Again, one Options file will take care of all the Target systems under one program.

Target systems will run with base software functionality if no Options file is installed on the sys-tem, or if the installed Options file does not contain information for that system.



4.2.1. Uploading the Options FilesThe Options file is shipped on a CD with the system. The Options file is a .tgz file.

1. Drag the file onto the ACE Studio desktop or any workstation on the local network that has a local web browser for RMS.

2. In RMS, navigate to Configuration > Option Files and select “Choose File.”

3. Find the file on the workstation and select “Choose.”

4. Upload the Option File.

A new Options file may be uploaded at any time.

Note: Selecting an Options file with the same name as the currently-installed Options file will result in the new file overwriting the existing file.



4.3. System Backup and Restore

The user can easily manage the system configuration files through the backup and restore options listed below.

Backup

Use the Backup System Configuration option to backup the individual sections of the overall sys-tem configuration or backup the entire system configuration.

There is also an option to Backup System Configuration as Text Only. This does not backup any binary information and is only useful when exporting a project from a classified area.

Restore

Use the Restore System Configuration to install or restore system configuration files from a previ-ously-created backup file. This file can be uploaded to the system if it is not already resident on the Target.

Manage

Use the Manage Backup Archives to inspect, download and/or delete System Configuration backup archives.



4.3.1. Backup System ConfigurationSelecting to backup system configurations creates an archive of these files on the workstation. Check all or some of the desired configuration sections and select “Start Backup.”

The System Configuration Backup categories include:

• Options - includes all options files loaded on the system.

• Projects Archive - includes all Projects archived on the system. The user can click the Proj-ects Archive link and select to backup some or all of the Projects on the Target.

• RMS Users and Config - includes all RMS users and their passwords, as well as any user lockout settings for RMS.

• Sound Library - the library of sound files on the system, which includes an index and all of the WAV files that are used in the Project. The user can click on the sound library link and select to backup some or all of the sounds files.

• Telestra Config - includes all configurations settings such as network settings and system preferences.



4.3.2. Restore System BackupThe Restore System Backup allows the user to restore a model archive that exists on the Target. Select “restore now” to start the installation.

The user can also choose to upload a backup file that has been saved to the local workstation. This option allows the user to restore system configuration files.



4.3.3. Backup ManagementThe System Backup Management page allows the user to backup or delete system configuration files that currently exist on the Target.



Archive Information

Select the ‘Info’ link for a detailed list of the archived files, as shown below.



4.4. Description

Enter system details for informational purposes on the description page.



4.5. Speech Recognition and Text-to-Speech

The Speech Recognition and Text-to-Speech (TTS) software packages require an additional license file provided by ASTi. The license files are activated upon upload.

This RMS page also provides Voice Management for voices provided by ASTi. Simply upload and install voices for TTS.

Note: If running a Target with ASTi’s Telestra 4 Security Package installed i.e. a hardened sys-tem, you must manually upload voices for TTS.



4.6. Terrain

To add third party terrain data upload the .zip file on the Terrain Management page.



4.7. Voisus Downloads

The Configuration > Voisus Downloads page provides the Windows and Linux Client applica-tions and the Voisus-VBS2 Plugin. The Voisus Downloads are for use with ASTi's Synapse Voisus Server (P/N: SYN4-VS-XX). See the Synapse Voisus Server Manual (DOC-01-SYN4-VS-1) for system overview, configuration and requirements.



5.0. Projects5.1. Project Management

Project Management allows the user to view project list, clone a project, and copy existing proj-ects.



5.2.1. Local and Global ProjectsIn the main Project Management page, select the ‘Show Projects’ link to view all projects local to the system and over the network. The user can delete any local projects on the system.



5.2.2. Clone and Copy ProjectsIn the main Project Management page, select the ‘Clone New Project’ link. This is used in situa-tions where one project is used across multiple Targets. The user selects an existing project and clones it to create a link between a Master Target and a Slave Target. For more information, see ASTi Application Note 90: Managing a Single Project across multiple Target Platforms on the ASTi web site (www.asti-usa.com).

Selecting to copy a project simply creates an independent copy of the project.



6.0. Network6.1. Targets

The Network Targets page displays all the Targets on the network. Select the link to open a new RMS browser for a specific Target.



6.2. ACENet Devices

Important: The following section applies to ACE software versions 4.17 or greater. ACENet devices must have firmware version 2.x to run properly with ACE software versions 4.17 or greater. The RMS ACENet screen will report “Need firmware version > = 2.0” message if an ACENet device needs a firmware update to operate with the ACE software version.

Select the Network ACENet page to view all ACENet devices (e.g. ACE-RIU, ACU2, ACU, and Crown Amp) on the network. Each device on ACENet must have a unique device name.

For more information about ACENet see the ACENet User Guide (DOC-01-TEL4-AN-UG-1) specifically the ACENet Frequently Asked Questions (FAQs) section.



6.2.1. Firmware VersionACENet devices must have firmware version 2.x to run properly with ACE software versions 4.17 or greater.



6.2.2. Device NumberEach ACENet device self-assigns a number to itself called the “Device Number.” The device number determines the ACENet address space, which is used to communicate with Targets. The RMS ACENet screen displays the number selected by each device, which is generally unique.

However, the device number is not guaranteed to always be unique and in rare cases a conflict may arise between two devices using the same device number. The ACENet screen will report this error condition as “Duplicate device number.” To resolve a duplicate number conflict, the user must manually assign a unique number to the device in conflict. Select “Device Numbers” and change the device with the number in conflict. Then select “Apply”.



6.3. ACE-RIU

The Network ACENet page displays all the ACE-RIUs available on the network. The Layout col-umn displays whether the ACE-RIU is in use in the ACE Studio Layout. The network, firmware, device number, latency mode, status and message columns display additional information to ensure the ACE-RIU is running properly. Each ACE-RIU on the ACENet must have a unique device name and device number.

Select the ACE-RIU name to view the status of each channel.



View the ACE-RIU channel details.

Select the “Device Gain References” for general gain information.



6.3.1. Updating ACE-RIU FirmwareOn the ACENet page next to “Update Firmware” select the ‘ACE-RIU’ link for instructions to update the firmware. The following page will display the step-by-step instructions for updating the firmware.

Note: If running a Target with ASTi’s Telestra 4 Security Package installed i.e. a hardened sys-tem, you must manually install firmware that is not included with the original software installa-tion.



6.4. ACU

The Network ACENet page displays all of the ACUs available on the network. The Layout col-umn displays whether the ACU is in use in the ACE Studio Layout. The network, firmware, device number, latency mode, status and message columns display additional information to ensure the ACU is running properly. Each ACU on the ACENet must have a unique device name and device number.

Select the ACU to view the status of each channel or adjust the gains.



Selecting the ACU name displays the ACU channel details. Select each channel to set the gains.

Select the “Device Gain References” for general gain information. For more information on gains continue to the next section.



6.4.1. Setting ACU Channel GainsIn the Network >ACENet > ACU channel page, the user can enable the preamp and mic power. The user also sets the input and output gains. If an input or output gain is set to a value that is out-side of the acceptable gain minimum/maximum range it will be truncated to the accepted value. The range will vary depending on ACU firmware.

Alternate Gains

The ACU and ACU2 support the ability to select alternate gain settings via the ControlIn3 input on the ACU/ACU2 channel. By varying the resistance across the ControlIn3 pins, alternate gain sets can be selected, similar to how a 4-Channel PTT device works with the ControlIn2 pins. Note that a toggle can also be used to select between two of the four settings. For specifics on how to configure a hardware gain selector, please contact ASTi.



6.4.2. Updating ACU FirmwareThere are three ways to access the ACU firmware file.

• The firmware file may reside on the Target’s software.

• The file may be sent via an ACU Firmware Update CD. Insert the ACU Firmware Update CD into the ACE Studio development workstation.

• The firmware update file could also be sent in an email, in which case use a thumb drive to transport the file to the ACE Studio development workstation.

To update ACU firmware, the device must be powered on in “Boot Mode.” Note that this is differ-ent from normal ACU operation. Follow the step-by-step directions below.

Important: Do not simply click “Check All” and upgrade them all at once, this may adversely affect the stability of the ACUs.

Note 1: ASTi recommends updating all of the ACUs on the Targets' local ACENet to the same firmware version.

Note 2: If running a Target with ASTi’s Telestra 4 Security Package installed i.e. a hardened sys-tem, you must manually install firmware that is not included with the original software installa-tion.



1. On the ACENet page next to “Update Firmware” select the ‘ACU’ link for instructions to update firmware.

2. Follow the instructions on the page to reset the ACU in boot mode.

Note: When cycling power on the ACU, unplug the power for at least 30 seconds.

3. Once the ACU is in boot mode, refresh the RMS page.

4. Select the name of the ACU that is being updated.

5. After setting the ACU in boot mode, follow the step-by-step instructions on the RMS ACU Firmware Update page.

6. After selecting the ACU name and firmware version, click on “Continue to the next step.”



Note: If the firmware update was sent via email or CD-ROM the user must browse to select the file from the workstation.



7. Verify the ACU name and MAC address then click “Yes, Update ACU Firmware.”



8. Once the results page appears, follow the instructions on the page to reset the ACU in nor-mal operation mode.

Note: When cycling power on the ACU, unplug the power for at least 30 seconds. Do not click ‘refresh’ on the results page.



9. To verify the ACU firmware version, navigate to the ACU Health page and select ‘Show Detail.’ The new firmware version should appear, as shown below, the new version in this example is 1.10.



6.5. ACU2

The Network ACENet page displays all the ACU2s available on the network. The Layout column displays whether the ACU2 is in use in the ACE Studio Layout. The network, firmware, device number, latency mode, status and message columns display additional information to ensure the ACU2 is running properly. Each ACU2 on the ACENet must have a unique device name and device number.

Select the ACU2 name to view the status of each channel.

Selecting the ACU2 name displays the ACU2 channel details. Select each channel to set the gains. Continue with the next section for more information on channel gains.



6.5.1. Setting ACU2 Channel GainsIn the Network > ACENet > ACU2 page, the user can enable the preamp and mic power. The user also sets the input and output gains. If an input or output gain is set to a value that is outside of the acceptable gain minimum/maximum range it will be truncated to the accepted value. The range will vary depending on ACU2 firmware.

Select the “Device Gain References” for general gain information.



Alternate Gains

The ACU and ACU2 support the ability to select alternate gain settings via the ControlIn3 input on the ACU/ACU2 channel. By varying the resistance across the ControlIn3 pins, alternate gain sets can be selected, similar to how a 4-Channel PTT device works with the ControlIn2 pins. Note that a toggle can also be used to select between two of the four settings. For specifics on how to configure a hardware gain selector, please contact ASTi.



6.5.2. Updating ACU2 FirmwareThe following procedure is recommended to maximize firmware upgrade reliability. There are a few initial conditions that must be setup to ensure a smooth firmware upgrade.

First, you must install a project and layout that includes all ACENet devices connected to the Tar-get. Follow the steps below to do this.

1. Using ACE Studio, open a project on the Target connected to the ACENet device(s).

2. The layout running in Studio must include all of the ACU2s that are getting upgraded. One way to do this is to create a readiness model, this ensures that your layout includes the connected ACU2s. In the menu bar select "Layout" and "Add Readiness." Overwrite any previous readiness layouts if prompted.

3. Select the readiness layout and then click "Install Project."

Follow the ACU2 firmware update instructions in RMS. On the ACENet page next to “Update Firmware” select the ‘ACU2’ link for instructions to update the firmware. The following RMS page will display the step-by-step instructions for updating the firmware.

Important: If upgrading more than one ACU2, only initialize a maximum of two ACU2s into boot mode. After a pair is complete, boot them in to normal mode. Repeat this cycle until all ACU2s are upgraded.

Note: If running a Target with ASTi’s Telestra 4 Security Package installed i.e. a hardened sys-tem, you must manually install firmware that is not included with the original software installa-tion.



6.6. Crown Amp

The Network ACENet page displays all the Crown Amps available on the network. The Layout column displays whether the Crown Amp is in use in the ACE Studio Layout. The network, firm-ware, device number, latency mode, status and message columns display additional information to ensure the Crown Amp is running properly. Each Crown Amp on the ACENet must have a unique device name and device number.



6.7. HLA

6.7.1. RTI ManagementThe RMS HLA pages provide RTI management. ASTi’s HLA communications environment sup-ports RTIs downloaded from DMSO (http://www.dmso.mil/), MÄK Technologies (http://www.mak.com/), and VTC (http://www.virtc.com/) websites. Download the RTI that is compati-ble with the corresponding Target release, as specified in the Telestra 4 Target Operation & Main-tenance Manual (DOC-01-TELA-TUG-1), Appendix C: HLA RTIs Compatibility.

IMPORTANT: The upload process must not be interrupted. Some RTI files can be several megabytes in size, and RMS may appear unresponsive while the file is transferring from your computer over the network to the Telestra machine. This is normal for any file transfer of this size. Users must wait for the confirmation screen to appear.

Note: If running a Target with ASTi’s Telestra 4 Security Package installed i.e. a hardened sys-tem, you must manually upload and install the RTI.

Installing an RTI on the Target is a simple process.

1. In RMS, select “HLA” under the left menu bar, this will open the RTI Management page.

2. Under the “RTI - Upload & Install” section of the page, click the “Browse” button.

Browse for the RTI file on your local computer (where your web browser is running). RTI files usually end in one of the following file extensions: .tar.gz, .tgz, or .sh.



3. After you’ve located the file, click the “Upload & Install RTI” button. Once the file upload is complete, the Target will unpack and install the RTI files in the appropriate loca-tion.

4. RMS will display a message stating the RTI file was successfully uploaded and installed.



6.7.2. RTI ConfigurationAfter an RTI is installed through HLA Management, users must activate the RTI.

1. In RMS, select “HLA” under the left menu bar then select the “HLA Configuration” link.



2. Select the RTI installed on the system from the pull-down menu and click “Activate RTI” on the configuration page to activate it. Note: You will need admin access to complete this step.

3. RMS will prompt you to restart the Target for the RTI to become active.

For more details on the RTI see the Telestra 4 Target Operation & Maintenance Manual (DOC-01-TELA-TUG-1), Chapter 5: HLA.



7.0. Audio7.1. Uploading Sound Files

The Uploading Sound Files page provides a two-step process to uploading sound files on the sys-tem. The user must first select a waveset or create a new one. The waveset is a folder that contains the soundfiles in the sound repository. The selected sound files are then uploaded to the waveset folder.

Important: All sound files must be in the following format: 16-bit PCM MONO WAV files with a 48khz sample rate. RMS will give you an error if the file is not in this format.



7.2. Spectral Analysis

The RMS Spectral Analysis page creates a pdf comparison file of the recorded audio files matched up to reference audio. The recorded files are typically generated using the Level D Cap-ture component or the RecordReplay component.



Stand-Alone

Simply select the sound file to generate a stand-alone spectral analysis graph. Select “Start Spec-tral Analysis” and wait as the system initializes, analyzes the sound files, saves the sound file data, and generates the PDF.



Comparison

When selecting “Comparison” plot you must also select the waveset containing the wave files for comparison. Select a waveset to view the files for comparison.



Below is an example of a generated comparison plot.



Below is an example of a generated difference plot.



7.3. Archive Recordings

In RMS Archive Recordings save all recording files that are created using the Level D Capture component or Record/Replay component.

Date post:	31-Dec-2016
Category:	Documents
Upload:	hoangque
View:	243 times
Download:	5 times

ASTi Telestra 4 Remote Management System 4 User Guide ...

Documents