RBS200 TF Fault Code List

8/3/2019 RBS200 TF Fault Code List

1/36

DESCRIPTION

QPLSAEL QPLSAEL 10/1551HRB 103 02 Uen

ERA/LRF/TC (Hans Lundqvist) 20000911 M

(trs2;t6_43binder)d10_1551.tec;14 d10_1551.tec

L Z F 0 3 2 4 1 / 1 M

R J

Uppgjord (ven faktaansvarig om annan) -

Datum - Rev

Nr -

Dokumentansvarig/Godknd - Kontr - Tillhr/Referens - File/Reference Checked Document responsible/Approved

No.

Date

Prepared (also subject responsible if other)

1(36)

TF FAULT LISTS

Abstract

This document describes disturbances and faultsdetected by the supervision in the managed object TF inthe TRS system.

Application

Interpretation of disturbance and fault identities

Supplementary documents

Revision History

Complete list of revisions presented:

Date Rev Characteristics19911119 A First approved edition19920327 B Adjusted in accordance with

CR 1419920522 C First approved R2 edition.

including CR 5A,7A,8A,91219921209 D Approved by PCBTS19930226 E Approved by PCBTS19930611 F Approved by PCBTS19930924 G CR 17&18 included19960429 H CR 19 included19960627 J CR 20 included19981214 K Approved for TRS R6/TG

Synchronization.19991014 L Approved after KG20000908 M CR 22 included.

Updates


2/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


2

Table of Contents

1 Introduction 4

1.1 Mapping between TRS and Abis format 5

2 Abbreviations 6

3 Terminology 7

4 Brief lists 10

4.1 TF faults, class 1 104.2 TF faults, class 2 114.3 TF faults, external class 1 124.4 TF disturbances 134.5 RUmap 14

5 Visual indication on TU 15

5.1 Red LED 155.2 Green LED 155.3 Yellow LED 15

6 TU fault list 16

6.1 PCMref1 interruption 176.2 PCMref2 interruption 176.3 TU1 interruption 176.4 TU2 interruption 176.5 TU3 interruption 186.6 PCMref1 illegal high relative frequency

deviation 186.7 PCMref2 illegal high relative frequency

deviation 186.8 TU is not in sync with TU1 186.9 TU is not in sync with TU2 196.10 TU is not in sync with TU3 196.11 PCMref1 illegal high wander 196.12 PCMref2 illegal high wander 206.13 TGB distribution fault 206.14 TIB distribution fault 206.15 VCO control value fault 20

7 TF fault lists 22

7.1 TF Class 1 faults 227.1.1 To few usable TU:s 227.1.2 No usable PCMreference 227.1.3 LMT intervention 227.1.4 Synchronization lost, HWerror between TU:s 23

7.1.5 Synchronization lost, timeout between TU:s 237.1.6 Synchronization lost, HWerror, reference 247.1.7 Synchronization lost, timeout, reference 247.1.8 Synchronization lost, other reason 25


3/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


3

7.1.9 Severe fault during reload in ENABLED state 257.1.10 Multiple mismatch due to communication fault. 267.2 TF Class 2 faults 267.2.1 Reset, unspecified 267.2.2 Reset, Power on 267.2.3 Reset, Push button reset 267.2.4 Reset, Watchdog 277.2.5 Reset, CPU exception 277.2.6 Reset, SW fault 277.2.7 Reset, Checksum fault 277.2.8 Communication fault 287.2.9 Failed restart attempt 287.2.10 TGB distribution fault 287.2.11 Illegal software version 297.2.12 OMB fault channel 297.2.13 OMB HSCX fault single channel 297.2.14 TIB distribution fault 307.2.15 VCO control value fault 307.2.16 TU synchronization fault 307.2.17 TUTU fault, connection 317.2.18 TUTU fault, synchronism 317.2.19 Single interruption PCM ref 327.2.20 Single frequency fault PCM ref 327.2.21 Single wander problem PCM ref 337.2.22 PCMref interruption 337.2.23 PCMref frequency fault 33

7.2.24 PCMref illegal high wander 347.2.25 Checksum fault boot PROM 347.2.26 Checksum fault HW revision info 347.3 TF External Class 1 faults 357.3.1 LMT, Local Operator Intervention 35

8 References 36


4/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


4

1 INTRODUCTION

This document is only applicable for MO TF. All faultsand disturbances detected and reported is described inthis document.

TF differs from the other LUs in TRS. There is noonetoone relations between LU and subprocessor as itis for the other LUs. TF is a hardware redundantsystem with three timing units, TU. The three TU:s arenot always reporting fully consistent faults. A faultdetected by a single TU has to be further analysed byTMH which has an overview of the fault status of theentire TM. The faults detected in a TU are named TUfaults. The function block TMH, in TCS, analyses TUfaults and report TF faults.

TMG TUfaults TRXC TU1

TFfaults

TU2

TMH

TU3

Fault detection Fault analyses

Note TU1TU3 and TRXC are hardware units.TMG and TMH are functional blocks.

Figure 1, Fault reporting in TF


5/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


5

1.1 MAPPING BETWEEN TRS AND ABIS FORMAT

The Fault Maps and RU Maps in TRS are mapped on the Abismap elements according to the tables below:

TRS Maps (32 bits) Abis Maps (48 bits)

Fault Map, Class 1 Internal Fault Map Class 1A,bit 0..31

(not used by TRS) Internal Fault Map Class 1BFault Map, Class 2 Internal Fault Map Class 2A,

bit 0..31Replacement Unit Map Replacement Unit Map Bis, bit 0..31

TRS Maps (16 bits) Abis Maps (16 bits)

External Fault Map, Class 1 External Fault Map, Class 1B (not used by TRS) External Fault Map, Class 2B

