Comm Pro

1 of 20

Commissioning Procedure for Motorola BTS

INTRODUCTION : Commissioning is a process of integrating site i.e downloading site codes to BTS,

calibration of TRX unit, measurement of VSWR, measurement of reverse power, documentation of the site etc.TYPES OF BTS USED BY HUTHISION DELHI :

1. IN-CELL (900MHz)2. M-CELL (900MHz)3. HORIZON MACRO (900MHz & 1800MHz)4. HORIZON MACRO 2 (900MHz & 1800MHz)

All above BTS are manufacture by MOTOROLA

SECURITY LEVEL IN MOTOROLA BTS :

There are three-security levels in the MOTOROLA system. In the first security level, we can only check and display the status of DRI, RTF, MMS, RSL, CAGE, PATH etc.

In the second security level, we can modify ( i.e lock, unlock, in-service) the DRI.

In the third security level, we can login to BSC/to other site.

PROCEDURE FOR CHANGING SECURITY LEVEL :

a. Whenever you login to BTS, you are in security level one.b. For changing security level from one to two. Enter the following command;

MMI-RAM 1015 -> chg_l

Enter password for security level you wish to access: (press )Current security level is 2

c. For changing security level from one to third. Enter the following command;MMI-ROM 1015 -> chg_l

Enter password for security level you wish to access:3stoogesEnter password for security level you wish to access:4beatlesCurrent security level is 3

COMMANDS USED IN MOTOROLA BTS :

1. disp_siteThis command is used to check current site number (i.e logical id of the site). Whenever

you log in to BTS. You should to now site number, which is displayed on the screen when this command is execute.

Syntax & Massage after execution of this command is shown below:

MMI-RAM 1015 -> disp_siteCurrent site number is 30

© Alliance Telecom Pvt. Ltd.

2 of 20


Note site number is different for different sites.

2. state (site number) dri (dri id)This command is used to check status of all/particular dri. This command gives status of

dri ( i.e how many dri are busy, dri are busy on which rtf, how many dri are equipped, time & date of last action of dri).


MMI-RAM 1015 -> state 30 dri * *

DEVICE STATUS INFORMATION FOR LOCATION 30:OPER STATES: D:Disabled E:Enabled B:BusyADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition RelatedDevice State Reason dd/mm hh:mm:ss Function------------- ----- ------------------------- --------------- ---------DRI 0 0 0 D-L NO REASON 08/09 16:49:22 NoneDRI 0 1 0 B-U NO REASON 08/09 16:49:56 RTF 0 0 0DRI 0 2 0 E-U NO REASON 08/09 16:35:08 NoneDRI 0 3 0 E-U NO REASON 08/09 16:35:14 NoneDRI 1 0 0 B-U NO REASON 08/09 16:35:08 RTF 1 0 0DRI 1 1 0 E-U NO REASON 08/09 16:35:14 NoneDRI 1 2 0 E-U NO REASON 08/09 16:34:46 NoneDRI 1 3 0 E-U NO REASON 08/09 16:34:46 NoneDRI 2 0 0 B-U NO REASON 08/09 16:35:02 RTF 2 0 0DRI 2 1 0 E-U NO REASON 08/09 16:35:02 NoneDRI 2 2 0 E-U NO REASON 08/09 16:35:08 NoneDRI 2 3 0 E-U NO REASON 08/09 16:35:08 None

END OF STATUS REPORT

In the above massage, we see that there are twelve DRI are equipped. Four dris in all sector. DRI with id starting from 0 is in first sector, similarly DRI with id starting from 1 is in second sector, in the same way, DRI with id starting from 2 is in third sector. In this way DRI 0 0, 0 1, 0 2, 0 3 are in first sector, DRI 1 0, 1 1, 1 2, 1 3 are in second sector, DRI 2 0, 2 1, 2 2, 2 3 are in third sector. In the device row DRI with id show. In the state row, status of DRI show ( D means DRI are disable, E means DRI are enabled, L means DRI are locked, U means DRI are unlocked). Last transition shows the time when DRI gets last reset. In the related function row, which one rtf is on which DRI.

