ASTi Model Builder Visual Basic Training Manual Document: DOC ...

ASTi 

Model Builder Visual 

Basic Training Manual 

Document: DOC-01-MBV-BTM-1 

Advanced Simulation Technology inc. 500 A Huntmar Drive, Herndon, Virginia, 20170 USA 

Revision B (September 2006) 

500 A Huntmar Park Drive

Product Name: Telestra 

ASTi ASTi Model Builder Visual Basic Training Manual 

© Copyright ASTi 2006. 

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). 

ASTi 

500 A Huntmar Park Drive 

Herndon, VA 20170

Table of Contents 

1.0. Introduction and Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 

1.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 

1.2. Course Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 

2.0. Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 

2.1. Telestra . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 

2.1.1. Ethernet Interfaces ................................................................................................2 

Figure 1: Telestra - Front View .............................................................................................2 

Figure 2: Telestra - Back View ..............................................................................................3 

2.2. USB Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 

Figure 3: Audio Distribution Architecture ..............................................................................4 

2.2.1. Iris ..........................................................................................................................5 

Figure 4: Iris - Front View ......................................................................................................5 

Figure 5: Iris - Rear View ......................................................................................................5 

Figure 6: 1U Iris ....................................................................................................................6 

Figure 7: 4 Channel Iris ........................................................................................................6 

Figure 8: 6 Channel Iris ........................................................................................................6 

2.2.2. Axis ........................................................................................................................7 

Figure 9: Axis - Front View ....................................................................................................7 

Figure 10: Axis - Rear View ..................................................................................................7 

2.2.3. Prism .....................................................................................................................8 

Figure 11: Prism (4-Channel) ...............................................................................................8 

Figure 12: Prism (2-Channel) ...............................................................................................8 

2.2.4. Spectrum ...............................................................................................................9 

Figure 13: Spectrum - Front View .........................................................................................9 

Figure 14: Spectrum - Rear View .........................................................................................9 

2.2.5. Ancillary Equipment .............................................................................................10 

Figure 15: Ancillary Equipment ...........................................................................................10 

i

3.0. Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 

ii 

3.1. Telestra . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 

3.2. Model Builder Visual Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . 13 

Figure 16: MBV Startup Screen ..........................................................................................14 

Figure 17: MBV Model Folder .............................................................................................15 

Figure 18: Telestra Toolbar ................................................................................................16 

3.3. Remote Management System 3.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 

Figure 19: RMS Telestra Status Page ................................................................................18 

4.0 DIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

4.1. DIS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

4.1.1. TX PDU ...............................................................................................................20 

4.1.2. Signal PDU ..........................................................................................................21 

4.1.3. RX PDU ...............................................................................................................21 

4.1.4. Entity State PDU .................................................................................................21 

5.0. Host Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 

6.0. Getting Started with Telestra and RMS . . . . . . . . . . . . . . . . . . . . . . . . . 23 

6.1. Cold Starting Telestra. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 

6.2. Uploading Options File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 

6.2.1. Instructions to Upload the Options File ...............................................................24 

Figure 20: RMS Options File ..............................................................................................25 

6.3. Configure Basic Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 

Figure 21:Telestra System Status ......................................................................................26 

6.4. Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 

Figure 22: RMS Telestra Networking Page ........................................................................28 

6.5. Model Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 

Figure 23: RMS Telestra Models Management Page .........................................................29 

6.6. Detecting USB Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 

6.6.1. Instructions for discovering USB Hardware in RMS ............................................30 

Figure 24: RMS Hardware Detection Page ........................................................................30 

Figure 25: USB Detection ...................................................................................................31 

6.7. Mapping Iris Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 

Figure 26: Hardware Setup and Mapping ...........................................................................32 

Figure 27: RMS Iris Hardware Assignments Page .............................................................33

6.8. Configuring Model Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 

Figure 28: RMS Models Host Interface Configuration Page ...............................................35 

7.0. Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

7.1. Saving Model Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

7.2. Saving Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 

Figure 29: RMS Telestra Actions ........................................................................................37 

Figure 30: RMS System Configuration Backup Page .........................................................38 

7.3. Restoring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 

7.4. Installing Telestra Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 

Figure 31:Telestra Software Upgrade .................................................................................40 

7.5. Hardware Readiness Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 

Figure 32: RMS Hardware Readiness ................................................................................42 

8.0. Model Builder Visual Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 

8.1. Creating a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 

Figure 33: RMS Telestra Preferences Page .......................................................................44 

Figure 34: RMS New User Account ....................................................................................44 

8.2. MBV Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 

8.3. Component Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 