The Abis maps, Internal 1B & External 2B, and theadditional bits (3247) in the larger Abis maps arealways set to zeroes.


6/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


6

2 ABBREVIATIONS

A" Abis BTS PLMN connectionBSC Base Station ControllerBTS Base Transceiver StationEXT RU indicating that the fault originates outside

managed object TF or the TRS.FN TDMA frame numberFN offset TDMA frame number offset. Added to site FN

for each TG.LA Logical AddressLIF Line InterfaceLU Logical UnitLUH Logical Unit HandlerMO Managed ObjectMOI Managed Object Identity/InstanceO&M Operation and MaintenanceOMB Operations and Maintenance BusOMBA Operations and Maintenance Bus Channel AOMBB Operations and Maintenance Bus Channel BOMH Operations and Maintenance Bus HandlerOML Operation and Maintenance LinkPSC Processor System ControllerPU Physical UnitPUI Physical Unit IdentityRU Replaceable Unit

RUM Replacement Unit MapSite FN TDMA frame number common for a TRS.SLH Software Load HandlerTC Transceiver ControlTCS Transceiver Control SystemTEI Terminal Endpoint IdentifierTF Timing Function (LU)TG Transceiver GroupTGB TG Synchronization BusTGC Transceiver Group ControlTIB Timing BusTM Timing ModuleTMBP Timing Module Back PlaneTMCB Timing Module Connection boardTMG Timing GenerationTMH Timing HandlerTRI Transmission Radio InterfaceTRS Transceiver SystemTRX TransceiverTRXC Transceiver ControllerTU Timing UnitVCO Voltage controlled oscillator. Vital part

of TU hardware.& Logical and of two or more events or

properties


7/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


7

3 TERMINOLOGY

Master/slave TU: Master TU synchronizes towards theexecutive reference. Slave TU synchronizestowards master TU. For further informationsee reference #1.

Synchronization source: Input to the synchronizationalgorithm in a TU. Can be a reference oran other TU.

Reference: Synchronization source used to synchronizea TU to the PCM network. Used referencesare PCMreference 1 and 2.

PCMreference: Reference extracted from TRI/PCMnetwork.

Executive Reference chosen to synchronize towards.reference:

Default A reference which a TU shall synchronizereference: towards when there are no ordered

synchronization source.

Unexpected PCMreference: A reference is unexpected

when TMH do not have contact with the TRXCthat sends the reference to the TU:s.TRXC1 sends PCMreference 1 and TRXC2sends PCMreference 2.

Expected PCMreference:The opposite to unexpected PCMreference.

Synchronizing: The synchronization has been started butsynchronism has not been reached.

Timing: With timing is basically meant thefollowing three pieces of timinginformation:o TDMA frame number.o TDMA frame sync.o TIB_CLK, a 65 kHz frequency.

Blocking: Blocking is a mean for fault isolation. Ablocked TU is not to distribute timing onTIB and is not allowed to be master TU. Ablocked reference is forbidden to synchronize towards. Blocked units shall still besupervised.

Deblocking: The opposite of Blocking


8/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


8

Hold over: If TF is synchronized towards thePCMnetwork and detects faults on bothPCMreferences then TF will start the holdover operation. At start of the hold overoperation the master TU will freeze theVCO control value and start a one hourtimer. If the fault situation disappearsthen the hold over operation will bestopped. If the timer above expires beforethe fault situation disappears then thesynchronization is considered as lost, seechapter 7.1.2.

When the executive reference becomesblocked then TF will run the hold overoperation before changing executivereference.

Fault number: The parameter "fault number" is accordingto the ABIS O&M IWD, and indicates thebit position in the bit maps of Class 1 andClass 2.

Local mode: If the TU has lost contact with TMH thenthe TU will enter "local mode".

Normal mode: A TU with contact with TMH.Supervised object property:

The TU:s supervises a number of objects(e.g PCMref, TU:s). A number ofproperties can be supervised for eachobject (e.g. interruption, high wander).

Local action: A fault isolation action that isperformed based on local decisions. Atypical local action is to block a TUwhich is faulty. Both TMH and TU can do alocal action.

Restart: At some fault situations a TU can be automatically restarted. The restart alwaysincludes reset and start of the TU. If theTU has no, wrong or corrupt software thenthe TU will also be reloaded. Note that TFis not allowed to perform such an automatic reload more than one time every 10minutes. That 10 minute restriction isoverruled by a push button reset.

Fault cause: A description of the criteria(s) that mustbe fulfilled when a fault becomes active.


9/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


9

Fault cease: A description of the criteria(s) that mustbe fulfilled when a fault is no longeractive.

Not critical A TU fault that not affect the timingTU fault: distribution withing the TG.


10/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


10

4 BRIEF LISTS

4.1 TF FAULTS, CLASS 1

Fault Fault typeno

0 To few usable TU:s1 No usable PCMreference9 LMT intervention

10 Synchronization lost, HWerror between TU:s11 Synchronization lost, timeout between TU:s12 Synchronization lost, HWerror, reference13 Synchronization lost, timeout, reference14 Synchronization lost, other reason19 Severe fault during reload in ENABLED state.20 Multiple mismatch due to communication fault.

Note: The faults are further described in chapter 7.1.

Figure 2, TF fault, class 1


11/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


11

4.2 TF FAULTS, CLASS 2

Fault TU Ref Fault typeno *) *)

0 Y Reset, unspecified1 Y Reset, Power on2 Y Reset, Push button reset3 Y Reset, Watchdog4 Y Reset, CPU exception5 Y Reset, SW fault6 Y Reset, Checksum fault7 Y Communication fault8 Y Failed restart attempt9 TGB distribution fault

