UNIX in general but not Linux in particular, there are some useful commands and tools specific to Linux described at the end of this document. This guide is intended to assist the user in initial start-up of the Telestra unit and provides an over- view of the basic commands and facilities of the system.
Page 5
Host # n DACS System 4 Please note that in order to integrate Telestra into your network, certain configuration set-up pro- cedures are required to set the IP address of the HLA Ethernet adapter and Host Interface adapter. The second Ethernet adapter, used to connect to the DACS node, is pre-configured on shipment, and should not be modified unless under ASTi instruction.
file system integrity. To start the unit, apply power via the front mounted on/off switch. The unit will boot-up and run the Telestra federate on the first console. To log into the system and edit files, you must switch to the second console by pressing the ‘Alt-F2’...
Telestra Setup Procedure Telestra Configuration Utility The Telestra system ships with a console GUI configuration tool that supports configuring all net- work interfaces, host access, terrain queries, tactical data links, and access to the federate remote control interface. To start the configuration utility, login as root and run the command con- figTelestra.pyc.
Nameserver for the system. For each of the remaining interfaces, the Telestra Configuration Utility contains options for the IP address, Netmask, and Gateway. The Telestra system ships with default values for all three interfaces. Users will need to modify the settings for the HLA and Host interfaces to match their specific network configurations.
Next, execute the ‘moveRTI.sh’ command to move the RTI components into their ASTi specific locations. To test if the RTI has been properly installed, log out and log in as hlauser. Then type “telestra -t” at the prompt. If the last line printed reads “TEST OK”, then the installation was successful.
HLA network. However, to allow local only testing or stand-alone tests to be performed, it is pos- sible to run the rtiexec on the Telestra box. The rtiexec must be running somewhere in order for the system to function. The rtiexec can be run by logging in as hlauser and typing rtiexec from consoles 2 through 6 (see below).
Page 12
first: issuing a new join command will cause the Telestra federate to resign from its current federation before attempting to join the new one. If the Telestra federate is instructed to join a federation it is already joined to, it will resign and re-join that federation.
ASTi Telestra User Guide (Version 1, Revision D) Using the Remote Control Interface The commands discussed above are part of a complete set of commands that the Telestra federate recognizes. These commands can either be issued from the console or through a TCP/IP connec- tion with the Telestra Remote Control Interface.
The default value is N and therefore requires the user to perform a manual “join”. If this is set to Y, and the Telestra federate is run before an rtiexec is started, the federate will be unable to join, and may crash on some RTIs.
Page 15
ASTi Telestra User Guide (Version 1, Revision D) Audio_Backchannel = <ON or OFF> If this is set, the Telestra Federate sends the audio over the HLA physical network, but bypasses the RTI. The Telestra federate will still create transmitter and receiver HLA objects.
Telestra Federate. The following files are resident in this directory (or sub directory as indicated). telestra This file starts the Telestra federate. Use of the argument “-t” forces the system to run a system confidence test. When simply used on the command line, this starts the application federate, and uses the commands found in the configuration file.
As stated previously the rtiexec application must be running somewhere on the network to which Telestra is connected. However there may be cases where the system is down or some standalone testing is required. In order to support this Telestra includes a local copy of rtiexec.
“Cockpit_UHF1”, then the object name displayed (and created on the RTI) will be “Aircraft_Posn.Cockpit_UHF1.rx”. (A radio object actually consists of two separate objects which are created on the RTI. These are Transmitter objects, whose names the ASTi System ends in ‘.tx’, and receiver objects, whose names will end in ‘.rx’).
Page 20
ASTi Telestra User Guide (Version 1, Revision D) The “Entity” object used for entity attach now functions in a different way. It is now only neces- sary to enter the HLA name of the required attach entity in the name field of the Entity object in Model Builder.
Red Hat Linux (and hence the Telestra System) includes a set of utilities that greatly simplifies access to the 3.5” floppy drive fitted to the unit. These tools are known as “mtools” and allow DOS-like commands to be used for all normal floppy operation, without the need to mount/unmount the drive.
Updating the Telestra software The Telestra software updates are distributed as a Red Hat Package file, which have a file exten- sion “.rpm”. These are small enough to fit on a floppy disk, so the mtools mentioned above can be used to get them from a Windows machine onto the Telestra system.
Telestra systems. To test the installation, log in as hlauser and type “telestra -t”. For the purposes of this scenario, the rtiexec process will run on one of the two Telestra systems. Only one rtiexec process should exist on the network. For performance reasons, ASTi recommends running this process on a separate machine during an actual exercise and NOT on one of the Telestra systems.
Step 1: Make sure the Telestra system is powered ON. Step 2: Switch to the second console using ‘ALT-F2’ and login as root. Step 3: Start the Telestra Configuration Utility using ‘configTelestra.pyc’. The network settings will reflect the default values.
Page 28
ASTi Telestra User Guide (Version 1, Revision D) Figure 8: Modified HLA Interface Settings Step 6: Reboot the system to activate the changes. Step 7: Repeat steps 1 through 6 for additional machines, using the specific settings for each machine.
‘rtiexec’. Figure 9: Running rtiexec on Telestra_A Step 2: On each machine switch to the first console (You will see the ‘Telestra >’ prompt) and enter the command ‘join asti’. Figure 10: Telestra Federate before the Join Command...
Page 30
ASTi Telestra User Guide (Version 1, Revision D) Step 3: Wait for the federate software to return a ‘JOIN OK’ to indicate a successful join opera- tion. If the software returns a ‘JOIN FAIL’, double check the network configuration on each machine.
Page 31
ASTi Telestra User Guide (Version 1, Revision D) Step 4: On any Telestra system, switch to one of the alternate consoles and execute the command ‘rtiConsole’. This will allow the user to view the current Federations, as well as the list of joined Federates.
ASTi Telestra User Guide (Version 1, Revision D) Appendix B: ASTi Radio SOM Version 3.0 OMD File (OMDT v1.3.4.16) (ObjectModel (Name "ASTi Radio SOM") (VersionNumber "3.0") (Type FOM) (Purpose "To support real time,person in the loop radio simulation") (ApplicationDomain "Real time, platform level simulations.\r\n") (SponsorOrgName "ASTi")
Page 43
ASTi Telestra User Guide (Version 1, Revision D) (Attribute (Name "ReceivedPower") (DataType "float") (Cardinality "1") (Units "dB-milliwatts") (Accuracy "perfect") (AccuracyCondition "always") (UpdateType Conditional) (UpdateCondition "> RX PWR THRSH" [8]) (TransferAccept N) (UpdateReflect UR) (Description "The power of the received transmission.") (DeliveryCategory "best_effort")
Page 44
ASTi Telestra User Guide (Version 1, Revision D) (Description "The radiation pattern of the radio\'s antenna.") (DeliveryCategory "best_effort") (MessageOrdering "receive") (Attribute (Name "Encryption") (DataType "CryptographicStruct") (Cardinality "1") (Units "N/A") (Resolution "N/A") (Accuracy "perfect") (AccuracyCondition "always") (UpdateType Conditional) (UpdateCondition "On change")
Page 45
ASTi Telestra User Guide (Version 1, Revision D) (DataType "TransmitStateStruct") (Cardinality "1") (Accuracy "perfect") (AccuracyCondition "always") (UpdateType Conditional) (TransferAccept N) (UpdateReflect UR) (Description "Data defines the transmission state power, activity, and input source.") (DeliveryCategory "best_effort") (MessageOrdering "receive") (Attribute (Name "WorldLocation") (DataType "WorldLocationStruct")
Page 46
ASTi Telestra User Guide (Version 1, Revision D) (DeliveryCategory "best_effort") (MessageOrdering "receive") (Interaction (ID 2) (Name "EncodedAudioRadioSignal") (ISRType IR) (Description "A form of radio signal, where the signal is voice/audio data encoded according to a standard encoding scheme.") (DeliveryCategory "best_effort") (MessageOrdering "receive")
Page 47
(Note (NoteNumber 13) (NoteText "This field is not currently supported by the ASTi radio. However, when anistropic antennae are modeled in the ASTi radio, it will follow these data formats, plus additional ones (if required)")) (Note (NoteNumber 14) (NoteText "This structure is preceded by a 16 bit field, so the padding does, in fact, come out correctly"))
ASTi Telestra User Guide (Version 1, Revision D) Version 3.0 OMT File (DIF HLA-OMT v1.3 (TYPE Single)) (ObjectModel (Name "ASTi Radio SOM") (VersionNumber "3.0") (Type FOM) (Purpose "To support real time,person in the loop radio simulation") (ApplicationDomain "Real time, platform level simulations.\r\n") (SponsorOrgName "ASTi")
Page 58
ASTi Telestra User Guide (Version 1, Revision D) (DataType "float") (Cardinality "1") (Units "dB-milliwatts") (Accuracy "perfect") (AccuracyCondition "always") (UpdateType Conditional) (UpdateCondition "> RX PWR THRSH" [8]) (TransferAccept N) (UpdateReflect UR) (Description "The power of the received transmission.") (Attribute (Name "ReceivedTransmitterIdentifier") (DataType "RTIObjectIdStruct")
Page 59
ASTi Telestra User Guide (Version 1, Revision D) (Accuracy "perfect") (AccuracyCondition "always") (UpdateType Conditional) (UpdateCondition "On change") (TransferAccept N) (UpdateReflect UR) (Description "The data specifying the encryption of the transmitted signal.") (Attribute (Name "Frequency") (DataType "FrequencyStruct") (Cardinality "1") (Accuracy "perfect") (AccuracyCondition "always")
Page 60
ASTi Telestra User Guide (Version 1, Revision D) (UpdateReflect UR) (Description "The location of the radio transmitter in the world coordinate system.") (Class (ID 4) (Name "BaseEntity" [15]) (PSCapabilities S) (Description "Object represented in the simulated world.") (Attribute (Name "WorldLocation") (DataType "WorldLocationStruct")
Page 61
ASTi Telestra User Guide (Version 1, Revision D) The user can also obtain the ObjectName for a particular object instance using the getObject- InstanceName call.")) (Note (NoteNumber 2) (NoteText "The current OMT standard does not allow the definition of variant records in com- plex data types, i.e.
Page 62
ASTi Telestra User Guide (Version 1, Revision D) (Note (NoteNumber 13) (NoteText "This field is not currently supported by the ASTi radio. However, when anistropic antennae are modeled in the ASTi radio, it will follow these data formats, plus additional ones (if required)")) (Note (NoteNumber 14) (NoteText "This structure is preceded by a 16 bit field, so the padding does, in fact, come...
Need help?
Do you have a question about the Telestra and is the answer not in the manual?
Questions and answers