8.4. MBV ICD Tool (with Tutorial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 

Step 1: Creating a New ICD ..........................................................................................47 

Figure 35: Creating an ICD .................................................................................................47 

Step 2: Naming the ICD ................................................................................................48 

Figure 36: ICD Name ..........................................................................................................48 

8.4.2 Adding Packets ....................................................................................................49 

Figure 37: ICD Packet Information .....................................................................................49 

Step 3: Adding a Packet to the ICD ...............................................................................49 

8.4.3. Choosing a View Mode .......................................................................................50 

8.4.4. ICD Packet Members ..........................................................................................50 

Step 4: Adding a Member ..............................................................................................51 

Figure 38: Adding Members ...............................................................................................51 

Step 5: Defining the Member .........................................................................................52 

Figure 39: Setting the Member Type ..................................................................................52 

8.4.5. Setting Offsets .....................................................................................................53 

Figure 40: Setting Offset .....................................................................................................53 

8.4.6. Saving Changes ..................................................................................................54 

iii

iv 

8.4.7. Implementing Changes in Your Model ................................................................54 

8.5. Changing an Existing ICD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 

9.0. Creating a Basic Model in MBV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 

Figure 41: Model Tutorial Overview ....................................................................................57 

9.1 Tutorial 1 - Sine Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 

Step 1: Creating a New Model ......................................................................................60 

Figure 42: Creating a New Model .......................................................................................60 

Step 2: Setting up the Iris ..............................................................................................61 

Figure 43: Setting up the Iris ...............................................................................................61 

Step 3: Creating the Sine Wave ....................................................................................62 

Step 4: Creating the Table ............................................................................................64 

Step 5: Driving the Amplitude by Creating a Counter and Comparator .........................66 

Step 6: Creating a New ICD ..........................................................................................70 

Step 7: Linking the ICD to the Model .............................................................................72 

Step 8: Mapping the Iris ................................................................................................74 

Figure 44:Mapping the Iris Hardware .................................................................................74 

Step 9: Organizing Your Model .....................................................................................76 

Figure 45: Final Model ........................................................................................................76 

9.2. Tutorial 2- VOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 

Step 1: Creating a Vox subfolder ..................................................................................77 

Step 2: Creating the Vox object and Iris Cable .............................................................77 

Step 3: Creating New Vox Members in the ICD and Assigning them in the Model .......80 

9.3. Tutorial 3- Play Sounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 

Figure 46:Simple and Complex Loop Diagram ...................................................................85 

Figure 47: Playsounds ........................................................................................................86 

Figure 48: MBV Sound Library ...........................................................................................87 

Step 1: Creating Playsound Object and Using the Sound Library .................................88 

Step 2: Assigning Sounds to Playsound Object ............................................................90 

Step 3: Routing the Audio to the Iris ..............................................................................91 

Step 4: Creating the 4 Channel PTT Psound Index ......................................................92

9.4. Tutorial 4- Mixer and Channel Handles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 

Step 1: Creating the Mixer and Iris Cable .....................................................................98 

Step 2: Deleting Audio Out Links from other Subfolders ...............................................99 

Step 3: Setting up the Bus and Mixer ..........................................................................100 

Step 4: Routing Audio .................................................................................................105 

Step 5: Selecting the Sound ........................................................................................106 

Step 6: Adding Members to the ICD Packet ................................................................107 

Step 7: Assigning the ICD to the Model ......................................................................109 

Figure 49: MBV Components Tutorial Complete Model ...................................................114 

10.0. Creating a Radio Model in MBV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 

10.1. Tutorial- Radio Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 

Step 1: Creating the Iris Asset .....................................................................................116 

Step 2: Creating the Entity Object ...............................................................................117 

Step 3: Creating a New ICD ........................................................................................119 

Step 4: Creating the UDP Cable and Links .................................................................121 

Step 5: Creating the Radio ..........................................................................................123 

Step 6: Adding Members to the ICD Packet for Radio 1 .............................................126 

Step 7: Creating Radio 2 .............................................................................................128 

Step 8: Adding Members to the ICD for Radio 2 .........................................................129 

Step 9: Creating Operator 1 ........................................................................................131 

Step 10: Adding Members to the ICD for Operator 1 ..................................................133 

Step 11: Creating the UDP in Cable and Assigning Links ...........................................134 

Step 12: Creating Operator 2 and Adding Members to the ICD Packet ......................137 

Step 13: Adding Links for Operator 2 ..........................................................................139 

Step 14: Connecting the Iris Asset ..............................................................................140 

Step 15: Mapping the Iris Hardware Devices to the Model .........................................144 

Step 16: Running the Model ........................................................................................145 

11.0 Converting a 2-operator 2-radio model to an 8-operator 

4-radio model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 

Step 1: Adding Radios 3 and 4 ....................................................................................147 

Step 2: Adding to the Existing ICD ..............................................................................147 

Step 3: Linking the ICD to Radio_3 and Radio_4 ........................................................149 

Step 4: Adding Operators ............................................................................................151 

Step 5: Adding ICD members to Drive the Operators .................................................154 

v

12.0 Model Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 

vi 

12.1. Creating Debug Sets in RMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 

12.3. MBV Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 

12.4. Viewing RX Buffer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 

12.5. Viewing TX Buffer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

ASTi MBV Telestra Training (Ver.1, Rev.B) 

1.0. Introduction and Agenda 

1.1. Summary 

The heart of the ASTi Telestra is the Model Builder Visual (MBV) model development system 

and the Remote Management System (RMS). These software applications transform the Telestra 

into a comprehensive development workstation for the creation, extension and tuning of sophisticated 

audio simulation models. 

This training course will familiarize you with the layout of RMS and MBV, as well as the related 

hardware and its uses. 

1.2. Course Goals 

After completion of this course you will understand how to: 

• Understand the setup of the general system including networking, software management, 

user accounts, backups, boot settings, and option management. 

• Easily navigate RMS: 

• Setup Iris hardware mapping it in RMS and conduct testing 

• Work with models including model management and host interface setup 

• View radio information and setup 

• Troubleshoot models using debug screens 

• Manage users accounts and models 

• Understand MBV interfaces: 

• Build models using the ICD tool (packet editor) including UDP in and out cables for 

receive and transmit buffers 

• Create sounds for your model using the Sound Library Editor 

• Generate Intercoms and Radios via the intercom/radio channel editor 

• Employ the radio monitor 

• Develop with the component set 

• Work with the model canvas 

Copyright © 2006 Advanced Simulation Technology inc. 1

2.0. Hardware Overview 

2.1. Telestra 


ASTi’s Telestra product line consists of a network scalable, high performance, Linux-based hardware 

platform, USB-based digital audio and I/O distributions equipment. 

• 3.4 GHz Pentium Processor 

• One (1) 1 Gbps Ethernet Interface 

• Two (2) 10/100 Mbps Ethernet Interfaces 

• Four (4) USB Ports (For use with ASTi USB devices only) 

The various components of the Telestra are listed below: 

• Power supply 

• Removable hard drive 

• CD-RW drive 

• USB ports 

• Ethernet Interfaces 

2.1.1. Ethernet Interfaces 

The Telestra comes standard with a DIS (Distributed Interactive Simulation) network interface 

card (NIC), which is used for voice traffic (radio, intercom, etc.) to and from other Telestras or 

simulators on the network. An optional Host interface can be purchased to control state information 

such as frequencies, squelch, engine RPM, etc. The host control and voice traffic functionality 

can be combined onto one interface, if the traffic load is fairly low and permitted under 

security guidelines. 

Power Button 

Reset Button 

CD-RW Drive 

Figure 1: Telestra - Front View 

Air Filter 

Removable Hard Drive 

2 Copyright © 2006 Advanced Simulation Technology inc.


Power Connection 

Power Switch 

Keyboard 

Figure 2: Telestra - Back View 

Mouse 

Monitor 

USB Ports 

Ethernet Interfaces 


2.2. USB Devices 


All the equipment needed for the training course is provided in the ASTi training room. This 

includes: 

• (2) Telestra units with MBV and RMS installed 

• (2) Iris - Audio interface module 

• (2) Axis - Local USB distribution module 

• Prism - USB extender module 

• Spectrum - Remote USB distribution module 

• (2) Telex headset/microphone units 

• (2) PTT buttons 

• (2) Fostex powered speakers 

MBV also requires a three-button mouse. 

For more information on the USB connections see the ASTi Telestra USB Device Connections 

Matrix (ASSY 01 UMCX-IN 1) 

Cat 5 Cable 

Max. Length 300’ 

Spectrum 

Iris Iris 

Iris Iris 

Telestra 

Prism 

Spectrum Spectrum Spectrum 

Figure 3: Audio Distribution Architecture 

Out A Out B 

Out C 

Out D 

4 Copyright © 2006 Advanced Simulation Technology inc. 

Axis 

AXIS 

Advanced Simulation Technology inc. www.asti-usa.com 

USB Cable 


Iris Iris 

USB Cable 


Iris 

USB Cable 

Max. Length 15’


2.2.1. Iris 

The Iris module is the audio and input/output (I/O) unit for ASTi’s Telestra platform. The Iris permits 

installation close to operator positions, and takes advantage of digital audio and I/O distribution 

to reduce noise and cross-talk susceptibility. This unit may be connected to ASTi’s Axis, 

Prism (2-Channel version), and Spectrum remote USB module, or daisy-chained from another 

Iris*. 

*Not supported in all configurations. 

Overview of the Iris features: 

• Installed as close to operator as possible 

• Upstream connections to Spectrum, Axis, or another Iris 

• Downstream connection to another Iris 

• Two (2) independent, software-configurable audio inputs and outputs (1 per channel) 

• Six (6) Digital Inputs (3 per channel) 

• Two (2) Digital Outputs (1 per channel) 

• Two (2) RS-422 serial ports 

• Two (2) ASTi USB connections 

• +15 VDC required 

Figure 4: Iris - Front View 

Figure 5: Iris - Rear View 



Other Iris options include the 1U and 4 Channel Extended and Local Iris and the 6 Channel Iris. 

The 1U Local Iris, 4 Channel Local Iris, and 6 Channel Iris all connect directly to the Telestra for 

local distribution. The 1U Extended Iris and the 4 Channel Extended Iris both connect to the 

Prism via a CAT 5 cable of up to a maximum of 300 feet for extended distribution. For more 

information on these see the ASTi Audio Interface Module Technical & User Guide (ASSY 01 

UMAU UG 1). 

Figure 6: 1U Iris 

Figure 7: 4 Channel Iris 

Figure 8: 6 Channel Iris 



2.2.2. Axis 

The Axis provides connection and distribution for ASTi USB-based peripheral devices local to the 

Telestra. The Axis may support up to eight (8) Iris devices. When powering on the Axis, the red 

LED on the rear panel of the Axis module will light when power is applied to the unit. On the 

front of the Axis the upper green LED will light when the connected USB device has been properly 

identified by the software on the Telestra. The lower yellow LED will light when there is a 

USB-related problem. 

For more information on the Axis see the ASTi Local Distribution Module Technical & User 

Guide (ASSY 01 UMLD UG 1). 

Overview of the Axis features: 

• Distributes digital audio to peripheral devices within 21' of the Telestra platform 

• Upstream connections to Telestra USB port 

• Downstream connections to up to eight (8) Iris devices 

• Four (4) Type A USB connections 

• One (1) Type mini-B USB connection to Telestra 


Figure 9: Axis - Front View 

AXIS 

Figure 10: Axis - Rear View 

Out A Out B 

Out C 

Out D 


AXIS 

In 

Power 

+15VDC 



2.2.3. Prism 


The Prism modules allow the Iris devices to be located up to 300 feet away from the Telestra. 

There are two types of Prisms. The 2-Channel Prism supports two (2) Spectrum units plus two (2) 

local ports, while the4-Channel Prism supports four (4) Spectrum units. The red LED on the rear 

panel of the 2 or 4 Channel Prism will light when power is applied. 

For more information on the Prism see the ASTi Prism & Spectrum Remote Distribution Modules 

Technical & User Guide (ASSY-01-UMRXRD-UG-1) 

Overview of the Prism features: 

• Distributes digital audio to remote devices up to 300' away from Telestra 

• Upstream connections to Telestra USB port 


• 4-Channel Prism 

• Downstream connections to up to four (4) Spectrum devices 

• One (1) USB, mini-B type connector to Telestra 

• Four (4) RJ-45 connectors to Spectrum units 

• 2-Channel Prism 

• One (1) USB, mini-B type connector to Telestra 

• Two (2) RJ-45 connectors to Spectrum units 

• Two (2) USB, A type connectors to Iris devices 

Figure 11: Prism (4-Channel) 

Figure 12: Prism (2-Channel) 



2.2.4. Spectrum 

The Spectrum module connects to the Prism allowing Iris devices to be located up to 300 feet 

away from the Telestra. The Spectrum supports up to two (2) Iris devices with two (2) additional 

ports for future ASTi USB devices. The green power LED will light when power is received from 

the Prism unit. A separate power supply for the Spectrum is not necessary. The green connector 

LED will light when the Spectrum is connected to a Prism and when the Spectrum is detected in 

the Telestra software. 

For more information on the Spectrum see the ASTi Prism & Spectrum Remote Distribution 

Modules Technical & User Guide (ASSY-01-UMRXRD-UG-1). 

Overview of the Spectrum features: 

• Receives digital audio from Prism and distributes to local devices 

• One (1) RJ-45 connector to a Prism unit 

• Four (4) USB, A type connectors to USB devices (2 Iris units + future modules) 

Figure 13: Spectrum - Front View 

Figure 14: Spectrum - Rear View 


2.2.5. Ancillary Equipment 


In addition to the Telestra USB hardware, there are several pieces of peripheral equipment that 

connect to the USB hardware. These include but are not limited to: 

• Headsets, microphones, and speakers 

• Cables 

• Press-to-talk (PTT) switches 

• Touchscreen Display 

Refer to the ASTi web site (www.asti-usa.com) for details about options, pricing, and ordering 

information. 

Figure 15: Ancillary Equipment 

Handset Hand Mic Headset 4-Channel PTT 

Speaker Fostex Speaker Table Mic Touchscreen Display 



3.0. Software Overview 

3.1. Telestra 

The Linux-based operating Telestra runs in real-time framework. The system runs in three (3) levels 

including: 

1. 

2. 

3. 

Embedded Mode-In 

Embedded mode the system will boot, load and run the default 

MBV model. This is the recommended boot mode. 

Development Mode- 

In Development mode the system will boot and load, this mode is 

used when developing models in MBV. 

Recovery Mode- 

This mode is not recommended unless the Telestra crashes and development 

mode won’t run. In Recovery mode the system boots straight to the prompt for 

debugging. Please contact ASTi for more information. 

Telestra supports a variety of additional software services and packages to meet even the highest 

of communications simulation requirements including: 

• 

• 

• 

• 

MBV-Model 

Builder Visual is the Telestra audio and communications visual runtime environment. 

RMS- 

The Remote Management System is a specialized web server that provides complete 

sight and control of ASTi devices on the simulation network, ranging from stand-alone to 

multi-site, exercise-wide network configurations. 

HLA Communications-For 

High Level Architecture (HLA) applications, Telestra come 

with ASTi’s federate software and various debug tools pre-installed. 

High-Fidelity (HF) Radio Environment- The 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, and solar activity. 

• Automatic Link Establishment (ALE) for HF radios- The ALE server is used in conjunction 

with the HF server to realistically simulate the functionality of modern HF ALE 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. 

• Satellite Communications- This software package provides high-fidelity satellite communications 

modeling, including adjustable voice delays, uplink and downlink frequency modeling, 

half- or full-duplex communications channels, satellite positioning, channel 

allocation, and passband discrimination. 

• Terrain Interface and Database- This software applies occulting and degradation effects 

to communication paths in the radio environment. 



• Link-16 Tactical Data Link (TDL)- This software package supports the current DIS version 

of TADIL-J protocol specification, and includes some of the following features: 

• Multiple JTIDS Class 2 style Terminal Simulation 

• Integrated Link-16 Transmission and Reception, with DIS/HLA Radio Environment 

• Interoperates with SISO TADIL-TALES DIS/HLA Standard (TSA levels 0 and 1) 

• Proper Link-16 Data Rate Simulation Based on Timeslot Allocation 

• NPG Buffer Management, Priority and Status Reporting 

• Stacked and Crypto Net Support 

• Generic Host Computer Interface 

• Low Cost 

• Network Time Protocol (NTP)- Allows the user specify and test connection to a network 

time server for synchronizing Telestra’s internal clock. See the RMS Telestra Networking 

page for Time Server settings. 

• Multicast Router- Distinguishes between multicast and unicast packets and determines 

how to distribute the packets. 



3.2. Model Builder Visual Development Environment 

ASTi’s powerful and comprehensive Model Builder Visual (MBV) communications and audio 

development/runtime environment integrates seamlessly with RMS and the Telestra. MBV provides 

the user with a sound and communications simulation model development environment 

with many of the same features, capabilities and a similar toolset used in Model Builder software. 

In addition, MBV includes the visual approach to building and testing sound and communications 

models. Running models in MBV is also useful when troubleshooting. 

Note: ASTi does not recommend continuously switching between RMS and MBV while working 

in Development mode. 

Overview of features include: 

• Available only in Development or Recovery modes 

• Graphical user interface front-end for model development 

• Component library 

• Folder-based structure 

• Model explorer window for easy navigation 

• Model loader interprets and loads model inside ASTi's real-time framework 

The assets folder represents the physical hardware. The user can right-click on objects to give 

them descriptive names, ex. Iris, speakers, subwoofer, cable, mics. 

Overview of starting a new model: 

1. Add an Iris in the Assets Folder 

2. Go to RMS pages and map it 

3. Under Iris model settings set the gain settings 

4. In MBV, open the model folder and add an Iris cable in the workspace. Note an Iris can 

have more than one cable b/c of different channels. 

5. To add audio input, middle-click the Iris and add audio inA and audio outA, double-click 

the Iris object. Then in the schematic click input A and view the scope. 


Figure 16: MBV Startup Screen 




Figure 17: MBV Model Folder 


Figure 18: Telestra Toolbar 




3.3. Remote Management System 3.x 

The Telestra 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 HLA Communications 

Environment, multicast routing capability, 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. 

Section 4.0. ‘Getting Started with Telestra and RMS’ provides an overview of instructions to navigate 

RMS. For additional information on RMS 3.x see the ASTi Telestra v3.0 User Guide (DOC- 

01-TELS-UG-3). 

Overview of RMS capabilities include: 

• Telestra software updates 

• Hardware 

• Model installation and management 

• Network parameters configuration 

• Model browsing and control 

• System reboot and shutdown 

• DIS network configuration and monitoring 

• Debugging 


Figure 19: RMS Telestra Status Page 




4.0 DIS 

4.1. DIS Interface 

The DIS interface carries the radio, network intercom, voice and data traffic, which is generated 

and received by Model Builder Visual. Within MBV each asset can be set to DIS or local only 

operation. This allows the user to have the ability to define DIS radios up to the processing limits 

of the platform. Global DIS settings can be configured through RMS. 

DIS Radio Basics 

Network configuration: 

• To communicate over DIS, this feature must be enabled by ASTi in your options file. 

• You need two DIS enabled network products (Telestra, DACS, PC’ver). 

• Local IP address and Mask 

• Broadcast or multicast IP address 

• UDP port 

• Checksum parameters and DIS PDU timeout values 

• DIS Site and Host Values 

• Other/Advanced 

Model configuration: 

• Ensure the DIS IDs are unique and radios are in the same exercise. 

• Match modulation type, frequency, Bandwidth, modulation, crypto state, Frequency Hopping/HQ 

settings, etc. for the radios. 

• MBV decodes incoming audio based on signal PDU. 

• Support of multiple simultaneous exercises (up to 255). 

DIS PDU Types 

While this is a course on the Telestra and MBV software, it is important to understand the DIS 

interface traffic and its characteristics. When the DIS interface is used to carry model communications 

information the packet format is “IP|UDP|DIS_PDU” over standard Ethernet. The UDP port 

setting is configured through RMS. The DIS PDUs contain all of the pertinent information such 

as: 

• Voice communication 

• Tactical Data communication 

• Radio Parameters (frequency, location, Tx power, DIS IDs, exercise #, etc.) 



DIS IDs are broken down into site, host, entity and radio IDs. The 4 set string: 

site:host:entity:radio (for example: 10:20:30:40) must be unique for each radio on the network. 

While there is not a steadfast rule for setting up the IDs, one common scenario is to associate the 

site and host IDs with a physical location, the entity ID with a telestra and then have individual 

radio IDs for each radio instance. 

There are four types of PDUs detailed in the following sections. 

4.1.1. TX PDU 

Transmitter PDUs are required for telestras to operate in a networked mode. They are both transmitted 

and received by telestra systems. The TX PDU is an informational PDU that is sent out 

periodically based on Tx Setting and contains information about: 

• Site:Host:Entity:Radio IDs 

• Radio frequency 

• Location 

• TX Power 

• Exercise number 

• Modulation 

• Bandwidth 

• Crypto parameters 

• Frequency Hopping/HQ parameters 

• State (On, Off, On_Tx or ACTIVE) 

Within RMS, you can see all active TX PDU IDs that have been received by a telestra. In RMS, 

you will see all local and remote DIS IDs on the net work. 

In short, Tx PDUs are a radio's (or other object in MBV, i.e. transmitter, network intercom) way of 

saying, “who, what and where I am.” Rx objects in MBV scan Tx PDUs to determine who is in 

range. Transmitter PDUs are put out periodically if the radio is stationary (five second default) or 

when the radio has changed state; that is moved, started/ended transmission, or changed parameters. 



4.1.2. Signal PDU 

Signal PDUs are required for telestras to operate in a networked mode. They are both transmitted 

and received by telestra systems. The signal PDU is a UDP packet, which contains encoded voice 

information or data messages. When actively transmitting or receiving from a radio, for example, 

you will Rx/Tx a continuous packet flow during this time. The audio is encoded with the settings 

(uLaw, PCM, CVSD) in a given radio/intercom object. The default audio encoding type can be set 

through RMS. Also within MBV you can override the default on and per radio buses. 

4.1.3. RX PDU 

The RX PDU is not necessary for MBV to run, however it is built into MBV as a standard feature. 

RX PDUs transmit receiver state information, such as the received power level. It is for informational 

purposes only, and does not cause the Telestra to make any adjustments based on the values 

received. The Rx PDU says, “who I am in tune with” for each receiver, and whether or not they 

are actively receiving audio. 

4.1.4. Entity State PDU 

Entity state PDUs are not necessary for MBV to run and are not generated by the telestra. The 

telestra receives entity PDUs to obtain position information for radios when an “Radio_Entity” 

object is used. For example, the radios in MBV can be moved by a Mod Semi Automated Force 

(SAF) entity generator. 


5.0. Host Interface 


The host interface is used to receive simulation state data for control of the local audio model(s). 

This host simulation computer will normally provide simulation state and sound model control 

parameters such as engine RPM, radio frequency, radio position, communications panel switch 

settings, etc. 

This data is transmitted over an Ethernet network to the telestra and received via the host interface 

network card. Communications with the telestra are asynchronous. The host computer transmits 

packets at the host defined iteration rate. The telestra ethernet hardware receives and buffers the 

packet in local memory. The value is then read into the model at a rate of 100 Hz. 

Some model state data and system health parameters can also be transmitted back to the host. 

Packet transmission for data being returned to the Host can take place in each model iteration, or 

be reduced in frequency via host setting parameters in RMS. Data received is buffered and 

brought in to the model using various control objects available in the MBV development environment. 

The user can inspect packet data through MBV and RMS. For transferring simulation state 

parameters, the telestra supports IEEE 802.3 standard UDP level protocol with IP addresses. The 

use of UDP facilitates the reception of state data from multiple simulation sources by selection of 

independent port numbers. The user will need to configure the telestra with the appropriate network 

settings to ensure proper network operation. The telestra can receive host data on 1 or more 

UDP ports for MBV. Additionally, the telestra can send host data on 1 or more UDP ports. 



6.0. Getting Started with Telestra and RMS 

6.1. Cold Starting Telestra 

The Telestra Cold Start Procedure allows the users to build Telestra systems from scratch. There 

are three main reasons for using the Telestra Cold Start Procedure. 

1. Installing the latest software version 

2. Rebuilding a damaged hard disk 

3. Creating spare hard disks 

The following provides an overview of the Telestra Cold Start Procedure for detailed information 

on the procedure please see the ASTi Telestra Cold Start Procedure (DOC-01-TELS-CS-3). 

4. Verify BIOS settings match configuration settings listed in the Telestra Cold Start Guide 

5. Turn on the Telestra system via the power switch on the front of the chassis. 

6. The system may or may not fully boot, and you may receive an error message. 

7. Insert the Telestra Software CD into the CD-ROM drive. 

8. Reboot the system using the “Reset” button on the front of the chassis. 

9. The system will begin to boot from the CD. You will be given the option of installing the 

software with or without a graphical interface. At the “boot:” prompt, press the ENTER 

key to install in graphical mode. 

The screen may go blank for about a minute as the X server (graphical interface) starts. 

This is normal, and the process should not be interrupted. 

10. The Telestra Software Installer will load, and the software installation will proceed without 

any further user action. 

11. When the installation is complete, the CD tray will slide open. Remove the CD from the 

tray. 

12. Click the “Exit” button in the graphical interface if you have a mouse connected to the 

Telestra system. Otherwise, press the ENTER key to select “Exit”. 

13. The Telestra system will reboot and start from the hard disk. 


6.2. Uploading Options File 


The Telestra Options file is a program-specific encrypted file containing software packages for all 

of the Telestra systems delivered under that program. A single Telestra Options file may be 

installed on multiple Telestra platforms but will only activate the appropriate software packages 

on each platform. The software functionality, as defined by the Telestra Options File, is linked 

directly to the Telestra system’s hardware configuration. The Telestra Options screen in RMS 

allows the user to manage the Telestra Options file. 

Overview of the Options File Background 

• The Options file contains the software license key, which is required for MBV operation. 

• The Options file enables certain software modules available on the Telestra platform (e.g. 

HF server, Terrain server) and specifies the number of credits allocated to the Telestra 

• The number of credits determines the scope of the models that can be created and run in 

MBV. 

• The Options file is keyed to the MAC address of Telestra 

6.2.1. Instructions to Upload the Options File 

1. Insert the Telestra Options CD into the machine running the RMS browser. 

2. The following steps apply only if the Options CD has been inserted into Telestra: 

2a. Go to console 

• In Embedded or Recover y Mode, press ALT-F2 

• In Development Mode, press CTRL-ALT-F2 

2b. Login to console as root 

2c. Type “mount /cdrom” at prompt 

2d. In Development Mode, press ALT-F7 to return to X Windows environment 

2e. ** After uploading options file per the steps below, return to console and type “eject” 

at prompt 

3. In the RMS browser, go to the Telestra >> Options screen 

4. Select the “Choose File” button to locate the file on your local workstation. 

5. Select “Upload New Options File” button 

Important: Selecting an Options File with the same name as the currently-installed Options 

File will result in the new file over-writing the existing file. 

Click on the filename of the existing Options File to download it to your local workstation for 

archiving and backup purposes. 



Figure 20: RMS Options File 


6.3. Configure Basic Settings 


RMS allows user to enter basic information that identifies and describes a Telestra platform. The 

Telestra >> Preferences screen shows the system’s basic settings, such as installation and contact 

information. It also provides the ability to add and delete Telestra user accounts, which are important 

in MBV model management. Settings include: 

• Description (e.g. Comms Telestra) 

• Installation Facility (e.g. NLX Corporation) 

• Installation Location (e.g. Sterling, VA) 

• Installation Trainer (e.g. E-2C WST) 

• Contact Name 

• Contact Phone 

• Contact Email 

Figure 21:Telestra System Status 



6.4. Network Settings 

RMS allows the user to configure the following network settings on the Telestra platform. 

• General Networking. This section encompass network-wide, interface-independent settings 

such as Autodiscovery, DNS nameserver and router gateway IP addresses. 

• Time Server. This section allows you to specify and test connection to a network time 

server (NTP server) for synchronizing Telestra’s internal clock. Other settings allow you to 

tweak Telestra’s NTP client variables. 

• Ping Utility. Enter another computer’s hostname or IP address to send five pings (echo 

requests) to it. Positive response indicates that computer is reachable over the network, 

using any of Telestra’s three network interfaces. 

• Network Interfaces. These sections allow you to specify IP address, card mode and subnet 

mask for each of Telestra’s three Ethernet interface cards. 

Operational Warning: Making changes to the interface settings (especially eth0), such as changing 

manual IP address, or setting card mode to DHCP may result in your not being able to access 

RMS at the original (previous) IP address. If you change these settings, you must then specify the 

new IP address in your browser’s Address slot to access RMS at its new network location. 


Instructions to Configure Network Settings 

1. In RMS browser, go to the Telestra >> Networking screen 

2. Click on the “Edit Configuration” link under the section of interest 

3. Enter data into appropriate fields 

4. Select “Make Changes” button to commit the changes 

Figure 22: RMS Telestra Networking Page 




6.5. Model Management 

Model management allows you to stop, reload, copy, delete or backup the model. In Development 

mode, each user’s “default” model will be loaded in MBV when it is launched. In embedded 

mode, the “Embedded Operation” default model is automatically loaded and started when the 

Telestra system is booted. Users can copy models from other users to work with them, but they 

cannot copy over other user’s models. 

For more information on Model Management in RMS, see the Telestra 3.0 Users Guide (DOC-01- 

TELS-UG-3), Chapter 6. 

Figure 23: RMS Telestra Models Management Page 


6.6. Detecting USB Devices 


The USB devices must be connected and running properly with the Telestra. There are two ways 

to ensure the USB devices are working. The first way of detection is by looking at the LED lights 

on the USB hardware. For more information on the location of the LED see the specific user 

guide for the device. 

The second way is through RMS Hardware>>Layout page. The Hardware Layout displays the 

arrangement of all detected USB devices. Each device has its own icon and the black arrow indicates 

the Telestra USB traffic. The blue arrow indicates remote distribution of USB traffic and the 

orange arrow indicates local distribution of USB traffic. The dotted arrow indicates a physical 

cable connection between USB devices. 

6.6.1. Instructions for discovering USB Hardware in RMS 

1. In RMS browser, go to Hardware >> Layout 

2. Select “Reset USB devices” button 

3. Wait for all devices to be detected 

4. Hardware layout will be displayed when detection is complete 

Figure 24: RMS Hardware Detection Page 



If the USB devices are not recognized disconnect all USB cables and connect in the following 

order. 

1. Connect Axis* and Prisms* and discover via RMS 

2. Connect 1 Iris* to Axis* 

3. Connect Spectrum* to Prism* and discover via RMS 

4. Connect remaining Iris* devices and discover via RMS 

*- power cycle the device (ie prism, axis) prior to connecting 

Step 1 Connect 

Axis and Prism 

Step 2 Connect 

1 Iris to Axis 

Step 3 Connect Spectrum 

to Prism via Cat 5 Cable 

Step 4 Connect remaining 

Irises 

Figure 25: USB Detection 

Iris 

Axis 

AXIS 

Telestra 

Out A Out B 

Out C 

Out D 


Iris 

Prism 

Spectrum 

Copyright © 2006 Advanced Simulation Technology inc. 31 

Iris 

Iris

6.7. Mapping Iris Devices 


There are two parts to mapping the hardware. First the user must setup the software side in MBV 

by adding Iris assets in the model. Then the user must map the Iris assets to the physical Iris 

devices in RMS. 

Figure 26: Hardware Setup and Mapping 

Hardware Setup and Mapping 

Step 1 (MBV) Assign Iris cables to Iris Assets 

Assets Folder 

“Pilot” 

Iris Asset 

Model Folder 

Iris Cable 

Iris Cable 

Step 2 (RMS) Map Iris Assets to Hardware devices (serial number) 

“Pilot” 3-xxx 

“Copilot” 3-yyy 

“Instr” 3-zzz 

Digital audio 

input and output 



Iris assets in the model route audio and digital I/O to physical devices. The physical “On-Wire” 

Iris devices must be mapped to Iris assets in the model. Iris mapping is saved with the model in 

the hardware mapping file. The following instructions provide an overview on how to map Iris 

devices. 

Instructions 

1. In the RMS browser, go to Hardware >>Mapping. You will see a list of Irises and quite a 

few “Map it” buttons. 

2. Select the “Map it” button to the right of the first Iris (or any of the Irises). This will open 

the Iris Hardware Assignments page (shown below). 

3. For each Iris component, select an Iris serial number from the pulldown list. 

4. Once all components have been mapped, select the “Map Hardware” button. 

5. Wait for the model to reload until the “Model is now Loaded” message is displayed. 

For more information on mapping Iris devices see the, ASTi Telestra 3.0 User Guide (DOC-01- 

TELS-UG-3), Chapter 6. 

Figure 27: RMS Iris Hardware Assignments Page 


6.8. Configuring Model Network Settings 


UDP cables in the model receive and transmit host data. The host network settings for UDP cables 

in the model must be configured in RMS. The RMS Models Host Interface page also lets you 

select the interface on which all multicast UDP host traffic is output. The host must configure the 

following settings: 

• IP address / Ethernet interface 

• UDP port number 

• Endianness 

• Periodicity (timeout period) 

The settings are saved with the model in the hardware mapping file. The user must reload the 

model to apply the changes 

Configuring Network Settings in RMS 

1. In the RMS browser, go to Models > Host Interface 

2. Configure the settings for all UDP cables 

3. Select “Change IP Addresses / Ports” button when complete 

4. Wait for the model to load until “Model installing complete” message is displayed 



Figure 28: RMS Models Host Interface Configuration Page 


7.0. Operation and Maintenance 

7.1. Saving Model Archives 


Models are saved through the RMS Model Management screen or through RMS Telestra Actions 

in RMS. Models are saved as tgz archive files. The archive includes all files and subdirectories 

under the model directory. Model archives can be uploaded to another user. by selecting “Copy.” 

Instructions to Backup in Model Management 

1. In RMS browser, go to Models >> Management screen 

2. Select “backup” link next to model to be saved 

3. Select the files to backup from the list which include: 

• Model 

• Model Folder 

• Services Folder 

• Assets Folder 

• Hardware Mapping 

• Components 

• Debug 

• Profiles 

• ICD 

• Soundfiles 

4. Select “Start Backup” and RMS will generate the model archive 

5. Select the download location in the file browser window 

6. Select “OK” to save model archive 

Note: RMS facilitates archiving and restoring only the models in the user accounts. If users 

choose to store any other information in their directories they are responsible for backing it up. 



7.2. Saving Settings 

RMS provides a backup utility that allows users to save current configuration in archive files for 

the radio environment including the DIS network settings and DIS protocol settings. The user can 

also backup the telestra configuration including preferences settings, network settings, and the 

options file. 

Instructions to Backup in Telestra Actions 

1. In RMS browser, go to Telestra > Actions 

2. Select the “Backup System Configuration” link 

3. Select the checkbox(es) next to configuration files to be saved or select “All” checkbox 

4. Select the “Start Backup” button 

5. RMS generates a configuration archive tgz file 

6. Select download location in file browser window 

7. Select “OK” to save file to browser machine 

Figure 29: RMS Telestra Actions 


Figure 30: RMS System Configuration Backup Page 




7.3. Restoring Settings 

There are two ways to restore model settings in RMS. The first is through the Model Management 

screens. There are two ways for the user to start a model installation or restoration in Model Management. 

The user can choose to upload a model from their workstation OR choose to restore a 

model archive already stored on the Telestra. 

For detailed instructions please see the Telestra 3.0 Users Guide (DOC-01-TELS-UG-3), Chapter 

6, Uploading & Installing Model Files. 

The second way to restore model settings in RMS is through the Telestra Actions screen. 

Instructions 

1. In RMS browser, go to Telestra > Actions 

2. Select the “Restore System Configuration” link 

3. Select the “Choose File” button 

4. Select “Restore Now” next to the model file you want to restore 

5. Check the files to restore or select the “Check All” button 

6. Select “Start Restoration” 

7. Restart your Telestra to apply the restoration. 


7.4. Installing Telestra Software Upgrade 


In RMS, the Packages Update System will display the Software Update screen, shown below. 

Telestra software updates may be installed without performing a system cold start 

Instructions 

1. In RMS browser, go to Packages >Update System 

2. Insert the Telestra Software CD into Telestra 

Figure 31:Telestra Software Upgrade 

3. Check the “Verify CD Checksum” box to allow you to verify the integrity of the installation 

media. The verification will fail if any file on the CD is unreadable due to scratches, 

marks, etc. 

4. Select the “Read CD” button 

5. Telestra mounts the CD and lists software packages to be installed (Please be patient this 

may take a few minutes). 

6. After the Telestra determines which packages to update, another page will display any 

appropriate release notes, and lists the packages to be upgraded on your system. 



7. Review the packages then select the “Install updates” button. The telestra will then proceed 

to install the necessary package updates. 

8. When done, RMS will display a confirmation screen, “Update completed successfully” 

wait for the message to display. 

9. Remove CD from drive 

IMPORTANT! At this point, you must remove the CD from the CD-ROM drive of the Telestra 

system before doing anything else! Failure to remove the update CD from the drive will result 

in a full-up system installation (including complete erasure of the hard disk) the next time the 

Telestra system is started. 

10. Reboot Telestra from Telestra > Actions page 


7.5. Hardware Readiness Tests 


RMS’ hardware readiness test allows you to verify hardware setup, cable connections and Iris 

operation. Navigate to Hardware Readiness to display a confirmation screen, shown below. 

Figure 32: RMS Hardware Readiness 

The test will create a custom readiness model based upon all the “on wire” USB devices that have 

been properly initialized. This readiness model provides testing of audio in and out channels, as 

well as digital in by way of PTT. To perform the test, you will need at least a headset for connecting 

to the Iris device(s) to be tested. The recommended test rig, consists of: 

• Iris-to-PTT cable (DB-15 male to female, 6-pin XLR) 

• Inline ASTi PTT box 

• Stereo headset with microphone and male, 4-pin XLR connector 

Running the Hardware Readiness Test 

1. Connect the stereo headset and in-line ASTi PTT to Iris Channel 

2. In RMS browser, go to Hardware > Readiness 

3. Select the “Run Readiness Test” button 

4. Verify that a tone is heard in the headset without distortion 

• On Channel A, a beeping tone is heard 

• On Channel B, a steady tone is heard 

• On either channel, a tone frequency changes when PTT is keyed 

• On either channel, a tone frequency changes with channel select knob position 

5. Verify microphone input is heard in headset without distortion 

Important: When you are done with the readiness test, you must reload the desired MBV model 

to replace the custom readiness test model. 



8.0. Model Builder Visual Introduction 

The user must operate in Development mode to create models in MBV. The user must setup a user 

account and password in RMS to operate in Development mode. 

8.1. Creating a User Account 

1. Boot the Telestra in Development mode. 

If a username and password is requested, use rmsuser and astirules for the password. Do 

not stay in Development mode with this username, you must create a new username. 

2. Select the RMS icon to launch the web browser and navigate to Telestra >> Preferences 

page. 

3. Left click on “Add New User Account.” 

4. Type in the new username and password and select “Create User.” 

5. Navigate back to Telestra >> Preferences. 

6. Under the Boot menu, select Development. 

7. Navigate to Telestra >> Actions page and select “Reboot Telestra System.” 

8. Once the Telestra reboots, type in the new username and password. 

You are now ready to begin developing models in MBV. 

Note: MBV takes a few minutes to start the real-time framework, load the components library and 

load the model. 

To develop a working model the user must know how to: 

• Add objects 

• Connect links to the objects 

• Route using the Channel Handle 

• Control the inputs using the ICD tool 

• Drive the hosts 


Figure 33: RMS Telestra Preferences Page 

Figure 34: RMS New User Account 




8.2. MBV Navigation 

While navigating in MBV is fairly self-explanatory, the following provides a quick overview. 

• To enter a folder in MBV either 

• Double-click on folder icon in workspace area or 

• Click once on folder in explorer window 

• To view components in MBV either 

• Double-click on component icon in workspace area or 

• Right click on component icon in workspace area then select “Open” 

• To run a model either 

• Select “Resume Scenario” from Scenario menu or 

• Press F3 key 

• To stop a model either 

• Select “Pause Scenario” from Scenario menu or 

• Press F3 key 

A few nuisances of MBV need to be mentioned before beginning model development. 

• When creating a new object/asset or a new link between objects/assets, the model needs to 

be reloaded before the object/asset can be edited or used. This is not to say that multiple 

objects can't be placed and linked together before reloading, but it is good practice to reload 

after a group of objects/links have been created. Note: The links in MBV represent audio 

when red, and they represent controls when blue. 

• Saving the model. Whenever something is changed in the model, MBV automatically saves. 

This is why there is not “Save” function. The “Save As” function creates a copy and any 

further edits are saved on that copy. Use this option if you want to retain a certain state 

When creating a new object/asset or a new link between objects/assets, the model needs to be 

reloaded before the object/asset can be edited or used. This is not to say that multiple objects can’t 

be placed and linked together before reloading, but it is good practice to reload after a group of 

objects/links have been created. Note: The links in MBV represent audio when red, and they represent 

controls when blue. 

Note: When naming models the model name cannot have spaces, the user should insert underscores 

(_) for spaces, for example, MBV_Model_Tutorial. 


8.3. Component Overview 


The Components consist of Audio, Control, DRED (Daily Readiness), Engine, Intercom, Platform, 

and Radio components. These components provide the palette from which a user creates a 

model. 

Audio components generate sounds. This group includes components such as a wave generator, 

an amplitude modulator, an audio mixer, and a vox. This component plays sound object filter. 

Control components provide logic for a model. This group includes components such as a logic 

table, a math function, a lookup table, byte control, etc. 

DRED components include objects that are used to create the daily readiness test model. The 

readiness model is dynamically generated when triggered by a user via Telestra RMS. This group 

includes components such as Amp mode, bit to Byte, Gain, input, math functions, mixers, and 

wave. 

Engine components include both rotor and engine sounds. The audio from the engine and rotor 

components changes dynamically based on inputs such as RPM, whine frequency, and gain. 

Intercom components relate to internal communication paths within the model. This group 

includes the communication panel and local intercom buses. Audio on intercom buses is never 

transmitted onto the voice network. These buses are used internally to pass audio around. If put in 

a radio, for example then audio can be sent out on the DIS network. 

Platform components simulate power distribution to both individual assets such as radios, intercoms, 

and communication panels and to groups of assets. 

Radio components include communication assets whose audio is transmitted to or received from 

the voice network. The radio components include generic radios, transmitters, receivers, network 

intercoms, etc. 

• Schematic 

• Displays graphical layout of component code 

• Primitives (building blocks of component) 

• Mousing over primitive displays current values of primitive variables 

• Connections between primitives 

• Data Viewer 

• Displays primitive details in a list format (tree view) opposed to the graphical layout 

of the schematic. The user can view or set values of primitive variables. 

• Link Inspector 

• View incoming and outgoing link data 

• Right click on source or destination component to access menu 

• Go to data view tab of source / destination component 

• Go to link inspector tab of source / destination component 



8.4. MBV ICD Tool (with Tutorial) 

The Interface Control Definition (ICD) tool allows a host computer and an MBV model to share 

information via ethernet UDP packets by labeling and standardizing the information contained in 

the UDP packet. In other words, the ICD tool defines the XML packet layout. When creating an 

ICD, the user creates the packets that makeup the ICD and the members that makeup the packets. 

For every model with network host inputs the user must create a new ICD. Before getting started 

boot MBV on your Telestra and login. The remainder of this section describes how to create a 

new ICD and provides a step-by-step tutorial. 

Step 1: Creating a New ICD 

1. Navigate to file in the top menu bar and select ‘Start a New Model.’ Name the new 

model 

ICD_Tutorial 

Note: This will be an “empty” model focusing on demonstrating the ICD tool. 

2. Navigate to the top menu bar and under Tools select ‘ICD Tool.’ Then open the ICD tool 

and click ‘Create’ to create a new ICD. 

Figure 35: Creating an ICD 


Step 2: Naming the ICD 


You will need to name your ICD. This name is just an arbitrary name that will identify the 

ICD from the others. The standard naming convention is to use a name which corresponds 

with the function of the ICD. 

Figure 36: ICD Name 



8.4.2 Adding Packets 

The packets makeup the ICD. The user enters the values for each packet which will makeup the 

packets structure. Existing packets can also be edited by selecting a packet under the ‘Current 

Packet’ pull down menu. 

The following inputs define the packet. 

• Endian- Selects the default Endianess (Big or Little) of the packet data. This can also be set 

and overridden in the RMS>>Host pages. ASTi recommends using RMS to set this value. 

• Direction- Defines whether the packet data is to be received as input or is to be transmitted 

as output. 

• Timeout (ticks)- This value represents the number of 100 Hz system frames that can occur 

before loading the initialization/default values set in the UDP inputs assets in your model. 

Loading these values will only occur if packet information is not received on this port 

within the time represented by the number of frames. If a packet is received in this time 

frame, the count is rest. A value of zero (0) means the interface never times out and initialization/default 

parameters are not loaded. 

• Port- The port number selects the default UDP receive port for the packet data if this is an 

input packet, or the transmit UDP port if this is an output packet. This can also be set and 

overridden in the RMS>>Host pages. ASTi recommends using RMS to set this value. 

• IP Address- If the packet is an output packet this field will allow setting the destination IP 

address (i.e. the host computer you wish to send the data to). This can also be set and overridden 

in the RMS>>Host pages. ASTi recommends using RMS to set this value. 

Figure 37: ICD Packet Information 

Step 3: Adding a Packet to the ICD 

1. Select the packet icon from the top tool bar and name it 

Packet1 

2. Select Packet1 from the ‘Current Packet’ pulldown list. 

You have now added a packet now you must add members, continue to the next tutorial. 


8.4.3. Choosing a View Mode 


There are two ways to view the ICD interface, most of the changes will be performed in ‘Offset’ 

view. 

• Offset view shows the “variable” name. This is the name of the packet entry at its lowest 

level. One level up from this is a wire name. 

• Wire view allows abstraction of the variable name. It is the name you see on the MBV 

desktop when you middle-click on a component to create a link. It’s also the name you see 

in the Host UDP assets and cables in your model. Wires can also be bundled by adding a 

name to identify the bundle. 

8.4.4. ICD Packet Members 

The user adds members to define each packet. The following inputs must be defined for each 

member. 

• Name- Enter the variable name. If you change the variable name of an existing member 

than the wire name under the wire view needs to be changed as well. 

• Type- Sets the variable type and data type for the member. ASTi recommends sticking to 

common/basic variables. Note: This variable type must match the variable type of 

the component variables it connects to in the model. 

• Offset- Sets the offset location in the ethernet packet for the data associated with this member. 

• Bit Offset- This is only needed for bit packed booleans. 

• Size- Identifies the size of the data in bytes. 

• Units, Range, and Comments- These are used to provide additional information and are 

not used for anything functional. 

• Default- Not used. 



Step 4: Adding a Member 

You can add a member by clicking the icon button at the top of the ICD page or right click in 

the workspace (shown below). You’ll be asked to provide a member name (in this case the 

same name will be used for the wire names.) 

Add a member and name it, 

SineWave_Frequency 

Note: The user can also edit, move, or delete existing members by right clicking or 

choosing the proper icon in the tool bar. 

Figure 38: Adding Members 


Step 5: Defining the Member 


After adding a member, you must define the member name, type, offset, bit offset, and size. 

Hint: To find the type variable for your member open up the object and view the schematic 

(see arrow 1 below). Then double-click on the input option needed (2). Look under the Type 

values to find the value needed (3). Return to the ICD packet member inputs and enter the 

Type (4). 

After you have finished editing the packet select ‘Ok’ and your member is created. 

Figure 39: Setting the Member Type 



8.4.5. Setting Offsets 

To set offsets the view mode must be in Offset mode. There are several ways to edit offsets individually 

or grouped together. 

• Edit offsets by editing each member through the edit member window. 

• Highlight a particular member and use the +/- keys to increment and decrement the current 

offset number. 

• Highlight a block of members (drag your mouse across them or click on the first entry and 

then shift/click on the last entry) and use the +/- keys to increment and decrement all offset 

values in the highlighted block. 

Hint: You can also select different members across the packet and use the control button 

to perform the same operation (i.e. the members do not need to be in a continuous block.) 

• There is also an auto offset function which will automatically set the offsets of all the highlighted 

members. Highlight a block of members and right-click to select “auto Index/offset.” 

This will set the offsets starting at the input offset number (shown below). 

Note: You can click on any of the column names to sort the list (alphabetical, etc.) The tool does 

not currently check for overlaps so be diligent! 

Figure 40: Setting Offset 


8.4.6. Saving Changes 


After completing changes to the ICD the user should either Save or Save As. Use Save As to 

change the name of the XML file to help track revisions. This saves the changes to the XML file 

but have yet to be implemented in the model. 

8.4.7. Implementing Changes in Your Model 

After saving the ICD XML file, the changes need to be added to the model. To add the 

changes to the model, click on the ‘Create Assets’ (magic wand) icon button or select 

this action from the top menu under model. 

MBV will then recreate the Host Assets in the model using the currently selected (and updated) 

ICD file. These changes will be made to the currently loaded MBV model. A prompt will appear 

when this process is complete. Larger models may take a few minutes, so be patient. 

After implementing the changes, reload the model in MBV and look for warning/error entries in 

the reporting screen at the bottom of the MBV development environment window. 

Hints: You can also select the ‘Clear MBV Log’ entry under the Debug menu before reloading 

because it is easier to find any errors. Watch for warnings regarding type or size mismatches and 

link errors which could occur if you change the wire name of a variable. To correct type/size problems 

you'll need to return to the ICD tool. To correct link errors you'll need to create the new link 

and delete the old one. Reload after these changes and check the reporting window to see if you 

have cleared everything. 



8.5. Changing an Existing ICD 

The user must change the existing ICD to make changes to the host interface. The following 

describes how to edit a member in a step-by-step example. 

1. Load the model you wish to change and select the ICD tool. 

2. When the ICD tool opens you will have two options: 

A) Create a new ICD or 

B) Open an existing ICD 