10 Y Illegal software version11 OMB fault channel12 OMB HSCX fault single channel13 Y TIB distribution fault14 Y VCO control value fault15 Y TU synchronization fault16 Y TUTU fault, connection17 Y TUTU fault, synchronism18 Y Single interruption PCM ref19 Y Single frequency fault PCM ref20 Y Single wander problem PCM ref

22 Y PCMref interruption23 Y PCMref frequency fault24 Y PCMref illegal high wander30 Checksum fault boot PROM31 Checksum fault HW revision info

*) The column "TU" shows blocking status of a TU withthat kind of fault. The letter Y means that a TUwith that fault is BLOCKED. The column "Ref" givesthe same information about references.

Note: The faults are further described in chapter 7.2.

Note: PCMref1 is expected to be present when TRXC1 ispresent in the system. PCMref2 when TRXC2 ispresent.

Figure 3, TF fault, class 2


12/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


12

4.3 TF FAULTS, EXTERNAL CLASS 1

Fault Fault typeno

2 LMT, Local Operator Intervention

Note: The fault(s) are further described in chapter 7.3.

Figure 4, TF fault, external class 1


13/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


13

4.4 TF DISTURBANCES

Disturbance Disturbance Described number in chapter TU1 TU2 TU3 *) *) *)

1 41 81 PCMref1 interruption 6.1 2 42 82 PCMref2 interruption 6.2 6 46 86 TU1 interruption 6.3 7 47 87 TU2 interruption 6.4 8 48 88 TU3 interruption 6.5 11 51 91 PCMref1 illegal high relative 6.6 frequency deviation 12 52 92 PCMref2 illegal high relative 6.7 frequency deviation 15 55 95 TU is not in sync with TU1 6.8 16 56 96 TU is not in sync with TU2 6.9 17 57 97 TU is not in sync with TU3 6.10 18 58 98 PCMref1 illegal high wander 6.11 19 59 99 PCMref2 illegal high wander 6.12 20 60 100 TGB distribution fault 6.13 22 62 102 TIB distribution fault 6.14 23 63 103 VCO control value fault 6.15

24

64

104

OMB fault channel A

7.2.12

25 65 105 OMB HSCX fault channel A 7.2.13 26 66 106 OMB fault channel B 7.2.12 27 67 107 OMB HSCX fault channel B 7.2.13 32 72 112 Communication disturbance 7.2.8 33 73 113 Failed restart attempt 7.2.9 34 74 114 Illegal software version 7.2.11 Failed synchronization... 36 76 116 ...due to HWerror TU 7.1.4 7.2.16 37 77 117 ...due to timeout TU 7.1.5 7.2.16 38 78 118 ...due to HWerror Ref 7.1.6 39 79 119 ...due to timeout Ref 7.1.7

*) The three TUs has up to 40 individual disturbancenumbers each. Disturbance 023, 4063 and 80103are detected by the function block TMG. They corresponds to the TU faults in accordance with figure7. The rest of the disturbances are detected bythe function block TMH. They are in some casesbased on information from the TMG.

Figure 5, Disturbances


14/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


14

4.5 RUMAP

No: 0 1 2 3 4 5 6 7RU: TRXC TU_1 TU_2 TU_3

No: 8 9 10 11 12 13 14 15RU: PCM PCM

ref1 ref2

No: 16 17 18 19 20 21 22 23RU: OMBA OMBB TIB TMCB EXT

No: 24 25 26 27 28 29 30 31RU:

Note : The indication of RU#14, 15, 16, 17 or 18 canindicate a fault in TMBP or TMCB.

Figure 6, Replacement unit map


15/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


15

5 VISUAL INDICATION ON TU

5.1 RED LED

Red LED at HW reset of TUThe red LED is turned on at poweron reset, Manualreset or Write protect reset. It remains on until theboot tests has successfully terminated. The LED isturned off if no fault has been found during the boottest. If any fault is found, the LED remains on.

The boot tests consists of a checksum test of the bootprogram area (EEPROM) and, at Poweron reset, a RAM(read/write) test.

Red LED at blocking of faulty TUTMH turns the red LED on when the TU is BLOCKED dueto that one or several class 2 faults are active. Seechapter 7.2

Red LED at faulty TU, no blockingTMH detects a TU with one or more not critical faults,i.e faults not affecting the timing distribution withinthe TG, active. The red LED is turned on, but the TUis not BLOCKED.

The LED is turned off when the TU is DEBLOCKED and nonot critical faults remain.

5.2 GREEN LED

Indicates presence of +5v.

5.3 YELLOW LED

The LED is turned on at poweron reset, Manualreset or Write protect reset.It remains on until the boot tests has terminated.

The LED is off when the TU is in reset state.

The LED is flashing when the TU executes applicationsoftware, but is not distributing timing on TIB.

The LED is on under normal (TU is distributing timingon TIB) operating conditions.


16/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


16

6 TU FAULT LIST

The supervision in a TU is based on a number of objectsto supervise. A number of properties can be supervisedon each object. An overview of the supervised objectproperties is given in figure 7. More detailed information is given in chapters below. TMH orders the TU tostart supervise the individual object propertiespossible to supervise. The TU will serve TMH withinformation about which supervised object propertiesthat has a valid result.

No Supervised object property

1 PCMref1 interruption 2 PCMref2 interruption 6 TU1 interruption 7 TU2 interruption 8 TU3 interruption 11 PCMref1 illegal high relative frequency deviation 12 PCMref2 illegal high relative frequency deviation 15 TU is not in sync with TU1

16

TU is not in sync with TU2

17 TU is not in sync with TU3 18 PCMref1 illegal high wander 19 PCMref2 illegal high wander 20 TGB distribution fault 22 TIB distribution fault 23 VCO control value fault

Figure 7, Summary of the supervised object properties

