LBI-38985A

Mobile Communications

EDACSSITE CONTROLLER

Maintenance Manual

TABLE OF CONTENTS

PageINTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Standard Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

EDACS Interface Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Downlink GETC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Controller (Computer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5System Manager Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.8 VDC Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Uninterruptible 120 VAC Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Optional Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Power Monitor Unit Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Local Telephone Interconnect Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Redundant Downlink GETC Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Test and Alarm Unit Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7230 VAC Modification Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Optional Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Protective Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8AC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Mechanical Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Cabinet Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Cabinet Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Cabinet Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Cabinet-Top Cable Duct Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Electrical Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8EDACS Interface Panel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Power Monitor Sensor Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Downlink and Redundant Downlink Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 10Telephone Line Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Direct Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Alarm and Control Unit (ACU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Test Unit (TU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11System Manager Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Controller (Computer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Power-Up/Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Call Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Toll Call Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Line Rotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

LBI-38985

2

Copyright© November 1993, Ericsson GE Mobile Communications Inc.

TABLE OF CONTENTS

PageOPERATION Continued)

Call Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Eight Priority Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Recent User Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Activity Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Repeater Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

System Manager Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Full-Featured Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Failsoft Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Multisite Trunking and Console Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Downlink GETC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Redundant Downlink GETC Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Local Telephone Interconnect Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Telephone-Originated Call on a Dedicated Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Telephone-Originated Call on a Non-Dedicated Line . . . . . . . . . . . . . . . . . . . . . . . . . . 19Radio-Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Power Monitor Unit Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Test and Alarm Unit Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Alarm and Control Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Test Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28ATTACHED DRAWINGS

Mechanical Assembly (19D438315, Sheets 1&2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 & 31Interconnection Diagrams:

#1A - EDACS Site Controller (For Sites with 2 Repeaters Per Cabinet) . . . . . . . . . . . . . . . . 32#1B - EDACS Site Controller (For Sites with 3 Repeaters Per Cabinet) . . . . . . . . . . . . . . . . 33#2 - System Manager Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34#3A - Channel GETC Data Links (For Sites with 2 Repeaters Per Cabinet) . . . . . . . . . . . . . . 35#3B - Channel GETC Data Links (For Sites with 3 Repeaters Per Cabinet) . . . . . . . . . . . . . . 36#4A - Downlink and Redundant Downlink Option (For Sites with 2 Repeaters Per Cabinet) . . . . . 37#4B - Downlink and Redundant Downlink Option (For Sites with 3 Repeaters Per Cabinet) . . . . . 38#5A - Local Telephone Interconnect Option (For Sites with 2 Repeaters Per Cabinet) . . . . . . . . 39#5B - Local Telephone Interconnect Option (For Sites with 3 Repeaters Per Cabinet) . . . . . . . . 40#6A - Power Monitor Option (For Sites with 2 Repeaters Per Cabinet) . . . . . . . . . . . . . . . . 41#6B - Power Monitor Option (For Sites with 3 Repeaters Per Cabinet) . . . . . . . . . . . . . . . . 42#7 - Test and Alarm Unit Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43#8 - AC Power (Rear View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44#9 - DC Power (Rear View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

LBI-38985

3

INTRODUCTION

DEFINITIONS

The EDACS (Enhanced Digital Access CommunicationsSystem) Site Controller is all that standard and optionalequipment housed in the single cabinet that houses the Con-troller.

The Controller is the computer itself, currently a DECmodel CT-UXXXF-EK. This model is characterized by theDEC model KDJ11 CPU module and modular RJ11-typeconnectors on the back. Information about earlier PDP andVAX models, characterized by a separately-mounted, 32-port distribution panel (Emulex or Dilog), are not includedin this manual. However, most information in this manual(except information relating to the EDACS Interface Panelsand connections to the Controller) applies to these earliermodels.

GENERAL

The intent of this instruction manual is to provide infor-mation about how the individual pieces of equipment areconnected and work together as the EDACS Site Controller,and how they are connected and work with other pieces ofequipment at the site or other locations. The information isorganized in the following sections by the question the in-formation answers:

Description: What is it?Where is it?What does it do?

Installation: How do I hook it up?

Operation: How does it work?

Troubleshooting: How do I fix it?

For additional information, refer to the instruction man-ual for that piece of equipment. (Current LBI numbers arelisted as References following the Table of Contents.)

LIST OF FIGURES & TABLES

PageFigure 1 - Equipment Mounting in EDACS Site Controller Cabinet (Front View) . . . . . . . . . . . . . . . . 5Figure 2 - External Connections to EDACS Interface Panel #1 . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 3 - External Connections to EDACS Interface Panel #2 . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 4 - External Connections Directly to Other Equipment (Rear View) . . . . . . . . . . . . . . . . . . . . 11Figure 5 - Typical Alarm Input Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 6 - Typical Control Output Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 7 - System Manager to Controller Using Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 8 - PROM Mounting in Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 1 - Downlink Connection Pin Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 2 - Telephone Line Connections Pin Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 3 - Alarm Input Connections Pin Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 4 - Control Output Connections Pin Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

REFERENCES

LBI-38762 - Installation Manual - Basic and Level 1 EDACS Installation and Field Acceptance TestLBI-38812 - Maintenance Manual - EDACS Interface PanelLBI-38174 - Maintenance Manual - GETC Trunking CardLBI-38513 - Maintenance Manual - EDACS Telephone Interconnect SystemLBI-31939 - Maintenance Manual - EDACS Test and Alarm UnitLBI-38980 - Maintenance Manual - EDACS 900 MHz Test UnitLBI-38875 - Maintenance Manual - EDACS Cable Duct SystemLBI-38138 - Installation Manual - EDACS Site Controller (Old Configuration)

LBI-38985

4

DESCRIPTION

OVERVIEW

The EDACS Site Controller consists of the followingstandard PST25 package of equipment, including a 69-inchcabinet with a 6-outlet AC power strip, 2-outlet AC powerstrip, and exhaust fan.

• EDACS Interface Panels• Downlink GETC• Controller (Computer)• System Manager Modem• 13.8 VDC Power Supply• Uninterruptible 120 VAC Power Supply

In addition to the standard equipment, the EDACS SiteController may also include some or all of the following op-tional equipment:

• Power Monitor Unit• Local Telephone Interconnect• Redundant Downlink GETC• Test and Alarm Unit• 230 VAC Modification• Optional Cabinets

Figure 1 shows the normal position of the standard andoptional equipment in an EDACS Site Controller cabinet.

STANDARD EQUIPMENT

EDACS Interface Panels

The two EDACS Interface Panels are mounted in theback of the cabinet. Panel #1 provides connection points foraudio and data communications cables to other EDACSequipment, such as repeater cabinets. Panel #2 providesconnection points for the Downlink and Redundant Down-link to the multisite/console switch, and the local telephonelines for the Local Telephone Interconnect option.

Downlink GETC

The Downlink GETC is mounted in a pull-out shelf. Itserves as the data communications interface between theDownlink to the multisite/ console switch and the Control-ler (for Full-Featured Trunking), or the Control ChannelGETC (for Failsoft Trunking).

Controller (Computer)

The Controller is a 32-port computer responsible for di-recting the following functions (some parameters requiredfor these functions can be reconfigured by the System Man-ager):

• Repeater Trunking (including partitioning)• Local Telephone Interconnect option• Power Monitor Unit option• Alarm and Control Unit option• Test Unit option

Alarm and Control Unit

Test Unit

System Manager Modem

Blank Panel

13.8 VDCPower Supply

Blank PanelBlank Panel

UninterruptiblePower Supply

Blank Panel

Power Monitor Unit

Downlink GETCRedundant Downlink GETC

Blank Panel

Controller (Computer)

Local TelephoneInterconnect

Blank Panel

Figure 1 - Equipment Mounting In EDACS Site Controller

LBI-38985

5

The Controller supports the following functions directedby other equipment:

• System Manager Site Database• System Manager Activity Reports• Downlink to the multisite/console switch• Redundant Downlink to the multisite/console switch

In addition, the Controller manages the following fea-tures used with one or more functions (some parameters re-quired for these features can be reconfigured by the SystemManager):

• Call Validation (Logical and Group ID)• Toll Call Restrictions• Line Rotations• Call Queueing• Eight Priority Levels• Recent-User Priority• Alarm Management• Activity Logging• Patch• Simulselect• Dynamic Regrouping• Fault Detection• Unit Enable/Disable

System Manager Modem

The standard configuration for connecting the SystemManager to the Controller is to use a telephone line for thedata link, with a modem at each end. (The modems can beomitted if the distance is short and a full RS-232 data link isavailable.)

If the System Manager Modem is used, it is mounted ona shelf below the Test Unit, and serves as the data communi-cations interface between the Controller and either a dedi-cated or a dial-up telephone-line data link to the SystemManager.

13.8 VDC Power Supply

The 13.8 VDC Power Supply is a regulated power sup-ply that converts the AC line voltage to +13.8 VDC for thefollowing equipment:

• Downlink GETC• Redundant Downlink GETC option• Local Telephone Interconnect option• Test and Alarm Unit option• Power Monitor Unit option

Uninterruptible 120 VAC Power Supply

The Uninterruptible 120 VAC Power Supply (UPS) is abattery-driven, inverter power supply that provides approxi-mately 10 minutes of uninterrupted 120 VAC to the follow-ing equipment, after losing AC line voltage to its input:

• Controller (Computer)• System Manager Modem

OPTIONAL EQUIPMENT

Power Monitor Unit Option

The Power Monitor Unit option consists of a basic con-trol monitor unit and external RF sensors, to determine thestatus of each channel’s output RF path to an antenna. Uni-directional RF sensors are located at the output of eachtransmitter, and bi-directional RF sensors at the output ofeach transmitter combiner.

Local Telephone Interconnect Option

The Local Telephone Interconnect is a 2-wire telephoneswitch manufactured by IDA. A fully-equipped Local Tele-phone Interconnect is capable of connecting up to 32 tele-phone lines to up to 20 repeaters, under the direction of theController. The Local Telephone Interconnect allows author-ized radios to make calls to, and receive calls from, a tele-phone system without dispatcher assistance.

The Local Telephone Interconnect is made up of a shelfwith up to 2 PLA (Phone Line Adapter) boards, a LIC (LineInterconnect Controller) plug-in module, and up to 8 LIX(Line Interconnect and Cross Bar) plug-in modules.

The PLA boards mount on the back plane of the shelf.Each board provides a modular jack and 2 gas-tube surgeprotectors for each of 16 telephone line connections.

The LIC module controls up to 8 LIX modules under thedirection of the Controller, and generates pulse dialing whenneeded.

The LIX modules make the actual cross connections be-tween the telephone lines and the repeaters. Each LIX mod-ule can connect 4 telephone lines individually to any of 20repeaters. The LIX module also detects ringing on the tele-phone lines, and contains the line buildout network boardwhich contains 4 equalizer circuits to normalize each of the4 telephone lines (so that the 4-wire/2-wire hybrid trans-former in each repeater interface will remain balanced re-gardless of which telephone line is connected to it).

LBI-38985

6

Each EDACS repeater to be used for telephone intercon-nect calls, must be equipped with a Repeater InterconnectController (RIC) The RIC provides the necessary interfacebetween the repeater and the Local Telephone Interconnect(including the hybrid transformer mentioned above).

The RIC connects the repeater’s receive audio to the re-peater’s transmit audio for radio-to-radio calls, or connectsthe repeater’s receive and transmit audio through a hybridtransformer to a 2-wire audio line to the LIX module for ra-dio-to-telephone interconnect calls. The RIC also generatesdial tone, multiple frequency tones, and DTMF tones as di-rected by the Controller. The RIC also detects and reports tothe Controller any DTMF tones from the radio or the tele-phone line, and dial tone from the telephone line.

Redundant Downlink GETC Option

The Redundant Downlink GETC is mounted in a pull-out shelf. It serves as the data communications interface be-tween the Redundant Downlink to the multisite/ consoleswitch and the Controller (for Full-Featured Trunking), orthe Control Channel GETC (for Failsoft Trunking).

Test and Alarm Unit Option

The Test and Alarm Unit (TAU) option is made up of theAlarm and Control Unit (ACU), and the Test Unit (TU). TheTU is mounted in the pull-out shelf at the bottom of theACU. The ACU can also be ordered and operated withoutthe TU, but the TU can’t be operated without the ACU (be-cause the TU depends upon interface circuitry in the ACUto communicate with the Controller).

The ACU monitors up to 32 alarm inputs, provides up to8 control relay outputs, displays the status of up to 56 siteparameters, houses the TU, and provides the data interfacebetween the TU and the Controller. (Alarm inputs and con-trol outputs must be configured by the Controller or SystemManager before they can be used.)

The TU is basically a mobile radio with special TU soft-ware that operates under the direction of the Controller. TheTU is responsible for monitoring and reporting the health ofthe Control Channel, and for making test calls (that simulatemobile-originated channel-request sequences) and reportingthe health of the Working Channels used for the test calls.The TU also directs the switching of the ACU and TU to theBackup Controller (if installed).

The VHF, UHF, and 800 MHz TU can be operated in theUser Call Mode, allowing service personnel to use the TUlike a normal EDACS mobile.

230 VAC Modification Option

The 230 VAC Modification option substitutes the fol-lowing parts for their 120 VAC equivalents:230 VAC 6-Outlet Power Strip

• 230 VAC Cabinet Fan• Uninterruptible 230 VAC Power Supply• 230 VAC to 13.8 VDC Power Supply• 230 VAC System Manager Modem

Optional Cabinets

The EDACS Site Controller may also be mounted in op-tional cabinets of various sizes. See the description of cabi-net size in the Installation section. InterconnectionDrawings for the EDACS Site Controller are included at theend of this manual.

INSTALLATION

OVERVIEW

See the Basic and Level 1 EDACS installation manualfor complete installation instructions. Only the issues di-rectly concerning the EDACS Site Controller are coveredhere.

SITE REQUIREMENTS

Protective Grounding

Protective grounding is probably the most important sin-gle factor in reducing maintenance time and expense. Theserecommendations are thought to be adequate, but becauselightning intensity and frequency of occurrence are unpre-dictable, the user may wish to use larger ground wires,shorter distances, and/or additional protective devices basedon experience.

Each cabinet should have its own AWG 6 annealed cop-per wire connecting the inner welded structure of the cabi-net to an AWG 4 annealed copper ground buss, in anover-cabinet or under-cabinet cable duct. This ground busshould be connected to the site’s ground, no farther than 25feet away. All the EDACS equipment should be connectedto the site ground at the same point.

The EDACS Site Controller requires that all telephonelines, alarm inputs, control outputs, and data links to theSystem Manager and Multisite Coordinator, enter the equip-ment room via protected punch blocks or equivalent protec-tion.

LBI-38985

7

A coaxial cable grounding kit should be installed at thetop end of each coaxial cable run on the tower. A second kitshould be installed on the cable at the bottom of the tower. Athird kit should be installed on the cable at the point wherethe cable enters the building if the tower-to-building dis-tance is greater than 20 feet. For cable runs on the tower thatare greater than 200 feet, additional kits should be installedat each 200 foot interval.

A lightning arrester should be installed on the AC powerline at the point where the cable enters the building.

Environment

The EDACS Site Controller should be operated in acontrolled environment, between 17 and 27 degrees C (60and 80 degrees F) and 50% relative humidity.

Although the maintenance manuals for the individualpieces of equipment that make up the EDACS Site Control-ler give higher temperature limits, those limits are for thatone piece of equipment out in the open. When all of thesepieces are assembled together in a cabinet, the ambientroom temperature outside the cabinet must be significantlylower to assure that the temperature inside the cabinet doesnot exceed the limits for the equipment.

AC Power

The EDACS Site Controller requires an AC powersource of 121 VAC ±20% at 60 Hz ±2% with a receptacle

for the standard US 120 VAC grounding plug. The recepta-cle should be protected by a 20-amp circuit breaker and lo-cated within 4 feet of the cabinet, either in an above-cabinetcable tray or on a wall near the cabinet.

The 230 VAC option requires an AC power source of230 VAC ±15% at 50 Hz ±2% protected by a 10-amp circuitbreaker. A standard European plug is provided on the end ofthe cabinet’s power cord for this option.

MECHANICAL CONSIDERATIONS

Cabinet Size

The standard cabinet for the EDACS Site Controller is a69-inch high x 23-inch wide x 21-inch deep enclosed cabi-

net. An 83-inch high enclosed cabinet and an 86-inch highopen rack are used as options. Extra deep 69-inch and 83-inch cabinets are also sometimes used as special options andhave an additional 4 inches of depth.

Cabinet Location

The length and quantity of interconnecting site cablesbetween EDACS cabinets are based on using standard floorplans and on using cabinet-top cable ducts. For installationswhich require other than the standard floor layout or cablerouting, the interconnections may require additional materi-als or other special considerations. Standard floor plans areshown in the Basic and Level 1 EDACS installation manual.

Cabinet Mounting

A hole is located near each of the bottom 4 corners ofthe cabinet for fastening the cabinet to the floor with 1/2-inch diameter bolts.

Cabinet-Top Cable Duct Option

If optional cabinet-top ducts are used, see the mainte-nance manual for the EDACS Cable Duct System.

ELECTRICAL CONNECTIONS

EDACS Interface Panel Connections

Overview

Most audio and data connections between EDACS cabi-nets are made using 25-pair cables with 50-pin connectorsthat plug into EDACS Interface Panel #1, mounted in theback of each EDACS cabinet. Figure 2 shows where theseexternal cables connect to the EDACS Interface Panel #1 inthe EDACS Site Controller cabinet.

If a particular cable needs to go to several cabinets, thecabinets are daisy-chained together (EDACS Interface Panelto EDACS Interface Panel) by a series of individual cables.The EDACS Site Controller cabinet is connected to theclosest of the cabinets, and the daisy-chain continues fromthere. The Basic and Level 1 EDACS installation manualshows this daisy-chaining method for typical configura-tions.

Figure 3 shows where the external cables connect toEDACS Interface Panel #2 in the EDACS Site Controllercabinet.

Remember to check and clean the air filter in thecabinet door at regular intervals. Failure to do so maycause the equipment to overheat and fail.

CAUTION

LBI-38985

8

Figure 3 - External Connections To EDACS Interface Panel #2

A: Daisy-chain to channels 1-10 (2 repeaters per cabinet), or to channels 1-12 (3 repeaters per cabinet). Plug with shorting jumpers (in J1 of Power Sensor module) must be moved to the end of daisy chain.

B: Daisy-chain to channels 11-20 (2 repeaters per cabinet), or to channels 13-20 (3repeaters per cabinet) Plug with shorting jumpers (in J2 of Power Sensor module) must be moved to the end of daisy chain.

C: Daisy-chain to antenna sensors.

Figure 2 - External Connections To EDACS Interface Panel #1

A

B

A B B A B

C

CA

A: Downlink GETC and Redundant Downlink GETC Data Link to Multisite Coordinator.

B: LIX 2-wire audio links for telephone lines 1-16.

C: LIX 2-wire audio links for telephone lines 17-32.

B A

LBI-38985

9

Power Monitor Sensor Jumpers

The "POWER SENSOR" board in EDACS InterfacePanel #1 comes with two 19C852379G1 jumper modules,plugged into J1 and J2. If a site interconnect cable needs tobe connected to J1 or J2, the jumper module must be movedto the EDACS Interface Panel at the other end of this siteinterconnect cable or (if daisy chained) at the end of thedaisy chain.

These jumper modules come with all circuits jumpered,so jumpers for the circuits being used must be removed. Seethe Interconnect Drawings 6A and 6B, at the back of thismanual, to determine which jumper applies to which circuit.

Downlink and Redundant Downlink Connections

The "DOWNLINK DATA" board in EDACS InterfacePanel #2 provides a 50-pin connector for connection of theDownlink and Redundant Downlink from the Multisite Co-ordinator. Pin identification for the 50-pin connector isshown in Table 1.

Telephone Line Connections

The "PHONE LINE 1-16" and "PHONE LINE 17-32"modules in EDACS Interface Panel #2 provide two 50-pinconnectors for connection of up to 32 external 2-wire tele-phone lines, for use with the Local Telephone Interconnectoption. Pin identification for the two 50-pin connectors isshown in Table 2.

All unused sensor inputs must be jumpered (shorted)at an EDACS Interface Panel.

NOTE

The power sensors for transmitters 11 and 12 can beconnected to J1 (for sites with 2 repeaters per cabinet- see Interconnection Diagram 6A) or to J2 (for siteswith 3 repeaters per cabinet - see InterconnectionDiagram 6B). Therefore there are 2 jumpers in paral-lel for each of these 2 circuits and both jumpers mustbe removed (one for J1 and one for J2) if a powersensor is connected to the circuit for transmitter 11and/or 12.

NOTE

These data lines must come through protected punchblocks or equivalent protection before being con-nected to the EDACS Interface Panel.

CAUTION

126

Data Direction

Outgoing

Data Circuit

Downlink

227328429

Incoming

Outgoing

Incoming

Downlink

Redundant Downlink

Redundant Downlink

J14Pin #

+

+

__

+

+

__

Table 1 - Downlink Connection Pin Identification

EDACS Interface Modules

"PHONE LINE 1-16" "PHONE LINE 17-32"Line # Line #

J14Pin #

Polarity

1262273

4

5

6

7

8

9

28

29

30

31

32

33

34

RingTip

RingTipRingTipRingTip

RingTip

RingTip

RingTipRingTipRingTip

1

2

3

4

5

6

7

9

8

17

18

19

20

21

22

23

24

25

10

11

12

13

14

15

16

26

27

28

29

30

31

32

RingTipRingTipRingTipRingTipRingTipRingTipRingTip

10

11

12

13

14

15

16

35

36

37

38

39

40

41

Table 2 - Telephone Line Connection Pin Identification

These telephone lines must come through protectedpunch blocks or equivalent protection before beingconnected to the EDACS Interface Panel.

CAUTION

LBI-38985

10

Direct Connections

Overview

Most connections to user-supplied devices bypass theEDACS Interface Panels and connect directly to a specificpiece of equipment within the EDACS Site Controller cabi-net. The following direct connections to user-supplied de-vices may be required:

• 32 alarm inputs and 8 control outputs connecting tothe ACU (Alarm and Control Unit) option.

• An antenna connecting to the TU (Test Unit) option.• A data link to the System Manager connecting to the

System Manager Modem.• The AC power connection.

The locations of these direct connections to user-sup-plied devices are shown in Figure 4.

Use cable ties to secure the cables to the side rails of theEDACS Site Controller cabinet so that access is allowed tothe internal equipment without moving the cables, and sothat the appearance is neat and orderly.

Alarm and Control Unit (ACU)

The Alarm and Control Unit provides two 50-pin con-nectors for up to 32 alarm inputs (A1 through A32) to user-supplied, alarm-sensing devices. Typical alarm inputconfigurations are shown in Figure 5. Alarm input connec-tions are shown in Table 3.

The alarm and Control Unit also provides one 50-pinconnector for up to 8 control outputs (C1 through C8) touser-supplied control devices. Typical control output con-figurations are shown in Figure 6. Control output connec-tions are shown in Table 4.

Test Unit (TU)

The coaxial cable to the Test Unit antenna (if needed) isconnected to the end of the attenuator at the back of the TestUnit. See Figure 4. If the coaxial cable leaves the building, acoaxial cable grounding kit should be installed where thecable enters the building.

System Manager Modem

If the System Manager Modem is used, connect the tele-phone-line data link from the System Manager to the right-hand, 4-pin modular phone jack on the rear of the SystemManager Modem. See Figure 4.

Avoid routing any cables near the sharp end ofmounting screws, and route the cables so that mount-ing screws can be removed and re-installed withoutdamaging the cables.

CAUTION

Never make a direct connection between a power cir-cuit or ground in the external equipment, and a powercircuit or ground in the ACU.

CAUTION

These alarm inputs and control outputs must comethrough protected punch blocks or equivalent protec-tion before being connected to the ACU.

CAUTION

EDACS Interface Panel#1

EDACS Interface Panel#2

Alarm and Control Unit

Test Unit

J3 J4 J5

J1

to ExternalAlarm Inputs A1 - A16

Alarm Inputs A17-A32to External

Control Outputs C1-C8to ExternalControl Devices

Coax to TU Antenna

Data Link to System Manager

Alarm-Sensing Devices

Alarm-Sensing Devices

Figure 4 - External Connections Directly To Other Equipment (Rear View)

This data link must come through a protected punchblock or equivalent protection before connecting tothe modem.

CAUTION

LBI-38985

11

.

+V1

2

3

+

C

G

.

+V1

2

3

+

C

G

.

+V1

2

3

+

C

G

.

+V1

2

3

+

C

G

CCCC

RELAY CONTACT CLOSUREClosure=Logic 0=Active LED

OPEN COLLECTOR DRIVEXstr On=Logic 0=Active LED

+5 to +16 VDC

+5 to +16 VDC Return

Xstr On=Logic 0=Active LEDOPEN COLLECTOR DRIVE

+15 to +48 VDC

+15 to +48 VDC Return

OP AMP Driver+Output=Logic 0=Active LED

.

+15 VDC

-15 VDC

User-SuppliedEquipment

TAU Alarm Input

OptoelectronicCoupler

OptoelectronicCoupler

OptoelectronicCoupler

OptoelectronicCoupler

Figure 5 - Typical Alarm Input Configuration

FunctionConnector J4 Connector J5

Pin# Alarm # Pin # Alarm #+CG

1

2

3

4

5

6

7

8

9

26

27

28

29

30

31

32

33

34

A1

A2

A3

A4

A5

A6

A17

A18

A19

A20

A21

A22

1

2

3

4

5

6

7

8

9

26

27

28

29

30

31

32

33

34

A7

A8

A9

A10

A11

A12

A23

A24

A25

A26

A27

A28

10

11

12

13

14

15

16

17

18

35

36

37

38

39

40

41

42

43

10

11

12

13

14

15

16

17

18

35

36

37

38

39

40

41

42

43

A13

A14

A15

A16

A29

A30

A31

A32

19

20

21

22

23

24

44

45

46

47

48

49

50

19

20

21

22

23

24

44

45

46

47

48

49

50

--- ---+13.8 VDC*

* Requires jumper on the Alarm/Control Interface Board:

2525

--- ---PWR GND

jumper J40 for connector J4, jumper J41 for connector J5.See cautions about power circuits in text.

+CG

+CG+CG+CG+CG+CG

+CG+CG+CG+CG+CG

+CG

+CG+CG+CG

Table 3 - Alarm Input Connections Pin Identification

LBI-38985

12

If the System Manager Modem is not used, connect theSystem Manager to Port 0 (SM) on the back of the Control-ler using the connection shown in Figure 7.

OPERATION

This section concentrates on what general information ispassed between pieces of equipment, for what reason, andunder what circumstances. The operation of the discreteelectronic circuits is left to the individual LBI for that pieceof equipment. (Current LBI numbers are listed as Refer-ences following the Table of Contents.)

CONTROLLER (COMPUTER)

Overview

Although only the DEC model CT-UXXXF-EK Con-troller, characterized by the DEC model KDJ11 CPU mod-ule and modular RJ11-type connectors on the back, isspecifically covered in this manual, the operation of earlierPDP and VAX models, characterized by a separately-mounted, 32-port distribution panel (Emulex or Dilog), isthe same. For these earlier models, disregard informationabout PROM location.

The Controller operates by following the Controller Ap-plication Software, stored in a set of up to 14 PROMs. TheController Application Software requires certain informa-tion about the specific site where the Controller is located,such as Site ID, equipment available at the site, validationtables by feature and priority for each Logical (individual)ID and Group ID, etc. Initial values of the Controller’s Con-figuration (personality) are stored in a set of 2 PROMs. Theposition of these PROMs on the DEC model MRV11-DEPROM module is shown in Figure 8.

1 13 22 37 7

ShieldTx DataRx DataSignal GND

ShieldRx DataTx Data

Signal GND

Controller System Manager

DB-25 (F)DB-25 (F)

Figure 7 - System Manager To Controller Using Direct Connection

CCCC

TAU RELAY SWITCHES

TAU RELAY SWITCHES

User-SuppliedEquipment

TAU Control Output

USER'S RELAY

USER'S LOAD

.

+V

.

+13.8 VDC

TAU Output Relay

User's Loadto be Controlled

+13.8 VDC

N.O.

COM

N.C.

PWR GND

.

+V

TAU Output Relay

User's Loadto be Controlled

N.O.

COM

N.C.

Contacts

Contacts

Figure 6 - Typical Control Output Configurations

FunctionConnector J3

Pin# Control # Pin # Control #

1

2

3

4

5

6

7

8

9

26

27

28

29

30

31

32

33

34

A1

A2

A3

A4

A5

A6

A7

A8

10

11

12

35

36

37

N.O.COMN.C.N.O.COMN.C.N.O.COMN.C.N.O.COMN.C.

+5 VDC

LOG GND

+13.8 VDC

PWR GND

+5 VDC

LOG GND

+13.8 VDC

PWR GND

13

14

15

16

38

39

40

41

+5 VDC requires jumper P38 onthe Alarm/Control Interface Board.

+13.8 VDC requires jumper P39 onthe Alarm/Control Interface Board.

See cautions about power circuitsin text.

Table 4 - Control Output Connections Pin Identification

LBI-38985

13

Power-Up/Reset

Whenever the Controller is turned on or reset, the Con-troller loads the Application Software from its ApplicationSoftware PROMs and its Initial Configuration from its Per-sonality PROMs into a volatile working memory. The Con-troller then requests the current Site Database from theSystem Manager to update its Initial Configuration. TheController’s updated Initial Configuration becomes its Ac-tive Configuration. If for some reason the Controller cannotget the current Site Database from the System Manager, theController uses its Initial Configuration as its Active Con-figuration until it is able to obtain the current Site Databasefrom the System Manager.

Some parts of the Controller’s Initial Configuration,such as the Site ID, cannot be reconfigured by the SystemManager. If changes need to be made in the Controller’s In-itial Configuration, whether or not they can be reconfiguredby the System Manager, the changes in the Controller Per-sonality PROMs must be made in Lynchburg.

System Manager

The Controller supports the System Manager throughthe following chores:

• After power up or a reset, the Controller requests thelatest Site Database from the System Manager. TheSystem Manager responds by sending the current SiteDatabase to the Controller.

• At any time the System Manager may want toreconfigure the site and send the new information tothe Controller.

• The Controller sends stored activity reports to theSystem Manager when they reach a preset volume orwhen the System Manager requests them.

Call Validation

All call requests, sent to the Controller from either theControl Channel or Downlink GETC, are checked by theController against the Controller’s Active Configuration toverify that the caller’s Logical (individual) ID is permittedto make that type of call, and that the called Logical ID orGroup ID is permitted to receive that type of call. Possibletypes of calls are Analog Voice, Digital Voice, Data, andTelephone Interconnect. Only permitted requests are given atrunk assignment. These parameters can be reconfigured bythe System Manager.

Toll Call Restrictions

The Controller manages 16 levels of toll call restrictions- one for each caller’s Logical ID - to limit callers to variousgroups of area codes. This parameter can be reconfigured bythe System Manager.

Line Rotations

The Controller manages 15 rotary hunt sequences - onefor each caller’s Logical ID - used by the telephone equip-ment to find an available line when a radio requests a tele-phone interconnect call. This parameter can be reconfiguredby the System Manager.

Call Queuing

The Controller manages call queuing when all availableWorking Channels, for that requested call type, are in use.During this time of full loading, call requests are filled firstby priority level and second by time in queue. A special halflevel incremental priority is given to recent users.

01 02

13

24

57

68

911

1012

13 14PersonalityPROMS

Controller

01-02

Application

PROMSSoftware

Controller

1-14

Figure 8 - PROM Mounting In Controller

LBI-38985

14

Eight Priority Levels

The Controller manages 8 priority levels when fillingqueued call requests. The higher of the caller’s or thecallee’s priority is used.

Of the eight priority levels available, the highest prior-ity is reserved for emergency calls. The remaining sevenpriority levels are assigned to each Logical and Group ID(whether radio or telephone line) for each grade of service(Analog Voice, Digital Voice, Data, and Telephone Intercon-nect). These priority level assignments are contained in theController’s Active Configuration and can be reconfiguredby the System Manager.

Recent User Priority

The Controller gives a recent user a slight edge whencalls are being queued, to help maintain the continuity of aconversation. The Controller increases the priority of a callrequest half a level if the time between the last call requestand the current request is less than the recent call queue in-terval in its Active Configuration. This interval can be re-configured by the System Manager.

Alarm Management

The Controller Continuously monitors fault indicationsfrom the various diagnostic equipment at the site. Majoralarms, identified in its Active Configuration, must be re-ported to the System Manager immediately. Major and mi-nor alarm classifications, and most alarm parameters, can bereconfigured by the System Manager.

Activity Logging

The Controller continuously monitors the EDACS siteand logs all call requests, channel dispositions (assignmentsand disassignments), channel or equipment failures, andalarm information. These activities are formatted into re-cords and stored. When the stored activity records reach apreset volume, they are sent to the System Manager for lateruse in compiling various management reports. This presetvolume, called the Activity Dump Threshold, can be recon-figured by the System Manager.

If for some reason the Controller cannot communicatewith the System Manager before the stored records run outof storage space, the Controller writes over the oldest re-cords first. This allows the most recent records to be sentonce communications to the System Manager is restored.

Repeater Control

The Controller sends messages to the Station GETCstelling them which station operates as a Control Channeland which stations operate as Working Channels. The Con-troller also sends messages to the Station GETCs tellingeach Working Channel when to start transmitting and whento stop.

The Controller receives messages from the ControlChannel GETC requesting trunk assignments, and fromWorking Channel GETCs telling the Controller when call-ing radios start and stop transmitting on the assigned trunks.

When a Station GETC does not respond to Poll mes-sages, the Controller assumes that it is defective and doesnot assign it for use as a Control or Working Channel until itbegins to respond to Poll messages again. If the non-re-sponding GETC is the current Control Channel GETC, theController selects a new Control Channel and sends the newControl Channel assignment in the next Poll message to thatStation’s GETC.

The Controller communicates with each Station GETCthrough a separate 19.2 Kbaud serial data link. Messagebytes are made up of 8 data bits, 1 stop bit, and no paritybit. See Interconnection Diagrams 3A and 3B.

SYSTEM MANAGER MODEM

The standard configuration for connecting the Controllerto the System Manager uses a 2-wire, dial-up or dedicatedtelephone line with a modem at each end.

Port 0 (SM) of the Controller is connected to the modemthrough an asynchronous RS-232 serial data link. Messagebytes are made up of 8 data bits, 1 stop bit, and no paritybit. The baud rate is configurable through the Controller’sPersonality PROMs.

The modems convert this RS-232 serial data to a 9600bps modulated 1800 Hz carrier (for transmission over thetelephone line) and back to RS-232 serial data. The modemsalso take care of placing and answering calls if a dial-up lineis used.

If the distance between the Controller and the SystemManager does not exceed the 50-foot limit of the standardRS-232 interface, the modems can be omitted and replacedwith the direct connection shown previously in Figure 7.

LBI-38985

15

FULL-FEATURED TRUNKING

The Controller manages Full-Featured Trunking by fol-lowing the Controller Application Software and trunkingparameters in the Controller’s Active Configuration. TheSystem Manager has control over the following trunking pa-rameters (parameter values are customer specific - the val-ues indicated below apply when generic PersonalityPROMs are installed - some parameters have separate val-ues for individual and group calls):

• Which channel is the initial Control Channel - defaultis channel 1

• Which channels are the initial Working Channels -default is channels 2-20

• Which channels have Control Channel capability -default is channels 1-20

• Enable rotation of Working Channel assignments -default is enable

• Assign ascending or descending rotation - default isascending

• Assign alternating channel assignment algorithm toavoid intermod - default is disabled

• Which channels are equipped to handle digital voice -default is channels 1-20

• Which channels are equipped to handle data - defaultis channels 1-20

• Which channels are assigned as test channels - defaultis none

• Which radios are permitted to use test channels -default is none

• Which channels are permitted to be used in multisitecalls - default is channels 1-20

• Which radios are permitted to make multisite calls -default is none

• Time limit for transmission trunked calls - default is30 seconds

• Time limit for message trunked conversations -default is 30 seconds

• Hang time between unkey and channel drop - defaultis 0 seconds - note that hang time must be 0 fortransmission trunking and more than 0 for messagetrunking

• Hang time between unkey and channel drop foremergency calls - default is 2 seconds

• Maximum number of simultaneous individual callspermitted - default is 20

• Queue priority for voice calls - default is lowestpriority (zero)

• Queue priority for digital voice calls - default islowest priority (zero)

• Queue priority for data calls - default is lowestpriority (zero)

• Time limit between call requests to qualify for recentcall priority increment - default is 5 seconds

• Time interval between Morse code ID transmissionson Working Channels - default is 15 minutes

• Time between scramble data calls used to discourageunauthorized monitoring - default is 5 seconds - notethat an interval of 0 inhibits this feature

When an EDACS mobile or portable radio is turned on,its receiver scans the channels of the system looking for theControl Channel sending a control message every 30 milli-seconds. The radio decodes and synchronizes itself with thisperiodic control message. When the radio is synchronizedwith the Control Channel, it is ready to place or receivetrunked calls. The following sequence of steps describes aFull-Featured Trunking call:

1. The user of a mobile or portable radio selects thecommunication mode (analog voice, digital voice, ordigital data), call type (group, emergency group, in-dividual, or system all call), and the individual orgroup called. An individual call from a radio can beto another radio, or can be a telephone interconnectcall. A telephone interconnect call form a telephonecan be to an individual or group. The user thenpushes the Push-To-Talk (PTT) switch on the radio.

2. The radio transmits a call request message on theControl Channel. The message includes the radio’sidentification (Logical ID), communication mode,call type, and the identification (Logical ID or GroupID) of the called radio(s).

3. The Control Channel GETC receives the call requestfrom the calling radio, translates it to Controller pro-tocol, and sends a call/channel request message tothe Controller.

4. The Controller receives the message and checks withits Active Configuration to see if the request is per-mitted. (If it isn’t permitted, the Controller sends anappropriate system busy or call denied message tothe Control Channel GETC which in turn sends aproper indication to the calling radio.)

5. If the call request is permitted, the Controller checksto see if a Working Channel is available. (If a Work-ing Channel is not currently available, the Controllerqueues the call request and directs the Control Chan-nel GETC to send a queued-call signal to the callingradio. When the call request comes out of queue,continue to next step.) If queuing is disabled or oth-erwise not possible, the Controller generates a sys-tem busy indication.

6. The Controller directs the Control Channel GETC tosend the Working Channel assignment to the callingand called radios. The Controller also sends channelassignments to the Downlink to support multisite

LBI-38985

16

and/or console operation. This channel assignmentincludes a hang time value for this call. A hang timeof zero indicates Transmission Trunking; non-zeroindicates Message Trunking.

7. The calling and called radios receive the WorkingChannel assignment from the Control ChannelGETC and tune to the assigned Working Channel.

8. A high speed handshake on the Working Channelwith the calling radio occurs.

9. After confirmation, the caller hears the "ok to trans-mit" prompt tone alerting the caller to begin talking.

10. Signaling on the assigned Working Channel tells thecalled radio(s) to unmute their speakers.

11. When the caller finishes talking, the caller releasesthe PTT switch, sending an unkey message to the as-signed Working Channel and all called radio(s). TheController receives either a call dropped (Transmis-sion Trunked call) or a call unkey (Message Trunkedcall).

12. With Transmission Trunking, the radios involved inthe call return to monitor the Control Channel. WithMessage Trunking, the radios stay on the WorkingChannel until hang time expiration or manual drop.

FAILSOFT TRUNKING

If the Controller fails, the site continues to provide thetrunking feature by switching to the Trunked Failsoft modeof operation to provide Failsoft Trunking. Failsoft Trunkingis managed by the Control Channel GETC through thedaisy-chained backup serial link to the other Station andDownlink GETCs. See Interconnection Diagrams 4A and4B.

The sequence of steps for a Failsoft Trunking call isidentical to that of a Full-Featured Trunking call except thatthe Control Channel GETC manages the trunking instead ofthe Controller. The following features and options are notusable during Failsoft Trunking:

• Call Validation• Activity Logging• Basic Diagnostics• Eight Levels of Priority• Local Telephone Interconnect• Dynamic Regrouping• Unit Enable/Disable• Patch• Simulselect

MULTISITE TRUNKING AND CONSOLEOPERATION

Multisite Trunking and console operation is not coveredin this manual except to mention the function of the Down-link and Redundant Downlink GETCs.

Downlink GETC

The Downlink GETC serves as the interface between theController and the Downlink to the multisite/consoleswitch. When managing calls placed between sites (or be-tween a site and a console), the Controller sends messagesto and receives messages from the multisite/console switchthrough the Downlink GETC. The Controller communicateswith the Downlink GETC over a 19.2 Kbaud RS-232 datalink connecting Port 26 on the back of the Controller toJ100 on the back of the Downlink GETC. Message Bytesare made up of 8 data bits, 1 stop bit, and no parity bit. SeeInterconnect Diagrams 4A and 4B.

If the site is in the Failsoft Trunking mode of operation,the individual Station GETCs send messages to and receivemessages from the Multisite Coordinator through theDownlink and the Downlink GETC over the daisy-chainedRS-232 Backup Data Link connecting J102 on each StationGETC to J102 on the Downlink GETC.

Redundant Downlink GETC Option

If the Downlink or Uplink GETC, or the physical linkbetween them fails, the Redundant Downlink GETC servesas the data interface between the Controller (or the StationGETCs if the site is in the Trunked Failsoft mode of opera-tion) and the multisite/console switch.

The connections to the Redundant Downlink GETC areidentical to those for the Downlink GETC, except for theconnection to the Controller. The Controller communicateswith each Redundant Downlink GETC on a selectable port(typically ports 21-25), as specified in its Active Configura-tion.

LOCAL TELEPHONE INTERCONNECTOPTION

Overview

Operation of the Local Telephone Interconnect option(manufactured by IDA) is a cooperative function of the LineInterconnect Controller (LIC) plug-in module of the LocalTelephone Interconnect, and Repeater Interconnect Control-ler (RIC) shelf connected to each repeater configured fortelephone interconnect calls. Each operates by following itsown software and responding to messages from the Control-ler.

LBI-38985

17

The System Manager has control over the following Lo-cal Telephone Interconnect parameters in the Controller’sActive Configuration (Trunking parameters also apply - seeFull-Featured Trunking section - default values are cus-tomer specific; the values indicated below apply when ge-neric Personality PROMs are installed):

• Which channels are equipped to handle telephoneinterconnects - default is channels 1-20

• What is the telephone interconnect Hang Timebetween unkey and channel drop - default is 30seconds

• What is the maximum number of simultaneoustelephone interconnect calls permitted - default is 20

• What is the level of toll call restrictions for eachindividual radio - default is totally restricted

• What is the queue priority for telephone interconnectcalls for each radio - default is lowest priority (zero)

• Which radios are permitted to receive inboundtelephone interconnect calls - default is no Group IDs(all are Logical IDs)

• What line number is dedicated to outgoing calls foreach individual radio - default is 1

• What is the rotary hunt sequence for each individualradio - default is none - note that a none for bothrotary hunt sequence and dedicated line numberprevents telephone interconnect calls for that radio

The Controller supervises the Local Telephone Intercon-nect over two 19.2 Kbaud serial data links: one to the LICmodule, and one daisy-chained to all the RIC shelves. Mes-sage bytes are made up of 8 data bits, 1 stop bit, and no par-ity bit. See Interconnect Diagrams 5A and 5B.

Telephone interconnect calls utilizing a CentralizedTelephone Interconnect system are managed by the Mul-tisite Coordinator. Their operation is not described here.

Telephone-Originated Call on a DedicatedLine

When a telephone line is dedicated to a Logical (individ-ual) ID or Group ID, telephone-originated calls coming inon this line will only go to the specific radio or group of ra-dios assigned to that line.

The sequence of steps for a telephone-initiated tele-phone interconnect call coming in on a dedicated line is asfollows:

IDENTIFYING LINE TYPE

1. When a call comes in on one of the telephone linesconnected to the Local Telephone Interface, the LICreports to the Controller that a LIX has detectedringing voltage on a calling line.

2. The Controller receives the report from the LIC thatringing voltage has been detected on a calling lineand checks to see if it is permitted to add anothertelephone interconnect call. There may be a limit,imposed by the System Manager, on the number oftelephone interconnect calls allowed at any one time.(If the Controller is not permitted to add anothertelephone interconnect call, the Controller lets the in-coming call go unanswered and never reconsidersthat incoming call again, even if room for the call isavailable before the caller hangs up. So if the callerdoes not get an answer within 3 ringbacks, the callershould hang up and call again. This ends the se-quence here.)

3. If the Controller is permitted to add another tele-phone interconnect call, the Controller checks to seeif the incoming call is on a dedicated line or a non-dedicated line. (If it is on a non-dedicated line, seethe next sequence of steps, Telephone-OriginatedCall on a Non-Dedicated Line.)

OBTAINING WORKING CHANNEL

4. If the incoming call is on a dedicated line, the Con-troller checks to see if a Working Channel with aRIC is available. (If no Working Channel with a RICis currently available, the Controller lets the incom-ing call go unanswered. The caller should hang upand call back after 3 ringbacks. This ends the se-quence here.)

5. If a Working Channel with a RIC is available, theController directs the LIC to have the LIX connectitself to the calling line (to simulate a telephone be-ing taken "off hook"). A LED on the front of the LIXindicates which line is "off hook".

6. The telephone exchange detects that the calling line(actually the called line from the telephone exchangepoint of view) has come "off hook", and removes theringing voltage from the calling line.

7. The Controller directs the Control Channel GETC tosend the Working Channel assignment to the radio(s)with the Logical (Group) ID assigned to the dedi-cated line.

8. The Controller directs the assigned Working ChannelRIC to connect its associated radio channel for atelephone interconnect call without DTMF regenera-tion.

LBI-38985

18

9. The Controller directs the LIC to have the LIX con-nect the assigned Working Channel RIC to the call-ing line.

10. The Controller directs the assigned Working ChannelRIC to send a call-completion tone to the calling lineand the called radio(s). The audio path is now con-nected between the calling line and the called ra-dio(s).

11. The Controller directs the assigned Working ChannelRIC to connect its DTMF decoder to the calling line,to be able to detect the end-of-call DTMF digit fromthe calling line.

ENDING THE CALL

12. To end the telephone interconnect call, the callerpresses the # key on the DTMF keypad of the tele-phone.

13. The assigned Working Channel RIC detects this end-of-call DTMF # digit and reports it to the Controller.

14. The Controller receives the DTMF digit and identi-fies it as the end-of-call signal.

15. The Controller directs the assigned Working ChannelRIC to disconnect audio.

16. The Controller directs the LIC to have the LIX dis-connect itself from the assigned Working ChannelRIC.

17. The Controller directs the LIC to have the LIX dis-connect itself from the calling line (to simulate atelephone being put "on hook").

If at the end of the call the caller forgets to press the #key, the callee can push the EXIT, SPC, or designated but-ton on the radio. See the operator’s manual for the radio.The radio will then transmit the disconnect signal to theWorking Channel GETC. If neither the caller nor the calleepushes any button or key, the conversation time interval willtime out and terminate the call.

Telephone-Originated Call on aNon-Dedicated Line

When a telephone line isn’t dedicated to a Logical (indi-vidual) ID or Group ID, telephone-originated calls coming

in on these lines can go to any valid radio or group of radiosprovided the caller has a DTMF keypad.

The sequence of steps for a telephone-initiated tele-phone interconnect call coming in on a non-dedicated line isas follows:

IDENTIFYING LINE TYPE

1. When a call comes in on one of the telephone linesconnected to the Local Telephone Interface, the LICreports to the Controller that a LIX has detectedringing voltage on a calling line.

2. The Controller receives the report from the LIC thatringing voltage has been detected on a calling lineand checks to see if it is permitted to add anothertelephone interconnect call. There may be a limit,imposed by the System Manager, on the number oftelephone interconnect calls allowed at any one time.(If the Controller is not permitted to add anothertelephone interconnect call, the Controller lets the in-coming call go unanswered and never reconsidersthat incoming call again, even if room for the call isavailable before the caller hangs up. So if the callerdoes not get an answer within 3 ringbacks, the callershould hang up and call again. This ends the se-quence here.)

3. If the Controller is permitted to add another tele-phone interconnect call, the Controller checks to seeif the incoming call is on a dedicated line or a non-dedicated line. (If it is on a dedicated line, see theprevious sequence of steps for a telephone-initiatedtelephone interconnect call coming in on a dedicatedline.)

BORROWING A RIC

4. If the incoming call is on a non-dedicated line, theController checks to see if a RIC is available just todecode DTMF digits from the calling line. The Con-troller first checks the availability of the ControlChannel RIC, since it is not used for Control Chan-nel operation. If the Control Channel RIC is not cur-rently available, the Controller checks to see if oneof the Working Channel RICs is available. (If noRIC is currently available, the Controller lets the in-coming call go unanswered. The caller should hangup and call back after 3 ringbacks. This ends the se-quence here.)

5. If a RIC is available, the Controller directs the LICto have a LIX connect itself to the calling line (tosimulate a telephone being taken "off hook"). A LED

LBI-38985

19

on the front of the LIX indicates which line is "offhook".

6. The telephone exchange detects that the calling line(actually the called line from the telephone exchangepoint of view) has come "off hook", and removes theringing voltage from the calling line.

7. The Controller directs the LIC to have the LIX con-nect itself to the borrowed RIC.

8. The Controller directs the borrowed RIC to startsending a dial tone to the calling line.

9. The Controller directs the borrowed RIC to connectits DTMF decoder towards the calling line.

10. The Controller starts a rapid polling mode of opera-tion to poll the LIC and borrowed RIC more fre-quently than usual.

11. The caller hears the dial tone from the borrowedRIC, and starts sending DTMF digits indicatingwhether the call is to an individual or a group,whether the call is conventional or Voiceguard, andthe ID of the individual or group.

IDENTIFYING CALLED ID

12. The borrowed RIC detects the first DTMF digit andreports it to the Controller.

13. The Controller directs the borrowed RIC to stopsending a dial tone to the calling line, and sets up acounter to count the received DTMF digits.

14. The Controller receives the report from the borrowedRIC and checks the first DTMF digit to see if it is a*, #, or number from 0 to 9. If the first DTMF digitis a *, the call is identified as a group call and the *is counted as a digit. If the first DTMF digit is a #,the call is identified as a Voiceguard call but the # isnot counted as a digit. If the first DTMF digit is anumber from 0 to 9, the digit is stored in the ID buff-er and is counted as a digit.

15. The borrowed RIC detects the next DTMF digit andreports it to the Controller.

16. The Controller receives the report from the borrowedRIC, stores the digit in its ID buffer, and advancesthe counter by 1. (If the counter is less than 5, returnto step 15.)

17. If the counter equals 5, the Controller has receivedall 5 digits of the ID, and the Controller directs theLIC to have the LIX disconnect itself from the bor-rowed RIC.

OBTAINING WORKING CHANNEL

18. The Controller checks to see if a Working Channelwith a RIC is available. (If no Working Channel witha RIC is currently available, the Controller queuesthe call. When the call comes out of queue, continueto the next step.)

19. If a Working Channel with a RIC is available, theController directs the Control Channel GETC tosend the Working Channel assignment to the radio(s)with the Logical (Group) ID called.

20. The Controller directs the assigned Working ChannelRIC to connect its associated radio channel for atelephone interconnect call without DTMF regenera-tion.

21. The Controller directs the LIC to have the LIX con-nect itself to the assigned Working Channel RIC.

22. The Controller directs the assigned Working ChannelRIC to send a call-completion tone to the calling lineand the called radio(s). The audio path is now con-nected between the calling line and the called ra-dio(s).

23. The Controller directs the assigned Working ChannelRIC to connect its DTMF decoder to the calling line,to be able to detect the end-of-call DTMF digit fromthe calling line.

ENDING THE CALL

24. To end the telephone interconnect call, the callerpresses the # key on the DTMF keypad of the tele-phone.

25. The assigned Working Channel RIC detects this end-of-call DTMF # digit and reports it to the Controller.

26. The Controller receives the DTMF digit and identi-fies it as the end-of-call signal.

27. The Controller directs the assigned Working ChannelRIC to disconnect audio.

LBI-38985

20

28. The Controller directs the LIC to have the LIX dis-connect itself from the assigned Working ChannelRIC.

29. The Controller directs the LIC to have the LIX dis-connect itself from the calling line (to simulate atelephone being put "on hook").

If at the end of the call the caller forgets to press the #key, the callee can push the EXIT, SPC, or designated but-ton on the radio. See the operator’s manual for the radio.The radio will then transmit the disconnect signal to theWorking Channel GETC. If neither the caller nor the calleepushes any button or key, the conversation time interval willtime out and terminate the call

Radio-Originated Call

A request for a telephone interconnect call can be madefrom any radio that is equipped to place telephone intercon-nect calls, but will only be connected if the Controller’s Ac-tive Configuration permits that specific radio to place thatspecific type of call. Of those radios so equipped, some maynot be permitted to place any type of telephone interconnectcall, some may only be permitted to place a local call, andsome may be permitted to place some toll calls in additionto a local calls. The System Manager manages and modifiesthese call restrictions as needed.

To place a telephone interconnect call, the radio mustsend telephone number digits to the Controller. There are 3sources of telephone number digits:

• Telephone number digits may be prestored in theradio when the radio is programmed.

• Telephone number digits may be temporarily stored atthe time of the call by entering the telephone numberdigits using the keypad on the radio.

• Telephone number digits may be sent without beingstored, as DTMF digits directly from the keypad onthe radio.

A telephone number can be made up entirely from anyone of the three sources of telephone number digits, from acombination of one or more prestored digits followed by theremaining DTMF digits, or from a combination of one ormore temporarily stored digits followed by the remainingDTMF digits.

Both prestored and temporarily stored telephone numberdigits are digitally transmitted to the Control ChannelGETC where they are translated to Controller protocol andsent to the Controller. DTMF digits are transmitted as audiotones to the assigned Working Channel RIC where they aredecoded and sent to the Controller.

The end of a group of prestored or temporarily storeddigits, whether or not it is the end of the telephone number,is marked with a digit stream terminator automatically bythe calling radio. The end of the telephone number, whenthe last digit is a DTMF digit, whether or not it is added tothe end of a group of prestored or temporarily stored digits,must be marked manually by the caller by pressing the *key following the last digit of the telephone number. Failureto do so will cause the call to be dropped at the end of atimed interval.

All telephone number digits are intercepted, checked forall applicable toll call restrictions, and logged before a tele-phone line is actually connected and the regenerated DTMFor pulsed digits are sent to the telephone line. Any DTMFoverdialed digits, sent by the calling radio after the calledtelephone answers, are also logged by the Controller but areallowed to pass directly to the telephone line without inter-ception and regeneration.

The sequence of steps for a radio-initiated telephone in-terconnect call is as follows:

OBTAINING WORKING CHANNEL

1. The radio user sets the radio to the mode of opera-tion that allows an interconnect call, and selects aprestored telephone number or manually enters atemporarily-stored telephone number.

2. he radio user keys the radio, which sends a requeston the Control Channel for a telephone interconnectcall.

3. The Control Channel GETC receives the request,translates it to Controller protocol, and sends a callrequest message to the Controller.

4. The Controller receives the call request messagefrom the Control Channel GETC and checks to see ifit is permitted to add another telephone interconnectcall. There may be a limit, imposed by the SystemManager, on the number of telephone interconnectcalls allowed at any one time. (If the Controller isnot permitted to add another telephone interconnectcall, the Controller directs the Control ChannelGETC to send a busy signal to the calling radio. Thisends the sequence here.)

5. If the Controller is permitted to add another tele-phone interconnect call, the Controller checks to seeif the caller is allowed to place some type of tele-phone interconnect call. (If the caller is not allowedto place some type of telephone interconnect call, theController directs the Control Channel GETC to

LBI-38985

21

send a call-denied signal to the calling radio. Thisends the sequence here.)

6. If the caller is allowed to place some type of tele-phone interconnect call, the Controller checks to seeif the LIC appears to be working. (If the LIC appearsto have failed, the Controller directs the ControlChannel GETC to send a call-denied signal to thecalling radio. This ends the sequence here.)

7. If the LIC appears to be working, the Controllerchecks to see if a telephone line is available. (If atelephone line is not available, the Controller directsthe Control Channel GETC to send a busy signal tothe calling radio. This ends the sequence here.)

8. If a telephone line is available, the Controller allo-cates a telephone line for the telephone interconnectcall and checks to see if a Working Channel with aRIC is available. (If a Working Channel with a RICis not available, the Controller queues the call re-quest and directs the Control Channel GETC to senda cueued-call signal to the calling radio. When thecall request comes out of queue, continue to nextstep.)

9. The Controller directs the Control Channel GETC tosend the Working Channel assignment to the callingradio and directs the assigned Working ChannelGETC to establish contact with the calling radio.

10. The calling radio receives the Working Channel as-signment from the Control Channel GETC and tunesto the assigned Working Channel.

DIGITALLY-TRANSMITTED DIGITS

11. The calling radio confirms the connection with theassigned Working Channel GETC, and digitallytransmits all of the prestored or temporarily storedtelephone number digits and the digital stream termi-nator to the Working Channel GETC. The assignedWorking Channel GETC and the calling radio hand-shake until the digital stream terminator is received.(If the digital stream terminator is not received bythe assigned Working Channel GETC within the al-lowed time interval, the Controller directs the as-signed Working Channel GETC to terminate the calland deallocate the telephone line. This ends the se-quence here.)

12. he assigned Working Channel GETC receives all ofthe prestored or temporarily stored telephone numberdigits and the digital stream terminator from the call-ing radio, translates them to Controller protocol, and

sends them in a message to the Controller. More thanone message may be sent, depending on the length ofthe telephone number.

13. The Controller receives the message(s) containingthe telephone number digits and the digital streamterminator from the Working Channel GETC, trans-lates the message(s) into telephone number digitsand stores them, and counts how many telephonenumber digits were received before the digitalstream terminator was received.

14. If 4 or more telephone number digits were receivedbefore receiving the digital stream terminator, theController checks the first 4 telephone number digitsfor all applicable toll call restrictions for that radio.Go to step 32. (If the Controller determines that the 4telephone number digits fail any applicable toll callrestriction, the Controller directs the assigned Work-ing Channel GETC to terminate the call and deallo-cate the telephone line. This ends the sequence here.)

15. If less than 4 telephone number digits were receivedbefore receiving the digital stream terminator, theController assumes that the digits received (if any)are the very first digits of the telephone number andchecks for all applicable toll call restrictions for thatradio, using all possible values for any of the 4 digitsthat are missing. (If the Controller determines thatthe telephone number digits (or the lack of them)fails any applicable toll call restrictions for that ra-dio, the Controller directs the assigned WorkingChannel GETC to terminate the call, and deallocatesthe telephone line. This ends the sequence here.)

DTMF CODED DIGITS

16. The Controller directs the assigned Working ChannelRIC to connect its DTMF decoder to interceptDTMF digits from the calling radio.

17. The Controller directs the assigned Working ChannelRIC to generate and send a psuedo dial-tone to thecalling radio.

18. The Controller starts a timer. (If the Controller doesnot receive a message from the assigned WorkingChannel RIC containing the first DTMF digit withinthe time allowed, the Controller directs the assignedWorking Channel GETC to terminate the call, directsthe assigned Working Channel RIC to stop generat-ing and sending a psuedo dial-tone to the calling ra-dio, and deallocates the telephone line. This ends thesequence here.)

LBI-38985

22

19. The Calling radio receives the psuedo dial-tone andthe caller proceeds to send DTMF digits using theDTMF keypad on the radio.

20. The assigned Working Channel RIC receives the firstDTMF digit from the calling radio, translates it toController protocol, and sends a message containingthe first DTMF digit to the Controller.

21. The Controller receives a message from the assignedWorking Channel RIC containing the first DTMFdigit, directs the assigned Working Channel RIC tostop generating and sending a psuedo dial-tone to thecalling radio, stores this DTMF digit with any pre-viously received digitally-transmitted telephonenumber digit(s) if there were any, and counts the to-tal number of telephone number digits accumulatedso far.

22. If the number of accumulated telephone number dig-its is now 4, go to step 26.

23. If the number of accumulated telephone number dig-its is still less than 4, the Controller starts a timer. (Ifthe Controller does not receive a message containingthe next DTMF digit within the time allowed, theController directs the assigned Working ChannelGETC to terminate the call, and deallocates the tele-phone line. This ends the sequence here.)

24. The assigned Working Channel RIC receives thenext DTMF digit from the calling radio, translates itto Controller protocol, and sends a message contain-ing the next DTMF overdialed digit to the Control-ler.

25. The Controller receives a message containing thenext DTMF digit, stores the digit. with the pre-viously received telephone number digits, and countsthe number of telephone number digits accumulated.(If less than 4 telephone number digits have been ac-cumulated, return to step 23.)

26. If 4 telephone number digits have been accumulated,the Controller checks these 4 accumulated telephonenumber digits for all applicable toll call restrictionsfor that radio. (If the Controller determines that these4 telephone number digits do not pass all applicabletoll call restrictions for that radio, the Controller di-rects the assigned Working Channel GETC to termi-nate the call, and deallocates the telephone line. Thisends the sequence here.)

27. If the Controller determines that these 4 telephonenumber digits do pass all applicable toll call restric-

tions for that radio, the Controller starts a timer. (Ifthe Controller does not receive a message containingthe next DTMF digit within the time allowed, theController directs the assigned Working ChannelGETC to terminate the call, and deallocates the tele-phone line. This ends the sequence here.)

28. The assigned Working Channel RIC receives thenext DTMF digit from the calling radio, translates itto Controller protocol, and sends a message contain-ing the next DTMF digit to the Controller.

29. The Controller receives a message containing thenext DTMF digit and checks to see if it is the * keyindicating the end of the telephone number. (If theDTMF digit is the * key, go to step 32.)

30. If the DTMF digit is not the * key, the Controllerchecks to see if it has room to store any more digits.A maximum of 32 digits can be stored for a tele-phone number. (If the Controller has already stored32 digits, the Controller directs the assigned Work-ing Channel GETC to terminate the call, and deallo-cates the telephone line. This ends the sequencehere.)

31. If the Controller has not already stored 32 digits, theController stores this DTMF digit with the pre-viously stored digits. Return to step 27.

DIALING TO TELEPHONE LINE

32. The Controller directs the assigned Working ChannelRIC to look for dial tone from the telephone line.

33. The Controller directs the LIC to have the LIX con-nect itself to the allocated telephone line (to simulatea telephone being taken "off hook").

34. The Controller directs the LIC to have the LIX con-nect itself to the assigned Working Channel RIC.

35. The Controller starts a timer for the dial tone

36. The telephone exchange detects that the allocatedline is "off hook", and applies dial tone to the allo-cated line.

37. If the assigned Working Channel RIC detects dialtone, go ahead to step 43.

38. If the assigned Working Channel RIC does not reportto the Controller that it has detected dial tone withinthe time allowed by the Controller, the Controller di-rects the RIC to send a momentary tone to both the

LBI-38985

23

radio and the telephone line to indicate that a prob-lem has been encountered.

39. The Controller directs the LIC to have the LIX dis-connect itself from the assigned Working ChannelRIC.

40 The Controller directs the LIC to have the LIX dis-connect itself from the allocated line.

41. The Controller checks to see if a telephone line isavailable. (If a telephone line is not available, theController directs the Control Channel GETC tosend a busy signal to the calling radio.

42. If a telephone line is available, the Controller allo-cates that line for the telephone interconnect call. Re-turn to step 32.

43. The assigned Working Channel RIC reports to theController that it has detected dial tone.

44. The Controller receives the report from the assignedWorking Channel RIC and checks to see if the allo-cated telephone line requires pulsed or DTMF dial-ing.

45. If pulsed dialing is required, the Controller directsthe LIC to apply dial pulses on the allocated tele-phone line corresponding to each digit of the tele-phone number called. The caller will hear the dialpulsed digits as they are sent.

46. If DTMF dialing is required, the Controller directsthe assigned Working Channel RIC to generate andsend the DTMF digits to the allocated telephone line.The caller will hear the DTMF digits as they aresent.

47. The Controller directs the assigned Working ChannelRIC to connect its DTMF decoder to the assignedWorking Channel to detect any DTMF overdialeddigits that might come from the radio.

48. The Controller starts a timer for the telephone inter-connect call.

49. When the called telephone answers, the audio path isconnected between the calling radio and the calledtelephone.

ENDING THE CALL

50 If the caller terminates the call before the time al-lowed by the Controller, go to step 51. If the timertimes out first, go to step 54.

51. The telephone interconnect call can be terminated bypressing the EXIT button on the front of the radio, tocause the radio to transmit a digitally transmittedend-of-call signal to the assigned Working ChannelGETC.

52. The assigned Working Channel GETC or RIC re-ceives the end-of-call signal from the calling radio,and sends it in a message to the Controller.

53. The Controller receives the message from the as-signed Working Channel GETC or RIC and deter-mines that it is the end-of-call signal.

54. The Controller directs the assigned Working ChannelRIC to disconnect audio.

55. The Controller directs the LIC to have the LIX dis-connect itself from the assigned Working ChannelRIC.

56. The Controller directs the LIC to have the LIX dis-connect itself from the allocated telephone line.

57. The Controller directs the assigned Working ChannelGETC to terminate the call.

POWER MONITOR UNIT OPTION

The Power Monitor Unit (PMU) operates by followingits own custom PMU software and responding to messagesfrom the Controller. The System Manager has control overthe following PMU parameters in the Controller’s ActiveConfiguration:

• PMU Enabled (default is enabled)• PMU Power Level (alarm threshold of the output

power level - default is 30 watts)

The Controller communicates with the PMU through a2400 baud serial data link. Message bytes are made up of 8data bits, 1 stop bit, and no parity bit. See InterconnectionDiagrams 6A and 6B.

The Controller uses the following 6 messages to super-vise the operation of the PMU:

• Clear Alarms• Poll

LBI-38985

24

• Enable Mask• Program Threshold• Power Request• On Channel

The PMU uses the following 2 messages to report theresults of its activities to the Controller:

• Status• Channel Power

When the PMU powers-up or the Controller is reset, theController sends a Clear Alarm message to the PMU whichcauses the PMU to clear all 22 alarm circuits.

The PMU enables or disables each individual alarm cir-cuit using information from the Enable Mask message re-ceived from the Controller.

The PMU sends a Status message to the Controller eachtime it receives a Poll message from the Controller. TheStatus message contains the current state of all 22 alarm cir-cuits. Only enabled alarm circuits report alarm conditions.

The PMU determines if an alarm condition has been metby comparing the measurements and calculations to thethreshold values programmed through the front keypad. Theminimum transmit power threshold values can also be ad-justed by the System Manager, by having the Controllersend a Program Threshold message to the PMU.

The PMU only makes measurements for a specific chan-nel’s transmitter when that transmitter is in use under the di-rection of the Controller. As the Controller directs aWorking Channel, it also sends a Channel Assignment mes-sage and a Channel Drop message to the PMU, so the PMUknows when to start and stop the measurements, and whichchannel’s RF sensors to measure. (Which antenna is usedwith which transmitter must be programmed into the PMUat installation time using the front keypad.)

When the PMU determines that an alarm condition hasbeen met and the alarm circuit is enabled, the PMU immedi-ately sends a Status message to the Controller without wait-ing to receive a Poll message.

TEST AND ALARM UNIT OPTION

The Test and Alarm Unit (TAU) option is made up of theAlarm and Control Unit (ACU), and the Test Unit (TU). TheACU can also be operated without the TU, but the TU can’tbe operated without the ACU (because the TU dependsupon interface circuitry in the ACU to communicate withthe Controller).

Alarm and Control Unit

The Alarm and Control Unit (ACU) operates by follow-ing its own ACU software and responding to messages fromthe Controller. The System Manager has control over thefollowing ACU parameters in the Controller’s Active Con-figuration:

• Enabled (which alarm circuits are enabled - default isdisabled)

• Active High (which alarm circuits are consideredactive or alarmed for a logic high input)

• Major (which alarm circuits are considered majoralarms)

• Relay On (which relays are set - default is reset)

The Controller communicates with the ACU through a19.2 Kbaud asynchronous serial data link. Message bytesare made up of 8 data bits, 1 stop bit, and no parity bit. SeeInterconnection Diagram 7.

The Controller uses the following 4 messages to super-vise the operation of the ACU:

• Poll• Set Relays• Alarm Mask• Reset

The ACU uses the following message to report the re-sults of its activities to the Controller:

• Status

All 4 messages from the Controller give the latest statusof the 8 system status parameters listed on the front of theACU. The ACU responds by turning LEDs on and off asneeded.

The Status message from the ACU gives the latest statusof 32 alarm inputs, 8 control outputs, and 8 alarm unit statusparameters. This status information is also displayed on thefront of the ACU.

The Controller sends a Poll message at regular intervals.The ACU responds each time with a Status message.

The Alarm Mask message from the Controller containsthree 32-bit masks. The Enable/Disable mask contains a 1 inthe bit locations representing each alarm input to be en-abled. The ACU responds by reporting a disabled alarm in-put as normal (not in the alarm state), whether the actualalarm input is in the normal or the alarm state. The ActiveHi/Low mask contains a 1 in the bit locations representingeach alarm input where the alarm state is a logic high. TheACU uses this mask to determine the alarm state for eachalarm input. The Major/Minor Alarm mask contains a 1 inthe bit locations representing each alarm point designated as

LBI-38985

25

a major alarm. The ACU uses this mask to determine if analarm is a major alarm or a minor alarm.

The ACU continually scans the 32 alarm inputs, lookingfor changes from user-supplied alarm-sensing devices. TheACU uses the Active Hi/Low mask to determine an alarmstate and the Enable/Disable mask to determine whether toignore it or report it. Whenever the ACU detects a change inan enabled alarm input, the ACU sends a status message tothe Controller. If the detected change is to an alarm condi-tion, the ACU uses the Major/Minor Alarm mask to deter-mine which alarm unit status LED to turn on.

The ACU also continually scans the 8 control output re-lay positions using the Set Relays message mask. If a dis-crepancy is detected, the ACU turns on the "RELAYERROR" LED in the "ALARM UNIT STATUS" displaygroup and tries to set (or reset) the appropriate relay. If therelay is successfully set (or reset), the discrepancy disap-pears and the "RELAY ERROR" LED is turned off.

The Set Relays message from the Controller contains an8-bit mask containing a 1 in the bit locations representingeach control output relay that should be set (N.O. contactsclosed). The ACU responds by setting (or resetting) eachcontrol relay to agree with the mask.

The Reset message from the Controller causes the ACUto initiate a reset cycle, during which time the ACU per-forms a diagnostic self test. During this self test, the ACUdisables all 32 alarm inputs, leaves all 8 control output re-lays in their existing positions, and turns on all front panelLEDs. If a problem is detected, the ACU sends a message tothe Controller identifying the problem.

Test Unit

The Test Unit (TU) operates by following its own TUsoftware and responding to messages from the Controller.The System Manager has control over the following TU pa-rameters in the Controller’s Active Configuration:

• TU Enabled (default is enabled)• Testcall Enabled (default is enabled)• Background Testcall Interval (the time interval

between test calls - default is 5 minutes - note that aninterval of 0 inhibits test calls)

The Controller communicates with the TU through a19.2 Kbaud asynchronous serial data link. Message bytesare made up of 8 data bits, 1 stop bit, and no parity bit. SeeInterconnection Diagram 7.

The Controller uses the following 4 messages to super-vise the operation of the TU:

• Reset• Status Request• Monitor Control Channel• Testcall State

The TU uses the following 3 messages to report the re-sults of its activities to the Controller:

• Status Response• CC Fail• Call Results

During normal operation, the TU operates in one of thefollowing states:

• Power-Up• Initialization• Set-Up• Monitor• Test Call

Power-Up

The TU is in the Power-Up state when power is first ap-plied or after receiving the Reset message from the Control-ler. In the Power-Up state the Test Unit sets all switchingcircuits to a predetermined known state and performs self-diagnostic checks. When these tasks are finished, the TUsends a Status Response message to the Controller andwaits for a Status Request message from the Controller. In-dividual bits within the Status Response message tell theController

• Presence of Personality• Presence of Error in Memory• Synthesizer Locked• Operational State

If a Status Request message is not received within 10seconds, the TU again sends a Status Response message andagain waits for a Status Request message. This continuesuntil a Status Request message is received from the Control-ler.

Initialization

The TU enters the Initialization state after it has receivedthe first Status Request message from the Controller. Uponentering this state, the TU sends another Status Responsemessage to the Controller and proceeds to the Set-Up state.

Set-Up

The TU is in the Set-Up state when it has finished itslast task and is waiting for a new task.

LBI-38985

26

Monitor

The TU enters the Monitor state when it receives theMonitor Control Channel message from the Controller.Upon entering this state, the TU sets its receiver to the fre-quency of the current Control Channel number (given in theMonitor Control Channel message) and begins monitoringthe outbound Control Channel.

Monitoring the Control Channel is the primary functionof the TU. Control Channel monitoring consists of the fol-lowing chores:

1. Obtaining synchronization with the outbound Con-trol Channel data frames.

2. Decoding the outbound Control Channel data.

3. Verifying the site ID from the outbound ControlChannel data.

If the TU is unable to do any one or more of thesechores, the TU sends the CC Fail message to the Controllerand returns to the Set-Up state. When the Controller re-ceives the CC Fail message, it logs the failure and sends aCC Monitor message with a new Control Channel numberto the TU. When the TU receives the new CC Monitor mes-sage, it returns to the Monitor state and begins monitoringthe new Control Channel.

If the number of failed channels, as a percentage of thetotal channels at the site, reaches 50%, the Controllersearches its activity log to find and disable the piece ofequipment responsible for identifying most of the failuresunder the assumption that it is falsely failing channels. If, insuch a case, the TU is the suspect piece of equipment, theController effectively disables the TU by sending the Resetmessage and no more messages.

Test Call

The TU enters the Test Call state when it receives theTestcall State message from the Controller. Upon enteringthis state, the TU initiates a simulated mobile-originated,channel-request sequence. A normal (successful) sequencecontains the following major steps (a failure at any step inthe sequence causes a jump to step 13):

1. The TU receives the Testcall State message from theController.

2. The TU sets itself to the frequency of the ControlChannel and obtains synchronization with the out-bound Control Channel data frames.

3. The TU sends a request for an individual call andwaits to receive a Working Channel assignment. (Forcall requests, the TU uses a Logical ID of 0 for boththe caller and callee.)

4. The TU receives the Working Channel assignmentand sets itself to the frequency of the assigned Work-ing Channel.

5. The TU receives the high-speed-data channel confir-mation from the Working Channel.

6. The TU sends the high-speed-data key message fol-lowed by low-speed data to the Working Channel.

7. The Working Channel detects the high-speed-datakey message followed by low-speed data from theTU.

8. The TU stops sending low-speed data to the WorkingChannel.

9. When the Working Channel stops receiving the low-speed data from the TU, it starts a 2-second hangtime interval. During this interval, the WorkingChannel transmitts low-speed data, if in a wide-bandsystem. (For 900 MHz systems, the Working Chan-nel transmitts pre-drop alert dotting for the first 0.7second, followed by low-speed data for the remain-ing 1.3 second.)

10. The TU detects and checks the low-speed data in awide-band system; pre-drop alert dotting in a 900MHz system.

11. Approximately 2 seconds after the Working Channelstops receiving the low-speed data from the TU, theWorking Channel transmits the drop-channel mes-sage.

12. The TU receives the drop-channel message.

13. The TU sends the Call Results message to the Con-troller, and returns to the Set-Up state to wait for fur-ther instructions.

If the Working Channel fails the test, the Controller re-moves it from service and logs the failure. If the number offailed channels, as a percentage of the total channels at thesite, reaches the number specified in the Personality PROM(default is 50%), the Controller disables the piece of equip-ment responsible for identifying most of the failures underthe assumption that it is falsely failing channels. If, in sucha case, the TU is the suspect piece of equipment, the Con-

LBI-38985

27

troller effectively disables the TU by sending the Reset mes-sage and no more messages.

TROUBLESHOOTING

This section will be expanded in future revisions. How-ever, for now the following three techniques are especiallyuseful for troubleshooting EDACS Site Controllers:

1. Comparison - Compare all of the readily measurableparameters of a suspect assembly with an identical,known-to-be-good assembly. If a significant differ-

ence is found, then the problem may have been lo-cated.

2. Substitution - Exchange the suspect assembly withan identical, known-to-be-good assembly. If theproblem moves, then the defective component musthave moved also.

3. Divide and Conquer - Divide the equipment in halfand find a symptom of the problem that appears inone half only. Then divide that half in half and repeatuntil you come to a point where the problem existson one side of a replaceable component and not onthe other.

GLOSSARY

Control Channel GETC A Control Channel GETC is a Station GETC that is at the moment connected to a Con-trol Channel.

Controller The 32-port computer housed in the EDACS Site Controller cabinet and responsiblefor directing the Full Featured Trunking at the site.

Controller’s Active Configuration The Controller’s Active Configuration is the Controller’s Initial Configuration modi-fied by the current Site Database from the System Manager.

Controller Application Software The Controller Application Software is the programming instructions read from theController’s 12 Application Software PROMs. It is used by the Controller to controlthe operation of the site.

Controller’s Initial Configuration The Controller’s Initial Configuration is the data read from the Controller’s 2 Personal-ity PROMs. It is usually only present at power up or reset, but will remain the Control-ler’s Active Configuration until System Manager communication is established (ifever).

Controller’s Personality PROMs The Controller’s Personality PROMs contain certain information about the specificsite where the Controller is located, such as Site ID, equipment available at the site,validation tables by feature and priority for each Logical (individual) ID and GroupID, etc.

Downlink GETC A Downlink GETC is the GETC that is connected to the Downlink to the mul-tisite/console switch. The Downlink GETC provides the communications interface be-tween the Downlink and the Controller (or between the Downlink and the FailsoftData Link to the Station GETCs in the event of a Controller failure).

EDACS EDACS is the acronym for Enhanced Digital Access Communications System.

EDACS Site Controller The EDACS Site Controller is all that standard and optional equipment housed in thesingle cabinet that houses the Controller (computer).

Failsoft Data Link The Failsoft Data Link is a daisy-chained data link connecting all the Station GETCsto the Downlink and Redundant Downlink GETCs. The Failsoft Data Link providesthe communications path needed for Failsoft Trunking in the event of a Controller fail-ure, or a combination Controller and Downlink GETC failure.

LBI-38985

28

Printed in U.S.A.

Failsoft Trunking Failsoft Trunking is an EDACS design feature that puts the Control Channel GETC incharge of basic trunking in the event of a Controller failure.

Full Featured Trunking Full Featured Trunking is any trunking under the direction of the Controller utilizingall features of its customer specific configuration (however many or few features theyare).

GETC A GETC is a communications interface with various hardware and software configura-tions. For specific configurations, see: Station GETC Control Channel GETC Working Channel GETCDownlink GETC Redundant Downlink GETC

Redundant Downlink GETC A Redundant Downlink GETC is the GETC that is connected to the Redundant Down-link to the multisite/console switch. The Redundant Downlink GETC provides thecommunications interface between the Redundant Downlink and the Controller (or be-tween the Redundant Downlink and the Failsoft Data Link to the Station GETCs in theevent of a Controller failure).

Site Database The Site Database is the specific information about the site, such as equipment avail-able at the site, validation tables by feature and priority for each Logical (individual)ID and Group ID, etc. maintained by the System Manager.

Station GETC A Station GETC is the GETC that is connected to a MASTR II, IIe, or III repeater sta-tion to make it an EDACS trunk. The Station GETC provides the communications in-terface between the repeater station and the Controller (or between the repeater stationand other Station GETCs in the event of a Controller failure). A Station GETC canmore specifically be called a Control Channel GETC or a Working Channel GETC de-pending upon how it is being used at that moment.

System Manager Modem The System Manager Modem is a telephone channel modem serving as the data inter-face between the Controller and the telephone line used as the data link to the SystemManager (through a second modem at the far end).

Working Channel GETC A Working Channel GETC is a Station GETC that is at the moment connected to aWorking Channel.

LBI-38985

29

Application Assembly

(19D438315, Sh. 1, Rev. 18)

LBI-38985

30

Application Assembly

(19D438315, Sh. 2, Rev. 14)

LBI-38985

31

J1

J10

GETC DATA

J14

GETC DATA

J1

J10J14

19D903880P61

19D903880P61Interconnect Cables (10 Each)

Interconnect Cables (10 Each)19C852313G1

19C852313G1

19C852323G1SERIAL MODULE

J1119D903880P61

Interconnect Cable

Downlink GETC

J7 J100J102

TB10

J102J8 J100

Redundant Downlink GETC

TB10

Port 30 (RIC)

Port 26 (DL)

Port 25

19C852213G1POWER SENSOR

J3

19C336861P1Power Monitor Unit

19D903880P70

J4

J5

J6

19D903880P70

19D903880P70

Interconnect Cable (Chan 10-18)

Interconnect Cable (Chan 19-20)

Interconnect Cable (Chan 1-9)

Interconnect Cable (Tx Comb)19D903880P71

J5

J6

J8

J4

J9 Port 29 (PMU)

Port 1

Port 10

Port 11

Port 20

J1

J2

J7

From Power Sensorsfor Chan 1-10

From Power Sensorsfor Chan 11-20

From Power Sensorsfor Tx Comb

for Chan 1-10

From Station GETCsfor Chan 11-20

From Station GETCs

Interface Panel #1EDACS

19A149302P9Controller

J1

J2

Failsoft Data Linkfor Chan 1-10

Failsoft Data Linkfor Chan 11-20

19C852204G1RIC AUDIO 1-12

Local Telephone Interconnect

19D903880P21

19D903880P21

Interconnect Cable

Interconnect Cable

19D903880P13

19D903880P13

Interconnect Cable

Interconnect Cable

P1

P10

J1

J10

J1

J10

P11

P20

19C852204G1RIC AUDIO 13-20

19D903880P45

19D903880P45

Interconnect Cable (10 Each)

Interconnect Cable (10 Each)

From Station RICsfor Chan 1-10

From Station RICsfor Chan 11-20

19D852204G1PHONE LINE 17-32

J1

J8

Telephone Lines1-16

19D852204G1PHONE LINE 1-16

J1

J8

Telephone Lines17-32

19D903880P81Interconnect Cable

P1---P16 P1---P16

PLA-1PLA-2

Port 31 (LIC)

19D903880P91Interconnect Cable

19D903880P91Interconnect Cable

19D903880P101Interconnect Cable

Interface Panel #2EDACS

19C852204G1DWNLINK DATA

J1

J2J14

Downlinkfrom Multisite Coordinator

344A4656P1Interconnect Cable (8 Each)

344A4656P1Interconnect Cable (8 Each)

J219D903880P101Interconnect Cable

J119D903880P101Interconnect Cable (TAU)

Test and Alarm Unit

Port 28 (ACU)

PORT 27 (TU)

Line

DataPort 0 (SM)

Telephone ModemSystem Manager

19D903880P905Interconnect Cable

Data Linkfrom System Manager

Interconnection Diagram #1AEDACS Site Controller (For Sites with 2 Repeaters Per Cabinet)

LBI-38985

32

J1

J12

GETC DATA

J14

GETC DATA

J1

J8J14

19D903880P61

19D903880P61Interconnect Cables (8 Each)

Interconnect Cables (12 Each)19C852313G1

19C852313G1

19C852323G1SERIAL MODULE

J1119D903880P61

Interconnect Cable

Downlink GETC

J7 J100J102

TB10

J102J8 J100

Redundant Downlink GETC

TB10

Port 30 (RIC)

Port 26 (DL)

Port 25

19C852213G1POWER SENSOR

J3

19C336861P1Power Monitor Unit

19D903880P70

J4

J5

J6

19D903880P70

19D903880P70

Interconnect Cable (Chan 10-18)

Interconnect Cable (Chan 19-20)

Interconnect Cable (Chan 1-9)

Interconnect Cable (Tx Comb)19D903880P71

J5

J6

J8

J4

J9 Port 29 (PMU)

Port 1

Port 12

Port 13

Port 20

J1

J2

J7

From Power Sensorsfor Chan 1-12

From Power Sensorsfor Chan 13-20

From Power Sensorsfor Tx Comb

for Chan 1-12

From Station GETCsfor Chan 13-20

From Station GETCs

Interface Panel #1EDACS

19A149302P9Controller

J1

J2

Failsoft Data Linkfor Chan 1-12

Failsoft Data Linkfor Chan 13-20

19C852204G1RIC AUDIO 1-12

Local Telephone Interconnect

19D903880P21

19D903880P21

Interconnect Cable

Interconnect Cable

19D903880P13

19D903880P13

Interconnect Cable

Interconnect Cable

P1

P12

J1

J12

J1

J8

P13

P20

19C852204G1RIC AUDIO 13-20

19D903880P45

19D903880P45

Interconnect Cable (12 Each)

Interconnect Cable (8 Each)

From Station RICsfor Chan 1-12

From Station RICsfor Chan 13-20

19D852204G1PHONE LINE 17-32

J1

J8

Telephone Lines1-16

19D852204G1PHONE LINE 1-16

J1

J8

Telephone Lines17-32

19D903880P81Interconnect Cable

P1---P16 P1---P16

PLA-1PLA-2

Port 31 (LIC)

19D903880P91Interconnect Cable

19D903880P91Interconnect Cable

19D903880P101Interconnect Cable

Interface Panel #2EDACS

19C852204G1DWNLINK DATA

J1

J2J14

Downlinkfrom Multisite Coordinator

344A4656P1Interconnect Cable (8 Each)

344A4656P1Interconnect Cable (8 Each)

J219D903880P101Interconnect Cable

J119D903880P101Interconnect Cable (TAU)

Test and Alarm Unit

Port 28 (ACU)

PORT 27 (TU)

Line

DataPort 0 (SM)

Telephone ModemSystem Manager

19D903880P905Interconnect Cable

Data Linkfrom System Manager

Interconnection Diagram #1BEDACS Site Controller (For sites With 3 Repeaters Per Cabinet)

LBI-38985

33

Telephone Modem19A149786P2

Controller19A149302P9

123

456

7820

22

123

456

7820

22

SHIELDTX DATARX DATA

RTSCTSDSR

SIGNAL GNDDCDDTR

RING INDICATOR

PORT 0

123

456

7820

22

123

456

7820

22

Interconnect Cable19D903880P905

23

1

4

Telephone Line2-Wire

to System

Manager

MOD-4(F)LINE

DATADB-25(F)

P2DB-25(M)P1

DB-25(M)DB-25 (F)

Interconnection Diagram #2System Manager Data Link

LBI-38985

34

J1

327

RJ11-8(F)

J10RJ11-8(F)

Interconnect Cable19D903880P61

Interconnect Cable19D903880P611

2

J14

19204445

GETC DATAEDACS Interface Module

19C852313G1

327

327

PORT 1

Controller19A149302P9

RJ11-8(F)

RJ11-8(F)

25 PR (F)

327

PORT 10

To J100 ofEach GETCfor Channels

1-10

19C852313G1

EDACS Interface ModuleGETC DATA

J14 J1

P2

P2P1

P1

P1 P2

2726

25 PR (F) RJ11-8(F)

327

122627

J10RJ11-8(F)

327

19204445

P1RJ11-8(F)

P2

RJ11-8(F)PORT 11

PORT 20

19D903880P61

19D903880P61

Interconnect Cable

Interconnect Cable

Each GETCTo J100 of

for Channels11-20

327

327

Interconnection DiagramStation GETC Data Links (For Sites With 2 Repeaters Per Cabinet)

LBI-38985

35

J1

327

RJ11-8(F)

J12RJ11-8(F)

Interconnect Cable19D903880P61

Interconnect Cable19D903880P611

2

J14

23244849

GETC DATAEDACS Interface Module

19C852313G1

327

327

PORT 1

Controller19A149302P9

RJ11-8(F)

RJ11-8(F)

25 PR (F)

327

PORT 12

To J100 ofEach GETCfor Channels

1-12

19C852313G1

EDACS Interface ModuleGETC DATA

J14 J1

P2

P2P1

P1

P1 P2

2726

25 PR (F) RJ11-8(F)

327

122627

J8RJ11-8(F)

327

15164041

P1RJ11-8(F)

P2

RJ11-8(F)PORT 13

PORT 20

19D903880P61

19D903880P61

Interconnect Cable

Interconnect Cable

Each GETCTo J100 of

for Channels13-20

327

327

Interconnection Diagram #3BStation GETC Data Links (For Sites With 3 Repeaters Per Cabinet)

LBI-38985

36

Backup ControllerRedundant Downlink GETC

PORT 25RJ11-8 (F)

3271

PORT 26 (DL)RJ11-8 (F)

3271

J101DB-9 (F)

J101DB-9 (F)

321

321

Downlink GETC

GETC Logic Board

123

J19

Controller

PORT 25RJ11-8 (F)

3271

321

J100DB-9 (F)

PORT 26 (DL)RJ11-8 (F)

3271

321

123

6

46

J100J8

DB-9 (F)

DB-9 (F)J102

321

19D903880P21Interconnect Cable

2435

J7RJ11-6 (F)

321

2435

19D903880P21Interconnect Cable

J102DB-9 (F)

J8RJ11-6 (F)

19C852323G1SERIAL MODULE

EDACS Interface Panel #1

J1DB-15 (F)

J2DB-15 (F)

12910

12910

19852204G1DWNLINK DATA

J1RJ11-6 (F)

TB10

2345

9101112

9867

J6

TB10

9101112

2345

J2RJ11-6 (F)

J1425 PR (F)

126227

3284

DownlinkSyncGND

Sync

Downlink

GNDGND

Tx +Tx -Rx -Rx +

Tx +Tx -Rx -Rx +

TxRx

GND

RxTxGNDGND

TxRx

TxRx

GND

RxTxGNDGND

19D903880P91

19D903880P91Interconnect Cable

Interconnect Cable

TxRx

GND

RxTxGNDGND

RxTxGNDGND

19D903880P91Interconnect Cable

19A149302P9

19A149302P9

19D903880P91Interconnect Cable

19D903880P13Interconnect Cable

19D903880P13Interconnect Cable

Multisite/ConsoleTo

Switch

Station GETCsto

forChannels 11-20

Failsoft Data Link

Data Link

Station GETCsfor

Channels 1-10

toFailsoft Data Link

EDACS Interface Panel #2

29

Interconnection Diagram #4ADownlink And Redundant Downlink Option (For Sites With 2 Repeaters Per Cabinet)

LBI-38985

37

Backup ControllerRedundant Downlink GETC

PORT 25RJ11-8 (F)

3271

PORT 26 (DL)RJ11-8 (F)

3271

J101DB-9 (F)

J101DB-9 (F)

321

321

Downlink GETC

GETC Logic Board

123

J19

Controller

PORT 25RJ11-8 (F)

3271

321

J100DB-9 (F)

PORT 26 (DL)RJ11-8 (F)

3271

321

123

6

46

J100J8

DB-9 (F)

DB-9 (F)J102

321

19D903880P21Interconnect Cable

2435

J7RJ11-6 (F)

321

2435

19D903880P21Interconnect Cable

J102DB-9 (F)

J8RJ11-6 (F)

19C852323G1SERIAL MODULE

EDACS Interface Panel #1

J1DB-15 (F)

J2DB-15 (F)

12910

12910

19852204G1DWNLINK DATA

J1RJ11-6 (F)

TB10

2345

9101112

9867

J6

TB10

9101112

2345

J2RJ11-6 (F)

J1425 PR (F)

126227

3284

DownlinkSyncGND

Sync

Downlink

GNDGND

Tx +Tx -Rx -Rx +

Tx +Tx -Rx -Rx +

TxRx

GND

RxTxGNDGND

TxRx

TxRx

GND

RxTxGNDGND

19D903880P91

19D903880P91Interconnect Cable

Interconnect Cable

TxRx

GND

RxTxGNDGND

RxTxGNDGND

19D903880P91Interconnect Cable

19A149302P9

19A149302P9

19D903880P91Interconnect Cable

19D903880P13Interconnect Cable

19D903880P13Interconnect Cable

Multisite/ConsoleTo

Switch

Station GETCsto

forChannels 13-20

Failsoft Data Link

Data Link

Station GETCsfor

Channels 1-12

toFailsoft Data Link

EDACS Interface Panel #2

29

Interconnection Diagram #4BDownlink And Redundant Downlink Option (For Sites With 3 Repeaters Per Cabinet)

LBI-38985

38

J1

23

RJ11-6(F) Interconnect Cable344A4656P1

126

J14

PHONE LINE 1-16

EDACS Interface Panel #1

19C852204G1

43

J125 PR (F)

P1

P1 P2

2

344A4656P1Interconnect Cable

45

Local Telephone Interconnect

J227

P343

TRTR

Line #1

Line #2

1792

1237

Port 31 (LIC)J34

S

RJ11-8 (F)

RJ11-6 (F)

RJ11-6 (F)

19D903880P81Interconnect CableDB-9 (F)

ShieldRx DataTx DataSignal GNDConnector Shield

J15RJ11-6 (F)

J8RJ11-6 (F)

2345

34

P2

P3

J16RJ11-6 (F)

43

PLA #1

15401641

TRTR

Line #15

Line #16

19C852204G1PHONE LINE 17-20

J1425 PR (F)

J1RJ11-6 (F)

J1RJ11-6 (F)

43

2345 J2

RJ11-6 (F)

43

P1 P2

P3

344A4656P1Interconnect Cable

126227

TRTR

Line #17

Line #18

PLA #2

J15RJ11-6 (F)

43

J16RJ11-6 (F)

43

2345

15401641

J8RJ11-6 (F)

TRTR

Line 31

Line 32

344A4656P1Interconnect Cable

P1 P2

P3

19C852204G1RIC AUDIO 1-12

13

23

126

13

2

J1425 PR (F)

P11x3 Molex (F)

P101x3 Molex (F)

J1

J10

RJ11-6 (F)

RJ11-6 (F)

Chan #1

Chan #103

1944

19C852204G1RIC AUDIO 13-20

P111x3 Molex (F)

J1425 PR (F)

J1RJ11-6 (F)

13

23

126

P201x3 Molex (F)

J10RJ11-6 (F)

13

23

1944

Chan #11

Chan #20

19D903880P45Interconnect Cable

19D903880P45Interconnect Cable

19D903880P45Interconnect Cable

19D903880P45Interconnect Cable

P1

P1

P1 P2

P2

P2

P2P1

19C852323G1SERIAL MODULE

3411

237

3411

237S

Port 30 (RIC)RJ11-8 (F)

Rx DataTx DataSignal GNDConnector Shield

P2P1 19D903880P61

Interconnect CableJ11

RJ11-8 (F)J1DB-15 (F)

J2DB-15 (F)

to RICs forChannels 1-10

Data Link

Data linkto RICs for

Channels 11-20

to RICs forAudio Links

Channels 11-20

to RICs forAudio Links

Channels 1-10

toAudio Links

ExternalTelephone Lines

19A149302P9Controller

P1 P2

Interconnection Diagram #5ALocal Telephone Interconnect Option (For Sites With 2 Repeaters Per Cabinet)

LBI-38985

39

J1

23

RJ11-6(F) Interconnect Cable344A4656P1

126

J14

PHONE LINE 1-16

EDACS Interface Panel #1

19C852204G1

43

J125 PR (F)

P1

P1 P2

2

344A4656P1Interconnect Cable

45

Local Telephone Interconnect

J227

P343

TRTR

Line #1

Line #2

1792

1237

Port 31 (LIC)J34

S

RJ11-8 (F)

RJ11-6 (F)

RJ11-6 (F)

19D903880P81Interconnect CableDB-9 (F)

ShieldRx DataTx DataSignal GNDConnector Shield

J15RJ11-6 (F)

J8RJ11-6 (F)

2345

34

P2

P3

J16RJ11-6 (F)

43

PLA #1

15401641

TRTR

Line #15

Line #16

19C852204G1PHONE LINE 17-20

J1425 PR (F)

J1RJ11-6 (F)

J1RJ11-6 (F)

43

2345 J2

RJ11-6 (F)

43

P1 P2

P3

344A4656P1Interconnect Cable

126227

TRTR

Line #17

Line #18

PLA #2

J15RJ11-6 (F)

43

J16RJ11-6 (F)

43

2345

15401641

J8RJ11-6 (F)

TRTR

Line 31

Line 32

344A4656P1Interconnect Cable

P1 P2

P3

19C852204G1RIC AUDIO 1-12

13

23

126

13

2

J1425 PR (F)

P11x3 Molex (F)

P121x3 Molex (F)

J1

J12

RJ11-6 (F)

RJ11-6 (F)

Chan #1

Chan #123

2348

19C852204G1RIC AUDIO 13-20

P131x3 Molex (F)

J1425 PR (F)

J1RJ11-6 (F)

13

23

126

P201x3 Molex (F)

J8RJ11-6 (F)

13

23

1540

Chan #13

Chan #20

19D903880P45Interconnect Cable

19D903880P45Interconnect Cable

19D903880P45Interconnect Cable

19D903880P45Interconnect Cable

P1

P1

P1 P2

P2

P2

P2P1

19C852323G1SERIAL MODULE

3411

237

3411

237S

Port 30 (RIC)RJ11-8 (F)

Rx DataTx DataSignal GNDConnector Shield

P2P1 19D903880P61

Interconnect CableJ11

RJ11-8 (F)J1DB-15 (F)

J2DB-15 (F)

to RICs forChannels 1-12

Data Link

Data linkto RICs for

Channels 13-20

to RICs forAudio Links

Channels 13-20

to RICs forAudio Links

Channels 1-12

toAudio Links

ExternalTelephone Lines

19A149302P9Controller

P1 P2

Interconnection Diagram #5BLocal Telephone Interconnect Option (For Sites With 3 Repeaters Per Cabinet)

LBI-38985

40

19D149302P9Controller

19C336861P1Power Monitor Unit

Interface PanelEDACS

19C852213G1"POWER SENSOR"

126

120

120221

19D903880P70Interconnect Cable

Xmtr #1

Xmtr #2

1742

328

1736

322

17361837

3

422

23

Xmtr #9

P3P2HIGNDHIGNDHIGNDHIGND

HIGNDHIGND

J5DB-37 (M)

J1 J3DB-37 (F)25 PR (F)

1944

120

322

524

120221322423524625

19D903880P70Interconnect Cable

J6DB-37 (M)

J4DB-37 (F)

S Connector ShieldXmtr #10

Xmtr #11

Xmtr #12

J225 PR (F)

HIGNDHIGNDHIGNDHIGNDHIGNDHIGND

1540

1736

17361837S

Xmtr #18

HI

GNDHIGND

Connector Shield

P2P3

114215316417S

J7DB-25 (M)19D903880P72

Interconnect CableP2 P3

J5DB-9 (F)

16

38

1742

1944

Xmtr #19

Xmtr #20

HIGNDHIGNDHIGNDHIGNDConnector Shield

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Reflected

Forward

Reflected

Forward

19D903880P71Interconnect Cable

16

27

38

49

16

27

38

49

19

210

311

412

HIGND

HIGND

HIGND

HIGND

Forward

Reflected

Forward

Reflected

Ant #1

Ant #1

Ant #2

Ant #2

J6DB-9 (F)

J7DB-9 (F)

J4DB-15 (M)

1237S

132745620

19D903880P101Interconnect Cable

Port 29 (PMU)RJ11-8 (F)

J8DB-25 (F) P2P1

ShieldTx DataRx DataSignal GNDConnector Shield

Jumper in P1

Jumper in P1Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

513

614

715

816

S

P2P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

HIGND

HIGND

HIGND

HIGND

Connector Shield

Forward

Reflected

Forward

Reflected

To Power Sensors for Antennas 1-2.

2146

2348

726827

530

Xmtr #13726

HIGNDHIGND

Forward

ReflectedJumper in P3

116

328

Xmtr #11

Xmtr #12

Remove Redundant Jumpers.Not Used in this Application.

See Installation Section in Text.

Remove Jumpers for Circuits Used.

To Power Sensors for Xmtrs 11-20.

See Installation Section in Text.

Remove Jumpers for Circuits Used.To Power Sensors for Xmtrs 1-10.

See Installation Section in Text.

This Is Not a Typo.

Add Jumpers for Unused Circuits.See Installation Section in Text.

Interconnection Diagram #6APower Monitor Option (For Sites With 2 Repeaters Per Cabinet)

LBI-38985

41

19D149302P9Controller

19C336861P1Power Monitor Unit

Interface PanelEDACS

19C852213G1"POWER SENSOR"

126

120

120221

19D903880P70Interconnect Cable

Xmtr #1

Xmtr #2

1742

328

1736

322

17361837

3

422

23

Xmtr #9

P3P2HIGNDHIGNDHIGNDHIGND

HIGNDHIGND

J5DB-37 (M)

J1 J3DB-37 (F)25 PR (F)

19

44

120

3

22

524

120221322423524625

19D903880P70Interconnect Cable

J6DB-37 (M)

J4DB-37 (F)

S Connector ShieldXmtr #10

Xmtr #11

Xmtr #12

J225 PR (F)

HIGNDHIGNDHIGNDHIGNDHIGNDHIGND

1540

1736

17361837S

Xmtr #18

HI

GNDHIGND

Connector Shield

P2P3

114215316417S

J7DB-25 (M)19D903880P72

Interconnect CableP2 P3

J5DB-9 (F)

1

6

38

17

42

1944

Xmtr #19

Xmtr #20

HIGNDHIGNDHIGNDHIGNDConnector Shield

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Forward

Reflected

Reflected

Forward

Reflected

Forward

19D903880P71Interconnect Cable

16

27

38

49

16

27

38

49

19

210

311

412

HIGND

HIGND

HIGND

HIGND

Forward

Reflected

Forward

Reflected

Ant #1

Ant #1

Ant #2

Ant #2

J6DB-9 (F)

J7DB-9 (F)

J4DB-15 (M)

1237S

132745620

19D903880P101Interconnect Cable

Port 29 (PMU)RJ11-8 (F)

J8DB-25 (F) P2P1

ShieldTx DataRx DataSignal GNDConnector Shield

Jumper in P1

Jumper in P1Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

513

614

715

816

S

P2P3

Jumper in P3

Jumper in P3

Jumper in P3

Jumper in P3

HIGND

HIGND

HIGND

HIGND

Connector Shield

Forward

Reflected

Forward

Reflected

To Power Sensors for Antennas 1-2.

2146

2348

726827

530

Xmtr #13726

HIGNDHIGND

Forward

ReflectedJumper in P3

116

328

Xmtr #11

Xmtr #12

Remove Redundant Jumpers.Not Used in this Application.

See Installation Section in Text.

Remove Jumpers for Circuits Used.To Power Sensors for Xmtrs 13-20.

See Installation Section in Text.

Remove Jumpers for Circuits Used.To Power Sensors for Xmtrs 1-12.

See Installation Section in Text.

This Is Not a Typo.

Add Jumpers for Unused Circuits.See Installation Section in Text.

Interconnection Diagram #6BPower Monitor Option (For Sites With 3 Repeaters Per Cabinet)

LBI-38985

42

19A149302P9Controller

19D901365G2Alarm and Control Unit

19D901331G3Interface BoardAlarm/Control

19C851141G3Panel w HarnessRear Bulkhead

Port 28 (ACU)RJ11-8 (F)

J425 PR (F)

J1DB-25 (F)

1237S

1327

19D903880P101Interconnect Cable

P1 P2

TXDRXDGND

ShieldTx DataRx DataSignal GNDConnector Shield

Port 27 (TU)RJ11-8 (F)

J2DB-25 (F)

1237S

1327

19D903880P101Interconnect Cable

P1 P2

TXDRXDGND

ShieldTx DataRx DataSignal GNDConnector Shield

Port 28 (ACU)RJ11-8 (F)

J3DB-25 (F)

1237S

1327

19D903880P101Interconnect Cable

P1 P2

TXDRXDGND

ShieldTx DataRx DataSignal GNDConnector Shield

Port 27 (TU)RJ11-8 (F)

J4DB-25 (F)

1237S

1327

19D903880P101Interconnect Cable

P1 P2

TXDRXDGND

ShieldTx DataRx DataSignal GNDConnector Shield

19A149302P9Backup Controller

26127

A1 +A1 CA1 G

23

24

A16 +A16 CA16 G

2550

+13.8 VDCPWR GND

J525 PR (F)

26127

A17 +A17 CA17 G

23

24

A32 +A32 CA32 G

2550 PWR GND

+13.8 VDC

49

49

J325 PR (F)

26127

113712

3813391440154116

C1 NOC1 COMC1 NC

C8 NOC8 COMC8 NC

+5 VDC+5 VDC5V GND5V GND+13.8 VDC+13.8 VDC13.8V GND13.8V GND

Alarm SensorsTo

forAlarms C1-C16

Alarm SensorsTo

forAlarms C17-C32

Control DevicesTo

forControls C1-C8

Interconnection Diagram #7Test And Alarm Unit Option

LBI-38985

43

Controller6-Outlet

Power Strip

2-OutletPower Strip

Cabinet Fan Assembly

Modem

UPS

13.8 Vdc P.S.

Controller 5-OutletPower Strip

Cabinet Fan Assembly

Modem

UPS

13.8 Vdc P.S.

120 V, 60 Hz Configuration 230 V, 50 Hz Configuration

19A149978P2

19C320895G12 19C320895G15

19B226209G1

19B226350G2

19A149978P1

349A9903P1 349A9903P2

19B801967P1

344A4282P1

Power Cord

19A149786P2(Includes

DC Power Cordwith 120 VacP.S. at End)

Modem

(IncludesPower Cordwith Plug)

(IncludesPower Cordwith Plug)

13.8 Vdc P.S.

(IncludesPower Cordwith Plug)

(IncludesPower Cordwith Plug)

(IncludesPower Cordwith Plug)

(IncludesPower Cordwith Plug)

19A149302P9Controller

(Includes Power Cordwith Plug)

(Includes Power Cordwith Plug)

(Use SubstitutePower Cord)

19A149302P9Controller

Substitute

19A149786P3(Includes

DC Power Cordwith 230 VacP.S. at End)

Modem

13.8 Vdc P.S.

(IncludesPower Cordwith Plug)

(IncludesPower Cordwith Plug)

19A149575P58

AC Power Cord

RecepticlesAccept

NEMA 515Plugs

UPS

RecepticlesAccept

CEE 7/7Plugs

UPS

Interconnection Diagram #8AC Power (Rear View)

LBI-38985

44

12 VDC

12

12

TB10 - 1

TB10 - 1

P33

#16 R

#18 BK

#18 BK

#18 R

#18 R

#16 BK

R

BK

R BK

P5/J5

J801

13.8 VDC Power Supply

Alarm and Control Unit

Test Unit

}to TU Mobile

_+

F801B

+ _

+ _ Local Telephone Interconnect

Power Monitor Unit

19A149357G2 Cable

Part of 19D901864G2 Mobile Control Cable for RANGRor 19B801358P18 DC Power Cable for MDX

1 +2 GND

Downlink GETC

Redundant Downlink GETC

#18 R

#18 BK

#16 R

#16 BK

#18 BK#18 R

J33

19C336861P1

19C337482P1-P8

19D901868G3

19D901868G3

19D901365G2

Modified RANGR or MDX Mobile

19A149978P1 for 120 V, 60 Hz19A149978P2 for 230 V, 50 Hz

123

47

1 1 23 4

Part of Local Telephone Interconnect

Interconnection Diagram #9DC Power (Rear View)

LBI-38985

45