You will choose to open an existing ICD. 

When you select to open an existing ICD you will be given a list of XML files from previous 

ICD files generated and saved by the tool for the currently loaded model. 

Note: If you don’t purge these files you can rack up a long list. The ICD files are found in 

the ICD folder one level down from your top level model folder. 

3. Pick the file you wish to change (this will most likely be the latest file). 

4. Change the view mode to Offset. 

5. Double-click on the entry/member you wish to modify, or click to highlight the entry. 

6. Right click and select Edit Member/Wire, or click on the gear icon at the top of 

the page. The Edit Packet Member window will pop up. 

After making changes to the ICD tool, save the changes and then click the “Magic 

Wand” tool to create the asset. 





9.0. Creating a Basic Model in MBV 

The following subsections in this chapter will walk the user through creating a basic MBV model, 

demonstrating how to use the most common objects in MBV. The model will be built in 4 blocks, 

or tutorials, which will build upon each other by adding new components and illustrating new 

concepts and tools. The following diagram outlines the final model. 

Counter 

Trigger Comparator 

Dur. 10 ms 

End 1 

Start 0 

X Type 

Y 

Z 

X 

TableXY 

X Y 

1 100 

2 200 

3 300 

4 400 

Y 

Sine Wave 

Amp 

Freq 

ICD 