Each object property with started supervision ischecked regularly. The result of the check can beeither ok or not ok. If the check result is not ok, thecorresponding bit in the disturbance map is set. Theresult of the check is passed to a filtering function.The filtering function is different for each supervisedobject property. The main principle is to filter outtemporarily disturbances which do not affect the synchronization function. The result after the filteringis the fault status of the supervised object property.It is either fault or no fault. The corresponding bitin a TU fault map is set or reset depending on theactual fault status. The filtering function is resetwhen supervision is started or stopped.

Both the disturbance and the TU fault map is read byTMH each second.


17/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


17

6.1 PCMREF1 INTERRUPTION

TU fault number: 1TF Disturbance numbers: 1,41,81Fault cause : No sync from PCMref1 during 1 second.Fault cease cause : Sync from PCMref1 has been presentfor 10 second.Disturbance criteria : A single measurement of thepresense of PCMref1 has failed.TU actions upon disturbance : The control value to theVCO is held constant if the TU is ordered tosynchronize to PCMref1. (Hold over operation.)TU actions upon fault : This fault can cause TF tostart the hold over operation. If a TU in local modehas run the hold over operation during one hour thenthe TU will enter RESET state. Validity condition: Supervision has been active for thelast 10 second.

6.2 PCMREF2 INTERRUPTION

TU fault number: 2TF Disturbance numbers: 2,42,82

In analogy with chapter 6.1.

6.3 TU1 INTERRUPTION

TU fault number: 6TF Disturbance numbers: 6,46,86Fault cause : No TIB_CLK, TIB_FS or TIB_FN from TU1during 1 second.Fault cease cause : TIB_CLK, TIB_FS and TIB_FN from TU1has been present for 1 second.Disturbance criteria : A short interrupt on TU1.TU actions upon disturbance : The control value to theVCO is held constant if the TU is ordered to synchronize to TU1.TU actions (TU in local mode) upon fault : The TU willenter RESET state if the TU is ordered to synchronizeto TU1. Validity condition: Supervision has been active for thelast 1 second.





18/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


18




6.6 PCMREF1 ILLEGAL HIGH RELATIVE FREQUENCY DEVIATION

Fault number : 11TF Disturbance numbers: 11,51,91Fault cause : The relative frequency deviation (FDEV)to PCMref1 has been either > +0.1 ppm during twoconsecutive measurement intervals or < 0.1 ppm duringtwo consecutive measurement intervals. The relativefrequency deviation is measured as the change of phaseduring 10 seconds (a measurement interval).Fault cease cause : The value of the relative frequencydeviation (FDEV) to PCMref1 has been less than |0.1|ppm during two consecutive measurement intervals.Disturbance criteria : The measurement described abovehas a value exceeding |0.1| ppm.TU actions upon disturbance : The control value to theVCO is held constant if the TU is ordered to synchronize to PCMref1. (Hold over operation.)

TU actions upon fault : This fault can cause TF tostart the hold over operation. If a TU in local modehas run the hold over operation during one hour thenthe TU will enter RESET state. Validity condition : Supervision has been active forthe last 20 seconds and the TUfault no 1 has beencleared during this time.

6.7 PCMREF2 ILLEGAL HIGH RELATIVE FREQUENCY DEVIATION



6.8 TU IS NOT IN SYNC WITH TU1

TU fault number: 15TF Disturbance numbers: 15,55,95Fault cause : Comparisons of TIB_FS, TIB_FN, TIB_CLKfrom the reporting TU and TIB_FS1, TIB_FN1, TIB_CLK1from TU1 indicates that the TU:s are not deliveringidentical signals. The TU:s are not in synchronism with

each others. The mismatch has been present for morethan 500 ms.Fault cease cause : The TU has delivered identicalsignals for 1 second. See note


19/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


19

Disturbance criteria : A single comparison has failed.TU actions (TU in normal mode) upon fault : None.TU actions (TU in local mode) upon fault : The TU willenter RESET state if the TU is ordered to synchronizeto TU1. Validity condition: Supervision has been active for thelast 1 second.

Note that this supervision is stopped if fault bits no.6 (TU1 interruption) is set. It is restarted when thefault bit is cleared.







6.11 PCMREF1 ILLEGAL HIGH WANDER

TU fault number: 18TF Disturbance numbers: 18,58,98Fault cause : The phase difference between the TU andPCMref1 is sampled at 250 ms intervals. If the phasedifference between two consecutive samples has changedmore than 1.25 us twice during the last 10 samples,this fault is set.Fault cease cause : The phase difference between twoconsecutive samples has not changed more than 1.25 usduring 10 seconds. See note.Disturbance criteria : Same as fault cause.TU actions upon disturbance/fault : The control valueto the VCO is held constant if the TU is ordered tosynchronize to PCMref1. (Hold over operation.)TU actions upon fault : This fault can cause TF tostart the hold over operation. If a TU in local modehas run the hold over operation during one hour thenthe TU will enter RESET state. Validity condition: Supervision has been active for thelast 10 seconds.

Note : This supervision is stopped if the fault bitnumber 1 is set. It is restarted when the fault bit iscleared.


20/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


20

6.12 PCMREF2 ILLEGAL HIGH WANDER



6.13 TGB DISTRIBUTION FAULT

TU fault number: 20TF Disturbance numbers: 20,60,100Fault cause : The driver circuits for TGB has failed(loop test).Fault cease cause : Loop test has succeeded for 2 seconds.Disturbance criteria : Same as fault criteria.TU actions (TU in normal mode) upon disturbance/fault :None.TU actions (TU in local mode) upon disturbance/fault :None.Validity condition: Distribution of timing on TGB hasbeen active for 1 second.

Note: The supervision is always started after an orderto start TGB distribution. It is stopped when theTGB distribution is stopped.

6.14 TIB DISTRIBUTION FAULT

