RTS TBX - TriBus ADAM User manual

ADAM
TBX - TriBus
Triple Bus Expander for ADAM
93507838000 Rev A 12/2008

PROPRIETARY NOTICE
The product information and design disclosed herein were originated by
and are the property of Telex Communications, Inc. Telex reserves all
patent, proprietary design, manufacturing, reproduction, use and sales
rights thereto, and to any article disclosed therein, except to the extent
rights are expressly granted to others.
COPYRIGHT NOTICE
Copyright 2008 by Telex Communications, Inc. All rights reserved.
Reproduction, in whole or in part, without prior written permission from
Telex is prohibited.
WARRANTY NOTICE
See the enclosed warranty card for further details.
CUSTOMER SUPPORT
Technical questions should be directed to:
Customer Service Department
RTS/Telex Communications, Inc.
12000 Portland Avenue South
Burnsville, MN 55337 USA
Telephone: [phone]
Fax: [phone]
Factory Service: 800-553-5992
Technical Questions Europe
RTS/Telex Technical Support EMEA
Telex Communications (UK) Ltd
www.rtsintercoms.com
R[email protected]
Phone: [phone]
RETURN SHIPPING INSTRUCTIONS
Customer Service Department
Telex Communications, Inc. (Lincoln, NE)
Telephone: [phone]
Fax: [phone]
Factory Service: 800-553-5992
Please include a note in the box which supplies the company name,
address, phone number, a person to contact regarding the repair, the type
and quantity of equipment, a description of the problem and the serial
number(s).
SHIPPING TO THE MANUFACTURER
All shipments of product should be made via UPS Ground, prepaid (you
may request from Factory Service a different shipment method). Any
shipment upgrades will be paid by the customer. The equipment should
be shipped in the original packing carton. If the original carton is not
available, use any suitable container that is rigid and of adequate size. If
a substitute container is used, the equipment should be wrapped in paper
and surrounded with at least four (4) inches of excelsior or similar
shock-absorbing material. All shipments must be sent to the following
address and must include the Proof of Purchase for warranty repair.
Upon completion of any repair the equipment will be returned via
United Parcel Service or specified shipper, collect.
Factory Service Department
Telex Communications, Inc.
8601 East Cornhusker Hwy.
Lincoln, NE 68507 U.S.A.
Attn: Service
Return Shipping Instructions EAME
Customer Service Department EVI Audio GmbH
After sales service Department
Hirschberger Ring 45
94315 Straubing
Germany

Table
of
Contents
INTRODUCTION .............................................3
General Description ...............................................3
VERSION REQUIREMENTS ..............................................3
Features ..................................................................4
Specifications ..........................................................5
Fail-Over Modes ....................................................6
FULL REDUNDANCY ......................................................7
PARTIAL REDUNDANCY .................................................8
NON-REDUNDANCY .......................................................9
Debug Information ...............................................13
INSTALLATION AND CONFIGURATION .17
Installation ............................................................17
REQUIREMENTS ..........................................................17
Configuration .......................................................18
CONFIGURE EACH MCII-EMASTER CONTROLLER
IP ADDRESS FOR THE ETHERNET ................................18
CONFIGURE THE SIZE OF YOUR INTERCOM
SYSTEM FOR EACH FRAME ...........................................19
CONFIGURE THE FRAME USING THE FRAME
MAPPING WINDOW IN AZEDIT .....................................23
Base 8 vs. Base 16 Port Number Systems .............24
BASE 8 PORT NUMBER SYSTEM ...................................24
BASE 16 PORT NUMBER SYSTEM .................................26
Force Autonomous Mode Check Box ...................27
AZedit Connections ..............................................28
WINDOW DESCRIPTIONS ...........................29
Frame Mapping Table Window ............................29
FRAME COLUMN .........................................................29
IP ADDRESS 1 COLUMN ..............................................30
MAC ADDRESS 1 COLUMN .........................................30
IP ADDRESS 2 COLUMN ..............................................30
MAC ADDRESS 2 COLUMN .........................................30
BASE 16 COLUMN CHECK BOX ...................................31
MOVE UPBUTTON .....................................................31
MOVE DOWN BUTTON ................................................31
ACCEPT FRAME MAPPING TABLE FROM
OTHER FRAMES CHECK BOX ......................................31
APPLY BUTTON .......................................................... 31
TEST BUTTON ............................................................. 32
DONE BUTTON ........................................................... 32
Select Frame Window ...........................................32
IP ADDRESS 1 COLUMN ............................................. 32
MAC ADDRESS 1 COLUMN ........................................ 33
IP ADDRESS 2 COLUMN ............................................. 33
MAC ADDRESS 2 COLUMN ........................................ 33
OK BUTTON ............................................................... 33
CANCEL BUTTON ........................................................ 33
TBX Links Status Window ....................................34
TBX COLUMN ............................................................ 34
COMM COLUMN ......................................................... 34
(A) LINK UP/DNCOLUMN ......................................... 35
(A) PARTNER COLUMN ............................................... 35
(B) LINK UP/DNCOLUMN ......................................... 35
(B) PARTNER COLUMN ............................................... 35
(C) LINK UP/DNCOLUMN ......................................... 35
(C) PARTNER COLUMN ............................................... 35
AUDIO A COLUMN ..................................................... 36
AUDIO B COLUMN ..................................................... 36
AUDIO C COLUMN ..................................................... 36
Intercom Alarms ...................................................36
FRAME COLUMN ........................................................ 38
ALARM TIME COLUMN ............................................... 38
RESOLVED TIME COLUMN .......................................... 38
DESCRIPTION COLUMN .............................................. 38
Hiding and Clearing Alarms ................................. 38
Logging Window ...................................................39
Configure Logging Window .................................39
J1 RADIO BUTTON ..................................................... 40
J9 RADIO BUTTON ..................................................... 40
J10 RADIO BUTTON ................................................... 40
ETHERNET RADIO BUTTON ......................................... 40
IP ADDRESS FIELD .................................................... 40
ALL FRAMES RADIO BUTTON ..................................... 40
THIS FRAME ONLY RADIO BUTTON ............................ 40
DOWNLOAD FIRMWARE UPGRADES ......41
Download Firmware to the TBX-Tribus Card .....41