5 500 

Iris Cable 

Vox Threshold 

Vox Enable 

PTT 

Vox 

Vox Threshold 

Vox Enable 

PTT 

Audio In Audio 

Figure 41: Model Tutorial Overview 

In order to successfully complete all the tutorials, you will need the following hardware: 

• One Iris properly connected to the Telestra 

• Headset 

4Ch.PTT 4Ch.PTT 

Decoder 

• Microphone 

• 4 Channel PTT Switch 

• Speaker (optional) 

Trigger 

Psound 

Trigger 

Index 

Sound 1 

Sound 2 

Sound 3 

IcomTx 

IcomTx 

IcomTx 

BitToByte 

IcomRx 

IcomRx 

Mixer 

Control 

Input 1 

Input 2 

Input 3 

Rx Vol 1 

Rx Vol 2 

Rx Vol 3 

IcomRx 

Master 

Math 2 

Volume 

Y= (scale)=.01 

The first tutorial will focus on the wave object and three different control objects used to control 

and modify the input fields of the wave object. Specifically, the Wave object will generate a sine 

wave. A TableXY control object will determine the sine wave’s frequency. The Amplitude will be 

driven in a square wave fashion using a counter and a comparator to generate the square wave 

amplitude input. The ICD tool will be utilized to drive inputs into the control objects, demonstrating 