TU fault number: 22TF Disturbance numbers: 22,62,102Fault cause : The driver circuits for TIB has failed(loop test)Fault cease cause : NoneDisturbance criteria : Same as fault criteria.TU actions (TU in normal mode) upon disturbance/fault :None.TU actions (TU in local mode) upon disturbance/fault :The TU will enter RESET state. Validity condition: Distribution of timing on TIB hasbeen active for 1 second.

Note : The supervision is always started after an orderto start TIB distribution. It is stopped when theTIB distribution is stopped.

6.15 VCO CONTROL VALUE FAULT

TU fault number: 23TF Disturbance numbers : 23,63,103Fault cause : The control value to the VCO is outsidethe range 104085.Fault cease cause : The control value is inside the


21/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


21

range 504045.Disturbance criteria : Same as fault cause duringnormal operation.TU actions (TU in normal mode) upon disturbance/fault :None.TU actions (TU in local mode) upon disturbance/fault :The TU will enter RESET state. Validity condition: Supervision has been active for thelast 1 second.


22/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


22

7 TF FAULT LISTS

7.1 TF CLASS 1 FAULTS

7.1.1 To few usable TU:s

Fault no: 0Fault cause: More than one TUs have been BLOCKED. Forinformation about faults causing a TU to become BLOCKEDsee figure 3.Fault cease: Not ceased.Disturbances: See class 2 fault causing the blocking.Possible RU: See class 2 fault causing the blocking.Local action: TF is auto reset. Distribution of timingis stopped.

7.1.2 No usable PCMreference

Fault no: 1Fault cause: There is no DEBLOCKED PCMreference. Forinformation about faults causing a PCMreference tobecome BLOCKED see figure 3. The fault can be set forboth TF mode standalone and TF mode master.

If TF is synchronized then TF will have to run holdover operation for one hour before setting this fault.But if master TU becomes blocked then the setting ofthe fault is made immedite.

Fault cease: A PCMreference is deblocked.Disturbances: See class 2 fault causing the blocking.Possible RU: See class 2 fault causing the blocking.Local action: If this fault become set then the synchronization of TF will be stopped. Automatic synchronization tests will be initiated when there is at leastone PCMreference which is neither interrupted norunexpected. The auto test of TF will also be postponedwhile there are less than two responding TU:s.

7.1.3 LMT intervention

Fault no: 9Fault cause: Abis OML simulation towards MO TF isstarted on LMT. Note that this fault is not ceased byfault localization test started by TEST COMMAND. Nor isthis fault ceased when entering state RESET.Fault cease: Abis OML simulation towards MO TF isstopped.Disturbances: None.Possible RU: Local action:


23/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


23

7.1.4 Synchronization lost, HWerror between TU:s

Fault no: 10Fault cause: Both slave TU:s in a synchronized TF haslost the synchronism. At least one of them has lost itbecause of a failed resynchronization. All slave TU:sreporting failed synchronization has failed to reachsynchronism because of the connection with the synchronization source was interrupted. Another reason for"HWerror" is if the TU has got a VCO control valuefault, see chapter 6.15.Fault cease: When at least two TU:s are found to becapable to get in synchronism with each other and theexecutive reference then the fault is reset, see note.Disturbances: A disturbance is sent when a slave TUreports the synchronization fault. Disturbance 36 issent when TU1, 76 when TU2 and 116 when TU3 reports thesynchronization faultPossible RU: Master TU. This fault situation can becaused by a fault situation also generating a class 2fault. For further information about RU see existingclass 2 faults.Local action: If this fault become set then the synchronization of TF will be stopped. Automatic synchronization tests will be initiated when there is at leastone PCMreference which is neither interrupted nor

unexpected. The auto test of TF will also be postponedwhile there are less than two responding TU:s.

7.1.5 Synchronization lost, timeout between TU:s

Fault no: 11Fault cause: Both slave TU:s in a synchronized TF haslost the synchronism. At least one of them has lost itbecause of a failed resynchronization. At least one ofthe slave TU:s has failed to reach synchronism before 1minute has gone after the synchronization was ordered.Fault cease: When at least two TU:s are found to becapable to get in synchronism with each other and theexecutive reference then the fault is reset, see note.Disturbances: A disturbance is sent when a slave TUreports the synchronization fault, due to timeout.Disturbance 37 is sent when TU1, 77 when TU2 and 117when TU3 reports the synchronization faultPossible RU: Master TU. This fault situation can becaused by a fault situation also generating a class 2fault. For further information about RU see existingclass 2 faults.Local action: If this fault become set then the synchronization of TF will be stopped. Automatic synchro

nization tests will be initiated when there is at leastone PCMreference which is neither interrupted norunexpected. The auto test of TF will also be postponedwhile there are less than two responding TU:s.


24/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


24

7.1.6 Synchronization lost, HWerror, reference

Fault no: 12Fault cause: Master TU in a synchronized TF has failedto resynchronize. The resynchronization is initiated bya blocking of the previous master TU. It can also beinitiated by a blocking or deblocking of a reference.The master TU has failed to reach synchronism becauseof a interruption in the connection with the executivePCMreference. Another reason for "HWerror" is if theTU has got a VCO control value fault, see chapter 6.15.Fault cease: When at least two TU:s are found to becapable to get in synchronism with each other and theexecutive reference then the fault is reset, see note.Disturbances: A disturbance is sent when the master TUreports the synchronization fault. Disturbance 38 issent when TU1, 78 when TU2 and 118 when TU3 reports thesynchronization faultPossible RU: Executive PCMref. This fault situationcan be caused by a fault situation also generating aclass 2 fault. For further information about RU seeexisting class 2 faults.Local action: If this fault become set then the synchronization of TF will be stopped. Automatic synchronization tests will be initiated when there is at leastone PCMreference which is neither interrupted nor

unexpected. The auto test of TF will also be postponedwhile there are less than two responding TU:s.