List
of
Figures
FIGURE 1. 4 Frame System with Full Redundancy, including failover Master Controller ....................................7
FIGURE 2. Partially Redundant system, including failover Master Controller ......................................................8
FIGURE 3. 4 Frame System with No Redundancy, including failover Master Controller ......................................9
FIGURE 4. Eight Frame Tribus System – Non-Redundant ...................................................................................11
FIGURE 5. Upload Debug Information .................................................................................................................13
FIGURE 6. Upload Debug Information window ...................................................................................................14
FIGURE 7. Uploading Debug Information Status window ...................................................................................14
FIGURE 8. Navigation to the Debug Folder for AZedit ........................................................................................15
FIGURE 9. Tribus Backcard Slots .........................................................................................................................17
FIGURE 10. Base 8 Port Numbering System Example ............................................................................................24
FIGURE 11. Base 8 Port Numbering scheme with both AIO-16 and an AIO-8 card
installed. ..............................................................................................................................................25
FIGURE 12. Base 16 Port Numbering System Example ..........................................................................................26
FIGURE 13. Force Autonomous Mode when no audio links up – Intercom Configuration|Options Tab ...............27
FIGURE 14. Connect To Frame Menu ....................................................................................................................28
FIGURE 15. Frame Mapping Table ........................................................................................................................29
FIGURE 16. Frame Mapping Table Browse Button which opens the Select Frame window. ................................30
FIGURE 17. Apply Button message .........................................................................................................................31
FIGURE 18. Frame Mapping Table Valid message ................................................................................................32
FIGURE 19. Select Frame Window .........................................................................................................................32
FIGURE 20. TBX Links Status Window ...................................................................................................................34
FIGURE 21. Intercom Alarm Indication ..................................................................................................................36
FIGURE 22. Intercom Alarms Window ...................................................................................................................37
FIGURE 23. Log Viewer Window ............................................................................................................................39
FIGURE 24. Configure Logging Window ................................................................................................................39
FIGURE 25. I/O Card Version Information Window ..............................................................................................41
FIGURE 26. Download Device Firmware Window .................................................................................................42
FIGURE 27. Download in Progress Window ..........................................................................................................42
FIGURE 28. Successful Download Message ...........................................................................................................43

3
CHAPTER 1
Introduction
General Description
A single TBX-Tribus fiber card can link up to eight (8) ADAM frames. This makes it possible to increase the number of
available users on a system by transparently integrating additional frames. The ADAM frame must be equipped with an
MCII-e Master Controller card (version 2.0.4 or later), allows the TBX-Tribus to link together multiple frames, thereby
allowing users to quickly connect multiple ADAM intercom systems. This functionality can be useful in mobile production
scenarios to tie systems together via fiber using the digital audio of the TBX-Tribus. In this scenario, the MCII-e Master
Controllers are tied together via Ethernet connections. In a failure of the Ethernet connection of one frame, the affected
ADAM can be automatically isolated as an autonomous frame, and the remaining frame(s) function as a normal
interconnected system. The TBX-Tribus works in both AIO-8 and AIO-16 frame environments with simple software settings
in AZedit intercom software. The TBX-Tribus card comes with a fiber connection only, allowing a range of up to 24.8 miles
(40km) between ADAM frames. The TBX-Tribus surpasses the DBX (Dual Bus Expansion) card with its superior channel
capability, transmitting 256 channels of audio, rather than the 128 channels supported by DBX.
Version Requirements
•MCII-e version 2.0.4 or later
•AZedit version 3.6.1 or later