a host controlling the sinewave. 

Copyright © 2006 Advanced Simulation Technology inc. 57 

Bit 0 

Bit 1 

Bit 2 

0-100 

Rx Volume 

X 

Audio Out 

Iris


The second tutorial will focus on the Vox object. Audio from a mic will route through the Iris into 

the Vox, and then back out through the Iris and into the headset as sidetone. The ICD inputs will 

drive the Vox parameters. 

The third tutorial will focus on play sounds using the PSound255 object. This tutorial will demonstrate 

how the Sound Editor library tool is used and how the Psound255 object is used to manage 

sound files within a model. A Four Channel PTT switch will be used to select which play sound 

files will play when triggered via host control. 

The fourth tutorial will focus on the mixer object and how to use channel handles to internally 

route the audio generated from the previous three tutorials to the mixer object. A Math2Function 

object will control Audio volume and a BitToByte object will control the mixing of the audio signals. 

Before beginning each tutorial refer to the Telestra MBV Quick Components Reference Guide 

(DOC-01-MBV-QCRG-1)for explanations of each component. 



9.1 Tutorial 1 - Sine Wave 

This tutorial will consist of four (4) components. The Iris object and cable will be used with this 

portion of the tutorial. A Wave object will generate a sinusoidal wave whose signal will be routed 

via the Iris cable to an Iris asset. The Frequency of the sine wave will be controlled by the 

TableXY component. Host control (ICD tool and packet) will drive input integers with values of 1 

through 5 into the TableXY object and a corresponding frequency value will output from the 

TableXY object and drive the frequency field of the sine wave. 

Two components will work in tandem to modulate the amplitude of the sine wave. A Counter 

object will continuously count and input its signal into the Comparator object. This will cause the 

Comparator object to alternately output a 0 or 1 which in essence becomes a square wave signal. 

This square wave signal drives the input of the amplitude field of the sine wave. The final output 

of the sine wave will be a beeping sound. 

By the end of this section the user should be familiar with: 

• Creating a new model 

• Setting up Iris assets 

• Mapping Model Iris's to 'on the wire' Iris's 

• Using Model Subfolders 

• Generating a Sine Wave 

• Routing audio from a model to a headset 

• Using a Counter, Comparator, and Table object 

• Driving component fields with host controls (ICD Tool) 


Step 1: Creating a New Model 


Open MBV in development mode and left click on “File” in the upper left, select “New”, name 

the model 

MBV_Component_Tutorial 

Remember: The model names cannot contain spaces. Underscores must be used in lieu of space 

characters. 

Your screen should look like the figure below. This creates a blank canvas for building your 

model. 

Figure 42: Creating a New Model 



Step 2: Setting up the Iris 

Before building the sine wave you must setup the hardware assets in MBV to allow you to hear 

the signal. 

1. Under Model Explorer (upper left window in MBV), open up the Assets tree by left clicking 

on the plus symbol next to Assets. 

2. Select the Telestra. 

3. Right-click on the workspace. 

4. Select “iris” and name it 

Iris1 

5. In order to edit the Iris values, you must 

reload your model. The reload button is the 

circle with a blue arrow rotating clockwise. 

6. After reloading, double left-click on Iris1 

asset to bring up its properties. 

7. Next you will set the gain levels, this is done to hear the audio out after you finish creating 

the model. To do this, scroll down to the atmel_gains box and double-left-click on it to 

open the properties. 

8. Set all the values to 15 by double-clicking each name and typing in the value. Select “Set 

Default” and select Close. 

Figure 43: Setting up the Iris 


Step 3: Creating the Sine Wave 

1. Under Model Explorer, open up the Model folder by left-clicking on it. 

2. Right-click in the workspace, under Audio select Wave and name it 

Sine_Wave 

Remember: The object names cannot contain spaces. Underscores 

must be used in lieu of space characters. 

3. Reload the model, so you can edit the fields in the Sine 

Wave. 

4. Open the Sinewave object and in the schematic open 

wavetype and select the sine wavetype by double-leftclicking 

on kin and selecting it from the drop down 

menu. This must be done to hear sound in the model 

after the model is finished. 

5. Navigate back to the workspace and right-click to add 

an IrisCable, name it 

IrisCable1 

6. Reload the model. 

7. Right-click on IrisCable1 and select ‘assign to an Iris’, then select 

Iris1 




8. To route the audio from the Sine Wave out to the Iris middle-click on the Sine Wave 

object and select 

from Signal >> all of 

Important! Between this step and the next step, once you select the ‘all of’ with the middle 

mouse button, you can only navigate the folders with the left mouse button before 

finishing the link with the middle mouse button. If you do hit another button you will 

lose the link “focus” you have from the sine wave. 

9. Then middle-click on the IrisCable1 and select 

to stereoOperator >> AudioOutA 


Step 4: Creating the Table 


1. Right-click in the workspace and select Control and TableXY16, rename this to 

Sine_Freq_Table 


3. Open the Sine_Freq_Table, double-click Table and open the tree table. Expand the table 

data and set Data X and Y values for the data fields 0 through 4. The ‘X’ values range 

from 1 to 5. The ‘Y’ fields will be the corresponding frequencies, shown below. 

Note: Continue to set values as ‘Default.’ 

Close the window after setting the values. 



4. Then double-click on the ‘X’ input from the schematic view. In the fields list, under Type 

view select Uint from the pulldown list. Set as Default and close the window. 

5. To drive the table output into the Sine Wave navigate back to the workspace, middle-click 

on the Sine_Freq_Table object and select 

from Output_kout_float 

Then middle-click on the Sine Wave object and select 

to Frequency 

The result should be linked as shown below. 



Step 5: Driving the Amplitude by Creating a Counter and Comparator 

1. To add the counter component right-click in the workspace and under Control select 

Counter. Name the new counter object 

Sine_Amp_Counter 

2. Reload the Model. 

3. Double-click the Sine_Amp_Counter to set the values. 

Open Duration and set kin to 10. 

Open End Value and set kin to 1. 

Open Start Value and set kin to 0. 

Then open the Counter and set Continuous to TRUE. 



4. To add the comparator component return to the workspace and right-click and under Control 

select Comparator. Name the comparator object 

Sine_Amp_Comparator 


6. To set the comparator values, open the comparator object. 

Open the ‘Y’ and set the kin to 0.5. 

Open Compare and set the LessThan value to 1. 



7. To link Sine_Amp_Counter inputs to Sine_Amp_Comparator navigate back to the workspace 

and middle-click on the Sine_Amp_Counter object and select 

from Count_kout_float 

Then middle-click the Sine_Amp_Comparator and select 

to X 



8. To set the sine wave amplitude middle-click the Sine_Amp_Comparator object and 

select 


Then middle-click the Sine Wave and select 

to Amplitude 




1. Navigate to tools in the top menu bar and click on ‘ICD Tool.’ Create a new ICD and 

name it 

Host_ICD 

Note: The ICD name cannot contain spaces, using spaces may cause problems in MBV. 

Underscores must be used in lieu of space characters. 

2. Then create a new packet and name it 

Component_Tutorial_Inputs 

(This ICD and packet will be used throughout section 9.0 tutorials.) 

3. Under Current Packet, select the new packet Component_Tutorial_Inputs. 

4. Add a new member and name it 

Sine_Counter_Trigger 

5. Set the member information as shown below. 

Remember: To find the type open the Sine_Amp_Counter object and open the Trigger 

input. The default type is basic/boolean, as shown below. 



6. Add another new member and name it 

Sine_Freq_Table_Select 

The type for this member can be set to various options but for this tutorial set it to basic/ 

uint32. 

7. Highlight both the members and right-click, select ‘Auto Index/Offset’ and set to 0. 

8. Save the new ICD and then hit the “magic wand” tool to create the assets. 


Step 7: Linking the ICD to the Model 


1. Navigate back to the workspace. Right-click and add a UDPinCable and rename it 

Tutorial_Inputs 

2. Right-click on Tutorial_Inputs and 

assign the UDP cable to the 

Component_Tutorial_Inputs packet. 

3. To set the trigger in the Sine_Amp_Counter middle-click Tutorial_Inputs and select 

from host packet >> Sine_Counter_Trigger 

4. Then middle-click Sine_Amp_Counter and select 

to Trigger 



5. Middle-click on Tutorial_Inputs and select 

from/to host packet >> Sine_Freq_Table_Select 

6. Then middle-click Sine_Freq_Table and select 

to x_kin_uint 

7. Reload the model and the log list should look like the list below (no errors). 

Remember: The log list is found at the bottom of the main MBV page. Drag it up with the 

mouse arrow to allow a larger viewing area. 


Step 8: Mapping the Iris 


You will route the audio to the Iris cable using RMS. This step maps the actual Iris hardware 

device to the Iris1 asset you created in MBV. Before you can map the Iris you must load the current 

model in RMS Model>> Management. 

1. Open RMS and navigate to the Hardware>>Mapping page. 

2. You should see two Irises that have a “Map It” button under the Model Asset Column. 