7.1.7 Synchronization lost, timeout, reference

Fault no: 13Fault cause: Master TU in a synchronized TF has failedto resynchronize. The resynchronization is initiated bya blocking of the previous master TU. It can also beinitiated by a blocking or deblocking of a reference.The master TU failed to reach synchronism before 10minutes has gone after the new synchronization wasordered.Fault cease: When at least two TU:s are found to becapable to get in synchronism with each other and theexecutive reference then the fault is reset, see note.Disturbances: A disturbance is sent when the master TUreports the synchronization fault. Disturbance 39 issent when TU1, 79 when TU2 and 119 when TU3 reports thesynchronization faultPossible RU: Executive PCMref. This fault situationcan be caused by a fault situation also generating aclass 2 fault. For further information about RU seeexisting class 2 faults.

Local action: If this fault become set then the synchronization of TF will be stopped. Automatic synchronization tests will be initiated when there is at least


25/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


25

one PCMreference which is neither interrupted norunexpected. The auto test of TF will also be postponedwhile there are less than two responding TU:s.

7.1.8 Synchronization lost, other reason

Fault no: 14Fault cause: Less than two TU:s in a previous synchronized TF is synchronized and DEBLOCKED. Non of theTU:s has reported synchronization failed. A TU can beunsynchronized because of a blocking fault, such asreset.Fault cease: When at least two TU:s are found to becapable to get in synchronism with each other and theexecutive reference then the fault is reset, see note.Disturbances: No disturbance initiated.Possible RU: This fault situation can be caused by afault situation also generating a class 2 fault. Forfurther information about RU see existing class 2faults.Local action: If this fault become set then the synchronization of TF will be stopped. Automatic synchronization tests will be initiated when there is at leastone PCMreference which is neither interrupted norunexpected. The auto test of TF will also be postponed

while there are less than two responding TU:s.

7.1.9 Severe fault during reload in ENABLED state

Fault no: 19Fault cause: A severe fault has been detected or sometype of failure has happened during reload of TF software. The following events are identified:

a The communication with a single TU fails, disturbedcommunication.

b The fault analysis in TMH gives a blocking of a TUor a reference as result.

c A class 1 fault is detected.d One of the TU:s fails to synchronize after software

loading.

Fault cease: None.Disturbances: None.Possible RU: None.Local action: TF is auto reset. Distribution of timingis stopped.


26/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


26

7.1.10 Multiple mismatch due to communication fault.

Fault no: 20Fault cause: There has been a short interruption in thecommunication with at least two TU:s. When the communication has been regained an analysis of the TU:scurrent status shows that at least two TU:s has another configuration then the requested.Fault cease: Not ceased.Disturbances: None.Possible RU: None.Local action: TF is auto reset. Distribution of timingis stopped.

7.2 TF CLASS 2 FAULTS

7.2.1 Reset, unspecified

Fault no: 0Fault cause: A TU has been reset by a not separatelydefined reset cause. The reset is NOT caused by a RESETCOMMAND from BSC.Fault cease: After a successful restart.Disturbances: None.

Possible RU: EXT, TU_13Local action: A TU with this fault is BLOCKED andrestarted automatically.

7.2.2 Reset, Power on

Fault no: 1Fault cause: The TU has been reset due to a power on.Fault cease: After a successful restart.Disturbances: None.Possible RU: EXT, TU_13Local action: A TU with this fault is BLOCKED andrestarted automatically.

7.2.3 Reset, Push button reset

Fault no: 2Fault cause: Manual reset of the CPU by the resetbutton upon a TU.Fault cease: After a successful restart.Disturbances: None.Possible RU: EXT, TU_13Local action: TU is BLOCKED and restartedautomatically.


27/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


27

7.2.4 Reset, Watchdog

Fault no: 3Fault cause: The CPU has been reset by the watchdog,caused by a software error or that the softwarehas detected a serious fault and waited in an endlessloop for the watchdog reset to be activated.Fault cease: After a successful restart.Disturbances: None.Possible RU: TU_13Local action: A TU with this fault is BLOCKED andrestarted automatically.

7.2.5 Reset, CPU exception

Fault no: 4Fault cause: The CPU has activated an interrupt upon anexception. The exceptions detected are illegal opcodeor clock fault.Fault cease: After a successful restart.Disturbances: None.Possible RU: TU_13Local action: A TU with this fault is BLOCKED andrestarted automatically.

7.2.6 Reset, SW fault

Fault no: 5Fault cause: Memory protection violation at executionof application software.Fault cease: After a successful restart.Disturbances: None.Possible RU: TU_13Local action: A TU with this fault is BLOCKED andrestarted automatically.

7.2.7 Reset, Checksum fault

Fault no: 6Fault cause: A checksum or a parity fault in TU programmemory has been detected.Fault cease: After a successful restart.Disturbances: None.Possible RU: TU_13Local action: A TU with this fault is BLOCKED andrestarted automatically.


28/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


28

7.2.8 Communication fault

Fault no: 7Fault cause: If the TU does not answer the TU_POLL_CMD(after three consecutive attempts, poll cycle = 1 sec),the TMH tries to find out the reason by issuing aSTATUS_CMD. If TU replies then either one of the Resetfault types becomes active, or the CPU is started andno fault is active. Otherwise TMH continues issuingSTATUS_CMDs every second. The TU communication faultoccurs when the total abortion time equals 85 seconds.Fault cease: After a successful restart.Disturbances: Sent each time there is no answer on theTU_POLL_CMD or the SU_STATUS_CMD. Disturbance sent isnumber 32, 72 or 112 dependent of what TU that has thecommunication fault.Possible RU: TRXC, TU_13, OMBA, OMBBLocal action: A TU with this fault is BLOCKED andrestarted automatically.

7.2.9 Failed restart attempt