3. state (site number) rtf (rtf id)This command is used to check the status of all/particular rtf. This command gives the

status of the rtf. Syntax & Massage after execution of this command is shown below:

MMI-RAM 1015 -> state 30 rtf * *


3 of 20


FUNCTION STATUS INFORMATION FOR LOCATION 30:OPER STATES: E:Enabled B:Busy ADMIN STATES: E:Equipped

Last Transition RelatedFunction State Reason dd/mm hh:mm:ss Device------------- ----- ------------------------- --------------- ---------RTF 0 0 0 B-E NO REASON 08/09 16:34:47 DRI 0 0 0RTF 1 0 0 B-E NO REASON 08/09 16:34:50 DRI 1 0 0RTF 2 0 0 B-E NO REASON 08/09 16:34:47 DRI 2 0 0

END OF STATUS REPORTIn the above massage, all information is same as DRI command.

4. disp_cal_data (site number) dri (dri id)This command is used to display calibration data of the particular DRI.


MMI-RAM 1015 -> disp_cal_data 30 dri 0 0

DRI ID: 0 0 0Data read from transceiverStore Calibration Data:disabledCalibration Data (All values in Hex):Transmit Power Offsets = 3Receiver System Data:Antenna Number 1 2 3 4 5 6------------------------------------------------- 9b3, 9b3, 9b3, b4d, b4d, b33, 9b3, 9b3, 9b3, b33, b4d, b33, 9cd, 9cd, 9e6, b80, b80, b80, a4d, a66, a4d, b9a, b9a, b9a, a66, a66, a80, b4d, b4d, b66, a1a, a1a, a1a, ae6, ae6, ae6, 9b3, 9b3, 9b3, a9a, a9a, a9a, 980, 980, 980, a80, a80, a80, 980, 980, 980, a80, a80, a80, 94d, 980, 980, ab3, ab3, ab3, 9b3, 980, 9b3, ae6, ae6, ae6, 9e6, 9e6, 9e6, ae6, ae6, ae6, 980, 980, 980, a66, a4d, a66, 94d, 94d, 94d, a1a, a1a, a1a, 980, 980, 980, a80, a80, a66, 9cd, 9cd, 9cd, acd, acd, acd,

5. disp_cell_s (site number)This command is used to check how many calls are going on in all sectors.


MMI-RAM 1015 -> disp_cell_s 30


4 of 20


Start of report for LOCATION 30:

GSM CELL ID

MCC 404 404 404MNC 11 11 11LAC 109 (006Dh) 109 (006Dh) 109 (006Dh)CI 18521 (4859h) 18522 (485Ah) 18523 (485Bh)RAC 109 (006Dh) 109 (006Dh) 109 (006Dh)-------------------------------------------------------------------------------Primary Freq Type PGSM PGSM PGSMSecondary Freq Type N/A N/A N/ABCCH Frequency 69 72 67-------------------------------------------------------------------------------

Status Unbarred Unbarred UnbarredGPRS Status Unbarred Unbarred UnbarredEGPRS Status EGPRS Unavail EGPRS Unavail EGPRS UnavailPDCH Status PD Available PD Available PD AvailableRES PDCH Requested 1 1 1SW PDCH Requested 1 1 1Reset in Prog No No NoGPRS Reset in Prog No No NoSPI in Prog No No NoBSS BSSAP Prhb NA NA NAMSC BSSAP Prhb NA NA NASPI/MSC SCCP Prhb NA NA NAAccClass Bar None None NoneGPRS AccClass Bar 4 4 4EGPRS Chan Req Unavail Unavail UnavailFull Power Mode OFF OFF OFFExt Range Mode OFF OFF OFFActive PCU Site 0 0 0