3. Select the first Iris “Map It” button, in the drop down box of Iris1, select one of the two 

numbers. The numbers correspond to the actual Iris’s serial numbers. If you look at the 

front of your two Irises you should see the serial numbers in the upper right hand corner. 

4. After choosing the serial numbers, select “Map Hardware”. 

5. Return to MBV and in the top toolbar under Models, select “Start Model”. 

Figure 44:Mapping the Iris Hardware 



Now you have completed your sine wave, plug your speaker or headset into channel A of the Iris 

you just mapped. To hear your different sine wave tones open the Component_Tutorial_Inputs 

UDP cable and change the Sine_Freq_Table_Select values between 1-5. You should hear the different 

frequencies as you change the values. 


Step 9: Organizing Your Model 


As you continue with the following tutorials in section 6.0 or as you build a large model, you will 

want to organize different parts of the model into subfolders. 

1. Highlight the entire model workspace created in this tutorial, right-click and select cut. 

2. Right-click and create a new model subfolder and name it SineWave. 

3. Paste the contents of your model into the SineWave folder. 

Figure 45: Final Model 



9.2. Tutorial 2- VOX 

This section is intended to follow and build upon the model from Tutorial 1 in section 9.1 

The second tutorial will focus on the vox object. This tutorial will demonstrate how to route audio 

into the model from an 'on the wire' object. In this case, we assume it is an operator using a mic to 

transmit a voice signal. The additional components in the model will be the vox object, Iris cable 

and UDP input cable. The audio input will be routed back out to the Iris so the operator can hear 

his voice, much like a side tone. A PTT switch can be used to enable/disable voice signal output. 

The host driven input from a UDP pack can enable/disable the Vox to detect the mic sound. 


• The vox object 

• Enabling/disabling the vox object and adjusting its detection level 

• Using the PTT switch to activate voice transmission 

Step 1: Creating a Vox subfolder 

1. Click in the workspace under the main Model folder and add a new model subfolder. 

Name the folder Vox. 

2. Open the Vox folder, use this folder workspace to create the Vox tutorial. 

Step 2: Creating the Vox object and Iris Cable 

1. Right-click in the workspace and under Audio select Vox. Name the vox object 

Mic_Input_Vox 

2. Right-click to add an Iris cable, name it 

IrisCable1 

3. Right-click on the IrisCable1 and select 

assign to an Iris >> Iris1 

This assigns the Iris cable to the Iris asset in the model. 



4. To route the audio from the Iris to the Vox, middle-click IrisCable1 and select 

from/to stereo Operator >> AudioInA 

5. Then middle-click on the Mic_Input_Vox object and select 

to AudioIn >> all of 

6. Then to route the audio from the microphone to the vox back out, you will need to middleclick 

Mic_Input_Vox and select 

from AudioOut >> all of 

7. Then middle-click IrisCable1and select 




8. To route the PTT, middle-click IrisCable1 and select 

from/to stereoOperator >> digital_inA1 >> 

digital_inA1_kout_bool 

9. Then middle-click Mic_Input_Vox and select 

to PTT 



Step 3: Creating New Vox Members in the ICD and Assigning them in the Model 

1. In the workspace right-click and add the UDPincable, name it 


(the same name used in the previous tutorial). 

2. Right-click on Tutorial_Inputs and select 

Assign UDP Input Cable >> 

Telestra[Component_Tutorial_Inputs_PortXXXXXX] 

3. Navigate to the menu bar and open the ICD tool. Open the ICD and packet created in the 

previous tutorial. 


Vox_Level 

5. Set the required settings as shown below. 

6. Add a second member and name it 

Vox_Enable 

7. Set the required settings. 



8. Highlight all the members in the packet, right-click and select ‘Auto Index/Offset.’ Enter 

0 for the starting offset number. 

9. Save the ICD and click the “magic wand” to create the assets. 

10. Return to the Vox folder workspace, middle-click Tutorial_Inputs and select 

from/to hostPacket >> Vox_Level 

11. Then middle-click on Mic_Input_Vox and select 

to VoxLevel 



12. Repeat step 10 above for Vox Enable by middle-clicking Tutorial_Inputs and select 

from/to host packets >> Vox_Enable 

13. Then middle-click on Mic_Input_Vox and select 

to VoxEnable 



14. The last step is to turn on your mic. Return to the Telestra object in the Assets folder. Open 

the Iris1 and open the input settings. 

15. Set the mic_preamp_a to 1(default). 

16. Set the mic_preamp_b to 1(default). 

Reload and start your model to test your work. You should hear the 100 Hz Sine Wave from the 

first tutorial as soon as you start the model. Then select the press-to-talk (PTT) button to hear 

yourself talk. Open up the Tutorial_Inputs and change the Vox_Enable setting to TRUE to hear 

yourself without having to use the PTT. You can adjust the level the Vox object picks up your 

voice and transmits it by adjusting the Vox_Level value. 


9.3. Tutorial 3- Play Sounds 


This section is intended to follow and build upon the models from Tutorial 1 and 2 in sections 9.1 

and 9.2. 

This tutorial will demonstrate how to use the play sound object to play wave files. The Sound 

Library tool will be used to build a sound library of a group of wave files. The wave files will be 

assigned to positions in the PSound255 object. The 4 Channel PTT will control the soundfiles, 

which are played. Each channel on the PTT switch will play a different sound file. Host controls 

will trigger the playing of the sound files. 


• The Sound Library Editor 

• The PSound255 object 

• The 4 Channel PTT 



Before using the Sound Library the user should be aware of the Loop modes. There are three loop 

mode options in the Sound Library. 

• One-shot- set this to play the sound from beginning to end, one time only. 

• Simple Loop- set this to play the file from beginning to end in a continuous loop. 

• Complex Loop- set this to play a subsection of a file in a loop for a designated time and then 

it continues on after the second trigger and finishes playing the remainder of the file. 

Simple Loop 

Start Finish 

Complex Loop 

Trigger Trigger 

Loop 

Start Finish 

Figure 46:Simple and Complex Loop Diagram 



The PSound is an audio object that allows for the playing of one or multiple audio files. The audio 

files must be in the following format: 

• Wave 16-bit PCM (*.wav) 

• 48 kHz sample rate 

• Mono 

Controls for the PSound object: 

• Trigger: When true, causes the soundfile located in playfiles[Index] to play 

• Pause: When true, pauses the playback of the audio 

• Index: Pointer which specifies which playfiles[index] will be played. 

• Gain: playback volume of the output audio 

Pause 

Trigger 

Index 

Gain 

Sound Library Editor 

Figure 47: Playsounds 

Playsounds 

“Stall” Filename= /home/..../.../...../.wav 

Start= 0 

End= 1000 

Loop Mode= one-shot/simpleloop/complexloop 

Play All=yes/no 

86 Copyright © 2006 Advanced Simulation Technology inc. 

32 

Aout 

Psound: playfiles [32] 

[0] = Stall 

[1] = TACAN Tone 

[2] = Weapon fire 

[3] = Rain 

: 

: 

[31] = .....


After completing the following tutorial you should be able to: 

• Use the sound library 

• Assign playsounds to the Iris asset 

• Change input/output settings to hear sounds 

Note for the purpose of this tutorial three sound files are available on the asti web site at http:/ 

www.asti-usa.com. These files are chopper, tankfire, and airtraffic. You need to save the wave 

files into the .soundlibrary directory under your model directory. 

Figure 48: MBV Sound Library 


Step 1: Creating Playsound Object and Using the Sound Library 

1. Create a new model subfolder and name it Playsound. 

2. Open the Playsound folder and in the workspace rightclick 

and under Audio select PSound255, name it 

Audio_Psound 


3. Reload and then open the edit sound library under ‘Tools’ in the top tool bar. 

4. In the sound library click the play file icon and type Chopper. Then go to browse and find 

the chopper.wav file. Open the file and set the loop mode to one-shot start to end. 



5. Open another play file and name it tankfire. Then go to browse and select the tankfire.wav 

file. Open the file and set it to simple loop. Note: Do not check ‘Play All.’ 

6. Open another play file and name it Airtraffic. Then go to browse and select the incoming.wav 

file. Open the file and set it to one shot and check ‘Play All.’ Then click ‘Ok’. 


Step 2: Assigning Sounds to Playsound Object 


1. Navigate back to the playsound workspace and open Audio_Psound. In the schematic, 

open psound and expand playfiles. 

2. Right-click on playfile 0 and under playsound file select chopper. Set playfile 1 to tankfire 

and playfile 2 to Airtraffic. Close the window. 



Step 3: Routing the Audio to the Iris 

1. Right-click in the workspace and add an IrisCable. Name it, 

IrisCable1 

2. Right-click on the IrisCable1 and select 

assign to an Iris >> Iris1 

3. Middle-click on Audio_Psound and select 

from Aout >> all of 

4. Middle-click on IrisCable1 and select 

to stereoOperator >> Audio Out A 



Step 4: Creating the 4 Channel PTT Psound Index 


1. Navigate back to the Playsound workspace and right-click under Control select 

FourChPTTDecoder and name it 

4chPTT_Psound_Index 

2. Reload the model and open the 4chPTT_Psound_Index. Under the ‘Data Viewer’ tab 

expand the LevelMap, expand the table and under data (3) set the ‘y’ value to 3. Set data 

(2) y value to 2 and set data (1) y value to 1. 



3. Navigate back to the workspace and middle-click on 4ChPTT_Psound_Index and select 

from ChannelBitMask 

4. Then middle-click Audio_Psound select 

to index 

5. Next open IrisCable1 and open digital_inA2 and make sure the mode is set to Analog 

Mode (this is the default mode). 



6. Navigate back to the workspace and middle-click on IrisCable1 and select 

from/to StereoOperator >> digital_inA2 >> 

digital_inA2_kout_float 

7. Then middle-click the 4ChPTT_Psound_Index and select 

to LevelIn 

This routs the analog signal from the 4Ch.PTT to the decoder object in the model. 

8. Right-click in workspace and add the UDPinCable and name it 

Turorial_Inputs 

9. Reload and right-click Tutorial_Inputs to assign UDPInputCable and select 

Telestra [Component_Tutorial_Inputs] 



10. Open the ICD tool and the ICD and packet created in the previous tutorials. Create a new 

member and name it 

Psound_Trigger 

11. Set the required settings (basic/boolean). 

12. Highlight all the members and right-click and select 

Auto Index/Offset 

13. Save and create the assets by selecting the “magic wand” tool. 



14. To assign host packet to Audio_Psound navigate back to the workspace and middle-click 

Tutorial_Inputs and select 

from/to hostPacket >> Psound_Trigger 

15. Then middle-click Audio_Psound and select 

to Trigger 

16. Open the Tutorial_Inputs UDP cable and set the Psound_Trigger to 

True 

17. Reload and start the model. Use the PTT channels to listen to the play sounds. 

You have successfully created a model with the Psound component! As you change the PTT channels 

you should hear the different sound files. You should also hear the continuous sine wave and 

if you press the PTT switch you will hear your voice (or if you have Vox enable set to True you 

should hear your voice as you speak into the mic without using the PTT switch.) 

You will hear all three tutorials sounds at the same time because all three audio outputs were 

routed to the same channel. In the next tutorial, we will show you how to use a mixer to pick and 

choose any combination of audio outputs. 



9.4. Tutorial 4- Mixer and Channel Handles 

The final tutorial of this series is intended to incorporate the models developed in Tutorials 1, 2 

and 3 from sections 9.1, 9.2 and 9.3. 

Up until this point of the tutorial the audio output signals from all three tutorials could be heard at 

the same time. In this final stage of the tutorial the mixer object will be used to select and combine 

any combination of the three previous tutorial audio outputs onto one audio stream. 

A BitToByte object will take in host control Boolean inputs representing each tutorial’s audio signal 

and they will be combined to form a bit mask which will be used to control which signals are 

mixed in the Mixer object. A Math2 function will use a host driven integer value with a range 

from 1 to 100 and convert it into a percentage of total volume which is used to control the output 

volume level. The audio signals generated from the three previous tutorials will be transmitted on 

and off an internal audio bus using the IcomTx and IcomRx. The audio bus is created using the 

Channel Handle tool. 

By then end of this section the user should be familiar with: 

• The Mixer Object 

• The BitToByte Object 

• The Math2 Function Object 

• The IcomTx object 

• The IcomRx Object 

• The Channel Handle tool 


Step 1: Creating the Mixer and Iris Cable 


1. In the workspace, right-click and create a new model subfolder and name it 

Mixer 

2. Open the Mixer folder and right-click in the workspace and under Audio select Mixer8, 

name it 

Tutorial_Mixer8 

3. Right-click in the workspace and create an IrisCable, name it 

IrisCable1 

4. Right click on IrisCable1 and assign it to Iris1. 

5. Route the mixer audio out through the Iris by middle-clicking on the Tutorial_Mixer8 

and select 

from output >> all of 

6. Then middle-click on IrisCable1 and select 

to StereoOperator >> AudioOutA 



Step 2: Deleting Audio Out Links from other Subfolders 

1. Since we will be using the mixer in this tutorial, you will need to delete all the other audio 

out links in the other subfolders (from the previous tutorials). 

2. Right-click on each folder and highlight to expand. 

3. In the Vox folder delete the audio out (the Iris cable to Vox). 

4. In the Psound folder delete the audio out link. 

5. In the SineWave folder delete audio out link and the IrisCable1. 

