SERVICE MANUAL HORIZON II MICRO

68P02903W31-C

SE

RV

ICE

MA

NU

AL

HO

RIZO

N II M

ICR

O

68P02903W31-C

Service Manual: Horizon II micro

68P02903W31-C Aug 2007© 2005 - 2007 Motorola, Inc. All Rights Reserved

Accuracy

While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes noliability resulting from any inaccuracies or omissions in this document, or from use of the information obtainedherein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,function, or design, and reserves the right to revise this document and to make changes from time to time in contenthereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liabilityarising out of the application or use of any product, software, or circuit described herein; neither does it conveylicense under its patent rights or the rights of others. It is possible that this publication may contain references to, orinformation about Motorola products (machines and programs), programming, or services that are not announcedin your country. Such references or information must not be construed to mean that Motorola intends to announcesuch Motorola products, programming, or services in your country.

Copyrights

This document, Motorola products, and 3rd Party Software products described in this document may includeor describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductormemories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, andother 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive rightto copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in theMotorola products described in this document may not be copied, reproduced, reverse engineered, distributed,merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchaseof Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, anylicense under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of aproduct.

A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of thisdocument.

Restrictions

Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No partof the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, ortranslated into any language or computer language, in any form or by any means, without prior written permissionof Motorola, Inc.

License Agreements

The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by expresslicense agreement only and may be used only in accordance with the terms of such an agreement.

High Risk Materials

Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOTdesigned, manufactured, or intended for use as on-line control equipment in the following hazardous environmentsrequiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft CommunicationSystems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.

Trademarks

Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or servicenames are the property of their respective owners.

The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copiesof the Declaration of Compliance and installation information in accordance with the requirements of EN50385 canbe obtained from the local Motorola representative or by contacting the Customer Network Resolution Center(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select CustomerNetwork Resolution Center contact information. Alternatively if you do not have access to CNRC or theinternet, contact the Local Motorola Office.

Aug 2007

Tableof

Contents

Contents■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Service Manual: Horizon II microRevision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Resolution of Service Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Incorporation of Change Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524–hour support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Questions and comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Security advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Electromagnetic energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Caring for the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9In EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9In non-EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Ordering documents and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Document banner definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1: Introduction to the Horizon II microFinding information in this manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Equipment introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Names and acronyms for main enclosure equipment . . . . . . . . . . . . . . . . . . . . 1-4Horizon II BTS comparison with Horizonmacro . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Compatibility with Horizonmacro and M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . 1-8Comparison of Horizon II equipment with Horizonmacro . . . . . . . . . . . . . . . . . . 1-10

Introduction to Horizon II micro specifications. . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Approval and safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Software requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Access control requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Horizon II micro physical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

68P02903W31-C i

Aug 2007

Contents

Enclosure dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Torque values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Environmental limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Structural considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Layout plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Horizon II micro electrical and RF specifications . . . . . . . . . . . . . . . . . . . . . . . . 1-17Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Battery backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18RF power output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Frequency capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21BSC connectivity options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22

Chapter 2: Horizon II micro structureHorizon II micro enclosure structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Overview of structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Filled enclosure view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4External solar cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Horizon II micro internal structure and harnesses . . . . . . . . . . . . . . . . . . . . . . . . 2-6Internal structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Midplane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Internal harness function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Secondary cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Interface panel and cable entry box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Interface panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Cable entry box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Line interface module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Enclosure temperature control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Enclosure and equipment temperature control . . . . . . . . . . . . . . . . . . . . . . . 2-17Temperature sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Enclosure restart after shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

External fan module description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20External fan operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20View of an external fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Internal fan unit description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22View of an internal fan unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Internal fan operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Enclosure doors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Door view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Mounting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Pole mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Chapter 3: Power distributionHorizon II micro power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Location of power modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Power supply unit (PSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

PSU location and redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3PSU module view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4PSU alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5PSU LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5PSU supply protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Horizon II mini battery module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7The Horizon II mini battery module features. . . . . . . . . . . . . . . . . . . . . . . . . 3-9The Horizon II mini battery module front panel LED. . . . . . . . . . . . . . . . . . . . . 3-10

ii 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Contents

Chapter 4: RF modulesRF equipment description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

RF general information and VSWR monitoring function . . . . . . . . . . . . . . . . . . . 4-2RF specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Receive (Rx) RF hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Transmit (Tx) RF hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Rx/Tx single antenna duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

RF overview and antenna VSWR monitoring function . . . . . . . . . . . . . . . . . . . . . . 4-5RF main components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Antenna VSWR monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6RF loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6RF functional diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Compact transceiver unit 2 (CTU2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Overview of the CTU2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8CTU2 internal boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9View of a CTU2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10CTU2 front panel detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11CTU2 Rx function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14CTU2 interface function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14CTU2 frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Compact Transceiver Unit 2 Double Density Edge (CTU2D) . . . . . . . . . . . . . . . . . . . 4-16Overview of the CTU2D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16CTU2D internal boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17View of a CTU2D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18CTU2D front panel detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19CTU2D Rx function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22CTU2D interface function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23CTU2D frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Mini-SURF module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Mini-SURF module view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26Mini-SURF functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27Mini-SURF to CTU2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

Tx blocks overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30Tx block connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30

Duplexer (DUP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31Duplexer Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31DUP view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32DUP functional diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33DUP connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

PGSM duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34Duplexer Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34PGSM duplexer view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34PGSM duplexer functional diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37PGSM duplexer connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37

Chapter 5: Digital modulesOverview of digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Digital module locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Communication between the HIISC and transceivers . . . . . . . . . . . . . . . . . . . . 5-4

Horizon II site controller (HIISC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6HIISC module view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Link to redundant HIISC (Horizon II macro only) . . . . . . . . . . . . . . . . . . . . . . 5-7Front panel interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Front panel switches and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8PIX output interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

68P02903W31-C iii

Aug 2007

Contents

SDRAM, flash EPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Code loading functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10HIISC internal architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11RSL configuration and control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Integral HIISC XMUX functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

XMUX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16XMUX module view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16XMUX functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Site expansion board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19View of site expansion board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Alarm module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21View of alarm module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Alarm module functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Alarm module replacement - effect on alarms . . . . . . . . . . . . . . . . . . . . . . . . 5-23Alarm collection from expansion cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Alarm module display presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

Chapter 6: Routine maintenanceRoutine maintenance overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Reporting faulty devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Routine maintenance intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Cleaning agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Torque values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Solar cover and door operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Visiting the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Before leaving for the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Arrival at site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Leaving site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Waste material on site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Rural sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7On site safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Weather conditions affecting unpacking, installation or maintenance . . . . . . . . . . . . . . 6-9Weather conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Maintenance cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

6-monthly maintenance procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Cleaning air inlets and exhaust grilles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

12-monthly maintenance procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Checking normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Annual check of the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

24-monthly maintenance procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Mechanical inspection of enclosure and doors . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Chapter 7: FRU replacement proceduresOverview of FRU replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

FRU list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Torque values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3FRU enclosure locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Non-FRU components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6List of non-FRU components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Procedure for replacing non-FRU components . . . . . . . . . . . . . . . . . . . . . . . . 7-6Chassis component attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Replacing an enclosure door . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Door replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Replacing fan units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

iv 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Contents

Fan test push button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9View of the internal fan unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Replacing an internal fan unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11View of the external fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Replacing an external fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Replacing a power supply unit (PSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15View of the PSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15Replacing a PSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Replacing a battery module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Replacing a CTU2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18View of a CTU2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19CTU2 replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20CINDY commissioning tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

CTU2 calibration data exchange scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25Commands used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

Preserving CTU2 calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26Calibration data overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26

Enabling the preserve CTU2 calibration data feature . . . . . . . . . . . . . . . . . . . . . . 7-30Enabling the preserve feature at the OMC-R. . . . . . . . . . . . . . . . . . . . . . . . . 7-30Enabling the preserve feature at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31

CTU2 calibration data exchange procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32Preserve CTU2 calibration data procedure . . . . . . . . . . . . . . . . . . . . . . . . . 7-32CTU2 calibration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32CTU2 recalibration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35

Calibrating CTU2 bay level offset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39Commands used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Preparation for Rx bay level calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41Rx bay level calibration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43Test frequency tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49Site restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51

Replacing a Mini-SURF module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56Replacement procedures for a Mini-SURF . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56View of the Mini-SURF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58

Replacing a Tx block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59Location of the Tx blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59Tx block connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61Replacing a DUP or PGSM duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61

Digital module replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66Location of digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66Replacing digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67

Calibrating the HIISC (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70Introduction to HIISC (GCLK) calibration . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70When to calibrate the GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-71Preparation for GCLK calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-71GCLK calibration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73

Line interface unit board replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77View of BIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78View of T43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79Replacing a line interface unit board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80

Replacing a heat sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82Heat sensor replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82

68P02903W31-C v

Aug 2007

Contents

Chapter 8: Site verication proceduresIntroduction to Horizon II BTS verification procedures . . . . . . . . . . . . . . . . . . . . . 8-2

CINDY commissioning tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Site verification test equipment, leads, and plugs . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Test leads required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

VSWR checks on Horizon II micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7CTU2 VSWR and cell site offset information . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

VSWR checks on Horizon II micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Commands used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Test stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11Preparation for output power calibration and VSWR check . . . . . . . . . . . . . . . . . 8-11

Normal CTU2 VSWR and cell site power (CSPWR) calibration . . . . . . . . . . . . . . . . . . 8-15Automatic VSWR test procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15Manual VSWR test procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18Tx output power calibration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21Tx enclosure channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . 8-27

Checking the database equipage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28Commands used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28Test procedures for checking the database equipage . . . . . . . . . . . . . . . . . . . . 8-28

Checking the backhaul link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Commands used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Test procedures for checking the backhaul link . . . . . . . . . . . . . . . . . . . . . . . 8-31

Checking PIX connections and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Commands used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Test procedures for checking PIX connections and alarms . . . . . . . . . . . . . . . . . . 8-35

Site restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Commands used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Site restoration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

Chapter 9: Parts information for Horizon II microHorizon II micro parts list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

FRU items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Horizon II micro FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Horizon II micro enclosure left accessible components . . . . . . . . . . . . . . . . . . . 9-4Horizon II micro enclosure right accessible components. . . . . . . . . . . . . . . . . . . 9-5Spares tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

vi 68P02903W31-C

Aug 2007

Listof

Figures

List of Figures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Figure 1-1: Horizon II micro, with solar cover . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Figure 1-2: Enclosure internal views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Figure 1-3: Functional diagram of Horizon II micro . . . . . . . . . . . . . . . . . . . . . . . 1-7Figure 1-4: Example of a mixed BTS site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Figure 1-5: Horizon II micro site layout plan . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Figure 2-1: External view of a Horizon II micro enclosure, without the solar cover fitted . . . . 2-2Figure 2-2: Left side view of Horizon II micro enclosure with the doors removed . . . . . . . . 2-3Figure 2-3: Enclosure showing main components . . . . . . . . . . . . . . . . . . . . . . . . 2-4Figure 2-4: External solar cover view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Figure 2-5: Front view of empty enclosure showing internal structure and midplanecomponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Figure 2-6: CTU2 connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Figure 2-7: Secondary cage with major features labelled . . . . . . . . . . . . . . . . . . . . 2-11Figure 2-8: Interface panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Figure 2-9: Cable entry box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Figure 2-10: BIB/BIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Figure 2-11: T43/CIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Figure 2-12: Cross sectional view of air flow in the enclosure . . . . . . . . . . . . . . . . . . 2-18Figure 2-13: External fan module power rating labels . . . . . . . . . . . . . . . . . . . . . . 2-20Figure 2-14: View of an external fan module. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Figure 2-15: View of an internal fan unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Figure 2-16: Door view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Figure 2-17: Mounting bracket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Figure 2-18: Pole-mounting bracket adapter kit . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Figure 3-1: Location of power modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Figure 3-2: PSU module view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Figure 3-3: The Horizon II mini battery module . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Figure 4-1: RF functional diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Figure 4-2: View of a CTU2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Figure 4-3: CTU2 front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Figure 4-4: View of a CTU2D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Figure 4-5: CTU2D front panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19Figure 4-6: Mini-SURF module with features identified . . . . . . . . . . . . . . . . . . . . . 4-26Figure 4-7: Mini-SURF functional diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27Figure 4-8: Mini-SURF to CTU2 connections (2 diversity) . . . . . . . . . . . . . . . . . . . . 4-29Figure 4-9: Duplexer with connectors identified . . . . . . . . . . . . . . . . . . . . . . . . . 4-32Figure 4-10: DUP functional diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33Figure 4-11: Motorola PGSM duplexer with connectors identified . . . . . . . . . . . . . . . . 4-35Figure 4-12: Filtronic PGSM duplexer with connectors identified . . . . . . . . . . . . . . . . 4-36Figure 4-13: PGSM duplexer functional diagram . . . . . . . . . . . . . . . . . . . . . . . . 4-37Figure 5-1: Digital module locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Figure 5-2: HIISC to transceiver communication path . . . . . . . . . . . . . . . . . . . . . 5-4Figure 5-3: View of the HIISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Figure 5-4: HIISC internal architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Figure 5-5: View of the XMUX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

68P02903W31-C vii

Aug 2007

List of Figures

Figure 5-6: XMUX interconnection block diagram . . . . . . . . . . . . . . . . . . . . . . . . 5-18Figure 5-7: Site expansion board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Figure 5-8: Alarm module view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Figure 7-1: FRU enclosure locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Figure 7-2: CTU2 handle – heat warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Figure 7-3: View of door . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Figure 7-4: Fan test push button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Figure 7-5: View of the internal fan unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Figure 7-6: View of the external fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Figure 7-7: External fan module electrical connector . . . . . . . . . . . . . . . . . . . . . . 7-14Figure 7-8: View of the PSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15Figure 7-9: CTU2 view with key features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Figure 7-10: Mini-SURF, showing connector details . . . . . . . . . . . . . . . . . . . . . . . 7-58Figure 7-11: Location of DUP/PGSM duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60Figure 7-12: View of the duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62Figure 7-13: Diagram of digital module locations . . . . . . . . . . . . . . . . . . . . . . . . 7-66Figure 7-14: Horizon II macro GCLK calibration cable connections . . . . . . . . . . . . . . . 7-72Figure 7-15: BIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78Figure 7-16: T43 board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79Figure 8-1: Horizon II 9-way to 9-way hardware verification cable connections . . . . . . . . . 8-5Figure 8-2: Horizon II 9-way to 9-way CTU2 cable connections . . . . . . . . . . . . . . . . . 8-5Figure 9-1: Horizon II micro enclosure components accessible from the left side . . . . . . . . 9-4Figure 9-2: Horizon II micro enclosure components accessible from the right side . . . . . . . 9-5

viii 68P02903W31-C

Aug 2007

Listof

Tables

List of Tables■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Table 1-1: Comparison of Horizon II micro with Horizonmacro . . . . . . . . . . . . . . . . . 1-10Table 1-2: Horizon II micro specification compliance . . . . . . . . . . . . . . . . . . . . . . 1-12Table 1-3: Enclosure dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Table 1-4: Enclosure weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Table 1-5: Torque values for all enclosure screws/bolts and RF connectors . . . . . . . . . . . 1-14Table 1-6: Environmental limits for operation and storage . . . . . . . . . . . . . . . . . . . . 1-14Table 1-7: Horizon II micro external power supply requirements . . . . . . . . . . . . . . . . 1-17Table 1-8: Horizon II micro power consumption details . . . . . . . . . . . . . . . . . . . . . 1-17Table 1-9: CTU2 RF standard power output option, installed in Horizon II micro enclosure withno external combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Table 1-10: CTU2 RF high power output option, installed in Horizon II micro enclosure with noexternal combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Table 1-11: Rx sensitivity performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Table 1-12: Horizon II micro frequency band characteristics . . . . . . . . . . . . . . . . . . 1-21Table 2-1: Temperature thresholds for CTU2 shutdown responses . . . . . . . . . . . . . . . . 2-18Table 3-1: Indications of the front panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Table 3-2: The Horizon II mini battery module front panel LED indications . . . . . . . . . . . 3-10Table 4-1: CTU2 front panel connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Table 4-2: CTU2 front panel status indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Table 4-3: CTU2D front panel connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Table 4-4: CTU2D front panel status indicators . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Table 4-5: Tx block connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30Table 5-1: HIISC front panel LED indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Table 5-2: Alarm module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Table 6-1: Horizon II mini routine maintenance schedule . . . . . . . . . . . . . . . . . . . . 6-3Table 6-2: Torque values for all equipment screws/bolts and RF connectors . . . . . . . . . . . 6-4Table 6-3: Normal LED indication of cabinet modules . . . . . . . . . . . . . . . . . . . . . . 6-13Table 7-1: Torque values for all equipment screws/bolts and RF connectors . . . . . . . . . . . 7-3Table 7-2: CTU2 calibration scenarios and procedures. . . . . . . . . . . . . . . . . . . . . . 7-24Table 7-3: CTU2 calibration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25Table 7-4: MMI commands for CTU2 Rx bay level offset calibration . . . . . . . . . . . . . . . 7-40Table 7-5: EGSM900 and PGSM900 test frequencies . . . . . . . . . . . . . . . . . . . . . . 7-49Table 7-6: GSM1800 test frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50Table 7-7: Connectors for each type of Tx block . . . . . . . . . . . . . . . . . . . . . . . . . 7-61Table 8-1: Hardware verification test equipment. . . . . . . . . . . . . . . . . . . . . . . . . 8-3Table 8-2: PIX test plug pin connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Table 8-3: Tx output power during tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Table 8-4: Tx output power during tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Table 8-5: VSWR and power calibration commands. . . . . . . . . . . . . . . . . . . . . . . . 8-10Table 8-6: VSWR and power calibration site restoration commands. . . . . . . . . . . . . . . . 8-37Table 9-1: Horizon II micro structural and thermal control spares . . . . . . . . . . . . . . . . 9-6Table 9-2: Horizon II micro power distribution spares . . . . . . . . . . . . . . . . . . . . . . 9-7Table 9-3: Horizon II micro RF component spares . . . . . . . . . . . . . . . . . . . . . . . . 9-7Table 9-4: Horizon II micro digital module spares . . . . . . . . . . . . . . . . . . . . . . . . 9-8Table 9-5: Expansion enclosure fibre optic cable pairs . . . . . . . . . . . . . . . . . . . . . . 9-8

68P02903W31-C ix

Aug 2007

List of Tables

Table 9-6: Miscellaneous spares for Horizon II micro . . . . . . . . . . . . . . . . . . . . . . 9-8

x 68P02903W31-C

Aug 2007

AboutThisManual

Service Manual: Horizon II micro■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

What is covered in this manual?

The manual contains technical descriptions of the hardware elements and repair procedures,and parts lists for the Horizon II micro BTS. The objectives of this manual are to help the reader:

• Gain an overview of the equipment and interconnection of components.

• Understand the function and operation of all components.

• Recognize configurations and equivalent module functions to previous equipment designs(M-Cell6, Horizon macro, and other Horizon II BTSs).

• Understand how to inspect, maintain, and repair the equipment.

• Be aware of the warnings (potential for harm to people) and cautions (potential for harm toequipment) to be observed when working on the equipment.

• Have access to a clear ready reference for all dedicated information in one manual.

Related information

Refer to Installation and configuration, Horizon II micro (68P02903W32) forinstallation and commissioning information for this equipment.

68P02903W31-C 1

Aug 2007

Revision history

Revision history■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following sections show the revision status of this document.

Version information

The following table lists the supported versions of this manual in order of issue:

Issue Date of issue Remarks

A Jun 2005 Original issue

B Jun 2006 Updated to incorporate hardware changes.

C Aug 2007 Final

Resolution of Service Requests

The following Service Requests are resolved in this document:

ServiceRequest CMBPNumber Remarks

MOTCM00892872 N/A Update to the flashing green LED status description.

MOTCM00925218 N/A Updates to reflect that in GSR9 the coexistance ofmicro and macro cells at a site has been removed.

Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:

CN Date CN Number Title

2 68P02903W31-C

Aug 2007

General information

General information■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Purpose

Motorola cellular communications documents are intended to instruct and assist personnel inthe operation, installation and maintenance of the Motorola cellular infrastructure equipmentand ancillary devices. It is recommended that all personnel engaged in such activities beproperly trained by Motorola.

Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss orreduction in system performance arising directly or indirectly out of the failure of the customer,or anyone acting on the customer's behalf, to abide by the instructions, system parameters,or recommendations made in this document.

These documents are not intended to replace the system and equipment training offered byMotorola. They can be used to supplement and enhance the knowledge gained through suchtraining.

If this document was obtained when attending a Motorola training course, it willnot be updated or amended by Motorola. It is intended for TRAINING PURPOSESONLY. If it was supplied under normal operational circumstances, to support a majorsoftware release, then corrections are supplied automatically by Motorola and postedon the Motorola customer website.

Cross references

References made to external publications are shown in italics. Other cross references,emphasized in blue text in electronic versions, are active links to the references.

This document is divided into numbered chapters that are divided into sections. Sections arenot numbered, but are individually named at the top of each page, and are listed in the table ofcontents.

68P02903W31-C 3

Aug 2007

General information

Text conventions

The following conventions are used in the Motorola cellular infrastructure documents torepresent keyboard input text, screen output text, and special key sequences.

Input

Characters typed in at the keyboard are shown like this.Items of interest within a command appear like this.

Output

Messages, prompts, file listings, directories, utilities, and environmental

variables that appear on the screen are shown like this.

Items of interest within a screen display appear like this.

Special key sequences

Special key sequences are represented as follows:

CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.

CTRL-SHIFT-c orCTRL+SHIFT+C

Press the Ctrl, Shift, and C keys at the same time.

ALT-f or ALT+F Press the Alt and F keys at the same time.

ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.

¦ Press the pipe symbol key.

RETURN or ENTER Press the Return or Enter key.

4 68P02903W31-C

Aug 2007

Contacting Motorola

Contacting Motorola■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Motorola appreciates feedback from the users of our documents.

24–hour support

If you have problems regarding the operation of your equipment, contact the Customer NetworkResolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listedat https://mynetworksupport.motorola.com. Select Customer Network Resolution Centercontact information. Alternatively if you do not have access to CNRC or the internet, contactthe Local Motorola Office.

Questions and comments

Send questions and comments regarding user documentation to the email address:mydocs@motorola.com.

Errors

To report a documentation error, call the CNRC (Customer Network Resolution Center) andprovide the following information to enable CNRC to open an SR (Service Request):

• The document type

• The document title, part number, and revision character

• The page number with the error

• A detailed description of the error and if possible the proposed solution

68P02903W31-C 5

Aug 2007

Security advice

Security advice■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Motorola systems and equipment provide security parameters that can be configured by theoperator based on their particular operating environment. Motorola recommends setting andusing these parameters following industry recognized security practices. Security aspectsto be considered are protecting the confidentiality, integrity, and availability of informationand assets. Assets include the ability to communicate, information about the nature of thecommunications, and information about the parties involved.

In certain instances, Motorola makes specific recommendations regarding security practices.The implementation of these recommendations and final responsibility for the security of thesystem lies with the operator of the system.

Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hourtelephone numbers are listed at https://mynetworksupport.motorola.com. Select CustomerNetwork Resolution Center contact information, from the menu located to the left of theLogin box. Alternatively if you do not have access to CNRC or the internet, contact the LocalMotorola Office.

6 68P02903W31-C

Aug 2007

Warnings, cautions, and notes

Warnings, cautions, and notes■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following describes how warnings and cautions are used in this document and in alldocuments of this Motorola document set.

Warnings

Warnings precede instructions that contain potentially hazardous situations. Warnings areused to alert the reader to possible hazards that could cause loss of life or physical injury. Awarning has the following format:

Warning text and consequence for not following the instructions in the warning.

Cautions

Cautions precede instructions and are used when there is a possibility of damage to systems,software, or individual items of equipment within a system. However, this damage presentsno danger to personnel. A caution has the following format:

Caution text and consequence for not following the instructions in the caution.

Notes

A note means that there is a possibility of an undesirable situation or provides additionalinformation to help the reader understand a topic or concept. A note has the following format:

Note text.

68P02903W31-C 7

Aug 2007

Safety

Safety■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

General safety

The following general safety guidelines apply to Motorola equipment:

• The power jack and mating plug of the power cable must meet InternationalElectrotechnical Commission (IEC) safety standards.

Refer to Grounding Guideline for Cellular Radio Installations – 68P81150E62.

• Power down or unplug the equipment before servicing.

• Using non-Motorola parts for repair could damage the equipment or void warranty.Contact Motorola Warranty and Repair for service and repair instructions.

• Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.Use precautions to prevent damage.

Electromagnetic energy

Relevant standards (USA and EC) applicable when working with RF equipment are:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposureto Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

• Council recommendation of 12 July 1999 on the limitation of exposure of the generalpublic to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective nationalregulations.

• Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 onthe minimum health and safety requirements regarding the exposure of workers to therisks arising from physical agents (electromagnetic fields) (18th individual Directive withinthe meaning of Article 16(1) of Directive 89/391/EEC).

8 68P02903W31-C

Aug 2007

Caring for the environment

Caring for the environment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following information describes national or regional requirements for the disposal ofMotorola supplied equipment and for the approved disposal of surplus packaging.

Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hourtelephone numbers are listed at https://mynetworksupport.motorola.com. Select CustomerNetwork Resolution Center contact information. Alternatively if you do not have accessto CNRC or the internet, contact the Local Motorola Office.

In EU countries

The following information is provided to enable regulatory compliance with the European Union(EU) directives identified and any amendments made to these directives when using Motorolaequipment in EU countries.

Disposal of Motorola equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)

Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunctionwith a recycling partner ensures that equipment is collected and recycled according to therequirements of EU environmental law.

Disposal of surplus packaging

European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste

Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipient’sresponsibility to ensure that packaging materials are collected and recycled according to therequirements of EU environmental law.

In non-EU countries

In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordancewith national and regional regulations.

68P02903W31-C 9

Aug 2007

CMM labeling and disclosure table

CMM labeling and disclosure table■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The People’s Republic of China require that our products comply with China ManagementMethods (CMM) environmental regulations. (China Management Methods refers to theregulation Management Methods for Controlling Pollution by Electronic Information Products.)Two items are used to demonstrate compliance; the label and the disclosure table.

The label is placed in a customer visible position on the product.

• Logo 1 means the product contains no substances in excess of the maximum concentrationvalue for materials identified in the China Management Methods regulation.

• Logo 2 means that the product may contain substances in excess of the maximumconcentration value for materials identified in the China Management Methods regulation,and has an Environmental Friendly Use Period (EFUP) in years, fifty years in the exampleshown.

Logo 1 Logo 2

The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxicand Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)will not leak or mutate causing environmental pollution, or bodily injury from the use of theEIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certainfield-replaceable parts, such as battery modules, can have a different EFUP and are markedseparately.

The Disclosure table is intended only to communicate compliance with China requirements.It is not intended to communicate compliance with EU RoHS or any other environmentalrequirements.

10 68P02903W31-C

Aug 2007

Motorola document set

Motorola document set■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Motorola document sets provide the information to operate, install, and maintain theMotorola equipment.

Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visitthe Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, orcontact your Motorola account representative.

Without internet access available, order hard copy documents or CD-ROMs with your MotorolaLocal Office or Representative.

If Motorola changes the content of a document after the original printing date, Motorolapublishes a new version with the same part number but a different revision character.

Document banner denitions

A banner (oversized text on the bottom of the page, for example, PRELIMINARY — UNDERDEVELOPMENT) indicates that some information contained in the document is not yet approvedfor general customer use.

Data encryption

In order to avoid electronic eavesdropping, data passing between certain elements in thenetwork is encrypted. In order to comply with the export and import requirements of particularcountries, this encryption occurs at different levels as individually standardized, or may not bepresent at all in some parts of the network in which it is normally implemented. The documentset, of which this document is a part, covers encryption as if fully implemented. Because therules differ in individual countries, limitations on the encryption included in the particularsoftware being delivered, are covered in the Release Notes that accompany the individualsoftware release.

68P02903W31-C 11

Aug 2007

Motorola document set

12 68P02903W31-C

Aug 2007

Chapter

1

Introduction to the Horizon II micro■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter provides a summary of the equipment, to enable readers to understand theterminology used and thus locate information using the table of contents and index.

68P02903W31-C 1-1

Aug 2007

Finding information in this manual Chapter 1: Introduction to the Horizon II micro

Finding information in this manual■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following are provided to enable readers to find the information in this manual.

• A full Table of Contents (TOC) is provided at the front of this manual.

• Headings are designed to convey contents accurately, to simplify searching for specificinformation.

• The Index at the back of the manual provides an alternative method of finding sub-sectionsof information.

• The first chapter provides a Summary of the equipment, to enable readers to understandterminology and thus locate information through the Table of Contents and Index.

The service manual comprises two main sections:

• Technical Description: In the Horizon II macro and Horizon II micro manuals, chaptersone to five and in the Horizon II mini manual, chapters one to six provide introduction,specifications, and technical descriptions of all the components of Horizon II equipment.

• Maintenance and Parts: In the Horizon II macro and Horizon II micro manuals, chapterssix to nine and in Horizon II mini manual, chapters seven to nine provide information onmaintenance and repair, with procedures to change field replaceable units (FRUs). Lists ofoptions and spares, with diagrams to illustrate FRUs, are also included.

The information in each chapter is grouped according to functionality.

Installation information for the Horizon II equipment is not provided in this manual(refer to the relevant Horizon II Installation and Configuration manual).

In this manual where CTU2 is mentioned, if CTU2Ds are installed, please read asCTU2D. If a section of the manual is specifically dealing with CTU2s or CTU2Ds, it ishighlighted at the beginning of the section.

1-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Equipment introduction

Equipment introduction■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II micro, shown in Figure 1-1, is a compact BTS, that may be pole or wall mountedoffering a wide range of deployment locations. It can be quickly deployed and is suitable for bothindoor and outdoor applications; no separate enclosure is required for outdoor applications.

It has multiple network functions, which include:

• Microcellular coverage requirements.

• Concentrated coverage in-fill.

• Hotspot capacity relief in higher subscriber networks.

• In-building coverage.

Figure 1-1 Horizon II micro, with solar cover

It is available in both GSM 900 and DCS1800 frequencies and provides up to two transceivercapacity in a single enclosure allowing it to support in Omni-2 configurations. In order toachieve sectored configurations, up to four Horizon II micro enclosures can be deployed in alogical site. For cost effectiveness, Horizon II micro enclosures can also be extended fromHorizon II BTSs, Horizonmacro or M-Cell6 base stations.

Horizon II micro supports GSM, GPRS and EDGE technologies, and can provide capacityimprovements through Adaptive Multi-Rate (AMR) and GSM Half Rate.

Horizon II micro uses the standard Motorola GSM carrier, the CTU2. All FRUs, are plug-infor easy maintenance and upgrade.

68P02903W31-C 1-3

Aug 2007

Equipment introduction Chapter 1: Introduction to the Horizon II micro

Names and acronyms for main enclosure equipment

This section provides an overview of the equipment in the Horizon II micro enclosures.

The Horizon II micro enclosure consists of: the frame structure (including doors and aheat exchanger), a main cage, on the enclosure left side, with an integrated midplane and asecondary cage on the enclosure right side. It contains the following equipment, as shown inFigure 1-2 Enclosure internal views on page 1-6, listed from the base up.

The left side of the enclosure houses the following:

• Power supply unit (PSU).

The PSU provides a regulated bus voltage converted from the primary power applied.

• External Fan module, mounted at the bottom of the heat exchanger.

This draws in cool air from the environment and passes it through the heat exchangerexternal circuit, where it cools the recirculated air.

• Internal fan unit.

This recirculates cooled air from the heat exchanger, providing cooling for the internalequipment, especially for the CTU2 transceivers and digital modules mounted directlyabove.

• Compact transceiver unit (CTU2).

Provides amplification and signal conditioning for downlink (Tx) signals and receivesuplink signals from the Mini-SURF. The CTU2 provides 2 x GSM/ GPRS and 1 x EGPRScapability. One CTU2 is fitted in the Horizon II micro enclosure to provide two GSM/GPRScarriers (double density).

• Compact transceiver unit 2 double density edge (CTU2D)

Support both SD and DD EDGE architectures, in addition to the various modes supportedby the legacy CTU2 radios. Similar to the CTU2, carrier A/B definitions and nomenclaturealso apply to CTU2D. The radio type CTU2D can be configured in different operatingmodes (single, double and capacity) within one cell.

• Alarm module.

This handles all enclosure alarm I/O signals and provides current sensing for externalsite alarms (through the PIX connectors).

• Site controller unit (HIISC).

Provides the site processing functions for the BTS (equivalent to the MCUF inHorizonmacro). Includes an integrated XMUX and NIU.

• Expansion multiplexer module (XMUX).

An optional module that replaces the site controller unit in an expansion (slave) enclosureto provide multiplexer connections to the master cabinet or enclosure.

1-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Equipment introduction

The right side of the enclosure houses the following:

• Miniature sectorized universal receiver front end (Mini-SURF) module.

Mounted at the lower front. Provides amplification, switching and signal conditioningfunctions for incoming (Rx) signals.

• Optional battery backup unit.

Mounted in the lower rear. Provides short term battery backup in the event of powersupply failure.

• PIX connector.

Mounted at the top front. Provides connection for customer-specific alarms and/orequipment.

• Tx blocks:

There are two types of Tx block available for the Horizon II micro: duplexer (DUP) andPGSM duplexer.

A single DUP or PGSM duplexer is fitted in the top rear.

The DUP/PGSM duplexer allows Rx and Tx signals to share an antenna and also providesfiltering and VSWR monitoring.

• Site expansion board.

An optional module mounted in the top centre. Provides fibre optic connections toexpansion, or from master, cabinets or enclosures.

Within the cable entry box:

• Line interface unit, (T43 or BIB type).

This is provides the interface for external network backhaul connections, along with lineisolation and impedance matching.

On the interface panel:

• The external power supplies ac connector.

• Enclosure main earth stud.

68P02903W31-C 1-5

Aug 2007

Equipment introduction Chapter 1: Introduction to the Horizon II micro

Figure 1-2 Enclosure internal views

1-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Equipment introduction

Figure 1-3 Functional diagram of Horizon II micro

68P02903W31-C 1-7

Aug 2007

Horizon II BTS comparison with Horizonmacro Chapter 1: Introduction to the Horizon II micro

Horizon II BTS comparison with Horizonmacro■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II macro is a development of and a replacement for the Horizonmacro indoor BTS,the Horizon II mini is a development of the Horizon II macro indoor BTS, and the Horizon IImicro is a development of the Horizon II mini indoor BTS. Although Horizon II mini and HorizonII micro cannot be used as a direct replacement for the Horizonmacro BTS, they are, however,compatible with it. Additionally, the Horizon II micro can be used as a direct replacement forthe Horizonmicro2 BTS but these two types of BTS are not compatible.

A mixed site of up to four Horizon II micro, Horizon II mini, Horizon II macro and Horizonmacro(or even M-Cell6) BTSs can be combined to form a single site, with either the Horizon IIequipment, a Horizonmacro indoor, or an M-Cell6 being in control of the other units.

In cases where a Horizonmacro MCUF or M-Cell6 MCU is the master site controllerwith Horizon II equipment as an expansion cabinet, the MCUF/MCU MUST have aPCMCIA card (running CSFP) installed to provide the additional memory required bythe Horizon II equipment. Use of Horizon II micro as a master in mixed technologysite is not recommended as there is no provision for redundancy

In a site running GSR9 software, macro and micro cells cannot coexist. So, Horizon II macroand Horizon II micro BTS equipment cannot be deployed at the same site, if it is running GSR9software.

Compatibility with Horizonmacro and M-Cell6

A mixed technology BTS site can be achieved by combining a maximum of four units. Theunits can be any combination of Horizon II mini, Horizon II macro, Horizonmacro and M-Cell6,any of which can be the controlling (master) BTS, subject to the requirements described inthe previous NOTE. For example, a 24-carrier BTS site (in an 8/8/8 configuration) can beachieved by combining a maximum of four units. The units can be any combination of eitherthe following equipment:

• Horizon II equipment

• Horizonmacro

• M-Cell6

Any of the above can be the controlling (master) BTS, subject to the requirementsdescribed in the previous NOTE.

1-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II BTS comparison with Horizonmacro

Figure 1-4 shows an illustration of a mixed three cabinet site, with a Horizon II micro BTSas the controller (master).

Figure 1-4 Example of a mixed BTS site

In Figure 1-4 the CTU2s in the Horizon II macro BTS are double density and aretherefore capable of handling two carriers each (12 carriers total).

The maximum site capacity is 24 carriers across all expansion cabinets in the site.

68P02903W31-C 1-9

Aug 2007

Horizon II BTS comparison with Horizonmacro Chapter 1: Introduction to the Horizon II micro

Comparison of Horizon II equipment with Horizonmacro

Table 1-1 compares the functionality of main components of the Horizon II equipment withequivalent components of the previous generation Horizonmacro equipment.

Table 1-1 Comparison of Horizon II micro with Horizonmacro

Function Horizon II micro Horizon II mini Horizon II macro Horizonmacro

Input powerconversionunits (max.

fitted)

PSU (1) PSU (1) PSU (4) PSM (3)

Power totransceiversand signal

routing

Midplane Midplane Backplane BPSM andbackplane

Transceivers(max. fitted)

CTU2 (1) CTU2 (2) CTU2 (6) CTU (6)

Mainprocessor

module (max.fitted)

HIISC (1) HIISC (1) HIISC (2) MCUF (2)

Processormodule

connection totransceiversin another

cabinet

Internal XMUXin HIISC (1) and

separate siteexpansion boards (1)

Internal XMUXin HIISC (1)and separatesite expansionboards (1)

Internal XMUX inHIISC (1) andseparate siteexpansion boards(1 or 2)

InternalFMUX inMCUF (2)or externalFMUX (2)

Slave cabinetmultiplexer

XMUX XMUX XMUX FMUX

Rxcomponents

Mini-SURF Mini-SURF SURF2 (2) SURF

Transceiverto Rx

components

Mini-SURF harness Mini-SURFharness

SURF2 harness SURF harness

Tx blocks(max. fittedinternally)

DUP/PGSM duplexer(1)

DUP/PGSMduplexer (2) andCMB (1)

DUP, HCU andDHU (6)

DCF, TDF,DDF and HCU(3)

DC powersupply

for digitalmodules

(max. fitted)

Integrated in HIISC,supplied through

midplane

Integrated inHIISC, suppliedthroughmidplane

Integrated inHIISC, suppliedthrough backplane

BPSM (2)

Equipmentprotection/isolation

External protectivedevice

MCBM CBC CBM

Continued

1-10 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II BTS comparison with Horizonmacro

Table 1-1 Comparison of Horizon II micro with Horizonmacro (Continued)

Function Horizon II micro Horizon II mini Horizon II macro Horizonmacro

Links toterrestrialnetwork

(max. fitted)

Internal NIU in HIISC Internal NIU inHIISC

Internal NIU inHIISC

NIU (4)

Alarmhandling

Alarm module * Alarm module * Alarm module * Alarm module

E1 links T43/CIM or BIB/BIM(E1 only)

T43/CIM orBIB/BIM (E1only)

CIM/T43 orBIM/BIB

T43/CIM orBIB/BIM

Installationtemperature

control

Integral heatexchanger

HMS HMS TMS(Outdoor) Fanunits (Indoor)

* Not compatible with the Horizon macro alarm module.

68P02903W31-C 1-11

Aug 2007

Introduction to Horizon II micro specications Chapter 1: Introduction to the Horizon II micro

Introduction to Horizon II micro specications■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

All Horizon II micro specifications are included in the following sections:

• Introduction to specifications.

• Physical specifications.

• Electrical and RF specifications.

Approval and safety

Table 1-2 Horizon II micro specication compliance

Specicationtype Specication number

Type Approval EN 301 502

EMC EN 301 489-8; Part 8, ETSI EN 301 489-1 EU Directive 89/336/EEC (relatingto Electromagnetic Compatibility amending Directives 91/263/EEC,92/31/EEC, 93/97/EEC)

Safety EU Directive 73/23/EEC, EN50385, EN 41003, EN 60215 and IEC 60950

Environmental ETS300 019 1-4 Class 4.1 Operation (outdoor)with extended temperature (-40 °C to +50 °C)ETS300 019 1-2 Class 2.3 TransportETS300 019 1-1 Class 1.3E StorageWEEE directive 2002/96/EC

Software requirements

All Horizon II micro BTSs require software release GSR6 (Horizon II) or later in the network.

Half rate requires software release GSR7 (HR) or later in the network.

The PGSM duplexer requires software release GSR6 (Horizon II) 1670.25 or GSR7 1760.0ain the network.

Access control requirements

Unauthorized access to the Horizon II micro equipment must be prevented. The Horizon II microis suitable for either indoor or outdoor installation but must be installed only in a location whereaccess by unauthorized personnel can be prevented.

1-12 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro physical specications

Horizon II micro physical specications■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the physical dimensions, weights, torque values and structuralconsiderations of the Horizon II micro base station. The section also provides a simple sitelayout plan to help visualize the site dimensions.

Enclosure dimensions

The maximum external dimensions for Horizon II micro (including all external covers) aregiven in the table below.

Table 1-3 Enclosure dimensions

Height Width Depth

Horizon II micro 590 mm 590 mm 250 mm

(including wall bracket) 300 mm

(including pole-mountingbracket adapter kit)

332 mm to 342 mm(Depending on pole

diameter)

Weights

Table 1-4 shows the maximum enclosure weights.

Consider future expansion. Additional enclosures may be added to the site. Ensurethe mounting structure is capable of supporting the total weight.

Table 1-4 Enclosure weights

Item Weight

Horizon II micro enclosure (empty, withoutsolar cover)

18.5 kgs

Horizon II micro (fully populated excludingbattery unit)

32 kg

Battery unit 5 kg

Mounting bracket 4.7 kg

Pole-mounting bracket adapter kit 1.65 kgs

68P02903W31-C 1-13

Aug 2007

Horizon II micro physical specications Chapter 1: Introduction to the Horizon II micro

Torque values

Table 1-5 details torque values used during installation, maintenance and repair procedures.

Table 1-5 Torque values for all enclosure screws/bolts and RF connectors

Size ofscrew/bolt M4 M6 M8 M10 SMA N-Type 7/16

Torque value 2.2 Nm 3.4 Nm 5 Nm 10 Nm 1 Nm 3.4 Nm 25 Nm

Torque values used with anchor bolts will depend on the anchor bolt manufacturer.Check manufacturer’s data for correct values.

Environmental limits

Table 1-6 lists the environmental limits for Horizon II micro operation and storage.

Table 1-6 Environmental limits for operation and storage

Environment Temperature Relative Humidity

Operating –40 °C to +50 °C. 5% to 100% relative humidity,not to exceed 29 g water/m3 air.

Storage –45 °C to +70 °C. 8% to 100% relative humidity,not to exceed 30 g water/m3 air.

This specification is valid up to 3 km altitude, corresponding to an atmosphericpressure range of 648 to 1048 millibars.

1-14 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro physical specications

Structural considerations

The site structure must be designed to meet accepted cellular system specifications, andmeet Horizon II micro physical, electrical and RF specifications. Additional considerationsare described below:

• The structure on which the BTS enclosure is mounted must be of sufficient strength tosupport the maximum gross weight of the equipment.

Motorola recommends using a qualied structural engineer to assess equipmentmounting requirements, such as: mounting pole construction, wall mountinganchors, cell site construction, cable routing conduits or ducts, and, in seismicallyactive areas, to provide a suitable design for earthquake proong, if required.

• Adequate clearance must be provided at the front and sides of the enclosure for operationand maintenance purposes. Additionally, the enclosure must be installed in an area whereunauthorized access to the equipment can be prevented.

• The enclosure ventilation air enters at the bottom of the enclosure and is expelled atthe top of the front face of the solar cover.

• The mounting brackets allow an enclosure to be mounted to a wall or pole, and themounting bracket provides correct clearance at the rear and top for ventilation.

• In addition to supporting the equipment weight, the structure on which the BTS enclosureis mounted must be of sufficient strength to withstand 105 knot (192 kph) winds on theenclosure.

• Cable entry for the Horizon II micro enclosure is from below, therefore appropriate meansof cable routing, (such as cable ducts, troughs or conduits), must already be in place.

Through-wall cable ducts or conduits should be specified by a structuralengineer or site architect.

Layout plan

The site layout must take into account not only the dimensions of the equipment but alsominimum clearances for correct operation, ventilation and maintenance purposes.

68P02903W31-C 1-15

Aug 2007

Horizon II micro physical specications Chapter 1: Introduction to the Horizon II micro

Figure 1-5 shows the Horizon II micro installation layout plan.

Figure 1-5 Horizon II micro site layout plan

1-16 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro electrical and RF specications

Horizon II micro electrical and RF specications■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the power, radio frequency specifications and backhaul connectivityoptions of the Horizon II micro BTS.

Power requirements

The power supply requirements and power consumption of the Horizon II micro are describedbelow.

Enclosure power supply requirements

Table 1-7 lists the external power supply requirements for the different power supply options.

Table 1-7 Horizon II micro external power supply requirements

Nominal Voltage Voltage supply range Current supplymaximum

110 V ac to 240 V ac (45 HZ to 66 Hz) 88 V ac to 270 V ac 5 A

Power consumption

Table 1-8 lists typical and worst case power consumption values for example Horizon II microconfigurations.

Table 1-8 Horizon II micro power consumption details

Power consumption (W)Example conguration

Typical Worst case

Micro Tx double densityapprox 2 W

250 400Enclosure ac input (88 Vto 270 V)

Micro Tx single densityapprox 4 W

250 400

“Worst case” power consumption figures are theoretical values derived underextreme conditions and are affected by variables such as temperature, componenttolerances, transmission power and supply voltage. Although these figures must beconsidered when planning site power requirements, typical measured consumptionvalues will be lower.

68P02903W31-C 1-17

Aug 2007

Horizon II micro electrical and RF specications Chapter 1: Introduction to the Horizon II micro

Battery backup

The Horizon II micro BTS can be fitted with an optional battery unit to provide short termbattery backup (sufficient to send a low voltage disconnect imminent (LVDI) alarm and performcontrolled shut down).

The typical duration of the battery backup, is 18 to 20 minutes, depending on loading.

RF power output

Table 1-9 and Table 1-10 list the RF power output of the CTU2 for the 900 MHz and 1800 MHzfrequency bands in the various configuration options available.

The RF output power is measured at the antenna port at the bottom of the enclosure.

Use the max_tx_bts parameter to ensure the maximum Tx power is correctly set oninstallation and after CTU2 replacement. For example; if using standard power option,set value = 5 to 21, or high power option, set value = 0 to 21). See the commissioningsection of 68P02902W32, or 68P02902W31 Site verication procedures, for Cell Sitepower (CSPWR) calibration, Tx output power calibration procedure.

For a standard power option, setting the max_tx_bts to less than 5 may result in:

• Transmit output power above recommended levels.

• Increased fan noise.

• The possibility of power cutback or shutdown due to increased enclosuretemperature.

The CTU2 transmit power, in Horizon II micro, is factory calibrated as a macro BTS(potentially up to: 60 W for PGSM900, 63 W for EGSM900 and 50 W for DCS1800,in single density high power mode), prior to delivery.

Refer to the following standards (USA and EU), or equivalent national and regionalregulations, when making calculations for RF equipment:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10 kHz to 300 GHz).

1-18 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro electrical and RF specications

RF output — standard option

The CTU2D maintains the same output power figures as CTU2, but with a -0/+2 dBtolerance at mid-band in room temperature and -0/+2.5 dB tolerance applies for allchannels at extreme conditions.

Table 1-9 lists the RF standard power output option of the CTU2 for the 900 MHz and 1800MHZ frequency bands in the various configuration options possible.

Table 1-9 CTU2 RF standard power output option, installed in Horizon II microenclosure with no external combining

Output power (+/-2 dB)

GMSK 8–PSKCTU2conguration

PGSM900 EGSM900 DCS1800 PGSM900 EGSM900 DCS1800

Singledensity

4 W(36 dBm)

4 W(36 dBm)

3.2 W(35 dBm)

4 W(36 dBm)

4 W(36 dBm)

3.2 W(35 dBm)

Doubledensity

2 W(33 dBm)

2 W(33 dBm)

1.6 W(32.0 dBm)

n/a n/a n/a

RF output — high power option

Table 1-10 lists the RF high power output option of the CTU2 for the 900 MHz and 1800 MHZfrequency bands in the various configuration options possible.

Table 1-10 CTU2 RF high power output option, installed in Horizon II micro enclosurewith no external combining

Output power (+/-2 dB)

GMSK 8–PSKCTU2conguration

PGSM900 EGSM900 DCS1800 PGSM900 EGSM900 DCS1800

Singledensity

60 W(47.78 dBm)

63 W(48 dBm)

50 W(47 dBm)

19 W(42.78 dBm)

20 W(43 dBm)

16 W(42 dBm)

Doubledensity

19 W(42.78 dBm)

20 W(43 dBm)

16 W(42.0 dBm)

n/a n/a n/a

68P02903W31-C 1-19

Aug 2007

Horizon II micro electrical and RF specications Chapter 1: Introduction to the Horizon II micro

Sensitivity

The receiver sensitivity performance of the equipment is shown in Table 1-11.

Table 1-11 Rx sensitivity performance

PGSM900 EGSM900 GSM1800Conditions

Typical Guaranteed Typical Guaranteed Typical Guaranteed

Static channel -111.4dBm

-109.8 dBm -112.0dBm

-110.5dBm

-114.0dBm

-111.5 dBm

Faded channel -108.4dBm

-106.8 dBm -109.0dBm

-107.5dBm

-111.0dBm

-108.5 dBm

Faded withdiversity

Up to–113.4dBm

Up to–111.8 dBm

Up to-114.0dBm

Up to-112.5dBm

Up to-116.0dBm

Up to-113.5 dBm

Notes to Table 1-11:

• GMSK performance for a nominal 2-2 configuration with a duplexer on the main receiverbranch.

• Typical values are the average expected performance over the frequency band whenmeasured at the main branch BTS antenna port, that is, the duplexer antenna port.

• There is approximately 0.5 dB degradation of performance over the frequency bandcompared to mid-band. Mid-band performance is typically 0.5 dB better than values quotedabove which are intended to cover the entire receive band.

• Guaranteed values are the worst expected performance over the frequency band whenmeasured at the main branch BTS antenna port, that is, the duplexer antenna port.

• Diversity performance (2 branch) is shown to be 5 dB better than non diversity, but theexact figure is dependent on the BTS configuration, antenna spacing/orientation andradio propagation environment.

All values cited assume the use of qualified and calibrated BTS BER test equipment.All signal sources, faders, attenuators and RF cables are assumed to have beenaccurately calibrated in order to determine the true power level being applied tothe BTS antenna port.

1-20 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro electrical and RF specications

Frequency capability

The frequency capabilities of the Horizon II micro are described in this section.

Frequency band characteristics

BTS radio channels (RF carriers) are full duplex (transmit and receive) with the characteristicslisted in the table below:

Table 1-12 Horizon II micro frequency band characteristics

PGSM900 EGSM GSM1800

Transmit frequency band (MHz) 935 to 960 925 to 960 1805 to 1880

Receive frequency band (MHz) 890 to 915 880 to 915 1710 to 1785

Transmit/receive duplex separation(MHz)

45 45 95

Channel width (kHz) 200 200 200

Number of channels 124 174 374

935.0 to 935.1 925.0 to 925.1 1805.0 to 1805.1Transmit frequency guard bands(MHz) 959.9 to 960.0 959.9 to 960.0 1879.9 to 1880.0

890.0 to 890.1 880.0 to 880.1 1710.0 to 1710.1Receive frequency guard bands(MHz) 914.9 to 915.0 914.9 to 915.0 1784.9 to 1785.0

Transmit channel centre frequency(MHz)

Even tenths of aMHz from 935.2

to 959.8 (200kHz spacing)

Even tenths of aMHz from 925.2

to 959.8 (200kHz spacing)

Even tenths of aMHz from 1805.2to 1879.8 (200kHz spacing)

Receive channel centre frequency(MHz)

Even tenths of aMHz from 890.2

to 914.8 (200kHz spacing)

Even tenths of aMHz from 880.2

to 914.8 (200kHz spacing)

Even tenths of aMHz from 1710.2to 1784.8 (200kHz spacing)

Frequency hopping

The Horizon II micro supports baseband frequency hopping (BBH) and synthesizer frequencyhopping (SFH).

If Horizon II micro is used to expand from a Horizonmacro or M-Cell6, BBH is notsupported.

68P02903W31-C 1-21

Aug 2007

Horizon II micro electrical and RF specications Chapter 1: Introduction to the Horizon II micro

BSC connectivity options

Only E1 connection is supported.

1-22 68P02903W31-C

Aug 2007

Chapter

2

Horizon II micro structure■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter describes the enclosure structure and inner connections to assist understanding ofthe equipment functions. It should not normally be necessary to dismantle the enclosure beyondfield replaceable unit (FRU) level.

The Horizon II micro structure components are explained in the following sections:

• Horizon II micro internal structure and harnesses on page 2-6

This section describes the empty enclosure and the Mini-SURF harness connectionsbetween the Mini-SURF and the midplane and transceivers.

• Interface panel and cable entry box on page 2-12

This section describes how all external cabling enters the enclosure.

• Enclosure temperature control on page 2-17

This section describes the principles of the enclosure temperature control system.

• External fan module description on page 2-20

This section describes the fan unit within the temperature control system.

• Enclosure doors on page 2-24

This section describes the structure and function of the door.

• Mounting options on page 2-26

This section describes the various mounting options that can be used with the HorizonII micro enclosure.

68P02903W31-C 2-1

Aug 2007

Horizon II micro enclosure structure Chapter 2: Horizon II micro structure

Horizon II micro enclosure structure■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Figure 2-1 shows an external view of a closed enclosure and Figure 2-2 shows an enclosure withthe doors removed.

Figure 2-1 External view of a Horizon II micro enclosure, without the solar cover tted

2-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro enclosure structure

Figure 2-2 Left side view of Horizon II micro enclosure with the doors removed

68P02903W31-C 2-3

Aug 2007

Horizon II micro enclosure structure Chapter 2: Horizon II micro structure

Overview of structure

The equipped enclosure is shown in Figure 2-3 . The enclosure is designed for minimummaintenance and maximum ease of module replacement, and has access only from the front.

Filled enclosure view

Figure 2-3 shows a Horizon II micro enclosure with a representative selection of modulesinstalled. Individual modules are described in detail in later chapters of this technicaldescription.

Figure 2-3 Enclosure showing main components

2-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro enclosure structure

External solar cover

To protect the system from solar radiation a plastic cover is fitted. The cover is located at thefront and gives the BTS a more aesthetic shape.

Figure 2-4 External solar cover view

68P02903W31-C 2-5

Aug 2007

Horizon II micro internal structure and harnesses Chapter 2: Horizon II micro structure

Horizon II micro internal structure and harnesses■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II micro internal structure provides a platform for module installation and powerand digital signal interconnection to enclosure modules. The internal structural componentscomprise:

• The main cage providing compartments for internal fans, the CTU2, digital modules andthe PSU.

• The secondary cage providing compartments for the mini-SURF, the DUPs, the siteexpansion board and the optional backup battery.

• The midplane and internal harnesses for routing power and signals to all modules andpower to the Mini-SURF.

• The cable entry box that contains the line interface unit, either T43 or BIB and allows theconnection of other communications connectors, (PIX alarms and site expansion fibreoptics).

• The Interface panel that houses power and earth connectors and communications cableglands.

The midplane and internal harnesses are permanently fixed to the external enclosure body atthe factory and cannot be removed in the course of normal maintenance or FRU replacementprocedures.

2-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro internal structure and harnesses

Internal structure

Figure 2-5 shows the front view of empty enclosure showing internal structure and midplanecomponents.

Figure 2-5 Front view of empty enclosure showing internal structure and midplanecomponents

Midplane

All possible RF and digital module combinations are served by the same midplane. The onlymodule-to-module cabling required is the Tx cabling from the CTU2 to the Tx block and theMini-SURF to the TX block. Any external attachments requires separate cabling.

68P02903W31-C 2-7

Aug 2007

Horizon II micro internal structure and harnesses Chapter 2: Horizon II micro structure

The midplane is a multi layered printed circuit board with attached connectors on front andback; this construction maintains controlled impedance and screening for high speed signallines. The midplane uses partial planes for power circuits to meet conductor separationrequirements and minimize electromagnetic interference (EMI).

The midplane:

• Routes power and digital signals throughout the enclosure.

• Provides connectors for hot swap capable plug in modules, including Horizon II minibattery module.

• Provides power to the Mini-SURF harness.

• Provides connectors for the heat sensors in the enclosure above the CTU2.

• RF connections are not made through the midplane, but are separately cabled.

• All FRUs connected to the midplane, are hot swap capable.

• The midplane is not user replaceable and is supplied as part of the enclosureassembly.

Figure 2-5 shows the connector locations on the front of the midplane.

Internal harness function

The harnesses provide cables to link connectors on the midplane with internal equipment.

The internal harnesses are fitted to the enclosure at the factory and are not intendedto be removed in the course of normal maintenance or FRU replacement procedures.

2-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro internal structure and harnesses

Mini-SURF harness

The Mini-SURF harness connects between the Mini-SURF chassis and the CTU2 connector fittedon the midplane of the enclosure. The Mini-SURF chassis supports the Mini-SURF modules.The Mini-SURF harness provides:

• One connector to the Mini-SURF for RF and power.

• One RF connector to the CTU2, consisting of two inputs, one each for Rx A and Rx B, asshown in Figure 2-6 The RF connectors are free floating to ensure correct fitting of theCTU2 modules.

The additional connectors are not used in the Horizon II micro.

• One connector to the midplane is supplied, for power from the PSUs.

Figure 2-6 CTU2 connector

68P02903W31-C 2-9

Aug 2007

Horizon II micro internal structure and harnesses Chapter 2: Horizon II micro structure

Secondary cage

The secondary cage, shown in Figure 2-7, provides:

• An area to hold a single duplexer (DUP or PGSM).

• An area to hold one site expansion board.

• An area to hold a Mini-SURF module.

• An area to hold the backup battery unit.

• The PIX alarms connector.

All connectors are linked to the midplane by internal cable harnesses. Plastic connector covers,supplied by Motorola, keep unused connectors protected from damage by static or foreignmatter and should be retained.

2-10 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro internal structure and harnesses

Figure 2-7 shows the secondary cage with major features labelled.

Figure 2-7 Secondary cage with major features labelled

68P02903W31-C 2-11

Aug 2007

Interface panel and cable entry box Chapter 2: Horizon II micro structure

Interface panel and cable entry box■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The interface panel and cable entry box are located on the right side of the enclosure nearthe base , as shown in Figure 2-7.

Interface panel

The interface panel, shown in Figure 2-8 provides a connection point for antenna cables, acmain power, the main enclosure earth and cable glands for passing all external cabling intothe enclosure.

Internal antenna connections to the Horizon II micro Mini-SURF and duplexer are made bycables fitted as part of the interface panel.

2-12 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Interface panel and cable entry box

Figure 2-8 Interface panel view

68P02903W31-C 2-13

Aug 2007

Interface panel and cable entry box Chapter 2: Horizon II micro structure

Cable entry box

The cable entry box, shown in Figure 2-9, houses:

• A mounting point for the backhaul line interface unit (T43 or BIB).

• The cable access to the PIX alarms connector.

• The ac power filter.

Figure 2-9 Cable entry box

2-14 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Interface panel and cable entry box

Line interface module

The line interface module consists of passive analogue components and is responsible forphysical termination and protection. It provides connections for six span lines.

75 ohm coax T43/CIM and 120 ohm twisted pair BIB/BIM boards are provided for E1 termination.Each provides a 120 ohm interface to the HIISC integral NIU line interface unit (LIU).

BIB/BIM

The Balanced-line Interconnect Board (BIB), also known as BIM, provides the line isolationbetween the pulse code modulated (PCM), E1 circuit lines and the Horizon II micro midplane.The board provides an interface for up to six input and six output balanced 120 ohm lines. 12transformers are used to provide line isolation while maintaining impedance matching betweenthe E1 circuit lines and the NIU part of the HIISC. Each transformer has a 1:1 turn ratio tomatch the external and midplane 120 ohm connections.

Connection is made using a 37-pin D-type connector to both the back panel and the externalPCM screened twisted pair circuit lines. Figure 2-10 shows a typical BIB/BIM.

Figure 2-10 BIB/BIM

BIB pinouts are detailed in Chapter 2 of 68P02903W32, Horizon II micro: Installation andConfiguration.

68P02903W31-C 2-15

Aug 2007

Interface panel and cable entry box Chapter 2: Horizon II micro structure

T43/CIM

The Type 43 Interconnect Board (T43), also known as CIM, provides the impedance matchingand line isolation between the pulse code modulated (PCM), E1 circuit lines and the Horizon IImicro. The board provides an interface for up to six input and six output unbalanced coaxial 75ohm lines. 12 transformers are used to provide impedance matching and line isolation betweenthe E1 circuit lines and the NIU part of the HIISC. Each transformer has a 1:1.25 turns ratioto match the external 75 ohm and midplane 120 ohm connections. Each input and output isisolated to 1500 V from the midplane.

Connection is made using a 37-pin D-type connector to the back panel and 12 T43 coaxialconnectors to the external E1 circuit lines. Figure 2-11 shows a T43/CIM.

Figure 2-11 T43/CIM

T43 pinouts are detailed in Chapter 2 of 68P02903W32, Horizon II micro: Installation andConfiguration.

2-16 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Enclosure temperature control

Enclosure temperature control■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II micro enclosure contains equipment that must be maintained within theoperational temperature range to ensure correct operation of the equipment and to guardagainst premature failure. The internal temperature is maintained within these limits bya heat exchanger system.

Enclosure and equipment temperature control

Under normal operating conditions, hot air from the equipment in the enclosure is circulatedthrough the heat exchanger by the internal fans. This air passes downwards through the heatexchanger, and the cooled air returns to the inside of the enclosure through a vent at thebottom inside face of the enclosure. This circuit forms a closed system, ensuring that theenclosure remains sealed from the external atmosphere. An external fans draws cool air intothe external circuit through the base of the heat exchanger. The air passes upwards throughthe heat exchanger and the heated air is expelled through the front panel top grille. This isshown in Figure 2-12.

The speed of the internal fans is constant to ensure adequate airflow, while that of the externalfans are temperature controlled, by the climate control unit, mounted inside the enclosure. Ifthe temperature within the enclosure (measured at the climate control unit circuit board) risesabove a predetermined level, the external fans start, then as temperature rises the speedof the external fans increase to boost the external airflow through the heat exchanger, thusincreasing the cooling rate.

An electric heater is located above the internal fans. It is thermostat controlled and thethermostat turns on at 0 ºC and off at +5 ºC. It also has its own high limit temperaturethermostat operating at 60 ºC, if the controlling thermostat fails. The purpose of the heater is toprevent the enclosure air temperature from dropping too low. Circuit protection is provided bytwo 3.15 A ceramic fuses, (one for live; one for neutral), mounted in the enclosure structureimmediately above the fan tray.

68P02903W31-C 2-17

Aug 2007

Enclosure temperature control Chapter 2: Horizon II micro structure

Figure 2-12 Cross sectional view of air ow in the enclosure

Over heat conditions

Under overheat conditions, as the temperature rises above preset levels, temperature sensorslocated in various areas within the enclosure provide alarms. A further increase in temperaturecauses dual sensors, set at a higher threshold temperature to initiate PSU and enclosureshutdown. The enclosure is restarted when the sensors are reset by a specified, substantialfall in temperature.

The CTU2 has its own shutdown responses to overheating. The CTU2 reduces RF transmit powerby 0.6 dB if the internal enclosure temperature exceeds a preset threshold. The CTU2 furtherreduces RF transmit power by 4 dB and a power amplifier over-temperature alarm is generatedif the internal enclosure temperature exceeds a second higher preset threshold. The CTU2resets if the enclosure temperature exceeds a third, still higher threshold. The temperatures atwhich these protective actions occur is dependent on the Tx power and equipment configuration.

Table 2-1 Temperature thresholds for CTU2 shutdown responses

Action Carrier A internal temp Carrier B internal temp

0.6 dB cutback 92 ºC 89 ºC

4 dB cutback 102 ºC 99 ºC

Shut off 107 ºC 104 ºC

The CTU2 shutdown response to overheating provides a second level of enclosure protection,independent of the enclosure heat sensors.

2-18 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Enclosure temperature control

Temperature sensors

The three enclosure temperature sensors are located above the transceiver rack and consistof the following:

• One sensor provides an enclosure over-temperature alarm when air at the sensor reaches+75 °C. The alarm is processed by the alarm board and site controller unit, and is sent onto the OMC-R through the BSC.

• Two sensors shut down the BTS to protect the enclosure equipment from heat damagewhen air at the sensors reaches +85 °C. Both sensors must detect excess temperaturefor the shutdown to take place; this reduces the risk of an unnecessary shutdown. Noprior notification of shutdown is given to the OMC-R, except for the original 75 °Cenclosure sensor alarm. This is because the site controller unit and CTU2s lose powerand functionality on shutdown.

The internal enclosure temperature will vary, depending on enclosure configurationand operating conditions.

Enclosure restart after shutdown

The enclosure is restarted when the over-temperature condition initiating shutdown hasreturned to within specified limits. The two +85 °C temperature sensors reset at +55 °C.This re-establishes an earth point for the PSU internal detectors connected to the enclosureheat sensors, which then reactivate the PSU outputs. The site controller unit then rebootsas in a normal power up.

68P02903W31-C 2-19

Aug 2007

External fan module description Chapter 2: Horizon II micro structure

External fan module description■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The external fan module consists of 4 fans controlled by two internal thermostats. The fans arelocated on a fan tray under the heat exchanger.

Either standard or high power fan modules may be fitted to the unit. If a high power module isfitted, then a dongle must be fitted to the D-type PIX connector located at the rear of the unit.

Standard and high power fan modules are identical in appearance, differing only in powerconsumption and performance. Labels are attached to the units, as shown inFigure 2-13 toidentify their power rating

Figure 2-13 External fan module power rating labels

External fan operation

The external fans draw ambient air from the enclosure exterior at the base of the heat exchangerpasses it upward through the heat exchanger matrix, where it cools the recirculated air fromthe enclosure interior. The heated air is expelled through the heat exchanger upper grille andout through the top vent of the solar cover.

The fans have linear fan speed regulation and speed depending on the temperature insidethe enclosure.

The following functionality is supported:

• Speed control for up to six fans (although only four are used).

• Two temperature sensors for monitoring the internal temperature.

Fan speed control

There is one set-point value for the fans (T-start). This is used when an internal temperatureabove 35 °C is measured. The fans then start to operate.

2-20 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro External fan module description

Temperature sensors

The two temperature sensors are mounted on a bracket above the PSU module and areconnected to the fan module electrical harness using a 4–way push-in connector.

View of an external fan module

Figure 2-14 View of an external fan module

68P02903W31-C 2-21

Aug 2007

Internal fan unit description Chapter 2: Horizon II micro structure

Internal fan unit description■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Internal airflow for the enclosure is provided by a single fan unit, located beneath the CTU2 anddigital modules. The fan unit contains two fans, as shown in Figure 2-15.

Either standard or high power fan modules may be fitted to the unit. Standard and high powerfan modules are identical in appearance, differing only in power consumption and performance.

The internal fan tray uses the same connector, electrical interface and alarm interface as theHorizon II mini fan tray.

In Horizon II micro the fan unit does not directly provide cooling for the PSU. ThePSU contains internal fans, which draw in cool air, from the heat exchanger, throughthe side of the PSU and pass it upward into the rest of the enclosure.

View of an internal fan unit

Figure 2-15 View of an internal fan unit

2-22 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Internal fan unit description

Internal fan operation

The internal fans recirculate air within the enclosure, this circuit forms a closed system,ensuring that the enclosure remains sealed from the external atmosphere. The fans draw incooled air from the base of the heat exchanger and passes the air upward through the enclosurecooling the internal components. Air is returned to the top of the heat exchanger through agrille at the top of the side wall the enclosure. The fans run continuously at a fixed speed toensure adequate air flow.

The fan unit is not of the same type as used in other Horizon II equipment.

68P02903W31-C 2-23

Aug 2007

Enclosure doors Chapter 2: Horizon II micro structure

Enclosure doors■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The two doors on the right and left sides of the enclosure gives access to the BTS internalcomponents. Both doors are securely held in place with four SouthCo trilobe high securityfasteners. The doors are fitted with magnets, which actuate sensors used to generate a dooropen alarm signal when either of the door is opened.

The doors each have four blind, threaded holes to accept the securing screws for the Solar cover.

A door open alarm is generated if either of the door is opened while the equipmentis active.

2-24 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Enclosure doors

Door view

Figure 2-16 Door view

68P02903W31-C 2-25

Aug 2007

Mounting options Chapter 2: Horizon II micro structure

Mounting options■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II micro enclosure can be either wall or pole mounted.

Wall mounting

The enclosure can be wall mounted using the bracket supplied with the enclosure.

Figure 2-17 Mounting bracket

2-26 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Mounting options

Pole mounting

The pole-mounting bracket adapter kit is not supplied with the enclosure. It must be orderedseparately and requires assembly before use.

Figure 2-18 Pole-mounting bracket adapter kit

68P02903W31-C 2-27

Aug 2007

Mounting options Chapter 2: Horizon II micro structure

2-28 68P02903W31-C

Aug 2007

Chapter

3

Power distribution■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter describes the functional operation of power supply components and powerdistribution used in the Horizon II micro.

68P02903W31-C 3-1

Aug 2007

Horizon II micro power supplies Chapter 3: Power distribution

Horizon II micro power supplies■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II micro power supply and distribution elements comprise:

• A single 88 V to 270 V ac wide ranging power supply unit (PSU)

The Horizon II micro outdoor operates on ac only.

• An optional battery module, the battery used is the Horizon II mini battery module.

Location of power modules

Figure 3-1 shows the Horizon II micro enclosure with the power supply and distribution modulesindicated.

Figure 3-1 Location of power modules

3-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Power supply unit (PSU)

Power supply unit (PSU)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

There is only one type of PSU used in Horizon II micro, wide ranging 110 V to 240 V ac nominal(88 V to 270 V ac actual).

The PSUs are fed from a midplane connector and use pulse width modulation to generate outputsupply. A front panel switch shown in Figure 3-2 disables the output, reducing the input current.

There are several manufacturers of the PSU, each is fully compatible with the HorizonII micro.

PSU location and redundancy

Viewed from the front, the PSU is mounted in the left side, at the base of the Horizon II microenclosure.

There is only one PSU in a Horizon II micro enclosure, therefore power supply redundancy isnot supported.

68P02903W31-C 3-3

Aug 2007

Power supply unit (PSU) Chapter 3: Power distribution

PSU module view

Figure 3-2 shows a view of the PSU with LEDs identified.

Figure 3-2 PSU module view

3-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Power supply unit (PSU)

PSU alarms

In addition to the PSU front panel LEDs the following warnings are generated and signalledthrough the rear connector.

• Input Fail.

• Output Fail (SPDT).

• Over Temperature.

• Over Voltage.

• Fan Failure.

• Low voltage disconnect imminent (LVDI) alarm.

The PSU has internal double pole/neutral fusing, after the operation of a single fuse,parts of the equipment may remain energized.

When an alarm condition, other than LVDI or over-temperature, is detected the PSU output isinhibited until the output enable switch is cycled to reset the power supply unit. The likely causeof the alarm is indicated by a combination of the front panel LEDs (see Table 3-1).

The PSU has integral cooling fans and temperature monitoring and provides a separate overtemperature shut down, from the enclosure, in response to PSU internal over temperature(> +64 °C).

PSU LEDs

The front panel LEDs indicate the conditions shown in Table 3-1

Table 3-1 Indications of the front panel LEDs

Green LED (ACTIVE) Red LED (ALARM) Indication

OFF OFF• Power supply off.

• No power input to PSU.

ON OFF Normal operation.

OFF ON• PSU connected and output disabled.

• Alarm condition with PSU unable to supplypower.

ON ON Internal problem (such as over-temperature), butstill able to maintain supply.

68P02903W31-C 3-5

Aug 2007

Power supply unit (PSU) Chapter 3: Power distribution

PSU supply protection

If a power track to the PSU is broken or short-circuited, the PSU detects the fault and shutsdown to prevent further damage.

3-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II mini battery module

Horizon II mini battery module■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II mini battery module is an optional, hot swap capable unit that provides shortterm dc back up in the event of a supply failure or brown out. The duration of the useful batteryback up is dependant on the load and will vary from 18 to 20 minutes approximately.

In the event of a PSU failure the battery module will support a graceful shutdown ofthe site.

Removal of a faulty PSU will cause a site outage, since removal will disconnect thebattery supply to the enclosure.

The battery backup will not support a site long enough to allow the PSU to bereplaced.

It is recommended that following installation, the battery is allowed a commissioning charge of10 to 12 hours prior to discharge.

The battery module is shown in Figure 3-3.

68P02903W31-C 3-7

Aug 2007

Horizon II mini battery module Chapter 3: Power distribution

Figure 3-3 The Horizon II mini battery module

3-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II mini battery module

The Horizon II mini battery module features

The Horizon II mini battery module has the following features:

• Lead acid batteries charged directly from dc bus.

• Internal charge current limitation. Low voltage disconnect (LVD) and battery conditionmonitoring.

• Non regulated output, which may result in Tx power reduction on transition to back upbattery.

• Thermal charge compensation to improve low temperature performance.

• High temperature charge disable

• Alarms for Battery Condition; Battery Failure/Battery Off; Low voltage disconnectimminent.

• Charge current limited to 1 A.

In the event of a sustained high charge current, the battery will indicate a failcondition at the battery module LED and by generating a failure alarm. If the HorizonII mini optional battery module is NOT fitted, the original, battery connector shortingplug must be fitted or an LVDI alarm will be generated.

If there is a primary ac supply failure, the battery module will not generate an acfailure alarm. However, a PSU input fail alarm will still be generated.

The front panel switch must be set to ON to allow charge and discharge of the battery.

Do not allow the battery to remain in a discharged state for prolonged periods.

The battery is charged directly from the dc bus and will achieve approximately 90% full chargewithin 3 to 6 hours from a discharged state. It is recommended that following installation, thebattery is allowed a commissioning charge of 10 to 12 hours prior to discharge. The defaultcondition for the battery when not fitted or switched off is LVD disconnected. In this state,there is no drain on the battery and it is safe for transport or storage with its terminals keptaway from any power source.

68P02903W31-C 3-9

Aug 2007

Horizon II mini battery module Chapter 3: Power distribution

The Horizon II mini battery module front panel LED

The Horizon II mini battery module front panel is fitted with an LED to indicate operationalstatus, as detailed in Table 3-2:

Table 3-2 The Horizon II mini battery module front panel LED indications

LED color Indication

Green Status good

Amber Battery on charge

Red Battery failure or battery off

3-10 68P02903W31-C

Aug 2007

Chapter

4

RF modules■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter describes the functional operation of radio frequency (RF) modules used in theHorizon II micro. All descriptions are presented at a block diagram level.

68P02903W31-C 4-1

Aug 2007

RF equipment description Chapter 4: RF modules

RF equipment description■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following equipment is described:

• Compact transceiver unit (version 2) (CTU2). The CTU2 supports both the EGSM900and GSM1800 frequency bands.

• Compact transceiver unit 2 double density edge (CTU2D). The new CTU2D radios cansupport both SD and DD EDGE architectures, in addition to the various modes supportedby the legacy CTU2 radios.

• Miniature Sectorized universal receiver front-end module (Mini-SURF). Two versions of theMini-SURF are available for the Horizon II micro: one operates in the 900 MHz frequencyband and the other operates in the 1800 MHz frequency band.

• Duplexer transmit blocks (DUPs) or PGSM duplexer. These are used for variousconfigurations of transmit path, depending on number of antennas, frequency band andfunctionality, including potential shared receive path.

RF general information and VSWR monitoring function

The following additional information is also provided:

• General definition of transmit and receive functions.

• An RF overview and VSWR monitoring function description.

• A brief explanation of CTU2 frequency hopping.

These descriptions are intended to assist the reader in understanding the information on the RFmodules.

RF specications

All equipment meets or exceeds ETSI regulations.

Receive (Rx) RF hardware

Receiver RF hardware consists of the Mini-SURF module and the receive section of the CTU2.The DUP/PGSM duplexer is required for Rx filtering on the main (A) path and is optional forthe Rx diversity (B) path.

The Mini-SURF module provides bandpass filtering and low-noise amplification for up to twosectors, with two branch diversity receive antenna signals, together with switching to the CTU2.

4-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro RF equipment description

CTU2 Rx role

The CTU2 provides the following receive functions:

• Synthesised receiver tuning (on a timeslot basis) to any receive channel frequency.

• Demodulation and equalization of the receive channel signal.

• Measurement of the received signal strength indication (RSSI) and signal quality.

• Recovery of received voice/data from the demodulated radio channel.

• Channel decoding of the received voice/data and processing of the recovered signal. Trafficand signalling data is passed on to the site controller module for routing to the MSC.

• Digital interface to the Mini-SURF module, which controls selection by the Mini-SURFswitch of the receive signals from the appropriate antenna.

• Comparison and processing of an additional receive path from a second diversity antennainput to compensate for multipath fading and interference.

Transmit (Tx) RF hardware

Transmit RF hardware consists of a duplexer (DUP) or a PGSM duplexer and the transmitsection of the CTU2.

CTU2 Tx role

The CTU2 provides the following transmit functions:

• Synthesised transmit tuning (on a timeslot basis) for generation of any transmit channelRF frequency.

• Encoding transmit data output.

• Digital modulation of transmit data onto the transmit radio channel signal.

• Final RF power amplification and static/dynamic output power level control of the transmitradio channel RF signal.

• Channel encoding of the data to be transmitted, interleaving signal and traffic channeldata, as defined by ETSI.

68P02903W31-C 4-3

Aug 2007

RF equipment description Chapter 4: RF modules

Rx/Tx single antenna duplexing

Duplexers allow a single antenna to be used for both transmit and receive operations. Typically,duplexed RF signals pass through one antenna, with a second dedicated receive antennato provide diversity.

If a single antenna (non-diversity) is required, the duplex antenna RF receive cablefrom the transmit block must be connected to the Rx A path at the Mini-SURF. Simplyswitching off diversity at the OMC-R without the correct Mini-SURF congurationcauses a loss of reception.

The duplex antenna RF receive cable from the transmit block is connected to the Rx Apath as standard from the factory to allow single antenna (non-diversity) operation.

4-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro RF overview and antenna VSWR monitoring function

RF overview and antenna VSWR monitoring function■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section explains the RF functional blocks and additional antenna VSWR monitoring function.

The terminology, functionality, and optional capabilities, are set out as a basis for understandingmore detailed descriptions in the RF module sections of this chapter.

RF main components

The following description should be read in conjunction with

The RF equipment consists of three main components:

• The CTU2/CTU2D.

• The Mini-SURF.

• The duplexer (DUP).

CTU2

The CTU2 can be one of two variants, either 900 MHz or 1800 MHz. It can receive two (singledensity or EGPRS) Rx inputs from the Mini-SURF. These inputs are converted into digitalvoice/data. The CTU2 is capable of using Rx signal diversity from the MS (uplink). The CTU2generates a Tx data signal, translated from received digital voice/data, which is transmitted bycable to the Tx block for transmission through the antenna to the MS (downlink).

CTU2D

CTU2D support both SD and DD EDGE architectures, in addition to the various modes supportedby the legacy CTU2 radios. Similar to the CTU2, carrier A/B definitions and nomenclaturealso apply to CTU2D. The radio type CTU2D can be configured in different operating modes(single, double and capacity) within one cell.

Mini-SURF module

Two alternative types of Mini-SURF module are available for use in the Horizon II micro. Oneprovides 900 MHz reception capability and the other provides 1800 MHz reception capability.Each Mini-SURF module accepts up to two pairs of antenna inputs. The Mini-SURF switches theinputs to the appropriate CTU2s under the control of the database through the HIISC. Thereare two inputs to the CTU2 for Rx diversity. The Mini-SURF does not contain any loopback testcircuitry.

68P02903W31-C 4-5

Aug 2007

RF overview and antenna VSWR monitoring function Chapter 4: RF modules

Duplexer

Only one DUP or PGSM duplexer can be installed in the Horizon II micro enclosure. TheDuplexer filters the transmit signal for the required Tx band. It also uses bandpass filters toenable the Rx frequency signal to be passed to the Mini-SURF, if one antenna is used for both Txand Rx signals.

Antenna VSWR monitoring

The antenna VSWR monitoring function is used to detect faults in antennas or antenna pathconnections. This is achieved by sending a known signal power level to the antenna and thenmeasuring the reflected power.

The test signal for antenna VSWR monitoring is generated by the CTU2. The DUP/PGSMduplexer contains a VSWR monitoring circuit that monitors the reflected power. If the returnloss from the antenna port is less than 6 dB, a VSWR alarm signal is sent to the alarm module.

RF loopback

The loopback test function is primarily used to identify faults within the RF system. Theloopback test function provides a diagnostic capability at the OMC-R, by creating a test signal toidentify the source of the fault from the following:

• Software (that the OMC-R can correct).

• Hardware (requires a site visit).

The result is a reduction in site assessment visits, and avoidance of unnecessary visits whenhardware is functioning correctly.

Software operation

The loopback test function is normally carried out under the control of the OMC-R.

Hardware

The RF loopback test function is a hardware capability built into the CTU2. Software instructionsactivate the test hardware, causing an attenuated loopback signal from the transmitter to beinjected internally into the Rx input of the CTU2 to test its receive section.

4-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro RF overview and antenna VSWR monitoring function

RF functional diagram

Figure 4-1 RF functional diagram

ti-GSM-HII Micro RF function-00020-eps-sw

68P02903W31-C 4-7

Aug 2007

Compact transceiver unit 2 (CTU2) Chapter 4: RF modules

Compact transceiver unit 2 (CTU2)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides the technical description of the CTU2.

Two versions of the CTU2 are available for the Horizon II equipment. One versionoperates in the EGSM900 frequency band and the other operates in the GSM1800frequency band.

Horizon II equipment is defined as Horizon II macro, Horizon II mini and HorizonII micro hardware.

Overview of the CTU2

The CTU2:

• Generates the RF frequencies required to perform the transmit and receive functions.

• Contains the digital circuits required for 32 timeslots of channel equalization, encodingand decoding, and transceiver control logic.

The CTU2 provides the air interface between a BTS and MSs, with the following features:

• Capability of diversity reception (input from up to four antennas) which improves thequality reception in the presence of multipath fading and interference.

• Frequency change on a timeslot basis for frequency hopping and equipment sharing.

• Static or dynamic transmit power control.

CTU2 features

The CTU2 has the following features:

• Single or double density mode in Horizon II equipment cabinets. Single density modeprovides single carrier GSM Tx capability. Double density mode provides 2 carrier GSMTx capability (both carriers must be in the same sector).

• Single carrier EGPRS Tx and Rx capability.

• Backwards compatibility with CTU used in Horizonmacro indoor (with restrictions).

• Two or four branch Rx diversity. (Four branch diversity, available in Horizon II macroordered configurations only, requires 2 x SURF2 modules and a second SURF2 harnesscable to be installed. Four branch diversity is not retrofittable in the field).

• Hardware support for Adaptive Multirate (AMR) (upgrade required for pre-GSR7 software).

4-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact transceiver unit 2 (CTU2)

CTU2 Tx RF output specication

For Tx RF output refer to Electrical and RF specifications in this manual.

Location and requirements

The CTU2 shelf is located below the basket for the Tx blocks in Horizon II macro, at the topfront of the Horizon II mini cabinet and at the top rear of the left side of the Horizon II microenclosure. This takes up the majority of the space in all types of cabinet.

A Horizon II macro cabinet can contain up to six CTU2s, a Horizon II mini cabinet up to two anda Horizon II micro enclosure, only one. At least one CTU2 must be fitted in each cabinet. AllCTU2s in these cabinets must operate in the same frequency band (either 900 MHz or 1800MHz). A Horizon II micro enclosure contains only one CTU2.

CTU2 internal boards

The CTU2 is considered a single field replaceable unit (FRU), which contains:

• CTU2 transceiver (XCVR) board.

• Power amplifier (PA) board.

• Power supply unit.

68P02903W31-C 4-9

Aug 2007

Compact transceiver unit 2 (CTU2) Chapter 4: RF modules

View of a CTU2

Figure 4-2 shows the CTU2 with main features identified.

Figure 4-2 View of a CTU2

Rx A (main branch) and Rx B (diversity branch) are the only Rx connectors used ina cabinet using two branch Rx diversity, that is Horizon II micro, Horizon II mini orHorizon II macro containing a single SURF2.

Rx C (branch 3) and Rx D (branch 4) are only used in Horizon II macro when a secondSURF2 is installed in the cabinet to provide four branch Rx diversity.

4-10 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact transceiver unit 2 (CTU2)

CTU2 front panel detail

Figure 4-3 shows the CTU2 front panel and Table 4-1 lists connector functions.

Figure 4-3 CTU2 front panel

68P02903W31-C 4-11

Aug 2007

Compact transceiver unit 2 (CTU2) Chapter 4: RF modules

The CTU2 does not have a reset button. A reset is achieved by cycling the power:

• In Horizon II macro using the appropriate CTU2 circuit breaker on the CBC.

• In Horizon II mini using the appropriate CTU2 circuit breaker on the MCBM.

• In Horizon II micro by cycling the PSU.

CTU2 front panel connectors

Table 4-1 lists CTU2 the front panel connectors:

Table 4-1 CTU2 front panel connectors

Front panel legend Function Connection to

TRANSMIT OUT Transmitter RF output Tx block

CONTROL PROCESSOR Test access to processor Three RS-232s

TEST INTERFACE Factory use Test equipment

VCAT INTERFACE Motorola Field Engineer use Test equipment

In Horizon II macro the CTU2 Tx connection is a short SMA to SMA cable to the base of theappropriate Tx block or feed-through plate. In Horizon II mini and Horizon II micro the CTU2 Txconnection is either a long cable to the SMA connector on the back of the DUP/PGSM duplexeror, in Horizon II mini only, a short cable to one of the N-type connectors of the CMB with longercables connecting the CMB to the duplexer.

The Tx cables have a 90° SMA connector at one end and a straight SMA connector atthe other end. The 90° end is designed for connection to the Tx port of the CTU2.

The TTY RS-232 serial port has three serial links onto the 9-way connector:

• Radio subsystem (RSS).

• Equalizer and control processor (EQCP).

• Channel coder control processor (CCCP).

A test interface port on the CTU2 front panel provides access to critical test points for factorycalibration and maintenance.

The VCAT interface port on the CTU2 front panel also provides access to critical test points forfactory calibration and maintenance.

4-12 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact transceiver unit 2 (CTU2)

Alarm reporting

The CTU2 status is displayed by LED indicators on the front panel, as shown in Figure 4-3, onpage 4-11, and detailed in Table 4-2. Major sub-systems, such as synthesizers and RF amplifiers,are monitored and generate alarm signal for display at the OMC-R.

Table 4-2 CTU2 front panel status indicators

LED Status Meaning

Unlit CTU2 is off.

Flashing green Boot code being loaded.(Do not remove power or reset -see CAUTION below.)

The flashing green status can alsoindicate that the device is locked.

Green Normal operational mode.

Flashing yellow Test mode.

Yellow Transceiver inhibited.

Red Alarm condition.

RADIO STATUS

Alternately flashing redand green

Flash reprogramming in progress.(Do not remove power or reset - seeCAUTION below.)

Unlit Transmitter A is off.TRANSMIT (Tx)STATUS A

Yellow Transmitter A is keyed on.

Unlit Transmitter B is off.TRANSMIT (Tx)STATUS B

Yellow Transmitter B is keyed on.

Removing power or resetting the cabinet while the boot code is downloading or ashreprogramming is taking place will cause memory corruption.

If the boot code is corrupted, contact Motorola Customer Network Resolution Centrerequesting the boot code restoration procedure and the appropriate boot code le.

68P02903W31-C 4-13

Aug 2007

Compact transceiver unit 2 (CTU2) Chapter 4: RF modules

CTU2 Rx function

The receiver part of the CTU2 can accept two amplified and filtered receive antenna signalsfrom each SURF2 or Mini-SURF module (up to four Rx signals in total). These signals areapplied to inputs (branch A and branch B) of the CTU2 transceiver board.

The transceiver can be configured to provide double density receive capacity or 4 branch Rxdiversity (in Horizon II macro only). In double density mode, the receiver provides demodulationof a main and diversity path for each of two RF channels. In 4 branch Rx diversity mode, thereceiver provides four independent Rx paths for one RF channel.

The input from the SURF2 or Mini-SURF module is filtered, amplified and down converted toensure the signal level and frequency range are correct for the next stage.

CTU2 interface function

The CTU2 interface function provides the air interface timing and transceiver control circuitryrequired for Rx (uplink) and Tx (downlink) control functions.

The CTU2 interface includes:

• Master GSM air interface timing function.

• Independent Rx gain control interface for each diversity receiver branch.

• Baseband Rx data interface for each diversity receiver branch.

• Receiver front end control.

• Tx data interface including GMSK modulator which provides baseband data to thetransmitter.

• Tx and power amplifier power control interface.

• Rx and Tx frequency synthesizer control which supports RF frequency hopping.

• CTU2 and cabinet alarm data collection.

• Alarms sampling and multiplexing.

CTU2 frequency hopping

The CTU2 supports two types of frequency hopping, synthesizer frequency hopping (SFH)and baseband frequency hopping (BBH). This section provides an explanation of both types.In either type, the BTS and MS switch channels after every transmit/receive (Tx/Rx) burstpair. The difference between SFH and BBH is in the method by which channel switching isachieved at the BTS.

4-14 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact transceiver unit 2 (CTU2)

BBH is not possible if the CTU2 is used in double density mode in a Horizonmacrocabinet which is controlled by a MCUF site controller (refer to System Information:BSS Equipment Planning (68P02900W21) for further details).

Synthesized frequency hopping (SFH)

SFH is achieved by changing the frequency of each BTS carrier for successive timeslots,under control of a predetermined algorithm. The BCCH frequency must be constant and mustbe transmitted on all eight timeslots. A minimum of two carriers is therefore required forSFH since for every timeslot, one carrier must transmit the BCCH frequency. The minimumconfiguration of two carriers allows the full range of hopping frequencies to be deployed on oneof the two carriers. Uplink hopping is achieved in a similar manner by tuning each receiver to adifferent frequency for each timeslot (channel). SFH can be used only with hybrid (wide band)combining, or with a direct antenna connection to the transmitter(s).

Baseband frequency hopping (BBH)

BBH is achieved by switching successive downlink timeslots between different transmitters atthe BTS, under control of a predetermined algorithm. Each carrier is generated at a constant,but different, frequency. The number of frequencies available for hopping is therefore equal tothe number of carriers used by the BTS. BBH cannot be used by BTSs with only a single carrier,since only a single transmit frequency is available. Uplink hopping is achieved in a similarmanner by switching timeslots (channels) between different receivers, each of which receivesat a constant, but different, frequency. Since each downlink carrier is transmitted at constantfrequency, BBH can be used with narrow band combiners – for example, RTCs.

68P02903W31-C 4-15

Aug 2007

Compact Transceiver Unit 2 Double Density Edge (CTU2D) Chapter 4: RF modules

Compact Transceiver Unit 2 Double Density Edge(CTU2D)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides the technical description of the CTU2D. The radio type CTU2D can beconfigured in different operating modes (single, double and capacity) within one cell.

CTU2D is supported on Horizon II macro, Horizon II mini and Horizon II micro sitesonly. When the master cabinets are Horizon II macro, Horizon II mini and Horizon IImicro, the extension Horizon II cabinets support CTU2D; legacy MCell and Horizonextension cabinets do not support CTU2D and remain OOS.

Overview of the CTU2D

The new CTU2D radios can support both SD and DD EDGE architectures, in addition to thevarious modes supported by the legacy CTU2 radios. Similar to the CTU2, carrier A/B definitionsand nomenclature also apply to CTU2D. The following are the different edge modes that theCTU2D radio supports:

• CTU2D SD: This mode is identical in operation to the existing CTU2 SD and is includedfor reference only.

• CTU2D PWR: This mode is also known as ITS Mode whereby the CTU2 and CTU2Doperations are identical. Of the two carriers, if the TS on carrier A is supporting anEDGE TS, then the corresponding TS on carrier B is blanked. Carrier B TS is capable ofsupporting only TCH or GPRS PDs while the corresponding TS on carrier A does nothave an EDGE TS.

• CTU2D CAP: Of the two carriers, carrier A is fully EDGE-capable, while carrier B supportsGPRS/TCH. TS blanking is not required. The maximum output power of carrier A in 8PSKmode is 10 W* and GMSK mode is 20 W*.

* The output powers listed are for 900 MHz frequency. For all other frequencies, theoutput power may vary.

4-16 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact Transceiver Unit 2 Double Density Edge (CTU2D)

CTU2D features

The CTU2D has the following features:

• Single or double density mode in Horizon II equipment cabinets. Single density modeprovides single carrier GSM Tx capability. Double density mode provides 2 carrier GSMTx capability (both carriers must be in the same sector). Double density edge removesneed for ITS blanking.

• Single carrier EGPRS Tx and Rx capability.

• Two or four branch Rx diversity. Four branch diversity, available in Horizon II macroordered configurations only, requires 2 x SURF2 modules and a second SURF2 harnesscable to be installed. Four branch diversity is not retrofittable in the field.

CTU2D Tx RF output specication

For Tx RF output refer to Electrical and RF specifications in this manual.

The CTU2D maintains the same output power figures as CTU2, but with a -0/+2 dBtolerance at mid-band in room temperature and -0/+2.5 dB tolerance applies for allchannels at extreme conditions.

CTU2D internal boards

The CTU2D is considered a single Field Replaceable Unit (FRU), which contains:

• CTU2D transceiver (XCVR) board.

• Power Amplifier (PA) board.

• Power supply unit.

68P02903W31-C 4-17

Aug 2007

Compact Transceiver Unit 2 Double Density Edge (CTU2D) Chapter 4: RF modules

View of a CTU2D

Figure 4-4 shows the CTU2D with main components identified.

Figure 4-4 View of a CTU2D

4-18 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact Transceiver Unit 2 Double Density Edge (CTU2D)

CTU2D front panel detail

Figure 4-5 shows the CTU2D front panel and Table 4-3 lists connector functions.

Figure 4-5 CTU2D front panel

The CTU2D does not have a reset button. A reset is achieved by cycling the power:

• In Horizon II macro, using the appropriate CTU2D circuit breaker on the CBC.

• In Horizon II mini, using the appropriate CTU2D circuit breaker on the MCBM.

• In Horizon II micro, by cycling the PSU.

68P02903W31-C 4-19

Aug 2007

Compact Transceiver Unit 2 Double Density Edge (CTU2D) Chapter 4: RF modules

CTU2D front panel connectors

Table 4-3 lists the CTU2D front panel connectors.

Table 4-3 CTU2D front panel connectors

Front panel legend Function Connection to

TRANSMIT OUT Transmitter RF output Tx block

CONTROL PROCESSOR Test access to processor Three RS-232s

TEST INTERFACE Factory use Test equipment

VCAT INTERFACE Motorola Field Engineer use Test equipment

In Horizon II macro the CTU2D Tx connection is a short SMA to SMA cable to the base of theappropriate Tx block or feedthrough plate. In Horizon II mini the CTU2D Tx connection is eithera long cable to the SMA connector on the back of the DUP/PGSM duplexer or a short cable toone of the N-type connectors of the CMB with longer cables connecting the CMB to the DUP.

The Tx cables have a 90° SMA connector at one end and a straight SMA connector atthe other end. The 90° end is designed for connection to the Tx port of the CTU2D.

The TTY RS-232 serial port has three serial links onto the 9-way connector:

• Radio subsystem (RSS).

• Equalizer and control processor (EQCP).

• Channel coder control processor (CCCP).

A test interface port on the CTU2D front panel provides access to critical test points for factorycalibration and maintenance.

The VCAT interface port on the CTU2D front panel also provides access to critical test points forfactory calibration and maintenance.

4-20 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact Transceiver Unit 2 Double Density Edge (CTU2D)

Alarm reporting

The CTU2D status is displayed by LED indicators on the front panel, as shown in Figure 4-5, anddetailed in Table 4-4. Major sub-systems, such as synthesizers and RF amplifiers, are monitoredand generate alarm signal for display at the OMC-R.

Table 4-4 CTU2D front panel status indicators

LED Status Meaning

Unlit CTU2D is off.

Flashing green Boot code being loaded.(Do not remove power orreset - see CAUTION below).

The flashing greenstatus can alsoindicate that thedevice is locked.

Green Normal operational mode.

Flashing yellow Test mode.

Yellow Transceiver inhibited.

Red Alarm condition.

RADIO STATUS

Alternately flashing red andgreen

Flash reprogramming inprogress.(Do not removepower or reset - see CAUTIONbelow).

Unlit Transmitter A is off.TRANSMIT (Tx) STATUS A

Yellow Transmitter A is keyed on.

Unlit Transmitter B is off.TRANSMIT (Tx) STATUS B

Yellow Transmitter B is keyed on.

• Removing power or resetting the cabinet while the boot code is downloading orash reprogramming is taking place will cause memory corruption.

• If the boot code is corrupted, contact Motorola Customer Network ResolutionCentre requesting the boot code restoration procedure and the appropriate bootcode le.

68P02903W31-C 4-21

Aug 2007

Compact Transceiver Unit 2 Double Density Edge (CTU2D) Chapter 4: RF modules

CTU2D Rx function

The receiver part of the CTU2D can accept two amplified and filtered receive antenna signalsfrom each SURF2 or Mini-SURF module (up to four Rx signals in total). These signals areapplied to inputs (branch A and branch B) of the CTU2D transceiver board.

The transceiver can be configured to provide double density receive capacity or 4 branch Rxdiversity (in Horizon II macro only). In double density mode, the receiver provides demodulationof a main and diversity path for each of two RF channels. In 4 branch Rx diversity mode, thereceiver provides four independent Rx paths for one RF channel.

The input from the SURF2 or Mini-SURF module is filtered, amplified and down converted toensure the signal level and frequency range are correct for the next stage.

4-22 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Compact Transceiver Unit 2 Double Density Edge (CTU2D)

CTU2D interface function

The CTU2D interface function provides the air interface timing and transceiver control circuitryrequired for Rx (uplink) and Tx (downlink) control functions.

The CTU2D interface includes:

• Master GSM air interface timing function.

• Independent Rx gain control interface for each diversity receiver branch.

• Baseband Rx data interface for each diversity receiver branch.

• Receiver front end control.

• Tx data interface including GMSK modulator which provides baseband data to thetransmitter.

• Tx and power amplifier power control interface.

• Rx and Tx frequency synthesizer control which supports RF frequency hopping.

• CTU2D and cabinet alarm data collection.

• Alarms sampling and multiplexing.

CTU2D frequency hopping

The CTU2D supports two types of frequency hopping, Synthesizer Frequency Hopping (SFH)and BaseBand frequency Hopping (BBH). In either type, the BTS and MS switch channelsafter every transmit/receive (Tx/Rx) burst pair. The difference between SFH and BBH is in themethod by which channel switching is achieved at the BTS.

BBH for edge capable RTFs is not supported when CTU2D is configured in capacitymode.

Synthesized frequency hopping

SFH is achieved by changing the frequency of each BTS carrier for successive timeslots, underthe control of a predetermined algorithm. The BCCH frequency must be constant and mustbe transmitted on all eight timeslots. A minimum of two carriers is therefore required forSFH since for every timeslot, one carrier must transmit the BCCH frequency. The minimumconfiguration of two carriers allows the full range of hopping frequencies to be deployed on oneof the two carriers. Uplink hopping is achieved in a similar manner by tuning each receiver to adifferent frequency for each timeslot (channel). SFH can be used only with hybrid (wide band)combining, or with a direct antenna connection to the transmitter(s).

68P02903W31-C 4-23

Aug 2007

Compact Transceiver Unit 2 Double Density Edge (CTU2D) Chapter 4: RF modules

Baseband frequency hopping

BBH is achieved by switching successive downlink timeslots between different transmittersat the BTS, under the control of a predetermined algorithm. Each carrier is generated at aconstant, but different, frequency. The number of frequencies available for hopping is thereforeequal to the number of carriers used by the BTS. BBH cannot be used by BTSs with only a singlecarrier, since only a single transmit frequency is available. Uplink hopping is achieved in asimilar manner by switching timeslots (channels) between different receivers, each of whichreceives at a constant, but different, frequency. Since each downlink carrier is transmitted atconstant frequency, BBH can be used with narrow band combiners, for example, RTCs.

4-24 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Mini-SURF module

Mini-SURF module■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The miniature sectorized universal receiver front end (Mini-SURF) module performs low noiseamplification, RF bandpass filtering, and antenna to CTU2 routing through a switch/splittermatrix. In Horizon II mini one Mini-SURF can route any of two Rx antenna inputs to either oftwo different CTU2s for both a main and diversity path.

The Mini-SURF is single band and two alternative versions are available for use in the Horizon IImini cabinet or the Horizon II micro enclosure:

• 900 MHz, for EGSM900 systems.

• 1800 MHz, for GSM1800 systems.

Only one Mini-SURF module may be installed in either Horizon II mini or Horizon II micro. TheMini-SURF module is located in a slot, at the rear of a Horizon II mini cabinet, or located atthe lower front of the right side of Horizon II micro enclosure. A connector on the underside ofthe module connects to the mini-SURF harness which provide connectivity to the midplane andthrough this to the CTU2. Antenna connections are located on the rear face of the unit.

Dual band operation in a single Horizon II mini cabinet is not supported.

68P02903W31-C 4-25

Aug 2007

Mini-SURF module Chapter 4: RF modules

Mini-SURF module view

Figure 4-6 shows a view of the Mini-SURF module with features identified.

Figure 4-6 Mini-SURF module with features identied

4-26 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Mini-SURF module

Mini-SURF functional description

The Mini-SURF module provides front end filtering, amplification, and matrix control of theRF receive signal between the antenna and the CTU2. It has two antenna pair connectionsproviding diversity reception.

The Mini-SURF functional sections (Figure 4-7) consist of filtering, amplification, splitting,switching and digital control.

The Mini-SURF does not support loopback mode.

Each section is duplicated for the second diversity path except for the digital and dc powersection which is shared by the two diversity paths. There are two antenna pair inputs (ANT0 and ANT 1) for each of the two diversity branches (Branch A and Branch B). There are twooutputs to the CTU2 for each of the two diversity branches.

Digital codes are transmitted from the CTU2 to the digital section. The digital codes aredissimilar in order that a CTU2 programmed for the 900 MHz or 1800 MHz frequency bands canbe recognized and appropriate switching can be made to the required antenna for transmissionand reception.

The digital and power supply section is also responsible for manual overrides, alarms and dcvoltages.

Mini-SURF functional diagram

Figure 4-7 shows a functional diagram of the Mini-SURF module.

Figure 4-7 Mini-SURF functional diagram

ti-GSM-HorizonII Mini W21-00043-eps-sw

68P02903W31-C 4-27

Aug 2007

Mini-SURF module Chapter 4: RF modules

Alarms

The alarm signal from the Mini-SURF is active low (0 V) and is multiplexed onto the branch 1 RFconnection. An alarm generated at an individual CTU2 is caused by an unexpected number ofantenna select pulses being read. An alarm generated at a CTU2 connected to the Mini-SURF iscaused by one of the amplifiers drawing too much or too little current.

Mini-SURF to CTU2 interface

This section describes two carrier, two branch receive diversity in Horizon II mini or Horizon IImicro, (four branch diversity is not supported).

Interface description - 2 carrier, 2-branch Rx diversity

The physical interface between the Mini-SURF and the CTU2 consists of two connections, onebi-directional and the other directional. The bi-directional connection is for the RF receive mainbranch (branch 1) and for digital communication between the Mini-SURF and the CTU2. Thedirectional connection is for the RF receive diversity branch (branch 2) only.

4-28 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Mini-SURF module

Interface block diagram

Figure 4-8 shows the interconnections between the Mini-SURF and the CTU2, for 2-branch Rxdiversity (double density).

Figure 4-8 Mini-SURF to CTU2 connections (2 diversity)

ti-GSM-HII Micro Surf 2CTU2-00021-eps-sw

Rx A on the CTU2 carries the Mini-SURF control and alarm signals.

The 6-pin connector on the base of the Mini-SURFs carries 4 x RF signals plus 1earth and 1 power.

68P02903W31-C 4-29

Aug 2007

Tx blocks overview Chapter 4: RF modules

Tx blocks overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

There are three types of internal Tx blocks:

• DUP = Duplexer.

900 MHz.

1800 MHz.

• PGSM duplexer.

Tx block connectors

The transmit block connections are listed in Table 4-5:

Table 4-5 Tx block connectors

Tx block Input connector Output connector

DUP 1 x SMA 1 x 7/16 Tx/Rx to antenna1 x N-type to mini SURF

PGSM duplexer 1 x SMA 1 x 7/16 Tx/Rx to antenna1 x N-type to mini SURF

4-30 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Duplexer (DUP)

Duplexer (DUP)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The purpose of the DUP is to enable an antenna to serve Tx and Rx paths. This is achieved bythe use of bandpass filters within the duplexer.

The DUP also contains a VSWR monitor that can detect and generate alarms for transmitantenna systems with a VSWR of 3:1 or worse.

Duplexer Location

In the Horizon II macro BTS, duplexers are located in the basket above the CTU2s, and isattached to the top panel using two M4 screws.

In the Horizon II mini BTS, duplexers are located in the shelf behind the CTU2s, and is attachedto the chassis using two M4 screws.

In the Horizon II micro BTS, the duplexer is located in secondary cage behind the CTU2, and isattached to the chassis using two M4 screws.

68P02903W31-C 4-31

Aug 2007

Duplexer (DUP) Chapter 4: RF modules

DUP view

Figure 4-9 Duplexer with connectors identied

4-32 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Duplexer (DUP)

DUP functional diagram

Figure 4-10 shows a functional diagram of the DUP.

Figure 4-10 DUP functional diagram

DUP connectors

Each DUP connects to:

• The Tx output from a CTU2, using an SMA connector. The connector is underneath the DUP.

• One antenna, for both Rx and Tx, using a 7/16 connector. This connector is on top ofthe DUP.

• The SURF2 or Mini-SURF, using one N-type connector. This connector is on top of the DUP.

68P02903W31-C 4-33

Aug 2007

PGSM duplexer Chapter 4: RF modules

PGSM duplexer■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The PGSM duplexer is used to block signals from collocated CDMA networks.

It is similar to the DUP, but provides a high level of rejection up to the bottom end of the PrimaryGSM (PGSM) receive band, preventing the BTS from operating on the Extended GSM (EGSM)channels.

The PGSM duplexer contains a VSWR monitor that can detect and generate alarms for transmitantennas with a VSWR of 3:1 or worse.

There are two variants of the PGSM duplexer, the Motorola version and a Filtronic version. TheMotorola PGSM duplexer is identical to the DUP, the Filtronic version is approximately 35mm taller.

Duplexer Location

In the Horizon II macro BTS, duplexers are located in the basket above the CTU2s, and isattached to the top panel using two M4 screws.

In the Horizon II mini BTS, duplexers are located in the shelf behind the CTU2s, and is attachedto the chassis using two M4 screws.

In the Horizon II micro BTS, the duplexer is located in secondary cage behind the CTU2, and isattached to the chassis using two M4 screws.

PGSM duplexer view

Figure 4-11 and Figure 4-12 show views of the types of PGSM duplexer with connectorsidentified.

The Filtronic PGSM duplexer is taller than the Motorola version, and when fittedprotrudes approximately 35 mm from the slot.

4-34 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro PGSM duplexer

Figure 4-11 Motorola PGSM duplexer with connectors identied

68P02903W31-C 4-35

Aug 2007

PGSM duplexer Chapter 4: RF modules

Figure 4-12 Filtronic PGSM duplexer with connectors identied

4-36 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro PGSM duplexer

PGSM duplexer functional diagram

Figure 4-13 shows a functional diagram of the PGSM duplexer.

Figure 4-13 PGSM duplexer functional diagram

PGSM duplexer connectors

Each PGSM duplexer connects to:

• The Tx output from a CTU2, using an SMA connector. The connector is underneath thePGSM duplexer.

• One antenna, for both Rx and Tx, using a 7/16 connector. This connector is on top ofthe PGSM duplexer.

• The SURF2 or Mini-SURF, using one N-type connector. This connector is on top of thePGSM duplexer.

68P02903W31-C 4-37

Aug 2007

PGSM duplexer Chapter 4: RF modules

4-38 68P02903W31-C

Aug 2007

Chapter

5

Digital modules■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter describes the functional operation of digital modules used in the Horizon II micro.All descriptions are presented at a block diagram level.

68P02903W31-C 5-1

Aug 2007

Overview of digital modules Chapter 5: Digital modules

Overview of digital modules■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The digital modules contained in the Horizon II micro cabinet are as follows:

• Site controller unit (HIISC).

The HIISC provides the processing power, interfacing, and expansion capability for theBTS.

• Expansion multiplexer (XMUX) module (optional).

The XMUX replaces the HIISC in expansion enclosures, where it connects to the HIISCin the master cabinet through the site expansion board.

• Site expansion board (optional).

The site expansion board provides the control interface and physical link connectionsbetween the master and expansion units through fiber optic connectors. The board isonly fitted if site expansion is required and must be fitted in both the master unit andall expansion units.

• Alarm module.

The alarm module provides all the monitoring and reporting facilities required for site andcustomer alarms. An alarm module is required in all units, whether master or expansion.

5-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Overview of digital modules

Digital module locations

Figure 5-1 shows the position of the digital modules in the Horizon II micro enclosure.

Site expansion boards are required only when expansion cabinets are used.

Figure 5-1 Digital module locations

Redundancy

In Horizon II micro, digital module redundancy is not supported.

68P02903W31-C 5-3

Aug 2007

Overview of digital modules Chapter 5: Digital modules

Communication between the HIISC and transceivers

The HIISC is connected to the CTU2 in the same enclosure through the enclosure midplane.

Where an additional slave unit is used, the data streams for up to six transceivers aremultiplexed onto a single line by the internal XMUX in the HIISC and then transmitted to thesite expansion board. fiber optic transceivers on the site expansion board convert the TTLsignals for transmission to the site expansion boards in the slave units through fiber opticcables. The receiving expansion board converts the data stream back to TTL signals before it isforwarded to the XMUX for demultiplexing. The individual data streams are then distributed tothe appropriate transceivers. Figure 5-2 shows the communication path in block diagram form.

Figure 5-2 HIISC to transceiver communication path

5-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Overview of digital modules

If the master BTS is a Horizonmacro, a Horizon II macro, or an M-Cell6 and the slaveBTS is a Horizon II mini or Horizon II micro, then a standby link alarm will always begenerated for the Horizon II mini or Horizon II micro. This alarm is due to the HorizonII mini or Horizon II micro not supporting link redundancy, and may be ignored.

68P02903W31-C 5-5

Aug 2007

Horizon II site controller (HIISC) Chapter 5: Digital modules

Horizon II site controller (HIISC)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The HIISC in Horizon II equipment provides all the site processing functions (except for theCTU2 RF functions). The functionality of the separate, legacy MCUF, NIU, FMUX, and BPSMmodules in the Horizonmacro cabinet are all integrated within the HIISC.

Each site and module has an electronic ID for remote identification.

Although the HIISC provides the equivalent functionality of the MCUF inHorizonmacro, it is NOT backwards compatible and cannot be used in a Horizonmacrocabinet.

The main features of the HIISC are as follows:

• Processors for software and NIU functionality.

• Programmable timeslot interchanger (TSI) that supports the following:

TDM links for single (legacy) and double density GSM and single density EGPRS.

Three expansion links (FMUX equivalent). These links can connect to additionalHorizon II equipment (with double density GSM or single density EGPRS transceivers)or legacy Horizonmacro cabinets (with single/double density GSM or single densityEGPRS transceivers).

BBH routing for GSM/GPRS (single or double density) or EGPRS transceivers.

• Six integrated backhaul span line interfaces. (When available, an upgrade for the T43/BIBwill support eight backhaul spans on later equipment).

• Programmable synchronization/timing block for support of multiple air interfaces. A GPSinterface is included to support Compact EGPRS and other air interfaces that requireinter-site synchronization.

HIISC module view

Figure 5-3 shows a HIISC module.

5-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II site controller (HIISC)

Figure 5-3 View of the HIISC

Link to redundant HIISC (Horizon II macro only)

The link to the redundant HIISC is similar to a transceiver link, but does not have the BBHcapability, or the link delay measurement and compensation facility. The 6.12 s and 60 ms,signals are inserted into timeslots 8 and 16.

When the HIISC is in slave mode, timeslot and backhaul clock information is extracted fromthe HIISC link and passed to the sync block.

The main processor HDLC link to the redundant HIISC can be routed in any unused timeslot(s)of this link.

68P02903W31-C 5-7

Aug 2007

Horizon II site controller (HIISC) Chapter 5: Digital modules

The ASIC can switch any timeslot on the redundancy link to any timeslot on any of the other linksconnected to it such as the transceiver links, network links, redundancy link or processor links.

Front panel interfaces

The following interface connections are located on the HIISC front panel:

• Compact flash card interface

The compact flash card slot is located on the front panel of the HIISC, and is used for:

Code Storage Facility Processor (CSFP) memory.

Rapid site initialization.

The 32 Mbyte card can be write enabled for upgrade of site information, or disabled toprotect card use for other sites or secure the site code.

• TTY MMI interface

A standard TTY interface is provided on the front panel, of 9.6 kbit/s (8 bits, no parity, 1stop bit (8 N 1)). A local maintenance terminal can be attached to this port to use theMMI (Man Machine Interface) of the HIISC.

• CAL port

The CAL port on the front panel of the HIISC can be used to calibrate the sync block clockthrough MMI commands. The 8 kHz reference output is used in the GCLK calibrationprocedure (see chapter on FRU replacement procedures, later in this manual).

• NIU ethernet port and SYNC/NIU TTY port

These ports are for Motorola test purposes only.

Front panel switches and indicators

The front panel of the HIISC has two reset switches as shown in Figure 5-3 View of the HIISC onpage 5-7:

• FULL is a hard reset (power up - removes software from the memory).

• CPU is a soft reset (this resets the HIISC main processors, but the software remainsin RAM).

A hard reset results in the software being reloaded to the DRAM in the same way as normalpower up.

During the CPU (soft) reset, pressing CPU reset again causes a hard reset. Pressingthe CPU reset button twice thus has the same effect as a hard reset.

5-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II site controller (HIISC)

The HIISC has two front panel LEDs (one green and one red) as shown in Figure 5-3 View of theHIISC on page 5-7, with indications listed in Table 5-1.

Table 5-1 HIISC front panel LED indication

Red Green Status

Off Off Board not powered up or in reset cycle.

Off On Normal operation.

On Off Fault condition.

Flashing Flashing Non-volatile memory boot code upgrade.(Do not remove power or reset - see CAUTION).

When red and green LEDs are ashing, the boot code is downloading into non-volatilememory for software upgrade. Do not remove power or reset the cabinet untildownloading has been completed, as this will corrupt the non-volatile memory. Ifboot code is corrupted, contact the Motorola Customer Network Resolution Centre,requesting the boot code restoration procedure and the appropriate boot code le.

PIX output interfaces

The HIISC provides a serial interface for the PIX outputs. These are routed to the cabinet alarmboard and enable relay contact control of external customer equipment.

If the high power external fan option is fitted to the unit then the PIX output D-typeconnector must be terminated with the supplied dongle.

68P02903W31-C 5-9

Aug 2007

Horizon II site controller (HIISC) Chapter 5: Digital modules

SDRAM, ash EPROM

The HIISC has the following memory:

• SDRAM

The 32 MByte SDRAM provides operational code and data storage for the main processors.

• Flash EPROM

The 8 MByte flash EPROM has the following functions:

Storing boot code and executive process code. It has a fast access time (< 75 ns),enabling direct execution. The boot code is factory set, and reprogrammed only inmajor software upgrades.

Non-volatile data storage of diagnostic data and module ID information.

Code loading functions

The HIISC performs the following code loading functions:

• Code loading

The boot and executive code held in the flash EPROM initiates the HIISC on power up orreset. If a compact flash card is fitted, operational code may be obtained from it andcopied to the SDRAM for execution. If no card or code is available, the operational code isobtained from the BSC.

Before execution, the operational code held in SDRAM is checked with code held at theBSC. The BSC downloads any changed code objects to the SDRAM.

After successful checking of the SDRAM operational code, the code is executed and thecompact flash card is updated with any changed objects.

• CSFP code loading

If a compact flash card is available, then a code storage facility processor (CSFP) functioncan be supported. A new software load can be downloaded in the background, without anyreduction in service, and stored on the compact flash card.

Once the complete load has been transferred to the compact flash card, a code swap canbe initiated. The site is reset and the new software brought into service (< 10 minutes). Asa precaution, the old version is held on the compact flash card to support a roll back tothe original version if required.

5-10 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II site controller (HIISC)

HIISC internal architecture

This section describes the internal connections and individual elements of the HIISC, relating tosite control. Figure 5-4 shows the internal architecture of the HIISC.

Figure 5-4 HIISC internal architecture

LIU and framers

Dual mode backhaul LIU and framers are used, thus permitting the soft selection of E1 spanline connections.

The LIU/framer bridges between the internal 32 timeslot 2048 kbit/s TDM highway and theexternal E1 2048 kbit/s TDM formats.

Timing extraction: A 2048/1544 kHz frequency reference and a 125 ms timing referenceis extracted by the framer/LIU from each span. This unit also performs jitter and wanderattenuation.

Each of the extracted references are fed into a switch that is under site control processorsupervision. This is used to select the reference used for phase locking the SYNC function.

68P02903W31-C 5-11

Aug 2007

Horizon II site controller (HIISC) Chapter 5: Digital modules

Timeslot interchanger (TSI)

The TSI is controlled by the site control processor (the NIU control processor is not equippedwith a TSI control interface). A 64 kbit/s timeslot switch is responsible (within the context ofbackhaul and RSL requirements) for switching the following:

• Timeslots containing TRAU between the CTU2s and NIU framer / LIU.

• Timeslots containing RSL traffic between the NIU framer / LIU and NIU control processor.

• Timeslots containing NIU control messages and RSL traffic stripped of LAPD between theNIU control processor and the site control processor.

• Inserting 16 kbit/s RSL links into a bit-pair of a designated timeslot.

The use of the TSI in this fashion allows a RSL to be placed into any timeslot (other than timeslot0 in E1 systems) on any of the 6 spans. The design provides complete flexibility in the numberof timeslots on any span that can be used for RSL traffic. Indeed, all 6 could be placed on asingle span. However, each RSL has the limitation that the uplink (BTS to BSC) and downlink(BSC to BTS) timeslot mappings are identical.

Daisy chains: The HIISC supports backhaul daisy chain configurations. Traffic for upstreamsites is routed through the TSI, allowing for multiplexing over shared spans with local site traffic.

TRAU: Span lines transporting TRAU are switched to the appropriate CTU2 by the TSI.

NIU control processor and RSL termination

The NIU control processor terminates the LAPD protocol layer for each RSL. It supports up to 8separate and simultaneous LAPD connections. Each LAPD connection may be configured aseither a 64 kbit/s link or as a 16 kbit/s link.

The NIU control processor also configures and monitors the LIU / framer. To facilitate thesefunctions the NIU control processor has a control interface to the LIU / framer and a dual 32timeslot 2048 kbit/s TDM interface to the TSI.

The NIU control processor terminates up to 16 full duplex HDLC channels - up to 8 for LAPDtransport to the BSC and up to 8 for RSL (including one for control) transport to the site controlprocessor.

Span type selection: The NIU defaults to the E1 interface type for all span lines.

Backhaul framing options: The NIU can enable and disable timeslot 0 CRC-4multi-framing (enabled by default). Selection is supported by a message interface with the sitecontrol processor. In either case, timeslot 16 multi-framing is disabled (allowing timeslot 16 toused for TRAU or RSL traffic) and HDB3 line coding is used.

Backhaul N-bit facility: The NIU can enable and disable the use backhaul N-bits for alarmindications. Selection is supported by a message interface with the site control processor.

5-12 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II site controller (HIISC)

Site control processor

The site control processor is provisioned with a control interface for the TSI and two 2048kbit/s TDM interfaces to the TSI. It is responsible for configuration of the TSI and controland monitoring of the NIU.

NIU control processor to site control processor interface

The interface between the NIU control processor and the site control processor consists of NIUcontrol messages plus RSL messages stripped of the LAPD protocol. Each RSL connection tothe BSC utilizes a 64 kbit/s timeslot between the NIU control processor and the site controlprocessor.

A 64 kbit/s connection is used, regardless of whether the connection to the BSC isoperating at 64 kbit/s or 16 kbit/s.

NIU control messages, including those used to establish, reconfigure and disconnect RSL links,are always carried within timeslot 0 on the NIU TDM port 0. These messages are multiplexedwith traffic comprising the first established RSL. The site control processor dynamically assignsadditional RSL connections to any of the other remaining 31 timeslots of NIU TDM port 0 or32 timeslots of NIU TDM port 1.

RSL conguration and control

LAPD links

Each LAPD link is configured with the following default parameters:

• T203 = 10 seconds.

• The maximum I frame size (N201 = 610 bytes).

The site control processor is able to configure the following parameters for each LAPDconnection through the control message interface to the NIU control processor:

• Rate (64 kbit/s or 16 kbit/s).

• Bit-pair for 16 kbit/s connections.

• SAP.

• TEI.

68P02903W31-C 5-13

Aug 2007

Horizon II site controller (HIISC) Chapter 5: Digital modules

• The maximum number of outstanding I frames (k value).

• The maximum number of retransmissions (N200).

The span line timeslot and span line are not required as the site control processorsets these directly at the TSI.

Additionally, the site control processor specifies the following internal connection parameters:

• NIU port and timeslot for the connection between the NIU control processor and the sitecontrol processor.

• NIU port and timeslot for the connection between the NIU control processor and the TSI.

16 kbit/s RSLs

Any or all of the 8 RSL links can be configured at either 16 kbit/s or 64 kbit/s. When configuredat 16 kbit/s, a RSL occupies a bit-pair within a single timeslot. Four bit-pair positions aresupported; bits 0 and 1, bits 2 and 3, bits 4 and 5, bits 6 and 7.

For downlink flows, the TSI switches the entire timeslot containing the 16 kbit/s bit-pair onto aNIU port timeslot. The NIU control processor recovers the LAPD from the designated bit-pair.

For uplink flows, the NIU control processor places the LAPD within the designated bit-pair andtimeslot on its TSI connection. The TSI then inserts this bit-pair into a designated timeslot,while preserving the content of the other six bits within that timeslot.

RSL and span alarms

LAPD link management events for each LAPD connection and span alarm events for each spanare reported to the site control processor by the NIU control processor.

Flow control

The interface between the NIU control processor and the site control processor supports flowcontrol. This enables the NIU processor to throttle RSL traffic from the site control processor inthe event of an overload condition. This condition may occur when 16 kbit/s RSL links are activeor when multiple heavily loaded 64 kbit/s RSL links are active.

To reduce the possibility of overloading, the processing delay within the NIU control processoris minimized and the RSL message buffer depth is maximized. A fully loaded NIU (up to 8established RSL links) maintains a maximum processor delay of less than 25 ms per message.Delay is measured from receipt of the end of the incoming frame to the start of transmission ofthe outgoing frame. The NIU control processor has 2000 kbytes of message buffers.

5-14 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II site controller (HIISC)

Integral HIISC XMUX functionality

The equivalent functionality of a separate XMUX module is integrated within the HIISC, thusenabling the HIISC in the master cabinet to communicate with the CTU2s in up to threeexpansion cabinets through fiber optic links between the site expansion boards.

68P02903W31-C 5-15

Aug 2007

XMUX module Chapter 5: Digital modules

XMUX module■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The expansion multiplexer (XMUX) module replaces the HIISC in expansion cabinets andprovides the interface to the master cabinet.

Two XMUX modules may be installed in a Horizon II macro expansion cabinet, one for themaster HIISC, and one for the slave. A Horizon II macro expansion cabinet only requires oneXMUX to connect up to six CTU2s within the cabinet (plus one for redundancy if required).

A Horizon II mini or Horizon II micro expansion cabinet only requires one XMUX to connect upto two CTU2s within the cabinet.

If Horizon II expansion cabinets are added, the master cabinet and expansion cabinetsmust also contain site expansion boards.

The XMUX can support up to six transceiver links. It uses a 16.384 Mbit/s Manchester encodedserial data link, organized as 256 x 8-bit timeslots in a 125 microsecond frame. Manchestercoding is used to detect errors, indicated at timeslot 0 for each transceiver, enabling errorcorrection at the receiving XMUX.

Although the XMUX provides the equivalent functionality of the FMUX inHorizonmacro, it is NOT backwards compatible and cannot be used in a Horizonmacrocabinet.

XMUX module view

Figure 5-5 shows a XMUX module.

5-16 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro XMUX module

Figure 5-5 View of the XMUX module

XMUX functional description

The HIISC transmits and receives a 2.048 Mbit/s data stream link to each operational CTU2. Inthe master cabinet this is routed through the backplane, without the need for a XMUX.

If the CTU2 is in an expansion cabinet, the integrated XMUX in the HIISC combines the datastream with up to five others and then sends the multiplexed signal to the site expansionboard through the backplane. The site expansion board performs a TTL to fiber optic signalconversion, for onward transmission to the expansion cabinet through fiber optic cables.

At the expansion cabinet, another site expansion board converts the fiber optic signal back toelectronic form and sends this to the XMUX. The XMUX demultiplexes the signal and sends thedata stream to the appropriate CTU2.

The data stream return path from the CTU2 in the expansion cabinet is a reversal of the above.

68P02903W31-C 5-17

Aug 2007

XMUX module Chapter 5: Digital modules

Figure 5-6 XMUX interconnection block diagram

Site expansion is not restricted to using Horizon II macro or Horizon II mini or HorizonII micro units as slaves. Horizonmacro and/or M-Cell6 (equipped with a FMUX) canalso be used. Similarly, the master BTS can be a Horizonmacro or FMUX-equippedM-Cell6 with a Horizon II macro or Horizon II micro as one or more slaves.

Refer to Installation & Configuration: Horizon II macro (68P02902W97) , Installation& Configuration: Horizon II mini (68P02903W22) or Installation & Configuration:Horizon II micro (68P02903W32) for full details of BTS interoperability.

5-18 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Site expansion board

Site expansion board■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The site expansion board is an optional module that is required only for site expansion:

• In the Horizon II macro cabinet one or two boards may be installed, depending on whetherredundancy is required.

• In a Horizon II mini cabinet or Horizon II micro enclosure only one board can be installed.

The primary function of the expansion board is to convert TTL signals to fiber optic signals (andvice versa) to enable the master and slave cabinets to communicate with each other.

The board contains the following I/O connectors (see Figure 5-7):

• 6 x fiber optic connectors (three Tx/Rx (OUT/IN) pairs), for connecting up to threeexpansion cabinets. Each fiber optic link is full duplex 16.384 Mbit/s and is capable ofdriving up to 1 km.

• Optional 1 x 15-pin D-sub connector for GPS.

In Horizon II macro, redundancy is determined by the complement of HIISCs in the mastercabinet. If the master cabinet contains two HIISCs (1 + 1 redundant), two XMUXs must beinstalled in each slave cabinet. Two site expansion boards are also required in the masterand in each slave cabinet.

68P02903W31-C 5-19

Aug 2007

Site expansion board Chapter 5: Digital modules

View of site expansion board

Figure 5-7 Site expansion board

5-20 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Alarm module

Alarm module■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II alarm module is located on the left side of the digital module shelf. It providesthe enclosure equipment with an external alarm monitoring system to report operational status.The alarm module:

• Collects all enclosure alarms (received from the backplane).

• Provides current sensing for 16 customer inputs (referred to as site alarms). These inputsare provided by the PIX connectors PIX 0 (and PIX 1 in Horizon II macro).

• Controls up to four relay driven outputs linked to customer equipment (change-overcontacts 30 V 1 A maximum). These outputs are provided by the PIX 0 connector.

• Transmits alarm information to all CTU2s in the same cabinet.

• Processes antenna VSWR monitor alarm signals.

The Horizon II alarm module is not backward compatible with the alarm moduleused in Horizonmacro.

68P02903W31-C 5-21

Aug 2007

Alarm module Chapter 5: Digital modules

View of alarm module

Figure 5-8 shows an alarm module.

Figure 5-8 Alarm module view

5-22 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Alarm module

Alarm module functionality

The alarm module receives inputs from:

• The external alarm connector on the interface panel (from the optional battery backupsystem).

• Cabinet PSUs (identifying manufacturer code and slot number).

• Environmental control devices.

• Customer defined alarms.

• Antenna VSWR monitoring circuit within Tx blocks.

The alarm board receives these inputs, encodes them, and then passes the code word to allCTU2s in the cabinet through the backplane.

Alarm module replacement - effect on alarms

The alarm module can be replaced while the cabinet system is running (hot swap). This willtemporarily interrupt alarms, with the OMC-R receiving an additional alarm module out ofservice alarm, which automatically clears following correct insertion of the replacement module.

Alarm collection from expansion cabinets

Alarms detected by the alarm module in an expansion cabinet are forwarded to the expansioncabinet transceivers. The transceivers then send the alarms to the HIISC in the master cabinetthrough the XMUX and site expansion board in the expansion cabinet, and the site expansionboard in the master cabinet.

68P02903W31-C 5-23

Aug 2007

Alarm module Chapter 5: Digital modules

Alarm module display presentation

All front panel alarm LEDs are green (OK) when equipment is functioning correctly or red(alarm) when equipment is faulty. Table 5-2 shows the LED designations.

Table 5-2 Alarm module LEDs

LEDlocation Legend LED color states Equipment monitored

(Green = OK, Red = FAULT)

1 MAINS Unlit/Red Not used.

2 RECTFR Unlit/Red Not used.

3 DOOR 1 Unlit/Red Door open alarm.

4 DOOR 2 Unlit/Red Not used.

5 LVD Unlit/Red Low voltage disconnect (LVD) alarm(battery backup option).

6 FAN 0 Unlit/Red Internal fan unit alarm.

7 FAN 1 Unlit/Red External fan module alarm.

8 FAN 2 Green/Red Not used.

9 HMS 1 Unlit/Red Not used.

10 HMS 2 Unlit/Red Not used

5-24 68P02903W31-C

Aug 2007

Chapter

6

Routine maintenance■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter contains the procedures for the routine maintenance of a Horizon II micro basetransceiver station (BTS).

68P02903W31-C 6-1

Aug 2007

Routine maintenance overview Chapter 6: Routine maintenance

Routine maintenance overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Since a Horizon II micro BTS operates as part of a network, the procedures in thischapter must be performed in conjunction with the relevant network proceduresshown in the associated OMC-R manuals. Before attempting any work on the cabinet,contact the OMC-R to advise on the proposed activity.

Safety

Potentially hazardous voltages and high energy sources are present in the cabinetwhen the external ac mains isolator switch is set to the ON position and/or batteriesare connected:

• Remove rings, watches and jewelry before starting these procedures, andexercise extreme caution when working on the equipment.

• Maintenance procedures on this equipment must only be carried out by suitablyqualied personnel.

If using a step ladder or platform for access to wall or pole mounted equipmentpay particular attention to Weather conditions affecting unpacking, installation ormaintenance.

Safety features are built into the equipment to protect against the potentially lethal hazards thatexist. All statements regarding safety within these routine maintenance procedures must beadhered to when working on the equipment.

Reporting faulty devices

During routine maintenance and FRU replacement procedures, first check for signs of damage,which may indicate a problem that could repeat, cause additional damage, or point to a failureelsewhere. Prompt, logical analysis of the problem may identify the fault and make correctiveaction possible.

If a safety issue arises, follow the steps shown in Procedure 6-1.

6-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Routine maintenance overview

Procedure 6-1 Reporting safety issues

1 Make the equipment concerned safe, for example, by removing power.

2 Make no further attempt to tamper with the equipment.

3 Inform the OMC-R that an equipment safety problem has been identified.

4 Select one of the following:

• Report the problem directly to the Customer Network Resolution Centre,Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) andfollow up with a written report by fax, Swindon +44 (0)1793 430987 orChina +86 10 68423633 (fax).

• Seek local office advice.

5 Collect evidence from the equipment under the guidance of:

• The Customer Network Resolution Centre.

• The local office.

Equipment failures that do not involve safety issues must be handled according to the type offailure. Most failures are signalled by an alarm at the OMC-R. Procedures for handling alarmsat the OMC-R are provided in Alarm Handling at the OMC-R, 68P02901W26.

Routine maintenance intervals

Routine maintenance for Horizon II installations is recommended at the intervals shown inTable 6-1.

Table 6-1 Horizon II mini routine maintenance schedule

6 months 12 months 24 months

Ensure that cabinet airinlets, exhaust grilles, andfilters (if fitted) are notblocked.

Annual check of theinstallation.

Inspect generalmechanical conditionof the cabinet.

– Check normal operation,including fans. Also cableintegrity and state of allconnections.

Inspect locks, handles,and hinges of door (ifappropriate). Lubricate ifrequired.

These procedures are described in subsequent sections.

• 6 monthly

• 12 monthly

• 24 monthly

68P02903W31-C 6-3

Aug 2007

Routine maintenance overview Chapter 6: Routine maintenance

Cleaning agents

The following is a list of cleaning and lubricant materials required for routine maintenance:

• Dustpan.

• Soft brush.

• Vacuum cleaner.

• Mild detergent.

• Deionized water.

• Soft cloth.

• Lubricant (WD40 or equivalent).

• Light grease (TBI or equivalent).

Tools

The only tools required are torque spanners, torque wrenches and Torx drivers, as listed inHorizon II micro: Installation & Configuration (68P02903W32). The manual is supplied alongwith the equipment.

Torque values

Table 6-2 details torque values used during installation, maintenance and repair procedures.

Table 6-2 Torque values for all equipment screws/bolts and RF connectors

Size ofscrew/bolt M4 M6 M8 M10 SMA N-Type 7/16

Torque value 2.2 Nm 3.4 Nm 5 Nm 10 Nm 1 Nm 3.4 Nm 25 Nm

Torque values used with anchor bolts will depend on the anchor bolt manufacturer.Check manufacturer's data for correct values.

6-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Routine maintenance overview

Solar cover and door operation

The enclosure access procedure is described in Procedure 6-2 and that for solar cover and doorrefitting in Procedure 6-3.

Procedure 6-2 Removing solar cover and opening enclosure doors

1 Loosen the four captive tamper-proof SouthCo trilobe fasteners at the rearcorners of the solar cover, using the SouthCo trilobe driver bit, supplied with theenclosure, and remove the solar cover.

2 Loosen the remaining tamper-proof SouthCo trilobe fasteners at the cornersof the doors.

3 Ease the door open.

The door is held in place by a EPDM seal.

4

The bonding cable spade terminal is a locking type, use of excessiveforce without operation of the locking tab may break the cable.

Disconnect the earth bonding cable at the spade terminal, by operating thelocking tab, and lift the door away from the enclosure.

Procedure 6-3 Retting solar cover and enclosure doors

1 Hold the door at about the 45° open position and lift into position, insertingrear edge of door first.

2 Reconnect the earth bonding cable at the spade terminal.

3 Shut the door by pressing the front edge of the door to, and tighten the fourtamper-proof SouthCo trilobe fasteners at the corners of the door, using theSouthCo trilobe driver bit, supplied with the enclosure.

4 Refit the solar cover by clipping the cover under the lips around the rear edgeof the enclosure. Secure by tightening the remaining tamper-proof SouthCotrilobe fasteners.

Assumptions - doors and solar cover

Any requirement to remove the solar cover or to open a door is assumed in all procedures.Shutting the doors, and refitting the solar cover is assumed at the end of any procedure.

68P02903W31-C 6-5

Aug 2007

Visiting the site Chapter 6: Routine maintenance

Visiting the site■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

When preparing to do work at a site and upon arrival, follow the guidelines provided in thissection.

Before leaving for the site

Before leaving for the site, follow Procedure 6-4.

Procedure 6-4 Initial preparation for site visit

1 Ensure that team members have adequate test equipment, tools, and necessaryhardware to complete the tasks. Check for any special requirements.

2 Contact the person in charge of the site to advise of the team's estimated timeof arrival and the expected duration of their stay on the site. Usually thelogistics will have already been arranged, but it is good practice to check thatthe information was received.

3 Ensure that the team read the site access details on each visit to a site as localregulations may change.

Arrival at site

When entering any site, follow Procedure 6-5.

Procedure 6-5 Site entry procedure

1 Contact the communications site manager before entering the site. Obtain thefollowing information from the on-site contact:

• Local regulations.

• Parking instructions.

• Waste material removal or disposal instructions.

• Directions to canteen facilities (if available).

2 Enter the site.

3 Check for building alarms, for example, intruder alarms, that may have beenactivated by entry. If fitted, disable the fire extinguishing systems, and anyalarms activated by entry.

4 Read any local instructions provided.

6-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Visiting the site

Leaving site

When leaving a site, follow Procedure 6-6.

Procedure 6-6 Site exit procedure

1 Enable the fire extinguishing system, if fitted, and any alarms that were disabled.

2 Contact the local site manager to announce the team's departure.

3 Sign out of the building as necessary.

Waste material on site

Clear waste material from the site on completion of the job, unless otherwise indicated by thecustomer.

Do not burn waste material, as packaging might give off toxic gasses.

Rural sites

It is the responsibility of the senior member of the team to ensure that all personnel on site areaware of all applicable national and regional environmental regulations or codes of practiceand, especially with respect to water authority sites, any relevant health regulations.

Adhere to these points:

• Guard against all risk of fire.

• Fasten all gates (remember, site visits could be traced back if a complaint is made).

• Leave no litter.

• Drive carefully on country roads and observe speed restrictions at all times.

• Keep to the paths and tracks if crossing farm land.

68P02903W31-C 6-7

Aug 2007

Visiting the site Chapter 6: Routine maintenance

On site safety

The following safety guidelines are applicable to all members of the installation/maintenanceteam and any visitors to the site.

All personnel must:

• Ensure that no-one moves heavy items without assistance. Equipment must be safelypositioned at all times.

• Wear safety helmets when antenna or overhead work is in progress, and when localregulations require them.

• Wear safety goggles and dust masks when drilling. This is particularly important whendrilling overhead ironwork.

• Wear ear protectors while drilling is in progress.

• Wear approved safety footwear when moving heavy equipment.

Stop any work if anyone in the team is not properly protected, or is unaware of safetyrequirements.

When installing cable ties, even temporarily, cut the excess or tail properly. This is to preventsharp edges inflicting injury when not cut flush with the locking edge.

6-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Weather conditions affecting unpacking, installation or maintenance

Weather conditions affecting unpacking, installationor maintenance■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Before beginning outdoor unpacking, installation or maintenance procedures, it is importantto read and take into account the following information concerning the climatic conditionsat the intended site.

Weather conditions

Due consideration should be given to the hazards of wind and other inclement weatherconditions when installing or maintaining outdoor equipment. This is especiallyimportant when using a ladder to gain access.

• Use discretion at all times.

• Do not climb a ladder, scaffolding, or use some other similar method of access, ifyou feel it is unsafe to do so under the prevailing weather conditions.

• Do not attempt to open the enclosure doors if the wind speed exceeds 25 knots.

• The equipment doors, and access panels must be safely restrained before workis carried out.

Maintenance cover

Motorola recommend the use of a maintenance cover for access to the equipment duringinclement weather conditions.

The maintenance cover is not supplied with the outdoor equipment and should beprovided by the customer, if required.

Installation or maintenance procedures for the equipment are dependent on the weatherconditions. There are three situations where the recommended guidelines should be consideredbefore commencing work.

• No access.

• Access with maintenance cover.

• Access without maintenance cover.

68P02903W31-C 6-9

Aug 2007

Weather conditions affecting unpacking, installation or maintenance Chapter 6: Routine maintenance

No access

Access should not be attempted to the enclosure during the following actual or imminentinclement weather conditions, with or without a maintenance cover.

• Winds in excess of 25 knots.

• Heavy persistent rain, snow, hail or sleet.

• During an electrical storm.

Access with a maintenance cover

Access may be made to the enclosure under the following conditions with the use of amaintenance cover.

• Wind speeds of less than 25 knots.

• Persistent rain, snow, hail or sleet.

• Where airborne substances (such as leaves or dust) may cause a problem.

Access without a maintenance cover

Access may not be made under the following conditions without the use of a maintenance cover.

• Wind speeds of less than 25 knots.

• No precipitation occurring or likely to occur during the maintenance period.

• Where airborne substances (such as leaves or dust) are not a problem.

6-10 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro 6-monthly maintenance procedures

6-monthly maintenance procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Potentially hazardous voltages and high energy sources are present in the cabinetwhen the external ac mains isolator switch is set to the ON position and/or batteriesare connected. Stored energy may remain present in the cabinet when external poweris not connected.

• Remove rings, watches and jewelry before starting these procedures, andexercise extreme caution when working on the equipment.

• Maintenance procedures on this equipment must only be carried out by suitablyqualied personnel.

The 6-monthly maintenance procedures involve cleaning air inlets and exhaust grilles.

Cleaning air inlets and exhaust grilles

The enclosure ventilation air enters at the bottom of the enclosure and is expelled at the topof the front face of the solar cover.

Use a vacuum cleaner or brush to ensure that the inlet and exhaust vents are clear of debris.

68P02903W31-C 6-11

Aug 2007

12-monthly maintenance procedures Chapter 6: Routine maintenance

12-monthly maintenance procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Potentially hazardous voltages and high energy sources are present in the cabinetwhen the external ac mains isolator switch is set to the ON position and/or batteriesare connected. Stored energy may remain present in the cabinet when external poweris not connected.

• Remove rings, watches and jewelry before starting these procedures, andexercise extreme caution when working on the equipment.

• Maintenance procedures on this equipment must only be carried out by suitablyqualied personnel.

The 12-monthly maintenance procedures involve the following:

• 6-monthly procedures.

• Checking normal operation.

• Annual check of the installation.

Checking normal operation

Check normal operation by visual inspection in the following procedure:

Procedure 6-7 Checking normal operation

1 Inspect the inside of the cabinet and note any signs of physical damage,overheating, loose connections, or badly fitting components. Take appropriateaction to correct the damage, and inform the OMC-R.

2 Ensure that the LEDs on modules listed in Table 6-3 are lit as shown; thisindicates correct functioning of the cabinet. If any red LEDs are lit, other thanthe door alarm (alarm 3 on the alarm module), inform the OMC-R.

6-12 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro 12-monthly maintenance procedures

Table 6-3 Normal LED indication of cabinet modules

Equipment with LEDs Color of LEDs lit

CTU2 Radio status (GREEN)and Tx status (YELLOW).

PSU Top LED on front panel GREEN.

Digital modules (HIISC or XMUX) Status LED GREEN.

Alarm module LED 6 Unlit (fan unit).

Battery unit Status LED GREEN.

Annual check of the installation

It is recommended that the following be performed annually:

• Power down cabinet.

• Earth continuity check.

• Power system insulation check.

• Check connection to site power supply.

• Pre-power up check of earth connection security and condition.

• Power up of cabinet.

Refer to Installation & Configuration: Horizon II micro (68P02903W32) manual, forinstructions to carry out the above procedures.

Log the maintenance activity. After procedures have been completed, restore the cabinet tooperational state and notify the OMC-R of base station availability.

68P02903W31-C 6-13

Aug 2007

24-monthly maintenance procedures Chapter 6: Routine maintenance

24-monthly maintenance procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Potentially hazardous voltages and high energy sources are present in the cabinetwhen the external ac mains isolator switch is set to the ON position and/or batteriesare connected. Stored energy may remain present in the cabinet when external poweris not connected.

• Remove rings, watches and jewelry before starting these procedures, andexercise extreme caution when working on the equipment.

• Maintenance procedures on this equipment must only be carried out by suitablyqualied personnel.

The 24-monthly maintenance procedures involve the following:

• 6-monthly procedures.

• 12-monthly procedures.

• Mechanical inspection of enclosure.

Mechanical inspection of enclosure and doors

The following must be performed every 24 months:

• Inspecting the enclosure exterior on page 6-14.

• Inspecting the doors on page 6-15.

• Inspecting the enclosure interior on page 6-15.

Inspecting the enclosure exterior

To inspect the enclosure exterior:

• Check solar cover, exterior panels and mounting brackets for dents and structural damage.

• Check cabinet electrical, data and RF connections for signs of overheating, corrosionand security of attachment.

6-14 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro 24-monthly maintenance procedures

Inspecting the doors

To inspect the doors:

• Check the enclosure doors for distortion, security and correct operation.

• Check the door earth connections for corrosion, damage and security.

Inspecting the enclosure interior

To inspect the enclosure interior:

• Check all rack equipment for security of attachment, especially PSU and CTU2 attachmentscrews using a Torx driver. Tighten to the correct torque (see Table 6-2, below, for torquevalues).

• Carry out a visual check of all wiring for signs of overheating and security of attachment.

• Check the earth connections for corrosion and tightness using a torque spanner.

Do not overstress the earth connections as this may damage the connector andreduce the protective function.

Tighten to the correct torque.

68P02903W31-C 6-15

Aug 2007

24-monthly maintenance procedures Chapter 6: Routine maintenance

6-16 68P02903W31-C

Aug 2007

Chapter

7

FRU replacement procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter provides information on the replacement of FRUs. Only those components classedas FRUs are covered in this chapter.

68P02903W31-C 7-1

Aug 2007

Overview of FRU replacement procedures Chapter 7: FRU replacement procedures

Overview of FRU replacement procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Potentially hazardous voltages and high energy sources are present in the cabinetwhen the external ac mains isolator switch is set to the ON position and/or batteriesare connected. Stored energy may remain present in the cabinet when external poweris not connected.

• Remove rings, watches and jewelry before starting these procedures, andexercise extreme caution when working on the equipment.

• Maintenance procedures on this equipment must only be carried out by suitablyqualied personnel.

The PSU has internal double pole/neutral fusing, after the operation of a single fuse,parts of the equipment may remain energized. In the event of a power supply failureensure that the equipment is disconnected from the primary power source beforeany servicing or maintenance activity.

If using a step ladder or platform for access to wall or pole mounted equipmentpay particular attention to Weather conditions affecting unpacking, installation ormaintenance.

This chapter provides information on the replacement of FRUs. Only those components classedas FRUs are covered in this chapter.

Guidance for all site visits is given in Visiting the site.

Any requirement to open or close a door, or remove and replace the solar cover, is assumed inprocedures. Shutting the doors, or refitting any cover is assumed at the end of any procedure.

Where customers wish to perform a minor repair on a FRU in order to save the cost of fullreplacement, they should consult Motorola for more detailed procedures or replacementcomponents (see Non-FRU components later in this chapter.).

7-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Overview of FRU replacement procedures

FRU list

The following is a list of FRUs used in the Horizon II micro:

• Solar cover.

• Enclosure doors.

• Fan units (internal and external).

• Power supply unit (PSU).

• Battery module.

• CTU2/CTU2D.

• Mini-SURF.

• Tx blocks, DUP or PGSM duplexer.

• Digital modules (HIISC, XMUX, site expansion board and alarm module).

• Line interface unit boards (T43/CIM or BIB/BIM).

Torque values

Table 7-1 shows torque values used during installation, maintenance and repair procedures.

Table 7-1 Torque values for all equipment screws/bolts and RF connectors

Size ofscrew/bolt M4 M6 M8 M10 SMA N-Type 7/16

Torque value 2.2 Nm 3.4 Nm 5 Nm 10 Nm 1 Nm 3.4 Nm 25 Nm

Torque values used with anchor bolts will depend on the anchor bolt manufacturer.Check manufacturer's data for correct values.

68P02903W31-C 7-3

Aug 2007

Overview of FRU replacement procedures Chapter 7: FRU replacement procedures

FRU enclosure locations

Figure 7-1 shows front and rear views of a fully equipped Horizon II micro enclosure withFRUs identified. The doors, omitted from this illustration for clarity , are shown in the doorreplacement sections.

Figure 7-1 FRU enclosure locations

7-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Overview of FRU replacement procedures

The CTU2 handle and adjacent metal surfaces, indicated in Figure 7-2, may be hotto touch.

Figure 7-2 CTU2 handle – heat warning

68P02903W31-C 7-5

Aug 2007

Non-FRU components Chapter 7: FRU replacement procedures

Non-FRU components■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Non-FRU components are:

• Items unlikely to fail, but replacement of which is essential if failure occurs.

or

• Sub-components of FRUs, where local conditions may make it more economical to repairthe FRU.

Only qualied personnel should attempt non-FRU component replacement, in orderto minimize risk of equipment damage. For example, the internal cable assembliesrequire care in removal and installation, and Individual fans require care in ensuringcorrect direction of airow.

List of non-FRU components

Non-FRU components include the following:

• Midplane heat sensors.

• Individual fans within a fan module.

• Any part of the chassis, harnesses, or midplane.

Procedure for replacing non-FRU components

Customers wanting to replace non-FRU components should:

• Contact the local Motorola office for availability.

• Seek Motorola advice for fitting non-FRU components.

Chassis component attachment

The chassis components are attached to the enclosure by rivets which must not be removed.

7-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing an enclosure door

Replacing an enclosure door■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The door is essential to the correct operation of the ventilation/cooling system. The door alsoprovides protection for the equipment contained inside. For these reasons, the replacementprocedure should be completed in one session, and the enclosure then secured.

Figure 7-3 View of door

68P02903W31-C 7-7

Aug 2007

Replacing an enclosure door Chapter 7: FRU replacement procedures

Door replacement procedure

Follow the given procedure to replace a door:

Procedure 7-1 Replacing a faulty door

1 Loosen the captive tamper-proof SouthCo trilobe fasteners at the corners ofthe doors.

2 Ease the door open.

The door is held in place by an EPDM seal.

3

The bonding cable spade terminal is a locking type, use of excessiveforce without operation of the locking tab may break the cable.

Disconnect the earth bonding cable at the spade terminal, by operating thelocking tab, and lift the door away from the enclosure.

4 Hold the door at about the 45° open position and lift into position, insertingrear edge of door first.

5 Reconnect the earth bonding cable at the spade terminal.

6 Shut the door by pressing the front edge of the door to, and tighten thetamper-proof SouthCo trilobe fasteners at the corners of the door, using theSouthCo trilobe driver bit, supplied with the enclosure.

7-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing fan units

Replacing fan units■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The internal fan unit can be replaced while the equipment is operational. Airflow is severelyreduced while fans are out of service and the door is open. This will raise equipmenttemperature, and could shut down the cabinet by triggering the heat sensors.

The external fan module replacement procedure requires that the equipment be shut downbefore replacement, due to the location of the external fan module electrical connections. Thiscan only take place after the equipment has been taken out of service, in agreement withthe OMC-R.

Fan test push button

A fan test push button (Figure 7-4) is located on the frame of the unit, above the PSU module.Press the push button to operate all fans simultaneously, allowing identification of faultymodules.

68P02903W31-C 7-9

Aug 2007

Replacing fan units Chapter 7: FRU replacement procedures

Figure 7-4 Fan test push button

7-10 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing fan units

View of the internal fan unit

Figure 7-5 shows a view of the internal fan unit fitted in a Horizon II micro.

Figure 7-5 View of the internal fan unit

Replacing an internal fan unit

Follow the given procedure to replace a fan unit.

68P02903W31-C 7-11

Aug 2007

Replacing fan units Chapter 7: FRU replacement procedures

If the enclosure is operational, this replacement procedure should be completed in theshortest possible time to minimize the duration of cooling air disruption.

Procedure 7-2 Replacing an internal fan unit

1 Undo the two M4 retaining screws on the front of the fan unit, using a T25torx driver.

2 Pull out the fan unit.

3 Refit the fan unit by carefully aligning the guide runners and pushing gentlyinto place.

4 Secure the fan unit by tightening the two M4 attachment screws to 2.2 Nmusing a T25 torx driver.

5 Ensure that all fans are operational.

View of the external fan module

Figure 7-6 View of the external fan module

7-12 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing fan units

Replacing an external fan module

Replacing the external fan module requires removal of the PSU; and therefore can only takeplace after the equipment is taken out of service, in agreement with the OMC-R.

Procedure 7-3 Replacing an external fan module

1 Set the switch of the PSU to OUTPUT DISABLE. The ACTIVE LED willextinguish. The ALARM LED (red) will illuminate.

2 Undo the two M4 retaining screw on the front of the PSU module, using a T25torx driver, and pull the module out of the cabinet using the handle. The ALARMLED will extinguish, (if previously lit).

3 Disconnect the fan unit cable plug form the connector shown in Figure 7-7.

4 Ease the cable grommet out through the hole in the enclosure side.

5 Undo the two M4 retaining screws on the front of the external fan module, usinga T25 torx driver, and gently pull the unit to release.

6 Insert the rear of the replacement external fan module onto the retaining lip atthe right of the enclosure. Lift the front of the unit into place and secure withthe two M4 retaining screws, tightening the screws to 2.2 Nm torque usinga T25 torx driver.

7 Feed the cable grommet through the hole in the enclosure side and plug intothe connector noted instep 3.

8 Refit the PSU in the empty slot. Push the PSU all the way in and secure inposition by tightening the M4 retaining screw to 2.2 Nm torque using a T25torx driver.

9 Set the front panel switch to OUTPUT ENABLE. Check that the ACTIVE LEDis lit, and ensure that all fans are operating. Return the cabinet to service andnotify the OMC-R of availability.

68P02903W31-C 7-13

Aug 2007

Replacing fan units Chapter 7: FRU replacement procedures

Figure 7-7 External fan module electrical connector

7-14 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a power supply unit (PSU)

Replacing a power supply unit (PSU)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

There is only one slot for a PSU in the Horizon II micro enclosure. Replacement of the PSU willnecessitate powering down the enclosure, and can only take place after the equipment has beentaken out of service, in agreement with the OMC-R.

View of the PSU

Figure 7-8 shows a view of the PSU with key features identified.

Figure 7-8 View of the PSU

There are several manufacturers of the PSUs. All PSUs of the same type are fullycompatible with each other, regardless of manufacturer.

68P02903W31-C 7-15

Aug 2007

Replacing a power supply unit (PSU) Chapter 7: FRU replacement procedures

Replacing a PSU

The BTS must be taken out of service, with the agreement of the OMC-R, before commencingthe following procedure.

The PSU has internal double pole/neutral fusing, after the operation of a singlefuse, parts of the equipment may remain energized. Ensure that the equipment isdisconnected from the primary power source before any servicing or maintenanceactivity.

Removal of the PSU will disconnect the battery module supply to the enclosure.

Procedure 7-4 Replacing a PSU

1 Set the switch of the replacement PSU to OUTPUT DISABLE.

2 Set the switch of the faulty PSU to OUTPUT DISABLE. The ACTIVE LED willextinguish (the ACTIVE LED may already be off if a fault has resulted in outputfailure of that PSU). The ALARM LED (red) will illuminate, or will stay on ifalready lit due to alarm state.

3 Undo the M4 retaining screw on the front of the faulty PSU module and pull themodule out of the cabinet using the handle. The ALARM LED will extinguish,(if previously lit).

4 Insert the replacement PSU in the empty slot. Push the PSU all the way inand secure in position by tightening the M4 retaining screw to 2.2 Nm torqueusing a Torx driver.

5 Set the front panel switch to OUTPUT ENABLE. Check that the ACTIVE LEDis lit.

6 Return the cabinet to service and notify the OMC-R of availability.

7-16 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a battery module

Replacing a battery module■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The battery module can be replaced without taking the equipment out of service, but opening thedoors will generate an alarm therefore the OMC-R should be notified of imminent repair activity.

Replacement procedure

Procedure 7-5 Replacing a battery module

1 Set the battery switch to OFF. The LED will show RED. A low voltage disconnectimmanent (LVDI) alarm will show at the OMC-R.

2 Unscrew the two M4 retaining screws, using a T25 torx driver.

3 Remove the battery.

If no replacement battery is to be fitted, refit a battery connectorshorting plug, or the low voltage disconnect immanent (LVDI) alarmwill continue to show at the OMC-R.

4 Insert the replacement module and tighten the two M4 retaining screws, usinga T25 torx driver.

5 Set the battery switch to ON. The LED will show AMBER until the battery is fullycharged, when it will show GREEN.

The battery module must be charged a minimum of 10 to 12 hours before initial use.

68P02903W31-C 7-17

Aug 2007

Replacing a CTU2 Chapter 7: FRU replacement procedures

Replacing a CTU2■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The CTU2 handle and adjacent metal surfaces may be hot to touch.

Replacing the CTU2 requires removal of RF transmitter power for that CTU2; it is thereforeadvisable to perform this procedure during periods of low traffic. The OMC-R should be notifiedof imminent repair activity.

The CTU2 replacement procedure is the same for all CTU2s, regardless of frequencyrating:

• Ensure the replacement CTU2 is the same frequency rating as the faulty CTU2.

• Read the Preserving CTU2 calibration section later in this chapter prior toremoving the CTU2.

7-18 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a CTU2

View of a CTU2

Figure 7-9 CTU2 view with key features

68P02903W31-C 7-19

Aug 2007

Replacing a CTU2 Chapter 7: FRU replacement procedures

CTU2 replacement procedure

The CTU2 transmit power, in Horizon II micro, is factory calibrated as a macro BTS(up to: 60 W for PGSM900, 63 W for EGSM900 and 50 W for DCS1800, in singledensity mode), prior to delivery.

Use the max_tx_bts parameter to ensure the maximum Tx power is correctly setafter CTU2 replacement. For example; if using standard power option, set value = 5to 21, or high power option, set value = 0 to 21). See the chapter Site vericationprocedures, for Normal CTU2 VSWR and cell site power (CSPWR) calibration, Txoutput power calibration procedure.

An earthing wrist strap must be worn when handling CTU2s. An ESP earthingconnection point is provided at the top left of the front of the cabinet.

There are two stages to this procedure:

• Removing a faulty CTU2 on page 7-20.

• Fitting a replacement CTU2 on page 7-22.

Removing a faulty CTU2

Ensure that the preserve CTU2 calibration data feature is enabled and determinewhich calibration data exchange scenario applies before proceeding further (refer toEnabling the preserve CTU2 calibration data feature and CTU2 calibration proceduresin CTU2 calibration data exchange procedures respectively, later in this chapter).

If the preserve CTU2 calibration data feature is NOT enabled, for any reason. PerformSite verication procedures, Tx output power calibration.

The CTU2 transmit power, in Horizon II micro, is factory calibrated as a macro BTS(up to: 60 W for PGSM900, 63 W for EGSM900 and 50 W for DCS1800, in singledensity mode), prior to delivery.

7-20 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a CTU2

Use the max_tx_bts parameter to ensure the maximum Tx power is correctly setafter CTU2 replacement. For example; if using standard power option, set value = 5to 21, or high power option, set value = 0 to 21). See the chapter Site vericationprocedures, for Normal CTU2 VSWR and cell site power (CSPWR) calibration, Txoutput power calibration procedure.

Procedure 7-6 CTU2 removal

1 Disable the CTU2 transmit RF power by using the lock_device orshutdown_device command at the OMC-R or from a PC connected to the HIISC.

Refer to Technical Description: BSS Command Reference(68P02901W23) for information on usage and specific commands.

2 When the CTU2 has been shutdown, check that the yellow Tx STATUS LEDsare unlit.

3 Set the appropriate CTU2 circuit breaker to the OFF position or, if Horizon IImicro, the switch of the PSU to OUTPUT DISABLE. Ensure that the RADIOSTATUS LED is not lit

Ensure that RF power is OFF, before disconnecting RF cables. Severeburns may result if RF power is ON when cables are connected ordisconnected.

Unscrew the coaxial cable from the Tx OUT SMA connector at the top of theCTU2 front panel.

4 Unscrew the two CTU2 attachment screws using a T20 Torx driver.

5

The CTU2 weighs 5 kg. Handle with care.

Take care to avoid damaging the CTU2 rear connectors when handlingoutside of the cabinet.

Withdraw the CTU2 using the handle. Support the unit from underneath asit slides out.

68P02903W31-C 7-21

Aug 2007

Replacing a CTU2 Chapter 7: FRU replacement procedures

Fitting a replacement CTU2

Ensure that the transmit RF power of the correct CTU2 has been locked using thelock_device or shutdown_device command at the OMC-R or from a PC connected tothe HIISC, if a CTU2 is being tted to an unused slot in Horizon II macro or Horizon IImini.

Procedure 7-7 CTU2 replacement

1 Insert the replacement CTU2 module, taking care to locate the module on theguide rails. Push firmly into place.

2 Tighten both module attachment screws to 2.2 Nm torque, using a T20 Torxdriver.

The Tx cable has a 90° SMA connector at one end, and a straight SMAconnector at the other end. The 90° end is designed for connection tothe Tx port of the CTU2.

3 Screw the 90° SMA connector of the coaxial cable onto the Tx OUT SMAconnector at the top of the CTU2 front panel. Tighten to the 1 Nm torque.

4 Set the appropriate CTU2 circuit breaker to the ON position or, if Horizon IImicro, the switch of the PSU to OUTPUT ENABLE. The RADIO STATUS LED willflash green until the CTU2 is unlocked, and then remain lit.

5 Enable the CTU2 transmit RF power by using the unlock_device or ins_devicecommand at the OMC-R or from a PC connected to the HIISC. The appropriateTx STATUS LED (yellow) will be lit if the CTU2 is transmitting.

For an unlocked CTU2, if the RADIO STATUS LED is ashing greenor alternating red and green, boot code is downloading or ashreprogramming is taking place. Do not remove power or reset thecabinet until downloading has been completed as this will corrupt thenon-volatile memory.

If the boot code is corrupted, contact Motorola Customer NetworkResolution Centre requesting the boot code restoration procedure andthe appropriate boot code le.

6 Calibrate the CTU2 using the appropriate procedure, as described in CTU2calibration data exchange procedures later in this chapter.

7 Notify the OMC-R of base station availability and log the maintenance activity.

7-22 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a CTU2

CINDY commissioning tool

Although not required, many of the procedures described in this chapter can be carriedout automatically using the CINDY commissioning tool. Refer to the relevant CINDY userdocumentation for details.

68P02903W31-C 7-23

Aug 2007

CTU2 calibration data exchange scenarios Chapter 7: FRU replacement procedures

CTU2 calibration data exchange scenarios■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The process of uploading/downloading calibration data between the CTU2 and the CM databaseis automatic, but the procedure used is determined by one of the scenarios described inTable 7-2.

Table 7-2 CTU2 calibration scenarios and procedures

Scenario: Site initializationwith... Description Procedure

Used

Calibration data held inthe CM database, butwith invalid/no calibrationdata in the CTU2.(That is when a CTU2has been replaced with thepreserve calibration datafeature enabled.)

If a CTU2 malfunctions and has to bereplaced, the associated DRI is locked andthe malfunctioning CTU2 replaced with a newCTU2 while the cell remains in service. TheDRI is then unlocked. When the executivemessage Radio standby Success is receivedby the CA at the BTS, the database is queriedto determine if any valid offset data isstored. If any is found in the database, thisis downloaded to the new CTU2 and theCTU2 is allowed to come into service (B-U).The CTU2 will flash the new calibration datato keep a permanent copy, (so that a new CMdatabase can be repopulated after downloadingfrom the OMC-R.

PreserveCTU2calibrationdata.

Invalid/no calibrationdata held in the CMdatabase and no calibrationdata in the CTU2.(That is when a CTU2has been replaced withoutthe preserve calibration datafeature enabled.)

Once the CA at the BTS receives the executivemessage Radio standby Success, it checksthe CM database for valid offsets. If none exist,the BTS then queries the CTU2 for valid data. Ifnone exists in the CTU2, the CTU2 is broughtinto service but the Invalid transceivercalibration data alarm is triggered.

CTU2calibration.

Invalid/no calibrationdata held in the CMdatabase, but with validcalibration data in the CTU2.(That is when a CTU2 hasbeen replaced without thepreserve calibration datafeature enabled and has thenbeen calibrated.)

Initially a CTU2 is calibrated and the antennaoffsets stored within the CTU2. When the BTSinitializes and enters call processing mode,the Central Authority (CA) at the BTS queriesConfiguration Management (CM) to see if validoffset data exists. If no valid data exists, in theCM database, then the CTU2(s) are queried forthe offset data, which is sent through the RadioSignalling Link (RSL) to the CM at the BSC.

PreserveCTU2calibrationdata.

Invalid/no calibrationdata held in the CMdatabase and invalidcalibration data in the CTU2.(That is when an RF frontend component has beenreplaced, for example: aSURF 2, Mini-SURF or aduplexer.)

If an RF front end component malfunctionsand has to be replaced, the associated CTU2is locked and the malfunctioning componentreplaced with a new RF front end componentwhile the cell remains in service. Thecalibration data must be cleared and the CTU2recalibrated. The DRI is then unlocked.

CTU2recalibrationandPreserveCTU2calibrationdata.

7-24 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro CTU2 calibration data exchange scenarios

Test equipment required

The following equipment is needed to carry out the CTU2 calibration or recalibration procedures:

• An IBM compatible personal computer (PC).

• Terminal emulator software.

• A 9-way to 9-way cable (BTS).

• A 9-way to 25-way cable (BSC).

Commands used

Table 7-3 lists the commands required to carry out this procedure.

Table 7-3 CTU2 calibration commands

BTS Command Function

lock_device Prevents the device being used (see Notebelow).

unlock_device Enables the device to be used (see Notebelow).

OMC-R/BSC Command Function

store_cal_data Stores calibration data for all transceivers inthe master CM database at the BSC, which isthen used to update the CM database copyat the BTS.

disp_cal_data• When transceiver is locked: Displays

calibration data in the CM database forthe specified transceiver.

• When transceiver is unlocked: Displayscalibration data in the RAM of thespecified transceiver.

clear_cal_data Clears calibration data in the CM database atthe BSC and BTS for a specified transceiver.

• Use shutdown_device instead of lock_device if the CTU2 is currently active.Use ins_device instead of unlock_device if shutdown_device was used tolock the CTU2.

• If there is no RSL from the BTS to the BSC then a command will not be executedby the BSC, as the BSC has no knowledge of the command being entered.

All calibration data is stored in the master CM database at the BSC, which is then used toupdate the CM database copy at the BTS only if the data is valid.

68P02903W31-C 7-25

Aug 2007

Preserving CTU2 calibration Chapter 7: FRU replacement procedures

Preserving CTU2 calibration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the preserve CTU2 transceiver calibration feature, which uses commandsto store, display and clear calibration data. This feature is used on busy systems where there isa need to replace a CTU2 quickly and thus reduce system down time during peak hours.

Calibration data overview

This function enables malfunctioning CTU2s to be replaced without the need to remove the cellfrom service. The calibration offsets can be displayed and cleared using the disp_cal_dataand clear_cal_data commands.

Display calibration offsets data

The disp_cal_data command only displays offsets from the CTU2 if the DRI is in thebusy-unlocked (B-U) state. The GPROC CM database values are displayed when the CTU2 islocked or not busy. If the calibration values have been cleared and the CTU2 is disabled, theywill not be available on the specific RAM of the CTU2 or the CM database, and the response willbe NO CALIBRATION DATA AVAILABLE.

7-26 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Preserving CTU2 calibration

Store calibration data

The store_cal_data command sets a flag to indicate that the preserve calibration feature isenabled. When the CTU2 is unlocked and comes into service, the calibration values will becopied from the RAM in the CTU2 into the GPROC CM database. The values from the RAM inthe CTU2 will only be copied to the database if there are no calibration values in the GPROC CMdatabase, and if the CTU2 has valid calibration data to be copied.

If the GPROC CM database has calibration values for that specific CTU2, when the CTU2 isunlocked it will get a copy of these values from the CM database. Different calibration valuesfor the same CTU2 can exist in the CM database and the RAM in the CTU2, only when theCTU2 is in calibration mode.

Care has to be taken when calibrating a CTU2. To ensure that the values in the RAM of theCTU2 and CM database have the same calibration data, the existing values have to be clearedusing the clear_cal_data command before a calibration can be successful and the correctcalibration data saved. Calibration data is stored in the master CM database at the BSC, and isused to update the CM database copy at the BTS if it is valid.

Calibration values in the BSC CM database are lost if a new database is downloaded. In this casethe CM database will be repopulated from the calibration data held in the CTU2(s), providedthat the preserve calibration feature is enabled.

The store_cal_data command is a one off enable of the preserve calibration feature andcannot, subsequently, be disabled by a command. Disabling the feature can only be achievedby downloading a new database.

The value 0800H must be cleared from all the paths (columns of data) stored in theCTU2, otherwise the calibration data will not be uploaded to the CM database.

Clear calibration data

The clear_cal_data command removes the offsets from RAM and the database. To clear thedata from a CTU2 that is B-U in the network, the command is issued after the CTU2 is locked. Anew CTU2 being put into the network must first be allowed to become B-U and then locked,only after this will the command clear the calibration data for that CTU2. This is explained inthe calibration procedure.

68P02903W31-C 7-27

Aug 2007

Preserving CTU2 calibration Chapter 7: FRU replacement procedures

Calibration data format from the CM database

The format of the calibration data output from the CM database is described here. Thisinformation is provided in response to the command:

disp_cal_data <site_id> DRI <device_id> <device_id2> [<device_id3>]

For example:

disp_cal_data 63 dri 0 0 0

Where: is:

63 site

dri dri device

0 first dev_id

0 second dev_id

0 third dev_id

System response:

DRI ID: 0 0 0Data read from databaseStore Calibration Data: enabledCalibration Data (All values in Hex):Transmit Power Offsets = 0Receive System Data:Antenna Number 1 2 3 4 5 6---------------------------------------------

e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80e80, e80, e80, e80, e80, e80

7-28 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Preserving CTU2 calibration

The second line of the system response indicates whether the data is read fromthe CTU2 or the database. In the example above the information is read from thedatabase.

The number of rows of offset calibration data are as follows:

• EGSM900 - 22.

• PGSM900 – 22 (same number as EGSM with default data stored in EGSM frequencies).

• GSM1800 - 47.

68P02903W31-C 7-29

Aug 2007

Enabling the preserve CTU2 calibration data feature Chapter 7: FRU replacement procedures

Enabling the preserve CTU2 calibration data feature■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Determine the BSC/BTS configuration and cage slot allocation before starting any of thecalibration data exchange procedures.

• The preserve CTU2 calibration data feature must be enabled at either theOMC-R or the BSC, otherwise none of the calibration data exchange proceduresdescribed in Table 7-2 will work.

• Calibration data is interchangeable between the Horizon II equipment CTU2sand the Horizonmacro CTUs. This means that a CTU2 can be inserted in aHorizonmacro cabinet and the original CTU calibration data used.

Enabling the preserve feature at the OMC-R

Procedure 7-8 Enabling the preserve feature at the OMC-R

1 Log in to the required base site controller (BSC) at the OMC-R man-machineinterface (MMI).

2 To initiate the preserve feature type:store_cal_data <site_id>

Once the store_cal_data command has been used to enable thepreserve calibration feature there is no requirement to reissue thiscommand, unless a new database has been downloaded.

All calibration data will be stored in the master CM database at the BSC, which is then used toupdate the CM database copy at the BTS (if the data is valid).

7-30 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Enabling the preserve CTU2 calibration data feature

Enabling the preserve feature at the BSC

Procedure 7-9 Enabling the preserve feature at the BSC

1 Connect the 9-way to 25-way cable from the PC serial A port to the BSP TTY port.

2 At the PC start the terminal emulator program.

3 At the MMI prompt, enter the appropriate level change command and passwords.

4 At the MMI prompt type:store_cal_data <site_id>

Once the store_cal_data command has been used to enable thepreserve calibration feature there is no requirement to reissue thiscommand, unless a new database has been downloaded.

68P02903W31-C 7-31

Aug 2007

CTU2 calibration data exchange procedures Chapter 7: FRU replacement procedures

CTU2 calibration data exchange procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The procedures listed in Table 7-2 are described here in detail. All three procedures assumethat the preserve CTU2 calibration data feature (described previously) has been enabled.

Preserve CTU2 calibration data procedure

To replace a CTU2 using preserved calibration data, follow the procedures for CTU2replacement given previously in this chapter.

This procedure assumes that the store_cal_data command has been used on theCTU2 at some time previously while it was operational.

If valid calibration data stored in the CM database and invalid/no calibration data is stored inthe CTU2, then valid data is automatically downloaded into the RAM of the new CTU2. The datais also stored in the non-volatile CTU2 memory.

If invalid/no calibration data stored in the CM database and valid calibration data is stored inthe CTU2, then valid data is automatically uploaded to the CM database.

CTU2 calibration procedures

This procedure is used to put a new CTU2 into service. If recalibration of a working CTU2 isrequired, use the CTU2 recalibration procedures provided later in this chapter.

This covers EGSM and PGSM for 900 MHz as specified.

There are two stages to this procedure:

• Procedure 7-10 Calibrating the CTU2 on page 7-33.

• Procedure 7-11 Checking the CTU2 calibration on page 7-34.

7-32 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro CTU2 calibration data exchange procedures

Calibrating the CTU2

The CTU2 requires a code load prior to the calibration process. Wait untilthe CTU2 finishes the code load and stops flashing (in BUSY-UNLOCKED orENABLED-UNLOCKED state) before proceeding.

Procedure 7-10 Calibrating the CTU2

1 Lock all the DRIs in the same sector of the CTU2 to be calibrated. Always lockthe CTU2 providing the BCCH last, as this prevents the BCCH switchingto an alternative CTU2. Enter the following command for each of the DRIs.lock_device <site_id> DRI <device_id1> <device_id2 [<device_id3>]

2 Unlock the CTU2 to be calibrated.

3 Carry out bay level and Normal CTU2 VSWR and cell site power (CSPWR)calibration procedures, as described in the relevant section of this manual.Record the data.

4 Display the data in the CM database for the CTU2 that has been calibrated:disp_cal_data <site_id> DRI <device_id1>

5 Clear the data for the CTU2 to be calibrated:clear_cal_data <site_id> DRI <device_id1>

6 Confirm the data has been cleared from the CM database for the specified CTU2:disp_cal_data <site_id> DRI <device_id1>

NO DATA AVAILABLE

If there is a different response, ensure the CTU2 is in the LOCKEDstate and carry out from step 4 again.

7 Use the reset_device command to bring the calibrated radio into service.

68P02903W31-C 7-33

Aug 2007

CTU2 calibration data exchange procedures Chapter 7: FRU replacement procedures

Checking the CTU2 calibration

If the DRI does not become B-U because of the error, Tx Power Unachievable,please refer to the Tx output power calibration section of this document.

Procedure 7-11 Checking the CTU2 calibration

1 Unlock the DRI of the calibrated CTU2.

Ensure the previous calibration data has been cleared beforeunlocking the CTU2.

Enter the command:unlock_device <site_id> DRI <device_id1>Check that the calibrated CTU2 passes into BUSY-UNLOCKED state. The newcalibration data is uploaded to the CM database and is then used to updatethe copy at the BTS.

2 Check the calibration data of the DRI of the calibrated CTU2 against the valuesnoted in step 3 of the previous procedure.

Allow one minute after uploading for the values in the CM databaseat the BSC to be updated.

Enter the command:disp_cal_data <site_id> DRI <device_id1>The values seen should match the previous ones.

If the CTU2 is BUSY-UNLOCKED the data can be read directly fromthe CTU2. In ENABLED-UNLOCKED or LOCKED state calibrationdata is read from the CM database.

3 Make test calls in all timeslots of the new DRI to check audio quality and thenlock the tested DRI using the command:lock_device <site_id> DRI <device_id1>

Continued

7-34 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro CTU2 calibration data exchange procedures

Procedure 7-11 Checking the CTU2 calibration (Continued)

4 With the CTU2 LOCKED, ensure the calibration processhas been carried out correctly by checking that the CMdatabase at the BSC has been updated with the new values.Enter the command:disp_cal_data <site_id> DRI <device_id1>If the values seen match the previous ones go to step 6.If not go to step 5.

5 If the BSC database indicates

NO CALIBRATION DATA AVAILABLE:

• Issue the command: store_cal_data <site_id>

• Unlock the DRI, using the command: unlock_device <site_id> DRI<device_id1>

• Wait one minute for the BSC data to upload

• Lock the DRIs, using the command: lock_device <site_id> DRI<device_id1>

• Repeat from step 4

6 If everything is in order, the cell can be put back into service. Unlock all theDRIs in the same sector that were locked previously, using the command:unlock_device <site_id> DRI <device_id1> <device_id2 [<device_id3>]

CTU2 recalibration procedures

This procedure is used to recalibrate a working CTU2 when there is invalid or no calibrationdata held in the CM database, and invalid calibration data is present in the CTU2.

There are two stages to this procedure:

• Recalibrating the CTU2 on page 7-36.

• Checking the CTU2 recalibration on page 7-36.

68P02903W31-C 7-35

Aug 2007

CTU2 calibration data exchange procedures Chapter 7: FRU replacement procedures

Recalibrating the CTU2

Procedure 7-12 Recalibrating the CTU2

1 Lock all the DRIs in the same sector of the CTU2 to be calibrated. Always lockthe CTU2 providing the BCCH last, as this prevents the BCCH switchingto an alternative CTU2. Enter the following command for each of the DRIs.lock_device <site_id> DRI <device_id1> <device_id2 [<device_id3>]

2 Unlock the CTU2 to be calibrated.

3 Carry out bay level and Normal CTU2 VSWR and cell site power (CSPWR)calibration procedures, as described in the relevant section of this manual.Record the data.

4 Display the data in the CM database for the CTU2 that has been calibrated:disp_cal_data <site_id> DRI <device_id1>

5 Clear the data for the CTU2 to be calibrated:clear_cal_data <site_id> DRI <device_id1>

6 Confirm the data has been cleared from the CM database for the specified CTU2:disp_cal_data <site_id> DRI <device_id1>

NO DATA AVAILABLE

If there is a different response, ensure the CTU2 is in the LOCKEDstate and carry out from step 4 again.

7 Use the reset_device command to bring the calibrated radio into service.

Checking the CTU2 recalibration

If the DRI does not become B-U because of the error, Tx Power Unachievable,please refer to the Tx output power calibration section of this document.

7-36 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro CTU2 calibration data exchange procedures

Procedure 7-13 Checking the CTU2 recalibration

1 Unlock the DRI of the recalibrated CTU2.

Ensure the previous calibration data has been cleared beforeunlocking the CTU2.

Enter the command:unlock_device <site_id> DRI <device_id1>Check that the recalibrated CTU2 passes into UNLOCKED state. The newcalibration data is uploaded to the CM database and is then used to update thecopy at the BTS (even if the DRI does not have an RTF assigned).

2 Check the calibration data of the DRI of the recalibrated CTU2 against thevalues noted in step 3 of the previous procedure.

Allow one minute after uploading for the values in the CM databaseat the BSC to be updated.

Enter the command:disp_cal_data <site_id> DRI <device_id1>The values seen should match the previous ones.

If the CTU2 is BUSY-UNLOCKED the data can be read directly fromthe CTU2. In ENABLED-UNLOCKED or LOCKED state calibrationdata is read from the CM database.

3 Lock the tested DRI using the command:lock_device <site_id> DRI <device_id1>

4 With the CTU2 LOCKED (or in ENABLED-UNLOCKED state), ensure therecalibration process has been carried out correctly, by checking thatthe CM database at the BSC has been updated with the new values.Enter the command:disp_cal_data <site_id> DRI <device_id1>If the values seen match the previous ones go to step 6.If not go to step 5.

Continued

68P02903W31-C 7-37

Aug 2007

CTU2 calibration data exchange procedures Chapter 7: FRU replacement procedures

Procedure 7-13 Checking the CTU2 recalibration (Continued)

5 If the BSC database indicates

NO CALIBRATION DATA AVAILABLE:

• Issue the command:store_cal_data <site_id>

• Unlock the DRI, using the command:unlock_device <site_id> DRI<device_id1>

• Wait one minute for the BSC data to upload.

• Lock the DRIs, using the command: lock_device <site_id> DRI<device_id1>

• Repeat from step 4.

6 If everything is in order, the cell can be put back into service. Unlock all theDRIs in the same sector that were locked previously using the command:unlock_device <site_id> DRI <device_id1> <device_id2 [<device_id3>]

7-38 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Calibrating CTU2 bay level offset tables■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Follow this procedure to calibrate the bay level offset tables to compensate for the losses orgains due to preselectors and RF cabling from the antenna inputs to the CTU2 input.

All units are factory calibrated. This procedure is thus necessary only if one of the followingchanges occur:

• RF front end equipment is changed.

• The site is reconfigured.

• High power duplexers are fitted.

The procedures contained in Calibrating CTU2 bay level offset tables are to calibratea single CTU2. Repeat the procedures for each CTU2 affected by the changes listedabove.

Test equipment required

The following test equipment is required:

• An IBM compatible personal computer (PC).

• Terminal emulator software.

• A 50 ohm 100 W dummy load.

• A signal generator (0 to 2 GHz).

• A 9-way to 9-way HIISC/CTU2 cable.

• A 9-way to 9-way DSP MMI/RSS CTU2 cable.

When using test equipment observe the following points:

• All test equipment and test leads must be calibrated annually by a recognizedlaboratory.

• Test equipment and test leads must not be calibrated in the eld.

• Do not optimize Motorola cellular base stations with test equipment that isbeyond its calibration due date.

• Allow test equipment to warm up for 30 minutes before use.

68P02903W31-C 7-39

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Commands used

Table 7-4 details the MMI commands that must be used to carry out the procedure:

The symbol 0 used in the commands in this procedure is a zero.

Table 7-4 MMI commands for CTU2 Rx bay level offset calibration

BSS MMI command Function

ins_device Initializes the device, bringing it into service.

lock_device Prevents the device being used.

unlock_device Frees the device for further use.

clear_cal_data Clears previously stored calibration data for aspecified radio unit on a per DRI basis.

chglev Changes the DSP MMI security level.

cal_test_mode on Enter calibration test mode.

fm test_mode on Puts the DSP fault management module intest mode.

fm_test block none 0xff Blocks all DSP fault management alarms.

set carrier cara Switches DSP MMI control to carrier A.

set_carrier carb Switches DSP MMI control to carrier B.

ts a txp 0xff Turns off Tx closed loop power control for thecurrent carrier.

cal_config rx_cab_antennas Configures which carriers will be calibratedby the Rx cabinet calibration procedure.

cal_config rf_band p900 Override for PGSM Only Duplexer.

cal_cabinet rx_cab Executes the Rx cabinet calibration procedure.

cal_store_1 Stores the calibration data.

ts a rx_br_sel 2 Sets the second carrier to Rx double densitymode so that the calibration procedure iseffective for both branches and both carriers.

cal_status tall Displays: the flash retrieval status, thedatapool valid flag and the checksum for allcalibration datapools.

disp_act_alarm Displays active alarms at the specified site.

disp_cal_data When transceiver is locked:Displays calibration data in the CMdatabase for the specified transceiver.When transceiver is unlocked:Displays calibration data in the RAM ofthe specified transceiver.

7-40 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Commands in the procedures in this section are frequently presented in the format: Command<site_id> dri <cell_id> <DRI_number> 0

Where: is:

<site_id> the number of the site logged into.

<cell_id> the antenna/relative cell number (0to 5 for Horizon II macro), (0 to 1 forHorizon II mini) or (0 for Horizon IImicro).

<DRI_number> DRI number of the transceiver.

Preparation for Rx bay level calibration

The RF path has to be prepared for bay level calibration. All DRIs in the site must be locked,the CTU2 has to be reset, a dummy load must be connected if there is no antenna, and allalarms must be disabled.

In the Horizon II macro, a transceiver may consist of one or two DRIs. If a CTU2 is configuredfor double density mode (two DRIs), Tx cabinet calibration needs to be performed only on thefirst DRI because the internal difference value keeps the power of the second carrier equalto the first.

The internal difference value is not visible through the MMI command, and the TXoffset reported by disp_cal_data for the second DRI is a copy of the value for the firstDRI. Dual carrier calibration can verify that both carriers transmit at equal power.

The following will determine whether a CTU2 is configured as single or double densitytransceiver and which DRI numbers correspond to which CTU2s.

At the BSC TTY, change to Level 3 and at the MMI-RAM> prompt type the following:

disp_eq <site_id> dri <cell_id> <DRI_number> 0

For single density CTU2s the output will look similar to the following:

[05/02/03 14:42:37] MMI-RAM 0115 -> disp_eq 81 dri 0 0

DRI identifier: 0 0

DRI Density[dri_density]: SINGLE

Cabinet identifier: 0

Type of connection to the BTP: MASTER

Port to which the TCU is connected[tcu_port]: 0

RTF identifier[pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell[antenna_select]: 1

68P02903W31-C 7-41

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Tuneable combining used: No

The diversity flag for this DRI is[diversity_flag]: 0

The fm cell type is[fm_cell_type]: 0

For double density CTU2s the output will look similar to the following:

[05/02/03 14:47:55] MMI-RAM 0115 -> disp_eq 81 dri 0 1

DRI identifier: 0 1

DRI Density[dri_density]: DOUBLE

Associated DRI identifier: 0 2

Cabinet identifier: 0

Type of connection to the BTP: MASTER

Port to which the TCU is connected[tcu_port]: 1

RTF identifier[pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell[antenna_select]: 1

Tuneable combining used: No

The diversity flag for this DRI is[diversity_flag]: 0

The fm cell type is[fm_cell_type]: 0

In this case we see that DRI 0 1 is a double density CTU2 and is associated with DRI 0 2.

Repeating the command for DRI 0 2 yields the following:

[05/02/03 14:48:07] MMI-RAM 0115 -> disp_eq 81 dri 0 2

DRI identifier: 0 2

DRI Density [dri_density]: DOUBLE

Associated DRI identifier: 0 1

Cabinet identifier: 0 Type of connection to the BTP: MASTER

Port to which the TCU is connected [tcu_port]: 1

RTF identifier [pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell [antenna_select]: 1

Tuneable combining used: No

The diversity flag for this DRI is [diversity_flag]: 0

The fm cell type is [fm_cell_type]: 0

Thus, in this example, DRI 0 1 and DRI 0 2 are on the same CTU2.

In the case of the single density CTU2, cabinet calibration will be performed once on the DRI.

In the case of the double density CTU2, cabinet calibration is still performed on only one of thetwo DRIs, but the other DRI must be locked for the procedures to be carried out. Furthermore,the clear_cal_data commands must be issued for both DRIs.

7-42 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Rx bay level calibration procedure

There are three stages to the Rx bay level calibration procedure. To calibrate each CTU2,complete the following procedures.

• Procedure 7-14 Rx bay level calibration test equipment connection on page 7-43.

• Procedure 7-15 Rx bay level calibration test configuration on page 7-44.

• Procedure 7-16 Rx bay level calibration and calibration data storage on page 7-47.

To connect the test equipment to each CTU2, proceed as follows:

If the DRI does not become B-U because of the error, Tx Power Unachievable,please refer to the Tx output power calibration section of this document.

Follow the steps described in Procedure 7-14 to check Rx bay level calibration test equipmentconnection.

Procedure 7-14 Rx bay level calibration test equipment connection

1 Connect the 9-way to 9-way HIISC cable from the PC serial A port to theHIISC TTY port.

2 At the PC, start the terminal emulator program.

3 Lock all DRIs in the sector. At the HIISC TTY, change to Level 3 and at the

MMI-RAM>

prompt typelock_device <site_id> dri <cell_id> <DRI_number> 0

Always lock the transceiver providing the BCCH last as this preventsthe BCCH being switched to alternate transceivers.

Continued

68P02903W31-C 7-43

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Procedure 7-14 Rx bay level calibration test equipment connection (Continued)

4 If a Tx antenna is not connected to the transceiver under test, connect a 50ohm 100 W dummy load to the Tx port.

5 Unlock the CTU2 to be calibrated. Change to Level 3 and at the

MMI-RAM>

prompt type:ins_device <site_id> dri <cell_id> <DRI_number> 0

In the case of a double density CTU2, Rx cabinet calibration onlyneeds to be performed on one of the two DRIs. The other DRI mustremain locked.

6 Connect a serial port on the PC to the TTY Interface port on the CTU2 to becalibrated using the 9-way to 9-way DSP MMI/RSS cable. If necessary, switchthe 9-way to 9-way DSP MMI/RSS cable from providing RSS connectivity toproviding DSP connectivity.

Follow Procedure 7-15 to configure each CTU2 for test.

Procedure 7-15 Rx bay level calibration test conguration

1 At the

DSP MMI>

prompt typechglevThen enter the following password:pizza

2 Enter calibration test mode and disable alarmsby typing the following commands:cal_test_mode onfm test_mode onfm_test block none none 0xff

3 If required, set the second carrier to Rx double density mode by typing thefollowing commandts a rx_br_sel 2This enables the calibration procedure to take effect on both branches and bothcarriers.

Continued

7-44 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Procedure 7-15 Rx bay level calibration test conguration (Continued)

4 Turn the CTU2's transmitters off by typing the following at the

DSP MMI>

prompt:set_carrier carats a txp 0xffset_carrier carbts a txp 0xffset_carrier cara

The response at the

DSP MMI

should be:

CTU2.carA.ts_0>

5 Set the quad diversity by entering the following command at the

DSP MMI>

prompt:cal_config quad_diversity yesThe response at the

DSP MMI

should be:

Setting quad diversity to ON

The command is valid only if 4 branch Rx diversity is enabled in theload and within the DRI, the diversity_flag is set to 2.

6 Configure which Rx antennas are to be calibrated using the following command:cal_config rx_cab_antennas <antenna> <antenna><antenna> <antenna> <antenna><antenna>Where <antenna> is one of the following:

• all - All antennas.

• 0a - Antenna 0A.

• 1a - Antenna 1A.

• 2a - Antenna 2A. *

• 0b - Antenna 0B.

Continued

68P02903W31-C 7-45

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Procedure 7-15 Rx bay level calibration test conguration (Continued)

• 1b - Antenna 1B.

• 2b - Antenna 2B. *

• 0c- Antenna 0C. *

• 1c - Antenna 1C. *

• 2c - Antenna 2C. *

• 0d - Antenna 0D. *

• 1d - Antenna 1D. *

• 2d - Antenna 2D. *

Up to twelve antenna options can be specified, separated by spaces. Theoption all is equivalent to 0A 1A 2A 0B 1B 2B 0C 1C 2C 0D 1D 2D.

For example, to calibrate antennas 0A and 0B, type the following command:cal_config rx_cab_antennas 0a 0bThe response will be:

Setting RX Cabinet Calibration antennas to: 0A 0B.

To calibrate all antennas, type the following command:cal_config rx_cab_antennas allThe response will be:

Setting RX Cabinet Calibration antennas to: All

*Antenna connections 2A, 2B, and 0C to 2D are applicable to HorizonII macro only.

Antennas 0C - 2D correspond to the antenna inputs on the rear SURF2 module.The C antennas are the A antenna positions on the rear SURF2 and the Dantennas are the B antenna positions on the rear SURF2.

Antennas 0C - 2D will be ignored by the calibration routine unlessthe cabinet has a rear SURF2 module and is configured for 4 BranchRx Diversity.

7-46 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Follow the Procedure 7-16 to calibrate the Rx bay level for each CTU2.

Procedure 7-16 Rx bay level calibration and calibration data storage

1

900 MHz radios take the EGSM RF band from the EID by default.If PGSM duplexers are tted, the radio needs to be congured forthe PGSM band.

To set the RF band to PGSM900 enter the following command:cal_config rf_band p900

The following message will be displayed on the screen:

Setting RF band to PGSM900

2 Start the Rx cabinet calibration procedure by typing the following commandat the

DSP MMI >

prompt.cal_cabinet rx_cab

The following message will be displayed on the screen. This includesthe SURF2, or Mini-SURF, antenna connector to which thesignal generator should be connected (shown in bold text).

cal_cabinet rx_cab

Enabling receive

[c A, b 0] Setting RX diversity switch to double density

(inject carrier A into carrier B)

Enabling transmit

Number of frequency groups=47

Please connect the signal generator to branch 0A

Press return when the signal generator is connected.

Press any key to continue

Continued

68P02903W31-C 7-47

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Procedure 7-16 Rx bay level calibration and calibration data storage (Continued)

3 When the signal generator is connected to the appropriate SURF2, orMini-SURF, antenna connector and configured, press ENTER at the

DSP MMI >

prompt.

The on screen instructions will list the new signal generatorsettings required (shown in bold in the sample output below).

Please set the signal generator to

POWER -65.2000 dBm

FREQ 1710.8052 MHz

Press any key to continue

Be sure to allow for any loss in the cables connecting the signal generator tothe antenna connector. For example, if the cables have a loss of 1.5 dB andyou are asked to provide -65.2 dBm, set the signal generator to -63.7 dBm.Make the appropriate adjustments and then press ENTER. The readings foreach test frequency will look something like the following:

IQ average reading C0B0: 2565696, 0x00272640

IQ average reading C1B0: 2762909, 0x002a289d

Measured gain: 14.76 (0x0ec2)

Measured gain: 15.69 (0x0fb0)

Frequency group 2 of 47

Please set the signal generator to

POWER -65.2000 dBm

FREQ 1712.4052 MHz

Press any key to continue

4 Repeat the calibration procedure in step 3 for all the appropriate testfrequencies, listed in Table 7-5 on page 7-49 for EGSM900 and PGSM900,and Table 7-6 on page 7-50 for GSM1800 in Test frequency tables on page7-49, (22 for EGSM, 16 for PGSM and 47 for DCS1800).

Continued

7-48 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Procedure 7-16 Rx bay level calibration and calibration data storage (Continued)

5 Once all frequencies have been calibrated, the program will request the signalgenerator is moved to the next SURF2 or Mini-SURF antenna connection(Refer to example message in step 2 of this procedure).

6 Repeat step 3 to step 5, of this procedure, for each antenna connection, untilall frequencies on all antennas have been calibrated.

7 Type the following command at the

DSP MMI>

prompt when the calibration procedure has been completed.cal_store_1After a few seconds delay (up to 16 seconds), the result of the data storage isdisplayed on the screen in the format:

cal_store_1

PASS

CTU2.carA.ts_0>

8 Take the CTU2 out of test mode by entering the following command:fm test_mode off

9 Connect to the BSC MMI and enter the following command to lock the CTU2that has been calibrated:lock_device <site_id> dri <cell_id> <DRI_number> 0

10 Clear the calibration data for both DRIs using the following command:clear_cal_data <site_id> dri <cell_id> <DRI_number> 0The clear_cal_data command clears all calibration data out of the CMdatabase. This is required to override the preserve calibration feature, ifenabled.

To calibrate additional CTU2s in the same Horizon II base station, move the 9-way to 9-way DSPMMI/RSS cable to the CTU2 TTY port of the next CTU2 to be calibrated and repeat the three Rxbay level calibration procedures from step 4 of Procedure 7-14.

Test frequency tables

The EGSM900, PGSM900 and DCS1800, and channel numbers and test frequencies are listed inTable 7-5 and Table 7-6 on page 7-50: PGSM subset denoted with asterisks.

Table 7-5 EGSM900 and PGSM900 test frequencies

Channel Frequency (MHz) Channel Frequency (MHz)

978 880.8052 43* 898.4052

986 882.4052 51* 900.0052

994 884.0052 59* 901.6052

1002 885.6052 67* 903.2052

1010 887.2052 75* 904.8052

Continued

68P02903W31-C 7-49

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Table 7-5 EGSM900 and PGSM900 test frequencies (Continued)

Channel Frequency (MHz) Channel Frequency (MHz)

1018 888.8052 83* 906.4052

03* 890.4052 91* 908.0052

11* 892.0052 99* 909.6052

19* 893.6052 107* 911.2052

27* 895.2052 115* 912.8052

35* 896.8052 123* 914.4052

Table 7-6 GSM1800 test frequencies

Channel Frequency (MHz) Channel Frequency (MHz)

515 1710.8052 707 1749.2052

523 1712.4052 715 1750.8052

531 1714.0052 723 1752.4052

539 1715.6052 731 1754.0052

547 1717.2052 739 1755.6052

555 1718.8052 747 1757.2052

563 1720.4052 755 1758.8052

571 1722.0052 763 1760.4052

579 1723.6052 771 1762.0052

587 1725.2052 779 1763.6052

595 1726.8052 787 1765.2052

603 1728.4052 795 1766.8052

611 1730.0052 803 1768.4052

619 1731.6052 811 1770.0052

627 1733.2052 819 1771.6052

635 1734.8052 827 1773.2052

643 1736.4052 835 1774.8052

651 1738.0052 843 1776.4052

659 1739.6052 851 1778.0052

667 1741.2052 859 1779.6052

675 1742.8052 867 1781.2052

683 1744.4052 875 1782.8052

691 1746.0052 883 1784.4052

699 1747.6052

7-50 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Site restoration

After the bay level calibration is completed, restore the site by the following procedure.

If the DRI does not become B-U because of the error, Tx Power Unachievable,please refer to the Tx output power calibration section of this document.

Procedure 7-17 Post Rx bay calibration site restoration

1 Remove the signal generator and dummy load and reconnect the site RF cables.

2 Remove the 9-way to 9-way cable from the TTY interface port on the CTU2and connect to the HIISC TTY port.

3 Type:reset_device <site_id> dri <Cell_id> <DRI_identity> 0The CTU2 is now in the BUSY-UNLOCKED state.

4 Type:disp_act_alarm <site_id> dri <Cell_id> <DRI_identity> 0Confirm that there is no DRI 218 alarm. If there is a DRI 218 alarm, redo thewhole bay level calibration procedure.

5 Remove the 9-way to 9-way cables from the HIISC TTY port and connect tothe TTY interface port on the CTU2.

6 At the DSP MMI prompt type:chglevpizza(this is a password and appears on screen as *****).

7 Verify the calibration result and datapool valid flag by typingcal_status tallat the command line and comparing with theExample of calibration status on page 7-53.Confirm that the Result and Valid Checksum values are pass and valid,respectively, for both RX CAB A and RX CAB B.

Continued

68P02903W31-C 7-51

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Procedure 7-17 Post Rx bay calibration site restoration (Continued)

If these values are incorrect the appropriate calibration must berepeated.

8 Verify the antenna calibration data or transmit power offset by typingdisp_cal_data <site_id> DRI <device_id> <device_id2> [<device_id3>]at the command line and comparing with the Exampleof calibration data format (for antenna 0) on page 7-54.Confirm that the values for those antennas calibrated are not e80

If the entire row for a calibrated antenna is e80 this antenna mustbe calibrated again.

9 Remove the 9-way to 9-way cable from the TTY interface port on the CTU2.

7-52 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

Example of calibration status

Entering the cal_status tall command will give a result similar to the example below:

System response:

CTU2.carA.ts_0>cal_status tallCal Ca Br Status Result Valid.Checksum Ver S/HC---------------------------------------------------------------------RF Lop A 0 pass valid 0x0672d5b5 1 / 1RF Lop B 0 pass valid 0x0d7b5025 1 / 1RX RF A 0 pass valid 0x2ae0b9fc 1 / 1RX RF A 1 pass valid 0x2bb91f4a 1 / 1RX RF B 0 pass valid 0x2c1ed905 1 / 1RX RF B 1 pass valid 0x2b063b6b 1 / 1RX IF A 0 pass valid 0xc8bc3caf 1 / 1RX IF A 1 pass valid 0xc8d99f37 1 / 1RX IF B 0 pass valid 0xc8dadb3f 1 / 1RX IF B 1 pass valid 0xc8bfbd0a 1 / 1RX FR A 0 pass valid 0xa8fe3af6 1 / 1RX FR A 1 pass valid 0xa8e8ba39 1 / 1RX FR B 0 pass valid 0xa8fb5db7 1 / 1RX FR B 1 pass valid 0xa8f593e0 1 / 1RX CAB A 0 pass valid 0x53703256 0 / 1RX CAB B 0 pass valid 0x45562835 0 / 1TX VVA A 0 pass valid 0xb0be7eb2 1 / 1TX VVA B 0 pass valid 0x96686359 1 / 1TX DSA A 0 pass valid 0x01a775df 1 / 1TX DSA B 0 pass valid 0x01a7863a 1 / 1TX FP A 0 pass valid 0x09e81286 1 / 1TX FP B 0 pass valid 0x07c8ee22 1 / 1TX Ver A 0 pass valid 0x064b1162 1 / 1TX Ver B 0 pass valid 0x063b5e9a 1 / 1TX CAB A 0 pass valid 0x019e2da9 1 / 1TX CAB B 0 pass valid 0x01bd2da9 1 / 1PA Det A 0 pass valid 0x15cc24be 1 / 1PA Det B 0 pass valid 0xd7dc8932 1 / 1PA VVA A 0 pass valid 0xda5d5f94 1 / 1

68P02903W31-C 7-53

Aug 2007

Calibrating CTU2 bay level offset tables Chapter 7: FRU replacement procedures

Example of calibration data format (for antenna 0)

Entering the disp_cal_data <site_id> DRI <device_id> <device_id2> [<device_id3>]command, for example disp_cal_data 63 dri 0 0 0 will give a result similar to the examplebelow:

Where: is:

63 site

dri dri device

0 first dev_id

0 second dev_id

0 third dev_id

The example below shows the data from a calibration when Only antenna 0 wascalibrated (It is recommended that all antennas are calibrated, but it is permissible tocalibrate only the antennas to be used).

In the following example: antenna number 1 represents antenna 0A, antenna number2 represents antenna 1A, antenna number 3 represents antenna 2A, antenna number4 represents antenna 0B, antenna number 5 represents antenna 1B, antenna number6 represents antenna 2B.

7-54 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating CTU2 bay level offset tables

System response:

DRI ID: 0 0 0Data read from databaseStore Calibration Data: enabledCalibration Data (All values in Hex):Transmit Power Offsets = 12Receive System Data:Antenna Number 1 2 3 4 5 6---------------------------------------------

a4b, e80, e80, a7b, e80, e80a3e, e80, e80, aff, e80, e80a5d, e80, e80, b45, e80, e80a8e, e80, e80, b5e, e80, e80aca, e80, e80, b4b, e80, e80ae8, e80, e80, b64, e80, e80af3, e80, e80, b61, e80, e80af2, e80, e80, b8b, e80, e80ae3, e80, e80, b65, e80, e80ac0, e80, e80, b65, e80, e80a97, e80, e80, b46, e80, e80a70, e80, e80, ae7, e80, e80a2d, e80, e80, a6b, e80, e809f6, e80, e80, a28, e80, e809b7, e80, e80, 95e, e80, e80954, e80, e80, 91d, e80, e80943, e80, e80, 909, e80, e80921, e80, e80, 8e3, e80, e80911, e80, e80, 8d5, e80, e808ef, e80, e80, 8b7, e80, e808d0, e80, e80, 8a1, e80, e80899, e80, e80, 855, e80, e80

68P02903W31-C 7-55

Aug 2007

Replacing a Mini-SURF module Chapter 7: FRU replacement procedures

Replacing a Mini-SURF module■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

A single Horizon II mini or Horizon II micro can contain only one 900 MHz or 1800 MHzMini-SURF module. Replacement of a Mini-SURF can take place only after the equipment hasbeen taken out of service, in agreement with the OMC-R.

Replacement procedures for a Mini-SURF

There are two stages to this procedure:

• Procedure 7-18 Removing a faulty Mini-SURF on page 7-56.

• Procedure 7-19 Fitting a replacement Mini-SURF module on page 7-57.

The Mini-SURF is hot swap capable. However, the associated circuit breaker on theMCBM is to be operated on Horizon II mini prior to replacement.

Removing a faulty Mini-SURF

Procedure 7-18 Removing a faulty Mini-SURF

1 Disable the CTU2 transmit RF power by using the lock_device orshutdown_device command at the OMC-R or from a PC connected to the HIISC.

2 Trip the associated circuit breaker on the MCBM, on Horizon II mini equipment.

3 Make a note of the RF cable connections to the Mini-SURF module to enablecorrect reconnection to the replacement module.

4

Before disconnecting RF cables, ensure that RF power is OFF sincedisconnecting the RF cables with power ON could result in severeburns.

Disconnect the coaxial RF cables by carefully unscrewing and pulling them outof the module sockets.

Continued

7-56 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a Mini-SURF module

Procedure 7-18 Removing a faulty Mini-SURF (Continued)

5 Using a Torx driver, unscrew the two T25 captive screws holding the Mini-SURFmodule to the top of the cabinet.

6 Pull the Mini-SURF module out of the slot.

Fitting a replacement Mini-SURF module

Procedure 7-19 Fitting a replacement Mini-SURF module

1 Transfer the protective caps on the RF connectors from the replacement moduleto the faulty module.

2 Insert the replacement Mini-SURF module into the slot. Take care to avoidtrapping cables as the module is seated.

3 Tighten the two captive T25 screws to the 2.2 Nm torque.

4

Ensure that RF power is OFF, before reconnecting RF cables. Severeburns may result if RF power is ON when RF cables are reconnected.

Reconnect the coaxial RF cables to the positions noted in the removal procedure.Tighten to the correct torque.

5 Reset the CTU2 by:

• Horizon II mini – Resetting the associated circuit breaker on the MCBM.

• Horizon II mini – Switching the power supply off and back on again.

Each RADIO STATUS LED will flash green for about two minutes, and thenremain lit.

6 Enable the CTU2 transmit RF power by using the unlock_device orins_device command at the OMC-R or from a PC connected to the HIISC. Theappropriate Tx STATUS LED (yellow) will be lit if the CTU2 is transmitting.

7 Carry out bay level procedures, as described in the relevant section of thismanual. Record the data.

8 Notify the OMC-R of base station availability and log the maintenance activity.

The Mini-SURF module replacement is now complete.

68P02903W31-C 7-57

Aug 2007

Replacing a Mini-SURF module Chapter 7: FRU replacement procedures

View of the Mini-SURF

Figure 7-10 shows the connectors on the Mini-SURF module.

Figure 7-10 Mini-SURF, showing connector details

7-58 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a Tx block

Replacing a Tx block■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Only a single DUP or PGSM duplexer is used in Horizon II micro. The slot for DUP/PGSMduplexers is at the top of the secondary cage in a Horizon II micro, behind the CTU2.

Replacing a Tx block requires removal of RF transmitter power for the CTU2. It is thereforeadvisable to perform this procedure during periods of low traffic. Notify the OMC-R of imminentrepair activity.

It is important to ensure that all Tx block/plate screw locations have a screw in place which istightened to the correct torque. This is to ensure the maximum quality of EMC and generalcontainment.

Location of the Tx blocks

Figure 7-11 shows the location of the DUP or PGSM duplexer.

68P02903W31-C 7-59

Aug 2007

Replacing a Tx block Chapter 7: FRU replacement procedures

Figure 7-11 Location of DUP/PGSM duplexer

7-60 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a Tx block

Tx block connectors

Table 7-7 lists the various connector types found on the Tx blocks used in Horizon II microenclosures.

Table 7-7 Connectors for each type of Tx block

Tx block Input connector Output connector

DUP or PGSM duplexer 1 x SMA 1 x 7/16 Tx/Rx to antenna1 x N-type to mini SURF

Replacing a DUP or PGSM duplexer

There are two stages to this procedure:

• Procedure 7-20 Removing a faulty DUP/PGSM duplexer on page 7-63.

• Procedure 7-21 Fitting a replacement DUP/PGSM duplexer on page 7-64.

68P02903W31-C 7-61

Aug 2007

Replacing a Tx block Chapter 7: FRU replacement procedures

View of the duplexer (DUP)

Figure 7-12 shows a duplexer (DUP) used in the Horizon II micro enclosure.

Figure 7-12 View of the duplexer

7-62 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a Tx block

Removing a faulty DUP/PGSM duplexer

Procedure 7-20 Removing a faulty DUP/PGSM duplexer

1 Locate the faulty DUP/PGSM duplexer, and note the RF cable connections toenable correct reconnection to the replacement module.

2 Disable the CTU2 transmit RF power by using the shutdown_device commandat the OMC-R or from a PC connected to the HIISC.

Refer to Technical Description: BSS Command Reference(68P02901W23) for information on usage and specific device codes.

3 When the CTU2 has been shutdown, check that the Tx status LED (yellow)is unlit.

4 Set the PSU switch to OUTPUT DISABLE. The ACTIVE LED will extinguish.Ensure that each RADIO STATUS LED is unlit.

5

Before disconnecting RF cables, ensure that RF power is OFF sincedisconnecting the RF cables with power ON could result in severeburns.

Disconnect the coaxial RF cables on the face of the unit by carefully unscrewingand pulling them out of the DUP/PGSM duplexer sockets.

6 Using a 6mm spanner, disconnect the CTU2 Tx out SMA connector andstraighten the bend in the cable.

7 Using a T20 Torx driver, unscrew the two captive M4 Torx screws holding theDUP/PGSM duplexer to the enclosure.

Continued

68P02903W31-C 7-63

Aug 2007

Replacing a Tx block Chapter 7: FRU replacement procedures

Procedure 7-20 Removing a faulty DUP/PGSM duplexer (Continued)

8

Handle the Tx blocks, which can weigh as much as 5 kg, with care.

• Ensure that the CTU2 Tx cable does not catch on internalequipment or structure.

• Do not use excessive force when removing duplexers.

Pull the DUP/PGSM duplexer from the back panel using its lifting handles.

Fitting a replacement DUP/PGSM duplexer

Procedure 7-21 Fitting a replacement DUP/PGSM duplexer

1 Transfer the protective caps on the RF connectors from the replacementDUP/PGSM duplexer to the faulty unit.

2 Transfer the CTU2 Tx cable from the faulty DUP/PGSM duplexer to thereplacement unit. Tighten the SMA connector to 1 Nm torque, using a 6 mmtorque spanner.

3

To prevent damage to the CTU2 Tx cable, care mast be taken that itdoes not catch on internal equipment or structure.

Carefully insert the replacement DUP/PGSM duplexer into its location, feedingthe CTU2 Tx cable along the top of the enclosure, adjust alignment for theretaining screws.

4 Tighten the two captive M4 Torx fastener that secure the duplexer to theenclosure, to 2.2 Nm torque, using a T20 Torx driver.

Continued

7-64 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a Tx block

Procedure 7-21 Fitting a replacement DUP/PGSM duplexer (Continued)

5

Ensure that RF power is OFF, before reconnecting RF cables. Severeburns may result if RF power is ON when RF cables are reconnected.

Reconnect the coaxial RF cables, on the face of the unit, to the positions notedin the removal procedure. Tighten to the correct torque, (3.4 Nm for N-typesand 25 Nm for 7/16).

6 Reconnect the CTU2 Tx out SMA connector, using a 6 mm torque spanner.Tighten to 1 Nm torque.

7 Set the front panel switch to OUTPUT ENABLE. Check that the ACTIVE LEDis lit. Each RADIO STATUS LED will flash green for about two minutes, andthen remain lit.

8 Enable the CTU2 transmit RF power by using the ins_device command at theOMC-R or from a PC connected to the HIISC. The appropriate Tx STATUS LED(yellow) will be lit if the CTU2 is transmitting.

9 Carry out bay level and Normal CTU2 VSWR and cell site power (CSPWR)calibration procedures, as described in the relevant section of this manual.Record the data.

10 Notify the OMC-R of base station availability and log the maintenance activity.

68P02903W31-C 7-65

Aug 2007

Digital module replacement Chapter 7: FRU replacement procedures

Digital module replacement■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

In Horizon II micro a faulty master HIISC, XMUX or site expansion board can not be hotswapped without affecting normal operation, although doing so will not harm the module.

Removal of a faulty digital module that is still partially functional, will affect service. Informthe OMC-R before replacing such modules.

Location of digital modules

Figure 7-13 Diagram of digital module locations

7-66 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Digital module replacement

Replacing digital modules

HIISC removal during ash memory programming may result in boot code corruption.This is only repairable by returning the HIISC to Motorola. For this reason, the HIISCshould not be removed while the code load is taking place, indicated by ashing redand green front panel LEDs.

There are two stages to this procedure:

• Procedure 7-22 Removing a faulty digital module on page 7-68.

• Procedure 7-23 Fitting replacement digital module on page 7-69.

68P02903W31-C 7-67

Aug 2007

Digital module replacement Chapter 7: FRU replacement procedures

Removing a faulty digital module

Procedure 7-22 Removing a faulty digital module

An earthing wrist strap must be worn when handling digital modules. ESP earthingconnection points are provided at the top left on the front of the enclosure and atthe top right on the rear.

1 If the faulty digital module is still partially functional, inform the OMC-R beforeproceeding.

2 Locate the faulty module.

3 Site expansion boards onlyRecord location of any fibre optic cable connections tothe module, to enable correct reconnection to the replacement module.

4 Site expansion boards only

There is a possibility of laser radiation when bre optic cables aredisconnected. Do not look directly into cables with or without theuse of any optical aids. Radiation can come from either the datain/out connectors or unterminated bre optic cables connected to datain/out connectors.

Remove strain relief clips and disconnect each fibre optic cable by gentlypushing the knurled connector in and rotating it through a quarter turnanticlockwise to disengage, then withdraw the cable carefully.

It is advisable to protect the tips of the fibre optic cables with aprotective cover and secure the cables to one side.

5 For the HIISC/XMUX or alarm module, unseat the module by gripping theupper and lower pair of ejectors between the thumb and first finger of eachhand, then gently squeeze and pull on the ejectors until the module releases atthe top and bottom of the front panel and unplugs from the rear connector.Carefully slide the module from its location and place it in an anti-static storagecontainer.

6 For the site expansion board, undo the single M4 attachment screw and carefullypull the board out of its slot using the handles provided and place it in ananti-static storage container.

7-68 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Digital module replacement

Fitting replacement digital module

Procedure 7-23 Fitting replacement digital module

1 Remove the replacement module from the anti-static storage container.

2 For the HIISC/XMUX or alarm module, slide the module into the guide rails andpush firmly into place. The ejectors will audibly click into place as confirmationof correct insertion.

3 For the site expansion board, insert the board into its slot using the handlesprovided. Ensure the midplane interface connector at the rear is firmly seatedin position and then tighten the M4 attachment screw to the 2.2 Nm torqueusing a Torx driver.

4 Site expansion boards onlyConnect any fibre optic cables by inserting theconnector and rotating a quarter turn clockwise to engage. Fit strain relief clipsaround the fibre optic cables and secure to one of the site expansion boardhandles (slots are provided in the handles for this purpose).

Ensure fibre optic cables are correctly connected to the locationsnoted during site expansion board removal.

5 Ensure that the appropriate LEDs indicate correct operation.

• When the red and green ALARM and STATUS LEDs on the frontpanel the HIISC are ashing, the boot code is downloading intonon-volatile memory for software upgrade.

• Do not remove power or reset the equipment until downloadinghas been completed, as this will corrupt the non-volatile memory.

• If the boot code is corrupted, contact Motorola Customer NetworkResolution Centre requesting the boot code restoration procedureand the appropriate boot code le.

6 Notify the OMC-R of BTS availability and log the maintenance activity.

68P02903W31-C 7-69

Aug 2007

Calibrating the HIISC (GCLK) Chapter 7: FRU replacement procedures

Calibrating the HIISC (GCLK)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Introduction to HIISC (GCLK) calibration

GCLK calibration can be carried out automatically using the CINDY commissioningtool. Refer to the relevant CINDY user documentation for details.

This procedure explains how to calibrate the Ovenized Crystal Oscillator (OCXO) in the HIISCGCLK in the Horizon II macro product at a BSS site.

When to calibrate the GCLK

The calibration procedure is to be used on the following occasions:

• When more than one frame slip per hour is observed at the OMC-R (typically more than34/day).

• Whenever calibration is required. (Display the active alarms for a site - if calibration isrequired, there will be an alarm stating this).

This procedure should only be carried out by fully trained, GSM qualied personnel.Under NO circumstances should this procedure be undertaken, unless all the correcttest equipment is readily available.

• The command gclk_cal_mode used in this procedure should only be executed atthe BTS where the calibration is being carried out.

• No call processing can occur involving the HIISC during calibration mode.

• Allow a period of 15 minutes to elapse after switching the OCXO power on, togive sufficient time for the unit to reach operating temperature and achievefrequency stabilization.

7-70 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating the HIISC (GCLK)

Test equipment required

The test equipment required to carry out the GCLK calibration is as follows:

• An IBM compatible personal computer (PC).

• A 9-way to 9-way TTY cable.

• A caesium or rubidium clock standard with 1 or 10 MHz output frequency.

• A universal counter with external reference, for example, the Hewlett Packard modelHP5385A or equivalent.

• A BNC to 3-way HIISC test lead, part number 3086144E01.

Preparation for GCLK calibration

Follow Procedure 7-24 to prepare the HIISC (GCLK) for calibration.

Procedure 7-24 Preparing for GCLK calibration

1 Connect the serial A port of the PC to the HIISC TTY MMI port using the 9-wayto 9-way TTY cable (See Figure 7-14).

2 Start the terminal emulator program.

3 Connect the output from the 10 MHz standard to the reference input of thefrequency counter, select external standard.

4 Set the frequency gate time to 10 seconds and the display to 10 significant digits.

5 Connect the test cable extracting the 8 kHz output signal from the CAL port onthe front of the HIISC to the input of the frequency counter. Pin 3 - Earth (toppin). Pin 1 - 8 kHz signal (bottom pin).

68P02903W31-C 7-71

Aug 2007

Calibrating the HIISC (GCLK) Chapter 7: FRU replacement procedures

Figure 7-14 Horizon II macro GCLK calibration cable connections

7-72 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating the HIISC (GCLK)

GCLK calibration procedure

Follow Procedure 7-25 to calibrate the HIISC (GCLK).

Procedure 7-25 Calibrating the HIISC (GCLK)

1 To start the GCLK calibration mode, enter the command:gclk_cal_modeThe command is used to tell the sync function and HIISC software that a calibrationis to be performed.gclk_cal_mode

The gclk_cal_mode command is used to tell the sync function and HIISCsoftware that a calibration is to be performed and can only be executedat Horizon II macro sites outside sysgen mode. The command is NOTallowed on a master HIISC when a standby HIISC is available.

When the command is executed the system will prompt for verification:

Site <Local site number> starting GCLK CALIBRATION MODE.

If this is a single MCU site, the site will be down until

Calibration is complete.

Are you sure (y=yes, n=no)?

Enter:y. The HIISC will begin calibration mode. The command is aborted if thereply is anything other than y.

2 After a short delay (about 30 seconds) the following prompt will appear:

Frequency Counter Connected, Enter y when ready,

or a to abort test.

Enter:y. The command is aborted and calibration mode exited if the reply isanything other than y

Continued

68P02903W31-C 7-73

Aug 2007

Calibrating the HIISC (GCLK) Chapter 7: FRU replacement procedures

Procedure 7-25 Calibrating the HIISC (GCLK) (Continued)

3 Adjust the OCXO control voltage using the +/- and 0 to 3 keys until the measuredfrequency is exactly 8000,000000 Hz. The values entered here, change thefrequency by varying degrees. For example:

• +0 will increase the output by a small amount.

• +1 will increase the frequency by approximately 10 times.

• +2 will increase the frequency by approximately 100 times.

• +3 will increase the frequency by approximately 1000 times.

These are not exact values as every OCXO has a different gain.This method gives sufficient control to correct the frequency withina short time. A typical sequence of numbers may look as follows:

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >-3

(7.99999898)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >+3

(8.00000020)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >-0

(8.00000019 - 8.00000020)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >-2

(8.00000004)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >+2

(8.00000020)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >-1

(8.00000018)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >-2

(8.00000002 -8.00000003)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >-1

(8.000000--)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >+0

(8.000000-)

Enter a to abort. s to save, +(0..3) to inc, -(0..3) to dec >+0

(8.00000000)

Continued

7-74 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Calibrating the HIISC (GCLK)

Procedure 7-25 Calibrating the HIISC (GCLK) (Continued)

4 A prompt will appear for saving the results:

Enter a to abort, s to save, +(0..3) to inc, -(0..3) to dec >

Enter s

CAL OFFSET is 23654 DAC bits.

After calibration, the HIISC applies a set of voltages to the DAC that feeds theOCXO, requiring the user to input the corresponding output frequency. This isnecessary because the OCXO frequency/voltage characteristic is not linear and theHIISC adjusts for this by taking readings across a range of DAC voltages.

5 To calibrate the OCXO, gain, enter the measured frequency value from the counterafter the value has settled in response to the

MMI

prompts.

When taking frequency measurements, ensure that a full gate periodelapses from the time the new value is set to reading the counter. Thiswait may be several seconds, depending on the counter.

A typical sequence of frequency measurements may be presented as follows:

Dac set to 1.0 volts, Enter Freq Value or a to abort > 7999.99853

Dac set to 2.0 volts, Enter Freq Value or a to abort > 7999.99915

Dac set to 3.0 volts, Enter Freq Value or a to abort > 7999.99969

Dac set to 4.0 volts, Enter Freq Value or a to abort > 8000.00020

Dac set to 5.0 volts, Enter Freq Value or a to abort > 8000.00070

Dac set to 6.0 volts, Enter Freq Value or a to abort > 8000.00122

Dac set to 7.0 volts, Enter Freq Value or a to abort > 8000.00176

Calibration Gain 3.865560e-01

SYNC>

6

The HIISC is reset when the calibration is complete.

Continued

68P02903W31-C 7-75

Aug 2007

Calibrating the HIISC (GCLK) Chapter 7: FRU replacement procedures

Procedure 7-25 Calibrating the HIISC (GCLK) (Continued)

7 On completion, the HIISC automatically rejects the calibration if it is outside thethreshold and the following message is displayed:

Computed Gain > Max WILL RETRY GAIN

In this case, calibration must be performed again. If calibration fails the second timewith the same or similar value, the OCXO may be operating outside the Motorolaspecification, in which case the HIISC is deemed faulty and should be replaced.

7-76 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Line interface unit board replacement

Line interface unit board replacement■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section gives instructions for removing and replacing a Balanced-line Interconnect Board(BIB/BIM) or a T43 Coaxial Interconnect board (T43/CIM). Since the procedure for both boardsis the same, this section refers to either board as a line interface unit board.

All channel trafc associated with a line interface unit board is lost during thereplacement procedure. If only one 2.048 Mbit/s link is affected by a line interface unitboard fault, replacement of the line interface unit board must be performed duringa period of low trafc so as not to interrupt service on the other 2.048 Mbit/s linksconnected to the line interface unit board.

Replacement of a Line interface unit can take place only after the equipment has been takenout of service, in agreement with the OMC-R.

The line interface unit is mounted on the interface panel in Horizon II macro and on the backpanel in Horizon II mini.

In Horizon II micro, the line interface unit is mounted on the side wall of the cable entry box,this requires that the equipment ac power supply is isolated before opening the cable entry box.

When electrical power is connected to the enclosure potentially hazardous voltages, inexcess of 240 V ac, are present inside the cable entry box.

The ac power to the enclosure MUST be isolated before the cable entry box coversare removed.

Figure 7-15 shows a BIB and Figure 7-16 shows a T43 board, with the covers removed for clarity.

68P02903W31-C 7-77

Aug 2007

Line interface unit board replacement Chapter 7: FRU replacement procedures

View of BIB

Figure 7-15 BIB

7-78 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Line interface unit board replacement

View of T43

Figure 7-16 T43 board

68P02903W31-C 7-79

Aug 2007

Line interface unit board replacement Chapter 7: FRU replacement procedures

Replacing a line interface unit board

Procedure 7-26 Replacing a line interface unit board

1 Enter the lock_device command to take device out of service (OOS) inagreement with the OMC-R.

2 Select one of the following:

IF: THEN...

Equipment is Horizon IImacro

Gain access to the interface panel

Equipment is Horizon IImini

Remove the rear door

Equipment is Horizon IImicro

The ac power to the enclosuremust be isolated before the cableentry box covers are removed.

Isolate the ac power to the enclosure andremove the cable entry box covers.

3 Select one of the following:

IF: THEN...

A T43 board1. Record the order in which the 2.048

Mbit/s links are connected to the T43board.

2. Disconnect the 2.048 Mbit/s links fromthe T43 board.

A BIB1. Undo the two screws that secure the

37-pin D-type connector to the BIB.

2. Disconnect the 37-pin D-type externallink connector from the BIB.

4 Remove, and retain, the four screws that secure the line interface unitboard cover to the line interface unit board. Remove and retain the cover.

Continued

7-80 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Line interface unit board replacement

Procedure 7-26 Replacing a line interface unit board (Continued)

5 Remove, and retain, the four screws that secure the line interface unitboard to the enclosure. Lift the line interface unit board free to disconnectthe 37-pin D-type connector.

6 Fit the replacement line interface unit board to the 37-pin D-typeconnector in the cable entry box.

7 Secure the line interface unit board to the enclosure using the four screwsremoved in step 5.

8 Refit the line interface unit board cover and screws retained in step 4.Hand tighten the screws.

9 Reconnect the 2.048 Mbit/s links or the 37-pin D-type external linkconnector to the replacement line interface unit board.

10 Refit any access panels, doors, or the cable box cover, as appropriate,and return the equipment to service.

11 Enter the unlock_device command to bring the device back in service(INS).

12 Notify the OMC-R of base station availability and log the maintenanceactivity.

68P02903W31-C 7-81

Aug 2007

Replacing a heat sensor Chapter 7: FRU replacement procedures

Replacing a heat sensor■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The heat sensors plug into the backplane from the front, above the CTU2s in the Horizon IImacro and Horizon II mini cabinets, and into the midplane from the front, above the CTU2s in aHorizon II micro cabinet. Each one can be removed separately, and a replacement inserted.CTU2(s) are removed to gain access for replacing a heat sensor.

There is one 70 °C sensor in a Horizon II macro, and one 75 °C sensor in a Horizon II microand a Horizon II mini and two 85 °C sensors in all the three Horizon II cabinets. Each sensor ismarked with the appropriate temperature.

In Horizon II micro replacement of a heat sensor requires that the equipment power supplyis isolated and can take place only after the equipment has been taken out of service, inagreement with the OMC-R.

Heat sensor replacement procedure

Procedure 7-27 Replacing a heat sensor

1 Execute the shutdown_device command at the OMC-R or from a PC connectedto the HIISC to disable the CTU2 transmit RF power (only CTU2 in a HorizonII micro, both the CTU2s in a Horizon II mini and CTU2 2 and CTU2 3 ina Horizon II macro cabinet).

Refer to Technical Description: BSS Command Reference(68P02901W23) for information on usage and specific device codes.

2 When the CTU2(s) have been shutdown, check if the Tx status LEDs (yellow)are unlit.

3

Before disconnecting the RF cables, ensure that the RF power isOFF Severe burns may result if RF power is ON when the cables aredisconnected.

In Horizon II macro and Horizon II mini, press and release the appropriateCTU2 circuit breaker button to the out (off) position. In Horizon II micro turnoff the enclosure PSU. Ensure that the RADIO STATUS LED is unlit.

Continued

7-82 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Replacing a heat sensor

Procedure 7-27 Replacing a heat sensor (Continued)

4 Remove the CTU2(s), (only CTU2 in a Horizon II micro, both the CTU2s in aHorizon II mini and CTU2 2 and CTU2 3 in a Horizon II macro cabinet, seeReplacing a CTU2), to access the heat sensors.

5 Identify the faulty heat sensor and unplug it from the midplane in a HorizonII micro cabinet and from the backplane in the Horizon II macro and minicabinets.

6 Insert the replacement heat sensor by pushing firmly into place. Refit theCTU2(s). (See Replacing a CTU2)

7 Switch on BTS PSU or reset the circuit breakers. Enable the CTU2 transmitRF power by using the ins_devicecommand at the OMC-R or from a PCconnected to the HIISC. The Tx STATUS LEDs (yellow) will be lit if the CTU2is transmitting.

68P02903W31-C 7-83

Aug 2007

Replacing a heat sensor Chapter 7: FRU replacement procedures

7-84 68P02903W31-C

Aug 2007

Chapter

8

Site verication procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter provides information required for the verification of Horizon II micro hardwareequipment.

68P02903W31-C 8-1

Aug 2007

Introduction to Horizon II BTS verication procedures Chapter 8: Site verication procedures

Introduction to Horizon II BTS verication procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The procedures described in this section are as follows:

• Checking the antenna VSWR and calibrating the transmit output power.

• Checking the database equipage.

• Checking the backhaul link.

• Checking the PIX connections and alarm test.

• Site restoration.

CINDY commissioning tool

Many of the procedures described in this chapter can be carried out automatically using theCINDY commissioning tool. Refer to the relevant CINDY user documentation for details.

8-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Site verication test equipment, leads, and plugs

Site verication test equipment, leads, and plugs■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides information on the test equipment required for the procedures in thischapter.

Ensure that all test equipment associated with commissioning of Motorola cellularbase stations is within calibration date.

Test equipment required

Table 8-1 provides details of the test equipment required to perform the hardware verificationprocedures provided in this chapter:

Table 8-1 Hardware verication test equipment

Quantity Description Comments

1 IBM compatible portable PersonalComputer

With:

• PCMCIA Type 2 slot

• serial comms port

• Battery power

1 Commercial terminal emulatorsoftware

PC PLUS or similar software (suitablefor PC being used).

1 Digital multimeter Hewlett Packard E2378A orequivalent.

1 ESD protection kit

1 Signal generator Up to 2 GHz.

1 30 dB attenuator 100 W minimum.

1 RF adaptor kit RTLXQ98088 or equivalent.

2 N to 7/16-inch adaptor

1 N to N barrel adaptor

Continued

68P02903W31-C 8-3

Aug 2007

Site verication test equipment, leads, and plugs Chapter 8: Site verication procedures

Table 8-1 Hardware verication test equipment (Continued)

Quantity Description Comments

1• RF wattmeter with 5W, 10W,

25W and 50W elements.

• Digital RF wattmeter withwideband power sensor.

• For measuring average poweron the calibration channel, usea Bird model 43 wattmeter orequivalent.

• For measuring TX power on aBCCH/TCH channel, use a metercapable of measuring burstaverage power.

1 2 metres of N to N male coaxial cable Must be calibrated.

1 4 metres of N to N male coaxial cable Must be calibrated.

2 9-way to 9-way cable Compatible with PC to TTY port onCTU2/HIISC.

1 9-way to 9-way cable (CTU2 only) DSP MMI/RSS cable, connecting PCto CTU2 TTY port.

8-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Site verication test equipment, leads, and plugs

Test leads required

Figure 8-1 and Figure 8-2 show schematic wiring diagrams of the test leads required for siteverification.

Figure 8-1 Horizon II 9-way to 9-way hardware verication cable connections

Figure 8-2 Horizon II 9-way to 9-way CTU2 cable connections

TCU-B test lead 3086240N01 can be used instead of CTU2 test lead 3086299N01,but an adaptor (58C86540N01) is required to attach the 25-way cable connectorto the 9-way CTU2 port.

68P02903W31-C 8-5

Aug 2007

Site verication test equipment, leads, and plugs Chapter 8: Site verication procedures

Connections for a PIX test lead

Table 8-2 shows the details necessary to make a PIX test lead.

Table 8-2 PIX test plug pin connections

Short-circuit

From Pin To PinRelay connections

1 14 9 RELAY_1_NO

2 15 10 RELAY_1_NC

3 16 22 RELAY_1_COM

4 17 11 RELAY_2_NO

5 18 12 RELAY_2_NC

6 19 23 RELAY_2_COM

7 20 13 RELAY_3_NO

8 21 24 RELAY_3_NC

25 RELAY_3_COM

When making the PIX test lead:

• Connect normally open (N/O) PIX inputs through a 50 ohm resistor.

• Connect normally closed (N/C) PIX inputs through a 50 kohm resistor.

• Details of N/O and N/C site inputs can be found in the equip_eas file in thesite commissioning database.

Test lead calibration

To minimize variations in test results, ensure that all appropriate test leads used in hardwareverification procedures are calibrated.

Out of calibration test equipment may damage equipment or degrade hardwareperformance. Ensure the following to prevent any such eventuality:

• A recognized laboratory must calibrate all test equipment and associated testleads annually.

• Do not calibrate test equipment or test leads in the eld.

8-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro VSWR checks on Horizon II micro

VSWR checks on Horizon II micro■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Horizon II micro makes use of the standard CTU2 radio. The Tx calibration is at macro levels.

The CTU2 transmit power, in Horizon II micro, is factory calibrated as a macro BTS(potentially up to: 60 W for PGSM900, 63 W for EGSM900 and 50 W for DCS1800,in single density high power mode), prior to delivery.

Personnel carrying out BTS calibration must be prepared to calibrate for macro BTSlevels.

Refer to the following standards (USA and EC), or equivalent national and regionalregulations, when making calculations for RF equipment:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10 kHz to 300 GHz).

The max_tx_bts parameter value for the Horizon II micro BTS MUST be set from 5through 21 to ensure that the transmit power remains within the preset limit speciedfor this equipment.

For a standard power option, if max_tx_bts is set to any value under 5:

• Transmit output power will rise above recommended levels.

• Fan noise will increase drastically.

• Power cutback or shutdown due to increased enclosure temperature can alsooccur.

Table 8-3 Tx output power during tests

Mode 900 MHz 1800 MHZ

Single density 40 W (46 dBm) 32 W (45 dBm)

Double density 20 W (43 dBm) 16 W (42 dBm)

During normal operation the database parameter max_tx_bts, with a value of greater than 5,ensures the correct power levels for a standard power unit. A high power unit will have amax_tx_bts parameter ranging from 0 to 21).

68P02903W31-C 8-7

Aug 2007

CTU2 VSWR and cell site offset information Chapter 8: Site verication procedures

CTU2 VSWR and cell site offset information■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The objective of the VSWR check is to ensure that antenna feeders and connectors are properlyterminated. The power calibration procedure ensures that the pre-defined maximum transmitterpower output is correctly set at the RF connector of the equipment.

When a transceiver is manufactured, it undergoes comprehensive transmit-and-receivecalibration procedures. These procedures aim to produce a transceiver that exhibits a flatfrequency response over the GSM band. When a transmitter is used, the calibration isperformed by distributing the channels over three detector groups (the detector being thedevice that maintains a steady output power level).

In the field, the procedure for setting the transmit output power involves using a set ofcommands called Cell Site Power (CSPWR). The CSPWR, through its functionality of trimmingthe BTS output power, can be used to account for any abnormalities that occur between theCTU2 and the RF. The offset is reduced from the requested power level, so that a steady outputis maintained at the RF connector of the BTS for all the channels.

Complete the procedures, Preparation for output power calibration and VSWR check on page8-11 before beginning the VSWR and cell site power calibration procedures.

VSWR checks on Horizon II micro

The CTU2 transmit power, in Horizon II micro, is factory calibrated as a macro BTS(potentially up to: 60 W for PGSM900, 63 W for EGSM900 and 50 W for DCS1800,in single density high power mode), prior to delivery. Personnel carrying out BTScalibration must be prepared to calibrate for macro BTS levels.

Refer to the following standards (USA and EC), or equivalent national and regionalregulations, when making calculations for RF equipment:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10 kHz to 300 GHz).

With the Horizon II micro BTS the max_tx_bts parameter value MUST be set between 5and 21 or the transmit power will exceed the value that is specied for this equipment.

For a standard power option, setting the max_tx_bts to less than 5 can result in:

• Transmit output power above recommended levels.

• Increased fan noise.

• The possibility of power cutback or shutdown due to increased enclosuretemperature.

8-8 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro CTU2 VSWR and cell site offset information

Table 8-4 Tx output power during tests

Mode 900 MHz 1800 MHz

Single density 40 W (46 dBm) 32 W (45 dBm)

Double density 20 W (43 dBm) 16 W (42 dBm)

Test equipment required

The following test equipment is required during the VSWR and output power calibrationprocedure:

• An IBM compatible personal computer (PC).

• Terminal emulator software.

• A digital power meter which can measure the burst average power, with 5 W and 50 Welements.

• A 9-way to 9-way cable (a diagram of this cable is provided in the chapter on Siteverification procedures).

• A 9-way to 9-way DSP MMI/RSS cable (a diagram of this cable is provided in the chapteron Site verification procedures).

• A 7/16 N-type adaptor.

• A 50 ohm, 100 W power attenuator.

All test equipment and test leads must be calibrated annually by a recognizedlaboratory. Test equipment and test leads must not be calibrated in the eld.

Do not optimize Motorola cellular base stations with test equipment that is beyondits calibration due date.

Allow test equipment to warm up for 30 minutes before use.

Commands used

Table 8-5 lists the commands for the VSWR and output power calibration procedure.

The symbol 0 used in the commands is a zero.

68P02903W31-C 8-9

Aug 2007

CTU2 VSWR and cell site offset information Chapter 8: Site verication procedures

Table 8-5 VSWR and power calibration commands.

BSS MMI Command Function

ins_device Initializes the device, bringing it into service.

lock_device Prevents the device from being used.

unlock_device Frees the device for further use.

clear_cal_data Clears previously stored calibration data for aspecified transceiver on a per DRI basis.

chglev Changes the DSP MMI security level.

cal_test_mode on Enters the calibration test mode.

fm test_mode on Puts the DSP fault management module in test mode.

fm_test block none none 0xff Blocks all the DSP fault management alarms.

cal_config tx_cab_mode <single>ORcal_config tx_cab_mode<double>

Sets Tx power calibration mode for single density.single is the default mode and can be omitted.

Sets Tx power calibration mode for double density.

cal_config tx_cab_carriers<carriera>ORcal_config tx_cab_carriers <both>

Sets Tx power calibration to calibrate the firstcarrier only when in double density mode.carriera is the default carrier and can be omitted.Sets Tx power calibration to calibrate bothcarriers when in double density mode.This feature is available only with 1670.27, 1740.22,1760.0C or later software release.

cal_cabinet tx_cab Performs Tx power calibration.

ts a txp 0x00 Turns all timeslots to max power for the currentcarrier.

ts a txp 0xff Turns off power to all timeslots for the currentcarrier.

ts a modulator unmod Turns off modulation.

ts a state call_proc Puts all timeslots into call processing state.

ts a synth lock Locks the synthesizers.

cal_store_1 Stores the calibration data.

cal_config rf_band p900 Overrides for PGSM only Duplexer.

chg_ele max_tx_bts <N> <site_id><CELL_ID>

Changes the max_tx_bts parameter to set cell site Txoutput power. Where N is the desired value.

For Horizon II micro, this value must bewithin the range of 5 to 21 (standardpower option) or 0 to 21 (high poweroption).

chg_ele max_tx_bts Changes the max_tx_bts parameter to a desiredvalue.

8-10 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro CTU2 VSWR and cell site offset information

Refer to Technical Description: BSS Command Reference (68P02901W23) forinformation on usage of specific commands.

Test stages

There are four stages to the procedure:

• Preparing for test.

• Checking the VSWR.

• Calibrating the transmit output power.

• Restoring the site.

VSWR checks ensure correct antenna matching and can prove the serviceability of theantenna. Repeat the procedures for all antennas on site, including receive antennas.

Preparation for output power calibration and VSWR check

Prepare the RF path for bay level calibration. DRIs in the site must be locked, the CTU2 has to bereset, a dummy load must be connected if there is no antenna, and all alarms must be disabled.

In the Horizon II macro, a transceiver may consist of one or two DRIs. If a CTU2 is configuredfor double density mode (two DRIs), Tx cabinet calibration needs to be performed only on thefirst DRI because the internal difference value keeps the power of the second carrier equalto the first.

The internal difference value is not visible through the MMI command, and the TXoffset reported by disp_cal_data for the second DRI is a copy of the value for the firstDRI. Dual carrier calibration can verify that both carriers transmit at equal power.

Optionally, the Tx power of both DRIs can be calibrated as described in the section, Preparingto calibrate CTU2 transmit output power.

To determine the configuration of the CTU2 as single or double density transceiver and theDRI numbers corresponding to each CTU2.

68P02903W31-C 8-11

Aug 2007

CTU2 VSWR and cell site offset information Chapter 8: Site verication procedures

At the BSC TTY, change to Level 3 and at the MMI-RAM> prompt type the following: disp_eq<site_id> dri <cell_id> <DRI_number> 0

Where: is:

<site_id> the number of the site logged into.

<cell_id> the antenna/relative cell number (0 to 5).

<DRI_number> DRI number of the transceiver.

Output for a single density CTU2:

[05/02/03 14:42:37] MMI-RAM 0115 -> disp_eq 81 dri 0 0

DRI identifier: 0 0

DRI Density[dri_density]: SINGLE

Cabinet identifier: 0

Type of connection to the BTP: MASTER

Port to which the TCU is connected[tcu_port]: 0

RTF identifier[pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell[antenna_select]: 1

Tuneable combining used: No

The diversity flag for this DRI is[diversity_flag]: 0

The fm cell type is[fm_cell_type]: 0

Output for a double density CTU2:

[05/02/03 14:47:55] MMI-RAM 0115 -> disp_eq 81 dri 0 1

DRI identifier: 0 1

DRI Density[dri_density]: DOUBLE

Associated DRI identifier: 0 2

Cabinet identifier: 0

Type of connection to the BTP: MASTER

Port to which the TCU is connected[tcu_port]: 1

RTF identifier[pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell[antenna_select]: 1

Tuneable combining used: No

The diversity flag for this DRI is[diversity_flag]: 0

The fm cell type is[fm_cell_type]: 0

In this case we see that DRI 0 1 is a double density CTU2 and is associated with DRI 0 2.

8-12 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro CTU2 VSWR and cell site offset information

Repeating the command for DRI 0 2 yields the following:

[05/02/03 14:48:07] MMI-RAM 0115 -> disp_eq 81 dri 0 2

DRI identifier: 0 2

DRI Density[dri_density]: DOUBLE

Associated DRI identifier: 0 1

Cabinet identifier: 0

Type of connection to the BTP: MASTER

Port to which the TCU is connected[tcu_port]: 1

RTF identifier[pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell[antenna_select]: 1

Tuneable combining used: No

The diversity flag for this DRI is[diversity_flag]: 0

The fm cell type is[fm_cell_type]: 0

Thus, in this example, DRI 0 1 and DRI 0 2 are on the same CTU2.

Calibrate the single density CTU2 once on the DRI.

For the double density CTU2, calibration is performed on only one of the two DRIs, but the otherDRI must be locked for the procedures to be carried out. Furthermore, the clear_cal_datacommands must be issued for both DRIs.

For 4 Branch Rx Diversity the output looks similar to the following:

[05/02/03 14:42:37] MMI-RAM 0115 -> disp_eq 81 dri 0 0

DRI identifier: 0 0

DRI Density[dri_density]: SINGLE

Cabinet identifier: 0

Type of connection to the BTP: MASTER

Port to which the TCU is connected[tcu_port]: 0

RTF identifier[pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell[antenna_select]: 1

Tuneable combining used: No

The diversity flag for this DRI is [diversity_flag]: 2

The fm cell type is [fm_cell_type]: 4

68P02903W31-C 8-13

Aug 2007

CTU2 VSWR and cell site offset information Chapter 8: Site verication procedures

Output format for disp_cal_data command

The CTU2 stores calibration data in a higher precision format (UWORDs) than the CTU(UBYTEs). Since the two transceivers are interchangeable, the data is stored in the database ina common format and the higher precision UWORD format is now used.

This does not affect the output format of the disp_cal_data command when the transceiveris unlocked (UWORDs for the CTU2 and UBYTEs for other transceivers). However, if thetransceiver is locked, the data on it cannot be accessed nor can the transceiver type bedetermined and therefore the data can only be displayed in the format in which it is storedon the database (that is, UWORD format).

Use one of the following formulae to convert the appropriate disp_cal_data output to a gainvalue (FEG):

• For the CTU2: FEG = 2's_complement_16_bit_value / 256

• For other transceivers: FEG = 17.5 + (2's_complement_8_bit_value / 10)

Use one of the following formulae to convert the gain value (FEG) to the UWORD or UBYTEformat:

• UWORD: 2's_complement_16_bit_value = round(FEG x 256)

• UBYTE: 2's_complement_8_bit_value = round{(FEG - 17.5) x 10}

8-14 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Normal CTU2 VSWR and cell site power (CSPWR) calibration

Normal CTU2 VSWR and cell site power (CSPWR)calibration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

CTU2 cell site power calibration and VSWR checks can be carried out automaticallyusing the CINDY commissioning tool. Refer to the relevant CINDY user documentationfor details.

Two methods available for normal VSWR checking are described in this section; one automaticand one manual. The reason for the two methods is as follows:

VSWR method 1 (automatic) When typing the cal_cabinet tx_cab command at the DSPMMI prompt, it effectively executes a small script containing the following commands:

TS A CHAN 23 Set all timeslots to channel 23 (900 MHz).

TS A CHAN 53 Set all timeslots to channel 53 (900 MHz PGSM).

TS A CHAN 668 Set all timeslots to channel 668 (1800 MHz).

TS A TXP 00

TS A MODULATOR UNMOD

TS A STATE CALL_PROC

TS A SYNTH LOCK

Before executing the cal_cabinet tx_cab command, it assumes that the synthesizers are innormal mode (not locked), as is the case after the unit is powered up for the first time.

VSWR method 2 (manual) To set a specific channel, instead of defaulting to channel 23,53 or 668, additional commands must be entered, rather than using the cal_cabinet tx_cabcommand. One command sets the appropriate channel and the other switches the CTU2output power on and off.

Automatic VSWR test procedure

The first method for normal VSWR checking uses automatic channel selection. The cal_cabinettx_cab command automatically selects a midpoint channel number. However, manual channelselection can be performed following the steps detailed in the manual test procedure.

To automate the validation of the VSWR of the transmission path:

• Perform Procedure 8-1 Automatic VSWR forward power test on page 8-16.

• Perform Procedure 8-2 Automatic VSWR reverse power test on page 8-17.

68P02903W31-C 8-15

Aug 2007

Normal CTU2 VSWR and cell site power (CSPWR) calibration Chapter 8: Site verication procedures

Automatic VSWR forward power test

Full power is transmitted during VSWR checks. Ensure that all personnel are clear ofthe antenna. Do not carry out this check unless antenna installation is complete.

Ensure that the antenna is rated to allow full power to avoid damage to equipment.

To reduce the possibility of interference with other users, minimize the time thatthe CTU2 is powered up.

Procedure 8-1 Automatic VSWR forward power test

1

Ensure that RF power is OFF before connecting or disconnectingantenna cables. Severe burns may result if RF power is present whencables are connected or disconnected

Disable the CTU2 to ensure that RF is not present, then disconnect the antenna.Connect a dummy load to the meter, ensuring that the meter is fitted with a 50W element and connect the meter to the Tx output.

2 Bring the CTU2 into service using the ins_device command.

3 At the DSP MMI prompt type:chglevpizza (this is a password and appears on screen as *****)fm test_mode onfm_test block none none 0xffcal_cabinet tx_cab

Continued

8-16 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Normal CTU2 VSWR and cell site power (CSPWR) calibration

Procedure 8-1 Automatic VSWR forward power test (Continued)

4 Press N to specify that the test should NOT be run in high power mode.

5 Monitor and record the power meter reading (the forward output power).

6 Press Q.

Automatic VSWR reverse power test

Procedure 8-2 Automatic VSWR reverse power test

1

Ensure that RF power is OFF before connecting or disconnectingantenna cables. Severe burns may result if RF power is present whencables are connected or disconnected.

Replace the 50 W element in the wattmeter with a 5 W element and reverse thedirection on the power meter.

2 Remove the dummy load and connect the power meter through to the antenna.

3 At the DSP MMI TEST prompt type:cal_cabinet tx_cab

4 Press N to specify that the test should NOT be run in high power mode.

5 Monitor and record the reverse power reading indicated on the power meter.

Readings should show reflected (reverse) power of no more than 5%of the forward power at the point of measurement, and less than 1W. If the ratio of the forward and reverse readings is unacceptable,suspect an improper termination of the antenna feeder and connector.

6 Press Q.

7 Disable the CTU2 then remove the power meter and reconnect the antenna.

This procedure leaves the transceiver in an overridden state. It mustbe reset before it can be used.

8 Use the Site restoration procedure given later in this chapter to return thesite to service.

68P02903W31-C 8-17

Aug 2007

Normal CTU2 VSWR and cell site power (CSPWR) calibration Chapter 8: Site verication procedures

Manual VSWR test procedure

The second method for normal VSWR checking allows the manual selection of a channel.

To mechanically validate the VSWR of the transmission path through to the antenna:

• Perform Procedure 8-3Manual VSWR forward power test on page 8-18.

• Perform Procedure 8-4Manual VSWR reverse power test on page 8-20.

Manual VSWR forward power test

Full power is transmitted during VSWR checks. Ensure that all personnel are clear ofthe antenna. Do not carry out this check unless antenna installation is complete.

Ensure that the antenna is rated to allow full power to avoid any damage to equipment.

To reduce the possibility of interference with other users, minimize the time thatthe CTU2 is powered up.

Procedure 8-3 Manual VSWR forward power test

1

Ensure that RF power is OFF before connecting or disconnectingantenna cables. Severe burns may result if RF power is present whencables are connected or disconnected

Disconnect the antenna. Connect a dummy load to the power meter, ensuringthat the meter is fitted with a 50 W element and connect the meter to the Txoutput.

2 Bring the CTU2 into service using the ins_device command.

Continued

8-18 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Normal CTU2 VSWR and cell site power (CSPWR) calibration

Procedure 8-3 Manual VSWR forward power test (Continued)

3 At the DSP MMI prompt type:

• chglev

• pizza this is a password and appears on screen as *****

• fm test_mode on

• fm_test block none none 0xff

• ts a state call_proc

4 Enter the following command: ts a chan nnnwhere: a is all time slots (TS) and nnn is the specified channel number.

5 To switch the power on, enter the following command: ts a txp 0x00Where: a is all time slots (TS) and 00 is maximum output power.

6 Monitor and record the power meter reading (the forward output power).

7 To switch the power off, enter the following command: ts a txp 0xffWhere: a is all time slots (TS) and ff is zero output power.

68P02903W31-C 8-19

Aug 2007

Normal CTU2 VSWR and cell site power (CSPWR) calibration Chapter 8: Site verication procedures

Manual VSWR reverse power test

Procedure 8-4 Manual VSWR reverse power test

1

Ensure that RF power is OFF before connecting or disconnectingantenna cables. Severe burns may result if RF power is present whencables are connected or disconnected

Replace the 50 W element in the power meter with a 5 W element and reversethe direction on the power meter.

2 Remove the dummy load and connect the power meter through to the antenna.

3 To switch the power on, enter: ts a txp 0x00Where: a is all time slots (TS) and 00 is maximum outputpower.

4 Monitor and record the reverse power reading indicated on the power meter.

Readings should show reflected (reverse) power of no more than 5%of the forward power at the point of measurement, and less than 1W. If the ratio of the forward and reverse readings is unacceptable,suspect an improper termination of the antenna feeder and connector.

5 To switch the power off, enter: ts a txp 0xffWhere: a is all time slots (TS) and ff is zero outputpower.

6 Repeat the above forward and reverse power checks for the required numberof channels.

7 When all channels have been checked, at the DSP MMI TEST prompt type:ts a state active_standby.

8 Remove the power meter and reconnect the antenna.

This procedure leaves the transceiver in an overridden state. It mustbe reset before it can be used.

9 Use the Site restoration procedure given in later in this chapter to return thesite to service.

8-20 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Normal CTU2 VSWR and cell site power (CSPWR) calibration

Tx output power calibration procedure

To calibrate CTU2 transmit output power carry out the following procedures:

• If required, perform Procedure 8-5Changing the max_tx_bts on page 8-22.

The CTU2 transmit power, in Horizon II micro, is factory calibrated as a macroBTS (potentially up to: 60 W for PGSM900, 63 W for EGSM900 and 50 W forDCS1800, in single density high power mode), prior to delivery.

Personnel carrying out BTS calibration must be prepared to calibrate for macroBTS levels.

Refer to the following standards (USA and EC), or equivalent national andregional regulations, when making calculations for RF equipment:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect toHuman Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300GHz.

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10 kHz to 300 GHz).

With the Horizon II micro BTS standard power option the max_tx_bts parametervalue MUST be set between 5 and 21 or the transmit power will exceed thatspecied for this equipment.

Setting the max_tx_bts on a standard power unit to less than 5 may result in:

• Transmit output power above recommended levels.

• Increased fan noise.

• The possibility of power cutback or shutdown due to increased enclosuretemperature.

A high power option unit may have the max_tx_bts parameter set between 0 and 21.

• Perform Procedure 8-6Preparing to calibrate CTU2 transmit output power on page 8-22.

• Perform Procedure 8-7Calibrating CTU2 transmit output power on page 8-25.

• Perform Procedure 8-8Calibrating additional CTU2s and completion on page 8-26.

68P02903W31-C 8-21

Aug 2007

Normal CTU2 VSWR and cell site power (CSPWR) calibration Chapter 8: Site verication procedures

If the DRI does not become B-U because of the error, Tx Power Unachievable, thenthe max_tx_bts of the cell needs to be temporarily modified to a lower power so thatthe radio can come into service. At this point, calibration can be performed as normal.Once the radio is calibrated in its desired configuration (single or double density,Horizon or Horizon II equipment), the max_tx_bts can be returned to its desired value.

Procedure 8-5 Changing the max_tx_bts

Execute the following command from the OMC, BSC or by remote login fromthe PC:chg_ele max_tx_bts <N> <site_id> cell_number=<CELL_ID>

Where: <N> is: the max_tx_bts value (the validrange for Horizon II micro is 5to 21, standard power optionor 0 to 21, high power option)

<site_id> is the site number

<CELL_ID> is the cell identifier

Preparing to calibrate CTU2 transmit output power

Procedure 8-6 Preparing to calibrate CTU2 transmit output power

1 Connect the 9-way to 9-way HIISC cable from the PC serial A port to the HIISCTTY port.

2 At the PC, start the terminal emulator program.

3 Lock all DRIs in the sector. At the HIISC TTY, change to Level 3 and at theMMI-RAM> prompt type:lock_device <site_id> dri <cell_id> <DRI_number> 0

Always lock the transceiver providing the BCCH last as this preventsthe BCCH being switched to alternate transceivers.

Continued

8-22 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Normal CTU2 VSWR and cell site power (CSPWR) calibration

Procedure 8-6 Preparing to calibrate CTU2 transmit output power (Continued)

4

Ensure that RF power is OFF before connecting or disconnectingantenna cables. Severe burns may result if RF power is present whencables are connected or disconnected

Disconnect the antenna. Connect a dummy load/attenuator/coupler to the powermeter, ensuring the meter is fitted with a 100 W element. Connect the meterto the Tx output, ensuring that sufficient attenuation is present to protect thepower meter/sensor from damage.

Ensure that the digital power wattmeter has been correctly set up.Refer to the manufacturer’s manual for detailed instructions on howto carry out the following:

• Perform self-calibration of power meter with sensor.

• Enter cable offset (Cable loss) into power meter to display thecorrect output power.

• Enable burst averaging or “Burst Average Power”.

5 Ensure that both the carriers A and B are unlocked BEFORE starting theprocedure. Change to Level 3 and at the MMI-RAM> prompt, type:ins_device <site_id> dri <cell_id> <DRI_number> 0

6 Connect a serial port on the PC to the TTY Interface port on theCTU2 to be calibrated using the 9-way to 9-way DSP MMI/RSS cable.If necessary, switch the 9-way to 9-way DSP MMI/RSS cable from providing RSSconnectivity to providing DSP connectivity.

7 At the DSP MMI prompt type: chglev. The password is pizza.

8 Enter calibration test mode and disable alarms by typing the followingcommands:cal_test_mode onfm test_mode onfm_test block none none 0xff

Continued

68P02903W31-C 8-23

Aug 2007

Normal CTU2 VSWR and cell site power (CSPWR) calibration Chapter 8: Site verication procedures

Procedure 8-6 Preparing to calibrate CTU2 transmit output power (Continued)

9 By default, Tx calibration is performed in the mode specified in the database. Toforce Tx calibration in either single or double density mode for a transceiver,enter one of the following commands as required:cal_config tx_cab_mode singlecal_config tx_cab_mode doubleTo reset Tx calibration to the mode specifiedin the database, enter the following command:cal_config tx_cab_mode database

When configuring a double density CTU2, the second carrier needs tobe locked BEFORE calibration if the same calibration figures are tobe used for the operation of both A and B carriers.

10 OPTIONAL STEP TO CALIBRATE CARRIER B. This step is only applicable ifcalibrating in double density mode (see step 9). By default, only the first carrier(Carrier A) is calibrated. To calibrate the second carrier (Carrier B) additionally,specify that both carriers are to be calibrated with the following command:cal_config tx_cab_carriers both

This feature is only available with software release 1670.27, 1740.22,1760.0C or later. Both carriers have approximately the same outputpower. Due to variations in the hardware and factory calibration,small differences can occur. To fine-tune the calibration so that bothcarriers can achieve the same power, specify that both carriers shouldbe calibrated by entering the above command.

To reset Tx calibration to only calibrate Carrier A, enter the following command:cal_config tx_cab_carriers carriera

11

900 MHz radios take the EGSM RF band from the EID by default. IfPGSM duplexers are fitted, the radio needs to be configured for thePGSM band.

To set the RF band to PGSM900, enter the following command:cal_config rf_band p900The following message is displayed on the screen:

Setting RF band to PGSM900

8-24 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Normal CTU2 VSWR and cell site power (CSPWR) calibration

Calibrating CTU2 transmit output power

Procedure 8-7 Calibrating CTU2 transmit output power

1 Start the Tx calibration procedure by typing the followingcommand at the DSP MMI prompt: cal_cabinet tx_cabThe following warning message is displayed on the screen:

WARNING! All attenuation is about to be removed.

Please ensure that appropriate attenuation

is attached to the CTU2 TX output.

Press any key to continue

2 Check the connections to the antenna and then press ENTER.For calibration in single density mode only, the following information andinstructions is printed:

High Power Mode is currently DISABLED (max_tx_bts is >= 0).

High Power Mode will only be used if max_tx_bts database

parameter is set to -1.

If the current site database is accurate, you should run

TX cabinet calibration in the same mode as the database.

Press H to calibrate in High Power Mode, or press N to calibratein Normal Power Mod

The above message does not appear if the transceiver is set to highpower mode.

3

For Horizon II micro, only use N.

Press H or N, as appropriate.The following instructions is displayed:

Press U to increase power, D to decrease power

until the target output power is reached.

Then press Q when finished.

Continued

68P02903W31-C 8-25

Aug 2007

Normal CTU2 VSWR and cell site power (CSPWR) calibration Chapter 8: Site verication procedures

Procedure 8-7 Calibrating CTU2 transmit output power (Continued)

4 Press U to increase output power or D to decrease output power until thereading on the power meter matches the target maximum power for the sector.

With the Horizon II micro BTS standard power option the max_tx_btsparameter value MUST be set between 5 and 21 or the transmit powerwill exceed the value that is specied for this equipment. A high poweroption BTS may have a max_tx_bts parameter setting of 0 to 21.

As the output power is adjusted, a message similar to the following is displayed:

Setting offset to = 0x13

5 Press Q when the desired output power level has been reached.

6 If Carrier B was configured to be calibrated in the previous procedure, thenfollow the on screen directions to repeat step 2 to step 5 for Carrier B.Otherwise, proceed to next step.

7 Store the new Tx calibration using thefollowing DSP MMI command: cal_store_1After a few seconds delay (up to 16 seconds), the result of the data storage isdisplayed on the screen in the format:

cal_store_1

PASS

CTU2.carA.ts_0>

8 After the data has been stored, connect the 9-way to 9-way HIISCcable from the PC serial A port to the HIISC MMI TTY port and enterthe following command to lock the CTU2 that has been calibrated:lock_device <site_id> dri <cell_id> <DRI_number> 0.

Calibrating additional CTU2s and completion

Procedure 8-8 Calibrating additional CTU2s and completion

1 Move the 9-way to 9-way DSP MMI/RSS cable to the CTU2 TTY port of the nextCTU2 to be calibrated and repeat the procedure from Procedure 8-5 on page8-22 step 4.

2 Disable the CTU2. Remove the power meter and check that all antennas havebeen reconnected.

Continued

8-26 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Normal CTU2 VSWR and cell site power (CSPWR) calibration

Procedure 8-8 Calibrating additional CTU2s and completion (Continued)

This procedure leaves the transceiver in an overridden state. It mustbe reset before it can be used.

3 Use the Site restoration procedure given later in this chapter to return thesite to service.

Tx enclosure channel numbers and frequencies

The Tx channel numbers and frequencies for the Horizon II equipment are as follows:

TS A CHAN 23 Set all timeslots to channel 23 (900 MHz).

TS A CHAN 53 Set all timeslots to channel 53 (900 MHz PGSM).

TS A CHAN 668 Set all timeslots to channel 668 (1800 MHz).

68P02903W31-C 8-27

Aug 2007

Checking the database equipage Chapter 8: Site verication procedures

Checking the database equipage■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The database equipage checks determine what devices and functions have been equipped inthe BSC/Horizon II BTS database.

Test equipment required

The following test equipment is required during the procedure:

• An IBM compatible personal computer (PC).

• Terminal emulator software.

• A 9-way to 9-way cable.

All test equipment and test leads must be calibrated annually by a recognizedlaboratory. Test equipment and test leads must not be calibrated in the eld.

Do not optimize Motorola cellular base stations with test equipment that is beyondits calibration due date.

Allow test equipment to warm up for 30 minutes before use.

Commands used

The following commands are used during the procedure:

Command Function

disp_site Displays the site number.

disp_equipment Displays the active equipment at a specified site.

Test procedures for checking the database equipage

There are two stages to the procedure:

• Preparation for database checks on page 8-29.

• Database equipage check procedure on page 8-29.

8-28 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Checking the database equipage

Preparation for database checks

Procedure 8-9 Preparation for database checks

1 Ensure that the site is in call processing mode.

2 Connect the serial A port on the PC to the HIISC TTY port using the 9-way to9-way cable.

3 Start the terminal emulator program at the PC.

Database equipage check procedure

Procedure 8-10 Database equipage check

1 At the CUST MMI prompt type: disp_siteThe following message (from the HIISC) is displayed:

current site is #

where # is the number of the site logged into.

2 At the CUST MMI prompt type: disp_equipment #where # is the number of the site logged into.A complete list of the equipment and functions in the databaseis displayed. For example an omni 2 gives:

CSFP 000

BTP 000

DRI 000 (010)

DRI 010 (000)

MMS 000

MMS 010

RSL 000

GCLK 000

EAS 000

CAB 000

SITE 000

PATH 000

RTF 000

RTF 010

Continued

68P02903W31-C 8-29

Aug 2007

Checking the database equipage Chapter 8: Site verication procedures

Procedure 8-10 Database equipage check (Continued)

3 To check the MSI configuration at the CUST MMI prompttype: disp_equipment # MSI 0 0 Where: # is site number.A message similar to the following example is displayed:

MSI identifier: 0

MSI type [msi_type]: NIU2

8-30 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Checking the backhaul link

Checking the backhaul link■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The backhaul link checks verify the integrity of the links back to the BSC/MSC.

Test equipment required

The backhaul link checks require the following test equipment:

• An IBM compatible personal computer (PC).

• Terminal emulator software.

• A 9-way to 9-way cable (a diagram of this cable is provided in the Test equipment, leadsand plugs section).

All test equipment and test leads must be calibrated annually by a recognizedlaboratory. Test equipment and test leads must not be calibrated in the eld.

Do not optimize Motorola cellular base stations with test equipment that is beyondits calibration due date.

Allow test equipment to warm up for 30 minutes before use.

Commands used

The following command is used to carry out the procedure:

Command Function

state Displays the status of specified devices orfunctions.

Test procedures for checking the backhaul link

There are two stages to the procedure:

• Preparation for the network backhaul link check on page 8-32.

• Backhaul link test procedure on page 8-32.

68P02903W31-C 8-31

Aug 2007

Checking the backhaul link Chapter 8: Site verication procedures

Preparation for the network backhaul link check

The following procedure is used to set up the equipment to check the backhaul links:

Procedure 8-11 Preparation for the network backhaul link check

1 Make sure the site is in call processing mode.

2 Connect the serial A port on the PC to the HIISC TTY port using the 9-way to9-way cable.

3 Start the terminal emulator program at the PC.

The system and the hardware are set up to check the backhaul links.

Backhaul link test procedure

Procedure 8-12 Backhaul link test procedure

1 Contact the BSC/MSC of the backhaul link to be tested, and request a loopbackon the relevant Digital Distribution Frame (DDF) port.

Repeat for all backhaul links.

• If the backhaul link has not been installed, perform this test atthe DDF in the site.

• If no DDF is fitted, do this test at the top of the cabinet.

2 Ascertain the site number, equipment list and MMS configuration.

3 At the CUST MMI prompt enter: state # MMS ** * where # is location, and * * * is dev/func id.For example: state 2 MMS 0 1 0Example system message on page 8-33 shows the system messagefrom the HIISC:If this display shows Unlocked and Disabled then the T43, cabling and thebackhaul link are all good.

Continued

8-32 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Checking the backhaul link

Procedure 8-12 Backhaul link test procedure (Continued)

If the loop is removed and the command re-entered, the result is displayed.

A delay in excess of 20 seconds may be required before a change instatus is registered.

If the display continues to show Unlocked and Busy, this may bebecause:

• The wrong connection is looped, if the cabling is direct.

• The MMS may be terminated by a device generating a backhaullink.

Example system message

DEVICE STATUS INFORMATION FOR LOCATION 2:OPER STATES: D:Disabled E:Enabled B:BusyADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition RelatedDevice State Reason dd/mm hh:mm:ss Function---------- ----- -------------------------- --------------- --------

MMS 0 1 0 B-U No reason 18/02 13:23:05 None

END OF STATUS REPORT

68P02903W31-C 8-33

Aug 2007

Checking PIX connections and alarms Chapter 8: Site verication procedures

Checking PIX connections and alarms■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The alarm tests check the serial connections and alarm status.

Test equipment required

The PIX connections and alarms checks require the following test equipment:

• An IBM compatible personal computer (PC).

• Terminal emulator software.

• A 9-way to 9-way cable.

All test equipment and test leads must be calibrated annually by a recognizedlaboratory. Test equipment and test leads must not be calibrated in the eld.

Do not optimize Motorola cellular base stations with test equipment that is beyondits calibration due date.

Allow test equipment to warm up for 30 minutes before use.

Commands used

The following commands are used to test the PIX connections:

Command Function

alarm_mode <site_id> on Enables alarm reporting for a specified site.

disp_act_alarm <site_id> Displays active alarms at the specified site.

equip <site_id> EAS Equip the external IAS alarm system at thespecified site.

8-34 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Checking PIX connections and alarms

Test procedures for checking PIX connections and alarms

There are two stages to the procedure:

• Preparing for the PIX connections and alarms test on page 8-35.

• PIX connection test procedure on page 8-36.

Preparing for the PIX connections and alarms test

Procedure 8-13 Preparing for the PIX connections and alarms test

1 Ensure that the software download has been completed.

2 Connect the serial A port on the PC to the master HIISC using the 9-way to9- way cable.

3 Start the terminal emulator program at the PC.

The system displays the CUST MMI prompt.

4 Enter the password at the CUST MMI prompt.

5 Use the equip <site_id> EAS command to set up reference conditions forchecking that the alarms operate correctly when the appropriate relay changesstate.

Refer to Technical Description: BSS Command Reference,(68P02901W23) for specific details regarding the equip command.

68P02903W31-C 8-35

Aug 2007

Checking PIX connections and alarms Chapter 8: Site verication procedures

PIX connection test procedure

The following procedure can be used to test the PIX connections on each PIX board.

Procedure 8-14 PIX connection test

1 At the CUST MMI prompt type: alarm_mode # onwhere # is the site number.

2 Connect a suitable test lead to the PIX connector.

Wait at least six seconds before continuing the testing. The time isrequired to allow polling to detect the presence of the test plug.

3 Type the disp_act_alarm command to view the alarms.The system displays all 8 alarms.

The display depends on the database settings, that is, whether a faultcondition is indicated by a closed loop or an open loop.

If the high power external fan module is fitted to the unit alarmchannel 8 is permanently closed circuit.

4 Change the state of each alarm using the test plug/lead. If the appropriaterelay is operating correctly, the alarm state changes accordingly (alarm eithercleared or activated).

5 Remove the test lead.The system clears the alarm display.

6 If testing Horizon II macro, repeat procedure for the second PIX board.

8-36 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Site restoration

Site restoration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

After Tx output power calibration procedures are completed, restore the site using the followingprocedure.

Commands used

Table 8-6 lists the commands for the site restoration procedure.

The symbol 0 used in the commands is a zero.

Table 8-6 VSWR and power calibration site restoration commands.

BSS MMI Command Function

unlock_device Frees the device for further use.

disp_act_alarm Displays active alarms at the specified site.

chglev Changes the DSP MMI security level.

cal_staus tall Displays: the flash retrieval status, the datapool validflag and the checksum for all calibration datapools.

disp_cal_data When transceiver is locked:Displays calibration data in the CMdatabase for the specified transceiver.When transceiver is unlocked:Displays calibration data in the RAM ofthe specified transceiver.

Site restoration procedure

After the Tx output power calibration is completed, restore the site by using the followingprocedure.

If the DRI does not become B-U because of the error, Tx Power Unachievable,please refer to the Tx output power calibration section of this document.

68P02903W31-C 8-37

Aug 2007

Site restoration Chapter 8: Site verication procedures

Procedure 8-15 Post Tx output power calibration site restoration

1

Ensure that RF power is OFF before connecting or disconnectingantenna cables. Severe burns may result if RF power is present whencables are connected or disconnected

Remove the signal generator and dummy load and reconnect the site RF cables.

2 Remove the 9-way to 9-way cable from the TTY interface port on the CTU2and connect to the HIISC TTY port.

3 Reset the CTU2 by:

• Horizon II macro and Horizon II mini – Tripping and resetting theappropriate circuit breaker.

• Horizon II micro – Switching the PSU to output disable (off) and thenswitching to output enable (on) again.

(The CTU2 does not have a front panel reset button).

This step must be carried out to initialize software and so ensure thatthe CTU2 is correctly brought into service.

4 Type:unlock_device <site_id> dri <Cell_id> <DRI_identity> 0The CTU2 is now in the BUSY-UNLOCKED state.

5 Type:disp_act_alarm <site_id> dri <Cell_id> <DRI_identity> 0Confirm that there is no DRI 218 alarm. If there is a DRI 218 alarm, redo thewhole bay level calibration procedure.

6 Remove the 9-way to 9-way cables from the HIISC TTY port and connect tothe TTY interface port on the CTU2.

7 At the DSP MMI prompt type:chglevpizza(this is a password and appears on screen as *****)

Continued

8-38 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Site restoration

Procedure 8-15 Post Tx output power calibration site restoration (Continued)

8 Verify the calibration result and datapool valid flag by typingcal_status tallat the command line and comparing with theExample of calibration status on page 8-40.Confirm that the Result and Valid Checksum values are pass and valid,respectively, for both TX CAB A and TX CAB B.

If these values are incorrect the appropriate calibration must berepeated.

9 Verify the antenna calibration data or transmit power offset by typingdisp_cal_data <site_id> DRI <device_id> <device_id2> [<device_id3>]at the command line and comparing with the Exampleof calibration data format (for antenna 0) on page 8-41.Confirm that the value for the Transmit Power Offsets is correct.

If this value is incorrect the Tx power output calibration must berepeated.

10 Remove the 9-way to 9-way cable from the TTY interface port on the CTU2.

68P02903W31-C 8-39

Aug 2007

Site restoration Chapter 8: Site verication procedures

Example of calibration status

Entering the cal_status tall command gives a result similar to the example below:

System response:

CTU2.carA.ts_0>cal_status tallCal Ca Br Status Result Valid.Checksum Ver S/HC---------------------------------------------------------------------RF Lop A 0 pass valid 0x0672d5b5 1 / 1RF Lop B 0 pass valid 0x0d7b5025 1 / 1RX RF A 0 pass valid 0x2ae0b9fc 1 / 1RX RF A 1 pass valid 0x2bb91f4a 1 / 1RX RF B 0 pass valid 0x2c1ed905 1 / 1RX RF B 1 pass valid 0x2b063b6b 1 / 1RX IF A 0 pass valid 0xc8bc3caf 1 / 1RX IF A 1 pass valid 0xc8d99f37 1 / 1RX IF B 0 pass valid 0xc8dadb3f 1 / 1RX IF B 1 pass valid 0xc8bfbd0a 1 / 1RX FR A 0 pass valid 0xa8fe3af6 1 / 1RX FR A 1 pass valid 0xa8e8ba39 1 / 1RX FR B 0 pass valid 0xa8fb5db7 1 / 1RX FR B 1 pass valid 0xa8f593e0 1 / 1RX CAB A 0 pass valid 0x53703256 0 / 1RX CAB B 0 pass valid 0x45562835 0 / 1TX VVA A 0 pass valid 0xb0be7eb2 1 / 1TX VVA B 0 pass valid 0x96686359 1 / 1TX DSA A 0 pass valid 0x01a775df 1 / 1TX DSA B 0 pass valid 0x01a7863a 1 / 1TX FP A 0 pass valid 0x09e81286 1 / 1TX FP B 0 pass valid 0x07c8ee22 1 / 1TX Ver A 0 pass valid 0x064b1162 1 / 1TX Ver B 0 pass valid 0x063b5e9a 1 / 1TX CAB A 0 pass valid 0x019e2da9 1 / 1TX CAB B 0 pass valid 0x01bd2da9 1 / 1PA Det A 0 pass valid 0x15cc24be 1 / 1PA Det B 0 pass valid 0xd7dc8932 1 / 1PA VVA A 0 pass valid 0xda5d5f94 1 / 1

8-40 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Site restoration

Example of calibration data format (for antenna 0)

Entering the disp_cal_data <site_id> DRI <device_id> <device_id2> [<device_id3>]command, for example disp_cal_data 63 dri 0 0 0 gives a result similar to the examplebelow:

Where: is:

63 site

dri dri device

0 first dev_id

0 second dev_id

0 third dev_id

The example below shows the data from a calibration when Only antenna 0 was calibrated(It is recommended that all antennas are calibrated, but it is permissible to calibrate onlythe antennas to be used).

In the following example: antenna number 1 represents antenna 0A, antenna number 2represents antenna 1A, antenna number 3 represents antenna 2A, antenna number 4 representsantenna 0B, antenna number 5 represents antenna 1B, antenna number 6 represents antenna2B.

System response:

DRI ID: 0 0 0Data read from databaseStore Calibration Data: enabledCalibration Data (All values in Hex):Transmit Power Offsets = 12Receive System Data:Antenna Number 1 2 3 4 5 6---------------------------------------------

a4b, e80, e80, a7b, e80, e80a3e, e80, e80, aff, e80, e80a5d, e80, e80, b45, e80, e80a8e, e80, e80, b5e, e80, e80aca, e80, e80, b4b, e80, e80ae8, e80, e80, b64, e80, e80af3, e80, e80, b61, e80, e80af2, e80, e80, b8b, e80, e80ae3, e80, e80, b65, e80, e80ac0, e80, e80, b65, e80, e80a97, e80, e80, b46, e80, e80a70, e80, e80, ae7, e80, e80a2d, e80, e80, a6b, e80, e809f6, e80, e80, a28, e80, e809b7, e80, e80, 95e, e80, e80954, e80, e80, 91d, e80, e80943, e80, e80, 909, e80, e80921, e80, e80, 8e3, e80, e80911, e80, e80, 8d5, e80, e808ef, e80, e80, 8b7, e80, e808d0, e80, e80, 8a1, e80, e80899, e80, e80, 855, e80, e80

68P02903W31-C 8-41

Aug 2007

Site restoration Chapter 8: Site verication procedures

8-42 68P02903W31-C

Aug 2007

Chapter

9

Parts information for Horizon II micro■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter contains illustrated parts lists for the Horizon II micro to assist in identifying andordering FRUs and spares.

68P02903W31-C 9-1

Aug 2007

Horizon II micro parts list Chapter 9: Parts information for Horizon II micro

Horizon II micro parts list■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

In the parts lists contained in this chapter, each item consists of a location number (relatedto the associated diagram), description, and an order number. The order number uniquelyidentifies the required component. Some components may be used in other equipment inaddition to Horizon II micro.

FRU items

The majority of items on the parts list are field replaceable units (FRUs). It is not normallyintended to supply sub-units of these spares.

Ordering method

Contact the local Motorola office for ordering information, including cost and delivery.

• Motorola reserves the right to change the design of the product without notice.The information provided in this chapter is intended as a guide. If the customerrequires the latest information, then consult the Motorola local office who willbe able to check on the web and confirm the current situation.

• Some items, for example PSUs, are produced by different manufacturers, andso a replacement may appear slightly different to the item it is replacing. Allitems bearing the same order number, regardless of manufacturer, are fullycompatible.

9-2 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro FRUs

Horizon II micro FRUs■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Figure 9-1 and Figure 9-2 show the Horizon II micro enclosure module, including major FRUs,(with the doors and solar cove omitted, for clarity).

68P02903W31-C 9-3

Aug 2007

Horizon II micro FRUs Chapter 9: Parts information for Horizon II micro

Horizon II micro enclosure left accessible components

Figure 9-1 Horizon II micro enclosure components accessible from the left side

9-4 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro FRUs

Horizon II micro enclosure right accessible components

Figure 9-2 Horizon II micro enclosure components accessible from the right side

68P02903W31-C 9-5

Aug 2007

Horizon II micro FRUs Chapter 9: Parts information for Horizon II micro

Spares tables

The Horizon II micro spares are listed in the following tables:

• Table 9-1, Horizon II micro structural and thermal control spares, on page 9-6

• Table 9-2, Horizon II micro power distribution spares, on page 9-7

• Table 9-3, Horizon II micro RF component spares, on page 9-7

• Table 9-4, Horizon II micro digital module spares, on page 9-8

• Table 9-5, Expansion enclosure fibre optic cable pairs, on page 9-8

• Table 9-6, Miscellaneous spares for Horizon II micro, on page 9-8

Structural and thermal control spares

Table 9-1 shows the structural and thermal control spares of Horizon II micro.

Table 9-1 Horizon II micro structural and thermal control spares

Item Order Number

Enclosure SVHN8136

Enclosure door SVLN8482

Solar cover SYHN4679

Mounting Bracket SVLN8172

Pole-mounting bracket adapter kit SVLN8178

BIB/BIM SVLN2701

T43/CIM SVLN2700

Internal fan module (standard unit) SYHN4750

Internal fan module (high power unit) SYHN4756

External fan module (standard unit) SYHN4440

External fan module (high power unit) SYHN4442

Fan upgrade (high power to standard) SYHN4748

Fan upgrade (standard to high power) SYHN4749

Heat sensor, 75 °C (see Note) 4004825C02

Heat sensor, 85 °C (see Note) 4004825C03

Not identified as an FRU but available to order if required. Contact Motorola localoffice for further advice.

9-6 68P02903W31-C

Aug 2007

Service Manual: Horizon II micro Horizon II micro FRUs

Power distribution spares

Table 9-2 shows the power distribution spares of Horizon II micro.

Table 9-2 Horizon II micro power distribution spares

Item Order Number

88 to 270 V ac PSU SVPN8133

Horizon II mini battery module SVLN4465

RF component spares

Table 9-3 shows the RF component spares of Horizon II micro.

Table 9-3 Horizon II micro RF component spares

Item Order Number

900 MHz CTU2 SWRF9139

1800 MHz CTU2 SWRG9135

900 MHz CTU2D TBD

1800 MHz CTU2D TBD

900 MHz Mini-SURF SVRF4243

1800 MHz Mini-SURF SVRG4244

900 MHz Duplexer (DUP) SVLF9150

1800 MHz Duplexer (DUP) SVLG9153

PGSM duplexer SVLF7308A

68P02903W31-C 9-7

Aug 2007

Horizon II micro FRUs Chapter 9: Parts information for Horizon II micro

Digital module spares

Table 9-4 shows the digital module spares of Horizon II micro.

Table 9-4 Horizon II micro digital module spares

Item Order Number

Horizon II site controller (HIISC) SWLN9221

Expansion multiplexer (XMUX) SWLN9166

Alarm module SWLN9222

Site expansion board SWLN9159

Fibre optic cable spares

Table 9-5 shows the fibre optic cable spares available for Horizon II micro

Table 9-5 Expansion enclosure bre optic cable pairs

Order number Length Description

SVKN1244 5 m long connects master enclosure to first expansion,(indoor use only).

SVKN1245 7.6 m long connects master enclosure to second expansion,(indoor use only).

SVKN5973 7.0 m long connects master enclosure to first expansion,(outdoor use only).

SVKN5969 10 m long connects master enclosure to expansion, (indooror outdoor use).

SVKN5972 20 m long connects master enclosure to expansion, (indooror outdoor use).

Miscellaneous spares

Table 9-6 shows the miscellaneous spares available for Horizon II micro.

Table 9-6 Miscellaneous spares for Horizon II micro

Item Order Number

Compact flash card 5191096A09

CTU2 Tx cable 3086970W01

Duplexer to Mini SURF cable 3086225N01

9-8 68P02903W31-C

Aug 2007

Index

Index■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

16 kbit/s RSLs. . . . . . . . . . . . . . . 5-14

A

accessrestrictions . . . . . . . . . . . . . . . 6-10

access controlspecifications . . . . . . . . . . . . . . 1-12

acronymsindoor cabinet. . . . . . . . . . . . . . . 1-4

adaptive multirate (AMR) . . . . . . . . . . 4-8air interface. . . . . . . . . . . . . . . . . 4-8alarm module . . . . . . . . . . . . . . . 5-21

front panel LEDs . . . . . . . . . . . . 5-24hot swapping

effect on alarms. . . . . . . . . . . . 5-23inputs to . . . . . . . . . . . . . . . . 5-23

alarmsexternal . . . . . . . . . . . . . . . . . 5-21mini-SURF module . . . . . . . . . . . 4-28PIX

check . . . . . . . . . . . . . . . . . 8-36PSU . . . . . . . . . . . . . . . . . . . . 3-5

AMR (adaptive mutirate. . . . . . . . . . . 4-8

antennaduplexing

single Rx /Tx . . . . . . . . . . . . . . 4-4antenna 0

calibration statusexample . . . . . . . . . . . . . . . . 7-54

calibration status examplesite restoration CTU2 . . . . . . . . . 8-41

antennasVSWR monitoring . . . . . . . . . . . . . 4-6

approval and safetyspecifications . . . . . . . . . . . . . . 1-12

architectureHIISC . . . . . . . . . . . . . . . . . . 5-11

arrival at site . . . . . . . . . . . . . . . . 6-6attach chassis components . . . . . . . . . 7-6automatic power test

VSWRforward . . . . . . . . . . . . . . . . 8-16reverse . . . . . . . . . . . . . . . . 8-17

B

backhaulframing options . . . . . . . . . . . . . 5-12N-bit facility. . . . . . . . . . . . . . . 5-12

backhaul linkcheck . . . . . . . . . . . . . . . 8-31 to 8-32

commands . . . . . . . . . . . . . . 8-31preparation . . . . . . . . . . . . . . 8-32system message example . . . . . . . 8-33test equipment . . . . . . . . . . . . 8-31

backhaul LIU . . . . . . . . . . . . . . . 5-11backwards compatibility

CTU2 . . . . . . . . . . . . . . . . . . . 4-8balanced line interconnect board (BIB/BIM)

pinouts . . . . . . . . . . . . . . . . . 2-15view of . . . . . . . . . . . . . . . . . 2-15

balanced line interconnect module - see balancedline interconnect board (BIB/BIM) . . . . 2-15

baseband frequency hopping . . . . . . . 4-15battery

backupduration. . . . . . . . . . . . . . . . 1-18

battery module . . . . . . . . . . . . . . . 3-7features . . . . . . . . . . . . . . . . . . 3-9front panel LED . . . . . . . . . . . . . 3-10LEDs . . . . . . . . . . . . . . . . . . 3-10replace . . . . . . . . . . . . . . . . . 7-17

bay level calibrationfrequency tables

test . . . . . . . . . . . . . . . . . . 7-49RX . . . . . . . . . . . . . . . . . 7-41, 7-43

BBHrouting . . . . . . . . . . . . . . . . . . 5-6

68P02903W31-C IX-1

Aug 2007

Index

BBH - see also frequency hopping. . . . . 4-15BIB/BIM. . . . . . . . . . . . . . . . . . 2-15

pinouts . . . . . . . . . . . . . . . . . 2-15replacing . . . . . . . . . . . . . . . . 7-77

boardsBIB/BIM. . . . . . . . . . . . . . . . . 2-15CIM/T43 . . . . . . . . . . . . . . . . 2-16CTU2 internal . . . . . . . . . . . . . . . 4-9PA . . . . . . . . . . . . . . . . . . . . . 4-9replace

LIU . . . . . . . . . . . . . . . . . . 7-80site expansion. . . . . . . . . . . . . . 5-19T43/CIM . . . . . . . . . . . . . . . . 2-16XCVR . . . . . . . . . . . . . . . . . . . 4-9

boot codedownload restrictions . . . . . . . . . . 4-13

bracketpole mounting. . . . . . . . . . . . . . 2-27wall mounting. . . . . . . . . . . . . . 2-26

BSCpreserve calibration data

enable. . . . . . . . . . . . . . . . . 7-31BSC connectivity

options . . . . . . . . . . . . . . . . . 1-22button

CTU2 reset . . . . . . . . . . . . . . . 4-11CTU2D reset . . . . . . . . . . . . . . 4-19

C

cabinetdoors . . . . . . . . . . . . . . . . . . 2-24exterior inspection . . . . . . . . . . . 6-14interior inspection . . . . . . . . . . . 6-15pole mounting

bracket . . . . . . . . . . . . . . . . 2-27power consumption . . . . . . . . . . . 1-17power requirements . . . . . . . . . . 1-17restart . . . . . . . . . . . . . . . . . 2-19structure . . . . . . . . . . . . . . . . . 2-2temperature control. . . . . . . . . . . 2-17wall mounting

bracket . . . . . . . . . . . . . . . . 2-26cable entry box . . . . . . . . . . . . . . 2-14cables

part numbersfibre optic . . . . . . . . . . . . . . . . 9-8

CAL port on HIISC . . . . . . . . . . . . . 5-8calibration

bay level offset tablescommands . . . . . . . . . . . . . . 7-40test equipment . . . . . . . . . . . . 7-39

CTU2 . . . . . . . . . . . . . . . . . . 7-33bay level offset tables . . . . . . . . . 7-39check . . . . . . . . . . . . . . . . . 7-34

Rx bay level . . . . . . . . . . . . . 7-41, 7-43test frequency tables . . . . . . . . . 7-49

test leads . . . . . . . . . . . . . . . . . 8-6Tx output power . . . . . . . . . . 8-21, 8-25

additional CTU2s . . . . . . . . . . . 8-26preparation . . . . . . . . . . . . . . 8-22

CalibrationHIISC (GCLK) . . . . . . . . . . . . . . 7-70

calibration dataCTU2 . . . . . . . . . . . . . . . . . . 7-24

commands . . . . . . . . . . . . . . 7-25test equipment . . . . . . . . . . . . 7-25

exchange proceduresCTU2 . . . . . . . . . . . . . . . . . 7-32

calibration data (contd.)format. . . . . . . . . . . . . . . . . . 7-28preserve

CTU2 . . . . . . . . . . . . . . . 7-26, 7-32enable at BSC. . . . . . . . . . . . . 7-31enable at OMC-R . . . . . . . . . . . 7-30

calibration statusexample . . . . . . . . . . . . . . . . . 7-53

antenna 0 . . . . . . . . . . . . . . . 7-54site restoration CTU2 . . . . . . . . . 8-40

example antenna 0site restoration CTU2 . . . . . . . . . 8-41

cell siteCTU2

offset information . . . . . . . . . . . . 8-8channel numbers

Tx . . . . . . . . . . . . . . . . . . . . 8-27chassis components

attach . . . . . . . . . . . . . . . . . . . 7-6check

CTU2 calibration . . . . . . . . . . . . 7-34CTU2 recalibration . . . . . . . . . . . 7-37

CIM - see T43 interconnect board. . . . . 2-16CINDY commissioning tool

used for CSPWR calibration. . . . . 7-23, 8-2cleaning agents . . . . . . . . . . . . . . . 6-4clear calibration data . . . . . . . . . . . 7-27clear_cal_data

command . . . . . . . . . . . . . . . . 8-14code loading functions . . . . . . . . . . 5-10commands

backhaul linkcheck . . . . . . . . . . . . . . . . . 8-31

bay level offset tablesCTU2 calibration . . . . . . . . . . . 7-40

cell site power (CSPWR) . . . . . . . . . 8-8clear_cal_data. . . . . . . . . . . . . . 8-14CTU2 calibration . . . . . . . . . . . . 7-25database equippage

IX-2 68P02903W31-C

Aug 2007

Index

commands (contd.)database equippage (contd.)

check . . . . . . . . . . . . . . . . . 8-28PIX connectors and alarms

check . . . . . . . . . . . . . . . . . 8-34site restoration

power calibration CTU2. . . . . . . . 8-37VSWR check CTU2 . . . . . . . . . . 8-37

VSWR checkCTU2 . . . . . . . . . . . . . . . . . . 8-9CTU2 test . . . . . . . . . . . . . . . . 8-9

commissioning chargebattery module . . . . . . . . . . . . . . 3-9

compact flash card interface . . . . . . . . 5-8compatibility

Horizon macro . . . . . . . . . . . 1-8, 1-10M-Cell 6. . . . . . . . . . . . . . . . . . 1-8

compliancespecifications . . . . . . . . . . . . . . 1-12

componentsbattery module replace . . . . . . . . . 7-17chassis attach . . . . . . . . . . . . . . . 7-6CTU2 replace . . . . . . . . . . . . . . 7-20digital modules

spare parts list . . . . . . . . . . . . . 9-8doors replace . . . . . . . . . . . . . . . 7-8fan unit replace

external . . . . . . . . . . . . . . . . 7-13internal . . . . . . . . . . . . . . . . 7-11

fibre optic cablesspare parts list . . . . . . . . . . . . . 9-8

miscellaneousspare parts list . . . . . . . . . . . . . 9-8

non-FRUlist . . . . . . . . . . . . . . . . . . . 7-6replacing . . . . . . . . . . . . . . . . 7-6

power distributionspare parts list . . . . . . . . . . . . . 9-7

PSU replace. . . . . . . . . . . . . . . 7-16RF. . . . . . . . . . . . . . . . . . . . . 4-5

CTU2 . . . . . . . . . . . . . . . . . . 4-5duplexer . . . . . . . . . . . . . . . . 4-6spare parts list . . . . . . . . . . . . . 9-7

structural and thermal controlspare parts list . . . . . . . . . . . . . 9-6

components, non-FRU. . . . . . . . . . . . 7-6connections

PGSM duplexer . . . . . . . . . . . . . 4-37PIX

check . . . . . . . . . . . . . . . . . 8-36PIX test lead

site verification . . . . . . . . . . . . . 8-6TX blocks . . . . . . . . . . . . . . . . 4-30

connectorsCTU2 front panel . . . . . . . . . . . . 4-11CTU2D front panel . . . . . . . . . . . 4-19Tx blocks

connectors (contd.)Tx blocks (contd.)

duplexer . . . . . . . . . . . . . . . 7-61cover

maintenance . . . . . . . . . . . . . . . 6-9access. . . . . . . . . . . . . . . . . 6-10access restrictions . . . . . . . . . . 6-10

CSFPcode loading . . . . . . . . . . . . . . 5-10

CSPWRcalibration . . . . . . . . . . . . . . . 8-15

commands used . . . . . . . . . . . . 7-25test equipment required . . . . . . . 7-25use of CINDY commissioning tool . . . 7-23,7-39, 8-2

calibration data from databaseCTU2 . . . . . . . . . . . . . . . . . 7-28

clear calbration data . . . . . . . . . . 7-27display calibration offset data . . . . . . 7-26enable preserve CTU2 calibration data feature

at the BSC . . . . . . . . . . . . . . 7-31at the OMC-R . . . . . . . . . . . . . 7-30

site restoration after bay level calibration . . . . . . . . . . . . . . . . . . . 7-51site restoration after Tx output powercalibration . . . . . . . . . . . . . . . 8-37store calibration data . . . . . . . . . . 7-24

CSPWR calibrationdata enable

at BSC . . . . . . . . . . . . . . . . 7-31at OMC-R . . . . . . . . . . . . . . . 7-30

data overview . . . . . . . . . . . . . . 7-26CTU calibration

check . . . . . . . . . . . . . . . . . . 7-34CTU calibration data

preserve . . . . . . . . . . . . . . . . 7-26CTU2 . . . . . . . . . . . . . . . . . . . . 4-5

alarm data collection . . . . . . . . . . 4-14alarm reporting . . . . . . . . . . . . . 4-13backward compatibility . . . . . . . . . . 4-8bay level calibration procedure

commands . . . . . . . . . . . . . . 7-43calibrating bay level offset tables

commands used . . . . . . . . . . . . 7-40test equipment required . . . . . . . 7-39

calibrationpreserving . . . . . . . . . . . . . . 7-26

calibration data . . . . . . . . . . . . . 7-24commands . . . . . . . . . . . . . . 7-25test equipment . . . . . . . . . . . . 7-25

calibration data exchange procedures. . 7-32cell offset information. . . . . . . . . . . 8-8connector . . . . . . . . . . . . . . . . . 2-9connector functions . . . . . . . . . . . 4-11constraints when downloading bootcode. . . . . . . . . . . . . . . . . . . 4-13CSPWR calibration . . . . . . . . . . . 8-15

68P02903W31-C IX-3

Aug 2007

Index

CTU2 (contd.)features . . . . . . . . . . . . . . . . . . 4-8frequency hopping . . . . . . . . . . . 4-14front panel connectors . . . . . . . . . 4-12front panel detail . . . . . . . . . . . . 4-11front panel status indicators . . . . . . 4-13functional description . . . . . . . . . . . 4-8GMSK modulation. . . . . . . . . . . . 4-14interface function . . . . . . . . . . . . 4-14internal boards . . . . . . . . . . . . . . 4-9location . . . . . . . . . . . . . . . . . . 4-9overview . . . . . . . . . . . . . . . . . 4-8power amplifier . . . . . . . . . . . . . . 4-9power supply unit . . . . . . . . . . . . . 4-9recalibration

check . . . . . . . . . . . . . . . . . 7-37recalibration procedures . . . . . . . . 7-35receive role . . . . . . . . . . . . . . . . 4-3replace . . . . . . . . . . . . . . . . . 7-20resetting . . . . . . . . . . . . . . . . 4-11RF output . . . . . . . . . . . . . . . . . 4-9Rx function . . . . . . . . . . . . . . . 4-14

CTU2 (contd.)test interface port. . . . . . . . . . 4-12, 4-34transceiver board . . . . . . . . . . . . . 4-9transmit role . . . . . . . . . . . . . . . 4-3VCAT interface port . . . . . . . . . 4-12, 4-34VSWR . . . . . . . . . . . . . . . . . . . 8-8VSWR calibration . . . . . . . . . . . . 8-15

CTU2 calibration . . . . . . . . . . . . . 7-33CTU2 calibration data

preserve . . . . . . . . . . . . . . . . 7-32enable at BSC. . . . . . . . . . . . . 7-31enable at OMC-R . . . . . . . . . . . 7-30

CTU2Dconnector functions . . . . . . . . . . . 4-19Features . . . . . . . . . . . . . . . . 4-17Frequency hopping . . . . . . . . . . . 4-23front panel detail . . . . . . . . . . . . 4-19Internal function . . . . . . . . . . . . 4-23Overview . . . . . . . . . . . . . . . . 4-16resetting . . . . . . . . . . . . . . . . 4-19Rx function . . . . . . . . . . . . . . . 4-22

CTU2D functional description. . . . . . . 4-16

D

daisy chain cnfigurations . . . . . . . . . 5-12data exchange

calibration . . . . . . . . . . . . . . . 7-24commands . . . . . . . . . . . . . . 7-25test equipment . . . . . . . . . . . . 7-25

databasecheck equippage . . . . . . . . . . . . 8-29

additional CTU2s . . . . . . . . . . . 8-28commands . . . . . . . . . . . . . . 8-28test equipment . . . . . . . . . . . . 8-28

equippage checkpreparation . . . . . . . . . . . . . . 8-29

digital moduleslocations . . . . . . . . . . . . . . . . . 5-3redundancy . . . . . . . . . . . . . . . . 5-3removing a faulty module . . . . . . . . 7-68replacement. . . . . . . . . . . . . . . 7-66spare parts list . . . . . . . . . . . . . . 9-8

dimensions . . . . . . . . . . . . . . . . 1-13

diversityreception . . . . . . . . . . . . . . . . . 4-8

doors . . . . . . . . . . . . . . . . . . . 2-24inspection . . . . . . . . . . . . . . . . 6-15operating . . . . . . . . . . . . . . . . . 6-5replace . . . . . . . . . . . . . . . . . . 7-8

down conversion . . . . . . . . . . . . . 4-14dual band operation. . . . . . . . . . . . 4-25DUP

location . . . . . . . . . . . . . . . . . 7-59purpose of . . . . . . . . . . . . . . . 4-31VSWR monitor . . . . . . . . . . . . . 4-31

duplexer . . . . . . . . . . . . . . . . . . 4-6replace . . . . . . . . . . . . . . . . . 7-61

Duplexer (DUP) . . . . . . . . . . . . . . 4-31duplexing

single antennaRx/Tx . . . . . . . . . . . . . . . . . . 4-4

E

E1 connectivity . . . . . . . . . . . . . . 1-22earthquake proofing . . . . . . . . . . . 1-15electrical specifications . . . . . . . . . . 1-17EMC

specifications . . . . . . . . . . . . . . 1-12enclosure

structure . . . . . . . . . . . . . . . . . 2-2

environmentalspecifications . . . . . . . . . . . . . . 1-12

limits . . . . . . . . . . . . . . . . . 1-14equipment . . . . . . . . . . . . . . . . . 1-3

backhaul link

IX-4 68P02903W31-C

Aug 2007

Index

equipment (contd.)backhaul link (contd.)

check . . . . . . . . . . . . . . . . . 8-31database equippage

check . . . . . . . . . . . . . . . . . 8-28PIX connectors and alarms

check . . . . . . . . . . . . . . . . . 8-34test

site verification . . . . . . . . . . . . . 8-3VSWR check

CTU2 test . . . . . . . . . . . . . . . . 8-9example

antenna 0 calibration statussite restoration CTU2 . . . . . . . . . 8-41

calibration status . . . . . . . . . . . . 7-53

example (contd.)calibration status (contd.)

antenna 0 . . . . . . . . . . . . . . . 7-54site restoration CTU2 . . . . . . . . . 8-40

system messagebackhaul link check . . . . . . . . . . 8-33

expansion cabinetsalarm collection from . . . . . . . . . . 5-23transceiver . . . . . . . . . . . . . . . 5-23

expansion multiplexer - see XMUX . . . . 5-16external alarms . . . . . . . . . . . . . . 5-21external fan module . . . . . . . . . . . . 2-20

operation . . . . . . . . . . . . . . . . 2-20speed control . . . . . . . . . . . . . 2-20temperature sensors . . . . . . . . . 2-21

F

fading . . . . . . . . . . . . . . . . . . . . 4-8fan test pushbutton . . . . . . . . . . . . . 7-9fan unit

external . . . . . . . . . . . . . . . . . 2-20operation . . . . . . . . . . . . . . . 2-20

internal . . . . . . . . . . . . . . . . . 2-22operation . . . . . . . . . . . . . . . 2-23

replaceexternal . . . . . . . . . . . . . . . . 7-13internal . . . . . . . . . . . . . . . . 7-11

fastenerstorque values . . . . . . . . . . . . 1-14, 6-4

faulty devicesreporting . . . . . . . . . . . . . . . . . 6-2

fibre optic cablesspare parts list . . . . . . . . . . . . . . 9-8

Flash EEPROMHIISC . . . . . . . . . . . . . . . . . . 5-10

flow controlbetween NIU control processor and site controlprocessor . . . . . . . . . . . . . . . . 5-14

forward power testVSWR

automatic . . . . . . . . . . . . . . . 8-16manual . . . . . . . . . . . . . . . . 8-18

frequenciesTx . . . . . . . . . . . . . . . . . . . . 8-27

frequencyband characteristics . . . . . . . . . . 1-21

frequency (contd.)capability . . . . . . . . . . . . . . . . 1-21

bands . . . . . . . . . . . . . . . . . 1-21hopping . . . . . . . . . . . . . . . . 1-21

channel numbers and test frequencies. . 7-49frequency hopping

baseband . . . . . . . . . . . . . . . . 4-15CTU2 . . . . . . . . . . . . . . . . . . 4-14synthesized . . . . . . . . . . . . . . . 4-15

Frequency hoppingCTU2D . . . . . . . . . . . . . . . . . 4-23

frequency tablesbay level calibration procedure

commands . . . . . . . . . . . . . . 7-49FRU

list . . . . . . . . . . . . . . . . . . . . 7-3locations . . . . . . . . . . . . . . . . . 7-4

FRU replacementFRU list . . . . . . . . . . . . . . . . . . 7-3FRU locations . . . . . . . . . . . . . . . 7-4overview . . . . . . . . . . . . . . . . . 7-2torque values . . . . . . . . . . . . . . . 7-3

FRUsordering spare parts . . . . . . . . . . . 9-2

functional descriptionmini-SURF module . . . . . . . . . . . 4-27XMUX. . . . . . . . . . . . . . . . . . 5-17

functionalityalarm module . . . . . . . . . . . . . . 5-23

G

GCLKcalibration . . . . . . . . . . . . . . . 7-70

GMSK modulation. . . . . . . . . . . 1-20, 4-14

68P02903W31-C IX-5

Aug 2007

Index

H

hardwareoperation

RF loopback. . . . . . . . . . . . . . . 4-6RF receive . . . . . . . . . . . . . . . . 4-2RF transmit . . . . . . . . . . . . . . . . 4-3

harnesses . . . . . . . . . . . . . . . . . . 2-6internal

function . . . . . . . . . . . . . . . . . 2-8mini-SURF . . . . . . . . . . . . . . . . 2-9

high power optionRF power output . . . . . . . . . . . . 1-19

HIISC . . . . . . . . . . . . . . . . . . 5-4, 5-6CAL port . . . . . . . . . . . . . . . . . 5-8code loading functions . . . . . . . . . 5-10connection to CTU2 . . . . . . . . . . . . 5-4

HIISC (contd.)diagram showing internal architecture . . . . . . . . . . . . . . . . . . . 5-11flash EPROM . . . . . . . . . . . . . . 5-10front panel interfaces . . . . . . . . . . . 5-8front panel switches and indicators . . . . 5-8functions . . . . . . . . . . . . . . . . . 5-6hard and soft resets . . . . . . . . . . . . 5-8red LED front panel alarm

CAUTION . . . . . . . . . . . . . 5-9, 5-34redundancy link . . . . . . . . . . . . . . 5-7SDRAM . . . . . . . . . . . . . . . . . 5-10XMUX functionality . . . . . . . . . . . 5-15

HIISC (GCLK)calibration . . . . . . . . . . . . . . . 7-70

I

indicatorsHIISC . . . . . . . . . . . . . . . . . . . 5-8

informationfinding in this manual . . . . . . . . . . . 1-2

interfacecompact flash card . . . . . . . . . . . . 5-8min-SURF to CTU2 . . . . . . . . . . . 4-28

Rx diversity . . . . . . . . . . . . . . 4-28NIU control processor to site controlprocessor . . . . . . . . . . . . . . . . 5-13TTY-MMI . . . . . . . . . . . . . . . . . 5-8

interface panel . . . . . . . . . . . . . . 2-12

interface panel and cable entry box . . . . 2-12interfaces

HIISC . . . . . . . . . . . . . . . . . . . 5-8PIX outputs . . . . . . . . . . . . . . . . 5-9

internal fan module . . . . . . . . . . . . 2-22operation . . . . . . . . . . . . . . . . 2-23

Internal functionCTU2D . . . . . . . . . . . . . . . . . 4-23

internal harnessesfunction . . . . . . . . . . . . . . . . . . 2-8

internal structure . . . . . . . . . . . . . . 2-6

L

LAPD, configuring links . . . . . . . . . . 5-13leaving for the site . . . . . . . . . . 6-6 to 6-7LED indication

operational check . . . . . . . . . . 6-13, 6-34LEDs

alarm module . . . . . . . . . . . . . . 5-24batttery module . . . . . . . . . . . . . 3-10HIISC . . . . . . . . . . . . . . . . 5-9, 5-34PSU . . . . . . . . . . . . . . . . . . . . 3-5

line interface module . . . . . . . . . . . 2-15connection . . . . . . . . . . . . . . . 2-15

linksLAPD . . . . . . . . . . . . . . . . . . 5-13

list of non-FRU components. . . . . . . . . 7-6

LIUtiming extraction . . . . . . . . . . . . 5-11

LIU replace . . . . . . . . . . . . . . . . 7-80location

CTU2 . . . . . . . . . . . . . . . . . . . 4-9digital modules . . . . . . . . . . . . . . 5-3power modules . . . . . . . . . . . . . . 3-2Tx blocks

duplexer . . . . . . . . . . . . . . . 7-59locations

FRUs . . . . . . . . . . . . . . . . . . . 7-4loop back test

RF system. . . . . . . . . . . . . . . . . 4-6low noise amplification . . . . . . . . . . 4-25

IX-6 68P02903W31-C

Aug 2007

Index

M

maintenance12 monthly . . . . . . . . . . . . . . . 6-12

operational check . . . . . . . . . . . 6-1224 monthly . . . . . . . . . . . . . . . 6-146-monthly . . . . . . . . . . . . . . . . 6-11

air inlet/exhausts cleaning . . . . . . 6-11annual check . . . . . . . . . . . . . . 6-13cabinet inspection

exterior . . . . . . . . . . . . . . . . 6-14interior . . . . . . . . . . . . . . . . 6-15

doors inspection . . . . . . . . . . . . 6-15routine

overview . . . . . . . . . . . . . . . . 6-2safety

overview . . . . . . . . . . . . . . . . 6-2maintenance cover . . . . . . . . . . . . . 6-9

access. . . . . . . . . . . . . . . . . . 6-10access restrictions . . . . . . . . . . . 6-10

Manchester encoding . . . . . . . . . . . 5-16manual power test

VSWRforward . . . . . . . . . . . . . . . . 8-18reverse . . . . . . . . . . . . . . . . 8-20

midplane . . . . . . . . . . . . . . . . . . 2-7mini-SURF . . . . . . . . . . . . . . . . . 4-5

functional description . . . . . . . . . . 4-27interface to CTU2 . . . . . . . . . . . . 4-28

Rx diversity . . . . . . . . . . . . . . 4-28low noise amplification . . . . . . . . . 4-25replace . . . . . . . . . . . . . . . . . 7-56splitter matrix. . . . . . . . . . . . . . 4-25

mini-SURF harness . . . . . . . . . . . . . 2-9mini-SURF module . . . . . . . . . . . . 4-25

alarms . . . . . . . . . . . . . . . . . 4-28mixed sites . . . . . . . . . . . . . . . . . 1-8modulation, GMSK . . . . . . . . . . . . 1-20modules

alarm . . . . . . . . . . . . . . . . . . 5-23alarms . . . . . . . . . . . . . . . . . 5-21battery . . . . . . . . . . . . . . . . . . 3-7fan

external . . . . . . . . . . . . . . . . 2-20internal . . . . . . . . . . . . . . . . 2-22

line interface . . . . . . . . . . . . . . 2-15location

digital . . . . . . . . . . . . . . . . . 7-66locations

digital . . . . . . . . . . . . . . . . . . 5-3mini-SURF . . . . . . . . . . . . . . . 4-25part numbers

digital . . . . . . . . . . . . . . . . . . 9-8power supply . . . . . . . . . . . . . . . 3-2redundancy

digital . . . . . . . . . . . . . . . . . . 5-3RF

mini-SURF . . . . . . . . . . . . . . . 4-5XMUX. . . . . . . . . . . . . . . . . . 5-16

mounting optionswall mounting. . . . . . . . . . . . . . 2-26

multipath fading . . . . . . . . . . . . . . 4-8

N

namesindoor cabinet. . . . . . . . . . . . . . . 1-4

NIUcontrol messages . . . . . . . . . . . . 5-13ethernet port . . . . . . . . . . . . . . . 5-8

non-FRU components . . . . . . . . . . . . 7-6chassis components

attach . . . . . . . . . . . . . . . . . . 7-6list . . . . . . . . . . . . . . . . . . . . 7-6replace . . . . . . . . . . . . . . . . . . 7-6

non-FRU components (contd.)replace (contd.)

battery module . . . . . . . . . . . . 7-17CTU2 . . . . . . . . . . . . . . . . . 7-20doors . . . . . . . . . . . . . . . . . . 7-8external fan unit . . . . . . . . . . . 7-13internal fan unit. . . . . . . . . . . . 7-11PSU . . . . . . . . . . . . . . . . . . 7-16

nternal boardsCTU2D . . . . . . . . . . . . . . . . . 4-17

O

offset tablesbay level

CTU2 calibration . . . . . . . . . . . 7-39OMC-R

OMC-R (contd.)preserve calibration data

enable. . . . . . . . . . . . . . . . . 7-30on-site safety . . . . . . . . . . . . . . . . 6-8

68P02903W31-C IX-7

Aug 2007

Index

operating limitsenvironmental. . . . . . . . . . . . . . 1-14

operationfan module

external . . . . . . . . . . . . . . . . 2-20internal . . . . . . . . . . . . . . . . 2-23

operational checkLED indicators . . . . . . . . . . . . . 6-12

ouput power calibrate

ouput power calibrate (contd.)Tx . . . . . . . . . . . . . . . . . . 8-21, 8-25

additional CTU2s . . . . . . . . . . . 8-26preparation . . . . . . . . . . . . . . 8-22

ouput power changeTx . . . . . . . . . . . . . . . . . . . . 8-22

outdoor enclosureweather conditions for unpacking. . . . . 6-9

over temperature . . . . . . . . . . . . . 2-18

P

PA board . . . . . . . . . . . . . . . . . . 4-9panels

interface . . . . . . . . . . . . . . . . 2-12parts information

FRUs . . . . . . . . . . . . . . . . . . . 9-2parts list tables

digital modules . . . . . . . . . . . . . . 9-8fibre optic cables . . . . . . . . . . . . . 9-8miscellaneous . . . . . . . . . . . . . . . 9-8power distribution . . . . . . . . . . . . 9-7RF. . . . . . . . . . . . . . . . . . . . . 9-7structural and thermal control . . . . . . 9-6

PGSMreplace . . . . . . . . . . . . . . . . . 7-61

PGSM connections . . . . . . . . . . . . 4-37PGSM duplexer . . . . . . . . . . . . . . 4-34physical specifications . . . . . . . . . . 1-13PIX alarms

check . . . . . . . . . . . . . . . . . . 8-36preparation . . . . . . . . . . . . . . 8-35

PIX connectionscheck . . . . . . . . . . . . . . . . . . 8-36

reparation. . . . . . . . . . . . . . . 8-35PIX connections and alarms

commandscheck . . . . . . . . . . . . . . . . . 8-34

test equipment . . . . . . . . . . . . . 8-34PIX output

interfaces . . . . . . . . . . . . . . . . . 5-9pole mounting

bracket . . . . . . . . . . . . . . . . . 2-27power calibration

commandssite restoration . . . . . . . . . . . . 8-37

power consumption . . . . . . . . . . . . 1-17power distribution

spare parts list . . . . . . . . . . . . . . 9-7power requirements. . . . . . . . . . . . 1-17

outdoor enclosure. . . . . . . . . . . . 1-17power supply

modules . . . . . . . . . . . . . . . . . . 3-2power supply modules . . . . . . . . . . . 3-3power supply units (PSUs)

from different manufacturers, compatibility . . . . . . . . . . . . . . . . . . . . 7-15replace . . . . . . . . . . . . . . . . . 7-16

power testforward automatic

VSWR . . . . . . . . . . . . . . . . . 8-16forward manual

VSWR . . . . . . . . . . . . . . . . . 8-18reverse automatic

VSWR . . . . . . . . . . . . . . . . . 8-17reverse manual

VSWR . . . . . . . . . . . . . . . . . 8-20procedures

site verification . . . . . . . . . . . . . . 8-2PSU . . . . . . . . . . . . . . . . . . . . . 3-3

alarms . . . . . . . . . . . . . . . . . . 3-5LEDs . . . . . . . . . . . . . . . . . . . 3-5part number . . . . . . . . . . . . . . . 9-7redundancy . . . . . . . . . . . . . . . . 3-3supply protection . . . . . . . . . . . . . 3-6

pushbuttonfan test . . . . . . . . . . . . . . . . . . 7-9

R

rapid site initialization . . . . . . . . . . . 5-8recalibration

CTU2 . . . . . . . . . . . . . . . . . . 7-36receive

RF hardware . . . . . . . . . . . . . . . 4-2

receiver sensitivity . . . . . . . . . . . . 1-20redundancy

digital modules . . . . . . . . . . . . . . 5-3HIISC link. . . . . . . . . . . . . . . . . 5-7PSU . . . . . . . . . . . . . . . . . . . . 3-3

IX-8 68P02903W31-C

Aug 2007

Index

replacedigital modules . . . . . . . . . . . . . 7-67duplexer . . . . . . . . . . . . . . . . 7-61LIU . . . . . . . . . . . . . . . . . . . 7-80mini-SURF module . . . . . . . . . . . 7-56

replacement procedures . . . . . . . . . . 7-2FRU list . . . . . . . . . . . . . . . . . . 7-3FRU locations . . . . . . . . . . . . . . . 7-4torque values . . . . . . . . . . . . . . . 7-3

replacing non-FRU components . . . . . . . 7-6restart . . . . . . . . . . . . . . . . . . 2-19restrictions

access. . . . . . . . . . . . . . . . . . 6-10reverse power test

VSWRautomatic . . . . . . . . . . . . . . . 8-17manual . . . . . . . . . . . . . . . . 8-20

RFpower output . . . . . . . . . . . . . . 1-18

high power . . . . . . . . . . . . . . 1-19standard . . . . . . . . . . . . . . . 1-19

spare parts list . . . . . . . . . . . . . . 9-7RF components

CTU2D . . . . . . . . . . . . . . . . . . 4-5mini-SURF . . . . . . . . . . . . . . . . 4-5

RF componets. . . . . . . . . . . . . . . . 4-5CTU2 . . . . . . . . . . . . . . . . . . . 4-5duplexer . . . . . . . . . . . . . . . . . 4-6

RF equipmentdescription . . . . . . . . . . . . . . . . 4-2specifications . . . . . . . . . . . . . . . 4-2VSWR monitoring . . . . . . . . . . . . . 4-2

RF hardwarereceive . . . . . . . . . . . . . . . . . . 4-2transmit. . . . . . . . . . . . . . . . . . 4-3

RF loopback testantenna monitoring . . . . . . . . . . . . 4-6hardware operation . . . . . . . . . . . . 4-6software operation . . . . . . . . . . . . 4-6

RF specifications . . . . . . . . . . . . . 1-17RF tx output

specificationsCTU2 . . . . . . . . . . . . . . . . . . 4-9

routine maintenance12-monthly procedures . . . . . . . . . 6-1224-monthly procedures . . . . . . . . . 6-146-monthly procedures . . . . . . . . . . 6-11

air inlets/outlets cleaning . . . . . . . 6-11annual checks. . . . . . . . . . . . . . 6-13checking normal operation . . . . . . . 6-12cleaning agents . . . . . . . . . . . . . . 6-4door operation . . . . . . . . . . . . . . 6-5mechanical inspection . . . . . . . . . 6-14overview . . . . . . . . . . . . . . . . . 6-2

safety . . . . . . . . . . . . . . . . . . 6-2recommended intervals . . . . . . . . . . 6-3reporting equipment failures . . . . . . . 6-2reporting safety issues . . . . . . . . . . 6-2tools . . . . . . . . . . . . . . . . . . . 6-4

RSL16kbit/s . . . . . . . . . . . . . . . . . 5-14

RSL and span alarms . . . . . . . . . . . 5-14rural sites . . . . . . . . . . . . . . . . . . 6-7Rx bay level

calibration . . . . . . . . . . . . . 7-41, 7-43frquency tables

test . . . . . . . . . . . . . . . . . . 7-49Rx diversity

CT2 interface to mini-SURF. . . . . . . 4-28

S

safety and approvalspecifications . . . . . . . . . . . . . . 1-12

safety issueson site. . . . . . . . . . . . . . . . . . . 6-8

SDRAMHIISC . . . . . . . . . . . . . . . . . . 5-10

secondary cage . . . . . . . . . . . . . . 2-10sensors

temperature. . . . . . . . . . . . . . . 2-19SFH - see frequency hopping . . . . . . . 4-15site

layout plan . . . . . . . . . . . . . . . 1-15mixed . . . . . . . . . . . . . . . . . . . 1-8verification

test equipment . . . . . . . . . . . . . 8-3test lead calibration. . . . . . . . . . . 8-6test leads for . . . . . . . . . . . . . . 8-5

verification procedures . . . . . . . . . . 8-2

site (contd.)visiting . . . . . . . . . . . . . . . . . . 6-6

site control processor . . . . . . . . 5-12 to 5-13site controller

HIISC . . . . . . . . . . . . . . . . . . . 5-6site expansion

using mixed hardware . . . . . . . . . 5-17site expansion board . . . . . . . . . 5-4, 5-19

I/O connectors . . . . . . . . . . . . . 5-19primary function . . . . . . . . . . . . 5-19

site restorationafter bay level calibration . . . . . . . . 7-51after Tx output power calibration . . . . 8-37commands

power calibration CTU2. . . . . . . . 8-37VSWR check CTU2 . . . . . . . . . . 8-37

site safety . . . . . . . . . . . . . . . . . . 6-8

68P02903W31-C IX-9

Aug 2007

Index

site visitingarrival. . . . . . . . . . . . . . . . . . . 6-6before leaving. . . . . . . . . . . . 6-6 to 6-7rural sites . . . . . . . . . . . . . . . . . 6-7safety . . . . . . . . . . . . . . . . . . . 6-8waste material . . . . . . . . . . . . . . 6-7

softwareoperation

RF loopback. . . . . . . . . . . . . . . 4-6software requirements

specifications . . . . . . . . . . . . . . 1-12solar cover . . . . . . . . . . . . . . . . . 2-5

remove/refit . . . . . . . . . . . . . . . . 6-5span alarms

reporting . . . . . . . . . . . . . . . . 5-14spare parts

listdigital modules . . . . . . . . . . . . . 9-8fibre optic cables . . . . . . . . . . . . 9-8miscellaneous . . . . . . . . . . . . . . 9-8power distribution . . . . . . . . . . . 9-7RF . . . . . . . . . . . . . . . . . . . 9-7structural and thermal control . . . . . 9-6

ordering. . . . . . . . . . . . . . . . . . 9-2specifications

access control. . . . . . . . . . . . . . 1-12approval and safety . . . . . . . . . . . 1-12battery backup duration . . . . . . . . 1-18BSC connectivity . . . . . . . . . . . . 1-22compliance . . . . . . . . . . . . . . . 1-12dimensions . . . . . . . . . . . . . . . 1-13electrical and RF . . . . . . . . . . . . 1-17environmental limits . . . . . . . . . . 1-14frequency bands . . . . . . . . . . . . 1-21frequency capability . . . . . . . . . . 1-21frequency hopping . . . . . . . . . . . 1-21introduction. . . . . . . . . . . . . . . 1-12physical . . . . . . . . . . . . . . . . . 1-13power consumption . . . . . . . . . . . 1-17power requirements . . . . . . . . . . 1-17receiver sensitivity . . . . . . . . . . . 1-20RF equipment . . . . . . . . . . . . . . . 4-2

specifications (contd.)RF output Tx

CTU2 . . . . . . . . . . . . . . . . . . 4-9RF power output . . . . . . . . . . . . 1-18site plan. . . . . . . . . . . . . . . . . 1-15software requirements . . . . . . . . . 1-12structural considerations . . . . . . . . 1-15torque values . . . . . . . . . . . . . . 1-14weights . . . . . . . . . . . . . . . . . 1-13

splitter matrix. . . . . . . . . . . . . . . 4-25stages

VSWR checkCTU2 test . . . . . . . . . . . . . . . 8-11

stand-by link alarmin mixed configuration . . . . . . . . . . 5-4

standard optionRF power output . . . . . . . . . . . . 1-19

storage limitsenvironmental. . . . . . . . . . . . . . 1-14

storing calibration data . . . . . . . . . . 7-27structural and thermal control

spare parts list . . . . . . . . . . . . . . 9-6structural considerations

specifications . . . . . . . . . . . . . . 1-15structure

cabinet . . . . . . . . . . . . . . . . . . 2-2harnesses . . . . . . . . . . . . . . . . . 2-6

internal . . . . . . . . . . . . . . . . . 2-8internal . . . . . . . . . . . . . . . . . . 2-6midplane . . . . . . . . . . . . . . . . . 2-7secondary cage . . . . . . . . . . . . . 2-10solar cover . . . . . . . . . . . . . . . . 2-5

supplyprotection

PSU . . . . . . . . . . . . . . . . . . . 3-6switches

HIISC . . . . . . . . . . . . . . . . . . . 5-8sync block clock

calibrating . . . . . . . . . . . . . . . . 5-8SYNC/NIU TTY port . . . . . . . . . . . . . 5-8synthesized frequency hopping . . . . . . 4-15

T

T43 interconnect board (CIM). . . . . . . 2-16connection . . . . . . . . . . . . . . . 2-16pinouts . . . . . . . . . . . . . . . . . 2-16replacing . . . . . . . . . . . . . . . . 7-77

temperature control. . . . . . . . . . . . 2-17overheat conditions . . . . . . . . . . . 2-18

temperature sensors . . . . . . . . . . . 2-19test

RF loopback. . . . . . . . . . . . . . . . 4-6test equipment

backhaul link

test equipment (contd.)backhaul link (contd.)

check . . . . . . . . . . . . . . . . . 8-31CTU2 bay level offset tables

calibration . . . . . . . . . . . . . . 7-39CTU2 calibration . . . . . . . . . . . . 7-25database equippage

check . . . . . . . . . . . . . . . . . 8-28PIX connectors and alarms

check . . . . . . . . . . . . . . . . . 8-34site verification . . . . . . . . . . . . . . 8-3

IX-10 68P02903W31-C

Aug 2007

Index

test equipment (contd.)VSWR check

CTU2 . . . . . . . . . . . . . . . . . . 8-9test leads

calibration . . . . . . . . . . . . . . . . 8-6test stages

VSWR checkCTU2 . . . . . . . . . . . . . . . . . 8-11

timeslot interchanger . . . . . . . . . . . 5-12tools. . . . . . . . . . . . . . . . . . . . . 6-4torque values . . . . . . . . . . . . . . . 1-14

cabinet screwbolts and RF connectors . . 6-4list . . . . . . . . . . . . . . . . . . . . 7-3

transmitRF hardware . . . . . . . . . . . . . . . 4-3

TSI . . . . . . . . . . . . . . . . . . . . 5-12TTY/MMI interface . . . . . . . . . . . . . 5-8Tx

channel numbers . . . . . . . . . . . . 8-27frequencies . . . . . . . . . . . . . . . 8-27

Tx blocksconnectors

duplexer . . . . . . . . . . . . . . . 7-61location

duplexer . . . . . . . . . . . . . . . 7-59TX blocks

overview . . . . . . . . . . . . . . . . 4-30Tx ouput power

calibration . . . . . . . . . . . . . . . 8-21additional CTU2s . . . . . . . . . . . 8-26

Tx ouput power checkVSWR check

CTU2 . . . . . . . . . . . . . . . 8-7, 8-16Tx output power

calibration . . . . . . . . . . . . . . . 8-25preparation . . . . . . . . . . . . . . 8-22preparations . . . . . . . . . . . . . 8-11

change . . . . . . . . . . . . . . . . . 8-22

V

verificationsite procedures

LIU . . . . . . . . . . . . . . . . . . . 8-2visiting a site . . . . . . . . . . . . . . . . 6-6VSWR

antenna monitoring . . . . . . . . . . . . 4-6calibration . . . . . . . . . . . . . . . 8-15

VSWR check . . . . . . . . . . . . . . . . 8-7automatic forward power test . . . . . . 8-16automatic reverse power test . . . . . . 8-17commands . . . . . . . . . . . . . . . . 8-9preparation . . . . . . . . . . . . . . . 8-11

VSWR check (contd.)test equipment . . . . . . . . . . . . . . 8-9test stages . . . . . . . . . . . . . . . 8-11Tx output power . . . . . . . . . . 8-7, 8-16

VSWR checksmanual forward power test . . . . . . . 8-18manual reverse power test . . . . . . . 8-20

VSWR monitoringRF equipment . . . . . . . . . . . . . . . 4-2

VSWR restorationcommands

site restoration . . . . . . . . . . . . 8-37

W

wall mountingbracket . . . . . . . . . . . . . . . . . 2-26

waste material on site. . . . . . . . . . . . 6-7

weather conditions . . . . . . . . . . . . . 6-9access restrictions . . . . . . . . . . . 6-10

weights . . . . . . . . . . . . . . . . . . 1-13

X

XCVR board . . . . . . . . . . . . . . . . . 4-9XMUX. . . . . . . . . . . . . . . . . . . 5-16

XMUX (contd.)functional description . . . . . . . . . . 5-17

68P02903W31-C IX-11

Aug 2007

Standard Printing Instructions

Part Number 68P02903W31-C

Manual Title Service Manual: Horizon II micro

Date August 2007

A5 Ring Bound - GSD (UK)

Binder • D-ring binder – A5 size (148.5mm x 210mm) white PVC.

• 40mm or 65mm capacity depending on the size of the manual.

• Clear pockets on front and spine.

Printing • Cover / spine text overprinted onto Motorola supplied cover stock.

• Body- printed double sided onto white A5 size (148.5mm x 210mm) 80g 3 hole paper.

• Photo reduce to A5.

Finishing • A5 size (148.5mm x 210mm) clear PVC sheet front page for protection.

• Bag wrapped with clear polythene.

If this is to be used by manufacturing as an Inbox document, then refer to appropriate Materials or Methods Specification.