Motorola BSS Optimization

CHAPTER 1
INTRODUCTION TO BSS
OPTIMIZATION
CHAPTER 2
INCELL, EXCELL & TOPCELL
OPTIMIZATION
CHAPTER 3
M-CELL2 & M-CELL6
OPTIMIZATION
CHAPTER 4
PRESERVE CALIBRATION
CHAPTER 5
MICROCELLULAR SYSTEMS
OPTIMIZATION
CHAPTER 6
BASE SITE INTEGRATION
CHAPTER 7
CHANNEL NUMBERS AND
FREQUENCIES
CHAPTER 8
NETWORK OPTIMIZATION
CHAPTER 9
OPTIMIZATION RESULTS
FORMS
INDEX
68P02901W43-P GMR-01
68P02901W43-P GMR-01
GSM Manual Revision dated 23 Feb 2004
Motorola manual affected

This Manual Revision is applicable only to the manual number and version listed below:
68P02901W58-P
Installation & Configuration: BSS Optimization

GSM Software Release 7
Service requests
This revision provides a fix to the following service requests:
None
Reason for revision

This revision provides additional and updated information as follows:
Chap 2
to
Chap 6:
Formatting improvements.
There are no technical changes to this manual for this revision
Action
Remove and replace pages in the manual as follows:
Remove
Insert
All pages between the clear acetate

front sheet and the blank backing sheet,
remove from binder.
All pages of the GMR between the front

sheet and the blank backing sheet, insert
into binder.
68P02901W43-P
23 Feb 2004
GMR-01
68P02901W43-P GMR-01
Obsolete pages
Destroy all obsolete pages. Do not destroy this page.
Completion
On completion of the Manual Revision, insert this Manual Revision sheet in the front
or back of the manual, for future reference.
Motorola service web

The Motorola Service Web at url: http://mynetworksupport.motorola.com/mysupport.asp is
updated to coincide with printed release of this GMR.
CD-ROM
The Motorola documentation CD-ROM that contains this manual will be updated to include
this GMR at the next issue after the printed release.
GMR-01
68P02901W43-P
23 Feb 2004
INSTALLATION & CONFIGURATION

BSS OPTIMIZATION
GSM SOFTWARE RELEASE 7
GSR7
GMR-01
68P02901W43-P
INSTALLATION & CONFIGURATION

BSS OPTIMIZATION
GSM SOFTWARE RELEASE 7
GMR-01
GSR7
68P02901W43-P
Installation & Configuration: BSS

Optimization
1994 - 2004 Motorola, Inc.

All Rights Reserved
GMR-01
68P02901W43-P
23 Feb 2004
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media.
Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to
copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products
described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent
applications of Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in
accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of
the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language,
in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions
in this document, or from the use of the information obtained herein. Motorola 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 content hereof with no obligation to
notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein;
neither does it convey license under its patent rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
GMR-01
23 Feb 2004
Table
of
Contents
Contents

Issue status of this manual . . . . . .
Version information . . . . . . .
Resolution of Service Requests. .
Version updates . . . . . . . . .
General information . . . . . . . . .
Purpose . . . . . . . . . . . .
Feature references. . . . . . . .
Cross references . . . . . . . .
Data encryption . . . . . . . . .
Text conventions . . . . . . . .
Reporting safety issues . . . . . . .
Procedure . . . . . . . . . . .
Warnings and cautions . . . . . . . .
Warnings . . . . . . . . . . . .
Failure to comply with warnings .
Cautions . . . . . . . . . . . .
General warnings . . . . . . . . . .
Warning labels . . . . . . . . .
Specific warnings . . . . . . . .
General cautions . . . . . . . . . .
Caution labels. . . . . . . . . .
Specific cautions . . . . . . . .
Devices sensitive to static . . . . . .
Special handling techniques . . .
Motorola manual set . . . . . . . . .
Ordering manuals and CD-ROMs
GMR amendment . . . . . . . . . .
GMR availability . . . . . . . .
GMR instructions . . . . . . . .
GMR amendment record. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
3
3
4
4
4
5
5
6
7
7
8
8
8
8
10
10
10
14
14
14
15
15
16
16
17
17
17
18
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-2
1-2
1-3
1-3
1-3
Chapter 1: Introduction to BSS optimization

Using this manual . . . . .
Audience . . . . . . .
Prerequisites . . . . .
Structure . . . . . . .
Test equipment . . . .
Related documentation
Equipment supported .
68P02901W43-P
23 Feb 2004
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
GMR-01
Contents
Chapter 2: InCell, ExCell and TopCell optimization

Introduction to InCell, ExCell and TopCell optimization . . . . . . .
Code download . . . . . . . . . . . . . . . . . . . . . . . .
CINDY commissioning tool . . . . . . . . . . . . . . . . . .
Test equipment, leads and plugs . . . . . . . . . . . . . . . . . .
Test equipment required . . . . . . . . . . . . . . . . . . . .
Test leads required . . . . . . . . . . . . . . . . . . . . . .
Test plugs required . . . . . . . . . . . . . . . . . . . . . .
DC power supply test . . . . . . . . . . . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . . . . . . . . . .
Preparation for the dc power supply test . . . . . . . . . . . .
DC power supply test procedure . . . . . . . . . . . . . . . .
Site restoration . . . . . . . . . . . . . . . . . . . . . . . .
Circuit breaker tables . . . . . . . . . . . . . . . . . . . . .
RTC manual tuning . . . . . . . . . . . . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . . . . . . . . . .
Preparation for manually tuning the RTC . . . . . . . . . . . .
RTC manual tuning procedure . . . . . . . . . . . . . . . . .
DRCU, DRCUII and DRCU3 Tx power calibration and VSWR check
Commands used . . . . . . . . . . . . . . . . . . . . . . .
Preparation for Tx power calibration and VSWR check . . . . .
Tx forward power test procedure . . . . . . . . . . . . . . . .
Tx reverse power test procedure . . . . . . . . . . . . . . . .
Tx output power setting procedure . . . . . . . . . . . . . . .
DRCU, DRCUII and DRCU3 bay level offset tables calibration . . .
Commands used . . . . . . . . . . . . . . . . . . . . . . .
Preparation for bay level table calibration . . . . . . . . . . . .
Calibration setup procedure . . . . . . . . . . . . . . . . . .
Calibration with a six-way splitter procedure . . . . . . . . . .
Calibration with a receive matrix procedure . . . . . . . . . . .
Stored bay level offset verification procedure . . . . . . . . . .
SCU Tx power calibration and VSWR check . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . . . . . . . . . .
Preparation for Tx power calibration and VSWR check . . . . .
Tx forward power test procedure . . . . . . . . . . . . . . . .
Tx reverse power test procedure . . . . . . . . . . . . . . . .
Tx output power setting procedure . . . . . . . . . . . . . . .
SCU900/1800 bay level offset tables calibration . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . . . . . . . . . .
Setting up procedure . . . . . . . . . . . . . . . . . . . . .
GSM900 and DCS1800 test frequencies . . . . . . . . . . . .
Branch1 RX1A bay level offsets calibration procedure. . . . . .
Branch 1 RX2A bay level offsets calibration procedure . . . . .
Branch 1 RX3A bay level offsets calibration procedure . . . . .
Branch 1 completion . . . . . . . . . . . . . . . . . . . . .
Branch 2 bay level offsets calibration . . . . . . . . . . . . . .
ii
GMR-01
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-2
2-3
2-4
2-4
2-5
2-7
2-9
2-9
2-9
2-9
2-10
2-11
2-11
2-14
2-14
2-14
2-14
2-15
2-16
2-17
2-17
2-19
2-20
2-21
2-21
2-22
2-23
2-23
2-24
2-25
2-26
2-27
2-28
2-29
2-31
2-32
2-33
2-33
2-34
2-35
2-37
2-37
2-38
2-39
2-39
2-40
2-41
2-42
2-44
2-45
2-45
2-46
2-46
68P02901W43-P
23 Feb 2004
Calibration check procedure . . . . . .

Diagnostic check procedure . . . . . .
Site restoration . . . . . . . . . . . .
Database check for devices and functions . .
Test equipment required . . . . . . . .
Commands used . . . . . . . . . . .
Database check procedure . . . . . . .
E1/T1 link check . . . . . . . . . . . . .
Commands used . . . . . . . . . . .
E1/T1 link test procedure . . . . . . .
PIX connections check. . . . . . . . . . .
Commands used . . . . . . . . . . .
Preparation for PIX connections check .
PIX connections test procedure. . . . .
Transcoder integration . . . . . . . . . . .
Introduction to transcoder integration .
Commands used . . . . . . . . . . .
Displaying MMS timeslot usage . . . .
Displaying BSC-MSC connectivity. . .
CIC test procedure . . . . . . . . . .
GCLK calibration . . . . . . . . . . . . .
Commands used . . . . . . . . . . .
Preparation for GCLK calibration . . .
Clearing GCLK LTA values . . . . . .
GCLK frequency adjustment procedure.
GCLK calibration record form . . . . .
ExCell alarms check . . . . . . . . . . . .
Commands used . . . . . . . . . . .
Preparation for the alarms check . . . .
ExCell alarm list . . . . . . . . . . .
Smoke alarm check procedure . . . . .
Overtemperature alarm check procedure
Door open alarm check procedure . . .
Fan fail alarm check procedure . . . . .
Mains fail alarm check procedure . . .
Rectifier fail alarm check procedure . .
Low dc voltage alarm check procedure .
Inverter fail alarm check procedure . . .
MCB trip alarm check procedure . . . .
Battery fault alarm check procedure . .
Comms PSU fail alarm check procedure
External alarm 0 check procedure . . .
DRCU fault identification . . . . . . . . .
Symptoms during normal operation. . .
Symptoms during commissioning . . .
68P02901W43-P
23 Feb 2004
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-47
2-48
2-49
2-50
2-50
2-50
2-50
2-52
2-52
2-52
2-52
2-54
2-54
2-54
2-54
2-55
2-55
2-56
2-56
2-56
2-56
2-57
2-57
2-58
2-61
2-61
2-62
2-62
2-63
2-64
2-65
2-65
2-66
2-66
2-66
2-66
2-67
2-68
2-68
2-69
2-70
2-70
2-71
2-72
2-73
2-73
2-74
2-74
2-75
2-76
2-76
2-77
2-78
2-78
2-78
iii
GMR-01
Contents
Procedure during normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Procedure during commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-79
2-82
Chapter 3: M-Cell2 and M-Cell6 optimization

Introduction to M-Cell2 and M-Cell6 optimization. . . . . . .
CINDY commissioning tool . . . . . . . . . . . . . . .
Test equipment and leads . . . . . . . . . . . . . . . . . .
Test equipment required . . . . . . . . . . . . . . . . .
Test leads required . . . . . . . . . . . . . . . . . . .
TCU output power calibration and VSWR check . . . . . . .
Setting output transmit power methods . . . . . . . . . .
Test stages . . . . . . . . . . . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . . . . . . .
Preparation for output power calibration and VSWR check.
Automatic VSWR test procedure . . . . . . . . . . . . .
Manual VSWR test procedure . . . . . . . . . . . . . .
Tx output power calibration procedure . . . . . . . . . .
M-Cell6 with CCB cellsite power setting . . . . . . . . .
Cellsite power setting procedure . . . . . . . . . . . . .
Tuning CCB cavities . . . . . . . . . . . . . . . . . .
Site restoration . . . . . . . . . . . . . . . . . . . . .
RF output power check . . . . . . . . . . . . . . . . .
Returning the TCUs to call processing mode . . . . . . .
TCU900/1800/1900 bay level offset tables calibration . . . . .
Commands used . . . . . . . . . . . . . . . . . . . .
Locking radio, dummy load and TCU reset . . . . . . . .
Silencing PLL_LK alarm . . . . . . . . . . . . . . . .
Bay level setting procedure . . . . . . . . . . . . . . .
Branch1 RX1A bay level calibration procedure . . . . . .
Branch 1 RX2A bay level calibration procedure . . . . . .
Branch 1 RX3A bay level calibration procedure . . . . . .
Branch completion . . . . . . . . . . . . . . . . . . .
Branch 2 calibration . . . . . . . . . . . . . . . . . . .
Calibration check procedure . . . . . . . . . . . . . . .
Diagnostic check procedure . . . . . . . . . . . . . . .
Site restoration . . . . . . . . . . . . . . . . . . . . .
TCU-B VSWR and cellsite offset information . . . . . . . . .
Test stages . . . . . . . . . . . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . . . . . . .
Preparation for output power calibration and VSWR check.
TCU-B VSWR and cellsite power calibration . . . . . . . . .
Automatic forward output power test procedure . . . . . .
Automatic reverse power test procedure . . . . . . . . .
Manual forward output power test procedure . . . . . . .
Manual reverse power test procedure . . . . . . . . . . .
Output power calibration procedure . . . . . . . . . . .
TCU-B VSWR and cellsite power calibration for CCBs . . . .
Example of DIP switch setting . . . . . . . . . . . . . .
CCB control board details . . . . . . . . . . . . . . . .
Calibration procedures. . . . . . . . . . . . . . . . . .
CCB cavities tuning procedure . . . . . . . . . . . . . .
iv
GMR-01
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-2
3-2
3-3
3-3
3-4
3-7
3-7
3-8
3-8
3-9
3-10
3-11
3-12
3-14
3-15
3-16
3-18
3-19
3-20
3-21
3-22
3-22
3-23
3-24
3-25
3-26
3-27
3-34
3-35
3-36
3-36
3-36
3-39
3-40
3-41
3-41
3-42
3-43
3-44
3-46
3-46
3-47
3-48
3-49
3-50
3-52
3-52
3-53
3-53
3-54
68P02901W43-P
23 Feb 2004
Contents
VSWR calibration procedure. . . . . . . . . .

Cellsite power calibration . . . . . . . . . . .
Parking the CCB cavity . . . . . . . . . . . .
Calibration procedures for remaining cavities . .
Site restoration . . . . . . . . . . . . . . . .
Rf output power check. . . . . . . . . . . . .
Returning the TCU-Bs to call processing mode .
TCU-B bay level offset tables calibration . . . . . .
Test equipment required . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . .
Preparation for bay level calibration . . . . . .
Branch 1 RX1A bay level calibration procedure
Antenna identification diagrams . . . . . . . .
Branch 1 completion . . . . . . . . . . . . .
Branch 2 procedure . . . . . . . . . . . . . .
Calibration check procedure . . . . . . . . . .
Diagnostic check procedure . . . . . . . . . .
Site restoration . . . . . . . . . . . . . . . .
Database equipage check . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . .
Preparation for check procedure . . . . . . . .
Database equipage check procedure . . . . . .
E1/T1 link check . . . . . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . . .
Preparation for checking the E1/T1 link. . . . .
E1/T1 link test procedure . . . . . . . . . . .
PIX connections and alarms check . . . . . . . . .
Commands used . . . . . . . . . . . . . . .
Preparation for PIX connections and alarm tests .
PIX connections test procedure. . . . . . . . .
MCU (GCLK) calibration . . . . . . . . . . . . .
When to calibrate the GCLK . . . . . . . . . .
Preparation for GCLK calibration . . . . . . .
GCLK calibration procedure . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-55
3-56
3-57
3-58
3-58
3-58
3-59
3-60
3-60
3-61
3-62
3-65
3-67
3-69
3-69
3-70
3-71
3-71
3-73
3-74
3-76
3-76
3-76
3-77
3-77
3-79
3-79
3-79
3-80
3-80
3-82
3-82
3-82
3-83
3-83
3-84
3-84
3-85
3-85
3-86
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-2
4-2
4-3
4-3
4-5
4-5
4-6
4-7
4-7
4-8
4-8
Chapter 4: Preserve calibration

Preserve calibration data overview . . . . . . .
Display calibration offsets data. . . . . . .
Store calibration data . . . . . . . . . . .
Clear calibration data . . . . . . . . . . .
Calibration data exchange . . . . . . . . .
CINDY commissioning tool . . . . . . . .
Commands used. . . . . . . . . . . . . . . .
Preserve calibration procedures. . . . . . . . .
Activating the preserve calibration feature .
Replacing a transceiver using preserved data
Viewing the calibration data in CM database
68P02901W43-P
23 Feb 2004
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
GMR-01
Contents
Transceiver calibration. . . . . . . . .
Transceiver calibration procedure .
Calibration check procedure . . . .
Transceiver recalibration . . . . . . . .
Transceiver recalibration procedure.
Recalibration check procedure . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-10
4-10
4-11
4-13
4-13
4-14
Chapter 5: Microcellular systems optimization

Introduction to microcellular systems optimization.
Code download . . . . . . . . . . . . . . .
CINDY commissioning tool . . . . . . . . .
Test equipment and leads . . . . . . . . . . . .
Test equipment required . . . . . . . . . . .
Test leads. . . . . . . . . . . . . . . . . .
Code download from PCMCIA. . . . . . . . . .
Preparation for PCMCIA code download . . .
PCMCIA download procedure . . . . . . . .
Code download from BSC . . . . . . . . . . . .
BSC download procedure with example results
Site status check procedure. . . . . . . . . . . .
Battery check . . . . . . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . .
Battery test procedure . . . . . . . . . . . .
E1/T1 link check . . . . . . . . . . . . . . . .
Commands used . . . . . . . . . . . . . .
Preparation for checking the E1/T1 link. . . .
E1/T1 test procedure . . . . . . . . . . . .
Fitting chassis bottom cover . . . . . . . . .
MCU-m GCLK calibration. . . . . . . . . . . .
MCU-m calibration procedure . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-2
5-3
5-4
5-4
5-5
5-8
5-8
5-8
5-9
5-16
5-16
5-22
5-24
5-24
5-24
5-24
5-26
5-26
5-26
5-26
5-27
5-28
5-29
5-29
5-29
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-2
6-2
6-3
6-3
6-4
6-5
6-5
6-5
6-5
6-6
6-8
6-9
6-9
6-9
6-9
6-10
6-11
6-13
Chapter 6: Base site integration

Introduction to base site integration . . . . . . .
CINDY commissioning tool . . . . . . . .
Test equipment and leads . . . . . . . . . . .
Test equipment required . . . . . . . . . .
Test leads required . . . . . . . . . . . .
Base site integration using logging software . . .
Commands used . . . . . . . . . . . . .
Preparation for integration . . . . . . . . .
Obtaining channel/timeslot information . . .
Intra/inter-cell handover test procedure . . .
Base site integration without logging software . .
Commands used . . . . . . . . . . . . .
Preparation for integration . . . . . . . . .
Obtaining channel/timeslot information . . .
Intra/inter-cell handover test procedure . . .
Base site integration without an MSC connection
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
vi
GMR-01
68P02901W43-P
23 Feb 2004

Commands used . . . . . . . . . . .
Preparation for integration . . . . . . .
Obtaining channel/timeslot information .
Intra/inter-cell handover test procedure .
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-13
6-13
6-13
6-14
6-15
Chapter 7: Channel numbers and frequencies

Introduction to channels and frequencies . . . .
PGSM channel numbers and frequencies . . . .
Channels 1 to 124 . . . . . . . . . . . . .
Extended GSM channel numbers and frequencies
Channels 975 to 1023 and channel 0 . . . .
GSM850 channel numbers and frequencies . . .
Channels 128 to 251. . . . . . . . . . . .
DCS1800 channel numbers and frequencies . . .
Channels 512 to 885. . . . . . . . . . . .
PCS1900 channel numbers and frequencies . . .
Channels 512 to 810. . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-3
7-3
7-10
7-10
7-13
7-13
7-20
7-20
7-40
7-40
Network optimization tools . . . . . . . . . . .

Motorola Drive Test Tool (MDTT) . . . . . .
Cell Optimization Product (COP) . . . . . .
Call Trace Product for Windows NT (CTP-NT)
Intelligent Optimization Service (IOS) . . . .
Network optimization process . . . . . . . . . .
Worst ten cells method . . . . . . . . . . .
Stages in an optimization exercise . . . . . .
System drive test . . . . . . . . . . . . . . . .
Preparation for the drive test . . . . . . . . .
Optimizing for worst case interference . . . .
Drive test process . . . . . . . . . . . . . .
Data collection overview . . . . . . . . . .
Personnel requirements . . . . . . . . . . .
Data collection process . . . . . . . . . . .
FICS explained . . . . . . . . . . . . . . .
Classification of test calls . . . . . . . . . .
Drive test results analysis . . . . . . . . . . . .
Analysis of data. . . . . . . . . . . . . . .
High handover failure rates . . . . . . . . .
High set-up failure rates . . . . . . . . . . .
High dropped call rate . . . . . . . . . . . .
No audio calls . . . . . . . . . . . . . . .
Noisy calls . . . . . . . . . . . . . . . . .
Poor quality of service calls . . . . . . . . .
High blocking cells . . . . . . . . . . . . .
Audio call faults . . . . . . . . . . . . . .
Mean time between drops . . . . . . . . . .
Drive test report. . . . . . . . . . . . . . .
Effects of a recommendation implemented . .
Residual defect investigation. . . . . . . . .
DSP test . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-2
8-2
8-2
8-3
8-4
8-5
8-5
8-5
8-7
8-7
8-10
8-11
8-11
8-12
8-12
8-12
8-12
8-13
8-15
8-15
8-16
8-17
8-18
8-20
8-20
8-20
8-21
8-23
8-23
8-23
8-24
8-24
8-25
8-25
Chapter 8: Network optimization
68P02901W43-P
23 Feb 2004
vii
GMR-01
Contents
Commands used . . . . . . .
Preparation for testing the DSP.
DSP test procedure . . . . . .
Site restoration . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-25
8-26
8-26
8-27
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-2
9-3
9-3
9-4
9-4
9-6
9-13
9-20
9-27
9-40
9-53
9-54
9-54
9-55
9-56
9-56
9-57
9-59
9-61
9-62
9-63
9-64
Chapter 9: Optimization results forms

BTS optimization results forms. . . . . . .
Personnel details . . . . . . . . . . .
DC power supply tests. . . . . . . . .
Antenna reflected power tests . . . . .
PIX tests . . . . . . . . . . . . . . .
DRCU tests . . . . . . . . . . . . . .
CTU850 tests . . . . . . . . . . . . .
SCU/TCU900/ TCU-B/CTU900 tests. .
SCU/TCU1800/ CTU1800 tests . . . .
TCU1900/ CTU1900 tests . . . . . . .
Loopback and RTC checks . . . . . .
BSC/RXCDR optimization results forms . .
BSC/RXCDR optimization results forms
Personnel details . . . . . . . . . . .
DC power supply tests. . . . . . . . .
PIX tests . . . . . . . . . . . . . . .
E1/T1 loopback (BSC) . . . . . . . .
E1/T1 loopback (RXCDR). . . . . . .
Site documentation check . . . . . . .
Drive test optimization forms . . . . . . .
Tick Sheet Proforma. . . . . . . . . .
Recommendation Proforma . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
viii
GMR-01
68P02901W43-P
23 Feb 2004
List
of
Figures
List of Figures
Figure 2-1:
Figure 2-2:
Figure 3-1:
Figure 3-2:
Figure 3-3:
Figure 3-4:
Figure 3-5:
Figure 3-6:
Figure 3-7:
Figure 3-8:
Figure 5-1:
Figure 5-2:
BTS 9-way to 9-way PCU to DCB/CEB, MCU, RTC and transceiver cable connections.
BTS 9-way to 25-way PC to GPROC cable connections . . . . . . . . . . . . . . .
M-Cell 9-way to 9-way PC to TCU/MCU hardware optimization cable connections . .
M-Cell 9-way to 25-way PC to TCU-B EQCP/RSS cable connections . . . . . . . . .
M-Cell 3-way to BNC MCU calibration cable connections . . . . . . . . . . . . . .
Single M-Cell6 cabinet 2/2/2 configuration . . . . . . . . . . . . . . . . . . . . .
Two M-Cell6 cabinets 4/4/4 configuration . . . . . . . . . . . . . . . . . . . . . .
Single M-Cell6 cabinet 2/2/2 configuration . . . . . . . . . . . . . . . . . . . . .
Two M-Cell6 cabinets 4/4/4 configuration . . . . . . . . . . . . . . . . . . . . . .
M-Cell GCLK calibration cable connections . . . . . . . . . . . . . . . . . . . . .
M-Cellcity 9-way to 37-way TTY cable connections . . . . . . . . . . . . . . . . .
M-Cellcity 9-way to 9-way MCU cable connections . . . . . . . . . . . . . . . . .
68P02901W43-P
23 Feb 2004
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-6
2-6
3-5
3-5
3-6
3-32
3-33
3-67
3-68
3-86
5-6
5-7
ix
GMR-01
List of Figures
This page intentionally left blank.
GMR-01
68P02901W43-P
23 Feb 2004
List
of
Tables
List of Tables
Table 1: Manual version history . . . . . . . . . . . . . . . . . .

Table 2: Service requests resolved in this manual . . . . . . . . . .
Table 2-1: Hardware optimization equipment . . . . . . . . . . . .
Table 2-2: Test plug A pin connections . . . . . . . . . . . . . . .
Table 2-3: Test plug B pin connections . . . . . . . . . . . . . . .
Table 2-4: Test plug C pin connections . . . . . . . . . . . . . . .
Table 2-5: -48/60 V BTS cabinet circuit breakers . . . . . . . . . .
Table 2-6: +27 V BTS cabinet circuit breakers . . . . . . . . . . .
Table 2-7: -48/60 V BSSC/RXCDR cabinet circuit breakers . . . . .
Table 2-8: +27 V BSSC/RXCDR cabinet circuit breakers . . . . . .
Table 2-9: Channel frequency listing . . . . . . . . . . . . . . . .
Table 2-10: Branch 1 offset table locations . . . . . . . . . . . . .
Table 2-11: Branch 2 offset table locations . . . . . . . . . . . . .
Table 2-12: GSM900 test frequencies . . . . . . . . . . . . . . . .
Table 2-13: DCS1800 test frequencies . . . . . . . . . . . . . . .
Table 2-14: SCU900 frequency offset addresses . . . . . . . . . . .
Table 2-15: DCS1800 frequency offset addresses . . . . . . . . . .
Table 3-2: Test plug pin connections . . . . . . . . . . . . . . . .
Table 3-3: TCU achievable TX RF power output . . . . . . . . . .
Table 3-4: TCU switch settings for example of value 75 . . . . . . .
Table 3-5: TCU cavity bitmap . . . . . . . . . . . . . . . . . . .
Table 3-6: Signal generator to TCU connection . . . . . . . . . . .
Table 3-7: GSM900 and EGSM900 test frequencies . . . . . . . . .
Table 3-8: DCS1800 test frequencies . . . . . . . . . . . . . . . .
Table 3-9: PCS1900 test frequencies . . . . . . . . . . . . . . . .
Table 3-10: GSM900 frequency offset addresses. . . . . . . . . . .
Table 3-11: EGSM900 frequency offset addresses . . . . . . . . . .
Table 3-12: DCS1800 frequency offset addresses . . . . . . . . . .
Table 3-13: PCS1900 frequency offset addresses . . . . . . . . . .
Table 3-14: TCU-B achievable Tx RF power output . . . . . . . . .
Table 3-15: TCU-B CCB switch settings for example of 75 . . . . .
Table 3-16: TCU-B CCB cavity tuning commands. . . . . . . . . .
Table 3-17: TCU-B CCB achievable Tx RF power output . . . . . .
Table 3-18: TCU-B CCB cavity parking commands . . . . . . . . .
Table 3-19: EGSM900 test frequency table . . . . . . . . . . . . .
Table 3-20: TCU-B frequency offset addresses . . . . . . . . . . .
Table 4-1: Explanation of offset calibration data presentation per row .
Table 5-2: 9-way to 37-way cable connections. . . . . . . . . . . .
Table 5-3: 9-way to 9-way cable connections . . . . . . . . . . . .
Table 6-1: Base site integration equipment . . . . . . . . . . . . .
68P02901W43-P
23 Feb 2004
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
3
2-4
2-7
2-7
2-8
2-11
2-12
2-12
2-13
2-28
2-30
2-31
2-42
2-43
2-47
2-48
3-3
3-6
3-15
3-16
3-18
3-29
3-29
3-30
3-31
3-37
3-38
3-38
3-38
3-51
3-52
3-55
3-57
3-57
3-66
3-72
4-9
5-4
5-6
5-7
6-3
xi
GMR-01
List of Tables
Table 7-1: PGSM channels 1 to 10 . . . .

Table 7-2: PGSM channels 11 to 20 . . .
Table 7-10: PGSM channels 91 to 100 . .
Table 7-14: EGSM channels 975 to 984. .
Table 7-15: EGSM channels 985 to 994. .
Table 7-16: EGSM channels 995 to 1004 .
Table 7-17: EGSM channels 1005 to 1014
Table 7-18: EGSM channels 1015 to 0 . .
Table 7-19: GSM850 channels 128 to 130.
Table 7-32: DCS 1800 channels 512 to 520
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xii
GMR-01
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-3
7-4
7-4
7-5
7-5
7-6
7-6
7-7
7-7
7-8
7-8
7-9
7-9
7-10
7-11
7-11
7-12
7-12
7-13
7-13
7-14
7-14
7-15
7-15
7-16
7-16
7-17
7-17
7-18
7-18
7-19
7-20
7-21
7-21
7-22
7-22
7-23
7-23
7-24
7-24
7-25
7-25
7-26
7-26
7-27
7-27
7-28
7-28
7-29
7-29
7-30
7-30
7-31
7-31
7-32
68P02901W43-P
23 Feb 2004
List of Tables
Table 7-56: DCS 1800 channels 751 to 760 . . . . . . .

Table 7-70: PCS 1900 channels 512 to 520 . . . . . . .
Table 8-1: Equipment required for drive testing . . . . .
Table 8-2: Equipment required for systems analysis . . .
Table 8-3: Equipment required for problem investigation.
68P02901W43-P
23 Feb 2004
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-32
7-33
7-33
7-34
7-34
7-35
7-35
7-36
7-36
7-37
7-37
7-38
7-38
7-39
7-40
7-41
7-41
7-42
7-42
7-43
7-43
7-44
7-44
7-45
7-45
7-46
7-46
7-47
7-47
7-48
7-48
7-49
7-49
7-50
7-50
7-51
7-51
7-52
7-52
7-53
7-53
7-54
7-54
7-55
8-10
8-10
8-11
xiii
GMR-01
List of Tables
xiv
GMR-01
68P02901W43-P
23 Feb 2004
About
This
Manual
Installation & Configuration: BSS

Optimization
What is Covered In This Manual?

This manual contains optimization, configuration and integration information to support the following
Motorola BSS equipment: BTS4, BTS5, BTS6, BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-Cell2,
M-Cell6, M-Cellcity, Horizonmicro, Horizoncompact, Horizonmicro2, and Horizoncompact2.
The transceivers used in Motorola BSS equipment can be used in either PGSM, EGSM, GSM850, DCS1800,
or PCS1900 frequency bands. The frequency band used depends on equipment capability.
The optimization information for Horizonmacro equipment which previously was in this
manual, can now be found in the relevant service manuals
68P02901W43-P
23 Feb 2004
GMR-01
Issue status of this manual
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue:
Table 1
Manual version history
Manual
issue
Remarks
Date of issue
3 Oct 19 94
Original issue - Software release 1.2.2.x
30 Dec 1994
Issue A - Software release 1.2.3.x
01 Sep 1995
Issue B - Software release 1.3.0.x
31 May 1996
Issue C - Software release 1.4.0.x
28 Mar 1997
Issue D - Software release 1.4.1.x
29 Aug 1997
Issue E - GSM Software Release 2
27 Apr 1998
Issue F - GSM Software Release 3
12 Mar 1999
Issue G - GSM Software Release 4
14 Jul 2000
Issue H - GSM Software Release 4.1
31 Jul 2001
Issue J - GSM Software Release 5
31 May 2002
Issue K - GSM Software Release 5.1
30 Nov 2002
Issue L - GSM Software Release 6
02 May 2003
Issue M - GSM Software Release 6 (Horizon II)
13 Nov 2003
Issue P - GSM Software Release 7
GMR-01
68P02901W43-P
23 Feb 2004
Resolution of Service Requests

The following Service Requests are now resolved in this manual:
Table 2
Service requests resolved in this manual
Service
Request
GMR
Number
SR1050489
N/A
Remarks
Replaced SNDCMD command with SEND EQCP command
in Chapter 3.
Version updates
The GPROC3 feature has been incorporated in GSR7 version of this manual. This feature affects the generic
form GPROC; wherever used in this manual it denotes GPROC, GPROC2 and GPROC3 processor boards.
68P02901W43-P
23 Feb 2004
GMR-01
General information
General information
Motorola disclaims all liability whatsoever, implied or express, for any risk of damage,
loss or reduction in system performance arising directly or indirectly out of the failure
of the customer, or any one acting on the customers behalf, to abide by the instructions,
system parameters or recommendations made in this manual
If this manual was obtained when attending a Motorola training course, it will not be updated
or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied
under normal operational circumstances, to support a major software release, then corrections
will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation,
installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is
recommended that all personnel engaged in such activities be properly trained by Motorola.
Failure to comply with Motorolas operation, installation and maintenance

instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although
they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features
released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In
these manuals, new and amended features are tagged to help users to assess the impact on installed
networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and
Development Prioritization (RDP) numbers. The tags include index references which are listed in the
manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP
numbers for the released features, with page references and hot links in electronic copy.
GMR-01
68P02901W43-P
23 Feb 2004
General information
The tags have the format: {nnnn} or {nnnnn}

Where:
is:
{nnnn}
the RDB number
{nnnnn}
the RDP number
The tags are positioned in text as follows:

New and amended feature information
Tag position in text
New sentence/s or new or amended text.
Immediately before the affected text.
Complete new blocks of text as follows:
Immediately after the headings as follows:
Full sections under a main heading
Main heading
Full paragraphs under subheadings
Subheading
New or amended complete Figures and Tables
After the Figure or Table number and before

the title text.
Warning, Caution and Note boxes.
Immediately before the affected text in the box.
General command syntax, operator input or

displays (in special fonts).
On a separate line immediately above the

affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this
software release, refer to the manualSystem Information: GSM Overview (68P02901W01), or to
the manual System Information: GPRS Overview (68P02903W01).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and
section names. The references to external publications are shown in italics, chapter and
section name cross references are emphasised blue in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of
each page, and are listed in the table of contents.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and
GPRS network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels as individually standardised, or may not be present
at all in some parts of the network in which it is normally implemented. The manual set, of which
this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual
countries, limitations on the encryption included in the particular software being delivered, are covered
in the Release Notes that accompany the individual software release.
68P02901W43-P
23 Feb 2004
GMR-01
General information
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent
keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c
Press the Control and c keys at the same time.
ALT-f
Press the Alt and f keys at the same time.
Press the pipe symbol key.
CR or RETURN
Press the Return key.
GMR-01
68P02901W43-P
23 Feb 2004
Reporting safety issues
Reporting safety issues
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure
that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
Procedure 1
68P02901W43-P
23 Feb 2004
Safety issue reporting
Make the equipment concerned safe, for example by removing power.
Make no further attempt to adjust or rectify the equipment.
Report the problem directly to the Customer Network Resolution Centre, Swindon +44
(0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written
report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax).
Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.
GMR-01
Warnings and cautions
The following describes how warnings and cautions are used in this manual and in
all manuals of this Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical
injury, or ill health. This includes hazards introduced during maintenance, for example, the use of
adhesives and solvents, as well as those inherent in the equipment.
Example and format
Do not look directly into fibre optic cables or data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these warnings, or with specific
warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety
standards of design, manufacture and intended use of the equipment. Motorola assumes no
liability for the customers failure to comply with these requirements.
Cautions
A definition and example follow below:
GMR-01
68P02901W43-P
23 Feb 2004
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.
Example and format
Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.
68P02901W43-P
23 Feb 2004
GMR-01
General warnings
General warnings
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
Potentially hazardous voltage.
Electric shock.
RF radiation.
Laser radiation.
Heavy equipment.
Parts substitution.
Battery supplies.
Lithium batteries,
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals,
violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes
no liability for the customers failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working
with or operating Motorola equipment must comply with any warning labels fitted to the equipment.
Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be
incorporated into procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must
any other warnings given in text, in the illustrations and on the equipment.
10
GMR-01
68P02901W43-P
23 Feb 2004
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single
phase or 415 V a.c. three phase supply. To achieve isolation of the equipment
from the a.c. supply, the a.c. input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989
(UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
Do not touch the victim with your bare hands until the electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating material
and pull or push the victim clear of the conductor.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even
death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart,
to stop. It can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS
send for trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool,
until trained first aid or medical assistance arrives.
RF radiation
High RF potentials and electromagnetic fields are present in this equipment

when in operation. Ensure that all transmitters are switched off when
any antenna connections have to be changed. Do not key transmitters
connected to unterminated cavities or feeders.
68P02901W43-P
23 Feb 2004
11
GMR-01
General warnings
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz
CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields

High Frequency (10 kHz to 300 GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors.
Laser radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a

competent responsible person must ensure that adequate lifting facilities are
available. Where provided, lifting frames must be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible
person must ensure that adequate lifting facilities are available. Where provided, lifting frames
must be used for these operations. When equipment has to be manhandled, reference must be
made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling
of loads legislation for the country in which the equipment is used.
Parts substitution
Do not install substitute parts or perform any unauthorized modification of

equipment, because of the danger of introducing additional hazards. Contact
Motorola if in doubt to ensure that safety features are maintained.
12
GMR-01
68P02901W43-P
23 Feb 2004
General warnings
Battery supplies
Do not wear earth straps when working with stand-by battery

supplies. Use only insulated tools.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

lithium batteries must not be removed or replaced. Any boards containing
defective lithium batteries must be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.
68P02901W43-P
23 Feb 2004
13
GMR-01
General cautions
General cautions
Observe the following cautions during operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these cautions or with specific cautions
elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no
liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to
the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual.
These must be observed by all personnel at all times when working with the equipment, as must
any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor

(MOS) devices are susceptible to damage from electrostatic charge. See the section
Devices sensitive to static in the preface of this manual for further information.
14
GMR-01
68P02901W43-P
23 Feb 2004
Devices sensitive to static
Devices sensitive to static
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied to
the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high
insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads short circuited together,
for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic
foam. Provided the leads are short circuited it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
Always wear an earth strap which must be connected to the electrostatic

point (ESP) on the equipment.
Leave the short circuit on the leads until the last moment. It may be necessary to replace
the conductive foam by a piece of wire to enable the device to be fitted.
Do not wear outer clothing made of nylon or similar man made material.
A cotton overall is preferable.
If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic
work surfaces with an anti-static cloth before starting the operation.
All metal tools should be used and when not in use they should be placed on an earthed surface.
Take care when removing components connected to electrostatic sensitive devices.

These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to
electrostatic damage. However PCBs should be handled with care, preferably by their edges and
not by their tracks and pins, they should be transferred directly from their packing to the equipment
(or the other way around) and never left exposed on the workbench.
68P02901W43-P
23 Feb 2004
15
GMR-01
Motorola manual set
Motorola manual set
The Motorola manual sets provide the information needed to operate, install and maintain the Motorola
equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:
Printed hard copy.
Electronic, as fully navigable PDF files on:

The Motorola customer support web site at:
(https://mynetworksupport.motorola.com/index.asp).
CD-ROM produced in support of a major system software release.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software
release, together with current versions of appropriate hardware manuals, and has additional
navigation facilities. A snapshot copy of on-line documentation is also included, though it
will not be updated in line with subsequent point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist
products such as MARS or COP.
Ordering manuals and CD-ROMs

Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs.
All orders must be placed with your Motorola Local Office or Representative.
16
GMR-01
68P02901W43-P
23 Feb 2004
GMR amendment
GMR amendment
Changes to a manual that occur after the printing date are incorporated into the manual using
General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when
required. A GMR has the same identity as the target manual. Each GMR is identified by a
number in a sequence that starts at 01 for each manual at each issue.
GMR availability
GMRs are published as follows:
Printed hard copy - Complete replacement content or loose leaf pages with amendment list.
Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
Motorola service web - Updated at the same time as hard copies.
CD-ROM - Updated periodically as required.
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to
record the GMR. Retain the instruction sheet that accompanies each GMR and insert it in
a suitable place in this manual for future reference.
68P02901W43-P
23 Feb 2004
17
GMR-01
GMR amendment
GMR amendment record

Record the insertion of GMRs in this manual in the following table:
GMR number
01
Incorporated by (signature)
Incorporated (this GMR)
Date
23 Feb 2004
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
18
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
1
Introduction to BSS optimization
This chapter provides a guide to using this manual for the purposes of optimizing the Base Station
System (BSS) at installation and commissioning of BSS equipment.
This chapter:
68P02901W43-P
23 Feb 2004
Informs of the purpose of the manual.
Defines the audience for whom this manual is intended
Lists the prerequisites for using the manual.
Explains the purpose of each manual chapter.
Indicates related documentation.
States the range of equipment supported.
1-1
GMR-01
Using this manual
Using this manual
Use this manual at the BSS to:
Optimize and integrate BSS and BTS sites during commissioning.
Calibrate the transceiver transmit power and check VSWR.
Calibrate transceiver bay level offsets.
Check other communications and calibrations relevant to each system.
Audience
This manual is for technicians who work at BSS sites to install, configure and optimize the BSS cabinets.
Prerequisites
This manual assumes the reader:
Is familiar with Motorola BSS hardware and software.
Knows how to operate a local maintenance terminal (LMT).
Understands how the BSS and BTS systems work.
Structure
The manual contains the following chapters:
Chapter 1:
This introductory chapter providing a guide to the use of this manual.
Chapter 2:
Optimization procedures for pre M-Cell systems.
Chapter 3:
Optimization procedures for M-Cell2 and M-Cell6.
Chapter 4:
Preserve calibration procedures for all systems in previous chapters.
Chapter 5:
Optimization procedures for microcellular systems.
Chapter 6:
Integration procedures for all systems.
Chapter 7:
Channel numbers and frequencies associated with all systems.
Chapter 8:
Optimization procedures for drive testing a network.
Chapter 9:
Optimization results forms used for those systems that have manual calibration.
1-2
GMR-01
68P02901W43-P
23 Feb 2004
Using this manual
Test equipment
Test equipment required and commands used are listed in each chapter containing procedures.
Related documentation
Refer to the appropriate equipment related service manuals.
Equipment supported
This manual supports the following Motorola BSS equipment:
BTS4, BTS5, BTS6, BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-Cell2, M-Cell6, M-Cellcity,
Horizonmicro, Horizoncompact, Horizonmicro2 and Horizoncompact2.
The optimization information for Horizonmacro equipment is found in the relevant service manuals:
Service Manual: Horizonmacro Indoor (68P02902W06), Service Manual: Horizonmacro Outdoor
(68P02902W12) and Service Manual: Horizonmacro 12 Carrier Outdoor (68P02902W66).
The transceivers use, depending on capability, PGSM, EGSM, GSM850, DCS1800 and PCS1900 frequencies.
Throughout this manual, the generic term GPROC is used to denote the GPROC,
GPROC2 and {4354} GPROC3 processor boards.
68P02901W43-P
23 Feb 2004
1-3
GMR-01
Using this manual
1-4
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
2
InCell, ExCell and TopCell optimization
Hazardous voltages in excess of 50 V dc exist inside -48 V/-60 V cabinets.

Use extreme caution when working on a cabinet with power applied.
Remove all rings, watches and other jewellery.
This chapter provides information required to optimize and configure Motorola BTS4, BTS5,
BTS6, ExCell, TopCell and BSC cabinets. For information about equipment not supplied by
Motorola, for example battery chargers, power supplies and antennas, refer to the site specific
documentation and the vendor instructions provided with the equipment.
Hardware optimization of the InCell, ExCell and TopCell equipment consists of :
Checking the dc power supply.
Manually tuning the RTC
Checking the antenna VSWR and calibrating the transmit output power.
Calibrating the bay level offset tables.
Checking the database equipage.
Checking the 2.048 Mbit link.
Checking the PIX connections and alarm status.
Integrating transcoders.
Calibrating the GCLK.
Checking ExCell alarms
In this chapter DRCU is used to mean DRCU, DRCUII, DRCU3, SCU900 or SCU1800.
All procedures are the same for each unless otherwise indicated.
68P02901W43-P
23 Feb 2004
2-1
GMR-01
Introduction to InCell, ExCell and TopCell optimization
Introduction to InCell, ExCell and TopCell

optimization
The following procedures are used for InCell, ExCell and TopCell optimization:
"DC power supply test" on page 2-9
"RTC manual tuning" on page 2-14
"DRCU, DRCUII and DRCU3 Tx power calibration and VSWR check" on page 2-16
"DRCU, DRCUII and DRCU3 bay level offset tables calibration" on page 2-23
"SCU Tx power calibration and VSWR check" on page 2-32
"SCU900/1800 bay level offset tables calibration" on page 2-39
"Database check for devices and functions" on page 2-50
"E1/T1 link check" on page 2-52
"PIX connections check" on page 2-54
"Transcoder integration" on page 2-56
"GCLK calibration" on page 2-61
"ExCell alarms check" on page 2-66
"DRCU fault identification" on page 2-78
Code download
The system software is downloaded from the OMC-R at initial loading or when new system software is
distributed to the system. If a new load is required at a site, request a download from the OMC-R to that site.
If the existing software detects a corrupted segment in the current load, it automatically
requests a download from the OMC-R.
2-2
GMR-01
68P02901W43-P
23 Feb 2004
Introduction to InCell, ExCell and TopCell optimization
CINDY commissioning tool

Many of the optimization procedures described in this chapter can be carried out automatically using the
CINDY commissioning tool. Refer to the relevant CINDY user documentation for details.
68P02901W43-P
23 Feb 2004
2-3
GMR-01
Test equipment, leads and plugs
This section provides information on the test equipment required for the hardware
optimization procedures in this chapter.
Ensure that all test equipment associated with commissioning of Motorola

cellular base stations is within calibration date.
Allow test equipment to warm up for 30 minutes before use.
Test equipment required

Table 2-1 lists the equipment required for system optimization.
Table 2-1 Hardware optimization equipment
Quantity
Description
Comments
IBM-compatible personal computer

(PC)
Requires PCMCIA type 2 slot and serial

comms port
Commercial terminal emulator

software
PC PLUS or similar software
RTC control program
Rubidium clock standard
1 or 10 MHz output frequency. Minimum

accuracy 1x10-10
Frequency counter
1.25 ppb or better reference, 10-digit

display. Hewlett Packard model HP5385A
or equivalent
Signal generator
Range 0 to 2 GHz
RF wattmeter with 5 W, 10 W,
25 W and 50 W elements
Bird model 43 or equivalent
Digital multimeter
Hewlett Packard E2378A or equivalent
50 ohm RF dummy load
50 W minimum
2-4
GMR-01
68P02901W43-P
23 Feb 2004
Table 2-1 Hardware optimization equipment (Continued)

Description
Quantity
Comments
30 dB attenuator
100 W minimum
RF adaptor kit
RTLXQ98088 or equivalent
N to 7/16 inch adaptor
N to N barrel adaptor
N to N male coaxial cable
2 m, calibrated
4 m, calibrated
BNC to 2 mm multicontact AG
connector screened coaxial cable
Frequency counter to GCLK
9-way to 9-way hardware optimization

cable
PC to DCB/CEB, DRCU, MCU, RTC or

TCU. See Figure 2-1.
9-way to 25-way GPROC cable
PC to GPROC. See Figure 2-2.
Type 43 loopback cables
0.23 m
BIB loopback plug
1 each
Test plugs A, B and C
Non-ferrous tuning tool
Krone tool and pegs
Test mobile
ESD protection kit
Approved smoke canister
GSM MS with registered SIM card
GCLK calibration stickers
Test leads required

Test lead calibration
To minimize variations in test results, ensure that all appropriate test leads used in
hardware optimization procedures are calibrated.
A recognized laboratory must calibrate all

test equipment and associated test leads annually.
Do not calibrate test equipment or test leads in the field.
68P02901W43-P
23 Feb 2004
2-5
GMR-01
9-way to 9-way hardware optimization cable

Figure 2-1
BTS 9-way to 9-way PCU to DCB/CEB, MCU, RTC and transceiver cable connections
PIN NUMBER
PIN NUMBER
6
7
8
4 m LONG SCREENED CABLE
TO PC COMMUNICATIONS PORT
9-WAY D-TYPE F
TO DESTINATION PORT CONNECTOR

9-WAY D-TYPE M
9-way to 25-way GPROC cable

Figure 2-2 BTS 9-way to 25-way PC to GPROC cable connections
PIN NUMBER
PIN NUMBER
20
22
25-WAY D-TYPE M
9-WAY D-TYPE F
2-6
GMR-01
68P02901W43-P
23 Feb 2004
Test plugs required

Test plug A
Table 2-2 lists the pin connections for test plug A.
Table 2-2 Test plug A pin connections
From pin
To pin
Connection
Connect with a 1 kohm resistor
10
11
44
45
47
48
50
51
53
54
Test plug B
Table 2-3 lists the pin connections for test plug B.
Table 2-3 Test plug B pin connections
68P02901W43-P
23 Feb 2004
From pin
To pin
10
11
44
45
47
48
50
51
53
54
Connection
2-7
GMR-01
Test plug C
Table 2-4 lists the pin connections for test plug C.
Table 2-4
Test plug C pin connections
From pin
To pin
Connect with a wire link
10
11
44
45
47
48
50
51
53
54
2-8
GMR-01
Connection
68P02901W43-P
23 Feb 2004
DC power supply test
The person carrying out these tests must be accompanied by a second

person acting in a safety capacity.
The objective of the dc power supply tests is to verify that the main dc supply and
power supply modules are operating.
In this section, the term PSM is used to indicate a DPSM, EPSM, or IPSM as appropriate.

No special test equipment is required to carry out the dc power supply tests.
Commands used
No special software commands are required for the dc power supply tests.
Preparation for the dc power supply test

Use the following procedure to prepare for the dc power supply test:
Procedure 2-1
68P02901W43-P
23 Feb 2004
Prepare for dc power supply test
Ensure that none of the full size modules, half size modules or PSMs are seated
in their backplane connectors.
Set all cabinet power supply circuit breakers to the OFF position.
2-9
GMR-01
Procedure 2-1
Prepare for dc power supply test (Continued)
For positive earth BTS4 cabinets go to step 4.

For all other BTS cabinets and BSSC cabinets go to DC power supply test
procedure step 1.
Firmly seat all power converters (up to four depending upon the cabinet
configuration).
DC power supply test procedure

Use the following procedure to test the dc power supply:
Procedure 2-2
Test dc power supply
Apply power to the cabinet.
Set the circuit breakers for the following cabinets to ON:
Positive earth BTS4 cabinets - CB5 and CB6
Positive earth BSSC cabinets - CB4 and CB5
Negative earth BTS6 and BSSC2 cabinets - CB1
Positive earth BTS6 and BSSC2 cabinets - CB1 and go to step 4.
Check that the cabinet fans are operating.

If the fans are not operating:
1. Check that dc power is connected to the cabinet (if not, suspect the dc power
supply, the power cabling and the cabinet power input connections).
2. Check the fan fuses and the dc power cabling to the fans, and to the power
converters (positive earth BTS4) or fan power converters (positive earth
BSSC).
3. Verify correct power converter (positive earth BTS4) or fan power converter
(positive earth BSSC) operation by substituting known good units.
Firmly seat all PSMs in their backplane connectors.
Set the circuit breaker to ON for each PSM.

Check that the green LED active indicator for the chosen PSM lights.
With exception to the cabinets detailed in step 6 below. The fans

must be operating before PSMs or DRCUs can be switched on.
2-10
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-2 Test dc power supply (Continued)

Positive earth BTS6 and BSSC2 cabinets only, check that the cabinet fans are
operating.
If the fans are not operating:
1. Check that dc power is connected to the cabinet (if not, suspect the dc power
supply, the power cabling or the cabinet input power connections).
2. Check the fan fuses and the dc power cabling to the fans.
7
Set the circuit breaker for each DRCU to ON.
Site restoration
Use the following procedure to restore the site when dc power supply testing is complete:
Procedure 2-3 Restore site after dc power supply testing
1
Insert all processor cards into their backplane connectors.
Insert all other modules into their backplane connectors.
Circuit breaker tables

Table 2-5 to Table 2-8 list the cabinet circuit breaker assignments.
-48/60 V BTS cabinets

Table 2-5
-48/60 V BTS cabinet circuit breakers

BTS4
68P02901W43-P
23 Feb 2004
BTS6
CB
Protects
CB
Protects
11
PSM2
11
Not fitted
10
PSM1
10
IPSM2
PSM0
IPSM1
PC4
IPSM0
PC3
DRCU5
PC2
DRCU4
PC1
DRCU3
DRCU3
DRCU2
DRCU2
DRCU1
2-11
GMR-01
Table 2-5 -48/60 V BTS cabinet circuit breakers (Continued)

BTS4
BTS6
DRCU1
DRCU0
DRCU0
DAB
+27 V BTS cabinets

Table 2-6 +27 V BTS cabinet circuit breakers
BTS4/BTS5
BTS6
CB
Protects
CB
Protects
11
PSM2
11
Not fitted
10
PSM1
10
EPSM2
PSM0
EPSM1
Not used
EPSM0
Not used
DRCU5
Not used
DRCU4
DRCU4
DRCU3
DRCU3
DRCU2
DRCU2
DRCU1
DRCU1
DRCU0
DRCU0
DAB
-48/60 V BSSC/RXCDR cabinets

Table 2-7
-48/60 V BSSC/RXCDR cabinet circuit breakers

BSSC
BSSC2
CB
Protects
CB
Protects
11
PSM2L
11
Not fitted
10
PSM1L
10
IPSM2L
PSM0L
IPSM1L
PSM2U
IPSM0L
PSM1U
IPSM2U
PSM0U
IPSM1U
FPC2
IPSM0U
FPC1
Not used
Not used
Not used
2-12
GMR-01
68P02901W43-P
23 Feb 2004
Table 2-7
-48/60 V BSSC/RXCDR cabinet circuit breakers (Continued)

BSSC
BSSC2
Not used
Not used
Not used
DAB
+27 V BSSC/RXCDR cabinets

Table 2-8 +27 V BSSC/RXCDR cabinet circuit breakers
BSSC
68P02901W43-P
23 Feb 2004
BSSC2
CB
Protects
CB
Protects
11
PSM2L
11
Not fitted
10
PSM1L
10
EPSM2L
PSM0L
EPSM1L
PSM2U
EPSM0L
PSM1U
EPSM2U
PSM0U
EPSM1U
Not used
EPSM0U
Not used
Not used
Not used
Not used
Not used
Not used
Not used
DAB
2-13
GMR-01
RTC manual tuning
RTC manual tuning
Follow this procedure to tune a remotely tuneable combiner (RTC) to a required frequency.
This procedure is not applicable to DCS1800 or PCS1900 systems.

The following test equipment is required to carry out this procedure:
IBM-compatible personal computer (PC).
Terminal emulator software.
RTC control program.
9-way to 9-way hardware optimization cable.
Commands used
No special software commands are required for this procedure.
Preparation for manually tuning the RTC

Use the following procedure to prepare for manual tuning of the RTC:
Procedure 2-4 Prepare for RTC manual tuning
1
Ensure that the RTC jumpers are in the correct position for manual operation.
Only one link must be fitted, remove the redundant link.
Connect the 9-way to 9-way cable from the serial A port on the PC to the RS232
port on the RTC (behind the top left side of the RTC).
2-14
GMR-01
68P02901W43-P
23 Feb 2004
RTC manual tuning
RTC manual tuning procedure

Use the following procedure to manually tune the RTC:
Procedure 2-5 Manually tune the RTC
1
Start the RTC tuning program using the following command at the PC:
COM00_02
Press Enter eleven times.
The following message is displayed:
Press a highlighted letter of an option or parameter.
Select the manual mode of communication with the RTC, enter:

V
Press Enter four times.
Press a highlighted letter of an option or parameter.
Select address, enter:

A
Enter the required address:
255
or the address determined by the jumpers and then press Enter.
Select cavity, enter:

Y
Follow the instructions displayed at the bottom of the screen and then press
Enter.
Select channel, enter:

C
Follow the instructions displayed at the bottom of the screen and select the cavity
to be tuned.
Select download, enter:

D
Repeat step 5 and step 6 for each cavity that is to be tuned.
Quit the RTC tuning program, enter:

Q
To restore the site return the RTC jumpers to the auto position.
68P02901W43-P
23 Feb 2004
2-15
GMR-01
DRCU, DRCUII and DRCU3 Tx power calibration and

VSWR check
DRCU Tx power calibration and VSWR checks can be carried out automatically using the
This procedure is used to set the predefined maximum transmitter output power at the top of the cabinet,
and to ensure that antenna feeders and connectors are properly terminated.
The objective of the VSWR check and output power calibration procedure is to ensure that
antenna feeders and connectors are properly terminated and then set the pre-defined maximum
transmitter output power at the top of the cabinet.
When a radio is manufactured, it undergoes comprehensive transmit and receive calibration procedures.
These procedures aim to produce a radio that exhibits a flat frequency response over the full PGSM
band. In the case of the transmitter, this is performed by sharing out the 124 channels over eight detector
groups (the detector being the device that maintains a steady output power level).
In the field, the procedure for setting the transmit output power involves using a set of commands
called cellsite power (CSPWR). During CSPWR the cabinet output power can be trimmed to
account for any abnormalities that may occur between the DRCU and the top of the cabinet.
The offset is effectively subtracted from the requested power level, so that a steady output is
maintained at the top of the cabinet whatever channel is selected.
When the D command is entered at the DCB/RCB/SCB prompt, it effectively executes a
small script containing the following commands:
TS A CHAN 60
Set all timeslots to channel 60.
TS A TX 00
Set all timeslots to full power.
MDLTR UC
Turn the modulation off.
Prior to executing the CSPWR command, it assumes that the synthesizers are hopping (not locked) as is the case
after the unit is powered up for the first time. To alter the power, typing U increments or typingD decrements
the power setting byte. On completion, the command is exited and the appropriate power byte is saved to RAM.
To specify a particular channel (instead of defaulting to channel 60), two extra commands must be
entered prior to executing the CSPWR command, one to set the appropriate channel and the other to
lock the synthesizer. By locking the synthesizer, the channel selection made in the CSPWR command
will be ignored and the output is maintained at the frequency specified.
2-16
GMR-01
68P02901W43-P
23 Feb 2004
This procedure applies to the DRCU, DRCUII and DRCU3.

In this section DRCU is used to mean DRCU, DRCUII, or DRCU3.
The DCB prompt applies to the DRCU.
The RCB prompt applies to the DRCUII.
The SCB prompt applies to the DRCU3.

The following equipment is needed to carry out the procedure:
RF wattmeter with 5 W and 50 W elements.
50 ohm 50 W dummy load.
9-way to 25-way GPROC cable.
All test equipment and test leads must be calibrated annually by a recognized
laboratory. Test equipment and test leads must not be calibrated in the field.
Do not optimize Motorola cellular base stations with
test equipment that is beyond its calibration due date.
Commands used
The following commands are used to carry out the procedure:
BSS MMI command
lock_device
68P02901W43-P
23 Feb 2004
Function
Prevents the device being used.
2-17
GMR-01
Function
BSS MMI command

unlock_device
Frees the device for further use.
clear_cal_data
Clears previously stored calibration data for a

specified radio unit on a per DRI basis.
Function
DRCU emulator command

SWAP C 0
Swaps control code between memories to check data.
SWAP E A
Swaps equalizer code between memories to check data.
SWAP P 0
Swaps PA code between memories to check data.
EXEC C 0
Executes control code currently held in RAM.
EXEC P 0
Executes PA code currently held in RAM.
HALT P 0
Places the power amplifier into active standby mode.
HALT C 0
Places the SCB into active standby mode.
TEST
Places the DRCU into test mode.
ACTIVE P 0
Places the power amplifier into call processing mode.
CSPWR
Sets the cellsite power level using the following controls:

U
Increases cellsite power by 0.2 dB.
Decreases cellsite power by 0.2 dB.
ESC
Exits the calibration session and stores the settings.
TS T CHAN XX
Timeslot set up.

Where:
TS = timeslot number or A = ALL.
XX = ARFCN to tune timeslot to.
SYNTH N
Locks the transmitted frequency on synthesizer n.
The symbol 0 in the commands above is a zero.
2-18
GMR-01
68P02901W43-P
23 Feb 2004
Preparation for Tx power calibration and VSWR check

Use the following procedure to prepare for calibration of the DCRU Tx power and VSWR check:
Procedure 2-6
1
Prepare for DCRU Tx power calibration and VSWR check
Connect the 9-way to 25-way cable from the PC serial A port to a GPROC TTY
port.
The generic term GPROC is used to denote the GPROC, GPROC2

and {4354} GPROC3 processor boards.
2
Start the terminal emulator program at the PC and enter the password at the
CUST/MMI prompt.
Lock the cell, enter the command:

lock_device # dri a * 0
Where:
# is the number of the site logged into.
a is the antenna/relative cell number (0 to 5).
* is the DRI number on the antenna.
Clear all calibration data from the CM database to override the preserve
calibration feature, if enabled. Enter the command:
clear_cal_data # dri a * 0
Where:
68P02901W43-P
23 Feb 2004
Connect the wattmeter, with 50 W element and dummy load to the TX port, at the
top of the cabinet. If a remote tune combiner is fitted, the relevant port must be
tuned to channel 60.
In the case of external combiners, connect the wattmeter with 50 W element and
dummy load to the output port of the combiner.
Disconnect and remove the 9-way to 25-way cable.
Disable the DRI controlling the DRCU under test using the disable switch on the
DRI front panel.
Connect the 9-way to 9-way cable from the PC serial A port to a CONT PRCSR
port on the DRCU.
Reset the DRCU using the manual reset button.
2-19
GMR-01
Tx forward power test procedure

Use the following procedure to check Tx forward power:
Procedure 2-7
Check Tx forward power
Enter the boot code passwords.
Enter the commands:

SWAP C 0
EXEC C 0
At the DCB/RCB/SCB prompt, enter the op code password.
Enter the commands:

SWAP P 0
EXEC P 0
SWAP E A
TEST
ACTIV P 0
If an RTC is fitted go to step 7.
To select all timeslots and a particular channel, enter the following commands at
the DCB/RCB/SCB prompt:
TS A CHAN NNN
SYNTH N
Where:
A is all the timeslots.
NNN is the specified channel number.
N is the synthesizer number.
At the DCB/RCB/SCB prompt, enter the command:

CSPWR
Monitor and record the forward output power readings indicated on the wattmeter.
Press ESC.
2-20
GMR-01
68P02901W43-P
23 Feb 2004
Tx reverse power test procedure

Use the following procedure to check Tx reverse power:
Procedure 2-8
Check Tx reverse power
Replace the 50 W element in the wattmeter with a 5 W element and reverse

the direction on the wattmeter.
Enter the command: CSPWR.
Monitor and record the reverse power readings indicated on the wattmeter.
Readings should show reflected (reverse) power of no more than 1

W or 5% of forward power. If the ratio of the forward and reverse
readings is unacceptable, suspect an improper termination of the
antenna feeder and connector.
4
Press ESC
Tx output power setting procedure

Use the following procedure to set the Tx output power:
Procedure 2-9
Set Tx output power
Replace the 5 W element in the wattmeter with a 50 W element, and connect the
meter in the forward direction.
Enter the command:CSPWR.

Hit U or D until desired max is measured then hit (ESC, CTL-Y
OR CTL-C)
68P02901W43-P
23 Feb 2004
Enter the command: U or D to achieve 43 dBm (20 W) measured power at the top
of the cabinet.
When combiners are used the full power may not be achieved. The acceptable
measured power levels are listed below:
Equipment fitted
Measured power
1 stage combiner
42.55 dBm (18 W)
RTC
42.75 dBm (18.8 W)
2-21
GMR-01
Procedure 2-9
Set Tx output power (Continued)
An additional hybrid combiner can add a 3.2 dB loss.

A message similar to the following example is displayed:
D
P:47.8 dBm
Cell Site Offset
:1
The message indicates the DRCU output power and offset (1 step = 0.2 dB).
4
When the required level is achieved press ESC.The cellsite offset can be checked by
connecting to the CONT PRCSR port and reading the following memory locations:
For a DRCU, enterR E:5B13
For a DRCUII, enterR E:5B0C
For a DRCU3, enterR E:5B0C
Site restoration
Use the following procedure to restore the site after the DRCU Tx output power is set:
Procedure 2-10
Restore site after setting DRCU Tx output power
Remove the 9-way to 9-way cable and reconnect the DATA IN fibre cable.
Connect the serial A port on the PC to a GPROC TTY port using the 9 to 25-way
cable.
Power down the DRCU and remove the wattmeter and dummy load from the Tx
port.
Reconnect the antenna lead to the Tx port.
Power up the DRCU.
At the CUST MMI prompt, enter the command:

unlock_device # dri a * 0
Where:
Remove the 9-way to 25-way cable.

The DRCU is now in call processing mode.
2-22
GMR-01
68P02901W43-P
23 Feb 2004
DRCU, DRCUII and DRCU3 bay level offset tables calibration
DRCU, DRCUII and DRCU3 bay level offset tables

calibration
DRCU, DRCUII and DRCU3 bay level offset tables calibration can be carried out automatically
using the CINDY commissioning tool. Refer to the relevant CINDY user documentation for details.
This procedure is used to calibrate the bay level offset tables which compensate for the losses or gains, due to
preselectors and RF cabling, from the antenna inputs at the BTS to the DRCU, DRCUII or DRCU3 input.
This procedure applies only to the DRCU, DRCUII and DRCU3.

In this section DRCU is used to mean DRCU, DRCUII or DRCU3. Exceptions
are identified by DRCUII or DRCU3 alternatives.
The DCB prompt applies to the DRCU.
The RCB prompt applies to the DRCUII.
The SCB prompt applies to the DRCU3.
When the disp_cal_data command is used from the CM database to check

calibration offsets (with the transceiver locked), the value displayed will be 15 (1.5
dB) offset to that of the unlocked transceiver.

The following test equipment is required to carry out this procedure:
68P02901W43-P
23 Feb 2004
Signal generator.
2-23
GMR-01
Do not optimize Motorola cellular base stations with test equipment
that is beyond its calibration due date.
Commands used
The following commands are used to carry out this procedure:
BSS MMI command
Function
lock_device
unlock_device
clear_cal_data

specified radio unit on a per DRI basis.
Function

SWAP C 0
Swaps controller code between memories to check validity.
EXEC C 0
Executes controller code currently stored in RAM.
SWAP P 0
Swaps PA code between memories to check validity.
EXEC P 0
Executes PA code currently stored in RAM.
SWAP E A
Swaps equalizer code between memories to check validity.
CONFGR E A
Sends call processing calibration tables to DEQDSP.
TEST
Places the DRCU into test mode.
SNDEQ 0 3C
Emulates equalizer messaging.
IQDC0 0
Queries equalizer for IQ absolute dc offset.
IQDCP 0
Passes dc offset information to equalizer DSP.
AIC OUT
Disables automatic intermodulation compensation.
TS A CHAN #
Sets all timeslots to channel #.
TS A ANT #
Sets all timeslots to antenna #.
CAL BAY @1/@2
Calibrates the bay level receive equipment.
2-24
GMR-01
68P02901W43-P
23 Feb 2004
Function

CALCHK
Verifies calibration data.
1. The symbol 0 in the commands above is a zero.

2. The lock_device, unlock_device and clear_cal_data commands are BSS MMI commands
and may be entered in upper or lower case; the rest of the commands in this list are DRCU
(emulator) commands and case is as shown.
Preparation for bay level table calibration

Use the following procedure to prepare for calibration of the DRCU, DRCUII and DRCU3 bay level
offset tables:
Procedure 2-11 Prepare for DRCU bay level offset table calibration
1
port.

{4354} and GPROC3 processor boards.
2
At the PC start the terminal emulator program.
Lock the cell using the lock device command.
Failure to lock the cell could result in the BCCH

transmitting into, and causing damage to the signal
generator.The maintenance engineer could receive RF
burns when connecting to the antenna socket.
Enter the command:
Where:
68P02901W43-P
23 Feb 2004
2-25
GMR-01
Procedure 2-11
4
Prepare for DRCU bay level offset table calibration (Continued)

5
If the DRCU is not connected to a Tx antenna, connect a dummy load to the Tx

port of the DRCU under test.
Connect the RF output of the signal generator to the DRCU Rx port.
Disconnect the 9-way to 25-way cable from the GPROC TTY port.
Connect the serial A port on the PC to the CONT PRCSR port on the DRCU
using the 9-way to 9-way cable.
Calibration setup procedure

Use the following procedure to set up the calibration:
Procedure 2-12
1
Set up calibration
Enter the entry level password to obtain the DCB/RCB/SCB prompt.
DCB is the prompt for DRCU.RCB is the prompt for DRCUII.SCB

is the prompt for DRCU3.
For DRCU3, reset using the front panel switch, and at the SCB
prompt, enter the boot passwords one and two.
2

SWAP C 0
EXEC C 0
At the DCB/RCB/SCB prompt, enter the password.
For DRCU3, the entered password is password three.
2-26
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-12
Set up calibration (Continued)

SWAP P 0
EXEC P 0
SWAP E A
TEST
SNDEQ 0 3C
IQDCO 0
IQDCP 0
AIC OUT
Set the signal generator to the first channel frequency (channel 04 = 890.801
MHz) at a level of -65.2 dBm.
The Tx level of the signal generator must be set to allow for losses in
the test leads used. It is vital that the signal generator and cables are
correctly calibrated, and the RF cables are in good order.
6
If a six-way splitter is used, go to Calibration with a six-way splitter procedure.

If a receiver matrix is fitted, go to Calibration with a receive matrix procedure.
Calibration with a six-way splitter procedure

Use the following procedure to set calibration with a six-way splitter:
Procedure 2-13 Set calibration with a six-way splitter
1
Connect the output of the signal generator to branch 1 of the antenna to be used
(RX1A, RX2A or RX3A) for the DRCU under test.
At the DCB/RCB/SCB prompt, enter the appropriate command for RX1A, 2A &
3A:
TS A ANT 1 (2) or (3)

TS A CHAN #
Where:
# is the channel number shown in Table 2-9
68P02901W43-P
23 Feb 2004

CAL BAY @1
Repeat step 2 and step 3 with the signal generator set to the appropriate frequency
for all the test frequencies shown in Table 2-9
For branch 2, set the signal generator back to channel 04 (890.801 MHz) at -65.2
dBm and repeat step 1 to step 4using connectors RX1B, RX2B and RX3B at the
top of the cabinet.
Enter @2instead of@1 in the CAL BAY command.
2-27
GMR-01
Table 2-9
Channel frequency listing
Channel
Frequency (MHz)
Channel
Frequency (MHz)
04
890.801
68
903.601
12
892.401
76
905.201
20
894.001
84
906.801
28
895.601
92
908.401
36
897.201
100
910.001
44
898.801
108
911.601
52
900.401
116
913.201
60
902.001
122
914.401
Calibration with a receive matrix procedure

Use the following procedure to set calibration with a receive matrix:
Procedure 2-14
Calibrate with a receive matrix
Ensure that the DIP switches on the receiver matrix are set to output signal
selection DRCU data controlled.
Connect the output of the signal generator to RX1A and at the DCB/RCB/SCB
prompt, enter the command:
TS A ANT 1

TS A CHAN #
Where:
# is the channel number shown in Table 2-9.
CAL BAY @1
Set the signal generator to the appropriate frequency and repeat step 3 for all test
frequencies listed in Table 2-9.
TS A ANT 2

TS A CHAN #
Where:
CAL BAY @1
2-28
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-14
Calibrate with a receive matrix (Continued)
TS A ANT 3

TS A CHAN #
Where:
CAL BAY @1
10
11
For branch 2, set the signal generator back to channel 04 (890.801 MHz) at -65.2
dBm and repeat step 1 to step 10, using connectors RX1B, RX2B and RX3B at
the top of the cabinet.
Enter @2 instead of @1 in the CAL BAY command.
Stored bay level offset verification procedure

Use the following procedure to verify the bay level offset values have been stored in EPROM:
Procedure 2-15
Verify bay level offset values stored in EPROM
Refer to Table 2-10 and Table 2-11 for lists of commands with offset table
location for branch 1 and branch 2.
Enter the read command with the required offset table location as an argument.
For example, in the case of Branch 1 DRCU antenna 1, the read command is:R
E: 5391 53A0
If the bay level calibration is successful, each of the locations shown in the
appropriate table, will contain valid offsets and must not contain the factory
default of 80.
Any value from 81 to FF and 00 to 7F except 80 is a valid offset.

The value 80 indicates an unsuccessful calibration procedure or an
uncalibrated antenna port and will result in error alarm DRI 218:
Invalid Transceiver Calibration Data being reported when the unit is
unlocked. The calibration procedure will have to be repeated after
checking the configuration and RF cables.
Unused data columns in a site configuration may have value 80.
No alarm will be reported as such table locations are inappropriate
to the site.
68P02901W43-P
23 Feb 2004
2-29
GMR-01
Procedure 2-15
Verify bay level offset values stored in EPROM (Continued)

CALCHK
All the calibrated parameters for the DRCU are displayed.
To check the calibration valid bits are set correctly, for transceiver type:
DRCU enter: DCB> R E: 5B1C
DRCUII enter: RCB> R E: 5B15
DRCU3 enter: SCB> R E: 5B15
If the reply is FFFFFF on a DRCU or FFFE00 on a DRCUII/DRCU3, the
calibration valid bits are set correctly.
The bits must be set, otherwise the bay level tables will not be used
as offset, and a default value of 80 will be used.
5
To enable setting of the calibration valid bits on a DRCU at the DCB/RCB/SCB

WRENB E
To set the calibration valid bits at the DCB/RCB/SCB prompt for transceiver type:
DRCU enter: DCB> R E: 5B1C FFFFF
DRCUII enter: RCB> R E: 5B15 FFFE00
DRCU3 enter: SCB> R E: 5B15 FFFE00
To protect the calibration valid bits set on a DRCU at the DCB/RCB/SCB

WRPTC E
To check if the calibration valid bits are set correctly, for transceiver type:
DRCU enter: DCB> R E: 5B1C
DRCUII enter: RCB> R E: 5B15
DRCU3 enter: SCB> R E: 5B15
If the reply is FFFFFF on a DRCU or FFFE00 on a DRCUII/DRCU3, the
calibration valid bits are set correctly.
Table 2-10 and Table 2-11 list the commands with offset table location for branch 1 and branch 2.
Table 2-10
Ant
Branch 1 offset table locations

Parameter DRCU
Valid Input DRCUII
Default DRCU3
DCB> R E:5391 53A0
DCB> R E:538A 5399
DCB> R E:538A 5399
DCB> R E:53C1 53D0
DCB> R E:53BA 53C9
DCB> R E:53BA 53C9
DCB> R E:53F1 5400
DCB> R E:53EA 53F9
DCB> R E:53EA 53F9
2-30
GMR-01
68P02901W43-P
23 Feb 2004
Table 2-11
Branch 2 offset table locations
Ant
Parameter DRCU
Valid Input DRCUII
Default DRCU3
DCB> R E:5421 5430
DCB> R E:541A 5429
DCB> R E:541A 5429
DCB> R E:5451 5460
DCB> R E:544A 5459
DCB> R E:544A 5459
DCB> R E:5481 5490
DCB> R E:547A 5489
DCB> R E:547A 5489
Site restoration
Use the following procedure to restore the site after calibration of DRCU, DRCUII
and DRCU3 bay level offset tables:
Procedure 2-16
Restore site after DRCU bay level offset calibration
Connect the serial A port on the PC to a GPROC TTY port using the 9-way
to25-way cable.
Enter the command:

Where:
68P02901W43-P
23 Feb 2004

The DRCU is now in call processing mode.
2-31
GMR-01
SCU Tx power calibration and VSWR check
SCU Tx power calibration and VSWR checks can be carried out automatically using the CINDY
commissioning tool. Refer to the relevant CINDY user documentation for details.
This procedure is used to set the pre-defined maximum transmitter output power at the top of the
cabinet, and to ensure that antenna feeders and connectors are properly terminated.
This procedure applies only to the SCU900 and SCU1800.

TCUs can be converted to SCU use in a BTS cabinet, by operation of a switch
on the TCU unit. The TCU can then be considered an SCU, with the procedure
the same as for an SCU, except where stated.
Ensure that a TCU is switched to SCU mode before connection to B2. (In TCU mode the
B2 inner is at +12 V dc to power the DLNB in M-Cell equipment).
These procedures aim to produce a radio that exhibits a flat frequency response over the full GSM
band. In the case of the transmitter, this is performed by sharing out the channels over three detector
groups (the detector being the device that maintains a steady output power level).
called cellsite Power (CSPWR). During CSPWR the cabinet output power can be trimmed
to account for any abnormalities that may occur between the SCU and the top of the cabinet.
When the CSPWR command is entered at the SCP prompt, it effectively executes a small
script containing the following commands:
TS A CHAN 700
Set all timeslots to channel 700 (SCU1800).
TS A CHAN 31
Set all timeslots to channel 31 (SCU900).
TS A TXP 00
MDLTR UC
Prior to executing the CSPWR command, it assumes that the synthesizers are hopping (not locked) as is the case
after the unit is powered up for the first time. To alter the power, typing Uincrements or typing Ddecrements the
power setting byte. On completion, the command is exited and the appropriate power byte is saved to RAM.
2-32
GMR-01
68P02901W43-P
23 Feb 2004
To specify a particular channel (instead of defaulting to channel 31 or 700), two extra commands
must be entered prior to executing the CSPWR command, one to set the appropriate channel and
the other to lock the synthesizer. By locking the synthesizer, the channel selection made in the
CSPWR command will be ignored and the output is maintained at the frequency specified. To save
to non-volatile memory, the SAVE CAL TX command must be used.

The following equipment is needed to carry out this procedure:
Commands used
BSS MMI command
Function
lock_device
unlock_device
clear_cal_data
Clears previously stored calibration data for a specified radio unit

on a per DRI basis.
state
Displays the current status of devices or functions.

Function
SCU emulator command

SWAP C 0
Swaps SCP code between memories to check data.
SWAP E A
Swaps EQB code between memories to check data.
EXEC C 0
Executes SCP code currently held in RAM.
TEST
Places the SCU into test mode.
CSPWR
Sets the cellsite power level using the following controls:
Increases cellsite power by 0.2 dB.
Decreases cellsite power by 0.2 dB.
ESC
Exits the calibration session and stores the settings.
68P02901W43-P
23 Feb 2004
2-33
GMR-01
Function

TS A CHAN XX
Timeslot set up.

Where:
TS = Timeslot No. or A = ALL.
SYNTH N
Locks the transmitted frequency on synthesizer n.
SAVE CAL TX
Saves the calibration settings.

2. The lock_device, unlock_device and clear_cal_data commands are BSS
MMI commands and may be entered in upper or lower case; the rest of the commands in this
list are all SCU (emulator) commands and case is as shown.
Preparation for Tx power calibration and VSWR check

Use the following procedure to prepare for calibration of SCU Tx power and VSWR check:
Procedure 2-17
1
Prepare for SCU Tx power calibration and VSWR check
port.

2
At the CUST/MMI prompt, enter the password.
Lock the cell using the lock device command:

Where:
2-34
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-17
5
Prepare for SCU Tx power calibration and VSWR check (Continued)
Where:
Connect the wattmeter with 50 W element and dummy load to the Tx port at the
top of the cabinet.
If an RTC is fitted the relevant port must be tuned to the channel the RTC is set to.
If external combiners are used connect the wattmeter with 50 W element and
dummy load to the output port of the combiner.
Disconnect and remove the 9-way to 25-way cable.
Connect the 9-way to 9-way cable from the PC serial A port to a CONT PRCSR
port on the SCU.
Reset the SCU under test using the front panel reset button.
Tx forward power test procedure

Use the following procedure to check Tx forward power:
Procedure 2-18 Check Tx forward power
1
Enter the boot passwords (different from the DRCU passwords).
At the SCP prompt, enter the command:

SWAP C 0
EXEC C 0
.<LEVEL_3_PASSWORD> (different from the DRCU password)
TEST
To select all timeslots and a particular channel, enter the following commands at
the SCP prompt:
TS A CHAN XXX
SYNTH Y
Where:
A is all the timeslots (TS).
XXX is the specified channel number.
Y is the synthesizer number.
When an RTC is fitted, the channel number must be the same as the
one chosen for the RTC cavity connected to this SCU.
68P02901W43-P
23 Feb 2004
2-35
GMR-01
Procedure 2-18
Check Tx forward power (Continued)

CSPWR
Press ESC.
2-36
GMR-01
68P02901W43-P
23 Feb 2004
Tx reverse power test procedure

Use the following procedure to check Tx reverse power:
Procedure 2-19 Check Tx reverse power
1


CSPWR
Readings should show reflected (reverse) power of no more than 1 W

or 5% of forward power.
If the ratio of the forward and reverse readings is unacceptable,
suspect an improper termination of the antenna feeder and connector.
4
Press ESC.
Tx output power setting procedure

Use the following procedure to set Tx output power:
Procedure 2-20
Set Tx output power
Replace the 5 W element in the wattmeter with a 50 W element and connect the

CSPWR
Enter U or D to achieve measured power at the top of the cabinet of 42.05 dBm
(16 W) for SCU1800, or 43 dBm (20 W) for SCU900.
When combiners are used the full power may not be achieved. The acceptable
measured power levels are listed below:
Equipment fitted
Measured power
(SCU900)
Measured power
(SCU1800)
1 stage combiner
42.55 dBm (18 W)
39.0 dBm (8 W)
RTC
42.75 dBm (18.8 W)
40 dBm (10 W)
An additional hybrid combiner can add a 3.2 dB loss.

As U orD is entered, a message similar to the following example is displayed:
D
P:43.8 dBm
Cell Site Offset
:1
The message indicates the DRCU output power and offset value (1 step = 0.2 dB).
68P02901W43-P
23 Feb 2004
2-37
GMR-01
Procedure 2-20
Set Tx output power (Continued)
When the required level is achieved, press ESC.

SAVE CAL TX
The cellsite offset can be checked by reading its memory location:R F:15780
Repeat the forward and reverse output power checks and the setting up Tx output
power, for all SCUs.
Site restoration
Use the following procedure to restore the site after calibration of SCU Tx power and VSWR check:
Procedure 2-21
Restore site after SCU Tx power ans VSWR check
Remove the 9-way cable from the CNTRL PRSCR port and press the reset button
on the SCU front panel.
Connect serial A port on the PC to a GPROC TTY port using the 9-way to
25-way cable
Power down the SCU and remove the wattmeter from the Tx port.
Reconnect the antenna lead to the Tx port.
Power up the SCU and at the customer MMI prompt, enter:

state # dri a * 0
Where:
Remove the 9-way to 25-way cable from the GPROC TTY port.
The SCU is now in call processing mode.
2-38
GMR-01
68P02901W43-P
23 Feb 2004
SCU900/1800 bay level offset tables calibration
SCU bay level offset tables calibration can be carried out automatically using the CINDY
This procedure is used to calibrate the bay level offset tables which compensate for the losses or gains due to
preselectors and RF cabling from the antenna inputs at the BTS to the SCU900 or SCU1800 input.
This procedure applies only to the SCU900 and SCU1800.

TCUs can be converted to SCU use in a BTS cabinet, by operation of a switch
on the TCU unit. The TCU can then be considered an SCU, with the procedure
the same as for an SCU, except where stated.
The following test equipment is required:
68P02901W43-P
23 Feb 2004
Signal generator.
2-39
GMR-01
Commands used
Function
BSS MMI command

lock_device
unlock_device
clear_cal_data

on a per DRI basis.
Function

SWAP C 0
Swaps DPC code from ROM to RAM and checks validity.
EXEC C 0
Executes DPC code currently stored in RAM.
SWAP E A
Swaps EQB code from ROM to all four EQDSPs and checks validity.
CONFGR E A
Sends call processing calibration tables to equaliser.
TEST
Places the SCU/TCU into test mode.
CAL BAY @1/@2
Calibrates the bay level receive equipment.
EQTEST 0
Puts equalizer 0 into test mode and checks status.
IQDCP 0
Passes the factory calibrated dc offset information stored in ROM to

EQDSP 0.
AIC OUT
Disables automatic intermodulation compensation.
TS A CHAN #
Sets all timeslots to channel #.
TS A ANT #
Sets all timeslots to antenna #.
R F:XX YY
Reads flash memory bay level data held at addresses XX to YY.
SYNTH 1
Stops synthesizer switching with synthesizer 1 permanently on.
SYNTH NRM
Enables synthesizer switching into normal working.
SAVE CAL BAY
Transfers bay level calibration data in RAM to ROM.
BAYDONE @N
Informs control processor that bay level calibration is valid for

branch N and sets bay level flag.

MMI commands and may be entered in upper or lower case; the remainder of the commands in
this list are all SCU (emulator) commands, input as shown. The first SCU password must be
in upper case.
2-40
GMR-01
68P02901W43-P
23 Feb 2004
Setting up procedure
The radio has to first be locked, a dummy load fitted if there is no antenna connected, and
the SCU reset and set up for bay level calibration.
Ensure that a TCU is switched to SCU mode before connection to B2. (In TCU
mode, the RX2 inner is at +12 V dc to power the DLNB in M-Cell equipment.)
Use the following procedure to prepare for SCU900/1800 bay level offset tables calibration:
Procedure 2-22
1
Prepare for SCU900/1800 bay level offset tables calibration
port.

2

generator. The maintenance engineer could receive RF
Enter the command:
Where:
4
Where:
68P02901W43-P
23 Feb 2004
2-41
GMR-01
Procedure 2-22
Prepare for SCU900/1800 bay level offset tables calibration (Continued)
If a Tx antenna is not connected to the SCU under test, connect a 50 ohm 50 W

dummy load to the Tx port of the SCU under test.
Remove the 9-way to 25-way cable from the PC serial A port to the GPROC
TTY port.
Connect the serial A port on the PC to the CNTRL PRCSR port on the SCU
using the 9-way to 9-way cable.
Reset the SCU using the front panel reset button.
Enter the boot passwords.
10
At the SCP prompt, enter the commands:

SWAP C 0
EXEC C 0
.<LEVEL_3_PASSWORD> (different from the (D)RCU password)
SWAP E A
CONFGR E A
TEST
AIC OUT
EQTEST 0
IQDCP 0
GSM900 and DCS1800 test frequencies

Table 2-12 and Table 2-13 list GSM900 and DCS1800 test frequencies required for
the bay level offsets calibration procedures.
Table 2-12
GSM900 test frequencies
Channel
Frequency (MHz)
Channel
Frequency (MHz)
03
890.601
67
903.401
11
892.201
75
905.001
19
893.801
83
906.601
27
895.401
91
908.201
35
897.001
99
909.801
43
898.601
107
911.401
51
900.201
115
913.001
59
901.801
123
914.601
2-42
GMR-01
68P02901W43-P
23 Feb 2004
Table 2-13
68P02901W43-P
23 Feb 2004
DCS1800 test frequencies
Channel
Frequency (MHz)
Channel
Frequency (MHz)
516
1711.001
708
1749.401
524
1712.601
716
1751.001
532
1714.201
724
1752.601
540
1715.801
732
1754.201
548
1717.401
740
1755.801
556
1719.001
748
1757.401
564
1720.601
756
1759.001
572
1722.201
764
1760.601
580
1723.801
772
1762.201
588
1725.401
780
1763.801
596
1727.001
788
1765.401
604
1728.601
796
1767.001
612
1730.201
804
1768.601
620
1731.801
812
1770.201
628
1733.401
820
1771.801
636
1735.001
828
1773.401
644
1736.601
836
1775.001
652
1738.201
844
1776.601
660
1739.801
852
1778.201
668
1741.401
860
1779.801
676
1743.001
868
1781.401
684
1744.601
876
1783.001
692
1746.201
883
1784.401
700
1747.801
2-43
GMR-01
Branch1 RX1A bay level offsets calibration procedure

Use the following procedure to calibrate bay level offsets for RX1A:
Procedure 2-23
Calibrate bay level offsets for RX1A
Connect the output of the signal generator to branch 1 of the antenna port (RX1A,
RX2A or RX3A at the top of the cabinet) for the SCU under test.
Set the signal generator to the first channel test frequency shown in Table 2-12
or Table 2-13 at a level of -65.2 dBm.
3

TS A ANT 1

TS A CHAN #
Where:
# is the channel number as shown in Table 2-12 or Table 2-13

SYNTH 1
CAL BAY @1
SYNTH NRM
When the synthesizer is left unlocked, the bay level figure can vary
as much as 1dB at certain frequencies. By locking the synthesizer
(using commands SYNTH 1 and SYNTH NRM this variation can
be reduced to 0.1 dB.
6
Repeat step 4 and step 5 for each signal generator test frequency in Table 2-12
or Table 2-13.
The BTS cabinets described in this chapter only support PGSM,

and not EGSM.
7
Transfer the bay level calibration figures to non-volatile SCU memory. At the
SCP prompt, enter the command:
SAVE CAL BAY
2-44
GMR-01
68P02901W43-P
23 Feb 2004
Branch 1 RX2A bay level offsets calibration procedure

Procedure 2-24 Calibrate bay level offsets for RX2A
1
Connect the output of the signal generator to RX2A.
or Table 2-13.
At the SCP prompt enter the command:

TS A ANT 2

TS A CHAN #
Where:
# is the channel number as shown in Table 2-12 or Table 2-13.

SYNTH 1
CAL BAY @1
SYNTH NRM
or Table 2-13.
Transfer the bay level calibration figures to non-volatile SCU memory

SAVE CAL BAY

1
or Table 2-13.

TS A ANT 3

TS A CHAN #
Where:
# is the channel number as shown in Table 2-12 or Table 2-13.
68P02901W43-P
23 Feb 2004
2-45
GMR-01
Procedure 2-25
Calibrate bay level offsets for RX3A (Continued)

SYNTH 1
CAL BAY @1
SYNTH NRM
or Table 2-13.
Transfer the bay level calibration figures to non-volatile SCU memory.

SAVE CAL BAY
Branch 1 completion
The BAYDONEcommand completes the procedure for a branch
by setting a flag to indicate the calibration figures are correct:
Procedure 2-26 Complete branch 1 bay level offsets calibration
BAYDONE @1
This completes the bay level offset tables calibration for Branch 1.
Branch 2 bay level offsets calibration

To calibrate bay level offset tables for Branch 2, repeat the following procedures using connectors
RX1B, RX2B and RX3B respectively at the top of the cabinet:
Branch
Branch
Branch
Branch
1
1
1
1
RX1A bay level offsets calibration procedure

completion
Enter @2 instead of @1 in the CAL BAY and BAYDONE commands.
2-46
GMR-01
68P02901W43-P
23 Feb 2004
Calibration check procedure

Use the following procedure to check that the SCU900/1800 bay level offset values have been stored in EPROM:
Procedure 2-27
Check SCU900/1800 bay level offset values stored in EPROM
Use the read command with the required offset table location as an argument.
The read command locations are shown in Table 2-14 and Table 2-15.
For example:R F:153B6 153C5 in the case of an SCU900
As the SCU is used only in BTS cabinets, covering the GSM range, only the 16
locations per antenna per branch are relevant, as shown in Table 2-14.
If the bay level calibration is successful, each appropriate table location will
contain valid offsets and not the factory default of 80.

uncalibrated antenna port and will result in error alarm DRI 218:
Invalid Transceiver Calibration Databeing reported when
the unit is unlocked. The calibration procedure will have to be
repeated after checking the configuration and RF cables.
to the site.
3
Table 2-14
If the radio is suspected to be faulty, see next section Diagnostic check

procedure.
SCU900 frequency offset addresses

Antenna
Locations
RX1A Antenna 1 Branch 1
F: 15386 15395
F: 153B6 153C5
F: 153E6 153F5
RX1B Antenna 1 Branch 2
F: 15416 15425
F: 15446 15455
F: 15476 15485
The read command allows a maximum of 16 locations to be read at one time. Thus for DCS1800, SCUs
require using the read command three times per antenna per branch, as shown in Table 2-15.
68P02901W43-P
23 Feb 2004
2-47
GMR-01
Table 2-15 DCS1800 frequency offset addresses

Antenna
Locations
First read
Second read
Third read
RX1A Antenna 1 (A)
F: 15380 1538F
F: 15390 1539F
F: 153A0 153AE
RX2A Antenna 2 (A)
F: 153B0 153BF
F: 153C0 153CF
F: 153D0 153DE
RX3A Antenna 3 (A)
F: 153E0 153EF
F: 153F0 153FF
F: 15400 1540E
RX1B Antenna 1 (B)
F: 15410 1541F
F: 15420 1542F
F: 15430 1543E
RX2B Antenna 2 (B)
F: 15440 1544F
F: 15450 1545F
F: 15460 1546E
RX3B Antenna 3 (B)
F: 15470 1547F
F: 15480 1548F
F: 15490 1549E
Diagnostic check procedure

If it is suspected that a bay level calibration problem is caused by the SCU, a diagnostic check
can be made by performing a bay level calibration on the SCU alone.
Use the following procedure to carry out the diagnostic check:
Procedure 2-28
Perform diagnostic check
Set the signal generator to -55 dBm plus lead loss to simulate a gain of 10 dB.
Connect directly to branch 1 or 2 on the SCU.
Ensure a TCU is switched to SCU mode before connection

to RX2. In TCU mode the RX2 inner is at +12 V dc to power
the DLNB in M-Cell equipment. A signal source may be
damaged by taking +12 V dc in its RF output.
3
Follow the bay level calibration procedures:

Check the diagnostic offset values are within the range 97 (lower) and D3 (upper).
The range 97 - D3 used in step 4, applies to SCU diagnostic checks

only, and should not be compared with the bay level calibration
figures.
If the values are correct, then the SCU is working correctly and any fault will
probably be in the cabinet front end cables, cable connections or preselector
modules.
If the offsets are outside this range, the SCU is faulty and should be returned.
2-48
GMR-01
68P02901W43-P
23 Feb 2004
Site restoration
Use the following procedure to restore the site after bay level calibration:
Procedure 2-29
Restore site after bay level calibration
Remove the signal generator and dummy load and refit the site RF cables.
Remove the 9-way to 9-way cable from the CNTRL PRSCR port on the SCU.
port
Press the reset button on the front panel of the SCU.
Enter the command:

Where:
68P02901W43-P
23 Feb 2004
Remove the 9-way to 25-way cable from the GPROC TTY port.
2-49
GMR-01
Database check for devices and functions
This procedure is used to check which devices and functions are contained in the BSC/BTS database.

The following test equipment is required to carry out the procedure:
Commands used
The following commands must be used to carry out the procedure:
Function
Command
disp_site
Displays the site number.
disp_equipment
Displays the active equipment at a specified site.
Database check procedure

Use the following procedure to check the database for devices and functions:
Procedure 2-30
Check database for devices and functions
Ensure that the site is in call processing mode.
Connect the serial A port on the PC to a GPROC port using the 9-way to 25-way
cable.

3
2-50
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-30 Check database for devices and functions (Continued)

4
At the CUST MMIprompt, enter the command:

disp_site
The following message (from the GPROC) is displayed:
Current site is #
Where:
# is the location id.
5

disp_equipment #
Where:
# is the location id.
A complete list of the equipment and functions in the database is displayed, for
example:
GPROC
GPROC
BSP
DRI
DRI
MSI
MMS
MMS
MTL
OML
GCLK
KSW
CAGE
CAB
SITE
BTF
RTF
RTF
RTF
RTF
RTF
0
1
0
0
0
1
1
1
1
1
0
0
0
0
0
0
0
1
2
3
0
0
0
0
0
1
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
To check the MSI configuration, at the CUST MMI prompt, enter the command:
disp_equipment # MSI * * *
Where:
# is the location id
* is the device/function id (id1, id2, and id3)
MSI identifier 1
Cage number
0
Slot number
16
MSI type
0
(For MSI type: 0 = MSI and 1 = XCDR)
68P02901W43-P
23 Feb 2004
2-51
GMR-01
E1/T1 link check
E1/T1 link check
This procedure is used to verify the integrity of the E1/T1 links to the BSC/MSC.

Commands used
The following command must be used to carry out the procedure:
Function
Command
Displays the status of specified devices or functions.
state
E1/T1 link test procedure

Use the following procedure to check the E1/T1 link:
Procedure 2-31
Check E1/T1 link
Connect the serial A port on the PC to a GPROC TTY port using the 9-way
to 25-way cable.

3
2-52
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-31
4
E1/T1 link check
Check E1/T1 link (Continued)
Contact the BSC/MSC of the E1/T1 link to be tested and request a loopback on
the relevant digital distribution frame (DDF) port.
Repeat for all MSIs and E1/T1 links. If the E1/T1 link has not been
installed, perform this test at the digital distribution frame (DDF) in
the site, or at the top of the cabinet if no DDF is fitted.
5
Determine the site number, equipment list and MMS configuration.

state <site #> MMS <MMS #>
For example:
state 0 MMS 1 0 0
The following message (from the GPROC) is displayed:
Status Information
Administration state : Unlocked
Operational state : Busy
Reason code is : 0
Time of last transition : Wed Jan 5 01:43:13 1994
Other identification : 255 255 255 255
End of status report
If this display shows Unlocked and Busy, then the MSI port (MMS) T43 cabling
and the E1/T1 link are all good.
If the loop is removed and the command re-entered, the result is Unlocked and
Disabled.
The MSI requires at least 20 seconds to register a change in status

after these commands are entered.
If the display continues to show Unlocked and Busy, this may be
because:
68P02901W43-P
23 Feb 2004
The wrong connection is looped, if the cabling is direct.
The MMS may be terminated by a device generating a 2.048

Mbit/s link.
2-53
GMR-01
PIX connections check
This procedure is used to check the PIX connections. This test can be carried out at a live site.

Test plugs A, B and C.
Commands used
The following command is used to carry out the procedure:
Function
Command
enable_alarm
Enables alarm reporting for a specified site.
Preparation for PIX connections check

Use the following procedure to prepare for PIX connections verification:
Procedure 2-32
Prepare for PIX connections verification
Ensure download has been completed.
Connect the serial A port on the PC to the master GPROC using the 9-way to
25-way cable.

3
At the CUST MMI prompt, enter the password.
2-54
GMR-01
68P02901W43-P
23 Feb 2004
PIX connections test procedure

Use the following procedure to verify the PIX connections:
Procedure 2-33
1
At the PC, enter the command:enable_alarm #

Where:
# is the site number.
The system responds with:
SITE
____
#
Verify PIX connections
ENABLE ALARM STATUS

___________________
Site enabled
Connect the PIX test plug C to the appropriate socket on top of the rack.
All eight alarms are displayed.
The states in this step depend on the database settings; whether a fault
condition is indicated by closed loop or an open loop.
Site restoration
To restore the site following PIX connections verification, remove the test plug. This clears the alarm display.
The states in this step depend on the database settings; whether a fault condition
is indicated by closed loop or an open loop.
68P02901W43-P
23 Feb 2004
2-55
GMR-01
Transcoder integration
This procedure is used to ensure that all allocated Circuit Identification Codes (CICs)
are carrying good quality voice traffic.
Transcoders may be in the form of XCDR boards, or an enhanced version utilising a Generic
Digital Signal Processor Board (GDP). If GDPs are used in XCDR slots as XCDRs,
the procedure is the same as for XCDRs, except where stated.
Introduction to transcoder integration

GSM mobile with registered SIM card.
Commands used
Function
Command
disp_mms_ts_usage
Displays the timeslot usage on an MMS span.
disp_link
Displays the BSC-MSC connectivity.
fil_list
Lists active filters.
fil_create
Creates a filter.
fil_start
Starts a filter.
2-56
GMR-01
68P02901W43-P
23 Feb 2004
Function
Command
fil_stop
Stops a filter.
fil_delete
Deletes filters.
Displaying MMS timeslot usage

Before starting the transcoder integration procedure, consult the site specific documentation to
determine the BSC/RXCDR configuration and cage slot allocation. Conventionally, timeslots 00
and 16 on XCDR boards are not allocated to voice/traffic channels.
Use the following procedure to display the MMS timeslot usage:
Procedure 2-34
Display MMS timeslot usage
At the operations and maintenance centre (OMC-R) man-machine interface (MMI), log in
to the required base site controller (BSC).
To display the circuit mapping, enter the command:disp_mms_ts_usage X Y Z

Where:
X is the location.
Y is the 1st digit of MMS identifier.
Z id ht e 2nd digit of the MMS identifier.
The following header message is displayed:
Start of Report:
Site: X MMS: Y Z
TS
Usage
Device ID
Type
Site
CIC
Group
Group
CIC
State
RTF
State
TS
RTF
TS
Under each heading, information relevant to the site and MMS port is displayed.
3
Repeat step 2 for all MMSs.
Log out from the BSC.
Displaying BSC-MSC connectivity

Use the following procedure to display BSC-MSC connectivity:
68P02901W43-P
23 Feb 2004
2-57
GMR-01
Procedure 2-35
Display BSC-MSC connectivity
Log on to the required RXCDR.
To display all CEPT nailed connections, enter the command:

disp_link
The following message is an example response:
Incoming MMS id 6 1, timeslot: - 2 group :
Outgoing MMS id 24 0, timeslot:
- 3
- 1
- 2
- 2
- 1
- 3
- 0
- 4
- 3
- 5
- 2
- 6
- 1
- 7
- 0
- 8
The information in the messagestogether with BSC/RXCDR site documentation,

contain the CIC mapping. Two examples are:
Circuit ID = 3
Group Number = 1
Timeslot Number = 2
Incoming MMS id 6 1, timeslot: - 2 group : - 1
Outgoing MMS id 24 0, timeslot: - 3
Circuit ID = 91
Group Number = 2
Timeslot Number = 24
Incoming MMS id 6 1, timeslot: - 24 group : - 2
Outgoing MMS id 24 0, timeslot: - 3
CIC test procedure

Use the following procedure to check circuit identity code (CIC):
Procedure 2-36
Check CIC
Log on to the required BSC.
At the RAM EMON prompt, enter the command:

fil list
If any filters are shown delete them using the fil delete command.
Remotely log in to the GPROC running the LCF that supports the site under
test using the rlogin command. Determine this using the disp_p <site
number> command at the BSP.
2-58
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-36
4
Check CIC (Continued)

fil create tag 10501h
Filter 10501h is created.
A response ise returned with a filter id.
At the prompt, enter the command:

fil start *
Filter * is started.
Where:
* is the filter id.
Set up a mobile to land or land to mobile call and monitor the filter output.
FILTER: SRC: pid: 10 mbid: 0002 cpu: 0119 subsys: 01
tag: 00010501 len:0014
DEST: function: 0009 instance: 001b mbid: 0003 TIME:
96942.975s
data:00.7b.60.00.0f.00.0d.01.0b.03.01.08.01.07.02.06.00.06.01.00.05
The last two bytes of the data displayed (in hexadecimal) indicate the CIC in
use.Check the quality of the call and, if good, check off the CIC number on
the checklist on the next page.If the quality is bad, note the CIC number and
retest.The last two bytes in the example show a call on CIC 05 (hexadecimal).
Repeat this step until all CICs have been tested.
7

fil stop *
Filter * is stopped.
Where:
* is the filter id.

fil delete *
Filter * is deleted.
Where:
* is the filter id.

fil list
If any filters are shown delete them using the fil delete command.
68P02901W43-P
23 Feb 2004
10
Log out of the BSC.
11
Report the result of the integration and any anomalies to the OMC-R operator.
2-59
GMR-01
CIC checklist
Check off good quality calls on the CIC checklist:
Slot
no.
Slot
no.
Slot
no.
Slot
no.
Slot
no.
Slot
no.
Slot
no.
Slot
no.
Slot
no.
Slot
no.
00 01
00 21
00 41
00 61
00 81
00 A1
00 C1
00 E1
01 01
01 21
00 02
00 22
00 42
00 62
00 82
00 A2
00 C2
00 E2
01 02
01 22
00 03
00 23
00 43
00 63
00 83
00 A3
00 C3
00 E3
01 03
01 23
00 04
00 24
00 44
00 64
00 84
00 A4
00 C4
00 E4
01 04
01 24
00 05
00 25
00 45
00 65
00 85
00 A5
00 C5
00 E5
01 05
01 25
00 06
00 26
00 46
00 66
00 86
00 A6
00 C6
00 E6
01 06
01 26
00 07
00 27
00 47
00 67
00 87
00 A7
00 C7
00 E7
01 07
01 27
00 08
00 28
00 48
00 68
00 88
00 A8
00 C8
00 E8
01 08
01 28
00 09
00 29
00 49
00 69
00 89
00 A9
00 C9
00 E9
01 09
01 29
00 0A
00 2A
00 4A
00 6A
00 8A
00 AA
00 CA
00 EA
01 0A
01 2A
00 0B
00 2B
00 4B
00 6B
00 8B
00 AB
00 CB
00 EB
01 0B
01 2B
00 0C
00 2C
00 4C
00 6C
00 8C
00 AC
00 CC
00 EC
01 0C
01 2C
00 0D
00 2D
00 4D
00 6D
00 8D
00 AD
00 CD
00 ED
01 0D
01 2D
00 0E
00 2E
00 4E
00 6E
00 8E
00 AE
00 CE
00 EE
01 0E
01 2E
00 0F
00 2F
00 4F
00 6F
00 8F
00 AF
00 CF
00 EF
01 0F
01 2F
00 11
00 31
00 51
00 71
00 91
00 B1
00 D1
00 F1
01 11
01 31
00 12
00 32
00 52
00 72
00 92
00 B2
00 D2
00 F2
01 12
01 32
00 13
00 33
00 53
00 73
00 93
00 B3
00 D3
00 F3
01 13
01 33
00 14
00 34
00 54
00 74
00 94
00 B4
00 D4
00 F4
01 14
01 34
00 15
00 35
00 55
00 75
00 95
00 B5
00 D5
00 F5
01 15
01 35
00 16
00 36
00 56
00 76
00 96
00 B6
00 D6
00 F6
01 16
01 36
00 17
00 37
00 57
00 77
00 97
00 B7
00 D7
00 F7
01 17
01 37
00 18
00 38
00 58
00 78
00 98
00 B8
00 D8
00 F8
01 18
01 38
00 19
00 39
00 59
00 79
00 99
00 B9
00 D9
00 F9
01 19
01 39
00 1A
00 3A
00 5A
00 7A
00 9A
00 BA
00 DA
00 FA
01 1A
01 3A
00 1B
00 3B
00 5B
00 7B
00 9B
00 BB
00 DB
00 FB
01 1B
01 3B
00 1C
00 3C
00 5C
00 7C
00 9C
00 BC
00 DC
00 FC
01 1C
01 3C
00 1D
00 3D
00 5D
00 7D
00 9D
00 BD
00 DD
00 FD
01 1D
01 3D
00 1E
00 3E
00 5E
00 7E
00 9E
00 BE
00 DE
00 FE
01 1E
01 3E
00 1F
00 3F
00 5F
00 7F
00 9F
00 BF
00 DF
00 FF
01 1F
01 3F
2-60
GMR-01
68P02901W43-P
23 Feb 2004
GCLK calibration
GCLK calibration
The GCLK must be calibrated only by fully trained GSM qualified personnel.
Do not attempt this procedure under any circumstances unless the
test equipment listed below is available.
This procedure is used to calibrate the GCLK in the field. The GCLK must be calibrated
when either of the following occur:
More than one frame slip per hour is observed at the OMC-R.
The GCLK calibration request alarm is observed at the OMC-R.
The GCLK cannot phase lock, and the LTA values are near their limits.
GCLK calibration can be carried out automatically using the CINDY


68P02901W43-P
23 Feb 2004
Rubidium clock standard.
Frequency counter.
BNC to 2 mm multicontact AG connector screened coaxial cable.
Non-ferrous tuning tool.
New calibration sticker(s).
2-61
GMR-01
GCLK calibration
Commands used
The following commands are used to calibrate the GCLK:
Function
Command
disp_equipment
state
disp_element
phase_lock_gclk <location>
Shows the status of the phase lock function. <location> is the site id.
chg_element
phase_lock_gclk <flag>
<location>
Turns the phase lock function on or off, where <flag> is 0" for off
and 1" for on, and <location> is the site id.
clear_gclk_avgs
<location>
Clears LTA values in memory for a specified GCLK.
Preparation for GCLK calibration

Before starting the procedure, consult the site specific documentation to determine the
BSC/BTS configuration and cage slot allocation.
Call processing cannot take place during calibration if GCLK redundancy is not provided.
Do not proceed until a suitable time has been agreed with the OMC-R.
Prior to carrying out the following calibration procedure, allow a 30 minute warm-up period
after switching on the GCLK to enable it to reach its operating temperature.
If the GCLK hardware is revision 9 or greater and the Fast GCLK Warmup feature
(gclk_qwarm_flag) is enabled, only 15 minutes will be needed for GCLK warm-up.
2-62
GMR-01
68P02901W43-P
23 Feb 2004
GCLK calibration
Use the following procedure to prepare for GCLK calibration:

Procedure 2-37 Prepare for GCLK calibration
1
Record the GCLK board serial number, present date, and date of last calibration
on the calibration record at the end of this section. Remove the old calibration
stickers from the GCLK front panels.
Connect the PC serial port A to the GPROC TTY port using the 9-way to 25-way
cable.

3
Start the terminal emulator program at the PC.
Connect the output from the 10 MHz standard to the reference input of the
frequency counter. Select external standard.
Connect the BNC connector of the coaxial cable to the frequency counter input
port. Connect the multicontact AG connector to the front panel of the GCLK
16.384 MHz output and earth.
Set the frequency gate time to 10 seconds and set the display to give 10 significant
digits. Note the current frequency and record it on the calibration form.
If GCLK redundancy is not provided, go straight toClearing GCLK LTA values.

If GLCK redundancy is provided check the clock status, one will be
BUSY-UNLOCKED (Master) the other will be ENABLED-UNLOCKED
(Slave).
Go toClearing GCLK LTA values to calibrate the ENABLED-UNLOCKED
(Slave) GLCK first.
Clearing GCLK LTA values

Use the following procedure to clear the GCLK Long Term Average (LTA) values:
Procedure 2-38 Clear GCLK LTA values
1
Check to see if phase lock is on. At the CUST MMI prompt, enter the command:
disp_element phase_lock_gclk <location>
Where:
<location> is 0 to 40, or bsc.
This gives the phase lock status of the site. 0 is shown for phase lock off and 1
is shown for phase lock on.
68P02901W43-P
23 Feb 2004
If phase lock at the site is on, turn it off. Enter the command:
chg_element phase_lock_gclk 0 <location>
To determine the GCLK device id, enter the command:

disp_equipment <location>
2-63
GMR-01
GCLK calibration
Procedure 2-38
Clear GCLK LTA values (Continued)
Check that phase lock for the GCLK is off. Enter the command:
state <location> GCLK <dev id> <dev id> <dev id>
Clear the GCLKvalues. Enter the command:

clear_gclk_avgs <location>
The system will respond with:
Enter the gclk_id:
Enter: 0 or 1.
This clears the LTA values for the specified GCLK
GCLK frequency adjustment procedure

Use the following procedure to adjust GCLK frequency:
Procedure 2-39
Adjust GCLK frequency
Using a non-ferrous tuning tool, adjust the potentiometer labelled FREQ ADJUST
on the GCLK. Turn the potentiometer clockwise to increase the frequency and
anticlockwise to decrease the frequency.
The GSM specified tolerance is 0.8 Hz. You should aim to achieve 10 times
this accuracy (i.e. 0.08 Hz). Frequency counter readings should be in the range
16.383999 92 MHz to 16.384 000 08 MHz.
If GCLK redundancy is not provided go to step 3.

If redundancy is provided, swap to the other GCLK using the command:
swap_devices <location> <GCLK> <act_dev_id1>
<act_dev_id2> <act_dev_id3> <GCLK> <standby_device_id1> <standby_device_id2> <standby_device_id3>
Where:
location is 0 or bsc
Repeat from step 3 in Clearing GCLK LTA values to step 1 above.
If phase locking of the GCLK(s) at the site is required, at the CUST MMI prompt
enter the command:
chg_element phase_lock_gclk 1 <location>
This turns the phase lock on for the specified site.

Place a new calibration sticker, indicating the date of calibration, over the
potentiometer labelled FREQ ADJUST on each calibrated GCLK.
2-64
GMR-01
68P02901W43-P
23 Feb 2004
GCLK calibration
Site restoration
Use the following procedure to restore the site after GCLK calibration:
Procedure 2-40 Restore site after GCLK calibration
1
Remove the frequency counter cable from the front panel 16.384 MHz connection
of the GCLK.
Remove the 9-way to 25-way cable from the front of the GPROC TTY port
Inform the OMC-R that site restoration is complete.
GCLK calibration record form

The GCLK calibration record form is shown below:
TESTERS NAMES
SITE NAME.................................
......................................................
SITE ID........................................
......................................................
SERIAL NUMBER
OF BOARD
68P02901W43-P
23 Feb 2004
DATE
DATE OF LAST
CALIBRATION
FREQUENCY
BEFORE
CALIBRATION
2-65
GMR-01
ExCell alarms check
ExCell alarms check
Follow the procedures described in this section to verify that the ExCell alarms function correctly.

The following test equipment is required to carry out the serial and alarm tests:
Krone tool.
Approved smoke canister.
Commands used
The following commands must be used to carry out the ExCell alarm tests:
Function
Command
enable_alarm
state
Preparation for the alarms check

Use the following procedure to prepare for ExCell alarms verification:
2-66
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 2-41
ExCell alarms check
Prepare for ExCell alarms verification
Ensure download has been completed.
Connect the serial A port on the PC to the master GPROC using the 9-way to
25-way cable.

3
At the CUST MMI prompt enter the password.
At the PC, enter the command:

enable_alarm 0
Check that PIX 0 is unlocked and busy. At the prompt enter the command:
state 0 EAS 000
Check that PIX 1 is unlocked and busy. At the prompt enter the command:
state 0 EAS 100
ExCell alarm list

The following ExCell alarms are tested:
68P02901W43-P
23 Feb 2004
Smoke alarm.
Overtemperature alarm.
Door open alarm.
Fan fail alarm.
Mains fail alarm.
Rectifier fail alarm.
Low dc voltage alarm.
Inverter fail alarm.
Miniature circuit breaker trip alarm.
Battery fault alarm.
Comms PSU fail alarm.
External alarm 0.
External alarm 1.
2-67
GMR-01
ExCell alarms check
External alarm 2.
External alarm 3.
Smoke alarm check procedure

Use the following procedure to verify the ExCell smoke alarm:
Procedure 2-42
Verify ExCell smoke alarm
Ensure that both the smoke sensors are not set (the red LED on each sensor isnot
lit). If one or both LEDs are lit, switch the cabinet control circuit breaker off then
on again to reset the sensors.
As directed by the instructions on the smoke canister, direct ajet of smoke at both
sensors. When both sensors are active the following message is displayed:
EAS ALARM: 20 0 0 0:40:Optocoupler 1
SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A
Severity: Critical Category: Environment
Date
Alarm Type: Fault Management Initiated Clear
ADDITIONAL INFO: Smoke Alarm
Switch the cabinet control circuit breakerto off then on again to reset the sensors.
Severity: Clear Category: Environment
Date
ADDITIONAL INFO:
Overtemperature alarm check procedure

Use the following procedure to verify the ExCell overtemperature alarm:
2-68
GMR-01
68P02901W43-P
23 Feb 2004
ExCell alarms check
Procedure 2-43 Verify ExCell overtemperature alarm

1
Press the control override button. The heat management system (HMS) display
should show a temperature of about 25 C.
Adjust the Adjust Test Temp control until the HMS display shows a temperature
between 65 C and 67 C. The overtemperature sensor lamp should light and the
following message should be displayed:
Date
ADDITIONAL INFO: Over Temperature
Adjust the Adjust Test Temp control until the HMS display shows a temperature
below 60 C. The overtemperature sensor lamp should light and the following
message should be displayed:
Date
ADDITIONAL INFO:
Door open alarm check procedure

Use the following procedure to verify the ExCell door open alarm:
Procedure 2-44 Verify ExCell door open alarm
1
Close the cabinet doors. The following message should be displayed:

Date
ADDITIONAL INFO:
Open any cabinet door. The following message should be displayed:

Date
ADDITIONAL INFO: Cabinet Door Open
68P02901W43-P
23 Feb 2004
2-69
GMR-01
ExCell alarms check
Fan fail alarm check procedure

Use the following procedure to verify the ExCell fan fail alarm:
Procedure 2-45
1
Verify ExCell fan fail alarm
Switch off any of the RCU or BSC fans. The following message should be
displayed:
Date
ADDITIONAL INFO: Fan Failure
Switch the fan on again. The following message should be displayed:

Date
ADDITIONAL INFO:
Mains fail alarm check procedure
This alarm is active when the ac mains input to all the rectifiers is interrupted. With
mains input to just one rectifier the alarm will remain inactive.
Use the following procedure to verify the ExCell mains fail alarm:
2-70
GMR-01
68P02901W43-P
23 Feb 2004
ExCell alarms check
Procedure 2-46 Verify ExCell mains fail alarm

1
Switch off the mains supply to all rectifiers. The following message should be
displayed:
Date
ADDITIONAL INFO: Mains Failure
Reconnect the mains supply to all rectifiers. The following message should be
displayed:
Date
ADDITIONAL INFO:
Rectifier fail alarm check procedure
This alarm is active when the ac mains input to a rectifier is interrupted.

Use the following procedure to verify the ExCell rectifier fail alarm:
68P02901W43-P
23 Feb 2004
2-71
GMR-01
ExCell alarms check
Procedure 2-47
1
Verify ExCell rectifier fail alarm
Switch off the mains supply to rectifier 1. The following message should be
displayed:
Date
ADDITIONAL INFO: Rectifier Failure
Reconnect the mains supply to all rectifiers. The following message should be
displayed:
Date
ADDITIONAL INFO:
Low dc voltage alarm check procedure

Use the following procedure to verify the ExCell low dc voltage alarm:
Procedure 2-48
1
Verify ExCell low dc voltage alarm
Remove the alarms fuse on the PSU meter panel. The following message should
be displayed:
Date
ADDITIONAL INFO: Low dc voltage
Replace the fuse. The following message should be displayed:

Date
ADDITIONAL INFO:
2-72
GMR-01
68P02901W43-P
23 Feb 2004
ExCell alarms check
Inverter fail alarm check procedure
Only carry out this test if an inverter is fitted.

Use the following procedure to verify the ExCell inverter fail alarm:
Procedure 2-49
1
Verify ExCell inverter fail alarm
witch off the mains supply to the inverter. The following message should be
displayed:
Date
ADDITIONAL INFO: Inverter Fail
Reconnect the mains supply to the inverter. The following message should be
displayed:
Date
ADDITIONAL INFO:
MCB trip alarm check procedure

Use the following procedure to verify the ExCell miniature circuit breaker (MCB) trip alarm:
68P02901W43-P
23 Feb 2004
2-73
GMR-01
ExCell alarms check
Procedure 2-50
1
Verify ExCell MCB trip alarm
Manually trip any MCB associated with the PSU. The following message should
be displayed:
Date
ADDITIONAL INFO: MCB Tripped
Reset the MCB. The following message should be displayed:

Date
ADDITIONAL INFO:
Battery fault alarm check procedure

Use the following procedure to verify the ExCell battery fault alarm:
Procedure 2-51
1
Verify ExCell battery fault alarm
Remove any fuse from the front of the battery box. The following message
should be displayed:
Date
ADDITIONAL INFO: Battery Fault
Replace the fuse. The following message should be displayed:

Date
ADDITIONAL INFO:
Comms PSU fail alarm check procedure

Use the following procedure to verify the ExCell comms PSU fail alarm:
2-74
GMR-01
68P02901W43-P
23 Feb 2004
ExCell alarms check
Procedure 2-52 Verify ExCell comms PSU fail alarm

1
Manually trip the MCB supplying the comms PSU module. The following
Date
ADDITIONAL INFO: Comms. PSU Failure
Reset the MCB. The following message should be displayed:

Date
ADDITIONAL INFO:
External alarm 0 check procedure

Use the following procedure to verify the ExCell external alarm 0:
Procedure 2-53 Verify ExCell external alarm 0
1
Insert a Krone peg into position 1 of the top Krone connector. The following
Date
ADDITIONAL INFO: External Alarm #0
Remove the Krone peg. The following message should be displayed:

Date
ADDITIONAL INFO:
68P02901W43-P
23 Feb 2004
2-75
GMR-01
ExCell alarms check

Procedure 2-54
1
Verify ExCell external alarm 1
Date

Date
ADDITIONAL INFO:

Procedure 2-55
1
Verify ExCell external alarm 2
Date

Date
ADDITIONAL INFO:
2-76
GMR-01
68P02901W43-P
23 Feb 2004
ExCell alarms check

Procedure 2-56 Verify ExCell external alarm 3
1
Date

Date
ADDITIONAL INFO:
68P02901W43-P
23 Feb 2004
2-77
GMR-01
DRCU fault identification
Follow these procedures to identify DRCU module faults without returning the unit to Motorola.
These procedures are also available as a quick reference card (catalogue number 68P02900W39).
Refer to the Test equipment, leads and plugs section earlier in this chapter for recommended test equipment.
Symptoms during normal operation

Go to the indicated procedure step for the following symptoms:
For this symptom ...
Go to step ...
If the codes and instances are incorrect on the local maintenance terminal (LMT)
P1
If the DRCU goes to sleep
P2
If only the DRCU goes to sleep and the alarm LED lights briefly
P3
If code loads CEB/DCB/RCB/SCB, EQ, or PA fail
P3
If the DRCU resets
P4
If a DRI alarm indicates a DRCU failure
P4
If there are bad timeslots or if reception quality is poor
P5
Symptoms during commissioning

Go to the indicated procedure step for the following symptoms:
For this symptom ...
Go to step ...
If the transmitter output is high or low
C1
If the transmitter output is zero
C1
If the transmitter output is unchangeable
C2
If, after bay level calibration, some or all channels read 80H
C3
If, after bay level calibration, some or all channels marginal
C4
2-78
GMR-01
68P02901W43-P
23 Feb 2004
Procedure during normal operation

Use the following procedure to identify DRCU module faults during normal operation:
Action
Step
P1
Lock the DRI.

Check DRIX and fibre optic cable by substitution.
Refit DRIX and fibre optic cable.
Recheck the codes and instances on the LMT.
If they are not correct.......................................................
If they are correct, continue:
P2
Go to step...
C6
Lock the DRI.

Remove the fibre optic cables from the DRCU.
Connect a 9 to 9-way cable from a PC serial port A to the DRCU
TTY port.
Start the terminal emulator program.
Manually reset the DRCU using the reset button.
Check that the calibration checksums and operational code versions
are correct.
If they are not corect........................................................
If they are correct continue.
Refit the fibre optic cables.
Unlock the DRI
If the DRCU goes into or remains in sleep
mode.................................................................................
C6
C6
If not, continue:
Run the failed test again.
If the test fails again.........................................................
If the DRCU passes this time, continue:
P3
Lock the DRI.

TTY port.
Unlock the DRI and verify that the DRCU reset sequence is
performed.
Wait until the CEB/DCB/RCB/SCB> prompt has been displayed
twice.
At the PC enter the third level password.
At the PC enter the command:
ALARM_ALL
If alarms are displayed.....................................................
If not allow the system to complete its configuration of the DRCU.
68P02901W43-P
23 Feb 2004
C6
C6
2-79
GMR-01
Action
Step
Go to step...

If are not displayed, continue:
Lock the DRI.
are correct.
C6
If they are not correct........................................................

First level password
Second level password
SWAP C 0
EXEC C 0
Third level password
SWAP E A
SWAP P 0
EXEC P 0
TEST
In test mode, watch the display for any alarms that might be
generated.
C6

If they are not displayed, at the PC enter the command:
ALARM_ALL
C6

If not, continue
C6
2-80
GMR-01
68P02901W43-P
23 Feb 2004
Step
Action
P4
Lock the DRI.

TTY port.
are correct.
P5
If they are not correct.......................................................

SWAP C 0
EXEC C 0
SWAP E A
SWAP P 0
EXEC P 0
TEST
In test mode, watch the display for any alarms that might be
generated.
C6
If alarms are displayed......................................................

If they are not displayed, at the PC enter the command:
ALARM_ALL
C6
If alarms are displayed .....................................................

If not, continue:
C6
Lock the DRI.

Carry out the bay level and cell site offset calibration again.
If the calibration cannot be carried out.............................
If the calibrations can be carried out, continue:
Check the DRIM, DRIX, and fibre optic cables by substitution.
Check the BSS code load is the latest version.
If necessary, contact the Motorola local office to see if any FYI or
CSB covers a similar failure............................................
P6
P7
68P02901W43-P
23 Feb 2004
Go to step...
P6
P7
Which calibration routine failed?

If the transmitter power calibration is incorrect................
If the bay level calibration is incorrect.............................
C1
C4

If the test fails again..........................................................
If the DRCU passes, continue:
C6
2-81
GMR-01
Procedure during commissioning

Use the following procedure to identify DRCU module faults during commissioning:
Action
Step
C1
Go to step...

TTY port.
ALARM_ALL
If not, continue:
Remove power from the DRCU.
Connect the combination of a 50 W dummy load and hybrid combiner
through a power meter to the output of the PA module (make a note
of all the losses).
Apply power to the DRCU.
SWAP C 0
EXEC C 0
SWAP E A
SWAP P 0
EXEC P 0
TEST
In test mode watch the display for any alarms that might be generated.
C6

If they are not, at the PC enter the command:
ALARM_ALL
C6

If not, at PC enter the command:
ACTIV P 0
TS A TX 0
Check the reading on the power meter (bearing in mind the losses
noted above) is within the limits 48.5 to 60.5 W (46.85 to 47.85
dBm).
If the power is within limits, the problem probably lies between the
DRCU output connector and the top of the cabinet.
C6
If the power is not within limits........................................
C6
2-82
GMR-01
68P02901W43-P
23 Feb 2004
Step
C2
68P02901W43-P
23 Feb 2004
Action
Go to step...

TTY port.
Check that the calibration checksums and code versions are correct.
Check that the PA operation code is version PA_0040.BIN or later.
C6
If the code is correct..........................................................

If the code is not correct, continue:
Connect a 9 to 25-way cable from a second PC serial port A to the
DRCU TTY port.
Unlock the DRI (PC2) and verify that the DRCU reset sequence is
performed (PC1).
Wait until the CEB/DCB/RCB/SCB> prompt has been displayed
twice.
At the PC enter the third level password.
ALARM_ALL
C5

If not, continue:
At the prompt enter the command:
FM TEST
HALT P 0
(The next two commands must be entered within five seconds of
each other.)
HALT C 0
TEST
Pause briefly to check that the DRCU does not reset.
At the prompt enter the command:
REVSWAP P U
Wait for 50 seconds for code to be swapped from RAM to EEPROM.
C6
If the swap was unsuccessful, lock the DRI.....................

If the swap was successful, continue:
C6
Lock the DRI....................................................................
C5
2-83
GMR-01
Action
Step
C3
Go to step...

TTY port. Start the terminal emulator program.
ALARM_ALL
If not, continue:
Rerun the bay level procedures for those channels that read 80H.
C6
If the channels are correct.................................................

If not, continue:
At the CEB/DCB/RCB/SCB> prompt enter the command:
TS A CHAN
Check that the displayed response has TS0 - TS7 on the same channel.
Use a channel frequency table to check that the signal generator is
set up correctly.
C5
If the signal generator is not set up correctly.....................
C5
If the signal generator is set up correctly..........................
C4
2-84
GMR-01
68P02901W43-P
23 Feb 2004
Step
C4
Action
Go to step...

TTY port. Start the terminal emulator program.
ALARM_ALL
If not, continue:
Remove power from the DRCU.
Connect a coaxial cable from the signal generator to the DRCU Rx
branch 1 input
Calculate the new signal generator output power using the formula:
Revised output = splitter/preselector gain + cable loss + nominal
generator output.
Where splitter/preselector gain is taken at 13.3 dBm and nominal
generator output is -65.5 dBm.
Apply power to the DRCU.
Check that the calibration checksums and code versions are correct.
C6

C6

SWAP C 0
EXEC C 0
SWAP E A
SWAP P 0
EXEC P 0
In test mode watch the display for any alarms that might be generated.
If they are not, at the PC enter the command:
ALARM_ALL
C6
C6
If they are not, rerun the bay level procedures using the revised signal
generator output power calculated above (ignore the RX_MATRIX
alarm).
Repeat the bay level procedures for both branches.
If not..................................................................................
68P02901W43-P
23 Feb 2004
C6
2-85
GMR-01
Action
Step
C5

If not.................................................................................
C6
Go to step...
C6
Power the DRCU down in a controlled manner by halting each

processor:
HALT E A
Record all details of the fault including the procedures used.
Return the DRCU for repair.
2-86
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
3
M-Cell2 and M-Cell6 optimization
This chapter provides information required for the hardware optimization of M-Cell2 and M-Cell6 equipment.
Before starting the hardware optimization, the equipment must be commissioned.
Hardware optimization of the M-Cell2 and M-Cell6 equipment consists of :
68P02901W43-P
23 Feb 2004
Checking the antenna VSWR and calibrating the transmit output power.
Calibrating the bay level offset tables.
Checking the 2.048 Mbit link.
Checking the serial connections, power supply module version and alarm status.
Calibrating the MCU (GCLK)
3-1
GMR-01
Introduction to M-Cell2 and M-Cell6 optimization
Introduction to M-Cell2 and M-Cell6 optimization
The following procedures are used for M-Cell2 and M-Cell6 optimization:
"TCU output power calibration and VSWR check" on page 3-7
"TCU900/1800/1900 bay level offset tables calibration" on page 3-22
"TCU-B VSWR and cellsite offset information" on page 3-41
"TCU-B VSWR and cellsite power calibration" on page 3-46
"TCU-B VSWR and cellsite power calibration for CCBs" on page 3-52
"TCU-B bay level offset tables calibration" on page 3-60
"Database equipage check" on page 3-76
"E1/T1 link check " on page 3-79
"PIX connections and alarms check" on page 3-82
"MCU (GCLK) calibration" on page 3-84
The M-Cell2 and M-Cell6 and all associated site equipment must be completely
optimized before integrating the base site for operation.

CINDY commissioning tool. Refer to the relevant CINDY documentation for details.
3-2
GMR-01
68P02901W43-P
23 Feb 2004
Test equipment and leads


Table 3-1 provides details of the test equipment required to perform the hardware
optimization procedures provided in this chapter.
Table 3-1
Hardware optimization equipment
Quantity
68P02901W43-P
23 Feb 2004
Description
Comments

(PC)
PCMCIA type 2 slot and serial comms port
Commercial terminal emulator

software

accuracy 1x10-10
Frequency counter

display. Hewlett Packard model HP5385A or
equivalent
Signal generator
Range 0 to 2 GHz
Digital multimeter
50 W minimum
3-3
GMR-01
Table 3-1
Hardware optimization equipment (Continued)

Description
Quantity
Comments
30 dB attenuator
100 W minimum
RF adaptor kit
RTLXQ98088 or equivalent
N to 7/16 inch adaptor
N to N barrel adaptor
2 m, calibrated
4 m, calibrated
9-way to 9-way TCU/MCU cable
PC to TCU/MCU. See Figure 3-1.
9-way to 25-way EQCP/RSS cable
PC to TCU-B. See Figure 3-2.
9-way to 25-way RS232 cable
BNC to 3-way connector coaxial cable
Frequency counter to GCLK. 2 m, part no.

3086144E01.
See Figure 3-3
PIX test lead
See Table 3-2.
Test mobile
ESD protection kit

GCLK calibration stickers
Test leads required


3-4
GMR-01
68P02901W43-P
23 Feb 2004
9-way to 9-way TCU/MCU cable

Figure 3-1
M-Cell 9-way to 9-way PC to TCU/MCU hardware optimization cable connections
PIN NUMBER
PIN NUMBER
4
6
7
8
4m SCREENED CABLE
9-WAY
D-TYPE
TCU/MCU CONNECTOR
9-WAY D-TYPE
PC COMMUNICATIONS PORT
9-way to 25-way EQCP/RSS cable

Figure 3-2
M-Cell 9-way to 25-way PC to TCU-B EQCP/RSS cable connections
PIN NUMBER
PIN NUMBER
EQCP PINS
6
5
5
RSS PINS
SELECTOR
SWITCH
9-WAY D-TYPE F
CONNECTOR
(PC COMMUNICATIONS
PORT)
68P02901W43-P
23 Feb 2004
4m SCREENED CABLE
25-WAY D-TYPE M
CONNECTOR
(TCU-B INTERFACE
PORT)
3-5
GMR-01
GCLK calibration cable

Figure 3-3 M-Cell 3-way to BNC MCU calibration cable connections
PIN NUMBER
EARTH
3
2
1
NOT USED
8 kHz OUTPUT
2m RG178 COAXIAL CABLE
50 OHM BNC CONNECTOR
FREQUENCY COUNTER
3-WAY
CONNECTORMCU
CALIBRATION PORT
PIX test lead connections

Table 3-2 shows pinout details to make a PIX test lead.
Table 3-2
Test plug pin connections

From PIN
To PIN
20
21
22
23
24
25
26
27
Not used
10
Not used
11
29
When making the PIX test lead:

Normally open (N/O) PIX inputs should be connected through a 50 ohm resistor.
Normally closed (N/C) PIX inputs should be connected through a 50 kohm resistor.
Details of N/O and N/C site inputs can be found in the equip_eas file
in the site commissioning database.
3-6
GMR-01
68P02901W43-P
23 Feb 2004
TCU output power calibration and VSWR check
TCU output power calibration and VSWR checks can be carried out automatically using the
These procedures aim to produce a radio that exhibits a flat frequency response over the GSM band.
In the case of the transmitter, this is performed by distributing the channels over three detector groups
(the detector being the device that maintains a steady output power level).
called cellsite power (CSPWR). During CSPWR the cabinet output power can be trimmed to
account for any abnormalities that may occur between the TCU and the top of the cabinet.
Setting output transmit power methods

Two methods for setting output transmit power are described in this section, one automatic and one manual:
Method 1 (automatic)
When the CSPWR command is typed at the SCP prompt, it effectively executes a small
script containing the following commands:
TS A CHAN 31
Set all timeslots to channel 31 (TCU900).
TS A CHAN 700
Set all timeslots to channel 700 (TCU1800/1900).
TS A TXP 00
MDLTR UC
Prior to executing the CSPWR command, it assumes that the synthesizers are
hopping (not locked) as is the case after the unit is powered up for the first time.
To alter the power, typing U increments or typing D decrements the power setting byte.
On completion, the command is exited and the appropriate power byte is saved to RAM.
68P02901W43-P
23 Feb 2004
3-7
GMR-01
Method 2 (manual)
To specify a particular channel (instead of defaulting to channel 31 or 700), two extra commands
must be entered prior to executing the CSPWR command, one to set the appropriate channel and the
other to lock the synthesizer. By locking the synthesizer, the channel selection made in the CSPWR
command will be ignored and the output is maintained at the frequency specified.
Test stages
There are four stages to the manual 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 the antenna. Repeat the following procedures for all
antennas on site, including receive antennas.

The following test equipment is required during the VSWR and output power calibration procedure:
9-way to 9-way TCU/MCU cable.
7/16 N-type adaptor.
50 ohm/100 W power attenuator.
3-8
GMR-01
68P02901W43-P
23 Feb 2004
Commands used
The commands used during the VSWR and output power calibration procedure, are listed below:
Function
BSS MMI command

lock_device
unlock_device
clear_cal_data

on a per DRI basis.
Function
TCU emulator command

SWAP
Swaps the code from one memory storage device to another (eg
RAM to ROM). It verifies that the source code contains valid code
and that the destination is in the proper state. If either of these
conditions are not met, an error is flagged.
EXEC
Executes the code currently in RAM (see swap command).
TS <T> CHAN XX
Timeslot set up.

Where: <T> = Timeslot No. or A = ALL
TS <T> TXPWR <nn>
Timeslot set up.

Where: <T> = Timeslot No. or A = ALL
nn = Attenuation level from max.
TEST
Places the TCU in test mode.
SYNTH 1
Uses one synth for all timeslots.
SYNTH NRM
Restore synth to normal working mode.
CSPWR
Cellsite power. Allows the cellsite power to be set to the maximum

output power.
Used with the CSPWR command to increase the power level by

a factor of 0.2 dB.
Used with the CSPWR command to decrease the power level by

a factor of 0.2 dB.
ESC (key)
Used to exit the CSPWR command and store the resulting offset to
RAM.
SAVE CAL TX
Used to store the resulting offset in ROM.
ACTIV
Changes the state of the requested processor from Active Standby

to Call processing.
68P02901W43-P
23 Feb 2004
3-9
GMR-01
Function
TCU emulator command
Displays the current state of the code for the processor requested.
state

MMI commands and may be entered in upper or lower case; the rest of the commands in this
list are all TCU (emulator) commands and case is as shown.
Preparation for output power calibration and VSWR check

Use the following procedure to prepare for the TCU output power calibration and VSWR check:
Procedure 3-1
Prepare for TCU output power calibration and VSWR check
Connect the 9-way to 9-way cable from the PC serial A port to the MCU MMI
port.
Enter the password at the CUST/MMI prompt.
Lock the DRI using the lock device command.
An RF hazard exists during DRI transmissions. As one

antenna may be connected to a number of DRIs, the lock
command must be repeated for all DRIs on the antenna
being worked on before connecting the wattmeter.
Enter:
Where:
5
Clear all the calibration data from the CM database to override the preserve
clear_cal_data # dri A * 0
This is required.
Connect the wattmeter, with the 50 W element in series, with the Tx port at the
top of the cabinet and the antenna. In the case of external high power duplexers,
connect the wattmeter with 50 W element to the output port of the high power
duplexer.
3-10
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-1 Prepare for TCU output power calibration and VSWR check (Continued)
7
Connect the 9-way to 9-way cable from the PC to the CNTRL PRCSR port on
the TCU.
Press the front panel RESET button to reset the TCU under test.
Enter the boot code passwords.
Automatic VSWR test procedure
The VSWR check requires full power to be transmitted through the antenna.
Ensure all personnel are clear of the antenna. Do not carry out this VSWR
test unless the antenna installation is complete.
Minimize the time that the radio is powered up to reduce the possibility
of interference with other users.
Use the following procedure to check the VSWR automatically:

Procedure 3-2
68P02901W43-P
23 Feb 2004
Check VSWR automatically
Disconnect the antenna and connect a dummy load to the wattmeter.
Enter the following commands at the SCP prompt:

SWAP C 0
EXEC C 0
level_3_password
TEST
CSPWR
Press ESC.
Replace the 50 W element in the wattmeter with a 5 W element and reverse the
direction on the wattmeter. Connect the wattmeter through to the antenna.
Enter the command:

CSPWR
3-11
GMR-01
Procedure 3-2 Check VSWR automatically (Continued)

7
Monitor and record the reverse power reading indicated on the wattmeter.
Readings should show reflected (reverse) power of no more than

1 W or 5% of forward power.
8
Press ESC.
The CSPWR command defaults to a midpoint channel number

(normally 31 or 700). If required, a manual process can be performed
as shown in Manual VSWR test procedure.
9
Reconnect the antenna.
Manual VSWR test procedure
The VSWR check requires full power to be transmitted through the antenna.
Ensure all personnel are clear of the antenna. Do not carry out this VSWR
test unless the antenna installation is complete.
Minimize the time that the radio is powered up to reduce the possibility
of interference with other users.
Use the following procedure to check the VSWR manually:
3-12
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-3 Check VSWR manually

1
Enter the following commands at the SCP prompt:

SWAP C 0
EXEC C 0
level_3_password
TEST
Enter the following two commands:

TS A CHAN nnn
SYNTH 1
Where:
A is all timeslots.
nnn is the specific channel number.
Enter the command:

CSPWR
Monitor and record the forward output power readings indicated on the wattmeter,
and then press ESC.
Enter the command:

SYNTH NRM
Once the SYNTH 1 command has been executed, theCSPWR and

ESC commands can be toggled between as many times as required.
The channel will still remain on the one originally defined in step 3.
Repeat step 3 through step 6 for the required number of channels.
7
Replace the 50 W element in the wattmeter with a 5 W element and reverse the
direction on the wattmeter. Connect the wattmeter through to the antenna.
Enter the command:

CSPWR
Monitor and record the reverse power readings indicated on the wattmeter, and
then press ESC.
Readings should show reflected (reverse) power of no more than

1 W or 5% of forward power.
10
68P02901W43-P
23 Feb 2004
3-13
GMR-01
Tx output power calibration procedure

Use the following procedure to calibrate the transmit output power:
Procedure 3-4 Calibrate Tx output power
1
Replace the 5 W element in the wattmeter with a 50 W element and connect the
Enter the two following commands:

TS A CHAN nnn
SYNTH 1
Where:
A is all timeslots (TS)
nnn is the specified channel number.
Enter the command:

CSPWR
Hit U or D until desired max is measured then
hit ESC, CTRL-Y or CTRL-C
Enter U or D to achieve the appropriate value in Table 3-3.

A message similar to the following example, indicating the TCU output power
and offset value, is displayed:
D
P: 43.8 dBm
Cell Site Offset:
1
When the required output level is achieved, press ESC

SAVE CAL TX
The cellsite offset can be checked by reading the memory location:

R F:15780
7
Repeat step 2 to step 6 until all TCUs have been tested.
3-14
GMR-01
68P02901W43-P
23 Feb 2004
Table 3-3
TCU achievable TX RF power output

Achievable value
TCU type
Twin band pass filter,

no duplexer
No combining
One stage combining
TCU900
40 W (46 dBm)
Not applicable
20 W (43 dBm)
TCU1800/1900
Not applicable
16 W (42.05 dBm)
8 W (39.05 dBm)
High Power
TCU1800/1900
Not applicable
32 W (45.05 dBm)
16 W (42.05 dBm)
All
Or the customer-specified value at the top of the cabinet, taking cable losses into
account.
M-Cell6 with CCB cellsite power setting

The Cavity Combining Block (CCB) combines the output of up to three radios to a common output, and up
to six radios by use of an additional CCB (extension). The CCB (extension) output is an input to the CCB
(output) for a single-antenna system. Every transmitted frequency is attenuated by approximately 3.5 dB
for a six cavity system and 2.7 dB for a three cavity system. The CCB is not available for M-Cell2.
All CCB commands are issued via the TTY port on a TCU.
An M-Cell6 can support one or two CCB modules. There is a minimum of one CCB control board. The
CCB control board is located at the front of the CCB beneath a screw down cover. If redundancy of the CCB
control board is provided, both CCB modules will be equipped with a CCB control board.
The CCB has an address which is defined in the database using the equip_device comb command.
The address can also be displayed by using the disp_equipment comb command.
The CCB control board has a set of eight DIP switches which are used to provide the binary
representation of the address defined in the database. If a single CCB control board is used, it must
be in position 0, or the right side of the cabinet viewed from the front. If two CCB control boards
are used, the one mounted on the right module (looking from the front) will normally be the master.
If this unit fails, the redundant unit will automatically assume control.
The initial main/standby relationship is defined from the power connection to the top panel of
the M-Cell6 cabinet. The two CCB control boards receive power from different pins in the
connector, this provides the main/ standby relationship. A fault or problem with the CCB control
board is indicated by a red LED, which can be viewed from above.
There is not a master/slave relationship as no CCB control board has any influence over the other. It
is a main/standby relationship where each CCB control board is equally aware of what is happening
with the CCB system, hence the ability for the standby CCB control board to take seamless
control in the event of a problem with the main CCB control board.
68P02901W43-P
23 Feb 2004
3-15
GMR-01
The CCB control board is sometimes referred to as the Transmit Antenna Transceiver
Interface Control Board (TATI Control Board or TCB).
Example:
If the combiner address is required to be 75, the DIP switches are set as in Table 3-4.
Table 3-4
TCU switch settings for example of value 75
Switch
On/off for value 75
off
on
off
off
on
off
on
on
Binary value of each

switch
128
64
32
16
If CCB control board redundancy is supported, the dip switches must be set
the same on both CCB control boards.
255, represented by the dip switches being all on, is not a valid address.
The CCB control board is equipped with a green LED to indicate the presence of power.
Cellsite power setting procedure

The following procedure details the necessary steps to perform the setting of the cellsite power on M-Cell6
sites when they are equipped with CCBs. The radio in slot 0 can be used to control all the cavities in the CCB.
Use the following procedure to set cellsite power:
3-16
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-5
Set cellsite power on M-Cell6 sites equipped with CCBs
Connect a PC to the TCU TTY port and put the radio into test mode.
Issue the full reset command to the CCB. At the SCP prompt, enter the command:
SEND EQCP A0 05 0A 02 <CCB control board address
00-FE> <cavity address> <checksum>
Where:
05 is the word count
0A is the reset command
02 is the byte count
CCB control board address is the address, in hex, .set by the CCB control board
DIP switches (seeTable 3-4).
cavity address is the address, in hex, of the cavity to be reset (see Table 3-5)
checksum is the low byte of the sum of all other values
For example, to perform a reset of cavity 0, on a CCB with address 254 decimal,
enter the command:
SEND EQCP A0 05 0A 02 FE 01 0B
The response should occur in under 12 seconds and begin with 09. The 09
indicates a reset response.
If OK the response is:
09 02 FE 00 0A
If not OK the response is:

09 02 FE FF 08
68P02901W43-P
23 Feb 2004
The TCU radios use channel 31 as the default value associated with the CSPWR
command.
If a different channel is required, enter the following commands with the radio in
test mode:
TS A CHAN nnn (where nnn represents the channel to use)
SYNTH 1
CSPWR.
3-17
GMR-01
Tuning CCB cavities

Cavities may be tuned individually or as a group from a single command. When tuning multiple cavities in a
single command, the channel spacing between cavities must be 800 kHz or four channels.
The cavities are addressed from a bitmap. The mapping follows the plan in Table 3-5.
Table 3-5
TCU cavity bitmap
MSB
LSB
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Reserved
Reserved
Cav 5
Cav 4
Cav 3
Cav 2
Cav 1
Cav 0
The reserved bits are always set to zero.

The channel number has a high and low byte as the CCB has the ability to handle EGSM frequencies.
The power level value is always set to zero.
Tuning a single CCB cavity

Use the following procedure and example to tune a CCB cavity from a single command:
Procedure 3-6 Tune a single CCB cavity
Enter the command:
SEND EQCP A0 <word count> 02 <byte count> <CCB control board address>
<cavity address> <channel high byte> <channel low byte> <power level>
<checksum low byte>
Example:
To tune the first cavity of the CCB with address 254 to channel 120 enter the command:
SEND EQCP 08 02 05 FE 01 00 78 00 7E
Where:
is:
08
is the parameter word count.
02
is the parameter download message ID.
05
is the number of bytes to follow.
FE
is the address 254 in hex.
01
is the cavity.
00
is the channel high byte.
78
is the channel low byte = 120.
00
is the power level - always 00.
7E
is the low byte of the checksum (02 + 05 +FE + 01 +

00 + 78 + 00).
The CCB responds within 7 seconds for a single cavity with the message:
ID 01, parameter download confirm
3-18
GMR-01
68P02901W43-P
23 Feb 2004
Tuning multiple CCB cavities

Use the following procedure and example to tune multiple CCB cavities:
Procedure 3-7 Tune multiple CCB cavities
Enter the command:
SEND EQCP A0 <word count> 02 <byte count> <CCB control board address>
<cavity address> <channel high byte> <channel low byte> <power level>
<checksum low byte>
The sequence <channel high byte> <channel low byte> < power level>
is repeated for each cavity until all cavities have been defined.
Example:
To tune all cavities starting with channel 60 for cavity 0 and incrementing the channel number by 4 for
subsequent cavities, and with the CCB having an address of 254, enter the command:
SEND EQCP A0 10 02 14 FE 3F 00 3C 00 00 40 00 00 44 00 00
48 00 00 4C 00 00 50 00 F7
Where:
is:
10
is the parameter word count.
02
is the command to tune cavities.
14
is the number of bytes to follow excluding checksum.
FE
is the CCB control board address.
3F
is the cavity bitmap (represents all 6 cavities).
00
is the channel high byte per cavity.
3C 40 44 48 4C 50
are the channel numbers low bytes.
00
is the power level per cavity.
7F
is the low byte of the checksum .
The CCB responds within 14 seconds for multiple cavities with the message:
ID 01, parameter download confirm
Site restoration
After all installed TCUs have been checked and calibrated, the site needs to be restored to
call processing mode. This is done in two stages:
68P02901W43-P
23 Feb 2004
RF output power check.
Returning the TCUs to call processing mode.
3-19
GMR-01
RF output power check

Use the following procedure to check the RF output power:
Procedure 3-8
Check RF output power
Remove the 9-way to 9-way cable from the CNTRL PRSCR port and connect
to the MCU MMI port.
Connect a wattmeter fitted with a 50 W element and a dummy load to the TX

port of the TCU to be tested.
Press the reset button on the TCU front panel
Unlock the DRI under test using the following commands:

state # dri a * 0
Where:
This returns the TCU to the Unlocked Busy state (as confirmed by the state
command).
Via the MMI, determine whether maximum BTS power output is set on the
database. Enter the command:
disp_element max_tx_bts X cell_number=a a a b b ccc dd
Where:
a is the mobile country code (MCC).
b is the mobile network code (MNC).
c is the locstion area code (LAC).
d is the cell ID.
Observe the value displayed; zero indicates maximum transmit power. Each
step decreases power by 2 dB.
Note the RF output reading on the wattmeter; it should be the same as the
maximum power set up in step 5 of Tx output power calibration procedure in
this section.
Lock the TCU. Enter the command:

Where:
Repeat step 2 to step 7 for all TCUs.
3-20
GMR-01
68P02901W43-P
23 Feb 2004
Returning the TCUs to call processing mode

Use the following procedure to return the TCUs to call processing mode:
Procedure 3-9
68P02901W43-P
23 Feb 2004
Return TCUs to call processing mode
Ensure the Tx ports of all TCUs tested are reconnected to their correct antenna
feeder cables.
Unlock all TCUs tested using the command detailed in step 4 of RF output
power check.
Enter the commands for each TCU to be unlocked.
Remove the 9-way to 9-way cable from the MCU MMI port.
Inform the OMC-R the VSWR and cellsite power calibration has been completed.
3-21
GMR-01
TCU900/1800/1900 bay level offset tables calibration
M-Cell2/6 TCU bay level offset tables calibration can be carried out automatically using the
This procedure is used to calibrate the bay level offset tables which compensate for the
losses or gains due to preselectors and RF cabling from the antenna inputs at the M-Cell2 or
M-Cell6 to the TCU900, TCU1800, or TCU1900 input.
This procedure applies only to the TCU900, TCU1800 and TCU1900.

All units are factory calibrated. This procedure is thus necessary only if one of the following changes occur:
A TCU is replaced.
RF front end equipment is changed.
The site is reconfigured.
High power duplexers are fitted.
The procedures contained in TCU900/1800/1900 bay level offset tables calibration are to
calibrate a single TCU. Repeat the procedures for all TCUs affected by the changes listed above.

Signal generator.
3-22
GMR-01
68P02901W43-P
23 Feb 2004
9-way to 25-way RS232 cable.
Commands used
The commands used to carry out the procedure are listed below:
Function
BSS MMI command

lock_device
Prevents the device being used
unlock_device
Frees the device for further use
clear_cal_data

on a per DRI basis
TCU TTY command
Function
SWAP C 0
Swaps DPC code from ROM to RAM and checks validity
EXEC C 0
Executes DPC code currently stored in RAM
SWAP E A
Swaps EQ code from ROM to all four EQUIPSs and checks validity
CONFGR E A
Sends call processing calibration tables to equaliser
TEST
Places the TCU into test mode
CAL BAY @1/@2
Calibrates the bay level receive equipment
EQTEST 0
Puts equalizer 0 into test mode and checks status
IQDCP 0
Passes the factory calibrated dc offset information stored in ROM to

EQDSP 0
AIC OUT
Disables automatic intermodulation compensation
TS A CHAN #
Sets all timeslots to channel #
TS A ANT #
Sets all timeslots to antenna #
R F:XX YY
Reads flash memory bay level data held at addresses XX to YY
SYNTH 1
Stops synthesizer switching with synthesizer 1 permanently on
68P02901W43-P
23 Feb 2004
3-23
GMR-01
Function
TCU TTY command

SYNTH NRM
Enables synthesizer switching into normal working
SAVE CAL BAY
Transfers Bay Level Calibration stored data in RAM to ROM
BAYDONE @N
Informs control processor that Bay Level Calibration is valid for

branch N and sets bay level flag
Function
TCU TSM port command

tcu_clock 0
Stops the TCU hunting between fibre A and fibre B and forces the
TCU to look only at fibre A.

2. The lock_device, unlock_device and clear_cal_data commands are BSS MMI commands
and may be entered in upper or lower case. TCU emulator or TCU TSM port commands must
be entered as shown. The first TCU password must be upper case.
Locking radio, dummy load and TCU reset

The radio has first to be locked, a dummy load fitted if there is no antenna connected, and
the TCU reset so that it is ready for bay level calibration.
Use the following procedure to prepare for TCU900/1800/1900 bay level calibration:
The two receive cables must be connected to the TCU at all times, as the cable connecting
the TCU RX IN 1 terminal carries signalling information to the IADU and the cable
connecting the TCU RX IN 2 terminal carries power feed to the DLNB.
Procedure 3-10
Prepare for TCU900/1800/1900 bay level calibration
Connect the 9-way to 9-way cable from the PC serial A port to MCU TTY port.
3-24
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-10
3
Prepare for TCU900/1800/1900 bay level calibration (Continued)

Enter the command:
Where:
4
Where:
If a Tx antenna is not connected to the TCU under test connect a 50 ohm 50 W

dummy load to the Tx port of the TCU under test.
Remove the 9-way to 9-way cable from the PC serial A port to MCU TTY port.
Reset the TCU using the front panel reset button.
Silencing PLL_LK alarm

With the TCU in test mode, and no redundant MCU or FOX fibre pair present, there will be a PLL_LK alarm
cycling on and off as the radio hunts between its fibre inputs for a reference. This may interfere with the CAL
BAY @n (n=1,2) command. The following procedure forces the radio to lock to fibre A, stopping the alarm.
If the BTS is equipped with a redundant MCU and both fibre pairs A and B are
connected then this procedure may be omitted.
Use the following procedure to silence the PLL_LK alarm:
68P02901W43-P
23 Feb 2004
3-25
GMR-01
Procedure 3-11
Silence the PLL_LK alarm
Connect a standard 9-way to 25-way RS232 cable from the PC serial A port
to the TCU TSM port.
Set up a terminal connection to this port at 9600 baud.
At the ROM prompt enter the command:

tcu_clock 0
Remove the 9-way to 25-way cable from the PC serial A port to the TCU TSM
port.
Bay level setting procedure

Use the following procedure to set the TCU to respond to bay level calibration:
Procedure 3-12
Set TCU to respond to bay level calibration
Connect the 9-way to 9-way cable from the PC serial A port to CNTRL PRCSR
port on the TCU.
Enter the boot passwords.

SWAP C 0
The system responds with the following:
Swap in completed O.K.

EXEC C 0
The current state of the Control Processor is Active
Standby.
The last reset was caused by hardware.
At the SCP prompt enter the command:.<LEVEL_3_PASSWORD> (different

from the RCU level 3 password)
SWAP E A
Swap in completed O.K.

CONFGR E A
Equalizer
Equalizer
Equalizer
Equalizer
#0
#1
#2
#3
configuration
configuration
configuration
configuration
3-26
GMR-01
successful
successful
successful
successful
68P02901W43-P
23 Feb 2004
Procedure 3-12 Set TCU to respond to bay level calibration (Continued)

7

TEST
AIC OUT
EQTEST 0
003D
Equalizer is now in Test Mode

IQDCP 0
0057
Equalizer has been configured with the DC Offsets
Branch1 RX1A bay level calibration procedure

Use the following procedure for bay level calibration of branch 1 RX1A:
68P02901W43-P
23 Feb 2004
3-27
GMR-01
Procedure 3-13
1
Connect the output of the signal generator to branch 1 of the antenna port at the
top of the cabinet for the TCU under test as indicated in Table 3-6.
As the IADU connects the TCU900 receive port to the receive

antenna via the DLNB, and there are up to three DLNBs per cabinet,
it is important to choose the correct number in the TS A ANT
command.
If RX path is via DLNB 0 then antenna is TS A ANT 1.
See Antenna identification diagrams in later pages for further
explanation.
The antenna number can also be found by using the disp_equipment # DRI a * 0
command. The number next to antenna_select is the antenna number.
2
Set the signal generator at a level of -65.2 dBm, to the first channel test frequency
shown in Table 3-7, Table 3-8 or Table 3-9.
If signal generator connection is made at a location away from the
top of the cabinet, make allowance for loss in the feeder cable to the
antenna port at the top of the cabinet, by increasing the -65.2 dBm
level.For example, if feeder cable loss is 4dBm, the signal generator
should be set to -61.2 dBm.
The High Power Duplexer should be considered part of the cabinet
for this connection.
3

TS A ANT 1

TS A CHAN #
Where:
# is the channel number as shown in Table 3-7, Table 3-8 or Table 3-9.

SYNTH 1
CAL BAY @1
0051 0005 28F4
Rx Bay Level Offset = F7
3-28
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-13

SYNTH NRM
When the synthesizer is left unlocked, the bay level figure can vary
as much as 1dB at certain frequencies. By locking the synthesizer
(using commands SYNTH 1 and SYNTH NRM this variation can
be reduced to 0.1 dB.
7
Repeat step 4 to step 6 for each signal generator test frequency in Table 3-7,
Table 3-8 or Table 3-9.
Transfer the bay level calibration figures to non-volatile TCU memory. At the
SCP prompt enter the command:
SAVE CAL BAY
Transfer of Calibration Data to Non-Volatile Storage
Complete
Table 3-6
Signal generator to TCU connection
TCU frequency
Non duplexer
configurations
PGSM
EGSM900
RX1 on relevant
DLNB.
ANTENNA/ANT port of medium or external high

power duplexer which is connected to RX1 on the
DLNB.
DCS1800
PCS1900
A on the relevant LNA.
ANTENNA/ANT port of duplexer which is connected

to A on the LNA.
Duplexer configurations
Any TCU within an M-Cell6 cabinet can be connected to any input signal. The IADU
switches the outputs of up to three DLNBs to up to six TCUs. An IADU in one cabinet can be
connected to an IADU in another cabinet via extension ports.
Test frequencies
Table 3-7 lists the GSM900 and EGSM900 test frequencies.
Table 3-7
68P02901W43-P
23 Feb 2004
GSM900 and EGSM900 test frequencies
Channel
Frequency (MHz)
Channel
Frequency (MHz)
979 (see note)
881.001
43
898.601
987 (see note)
882.601
51
900.201
995 (see note)
884.201
59
901.801
1003 (see note)
885.801
67
903.401
1011 (see note)
887.401
75
905.001
3-29
GMR-01
Table 3-7 GSM900 and EGSM900 test frequencies (Continued)

Channel
Frequency (MHz)
Channel
Frequency (MHz)
1019 (see note)
889.001
83
906.601
03
890.601
91
908.201
11
892.201
99
909.801
19
893.801
107
911.401
27
895.401
115
913.001
35
897.001
123
914.601
Channels 979 to 1019 apply to Extended GSM only.

Table 3-8 lists the DCS1800 test frequencies.
Table 3-8
DCS1800 test frequencies
Channel
Frequency (MHz)
Channel
Frequency (MHz)
516
1711.001
708
1749.401
524
1712.601
716
1751.001
532
1714.201
724
1752.601
540
1715.801
732
1754.201
548
1717.401
740
1755.801
556
1719.001
748
1757.401
564
1720.601
756
1759.001
572
1722.201
764
1760.601
580
1723.801
772
1762.201
588
1725.401
780
1763.801
596
1727.001
788
1765.401
604
1728.601
796
1767.001
612
1730.201
804
1768.601
620
1731.801
812
1770.201
628
1733.401
820
1771.801
636
1735.001
828
1773.401
644
1736.601
836
1775.001
652
1738.201
844
1776.601
660
1739.801
852
1778.201
3-30
GMR-01
68P02901W43-P
23 Feb 2004
Table 3-8
DCS1800 test frequencies (Continued)
Channel
Frequency (MHz)
Channel
Frequency (MHz)
668
1741.401
860
1779.801
676
1743.001
868
1781.401
684
1744.601
876
1783.001
692
1746.201
883
1784.401
700
1747.801
Table 3-9 lists the PCS1900 test frequencies.

Table 3-9 PCS1900 test frequencies
68P02901W43-P
23 Feb 2004
Channel
Frequency (MHz)
Channel
Frequency (MHz)
516
1851.001
668
1881.401
524
1852.601
676
1883.001
532
1854.201
684
1884.601
540
1855.801
692
1886.201
548
1857.401
700
1887.801
556
1859.001
708
1889.401
564
1860.601
716
1891.001
572
1862.201
724
1892.601
580
1863.801
732
1894.201
588
1865.401
740
1895.801
596
1867.001
748
1897.401
604
1868.601
756
1899.001
612
1870.201
764
1900.601
620
1871.801
772
1902.201
628
1873.401
780
1903.801
636
1875.001
788
1905.401
644
1876.601
796
1907.001
652
1878.201
804
1908.601
660
1879.801
3-31
GMR-01
Antenna identification diagrams

The following examples are intended to clarify how to identify the antenna number for each TCU.
Figure 3-4
Single M-Cell6 cabinet 2/2/2 configuration
CELL C
CELL B
CELL A
D
L
N
B
0
I
A
D
U
T
C
U
3
T
C
U
3
T
C
U
T
C
U
T
C
U
T
C
U
ANTENNA SELECT NUMBER
For cell A the receive antennas are connected to DLNB 0; these antennas are known as
antenna 1, so the timeslot command is TS A ANT 1.
For cell B the receive antennas are connected to DLNB 1; these antennas are known as
For cell C the receive antennas are connected to DLNB 2; these antennas are known as
3-32
GMR-01
68P02901W43-P
23 Feb 2004
Figure 3-5
Two M-Cell6 cabinets 4/4/4 configuration
CELL C
CELL A
CELL B
CABINET 2
CABINET 1
D
L
N
B
0
I
A
D
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
1
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
For cell A the receive antennas are connected to DLNB 0 in cabinet 1; these antennas are known
as antenna 1, so the timeslot command is TS A ANT 1.
For cell B the receive antennas are connected to DLNB 2 in cabinet 1 and extended to the IADU in
cabinet 2 (by using the extender module). The cabinet 1 transceivers see the antennas as antenna
3 and require the TS A ANT 3 timeslot command, and the cabinet 2 transceivers see the antennas
as antenna 1 and require the TS A ANT 1 timeslot command.
For cell C the receive antennas are connected to DLNB 2 in cabinet 2; these antennas are
known as antenna 3, so the timeslot command is TS A ANT 3.
68P02901W43-P
23 Feb 2004
3-33
GMR-01

Use the following procedure for bay level calibration of the second antenna port:
It may not be possible to calibrate all three antennas because there may not be
a DLNB or LNA fitted to every RX port.
Procedure 3-14
Set the signal generator to the first channel test frequency shown in Table 3-7,

TS A ANT 2

TS A CHAN #
Where:

SYNTH 1
CAL BAY @1
0051 0005 28F4

SYNTH NRM
Repeat step 4 to step 6 for each signal generator test frequency in Table 3-7,
SCP prompt enter the command
SAVE CAL BAY
Complete
3-34
GMR-01
68P02901W43-P
23 Feb 2004

Use the following procedure for bay level calibration of the third antenna port:
1
Set the signal generator to the first channel test frequency shown in Table 3-7,

TS A ANT 3

TS A CHAN #
Where:

SYNTH 1CAL BAY @1
0051 0005 28F4

SYNTH NRM
Repeat step 4 to step 6 for each signal generator test frequency listed in Table 3-7,
SCP prompt enter the command:
SAVE CAL BAY
Complete
68P02901W43-P
23 Feb 2004
3-35
GMR-01
Branch completion
The BAYDONE command completes the procedure for a branch
by setting a flag to indicate the calibration figures are correct.
Procedure 3-16
Complete branch 1 bay level calibration

BAYDONE @1
Transfer of Calibration Data to Non-Volatile Storage Complete
Branch 2 calibration
To calibrate bay level offset tables for branch 2, repeat the following procedures using connector RX2
for TCU900, or connector B for TCU1800/TCU1900 at the top of the cabinet:
Enter @2 instead of @1 in the cal bay and baydone commands.
Only one branch calibration is required in the special case of an M-Cell2 dual antenna/shared
radios (bow-tie). This is because each radio can be split in a bow-tie to either antenna, and
one measured branch will provide accuracy to within the GSM specification.

Use the following procedure to check that bay level calibration has been successful:
3-36
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-17 Check bay level calibration success

1
To verify that the bay level offset values have been stored in EPROM use the
read command with the required offset table location as an argument, the read
command locations are shown in Table 3-10 to Table 3-13 below, for example:
R F:153B6 153C5as in the case of a TCU900.
TCUs that cover only the GSM range, need only use the 16 locations per antenna
per branch shown in Table 3-10.
If the bay level calibration is successful, each appropriate table location will
contain valid offsets and not the factory default of 80.

uncalibrated antenna port and will result in error alarm
DRI 218:
Invalid Transceiver Calibration Data
being reported when the unit is unlocked. The calibration procedure

will have to be repeated after checking the configuration and RF
cables.
to the site.
3
Table 3-10
If the radio is suspected to be faulty, see next section Diagnostic check

procedure.
GSM900 frequency offset addresses

Antenna
Locations
F: 15386 15395
F: 153B6 153C5
F: 153E6 153F5
F: 15416 15425
F: 15446 15455
F: 15476 15485
TCUs that cover the EGSM range, store offsets at 22 locations in each memory area per antenna
per branch. As the read command allows a maximum of 16 locations to be read at one time, each
memory area has to use the read command twice, as shown in Table 3-11.
68P02901W43-P
23 Feb 2004
3-37
GMR-01
Table 3-11
EGSM900 frequency offset addresses

Antenna
Locations
First read
Second read
F: 15380 1538F
F: 15390 15395
F: 153B0 153BF
F: 153C0 153C5
F: 153E0 153EF
F: 153F0 153F5
F: 15410 1541F
F: 15420 15425
F: 15440 1544F
F: 15450 15455
F: 15470 1547F
F: 15480 15485
Note: The lowest 6 locations for each antenna apply to Extended GSM only
DCS1800/PCS1900 TCUs require the read command to be used three times per antenna
per branch, as shown in Table 3-12 and Table 3-13.
Table 3-12 DCS1800 frequency offset addresses
Antenna
Locations
First read
Second read
Third read
RX1A Antenna 1 (A)
F: 15380 1538F
F: 15390 1539F
F: 153A0 153AE
RX2A Antenna 2 (A)
F: 153B0 153BF
F: 153C0 153CF
F: 153D0 153DE
RX3A Antenna 3 (A)
F: 153E0 153EF
F: 153F0 153FF
F: 15400 1540E
RX1B Antenna 1 (B)
F: 15410 1541F
F: 15420 1542F
F: 15430 1543E
RX2B Antenna 2 (B)
F: 15440 1544F
F: 15450 1545F
F: 15460 1546E
RX3B Antenna 3 (B)
F: 15470 1547F
F: 15480 1548F
F: 15490 1549E
Table 3-13 PCS1900 frequency offset addresses

Antenna
Locations
First read
Second read
Third read
RX1A Antenna 1 (A)
F: 15380 1538F
F: 15390 1539F
F: 153A0 153A4
RX2A Antenna 2 (A)
F: 153B0 153BF
F: 153C0 153CF
F: 153D0 153D4
RX3A Antenna 3 (A)
F: 153E0 153EF
F: 153F0 153FF
F: 15400 15404
RX1B Antenna 1 (B)
F: 15410 1541F
F: 15420 1542F
F: 15430 15434
RX2B Antenna 2 (B)
F: 15440 1544F
F: 15450 1545F
F: 15460 15464
RX3B Antenna 3 (B)
F: 15470 1547F
F: 15480 1548F
F: 15490 15494
3-38
GMR-01
68P02901W43-P
23 Feb 2004

If it is suspected that a bay level calibration problem is caused by the TCU, then a diagnostic check
can be made by performing a bay level calibration on the TCU alone.
Procedure 3-18
Diagnostic check for TCU bay level calibration
Set the signal generator to -55 dBm plus lead loss to simulate a gain of 10 dB.
Connect the signal generator directly to branch 1 or 2 on the TCU.
Ensure a TCU is switched to SCU mode before connection

to RX2.In TCU mode the RX2 inner is at +12 V dc to power
the DLNB in M-Cell equipment.A signal source may be
damaged by taking +12 V dc in its RF output.
3
Follow the bay level calibration procedure for each branch:
Ensure the mode switch is returned to the TCU position on

completion of testing.
4
The range 97 - D3 used in step 4 applies to TCU diagnostic checks

figures.
If the values are correct, then the TCU is working correctly and any fault will
probably be in the cabinet front end cables, cable connections or LNA or DNLB.If
the offsets are outside this range, the TCU is faulty and should be returned.
68P02901W43-P
23 Feb 2004
3-39
GMR-01
Site restoration
Use the following procedure to restore the site after the bay level calibration procedure is complete:
Procedure 3-19
Restore site after TCU900/1800/1900 bay level calibration
Remove the 9-way to 9-way cable from the CNTRL PRSCR port on the TCU.
Connect the 9-way to 9-way cable from the PC serial A port to a MCU TTY port
Press the reset button on the front panel of the TCU.
Enter the command:

Where:
The TCU is now in the UNLOCKED_BUSY state.
Enter the command:

disp_act_alarm # dri a * 0
Where:
Confirm that there is no DRI 218 alarm.
If a DRI 218 alarm is seen, the entire bay level calibration procedure
must be repeated.
7
Remove the 9-way to 9-way cable from the MCU TTY port.
3-40
GMR-01
68P02901W43-P
23 Feb 2004
TCU-B VSWR and cellsite offset information
TCU-B cellsite power calibration and VSWR checks can be carried out automatically using the
The TCU-B can only be used with BSS software release 1.5.1.6 onwards.
There is no DCS1800/PCS1900 version of TCU-B.
The TCU-B cannot be used as an SCU.
These procedures aim to produce a radio that exhibits a flat frequency response over the GSM band.
In the case of the transmitter, this is performed by distributing the channels over three detector groups
(the detector being the device that maintains a steady output power level).
In the field, the procedure for setting the transmit output power involves using a set of commands called cellsite
power (CSPWR). During CSPWR the user can trim the cabinet output power to account for any abnormalities
that may occur between the TCU-B and the top of the cabinet. The offset is effectively subtracted from the
requested power level so that a steady output is maintained at the top of the cabinet whatever channel is selected.
There are two sets of procedures available for checking VSWR and cellsite power:
Normal TCU-B VSWR and cellsite power calibration
TCU-B VSWR and cellsite power calibration for CCBs
The Preparation for output power calibration and VSWR check procedure at the end of this section
should be completed before attempting the VSWR and cellsite power calibration procedures.
Test stages
There are four stages to the procedure:
68P02901W43-P
23 Feb 2004
Preparing for test.
Checking the VSWR.
Calibrating the transmit output power.
3-41
GMR-01
Restoring the site.
VSWR checks ensure correct antenna matching and can prove the
serviceability of the antenna. Repeat the following procedures for all
antennas on site, including receive antennas.

The following test equipment is required during the VSWR and output power calibration procedure:
9-way to 25-way EQCP/RSS cable.
7/16 N-type adaptor.
50 ohm/100 W power attenuator.
All test equipment and test leads must be calibrated annually

by a recognized laboratory. Test equipment and test leads
must not be calibrated in the field.
3-42
GMR-01
68P02901W43-P
23 Feb 2004
Commands used
The commands used to carry out the VSWR and output power calibration procedure are listed below:
Function
BSS MMI command

ins_device
Initializes the device, bringing it into service.
lock_device
unlock_device
clear_cal_data

on a per DRI basis
tcu_clock 0
Stops the TCU-B hunting between link A and link B and forces the
TCU-B to look only at link A.
Function
TCU-B TTY command

TEST
Places the TCU-B in test mode.
ACT C
Activates the Control Processor.
BBH ALARM OFF
Inhibits the BBH alarm.
CSPWR
Cellsite power. Allows the cellsite power to be set to the maximum

output power.
HALT C
Stops the Control Processor.
TS <T> CHAN XXX
Timeslot set up.

Where: <T> = Timeslot No or A = ALL
XXX = ARFCN to tune Timeslot to.
TS <T> TXPWR <nn>
Timeslot set up.

Where: <T> = Timeslot No or A = ALL
nn = Attenuation level from max.
Used with the CSPWR command to increase the power level by

a factor of 0.2dB.
Used with the CSPWR command to decrease the power level by

a factor of 0.2dB.
ESC (key)or CTRL-Y or CTRL-C
Used to exit the CSPWR command and store the resulting offset to
RAM.
WRENB
Write enables the FLASH EPROM.
SAVE CAL TX
Used to store the resulting offset in FLASH EPROM.
WRPTC
Write protects the FLASH EPROM.
FR TX
Reads Tx offset for FLASH EPROM.
MR TX
Reads Tx offset for RAM.
68P02901W43-P
23 Feb 2004
3-43
GMR-01
Function
TCU-B TTY command

SEND EQCP A0 <WC>
Emulates Combiner Control Processor messaging.

Where: <WC> is the parameter word count.

2. BSS MMI commands may be entered in upper or lower case. RSS MMI or TCU-B
(emulator) commands must be entered in case as shown.
Preparation for output power calibration and VSWR check

Use the following procedure to prepare for TCU-B output power calibration and VSWR check:
Procedure 3-20
Prepare for TCU-B output power calibration and VSWR check
If CCBs are fitted, set all DIP switches on the CCB control board to zero
(thisassists programming and checksum calculations).
At the MMI-RAM> prompt enter the command:

ins_device # dri a *
Where:
* is DRI number on the antenna.
The radio must be brought into service as there is no Flash EPROM

storage of code at the radio control processor level.
If a connection to the BSC is not available a PCMCIA commissioning
card must be used.
3-44
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-20 Prepare for TCU-B output power calibration and VSWR check (Continued)
5
Wait for the radio to finish initializing, then lock the DRI using the lock device
command.
An RF hazard exists during DRI transmissions. As one

antenna may be connected to a number of DRIs, the lock
command must be repeated for all DRIs on the antenna
being worked on before connecting the wattmeter.
Enter the command:
lock_device # dri a *
Where:
For ease of calibration, all TCU-Bs in a cell should be initialized and

then locked. Always lock the transceiver providing the BCCH last, as
this prevents the BCCH being switched to alternate transceivers.
6
clear_cal_data # dri A * 0
Where:
68P02901W43-P
23 Feb 2004
Connect port COM1 on the PC to the TTY Interface port on the transceiver using
the 9-way to 25-way RSS cable.
At the MMI-ROM prompt enter the command:

tcu_clock 0
Remove the 9-way to 25-way RSS cable from the transceiver and replace it with
the 9-way to 25-way EQCP cable.
3-45
GMR-01
TCU-B VSWR and cellsite power calibration
Two methods available for normal VSWR checking are described in this section:
VSWR method 1(automatic)

When typing the CSPWR command at the EQCP prompt, it effectively executes a
small script containing the following commands:
TS A CHAN 31
Set all timeslots to channel 31(TCU900 and TCU-B)
TS A CHAN 700
Set all timeslots to channel 700(TCU1800/1900)
TS A TXP 00
Set all timeslots to full power
MDLTR UC
Turn the modulation off
Prior to executing the CSPWR command, it assumes that the synthesizers are in normal
mode (not locked), as is the case after the unit is powered up for the first time.
Although embedded in the CSPWR script, the TS a CHAN 700 command

is ignored by the TCU-B VSWR calibration procedure.
VSWR method 2 (manual)

To allow a particular channel to be specified (instead of defaulting to channel 31 or 700)
additional commands rather than CSPWR must be entered. One command sets the appropriate
channel and the other switches the TCU-B output power on and off.
Automatic forward output power test procedure

The first method for normal VSWR checking uses automatic channel selection. The CSPWR
command automatically selects a midpoint channel number (channel 31 or 700), but if required
a manual process can be performed as shown in method 2.
Use the following procedure to automatically check the transmission path forward output power:
3-46
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-21
Automatic check for Tx forward output power
Disconnect the antenna.Fit a dummy load to the wattmeter, ensure a 50 W

element is fitted and connect the wattmeter to the Tx output.
At the EQCP prompt enter the command:

.GSMFW
TEST
ACT C
BBH ALARM OFF
CSPWR
Press ESC or CTRL-Y or CTRL-C.
Automatic reverse power test procedure
Full power is transmitted during VSWR checks. Ensure all personnel are clear of
the antenna. Do not carry out this check unless antenna installation is complete.
To reduce the possibility of interference with other users, minimize

the time that the radio is powered up.
Use the following procedure to automatically check the transmission path reverse power:
Procedure 3-22
68P02901W43-P
23 Feb 2004
Automatic check for Tx reverse power

Remove the dummy load and connect the wattmeter through to the antenna.

CSPWR
3-47
GMR-01
Procedure 3-22
4
Automatic check for Tx reverse power (Continued)
Readings should show reflected (reverse) power of no more than 5%

of the forward power at the point of measurement, but less than 1W.
5

HALT C
Remove the wattmeter and reconnect antenna.
Manual forward output power test procedure

The second method for normal VSWR checking allows the manual selection of a channel.
Use the following procedure to manually check the transmission path forward output power:
Procedure 3-23
Manual check for Tx forward output power


.GSMFW
TEST
ACT C
BBH ALARM OFF
Enter the following command:

TS A CHAN nnn
Where:
A is all timeslots (TS).
nnn is the specifed channel number.
To switch the power on, enter the following command:

TS A TXPWR 00
Where:
00 is the maximum output power.
3-48
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-23 Manual check for Tx forward output power (Continued)

5
To switch the power off, enter the following command:

TS A TXPWR FF
Where:
FF is zero output power.
Manual reverse power test procedure

Use the following procedure to manually check the transmission path reverse power:
Procedure 3-24 Manual check for Tx reverse power
68P02901W43-P
23 Feb 2004

To switch the power on, enter the command:

TS A TXPWR 00
3-49
GMR-01
Procedure 3-24 Manual check for Tx reverse power (Continued)

4

of the forward power at the point of measurement, but less than 1 W.
5
To switch the power off, enter the command:

TS A TXPWR FF
Repeat step 3 to step 5 for the required number of channels.

HALT C
Remove the wattmeter and reconnect the antenna.
Output power calibration procedure

Use the following procedure to calibrate TCU-B transmit output power:
Procedure 3-25
Calibrate TCU-B Tx output power


.GSMFW
TEST
ACT C
BBH ALARM OFF

CSPWR

Enter U or D to adjust the TCU-B Tx power to achieve the appropriate value, as

detailed in Table 3-14.
As U or D is typed, a message similar to the following example, indicating the
TCU-B output power and offset value, is displayed:
D
P: 43.8 dBm
Cell Site Offset:
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C.
3-50
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-25
Calibrate TCU-B Tx output power (Continued)
At the EQCP prompt enter the commands:

HALT C
WRENB
SAVE CAL TX
WRPTC
The cellsite offset can be checked by reading the memory location

using:
FR TX to verify writes to FLASH.
MR TX to verify writes to RAM.
7
Repeat step 1 to step 6 until all transceivers have been calibrated.
Remove the wattmeter and reconnect the antenna.
Use the Site restoration procedures to return the site to service.
Table 3-14
Type

no duplexer
No combining
One stage combining
TCU-B
40 W (46 dBm)
Not applicable
20 W (43 dBm)
All
68P02901W43-P
23 Feb 2004
TCU-B achievable Tx RF power output
Or the customer-specified value at the top of the cabinet, taking cable losses into account.
3-51
GMR-01
TCU-B VSWR and cellsite power calibration for

CCBs
The Cavity Combining Block (CCB) combines the output of up to three radios to a common output, and up
to six radios by use of an additional CCB (extension). The CCB (extension) output is an input to the CCB
(output) for a single-antenna system. Every transmitted frequency will be attenuated by approximately 3.5 dB
for a six cavity system and 2.7 dB in a three cavity system. The CCB is not available for M-Cell2.
All CCB commands are issued via the TTY port on a TCU-B.
An M-Cell6 can support up to two CCB modules. There is a minimum of one CCB control board.
The CCB control board is located at the front of the CCB beneath a screw down cover. If redundancy
of the CCB control board is provided, both CCB modules will be equipped with a CCB control board.
The CCB has an address which is defined in the database using the equip_device COMB command.
The address can also be displayed by using the disp_equipment COMB command.
The CCB control board has a set of eight DIP switches which are used to provide the binary
representation of the address defined in the database. These switches have all been set to zero in
the Preparing for test procedure. Once the cellsite power has been set the DIP switches should
be returned to positions for the address defined in the database.
Example of DIP switch setting

If the combiner address is required to be 75 (hexidecimal 4B), the DIP switches will be set as Table 3-15.
Table 3-15
TCU-B CCB switch settings for example of 75

Switch
On/off for value 75
off
on
off
off
on
off
on
on
Binary value of each switch
128
64
32
16
3-52
GMR-01
68P02901W43-P
23 Feb 2004
If CCB control board redundancy is supported, the dip

switches must be set the same on both CCB control boards.
255, all dip switches set to the on position, is not a valid address.
CCB control board details

The CCB control board is equipped with a green LED to indicate the presence of power.
If a single CCB control board is used it must be in position 0, or the right of the cabinet as viewed from the front.
If two CCB control boards are used, the one mounted on the right, looking from the front, will normally be
the master. If this unit fails, the redundant unit will automatically assume control. The initial main/standby
relationship is defined from the power connection to the top panel of the M-Cell6 cabinet. The two CCB
control boards receive power from different pins in the connector, this provides the main/ standby relationship.
A fault or problem with the CCB control board is indicated by a red LED, which can be viewed from above.
There is not a master/slave relationship as no CCB control board has any influence over the other. It
is a main/standby relationship where each CCB control board is equally aware of what is happening
with the CCB system, hence the ability for the standby CCB control board to take seamless
control in the event of a problem with the main CCB control board.
Calibration procedures
The following procedures are used for VSWR and cellsite calibration of M-Cell6 cabinets
equipped with TCU-Bs and CCB RF combiners:
CCB cavities tuning procedure
VSWR calibration procedure
Cellsite power calibration
Parking the CCB cavities
The four calibration procedures should be completed sequentially, and without pause, for each radio.
Failure to do so could result in the associated CCB being parked on the wrong channel.
68P02901W43-P
23 Feb 2004
3-53
GMR-01

The following procedure details the steps necessary to tune the cavities in preparation for
the VSWR and cellsite power calibration. The TCU-B radios use channel 31 as the default
value associated with the CSPWR command.
Use the following procedure to tune each radio in turn:
Procedure 3-26
Tune CCB cavities

Connect a PC to the TCU-B TTY interface port.

GSMFW
TEST
ACT C
BBH ALARM OFF
Issue the full tuning command to the CCB as detailed in Table 3-16.
To tune cavity 0, at the EQCP prompt enter the command:
SEND EQCP A0 08 02 05 00 01 00 1F 00 27
Where:
08 is the parameter word count.
02 is the parameter download message ID.
05 is the number of bytes to follow, excluding final checksum.
00 is the CCB address of the cavity to be tuned.
01 is the hex value of the cavity to be tuned (set for cavity 0).
00 is the channel high byte.
1F is the channel low byte (set for channel 31).
00 is the power level always 00.
27 is the low byte of the checksum (02 + 05 + 00 + 01 + 00 + 1F + 00).
The response should occur in under 12 seconds and begin with 01.
A typical response, if OK, is:
01 04 00 01 00 00 06
A typical failure response is:

F1 0B 00 A0
followed by a repetition of the input bytes
3-54
GMR-01
68P02901W43-P
23 Feb 2004
Table 3-16
TCU-B CCB cavity tuning commands
Cavity to be tuned
Cavity tuning command
02
05
00
01
00
1F
00
27
02
05
00
02
00
1F
00
28
02
05
00
04
00
1F
00
2A
02
05
00
08
00
1F
00
2E
02
05
00
10
00
1F
00
36
02
05
00
20
00
1F
00
46

Use the following procedure to check the VSWR of the transmission path:
Procedure 3-27 Check Tx VSWR
68P02901W43-P
23 Feb 2004

CSPWR
Monitor and record the forward power readings indicated on the wattmeter.


CSPWR
3-55
GMR-01
Procedure 3-27
7
Check Tx VSWR (Continued)
Monitor and record the reverse power reading indicated on the wattmeter.

of the forward power at the point of measurement, but less than 1 W
.If the ratio of the forward and reverse readings is unacceptable,
8

Use the following procedure to calibrate the cellsite power:
Procedure 3-28
1
Calibrate cellsite power

CSPWR
Enter U or D to adjust the TCU-B Tx power to achieve the appropriate value, as

detailed in Table 3-17.
As U or D is typed,a message similar to the following example, indicating the
TCU-B output power and offset value, is displayed:
D P: 43.8 dBm Cell Site Offset:
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C.
Save the transmit power calibration. At the EQCP prompt enter the commands:
HALT C
WRENB
SAVE CAL TX
WRPTC
3-56
GMR-01
68P02901W43-P
23 Feb 2004
Table 3-17
TCU-B CCB achievable Tx RF power output

Achievable value
Type

no duplexer
No combining
TCU-B
40 W (46 dBm)
Not applicable
All
One stage combining

20 W (43 dBm)
Or the customer-specified value at the top of the cabinet, taking cable losses into account.
Parking the CCB cavity

Park the cavity to prevent cavity interference using the following procedure and example
to issue the full parking command to the CCB cavity as detailed in Table 3-18:
Procedure 3-29 Park CCB cavities
To park a CCB cavity, enter the following command:

SEND EQCP A0 <word count> C2 <byte count> <CCB address> <cavity
address> <checksum low byte>
Example: To park CCB cavity 0, at the EQCP prompt enter the command:
SEND EQCP A0 05 C2 02 00 01 C5
Where:
Table 3-18
is:
05
the parameter word count.
C2
the parameter download message ID.
02
the number of bytes to follow, excluding final checksum.
00
the CCB address (as set on the DIP switches).
01
the hex value of the address of the cavity to be tuned.

(set for cavity 0)
C5
the low byte of the checksum (C2 + 02 + 00 + 01).
TCU-B CCB cavity parking commands
Cavity to be parked
68P02901W43-P
23 Feb 2004
Cavity parking command
C2
02
00
01
C5
C2
02
00
02
C6
C2
02
00
04
C8
C2
02
00
08
CC
C2
02
00
10
D4
C2
02
00
20
E4
3-57
GMR-01
Calibration procedures for remaining cavities

Repeat the following calibration procedures until all transceivers have tuned the CCB cavity they
are connected to, and the Tx output power has been calibrated:
Parking the CCB cavity
When all CCB caviteis have been tuned, remove the wattmeter and reconnect the antenna.
Use the Site restoration procedure to return the site to service.
Site restoration
After all installed TCU-Bs have been checked and calibrated, perform the following steps to
restore the site. Restoration of the site is done in two stages:
RF output power check.
Returning the TCU-Bs to call processing mode.
Rf output power check

Use the following procedure to check RF output power:
Procedure 3-30
Check RF outut power
Remove the 9 to 25-way EQCP cable from the TTY port and connect a 9 to
9-way cable to the MCU MMI port.
Disconnect the antenna. Fit a dummy load to the wattmeter, ensure a 50 W

element is fitted and connect it to the Tx output.
Return the DIP switches on the CCB control boards to their original positions.
Press the reset button on the front panel of the TCU-B under test.
3-58
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-30 Check RF outut power (Continued)

5
Unlock the DRI under test using the following commands:

unlock_device # dri a *
state # dri A *
Where:
This forces the TCU-B to enter the Unlocked Busy state (as confirmed by the
state command).
Monitor and record the wattmeter reading.
Lock the TCU-B by entering the following commands

lock_device # dri a *
Where:
Repeat step 4 to step 7 for all DRIs
Returning the TCU-Bs to call processing mode

Use the following procedure to return the TCU-Bs to call processing mode:
Procedure 3-31
68P02901W43-P
23 Feb 2004
Return TCU-Bs to call processing mode
Remove the wattmeter and reconnect the antenna lead to the TX port.
Unlock all DRIs tested using the command detailed in step 5 of RF output
power check.
Remove the 9-way to 9-way cable from the MCU MMI port.
Inform the OMC the VSWR and cellsite power calibration has been completed.
3-59
GMR-01
TCU-B bay level offset tables calibration
M-Cell2/6 TCU-B bay level offset tables calibration can be carried out automatically using the
This procedure is used to calibrate the bay level offset tables which compensate for the losses or gains due to
preselectors and RF cabling from the antenna inputs at the M-Cell2 or M-Cell6 to the TCU-B input.
This procedure applies only to the TCU-B and can only be used with
software release 1.5.1.6 onwards.
All units are factory calibrated. This procedure is only necessary if one of the following changes occur:
A TCU-B is replaced.
RF front end equipment is changed.
The site is reconfigured.
High power duplexers are fitted.
The procedures contained in TCU-B bay level offset tables calibration are to calibrate a single
TCU-B. Repeat the procedures for all TCU-Bs affected by the changes listed above.

Signal generator.
3-60
GMR-01
68P02901W43-P
23 Feb 2004
9-way to 25-way EQCP cable.
Commands used
The following table lists the commands for the bay level calibration procedure:
Function
BSS MMI command

ins_device
Initializes the device, bringing it into service
lock_device
unlock_device
Frees the device for further use
clear_cal_data

specified radio unit on a per DRI basis
Function
TCU-B emulator TTY command

TEST
Places the TCU-B into test mode
BBH ALARM OFF
Inhibits the BBH alarm
CAL BAY @1/@2
Calibrates the bay level receive equipment
AIC OUT
Disables automatic intermodulation compensation
ACT C
Activates the Control Processor
TS A CHAN #
Sets all timeslots to channel #
TS A ANT #
Sets all timeslots to antenna #
SYNTH 1
Stops synthesizer switching with synthesizer 1 permanently on
SYNTH NRM
Enables synthesizer switching into normal working
SAVE CAL BAY
Transfers Bay Level Calibration stored data in RAM to FLASH

EPROM
BAYDONE @N
Informs control processor that bay level calibration is valid for

branch N and sets bay level flag
68P02901W43-P
23 Feb 2004
3-61
GMR-01
Function
TCU-B emulator TTY command

HALT C
Stops the Control Processor
WRENB
Write enables the FLASH EPROM
WRPTC
Write protects the FLASH EPROM
FR BAY
Reads cal bay offsets from FLASH EPROM
MR BAY
Reads cal bay offsets from RAM

Function
RSS MMI command
Stops the TCU-B hunting between fibre A and fibre

B and forces the TCU-B to look only at fibre A.
tcu_clock 0

2. BSS MMI commands may be entered in upper or lower case. TCU-B emulator or RSS MMI
commands must be entered as shown. The first transceiver password must be in upper case.
Preparation for bay level calibration

The RF path has to be prepared for bay level calibration. The radio has to be reset and locked, a
dummy load fitted if there is no antenna connected and the alarms disabled.
Use the following procedure to prepare for TCU-B bay level calibration:
The two receive cables must be connected to the TCU-B at all times, as the cable connecting
the TCU-B RX IN 1 terminal carries signalling information to the IADU and the cable
connecting the TCU-B RX IN 2 terminal carries power feed to the DLNB.
3-62
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-32
Prepare for TCU-B bay level calibration
At the MMI-RAM> prompt enter the command:

ins_device # dri a * 0
Where:
The radio must be brought into service as there is no flash EPROM

storage of code at the radio control processor level.
If a connection to the BSC is not available a PCMCIA commissioning
card must be used.
3
Wait for the radio to finish initializing, then lock the cell using the lock device
command.

Enter the command:
Where:
For ease of calibration, all TCU-Bs in a cell should be initialized and

then locked.Always lock the transceiver providing the BCCH last as
this prevents the BCCH being switched to alternate transceivers.
4
Where:
68P02901W43-P
23 Feb 2004
3-63
GMR-01
Procedure 3-32
Prepare for TCU-B bay level calibration (Continued)
Connect port COM1 on the PC to the TTY Interface port on the radio using a
At the MMI-ROM prompt enter the command:

tcu_clock 0
WARNING:
TCU must be reset to get connection to MCU.
Do not reset the TCU at this point. The reset is carried out on
completion of the bay level calibration procedure, as detailed in
section Site restoration.
7
If a tx antenna is not connected to the radio under test, connect a 50 ohm 50 W

dummy load to the Tx port of the radio under test.
Ensure that you have entered the tcu_clock 0 command

at the RSS MMI-ROM 0000> prompt, as shown in step 7
before entering call processing to avoid EQCP instability
at step 3 of the next procedure.
8
Remove the 25 pin RSS connector from the radio and replace it with a 9-way
to 25-way EQCP cable.

.GSMFW
TEST
WARNING:
10
The EQCP is now in test mode.
At the EQCP TEST prompt enter the command:

BBH ALARM OFF
The alarm reporting for the BBH connection is turned off
11

AIC OUT
The AIC pad for branch 1 is OUT.
The AIC pad for branch 2 is OUT.
3-64
GMR-01
68P02901W43-P
23 Feb 2004

Use the following procedure for bay level calibration of branch 1 RX1A:
1
Connect the output of the signal generator to branch 1 of the antenna port at
the top of the M-Cell cabinet.
As the IADU connects the TCU-B receive port to the receive antenna
via the DLNB, and there are up to three DLNBs per cabinet, it is
important to choose the correct number in the TS A ANT command.
See Antenna identification diagrams for further explanation.
The antenna number can also be found by using thedisp_equipment # DRI A * 0
command. The number next to antenna_select is the antenna number.
2
Set the signal generator to provide -65.0 dBm at the antenna port and to the first
channel test frequency shown in Table 3-19.

ACT C
The EQCP is in the Call Processing state
Warning: After locking carrier down, enter TCU_CLOCK 0
command at RSS MMI-ROM 0000> prompt before entering Call
Processing to avoid EQCP instability.
Enter the command:

TS A ANT 1
All timeslots are under user control.

TS A CHAN #
Where:
# is the channel number of the selected frequency, as shown in Table 3-19.
The data for all timeslots has been changed.
68P02901W43-P
23 Feb 2004
3-65
GMR-01
Procedure 3-33
5
At the EQCP TEST prompt enter the command

SYNTH 1
Synthesizer 1 is enabled.
Enter the command:

CAL BAY @1
BAY LEVEL OFFSET =
XX
Where: XX is the hex value of the bay level reading

Enter the command:
SYNTH NRM
The system is under real time control.
Set the signal generator to the next frequency and repeat step 4 and step 5 for
all the test frequencies in Table 3-19.
Table 3-19
EGSM900 test frequency table
Channel
Frequency (MHz)
Channel
Frequency (MHz)
979
881.001
43
898.601
987
882.601
51
900.201
995
884.201
59
901.801
1003
885.801
67
903.401
1011
887.401
75
905.001
1019
889.001
83
906.601
03
890.601
91
908.201
11
892.201
99
909.801
19
893.801
107
911.401
27
895.401
115
913.001
35
897.001
123
914.601
3-66
GMR-01
68P02901W43-P
23 Feb 2004
Antenna identification diagrams

The following examples are intended to clarify how to identify antenna number for each transceiver.
Figure 3-6
Single M-Cell6 cabinet 2/2/2 configuration
CELL C
CELL B
CELL A
D
L
N
B
0
I
A
D
U
T
C
U
B
3
T
C
U
B
3
T
C
U
B
T
C
U
B
T
C
U
B
T
C
U
B
For cell A the receive antennas are connected to DLNB 0; these antennas are known as
For cell B the receive antennas are connected to DLNB 1; these antennas are known as
68P02901W43-P
23 Feb 2004
3-67
GMR-01
For cell C the receive antennas are connected to DLNB 2; these antennas are known as
Figure 3-7
Two M-Cell6 cabinets 4/4/4 configuration
CELL C
CELL A
CELL B
CABINET 2
CABINET 1
D
L
N
B
0
I
A
D
U
T
C
U
B
T
C
U
B
T
C
U
B
T
C
U
B
T
C
U
B
1
T
C
U
B
T
C
U
B
T
C
U
B
T
C
U
B
T
C
U
B
T
C
U
B
T
C
U
B
For cell A the receive antennas are connected to DLNB 0 in cabinet 1; these antennas are known
as antenna 1, so the timeslot command is TS A ANT 1.
For cell B the receive antennas are connected to DLNB 2 in cabinet 1 and extended to the IADU in
cabinet 2 (by using the extender module). The cabinet 1 transceivers see the antennas as antenna
3 and require the TS A ANT 3 timeslot command, and the cabinet 2 transceivers see the antennas
as antenna 1 and require the TS A ANT 1 timeslot command.
For cell C the receive antennas are connected to DLNB 2 in cabinet 2; these antennas are
known as antenna 3, so the timeslot command is TS A ANT 3.
3-68
GMR-01
68P02901W43-P
23 Feb 2004

Use the following procedure for bay level calibration of the second antenna port RX2A:
1
Connect the output of the generator to RX2A.
Set the signal generator to provide -65.0 dBm at the antenna port and set to the
first channel test frequency shown in Table 3-19.

TS A ANT 2

TS A CHAN #
Where:

SYNTH 1
CAL BAY @1
SYNTH NRM

Use the following procedure for bay level calibration of the third antenna port RX3A:
68P02901W43-P
23 Feb 2004
3-69
GMR-01
Procedure 3-35
Connect the output of the generator to RX3A.
Set the signal generator to provide -65.0 dBm at the antenna port and set to the
first channel test frequency shown in Table 3-19.

TS A ANT 3

TS A CHAN #
Where:

SYNTH 1CAL
BAY @1
SYNTH NRM
Branch 1 completion
Use the following procedure to complete the bay level calibration for branch 1:
Procedure 3-36
1
Complete branch 1 bay level calibration

BAYDONE @1
BAY LEVEL CALIBRATION IS DONE
At the EQCP TEST prompt enter the command

HALT C
The EQCP is in the Active Standby state

WRENB
Device OK. Flash is now write enabled.
3-70
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-36
Complete branch 1 bay level calibration (Continued)

SAVE CAL BAY

Save Cal Completed.

WRPTC
Flash is now write protected.
Branch 2 procedure
To calibrate bay level offset tables for branch 2, repeat the following procedures using
connectors RX1B, RX2B and RX3B respectively:
Branch 1 completion
Enter @2 instead of @1 in the cal bay and baydone commands.
Only one branch calibration is required in the special case of an M-Cell2 dual antenna/shared
radios. This is because each radio can be split in a bow tie to either antenna, and one
measured branch will provide accuracy to within the GSM specification.

Use the following procedure to check the bay level calibration has been successful:
68P02901W43-P
23 Feb 2004
3-71
GMR-01
Procedure 3-37
1
Check bay level calibration success
To verify that the bay level offset values have been stored in EPROM, use the read
command with the required offset address from Table 3-20 as an argument.
To verify writes to FLASH use command FR BAY.
To verify writes to RAM use command MR BAY
TCU-Bs cover the EGSM range and store offsets in 22 locations in each memory area
per antenna per branch.
Each location consists of three bytes.For example, the branch 1 valid flag
data is stored in address locations A000700, A000701 and A000702.
2
The following is an example of the first line of the FLASH BAY LEVEL OFFSET
table when using the FR BAY command, and a description of the fields displayed:
Address BRI
BR2
BR1
BR2
BL
BL
BL
BL
flag
Cksum Cksum offset offset offset offset
A000700 000001 000001 000595 000595 000060 000002 000005 000002
The remaining rows of the tabulated output contain BL offset values.

3
If the bay level calibration is successful, each appropriate table location will contain
valid offsets, and not thefactory default of 80.

uncalibrated antenna port and will result in error alarm DRI 218: Invalid
Transceiver Calibration Data being reported when the unit is unlocked.
The calibration procedure will have to be repeated after checking the
configuration and RF cables.
Unused data columns in a site configuration may have value 80. No
alarm will be reported as such table locations are inappropriate to the site.
4
Table 3-20
If the radio is suspected as being at fault, a diagnostic check needs to be run.

See section Diagnostic check procedure.
TCU-B frequency offset addresses

Bay Level Calibration Storage
Flash Address
Branch 1 Valid Flag
A000700
Branch 2 Valid Flag
A000703
Branch 1 Checksum
A000706
Branch 2 Checksum
A000709
Bay Level Offsets For Branch 1 Antenna 1
3-72
GMR-01
A00070C - A00074B
68P02901W43-P
23 Feb 2004
Table 3-20 TCU-B frequency offset addresses (Continued)

Bay Level Calibration Storage
Flash Address
A00074E - A00078D
A000790 - A0007CF
A0007D2 - A000811
A000814 - A000859
A00085C - A000895
The RX2 inner of the TCU-B is at +12 V dc and is used to power the
DLNB in M-Cell equipment. Failure to follow this procedure accurately
could result in damage to the signal generator.
If it is suspected that a bay level calibration problem is caused by the TCU-B, then a diagnostic check
can be made by performing a bay level calibration on the TCU-B alone.
Procedure 3-38 TCU-B diagnostic check
68P02901W43-P
23 Feb 2004
Set a signal generator that can withstand +25 V dc applied to its output or has a
dc block between the generator output and transceiver RX2 input, to -55 dBm
plus lead loss to simulate a gain of 10 dB.
Connect the signal generator directly to branch 1 or 2 on the TCU-B.
3-73
GMR-01
Procedure 3-38
3
TCU-B diagnostic check (Continued)
Follow the bay level calibration procedures for each branch, refer to:
The range 97 - D3 used in step 4 applies to TCU-B diagnostic checks

figures.
If the values are correct, then the TCU-B is working correctly and any fault will
probably be in the cabinet front end cables, cable connections or LNA or DNLB.
If the offsets are outside this range, the TCU-B is faulty and should be returned.
Site restoration
Use the following procedure to restore the site after bay level calibration is complete:
Procedure 3-39 Restore site after TCU-B bay level calibration
1
Remove the 9-way to 25-way cable from the TTY INTERFACE port on the
TCU-B.
Connect the 9-way to 9-way cable from the PC serial A port to a MCU TTY port.
The following step must be carried out to initialize software

and so ensure the TCU-B is correctly brought into service.
4
Press the Reset button on the front panel of the TCU-B.
Enter the command:

Where:
The TCU-B is now in the UNLOCKED_BUSY state.
3-74
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-39 Restore site after TCU-B bay level calibration (Continued)
6
Enter the command:

disp_act_alarm # dri a * 0
Where:
Confirm that there is no DRI 218 alarm.
If a DRI 218 alarm is seen, the entire bay level calibration procedure
must be repeated.
7
68P02901W43-P
23 Feb 2004
Remove the 9-way to 9-way cable from the MCU TTY port.
3-75
GMR-01
Database equipage check
The database equipage checks determine what devices and functions have been equipped
in the BSC or M-Cell2/M-Cell6 database.
There are two stages to the procedure:
Preparing for the test.

The following test equipment is required during the procedure:
Do not optimize Motorola cellular basestations with
Commands used
The following commands are used during the procedure:
Function
Command
disp_site
Displays the site number.
disp_equipment
3-76
GMR-01
68P02901W43-P
23 Feb 2004
Preparation for check procedure

The following procedure is used to prepare for the database equipage checks:
Procedure 3-40
Prepare for database equipage checks
Connect the serial A port on the PC to a MCU TTY port using the 9-way to
9-way cable.
Database equipage check procedure

The following procedure is used to check the database for devices and functions:
68P02901W43-P
23 Feb 2004
3-77
GMR-01
Procedure 3-41
1
Check database for devices and functions
At the CUST MMI prompt enter the command:

disp_site
The following message (from the MCU) is displayed:
current site is #
Where: # is the number of the site logged onto.

2

disp_equipment #
Where:
# is the number of the site logged onto.
A complete list of the equipment and functions in the database is displayed, for
example:
GPROC
GPROC
BSP
DRI
DRI
MSI
MMS
MMS
GCLK
KSW
CAB
SITE
RTF
RTF
0 0 0
1 0 0
0 0 0
0 0 0
0 1 0
0 0 0
0 0 0
0 1 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 1 0
Check the MSI configuration by entering:

disp_equipment # MSI 1 0 0
Where: # is the site number.
MSI identifier 1
Cage number
0
Slot number
16
MSI type
0
(0 = MSI)
3-78
GMR-01
68P02901W43-P
23 Feb 2004
E1/T1 link check
E1/T1 link check
The E1/T1 link checks verify the integrity of the links back to the BSC/MSC.
Checking the 2.048 Mbit/s link.

The 2.048 Mbit/s link checks require the following test equipment:
Commands used
The following command is used to carry out the procedure:
Function
Command
state
68P02901W43-P
23 Feb 2004
3-79
GMR-01
E1/T1 link check
Preparation for checking the E1/T1 link

To set up the equipment to check the 2.048 Mbit/s links:
Procedure 3-42
Prepare for E1/T1 link check
Ensure the site is in call processing mode.
Connect the serial A port on the PC to an MCU TTY port using the 9-way to
9-way cable.

The system and the hardware are set up to check the 2.048 Mbit/s links.
E1/T1 link test procedure

The following procedure is used to check the E1/T1 link:
3-80
GMR-01
68P02901W43-P
23 Feb 2004
E1/T1 link check
Procedure 3-43 Check E1/T1 link

1
the relevant Digital Distribution Frame (DDF) port.
Repeat for all NIUs and 2 Mbit/s links.
If the 2.048 Mbit/s link has not been installed, perform this test
at the DDF in the site.
If No DDF is fitted, do this test at the top of the cabinet
Ascertain the site number, equipment list and MMS configuration.

state # MMS * * *
Where:
# is the location
* * * is the dev/func id
For example, state 1 MMS 1 0 0
The system displays the following message from the MCU:
STATUS INFORMATION
Device: MMS 1 0 0
Reason code is : 0
Related Device/Function:
Assigned to:
END OF STATUS REPORT
If this display shows UNLOCKED and BUSY, then the NIU port (MMS), T43,
cabling and the 2.048 Mbit/s link are all good.
If the loop is removed and the command re-entered, the result will be
UNLOCKED and DISABLED
The NIU requires a minimum of 20 seconds after receiving these

commands before it registers a change in status.
If the display continues to show Unlocked and Busy, this may be
because:
68P02901W43-P
23 Feb 2004
The wrong connection is looped, if the cabling is direct.
The MMS may be terminated by a device generating a 2.048

Mbit/s link.
3-81
GMR-01
PIX connections and alarms check
The alarm tests check the serial connections and alarm status of M-Cell equipment.
Testing the PIX connections using the database external alarm system (EAS).

The serial and alarm tests require the following test equipment:
Commands used
The following command is used to test the PIX connections:
Function
Command
enable_alarm
3-82
GMR-01
68P02901W43-P
23 Feb 2004
Preparation for PIX connections and alarm tests

The following procedure is used to prepare for the PIX connections and alarm tests:
Procedure 3-44
Prepare for PIX connections and alarm tests
Make sure the software download has been completed.
Connect the serial A port on the PC to the master MCU using the 9 to 25 way
cable.

The system displays the CUST MMI prompt.
Enter the password at the CUST MMI prompt.

The equipment is set up for the test.
PIX connections test procedure

The PIX connections may be tested at a live site using the following test procedure:
Procedure 3-45
Test PIX connections
Apply suitable test plug to PIX input on cabinet top panel.
At the CUST MMI prompt on the PC enter the command:

enable_alarm #
Where: # is the site number.
The system displays all 8 alarms.
The display depends on the database settings, that is, whether a fault
condition is indicated by a closed loop or an open loop.
3
68P02901W43-P
23 Feb 2004
Remove the test plug.

The system clears the alarm display.
3-83
GMR-01
MCU (GCLK) calibration
GCLK calibration can be carried out automatically using the CINDY commissioning tool.
Refer to the relevant CINDY user documentation for details.
This procedure explains how to calibrate the Ovenized Crystal Oscillator (OCXO) in the
MCU GCLK in the M-Cell2 and M-Cell6 product at a BSS site. The calibration procedure
is not applicable to the MCU-micro product.
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 than 34/day).
When ever calibration is required. (Display the active alarms for a site - if calibration
is required, there will be an alarm stating this).
This procedure should only be carried out by fully trained,

GSM qualified personnel. Under NO circumstances should
this procedure be undertaken, unless all the correct test
equipment is readily available.
The command gclk_cal_mode used in this procedure should only be executed

at the BTS where the calibration is being carried out.
No call processing can occur involving the MCU during calibration mode.
Allow a period of 15 minutes to elapse after switching the OXCO

power on, to give sufficient time for the unit to reach operating
temperature and achieve frequency stabilization.
3-84
GMR-01
68P02901W43-P
23 Feb 2004

The test equipment required to carry out the GCLK calibration is as follows:
IBM compatible personal computer (PC).
Rubidium clock standard.
Frequency counter.
BNC to 3-way MCU test lead.
Preparation for GCLK calibration

Use the following procedure to prepare the MCU (GCLK) for calibration:
Procedure 3-46 Prepare for GCLK calibration
1
Connect the serial A port of the PC to the MCU-TTY port using the 9-way to
9-way TTY cable.
Connect the output from the 10 MHz standard to the referenceinput of the
frequency counter, select external standard.
Set the frequency gate time to 10 seconds and the display to 10 significant digits.
Connect the test cable extracting the 8 kHz output signal from the front of the
MCU to the input of the counter as follows:
Pin 3 - Earth (top pin)
Pin 1 - 8 kHz signal (bottom pin)
See also Figure 3-8 below.
68P02901W43-P
23 Feb 2004
3-85
GMR-01
Figure 3-8
M-Cell GCLK calibration cable connections
MCU TTY
MCU
8 kHz Out
8000.000000
10 MHz REFERENCE
UNIVERSAL COUNTER
GCLK calibration procedure

The following procedure is used to calibrate the MCU (GCLK):
Procedure 3-47
1
Calibrate MCU GCLK
At the MMI-RAM 1015 prompt enter the command:

clear_gclk_avgs <location>
Where: <location> is the site number
The user is prompted for an mms id, for all M-Cell sites enter:
0 0
3-86
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-47 Calibrate MCU GCLK (Continued)

3
To start GCLK calibration mode, enter the command:

gclk_cal_mode
The gclk_cal_mode command is used to tell the sync function and MCU
software that a calibration is to be performed and can only be executed at
M-Cell sites outside Sysgen mode.The command is NOT allowed on a
Master MCU when a Standby MCU is available.
When the command is executed the system prompts for verification:
Site <Local site number> starting GCLK CALIBRATION MODE.
this is a single MCU site, the site will be down until
calibration is complete.
Are you sure (y=yes, n=no)?
If
Enter:
y
The MCU begins calibration mode.
The command is aborted if the reply is anything other than y.
4
The user is then prompted with the following:
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 is anything other
than y.
68P02901W43-P
23 Feb 2004
3-87
GMR-01
Procedure 3-47
5
Calibrate MCU GCLK (Continued)
Adjust the OCXO control voltage using the +, , and 0 to 3 keys until the measured
frequency is exactly 8000.000000 Hz on the frequency counter.
The values entered here, change the frequency by varying degrees.For example:
+0 will increase the output by a small amount.
+1 will increase the frequency by approximately 10 times.
These are not exact values as every OCXO has a different gain. This method gives
sufficient control to correct the frequency within a short time.
A typical sequence of numbers may look as follows:
Enter a to abort. s to save, +(0..3)

>-3 (7.99999898)
>+3 (8.00000020)
>-0 (8.00000019 - 8.00000020)
>-2 (8.00000004)
>+2 (8.00000020)
>-1 (8.00000018)
>-2 (8.00000002 -8.00000003)
>-1(8.000000--)
>+0 (8.000000-)
>+0 (8.00000000)
to inc, -(0..3) to dec

The user is then prompted to save 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 MCU applies a set of voltages to the DAC that feeds the OCXO,
requiring the user to input the corresponding output frequency. This is necessary
because the OCXO frequency/voltage characteristic is not linear and the MCU adjusts
for this by taking readings across a range of DAC voltages.
3-88
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 3-47 Calibrate MCU GCLK (Continued)

7
To calibrate the OCXO gain, enter the measured frequency value from the counter
after the value has settled in response to the MMI prompts.
When taking frequency measurements, ensure that a full gate period

elapses from the time the new value is set to reading the counter.This wait
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
7999.99915
7999.99969
8000.00020
8000.00070
8000.00122
8000.00176
Calibration Gain 3.865560e-01
SYNC>
The MCU will be reset when the calibration is complete.

8
On completion the MCU automatically rejects the calibration if it is outside the

threshold, and the following message is displayed:
Computed Gain > Max
WILL RETRY GAIN
Calibration must be performed again.

If calibration fails the second time with the same or similar value, the OCXO may
be operating outside the Motorola specification, in which case the MCU is deemed
faulty and should be replaced.
68P02901W43-P
23 Feb 2004
3-89
GMR-01
3-90
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
4
Preserve calibration
The preserve transceiver calibration feature uses commands to store, display and clear calibration
data. This feature is used on busy systems where there is a need to replace a transceiver quickly
and thus reduce system down time during peak hours. Following transceiver replacement however,
another site visit during an off-peak period will be necessary to carry out bay level and Cellsite
Power (CSPWR) calibration to fully optimize the hardware.
In this chapter procedures for the following are described:
Preserving calibration in "Preserve calibration procedures" on page 4-7
Calibration of transceivers in "Transceiver calibration" on page 4-10
Recalibration of transceivers in "Transceiver recalibration" on page 4-13
The preserve transceiver calibration feature applies only to BTS4/5/6, ExCell, TopCell,
M-Cell2, M-Cell6 and Horizonmacro equipment.
Refer to the relevant section of this manual for calibration procedures for specific transceivers.
68P02901W43-P
23 Feb 2004
4-1
GMR-01
Preserve calibration data overview
The preserve calibration feature enables malfunctioning transceivers to be replaced without the
need to remove the cell from service. The calibration offsets can be displayed, stored and cleared
using the disp_cal_data, store_cal_data and clear_cal_data commands.
The preserve transceiver calibration feature applies only to BTS4/5/6, ExCell, TopCell,
M-Cell2, M-Cell6 and Horizonmacro equipment.
Display calibration offsets data

The disp_cal_data command only displays offsets from the transceiver if the DRI is in the
busy-unlocked (B-U) state. The GPROC CM database values are displayed when the radio is
locked or not busy. If the calibration values have been cleared, they will not be available
on the specific RAM of the radio or the CM database, and the response will be:
NO CALIBRATION DATA AVAILABLE
Store calibration data

The store_cal_data command sets a flag to indicate that when the radio is unlocked and comes into
service, the calibration values will be copied from the RAM in the radio into the GPROC CM database.
The values from the RAM in the radio will only be copied to the database if there are no calibration
values in GPROC CM database, and if the radio has values in the RAM to be copied.
If the RAM in the radio has been cleared of all values, and the GPROC CM database has calibration values
for that specific radio, when the radio is unlocked it will get a copy of these values from the CM database.
Different calibration values for the same radio can exist in the CM database and RAM in the radio.
Care has to be taken when calibrating a radio. To ensure that the values in the RAM of the radio and CM
database have the same calibration data, the existing values have to be cleared using the clear_cal_data
command before a calibration can be successful and the correct calibration saved. Calibration data is stored in
the master CM database at the BSC, and is used to update the CM database copy at the BTS if it is valid.
4-2
GMR-01
68P02901W43-P
23 Feb 2004
In any transceiver calibration, the value 80 must be cleared from all the paths (columns of data)
stored in the radio, otherwise calibration data will not be passed to the CM database.
This applies even when the value 80 is not in the path of the transceiver being calibrated.
If the 80 value exists on another path, the data will not be copied to the CM database
when the radio is unlocked and calibration will appear to be lost.
If an 80 value is found it must be removed by calibrating the radio on that path.
For a CTU2 radio the invalid data is 0800hex.
Clear calibration data

The clear_cal_data command removes the offsets from RAM and the database. To clear the data from a
radio that is B-U in the network, the command is issued after the radio is locked. A new radio 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 this radio. This is explained in the calibration procedure.
Calibration data exchange

The process of uploading/downloading calibration data between the radio and the CM database
is automatic, based on the following conditions:
Site Initialization with calibration data held in CM database but with

invalid/no calibration data in radio.
If a radio malfunctions and has to be replaced, the associated DRI is locked and the
malfunctioning radio replaced with a new radio while the cell remains in service.
The DRI is then unlocked. When the executive message radio Standby Success is
received by the CA at the BTS, the database is queried to determine if any valid
offset data is stored. If any is found in the database, this is downloaded to the new
radio and the radio is allowed to come into service (B-U).
Refer to "Preserve calibration procedures" on page 4-7 procedures for this procedure.
Site Initialization with invalid/no calibration data held in CM database and

invalid/no calibration data in the transceiver.
Once the CA at the BTS receives the executive message radio Standby Success, it
checks the CM database for valid offsets. If none exist, the BTS then queries the
radio for valid data. If none exist in the radio, the radio is brought into service but
the Invalid transceiver calibration data alarm is triggered.
Refer to "Transceiver calibration" on page 4-10 for this procedure.
68P02901W43-P
23 Feb 2004
4-3
GMR-01
Site Initialization with invalid/no calibration data held in CM database but

with valid calibration data in radio.
Initially a radio is calibrated and the antenna offsets stored within the radio. When
the BTS initializes and enters call processing mode, the Central Authority (CA) at
the BTS queries Configuration Management (CM) to see if valid offset data exists.
If no valid data exists then the radio(s) are queried for the offset data, which is sent
via the Radio Signalling Link (RSL) to CM at the BSC.
Refer to "Transceiver recalibration" on page 4-13 for this procedure.
4-4
GMR-01
68P02901W43-P
23 Feb 2004
The following equipment is needed to carry out these procedures:
9-way to 9-way cable (Horizon and M-Cell BTS only).
9-way to 25-way GPROC cable (BTS 4, 5, 6 and BSC only).

Many of the procedures described in this chapter can be carried out automatically using the CINDY
68P02901W43-P
23 Feb 2004
4-5
GMR-01
Commands used
Commands used
The following commands are used to carry out these procedure:

BTS Command
Function
lock_device
unlock_device
Enables the device to be used

Function
OMC/BSC Command
store_cal_data
Stores calibration data for all transceivers into the master CM database at
the BSC, which is then used to update the CM database copy at the BTS.
disp_cal_data
When transceiver is locked: Displays calibration data in the CM

database for the specified transceiver.
When transceiver is unlocked: Displays calibration data in the RAM of
the specified transceiver.
clear_cal_data
Clears calibration data in CM database at BSC and BTS for a specified

transceiver.
If there is no RSL from the BTS to the BSC then the command will not be executed by the
BSC, as the BSC has no knowledge of the command being entered.
All calibration data will be stored in the master CM database at the BSC, which is then used to
update the CM database copy at the BTS only if the data is valid.
4-6
GMR-01
68P02901W43-P
23 Feb 2004
Preserve calibration procedures
This section describes the following preserve calibration procedures:
Activating the preserve calibration feature.
Viewing the calibration data in the CM database.
Before starting the preserve calibration procedures, consult the site specific documentation to
determine the BSC/BTS configuration and cage slot allocation.
Activating the preserve calibration feature

The preserve calibration feature must first be activated at either the OMC-R or the BSC.
Activating the preserve calibration feature at the OMC-R

Use the following procedure to activate the preserve calibration feature at the OMC-R:
Procedure 4-1
Activate preserve calibration at the OMC-R
At the operations and maintenance centre (OMC-R) man-machine interface (MMI),

log in to the required base site controller (BSC).
To initiate the preserve feature enter the command:

store_cal_data <site_id>
All calibration data will be stored in the master CM database at the BSC, which is then used to
update the CM database copy at the BTS only if the data is valid.
Activating the preserve calibration feature at the BSC

Use the following procedure to activate the preserve calibration feature at the BSC:
Procedure 4-2
1
Activate preserve calibration at the BSC
Connect the 9-way to 25-way cable from the PC serial A port to a GPROC TTY port.
The generic term GPROC is used to denote the GPROC, GPROC2 and
{4354} GPROC3 processor boards.
2
68P02901W43-P
23 Feb 2004
4-7
GMR-01
Procedure 4-2
Activate preserve calibration at the BSC (Continued)
At the CUST/MMI prompt, enter the appropriate change command and passwords.
At the BSP MMI prompt enter the command:

store_cal_data <location>

If there is valid calibration data present in the CM database, a transceiver can be
replaced whilst the cell remains in service.
Use the following procedure to replace the transceiver:
Procedure 4-3
1
Replace a transceiver using preserve data
Lock the DRI of the transceiver to be replaced, enter the command:

lock_device <location> DRI <device_id1> <device_id2>
[<device_id3>]
A CTU2 transceiver is capable of supporting two DRI.

2
Replace the transceiver with the new transceiver. Refer to the appropriate service
manual for instructions.
Unlock the DRI of the transceiver, enter the command:

unlock_device <location> DRI <device_id1> <device_id2>
[<device_id3>]
The calibration data stored in the CM database will be downloaded into the RAM of the new transceiver.
The data is also stored in the non-volatile transceiver memory
if the new transceiver is a CTU, TCU, SCU or DRCU.
Update of non-volatile transceiver memory from CM database does not occur for DRCUII or DRCU3.
Viewing the calibration data in CM database

Use the following procedure to view the current calibration data in the CM database:
4-8
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 4-4
View calibration data in CM database
Lock the DRI of the transceiver to be checked, enter the command:

[<device_id3>]
Display the CM database calibration data, enter the command:

disp_cal_data <location> DRI <device_id> <device_id2>
[<device_id3>]
The response should be:
DRI ID: (device id1) (device id2) (device id3)
Data read from CM database
Calibration data (all values in hex)
Transmit power offset =(CSPWR power offset)
Receive system data:
Antenna Number
1
2
3
4
5
6
Six columns of bay level offset calibration data will be displayed as explained in Table 4-1:
Table 4-1
Explanation of offset calibration data presentation per row
Column:
is branch:
and antenna:
The number of rows of offset calibration data are as follows:
68P02901W43-P
23 Feb 2004
GSM850 - 16
PGSM900 - 16
EGSM900 - 22
DCS1800 - 47
PCS1900 - 38
4-9
GMR-01
Transceiver calibration
The following procedure is used to put a new transceiver into service if there is invalid or no
calibration data held in CM database. If recalibration of a working transceiver is required,
use the "Transceiver recalibration" on page 4-13 procedure.
Transceiver calibration procedure

Use the following procedure to calibrate the transceiver:
TCU-Bs and CTUs require a code load prior to the calibration process. Wait until
the TCU-B/CTU finishes the code load and stops flashing (in BUSY-UNLOCKED
or ENABLED-UNLOCKED state) before proceeding.
Procedure 4-5 Calibrate transceiver
1
Activate the preserve calibration feature for the site to ensure the new data is stored
in the CM database following recalibration.
Lock all the DRIs in the same sector of the transceiver to be calibrated. Enter the
following command for each of the DRIs:
[<device_id3>]
A CTU2 transceiver is capable of supporting two DRI. The Cal_data for

both DRIs must be Locked and Cleared during the calibration procedure
3
Display the data in the CM database for all the transceivers in the sector, enter the
command:
disp_cal_data <location> DRI <device_id1> <device_id2>
[<device_id3>]
If valid data is present proceed to step 6.

If the response seen is:
Enter the command:

4-10
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 4-5 Calibrate transceiver (Continued)

5
Check there is calibration data present in the CM database for all the DRIs in the
sector, then clear that data for each transceiver. Enter the command:
clear_cal_data <location> DRI <device_id1> <device_id2>
[<device_id3>]
The second DRI must also be cleared when using a CTU2 transceiver in
double mode.
6
Confirm the data has been cleared from the CM database for the specified transceiver,
enter the command:
[<device_id3>]
If no problems have occurred, the response will be:
NO DATA AVAILABLE
If there is a different response, ensure the transceiver is in the LOCKED

state and carry out from step 4 again.
7
Carry out bay level and cellsite power procedures, as described in the relevant section
of this manual. Record the data.
DCS1800 TCUs, TCU-Bs and CTUs require the following additional

command to perform calibration. Under the TSM test port at the TCU
(25-pin port) enter the command: tcu_clock 0

Use the following procedure to check the calibration:
68P02901W43-P
23 Feb 2004
4-11
GMR-01
Procedure 4-6
1
Check calibration
Unlock the DRI of the calibrated transceiver.
Before unlocking the transceiver, ensure the previous calibration data

has been cleared.
Enter the command:
[<device_id3>]
Check the calibrated transceiver passes into BUSY-UNLOCKED state. The new
calibration data is uploaded to the CM database and is then used to update the copy at
the BTS.
2
Check the calibration data of the DRI of the calibrated transceiver against the values
recorded in step 6 of the previous procedure.
Allow one minute after uploading for the values in the CM database
at the BSC to be updated.
Enter the command:
[<device_id3>]
If the transceiver is BUSY-UNLOCKED the data can be read directly

from the transceiver, in ENABLED-UNLOCKED or LOCKED state
calibration data is read from the CM database.
The values seen should match the previous ones.
3
Make test calls in all timeslots of the new DRI to check audio quality then lock
the tested DRIs. Enter the command:
[<device_id3>]
With the transceivers LOCKED (or in ENABLED-UNLOCKED state), ensure the

calibration process has been carried out correctly, by checking that the CM database
at the BSC has been updated with the new values. Enter the command:
[<device_id3>]
If everything is in order, the cell can be put back into service. Unlock all the DRIs
locked previously using the command:
[<device_id3>]
4-12
GMR-01
68P02901W43-P
23 Feb 2004
Transceiver recalibration
The following procedure is used to recalibrate a working transceiver when there is invalid or no
calibration data held in CM database but valid calibration data is present in the radio.
Transceiver recalibration procedure

Use the following procedure to recalibrate the transceiver:
Procedure 4-7 Recalibrate transceiver
1
Activate the preserve calibration feature for the site to ensure the new data is stored in
the CM database following recalibration.
At the site BTP, remote login to the serving BSC and enter the following MMI
command:
Lock all the DRIs in the same sector of the transceiver to be recalibrated. Enter the
following command for each of the DRIs:
[<device_id3>]
A CTU2 transceiver is capable of supporting two DRI. The Cal_data for

both DRIs must be Locked and Cleared during the calibration procedure
4
Display the data in the CM database for the transceivers in the sector, enter the
command:
[<device_id3>]
If valid data is present proceed to step 6.

If the response seen is:
Enter the command:

68P02901W43-P
23 Feb 2004
4-13
GMR-01
Procedure 4-7
6
Recalibrate transceiver (Continued)
Check there is calibration data present in the CM database for all the DRIs in the
sector, then clear that data for each transceiver using the command:
clear_cal_data <location> DRI <device_id1> <device_id2>
[<device_id3>]
The second DRI must also be cleared when using a CTU2 transceiver in
double mode.
7
Confirm the data has been cleared from the CM database for the specified transceiver,
enter the command:
[<device_id3>]
If no problems have occurred, the response will be:
NO DATA AVAILABLE
If there is a different response, ensure the transceiver is in the LOCKED

state and carry out step 3 again.
8
Carry out bay level and cellsite power check procedures, as described in the relevant
section of this manual. Record the data.
Recalibration check procedure

Use the following procedure to check the recalibration:
4-14
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 4-8
1
Check recalibration
Unlock the DRI of the recalibrated transceiver.
Before unlocking the transceiver, ensure the previous calibration data

has been cleared.
Enter the command:
[<device_id3>]
Check the calibrated transceiver passes into UNLOCKED state. The new calibration
data is uploaded to the CM database and is then used to update the copy at the BTS
(even if the DRI does not have an RTF assigned).
2
Check the calibration data of the DRI of the calibrated transceiver against the values
recorded in step 7 of the previous procedure.
Allow one minute after uploading for the values in the CM database
at the BSC to be updated.
Enter the command:
[<device_id3>]
If the transceiver is BUSY-UNLOCKED the data can be read directly

from the transceiver, in ENABLED-UNLOCKED or LOCKED state
calibration data is read from the CM database.
3
68P02901W43-P
23 Feb 2004
Lock the tested DRIs using the command:

[<device_id3>]
4-15
GMR-01
Procedure 4-8
Check recalibration (Continued)
With the transceivers LOCKED (or in ENABLED-UNLOCKED state), ensure the

calibration process has been carried out correctly, by checking that the CM database
at the BSC has been updated with the new values. Enter the command:
[<device_id3>]
If everything is in order, the cell can be put back into service. Unlock all the DRIs
locked previously using the command:
[<device_id3>]
4-16
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
5
Microcellular systems optimization
This chapter provides information required for commissioning and optimizing the
following microcellular systems:
M-Cellcity and M-Cellcity+
Horizonmicro (M-Cellarena) and Horizonmicro2
Horizoncompact (M-Cellarenamacro) and Horizoncompact2
It is possible that some equipment at the site may not be produced by Motorola. Examples of such
equipment may include battery chargers, power supplies, and antennas. Refer to site specific
documentation and the vendor instructions provided with non-Motorola equipment.
Optimizing cellular systems consists of:
68P02901W43-P
23 Feb 2004
Code download
Status check
Battery check
Link check
GCLK calibration
5-1
GMR-01
Introduction to microcellular systems optimization
The following procedures are used for the optimization of microcellular systems:
"Code download from PCMCIA" on page 5-8
"Code download from BSC" on page 5-16
"Battery check" on page 5-24
"E1/T1 link check" on page 5-26
"MCU-m GCLK calibration" on page 5-29
Before starting the optimization, the site should be prepared and the equipment installed as detailed
in the appropriate service manuals and the site specific documentation.
Code download
For the purposes of testing, the M-Cellcity must be installed with system software. How far overall
network installation has progressed will dictate the source of this software.
At initial loading, or when new system software is distributed to the system, the
system software is downloaded from the BSC.
To perform a code download to an M-Cellcity, the BSC must be equipped with a CSFP facility.
Once the BSC has established connection, it will automatically download operational code.
This procedure takes approximately 30 minutes.
If the BSC is not yet able to perform this download process, the M-Cellcity enclosure is provided with
software loaded on a PCMCIA flash card which is permanently inserted in the PCMCIA socket of MCU-m.
PCMCIA card
The use of a PCMCIA flash card containing operational code provides the following advantages:
The time taken to download code from the BSC may be significantly shortened, since the
BSC only download objects that are missing, corrupted or out of date.
The MCU-m automatically saves its code on the PCMCIA flash card, which is non-volatile.
The advantage of this is that in the event of a power failure leading to system shutdown,
the code will not have to be downloaded again from the BSC and so the system may
be restored to call processing status as quickly as possible.
5-2
GMR-01
68P02901W43-P
23 Feb 2004
The M-Cellcity may be commissioned without the presence of an active E1/T1 link,
if the necessary code is contained on the PCMCIA flash card.

68P02901W43-P
23 Feb 2004
5-3
GMR-01


Table 5-1 lists the test equipment required to carry out the optimization tests in this chapter.
Table 5-1 Hardware optimization equipment
Quantity
Description
Comments
IBM-compatible personal computer (PC)
Commercial terminal emulator software

accuracy 1x10-10
Frequency counter

display. Hewlett Packard model HP5385A
or equivalent
Signal generator
Range 0 to 2 GHz
Digital multimeter
50 W minimum
9-way to 37-way MCU cable
TTY cable. See Figure 5-1
PC to MCU. See Figure 5-2.
5-4
GMR-01
68P02901W43-P
23 Feb 2004
Table 5-1 Hardware optimization equipment (Continued)

Description
Quantity
Comments
9-way to 9-way connector and breakout

board, including shorting links (jumper
cables).
Motorola supply for GCLK calibration.

Kit number SWLN7898.
HIM-75 Type 43 loopback cables,
0.23 m
HIM-120 loopback plug
Test mobile
ESD protection kit
Test leads
Figure 5-1 and Figure 5-2 show the cable connections for the 9-way to 37-way TTY and
the 9-way to 9-way MCU test leads for the M-Cellcity.


68P02901W43-P
23 Feb 2004
5-5
GMR-01
9-way to 37-way TTY cable

Figure 5-1 M-Cellcity 9-way to 37-way TTY cable connections
PIN NUMBER
PIN NUMBER
PINS 1,4
AND 6 to 9
NOT USED
PINS 1,2
AND 6 to 37
NOT USED
TO PC
COMMUNICATIONS PORT
TO TTY MCU-m PORT
9-WAY D-TYPE F
37-WAY D-TYPE M
.
The 9-way to 37-way cable connections are listed in Table 5-2.
Table 5-2 9-way to 37-way cable connections
9-way pin number
37-way pin number
Signal name
TXD
Transmit Data
RXD
Receive Data
GND
Earth
5-6
GMR-01
68P02901W43-P
23 Feb 2004

Figure 5-2
M-Cellcity 9-way to 9-way MCU cable connections
PIN NUMBER
PIN NUMBER
4
6
7
8
TO PC
COMMUNICATIONS PORT
TO BREAKOUT BOARD
CONNECTOR
9-WAY D-TYPE F
9-WAY D-TYPE M
Usually, only a 3-wire interface connecting RXD, TXD and GND is required. However, some
PC applications will require two extra shorting connections to be made at the PC connector only.
These two connections are pin 4 to pin 6, and pin 7 to pin 8.
The RS-232 TTY connection on a PC is usually a male D9 connector with the pin
connections as shown in Table 5-3.
Table 5-3
9-way to 9-way cable connections
Pin Number
68P02901W43-P
23 Feb 2004
Signal name
DCD
Data Carrier Detect
RXD
Receive Data
TXD
Transmit Data
DTR
Data Terminal Ready
GND
Earth
DSR
Data Set Ready
RTS
Request To Send
CTS
Clear To Send
RI
Ring Indicator
5-7
GMR-01
Code download from PCMCIA
The PCMCIA is used initially to download code to the microcellular equipment in

preparation for commissioning.
This method requires a valid software load on a PCMCIA flash card and that the E1/T1 link is NOT connected.

The following test equipment is required to be connected before proceeding with the code download:
IBM compatible Personal Computer (PC).
RF wattmeter with 2.5 W element.
9-way to 37-way MCU cable.
Preparation for PCMCIA code download
The ac-dc PSM must not be powered up during the following preparations.
Use the following procedure to prepare for PCMCIA code download:
Procedure 5-1
1
Prepare for PCMCIA code download
Ensure the E1/T1 link is not connected.
This connection will allow monitoring of the download sequence and

at the end of a successful download allows input of MMI commands.
2
Connect the 9-way to 37-way cable from serial A port to the user TTY MCU-m
port (37-way D-type located beside the HIM module).
Connect the wattmeter, fitted withthe 2.5 W element, in series with the antenna
port and the antenna at the bottom of the cabinet.
Follow the procedure detailed in PCMCIA download procedure.
5-8
GMR-01
68P02901W43-P
23 Feb 2004
PCMCIA download procedure

Use the following procedure to download code from PCMCIA:
Procedure 5-2 PCMCIA code download
1
Switch on the ac-dc PSM and observe the download process (an output example follows).
!!!
REBOOT !!!
RSR=0xc0 PA12=0 PA11=1

Reset due to power reset
Checking DRAM: 16 of 16 MB complete
Motorola MCU Boot Software Version 1.4.0.6.5 15-Jul-96
Copyright 1996, Motorola Incorporated
Board type is MCU-micro
QUICC microcode revision 0x0082
PCMCIA: Intel Series 2+ Flash detected in socket 0
Turning caches on
caches are ON
taking PCMCIA version of object 2
MMI-ROM 0000 ->
MMI-ROM 0000 -> y
MMI-ROM 1015 ->
68P02901W43-P
23 Feb 2004
5-9
GMR-01
Procedure 5-2 PCMCIA code download (Continued)

2
At the MMI prompt, change the security level. Enter the command:
chg_l
Enter the password for security level you wish to access:
Enter the second level password.
Enter password for security level you wish to access:
Enter the third level password.
Current security level is 3
These are the standard 2 or 3 level passwords.
5-10
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 5-2
3
PCMCIA code download (Continued)
Once level 3 access is confirmed switch to the executive monitor (EMON) by selecting keys Ctrl and
N together.
At security level 3 the executive monitor (EMON) must be selected to view the download.
MCU:emon_1015 %
MCU:emon_0000 %
MIP: Starting Micro IP
MIP: In slot 0
MIP: csfp_swap value is 0
MIP: Reset type is x4.
MIP: Initializing Codeload structures
MIP: Creating Mailboxes...
MIP: Performing Hard Reset.
MIP: Now master MCU...
MIP: Starting to contact BSC.
MIP: Establishing links to NIU frame 0, slot 0
NG EXEC DLSP dl_message_con: Control mailbox opened for channel 1,= c0003120
NG EXEC DLSP dl_message_con: Control mailbox opened for channel 3,=
c0003120MCU:emon_1015 % NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for
channel 1,
Link Mailbox id = 1001
MIP: HDLC link connected on frame 0, slot 0
MIP: CPU assigned ok on frame 0, slot 0
MIP: Link state 2
MIP: Query of NIU successful on frame 0, slot 0
MIP: NIU configured ok on frame 0, slot 0
MIP: Establishing second RSL from MCU to the BSC over NIU frame 0, slot 0, span 1
MIP: Activated LAPD on frame 0, slot 0
MIP: NIU configured ok on frame 0, slot 0, span 1
MIP: SAP open ok on frame 0, slot 0
NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 5, Link Mailbox id=
9001
MIP: HDLC link connected on frame 0, slot 0, span 1
MIP: Link state 2
MIP: Query of NIU successful on frame 0, slot 0, span 1
MIP: Activated LAPD on frame 0, slot 0, span 1
MIP: SAP open ok on frame 0, slot 0, span 1
MIP: Bad EXEC DLSP return code 1
MIP: HDLC link failed to connect on frame 1, slot 0 with code 5
MIP: Tag 0x00 indicates nv_write successful!
MCU:emon_1015 %
MCU:emon_1015 %
MMI-ROM 1015 -> MMI-ROM 1015 ->
68P02901W43-P
23 Feb 2004
5-11
GMR-01

4
Set the site id using the command:

set_s <X>
Where X is the site id for the M-Cellcity site equipped on the PCMCIA.
For M-Cell products, the site id value will never be 0.

Setting subsystem to 2 for site 1
Process 0x95 (Temp CM) requested a self-initiated soft reset
!!!
REBOOT !!!
Reset due to self-initiated soft reset

PCMCIA: Intel Series 2+ Flash detected in socket 0
Turning caches on
caches are ON
MMI-ROM 0000 ->
MMI-ROM 0000 ->
MMI-RAM 1015 -> Waiting for System Initialization to complete.....
MMI-RAM 1015 ->
chg_l



MMI-RAM 1015 ->
MCU:emon_1015 %
MCU:emon_0000 %
MIP: In slot 0
MIP: Current seconds is 31.
MIP: Soft reset count read is 0.
MIP: Writing time 31, count 1.
MIP: Performing Soft Reset.
5-12
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 5-2
CM: DB size is = 2046040

CM: EXEC has just allocated DB space
CM: Stored DB Checksum
= 51a73f4
CM: Calculated DB Checksum = 51a73f4
CM: DB Validity: 0
CM: Send DB Status message to IP process.
CM: DB Status response from IP = 0.
CM: Site number 1, Subsystem 2
MIP: Starting creator
MCU:emon_1015 % MIP: Tag 0x00 indicates nv_write successful!
SAP CONFIGURED
NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 7, Link Mailbox id =
1005
NG EXEC DLSP dl_message_disc: DL_DISCONNECT_REQ SUCCESSFUL.
Waiting for confirm before deleting mbox. Channel = 7.
HDLC/set_t2_timer: NO chnls ACTIVE, dev index is 3
mSM: POOL SIZE = 95552
SM: PORT DATABASE INITIALIZED
SM: HASH TABLES INITIALIZED
mSM: Redundant MSW is OOS
<*><*><*> mSM & MSW(s) CONFIGURED <*><*><*>
NG EXEC DLSP dl_message_con: Control mailbox opened for channel 30,
= c0003120
NG EXEC DLSP dl_message_con: Control mailbox opened for channel 31, = c0003120
NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 30, Link Mailbox id
= 2017
= 2018
NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 1, Link Mailbox id=
1001
HDLC/set_t2_timer: NO chnls ACTIVE, dev index is 0
= 2017
= 2018
MIP: Starting codeload; getting list for cpu 0x2017.
MIP: Sending download OK no objects to load to CA for CPU 0x2017
MIP: Sending download OK no objects to load to CA for CPU 0x2018
MMI-RAM 1015 ->
68P02901W43-P
23 Feb 2004
5-13
GMR-01

6
At the MMI prompt, display the processor status information. Enter the command:
disp_p <site no.>
Where <site no.> is the site id of the M-Cellcity in the database.
For M-Cell products, the site id value will never be 0.
PROCESSOR STATUS INFORMATION FOR LOCATION 1:

OPER STATES:
D:Disabled E:Enabled
B:Busy
ADMIN STATES: L:Locked
U:Unlocked E:Equipped NE:Not Equipped
CPU#
Processor Name
State Reason
Related
Related
Device
Function
____
__________________ _____ _______________ ________ ________
1015
BTP 0 0
B-U
NO REASON
N/A
N/A
2017
DRI 0 0
E-U
GCLK Not Warm
N/A
N/A
2018
DRI 0 1
E-U
GCLK Not Warm
N/A
N/A
MCU:emon_1015 % SITE 0 initialization complete
MMI-RAM 1015 -> Database display commands accepted.
MMI-RAM 1015 -> Initialization complete. All commands accepted.
***** The MIP will wait for Gclk warm up timer to elapse before proceeding*****
***** This is currently 30 minutes *****
MMI-RAM 1015 ->
MMI-RAM 1015 ->disp_p <site no>
OPERSTATES: D:Disabled E:Enabled
B:Busy
U:Unlocked E:Equipped NE:Not
CPU#
Processor Name
State Reason
Related
Device
____
__________________ _____ _______________ _________
1015
BTP 0 0
B-U
NO REASON
N/A
2017
DRI 0 0 (RTF 0 0) B-U
NO REASON
N/A
2018
DRI 0 1 (RTF 0 1) E-U
NO REASON
N/A
Equipped
Related
Function
________
N/A
N/A
N/A

MMI-RAM 1015 ->
MMI-RAM 1015 -> Initialization complete.
MMI-RAM 1015 ->
MCU:emon_1015 %rlogin 2 2017hen
5-14
GMR-01
All commands accepted.
68P02901W43-P
23 Feb 2004
Procedure 5-2
7
Use the login command to view transceivers initialization. Enter the command:
rlogin <site id + 1> processor id
RSS:emon_2017% dri_activate: recd DRI_ACT for dri 0

send_abis_dri_act: sending a RSS_ABIS_ACT for DRI 0 to Abis.
send_ceb_activate: sending a ACTIVATE_REQ to CEB.
send_dri_act_suc: sending a DRI_ACTIV_SUCCESS for DRI 0 to FM.
send_chan_create: sending a CHAN_CREATE for DRI 0 to Layer 2.
prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 7, type: TCH (full rate)
prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 0, type: BCCH - SDCCH/4 combined
This completes the PCMCIA download.
68P02901W43-P
23 Feb 2004
5-15
GMR-01
Code download from BSC
This section describes the software download from BSC when the BSC has established a connection.
To perform a code download to an M-Cellcity, the BSC must be equipped with a CSFP facility.
BSC download procedure with example results

Use the following procedure to download software code from the BSC:
Procedure 5-3 BSC code download
1
Connect the E1/T1 link to the equipment.
Switch on the ac power.

Wait for the equipment to link to the BSC and verify that the normal download from the BSC takes place.
The BSCl overwrites the data in the PCMCIA card when it performs a normal download function.
The following is only be seen if there is an E1/T1 link to the BSC and the BSC holds a database
for the M-Cellcity site. The download takes approximately 30 minutes.
!!! REBOOT !!!

RSR =0xc0 PA12=0 PA11=1
Reset due to power reset
Checking DRAM: 16 of 16 MB complete
Motorola MCU Boot Software Version 1.4.0.6.5 15-Jul-96
Copyright 1996, Motorola Incorporated
Board type is MCU-micro
QUICC microcode revision 0x0082
PCMCIA: Socket 0 empty
Turning caches on
caches are ON
MMI-ROM 0000 ->
MMI-ROM 0000 -> y
MMI-ROM 1015 ->
5-16
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 5-3 BSC code download (Continued)

3
chg_l



4
Once level 3 access is confirmed switch to the executive monitor (EMON) by selecting keys CTRL and
N together.
At security level 3 the executive monitor (EMON) must be selected to view the download.
MCU:emon_1015 %
MCU:emon_0000 %
MIP: In slot 0
MIP: Performing Hard Reset.
MIP: Now master MCU...
MIP: Starting to contact BSC.
NG EXEC DLSP dl_message_con: Control mailbox opened
MCU:emon_1015 % NG EXEC_DLSP process_hdlc_msg: LINK
Link Mailbox id = 1001
MIP: HDLC link connected on frame 0, slot 0
MIP: CPU assigned ok on frame 0, slot 0
MIP: Link state 2
MIP: Query of NIU successful on frame 0, slot 0
MIP: NIU configured ok on frame 0, slot 0
MIP: Establishng second RSL from MCU to the BSC over
MIP: Activated LAPD on frame 0, slot 0
MIP: NIU configured ok on frame 0, slot 0, span 1
MIP: SAP open ok on frame 0, slot 0
NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for
9001
68P02901W43-P
23 Feb 2004
for channel 1,= c0003120

ESTABLISHED for channel 1,
NIU frame 0, slot 0, span 1

channel 5, Link Mailbox id=
5-17
GMR-01
Procedure 5-3
BSC code download (Continued)
MIP: HDLC link connected on frame 0, slot 0, span 1

MIP: Link state 2
MIP: Query of NIU successful on frame 0, slot 0, span 1
MIP: Activated LAPD on frame 0, slot 0, span 1
MIP: SAP open ok on frame 0, slot 0, span 1
MIP: Sending CA polling message
MIP: Bad EXEC DLSP return code 1
MIP: HDLC link failed to connect on frame 1, slot 0 with code 5
MIP: Received Subsystem State Query message. Subsystem = 2, level number 263e
MIP: BSC-MCELL Code Downloading in Progress...
MCU:emon_1015 %
Load version information not present
MCU:emon_1015 % Uncompressing MCU used objects
MIP: Code Downloading complete
MIP: Creating CM and MMI
MIP: Disconnecting RSL
NG EXEC DLSP dl_message_disc: DL_DISCONNECT_REQ SUCCESSFUL. Waiting for confirm
before deleting mbox. Channel = 1.
MIP: Terminate HDLC frame 1 slot 0 received
MMI-RAM 1015 ->
MMI-RAM 1015 ->
MMI-RAM 1015 -> Waiting for System Initialization to complete.
MMI-RAM 1015 -> Database display commands accepted.
MMI-RAM 1015 -> Initialization complete. All commands accepted.
MMI-RAM 1015 ->
MMI-RAM 1015 ->
chg_l
5-18
GMR-01
68P02901W43-P
23 Feb 2004

6
Once level 3 access is confirmed switch to the executive monitor (EMON) by selecting keys CTRL and N
together.
MCU:emon_1015 %
fore deleting mbox. Channel 3.
MIP: Leaving RSL thread
MIP: HDLC Link to the NIU disconnected successfully
MIP: Leaving second RSL thread
CM: DB size is 2046040
CM: EXEC has just allocated DB space
CM: Stored DB Checksum =51a701d
CM: Calculated DB Checksum =51a701d
CM: DB Validity: 0
CM: Send DB Status message to IP process
CM: DB status response from IP =11
CM: Set level number to x0 x0 x26 x3e per IP.
CM: Site number 1, Subsystem 2
CM: Reassigning DB for the site.
HDLC/sabm_timeout_func: Channel 3 not being established or SABMs are outstanding
Skipping transmit of SABM. Channel state is 0
HDLS/set_t2_timer: NO chnls ACTIVE, dev index is 1
MIP: Starting creator
NG EXEC DLSP dl_message_con: Control mailbox opened for channel 2, =c0003120.
NG EXEC DLSP dl_message_con: Control mailbox opened for channel 4, =c0003120
NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 4, Link Mailbox id
= 104
= 102
NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm
before deleting mbox. Channel = 2
= 107
= 106
= 109
= 108
before deleting mbox. Channel =8
NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 15, Link Mailbox
id = 10f
id = 10e
68P02901W43-P
23 Feb 2004
5-19
GMR-01
Procedure 5-3
BSC code download (Continued)

id = 115
id = 114
NG EXEC DLSP
id = 11f
id = 11e
SAP CONFIGURED
NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 7, Link Mailbox id =
1005
mSM: POOL SIZE = 95552
SM: PORT DATABASE INITIALISED
SM: HASH TABLES INITIALISED
mSM: Redundant MSW is OOS
<*><*>mSM &MSW(s) CONFIGURED <*><*>
NG EXEC dl_message_con: Control mailbox opened for channel 30, =c0003120.
id = 2017
id = 2018
1001
1001
CA ->RSL | received link CONNECT Indication, site=0
id = 2017
5-20
GMR-01
68P02901W43-P
23 Feb 2004

id = 2018
MIP: Sending download OK no objects to CA for CPU 0x2017
MIP: Sending download OK no objects to CA for CPU 0x2018
SITE 0 initialization complete
MCU:emon_1015 %
MCU:emon_1015 %
Once site initialization is complete, code objects can be viewed. At the EMON prompt enter the command:
O
Load version information not present

MCU:emon_1015 %
MCU:emon_1015 %
After 30 minutes, confirm the GCLK warm-up time has elapsed, by displaying the processor status information
for location 1 again. At the MMI prompt enter the command:
disp_p 1

OPER STATES: D:Disabled E:Enabled
B:Busy
U:Unlocked E:Equipped
CPU#
____
1015
2017
2018
Processor Name
State Reason
NE:Not Equipped
Related
Device
__________________ _____ _______________ _________
BTP 0 0
B-U
NO REASON
N/A
DRI 0 0 (RTF 0 0) B-U
NO REASON
N/A
DRI 0 1 (RTF 0 1) B-U
NO REASON
N/A
Related
Function
________
N/A
N/A
N/A
MMI-RAM 1015 ->
This completes the log of the download.
68P02901W43-P
23 Feb 2004
5-21
GMR-01
Site status check procedure
Use the following procedure to check the site status once it is fully operational:
Procedure 5-4
1
Check site status
Display the high level information of all sites supported in the BSS. At the MMI prompt enter the command:
disp_bss
OPER STATES: D:Disabled

E:Enabled
U:Unlocked
B:Busy
E:Equipped
NE:Not Equipped
S:Shutdown
SITE
FUNCTIONAL # OF
GSM CELL ID
FREQ BCCH
SITE STATE UNIT STATUS MCC MNC
LAC
CI
RAC TYPE FREQ
____ _____ _____________ ________________________ ___ ____ ____
0
B-U
UNAVAILABLE
UNAVAILABLE 543 21 1 (F111h 4 (1110h) N/A PGSM 40
1
B-U
CRITICAL
CRITICAL
543 21 1 (F111h 1 (1110h) N/A PGSM 87
Display the cell status for location 1. At the MMI prompt enter the command:
disp_cell_status 1
Start of report for LOCATION 1:

GSM CELL ID
MCC 543 MNC 21
LAC
CI
(dec)
61713
1368
(hex)
F111h
1110h
____________________________________________
Frequency Type
PGSM
BCCH Frequency
87
____________________________________________
Status
Barred
Reset in Prog
No
SPI in Prog
Yes
BSS BSSAP Prhb
Yes
MSC BSSAP Prbb
No
SPI/MSC SCCP Prhb
NA
AccClass Bar
NA
SDCCH
Norm Outer TCH/F
Norm Inner TCH/F
Ext Outer TCH/F
FREE
_____
3
15
0
0
INUSE
_____
1
0
0
0
UNAVL
_____
0
0
0
0
End of Report
5-22
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 5-4 Check site status (Continued)

3
Display the device status information for location 1. At the MMI prompt enter the command:
state 1
DEVICE STATUS INFORMATION FOR LOCATION 1:

OPER STATES:
B:Busy
Device
___________
CSFP 0 0 0
BTP 0 0 0
DRI 0 0 0
DRI 0 0 0
MSI 1 0 0
MMS 1 0 0
MMS 1 0 0
State
_____
D-U
B-U
B-U
B-U
B-U
B-U
D-U
RSL 0 0 0
GCLK 0 0 0
B-U
B-U
CAB 0 0 0
SITE 0 0 0
PATH 0 0 0
B-U
B-U
D-U
Reason
_______________
NO REASON
NO REASON
NO REASON
NO REASON
NO REASON
NO REASON
Synch Loss OSS
Timer
NO REASON
GCLK in Set
Freq. Mode
NO REASON
NO REASON
NO REASON
Last Transition
dd/mm hh:mm:ss
_______________
19/01 10:36:57
19/01 10:02:31
19/01 10:03:55
19/01 10:03:55
19/01 10:02:49
19/01 10:06:30
19/01 10:06:30
S:Shutdown
Related
Function
_________
None
None
RTF 0 0 0
RTF 0 1 0
None
None
None
22/01
19/08
10:46:52 None
10:24:44 None
19/01
19/01
22/01
08:02:23 None
08:04:51 None
08:46:51 None
FUNCTION STATUS INFORMATION FOR LOCATION 1

OPER STATES: E:Enabled B:Busy
ADMIN STATES: E:Equipped
Last Transition Related
Function
State Reason
dd/mm hh:mm:ss Device
___________ _____ _______________ _______________ _________
RTF 0 0 0
B-E
NO REASON
19/08 10:30:09 DRI 0 0 0
RTF 0 1 0
B-E
NO REASON
19/08 01:31:04 DRI 0 0 0
68P02901W43-P
23 Feb 2004
5-23
GMR-01
Battery check
Battery check
The objective of the battery check is to verify the serviceability of the battery in the
event of an ac mains power supply failure.
Before performing the battery test it is imperative that the battery is fully charged.
The battery takes a minimum of 12 hours to fully charge.

The battery check requires the following test equipment:
Commands used
The following command is to be used to carry out the procedure:
Function
Command
state
Battery test procedure

Use the following procedure to test the battery:
Procedure 5-5
Battery test
Ensure the 9-way to 37-way cable from serial A port (on the PC) to the user TTY MCU-m port
(37-way D-type located beside the HIM module) is connected
Switch off the ac mains supply to the M-Cellcity.
5-24
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 5-5
3
Battery check
Battery test (Continued)
Start terminal emulator, and at the MMI prompt enter the command:
state #
where # is the location id.
An example of this command would be
state 1
Device status information for location 1 is displayed:
DEVICE STATUS INFORMATION FOR LOCATION 1:
OPER STATES:
B:Busy
Device
___________
CSFP 0 0 0
BTP 0 0 0
DRI 0 0 0
DRI 0 0 0
MSI 1 0 0
MMS 1 0 0
MMS 1 0 0
State
_____
D-U
B-U
B-U
B-U
B-U
B-U
D-U
RSL 0 0 0
GCLK 0 0 0
B-U
B-U
CAB 0 0 0
SITE 0 0 0
PATH 0 0 0
B-U
B-U
D-U
Reason
_______________
NO REASON
NO REASON
NO REASON
NO REASON
NO REASON
NO REASON
Synch Loss OSS
Timer
NO REASON
GCLK in Set
Freq. Mode
NO REASON
NO REASON
NO REASON
Last Transition
dd/mm hh:mm:ss
_______________
19/01 10:36:57
19/01 10:02:31
19/01 10:03:55
19/01 10:03:55
19/01 10:02:49
19/01 10:06:30
19/01 10:06:30
S:Shutdown
Related
Function
_________
None
None
RTF 0 0 0
RTF 0 1 0
None
None
None
22/01
19/08
10:46:52 None
10:24:44 None
19/01
19/01
22/01
08:02:23 None
08:04:51 None
08:46:51 None
FUNCTION STATUS INFORMATION FOR LOCATION 1

OPER STATES: E:Enabled B:Busy
ADMIN STATES: E:Equipped
Last Transition Related
Function
State Reason
dd/mm hh:mm:ss Device
___________ _____ _______________ _______________ _________
RTF 0 0 0
B-E
NO REASON
19/08 10:30:09 DRI 0 0 0
RTF 0 1 0
B-E
NO REASON
19/08 01:31:04 DRI 0 0 0
Ensure that responses that should be BUSY and UNLOCKED are showing B-U.
68P02901W43-P
23 Feb 2004
Switch on the ac mains supply.
Disconnect the serial cable from the TTY port. This completes the test.
5-25
GMR-01
E1/T1 link check
E1/T1 link check
The E1/T1 link checks verify the integrity of the E1/T1 link back to the BSC/MSC.

The E1/T1 link checks require the following test equipment:
Commands used
The following command is to be used to carry out the procedure:
Function
Command
state
Preparation for checking the E1/T1 link

Use the following procedure to prepare the equipment to check the E1/T1 link:
Procedure 5-6
Prepare for E1/T1 link check
Enure the site is in call processing mode.
Ensure the 9-way to 37-way cable from serial A port (on the PC) to the user TTY
MCU-m port (37-way D-type located beside the HIM module) is connected.
The system and the hardware are now set up to check the E1/T1 link.
5-26
GMR-01
68P02901W43-P
23 Feb 2004
E1/T1 link check
E1/T1 test procedure

Use the following procedure to check the E1/T1 links:
Procedure 5-7
E1/T1 link test
the relevant Digital Distribution Frame (DDF) port.
Determine the site number, equipment list and MMS configuration.

state # MMS * * *
where:
# is location.
* is dev/func id.
An example of this command would be:
state 0 MMS 1 0 0
The system displays the following message from the MCU-m for location 0:
STATUS INFORMATION
Device: MMS 1 0 0
Reason code is : NO REASON
Related Device/Function: NONE
If this display shows UNLOCKED and BUSY, then the NIU-m port (MMS),
HIM-75/HIM-120, cabling and the E1/T1 link are all good.
If the loop is removed and the command re-entered, the result should be
UNLOCKED and DISABLED
The NIU-m requires a minimum of 20 seconds after receiving these

commands before it registers a change in status.
68P02901W43-P
23 Feb 2004
5-27
GMR-01
E1/T1 link check
Fitting chassis bottom cover

Use the following procedure to fit the chassis bottom cover after completion of all
necessary configuration checks:
Procedure 5-8
Fit chassis bottom cover
Using a clean, dry cloth, wipe out the inside of the chassis bottom cover to
remove any excess moisture.
Fit the chassis bottom cover onto the lower compartment, taking care not
todamage to the gasket seal.
Tighten the eleven M4 bolts around the edge of the chassis bottom cover.
5-28
GMR-01
68P02901W43-P
23 Feb 2004
MCU-m GCLK calibration
GCLK calibration can be carried out automatically using the CINDY commissioning tool.
Refer to the relevant CINDY user documentation for details.
Follow this procedure to calibrate the M-Cellcity and Horizonmicro2 MCU-m GCLK.

MCU-m GCLK calibration requires the following test equipment:
Frequency counter.
9-way to 37-way MCU cable for M-Cellcity or
9-way to 9-way MCU cable for Horizonmicro2.
MCU-m calibration procedure

Use the following procedure to calibrate an MCU-m GLCK:
Procedure 5-9 Calibrate MCU-m GCLK
1
Connect the 9-way to 37-way cable or 9-way to 9-way cable from serial A port on the PC to the
user TTY MCU-m port.
At the PC running the terminal emulator software the prompt SYNC-MMI should appear.
Connect the frequency counter to the 8 kHz (ref_125 s) BNC connector of the MCU TTY cable.
Attach a 10 MHz reference signal to the 10 MHz BNC input connector on the frequency counter.
Allow the MCU-m to warm up for 30 minutes or the OCXO will not
be stable.
68P02901W43-P
23 Feb 2004
5-29
GMR-01
Procedure 5-9 Calibrate MCU-m GCLK (Continued)

4
If the module is reset for any reason, this restarts the module 30 minute counter.
If this happens, enter the following command to force the sync section into the warmed-up state:
SYNC-MMI>dwarm
Enter the command:

SYNC-MMI>dcal
8000Hz source Connected, Enter y when ready, a to abort test>y
The frequency measured will be approximately but not exactly 8000.00000 Hz

6
Adjust the OCXO control voltage by typing +3...+2...+1...+0...-0...-1...2...-3 until the frequency is exactly 8000.00000 Hz:
Enter a to abort, s to save, +[0..3] to inc, -[0..3] to dec>+2
These numbers as entered relate to orders of magnitude. For example, typing +3

causes an increase ten times bigger than that caused by typing +2.The entries +0
and -0 are both valid.
7
When the ref_125 s frequency is exactly 8000.00000 Hz, specify save as follows:
Enter a to abort, s to save, +[0..3] to inc, -[0..3] to dec>s
Thecalibration program sets the output frequencies to various different values and now requests
that you type in the values of the output frequency at various points:
Dac set to 1.0 volts, Enter Freq value or a to abort>7999.99673
Calibration Gain 0.37345 RETURN
SYNC-MMI>
This ends the calibration procedure.
5-30
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
6
Base site integration
Once a base site has been installed and its hardware optimized, the base site call handling qualities
must be tested and all traffic channels available for call processing established.
This chapter details three ways of integrating a GSM base site:
When logging software such as LOMS is available.
When logging software is not available.
When the base site is not connected to a mobile switching centre (MSC).
In this chapter transceiver is used to mean DRCU, DRCUII, DRCU3, SCU, TCU, TCU-B or CTU.
68P02901W43-P
23 Feb 2004
6-1
GMR-01
Introduction to base site integration
Introduction to base site integration
Hazardous voltages in excess of 50 V dc exist inside -48 V and -60 V cabinets.

Use extreme caution when working on a cabinet with power applied.
Remove all rings, watches and other jewellery.
Once a base site has been installed and its hardware optimized, the base site call handling qualities must
be tested and all traffic channels available for call processing must be established.
Use the appropriate one of the following methods to integrate a base site into a GSM network:
"Base site integration using logging software" on page 6-5 when logging
software such as LOMS is available.
"Base site integration without logging software" on page 6-9 when logging
software is not available.
"Base site integration without an MSC connection" on page 6-13 when the base site
is not connected to a mobile switching centre (MSC).
In this chapter transceiver is used to mean DRCU, DRCUII, DRCU3, SCU, TCU, TCU-B or CTU.

CINDY commissioning tool. Refer to the relevant CINDY documentation for details.
6-2
GMR-01
68P02901W43-P
23 Feb 2004
This section provides information on the test equipment required for the base site
integration procedures in this chapter.


Table 6-1 lists the equipment required for base site integration.
Table 6-1
Base site integration equipment

Description
Quantity
68P02901W43-P
23 Feb 2004
Comments

(PC)
Commercial terminal emulator software
LOMS or TEMS logging software
Must be compatible with test mobile.
Tekelec switch simulator
Test mobile
Engineering SIM card
PC to test mobile interface cable.
Orbitel 901 or Ericsson EH337 GSM MS

with registered SIM card
6-3
GMR-01
Test leads required

A suitable interface cable is required to connect the PC to the test mobile. The connections will depend on
the make and model of the test mobile, refer to the manufacturer-specific information for details.
6-4
GMR-01
68P02901W43-P
23 Feb 2004
Base site integration using logging software
Follow this procedure to integrate a base site using logging software such as LOMS or TEMS.

The following test equipment and result forms are required for base site integration
when the base site is connected to an MSC:
Appropriate logging software such as LOMS or TEMS. The logging software

must be compatible with the test mobile used.
Interface cable to connect the test mobile to the PC.
Suitable test mobile e.g. Orbitel 901 or Ericsson EH337 with a registered SIM card.
Site integration forms.
Commands used
No special commands are required.
Preparation for integration

Use the following procedure to prepare for integration:
Procedure 6-1
1
Contact the OMC and verify the frequencies and base station identity code
(BSIC) allocated to the base site under test and ensure that the base site is active
and transmitting.
Ensure that both members of the team have:
68P02901W43-P
23 Feb 2004
Prepare for integration with logging software
The base site landline telephone number.
Each others test mobile telephone numbers.
Position one member of the team at the base site.
6-5
GMR-01
Procedure 6-1 Prepare for integration with logging software (Continued)

4
Connect the PC to the test mobile and start the logging software. Consult the
software manufacturer user guide before using the logging software. Set the
logging software to show:
Serving cell.
Serving and neighbouring cells.
Dedicated channel.
Radio environment.
Open a log file before initiating any tests. The format for the log file filename is:
<4 digit site id><4 character sitename>.LOG
For example:0037stre.LOG
Test calls must not be made by the driver of a motor

vehicle while the vehicle is in motion.
6
Ensure that the engineer making the test calls (the mobile calling party) is
stationed at least 1 km away from the base site (100 m from a microcellular site)
and, on a sectored site, within the correct cell coverage area.
Obtaining channel/timeslot information

Use the following procedure to obtain channel/timeslot information:
Procedure 6-2
1
Obtain channel/timeslot information for integration with logging software
Using the serving cell and serving and neighbouring cell displays, ensure that:
The mobile is locked to sector A absolute radio frequency channel number

(ARFCN).
Sectors B and C ARFCNs andbase station identity codes (BSIC) are

displayed.
Note all sector Rx levels on the site integration form.
Set up a MS to land call.
6-6
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 6-2
(Continued)
4
Obtain channel/timeslot information for integration with logging software
Using the dedicated channel display, note the following on the site integration
form:
ARFCN.
Timeslot number.
Subchannel number.
Channel type.
Channel mode.
Using the radio environment display, note the following on the site integration
form:
Rx level.
Rx quality (in range 0 to 7, 0 = good 7 = bad).
Timing advance (in range 0 to 2).
Tx power (in range 0 to 15, 15 = minimum MS power).
Repeat step 3 to step 5 until all SD subchannels and TCH timeslots have been
verified.
Timeslot 0 of the BCCH carrier will not be allocated as a traffic

channel. Timeslot 1 of the BCCH carrier may be configured as an
SDCCH, in which case it will not be allocated as a traffic channel.
Carrier 00 is on transceiver 0 (first transceiver in sector A or in
omni-site).
Carrier 01 is on transceiver 1 (second transceiver in sector A or in
omni-site, or first transceiver in sector B).
On sectors with more than one transceiver ensure that all transceiver
timeslots are tested, non BCCH transceivers will be seen as next
carrier in sequence.
68P02901W43-P
23 Feb 2004
If the cell has only one transceiver, go to step 10. For cells with more than one
transceiver, carry out step 8 to step 10.
Request the OMC to take the transceiver with the BCCH carrier out of service.
Check that the BCCH carrier is now available on another transceiver.
10
Request the OMC to put the transceiver taken out of service in stepback into
service.
6-7
GMR-01
Intra/inter-cell handover test procedure

Use the following procedure to carry out handover tests:
Procedure 6-3
1
Intra/inter-cell handover test for integration with logging software
Request the OMC to call the test mobile to verify correct cell allocation.

2
If the base site under test is sectored, continue the call made in step 1 while
walking/driving into the next sector and verify that intra-cell handover is achieved
and that the call is assigned to the correct carrier.
Repeat step 1 to step 2 for all sectors. When all sectors have been tested,
walk/drive in the opposite direction to ensure that handovers are correct to/from
all cells.
Make a call from the test mobile to the emergency operator and, where
appropriate, request a record (for example a zone code). Note this on the site
integration form.
Make a call from the test mobile to the base site landline telephone, then
walk/drive towards a neighbouring base site and verify, using the logging
software, that an inter-cell handover is achieved.
Once the handover has been achieved, walk/drive back towards the base site
under test and verify that a handover is achieved.
Verify that handovers are possible to all neighbouring sites.The OMC can supply
ARFCN and BSIC of any neighbouring sites.
When the test is complete, inform the OMC of any problems.
6-8
GMR-01
68P02901W43-P
23 Feb 2004
Base site integration without logging software
Follow this procedure to integrate a base site without using logging software.

The following test equipment is required when logging software is not available:
Test mobile with registered SIM card.
Engineering SIM card.
Commands used

Procedure 6-4 Prepare for integration without logging software
1
Contact the OMC and verify the frequencies and base station identity code
(BSIC) allocated to the base site under test and ensure that the base site is active
and transmitting.
68P02901W43-P
23 Feb 2004
Request the OMC to remotely log in (rlogin) to the base site under test and set:
iir_mod 32 0Fch filter
6-9
GMR-01
Procedure 6-4 Prepare for integration without logging software (Continued)

4

5

Procedure 6-5 Obtain channel/timeslot information for integration without logging software
1
Insert the engineering SIM card into the test mobile.
Check that the MS can synchronize to the BCCH.
Check that the frequency allocation is correct.
Measure the signal strength of each BCCH carrier on the BTS.
Replace the engineering SIM card with the registered SIM card.
Set up a mobile to land call.
Request the OMC to display and note:
Carrier number.
Timeslot number.
Subchannel number.
Channel type.
6-10
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 6-5
(Continued)
8
Obtain channel/timeslot information for integration without logging software
Repeat step 6 and step 7 until all SD subchannels and TCH timeslots have been
verified.

omni-site)
omni-site or first transceiver in sector B).
9
transceiver, carry out step 10to step 12.
10
11
12
service.

Procedure 6-6
1
Intra/inter cell handover test for integration without logging software

68P02901W43-P
23 Feb 2004
If the base site under test is sectored, continue the call made in step 1while
Repeat step 1 to step 2 for all sectors.On completion of the testing of all sectors,
walk/drive in the reverse direction to ensure that handovers are correct to/from
all cells.
appropriate, request a record, for example, a zone code.Record this on the site
integration form.
6-11
GMR-01
Procedure 6-6 Intra/inter cell handover test for integration without logging software (Continued)
5
If neighbour sites are available carry out step 6 to step 8.

If not, go to step 9.
Make a call from the test mobile to the base site landline telephone, the mobile
calling party should then walk/drive toward a neighbouring base site and verify
that an inter-cell handover is achieved.
Use the engineering SIM card to verify neighbour site frequencies.
Once the handover has been achieved, the mobile calling party should walk/drive
back toward the base site under test and verify that a hand over is achieved.
Request the OMC to remote login (rlogin) to the base site under test and set:
iir_mod 32 00
10
On completion of the test, inform the OMC of any problems.
6-12
GMR-01
68P02901W43-P
23 Feb 2004
Follow this procedure to integrate a base site when the base site is not connected
to a mobile switching centre (MSC).

The following test equipment is required when the base site is not connected to an MSC:
Test mobile with registered SIM card.
Engineering SIM card.
Tekelec switch simulator.
Commands used

Procedure 6-7 Prepare for integration without MSC connection
68P02901W43-P
23 Feb 2004
Contact the OMC or BSC and verify the frequencies and base station identity
code (BSIC) allocated to the base site under test and ensure that the base site is
active and transmitting.
Request the OMC to connect the E1/T1 lines from the BSC to a Tekelec to
simulate the operation of an MSC.
iir_mod 32 0Fch
6-13
GMR-01
Procedure 6-7 Prepare for integration without MSC connection (Continued)

5

6

Procedure 6-8 Obtain channel/timeslot information for integration without MSC connection
1
Insert the engineering SIM card into the test mobile.
Check that the MS can synchronize to the BCCH
Check that the frequency allocation is correct.
Measure the signal strength of each BCCH carrier on the BTS.
Replace the engineering SIM card with the registered SIM card.
Set up a mobile to land call.
Request the OMC to display and note:
Carrier number.
Timeslot number.
Subchannel number.
Channel type.
6-14
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 6-8
(Continued)
8
Obtain channel/timeslot information for integration without MSC connection
Repeat step 6 and step 7 until all SD subchannels and TCH timeslots have been
verified.

omni-site)
omni-site or first transceiver in sector B).
9
transceiver, carry out step 10 to step 12.
10
11
12
service.

Procedure 6-9
1
Intra/inter-cell handover test for integration without MSC connection

68P02901W43-P
23 Feb 2004
If the base site under test is sectored, continue the call made in step 1 while
Repeat step 1 to step 2 for all sectors. On completion of the testing of all sectors,
walk/drive in the reverse direction to ensure that handovers are correct to/from
all cells.
appropriate, request a record, for example, a zone code.Record this on the site
integration form.
6-15
GMR-01
Procedure 6-9 Intra/inter-cell handover test for integration without MSC connection (Continued)
5
If neighbour sites are available carry out step 6 to step 8.

If not, go to step 9.
Make a call from the test mobile to the base site landline telephone, the mobile
calling party should then walk/drive toward a neighbouring base site and verify
that an inter-cell handover is achieved.
Use the engineering SIM card to verify neighbour site frequencies.
Once the handover has been achieved, the mobile calling party should walk/drive
back toward the base site under test and verify that a handover is achieved.
iir_mod 32 00
10
On completion of the test inform the OMC of any problems.
6-16
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
7
Channel numbers and frequencies
The transceivers used in the Motorola BSS may be used in PGSM, EGSM, GSM850, DCS1800
or PCS1900 frequency bands dependent on the equipment capability.
This chapter lists all channels and frequencies for each of the following channel types:
68P02901W43-P
23 Feb 2004
PGSM The standard GSM frequency range.
EGSM The extended GSM frequency range.
GSM850 The GSM850 frequency range.
DCS1800 The standard 1800MHz frequency range.
PCS1900 The higher frequency range allocated in countries such as the USA.
7-1
GMR-01
Introduction to channels and frequencies
Introduction to channels and frequencies
In the following sections, the channel numbers with their respective receive and transmit frequencies are shown
in tables each containing a block of ten channels maximum. The table title indicates the range of channels listed.
Refer to section:
"PGSM channel numbers and frequencies" on page 7-3 for the standard GSM frequency range.
"Extended GSM channel numbers and frequencies" on page 7-10 for the
extended GSM frequency range.
"GSM850 channel numbers and frequencies" on page 7-13 for the GSM850 frequency range.
"DCS1800 channel numbers and frequencies" on page 7-20 for the standard
1800MHz frequency range.
"PCS1900 channel numbers and frequencies" on page 7-40 for the higher frequency
range allocated in countries such as the USA.
7-2
GMR-01
68P02901W43-P
23 Feb 2004
PGSM channel numbers and frequencies
Channels 1 to 124
This section lists all the frequencies used in PGSM, with their channel numbers shown
in both decimal and hexadecimal notation.
Channels 1-10
Table 7-1 shows the frequencies for PGSM channels 1 to 10.
Table 7-1 PGSM channels 1 to 10
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
01
890.20
935.20
02
890.40
935.40
03
890.60
935.60
04
890.80
935.80
05
891.00
936.00
06
891.20
936.20
07
891.40
936.40
08
891.60
936.60
09
891.80
936.80
10
0A
892.00
937.00
7-3
GMR-01
Channels 11-20
Table 7-2
PGSM channels 11 to 20
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
11
0B
892.20
937.20
12
0C
892.40
937.40
13
0D
892.60
937.60
14
0E
892.80
937.80
15
0F
893.00
938.00
16
10
893.20
938.20
17
11
893.40
938.40
18
12
893.60
938.60
19
13
893.80
938.80
20
14
894.00
939.00
Channels 21-30
Table 7-3
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
21
15
894.20
939.20
22
16
894.40
939.40
23
17
894.60
939.60
24
18
894.80
939.80
25
19
895.00
940.00
26
1A
895.20
940.20
27
1B
895.40
940.40
28
1C
895.60
940.60
29
1D
895.80
940.80
30
1E
896.00
941.00
7-4
GMR-01
68P02901W43-P
23 Feb 2004
Channels 31-40
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
31
1F
896.20
941.20
32
20
896.40
941.40
33
21
896.60
941.60
34
22
896.80
941.80
35
23
897.00
942.00
36
24
897.20
942.20
37
25
897.40
942.40
38
26
897.60
942.60
39
27
897.80
942.80
40
28
898.00
943.00
Channels 41-50
Table 7-5
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
41
29
898.20
943.20
42
2A
898.40
943.40
43
2B
898.60
943.60
44
2C
898.80
943.80
45
2D
899.00
944.00
46
2E
899.20
944.20
47
2F
899.40
944.40
48
30
899.60
944.60
49
31
899.80
944.80
50
32
900.00
945.00
7-5
GMR-01
Channels 51-60
Table 7-6
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
51
33
900.20
945.20
52
34
900.40
945.40
53
35
900.60
945.60
54
36
900.80
945.80
55
37
901.00
946.00
56
38
901.20
946.20
57
39
901.40
946.40
58
3A
901.60
946.60
59
3B
901.80
946.80
60
3C
902.00
947.00
Channels 61-70
Table 7-7
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
61
3D
902.20
947.20
62
3E
902.40
947.40
63
3F
902.60
947.60
64
40
902.80
947.80
65
41
903.00
948.00
66
42
903.20
948.20
67
43
903.40
948.40
68
44
903.60
948.60
69
45
903.80
948.80
70
46
904.00
949.00
7-6
GMR-01
68P02901W43-P
23 Feb 2004
Channels 71-80
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
71
47
904.20
949.20
72
48
904.40
949.40
73
49
904.60
949.60
74
4A
904.80
949.80
75
4B
905.00
950.00
76
4C
905.20
950.20
77
4D
905.40
950.40
78
4E
905.60
950.60
79
4F
905.80
950.80
80
50
906.00
951.00
Channels 81-90
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
81
51
906.20
951.20
82
52
906.40
951.40
83
53
906.60
951.60
84
54
906.80
951.80
85
55
907.00
952.00
86
56
907.20
952.20
87
57
907.40
952.40
88
58
907.60
952.60
89
59
907.80
952.80
90
5A
908.00
953.00
7-7
GMR-01
Channels 91-100
Table 7-10

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
91
5B
908.20
953.20
92
5C
908.40
953.40
93
5D
908.60
953.60
94
5E
908.80
953.80
95
5F
909.00
954.00
96
60
909.20
954.20
97
61
909.40
954.40
98
62
909.60
954.60
99
63
909.80
954.80
100
64
910.00
955.00
Channels 101-110
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
101
65
910.20
955.20
102
66
910.40
955.40
103
67
910.60
955.60
104
68
910.80
955.80
105
69
911.00
956.00
106
6A
911.20
956.20
107
6B
911.40
956.40
108
6C
911.60
956.60
109
6D
911.80
956.80
110
6E
912.00
957.00
7-8
GMR-01
68P02901W43-P
23 Feb 2004
Channels 111-120
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
111
6F
912.20
957.20
112
70
912.40
957.40
113
71
912.60
957.60
114
72
912.80
957.80
115
73
913.00
958.00
116
74
913.20
958.20
117
75
913.40
958.40
118
76
913.60
958.60
119
77
913.80
958.80
120
78
914.00
959.00
Channels 121-124
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
121
79
914.20
959.20
122
7A
914.40
959.40
123
7B
914.60
959.60
124
7C
914.80
959.80
7-9
GMR-01
Channels 975 to 1023 and channel 0

This section lists all the extra frequencies used in Extended GSM (EGSM), with their channel
numbers shown in both decimal and hexadecimal notation. EGSM also uses all frequencies
listed in PGSM channel numbers and frequencies.
Channels 975-984
Table 7-14 shows the frequencies for EGSM channels 975 to 984.
Table 7-14
EGSM channels 975 to 984

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
975
3CF
880.20
925.20
976
3D0
880.40
925.40
977
3D1
880.60
925.60
978
3D2
880.80
925.80
979
3D3
881.00
926.00
980
3D4
881.20
926.20
981
3D5
881.40
926.40
982
3D6
881.60
926.60
983
3D7
881.80
926.80
984
3D8
882.00
927.00
7-10
GMR-01
68P02901W43-P
23 Feb 2004
Channels 985-994
Table 7-15 EGSM channels 985 to 994
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
985
3D9
882.20
927.20
986
3DA
882.40
927.40
987
3DB
882.60
927.60
988
3DC
882.80
927.80
989
3DD
883.00
928.00
990
3DE
883.20
928.20
991
3DF
883.40
928.40
992
3E0
883.60
928.60
993
3E1
883.80
928.80
994
3E2
884.00
929.00
Channels 995-1004
Table 7-16 EGSM channels 995 to 1004
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
995
3E3
884.20
929.20
996
3E4
884.40
929.40
997
3E5
884.60
929.60
998
3E6
884.80
929.80
999
3E7
885.00
930.00
1000
3E8
885.20
930.20
1001
3E9
885.40
930.40
1002
3EA
885.60
93.60
1003
3EB
885.80
930.80
1004
3EC
886.00
931.00
7-11
GMR-01
Channels 1005-1014
Table 7-17

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
1005
3ED
886.20
931.20
1006
3EE
886.40
931.40
1007
3EF
886.60
931.60
1008
3F0
886.80
931.80
1009
3F1
887.00
932.00
1010
3F2
887.20
932.20
1011
3F3
887.40
932.40
1012
3F4
887.60
932.60
1013
3F5
887.80
932.80
1014
3F6
888.00
933.00
Channels 1015-0
Table 7-18

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
1015
3F7
888.20
933.20
1016
3F8
888.40
933.40
1017
3F9
888.60
933.60
1018
3FA
888.80
933.80
1019
3FB
889.00
934.00
1020
3FC
889.20
934.20
1021
3FD
889.40
934.40
1022
3FE
889.60
934.60
1023
3FF
889.80
934.80
890.00
935.00
7-12
GMR-01
68P02901W43-P
23 Feb 2004
GSM850 channel numbers and frequencies
Channels 128 to 251

This section lists all the frequencies used in GSM850, with their channel numbers shown
Channels 128-130
Table 7-19 shows the frequencies for GSM850 channels 128-130.
Table 7-19 GSM850 channels 128 to 130
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
128
80
824.20
869.20
129
81
824.40
869.40
130
82
824.60
869.60
Channels 131-140
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
131
83
824.80
869.80
132
84
825.00
870.00
133
85
825.20
870.20
134
86
825.40
870.40
135
87
825.60
870.60
136
88
825.80
870.80
137
89
826.00
871.00
138
8A
826.20
871.20
139
8B
826.40
871.40
140
8C
826.60
871.60
7-13
GMR-01
Channels 141-150
Table 7-21
GSM850 channels 141 to 150

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
141
8D
826.80
871.80
142
8E
827.00
872.00
143
8F
827.20
872.20
144
90
827.40
872.40
145
91
827.60
872.60
146
92
827.80
872.80
147
93
828.00
873.00
148
94
828.20
873.20
149
95
828.40
873.40
150
96
828.60
873.60
Channels 151-160
Table 7-22

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
151
97
828.80
873.80
152
98
829.00
874.00
153
99
829.20
874.20
154
9A
829.40
874.40
155
9B
829.60
874.60
156
9C
829.80
874.80
157
9D
830.00
875.00
158
9E
830.20
875.20
159
9F
830.40
875.40
160
A0
830.60
875.60
7-14
GMR-01
68P02901W43-P
23 Feb 2004
Channels 161-170
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
161
A1
830.80
875.80
162
A2
831.00
876.00
163
A3
831.20
876.20
164
A4
831.40
876.40
165
A5
831.60
876.60
166
A6
831.80
876.80
167
A7
832.00
877.00
168
A8
832.20
877.20
169
A9
832.40
877.40
170
AA
832.60
877.60
Channels 171-180
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
171
AB
832.80
877.80
172
AC
833.00
878.00
173
AD
833.20
878.20
174
AE
833.40
878.40
175
AF
833.60
878.60
176
B0
833.80
878.80
177
B1
834.00
879.00
178
B2
834.20
879.20
179
B3
834.40
879.40
180
B4
834.60
879.60
7-15
GMR-01
Channels 181-190
Table 7-25

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
181
B5
834.80
879.80
182
B6
835.00
880.00
183
B7
835.20
880.20
184
B8
835.40
880.40
185
B9
835.60
880.60
186
BA
835.80
880.80
187
BB
836.00
881.00
188
BC
836.20
881.20
189
BD
836.40
881.40
190
BE
836.60
881.60
Channels 191-200
Table 7-26

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
191
BF
836.80
881.80
192
C0
837.00
882.00
193
C1
837.20
882.20
194
C2
837.40
882.40
195
C3
837.60
882.60
196
C4
837.80
882.80
197
C5
838.00
883.00
198
C6
838.20
883.20
199
C7
838.40
883.40
200
C8
838.60
883.60
7-16
GMR-01
68P02901W43-P
23 Feb 2004
Channels 201-210
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
201
C9
838.80
883.80
202
CA
839.00
884.00
203
CB
839.20
884.20
204
CC
839.40
884.40
205
CD
839.60
884.60
206
CE
839.80
884.80
207
CF
840.00
885.00
208
D0
840.20
885.20
209
D1
840.40
885.40
210
D2
840.60
885.60
Channels 211-220
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
211
D3
840.80
885.80
212
D4
841.00
886.00
213
D5
841.20
886.20
214
D6
841.40
886.40
215
D7
841.60
886.60
216
D8
841.80
886.80
217
D9
842.00
887.00
218
DA
842.20
887.20
219
DB
842.40
887.40
220
DC
842.60
887.60
7-17
GMR-01
Channels 221-230
Table 7-29

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
221
DD
842.80
887.80
222
DE
843.00
888.00
223
DF
843.20
888.20
224
E0
843.40
888.40
225
E1
843.60
888.60
226
E2
843.80
888.80
227
E3
844.00
889.00
228
E4
844.20
889.20
229
E5
844.40
889.40
230
E6
844.60
889.60
Channels 231-240
Table 7-30

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
231
E7
844.80
889.80
232
E8
845.00
890.00
233
E9
845.20
890.20
234
EA
845.40
890.40
235
EB
845.60
890.60
236
EC
845.80
890.80
237
ED
846.00
891.00
238
EE
846.20
891.20
239
EF
846.40
891.40
240
F0
846.60
891.60
7-18
GMR-01
68P02901W43-P
23 Feb 2004
Channels 241-251
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
241
F1
846.80
891.80
242
F2
847.00
892.00
243
F3
847.20
892.20
244
F4
847.40
892.40
245
F5
847.60
892.60
246
F6
847.80
892.80
247
F7
848.00
893.00
248
F8
848.20
893.20
249
F9
848.40
893.40
250
FA
848.60
893.60
251
FB
848.80
893.80
7-19
GMR-01
DCS1800 channel numbers and frequencies
Channels 512 to 885

This section lists the frequencies used in DCS1800, with their channel numbers shown
Channels 512-520
Table 7-32 shows the frequencies for DCS1800 channels 512 to 520.
Table 7-32
DCS 1800 channels 512 to 520

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
512
200
1710.2
1805.2
513
201
1710.4
1805.4
514
202
1710.6
1805.6
515
203
1710.8
1805.8
516
204
1711.0
1806.0
517
205
1711.2
1806.2
518
206
1711.4
1806.4
519
207
1711.6
1806.6
520
208
1711.8
1806.8
7-20
GMR-01
68P02901W43-P
23 Feb 2004
Channels 521-530
Table 7-33 DCS 1800 channels 521 to 530
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
521
209
1712.0
1807.0
522
20A
1712.2
1807.2
523
20B
1712.4
1807.4
524
20C
1712.6
1807.6
525
20D
1712.8
1807.8
526
20E
1713.0
1808.0
527
20F
1713.2
1808.2
528
210
1713.4
1808.4
529
211
1713.6
1808.6
530
212
1713.8
1808.8
Channels 531-540
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
531
213
1714.0
1809.0
532
214
1714.2
1809.2
533
215
1714.4
1809.4
534
216
1714.6
1809.6
535
217
1714.8
1809.8
536
218
1715.0
1810.0
537
219
1715.2
1810.2
538
21A
1715.4
1810.4
539
21B
1715.6
1810.6
540
21C
1715.8
1810.8
7-21
GMR-01
Channels 541-550
Table 7-35

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
541
21D
1716.0
1811.0
542
21E
1716.2
1811.2
543
21F
1716.4
1811.4
544
220
1716.6
1811.6
545
221
1716.8
1811.8
546
222
1717.0
1812.0
547
223
1717.2
1812.2
548
224
1717.4
1812.4
549
225
1717.6
1812.6
550
226
1717.8
1812.8
Channels 551-560
Table 7-36

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
551
227
1718.0
1813.0
552
228
1718.2
1813.2
553
229
1718.4
1813.4
554
22A
1718.6
1813.6
555
22B
1718.8
1813.8
556
22C
1719.0
1814.0
557
22D
1719.2
1814.2
558
22E
1719.4
1814.4
559
22F
1719.6
1814.6
560
230
1719.8
1814.8
7-22
GMR-01
68P02901W43-P
23 Feb 2004
Channels 561-570
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
561
231
1720.0
1815.0
562
232
1720.2
1815.2
563
233
1720.4
1815.4
564
234
1720.6
1815.6
565
235
1720.8
1815.8
566
236
1721.0
1816.0
567
237
1721.2
1816.2
568
238
1721.4
1816.4
569
239
1721.6
1816.6
570
23A
1721.8
1816.8
Channels 571-580
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
571
23B
1722.0
1817.0
572
23C
1722.2
1817.2
573
23D
1722.4
1817.4
574
23E
1722.6
1817.6
575
23F
1722.8
1817.8
576
240
1723.0
1818.0
577
241
1723.2
1818.2
578
242
1723.4
1818.4
579
243
1723.6
1818.6
580
244
1723.8
1818.8
7-23
GMR-01
Channels 581-590
Table 7-39

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
581
245
1724.0
1819.0
582
246
1724.2
1819.2
583
247
1724.4
1819.4
584
248
1724.6
1819.6
585
249
1724.8
1819.8
586
24A
1725.0
1820.0
587
24B
1725.2
1820.2
588
24C
1725.4
1820.4
589
24D
1725.6
1820.6
590
24E
1725.8
1820.8
Channels 591-600
Table 7-40

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
591
24F
1726.0
1821.0
592
250
1726.2
1821.2
593
251
1726.4
1821.4
594
252
1726.6
1821.6
595
253
1726.8
1821.8
596
254
1727.0
1822.0
597
255
1727.2
1822.2
598
256
1727.4
1822.4
599
257
1727.6
1822.6
600
258
1727.8
1822.8
7-24
GMR-01
68P02901W43-P
23 Feb 2004
Channels 601-610
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
601
259
1728.0
1823.0
602
25A
1728.2
1823.2
603
25B
1728.4
1823.4
604
25C
1728.6
1823.6
605
25D
1728.8
1823.8
606
25E
1729.0
1824.0
607
25F
1729.2
1824.2
608
260
1729.4
1824.4
609
261
1729.6
1824.6
610
262
1729.8
1824.8
Channels 611-620
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
611
263
1730.0
1825.0
612
264
1730.2
1825.2
613
265
1730.4
1825.4
614
266
1730.6
1825.6
615
267
1730.8
1825.8
616
268
1731.0
1826.0
617
269
1731.2
1826.2
618
26A
1731.4
1826.4
619
26B
1731.6
1826.6
620
26C
1731.8
1826.8
7-25
GMR-01
Channels 621-630
Table 7-43

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
621
26D
1732.0
1827.0
622
26E
1732.2
1827.2
623
26F
1732.4
1827.4
624
270
1732.6
1827.6
625
271
1732.8
1827.8
626
272
1733.0
1828.0
627
273
1733.2
1828.2
628
274
1733.4
1828.4
629
275
1733.6
1828.6
630
276
1733.8
1828.8
Channels 631-640
Table 7-44

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
631
277
1734.0
1829.0
632
278
1734.2
1829.2
633
279
1734.4
1829.4
634
27A
1734.6
1829.6
635
27B
1734.8
1829.8
636
27C
1735.0
1830.0
637
27D
1735.2
1830.2
638
27E
1735.4
1830.4
639
27F
1735.6
1830.6
640
280
1735.8
1830.8
7-26
GMR-01
68P02901W43-P
23 Feb 2004
Channels 641-650
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
641
281
1736.0
1831.0
642
282
1736.2
1831.2
643
283
1736.4
1831.4
644
284
1736.6
1831.6
645
285
1736.8
1831.8
646
286
1737.0
1832.0
647
287
1737.2
1832.2
648
288
1737.4
1832.4
649
289
1737.6
1832.6
650
28A
1737.8
1832.8
Channels 651-660
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
651
28B
1738.0
1833.0
652
28C
1738.2
1833.2
653
28D
1738.4
1833.4
654
28E
1738.6
1833.6
655
28F
1738.8
1833.8
656
290
1739.0
1834.0
657
291
1739.2
1834.2
658
292
1739.4
1834.4
659
293
1739.6
1834.6
660
294
1739.8
1834.8
7-27
GMR-01
Channels 661-670
Table 7-47

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
661
295
1740.0
1835.0
662
296
1740.2
1835.2
663
297
1740.4
1835.4
664
298
1740.6
1835.6
665
299
1740.8
1835.8
666
29A
1741.0
1836.0
667
29B
1741.2
1836.2
668
29C
1741.4
1836.4
669
29D
1741.6
1836.6
670
29E
1741.8
1836.8
Channels 671-680
Table 7-48

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
671
29F
1742.0
1837.0
672
2A0
1742.2
1837.2
673
2A1
1742.4
1837.4
674
2A2
1742.6
1837.6
675
2A3
1742.8
1837.8
676
2A4
1743.0
1838.0
677
2A5
1743.2
1838.2
678
2A6
1743.4
1838.4
679
2A7
1743.6
1838.6
680
2A8
1743.8
1838.8
7-28
GMR-01
68P02901W43-P
23 Feb 2004
Channels 681-690
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
681
2A9
1744.0
1839.0
682
2AA
1744.2
1839.2
683
2AB
1744.4
1839.4
684
2AC
1744.6
1839.6
685
2AD
1744.8
1839.8
686
2AE
1745.0
1840.0
687
2AF
1745.2
1840.2
688
2B0
1745.4
1840.4
689
2B1
1745.6
1840.6
690
2B2
1745.8
1840.8
Channels 691-700
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
691
2B3
1746.0
1841.0
692
2B4
1746.2
1841.2
693
2B5
1746.4
1841.4
694
2B6
1746.6
1841.6
695
2B7
1746.8
1841.8
696
2B8
1747.0
1842.0
697
2B9
1747.2
1842.2
698
2BA
1747.4
1842.4
699
2BB
1747.6
1842.6
700
2BC
1747.8
1842.8
7-29
GMR-01
Channels 701-710
Table 7-51

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
701
2BD
1748.0
1843.0
702
2BE
1748.2
1843.2
703
2BF
1748.4
1843.4
704
2C0
1748.6
1843.6
705
2C1
1748.8
1843.8
706
2C2
1749.0
1844.0
707
2C3
1749.2
1844.2
708
2C4
1749.4
1844.4
709
2C5
1749.6
1844.6
710
2C6
1749.8
1844.8
Channels 711-720
Table 7-52

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
711
2C7
1750.0
1845.0
712
2C8
1750.2
1845.2
713
2C9
1750.4
1845.4
714
2CA
1750.6
1845.6
715
2CB
1750.8
1845.8
716
2CC
1751.0
1846.0
717
2CD
1751.2
1846.2
718
2CE
1751.4
1846.4
719
2CF
1751.6
1846.6
720
2D0
1751.8
1846.8
7-30
GMR-01
68P02901W43-P
23 Feb 2004
Channels 721-730
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
721
2D1
1752.0
1847.0
722
2D2
1752.2
1847.2
723
2D3
1752.4
1847.4
724
2D4
1752.6
1847.6
725
2D5
1752.8
1847.8
726
2D6
1753.0
1848.0
727
2D7
1753.2
1848.2
728
2D8
1753.4
1848.4
729
2D9
1753.6
1848.6
730
2DA
1753.8
1848.8
Channels 731-740
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
731
2DB
1754.0
1849.0
732
2DC
1754.2
1849.2
733
2DD
1754.4
1849.4
734
2DE
1754.6
1849.6
735
2DF
1754.8
1849.8
736
2E0
1755.0
1850.0
737
2E1
1755.2
1850.2
738
2E2
1755.4
1850.4
739
2E3
1755.6
1850.6
740
2E4
1755.8
1850.8
7-31
GMR-01
Channels 741-750
Table 7-55

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
741
2E5
1756.0
1851.0
742
2E6
1756.2
1851.2
743
2E7
1756.4
1851.4
744
2E8
1756.6
1851.6
745
2E9
1756.8
1851.8
746
2EA
1757.0
1852.0
747
2EB
1757.2
1852.2
748
2EC
1757.4
1852.4
749
2ED
1757.6
1852.6
750
2EE
1757.8
1852.8
Channels 751-760
Table 7-56

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
751
2EF
1758.0
1853.0
752
2F0
1758.2
1853.2
753
2F1
1758.4
1853.4
754
2F2
1758.6
1853.6
755
2F3
1758.8
1853.8
756
2F4
1759.0
1854.0
757
2F5
1759.2
1854.2
758
2F6
1759.4
1854.4
759
2F7
1759.6
1854.6
760
2F8
1759.8
1854.8
7-32
GMR-01
68P02901W43-P
23 Feb 2004
Channels 761-770
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
761
2F9
1760.0
1855.0
762
2FA
1760.2
1855.2
763
2FB
1760.4
1855.4
764
2FC
1760.6
1855.6
765
2FD
1760.8
1855.8
766
2FE
1761.0
1856.0
767
2FF
1761.2
1856.2
768
300
1761.4
1856.4
769
301
1761.6
1856.6
770
302
1761.8
1856.8
Channels 771-780
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
771
303
1762.0
1857.0
772
304
1762.2
1857.2
773
305
1762.4
1857.4
774
306
1762.6
1857.6
775
307
1762.8
1857.8
776
308
1763.0
1858.0
777
309
1763.2
1858.2
778
30A
1763.4
1858.4
779
30B
1763.6
1858.6
780
30C
1763.8
1858.8
7-33
GMR-01
Channels 781-790
Table 7-59

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
781
30D
1764.0
1859.0
782
30E
1764.2
1859.2
783
30F
1764.4
1859.4
784
310
1764.6
1859.6
785
311
1764.8
1859.8
786
312
1765.0
1860.0
787
313
1765.2
1860.2
788
314
1765.4
1860.4
789
315
1765.6
1860.6
790
316
1765.8
1860.8
Channels 791-800
Table 7-60

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
791
317
1766.0
1861.0
792
318
1766.2
1861.2
793
319
1766.4
1861.4
794
31A
1766.6
1861.6
795
31B
1766.8
1861.8
796
31C
1767.0
1862.0
797
31D
1767.2
1862.2
798
31E
1767.4
1862.4
799
31F
1767.6
1862.6
800
320
1767.8
1862.8
7-34
GMR-01
68P02901W43-P
23 Feb 2004
Channels 801-810
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
801
321
1768.0
1863.0
802
322
1768.2
1863.2
803
323
1768.4
1863.4
804
324
1768.6
1863.6
805
325
1768.8
1863.8
806
326
1769.0
1864.0
807
327
1769.2
1864.2
808
328
1769.4
1864.4
809
329
1769.6
1864.6
810
32A
1769.8
1864.8
Channels 811-820
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
811
32B
1770.0
1865.0
812
32C
1770.2
1865.2
813
32D
1770.4
1865.4
814
32E
1770.6
1865.6
815
32F
1770.8
1865.8
816
330
1771.0
1866.0
817
331
1771.2
1866.2
818
332
1771.4
1866.4
819
333
1771.6
1866.6
820
334
1771.8
1866.8
7-35
GMR-01
Channels 821-830
Table 7-63

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
821
335
1772.0
1867.0
822
336
1772.2
1867.2
823
337
1772.4
1867.4
824
338
1772.6
1867.6
825
339
1772.8
1867.8
826
33A
1773.0
1868.0
827
33B
1773.2
1868.2
828
33C
1773.4
1868.4
829
33D
1773.6
1868.6
830
33E
1773.8
1868.8
Channels 831-840
Table 7-64

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
831
33F
1774.0
1869.0
832
340
1774.2
1869.2
833
341
1774.4
1869.4
834
342
1774.6
1869.6
835
343
1774.8
1869.8
836
344
1775.0
1870.0
837
345
1775.2
1870.2
838
346
1775.4
1870.4
839
347
1775.6
1870.6
840
348
1775.8
1870.8
7-36
GMR-01
68P02901W43-P
23 Feb 2004
Channels 841-850
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
841
349
1776.0
1871.0
842
34A
1776.2
1871.2
843
34B
1776.4
1871.4
844
34C
1776.6
1871.6
845
34D
1776.8
1871.8
846
34E
1777.0
1872.0
847
34F
1777.2
1872.2
848
350
1777.4
1872.4
849
351
1777.6
1872.6
850
352
1777.8
1872.8
Channels 851-860
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
851
353
1778.0
1873.0
852
354
1778.2
1873.2
853
355
1778.4
1873.4
854
356
1778.6
1873.6
855
357
1778.8
1873.8
856
358
1779.0
1874.0
857
359
1779.2
1874.2
858
35A
1779.4
1874.4
859
35B
1779.6
1874.6
860
35C
1779.8
1874.8
7-37
GMR-01
Channels 861-870
Table 7-67

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
861
35D
1780.0
1875.0
862
35E
1780.2
1875.2
863
35F
1780.4
1875.4
864
360
1780.6
1875.6
865
361
1780.8
1875.8
866
362
1781.0
1876.0
867
363
1781.2
1876.2
868
364
1781.4
1876.4
869
365
1781.6
1876.6
870
366
1781.8
1876.8
Channels 871-880
Table 7-68

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
871
367
1782.0
1877.0
872
368
1782.2
1877.2
873
369
1782.4
1877.4
874
36A
1782.6
1877.6
875
36B
1782.8
1877.8
876
36C
1783.0
1878.0
877
36D
1783.2
1878.2
878
36E
1783.4
1878.4
879
36F
1783.6
1878.6
880
370
1783.8
1878.8
7-38
GMR-01
68P02901W43-P
23 Feb 2004
Channels 881-885
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
881
371
1784.0
1879.0
882
372
1784.2
1879.2
883
373
1784.4
1879.4
884
374
1784.6
1879.6
885
375
1784.8
1879.8
7-39
GMR-01
PCS1900 channel numbers and frequencies
Channels 512 to 810

This section lists the frequencies used in PCS1900, with their channel numbers shown
Channels 512-520
Table 7-70 shows the frequencies for PCS1900 channels 512 to 520.
Table 7-70
PCS 1900 channels 512 to 520

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
512
200
1850.2
1930.2
513
201
1850.4
1930.4
514
202
1850.6
1930.6
515
203
1850.8
1930.8
516
204
1851.0
1931.0
517
205
1851.2
1931.2
518
206
1851.4
1931.4
519
207
1851.6
1931.6
520
208
1851.8
1931.8
7-40
GMR-01
68P02901W43-P
23 Feb 2004
Channels 521-530
Table 7-71 PCS 1900 channels 521 to 530
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
521
209
1852.0
1932.0
522
20A
1852.2
1932.2
523
20B
1852.4
1932.4
524
20C
1852.6
1932.6
525
20D
1852.8
1932.8
526
20E
1853.0
1933.0
527
20F
1853.2
1933.2
528
210
1853.4
1933.4
529
211
1853.6
1933.6
530
212
1853.8
1933.8
Channels 531-540
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
531
213
1854.0
1934.0
532
214
1854.2
1934.2
533
215
1854.4
1934.4
534
216
1854.6
1934.6
535
217
1854.8
1934.8
536
218
1855.0
1935.0
537
219
1855.2
1935.2
538
21A
1855.4
1935.4
539
21B
1855.6
1935.6
540
21C
1855.8
1935.8
7-41
GMR-01
Channels 541-550
Table 7-73

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
541
21D
1856.0
1936.0
542
21E
1856.2
1936.2
543
21F
1856.4
1936.4
544
220
1856.6
1936.6
545
221
1856.8
1936.8
546
222
1857.0
1937.0
547
223
1857.2
1937.2
548
224
1857.4
1937.4
549
225
1857.6
1937.6
550
226
1857.8
1937.8
Channels 551-560
Table 7-74

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
551
227
1858.0
1938.0
552
228
1858.2
1938.2
553
229
1858.4
1938.4
554
22A
1858.6
1938.6
555
22B
1858.8
1938.8
556
22C
1859.0
1939.0
557
22D
1859.2
1939.2
558
22E
1859.4
1939.4
559
22F
1859.6
1939.6
560
230
1859.8
1939.8
7-42
GMR-01
68P02901W43-P
23 Feb 2004
Channels 561-570
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
561
231
1860.0
1940.0
562
232
1860.2
1940.2
563
233
1860.4
1940.4
564
234
1860.6
1940.6
565
235
1860.8
1940.8
566
236
1861.0
1941.0
567
237
1861.2
1941.2
568
238
1861.4
1941.4
569
239
1861.6
1941.6
570
23A
1861.8
1941.8
Channels 571-580
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
571
23B
1862.0
1942.0
572
23C
1862.2
1942.2
573
23D
1862.4
1942.4
574
23E
1862.6
1942.6
575
23F
1862.8
1942.8
576
240
1863.0
1943.0
577
241
1863.2
1943.2
578
242
1863.4
1943.4
579
243
1863.6
1943.6
580
244
1863.8
1943.8
7-43
GMR-01
Channels 581-590
Table 7-77

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
581
245
1864.0
1944.0
582
246
1864.2
1944.2
583
247
1864.4
1944.4
584
248
1864.6
1944.6
585
249
1864.8
1944.8
586
24A
1865.0
1945.0
587
24B
1865.2
1945.2
588
24C
1865.4
1945.4
589
24D
1865.6
1945.6
590
24E
1865.8
1945.8
Channels 591-600
Table 7-78

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
591
24F
1866.0
1946.0
592
250
1866.2
1946.2
593
251
1866.4
1946.4
594
252
1866.6
1946.6
595
253
1866.8
1946.8
596
254
1867.0
1947.0
597
255
1867.2
1947.2
598
256
1867.4
1947.4
599
257
1867.6
1947.6
600
258
1867.8
1947.8
7-44
GMR-01
68P02901W43-P
23 Feb 2004
Channels 601-610
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
601
259
1868.0
1948.0
602
25A
1868.2
1948.2
603
25B
1868.4
1948.4
604
25C
1868.6
1948.6
605
25D
1868.8
1948.8
606
25E
1869.0
1949.0
607
25F
1869.2
1949.2
608
260
1869.4
1949.4
609
261
1869.6
1949.6
610
262
1869.8
1949.8
Channels 611-620
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
611
263
1870.0
1950.0
612
264
1870.2
1950.2
613
265
1870.4
1950.4
614
266
1870.6
1950.6
615
267
1870.8
1950.8
616
268
1871.0
1951.0
617
269
1871.2
1951.2
618
26A
1871.4
1951.4
619
26B
1871.6
1951.6
620
26C
1871.8
1951.8
7-45
GMR-01
Channels 621-630
Table 7-81

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
621
26D
1872.0
1952.0
622
26E
1872.2
1952.2
623
26F
1872.4
1952.4
624
270
1872.6
1952.6
625
271
1872.8
1952.8
626
272
1873.0
1953.0
627
273
1873.2
1953.2
628
274
1873.4
1953.4
629
275
1873.6
1953.6
630
276
1873.8
1953.8
Channels 631-640
Table 7-82

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
631
277
1874.0
1954.0
632
278
1874.2
1954.2
633
279
1874.4
1954.4
634
27A
1874.6
1954.6
635
27B
1874.8
1954.8
636
27C
1875.0
1955.0
637
27D
1875.2
1955.2
638
27E
1875.4
1955.4
639
27F
1875.6
1955.6
640
280
1875.8
1955.8
7-46
GMR-01
68P02901W43-P
23 Feb 2004
Channels 641-650
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
641
281
1876.0
1956.0
642
282
1876.2
1956.2
643
283
1876.4
1956.4
644
284
1876.6
1956.6
645
285
1876.8
1956.8
646
286
1877.0
1957.0
647
287
1877.2
1957.2
648
288
1877.4
1957.4
649
289
1877.6
1957.6
650
28A
1877.8
1957.8
Channels 651-660
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
651
28B
1878.0
1958.0
652
28C
1878.2
1958.2
653
28D
1878.4
1958.4
654
28E
1878.6
1958.6
655
28F
1878.8
1958.8
656
290
1879.0
1959.0
657
291
1879.2
1959.2
658
292
1879.4
1959.4
659
293
1879.6
1959.6
660
294
1879.8
1959.8
7-47
GMR-01
Channels 661-670
Table 7-85

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
661
295
1880.0
1960.0
662
296
1880.2
1960.2
663
297
1880.4
1960.4
664
298
1880.6
1960.6
665
299
1880.8
1960.8
666
29A
1881.0
1961.0
667
29B
1881.2
1961.2
668
29C
1881.4
1961.4
669
29D
1881.6
1961.6
670
29E
1881.8
1961.8
Channels 671-680
Table 7-86

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
671
29F
1882.0
1962.0
672
2A0
1882.2
1962.2
673
2A1
1882.4
1962.4
674
2A2
1882.6
1962.6
675
2A3
1882.8
1962.8
676
2A4
1883.0
1963.0
677
2A5
1883.2
1963.2
678
2A6
1883.4
1963.4
679
2A7
1883.6
1963.6
680
2A8
1883.8
1963.8
7-48
GMR-01
68P02901W43-P
23 Feb 2004
Channels 681-690
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
681
2A9
1884.0
1964.0
682
2AA
1884.2
1964.2
683
2AB
1884.4
1964.4
684
2AC
1884.6
1964.6
685
2AD
1884.8
1964.8
686
2AE
1885.0
1965.0
687
2AF
1885.2
1965.2
688
2B0
1885.4
1965.4
689
2B1
1885.6
1965.6
690
2B2
1885.8
1965.8
Channels 691-700
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
691
2B3
1886.0
1966.0
692
2B4
1886.2
1966.2
693
2B5
1886.4
1966.4
694
2B6
1886.6
1966.6
695
2B7
1886.8
1966.8
696
2B8
1887.0
1967.0
697
2B9
1887.2
1967.2
698
2BA
1887.4
1967.4
699
2BB
1887.6
1967.6
700
2BC
1887.8
1967.8
7-49
GMR-01
Channels 701-710
Table 7-89

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
701
2BD
1888.0
1968.0
702
2BE
1888.2
1968.2
703
2BF
1888.4
1968.4
704
2C0
1888.6
1968.6
705
2C1
1888.8
1968.8
706
2C2
1889.0
1969.0
707
2C3
1889.2
1969.2
708
2C4
1889.4
1969.4
709
2C5
1889.6
1969.6
710
2C6
1889.8
1969.8
Channels 711-720
Table 7-90

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
711
2C7
1890.0
1970.0
712
2C8
1890.2
1970.2
713
2C9
1890.4
1970.4
714
2CA
1890.6
1970.6
715
2CB
1890.8
1970.8
716
2CC
1891.0
1971.0
717
2CD
1891.2
1971.2
718
2CE
1891.4
1971.4
719
2CF
1891.6
1971.6
720
2D0
1891.8
1971.8
7-50
GMR-01
68P02901W43-P
23 Feb 2004
Channels 721-730
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
721
2D1
1892.0
1972.0
722
2D2
1892.2
1972.2
723
2D3
1892.4
1972.4
724
2D4
1892.6
1972.6
725
2D5
1892.8
1972.8
726
2D6
1893.0
1973.0
727
2D7
1893.2
1973.2
728
2D8
1893.4
1973.4
729
2D9
1893.6
1973.6
730
2DA
1893.8
1973.8
Channels 731-740
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
731
2DB
1894.0
1974.0
732
2DC
1894.2
1974.2
733
2DD
1894.4
1974.4
734
2DE
1894.6
1974.6
735
2DF
1894.8
1974.8
736
2E0
1895.0
1975.0
737
2E1
1895.2
1975.2
738
2E2
1895.4
1975.4
739
2E3
1895.6
1975.6
740
2E4
1895.8
1975.8
7-51
GMR-01
Channels 741-750
Table 7-93

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
741
2E5
1896.0
1976.0
742
2E6
1896.2
1976.2
743
2E7
1896.4
1976.4
744
2E8
1896.6
1976.6
745
2E9
1896.8
1976.8
746
2EA
1897.0
1977.0
747
2EB
1897.2
1977.2
748
2EC
1897.4
1977.4
749
2ED
1897.6
1977.6
750
2EE
1897.8
1977.8
Channels 751-760
Table 7-94

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
751
2EF
1898.0
1978.0
752
2F0
1898.2
1978.2
753
2F1
1898.4
1978.4
754
2F2
1898.6
1978.6
755
2F3
1898.8
1978.8
756
2F4
1899.0
1979.0
757
2F5
1899.2
1979.2
758
2F6
1899.4
1979.4
759
2F7
1899.6
1979.6
760
2F8
1899.8
1979.8
7-52
GMR-01
68P02901W43-P
23 Feb 2004
Channels 761-770
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
761
2F9
1900.0
1980.0
762
2FA
1900.2
1980.2
763
2FB
1900.4
1980.4
764
2FC
1900.6
1980.6
765
2FD
1900.8
1980.8
766
2FE
1901.0
1981.0
767
2FF
1901.2
1981.2
768
300
1901.4
1981.4
769
301
1901.6
1981.6
770
302
1901.8
1981.8
Channels 771-780
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
771
303
1902.0
1982.0
772
304
1902.2
1982.2
773
305
1902.4
1982.4
774
306
1902.6
1982.6
775
307
1902.8
1982.8
776
308
1903.0
1983.0
777
309
1903.2
1983.2
778
30A
1903.4
1983.4
779
30B
1903.6
1983.6
780
30C
1903.8
1983.8
7-53
GMR-01
Channels 781-790
Table 7-97

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
781
30D
1904.0
1984.0
782
30E
1904.2
1984.2
783
30F
1904.4
1984.4
784
310
1904.6
1984.6
785
311
1904.8
1984.8
786
312
1905.0
1985.0
787
313
1905.2
1985.2
788
314
1905.4
1985.4
789
315
1905.6
1985.6
790
316
1905.8
1985.8
Channels 791-800
Table 7-98

Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
791
317
1906.0
1986.0
792
318
1906.2
1986.2
793
319
1906.4
1986.4
794
31A
1906.6
1986.6
795
31B
1906.8
1986.8
796
31C
1907.0
1987.0
797
31D
1907.2
1987.2
798
31E
1907.4
1987.4
799
31F
1907.6
1987.6
800
320
1907.8
1987.8
7-54
GMR-01
68P02901W43-P
23 Feb 2004
Channels 801-810
Channel number
68P02901W43-P
23 Feb 2004
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
801
321
1908.0
1988.0
802
322
1908.2
1988.2
803
323
1908.4
1988.4
804
324
1908.6
1988.6
805
325
1908.8
1988.8
806
326
1909.0
1989.0
807
327
1909.2
1989.2
808
328
1909.4
1989.4
809
329
1909.6
1989.6
810
32A
1909.8
1989.8
7-55
GMR-01
7-56
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
8
Network optimization
Network optimization requires testing of the signal strength between BSS and MSs within the reception area(s)
covered by the BTS(s). This requires going out into the field with mobile equipment usually in a vehicle.
This chapter describes the process and procedures involved in the optimization of a network by drive
testing, and provides guidance on analysing logs and resolving problems.
The techniques involved in optimization of the macrocellular system also apply to microcellular
systems. The same techniques apply to any frequency band, although there are significant
differences in the RF propagation properties.
The following network optimization topics are described:
68P02901W43-P
23 Feb 2004
Tools required for Network optimization in "Network optimization tools" on page 8-2.
Network optimization discussion in "Network optimization process" on page 8-5.
Drive testing the system in "System drive test" on page 8-7.
Diagnosing drive test results in "Drive test results analysis" on page 8-15.
Checking for a DSP failure in "DSP test" on page 8-25.
8-1
GMR-01
Network optimization tools
Motorola offer a number of tools and services to facilitate optimization of a network.
Motorola Drive Test Tool (MDTT)

The Motorola Drive Test Tool (MDTT) is designed to help field engineers locate problems in a network. GSM
and GPRS air interface messages and parameters are decoded and displayed along with Global Positioning
System (GPS) data. It uses log files to record and subsequently replay the information.
The MDTT is installed on a laptop or desktop PC supporting Windows versions NT4 Service Pack 6 or
Windows 2000. The PC is connected to a Motorola GSM or GPRS mobile station (MS) via an M-PLUS
firmware card to enable it to receive the data. A GPS device is also connected to the computer.
Use of the MDTT is beyond the scope of this document, for further information refer to the MDTT on-line help.
Cell Optimization Product (COP)

The Cell Optimization Product (COP) is a collection of tools which allows the user to:
Obtain accurate configuration data across multiple OMC-Rs.
Provide information on cell performance and problems.
Tune and optimize networks.
Gather information about network events and alarms.
Generic Lookup Utility (GLU)

The Generic Lookup Utility (GLU) is used to obtain accurate configuration data across multiple OMC-Rs.
The GLU provides answers to most network configuration queries, for example:
The number of BSCs connected.
How the BSCs are connected (via RXCDR or directly to the MSC).
Cell frequency usage.
The GLU can produce comprehensive network-wide reports in:
Directly printable format.
Tab separated files for commercial spreadsheet analysis.
The GLU extracts the data specified by the user and displays it in an easy-to-read format on screen or, if
selected, it saves it to a file that can be interpreted by using a commercial spreadsheet facility.
8-2
GMR-01
68P02901W43-P
23 Feb 2004
Cell Analysis Tool (CAT)

The Cell Analysis Tool (CAT) provides information about GSM network cell performance. It allows the user
to find out quickly which cells currently have problems, or might have problems in the near future. CAT
interrogates the OMC-R system and the Performance Monitor (PM) database every hour. It compares the
data returned with thresholds and reports on cells that are deemed to have failed in some way.
Call Trace Product (CTP)

The Call Trace Product (CTP) is designed to help operators of GSM900 and DCS1800
communication networks to tune and optimize their systems. CTP is flexible and can be
used in many ways to satisfy different user requirements.
Event Counting Tool (ECT)

The Event Counting Tool (ECT) provides information about the number and type of events and alarms
generated throughout a GSM network. It extracts data from the event log files for specified dates. ECT allows
the user to generate reports on individual network elements, groups of elements, or the whole network.
Call Trace Product for Windows NT (CTP-NT)

The Call Trace Product for Windows NT (CTP-NT) is a tool for the decoding and analysis of call trace data
that is collected by the BSS and sent to the OMC-R in the form of Call Trace files. The decoded data is stored
in an SQL Server database. Call Trace files contain both measurement reports and Layer 3 messages.
CTP-NT provides a collection and decode service that continuously checks each enabled OMC-R
stored in the call trace database for call trace files that have not been decoded and stored. These
collected files are copied to the machine that CTP-NT is running on.
The CTP-NT database contains data, collected from the OMC-R CM cache, for all the BSS, XCDR, BTS,
cells, and neighbour network elements managed by the OMC-R. Using the call trace database, CTP-NT allows:
68P02901W43-P
23 Feb 2004
Statistical analysis of measurement report data for individual cells or arbitrary groupings of cells.
Call analysis in which measurement report data and Layer3 messages may
be viewed on a call by call basis.
Filtering of call trace files by any combination of network elements, date range, message type,
call type, and DTX. Filtering can also be applied to MR Distributions reports.
Generation of pre-defined CTP reports which can be run over the Call Trace database.
Exporting of tabular and graphical data to other MS Office applications.
8-3
GMR-01
Intelligent Optimization Service (IOS)

The Intelligent Optimization Service (IOS) is a network based service provided by Motorola. IOS
automatically collects and stores measurement reports and analyses large volumes of subscriber generated
measurement reports together with the current network configuration, to produce a series of recommendations
for neighbour topology and frequency plan changes. Key metrics, distributions and a comprehensive Carrier
to Interference Ratio (C/I) matrix for the complete region being optimized may also be produced.
8-4
GMR-01
68P02901W43-P
23 Feb 2004
Network optimization process
Optimization is the task of improving the call success rate for mobile subscribers.
In a newly deployed network, problems may emerge due to any or all of the following:
The set-up of the database parameters.
The installation of the equipment.
The orientation of the antennas.
There will almost certainly be problems with congestion in busy parts of the network.
As a network matures from an initial coverage priority to handling more subscribers, it becomes clear
that some of the original cells need to be modified or removed from the network.
Worst ten cells method

The optimization of an entire network with hundreds or thousands of cells is a time-consuming and slow
process, and can show little improvement in overall network quality in the short term. Drive testing and
analysis of collected data are two stages of a practical method of optimizing a network by attacking the worst
ten performing cells. Dealing with the worst ten cells in each optimization exercise, slowly resolves the
problems and raises the overall quality of service available to subscribers. As the network expands each
new cell integrated into the network is automatically assessed along with all the original cells.
The overall performance of a network which has had little or no upgrading can also be improved
by implementing newer features or operating practices.
Stages in an optimization exercise

The optimization process can be divided into the following stages:
Preparing for an optimization exercise from the OMC-R.

This involves consultation with network operators to review their network administration
procedures and feature implementation to determine where areas can be modified to
increase efficiency and unnecessary diagnostic effort. See Preparing for optimization in
Installation and Configuration: GSM System Configuration (68P02901W17).
68P02901W43-P
23 Feb 2004
Checking, collecting and researching network information from the OMC-R.

Details can be found in the manual Installation and Configuration: GSM
System Configuration (68P02901W17).
Analysing, diagnosing and rectifying network problem areas from the OMC-R.
Details can be found in the manual Installation and Configuration: GSM
System Configuration (68P02901W17).
8-5
GMR-01
Drive testing, if required.

Drive testing is a significant stage in optimizing a network. It is labour intensive, slow, and drive
test teams cannot cover cells that are geographically widely separated. In these circumstances
statistical analysis of the network from the OMC-R can be quicker, but in other circumstances
drive testing may still be necessary. See sections in this chapter for further details.
Analysing and resolving any problem cells using data, logs and tick sheets collected
during the drive tests. See sections in this chapter for further details.
8-6
GMR-01
68P02901W43-P
23 Feb 2004
System drive test
System drive test
Once the network optimization exercise has reached the stage of drive testing and network
performance is still poor, a drive test of the problem cells is required.
This involves:
Preparing for the drive test.
Equipment lists.
Optimizing for worst case interference.
Drive test process.
Data collection overview.
Personnel requirements.
Data collection process.
FICS.
The classification of test calls.
Preparation for the drive test

Prior to the commencement of drive testing, certain system features must be set, and equipment for
carrying out the drive test and collection of data must be organized.
System features
Prior to drive testing ensure:
68P02901W43-P
23 Feb 2004
Base station power control feature is turned off.
Directed retry feature is turned off.
Congestion relief feature is turned off.
All non-BCCH carriers are transmitting dummy bursts on all timeslots.
8-7
GMR-01
System drive test
Equipment required for data collection/analysis

The following equipment is required for gathering and analyzing drive test data.
TEMS compatible mobile station.
PC with TEMS mobile logging software and 2 serial ports.
Colour printer.
Equipment/information required for drive test

To carry out the drive test the following equipment and information is required.
A suitable number to ring is required to be available for the duration of the drive test.
The number may be for a recorded announcement located at the MSC or PSTN,
or to contact a third person at a land line phone.
A recorded announcement such as weather or news can be used as long

as it is 3 minutes or more in duration.
Cordless or mobile phones should not be used for the landline contact.
Maps of area to be tested,1:10000 to 1:50000 scale and marked with longitude and latitude.
BTS sites showing antenna direction identified on the maps.
A list of BCCH frequencies and BSICs for all BTS sites.

The list must also contain BCCH frequencies and BSICs of BTSs from another
equipment supplier, if this equipment borders the area under test.
A complete neighbour list for all BTSs in the area under test.
Current database scripts for the sites that are to be optimized.
Daily network performance statistics and information on outages that have affected the
network over the past day must be collected from the OMC-R.
Notice of planned outages should also be obtained to avoid time being wasted
collecting data in areas with no service.
A second MS for the drive test team.
This phone should be from a rival network to maintain contact during outages,
if the area under test is liable to no or poor service.
8-8
GMR-01
68P02901W43-P
23 Feb 2004
System drive test
A suitable vehicle for the drive test team.

The vehicle must be comfortable and capable of negotiating terrain within the test area.
GPS or other positioning system.
Suitable power supplies/invertors to allow the use of data gathering equipment in

the vehicle throughout the duration of the drive test.
GSM recommendations 04.08, 05.08 and 08.08 are to be available.

GSM recommendation 05.05 may be of use.
68P02901W43-P
23 Feb 2004
8-9
GMR-01
System drive test

The following tables list the equipment required for drive testing, systems analysis
and any necessary fault investigation.
Table 8-1 lists the equipment required for drive testing.
Table 8-1 Equipment required for drive testing
Equipment
Alternative
Preferred
Vehicle
Minibus or MPV
Any
Laptop PC, Colour, 500 Mb min HD
Dell Latitude, any model
Toshiba 110CT upward
Operating System
MS Windows NT 4.0
MS Windows 3.11 or later
2nd Serial Port
Socket I/O PCMCIA
None Known
Vehicle Inverter 12 Vdc to 240 Vac
Any Retail
Any Retail
2nd
Alternative Network
Any Retail
Ericsson Test Mobile (outdoor)
GH388 (900 MHz)
Orbitel Test Mobile
Ericsson Test Mobile (outdoor)
PH337 (1800 MHz)
Later Model
Mobile Logging Software
Erisoft TEMS V96
Later Version
Indoor Test Mobile 900 MHz
Ericsson Pocket TEMS GH388
Motorola 8900 in test mode
Indoor Test Mobile 1800 MHz
Ericsson Pocket TEMS PH337
Motorola 8900 in test mode
Data Analysis Software
Erisoft FICS Shell V96
Later Version
Global Positioning Hardware
Motorola PVT6
Trimble 21426 + Card
Global Positioning Software
Oncore Rx Controller
Trimble V4.24
Mobile Phone
Table 8-2 lists the equipment required for systems analysis.

Table 8-2
Equipment required for systems analysis

Equipment
Alternative
Preferred
Colour Plotter or Printer
HP Designjet 650C upward
HP Deskjet 1120 (A3 Paper)
Workstation
SUN Ultra Sparc 1
SUN Sparc 20
Operating System
UNIX
UNIX
MSI PlaNet
Netplan
Erisoft FICS Shell V96
Later Version
Table 8-3 lists the equipment required for problem investigation.
8-10
GMR-01
68P02901W43-P
23 Feb 2004
System drive test
Table 8-3 Equipment required for problem investigation

Equipment
Preferred
Alternative
Network Protocol Analyser
Siemens K1103
None
Spectrum Analyser
Advantest U4342 Tracking Opt
Wavetek 4031 or 4032
Antenna System
Bird T43 (VSWR only)
Wiltron Sitemaster S331
Laptop PC, Colour, 500 Mb min HD
Dell Latitude, any model
Toshiba 110CT upward
Operating System
MS Windows NT 4.0
MS Windows 3.11 or later
9/25 Way Interface cable

(BSC/XCDR)
Standard RS232
None
Interface cable (BTS)
BTS H/W Model Specific
None
Terminal Emulator Software
Procomm +
MS Hyperterminal
Optimizing for worst case interference

During the drive testing phase of the optimization, downlink power control must be turned off. Once
optimization is complete downlink power control can be reactivated. A feature at the OMC-R allows
the operator to achieve this, configuring all non-BCCH carriers to transmit dummy bursts on all
timeslots not carrying traffic. This will give a worst case interference environment in which optimization
can be carried out. Information on how to enable this feature using the set_full_power command
can be found in Technical Description: BSS Command Reference (68P02901W23). This is useful,
if during optimization, there is very little traffic currently on the network.
Drive test process

Drive testing provides the data necessary to optimize network performance. The two minute call method
provides the means for investigating the performance of our systems, and optimizing networks. The two
minute calls used as a standard, give a representation of traffic and can be used to measure performance
of the network giving an indication of progress being made by optimization teams. With this method
not only can interference and coverage issues be identified, but also signalling and other problems that
are present can be discovered and their effects on system performance quantified.
Data gathered can be used for the benchmarking of system performance. If this is the requirement, then
in excess of 1000 calls will be required before data can be looked at with confidence. Consideration
must be given to available time, goals and resources when looking at benchmarking. A significant
picture can be built up with a much smaller sample, consisting of a minimum 200 calls.
Drive test routes are best defined in consultation with operators, as they will have priority areas that require
constant evaluation. Recommendations resulting from analysis of network optimization data must reflect
circumstances and goals, and wherever possible use existing hardware and features already in place.
Drive tests are to be conducted by using mobiles in the same manner as they would be used by network
subscribers. For instance, it is rare that a subscriber would have a car mounted mobile station, so this
must not be used to carry out a drive test. If a roof mounted antenna is to be used then an attenuator
should be used to simulate the in-car losses. Similarly if coverage of buildings is important within
a city, then it will be necessary to do tests within a few key buildings.
68P02901W43-P
23 Feb 2004
8-11
GMR-01
System drive test
Data collection overview

Data is collected by drive teams using TEMS mobiles. The TEMS mobile is a test mobile station combined
with logging software that runs on a PC. The collecting of data is carried out by a two man team, consisting of
a driver and an operator. The drive testing task is very labour intensive and time consuming.
Personnel requirements
Optimizing a network in a large city environment will require a number of teams to speed
up the process. Rural network optimization will again require multiple teams, however this
time the need is to compensate for geographical dispersion.
A number of personnel will also be required for data analysis. Data analysis consists of two stages:
The generation of statistics to monitor network performance.
The resolution of problems on the network once detected.
Problems resulting from localised interference will require system investigators to visit the problem area in
person. Spectrum analysers will be used by the investigators to track extraneous interference.
Data collection process

A number of drive test teams will be collecting data, with each team required to make in excess of 175 calls
per day. TEMS mobile stations equipped with the latest version of the software can make and terminate these
calls automatically. This can lead to uncertainty as to whether a call was dropped or terminated normally.
A call should:
Have a duration of 2 minutes ( 5 seconds).
Have a minimum gap of 20 seconds in between it and the next call.
Not be made for 20 seconds after a failed call has terminated.
Drive test teams have the option of recording each call attempt made onto a tick sheet or processing the
results wholly through FICS. An example tick sheet can be found in Chapter 11 of this manual.
FICS explained
When using tick sheets to process call log data, errors are to be expected. File & Information Converting
System (FICS) must be used to confirm the tick sheets, and identify calls that need further analysis.
Calls are to be logged manually if the latest version of FICS is unavailable.
8-12
GMR-01
68P02901W43-P
23 Feb 2004
System drive test
An alternative to using tick sheets is to process the call log data direct through TEMS automatic logging and
FICS. This eliminates tick sheet errors and makes the collection of data easier and more reliable. However,
FICS is unable to differentiate noise during a call, so even with good signal strength if there is induced noise or
no audio then it will go undetected. Taking this into account, the proportion of noisy calls and low audio calls is
relatively low, and considering the volume of calls generated may have low impact on overall network quality.
The ineffectiveness of FICS to identify no audio calls can be counteracted by running a
message_send command for the transcoders. This will identify any faulty DSPs on transcoder
boards at the site. Information on using the message_send command can be found in Technical
Description: BSS Command Reference (68P02901W23).
This command will not help in identifying noisy calls, which will still go completely undetected.
Report generation
A report can be generated showing call failure analysis when using FICS as opposed to tick sheets.
This is done using the FICS.sta files, by summing all quality entries in the RxQual 0 to 4 bands
inclusive, and using the resultant as a Q measure. An added benefit of this is that it will also
give any MSC related issues that would not normally be highlighted.
Classification of test calls

A call will fall into one of the categories defined below:
No service.
A call will fall into this category if the mobile is saying No Service or Select
Service before the send button is pressed.
No set-up.
If, after pushing send, the call does not proceed to audio it is categorized as no set-up.
No audio.
This category applies when after a traffic channel has been assigned the audio
connection is never made, or only appears after a handover.
Noisy call.
A call is defined as noisy if there are more than 5 seconds of noise or
breaks in the audio during the call.
Dropped call.
If a call terminates during a 2 minute test call it will be classed as a dropped call.
68P02901W43-P
23 Feb 2004
8-13
GMR-01
System drive test
Good call.
A call that does not fit into any of the above criteria will be deemed to have
been successful and classed a good call.
Tick sheets
When entering test call results onto a tick sheet, only one tick per call should be entered.
Log files
When using log files to record call information the log file names should be changed after
every 10 calls. A suitable naming convention scheme, to ensure unique files, is to use the form
xydmz.log. Here xy are the initials of the operator, dm are the day and month and z is a sequencing
indicator, starting with a and progressing through the alphabet.
Archiving
All data should be archived at the end of the day. Archiving may be to floppy disk, CD-ROM or any
other suitable means which is convenient to the drive test team carrying out the work.
8-14
GMR-01
68P02901W43-P
23 Feb 2004
Drive test results analysis
Once a drive test of the system is completed, the resultant data of test calls made must be analysed.
This involves looking at:
Analysis of data.
High handover failure rates.
High set-up failure rates.
High dropped call rates.
No audio calls.
Noisy calls.
Poor quality of service calls.
High blocking cells.
Audio call faults.
Mean time between drops.
Drive test report.
Implementation of drive test recommendation.
Effects of a recommendation implemented.
Residual defect investigation.
Analysis of data
Call failures will be due to a number of different factors, so each failure must therefore be analysed.
If a failure cannot be explained further assistance should be sought.
Graphs are a useful way of showing the contribution each type of failure is making to the
call success rate. Graphs can be used to show:
The percentage of failed calls.

These calls will consist of dropped calls, no set-up calls, no service calls and no audio calls.
The contribution of different causes of failure to each failure category.
The graphs provide a useful means of analysis and give problem solving teams an idea of
causes of the greatest number of failures. The failures can then be addressed on a priority basis,
with the largest percentage of failures being rectified first.
68P02901W43-P
23 Feb 2004
8-15
GMR-01
The results collected can be used for benchmarking the systems performance, as discussed in Drive test
process. Doing this allows the progress of the system performance to be monitored. However, for the
results to have any statistical significance a large number of calls will need to be made.
Quoting the margin of error when presenting the results is necessary to explain the variance
that will been seen in results from week to week.
High handover failure rates

High handover failure rates will probably be due to one or more of:
High neighbour interference.
High source cell interference.
Mobile on incorrect source cell.
Mobile allocated incorrect or unexpected neighbour.
Location area borders planned poorly.

Borders on road junctions or ridges.
Borders on large water expanses.
Cell borders planned poorly.

Borders on road junctions or ridges.
Borders on large water expanses.
Database parameters.
Power budget algorithms incorrectly specified.
RxQual algorithms incorrectly specified.
RxLev algorithms incorrectly specified.
Timing advance algorithms incorrectly specified.
No dominant server.
Neighbours being received at similar levels.
Missing cell site.
8-16
GMR-01
68P02901W43-P
23 Feb 2004
High set-up failure rates

High set-up failure rates will probably be due to one or more of:
No access to SDCCH.
Mobile failed to send RACH.
No UA received from BTS due to interference.
Mobile access class barred.
Mobile failed to carry out location update.
SDCCH congestion, location area boundaries being undesirable or
insufficient SDCCHs available.
Failure before assignment of TCH.

Downlink disconnect message from MSC.
Congestion on the A interface.
No free TCHs available.
Failure after assignment of TCH.

High interference on allocated TCH or timeslot.
On site cabling faulty.
Disconnect due to called party busy.
PSTN congestion.
No answer.
Incorrectly dialled digits.
Mobile on wrong cell.
Rx path failure on non-BCCH carrier.
68P02901W43-P
23 Feb 2004
8-17
GMR-01
High dropped call rate

High dropped call rates will probably be due to one or more of the following.
Interference problems
Interference problems can be attributed to:
Adjacent channel interference.

Neighbouring cells causing interference.
Co-channel interference.
Neighbouring cells on same frequency as source.
Non neighbouring cells penetrating due to topology.
Mobile elevated and receiving out of area signals.
Antennas to high, causing interference and out of area originations.
Uplink interference.
Background interference.
Extraneous interference.
Other mobile networks.
Military communications.
High power radio transmission stations.
Proximity of ground based radar systems.
Cordless telephones.
Industrial electrical emissions.
Illegal radio communication equipment.
Mobile to cell link problems

Link problems can be attributed to:
Link imbalance.
Mobile transmitting too high.
Mobile transmitting too low.
BTS transmitting too high.
BTS transmitting too low.
8-18
GMR-01
68P02901W43-P
23 Feb 2004
Physical obstructions.
Nearby microwave or high power radiating devices.
Antennas positioned to close together.
Transmit and receive antennas facing different directions.
Transmit and receive antennas having different tilts.
Transmit and receive antennas having different beam widths.
Antenna feeder damage, corrosion or water ingress, or antenna radiating
surfaces being contaminated.
Cell allocation problems

Cell allocation problems can be attributed to:
Drop on handover.
Mobile on incorrect source cell.
Mobile allocated incorrect or unexpected neighbour.
Missing neighbour cell.

Mobile on wrong source cell for location.
Missing handover definition.
Neighbour weaker than serving cell.
Incorrect BSIC or frequency with respect to the neighbour list.
Target cell congested.
Frequency not sent in system information message.
Mobile on wrong cell.

Missing neighbour.
Incorrect antenna orientation.
Antennas cross connected.
Mobile handed-in to wrong cell from previous server.
Optimum server out of service.
Wrong frequency.
Cell is not on the correct frequency as detailed in the network plan.
Cell is not on the correct frequency as detailed in the neighbour lists.
68P02901W43-P
23 Feb 2004
8-19
GMR-01
Cell out of service.

Cell out of service, causing a coverage hole.
Sleeping cell.
Signal and propagation problems.

Signal and propagation problems can be attributed to:
Low signal level.

BTS transmission power too low.
Radio signal propagation problems.
Local cell out of service.
Ridges causing immediate signal loss before handover can be initiated.
Narrow cell boundaries, mobile cannot handover in time.
No audio calls
No audio calls will probably be due to one or more of:
Hardware problems in the transcoder circuitry.
Software problems in the transcoder database.
Noisy calls
Noisy calls will probably be due to one or more of:
Interference.
Low signal level.
Poor quality of service calls

Poor quality calls will probably be due to one or more of:
Interference.
Low signal level.
No serving cell.
8-20
GMR-01
68P02901W43-P
23 Feb 2004
High blocking cells

Blocking cells can be attributed to:
SDCCH blocking
No access to SDCCH.
Mobile failed to send RACH.
No UA received by MS due to interference.
Mobile access class barred.
Mobile failed to carry out location update.
Check HLR, VLR or their respective links.
Location update timer is too long for immobile MS.
SDCCH congestion.
Location area boundaries undesirable
Insufficient SDCCHs available.
Failure before assignment of TCH.

Downlink disconnect message from MSC.
Congestion on the A interface.
No free TCHs available.
High paging loads.

Each location area should have similar paging loads.
A location area with a high paging load needs to be reduced in size
to relieve SDCCH blocking.
A location area with a low paging load needs to be enlarged in size to
reduce the overall number of location areas.
Incorrect or inappropriate timer values.

Timer rr_t3111_sd should be set to 1200 ms.
Timer rr_t3212 needs to be the same as the MSC database implicit detach
timer and should be similar across all cells.
68P02901W43-P
23 Feb 2004
8-21
GMR-01
TCH blocking
Handover margins not optimized.
Power budget margins too high to move traffic to neighbouring cells.
Cell too large.

Antennas too high, pulling in out of area traffic.
Antenna tilts too shallow, pulling in out of area traffic.
Capacity limitation for sites suffering SDCCH and TCH blocking.
Incorrect or inappropriate timer and parameter values.

Timer rr_t3111_tch should be set to 1200 ms.
Parameter link_fail should be set to 3.
Parameter radio_link_timeout should be set to 3 and timer rr_t3109 to 8000.
MTL blocking
On site cabling faulty.
Disconnect due to the called party being busy.
PSTN congestion.
No answer.
Incorrectly dialled digits.
8-22
GMR-01
68P02901W43-P
23 Feb 2004
Audio call faults

The process of tracing faults associated with no audio or one way audio calls is exasperated by the
way the circuits are allocated dynamically. With circuits being allocated dynamically it may take
several attempts, by the person trying to trace the fault, before the faulty circuit is allocated again.
This could result in other users on the system being allocated the faulty circuit when trying to make
a call, whilst the faulty circuit is being traced. See next section DSP test.
Mean time between drops

When making test calls the length of the call may need to be varied, depending on differing conditions. This is
creates a problem when using test calls to benchmark a network, as the baseline criteria is variable. A metric
has been devised to overcome this that does not require the rigid adherence of test call length to be 2 minutes.
This method uses the probability of a drop, as a consequence of call length, for the baseline measurement.
The mean time between drops is defined as:
For call drive test metrics:

Length of Test Call
Mean Time Between Drop =
Drop Call Percentage
For system statistics:

Length of Average Hold Time
Mean Time Between Drop =
Drop Call Percentage
For example:
2 minute calls, 1% drop = 200 minutes (MTBD)
30 second calls, 1% drop = 50 minutes (MTBD)
Drive test report

The result of a drive test is a report, which is generated by compiling all the relevant data gathered, in support
of conclusions and recommendations which are to be made to the customer. Each conclusion in the report is
to have a supporting numbered recommendation related to it. A recommendation must describe the issue,
recommended solution and the impact that carrying out the recommendation will have on the rest of the
network. As much detail as possible is to be included to aid in the recommendations implementation.
Blank field report forms can be found in Chapter 9 Opimization results forms.
68P02901W43-P
23 Feb 2004
8-23
GMR-01
Effects of a recommendation implemented

Any recommendation is to be monitored and confirmation sought that its implementation cured the issue.
Residual defect investigation

Any defects discovered during the optimization process that cannot be resolved are to be reported through the
normal process for raising problem reports. It is recommended that defects discovered are fixed. However it
is not within the scope of this document to identify procedures for the repair/replacement of faulty hardware.
8-24
GMR-01
68P02901W43-P
23 Feb 2004
DSP test
DSP test
Calls being processed by the suspect transcoder board that are unaffected
by the faulty DSP will be affected by this test procedure.
The OMC-R must take the appropriate steps to route all calls away from
the suspect board prior to commencement of the test.
The most likely cause of audio fault on a circuit is a faulty DSP on a transcoder/GDP board. The
following procedure details how to check the DSPs using a Local Maintenance Terminal (LMT)
connected to the RXCDR containing the suspect XCDR board.

The following test equipment is required to test the DSP:
9-way to 25-way GPROC cable, see Chapter 2 Test leads required.
Commands used
Function
Command
msg_send
Replicates the internal message structure.
disp_act_alarm
Displays the active alarms.
68P02901W43-P
23 Feb 2004
8-25
GMR-01
DSP test
Preparation for testing the DSP

Use the following procedure to prepare for DSP testing:
Procedure 8-1
Prepare for testing DSP
Disable the suspect transcoder board using the front panel tri-state switch.
This will bring up an alarm in the event window at the OMC-R.
Connect the serial A port on the PC to a GPROC TTY port using the 9-way to
25-way cable.

3
Start the terminal emulator software on the PC.
DSP test procedure

Use the following procedure to test the DSP:
Procedure 8-2
1
Test DSP
Press CTRL-n to enter the Executive Monitor (EMON), and at the prompt enter
the command:
msg_send 75 4 74 7791h 2622h 9 x x x 4 3 1 2 3 4
Where: x x x is XCDR MSI number.
Sending this message makes the Fault Translation Process (FTP) think the device
is in-service, when it is actually disabled.
At the EMON prompt enter the command:

msg_send 4ah 50h 0 0 2371h 9 x x x 10 2
This message will generate a DSP check failure alarm.
Exit the Executive Monitor and at the MMI-RAM prompt enter the command:
disp_act_alarm #
Where: # is location id.
ailed alarm should appear, upon receipt of the command in step 2.
8-26
GMR-01
68P02901W43-P
23 Feb 2004
Procedure 8-2
4
DSP test
Test DSP (Continued)
Press CTRL-n to enter the EMON, and at the prompt enter the command:
msg_send 4ah 50h 0 0 2371h 9 x x x 10 1
This message will clear the alarm.
Exit the EMON and at the MMI-RAM prompt enter the command:
disp_act_alarm #
Where: # is location id.
The alarm generated in step 2 should now be cleared.
To re-generate and clear the alarm repeat step 2 to step 5.
Site restoration
Use the following procedure to restore the site on completion of testing:
Procedure 8-3
68P02901W43-P
23 Feb 2004
Restore site after DSP test
Reset or replace the transcoder board as necessary.

To replace the transcoder board follow the procedure detailed in Maintenance
Information: BSC/RXCDR (68P02901W38).
Inform the OMC-R that the test is complete.
8-27
GMR-01
DSP test
8-28
GMR-01
68P02901W43-P
23 Feb 2004
Chapter
9
Optimization results forms
The results of optimization tests carried out at equipment commissioning need to be recorded
to form a known baseline for future reference.
This chapter contains the following blank examples of forms used for recording optimization results:
BTS optimization results forms.
BSC/RXCDR optimization results forms.
Drive test optimization forms.
The forms may be photocopied for use so that the originals are kept unmarked for future use.
68P02901W43-P
23 Feb 2004
9-1
GMR-01
BTS optimization results forms
Complete the forms in this section while optimizing the equipment. Photocopy them
as necessary to avoid writing on the originals.
The following forms are provided:
Personnel details.
DC power supply tests.
Antenna reflected power tests.
PIX tests.
DRCU tests.
CTU850 tests.
SCU900 tests.
TCU900 tests
TCU-B tests.
CTU900 tests.
SCU1800 tests.
TCU1800 tests.
CTU1800 tests.
TCU1900 tests
CTU1900 tests.
Loopback and RTC checks.
Site documentation check.
9-2
GMR-01
68P02901W43-P
23 Feb 2004
Personnel details
Cell Site Name.........................................................................
Cell Site Number......................................................................
Date
Engineers Name........................................................................
Signature
Customer Representative...........................................................
Signature
DC power supply tests

Battery supply
V
68P02901W43-P
23 Feb 2004
PSU output
V
DC input to cabinet
V
9-3
GMR-01
Antenna reflected power tests

Antenna
Forward power
Reverse power
Sector 1 Tx
Rx 1
Rx 2
Sector 2 Tx
Rx 1
Rx 2
Sector 3 Tx
Rx 1
Rx 2
Omni
Tx
Rx 1
Rx 2
Channel
PIX tests
Tick the boxes if all alarms show, then clear the alarms.
PIX0/slot 15
PIX0/slot 16
PIX1/slot 17
PIX1/slot 18
9-4
GMR-01
68P02901W43-P
23 Feb 2004
BTS4 and BTS5 systems use slots 15 and 16 only.

BTS6 systems use slots 16, 17, and 18 only.
68P02901W43-P
23 Feb 2004
9-5
GMR-01
DRCU tests
The following test forms are provided in this section for DRCU tests:
DCRU 0 tests for slot number 0
9-6
GMR-01
68P02901W43-P
23 Feb 2004
DRCU 0 tests
Serial Number ____________
Slot Number ______ 0______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at top of cabinet
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)
Receive Bay Level Calibration

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
12
12
20
20
28
28
36
36
44
44
52
52
60
60
68
68
76
76
84
84
92
92
100
100
108
108
116
116
122
122
Ant 1
Ant 2
Ant 3
9-7
GMR-01
DRCU 1 tests
Slot Number ______ 1______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
12
12
20
20
28
28
36
36
44
44
52
52
60
60
68
68
76
76
84
84
92
92
100
100
108
108
116
116
122
122
9-8
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
DRCU 2 tests
Slot Number ______ 2______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
12
12
20
20
28
28
36
36
44
44
52
52
60
60
68
68
76
76
84
84
92
92
100
100
108
108
116
116
122
122
Ant 1
Ant 2
Ant 3
9-9
GMR-01
DRCU 3 tests
Slot Number ______ 3______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
12
12
20
20
28
28
36
36
44
44
52
52
60
60
68
68
76
76
84
84
92
92
100
100
108
108
116
116
122
122
9-10
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
DRCU 4 tests
Slot Number ______ 4______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
12
12
20
20
28
28
36
36
44
44
52
52
60
60
68
68
76
76
84
84
92
92
100
100
108
108
116
116
122
122
Ant 1
Ant 2
Ant 3
9-11
GMR-01
DRCU 5 tests
Slot Number ______ 5______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
12
12
20
20
28
28
36
36
44
44
52
52
60
60
68
68
76
76
84
84
92
92
100
100
108
108
116
116
122
122
9-12
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CTU850 tests
The following test forms are provided in this section for CTU850 tests:
68P02901W43-P
23 Feb 2004
CTU850 0 tests for slot number 0
9-13
GMR-01
CTU850 0 tests
Slot Number ______ 0______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
132
132
140
140
148
148
156
156
164
164
172
172
180
180
188
188
196
196
204
204
212
212
220
220
228
228
236
236
244
244
250
250
9-14
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CTU850 1 tests
Slot Number ______ 1______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
132
132
140
140
148
148
156
156
164
164
172
172
180
180
188
188
196
196
204
204
212
212
220
220
228
228
236
236
244
244
250
250
Ant 1
Ant 2
Ant 3
9-15
GMR-01
CTU850 2 tests
Slot Number ______ 2______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
132
132
140
140
148
148
156
156
164
164
172
172
180
180
188
188
196
196
204
204
212
212
220
220
228
228
236
236
244
244
250
250
9-16
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CTU850 3 tests
Slot Number ______3______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
132
132
140
140
148
148
156
156
164
164
172
172
180
180
188
188
196
196
204
204
212
212
220
220
228
228
236
236
244
244
250
250
Ant 1
Ant 2
Ant 3
9-17
GMR-01
CTU850 4 tests
Slot Number ______ 4______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
132
132
140
140
148
148
156
156
164
164
172
172
180
180
188
188
196
196
204
204
212
212
220
220
228
228
236
236
244
244
250
250
9-18
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CTU850 5 tests
Slot Number ______ 5______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
132
132
140
140
148
148
156
156
164
164
172
172
180
180
188
188
196
196
204
204
212
212
220
220
228
228
236
236
244
244
250
250
Ant 1
Ant 2
Ant 3
9-19
GMR-01
SCU/TCU900/ TCU-B/CTU900 tests

The following test forms are provided in this section for SCU/TCU900/ TCU-B/CTU900 tests:
SCU/TCU900/ TCU-B/CTU900 0 tests for slot number 0
9-20
GMR-01
68P02901W43-P
23 Feb 2004
SCU/TCU900/TCU-B/CTU900 0 tests
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
11
11
19
19
27
27
35
35
43
43
51
51
59
59
67
67
75
75
83
83
91
91
99
99
107
107
115
115
123
123
EGSM ONLY
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
EGSM ONLY
979
979
987
987
995
995
1003
1003
1011
1011
1019
1019
9-21
GMR-01
Slot Number ______ 1______
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
11
11
19
19
27
27
35
35
43
43
51
51
59
59
67
67
75
75
83
83
91
91
99
99
107
107
115
115
123
123
EGSM ONLY
979
987
987
995
995
1003
1003
1011
1011
1019
1019
GMR-01
Ant 2
Ant 3
EGSM ONLY
979
9-22
Ant 1
68P02901W43-P
23 Feb 2004
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)
Receive Bay Level Caibration

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
11
11
19
19
27
27
35
35
43
43
51
51
59
59
67
67
75
75
83
83
91
91
99
99
107
107
115
115
123
123
EGSM ONLY
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
EGSM ONLY
979
979
987
987
995
995
1003
1003
1011
1011
1019
1019
9-23
GMR-01
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
11
11
19
19
27
27
35
35
43
43
51
51
59
59
67
67
75
75
83
83
91
91
99
99
107
107
115
115
123
123
EGSM ONLY
979
987
987
995
995
1003
1003
1011
1011
1019
1019
GMR-01
Ant 2
Ant 3
EGSM ONLY
979
9-24
Ant 1
68P02901W43-P
23 Feb 2004
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
11
11
19
19
27
27
35
35
43
43
51
51
59
59
67
67
75
75
83
83
91
91
99
99
107
107
115
115
123
123
EGSM ONLY
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
EGSM ONLY
979
979
987
987
995
995
1003
1003
1011
1011
1019
1019
9-25
GMR-01
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
132
11
140
19
148
27
156
35
164
43
172
51
51
59
59
67
67
75
75
83
83
91
91
99
99
107
107
115
115
123
123
EGSM ONLY
979
987
987
995
995
1003
1003
1011
1011
1019
1019
GMR-01
Ant 2
Ant 3
EGSM ONLY
979
9-26
Ant 1
68P02901W43-P
23 Feb 2004
SCU/TCU1800/ CTU1800 tests

The following test forms are provided in this section for SCU/TCU1800/ CTU1800 tests:
68P02901W43-P
23 Feb 2004
SCU/TCU1800/ CTU1800 0 tests for slot number 0
9-27
GMR-01
SCU/TCU1800/CTU1800 0 tests
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
9-28
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
Receive Bay Level Calibration (continued) - Slot Number 0

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
812
812
820
820
828
828
836
836
844
844
852
852
860
860
868
868
876
876
883
883
Ant 1
Ant 2
Ant 3
9-29
GMR-01
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
9-30
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
812
812
820
820
828
828
836
836
844
844
852
852
860
860
868
868
876
876
883
883
Ant 1
Ant 2
Ant 3
9-31
GMR-01
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
9-32
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
812
812
820
820
828
828
836
836
844
844
852
852
860
860
868
868
876
876
883
883
Ant 1
Ant 2
Ant 3
9-33
GMR-01
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
9-34
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
812
812
820
820
828
828
836
836
844
844
852
852
860
860
868
868
876
876
883
883
Ant 1
Ant 2
Ant 3
9-35
GMR-01
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
9-36
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
812
812
820
820
828
828
836
836
844
844
852
852
860
860
868
868
876
876
883
883
Ant 1
Ant 2
Ant 3
9-37
GMR-01
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
9-38
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
812
812
820
820
828
828
836
836
844
844
852
852
860
860
868
868
876
876
883
883
Ant 1
Ant 2
Ant 3
9-39
GMR-01
TCU1900/ CTU1900 tests

The following test forms are provided in this section for TCU1900/ CTU1900 tests:
TCU1900/ CTU1900 0 tests for slot number 0
9-40
GMR-01
68P02901W43-P
23 Feb 2004
TCU1900/CTU1900 0 tests
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
Ant 1
Ant 2
Ant 3
9-41
GMR-01

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
809
809
9-42
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
Ant 1
Ant 2
Ant 3
9-43
GMR-01

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
809
809
9-44
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
Ant 1
Ant 2
Ant 3
9-45
GMR-01

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
809
809
9-46
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
Ant 1
Ant 2
Ant 3
9-47
GMR-01

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
809
809
9-48
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
Ant 1
Ant 2
Ant 3
9-49
GMR-01

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
809
809
9-50
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
CSPWR
P:
Cell Site Offset

Hex
dBm
Loss in test cable
O/P at SCU/TCU PA
dB
Watts
Watts (on meter)
Watts (on meter)

Rx 1
Rx 2
Chan
68P02901W43-P
23 Feb 2004
Ant 1
Ant 2
Ant 3
Chan
516
516
524
524
532
532
540
540
548
548
556
556
564
564
572
572
580
580
588
588
596
596
604
604
612
612
620
620
628
628
636
636
644
644
652
652
660
660
668
668
676
676
684
684
692
692
Ant 1
Ant 2
Ant 3
9-51
GMR-01

Rx 1
Rx 2
Chan
Ant 1
Ant 2
Ant 3
Chan
700
700
708
708
716
716
724
724
732
732
740
740
748
748
756
756
764
764
772
772
780
780
788
788
796
796
804
804
809
809
9-52
GMR-01
Ant 1
Ant 2
Ant 3
68P02901W43-P
23 Feb 2004
Loopback and RTC checks

E1/T1 loopback - BTS
MS1
SLOT
PORT
MS3
T43 BIB
SLOT
PORT
DDF
12/A
13/A
12B
13/B
14/A
15/A
14/B
15/B
16/A
17/A
16/B
17/B
T43 BIB
DDF
Site documentation check

Tick box if the distribution frame (DDF) is wired as in the site documentation.
If not, list the changes below or on a separate sheet of paper.
68P02901W43-P
23 Feb 2004
9-53
GMR-01
Complete the forms in this section while optimizing the equipment. Photocopy them as
necessary, but do not write on the originals.

Complete the forms in this section while optimizing the equipment. Photocopy the forms
as necessary to avoid writing on the originals.
The following forms are included:
Personnel details.
DC power supply tests.
PIX tests.
E1/T1 loopback - BSC.
E1/T1 loopback - RXCDR.
Site documentation check.
9-54
GMR-01
68P02901W43-P
23 Feb 2004
Personnel details
Cell Site Name..............................................................................
Cell Site Number ..........................................................................
Date
Engineers Name ............................................................................
Signature
Customer Representative ..............................................................
Signature
68P02901W43-P
23 Feb 2004
9-55
GMR-01
DC power supply tests

Battery supply
PSU output
DC input to cabinet
V
PIX tests
Tick the boxes if all alarms show then clear.
PIX0/slot 15
PIX0/slot 16
PIX1/slot 17
PIX1/slot 18
BTS4 and BTS5 systems use slots 15 and 16 only.

BTS6 systems use slots 16, 17, and 18 only.
9-56
GMR-01
68P02901W43-P
23 Feb 2004
E1/T1 loopback (BSC)

This is for maximum utilization. Checks can only be carried out if MSIs are equipped in
the database. If the cables have not been installed to the distribution frame but the boards
are equipped, then test loop to the T43 or BIB.
Upper shelf
MS 4
SLOT PORT
MS 5
T43 BIB
DDF
SLOT PORT
13/A
12/A
13/B
12/B
15/A
14/A
15/B
14/B
17/A
16/A
17/B
16/B
MS 6
SLOT PORT
DDF
T43 BIB
DDF
MS 7
T43 BIB
DDF
SLOT PORT
7/A
6/A
7/B
6/B
9/A
8/A
9/B
8/B
11/A
10/A
11/B
10/B
68P02901W43-P
23 Feb 2004
T43 BIB
9-57
GMR-01
Lower shelf
MS 0
SLOT PORT
MS 1
T43 BIB
DDF
SLOT PORT
13/A
12/A
13/B
12/B
15/A
14/A
15/B
14/B
17/A
16/A
17/B
16/B
MS 2
SLOT PORT
T43 BIB
DDF
T43 BIB
DDF
MS 3
T43 BIB
DDF
SLOT PORT
7/A
6/A
7/B
6/B
9/A
8/A
9/B
8/B
11/A
10/A
11/B
10/B
9-58
GMR-01
68P02901W43-P
23 Feb 2004
E1/T1 loopback (RXCDR)

This is for maximum utilization. Checks can only be carried out where MSIs or XCDRs are
equipped in the database. If the cables have not been installed to the distribution frame but
the boards are equipped, then test loop to the T43 or BIB.
Upper shelf
MS 4
SLOT PORT
MS 5
T43 BIB
DDF
SLOT PORT
19/A
13/A
20/B
14/B
21/A
15/A
22/B
16/B
23/A
17/A
24/B
18/B
MS 6
SLOT PORT
DDF
T43 BIB
DDF
MS 7
T43 BIB
DDF
SLOT PORT
9/A
6/A
9/B
6/B
10/A
7/A
10/B
7/B
11/A
8/A
12/A
8/B
68P02901W43-P
23 Feb 2004
T43 BIB
9-59
GMR-01
Lower shelf
MS 0
SLOT PORT
MS 1
T43 BIB
DDF
SLOT PORT
19/A
13/A
20/B
14/A
21/A
15/A
22/B
16/A
23/A
17/A
24/B
18/B
MS 2
SLOT PORT
T43 BIB
DDF
T43 BIB
DDF
MS 3
T43 BIB
DDF
SLOT PORT
9/A
6/A
9/B
6/B
10/A
7/A
10/B
7/B
11/A
8/A
12/A
8/B
9-60
GMR-01
68P02901W43-P
23 Feb 2004
Site documentation check

Tick box if the distribution frame (DDF) is wired as in the site documentation.
If not, list the changes below or on a separate sheet of paper.
68P02901W43-P
23 Feb 2004
9-61
GMR-01
Drive test optimization forms
Use the following forms as required when carrying out drive testing optimization. Photocopy
the forms as necessary, but do not write on the originals.
The forms included in this section are:
Tick sheet proforma.
Recommendation performa.
9-62
GMR-01
68P02901W43-P
23 Feb 2004
Tick Sheet Proforma

Time
Location
No
service
No
setup
No
audio
Noisy
Drop
Good
Comments
File Name:
1
2
3
4
5
6
7
8
9
10
File Name:
1
2
3
4
5
6
7
8
9
10
68P02901W43-P
23 Feb 2004
9-63
GMR-01
Recommendation Proforma
Equipment Type:
Recommendation Number:
Title
Description of issue:
Solution:
Impact:
9-64
GMR-01
68P02901W43-P
23 Feb 2004
Index
Index
B
base site
integrating
with logging software . . . . .
with no connection to the MSC .
without logging software . . . .
bay level offset calibration
DRCU . . . . . . . . . . . . .
DRCU3 . . . . . . . . . . . . .
DRCUII . . . . . . . . . . . . .
SCU900/1800 . . . . . . . . . .
TCU-B . . . . . . . . . . . . .
. . . . . . 6-5
. . . . . . 6-13
. . . . . . 6-9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-23
2-23
2-23
2-39
3-60
bay level offset calibration (contd.)

TCU900/1800/1900 . . . . . .
bay level offset tables
results forms
BSC/RXCDR . . . . . . . .
BTS/BSS/M-Cell . . . . . .
BSC
optimization results forms . . .
BTS
optimization results forms . . .
. . . . . . . 3-22
. . . . . . . 9-54
. . . . . . . 9-2
. . . . . . . 9-54
. . . . . . .
9-2
. . . . . . .
3-7
C
calibrating
GCLK. . . . . . . . . . . . .
M-Cell2/6 . . . . . . . . . .
MCU-m. . . . . . . . . . .
record form . . . . . . . . .
calibrating bay level offsets
DRCU . . . . . . . . . . . .
DRCU3 . . . . . . . . . . . .
DRCUII . . . . . . . . . . . .
SCU900/1800 . . . . . . . . .
TCU-B . . . . . . . . . . . .
TCU900/1800/1900 . . . . . .
calibrating transmitter output power
DRCU . . . . . . . . . . . .
DRCU3 . . . . . . . . . . . .
DRCUII . . . . . . . . . . . .
SCU900/1800 . . . . . . . . .
TCU-B . . . . . . . . . . . .
TCU900/1800/1900 . . . . . .
calibration, checking VSWR
DRCU . . . . . . . . . . . .
DRCU3 . . . . . . . . . . . .
DRCUII . . . . . . . . . . . .
SCU900/1800 . . . . . . . . .
TCU-B . . . . . . . . . . . .
68P02901W43-P
23 Feb 2004
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-84
2-61
5-29
2-65
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-23
2-23
2-23
2-39
3-60
3-22
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-21
2-21
2-21
2-32
3-41
3-7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-21
2-21
2-21
2-32
3-41
calibration, checking VSWR (contd.)

TCU900/1800/1900 . . . . . .
CCB
VSWR . . . . . . . . . . . .
CCB cavity tuning for TCUs
CCB cavity tuning for TCUs . .
channels
DCS1800 frequencies . . . . .
EGSM frequencies . . . . . . .
GSM850 frequencies . . . . . .
PCS1900 frequencies. . . . . .
PGSM frequencies . . . . . . .
checking
checking serial connections . . .
database devices and functions .
E1/T1 link . . . . . . . . . . .
M-Cell2/6 . . . . . . . . . .
circuit breakers
negative earth BSSC/RXCDR. .
negative earth BTS . . . . . . .
positive earth BSSC/RXCDR . .
positive earth BTS . . . . . . .
code
downloading. . . . . . . . . .
. . . . . . . 3-52
. . . . . . . 3-18
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . 3-82
. 2-50, 3-76
. . . . 3-79
. . . . 2-52
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-20
7-10
7-13
7-40
7-3
.
.
.
.
2-13
2-12
2-12
2-11
. . . . . . .
2-2
IX-1
GMR-01
Index
D
database
checking devices and functions
DCS1800
channel frequencies . . . . .
downloading code . . . . . . .
DRCU
identifying faults . . . . . . .
preserve calibration feature . .
DRCU calibration
bay level offset tables . . . .
checking VSWR . . . . . . .
transmitter output power . . .
DRCU term
definition . . . . . . . . . .
DRCU3
identifying faults . . . . . . .
DRCU3 calibration
DRCUII
DRCU2 . . . . . . . . . . .
DRCUII calibration
. . . . .
Drive testing
audio call faults . . . . . .
call classification. . . . . .
data analysis . . . . . . . .
data collection overview . .
data collection process . . .
diagnosing results . . . . .
drive test report . . . . . .
dropped call rate . . . . . .
effects of recommendations .
FICS . . . . . . . . . . .
handover failure rates . . .
high blocking cells . . . . .
mean time between drops . .
no audio calls . . . . . . .
noisy calls . . . . . . . . .
optimization . . . . . . . .
personnel requirements . . .
poor quality service calls . .
preparation . . . . . . . .
process . . . . . . . . . .
residual defect investigation
results forms . . . . . . . .
set up failure rates . . . . .
2-50, 3-76
. . . . . . . . 7-20
. . . . . . . . 2-2
. . . . . . . . 2-78
. . . . . . . . 4-2
. . . . . . . . 2-23
. . . . . . . . 2-21
. . . . . . . . 2-21
. . . . . . . .
2-1
. . . . . . . . 2-78
. . . . . . . . 2-23
. . . . . . . . 2-21
. . . . . . . . 2-21
. . . . . . . . 2-78
. . . . . . . . 2-23
. . . . . . . . 2-21
. . . . . . . . 2-21
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-23
8-13
8-15
8-12
8-12
8-15
8-23
8-18
8-24
8-12
8-16
8-21
8-23
8-20
8-20
8-7
8-12
8-20
8-7
8-11
8-24
9-62
8-17
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-76
2-77
2-70
2-73
2-72
2-70
2-73
2-68
2-71
2-68
E
E1/T1 link
checking . . . . .
M-Cell2/6 . . . .
M-Cellcity . . .
EGSM
channel frequencies
Excell alarms
verifying . . . . .
battery fault . . .
comms PSU fail .
door open . . . .
external 0 . . . .
external 1 . . . .
. . . . . . . . . . . . . 3-79
. . . . . . . . . . . . . 2-52
. . . . . . . . . . . . . 5-26
. . . . . . . . . . . . . 7-10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-66
2-74
2-74
2-69
2-75
2-76
IX-2
GMR-01
Excell alarms (contd.)

verifying (contd.)
external 2 . . . .
external 3 . . . .
fan fail . . . . .
inverter fail . . .
low dc voltage . .
mains fail . . . .
MCB trip . . . .
over temperature.
rectifier fail . . .
smoke . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W43-P
23 Feb 2004
Index
F
frequencies (contd.)
feature
4354 . . . . . . . . . 1-3, 2-19, 2-25, 2-34, 2-41,
2-50, 2-52, 2-54, 2-63, 2-67, 4-7, 8-26
frequencies
DCS1800 channels . . . . . . . . . . . . . . 7-20
EGSM channels . . . . . . . . . . . . . . . 7-10
frequencies (contd.)
GSM850 channels . . . . . . . . . . . . . . 7-13
PCS1900 channels . . . . . . . . . . . . . . 7-40
PGSM channels . . . . . . . . . . . . . . . 7-3
G
GCLK
calibrating . .
M-Cell2/6 .
M-Cellcity
record form
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
GSM850
channel frequencies . . . . . . . . . . . . . 7-13
3-84
2-61
5-29
2-65
I
integrating
the base site
with logging software . . . . . . . . . . . 6-5
with no connection to the MSC . . . . . . . 6-13
integrating (contd.)
the base site (contd.)
without logging software . . . . . . . . . . 6-9
the transcoder . . . . . . . . . . . . . . . . 2-56
M
M-Cell2/6
bay level offset calibration . . . . . . . 3-22, 3-60
TCU-B
bay level offset calibration . . . . . . . . . 3-60
TCU900/1800/1900
bay level offset calibration . . . . . . . . . 3-22
M-Cellcity
commissioning
M-Cellcity (contd.)
commissioning (contd.)
check, battery . . . . . . . .
check, E1/T1 link . . . . . .
downloading, code. . . . . .
downloading, from PCMCIA .
GCLK calibration . . . . . . .
test equipment . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5-24
. 5-26
. 5-2
. 5-8
. 5-29
. 5-4
N
network
optimization . . . . . . . . . . . . . . . . .
network optimization
stages . . . . . . . . . . . . . . . . . . . .
8-5
8-5
O
optimization
drive testing . . . . . . . . . . . . . . . . .
68P02901W43-P
23 Feb 2004
8-7
optimization (contd.)
equipment for . . . . . . . . . . . . . .
2-4, 6-3
IX-3
GMR-01
Index
network . . . . . .
results forms
BSC/RXCDR . .
BTS/BSS/M-Cell
drive testing . . .
. . . . . . . . . . . . .
8-5
. . . . . . . . . . . . . 9-54
. . . . . . . . . . . . . 9-2
. . . . . . . . . . . . . 9-62
test leads
9-way to 25-way.
9-way to 9-way .
test plugs
A. . . . . . . .
B. . . . . . . .
C. . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
2-6
2-6
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
2-7
2-7
2-8
P
PCS1900
PGSM
power
power (contd.)
circuit breakers
negative earth BSSC/RXCDR
negative earth BTS . . . . .
positive earth BSSC/RXCDR .
positive earth BTS . . . . . .
preserve calibration feature . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-13
2-12
2-12
2-11
4-2
R
RXCDR
optimization results forms . . . . . . . . . . 9-54
S
SCU900/1800
identifying faults . . . . . . . . . . . . . . . 2-78
preserve calibration function . . . . . . . . . 4-2
SCU900/1800 calibration
IX-4
GMR-01
SCU900/1800 calibration (contd.)

bay level offset tables . . . . . . . . . . . . 2-39
checking VSWR . . . . . . . . . . . . . . . 2-32
transmitter power output . . . . . . . . . . . 2-32
68P02901W43-P
23 Feb 2004
Index
T
TCU-B calibration
bay level offset tables . . .
checking VSWR . . . . . .
transmitter power output . .
TCU900/1800/1900
preserve calibration feature .
TCU900/1800/1900 calibration
bay level offset tables . . .
checking VSWR . . . . . .
transmitter output power . .
test equipment
2.048 Mbit/s checks
M-Cellcity . . . . . . .
calibration . . . . . . . . .
for optimization . . . . . .
integrating base site
without logging software .
integrating the base site. . .
no connection to the MSC
with logging software . .
Test equipment
hardware integration . . . .
test leads
for optimization
9-way to 25-way. . . . . . .
9-way to 9-way . . . . . . .
test plugs
for optimization
A. . . . . . . . . . . . . .
B. . . . . . . . . . . . . .
C. . . . . . . . . . . . . .
testing
dc power supply . . . . . . . .
transcoder
integrating . . . . . . . . . . .
transmitter output power calibration
DRCU . . . . . . . . . . . .
DRCU3 . . . . . . . . . . . .
DRCUII . . . . . . . . . . . .
SCU900/1800 . . . . . . . . .
TCU-B . . . . . . . . . . . .
TCU900/1800/1900 . . . . . .
tuning the RTC . . . . . . . . . .
. . . . . . . . . 3-60
. . . . . . . . . 3-41
. . . . . . . . . 3-41
. . . . . . . . .
4-2
. . . . . . . . . 3-22
. . . . . . . . . 3-7
. . . . . . . . . 3-7
. . . . . . . . . 5-26
. . . . . . . . . 2-4
. . . . . . . 2-4, 6-3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6-9
. 8-25
. 6-13
. 6-5
. . . . . . . . .
. . . . . . .
. . . . . . .
2-6
2-6
. . . . . . .
. . . . . . .
. . . . . . .
2-7
2-7
2-8
. . . . . . .
2-9
. . . . . . . 2-56
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-20
2-20
2-20
2-32
3-41
3-7
2-14
3-3
V
verifying
Excell alarms . . .
battery fault . . .
comms PSU fail .
door open . . . .
external 0 . . . .
external 1 . . . .
external 2 . . . .
external 3 . . . .
fan fail . . . . .
inverter fail . . .
low dc voltage . .
mains fail . . . .
MCB trip . . . .
over temperature.
68P02901W43-P
23 Feb 2004
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-66
2-74
2-74
2-69
2-75
2-76
2-76
2-77
2-70
2-73
2-72
2-70
2-73
2-68
verifying (contd.)
Excell alarms (contd.)
rectifier fail . . .
smoke . . . . .
VSWR
TCU-B
CCBs . . . . . .
VSWR, checking
DRCU . . . . . .
DRCU3 . . . . . .
DRCUII . . . . . .
SCU900/1800 . . .
TCU-B . . . . . .
TCU900/1800/1900
. . . . . . . . . . . . . 2-71
. . . . . . . . . . . . . 2-68
. . . . . . . . . . . . . 3-52
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-21
2-21
2-21
2-32
3-41
3-7
IX-5
GMR-01

Motorola BSS Optimization

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Motorola BSS Optimization

Uploaded by

Copyright:

Available Formats

CHAPTER 1

GSM Manual Revision dated 23 Feb 2004

Motorola manual affected

Installation & Configuration: BSS Optimization

Reason for revision

All pages between the clear acetate

All pages of the GMR between the front

Motorola service web

INSTALLATION & CONFIGURATION

INSTALLATION & CONFIGURATION

Installation & Configuration: BSS

1994 - 2004 Motorola, Inc.

Installation & Configuration: BSS Optimization

Chapter 1: Introduction to BSS optimization

Chapter 2: InCell, ExCell and TopCell optimization

Installation & Configuration: BSS Optimization

Calibration check procedure . . . . . .

Procedure during normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3: M-Cell2 and M-Cell6 optimization

Installation & Configuration: BSS Optimization

VSWR calibration procedure. . . . . . . . . .

Chapter 4: Preserve calibration

Chapter 5: Microcellular systems optimization

Chapter 6: Base site integration

Installation & Configuration: BSS Optimization

Test equipment required . . . . . . . .

Chapter 7: Channel numbers and frequencies

Network optimization tools . . . . . . . . . . .

Chapter 8: Network optimization

Chapter 9: Optimization results forms

This page intentionally left blank.

Table 1: Manual version history . . . . . . . . . . . . . . . . . .

Table 7-1: PGSM channels 1 to 10 . . . .

Table 7-56: DCS 1800 channels 751 to 760 . . . . . . .

This page intentionally left blank.

Installation & Configuration: BSS

What is Covered In This Manual?

Issue status of this manual

Issue status of this manual

Manual version history

Original issue - Software release 1.2.2.x

Issue A - Software release 1.2.3.x

Issue B - Software release 1.3.0.x

Issue C - Software release 1.4.0.x

Issue D - Software release 1.4.1.x

Issue E - GSM Software Release 2

Issue F - GSM Software Release 3

Issue G - GSM Software Release 4

Issue H - GSM Software Release 4.1

Issue J - GSM Software Release 5

Issue K - GSM Software Release 5.1

Issue L - GSM Software Release 6

Issue M - GSM Software Release 6 (Horizon II)

Issue P - GSM Software Release 7

Issue status of this manual

Resolution of Service Requests

Service requests resolved in this manual

Failure to comply with Motorolas operation, installation and maintenance

The tags have the format: {nnnn} or {nnnnn}

the RDB number

the RDP number

The tags are positioned in text as follows:

Tag position in text

New sentence/s or new or amended text.