6. Highlight the box around the folder objects by using the mouse. When the box turns red, 

select reduce. This will reduce the models back into their subfolders. 


Step 3: Setting up the Bus and Mixer 


1. To create the channel handle navigate to the top tool bar to Tools and open Edit Channel 

Handle then select “New Handle,” name it 

SineWave 

2. Assign SineWave to channel 1 and then hit ‘Apply.’ 

3. Add two new channel handles for Vox and Playsound, assign them to 2 and 3, then hit 

‘Apply.’ 

4. Open the SineWave folder to create the Intercom object. In the workspace, right-click to 

Intercom and select IcomTx and name it 

SineWave_IcomTx 

Reload the model. 



5. Open SineWave_IcomTx and then open the Asset definition. Expand kin and asset and 

right-click on channel then left-click to select Sinewave. 

6. To assign the Sine Wave audio to route out to IcomTx return to the SineWave workspace 

and middle-click on Sine_Wave, then select 

from Signal >> all of... 

7. Then middle-click on Sinewave_IcomTx and select 

to TxAudio >> all of... 



8. Add IcomTx in the Vox and Playsound subfolders, open each IcomTx and set the asset 

definition channel to the corresponding name, as shown below. 



9. Assign the Vox signal to route out to the IcomTx. To assign the Vox to route out to IcomTx 

return to the Vox workspace and middle-click on Mic_Input_Vox, then select 

from AudioOut >> all of 

10. Then middle-click on Vox_IcomTx and select 

to TxAudio >> all of 


12. Assign the Playsounds signal to route out to the IcomTx. To assign the Playsounds to 

route out to IcomTx return to the Playsound workspace and middle-click on 

Audio_Psound, then select 

from Aout >> all of 

13. Then middle-click on Psound_IcomTx and select 





15. Navigate back to the Mixer folder and right-click and under Intercom select IcomRx and 

name it 

SineWave_IcomRx 

16. Then add two more IcomRx’s and name them 

Vox_IcomRx and PSound_IcomRx 


18. Open up each IcomRx and in the schematic open the asset definition and select the corresponding 

channel handle name. 

For example, for SineWave_IcomRx assign the channel to Sinewave. 



Step 4: Routing Audio 

1. Middle-click on the SineWave_IcomRx and select 

from RxAudio >> select all of 

2. Then middle-click on Tutorial_Mixer and select 

SignalIn0 >> all of 

3. Repeat Step 1 and 2 for Vox_IcomRx and for step 2 select 


4. Repeat Step 1 and 2 for Playsound_IcomRx and for step 2 select 



Step 5: Selecting the Sound 


1. Right-click in the Mixer workspace and under Control select BitToByte, name it 

Mixer_Control_BitToByte 


3. Middle-click on Mixer_Control_BitToByte and select 

from Output kout uint8 

4. Then middle-click Tutrorial_Mixer8 and select 

to Control 



Step 6: Adding Members to the ICD Packet 

1. Open the ICD tool and open the previously created ICD and packet. 


Mixer_Select_Sinewave 

3. Enter the member’s required values (basic/boolean). 

4. Add two new members and name them 

Mixer_Select_Vox and Mixer_Select_Psound 

5. Enter the required values for each member. 


Mixer_Master_Volume 

7. Enter the required values (basic/uint8). 

8. Add 3 new members and name them 

Mixer_Sig0_Volume, Mixer_Sig1_Volume, and 

Mixer_Sig2_Volume 

9. Highlight all members and right-click, select Auto Index/Offset. 

10. Save the model and select the “magic wand” tool to create assets. 





Step 7: Assigning the ICD to the Model 

1. Navigate back to the Mixer folder workspace, right-click and to add the UDPInCable and 

name it 



3. To assign the ICD packet controls, middle-click Tutorial_Inputs and select 

from/to host packet >> Mixer Select Sinewave 

4. Then middle-click Mixer_Control_BitToByte and select 

Bit 0 

5. Middle-click Tutorial 

Inputs and select 

from/to host 

packet >> 

Mixer_Select_Vox 

6. Then middle-click 

Mixer_Control_BitToByte 

and select 

Bit 1 

7. Then repeat this for Psound but select 

Mixer_Select_Psound>> bit2 

8. Then middle-click Mixer_Control_BitToByte and select 

Bit 2 



from/to host packet >> 


10. Then middle-click Tutorial_Mixer8 select 

to SignalGain0 


from/to host packet >> 





from/to host packet >> Mixer_Sig2_Volume 



Note: Sig 0 -> Sinewave Volume 

Sig 1 -> Vox Volume 

Sig 2 -> Psound Volume 




15. Right-click in the Mixer workspace and under Control select MathFunction2. Name the 

math function 

Mixer_Volume_Control 


17. Open the Mixer_Volume_Control and double-click on Function and set Type to 

Multiply 

18. Open the ‘Y’ and set the kin to .01 (and the type should be float). 

19. Open the ‘X’ and set the type to uint. Do not set the value for ‘X,’ this is done with the 

ICD. 


from/to hostPacket >> Mixer_Master_Volume 


21. Then middle-click Mixer_Volume_Control and select 

to X_kin_uint 

22. Then middle-click Mixer_Volume_Control and select 





23. Then middle-click Tutorial_Mixer8 and select 

to OutGain 

24. Reload the model and start. 

25. Open the Tutorial_Inputs to change values of volume and drive the model. Set the 

Mixer_Select object to True. 

Hint: Don’t forget to map the Iris and set the Iris asset gains, if you have not already done so. 

Play the audio generated from the selected component. Try different combinations to see how to 

mix different audio sources. You can also set the individual volumes for each with the 