4
Features
Interface
with ADAM The TBX-Tribus card is backward compatible with all existing AES, AIO, and RVON cards in an ADAM
intercom system. The hardware and software is compatible to work seamlessly with the TDMa(Time
Division Multiplexing) and control bus circuitry for routing audio and controlling data. This card provides
a downloadable firmware feature through AZedit Intercom Software.
a. TDM is a technology that transmits multiple signals simultaneously over a single transmission path.
Channels
Per Link The TBX-Tribus has three (3) fiber links. Each link can support up to a maximum of 256 audio channels per link. This channel capability is provided in AIO-16 systems. Moreover, the link can also be scaled
down to 128 channels, allowing it to support AIO-8 based intercom systems.
New System
Architecture The System Framework has been redefined for the TBX-Tribus allowing the system to reconfigure itself in the event of a frame failure. In the scenario where the master frame fails, another ADAM frame within the
system seizes control until the fault is fixed. This fail-save mechanism monitors both audio and control,
and sends messages to report any corrupt behavior in the system.
NOTE: DBX cards are not compatible with TBX-Tribus cards.
Support for
Multiple
Distances
The backcard features three (3) SFP (Small Form-Factor Pluggable) connectors that allow for support of
multiple distances. This allows the user to configure these cards based on their custom application. The
user can insert COTS (Commercial Off-The-Shelf) modules (Multi Mode/Single Mode) to match their
needs.
System
Expansion The TBX-Tribus employs the next generation ASIC (Application Specific Integrated Circuit) Nucleus for higher performance and future system expansion. See Table 1 on page 5.
Autonomous
Mode Normally, a TBX-Tribus frame communicates with other frames that are part of the same intercom. However, if an Ethernet link is not present, the Tribus automatically enters Autonomous mode.
AZedit also has a new option on the Intercom Configuration Options window (Options|Intercom
Configuration|Options Tab) called “Force Autonomous Mode when no audio links up.” The Force
Autonomous Mode check box is used to force the current frame into autonomous (independent) mode, if
none of its Tri-bus links are up. Normally, a frame communicates with other frames that are part of the
same intercom. If selected, the frame refuses to communicate with any other frames if none of its Tri-bus
links are up, even if Ethernet communications are fine. And, once one (1) or more of its audio links are
restored, the frame automatically tries to re-establish messaging links to the other frames in the cluster.
Automatic
Transfer of
Control
Within each frame, both the active and the standby MCII-e master controllers maintain Ethernet messaging
links with every other frame in the cluster. If the Active controller in the frame loses its messaging links,
but the standby controller has one (1) or more Ethernet links available, an automatic transfer of control is
performed. When this transfer occurs, the standby controller becomes the active controller and the
previously active controller becomes the standby controller when its messaging links are restored.
Alarms and
Warnings A new view in AZedit displays various alarms and warnings that have occurred in the intercom. Once an alarm has been resolved, it is deleted after five (5) minutes.
AZedit
Connections AZedit Connections (Options|Connect to Frame) allow the user to select the frame AZedit should connect to.
AZedit version 3.6.1 or higher is required.
Unavailable
Tally
Indicator
When a user turns a talk or listen key ON to connect with a resource in another frame within the cluster, the
key displays a busy tally, flashing between the Alpha and **, to indicate the resource is unavailable.
NOTE: For special lists and party lines, no unavailable tally is generated if there are any members of
the special list or party line in accessible frames
Logging Each frame in an intercom cluster generates its own log message and stores them locally. Normally, the log
messages are identical from frame to frame, except when frames are synchronizing. Using the logging
configuration window, you can select whether changes affect all frames in a cluster or just the locally
connected frame.