Fault no: 8Fault cause: TMH has failed to restart a TU.Fault cease: After a successful restart.

Disturbances: When a restart fails disturbance number33, 73 or 113 is sent dependent of which TU thatfailed.Possible RU: TU_13Local action: A TU with this fault is BLOCKED. The TUis restarted after a manual push button reset.

7.2.10 TGB distribution fault

Fault no: 9Fault cause: The TU has reported TGB distributionfault, see chapter 6.13.Fault cease: Ceased when the TU_POLL_RLY stopsreporting the fault.Disturbances: None detected in TMH. For disturbancescorresponding to the TU fault see figure 5.Possible RU: TU_13, TGB, TMCBLocal action: Red LED is turned on.Note: The supervision is always started after an orderto start TGB distribution. It is stopped when theTGB distribution is stopped.


29/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


29

7.2.11 Illegal software version

Fault no: 10Fault cause: A TU has a program version not matchingthe program version of the other two. This fault can becaused by a restart/reload of the TU.Fault cease: Not ceased.Disturbances: When a mismatching software version isdetected disturbance number 34, 74 or 114 is sentdependent of which TU that has the mismatching softwareversion.Possible RU: TU_13Local action: A TU with this fault is BLOCKED.

7.2.12 OMB fault channel

Fault no: 11Fault cause: OMH indicates channel fault on one or bothOMB channels towards a TU.Fault cease: OMH indicates that the channel fault hasbeen removed.Disturbances: When OMH indicates OMB channel A asfaulty then TMH will send disturbance number 24, 64 or104 is sent dependent of which TU that has the OMBchannel A fault. When OMH indicates OMB channel B as

faulty then TMH will send disturbance number 26, 66 or106 is sent dependent of which TU that has the OMBchannel B fault.Possible RU: TU_13, OMBA, OMBBLocal action: None.

7.2.13 OMB HSCX fault single channel

Fault no: 12Fault cause: OMH indicates channel fault on one of theOMB channels towards a TU. The HSCX loop test in TU hasalso indicated fault.Fault cease: OMH indicates that the HSCX channel faulthas been removed.Disturbances: When OMH indicates OMB channel A ashaving a HSCX fault then TMH will send disturbancenumber 25, 65 or 105 is sent dependent of which TU thathas the OMB channel A fault. When OMH indicates OMBchannel B as having a HSCX fault then TMH will senddisturbance number 27, 67 or 107 is sent dependent ofwhich TU that has the OMB channel B fault.Possible RU: TU_13, OMBA, OMBBLocal action: None.


30/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


30

7.2.14 TIB distribution fault

Fault no: 13Fault cause: The TU has reported TIB distributionfault, see chapter 6.14.Fault cease: The TU is successfully restarted.Disturbances: None detected in TMH. For disturbancescorresponding to the TU fault see figure 5.Possible RU: TU_13, TIBLocal action: A TU with this fault is BLOCKED. Red LEDis turned on. Note: The supervision is always started after an orderto start TIB distribution. It is stopped when theTIB distribution is stopped.

7.2.15 VCO control value fault

Fault no: 14Fault cause: The TU has reported VCO control valuefault, see chapter 6.15.Fault cease: The TU stops reporting the fault as above.The TU is successfully restarted.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.Possible RU: TU_13

Local action: A TU with this fault is BLOCKED. Red LEDis turned on.

7.2.16 TU synchronization fault

Fault no: 15Fault cause: A TU in a synchronized TF has been reporting synchronization failed for more than 10 seconds.Synchronization failed is reported as a parameterSynchronization status contained in the TU_POLL_RLYmessage.

The fault can also be set when TF is trying to synchronize as a consequence of a class 1 fault. The fault isset for a failing TU if the other TU:s are capable ofgetting in synchronism with each other and the executive reference.Fault cease: Synchronism of the TU regained or synchronism of TF lost. The TU is successfully restarted.Disturbances: Disturbance is sent when a slave TUreports synchronization fault, due to connection fault.Disturbance 36 is sent when TU1, 76 when TU2 and 116when TU3 fails.

Disturbance is sent when a slave TU reports synchronization fault, due to timeout. Disturbance 37 is sentwhen TU1, 77 when TU2 and 117 when TU3 fails.


31/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


31

Possible RU: TU_13, EXTLocal action: A TU with this fault is BLOCKED. Red LEDis turned on.

7.2.17 TUTU fault, connection

Fault no: 16Fault cause: There are three different ways that thisfault can be set. This TF fault is based on the reporting of the TU fault TU x interruption.

TU indicating it self as faulty: TUx indicates aconnection problem with TU x.

A single TU having connection problem with theother two: Two TU:s are reporting connectionproblem with the third TU and/or that third TUreports the same about the other two.

Other combinations of reports: This analysis ismade after a coordination time of 15 seconds duringwhich no change in TUTU interruption status maybe received. If the reports dont fit into any ofthe patterns described above, all TU:s reported asfailing to distribute timing to any other TU willhave this fault set.

Fault cease: Indications above is stopped. The TU issuccessfully restarted.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.Possible RU: TU_13Local action: A TU with this fault is BLOCKED. Red LEDis turned on.

7.2.18 TUTU fault, synchronism

Fault no: 17Fault cause: There are four different ways that thisfault can be set. This TF fault is based on the reporting of the TU fault TU is not in sync with TU x.

TU indicating it self as faulty: TUx indicates asynchronization problem with TU x.

A single TU having synchronization problem with theother two: Two TU:s are reporting not in synchronism with the third TU and/or that third TUreports the same about the other two.

Two TU:s having synchronization problem with eachother: Two of the TU:s reports synchronizationproblem with each other, but not with the third,


32/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


32

during a time of 2 minutes. This fault is also setif only one TU reports TU is not in sync withTUx. Both TUs will have this class 2 fault set.

