BTS4812ET Opto R22

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE
Notice
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any
inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been
carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Motorola,
Inc. reserves the right to make changes to any products described herein 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, Inc. does not
assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others.
It is possible that this publication may contain references to, or information about Motorola products (machines and programs),
programming, or services that are not announced in your country. Such references or information must not be construed to mean
that Motorola intends to announce such Motorola products, programming, or services in your country.
Copyrights
This instruction manual, and the Motorola products described in this instruction manual may be, include or describe copyrighted
Motorola material, such as computer programs stored in semiconductor memories or other media. Laws in the United States and
other countries preserve for Motorola and its licensors certain exclusive rights for copyrighted material, including the exclusive
right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any
copyrighted material of Motorola and its licensors contained herein or in the Motorola products described in this instruction manual
may not be copied, reproduced, distributed, merged or modified 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, as arises by operation of law in the sale of a
product.
Computer Software Copyrights

The Motorola and 3rd Party supplied Software (SW) products described in this instruction manual may include copyrighted Motorola
and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including
the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola or
other 3rd Party supplied SW computer programs contained in the Motorola products described in this instruction manual may not be
copied (reverse engineered) or reproduced in any manner without the express written permission of Motorola or the 3rd Party SW
supplier. 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 or other 3rd Party supplied SW, except for the
normal nonexclusive, royalty free license to use that arises by operation of law in the sale of a product.
VENDOR
Apache Software Foundation
Artesyn
CMU *
Freeware Tools / Utilities *
Performance Technologies
Telelogic
QNX *
* Freeware
COPYRIGHT
Copyright 20022003
Copyright 20022003
Copyright 20022003
Copyright 20022003
Copyright 20022003
Copyright 20022003
Copyright 20022003
All Rights Reserved

All Rights Reserved
All Rights Reserved
All Rights Reserved
All Rights Reserved
All Rights Reserved
All Rights Reserved
Usage and Disclosure Restrictions

License Agreement
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express license
agreement only and may be used only in accordance with the terms of such an agreement.
Copyrighted Materials
Software and documentation are copyrighted 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, Inc.
High Risk Activities
Components, units, or thirdparty products used in the product described herein are NOT faulttolerant and are NOT designed,
manufactured, or intended for use as online control equipment in the following hazardous environments requiring failsafe
controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life
Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s) specifically disclaim any expressed or implied
warranty of fitness for such High Risk Activities.
Trademarks
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are
the property of their respective owners.
Copyright 2009 Motorola, Inc.
Javat Technology and/or J2MEt: Java and all other Javabased marks are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
UNIXR: UNIX is a registered trademark of The Open Group in the United States and other countries.
3ComR and OfficeConnectR: 3Com and OfficeConnect are registered trademarks of the 3Com Corporation.
MicrosoftR, WindowsR. Windows MeR, and Windows XPt: Microsoft, Windows and Windows Me are registered trademarks of
Microsoft Corporation; Windows XP is a trademark of Microsoft Corporation.
CiscoR, Cisco IOSR, and IOSR: Cisco, Cisco IOS, and IOS are registered trademarks of Cisco Systems, Inc. and/or its affiliates in
the U.S. and certain other countries.
PC Cardt: PC Card is a trademark of the Personal Computer Memory Card International Association (PCMCIA)
Anritsut is a trademeark of the Anritsu Company.
REV052604
Table of Contents
1X SC4812ET BTS Optimization/ATP
Software Release 2.22.0.x
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xi
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xviii
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xix
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xix
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxi
Security Advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxii
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiii
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiii
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiii
Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiii
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiv
Caring for the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxv
CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxvi
Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxvii
Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxvii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxviii
Third Party computer software and trademarks . . . . . . . . . . . . . . . . . . . . . . . . .
xxviii
FCC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxix
Chapter 1: Introduction
Scope, Assumptions, and Audience
SEP 2009
.................................
1-1
Content Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
Purpose of Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4
When to Perform BTS RF Calibration and Acceptance Testing . . . . . . . . . . . .
1-5
General Test Equipment Selection, Calibration, and

Operation Requirememnts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8
Required Test Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-9
Required Documents and Related Publications . . . . . . . . . . . . . . . . . . . . . . . . .
1-15
Table of Contents continued

Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-17
BTS Equipment Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-22
Sector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-35
Chapter 2: Preliminary Operations

Preliminary Operations: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
Site Equipage Verification and Card/Module Installation . . . . . . . . . . . . . . . . .
2-2
Frame Identification Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4
PrePowerup Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
AC Power Up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-8
PreDC Powerup test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-10
RF Cabinet Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-12
Power Cabinet Battery Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-14
Heat Exchanger Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-16
Circuit Breaker Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-17
Chapter 3: Optimization/Calibration
ii
Introduction to Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1
Preparing the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-5
Prepare the LMF Computer for MMI Communication . . . . . . . . . . . . . . . . . . .
3-12
Optional Channel Service Units (CSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-15
Punchblocks and Pin/Signal Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-17
LMF to BTS Connection Service Shelf Connection . . . . . . . . . . . . . . . . . . . .
3-23
Using the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-25
Establishing an MMI Communication Session . . . . . . . . . . . . . . . . . . . . . . . . .
3-38
LMF Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-40
Pinging the Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-41
Take Control of Packet BTS Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-45
Download the BTS General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-47
Download BTS Loading Packet GLI Devices . . . . . . . . . . . . . . . . . . . . . . . . .
3-49
Download BTS Loading NonGLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . .
3-52
Enabling Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-55
CSM System Time GPS, LFR, and HSO/MSO Verification . . . . . . . . . . . . .
3-59
Test Equipment Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-72
Test Equipment Connection to the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-93
Test Equipment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-96
Test Set Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-103
Setting and Editing Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . .
3-109
SEP 2009

Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-111
Bay Level Offset Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-123
TX BLO Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-131
Download BLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-134
TX Calibration Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-135
Create CAL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-136
RFDS Setup and Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-137
Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration . .
3-148
Alarms Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-149
Chapter 4: Automated Acceptance Test Procedure

Acceptance Test Procedures Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1
Automated Acceptance Test Procedures TX & RX . . . . . . . . . . . . . . . . . . . . .
4-3
Individual Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-8
TX Spectral Purity Transmit Mask Acceptance Test . . . . . . . . . . . . . . . . . . . . .
4-10
TX Waveform Quality (rho) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . .
4-12
TX Pilot Time Offset Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-13
TX Code Domain Power/Noise Floor Acceptance Test . . . . . . . . . . . . . . . . . . .
4-14
RX Frame Error Rate (FER) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . .
4-16
Receive Signal Strength Indication (RSSI) Acceptance Test . . . . . . . . . . . . . . .
4-17
Generate an ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-19
Chapter 5: Configuring Packet BTS Transport

Introduction to Packet BTS Transport Configuration . . . . . . . . . . . . . . . . . . . . .
5-1
GLI3 Required Software Release, Operating Mode, and Loading Code . . . . . .
5-3
GLI3 Card Software Version and Backhaul Mode . . . . . . . . . . . . . . . . . . . . . . .
5-5
Preloading GLI3 Cards in Packet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-10
Configure GLI3 Cards for IBR Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-12
Configure GLI3 Cards for Operation with External BTS Routers . . . . . . . . . . .
5-27
Configuring BTS File Transfer Protocol Introduction . . . . . . . . . . . . . . . . . .
5-33
Configuring BTS File Transfer Protocol New BTS Installation . . . . . . . . . . .
5-35
GLI3 Software Release and Backhaul Mode Worksheet . . . . . . . . . . . . . . . . . .
5-37
Chapter 6: Prepare to Leave the Site

Updating Calibration Data Files Packet BTS . . . . . . . . . . . . . . . . . . . . . . . . .
6-1
Prepare to Leave the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5
Chapter 7: Basic Troubleshooting

Basic Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEP 2009
7-1
iii

Troubleshooting: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
Troubleshooting: Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-8
Troubleshooting: Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-10
Troubleshooting: Transmit ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-12
Troubleshooting: Receive ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-16
Troubleshooting: CSM Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-17
CCCP Backplane Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-19
Troubleshooting: Span Control Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-27
Troubleshooting: GLI3 card continually reboots after converting to

satellite backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-35
Module Front Panel LED Indicators and Connectors . . . . . . . . . . . . . . . . . . . . .
7-42
Appendix A: System Data

Site Operation Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-1
Appendix B: PN Offset
PN Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-1
Appendix C: ATP Matrix Table

Reoptimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C-1
Appendix D: BBX Gain

BBX Gain Set Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D-1
Appendix E: CDMA Operating Frequency

CDMA Operating Frequency Programming Information . . . . . . . . . . . . . . . . .
E-1
1900 MHz PCS Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-2
800 MHz CDMA Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-5
Appendix F: Test Equipment Preparation
iv
Test Equipment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-1
Test Equipment Setup: Agilent E7495 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-2
Verifying and Setting GPIB Addresses: Advantest R3267

Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-5
Verifying and Setting GPIB Addresses: Advantest R3465 Communications

Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-7
Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator . .
F-8
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set . .
F-9
Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester . .
F-11
Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter . . . . . . . .
F-13
Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator . . .
F-15
SEP 2009

Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter . . . .
F-17
Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box . . . . . . . .
F-18
Test Equipment Interconnection: Advantest R3267 and R3562 . . . . . . . . . . . . .
F-19
Test Equipment Interconnection: Agilent 8935 Series E6380 and E4438C . . .
F-20
Test Equipment Interconnection: Agilent E4406A and E4438C . . . . . . . . . . . .
F-21
Test Equipment Calibration: Agilent E4406A Selfalignment . . . . . . . . . . . . .
F-22
Test Equipment Calibration: Gigatronics 8542 Power Meter . . . . . . . . . . . . . . .
F-23
Cable Calibration with R3465 Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-24
Appendix G: Download ROM Code

Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G-1
Appendix H: Cable Interconnection

IntraCabinet Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-1
Appendix I: Inservice Calibration

Inservice Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I-1
Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I-3
InService Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I-14
Appendix J: Companion Frame Optimization

Optimizing the Companion Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J-1
Appendix K: BTS Router Initial Configuration

BTS Router Configuration Operations Introduction . . . . . . . . . . . . . . . . . . . .
K-1
Terminal Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-2
Establishing a BTS Router Communication Session . . . . . . . . . . . . . . . . . . . . .
K-5
Obtain BTS Router Minimum (Canned) Configuration Files from

the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-8
BTS Router IOS Version Verification and Canned Configuration

File Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-15
Change or Upgrade BTS Router IOS Version . . . . . . . . . . . . . . . . . . . . . . . . . .
K-35
Verify and Upgrade ROMmon Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-47
Recovery from BTS Router Boot to ROMmon . . . . . . . . . . . . . . . . . . . . . . . . .
K-57
Entering or Changing BTS Router FE Interface IP Addresses . . . . . . . . . . . . . .
K-72
Example BTS Router Canned Configuration Files . . . . . . . . . . . . . . . . . . . . . .
K-77
Network Interface Card (NIC) Configuration Worksheet . . . . . . . . . . . . . . . . . .
K-84
External BTS Router Compact Flash (CF) Memory Card Installation

and Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-85
Appendix L: MMI Cable Fabrication

MMI Cable Fabrication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L-1
Index
SEP 2009
List of Figures
vi
Figure 1-1: Null Modem Cable Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-10
Figure 1-2: SC 4812ET RF Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-23
Figure 1-3: RF Cabinet Internal Assemblies and FRUs . . . . . . . . . . . . . . . . . . .
1-25
Figure 1-4: SC 4812ET CCCP Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-27
Figure 1-5: SC 4812ET Intercabinet I/O Detail (Rear View) . . . . . . . . . . . . . . .
1-28
Figure 1-6: SC 4812ET I/O Plate Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-29
Figure 1-7: RFDS Location in an SC 4812ET RF Cabinet . . . . . . . . . . . . . . . .
1-30
Figure 1-8: Power Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-31
Figure 1-9: Power Cabinet with Batteries Installed

(Doors Removed for Clarity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-32
Figure 1-10: SC4812ET PA Configuration with Combiners/Filters . . . . . . . . .
1-38
Figure 2-1: SC4812Tseries BTS Switch Card DIP Switch Settings . . . . . . . .
2-3
Figure 2-2: SC4812Tseries BTS Backplane DIP Switch Settings for BTS or
Logical BTS Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4
Figure 2-3: AC Load Center Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-7
Figure 2-4: Meter Alarm Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-8
Figure 2-5: Temperature Compensation Panel . . . . . . . . . . . . . . . . . . . . . . . . . .
2-9
Figure 2-6: RF Cabinet Circuit Breaker Panel and 27 Vdc

Terminal Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-13
Figure 2-7: Battery Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-15
Figure 2-8: Heat Exchanger Blower Assembly . . . . . . . . . . . . . . . . . . . . . . . . .
2-16
Figure 2-9: Power Cabinet Circuit Breaker Assemblies . . . . . . . . . . . . . . . . . . .
2-18
Figure 2-10: Power Cabinet AC Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . .
2-19
Figure 2-11: Power Cabinet DC Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . .
2-20
Figure 3-1: LMF Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-6
Figure 3-2: Rear and Front View of the CSU . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-16
Figure 3-3: 50 Pair Punch Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-17
Figure 3-4: Service Shelf LAN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-23
Figure 3-5: BTS Login screen identifying circuit and packet BTS files . . . . .
3-27
Figure 3-6: SelfManaged Network Elements (NEs) state of a packet mode

BTS (SC4812T shown) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-28
SEP 2009
List of Figures continued
SEP 2009
Figure 3-7: Available packet mode commands . . . . . . . . . . . . . . . . . . . . . . . . . .
3-29
Figure 3-8: Packet mode BTS with MCC2 and BBX2 under LMF control .
3-30
Figure 3-9: CDMA LMF Computer Common MMI Connections Cable

CGDSMMICABLE219112 or Fabricated MMI Cable . . . . . . . . . . . . . . . . . . .
3-39
Figure 3-10: CDMA LMF Computer Common MMI Connections

Motorola MMI Interface Kit, SLN2006A . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-39
Figure 3-11: SC4812ET External 10Base2 Ethernet LAN

Connector Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-41
Figure 3-11: BTS Ethernet LAN Interconnect Diagram . . . . . . . . . . . . . . . . . .
3-42
Figure 3-12: CSM Front Panel PWR/ALM LED Indicator . . . . . . . . . . . . . . . .
3-60
Figure 3-13: CSM MMI Terminal Connection . . . . . . . . . . . . . . . . . . . . . . . . . .
3-64
Figure 3-14: TX Calibration Test Setup Agilent 8935 (IS95A/B &

CDMA2000 1X) (IS95A/B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-79
Figure 3-15: TX Calibration Test Setup Using Power Meter . . . . . . . . . . . . .
3-80
Figure 3-16: TX Calibration Test Setup Agilent E4406A and

Advantest R3267 (IS95A/B and CDMA2000 1X) . . . . . . . . . . . . . . . . . . . . . .
3-81
Figure 3-17: TX Calibration Test Setup Agilent E7495A and E7495B

(IS95A/B & CDMA2000 1X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-82
Figure 3-18: TX Calibration Test Setup Anritsu MT8212B (IS95A/B and

CDMA2000 1X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-83
Figure 3-19: ATP Test Setup, IS95A/B, TRDC Shown (Agilent 8935 and
Advantest R3465) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-84
Figure 3-20: ATP Test Setup, IS95A/B and CDMA2000 1X, with TRDC
(Agilent E4432B/8935 and Agilent E4432B/E4406A) . . . . . . . . . . . . . . . . . . .
3-85
Figure 3-21: ATP Test Setup, IS95A/B and CDMA2000 1X, with DRDC
(Advantest R3267/3562) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-86
(Advantest R3267/3562) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-87
Figure 3-23: IS95A/B and CDMA2000 1X Optimization/ATP Test Setup

Agilent E7495A and E7495B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-88
Figure 3-24: ATP Test Setup IS95A/B and CDMA2000 1X

(Anritsu MT8212B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-89
Figure 3-25: Alternate ATP Test Setups (Except Agilent E7495A/B and
Anritsu MT8121B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-90
Figure 3-26: Alternate ATP Test Setups (Agilent E7495A or E7495B) . . . . . . .
3-91
Figure 3-27: Alternate ATP Test Setups (Anritsu MT8212B) . . . . . . . . . . . . . .
3-92
Figure 3-28: IS95A/B Cable Calibration Test Setup Agilent 8935 . . . . . . . .
3-114
Figure 3-29: IS95A/B and CDMA 2000 1X Cable Calibration Test Setup
Agilent E4406A/E4432B and Advantest R3267/R3562 . . . . . . . . . . . . . . . . . .
3-115
Figure 3-30: CDMA2000 1X Cable Calibration Test Setup

Agilent E7495A or E7495B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-116
Anritsu MT8212B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-117
vii
viii
Figure 3-32: Calibrating Test Equipment Setup for TX BLO and TX ATP
Tests (using Signal Generator and Spectrum Analyzer) . . . . . . . . . . . . . . . . . . .
3-119
Figure 3-33: Calibrating Test Equipment Setup for RX ATP Test

(using Signal Generator and Spectrum Analyzer) . . . . . . . . . . . . . . . . . . . . . . .
3-120
Figure 3-34: Battery Overtemperature Sensor . . . . . . . . . . . . . . . . . . . . . . . . .
3-155
Figure 3-35: Location of Connector J8 on the Meter Alarm Panel . . . . . . . . . .
3-157
Figure 4-1: TX Mask Verification Spectrum Analyzer Display . . . . . . . . . . . . .
4-11
Figure 4-2: Code Domain Power and Noise Floor Levels . . . . . . . . . . . . . . . . .
4-15
Figure 6-1: Automated Calibration File Transfer Process

User and LMF Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2
Figure 6-2: Automated Calibration File Transfer Process

GLI3 and LMF Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
Figure 6-3: GLI3 Card MMI Connection Detail . . . . . . . . . . . . . . . . . . . . . . . .
6-7
Figure 6-4: GLI3 Card MMI Connection Detail Fabricated MMI Cable . . . .
6-8
7-28
7-29
Figure 7-3: CSM Front Panel Indicator and Monitor Connectors . . . . . . . . . . .
7-43
Figure 7-4: MCC Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-48
Figure E-1: North America PCS Frequency Spectrum (CDMA Allocation) . . .
E-2
Figure E-2: North American Cellular Telephone System Frequency Spectrum

(CDMA Allocation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-5
Figure F-1: Agilent E7495 PrePower Sensor Calibration connection . . . . . . .
F-3
Figure F-2: Agilent E7495 Power Sensor Calibration connection . . . . . . . . . . .
F-4
Figure F-3: Setting Advantest R3267 GPIB Address . . . . . . . . . . . . . . . . . . . . .
F-5
Figure F-4: R3465 Communications Test Set . . . . . . . . . . . . . . . . . . . . . . . . . .
F-7
Figure F-5: Advantest R3562 GPIB Address Switch Setting . . . . . . . . . . . . . .
F-8
Figure F-6: Agilent 8935 Series E6380 Test Set Verify and Set/Change
GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-9
Figure F-7: Agilent E4406A Transmitter Tester Verify and Set/Change

GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-11
Figure F-8: Agilent E4418B Power Meter Verify and Set/Change

GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-13
Figure F-9: Agilent E4438C Verify and Set/Change GPIB Address . . . . . . . . .
F-15
Figure F-10: Gigatronics 8541C Power Meter Detail . . . . . . . . . . . . . . . . . . . .
F-17
Figure F-11: Verify and Set/Change RS232 GPIB Interface Box

GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-18
Figure F-12: Advantest 10 MHz Reference and Serial I/O Connections . . . . . .
F-19
Figure F-13: Agilent 8935/E4438C 10MHz Reference and Even Second

Tick Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-20
Figure F-14: Agilent 10 MHz Reference Connections . . . . . . . . . . . . . . . . . . . .
F-21
Figure F-15: Agilent E4406A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-22
SEP 2009
SEP 2009
Figure F-16: Gigatronics 8541C Power Meter . . . . . . . . . . . . . . . . . . . . . . . . . .
F-23
Figure F-17: Cable Calibration using Advantest R3465 . . . . . . . . . . . . . . . . . .
F-27
Figure H-1: 4812ET RF Cabinet Internal FRU Locations . . . . . . . . . . . . . . . . .
H-3
Figure H-2: C-CCP Shelf Cable Numbers and Connectors . . . . . . . . . . . . . . . .
H-5
Figure H-3: CCCP Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-6
Figure H-4: PAs for the SC 4812ET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-7
Figure H-5: BTS Combiner to PA Backplane Cables . . . . . . . . . . . . . . . . . . . .
H-8
Figure H-6: Combiner to PA Backplane/PA Backplane to CIO Board Cables .
H-9
Figure H-7: Components Located on CIO Card . . . . . . . . . . . . . . . . . . . . . . . . .
H-10
Figure H-8: LPAC Interface Board Connectors and Attaching

Cable Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-11
Figure H-9: ETIB I/O Connectors and Attaching Cable Numbers . . . . . . . . . . .
H-12
Figure H-10: SPAN I/O Cables and Connectors . . . . . . . . . . . . . . . . . . . . . . . .
H-14
Figure H-11: 3 Sector, 2 Carrier BTS Combiner DRDC/TRDC

Cable Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-16
Figure H-12: BTS 2 to 1, 3 or 6 Sector Combiner DRDC/TRDC

H-17
Figure H-13: BTS Combiner DRDC/TRDC Cable Connection . . . . . . . . . . . .
H-18
Figure H-14: SC 4812ET BTS Combiner DRDC/TRDC Cable Connection . .
H-19
Figure H-15: DRDC To CCCP Cage MPC Boards Cable Connections . . . . .
H-21
Figure H-16: RFDS Component Identification . . . . . . . . . . . . . . . . . . . . . . . . .
H-22
Figure H-17: SC 4812ET BTS Combiner DRDC/TRDC RFDS

H-25
Figure H-18: 50 Pair Punchblock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-27
Figure H-19: SC 4812ET RF Cabinet Parts Locator . . . . . . . . . . . . . . . . . . . . .
H-33
Figure I-1: Delta Calibration Setup Agilent E4432B to HP437 . . . . . . . . . . .
I-5
Figure I-2: Delta Calibration Setup Agilent E4432B to Agilent E4406A . . .
I-5
Figure I-3: Delta Calibration Setup Advantest R3562 to HP437 . . . . . . . . . .
I-8
Figure I-4: Delta Calibration Setup Advantest R3562 to R3267 . . . . . . . . . .
I-8
Figure I-5: Delta Calibration Setup Agilent 8935 to HP437 . . . . . . . . . . . . . .
I-10
Figure I-6: Delta Calibration Setup Agilent 8935 to Agilent 8935 . . . . . . . . .
I-11
Figure I-7: Delta Calibration Setup R3561L to HP437 . . . . . . . . . . . . . . . . . .
I-13
Figure I-8: Delta Calibration Setup R3561L to R3465 . . . . . . . . . . . . . . . . . .
I-13
Figure I-9: TX Calibration Test Setup Agilent E4406A, Advantest R3267,

and Agilent 8935 with Option 200 or R2K (IS95A/B and 1X CDMA 2000) .
I-16
Figure I-10: TX Calibration Test Setup Advantest R3465 (IS95A/B only) .
I-17
Figure J-1: Cabling of SC 4812ET Companion BTS to SC 4812ET Companion

BTS (3 Sector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J-2
Figure J-2: WinLMF Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J-3
ix
Figure K-1: Wiring Diagram, BTS Router Communication Rollover Cable . . .
K-5
Figure K-2: Wiring Diagram, DB9 Plugto8contact Modular

Plug Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-6
Figure K-3: LMF Computer Connections to BTS Router . . . . . . . . . . . . . . . . .
K-7
Figure K-4: LMF Computer TFTP Connections to BTS Router . . . . . . . . . . . .
K-22
Figure K-5: Router CF Memory Card Removal . . . . . . . . . . . . . . . . . . . . . . . . .
K-85
Figure L-1: Fabricated MMI Cable Details . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L-1
SEP 2009
List of Tables
SEP 2009
FCC Part 68 Registered Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxx
Table 1-1: CDMA LMF Test Equipment Support Table . . . . . . . . . . . . . . . . . .
1-11
Table 1-2: Abbreviations and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-17
Table 1-3: CCCP Shelf/Cage Card/Module Device ID Numbers

(Top Shelf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-24
Table 1-4: CCCP Shelf/Cage Card/Module Device ID Numbers

(Bottom Shelf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-24
Table 1-5: BTS Sector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-35
Table 1-6: Sector Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-36
Table 2-1: Initial Installation of Cards/Modules . . . . . . . . . . . . . . . . . . . . . . . . .
2-2
Table 2-2: Initial Inspection and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-6
Table 2-3: AC Voltage Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-6
Table 2-4: Applying AC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-8
Table 2-5: Power Cabinet Power Up Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-9
Table 2-6: DC Power Pretest (BTS Frame) . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-10
Table 2-7: RF Cabinet Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-12
Table 2-8: Battery Charge Test (Connected Batteries) . . . . . . . . . . . . . . . . . . . .
2-14
Table 2-9: Battery Discharge Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-15
Table 2-10: Heat Exchanger Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-16
Table 3-1: LMF Application Program Installation . . . . . . . . . . . . . . . . . . . . . . .
3-9
Table 3-2: Copying NEC Files to the LMF Computer . . . . . . . . . . . . . . . . . . . .
3-10
Table 3-3: Establish HyperTerminal Connection . . . . . . . . . . . . . . . . . . . . . . . .
3-13
Table 3-4: PinOut for 50Pair Punchblock . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-18
Table 3-5: Connecting the LMF to the BTS, Service Shelf Connection . . . . . .
3-24
Table 3-6: BTS GUI Login Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-33
Table 3-7: BTS CLI Login Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-35
Table 3-8: BTS GUI Logout Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-36
Table 3-9: BTS CLI Logout Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-37
Table 3-10: Establishing MMI Communication . . . . . . . . . . . . . . . . . . . . . . . . .
3-38
Table 3-11: Pinging the Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-42
xi
List of Tables
xii
continued
Table 3-12: Take Control of Packet BTS Resources with the LMF . . . . . . . . . .
3-46
Table 3-13: Loading Code into Packet GLI3 Card with the LMF . . . . . . . . . . .
3-49
Table 3-14: Download RAM Code and Data or Data Only to

NonGLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-53
Table 3-15: Select CSM Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-55
Table 3-16: Enable CSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-56
Table 3-17: Enable MCCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-58
Table 3-18: CSM PWR/ALM LED Indications . . . . . . . . . . . . . . . . . . . . . . . . .
3-61
Table 3-19: Test Equipment Setup for GPS and

LFR/HSO/MSO/QHSO Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-63
Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification . . . . . . . . . .
3-65
Table 3-21: Loran Initialization/Verification . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-70
Table 3-22: IS95A/Bonly Test Equipment Interconnection . . . . . . . . . . . . . .
3-75
Table 3-23: CDMA2000 1X/IS95A/B Test Equipment Interconnection . . . . .
3-76
Table 3-24: Additional CDMA2000 1X/IS95A/B Test

Equipment Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-77
Table 3-25: Selecting a COM Port for GPIB or Serial Test

Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-93
Table 3-26: Disconnect and Reconnect the LMF and the Active COM Port . . .
3-94
Table 3-27: Manually Selecting Test Equipment GPIB Interface . . . . . . . . . .
3-97
Table 3-28: Autodetecting Test Equipment GPIB Interface . . . . . . . . . . . . . .
3-98
Table 3-29: Manually Selecting Test Equipment Serial Interface . . . . . . . . . .
3-99
Table 3-30: Autodetecting Test Equipment Serial Interface . . . . . . . . . . . . . .
3-100
Table 3-31: Manually Selecting Test Equipment Network Interface . . . . . . . .
3-101
Table 3-32: Autodetecting Test Equipment Network Interface . . . . . . . . . . . .
3-101
Table 3-33: Calibrate Test Equipment Power Measurement Zeroing . . . . . . .
3-105
Table 3-34: Anritsu MT8212B Multifunction Test Set Zero Out

Power Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-106
Table 3-35: Anritsu MT8212B Multifunction Test Set TX

Analyzer Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-107
Table 3-36: Anritsu MT8212B Multifunction Test Set CW

Generator Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-108
Table 3-37: Set or Edit Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . .
3-109
Table 3-38: Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-112
Table 3-39: Calibrating TX and Duplexed RX Cables Using Signal Generator

and Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-118
Table 3-40: Calibrating RX Cables Using a Signal Generator and

3-119
Table 3-41: Setting Cable Loss Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-121
Table 3-42: Setting Coupler Loss Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-122
SEP 2009
List of Tables continued
SEP 2009
Table 3-43: BLO BTS.cal file Array Branch Assignments . . . . . . . . . . . . . . . .
3-126
Table 3-44: BTS.cal File Array (Per Sector) . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-127
Table 3-45: Set Up Test Equipment for RF Path Calibration . . . . . . . . . . . . . . .
3-128
Table 3-46: All Cal/Audit and TX Calibration Procedure . . . . . . . . . . . . . . . . .
3-132
Table 3-47: Download BLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-134
Table 3-48: Create CAL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-136
Table 3-49: RFDS Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-138
Table 3-50: Defintion of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-141
Table 3-51: Valid NAM Field Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-142
Table 3-52: Set Antenna Map Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-143
Table 3-53: Set RFDS Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-144
Table 3-54: RFDS TSIC Calibration Channel Frequencies . . . . . . . . . . . . . . . .
3-145
Table 3-55: RFDS Calibration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-146
Table 3-56: Program NAM Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-147
Table 3-57: Alarm Testing Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-150
Table 3-58: Heat Exchanger Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-150
Table 3-59: Door Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-150
Table 3-60: AC Fail Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-151
Table 3-61: Minor Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-151
Table 3-62: Single Rectifier Fail or Minor Alarm . . . . . . . . . . . . . . . . . . . . . . .
3-152
Table 3-63: Multiple Rectifier Failure or Major Alarm . . . . . . . . . . . . . . . . . . .
3-152
Table 3-64: Single Rectifier Fail or Minor Alarm . . . . . . . . . . . . . . . . . . . . . . .
3-153
Table 3-65: Multiple Rectifier Failure or Major Alarm . . . . . . . . . . . . . . . . . . .
3-153
Table 3-66: Battery Over Temperature Alarm . . . . . . . . . . . . . . . . . . . . . . . . . .
3-154
Table 3-67: Rectifier Over Temperature Alarm . . . . . . . . . . . . . . . . . . . . . . . . .
3-156
Table 3-68: Check Before Leaving the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-157
Table 4-1: ATP Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6
Table 4-2: Reload Affected MCC(s) with Data After Redundant BBX TX
Testing with Standard Test Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-7
Table 4-3: Test RSSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-18
Table 4-4: Generating an ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-19
Table 5-1: Packet BTS Transport Conversions . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2
Table 5-2: GLI3 Packet Backhaul Mode and Software Release Required . . . . .
5-3
Table 5-3: GLI3 Code Loading Methods Based on Operating Mode . . . . . . . .
5-3
Table 5-4: GLI3 Backhaul Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-4
Table 5-5: Determine GLI3 Card Software Version and Backhaul Mode . . . . .
5-5
Table 5-6: Does GLI3 Card Need Configuration Change? . . . . . . . . . . . . . . . . .
5-8
xiii
List of Tables
xiv
continued
Table 5-7: Preload GLI3 Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-10
Table 5-8: Item Required for BTS Redundant GLI Cabling Integrated BTS
Router Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-12
Table 5-9: IBR Configuration Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-13
Table 5-10: IBR Conversion BTS Provisioned with Full Span(s) . . . . . . . . .
5-15
Table 5-11: IBR Conversion BTS Provisioned with Fractional Span . . . . . . .
5-20
Table 5-12: Prevent GLI3 Configuration Fallback . . . . . . . . . . . . . . . . . . . . . . .
5-26
Table 5-13: Items Required for FE Cabling External BTS Router Group . . .
5-27
Table 5-14: EBR Conversion Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-28
Table 5-15: Convert GLI3 Cards to EBR Operation . . . . . . . . . . . . . . . . . . . . .
5-30
Table 5-16: LMF File Transfer Protocol Selections . . . . . . . . . . . . . . . . . . . . . .
5-33
Table 5-17: Determine Operating File Transfer Protocol Using the LMF . . . . .
5-35
Table 5-18: Change Operating File Transfer Protocol Using the LMF . . . . . . .
5-36
Table 5-19: Software Release and Backhaul Mode Record . . . . . . . . . . . . . . . .
5-37
Table 6-1: Uploading Calibration File to a Packet BTS . . . . . . . . . . . . . . . . . . .
6-4
Table 6-2: External Test Equipment Removal . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5
Table 6-3: IBR Span Parameter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5
Table 6-4: Bring Modules into Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-9
Table 6-5: LMF Termination and Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-10
Table 6-6: Span/IFM Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-10
Table 6-7: Reset BTS Devices and Remote Site Initialization . . . . . . . . . . . . . .
6-11
Table 7-1: Login Failure Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . . .
7-2
Table 7-2: Force Ethernet LAN A to Active State as Primary LAN . . . . . . . . .
7-2
Table 7-3: GLI IP Address Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-3
Table 7-4: Turn Off Video Card Acceleration . . . . . . . . . . . . . . . . . . . . . . . . . .
7-5
Table 7-5: Troubleshooting a Power Meter Communication Failure . . . . . . . . .
7-6
Table 7-6: Troubleshooting a Communications Analyzer

Communication Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-6
Table 7-7: Troubleshooting a Signal Generator Communication Failure . . . . . .
7-7
Table 7-8: Troubleshooting Code Download Failure . . . . . . . . . . . . . . . . . . . . .
7-8
Table 7-9: Troubleshooting Data Download Failure . . . . . . . . . . . . . . . . . . . . .
7-9
Table 7-10: Troubleshooting Device Enable (INS) Failure . . . . . . . . . . . . . . . .
7-9
Table 7-11: PA Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-9
Table 7-12: Troubleshooting BLO Calibration Failure . . . . . . . . . . . . . . . . . . .
7-10
Table 7-13: Troubleshooting Calibration Audit Failure . . . . . . . . . . . . . . . . . . .
7-11
Table 7-14: Correcting E7495A/B Test Set Communication Failure . . . . . . . . .
7-12
Table 7-15: Troubleshooting Forward Link Failure (BTS Passed

Reduced ATP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-12
SEP 2009
SEP 2009
Table 7-16: Troubleshooting TX Mask Measurement Failure . . . . . . . . . . . . . .
7-13
Table 7-17: Troubleshooting Rho and Pilot Time Offset

Measurement Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-13
Table 7-18: Troubleshooting Code Domain Power and Noise Floor

Measurement Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-13
Table 7-19: Troubleshooting Carrier Measurement Failure . . . . . . . . . . . . . . . .
7-14
Table 7-20: Troubleshooting Carrier Measurement Failure . . . . . . . . . . . . . . . .
7-14
Table 7-21: CD Power/Noise Floor Test Failure Workaround for

Agilent E7495A/B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-15
Table 7-22: Troubleshooting Multi-FER Failure . . . . . . . . . . . . . . . . . . . . . . . .
7-16
Table 7-23: No GLI Control via LMF (all GLIs) . . . . . . . . . . . . . . . . . . . . . . . .
7-21
Table 7-24: No GLI Control through Span Line Connection (Both GLIs) . . . .
7-21
Table 7-25: MGLI Control Good No Control over Colocated GLI . . . . . . .
7-21
Table 7-26: MGLI Control Good No Control over AMR . . . . . . . . . . . . . . . .
7-22
Table 7-27: MGLI Control Good No Control over Colocated GLIs . . . . . . .
7-22
Table 7-28: BBX Control Good No (or Missing) Span Line Traffic . . . . . . . .
7-22
Table 7-29: No MCC1X/MCC24E/MCC8E Channel Elements . . . . . . . . . . .
7-23
Table 7-30: No DC Input Voltage to Power Supply Module . . . . . . . . . . . . . . .
7-23
Table 7-31: No DC Input Voltage to any CCCP Shelf Module . . . . . . . . . . . .
7-24
Table 7-32: No DC Input Voltage to any CCCP Shelf Module . . . . . . . . . . . .
7-24
Table 7-33: RFDS Fault Isolation All tests fail . . . . . . . . . . . . . . . . . . . . . . . .
7-25
Table 7-34: RFDS Fault Isolation All RX and TX paths fail . . . . . . . . . . . . .
7-25
Table 7-35: RFDS Fault Isolation All tests fail on single antenna path . . . . .
7-26
Table 7-36: Troubleshoot Control Link Failure . . . . . . . . . . . . . . . . . . . . . . . . .
7-27
Table 7-37: Set BTS Span Parameter Configuration . . . . . . . . . . . . . . . . . . . . .
7-30
Table 7-38: Setting GLI3 Backhaul Type to Satellite and Correct

Timeout Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-36
Table 7-39: GLI3 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-46
Table A-1: Verification of Test Equipment Used . . . . . . . . . . . . . . . . . . . . . . . .
A-1
Table A-2: Site Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-2
Table A-3: Preliminary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-3
Table A3a: Prepower Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-4
Table A3b: Prepower Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-5
Table A-4: GPS Receiver Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-6
Table A-5: LFR Receiver Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-7
Table A-6: Power Amplifier IM Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-8
Table A-7: TX BLO Calibration (3Sector: 1Carrier, 2and 4Carrier

Nonadjacent Channels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-9
Table A-8: TX Bay Level Offset Calibration (3Sector: 2Carrier

Adjacent Channels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-11
xv
List of Tables
xvi
continued
Table A-9: TX Bay Level Offset Calibration (3Sector: 3 or 4Carrier

Adjacent Channels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-12
Table A-10: TX BLO Calibration (6Sector: 1Carrier, 2Carrier

Nonadjacent Channels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-14
Table A-11: TX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-16
Table A-12: RX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-16
Table A-13: CDI Alarm Input Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-17
Table B-1: PnMaskI and PnMaskQ Values for PilotPn . . . . . . . . . . . . . . . . . . .
B-3
Table C-1: SC 4812ET BTS Optimization and ATP Test Matrix . . . . . . . . . . .
C-2
Table D-1: BBX Gain Set Point vs. Actual BTS Output (in dBm) . . . . . . . . . .
D-1
Table E-1: 1900 MHz TX and RX Frequency vs. Channel . . . . . . . . . . . . . . . .
E-3
Table E-2: 800 MHz TX and RX Frequency vs. Channel . . . . . . . . . . . . . . . . .
E-6
Table F-1: Set IP Address on Agilent E7495 test set . . . . . . . . . . . . . . . . . . . . .
F-2
Table F-2: E7495 Power Sensor Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-3
Table F-3: Verify and Set/Change Advantest R3267 GPIB Address . . . . . . . . .
F-5
Table F-4: Verify and Set/Change Advantest R3465 Communications Test Set
GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-7
Table F-5: Verify and Set/Change Agilent 8935 Series E6380 Test Set
GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-9
Table F-6: Verify and Set/Change Agilent E4406A Transmitter Tester

GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-11
Table F-7: Verify and Set/Change Agilent E4418 Power Meter

GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-13
Table F-8: Verify and Change Agilent E4438C Signal Generator

GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-15
Table F-9: Verify and Set/Change Gigatronics 8541C Power Meter

GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-17
Table F-10: Agilent E4406A Selfalignment (Calibration) . . . . . . . . . . . . . . . .
F-22
Table F-11: Calibrate Gigatronics 8542 Power Meter . . . . . . . . . . . . . . . . . . . .
F-23
Table F-12: Procedure for Calibrating Test Cable Setup Using

Advantest R3465 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-24
Table G-1: Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G-1
Table H-1: SC4812ET RF Cabinet InterConnect Cables . . . . . . . . . . . . . . . . .
H-1
Table H-2: SC 4812ET Series 3-Sector Duplexed Directional Coupler to RFDS

Cabling Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-23
Table H-3: SC 4812ET Series 6-Sector Duplexed Directional Coupler to RFDS

Cabling Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-24
Table H-4: PinOut for 50Pair Punchblock . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-28
Table I-1: Agilent E4406A Power Delta Calibration Procedure . . . . . . . . . . . .
I-3
Table I-2: Advantest R3267 Power Delta Calibration Procedure . . . . . . . . . . . .
I-6
Table I-3: Agilent 8935 Power Delta Calibration Procedure . . . . . . . . . . . . . . .
I-9
SEP 2009
SEP 2009
Table I-4: Advantest Power Delta Calibration Procedure . . . . . . . . . . . . . . . . . .
I-11
Table I-5: InService Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I-18
Table J-1: Optimizing the RX (Main) section of the Companion Frame . . . . . .
J-1
Table J-2: Optimizing the RX (Diversity) on a Single Frame . . . . . . . . . . . . . .
J-1
Table J-3: Optimizing the RX (Diversity) on a Two Frame Companion Site . .
J-2
Table K-1: Establish HyperTerminal Connection . . . . . . . . . . . . . . . . . . . . . . . .
K-3
Table K-2: Establishing BTS Router Serial Communication . . . . . . . . . . . . . . .
K-6
Table K-3: BTS Router Canned Configuration File FTP Transfer from
the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-9
Table K-4: Configure Computer NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-19
Table K-5: Create a Default TFTP Directory . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-21
Table K-6: Connecting the LMF Computer to the BTS Router for TFTP
File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-23
Table K-7: BTS Router Powerup and Initial Ethernet Configuration . . . . . . .
K-23
Table K-8: Transfer Canned Configuration Files to the BTS Router Using a
TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-27
Table K-9: Using a TFTP Server Application for Upgrading/Replacing Loaded

IOS Version and Verifying File Sequence Position . . . . . . . . . . . . . . . . . . . . . .
K-37
Table K-10: Verify and Upgrade/Replace Installed ROMmon Version Using a

TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-49
Table K-11: Simple Recovery from BTS Router ROMmon Boot . . . . . . . . . . .
K-58
Table K-12: Extended Recovery from BTS Router ROMmon Boot . . . . . . . . .
K-67
Table K-13: Entering or Changing BTS Router FE Interface IP Addresses and

Operating Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-72
Table K-14: Advanced Tab Property List Box Connection

Settings Original . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-84
Table K-15: Advanced Tab Property List Box Connection Settings

for BTS Router Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-84
Table K-16: External BTS Router Flash Memory Card Removal . . . . . . . . . . .
K-86
Table K-17: External BTS Router Flash Memory Card Installation . . . . . . . . .
K-87
Table L-1: Parts Required to Fabricate MMI Cable . . . . . . . . . . . . . . . . . . . . . .
L-1
Table L-2: Fabricated MMI Cable Wire Run List . . . . . . . . . . . . . . . . . . . . . . .
L-2
xvii
Revision History
Version Information
The following table lists the manual version, date of version, and
remarks on the version.
Issue
Date of Issue
SEP 2009
Remarks
Release for General Availability (GA).
Manual Number
The following Service Requests are resolved in this document.
Service
Request
CMBP
Number
NA
NA
Remarks
Initial release
Cellular Manual Revision

Information
The following Change Notices (CN) are incorporated in this document.
CN Date
CN
NA
NA
xviii
Title
NA
SEP 2009
General information
Scope of manual
This manual is intended for use by cellular telephone system
craftspersons in the day-to-day operation of Motorola cellular system
equipment and ancillary devices.
This manual is not intended to replace the system and equipment
training offered by Motorola, although it can be used to supplement or
enhance the knowledge gained through such training.
NOTE
If this document 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 are supplied automatically by Motorola and
posted on the Motorola customer website.
Cross references
The following special paragraphs are used in this manual to point out
information that must be read. This information may be set-off from the
surrounding text, but is always preceded by a bold title in capital letters.
The four categories of these special paragraphs are:
SEP 2009
xix
Foreword continued
Text conventions
The following conventions are used in the Motorola cellular

infrastructure documents to represent keyboard input text, screen output
text and special key sequences.
Input
CMMD required required [optional] [optional]
Output
CMMD required required [optional] [optional]
Special key sequences
xx
CRTLc or CTRL+C
Press the Ctrl and C keys at the

same time.
CTRLSHIFTc or
CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys

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

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

keys at the same time.
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
SEP 2009
Contacting Motorola
Motorola appreciates feedback from the users of our information.

24-hour support service
If you have problems regarding the operation of your equipment, please
contact the Customer Network Resolution Center (CNRC) for immediate
assistance. The 24 hour telephone numbers are listed at
https://mynetworksupport.motorola.com. Select Customer Network
Resolution Center contact information, from the menu located to the
left of the Login box.
For additional CNRC contact information, contact your Motorola
account representative.
Contact us
Send questions and comments regarding user documentation to the email
address below:
cdma.documentation@motorola.com
Reporting manual errors
To report a documentation error, call the CNRC (Customer Network
Resolution Center) and provide the following information to enable
CNRC to open an SR (Service Request):
the document type
the manual title, part number, and revision character
the page number(s) with the error
a detailed description of the error and if possible the proposed solution
Motorola appreciates feedback from the users of our manuals.
SEP 2009
xxi
Security Advice
Motorola systems and equipment provide configurable security

parameters to be set by the operator based on their particular operating
environment. Motorola recommends setting and using these parameters
following industry recognized security practices. Security aspects to be
considered are protecting the confidentiality, integrity, and availability of
information and assets. Assets include the ability to communicate,
information about the nature of the communications, and information
about the parties involved.
In certain instances Motorola makes specific recommendations regarding
security practices, however the implementation of these
recommendations and final responsibility for the security of the system
lies with the operator of the system.
Please contact the Customer Network Resolution Center (CNRC) for
https://mynetworksupport.motorola.com/. Select Customer Network
Resolution Center contact information, from the menu located to the
left of the Login box. Alternatively if you do not have access to CNRC
or the internet, contact the Local Motorola Office.
xxii
SEP 2009
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this
document and in all documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous

situations. Warnings are used to alert the reader to possible hazards that
could cause loss of life or physical injury. A warning has the following
format:
WARNING
Warning text and consequence for not following the
instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of

damage to systems, software, or individual items of equipment within a
system. However, this damage presents no danger to personnel. A
caution has the following format:
CAUTION
Caution text and consequence for not following the
instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or

provides additional information to help the reader understand a topic or
concept. A note has the following format:
NOTE
Note text.
SEP 2009
xxiii
Safety
Remember! . . . Safety
depends on you!!
The following general safety precautions must be observed during all
phases of operation, service, and repair of the equipment described in
this manual. Failure to comply with these precautions or with specific
warnings elsewhere in this manual violates safety standards of design,
manufacture, and intended use of the equipment. Motorola, Inc. assumes
no liability for the customers failure to comply with these requirements.
The safety precautions listed below represent warnings of certain dangers
of which we are aware. You, as the user of this product, should follow
these warnings and all other safety precautions necessary for the safe
operation of the equipment in your operating environment.
S not remove equipment covers. Only Factory Authorized Service
Personnel or other qualified maintenance personnel may remove

equipment covers for internal subassembly, or component
replacement, or any internal adjustment.
NOTE
Refer to Grounding Guideline for Cellular Radio
Installations 68P81150E62.
S not replace components with power cable connected. Under certain
conditions, dangerous voltages may exist even with the power cable
removed.
S always disconnect power and discharge circuits before touching them.

S Portions of Motorola equipment may be damaged from exposure to
electrostatic discharge. Use precautions to prevent damage
Use caution when exposing or

handling the CRT
Breakage of the CathodeRay Tube (CRT) causes a high-velocity
scattering of glass fragments (implosion). To prevent CRT implosion,
avoid rough handling or jarring of the equipment. The CRT should be
handled only by qualified maintenance personnel, using approved safety
mask and gloves.
S ANSI IEEE C95.11991, IEEE Standard for Safety Levels with
Respect to Human Exposure to Radio Frequency Electromagnetic

Fields, 3 kHz to 300 GHz.
S Council recommendation of 12 July 1999 on the limitation of
exposure of the general public to electromagnetic fields (0 Hz to 300

GHz) (1999/519/EC) and respective national regulations.
S Directive 2004/40/EC of the European Parliament and of the Council

of 29 April 2004 on the minimum health and safety requirements
regarding the exposure of workers to the risks arising from physical
agents (electromagnetic fields) (18th individual Directive within the
meaning of Article 16(1) of Directive 89/391/EEC).
xxiv
SEP 2009
Caring for the Environment
Please do not dispose of Motorola Networks equipment in landfill sites.

Please contact the Customer Network Resolution Center (CNRC) for
https://mynetworksupport.motorola.com/.
Select Customer Network Resolution Center contact information,
from the menu located to the left of the Login box. Alternatively if you
do not have access to CNRC or the internet, contact the Local Motorola
Office.
Disposal of Motorola Networks
equipment in EU countries
In the EU, Motorola Networks in conjunction with a recycling partner

will ensure that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of Motorola equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and
Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU,
Motorola in conjunction with a recycling partner ensures that equipment
is collected and recycled according to the requirements of EU
environmental law.
Disposal of surplus packaging
European Parliament and Council Directive 94/62/EC Packaging and
Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the
individual recipients responsibility to ensure that packaging materials
are collected and recycled according to the requirements of EU
environmental law.
Disposal of Motorola Networks
equipment in nonEU countries
In nonEU countries, dispose of Motorola Networks equipment in

accordance with national and regional regulations.
SEP 2009
xxv
CMM labeling and disclosure table
The Peoples Republic of China require that our products comply with
China Management Methods (CMM) environmental regulations. (China
Management Methods refers to the regulation Management Methods for
Controlling Pollution by Electronic Information Products.) Two items
are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
S Logo 1 means the product contains no substances in excess of the
maximum concentration value for materials identified in the China

Management Methods regulation.
S Logo 2 means that the product may contain substances in excess of the
maximum concentration value for materials identified in the China
Management Methods regulation, and has an Environmental Friendly
Use Period (EFUP) in years, fifty years in the example shown.
The Environmental Friendly Use Period (EFUP) is the period (in years)
during which the Toxic and Hazardous Substances (T&HS) contained in
the Electronic Information Product (EIP) will not leak or mutate causing
environmental pollution, or bodily injury from the use of the EIP. The
EFUP indicated by the Logo 2 label applies to a product and all its parts.
Certain fieldreplaceable parts, such as battery modules, can have a
different EFUP and are marked separately.
The Disclosure table is intended only to communicate compliance with
China requirements. It is not intended to communicate compliance with
EU RoHS or any other environmental requirements.
xxvi
SEP 2009
Motorola document set
The Motorola document sets provide the information needed to operate,

install and maintain the Motorola equipment.
Obtaining manuals
To view, download, or order manuals (original or revised), visit the
Motorola Lifecycles Customer web page at
https://mynetworksupport.motorola.com, or contact your Motorola
account representative.
If Motorola changes the content of a manual after the original printing
date, Motorola publishes a new version with the same part number but a
different revision character.
If Motorola changes the content of a document after the original printing
date, Motorola publishes a new version with the same part number but a
different revision character.
Manual banner definitions
A banner (oversized text on the bottom of the page, for example,
PRELIMINARY) indicates that some information contained in the
manual is not yet approved for general customer use.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain

elements in the network is encrypted. In order to comply with the export
and import requirements of particular countries, this encryption occurs at
different levels as individually standardized, or may not be present at all
in some parts of the network in which it is normally implemented. The
document set, of which this document 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.
SEP 2009
xxvii
Third Party computer software and trademarks
Computer Software
The Motorola and 3rd Party supplied Software (SW) products described in this instruction manual may include copyrighted Motorola
and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including
the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola or
other 3rd Party supplied SW computer programs contained in the Motorola products described in this instruction manual may not be
copied (reverse engineered) or reproduced in any manner without the express written permission of Motorola or the 3rd Party SW
supplier. 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 or other 3rd Party supplied SW, except for the
normal nonexclusive, royalty free license to use that arises by operation of law in the sale of a product.
Vendor
Copyright
Wind River Systems, Inc.
Copyright 19842007 All rights reserved.
Apache Software Foundation *
Copyright 19992007 All rights reserved.
* Publicly Available Software
Trademarks
Javat Technology and/or J2MEt: Java and all other Javabased marks
are trademarks or registered trademarks of Sun Microsystems, Inc. in the
U.S. and other countries.
UNIXR: UNIX is a registered trademark of The Open Group in the
United States and other countries.
3ComR and OfficeConnectR: 3Com and OfficeConnect are registered
trademarks of the 3Com Corporation.
MicrosoftR, WindowsR. Windows MeR, and Windows XPt:
Microsoft, Windows and Windows Me are registered trademarks of
Microsoft Corporation; Windows XP is a trademark of Microsoft
Corporation.
CiscoR, Cisco IOSR, and IOSR: Cisco, Cisco IOS, and IOS are
registered trademarks of Cisco Systems, Inc. and/or its affiliates in the
U.S. and certain other countries.
PC Cardt: PC Card is a trademark of the Personal Computer Memory
Card International Association (PCMCIA)
Anritsut is a trademeark of the Anritsu Company.
xxviii
SEP 2009
FCC Requirements
Content
This section presents Federal Communications Commission (FCC)

Rules Parts 15 and 68 requirements and compliance information for the
SCt4812 series Radio Frequency Base Transceiver Subsystems (BTS).
FCC Part 15 Requirements
Part 15.19a(3) INFORMATION TO USER

NOTE
This device complies with Part 15 of the FCC Rules.
Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received,
including interference that may cause undesired operation.
Part 15.21 INFORMATION TO USER
Changes or modifications that change the FCC type approved
configuration of the equipment could void the users authority to operate
the equipment.
SEP 2009
xxix
FCC Requirements continued

15.105(b) INFORMATION TO USER
NOTE
This equipment has been tested and found to comply with
the limits for a Class B digital device, pursuant to Part 15
of the FCC Rules. These limits are designed to provide
reasonable protection against harmful interference in a
residential installation. This equipment generates, uses and
can radiate radio frequency energy and, if not installed and
used in accordance with the instructions, may cause
harmful interference to radio communications. However,
there is no guarantee that interference will not occur in a
particular installation. If this equipment does cause harmful
interference to radio or television reception, which can be
determined by turning the equipment OFF and ON, the
user is encouraged to try to correct the interference by one
or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician
for help.
FCC Part 68 Requirements
This equipment complies with Part 68 of the FCC rules and the
requirements adopted by the Administrative Council for Terminal
Attachments (ACTA). The product identifier in the format
US: AAAAEQ##TXXXX is located on a label. If requested, this
number must be provided to the telephone company. The label that
contains the product identifier is visible when the GLI and MCCDO
boards are removed from the cage.
FCC Part 68 Registered Devices
Item
Description
Group Line Interface (GLI2)

*See Note
US: IHEUSA32769XDE
Group Line Interface (GLI3)

*See Note
US: IHEXDNANGLI31X
Cisco Model 190027 Router
US: 5B1DDNDN0006
ADC KENTROX Model 537
US: F81USA31217DEN
table continued on next page
xxx
SEP 2009
FCC Part 68 Registered Devices

Item
MultiChannel CDMA Data
Only (MCCDO)
*See Note
Description
US: 83YXDNANMCCDO
NOTE
The BTS equipment may be equipped with either the GLI2, <US:
IHEUSA32769XDE>, or the GLI3,
< US: IHEXDNANGLI31X>, and the MCCDO, <US:
83YXDNANMCCDO>, and may be used in conjunction with one or
both of the listed registered CSU devices, or another registered CSU
device not listed above.
A plug and jack used to connect this equipment to the premises wiring
and telephone network must comply with the applicable FCC Part 68
rules and requirements adopted by the ACTA. A compliant telephone
cord and modular plug is provided with this product. It is designed to be
connected to a compatible modular jack that is also compliant. See
installation instructions for details.
The Ringer Equivalence Number (REN) is used to determine the number
of devices that may be connected to a telephone line. Excessive RENs on
a telephone line may result in the devices not ringing in response to an
incoming call. In most but not all areas, the sum of RENs should not
exceed five (5.0). To be certain of the number of devices that may be
connected to a line, as determined by the total RENs, contact the local
telephone company. For products approved after July 23, 2001, the REN
for this product is part of the product identifier that has the format
US:AAAEQ##TXXXX. The digits represented by ## are the REN
without a decimal point (for example, 03 is a REN of 0.3). For earlier
products, the REN is separately shown on the label.
SEP 2009
xxxi

The telephone company may make changes in its facilities, equipment,
operations, or procedures that could affect the operation of the users T1.
If this happens, the telephone company will provide advance notice to
users so that they can modify their equipment as required to maintain
uninterrupted service.
If this equipment causes harm to the telephone network, the telephone
company will notify users in advance that temporary discontinuance of
service may be required. If advance notice is not practical, the telephone
company will notify users as soon as possible. Also, users will be
advised of their right to file a complaint with the FCC if the users
believe it is necessary.
If trouble is experienced operating this equipment with the T1, please
contact the Customer Network Resolution Center (CNRC) for repair
and/or warranty information. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network
Resolution Center contact information.
If the trouble is causing harm to the telephone network, the telephone
company may request users to disconnect the equipment from the
network until the problem is solved. Users should not attempt to repair
this equipment themselves. This equipment contains no customer or
userserviceable parts.
Changes or modifications not expressly approved by Motorola could
void the users authority to operate this equipment.
xxxii
SEP 2009
Chapter 1: Introduction
Table of Contents
SEP 2009
Scope, Assumptions, and Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Circuit and Packet BTS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intended Reader Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1
1-1
1-1
1-1
1-2
1-2
Content Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Publication Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
1-3
Purpose of Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why Optimize? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Is Calibration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Happens During Calibration? . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4
1-4
1-4
1-4
When to Perform BTS RF Calibration and Acceptance Testing . . . . . . . . . . . .

New Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
After Adding MCC Card(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Periodic Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Repaired Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-5
1-5
1-6
1-6
1-7
1-7
1-7
General Test Equipment Selection, Calibration, and

Operation Requirememnts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Equipment Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Warmup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8
1-8
1-8
1-8
1-8
Required Test Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LMF Computer and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications System Analyzer CDMA/analog . . . . . . . . . . . . . . . .
Optional Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-9
1-9
1-9
1-11
1-13
Required Documents and Related Publications . . . . . . . . . . . . . . . . . . . . . . . . .

Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-15
1-15
1-16
Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standard and Nonstandard Terms and Abbreviations . . . . . . . . . . . . .
1-17
1-17
Table of Contents
continued
BTS Equipment Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RF Cabinet configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal RF Cabinet components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal RF Cabinet Assemblies and FRUs . . . . . . . . . . . . . . . . . . . . . .
Power Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal Power Cabinet FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCCP Cage Configuration and 1X Devices . . . . . . . . . . . . . . . . . . . .
BBX Interchangeability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-22
1-22
1-23
1-24
1-25
1-31
1-32
1-34
1-34
Sector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-35
1-35
SEP 2009

Scope
This document provides information pertaining to the optimization and

acceptance tests of the Motorola 1X SC4812ET CLPA Base
Transceiver Subsystem.
The following models, equipped with either Trunked Linear Power
Amplifiers (TLPA) or C Linear Power Amplifiers (CLPA), as
indicated, and their associated internal and external interfaces are
covered:
S 800 MHz Models (equipped with TLPAs):
ST1198CA/ST1296BA
ST1199CA
S 1900 MHz Models (equipped with TLPAs or CLPAs):
ST1152CA/ST1154AA
ST1153AA/ST1156AA
NOTE
Throughout the remainder of this publication, TLPA
amplifiers will be referred to as LPA amplifiers. Where
important, distinctions are made between between LPAs
and CLPAs, specific abbreviations will be used.
Circuit and Packet BTS
Support
Information in this publication supports optimization and calibration of

cdma2000 1X packet BTS sites operating with Motorola Software
Release 2.22.0.x and later.
The cdma2000 1X (1X) packet BTS has a packet backhaul network
interface provided through BTS routers operating with a
Thirdgeneration Group Line Interface (GLI3) card that can support
voice (IS-95A/B, 1X) and data (IS-95B, 1X).
This BTS equipment is configured with all 1X cards (BBX1X and
MCC1X). This configuration is compliant with all applicable 1X
specifications. It provides the forward link and reverse link RF functions
to support Second Generation (2G) features and Third Generation (3G)
1X features; that is, high capacity voice and high bitrate data.
Assumptions
This document assumes that the BTS frames and cabling have been
installed according to the following manuals:
S SC Product Family Frame Mounting Guide; 68P09226A18, which
covers the physical bolt down of all SCseries equipment frames
S 1X SC4812ET BTS Hardware Installation, which covers BTSspecific
cabling configurations for packet backhaul and the addition of carriers
to the BTS
SEP 2009
1-1
continued
Audience
Motorola has attempted to incorporate into this document the many

customer suggestions and comments received since the introduction of
the SC product line. Additionally, the attempt has been made to ensure
that the scope of the document supports both the novice and expert site
technician and engineer with the information required to successfully
perform the task at hand. If, in some areas, the manual seems to cover a
subject with too much or not enough detail, please keep this in mind.
Intended Reader Profile
The information in this manual set is intended for use by cellular

communications personnel in the initial installation and configuration, as
well as the day-to-day operation and maintenance of a BTS.
The user of this information must have a general understanding of
telephony, as used in the operation of the Public Switched Telephone
Network (PSTN), and must be familiar with these concepts as they are
applied in the cellular and mobile/portable radiotelephone maintenance
environment.
The user also must have a working knowledge of the Microsoftr
Windowsr 2000 or Windows XP operating system.
1-2
SEP 2009
Content Summary
Content Summary
Publication Composition
This document covers the following major areas:
S Introduction, consisting of preliminary background information (such

as component and subassembly locations and frame layouts) to be
considered by the Cell Site Field Engineer (CFE) before optimization
or tests are performed.
S Preliminary Operations, consisting of cabinet power up and power

down procedures.
S Optimization/calibration, covering topics of Local Maintenance
Facility (LMF) connection to the BTS equipment, Global Positioning

System (GPS) Verification, test equipment setup, downloading all
BTS processor boards, RF path verification, Bay Level Offset (BLO)
calibration and calibration audit, and Radio Frequency Diagnostic
System (RFDS) calibration.
S Acceptance Test Procedures (ATPs), consisting of ATP tests executed

by the LMF and used to verify all major transmit (TX) and
receive (RX) performance characteristics on all BTS equipment.
Includes generating an ATP report.
S Packet BTS Transport Configuration Procedures: configuring the BTS

GLI3 card to interface with the various available transport
technologies/techniques and implementing available file transport
protocols.
S Preparing to leave the site, presents instructions on how to properly
exit customer site, ensure that all equipment is operating properly, and
all work is complete according to Motorola guidelines.
S Basic troubleshooting, consisting of procedures for installation,
calibration, transmit and receive tests, backplane problems, GPS

failures, and module connectors.
S Appendices, including data sheets for CFEs recording at the site,
Pseudorandom Noise (PN) Offset information, Optimization/ATP

matrix, BBX Gain set point vs BTS output, CDMA operating
frequency programming information, manual test setup information,
downloading ROM and RAM code, GPIB addresses, RF cabinet
interconnect cable information, Power Delta calibration procedures,
and Companion Frame optimization/ATP.
SEP 2009
1-3
Purpose of Optimization
Purpose of Optimization
Why Optimize?
Proper optimization, also known as calibration, ensures that:
S Accurate downlink RF power levels are transmitted from the site.

S Accurate uplink signal strength determinations are made by the site.
What Is Calibration?
Calibration compensates for the site-specific cabling and normal

equipment variations. Site calibration guarantees that the combined
losses of the cables and the gain/loss characteristics and built-in
tolerances of each BTS frame do not accumulate and cause improper site
operation.
What Happens During
Calibration?
Overview During calibration, the accumulated path loss or gain is first

determined for each RF transmit path in the BTS. These transmit path
loss or gain values are then stored in a database along with RF receive
path default values.
RF path defintions For definitions of the BTS transmit (TX) and
receive (RX) paths, see What is Bay Level Offset Calibration? in the
Bay Level Offset Calibration section of Chapter 3.
NOTE
In this publication, all models of the Broad Band
Transceiver (BBX) board usable in this BTS, are
generically identified as BBX, unless otherwise specified.
Also, all models of the MultiChannel CDMA (MCC)
cards usable in this BTS, are generically identified as
MCC, unless otherwise specified.
RF paths and transceiver calibration Twelve of the BBX boards in

each CombinedCDMA Channel Processor (CCCP) shelf are
optimized to specific RX and TX antenna connectors. The last BBX
board provides redundancy for BBX boards 1 through 12, and is
optimized to all antenna connectors. A single calibration value is
generated for each complete path. This eliminates the accumulation of
error that would occur from individually measuring and summing the
gain and loss of each element in the path.
Using RF path gain/loss values BTS equipment factors in the derived
calibration values internally to adjust transceiver power levels, leaving
only sitespecific antenna feedline loss and antenna gain characteristics
to be factored in by the CFE when determining required site Effective
Radiated Power (ERP) output power levels.
1-4
SEP 2009
When to Perform BTS RF Calibration and Acceptance Testing

This section summarizes Motorolarecommended BTS transmit RF path
calibration, forward and reverse RF path integrity and operation
verification, and other acceptance testing. Specific calibration and testing
recommendations are included for periodic maintenance, troubleshooting
and for use after the following listed installation/upgrade activities:
S New BTS and expansion frame installation

S BTS conversion from 3 to 6sector operation
S Carrier additions
S MultiChannel CDMA (MCC) card additions
S Site repairs
New Installations
Objectives
1. Calibrate and verify forward (transmit) RF paths
2. Verify reverse (receive) RF path performance
3. Verify MCC operation for a new BTS installation, expansion frame
installation, or conversion from 3 to 6sector operation
Recommended Actions
Perform the following actions after initial powerup, downloading
operating code, and verifying GPS operation:
1. Calibrate all transmit RF paths and download derived calibration
data.
2. Audit TX calibration of all transmit RF paths to verify BTS
calibration is within tolerance.
3. After testing alarm reporting and redundancy performance, perform
the code domain power test on all equipped sector carriers, making
sure that each equipped MCC is exercised at least once.
4. Perform Frame Error Rate (FER) test, or, for 1xEVDOequipped
frames, Packet Erase Rate (PER) test on both the main and diversity
RX paths for all sector carriers using at least one MCC.
NOTE
It is not necessary to test all equipped MCCs during
FER/PER testing.
5. Perform any other acceptance tests required to demonstrate
compliance with applicable regulatory requirements.
SEP 2009
1-5
continued
Site Expansion
Objectives
1. Calibrate and verify forward RF paths
2. Verify reverse RF path performance for the newly added sector
carriers.
Recommended Actions
Perform the following actions after expansion of a site with additional
carriers (carrier add):
NOTE
If carriers are added in conjunction with adding MCCs,
testing of both should be combined. It is not necessary to
perform separate MCC testing in addition to testing newly
added sector carriers.
1. Perform TX calibration and audit on each new sector carrier.
2. Perform the code domain power test for all new sector carriers,
making sure that each applicable MCC is exercised at least once.
3. Perform FER/PER test on both the main and diversity RX paths for
each new sector carrier using at least one MCC.
NOTE
It is not necessary to test all equipped MCCs during
FER/PER testing.
After Adding MCC Card(s)
Objective
Verify operation of new MCC cards.
Recommended Actions
Perform the following after adding one or more MCC cards to a BTS:
NOTE
If carriers are added in conjunction with adding MCC
cards, testing of both should be combined. It is not
necessary to perform separate MCC testing in addition to
testing newly added sector carriers.
1. Perform the code domain power test for at least one sector carrier,
making sure that each new MCC is exercised at least once.
1-6
SEP 2009
continued
2. Perform FER/PER test for at least one sector carrier on either the
main or diversity RX path using each new MCC.
Periodic Maintenance
Objectives
1. Verify transmit RF path calibration, and recalibrate as required to
compensate for equipment performance changes.
2. Validate reverse path performance.
NOTE
Reverse path validation is not always necessary, but may
be desired as a result of observed site operational
performance changes.
Recommended Actions
Perform the following tests on a yearly basis to revalidate the TX and
RX paths of the BTS:
1. Perform TX calibration and audit on each sector carrier.
2. Perform FER/PER test for each sector carrier.
Troubleshooting
Objective
Support fault isolation or identifying source of degraded performance.
Recommended Actions
Use any or all of the following tests during a troubleshooting visit to
determine the nature of a BTS problem:
S
S
S
S
S
S
TX calibration and audit on the affected sector carrier(s)

Code domain power for the affected sector carrier(s)
TX mask for the affected sector carrier(s)
Pilot time offset for the affected sector carrier(s)
Rho for the affected sector carrier(s)
FER/PER for the affected sector carrier(s)
Repaired Sites
Refer to Appendix C for a detailed FRU Optimization/ATP Test Matrix

outlining the minimum tests that must be performed any time a BTS RF
subassembly or cable associated with an RF path is replaced.
SEP 2009
1-7
General Test Equipment Selection, Calibration, and Operation

Requirememnts
General Test Equipment Selection, Calibration, and Operation
Requirememnts
Policy
General Requirements To ensure consistent, reliable, and repeatable

BTS calibration results, test equipment and software meeting the
following technical criteria should be used for BTS calibration.
Test equipment substitution Test equipment can be substituted with
other test equipment models, but substitute items must meet the same
technical specifications. All test equipment models selected for use in
BTS calibration and acceptance testing must be supported by the LMF.
Measurement variances and test equipment substitution It is the
responsibility of the customer to account for any measurement variances
and/or additional losses/inaccuracies which can be introduced as a
result of test equipment item substitutions. Before beginning BTS
calibration or troubleshooting, make sure that the test equipment needed
is onhand and operating properly.
Test Equipment Calibration
Optimum system performance and capacity depend on regular support

equipment service and calibration prior to its use for BTS calibration.
Follow the original equipment manufacturer (OEM) recommended
maintenance and calibration schedules closely.
Test Cable Calibration
Onsite cable calibration Test cables can make critical differences in

calibration accuracy. Motorola recommends that cable calibration be run
at every BTS with the complete test equipment set. This method
compensates for test cable insertion loss within the test equipment set
itself. No other allowance for test cable insertion loss needs to be made
during the performance of BTS calibration or acceptance tests.
Inshop cable characterization Another method to account for cable
loss is by entering it into the LMF prior to the calibration procedure.
This method requires accurate test cable characterization using shop test
equipment. Characterized cables should be tagged with the
characterization information, and the measured losses entered into the
LMF before performing BTS calibration.
Equipment Warmup
After arriving at the a site, the test equipment should be plugged in and
turned on to allow warm up and stabilization for as long as possible. The
following test equipment items must be warmed up for a minimum of 60
minutes prior to use for BTS calibration.
S Communications Test Set
S Power Meter
1-8
SEP 2009
Required Test Equipment and Software

Overview
Test equipment and software described in this section is required for the
calibration and acceptance testing procedures. Common tools such as
screwdrivers and frame keys are also needed. Read the operators manual
for all test equipment items to understand their individual operation
before using them for calibration or acceptance testing.
LMF Computer and Software
LMF Hardware Requirements

An LMF computer platform that meets the following requirements (or
better) is recommended:
S Laptop computer
S Windows 2000 or Windows XP operating system
S 533 MHz processor (1 GHz or higher recommended)
S 4 GB internal hard disk drive
S Color display with 1024 x 768 resolution
S Memory requirements:
Minimum required RAM: 256 MB
Recommended RAM: 512 MB
S CD/DVD drive
S 3 1/2 inch floppy drive (may not be required if equipped with
CD/DVD writer drive)
S Serial port (COM 1)
S Serial port (COM 2) for SC 6XX BTS and serial versions of SC 3XX
BTS
S Builtin Ethernet Network Interface Card (NIC) (recommended) or
PCMCIA Ethernet interface card (not recommended)
LMF Computer to BTS Interface Device
One or both of the following may be requred to connect the LMF
computer platform to the BTS 10Base2 LAN:
Ethernet LAN hub or switch Ethernet Hub or Switch (recommended
with 10Base2 port, for example 3ComR OfficeConnectR Ethernet Hub
4C)
10Base2/10BaseT converter 10Base2/10BaseT Converter (only
needed if hub/switch does not have 10Base2 port, for example Unicom
ETP20038T)
NOTE
Xircom Model PE310B2 or equivalent can also be used to
interface the LMF Ethernet connection to the frame.
SEP 2009
1-9
continued
LMF Software
The Local Maintenance Facility (LMF) application program is a
graphical user interface (GUI)based software tool. This product is
specifically designed to provide cellular communications field personnel
with the capability to support the following CDMA BTS operations:
S Installation
S Maintenance
S Calibration
3CPCCOMBO CBL
S Connects to the 3COM PCMCIA card and eliminates the need for a
10BaseT/10base2 Converter.
RS232 to GPIB Interface
S National Instruments GPIB232CT with Motorola CGDSEDN04X

RS232 serial null modem cable or equivalent; used to interface the
LMF to the test equipment.
S Standard RS232 cable can be used with the following modifications
(see Figure 1-1):

This solution passes only the 3 minimum electrical connections
between the LMF and the General Purpose Information Bus (GPIB)
interface. The control signals are jumpered as enabled on both ends
of the RS232 cable (9pin D). TX and RX signals are crossed as
Null Modem effect. Pin 5 is the ground reference.
Short pins 7 and 8 together, and short pins 1, 4, and 6 together on
each connector.
Figure 1-1: Null Modem Cable Detail

9PIN DFEMALE
GND
RX
TX
RTS
CTS
RSD/DCD
DTR
DSR
5
3
2
7
8
1
4
6
9PIN DFEMALE
ON BOTH CONNECTORS
SHORT PINS 7, 8;
SHORT PINS 1, 4, AND 6
5
2
3
7
8
1
4
6
GND
TX
RX
RTS
CTS
RSD/DCD
DTR
DSR
MMI Interface
Motorola cable part number CGDSMMICABLE219112 or a cable
locally fabricated as described in Appendix L is used to connect the
LMF to the BTS.
1-10
SEP 2009
continued
Communications System
Analyzer CDMA/analog
Table 1-1: CDMA LMF Test Equipment Support Table

Item
Description
Test Capability
Test Sets
Advantest R3465 (with 3561L)
Communications analyzer (with 3561 CDMA

option)
IS95A/B only
Agilent E4406A (with E4438C)
Communications Analyzer with Agilent E4438C

CDMA Signal Generator
IS95A/B and
CDMA 2000 testing
Advantest R3267 Analyzer (with

R3562)
Communications Analyzer with Advantest

R3562 Generator
IS95A/B and
CDMA 2000 testing
Agilent 8935 series E6380A

(formerly HP 8935) with option
200 or R2K
Communications test set
IS95A/B and
CDMA 2000 testing
Agilent E7495A or E7495B
Communications test set
IS95A/B and
CDMA 2000 testing
Anritsut MT8212B
Multifunction base station test set
IS95A/B and
CDMA 2000 testing
Power Meters
Agilent E4418B
Power meter
Gigatronix 8541C
Power meter
SEP 2009
1-11
continued
A combination of test equipment supported by the LMF may also be

used during calibration and testing of the RF communications portion of
BTS equipment when the communications system analyzer does not
perform all of the following functions:
S
S
S
S
S
S
Frequency counter
S
S
S
S
Noise measurement meter
Deviation meter
RF power meter (average and code domain)
RF signal generator (capable of DSAT/CDMA modulation)
Audio signal generator
AC voltmeter (with 600ohm balanced audio input and high
impedance input mode)
CMessage filter
Spectrum analyzer
CDMA code domain analyzer
GPIB Cables
S Hewlett Packard 10833A or equivalent; 1 to 2 meters (3 to 6 feet) long

used to interconnect test equipment and LMF terminal.
Timing Reference Cables
S Two BNC-male to BNC-male RG316 cables; 3.05 m (10 ft.) long.

Used to connect the communications analyzer to the front timing
reference of the CSM cards in the BTS frame.
Digital Multimeter
S Fluke Model 8062A with Y8134 test lead kit or equivalent; used for
precision dc and ac measurements, requiring 41/2 digits.
Directional Coupler
S Narda Model 30445 30 dB (Motorola Part No. 58D09643T01 )
800 MHz coupler terminated with two Narda Model 375BNM loads,
or equivalent.
RF Terminations/Loads
S At least three 100Watt (or larger) nonradiating RF

terminations/loads.
1-12
SEP 2009
continued
Miscellaneous RF Adapters, Loads, etc
S As required to interface test cables and BTS equipment and for
various test set ups. Should include at least two 50 Ohm loads (type
N) for calibration and one RF short, two NType FemaletoFemale
Adapters.
LAN Cables and Adapters
S For connection to the 10Base2 LAN below the CCCP cage: BNCto
BNC 50 Ohm coaxial cable [.91 m (3 ft) maximum] with an FtoF
adapter, used to connect the 10BaseTtocoaxial adapter to the BTS
LAN connector.
S Trompeter Electronics, Inc., ADBJ20E1PL75 or equivalent
BNC (F) to TRB (M) adapter is required if it is necessary to connect

the LMF computer to the LAN external interface triaxial connectors
located in the power entry compartment.
S For connection to power entry compartment 10Base2 LAN connectors

(if necessary): 50 Ohm coaxial cable with two BNC plugs and
sufficient length to reach the operating location for the LMF computer
and/or 10BaseTto10Base2 Ethernet converter or hub
Highimpedance Conductive Wrist Strap
S Motorola Model 4280385A59; used to prevent damage from
Electrostatic Discharge (ESD) when handling or working with

modules.
Test Set Calibration Support Items

The Anritsu MT8212B requires the following additional items to
perform the indicated calibrations:
S For standard OpenShortLoad (OSL) calibration:

Anritsu 22N50 Open/Short, DC to 18 GHz, N(m) connector, 50
ohm
Anritsu SM/PL precision load, DCto4 GHz, 42 dB, N(m)
connector, 50 ohm
S For standard InstaCalt calibration:

Anritsu ICN50 InstaCalt calibration module, 2 MHz to 4 GHz,
N(m) connector, 50 ohm
Optional Equipment
NOTE
Not all optional equipment specified here will be supported
by the LMF in automated tests or when executing various
measure type command line interface (CLI) commands. It
is meant to serve as a list of additional equipment that
might be required during maintenance and troubleshooting
operations.
SEP 2009
1-13
continued
Frequency Counter
S Stanford Research Systems SR620 or equivalent. If direct
measurement of the 3 MHz or 19.6608 MHz references is required.
Spectrum Analyzer
S Spectrum Analyzer (HP8594E with CDMA personality card) or

equivalent; required for manual tests.
Local Area Network (LAN) Tester
S Model NETcat 800 LAN troubleshooter (or equivalent); used to

supplement LAN tests using the ohmmeter.
Span Line (T1/E1) Verification Equipment
S As required for local application

Oscilloscope
S Tektronics Model 2445 or equivalent; for waveform viewing, timing,

and measurements or during general troubleshooting procedure.
2way Splitter
S MiniCircuits Model ZFSC22500 or equivalent; provides the

diversity receive input to the BTS
High Stability 10 MHz Rubidium Standard
S Stanford Research Systems SR625 or equivalent required for CSM

and Low Frequency Receiver/High Stability Oscillator (LFR/HSO)
frequency verification.
Itasca Alarms Test Box
S Itasca CGDSCMIS00014 This test box may be used as a tool to

assist in the testing of customer alarms.
1-14
SEP 2009
Required Documents and Related Publications

Required Documents
The following documents are required to perform optimization of the

cell site equipment:
S Site document (generated by Motorola systems engineering), which

includes:
General site information
Floor plans
Power levels
Site PN
Site paging and traffic channel allocation
Board placement
Site wiring lists
CDF or NECF files (bts#.cdf and cbsc#.cdf or bts#.necf and
cbsc#.cdf)
S Demarcation Document (Scope of Work Agreement)

S Equipment manuals for non-Motorola test equipment.
Motorola Publications
General In addition to this publication, BTS, operating, conversion,
and other related publications listed in the following subsections are
required to support operations with the cell site equipment.
Required publication issue Use the issue of the publication for the
software release installed on the Radio Access Network (RAN) to which
the BTS being modified is assigned.
Visit https://mynetworksupport.motorola.com for complete lists of
Motorola BTS and operating publications by software release.
SC4812ET and Other Publications
The following publications are required to support various operations on
the cell site equipment:
S LMF Help function online documentation (part of the Local

Maintenance Facility (LMF) software application)
S 1X SC4812ET BTS Hardware Installation

S 1X SC4812ET Field Replaceable Units
S LMF CLI Reference
CDMA Remote Montoring System (CRMS) Publicaitons
S CRMS Probe Installation Guide; 68P02969A20

S CRMS Probe Users Guide; 68P02969A25
SEP 2009
1-15
continued
S CDMA RFDS Hardware Installation; 68P64113A93

S CDMA RFDS Users Guide; 68P64114A51
Additional NonMotorola Publications
S MWR1941DC Mobile Wireless Edge Router Hardware Installation

Guide; part number 7815827
S MWR 1941DC Wireless Mobile Edge Router Software Configuration

S MPATHt T1 Channel Service Unit Users Guide, 6577538101

S MPATHt T1 Channel Service Unit Installation Guide,
6577538001
S 2Slot Universal Shelf Installation Guide, 6578070001

Related Publications
Additional, detailed information about the installation, operation, and

maintenance of the SC4812ET BTS and its components is included in
the following publications:
S SC Product Family Frame Mounting Guide; 68P09226A18

S 1X SC4812 Series Packet BTS Troubleshooting Guide; 68P0926A07
S Cellular System Administration CDMA OnLine Documentation,
68P09271A90
S Glossary of Cellular Acronyms and Terms CDMA Online

Documentation
1-16
SEP 2009
Terms and Abbreviations

Standard and Nonstandard
Standard terms and abbreviations used in this manual are defined in

Glossary of Cellular Acronyms and Terms CDMA Online
Documentation. Any nonstandard terms or abbreviations included in
this manual are listed in Table 1-2.
Table 1-2: Abbreviations and Acronyms
Acronym
Definition
1X
One of two bandwidths currently defined in the IS2000 CDMA specification, which
extends the capability of the IS95A and B specifications. 1X bandwidth provides
wireless packet voice and data transmission capability at up to 144 Mbps.
ACLC
AC Load Center. Subassembly used in outdoor BTSs which provides the frame
interface for external AC power connection and internal AC circuit control and
protection.
AR
As Required
BBX1X
Broadband Transceiver, 3rd Generation supports IS95A/B and cdma2000 1X
BBXR
Redundant BBX for a CCP shelf or cage.
BPR
BTS Packet Router. Markings on GLI3 Fast Ethernet connectors and SC4812T Fast
Ethernet interface housing.
BSS
Base Station Subsystem (BSS). The BSS consists of a Radio Access Network (RAN), at
least one Access Node (AN), and a pair of core routers. It may also include a Digital
Access Crossconnect System (DACS) to support split backhaul and, under Software
Release 2.16.1.x and higher, a Selector Distribution Unit (SDU).
BTSRTR
BTS RouTeR (see BTS router)
BTSRTRGRP
BTS RouTeR GRouP (see BTS router group)
BTS router
One of the routers in a BTS router group.
BTS router group
The single nonredundant router or redundant router pair required for network interface
when a BTS is operating on packet backhaul.
cage
Used interchangeably with shelf in SC4812T/ET/ET Lite BTSs, as in Combined

CDMA Channel Processor shelf.
canned
configuration
See minimum standard configuration.
CCCP
Combined CDMA Channel Processor
CCD
Clock Combining and Distribution. CCP shelf module which accepts timing signals from
the active source and distributes them to other CCP shelf modules.
CEPT
Conference of European Postal and Telecommunications Administrators

SEP 2009
1-17
continued

Acronym
Definition
CF
Compact Flash. Type of flash memory card used in the BTS router to store the
Internetwork Operating System and configuration files.
CIO
Combiner Input/Output
CLPA
HighPower Linear Power Amplifier (supports 1.9 GHz only)
CRMS
Cellular Radio Monitoring System
companion frame
BTS frame configured to operate at the same site with another companion frame.
Companion frames may share antenna signals, but are not interconnected on the
same LAN. Companion frames are managed as separate BTSs in the Base Station
System.
DBPF
Dual Bandpass Filter
DBM
Debug Monitor
DLM
DownLoad Manager. Software application resident on the GLI card which permits
download of software upgrades from the Centralized Base Station Controller (CBSC)
to BTSs without the need for a site visit.
DMAC
Digital Metering and Alarm Control (also see MAP)
DRDC
Duplexer/RX Filter/Directional Coupler
DSP
Digital Signal Processor
duplex router
See redundant router
EMPC
Expansion Multicoupler Preselector Card
ESM
Ethernet Surge Module
ETIB
External Trunked Interface Board
EBR
External BTS Router
external BTS
router
MWR 1900 or MWR 1941 BTS routers mounted outside the CCCP or SCCP cage of a
packet BTS.
FE
Fast Ethernet. 100baseT mode of 10/100baseT Ethernet used for transmitting

packetized control and bearer traffic between the BTS router group and GLI3 cards in the
BTS.
FSI
Frame Status Indicator
FTP
File Transfer Protocol
FWTIC
Fixed Wireless Terminal Interface Card
GFCI
Ground Fault Connection Interrupt

1-18
SEP 2009
continued

Acronym
Definition
GLI3
Third generation Group Line Interface card. Replaces GLI2 cards in a BTS when
upgrading to packet backhaul capability under Software Release 2.16.1.x or higher.
Provides all the functionality of GLI2 cards plus additional capabilities needed for packet
backhaul. GLI3 cards may only be installed in BSSs operating with Software Release
2.16.1.x or higher software.
high availability
BTS router
See redundant router.
HSO
High Stability Oscillator
HSO2
Secondgeneration HSO card
HSOX
High Stability Oscillator eXpansion. Module installed in a BTS expansion frame which
interfaces with the starter frame HSO or MSO for distribution of starter frame timing
signals to the expansion frame CSM cards.
IBR
Integrated BTS Router; see integrated BTS router
Integrated BTS
Router
A GLI3 card loaded with bootROM code which allows the cards controller for
Concentration Interface Highway (CHI) bus 2 to function as a router for packet traffic for
the BTS. Employing IBRs permits converting a BTS to packet backhaul operation
without using an external BTS router group. IBRs can operate as nonredundant or
redundant BTS routers, but their employment limits BTS span capacity to two spans as
opposed to four spans for external BTS routers.
IFM
Integrated Frame Modem
IOSR
Internetwork Operating System. Operating system software used by the external BTS
routers.
LIF
Load Information File
LPAC
Linear Power Amplifier Controller
LORAN
LOng RAnge Navigational
MAP
MCC8E
Multichannel CDMA Card supporting 8 IS95A/B channels.
MCC24E
Multichannel CDMA Card supporting 24 IS95A/B channels.
MCC1X
Multichannel CDMA Card supporting 16 or 48 CDMA2000 1X or (with Software

Release 2.16.0.84.3 and higher) IS95A/B channels.
SEP 2009
1-19
continued

Acronym
Definition
minimum
standard
configuration
The initial minimum configuration data which must be loaded into a BTS router to enable
it to communicate on the network. This standard canned configuration is generated by a
script included in the R16.1 software load for the OMCR/CBSC. Separate configuration
files for the primary BTS router on each FE LAN at a site is created by the script and can
be copied to the Compact Flash (CF) memory card containing the IOS for BTS routers.
Once the CF card with the IOS and minimum standard configuration is installed, the BTS
router can communicate with the OMCIP and the full, sitespecific router configuration
file can be downloaded from the Mobile Wireless Center to the router. Different
configuration files are required for circuit and packet backhaul operation.
MPC
Multicoupler Preselector Card
MSO
Motorola Standard Oscillator
NECB
Network Element Configuration Baseline
NECF
Network Element Configuration File. Term which includes both the NECB and NECJ
files (see NECB and NECJ).
NECJ
Network Element Configuration Journal
NIC
Network Interface Card
nonredundant
router
A BTS router group consisting of a single router without redundancy used as a

costreduced network interface for a BTS operating on packet backhaul.
PDA
Power Distribution Assembly
packet backhaul
IPbased backhaul between the BTS and the the network. Packet backhaul capability is
implemented in Software Release 2.16.1.x and requires equipping a BTS with BTS
routers and GLI3 cards. With the packet backhaul upgrade, a BTS can be configured for
circuit operation with the capability to switch to packet backhaul or for packetonly
operation.
packet BTS
A BTS operating on packet backhaul
pBTS
Packet BTS
redundant router
A BTS router group consisting of two MWR 1900 or MWR 1941 routers with Hot
Standby Router Protocol (HSRP) to provide redundancy.
ROMmon
Lowlevel operating system used in MWR 1900 or MWR 1941 routers along with the
IOS
RGD
Remote Global Positioning System (GPS) Distribution. Module which allows distribution
of digital timing information from a single Remote GPS receiver to up to four BTS RF
modem frames (RFMFs).
RGPS
Remote Global Positioning System. GPS receiver which provides digital timing
information for BTS RFMFs at a cell site.
RHSO
Remote HighStability Oscillator. Subsystem which generates and distributes

synchronization signals from a single HSO to up to four RF modem frames.
1-20
SEP 2009
continued

Acronym
Definition
ROMmon
Lowlevel operating system used in MWR 1900 or MWR 1941 routers along with the
IOS
SBPF
Single Bandpass Filter
SFTP
Secure File Transfer Protocol
simplex router
See nonredundant router.
SNMP
Simple Network Management Protocol
SUA
Subscriber Unit Assembly
TCP
Temperature Compensation Panel
tftp
trivial file transfer protocol
UTC
Universal Time Coordinates
Var.
Variable
VWIC
VoiceWAN Interface Card
WIC
WAN Interface Card (also VWIC)
SEP 2009
1-21
BTS Equipment Identification

Equipment overview
The major components that make up the Motorola 1X SC 4812ET are

illustrated and described in this section. The major components are:
RF Cabinet The 1X SC 4812ET BTS (see Figure 1-2) consists of an
RF Cabinet that is an outdoor, weatherized version of the SC 4812T. The
RF cabinet is powered by 27 Vdc and each cabinet has the capability to
support up to 4 carriers (at 3 sector) or 2 carriers (at 6 sector). The RF
Cabinet houses the fan modules, CCCP, PA modules, PA trunking
backplane, Bandpass 2:1 and 4:1 Combiners, Duplexer/Receive
Filter/Directional Couplers (DRDC) and a DC Power distribution
assembly.
Power Cabinet The Power Cabinet (see Figure 1-8) provides +27
Vdc distribution and battery backup for the SC 4812ET. The Power
Cabinet houses batteries, battery heaters, rectifiers, an AC Load Center
(ACLC), a power distribution assembly, and two duplexed GFCI
convenience outlets.
1-22
SEP 2009
continued
RF Cabinet configurations
The SC4812ET RF Cabinet (see Figure 1-2) is available in starter and

companion frame configurations. Following are brief descriptions of
each
1. Starter This frame configuration is available with one, two, three
and four carriers, with separate antenna sets for each carrier. It can
operate as a standalone BTS, or can be modified in the field to the
companion frame configuration.
2. Companion This frame configuration is available with up to four
carriers. Companion frames share RX signals to provide diversity
RX for the opposite frame. Companion frames allow equipping an
SC 4812ET site with up to eight carriers. Each companion frame is
managed in the Base Station System (BSS) as a separate BTS.
Figure 1-2: SC 4812ET RF Cabinet
RF I/O
Area Cover Plate
Main Door
Rear Conduit Panel
PA Door
(Can only be opened after Main Door is open)
Rear DC Conduit Panel
Rear I/O Door

FW00189
SEP 2009
1-23
continued
Internal RF Cabinet
components
CCCP Shelf Card/Module Device ID Numbers

All cards/modules/boards in the frames at a single site, assigned to a
single BTS number, are also identified with unique Device ID numbers
dependent upon the Frame ID number in which they are located. Refer to
Table 1-3 and Table 1-4 for specific CCCP Shelf Device ID numbers.
Table 1-3: CCCP Shelf/Cage Card/Module Device ID Numbers (Top Shelf)
Frame
#
Card/Module ID Number (Left to Right)

Power
Power
Power
AMR
GLI
(PS1)
(PS2)
(PS3)
MCC
101
101
101
101 102
103
104 105
106
101 102
201
201
201
201 202
203
204 205
206
301
301
301
301 302
303
304 305
306
BBX
BBX
MPC/
EMPC
1
R1
103 104
105
106
R101
201 202
203 204
205
206
R201
301 302
303 304
305
306
R301
Table 1-4: CCCP Shelf/Cage Card/Module Device ID Numbers (Bottom Shelf)

Frame
#
Card/Module ID Number (Left to Right)

HSO/ CSM CSM CCD CCD
LFR
1
2
A
B
AMR GLI2
2
MCC
10
11
12
10
MPC/
EMPC
2
12
111 112
101
101
102
102
102
107 108 109 110
111 112 107 108
109 110
201
201
202
202
202
207 208 209 210
211
212 207 208
209 210 211
212
301
301
302
302
302
307 308 309 310
311
312 307 308
309 310 311
312
SW
1-24
BBX
11
SEP 2009
continued
Internal RF Cabinet Assemblies

and FRUs
Figure 1-3 shows the location of the internal assemblies and Field
Replaceable Units (FRU). A brief description of each item is found in
the following paragraphs.
Figure 1-3: RF Cabinet Internal Assemblies and FRUs

NOTE
Cabinet doors not shown for clarity.
EBA
ETIB
CCP Fans
RFDS
CCCP Shelf
5 RU Rack Space
Combiner
Cage
OPTIONAL AREA
DC
Power
Dist.
Punch
Block
(back)
Circuit
Breaker Panel
DRDC
SEP 2009
PA Trunking
Backplane
LPAs/
CLPAs
FW00163
1-25
continued
Duplexer/RX Filter Directional Coupler

The DRDC combines, in a single module, the functions of antenna
duplexing, receive band pass filtering, and surge protection (see
Figure 1-7).
Combiner Cage (2:1, 4:1, or Band pass Filter)
The Combiner Cage holds the transmit band pass filters, 2:1 combiners,
or 4:1 combiners, depending on system configuration.
Combined CDMA Channel Processor Shelf
The CCCP shelf contains the following (see Figure 1-4):
S Low Frequency Receiver (LFR), High Stability Oscillator (HSO),

Motorola Standard Oscillator (MSO), or Quartz High Stability
Oscillator (QHSO) card (1)
S
S
S
S
Clock Synchronization Manager (CSM) cards (2)

CDMA Clock Distribution (CCD) cards (2)
Power Supply cards (2 minimum, 3 maximum)
Multicoupler Preselector Cards (MPC) or Expansion Multicoupler
Preselector Cards (EMPC) (2)
S Alarm Monitoring and Reporting (AMR) cards (2)

S Multi Channel CDMA (MCC8E, MCC24E or MCC1X) cards (up to
12)
S
S
S
S
S
S
S
1-26
Broadband Transceiver (BBX2 or BBX1X) cards (up to 13)

Combined Input/Output (CIO) card (1)
Group Line Interface (GLI2 or GLI3) cards (2)
BBX Switch card (1)
Modem (optional)
Filler Panels (as required)
Fan Module (3)
SEP 2009
continued
Figure 1-4: SC 4812ET CCCP Shelf

SC 4812ET RF Cabinet
ETIB
EBA
MPC/EMPC1
5 RU RACK
SPACE
MPC/EMPC2
Switch
BBX12
BBX11
BBX10
BBX9
BBX8
BBX7
MCC11
MCC12
MCC9
MCC10
MCC8
MCC7
GLI3
AMR
MODEM
CCD
CSM
CSM
HSO/LFR
CCD
CIO
BBX6
BBXR
BBX5
BBX4
BBX3
BBX2
BBX1
MCC6
MCC5
MCC4
MCC3
MCC2
GLI3
MCC1
AMR
Power Supply
Power Supply
Power Supply
19 mm Filter Panel
RFDS
NOTE: MCCs may be

MCC8Es, MCC24Es
or MCC1Xs. BBXs
may be BBX2s or
BBX1Xs.
REF FW00304
Punch Block
The Punch Block is the interface point of the RF Cabinet between the
T1/E1 span lines, the Customer I/O, alarms, multicabinet timing
(RGPS and HSO), and Pilot Beacon control (optional). (see Figure 1-6).
Span I/O Board
The Span I/O Board provides the interface for the span lines from the
CSU to the CCCP backplane (see Figure 1-6).
RF Diagnostic Subsystem
The RFDS provides the capability for remotely monitoring the status of
the SC 4812ET RF Transmit and Receive paths (Figure 1-7).
Heat Exchanger
The Heat Exchanger provides cooling to the internal compartment of the
RF Cabinet. The fan speed of the heat exchangers adjusts automatically
with temperature. The Heat Exchanger is located in the primary front
door of the RF Cabinet.
SEP 2009
1-27
continued
Interface Board (ETIB) & PA Control Brd (LPAC)

The ETIB is an interconnect board showing status LEDs for the RF
Cabinet, as well as providing secondary surge protection. The LPAC
board provides the interface for the PA connection.
Trunking Backplane
The Trunking Backplane contains a complex passive RF network that
allows RF signals to share the resources of a bank of four PAs. It also
provides DC Power and digital interconnect.
Power Amplifiers
S Trunked Linear Power Amplifier (TLPA, or more commonly referred

to as LPA) modules, OR
S High Power Linear Power Amplifier (CLPA; currently supporting

only 1.9 GHz band) modules.
Figure 1-5: SC 4812ET Intercabinet I/O Detail (Rear View)
RF CABINET
(Rear View)
Exp. Punch
Block
Punch
Block
RF Expansion
27V
Microwave
RF GPS
13 Sector Antennas
RFDS Expansion
27V Ret
46 Sector Antennas
2 Sec Tick
RF CABINET
(Rear Door closed)
19 MHz Clock
Ground Cable
Lugs
Expansion 1
Expansion 2
1-28
LAN
DC Conduit
RGPS
RFGPS
Span/Alarm
FW00147
Pilot Beacon
SPAN I/O
SEP 2009
continued
Figure 1-6: SC 4812ET I/O Plate Diagram
20 Pair
Punchblock
(RGPS)
1A
2A
3A
1B
2B
3B
4A
5A
6A
4B
5B
6B
50 Pair
Punch
Block
(Alarms/Spans)
RGD/RGPS
2A
3A
1B
Power Input
+27V
Micro
wave
RF Expansion Ports
1A
RGD
Board
RF
GPS
2B
LAN
3B
IN OUT
A
B
Remote
ASU
1
4A
5A
6A
4B
5B
6B
19 MHz
Spans
Modem
Alams
Antennas
Power Input
27V Ret
2 Sec
GND
Lugs
FW00171
SEP 2009
1-29
continued
Figure 1-7: RFDS Location in an SC 4812ET RF Cabinet

FRONT VIEW
(door not shown for clarity)
RFDS
WALL
MOUNTING
BRACKET
DRDC
BTS
CPLD
ANT
CPLD
3B 2B 1B 3A 2A 1A
DRDC CAGE
6B 5B 4B 6A 5A 4A
FW00170
1-30
SEP 2009
continued
Power Cabinet
Figure 1-8 illustrates the Power Cabinet design.

Figure 1-8: Power Cabinet
GFCI Outlet
Cover
Battery Door
Rear I/O
Door
Rear DC
Conduit Panel
Main Door
Rear AC Conduit
Panel
FW00193
SEP 2009
1-31
continued
Internal Power Cabinet FRUs
Figure 1-9 shows the location of the Internal Field Replaceable

Units (FRUs). A brief description of each Internal FRU is found in the
following paragraphs.
Figure 1-9: Power Cabinet with Batteries Installed (Doors Removed for Clarity)
Rectifier
Alarm Module
Temperature
Control Module
Rectifier
Shelves
Batteries (Battery
Heaters located
under batteries)
GFCI Outlets
(Back)
NOTE
Punch Block is not
visible in this view.
DC Circuit
Breakers
AC Load
Center
FW00164
FRONT VIEW POWER CABINET
Batteries
The batteries provide a +27 Vdc backup to the RF Cabinet should AC
Power be lost. The Power Cabinet can accommodate a total of 24 12V
batteries, configured in 12 strings of 2 batteries each. The time duration
of backup provided depends on system configuration.
Battery Heater
The battery heaters provide heating to the batteries in the Power Cabinet.
A separate heater is required for each string of batteries. The heater is a
pad the batteries sit on located top of each battery shelf. The number of
heaters is dependent on system configuration.
1-32
SEP 2009
continued
Battery Compartment Fan

The battery compartment fan provides air circulation for the two battery
compartments. It is located on the inside of the battery compartment
door.
Heat Exchanger
The Heat Exchanger provides cooling to the rectifier compartment of the
Power Cabinet. The Heat Exchanger is located in the primary front door
of the Power Cabinet.
Rectifiers
The +27 Vdc rectifiers convert the AC power supplied to the Power
Cabinet to +27 Vdc to power the RF Cabinet and maintain the charge of
the batteries.
AC Load Center
The ACLC is the point of entry for AC Power to the Power Cabinet. It
incorporates AC power distribution and surge protection.
Punch Block
The Punch Block is the interface for the alarm signalling between the
Power Cabinet and the RF Cabinet.
SEP 2009
1-33
continued
CCCP Cage Configuration and

1X Devices
SC4812ET frames have one CCCP cage (see Figure 1-4) which will
support up to 12 MCC cards and 13 BBX cards.
MCC Cards
A BTS may be configured with a mix of MCC8E, MCC24E, and
MCC1X cards. Any CCCP cage MCC card slot will support any of
the three MCC types. For 1X capability under R16.0, at least one MCC
card must be an MCC1X which can be installed in any MCC card slot.
In a BSS operating with Software Release 2.16.0.84.3 and higher,
MCC1X cards will support IS95A and B traffic as well as
CDMA2000 1X. When operating with Software Release 2.16.0.5x.x, the
MCC1X cards do not support IS95A/B operation. For additional
software release compatibility and capability information, contact the
local Motorola account team.
BBX Cards
Up to twelve BBX cards of mixed BBX2s and BBX1Xs can also be
supported. CCCP cage BBX card slots 1 through 12 are carrier and
sectordependent. As a result, the BBX slots dedicated to the sectors for
one carrier should be populated with the same type of cards. Refer to
Table 1-6 for BBX card slot carrier and sector correlations.
IMPORTANT
See BBX Interchangeability below for proper

implementation of the variety of BBX cards available.
The CCCP cage BBXR card slot is dedicated to the redundant BBX.
This slot will support either a BBX2 or a BBX1X. If a cage has
BBX1X carriers, the redundant BBX (BBXR) must be a BBX1X card
to provide 1X redundancy.
BBX Interchangeability
In a BTS operating with R16.x software, BBX1X cards can be used as

direct replacements for BBX2 cards; however, different types of BBXs
should not be mixed on the same carrier. Therefore, if a BBX2 card is
replaced with a BBX1X, all remaining BBX2 cards for the carrier
supported by the replaced card must also be replaced with BBX1X
cards.
1-34
SEP 2009
Sector Configuration
There are a number of ways to configure the BTS frame. Table 1-5
outlines the basic requirements. When carrier capacity is greater than
two, a 2:1 or 4:1 cavity combiner must be used. For one or two carriers,
bandpass filters or cavity combiners may be used, depending on
sectorization and channel sequencing.
Table 1-5: BTS Sector Configuration
Number of carriers
Number of sectors
3 or 6
Channel spacing
Filter requirements
N/A
Bandpass Filter, Cavity Combiner

(2:1 or 4:1)
Nonadjacent
Cavity Combiner (2:1 Only)
Adjacent
Dual Band Pass Filter
Nonadjacent
Cavity Combiner (2:1 or 4:1)
Adjacent
Bandpass Filter
3,4
Nonadjacent
Cavity Combiner (2:1 or 4:1)
3,4
Adjacent
Cavity Combiner (2:1 Only)
The matrix in Table 1-6 shows a correlation between the various sector
configurations and BBX cards.
NOTE
In Table 1-6, BBXs may be BBX2s or BBX1Xs.
SEP 2009
1-35
continued
Table 1-6: Sector Configurations

Config Ref. No.
Description
3Sector/2ADJACENT Carriers The configuration below maps TX with optional 2:1
cavity combiners for 3 sectors/2 carriers for adjacent channels. Note that 2:1 cavity
combiners are used (6 total).
TX1
TX2
TX3
TX4
TX5
TX6
Carrier#
BBX1
BBX2
BBX3
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
6Sector/2NONADJACENT Carriers The configuration below maps TX with 2:1

cavity combiners for 6 sectors/2 carriers for nonadjacent channels.
2
TX1
TX2
TX3
TX4
TX5
TX6
Carrier#
BBX1
BBX2
BBX3
BBX4
BBX5
BBX6
BBX7
BBX8
BBX9
BBX10
BBX11
BBX12
3Sector/2NONADJACENT Carriers The configuration below maps TX with 2:1

cavity combiners for 3 sectors/2 carriers for nonadjacent channels.
3
TX1
TX2
TX3
TX4
TX5
TX6
Carrier#
BBX1
BBX2
BBX3
N/A
N/A
N/A
BBX7
BBX8
BBX9
N/A
N/A
N/A
3Sector/4ADJACENT Carriers The configuration below maps TX with 2:1 cavity

combiners for 3 sector/4 carriers for adjacent channels.
TX1
TX2
TX3
TX4
TX5
TX6
Carrier#
BBX1
BBX2
BBX3
N/A
N/A
N/A
N/A
N/A
N/A
BBX7
BBX8
BBX9
BBX4
BBX5
BBX6
N/A
N/A
N/A
N/A
N/A
N/A
BBX10
BBX11
BBX12
3Sector/2ADJACENT Carriers The configuration below maps TX with bandpass

filters for 3 sectors/2 carriers for adjacent channels.
5
TX1
TX2
TX3
TX4
TX5
TX6
Carrier#
BBX1
BBX2
BBX3
N/A
N/A
N/A
N/A
N/A
N/A
BBX7
BBX8
BBX9
table continued next page
1-36
SEP 2009
continued
Table 1-6: Sector Configurations

Config Ref. No.
Description
3Sector/3 or 4NONADJACENT Carriers The configuration below maps TX with
4:1 cavity combiners for 3 sectors/3 or 4 carriers for nonadjacent channels.
TX1
TX2
TX3
TX4
TX5
TX6
Carrier#
BBX1
BBX2
BBX3
N/A
N/A
N/A
BBX7
BBX8
BBX9
N/A
N/A
N/A
BBX4
BBX5
BBX6
N/A
N/A
N/A
BBX10
BBX11
BBX12
N/A
N/A
N/A
6Sector/1Carrier The configuration below maps TX with either bandpass filters or

2:1 cavity combiners for 6 sector/1 carrier.
7
SEP 2009
TX1
TX2
TX3
TX4
TX5
TX6
Carrier#
BBX1
BBX2
BBX3
BBX4
BBX5
BBX6
1-37
continued
Figure 1-10: SC4812ET PA Configuration with Combiners/Filters

Sector
Numbering
3 Sector
(6 Sector)
2 to 1 Combiner
3 Sector or 6 Sector
ETIB
4 to 1 Combiner
3 Sector Only
ETIB
EBA
RFDS
EBA
RFDS
C1, S1S3
C1
C2, S1S3
C2
(C1, S1S3)
(C2, S1S3)
5 RU RACK
SPACE
5 RU RACK
SPACE
C3, S1S3
C3
(C1, S4S6)
C4
C4, S1S3
(C2, S4S6)
Sector
Numbering
3 Sector
(6 Sector)

3 Sector Only
2 Carrier Maximum
ETIB
EBA
RFDS
C1, S1S3
(C1, S1S3)
NOTE:
An LPA Trunk set (4 LPAS per Trunk set)
can be replaced With a CLPA Trunk set
(3 CLPAs per Trunk set)
C2, S1S3
(C2, S1S3)
5 RU RACK
SPACE
C3, S1S3
(C1, S4S6)
4 LPAs
3 CLPAs
C4, S1S3
(C2, S4S6)
ti-CDMA-WP-00267-v01-ildoc-ftw
1-38
SEP 2009
Chapter 2: Preliminary Operations

Table of Contents
SEP 2009
Preliminary Operations: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cellsite Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NEC Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
2-1
2-1
2-1
Site Equipage Verification and Card/Module Installation . . . . . . . . . . . . . . . . .

Site Equipage Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial Installation of Cards/Modules . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2
2-2
2-2
Frame Identification Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting Frame Identification (ID) with CCCP Cage Backplane
DIP Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4
2-4
PrePowerup Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking for shorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial Inspection and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AC Power Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
2-5
2-5
2-6
2-6
AC Power Up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Applying AC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Cabinet Power Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-8
2-8
2-9
PreDC Powerup test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Testing Before Applying DC Power . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-10
2-10
RF Cabinet Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RF Cabinet Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-12
2-12
Power Cabinet Battery Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Charge Test (Connected Batteries) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discharge Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-14
2-14
2-15
Heat Exchanger Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-16
Circuit Breaker Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-17
Table of Contents
continued
Notes
SEP 2009
Preliminary Operations: Overview

Preliminary Operations: Overview
Introduction
2
This section first verifies proper frame equipage. This includes verifying
module placement, jumper, and Dual Inline Package (DIP) switch
settings against the site-specific documentation supplied for each BTS
application. Next, pre-power up and initial power-up procedures are
presented.
Cellsite Types
Sites are configured as Omni, 3sectored with a maximum of 4 carriers,

and 6sectored with a maximum of 2 carriers. Each type has unique
characteristics and must be optimized accordingly.
NEC Files
The Network Element Configuration (NEC) files (packet BTS) contain

site type and equipage data information and passes it directly to the LMF
during optimization. The number of modem frames, CCCP shelves,
BBX boards, MCC boards (per cage), and power amplifier assignments
are some of the equipage data included in the NEC files.
CAUTION
Be sure that the correct NECB*bts#.xml and
NECJ*bts#.xml files are used for the BTS. These should
be the NEC files that are provided for the BTS by the
OMCR. Failure to use the correct NEC files can cause
system errors. Failure to use the correct NEC files to log
into a live (traffic carrying) site can shut down the site.
SEP 2009
2-1
Site Equipage Verification and Card/Module Installation

2
Site Equipage Verification
Review the site documentation. Match the site engineering equipage data
to the actual boards and modules shipped to the site. Physically inspect
and verify the equipment provided for the BTS or modem frame and
ancillary equipment frame.
CAUTION
Always wear an approved antistatic wrist strap while
handling any circuit card/module to prevent damage from
ESD. After removal, the card/module should be placed on
a conductive surface or back into the antistatic shipping
container.
Initial Installation of
Cards/Modules
Follow the procedure in Table 2-1 to verify the initial installation of

cards/modules.
Table 2-1: Initial Installation of Cards/Modules
Step
Action
Refer to the site documentation and install all cards and modules into the appropriate shelves as
required. Verify they are NOT SEATED at this time.
NOTE
The Switch card has a configuration DIP switch that must be set to match the site configuration (see
Figure 2-1).
As the actual site hardware is installed, record the serial number of each module on a Serial Number
Checklist in the site logbook.
NOTE
Figure 2-1 shows DIP switch configuration settings for
SC4812Tseries BTS models in both 3sector and
6sector configurations. Switches 1 and 4 control
configuration.
For Multicarrier BTS models, switch 1 should be down.
2-2
SEP 2009
continued
Figure 2-1: SC4812Tseries BTS Switch Card DIP Switch Settings
SHIELDS
CONFIGURATION
DIP SWITCH
CCCP CAGE
BTS AND SECTOR CONFIGURATION

SWITCH SETTINGS
SC4812T,
SC4812T CLPA,
and
SC4812TMC
SC4812ET
3SECTOR SITE
3SECTOR SITE
1 2 3 4
1 2 3 4
3 Sector
6 Sector
BTS ON
MF
MF
6SECTOR SITE
SWITCH CARD
6SECTOR SITE
1 2 3 4
BTS ON
MF
3 Sector
6 Sector
BTS ON
1 2 3 4
3 Sector
6 Sector
BTS ON
MF
3 Sector
6 Sector
SEP 2009
2-3
Frame Identification Switch Settings

Frame Identification Switch Settings
Setting Frame Identification
(ID) with CCCP Cage
Backplane DIP Switch
IMPORTANT
Inspect and set the BTS frame ID with the CCCP cage
backplane Dual Inline Package (DIP) switch before power
is applied to the frame.
Inspect the CCCP cage backplane switch in a BTS or in each frame of a

logical BTS and set as required for the BTS frame number as shown in
Figure 2-2.
Figure 2-2: SC4812Tseries BTS Backplane DIP Switch Settings for BTS or Logical BTS Operation
MODEM_FRAME_ID_0
MODEM_FRAME_ID_1
RIGHT / LEFT
PWR/ALM
MPC
AMR / MACH
GLI2
MCC247
MCC248
MCC249
MCC2410
MCC2411
MCC2412
BBX27
BBX28
BBX29
BBX210
BBX211
BBX212
Switch
39 mm Filter Panel
FRAME 201
SETTING
(EXPANSION
FRAME 2)
CSM
CCD
CIO
MPC
FRONT
AMR / MACH
GLI2
MCC241
MCC242
MCC243
MCC244
MCC245
MCC246
BBX21
BBX22
BBX23
BBX24
BBX25
BBX26
BBX2R
Power Supply
Power Supply
19 mm Filter Panel
Power Supply
PWR/ALM
FRONT
FRAME 101
SETTING
(EXPANSION
FRAME 1)
FAN
MODULE
REAR
CCD
ON
OFF
FAN
MODULE
REAR
CSM
MODEM_FRAME_ID_0
MODEM_FRAME_ID_1
RIGHT / LEFT
BOTTOM / TOP
ON
OFF
FARRIGHT
FAN MODULE
REMOVED
FRAME 1
SETTING
(STANDALONE
STARTER FRAME
AND LOGICAL
BTS PRIMARY
FRAME)
HSO
MODEM_FRAME_ID_0
MODEM_FRAME_ID_1
RIGHT / LEFT
BOTTOM / TOP
ON
OFF
BOTTOM / TOP
SC4812T SERIES BTS CCCP CAGE

SC4812T_01010
2-4
SEP 2009
PrePowerup Tests
PrePowerup Tests
Checking for shorts
2
The following information is used to check for any electrical short
circuits and to verify the operation and tolerances of the cellsite and BTS
power supply units before applying power for the first time. It contains
instructional information on the initial proper power up procedures for
the SC 4812ET power cabinet and RF cabinet. Also presented are tests
to be performed on the power cabinet. Please pay attention to all
cautions and warning statements in order to prevent accidental injury to
personnel.
Required Tools
The following tools are used in the procedures.
S DC current clamp (600 A capability with jaw size to accommodate 2/0

cable).
S Hot Air Gun (optional for part of the Alarm Verification)

S Digital Multimeter (DMM)
Cabling Inspection
Using the site-specific documentation generated by Motorola Systems

Engineering, verify that the following cable systems are properly
connected:
S Receive RF cabling up to 12 RX cables

S Transmit RF cabling up to six TX cables
NOTE
For positive power applications (+27 V):
S The positive power cable is red.
S The negative power cable is black. (The black power

cable is at ground potential.)
SEP 2009
2-5
PrePowerup Tests
continued
Initial Inspection and Setup
CAUTION
Ensure all battery breakers for unused battery positions are

open (pulled out) during any part of the power up process,
and remain in the off position when leaving the site.
Table 2-2: Initial Inspection and Setup

Step
Action
Verify that ALL AC and DC breakers are turned OFF in both the Power and RF cabinets. Verify that
the DC power cables between the Power and RF cabinets are connected with the correct polarity
The RED cables connect to the uppermost three (3) terminals (marked +) in both cabinets. Confirm
that the split phase 240/120 AC supply is correctly connected to the AC load center input.
CAUTION
Failure to connect the proper AC feed will damage the
surge protection module inside the AC load center.
AC Power Check
The first task in the power up sequence is to apply AC power to the

Power cabinet. Once power is applied a series of AC Voltage
measurements is required.
Table 2-3: AC Voltage Measurements
Step
Action
Measure the AC voltages connected to the AC load center (access the terminals from the rear of the
cabinet after removing the AC load center rear panel). See Figure 2-3.
Measure the AC voltage from terminal L1 to neutral. This voltage should be in the range of nominally
115 to 120 Vac.
Measure the AC voltage from terminal L1 to ground. This voltage should be in the range of nominally
115 to 120 Vac.
Measure the AC voltage from terminal L2 to neutral. This voltage should be in the range of nominally
115 to 120 Vac.
Measure the AC voltage from terminal L2 to ground. This voltage should be in the range of nominally
115 to 120 Vac.
Measure L1 L2 should be from 208 to 240 Vac.
2-6
SEP 2009
PrePowerup Tests
continued
CAUTION
If the AC voltages are in excess of 120 V (or exceed
200 V) when measuring between terminals L1 or L2 to
neutral or ground, STOP and Do Not proceed until the
cause of the higher voltages are determined. The power
cabinet WILL be damaged if the Main breaker is turned
on with excessive voltage on the inputs.
Figure 2-3: AC Load Center Wiring
G (Ground)
N (Neutral)
L1 (Line 1)
L2 (Line 2)
AC to Pilot Beacon
FW00305
SEP 2009
2-7
AC Power Up Sequence
2
Applying AC Power
Once AC Voltage Measurements are complete, apply AC power to the

Power Cabinet. Table 2-4 provides the procedure for applying AC
power.
Table 2-4: Applying AC Power
Step
Action
When the input voltages are verified as correct, turn the Main AC breaker (located on the front of the
ACLC) ON. Observe that all eight (8) green LEDs on the front of the ACLC are illuminated (see
Figure 2-9).
Turn Rectifier 1 and Rectifier 2 AC branch breakers (on the AC Load Center) ON. All the installed
rectifier modules (see Figure 2-9) will start up and should each have two green LEDs (DC and Power)
illuminated.
Turn the Meter Alarm Panel module, ON (see Figure 2-4), while observing the K2 contact in the PDA
assembly (see Figure 2-11). The contact should close. The Meter Alarm Panel voltage meter should
read approximately 27.4 + 0.2 Vdc.
Turn the Temperature Compensation Panel (TCP) ON, (see Figure 2-5). Verify that the Meter Alarm
Control Panel does not have any alarm LEDs illuminated.
Check the rectifier current bargraph displays (green LED display on the rectifier module). None should
be illuminated at this point.
NOTE
If batteries are fitted, turn on the two battery heater AC
breakers on the AC Load Center.
Figure 2-4: Meter Alarm Panel
VOLT
AMPS
VOLT
+
AMP
TEST POINTS
TEST POINTS
FRONT VIEW
2-8
PWR
OFF ON
FW00245
SEP 2009
continued
Figure 2-5: Temperature Compensation Panel
TEMPERATURE COMPENSATION PANEL
1/2 A 250V
OFF ON
ON
SENSOR SENSE
COM 1 2 +
FRONT VIEW
25_ c
V ADJ
FW00246
Power Cabinet Power Tests
Table 2-5 lists the stepbystep instructions for Power Up Tests.

Table 2-5: Power Cabinet Power Up Tests
Step
Action
Probe the output voltage test point on the Meter Alarm Panel while pressing the 25 C set button on
the TCP (see Figure 2-5). The voltage should read 27.4 + 0.2 Vdc. Adjust Master Voltage on Meter
Alarm Panel if necessary. Release the TCP 25 C set button.
Depending on the ambient temperature, the voltage reading may now change by up to + 1.5 V
compared to the reading just measured. If it is cooler than 25_C, the voltage will be higher, and if it is
warmer than 25_C, the voltage will be lower.
Ensure the RF cabinet 400 A main DC breaker is OFF.
Close the three (3) Main DC breakers on the Power Cabinet ONLY. Close by holding in the reset
button on the front of the PDA, and engaging one breaker at a time.
Measure the voltage between the + and terminals at the rear of the Power Cabinet and the RF
Cabinet, observing that the polarity is correct. The voltage should be the same as the measurement in
step 2.
Place the probes across the black and red battery buss bars in each battery compartment. Place the
probe at the bottom of the buss bars where the cables are connected. The DC voltage should measure
the same as the previous step.
SEP 2009
2-9
PreDC Powerup test

PreDC Powerup test
2
Testing Before Applying DC

Power
Before applying any power to the BTS cabinet, verify there are no shorts
in the RF or power DC distribution system (see Figure 2-6).
Table 2-6: DC Power Pretest (BTS Frame)
Step
Action
Physically verify that all AC rectifiers supplying power to the RF cabinets are OFF or disabled (see
Figure 2-6). There should be no 27 Vdc on DC feed terminals.
On each RF cabinet:
S Unseat all circuit boards/ modules in the distribution shelf, transceiver shelf, and Single Carrier
Linear Power Amplifier (SCLPA) shelves, but leave them in their associated slots.
S Unseat all circuit boards (except CCD and CIO cards) in the CCCP shelf and LPA shelves, but
leave them in their associated slots.
S Set CCCP shelf breakers to the OFF position by pulling out power distribution breakers (labeled
CCCP 1, 2, 3 located on the power distribution panel).
S Set LPA breakers to the OFF position by pulling out power distribution breakers (8 breakers,
labeled 1A1B through 4C4D located on the power distribution panel).
Verify that the resistance from the power (+) feed terminals with respect to the ground terminal on the
cabinet measures > 500 (see Figure 2-6).
S If reading is < 500 , a short may exist somewhere in the DC distribution path supplied by the
breaker. Isolate the problem before proceeding. A reading > 3 M could indicate an open (or
missing) bleeder resistor (installed across the filter capacitors behind the breaker panel).
Set the 400 Amp Main Breaker and the CCCP breakers (CCCP 1, 2, 3) to the ON position by
pushing them IN one at a time. Repeat step 3 after turning on each breaker.
* IMPORTANT
If, after inserting any board/module, the ohmmeter stays at 0 , a short probably exists in that
board/module. Replace the suspect board/module and repeat the test. If test still fails, isolate the
problem before proceeding.
5
Insert and lock the DC/DC converter modules into their associated slots one at a time. Repeat step 3
after inserting each module.
S A typical response is that the ohmmeter will steadily climb in resistance as capacitors charge, finally
indicating approximately 500 .
! CAUTION
Verify the correct power/converter modules by observing the locking/retracting tabs appear as follows:
STPN4009
PWR CONV CDMA RCVR
2-10
SEP 2009
PreDC Powerup test
continued
Table 2-6: DC Power Pretest (BTS Frame)

Step
Action
Insert and lock all remaining circuit boards and modules into their associated slots in the CCCP shelf.
Repeat step 3 after inserting and locking each board or module.
S A typical response is that the ohmmeter will steadily climb in resistance as capacitors charge,
stopping at approximately 500 ..
Set the 8 LPA breakers ON by pushing them IN one at a time. Repeat step 3 after turning on each
breaker.
Seat all LPA and associated LPA fan modules into their associated slots in the shelves one at a time.
Repeat step 3 after seating each LPA and associated LPA fan module.
Seat the Heat Exchanger, ETIB, and Options breakers one at a time. Repeat step 3.
SEP 2009
2-11
RF Cabinet Power Up
RF Cabinet Power Up
2
RF Cabinet Power Up
Table 2-7 covers the procedures for properly powering up the RF

Cabinet.
Table 2-7: RF Cabinet Power Up
Step
Action
Ensure the 400 Amp Main DC breaker and all other breakers in the RF Cabinet are OFF.
Proceed to the DC Power Pretest (BTS Frame) sequence (see Table 2-6) (for initial powerup as
required).
Ensure the power cabinet is turned on (see Table 2-5). Verify that 27 volts is applied to the terminals
on the back of the RF cabinet.
Engage the main DC circuit breaker on the RF cabinet (see Figure 2-6).
On each RF cabinet:
S Set CCCP shelf breakers to the ON position by pushing them in one at a time (labeled
CCCP 1, 2, 3 located on the power distribution panel).
S Set LPA breakers to the ON position by pushing them in one at a time (8 breakers, labeled 1A1B
through 4C4D located on the power distribution panel).
S Set the two heat exchanger breakers to the ON position by pushing them in one at a time.
S Set the ETIB breaker to the ON position by pushing it in.
S Set the OPTION breaker to the ON position by pushing it in.
6
Measure the voltage drop between the Power Cabinet meter test point and the 27 V buss bar inside the
RF Cabinet PDA while the RF Cabinet is transmitting.
NOTE
S For a 3sector carrier system, the voltage drop should be less than 0.2 V.
S For a 12sector carrier system, the voltage drop should be less than 0.3 V.
7
2-12
Using a DC current probe, measure the current in each of the six (6) DC cables that are connected
between the RF and Power Cabinet. The DC current measured should be approximately the same. If
there is a wide variation between one cable and the others (>20 A), check the tightness of the
connections (torque settings) at each end of the cable.
SEP 2009
RF Cabinet Power Up
continued
Figure 2-6: RF Cabinet Circuit Breaker Panel and 27 Vdc Terminal Locations
2
400
5 RU RACK
SPACE
MAIN BREAKER
L
P
A
C
C
C
P
1A
30
1B
1C
30
1D
2A
30
2B
2C
30
2D
3A
30
3B
3C
30
3D
4A
30
4B
4C
30
4D
PS1
50
PS2
50
PS3
50
LPA
BLOWERS
25
SC 4812ET BTS RF Cabinet

(Front View)
RF CABINET
(Rear View)
HEAT EXCHANGER
CAUTION
SHUT OFF BOTH BREAKERS
PUSH BUTTON
TO RESET
LPA BLOWERS
MAINTENANCE OR REPAIR
ETIB
10
OPTION
15
FW00307
SEP 2009
27V
25 ONLY DURING HEAT EXCHANGER
27V Ret
I/O Plate + and DC Feed Terminals

(Back Panel of RF Cabinet)
2-13
Power Cabinet Battery Test

2
Charge Test (Connected

Batteries)
Table 2-8 lists the step-by-step instructions for testing the batteries.
Table 2-8: Battery Charge Test (Connected Batteries)
Step
1
Action
Close the battery circuit breakers (press in) for connected batteries ONLY (see Figure 2-7). This
process should be completed quickly to avoid individual battery strings with excess charge current.
NOTE
If the batteries are sufficiently discharged, the battery circuit breakers may not engage individually due
to the surge current. If this condition is observed, turn off the Meter Alarm Panel power switch, and
then engage all the connected battery circuit breakers. Then, turn ON the Meter Alarm Panel power
switch.
2
Using the DC current probe, measure the current in each of the battery string connections to the buss
bars in each battery cabinet. The charge current may initially be high but should quickly reduce in a
few minutes if the batteries have a typical new battery charge level.
The current in each string should be approximately equal (+ 5 A).
The bargraph meters on the rectifier modules can be used as a rough estimate of the total battery
charge current. Each rectifier module has eight LEDs to represent the output current. Each illuminated
LED indicates that approximately 12.5% (1/8 or 8.75 A) of the rectifiers maximum (70 A) current is
flowing.
EXAMPLE:
Question: A system fitted with three rectifier modules each have three bargraph LEDs illuminated.
What is the total output current into the batteries?
Answer: Each bargraph is approximately indicating 12.5% of 70 A, therefore, 3 X 8.75A equals
26.25A. As there are three rectifiers, the total charge current is equal to (3 X 26.25 A) 78.75 A.
This charge current calculation only applies at this part of the start up procedure when the RF Cabinet
is not powered on, and the power cabinet heat exchanger is turned off.
Allow a few minutes to ensure that the battery charge current stabilizes before taking any further
action. Recheck the battery current in each string. If the batteries had a reasonable charge, the current
in each string should reduce to less than 5 A.
Recheck the DC output voltage. It should remain the same as measured in step 4 of the Power Up
Test.
NOTE
If discharged batteries are installed, all bargraphs may be illuminated on the rectifiers during the
charge test. This indicates that the rectifiers are at full capacity and are rapidly charging the batteries. It
is recommended in this case that the batteries are allowed to charge and stabilize as in the above step
before commissioning the site. This could take several hours.
2-14
SEP 2009
continued
Figure 2-7: Battery Circuit Breakers
2
OUT=OFF
(Side View)
IN=ON
10mm
Hex Nut
(Front View)
M6 Screw
Battery Tray Circuit Breaker

Batteries
Power Cabinet Front View
Discharge Test
Perform the test procedure in Table 2-9 only when the battery current is
less than 5 Amp per string. Refer to Table 2-8 for the procedures to
check current levels.
Table 2-9: Battery Discharge Test
Step
Action
Turn the battery test switch on the Meter Alarm Panel, ON (see Figure 2-4). The rectifier output
voltage and current should decrease by approximately 10% as the batteries assume the load. Alarms
for the Meter Alarm Panel may occur.
Measure the individual battery string current using the DC current probe. The battery discharge current
in each string should be approximately the same (within 5 A).
Turn Battery Test Switch OFF.
CAUTION
Failure to turn OFF the Battery Test Switch before leaving
the site, will result in low battery capacity and reduce
battery life.
SEP 2009
2-15
Heat Exchanger Power Up

Heat Exchanger Power Up
Table 2-10: Heat Exchanger Power Up
2
Step
Action
Turn the Power Cabinet Heat Exchanger breakers ON (see Figure 2-8 for breaker location).
The Heat Exchanger will now go into a five (5) minute test sequence. Ensure that the internal and
external fans are operating. Place a hand on the internal and external Heat Exchanger grills to feel for
air draft.
Figure 2-8: Heat Exchanger Blower Assembly

Heat Exchanger
Assembly
Bottom (Ambient) Blower

Mounting
Bracket
Fan Module
Top (Internal) Blower

Blower
Power
Cord
Core
Mounting
Bracket
Fan Module
T30 Screw
Blower
Power
Cord
T30 Screw
Power Cabinet
Front View
OUT=OFF
IN=ON
Blower Assembly
Circuit Breaker
Side View
2-16
FW00181
SEP 2009
Circuit Breaker Locations

The following illustrations show the location of various circuit breakers
in the BTS power cabinet.
SEP 2009
2-17
continued
Figure 2-9: Power Cabinet Circuit Breaker Assemblies
DC Circuit
Breaker
25
160
160
160
25
ON
OFF
BREAKER SYSTEM BREAKER

SHOULD BE RESET
IF ILLUMINATED OR
AFTER RESET OF
BREAKER SYSTEM
3 MAIN BREAKERS
BREAKER
SYSTEM RESET
BUTTON
TO RESET MAIN BREAKERS, PRESS

AND HOLD IN GREEN BUTTON WHILE
PRESSING 160 AMP BREAKER BUTTON
UNTIL LATCHED RELEASE GREEN BUTTON
AFTER ALL 3 BREAKERS HAVE BEEN RESET
Power Cabinet
Front View
ATTENTION
RECTIFIER
SHELF #1
2
Circuit Breaker Legend:
1.
2.
3.
4.
5.
6.
7.
Main . . . . . . . . . . . . . . .
Rectifier Shelf #1 . . . .
Rectifier Shelf #2 . . . .
Battery Heater #1 . . . .
Battery Heater #2 . . . .
GFCI . . . . . . . . . . . . . . .
Spare . . . . . . . . . . . . . .
RECTIFIER
SHELF #2
3
150 Amp
70 Amp
70 Amp
15 Amp
15 Amp
15 Amp
15 Amp
BATTERY
HEATER #1
4
1
CAUTION
MAIN
BATTERY
HEATER #2
LIVE TERMINALS
GFCI
SPARE
LED Status
AC Circuit
Breaker
FW00144
2-18
SEP 2009
continued
Figure 2-10: Power Cabinet AC Circuit Breakers
7/16 Nut
AC Circuit Breaker
150 Amp Breaker
Power Cabinet
Front View
5/16 Nut
Screw
Wire
Left Tab
15 Amp Breaker
Right Tab
Screw
5/16 Nut
Wire
Wire
Left Tabs
30 Thru 140 Amp Breaker
Right Tabs
FW00145
SEP 2009
2-19
continued
Figure 2-11: Power Cabinet DC Circuit Breakers
DC Circuit Breaker
9/32 Nut
15 AMP
Power Cabinet
Front View
3x150 AMP
DC Power
Panel Door
Locks
FW00146
2-20
Flat Washer
Lock Washer
17 mm Nut
SEP 2009
Chapter 3: Optimization/Calibration
Table of Contents
3
SEP 2009
Introduction to Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibration Process Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell-site Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Equipage Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1
3-1
3-1
3-2
3-2
3-3
3-3
Preparing the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Packet BTS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LMF File Structure Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LMF Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Filename Conventions and Directory Location . . . . . . . . . . . . . . . . . . .
LMF Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copy NEC Files to the LMF Computer . . . . . . . . . . . . . . . . . . . . . . . .
3-5
3-5
3-5
3-6
3-7
3-7
3-8
3-9
Prepare the LMF Computer for MMI Communication . . . . . . . . . . . . . . . . . . .

Named HyperTerminal Connection for MMI Sessions . . . . . . . . . . . . .
Terminal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-12
3-12
3-12
Optional Channel Service Units (CSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configure Channel Service Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-15
3-15
Punchblocks and Pin/Signal Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-17
LMF to BTS Connection Service Shelf Connection . . . . . . . . . . . . . . . . . . . .

Connect the LMF to the BTS at the Service Shelf . . . . . . . . . . . . . . . .
3-23
3-23
Using the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic LMF Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The LMF Display and the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Graphical User Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding GUI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Line Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logging into a BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-25
3-25
3-26
3-26
3-26
3-31
3-32
3-36
Establishing an MMI Communication Session . . . . . . . . . . . . . . . . . . . . . . . . .

Establishing an MMI Communication Session . . . . . . . . . . . . . . . . . . .
3-38
3-38
LMF Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-40
3-40
Table of Contents
continued
Pinging the Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pinging the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-41
3-41
Take Control of Packet BTS Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet BTS Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Taking Control of Packet BTS Resources . . . . . . . . . . . . . . . . . . . . . . .
3-45
3-45
3-45
Download the BTS General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RAM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-47
3-47
3-47
3-47
Download BTS Loading Packet GLI Devices . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading code to packet GLI3 card . . . . . . . . . . . . . . . . . . . . . . . .
3-49
3-49
3-49
Download BTS Loading NonGLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . .

Download Code and Data to NonGLI Devices . . . . . . . . . . . . . . . . . .
3-52
3-52
Enabling Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selecting the CSM Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable CSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable MCCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-55
3-55
3-56
3-58
CSM System Time GPS, LFR, and HSO/MSO Verification . . . . . . . . . . . . .

Clock Synchronization Manager (CSM) Subsystem Description . . . .
Front Panel LED and Status Displays . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup Timing Reference Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSM Frequency Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Equipment Setup for
GPS and LFR/HSO/MSO/QHSO Verification . . . . . . . . . . . . . . . . . . .
GPS and HSO/MSO/QHSO Initialization/Verification . . . . . . . . . . . . .
Loran Initialization/Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-59
3-59
3-60
3-61
3-63
3-63
3-64
3-70
Test Equipment Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting Test Equipment to the BTS . . . . . . . . . . . . . . . . . . . . . . . .
Test Equipment GPIB Address Settings . . . . . . . . . . . . . . . . . . . . . . . .
Supported Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Equipment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Equipment Connection Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Warm-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic Cable Calibration Setup . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set-up for TX Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setup for ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-72
3-72
3-72
3-73
3-73
3-74
3-78
3-78
3-78
3-79
3-84
Test Equipment Connection to the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Addressing Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-93
3-93
3-95
Test Equipment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Equipment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual and Autodetect Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-96
3-96
3-96
3-96
3-96
SEP 2009
Table of Contents
SEP 2009
continued
Test Set Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Set Calibration Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibration Procedures Included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibrate Test Equipment Function (Except Agilent E4406A and
Anritsu MT8212B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibrating the Anritsu MT8212B . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-104
3-105
Setting and Editing Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . .

Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-109
3-109
Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibrating Cables Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Calibration Setup Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibrate Test Cabling Using Communications System Analyzer . . . .
Calibrate Test Cabling Using Signal Generator &
Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Cable Loss Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Coupler Loss Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-111
3-111
3-112
3-112
3-118
3-121
3-122
Bay Level Offset Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purpose of Bay Level Offset Calibration . . . . . . . . . . . . . . . . . . . . . . . .
What is BLO Calibration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
When to Calibrate BLOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX Path Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BLO Calibration Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Equipment Setup for RF Path Calibration . . . . . . . . . . . . . . . . . .
Transmit (TX) Path Calibration Description . . . . . . . . . . . . . . . . . . . . .
TX Calibration and the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-123
3-123
3-123
3-124
3-124
3-125
3-128
3-129
3-129
TX BLO Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All Cal/Audit and TX Calibration Procedure . . . . . . . . . . . . . . . . . . . .
3-131
3-131
3-131
Download BLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-134
TX Calibration Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX Audit Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-135
3-135
3-135
Create CAL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-136
RFDS Setup and Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RFDS Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RFDS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking and Setting RFDS Parameters . . . . . . . . . . . . . . . . . . . . . . . .
RFDS TSU NAM Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Explanation of Parameters Used When Programming the
TSU NAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Valid NAM Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Antenna Map Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set RFDS Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RFDS Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Program TSU NAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-137
3-137
3-137
3-138
3-140
3-141
3-142
3-143
3-144
3-145
3-147
Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration . .

CRMS Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-148
3-148
3-103
3-103
3-104
Table of Contents
continued
Alarms Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarms Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Reporting Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Testing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heat Exchanger Alarm Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Door Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AC Fail Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Minor Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rectifier Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Battery Over Temperature Alarm (Optional) . . . . . . . . . . . . . . . . . . . . .
Rectifier Over Temperature Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before Leaving the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-149
3-149
3-149
3-150
3-150
3-150
3-151
3-151
3-152
3-154
3-156
3-157
SEP 2009
Introduction to Calibration
Overview
This section describes procedures for isolating the BTS from the span
lines, preparing and using the LMF, downloading BTS software, CSM
reference verification/optimization, set up and calibration of the
supported test equipment, transmit/receive path verification, using the
RFDS/CRMS, and verifying the customer defined alarms and relay
contacts are functioning properly.
NOTE
Before using the LMF, use an editor to view the
CAVEATS section in the readme.txt file in the c:\wlmf
folder for any applicable information.
Calibration Process Summary
After a BTS is physically installed and the preliminary operations, such

as power up, have been completed, the LMF is used to calibrate the
BTS. Companion frames must be optimized individually as separate
BTSs. The basic calibration process consists of the following:
1. Download GLI 1 with code and data and then enable GLI 1.
NOTE
GLIs must be GLI3 cards.
2. Use the status function and verify that all of the installed devices of
the following types respond with status information: CSM, BBX,
GLI, and MCC (and TSU if RFDS is installed). If a device is
installed and powered up but is not responding and is colored gray in
the BTS display, the device is not listed in the NEC files. The NEC
files must be corrected before the device can be accessed by the
LMF.
3. Download code and data to all devices of the following types:
CSM
BBX (BBX1X)
GLI (other than GLI 1)
MCC1X
4. Download the RFDS TSIC (if installed).
5. Verify the operation of the GPS and QHSO, HSO, MSO, or LFR
signals.
6. Enable the following devices (in the order listed):
Secondary CSM (slot 2)
Primary CSM (slot 1)
All MCCs
SEP 2009
3-1
continued
7. Connect the required test equipment for a full optimization.

8. Select the test equipment using the LMF.
9. Calibrate the TX and RX test cables if they have not previously been
calibrated using the CDMA LMF that is going to be used for the
optimization/calibration. The cable calibration values can also be
entered manually.
10. Select all of the BBXs and all of the MCCs and use the full
optimization function. The full optimization function performs TX
calibration, BLO download, TX audit, all TX tests, and all RX tests
for all selected devices.
11. If the TX calibration fails, repeat the full optimization for any failed
paths.
12. If the TX calibration fails again, troubleshoot and correct the
problem that caused the failure and repeat the full optimization for
the failed path.
13. If the TX calibration and audit portion of the full optimization passes
for a path but some of the TX or RX tests fail, correct the problem
that caused the failure and run the individual tests as required until
all TX and RX tests have passed for all paths.
Cell-site Types
Sites are configured as Omni/Omni or Sector/Sector (TX/RX). Each type

has unique characteristics and must be optimized accordingly.
NOTE
For more information on the different in site types, please
refer to the applicable BTS hardware installation manual.
Configuration Files
The Network Element Configuration (NEC) files contain information

that defines the BTS and data used to download files to the devices. The
NEC Base (NECB NECB*bts#.xml) and NEC Journaling (NECJ
NECJ*bts#.xml) files are used by packet BTSs. NEC files must be
placed in the applicable BTS folder before the LMF can be used to log
into that BTS. NEC files can be obtained from the OMCR using a
floppy disk. A file transfer protocol (ftp) method can be used if the LMF
computer has that capability.
The NEC files include the following information:
S Download instructions and protocol

S Site specific equipage information
S CCCP shelf allocation plan
BBX equipage (based on cellsite type) including redundancy
CSM equipage including redundancy
3-2
SEP 2009
continued
MCC (MCC1X and/or MCCDO) channel element allocation plan.

This plan indicates how the CCCP shelf is configured, and how
the paging, synchronization, traffic, and access channel elements
(and associated gain values) are assigned among the (up to 12)
MCCs in the shelf.
S CSM equipage including redundancy
S HSO equipage whenever either an HSO, QHSO, or MSO backup
timing reference source card is installed in the BTS.
S Effective Rated Power (ERP) table for all TX channels to antennas
respectively. Motorola System Engineering specifies the ERP of a
transmit antenna based on site geography, antenna placement, and
government regulations. Working from this ERP requirement, the
antenna gain, (dependent on the units of measurement specified) and
antenna feed line loss can be combined to determine the required
power at the top of the BTS frame. The corresponding BBX output
level required to achieve that power level on any channel/sector can
also be determined.
NOTE
Refer to the LMF Help function online documentation
(part of the LMF software application) for additional
information on the layout of the LMF directory structure
(including NEC file location and format).
BTS Software Download
BTS software must be successfully downloaded to the BTS processor

boards before optimization can be performed. BTS operating code is
loaded from the LMF computer terminal.
CAUTION
Before using the LMF for calibration or acceptance testing,
the correct NECB*bts#.xml and NECJ*bts#.xml files
for the BTS must be obtained from the OMCR and put in
a bts# folder in the LMF. Failure to use the correct NEC
files can cause improper or unpredictable BTS operation.
Failure to use the correct NEC files to log into a live
(traffic carrying) site can shut down the site.
The NEC files are normally obtained from the OMCR on a DOS
formatted diskette, or through a file transfer protocol (ftp) if the LMF
computer has ftp capability. Refer to the LMF Help function online
documentation (part of the LMF software application) for the procedure.
Site Equipage Verification
If it has not already done, use an editor to view the NEC files, and
review the site documentation. Verify the site engineering equipage data
in the NEC files matches the actual site hardware using a NEC file
conversion table.
SEP 2009
3-3
continued
CAUTION
Use extreme care not to make any changes to the NEC file
content while viewing the file. Changes to the NEC file
can cause the site to operate unreliably or render it
incapable of operation.
3-4
SEP 2009
Preparing the LMF

Preparing the LMF
Overview
Before optimization can be performed, the LMF application software

must be installed and configured on a computer platform meeting
Motorolaspecified requirements (see Recommended Test Equipment
and Software in Chapter 1).
Software and files for installation and updating of the LMF are provided
on CD ROM disks. The following installation items must be available:
S LMF Program on CD ROM
S NEC files for each supported BTS (on diskette or available from the
OMCR)
The following section provides information and instructions for
installing and updating the LMF software and files.
Overview of Packet BTS files
R16.0 and earlier software releases used the CDF configuration file for
each BTS and CBSC supported by the LMF. In a packet BTS operating
with Software Release 16.1 or later, the CDF is replaced by the NEC
files. There are two NEC files. These are:
S NEC Base (NECB) file
S NEC Journal (NECJ) file
The NECB contains the baseline configuration information and is
analogous to the CDF, while the NECJ contains all the changes made to
the configuration since the last time the NECB was regenerated. Once
the NECJ reaches 80% of its maximum size, the NECB is regenerated
by the OMCR, and all updates from the NECJ file are rolled into it.
The NEC files play much more extensive role than the previouslyused
CDF files.
Additional important, LMFrelated facts about the the NEC files are:
S Both files (NECB and NECJ) are in eXtensible Markup Language

S
S
S
S
SEP 2009
(XML) format.
NECB contains all the up-to-date static configuration information and
NECJ contains all the recent changes (including operations) which are
not updated in the NECB.
Both files can be viewed in any XML viewer (most easily available is
Internet Explorer V5.0 and higher). They can be also viewed by any
other word or text processor, but the XML tags will also be seen when
using these types of applications.
These files will be created by OMCR from MIB and reflect the BTS
provisioning.
These files will be regenerated for each software release upgrade on
the system for each BTS.
Unlike the CDF file, the NEC files will reside on both OMCR and
GLI3s operating in packet mode. The NEC files will be synchronized
periodically between the OMCR and GLI3s in each BTS.
3-5
Preparing the LMF
continued
S Both the NECB and NECJ files contain a SoftwareVersion field in

their header section indicating the system release version of these
files.
S Instead of the bts#.cdf file, the packet LMF uses
NECB*bts#.xml and NECJ*bts#.xml files, which are copies of the
NEC files.
S A GLI3 operating in packet mode will need the NECB and NECJ files
for site initialization.
S The scope of the NEC files has grown much broader than that of the
CDF and has much more BTScentric information. This is principally

because the role of the GLI card has expanded significantly with the
introduction of the GLI3 card and packet backhaul.
CAUTION
Never use a generic NEC file. The specific, siteunique
information for the BTS must be included in the NEC file
for the site to operate properly.
LMF File Structure Overview
The LMF uses a <x>:\lmf home directory> folder that contains all of the
essential data for installing and maintaining the BTS. The following list
outlines the folder structure for LMF. Except for the bts# folders, these
folders are created as part of the the LMF installation. Refer to the
CDMA LMF Operators Guide for a complete description of the folder
structure.
Figure 3-1: LMF Folder Structure
(C:)
x:\<lmf home directory> folder
cdma folder
bts# folders (A separate folder is required
for each BTS where bts# is the unique BTS
number; for example, bts163.)
loads folder
version folder (A separate folder is
required for each different version; for
example, a folder name 2.8.1.1.1.5.)
code folder
data folder
3-6
SEP 2009
Preparing the LMF
continued
NOTE
The loads folder and all the folders below it are not
available from the LMF for Software Release 2.16.4.1.
These folders may be present as as a legacy from previous
software versions or downloaded from the OMCR.
Users will need to manually add the directories to a newly
installed LMF when they add the code loads to be
downloaded.
LMF Home Directory
The CDMA LMF installation program creates the default home

directory, c:\wlmf, and installs the application files and subdirectories
(folders) in it. Because this can be changed at installation, the CDMA
LMF home directory will be referred to with the generic convention of:
<x>:\<lmf home directory>
Where:
<x> = the LMF computer drive letter where the CDMA LMF home
directory is located.
<lmf home directory> = the directory path or name where the CDMA
LMF is installed.
Filename Conventions and
Directory Location
NEC Files
The naming conventions for the NECB and NECJ files are:
NECB*bts#.xml
NECJ*bts#.xmlNECJ*bts#.xml
Where:
* = any characters can be substituted
# = the actual integer BTS number; for example,
NECB2.16.4.1.40bts480.xml
The NECB and its corresponding NECJ must have the exact same name,
except for the B and J after the initial NEC characters.
The NECB and the NECJ must reside in the
<LMF_HOME>\cdma\bts# directory for the BTS to which they apply.
Load Information File (LIF)
The LIF is used for packet BTS. It contains all the devices binaries
available for the specified System Software Release. It is the functional
equivalent of the Object List File (OLF) file that was used prePacket.
SEP 2009
3-7
Preparing the LMF
continued
The naming convention for the LIF is:

NE_LIF.xml
The LIF must be placed in the
<x>:\lmf home directory>\cdma\loads\<software_release#> directory;
for example, c:\wlmf\cdma\loads\2.17.0.10.
The LIF can be obtained from the OMCR directory
/screl/<software_release#>/loadable/bts
Cal File
The Cal File still resides in the <LMF_HOME>\cdma\bts# directory
and is named bts#.cal, where # is the actual integer number of the
BTS.
LMF Application Installation
This section provides information and instructions for installing and

updating the LMF software and files.
NOTE
First Time Installation Sequence:
1. Install Java Runtime Environment (JRE)
2. Install U/WIN Kshell emulator
3. Install LMF application programs
4. Install/create BTS folders
NOTE
Any time U/WIN is installed, the LMF application
software must also be installed. This is because the LMF
application installation modifies some of the files that are
installed during the U/Win installation. These
modifications are necessary for proper LMF operation.
Installing U/Win overwrites these modifications.
There are multiple binary image packages for installation
on the CDROM. When prompted, choose the load that
corresponds to the software release currently installed in
the network. Perform the Device Images installation after
the LMF installation.
If applicable, a separate CD ROM of BTS Binaries may be
available for binary updates.
Follow the procedure in Table 3-1 to install the LMF application

program using the LMF CD ROM.
3-8
SEP 2009
Preparing the LMF
continued
Table 3-1: LMF Application Program Installation

n Step
Action
Insert the LMF Program CD ROM into the LMF CD ROM drive.
If the Setup screen appears, follow the instructions displayed on the screen.
If the Setup screen is not displayed, proceed to Step 4.
Click on the Start button.
Select Run.
Enter d:\autorun In the Open box and click OK.
NOTE
If applicable, replace the letter d with the correct CD ROM drive letter.
Copy NEC Files to the LMF

Computer
Before logging on to a BTS with the LMF computer to execute

optimization/ATP procedures, the correct NECB*bts#.xml and
NECJ*bts#.xml files must be obtained from the OMCR and put in a
bts-# folder in the LMF computer. This requires downloading the files
using File Transfer Protocol (FTP) or creating versions of the OMCR
NEC files on a DOSformatted floppy diskette and using the diskette to
install the NEC files on the LMF computer.
NOTE
S If a network connection is available, the ftp method can

be used to copy the NEC files from the OMCR.
S On Sun OS workstations, the unix2dos command can
be used in place of the cp command (for example,

unix2dos NECB2.21.0.0.9bts248.xml
NECB2.21.0.0.9bts248.xml). This should be done
using a copy of the OMCR NEC files so the original
OMCR NEC files are not changed to DOS format.
NOTE
When copying NEC files, be sure the numbers used in the
NECB*bts#.xml and NECJ*bts#.xml filenames
correspond to the locally assigned numbers for each BTS
and its controlling OMCR. This will prevent BTS login
problems with the LMF.
SEP 2009
3-9
Preparing the LMF
continued
The procedure in Table 3-2 lists the steps required to transfer the NEC
files from the OMCR to the LMF computer using a floppy diskette. For
further information, refer to the LMF Help function on line
documentation.
Table 3-2: Copying NEC Files to the LMF Computer
n Step
Action
AT THE OMCR:
Start a Command Line Interface (CLI) session and log in.
Insert a DOS formatted diskette in the workstation drive.
Type eject q and press the <Enter> key.
Type mount and press the <Enter> key.
NOTE
S Look for the floppy/no_name message on the last line displayed.
S If the eject command was previously entered, floppy/no_name will be appended with a
number. Use the explicit floppy/no_name reference displayed when performing step 7.
Change to the directory containing the file by typing cd <directory name> (ex. cd
bts248) and pressing <Enter>.
Type ls <Enter> to display the list of files in the directory.
With Solaris versions of Unix, create DOSformatted versions of the NECB*bts#.xml and
NECJ*bts#.xml files on the diskette by entering the following command:
unix2dos <source filename> /floppy/no_name/<target filename>
For example, unix2dos
NECB2.12.4.41bts248.xml
/floppy/no_name/
NECB2.12.4.41bts248.xml .
NOTE
S Other versions of Unix do not support the unix2dos and dos2unix commands. In these cases,
use the Unix cp (copy) command. The copied files will be difficult to read with a DOS or
Windows text editor because Unix files do not contain line feed characters. Editing copied NEC
files on the LMF computer is, therefore, not recommended.
S Using cp, multiple files can be copied in one operation by separating each filename to be copied
with a space and ensuring the destination directory (floppy/no_name) is listed at the end of the
command string following a space (for example,
cp NECB2.21.4.41bts248.xml NECJ2.21.4.41bts248.xml /floppy/no_name).
Repeat steps 5 through 7 for each bts# that must be supported by the LMF.
When all required files have been copied to the diskette, type eject and press the <Enter> key.
10
Remove the diskette from the workstation drive.

3-10
SEP 2009
Preparing the LMF
continued
Table 3-2: Copying NEC Files to the LMF Computer

n Step
Action
ON THE LMF COMPUTER:
11
Start the Windows operating system.
12
Insert the diskette into the LMF.
13
Using Windows Explorer (or equivalent program), create a corresponding bts# folder in the
<lmf home directory>\cdma directory for each NECB*bts#.xml and NECJ*bts#.xml file pair
copied from the OMCR.
14
Use Windows Explorer (or equivalent program) to transfer the NECB*bts#.xml and
NECJ*bts#.xml files from the diskette to the corresponding <lmf home directory>\cdma\bts#
folders created in step 13.
SEP 2009
3-11
Prepare the LMF Computer for MMI Communication

Named HyperTerminal
Connection for MMI Sessions
General Confirming or changing the configuration data of External

BTS Routers (EBR) and certain BTS Field Replaceable Units (FRU)
requires establishing a ManMachine Interface (MMI) communication
session between the LMF and the FRU or EBR. Using features of the
Windows operating system, the connection properties for an MMI
session can be saved on the LMF computer as a named HyperTerminal
connection. This eliminates the need for setting up connection
parameters each time an MMI session is required to support operations.
Desktop Shortcut Once the named connection is saved, a shortcut for

it can be created on the Windows operating system desktop. Double
clicking the shortcut icon will start the connection without the need to
negotiate multiple menu levels.
Terminal Settings
Perform the following to create a named HyperTerminal connection for

FRU or EBR MMI interface and generate a Windows operating system
desktop shortcut for it.
NOTE
There are differences between Windows 2000 and Windows
XP operating systems in the menus and screens used for
creating a HyperTerminal connection. In the following
procedure, items applicable only to the:
S Windows 2000 operating system will be identified with
Win2000)
S Windows XP operating system will be identified with

WinXP
3-12
SEP 2009
continued
Table 3-3: Establish HyperTerminal Connection

Step
Action
From the Windows operating system Start menu, select:

Programs > Accessories
Perform one of the following:
S For Win2000, select Hyperterminal and then click on HyperTerminal

S For WinXP, select Communications and then click on the HyperTerminal icon.
NOTE
S If a Location Information Window appears, enter the required information, then click on the
Close button. (This is required the first time a HyperTerminal connection is configured, even if a
modem is not to be used.)
S If a You need to install a modem..... message appears, click on NO.

3
When the Connection Description box opens:

Type a name for the connection being defined (for example, BTSRTR Session, MMI) in the
Name: window,
Highlight any icon preferred for the named connection in the Icon: chooser window, and
Click OK.
From the Connect using: pick list in the Connect To box displayed, select the RS232 port to be
used for the connection (e.g., COM1 or COM2), and click OK.
In the Port Settings tab of the COM# Properties window displayed, configure the RS232 port
settings as follows:
S
S
S
S
S
Bits per second: 9600

Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Click OK.
With the HyperTerminal window still open and the connection running, select:
File > Properties
Click the Settings tab, click the arrow in the Emulation window, and select VT100 from the
dropdown list.
Click the ASCII Setup button, uncheck all boxes in the ASCII Setup window which appears, and
click OK.
10
Click OK for the connection Properties box.
11
Save the defined connection by selecting:

File > Save
SEP 2009
3-13
continued
Table 3-3: Establish HyperTerminal Connection

Step
Action
12
Close the HyperTerminal window by selecting:

File > Exit
13
Click the Yes button to disconnect when prompted.
14
From the Windows operating system Start menu, select Programs > Accessories
15
S For Win2000, select Hyperterminal and release any pressed mouse buttons.
S For WinXP, select Communications and double click the Hyperterminal folder.
16
Move the cursor over the newlycreated connection icon.
17
Right click and drag the connection icon to the Windows operating system desktop and release the
right mouse button.
18
From the popup menu displayed, select one of the following depending on the operating system used:
S Win2000: Create Shortcut(s) Here

S WinXP: Copy Here
19
If desired, reposition the shortcut icon for the new connection by dragging it to another location on the
Windows operating system desktop.
NOTE
The shortcut icon can now be doubleclicked to open a BTS router or BTS card/module MMI
HyperTerminal session without the need to negotiate multiple menu levels.
20
In WinXP, select File > Close to close the HyperTerminal window.
3-14
SEP 2009
Optional Channel Service Units (CSU)

Configure Channel Service Unit
The MPATH 537 Channel Service Unit (CSU) provides inband

SNMPmanaged digital service access to T1 and fractional T1 lines.
MPATH units plug into the Kentrox 2slot frame (see Figure 3-2).
Remote MPATH management is available via SNMP over an inband
data link on the T1 line (using a facility data link or 864 kbps of a DS0
channel). The unit at the near end of the management path can be an
SNMP manager or another MPATH CSU.
Each 19 inch rack can support two CSU MPATH 537 modules. Each
MPATH 537 module supports one and only one span connection.
Programming of the MPATH is accomplished through the DCE 9pin
connector on the front panel of the CSU shelf. Manuals and a Microsoft
Windows programming disk is supplied with each unit.
Setting the Control Port
Whichever control port is chosen, it must first be set up so the control
port switches match the communication parameters being used by the
control device. If using the rearpanel DTE control port, set the
shelfaddress switch SA5 to up (leave the switch down for the
rearpanel DCE control port).
For more information, refer to the vendor user manual (part number
1174139) and installation manual (part number 1174462) provided with
each CSU.
Plug one of the cables listed below into the Control Port connectors:
Part Number
Description of Cable
0195006022 (six feet)
DB9S to DB9P
0195010022 (ten feet)

The control port cables can be used to connect the shelf to:
S A PC using the AT 9pin interface

S A modem using the 9pin connector
S Other shelves in a daisy chain
SEP 2009
3-15
continued
Figure 3-2: Rear and Front View of the CSU

To/From
Network
DTE
T1
To/From
Network
To/From
GLI
DDS
SLOT 2
To/From
GLI
DATA PORT
T1 TERMINAL
DCE
T1
NETWORK
DDS
SLOT 1
DATA PORT
T1 TERMINAL
NETWORK
CONTROL
PORT
GROUP
ADDRESS
SHELF
ADDRESS
Rear View
SLOT 1
DCE Connector
(Craft Port)
SLOT 2
Front View
REF. FW00212
CAUTION
SC4812ET Span Line Labeling for Span B and Span C
may be swapped.
S On the SC4812ETs, the span cable internal to the base
station that connects the 50 pin header on the I/O plate
to the CSU has Span B and Span C (RJ45) connectors
mislabeled.
S CFE will punch down the span on the 50 pair
punchblock as per Motorola documentation and

punchdown chart. When conecting the span input to the
CSU relabel Span B cable to Span C cable, and
Span C cable to Span B. Connect to CSU as per
documentation.
NOTE
The labeling issue on the cable from the I/O plate to the
CSU Part Number 3086601H01 Rev C shall be corrected
on revision D to address this issue. The cut over date to
Rev. D was approximately January 30, 2001.
3-16
SEP 2009
Punchblocks and Pin/Signal Information

See Figure 3-3 and refer to Table 3-4 for the physical location and pin
callout information for the 50pin punch block.
Figure 3-3: 50 Pair Punch Block
3
TO MODEM
CONNECTOR TO ALARMS
CONNECTOR
STRAIN RELIEVE INCOMING

CABLE TO BRACKET WITH
TIE WRAPS
TO LAN
CONNECTOR
RF CABINET I/O AREA

TO RGD/RGPS
CONNECTOR
LEGEN
D
1T = PAIR 1 TIP
1R = PAIR 1 RING
2R
2T
1R
1T
2
49T
1T 1R 2T 2R
49R
50T
50R
FW00162
TOP VIEW OF PUNCH BLOCK

SEP 2009
3-17
continued
Table 3-4 lists the complete pin/signal identification for the 50pin
punch block.
Table 3-4: PinOut for 50Pair Punchblock
Punchblock Cable
Connector
Function
Power Cabinet
ALARM
HSO/LFR
Extension
LFR Antenna
Pilot Beacon
Signal Name
Punch
Pin
Ext. Cable
Wire Color
Power Cab Control NC
1T
Blue
Power Cab Control NO
1R
Blk/Blue
Power Cab ControlCom
2T
Yellow
Reserved
2R
N/C
Rectifier Fail
3T
Blk/Yellow
AC Fail
3R
Green
Power Cab Exchanger Fail
4T
Blk/Grn
Power Cab Door Alarm
4R
White
Power Cab Major Alarm
5T
Blk/White
Battery Over Temp
5R
Red
Power Cab Minor Alarm
6T
Blk/Red
Rectifier Over Temp
6R
Brown
Power Cab Alarm Rtn
7T
Blk/Brn
LFR_HSO_GND
7R
EXT_1PPS_POS
8T
EXT_1PPS_NEG
8R
CAL_+
9T
CAB_
9R
LORAN_+
10T
LORAN_
10R
Pilot Beacon Alarm Minor
11T
Pilot Beacon Alarm Rtn
11R
Pilot Beacon Alarm Major
12T
Pilot Beacon ControlNO
12R
Pilot Beacon Control COM
13T
Pilot Beacon Control NC
13R
3-18
SEP 2009
continued

Punchblock Cable
Connector
ALARM
ALARM
Function
Customer Outputs
Customer Inputs
Signal Name
Punch
Pin
Customer Outputs 1 NO
14T
Customer Outputs 1 COM
14R
14T
14R
Customer Outputs 1 NC
15T
15R
16T
16R
17T
17R
18T
18R
Customer Outputs 4COM
19T
19R
Customer Inputs 1
20T
Cust_Rtn_A_1
20R
Customer Inputs 2
21T
Cust_Rtn_A_2
21R
Customer Inputs 3
22T
Cust_Rtn_A_3
22R
Customer Inputs 4
23T
Ext. Cable
Wire Color
SEP 2009
3-19
continued

Punchblock Cable
Connector
Function
ALARM
Customer Inputs
Span 1
Span 2
SPAN I/O
Span 3
Span 4
Signal Name
Punch
Pin
Cust_Rtn_A_4
23R
Customer Inputs 5
24T
Cust_Rtn_A_5
24R
Customer Inputs 6
25T
Cust_Rtn_A_6
25R
Customer Inputs 7
26T
Cust_Rtn_A_7
26R
Customer Inputs 8
27T
Cust_Rtn_A_8
27R
Customer Inputs 9
28T
Cust_Rtn_A_9
28R
Customer Inputs 10
29T
Cust_Rtn_A_10
29R
RCV_TIP_A
30T
RCV_RING_A
30R
XMIT_TIP_A
31T
XMIT_RING_A
31R
RCV_TIP_B
32T
RCV_RING_B
32R
XMIT_TIP_B
33T
XMIT_RING_B
33R
RCV_TIP_C (Note)
34T
RCV_RING_C (Note)
34R
XMIT_TIP_C (Note)
35T
XMIT_RING_C(Note)
35R
RCV_TIP_D (Note)
36T
RCV_RING_D (Note)
36R
XMIT_TIP_D (Note)
37T
Ext. Cable
Wire Color

3-20
SEP 2009
continued

Punchblock Cable
Connector
Function
Span 4
Span 5
SPAN I/O
Span 6
Signal Name
Punch
Pin
XMIT_RING_D(Note)
37R
RCV_TIP_E (Note)
38T
RCV_RING_E (Note)
38R
XMIT_TIP_E (Note)
39T
XMIT_RING_E(Note)
39R
RCV_TIP_F (Note)
40T
RCV_RING_F (Note)
40R
XMIT_TIP_F (Note)
41T
XMIT_RING_F(Note)
41R
Ext. Cable
Wire Color
NOTE
Span 3 through 6 are spares for expansion purposes
RGD/RGPS
For fframe
F
without RGD
Expansion
Punchblock
Single Frame
BTS;RGPS Head
Connection
OR
Multiple Frame
BTS RGD
BTS;
Connection at
RGPS Secondary
Frame
GPS_Power_A
42T
Yellow
GPS_Power_A_Return
42R
Yellow/Black
GPS_Power_B
43T
Blue
GPS_Power_B_Return
43R
Blue/Black
GPS_TXD+
44T
White
GPS_TXD
44R
White/Black
GPS_RXD+
45T
Green
GPS_RXD
45R
Green/Black
Signal Ground (TDR+)
46T
Red
Signal Ground (TDR)
46R
Red/Black
GPS_1PPS+
47T
Brown
GPS_1PPS
47R
Brown/Black
SEP 2009
3-21
continued

Punchblock Cable
Connector
Function
Signal Name
Punch
Pin
Ext. Cable
Wire Color
GPS_Power_A
42T
Yellow
GPS_Power_A_Return
42R
Yellow/Black
GPS_Power_B
43T
Blue
GPS_Power_B_Return
43R
Blue/Black
GPS_TXD+
44T
White
GPS_TXD
44R
White/Black
GPS_RXD+
45T
Green
GPS_RXD
45R
Green/Black
46T
Red
Master Frame (TDR)
46R
Red/Black
GPS_1PPS+
47T
Brown
GPS_1PPS
47R
Brown/Black
Reserved
48T
MODEM
Reserved
48R
RGD/RGPS
Chassis Ground
49T
N/A
None
No Connection
49R
None
Reserved
50T
None
Reserved
50R
None
RGD/RGPS
ALARM
3-22
For frame with

RGD Expansion
Punchblock
OR
M li l F
Multiple
Frame
BTS; RGPS Head
Connection at
RGPS Primary
Frame
SEP 2009
LMF to BTS Connection Service Shelf Connection

Connect the LMF to the BTS at
the Service Shelf
The LMF computer may be connected to the LAN A or B connector

located behind the frame lower air intake grill below the CCCP cage.
Figure 3-4, below, shows the general location of these connectors. LAN
A is considered the primary LAN.
Figure 3-4: Service Shelf LAN Connection
NOTE:
OPEN LAN CABLE ACCESS DOOR.
PULL APART HOOKANDLOOP
FABRIC AND GAIN ACCESS TO THE
LAN A OR LAN B LMF BNC
CONNECTOR.
LMF BNC T CONNECTIONS ON

LEFT SIDE OF FRAME
(ETHERNET A SHOWN;
ETHERNET B COVERED WITH
HOOKANDLOOP FABRIC)
ETIB
10BASETTO10BASE2
CONVERTER OR HUB CONNECTS
DIRECTLY TO LAN BNC T
LMF COMPUTER
TERMINAL WITH
MOUSE
SEP 2009
PCMCIA 10BASET
ETHERNET NETWORK
INTERFACE CARD (NIC)
UNSHIELDED TWISTED
PAIR (UTP) CABLE (RJ45
CONNECTORS)
EB
A
RFDS
115 VAC POWER

CONNECTION
(IF REQUIRED)
3-23
continued
Table 3-5: Connecting the LMF to the BTS, Service Shelf Connection
Step
Action
Open the LAN cable access door. (see Figure 3-4).
Pull apart the fabric covering one of the BNC T connectors.
! CAUTION
3
The outer conductor in the 10base2 LAN cabling is isolated from chassis ground. This conductor is
connected to the BNC connector shell. Do not allow the BTC T connectors to touch the chassis
during calibration.
3
Slide out the service shelf, if desired.
Connect the LMF computer to the BNC connector through an Ethernet Network Interface Card (NIC)
(internal or PCMCIA) and 10BaseTto10Base2 converter or hub.
NOTE
Xircom Model PE310B2 or equivalent can also be used to interface the LMF Ethernet connection to
the BTS frame connected to the PC parallel port, powered by an external AC/DC transformer. In this
case, the BNC cable must not exceed 91 cm (3 ft) in length.
3-24
SEP 2009
Using the LMF

Using the LMF
Basic LMF Operation
LMF Coverage in This Publication There are LMF application

programs to support maintenance of both CDMA and SAS BTSs. All
references to the LMF in this publication are for the CDMA application
program.
Operating Environments The LMF application program allows the
user to work in the two following operating environments which are
accessed using the specified desktop icons:
S Graphical User Interface (GUI) using the WinLMF icon
S Command Line Interface (CLI) using the WinLMF CLI icon
The GUI is the primary optimization and acceptance testing operating
environment. The CLI environment provides additional capability to the
user to perform manually controlled acceptance tests and audit the
results of optimization and calibration actions.
Basic Operation Basic operation of the LMF in either environment
includes performing the following:
S Selecting and deselecting BTS devices
S Enabling devices
S Disabling devices
S Resetting devices
S Obtaining device status
The following additional basic operation can be performed in a GUI
environment:
S Sorting a status report window
For detailed information on performing these and other LMF operations,
refer to the LMF Help function online documentation (part of the Local
Maintenance Facility (LMF) software application).
NOTE
Unless otherwise noted, LMF procedures in this manual
are performed using the GUI environment.
Online Help Task oriented online help is available in the LMF by
clicking on Help from the menu bar.
NOTE
When using the R17 and earlier LMF versions which use
JRE 1.4.1, a bug in this JRE version can cause the LMF to
become unresponsive when operating with some video
cards. See the Troubleshooting: Installation section of
Chapter 7 if this problem occurs.
SEP 2009
3-25
Using the LMF
continued
The LMF Display and the BTS
BTS Display When the LMF is logged into a BTS, a frame tab is
displayed for each BTS frames. The frame tab will be labeled with
CDMA and the BTS number, a dash, and the frame number (for
example, BTS8121 for BTS 812, RFMF 1). If there is only one frame
for the BTS, there will only be one tab.
NEC file Requirements For the LMF to recognize the devices
installed in the BTS, BTS NEC files which include equipage information
for all the devices in the BTS must be located in the applicable
<x>:\<lmf home directory>\cdma\bts# folder.
RFDS or CRMS Probe Display If an RFDS or CRMS Probe is

included in the NEC files, a tab labeled with RFDS, a dash, and the
BTS numberframe number combination (for example, RFDS8121)
will be displayed.
NOTE
The RFDS display is used for the CRMS models. CRMS
models are NOT shown or called out in the LMF screens.
Graphical User Interface

Overview
The LMF uses a Graphical User Interface (GUI), which supports the
following functions:
S Selecting a device or devices.

S Selecting an action to apply to selected device(s).
S Status report window displaying progress of actions taking place and
related information.
S Notification when an action is complete and related information such

as indication of success or failure
S An OK button to close the status report window.

Understanding GUI Operation
The following screen captures are provided to help understand how the
GUI operates:
Figure 3-5 shows the differences between packet and circuit BTS
representations on the LMF login screen. If there is a packet
configuration file (NEC) for the BTS, the (P) is added as a suffix
to the BTS number.
Figure 3-6 shows the Self-Managed Network Elements (NE) state
of a packetmode BTS (SC4812T shown). An X is displayed on
the front of each card that is under SelfManaged NE control by the
GLI3 card.
3-26
SEP 2009
Using the LMF
continued
Figure 3-7 shows three of the available packet mode commands.

Normally the GLI3 has Self-Managed NE control of all cards as
shown inFigure 3-7 identified with an X. In that state, the LMF
may only status a card. In order to download code or test a card, the
LMF must request Self-Managed NE control of the card by using
the dropdown menu shown. The LMF also uses this menu to release
control of the card back to the GLI3. The GLI3 will also assume
control of the cards after the LMF logs out of the BTS. The packet
mode GLI3 normally is loaded with a tape release and NECB and
NECJ files which point to a tape release stored on the GLI3. When
the GLI3 has control of a card it will maintain that card with the
code on that tape release.
Figure 3-8 depicts a packetmode BTS that has the MCC1 and the
BBX1 cards under LMF control. Notice that the X is missing
from the front of these two cards.
Figure 3-5: BTS Login screen identifying circuit and packet BTS files
For detailed information on performing these and other LMF operations,

refer to the LMF Help function online documentation (part of the Local
Maintenance Facility (LMF) software application).
SEP 2009
3-27
Using the LMF
continued
Figure 3-6: SelfManaged Network Elements (NEs) state of a packet mode BTS (SC4812T shown)
3-28
SEP 2009
Using the LMF
continued
Figure 3-7: Available packet mode commands
SEP 2009
3-29
Using the LMF
continued
Figure 3-8: Packet mode BTS with MCC2 and BBX2 under LMF control
3-30
SEP 2009
Using the LMF
continued
Command Line Interface

Overview
The LMF also provides Command Line Interface (CLI) capability.

Activate the CLI by clicking on a shortcut icon on the desktop. The CLI
cannot be launched from the GUI, only from the desktop icon.
Both the GUI and the CLI use a program known as the handler. The
LMF architectural design is such that only one handler can be running at
one time. Because of this in R19.0 and later, the GUI must be started
before the CLI if the GUI and CLI are to be used at the same time. When
the CLI is launched after the GUI, the CLI automatically finds and uses
an inprogress login session with a BTS initiated under the GUI. This
allows the use of the GUI and the CLI in the same BTS login session.
If a CLI handler is already running when the GUI is launched (this
happens if the CLI window is already open when the user starts the GUI)
or if the GUI is already running when the user starts a second GUI
instance, a dialog window displays the following warning message:
The CLI handler is already running.
This may cause conflicts with the LMF.
Are you sure that you want to start the application?
Yes
No
Selecting the yes button starts the application. Selecting the no button
terminates the application.
CLI Format Conventions
The CLI command can be broken down in the following way:
S
S
S
S
verb
device including device identifier parameters
switch
option parameters consisting of:
keywords
equals signs (=) between the keywords and the parameter values
parameter values
Spaces are required between the verb, device, switch, and option
parameters. A hyphen is required between the device and its identifiers.
Following is an example of a CLI command.
measure bbx<bts_id><bbx_id> rssi channel=6 sector=5
Refer to the LMF CLI Reference manual for a complete explanation of
the CLI commands and their use.
SEP 2009
3-31
Using the LMF
continued
Logging into a BTS
Logging into a BTS establishes a communications link between the BTS

and the LMF. An LMF session can be logged into only one BTS at a
time.
Prerequisites
Before attempting to log into the BTS,
Before attempting to login to a BTS, ensure the following have been

completed:
S
S
S
S
The LMF is properly connected to the BTS (see Figure 3-4).

The LMF application program is correctly installed and prepared.
A bts-# folder with the correct NEC files exists.
The LMF computer was connected to the BTS before starting the
Windows operating system and LMF software. If necessary, restart the
computer after connecting it to the BTS in accordance with Table 3-5.
NOTE
Be sure that the correct NECB*bts#.xml and
NECJ*bts#.xml files are used for the BTS. These should
be the NEC files that are provided for the BTS by the
OMCR. Failure to use the correct NEC files can result in
invalid optimization. Failure to use the correct NEC files
to log into a live (traffic carrying) site can shut down
the site.
3-32
SEP 2009
Using the LMF
continued
BTS Login from the GUI Environment

Follow the procedure in Table 3-6 to log into a BTS when using the GUI
environment.
Table 3-6: BTS GUI Login Procedure
n Step
1
Action
Start the LMF GUI environment by double clicking on the LMF desktop icon (if the LMF is not
running).
NOTE
If a warning similar to the following is displayed, select No, shut down other LMF sessions which
may be running, and start the LMF GUI environment again:
This may cause conflicts with the LMF
Are you sure you want to start the application?
Yes
No
Click on the Login tab (if not displayed).
If no base stations are displayed in the Available Base Stations pick list, double click on the
CDMA icon.
Click on the desired BTS number.
Click on the Network Login tab (if not already in the forefront).
Enter the correct IP address (normally 128.0.0.2 for a field BTS) if not correctly displayed in the
IP Address box.
NOTE
128.0.0.2 is the default IP address for the card in cage slot GLI 1 in field BTS units.
128.0.0.1 is the default IP address for the card in cage slot GLI 2.
7
Type in the correct IP Port number (normally 9216) if not correctly displayed in the IP Port box.
Click on Ping.
If the connection is successful, the Ping Display window shows text similar to the following:
Reply from 128 128.0.0.2: bytes=32 time=3ms TTL=255
If there is no response the following is displayed:

128.0.0.2:9216:Timed out
NOTE
If the GLI fails to respond, reset and perform the ping process again. If the GLI still fails to
respond, typical problems are shorted BNC to interframe cabling, open cables, crossed A and B
link cables, missing 50Ohm terminators, or the GLI itself.
SEP 2009
3-33
Using the LMF
continued
Table 3-6: BTS GUI Login Procedure

n Step
9
Action
Change the Multi-Channel Preselector (from the Multi-Channel Preselector pick list) selection,
normally MPC, to correspond to the BTS configuration, if required.
NOTE
When performing RX tests on expansion frames, do not choose EMPC if the test equipment is
connected to the starter frame.
3
NOTE
Use a Tower Top Amplifier is not applicable to the SC4812T, SC4812ET, SC4812ET Lite, SC4812TMC,
or SC4812T Lite BTS models.
10
Click on Login.
A BTS tab with a graphical representation of the BTS CCP cage is displayed.
NOTE
S If login is attempted to a BTS that is already logged on, all devices will be gray.
S For Software Release 2.16.4.0 and earlier, a Mode Selection box asking if the BTS is Trunked
or Multicarrier will pop up. Multicarrier must be selected for the SC4812TMC BTS.
S There may be instances where the BTS initiates a log out due to a system error (than is, a device
failure).
S If the GLI is OOS_ROM (blue), it will have to be downloaded with code before other devices
can be seen.
S If the GLI is OOS_RAM (yellow), it must be enabled before other installed devices can be seen.
3-34
SEP 2009
Using the LMF
continued
BTS Login from the CLI Environment

Follow the procedure in Table 3-7 to log into a BTS when using the CLI
environment.
NOTE
If the CLI and GUI environments are to be used at the
same time, the GUI must be started first and BTS login
must be performed from the GUI. Refer to Table 3-6 to
start the GUI environment and log into a BTS.
Table 3-7: BTS CLI Login Procedure

n Step
1
Action
Double click the LMF CLI desktop icon (if the LMF CLI environment is not already running).
NOTE
If a warning similar to the following is displayed, select No, shut down other LMF sessions which
may be running, and start the LMF CLI environment again:
This may cause conflicts with the LMF
Are you sure you want to start the application?
Yes
No
At the /wlmf prompt, enter the following command:

login bts<bts#> host=<host> port=<port>
where:
host = GLI card IP address (defaults to address last logged into for this BTS or 128.0.0.2 if this is
first login to this BTS).
port = IP port of the BTS (defaults to port last logged into for this BTS or 9216 if this is first login
to this BTS).
A response similar to the following will be displayed:
LMF>
13:08:18.882 Command Received and Accepted
COMMAND=login bts33
13:08:18.882 Command In Progress
13:08:21.275 Command Successfully Completed
REASON_CODE=No Reason
SEP 2009
3-35
Using the LMF
continued
Logging Out
Logging out of a BTS is accomplished differently for the GUI and the
CLI operating environments.
NOTE
The GUI and CLI environments use the same connection to
a BTS. If a GUI and the CLI session are running for the
same BTS at the same time, logging out of the BTS in
either environment will log out of it for both. When either
a login or logout is performed in the CLI window, there is
no GUI indication that logout has occurred.
Logging Out of a BTS from the GUI Environment

Follow the procedure in Table 3-8 to logout of a BTS when using the
GUI environment.
Table 3-8: BTS GUI Logout Procedure
n Step
Action
Click on BTS on the BTS tab menu bar.
Click the Logout item in the pulldown menu (a Confirm Logout popup message appears).
Click on Yes or press the <Enter> key to confirm logout.

The screen display returns to the Login tab.
NOTE
If a logout was previously performed on the BTS from a CLI window running at the same time as
the GUI, a Logout Error popup message appears stating the system should not log out of the
BTS. When this occurs, the GUI must be exited and restarted before it can be used for further
operations.
4
If a Logout Error popup message appears stating that the system could not log out of the Base
Station because the given BTS is not logged in, perform the following actions:
Click OK.
Select File>Exit in the window menu bar.
Click Yes in the Confirm Logout popup.
Click Yes in the Logout Error popup which appears again.
If further work is to be done in the GUI, restart it.
NOTE
S The Logout item on the BTS menu bar will only log the LMF out of the displayed BTS.
S Logging out of all BTS sessions and exiting the LMF can be done by clicking on the File
selection in the menu bar and selecting Exit from the File menu list. A Confirm Logout
popup message will appear.
3-36
SEP 2009
Using the LMF
continued
Logging Out of a BTS from the CLI Environment

Follow the procedure in Table 3-9 to logout of a BTS when using the
CLI environment.
Table 3-9: BTS CLI Logout Procedure
n Step
1
Action
NOTE
If the BTS is also logged into from a GUI running at the same time and further work must be done
with it in the GUI, proceed to step 2.
Logout of a BTS by entering the following command:
logout bts<bts#>
A response similar to the following is displayed:
LMF>
Command=logout bts33
12:22:58.028 Command Successfully Completed
REASON_CODE=No Reason
If desired, close the CLI interface by entering the following command:

exit
A response similar to the following is displayed before the window closes:
Killing background processes....
SEP 2009
3-37
Establishing an MMI Communication Session

Establishing an MMI
Communication Session
For those procedures that require MMI communications between the

LMF and BTS FRUs, follow the procedure in Table 3-10 to initiate the
communication session.
Table 3-10: Establishing MMI Communication

Step
Action
Connect the LMF computer to the equipment as detailed in the applicable procedure that requires the
MMI communication session and Figure 3-9 or Figure 3-10.
If the LMF computer has only one serial port (COM1) and the LMF is running, disconnect the LMF
from COM1 by performing the following:
1. Click on Tools in the LMF window menu bar, and select Options from the pulldown menu list.
Result: An LMF Options dialog box will appear.
2. In the Test Equipment tab of the dialog box, select COM1 in the Comm Port pulldown on the
Serial Connection tab.
3. Click the Disconnect Port button on the Serial Connection tab.
Start the named HyperTerminal connection for MMI sessions by double clicking on its Windows
operating system desktop shortcut.
NOTE
If a Windows desktop shortcut was not created for the MMI connection, access the connection from the
Windows Start menu by selecting:
Programs > Accessories > Hyperterminal > HyperTerminal > <Named HyperTerminal
Connection (e.g., MMI Session)>
4
3-38
Once the connection window opens, establish MMI communication with the BTS FRU by pressing
the LMF computer Enter key until the prompt identified in the applicable procedure is obtained.
SEP 2009
continued

Cable CGDSMMICABLE219112 or Fabricated MMI Cable
TO FRU MMI CONNECTOR
8PIN
3
LMF COMPUTER
CABLE PART NUMBEr
CGDSMMICABLE219112
OR
COM1
OR
COM2
FABRICATED MMI CABLE

(SEE APPENDIX L)
DB9
CONNECTOR

Motorola MMI Interface Kit, SLN2006A
TO FRU MMI PORT
8PIN
NULL MODEM
BOARD
(TRN9666A)
8PIN TO 10PIN
RS232 CABLE
(P/N 3009786R01)
CDMA LMF
COMPUTER
RS232 CABLE
COM1
OR
COM2
DB9TODB25
ADAPTER
FW00687
SEP 2009
3-39
LMF Online Help

LMF Online Help
Online Help
Task oriented online help is available in the LMF by clicking on Help

in the LMF window menu bar, and selecting LMF Help from the
pulldown menu.
3-40
SEP 2009
Pinging the Processors

Pinging the BTS
For proper operation, the integrity of the Ethernet LAN A and B links
must be be verified. Figure 3-12 represents a typical BTS Ethernet
configuration for an SC4812ET twoframe logical BTS. The illustration
shows cabling and termination for both the A and B LANs.
Ping is a program that sends request packets to the LAN network
modules to get a response from the specified target module.
NOTE
WinLMF has an option in the LOGIN menu to ping the
GLI prior to login.
Follow the steps in Table 3-11 to ping each processor (on both LAN A
and LAN B) and verify LAN redundancy is working properly.
CAUTION
handling any circuit card/module to prevent damage by
ElectroStatic Discharge (ESD).
Figure 3-11: SC4812ET External 10Base2 Ethernet LAN Connector Locations
LAN A IN
LAN A OUT
LAN B IN
LAN B OUT
NOTE: Punchblock and power

cables not shown for clarity
SEP 2009
Rear of RF Frame
(Power I/O Compartment Door Not
Shown)
SC4812ET00241
3-41
continued
Figure 3-12: BTS Ethernet LAN Interconnect Diagram

OUT
50
IN
50
SIGNAL
GROUND
SIGNAL
GROUND
3
BTS
(MASTER)
20 Pair
Punchblock
(RGPS)
1A
2A
3A
1B 2B
3B
4A
5A
6A
4B 5B
6B
RF Expansion Ports
1A
2A
3A
1B 2B
Micro
wave
Power Input
+27V
RF
GPS
1A
2A
3A
1B 2B
3B
4A
5A
6A
4B 5B
6B
(Alarms/
Spans)
1A
IN OUT
2A
3A
1B 2B
4A
5A
6A
4B 5B
6B
Spans
Antennas
19 MHz
Modem
Alams
Micro
wave
Power Input
+27V
RF
GPS
LAN
3B
IN OUT
A
B
Remote
ASU
RGD
Board
RGD/RGPS
50 Pair
Punch
Block
RF Expansion Ports
LAN
3B
20 Pair
Punchblock
(RGPS)
RGD/RGPS
50 Pair
Punch
Block
(Alarms/
Spans)
BTS
(EXPANSION)
RGD
Board
A
B
Power Input
27V Ret
Remote
ASU
4A
5A
2 Sec
6A
6B
19 MHz
Spans
Antennas
GND
Lugs
4B 5B
Modem
Alams
Power Input
27V Ret
2 Sec
GND
Lugs
50
50
SIGNAL
GROUND
SIGNAL
GROUND
FW0019901
Follow the steps in Table 3-11 to ping each processor (on both LAN A
and LAN B) and verify LAN redundancy is working properly.
NOTE
Ethernet cables or terminators must be installed on all
LAN A and B connectors on each BTS frame I/O panel
before performing this test.
Table 3-11: Pinging the Processors
Step
Action
If this is a firsttime communication with a newlyinstalled frame or a GLI card which has been
replaced, perform the procedure in Table 7-3 and then return to step 2.
Be sure uncabled LAN A and B IN and OUT connectors in the power I/O compartment (rear of frame
Figure 3-11 and Figure 3-12) are terminated with 50 terminators or Ethernet cables connecting to
another frame.
3-42
SEP 2009
continued

Step
Action
If it has not already been done, connect the LMF computer to the BTS (refer to Figure 3-4 and
Table 3-5).
If it has not already been done, start a GUI LMF session and log into the BTS (refer to Table 3-6).
In the power I/O compartment, remove the 50 terminator on the frame LAN B IN connector.
Result: The LMF session should remain active.
Replace the 50 terminator on the BTS frame LAN B IN connector.
From the Windows desktop, click the Start button and select Run.
In the Open box, type ping and the GLI2 IP address (for example, ping 128.0.0.2).
NOTE
128.0.0.2 is the default IP address for the card in cage slot GLI 1 in field BTS units.
128.0.0.1 is the IP address for the card in cage slot GLI 2 in field BTS units.
9
Click on OK.
10
If the targeted module responds, a command prompt window will appear with a display similar to the
following:
Reply from 128.0.0.2: bytes=32 time=3ms TTL=255
If the device responds, proceed to step 17.

11
If there is no response, the following is displayed:

Request timed out
If the GLI fails to respond, it should be reset and repinged. If it still fails to respond, typical problems
would be: failure of the LMF to login, shorted BNCtointer-frame cabling, open cables, crossed A
and B link cables, or the GLI card itself. Proceed to step 12.
12
Logout of the BTS as described in Table 3-8, exit from the LMF program, and restart the Windows
operating system on the LMF computer.
13
Restart the LMF GUI program, and log into the BTS as described in Table 3-6.
14
Perform steps 7 through 10 again.
15
Perform one of the following depending on the result of step 14:
S If the device responds, proceed to step 17.

S If there is still no response, proceed to step 16.
SEP 2009
3-43
continued

Step
16
Action
If ping was unsuccessful after restarting the CDMA LMF computer, press the GLI front panel reset
pushbutton and perform steps 7 through 10 again.
NOTE
3
Refer to Table 7-1 if ping was unsuccessful after resetting the GLI.
17
After the BTS has been successfully pinged, be sure the 50 terminator was replaced on the BTS
frame LAN B IN connector in the power I/O compartment (Figure 3-11). Disconnect the LMF cable
from the service shelf LAN A connector, and connect it to LAN B (righthand connector).
18
In the power I/O compartment, remove the 50 terminator on the BTS frame LAN A IN connector.
19
Repeat steps 7 through 10 using LAN B.
20
After the BTS has been successfully pinged on the secondary LAN, replace the 50 terminator on the
frame LAN A IN connector in the power I/O compartment.
21
Disconnect the LMF cable from the LAN shelf LAN B and connect it to LAN A.
22
Remove and replace the 50 terminator on the LAN B IN connector to force the GLI to switch to
primary LAN A.
23
Repeat steps 7 through 10 to ensure proper primary LAN operation.
3-44
SEP 2009
Take Control of Packet BTS Resources

Packet BTS Control
In a packet BTS, the GLI3 card controls all BTS resources, such as the
MCC, BBX, and CSM cards, which were previously managed by the
Central Base Station Controller (CBSC) Mobility Manager (MM) for
circuit BTSs. As a result, the LMF can not perform any of the normal
code/data download, optimization, or test functions with packet BTS
cards until the GLI3 gives up control of these items.
NOTE
The GLI3 cards in a packet BTS can never be placed under
LMF control. GLI3 cards are selfmanaged Network
Elements (NE) in a packet Base Station System (BSS). The
GLI3 cards are not designed to give up control of the
packet BTS and, in packet mode, will not transfer control
of themselves to the LMF. An LMF control request for a
GLI3 in a packet BTS will fail immediately with a status
message of GLI Object Not Supported For LMF Control.
In a packet BTS, the GLI3 cards will always show the X
in the LMF display indicating they are not under LMF
control.
Taking Control of Packet BTS

Resources
After logging into a packet BTS for optimization or acceptance testing,

the first action which must be performed is transferring control of the
BTS cards from the GLI3 to the LMF.
Prerequisites
LMF must be logged into the BTS.
SEP 2009
3-45
continued
Taking Control
Perform the following to have the LMF assume control of the BTS
resources.
Table 3-12: Take Control of Packet BTS Resources with the LMF
Step
Action
With the BTS frame card cage displayed in the LMF, click on all MCC and BBX cards or use
selections under the BTS tab Select menu item to select them.
Result: Cards will change to a darker color in the display when selected.
In the BTS tab menu select Device > Packet Mode Options > LMF Control Request
Result: An LMF Control progress window will be displayed followed by a status report window when
the activity is completed.
NOTE
The X indicating GLI3 control (Figure 3-6) will not be displayed on any cards for which control has
been transferred to the LMF.
3
3-46
If the attempt to obtain control of some cards fails, repeat steps 1 and 2 for each failed card one card at
a time.
SEP 2009
Download the BTS General Information

Overview
Before a BTS can operate, each equipped device must contain device
initialization (ROM) code. ROM code is loaded in all devices during
manufacture or factory repair. Device application (RAM) code and data
must be downloaded to each equipped device by the user before the BTS
can be made fully functional for the site where it is installed.
Download ROM Code
Downloading ROM code to BTS devices from the LMF is NOT routine
maintenance nor a normal part of the optimization process. It is only
done in unusual situations where the resident ROM code in the device
does not match the release level of the software on the RAN AND the
OMCR cannot communicate with the BTS to perform the download. If
ROM code must be downloaded, refer to Appendix G.
Before ROM code can be downloaded from the LMF, the correct ROM
code file for each device to be loaded must exist on the LMF computer.
ROM code must be manually selected for download.
NOTE
The ROM code file is not available for GLI3 cards. GLI3s
are ROM code loaded at the factory.
RAM Code
NOTE
Beginning in R22.0, GLI3 cards in packet mode can be
downloaded with RAM code and data using the WinLMF.
Before RAM code can be downloaded from the CDMA LMF, the correct
RAM code file for each device must exist on the LMF computer. RAM
code can be automatically or manually selected depending on the Device
menu item chosen and where the RAM code file for the device is stored
in the CDMA LMF file structure. The RAM code file is selected
automatically if the file is in the \lmf\cdma\loads\n.n.n.n\code folder
(where n.n.n.n is the version number of the download code). The RAM
code file in the code folder must have the correct hardware bin number.
RAM code can be downloaded from the LMF to a device that is in any
state. After the download is started, the device being downloaded
changes to Out Of Service_ReadOnly Memory (OOS_ROM) (blue).
When the download is completed successfully, the device changes to
Out Of Service_Random Access Memory (OOS_RAM) (yellow).
For nonGLI devices, data must be downloaded after RAM code is
downloaded. To download data, the device state must be OOS_RAM
(yellow).
SEP 2009
3-47
continued
Prior to downloading to a device, a code file must be located on the

LMF computer. The code file is selected automatically if the code file is
in the /lmf/cdma/n.n.n.n/code folder (where n.n.n.n is the version number
of the download code that matches the NextLoad parameter in the
NEC files). The code file in the code folder must have the correct
hardware bin number. Code can be automatically or manually selected.
The devices to be loaded with RAM code and data are:
S Clock Synchronization Module (CSM)

S Multi Channel Card (MCC24E, MCC8E or MCC1X)
S Broadband Transceiver (BBX)
NOTE
S One GLI3 card must be loaded with code and data, and
operating as INS_ACT before the LMF can download

any other device. Beginning with R22.0, if the GLI3
cards in the BTS require a different code load from that
installed, they can be loaded from the R22.0 and later
WinLMF.
S Other devices in the BTS can be downloaded by the

LMF in any order.
3-48
SEP 2009
Download BTS Loading Packet GLI Devices

Beginning with R22.0, the LMF has the capability to download code to
GLI3 cards operating in packet mode. This section contains the
intructions needed to do this.
Prerequisites
The following must be done before performing this procedure:
S The BTS has power applied and has reached normal operating
temperature
S The GLI3 code and data files required for the software release
installed in the RAN where the BTS is assigned have been loaded in
the LMF computer in the correct directory (refer to the Preparing the
LMF section in this chapter).
S For a logical BTS, the interframe 10Base2 LAN cables are correctly
connected, and unused LAN connectors are properly terminated (refer
to Figure 3-12).
S The LMF computer is connected to the BTS 10Base2 LAN A and, if

necessary, LAN A has been forced to be the active LAN (refer to the
procedure in Table 3-11)
S The LMF is operating

S The LMF is NOT logged into the BTS
Downloading code to packet
GLI3 card
Perform the following to load code into the GLI3 cards.

Table 3-13: Loading Code into Packet GLI3 Card with the LMF
Step
1
Action
With the BTS fully powered up, the GLI3 cards should have been connected (seated) in the correct
cage slots. Perform one of the following:
S If cards are not seated, seat only the card in Frame 1 cage slot 1, and allow it to complete
initialization to OOS_SBY.
S If all cards are seated, disconnect (unseat) the card in Frame 1 cage slot 2 from the cage backplane
connector.
NOTE
Do not disconnect any installed Fast Ethernet (FE) cables from card BPR and GLI connectors.
2
In logical BTS expansion frames, unseat all GLI3 cards from their backplane connectors.
NOTE
Do not disconnect any installed FE cables from card BPR and GLI connectors.
SEP 2009
3-49
continued
Step
Action
If desired or required by the network operators procedures, back up the powered GLI3 card
configuration files by selecting Tools > GLI3 Code Operations > GLI3 Configuration Files
Backup from the LMF window menu bar.
Result: A status window will open displaying a progress bar. When the operation is complete, the
status window will display a pass/fail indication.
If files were backed up, click OK to close the GLI3 Configuration Files Backup status window
Verify availability of the GLI3 card in cage slot 1 by selecting Tools > GLI3 Code Operations >
Verify GLI3 Availability from the LMF window menu bar.
Result: A message box will open, and, if the GLI3 is available, it will display a message that the GLI3
card is detected at IP address 128.0.0.2, port 9216 (128.0.0.2:9216).
Click OK to close the message box.
Begin the download GLI3 code process for the card by selecting Tools > GLI3 Code Operations >
GLI3 Code Download from the LMF window menu bar.
Result: A GLI3 Code Download window will open, and download parameter options will be
displayed.
Using the dropdown pick list for Code file to put on GLI3, select the required code image for the
GLI3 card based on the required software release and GLI3 operation mode.
NOTE
1. The dropdown picklist will display the GLI3 code images available on the LMF computer by their
software release numbers.
2. Listed GLI3 code images will have a suffix of (P) for packet operation or (C) for circuit operation.
9
Select Reset after code download to GLI3 by clicking in the checkbox.
NOTE
This option will cause the GLI3 to reset and initialize with the code image downloaded with this
procedure.
10
To prevent a packet GLI3 from continually resetting because the timeout for synchronizing with the
OMCR expires, click in the checkbox Leave synchronization resets turned OFF on GLI3 (P).
NOTE
1. This option is only available when packet code is selected for download and Reset after code
download to GLI3 is selected.
2. This option is very useful when there will be an extended time before communication between the
BTS and the OMCR can be established. Examples are optimization of a new (greenfield) BTS and
reconfiguring the BTS backhaul mode.
11
Click OK to download code to the GLI3 card.

Result: A GLI3 Code Download status window will open displaying a progress bar and each action
taken during the GLI3 code download. A pass/fail indication and description are also provided for
each action taken.
3-50
SEP 2009
continued
Step
Action
12
When download and reset are successfully completed, be sure the GLI3 initializes as INS_ACT
(shows light green in the LMF; LED states: ACT LED steady green, STA LED slow flashing green)
13
If no further actions are needed which requre the other GLI3 card(s) in the BTS to remain unpowered
(such as completing conversion to OTI backhaul), seat the other GLI3 cards in the cage backplane.
Result: The other GLI3 cards will initialize and the INS_ACT GLI3 will crossload them with the
downloaded code.
SEP 2009
3-51
Download BTS Loading NonGLI Devices

Download Code and Data to
NonGLI Devices
Prerequisite
In a packet BTS, control of the nonGLI devices has been transferred to
the LMF (Table 3-12).
Downloading NonGLI Devices

NonGLI devices can be downloaded individually or all equipped
devices can be downloaded with one action. Follow the procedure in
Table 3-14 to download code and data to the nonGLI devices.
NOTE
S CSM devices are RAM codeloaded at the factory.
RAM code is downloaded to CSMs only if updating to

a newer software version.
S When downloading multiple devices, the download
may fail for some of the devices (a time out occurs).

These devices can be downloaded separately after
completing the multiple download.
3-52
SEP 2009
continued
Table 3-14: Download RAM Code and Data or Data Only to NonGLI Devices
n Step
1
Action
NOTE
In a packet BTS, be sure to perform the procedure in Table 3-12 to give the LMF control of the
nonGLI devices before continuing.
Select the target CSM, MCC, and/or BBX device(s) by clicking on them.
Do one of the following, as required:
S To download code and data, click Device in the BTS menu bar, and select Download >
Code/Data in the pulldown menus.
S To download only data, click Device in the BTS menu bar, and select Download > Data in the
pulldown menus.
Result: A status report is displayed that shows the results of the download for each selected
device.
3
Click OK to close the status report window when downloading is completed.
NOTE
S After the download has started, the device being downloaded changes to blue. If the download
is completed successfully, the device changes to yellow (OOSRAM with code loaded).
S After a BBX, CSM, or MCC device is successfully loaded with RAM code and has changed to
the OOS_RAM state (yellow), the status LED should be rapidly flashing GREEN.
S Data can be downloaded without doing a code download any time a device is OOSRAM using
the Device > Download > Data command.
NOTE
When downloading code and data to MCC1X cards, the
LMF may report that the cards are not responding or have
timed out. Newly installed MCC1X cards can take up to 5
minutes to establish the link with the GLI and complete the
download.
If the LMF reports that newly installed MCC1X cards are
not responding, allow a minimum of 5 minutes for the
cards to complete the download process and then restatus
the cards.
Until the 5minute minimum wait time is over, do not:
S Attempt to restart the download process to the cards
S Remove the cards from the BTS

SEP 2009
3-53
continued
BBX Cards Remain OOS_ROM

If BBX cards remain OOS_ROM (blue) after powerup or following
code load, refer to Table 7-8, Steps 9 and 10.
3-54
SEP 2009
Enabling Other Devices

Selecting the CSM Clock
Source
CSMs must be enabled prior to enabling the MCCs. Procedures in the

following two subsections cover the actions to accomplish this. For
additional information on the CSM subsystem, see Clock
Synchronization Manager (CSM) Subsystem Description in the CSM
System Time GPS, LFR, and HSO/MSO Verification section of this
chapter.
Select CSM Clock Source
A CSM can monitor up to three reference sources at the same time.
Typically, however, only two sources are used. The Select CSM Source
function can be used to select the clock source for each of the three
reference source inputs. This function is only used if the clock source for
a CSM needs to be updated to match the currently installed hardware.
The Clock Source function provides the following clock source options:
S Local GPS
S
S
S
S
S
S
Mate GPS
Remote GPS
HSO/MSO/QHSO (only used as source 2 or 3)
HSO Extender (only used as source 2 or 3)
LFR (only used as source 2 or 3)
NONE (only used as source 2 or 3)
Prerequisites
S GLI is INS_ACT (light green in the LMF)
S CSM is OOS_RAM (yellow in the LMF) or INS_ACT (light green in
the LMF)
Table 3-15: Select CSM Clock Source
Step
Action
Display the CSM cage view in the LMF by clicking on the CSM area of the CCCP shelf in the
picture of the BTS frame.
When the CSM cage view replaces the GLI/MCC/BBX view, click on the CSM(s) for which the clock
source is to be selected.
In a packet BTS, gain control of the selected card(s) by performing the procedure in Table 3-12.
2
3
4
Click on Device in the BTS menu bar, and select CSM/MAWI > Select Clock Source... in the
pulldown menu list.
Result: A CSM clock reference source selection window will appear.
Select the applicable clock source in the Clock Reference Source pick lists. Uncheck the related
check boxes for Clock Reference Sources 2 and 3 if the displayed pick list item is NOT to be used.
SEP 2009
3-55
continued
Table 3-15: Select CSM Clock Source

Step
6
Action
Click on the OK button.
Result: A status report is displayed showing the results of the operation.
Click on the OK button to close the status report window.
3
NOTE
For RFGPS, verify the CSM configured with the GPS
receiver daughter board is installed in slot CSM 1 before
continuing.
Enable CSMs
Perform the following to enable the CSMs.
Table 3-16: Enable CSMs
Step
1
Action
NOTE
If the BTS is equipped with two CSMs, enable the card in slot CSM 2 first.
Click on the target CSM.
Click on Device in the BTS menu bar, and select Enable/Activate in the pulldown menu list.
Result: A status report is displayed showing the results of the enable operation.
Click OK to close the status report window.
NOTE
S The card in slot CSM 1 interfaces with the GPS receiver (either onboard or remote). The enable
sequence for this card can require up to one hour to complete (see below).
S FAIL may be shown in the status report table for a slot CSM 1 enable action. If Waiting For
Phase Lock is shown in the Description field, do not cancel the enable process. The CSM will
change to the Enabled state after phase lock is achieved.
3-56
SEP 2009
continued
Table 3-16: Enable CSMs

Step
4
Action
Allow the card to come into service.
NOTE
The GPS satellite system satellites are not in a geosynchronous orbit and are maintained and operated
by the United States Department of Defense (DOD). The DOD periodically alters satellite orbits;
therefore, satellite trajectories are subject to change. A GPS receiver that is INS contains an ephemeris
(satellite position table) that is updated periodically to take these changes into account.
If a GPS receiver has not been updated for a number of weeks, it may take up to an hour for the GPS
receiver ephemeris to be updated.
Once updated, the GPS receiver must track at least four satellites and obtain (hold) a 3D position fix
for a minimum of 45 seconds before the CSM will come in service. (In some cases, the GPS receiver
needs to track only one satellite, depending on accuracy mode set during the data load.)
5
NOTE
S If two CSM cards are installed and the CSM in slot CSM 1 is in the INS_ACT state, the LMF cage
view should show CSM 1 as light green. If the CSM in slot CSM 2 is the INS_SBY state, the LMF
cage view should display CSM 2 colored dark green.
S If more than an hour has passed without the board in slot CSM 1 enabling, refer to the CSM System
Time GPS & LFR/HSO Verification section of this chapter (see Table 3-19, Figure 3-14, and
Table 3-20) to determine the cause.
After CSMs have been successfully enabled, be sure the PWR/ALM LEDs are steady green
(alternating green/red indicates the card is in an alarm state).
SEP 2009
3-57
continued
Enable MCCs
Prerequisites
One GLI and the primary CSM must be downloaded and enabled
(INS_ACTIVE green) before downloading and enabling MCCs.
Enabling MCCs
Perform the following to enable the MCCs.
Table 3-17: Enable MCCs

Step
Action
Verify the MCC(s) have been downloaded with code (yellow,

OOS_RAM) and data.
Select the MCCs to be enabled from the Select pulldown

menu by choosing MCCs or by clicking on them in the
graphic display.
In a packet BTS, gain control of the selected card(s) by

performing the procedure in Table 3-12.
From the Device menu, select Enable/Activate.

Result: A status report confirms change in the device(s)
status.
3-58
Click on OK to close the status report window.
SEP 2009
CSM System Time GPS, LFR, and HSO/MSO Verification

CSM System Time GPS, LFR, and HSO/MSO Verification
Clock Synchronization
Manager (CSM) Subsystem
Description
Overview
Each BTS CSM subsystem features two CSM cards per RFMF. The
primary function of the CSM cards is to maintain CDMA system time.
GPS is used as the primary timing reference and synchronizes the entire
cellular system. In typical operation, the primary CSM locks its Digital
Phase Locked Loop (DPLL) circuits to GPS signals. These signals are
provided by either an onboard GPS receiver module (RFGPS) or a
remote GPS receiver (RGPS). RGPS uses a GPS receiver in the antenna
head that has a digital output. The second generation CSM card
(CSMII) is required when using the RGPS. A CSMII card can also be
equipped with a local (RFGPS) GPS receiver daughter card to support
an RFGPS signal.
CCCP Shelf CSM Card Slot Assignments
The card in CCCP or SCCP shelf slot CSM 1 (CSM 1 card) is the
primary timing source, while the card in CSM slot 2 (CSM 2 card)
provides redundancy. For RFGPS, the GPS receiver is installed on the
CSM 1 card. In a BTS equipped with Remote GPS neither CSM card
has a GPS receiver installed. The redundant CSM card is never equipped
with a GPS receiver.
CSMII Card Type Description
Each CSMII card provides a 19.6608 MHz clock, Even Second Tick
pulse, and 3 MHz reference that is referenced to one or more of the
following available clock sources:
S GPS: local/remote RFGPS or RGPS
S High Stability Oscillator (HSO)
S Motorola Standard Oscillator (MSO)
S Quartz High Stability Oscillator (QHSO)
S High Stability Oscillator eXpansion (HSOX)
S Low Frequency Receiver (LFR)
CDMA Clock Distribution Card (CCD) Description
CCD cards buffer and distribute evensecond reference and 19.6608
MHz clock signals from the CSM cards. CCD 1 is married to the CSM 1
card, and CCD 2 is married to the CSM 2 card.
CSM Card Redundancy
The BTS switches between the primary and redundant units (cards CSM
1 and CSM 2, respectively) upon a card failure or command. A failure in
CSM 1 or CCD 1 will cause the system to switch to the CSM 2CCD 2
redundant card pair. GPS timing synchronization is continually
maintained between the primary and redundant CSMCCD pairs.
SEP 2009
3-59
CSM System Time GPS, LFR, and HSO/MSO Verification continued

Secondary Timing References
The BTS should be equipped with a backup time reference source to
maintain synchronization if the GPS reference becomes unavailable. The
BTS supports the following backup reference sources: HSO, MSO,
HSOX, or LFR. The CSM continuously monitors all available reference
sources and selects the most appropriate source for the current
operational conditions.
Timing Source Fault Management
CSM fault management has the ability to switch between the GPS and
any available backup reference source in the event of a GPS reference
failure. During normal operation, the CSM 1 card will select a GPS
reference source (Table 3-20). The source selection can also be
overridden through the LMF or system commands.
Front Panel LED and Status
Displays
The CSM cards include on-board alarm detection. Hardware and

software/firmware state and alarm conditions are displayed by the front
panel LED indicator (Figure 3-13). Table 3-18 provides explanations of
card front panel LED indications for CSM card state/status.
Figure 3-13: CSM Front Panel PWR/ALM LED Indicator
PWR/ALM
Indicator
FW00303
After running onboard memory tests, the CSM loads OOS_RAM code
from the Flash EPROM, if available. If not available, the OOS_ROM
code is loaded from the Flash EPROM.
3-60
SEP 2009
Table 3-18: CSM PWR/ALM LED Indications

LED Display
CSM Card State
Steady GREEN
CSM is in INS_ACT or INS_SBY state

with no detected faults.
Steady RED
Initial power up or module is operating in

a fault (alarm) condition.
Slowly Flashing GREEN
OOS_ROM (no alarm)
Alternating Long RED /

Short GREEN
OOS_ROM with detected fault (alarm)
Rapidly Flashing
GREEN
OOS_RAM state with no detected faults
Alternating Short RED /

Short GREEN
OOS_RAM with detected fault (alarm) or

CSM in GPS satellite
acquisition/synchronization process
Alternating
Long GREEN / Short
RED
INS_ACT or INS_SBY with detected

fault (alarm)
Off
No DC power or on-board fuse is open.
Steady YELLOW
After a reset, the CSMs begin to boot.

During SRAM test and Flash EPROM
code check, the LED is yellow. (If SRAM
or Flash EPROM fail, the LED changes
to a solid RED and the CSM attempts to
reboot.)
Backup Timing Reference

Sources
CSM and LFR, HSO, MSO, or QHSO Backup

The CSM performs the overall configuration and status monitoring
functions for the LFR, HSO, MSO, or QHSO backup reference. During
times when a GPS timing reference is unavailable, the CSM can use the
LFR, HSO, or MSO to maintain the synchronization initially established
by the GPS reference.
LFR
The LFR requires an external antenna to receive longrange navigation
(loran) RF signals. Timing pulses are obtained from this signal, which is
synchronized to Universal Time Coordinates (UTC) and GPS time. After
initial GPS lock, the LFR can maintain system synchronization
indefinitely.
SEP 2009
3-61

HSO
An HSO card provides a highly stable clock source for installed CSM
cards. The HSO is capable of maintaining CSM synchronization for a
minimum of 24 hours following 24 hours of calibration by a GPS
reference.
MSO
An MSO card provides a highly stable clock source for installed CSM
cards. The MSO is capable of maintaining CSM synchronization for a
minimum of 8 hours following 8 hours of calibration by a GPS
reference.
QHSO
A QHSO card provides the same highly stable clock source for installed
CSM cards. Like the HSO, the QHSO is capable of maintaining CSM
synchronization for a minimum of 24 hours following 24 hours of
calibration by a GPS reference.
HSOX
An HSOX card is used to receive an HSO or MSO clock reference from
a starter frame in a multiframe BTS. CSM cards using an HSOX
backup reference will maintain synchronization from the HSO or MSO
in the starter frame during the absence of a GPS reference source.
NOTE
Allow the base site and test equipment to warm up for
60 minutes after any interruption in oscillator power. CSM
card warm-up allows the oscillator oven temperature and
oscillator frequency to stabilize prior to test. Test
equipment warm-up allows the Rubidium standard
timebase to stabilize in frequency before any measurements
are made.
3-62
SEP 2009

CSM Frequency Verification
The objective of this procedure is the initial verification of the Clock

Synchronization Module (CSM) cards and timing sources before
performing the RF path verification tests.
GPS and LFR/HSO/MSO/QHSO
Verification
Follow the steps outlined in Table 3-19 to set up test equipment.

Table 3-19: Test Equipment Setup for GPS and LFR/HSO/MSO/QHSO Verification
Step
Action
Perform one of the following as required by installed equipment:

1. For local GPS (RFGPS): Verify a CSM card with a GPS receiver is installed in the primary CSM
slot, CSM 1, and that the card is INS_ACT (light green in LMF display).
NOTE
Verify by checking the card ejectors for kit number SGLN1145 on the CSM 1 card.
2. For Remote GPS (RGPS): Verify a CSMII card, kit number SGLN4132ED or subsequent, is
installed in both the primary (CSM 1) and secondary (CSM 2) card slots, and that the cards are
INS_ACT (steady green LED on card front panels and light and dark green color, respectively, in
LMF display).
2
Remove the CSM 2 card (if installed), and connect an MMI communication cable from the LMF
computer COM 1 port to the MMI port on the CSM 1 card (see Figure 3-14).
Reinstall the CSM 2 card.
Start an MMI communication session with the CSM 1 card by using the Windows desktop shortcut
icon (see Table 3-3) .
When the terminal screen appears press the Enter key until the CSM> prompt appears.
CAUTION
1. In the power entry compartment, connect the GPS
antenna to the RF GPS connector ONLY. Damage to
the GPS antenna and/or receiver can result if the GPS
antenna is inadvertently connected to any other RF
connector.
2. The following procedure requires handling of
staticsensitive devices. Always wear an approved
antistatic wrist strap while handling any circuit
card/module to prevent damage by ESD. Extreme care
should be taken during the removal and installation of
any card/module. After removal, the card/module
should be placed on a conductive surface or back into
the antistatic container in which it was shipped.
SEP 2009
3-63

Figure 3-14: CSM MMI Terminal Connection
REFERENCE
OSCILLATOR
CSM CARD SHOWN

REMOVED FROM FRAME
MMI SERIAL
PORT
EVEN SECOND
TICK TEST POINT
REFERENCE
GPS RECEIVER
ANTENNA INPUT
ANTENNA COAX
CABLE
GPS RECEIVER
LED (SEE NOTE)
NULL MODEM
BOARD
(TRN9666A)
9PIN TO 9PIN
RS232 CABLE
19.6 MHZ TEST

POINT REFERENCE
FW00372
LMF
COMPUTER
PLATFORM
DB9TODB25
ADAPTER
RS232 SERIAL
MODEM CABLE
COM1
NOTE
1. For card state LED indications, see Table 3-18 and
Figure 3-13 in this section.
2. MMI connection can also be made using locally
fabricated MMI cable. See Appendix L.
GPS and HSO/MSO/QHSO
Initialization/Verification
Prerequisites
Ensure the following prerequisites have been met before proceeding:
S The LMF is not logged into the BTS.

S The primary CSM and HSO, MSO, or QHSO (if equipped) has been
warmed up for at least 15 minutes.

S The LMF computer serial port (COM1) is connected to the MMI port
of the primary CSM as shown in Figure 3-14.
3-64
SEP 2009

S An MMI communication session has been started, and the CSM>
prompt is present in the HyperTerminal window (Table 3-19).
Follow the steps outlined in Table 3-20 to initialize and verify proper
GPS receiver functioning.
Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification
Step
Action
To verify that Clock alarms (0000), Dpll is locked and has a reference source, and
GPS self test passed messages are displayed within the report, issue the following MMI
command
bstatus
The system will display a response similar to the following:
Clock Alarms (0000):
DPLL is locked and has a reference source.
GPS receiver self test result: passed
Time since reset 0:33:11, time since power on: 0:33:11
Verify the following GPS information (underlined text above):

GPS information is usually the 0 reference source.
At least one Primary source must indicate Status = good and Valid = yes to bring site up.
SEP 2009
3-65

Step
3
Action
Enter the following command at the CSM> prompt to verify that the GPS receiver is in tracking mode.
gstatus
The CSM will provide a response similar to the following:
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
(GPS)
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
0:25:54
GPS Receiver Control Task State: tracking satellites.

Frame type (0): master.
Recent Change Data:
GPS time offset 0 ns.
Initial position: lat 151681457 msec, lon 316796711 msec, height 20647 cm
Initial position accuracy (0): estimated.
GPS Receiver Status:
Position hold: lat 123204234 msec, lon 280481015 msec, hgt 1584 cm
Current position: lat 123204233 msec, lon 280481014 msec, hgt 1584 cm (GPS)
8 satellites tracked, receiving 8 satellites, 11 satellites visible.
Current Dilution of Precision (PDOP or HDOP): 0.
Date & Time: 2005:01:31:20:50:18 LS:13 Cached LS:13
GPS Receiver Status Byte:0x08
Chan:0, SVID: 2, Mode: 8, RSSI: 49, Status: 0xa2
GPS Receiver Identification:
COPYRIGHT 20002003 NAVMAN LTD.
SFTW P/N # 0000
SOFTWARE VER # 93
SOFTWARE REV # 07
SOFTWARE DATE 09/04/2003
MODEL # R01
HDWR P/N # TU60D125
SERIAL # 1103108952
MANUFACTUR DATE 111//02030
OPTIONS LIST 5843
The receiver has 8 channels and is equipped with TRAIM.
Verify the following GPS information (shown above in underlined text):

At least 4 satellites are tracked, and 4 satellites are visible.
GPS Receiver Control Task State is tracking satellites. Do not continue until this occurs!
Record the following:
Current position latitude and longitude in the displayed milliseconds format
Current position height in the displayed cm units
3-66
SEP 2009

Step
5
Action
If steps 1 through 4 pass, the GPS is good.
NOTE
If any of the above mentioned areas fail, verify that:
If Initial position accuracy is estimated (typical), at least 4 satellites must be tracked and
visible (1 satellite must be tracked and visible if actual lat, log, and height data for this site has
been entered into NEC file).
If Initial position accuracy is surveyed, position data currently in the NEC file is assumed to be
accurate. GPS will not automatically survey and update its position.
The GPS antenna is not obstructed or misaligned.
GPS antenna connector center conductor measures approximately +5 Vdc with respect to the
shield.
There is no more than 10dB signal loss (@ 1.575GHz) between the GPS antenna and BTS RF
modem frame I/O connection. The total GPS antenna system noise figure (including all
preamplifiers, cable losses, splitters) is less than 4.0dB.
Any lightning protection installed between GPS antenna and BTS frame is installed correctly.
SEP 2009
3-67

Step
6
Action
Enter the following command at the CSM> prompt to display the current status of the GPS receiver
and, depending on how the BTS is equipped, the LFR (loran receiver), the HSO, or the MSO backup
timing source:
sources
When equipped with LFR, the system will generate a response similar to the following:
N Source Name Type

TO Good Status
Last Phase Target Phase Valid
0 LocalGPS
Primary 4
YES
Good
0
0
Yes
1 LFR CHA
Secondary 4
YES
Good
2013177
2013177
Yes
2 Not Used
Current reference source number: 0
When equipped with HSO or MSO, the system will generate a response similar to the following:
Num Source Name Type
TO Good
Status Last Phase Target Phase Valid
0
Local GPS
Primary 4
Yes
Good
3
0
Yes
1
HSO
Backup
4
No
N/A
timedout*
Timedout* No
NOTE
HSO will be displayed in the CSM MMI responses when either and HSO or an MSO is installed.
Timedout should only be displayed while the HSO or MSO is warming up. If an HSO or MSO is
installed and HSO does not appear as one of the sources, configure the HSO or MSO as a backup
source by entering the following command at the CSM> prompt:
ss 1 12
After a maximum of 15 minutes, the HSO or MSO should reach operational temperature. This will be
indicated by the HSO or MSO front panel LED changing to green. After the HSO or MSO front panel
LED has changed to green, enter sources <cr> at the CSM> prompt. Verify that the HSO or MSO is
now receiving valid clock pulses as indicated by a numeric value (not timedout) in the Last
Phase column as shown below. A valid HSO or MSO is indicated by Yes in the Valid column of
the sources response below.
TO Good
0
Local GPS
Primary 4
Yes
Good
3
0
Yes
1
HSO
Backup
4
Yes
N/A
xxxxxxxxxx
xxxxxxxxxx Yes
NOTE
The time required for an MSO to become a valid reference source can range from 8 hours for a newly
installed module to less than 1 hour for modules that have been in operation for several days.
3-68
SEP 2009

Step
Action
HSO, MSO, or QHSO information (underlined text in step 6, above, read from left to right) is usually
the #1 reference source. If this is not the case, have the OMCR determine the correct BTS timing
source has been identified in the database by entering the display bts csmgen command and
correct as required using the edit csm csmgen refsrc command.
NOTE
If any of the above areas fail, verify:
If LED is RED, verify that HSO/MSO/QHSO had been powered up for at least 5 minutes. After
oscillator temperature is stable, LED should change to GREEN Wait for this to occur before
continuing !
If timed out is displayed in the Last Phase column, suspect the HSO/MSO/QHSO output buffer
or oscillator is defective
Verify the HSO/MSO/QHSO is FULLY SEATED and card extractor levers are LOCKED to
prevent possible card warpage
8
Enter the following commands at the CSM> prompt to verify that the CSM is warmed up and that GPS
acquisition has taken place.
debug dpllp
Observe the following typical response if the CSM is not warmed up (15 minutes from application of
power) (If warmedup proceed to step 9)
CSM>DPLL Task Wait. 884 seconds left.
DPLL Task Wait. 882 seconds left.
DPLL Task Wait. 880 seconds left.
...........etc.
NOTE
The warm command can be issued at the MMI port used to force the CSM into warmup, but the
reference oscillator will be unstable.
9
Observe the following typical response if the CSM is warmed up.

c:17486
c:17486
c:17470
c:17486
c:17470
c:17470
off:
off:
off:
off:
off:
off:
11,
11,
11,
11,
11,
11,
3,
3,
1,
3,
1,
1,
6
6
6
6
6
6
TK
TK
TK
TK
TK
TK
SRC:0
SRC:0
SRC:0
SRC:0
SRC:0
SRC:0
S0:
S0:
S0:
S0:
S0:
S0:
3
3
1
3
1
1
S1:2013175,2013175
S1:2013175,2013175
S1:2013175,2013175
S1:2013175,2013175
S1:2013175,2013175
S1:2013175,2013175
10
Verify the following GPS information (underlined text above, from left to right):
Lower limit offset from tracked source variable is not less than 60 (equates to 3s limit).
Upper limit offset from tracked source variable is not more than +60 (equates to 3s limit).
TK SRC: 0 is selected, where SRC 0 = GPS.
11
Enter the following commands at the CSM> prompt to exit the debug mode display.
debug dpllp
SEP 2009
3-69

Loran Initialization/Verification
Table 3-21: Loran Initialization/Verification

Step
Action
At the CSM> prompt, enter lstatus <cr> to verify that the LFR is in tracking
mode. A typical response is:
CSM> lstatus <cr>
LFR Station Status:
Stat s
Clock coherence: 512
5930M 51/60 dB 0 S/N
5930X 52/64 dn 1 S/N
5990
47/55 dB 6 S/N
7980M 62/66 dB 10 S/N
7980W 65/69 dB 14 S/N
7980X 48/54 dB 4 S/N
7980Y 46/58 dB 8 S/N
7980Z 60/67 dB 8 S/N
8290M 50/65 dB 0 S/N
8290W 73/79 dB 20 S/N
8290W 58/61 dB 6 S/N
8970M 89/95 dB 29 S/N
8970W 62/66 dB 10 S/N
8970X 73/79 dB 22 S/N
8970Y 73/79 dB 19 S/N
8970Z 62/65 dB 10 S/N
9610M 62/65 dB 10 S/N
9610V 58/61 dB 8 S/N
9610W 47/49 dB 4 S/N
9610X 46/57 dB 5 S/N
9610Y 48/54 dB 5 S/N
9610Z 65/69 dB 12 S/N
9940M 50/53
/
dB 1 S/N
/
9940W 49/56 dB 4 S/N
9940Y 46/50 dB10 S/N
9960M 73/79 dB 22 S/N
9960W 51/60 dB 0 S/N
9960X 51/63 dB 1 S/N
9960Y 59/67 dB 8 S/N
9960Z 89/96 dB 29 S/N
Flag:
Flag:
Flag:
Flag:
Flag: . PLL Station .
Flag:
Flag:E
Flag:
Flag:
Flag:
Flag:
Flag:
Flag:
Flag:
Flag:
Flag:
Flag:
Flag:
Flag:E
Flag:E
Flag:E
Flag:
g
Flag:S
Flag:E
Flag:E
Flag:
Flag:
Flag:
Flag:
Flag:
LFR Task State: lfr locked to station 7980W

LFR Recent Change Data:
Search List: 5930 5990 7980 8290 8970 9940 9610 9960
PLL GRI: 7980W
LFR Master, reset not needed, not the reference source.
CSM>
Note
> This must be greater
than 100 before LFR

becomes a valid source.
> This shows the LFR is
locked to the selected

PLL station.
This search list and PLL

data must match the
> configuration for the
geographical location
of the cell site.
3-70
SEP 2009
Table 3-21: Loran Initialization/Verification

Step
2
Action
Note
Verify the following LFR information (highlighted above in boldface type):

Locate the dot that indicates the current phase locked station assignment (assigned by MM).
Verify that the station call letters are as specified in site documentation as well as M X Y Z
assignment.
Verify the S/N ratio of the phase locked station is greater than 8.
At the CSM> prompt, enter sources <cr> to display the current status of the the loran receiver.
Observe the following typical response.
TO Good
0
Local GPS
Primary 4
Yes
Good
3
0
Yes
1
LFR ch A
Secondary 4
Yes
Good
2013177
2013177
Yes
2
Not used
Current reference source number: 1
NOTE
Timedout should only be displayed while the LFR is warming up. NotPresent or Faulty
should not be displayed. If the LFR does not appear as one of the sources, then configure the LFR as a
backup source by entering the following command at the CSM> prompt:
ss 1 2
Loran LFR information (highlighted above in boldface type) is usually the #1 reference source
(verified from left to right).
NOTE
1. If any of the above mentioned areas fail, verify:
The LFR antenna is not obstructed or misaligned.
The antenna preamplifier power and calibration twisted pair connections are intact and < 91.4 m
(300 ft) in length.
A dependable connection to suitable Earth Ground is in place.
The search list and PLL station for cellsite location are correctly configured .
2. LFR functionality should be verified using the source command (as shown in Step 3). Use the
underlined responses on the LFR row to validate correct LFR operation.
5
Close the hyperterminal window.
SEP 2009
3-71
Test Equipment Set-up

Connecting Test Equipment to
the BTS
The following types of test equipment are required to perform calibration

and ATP tests:
S LMF
S Communications system analyzer model supported by the LMF
S Power meter model supported by the LMF (required when using the
Advantest R3465 analyzer)
S
S
S
S
S
Nonradiating transmit line termination load

Directional coupler and inline attenuator
RF cables and adapters
Null modem cable (see Figure 1-1)
GPIB interface box
Refer to Table 3-22, Table 3-23, and Table 3-24 for an overview of
connections for test equipment currently supported by the LMF. In
addition, see the following figures:
S Figure 3-15 through Figure 3-19 show the test set connections for TX
calibration.
S Figure 3-20 shows test set connections for IS95 A/B

optimization/ATP tests
S Figure 3-21 through Figure 3-25 show test set connections for
IS95 A/B and CDMA2000 optimization/ATP tests.
S Figure 3-26, Figure 3-27, and Figure 3-28 show alternate test setups
for duplexed antenna connections and externally mounted directional
couplers.
Test Equipment GPIB Address

Settings
All test equipment except the Agilent E7495 and Anritsu MT8212B is
controlled by the LMF through an IEEE488/GPIB bus. To
communicate on the bus, each piece of test equipment must have a GPIB
address set which the LMF will recognize. The standard address settings
used by the LMF for the various types of test equipment items are as
follows:
S Signal generator address: 1

S Power meter address: 13
S Communications system analyzer: 18
Using the procedures included in the Verifying and Setting GPIB
Addresses section of Appendix F, verify and, if necessary, change the
GPIB address of each piece of employed test equipment to match the
applicable addresses above
.
3-72
SEP 2009
continued
Supported Test Equipment
CAUTION
To prevent damage to the test equipment, all TX test
connections must be through the directional coupler and
in-line attenuator as shown in the test setup illustrations.
IS95A/B Testing
Optimization and ATP testing for IS95A/B sites or carriers may be
performed using the following test equipment:
S Agilent 8935 series E6380A communications test set (formerly HP
8935) with option 200 or R2K
S Advantest R3465 spectrum analyzer with R3561L signal generator

and Agilent E4418B or Gigatronics Power Meter
The equipment as listed above cannot be used for CDMA 2000 testing.
CDMA2000 Testing
NOTE
IS95 C is the same as CDMA 2000.
Optimization and ATP testing for CDMA2000 1X sites or carriers may
be performed using the following test equipment:
S Advantest R3267 spectrum analyzer with R3562 signal generator
S Agilent E4406A transmitter test set with E4438C signal generator

S Agilent 8935 series E6380A communications test set (formerly HP
8935) with option 200 or R2K and with E4438C signal generator for
1X FER
S Agilent E7495A and E7495B communications test sets
S Anritsu MT8212B communications test set

The E4406A/E4438C pair, or the R3267/R3562 pair, should be
connected together using a GPIB cable. In addition, the R3562 and
R3267 should be connected with a serial cable from the Serial I/O to the
Serial I/O. This test equipment is capable of performing tests in both
IS95 A/B mode and CDMA 2000 mode if the required options are
installed.
Optional test equipment
S Spectrum Analyzer (HP8594E) can be used to perform cable
calibration.
Test Equipment Preparation
See Appendix F for specific steps to prepare each type of test set and
power meter to perform calibration and ATP .
SEP 2009
3-73
continued
Agilent E7495A and E7495B communications test sets requires

additional setup and preparation. This is described in detail in Appendix
F.
NOTE
Calibration of the communications test set (or equivalent
test equipment) must be performed at the site before
calibration the overal tes equipment set. Calibrate the
communications test set after it has been allowed to warm
up and stabilize for a minimum of 60 minutes.
CAUTION
If any piece of the the test equipment set (for example, test
cable, RF adapter) has been replaced, the test equipment
set must be recalibrated. Failure to do so could introduce
measurement errors, resulting in incorrect measurement
and degredation of system performance.
Test Equipment Connection

Charts
To use the following charts to identify necessary test equipment

connections, locate the communications system analyzer being used in
the COMMUNICATIONS SYSTEM ANALYZER columns, and read
down the column. Where a dot appears in the column, connect one end
of the test cable to that connector. Follow the horizontal line to locate the
end connection(s), reading up the column to identify the appropriate
equipment and/or BTS connector.
IS95A/Bonly Test Equipment Connections
Table 3-22 depicts the interconnection requirements for currently
available test equipment supporting IS95A/B only which meets
Motorola standards and is supported by the LMF.
3-74
SEP 2009
continued
Table 3-22: IS95A/Bonly Test Equipment Interconnection

COMMUNICATIONS SYSTEM ANALYZER
SIGNAL
EVEN SECOND
SYNCH
19.6608 MHZ
CLOCK
Advantest
R3465
Power
Meter
GPIB
Interface
LMF
Attenuator
&
Directional
Coupler
CDMA
TIME BASE
IN
GPIB
TX TEST
CABLES
INPUT
50W
RX TEST
CABLES
RF OUT
50W
BTS
SYNC
MON-ITOR
EVEN SEC
SYNC IN
CONTROL
IEEE 488 BUS
SEP 2009
ADDITIONAL TEST EQUIPMENT
FREQ
MONITOR
20 DB
BTS
ATTEN. PORT
TX16
RX16
3-75
continued
CDMA2000 1X/IS95A/Bcapable Test Equipment

Connections
Table 3-23 and Table 3-24 depict the interconnection requirements for
currently available test equipment supporting both CDMA 2000 1X and
IS95A/B which meets Motorola standards and is supported by the
LMF.
Table 3-23: CDMA2000 1X/IS95A/B Test Equipment Interconnection
SIGNAL
Agilent
8935
(Option
200 or
R2K)
Agilent
E7495A
and
E7495B
EVEN SECOND
SYNCH
EXT
TRIG IN
EVEN
SECOND
SYNC IN
19.6608 MHZ
CLOCK
MOD TIME
BASE IN
CONTROL
IEEE 488 BUS
IEEE
488
10 MHZ
RX TEST
CABLES
EXT
TRIG
Agilent
E4406A
Agilent
E4438C
Signal
Generator
TRIGGER
IN
PATTERN
TRIG IN
EXT REF
IN
GPIB
10 MHZ
OUT
10 MHZ IN
HPIB
10 MHZ OUT
(SWITCHED)
GPIB
10 MHZ IN
SERIAL
I/O
SIGNAL SOURCE
CONTROLLED
SERIAL I/O
TX TEST
CABLES
Advan
test
R3267
RF
IN/OUT
DUPLEX
OUT *
PORT 2
RF IN
RF IN
PORT 1
RF OUT
RF OUT
50OHM
Advantest
R3562
Signal
Generator
Power
Meter
GPIB
Interface
LMF
30 dB
Directional
Coupler &
20 dB Pad*
BTS
EVEN
SECOND
SYNC IN
SYNC
MONITOR
EXT REF
IN
FREQ
MONITOR
HPIB
HPIB
GPIB
SERIAL
PORT
SYNTHE
REF IN
SERIAL
I/O
RF INPUT
50 OHM
RF OUTPUT
50 OHM
RF IN/OUT
RF OUT
ONLY
RF OUTPUT
50OHM
RF OUT
50 OHM
30 DB COUPLER
AND 20 DB PAD
TX16
RX16
* WHEN USED ALONE, THE AGILENT 8935 WITH OPTION 200 OR R2K SUPPORTS IS95A/B RX TESTING BUT NOT CDMA2000 1X RX TESTING.
3-76
SEP 2009
continued
Table 3-24: Additional CDMA2000 1X/IS95A/B Test Equipment Interconnection

SIGNAL
Anritsu
MT8212B
EVEN SECOND
SYNCH
EXTERNAL
FREQ REF /
EXT TRIGGER
19.6608 MHZ
CLOCK
Power
Meter
GPIB
Interface
LMF
30 dB
Directional
Coupler &
Inline
Attenuator
BTS
SYNC
MONITOR
CDMA
TIMING
INPUT
FREQ
MONITOR
CONTROL
IEEE 488 BUS
CONTROL
SERIAL BUS
SERIAL
INTERFACE
SERIAL
PORT
10 MHZ
SIGNAL SOURCE
CONTROLLED
SERIAL I/O
TX TEST
CABLES
RF IN 50 W
RX TEST
CABLES
RF OUT 50 W
SEP 2009
30 DB COUPLER
AND MINIMUM
OF 10 DB PAD
30 DB COUPLER
AND MINIMUM
OF 35 DB PAD
TX16
RX16
3-77
continued
Equipment Warm-up
To assure BTS stability and contribute to optimization accuracy of the

BTS, warm-up the BTS and test equipment prior to performing the BTS
optimization procedure as follows:
S Agilent E7495A/B for a minimum of 30 minutes

S All other test equipment and BTS equipment for a minimum of 60
minutes
NOTE
Time spent running initial or normal power-up, hardware/
firmware audit, and BTS download counts as warm-up
time.
WARNING
Before installing any test equipment directly to any BTS
TX OUT connector, verify there are NO CDMA BBX
channels keyed. At active sites, have the OMC-R/CBSC
place the antenna (sector) assigned to the PA under test
OOS. Failure to do so can result in serious personal injury
and/or equipment damage.
Automatic Cable Calibration

Setup
Refer to Table 3-38 in the Calibrate Test Cabling Using

Communications System Analyzer section of this chapter for automatic
cable calibration procedures using a communications test set.
Manual Cable Calibration
If manual cable calibration is required, refer to Table 3-39 and

Table 3-40 in the Calibrate Test Cabling Using Signal Generator and
Spectrum Analyzer section of this chapter for procedures to use a
spectrum analyzer and signal generator.
An additional manual cable calibration procedure is available using the
using the Advantest R3465 communications system analyzer. Refer to
the Cable Calibration with R3465 Test Set section of Appendix F.
3-78
SEP 2009
continued
Set-up for TX Calibration
Figure 3-15 through Figure 3-19 show the test set connections for TX
calibration.
Figure 3-15: TX Calibration Test Setup Agilent 8935 (IS95A/B & CDMA2000 1X) (IS95A/B)
TEST SETS
AGILENT 8935 SERIES E6380A (FORMERLY HP 8935)
TRANSMIT (TX) SET UP

POWER
SENSOR
100WATT (MIN)
NONRADIATING
RF LOAD
HPIB
TO GPIB
BOX
POWER
METER
(OPTIONAL)*
TX TEST
CABLE
COMMUNICATIONS
SYSTEM ANALYZER
OUT
TEST SET
INPUT/
OUTPUT
PORTS
30 DB
DIRECTIONAL
COUPLER
50
TERM.
CONTROL
IEEE 488
GPIB BUS
OR
TX TEST IN
10 DB MINIMUM
CABLE
INLINE ATTENUATOR
RF IN/OUT
TX
TEST
CABLE
ADVANTEST MODEL R3465

TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
* A POWER METER CAN BE

USED IN PLACE OF THE
COMMUNICATIONS TEST SET
FOR TX CALIBRATION/AUDIT
NOTE:
If BTS is equipped with
DRDCs (Duplexed RX/TX
Signals), connect the TX
test cable to the DRDC
antenna connector.
GPIB
CABLE
TRDC
GPIB
CONNECTS TO
BACK OF UNIT
INPUT 50
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
INTERNAL
TX
CABLE
TO
MPC
TO PA
TRUNKING
MODULE
DIP SWITCH SETTINGS
S MODE
DATA FORMAT
BAUD RATE
ON
BTS
LAN
A
LAN
B
GPIB ADRS
RS232GPIB
INTERFACE BOX
G MODE
RS232
NULL
MODEM
CABLE
10BASET/
10BASE2
CONVERTER
CDMA
LMF
UNSHIELDED TWISTED
PAIR (UTP) CABLE
(RJ45 CONNECTORS)
INTERNAL OR PCMCIA ETHERNET

NETWORK INTERFACE CARD (NIC)
FROM FW00094
SEP 2009
3-79
continued
Figure 3-16: TX Calibration Test Setup Using Power Meter

TEST SETS

POWER
SENSOR
NOTE:
The Advantest R3465 cannot be used for
TX Calibration. A Power Meter must be
used.
POWER METER
3
100WATT (MIN.)
NONRADIATING
RF LOAD
TX TEST
CABLE
DIRECTIONAL
COUPLER
(30 DB)
50
TERM.
1O DB MINIMUM
INLINE ATTENUATOR
TX TEST
CABLE
TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
TRDC
RX
RX
BTS ANT
CPLD CPLD
NOTE:
Signals), connect the TX test
cable to the DRDC antenna
connector.
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
INTERNAL
TX
CABLE
TO
MPC
TO PA
TRUNKING
MODULE
* BLACK RECTANGLES
REPRESENT THE RAISED
PART OF SWITCHES
DIP SWITCH SETTINGS
S MODE
DATA FORMAT
BAUD RATE
ON
BTS
GPIB ADRS
SYNC
MONITOR
LAN
A
G MODE
RS232GPIB
INTERFACE BOX
FREQ
MONITOR
LAN
B
GPIB
CABLE
RS232 NULL
MODEM
CABLE
CSM
10BASET/
10BASE2
CONVERTER
UNSHIELDED TWISTED PAIR (UTP)

CABLE (RJ45 CONNECTORS)
CDMA
LMF
INTERNAL PCMCIA
ETHERNET CARD
3-80
SEP 2009
continued
Figure 3-17: TX Calibration Test Setup Agilent E4406A and Advantest R3267
(IS95A/B and CDMA2000 1X)
TEST SETS
AGILENT E4406A
POWER
SENSOR
100WATT (MIN)
NONRADIATING
RF LOAD
POWER
METER
(OPTIONAL)*
TX TEST
CABLE
3
OUT
30 DB
DIRECTIONAL
COUPLER
50
TERM.
COMMUNICATIONS
SYSTEM ANALYZER
TEST SET
INPUT/
OUTPUT
PORTS
CONTROL
IEEE 488
GPIB BUS
OR
1O DB MINIMUM
INLINE ATTENUATOR
RF INPUT
50
TX
ANTENNA
CONNECTOR
TRDC
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
IN
* A POWER METER CAN BE

USED IN PLACE OF THE
COMMUNICATIONS TEST SET
FOR TX CALIBRATION/AUDIT
TX
TEST
CABLE
RX
ANTENNA
CONNECTOR
TX TEST
CABLE
INTERNAL
TX
CABLE
NOTE:
antenna connector.
DIP SWITCH SETTINGS
S MODE
DATA FORMAT
BAUD RATE
RF IN
TO
MPC
TO PA
TRUNKING
MODULE
GPIB
CABLE
ON
BTS
GPIB ADRS
LAN
B
LAN
A
G MODE
RS232GPIB
INTERFACE BOX
RS232
NULL
MODEM
CABLE
10BASET/
10BASE2
CONVERTER
CDMA
LMF
UNSHIELDED TWISTED
PAIR (UTP) CABLE
(RJ45 CONNECTORS)

FROM FW00094
SEP 2009
3-81
continued
Figure 3-18: TX Calibration Test Setup Agilent E7495A and E7495B (IS95A/B & CDMA2000 1X)
TEST SETS

POWER
SENSOR
AGILENT E7495A AND E7495B
TX TEST
CABLE
POWER METER
PORT 1
RF OUT
COMMUNICATIONS
SYSTEM ANALYZER
100WATT (MIN.)
NONRADIATING
OR
RF LOAD
INTERNAL
ETHERNET
CARD
PORT 2
RF IN
TX TEST
CABLE
30 DB
DIRECTIONAL
COUPLER
50
TERM.
1O DB MINIMUM
INLINE ATTENUATOR
GPIO
Port 2
RF In
Ext Ref
In
Power REF
50 MHz
Serial 1
Sensor
Even Second
Sync In
Serial 2
Use only
Agilent supplied
power adapter
TX TEST
CABLE
Port 1
RF Out / SWR
TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
GPS
Antenna
TRDC
PORT 2
RF IN
SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
NOTES:
1. WHEN USING THE E7495A, TX TESTS
REQUIRE A MINIMUM OF 30 DB
ATTENUATION PLUS THE CABLE
LOSSES.
2. IF BTS IS EQUIPPED WITH DRDCS
(DUPLEXED RX/TX SIGNALS), CONNECT
THE TX TEST CABLE TO THE DRDC
ANTENNA CONNECTOR.
ETHERNET HUB
INTERNAL
TX
CABLE
TO
MPC
TO PA
TRUNKING
MODULE
BTS
SYNC
MONITOR
LAN
A
LAN
B
CSM
10BASET/
10BASE2
CONVERTER

3-82
NOTE:
antenna connector.
CDMA
LMF

SEP 2009
continued
Figure 3-19: TX Calibration Test Setup Anritsu MT8212B (IS95A/B and CDMA2000 1X)
TEST SETS
ANRITSU MT8212B
RF OUT
50
COMMUNICATIONS
SYSTEM ANALYZER
100WATT (MIN.)
NONRADIATING
RF LOAD
SERIAL
INTERFACE
CONNECTOR
RF IN
50
TX AND
RX TEST
CABLE
RF IN
50
SERIAL
INTERFACE
30 DB
DIRECTIONAL
COUPLER
50
TERM.
1O DB MINIMUM
INLINE ATTENUATOR
TX AND
RX TEST
CABLE
TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
TRDC
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
RS232 SERIAL
INTERFACE CABLE
NOTE:
If BTS is equipped
with DRDCs
(Duplexed RX/TX
Signals), connect the
TX test cable to the
DRDC antenna
connector.
INTERNAL
TX
CABLE
TO
MPC
TO PA
TRUNKING
MODULE
BTS
SYNC
MONITOR
LAN
A
LAN
B
CSM
10BASET/
10BASE2
CONVERTER
CDMA
LMF
SEP 2009
3-83
continued
Setup for ATP
Figure 3-20 through Figure 3-28 show test set connections for
optimization/ATP tests.
Figure 3-20: ATP Test Setup, IS95A/B, TRDC Shown (Agilent 8935 and Advantest R3465)
TEST SETS
ATP TEST SET UP
AGILENT 8935 SERIES E6380A (FORMERLY HP 8935)

SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
FREQ MONITOR
19.6608 MHZ CLOCK
REFERENCE FROM
CSM BOARD
NOTE: If BTS is equipped with DRDCs

(Duplexed RX/TX Signals), both the TX
and RX test cables connect to the DRDC
antenna connector.
HPIB
TO GPIB
BOX
100WATT (MIN)
NONRADIATING
RF LOAD
RX
TEST
CABLE
OUT
COMMUNICATIONS
SYSTEM ANALYZER
TEST SET
CDMA
INPUT/ TIMEBASE
OUTPUT
IN
PORTS
EVEN
SECOND/SYNC
IN
IN
IEEE 488
GPIB BUS
DUPLEX OUT
50
TERM.
RF IN/OUT

SYNC MONITOR EVEN
SEC TICK PULSE
REFERENCE FROM
CSM BOARD
BNC
T
30 DB
DIRECTIONAL
COUPLER
FREQ MONITOR
19.6608 MHZ CLOCK
REFERENCE FROM
CSM BOARD
10 DB MINIMUM
INLINE ATTENUATOR
TX
TEST
CABLE
RF OUT 50
GPIB CONNECTS
TO BACK OF
UNIT
TRDC
INPUT 50
TO EXT TRIGGER CONNECTOR
ON REAR OF TEST SET
TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
DIP SWITCH SETTINGS
S MODE
DATA FORMAT
BAUD RATE
ON
BTS
GPIB ADRS
FREQ
MONITOR
SYNC
MONITOR
LAN
B
LAN
A
G MODE
RS232GPIB
INTERFACE BOX
RS232 NULL
MODEM
CABLE
CSM
10BASET/
10BASE2
CONVERTER
UNSHIELDED TWISTED
PAIR (UTP) CABLE
(RJ45 CONNECTORS)
CDMA
LMF

REF FW00096
3-84
SEP 2009
continued
(Agilent E4432B/8935 and Agilent E4432B/E4406A)
TEST SETS
OPTIMIZATION/ATP SET UP
RF OUTPUT 50
OR DUPLEX OUT
RX TEST
CABLE
AGILENT E4438C (TOP) AND 8935 SERIES E6380A

(BOTTOM)
RF
OUTPUT
50
RF IN/OUT
OR RF INPUT 50
100WATT (MIN.)
NONRADIATING
RF LOAD
SIGNAL GENERATOR
10 MHZ
IN
PATTERN
TRIG IN
GPIB
COMMUNICATIONS
SYSTEM ANALYZER
EXT
REF
IN
TRIGGER IN
OR
EVEN SEC
SYNCH IN
10 MHZ
OUT
GPIB
BNC
T
RF
IN/OUT
50
TERM.
BNC
T
SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
30 DB
DIRECTIONAL
COUPLER
FREQ MONITOR
19.6608 MHZ CLOCK
REFERENCE FROM
CSM BOARD
1O DB MINIMUM
INLINE ATTENUATOR
NOTES:
10 MHZ IN ON REAR OF SIGNAL GENERATOR IS CONNECTED TO
10 MHZ REF OUT ON SIDE OF CDMA BASE STATION TEST SET
PATTERN TRIG IN ON REAR OF SIGNAL GENERATOR IS
CONNECTED TO EVEN SECOND SYNC IN ON SIDE OF CDMA
BASE STATION TEST SET.
TX TEST
CABLE
RX
ANTENNA
CONNECTOR
AGILENT E4438C (TOP) AND E4406A

(BOTTOM)
TX
ANTENNA
CONNECTOR
GPIB
CABLE
TRDC
RF
OUTPUT
50
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
INTERNAL
TX
CABLE
* BLACK RECTANGLES
PART OF SWITCHES
DIP SWITCH SETTINGS
RF INPUT
50
TO PATTERN TRIG
IN ON REAR OF
SIGNAL
GENERATOR
TO TRIGGER IN
ON REAR OF
TRANSMITTER
TESTER
TO
MPC
TO PA
TRUNKING
MODULE
GPIB ADRS
FREQ
MONITOR
LAN
A
FREQ MONITOR
19.6608 MHZ CLOCK
REFERENCE FROM
CSM BOARD
10 MHZ IN ON REAR OF SIGNAL GENERATOR IS CONNECTED TO

10 MHZ OUT (SWITCHED) ON REAR OF TRANSMITTER TESTER
SEP 2009
G MODE
RS232GPIB
INTERFACE BOX
SYNC
MONITOR
LAN
B
NOTE:
ON
BTS
TO EXT REF IN
ON REAR OF
TRANSMITTER
TESTER
BNC
T
SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
S MODE
DATA FORMAT
BAUD RATE
RS232 NULL
MODEM
CABLE
CSM
10BASET/
10BASE2
CONVERTER

CDMA
LMF
INTERNAL PCMCIA ETHERNET

3-85
continued
Figure 3-22: ATP Test Setup, IS95A/B and CDMA2000 1X, with DRDC (Advantest R3267/3562)
TEST SETS
ATP TEST SET UP
ADVANTEST R3267 (TOP) AND R3562 (BOTTOM)

RF OUT
50
TO EXT TRIG
ON REAR OF
SPECTRUM
ANALYZER
SIGNAL GENERATOR
SYNTHE
EXT
MOD TIME
REF
TRIG IN
BASE IN
IN
GPIB
RX TEST
TEST
CABLE
SPECTRUM
ANALYZER
100WATT (MIN.)
NONRADIATING
RF LOAD
INPUT 50
INPUT
50
10 MHZ
OUT
EXT TRIG
GPIB
BNC
T
TX TEST
RF OUT
50
50
TERM.
BNC
T
30 DB
DIRECTIONAL
COUPLER
FREQ MONITOR
19.6608 MHZ CLOCK
REFERENCE FROM
CSM BOARD
1O DB MINIMUM
INLINE ATTENUATOR
SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
TX TEST
CABLE
NOTE:
DUPLEXED
TX/RX
ANTENNA
CONNECTOR
SYNTHE REF IN ON REAR OF SIGNAL GENERATOR IS

CONNECTED TO 10 MHZ REF OUT ON REAR OF
SPECTRUM ANALYZER
GPIB
CABLE
DRDC
ANT
CPLD
BTS
CPLD
INTERNAL
RX
CABLE
INTERNAL
TX
CABLE
* BLACK RECTANGLES
PART OF SWITCHES
DIP SWITCH SETTINGS
TO
MPC
TO PA
TRUNKING
MODULE
BTS
FREQ
MONITOR
ON
GPIB ADRS
G MODE
RS232GPIB
INTERFACE BOX
SYNC
MONITOR
LAN
B
S MODE
DATA FORMAT
BAUD RATE
RS232 NULL
MODEM
CABLE
CSM
LAN
A
CDMA
LMF
UNSHIELDED TWISTED
PAIR (UTP) CABLE
(RJ45 CONNECTORS)
3-86

SEP 2009
continued
Figure 3-23: ATP Test Setup, IS95A/B and CDMA2000 1X, with TRDC (Advantest R3267/3562)
RX TEST
CABLE
Advantest R3267 (Top) and R3562 (Bottom)
RF OUT
50
SIGNAL GENERATOR
MOD TIME
BASE IN
TO EXT TRIG
ON REAR OF
SPECTRUM
ANALYZER
EXT
TRIG IN
SYNTHE
REF
IN
GPIB
10 MHZ
OUT
SPECTRUM
ANALYZER
100WATT (MIN.)
NONRADIATING
RF LOAD
INPUT 50
INPUT
50
EXT TRIG
GPIB
BNC
T
BNC
T
50
TERM.
RF OUT
50
30 DB
DIRECTIONAL
COUPLER
1O DB MINIMUM
INLINE ATTENUATOR
FREQ MONITOR
19.6608 MHZ CLOCK
REFERENCE FROM
CSM BOARD
TX TEST
CABLE
SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
RX
ANTENNA
CONNECTOR
NOTE:
SYNTHE REF IN ON REAR OF SIGNAL GENERATOR IS
CONNECTED TO 10 MHZ REF OUT ON REAR OF
SPECTRUM ANALYZER
RX
BTS
CPLD
TX
ANTENNA
CONNECTOR
GPIB
CABLE
TRDC
RX
ANT
CPLD
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
INTERNAL
TX
CABLE
* BLACK RECTANGLES
PART OF SWITCHES
DIP SWITCH SETTINGS
TO
MPC
TO PA
TRUNKING
MODULE
S MODE
DATA FORMAT
BAUD RATE
ON
BTS
GPIB ADRS
FREQ
MONITOR
SYNC
MONITOR
LAN
B
LAN
A
G MODE
RS232GPIB
INTERFACE BOX
RS232 NULL
MODEM
CABLE
CSM
10BASET/
10BASE2
CONVERTER
CDMA
LMF

SEP 2009
3-87
continued
Figure 3-24: IS95A/B and CDMA2000 1X Optimization/ATP Test Setup Agilent E7495A and E7495B
ATP TEST SET UP
TEST SET
POWER METER
AGILENT E7495A AND E7495B

RX TEST
(SEE NOTES FOR RX TEST
ATTENUATION SELECTION)
100WATT (MIN.)
NONRADIATING
RF LOAD
RF INPUT 50
OR INPUT 50
PORT 1
RF OUT
EVEN SECOND
SYNC IN
COMMUNICATIONS
SYSTEM ANALYZER
PORT 2
RF IN
TX TEST
INTERNAL
ETHERNET
CARD
DIRECTIONAL
COUPLER
(30 DB)
50
TERM
TX TEST: 10 DB MINIMUM
INLINE ATTENUATOR
GPIO
Port 2
RF In
Ext Ref
In
Power REF
50 MHz
Serial 1
Sensor
Even Second
Sync In
Serial 2
PORT 2
RF IN
SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
TEST
CABLES
Use only
Agilent supplied
power adapter
TX TEST
Port 1
RF Out / SWR
GPS
Antenna
TRDC
PORT 1
RF OUT
RX
RX
BTS ANT
CPLD CPLD
NOTES:
1. FOR RX TESTING, TOTAL RF PATH ATTENUATION
(CABLES+COUPLERS+ATTENUATORS) MUST BE
WITHIN THE VALUES SPECIFIED BELOW FOR EACH
TYPE OF TEST SET:
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
INTERNAL
TX
CABLE
TO
MPC
E7495A: 25 TO 32 dB
E7495B: 10 TO 100 dB
2. WHEN USING THE E7495A, TX TESTS REQUIRE A
MINIMUM OF 30 DB ATTENUATION PLUS THE CABLE
LOSSES.
3. USE THE SAME CABLE SET FOR TX AND RX ATP.
SWITCH THE CABLES DURING ALL ATP TESTS AS
SHOWN.
ETHERNET HUB
TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
LAN
A
LAN
B
TO PA
TRUNKING
MODULE
SYNC
MONITOR
10BASET/
10BASE2
CONVERTER
CSM
BTS
UNIVERSAL TWISTED PAIR (UTP)

CDMA
LMF
INTERNAL PCMCIA
ETHERNET CARD
4. IF BTS IS EQUIPPED WITH DUPLEXED RX/TX

SIGNALS, CONNECT THE TX TEST CABLE TO THE
DUPLEXED ANTENNA CONNECTOR.
3-88
SEP 2009
continued
Figure 3-25: ATP Test Setup IS95A/B and CDMA2000 1X (Anritsu MT8212B)
TEST SET
ANRITSU MT8212B
FREQ MONITOR
19.6608 MHZ CLOCK
REFERENCE FROM
CSM BOARD
RX TEST
SYNC MONITOR
EVEN SEC TICK
PULSE REFERENCE
FROM CSM BOARD
RF OUT
50
(SEE NOTES FOR RX TEST

COMMUNICATIONS
SYSTEM ANALYZER
100WATT (MIN.)
NONRADIATING
RF LOAD
RF IN
50
SERIAL
INTERFACE
TX TEST
SERIAL
INTERFACE
CONNECTOR
RF IN
50
30 DB
DIRECTIONAL
COUPLER
RF OUT
50
50
TERM.
TX TEST: 1O DB MINIMUM
INLINE ATTENUATOR
RX TEST (RSSI): 35 DB
MINIMUM INLINE
ATTENUATOR
TX TEST
RX
ANTENNA
CONNECTOR
TX
ANTENNA
CONNECTOR
RS232 SERIAL
INTERFACE CABLE
TRDC
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
INTERNAL
RX
CABLE
NOTES:
1. USE THE SAME CABLE SET FOR TX
AND RX ATP. SWITCH THE CABLES
DURING ATP TESTS AS SHOWN.
2. FOR RX TESTING (RSSI), TOTAL RF
PATH ATTENUATION
(CABLES+COUPLERS+ATTENUATORS)
MUST BE 65 dB OR GREATER.
INTERNAL
TX
CABLE
TO
MPC
TO PA
TRUNKING
MODULE
FREQ
MONITOR
SYNC
MONITOR
CSM
LAN
A
LAN
B
BTS
10BASET/
10BASE2
CONVERTER
CDMA
LMF

SEP 2009
3-89
continued
Figure 3-26: Alternate ATP Test Setups (Except Agilent E7495A/B and Anritsu MT8121B)
RX TEST CABLE
SIGNAL
GENERATOR
OUT
ANTENNA CABLE
REMOVED FOR
TESTING
100WATT (MIN.)
NONRADIATING
RF LOAD
TX TEST
CABLE
3
RX TESTING
TX TESTING
IN
TX TEST
CABLE
DIRECTIONAL
COUPLER
(30 DB)
50
TERM.
50
TERM.
COMMUNICATIONS
SYSTEM ANALYZER
EVEN
SEC IN
REF IN
50
TERM.
50
TERM.
TX TEST
CABLE
TX
TESTING
OPTIONAL
EXTERNAL
DIRECTIONAL
COUPLERS
RX ANTENNA
CONNECTOR
1O DB MINIMUM
INLINE
ATTENUATOR
50
TERM.
OR
TX & RX
TESTING
TX ANTENNA
CONNECTOR
DUPLEXED
TX/RX
ANTENNA
CONNECTOR
GPIB
CABLE
INTERNALTX
CABLE TO PA
TRUNKING
MODULE
INTERNAL
RX CABLE
TO MPC
* BLACK RECTANGLES
PART OF SWITCHES
DIP SWITCH SETTINGS
S MODE
DATA FORMAT
BAUD RATE
ON
FREQ
MONITOR
FREQ
MONITOR
SYNC
MONITOR
SYNC
MONITOR
CSM
CSM
LAN
B
LAN
A
10BASET/
10BASE2
CONVERTER
GPIB ADRS
10BASET/
10BASE2
CONVERTER
UNSHIELDED TWISTED PAIR (UTP) CABLE (RJ45 CONNECTORS)
BTS WITHOUT DUPLEXED

RX &TX PORTS
3-90
RS232 NULL
MODEM
CABLE
LAN
B
LAN
A
BTS WITH DUPLEXED

RX &TX PORTS
G MODE
RS232GPIB
INTERFACE BOX
CDMA
LMF

SEP 2009
continued
Figure 3-27: Alternate ATP Test Setups (Agilent E7495A or E7495B)

(SEE NOTE FOR RX TEST
ANTENNA CABLE
REMOVED FOR
TESTING
PORT 1
RF OUT
100WATT (MIN.)
NONRADIATING
RF LOAD
OUT
TX TEST
CABLE
TX TEST
CABLE
PORT 2
RF IN
IN
OR
RX TESTING
TX TESTING
50
TERM.
COMMUNICATIONS
SYSTEM ANALYZER
INTERNAL
ETHERNET NIC
DIRECTIONAL
COUPLER
(30 DB)
50
TERM.
50
TERM.
INLINE ATTENUATOR
50
TERM.
50
TERM.
NOTES:
OPTIONAL
EXTERNAL
DIRECTIONAL
COUPLERS
RX ANTENNA
CONNECTOR
POWER METER
OR
TX & RX
TESTING
TX ANTENNA
CONNECTOR
1. FOR RX TESTING, TOTAL RF PATH

ATTENUATION
MUST BE WITHIN THE VALUES
SPECIFIED BELOW FOR EACH TYPE
OF TEST SET:
E7495A: 25 TO 32 dB
DUPLEXED
TX/RX
ANTENNA
CONNECTOR
E7495B: 10 TO 100 dB
2. WHEN USING THE E7495A, TX
TESTS REQUIRE A MINIMUM OF 30 DB
LOSSES.
INTERNALTX
CABLE TO PA
TRUNKING
MODULE
INTERNAL
RX CABLE
TO MPC
ETHERNET HUB
LAN
B
LAN
A
LAN
B
LAN
A
10BASET/
10BASE2
CONVERTER
10BASET/
10BASE2
CONVERTER

RX & TX PORTS
SEP 2009
BTS WITH DUPLEXED

RX & TX PORTS
CDMA
LMF

3-91
continued
Figure 3-28: Alternate ATP Test Setups (Anritsu MT8212B)

NOTES:
1. USE THE SAME CABLE SET FOR TX AND RX ATP.
SWITCH CABLES DURING ALL ATP TESTS AS SHOWN.
ANTENNA CABLE
REMOVED FOR
TESTING
2.FOR RX TESTING (RSSI) TOTAL RF PATH ATTENUATION

(CABLES + COUPLERS + ATTENUATORS) MUST BE 65 DB
OR GREATER.
100WATT (MIN.)
NONRADIATING
RF LOAD
RF OUT
50
RX TEST
OUT
TX AND RX
TEST CABLE
IN
OR
RX TESTING
TX TESTING
50
TERM.
DIRECTIONAL
COUPLER
(30 DB)
50
TERM.
50
TERM.
50
TERM.
TX TEST
OR
TX & RX
TESTING
TX ANTENNA
CONNECTOR
DUPLEXED
TX/RX
ANTENNA
CONNECTOR
LAN
B
RS232 SERIAL
INTERFACE CABLE
INTERNALTX
CABLE TO PA
TRUNKING
MODULE
INTERNAL
RX CABLE
TO MPC
LAN
B
LAN
A
10BASET/
10BASE2
CONVERTER
10BASET/
10BASE2
CONVERTER

RX & TX PORTS
3-92
SERIAL
INTERFACE
RX TEST (RSSI): 35 DB
MINIMUM INLINE
ATTENUATOR
OPTIONAL
EXTERNAL
DIRECTIONAL
COUPLERS
LAN
A
RF IN
50
INLINE ATTENUATOR
50
TERM.
RX ANTENNA
CONNECTOR
COMMUNICATIONS
SYSTEM ANALYZER
BTS WITH DUPLEXED

RX & TX PORTS
CDMA
LMF

SEP 2009
Test Equipment Connection to the LMF

Test Equipment Connection
The LMF computer platform provides two types of hardware interfaces

which support three different test equipment communication methods.
S The COM hardware interface (RS232) supports connection with both

the General Purpose Interface Bus (GPIB) and direct serial
communication methods.
S The Ethernet interface supports the network test equipment

communication method.
Additional information on each interface type is provided in the

following subsections.
COM Port Interface
The LMF computer RS232 serial bus interfaces are designated as COM
connections or ports in software. These interfaces support
communication with test equipment connected to the LMF computer
directly with a serial cable or through a GPIB interface device (GPIB
box). The LMF normally uses COM1 for the interface. COM2 is not
used unless the LMF computer has two RS232 connectors. The COM
port selected in the LMF can not be used for any other purpose when the
LMF is using it.
Selecting the COM port Perform the following to select a COM port
for use with test equipment needing a GPIB or direct serial connection:
Table 3-25: Selecting a COM Port for GPIB or Serial Test Equipment Connection
Step
Action
From the LMF window menu bar select Tools > Options.
Result: The LMF Options window opens.
If the Test Equipment tab is not in the forefront, click the tab to bring it forward.
Click in the COM radio button in the GPIB/COM settings area.

Result: A black dot appears in the circle.
Select the COM port to use (normally COM1) from the dropdown in the Port: box of the GPIB/COM
settings area.
Click the Save button to save the selection configuration for future LMF sessions.
Click the Close button to close the LMF Options window.
SEP 2009
3-93
continued
Disconnecting and Reconnecting the LMF and the COM port The
LMF can be disconnected from the active COM port by using the
Disconnect Port button in the GPIB/COM settings area of the Test
Equipment tab. Disconnecting the LMF may be needed, for example, to
use a HyperTerminal connection for a hardware Man Machine Interface
(MMI) communication session.
Perform the following to disconnect or reconnect the LMF and the
selected COM port.
Table 3-26: Disconnect and Reconnect the LMF and the Active COM Port
Step
Action
From the LMF window menu bar select Tools > Options.
Result: The LMF Options window opens.
If the Test Equipment tab is not in the forefront, click the tab to bring it forward.
Disconnect the LMF from the active COM port: click the Disconnect Port button in the GPIB/COM
settings area.
Reconnect the LMF to the active COM port: click the Detect button in the GPIB Test equipment or
Serial Test Equipment area.
If no other operations are required in the LMF Options window click Close to close the window.
Ethernet Interface
The LMF computer Ethernet interface supports communication with test
equipment which uses the network connection method. This interface
uses Internet Protocol (IP) addressing to differentiate each node on the
network. Motorola recommends that Ethernet connection of the test
equipment and the LMF computer be done though an Ethernet hub
which includes both 10/100BaseT and coaxial 10Base2 connections.
The hub connects to the LMF computer, the test equipment and the BTS.
Connection details are as follows:
Test equipment to hub This is an Unshielded Twisted Pair (UTP)
Ethernet cable with two 10/100BaseT 8contact modular connectors.
LMF to Hub Use one of the following cables to connect the LMF to
the Hub:
S Ethernet cable. Be sure the LMF computer Network Interface Card
(NIC) is set for either AUTO or to use the 8contact modular
connector only.
S Coaxial cable between NIC and Hub. Use a 10Base2 (BNC) tee
connector on the hub. If the hub does not have BNC connectors, use a
BNCtoUTP adapter with the tee connector. Connect a coaxial cable
between the LAN card and one end of the BNC tee crossbar.
Hub to BTS With a BNC tee connector on the hub, connect a coaxial
cable between the open end of the T crossbar and the BTS LAN
connection.
3-94
SEP 2009
continued
Addressing Methods
Different addressing methods are used for test equipment depending on

the type of interface connection it has. The different addressing methods
are described in the following subsections.
GPIB Addresses
GPIB addresses can range from 1 through 30. The LMF will accept any
address in that range, but the numbers entered in the LMF Options
window GPIB address box must match the addresses set in the test
equipment. Motorola recommends using 1 for a CDMA signal generator,
13 for a power meter, and 18 for a communications system analyzer. To
verify and, if necessary, change the GPIB addresses of the test
equipment, refer to the Setting GPIB Addresses sections of Appendix F.
Serial Connection
This connection type uses a direct serial connection between the test
equipment and the LMF computer platform. The Anritsu MT8212B
communications test set is an example of test equipment using this type
of connection. There are no specific addressing requirements for this
type of interface.
IP Addresses
Test equipment using the Network connection type use IP addresses to
identify them on the Ethernet Local Area Network (LAN). The E7495A
and E7495B communications test sets are examples of Network
connection test equipment. Setting the IP address in the test equipment is
covered in the specific test equipment (for example, Agilent E7495)
setup section of Appendix F.
SEP 2009
3-95
Test Equipment Selection

Test equipment selection is performed in the LMF Options window,

accessed through Tools > Options in the LMF window menu bar. The
window has four tabs covering different categories of options. Test
equipment operations, including selection, are performed on the Test
Equipment tab. For software release 2.20.0.x (R20), the test equipment
list displayed on this tab is context sensitive based on the Connection
type selected.
S When GPIB is selected, only test equipment with a GPIB interface is
displayed.
S When Serial is selected, only test equipment needing a direct serial

connection is displayed.
S When Network is selected, only test equipment needing an Ethernet

connection is displayed.
Manual and Autodetect

Selection
Test equipment can be manually specified before or after the test

equipment is connected. The LMF does not try to determine if the test
equipment is actually connected for manual selection. The LMF can be
commanded to automatically detect test equipment connected to it. This
autodetection feature is operated by a Detect button located in the test
equipment list area for each connection type (GPIB, Serial, or Network).
Selecting Test Equipment
There is a different set of test equipment selection procedures for each

test equipment connection type. These are:
S GPIB connection
S Serial connection
S Network (Ethernet) connection
Selection Procedures
Test equipment selection procedures are contained in the following

subsections. Each subsection is for a different connection type. Each
subsection includes a procedure for manually specifying test equipment
items and a procedure to have the LMF automatically detect the
connected test equipment.
GPIB Interface Test Equipment Manual Selection and
Autodetection
Prerequisites The following must be done before performing these
procedures:
S LMF computer and test equipment are both correctly connected to the
GPIB box
3-96
SEP 2009
continued
S Test equipment is turned on

S GPIB addresses set in the test equipment have been verified as correct
using the applicable procedures in Appendix F.
Manual selection Test equipment may be selected manually even if it

is not connected to the LMF.
Table 3-27: Manually Selecting Test Equipment GPIB Interface
Step
Action
In the LMF menu bar, select Tools > Options.

Result: The LMF Options window appears.
Click on the Test Equipment tab (if not in the forefront).
Click the GPIB radio button in the Connection Type area.

Click the COM radio button in the GPIB/COM settings area.

Select the correct LMF computer serial port from the Port: pick list (normally COM1) (Refer to the
Test Equipment Connection to the LMF section of this chapter).
In the GPIB Test equipment area click the checkbox(es) of the test equipment being used.
Result: Checkmarks appear in the boxes clicked on.
If one is not already displayed, type the GPIB address for each checked piece of test equipment in the
corresponding box labeled GPIB.
Recommended Addresses
1 = CDMA Signal generator
13 = Power Meter
18 = CDMA Analyzer
NOTE
When the test equipment items are manually selected, the CDMA analyzer is used only if a power
meter is not selected.
8
Click the Apply button. The button will darken until the selection is committed.
Click the Detect on startup checkbox in the Autodetection settings area to allow the LMF to detect
the test equipment automatically on application startup.
Result: A checkmark appears in the box.
10
11
NOTE
When two devices of the same type have been selected, a window will appear warning that more than
one signal generator/power meter/ analyzer has been chosen. Click the Continue button to close this
window. The checkbox can be clicked to prevent the window from being displayed again, if desired.
SEP 2009
3-97
continued
Automatically Selecting Test Equipment (Autodetection) When

using the autodetection feature to select test equipment, the LMF
determines which test equipment items are actually communicating with
the LMF.
Table 3-28: Autodetecting Test Equipment GPIB Interface
Step
Action

Click the GPIB radio button in the Connection Type area.


If they are not already displayed, enter the GPIB address for each piece of required test equipment,
separated by commas, in the GPIB Addresses: box in the GPIB Test equipment area.
Recommended Addresses
1 = CDMA Signal generator
13 = Power Meter
18 = CDMA Analyzer
NOTE
In autodetection when both a power meter and a CDMA analyzer are selected, the LMF uses the first
item that is capable of performing RF power measurement listed in the GPIB Addresses: box. The
address for a CDMA signal generator is normally 1, the address for a power meter is normally 13, and
the address for a CDMA analyzer is normally 18. If 1,13,18 is listed in the GPIB Addresses: box, the
power meter (13) is used for RF power measurements. When the test equipment items are manually
selected, the CDMA analyzer is used only if a power meter is not selected.
7
Click the Detect button. The button will darken until the selection is committed.
Result: For each detected equipment item, a check will appear in its checkbox and its GPIB address
will appear in its GPIB box.
10
NOTE
When two devices of the same type have been selected, a window will appear warning that more than
one signal generator/power meter/ analyzer has been chosen. Click the Continue button to close this
window. The checkbox can be clicked to prevent the window from being displayed again, if desired.
3-98
SEP 2009
continued
Serial Interface Test Equipment Manual Selection and

Autodetection
procedures:
S Test equipment is correctly connected to the LMF computer RS232

connector with a serial cable

Table 3-29: Manually Selecting Test Equipment Serial Interface
Step
Action

Click the Serial radio button in the Connection Type area.


In the Serial Test equipment area click the checkbox(es) of the test equipment being used.
Result: Checkmarks appear in the box(es) clicked on.
10

SEP 2009
3-99
continued

the LMF.
Table 3-30: Autodetecting Test Equipment Serial Interface
Step
Action

Click the Serial radio button in the Connection Type area.


Choose the test equipment on the Serial Test Equipment list by clicking the corresponding checkbox.
Result: For each detected equipment item, a check will appear in its checkbox.
10
Network Interface Test Equipment Manual Selection and

Autodetection
procedures:
S Be sure that no other equipment is connected to the LMF.

S Test equipment is correctly connected to the LMF computer through
the Ethernet LAN
S The IP address is set in the test equipment as specified in the test
equipment model (for example, Agilent E7495) setup section of

Appendix F.

S TURN OFF any firewall software installed on the LMF computer
platform
3-100
SEP 2009
continued

Table 3-31: Manually Selecting Test Equipment Network Interface
Step
Action

Click the Network radio button in the Connection Type area.

In the Ethernet Test equipment area click the checkbox(es) of the test equipment being used.
Result: Checkmarks appear in the box(es) clicked on.
If it is not already displayed, enter the IP address for the required piece test equipment in the IP box
in the Ethernet Test equipment area.

the LMF.
Table 3-32: Autodetecting Test Equipment Network Interface
Step
Action

Click the Network radio button in the Connection Type area.

If it is not already displayed, enter the IP address for the required piece test equipment in the IP box
in the Ethernet Test equipment area.
Result: For each detected equipment item, a check will appear in its checkbox.
SEP 2009
3-101
continued
Table 3-32: Autodetecting Test Equipment Network Interface

Step
Action
3-102
SEP 2009
Test Set Calibration

Background
Proper test equipment calibration ensures that the test equipment and
associated test cables do not introduce measurement errors, and that
measurements are correct.
NOTE
If the test set being used to interface with the BTS has been
calibrated and maintained as a set, this procedure does not
need to be performed. (Test Set includes LMF terminal,
communications test set, additional test equipment,
associated test cables, and adapters.)
This procedure must be performed before beginning the optimization.
Verify all test equipment (including all associated test cables and
adapters actually used to interface all test equipment and the BTS) has
been calibrated and maintained as a set.
CAUTION
If any piece of test equipment, test cable, or RF adapter,
that makes up the calibrated test equipment set, has been
replaced, re-calibration must be performed. Failure to do so
can introduce measurement errors, resulting in incorrect
measurements and degradation to system performance.
NOTE
calibrating the overall test equipment set. Calibrate the test
equipment after it has been allowed to warm up and
stabilize for a minimum of 60 minutes.
SEP 2009
3-103
continued
Calibration Procedures
Included
Automatic
Procedures included in this section use the LMF automated calibration
routines to determine path losses of the supported communications
analyzer, power meter, associated test cables, adapters, and (if used)
antenna switch that make up the overall calibrated test equipment set.
After calibration, the gain/loss offset values are stored in a test
measurement offset file on the LMF computer.
Manual
Agilent E4406A Transmitter Tester The E4406A does not support
the power level zeroing calibration performed by the LMF. If this
instrument is to be used for Bay Level Offset calibration and calibration
is attempted with the LMF Calibrate Test Equipment function, the
LMF will return a status window failure message stating that zeroing
power is not supported by the E4406A. Refer to the Test Equipment
Calibration Agilent E4406A Selfalignment section of Appendix F for
instructions on using the instruments selfalignment (calibration)
function prior to performing Bay Level Offset calibration.
Power Meter Manual power meter calibration procedures to be
performed prior to automated calibration are included in the Test
Equipment Calibration Gigatronics 8542 Power Meter section of
Appendix F.
Prerequisites
S Test equipment is correctly connected and turned on.

S Test equipment addressing is set as required for the connection type
being used (GPIB, Serial, Network)
Calibrate Test Equipment

Function (Except Agilent
E4406A and Anritsu MT8212B)
The Calibrate Test Equipment function zeros the power measurement

level of the test equipment item to be used for TX calibration and audit.
If both a power meter and an analyzer are connected, only the power
meter is zeroed.
3-104
SEP 2009
continued
NOTE
1. The Agilent E4406A transmitter tester does not
support power measurement level zeroing. Refer to the
Test Equipment Calibration section of Appendix F for
E4406A calibration.
2. Power measurement zeroing and other required
calibration procedures for the Anritsu MT8212B are
included in the Calibrating the Anritsu MT8212B
subsection below.
Prerequisites
S Test equipment to be zeroed has been connected correctly for tests to
be run.
S Test equipment has been selected in the LMF (Table 3-27, Table 3-28,
Table 3-29, Table 3-30, Table 3-31, or Table 3-32) and detected.
Procedure
Follow the procedure in Table 3-33 to calibrate the test equipment.
Table 3-33: Calibrate Test Equipment Power Measurement Zeroing
Step
Action
From the Util menu, select Calibrate Test Equipment from

the pulldown menu. A Directions window is displayed.
Follow the directions provided.
Click on Continue to close the Directions window and start

the calibration process. A status report window is displayed.
Calibrating the Anritsu

MT8212B
Three types of calibration are required for the MT812B. These are:
S Zero out power meter

S Calibrate TX Analyzer
S Calibrate CW Generator
Procedures for each type of calibration is covered in the following
subsections.
Zero Out Power Meter
Before using the MT8212B test set to perform RF power measurement,
the test set internal power meter function must be zeroed.
SEP 2009
3-105
continued
Prerequisites The following must be done before the zeroing out the
power meter:
S The test set is connected to the LMF computer serial port with the
Anritsu 800441 RS232 serial interface cable
S Test equipment is turned on and has warmed up for at least 60

minutes.
S Test equipment has been selected/detected in the LMF (Table 3-29 or

Table 3-30)
Zero out power meter Perform the following to zero out the power
meter function before performing RF power measurements.
Table 3-34: Anritsu MT8212B Multifunction Test Set Zero Out Power Meter
Step
Action
In the LMF menu bar select Util > Calibrate Test Equipment.
Calibrate Anritsu MT8212B window appears
Click in the Option for zero out power meter on Anritsu MT8212B radio button in the Zero Out
Power Meter area.
A black dot appears in the circle.
Click on OK.
A Directions window is displayed.

A status report window will open.
Calibrate TX Analyzer
TX Analyzer calibration should be accomplished before performing any
ATP operations with the MT8212B.
Prerequisites The following must be done before the CW generator
calibration:

Table 3-30)
S Additional items must be available for the TX Analyzer calibration

method chosen as indicated in the following:
1. Standard OpenShortLoad Components calibration:
Anritsu 22N50 Open/Short, DC to 18 GHz, N(m) connector, 50
ohm
Anritsu SM/PL precision load, DCto4 GHz, 42 dB, N(m)
connector, 50 ohm
3-106
SEP 2009
continued
2. Standard InstaCalt calibration:

Anritsu ICN50 InstaCal calibration module, 2 MHz to 4 GHz, N(m)
connector, 50 ohm
TX analyzer calibration Perform the following to calibrate the
MT8212B TX analyzer function..
Table 3-35: Anritsu MT8212B Multifunction Test Set TX Analyzer Calibration
Step
Action
Result: Calibrate Anritsu MT8212B window appears
Click in the radio button in the Calibrate TX Analyzer area.

Select the required frequency band from the dropdown list in the Frequency Band: box.
NOTE
The dropdown list in the Frequency Band: box is automatically populated with selections for the
BTS the LMF is logged into.
4
Enter the channel number to be calibrated in the Channel box.
Select the desired calibration method from the dropdown list in the Calibration Method box.
Click OK.
Result: A Directions window is displayed.
When actions required by directions have been completed, click on Continue to close the Directions
window and start the generator calibration process.
Result: A status report window is displayed.
Calibrate CW Generator
Before using the MT8212B test set to perform BTS RSSI testing, the
test set internal Continuous Wave (CW) generator must be calibrated.
Prerequisites The following must be done before the CW generator
calibration:
minutes.
Table 3-30)
S RX cable(s) used in the calibration process must be calibrated for the
channel for which the CW generator is to be calibrated (refer to
Figure 3-32 and Table 3-38)
SEP 2009
3-107
continued
CW generator calibration Perform the following to calibrate the

MT8212B internal CW generator before performing RSSI testing with
this test set.
Table 3-36: Anritsu MT8212B Multifunction Test Set CW Generator Calibration
Step
Action
Result: Calibrate Anritsu MT8212B window appears
Click in the radio button in the Calibrate CW Generator area.

Select the required frequency band from the dropdown list in the Frequency Band: box.
NOTE
The dropdown list in the Frequency Band: box is automatically populated with selections for the
BTS the LMF is logged into.
4
Enter the channel or channels to be calibrated in the Channel(s) box (separate multiple channels with
a comma and no space).
NOTE
When two or more channels numbers are entered, the generator will be calibrated for each channel.
Interpolation will be accomplished for other channels as required for TX calibration. Channels must be
within the range of the selected frequency band.
5
Click OK.
Result: A Directions window is displayed.
When actions required by directions have been completed, click on Continue to close the Directions
window and start the generator calibration process.
3-108
SEP 2009
Setting and Editing Generator Calibration Data

Generator Calibration Data
Generator calibration data is automatically stored in a generator

calibration data file by the LMF when the generator function of a test
equipment item is calibrated using the LMF Util > Calibrate Test
Equipment functions. Stored data values can be edited with this
procedure, or new data can be entered manually for a test equipment
item generator function which was calibrated without using the LMF.
CAUTION
This procedure MUST be used to enter calibration data
values for any MT8212B which was calibrated without
using the LMF. Failure to do this will generate incorrect
results for any RSSI testing performed.
Prerequisites
The LMF is logged into a BTS.
Set or Edit Generator Calibration Data
Perform the following to enter new calibration data or edit existing data.
Table 3-37: Set or Edit Generator Calibration Data
Step
Action
In the LMF menu bar select Util > Edit > Generator Calibration Data.
Generator Calibration Data window appears with tabs for each type of generator test equipment
calibrated using the LMF (for example, the Anritsu MT8212B)
Click on the tab for the generator with data to be edited or entered.
The tab moves to the forefront.
To edit existing values, click in the data field to be edited and make required changes.
To add a new channel and its data:

1. Click the Add Row button.
2. Click in the field where data is to be entered; for example, Frequency Band, Channel #, or Power
(dB).
3. Enter the desired value.
NOTE
For Frequency Band fields, select the required frequency band from the dropdown provided.
Selections are made available for the BTS which the LMF is logged into.
SEP 2009
3-109
continued
Table 3-37: Set or Edit Generator Calibration Data

Step
Action
To delete a row, click in the row, and then click the Delete Row button.
For each tab with changes, click the Save button to save the displayed values.
NOTE
S Values entered after the Save button was used will not be saved.
S If generator calibration values exist for two different channels assigned to one frequency band, the
LMF will interpolate for all other channels on this frequency band.
S Entered values will be used by the LMF as soon as they are saved. It is not necessary to log out and
log back into the LMF for changes to take effect.
3-110
SEP 2009
Cable Calibration
Cable Calibration
Automatic
Procedures included in this section use the LMF automated calibration
routines to determine path losses of the supported communications
analyzer, power meter, associated test cables, adapters, and (if used)
antenna switch that make up the overall calibrated test equipment set.
After calibration, the gain/loss offset values are stored in a test
measurement offset file on the LMF computer.
Manual
Also included in this section are manual cable and directional coupler
calibration procedures using a signal generator and spectrum analyzer to
determine the path losses of cables which will be used in a test
equipment set. When these procedures are used, the cable loss values
established in the calibration process must be manually entered into the
LMF. The manual entry procedures are also included in this section
under Setting Cable Loss Values.
In addition, manual cable calibration procedures using the Advantest
R3465 communications system analyzer are provided in the Manual
Cable Calibration section of Appendix F, if needed.
Calibrating Cables Overview
The cable calibration function measures the loss (in dB) for the TX and
RX cables that are to be used for testing. A CDMA analyzer is used to
measure the loss of each cable configuration (TX cable configuration and
RX cable configuration). The cable calibration consists of the following:
S Measuring the loss of a short cable This is required to compensate

for any measurement error of the analyzer. The short cable (used only
for the calibration process) is used in series with both the TX and RX
cable configuration when measuring. The measured loss of the short
cable is deducted from the measured loss of the TX and RX cable
configuration to determine the actual loss of the TX and RX cable
configurations. The result is then adjusted out of both the TX and RX
measurements to compensate for the measured loss.
S Measuring the short cable plus the RX cable configuration loss
The RX cable configuration normally consists only of a coax cable

with type-N connectors that is long enough to reach from the BTS RX
port of the test equipment. Refer to Figure 3-29, Figure 3-30,
Figure 3-31, or Figure 3-32 for specific cable and connection
requirements for each type of communications system analyzer.
S Measuring the short cable plus the TX cable configuration loss
The TX cable configuration normally consists of two coax cables with

type-N connectors and a directional coupler, a load, and an additional
attenuator (if required by the specified BTS). The total loss of the path
loss of the TX cable configuration must be as required for the BTS
(normally 30 or 50 dB). Refer to Figure 3-29, Figure 3-30,
SEP 2009
3-111
Cable Calibration
continued
Figure 3-31, or Figure 3-32 for specific cable and connection

requirements for each type of communications system analyzer.
Cable Calibration Setup
Diagrams
Figure 3-29, Figure 3-30, Figure 3-31, and Figure 3-32 show the cable
calibration setup for various supported test sets. The left side of the
diagram depicts the location of the input and output ports of each test
set, and the right side details the set up for each test.
3
Calibrate Test Cabling Using
Communications System
Analyzer
Cable Calibration is used to calibrate both TX and RX test cables.

Appendix F covers the procedures for manual cable calibration.
Prerequisites
S One of the following:

LMF computer serial port and test equipment are connected to the
GPIB box
For MT8212B, the test equipment is connected to the LMF
computer serial port
For E7495A/B, the LMF computer network card and the E7495 are
connected to the Ethernet hub ( Test Equipment Connection section)
and any firewall software on the LMF computer platform is
TURNED OFF
minutes.
S Test equipment has been selected/detected in the LMF (Refer to the
Selection Procedures subsection of the Test Equipment Selection
section)
Calibrating cables
Refer to Figure 3-29, Figure 3-30, Figure 3-31, or Figure 3-32 and
follow the procedure in Table 3-38 to calibrate the test cable
configurations.
Table 3-38: Cable Calibration
n Step
Action
From the Util menu, select Cable Calibration. A Cable Calibration window is displayed.
Enter the channel number(s) in the Channels box.
NOTE
Multiple channel numbers must be separated with a comma and no space (for example; 200,800).
When two or more channel numbers are entered, the cables are calibrated for each channel.
Interpolation is accomplished for other channels as required for TX calibration.
3-112
SEP 2009
Cable Calibration
continued
Table 3-38: Cable Calibration

n Step
Action
In the Cable Calibration pick list select one of the following:

TX and RX Cable Cal
TX Cable Cal
RX Cable Cal
Click OK and follow the direction displayed for each step. A status report window displays the
results of the cable calibration.
SEP 2009
3-113
Cable Calibration
continued
Figure 3-29: IS95A/B Cable Calibration Test Setup Agilent 8935
CALIBRATION SET UP
SUPPORTED TEST SETS

HEWLETTPACKARD MODEL HP 8935
A. SHORT CABLE CAL
ANT
IN
DUPLEX
OUT
SHORT
CABLE
TEST
SET
B. RX TEST SETUP
NN FEMALE
ADAPTER
RX
CABLE
SHORT
CABLE
TEST
SET
C. TX TEST SETUP
50 TERM.
100WATT (MIN)
NONRADIATING
RF LOAD
10 DB MINIMUM
INLINE ATTENUATOR
SHORT
CABLE
RX
CABLE
3-114
DIRECTIONAL COUPLER
(30 DB)
TX
CABLE
NN FEMALE
ADAPTER
TEST
SET
SEP 2009
Cable Calibration
continued
Agilent E4406A/E4432B and Advantest R3267/R3562
SUPPORTED TEST SETS
CALIBRATION SET UP
A. SHORT CABLE CAL
ADVANTEST R3267 (TOP) AND R3562 (BOTTOM)
SHORT
CABLE
TEST
SET
RF IN
B. RX TEST SETUP
EXT TRIG IN
MOD TIME BASE IN
(EXT REF IN)
NN FEMALE
ADAPTER
RF OUT
RX
CABLE
AGILENT E4432B (TOP) AND E4406A (BOTTOM)
SHORT
CABLE
TEST
SET
RF
OUTPUT
50 OHM
RF
INPUT 50
OHM
C. TX TEST SETUP
50 TERM.
AGILENT E4432B (TOP) AND 8935 SERIES

E6380A (BOTTOM)
ANT
IN
RF
OUTPUT
50
10 DB MINIMUM
INLINE ATTENUATOR
SHORT
CABLE
RX
CABLE
NOTE:
10 MHZ IN on rear of signal generator is connected to
10 MHZ REF OUT on side of CDMA Base Station Test Set
SEP 2009
100WATT (MIN)
NONRADIATING
RF LOAD
DIRECTIONAL COUPLER
(30 DB)
TX
CABLE
NN FEMALE
ADAPTER
TEST
SET
REF FW00089
3-115
Cable Calibration
continued
Figure 3-31: CDMA2000 1X Cable Calibration Test Setup Agilent E7495A or E7495B
CALIBRATION SET UP
SUPPORTED TEST SETS
A. SHORT CABLE CAL

AGILENT E7495A OR E7495B
10 DB PAD
SHORT
CABLE
TEST
SET
10 DB PAD
B. RX and TX TEST SETUP

50
TERM.
10 DB MIMIMUM
INLINE ATTENUATOR
100WATT (MIN)
NONRADIATING
RF LOAD
GPIO
Power REF
50 MHz
Ext Ref
In
DIRECTIONAL
COUPLER
(30 DB)
TX
CABLE
Use only
Agilent supplied
power adapter
10 DB PAD
Serial 1
Port 2
RF In
Sensor
Serial 2
Even Second
Sync In
Port 1
RF Out / SWR
SHORT
CABLE
GPS
Antenna
NN FEMALE
ADAPTER
RX
CABLE
10 DB PAD
PORT 2
RF IN
PORT 1
RF OUT
TEST
SET
NOTES:
1. FOR RX TESTING, TOTAL RF PATH
ATTENUATION
MUST BE WITHIN THE VALUES
SPECIFIED BELOW FOR EACH TYPE
OF TEST SET:
E7495A: 25 TO 32 dB
E7495B: 10 TO 100 dB
2. WHEN USING THE E7495A, TX
TESTS REQUIRE A MINIMUM OF 30 DB
LOSSES.
3-116
SEP 2009
Cable Calibration
continued
Figure 3-32: IS95A/B and CDMA 2000 1X Cable Calibration Test Setup Anritsu MT8212B
CALIBRATION SET UP
SUPPORTED TEST SETS
A. SHORT CABLE CAL
ANRITSU MT8212B
SHORT
CABLE
TEST
SET
3
RF IN
50
RF OUT
50
C. RX and TX TEST SETUP

50 TERM.
100WATT (MIN.)
NONRADIATING
RF LOAD
DIRECTIONAL COUPLER
(30 DB)
TX TESTS: 10 DB MINIMUM
INLINE ATTENUATOR
RX TEST: 35 DB MINIMUM
INLINE ATTENUATOR
TX AND RX
CABLE
SHORT
CABLE
NOTE: FOR RX TESTING (RSSI), TOTAL

RF PATH ATTENUATION
MUST BE 65 dB OR GREATER.
SEP 2009
TX AND RX
CABLE
NN FEMALE
ADAPTER
TEST
SET
3-117
Cable Calibration
continued
Calibrate Test Cabling Using

Signal Generator & Spectrum
Analyzer
Follow the procedure in Table 3-39 to calibrate the TX/Duplexed RX

cables using a signal generator and spectrum analyzer. Refer to
Figure 3-33, if required. Follow the procedure in Table 3-40 to calibrate
the NonDuplexed RX cables using the signal generator and spectrum
analyzer. Refer to Figure 3-34, if required.
TX and Duplexed RX Cable Calibration

Table 3-39: Calibrating TX and Duplexed RX Cables Using Signal Generator and Spectrum Analyzer
n Step
Action
Connect a short test cable between the spectrum analyzer and the signal generator.
Set signal generator to 0 dBm at the customer frequency.
Use a spectrum analyzer to measure signal generator output (see Figure 3-33, A) and record the
value.
Connect the spectrum analyzers short cable to point B, (as shown in the lower right portion of the
diagram) to measure cable output at customer frequency. Record the value at point B.
Calibration factor = A B. Example:
Cal = 1 dBm (53.5 dBm) = 52.5 dB
NOTE
The short cable is used for calibration only. It is not part of the final test setup. After calibration is
completed, do not re-arrange any cables. Use the equipment setup, as is, to ensure test procedures
use the correct calibration factor.
3-118
SEP 2009
Cable Calibration
continued
Figure 3-33: Calibrating Test Equipment Setup for TX BLO and TX ATP Tests
(using Signal Generator and Spectrum Analyzer)
SIGNAL
GENERATOR
SPECTRUM
ANALYZER
SHORT
TEST
CABLE
3
40W NONRADIATING
RF LOAD
THIS WILL BE THE CONNECTION TO

THE TX PORTS DURING TX BAY LEVEL
OFFSET TEST AND TX ATP TESTS.
A
50 OHM
TERMINATION
SPECTRUM
ANALYZER
ONE 20DB 20 W IN
LINE ATTENUATOR
SHORT TEST CABLE
THIS WILL BE THE CONNECTION TO THE HP8481A POWER

SENSOR DURING TX BAY LEVEL OFFSET TEST AND TO THE
PCS INTERFACE BOX INPUT PORT DURING TX ATP TESTS.
SIGNAL
GENERATOR
30 DB
DIRECTIONAL
COUPLER
CABLE FROM 20 DB @ 20W ATTENUATOR TO THE

PCS INTERFACE OR THE HP8481A POWER SENSOR.
FW00293
Non-Duplexed RX Cable Calibration

Table 3-40: Calibrating RX Cables Using a Signal Generator and Spectrum Analyzer
n Step
Action
Connect a short test cable to the spectrum analyzer and connect the other end to the Signal
Generator.
Set signal generator to 10 dBm at the customers RX frequency.
Use spectrum analyzer to measure signal generator output (see Figure 3-34, A) and record the
value for A.
Connect the test setup, as shown in the lower portion of the diagram to measure the output at the
customers RX frequency. Record the value at point B.
Calibration factor = A B. Example:
Cal = 12 dBm (14 dBm) = 2 dBm
NOTE
The short cable is used for calibration only. It is not part of the final test setup. After calibration is
completed, do not re-arrange any cables. Use the equipment setup, as is, to ensure test procedures
use the correct calibration factor.
SEP 2009
3-119
Cable Calibration
continued
Figure 3-34: Calibrating Test Equipment Setup for RX ATP Test

(using Signal Generator and Spectrum Analyzer)
SIGNAL
GENERATOR
SIGNAL
GENERATOR
SPECTRUM
ANALYZER
SHORT
TEST
CABLE
CONNECTION TO THE HP PCS

INTERFACE OUTPUT PORT
DURING RX MEASUREMENTS.
SPECTRUM
ANALYZER
SHORT TEST
CABLE
BULLET
CONNECTOR
LONG
CABLE 2
CONNECTION TO THE RX PORTS

DURING RX MEASUREMENTS.
3-120
FW00294
SEP 2009
Cable Calibration
continued
Setting Cable Loss Values
Cable loss values for the TX and RX test cable configurations are
normally set by accomplishing cable calibration using the applicable test
equipment. The resulting values are stored in the cable loss files. The
cable loss values can also be set/changed manually. Follow the procedure
in Table 3-41 to set cable loss values.
CAUTION
If cable calibration was performed without using the LMF,
cable loss values must be manually entered in the LMF
database. Failure to do this will result in inaccurate BTS
calibration and reduced site performance.
Prerequisites
S Logged into the BTS

Table 3-41: Setting Cable Loss Values
n Step
Action
Click on the Util menu.
Select Edit > Cable Loss.
In the data entry popup window, select TX Cable Loss or RX Cable Loss.
To add a new channel number, click on the Add Row button, then click in the Channel # and
Loss (dBm) columns and enter the desired values.
To edit existing values, click in the data box to be changed and change the value.
To delete a row, click on the row and then click on the Delete Row button.
To save displayed values, click on the Save button.
To exit the window, click on the Dismiss button.

Values entered/changed after the Save button was used are not saved.
NOTE
S If cable loss values exist for two different channels, the LMF will interpolate for all other
channels.
S Entered values are used by the LMF as soon as they are saved. Logging out and logging in
again is not necessary.
SEP 2009
3-121
Cable Calibration
continued
Setting Coupler Loss Values
If an inservice coupler is installed, the coupler loss (e.g., 30 dB) must

be manually entered so it will be included in the LMF TX calibration
and audit calculations and RX FER Test. Follow the procedure in
Table 3-42 to set coupler loss values.
Prerequisites
S Logged into the BTS.

3
Table 3-42: Setting Coupler Loss Value

n Step
Action
Select Edit > Coupler Loss.
In the data entry popup window, select one of the following:

TX Coupler Loss
RX Coupler Loss.
Click in the Loss (dBm) column for each carrier that has a coupler and enter the appropriate value.
To edit existing values click in the data box to be changed and change the value.
Click on the Save button to save displayed values.
Click on the Dismiss button to exit the window.

Values entered/changed after the Save button was used are not saved.
NOTE
S The InService Calibration check box in the
Tools > Options > BTS Options tab must checked before entered coupler loss values are used
by the TX calibration and audit functions or RX FER test.
S Entered values are used by the LMF as soon as they are saved. Logging out and logging in
again is not necessary.
3-122
SEP 2009
Bay Level Offset Calibration

Purpose of Bay Level Offset
Calibration
Bay Level Offset (BLO) calibration is the central activity of the

optimization process. BLO calibration compensates for normal
equipment variations within the BTS RF paths and assures the correct
transmit power is available at the BTS antenna connectors to meet site
performance requirements.
What is BLO Calibration?
Description
BLO calibration is the complete title of what is normally referred to as
calibration. Calibration identifies the accumulated gain in every
transmit path at the BTS site. The transmit path BLO values determined
during calibration are stored in the LMF calibration data file, and are
subsequently downloaded to each BBX. When transmit path calibration
is performed, receive path BLO values will automatically be set to the
default value in the LMF calibration file and downloaded.
BTS RF Path Descriptions
Transmit (TX) path A TX path starts at an CCCP shelf BBX
backplane slot, travels through the CIO card, is routed to the Linear
Power Amplifier (LPA) trunking module for sector phase shifting,
through the LPAs, back through the LPA trunking module for sector
phase selection, through the TX bandpass filters, TX combiners, through
the Transmit & Receive Dual Directional Coupler (TRDC) or Duplexer
Directional Coupler (DRDC), and ends at the TRDC TX or DRDC
antenna connector.
Receive (RX) main path A main RX path starts at the receive
ANTENNAS connectors and travels through the associated TRDC or
DRDC, the MPC in CCCP cage slot MPC1, the CIO card, and
terminates at a backplane BBX slot in the CCCP shelf.
Diversity RX path Diversity RX paths differ for starter (standalone)
and companion frames. The following describe each type of path:
S Starter frame diversity RX path A starter frame diversity RX path

is the same as a main RX path except that it starts at the ANTENNAS
connectors travels through the associated TRDC or DRDC, and the
MPC card in CCCP cage slot MPC2.
SEP 2009
3-123
continued
S Companion frame diversity RX path The companion frame main
RX signal is used for the collocated companion frame diversity RX

signal. A companion frames diversity RX path starts at the
ANTENNAS connectors in the collocated companion frame. It travels
through the associated TRDC or DRDC, the MPC in CCCP cage slot
MPC1, and the CIO card where it is then routed out of the frame
through the RX expansion out connectors (RX EXPANSION 1A, 2A,
or 3A in Figure J1). The signal travels through the interframe
diversity RX cables, into the RX expansion in ports (RX
EXPANSION 1B, 2B, or 3B in Figure J1) of the companion frame,
through the Expansion MPC (EMPC) in CCCP cage slot MPC2,
the CIO, and terminates at a backplane BBX slot in the CCCP shelf.
S RFDS or CRMS Probe sampling paths Directional couplers for
RFDS signal sampling are integral to the SC4812ET Lite transmit and
receive paths in the DRDCs and TRDCs. Cables connect from these
directional couplers to the RFDS or CRMS Probe input connectors.
When to Calibrate BLOs
Calibration of BLOs is required after initial BTS installation.

The BLO data of an operational BTS site must be re-calibrated once
each year. Motorola recommends re-calibrating the BLO data for all
associated RF paths after replacing any of the following components or
associated interconnecting RF cabling:
S
S
S
S
S
S
S
S
BBX board
CCCP shelf
CIO card
CIO to PA backplane RF cable
PA backplane
LPA or CLPA
TX filter / TX filter combiner
TX thru-port cable to the top of frame
TX Path Calibration
The TX Path Calibration assures correct site installation, cabling, and the
first order functionality of all installed equipment. The proper function
of each RF path is verified during calibration. The external test
equipment is used to validate/calibrate the TX paths of the BTS.
WARNING
Before installing any test equipment directly to any TX
OUT connector you must first verify that there are no
CDMA channels keyed. Have the OMCR place the sector
assigned to the PA under test OOS. Failure to do so can
result in serious personal injury and/or equipment damage.
3-124
SEP 2009
continued
CAUTION
Always wear a conductive, high impedance wrist strap
while handling any circuit card/module. If this is not done,
there is a high probability that the card/module could be
damaged by ESD.
NOTE
At new site installations, to facilitate the complete test of
each CCP shelf (if the shelf is not already fully populated
with BBX boards), move BBX boards from shelves
currently not under test and install them into the empty
BBX slots of the shelf currently being tested to insure that
all BBX TX paths are tested.
S This procedure can be bypassed on operational sites
that are due for periodic optimization.
S Prior to testing, view the CDF file to verify the correct
BBX slots are equipped. Edit the file as required to

include BBX slots not currently equipped (per Systems
Engineering documentation).
BLO Calibration Data File
During the calibration process, the LMF creates a calibration (BLO) data
file. After calibration has been completed, this offset data must be
downloaded to the BBXs using the Download BLO function. An
explanation of the file is shown below.
NOTE
Due to the size of the file, Motorola recommends that you
print out a hard copy of a bts.cal file and refer to it for the
following descriptions.
The CAL file is subdivided into sections organized on a per slot basis (a
slot Block).
Slot 1 contains the calibration data for the 12 BBX slots. Slot 20
contains the calibration data for the redundant BBX (see Table 3-44).
Each BBX slot header block contains:
S A creation Date and Time broken down into separate parameters of

createMonth, createDay, createYear, createHour, and createMin.
S The number of calibration entries fixed at 720 entries corresponding

to 360 calibration points of the CAL file including the slot header and
actual calibration data.
SEP 2009
3-125
continued
S The calibration data for a BBX is organized as a large flat array. The
array is organized by branch, BBX slot, and calibration point.

The first breakdown of the array indicates which branch the
contained calibration points are for. The array covers transmit, main
receive and diversity receive offsets as follows:
Table 3-43: BLO BTS.cal file Array Branch Assignments
Range
Assignment
C[1]C[240]
Transmit
C[241]C[480]
Receive
C[481]C[720]
Diversity Receive
The second breakdown of the array is per sector. Three sectors are
allowed.
3-126
SEP 2009
continued
Table 3-44: BTS.cal File Array (Per Sector)

BBX
Sectorization
TX
RX
RX Diversity
Slot[1] (Primary BBXs 1 through 12)

1 (Omni)
33Sector,
S t
1st Carrier
2
3
4
6 Sector,
1st Carrier
33Sector,
S t
3rd Carrier
5
6
7
33Sector,
S t
2nd Carrier
8
9
10
6 Sector,
2nd Carrier
11
12
3Sector,
4th
C i
Carrier
C[1]C[20]
C[241]C[260]
C[481]C[500]
C[21]C[40]
C[261]C[280]
C[501]C[520]
C[41]C[60]
C[281]C[300]
C[521]C[540]
C[61]C[80]
C[301]C[320]
C[541]C[560]
C[81]C[100]
C[321]C[340]
C[561]C[580]
C[101]C[120]
C[341]C[360]
C[581]C[600]
C[121]C[140]
C[361]C[380]
C[601]C[620]
C[141]C[160]
C[381]C[400]
C[621]C[640]
C[161]C[180]
C[401]C[420]
C[641]C[660]
C[181]C[200]
C[421]C[440]
C[661]C[680]
C[201]C[220]
C[441]C[460]
C[681]C[700]
C[221]C[240]
C[461]C[480]
C[701]C[720]
Slot[20] (Redundant BBX13)

1 (Omni)
33Sector,
S t
1st Carrier
2
3
4
6 Sector,
1st Carrier
33Sector,
S t
3rd Carrier
5
6
7
33Sector,
S t
2nd Carrier
8
9
10
11
12
6 Sector,
2nd Carrier
3Sector,
4th
C i
Carrier
C[1]C[20]
C[241]C[260]
C[481]C[500]
C[21]C[40]
C[261]C[280]
C[501]C[520]
C[41]C[60]
C[281]C[300]
C[521]C[540]
C[61]C[80]
C[301]C[320]
C[541]C[560]
C[81]C[100]
C[321]C[340]
C[561]C[580]
C[101]C[120]
C[341]C[360]
C[581]C[600]
C[121]C[140]
C[361]C[380]
C[601]C[620]
C[141]C[160]
C[381]C[400]
C[621]C[640]
C[161]C[180]
C[401]C[420]
C[641]C[660]
C[181]C[200]
C[421]C[440]
C[661]C[680]
C[201]C[220]
C[441]C[460]
C[681]C[700]
C[221]C[240]
C[461]C[480]
C[701]C[720]
S Refer to the hard copy of the file. As you can see, 10 calibration
points per sector are supported for each branch. Two entries are
required for each calibration point.
S The first value (all odd entries) refer to the CDMA channel
(frequency) the BLO is measured at. The second value (all even
entries) is the power set level. The valid range for PwrLvlAdj is from
2500 to 27500 (2500 corresponds to 125 dBm and 27500
corresponds to +125 dBm).
SEP 2009
3-127
continued
S The 20 calibration entries for each slot/branch combination must be
stored in order of increasing frequency. If less than 10 points

(frequencies) are calibrated, the largest frequency that is calibrated is
repeated to fill out the 10 points.
Example:
C[1]=384,
odd cal entry
= 1 calibration point
C[2]=19102, even cal entry
C[3]=777,
C[4]=19086,
.
.
C[19]=777,
C[20]=19086, (since only two cal points were calibrated this
would be repeated for the next 8 points)
S When the BBX is loaded with BLO data, the cal file data for the BBX
is downloaded to the device in the order it is stored in the CAL file.
TxCal data is sent first, C[1] C[60]. BBX slot 1s 10 calibration
points are sent (C[1] C[20]), followed by BBX slot 2s 10
calibration points (C[21] C[40]), etc. The RxCal data is sent next,
followed by the RxDCal data.
S Temperature compensation data is also stored in the cal file for each
slot.

RF Path Calibration
Follow the steps in Table 3-45 to set up test equipment.

Table 3-45: Set Up Test Equipment for RF Path Calibration
Step
Action
If it has not already been done, refer to the procedure in Table 3-5 to interface the LMF computer
terminal to the frame LAN A connector.
If required, calibrate the test equipment per the procedure in Table 3-33.
NOTE
Verify the GPIB controller is properly connected and turned on.
! CAUTION
To prevent damage to the test equipment, all transmit (TX) test connections must be via the 30 dB
directional coupler for 800 MHz or via a 30 dB coupler with a 20 dB inline attenuator for 1900 MHz.
For TX path calibration, connect the test equipment as shown in Figure 3-22, Figure 3-21 and
Figure 3-23, depending on the communications analyzer being used.
3-128
SEP 2009
continued
Transmit (TX) Path Calibration

Description
The assigned channel frequency and power level (as measured at the top
of the frame) for transmit calibration is derived from the site NEC file.
For each BBX, the channel frequency is specified in the ChannelList
NEC file parameter and the power is specified in the SIFPilotPwr
NEC file parameter for the sector associated with the BBX (located
under the ParentSECTOR field of the ParentCARRIER NEC file
parameter).
The calibration procedure attempts to adjust the power to within +0.5 dB
of the desired power. The calibration will pass if the error is less than
+1.5 dB.
Transmit (TX) Bay Level Offset (BLO) Specifications SC4812ET
TX BLO specifications for different BTS configurations are as follows:
S At sites WITHOUT the RFDS option, is approximately 42.0 dB 3.0
dB.
Example BLO Calculation: TX BLO = Frame Power Output minus BBX
output level. TX output power measured at BTS (36.0 dBm) minus the
BBX TX output level (approximately 6.0 dBm) would equate to 42 dB
BLO.
S The TX Bay Level Offset at sites WITH the RFDS option, is
approximately 41.4 dB 3.0 dB. TX BLO = Frame Power Output

minus BBX output level.
Example BLO Calculation: TX BLO = Frame Power Output minus BBX

output level. TX output power measured at RFDS TX coupler
(39.4 dBm) minus the BBX TX output level (approximately 2.0 dBm)
and RFDS directional coupler/cable (approximately 0.6 dBm) would
equate to 41.4 dB BLO.
TX Calibration and the LMF
The LMF Tests > TX > TX Calibration... and Tests > All Cal/Audit...
selections perform TX BLO calibration testing for installed BBX(s). The
All Cal/Audit... selection initiates a series of actions to perform TX
calibration, and if calibration is successful, download BLO and perform
TX audit. The TX Calibration... selection performs only TX
calibration. When TX Calibration... is used, BLO download and TX
audit must be performed as separate activities. The CDMA Test
Parameters window which opens when TX Calibration... or All
Cal/Audit... is selected contains several userselectable features which
are described in the following subsections.
Rate Set Drop-down Pick List
The Rate Set Dropdown Box is enabled if at least one MCC card is
selected for the test. The available options for TX tests are 1 = 9600, and
3 = 9600 1X. Option 3 is only available if 1X cards are selected for the
test. The available transfer rate options for RX tests are 1 = 9600 and
2 = 14400. Option 2 is only available if no 1X cards are selected.
SEP 2009
3-129
continued
Verify BLO Checkbox

In both the TX Calibration and All Cal/Audit dialog boxes, a Verify
BLO checkbox is provided and checked by default. After the actual TX
calibration is completed during either the TX Calibration or All
Cal/Audit process, the BLO derived from the calibration is compared to
a standard, acceptable BLO tolerance for the BTS. In some installations,
additional items may be installed in the transmit path. The additional
change in gain from these items could cause BLO verification failure
and, therefore, failure of the entire calibration. In these cases, either the
Verify BLO checkbox should be unchecked or the additional path losses
should be added into each applicable sector using the
Util>Edit>TX Coupler Loss function.
Single-Sided BLO Checkbox

Normally valid values are some value plusorminus some offset. If
singlesided BLO is selected, the result will only be considered a
success if its in the lower half of the range. If it was normally success
from 3747 (which is 42 5), singlesided BLO would make it a
success only if the result was from 3742.
Test Pattern Drop-down Pick List
The Tests > TX > TX Calibration... menu window has a Test Pattern
pulldown menu. This menu has the following choices:
S Pilot (default) performs calibration using only the pilot channel.
This pattern setting should be used for inservice calibrations, and

requires selection of only a BBX.
S Standard performs calibration or audit using pilot, paging, synch,
and six traffic channels with IS97specified gain. This pattern setting
should be used for all noninservice calibrations and audits. Using
this pattern setting requires the selection of both a BBX and at least
one MCC.
S CDFPilot This pattern setting is for advanced users. It performs
calibration or audit using the CDF value for pilot gain and IS97 gain
values for all the other channels included in the Standard pattern
setting (paging, synch, and six traffic). Using this pattern setting
requires the selection of both a BBX and at least one MCC.
S CDF This pattern setting is for advanced users who need to use
CDF gain settings for all channels included in the Standard pattern
setting (pilot, paging, synch, and six traffic). Using this pattern setting
requires the selection of both a BBX and at least one MCC.
3-130
SEP 2009
TX BLO Calibration
TX BLO Calibration
TX Calibration
WARNING
OUT connector, first verify there are no CDMA BBX
channels keyed. Failure to do so can result in serious
personal injury and/or equipment damage.
CAUTION
handling any circuit card or module. If this is not done,
there is a high probability that the card or module could be
damaged by ESD.
All Cal/Audit and TX

Calibration Procedure
The LMF All Cal/Audit and TX calibration procedures are essentially

identical, except for the step that selects the type of procedure desired
(Refer to Step 3 in Table 3-46).
Prerequisites
Before running this procedure, be sure that the following have been
done:
S The card in slot CSM 1, GLIs, MCCs, and BBXs have correct code
and data loads.
S Primary CSM and MGLI are INS_ACT (bright green).

S All BBXs are OOS_RAM (yellow).
S If running calibration or audit using a test pattern other than Pilot,
MCCs are INS_ACT (bright green).
S Test equipment and test cables are calibrated and connected for TX
calibration.
S LMF is logged into the BTS in the GUI environment.

NOTE
Verify all BBX boards removed and repositioned have been
returned to their assigned shelves/slots. Any BBX boards
moved since they were downloaded will have to be
downloaded again.
Follow the procedure in Table 3-46 to perform All Cal/Audit and TX
path calibration test.
SEP 2009
3-131
TX BLO Calibration
continued
Table 3-46: All Cal/Audit and TX Calibration Procedure

Step
Action
If it has not already been done, configure test equipment for TX calibration by following the
procedure in Table 3-45.
Click on the BBX(s) to be calibrated and the BBXR.

For All Cal Audit...
Click Tests in the BTS menu bar, and select All Cal/Audit... from the pulldown menus. A
CDMA Test Parameters window will appear.
For TX Calibration
Click Tests in the BTS menu bar, and select TX > TX Calibration from the pulldown menus.
A CDMA Test Parameters window will appear.
Select the appropriate carrier(s) and sector(s) (carrier-bts#-sector#-carrier#) from those displayed in the
Channels/Carrier pick list.
NOTE
To select multiple items, hold down the Shift or Ctrl key while clicking on pick list items to select
multiple carrier(s)sector(s).
5
Verify that the correct channel number for the selected carrier is shown in the Carrier # Channels
box. If it is not, obtain the latest bts#.necf files from the OMCR.
NOTE
If necessary, the correct channel number may be manually entered into the Carrier # Channels box.
6
If Verify BLO is to be used during the calibration, leave the checkbox checked (default).
If SingleSided BLO is to be used during the calibration, click on the checkbox.
NOTE
SingleSided BLO should only be used for primary BBXs. Do not check the box when calibrating the
redundant BBX.
8
In the Test Pattern box, select the test pattern to use for the calibration from the dropdown list.
Result: The LMF will automatically key the designated BBX and ask the operator to move the test
equipment cable to appropriate TX path.
NOTE
If the Test Pattern to be used is Standard, CDFPilot, or CDF, select at least one MCC (refer to Test
Pattern Dropdown Pick List under TX Calibration and the LMF in this section).
9
If at least one MCC was selected in Step 8, select the appropriate transfer rate (1 = 9600, 3 = 9600 1X)
from the dropdown list in the Rate Set box.
NOTE
The rate selection of 3 is only available if 1X cards are selected for the test.
10
Click OK to display the status report window followed by a Directions pop-up window.
3-132
SEP 2009
TX BLO Calibration
continued
Table 3-46: All Cal/Audit and TX Calibration Procedure

Step
Action
11
Follow cable connection directions as they are displayed.

Result: When the calibration process is completed, results will be displayed in the status report
window.
12
3
Exception Handling
In the event of a failure, the calibration procedure displays a FAIL
message in the status report window and provides information in the
Description field.
Recheck the test setup and connection and rerun the test. If the tests fail
again, note specifics about the failure, and refer to Chapter 7,
Troubleshooting.
SEP 2009
3-133
Download BLO
Download BLO
After a successful TX path calibration, download the BLO calibration
file data to the BBXs.
NOTE
If a successful All Cal/Audit was completed, this
procedure does not need to be performed, as BLO is
downloaded as part of the All Cal/Audit.
Prerequisites
S BBXs being downloaded are OOSRAM (yellow).

S TX calibration is successfully completed.
Test Procedure
Follow the procedure in Table 3-47 to download the BLO data to the
BBXs.
Table 3-47: Download BLO
n Step
Action
Select the BBX(s) to be downloaded.
Click Device in the BTS menu bar, and select

Download > BLO from the pulldown menus. A status report window displays the result of the
download.
NOTE
Selected device(s) do not change color when BLO is downloaded.
3
3-134
SEP 2009
TX Calibration Audit
TX Calibration Audit
Introduction
NOTE
RF path verification, BLO calibration, and BLO data
download to BBXs must have been successfully completed
prior to performing the calibration audit.
3
The BLO calibration audit procedure confirms the successful generation
and storage of the BLO calibration offsets. The calibration audit
procedure measures the path gain or loss of every BBX transmit path at
the site. In this test, actual system tolerances are used to determine the
success or failure of a test. The external test equipment set up used is
same as that for TX calibration.
TX Audit Test
The Tests menu item, TX Audit, performs the TX BLO Audit test for a
BBX(s). All measurements are made through the appropriate TX output
connector using the calibrated TX cable setup.
Prerequisites
WARNING
OUT connector, first verify there are no CDMA BBX
channels keyed. Failure to do so can result in serious
personal injury and/or equipment damage.
Before running this test, ensure that the following have been done:
NOTE
All PAs must be INS during any TX testing.
S
S
S
S
CSM1, GLIs, and BBXs have correct code load and data load.
Primary CSM and MGLI are INS.
All BBXs are OOS_RAM.
Test equipment and test cables are calibrated and connected for TX
BLO calibration.
S LMF is logged into the BTS.
Test Procedure
Connect the test equipment as shown in Figure 3-15 through Figure 3-19
as applicable. Follow the procedure in Table 3-46 using the If
performing TX Audit alternate Step 3 to perform the BTS TX Path
Audit test.
SEP 2009
3-135
Create CAL File

Create CAL File
After downloading BLO data to the BBXs, the BLO data must also be
saved to a CAL file in the BTS folder on the LMF computer platform.
The CAL file must be created or updated so it can be transferred to the
OMCR. If no CAL file is stored in the BTS folder (such as after the
firsttime calibration of a new BTS), the Create Cal File function gets
the BLO data from the BBXs, creates the CAL file, and stores the BLO
data in it. If the CAL file already exists in the BTS folder, this function
will update it with the new BLO data.
NOTE
Create Cal File function only applies to selected
(highlighted) BBXs.
CAUTION
Motorola does not encourage the user to edit the CAL file
as this action can cause interface problems between the
BTS and the LMF. To manually edit the CAL file, the
LMF must first be logged out of the BTS. If the CAL file
is manually edited and then the Create Cal File function is
run, the edited information is lost.
Prerequisites
Before performing this procedure, the following should be done:
S LMF is logged into the BTS.

S BBXs are OOS_RAM with BLO downloaded.
Creating a CAL File
Table 3-48: Create CAL File
n Step
1
Action
Select the applicable BBXs.
NOTE
The CAL file is only updated for the selected BBXs.
2
Click on the Device menu.
Click on the Create Cal File menu item.

A status report window displays the results of the action.
3-136
SEP 2009
RFDS Setup and Calibration

RFDS Description
The optional RFDS is used to perform RF tests of the site from the
CBSC or from the LMF. The RFDS contains the following FRUs:
S Antenna Select Unit (ASU)

S Fixed Wireless Terminal Interface Card (FWTIC)
S Subscriber Unit Assembly (SUA)
For complete information regarding the RFDS, refer to the current issues
of CDMA RFDS Hardware Installation; 68P64113A93, CDMA RFDS
Users Guide; 68P64114A51, and the LMF Help function online
documentation (part of the Local Maintenance Facility (LMF) software
application).
RFDS Parameters
The bts#.cdf file includes RFDS parameter settings that must match the
installed RFDS equipment. The paragraphs below describe the editable
parameters and their defaults. Table 3-49 explains how to edit the
parameter settings.
S RfdsEquip valid inputs are 0 through 2.

0 = (default) RFDS is not equipped
1 = Non-Cobra/Patzer box RFDS
2 = Cobra RFDS
S TsuEquip valid inputs are 0 or 1

0 = (default) TSU not equipped
1 = TSU is equipped in the system
S MC1....4 valid inputs are 0 or 1
0 = (default) Not equipped

1 = Multicouplers equipped in RFDS system
(SC9600 internal RFDS only)
S Asu1/2Equip valid inputs are 0 or 1

0 = (default) Not equipped
1 = Equipped
S TestOrigDN valid inputs are (default) or a numerical string up to

15 characters. (This is the phone number the RFDS dials when
originating a call. A dummy number needs to be set up by the switch,
and is to be used in this field.)
NOTE
Any text editor may be used to open the bts#.cdf file to
verify, view, or modify data. Because the bts#.cdf file is
generated on a Unix system, a more sophisticated editor,
such as MicroSoft WordPad, will display file content in a
more easilyread format than many simple text editors.
SEP 2009
3-137
continued
Checking and Setting RFDS

Parameters
Follow the procedure in Table 3-49 to review and/or edit RFDS

parameters.
Table 3-49: RFDS Parameter Settings
Step
Action
* IMPORTANT
Log out of the BTS prior to performing this procedure.
1
Using a text editor, verify the following fields are set correctly in the bts#.cdf file:
EXAMPLE:
Asu1Equip = 1
Asu2Equip = 0 (1 if system is non-duplexed)
Mc1Equip = 0
Mc2Equip = 0
Mc3Equip = 0
Mc4Equip = 0
RfdsEquip = 2
TestOrigDN = 123456789
TsuEquip = 1
NOTE
The above is an example of entries extracted from the bts#.cdf file that should have been generated
by the OMCR and copied to the LMF. These fields will have been set by the OMCR if the
RFDSPARM database is modified for the RFDS.
2
Save changes and/or quit the editor.
Log into the BTS using an LMF GUI session (refer to Table 3-6).
If no changes were made to the bts#.cdf file fields listed in Step 1, proceed to Step 7. If changes were
made, continue with Step 5.
NOTE
To make certain the complete data download is accepted, the MGLI should be OOS_RAM (yellow)
when RFDS parameter settings are downloaded.
When changes are made to RFDS parameters in the bts#.cdf file, data must be downloaded to the
MGLI by performing the following:
5a
To be sure it does not take control when the MGLI is disabled, manually disable the redundant
GLI card by unseating it from the backplane connectors and sliding it partially out of the shelf
slot.
5b
Click on the MGLI.
5c
Click on Device in the BTS menu bar, and select Disable from the pulldown menu. A status
report window is displayed showing status of the operation.
5d
When the operation is complete, click OK to close the status report window.
5e
Click on the MGLI (now OOS_RAM (yellow)).

3-138
SEP 2009
continued

Step
Action
5f
Click on Device in the BTS menu bar, and select Download > Data from the pulldown menus
(selected devices do not change color when data is downloaded). A status report window is
displayed showing status of the download.
5g
5h
Click on the MGLI.
5i
Click on Device in the BTS menu bar, and select Enable from the pulldown menu. A status
report window is displayed showing status of the operation.
5j
When the operation is complete, click OK to close the status report window.
! CAUTION
When the MGLI changes to INS_ACT, data will automatically be downloaded to the RFDS. During
this process, the RFDS LED will slowly begin flashing red and green for approximately 23 minutes.
DO NOT attempt to perform any functions with the RFDS until the LED remains steady green.
5k
Reseat the redundant GLI card into the backplane connectors and lock it in place with the ejector
tabs.
5l
Once the redundant GLI initializes, download data to it by selecting the card and, in the BTS
menu bar, clicking Device and selecting Download > Data from the pulldown menus.
Any MCCs which were INS_ACT when the MGLI was disabled must be disabled, reenabled, and
downloaded with code as follows:
6a
Select the devices to be reset by clicking on them or using Select from the BTS menu bar and
clicking on MCCs in the pulldown menu.
6b
In the BTS menu bar, click on Device and select Disable from the pulldown menu. A status
window report window is displayed showing status of the operation.
6c
6d
Download data to the MCCs by following the procedure in Table 3-14.
6e
When data download is complete, enable the MCCs by following the procedure in Table 3-17.
Click on the RFDS tab.

SEP 2009
3-139
continued

Step
8
Action
Status the RFDS TSU by performing the following:
8a
8b
Click on the SUA to select it.

Click on TSU in the BTS menu bar, and select Status TSU from the pulldown menu. A status
report is displayed showing the software version number for the TSIC and SUA.
8c
NOTE
If the LMF displays an error message, check the following:
S
S
S
S
S
Ensure AMR cable is correctly connected from the BTS to the RFDS.
Verify RFDS has power.
Verify RFDS status LED is green.
Verify entries in RFDS fields of the bts#.cdf file are correct (refer to Step 1).
Status the MGLI and ensure it is communicating (by Ethernet) with the LMF, and is in the proper
state (INS_ACT (bright green)).
RFDS TSU NAM Programming
The Number Assignment Module (NAM) information needs to be

programmed into the TSU before it can receive and process test calls, or
be used for any type of RFDS test. The RFDS TSU NAM must be
programmed with the appropriate system parameters and phone number
during hardware installation. The TSU phone and TSU MSI must be
recorded for each BTS used for OMCR RFDS software configuration.
NOTE
The user will only need to program the NAM for the initial
installation of the RFDS.
3-140
SEP 2009
continued
Explanation of Parameters
Used When Programming the
TSU NAM
Table 3-50 defines the parameters used when editing the tsu.nam file.
Table 3-50: Defintion of Parameters
Access Overload Code
Slot Index
System ID
Network ID
These parameters are obtained from the switch.
Primary Channel A
Primary Channel B
Secondary Channel A
Secondary Channel B
These parameters are the channels which are to be used in operation

of the system.
Lock Code
Security Code
Service Level
Station Class Mark
Do NOT change.
IMSI MCC
IMSI 11 12
These fields are obtained at the OMC using the following command:
OMC000>disp bts# imsi
If the fields are blank, replace the IMSI fields in the NAM file to 0,
otherwise use the values displayed by the OMC.
MIN Phone Number
These fields are the phone number assigned to the mobile. The ESN
and MIN must be entered into the switch as well.
NOTE
This field is different from the TODN field in the bts#.cdf file. The
MIN is the phone number of the RFDS subscriber, and the TODN is
the number the subscriber calls.
SEP 2009
3-141
continued
Valid NAM Ranges
Table 3-51 provides the valid NAM field ranges. If any of the fields are
missing or out-ofrange, the RFDS will error out.
Table 3-51: Valid NAM Field Ranges
Valid Range
Minimum
Maximum
Access Overload Code
15
Slot Index
System ID
32767
Network ID
32767
Primary Channel A
25
1175
Primary Channel B
25
1175
Secondary Channel A
25
1175
Secondary Channel B
25
1175
Lock Code
999
Security Code
999999
Service Level
N/A
N/A
Station Class Mark
255
IMSI 11 12
99
IMSI MCC
999
N/A
N/A
NAM Field Name
MIN Phone Number
3-142
SEP 2009
continued
Set Antenna Map Data
The antenna map data must be entered manually if an RFDS is installed.

Antenna map data does not need to be entered if an RFDS is not
installed. The antenna map data is only used for RFDS tests and is
required if an RFDS is installed.
Prerequisite
S LMF is logged into the BTS
Follow the procedure in Table 3-52 to set antenna map data for the
RFDS.
Table 3-52: Set Antenna Map Data
Step
Action
Click on Util in the BTS menu bar, and select Edit > Antenna Map... from the pulldown menus. A
tabbed data entry popup window will appear.
In the data entry popup window, click on the TX Antenna Map or RX Antenna Map tab to select
the antenna map to be edited.
Locate the carrier and sector number for which data is to be entered or edited, and click in the column
where entry or editing is needed.
Enter/edit Antenna # and Antenna Label column data as needed for each carrier.
NOTE
Refer to the CDMA Help > Utility Menu > EditAntenna Map... section of LMF Help function
online documentation for antenna map examples.
5
For each tab with changes, click on the Save button to save displayed values.
Click on the Dismiss button to close the window.
NOTE
S Values entered or changed after the Save button was used will be lost when the window is
dismissed.
SEP 2009
3-143
continued
Set RFDS Configuration Data
If an RFDS is installed, the RFDS configuration data must be manually

entered.
Prerequisite
S LMF is logged into the BTS

NOTE
The entered antenna# index numbers must correspond to

the antenna# index numbers used in the antenna maps.
Follow the procedure in Table 3-53 to set RFDS configuration data.
Table 3-53: Set RFDS Configuration Data
Step
Action
Click on Util in the BTS menu bar, and select Edit > RFDS Configuration... from the pulldown
menus. A tabbed data entry popup window will appear.
In the data entry popup window, click on the TX RFDS Configuration or RX RFDS Configuration
tab, as required.
To add a new antenna number, perform the following:
3a
Click on the Add Row button.
3b
Click in the Antenna #, Cal Antenna, Scap Antenna, or Populate [Y/N] columns, as required.
3c
Enter the desired data.
To edit existing values, click in the data box to be changed and change the value.
NOTE
Refer to the CDMA Help > Utility Menu > EditRFDS Configuration... section of LMF Help
function online documentation for RFDS configuration data examples.
5
To delete a row, click on the row and then click on the Delete Row button.
For each tab with changes, click on the Save button to save displayed values.
Click on the Dismiss button to close the window.
NOTE
S Values entered or changed after the Save button was used will be lost when the window is
dismissed.
3-144
SEP 2009
continued
RFDS Calibration
The RFDS Calibration option is used to calibrate the RFDS TX and RX

paths.
TX Path Calibration For a TX antenna path calibration the BTS
XCVR is keyed at a predetermined power level and the BTS power
output level is measured by the RFDS. The power level is then measured
at the TX antenna directional coupler by the power measuring test
equipment item being used (power meter or analyzer). The difference
(offset) between the power level at the RFDS and the power level at the
TX antenna directional coupler is used as the TX RFDS calibration
offset value.
RX Path Calibration For an RX antenna path calibration the RFDS is
keyed at a predetermined power level and the power input level is
measured by the BTS BBX. A CDMA signal at the same power level
measured by the BTS BBX is then injected at the RX antenna directional
coupler by the communications system analyzer. The difference (offset)
between the RFDSkeyed power level and power level measured at the
BTS BBX is the RFDS RX calibration offset value.
RFDS calibration and the CAL file The TX and RX RFDS
calibration offset values are written to the CAL file in the slot[385]
Block.
TSIC channel frequency For each RFDS TSIC, the channel
frequency is determined at the lower third and upper third of the
appropriate band using the frequencies listed in Table 3-54.
Table 3-54: RFDS TSIC Calibration Channel Frequencies
System
Channel Calibration Points
800 MHz (A and B)
341 and 682
1.9 GHz
408 and 791
WARNING
OUT connector, verify that there are no CDMA channels
keyed. Failure to do so can result in serious personal injury
and/or equipment damage.
SEP 2009
3-145
continued
Prerequisites
S Test equipment has been selected.

S Test equipment and test cables have been calibrated.
S TX calibration has been performed and BLO data has been
downloaded to the BBXs.
S Test equipment and test cables are connected for TX calibration.

S Antenna map data has been entered for the site.
S BBXs are INS_TEST.
RFDS Calibration Procedure

Follow the procedure in Table 3-55 to perform RFDS calibration.
Table 3-55: RFDS Calibration Procedure
Step
Action
In the LMF, select the CDMA BTSxxx tab.
If the BTS Control button is not selected (no black dot showing), click on the B button in the BTS
menu bar to select it.
Select the BBX(s) assigned to the carrier(s) and sector(s) which will be used in RFDS calibration
(refer to Table 1-5 for BBX carrier and sector assignments).
Click on RFDS in the BTS menu bar, and select RFDS Calibration... from the pulldown menu. An
RFDS Calibration setup window will be displayed.
In the Tests to Perform box, select TX Calibration or RX Calibration, as required
Enter the appropriate channel number(s) (refer to Table 3-54) in the Channel Field box. To enter more
than one channel number, use the following methods:
Separate nonsequential channel numbers with a comma and no spaces;
for example: 247,585,742.
Enter a range of sequential channels by typing the first and last channel numbers in the range
separated by a dash and no spaces;
for example: 385395.
If the frame is equipped with TX combiners, click in the Has Combiners checkbox.
Select the appropriate carrier(s) and sector(s) from the Carriers pick list (hold down the Shift or Ctrl
key while clicking on pick list items to select multiple carrier(s)sector(s)).
Select the appropriate RX branch (Both, Main, or Diversity) in the dropdown list if performing RX
calibration.
10
Click on the OK button. A status report window is displayed, followed by a Directions popup
window.
11
Follow the cable connection directions as they are displayed.
12
When the test is completed, test results are displayed in the status report window.
13

3-146
SEP 2009
continued
Table 3-55: RFDS Calibration Procedure

Step
Action
14
Click on the Frame tab.
15
Select the MGLI by clicking on it.
16
Download updated RFDS offset data to the MGLI (see Step 5 in Table 3-49).
3
Program TSU NAM
The NAM must be programmed before it can receive and process test
calls, or be used for any type of RFDS test.
Prerequisites
S MGLI is INS_ACT (bright green).

S SUA is powered up and has a code load.
Program NAM Procedure
Follow the procedure in Table 3-56 to program the TSU NAM.
Table 3-56: Program NAM Procedure
Step
Action
In the LMF, select the RFDS tab.
Select the SUA by clicking on it.
Click on TSU in the BTS menu bar, and select Program TSU NAM from the pulldown menu. A
NAM programming window will appear.
Enter the appropriate information in the boxes (see Table 3-50 and Table 3-51) .
Click on the OK button to display the status report.
SEP 2009
3-147
Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration

Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration
CRMS Probe
If the BTS is equipped with a CRMS Probe, refer to CRMS Probe Users
Guide; 68P02969A25 for CRMS Probe setup, calibration, acceptance
testing, and required calibration and test application software.
3-148
SEP 2009
Alarms Testing
Alarms Testing
Alarms Verification
The alarms testing should be performed at a convenient point in the

optimization/ATP process, since the LMF is necessary to ensure that the
RF cabinet is receiving the appropriate alarms from the power cabinet.
The SC4812ET is capable of concurrently monitoring 10 customer
defined input signals and four customer defined outputs, which interface
to the 50pin punchblock. All alarms are defaulted to Not Equipped
during ATP testing. Testing of these inputs is achieved by triggering the
alarms and monitoring the LMF for statetransition messages from the
active MGLI3.
All customer alarms are routed through the 50 pair punchblock located
in the I/O compartment at the back of the frame. Testing is best
accomplished by using a specialized connector that interfaces to the
50pair punchblock. This connector is wired so that customer return 1 (2
for the B side) is connected to every input, CDI 0 through CDI 17.
Alarm Reporting Display
The Alarm Monitor window can be displayed to list alarms that occur
after the window is displayed. To access the Alarm Monitor window,
select Util>Alarm Monitor.
The following buttons are included:
S The Options button allows for a severity level (Warning, Minor,
Major, Critical, and Unknown) selection. The default is all levels.

To change the level of alarms reported click on the Options button
and highlight the desired alarm level(s). To select multiple levels press
the Ctrl key (for individual selections) or Shift key (for a range of
selections) while clicking on the desired levels.
S The Pause button can be used to pause/stop the display of alarms.
When the Pause button is clicked the name of the button changes to
Continue. When the Continue button is click the display of alarms
will continue. Alarms that occur between the time the Pause button is
clicked and the Continue button is clicked will not be displayed.
S The Clear button can be used to clear the Alarm Monitor display.
New alarms that occur after the Clear button is clicked will be
displayed.
S The Dismiss button is used to dismiss/close the Alarm Monitor

display.
SEP 2009
3-149
Alarms Testing
continued
Alarm Testing Setup
Prepare for any alarm testing by following the procedures in Table 3-57.
Table 3-57: Alarm Testing Preparation
Step
Action
If it has not already been done, refer to the procedure in Table 3-5 to connect the LMF computer
terminal to the frame LAN A connector.
If it has not already been done, refer to Table 3-6 to start a GUI LMF session.
Click on Util in the BTS menu bar, and select Alarm Monitor... from the pulldown menu.
An Alarm Monitor window will open.
Heat Exchanger Alarm Test
Table 3-58 gives instructions on testing the Heat Exchanger alarm.

Table 3-58: Heat Exchanger Alarm
Step
Action
Turn circuit breaker B of the Heat Exchanger circuit breakers OFF. This will generate a Heat
Exchanger alarm, ensure that the LMF reports the correct alarm condition in the RF Cabinet.
Alarm condition will be reported as BTS Relay #25 Heat Exchanger Alarm makes contact.
Turn the circuit breaker B ON. Ensure that the alarm condition is now removed.
NOTE
The Heat Exchanger will go through the Start Up sequence.
Door Alarm
Table 3-59 gives instructions on testing the door alarms.

NOTE
When conducting this test connect the LMF via the LAN
port on the back of the frame thru the Rear I/O Door.
Table 3-59: Door Alarm
Step
Action
Close all doors on the power cabinet. Ensure that no alarms are reported on the LMF.
Individually open and then close each power supply cabinet door. Ensure that the LMF reports an
alarm when each door is opened.
Alarm condition will be reported as BTS Relay #27 Door Alarm makes contact.
3-150
SEP 2009
Alarms Testing
continued
AC Fail Alarm
Table 3-60 gives instructions on testing the AC Fail Alarm.

Table 3-60: AC Fail Alarm
Step
1
Action
NOTE
The batteries should have a stable charge before performing this test.
Turn the Main AC breaker on the power cabinet OFF. The LMF should report an alarm on an AC Fail
(Rectifier Fail, Minor Alarm & Major Alarm) condition.
Alarm condition will be reported as BTS Relay #23, BTS # 21, BTS # 24 and BTS Relay # 29 AC
Fail Alarm makes contact respectively.
Turn the Main AC breaker on the power cabinet ON. The AC Fail alarm should clear.
Minor Alarm
Table 3-61 gives instructions on testing minor alarm.

Table 3-61: Minor Alarm
Step
Action
Turn the Temperature Compensation Panel (TCP) power switch OFF. This will generate a minor
alarm. Verify that the minor alarm LED (amber) is illuminated on the Meter Alarm Panel and the
LMF reports this minor alarm.
Alarm condition will be reported as BTS Relay #24 Minor Alarm makes contact.
Turn the TCP power switch ON. The alarm condition should clear.
SEP 2009
3-151
Alarms Testing
continued
Rectifier Alarms
The following series of tests are for single rectifier modules in a multiple
rectifier system. The systems include a three rectifier and a six rectifier
system.
Single Rectifier Failure (Three Rectifier System)
Table 3-62 gives instructions on testing single rectifier failure or minor
alarm in a three rectifier system.
Table 3-62: Single Rectifier Fail or Minor Alarm

Step
Action
Remove a single rectifier module and place it into the unused rectifier shelf #2.
Turn the AC breaker OFF, for this 2nd shelf.
Verify that a rectifier fail alarm is generated. The single rectifier module will lite two RED fail LED
(DC and Power), and the Meter Alarm Panel and LMF will also indicate a minor alarm and rectifier
fail status. The RECTIFIER FAIL LED will lite.
Check that the LMF reports both of these alarm conditions.
NOTE
Alarm conditions reported as BTS #24 and BTS #21, contacts respectively.
5
Turn the AC breaker for the 2nd shelf ON and verify that Rectifier Fail and minor alarm conditions
clear on the Meter Alarm Panel and LMF.
Multiple Rectifier Failure

Table 3-63 gives instructions on testing multiple rectifier failure or major
alarm in a three rectifier system.
Table 3-63: Multiple Rectifier Failure or Major Alarm
Step
Action
With the rectifier module still in the unused shelf position from Table 3-62 test procedures, turn the
AC breaker for the 1st shelf OFF.
Verify that a rectifier alarm is generated. Each of the two rectifier modules will lite two RED fail LED
(DC and Power), and the Meter Alarm Panel and LMF will indicate a major alarm (Rectifier Fail and
Major Alarm). The RECTIFIER FAIL LED will lite.
Verify that the LMF reports both alarm conditions. (BTS #29, BTS #21, and BTS #24)
Turn the AC breaker for the 1st shelf ON. Verify that all alarms have cleared.
Return the rectifier module to its original location. This completes the alarm test on the power cabinet.
3-152
SEP 2009
Alarms Testing
continued
Single Rectifier Failure (Six Rectifier System)

Table 3-64 gives instructions on testing single rectifier failure or minor
alarm in a six rectifier system.
Table 3-64: Single Rectifier Fail or Minor Alarm
Step
Action
Remove two(2) rectifier modules from shelf #2.
Turn the AC breaker OFF, for shelf #2.
Verify that a rectifier fail alarm is generated. The single rectifier module will lite two RED fail LED
(DC and Power), and the Meter Alarm Panel and LMF will also indicate a minor alarm and rectifier
fail status. The RECTIFIER FAIL LED will lite.
Check that the LMF reports both of these alarm conditions.

conditions (BTS #24 and BTS #21)
Turn the AC breaker for this shelf ON and verify that Rectifier Fail and Minor Alarm conditions have
cleared.
Multiple Rectifier Failure (Six Rectifier System)

Table 3-65 gives instructions on testing multiple rectifier failure or
major alarm in a six rectifier system.
Table 3-65: Multiple Rectifier Failure or Major Alarm
Step
Action
Replace one rectifier module previously removed and turn the AC breaker for this shelf, OFF.
Verify that a rectifier alarm is generated. Each of the two rectifier modules will lite a RED fail LED,
and the Meter Alarm Panel will indicate a major alarm (Rectifier Fail, Major and Minor Alarm).The
RECTIFIER FAIL LED will lite.
Verify that the LMF reports both alarm conditions. (BTS #29)
Turn the AC breaker for this shelf ON. Verify that all alarms have cleared.
Return all rectifier module to their original location. This completes the rectifier alarm tests on the
power cabinet.
SEP 2009
3-153
Alarms Testing
continued
Battery Over Temperature

Alarm (Optional)
CAUTION
Use special care to avoid damaging insulation on cables, or
damaging battery cases when using a power heat gun.
Table 3-66 gives instructions on testing the battery over temperature
alarm system.
Table 3-66: Battery Over Temperature Alarm

Step
Action
Use a low powered heat gun and gently heat the battery over temperature sensor (see location in
Figure 3-35). Do Not hold the hot air gun closer than 7.6 cm (3 in.) to the sensor. This will avoid
burning the cable insulation.
When the sensor is heated to approximately 50 C, a battery Over Temperature alarm is generated.
NOTE
An audible click will sound as K1 contact engage and K2 contacts disengage.
3
Visually inspect the K1 and K2 relays to verify state changes. The LMF should be displaying correct
alarms. (BTS #22)
Verify that the CHARGE DISABLE LED (amber) on the Meter Alarm Panel and the BATTERY
MAIN LED (green) are both illuminated.
Switch the hot air gun to cool. Cool the sensor until the K1 and K2 contact return to normal position
(K1 open and K2 closed). Use the LMF verify that all alarms have cleared.
3-154
SEP 2009
Alarms Testing
continued
Figure 3-35: Battery Overtemperature Sensor
Buss Bar
FW00408
6 AWG Cables
Battery Overtemp Sensor
Negative Temperature Compensation Sensor
SEP 2009
3-155
Alarms Testing
continued
Rectifier Over Temperature

Alarm
NOTE
This is connector J8 on the rear of the Meter Alarm Panel
itself, this is not connector J8 on the connector bulkhead at
the rear of the cabinet.
Table 3-67 gives instructions on testing the battery over temperature

alarm system.
Table 3-67: Rectifier Over Temperature Alarm
Step
1
Action
Remove the J8 link on the rear of the Meter Alarm Panel (see Figure 3-36 for J8 location).
NOTE
This is the J8 on the rear of the Meter Alarm Panel itself, this is not connector J8 on the connector
bulkhead at the rear of the cabinet.
2
Verify that RECTIFIER OVERTEMP LED (red) is lite. Contacts on K1 and K2 change states (K1
now closed and K2 open).
Verify that the LMF has reported an alarm condition. (BTS #26)
Reinstall J8 connector and verify that all alarm conditions have cleared. K1 and K2 should now be in
their normal states (K1 open and K2 closed).
This completes the system tests of the SC 4812ET power cabinet.
3-156
SEP 2009
Alarms Testing
continued
Figure 3-36: Location of Connector J8 on the Meter Alarm Panel

FRONT VIEW
VOLT
AMP
AMPS
VOLT
+
PWR
TEST POINTS
TEST POINTS
OFF ON
REAR VIEW
J1
J2
YEL
VIOLENT
OR
J3
J8
J9
J6
J4
J5
TERMINAL BLOCK
REAR CONNECTOR PANEL
RED BLK OR BRWN
TERMINAL BLOCK
J4
J5
J6
NOT
USED
J1
J2
J3
FW00245
Before Leaving the site
Table 3-68 gives instructions on what to check before leaving the site.
Table 3-68: Check Before Leaving the Site
Step
Action
Verify that ALL battery circuit breakers (for occupied shelves) are CLOSED (pushed in).
Verify that the Heat Exchanger is running.
Verify that the Meter Alarm Panel and TCP modules are switched ON.
Verify that the Battery Test Switch on the Meter Alarm Panel is in the OFF position.
Verify that no alarm conditions are being reported (with all doors closed).
SEP 2009
3-157
Alarms Testing
continued
Notes
3-158
SEP 2009
Chapter 4: Automated Acceptance Test Procedure

Table of Contents
SEP 2009
Acceptance Test Procedures Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reduced ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1
4-1
4-2
Automated Acceptance Test Procedures TX & RX . . . . . . . . . . . . . . . . . . . . .

Automated ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automated ATP Test Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATP Test Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Antenna Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATP Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reload MCC Following TX Testing of Redundant BBX Card Using
Standard Test Pattern, Software Release 2.18.0.x . . . . . . . . . . . . . . . . .
4-3
4-3
4-3
4-3
4-4
4-5
4-6
Individual Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX and RX Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Individual Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-8
4-8
4-8
TX Spectral Purity Transmit Mask Acceptance Test . . . . . . . . . . . . . . . . . . . . .

TX Mask Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-10
4-10
TX Waveform Quality (rho) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . .

Rho Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-12
4-12
TX Pilot Time Offset Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pilot Offset Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-13
4-13
TX Code Domain Power/Noise Floor Acceptance Test . . . . . . . . . . . . . . . . . . .

Code Domain Power Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CD Power/Noise FloorTest Failures with Agilent E7495A/B
Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-14
4-14
RX Frame Error Rate (FER) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . .

FER Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-16
4-16
Receive Signal Strength Indication (RSSI) Acceptance Test . . . . . . . . . . . . . . .

Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSSI Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-17
4-17
4-18
Generate an ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-19
4-19
4-19
4-7
4-14
Table of Contents
continued
Notes
SEP 2009
Acceptance Test Procedures Introduction

Introduction
General
The Acceptance Test Procedures (ATP) allow Cellular Field Engineers
(CFEs) to run automated acceptance tests on all BTS subsystem devices
equipped in the CDF using the LMF and the test equipment it supports.
LMF User Interface
This chapter provides procedures for performing acceptance testing from
the LMF GUI environment, the recommended method. The GUI
provides the advantages of simplifying the LMF user interface, reducing
the potential for miskeying commmands and associated parameters, and
speeding up the execution of complex operations involving multiple
command strings. If it is believed the LMF command line interface
(CLI) will provide additional insight into ATP operation or unexpected
test results, refer to LMF CLI Reference.
Test Reports
The CFE can choose to save the results of ATP tests to a report file from
which ATP reports are generated for later printing. See the Generating an
ATP Report section in this chapter.
Because test equipment functions during acceptance testing are
controlled by the LMF through the GPIB, only the test equipment
models supported by the LMF can be used.
CAUTION
1. Before using the LMF, read the Developer Release
Notes for WinLMF section in the LMF Help function
online documentation (part of the Local Maintenance
Facility (LMF) software application) for any
applicable information. Pay particular attention to the
Caveats/Known Issues part of this section.
2. The ATP test is to be performed on out-of-service
sectors only.
3. DO NOT substitute test equipment with other models
not supported by the LMF.
Test Equipment Set Calibration

Refer to Chapter 3 for detailed interconnection information needed for
calibrating equipment, cables, and other test equipment set components.
SEP 2009
4-1
continued
Reduced ATP
NOTE
Equipment has been factorytested for FCC compliance. If
licensegoverning bodies require documentation
supporting BTS site compliance with regulations, a full
ATP may be necessary. Perform the Reduced ATP only if
reports for the specific BTS site are NOT required.
After downloading the proper operational software to the BTS, the CFE
must perform these procedures (minimal recommendation):
1. Verify the TX/RX paths by performing TX Calibration, TX Audit,
and the Code Domain Power and FER tests.
2. Be sure calibration data for all equipped carrier sectors is obtained
and loaded on the OMCR (packet) or CBSC (circuit) for normal
site operation.
Failures During Testing

Should failures occur while performing the specified tests, refer to the
Basic Troubleshooting section of this manual for help in determining the
failure point. Once the point of failure has been identified and corrected,
refer to the FRU Optimization and ATP Test Matrix (Table C-1) in
Appendix C to determine the applicable test that must be performed.
In the unlikely event that the BTS passes these tests but has a forward
link problem during normal operation, the CFE should then perform the
additional TX tests for troubleshooting: TX spectral mask, TX rho, and
TX code domain.
4-2
SEP 2009
Automated Acceptance Test Procedures TX & RX

Automated ATP
This section covers the general requirements and procedures for

conducting both automated ATP testing and performing individual ATP
tests.
Automated ATP Test Options
Acceptance tests can be run individually or as one of the following

automated groups:
S All TX: TX tests verify the performance of the BTS transmit line up.
These include the GLI, MCC, BBX, and MCIO cards, the PAs and
passive components including ETMs, (S)PLCs, TX filters, and RF
cables.
S All RX: RX tests verify the performance of the BTS receiver line up.
These include the MPC (for starter frames), EMPC (for expansion
frames), MCIO, BBX, MCC, and GLI cards and the passive
components including RX filters (starter frame only), and RF cables.
S All TX/RX: Executes all the TX and RX tests.

S Full Optimization: Executes the TX calibration, downloads the BLO,
and executes the TX audit before running all of the TX and RX tests.
NOTE
The Full Optimization test can be run if TX path
calibration is needed before the TX and RX acceptance
tests are run.
If manual testing has been performed with the HP analyzer,
remove the manual control/system memory card from the
card slot and set the I/O Config to the Talk & Lstn mode
before starting the automated testing.
The STOP button can be used to stop the testing process.
Required Test Equipment
The following test equipment is required:
S LMF
S Power meter (used with HP8921A/600 and Advantest R3465)
S Communications system analyzer
S Signal generator for FER testing (required for all communications
system analyzers except the Agilent E7495A/B for 1X FER)
SEP 2009
4-3
continued
WARNING
S Before installing any test equipment directly to any

BTS TX OUT connector, verify that there are no
CDMA channels keyed.
S At active sites, have the OMCR operator place the
carrier assigned to the PAs under test OOS. Failure to

do so can result in serious personal injury and/or
equipment damage.
NOTE
Test equipment must be recalibrated before using it to
perform acceptance tests.
4
ATP Test Prerequisites
NOTE
For the SC4812TMC BTS, all CLPA modules in a
3sector frame must be INS during any TX testing. In a
6sector frame, all CLPA modules sharing a trunked group
must be INS during any TX testing. There are two trunked
groups in a 6 sector frame. Group one includes MCM1,
CLPA modules in slots 1 and 2 and sectors 13 of the
frame, Group two includes MCM2, CLPA modules in slots
3 and 4 and sectors 46 of the frame.
Before attempting to run any ATP tests, ensure the following have been
completed:
S BTS has been optimized (BBXs calibrated and BLOs downloaded)

(Chapter 3)
S The carrier(s) and/or sector(s) to be tested have been taken out of

service at the OMCR
S
S
S
S
S
S
S
S
LMF is logged into the BTS.

CSMs, GLIs, BBXs, and MCCs have correct code and data loads
Primary CSM and GLI are INS_ACT (light green in LMF)
MCCs are INS_ACT (light green in LMF)
BBXs are OOS_RAM (yellow in LMF)
No BBXs are keyed (not transmitting)
Test cables are calibrated
Test equipment is connected for ATP tests (refer to ATP Test Setup
illustrations in the Test Equipment Set Up section of Chapter 3).
S Test equipment has been selected in the LMF, warmed up 60 minutes,

and calibrated.
4-4
SEP 2009
continued
S GPIB is on (not required for Agilent E7495A or Anritsu MT)

S All required Ethernet test equipment connections are made
S BTS transmit connectors are properly terminated for the test(s) to be
performed
WARNING
1. All transmit connectors must be properly terminated
for all ATP tests.
2. Before a FER test is run, be sure that one of the
following is done:
All transmitter connectors are properly terminated
OR
All LPAs are turned OFF (circuit breakers pulled)
Failure to observe these warnings may result in bodily

injury or equipment damage.
Antenna Connectors
All acceptance testing requires test equipment connections to the BTS

antenna TX or RX connectors. Refer to the ATP Test Setup illustrations
in the Test Equipment Set Up section of Chapter 3 for specific
connection requirements
SEP 2009
4-5
continued
ATP Test Procedure
Follow the procedure in Table 4-1 to perform any ATP test.

Table 4-1: ATP Test Procedure
n Step
Action
Be sure all prerequisites have been met.
Select the BTS device(s) to be tested.
* IMPORTANT
All PAs must be enabled during TX testing.
NOTE
If the LMF has been logged into the BTS with a different MultiChannel Preselector setting than
the one to be used for this test, the LMF must be logged out of the BTS and logged in again with
the new MultiChannel Preselector setting. Using the wrong MPC setting can cause a false test
failure.
3
From the Tests menu, select the test to be run.
Select the appropriate carrier (carrier-bts#-sector#-carrier#) displayed in the Channels/Carrier

pick list.
NOTE
To select multiple items, hold down the <Shift> or <Ctrl> key while making the selections.
5
Enter the appropriate channel number in the Carrier n Channels box.

The default channel number displayed is determined by the CdmaChans[n] number in the
cbscn.cdf file for the BTS.
If applicable, select Verify BLO (default) or Singlesided BLO.
NOTE
Singlesided BLO is only used when checking nonredundant transceivers.
7
If applicable, select a test pattern from the Test Pattern pick list.
NOTE
S Selecting Pilot (default) performs tests using only a pilot signal.
S Selecting Standard performs tests using pilot, synch, paging, and 6 traffic channels. This
requires an MCC to be selected.
S Selecting CDFPilot performs tests using only a pilot signal, however, the gain for the channel
elements is specified in the CDF file.
S Selecting CDF performs tests using pilot, synch, paging, and 6 traffic channels, however, the
gain for the channel elements is specified in the CDF file.

4-6
SEP 2009
continued
Table 4-1: ATP Test Procedure

n Step
Action
Click on the OK button.

The status report window and a Directions pop-up are displayed.
Follow the cable connection directions as they are displayed.

The test results are displayed in the status report window.
10
Click on Save Results or Dismiss.
NOTE
If Dismiss is used, the test results will not be saved in the test report file.
4
Reload MCC Following TX
Testing of Redundant BBX
Card Using Standard Test
Pattern, Software Release
2.18.0.x
For software release 2.18.0.x, any MCCs supporting BBXR card

transmit tests using the Standard test pattern must be reloaded with
data before performing CD power/noise floor testing on a primary BBX
card.
CAUTION
In software release 2.18.0.x, failure to reload data into
MCC cards which supported BBXR TX testing using the
Standard test pattern will result in CD power/noise floor
test failures for subsequently tested primary BBX cards.
Reload affected MCCs with data as specified in the following procedure.
Table 4-2: Reload Affected MCC(s) with Data After Redundant BBX TX Testing with Standard Test Pattern
Step
Action
Select the applicable MCCs.
From the BTS tab menu bar, select Device > Disable/Deactivate.
Download data to the applicable MCC(s) by following the code load procedure in Table 3-14.
After data download is complete, select Device > Enable/Activate from the BTS tab menu bar.
SEP 2009
4-7
Individual Tests
Individual Tests
TX and RX Testing
The following individual ATP tests can be used to evaluate specific

aspects of BTS operation against individual performance requirements.
All testing is performed using the LMF GUI environment.
TX Testing
TX tests verify transmit antenna paths and output power control. All
tests are performed using the external, calibrated test equipment. All
measurements are made at the appropriate BTS TX OUT connector(s).
TX tests verify TX operation of the entire CDMA forward link using
selected BBXs assigned to respective sector antennas. Each BBX is
keyed up to generate a CDMA carrier (using both bbxlevel and BLO) at
the CDF or NEC filespecified carrier output power level.
RX Testing
RX testing verifies receive antenna paths for BBXs selected for the test.
All tests are performed using the external, calibrated test equipment to
inject a CDMA RF carrier with all zero longcode at the specified RX
frequency at the appropriate BTS RX IN connector(s).
RX tests verify RX operation of the entire CDMA reverse link.
Individual Tests
Spectral Purity TX Mask (Primary & Redundant BBX)

This test verifies that the transmitted CDMA carrier waveform generated
on each sector meets the transmit spectral mask specification with
respect to the assigned CDF or NEC file values.
Waveform Quality (Rho)
This test verifies that the transmitted Pilot channel element digital
waveform quality (rho) exceeds the minimum specified value in IS97.
Rho represents the correlation between the actual and perfect CDMA
modulation spectrums. 1.0000 represents 100% (or perfect correlation).
Pilot Time Offset
The Pilot Time Offset is the difference between the CDMA analyzer
measurement interval (based on the BTS system time reference) and the
incoming block of transmitted data from the BTS (Pilot only, Pilot
Gain = 262, PN Offset = 0).
Code Domain Power/Noise Floor
This test verifies the code domain power levels, which have been set for
all ODD numbered Walsh channels, using the OCNS command. This is
done by verifying that the ratio of PILOT divided by OCNS is equal to
10.2 + 2 dB, and, that the noise floor of all EVEN numbered OFF
Walsh channels measures < 27 dB for IS95A/B and CDMA2000 1X
with respect to total CDMA channel power.
4-8
SEP 2009
Individual Tests
continued
Frame Error Rate (FER)

The Frame Error Rate (FER) test verifies RX operation of the entire
CDMA Reverse Link using all equipped MCCs assigned to all
respective sectors/antennas. This test verifies the BTS sensitivity on all
traffic channel elements currently configured on all equipped MCCs at
an RF input level of 119 dBm (or 116 dBm if using TMPC).
NOTE
There are no pass/fail criteria associated with FER readings
taken at levels below 119 dBm, other than to verify that
the FER measurement reflects changes in the RX input
signal level.
Receive Signal Strength Indication (RSSI)

This test verifies the gain for BTS reverse (RX) paths for each
carriersector selected is within requirements for correct BBX receiver
operation for the operating band of the BTS as follows:
S 800 MHz: +15 dB (65 dBm or greater)

S 1900 and 2100 MHz: +9 dB (71 dBm or greater)
SEP 2009
4-9
TX Spectral Purity Transmit Mask Acceptance Test

TX Mask Test
This test verifies the spectral purity of each BBX carrier keyed up at a
specific frequency specified in the current NEC files. All tests are
performed using the external calibrated test set, controlled by the same
command. All measurements are via the appropriate TX OUT
(BTS/RFDS) connector.
The Pilot Gain is set to 541 for each antenna, and all channel elements
from the MCCs are forward-link disabled. The BBX is keyed up, using
both bbxlvl and bay level offsets, to generate a CDMA carrier (with pilot
channel element only). BBX power output is set to obtain +40 dBm as
measured at the TX OUT connector (on either the BTS or RFDS
directional coupler).
NOTE
TX output power is set to +40 dBm by setting BTS power
level to +33.5 dBm to compensate for 6.5 dB increase from
pilot gain set to 541.
The calibrated communications test set measures and returns the
attenuation level of all spurious and IM products in a 30 kHz resolution
bandwidth. With respect to the mean power of the CDMA channel
measured in a 1.23 MHz bandwidth in dB, verify that results meet
system tolerances at the following test points:
S 1.7/1.9 GHz:
at least 45 dB @ + 900 kHz from center frequency
at least 45 dB @ 900 kHz from center frequency
S 800 MHz:
at least 45 dB @ + 750 kHz from center frequency

The BBX then de-keys, and, if selected, the MCC is re-configured to

assign the applicable redundant BBX to the current TX antenna path
under test. The test is then repeated.
See Table 4-1 to perform this test.
4-10
SEP 2009
continued
Figure 4-1: TX Mask Verification Spectrum Analyzer Display
Mean CDMA Bandwidth

Power Reference
.5 MHz Span/Div
Ampl 10 dB/Div
Center Frequency
Reference
4
Attenuation level of all
spurious and IM products
with respect to the mean
power of the CDMA channel
+ 1980 kHz
1980 kHz
900 kHz
750 kHz
SEP 2009
+ 900 kHz
+750 kHz
FW00282
4-11
TX Waveform Quality (rho) Acceptance Test

TX Waveform Quality (rho) Acceptance Test
Rho Test
This test verifies the transmitted Pilot channel element digital waveform
quality of each BBX carrier keyed up at a specific frequency specified in
the current NEC files. All tests are performed using the external
calibrated test set controlled by the same command. All measurements
are via the appropriate TX OUT (BTS/RFDS) connector.
The Pilot Gain is set to 262 for each antenna, and all channel elements
from the MCCs are forward link disabled. The BBX is keyed up, using
both bbxlvl and bay level offsets, to generate a CDMA carrier (with pilot
channel element only, Walsh code 0). BBX power output is set to
40 dBm as measured at the TX OUT connector (on either the BTS or
RFDS directional coupler).
The calibrated communications test set measures and returns the Pilot
channel element digital waveform quality (rho) in dB, verifying that the
result meets system tolerances:
S Waveform quality (rho) should be w0.912 (0.4dB).

The BBX then de-keys and, if selected, the MCC is re-configured to
4-12
SEP 2009
TX Pilot Time Offset Acceptance Test

TX Pilot Time Offset Acceptance Test
Pilot Offset Test
This test verifies the transmitted Pilot channel element Pilot Time Offset
of each BBX carrier keyed up at a specific frequency specified in the
current NEC files. All tests are performed using the external calibrated
test set controlled by the same command. All measurements are via the
appropriate TX OUT (BTS/RFDS) connector.
The Pilot Gain is set to 262 for each antenna, and all TCH elements from
the MCCs are forward link disabled. The BBX is keyed up, using both
bbxlvl and bay level offsets, to generate a CDMA carrier (with pilot
channel element only, Walsh code 0). BBX power output is set to
40 dBm as measured at the TX OUT connector (on either the BTS or
RFDS directional coupler).
The calibrated communications test set measures and returns the Pilot
Time Offset in s, verifying results meet system tolerances:
S Pilot Time Offset should be within v3 ms of the target PT

Offset (0 ms).
The BBX then de-keys, and if selected, the MCC is re-configured to

SEP 2009
4-13
TX Code Domain Power/Noise Floor Acceptance Test

Code Domain Power Test
This test verifies the Code Domain (CD) power/noise floor of each BBX
carrier transmitting at a specific frequency as listed in the current CDF
file assignment. All tests are performed using the external calibrated test
set controlled by the same command. All measurements are via the
appropriate TX OUT connector.
For each sector/antenna under test, the Pilot Gain is set to 262. All MCC
channel elements under test are configured to generate Orthogonal
Channel Noise Source (OCNS) on different odd Walsh codes and to be
assigned a fullrate gain of 81. The maximum number of MCC Channel
Elements (CE) to be tested at any one time is 32 (32 odd Walsh codes).
If more than 32 CEs exist, then multiple sets of measurements are made
to verify all CEs on all sectors.
BBX power output is set to 40 dBm as measured at the TX OUT

connector.
Verify the code domain power levels, which have been set for all ODD
numbered Walsh channels, using the OCNS command. This is done by
verifying that Pilot Power (dBm) minus OCNS Power (dBm) is equal to
10.2 + 2 dB and that the noise floor of all OFF Walsh channels
measures < 27 dB (with respect to total CDMA channel power).
NOTE
When performing this test using the LMF and the MCC is
an MCC8E or MCC24E, the redundant BBX may fail or
show marginal performance. This is due to a timing
mismatch that the LMF does not address. Performing this
test from the CBSC will not have this timing problem.
After all channels are tested, the BBX(s) under test are de-keyed, and the
redundant BBX (BBXR), if selected, is assigned to the current TX
antenna path under test. The test is then repeated. Upon completion of
the test, OCNS is disabled on the specified MCC CE.
NOTE
If using Advantest test equipment, Code Domain Test
MUST be configured in RC1 mode.
CD Power/Noise FloorTest
Failures with Agilent E7495A/B
Test Set
If this test fails when using an Agilent E7495A/B test set, refer to
Table 7-21 in the Troubleshooting: Transmit ATP section of Chapter 7.
4-14
SEP 2009
continued
Figure 4-2: Code Domain Power and Noise Floor Levels

PILOT CHANNEL
PILOT LEVEL
MAX OCNS
CHANNEL
8.2 dB
ACTIVE CHANNELS
12.2 dB
MAX OCNS SPEC.
MIN OCNS SPEC.
MIN OCNS
CHANNEL
MAX NOISE
FLOOR
MAXIMUM NOISE FLOOR:
< 27 dB SPEC.
INACTIVE CHANNELS
Walsh 0 1 2 3 4 5 6 7
...
64
SHOWING ALL OCNS PASSING
PILOT CHANNEL
PILOT LEVEL
FAILURE EXCEEDS
MAX OCNS SPEC.
8.2 dB
ACTIVE CHANNELS
12.2 dB
MAX OCNS SPEC.
MIN OCNS SPEC.
FAILURE DOES NOT

MEET MIN OCNS SPEC.
FAILURE EXCEEDS MAX
NOISE FLOOR SPEC.
MAXIMUM NOISE FLOOR:
< 27 dB
INACTIVE CHANNELS
Walsh 0 1 2 3 4 5 6 7
...
INDICATING FAILURES
SEP 2009
64
FW00283
4-15
RX Frame Error Rate (FER) Acceptance Test

RX Frame Error Rate (FER) Acceptance Test
FER Test
This test verifies the BTS FER on all traffic channel elements currently
configured on all equipped MCCs (full rate at 1% FER) at an RF input
level of 119 dBm [or 116 dBm if using Tower Top
Amplifier (TMPC)]. All tests are performed using the external calibrated
test set as the signal source controlled by the same command. All
measurements are through the LMF.
The Pilot Gain is set to 262 for each TX antenna, and all channel
elements from the MCCs are forward-link disabled. The BBX is keyed
up, using only bbxlvl level offsets, to generate a CDMA carrier (with
pilot channel element only). BBX power output is set to 20 dBm as
measured at the TX OUT connector. The BBX must be keyed to enable
the RX receive circuitry.
The LMF prompts the MCC/CE under test to measure all zero longcode
and provide the FER report on the selected active MCC on the reverse
link for both the main and diversity RX antenna paths, verifying that
results meet the following specification:
S FER returned less than 1% and total frames measured is 1500

All MCC/CEs selected are tested on the specified RX antenna path. The
BBX then de-keys and, if selected, the MCC is re-configured to assign
the applicable redundant BBX to the current RX antenna paths under
test. The test is then repeated.
4-16
SEP 2009
Receive Signal Strength Indication (RSSI) Acceptance Test

Background
Overview This test verifies Receive Signal Strength Indication (RSSI)

for the selected sectors to ensure integrity of the reverse (RX) path and
that path losses are within tolerances required for correct receiver
operation. Testing is performed using the calibrated external test
equipment as the signal source. The test equipment is controlled by the
LMF during the test. The receive signal generated by the test equipment
is injected into the sector RX path to be tested at the applicable BTS
main and/or diversity receive ports.
Equipment operation during testing The LMF sets the pilot channel
power level of the BBX for the selected sector to 150 dBm (measured
at the TX port of the frame) and keys the BBX on pilot channel only to
enable the RX circuitry. The LMF then commands the test equipment to
generate the receive signal on the selected carrier at 80 dBm as
measured at the BTS RX port.
Test measurements The power level of the received signal is
measured by the BBX. The LMF corrects the measured power of the
signal using the RX BLO from the BBX database and determines if the
corrected signal gain is equal to or greater than the following specified
criteria for the band in which the BTS operates:
S 800 MHz: +15 dB (65 dBm or greater)

S 1900 and 2100 MHz: +9 dB (71 dBm or greater)
Redundant BBX testing When the redundant BBX is selected for
RSSI testing, the test is run on those carriersectors specified in the
Channels/Carriers pick list and the receive path(s) selected in the RX
Branch dropdown list (refer to Table 4-3).
SEP 2009
4-17
continued
RSSI Acceptance Test
Follow the steps in Table 4-3 to verify RSSI of the RX antenna paths for
the required sectorcarriers.
Table 4-3: Test RSSI
Step
Action
Set up the test equipment for RX acceptance tests (refer to Figure 3-20 through Figure 3-27 in the Test
Equipment Setup section of Chapter 3).
n WARNING
Be sure all TX antenna ports on the BTS are properly terminated with antenna connections or RF
loads. Failure to properly terminate transmit paths can result in personnel injury and/or equipment
damage.
4
2
If the LMF has been logged into the BTS with a different MultiChannel Preselector setting than the
one to be used for this test, the LMF must be logged out of the BTS and logged in again with the new
MultiChannel Preselector setting. Using the wrong MPC setting can cause a false test failure.
Select the BBXs for the carriersectors to be tested.
In the LMF window menu bar, click on Tests > RX > RSSI.
Select the sectors and carriers to be tested in the Channels/Carriers pick list which is displayed.
NOTE
To select multiple carrier(s)sectors(s), hold down the Shift or Ctrl while clicking on the required
items.
6
Select the RX Branch to be tested from the choices in the dropdown list provided (Both, Main, or
Diversity).
Enter the appropriate power level into the Generator amplitude box (default: 80 dBm)
Click OK. A status bar will be displayed followed by a Directions popup window..
Follow cable connection directions as they are displayed, and click the Continue button to begin
testing. Progress will be indicated in the status bar.
10
When the test is completed, click the Save Results or Dismiss button, as required, in the Status
Report window.
NOTE
If the Dismiss button is clicked, test results will not be saved in the test report file.
4-18
SEP 2009
Generate an ATP Report

Background
Each time an ATP test is run, an ATP report is updated to include the
results of the most recent ATP tests if the Save Results button is used to
close the status report window. The ATP report is not updated if the
status reports window is closed using the Dismiss button.
NOTE
The ATP report for a BTS will contain test results saved
with the Save Results button. Results will be saved for the
last test performed on the same:
S BBX
S Sector
S Carrier
S Channel
When an ATP report for a BTS is generated, all saved test

results will be included in the report.
ATP Report
Each time an ATP test is run, a report may be created for the BTS being
tested. If a previous report exists for the BTS, it is updated with the new
test results as noted above. The report includes the following for each
test:
S Test name
S Channel number
S Carrier number
S Sector number
S Test result
S PASS or FAIL
S Description information (if applicable)
S Time stamp
S Details/Warning information (if applicable)
The report can be printed if the LMF computer is connected to a printer.
Follow the procedure in the Table 4-4 to view and/or print the ATP
report for a BTS.
Table 4-4: Generating an ATP Report
Step
Action
Click on the Login tab (if not in the forefront).
Select the desired BTS from the available Base Station pick
list.
SEP 2009
4-19
continued
Table 4-4: Generating an ATP Report

Step
Action
Click on the Report button.
Click on a column heading to sort the report.
Do one of the following:
S If a printable file copy is not desired, click on the Dismiss

button.
S If a printable file copy is required, select the desired file

type in the picklist and click on the Save button.
4-20
SEP 2009
Chapter 5: Configuring Packet BTS Transport

Table of Contents
SEP 2009
Introduction to Packet BTS Transport Configuration . . . . . . . . . . . . . . . . . . . . .

Content Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1
5-1
5-1
GLI3 Required Software Release, Operating Mode, and Loading Code . . . . . .

Software release affect on backhaul mode . . . . . . . . . . . . . . . . . . . . . . .
GLI3 operating mode affect on loading code . . . . . . . . . . . . . . . . . . . .
GLI3 initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading code into GLI3 cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-3
5-3
5-3
5-4
5-4
GLI3 Card Software Version and Backhaul Mode . . . . . . . . . . . . . . . . . . . . . . .

Determine if GLI3 Card Configuration Changes Are Required . . . . . .
5-5
5-8
Preloading GLI3 Cards in Packet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-10
Configure GLI3 Cards for IBR Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Items Required for BTS with Redundant GLI3 Cards . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBR Implementation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBR Conversion Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convert GLI3 Cards to IBR Operation . . . . . . . . . . . . . . . . . . . . . . . . .
Exception Procedure for Use When Configuration Fallback Can Not
Be Overcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-12
5-12
5-12
5-13
5-13
5-14
Configure GLI3 Cards for Operation with External BTS Routers . . . . . . . . . . .

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional items for new packet BTS EBR conversion preparation . . .
EBR conversion preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convert GLI3 Cards to EBR Operation . . . . . . . . . . . . . . . . . . . . . . . .
5-27
5-27
5-27
5-28
5-30
Configuring BTS File Transfer Protocol Introduction . . . . . . . . . . . . . . . . . .

LMF file transfer protocol setting utility . . . . . . . . . . . . . . . . . . . . . . . .
5-33
5-33
Configuring BTS File Transfer Protocol New BTS Installation . . . . . . . . . . .

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Determining the operating file transfer protocol . . . . . . . . . . . . . . . . . .
Changing the operating file transfer protocol . . . . . . . . . . . . . . . . . . . .
5-35
5-35
5-35
5-36
GLI3 Software Release and Backhaul Mode Worksheet . . . . . . . . . . . . . . . . . .
5-37
5-25
Table of Contents
continued
Notes
SEP 2009
Introduction to Packet BTS Transport Configuration

There are several backhaul configurations used for traffic and control
signalling transport between a packet BTS and the OMCR. For
SC4812series and SC48x BTS models all of these depend on correctly
setting the GLI3 card operating mode to interface with the required
backhaul configuration. The backhaul configurations are:
S Integrated BTS Router (IBR)
S External BTS Router (EBR)

Content Summary
This chapter contains information and procedures necessary to configure

GLI3 cards for the backhaul configuration required for a packet BTS.
When additional procedures required for this are contained in other
sections of this publication or in other publications, the procedures in
this chapter will specify them at the point in the configuration process
where they are necessary.
This chapter contains procedures to accomplish the following:
S Determine GLI3 card:
Installed software version
Operating mode
Backhaul mode
S Loading GLI3 cards with code for the required software release
S Convert GLI3 card to IBR operation

S Convert GLI3 card to EBR operation
S Enable File Transfer Protocol (FTP) or Secure File Transfer Protocol
(SFTP)
Applicability
When to Use GLI3 Conversion Procedures in this Chapter

Procedures in this chapter are only for use in configuring GLI3 cards to
interface with the transport technique for which the BTS hardware has
already been configured. These include GLI3 cards in a newly installed
BTS and replacement GLI3 cards in an existing nonredundant BTS.
When to Use BTS Conversion Procedures from Another
Publication
If the BTS hardware configuration is being converted from one transport
techinque to another (for example, from IBR to EBR), the procedures in
the applicable BTS model conversion or upgrade manual must be used
instead of the procedures in this chapter. Table 5-1, below, lists the
various Motorolasupported packet BTS transport conversions along
with the applicable conversion or upgrade manual title needed to
perform the conversion. For more information on the applicable
conversion or upgrade manuals and how to obtain them, refer to the
Required Documents and Related Publications section of Chapter 1.
SEP 2009
5-1
continued
Table 5-1: Packet BTS Transport Conversions

Conversion Type
Use Procedures in
IBR to EBR
(BTS model) BTS Packet Backhaul Upgrade
EBR to IBR
(BTS model) BTS Packet Backhaul Upgrade
5-2
SEP 2009
GLI3 Required Software Release, Operating Mode, and Loading Code

If a GLI3 card is not loaded with code which supports the required BTS
backhaul configuration, it is necessary to load code into the card for the
correct software release.
Software release affect on
backhaul mode
The software release of the code loaded in a GLI card determines which
packet backhaul modes the card will support. Table 5-2 lists GLI3
backhaul modes along with the earliest Motorola software release which
supports each.
Table 5-2: GLI3 Packet Backhaul Mode and Software Release Required
Packet
Backhaul
Mode
Description
Required Software
Release
DUPLEX
EBR (redundant BTS routers)
2.16.1.x and later
INTERNAL
IBR
2.16.4.1 and later
IWFOTI
OTI
2.20.0.x and later
SIMPLEX
EBR (nonredundant BTS

routers)
2.16.1.1 and later
The software release of the code loaded in a GLI3 card can be

determined by following the procedure in Table 5-5.
GLI3 operating mode affect on
loading code
GLI3 card operating mode determines the methods which can be used to
load code into the GLI cards. Table 5-3 lists the code loading methods
available in each operating mode.
Table 5-3: GLI3 Code Loading Methods Based on Operating Mode
Operating
Mode
SEP 2009
Available Code Loading Methods
Circuit
1. Download from OMCR

2. Crossload from INS_ACT GLI card in a BTS
3. Download using WinLMF application
Packet
1. Download from OMCR

2. Crossload from INS_ACT GLI card
3. Download using WinLMF application (beginning
with R22.0)
5-3

continued
GLI3 initialization
A GLI3 card will initialize in the last operating and backhaul modes in
which it was functioning. This can be either of the two operating modes
and any of their corresponding backhaul modes listed in Table 5-4.
Table 5-4: GLI3 Backhaul Modes
Operating
Mode
MMI
display bkhaul_mode
Mode Designation
Description
Circuit
UNKNOWN
Circuit backhaul
Packet
INTERNAL
Integrated BTS Router (IBR)
DUPLEX
External BTS Router (EBR)

Redundant
SIMPLEX
EBR Nonredundant
IWFOTI
Open Transport Interface (OTI)
The operating mode and backhaul mode of a GLI3 card can be

determined by following the procedure in Table 5-5.
5
Loading code into GLI3 cards
Unless the customer knows the operating history and the exact software
release installed in them, GLI3 cards will initialize to an unknown
operating mode with a software release which may not support the
required backhaul mode.
The code loading methods for packet mode cards listed in Table 5-3 have
been changed with softare release 2.22.0.x (R22.0). Beginning with
R22.0, the WinLMF has the capability to load code into a packet GLI3.
The Motorolarecommended method to load GLI3 cards onsite is to
use the WinLMF. To do this, the BTS must have active spans which
allow the GLI3 cards to communicate with the network for DHCP
purposes. The second choice is preloading GLI3 cards with the correct
software release code and then transporting them to the base station site.
Preloaded cards can be exchanged for the GLI3 cards installed in the
BTS. The cards removed can be preloaded for the next new base station
installation or for use as spares.
Loading GLI3 cards with the WinLMF
(Motorolarecommended)
To load code to packet GLI3 cards with the WinLMF, refer to the
Preloading GLI3 cards (Motorolarecommended)
To preload GLI3 cards with OTIcapable code, refer to the procedure in
Table 5-7.
5-4
SEP 2009
GLI3 Card Software Version and Backhaul Mode

This procedure is used to obtain the information needed to determine if
the GLI3 cards installed in the BTS need:
S Code loaded for a different software release

S Change of backhaul mode
Prerequisites
The following are required before performing this procedure:
S
S
S
S
S
A minimum of one GLI3 card is installed in the BTS card cage

The installed GLI3 card is in BTS card cage slot GLI 1
The BTS has power applied
The installed GLI3 card has booted to the GLI3 prompt
A working copy has been made of the Software Release and Backhaul
Mode worksheet at the end of this chapter
Procedure
Determine GLI3 card installed software version and backhaul mode by
performing the following procedure.
Table 5-5: Determine GLI3 Card Software Version and Backhaul Mode
Step
Action
If GLI3 cards are installed in more than one slot in the BTS card cage, unseat all GLI3 cards except the
card in slot GLI 1.
If it has not been done, start a GLI3 MMI communication session on the LMF computer with the
powered GLI3 card as described in the GLI3 Card MMI Communication Session section of Chapter 1.
If GLI3 cards were preloaded with code for the software release installed on the Radio Access
Network (RAN), do the following:
1. Enter the preloaded software release number in the Software Version column of line 1 of
Table 5-19, Software Release and Backhaul Mode Record.
2. Skip to step 9.
Determine the software version loaded in the GLI3 card installed in GLI slot 1 by entering the
following at the GLI3 prompt:
display version
SEP 2009
5-5
continued
Step
5
Action
If a response similar to the following is displayed, the GLI3 card is operating in circuit mode:
GLI3> display version
01.09.1980 20:01:59 MGLI0022
OOSSBY
BTSCDMA 16.41.200.14
RAM version: 16.41.200.14

ROM version: 16.41.200.14
Built: Tue Oct 21 09:52:28 2003 il272112
Bootrom version: 16.41.200.12
Bootrom Built: Thu Oct 2 03:11:34 2003 IL270775
Bootblock version: 16.1.59.00
Bootblock Built: Wed Apr 10 07:08:06 2002 RIPCORD004
This GLI board is in RAM
Booted from /nvram00/loads/gli3_ckt_rom_upgrade.elf
Next boot from /nvram00/loads/gli3_ckt_rom_upgrade.elf
GLI3>
5
6
Record the release number for the RAM version in the Software Version column of line 2 of
Table 5-19, and skip to step 9.
NOTE
In the above example, the software release is 2.16.4.1. Later software releases use notation which is
more easily understood.
5-6
SEP 2009
continued
Step
7
Action
A GLI3 operating in packet mode will generate a response similar to the following:
GLI3>
display version
08.08.2007 13:27:28 MGLI19021
CC PRESENT BTSCDMA 20.00.30.42
INTERNAL RAM VERSION: 20.0.30.42

RAM Built: Tue Aug 7 10:00:00 2007 W0010711
BOOTROM VERSION: 20.00.130.26
BOOTROM Built: Wed Dec 20 11:05:06 2006 IL273595
BOOTBLOCK VERSION: 16.41.60.31
BOOTBLOCK Built: Fri Aug 27 16:50:14 2004 IL271322
SYSTEM VERSION: 2.20.0.30.42

COMMITTED VERSION: 2.20.0.30.42
NEXT VERSION: 2.20.0.30.42
BACK UP VERSION 2.20.0.30.42
CURRENT RELEASE PATH: /nvram00/screl/2.20.0.30.42/
CURRENT LIF: /nvram00/screl/2.20.0.30.42/NE_LIF.xml
CURRENT IMAGE: /nvram00/screl/2.20.0.30.42/gli_ram.bin.0108
CODE SERVER: 128.0.0.1
SW UPGRADE STATE: READY
GLI3>
Record the COMMITTED VERSION number in the Software Version column of line 2 of Table 5-19.
Determine the backhaul mode of the GLI3 cards by entering the following at the GLI3 prompt:
display bkhaul_mode
SEP 2009
5-7
continued
Step
10
Action
GLI3> display bkhaul_mode
06.08.2007 08:53:33 MGLI15502
The current BTS Router Backhaul Mode is DUPLEX

After the next reset, the BTS Router Backhaul Mode will be DUPLEX
GLI3>
NOTE
The possible modes and their meanings are:
S
S
S
S
S
DUPLEX = EBR with redundant BTS routers

INTERNAL = IBR
IWFOTI = OTI
SIMPLEX = EBR with a nonredundant BTS router
UNKNOWN = circuit mode
11
Record the response in the Backhaul Mode column of line 2 of Table 5-19.
12
If the software version requires updating for OTI operation, proceed to the GLI3 Operating Mode and
Loading Code section, and select the method to update software based on the card operating mode
(Table 5-3) and backhaul mode (Table 5-4).
13
If there are no additional MMI communication session requirements, disconnect the MMI cable from
the GLI3 MMI receptacle.
Determine if GLI3 Card

Configuration Changes Are
Required
Perform the following with the information recorded in Table 5-19.

Table 5-6: Does GLI3 Card Need Configuration Change?
Step
Action
Compare the entries in line 2 of Table 5-19 with the line 1 entries in the same column.
If there are differences in the software release, refer to Table 5-2 to determine if the code loaded in the
card will support the required backhaul mode for the BTS.
5-8
SEP 2009
continued
Table 5-6: Does GLI3 Card Need Configuration Change?

Step
Action
If the code will not support the required backhaul mode for the BTS, load the required software release
into the card (review the GLI3 Required Software Release, Operating Mode, and Loading Code
section of this chapter to determine how to proceed with loading the required software into the card).
If there are differences in the backhaul mode, perform the applicable GLI3 conversion procedure on
the card when the installed code will support it. GLI3 conversion procedures are:
S Configure GLI3 cards for IBR packet operation, Table 5-9, Table 5-10, and Table 5-11
S Configure GLI3 cards for operation with EBR, Table 5-14 and Table 5-15
SEP 2009
5-9
Preloading GLI3 Cards in Packet Mode

This procedure is for preloading GLI3 cards with the required software
release code and data when they are operating in packet mode. It can also
be used to preload cards for which the operating mode is unknown.
Required items
S A test laboratory packet BTS (toy cell) or an operational packet

BTS in which the INS_ACT GLI3 card is loaded with the correct
software release code
S Approved antistatic wrist strap

S GLI3 cards to be preloaded and their transport packaging
S Tagging materials
Preload procedure
Perform the following to preload GLI3 cards for a new base station site
or for use as spares.
Table 5-7: Preload GLI3 Cards

Step
Action
Identify the INS_SBY GLI3 card (ACT LED not lighted, STA LED slow flashing green) in the BTS
card cage.
Remove the card from the BTS card cage following the procedure in the Field Replaceable Unit
(FRU) manual for the base station model (Refer to the Required Documents and Related Publications
section of Chapter 1).
! CAUTION
Wear an approved antistatic wrist strap when performing the following. Failure to do so could result
in ElectroStatic Discharge (ESD) damage to the circuit cards.
Remove the GLI3 card to be preloaded from its protective packaging.
Follow the procedure in the base station FRU manual to install the GLI3 card in the BTS card cage
slot where the INS_SBY GLI3 card was removed in step 2, above.
Allow the GLI3 card to boot and reach OOS_SBY status (ACT LED not lighted, STA LED steady
green).
Contact the OMCR operator to request the OOS_SBY GLI3 be enabled, and ask the operator to
provide notification when the action is complete.
NOTE
Enabling the card will cause code to download to the card if the current loads in the card do not match
those required for the BTS.
Wait at least 17 minutes for the card to complete this operation and/or the STA indicator to change to
slow flashing green before proceeding beyond the next step.
5-10
SEP 2009
continued
Table 5-7: Preload GLI3 Cards

Step
Action
When notified that the GLI3 is enabled, visually verify when the GLI3 card has changed to INS_SBY
(ACT LED not lighted, STA LED slow flashing green).
Remove the preloaded INS_SBY GLI3 card from the BTS card cage following the procedure in the
base station FRU manual.
Place the preloaded GLI3 card in the original protective packaging for transport to the new BTS site.
10
Tag the packaging for the preloaded card to identify the preloaded software release code and data.
11
If other GLI3 cards must be preloaded, repeat steps 3 through 10 for each additional card.
12
When all cards have been preloaded, reinstall the GLI3 card originally removed from the BTS card
cage in step 2, above.
SEP 2009
5-11
Configure GLI3 Cards for IBR Operation

This section covers the actions needed to configure GLI3 cards for IBR
packet operation. Procedures unique to this process are contained in this
section. When procedures required for this process are contained in other
parts of this publication or in other publications, specifically direction to
them will be provided at the appropriate places in this section.
Items Required for BTS with
Redundant GLI3 Cards
If it is not already installed in the BTS, the following item is required to

support OMCR communication with the INS_SBY GLI during normal
redundant BTS operation:
Table 5-8: Item Required for BTS Redundant GLI Cabling Integrated BTS Router Group
Item
Double Crossover
Accessory Cable
Assembly
Item
Number
SGKN4408
Qty
Description
Consists of GLItoGLI FE cable 3088643C28.

Category 5E Ethernet transceiver cable, double
crossover, 2624 AWG, unshielded twisted pair,
0.3 m (12 in.), two 8contact modular plugs
Prerequisites
The following must be accomplished before traveling to the BTS site for
IBR implementation:
S The BTS has been installed as described in the BTS hardware
installation manual for the BTS type (refer to the Required Documents
and Related Publications section of Chapter 1)
S GLI3 cards for the site have been verified as having IBRcapable
software installed
S GLI3 card(s) are installed in the BTS

S The BTS has power applied
S The file transfer protocol setting required for operating the BTS (either
FTP or Secure FTP (SFTP)) on the network has been verified with the
OMCR provisioning and network operators policy
S Number and types of spans required at the site have been determined
and installed
S If a fractional span is to be used, the starting and ending DS0 numbers

provisioned on the OMCR have been obtained
S Required publications to support IBR implementation activities are on

hand for transportation to the BTS site (refer to the Required
Documents and Related Publications section of Chapter 1)
5-12
SEP 2009
continued
IBR Implementation Overview
Addition of fractional span support for IBRequipped packet BTS in

R18.0 has made IBR implementation at the BTS a twopart process. The
parts are:
1. Preparation actions
2. Configure GLI3 cards for IBR operation in either:
Full span or
Fractional span configuration
IBR Conversion Preparation
Follow the procedure in Table 5-9 to prepare the site for configuring the
GLI3 card(s) for IBR operation.
Table 5-9: IBR Configuration Preparation
Step
Action
Contact the OMCR and notify the operator that GLI3 transport configuration operations are starting.
With the BTS fully powered up, the GLI3 card(s) should have been seated in the correct slots. If not,
seat the card(s) at this time and allow each to complete its initialization.
Make sure the GLItoGLI double crossover Fast Ethernet (FE) cable (Table 5-8) is installed
between in the GLI connectors of the GLI3 cards
If it was not previously done, follow the procedure in Table 5-5 to verify the software version in the
GLI3 card(s)
If the GLI3 software requires upgrading for IBR capability, review the GLI3 Required Software
Release, Operating Mode, and Loading Code section of this chapter to determine how to proceed with
loading IBRcapable software into the card.
NOTE
Only one card in a BTS with redundant GLI3s is required to have IBRcapable software. This card
must be the INS_ACT card (shows light green in the LMF) in the BTS. The INS_ACT GLI will be the
first card in the BTS which is downloaded with code and data from the LMF. The INS_ACT GLI3
will crossload the correct software to the INS_SBY GLI3.
6
Refer to the site documentation for IBR spans and inspect the BTS span cabling connections to be sure
they match the requirements.
Correct any cabling discrepancies between the BTS span cabling and site documentation, referring to
the BTS hardware installation or packet backhaul upgrade manual as needed (Required Documents and
Related Publications section of Chapter 1).
If it has not already been done, follow the procedure in Table 3-10 to establish an MMI
communication session with the INS_ACT GLI3 card.
SEP 2009
5-13
continued
Table 5-9: IBR Configuration Preparation

Step
Action
Configure the file transfer protocol settings for each GLI3 card to match what is required for network
operation by performing the Configuring BTS File Transfer Protocol New BTS Installation
procedure in thchapter.
10
To complete the IBR conversion, perform one of the following, depending on what span configuration
has been provisioned for the BTS at the OMCR:
S If the BTS is provisioned with one or two full spans (24 DS0 for T1, 31 DS0 for E1), perform the
S If the BTS is provisioned with a fractional span (less than 24 DS0 for T1, less than 31 DS0 for E1),
perform the procedure in Table 5-11.
Convert GLI3 Cards to IBR

Operation
The procedure used to convert GLI3 cards to IBR operation depends on

the required span configuration (span_config) for the BTS:
S For a BTS provisioned with full span(s), use the procedure in

Table 5-10
S For a BTS provisioned with a fractional span, use the procedure in

Table 5-11
5-14
SEP 2009
continued
Full Span(s) IBR Conversion

To convert GLI3 cards in a BTS provisioned with full span(s) to IBR,
follow the procedure in Table 5-10.
Table 5-10: IBR Conversion BTS Provisioned with Full Span(s)
Step
Action
communication session with the INS_SBY GLI3 card, depending on the frame redundancy:
Enter the following at the GLI3 prompt to convert the GLI3 cards to IBR operation with full span(s):
convert_ibr
The system will display responses similar to the following:

GLI3>
convert_ibr
PARTIAL SYNTAX: convert_ibr span_type span_eq

Next available options:
LIST spanType : span Type
E1_1 : E1_1 E1 HDB3, CRC4 Framing 31TS (default for E1)
E1_2 : E1_2 E1 HDB3, Double Framing 31TS
T1_2 : T1_2 T1 ESF Framing, B8ZS (default for T1)
T1_3 : T1_3 T1 SF Framing, AMI, SW JBZS
current : Use current spanType
>
To set or change the span type, enter the correct option from the list at the entry prompt (>), as shown
in the following example:
> T1_2
NOTE
If the span type should not change from what is currently set, enter current.
SEP 2009
5-15
continued

Step
4
Action
The terminal will display a response similar to the following:
> T1_2
PARTIAL SYNTAX: convert_ibr T1_2
LIST
spanEq : Span Equalization
T1_1 : T1 Short Haul mode, 0131 feet (default for T1)
T1_2 : T1 Short Haul mode, 132262 feet
T1_3 : T1 Short Haul mode, 263393
E1_120 : E1 Short Haul mode, 120 ohm (default for E1)
T1_0DB : T1 Long Haul mode, LBO = 0 dB
T1_7_5DB : T1 Long Haul mode, LBO = 7.5 dB
current : Use current spanEq
>
Select the required equalization for the span type selected from the list and enter it at the prompt as
shown in the following example:
> T1_1
NOTE
If the span equalization should not change from what is currently set, enter current.
6
After selecting the required equalization for the span, the terminal will display a response similar to
the following:
> T1_1
PARTIAL SYNTAX: convert_ibr T1_2 T1_1
LIST
span_config : Span A full configuration
full_span : Full span configuration will be used on reset
to IBR mode.
RANGE
startDS0 : SPAN A startDS0 value*Value set is ignored except
in Fractional Span pBTSIBR mode(R18.0+) 1 31
>
For a BTS provisioned with full spans, accept the default setting full_span by pressing the Enter
key.
5-16
SEP 2009
continued

Step
8
Action
After entering the span_config, a warning and a series of actions will be displayed similar to the
following example:
> full_span
01.06.1980 00:13:05 MGLI0041
WARNING!!! This MMI is changing the GLI configuration.

Removing file: /nvram00/config/bootcfg.txt
Successfully removed file: /nvram00/config/bootcfg.txt
Removing file: /nvram00/config/hlp_param.txt
Successfully removed file: /nvram00/config/hlp_param.txt
Removing file: /nvram00/config/ospf_cfg.txt
Successfully removed file: /nvram00/config/ospf_cfg.txt
Removing file: /nvram00/config/ran_fail_cfg.txt
Successfully removed file: /nvram00/config/ran_fail_cfg.txt
Setting backhaul mode to IBR
Successfully set backhaul mode to: IBR
Setting spanType to: T1_2
Successfully set spanType to: T1_2
Setting spanEq to: T1_1
Successfully set spanEq to: T1_1
Setting SPAN A to FULL span configuration.
Successfully set SPAN A to FULL span configuration.
To complete the conversion to IBR, this GLI must be reset!
NOTE
Parameters which were entered in error will be identified after the final parameter is entered. Errors
will be reported by responses similar to the following:
> full_span
01.06.1980 00:13:05 MGLI0041
ERROR: Unsupported Span Type: J1_1.

Unsupported span types for IBR: E1_3, E1_4, J1_1, J1_2 & T1_1
Supported IBR Span Types: E1_1, E1_2, T1_2 & T1_3
Conversion to IBR failed!
Perform the following:

1. Disconnect the MMI cable from the INS_SBY card
2. Connect it to the INS_ACT GLI3 card
3. Establish MMI communication by pressing the Enter key to display the GLI3 > prompt
SEP 2009
5-17
continued

Step
Action
10
Repeat steps 1 through 8 of this table for the INS_ACT GLI card, and then proceed to step 11, below.
11
Reconnect the MMI cable to the INS_SBY GLI3 and press the Enter key to display the GLI3 >
prompt.
12
NOTE
For redundant BTS frames, the INS_SBY GLI3 must be reset first. The INS_ACT GLI3 card must
then be reset (step 13) within approximately 45 seconds of the INS_SBY GLI3 (step 12) to make sure
neither card reboots with configuration files for operation with external BTS routers or circuit mode. If
one GLI3 completes initialization before the other is reset, steps 1 through 8 must be repeated for both
cards and both must be reset again.
Use the MMI reset command to reset the GLI3 card where the MMI cable is connected.
13
Perform the following within 45 seconds of resetting the INS_SBY GLI3:

1.
2.
3.
4.
Disconnect the MMI cable from the INS_SBY GLI3

Connect the MMI cable to the INS_ACT GLI3
Press the Enter key to display the GLI3 > prompt
Reset the card using the MMI reset command
NOTE
In a redundant frame, if the INS_ACT GLI3 cannot be reset before the INS_SBY GLI3 completes its
reboot, perform steps 1 through 8 again for each card, reset the INS_SBY GLI3, and then reset the
INS_ACT GLI3 using the hardware RESET button on the front of each card.
14
NOTE
Upon rebooting after the convert_ibr operation, the GLI3 cards will begin sending Dynamic Host
Control Protocol (DHCP) requests over their backplane span connections. If they do not receive a
response within 50 minutes (redundant cards) or 25 minutes (nonredundant cards), they will
automatically reset to their previous backhaul mode (configuration fallback). The BTS must be placed
under OMCR control and initialized in packet mode within these times or the convert_ibr operation
must be performed again.
If continual problems are experienced with GLI3 configuration fallback before the OMCR can take
control of the BTS, do the following for each installed GLI3 card:
1. Perform the convert_ibr operation from steps 1 through 8 for the INS_SBY card.
2. Perform the exception procedure in Table 5-12 for the INS_SBY card.
3. Start an MMI session with the INS_ACT card and perform steps 1 through 8.
4. Perform the exception procedure in Table 5-12 for the INS_ACT card.
5. Resume this procedure at step 12, and follow the procedure to completion.
5-18
SEP 2009
continued

Step
Action
15
Wait at least 17 minutes for the cards to complete the rebooting operation and/or the STA indicator to
change to slow flashing green before attempting to proceed with the next step.
NOTE
Upon its first initialization with R18.0 or later RAM code, a packet GLI3 card will reallocate flash
memory space for a duplicate copy of the bootROM code. It will then write a redundant copy of the
code image to the new memory area. Visual indication of this process is provided by the STA LED
flashing orange at 0.5 second intervals. This onetime process can cause the card to require up to 17
minutes to complete initialization to an INS state. Once the redundant image is created on the card, the
extended 17minute upgrade process will not be repeated, even if the card is later downgraded to
preR18.0 software.
16
When all preparations for BTS operation are completed, contact the OMCR, notify the operator that
the BTS is ready for operation, and request notification when the operator no longer requires support
onsite.
17
When advised that there is no further requirement for onsite support of BTS and IBR initialization,
proceed to Chapter 6 and follow the procedures to prepare to leave the site.
SEP 2009
5-19
continued
Fractional Span IBR Conversion

To convert GLI3 cards in a BTS provisioned with a fractional span to
IBR, follow the procedure in Table 5-11.
Table 5-11: IBR Conversion BTS Provisioned with Fractional Span
Step
Action
communication session with the INS_SBY GLI3 card.
Enter the following at the GLI3 prompt to convert the GLI3 card(s) to IBR operation with a fractional
span:
convert_ibr

GLI3>
convert_ibr
PARTIAL SYNTAX: convert_ibr span_type span_eq

LIST spanType : span Type
E1_1 : E1_1 E1 HDB3, CRC4 Framing 31TS (default for E1)
E1_2 : E1_2 E1 HDB3, Double Framing 31TS
T1_2 : T1_2 T1 ESF Framing, B8ZS (default for T1)
T1_3 : T1_3 T1 SF Framing, AMI, SW JBZS
current : Use current spanType
>
> T1_2
NOTE
If the span type should not change from what is currently set, enter current.
5-20
SEP 2009
continued

Step
4
Action
> T1_2
PARTIAL SYNTAX: convert_ibr T1_2
LIST
spanEq : Span Equalization
T1_1 : T1 Short Haul mode, 0131 feet (default for T1)
T1_2 : T1 Short Haul mode, 132262 feet
E1_120 : E1 Short Haul mode, 120 ohm (default for E1)
T1_7_5DB : T1 Long Haul mode, LBO = 7.5 dB
current : Use current spanEq
>
Select the required equalization for the span type selected from the list and enter it at the prompt as
shown in the following example:
> T1_1
NOTE
If the span equalization should not change from what is currently set, enter current.
6
After selecting the required equalization for the span, the terminal will display a response similar to
the following:
> T1_1
PARTIAL SYNTAX: convert_ibr T1_2 T1_1
LIST
span_config : Span A full configuration
full_span : Full span configuration will be used on reset
to IBR mode.
RANGE
startDS0 : SPAN A startDS0 value*Value set is ignored except
in Fractional Span pBTSIBR mode(R18.0+) 1 31
>
SEP 2009
5-21
continued

Step
7
Action
For a BTS provisioned with a fractional span, enter the starting DS0 number for the span from the
specified range of values as shown in the following example:
> 1

> 1
COMMAND SYNTAX: convert_ibr T1_2 T1_1 startDS0 endDS0
RANGE
endDS0 : SPAN A endDS0 value*Value set is ignored except in
Fractional Span pBTSIBR mode(R18.0+) 1 31
>
Enter the ending DS0 number for the span from the specified range of values as shown in the
following example:
> 12
5-22
SEP 2009
continued

Step
9
Action
After entering the endDS0 value, a warning and a series of actions will be displayed similar to the
following example:
> 12
01.06.1980 00:13:05 MGLI0041

Removing file: /nvram00/config/ran_fail_cfg.txt
Successfully removed file: /nvram00/config/ran_fail_cfg.txt
Setting backhaul mode to IBR
Successfully set backhaul mode to: IBR
Setting spanType to: T1_2
Successfully set spanType to: T1_2
Setting spanEq to: T1_1
Successfully set spanEq to: T1_1
Setting SPAN A startDS0 to: 1
Successfully set SPAN A startDS0 to: 1
Setting SPAN A endDS0 to: 12
Successfully set SPAN A endDS0 to: 12
To complete the conversion to IBR, this GLI must be reset!
NOTE
Parameters which were entered in error will be identified after the final parameter is entered. Errors
will be reported by responses similar to the following:
> full_span
01.06.1980 00:13:05 MGLI0041
ERROR: Unsupported Span Type: J1_1.

Unsupported span types for IBR: E1_3, E1_4, J1_1, J1_2 & T1_1
Supported IBR Span Types: E1_1, E1_2, T1_2 & T1_3
Conversion to IBR failed!
SEP 2009
5-23
continued

Step
Action
10

1. Disconnect the MMI cable from the INS_SBY card
11
Repeat steps 1 through 9 for the INS_ACT GLI card, and then proceed to step 12, below.
12
For redundant frames, reconnect the MMI cable to the INS_SBY GLI3 and press the Enter key to
display the GLI3 > prompt.
13
NOTE
In a redundant BTS frame, the INS_SBY GLI3 must be reset first. The INS_ACT GLI3 card must then
be reset (step 14) within approximately 45 seconds of the INS_SBY GLI3 (step 13) to make sure
neither card reboots with configuration files for operation with external BTS routers or circuit mode. If
one GLI3 completes initialization before the other is reset, steps 1 through 9 must be repeated for both
cards and both must be reset again.
5
14
Perform the following within 45 seconds of resetting the INS_SBY GLI3:

1.
2.
3.
4.
Disconnect the MMI cable from the INS_SBY GLI3

Connect the MMI cable to the INS_ACT GLI3
NOTE
If the INS_ACT GLI3 cannot be reset before the INS_SBY GLI3 completes its reboot, perform steps 1
through 9 again for each card, reset the INS_SBY GLI3, and then reset the INS_ACT GLI3 using the
hardware RESET button on the front of each card.
5-24
SEP 2009
continued

Step
15
Action
NOTE
Upon rebooting after the convert_ibr operation, the GLI3 cards will begin sending DHCP requests
over their backplane span connections. If they do not receive a response within 50 minutes (redundant
cards) or 25 minutes (nonredundant cards), they will automatically reset to their previous backhaul
mode (configuration fallback). The BTS must be placed under OMCR control and initialized in
packet mode within these times or the convert_ibr operation must be performed again.
If continual problems are experienced with GLI3 configuration fallback before the OMCR can take
control of the BTS, do the following for each installed GLI3 card:
1. Perform the convert_ibr operation from steps 1 through 9 for the INS_SBY card.
2. Perform the exception procedure in Table 5-12 for the INS_SBY card.
3. Start an MMI session with the INS_ACT card and perform steps 1 through 9.
4. Perform the exception procedure in Table 5-12 for the INS_ACT card.
5. Resume this procedure at step 13 of this table, and follow the procedure to completion.
16
Wait at least 17 minutes for the cards to complete the rebooting operation and/or the STA indicator to
change to slow flashing green before attempting to proceed with the next step.
NOTE
preR18.0 software.
17
When all preparations for BTS operation are completed, contact the OMCR and notify the operator
that the BTS is ready for operation and request notification when the operator no longer requires
support onsite.
18
When advised that there is no further requirement for onsite support of BTS and IBR initialization,
proceed to Chapter 6 and follow the procedures to prepare to leave the site.
Exception Procedure for Use

When Configuration Fallback
Can Not Be Overcome
Perform the following procedure only when directed to it by the NOTE

after step 14 in Table 5-10 or step 14 in Table 5-11. This procedure is
intended for use when the OMCR is continually unable to take control
of the BTS before the GLI3 cards reboot to their lastknowngood
configuration.
SEP 2009
5-25
continued
IMPORTANT
This procedure should never be used unless absolutely

required because it will prevent backing the BTS out of the
IBR conversion if that is needed.
Table 5-12: Prevent GLI3 Configuration Fallback

Step
Action
If it has not been done, establish an MMI communication session with a GLI3 card by following the
Prevent the card from automatically rebooting to the last knowngood configuration (fallback) by
entering the following commands at the GLI3> prompt in the sequence shown and pressing the
ENTER key after each:
rmfile
rmfile
rmfile
rmfile
rmfile
rmfile
/nvram00/history/boothistory0.txt

GLI3> rmfile /nvram00/history/boothistory0.txt
09.16.2004 20:07:33 MGLI0031 CC NOT PRESENT BTSCDMA 17.00.201.22
GLI3>
Return to the table which directed using this procedure, and refer to the applicable table step of the
following to resume the conversion:
S For Table 5-10, see step 14 15 NOTE

S For Table 5-11, see step 15 NOTE
5-26
SEP 2009
Configure GLI3 Cards for Operation with External BTS Routers

This section covers the actions needed to configure GLI3 cards for
operation with External BTS Routers (EBR). Procedures in this section
apply to:
S New packet BTS initialization

S Replacement of a nonredundant GLI3 card
Procedures unique to this process are contained in this section. When
procedures required for this process are contained in other parts of this
publication or in other publications, the user will be specifically directed
to them at the appropriate places in this section.
Prerequisites
The following must be done before performing this procedure:
S The BTS has been installed as described in the BTS hardware
installation manual for the BTS type (refer to the Required Documents
and Related Publications section of Chapter 1)
S GLI3 card(s) for the site have been verified as having

IBR/EBRcapable software installed
S GLI3 card(s) for the site are installed in the BTS

S The BTS has power applied
S The file transfer protocol setting required for operating the BTS (either
FTP or Secure FTP (SFTP)) on the network has been verified with the
OMCR provisioning and network operators policy
S EBR span configuration required at the site has been determined from
site documentation
S Required publications to support conversion activities are on hand
(refer to the Required Documents and Related Publications section of

Chapter 1)
Additional items for new

packet BTS EBR conversion
preparation
The following items are required to prepare a new BTS EBR group for
the conversion:
Table 5-13: Items Required for FE Cabling External BTS Router Group
Item
External BTS router
FE connector
interconnect cables
SEP 2009
Part Number
Motorola
3088643C14 or
equivalent
Qty
2
Description
Category 5E Ethernet transceiver cable,
crossover, 24 AWG, shielded twisted pair, 0.6 m
(23.6 in), two 8contact modular plugs
5-27
continued
EBR conversion preparation
Do the following to prepare a new BTS for converting the GLI3 card(s)
to EBR operation.
Table 5-14: EBR Conversion Preparation
Step
Action
Contact the OMCR, and:

1. Notify the operator that EBR conversion preparation is starting
2. Request the operator provide notification when the OMCR is ready to initialize the BTS.
If it was not previously done, verify the software version in the GLI3 card(s) as described in Chapter 4
of the packet backhaul upgrade manual for the BTS type (refer to the Required Documents and Related
Publications section of Chapter 1).
If it was not previously done, follow the procedure in Table 5-5 to verify the software version in the
GLI3 card(s)
If the GLI3 software requires upgrading for EBR capability,, review the GLI3 Required Software
Release, Operating Mode, and Loading Code section of this chapter to determine how to proceed with
loading IBR/EBRcapable software into the card.
NOTE
Only one card in a BTS with redundant GLI3s is required to have IBRcapable software. This card
must be the INS_ACT card (shows light green in the LMF) in the BTS. The INS_ACT GLI will be the
first card in the BTS which is downloaded with code and data from the LMF. The INS_ACT GLI3
will crossload the correct software to the INS_SBY GLI3.
5
Refer to the site documentation for EBR spans and inspect the BTS span cabling connections to be
sure they match the requirements.
! CAUTION
Do not crossconnect external BTS router span cables to active spans in the termination equipment
when performing the procedures in this step.
Correct any cabling discrepancies between the BTS span cabling and site documentation, referring to
the BTS hardware installation or packet backhaul upgrade manual as needed (Required Documents and
Related Publications section of Chapter 1)..
Inspect the BTS and BTStoEBR 10/100BaseT Fast Ethernet (FE) cabling and be sure it matches
the required configuration for the EBR group type installed (redundant or nonredundant) according to
the hardware installation or packet backhaul upgrade manual.
If the FE cabling has not yet been functionally verified, verify it as described in the Fast Ethernet
Verification chapter of the packet backhaul upgrade manual for the BTS type.
5-28
SEP 2009
continued
Table 5-14: EBR Conversion Preparation

Step
9
Action
NOTE
If it has not been done, be sure to mark the EBR end of BTStoEBR FE cables for proper
reconnection before performing this step.
Disconnect BTStoEBR FE cables from the EBR FE interface connectors, and use FE crossover
cables (Table 5-13) to connect the EBR FE interface connectors as follows:
S FE0 of BTSRTR 1 to connector FE0 of BTSRTR2

S FE1 of BTSRTR 1 to connector FE1 of BTSRTR2
10
If it has not been done, apply power to the external BTS router(s) by setting the facility circuit breaker
for each router to ON.
11
Configure the GLI3 card file transfer protocol settings to match what is required for network operation
by performing the Configuring BTS File Transfer Protocol New BTS Installation procedure in this
chapter.
12
Proceed to the Convert GLI3 cards to EBR operation portion of this section.
SEP 2009
5-29
continued
Convert GLI3 Cards to EBR

Operation
When notified that the OMCR is prepared for BTS initialization,

perform the following procedure.
Table 5-15: Convert GLI3 Cards to EBR Operation
Step
Action
Following the procedure in Table 3-10, establish an MMI communication session with the INS_SBY
GLI3 card.
Enter the following command to configure the GLI3 card to EBR operation:
convert_ebr

GLI3> convert_ebr
11.24.2003 23:14:57 MGLI0041
5
Setting backhaul mode to EBR
Successfully set backhaul mode to: EBR
To complete the conversion to EBR, this GLI must be reset!
For redundant frames, perform the following:

1. Disconnect the MMI cable from the INS_SBY GLI3 card
Repeat step 2, above, for the INS_ACT GLI3 card, and then proceed to step 5, below.
For redundant frames, reconnect the MMI cable to the INS_SBY GLI3 card and press the Enter key
to display the GLI3 > prompt.
5-30
SEP 2009
continued

Step
6
Action
NOTE
In redundant frames, the INS_SBY GLI3 card must be reset first. Then the INS_ACT GLI3 card must
be reset (step 7) within approximately 45 seconds of the INS_SBY GLI3 (step 6) to make sure neither
card reboots with configuration files for operation with external BTS routers. If one GLI3 completes
initialization before the other is reset, steps 1 and 2 must be repeated for each card and the cards reset
again.
Perform the following within 45 seconds of resetting the INS_SBY GLI3 card:
1.
2.
3.
4.
Disconnect the MMI cable from the INS_SBY GLI3 card

Connect the MMI cable to the INS_ACT GLI3 card
NOTE
If the INS_ACT GLI3 card cannot be reset before the INS_SBY GLI3 card completes its reboot,
perform steps 1 through 5 again for each card, reset the INS_SBY GLI3, and then reset the INS_ACT
GLI3 card using the hardware RESET button on the front of each card.
8
When both cards complete their initialization after being reset, terminate the MMI communication
session and disconnect the LMF computer from the GLI3 card.
NOTE
The remaining steps in this procedure must be performed within 50 minutes (redundant cards) or 25
minutes (nonredundant card) to prevent the GLI3 cards from automatically rebooting to their last
known good operating mode. If cards selfinitiate configuration fall back before the OMCR takes
control, the convert_ebr procedure in steps 1 through 8 must be performed again.
9
Disconnect the FE crossover cables interconnecting the external BTS router FE connectors (Table 5-9,
step 9) and remove the cables from the routers.
10
Connect the FE cabling between the external BTS router FE connectors and the BTS FE interface
housing or ESM EXTERNAL connectors according to the cable markings and the applicable
procedure in the packet backhaul upgrade manual for the BTS type.
11
Crossconnect each external BTS router span cable or span Ycable to the specified site span in the
termination equipment (refer to the span connection section of the packet backhaul upgrade manual for
the BTS type).
12
Connect the ground lug for each router span cable or span Ycable to the ground stud at the
termination equipment.
SEP 2009
5-31
continued

Step
Action
13
Verify BTS router span cable connections with site documentation and the span connection section of
the packet backhaul upgrade manual for the BTS type, as applicable.
14
Contact the OMCR and advise the operator that:
S The convert_ebr command has been executed on the GLI3 card(s)

S All EBR cabling is complete
S The site is ready for operational verification
15
When advised that there is no further requirement for onsite support of EBR initialization, proceed to
Chapter 6, and follow the procedures to prepare to leave the site.
5-32
SEP 2009
Configuring BTS File Transfer Protocol Introduction

Motorola BTS models have used File Transfer Protocol (FTP) to transfer
data to and from the OMCR since the introduction of packet data
transport. Evolution of the traditional closed transport system to an Open
Transport Interface (OTI) has emphasized the need to provide customers
with increased security for data transfers. Motorola has incorporated
Secure FTP (SFTP) into the CDMA Network Elements (NE) to address
the problem of data security over open, unsecured networks. SFTP is
supported on all Motorola NE and Operations Support Subsystems
(OSS) beginning with CDMA software release 2.21.0.
The LMF is equipped with a utility which is used to select either FTP or
SFTP for information transfer between the BTS and the OMCR. This
utility is only used at the cell site before communication is established
with the OMCR to select the transfer protocol for a newly installed
BTS (greenfield) or after replacement of a nonredundant GLI3 card.
LMF file transfer protocol
setting utility
When the LMF is logged into a BTS, the file transfer protocol utility is
available as the Secure FTP Settings selection under Util on the BTS
tab menu bar . The Secure FTP Settings dialog box for the utility
contains a number of selection items which are available depending on
the protocol with which the BTS is operating.
NOTE
The protocol being used by the BTS is marked with a black
dot in its radio button when the dialog box first opens.
Table 5-16: LMF File Transfer Protocol Selections

Selection
Location in
Dialog Box
Description
Conditions when
Selection Can Be
Chosen
FTP
Protocol
group
Protocol to be used for transferring files

in unencrypted form to and from
NE
BTS is operating with

SFTP
SFTP
Protocol
group
Protocol to be used for transferring files

in encrypted form to and from NE

FTP
SEP 2009
5-33
continued
Table 5-16: LMF File Transfer Protocol Selections

Selection
Location in
Dialog Box
Change protocol
type with current
settings
Action group
Reset username
and password
Action group
Description
Change file transfer protocol from type

currently used without making any
changes to username, password, or key
Resets current username and password to

CDMA RAN default settings
NOTE
This selection can be used:
1. During conversion from FTP to SFTP
2. While BTS is operating with SFTP
without changing the protocol
5-34
Conditions when
Selection Can Be
Chosen
1. BTS is operating with
FTP, and...
2. SFTP is selected
(radio button is black)
Condition 1:
1. BTS is operating with
FTP, and...
2. SFTP is selected
(radio button is black)
...or...
Condition 2:
SFTP
SEP 2009
Configuring BTS File Transfer Protocol New BTS Installation

The procedures in this section specifically cover configuring the file
transfer protocol of a new BTS.
CAUTION
This procedure must be performed before converting the
GLI3 cards for operation with Integrated BTS Router
(IBR), External BTS Routers (EBR), or Open Transport
Interface (OTI) backhaul. Failure to perform this procedure
first can result in the BTS failing to synchronize with the
OMCR and delays in placing the site in service.
Prerequisites
The following conditions must be met before performing the procedures:

S The required transfer protocol for the BTS has been specified by the
network operator and provisioned at the OMCR
S The BTS has power applied, and is operating without traffic or
communication with the OMCR
S The procedures in this section specifically cover configuring the file
transfer protocol of a new BTS
S LMF application must be operating and logged into the BTS
Determining the operating file
transfer protocol
To configure the BTS or replacement GLI3 card file transfer protocol, it

is necessary to first determine if the current protocol on which the BTS
is operating is the one required. Determine the operating protocol by
performing the following.
Table 5-17: Determine Operating File Transfer Protocol Using the LMF
Step
1
Action
On the BTS tab menu bar select Util > Secure FTP Settings.
Result: The Secure FTP Settings dialog box will open.
Examine the Protocol group to determine the protocol with the darkened radio button (FTP or SFTP).
NOTE
The protocol with the darkened radio button is the one with which the BTS is operating.
3
Do one of the following depending on the protocol setting provisioned for this BTS at the OMCR:
S If the button for the required protocol is not darkened, the protocol must be changed. Proceed to
Table 5-18 to change the protocol.
S If the button for the required protocol is darkened, continue to step 4.

SEP 2009
5-35
continued
Table 5-17: Determine Operating File Transfer Protocol Using the LMF
Step
4
Action
If the required operating protocol is SFTP, click in the radio button for Reset username and
password in the Action group.
Result: The radio button for the selected choice will darken.
Click OK.
Result: Selected settings are applied, and the dialog box closes.
Proceed with converting the GLI3 cards to IBR, EBR, or OTI operation as specified in those sections
of this manual, as applicable.
Changing the operating file

transfer protocol
Change the file transfer protocol by performing the following.
Table 5-18: Change Operating File Transfer Protocol Using the LMF
Step
1
Action
If the Secure FTP Settings dialog box is not already open, open it by selecting Util > Secure FTP
Settings from the BTS tab menu bar.
Result: The Secure FTP Settings dialog box will open.
Do one of the following depending on the protocol setting required for operating this BTS on the
network:
S If FTP is required, click the FTP radio button in the Protocol group, and skip to step 4.
S If SFTP is required, click the SFTP radio button, and continue to step 3.
3
Click in the radio button for Reset username and password in the Action group.
Result: The radio button for the selected choice will darken.
Click OK.
Result: Selected settings are applied, and the dialog box closes.
5-36
Proceed with converting the GLI3 cards to IBR, EBR, or OTI operation as specified in those sections
of this manual, as applicable.
SEP 2009
GLI3 Software Release and Backhaul Mode Worksheet

NOTE
Copy this page and use it as a form to record the
information for a BTS.
Enter the information into Table 5-19 by performing the following:
1. Enter the BTS number assigned to the base station where the GLI3
cards are installed (for example, BTS180)
2. Enter the software version and backhaul mode required for the BTS
in the respective columns on the first line of Table 5-19.
3. Enter the software version of the code loaded in the GLI3 card
installed in BTS card cage slot GLI 1 when determined by
performing step 4 of Table 5-5.
4. Enter the backhaul mode of the GLI3 card installed in BTS card cage
slot GLI 1 when determined by performing step 9 of Table 5-5.
Software Version and Backhaul Mode
BTS#: _________________
Table 5-19: Software Release and Backhaul Mode Record

Software Release
SEP 2009
1.
Required for BTS
2.
GLI 1
Backhaul Mode
5-37
continued
Notes
5-38
SEP 2009
Chapter 6: Prepare to Leave the Site

Table of Contents
Updating Calibration Data Files Packet BTS . . . . . . . . . . . . . . . . . . . . . . . . .

Automated Calibration File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uploading Calibration File to the Master GLI3 in a Packet BTS . . . . .
6-1
6-1
6-1
6-4
Prepare to Leave the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

External Test Equipment Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBR Span Configuration Verification . . . . . . . . . . . . . . . . . . . . . . . . . .
Bringing Modules into Service with the LMF . . . . . . . . . . . . . . . . . . .
LMF Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reconnect BTS Spans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reset All Devices and Initialize Site Remotely . . . . . . . . . . . . . . . . . . .
6-5
6-5
6-5
6-9
6-10
6-10
6-11
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Updating Calibration Data Files Packet BTS

Automated Calibration File
Transfer
Beginning with Software Release 2.17.0, the user can load the
calibration (CAL) file from the LMF directly to the MGLI. The MGLI
will then:
1. Crossload the CAL file to the other GLI cards in the BTS
2. Crossload the BBX cards with their applicable TX calibration
parameters and reset the BBX cards
3. FTP the new CAL file to the OMCR during synchronization
This process eliminates the need for the user to transfer the CAL file to
the OMCR, either through FTP from the LMF computer or by using
the diskette transfer method.
Process Description
Figure 6-1 and Figure 6-2 provide a summary of the automated CAL file
transfer process showing the general steps required, decision points, and
messages provided to the user when applicable.
SEP 2009
6-1
continued
Figure 6-1: Automated Calibration File Transfer Process User and LMF Actions
START
Was CAL file updated
or created with current
TX BLO?
Perform procedure to
update/establish TX BLO.
Y
User commands LMF
to upload CAL file.
LMF opens window

showing upload progress
LMF begins
verification sequence
Does CAL file exist
in BTS folder on
LMF computer?
LMF displays an error

message that CAL file
does not exist and will not
be uploaded
Y
Is LMF FTP
server operating?
Can LMF
Connect to
MGLI?
LMF displays a warning

that LMF has problem
connecting to GLI FTP
server
Does user choose

to continue?
Does CAL file exist

on MGLI?
Y
LMF displays warning that this operation
will:
1. Overwrite the existing CAL file on
the GLI, and...
2. Result in synchronization between
GLI and OMCR
LMF displays a warning

that this operation will
result in synchronization
between GLI and
OMCR
Does user choose

to continue?
Y
LMF sends CAL file
upload request to
MGLI
N
LMF opens window
showing result of CAL
file upload process
LMF terminates CAL

file upload process
Go to
Figure 6-2
END
6-2
SEP 2009
continued
Figure 6-2: Automated Calibration File Transfer Process GLI3 and LMF Actions
From
Figure 6-1
MGLI receives CAL file

upload request from LMF
Is GLI synchronizing
with OMCR?
Does MGLI accept CAL

file upload from LMF
MGLI refuses upload

from LMF
Does CAL file upload

to MGLI succeed?
Y
Do other GLIs in BTS
accept MGLI distribution
request for new CAL file?
Y
Does CAL file
crossload to other
GLIs succeed?
Y
Does OMCR accept
MGLI request for
synchronization to upload
new CAL file?
LMF records failure of

CAL file to crossload
to other GLIs and
continues process
Y
Does CAL file upload
to OMCR succeed?
N
LMF records failure of
CAL file to upload to
OMCR and continues
process
LMF opens window

showing result of CAL
file upload process
LMF terminates CAL

file upload process
NOTE: The MGLI will refuse OMCR synchronization
requests while:
1. MGLI is in process of loading new CAL file from LMF
or
2. Crossloading new LMF CAL file to other GLIs in
the BTS.
SEP 2009
END
6-3
continued
Uploading Calibration File to

the Master GLI3 in a Packet
BTS
This procedure allows the user to upload a calibration (CAL) file from
the LMF computer to the MGLI in a packet BTS. It also causes the
MGLI to synchronize with the OMCR and transfer the uploaded CAL
file to the OMCR during the synchronization process.
Prerequisites
The following are required before performing this procedure:
S The LMF computer is connected to the BTS 10Base2 LAN

S The LMF application is logged into the BTS
S The BTS CAL file has been created and saved in the applicable BTS
folder on the LMF computer
S The BTS CAL file contains the current BLO calibration data
Procedure
Follow the procedure in Table 6-1 to upload a new CAL file from the
LMF computer to the MGLI and update the BTS CAL file on the
OMCR.
Table 6-1: Uploading Calibration File to a Packet BTS
Step
1
Action
In the LMF BTS tab menu bar, select BTS > Upload CAL file.
Result: A window will open showing progress of the upload CAL file process.
If issues are encountered during the upload process, error or warning messages will be displayed.
When the upload process ends, a window will open showing success or failure in the upload:
S If all the operations in the upload process are successful, the display will show complete success.
S If upload of the CAL file to the MGLI fails, the display will show complete failure without details.
S If CAL file crossload to other GLI cards fails, the display will show that operation failed but other
operations may be completed successfully.
S If CAL file upload to the OMCR fails, the display will show that operation failed but other
operations may be completed successfully.
NOTE
If the BTS is not enabled on the network or unable to communicate with the OMCR when the upload
process is performed, the CAL file upload to the OMCR will fail. The new CAL file will be uploaded
to the OMCR during the synchronization which will occur when communication is established
between the MGLI and the OMCR.
4
6-4
Click Save Results to save the information displayed or Dismiss to close the window.
SEP 2009
Prepare to Leave the Site

External Test Equipment
Removal
Perform the procedure in Table 6-2 to disconnect the test equipment and
prepare the BTS for active service.
Table 6-2: External Test Equipment Removal
Step
Action
Disconnect all external test equipment from all BTS TX and RX antenna cable connectors.
Visually inspect all TX and RX antennas cables and connect them to the BTS TX and RX antenna
cable connectors.
CAUTION
Verify that all sector antenna cables are connected to the
correct ports on the frame. Crossed antenna cables will
cause system degradation of call processing.
IBR Span Configuration

Verification
6
The procedure in Table 6-3 is required only for a packet BTS equipped
with Integrated BTS Router (IBR). Perform the procedure to verify the
current span parameter settings. ALL GLI3 cards in all CCCP shelves
that terminate a T1/E1 span should be verified.
Table 6-3: IBR Span Parameter Configuration
Step
Action
Connect the CDMA LMF computer to the MMI port on the applicable GLI as shown in Figure 6-3 or
Figure 6-4.
Start an MMI communication session with the applicable GLI by using the Windows desktop shortcut
icon (see Table 3-3).
Once the connection window opens, press the LMF computer Enter key until the GLI prompt is
obtained.
SEP 2009
6-5
continued
Table 6-3: IBR Span Parameter Configuration

Step
Action
Verify the span parameter settings for frame format, equalization, and linkspeed for the span to be used
by entering the following at the GLI3> prompt:
config ni current
(equivalent of span view command)
The system will respond with a display similar to the following:

The frame format in flash
Equalization:
Span A Default (0131
Span B Default (0131
Span C Default (0131
Span D Default (0131
Span E Default (0131
Span F Default (0131
is set to use T1_2.

feet
feet
feet
feet
feet
feet
for
for
for
for
for
for
T1/J1,
T1/J1,
T1/J1,
T1/J1,
T1/J1,
T1/J1,
120
120
120
120
120
120
Ohm
Ohm
Ohm
Ohm
Ohm
Ohm
for
for
for
for
for
for
E1)
E1)
E1)
E1)
E1)
E1)
Linkspeed: 64K
Currently, the link is running at the default rate
The actual rate is 0
Loopback: OFF
NOTE
Defaults for span equalization are 0131 feet for T1/J1 spans and 120 Ohm for E1.
There is no need to change from defaults unless the span configuration provisioned in the OMCR
requires it.
Linkspeed is set automatically by the GLI3 for the span type selected.
The span configurations loaded in the GLI must match those in the OMCR database for the BTS. If
they do not, follow the procedure in Table 5-10 or Table 5-11, as applicable, to correct span settings
for IBR.
Repeat steps 1 through 5 for all remaining GLIs.
If no other MMI actions are required with the GLI cards, terminate the GLI MMI session and
HyperTerminal connection by selecting File from the connection window menu bar, and then Exit
from the dropdown menu.
6-6
SEP 2009
continued
Figure 6-3: GLI3 Card MMI Connection Detail
To MMI
Connector
8PIN
MMI
Connector
NULL MODEM
BOARD
(TRN9666A)
8PIN TO 10PIN
RS232 CABLE (P/N
3009786R01)
LMF COMPUTER
OR EQUIVALENT
6
RS232 CABLE
COM1
OR
COM2
SEP 2009
DB9TODB25
ADAPTER
6-7
continued
Figure 6-4: GLI3 Card MMI Connection Detail Fabricated MMI Cable
RESET
Button
To MMI
Connector
MMI
Connector
8PIN
LMF COMPUTER
OR EQUIVALENT
CABLE PART NUMBEr
CGDSMMICABLE219112
OR
COM1
OR
COM2
FABRICATED MMI CABLE

(SEE MMI CABLE
FABRICATION SECTION)
6
DB9
CONNECTOR
6-8
SEP 2009
continued
Bringing Modules into Service

with the LMF
NOTE
Whenever possible, have the OMCR bring up the site and
enable all devices at the BTS.
If there is a reason code and/or data should or could not be loaded
remotely from the OMCR, follow the steps outlined in Table 6-4 as
required to bring BTS processor modules from OOS to INS state.
Table 6-4: Bring Modules into Service
Step
1
Action
In the LMF GUI environment, select the device(s) to be enabled by clicking on each one.
NOTE
S The GLI and CSM must be INS_ACT (bright green) before an MCC can be enabled.
S Processors which must be enabled and the order of enabling are as follows:
1. GLI
2. CSMs
3. MCCs
2
Click on Device in the BTS menu bar, and select Enable from the pulldown list.
NOTE
If a BBX is selected, a transceiver parameters window is displayed to collect keying information. Do
not enable the BBX.
3
Click Cancel to close the transceiver parameters window, if applicable.

Result: The color of devices which successfully change to INS will change to light green.
SEP 2009
6-9
continued
LMF Removal
DO NOT power down the LMF without performing the

procedure below. Corrupted/lost data files may result, and
in some cases, the LMF may lock up.
Follow the procedure in Table 6-5 to terminate the LMF session and
remove the terminal.
Table 6-5: LMF Termination and Removal
Step
1
Action
From the CDMA window select File > Exit.
NOTE
The File > Exit command will prompt to confirm the logout request. The File > Logout and Exit
command will not prompt to confirm logout and will shut down the LMF.
From the Windows Task Bar click Start > Shutdown.
Click Yes when the Shut Down Windows message appears.
Disconnect the LMF terminal Ethernet connector from the BTS cabinet.
Disconnect cables from the LMF serial port, the RS-232toGPIB interface box, and any other cables
as required for equipment transport.
Reconnect BTS Spans
Before leaving the site, be sure any span connectors that were removed
from the BTS are reconnected. Refer to Table 6-6.
Table 6-6: Span/IFM Connections
Step
Action
Reconnect any disconnected span connectors to either the Span I/O A and B boards (frames with
IBR) or the BTS routers (frames with EBR).
Ensure that the CSU, if installed for IBR, is powered ON.
Verify the span status.
6-10
SEP 2009
continued
Reset All Devices and Initialize

Site Remotely
Devices in the BTS should not be left with data and code loaded from
the LMF. The configuration data and code loads used for normal
operation could be different from those stored in the LMF files. Perform
the procedure in Table 6-7 to reset all devices and initialize site remotely.
NOTE
Each module or device can be in any state prior to
downloading. Each module or device will be in an
OOS_RAM state after downloading has completed.
S For all LMF commands, information in italics
represents valid ranges for that command field.
S Only those fields requiring an input will be specified.

Default values for other fields will be assumed.
S For more complete command examples (including

system response details), refer to the LMF Help
function online documentation (part of the LMF
software application).
Table 6-7: Reset BTS Devices and Remote Site Initialization

Step
Action
Terminate the LMF session by following the procedures in Table 6-5.
Reconnect spans by following the procedure in Table 6-6.
6
SEP 2009
6-11
continued
Table 6-7: Reset BTS Devices and Remote Site Initialization

Step
3
Action
From the BTS site, contact the OMCR and request the operator to PREACTIVATE the BTS to the
required software version for the BSS. There are two types of PREACTIVATE load processes:
Rolling Upgrade: This load process is only available when the BTS cards are populated for full
redundancy as applicable.
Quick Reboot: This process is used when there is not full redundancy for the BTS cards. The
GLI3 will disable and reboot to the new load. This will cause all the other cards to go out of
service. Once it is rebooted, the GLI3 determines which cards require a new load and then
downloads the cards in the order which they establish communication with the GLI3 following
their reboot. The GLI3 can reload up to 16 devices simultaneously.
NOTE
preR18.0 software.
Wait at least 17 minutes for the card to complete this operation and/or the STA indicator to change to
slow flashing green before attempting to proceed with the next step.
Account for all tools used and parts removed from the frame during the operations, being sure none
were left inside the frame.
Visually inspect the frame for any foreign objects left inside, and remove any discovered.
Visually inspect all cable connections, ensuring they are connected as required for normal BTS
operation.
Be sure all internal frame cables are routed and secured to prevent damage to them when the frame
doors are closed.
Close and secure the cabinet doors.
Verify no alarm conditions are being reported to the OMCR with the frame doors closed.
10
After all activities at the site have been completed, contact the OMCR and confirm that the BTS is
under OMCR control.
6-12
SEP 2009
Chapter 7: Basic Troubleshooting

Table of Contents
Basic Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Log into Cell-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Force Ethernet LAN A to Active State as Primary LAN . . . . . . . . . . .
GLI IP Address Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unresponsive LMF operation with LMF R17 or earlier software . . . . .
Cannot Communicate with Power Meter . . . . . . . . . . . . . . . . . . . . . . .
Cannot Communicate with Communications Analyzer . . . . . . . . . . . .
Cannot Communicate with Signal Generator . . . . . . . . . . . . . . . . . . . .
Troubleshooting: Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can not perform any operation when using the Agilent E7595A/B . . .
Code Download Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Download DATA to Any Device (Card) . . . . . . . . . . . . . . . . . .
Cannot ENABLE Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PA Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting: Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can not perform any operation when using the Agilent E7595A/B . . .
Bay Level Offset Calibration Failure . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibration Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting: Transmit ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can not perform any test when using the Agilent E7595A/B . . . . . . . .
Forward link problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Perform Tx Mask Measurement . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Perform Rho or Pilot Time Offset Measurement . . . . . . . . . . .
Cannot Perform Code Domain Power and Noise Floor Measurement .
Cannot Perform Carrier Measurement . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary BBX Fails CD Power/Noise Floor Test After Redundant BBX
TX Tests, Software Release 2.18.0.x . . . . . . . . . . . . . . . . . . . . . . . . . . .
CD Power/Noise FloorTest Failures with Agilent E7495A/B Test Set .
Troubleshooting: Receive ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Can not perform any test when using the Agilent E7595A/B . . . . . . . .
MultiFER Test Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting: CSM Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
No GPS Reference Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSM Reference Source Configuration Error . . . . . . . . . . . . . . . . . . . . .
Takes Too Long for CSM to Come INS . . . . . . . . . . . . . . . . . . . . . . . .
SEP 2009
7-1
7-1
7-2
7-2
7-2
7-3
7-5
7-6
7-6
7-7
7-8
7-8
7-8
7-8
7-9
7-9
7-10
7-10
7-10
7-11
7-12
7-12
7-12
7-12
7-13
7-13
7-14
7-14
7-14
7-16
7-16
7-16
7-17
7-17
7-17
7-18
7-18
Table of Contents
continued
CCCP Backplane Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connector Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCCP Backplane Troubleshooting Procedure . . . . . . . . . . . . . . . . . . .
Digital Control Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC Power Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RFDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All tests fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All RX and TX paths fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All tests fail on a single antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-19
7-19
7-19
7-20
7-21
7-23
7-24
7-25
7-25
7-26
Troubleshooting: Span Control Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Span Problems (No Control Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set BTS Site Span Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-27
7-27
7-30

satellite backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing the correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-35
7-35
7-35
Module Front Panel LED Indicators and Connectors . . . . . . . . . . . . . . . . . . . . .

Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LED Status Combinations for All Modules (except GLI, CSM,
BBX, MCC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC/DC Converter LED Status Combinations . . . . . . . . . . . . . . . . . . . .
CSM Indicator and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GLI LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GLI Pushbuttons and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BBX LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PA Shelf LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCC LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-42
7-42
7-42
7-42
7-43
7-44
7-45
7-47
7-47
7-47
SEP 2009
Basic Troubleshooting Overview

Basic Troubleshooting Overview
Overview
The information in this chapter addresses some of the scenarios likely to

be encountered by Customer Field Engineering (CFE) team members.
This troubleshooting guide was created as an interim reference document
for use in the field. It provides basic what to do if basic
troubleshooting suggestions when the BTS equipment does not perform
per the procedure documented in the manual.
Comments are consolidated from inputs provided by CFEs in the field
and information gained form experience in Motorola labs and
classrooms.
SEP 2009
7-1
Troubleshooting: Installation
Cannot Log into Cell-Site
Follow the procedure in Table 7-1 to troubleshoot any Login Failure

problem during normal operation.
Table 7-1: Login Failure Troubleshooting Procedure
n Step
Action
If GLI LED is solid RED, it implies a hardware failure. Reset MGLI by re-seating it. If this
persists, install RGLI card in MGLI slot and retry. A Red LED may also indicate no Ethernet
termination at top of frame.
Determine if the OMCR still has control of the BTS.
Try pinging the MGLI.
Verify the LMF is connected to the Primary LMF port (LAN A) in front of the BTS.
Verify the LMF was configured properly.
Verify the BTS-LMF cable is RG-58 (flexible black cable of less than 2.5 feet length).
Verify the Ethernet ports are terminated properly.
Verify a T-adapter is not used on LMF side port if connected to the BTS front LMF primary port.
Try connecting to the I/O panel (back of frame). Use TriAx to BNC adapter at the LMF port for
this connection.
10
Re-boot the CDMA LMF and retry.
11
Re-seat the MGLI and retry.
12
Verify IP addresses are configured properly.
7
Force Ethernet LAN A to Active
State as Primary LAN
Table 7-2: Force Ethernet LAN A to Active State as Primary LAN

n Step
Action
If LAN A is not the active LAN, make certain all external LAN connectors are either terminated
with 50 loads or cabled to another frame.
If it has not already been done, connect the LMF computer to the standalone or starter frame, as
applicable (Table 3-5).
If it has not already been done, start a GUI LMF session and log into the BTS on the active LAN
(Table 3-6).
Remove the 50 termination from the LAN B IN connector in the power entry compartment at the
rear of the standalone or starter frame. The LMF session will become inactive.
7-2
SEP 2009
continued
Table 7-2: Force Ethernet LAN A to Active State as Primary LAN

n Step
Action
Disconnect the LMF computer from the LAN shelf LAN B connector and connect it to the LAN A
connector.
If the LAN was successfully forced to an active state (the cards in any cage can be selected and
statused), proceed to step 13.
With the 50 termination still removed from the LAN B IN connector, remove the 50
termination from LAN B OUT connector. If more than one frame is connected to the LAN,
remove the termination from the last frame in the chain.
If the LAN was successfully forced to an active state (the cards in any cage can be selected and
statused), proceed to step 13.
With the 50 terminations still removed from LAN B, unseat each GLI card in each frame
connected to the LAN, until all are disconnected from the shelf backplanes.
10
Reseat each GLI card until all are reconnected.
11
Allow the GLIs to power up, and attempt to select and status cards in the CCP shelves. If LAN A
is active, proceed to step 13.
12
If LAN A is still not active, troubleshoot or continue troubleshooting following the procedures in
Table 7-1.
13
Replace the 50 terminations removed from the LAN B IN and OUT connectors.
GLI IP Address Setting
Table 7-3: GLI IP Address Setting

n Step
Action
If it has not previously been done, establish an MMI communication session with the GLI card as
described in Table 3-10.
Enter the following command to display the IP address and subnet mask settings for the card:
config lg0 current

GLI2>config lg0 current
lg0: IP address is set to
DEFAULT (configured based on card location)
lg0: netmask is set to
DEFAULT (255.255.255.128)

SEP 2009
7-3
continued

n Step
3
Action
If the IP address setting response shows an IP address rather than Default (configured
based on card location), enter the following:
config lg0 ip default

GLI2>config lg0 ip default
_param_config_lg0_ip(): param_delete(): 0x00050001
lg0: ip address set to DEFAULT
If the GLI subnet mask setting does not display as DEFAULT (255.255.255.128), set it to
default by entering the following command:
config lg0 netmask default

GLI2>config lg0 netmask default
_param_config_lg0_netmask(): param_delete(): 0x00050001
lg0: netmask set to DEFAULT
Set the GLI route default to default by entering the following command:
config route default default

GLI2>config route default default
_esh_config_route_default(): param_delete(): 0x00050001

route: default gateway set to DEFAULT
NOTE
Changes to the settings will not take effect unless the GLI is reset.
When changes are completed, close the MMI session, and reset the GLI card.
7-4
SEP 2009
continued

n Step
7
Action
Once the GLI is reset, reestablish MMI communication with it and issue the following command
to confirm its IP address and subnet mask settings:
config lg0 current

GLI2>config lg0 current
lg0: IP address is set to
DEFAULT (configured based on card location)
lg0: netmask is set to
DEFAULT (255.255.255.128)
Repeat steps 1 through 7 for all remaining GLIs, including those in any additional,
interconnected frames.
Unresponsive LMF operation

with LMF R17 or earlier
software
When using R17 and earlier LMF versions needing Java Runtime
Environment (JRE) 1.4.1, a bug in this JRE version can cause the LMF
to become unresponsive when operating with some video cards. If this
problem occurs, turn off video card acceleration by doing the following.
Table 7-4: Turn Off Video Card Acceleration
n Step
Action
Rightclick on the Windows operating system desktop.
Select Properties from the popup menu.
Click the Settings tab in the Display Properties dialog box if it is not in the front.
Click the Advanced button on the Settings tab.
In the new dialog box, click on the Troubleshooting* tab to bring it to the front.
Set Hardware acceleration to None.
Click the OK button on the dialog box.
Click the OK button on the Display Properties dialog.

SEP 2009
7-5
continued
Table 7-4: Turn Off Video Card Acceleration

n Step
9
Action
Restart the computer if directed to do so.
* The tab on which the hardware acceleration control is located may have any of several names. On some
comupters it is named Performance. In all cases, the tab is found by pressing the Advanced button on the
Settings tab in the Display Properties dialog box.
Cannot Communicate with

Power Meter
Table 7-5: Troubleshooting a Power Meter Communication Failure

n Step
Action
Verify the Power Meter is connected to the LMF with a GPIB adapter.
Verify the cable setup as specified in Chapter 3.
Verify the GPIB address of the power meter is set to the same value displayed in the applicable
GPIB address box of the LMF Options window Test Equipment tab. Refer to Table 3-27 or
Table 3-28 and the applicable power meter Verifying and Setting GPIB Addresses section of
Appendix F for details.
Verify the GPIB adapter DIP switch settings are correct. Refer to the Verifying and Setting GPIB
Addresses RS232 GPIB Interface Box section of Appendix F for details.
Verify the GPIB adapter is not locked up. Under normal conditions, only two green LEDs must be
ON (Power and Ready). If any other LED is continuously ON, then power-cycle the GPIB Box
and retry.
Verify the LMF computer COM1 port is not used by another application; for example, if a
HyperTerminal window is open for MMI, close it.
Reset all test equipment by clicking Util in the BTS menu bar and selecting
Test Equipment > Reset from the pulldown lists.

Communications Analyzer
Table 7-6: Troubleshooting a Communications Analyzer Communication Failure

n Step
Action
If using the Agilent E7495A/B or other network connection (IPbased connection) analyzer,
TURN OFF any firewall or intrusion protection software installed on the LMF computer platform.
Verify the analyzer is connected to the LMF with GPIB adapter.
Verify the cable setup.

7-6
SEP 2009
continued
Table 7-6: Troubleshooting a Communications Analyzer Communication Failure

n Step
Action
Verify the signal generator GPIB address is set to the same value displayed in the applicable GPIB
address box of the LMF Options window Test Equipment tab. Refer to Table 3-27 or Table 3-28
and the applicable communications analyzer Verifying and Setting GPIB Address section of
Appendix F for details.
Verify the GPIB adapter DIP switch settings are correct. Refer to the Verifying and Setting GPIB
Addresses RS232 GPIB Interface Box section of Appendix F for details.
Verify the GPIB adapter is not locked up. Under normal conditions, only two green LEDs must be
ON (Power and Ready). If any other LED is continuously ON, then cycle the GPIB box power
and retry.
Reset all test equipment by clicking Util in the BTS menu bar and selecting
Test Equipment > Reset from the pulldown lists.

Signal Generator
Table 7-7: Troubleshooting a Signal Generator Communication Failure

n Step
Action
Verify signal generator is connected to LMF with GPIB adapter.
Verify cable connections as specified in Chapter 3.
Verify the signal generator GPIB address is set to the same value displayed in the applicable GPIB
address box of the LMF Options window Test Equipment tab. Refer to Table 3-27 or Table 3-28
and the Setting GPIB Addresses section of Appendix F for details.
Verify the GPIB adapter DIP switch settings are correct. Refer to Test Equipment Preparation
section of Appendix F for details.
Verify the GPIB adapter is not locked up. Under normal conditions, only 2 green LEDs must be
ON (Power and Ready). If any other LED is continuously ON, then cycle GPIB box power and
retry.
Reset all test equipment by clicking Util in the BTS menu bar and selecting Test Equipment >
Reset from the pulldown lists.
SEP 2009
7-7
Troubleshooting: Download
Can not perform any operation
when using the Agilent
E7595A/B
Perform the procedure in Table 7-14 of the Troubleshooting: Transmit

ATP section when attempting to perform any operation using the Agilent
E7495A or B communication test set and the following message is
received:
Unable to receive desired data packet, too many
errors
Code Download Failure
Follow the procedure in Table 7-8 to troubleshoot any code download

failure.
Table 7-8: Troubleshooting Code Download Failure
n Step
Action
Be sure the OMCR does not have control of the BTS.
Verify LMF can communicate with the BTS device using the Status function.
Communication to MGLI must first be established before trying to talk to any other BTS device.
MGLI must be INS_ACT state (green).
Verify the card is physically present in the cage and powered-up.
If card LED is solid RED, it implies hardware failure. Reset card by re-seating it. If this persists,
replace card from another slot & retry.
NOTE
The card can only be replaced by a card of the same type.
Re-seat card and try again.
If a BBX reports a failure message and is OOS_RAM, the code load was OK. Use the LMF
Status function to verify the load.
If the download portion completes and the reset portion fails, reset the device by selecting the
device and Reset.
If a BBX or an MCC remains OOS_ROM (blue) after code download, use the LMF
Device > Status function to verify that the code load was accepted.
10
If the code load was accepted, use LMF Device > Download > Flash to load RAM code into flash
memory.
Cannot Download DATA to Any

Device (Card)
Follow the procedure in Table 7-9 to troubleshoot any data download

failure.
7-8
SEP 2009
continued
Table 7-9: Troubleshooting Data Download Failure

n Step
Action
Re-seat card and repeat code and data load procedure.
Verify the ROM and RAM code loads are of the same release by statusing the card. Refer to
Chapter 3, Download the BTS for more information.
Cannot ENABLE Device
Before a device can be enabled (placed in-service), it must be in the

OOS_RAM state (yellow on the LMF) with data downloaded to the
device. The color of the device on the LMF changes to green, once it is
enabled.
The three states that devices can be displayed:
S Enabled (green, INS)
S Disabled (yellow, OOS_RAM)
S Reset (blue, OOS_ROM)
Table 7-10: Troubleshooting Device Enable (INS) Failure
n Step
Action
Re-seat card and repeat code and data load procedure.
If CSM cannot be enabled, verify the CDF file has correct latitude and longitude data for cell site
location and GPS sync.
Ensure primary CSM is in INS_ACT state.
NOTE
MCCs will not go INS without the CSM being INS.
4
Verify 19.6608 MHz CSM clock; MCCs will not go INS otherwise.
The BBX should not be enabled for ATP tests.
If MCCs give invalid or no system time, verify the CSM is enabled.
PA Errors
Follow the procedure in Table 7-11 to troubleshoot any PA errors.

Table 7-11: PA Errors
n Step
1
SEP 2009
Action
If PAs continue to give alarms, even after cycling power at the circuit breakers, then connect an
MMI cable to the PA and set up a Hyperterminal connection. Enter ALARMS in the
Hyperterminal window. The resulting LMF display may provide an indication of the problem.
(Call Field Support for further assistance.)
7-9
Troubleshooting: Calibration
Can not perform any operation
when using the Agilent
E7595A/B

received:
errors
Failure
Follow the procedure in Table 7-12 to troubleshoot a BLO calibration

failure.
Table 7-12: Troubleshooting BLO Calibration Failure
n Step
7-10
Action
Verify the Power Meter is configured correctly (see the test equipment setup section) and
connection is made to the proper TX port.
Verify the parameters in the bts#.cdf file are set correctly for the following bands:
For 1900 MHz:
BandClass=1; FreqBand=16
For 800 MHz:
BandClass=0; FreqBand=8
Verify that no PA in the sector is in alarm state (flashing red LED). Reset the PA by pulling the
circuit breaker, and after 5 seconds, pushing back in.
Re-calibrate the Power Meter and verify it is calibrated correctly with cal factors from sensor head.
Verify GPIB adapter is not locked up. Under normal conditions, only 2 green LEDs must be ON
(Power and Ready). If any other LED is continuously ON, power-cycle (turn power off and on)
the GPIB Box and retry.
Verify sensor head is functioning properly by checking it with the 1 mW (0 dBm) Power Ref
signal.
If communication between the LMF and Power Meter is operational, the Meter display will show
RES :
Verify the combiner frequency is the same as the test freq/chan.
SEP 2009
continued
Calibration Audit Failure
Follow the procedure in Table 7-13 to troubleshoot a calibration audit

failure.
Table 7-13: Troubleshooting Calibration Audit Failure
n Step
Action
Verify Power Meter is configured correctly (refer to the test equipment setup section of chapter 3).
Re-calibrate the Power Meter and verify it is calibrated correctly with cal factors from sensor head.
Verify that no PA is in alarm state (rapidly flashing red LED). Reset the PA by pulling the circuit
breaker, and, after 5 seconds, pushing back in.
Verify that no sensor head is functioning properly by checking it with the 1 mW (0 dBm) Power
Ref signal.
After calibration, the BLO data must be re-loaded to the BBX2s before auditing. Click on the
BBX(s) and select Device>Download BLO
Re-try the audit.
Verify GPIB adapter is not locked up. Under normal conditions, only 2 green LEDs must be ON
(Power and Ready). If any other LED is continuously ON, power-cycle (turn power off and on)
the GPIB Box and retry.
SEP 2009
7-11
Troubleshooting: Transmit ATP

Can not perform any test when
using the Agilent E7595A/B
Perform the following procedure when attempting to perform any test

using the Agilent E7495A or B communication test set and the following
message is received:
errors
Table 7-14: Correcting E7495A/B Test Set Communication Failure
n Step
1
Action
Determine the manufacturer of the Network Interface Card (NIC) installed in the LMF computer
by accessing the Windows operating system Device Manager function.
! CAUTION
A user must have Adminisrtrator priveliges on the computer to make changes using Device
Manager. If unfamiliar with this function, get help from a person experienced in configuring the
Windows operating system. Incorrectly changing settings with Device Manager can cause the
computer to become unuseable.
2
Download and install the latest driver(s) for the NIC from the manufacturers web site.
If the problem continues, locate the latest drivers for all NICs installed on the LMF computer.
Download and store the drivers in a new folder on the LMF computer.
Uninstall all of the NICs using the Windows operating system Device Manager.
Reinstall all of the NICs using the new drivers downloaded in step 4, above.
Forward link problem
If the BTS passes the reduced ATP tests but has a forward link problem
during normal operation follow the procedure in Table 7-15 to
troubleshoot.
Table 7-15: Troubleshooting Forward Link Failure (BTS Passed Reduced ATP)
n Step
1
Action
Perform these additional TX tests to troubleshoot a forward link problem:
TX mask
TX rho
TX code domain
Cannot Perform Tx Mask

Measurement
Follow the procedure in Table 7-16 to troubleshoot a TX Mask

Measurement failure.
7-12
SEP 2009
continued
Table 7-16: Troubleshooting TX Mask Measurement Failure

n Step
Action
Verify that TX audit passes for the BBX(s).
If performing manual measurement, verify analyzer setup.
Verify that no PA in the sector is in alarm state (flashing red LED). Re-set the PA by pulling the
circuit breaker, and, after 5 seconds, pushing it back in.
Cannot Perform Rho or Pilot

Time Offset Measurement
Table 7-17: Troubleshooting Rho and Pilot Time Offset Measurement Failure
n Step
Action
Verify presence of RF signal by switching to spectrum analyzer screen.
Verify PN offsets displayed on the analyzer is the same as the PN offset in the CDF file.
Reload MGLI data and repeat the test.
If performing manual measurement, verify analyzer setup.
Verify that no PA in the sector is in alarm state (flashing red LED). Reset the PA by pulling the
circuit breaker, and, after 5 seconds, pushing back in.
If Rho value is unstable and varies considerably (e.g. .95,.92,.93), this may indicate that the GPS
is still phasing (i.e. trying to reach and maintain 0 freq. error). Go to the freq. bar in the upper
right corner of the Rho meter and select Hz. Press <Shiftavg> and enter 10, to obtain an average
Rho value. This is an indication the GPS has not stabilized before going INS and may need to be
re-initialized.
7
Cannot Perform Code Domain
Power and Noise Floor
Measurement
Follow the procedure in Table 7-18 to troubleshoot code domain and

noise floor measurement failure.
Table 7-18: Troubleshooting Code Domain Power and Noise Floor Measurement Failure
n Step
Action
Verify presence of RF signal by switching to spectrum analyzer screen.
Verify PN offset displayed on analyzer is same as PN offset being used in the CDF file.
Disable and re-enable MCC (one or more MCCs based on extent of failure).
SEP 2009
7-13
continued
Cannot Perform Carrier

Measurement
Table 7-19: Troubleshooting Carrier Measurement Failure

n Step
1
Action
Perform the test manually, using the spread CDMA signal. Verify High Stability 10 MHz
Rubidium Standard is warmed up (60 minutes) and properly connected to test set-up.
Primary BBX Fails CD

Power/Noise Floor Test After
Redundant BBX TX Tests,
For software release 2.18.0.x, the CD power/noise floor test on a primary

BBX can fail if the test is performed after any TX testing of the
redundant BBX (BBXR) which used the Standard test pattern. Perform
the following to retest primary BBXs which failed.
Table 7-20: Troubleshooting Carrier Measurement Failure
Step
Action
Reload MCCs used in BBXR testing by performing the procedure in Table 4-2.
Repeat CD/noise floor test for primary BBX(s) which failed.
CD Power/Noise FloorTest
Failures with Agilent E7495A/B
Test Set
Using an Agilent E7495 test set equipped with version A.06.00 firmware
or earlier, this test can fail when a number of successive channels are
keyed with the same spread factor and similar power (usually less than
1dB difference). An E7495 test set with the above firmware versions
may erroneously detect the multiple channels as a single channel with a
higher spread factor and power.
E7495A/B Test Failure Workaround
CD power/noise foor tests which fail under these conditions should be
performed again following the procedure in Table 7-21.
7-14
SEP 2009
continued
Table 7-21: CD Power/Noise Floor Test Failure Workaround for Agilent E7495A/B
Step
1
Action
Change the Measurement Time setting on the E7495A/B test set as follows:
1. Press the ESC/Lcl button on the E7495 front panel.
2. Press the Mode button on the E7495 front panel.
3. Press the TX Analyzer menu softkey selection (next to the test set display screen).
4. Press the CDMA Analyzer menu softkey selection which appears in the TX Analyzer menu.
5. Press the Setup menu softkey selection which appears in the CDMA Analyzer menu.
6. Press the Measurement Time softkey selection appearing in the Setup menu, repeating until Slow
appears.
NOTE
Changing the Measurement Time setting on the E7495 will reduce but not completely eliminate the
chance of the CD power/noise floor test failing.
2
From the LMF Login tab, open the LMF Options window by selecting Tools > Options.
Be sure the Agilent E7495:

1. Is selected in the Test Equipment tab under Non Gpib Test Equipment, and...
2. Test set IP address is correctly entered in the Non Gpib Test Equipment IP address window
Press the Apply button to close the LMF Options window.
Log into the BTS.
Use the LMF to perform the CD power/noise floor test as described in the Test Equipment Setup and
Automated ATP sections of this publication.
SEP 2009
7-15
Troubleshooting: Receive ATP

Troubleshooting: Receive ATP
Can not perform any test when
using the Agilent E7595A/B

received:
errors
MultiFER Test Failure
Follow the procedure in Table 7-22 to troubleshoot multiFER failure.

Table 7-22: Troubleshooting Multi-FER Failure
n Step
Action
Verify test equipment set up is correct for a FER test.
Verify test equipment is locked to 19.6608 and even second clocks. The yellow LED (REF
UNLOCK) must be OFF.
Verify MCCs have been loaded with data and are INSACT.
Disable and re-enable the MCC (one or more based on extent of failure).
Disable, re-load code and data, and re-enable MCC (one or more MCCs based on extent of
failure).
Verify antenna connections to frame are correct based on the directions messages.
7-16
SEP 2009
Troubleshooting: CSM Checklist

Problem Description
Many of the Clock Synchronization Manager (CSM) card failures may

be resolved in the field before sending the cards to the factory for repair.
This section describes known CSM problems identified in field returns,
some of which are field-repairable. Check these problems before
returning suspect CSM cards.
No GPS Reference Source
Correct Hardware
Check the CSM cards for proper hardware configuration for the type of
GPS in use and the cage slot where they are installed.
RFGPS (Local GPS) CSM kit SGLN1145, which should be installed
in card slot l, has an oncard GPS receiver; while kit SGLN4132, in card
slot 2, does not have a GPS receiver.
Remote GPS (RGPS) Kit SGLN4132ED or later, which should be
installed in both card slot 1 and card slot 2, does not have a GPS
receiver. Any incorrectly configured card must be returned to the repair
center. Do not attempt to change hardware configuration in the field.
GPS Subsystem Installation
1. Inspect the GPS antenna and cabling for damage, water leaks, or
loose connections.
2. Verify that the GPS antenna and lightning arrestor have not been
damaged by lightning strikes.
3. Verify that the GPS antenna has a clear view to the sky. The GPS
antenna should ideally have a clear view in all directions for
elevations above 20 degrees from the horizon. Suitable GPS
operation can be realized with as much as a 50 percent blockage in
visibility. Any decrease in visibility greater than 50 percent will
likely result in increased numbers of GPS reference source failure
alarms.
SEP 2009
7-17
continued
CSM Reference Source

Configuration Error
This problem is caused by incorrect reference source configuration

performed in the field by software download. CSM kits SGLN1145 and
SGLN4132 must have proper reference sources configured (as shown
below) to function correctly.
CSM Kit
No.
Hardware
Configuration
CSM Slot
No.
Reference Source
Configuration
CDF Value
SGLN1145
With GPS Receiver
Primary = Local GPS

Backup = HSO
0
2 or 18
SGLN4132
Without GPS Receiver
Primary = Remote GPS

Backup = HSO
1
2 or 18
Takes Too Long for CSM to

Come INS
Investigate the following to identify the source of delays in CSM cards

reaching the INS state:
GPS acquisition delay This problem may be caused by a delay in
GPS acquisition. Check the accuracy flag status and/or current position.
Refer to the CSM System time GPS, LFR and HSO/MSO verification
section in Chapter 3. At least one satellite should be visible and tracked
for the surveyed mode and four satellites should be visible and tracked
for the estimated mode. Also, verify correct base site position data
used in surveyed mode.
GPS satellite reception problems Delays in bringing CSM cards INS
are usually due to GPS satellite reception problems. Verify that the GPS
antenna is provided with a clear view to the sky. The GPS antenna
should ideally have a clear view in all directions for elevations above 20
degrees to the horizon. Suitable GPS operation can be realized with as
much as a 50% blockage in visibility. Any decrease in visibility beyond
50% will likely result in increased CSM initialization times.
Antenna system path losses Verify that no more than a 10dB signal
loss at a 1.575GHz frequency is present between the GPS antenna and
RF modem frame GPS antenna input. The total GPS antenna system
noise figure (including all preamplifiers, cabling and splitter losses) must
be less than 4.0dB. Higher GPS antenna system noise figures will result
in degraded GPS receiver performance.
Antenna location coordinates Verify that the GPS antenna coordinate
information contained in the BTS CDF or NEC file is accurate. The
<BtsLatGps>, <BtsLongGps> and <BtsHeightGps> should be within
+/200m in the estimated mode and +/30m in the surveyed mode. The
surveyed mode should only be used when absolutely necessary.
7-18
SEP 2009
CCCP Backplane Troubleshooting

Overview
The CCCP backplane is a multilayer board that interconnects all the

CCCP modules. The complexity of this board lends itself to possible
improper diagnoses when problems occur.
Connector Functionality
The following connector overview describes the major types of

backplane connectors along with the functionality of each. This will
allow the Cellular Field Engineer (CFE) to:
S Determine which connector(s) is associated with a specific problem
type.
S Allow the isolation of problems to a specific cable or connector.
Primary A and Redundant B ISB (Inter Shelf Bus)
connectors
The 40 pin ISB connectors provide an interface bus from the master GLI
to all other GLIs in the modem frame. Its basic function is to provide
clock synchronization from the master GLI to all other GLIs in the
frame.
The ISB is also provides the following functions:
S Groom span line when a single span is used for multiple cages.
S Provide MMI connection to/from the master GLI to cell site modem.
S Provide interface between GLIs and the AMR (for reporting BTS
alarms).
Span Line Connector
The span line input is an 8 pin RJ45 connector that provides a primary
and secondary (if used) span line interface to each GLI in the CCCP
shelf. The span line is used for MM/EMX switch control of the Master
GLI and also all the BBX traffic.
Power Input (Return A, B, and C connectors)
Provides a +27 Volt input for use by the power supply modules.
Power Supply Module Interface
Each power supply module has a series of three different connectors to
provide the needed inputs/outputs to the CCCP backplane. These
include a VCC/Ground input connector, a Harting style multiple pin
interface, and a +15 V/Analog Ground output connector. The Transceiver
Power Module converts 27/48 Volts to a regulated +15, +6.5, +5.0 Volts
to be used by the CCCP shelf cards.
GLI Connector
This connector consists of a Harting 4SU digital connector and a
6conductor coaxial connector for RDM distribution. The connectors
provide inputs/outputs for the GLIs in the CCCP backplane.
SEP 2009
7-19
continued
GLI Ethernet A and B Connections

These BNC connectors are located on the CCCP backplane and routed
to the GLI board. This interface provides all the control and data
communications between the master GLI and the other GLIs, between
gateways, and for the LMF on the LAN.
BBX Connector
Each BBX connector consists of a Harting 2SU/1SU digital connector
and two 6conductor coaxial connectors. These connectors provide DC,
digital, and RF inputs/outputs for the BBXs in the CCCP backplane.
CIO Connectors
S RX RF antenna path signal inputs are routed through RX TriFilters
(on the I/O plate), and via coaxial cables to the two MPC modules
the six A (main) signals go to one MPC; the six B (diversity) to
the other. The MPC outputs the lownoiseamplified signals via the
CCCP backplane to the CIO where the signals are split and sent to
the appropriate BBX.
S A digital bus then routes the baseband signal through the BBX, to the
backplane, then on to the MCC slots.
S Digital TX antenna path signals originate at the MCC24s. Each
output is routed from the MCC slot via the backplane appropriate
BBX.
S TX RF path signal originates from the BBX, through the backplane to

the CIO, through the CIO, and via multi-conductor coaxial cabling to
the PAs in the PA shelf.
CCCP Backplane
Troubleshooting Procedure
The following table provides a standard procedure for troubleshooting

problems that appear to be related to a defective CCCP backplane. The
table is broken down into possible problems and steps which should be
taken in an attempt to find the root cause.
NOTE
It is important to note that all steps be followed before
replacing ANY CCCP backplane.
7-20
SEP 2009
continued
Digital Control Problems
No GLI Control via LMF (all GLIs)

Follow the procedure in Table 7-23 for problems with GLI control.
Table 7-23: No GLI Control via LMF (all GLIs)
Step
Action
Check the ethernet for proper connection, damage, shorts, or opens.
Verify CCCP backplane Shelf ID DIP switch is set correctly.
Visually check the master GLI connector (both board and backplane) for damage.
Replace the master GLI with a known good GLI.
No GLI Control through Span Line Connection (All GLIs)

Table 7-24: No GLI Control through Span Line Connection (Both GLIs)
Step
Action
Verify CCCP backplane Shelf ID DIP switch is set correctly.
Verify that the BTS and GLIs are correctly configured in the OMCR/CBSC data base.
Check the span line inputs from the top of the frame to the master GLI for proper connection and
damage.
MGLI Control Good No Control over Colocated GLI

Table 7-25: MGLI Control Good No Control over Colocated GLI
Step
Action
Verify that the BTS and GLIs are correctly configured in the OMCR CBSC data base.
Check the ethernet for proper connection, damage, shorts, or opens.
Visually check all GLI connectors (both board and backplane) for damage.
Replace the remaining GLI with a known good GLI.
SEP 2009
7-21
continued
No AMR Control (MGLI good)

Follow the procedure in Table 7-26 for problems with AMR control.
Table 7-26: MGLI Control Good No Control over AMR
Step
Action
Replace the AMR with a known good AMR.
No BBX Control in the Shelf

Follow the procedure in Table 7-27 for problems with colocated GLI.
Table 7-27: MGLI Control Good No Control over Colocated GLIs
Step
Action
Visually check BBX connectors (both board and backplane) for damage.
Replace the BBX with a known good BBX.
No (or Missing) Span Line Traffic

Follow the procedure in Table 7-28 for problems with span line traffic.
Table 7-28: BBX Control Good No (or Missing) Span Line Traffic
7
Step
Action
Visually check all span line distribution (both connectors and cables) for damage.
If the problem seems to be limited to 1 BBX, replace the BBX with a known good BBX.
7-22
SEP 2009
continued
No (or Missing) MCC24 Channel Elements

Follow the procedure in Table 7-29 for problems with channel elements.
Table 7-29: No MCC1X/MCC24E/MCC8E Channel Elements
Step
Action
Verify channel elements on a colocated MCC of the same type (CDF MccType codes: MCC8E = 0;
MCC24E = 2; MCC1X = 3)
Check MCC connectors (both module and backplane) for damage.
If the problem seems to be limited to one MCC, replace it with a known good MCC of the same type.
If no channel elements on any MCC, verify clock reference to CIO.
DC Power Problems
WARNING
Potentially lethal voltage and current levels are routed to
the BTS equipment. This test must be carried out with a
second person present, acting in a safety role. Remove all
rings, jewelry, and wrist watches prior to beginning this
test.
No DC Input Voltage to Power Supply Module

Follow the procedure in Table 7-30 for problems with DC input voltage.
Table 7-30: No DC Input Voltage to Power Supply Module
Step
1
Action
Verify DC power is applied to the BTS frame. Verify there are no breakers tripped.
* IMPORTANT
If a breaker has tripped, remove all modules from the applicable shelf supplied by the breaker and
attempt to reset it.
S If breaker trips again, there is probably a cable or breaker problem within the frame.
S If breaker does not trip, there is probably a defective module or subassembly within the shelf.
2
Verify that the CCCP shelf breaker on the BTS frame breaker panel is functional.
Use a voltmeter to determine if the input voltage is being routed to the CCCP backplane by
measuring the DC voltage level on the PWR_IN cable.
If the voltage is not present, there is probably a cable or breaker problem within the frame.
If the voltage is present at the connector, reconnect and measure the level at the VCC power
feed clip on the distribution backplane. If the voltage is correct at the power clip, inspect the clip
for damage.
SEP 2009
7-23
continued
Table 7-30: No DC Input Voltage to Power Supply Module

Step
Action
If everything appears to be correct, visually inspect the power supply module connectors.
Replace the power supply module with a known good module.
If steps 1 through 4 fail to indicate a problem, the CCCP backplane failure (possibly an open trace)
has occurred.
No DC Voltage (+5, +6.5, or +15 Volts) to a Specific GLI,

BBX2, or Switchboard
Table 7-31: No DC Input Voltage to any CCCP Shelf Module
Step
Action
Verify steps outlined in Table 7-30 have been performed.
Inspect the defective board/module (both board and backplane) connector for damage.
Replace suspect board/module with known good board/module.
No DC Input Voltage to any CCCP Shelf Module

Table 7-32: No DC Input Voltage to any CCCP Shelf Module
Step
Action
Inspect all Harting Cable connectors and backplane connectors for damage in all the affected board
slots.
Perform steps outlined in the RF path troubleshooting flowchart in this manual.
RFDS
The RFDS is used to perform PreCalibration Verification and

Post-Calibration Audits which limit-check the RFDS-generate and
reported receive levels of every path from the RFDS through the
directional coupler coupled paths. In the event of test failure, refer to the
following tables.
7-24
SEP 2009
continued
All tests fail
Follow the procedure in Table 7-33 for problems with RFDS.

Table 7-33: RFDS Fault Isolation All tests fail
Step
Action
Check the calibration equipment for proper operation by manually setting the signal generator output
attenuator to the lowest output power setting and connecting the output port to the spectrum analyzer
rf input port.
Set the signal generator output attenuator to 90 dBm, and switch on the rf output. Verify that the
spectrum analyzer can receive the signal, indicate the correct signal strength, (accounting for the cable
insertion loss), and the approximate frequency.
Visually inspect RF cabling. Make sure each directional coupler forward and reflected port connects to
the RFDS antenna select unit on the RFDS.
Check the wiring against the site documentation wiring diagram or the BTS Site Installation manual.
Verify RGLI and TSU have been downloaded.
Check to see that all RFDS boards show green on the front panel indicators. Visually check (both
board and backplane) for damage.
Replace any boards that do not show green with known good boards one at a time in the following
order. Retest after each is replaced.
RFDS ASU board.
RFDS Transceiver board.
All RX and TX paths fail
If every receive or transmit path fails, the problem most likely lies with
the rf converter board or the transceiver board. Refer to Table 7-34 for
fault isolation procedures.
Table 7-34: RFDS Fault Isolation All RX and TX paths fail
Step
Action
Visually check the master RF converter board (both board and backplane) for damage.
Replace the RF converter board with a known good RF converter board.
Visually check RXCVR TSU (both board and backplane) for damage.
Replace the TSU with a known good TSU.
SEP 2009
7-25
continued
All tests fail on a single

antenna
If all path failures are on one antenna port, forward and/or reflected,
follow the procedures in Table 7-35 checks.
Table 7-35: RFDS Fault Isolation All tests fail on single antenna path
Step
Action
Visually inspect the site interface cabinet internal cabling to the suspect directional coupler antenna
port.
Verify the forward and reflected ports connect to the correct RFDS antenna select unit positions on the
RFDS backplane. Refer to the installation manual for details.
Visually check ASU connectors (both board and backplane) for damage.
Replace the ASU with a known good ASU.
Replace the RF cables between the affected directional coupler and RFDS.
NOTE
Externally route the cable to bypass suspect segment.
7-26
SEP 2009
Troubleshooting: Span Control Link

Span Problems (No Control
Link)
Perform the procedure in Table 7-36 to troubleshoot a control link

failure.
Table 7-36: Troubleshoot Control Link Failure
Step
Action
Connect the CDMA LMF computer to the MMI port on the applicable GLI as shown in Figure 7-1 or
Figure 7-2.
Start an MMI communication session with the applicable GLI by using the Windows desktop shortcut
icon (see Table 3-3).
Once the connection window opens, press the LMF computer Enter key until the GLI prompt is
obtained.
Verify the span parameter settings for frame format, equalization, and linkspeed for the span to be used
by entering the following at the GLI3> prompt:
config ni current
(equivalent of span view command)
The system will respond with a display similar to the following:

The frame format in flash
Equalization:
Span A Default (0131
Span B Default (0131
Span C Default (0131
Span D Default (0131
Span E Default (0131
Span F Default (0131
is set to use T1_2.

feet
feet
feet
feet
feet
feet
for
for
for
for
for
for
T1/J1,
T1/J1,
T1/J1,
T1/J1,
T1/J1,
T1/J1,
120
120
120
120
120
120
Ohm
Ohm
Ohm
Ohm
Ohm
Ohm
for
for
for
for
for
for
E1)
E1)
E1)
E1)
E1)
E1)
Linkspeed: 64K
Currently, the link is running at the default rate
Loopback: OFF
NOTE
Defaults for span equalization are 0131 feet for T1/J1 spans and 120 Ohm for E1.
There is no need to change from defaults unless the span configuration provisioned in the OMCR
requires it.
Linkspeed is set automatically by the GLI3 for the span type selected.
5
The span configurations loaded in the GLI must match those in the OMCR database for the BTS. If
they do not, follow the procedure in Table 7-37.
SEP 2009
7-27
continued
Table 7-36: Troubleshoot Control Link Failure

Step
Action
Repeat steps 1 through 5 for all remaining GLIs.
If no other MMI actions are required with the GLI cards, terminate the GLI MMI session and
HyperTerminal connection by selecting File from the connection window menu bar, and then Exit
from the dropdown menu.
STATUS LED
RESET
PUSHBUTTON
GLI2
ALARM LED
SPANS LED
MASTER LED
TO MMI PORT
MMI PORT
CONNECTOR
ACTIVE LED
8PIN
NULL MODEM
BOARD
(TRN9666A)
7
8PIN TO 10PIN
RS232 CABLE
(P/N 3009786R01)
CDMA LMF
COMPUTER
RS232
CABLE
COM1 OR COM2
NOTE:
MMI connection can also be made using locally fabricated
MMI cable. See Appendix L.
7-28
DB9TODB25
ADAPTER
SEP 2009
continued
BPR A
BPR B
100BASET to
BTS Packet Router
or Expansion cage
AUX
100BASET
Auxiliary Monitor
Port
GLI
Dual 100BASET
in a single RJ45
to Redundant
(Mate) GLI3
Reset Switch
SPAN
Span (LED)
Alarm (LED)
MMI Port
MMI
To MMI port
ALARM
RESET
GLI3
ACT
STA
Active (LED)
Status (LED)
NULL MODEM
BOARD
(TRN9666A)
8PIN
7
8PIN TO 10PIN
RS232 CABLE
(P/N 3009786R01)
CDMA LMF
COMPUTER
RS232
CABLE
COM1 or COM2
NOTE:
MMI connection can also be made using locally fabricated
MMI cable. See Appendix L.
SEP 2009
DB9TODB25
ADAPTER
REF ti-CDMA-WP-00064-v01-ildoc-ftw
7-29
continued
Set BTS Site Span

Configuration
Perform the procedure in Table 7-37 to set the span parameter

configuration.
NOTE
IMPORTANT: Perform the following procedure ONLY if
span configurations loaded in the GLIs do not match those
in the OMCR data base, AND ONLY when the exact
configuration data is available. Loading incorrect span
configuration data will render the site inoperable.
Table 7-37: Set BTS Span Parameter Configuration

Step
Action
If not previously done, connect the CDMA LMF computer to the MMI port on the applicable GLI as
shown in Figure 7-1 or Figure 7-2.
If there is no MMI communication session in progress with the applicable GLI, initiate one by using
the Windows desktop shortcut icon.
At the GLI3> prompt, enter the following:

config ni format
COMMAND SYNTAX: config ni format option_gli3
LIST option_gli3: Span Option
E1_1 : E1_1 E1 HDB3 CRC4
no TS16
E1_2 : E1_2 E1 HDB3 no CRC4 no TS16
E1_3 : E1_3 E1 HDB3 CRC4
TS16
E1_4 : E1_4 E1 HDB3 no CRC4 TS16
T1_1 : T1_1 D4, AMI, No ZCS
T1_2 : T1_2 ESF, B8ZS
J1_1 : J1_1 ESF, B8ZS (Japan)
J1_2 : J1_2 ESF, B8ZS
T1_3 : T1_3 D4, AMI, ZCS
>
NOTE
1. With this command, all active (inuse) spans will be set to the same format.
2. E1_1 and E1_2 are PCM31 formats which provide 31 time slots for bearer traffic.
3. E1_3 and E1_4 are PCM30 formats which provide 30 time slots for bearer traffic. TS16 in these
formats is reserved and not used for payload transport.
7-30
SEP 2009
continued

Step
4
Action
> T1_2
NOTE
The entry is casesensitive and must be typed exactly as it appears in the list. If the entry is typed
incorrectly, a response similar to the following will be displayed:
CP: Invalid command
01.061980 00:1159 MGLI0002 INSACT BTSCDMA 16.1.68.00
GLI3>
An acknowledgement similar to the following will be displayed:

The value has been programmed. It will take effect after the next reset.
GLI3>
NOTE
In R18.0 and later software releases, span linkspeed is no longer set using a config ni command.
Linkspeed is determined and automatically set by the span type selected.
6
If the span equalization must be changed, enter the following MMI command:
config ni equal

COMMAND SYNTAX: config ni equal span_gli3 equal
LIST span_gli3 : Span
a : Span A
b : Span B
c : Span C
d : Span D
e : Span E
f : Span F
>
SEP 2009
7-31
continued

Step
7
Action
At the entry prompt (>), enter the designator from the list for the span to be changed as shown in the
following example:
> a

COMMAND SYNTAX: config ni equal a equal
LIST
equal : Span Equalization
default : Default (0131 feet for T1/J1, 120 ohm for E1)
T1_1 : T1 Short Haul mode. 0131 feet
E1_120 : E1 Short Haul mode. 120 OHM
T1_0DB : T1 Short Haul mode. LBO = 0 dB
T1_7_5DB : T1 Short Haul mode. LBO = 7.5 dB
T1_15DB : T1 Short Haul mode. LBO = 15.0 dB
>
! CAUTION
For fourdigit BTSs supported with Channel Service Units (CSU), do not select any of the following
additional settings:
S
T1_0DB T1 Long Haul mode. LBO = 0 dB
S T1_7_5DB T1 Long Haul mode. LBO = 7.5 dB
S 10T1_15DB T1 Long Haul mode. LBO = 15.0 dB
8
At the entry prompt (>), enter the code for the required equalization from the list as shown in the
following example (this should be the distance from the BTS Span I/O to the site demarcation
equipment or CSU, as applicable):
> T1_1

> T1_1
The value has been programmed. It will take effect after the next reset.
GLI3>
Repeat steps 6 through 8 for each inuse span.

7-32
SEP 2009
continued

Step
10
Action
NOTE
This step must be performed for GLI3 cards operating on a packet image to ensure the span parameter
changes will replace the previous settings.
For a GLI3 card in packet mode, enter the following:
rmfile /nvram00/config/hlp_param.txt
A response similar to the following will be displayed :

GLI3> rmfile /nvram00/config/hlp_param.txt
11.24.2003 23:14:57 MGLI0041 CC PRESENT BTSCDMA 16.40.00.09
GLI3>
11
* IMPORTANT
S After executing the config ni format and/or config ni equal commands, the affected GLI card
MUST be reset and reloaded for changes to take effect.
S Although defaults are shown in the software, always consult sitespecific documentation for span
type and equalization used at the site where the cards are to be installed.
Reset the card using the MMI reset command.

12
Once the card has completed resetting, execute the following command to verify span settings are as
required:
config ni current

The frame format in flash is set to use T1_2.
Equalization:
Span A T1 Short Haul mode. 0131 feet
Span B T1 Short Haul mode. 0131 feet
Span C Default (0131 feet for T1/J1, 120
Span D Default (0131 feet for T1/J1, 120
Span E Default (0131 feet for T1/J1, 120
Span F Default (0131 feet for T1/J1, 120
Ohm
Ohm
Ohm
Ohm
for
for
for
for
E1)
E1)
E1)
E1)
Linkspeed: 64K
Currently, the link is running at 64K
Loopback: OFF
SEP 2009
7-33
continued

Step
Action
13
If the span configuration is not correct, perform the applicable step from this table to change it and
repeat steps 10 through 12 to verify required changes have been programmed.
14
Return to step 6 of Table 7-36.
7-34
SEP 2009

satellite backhaul
satellite backhaul
At times, a GLI3 card which should have been converted to satellite
backhaul will continuously reboot and display MMI messages similar to
the following:
Reset due Backhaul
Reset due Backhaul
DHCP attempt timed
Reset due Backhaul
timeout
timeout
out
timeout
This condition can occur when the GLI3 card(s) backhaul type has not
actually changed to satellite with associated longer timeout
periods. In this situation, the BTS can appear INS_ACTIVE at the
OMCR but will be generating communication alarms such as Packet
Backhaul Down. The BTS and OMCR will be unable to communicate.
Because of this, a site visit is needed to correct this condition.
This procedure can also be used to preconfigure a GLI3 card for
satellite backhaul before commissioning or converting a BTS.
Prerequisites
The following are required to perform the corrective procedure:
S Laptop computer with at least one serial port or laptop computer
meeting the LMF computer platform requirements specified in the

BTS optimization/ATP manual
S One of the following:

Motorola cable part number CGDSMMICABLE219112 (see
Figure 3-9 for connection)
Fabricated DB9 receptacleto8 contact MMI connector cable
(see the MMI Cable Fabrication Section of Appendix L for
fabrication instructions and Figure 3-9 for connection)
SLN2006A MMI Interface Kit (see Figure 3-10) (this kit is no
longer available to order), consisting of the following:
Motorola Model TRN9666A null modem board
Motorola 3009786R01 MMI cable or equivalent
S (For use with SLN2006A only) Straightthrough RS232 cable,

DB9 to DB9, and DB9 to DB25 connector adapter (see
Figure 3-10)
S A terminal emulation application such as HyperTerminal or PuTTY

Performing the correction
Perform the following to convert the GLI3 card to satellite backhaul and
establish communication with the OMCR.
SEP 2009
7-35
Troubleshooting: GLI3 card continually reboots after converting to satellite

backhaul continued
Table 7-38: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals
Step
Action
Upon arrival at the site, contact the OMC R and notify the operator that site operations are starting.
Locate the INS_ACT GLI3 card.
NOTE
The INS_ACT card LEDs will show the following indications:
S STA: Slow flashing green

S ACT: green
3
Start an MMI communication session with the INS_ACT GLI3 card by following the instructions and
illustrations in the Establishing an MMI Communication Session section of Chapter 3.
In a BTS with redundant GLI3 cards, locate the INS_SBY card.
NOTE
The INS_SBY card LEDs will show the following indications:
S STA: Slow flashing green

S ACT: OFF
5
Disable the INS_SBY GLI3 card by unseating it from the backplane.

7-36
SEP 2009

backhaul continued
Step
6
Action
At the GLI3> prompt, reset the INS_ACT card by entering the following
command:
reset
The system will display a response similar to the following partial

example:
GLI3>
reset
++
| GLI3 BootROM Version
22.00.70.37 |
++
| Redundant BootROM from:0xC0800000
|
| TFFS location:0xC0980000
|
| Checking FLASH formatting
|
| TFFS device created
|
| Checking TFFS device
|
/nvram00/ Volume is OK
++
|
Reset Status Register : 0x00000002 |
|
Other Reset Data : 0x00800000 |
|
Reset Reason : Soft Reset Command |
| Exception Type :
NONE |
| Cage Control Status : STANDBY (0x00) |
| File Transfer Mode : FTP
|
++
| Network Interface Initialization
|
7
<<< remaining output omitted >>>
SEP 2009
7-37

backhaul continued
Step
7
Action
The GLI3 boot process must be stopped within 3 seconds after the Press any key to stop autoboot...
line appears (see bold output line in the following):
VxWorks System Boot
Copyright 19841998
CPU: EST Corp. est8260 MPC8260 PowerQUICC II SBC

Version: 5.4.2
BSP version: 1.2/0
Creation date: Oct 22 2008, 10:58:02
Press any key to stop autoboot...
NOTE
If any key is not pressed within 3 seconds after the line appears, the card must be allowed to complete
the boot process and then reset again to force it to reboot.
8
When the Press any key to stop autoboot... line appears, press the Enter
key.

Press any key to stop autoboot...
Copyright 19841998
3
2
VxWorks Boot]:
7
10
Change the backhaul type to satellite by entering the following at the [VxWorks Boot]: prompt:
bkhaul_type_set satellite

[VxWorks Boot]: bkhaul_type_set satellite
New backhaul type has been set successfully.
7-38
SEP 2009

backhaul continued
Step
11
Action
Verify that the backhaul type has been changed to satellite by entering
the following at the [VxWorks Boot]: prompt:
bkhaul_type_get

[VxWorks Boot]: bkhaul_type_get
The current backhaul type is SATELLITE.
12
Verify the current satellite backhaul Link Control Protocol (LCP) values by entering the following at
the [VxWorks Boot]: prompt:
sat_bkhaul_get

VxWorks Boot]: sat_bkhaul_get
Satellite Backhaul LCP NegRetry Interval is 1000 ms.
Satellite Backhaul LCP Keepalive Interval is 0 ms.
13
If the LCP parameter values are not set to 3000, set the satellite backhaul keepalive interval by
entering the following at the [VxWorks Boot]: prompt:
sat_bkhaul_set keepalive_int 3

[VxWorks Boot]: sat_bkhaul_set keepalive_int 3
Set keepalive_int successfully.
NOTE
This sets the timeout interval to 3000 ms as required for satellite backhaul.
14
Set the satellite backhaul negotiation retry interval by entering the following at the [VxWorks Boot]:
prompt:
sat_bkhaul_set neg_retry_int 3

[VxWorks Boot]: sat_bkhaul_set neg_retry_int 3
Set neg_retry_int successfully.
SEP 2009
7-39

backhaul continued
Step
15
Action
Verify that the LCP parameter values have been set correctly by entering the following at the
[VxWorks Boot]: prompt:
sat_bkhaul_get

VxWorks Boot]: sat_bkhaul_get
Satellite Backhaul LCP NegRetry Interval is 3000 ms.
Satellite Backhaul LCP Keepalive Interval is 3000 ms.
16
Force the card to reboot with the new settings by entering the following at the [VxWorks Boot]:
prompt:
@
The system will display a response similar to the following partial example:
[VxWorks Boot]: @
[VxWorks Boot]: @
unit number
processor number
file name
code/gli3_pkt1.elf
inet on ethernet (e)
host inet (h)
user (u)
ftp password (pw)
flags (f)
: 0
: 0
: /ram00/projects/cdmaazlabs/frame/RF7224_14/
:
:
:
:
:
128.0.0.2:ffffff80
192.168.1.8
anonymous
user
0x0
<<< remaining output omitted >>>
17
Allow the card to complete rebooting to the GLI3 > prompt and reach INS_ACT state (STA LED:
slow flashing green; ACT LED: green).
NOTE
This process can take as long as 17 minutes to complete. Do not attempt to reboot or unseat the GLI3
card unless the LED indications do not change to INS_ACT after the 17 minute period has passed.
18
When the GLI3 reaches INS_ACT, reseat the redundant GLI3 in its backplane slot (if the BTS is so
equipped).
19
Allow the redundant GLI3 to boot, be crossloaded by the INS_ACT card with the new settings, and
reach INS_SBY (STA LED: slow flashing green; ACT LED: OFF).
7-40
SEP 2009

backhaul continued
Step
20
Action
When the GLI3 card(s) are INS, contact the OMCR operator and:
S Advise the operator that the BTS is operational with the correct backhaul settings
S Request notification when communication between the OMCR and the
BTS is confirmed
21
When notified that the OMCR and BTS can communicate, advise the operator
that site operations are complete, and perform the procedures in the Prepare
to leave the site section in Chapter 6.
SEP 2009
7-41
Module Front Panel LED Indicators and Connectors

Module Status Indicators
Each of the non-passive plug-in modules has a bi-color (green & red)
LED status indicator located on the module front panel. The indicator is
labeled PWR/ALM. If both colors are turned on, the indicator is yellow.
Each plug-in module, except for the fan module, has its own alarm
(fault) detection circuitry that controls the state of the PWR/ALM LED.
The fan TACH signal of each fan module is monitored by the AMR.
Based on the status of this signal, the AMR controls the state of the
PWR/ALM LED on the fan module.
LED Status Combinations for
All Modules (except GLI, CSM,
BBX, MCC)
PWR/ALM LED
The following list describes the states of the module status indicator.
S Solid GREEN module operating in a normal (fault free) condition.

S Solid RED module is operating in a fault (alarm) condition due to
electrical hardware failure.
Note that a fault (alarm) indication may or may not be due to a complete
module failure and normal service may or may not be reduced or
interrupted.
DC/DC Converter LED Status
Combinations
The PWR CNVTR has alarm (fault) detection circuitry that controls the
state of the PWR/ALM LED. This is true for both the CCCP and PA
power converters.
PWR/ALM LED
The following list describes the states of the bi-color LED.
S Solid GREEN module operating in a normal (fault free) condition.

S Solid RED module is operating in a fault (alarm) condition due to
electrical hardware problem.
7-42
SEP 2009
continued
CSM Indicator and Connectors
Figure 7-3: CSM Front Panel Indicator and Monitor Connectors
SYNC
MONITOR
PWR/ALM
INDICATOR
FREQ
MONITOR
FW00303
PWR/ALM LED
The CSM includes on-board alarm detection. Hardware and
software/firmware state and alarm conditons are displayed by the front
panel LED indicator (Figure 7-3). For detailed descriptions of displayed
state/alarm indications refer to Figure 3-13 and Front Panel LED and
Status Displays in the CSM System Time GPS, LFR, and HSO/MSO
Verification section of Chapter 3.
FREQ Monitor Connector
A test port provided at the CSM front panel via a BNC receptacle allows
monitoring of the 19.6608 MHz clock generated by the CSM. When
both CSM 1 and CSM 2 are in an in-service (INS) condition, the CSM 2
clock signal frequency is the same as that output by CSM 1.
The clock is a sine wave signal with a minimum amplitude of +2 dBm
(800 mVpp) into a 50 load connected to this port.
SYNC Monitor Connector
A test port provided at the CSM front panel via a BNC receptacle allows
monitoring of the Even Second Tick reference signal generated by the
CSMs.
At this port, the reference signal is a TTL active high signal with a pulse
width of 153 nanoseconds.
SEP 2009
7-43
continued
MMI Connector
Only accessible behind front panel. The RS232 MMI port connector is
intended to be used primarily in the development or factory
environment, but may be used in the field for debug/maintenance
purposes.
GLI LED Status Combinations
NOTE
GLIs must be GLI3 to support packet operation.
GLI
The GLI module has indicators, controls and connectors as described
below and shown in Table 7-39 (GLI3).
The operating states of the LEDs are:
ACTIVE
Solid GREEN GLI is active. This means that the GLI has shelf
control and is providing control of the digital interfaces.
Off GLI is not active (i.e., Standby). The mate GLI should be active.
7-44
SEP 2009
continued
ALARM
S Solid RED GLI is in a fault condition or in reset.

S While in reset transition, STATUS LED is OFF while GLI is
performing ROM boot (about 12 seconds for normal boot).
S While in reset transition, STATUS LED is ON while GLI is

performing RAM boot (about 4 seconds for normal boot).
S Off No Alarm.
STATUS
S Flashing GREEN GLI is in service (INS), in a stable operating

condition.
S On GLI is in OOS RAM state operating downloaded code.

S Off GLI is in OOS ROM state operating boot code.
SPANS
S Solid GREEN Span line is connected and operating.

S Solid RED Span line is disconnected or a fault condition exists.
GLI Pushbuttons and
Connectors
RESET Pushbutton Depressing the RESET pushbutton causes a

partial reset of the CPU and a reset of all board devices. The GLI is
placed in the OOS_ROM state
MMI Connector The RS232MMI port connector is intended to be
used primarily in the development or factory environment but may be
used in the field for debug/maintenance purposes.
10/100BaseT Ethernet Connectors Four 8contact modular
receptacles are located on the front panel of a GLI3 card. The BPR A
and BPR B connectors provide interfaces with for external BTS routers
for packet traffic transport. The GLI connector provides two Ethernet
connections in the same connector. The two connections provide a
passthrough for each BTS internal 10/100BaseT subnet to support
packet transport redundancy. The AUX connector provides an Ethernet
interface for external devices which may be used with the BTS in the
future.
Table 7-39 shows the front panel of the GLI3 card and includes a
description of the components.
SEP 2009
7-45
continued
Table 7-39: GLI3 Front Panel

LED
Operating Status
GLI
Supports the crosscoupled ethernet circuits to the mate GLI using

a double crossover cable.
RESET
Pressing and releasing the switch resets all functions on the GLI3.
ALARM
OFF operating normally

ON briefly during power-up when the Alarm LED turns OFF
SLOW GREEN when the GLI3 is INS (in-service)
SPAN
OFF card is powered down, in initialization, or in standby

GREEN operating normally
YELLOW one or more of the equipped initialized spans is
receiving a remote alarm indication signal from the far end
RED one or more of the equipped initialized spans is in an alarm
state
ACTIVE
7-46
Dual 100BASET in a single

RJ45 to Redundant (Mate)
GLI3
Reset Switch
Span (LED)
Alarm (LED)
Ala
MMI Port
ACT

ON briefly during power-up when the Alarm LED turns OFF
SLOW GREEN when the GLI3 is INS (in-service)
RAPID ORANGE (0.5 second intervals) Software upgrade in
progress (for a firsttime upgrade to R18.0 or later release, can
require up to 17 minutes)
VERY RAPID ORANGE (0.1 second intervals) FTP in progress
while card is operating on bootROM code. (No FTP indications in
normal operation.)
STA
STATUS
An RS-232, serial, asynchronous communications link for use as an

MMI port. This port supports 300 baud, up to a maximum of
115,200 baud communications.
100BASET Auxiliary
Monitor Port
MMI
MMI
100BASE T to BTS Packet

100BASET
Router or Expansion cage
SPAN
Wired as an ethernet client for direct connection to a personal

computer with a standard ethernet cable. It allows connection of
ethernet sniffer when the ethernet switch is properly configured
for port monitoring.
ALARM
M
RESET
AUX
GLI
Connects to either a BPR or expansion cage and is wired as an

ethernet client.
AUX
BPR B
BPR
RB
Connects to either a BPR or expansion cage and is wired as an

ethernet client.
BPR A
BPR A
Diagram
Active (LED)
Status (LED)
Shows the operating status of the redundant cards. The redundant

card toggles automatically if the active card is removed or fails
ON active card operating normally
OFF standby card operating normally
SEP 2009
continued
BBX LED Status Combinations
PWR/ALM LED
The BBX module has its own alarm (fault) detection circuitry that
controls the state of the PWR/ALM LED.
The following list describes the states of the bi-color LED:
S
S
S
S
S
S
S
Solid GREEN INS_ACT no alarm

Solid RED Red initializing or power-up alarm
Slowly Flashing GREEN OOS_ROM no alarm
Long RED/Short GREEN OOS_ROM alarm
Rapidly Flashing GREEN OOS_RAM no alarm
Short RED/Short GREEN OOS_RAM alarm
Long GREEN/Short RED INS_ACT alarm
PA Shelf LED Status

Combinations
PA Module LED
Each PA module contains a bicolor LED just above the MMI connector
on the front panel of the module. Interpret this LED as follows:
S GREEN PA module is active and is reporting no alarms (Normal

condition).
S Flashing GREEN/RED PA module is active but is reporting an low

input power condition. If no BBX is keyed, this is normal and does
not constitute a failure.
MCC LED Status Combinations
The MCC module has LED indicators and connectors as described

below (see Figure 7-4). Note that the figure does not show the
connectors as they are concealed by the removable lens.
The LED indicators and their states are as follows:

PWR/ALM LED
S RED fault on module

ACTIVE LED
S
S
S
S
Off module is inactive, off-line, or not processing traffic.

Slowly Flashing GREEN OOS_ROM no alarm.
Rapidly Flashing Green OOS_RAM no alarm.
Solid GREEN module is INS_ACT, on-line, processing traffic.
PWR/ALM and ACTIVE LEDs
S Solid RED module is powered but is in reset or the BCP is inactive.

SEP 2009
7-47
continued
MMI Connectors
S The RS232 MMI port connector (four-pin) is intended to be used
primarily in the development or factory environment but may be used

in the field for debugging purposes.
S The RJ11 ethernet port connector (eight-pin) is intended to be used
primarily in the development environment but may be used in the field

for high data rate debugging purposes.
Figure 7-4: MCC Front Panel
LED
PWR/ALM
PWR/ALM
PWR/ALM LED
ACTIVE
LENS
(REMOVABLE)
OPERATING STATUS

ON briefly during power-up and during failure
conditions
An alarm is generated in the event of a failure
RED
GREEN
RED
RAPIDLY BLINKING Card is code-loaded but not

enabled
SLOW BLINKING Card is not code-loaded
ON card is code-loaded and enabled (INS_ACTIVE)
ON fault condition
SLOW FLASHING (alternating with green) CHI
bus inactive on power-up
ACTIVE
ACTIVE LED
COLOR
7-48
SEP 2009
Appendix A: System Data

Appendix Content
Site Operation Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verification of Test Equipment Used . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preliminary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PrePower and Initial Power Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Optimization Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPS Receiver Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LFR Receiver Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Amplifier IM Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX Bay Level Offset / Power Output Verification for
3Sector Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX Bay Level Offset / Power Output Verification for
6Sector Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCCP Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Amplifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEP 2009
A-1
A-1
A-2
A-3
A-4
A-5
A-6
A-7
A-8
A-9
A-14
A-16
A-16
A-17
A-18
A-19
Table of Contents
continued
Notes
SEP 2009
Site Operation Verification

Verification of Test Equipment
Used
Table A-1: Verification of Test Equipment Used

Manufacturer
Model
Serial Number
Comments:________________________________________________________
SEP 2009
A-1
continued
__________________________________________________________________
Site Checklist
Table A-2: Site Checklist

OK
Parameter
Specification
Deliveries
Per established procedures
Floor Plan
Verified
Inter Frame Cables:

Ethernet
Frame Ground
Power
Per procedure
Per procedure
Per procedure
Factory Data:
BBX
Test Panel
RFDS
Per procedure
Per procedure
Per procedure
Site Temperature
Dress Covers/Brackets
A-2
Comments
SEP 2009
continued
Preliminary Operations
Table A-3: Preliminary Operations

OK
Parameter
Specification
Shelf ID Dip Switches
Per site equipage
Ethernet LAN verification
Verified per procedure
Comments
Comments:_________________________________________________________
SEP 2009
A-3
continued
PrePower and Initial Power

Tests
Table A3a: Prepower Checklist

OK
Parameter
Specification
Prepowerup tests
Verify power supply

output voltage at the top
of each BTS frame is
within specifications
Internal Cables:
ISB (all cages)
CSM (all cages)
Power (all cages)
Ethernet Connectors
LAN A ohms
LAN B ohms
LAN A shield
LAN B shield
Ethernet Boots
Air Impedance Cage (single cage)
installed
Initial powerup tests
Verify power supply

output voltage at the top
of each BTS frame is
within specifications:
Comments
verified
verified
verified
verified
verified
isolated
isolated
installed
Comments:_________________________________________________________
A-4
SEP 2009
continued
General Optimization Checklist
Table A3b: Prepower Checklist

OK
Parameter
Specification
LEDs
Frame fans
illuminated
operational
LMF to BTS Connection

Preparing the LMF
Log into the LMF PC
Create site specific BTS directory
Download device loads
per procedure
per procedure
per procedure
per procedure
Ping LAN A
Ping LAN B
per procedure
per procedure
Download/Enable MGLI3s
Download/Enable GLI3s
Set Site Span Configuration
Download CSMs
Enable CSMs
Enable CSMs
Download/Enable MCCs*
Download BBXs*
Download TSU (in RFDS)
Program TSU NAM
per procedure
per procedure
per procedure
per procedure
per procedure
per procedure
per procedure
per procedure
per procedure
per procedure
Comments
*MCCs may be MCC8Es, MCC24s or MCC1Xs. BBXs may be BBXs or BBX1Xs

Comments:_________________________________________________________
SEP 2009
A-5
continued
GPS Receiver Operation
Table A-4: GPS Receiver Operation

OK
Parameter
Specification
GPS Receiver Control Task State:

tracking satellites
Verify parameter
Initial Position Accuracy:
Verify Estimated
or Surveyed
Current Position:
lat
lon
height
RECORD in
msec and cm also
convert to deg
min sec
Current Position: satellites tracked

Estimated:
(>4) satellites tracked,(>4) satellites visible
Surveyed:
(>1) satellite tracked,(>4) satellites visible
Verify parameter
as appropriate:
Current reference source:

Number: 0; Status: Good; Valid: Yes
Verify parameter
Comments
Comments:_________________________________________________________
A-6
SEP 2009
continued
LFR Receiver Operation
Table A-5: LFR Receiver Operation

OK
Parameter
Specification
Station call letters M X Y Z

assignment.
SN ratio is > 8 dB
LFR Task State: 1fr

locked to station xxxx
Verify parameter
Current reference source:

Number: 1; Status: Good; Valid: Yes
Verify parameter
Comments
as specified in site
documentation
Comments:_________________________________________________________
SEP 2009
A-7
continued
Power Amplifier IM Reduction
Table A-6: Power Amplifier IM Reduction

Parameter
OK
PA
#
Comments
CARRIER
Specification
4:1 & 2:1

3Sector
2:1
6Sector
Dual BP
3Sector
Dual BP
6Sector
1A
C1
C1
C1
C1
No Alarms
1B
C1
C1
C1
C1
No Alarms
1C
C1
C1
C1
C1
No Alarms
1D
C1
C1
C1
C1
No Alarms
2A
C2
C2
C2
No Alarms
2B
C2
C2
C2
No Alarms
2C
C2
C2
C2
No Alarms
2D
C2
C2
C2
No Alarms
3A
C3
C1
C1
No Alarms
3B
C3
C1
C1
No Alarms
3C
C3
C1
C1
No Alarms
3D
C3
C1
C1
No Alarms
4A
C4
C2
No Alarms
4B
C4
C2
No Alarms
4C
C4
C2
No Alarms
4D
C4
C2
No Alarms
Comments:_________________________________________________________
A-8
SEP 2009
continued
TX Bay Level Offset / Power

Output Verification for
3Sector Configurations
1Carrier
2Carrier Nonadjacent Channels
Table A-7: TX BLO Calibration (3Sector: 1Carrier, 2and 4Carrier Nonadjacent Channels)
OK
Parameter
Specification
Comments
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
BBX7, ANT1 =
BBXr, ANT1 =
dB
dB
BBX8, ANT2 =
BBXr, ANT2 =
dB
dB
BBX9, ANT3 =
BBXr, ANT3 =
dB
dB
BBX4, ANT1 =
BBXr, ANT1 =
dB
dB
BBX5, ANT2 =
BBXr, ANT2 =
dB
dB
BBX6, ANT3 =
BBXr, ANT3 =
dB
dB
BBX10, ANT1 =
BBXr, ANT1 =
dB
dB
BBX11, ANT2 =
BBXr, ANT2 =
dB
dB
BBX12, ANT3 =
BBXr, ANT3 =
dB
dB
Calibrate
carrier 1
Calibrate
carrier 2
Calibrate
carrier 3
Calibrate
carrier 4
TX Bay Level Offset = 37 dB (+4 dB)

prior to calibration



SEP 2009
A-9
continued
Table A-7: TX BLO Calibration (3Sector: 1Carrier, 2and 4Carrier Nonadjacent Channels)
OK
Parameter
Specification
Comments
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
BBX7, ANT1 =
BBXr, ANT1 =
dB
dB
BBX8, ANT2 =
BBXr, ANT2 =
dB
dB
BBX9, ANT3 =
BBXr, ANT3 =
dB
dB
BBX4, ANT1 =
BBXr, ANT1 =
dB
dB
BBX5, ANT2 =
BBXr, ANT2 =
dB
dB
BBX6, ANT3 =
BBXr, ANT3 =
dB
dB
BBX10, ANT1 =
BBXr, ANT1 =
dB
dB
BBX11, ANT2 =
BBXr, ANT2 =
dB
dB
BBX12, ANT3 =
BBXr, ANT3 =
dB
dB
Calibration
Audit
carrier 1
Calibration
Audit
carrier 2
Calibration
Audit
carrier 3
Calibration
Audit
carrier 4
0 dB (+0.5 dB) for gain set resolution

post calibration

post calibration

post calibration

post calibration
Comments:________________________________________________________
__________________________________________________________________
A-10
SEP 2009
continued
2Carrier Adjacent Channel

Table A-8: TX Bay Level Offset Calibration (3Sector: 2Carrier Adjacent Channels)
OK
Parameter
Specification
Comments
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
BBX7, ANT4 =
BBXr, ANT4 =
dB
dB
BBX8, ANT5 =
BBXr, ANT5 =
dB
dB
BBX9, ANT6 =
BBXr, ANT6 =
dB
dB
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
BBX7, ANT4 =
BBXr, ANT4 =
dB
dB
BBX8, ANT5 =
BBXr, ANT5 =
dB
dB
BBX9, ANT6 =
BBXr, ANT6 =
dB
dB
Calibrate
carrier 1
Calibrate
carrier 2
Calibration
Audit
carrier 1
Calibration
Audit
carrier 2
TX Bay Level Offset = 42 dB (typical),

38 dB (minimum) prior to calibration
TX Bay Level Offset = 42 dB (typical),


post calibration

post calibration
Comments:________________________________________________________
__________________________________________________________________
SEP 2009
A-11
continued
3Carrier Adjacent Channels

4Carrier Adjacent Channels
Table A-9: TX Bay Level Offset Calibration (3Sector: 3 or 4Carrier Adjacent Channels)
OK
Parameter
Specification
Comments
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
BBX7, ANT1 =
BBXr, ANT1 =
dB
dB
BBX8, ANT2 =
BBXr, ANT2 =
dB
dB
BBX9, ANT3 =
BBXr, ANT3 =
dB
dB
BBX4, ANT4 =
BBXr, ANT4 =
dB
dB
BBX5, ANT5 =
BBXr, ANT5 =
dB
dB
BBX6, ANT6 =
BBXr, ANT6 =
dB
dB
BBX10, ANT4 =
BBX3, ANT4 =
dB
dB
BBX11, ANT5 =
BBXr, ANT5 =
dB
dB
BBX12, ANT6 =
BBXr, ANT6 =
dB
dB
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
Calibrate
carrier 1
Calibrate
carrier 2
Calibrate
carrier 3
Calibrate
carrier 4
Calibration
Audit
carrier 1
TX Bay Level Offset = 37 dB before

calibration
TX Bay Level Offset =37 dB before

calibration

calibration

calibration

post calibration

A-12
SEP 2009
continued
Table A-9: TX Bay Level Offset Calibration (3Sector: 3 or 4Carrier Adjacent Channels)
OK
Parameter
Specification
Comments
BBX7, ANT1 =
BBXr, ANT1 =
dB
dB
BBX8, ANT2 =
BBXr, ANT2 =
dB
dB
BBX9, ANT3 =
BBXr, ANT3 =
dB
dB
BBX4, ANT4 =
BBXr, ANT4 =
dB
dB
BBX5, ANT5 =
BBXr, ANT5 =
dB
dB
BBX6, ANT6 =
BBXr, ANT6 =
dB
dB
BBX10, ANT4 =
BBXr, ANT4 =
dB
dB
BBX11, ANT5 =
BBXr, ANT5 =
dB
dB
BBX12, ANT6 =
BBXr, ANT6 =
dB
dB
Calibration
Audit
carrier 2
Calibration
Audit
carrier 3
Calibration
Audit
carrier 4

post calibration

post calibration

post calibration
Comments:________________________________________________________
__________________________________________________________________
SEP 2009
A-13
continued
TX Bay Level Offset / Power

Output Verification for
6Sector Configurations
1Carrier
Table A-10: TX BLO Calibration (6Sector: 1Carrier, 2Carrier Nonadjacent Channels)
OK
Parameter
Specification
Comments
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
BBX4, ANT4 =
BBXr, ANT4 =
dB
dB
BBX5, ANT5 =
BBXr, ANT5 =
dB
dB
BBX6, ANT6 =
BBXr, ANT6 =
dB
dB
BBX7, ANT1 =
BBXr, ANT1 =
dB
dB
BBX8, ANT2 =
BBXr, ANT2 =
dB
dB
BBX9, ANT3 =
BBXr, ANT3 =
dB
dB
BBX10, ANT4 =
BBX3, ANT4 =
dB
dB
BBX11, ANT5 =
BBXr, ANT5 =
dB
dB
BBX12, ANT6 =
BBXr, ANT5 =
dB
dB
Calibrate
carrier 1
Calibrate
carrier 2
TX Bay
y Level Offset = 42 dB ((typical),
yp ),
TX Bay
y Level Offset = 42 dB ((typical),
yp ),
A-14
SEP 2009
continued
Table A-10: TX BLO Calibration (6Sector: 1Carrier, 2Carrier Nonadjacent Channels)

OK
Parameter
Specification
Comments
BBX1, ANT1 =
BBXr, ANT1 =
dB
dB
BBX2, ANT2 =
BBXr, ANT2 =
dB
dB
BBX3, ANT3 =
BBXr, ANT3 =
dB
dB
BBX4, ANT4 =
BBXr, ANT4 =
dB
dB
BBX5, ANT5 =
BBXr, ANT5 =
dB
dB
BBX6, ANT6 =
BBXr, ANT6 =
dB
dB
BBX7, ANT1 =
BBXr, ANT1 =
dB
dB
BBX8, ANT2 =
BBXr, ANT2 =
dB
dB
BBX9, ANT3 =
BBXr, ANT3 =
dB
dB
BBX10, ANT4 =
BBXr, ANT4 =
dB
dB
BBX11, ANT5 =
BBXr, ANT5 =
dB
dB
BBX12, ANT6 =
BBXr, ANT6 =
dB
dB
Calibration
Audit
carrier 1
Calibration
Audit
carrier 2
0 dB (+0.5
(
dB)) for gain
g set resolution
post calibration
0 dB (+0.5
(
dB)) for gain
g set resolution
post calibration
Comments:________________________________________________________
__________________________________________________________________
SEP 2009
A-15
continued
TX Antenna VSWR
Table A-11: TX Antenna VSWR

OK
Parameter
Specification
VSWR
Antenna 1
< (1.5 : 1)
VSWR
Antenna 2
< (1.5 : 1)
VSWR
Antenna 3
< (1.5 : 1)
VSWR
Antenna 4
< (1.5 : 1)
VSWR
Antenna 5
< (1.5 : 1)
VSWR
Antenna 6
< (1.5 : 1)
Data
Comments:________________________________________________________
__________________________________________________________________
RX Antenna VSWR
Table A-12: RX Antenna VSWR

OK
Parameter
Specification
VSWR
Antenna 1
< (1.5 : 1)
VSWR
Antenna 2
< (1.5 : 1)
VSWR
Antenna 3
< (1.5 : 1)
VSWR
Antenna 4
< (1.5 : 1)
VSWR
Antenna 5
< (1.5 : 1)
VSWR
Antenna 6
< (1.5 : 1)
Data
Comments:_________________________________________________________
A-16
SEP 2009
continued
Alarm Verification
Table A-13: CDI Alarm Input Verification

OK
Parameter
Verify CDI alarm input
operation per Table 3-4.
Specification
Data
BTS Relay #XX

Contact Alarm
Sets/Clears
Comments:_________________________________________________________
SEP 2009
A-17
continued
CCCP Shelf
Site I/O A & B

CCCP Shelf
CSM1
CSM2
HSO/MSO/HSOX
CCD1
CCD2
AMR1
AMR2
MPC1
MPC2
Fans 13
GLI31
GLI32
BBX1
BBX2
BBX3
BBX4
BBX5
BBX6
BBX7
BBX8
BBX9
BBX10
BBX11
BBX12
BBXr
MCC1
MCC2
MCC3
MCC4
MCC5
MCC6
MCC7
MCC8
MCC9
MCC10
MCC11
MCC12
CIO
SWITCH
PS1
PS2
PS3
A-18
SEP 2009
continued
Power Amplifiers
PA 1A
PA 1B
PA 1C
PA 1D
PA 2A
PA 2B
PA 2C
PA 2D
PA 3A
PA 3B
PA 3C
PA 3D
PA 4A
PA 4B
PA 4C
PA 4D
SEP 2009
A-19
continued
Notes
A-20
SEP 2009
Appendix B: PN Offset
Appendix Content
PN Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEP 2009
B-1
B-1
B-1
Table of Contents
continued
Notes
SEP 2009
PN Offset
PN Offset
Background
B
All channel elements transmitted from a BTS in a particular 1.25 MHz
CDMA channel are orthonogonally spread by 1 of 64 possible Walsh
code functions; additionally, they are also spread by a quadrature pair of
PN sequences unique to each sector.
Overall, the mobile uses this to differentiate multiple signals transmitted
from the same BTS (and surrounding BTS) sectors, and to synchronize
to the next strongest sector.
The PN offset per sector is stored on the BBXs, where the
corresponding I & Q registers reside.
The PN offset values are determined on a per BTS/per sector(antenna)
basis as determined by the appropriate cdf file content. A breakdown of
this information is found in Table B-1.
Usage
There are three basic RF chip delays currently in use. It is important to

determine what RF chip delay is valid to be able to test the BTS
functionality. This can be done by ascertaining if the CDF file
FineTxAdj value was set to on when the MCC was downloaded with
image data. The FineTxAdj value is used to compensate for the
processing delay (approximately 20 mS) in the BTS using any type of
mobile meeting IS97 specifications.
Observe the following guidelines:
S If the FineTxAdj value in the cdf file is 101 (65 HEX), the
FineTxAdj has not been set. The I and Q values from the 0 table
MUST be used.
If the FineTxAdj value in the cdf file is 213 (D5 HEX), FineTxAdj has
been set for the 14 chip table.
S If the FineTxAdj value in the cdf file is 197 (C5 HEX), FineTxAdj
has been set for the 13 chip table.
NOTE
CDF file I and Q values can be represented in DECIMAL
or HEX. If using HEX, add 0x before the HEX value. If
necessary, convert HEX values in Table B-1 to decimal
before comparing them to cdf file I & Q value
assignments.
SEP 2009
B-1
PN Offset
continued
If you are using a Qualcomm mobile, use the I and Q values from
the 13 chip delay table.
If you are using a mobile that does not have the 1 chip offset
problem, (any mobile meeting the IS97 specification), use the 14
chip delay table.
NOTE
If the wrong I and Q values are used with the wrong
FineTxAdj parameter, system timing problems will occur.
This will cause the energy transmitted to be smeared
over several Walsh codes (instead of the single Walsh code
that it was assigned to), causing erratic operation. Evidence
of smearing is usually identified by Walsh channels not at
correct levels or present when not selected in the Code
Domain Power Test.
B-2
SEP 2009
PN Offset
continued
Table B-1: PnMaskI and PnMaskQ Values for PilotPn

Pilot
PN
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
17523
32292
4700
14406
14899
17025
14745
2783
5832
12407
31295
7581
18523
29920
25184
26282
30623
15540
23026
20019
4050
1557
30262
18000
20056
12143
17437
17438
5102
9302
17154
5198
4606
24804
17180
10507
10157
23850
31425
4075
10030
16984
14225
26519
27775
30100
7922
14199
17637
23081
5099
23459
32589
17398
26333
4011
2256
18651
1094
21202
13841
31767
18890
30999
22420
20168
12354
11187
11834
10395
28035
27399
22087
2077
13758
11778
3543
7184
2362
25840
12177
10402
1917
17708
10630
6812
14350
10999
25003
2652
19898
2010
25936
28531
11952
31947
25589
11345
28198
13947
8462
9595
4473
7E24
125C
3846
3A33
4281
3999
0ADF
16C8
3077
7A3F
1D9D
485B
74E0
6260
66AA
779F
3CB4
59F2
4E33
0FD2
0615
7636
4650
4E58
2F6F
441D
441E
13EE
2456
4302
144E
11FE
60E4
431C
290B
27AD
5D2A
7AC1
0FEB
272E
4258
3791
6797
6C7F
7594
1EF2
3777
44E5
5A29
13EB
5BA3
7F4D
43F6
66DD
0FAB
08D0
48DB
0446
52D2
3611
7C17
49CA
7917
5794
4EC8
3042
2BB3
2E3A
289B
6D83
6B07
5647
081D
35BE
2E02
0DD7
1C10
093A
64F0
2F91
28A2
077D
452C
2986
1A9C
380E
2AF7
61AB
0A5C
4DBA
07DA
6550
6F73
2EB0
7CCB
63F5
2C51
6E26
367B
210E
257B
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
29673
16146
2350
7203
19657
28816
19740
21695
2916
18923
27855
24350
30205
14960
12592
13141
27167
7770
11513
30409
2025
21210
15131
9000
10028
18023
29662
8719
2551
4651
8577
2599
2303
12402
8590
17749
16902
11925
27824
22053
5015
8492
18968
25115
26607
15050
3961
19051
29602
31940
22565
25581
29082
8699
32082
18921
1128
27217
547
10601
21812
28727
9445
29367
11210
10084
6177
23525
5917
23153
30973
31679
25887
18994
6879
5889
18647
3592
1181
12920
23028
5201
19842
8854
5315
3406
7175
23367
32489
1326
9949
1005
12968
31109
5976
28761
32710
22548
14099
21761
4231
23681
73E9
3F12
092E
1C23
4CC9
7090
4D1C
54BF
0B64
49EB
6CCF
5F1E
75FD
3A70
3130
3355
6A1F
1E5A
2CF9
76C9
07E9
52DA
3B1B
2328
272C
4667
73DE
220F
09F7
122B
2181
0A27
08FF
3072
218E
4555
4206
2E95
6CB0
5625
1397
212C
4A18
621B
67EF
3ACA
0F79
4A6B
73A2
7CC4
5825
63ED
719A
21FB
7D52
49E9
0468
6A51
0223
2969
5534
7037
24E5
72B7
2BCA
2764
1821
5BE5
171D
5A71
78FD
7BBF
651F
4A32
1ADF
1701
48D7
0E08
049D
3278
59F4
1451
4D82
2296
14C3
0D4E
1C07
5B47
7EE9
052E
26DD
03ED
32A8
7985
1758
7059
7FC6
5814
3713
5501
1087
5C81
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
4096
9167
22417
966
14189
29150
18245
1716
11915
20981
24694
11865
6385
27896
25240
30877
30618
26373
314
17518
21927
2245
18105
8792
21440
15493
26677
11299
12081
23833
20281
10676
16981
31964
26913
14080
23842
27197
22933
30220
12443
19854
14842
15006
702
21373
23874
3468
31323
29266
16554
4096
1571
7484
6319
2447
24441
27351
23613
29008
5643
28085
18200
21138
21937
25222
109
6028
22034
15069
4671
30434
11615
19838
14713
241
24083
7621
19144
1047
26152
22402
21255
30179
7408
115
1591
1006
32263
1332
12636
4099
386
29231
25711
10913
8132
20844
13150
18184
19066
29963
1000
23CF
5791
03C6
376D
71DE
4745
06B4
2E8B
51F5
6076
2E59
18F1
6CF8
6298
789D
779A
6705
013A
446E
55A7
08C5
46B9
2258
53C0
3C85
6835
2C23
2F31
5D19
4F39
29B4
4255
7CDC
6921
3700
5D22
6A3D
5995
760C
309B
4D8E
39FA
3A9E
02BE
537D
5D42
0D8C
7A5B
7252
40AA
1000
0623
1D3C
18AF
098F
5F79
6AD7
5C3D
7150
160B
6DB5
4718
5292
55B1
6286
006D
178C
5612
3ADD
123F
76E2
2D5F
4D7E
3979
00F1
5E13
1DC5
4AC8
0417
6628
5782
5307
75E3
1CF0
0073
0637
03EE
7E07
0534
315C
1003
0182
722F
646F
2AA1
1FC4
516C
335E
4708
4A7A
750B
SEP 2009
B-3
PN Offset
continued
Pilot
PN
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
32743
7114
7699
19339
28212
29587
19715
14901
20160
22249
26582
7153
15127
15274
23149
16340
27052
13519
10620
15978
27966
12479
1536
3199
4549
17888
13117
7506
27626
31109
29755
26711
20397
18608
7391
23168
23466
15932
25798
28134
28024
6335
21508
26338
17186
22462
3908
25390
27891
9620
4670
14672
29415
20610
6479
10957
18426
22726
5247
29953
5796
16829
4528
5415
10294
17046
7846
10762
13814
16854
795
9774
24291
3172
2229
21283
16905
7062
7532
25575
14244
28053
30408
5094
16222
7159
174
25530
2320
23113
23985
2604
1826
30853
15699
2589
25000
18163
12555
8670
7FE7
1BCA
1E13
4B8B
6E34
7393
4D03
3A35
4EC0
56E9
67D6
1BF1
3B17
3BAA
5A6D
3FD4
69AC
34CF
297C
3E6A
6D3E
30BF
0600
0C7F
11C5
45E0
333D
1D52
6BEA
7985
743B
6857
4FAD
48B0
1CDF
5A80
5BAA
3E3C
64C6
6DE6
6D78
18BF
5404
66E2
4322
57BE
0F44
632E
6CF3
2594
123E
3950
72E7
5082
194F
2ACD
47FA
58C6
147F
7501
16A4
41BD
11B0
1527
2836
4296
1EA6
2A0A
35F6
41D6
031B
262E
5EE3
0C64
08B5
5323
4209
1B96
1D6C
63E7
37A4
6D95
76C8
13E6
3F5E
1BF7
00AE
63BA
0910
5A49
5DB1
0A2C
0722
7885
3D53
0A1D
61A8
46F3
310B
21DE
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
28195
3557
24281
29717
14106
26649
30545
19658
10080
31396
13291
23592
19547
7637
31974
8170
13526
19383
5310
7989
13983
18831
768
22511
22834
8944
18510
3753
13813
27922
27597
26107
30214
9304
24511
11584
11733
7966
12899
14067
14012
23951
10754
13169
8593
11231
1954
12695
26537
4810
2335
7336
30543
10305
17051
23386
9213
11363
17411
29884
2898
28386
2264
17583
5147
8523
3923
5381
6907
8427
20401
4887
24909
1586
19046
26541
28472
3531
3766
32719
7122
30966
15204
2547
8111
17351
87
12765
1160
25368
24804
1302
913
29310
20629
19250
12500
27973
22201
4335
6E23
0DE5
5ED9
7415
371A
6819
7751
4CCA
2760
7AA4
33EB
5C28
4C5B
1DD5
7CE6
1FEA
34D6
4BB7
14BE
1F35
369F
498F
0300
57EF
5932
22F0
484E
0EA9
35F5
6D12
6BCD
65FB
7606
2458
5FBF
2D40
2DD5
1F1E
3263
36F3
36BC
5D8F
2A02
3371
2191
2BDF
07A2
3197
67A9
12CA
091F
1CA8
774F
2841
429B
5B5A
23FD
2C63
4403
74BC
0B52
6EE2
08D8
44AF
141B
214B
0F53
1505
1AFB
20EB
4FB1
1317
614D
0632
4A66
67AD
6F38
0DCB
0EB6
7FCF
1BD2
78F6
3B64
09F3
1FAF
43C7
0057
31DD
0488
6318
60E4
0516
0391
727E
5095
4B32
30D4
6D45
56B9
10EF
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
22575
31456
8148
19043
25438
10938
2311
7392
30714
180
8948
16432
9622
7524
1443
1810
6941
3238
8141
10408
18826
22705
3879
21359
30853
18078
15910
20989
28810
30759
18899
7739
6279
9968
8571
4143
19637
11867
7374
10423
9984
7445
4133
22646
15466
2164
16380
15008
31755
31636
6605
29417
22993
27657
5468
8821
20773
4920
5756
28088
740
23397
19492
26451
30666
15088
26131
15969
24101
12762
19997
22971
12560
31213
18780
16353
12055
30396
24388
1555
13316
31073
6187
21644
9289
4624
467
18133
1532
1457
9197
13451
25785
4087
31190
8383
12995
27438
9297
1676
582F
7AE0
1FD4
4A63
635E
2ABA
0907
1CE0
77FA
00B4
22F4
4030
2596
1D64
05A3
0712
1B1D
0CA6
1FCD
28A8
498A
58B1
0F27
536F
7885
469E
3E26
51FD
708A
7827
49D3
1E3B
1887
26F0
217B
102F
4CB5
2E5B
1CCE
28B7
2700
1D15
1025
5876
3C6A
0874
3FFC
3AA0
7C0B
7B94
19CD
72E9
59D1
6C09
155C
2275
5125
1338
167C
6DB8
02E4
5B65
4C24
6753
77CA
3AF0
6613
3E61
5E25
31DA
4E1D
59BB
3110
79ED
495C
3FE1
2F17
76BC
5F44
0613
3404
7961
182B
548C
2449
1210
01D3
46D5
05FC
05B1
23ED
348B
64B9
0FF7
79D6
20BF
32C3
6B2E
2451
068C
B-4
SEP 2009
PN Offset
continued

Pilot
PN
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
6491
16876
17034
32405
27417
8382
5624
1424
13034
15682
27101
8521
30232
6429
27116
4238
5128
14846
13024
10625
31724
13811
24915
1213
2290
31551
12088
7722
27312
23130
594
25804
31013
32585
3077
17231
31554
8764
15375
13428
17658
13475
22095
24805
4307
23292
1377
28654
6350
16770
1290
4407
1163
12215
7253
8978
25547
3130
31406
6222
20340
25094
23380
10926
22821
31634
4403
689
27045
27557
16307
22338
27550
22096
23136
12199
1213
936
6272
32446
13555
8789
24821
21068
31891
5321
551
12115
4902
1991
14404
17982
19566
2970
23055
15158
29094
653
19155
23588
195B
41EC
428A
7E95
6B19
20BE
15F8
0590
32EA
3D42
69DD
2149
7618
191D
69EC
108E
1408
39FE
32E0
2981
7BEC
35F3
6153
04BD
08F2
7B3F
2F38
1E2A
6AB0
5A5A
0252
64CC
7925
7F49
0C05
434F
7B42
223C
3C0F
3474
44FA
34A3
564F
60E5
10D3
5AFC
0561
6FEE
18CE
4182
050A
1137
048B
2FB7
1C55
2312
63CB
0C3A
7AAE
184E
4F74
6206
5B54
2AAE
5925
7B92
1133
02B1
69A5
6BA5
3FB3
5742
6B9E
5650
5A60
2FA7
04BD
03A8
1880
7EBE
34F3
2255
60F5
524C
7C93
14C9
0227
2F53
1326
07C7
3844
463E
4C6E
0B9A
5A0F
3B36
71A6
028D
4AD3
5C24
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
23933
8438
8517
28314
25692
4191
2812
712
6517
7841
25918
16756
15116
23902
13558
2119
2564
7423
6512
17680
15862
19241
24953
21390
1145
27727
6044
3861
13656
11565
297
12902
27970
28276
22482
28791
15777
4382
20439
6714
8829
19329
31479
24994
22969
11646
21344
14327
3175
8385
645
18087
19577
23015
16406
4489
32729
1565
15703
3111
10170
12547
11690
5463
25262
15817
18085
20324
31470
31726
20965
11169
13775
11048
11568
23023
19554
468
3136
16223
21573
24342
32326
10534
28789
17496
20271
22933
2451
19935
7202
8991
9783
1485
25403
7579
14547
20346
27477
11794
5D7D
20F6
2145
6E9A
645C
105F
0AFC
02C8
1975
1EA1
653E
4174
3B0C
5D5E
34F6
0847
0A04
1CFF
1970
4510
3DF6
4B29
6179
538E
0479
6C4F
179C
0F15
3558
2D2D
0129
3266
6D42
6E74
57D2
7077
3DA1
111E
4FD7
1A3A
227D
4B81
7AF7
61A2
59B9
2D7E
5360
37F7
0C67
20C1
0285
46A7
4C79
59E7
4016
1189
7FD9
061D
3D57
0C27
27BA
3103
2DAA
1557
62AE
3DC9
46A5
4F64
7AEE
7BEE
51E5
2BA1
35CF
2B28
2D30
59EF
4C62
01D4
0C40
3F5F
5445
5F16
7E46
2926
7075
4458
4F2F
5995
0993
4DDF
1C22
231F
2637
05CD
633B
1D9B
38D3
4F7A
6B55
2E12
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
25414
7102
20516
19495
17182
11572
25570
6322
8009
26708
6237
32520
31627
3532
24090
20262
18238
2033
25566
25144
29679
5064
27623
13000
31373
13096
26395
15487
29245
26729
12568
24665
8923
19634
29141
73
26482
6397
29818
8153
302
28136
29125
8625
26671
6424
12893
18502
7765
25483
12596
19975
20026
8958
19143
17142
19670
30191
5822
22076
606
9741
9116
12705
17502
18952
15502
17819
4370
31955
30569
7350
26356
32189
1601
19537
25667
4415
2303
16362
28620
6736
2777
24331
9042
107
4779
13065
30421
20210
5651
31017
30719
23104
7799
17865
26951
25073
32381
16581
6346
1BBE
5024
4C27
431E
2D34
63E2
18B2
1F49
6854
185D
7F08
7B8B
0DCC
5E1A
4F26
473E
07F1
63DE
6238
73EF
13C8
6BE7
32C8
7A8D
3328
671B
3C7F
723D
6869
3118
6059
22DB
4CB2
71D5
0049
6772
18FD
747A
1FD9
012E
6DE8
71C5
21B1
682F
1918
325D
4846
1E55
638B
3134
4E07
4E3A
22FE
4AC7
42F6
4CD6
75EF
16BE
563C
025E
260D
239C
31A1
445E
4A08
3C8E
459B
1112
7CD3
7769
1CB6
66F4
7DBD
0641
4C51
6443
113F
08FF
3FEA
6FCC
1A50
0AD9
5F0B
2352
006B
12AB
3309
76D5
4EF2
1613
7929
77FF
5A40
1E77
45C9
6947
61F1
7E7D
40C5
SEP 2009
B-5
PN Offset
continued
Pilot
PN
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
14726
25685
21356
12149
28966
22898
1713
30010
2365
27179
29740
5665
23671
1680
25861
25712
19245
26887
30897
11496
1278
31555
29171
20472
5816
30270
22188
6182
32333
14046
15873
19843
29367
13352
22977
31691
10637
25454
18610
6368
7887
7730
23476
889
21141
20520
21669
15967
21639
31120
10878
31060
30875
11496
24545
9586
20984
30389
7298
18934
23137
24597
23301
7764
14518
21634
11546
26454
15938
9050
3103
758
16528
20375
10208
17698
8405
28634
1951
20344
26696
3355
11975
31942
9737
9638
30643
13230
22185
2055
8767
15852
16125
6074
31245
15880
20371
8666
816
22309
3986
6455
536C
2F75
7126
5972
06B1
753A
093D
6A2B
742C
1621
5C77
0690
6505
6470
4B2D
6907
78B1
2CE8
04FE
7B43
71F3
4FF8
16B8
763E
56AC
1826
7E4D
36DE
3E01
4D83
72B7
3428
59C1
7BCB
298D
636E
48B2
18E0
1ECF
1E32
5BB4
0379
5295
5028
54A5
3E5F
5487
7990
2A7E
7954
789B
2CE8
5FE1
2572
51F8
76B5
1C82
49F6
5A61
6015
5B05
1E54
38B6
5482
2D1A
6756
3E42
235A
0C1F
02F6
4090
4F97
27E0
4522
20D5
6FDA
079F
4F78
6848
0D1B
2EC7
7CC6
2609
25A6
77B3
33AE
56A9
0807
223F
3DEC
3EFD
17BA
7A0D
3E08
4F93
21DA
0330
5725
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
7363
25594
10678
18026
14483
11449
21128
15005
21838
25797
14870
23232
32747
840
25426
12856
29766
25939
28040
5748
639
27761
26921
10236
2908
15135
11094
3091
28406
7023
20176
30481
26763
6676
32048
27701
17686
12727
9305
3184
24247
3865
11738
20588
30874
10260
31618
20223
31635
15560
5439
15530
29297
5748
25036
4793
10492
30054
3649
9467
25356
32310
25534
3882
7259
10817
5773
13227
7969
4525
18483
379
8264
27127
5104
8849
24150
14317
19955
10172
13348
18609
22879
15971
23864
4819
30181
6615
25960
19007
24355
7926
20802
3037
29498
7940
27125
4333
408
26030
1CC3
63FA
29B6
466A
3893
2CB9
5288
3A9D
554E
64C5
3A16
5AC0
7FEB
0348
6352
3238
7446
6553
6D88
1674
027F
6C71
6929
27FC
0B5C
3B1F
2B56
0C13
6EF6
1B6F
4ED0
7711
688B
1A14
7D30
6C35
4516
31B7
2459
0C70
5EB7
0F19
2DDA
506C
789A
2814
7B82
4EFF
7B93
3CC8
153F
3CAA
7271
1674
61CC
12B9
28FC
7566
0E41
24FB
630C
7E36
63BE
0F2A
1C5B
2A41
168D
33AB
1F21
11AD
4833
017B
2048
69F7
13F0
2291
5E56
37ED
4DF3
27BC
3424
48B1
595F
3E63
5D38
12D3
75E5
19D7
6568
4A3F
5F23
1EF6
5142
0BDD
733A
1F04
69F5
10ED
0198
65AE
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
15408
6414
8164
10347
29369
10389
24783
18400
22135
4625
22346
2545
7786
20209
26414
1478
15122
24603
677
13705
13273
14879
6643
23138
28838
9045
10792
25666
11546
15535
16134
8360
14401
26045
24070
30300
13602
32679
16267
9063
19487
12778
27309
12527
953
15958
6068
23577
32156
32709
32087
97
7618
93
16052
14300
11129
6602
14460
25458
15869
27047
26808
7354
27834
11250
552
27058
14808
9642
32253
26081
21184
11748
32676
2425
19455
19889
18177
2492
15086
30632
27549
6911
9937
2467
25831
32236
12987
11714
19283
11542
27928
26637
10035
10748
24429
29701
14997
32235
3C30
190E
1FE4
286B
72B9
2895
60CF
47E0
5677
1211
574A
09F1
1E6A
4EF1
672E
05C6
3B12
601B
02A5
3589
33D9
3A1F
19F3
5A62
70A6
2355
2A28
6442
2D1A
3CAF
3F06
20A8
3841
65BD
5E06
765C
3522
7FA7
3F8B
2367
4C1F
31EA
6AAD
30EF
03B9
3E56
17B4
5C19
7D9C
7FC5
7D57
0061
1DC2
005D
3EB4
37DC
2B79
19CA
387C
6372
3DFD
69A7
68B8
1CBA
6CBA
2BF2
0228
69B2
39D8
25AA
7DFD
65E1
52C0
2DE4
7FA4
0979
4BFF
4DB1
4701
09BC
3AEE
77A8
6B9D
1AFF
26D1
09A3
64E7
7DEC
32BB
2DC2
4B53
2D16
6D18
680D
2733
29FC
5F6D
7405
3A95
7DEB
B-6
SEP 2009
PN Offset
continued

Pilot
PN
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
3698
16322
17429
21730
17808
30068
12737
28241
20371
13829
13366
25732
19864
5187
23219
28242
6243
445
21346
13256
18472
25945
31051
1093
5829
31546
29833
18146
24813
47
3202
21571
7469
25297
8175
28519
4991
7907
17728
14415
30976
26376
19063
19160
3800
8307
12918
19642
24873
22071
29563
13078
10460
17590
20277
19988
6781
32501
6024
20520
31951
26063
27203
6614
10970
5511
17119
16064
31614
4660
13881
16819
6371
24673
6055
10009
5957
11597
22155
15050
16450
27899
2016
17153
15849
30581
3600
4097
671
20774
24471
27341
19388
25278
9505
26143
13359
2154
13747
27646
0E72
3FC2
4415
54E2
4590
7574
31C1
6E51
4F93
3605
3436
6484
4D98
1443
5AB3
6E52
1863
01BD
5362
33C8
4828
6559
794B
0445
16C5
7B3A
7489
46E2
60ED
002F
0C82
5443
1D2D
62D1
1FEF
6F67
137F
1EE3
4540
384F
7900
6708
4A77
4AD8
0ED8
2073
3276
4CBA
6129
5637
737B
3316
28DC
44B6
4F35
4E14
1A7D
7EF5
1788
5028
7CCF
65CF
6A43
19D6
2ADA
1587
42DF
3EC0
7B7E
1234
3639
41B3
18E3
6061
17A7
2719
1745
2D4D
568B
3ACA
4042
6CFB
07E0
4301
3DE9
7775
0E10
1001
029F
5126
5F97
6ACD
4BBC
62BE
2521
661F
342F
086A
35B3
6BFE
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
1849
8161
29658
10865
8904
15034
18736
26360
30233
19154
6683
12866
9932
23537
31881
14121
24033
20750
10673
6628
9236
25468
28021
21490
23218
15773
27540
9073
24998
20935
1601
31729
24390
24760
24103
26211
22639
24225
8864
19959
15488
13188
29931
9580
1900
16873
6459
9821
24900
31435
30593
6539
5230
8795
27046
9994
17154
28998
3012
10260
28763
31963
31517
3307
5485
17663
28499
8032
15807
2330
21792
28389
16973
32268
17903
23984
17822
22682
25977
7525
8225
30785
1008
28604
20680
30086
1800
17980
20339
10387
25079
31578
9694
12639
23724
32051
21547
1077
21733
13823
0739
1FE1
73DA
2A71
22C8
3ABA
4930
66F8
7619
4AD2
1A1B
3242
26CC
5BF1
7C89
3729
5DE1
510E
29B1
19E4
2414
637C
6D75
53F2
5AB2
3D9D
6B94
2371
61A6
51C7
0641
7BF1
5F46
60B8
5E27
6663
586F
5EA1
22A0
4DF7
3C80
3384
74EB
256C
076C
41E9
193B
265D
6144
7ACB
7781
198B
146E
225B
69A6
270A
4302
7146
0BC4
2814
705B
7CDB
7B1D
0CEB
156D
44FF
6F53
1F60
3DBF
091A
5520
6EE5
424D
7E0C
45EF
5DB0
459E
589A
6579
1D65
2021
7841
03F0
6FBC
50C8
7586
0708
463C
4F73
2893
61F7
7B5A
25DE
315F
5CAC
7D33
542B
0435
54E5
35FF
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
23557
17638
3545
9299
6323
19590
7075
14993
19916
6532
17317
16562
26923
9155
20243
32391
20190
27564
20869
9791
714
7498
23278
8358
9468
23731
25133
2470
17501
24671
11930
9154
7388
3440
27666
22888
13194
26710
7266
15175
15891
26692
14757
28757
31342
19435
2437
20573
18781
18948
30766
5985
6823
20973
10197
9618
22705
5234
12541
8019
22568
5221
25216
1354
29335
6682
26128
29390
8852
6110
11847
10239
6955
10897
14076
12450
8954
19709
1252
15142
26958
8759
12696
11936
25635
17231
22298
7330
30758
6933
2810
8820
7831
19584
2944
19854
10456
17036
2343
14820
5C05
44E6
0DD9
2453
18B3
4C86
1BA3
3A91
4DCC
1984
43A5
40B2
692B
23C3
4F13
7E87
4EDE
6BAC
5185
263F
02CA
1D4A
5AEE
20A6
24FC
5CB3
622D
09A6
445D
605F
2E9A
23C2
1CDC
0D70
6C12
5968
338A
6856
1C62
3B47
3E13
6844
39A5
7055
7A6E
4BEB
0985
505D
495D
4A04
782E
1761
1AA7
51ED
27D5
2592
58B1
1472
30FD
1F53
5828
1465
6280
054A
7297
1A1A
6610
72CE
2294
17DE
2E47
27FF
1B2B
2A91
36FC
30A2
22FA
4CFD
04E4
3B26
694E
2237
3198
2EA0
6423
434F
571A
1CA2
7826
1B15
0AFA
2274
1E97
4C80
0B80
4D8E
28D8
428C
0927
39E4
SEP 2009
B-7
PN Offset
continued
Pilot
PN
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
13904
27198
3685
16820
22479
6850
15434
19332
8518
14698
21476
30475
23984
1912
26735
15705
3881
20434
16779
31413
16860
8322
28530
26934
18806
20216
9245
8271
18684
8220
6837
9613
31632
27448
12417
30901
9366
12225
21458
6466
8999
26718
3230
27961
28465
6791
17338
11832
11407
15553
1056
1413
3311
4951
749
6307
961
2358
28350
31198
11467
8862
6327
7443
28574
25093
6139
22047
32545
7112
28535
10378
15065
5125
12528
23215
20959
3568
26453
29421
24555
10779
25260
16084
26028
29852
14978
12182
25143
15838
5336
21885
20561
30097
21877
23589
26060
9964
25959
3294
3650
6A3E
0E65
41B4
57CF
1AC2
3C4A
4B84
2146
396A
53E4
770B
5DB0
0778
686F
3D59
0F29
4FD2
418B
7AB5
41DC
2082
6F72
6936
4976
4EF8
241D
204F
48FC
201C
1AB5
258D
7B90
6B38
3081
78B5
2496
2FC1
53D2
1942
2327
685E
0C9E
6D39
6F31
1A87
43BA
2E38
2C8F
3CC1
0420
0585
0CEF
1357
02ED
18A3
03C1
0936
6EBE
79DE
2CCB
229E
18B7
1D13
6F9E
6205
17FB
561F
7F21
1BC8
6F77
288A
3AD9
1405
30F0
5AAF
51DF
0DF0
6755
72ED
5FEB
2A1B
62AC
3ED4
65AC
749C
3A82
2F96
6237
3DDE
14D8
557D
5051
7591
5575
5C25
65CC
26EC
6567
0CDE
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
6952
13599
22242
8410
31287
3425
7717
9666
4259
7349
10738
27221
11992
956
26087
20348
22084
10217
28949
27786
8430
4161
14265
13467
9403
10108
17374
16887
9342
4110
23690
17174
15816
13724
18832
28042
4683
17968
10729
3233
16451
13359
1615
26444
26184
23699
8669
5916
18327
20400
528
19710
18507
18327
20298
17005
20444
1179
14175
15599
22617
4431
16999
16565
14287
32574
17857
25907
29100
3556
31111
5189
21328
17470
6264
25451
26323
1784
32150
30538
25033
23345
12630
8042
13014
14926
7489
6091
32551
7919
2668
25730
26132
29940
25734
24622
13030
4982
31887
1647
1B28
351F
56E2
20DA
7A37
0D61
1E25
25C2
10A3
1CB5
29F2
6A55
2ED8
03BC
65E7
4F7C
5644
27E9
7115
6C8A
20EE
1041
37B9
349B
24BB
277C
43DE
41F7
247E
100E
5C8A
4316
3DC8
359C
4990
6D8A
124B
4630
29E9
0CA1
4043
342F
064F
674C
6648
5C93
21DD
171C
4797
4FB0
0210
4CFE
484B
4797
4F4A
426D
4FDC
049B
375F
3CEF
5859
114F
4267
40B5
37CF
7F3E
45C1
6533
71AC
0DE4
7987
1445
5350
443E
1878
636B
66D3
06F8
7D96
774A
61C9
5B31
3156
1F6A
32D6
3A4E
1D41
17CB
7F27
1EEF
0A6C
6482
6614
74F4
6486
602E
32E6
1376
7C8F
066F
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
23393
5619
17052
21292
2868
19538
24294
22895
27652
29905
21415
1210
22396
26552
24829
8663
991
21926
23306
13646
148
24836
24202
9820
12939
2364
14820
2011
13549
28339
25759
11116
31448
27936
3578
12371
12721
10264
25344
13246
544
9914
4601
16234
24475
26318
6224
13381
30013
22195
1756
19068
28716
31958
16097
1308
3320
16682
6388
12828
3518
3494
6458
10717
8463
27337
19846
9388
21201
31422
166
28622
6477
10704
25843
25406
21523
8569
9590
22466
12455
27506
21847
28392
1969
30715
23674
22629
12857
30182
21880
6617
27707
16249
24754
31609
22689
3226
4167
25624
5B61
15F3
429C
532C
0B34
4C52
5EE6
596F
6C04
74D1
53A7
04BA
577C
67B8
60FD
21D7
03DF
55A6
5B0A
354E
0094
6104
5E8A
265C
328B
093C
39E4
07DB
34ED
6EB3
649F
2B6C
7AD8
6D20
0DFA
3053
31B1
2818
6300
33BE
0220
26BA
11F9
3F6A
5F9B
66CE
1850
3445
753D
56B3
06DC
4A7C
702C
7CD6
3EE1
051C
0CF8
412A
18F4
321C
0DBE
0DA6
193A
29DD
210F
6AC9
4D86
24AC
52D1
7ABE
00A6
6FCE
194D
29D0
64F3
633E
5413
2179
2576
57C2
30A7
6B72
5557
6EE8
07B1
77FB
5C7A
5865
3239
75E6
5578
19D9
6C3B
3F79
60B2
7B79
58A1
0C9A
1047
6418
B-8
SEP 2009
PN Offset
continued

Pilot
PN
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
17418
14952
52
27254
15064
10942
377
14303
24427
26629
20011
16086
24374
9969
29364
25560
28281
7327
32449
26334
14760
15128
29912
4244
8499
9362
10175
30957
12755
19350
1153
29304
6041
21668
28048
10096
23388
15542
24013
2684
19018
25501
4489
31011
29448
25461
11846
30331
10588
32154
30173
15515
5371
10242
28052
14714
19550
8866
15297
10898
31315
19475
1278
11431
31392
4381
14898
23959
16091
9037
24162
6383
27183
16872
9072
12966
28886
25118
20424
6729
20983
12372
13948
27547
8152
17354
17835
14378
7453
26317
5955
10346
13200
30402
7311
3082
21398
31104
24272
27123
440A
3A68
0034
6A76
3AD8
2ABE
0179
37DF
5F6B
6805
4E2B
3ED6
5F36
26F1
72B4
63D8
6E79
1C9F
7EC1
66DE
39A8
3B18
74D8
1094
2133
2492
27BF
78ED
31D3
4B96
0481
7278
1799
54A4
6D90
2770
5B5C
3CB6
5DCD
0A7C
4A4A
639D
1189
7923
7308
6375
2E46
767B
295C
7D9A
75DD
3C9B
14FB
2802
6D94
397A
4C5E
22A2
3BC1
2A92
7A53
4C13
04FE
2CA7
7AA0
111D
3A32
5D97
3EDB
234D
5E62
18EF
6A2F
41E8
2370
32A6
70D6
621E
4FC8
1A49
51F7
3054
367C
6B9B
1FD8
43CA
45AB
382A
1D1D
66CD
1743
286A
3390
76C2
1C8F
0C0A
5396
7980
5ED0
69F3
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
8709
7476
26
13627
7532
5471
20844
19007
32357
26066
30405
8043
12187
17064
14682
12780
26348
24479
28336
13167
7380
7564
14956
2122
16713
4681
16911
28070
18745
9675
21392
14652
23068
10834
14024
5048
11694
7771
32566
1342
9509
24606
22804
27969
14724
24682
5923
27373
5294
16077
29906
20593
17473
5121
14026
7357
9775
4433
21468
5449
29461
26677
639
22639
15696
18098
7449
24823
20817
24474
12081
16971
31531
8436
4536
6483
14443
12559
10212
17176
26311
6186
6974
31729
4076
8677
27881
7189
16562
32090
17821
5173
6600
15201
16507
1541
10699
15552
12136
31429
2205
1D34
001A
353B
1D6C
155F
516C
4A3F
7E65
65D2
76C5
1F6B
2F9B
42A8
395A
31EC
66EC
5F9F
6EB0
336F
1CD4
1D8C
3A6C
084A
4149
1249
420F
6DA6
4939
25CB
5390
393C
5A1C
2A52
36C8
13B8
2DAE
1E5B
7F36
053E
2525
601E
5914
6D41
3984
606A
1723
6AED
14AE
3ECD
74D2
5071
4441
1401
36CA
1CBD
262F
1151
53DC
1549
7315
6835
027F
586F
3D50
46B2
1D19
60F7
5151
5F9A
2F31
424B
7B2B
20F4
11B8
1953
386B
310F
27E4
4318
66C7
182A
1B3E
7BF1
0FEC
21E5
6CE9
1C15
40B2
7D5A
459D
1435
19C8
3B61
407B
0605
29CB
3CC0
2F68
7AC5
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
30380
15337
10716
13592
2412
15453
13810
12956
30538
10814
18939
19767
20547
29720
31831
26287
11310
25724
21423
5190
258
13978
4670
23496
23986
839
11296
30913
27297
10349
32504
18405
3526
19161
23831
21380
4282
32382
806
6238
10488
19507
27288
2390
19094
13860
9225
2505
27806
2408
10924
23096
22683
10955
17117
15837
22647
10700
30293
5579
11057
30238
14000
22860
27172
307
20380
26427
10702
30024
14018
4297
13938
25288
27294
31835
8228
12745
6746
1456
27743
27443
31045
12225
21482
14678
30656
13721
21831
30208
9995
3248
12030
5688
2082
23143
25906
15902
21084
25723
76AC
3BE9
29DC
3518
096C
3C5D
35F2
329C
774A
2A3E
49FB
4D37
5043
7418
7C57
66AF
2C2E
647C
53AF
1446
0102
369A
123E
5BC8
5DB2
0347
2C20
78C1
6AA1
286D
7EF8
47E5
0DC6
4AD9
5D17
5384
10BA
7E7E
0326
185E
28F8
4C33
6A98
0956
4A96
3624
2409
09C9
6C9E
0968
2AAC
5A38
589B
2ACB
42DD
3DDD
5877
29CC
7655
15CB
2B31
761E
36B0
594C
6A24
0133
4F9C
673B
29CE
7548
36C2
10C9
3672
62C8
6A9E
7C5B
2024
31C9
1A5A
05B0
6C5F
6B33
7945
2FC1
53EA
3956
77C0
3599
5547
7600
270B
0CB0
2EFE
1638
0822
5A67
6532
3E1E
525C
647B
SEP 2009
B-9
PN Offset
continued
Pilot
PN
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
29572
13173
10735
224
12083
22822
2934
27692
10205
7011
22098
2640
4408
102
27632
19646
26967
32008
7873
655
25274
16210
11631
8535
19293
12110
21538
10579
13032
14717
11666
25809
5008
32418
22175
11742
22546
21413
133
4915
8736
1397
18024
15532
26870
5904
24341
13041
23478
1862
5578
25731
10662
11084
31098
16408
6362
2719
14732
22744
1476
8445
21118
22198
22030
10363
25802
2496
31288
24248
14327
23154
13394
1806
17179
10856
25755
15674
7083
29096
3038
16277
25525
20465
28855
32732
20373
9469
26155
6957
12214
21479
31914
32311
11276
20626
423
2679
15537
10818
7384
3375
29EF
00E0
2F33
5926
0B76
6C2C
27DD
1B63
5652
0A50
1138
0066
6BF0
4CBE
6957
7D08
1EC1
028F
62BA
3F52
2D6F
2157
4B5D
2F4E
5422
2953
32E8
397D
2D92
64D1
1390
7EA2
569F
2DDE
5812
53A5
0085
1333
2220
0575
4668
3CAC
68F6
1710
5F15
32F1
5BB6
0746
15CA
6483
29A6
2B4C
797A
4018
18DA
0A9F
398C
58D8
05C4
20FD
527E
56B6
560E
287B
64CA
09C0
7A38
5EB8
37F7
5A72
3452
070E
431B
2A68
649B
3D3A
1BAB
71A8
0BDE
3F95
63B5
4FF1
70B7
7FDC
4F95
24FD
662B
1B2D
2FB6
53E7
7CAA
7E37
2C0C
5092
01A7
0A77
3CB1
2A42
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
14786
18538
17703
112
17993
11411
1467
13846
16958
23649
11049
1320
2204
51
13816
9823
25979
16004
24240
20631
12637
8105
18279
16763
29822
6055
10769
17785
6516
19822
5833
25528
2504
16209
31391
5871
11273
30722
20882
22601
4368
21354
9012
7766
13435
2952
32346
18600
11739
931
2789
31869
5331
5542
15549
8204
3181
19315
7366
11372
738
24130
10559
11099
11015
23041
12901
1248
15644
12124
21959
11577
6697
903
28593
5428
31857
7837
17385
14548
1519
20982
32742
27076
30311
16366
27126
23618
32041
17322
6107
26575
15957
28967
5638
10313
20207
19207
20580
5409
39C2
486A
4527
0070
4649
2C93
05BB
3616
423E
5C61
2B29
0528
089C
0033
35F8
265F
657B
3E84
5EB0
5097
315D
1FA9
4767
417B
747E
17A7
2A11
4579
1974
4D6E
16C9
63B8
09C8
3F51
7A9F
16EF
2C09
7802
5192
5849
1110
536A
2334
1E56
347B
0B88
7E5A
48A8
2DDB
03A3
0AE5
7C7D
14D3
15A6
3CBD
200C
0C6D
4B73
1CC6
2C6C
02E2
5E42
293F
2B5B
2B07
5A01
3265
04E0
3D1C
2F5C
55C7
2D39
1A29
0387
6FB1
1534
7C71
1E9D
43E9
38D4
05EF
51F6
7FE6
69C4
7667
3FEE
69F6
5C42
7D29
43AA
17DB
67CF
3E55
7127
1606
2849
4EEF
4B07
5064
1521
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
13347
7885
6669
8187
18145
14109
14231
27606
783
6301
5067
15383
1392
7641
25700
25259
19813
20933
638
16318
6878
1328
14744
22800
25919
4795
18683
32658
1586
27208
17517
599
16253
8685
29972
22128
19871
19405
17972
8599
10142
26834
23710
27280
6570
7400
26374
22218
29654
13043
13427
31084
24023
23931
15836
6085
30324
27561
13821
269
28663
29619
2043
6962
29119
22947
9612
18698
16782
29735
2136
8086
10553
11900
19996
5641
28328
25617
26986
5597
14078
13247
499
30469
17544
28510
23196
13384
4239
20725
6466
28465
19981
16723
4522
678
15320
29116
5388
22845
3423
1ECD
1A0D
1FFB
46E1
371D
3797
6BD6
030F
189D
13CB
3C17
0570
1DD9
6464
62AB
4D65
51C5
027E
3FBE
1ADE
0530
3998
5910
653F
12BB
48FB
7F92
0632
6A48
446D
0257
3F7D
21ED
7514
5670
4D9F
4BCD
4634
2197
279E
68D2
5C9E
6A90
19AA
1CE8
6706
56CA
73D6
32F3
3473
796C
5DD7
5D7B
3DDC
17C5
7674
6BA9
35FD
010D
6FF7
73B3
07FB
1B32
71BF
59A3
258C
490A
418E
7427
0858
1F96
2939
2E7C
4E1C
1609
6EA8
6411
696A
15DD
36FE
33BF
01F3
7705
4488
6F5E
5A9C
3448
108F
50F5
1942
6F31
4E0D
4153
11AA
02A6
3BD8
71BC
150C
593D
B-10
SEP 2009
PN Offset
continued

Pilot
PN
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
5850
5552
12589
23008
27636
17600
17000
21913
30320
28240
7260
17906
5882
22080
12183
23082
17435
18527
31902
18783
20027
7982
20587
10004
13459
13383
28930
4860
13108
24161
20067
2667
13372
28743
24489
249
19960
29682
31101
27148
26706
5148
4216
5762
245
21882
3763
206
28798
32402
23074
20250
14629
29175
13943
11072
29492
5719
7347
12156
25623
27725
28870
31478
28530
24834
9075
32265
3175
17434
12178
25613
31692
25384
18908
25816
4661
31115
7691
1311
16471
15771
16112
21062
29690
10141
19014
22141
11852
26404
30663
32524
28644
10228
23536
18045
25441
27066
13740
13815
16DA
15B0
312D
59E0
6BF4
44C0
4268
5599
7670
6E50
1C5C
45F2
16FA
5640
2F97
5A2A
441B
485F
7C9E
495F
4E3B
1F2E
506B
2714
3493
3447
7102
12FC
3334
5E61
4E63
0A6B
343C
7047
5FA9
00F9
4DF8
73F2
797D
6A0C
6852
141C
1078
1682
00F5
557A
0EB3
00CE
707E
7E92
5A22
4F1A
3925
71F7
3677
2B40
7334
1657
1CB3
2F7C
6417
6C4D
70C6
7AF6
6F72
6102
2373
7E09
0C67
441A
2F92
640D
7BCC
6328
49DC
64D8
1235
798B
1E0B
051F
4057
3D9B
3EF0
5246
73FA
279D
4A46
567D
2E4C
6724
77C7
7F0C
6FE4
27F4
5BF0
467D
6361
69BA
35AC
35F7
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
2925
2776
18758
11504
13818
8800
8500
31516
15160
14120
3630
8953
2941
11040
17947
11541
29661
30207
15951
30079
30413
3991
31205
5002
19353
19443
14465
2430
6554
32480
30433
21733
6686
27123
32260
20908
9980
14841
28014
13574
13353
2574
2108
2881
20906
10941
22153
103
14399
16201
11537
10125
21166
30407
21767
5536
14746
17687
16485
6078
31799
30746
14435
15739
14265
12417
24453
28984
18447
8717
6089
31802
15846
12692
9454
12908
18214
29433
16697
19635
28183
20721
8056
10531
14845
24050
9507
25858
5926
13202
30175
16262
14322
5114
11768
27906
32652
13533
6870
21703
0B6D
0AD8
4946
2CF0
35FA
2260
2134
7B1C
3B38
3728
0E2E
22F9
0B7D
2B20
461B
2D15
73DD
75FF
3E4F
757F
76CD
0F97
79E5
138A
4B99
4BF3
3881
097E
199A
7EE0
76E1
54E5
1A1E
69F3
7E04
51AC
26FC
39F9
6D6E
3506
3429
0A0E
083C
0B41
51AA
2ABD
5689
0067
383F
3F49
2D11
278D
52AE
76C7
5507
15A0
399A
4517
4065
17BE
7C37
781A
3863
3D7B
37B9
3081
5F85
7138
480F
220D
17C9
7C3A
3DE6
3194
24EE
326C
4726
72F9
4139
4CB3
6E17
50F1
1F78
2923
39FD
5DF2
2523
6502
1726
3392
75DF
3F86
37F2
13FA
2DF8
6D02
7F8C
34DD
1AD6
54C7
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
24457
17161
21314
28728
22162
26259
22180
2266
10291
26620
19650
14236
11482
25289
12011
13892
17336
10759
26816
31065
8578
24023
16199
22310
30402
16613
13084
3437
1703
22659
26896
1735
16178
19166
665
20227
24447
16771
27209
6050
29088
7601
4905
5915
6169
21303
28096
8905
26997
15047
28430
8660
2659
8803
19690
22169
8511
17393
11336
13576
22820
13344
20107
8013
18835
16793
9818
4673
13609
10054
10988
14744
17930
25452
11334
15451
11362
2993
11012
5806
20180
8932
23878
20760
32764
32325
25993
3268
25180
12149
10193
9128
7843
25474
11356
11226
16268
14491
8366
26009
5F89
4309
5342
7038
5692
6693
56A4
08DA
2833
67FC
4CC2
379C
2CDA
62C9
2EEB
3644
43B8
2A07
68C0
7959
2182
5DD7
3F47
5726
76C2
40E5
331C
0D6D
06A7
5883
6910
06C7
3F32
4ADE
0299
4F03
5F7F
4183
6A49
17A2
71A0
1DB1
1329
171B
1819
5337
6DC0
22C9
6975
3AC7
6F0E
21D4
0A63
2263
4CEA
5699
213F
43F1
2C48
3508
5924
3420
4E8B
1F4D
4993
4199
265A
1241
3529
2746
2AEC
3998
460A
636C
2C46
3C5B
2C62
0BB1
2B04
16AE
4ED4
22E4
5D46
5118
7FFC
7E45
6589
0CC4
625C
2F75
27D1
23A8
1EA3
6382
2C5C
2BDA
3F8C
389B
20AE
6599
SEP 2009
B-11
PN Offset
continued
Pilot
PN
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
13463
15417
23101
14957
23429
12990
12421
28875
4009
1872
15203
30109
24001
4862
14091
6702
3067
28643
21379
20276
25337
19683
10147
16791
17359
13248
22740
13095
10345
30342
27866
9559
8808
12744
11618
27162
17899
29745
31892
23964
23562
2964
18208
15028
21901
24566
18994
13608
27492
11706
3684
23715
15314
32469
9816
4444
5664
7358
27264
28128
30168
29971
3409
16910
20739
10191
12819
19295
10072
15191
27748
720
29799
27640
263
24734
16615
20378
25116
19669
14656
27151
28728
25092
22601
2471
25309
15358
17739
12643
32730
19122
16870
10787
18400
20295
1937
17963
7438
12938
3497
3C39
5A3D
3A6D
5B85
32BE
3085
70CB
0FA9
0750
3B63
759D
5DC1
12FE
370B
1A2E
0BFB
6FE3
5383
4F34
62F9
4CE3
27A3
4197
43CF
33C0
58D4
3327
2869
7686
6CDA
2557
2268
31C8
2D62
6A1A
45EB
7431
7C94
5D9C
5C0A
0B94
4720
3AB4
558D
5FF6
4A32
3528
6B64
2DBA
0E64
5CA3
3BD2
7ED5
2658
115C
1620
1CBE
6A80
6DE0
75D8
7513
0D51
420E
5103
27CF
3213
4B5F
2758
3B57
6C64
02D0
7467
6BF8
0107
609E
40E7
4F9A
621C
4CD5
3940
6A0F
7038
6204
5849
09A7
62DD
3BFE
454B
3163
7FDA
4AB2
41E6
2A23
47E0
4F47
0791
462B
1D0E
328A
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
19355
20428
31950
19686
31762
6495
18834
27061
22020
936
19553
27422
32560
2431
19029
3351
21549
26145
30737
10138
24748
30625
16897
28955
28727
6624
11370
18499
17892
15171
13933
17275
4404
6372
5809
13581
29477
27592
15946
11982
11781
1482
9104
7514
31510
12283
9497
6804
13746
5853
1842
24685
7657
29014
4908
2222
2832
3679
13632
14064
15084
29877
18580
8455
26301
24027
22325
27539
5036
21399
13874
360
29711
13820
20159
12367
28239
10189
12558
26710
7328
31547
14364
12546
25112
19183
32594
7679
27801
22157
16365
9561
8435
23341
9200
27039
19956
27945
3719
6469
4B9B
4FCC
7CCE
4CE6
7C12
195F
4992
69B5
5604
03A8
4C61
6B1E
7F30
097F
4A55
0D17
542D
6621
7811
279A
60AC
77A1
4201
711B
7037
19E0
2C6A
4843
45E4
3B43
366D
437B
1134
18E4
16B1
350D
7325
6BC8
3E4A
2ECE
2E05
05CA
2390
1D5A
7B16
2FFB
2519
1A94
35B2
16DD
0732
606D
1DE9
7156
132C
08AE
0B10
0E5F
3540
36F0
3AEC
74B5
4894
2107
66BD
5DDB
5735
6B93
13AC
5397
3632
0168
740F
35FC
4EBF
304F
6E4F
27CD
310E
6856
1CA0
7B3B
381C
3102
6218
4AEF
7F52
1DFF
6C99
568D
3FED
2559
20F3
5B2D
23F0
699F
4DF4
6D29
0E87
1945
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
17460
17629
10461
21618
11498
193
16140
13419
10864
28935
18765
27644
21564
5142
1211
1203
5199
16945
4883
25040
7119
17826
4931
25705
10726
17363
2746
10952
19313
29756
14297
21290
1909
8994
13295
21590
26468
13636
5207
29493
18992
12567
12075
26658
21077
15595
4921
14051
5956
21202
5164
17126
21566
21845
28149
9400
19459
7190
3101
491
25497
29807
26508
4442
4871
31141
9864
12589
5417
8549
14288
8503
20357
15381
18065
24678
23858
7610
18097
20918
7238
30549
16320
20853
26736
10327
24404
7931
5310
554
27311
6865
7762
15761
12697
24850
15259
24243
30508
13982
4434
44DD
28DD
5472
2CEA
00C1
3F0C
346B
2A70
7107
494D
6BFC
543C
1416
04BB
04B3
144F
4231
1313
61D0
1BCF
45A2
1343
6469
29E6
43D3
0ABA
2AC8
4B71
743C
37D9
532A
0775
2322
33EF
5456
6764
3544
1457
7335
4A30
3117
2F2B
6822
5255
3CEB
1339
36E3
1744
52D2
142C
42E6
543E
5555
6DF5
24B8
4C03
1C16
0C1D
01EB
6399
746F
678C
115A
1307
79A5
2688
312D
1529
2165
37D0
2137
4F85
3C15
4691
6066
5D32
1DBA
46B1
51B6
1C46
7755
3FC0
5175
6870
2857
5F54
1EFB
14BE
022A
6AAF
1AD1
1E52
3D91
3199
6112
3B9B
5EB3
772C
369E
B-12
SEP 2009
PN Offset
continued

Pilot
PN
501
502
503
504
505
506
507
508
509
510
511
14Chip Delay
Q
I
Q
(Dec.)
(Hex.)
14301
23380
11338
2995
23390
14473
6530
20452
12226
1058
12026
SEP 2009
19272
29989
8526
18139
3247
28919
7292
20740
27994
2224
6827
37DD
5B54
2C4A
0BB3
5B5E
3889
1982
4FE4
2FC2
0422
2EFA
4B48
7525
214E
46DB
0CAF
70F7
1C7C
5104
6D5A
08B0
1AAB
13Chip Delay
Q
I
Q
(Dec.)
(Hex.)
19006
11690
5669
21513
11695
19860
3265
10226
6113
529
6013
9636
29870
4263
27985
18539
30279
3646
10370
13997
1112
17257
4A3E
2DAA
1625
5409
2DAF
4D94
0CC1
27F2
17E1
0211
177D
25A4
74AE
10A7
6D51
486B
7647
0E3E
2882
36AD
0458
4369
0Chip Delay
Q
I
Q
(Dec.)
(Hex.)
11239
30038
30222
13476
2497
31842
24342
25857
27662
24594
16790
25039
24086
21581
21346
28187
23231
18743
11594
7198
105
4534
2BE7
7556
760E
34A4
09C1
7C62
5F16
6501
6C0E
6012
4196
61CF
5E16
544D
5362
6E1B
5ABF
4937
2D4A
1C1E
0069
11B6
B-13
PN Offset
continued
Notes
B-14
SEP 2009
Appendix C: ATP Matrix Table

Appendix Content
C
Reoptimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Usage & Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Detailed Optimization/ATP Test Matrix . . . . . . . . . . . . . . . . . . . . . . . .
SEP 2009
C-1
C-1
C-1
Table of Contents
continued
Notes
SEP 2009
Reoptimization
Reoptimization
Usage & Background
Periodic maintenance of a site may also mandate reoptimization of

specific portions of the site. An outline of some basic guidelines is
included in the following tables.
NOTE
Reoptimization steps listed for any assembly detailed in

the tables below must be performed anytime an RF cable
associated with it is replaced.
Detailed Optimization/ATP Test

Matrix
Table C-1 outlines in more detail the tests that would need to be
performed if one of the BTS components were to fail and be replaced. It
is also assumes that all modules are placed OOSROM via the LMF
until full redundancy of all applicable modules is implemented.
The following guidelines should also be noted when using this table.
NOTE
Not every procedure required to bring the site back in
service is indicated in Table C-1. It is meant to be used as a
guideline ONLY. The table assumes that the user is familiar
enough with the BTS Optimization/ATP procedure to
understand which test equipment set ups, calibrations, and
BTS site preparation will be required before performing the
Table # procedures referenced.
Various passive BTS components (such as the DRDCs, filter; etc.) only
require a TX calibration audit to be performed in lieu of a full path
calibration. If the TX path calibration audit fails, the entire RF path
calibration will need to be repeated. If the RF path calibration fails,
further troubleshooting is warranted.
Whenever any CCCP BACKPLANE is replaced, it is assumed that
only power to the CCCP shelf being replaced is turned off via the
breaker supplying that shelf.
NOTE
If any significant change in signal level results from any
component being replaced in the RX or TX signal flow
paths, it would be identified by rerunning the RX and TX
calibration audit command.
SEP 2009
C-1
Reoptimization
continued
When the CIO is replaced, the CCCP shelf remains powered up. The
BBX boards may need to be removed, then reinstalled into their
original slots, and redownloaded (code and BLO data). RX and TX
calibration audits should then be performed.
Download Code/Data
Table 3-16
Enable CSMs
D D D D
D
D
Table 3-20
GPS &HSO Initialization/

Verification
Table 3-21
LFR Initialization/
Verification
Table 3-46
TX Path Calibration
Table 3-47
Download Offsets to BBX
Table 3-46
TX Path Audit
Table 3-55
RFDS Path Calibration and

Offset Data Download (see
Note [)
4
4
4
6 5 4
RFDS
D
9
D D
D D D D D D
D
RFDS cables
Swithch Card
PA Bamd[ass Fo;ter or Combiner
PA Trunking Module
LPAC Cable
GLI3
ETIB or Associated Cables
RGD/20pair Punchblock w/RGD
CCD Card
50pair Punchblock w/RGPS
1 1 4
1 4
1 1 4
3 3 4 7
3 4 7
1 1 6
3 4
6 6
RFDS Path Calibration should be performed at initial BTS installation AND after replacement of the RFDS FRU.
RFDS Path Calibration is NOT required for other FRU replacement but may be used as an additional fault isolation tool.
Table 4-1
Spectral Purity TX Mask
Table 4-1
Waveform Quality (rho)
Table 4-1
Pilot Time Offset
4
4
4
Table 4-1
Code Domain Power/

Noise Floor
Table 4-1
FER Test
5 5
Table 3-58/
Table 3-67
HSO/HSOX
CSM/GPS
Table 3-14
LFR
MCC24E/MCC8E/MCC1X
CCCP Shelf Assembly (Backplane)
CIO
MPC / EMPC
RX Cables
Description
TX Cables
Doc
Tbl
#
DRDC or TRDC
BBX2/BBX1X
Table C-1: SC 4812ET BTS Optimization and ATP Test Matrix
*
*
1 4
1 4
1 4
1 4 8 8 8
5 2 2 5 8 8 8
Alarm Tests
7
D
C-2
SEP 2009
Reoptimization
continued
C
RFDS
RFDS cables
Swithch Card
PA Bamd[ass Fo;ter or Combiner
PA Trunking Module
LPAC Cable
GLI3
ETIB or Associated Cables
CCD Card
RGD/20pair Punchblock w/RGD
50pair Punchblock w/RGPS
HSO/HSOX
CSM/GPS
LFR
MCC24E/MCC8E/MCC1X
CCCP Shelf Assembly (Backplane)
BBX2/BBX1X
CIO
MPC / EMPC
TX Cables
Description
RX Cables
Doc
Tbl
#
DRDC or TRDC
Table C-1: SC 4812ET BTS Optimization and ATP Test Matrix
OPTIMIZATION AND TEST LEGEND:
D Required
* Perform if determined necessary for addtional fault isolation, repair assurance, or required for site
certification.
** Replace power supply modules one at a time so that power to the CCCP shelf is not interrupted. If power
to the shelf is lost, all cards in the shelf must be downloaded again.
1.
Perform on all carrier and sector TX paths to the CCCP cage.
2.
Perform on all carrier and sector RX paths to the CCCP cage.
3.
Perform on all primary and redundant TX paths of the affected carrier.
4.
Perform on the affected carrier and sector TX path(s) (BBXR replacement affects all carrier
and sector TX paths)
5.
Perform on the affected carrier and sector RX path(s) (BBXR replacement affects all carrier
RX paths)
6.
Perform on all RF paths of the affected carrier and sector (RFDS replacement affects all
carriers)
7.
Perform with redundant BBX for at least one sector on one carrier.
8.
Verify performance by performing on one sector of one carrier only.
Perform only if RGD/RGPS, LFR antenna, or HSO or LFR expansion was installed
9.
10.
Verify performance by performing testing on one sector of each carrier.
SEP 2009
C-3
Reoptimization
continued
Notes
C-4
SEP 2009
Appendix D: BBX Gain

Appendix Content
BBX Gain Set Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Usage & Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D-1
D-1
SEP 2009
Table of Contents
continued
Notes
SEP 2009
BBX Gain Set Point

BBX Gain Set Point
Usage & Background
Table D-1 outlines the relationship between the total of all code domain
channel element gain settings (digital root sum of the squares) and the
BBX Gain Set Point between 33.0 dBm and 44.0 dBm. The resultant
RF output (as measured at the top of the BTS in dBm) is shown in the
table. The table assumes that the BBX Bay Level Offset (BLO) values
have been calculated.
As an illustration, consider a BBX keyed up to produce a CDMA carrier
with only the Pilot channel (no MCCs forward link enabled). Pilot gain
is set to 262. In this case, the BBX Gain Set Point is shown to correlate
exactly to the actual RF output anywhere in the 33 to 44 dBm output
range. (This is the level used to calibrate the BTS).
Table D-1: BBX Gain Set Point vs. Actual BTS Output (in dBm)
dBm
Gainb
44
43
42
41
40
39
38
37
36
35
34
33
541
43.3
42.3
41.3
40.3
39.3
533
43.2
42.2
41.2
40.2
39.2
525
43
42
41
40
39
517
42.9
41.9
40.9
39.9
38.9
509
42.8
41.8
40.8
39.8
38.8
501
42.6
41.6
40.6
39.6
38.6
493
43.5
42.5
41.5
40.5
39.5
38.5
485
43.4
42.4
41.4
40.4
39.4
38.4
477
43.2
42.2
41.2
40.2
39.2
38.2
469
43.1
42.1
41.1
40.1
39.1
38.1
461
42.9
41.9
40.9
39.9
38.9
37.9
453
42.8
41.8
40.8
39.8
38.8
37.8
445
43.6
42.6
41.6
40.6
39.6
38.6
37.6
437
43.4
42.4
41.4
40.4
39.4
38.4
37.4
429
43.3
42.3
41.3
40.3
39.3
38.3
37.3
421
43.1
42.1
41.1
40.1
39.1
38.1
37.1
413
43
42
41
40
39
38
37
405
42.8
41.8
40.8
39.8
38.8
37.8
36.8
397
43.6
42.6
41.6
40.6
39.6
38.6
37.6
36.6
389
43.4
42.4
41.4
40.4
39.4
38.4
37.4
36.4
381
43.3
42.3
41.3
40.3
39.3
38.3
37.3
36.3

SEP 2009
D-1
BBX Gain Set Point
continued
Table D-1: BBX Gain Set Point vs. Actual BTS Output (in dBm)
dBm
Gainb
44
43
42
41
40
39
38
37
36
35
34
33
374
43.1
42.1
41.1
40.1
39.1
38.1
37.1
36.1
366
42.9
41.9
40.9
39.9
38.9
37.9
36.9
35.9
358
42.7
41.7
40.7
39.7
38.7
37.7
36.7
35.7
350
43.5
42.5
41.5
40.5
39.5
38.5
37.5
36.5
35.5
342
43.3
42.3
41.3
40.3
39.3
38.3
37.3
36.3
35.3
334
43.1
42.1
41.1
40.1
39.1
38.1
37.1
36.1
35.1
326
42.9
41.9
40.9
39.9
38.9
37.9
36.9
35.9
34.9
318
42.7
41.7
40.7
39.7
38.7
37.7
36.7
35.7
34.7
310
43.5
42.5
41.5
40.5
39.5
38.5
37.5
36.5
35.5
34.5
302
43.2
42.2
41.2
40.2
39.2
38.2
37.2
36.2
35.2
34.2
294
43
42
41
40
39
38
37
36
35
34
286
42.8
41.8
40.8
39.8
38.8
37.8
36.8
35.8
34.8
33.8
278
43.5
42.5
41.5
40.5
39.5
38.5
37.5
36.5
35.5
34.5
33.5
270
43.3
42.3
41.3
40.3
39.3
38.3
37.3
36.3
35.3
34.3
33.3
262
43
42
41
40
39
38
37
36
35
34
33
254
42.7
41.7
40.7
39.7
38.7
37.7
36.7
35.7
34.7
33.7
32.7
246
43.4
42.4
41.4
40.4
39.4
38.4
37.4
36.4
35.4
34.4
33.4
32.4
238
43.2
42.2
41.2
40.2
39.2
38.2
37.2
36.2
35.2
34.2
33.2
32.2
230
42.9
41.9
40.9
39.9
38.9
37.9
36.9
35.9
34.9
33.9
32.9
31.9
222
42.6
41.6
40.6
39.6
38.6
37.6
36.6
35.6
34.6
33.6
32.6
31.6
214
42.2
41.2
40.2
39.2
38.2
37.2
36.2
35.2
34.2
33.2
32.2
31.2
D-2
SEP 2009
Appendix E: CDMA Operating Frequency

Appendix Content
CDMA Operating Frequency Programming Information . . . . . . . . . . . . . . . . .
E-1
1900 MHz PCS Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calculating 1900 MHz Center Frequencies . . . . . . . . . . . . . . . . . . . . . .
E-2
E-3
800 MHz CDMA Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calculating 800 MHz Center Frequencies . . . . . . . . . . . . . . . . . . . . . . .
E-5
E-5
SEP 2009
Table of Contents
continued
Notes
SEP 2009
CDMA Operating Frequency Programming Information

CDMA Operating Frequency Programming Information
Programming of each of the BTS BBX synthesizers is performed by the
BTS GLI cards over the Concentration Highway Interface (CHI) bus.
This programming data determines the transmit and receive operating
frequencies (channels) for each BBX.
SEP 2009
E-1
1900 MHz PCS Channels

Figure E-1 shows the valid channels for the North American PCS
1900 MHz frequency spectrum. There are 10 CDMA wireline or
nonwireline band channels used in a CDMA system (unique per
customer operating system).
Figure E-1: North America PCS Frequency Spectrum
(CDMA Allocation)
FREQ (MHz)
RX
TX
1851.25 1931.25
CHANNEL
25
275
1863.75
1943.75
1871.25
1951.25
1883.75
1963.75
1896.25
1976.25
1908.75
1988.75
425
675
E
F
925
1175
E-2
FW004
SEP 2009
continued
Calculating 1900 MHz Center

Frequencies
Table E-1 shows selected 1900 MHz CDMA candidate operating

channels, listed in both decimal and hexadecimal, and the corresponding
transmit, and receive frequencies. Center frequencies (in MHz) for
channels not shown in the table may be calculated as follows:
S TX = 1930 + 0.05 * Channel#
Example: Channel 262

TX = 1930 + 0.05 * 262 = 1943.10 MHz
S RX = TX 80

RX = 1943.10 50 = 1863.10 MHz
Actual frequencies used depend on customer CDMA system frequency

plan.
Each CDMA channel requires a 1.77 MHz frequency segment. The
actual CDMA carrier is 1.23 MHz wide, with a 0.27 MHz guard band on
both sides of the carrier.
Minimum frequency separation required between any CDMA carrier and
the nearest NAMPS/AMPS carrier is 900 kHz (center-to-center).
Table E-1: 1900 MHz TX and RX Frequency vs. Channel
Channel Number
Decimal
Hex
25
0019
50
0032
75
004B
100
0064
125
007D
150
0096
175
00AF
200
00C8
225
00E1
250
00FA
275
0113
300
012C
325
0145
350
015E
375
0177
400
0190
425
01A9
450
01C2
475
01DB
500
01F4
525
020D
550
0226
Transmit Frequency (MHz)

Center Frequency
1931.25
1932.50
1933.75
1935.00
1936.25
1937.50
1938.75
1940.00
1941.25
1942.50
1943.75
1945.00
1946.25
1947.50
1948.75
1950.00
1951.25
1952.50
1953.75
1955.00
1956.25
1957.50
Receive Frequency (MHz)

Center Frequency
1851.25
1852.50
1853.75
1855.00
1856.25
1857.50
1858.75
1860.00
1861.25
1862.50
1863.75
1865.00
1866.25
1867.50
1868.75
1870.00
1871.25
1872.50
1873.75
1875.00
1876.25
1877.50

SEP 2009
E-3
continued
Channel Number
Decimal
Hex
575
023F
600
0258
625
0271
650
028A
675
02A3
700
02BC
725
02D5
750
02EE
775
0307
800
0320
825
0339
850
0352
875
036B
900
0384
925
039D
950
03B6
975
03CF
1000
03E8
1025
0401
1050
041A
1075
0433
1100
044C
1125
0465
1150
047E
1175
0497
E-4

Center Frequency
1958.75
1960.00
1961.25
1962.50
1963.75
1965.00
1966.25
1967.50
1968.75
1970.00
1971.25
1972.50
1973.75
1975.00
1976.25
1977.50
1978.75
1980.00
1981.25
1982.50
1983.75
1985.00
1986.25
1987.50
1988.75

Center Frequency
1878.75
1880.00
1881.25
1882.50
1883.75
1885.00
1886.25
1887.50
1888.75
1890.00
1891.25
1892.50
1893.75
1895.00
1896.25
1897.50
1898.75
1900.00
1901.25
1902.50
1903.75
1905.00
1906.25
1807.50
1908.75
SEP 2009
800 MHz CDMA Channels

Figure E-2 shows the valid channels for the North American cellular
telephone frequency spectrum. There are 10 CDMA wireline or
nonwireline band channels used in a CDMA system (unique per
customer operating system).
893.970
848.970
799
891.480
891.510
846.480
846.510
694
689
777
889.980
890.010
844.980
845.010
666
667
644
356
OVERALL WIRELINE (B) BANDS
739
879.990
880.020
834.990
835.020
333
334
311
OVERALL NONWIRELINE (A) BANDS
716
717
870.000
870.030
825.000
825.030
1023
1
CHANNEL
1013
869.040
RX FREQ
(MHz)
991
TX FREQ
(MHz)
824.040
Figure E-2: North American Cellular Telephone System Frequency Spectrum (CDMA Allocation).
CDMA NONWIRELINE (A) BAND
CDMA WIRELINE (B) BAND

FW00402
Calculating 800 MHz Center

Frequencies
Table E-2 shows selected 800 MHz CDMA candidate operating

channels, listed in both decimal and hexadecimal, and the corresponding
transmit, and receive frequencies. Center frequencies (in MHz) for
channels not shown in the table may be calculated as follows:
S Channels 1777
TX = 870 + 0.03 * Channel#

TX = 870 + 0.03*262 = 877.86 MHz
S Channels 10131023
TX = 870 + 0.03 * (Channel# 1023)

TX = 870 +0.03 *(1015 1023) = 869.76 MHz
S RX = TX 45 MHz

RX = 877.86 45 = 832.86 MHz
SEP 2009
E-5
continued

Channel Number
Decimal
Hex

Center Frequency

Center Frequency
0001
870.0300
825.0300
25
0019
870.7500
825.7500
50
0032
871.5000
826.5000
75
004B
872.2500
827.2500
100
0064
873.0000
828.0000
125
007D
873.7500
828.7500
150
0096
874.5000
829.5000
175
00AF
875.2500
830.2500
200
00C8
876.0000
831.0000
225
00E1
876.7500
831.7500
250
00FA
877.5000
832.5000
275
0113
878.2500
833.2500
300
012C
879.0000
834.0000
325
0145
879.7500
834.7500
350
015E
880.5000
835.5000
375
0177
881.2500
836.2500
400
0190
882.0000
837.0000
425
01A9
882.7500
837.7500
450
01C2
883.5000
838.5000
475
01DB
884.2500
839.2500
500
01F4
885.0000
840.0000
525
020D
885.7500
840.7500
550
0226
886.5000
841.5000
575
023F
887.2500
842.2500
600
0258
888.0000
843.0000
625
0271
888.7500
843.7500
650
028A
889.5000
844.5000
675
02A3
890.2500
845.2500
700
02BC
891.0000
846.0000
725
02D5
891.7500
846.7500
750
02EE
892.5000
847.5000
775
0307
893.2500
848.2500
E-6
SEP 2009
continued

Channel Number
Decimal
Hex

Center Frequency

Center Frequency
NOTE
Channel numbers 778 through 1012 are not used.
1013
03F5
869.7000
1023
03FF
870.0000
824.7000
825.0000
SEP 2009
E-7
continued
Notes
E-8
SEP 2009
Appendix F: Test Equipment Preparation

Appendix Content
SEP 2009
Test Equipment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test equipment setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify and set GPIB address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test equipment interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibrating test sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable calibration set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-1
F-1
F-1
F-1
F-1
F-1
F-1
Test Equipment Setup: Agilent E7495 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initial Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Agilent E7495A/B with the LMF . . . . . . . . . . . . . . . . . . . . .
Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Sensor Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-2
F-2
F-2
F-2
F-3
F-4

F-5
Verifying and Setting GPIB Addresses: Advantest R3465 Communications

Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-7
Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator . .
F-8
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set . .
F-9
Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester . .
F-11
Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter . . . . . . . .
F-13
Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator . . .
F-15
Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter . . . .
F-17
Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box . . . . . . . .
F-18
Test Equipment Interconnection: Advantest R3267 and R3562 . . . . . . . . . . . . .

10 MHz reference signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-19
F-19
F-19
Test Equipment Interconnection: Agilent 8935 Series E6380 and E4438C . . .

Agilent 8932/E4438C Test Equipment Interconnection . . . . . . . . . . . .
F-20
F-20
Test Equipment Interconnection: Agilent E4406A and E4438C . . . . . . . . . . . .
F-21
Test Equipment Calibration: Agilent E4406A Selfalignment . . . . . . . . . . . . .
F-22
Test Equipment Calibration: Gigatronics 8542 Power Meter . . . . . . . . . . . . . . .
F-23
Cable Calibration with R3465 Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-24
F-24
Table of Contents
continued
Notes
SEP 2009

Purpose
Test equipment preparation information includes verification and setting

GPIB addresses, interunit cabling, and equipment calibration for items
which are not calibrated with the LMF Calibrate Test Equipment
function. Manual cable calibration procedures using the Advantest
R3465 test set are also provided.
This portion of the publication is organized according to the following
for the listed CDMA test equipment supported by the LMF.
Test equipment setup
S Agilent E7495A/B test equipment setup

Verify and set GPIB address
S
S
S
S
S
S
S
S
S
Advantest R3267 spectrum analyzer

Advantest R3465 analyzer
Advantest R3562 signal generator
Agilent 8935 series E6380 analyzer (formerly HP 8935)
Agilent E4406A transmitter test set
Agilent E4418 power meter
Agilent E4438C signal generator
Gigatronics 8541C power meter

GPIB adapter
Test equipment
interconnection
S Advantest R3267 spectrum analyzer and Advantest R3562 signal

generator
S Agilent 8935 analyzer (formerly HP 8935) and Agilent E4438C signal

generator
S Agilent E4406A transmitter test set and Agilent E4438C signal

generator
Calibrating test sets
S Agilent E4406A Transmitter Tester Self-alignment (Calibration)

S Gigatronics 8542 power meter (Calibration)
Cable calibration set-up
S Calibrating Test Cable Setup using Advantest R3465
SEP 2009
F-1
Test Equipment Setup: Agilent E7495

Initial Requirement
This test equipment requires a warm-up period of at least 30 minutes

before BTS testing or calibration begins.
Using the Agilent E7495A/B
with the LMF
The Agilent E7495 does not require the use of the 19MHz frequency
reference; if connected, it will be ignored. The Even Sec SYNC
connection is required.
The Agilent E7495 signal generator is only calibrated down to 80dB. In
order to achieve accurate FER testing, be sure the RX setup includes at
least 40dB of attenuation. This will ensure the signal generator will
output sufficient power to operate in the calibrated range.
Set the IP Address in the test set as described in Table F-1.
Table F-1: Set IP Address on Agilent E7495 test set
n Step
Action
Use the System Button > Controls > IPAdmin to set an

IP address on the E7495A/B as 128.0.0.11, and Netmask
to 255.255.255.128.
If the IP addressed was changed, reboot the E7495
For compatibility, change the LMF computer Network

Interface Card (NIC) IP address to 128.0.0.48,
subnetmask 255.255.255.128.
Connection
Connect the E7495 test set as described in the Test Equpment

Connection to the LMF section of Chapter 3.
F-2
SEP 2009
continued
Power Sensor Calibration
Table F-2 describes the E7495 Power Sensor Calibration.

Table F-2: E7495 Power Sensor Calibration
n Step
Action
Display the power meter screen.
Zero the power meter. Make sure equipment is connected

as shown in Figure F-1.
Press the Zero softkey.
Press the Continue softkey.
Calibrate the power meter:

Press Ref CF.
Enter the reference cal factor, reading it off the label
on the power sensor head.
Press Calibrate.
Connect the power sensor (see Figure F-2).
Press Continue.
Press Cal Factor.
Enter the cal factor from the label on the power
sensor head. Select a cal factor that is within the
operating frequency of the BTS being calibrated.
F
Figure F-1: Agilent E7495 PrePower Sensor Calibration connection
GPIO
Port 2
RF In
Power REF
50 MHz
Serial 1
Sensor
Serial 2
Ext Ref
In
Even Second
Sync In
Use only
Agilent supplied
power adapter
Port 1
RF Out / SWR
GPS
Antenna
POWER SENSOR
NOT CONNECTED
SEP 2009
F-3
continued
Figure F-2: Agilent E7495 Power Sensor Calibration connection

POWER SENSOR
CONNECTED
GPIO
Port 2
RF In
Power REF
50 MHz
Serial 1
Sensor
Serial 2
Ext Ref
In
Even Second
Sync In
Use only
Agilent supplied
power adapter
Port 1
RF Out / SWR
GPS
Antenna
Cable Calibration
Follow the directions in the LMF application program to calibrate

cables.
Additional cable calibration details Calibrate the short cable (see
Figure 3-31) and two 10 dB attenuators to establish a baseline and then
calibrate the TX and RX setups. Because at least 40 dB of attenuation
is needed when testing the FER, the setup for RX is the same as for
TX.
F-4
SEP 2009

Spectrum Analyzer
Spectrum Analyzer
Figure F-3: Setting Advantest R3267 GPIB Address
SOFTKEY LABLE
DISPLAY AREA
SOFTKEY
BUTTONS
on
REMOTE LED
LCL KEY
CONFIG KEY
KEYPAD
BS KEY
ENTR KEY
Refer to Figure F-3 when performing the following.
Table F-3: Verify and Set/Change Advantest R3267 GPIB Address

Step
Action
If the REMOTE LED is lighted, press the LCL key.

The LED extinguishes.
Press the CONFIG key.

The CONFIG softkey labels will appear in the softkey label display area of the instrument
display.
The current GPIB address will be displayed below the GPIB Address softkey label.
SEP 2009
F-5

Spectrum Analyzer continued
Table F-3: Verify and Set/Change Advantest R3267 GPIB Address
Step
3
Action
If the current GPIB address is not set to 18, perform the following to change it:
1. Press the GPIB Address softkey. A GPIB Address entry window will open in the instrument
display showing the current GPIB address.
2. Enter 18 on the keypad in the ENTRY section of the instrument front panel. Characters typed on
the keypad will replace the address displayed in the GPIB Address entry window.
NOTE
To correct an entry, press the BS (backspace) key at the lower right of the keypad to delete one
character at a time.
3. Press the ENTR key to the lower right of the keypad to enter the address.
Result:
The GPIB Address entry window closes.
The new address is displayed in the bottom portion of the GPIB Address softkey label.
F-6
SEP 2009

Communications Test Set
Communications Test Set
Figure F-4: R3465 Communications Test Set
REF UNLOCK
Preset
BNC
T
EVEN
SEC/SYNC IN
CDMA
TIME BASE IN
GPIB and
others
POWER
OFF
ON
Vernier
Knob
Shift
LCL
REF FW00337
NOTE
This procedure assumes that the test equipment is set up
and ready for testing.

Table F-4: Verify and Set/Change Advantest R3465 Communications Test Set GPIB Address
Step
Action
To verify that the GPIB address is set correctly, perform the following procedure:
Press SHIFT then PRESET.
Press LCL.
Press the GPIB and Others CRT menu key to view the current address.
Turn the vernier knob as required to select 18.
Press the vernier knob to set the address.
To return to normal operation, press Shift and Preset.
SEP 2009
F-7
Verifying and Setting GPIB Addresses: Advantest R3562 Signal

Generator
Verifying and Setting GPIB Addresses: Advantest R3562 Signal
Generator
Set the GPIB ADDRESS switch on the rear of the Advantest R3562
signal generator to address 1 as shown in Figure F-5.
Figure F-5: Advantest R3562 GPIB Address Switch Setting
GPIB Address set to 1
GPIP ADDRESS
5 4 3 2 1
1
1
0
F-8
SEP 2009
Verifying and Setting GPIB Addresses: Agilent 8935 Series

E6380 Test Set
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380
Test Set
Figure F-6: Agilent 8935 Series E6380 Test Set Verify and Set/Change GPIB Address
Preset
Local
Inst Config
FW00885
Cursor Control
Shift
NOTE
Follow Refer to Figure F-6 when performing the following.

Table F-5: Verify and Set/Change Agilent 8935 Series E6380 Test Set GPIB Address
Step
1
Action
NOTE
The HP I/O configuration MUST be set to Talk & Listen, or NO device on the GPIB bus will be
accessible. (Consult test equipment manufacturers documentation for additional information as
required.)
To verify that the GPIB addresses are set correctly, press Shift and LOCAL on the 8935. The
current HPIB address is displayed at the top of the screen.
NOTE
HPIB is the same as GPIB.
SEP 2009
F-9
Verifying and Setting GPIB Addresses: Agilent 8935 Series

E6380 Test Set continued
Table F-5: Verify and Set/Change Agilent 8935 Series E6380 Test Set GPIB Address
Step
Action
Press Shift and Inst Config.
Turn the Cursor Control knob to move the cursor to the HPIB Adrs field.
Press the Cursor Control knob to select the field.
Turn the Cursor Control knob as required to change the address to 18.
Press the Cursor Control knob to set the address.
Press Preset to return to normal operation.
F-10
SEP 2009
Verifying and Setting GPIB Addresses: Agilent E4406A

Transmitter Tester
Transmitter Tester
Figure F-7: Agilent E4406A Transmitter Tester Verify and Set/Change GPIB Address
Active Function Area
Softkey Label Display Area
System Key
Bk Sp Key
Enter Key
Softkey Buttons
Data Entry Keypad
Table F-6: Verify and Set/Change Agilent E4406A Transmitter Tester GPIB Address
Step
1
Action
In the SYSTEM section of the instrument front panel, press the System key.
Result: The softkey labels displayed on the right side of the instrument screen will change.
Press the Config I/O softkey button to the right of the instrument screen.
Result:
The softkey labels will change.
The current instrument GPIB address will be displayed below the GPIB Address softkey label.
SEP 2009
F-11

Transmitter Tester continued
Table F-6: Verify and Set/Change Agilent E4406A Transmitter Tester GPIB Address
Step
3
Action
1. Press the GPIB Address softkey button. In the onscreen Active Function Area, GPIB Address
will be displayed followed by the current GPIB address.
2. On the front panel Data Entry keypad, enter the communications system analyzer GPIB address of
18.
Result:
The GPIB Address label will change to Enter.
Digits entered with the keypad will replace the current GPIB address in the display.
NOTE
To correct an entry, press the Bk Sp key at the upper right of the keypad to delete one character at a
time.
3. Press the Enter softkey button or the keypad Enter key to set the new GPIB address.
Result:
The Config I/O softkey labels will reappear.
The new GPIB address will be displayed under the GPIB Address softkey label.
F-12
SEP 2009
Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter

Figure F-8: Agilent E4418B Power Meter Verify and Set/Change GPIB Address
PRESET/
LOCAL
STATUS
REPORTING
LINE
SYSTEM/
INPUTS
SOFTKEY
LABEL
AREA
SOFTKEY
MENU
TITLE
ARROW
KEYS
LEFT
DOWN
UP
RIGHT
SOFTKEY
MENU PAGE
NUMBER
ticdma05962.eps

Table F-7: Verify and Set/Change Agilent E4418 Power Meter GPIB Address
Step
Action
If RMT (remote operation) is displayed on the left end of the instrument screen status reporting line,
press the Preset/Local front panel button.
The status line entry will change to LCL (local or front panel operation).
On the instrument front panel, press the System/Inputs key.

The softkey labels displayed on the right side of the instrument screen will change.
Press the Remote Interface > Configure Interface > GPIB softkeys to the right of the instrument
screen.
The softkey labels will change.
The current instrument GPIB address will be displayed below the GPIB Addr softkey label.
If the current GPIB address is set to 13, skip to step 11.
If the current GPIB address is not set to 13, press the GPIB Addr softkey.
A popup window will appear and display the current GPIB address.
Modify the GPIB address in the popup as necessary using the following front panel keys to perform
the indicated functions:
S Up and down arrow keys to change the digit on which the cursor is currently located
S Left and right arrow keys to move the cursor to other digits
SEP 2009
F-13

continued
Table F-7: Verify and Set/Change Agilent E4418 Power Meter GPIB Address
Step
Action
10
When the GPIB address is correct, press the Enter softkey.
11
Return the instrument to the required setup configuration for testing.
F-14
SEP 2009
Verifying and Setting GPIB Addresses: Agilent E4438C Signal

Generator
Generator
Figure F-9: Agilent E4438C Verify and Set/Change GPIB Address
Active Entry
Area
Softkey Label
Display Area
Return
Key
Utility Key
Softkey
Buttons
Numeric
Keypad
Backspace
Key
ticdma06850.eps
F
Table F-8: Verify and Change Agilent E4438C Signal Generator GPIB Address
Step
Action
In the MENUS section of the instrument front panel, press the Utility key.
Press the GPIB/RS232/LAN softkey button to the right of the instrument screen.
Result:
S The softkey labels will change.

S The current instrument GPIB address will be displayed below the GPIB Address softkey label.
3
If the current GPIB address is set to 1, skip to step 7.
If the current GPIB address is not set to 1, press the GPIB Address softkey button.
Result:
S The GPIB Address label and current GPIB address will change to boldface.
S In the onscreen Active Entry Area, Address: will be displayed followed by the current GPIB
address.

SEP 2009
F-15

Generator continued
Table F-8: Verify and Change Agilent E4438C Signal Generator GPIB Address
Step
5
Action
On the front panel Numeric keypad, enter the signal generator GPIB address of 1.
Result:
S The GPIB Address label will change to Enter.

S Digits entered with the keypad will replace the current GPIB address in the Active Entry display.
NOTE
To correct an entry, press the backspace key at the lower right of the keypad to delete one character at
a time.
6
Press the Enter softkey button to set the new GPIB address.
Result: The new GPIB address will be displayed under the GPIB Address softkey label.
Exit from the Utility menus by pressing the Return key several times.
F-16
SEP 2009
Verifying and Setting GPIB Addresses: Gigatronics 8541C Power

Meter
Verifying and Setting GPIB Addresses: Gigatronics 8541C Power
Meter
Figure F-10: Gigatronics 8541C Power Meter Detail
MENU
ENTER
ARROW
KEYS
REF FW00564

NOTE
Table F-9: Verify and Set/Change Gigatronics 8541C Power Meter GPIB Address
Step
1
Action
! CAUTION
Do not connect/disconnect the power meter sensor cable with AC power applied to the meter.
Disconnection could result in destruction of the sensing element or miscalibration.
Press MENU.
Use the b arrow key to select CONFIG MENU and press ENTER.
Use the b arrow key to select GPIB and press ENTER.

The current Mode and GPIB Address are displayed.
If the Mode is not set to 8541C, perform the following to change it:
Use the a arrow keys as required to select MODE.
Use the by arrow keys as required to set MODE to 8541C.
If the GPIB address is not set to 13, perform the following to change it:
Use the arrow key to select ADDRESS.
Use the by arrow keys as required to set the GPIB address to 13.
Press ENTER to return to normal operation.
SEP 2009
F-17
Verifying and Setting GPIB Addresses: RS232 GPIB Interface

Box
Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box
Be sure that the RS232 GPIB interface box DIP switches are set as
shown in Figure F-11.
Figure F-11: Verify and Set/Change RS232 GPIB Interface Box GPIB
Address
DIP SWITCH SETTINGS
S MODE
DATA FORMAT
BAUD RATE
ON
GPIB ADRS
G MODE
RS232GPIB
INTERFACE BOX
F-18
SEP 2009
Test Equipment Interconnection: Advantest R3267 and R3562

Test Equipment Interconnection: Advantest R3267 and R3562
To provide proper operation during testing when both units are required,
the R3257 spectrum analyzer must be interconnected with the R3562
signal generator as follows:
10 MHz reference signal
Connect a BNC (M)BNC (M) cable between the R3562 SYNTHE

REF IN connector and the R3267 10 MHz OUT connector as shown in
Figure F-12.
Serial I/O
Using the Advantest cable provided, connect the R3267 SERIAL I/O
connector to the R3562 SERIAL I/O connector as shown in
Figure F-12.
Figure F-12: Advantest 10 MHz Reference and Serial I/O Connections
R3267
10 MHZ OUT
R3267
SERIAL I/O
TO GPIB BOX
R3562
SYNTHE REF IN
SEP 2009
TO GPIB
BOX
R3562
SERIAL I/O
TDME00101
F-19
Test Equipment Interconnection: Agilent 8935 Series E6380 and
E4438C
Test Equipment Interconnection: Agilent 8935 Series E6380 and
E4438C
Agilent 8932/E4438C Test

Equipment Interconnection
To perform FER testing on a 1X BTS with the Agilent 8935, a

1Xcapable signal generator, such as the Agilent E4438C, must be used
in conjunction with the CDMA base station test set. For proper
operation, the test equipment items must be interconnected as follows:
10 MHz reference signal Connect a BNC (M)BNC (M) cable from
the 8935 10 MHz REF OUT connector to the E4438C 10MHz IN
connector as shown in Figure F-13
Even second pulse reference Refer to Figure F-13, and connect a
BNC T connector to the 8935 EVEN SEC SYNC IN connector.
Connect a BNC (M)BNC (M) cable from one side of the BNC T to
the E4438C PATT TRIG IN connector. Connect the other side of the
BNC T to the CSM board SYNC MONITOR connector using a BNC
(M)BNC (M) cable.
Figure F-13: Agilent 8935/E4438C 10MHz Reference and Even Second Tick Connections
E4438C
PATT TRIG IN
E4438C
10 MHz IN
TO GPIB
8935
EVEN SECOND
SYNC IN
WITH BNC T
8935
10 MHz
REF OUT
TO CSM BOARD
SYNCH MONITOR
(EVEN SEC TICK)
OR
UBS SSI TREF OUT
TDME00201
F-20
SEP 2009
Test Equipment Interconnection: Agilent E4406A and E4438C

Test Equipment Interconnection: Agilent E4406A and E4438C
To provide proper operation during testing when both units are required,
the 10 MHz reference signal from the E4406A transmitter test set must
be provided to the E4438C signal generator. Connect a BNC (M)BNC
(M) cable from the E4406A 10 MHz OUT (SWITCHED) connector to
the E4438C 10MHz IN connector as shown in Figure F-14.
Figure F-14: Agilent 10 MHz Reference Connections
E4438C
10 MHz IN
TO GPIB BOX
E4406A
10 MHz OUT
(SWITCHED)
TDME00091
SEP 2009
F-21
Test Equipment Calibration: Agilent E4406A Selfalignment

Test Equipment Calibration: Agilent E4406A Selfalignment
Figure F-15: Agilent E4406A
Softkey Label
Display Area
Softkey
Buttons
System
Key
Table F-10: Agilent E4406A Selfalignment (Calibration)

Step
1
Action
In the SYSTEM section of the instrument front panel, press the System key.
Press the Alignments softkey button to the right of the instrument screen.
Result: The softkey labels will change.
Press the Align All Now softkey button.

Result:
All other instrument functions will be suspended during the alignment.
The display will change to show progress and results of the alignments performed.
The alignment will take less than one minute.
F-22
SEP 2009
Test Equipment Calibration: Gigatronics 8542 Power Meter

Test Equipment Calibration: Gigatronics 8542 Power Meter
Precise transmit output power calibration measurements are made using
a bolometertype broadband power meter with a sensitive power sensor.
Follow the steps in Table F-11 to enter information unique to the power
sensor. Refer to Figure F-16 as necessary.
Table F-11: Calibrate Gigatronics 8542 Power Meter
Step
1
Action
! CAUTION
Do not connect/disconnect the power meter sensor cable with AC power applied to the meter.
Disconnection could result in destruction of the sensing element or miscalibration.
Make sure the power meter POWER pushbutton is OFF.
Connect the power sensor cable to the SENSOR input.
Set the POWER pushbutton to ON.
NOTE
Allow the power meter and sensor to warm up and stabilize for a minimum of 60 minutes before
performing the calibration procedure.
4
Connect the power sensor to the CALIBRATOR output connector.
Press ZERO.
Wait for the process to complete. Sensor factory calibration data is read to power meter during this
process.
When the zeroing process is complete, disconnect the power sensor from the CALIBRATOR output.
Figure F-16: Gigatronics 8541C Power Meter

CONNECT POWER SENSOR TO
CALIBRATOR POWER REFERENCE
WHEN CALIBRATING/ZEROING UNIT
CONNECT POWER SENSOR

WITH POWER METER
TURNED OFF
AC POWER
FRONT VIEW
GPIB CONNECTION
REAR VIEW
FW00564
SEP 2009
F-23
Cable Calibration with R3465 Test Set

NOTE
Warm-up BTS equipment for a minimum of 60 minutes
prior to performing the BTS optimization procedure. This
assures BTS site stability and contributes to optimization
accuracy. (Time spent running initial power-up,
hardware/firmware audit, and BTS download counts as
warm-up time.)
CAUTION
If any piece of test equipment (i.e., test cable, RF adapter)
has been replaced, re-calibration must be performed.
Failure to do so could introduce measurement errors,
resulting in incorrect measurements and degradation to
system performance..
NOTE
calibrating the overall test set. Calibrate the test equipment
after it has been allowed to warm-up and stabilize for a
minimum of 60 minutes.
F
Prerequisites
Prior to performing this procedure, all actions for preparing the LMF,
updating LMF files, and any other pre-calibration procedures identified
in Chapter 3 must be completed.
NOTE
Be sure the GPIB Interface box is OFF for this procedure.
Perform the following to calibrate the test cable setup using the
Advantest R3465. Advantest R3465 manual test setup and calibration
must be performed at both the TX and RX frequencies.
Table F-12: Procedure for Calibrating Test Cable Setup Using Advantest R3465
Step
Action
NOTE
This procedure can only be performed after test equipment has been allowed to warmup and stabilize for a
minimum of 60 minutes.
1
Press the SHIFT and the PRESET keys located below the display.
F-24
SEP 2009
continued
Step
Action
Press the ADVANCE key in the MEASUREMENT area of the control panel.
Select the CDMA Sig CRT menu key.
Select the Setup CRT menu key.
Using the vernier knob and the cursor keys set the following parameters:
NOTE
Fields not listed remain at default.
Generator Mode: SIGNAL
Link: FORWARD
Level Unit: dBm
CalCorrection: ON
Level Offset: OFF
6
Select the return CRT menu key.
Press FREQ key in the ENTRY area.
Set the frequency to the desired value using the keypad entry keys.
Verify that the Mod CRT menu key is highlighting OFF; if not, press the Mod key to toggle it OFF.
10
Verify that the Output CRT menu key is highlighting OFF; if not, press the Output key to toggle it
OFF.
11
Press the LEVEL key in the ENTRY area.
12
Set the LEVEL to 0 dBm using the key pad entry keys.
13
Zero power meter. Next connect the power sensor directly to the RF OUT port on the R3561L
CDMA Test Source Unit.
14
Press the Output CRT menu key to toggle Output to ON.
15
Record the power meter reading ________________________
16
Disconnect the power meter sensor from the R3561L RF OUT jack.
NOTE
The Power Meter sensor lower limit is 30 dBm. Thus, only components having losses < 30 dB
should be measured using this method. For best accuracy, always rezero the power meter before
connecting the power sensor to the component being calibrated. Then, after connecting the
power sensor to the component, record the calibrated loss immediately.
SEP 2009
F-25
continued
Step
Action
17
Disconnect all components in the the test setup and calibrate each one separately. Connect each
component oneatatime between the RF OUT port and the power sensor (see Figure F-17,
Setups A, B, and C). Record the calibrated loss value displayed on the power meter for each
connection.
Example:
(A) 1st Test Cable
= 0.5 dB
(B) 2nd Test Cable
= 1.4 dB
(C) 20 dB Attenuator
= 20.1 dB
(D) 30 dB Directional Coupler
= 29.8 dB
18
Press the Output CRT menu key to toggle Output OFF.
19
Calculate the total test setup loss by adding up all the individual losses:
Example:
Total test setup loss = 0.5 + 1.4 + 20.1 + 29.8 = 51.8 dB
This calculated value will be used in the next series of tests.
20
Press the FREQ key in the ENTRY area.
21
Using the keypad entry keys, set the test frequency to the RX frequency.
22
Repeat steps 9 through 19 for the RX frequency.
23
Refer to Table 3-41 for assistance in manually setting the cable loss values into the LMF.
F-26
SEP 2009
continued
Figure F-17: Cable Calibration using Advantest R3465

RF OUT
POWER
SENSOR
(A) & (B)
POWER
SENSOR
F
(C)
20 DB / 2 WATT
ATTENUATOR
POWER
SENSOR
(C)
POWER
SENSOR
(D)
100 W
NONRADIATING
RF LOAD
SEP 2009
FW00320
30 DB
DIRECTIONAL
COUPLER
F-27
continued
Notes
F-28
SEP 2009
Appendix G: Download ROM Code

Appendix Content
Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G-1
G-1
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Download ROM Code

Download ROM Code
Download ROM Code
ROM code can be downloaded to a device that is in any state. After the
download is started, the device being downloaded changes to
OOS_ROM (blue) and remains OOS_ROM (blue). The same Rlevel
RAM code must then be downloaded to the device. This procedure
includes steps for both the ROM code download and the RAM code
download.
ROM code files cannot be selected automatically. The ROM code file
must be selected manually. Follow the procedure in Table G-1 to
download ROM code.
Prerequisite
S ROM and RAM code files exist for the device to be downloaded.
CAUTION
The Rlevel of the ROM code to be downloaded must be
the same as the Rlevel of the ROM code for other devices
in the BTS. Code must not be mixed in a BTS. This
procedure should only be used to upgrade replacement
devices for a BTS and it should not be used to upgrade all
devices in a BTS. If a BTS is to be upgraded from one
Rlevel to another, the optimization and ATP procedures
must first be performed with the BTS in the original
configuration. The upgrade should then be done by the
OMCR.
G
Table G-1: Download ROM Code
Step
1
Action
Click on the device to be downloaded.
NOTE
More than one device of the same type can be selected for download by either clicking on each one to
be downloaded or from the BTS menu bar Select pulldown menu, select the device item that applies.
Where: device = the type of device to be loaded (BBX, CSM, GLI, MCC)
2
Click on the Status menu item.

A status report window appears.
SEP 2009
G-1
Download ROM Code
continued

Step
4
Action
Make a note of the number in the HW Bin Type column.
NOTE
HW Bin Type is the Hardware Binary Type for the device. This code is used as the last four digits in
the filename of a devices binary ROM code file. Using this part of the filename, the ROM code file
can be matched to the device in which it is to be loaded.
5
Click on the OK button to dismiss the status report window.
NOTE
ROM code is automatically selected for download from the <x>:\<lmf home
directory>\version folder>\<code folder> specified by the NextLoad property. To
check the value of the NextLoad property, click on Util>Examine>Display Nextload. A popup
message will show the value of the NextLoad.
Click on the Download Code Manual menu item.
Result: A file selection window appears.
Doubleclick on the version folder that contains the desired ROM code file.
Doubleclick on the Code folder.

Result: A list of ROM and RAM code files is displayed.
! CAUTION
A ROM code file having the correct hardware binary type (HW Bin Type) needs to be chosen. The
hardware binary type (last four digits in the file name) was determined in step 4. Unpredictable results
can happen and the device may be damaged (may have to be replaced) if a ROM code file with wrong
binary type is downloaded.
Choose a ROM code file having the correct hardware binary type (HW Bin Type).
The hardware binary type (last four digits in the file name) was determined in step 4.
10
Click on the ROM code file that matches the device type and HW Bin Type (e.g., bbx_rom.bin.0604
for a BBX having a HW Bin Type of 0604).
Result: The file should be highlighted.
11
Click on the Load button.

A status report window displays the result of the download.
NOTE
If the ROM load failed for some devices, load them individually by clicking on one device, perform
steps 6 through 11 for it, and repeat the process for each remaining device.
12
Click on the Ok button to close the status report window.
13
14
Select the Tools menu item.
15
Click on the Update NextLoad>CDMA menu item.

G-2
SEP 2009
Download ROM Code
continued

Step
Action
16
Select the version number of the folder that was used for the ROM code download.
17
18
Click on the Save button.

Result: A popup message indicates that the NextLoad property has been updated.
Click on the OK button to dismiss the popup message.
19
Click on the device that was downloaded with ROM code.
20
21
Click on the Download Code menu item to download RAM code.

Result: A status report window displays the result of the download.
NOTE
Data is automatically downloaded to GLI devices when the RAM code is downloaded. Use the
Download Data procedure to download data to other device types after they have been upgraded.
22

The downloaded device should be OOS_RAM (yellow) unless it is a GLI in which case it should be
INS (green).
23
Click on the device that was downloaded.
24
25
26
Click on the Status menu item.

Result: A status report window displays the result of the query for each selected device.
Verify that the status report window displays the correct ROM and RAM version numbers.
27
SEP 2009
G-3
Download ROM Code
continued
Notes
G-4
SEP 2009
Appendix H: Cable Interconnection

Appendix Content
IntraCabinet Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SC 4812ET IntraCabinet Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCCP Cables and Cable Connectors . . . . . . . . . . . . . . . . . . . . . . . . . .
RF Cabinet PA Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LPAC Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ETIB Cables and Cable Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPAN I/O Cable Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . .
DRDC/TRDC Cables and Cable Connections . . . . . . . . . . . . . . . . . . .
MPC Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RFDS Cabling Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50 Pair Punchblock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm and Span Line Cable Pin/Signal Information . . . . . . . . . . . . . . .
RF Cabinet Parts Locator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-1
H-1
H-4
H-7
H-11
H-12
H-13
H-15
H-20
H-22
H-26
H-28
H-33
SEP 2009
Table of Contents
continued
Notes
SEP 2009
IntraCabinet Cabling
SC 4812ET IntraCabinet
Cabling
This appendix provides the identification and location of the cables

connecting the components which make up the SC4812ET RF cabinet.
The number of cables and components incorporated in the RF cabinet
will vary depending on the the manner in which the cabinet is equipped.
For example, a 3 sector, 2 carrier system will require less components
and less cables than a 6 sector 2 carrier system.
Refer to Table H-1 and Figure H-1 through Figure H-19 for the cable
you wish to research.
NOTE
In some cases cables with the same number are used to
connect two different signalling paths. These cables are
designated A & B and the point they connect to and from
is also designated A & B. Ensure the correct cable (A or B)
is connected to the correct designation (A or B) connector
or plug.
Table H-1: SC4812ET RF Cabinet InterConnect Cables
DRDC, Combiner, Trunking Backplane Cables
CABLE #
FROM
NOTE
TO
3064795A05
TX CIO
Figure H-6
Trunking BP
3064735A10
TX Trunking BP
Figure H-5
Combiner Connector Pnl
3064735A07
TX Combiner
See Figure H-1, Figure H-11,

Figure H-12, Figure H-13, and
Figure H-14
DRDC
3064735A11
TX Combiner
(See Above)
DRDC
3064735A12
TX Combiner
(See Above)
DRDC
3064795A07
TX CIO
Figure H-11
Trunking BP
3086435H01
TX Combiner QDS
PkZ Adptr
3086435H02
TX Combiner QDS
PkZ Adptr
3086435H03
TX Combiner QDS
PkZ Adptr
3086168H01
Power PA PDA
Figure H-5
Trunk BP
CCCP Cables
CABLE #
FROM
NOTE
TO
3064809A01
Power CCCP/PDA
See Figure H-1 & Figure H-5
CCCP Backplane
3064899A04
LAN I/O A in
CCCP LAN I/O A In

SEP 2009
H-1
continued

CCCP Cables (cont)
CABLE #
FROM
NOTE
TO
3064899A04
LAN I/O B in
CCCP LAN I/O B In
3086033H03
GPS Surge Arrestor
CCCPBackplane
3064899A04
LAN I/O B in
CCCP LAN I/O B In
3064899A03
CCCP LAN I/O A Out
LAN I/O A Out
3064899A03
CCCP LAN I/O B Out
LAN I/O B Out
3064899A07
Sync CSM
See Figure H-1
I/O
3086000H02
Site I/O CCCP
See Figure H-9
J2 on ETIB
3086001H02
A SPAN I/O BlkHd
CCCP/A SPAN I/O
3086001H02
B SPAN I/O BlkHd
CCCP/B SPAN I/O
3086086H02
Alarm CCCP
J1 on ETIB
3086366H02
HSO/LFR
CCCP HSO/LFR
4886044H01
LBD
CCCP Backplane
Span I/O Board Cables

CABLE #
FROM
NOTE
TO
3086601H01
SPAN I/O Pblock
CSU
3086601H02
SPAN CSU
A & B SPAN I/O BRD
3086001H02
SPAN CSU
A & B SPAN Connector on

CCCP Backplane
RFDS Cables
CABLE #
FROM
NOTE
TO
3064238A17
RFDS/ASU1
Figure H-16 & Figure H-17
DRDC
3064238A18
RFDS/ASU2
DRDC
3064238A19
RFDS/ASU1
DRDC
3064238A20
RFDS/ASU2
DRDC
ETIB/LPAC Cables
CABLE #
FROM
NOTE
TO
3064794A03
LPAC
See Figure H-8
CCCP Bkpln
3064794A05
ETIB
RFDS
3086433H04
RGPS I/O
ETIB (15 position)
3086169H01
Power, Heat Exchanger,

PDA
ETIB, OPT, HX, EBA
3086500H01
Alm/Ctrl ETIB
HX/PA
H-2
SEP 2009
continued

CABLE #
FROM
NOTE
TO
3086505H01
DC Cable (DC Power Dist)
EBA Blower Assembly
3086566H01
LPAC
1 Cable to each PA Bk Pln
3086569H01
Door Intrusion Alarm
Door Switch
3086655H02
LPAC
See Figure H-8, Figure H-5 &

Figure H-19
ETIB
Figure H-1: 4812ET RF Cabinet Internal FRU Locations

(See Figure H-8,
Figure H-9), and
Figure H-10)
EBA
ETIB
LPAC
SPAN I/O
RFDS
CCCP Shelf
(See Figure H-2
and Figure H-5)
(See Figure H-11,
Figure H-12,
Figure H-13, and
Figure H-14)
OPTIONAL AREA
(See Figure H-10)
Combiner
Cage
DRDC
PAs
CSU
Modem
DC
Power
Dist.
Punch
Block
(back)
LAN
OUT
IN
H
DRDC
A
B
19 MHz
2 Sec
LAN I/O
Span I/O
to CCCP
SEP 2009
SYS
Sync
Alarm to
ETIB
To
Span I/O
(See Figure H-5
& Figure H-10)
FW00698
(See
Figure H-11)
PA Trunking
Backplane
(See Figure H-4,
Figure H-5, Figure H-6 &
Figure H-8)
H-3
continued
CCCP Cables and Cable

Connectors
The C-CCP Shelf assembly consists of the C-CCP Shelf and the attached
backplane with cables and connectors (see Figure H-2 and Figure H-3).
The CCCP shelf contains all of the CDMA unique functions within the
SC 4812ET RF frame. The CCCP shelf contains the following
components:
S
S
S
S
S
S
S
S
S
S
S
S
S
Broadband Transceiver (BBX) cards

MultiChannel CDMA (MCC) cards
Combiner Input/Output (CIO) card
Power Supply cards
Group Line Interface (GLI) cards
Alarm Monitor Reporting (AMR) cards
Clock Synchronization Modules (CSM)
High Stability Oscillator/Low frequency Receiver (HSO/LFR)
Multicoupler Preselector Cards (MPC)
CDMA Clock Distribution (CCD) card
Integrated Frame Modem (IFM) card
Switch card
CCCP Fan Modules
H-4
SEP 2009
continued
Figure H-2: C-CCP Shelf Cable Numbers and Connectors
MPC/EMPC1
BBX26
BBX213
BBX25
BBX24
BBX23
MCC243
MCC242
GLI31
MCC241
AMR1
PS3
BBX22
SPAN B
BBX21
SITE I/O
MCC246
(To SPAN B I/O

connector on the
Bulkhead)
Cable #
3086001H02
SPAN A
PS2
PS1
19 mm Filter Panel
ALARMS
(To J2
connector on
the ETIB)
Cable #
3086000H02
MCC245
(To SPAN A I/O

connector on
the Bulkhead)
Cable #
3086001H02
MCC244
(To J1
connector on
the ETIB)
Cable #
3086086H02
HSO/LFR
Cable #
3086366H02
LAN I/O A
Cable #
3064899A04
Cable #
3064899A04
LAN I/O B
MPC/EMPC2
Switch Card
BBX212
BBX211
BBX210
BBX29
BBX28
BBX27
MCC2412
MCC2411
MCC2410
MCC249
MCC248
MCC247
GLI32
AMR2
FILLER
CCD1
CCD2
CSM2
CSM1
HSO/LFR
CIO
To LAN I/O
connectors on
the Bulkhead
LPAC
CCCP Shelf
FW00699
Cable #
3064794A03
(To the CCCP
connector on the
LPAC Module)
SEP 2009
H-5
continued
Figure H-3: CCCP Backplane

(To J1
connector on
the ETIB)
Cable #
3086086H02
(To SPAN A I/O

connector on
the Bulkhead)
Cable #
3086001H02
(To J2
connector on
the ETIB)
Cable #
3086000H02
(To SPAN B I/O

connector on the
Bulkhead)
Cable #
3086001H02
SYSTEM
LED
Cable #
4886044H01
HSO/LFR
LAN in A
LAN in B
CCCP Power
3064809A01
Cable #
3086366H02
Cable #
3064899A04
Cable #
3064899A04
To LAN I/O
connectors on
the Bulkhead
Cable #
3064794A03
(To the CCCP
connector on the
LPAC Module)
Cable #
LAN out A 3064899A03
LAN out B Cable #
3064899A03
LPAC
GPS
Cable #
3086033H03
FW00700
H-6
SEP 2009
continued
RF Cabinet PA Cables
There can be a maximum of 16 PAs in an RF cabinet. The connections

shown are for one PA backplane which controls four PAs. The remaining
PAs are connected in the same manner. Refer to Figure H-4, through
Figure H-8 for the cables connected to the PAs in the 4812ET RF
cabinet.
Figure H-4: PAs for the SC 4812ET
EBA
ETIB
RFDS
5 RU RACK
SPACE
SC 4812ET BTS RF Cabinet

Note:
PA Component door
not shown for clarity
Unpopulated PA
Shelf Cover
External Blower
Assembly (EBA)
PA Module
(4Each Cage)
FW00173
SEP 2009
H-7
continued
Figure H-5: BTS Combiner to PA Backplane Cables

PA
BACKPLANE
EBA
RFDS
PA1
ETIB
TX
OUT1
5 RU RACK SPACE
CABLE
3064735A10
(3 EACH)
TX
IN 1
TX
OUT2
PA2
TX
IN2
TX
IN 3
PA3
TX
OUT3
SC 4812ET BTS
RF CABINET
PA4
4B
4A
1B
1A
S1
C1
S2
S3
S1
5B
5A
C2
PA1
S2
2B
2A
S3
S1
C3
S2
PA2
S3
6B
6A
3B
3A
S1
C4
S2
S3
FROM APPROPRIATE
PA
PA 1, PA 2,
PA 3, PA 4
PA3
PA4
BACK
H-8
FW00708REF
SEP 2009
continued
Figure H-6: Combiner to PA Backplane/PA Backplane to CIO Board Cables

PA
BACKPLANE 1
EBA
RFDS
PA1
ETIB
TX
OUT1
5 RU RACK SPACE
TX
IN 1
TX
OUT2
CABLE 3064735A10
(3 EACH)
PA2
RED
ORANGE
TX
IN2
YELLOW
TX
IN 3
PA3
TX
OUT3
SC 4812ET BTS
RF CABINET
PA4
4B
4A
1B
1A
S1
C1
S2
S3
S1
5B
5A
TO J15 on CIO Board

(See Figure H-7)
Cable 3064795A05
C2
PA1
S2
2B
2A
S3
S1
C3
TX
OUT1
S2
TX
IN 1
TX
OUT2
S3
6B
6A
3B
3A
S1
C4
PA2
GREEN
VIOLET
TX
IN2
S2
S3
BLUE
TX
IN 3
PA3
TX
OUT3
PA4
FW00711
PA
BACKPLANE 2
SEP 2009
H-9
continued
Figure H-7: Components Located on CIO Card

SC 4812ET RF CABINET
ETIB
EBA
RFDS
5 RU RACK
SPACE
RX EXP A
J12
RX EXP B
J13
TX BTS 16
J15
BTS 712
M/F 16
J14
TX
FW00237
H-10
SEP 2009
continued
LPAC Cabling
The LPAC module provides the communication interface from the ETIB
and CCCP to the PA through the trunking backplane. The LPAC
interface board is contained in a protective housing which is mounted on
the RF cabinet frame behind the ETIB module. See Figure H-3,
Figure H-8 and Figure H-9 for connecting cables and connector
locations.
The LPAC is located internally to the frame as shown in Figure H-1.
Figure H-8: LPAC Interface Board Connectors and Attaching Cable Numbers
LPAC INTERFACE
BOARD
FRONT
PA1
ALARM RIBBON
CABLE TO ETIB
3086655H02
RIBBON CABLE TO
CCCP BACKPLANE
3064794A03
TX
OUT1
PA2
TX IN
1
TX
OUT2
TX
IN2
TX IN 3
PA 1A, 1B 1C, 1D
RIBBON CABLE
3086566H01
PA3
TX
OUT3
PA 2A, 2B 2C, 2D
RIBBON CABLE
3086566H01
PA 3A, 3B 3C, 3D
RIBBON CABLE
3086566H01
PA 4A, 4B 4C, 4D
RIBBON CABLE
3086566H01
PA4
PA BACKPLANE
1, 2, 3, & 4
FW00702
CABLE # 3086566H01
(4 CONNECTIONS EACH SIDE)
NOTE: The LPAC is Located

Behind the ETIB Module
SEP 2009
H-11
continued
ETIB Cables and Cable

Connectors
The ETIB module (see Figure H-9) provides the interface for the PAs
through the LPAC, punchblock, heat exchanger and alarms to the
CCCP backplane. The ETIB interface board is contained in a protective
housing which is mounted on the RF cabinet frame.
The ETIB is located internally to the frame as shown in Figure H-1.
Figure H-9: ETIB I/O Connectors and Attaching Cable Numbers

Cable #
3064794A05
(See Figure H-16)
Cable #
3086168H01
J6
DC POWER
Cable #
3086655H02
(See Figure H-8)
P7
RFDS
P2
LPAC
P9 Alarms In
(from Bulkhead )
Cable #
3064534A08
(See Figure H-1)
J1 to Alarms Out
(CCCP Backplane)
(Reserved)
SITE I/O (CCCP Backplane)

P8 Options
Receptacle
Door Intrusion Alarm
Cable #
3086569H01
Cable #
3086000H02
See Figure 2-6
and Figure H-3
J2
J4
J5
LFR/HSO
Cable #
3086433H04
(See Figure H-1)
Cable #
3086500H01
HEAT EXCH
J3
RGD/RGPS
Cable #
3086366H02
See Figure 2-6
and Figure H-3
H-12
Cable #
3086086H02
See Figure 2-6
and Figure H-3
FW00701
SEP 2009
continued
SPAN I/O Cable Connection

Diagram
The SPAN I/O card provides the frame interface and secondary surge
protection for the T1 lines. There are two span cards in an RF cabinet.
SPAN I/O A supports spans A, C, and E. SPAN I/O B supports span B,
D, and F. See Figure H-10 for SPAN cables and cable connections.
The SPAN I/O is located internally to the frame as shown in Figure H-1.
SEP 2009
H-13
continued
Figure H-10: SPAN I/O Cables and Connectors
20 Pair
RGD
Punchblock Board
(RGPS)
SPAN I/O (A & B)

Interface Module
(Located Behind
the LPAC Module,
See Figure H-1)
4A 5A 6A 4B 5B 6B
Micro
wave
(Alarms/
Spans)
RF Expansion Ports
RF
GPS
IN OUT
A
B
Power Input
27V Ret
4A 5A 6A 4B 5B 6B
19 MHz
Spans
Antennas
Power Input
+27V
LAN
1A 2A 3A 1B 2B 3B
Remote
ASU
RGD/RGPS
50 Pair
Punch
Block
1A 2A 3A 1B 2B 3B
Modem
Alams
2 Sec
GND
Lugs
4812ET Rear Connector Panel

Span I/O Wiring Diagram
SPAN I/O A
SPAN I/O B
CCCP
Backplane
3086001H02
Bulkhead
SPAN I/O A
Bulkhead
SPAN I/O
Connector
3086601H01
CSU
3086601H02
SPAN I/O B
3086001H02
To/From
GLI
To/From
Network
DTE
T1
DDS
SLOT 2
NETWORK
To/From
GLI
To/From
Network
DATA PORT
T1 TERMINAL
DCE
T1
DDS
SLOT 1
DATA PORT
T1 TERMINAL
NETWORK
CONTROL
PORT
GROUP
ADDRESS
CSU Back View
H-14
SHELF
ADDRESS
FW00703
SEP 2009
continued
DRDC/TRDC Cables and Cable

Connections
The DRDC is a Duplexer, RX Filter, and Directional Coupler which

provides the RF interface at the rear of the cabinet. The connections are
the antenna connection (outside rear), transmit into the DRDC TX filter.
Receive out of DRDC (RX filter), and Directional coupler.
The TRDC is a TX filter/RX filter/Directional Coupler that is the same
as the DRDC except the TRDC has two antenna outputs (TX only and
RX only) The TRDC is not available in the 1.9 GHz band.
See Figure H-11, Figure H-12, Figure H-13, and Figure H-14 for the
cable diagram that fits the configuration of your BTS site.
SEP 2009
H-15
continued
Figure H-11: 3 Sector, 2 Carrier BTS Combiner DRDC/TRDC Cable Connection

Dual Bandpass Filters
3 Sector, 2 Carrier Maximum
Add the following

cables for 2nd Carrier
11B 3064735A11 3 Sec
22B 3064735A07 3 Sec
33B 3064735A07 3 Sec
1B
1A
2B
2A
3B
3A
11A 3064735A11 3 Sec

22A 3064735A07 3 Sec
33A 3064735A07 3 Sec
Combiner Cage
3B
2B
1B
3A
2A
1A
H
FW00704
DRDCs
H-16
SEP 2009
continued
Figure H-12: BTS 2 to 1, 3 or 6 Sector Combiner DRDC/TRDC Cable Connection

2 to 1 Combiners
2 Carrier 6 Sector
44A 3064735A12 6 Sec

55A 3064735A11 6 Sec
66A 3064735A07 6 Sec
* For 3 Sector4 Carrier
Connect Combiner 4 to 1B
Combiner 5 to 2B
Combiner 6 to 3B
11A 3064735A11 3/6 Sec

22A 3064735A07 3/6 Sec
33A 3064735A07 3/6 Sec
Combiner Cage
3B
2B
1B
3A
2A
1A
6B
5B
4B
6A
5A
4A
FW00705
DRDCs
SEP 2009
H-17
continued
Figure H-13: BTS Combiner DRDC/TRDC Cable Connection

4 to 1 Combiners
3 Sector
1A
11A 3064735A11 3 Sec

22A 3064735A07 3 Sec
33A 3064735A07 3 Sec
2A
3A
Combiner Cage
3B
2B
1B
3A
2A
1A
6B
5B
4B
6A
5A
4A
H
FW00706
DRDCs
H-18
SEP 2009
continued
Figure H-14: SC 4812ET BTS Combiner DRDC/TRDC Cable Connection

6 Sector 1 or 2 Carrier
4B
11B 3064735A11 6 Sec

22B 3064735A07 6 Sec
33B 3064735A07 6 Sec
4A
1B
1A
5B
5A
2B
2A
6B
6A
3B
3A
11A 3064735A11 6 Sec

22A 3064735A07 6 Sec
33A 3064735A07 6 Sec
44B 3064735A12 6 Sec

55B 3064735A11 6 Sec
66B 3064735A07 6 Sec
44A 3064735A12 6 Sec

55A 3064735A11 6 Sec
66A 3064735A07 6 Sec
Combiner Cage
3B
2B
1B
3A
6B
5B
4B
6A
2A
5A
1A
4A
H
FW00707
DRDCs
SEP 2009
H-19
continued
MPC Functional Description
The MPC card provides (see Figure H-15) low-noise amplification for
all RX path signals. The low noise, high gain design improves frame RX
sensitivity and overcomes the splitting loss in the receive path. DC
voltages are monitored on the RF devices and regulators and are used to
generate hard and soft alarms. The MPC is not redundant at the
cardlevel, but includes dualpath amplifiers which provide softfail
redundancy for all sectors.
MPC to DRDC Cabling
The cables connecting the MPC cards to the DRDCs for a three sector
RF cabinet are shown in Figure H-15. A six sector RF cabinet would
have six more DRDCs and they would be connected to the front of the
MPC cards.
H-20
SEP 2009
continued
Figure H-15: DRDC To CCCP Cage MPC Boards Cable Connections
MPC Boards
SC 4812ET
RF Cabinet
ETIB
EBA
RFDS
5 RU RACK
SPACE
CABLES CONNECT
1A, 2A, 3A TO TOP
MPC BOARD
# 3086659H01
CABLES CONNECT
1B, 2B, 3B TO
BOTTOM MPC BOARD
# 3086659H01
1A 3A: CABLE # 3086659H01

1B 3B: CABLE # 3086659H01
3B
2B
1B
3A
2A
1A
* Use Cable 3086659H02

For Sectors 4 6
DRDC Cage
SEP 2009
FW00710
H-21
continued
RFDS Cabling Details
Figure H-16 shows the components of the RFDS. Table H-2 depicts the
cabling for a 3-Sector Duplexed configuration and Table H-3 depicts the
cabling for a 6-Sector Duplexed configuration. Figure H-17 shows the
connection of the RFDS to the BTS combiners.
Figure H-16: RFDS Component Identification
HANDLE
FWTIC
AMR BUS/POWER
CABLE #
3064794A05 CONNECTOR (LR485)
(See Figure H-9)
ASU2
ASU1
SUBSCRIBER
UNIT ASSEMBLY
MCX CABLE DETAIL
(See Figure H-17)
P2
REFL/ANT PORTS 1
THROUGH 6
(See Figure H-17)
MCX
CONNECTOR
TO ASU
P3
FWD/BTS PORTS
1 THROUGH 6
(See Figure H-17)
SMA CONNECTORS
TO DRDC BTS OR
ANT PORTS
KNURLED
LOCK
SCREWS
CONNECTS to P2 AND
P3 OF ASU1 AND ASU2
FW00217REF
H-22
SEP 2009
continued
Table H-2: SC 4812ET Series 3-Sector Duplexed Directional Coupler to RFDS Cabling Table
DRDC Label
Directional Coupler Port
Cobra RFDS Port
ASU 1 FWD (six pack MCX)

1A BTS
Sector 1 Main BTS
ASU1FWD BTS1
1B BTS
Sector 1 Diversity BTS
ASU1FWD BTS2
2A BTS
Sector 2 Main BTS
ASU1FWD BTS3
2B BTS
ASU1FWD BTS4
3A BTS
Sector 3 Main BTS
ASU1FWD BTS5
3B BTS
ASU1FWD BTS6
ASU 1 REF (six pack MCX)

1A ANT
Sector 1 Main ANT
ASU1REF ANT1
1B ANT
Sector 1 Diversity ANT
ASU1REF ANT2
2A ANT
Sector 2 Main ANT
ASU1REF ANT3
2B ANT
ASU1REF ANT4
3A ANT
Sector 3 Main ANT
ASU1REF ANT5
3B ANT
ASU1REF ANT6
SEP 2009
H-23
continued
Table H-3: SC 4812ET Series 6-Sector Duplexed Directional Coupler to RFDS Cabling Table
DRDC Label
Directional Coupler Port
Cobra RFDS Port

1A BTS
Sector 1 Main BTS
ASU1FWD BTS1
1B BTS
ASU1FWD BTS2
2A BTS
Sector 2 Main BTS
ASU1FWD BTS3
2B BTS
ASU1FWD BTS4
3A BTS
Sector 3 Main BTS
ASU1FWD BTS5
3B BTS
ASU1FWD BTS6

4A BTS
Sector 4 Main BTS
ASU2FWD BTS1
4B BTS
ASU2FWD BTS2
5A BTS
Sector 5 Main BTS
ASU2FWD BTS3
5B BTS
ASU2FWD BTS4
6A BTS
Sector 6 Main BTS
ASU2FWD BTS5
6B BTS
ASU2FWD BTS6

1A ANT
Sector 1 Main ANT
ASU1REF ANT1
1B ANT
ASU1REF ANT2
2A ANT
Sector 2 Main ANT
ASU1REF ANT3
2B ANT
ASU1REF ANT4
3A ANT
Sector 3 Main ANT
ASU1REF ANT5
3B ANT
ASU1REF ANT6
4A ANT
Sector 4 Main ANT
ASU2REF ANT1
4B ANT
ASU2REF ANT2
5A ANT
Sector 5 Main ANT
ASU2REF ANT3
5B ANT
ASU2REF ANT4
6A ANT
Sector 6 Main ANT
ASU2REF ANT5
6B ANT
ASU2REF ANT6
H-24
SEP 2009
continued
Figure H-17: SC 4812ET BTS Combiner DRDC/TRDC RFDS Cable Connection

BTS COUPLED
TO RFDS ASU 1
(See Figure H-16)
ANT COUPLED
TO RFDS ASU 1
(See Figure H-16)
BTS COUPLED
TO RFDS ASU 2
(See Figure H-16)
3B
2B
1B
3A
6B
5B
4B
6A
2A
5A
TO RFDS
ASU1 & ASU2
1A
4A
DRDC CAGE
FW00709
ANT COUPLED
TO RFDS ASU 2
(See Figure H-16)
SEP 2009
H-25
continued
50 Pair Punchblock
The 50 pair punchblock is the main interface point for RGPS, span lines,
customer I/O, Power Cabinet alarm lines, and the modem. The
punchblock provides primary protection for all lines. Refer to
Figure H-18 and Table H-4 for punchblock pinout.
CAUTION
SC4812ET Span Line Labeling for Span B and Span C is
swapped
S On the SC4812ETs, the span cabel internal to the base
station that connects the 50 pin header on the I/O plate
to the CSU has Span B and Span C (RJ45) connectors
mislabeled.
S CFE will punch down the span on the 50 pair
bunchblock as per Motorola documentation and

punchdown chart. When conecting the span input to the
CSU relabel Span B cable toSpan C cable to
Span B. Connect to CSU as per documentation
S Note: The labeling issue on the cable from the I/O plate
to the CSU Part Number 3086601H01 Rev C shall be
corrected on revision D to address this issue. The cut
over date to Rev. D will be approximately January 30,
2001.
CAUTION
A wiring discrepancy exists between the manuals and the
frame for remote GPS.
S The TX and RX are reversed in the ETIB, leading to
inoperability of the RGPS. The RGPS will not work in
either a single standalone or multiple frame
configuration.
S Swap the White and White/Bk wires to punch pins 44T

and 44R. The Green and Green/Bk go to 45T and 45R.
This will correct nonexpansion configurations.
S Single frame and expansion BTSs without RGPS can

use this workaround as a permanent solution.
S For expansion with RGPS required a new cable (P/N

3086433H10 ) will correct the problem.
H-26
SEP 2009
continued
Figure H-18: 50 Pair Punchblock

TO MODEM
CONNECTOR TO ALARMS
CONNECTOR
STRAIN RELIEVE
INCOMING CABLE TO
BRACKET WITH TIE WRAPS
TO SPAN
CONNECTOR
RF CABINET
I/O AREA
TO RGD/RGPS
CONNECTOR
TOP VIEW OF
PUNCH BLOCK
2R
2T
LEGEND
1T = PAIR 1 TIP
1R = PAIR 1 RING
1R
1T
See Table H-4 for

PINOUT.
1
49T
49R
50T
1T 1R 2T 2R
50R
FW00162REF
SEP 2009
H-27
continued
Alarm and Span Line Cable

Pin/Signal Information
Table H-4 lists the complete pin/signal identification for the 50pin
punch block.
Table H-4: PinOut for 50Pair Punchblock
Punchblock
Cable Connector
Function
Power Cabinet
ALARM
HSO/LFR
Extension
LFR Antenna
H
Pilot Beacon
Signal Name
Punch Pin
Ext. Cable Wire

Color
Power Cab Control NC
1T
Blue
Power Cab Control NO
1R
Blk/Blue
Power Cab Control Com
2T
Yellow
Reserved
2R
N/C
Rectifier Fail
3T
Blk/Yellow
AC Fail
3R
Green
Power Cab Exchanger Fail
4T
Blk/Grn
Power Cab Door Alarm
4R
White
Power Cab Major Alarm
5T
Blk/White
Battery Over Temp
5R
Red
Power Cab Minor Alarm
6T
Blk/Red
Reticifier Over Temp
6R
Brown
Power Cab Alarm Rtn
7T
Blk/Brn
LFR_HSO_GND
7R
EXT_1PPS_POS
8T
EXT_1PPS_NEG
8R
CAL_+
9T
CAB_
9R
LORAN_+
10T
LORAN_
10R
Pilot Beacon Alarm Minor
11T
Pilot Beacon Alarm Rtn
11R
Pilot Beacon Alarm Major
12T
Pilot Beacon ControlNO
12R
Pilot Beacon Control COM
13T
Pilot Beacon Control NC
13R
H-28
SEP 2009
continued

Punchblock
Cable Connector
ALARM
Function
Customer Outputs
Signal Name
Punch Pin
14T
14R
14T
14R
15T
15R
16T
16R
17T
17R
18T
18R
Customer Outputs 4COM
19T
19R
Ext. Cable Wire

Color
SEP 2009
H-29
continued

Punchblock
Cable Connector
ALARM
Function
Customer Inputs
Signal Name
Punch Pin
Customer Inputs 1
20T
Cust_Rtn_A_1
20R
Customer Inputs 2
21T
Cust_Rtn_A_2
21R
Customer Inputs 3
22T
Cust_Rtn_A_3
22R
Customer Inputs 4
23T
Cust_Rtn_A_4
23R
Customer Inputs 5
24T
Cust_Rtn_A_5
24R
Customer Inputs 6
25T
Cust_Rtn_A_6
25R
Customer Inputs 7
26T
Cust_Rtn_A_7
26R
Customer Inputs 8
27T
Cust_Rtn_A_8
27R
Customer Inputs 9
28T
Cust_Rtn_A_9
28R
Customer Inputs 10
29T
Cust_Rtn_A_10
29R
Ext. Cable Wire

Color
H-30
SEP 2009
continued

Punchblock
Cable Connector
Function
Span 1
Span 2
Span 3
SPAN I/O
Span 4
Span 5
Span 6
Signal Name
Punch Pin
RCV_TIP_A
30T
RCV_RING_A
30R
XMIT_TIP_A
31T
XMIT_RING_A
31R
RCV_TIP_B
32T
RCV_RING_B
32R
XMIT_TIP_B
33T
XMIT_RING_B
33R
RCV_TIP_C (Note)
34T
RCV_RING_C (Note)
34R
XMIT_TIP_C (Note)
35T
XMIT_RING_C(Note)
35R
RCV_TIP_D (Note)
36T
RCV_RING_D (Note)
36R
XMIT_TIP_D (Note)
37T
XMIT_RING_D(Note)
37R
RCV_TIP_E (Note)
38T
RCV_RING_E (Note)
38R
XMIT_TIP_E (Note)
39T
XMIT_RING_E(Note)
39R
RCV_TIP_F (Note)
40T
RCV_RING_F (Note)
40R
XMIT_TIP_F (Note)
41T
XMIT_RING_F(Note)
41R
Ext. Cable Wire

Color
NOTE
Span 3 through 6 are spares for expansion purposes
SEP 2009
H-31
continued

Punchblock
Cable Connector
Signal Name
Punch Pin
Ext. Cable Wire

Color
GPS_Power_A
42T
Yellow
GPS_Power_A_Return
42R
Yellow/Black
GPS_Power_B
43T
Blue
GPS_Power_B_Return
43R
Blue/Black
GPS_TXD+
44T
White
GPS_TXD
44R
White/Black
GPS_RXD+
45T
Green
GPS_RXD
45R
Green/Black
46T
Red
Signal Ground (TDR)
46R
Red/Black
GPS_1PPS+
47T
Brown
GPS_1PPS
47R
Brown/Black
GPS_Power_A
42T
Yellow
GPS_Power_A_Return
42R
Yellow/Black
GPS_Power_B
43T
Blue
GPS_Power_B_Return
43R
Blue/Black
GPS_TXD+
44T
White
GPS_TXD
44R
White/Black
GPS_RXD+
45T
Green
GPS_RXD
45R
Green/Black
46T
Red
Master Frame (TDR)
46R
Red/Black
GPS_1PPS+
47T
Brown
GPS_1PPS
47R
Brown/Black
Reserved
48T
Reserved
48R
RGD/RGPS
Chassis Ground
49T
N/A
None
No Connection
49R
None
Reserved
50T
None
Reserved
50R
None
RGD/RGPS
RGD/RGPS
Function
MODEM
ALARM
H-32
For frame
without RGD
Expansion
Punchblock
Single
g Frame
BTS;RGPS Head
Connection
OR
Multiple Frame
BTS; RGD
Connection at
RGPS Secondary
Frame
For fframe with

F
ith
RGD Expansion
Punchblock
OR
Multiple Frame
BTS; RGPS Head
Connection at
RGPS Primary
Frame
SEP 2009
continued
RF Cabinet Parts Locator
Figure H-19 illustrates the location of door switch interlocks, DC Power

distribution and the EBA blower assembly.
Figure H-19: SC 4812ET RF Cabinet Parts Locator
1
2
INDEX:
1. Door Switch
2. Door Switch (Main)
3. DC Power Distribution
4. EBA Blower Assembly
FW00440REF
SEP 2009
H-33
continued
Notes
H-34
SEP 2009
Appendix I: Inservice Calibration

Appendix Content
Inservice Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Stabilization and Calibration . . . . . . . . . . . . . . . . . . . . . . . .
1X Test Equipment Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I-1
I-1
I-1
I-1
Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agilent E4406A Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . .
Advantest R3267 Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . .
Agilent 8935 series E6380A Power Delta Calibration . . . . . . . . . . . . .
Advantest R3465 Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . .
I-3
I-3
I-3
I-6
I-9
I-11
InService Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I-14
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Inservice Calibration
Purpose
This procedure is a guide to performing calibration of new BTS

expansion carriers while the system remains in service. This procedure
also supports BTS recalibration following replacement of RF chain
components while the remainder of the site stays in service.
Motorola recommends performing this procedure during a maintenance
window.
This procedure cannot be performed on BTSs with 4to1 combiners.
The procedure can only be performed on one side of the BTS at one
time. That is, PAs 1, 2 ,3, 7, 8, 9 (feed antennas 1, 2, 3) can be calibrated
while PAs 6, 7, 8, 10, 11, 12 (feed antennas 4, 5, 6) remain in service
and vice versa.
Equipment Stabilization and
Calibration
NOTE
calibrating the overall test equipment set. Calibrate the test
equipment after it has been allowed to warm-up and
stabilize for a minimum of 60 minutes.
CAUTION
If any component of the test equipment set (for example, a
test cable, RF adapter, signal generator) has been replaced,
the test equipment set must be recalibrated. Failure to do so
could introduce measurement errors which ultimately
result in degradation of system performance.
1X Test Equipment
Requirements
InService Calibration (ISC) of 1X carrier functions requires using the

following test equipment for the purposes indicated:
S An Advantest R3267 spectrum analyzer to perform TX calibration
S An Advantest R3562 signal generator for R3267 Delta Power
Calibration
S An Agilent E4406A Transmitter Test Set to perform TX calibration
S An Agilent E4432A signal generator for E4406A Delta Power
Calibration
S An Agilent 8935 series E6380A equipped with option 200 (if
purchased new) or option R2K (if retrofitted) to perform TX
calibration
SEP 2009
I-1
continued
The CDMA communications system analyzers listed above are capable

of calibrating the BTS for both IS95 A and B mode operation as well as
CDMA2000 1X operation.
NOTE
IS95A/B communication test sets such as the Advantest
R3561L can not calibrate 1X carrier functions.
Calibration and test setup for the Advantest R3561L test sets is
included only for situations where it is necessary to use this equipment
for calibration of IS95A/B mode operation.
I-2
SEP 2009
Power Delta Calibration

Introduction
The ISC procedure has several differences from a normal calibration

procedure. One of these is the use of a spectrum
analyzer/communications test set instead of a power meter to measure
power. Power meters are broadband measurement devices and cannot be
used to measure power during ISC because other carriers are operating.
A spectrum analyzer can be used because it measures power at a given
frequency. Measuring power using a spectrum analyzer is less accurate
than using a power meter, therefore, compensation is required for the
accuracy difference (delta) between the power meter and the spectrum
analyzer.
Agilent E4406A Power Delta
Calibration
The Agilent E4406A transmitter tester and E4432B signal generator test
equipment combination can be used for ISC of IS2000 CDMA 1X as
well as IS95A/B operation modes. The power delta calibration is
performed on the E4406A, but the E4432B is required to generate the
reference signal used to calculate the power delta offset. After the offset
value has been calculated, add it to the TX cable loss value in the LMF.
Preliminary Agilent Test Equipment Setup
To provide proper operation during power delta calibration, be sure the

E4406A and E4432B are connected as shown in Figure F-14.
Follow the procedure in Table I-1 to perform the Agilent E4406A Power
Delta Calibration procedure.
Table I-1: Agilent E4406A Power Delta Calibration Procedure
Step
Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of 60
minutes. After it is warmed up and stabilized, calibrate the test equipment as described in the Test Set
Calibration section of Appendix F.
1
Zero the Power Meter prior to connecting the power sensor to the RF cable from the signal generator.
NOTE
For best accuracy, always rezero the power meter before connecting the power sensor to the
component being calibrated.
2
Be sure the E4406A and E4432B are connected as shown in Figure F-14.
Connect a short RF cable from the E4432B RF OUTPUT connector the HP437 power meter power
sensor (see Figure I-1).

SEP 2009
I-3
continued

Step
Action
Set the E4432B signal generator as follows:

Press Preset to exit any modes for which the signal generator is configured
Press Frequency and enter the frequency of the channel to be calibrated on the numeric keypad
Using the soft keys to the right of the screen, select the frequency range to be measured; for
example MHz
Press Amplitude and, using the numeric keypad, set signal amplitude to 0 (zero)
Using the soft keys, set the measurement type to dBm
On the E4432B, press RF On/Off to toggle the RF output to RF ON.

Note that the RF On/Off status in the screen display changes.
Measure and record the value reading on the HP437 power meter as result A____________________.
On the E4432B, press RF On/Off to toggle the RF output to RF OFF.

Disconnect the short RF cable from the HP437 power meter power sensor, and connect it to the RF
INPUT connector on the E4406A transmitter tester (see Figure I-2).
NOTE
Do not change the frequency and amplitude settings on the E4432B when performing the following
steps.
Set the E4406A as follows:
Press Preset to exit any modes for which the transmitter tester is configured
Press MODE and, using the soft keys to the right of the screen, select cdmaOne
Press MEASURE and, using the soft keys, select spectrum
Press Frequency and, using the soft keys, select Center Frequency
Enter the frequency of the channel to be calibrated using the numeric keypad
Using the soft keys, select the frequency range to be measured; for example, MHz
Press Input/Output and, using the soft keys, select Input Atten
Using the numeric keypad, set Input Atten to 0 (zero) and, using the soft keys, select dB
Using the soft keys, select External Atten and then select Mobile
Using the numeric keypad, set Mobile to 0 (zero) and, using the soft keys, select dB
Using the soft keys, select Base
Using the numeric keypad, set Base to 0 (zero) and, using the soft keys, select dB
Press MEASURE and, using the soft keys, select Channel Power
10
On the E4432B signal generator, press RF On/Off to toggle the RF output to RF ON.
11
Read the measured Channel Power from the E4406A screen display and record it as
result B____________________.
I-4
SEP 2009
continued

Step
Action
12
On the E4432B, press RF On/Off to toggle the RF output to RF OFF.

13
Calculate the Power Calibration Delta value. The delta value is the power meter measurement minus
the Agilent measurement.
Delta = A B
Example: Delta = 0.70 dBm (1.25 dBm) = 0.55 dBm
Example: Delta = 0.26 dBm 0.55 dBm = 0.29 dBm
These examples are included to show the mathematics and do not represent actual readings.
NOTE
Add this delta value to the TX Cable Loss value during InService Calibration (see step 4 in
Table I-5).
Figure I-1: Delta Calibration Setup Agilent E4432B to HP437

AGILENT E4432B AND E4406A
HP437B
SENSOR
RF OUTPUT
POWER
SENSOR
SHORT RF CABLE
Figure I-2: Delta Calibration Setup Agilent E4432B to Agilent E4406A

AGILENT E4432B AND E4406A
RF OUTPUT
I
SHORT RF CABLE
RF INPUT
SEP 2009
I-5
continued
Advantest R3267 Power Delta

Calibration
The Advantest R3267 spectrum analyzer and R3562 signal generator test
performed on the R3267. After the offset value has been calculated, add
it to the TX cable loss value.
Preliminary Advantest Test Equipment Setup
To provide proper operation during power delta calibration, be sure the

R3267 is connected to the R3562 as shown in Figure F-12.
Follow the procedure in Table I-2 to perform the Advantest R3267
Power Delta Calibration procedure.
Table I-2: Advantest R3267 Power Delta Calibration Procedure
Step
1
Action
NOTE
Warm-up test equipment for a minimum of 60 minutes prior to this procedure. After it is warmed up
and stabilized, calibrate the test equipment as described in the Test Set Calibration section of
Chapter 3.
Be sure the R3267 and R3562 are connected as shown in Figure F-12.
Press the SHIFT and the PRESET keys located on the right side of the control panel.
Press the ADVANCE key in the MEASUREMENT area of the control panel.
On the CRT, select RX Control by pressing ACTIVE key 1.
On the CRT, select Frequency Setup by pressing ACTIVE key 3.
On the CRT, highlight Frequency by adjusting the DISPLAY CONTROL knob.
Press FREQ key in the ENTRY section of the control panel.
Set the frequency to the desired value using the keypad ENTRY section keys.
Press the LEVEL key in the ENTRY section of the control panel.
10
Set the level to 0 dBm using the keypad ENTRY section keys.
11
On the CRT, verify OFF is highlighted in Modulation, if not press the ACTIVE key 5 to toggle it
OFF.
12
On the CRT, verify OFF is highlighted in Output, if not press the ACTIVE key 6 to toggle it OFF.
13
NOTE
I-6
SEP 2009
continued

Step
Action
14
Connect the RF cable from the R3562 signal generator RF OUT port to the power sensor, refer to
Figure I-3.
15
On the R3562 CRT, set the Output to ON by pressing ACTIVE key 6.
16
Record the Power Meter reading as result A________________________
17
On the R3562 CRT, set the Output to OFF by pressing ACTIVE key 6.
18
Connect the RF cable from R3562 signal generator RF OUT port to the R3267 spectrum analyzer
INPUT Port, refer to Figure I-4.
19
On the R3562 CRT, set the Output to ON by pressing ACTIVE key 6.
20
On the R3267, press the POWER key in the MEASUREMENT section of the control panel.
21
Press the LEVEL key in the ENTRY section of the control panel.
22
Set the REF LEVEL to 10 dBm using the keypad ENTRY section keys.
23
On the CRT, select dB/div by pressing ACTIVE key 1.
24
On the CRT, select 10 dB/div by pressing ACTIVE key 1.
25
Press the FREQ key in ENTRY section of the control panel.
26
Set the frequency to the desired value using the keypad ENTRY section keys.
27
On the CRT, select more 1/2 by pressing ACTIVE key 7.
28
Press the Preselector CRT menu key to highlight 3.66G.
29
Press the POWER key in the MEASUREMENT section of the control panel.
30
Press the SPAN key in the ENTRY section of the control panel.
31
On the CRT, select Zero Span by pressing ACTIVE key 2.
32
Press the COUPLE key in the ENTRY section of the control panel.
33
On the CRT, select RBW and highlight MNL by pressing ACTIVE key 3.
34
Set RBW to 30 kHz using keypad ENTRY section keys.
35
On the CRT, select VBW and highlight MNL by pressing ACTIVE key 2.
36
Set VBW to 1 MHz using keypad ENTRY section keys.
37
Press the MKR key in the DISPLAY CONTROL section of the control panel.
38
On the CRT, select Normal Marker by pressing ACTIVE key 1.
39
Record the Marker Level reading as result B________________________
I
SEP 2009
I-7
continued

Step
Action
40
Press Single in ENTRY section of control panel.
41
the Advantest measurement.
Delta = A B
Example: Delta = 0.7 dBm (1.25 dBm) = 0.55 dB
NOTE
Add this delta value to the TX Cable Loss value during InService Calibration (see step 4 in
Table I-5).
Figure I-3: Delta Calibration Setup Advantest R3562 to HP437

ADVANTEST R3562 AND R3267
HP437B
SENSOR
POWER
SENSOR
RF OUT
SHORT RF CABLE
Figure I-4: Delta Calibration Setup Advantest R3562 to R3267

ADVANTEST R3562 AND R3267
RF IN
I
SHORT RF CABLE
RF OUT
I-8
SEP 2009
continued
Agilent 8935 series E6380A

The Agilent 8935 (formerly HP 8935) communications test set modified

with either option 200 or R2K and E4432B signal generator test
performed on the Agilent 8935. After the offset value has been
calculated, add it to the TX cable loss value.
Follow the procedure in Table I-3 to perform the Agilent 8935 Power
Table I-3: Agilent 8935 Power Delta Calibration Procedure
Step
Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of
60 minutes. After it is warmed up and stabilized, calibrate the test equipment as described in the Test Set
Calibration section of Chapter 3.
1
NOTE
2
Connect a short RF cable between the Agilent 8935 Duplex Out port and the HP437 power sensor
(see Figure I-5).
Set the Agilent 8935 signal source as follows:

Measure mode to CDMA Gen
Frequency to the CDMA Calibration target frequency
CW RF Path to IQ
Output Port to Dupl
Data Source to Random
Amplitude to 0 dBm
Measure and record the power value reading on the HP437 Power Meter.
Record the Power Meter reading as result A ________________________.
Turn off the Agilent 8935 signal source output, and disconnect the HP437.
NOTE
Leave the settings on the source Agilent 8935 for convenience in the following steps.
Connect the short RF cable between the Agilent 8935 Duplex Out port and the RFIN/OUT port (see
Figure I-6).
Ensure that the source Agilent 8935 settings are the same as in Step 3.
SEP 2009
I-9
continued
Table I-3: Agilent 8935 Power Delta Calibration Procedure

Step
Action
Set the Agilent 8935 as follows:

Measure mode to CDMA Anl
Frequency to the CDMA calibration target frequency
Input Attenuation to 0 dB
Input port to RFIN
Gain to Auto
Anl Dir to Fwd
10
Turn on the Agilent 8935 signal output.
11
Set the Chn Pwr Cal to Calibrate and select to calibrate.
12
Measure and record the channel power reading on the measuring Agilent 8935 as result
B ________________________.
13
Turn off the Agilent 8935 signal output and disconnect the equipment.
14
Delta = A B
NOTE
Add this delta value to the TX Cable Loss value during InService Calibration (see Step 4 in
Table I-5).
Figure I-5: Delta Calibration Setup Agilent 8935 to HP437
AGILENT AGILENT 8935
HP437B
SENSOR
POWER
SENSOR
DUPLEX OUT
SHORT RF CABLE
FW00805
I-10
SEP 2009
continued
Figure I-6: Delta Calibration Setup Agilent 8935 to Agilent 8935

AGILENT E6380A
DUPLEX OUT
RF IN/OUT
SHORT RF CABLE
FW00806
Advantest R3465 Power Delta

Calibration
Use the Advantest R3465 spectrum analyzer to measure power during

ISC only for IS95A and B operation. After the offset value has been
calculated, add it to the TX cable loss value.
Follow the procedure in Table I-4 to perform the Advantest 3465 Power
Table I-4: Advantest Power Delta Calibration Procedure
Step
Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of
60 minutes. After it is warmed up and stabilized, calibrate the test equipment as described in the Test Set
Calibration section of Chapter 3.
1
Press the SHIFT and the PRESET keys located below the CRT display.
Press the ADVANCE key in the Measurement area of the control panel.
Press the CDMA Sig CRT menu key.
Press the FREQ key in the Entry area of the control panel.
Press the LEVEL key in the Entry area of the control panel.
Set the LEVEL to 0 dBm using the keypad entry keys.
Verify the Mod CRT menu key is highlighting OFF, if not press the Mod key to toggle it OFF.
Verify the Output CRT menu key is highlighting OFF, if not press the Output key to toggle it OFF.
10
NOTE
11
Connect the RF cable from the R3561L CDMA signal generator RF OUT port to the power sensor,
refer to Figure I-7.
SEP 2009
I-11
continued

Step
Action
12
Press the Output CRT menu key to toggle the Output to ON.
13
Record the Power Meter reading as result A________________________.
14
Press the Output CRT menu key to toggle the Output to OFF.
15
Connect the RF cable from the R3561L signal generator RF OUT port to the R3465 INPUT Port,
refer to Figure I-8.
16
Press the Output CRT menu key to change the Output to ON.
17
Press the CW key in the Measurement area of the control panel.
18
Press the LEVEL key in the Entry area of the control panel.
19
Set the REF LEVEL to 10 dBm using the keypad entry keys.
20
Press the dB/div CRT menu key.
21
Press the 10 dB/div CRT menu key.
22
Press the FREQ key in Entry area of the control panel.
23
24
Press the more 1/2 CRT menu key.
25
Press the Preselector CRT menu key to highlight 3.0G.
26
Press the FORMAT key in the Display Control area of the control panel.
27
Press the TRACE CRT menu key.
28
Press the AVG A CRT menu key.
29
Set AVG to 20 using keypad entry keys.
30
Press the return CRT menu key.
31
Press the SPAN key in the Entry area of the control panel.
32
Press the Zero Span CRT menu key.
33
Press the BW key in the Entry area of the control panel.
34
Press the RBW CRT menu key to highlight MNL. using keypad entry keys enter 30 kHz.
35
Set RBW to 30 kHz using keypad entry keys.
36
Press the VBW CRT menu key to highlight MNL.
37
Set VBW to 1 MHz using keypad entry keys.
38
Press the Marker ON key in the Display Control area of the control panel.
39
Record the Marker Level reading as result B________________________.

I-12
SEP 2009
continued

Step
Action
40
Delta = A B
NOTE
Add this delta value to the TX Cable Loss value during InService Calibration (see Step 4 in
Table I-5).
Figure I-7: Delta Calibration Setup R3561L to HP437

ADVANTEST
R3561L
POWER
SENSOR
RF OUT
HP437B
SHORT RF CABLE
SENSOR
FW00803
Figure I-8: Delta Calibration Setup R3561L to R3465

RF OUT
R3561L
SHORT RF CABLE
R3465
INPUT
FW00804
SEP 2009
I-13
InService Calibration
CAUTION
(caution:normal) Type the caution statement here.
This feature does NOT have fault tolerance at this time.
The system has no safeguards to prevent actions which
will put the BTS out of service. If possible, perform this
procedure during a maintenance window.
Follow the procedures in this section precisely, otherwise
the entire BTS will most likely go OUT OF SERVICE.
At the CBSC, only perform operations on expansion
hardware when it is in the OOS_MANUAL state.
The operator must be trained in the LMF operation prior to
performing this procedure.
Prerequisites
S Any applicable expansion hardware has been added in the CBSC
database, and a CDF which includes the additions has been generated.
S Any expansion devices have been inserted into the SCCP cage and are
in the OOS_MANUAL state at the CBSC MM.
S The site specific CDF (with any expansion hardware) and CAL files
have been loaded onto the LMF.
S The LMF has the same device binary code and dds files as the CBSC.
CAUTION
Do not download code or data to any cards other than those
being worked on. Downloading code or data to other cards
will take the site OUT OF SERVICE.
The code file version numbers must match the current BSS
software release version numbers required for the equipped
devices. If the numbers do not match, the site may go OUT
OF SERVICE.
It is mandatory that the bts#.cdf (or bts#.necf) and
cbsc#.cdf files on the LMF computer for this BTS are
copies of the corresponding files created in the CBSC
database (see Table 3-2).
The CAL file loaded on the LMF computer for this BTS
must have come from the CBSC.
I-14
SEP 2009
continued
S Test equipment has been connected as shown in Figure I-9 or

Figure I-10.
S An RFDS (or as a minimum, a directional coupler), whose loss is
already known, must be in the applicable TX antenna path to perform

the inservice calibration.
S Test equipment has been calibrated after a 60minute warm up.

S A short RF cable and two BNCN adapters are available to perform
Cable Calibration.
S NSMA cable adapters are available to connect to TRDC or DRDC
BTS CPLD connectors, and are included in cable loss measurements.
S The Power Delta Calibration has been performed (see Table I-1,
Table I-2, Table I-3, or Table I-4).
SEP 2009
I-15
continued
Figure I-9: TX Calibration Test Setup Agilent E4406A, Advantest R3267, and Agilent 8935
with Option 200 or R2K (IS95A/B and 1X CDMA 2000)
TEST SETS
AGILENT E4406A
NOTE: IF BTS IS EQUIPPED

WITH DRDCS (DUPLEXED
RX/TX SIGNALS), CONNECT
THE TX TEST CABLE TO
THE DRDC BTS CPLD
CONNECTOR.
COMMUNICATIONS
SYSTEM ANALYZER
GPIB
RF INPUT 50,
INPUT 50,
OR RF IN/OUT
GPIB CONNECTS
TO BACK OF UNIT
RF INPUT
50
ADVANTEST R3267
ANTENNA
ANTENNA
TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
GPIB
CABLE
TRDC
RX
RX
BTS ANT
CPLD CPLD
GPIB CONNECTS
TO BACK OF UNIT
2O DB
INLINE
ATTENUATOR
INPUT 50
AGILENT 8935 SERIES E6380A

(FORMERLY HP 8935)
HPIB
TO GPIB
BOX
BTS
S MODE
DATA FORMAT
BAUD RATE
GPIB ADRS
TO LPA
TRUNKING
MODULE
G MODE
RS232GPIB
INTERFACE BOX
FREQ
MONITOR
LAN
B
RS232 NULL
MODEM
CABLE
SYNC
MONITOR
CSM
10BASET/
10BASE2
CONVERTER

NOTE:
DIP SWITCH SETTINGS
INTERNAL
TX
CABLE
TO
MPC
RF IN/OUT
* BLACK RECTANGLES
PART OF SWITCHES
ON
INTERNAL
RX
CABLE
LAN
A
TX
TX
BTS ANT
CPLD CPLD
CDMA
LMF
INTERNAL PCMCIA
ETHERNET CARD
THE AGILENT 8935 MUST BE EQUIPPED WITH OPTION 200 OR R2K

TO PERFORM 1X TX TESTING .
I-16
SEP 2009
continued
Figure I-10: TX Calibration Test Setup Advantest R3465 (IS95A/B only)
TEST SETS

NOTE: IF BTS IS EQUIPPED
WITH DRDCS (DUPLEXED
RX/TX SIGNALS), CONNECT
THE TX TEST CABLE TO
THE DRDC BTS CPLD
CONNECTOR.
GPIB CONNECTS
TO BACK OF UNIT
COMMUNICATIONS
SYSTEM ANALYZER
GPIB
INPUT 50
INPUT 50
ANTENNA
ANTENNA
TX
ANTENNA
CONNECTOR
RX
ANTENNA
CONNECTOR
GPIB
CABLE
TRDC
RX
RX
BTS ANT
CPLD CPLD
TX
TX
BTS ANT
CPLD CPLD
2O DB
INLINE
ATTENUATOR
S MODE
DATA FORMAT
BAUD RATE
INTERNAL
TX
CABLE
TO
MPC
BTS
GPIB ADRS
TO LPA
TRUNKING
MODULE
G MODE
RS232GPIB
INTERFACE BOX
FREQ
MONITOR
LAN
B
RS232 NULL
MODEM
CABLE
SYNC
MONITOR
CSM
10BASET/
10BASE2
CONVERTER

SEP 2009
DIP SWITCH SETTINGS
ON
INTERNAL
RX
CABLE
LAN
A
* BLACK RECTANGLES
PART OF SWITCHES
CDMA
LMF
INTERNAL PCMCIA
ETHERNET CARD
I-17
continued
Follow the procedure in Table I-5 to perform the InService Calibration.

Table I-5: InService Calibration
Step
Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of 60
minutes.
1
Set up the LMF for InService Calibration:

Start the LMF by doubleclicking the LMF icon on the Windows desktop.
Click Tools > Options from the menu bar at the LMF application window.
In the LMF Options window, check only the applicable communications system analyzer check
box on the Test Equipment tab.
Ensure that the GPIB address is 18.
Uncheck any other other equipment that is selected.
Click the Apply button.
Select the BTS Options tab in the LMF Options window.
Check the InService Calibration check box.
Click the Apply button.
Click the Dismiss button to close the LMF Option window.
Log into the target BTS:

Select the target BTS icon.
Click the Login button at the login screen.
Measure the Cable Loss using the Cable Calibration function:

Click Util > Cable Calibration... in the BTS menu bar at the main window.
Set the desired channel(s) and select TX and RX CABLE CAL from the Cable Calibration
window dropdown list.
Click the OK button to perform cable calibration.
Follow the onscreen instructions to complete the cable loss measurement.
NOTE
The measured value is input automatically to the cable loss file.
To view the cable loss file, click Util > Examine > Cable Loss from the BTS menu bar.
I-18
SEP 2009
continued

Step
4
Action
Add the communications system analyzer power delta to the TX Cable Loss.
In the BTS menu bar, click Util > Edit > Cable Loss... > TX.
Add the value computed in Table I-4 or Table I-3 to the TX Cable Loss.
NOTE
Be sure to include the sign of the value. The following examples are included to show the mathematics
and do not represent actual readings:
Example: 5.65 dBm + 0.55 dBm = 6.20 dBm
Example: 5.65 dBm + (0.29 dBm) = 5.36 dBm
Example: 5.65 dBm + 0.55 dBm = 5.10 dBm
Example: 5.65 dBm + (0.29 dBm) = 5.94 dBm
5
Input the Coupler Loss for the TX tests:

In the BTS menu bar, click Util > Edit > Coupler Loss... from the menu bar at the main window.
Select the TX Coupler Loss tab if not in the foreground.
Enter the appropriate coupler loss for the target carrier(s) by referring to the information taken at
the time of BTS installation.
Click the Save button.
Click the Dismiss button to close the window.
To view the coupler loss file, click Util > Examine > Coupler Loss in the BTS menu bar.
Input the Coupler Loss for the RX tests:

In the BTS menu bar, click Util > Edit > Coupler Loss... from the menu bar at the main window.
Select the RX Coupler Loss tab if not in the foreground.
Enter the appropriate coupler loss for the target carrier(s) by referring to the information taken at
the time of BTS installation.
Click the Save button.
Click the Dismiss button to close the window.
To view the couper loss file, click Util > Examine > Coupler Loss in the BTS menu bar.
If it was not previously done, have the CBSC operator put the redundant BBX OOS_MANUAL.
SEP 2009
I-19
continued

Step
8
Action
! CAUTION
Be sure to download OOS devices only. Loading inservice devices takes them OUT OF SERVICE
and can result in dropped calls.
The code file version numbers must match the version numbers on the other cards in the frame. If the
numbers do not match, the site may go OUT OF SERVICE.
NOTE
Be sure to include the redundant BBX in steps 8, 9, and 10.
Download code and data to the target devices:
In the LMF window menu bar, click Tools > Update NextLoad > CDMA to set the code version
that will be downloaded.
Check the appropriate code version in the popup window and click the Save button to close.
Select the target BBX(s) on the SCCP cage picture.
In the BTS menu bar, click Device > Download > Code/Data to start downloading code and data.
9
! CAUTION
Perform the All Cal/Audit procedure on OOS devices only.
Run the All Cal/Audit procedure:
Select the target BBX(s) on the SCCP cage picture.
In the BTS menu bar, click Tests > All Cal/Audit... from the menu bar at the main window.
Select the target carrier and confirm the channel number in the pop up window.
Leave the Verify BLO check box checked.
Be sure the Test Pattern box shows Pilot.
Click the OK button to start calibration.
Follow the onscreen instructions, except, do not connect to the BTS antenna port. Connect to the
DRDC or TRDC BTS CPL port associated with the onscreen prompted antenna port.
10
Save the result, and download the BLO data to the target BBX(s):
Click the Save Result button on the result screen.
The window closes automatically.
11
Logout from the BTS and close the LMF session:

In the BTS menu bar, click Select > Logout to close the BTS connection.
Close the LMF application program by selecting File > Exit from the window menu bar.
12
Disconnect all test cables from the BTS, and reconnect RFDS cables or termination loads, as
applicable, to the DRDC or TRDC BTS CPL ports used for the calibration.
13
Advise the CBSC to enable the target device(s).
14
Restore the new bts*.cal file to the OMCR (refer to Table 6-1).
I-20
SEP 2009
Appendix J: Companion Frame Optimization

Appendix Content
Optimizing the Companion Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Optimizing the TX section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optimizing the RX section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J-1
J-1
J-1
J
SEP 2009
Table of Contents
continued
Notes
J
SEP 2009
Optimizing the Companion Frame

Optimizing the TX section
The optimization/ATP procedure for the transmit side of the Companion

Frame is identical to that of the SC4812ET BTS standalone frame.
Refer to the TX BLO Calibration section in Chapter 3 of this manual for
step-by-step TX Optimization/ATP instructions.
Optimizing the RX section
Main Table J-1 describes testing of the RX Main antenna system.

Table J-1: Optimizing the RX (Main) section of the Companion Frame
n Step
Action
Connect the RX test cables to the antenna ports 1A3A (for 3sector optimization) or antenna
ports 1A6A (for 6sector optimization).
Login the LMF and select MPC (see Figure J-2 for display screen and field location).
Run the RX tests.
RX Diversity (Single Frame) Table J-2 describes testing of the RX

Diversity antenna system on a single frame.
Table J-2: Optimizing the RX (Diversity) on a Single Frame
n Step
Action
Connect the RX test cables to the expansion ports on the I/O plates labeled 1B3B (for 3sector
optimization) or expansion ports 1B6B (for 6sector optimization).
Login the LMF under EMPC (see Figure J-2 for display screen and field location).
Run the RX tests.
J
SEP 2009
J-1
continued
RX Diversity (Two Frame) Table J-3 describes testing of the RX

Diversity antenna configuration on a two frame Companion BTS system.
Table J-3: Optimizing the RX (Diversity) on a Two Frame Companion Site
n Step
1
Action
Connect RX expansion cables from the expansion ports on the other Companion frame labeled
1A3A (for 3sector optimization) or expansion ports 1A6A (for 6sector optimization) to the
1B3B (for 3sector optimization) or expansion ports 1B6B (for 6sector optimization) see
Figure J-1 for an illustration of the configuration.
NOTE
Connect the cables from the 2nd frame A ports to the B ports of the 1st frame.
2
Login using the LMF select MPC (see Figure J-2 for field location on LMF display screen)
NOTE
S Although the test will be done to one frame, the RX cable will be connected to the other frames
corresponding antenna ports.
S The other frame has to be powered up and include all the RX Path Components.
Figure J-1: Cabling of SC 4812ET Companion BTS to SC 4812ET Companion BTS (3 Sector)

RX EXPANSION
RX
Ant1A
C1
TX1
C3
RX1A
RX
Ant2A
C1
TX2
C3
RX2A
RX
C1
TX3
Ant3A
C3
RX3A
RX1A
RX2A
RX3A
MPCA
EMPCB
C2
C6
C4
C8
C2
C6
C4
C8
C2
C6
C4
C8
1A
2A
3A
1A
2A
3A
1B
2B
3B
3B
SC4812ET COMPANION
(STARTER)
J-2
RX
C5
Ant2A
TX2
C7
RX2A
RX
C5
TX3
C7
Ant3A
RX3A
MPCA
RX1A
RX2A
RX3A
EMPCB
SC4812ET COMPANION
SURGE
ARRESTORS
RX1A
1B
2B
Ant1A
TX1
C7
RX
C5
FW00407
SEP 2009
continued
Figure J-2: WinLMF Display Screen
J
SEP 2009
J-3
continued
Notes
J
J-4
SEP 2009
Appendix K: BTS Router Initial Configuration

Appendix Content
SEP 2009
BTS Router Configuration Operations Introduction . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-1
K-1
K-1
Terminal Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-2
K-2
K-2
Establishing a BTS Router Communication Session . . . . . . . . . . . . . . . . . . . . .

BTS Router Serial Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-5
K-5
Obtain BTS Router Minimum (Canned) Configuration Files from

the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Obtaining BTS Router Minimum (Canned) Configuration Files . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FTP File Transfer from the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-8
K-8
K-8
K-9
BTS Router IOS Version Verification and Canned Configuration

File Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using a TFTP Server to Copy Files to CF Memory Card . . . . . . . . . . .
K-15
K-15
K-17
Change or Upgrade BTS Router IOS Version . . . . . . . . . . . . . . . . . . . . . . . . . .

Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment and Software Required . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrade/Replace Installed IOS Version and Verify File
Sequence Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-35
K-35
K-35
K-36
Verify and Upgrade ROMmon Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verification and Upgrade/Replacement of Installed
ROMmon Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-47
K-47
K-47
K-48
K-48
Recovery from BTS Router Boot to ROMmon . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simple Recovery from Boot to ROMmon . . . . . . . . . . . . . . . . . . . . . . .
Extended Recovery from Boot to ROMmon . . . . . . . . . . . . . . . . . . . . .
K-57
K-57
K-57
K-67
Entering or Changing BTS Router FE Interface IP Addresses . . . . . . . . . . . . . .

FE Interface IP Addresses and Operating Parameters . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering or Changing FE Interface IP Addresses . . . . . . . . . . . . . . . . .
K-72
K-72
K-72
K-72
K-36
Table of Contents
continued
Example BTS Router Canned Configuration Files . . . . . . . . . . . . . . . . . . . . . .

BTS Router Canned Configuration File . . . . . . . . . . . . . . . . . . . . . . . .
Obtaining the Latest Configuration File Content . . . . . . . . . . . . . . . . .
Configuration File Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Blue BTS Router Canned Configuration . . . . . . . . . . . . . . . . . . . . . .
Red BTS Router Canned Configuration . . . . . . . . . . . . . . . . . . . . . .
K-77
K-77
K-77
K-77
K-78
K-81
Network Interface Card (NIC) Configuration Worksheet . . . . . . . . . . . . . . . . . .

Record of original NIC configuration . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS router communication NIC configuration . . . . . . . . . . . . . . . . . . .
K-84
K-84
K-84
External BTS Router Compact Flash (CF) Memory Card Installation

and Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CF Memory Card Installation/Removal Operations . . . . . . . . . . . . . . .
Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS Router CF Memory Card Removal and Installation . . . . . . . . . . .
K-85
K-85
K-85
K-86
SEP 2009
BTS Router Configuration Operations Introduction
BTS Router Configuration Operations Introduction

Overview
This appendix contains information and operations related to loading an

external BTS router with the minimum standard (canned) configuration
necessary for network communications. Once the router is
communicating on the network, the full, sitespecific, operational
configuration can be downloaded to the router over the network. This
appendix includes sections on:
S Setting up communications with a router using a Microsoftr

Windowsrbased computer
S Downloading BTS router canned configuration files from the OMCR

S Transferring the canned configuration files from the Windowsbased
computer to the BTS router
S Verifying and, if necessary, replacing/upgrading the IOS version

loaded on the CF memory card
S Verifying and, if necessary, replacing/upgrading the ROM monitor

lowlevel operating system version loaded in the BTS router
S Recovery from BTS router initialization with the ROM monitor
lowlevel operating system and troubleshooting to locate and correct

the cause
S Changing the router FE interface IP addresses if necessary to support

FE verification
S Sample listings of the BTS router canned configuration files

Application
Unless otherwise noted, the procedures and information in this appendix

apply to both the MWR 190027 and MWR 1941DC models of the
external BTS router.
SEP 2009
K-1
Terminal Setup
Terminal Setup
Creating a Terminal Session
General Confirming or changing the configuration data of External

BTS Routers (EBR) an certian BTS Field Replaceable Units (FRU)
requires establishing a ManMachine Interface (MMI) communication
session between a laptop computer and the FRU or EBR. Using features
of the Windows operating system, the connection properties for an MMI
session can be saved on the laptop computer as a named HyperTerminal
connection. This elminiates the need for setting up connection
parameters each time an MMI session is required to support operations.
Desktop Shortcut Once the named connection is saved, a shortcut for
it can be created on the Windows operating system desktop. Double
clicking the shortcut icon will start the connection without the need to
negotiate multiple menu levels.
Terminal Settings
Perform the following to create a named HyperTerminal connection for

FRU or EBR MMI interface and generate a Windows operating system
desktop shortcut for it.
NOTE
There are differences between the Windows 2000 and
Windows XT operating systems in the menus and screens
used for creating a HyperTerminal connection. In the
following procedure, items applicable only to:
Win2000)
S Windows XT operating system will be identified with

WinXT
K-2
SEP 2009
Terminal Setup
continued
Table K-1: Establish HyperTerminal Connection

Step
Action
From the Windows operating system Start menu, select:

Programs > Accessories
S For Win2000, select Hyperterminal and then click on HyperTerminal

S For WinXT, select Communications and then click on the HyperTerminal icon.
NOTE
S If a Location Information Window appears, enter the required information, then click on the
Close button. (This is required the first time a HyperTerminal connection is configured, even if a
modem is not to be used.)
S If a You need to install a modem..... message appears, click on NO.

3
When the Connection Description box opens:

Type a name for the connection being defined (for example, BTSRTR Session, MMI) in the
Name: window,
Highlight any icon preferred for the named connection in the Icon: chooser window, and
Click OK.
From the Connect using: pick list in the Connect To box displayed, select the RS232 port to be
used for the connection (e.g., COM1 or COM2), and click OK.
In the Port Settings tab of the COM# Properties window displayed, configure the RS232 port
settings as follows:
S
S
S
S
S
Bits per second: 9600

Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Click OK.
With the HyperTerminal window still open and the connection running, select:
File > Properties
Click the Settings tab, click the arrow in the Emulation window, and select VT100 from the
dropdown list.
Click the ASCII Setup button, uncheck all boxes in the ASCII Setup window which appears, and
click OK.
10
Click OK for the connection Properties box.
11
Save the defined connection by selecting:

File > Save
SEP 2009
K-3
Terminal Setup
continued
Table K-1: Establish HyperTerminal Connection

Step
Action
12
Close the HyperTerminal window by selecting:

File > Exit
13
Click the Yes button to disconnect when prompted.
14
From the Windows operating system Start menu, select Programs > Accessories
15
S For Win2000, select Hyperterminal and release any pressed mouse buttons.
S For WinXT, select Communications and double click the Hyperterminal folder.
16
Move the cursor over the newlycreated connection icon.
17
Right click and drag the connection icon to the Windows operating system desktop and release the
right mouse button.
18
From the popup menu displayed, select one of the following depending on the operating system used:
S Win2000: Create Shortcut(s) Here

S Winxp: Copy Here
19
If desired, reposition the shortcut icon for the new connection by dragging it to another location on the
Windows operating system desktop.
NOTE
The shortcut icon can now be doubleclicked to open a BTS router or BTS card/module MMI
HyperTerminal session without the need to negotiate multiple menu levels.
20
In WinXT, select File > Close to close the HyperTerminal window.
K-4
SEP 2009
Establishing a BTS Router Communication Session

BTS Router Serial
Communication
For those procedures which require serial communication with BTS

routers, follow the procedures in Table K-2 to initiate the communication
session. This procedure calls out the LMF computer platform, but any
VT100equivalent terminal or computer equipped with terminal
emulation software and a hardware serial connector may be used.
Required Items
The following items are required to perform the verification:
S LMF computer platform or equivalent

S Eightconductor (fourpair, unshielded twisted pair is acceptable)
rollover cable, two 8contact modular plugs (see Figure K-1 for cable
wiring requirements)
S Adapter, DB9 plugto8contact modular plug, Global Computer

Supplies C4717 or equivalent (see Figure K-2 for adapter wiring
requirements)
Figure K-1: Wiring Diagram, BTS Router Communication
Rollover Cable
8contact Plug
Contact Numbering
(Insertion End)
8 76543 21
Locking
Clip
SEP 2009
8contact
Modular
Plug
8contact
Modular
Plug
K-5
continued
Figure K-2: Wiring Diagram, DB9 Plugto8contact Modular Plug Adapter
Adapter
DB9 Receptacle
Socket Numbering
(Mating Side)
5
4 3 2 1
DB9
Receptacle
8contact
Modular
Receptacle
NC
Adapter
8contact Receptacle
Contact Numbering
(Mating Side)
12 34567 8
5
4
8 7 6
NC
Table K-2: Establishing BTS Router Serial Communication

Step
Action
If it has not been done, start the computer and allow it to complete bootup.
If a named HyperTerminal connection for BTS router serial communication or BTS card/module MMI
communication has not been created on the LMF computer, create one as described in Table K-1 in the
Terminal Setup section of this appendix.
Connect the computer to the BTS router as shown in Figure K-3.
Start the named HyperTerminal connection for BTS router communication sessions by double clicking
on its Windows desktop shortcut.
NOTE
If a Windows desktop shortcut was not created for the communication session, access the connection
from the Windows Start menu by selecting:
Programs > Accessories > Hyperterminal > HyperTerminal > <Named HyperTerminal
Connection (for example, BTSRTR)>
5
K-6
Once the connection window opens, establish communication with the BTS router by pressing the
computer Enter key until the prompt identified in the applicable procedure is obtained.
SEP 2009
continued
Figure K-3: LMF Computer Connections to BTS Router
ROLLOVER
CABLE
TO BTS ROUTER
CONSOLE
RECEPTACLE
DB9TORJ48C
ADAPTER
LMF COMPUTER
OR EQUIVALENT
COM1
OR
COM2
OPTOATP00010
SEP 2009
K-7
Obtain BTS Router Minimum (Canned) Configuration Files from the

OMCR
Obtain BTS Router Minimum (Canned) Configuration Files from the
OMCR
Obtaining BTS Router
Minimum (Canned)
Configuration Files
After they are generated on the OMCR, the BTS router canned
configuration files must be transferred to another computer platform
from which they can be installed into the BTS routers. A number of
procedures may be used to move the canned configuration files from the
OMCR to a platform from which they can be loaded into the routers.
Some alternatives are:
1. If a floppy diskette drive is available at the OMCR, such as the one
for UNO workstations, the configuration files can be transferred to
an LMF computer or similar machine using the NEC file transfer
procedure in the Preparing the LMF section of the optimization/ATP
manual. Directories identified in Table K-3 must be used rather than
those in the NEC file transfer procedure.
2. If a Windows operating systembased server connection is available
in the operators network and it can provide an FTP or telnet
connection to the OMCR, files may be transferred by either the
FTP or telnet methods.
3. If a dialup connection is available for accessing the OMCR, an
FTP or telnet session may be possible to transfer files to the
computer used to load the CF memory cards.
The procedure provided in this section covers FTP transfer using a
Windows operating systembased server in the operators network.
Coordinate with the local network administrator to determine the method
and procedure to use on a specific network.
Prerequisites
The following must be obtained from the local network administrator

before performing the canned configuration file FTP procedure in
Table K-3:
S User ID and password to log onto the OMCR

S Name of the subdirectory where the specific BTS router group
canned configuration files to be downloaded were created
K-8
SEP 2009
Obtain BTS Router Minimum (Canned) Configuration Files from the OMCR
continued
FTP File Transfer from the
OMCR
This procedure uses the Windows operating systembased LMF

computer platform to download BTS router canned configuration files
from the OMCR. Follow the procedure in Table K-3.
Table K-3: BTS Router Canned Configuration File FTP Transfer from the OMCR
Step
Action
If it has not been done, create a directory on the LMF computer where the BTS router canned
configuration files will be stored.
If it has not been done, obtain the OMCR logon user ID and password from the local network
administrator.
Connect the LMF computer to the local network and log on.
NOTE
This procedure uses the command line FTP client supplied with the Windows XP and Windows 2000
operating systems; however, any commercially available FTP client application can be used. Follow
the manufacturers instructions for operation of an alternative application.
Open a command line (MS DOS) window by clicking on Start > Programs > Command Prompt.
When the command line window opens, change to the directory where the canned configuration files
will be stored on the LMF computer by entering:
cd pathname
Where pathname = the path to the required directory

C:\> cd Can_Cfg
C:\Can_Cfg>
SEP 2009
K-9
continued
Step
6
Action
Check the contents of the directory by entering the following:
dir

C:\Can_Cfg>dir
Volume in drive C is MAIN
Volume Serial Number is F2AA1721
Directory of C:\Can_Cfg>
08/22/2002
08/22/2002
08/22/2002
08/22/2002
03:46p
<DIR>
.
03:46p
<DIR>
..
03:46p
2,223 btsrtr_canned.blue
03:47p
2,223 btsrtr_canned.red
2 File(s)
4,644 bytes
2 Dir(s)
2,556,045,312 bytes free
C:\Can_Cfg>
If either or both of the following files are found in the directory, delete them or move them to another
directory:
S btsrtr_canned.blue
S btsrtr_canned.red
8
Begin the FTP session by entering the following:

ftp hostname
Where hostname = the OMCR hostname or IP address

C:\Can_Cfg> ftp OMCR1
C:\Can_Cfg>
Connected to OMCR1.
220 OMCR1 FTP server (SunOS 5.6) ready.
User (OMCR1:(none)):
K-10
SEP 2009
continued
Step
9
Action
Enter the User ID and password when prompted, pressing the Enter key after each.
User (OMCR1:(none)): scadm
331 Password required for scadm.
Password:
230 User scadm logged in.
ftp>
10
Change to the directory where the BTS router canned configuration file subdirectories are created and
verify the present working directory by entering the following, pressing the Enter key after each:
cd /home/scadm/btsrtr_canned_configs
pwd

ftp> cd /home/scadm/btsrtr_canned_configs
240 CWD command successful.
ftp> pwd
245 /home/scadm/btsrtr_canned_configs is current directory.
11
Enter the following to list the contents of the directory and be sure the specific canned configuration
directory name provided by the administrator exists:
ls

ftp> ls
200 PORT command successful.
150 ASCII data connection for /bin/ls (10.182.29.117,80) (0 bytes).
Mon_Jul_2_01:55:07_CDT_2002
Wed_Jul_24_09:35:41_CDT_2002
Tue_Aug_04_10:35:22_CDT_2002
226 ASCII Transfer complete.
ftp: 30 bytes received in 0.02Seconds 1.50Kbytes/sec.
ftp>
NOTE
Directory names where canned configuration files are located will consist of the
weekday_month_day_time_year when the canned configuration files were created on the OMCR.
SEP 2009
K-11
continued
Step
12
Action
Change to the directory specified for the BTS router group to be configured and list the directory
contents by entering the following, pressing the Enter key after each command:
cd weekday_month_day_time_year
ls

ftp> cd Wed_Jul_24_09:35:41_CDT_2002
250 CWD command successful.
ftp> ls
150 ASCII data connection for /bin/ls (10.182.29.117,80) (0 bytes).
btsrtr_canned.blue
btsrtr_canned.red
226 ASCII Transfer complete.
ftp>
13
Change to the binary transfer mode and, if desired, turn on hash mark printing for transfer progress by
entering the following, pressing the Enter key after each command:
bin
hash

ftp> bin
200 Type set to I.
ftp> hash
Hash mark printing On
ftp>
ftp: (2048 bytes/hash mark) .
K-12
SEP 2009
continued
Step
Action
14
Download the BTS router canned configuration files to the LMF computer by performing the following:
1. Enter the following to download the first canned configuration file:
get btsrtr_canned.blue

ftp> get btsrtr_canned.blue
150 Binary data connection for btsrtr_canned.blue (10.182.29.117,80)
(2223 bytes).
#
226 Binary Transfer complete.
ftp>
2. Enter the following to download the second BTS router canned configuration file:
get btsrtr_canned.red

ftp> get btsrtr_canned.red
150 Binary data connection for btsrtr_canned.red (10.182.29.117,80) (2223
bytes).
#
226 Binary Transfer complete.
ftp>
15
Before terminating the FTP session, open the Windows operating system Explorer (Explorer)
application and view the contents of the directory where the canned configuration files are to be stored
to be sure the files are present. Perform the following:
1. Click Start > Programs > Windows Explorer
2. In the lefthand pane of Explorer, expand the user profile and directory display for the drive where
the canned configuration file storage directory is located by clicking on the + next to each icon,
respectively.
3. Expand any subdirectories as required to display the directory folder where the canned
configuration files are to be stored.
4. Click on the directory folder icon where the canned configuration files are to be stored.
5. In the righthand pane, verify that the files btsrtr_canned.blue and btsrtr_canned.red
appear.
6. If the files appear, proceed to step 16.
7. If the files do not appear, repeat step 14, its substeps, step 15 and its substeps.
SEP 2009
K-13
continued
Step
16
Action
Close Explorer, and, in the command line window, enter the following to terminate the FTP session:
bye

ftp> bye
221 Goodbye.
C:\Can_Cfg>
17
Close the command line window by entering the following:

exit
18
K-14
BTS router canned configuration files are now ready for transfer to a BTS router.
SEP 2009
BTS Router IOS Version Verification and Canned Configuration File

Installation

Installation
Introduction
Overview
This section covers the procedures and commands required to verify the
IOS version loaded on BTS router CF memory cards and copy standard
canned configuration files to the routers. Because of the setup required
and the length of some of the procedures, Motorola recommends
performing the actions covered in this section at a central location to
prepare the BTS routers for installation prior to the site visit.
IOS Version Verification and File Sequence Position
Version verification The IOS version loaded on the BTS router CF
memory card should be verified as the version required for operation on
the network where the routers will be installed. If the loaded IOS version
is not correct, it can be replaced with a different version. There are
several methods available to accomplish version verification. These
depend on the equipment and software applications the user selects to
use in installing the canned configuration files in the BTS routers.
Appropriate verification procedures are included in each of the two
canned configuration installation methods covered in this section.
Methods to change or upgrade the loaded IOS version are provided in the
Change or Upgrade BTS Router IOS Version section of this appendix
and are referenced at the appropriate places in the canned configuration
installation methods.
File sequence position During initialization, the MWR 190027 or
MWR 1941DC router will first search the startupconfig file for a
boot system command line telling it in what directory and file to find the
boot loader. If this line is not found, the router will default to attempting
to boot from the first file in its flash memory. Flash memory for the
MWR 190027 or MWR 1941DC is the CF memory card (software
identifier slot0:). The canned configuration files used for BTS router
installation do not contain a boot system command line because of the
need to maintain flexibility for IOS version changes. Because of this, it
is critical that the IOS file is the first file listed on the CF memory card.
The canned configuration installation procedures contain steps to assure
that this is the case, and, if it is not, provide guidance to correct the
condition. It is important to remember that, if the router boots and
displays a rommon 1 > prompt, the IOS file is missing, out of sequence,
has a corrupted flash memory image or the startupconfig file
contains a boot system line which specifies a missing or incorrect IOS
pathname/filename.
SEP 2009
K-15

Installation continued
Canned Configuration File Installation
Filename and installation location requirements The canned
configuration files for the BTS routers must be copied to the CF memory
card. The filename of the file on the CF memory card must be
cannedconfig. Canned configuration file location and filename
requirements are a result of Mobile Wireless Center (MWC) actions
during the process of switching a BTS from packet to circuit mode or
during BTS reparenting to another OMCR. In this process, the MWC
will query the BTS routers slot0: directory for a file named
cannedconfig. A missing or misnamed file will cause problems
with execution of the modeswitching process.
Installation Method The startupconfig configuration file used
by the BTS router during initialization is stored in NVRAM. This is a
memory device internal to the router and is separate from the CF
memory card. To install the canned configuration file so the router will
use it during bootup, the file must be copied into the
startupconfig file in NVRAM. This requires copying the canned
configuration file from the Windows operating systembased LMF
computer to the CF memory card installed in a router, and then copying
it to the startupconfig file in the routers NVRAM. The only
Motorolasupported method to copy files to the BTS router CF memory
card is through tftp file transfer.
CAUTION
Motorola does not support using a CF memory card reader
to copy files to the BTS router CF memory card. Do not
use a CF memory card reader for either of the following
actions:
S Formatting a BTS router CF memory card
S Copying files to a BTS router CF memory card
CAUTION
Do not format BTS router CF memory cards using a CF
memory card reader. Only format CF memory cards in a
BTS router. Using a card reader to format the CF memory
card will result in improper BTS router initialization which
requires special recovery procedures.
K-16
SEP 2009

Using a TFTP Server to Copy

Files to CF Memory Card
Required Equipment and Software

The following items are required to perform this procedure:
S A Windows operating systembased computer which meets the

requirements of the LMF computer platform
S One of the following operating systems for the Windows operating

systembased computer:
Windows 2000
Windows XP
CAUTION
BTS router CF memory cards loaded using computers
equipped with Windows 98 versions earlier than Windows
98 SE and using the FAT16 file system will not operate
properly, resulting in a complete site outage.
S One of the following for the Windows operating systembased

computer:
Internal 10/100baseT Network Interface Card (NIC)
PCMCIA 10/100baseT NIC
S Cable, rollover, as described in the Establishing a BTS Router

Communication Session section of this Appendix
S DB9 plugto8contact modular plug adapter as described in the
Establishing a BTS Router Communication Session section of this

Appendix
S Cable, Ethernet crossover, Category 5E or better, unshielded twisted
pair, two 8contact modular plugs, in one of the following lengths, as

determined necessary:
0.3 m (11.8 in) (Motorola pn 3088643C07)
0.6 m (23.6 in)(Motorola pn 3088643C13)
1.0 m (39.4 in) (Motorola pn 3088643C15)
2.1 m (84 in) (Motorola pn 3088643C08)
3.0 m (120 in) (Motorola pn 3088643C09)
S A +27 Vdc power supply to power the BTS router during

configuration file operations
S A tftp server software application (refer to the Setting Up the TFTP

Server Procedure in Cellular System Administration CDMA
OnLine Documentation, 68P09271A90) such as:
Cisco tftp server
PumpKIN tftp server
Any other equivalent tftp server application
SEP 2009
K-17

S A copy of the MWR 190027 or MWR 1941DC router IOS version
required for the network where the routers are to be installed (contact
the network administrator or the Motorola account team for
information on obtaining the required external BTS router IOS
version)
Required Materials
The following material is required to perform this method:
S Marking material to identify the BTS router and CF memory card with
the installed configuration (blue or red)
Required Publications
The following publications are required to perform procedures in this
section:
S The optimization/ATP manual for the BTS type
S Cellular System Administration CDMA OnLine Documentation,
68P09271A90
Preparation for Canned Configuration File TFTP Transfer to CF
Memory Card
Preparation for a canned configuration file tftp transfer consists of the

following activities:
1. Determining the speed of the LMF computer NIC (10 or 100 MHz)
2. Setting the LMF computer NIC IP address
3. Creating a directory (folder) on the LMF computer to be used for all
tftp file transfers
4. Installing the tftp server application on the LMF computer, and
setting the tftp server application root directory to the directory
created in 2, above
5. Connecting the LMF computer to the BTS router for both
HyperTerminal (serial) and Ethernet communication
6. BTS router powerup and initial configuration for Ethernet
communication
The following procedures are used to accomplish all of these preparatory
actions.
Set LMF computer NIC to communicate with BTS routers Follow
the procedure in Table K-4 to set the NIC IP address.
NOTE
If the IP address for the LAN connection on an LMF
computer is being changed using this procedure, the BTS
10base2 LAN IP address and subnet mask for the NIC
must be restored before the LMF can log into a BTS to
perform an optimization or ATP.
K-18
SEP 2009

NOTE
There are differences between the various operating
systems supported on the LMF computer in the menus and
screens used for setting or changing a NIC connection. In
the following procedure, items unique to:
S Windows XP operating system will be identified with
WinXP

Win2000
Table K-4: Configure Computer NIC

Step
Action
If it is not known, determine and record the speed of the LMF computer NIC (10 or 100 MHz) for use in
step 7 of Table K-7.
Start the computer.
Depending on the installed operating system, from the Windows operating system Start menu, select
one of the following:
S WinXP: Settings > Network Connections

S Win2000: Settings > Network and Dialup Connections
4
In the list of displayed connections, locate the Local Area Network connection for the NIC to be used.

1. Highlight the connection for the NIC
2. Right click the highlighted connection
3. Select Properties from the popup menu.
In the Local Area Connection Properties dialog box which appears, if Internet Protocol (TCP/IP) is
not showing in the Components checked are used by this connection: (Win2000) or The connection
uses the following items: (WinXP) listbox, refer to the operating system documentation and install
TCP/IP.
If the checkbox next to the Internet Protocol (TCP/IP) entry is not checked, click in the box to check
it.
Click the Configure button under the Connect using: list box at the top of the General tab.
In the Properties dialog box for the NIC hardware, click the Advanced tab to bring it to the front.
SEP 2009
K-19

Step
10
Action
NOTE
If the installed NIC does not support speeds of 100 Mbps, note the maximum speed available (such as
10 Mbps) in the worksheet and use it when initially configuring the BTS router in later procedures.
Perform one of the following as applicable for the installed operating system:
S For Win2000:
In the Property: listbox, highlight Connection Type.
Note the setting in the Value: list box, and record it in Table K-14 of the Network Interface Card
(NIC) Configuration Worksheet at the end of this appendix.
From the Value: listbox dropdown menu, select 100 Mbps Full_Duplex.
Click OK.
S For WinXP:
In the Property: listbox, highlight Speed & Duplex.
Note the setting in the Value: list box, and record it in Table K-14 of the Network Interface Card
(NIC) Configuration Worksheet at the end of this appendix.
From the Value: listbox dropdown menu, select 100 Mb Full.
Click OK.
11
S Win2000:
Highlight the Internet Protocol (TCP/IP) entry.
Cick on the Properties button below the Components checked are used by this connection:.
S WinXP:
Highlight the Internet Protocol (TCP/IP) entry.
Cick on the Properties button below the The connection uses the following items: listbox.
12
In the Internet Protocol (TCP/IP) Properties dialog box which appears, perform the following:
1. Note all settings on the General tab, and record them in the Record of original NIC configuration
subsection of the Network Interface Card (NIC) Configuration Worksheet at the end of this
appendix.
2. If a black dot is not showing in the the radio button circle next to Use the following IP address:,
click on the radio button.
Result: A black dot will appear in the circle.
3. Refer to the Network Interface Card (NIC) Configuration Worksheet, and enter the BTS router
communication setting values as indicated for the following under Use the following IP address: :
IP address:
Subnet mask:
K-20
SEP 2009


Step
Action
13
Click OK for the Internet Protocol (TCP/IP) Properties dialog box.
14
Click the OK button for the Local Area Connection Properties box.
Create default TFTP directory Perform the following to create a

default tftp directory on the laptop computer.
Table K-5: Create a Default TFTP Directory
Step
Action
Click Start > Programs > Windows Explorer to open the Windows operating system Explorer
(Explorer) application.
If the default tftp directory will be the same directory in which the files downloaded from the OMCR
are stored, proceed to step 10.
In the lefthand pane of Explorer, locate the icon for the drive where the default tftp directory is to be
created.
Highlight the drive icon and click Files > New > Folder.
While observing the new folder icon in the righthand pane, type the name for the folder (for example,
tftp_files), and press the Enter key.
In Explorer, locate the directory where the canned configuration files downloaded from the OMCR
are stored.
In the lefthand pane, highlight the directory where the files are stored.
Scroll the lefthand pane until the newlycreated default tftp directory is visible.
In the righthand pane, highlight the canned configuration files and drag them to the default tftp
directory.
10
In the lefthand pane, click on the default tftp directory, and verify that the canned configuration files
appear in the righthand pane.
11
Load a copy of the required BTS router IOS version into the default tftp directory using FTP, internet
download, or media such as a flash drive (file size is over 7 MB).
12
Click Files > Close to close Explorer.
Install and configure tftp server application To obtain, install, and

configure the Cisco or PumpKIN tftp software applications, refer to the
Setting Up the TFTP Server Procedure in Cellular System
Administration CDMA OnLine Documentation, 68P09271A90 For
other tftp server applications, install and configure the application
according to the manufacturers instructions.
SEP 2009
K-21

IMPORTANT
When entering the name of the tftp server root directory

while configuring the tftp server application, be sure to use
the name of the directory identified in Table K-4, step 2, or
created in Table K-5, step 2, above.
Connect the LMF computer to the BTS router Connect the LMF
computer to the BTS router by following the procedure in Table K-6 and
referring to Figure K-4.
Figure K-4: LMF Computer TFTP Connections to BTS Router
FAST ETHERNET PORT FE 0
(SOFTWARE DESIGNATION FA0/0)
ETHERNET
CROSSOVER
CABLE
CONSOLE
PORT
ROLLOVER
CABLE
TO BTS ROUTER
CONSOLE
RECEPTACLE
DB9TORJ48C
ADAPTER
LMF COMPUTER
OR EQUIVALENT
COM1
OR
COM2
10/100BASE T
NIC PORT
BTSRTR0025
K-22
SEP 2009

Table K-6: Connecting the LMF Computer to the BTS Router for TFTP File Transfer
Step
Action
If the BTS router has not been connected to a power source, be sure the +27 Vdc power source is not
on, and connect it to the router.
Connect the LMF computer to the BTS router as shown in Figure K-4, referring to the list of required
equipment in this section as required.
If the LMF computer has not been started, turn it on, login, and allow it to boot to the desktop.
Refer to the procedure in Table K-2 of this appendix, and start a HyperTerminal communication
session for the BTS router.
Start the tftp server application as specified for the software (refer to the Setting Up the TFTP Server
Procedure in Cellular System Administration CDMA OnLine Documentation, 68P09271A90 or the
manufacturers instructions).
BTS router powerup and initial configuration for Ethernet

communication Follow the procedure in Table K-7 to apply power to
the router and set an initial configuration for Ethernet communication.
S The required version of the IOS is loaded on the CF memory card

S The CF memory card is installed in the BTS router
Table K-7: BTS Router Powerup and Initial Ethernet Configuration
Step
Action
* IMPORTANT
This procedure does not cover all aspects of BTS router operation and programming. Before performing this
procedure, review BTS router initialization, operation, and programming information and procedures in MWR
1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983. Have this
publication available for reference while performing this procedure.
1
Be sure a CF memory card loaded with the Cisco IOS is installed in the BTS router (refer to the Replacing
a Compact Flash (CF) Memory Card section of the BTS Router chapter in the 1X SC4812TMF BTS Field
Replaceable Units for instructions to access the CF memory card slot).
NOTE
In this step do not touch the computer keyboard until the router completes the boot process. The router
will buffer any keystrokes made during the boot process and interpret them as commands to be
executed immediately following boot completion.
Apply power to the router and allow it to complete bootup.
If a message similar to the following, is displayed, press the Enter key and proceed to step 5:
Press RETURN to get started!

SEP 2009
K-23

Step
4
Action
If a message similar to the following, is displayed type no and press the Enter key:
Basic management setup configures only enough connectivity
for management of the system, extended setup will ask you
to configure each interface on the system
Would you like to enter basic management setup? [yes/no]:

Would you like to enter basic management setup? [yes/no]: no
Cisco Internetwork Operating System Software
IOS (tm) 1900 Software (MWR1900IM), Version 12.2(20020127:101239
Copyright (c) 19862002 by cisco Systems, Inc.
Compiled Sun 27Jan02 06:08 by walrobin
Router>
At the Router> user EXEC mode prompt, enter the following to access the privileged EXEC mode:
enable

Router>enable
Router#
At the Router# privileged EXEC mode prompt, enter the following to access the configure submode:
configure terminal

Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
The router is now in the global configuration mode and ready to accept configuration changes entered
from the keyboard.
K-24
SEP 2009


Step
7
Action
At the global configuration mode prompt, type each of the following commands, pressing the Enter
key after each command:
hostname btsrtr1
interface fa0/0
ip address 100.100.100.2 255.255.255.252
speed 100 or 10 depending on the speed of the LMF computer NIC
duplex full
no shutdown
line con 0
exectimeout 0 0
no login
line vty 0 4
no login
Responses similar to the following will be displayed:

Router(config)#hostname BTSRTR1
BTSRTR1(config)#interface fa0/0
BTSRTR1(configif)#ip address 100.100.100.2 255.255.255.252
BTSRTR1(configif)#speed 100
BTSRTR1(configif)#duplex full
BTSRTR1(configif)#no shutdown
BTSRTR1(configif)#line con 0
BTSRTR1(configline)#exectimeout 0 0
BTSRTR1(configline)#no login
BTSRTR1(configline)#line vty 0 4
BTSRTR1(configline)#no login
BTSRTR1(configline)#
Once the correct parameters have been set, return to the privileged EXEC mode prompt by holding
down the Ctrl key and pressing z (Ctrl+z).
BTSRTR1(configline)# ^z
01:11:27: %SYS5CONFIG_I: Configured from console by console
BTSRTR1#
NOTE
Entering exit twice, pressing the Enter key after each entry, will also complete the configuration
process and return the router to the privileged EXEC mode.
SEP 2009
K-25

Step
9
Action
Verify port FE 0 (fa0/0) is configured with the correct IP address by entering the following:
show ip interface brief

BTSRTR1#sh ip int br
Interface
IP Address
FastEthernet0/0 100.100.100.2
Serial0:0
unassigned
FastEthernet0/1 unassigned
Serial1:0
unassigned
OK?
YES
YES
YES
YES
Method
manual
unset
unset
unset
Status
Protocol
up
up
administratively down down
BTSRTR1#
10
The router is now configured for Ethernet communication on FE 0, and the canned configuration file
can be transferred by tftp. Proceed to Table K-8.
Verifying IOS Version and Canned Configuration File TFTP

Transfer to the BTS Router
Prerequisites A copy of the required MWR 190027 or MWR

1941DC router IOS version file must be installed in the default tftp
directory (transfer the file to the LMF computer using FTP, internet
download, or media such as a flash drive; file size is approximately 78
MB)
IMPORTANT
MWR 1941DC routers must be loaded with IOS version

mwr1900imz.1228.MC2d.bin or later. This router
model will not function properly with earlier IOS versions.
IOS verification and canned configuration file transfer Follow the

procedure in Table K-8 to verify the loaded IOS version and transfer the
canned configuration files from the LMF computer to the BTS router CF
memory card.
K-26
SEP 2009

IMPORTANT
This procedure does not cover all aspects of BTS router

operation and programming. Before performing this
procedure, review BTS router initialization, operation, and
programming information and procedures in MWR
1941DC Wireless Mobile Edge Router Software
Configuration Guide; part number 7813983. Have this
publication available for reference while performing this
procedure.
Table K-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server
Step
Action
! CAUTION
If personal firewall and/or intrusion detection software such as Black ICE is running on the LMF computer,
shut it down before performing this procedure. If this is not done, the tftp transfer process will not operate.
1
On the LMF computer, if it has not been done, start the tftp server according to the manufacturers
directions (refer to the Setting Up the TFTP Server Procedure in the Cellular System Administration
CDMA OnLine Documentation, 68P09271A90).
If a HyperTerminal communication session with the BTS router is not running, start one following the
procedure in Table K-2.
In the HyperTerminal window, the router must be in the privileged EXEC mode, as indicated by a
number sign at the end of the prompt:
BTSRTR1#
Be sure the Ethernet crossover cable is connected between the LMF computer NIC port and the BTS
router FE 0 port (Figure K-4).
SEP 2009
K-27

Step
5
Action
Begin verification that the CF memory card contains the correct version of the Cisco IOS by entering
the following:
dir slot0:

BTSRTR1#dir slot0:
Directory of slot0:/
1
rw
7051976
Mar 01 1993 00:11:34
mwr1900imz.1228.MC2a.bin
31932416 bytes total (24879104 bytes free)

BTSRTR1#
NOTE
1. The IOS defaults to the CF memory card (slot0:) directory unless the present working directory has
been changed using the cd command. Determine the present working directory by entering pwd .
If the present working directory has been changed, enter the command cd slot0: to return to the
default setting.
2. If slot0: is included in the command, be sure to include the colon (:) after slot0 when typing the
command.
3. The IOS filename will be similar to the following:
K-28
SEP 2009

Step
6
Action
Direct the router to show the version information by entering the following:
show version

BTSRTR1#sh ver
IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Compiled Mon 05Aug02 11:07 by nmasa
Image textbase: 0x60008940, database: 0x60B54000
ROM: System Bootstrap, Version 12.2(20020113:235343) [sbosewilma 109],
DEVELOPMENT SOFTWARE
ROM: 1900 Software (MWR1900IM), Version 12.2(8)MC2a, EARLY DEPLOYMENT
RELEASE SOFTWARE (fc1)
Router uptime is 1 minute
System returned to ROM by poweron
System image file is slot0:mwr1900imz.1228.MC2a.bin
cisco mwr1900 (R7000) processor (revision 0.1) with 121856K/18432K bytes
of memory.
Processor board ID JMX0611K5TS
R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 Cache
Bridging software.
X.25 software, Version 3.0.0.
Primary Rate ISDN software, Version 1.1.
Toaster processor tmc is running.
2 FastEthernet/IEEE 802.3 interface(s)
2 Serial network interface(s)
2 Channelized T1/PRI port(s)
DRAM configuration is 64 bits wide with parity disabled.
55K bytes of nonvolatile configuration memory.
31360K bytes of ATA Slot0 CompactFlash (Read/Write)
Configuration register is 0x101
BTSRTR1#
Compare the IOS filename returned in step 5 and the second line of the version information in step 6.
Note the correspondence between the filename and IOS version information.
* IMPORTANT
MWR 1941DC routers must be loaded with IOS version mwr1900imz.1228.MC2d.bin or later.
This router model will not function properly with earlier IOS versions.
SEP 2009
K-29

Step
Action
If the IOS filename from the CF memory card returned in step 5 is different than the filename of the
required IOS version loaded in the LMF computer default tftp directory, perform the procedure in
Table K-9 to load the required version, and then return to step 9, below.
! CAUTION
The file sequence on the CF memory card can not be verified with application programs which place
the listed file names in alphabetical order (for example, certain Unix telnet applications, Unix
directory listing commands, and Windows file managers such as Windows Explorer). This portion of
the procedure is intended for use only with applications, such as HyperTerminal, which do not list
directory contents alphabetically.
If the IOS version is correct and there is more than one file loaded on the CF memory card, be sure the
IOS file is the first file listed in the directory content display. If it is not, perform the following:
1. Backup all files on the CF memory card to the LMF computer default tftp directory by performing
steps 3 through 10 of Table K-9.
2. Perform steps 25 through 29 of Table K-9, as applicable.
3. Type the following to delete a possible boot system line in the startupconfig file, pressing the
Enter key after the command and at each prompt to confirm the filename and deletion operation:
del nvram:startupconfig

BTSRTR1#del nvram:startupconfig
Delete filename [startupconfig]?
Delete nvram:startupconfig? [confirm]
[OK]
BTSRTR1#
NOTE
Be sure to include the colon (:) after nvram when typing the command.
K-30
SEP 2009

Step
Action
4. Verify the startupconfig file size has been reduced to a minimum by entering the following:
dir nvram:

Router#dir nvram:
Directory of nvram:/
53
54
rw
5
5
<no date>
<no date>
startupconfig
privateconfig

BTSRTR1#
10
At the privileged EXEC mode prompt, enter the following:

copy tftp:btsrtr_canned.color slot0:cannedconfig
Where color = blue or red, as applicable.

BTSRTR1#copy tftp:btsrtr_canned.blue slot0:cannedconfig
Address or name of remote host []?
11
At the prompt for the remote host address or name, enter the IP address of the LMF computer NIC:
100.100.100.1

Address or name of remote host []? 100.100.100.1
Destination filename [cannedconfig]?
SEP 2009
K-31

Step
12
Action
At the prompt for the destination filename, press the Enter key.
Loading btsrtr_canned.blue from 100.100.100.1 (via Ethernet0/0): !
[OK 2457/4096 bytes]
2457 bytes copied in 84.724 secs (29 bytes/sec)
BTSRTR1#
13
Verify that the canned configuration file is saved on the CF memory card by entering the following:
dir

1
2
rw
rw
7051976
2457
Mar 01 1993 00:11:34

Mar 01 1993 00:14:48
cannedconfig

BTSRTR1#
14
To allow the BTS router to boot using the canned configuration, enter the following:
copy cannedconfig startupconfig

BTSRTR1#copy cannedconfig start
Destination filename [startupconfig]?
15
When prompted for the destination file name, press the Enter key.
BTSRTR1#copy cannedconfig start
2457 bytes copied in 3.52 secs
BTSRTR1#
K-32
SEP 2009

Step
16
Action
Display and note the file size of startupconfig by entering the following:
dir nvram:

Directory of nvram:/
26
27
rw
2457
5
<no date>
<no date>
startupconfig
privateconfig

BTSRTR1#
17
Scroll the HyperTerminal window back to the slot0: directory display obtained in step 13, above.
18
Compare the file size of startupconfig to the canned configuration file to verify the copy operation.
File sizes should be the same.
19
If desired, the contents of the startupconfig file may be verified against the file listings at the end of
this appendix for the blue or red canned configuration, as applicable, by entering the following:
show startupconfig
NOTE
Pressing the space bar at the MORE prompt will scroll another screenfull of data. Pressing the Enter
key will scroll the screen one line at a time.
20
Verify the router will boot properly on the IOS and revised startupconfig files by entering the
following:
reload

BTSRTR1#reload
System configuration has been modified. Save? [yes/no]: n
Proceed with reload? [confirm]
21
If prompted to save a modified configuration, enter n for no, and press the Enter key.
22
When prompted to proceed with reload, press the Enter key to continue the reload operation.
SEP 2009
K-33

Step
23
Action
NOTE
Reloading the router with the revised startupconfig file will change router FE port speed to 100. If
the router FE port speed was changed to 10 to communicate with the LMF computer NIC, the
computer may indicate that the FE LAN connection has been lost at this point.
Verify the router reboots without displaying the rommon 1 > prompt or error messages related to port
configurations. If the router boots to the rommon prompt, proceed to the Recovery from BTS Router
Boot to rommon section of this appendix.
24
Using the tagging materials, tag the router to clearly identify the installed configuration (blue
(BTSRTR1) or red (BTSRTR2)).
25
Remove the CF memory from the router following the procedure in the Replacing a Compact Flash
(CF) Memory Card section of the BTS Router chapter in the 1X SC4812TMF BTS Field Replaceable
Units, mark the installed configuration (blue or red) on the card label, and install the card in the router
following the CF memory card replacement procedure in the 1X SC4812TMF BTS Field Replaceable
Units.
26
If an additional router must have the canned configuration installed, perform the following:
1. Disconnect the cabling from the BTS router.
2. Remove power from the router and disconnect it from the power supply.
3. Repeat the procedures in Table K-6, Table K-7, and this table (Table K-8) using the additional
router.
27
If no additional routers must be configured, perform the first two substeps of step 26.
28
On the LMF computer, shut down the tftp server application and exit the HyperTerminal session.
29
If no additional tftp transfer activities will be performed, change the NIC IP address and subnet mask
back to those for LMFBTS communication recorded in Table K-4, step 10.
! CAUTION
If the BTS 10base2 LAN IP address and subnet mask for the LMF computers NIC are not restored,
the LMF can not log into a BTS when attempting to perform a BTS optimization or ATP.
K-34
SEP 2009
Change or Upgrade BTS Router IOS Version

Background
BTS routers are supplied with CF memory cards preloaded with a

version of the IOS. Prior to installing the routers in a BTS, the loaded
IOS version should be verified as being the one required for the network.
It is critical to also verify that the IOS file is the first file on the CF
memory card. If another file precedes the IOS file, the BTS router will
not boot properly and will not function in the network.
Equipment and Software
Required
The following items are required to perform this procedure:


Windows 2000
Windows XP
CAUTION
equipped with Windows 98 versions earlier than Windows
98 SE and using the FAT16 file system will not operate
properly, resulting in a complete site outage.


Appendix

0.3 m (11.8 in) (Motorola pn 3088643C07)
0.6 m (23.6 in)(Motorola pn 3088643C13)
1.0 m (39.4 in) (Motorola pn 3088643C15)
2.1 m (84 in) (Motorola pn 3088643C08)
3.0 m (120 in) (Motorola pn 3088643C09)


SEP 2009
K-35
continued
Cisco tftp server

PumpKIN tftp server
S A copy of the MWR 190027 or MWR 1941DC router IOS version
required for the network where the routers are to be installed
NOTE
Contact the network administrator or the Motorola Account
Team for assistance in determining and obtaining a copy of
the required IOS version.
IMPORTANT
MWR 1941DC routers must be loaded with IOS version

mwr1900imz.1228.MC2d.bin or later. This router
model will not function properly with earlier IOS versions.
The following publication is required to perform procedures in this

section:
Upgrade/Replace Installed IOS
Version and Verify File
Sequence Position
Description This procedure covers using an LMF computer equipped

with a tftp server application to perform the following activities:
1. Verify the IOS version loaded on a CF memory card and running on
a BTS router
2. Upgrade or replace the IOS version installed in a BTS router
3. Ensure the IOS file is the first file on the CF memory card
Prerequisites The following are required prior to performing this
procedure:
S The LMF computer and BTS router have been prepared for tftp file
transfer and are operating as they would be after performing the
procedures in Table K-4, Table K-6, Table K-7, and steps 1 through 8
of Table K-8
S A copy of the required IOS version is loaded into the tftp default
directory of the LMF computer
Upgrading/replacing installed IOS version and verifying file
sequence position Follow the procedure in Table K-9 to replace or
upgrade the installed IOS version using the tftp server application, and
ensure the IOS file is first in the stored file sequence on the CF memory
card.
K-36
SEP 2009
continued
Table K-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and
Verifying File Sequence Position
Step
Action
* IMPORTANT
1
This procedure assumes the LMF computer and BTS router are configured, connected, and operating
as they would be after performing the procedures in Table K-4, Table K-6, Table K-7, and steps 1
through 8 of Table K-8. If necessary, perform these procedures now.
NOTE
The IOS present working directory defaults to the CF memory card (slot0:) directory unless the present
working directory has been changed using the cd command. Determine the present working directory
by entering pwd . If the present working directory has been changed, enter the command cd slot0:
to return to the default setting.
Identify the filename of the currently loaded IOS which must be replaced by entering the following:
dir

BTSRTR1#dir
1
2
rw
rw
7051844
2212
Sep 23 2002 07:15:08

Mar 01 1993 00:11:00
mwr1900imz.07022002.bin
cannedconfig

BTSRTR1#
Begin to backup the currently installed version of the routers IOS to the LMF computers default tftp
directory by entering the following:
copy old_IOS_filename tftp:
Where old_IOS_filename = the filename of the IOS currently loaded on the BTS router CF
memory card.
BTSRTR1#copy mwr1900imz.07022002.bin tftp:
SEP 2009
K-37
continued
Step
4
Action
At the remote host prompt, enter the following:
100.100.100.1

Destination filename [mwr1900imz.07022002.bin]?
If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is
missing or not correct, enter the correct filename.
A response similar to the following will be displayed if the default filename is selected:
Destination filename [mwr1900imz.07022002.bin]?
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
BTSRTR1#
K-38
SEP 2009
continued
Step
6
Action
If additional files are stored on the CF memory card, begin backing them up to the LMF computers
default tftp directory by entering the following:
copy additional_filename tftp:
Where additional_filename = the filename of an additional file loaded on the BTS router CF
memory card.
BTSRTR1#copy cannedconfig tftp:
Address or name of remote host [100.100.100.1]?
If the default IP address displayed in the prompt is correct, press the Enter key to accept it. If it is
missing or not correct, enter the correct IP address for the LMF computer.
Source filename [cannedconfig]?
Source filename [cannedconfig]?
!
[OK 2212/4096 bytes]
BTSRTR1#
10
If more files are stored on the CF memory card, repeat steps 6 through 9 until all files have been
backed up to the LMF computer.
SEP 2009
K-39
continued
Step
11
Action
Delete all files from the CF memory card by entering the following command:
format slot0:

BTSRTR1#format slot0:
Format operation may take a while. Continue? [confirm]
12
Press the Enter key to continue the format operation.

Format operation will destroy all data in slot0:. Continue? [confirm]
13

Format: Drive communication & 1st Sector Write OK...
Writing Monlib
sectors....................................................................
................
Monlib write complete
.
Format: All system sectors written. OK...
Format: Total sectors in formatted partition: 62560
Format: Total bytes in formatted partition: 32030720
Format: Operation completed successfully.
Format of slot0 complete
BTSRTR1#
K-40
SEP 2009
continued
Step
14
Action
Verify all files have been deleted from the CF memory card by entering the following:
dir

No files in directory
BTSRTR1#
15
Begin to copy the required version of the IOS from the LMF computer to the BTS router by entering the
following:
copy tftp:new_IOS_filename slot0:
Where new_IOS_filename = the filename of the required IOS for the BTS router.
BTSRTR1#copy tftp:mwr1900imz.1228.MC2a.bin slot0:
16
Source filename [mwr1900imz.1228.MC2a.bin]?
17
Source filename [mwr1900imz.1228.MC2a.bin]?
Destination filename [mwr1900imz.1228.MC2a.bin]?
SEP 2009
K-41
continued
Step
18
Action
If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is not
correct, enter the correct filename.
Destination filename [mwr1900imz.1228.MC2a.bin]?
Accessing tftp://100.100.100.1/mwr1900imz.1228.MC2a.bin...
Loading mwr1900imz.1228.MC2a.bin from 100.100.100.1 (via FastEthernet0/0): !!!!
Loading mwr1900imz.1228.MC2a.bin from 100.100.100.1 (via FastEthernet0/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK 7051976/14103552 bytes]
BTSRTR1#
K-42
SEP 2009
continued
Step
19
Action
Display the CF memory card directory to verify that the new IOS file is there by entering the
following:
dir

BTSRTR1#dir
1 rw
7051976
Sep 23 2002 07:25:36
BTSRTR1#
20
If any additional files previously stored on the CF memory card are to be copied to the card, perform
the following:
copy tftp:filename slot0:
Where filename = the filename of the file to be copied to the CF memory card
BTSRTR1#copy tftp:cannedconfig slot0:
21
A response similar to the following will be displayed if the default IP address is selected:
22
Accessing tftp://100.100.100.1/cannedconfig...
Loading basic_config from 100.100.100.1 (via FastEthernet0/0): !
[OK 2212/4096 bytes]
BTSRTR1#

SEP 2009
K-43
continued
Step
23
Action
After the additional file is copied to the CF memory card, display the CF memory card directory by
entering the following:
dir

BTSRTR1#dir
1 rw
7051976
Sep 23 2002 07:24:18
2 rw
2212
Mar 01 1993 00:09:06
cannedconfig
24
The IOS file must be the first file listed for the BTS router to boot properly. If it is, proceed to step 29.
25
! CAUTION
If another file is listed before the IOS file, delete the file by performing steps 11 through 13 and
display the directory of the CF memory card as described in step 23 to be sure the file is deleted.
26
Copy the file from the LMF computer to the CF memory card again by performing steps 20 through
23.
27
If the file is again listed before the IOS file in the CF memory card directory display, format the CF
memory card by performing steps 11 through 14 of this table.
28
Copy the IOS file and any other required file to the formatted CF memory card by performing steps 15
through 24.
29
If additional files are to be transferred to the CF memory card, perform steps 20 through 24 for each
one.
K-44
SEP 2009
continued
Step
30
Action
After making sure the IOS file is the first file on the CF memory card, restart the BTS router with the
new IOS version by entering the following:
reload

BTSRTR1#reload
31
32
33
Once the router has completed rebooting, change to the privileged EXEC mode and confirm the
booted IOS version is correct by entering the following:
show version
A response similar to the following partial example will be displayed:

BTSRTR1#sh ver
IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
.
.
.
BTSRTR1#
34
Verify the version number displayed in the second line of the version information is the correct IOS
version.
35
If this procedure was entered from step 8 of Table K-8, return to Table K-8, step 9.
SEP 2009
K-45
continued
Step
36
Action
If no other BTS router file operations or configuration actions are required, perform the following:
2. Disconnect all other cabling from the BTS router.
3. On the LMF computer, exit the HyperTerminal communications session.
37
! CAUTION
K-46
SEP 2009
Verify and Upgrade ROMmon Version

Introduction
BTS routers are supplied preloaded with a version of the ROM monitor
(ROMmon) lowlevel operating system. Along with the IOS version, the
loaded ROMmon version should be verified as being the one required
for the network. Procedures in this section are used to verify the loaded
ROMmon version, and, if necessary, upgrade or change it to the required
version. A tftp server application is needed to transfer the required
ROMmon version to a BTS routers CF memory card.
Required Equipment and
Software
The following items are required to perform ROMmon version

verification and upgrade for both verification/upgrade methods:


Windows 2000
Windows XP
CAUTION
equipped with Windows 98 operating system versions
earlier than Windows 98 SE and using the FAT16 file
system will not operate properly, resulting in a complete
site outage.


Appendix

0.3 m (11.8 in) (Motorola pn 3088643C07)
0.6 m (23.6 in)(Motorola pn 3088643C13)
1.0 m (39.4 in) (Motorola pn 3088643C15)
2.1 m (84 in) (Motorola pn 3088643C08)
3.0 m (120 in) (Motorola pn 3088643C09)

SEP 2009
K-47
continued

Cisco tftp server
PumpKIN tftp server
S A copy of the MWR 190027 or MWR 1941DC router ROMmon
version required for the network where the routers are to be installed
NOTE
Contact the network administrator or the Motorola Account
Team for assistance in determining and obtaining a copy of
the required ROMmon version.
The following publication is required to perform procedures in this

section:

Verification and
Upgrade/Replacement of
Installed ROMmon Version
Description This procedure covers using an LMF computer equipped

with a tftp server application to perform the following activities:
1. Verify the ROMmon version loaded and running on a BTS router
2. Upgrade or replace the ROMmon version installed in a BTS router
Prerequisites The following are required prior to performing this
procedure:
S The LMF computer and BTS router have been prepared for tftp file
transfer and are operating as they would be after performing the

procedures in Table K-4, Table K-6, Table K-7, and steps 1 through 8
of Table K-8
S A copy of the required ROMmon version is loaded into the tftp

default directory of the LMF computer
K-48
SEP 2009
continued
Verifying and Upgrading/replacing installed ROMmon version

Follow the procedure in Table K-10 to verify and, if necessary, replace or
upgrade the installed ROMmon version using the tftp server application.
Table K-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server
Step
Action
* IMPORTANT
1
This procedure assumes the LMF computer and BTS router are configured, connected, and operating
as they would be after performing the procedures in Table K-4, Table K-6, Table K-7, and steps 1
through 4 of Table K-8. If necessary, perform these procedures now.
SEP 2009
K-49
continued
Step
2
Action
Determine the currently installed ROMmon version by entering the following at the router privileged
EXEC mode prompt:
show version

BTSRTR1#sh ver
IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3)
ROM: 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT
System image file is slot0:mwr1900imz.1228.MC2b.bin
of memory.
Bridging software.
BTSRTR1#
To determine the currently installed ROMmon version, examine the ROM: System Bootstrap line
in the response.
K-50
SEP 2009
continued
Step
4
Action
Compare the installed ROMmon version information with the filename of the ROMmon version
required for the network.
NOTE
1. Rommon filename format is similar to the following:
MWR1900_RM2.srec.1228r.MC3.bin
2. The ROMmon filename reflects the version number of the software (1228r.MC3).
5
If the installed version is the one required for the network skip to step 26.
If the installed ROMmon version is not the one required for the network, backup the current BTS
router configuration to the LMF computer by entering the following:
copy nvram:startupconfig tftp

BTSRTR1#copy nvram:start tftp
NOTE
Be sure to include the colon (:) after nvram when typing the command.
7
At the prompt for the remote host address or name, enter the IP address of the LMF computer NIC:
100.100.100.1

BTSRTR1#copy copy nvram:start tftp
Source filename [startupconfig]?
Source filename [startupconfig]?
SEP 2009
K-51
continued
Step
9
Action
!
[OK 2212/4096 bytes]
BTSRTR1#
10
NOTE
The IOS defaults to the CF memory card (slot0:) directory unless the present working directory has
been changed using the cd command. Determine the present working directory by entering pwd . If
the present working directory has been changed, enter the command cd slot0: to return to the default
setting.
Determine the amount of memory available (bytes free) on the CF memory card by entering the
following:
dir

BTSRTR1#dir
1 rw
7051976
Sep 23 2002 07:24:18
mwr1900imz.1228.MC2b.bin
2 rw
2212
Mar 01 1993 00:14:48
cannedconfig

Router#
11
Be sure there is at least 1 MB (1048580) of free memory.
NOTE
A ROMmon version file requires approximately 0.7 MB.
K-52
SEP 2009
continued
Step
Action
12
Begin to copy the required version of the ROMmon file from the LMF computer to the BTS router by entering the following:
copy tftp:new_rommon_filename slot0:
Where new_rommon_filename = the filename of the required ROMmon version for the BTS
router.
BTSRTR1#copy tftp:MWR1900_RM2.srec.1228r.MC3.bin slot0:
13
Source filename [MWR1900_RM2.srec.1228r.MC3.bin]?
14
Source filename [MWR1900_RM2.srec.1228r.MC3.bin]?
Destination filename [MWR1900_RM2.srec.1228r.MC3.bin]?
15
If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is not
correct, enter the correct filename.
Destination filename [MWR1900_RM2.srec.1228r.MC3.bin]?
Accessing tftp://100.100.100.1/MWR1900_RM2.srec.1228r.MC3.bin...
Loading MWR1900_RM2.srec.1228r.MC3.bin from 100.100.100.1 (via FastEthernet0/0): !!!!
Loading MWR1900_RM2.srec.1228r.MC3.bin from 100.100.100.1 (via FastEthernet0/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK 614306/14103552 bytes]
BTSRTR1#

SEP 2009
K-53
continued
Step
16
Action
Display the CF memory card directory to verify that the new ROMmon version file is there by
dir

BTSRTR1#dir
1 rw
7051976
Sep 23 2002 07:25:36
2 rw
2212
Mar 01 1993 00:09:06
3 rw
614306
Dec 13 2002 14:59:36
cannedconfig

BTSRTR1#
17
Replace the existing ROMmon version with the new one copied to the CF memory card by entering
the following:
upgrade rommonitor file slot0:MWR1900_RM2.srec.1228r.MC3

BTSRTR1#This command will reload the router. Continue?[yes/no]
18
When prompted to continue, enter yes and press the Enter key.
BTSRTR1#This command will reload the router. Continue?[yes/no] yes
ROMMON image upgrade in progress
Erasing boot flash
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
Programming boot flash pppp
Now reloading
19
When the router has completed initialization, change to the router privileged EXEC mode by entering
the following:
enable

BTSRTR1>enable
BTSRTR1#

K-54
SEP 2009
continued
Step
20
Action
Verify the router has initialized with the new ROMmon version by entering the following:
show version
A response similar to the following partial response will be displayed:

BTSRTR1#sh ver
ROM: System Bootstrap, Version 12.2(8r)MC3 RELEASE SOFTWARE (fc1)
21
Compare the version displayed in the response ROM: System Bootstrap line to the filename of the
new ROMmon version file copied to the CF memory card.
22
If the router successfully rebooted with the new ROMmon version, the ROMmon file can be deleted
from the CF memory card by entering the following:
delete slot0:new_rommon_filename
Where new_rommon_filename = the filename of the required ROMmon version copied to the CF
memory card in steps 12 through 15, above.
BTSRTR1#del slot0:MWR1900_RM2.srec.1228r.MC3.bin
Delete filename [MWR1900_RM2.srec.1228r.MC3.bin]?
23
Delete slot0:MWR1900_RM2.srec.1228r.MC3.bin? [confirm]
SEP 2009
K-55
continued
Step
24
Action
Press the Enter key to confirm the deletion.
Delete slot0:MWR1900_RM2.srec.1228r.MC3.bin? [confirm]
BTSRTR1#
25
! CAUTION
In this step, do not delete the IOS and cannedconfig files from the CF memory card. The BTS
router must have these files on the card to properly boot or switch between packet and circuit mode.
If additional unnecessary files, such as a backup of the startupconfig file, are also on the CF
memory card, delete them by repeating steps 22 through 24 for each file.
26
If no other BTS router file operations or configuration actions are required, perform the following:
2. Disconnect all cabling from the BTS router.
3. On the LMF computer, exit the HyperTerminal communications session.
27
! CAUTION
K-56
SEP 2009
Recovery from BTS Router Boot to ROMmon

Introduction
ROM monitor boot conditions Under certain circumstances the BTS

router will initialize with the ROM monitor (ROMmon) operating
system rather than the IOS. These circumstances include:
S The hexadecimal value in the routers configuration register has been
changed from the factory default (can change the location from where
the router attempts to load code for bootup).
S IOS file is missing from the CF memory card

S IOS file is not the first file on the CF memory card
S Startupconfig file contains an outdated boot system line specifying
an IOS file which has been replaced with an updated version
S Startupconfig file contains boot system line with typographical

error(s) in the IOS filename
S IOS file image on the CF memory card is corrupted

Description Router operation on ROMmon is signalled by the display
of the rommon # > prompt, where # is a number which increments
each time a command is issued. ROMmon is a lowlevel operating
system which provides limited capabilities for router testing and
troubleshooting operations, including viewing directory contents and
booting from a specified file.
Recovery methods Two recovery methods are included in this section.
The first is the simplest and requires that a valid, uncorrupted IOS
version is installed on the CF memory card. The second method requires
additional equipment and must be used in instances when an IOS file is
not installed on the CF memory card or the installed IOS image is
corrupted.
Simple Recovery from Boot to
ROMmon
Requirements Unless it is certain that the IOS image on the CF

memory card is corrupted, this method should always be the first tried
for router recovery from ROMmon initialization. This method does not
require any additional equipment beyond the items necessary to load
canned configuration files into the BTS router. To be effective, this
method does require that a valid, uncorrupted IOS image file is installed
on the routers CF memory card.
SEP 2009
K-57
continued
Recovery Follow the procedure in Table K-11 to attempt a simple

recovery from a BTS router ROMmon initialization.
Table K-11: Simple Recovery from BTS Router ROMmon Boot
Step
Action
* IMPORTANT
1
This procedure assumes the LMF computer is set up and connected to the BTS router with an active
HyperTerminal communication session. If it is not, follow the procedure in Table K-2 to establish a
HyperTerminal communication session.
With the rommon 1 > prompt displayed in the HyperTerminal window, enter the following to
determine if the routers configuration register is set to the factory default value:
confreg

rommon 4 > confreg
Configuration Summary
(Virtual Configuration Register: 0x100)
enabled are:
load rom after netboot fails
console baud: 9600
boot: image specified by the boot system commands
or default to: cisco2mwr1900
do you wish to change the configuration? y/n
[n]:
NOTE
S The configuration register setting is shown in the (Virtual Configuration Register: 0x____) line
S 0x in the Virtual Configuration Register line indicates the numbers following are hexadecimal
3
If the value shown for the configuration register is 2102, skip to step 6.
K-58
SEP 2009
continued

Step
4
Action
If the value shown for the configuration register is not 2102, perform the following:
1. Press the Return key to accept the default of n (for no).
2. Enter the following at the rommon prompt:
confreg 0x2102

rommon 3 > confreg 0x2102
You must reset or power cycle for new config to take effect
rommon 4 >
3. Enter the following at the rommon prompt:

reset
A response which begins and ends similar to the following will be displayed:
rommon 4 > reset
System Bootstrap, Version 12.2(20020113:235343) [sbosewilma 109], DEVELOPMENT SOFTWARE
mwr1900 processor with 131072 Kbytes of main memory
Main memory is configured to 64 bit mode with parity disabled
Readonly ROMMON initialized

.
...<output omitted>...
.
If the router reboots with the IOS, skip to step 21.

SEP 2009
K-59
continued

Step
6
Action
If the configuration register is set properly and/or the router does not reboot with the IOS, enter the
following at the rommon # > prompt to identify the IOS file on the CF memory card:
dir slot0:

rommon 1 > dir slot0:
program load complete, entry point: 0x80008000, size: 0xb2a0
Directory of slot0:
2
2212
rw
cannedconfig
7051976
rw
614306
rw
rommon 2 >
NOTE
The IOS filename will be similar to the following:
7
If there is no IOS file on the CF memory card, proceed to Table K-12 and perform the extended
recovery procedure.
K-60
SEP 2009
continued

Step
8
Action
If an IOS file is found, note the IOS filename, and enter the following to begin recovery to an IOS
boot:
boot slot0:IOS_filename
Where IOS_filename = the filename of the IOS noted in step 6, above.

A successful IOS reboot operation will result in display of a response which begins and ends similar
to the following:
rommon 2 > boot slot0:mwr1900imz.1228.MC2b.bin
program load complete, entry point: 0x80008000, size: 0x6b99ac
Self decompressing the image :
################################################################### [OK]
Smart Init is enabled
smart init is sizing iomem
ID
00031A
MEMORY_REQ
TYPE
0X005F3C00 MWR1900 Mainboard

0X000F3BB0 public buffer pools
0X00211000 public particle pools
TOTAL:
0X008F87B0
.
.
If the router successfully reboots with the IOS, skip to step 12.
10
If the router does not reboot with the IOS, perform the following:
1. Scroll the HyperTerminal display down until the directory display from step 6, above, is visible.
2. Compare the IOS filename from the directory display with the filename entered when performing
step 8, above.
3. If the filename was typed incorrectly, repeat step 8, using care to type the filename correctly.
SEP 2009
K-61
continued

Step
Action
11
If the router still does not reboot with the IOS after typing the filename correctly, proceed to
Table K-12 and perform the extended recovery procedure.
12
! CAUTION
After a successful reboot with IOS, perform the following to correct the cause of the boot to
ROMmon:
1. At the BTSRTR1> user EXEC mode prompt, enter the following to access the privileged EXEC
mode:
enable

BTSRTR1>enable
BTSRTR1#
2. Enter the dir slot0: command to display the CF memory card directory, and, if the IOS file is not
the first file listed, perform the procedure in Table K-9, steps 25 through 32, to correct the situation
K-62
SEP 2009
continued

Step
Action
3. If the IOS file is the first file, enter the following command to display the contents of the
startupconfig file:
show startupconfig
A response which begins similar to the following will be displayed:

BTSRTR1#sh start
Using 1589 out of 57336 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service passwordencryption
!
hostname BTSRTR1
!
boot system slot0:mwr1900imz.07132002.bin
no logging console
!
username cisco password 0 cisco
!
redundancy
mode ycable
standalone
!
13
Review the startupconfig file listing for a boot system line and perform the following:
1. If the startupconfig file does not contain a boot system line, skip to step 14.
2. If the file listing contains a boot system line, examine it for the correct IOS filename.
3. If the boot system slot0: filename is incorrect, enter the following, using care to type the filename
correctly:
boot system slot0:IOS_filename

4. Replace the boot system line in the startupconfig file with the line entered in substep 3, above, by
copy runingconfig startupconfig
SEP 2009
K-63
continued

Step
Action
5. Verify the correct IOS filename is now included in the listing by entering the following:
show startupconfig
A response which begins similar to the following will be displayed:

BTSRTR1#sh start
Using 1589 out of 57336 bytes
!
version 12.2
!
hostname BTSRTR1
!
boot system slot0:mwr1900imz.1228.MC2b.bin
no logging console
!
username cisco password 0 cisco
!
redundancy
mode ycable
standalone
!
K-64
SEP 2009
continued

Step
14
Action
Reverify the routers configuration register setting by entering the following:
show version

BTSRTR1#sh ver
ROM: 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT
System image file is slot0:mwr1900imz.1228.MC2b.bin
of memory.
Bridging software.
BTSRTR1#
NOTE
The configuration register value is shown in the last line of the show version response.
15
If the value shown for the configuration register is 0x2102, skip to step 18.
SEP 2009
K-65
continued

Step
16
Action
If the value shown for the configuration register is not 0x2102, enter the following command in the
order shown to change it:
configure terminal
configregister 0x2102

BTSRTR1#conf t
Enter configuration commands, one per line.
BTSRTR1(config)#configregister 0x2102
BTSRTR1(config)#
17
End with CNTL/Z.
Verify the change was entered properly by entering the following commands in the order shown:
exit
show version
A response which begins and ends similar to the following will be displayed:
BTSRTR1(config)#exit
BTSRTR1#sh ver
.
.
Configuration register is 0x101 (will be 0x2102 at next reload)
BTSRTR1#
18
If the filename is correctly written in the boot system line (substep 5 of step 13) and the configuration
register is properly set to the factory default of 0x2102, enter the following to determine if the router
will reboot to IOS:
reload

BTSRTR1#reload

K-66
SEP 2009
continued

Step
Action
19
20
21
After a successful reboot with IOS, proceed with other BTS router activities or remove power from the
router and disconnect it
22
If the router still will not successfully boot with IOS, proceed to Table K-12 and perform the extended
recovery procedure.
Extended Recovery from Boot

to ROMmon
Requirements If ROMmon boot recovery attempts fail using the

simple recovery method, this method must be used to reboot a BTS
router which has initialized with ROMmon. This method requires
additional equipment beyond the items necessary to load canned
configuration files into the BTS router. Extended recovery requires
formatting the CF memory card from the ROMmoninitialized router
and reloading the reformatted CF memory card with the required IOS
version.
Additional equipment required An additional, formatted, 32 MB CF
memory card with the required version of the IOS installed is required in
addition to the equipment and software required for BTS router canned
configuration installation. This card may be:
S A spare CF memory card which is loaded with the required IOS

version
S A CF memory card from an additional BTS router which is loaded

with the required IOS version
Recovery Follow the procedure in Table K-12 to perform an extended

recovery from a BTS router ROMmon initialization.
Table K-12: Extended Recovery from BTS Router ROMmon Boot
Step
Action
This procedure assumes the BTS router is powered and operating on ROMmon with the LMF
computer set up and connected to the router with an active HyperTerminal communication session. If
it is not, follow the procedure in Table K-2 to establish a HyperTerminal communication session.
Remove the CF memory card from the BTS router following the procedure in Table K-16.
Install the additional CF memory card in the router following the procedure inTable K-17.
SEP 2009
K-67
continued

Step
4
Action
Enter the following to obtain the filename of the IOS version loaded on the CF memory card:
dir slot0:

rommon 1 > dir slot0:
Directory of slot0:
1
7051976
rw
rommon 2 >
Note the exact filename displayed for the IOS version.

K-68
SEP 2009
continued

Step
6
Action
Enter the following to initialize the router with the IOS on the additional CF memory card:
boot slot0:IOS_filename

A successful IOS reboot operation will result in display of a response which begins and ends similar
to the following:
rommon 2 > boot slot0:mwr1900imz.1228.MC2b.bin
program load complete, entry point: 0x80008000, size: 0x6b99ac
Self decompressing the image :
################################################################### [OK]
Smart Init is enabled
smart init is sizing iomem
ID
00031A
MEMORY_REQ
TYPE
0X005F3C00 MWR1900 Mainboard

0X000F3BB0 public buffer pools
0X00211000 public particle pools
TOTAL:
.
.
.
0X008F87B0
System Configuration Dialog

Would you like to enter the initial configuration dialog? [yes/no]: n
If the router prompts with a question to enter the initial dialog as shown in step 6, above, type no and
press the Enter key to obtain the user EXEC mode prompt.
If the router prompts with Press RETURN to get started!, press the Enter key to obtain the
user EXEC mode prompt.
SEP 2009
K-69
continued

Step
9
Action
At the user EXEC mode prompt, enter the following to access the privileged EXEC mode:
enable

Router> enable
Router#
10
Remove the additional CF memory card from the BTS router following the procedure in Table K-16.
11
Install the original CF memory card in the router following the procedure inTable K-17.
12
Format the original CF memory card by entering the following:

format slot0:

Router#format slot0:
13

K-70
SEP 2009
continued

Step
14
Action
Format: Drive communication & 1st Sector Write OK...
Writing Monlib
sectors....................................................................
................
Monlib write complete
.
Format: All system sectors written. OK...
Format: Total sectors in formatted partition: 62560
Format: Total bytes in formatted partition: 32030720
Format: Operation completed successfully.
Format of slot0 complete
Router#
15
Copy the required IOS version to the formatted original CF memory card using the LMF computer and
a tftp server following the procedure in Table K-9.
16
If applicable, perform IOS initialization troubleshooting as described in Table K-11, steps 12 through
21.
SEP 2009
K-71
Entering or Changing BTS Router FE Interface IP Addresses

FE Interface IP Addresses and
Operating Parameters
It may be necessary to enter or change the IP addresses and/or operating

parameters for BTS router FE interfaces FE 0 and FE1 without making
other changes in the router configuration files. Procedures in this section
cover these operations.
Prerequisites
The following must be accomplished before entering or changing BTS

router FE port IP addresses and/or operating parameters:
S The user has read and understands the content of MWR 1941DC
Wireless Mobile Edge Router Software Configuration Guide; part

number 7813983
S BTS routers must have the required version of the IOS saved on their
installed CF memory card
S BTS routers must have power applied, be operating without alarms
other than span alarms, and have completed bootup to the user EXEC
mode prompt (BTSRTRbts#11>)
S The BTS router privileged EXEC mode password has been obtained
from the network administrator
Entering or Changing FE
Interface IP Addresses
To enter or change FE interface IP addresses, follow the procedure in

Table K-13.
Table K-13: Entering or Changing BTS Router FE Interface IP Addresses and Operating Parameters
Step
Action
* IMPORTANT
1
Obtain the correct IP addresses and subnet masks for the BTS router FE interfaces from the network
administrator.
If a HyperTerminal connection for BTS card/module MMI or BTS router (BTSRTR) communication
has not been created, create one as described in Table K-1 of this appendix.
Connect the LMF computer to the BTS router, and start a communication session as described in
Table K-2 in this appendix.
K-72
SEP 2009
continued
Step
4
Action
NOTE
Examples in this procedure show prompts for BTSRTRbts#11 and BTSRTRbts#12, but the
procedure can be used for any router in any BTS router group or a router running the canned
configuration file (BTSRTR1 or BTSRTR2).
At the BTSRTRbts#11> user EXEC mode prompt, enter the following to access the privileged
EXEC mode:
enable

BTSRTRbts#11> enable
Password:
Enter the privileged EXEC mode password.

BTSRTRbts#11> enable
Password:
BTSRTRbts#11#
At the BTSRTRbts#11# privileged EXEC mode prompt, display the FE interface IP addresses by
typing:
show ip interface brief

BTSRTRbts#11#
Interface
FastEthernet0/0
Serial0:0
FastEthernet0/1
Serial1:0
show ip interface
IP Address
OK?
192.168.146.1 YES
unassigned
YES
unassigned
YES
unassigned
YES
brief
Method
NVRAM
unset
unset
unset
Status
Protocol
up
up
BTSRTRbts#11#
SEP 2009
K-73
continued
Step
7
Action
For a FastEthernet0/0 (fa0/0) or FastEthernet0/1(fa0/1) interface which does not have a correct or an
assigned IP address, enter the following at the router prompt to access the global configuration mode:
configure terminal

BTSRTRbts#11# conf t
Enter configuration commands, one per line. End with CNTL/Z.
BTSRTRbts#11(config)#
At the global configure mode prompt, enter the following to access the configure interface submode
for the interface requiring IP address assignment/change:
interface fastethernetinterface#
Where interface# = 0/0 or 0/1, as applicable.

int fa0/1
BTSRTRbts#11(configif)#
At the configure interface submode prompt, assign or change the interface IP address by entering:
ip address IP_addr subnet_mask
Where:
IP_addr = the required IP address for the interface; for example, 192.168.147.1
subnet_mask = the required subnet mask for the interface; for example, 255.255.255.0
ip address
192.168.147.1
255.255.255.0
10
To complete configuration of the interface, enter the following parameter settings, one at a time,
pressing Enter after each:
duplex full
speed 100
keepalive 1
no shutdown

K-74
SEP 2009
continued
Step
11
Action
Return to the global configuration mode by entering the following:
exit

exit
12
If the IP address and/or parameters for the other FE interface on the router must be assigned or
changed at this time, repeat steps 8 through 11 for the other FE interface.
13
Once the correct parameters have been set for all FE interfaces, return to the privileged EXEC mode
prompt by holding down the Ctrl key and pressing z (Ctrl +z).
BTSRTRbts#11(configif)# ^z
01:11:27: %SYS5CONFIG_I: Configured from console by console
BTSRTRbts#11#
NOTE
Entering exit twice, pressing the Enter key after each entry, will also complete the interface
configuration and return the router to the privileged EXEC mode.
14
Save the interface configuration changes to the startup configuration file on the CF memory card by
copy runningconfig startupconfig

BTSRTRbts#11#
BTSRTRbts#11#
15
copy run start

Press Enter
BTSRTRbts#11# copy run start
BTSRTRbts#11# Destination filename [startupconfig]?
Building configuration...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!![OK]
BTSRTRbts#11#
SEP 2009
K-75
continued
Step
Action
16
If all FE IP address entries/changes for the router are complete, enter the following to return the router
to user EXEC mode:
disable

BTSRTRbts#11#
BTSRTRbts#11>
disable
17
If no other router requires the FE interfaces to be assigned/changed, proceed to step 20.
18
If FE interfaces on another router must be assigned/changed, disconnect the 8contact modular plug
from the current router CONSOLE port and connect it to the CONSOLE port of the other router.
19
Press the Enter key, and when the router user EXEC mode prompt appears repeat steps 3 through 16
for the other router.
20
When the router is in user EXEC mode, close the HyperTerminal session and disconnect the LMF
computer and additional components from the BTS router.
K-76
SEP 2009
Example BTS Router Canned Configuration Files

BTS Router Canned
Configuration File
This section presents listings of the blue and red router canned
configuration file contents for the MWR 190027 and MWR 1941DC
BTS routers. The blue router is the primary router on the BTS LAN
subnet 192.168.146.0, and the red router is the primary on BTS LAN
subnet 192.168.147.0. The canned configuration files allow
communication with the BTS routers for both onsite FE cabling
connectivity verification and for downloading the routers from the
network with the full, sitespecific operational configuration.
Obtaining the Latest
Configuration File Content
The files included here are for example only. The correct canned
configuration file content for each BTS router should be generated at the
OMCR using the /screl/active/bin/gen_btsrtr_canned_config.ksh script.
Configuration File Examples
Examples of both configuration files are provided in the following

subsections.
SEP 2009
K-77
continued
Blue BTS Router Canned

Configuration
! Canned Config file for BTSRTR1
version 12.2
!
hostname BTSRTR1
!
no logging console
!
!
ip subnetzero
ip classless
ip pim bidirenable
!
disableeadi
memorysize iomem 25
!
redundancy
mode ycable
standby useinterface Loopback101 health
standby useinterface Loopback102 revertive
standby useinterface Multilink1 backhaul
interface loopback 101
description BTSRTR health loopback
no ip address
description BTSRTR revertive loopback
no ip address
!
! configure 1 DS0 for BTSRTRLINK
!
controller T1 0/0
description 1st span on BTSRTR
framing esf
linecode b8zs
cablelength short 133
clock source line
channelgroup 0 timeslots 124 speed 64
! MLPPP bundle with BTSRTRLINK.
! This performs IPCP with RPM when BTSRTR is rebooted
interface Multilink 1
ip address negotiated
no ip routecache
no cdp enable
ppp multilink
K-78
SEP 2009
continued
multilinkgroup 1
no shutdown
!
! Setup Serial Interface for PPP and IPCP, no MLPPP at this time
!
interface Serial0/0:0
no ip address
encapsulation ppp
keepalive 1
ppp multilink
multilinkgroup 1
no shutdown
!
! Setup Ethernet Interfaces and HSRP between them
!
interface FastEthernet0/0
ip address 192.168.146.1 255.255.255.0
keepalive 1
speed 100
fullduplex
standby 1 timers 1 3
standby 1 preempt
standby 1 priority 100
standby 1 ip 192.168.146.3
standby 1 name one
standby 1 track Fa0/1 10
standby 1 track Multilink1 10
! Track the router health interface
standby 1 track Loopback101 10
! Track the router revertive (compensation) interface
no shutdown
!
ip address 192.168.147.1 255.255.255.0
keepalive 1
speed 100
fullduplex
standby 2 preempt
standby 2 ip 192.168.147.3
standby 2 name two
no shutdown
!
! Set a default route to RPM thru BTSRTRLINK
!
SEP 2009
K-79
continued
ip route 0.0.0.0 0.0.0.0 Multilink 1

!
line con 0
exectimeout 15 0
password cisco
line aux 0
login
password cisco
line vty 0 4
login
password cisco
end
K-80
SEP 2009
continued
Red BTS Router Canned

Configuration
! Canned Config file for BTSRTR2
version 12.2
!
hostname BTSRTR2
!
no logging console
!
!
ip subnetzero
ip classless
ip pim bidirenable
!
disableeadi
memorysize iomem 25
!
redundancy
mode ycable
standby useinterface Loopback101 health
standby useinterface Loopback102 revertive
standby useinterface Multilink1 backhaul
description BTSRTR health loopback
no ip address
description BTSRTR revertive loopback
no ip address
!
! configure 1 DS0 for BTSRTRLINK
!
controller T1 0/0
description 1st span on BTSRTR
framing esf
linecode b8zs
cablelength short 133
clock source line
channelgroup 0 timeslots 124 speed 64
! MLPPP bundle with BTSRTRLINK.
! This performs IPCP with RPM when BTSRTR is rebooted
interface Multilink 1
ip address negotiated
no ip routecache
no cdp enable
SEP 2009
K-81
continued
ppp multilink
multilinkgroup 1
no shutdown
!
! Setup Serial Interface for PPP and IPCP, no MLPPP at this time
!
interface Serial0/0:0
no ip address
encapsulation ppp
keepalive 1
ppp multilink
multilinkgroup 1
no shutdown
!
! Setup Ethernet Interfaces and HSRP between them
!
ip address 192.168.146.2 255.255.255.0
keepalive 1
speed 100
fullduplex
standby 1 preempt
standby 1 ip 192.168.146.3
standby 1 name one
no shutdown
!
ip address 192.168.147.2 255.255.255.0
keepalive 1
speed 100
fullduplex
standby 2 preempt
standby 2 ip 192.168.147.3
standby 2 name two
no shutdown
!
! Set a default route to RPM thru BTSRTRLINK
K-82
SEP 2009
continued
!
ip route 0.0.0.0 0.0.0.0 Multilink 1
!
line con 0
exectimeout 15 0
password cisco
line aux 0
login
password cisco
line vty 0 4
login
password cisco
end
SEP 2009
K-83
Network Interface Card (NIC) Configuration Worksheet

Network Interface Card (NIC) Configuration Worksheet
Record of original NIC
configuration
Advanced tab of NIC hardware Properties dialog box

Table K-14: Advanced Tab Property List Box Connection Settings Original
Operating System
Property:
Windows XP
Speed & Duplex
Windows 2000
Connection Type
Original Value:
Internet Protocol (TCP/IP) Properties dialog box General tab

____ Obtain an IP address automatically
____ Use the following IP address:
IP address:
_______________________________
Subnet mask:
_______________________________
Default Gateway: _______________________________
BTS router communication NIC
configuration
Advanced tab of NIC hardware Properties dialog box

Table K-15: Advanced Tab Property List Box Connection Settings for BTS Router
Communication
Operating System
Property:
OTI Test Value:
Windows XP
Speed & Duplex
100 Mb Full
Windows 2000
Connection Type
100 Mbps Full_Duplex
Internet Protocol (TCP/IP) Properties dialog box General tab

____ Obtain an IP address automatically
X Use the following IP address:
IP address:
100.100.100.1
Subnet mask:
K-84
255.255.255.252
SEP 2009
External BTS Router Compact Flash (CF) Memory Card Installation and
Removal
Removal
CF Memory Card
Installation/Removal
Operations
Procedures in this section apply to the removal or installation of the

external BTS router CF memory card
Tools Required
The following tools are required to perform procedures included in this

section:
S Number 2 crossrecess screwdriver

S Approved antistatic wrist strap or equivalent personal grounding
device
Figure K-5: Router CF Memory Card Removal

CF Memory
Card Cover
Card Ejector
Lever
ACT
LED
PUSH IN
CF Memory
Card
ROTATE OUT
Captive
Screws
SEP 2009
SC4812T0012
K-85
Removal continued
BTS Router CF Memory Card
Removal and Installation
The following procedures cover removal and installation of the CF

memory card used to store the IOS and configuration data for the
external BTS router.
Removing a CF memory card Refer to Figure K-5 and follow the
procedures in Table K-16 to remove the CF memory card from the
external BTS router models.
NOTE
The CF memory card may be removed and installed while
power is applied to the router.
Table K-16: External BTS Router Flash Memory Card Removal

Step
Action
Refer to MWR1941DC Mobile Wireless Edge Router Hardware Installation Guide; part number
7815827 for the latest information, cautions, and notes on BTS router CF memory card removal and
installation prior to proceeding with the following steps.
! CAUTION
Do not remove the CF memory card while there are read or write operations occurring on the card.
Removing the card during these operations will cause the router to shut down and damage the file
system.
If power is applied to the router, be sure there are no read or write operations in progress for the card
by verifying the ACT indicator LED is not lighted or lighting intermittently.
Using a crossrecess screwdriver, fully loosen the captive screws securing the flash memory card slot
cover to the router, and remove the cover.
Remove the CF memory card by performing the following:

1. Rotate the end of the card ejector lever until it is pointing out 90_ to the router front panel (see
Figure K-5).
2. Push the card ejector lever straight into the router to unseat the CF memory card.
3. Carefully pull the card out of the slot.
Place the CF memory card on an antistatic surface or in an antistatic container.
K-86
SEP 2009
Removal continued
Installing a Flash Memory Card Refer to Figure K-5 and follow the
procedures in Table K-17 to install the CF memory card in an external
BTS router
Table K-17: External BTS Router Flash Memory Card Installation
Step
Action
Refer to MWR1941DC Mobile Wireless Edge Router Hardware Installation Guide; part number
7815827 for the latest information, cautions, and notes on BTS router CF memory card removal and
installation prior to proceeding with the following steps.
If the flash memory slot cover is installed, use a crossrecess screwdriver to fully loosen the captive
screws securing the cover to the router, and remove the cover (see Figure K-5).
Install the CF memory card by performing the following:

1. Hold the CF memory card with the label facing up and the connector end pointing toward the
router.
2. Carefully insert the connector end into the flash memory card slot.
3. Push the CF memory card into the slot to seat it in the slot connector.
The card ejector lever will extend out of the router as the card is seated.
4. Pull on the card ejector lever to fully extend it from the router, and rotate it to the left to its stowed
position to latch the card in the slot (see Figure K-5).
SEP 2009
K-87
Removal continued
Notes
K-88
SEP 2009
Appendix L: MMI Cable Fabrication

Appendix Content
MMI Cable Fabrication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Wire Run List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEP 2009
L-1
L-1
L-1
L-1
L-2
Table of Contents
continued
Notes
SEP 2009
MMI Cable Fabrication

L
Purpose
When the Motorola SLN2006A MMI Interface Kit is not available, a

cable can be fabricated by the user to interface a ninepin serial
connector on an LMF computer platform with an MMI connector on
GLI cards and other Motorola BTS assemblies. This section provides
information necessary for fabricating this cable.
Required Parts
Table L-1: Parts Required to Fabricate MMI Cable

Item
Part Number
Qty
Description
Motorola 3009786R01
Ribbon cable assembly, 1.524 M, one 8contact MMI

connector, one 10contact connector
AMP 7498141,
Belkin A4B202BGC,
or equivalent
Receptacle kit, unassembled, 9position, socket contacts,

unshielded, metal or plastic shell, solder or crimptype
contacts
Cable Details
Figure L-1 illustrates the details of the fabricated MMI cable.
Figure L-1: Fabricated MMI Cable Details
8Contact MMI Plug

Socket Numbering
(Mating Side)
Item B
1 3 5 7
DB9 Plug
Socket Numbering
(Mating Side)
5
4 3 2 1
2 4 6 8
9
8 7 6
Item A: Cable assembly 3009786R01 (with 10contact plug removed)
FABRICATION NOTES:
1. Remove 10contact connector from ribbon cable of cable assembly 3009786R01
2. Separate wires at unterminated end of ribbon cable as required to connect to DB9
connector contacts
3. Dark wire on ribbon cable of cable assembly 3009786R01 connects to pin 1 of the
8contact plug
4. Strip three ribbon cable wires with connections specified in Table L-2 and connect to
DB9 plug contacts as specified in Table L-2
5. Shorten unconnected ribbon cable wires enough to prevent contacting DB9
contacts, leaving enough wire to egage any strain relief in the DB9 connector shell
SEP 2009
MMIFAB0010
L-1
continued
Wire Run List
Table L-2 provides the wire run/pinout information for the fabricated
MMI cable.
Table L-2: Fabricated MMI Cable Wire Run List

8CONTACT MMI
PLUG CONTACT
L-2
DB9 PLUG
CONTACT
No Connection (NC)
NC
NC
NC
NC
SEP 2009
Index
Numbers
Agilent E7495
calibration, power sensor, F-3
IP address, setting, F-2
100BaseT connectors, GLI, 7-45
Alarm and Span Line Cable Pin/Signal Information,

3-17
10BaseT/10Base2 Converter, 1-9

2way Splitter, 1-14
ALARM LED, GLI, 7-45
3Sector Duplexed Directional Coupler to RFDS

Cabling Table, H-23
3CPCCOMBO CBL, 1-10
4812ET RF Cabinet Internal FRU Locations, H-3
6Sector Duplexed Directional Coupler to RFDS
Cabling Table, H-24
Alarm Monitor window, 3-149

Alarm Reporting Display, 3-149
All Cal/Audit procedure, 3-131
All RX, 4-3
All tests fail on a single antenna, Troubleshooting,
RFDS, 7-26
All TX, 4-3
All TX/RX, 4-3
Acceptance Test Procedures ATP , 1-3
AMR, 1-26
ACTIVE LED
GLI, 7-44
MCC, 7-47
Anritsu MT8212B
ATP
alternate test setup, 3-92
TX and RX test setup, 3-89
Calibrating
CW generator, 3-107
power meter zeroing, 3-105
TX analyzer, 3-106
TX calibration, test setup, 3-83
Advantest R3267, GPIB Address, F-5

Advantest R3465, Calibrating Test Cable, F-1 , F-24
Advantest R3465 Communications Test Set GPIB
Address, F-7
Advantest R3562, GPIB Address, F-8
Agilent 8935 Series E6380 (formerly HP 8935) Test
Set GPIB Address, F-9
Agilent E4406A
calibration, F-1 , F-22
GPIB Address, F-11
Agilent E4418 power meter, GPIB address, setting,
F-13
Agilent E4418B, 3-73
Agilent E4438C Signal Generator, GPIB Address,
F-15
SEP 2009
Antenna connections, 4-5

Applying AC Power, 2-8
ATP
Code Domain Power, 4-14 , 4-15
Frame Error Rate (FER), 4-16
generate report, 4-19
Report, 4-19
test matrix/detailed optimization, C-1
Test Prerequisites, 4-4
Test Procedure, 4-6
test setup, 3-84
Advantest R3267/R3562, DRDCs, 3-86 , 3-87
Index-1
Index
continued
automated calibration file transfer, 6-1

process description, 6-1
GLI3 and LMF actions flowchart, 6-3
user and LMF actions flowchart, 6-2
upload procedure, 6-4
Cable
GPIB, 1-12
LAN Cable, 1-13
Calibrating, 3-111
Setting Loss Values, 3-121
Timimg Reference, 1-12
Basic Troubleshooting Overview, 7-1

Battery Charge Test (Connected Batteries), 2-14 ,
2-15
Bay Level Offset calibration, description, 3-123
Bay Level offset calibration failure, 7-10
BBX, gain set point vs SIF output considerations,
D-1
CCCP Backplane, H-6

CCCP Backplane Troubleshooting, Procedure, 7-20
CCCP shelf, 1-26
Cable Calibration, Manual, 3-78 , 3-118

cable calibration, automatic, test setup, Agilent
E4406A/E4432B, 3-115
Cable Calibration Setup, Automatic, 3-78 , 3-112
BBX2, 1-26
Cable calibration setup, diagrams, 3-112
BBX2 Connector, 7-20
cabling, Fast Ethernet, required cables,

BTSRTRtoframe, 5-27
BLO
Calibration Audit, 3-135
Download, 3-134
CAL File, create, 3-136

Calibrate BLO, 3-124
BPR, 1-17
Calibrate Test Cabling, Communications System

Analyzer, 3-112
BSS, 1-17
BTS
Ethernet LAN interconnect diagram, 3-42
system software download, 3-3
BTS Cabinet, 1-31
BTS Packet Router, BPR, 1-17
Calibrating
Cables, 3-111
Test Equipment, 3-104
Anritsu MT8212B, 3-105
manual, 3-104
Calibrating Test Cable, Advantest R3465, F-1 , F-24
BTS Router
change or upgrade IOS version, K-35
communication session, K-5
download configuration files, minimum canned,
K-8
IOS verification, canned config installation, K-15
IOS version verification
file sequence position, K-36
required equipment and software, K-35
TFTP server, CF memory card load, K-17
Calibrating Test Cabling, Signal Generator &

Spectrum Analyzer, 3-118
BTS router communication session, establishing, K-6
calibration, Gigatronics 8542B, F-1 , F-23
BTS router connections

FE verification, K-7
programming, K-7
Calibration Audit failure, 7-11
Calibration
Cable, 1-8
data file calibration, BLO, 3-125
InService, I-18
Test Equipment, 1-8
Test Cable Calibration, 1-8
Test Equipment Calibration, 1-8
Create CAL File, 3-136
Calibration data, Generator, 3-109

edit, 3-109
set, 3-109
BTSRTR, 1-17
calibration data file, description of, BLO, 3-125
BTSRTRGRP, 1-17
Calibration Procedures Included, Automatic, 3-104
Index-2
SEP 2009
Index
continued
Cannot communicate to Communications Analyzer,

7-6
Cannot communicate to Power Meter, 7-6
Cannot Download DATA to any device card, 7-8
Cannot ENABLE device, 7-9
Cannot Log into cellsite, 7-2
Cannot perform carrier measurement, 7-14
Cannot perform Code Domain Noise Power
measurement, 7-13
Cannot perform Rho or pilot time offset
measurement, 7-13
Cannot perform Txmask measurement, 7-12
CCD, 1-26
CDF, site equipage verification, 3-3
CDMA
allocation diagram for the North American, cellular
telephone frequency spectrum, E-5
optimization/ATP test matrix, C-1
CDMA LMF, Product Description, 1-9
Cell Site
equipage verification, 2-2
types configuration, 3-2
Communications test set. See Test equipment

communications test set, TX acceptance tests, 4-3
Components Located on CIO Card, H-10
Configuration, 1-20
BTS Router, IOS verification, K-15
OMCR FTP file transfer, K-9
operations overview, BTS Router, K-1
Connecting test equipment to the BTS, 3-72
Connector Functionality
Backplane, Troubleshooting, 7-19
Troubleshooting, Backplane, 7-19
Copy NEC Files from OMCR, 3-9
CSM, 1-26
Clock Source, 3-55
clock source, select, 3-55
Enable, 3-56
LEDs, 3-60
MMI terminal connection, illustration, 3-64
Reference Source Configuration Error, 7-18
system description, 3-59
Troubleshooting, 7-17 , 7-18
CSM clock source, select, 3-55
CSM frequency verification, 3-63
Customer I/O, 1-27
Cell Site Field Engineer CFE, 1-3

CEPT, 1-17
CF, 1-18
DC Power Pretest (BTS Frame), 2-10 , 2-11
CF Memory Card, load using a TFTP server, K-17

CF memory card, installation and removal, K-85
DC Power Problems, CCCP Backplane

Troubleshooting, 7-23
Channel Service Unit, 3-15
DC/DC Converter, LED Status Combinations, 7-42
CIO, 1-26
Detailed, optimization/ATP test matrix, C-1
CIO Connectors, 7-20
Digital Control Problems, 7-21

CCCP Backplane Troubleshooting, 7-21
CLI, 3-31
Command Line Interface, 3-25
Format Conventions, 3-31
Logging Out, 3-37
Digital Multimeter, 1-12

Directional Coupler, 1-12
Code Domain Power Test, 4-14
diversity receive path, definition, 3-123

companion frame, 3-124
standalone frame, 3-123
Command Line Interface, 3-31
diversity RX path. See diversity receive path
command terminal, settings, 3-12 , K-2
Download
BLO, 3-134
BTS system software, 3-3
NonGLI2 Devices, 3-52
Code Domain Power, ATP, 4-14 , 4-15
Communication Session, BTS Router, K-5

Communications System Analyzer, 1-11
SEP 2009
Index-3
Index
continued
ROM Code, G-1

Duplex Router, 1-18
Gain set point, D-1
Duplexer/Directional Coupler DDC, 1-26 , 1-27 ,

1-28 , 1-33
General optimization checklist, test data sheets, A-5

Gigatronics 8542 power meter, calibration, F-1 , F-23
Gigatronics 8542B power meter, illustration, F-17

Gigatronics Power Meter, 3-73
GLI, LED Status, 7-44
E4406A, calibration, F-1 , F-22

EBR, configure GLI3, 5-27
Enable
CSMs, 3-56
MCCs, 3-58
Equipment Overview, 1-22 , 1-23 , 1-24
Equipment warm-up, 3-78
establish MMI communication, 3-38
Ethernet LAN
hub, 1-9
interconnect diagram, 3-42
switch, 1-9
ETIB I/O Connectors, H-12
Every test fails, Troubleshooting, RFDS, 7-25
External BTS Router
CF memory card
installation, K-85
removal, K-85
memory card
installation, K-85
removal, K-85
External Test Equipment Removal, 6-5
F
Fast Ethernet (FE) connectors, GLI, 7-45
FE, 1-18
FER test, 4-16
file transfer protocol, configuring for, 5-35
Files, calibration data file, BLO, 3-125
Folder Structure Overview, 3-6
Frame Error Rate, 4-8 , 4-9
ATP, 4-16
FREQ Monitor Connector, CSM, 7-43
Frequency counter, optional test equipment, 1-14
Full Optimization, 4-3
Index-4
GLI Connector, 7-19

GLI Ethernet A and B Connections, 7-20
GLI2, 1-26
GLI3
backhaul mode
change required, 5-8
configure for EBR, 5-27
configure for IBR, 5-12
IBR full span, 5-15
determining, 5-5
IBR fractional span, 5-20
backhaul modes, 5-4
code loading
operating mode effect, 5-3
preload procedure, 5-10
recommended procedure, 5-4
code version
change required, 5-8
determining, 5-5
GPIB, power meter, Gigatronics 8542B, F-17
GPIB Cable, 1-12
GPIB Address
Advantest R3267, F-5
Agilent (formerly HP) 8935, F-9
Agilent E4406A, F-11
Agilent E4438C, F-15
GPS
receiver operation, test data sheets, A-6
Test Equipment Setup, 3-63
GPS Initialization/Verification
estimated position accuracy, 3-64
surveyed position accuracy, 3-64
GPS satellite system, 3-57
Graphical User Interface, 3-26
GUI, 3-26
Graphical User Interface, 3-25
SEP 2009
Index
continued
Logging Out, 3-36
MCC, 7-47
PA, 7-47
LFR, receiver operation, test data sheets, A-7
LMF Hardware Requirements, 1-9
LFR/HSO, Test Equipment Setup, 3-63
High Availability BTS Router, 1-19
LIF, Load Information File, 3-7
High Stability 10 MHz Rubidium Standard, 1-14
HyperTerminal Connection, Creating, 3-12
LMF, 3-5
1X FER acceptance test, 4-3
Installation and Update Procedures, 3-8
Termination and Removal, 6-10
TX acceptance tests, 4-3
LMF Home Directory, 3-7
I and Q values, B-1
LMF Operation, 3-25
IBR, configure GLI3, 5-12
LMF Removal, 6-10
IBR Span Configuration Verification, 6-5
Load Center Wiring, 2-7
InService Calibration, I-18

preliminary Agilent test equipment setup, I-3 , I-6
Load Information File, 3-7
Individual ATP Test Background

Pilot Time Offset, 4-13
Tx Mask, 4-10
Waveform Quality (Rho), 4-12
Logging Out, 3-36

CLI, 3-37
GUI, 3-36
Highimpedance Conductive Wrist Strap, 1-13

HSO, 1-26
LMF BTS displays, 3-26
Logging In to a BTS, 3-32
Initial Installation of Boards/Modules, preliminary

operations, 2-2
Login
CLI, 3-35
GUI, 3-33
Initial power tests, test data sheets, A-4
LORANC Initialization/Verification, 3-70
Intended reader profile, 1-2
LPAC Interface Board, H-11
Intercabinet I/O, 1-28
Internal FRU, 1-32

IOS Version, change or upgrade, BTS Router, K-35
IP Addresses, Agilent E7495A, 3-95
MMI Connector
CSM, 7-44
GLI, 7-45
MCC, 7-48
ISB Inter Shelf Bus connectors, 7-19

Itasca Alarms Test Box, 1-14
L
LAN
BTS frame interconnect, illustration, 3-42
Tester, 1-14
SEP 2009
MCC, Enable, 3-58

MMI Connection, 3-38
fabricated MMI cable, 3-39
IS97 specification, B-1
LED Status, 7-42

BBX, 7-47
CSM, 3-60 , 7-43
DC/DC Converter, 7-42
GLI, 7-44
major components, 1-22
MMI equipment setup

cable CGDSMMICABLE219112, 3-39
Kit SLN2006A, 3-39
Module status indicators, 7-42
MPC, 1-26
MultiFER test Failure, 7-16
MWR 1900 BTS Router, configuration overview,
K-1
Index-5
Index
continued
N
NEC files, site type and equipage data information,
2-1
NECF, 3-2
network, transport
configuration, 5-1
determine code version, 5-5
determine GLI3 backhaul mode, 5-5
FTP, 5-33
security, 5-33
SFTP, 5-33
software release requirements, 5-3
Network Element Configuration File. See CDF
New installations, 1-5
No AMR control, 7-22
No BBX2 control in the shelf, 7-22
No DC input voltage to Power Supply Module, 7-23
No DC voltage +5 +65 or +15 Volts to a specific
GLI2 BBX2 or Switch board, 7-24
No GLI2 Control through span line connection, 7-21
No GLI2 Control via LMF, 7-21
No GPS Reference Source, 7-17
No or missing MCC24 channel elements, 7-23
No or missing span line traffic, 7-22
NonGLI, Download, 3-52
North American, cellular telephone system frequency
spectrum, CDMA allocation, E-5
O
OMCR, FTP file transfer procedure, K-9
Online Help, 3-25 , 3-40
Optimization, 1-3
Optional Test Equipment, frequency counter, 1-14
Oscilloscope, 1-14
P
PA errors, 7-9
PA Module LED, 7-47
Pilot Gain, 4-12 , 4-13 , 4-14 , 4-16

See also PN
Ping, 3-41
PN
offset programming information, B-1
offset usage, B-1
PN Offset, B-1 , B-2 , B-3
PN offset per sector, B-1
PN Offset Usage , B-1
Advantest, I-11
Agilent 8935, I-9
Power Input, 7-19
Power meter
GPIB, Gigatronics 8542B, F-17
illustration, Gigatronics 8542B, F-17
Power Supply Module Interface, 7-19
Prepower tests, test data sheets, A-4
Preliminary operations
cell Site types, 2-1
test data sheets, A-3
External Test Equipment Removal, 6-5
IBR Span Configuration Verification, 6-5
LMF Removal, 6-10
Reconnect BTS T1/E1 Spans, 6-10
Reset All Devices and Initialize Site Remotely,
6-11
Procedures to Copy CAL Files From Diskette to the
CBSC, 7-2 , 7-6 , 7-8 , 7-9
Pseudorandom Noise. See PN
publications, required for upgrade, 1-15
Punch Block, 3-17
Pushbuttons and Connectors, GLI, 7-45
PWR/ALM LED
BBX, 7-47
CSM, 3-60
DC/DC Converter, 7-42
generic, 7-42
MCC, 7-47
MPC and EMPC Card, H-20
Packet Backhaul, defined, 1-20
Periodic optimization, 1-7
Receive Distribution Card RXDC, 1-33
Index-6
SEP 2009
Index
continued
receive path
calibration, 3-123
definition, 3-123
RSSI, 4-9
Receive Signal Strength Indication, 4-9

procedure, 4-17
testing, 4-18
Reduced ATP, 4-2
Reduced ATP passes but forward link problem
prevails, 7-12
Related Publications, 1-16
Removing and Installing LPAs for the SC 4812ET,
H-7
RX
acceptance tests, RSSI, 4-17
antenna VSWR, test data sheets, A-16
RX Acceptance Tests
Frame Error Rate, 4-8 , 4-9
RSSI, 4-9
RX and TX paths fail, Troubleshooting, RFDS, 7-25
RX path. See receive path
S
SC 4812 BTS Optimization/ATP Test Matrix, C-2
SC 4812ET BTS Combiner, H-8 , H-9 , H-16 , H-17 ,
H-18 , H-19 , H-21 , H-22 , H-25
Required Documents, 1-15

Required documents, 1-32
Required test equipment, communications system
analyzer, 1-11
SCLPA, convergence test data sheets, A-8

secure file transport protocol, configuring for, 5-35
Reset All Devices and Initialize Site Remotely, 6-11
Set Antenna Map Data, 3-143
RESET Pushbutton, GLI, 7-45
Set RFDS Configuration Data, 3-144
RF
Adapters, 1-13
Load, 1-12
Setting Cable Loss Values, 3-121
RF Cabinet Internal Assemblies and FRUs, 1-25
SIF, output considerations vs BBX gain set point, D-1
Setting Control Port, 3-15

Setting TX Coupler Loss Value, 3-122
50 Pair Punchblock, H-27

RF path calibration. See Bay Level Offset calibration
Signal Generator, 3-119
RFDS, Set Configuration Data, 3-144
signal generator, 1X FER acceptance test, 4-3
RFDS Cabling Details, H-22
Simplex Router, defined, 1-21
RFDS calibration
description, 3-145
procedure, 3-146
Site checklist, verification data sheets, A-2
Site, equipage verification, 3-3

Site equipage, NECF, 3-2
RFDS FRU, H-14
Site expansion, 1-6
RFDS Location, SC 4812ET, 1-30
SPAN I/O Functional Description, Introduction, H-13
RFDS parameters, 3-137

checking, 3-138
setting, 3-138
Span Line, T1/E1 Verification Equipment, 1-14
RFDS TSU Calibration Channel Frequencies, 3-145
Span line configuration, troubleshooting, 7-30
ROM Code, Download, G-1
Span Line connector , 7-19
ROM code, downloading, J-1 , J-2 , J-3
SPANS LED, GLI, 7-45
rommon, 1-20 , 1-21
Spectral Purity TX Mask, 4-8
RS232 to GPIB Interface, 1-10
Spectrum Analyzer, 1-14 , 3-119
RS232 GPIB Interface Box, F-18
Spectrum Analyzer , HP8594E, 3-73
SEP 2009
Span line, troubleshooting, 7-27
Index-7
Index
continued
STATUS LED, GLI, 7-45

Supported Test Sets, 3-73
SYNC Monitor Connector, CSM, 7-43
T
Telco Interface Board TIB, 1-33
terminal communication settings, 3-12 , K-2
Terminal Session, setup, BTS Router, K-2
Test data sheets
Alarm verification, A-17
general optimization checklist, A-5
GPS receiver operation, A-6
initial power tests, A-4
LFR receiver operation, A-7
prepower tests, A-4
preliminary operations, A-3
RX antenna VSWR, A-16
SCLPA convergence, A-8
site checklist, A-2
TX antenna VSWR, A-16
TX BLO, A-9 , A-14
verification of test equipment used, A-1
Test Equipment
Automatically Selecting, 3-98 , 3-99 , 3-101
Calibrating
Anritsu MT8212B, 3-105
automated, 3-104
manual, 3-104
Selecting, 3-96
Test equipment
See also Optional test equipment; Required test
equipment
system analyzer, 1-11
verification data sheets, A-1
test equipment connection
Ethernet, 3-94
GPIB
addresses, 3-95
COM port, 3-93
Serial
addresses, 3-95
COM port, 3-93
test equipment selection
Ethernet
automatic selection, 3-101
Index-8
manual selection, 3-101

prequisites, 3-100
GPIB
prerequisites, 3-96
network
prerequisites, 3-100
serial
prerequisites, 3-99
Test Equipment Setup, GPS & LFR/HSO, 3-63
Test Equipment Setup Chart, 3-74
Test equipment setup RF path calibration, 3-128
Test Set Calibration , Background, 3-103
TFTP, loading a CF memory card procedure, K-17
Timing Reference Cables, 1-12
timing reference sources, 3-61
transmit path
calibration, 3-123
definition, 3-123
Transmit TX path calibration, 3-129
Transmit/Receive Module TRX, 1-32
transport configuration, introduction, 5-1
Troubleshooting
DC Power Problems, 7-23
Set span configuration, 7-30
span problems, 7-27
troubleshooting
Ethernet LAN, 7-2
GLI IP address, 7-3
signal generator communication, 7-7
Troubleshooting Forward Link Failure (BTS Passed
Reduced ATP), 7-12
TSU NAM, programming
description, 3-140
parameter ranges, 3-142
parameters, 3-141
procedure, 3-147
TX
acceptance tests, equipment setup, 4-3
antenna VSWR, test data sheets, A-16 , A-17
SEP 2009
Index
continued
BLO test data sheets, A-9 , A-14
TX Pilot Time Offset ATP Background, 4-13
TX and RX Frequency vs Channel , E-3

TX Audit Test, 3-135
TX Waveform Quality (Rho) ATP Background, 4-12
TX calibration, 3-131
All Cal/Audit, 3-131
setup, 3-79
Advantest R3267, I-16
Advantest R3465, 3-80
Agilent E4406A, I-16
U
updating calibration data files, automated, 6-1
tx fine adjust, B-1

TX Mask Verification, spectrum analyzer display,
illustration, 4-11
TX Output Acceptance Tests
Code domain power, 4-14
Spectral purity TX mask, 4-8
Waveform quality (rho), 4-8
TX Spectral Purity (Tx Mask) ATP Background, 4-10
Verify, test equipment used, test data sheets, A-1
W
Walsh channels, 4-14
Warmup, 1-8
Waveform Quality (rho), 4-8
TX path
See also transmit path
audit, 3-135
WIC, 1-21
TX Path Calibration, 3-124
TX path calibration, 3-131
XCVR Backplane Troubleshooting, 7-19
SEP 2009
worksheet, software release and backhaul mode, 5-37
Index-9
Index
continued
Notes
Index-10
SEP 2009
*68P09293A75A*
68P09293A75A
Technical
Information
1X SC4812ET BTS OPTIMIZATION/ATP
SOFTWARE RELEASE 2.22.0.X

800 AND 1900 MHZ
CDMA
ENGLISH
SEP 2009
68P09293A75A
1X SC4812ET BTS OPTIMIZATION/ATP

SOFTWARE RELEASE 2.22.0.X
800 AND 1900 MHZ
CDMA
SEP 2009
ENGLISH
68P09293A75A
Cellular Networks Customer Documentation
STANDARD MANUAL PRINTING INSTRUCTIONS

Filename:
Part Number: 68P09293A75A
68P09293A75A.pdf
APC:
379
Title: 1X SC4812ET BTS Optimization/ATP

Volume 1
of 1
Print Vendor: eDOC
Date SEP 2009
STANDARD SPECIFICATIONS FOR REFERENCEDO NOT MODIFY
PAPER:
1st. LEVEL TABS: 2nd. LEVEL TABS:
Body: 70 lb.
Inside Cover: 65 lb. Cougar
Tabs: 110 lb. Index
Binder Cover: Standard TED
cover 10 pt. Carolina
Single Sided
5 Cuts
Clear Mylar
Pantone 2706C
Black Ink
Single Sided
7 Cuts
Clear Mylar
White
Black Ink
FINISHING:
3Ring Binder
SlantD
3Hole Punched
(5/16in. dia.)
Shrink Wrap Body
Black ink for body, inside cover, and binder cover.
TAB and SHEET SIZE/QUANTITY
7X9
8.5x11 328
1st Level Tabs
11x17
Sheets = (Total Pages) / 2
2nd Level Tabs
NONSTANDARD SPECIFICATIONS
Tape Bound
Corner Stitch
Other: Meet with manager to determine the deliverable.
SPECIAL INSTRUCTIONS

BTS4812ET Opto R22

Uploaded by

Document Information

Original Title

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

BTS4812ET Opto R22

Uploaded by

Copyright:

Available Formats

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE

Computer Software Copyrights

All Rights Reserved

Usage and Disclosure Restrictions

High Risk Activities

Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Caring for the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Third Party computer software and trademarks . . . . . . . . . . . . . . . . . . . . . . . . .

When to Perform BTS RF Calibration and Acceptance Testing . . . . . . . . . . . .

General Test Equipment Selection, Calibration, and

Required Test Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Required Documents and Related Publications . . . . . . . . . . . . . . . . . . . . . . . . .

1X SC4812ET BTS Optimization/ATP

Table of Contents continued

BTS Equipment Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2: Preliminary Operations

Site Equipage Verification and Card/Module Installation . . . . . . . . . . . . . . . . .

Frame Identification Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PreDC Powerup test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Power Cabinet Battery Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Heat Exchanger Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Circuit Breaker Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prepare the LMF Computer for MMI Communication . . . . . . . . . . . . . . . . . . .

Optional Channel Service Units (CSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Punchblocks and Pin/Signal Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMF to BTS Connection Service Shelf Connection . . . . . . . . . . . . . . . . . . . .

Using the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Establishing an MMI Communication Session . . . . . . . . . . . . . . . . . . . . . . . . .

LMF Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pinging the Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Take Control of Packet BTS Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Download the BTS General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Download BTS Loading Packet GLI Devices . . . . . . . . . . . . . . . . . . . . . . . . .

Download BTS Loading NonGLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . .

Enabling Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CSM System Time GPS, LFR, and HSO/MSO Verification . . . . . . . . . . . . .

Test Equipment Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Equipment Connection to the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Equipment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Set Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting and Editing Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . .

1X SC4812ET BTS Optimization/ATP

Table of Contents continued

Bay Level Offset Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create CAL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RFDS Setup and Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration . .

Chapter 4: Automated Acceptance Test Procedure

Automated Acceptance Test Procedures TX & RX . . . . . . . . . . . . . . . . . . . . .

TX Spectral Purity Transmit Mask Acceptance Test . . . . . . . . . . . . . . . . . . . . .

TX Waveform Quality (rho) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . .

TX Pilot Time Offset Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TX Code Domain Power/Noise Floor Acceptance Test . . . . . . . . . . . . . . . . . . .

RX Frame Error Rate (FER) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . .

Receive Signal Strength Indication (RSSI) Acceptance Test . . . . . . . . . . . . . . .

Generate an ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5: Configuring Packet BTS Transport

GLI3 Required Software Release, Operating Mode, and Loading Code . . . . . .

GLI3 Card Software Version and Backhaul Mode . . . . . . . . . . . . . . . . . . . . . . .

Preloading GLI3 Cards in Packet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .