Summary of the content on the page No. 1
ADAM
TBX - TriBus
Triple Bus Expander for ADAM
93507838000 Rev A 12/2008
Summary of the content on the page No. 2
PROPRIETARY NOTICE SHIPPING TO THE MANUFACTURER The product information and design disclosed herein were originated by All shipments of product should be made via UPS Ground, prepaid (you and are the property of Telex Communications, Inc. Telex reserves all may request from Factory Service a different shipment method). Any patent, proprietary design, manufacturing, reproduction, use and sales shipment upgrades will be paid by the customer. The equipment should rights thereto, and to any artic
Summary of the content on the page No. 3
Table of Contents APPLY BUTTON .......................................................... 31 INTRODUCTION ............................................. 3 TEST BUTTON ............................................................. 32 General Description ...............................................3 DONE BUTTON ........................................................... 32 VERSION REQUIREMENTS ..............................................3 Select Frame Window ....................................
Summary of the content on the page No. 4
Summary of the content on the page No. 5
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 .........................................................
Summary of the content on the page No. 6
Summary of the content on the page No. 7
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
Summary of the content on the page No. 8
Features Interface The TBX-Tribus card is backward compatible with all existing AES, AIO, and RVON cards in an ADAM a with ADAM intercom system. The hardware and software is compatible to work seamlessly with the TDM (Time Division Multiplexing) and control bus circuitry for routing audio and controlling data. This card provides a downloadable firmware feature through AZedit Intercom Software. Channels The TBX-Tribus has three (3) fiber links. Each link can support up to a maximum of 256 audi
Summary of the content on the page No. 9
Specifications 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
Summary of the content on the page No. 10
Fail-Over Modes 1 Unlike the DBX card, audio and communications (called control ) 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
Summary of the content on the page No. 11
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 7
Summary of the content on the page No. 12
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 8
Summary of the content on the page No. 13
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 9
Summary of the content on the page No. 14
10
Summary of the content on the page No. 15
Figure 2: Eight Frame Tribus System – Non-Redundant 11
Summary of the content on the page No. 16
12
Summary of the content on the page No. 17
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 c
Summary of the content on the page No. 18
1. From the Options menu, select Upload Debug Information. The Upload Debug Information window appears. FIGURE 33. Upload Debug Information window 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 34. Uploading Debug I
Summary of the content on the page No. 19
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 f
Summary of the content on the page No. 20
16