Other combinations of reports: This analysis ismade after a coordination time of 2 minutes duringwhich no change in TUTU synchronization statusmay be received. If the reports dont fit into anyof the patterns described above then all TU:s willhave this class 2 fault set.

Fault cease: The fault is reset if the reporting situation as above no longer is true. The fault is alsoreset if after a successful restart.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.Possible RU: TU_13Local action: A TU with this fault is BLOCKED. Red LEDis turned on.

7.2.19 Single interruption PCM ref

Fault no: 18Fault cause: A TU has been alone in reporting one orboth of the TU faults PCMref1, interruption and

PCMref2 interruption during a coordination time of15 seconds.Fault cease: The TU stops reporting the fault above orclass 2 fault #22 is set. The fault is also reset aftera successful restart.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.Possible RU: TU_13, PCMref_1, PCMref_2Local action: None.

7.2.20 Single frequency fault PCM ref

Fault no: 19Fault cause: A TU has been alone in reporting one orboth of PCMref1 illegal high relative frequencydeviation and PCMref2 illegal high relativefrequency deviation during a coordination time of 25secondsFault cease: The TU stops reporting the fault above orclass 2 fault #23 is set. The fault is also reset aftera successful restart.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.Possible RU: TU_13, PCMref_1, PCMref_2Local action: None.


33/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


33

7.2.21 Single wander problem PCM ref

Fault no: 20Fault cause: A TU has been alone in reporting one orboth of the TU faults PCMref1, illegal high wanderand PCMref2, illegal high wander during a coordination time of 15 seconds.Fault cease: The TU stops reporting the fault above orclass 2 fault #24 is set. The fault is also resetafter a successful restart.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.Possible RU: TU_13, PCMref_1, PCMref_2.Local action: None.

7.2.22 PCMref interruption

Fault no: 22Fault cause: Two or more TUs reports the TU faultPCMref1, interruption and/or PCMref2, interruption for at least 5 seconds.Fault cease: The fault will be reset when all TU:sstops the reporting of the faults mentioned above. Itis also reset if the Single interruption PCMref isset.

Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults PCMref1/2, interruption see figure 5.Possible RU: EXT, TRXC, PCMref_1, PCMref_2.Local action: The PCMref that is pointed out isBLOCKED. This may cause TMH to select a new executivereference. If so then a resynchronization of master TUwill be done. If no deblocked reference exists afterthe blocking then TF will start the hold over operation, see chapter 3.

7.2.23 PCMref frequency fault

Fault no: 23Fault cause: Two or more TUs has been reporting the TUfault PCMref1 illegal high relative frequency deviation and/or PCMref2 illegal high relative frequencydeviation longer than 30 seconds.Fault cease: The fault will be reset when all TU:sstops the reporting of the faults mentioned above. Itis also reset if the Single frequency fault PCMref is set.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.

Possible RU: EXT, PCMref_1, PCMref_2.Local action: The PCMref that is pointed out isBLOCKED. This may cause TMH to select a new executivereference. If so then a resynchronization of master TU


34/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


34

will be done. If no deblocked reference exists afterthe blocking then TF will start the hold over operation, see chapter 3. Note: If TF has a class 1 fault then TF can makeautomatic synchronization attempts towards thePCMreferences, one at the time. If such a synchronization test succeeds then the PCMreference which wasused in the successful test will have all faults reset.

7.2.24 PCMref illegal high wander

Fault no: 24Fault cause: Two or more TUs has been reporting the TUfault PCMref1, illegal high wander and/or PCMref2,illegal high wander longer than 30 seconds.Fault cease: The fault will be reset when all TU:sstops the reporting of the faults mentioned above. Itis also reset if the Single wander problem PCMref isset.Disturbances: None detected in TMH. For disturbancescorresponding to the TU faults see figure 5.Possible RU: EXT, PCMref_1, PCMref_2.Local action: The PCMref that is pointed out isBLOCKED. This may cause TMH to select a new executivereference. If so then a resynchronization of master TU

will be done. If no deblocked reference exists afterthe blocking then TF will start the hold over operation, see chapter 3. Note: If TF has a class 1 fault then TF can makeautomatic synchronization attempts towards thePCMreferences, one at the time. If such a synchronization test succeeds then the PCMreference which wasused in the successful test will have all faults reset.

7.2.25 Checksum fault boot PROM

Fault no: 30Fault cause: The TU has reported that a checksum testof the boot PROM has failed. The test was performed atreception of the A" command TEST COMMAND.Fault cease: A new checksum test passed.Disturbances: None.Possible RU: TU13.Local action: Red LED is turned on.

7.2.26 Checksum fault HW revision info

Fault no: 31Fault cause: The TU has reported that a checksum testof the HW revision area has failed. The test wasperformed at reception of the A" command TESTCOMMAND.


35/36

DESCRIPTION




L Z F 0 3 2 4 1 / 1 M

R J


Datum - Rev

Nr -


No.

Date


35

Fault cease: A new checksum test passed.Disturbances: None.Possible RU: TU13.Local action: Red LED is turned on.

7.3 TF EXTERNAL CLASS 1 FAULTS

7.3.1 LMT, Local Operator Intervention

Fault no: 2Fault Cause: The Access State for MO TF is changed fromCONNECTED to LOCALLY DISCONNECTED due to interventionfrom the LMT.Fault cease: The Access State for MO TF is changed backto CONNECTED due to cease of LMT intervention.Disturbance: None.Possible RU: Local Action: Control taken over from BSC.


36/36

DESCRIPTION



R J


Datum - Rev

Nr -


No.

Date


36

8 REFERENCES

Ref 1. Function description TRS synchronization12/155 16HRB 103 02 Uen

Documents

RBS200 TF Fault Code List