5
Specifications
NOTE: The TBX–Tribus supports up to eight (8) frames in non-redundant mode. Slot 10 should be used if a third TBX–
Tribus card is needed.
Board Performance
Throughput Per Link:
360Mb/sec
SFP Fiber Transceivers:
Voltage:3.3 V Rails
Standard Rate:
SONET OC12 or Gigabit Ethernet
Recommended Parts:
Multi-Mode:
Finisar - FTLF8519P2BNL (Oxide VCSEL, Maximum reach of 550m)
Single Mode:
Finisar - FTLF1422P1BTL (1310nm, Maximum reach 40km)
Fiber Cable Connector Type:
Multiple Mode Fiber LC–LC Duplex Connector – max length 500m (546.8 yd.)
Single Mode Fiber LC–LC Duplex Connector – max length 40km (24.9 miles)
Configuration Requirements
An MCII-e Master Controller card must be installed in the same frame as the TBX-Tribus. For more information, see
the MCII-e User Manual which can be found at www.rtsintercoms.com.
TABLE 1. Systems Supported by the TBX-Tribus Card
Links Used # TBX Cards
per Frame System Frames Supported Channels
1 1 AIO-8 2 256
1 1 AIO-16 2 512
3 1 AIO-8 3 384
3 1 AIO-16 3 768
6 1 AIO-8 4 512
6 1 AIO-16 4 880
10 2 AIO-8 5 640
10 2 AIO-16 5 880
15 2 AIO-8 6 768
15 2 AIO-16 6 880
21 2 AIO-8 7 880
21 2 AIO-16 7 880
28 3 AIO-8 8 880
28 3 AIO-16 8 880

6
Fail-Over Modes
Unlike the DBX card, audio and communications (called control1) between frames is separated between the TBX-Tribus card
and the MCII-e Master Controller Card. Communication between frames using TBX-Tribus occurs using the MCII-e Master
Controller over Ethernet. Audio is passed between frames using the TBX-Tribus card fiber connection (see Figure 29 to
Figure 31).
Audio between frames exists as long as there is a single valid link between frames. There are three (3) types of system
configurations:
•Full Redundancy
•Partial Redundancy
•Non-Redundancy
1. Control is the ability to talk to keypanels and act on key presses.

7
Full Redundancy
In Full Redundancy systems, there are two (2) links, shown in Figure 29, between each frame, so losing either one does not
affect audio.
FIGURE 29. 4 Frame System with Full Redundancy, including failover Master Controller

8
Partial Redundancy
In a Partial Redundancy systems, multiple frames, but not all frames, have two links configured between them. In the
example shown in Figure 30, Frame 1 and Frame 2 have full redundancy between them; however, Frame 3 has only one (1)
link to Frame 1. This means if the fiber connection between Frame 1 and Frame 3 is broken, Frame 3 can not send or receive
audio.
FIGURE 30. Partially Redundant system, including failover Master Controller

9
Non-Redundancy
In a Non-Redundancy systems, shown in Figure 31, there is only one link between frames, so if the fiber link goes down,
audio communications between the frames is lost.
FIGURE 31. 4 Frame System with No Redundancy, including failover Master Controller

10

11
Figure 2: Eight Frame Tribus System – Non-Redundant

12

13
Debug Information
The Debug Information menu item, shown in Figure 32, allows you to send a flash file to RTS to help troubleshoot the reason
for crash in AZedit. In the event of a processor crash, the processor saves diagnostic information about the cause of the
problem to its flash memory. The menu item stays greyed-out until a flash file is created when the processor crashes.
NOTE: Every card in every frames stores its own debug information. So, if frame 3 has a processor crash, you must
connect AZedit to frame three to create a .azd file to send to RTS for debugging.
To create the debug file, do the following:
NOTE: Once the processor has crashed the Upload Debug Information menu item becomes active.
FIGURE 32. Upload Debug Information

14
1. From the Options menu, select Upload Debug Information.
The Upload Debug Information window appears.
NOTE: By default, the Debug folder (C:\Telex\AZedit\Debug) is where the AZedit debug file you create is
stored.
2. In the File name field, enter a name for the debug file you create. For example, you could use the date as the file
name – 12152008.azd.
3. Click Save.
The Uploading Debug Information Status window appears.
FIGURE 33. Upload Debug Information window
FIGURE 34. Uploading Debug Information Status window

15
NOTE: Select the Delete debug information from intercom check box if you want to delete the debug
information from system once the .azd file is created. Otherwise, the information kept on the
intercom system. Remember, you will only be able to save the most current debug information.
This means that if your processor fails twice you will only be able to capture the second failure’s
diagnostic information.
4. Click OK.
The AZedit debug file is made.
To find the file you just created, do the following:
1. Right-click on My Computer, and from the popup menu, select Explore.
The My Computer window appears with a navigation pane down the left hand side of the window.
2. Navigate to C:\Telex\AZedit\Debug.
OR
Navigate to the folder you store your AZedit debug file.
The file you create is stored in this folder.
Once you have created the AZedit Debug file, please contact your RTS system engineering for further instructions. If you do
not know your local system engineer, please see http://www.rtsintercoms.com/contact.php.
FIGURE 35. Navigation to the Debug Folder for AZedit

16