FREE INUSE UNAVL FREE INUSE UNAVL FREE INUSE UNAVL ----- ----- ----- ----- ----- ----- ----- ----- --SDCCH 12 4 0 14 2 0 14 2 0Norm Outer TCH/F 9 18 0 21 6 0 17 2 0Norm Inner TCH/F 0 0 0 0 0 0 0 0 0Ext Outer TCH/F 0 0 0 0 0 0 0 0 0


5 of 20


PD CHANNEL 2 0 0 2 0 0 2 0 0EGPRS PD CHANNEL 0 0 0 0 0 0 0 0 0

End of Report.Numbers of inuse traffic channels shows, numbers of calls going on in the all sectors. First group shows first sectors, second group shows second sectors, and third group shows third sectors.

6. disp_rtf_ch (site number) (rtf id)This command is used to check numbers of time slots are active & call drop.


MMI-RAM 1015 -> disp_rtf_ch 30 0 0Start of report for RTF 0 0 at location 30:Packet Radio Capabilities: 32KRTF Currently capable of supporting EGPRS: NO TIMESLOT GPRS TYPE SUB-CHAN STATE ------------------------------------------------------------------- 0 BCCH N/A BCCH ACTIVE 1 (SDCCH/8) N/A 0 IDLE 1 IDLE 2 IDLE 3 IDLE 4 IDLE 5 IDLE 6 IDLE 7 IDLE 2 (TCH/F) N/A 0 ACTIVE 3 (TCH/F) N/A 0 ACTIVE 4 (TCH/F) N/A 0 ACTIVE 5 (TCH/F) N/A 0 ACTIVE 6 (32K PDTCH) SWITCHABLE 0 IDLE 7 (32K PDTCH) RESERVED 0 IDLE

End of Report.

7. disp_eq (site number) dri (dri id)This command is used to check equipage of the DRI. That give complete details of the

DRI.


MMI-RAM 1015 -> disp_eq 30 dri 2 1

DRI identifier: 2 1 DRI Density[dri_density]: double Transceiver Flag: 0 Cabinet identifier: 2 Type of connection to the BTP: FMUX1 Port to which the TCU is connected[tcu_port]: 4


6 of 20


RTF identifier[pref_rtf_id]: GSM cell ID where the DRI appears: 404 11 109 18523 Antenna select number for this cell[antenna_select]: 3 Tuneable combining used: No The diversity flag for this DRI is[diversity_flag]: 1 The fm cell type is[fm_cell_type]: 4

8. disp_intThis command is used to check current time interval of the site.


MMI-RAM 1015 -> disp_int

Interval Start Time(HH:MM:SS)-------- -------------------- 0 14:00:00 1 14:30:00 2 15:00:00 3 15:30:00 4 16:00:00 5 16:30:00 6 17:00:00 7 17:30:00 8 18:00:00 9 12:30:00 10 13:00:00 11 13:30:00

9. l (site number) dri (dri id)This command is used to lock the particular DRI.


MMI-RAM 1015 -> l 30 dri 2 2

DRI 2 2 Taking this DRI out of service may cause calls to be dropped.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

10. unl (site number) dri (dri id)This command is used to unlock the particular DRI.


MMI-RAM 1015 -> unl 30 dri 2 2

COMMAND ACCEPTED


7 of 20


11. ins (site number) dri (dri id)


MMI-RAM 1015 -> ins 30 dri 0 1DRI 0 1 Taking this DRI out of service may cause calls to be dropped.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

12. disp_stats (time interval) path_balance cell_number (MCC id) (MNC id) (LAC id) (Cell id)

This command is used to check path balance of the sites. This command gives balance value between TX path and RX path. The mean value of path balance should be in the range of 108 to 112 for 900 MHz band. Path balance value 105 can be acceptable if it is 1800 MHz band. Path balance command is separately entered and executed for each sectors.


Command for sector first.

MMI-RAM 1015 -> disp_stats 2 path_balance cell_number 4 0 4 1 1 109 18521

SITE : 30 CELL #: LAC=006Dh CI=4859h RTF ID : 0 0