Mixer_Sig(#)_Volume fields setting Sig0 for the Sinewave, Sig1 for the Vox, and Sig2 for 

Psound. The Mixer_Master_Volume will change the volume for all. 


Figure 49: MBV Components Tutorial Complete Model 




10.0. Creating a Radio Model in MBV 

10.1. Tutorial- Radio Model 

The two radio and two operator tutorial presented here is intended to show the user how a simple 

communications model is constructed. It will demonstrate the basic principles and main components 

upon which more complex communications models are developed. 

The model consists of Radio, Entity, ComSing and Vox objects. The Radios portion of the model 

uses the Radio and Entity objects. The Radio object simulates a radio to a level of fidelity customizable 

by the user. In this tutorial, only the essential parameters are covered that are needed to 

operate the radios. All the possible configurations of a Radio are beyond the scope of this tutorial. 

The Entity object is used to set a world position for the radio (one of the essential parameters 

needed). 

The operator portion of the model uses the ComSing and Vox objects. The ComSing is a simulated 

communications panel and is arguably the heart of any communications model. The CommPanel 

allows an operator to select amongst any number of Radio assets, in any combination, to 

transmit and receive on. (The Comm Panel audio signals routed to an operator are not just limited 

to Radios. Any type of audio signal can be selected and routed to an operator). The Vox object 

allows for more control and flexibility of how an operator’s voice is passed to the communications 

panel and ultimately a radio’s transmitter. The Vox object is capable of detecting filtered 

audio levels in order to auto transmit a voice signal. In this tutorial, only the Voxs' ability to detect 

a given audio threshold will be explored. The filter capability of the Vox will be left for the users 

exploration. 

In both the operator and radio sections, a host control interface will be used to set and drive the 

object parameters such as frequency selections and communication panel asset receive and transmit 

selections. 


Step 1: Creating the Iris Asset 

1. In MBV, create a new model and name it 

Radio_Tutorial 

2. Navigate to Assets and add an Iris asset in Telestra and name it 

Iris_Op1_Op2 



4. Open Iris_Op1_Op2 and open the input_settings set the preamps to 1. Then open the 

atmel_gains and set the gains to 15, as shown below. 



Step 2: Creating the Entity Object 

1. Navigate back to the models workspace. 

2. Create a new model subfolder and name it 

Radios 

3. Create a new model subfolder within the Radios subfolder and name it 

World_Position 

4. Open the new WorldPosition folder and right-click in the workspace, under radio select 

entity and name it 

Radio_WP 

Note: For this tutorial the world position will be used for multiple radios. If the radios are located 

in two different locations you need two world positions, but for radios in the same position only 

one world position is needed. 


6. Double-click on the Radio_WP to open the schematic. 

7. Open Entity and set 

kin to 1 

8. Open Local and set kin to 

TRUE 

9. Open Network and make sure the default is set to 

DIS 


. 





1. Navigate to Tools in the top menu and select ICD Tool to create a new ICD. 

2. Name the new ICD 

Radio_Tutorial_ICD 

3. Create a new packet and name it 

Radio_Tutorial_Inputs 

4. Under the Current Packet pull-down list select Radio_Tutorial_Inputs. 


Rad_Pos_X 

Set the member packet Type to float 64. 

Remember: To find the Type open the corresponding Radio object input, as shown below. 

6. Add new member and name it 

Rad_Pos_Y 

Set the member packet Type to basic/float 64. 

7. Add new member and name it 

Rad_Pos_Z 

Set the member packet Type to basic/float 64. 


8. Highlight the members and right-click to select Auto Index/Offset. 

9. Save the ICD and select the “magic wand” tool to create assets. 




Step 4: Creating the UDP Cable and Links 

1. Navigate back to the World Position subfolder workspace and rightclick 

to add the UDPinCable and name it 


2. Right click on Radio_Tutorial_Inputs and select 

Assign UDP Input Cable >> 


3. Middle-click Radio_Tutorial_Inputs and select 

from/host packet >> Rad_Pos_X 

4. Then middle-click Radio_WP and select 

to WorldGeocentric >> X 



You will repeat steps 1 and 2 for radio position ‘Y’ and ‘Z.’ Follow the steps below. 


from/host packet >> Rad_Pos_Y 


to WorldGeocentric >> Y 


from/host packet >> Rad_Pos_Z 


to WorldGeocentric >> Z 



Step 5: Creating the Radio 

1. Navigate to the Radio subfolder workspace. Right-click in the Radios subfolder and create 

a new subfolder, name it 

Radio_1 

2. Navigate to the top menu and under Tools select Edit Channel Handle. Create 2 new 

handles and name them 

Radio_1_Bus (Assign to Channel 1) 

Radio_2_Bus (Assign to Channel 2) 

3. Navigate to the Radio 1 subfolder 

to add a radio object. Right-click 

and under Radio select Generic 

and name it 

Radio 


5. Double-click on the Radio to 

open the schematic. 



6. Open the Entity Handle input. The Entity Handle in the Radio object is linked to the 

Radio_WP Entity. Set these to the same values. For this tutorial set the 

kin to 1 



7. In Radio 1, open the MainAssetDefinition and left-click on kin then right-click on Channel. 

Choose Intercom bus and select 

Radio_1_Bus 


Step 6: Adding Members to the ICD Packet for Radio 1 

1. Open the previously created ICD and select the same packet. 


2. Add 3 new members to drive the radio frequency, mode, and squelch. Name them and set 

the Types: 

Radio_1_Frequency, Type: basic/uint64 

Radio_1_Mode, Type: basic/uint32 

Radio_1_Squelch, Type: basic/float32 

3. Click on Name to reorganize the new and old members by name. 

4. Highlight the members and right-click and select Auto Index/Offset. 

5. Save the ICD and select the “magic wand” tool to create assets. 



6. Navigate back to the workspace for Radio 1, right-click to add UDPincable name it 


7. Right-click on Radio_Tutorial_Inputs and assign it to 


8. Middle-click Radio_Tutorial_Inputs (UDP cable) and 

select 

from/to hostPacket >> 

Radio_1_Frequency 

9. Then middle click Radio and select 

to MainFrequency 

10. Middle-click 

Radio_Tutorial_Inputs and select 


Radio_1_Mode 


to MainMode 

12. Middle-click 

Radio_Tutorial_Inputs and select 


Radio_1_Squelch 


to MainSquelch 


The model workspace should look like the image to the 

right. 


Step 7: Creating Radio 2 

1. Navigate back to the Radios folder and right-click on the Radio1 folder 

and copy and paste it in the workspace. MBV automatically names it 

Radio 2. 

2. You will need to change some specific things in the Radio 2 settings to 

differentiate it from Radio 1. 

3. Open Radio 2 schematic and open Radio ID and set 

kin to 2 

4. Also open the Main Asset Definition select channel and choose 

radio 2 bus 


5. In the Radio 2 subfolder delete the links by right-clicking and selecting delete for each 

one. 



Step 8: Adding Members to the ICD for Radio 2 

1. Open the ICD tool, and the previously created ICD and packet. 

2. Add 3 new members to drive the radio frequency, mode, and squelch. Name them and set 

the Types: 

Radio_2_Frequency, Type: basic/uint64 

Radio_2_Mode, Type: basic/uint32 

Radio_2_Squelch, Type: basic/float32 



5. Save the ICD and select the “magic wand” tool to create asset. 


6. Right-click on Radio_Tutorial_Inputs and assign it to 



from/to hostPacket >> Radio_2_Frequency 


to MainFrequency 


from/to hostPacket >> Radio_2_Mode 


to MainMode 


from/to hostPacket >> Radio_2_Squelch 


to MainSquelch 





Step 9: Creating Operator 1 

1. Navigate to the main model folder and add a 

subfolder, name it 

Operators 

2. In the Operators subfolder, add another new 

subfolder, name it 

Operator_1 

3. Open Operator 1 subfolder and in the workspace 

right-click and under Intercom select 

ComSing, name it 

Comm_Panel 

4. In the workspace right-click and under 

Audio select Vox, name it 

Vox 



6. Next you need to set the Operator settings. Open the 

CommPanel schematic. Open AssetDefinition0 and 

expand kin, set the channel to 

Radio_1_Bus 

7. Open AssetDefinition1 and set the channel to 

Radio_Bus_2 

8. Open RxGain0 and RxGain1 set 

kin to 1 

9. Open PTT and set 

kin to TRUE 

10. Open SidetoneGain set 

kin to 1 




Step 10: Adding Members to the ICD for Operator 1 

1. Open the ICD tool, and the previously created ICD and packet. 

2. Add a new member. Name it and set the Type: 

Operator_1_VoxEnable, Type: basic/boolean 


Operator_1_Voxlevel, Type: basic/float32 

4. Add two (2) new members. Name them and set the Types: 

Operator_1_ InputSelector, Type: basic/uint8 

Operator_1_OutputSelector, Type: basic/uint8 



7. Save the ICD and select the “magic wand” tool to create asset. 


Step 11: Creating the UDP in Cable and Assigning Links 


1. Navigate back to the Operator 1 subfolder workspace. Right-click to add the UDPincable, 

name it 

Radio_Tutorial_Input 

2. Right click on Radio_Tutorial_Input and assign it to 

Radio_Tututorial_Inputs 

3. Middle click Radio_Tutorial_Inputs and select 

from/to hostPacket >> Operator_1_VoxEnable 

4. Then middle-click Vox and select 

to VoxEnable 




from/to hostPacket >> Operator_1_VoxLevel 


to VoxLevel 


from/to hostPacket >> Operator_1_InputSelector 

8. Then middle-click Comm_Panel and select 

to InputSelector 




from/to hostPacket >> Operator_1_OutputSelector 


to OutputSelector 

11. Next you need to connect Vox audio to the Comm_Panel audio. Middle-click Vox and 

select 

from AudioOut >>all of 

12. Middle-click Comm_Panel and select 





Step 12: Creating Operator 2 and Adding Members to the ICD Packet 

1. Navigate back to the Operator subfolder. Rightclick 

and copy Operator 1 folder and paste it as 

Operator 2 in the Operator subfolder. 

2. In the Operator 2 subfolder delete the 

Radio_Tutorial_Input links. 

3. Open the ICD tool, and the previously created 

ICD and packet. 


Operator_2_VoxEnable, Type: basic/boolean 


Operator_2_Voxlevel, Type: basic/float32 

6. Add two (2) new members. Name them and set the Types: 

Operator_2_ InputSelector, Type: basic uint8 

Operator_2_OutputSelector, Type: basic uint8 



9. Save the model and select the “magic wand” tool to create the asset. 





Step 13: Adding Links for Operator 2 

1. Navigate back to the Operator 2 subfolder to change the UDP Input Assignment, and 

select the Radio_Tutorial_Inputs to 



from/to hostPacket >> Operator_2_VoxEnable 


to VoxEnable 


from/to hostPacket >> Operator_2_VoxLevel 


to VoxLevel 


from/to hostPacket >> Operator_2_InputSelector 


to InputSelector 


from/to hostPacket >> Operator_2_OutputSelector 


to OutputSelector 

Operator 1 and 2 should look identical. 


Step 14: Connecting the Iris Asset 


1. Navigate back to the Operators folder and right-click to add an Iris Cable, name it 

IrisCable_Op1_Op2 

2. Right-click on the Operator 1 subfolder and select to expand the subfolder. 

3. Right-click on IrisCable_Op1_Op2 and assign to 

IrisCable_Op1_Op2 

4. Middle-click IrisCable_Op1_Op2 and select 

from/to stereoOpertor >> AudioInA 

5. Then middle-click Vox (in Operator 1 subfolder) and select 

AudioIn >> all of 




from/to stereoOperator >> digital_inA1 >> digital_inA1 

kout_bool 

7. Then middle-click Vox (in Operator 1 subfolder) and select 

to PTT 

The workspace on your screen should look the same as the screen shown below. 

8. Middle-click Operator 1 Comm_ Panel and select 

from RxAudio >> all of 

9. Then middle-click IrisCable_Op1_Op2 and select 




10. Right-click on the box around the Operator 1 folder and reduce the contents back into the 

folder. Then expand the Operator 2 subfolder, shown below. 


from/to stereoOpertor >> AudioInB 

12. Middle-click Vox (Operator 2 subfolder) and select 

to AudioIn >> all of 


from/to stereoOperator >> digital_inB1 >> 

digital_inB1_kout_bool 

14. Middle-click Vox and select 

to PTT 



15. Middle-click Comm_Panel and select 

from Rx/Audio >> all of 


to stereoOpertor >> AudioOutB 

Below is an expanded view of both Operator 1 and Operator 2 subfolders with the Iris cable connections. 

Below is a folder view of both Operator 1 and Operator 2 subfolders with the Iris cable connections. 



Step 15: Mapping the Iris Hardware Devices to the Model 

1. Open the RMS with your local browser. 


2. Login to RMS using the same username you used to log into MBV for your model development. 

3. Navigate to the Model >> Management screen and confirm that the model is loaded but 

not started. 

4. Then navigate to the Hardware >> Mapping screen. 

5. Click on the “Map Iris Devices to Model” button. 

6. Select the serial number for the physical Iris device (if you don't know it look on the actual 

device). 

7. After setting the serial numbers select the “Map it” button. 



Step 16: Running the Model 

1. Navigate back to MBV and reload the model. 

2. Then start the model and confirm that its running. 

3. Open the Telestra Radio_Tutorial_Inputs. 

4. Set the values for following: 

• Operator_1_InputSelector to 1 

• Operator_1_OutputSelector to 1 

• Operator_2_InputSelector to 2 

• Operator_2_OutputSelector to 2 

• Radio_1_Frequency to 100 

• Radio_1_Mode to 2 

• Radio_1_Squelch to .02 

• Radio_2_Frequency to 100 

• Radio_2_Mode to 2 

• Radio_2_Squelch to .02 

5. Press the PTT and start talking. 

Note: The Vox settings are not manually set because they are driven by the host. When setting 

host driven outputs and inputs for the Comm Panel remember to set output to hear and input to 

talk. 


Congratulations, you have now completed the radio tutorial. 




11.0 Converting a 2-operator 2-radio model to an 8operator 

4-radio model 

This model tutorial builds onto the previous Radio Tutorial and shows the user how to convert the 

2-operator 2-radio model to an 8-operator 4-radio model. 

Step 1: Adding Radios 3 and 4 

1. In the Radios folder highlight Radio_1 and Radio_2. 

2. Right-click the highlighted subfolders 

and select Copy. Rightclick 

again in the workspace and 

select Paste. Two new sub folders 

named Radio_3 and Radio_4 

will appear. 

Step 2: Adding to the Existing ICD 

1. Open the ICD tool and open 

Radio_Tutorial_ICD.x 

ml 

2. Under the Current Packet pulldown 

list select 

Radio_Tutorial_Inputs. 

3. Right-click and select Add Member. 

Name the member 


Set the type to basic/uint64. 

4. Right-click and add two more 

members and name them 

Radio_3_Squelch and Radio_3_Mode 

Set the types for these two members. 

Remember that the type for squelch is basic/float32 and Mode is basic/uint32. 

5. Add three more members for Radio 4. Name them 


Radio_4_Squelch 

Radio_4_Mode 

6. Set the corresponding type for each member. 

7. Highlight all members in the ICD, right-click and select ‘Auto Index/Offset’ and set to 0. 


8. Save the ICD and click the “magic wand” tool to create the assets. 




Step 3: Linking the ICD to Radio_3 and Radio_4 

1. Navigate back to the Radio_3 sub-folder. Right-click on the UDP Cable and select 

Assign UDP Input Cable >> Telestra [Radio_Tutorial_Inputs 

(port 10000)] 

2. Right-click one of the links from the Radio_Tutorial_Inputs to the Radio and select 

delete link. Delete the other two links in this same fashion. 

3. Recreate the links using the Radio 3 inputs. To do this link the frequency, squelch, and 

mode from the Radio_Tutorial_Inputs to the Radio. See the example shown below linking 

the frequency. 




5. Navigate to the Radio_4 sub-folder. Again, delete the three links then re-link the Frequency, 

Mode, and Squelch using the Radio_4 inputs as done with Radio_3. 

6. Open the Channel Handle Editor and add two new handles named Radio_3_Bus and 

Radio_4_Bus and click ‘Apply’ and then click ‘OK.’ 



Step 4: Adding Operators 

1. Navigate to the Operator_1 subfolder and double-click on Comm_Panel. Open 

RxGain2 and set default kin to 1. Repeat with RxGain3. 

2. Open AssetDefinition2. Right-click on 

kin->assets->channel select 

Choose Intercom Channel and 

Radio_3_Bus 

3. Under AssetDefinition3 add the channel 

Radio_4_Bus using the same process. 

4. Repeat the previous three steps for on the Comm Panel in the Operator_2 sub-folder. 

5. Navigate to the Operators folder. In the workspace highlight the Iris Cable and both 

Operators_1 and Operators_2 sub-folders. 

6. Right-click on Operator_2 sub-folder and select copy. 



7. Right-click in the workspace and select paste. Right-click and paste two more times so 

you have a total of 8 operators. 

8. Navigate to the Assets->Telestra Folder. Right-click on Iris_Op1_Op2 and choose copy. 

Paste a new Iris onto the workspace and rename it Iris_Op3_Op4. Paste another Iris and 

name it Iris_Op5_Op6. Repeat again and name it Iris_Op7_Op8. 

9. Navigate to the Operators folder. Right-click on IrisCable_Op1_Op3 and rename the 

cable IrisCable_Op3_Op4. 

10. Right-click again on IrisCable_Op3_4 and select 

Assign To Iris 

then select 

Iris_Op3_Op4 



11. Right-click on IrisCable_Op1_Op4 and rename the cable IrisCable_Op5_Op6. Rightclick 

again on the cable and select 


then select 

Iris_Op5_Op6 

12. Right-click on IrisCable_Op1_Op5 and rename the cable IrisCable_Op7_Op8. Rightclick 

again on the cable and select 


then select 

Iris_Op7_Op8 


Step 5: Adding ICD members to Drive the Operators 

1. Open the ICD tool and add a new member and name it 

Operator_3_InputSelector 



Operator_3_OutputSelector 



Operator_3_VoxEnable 

Set the type to basic/boolean. 

4. Add another new members and name it 

Operator_3_VoxLevel 

Set the type to basic/float32. 

5. Repeat this process for Operators 4 through 8. 




6. Highlight all members, right-click and select Auto Index/Offset. Then save the ICD and 

click the “magic wand” tool to create assets. 

Congratulations you now have a 4 radio - 8 operator model!. 


12.0 Model Troubleshooting 


There are two ways to view/debug specific variables within a running model. The user can view 

model objects directly in the MBV development environment or the user can create debug sets in 

RMS. By creating debug sets in RMS, the user can quickly scan model inputs for debugging. 

12.1. Creating Debug Sets in RMS 

The user must be operating in Advanced Mode to create new sets for 

debugging. 

1. Select Debug from the main RMS menu. 

2. Click on “create new set” and name the set. This will display 

the options for creating a new entry. 

3. Add an Entry from the pull-down list. This list is compiled 

from the directories listed in your model. 

4. Add an object from the next pull-down list. The object list is 

compiled of the objects used in the chosen directory. 

5. Select a specific variable in the object from the pull-down list. 

6. Select the “Add Entry” button to add the new entry to the list. 

The user can choose to divide the debug sets by creating sections within a page and by creating 

separate pages. Use the list order option to organize your sets into specific orders. Exit Advanced 

Mode to view the set for debugging. The debug set can be downloaded and uploaded and is stored 

with the model. 



12.3. MBV Debugging 

To facilitate debugging, ensure that the MBV development environment is configured for 

advanced mode. 

Instructions 

1. Start MBV Development Environment 

2. From File Menu, select “Edit Config” 

3. Expand “Advanced” item 

4. Right click over value and select “yes” 

5. Select “Save changes” 

6. Select “OK” at confirmation pop-up window 

7. Select “Close” 

12.4. Viewing RX Buffer Data 

The UDP input cable data viewer displays the ICD variable values received from the host. The 

offset indicates byte location within the buffer. The bit-packed variables are not shown in bit 

order. The value shown for bit-packed variables is the overall byte value. The packet counter at 

the bottom of the data viewer increments as packets are received from the host. 

Instructions to View Rx Buffer Data 

1. Navigate to Telestra / Assets 

2. Find target UDP input cable 

3. Double-click icon or right click and select “Open” 

4. Expand window so that Offset column may be viewed 

12.5. Viewing TX Buffer Data 

The UDP output cable data viewer displays the ICD variable values sent to the host. The offset 

indicates byte location within the buffer. The bit-packed variables are not shown in bit order. The 

value shown for bit-packed variables is overall byte value. The packet counter at the bottom of the 

data viewer increments as packets are sent to the host 

Instructions to View Tx Buffer Data 

1. Navigate to Telestra / Host 

2. Find target UDP output cable 

3. Double-click icon or right click and select “Open” 

4. Expand window so that Offset column may be viewed

ASTi Model Builder Visual Basic Training Manual Document: DOC ...

Create successful ePaper yourself

Delete template?

Save as template?