SITE : 30 CELL #: LAC=006Dh CI=4859h RTF ID : 0 0 MEAS_TYPE : PATH_BALANCE Distribution Mean : 111 Distribution Max. : 135 Distribution Min. : 81 Bin : 0 0 0 2 3137 5957 3 0 0 0



SITE : 30 CELL #: LAC=006Dh CI=4859h


8 of 20


RTF ID : 0 2




Command for second sector.MMI-RAM 1015 -> disp_stats 2 path_balance cell_number 4 0 4 1 1 109 18522

SITE : 30 CELL #: LAC=006Dh CI=485Ah RTF ID : 1 0

SITE : 30 CELL #: LAC=006Dh CI=485Ah RTF ID : 1 0 MEAS_TYPE : PATH_BALANCE Distribution Mean : 111 Distribution Max. : 121 Distribution Min. : 99 Bin : 0 0 0 0 59 110 0 0 0 0




SITE : 30 CELL #: LAC=006Dh CI=485Ah RTF ID : 1 2 MEAS_TYPE : PATH_BALANCE Distribution Mean : 112


9 of 20


Distribution Max. : 125 Distribution Min. : 96 Bin : 0 0 0 0 617 1904 0 0 0 0



Command for third sector.MMI-RAM 1015 -> disp_stats 2 path_balance cell_number 4 0 4 1 1 109 18523

SITE : 30 CELL #: LAC=006Dh CI=485Bh RTF ID : 2 0

SITE : 30 CELL #: LAC=006Dh CI=485Bh RTF ID : 2 0 MEAS_TYPE : PATH_BALANCE Distribution Mean : 113 Distribution Max. : 136 Distribution Min. : 95 Bin : 0 0 0 0 348 1065 4 0 0 0





13. disp_act_a (site number)


10 of 20


This command is used to check current active alarm of the site. It can be either external alarm or internal alarm.


MMI-RAM 1015 -> disp_act_a 30

ACTIVE ALARM INFORMATION FOR LOCATION 30:

Device Alarm Clear (Subtype) Code Type Tag(hex) Date/Time Description-------------------- ---- ---- -------- ---------- --------------------EAS 1 0 0 19 FMIC Untagged 09-08-2004 INTRUDER ALARM (11) 16:32:58IAS 0 0 0 41 FMIC Untagged 09-08-2004 Multicoupler Failure 16:31:12

END OF REPORT

14. alarm_mode (site number) onThis command is used to enabling alarm mode of the site. After enabling alarm mode

each and every alarm raised is appear on the screen. These alarms are either external or internal. After enabling alarm mode, all the external alarm can be check by raising these from krone box.


MMI-RAM 1015 -> alarm_mode 30 on

SITE MODE ---- --------------------------------------- 30 Alarm reporting enabled

When Opto 1 alarm raised from Krone box. A massage is appearing on the screen as shown below.

* Device Alarm -- Untagged** (16) Optocoupler 1* -- Severity: CRITICAL Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:00:04:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: High Room Temp (0)

When Opto 1 alarm clear from Krone box. A massage is appearing on the screen as shown below.

* Device Alarm -- Untagged** (16) Optocoupler 1* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0


11 of 20


* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:00:19:280* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: High Room Temp (0)


* Device Alarm -- Untagged** (17) Optocoupler 2* -- Severity: MAJOR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:00:19:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Site on Battery (1)When Opto 2 alarm clear from Krone box. A massage is appearing on the screen as shown below.

* Device Alarm -- Untagged** (17) Optocoupler 2* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:00:34:440* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Site on Battery (1)


* Device Alarm -- Untagged** (18) Optocoupler 3* -- Severity: MAJOR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:00:34:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: 1 Rect. Fail (2)

When Opto 3 alarm clear from Krone box. A massage is appearing on the screen as shown below.* Device Alarm -- Untagged** (18) Optocoupler 3* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:00:49:600


12 of 20


* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: 1 Rect. Fail (2)


* Device Alarm -- Untagged** (19) Optocoupler 4* -- Severity: CRITICAL Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:01:15:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Fire At Site (3)


* Device Alarm -- Untagged** (19) Optocoupler 4* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:01:30:540* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Fire At Site (3)


* Device Alarm -- Untagged** (20) Optocoupler 5* -- Severity: MAJOR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 20:43:01:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Load on Diesel Gen. (4)


* Device Alarm -- Untagged** (20) Optocoupler 5* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 20:43:16:560* -- Alarm Type: Fault Management Initiated Clear


13 of 20


* -- Additional Info: Load on Diesel Gen. (4)


* Device Alarm -- Untagged** (21) Optocoupler 6* -- Severity: MAJOR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:01:31:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Air Conditioner Failure (5)


* Device Alarm -- Untagged** (21) Optocoupler 6* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:01:46:620* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Air Conditioner Failure (5)


* Device Alarm -- Untagged** (22) Optocoupler 7* -- Severity: CRITICAL Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:01:46:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Low Battery Voltage (8)When Opto 7 alarm clear from Krone box. A massage is appearing on the screen as shown below.

* Device Alarm -- Untagged** (22) Optocoupler 7* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:01:780* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Low Battery Voltage (8)


14 of 20



* Device Alarm -- Untagged** (23) Optocoupler 8* -- Severity: MAJOR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:01:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Low Diesel Level (7)


* Device Alarm -- Untagged** (23) Optocoupler 8* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 0 0 0* -- Site: 30 Cage: 15 Slot: 16* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:16:940* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: Low Diesel Level (7)


* Device Alarm -- Untagged** (16) Optocoupler 1* -- Severity: MAJOR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:17:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: DG on NO LOAD (6)


* Device Alarm -- Untagged** (16) Optocoupler 1* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:33:030* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: DG on NO LOAD (6)



15 of 20


* Device Alarm -- Untagged** (17) Optocoupler 2* -- Severity: MINOR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:33:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: DG FAIL to START (9)


* Device Alarm -- Untagged** (17) Optocoupler 2* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:48:190* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: DG FAIL to START (9)


* Device Alarm -- Untagged** (18) Optocoupler 3* -- Severity: MINOR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:02:48:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: CIRCUIT BREAKER FAILURE (10)


* Device Alarm -- Untagged** (18) Optocoupler 3* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:03:03:350* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: CIRCUIT BREAKER FAILURE (10)



16 of 20


* Device Alarm -- Untagged** (19) Optocoupler 4* -- Severity: MAJOR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 20:37:58:000* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: INTRUDER ALARM (11)


* Device Alarm -- Untagged** (19) Optocoupler 4* -- Severity: CLEAR Category: ENVIRONMENT* -- EAS 1 0 0* -- Site: 30 Cage: 15 Slot: 17* -- Functional Unit: Site 30* -- Time: Wed 8/9/2004 21:03:03:355* -- Alarm Type: Fault Management Initiated Clear* -- Additional Info: INTRUDER ALARM (11)

14. alarm_mode (site number) offThis command is used to disable alarm mode.


MMI-RAM 1015 -> alarm_mode 30 off

SITE MODE ---- --------------------------------------- 30 Alarm reporting disabled

COMMANDS FOR CALIBRATION OF M-CELL CARRIER UNITS

A. Lock all carrier unitsB. Connect serial cable to the carrier unit which is to be calibrateC. Press the reset button on the carrier unit D. Type the following commands;

(i) FOE (ii) .LMN3 (iii) SWAP C 0 (iv) EXEC C 0 (v) .IGUANA (vi) TEST (vii) CSPWR


17 of 20


E. PressUFor Up Calibration offsetDFor Down Calibration offsetUntil the desired power is reached i.e 20W, note down the Calibration offset

F. PressESC For Escape from calibration

G. Type the following commands;(i) SAVE CAL TX

H. Connect the serial cable to the MMI port I. Give the hard reset to the carrier unit J. Check the cal data, when the carrier unit is busyK. The cal data should be same as entered by youL. Repeat the action for all carrier units

COMMANDS FOR CALIBRATION OF HORIZON 2 DOUBLE DENSITY CARRIER UNITS

A. Lock all the carrier unitsB. Unlock the carrier unit which is to be calibrateC. Connect the serial cable to the carrier unitD. Type the following commands;

(i) chg(ii) pizza(iii) cal_test_mode on (iv) fm test_mode on (v) fm_test block none 0xff (vi) cal_config tx_cab_mode double (vii) cal_cabinet tx_cab

E. PressUFor Up Calibration offsetDFor Down Calibration offset


18 of 20


Until the desired power is reached i.e 20W, note down the Calibration offset

F. PressQ For Escape from calibration

G. Type the following commands;(i) cal_store 1 (ii) fm test_mode off (iii) cal_test_mode off

H. Connect the serial cable to the MMI port and lock the carrier unitI. Now gives the hard reset to the carrier unitJ. Lock both the dri in the carrier unit K. Unlock both the dri in the carrier unitL. Check the cal data of the both dri when it is busy M. The cal data must be (12+X), where X = offset given by youN. The cal data shown in hexadecimal valueO. Only one dri is calibrate in one CTU, other dri automatically taken the value

for first dri P. Now repeat the action for the all carrier units

COMMANDS FOR CALIBRATION OF HORIZON 2 SINGLE DENSITY CARRIER UNITS

A. Lock all the carrier unitsB. Unlock the carrier unit that is to be calibrate and wait till it is busy. We have

to calibrate the single density dri without power meter connected i.e dummy calibration.

C. Connect the serial cable to the carrier unitD. Type the following commands;

(i) chg(ii) pizza(iii) cal_test_mode on (iv) fm test_mode on (v) fm_test block none 0xff (vi) cal_config tx_cab_mode single (vii) cal_cabinet tx_cab

E. PressUFor Up Calibration offset


19 of 20


DFor Down Calibration offsetPress the D – key until 16 offset is achieve and then PressQ For Escape from calibration

G. Type the following commands;(i) cal_store 1 (ii) fm test_mode off (iii) cal_test_mode off

H. Connect the serial cable to the MMI port and lock the carrier unitI. Now gives the hard reset to the carrier unitJ. Lock the carrier unit K. Connect the power meter and thenL. Unlock the carrier unit till dri is busy and then gives the BCCH channels to

this dri. L. Check the power on the power meter if it is 20Watt then ok, otherwise

observe either power is less then 20 Watt or more then 20 Watt. If it is less then 20 Watt then again dummy calibrate and set offset below 16 value. If it is more then 20 Watt then again dummy calibrate and set offset beyond 16 value.

M. Check the cal data of the both dri when it is busy M. The cal data must be (12+X), where X = offset given by youNs. The cal data shown in hexadecimal valueO. Only one dri is calibrate in one CTU, other dri automatically taken the value

for first dri P. Now repeat the action for the all carrier units

COMMANDS FOR CALIBRATION OF HORIZON CARRIER UNITS

A. Lock all carrier units B. Connect the serial cable with toggle switch to the carrier unit which is to be

calibrateC. Change the position of the toggle switch D. Type the following commands;

(i) tcu_clock 0 E. Change the position of the toggle switch F. Type the following commands;

(i) .GSMFW


20 of 20


(ii) TEST(iii) ACT C (iv) BBH ALARM OFF (v) CSPWR

G. PressUFor Up Calibration offsetDFor Down Calibration offsetUntil the desired power is reached i.e 20W, note down the Calibration offset

H. PressESC For Escape from calibration

I. Type the following commands;(i) HALT C (ii) WRENB (iii) SAVE CAL TX (iv) WRPTC

J. Connect the serial cable to the MMI portK. Give the hard reset to the carrier unitL. Check the cal data of the carrier when it is busyM. Repeat the action for the all carrier units


Comm Pro

Documents

Transcript of Comm Pro