Operational Manual for FOX multiplexer., Exercises of Electrical and Electronics Engineering

Download Operational Manual for FOX multiplexer. and more Exercises Electrical and Electronics Engineering in PDF only on Docsity!

FOX from ABB

covers all your communication require-

ments in one system

FOX Manual "Units"

Part 1

4

th

Edition

1KHW 001447 R

The universal multiplexer FOX

ABB

FOX from ABB, covers all your communication

requirements in one system.

FOX Manual Units, Part 1

(4th Edition)

COBUX 219, 223, 212, 213

COBUV 220, 224, 217, 218

COBUX/COBUV

Copyright and Confidentiality: Copyright in this document vests in ABB Ltd. This document contains confidential information which is the property of ABB. It must be held in confidence by the recipient and may not be used for any purposes except those specifically authorised by contract or otherwise in writing by ABB. This document may not be copied in whole or in part, or any of its contents disclosed by the recipient to any third party, without the prior written agreement of ABB.

Disclaimer: ABB has taken reasonable care in compiling this document, however ABB accepts no liability whatsoever for any error or omission in the information contained herein and gives no other warranty or undertaking as to its accuracy.

ABB reserves the right to amend this document at any time without prior notice.

Document number: 1KW001447R0001 / Ref [315]

ABB Switzerland Ltd Bruggerstrasse 72 CH-5400 Baden Switzerland © January 2005 by ABB Ltd

ABB Contents^ © ABB Ltd

• Safety Contents i
  • Referenced documents
• Introduction
  • Functions
    • Common functions of the COBUX and COBUV
    • Conference function (COBUV only)
    • Functional versions
    • Definition of terms
  • Front panel
• Architectural description
  • Block diagram
  • Descriptions
    • CPU block
    • Clock Supply and Synchronisation
    • Intra Unit Communication
    • Highway Access and DXC
    • NE Database
    • QX-interface
    • F-/Q 1 -interface
    • Q 1 -master interface
    • OSPF router
    • Alarm Interface
    • Metering Pulse Generator
    • 1+1 Unit Protection Control
    • Diagnostics
    • Conference Processing (COBUV only)
• Functional description
  • Clock supply & synchronisation PDH domain (PETS)
    • Timing sources and signals
    • Timing signal outputs
    • PLL and clock signals
    • Modes
    • Jitter transfer function
  • Intra unit communication
    • Overview
    • Hardware control
    • μC-LAN
    • ICN
    • NE MIB / PC memory card ABB Contents © ABB Ltd
    • Cross connect
      • Principles
      • Capacities
    • 1+1 equipment protection
    • Metering pulse generator
    • Diagnostic function
    • Conference function (COBUV only)
      • Analogue Conference
      • Digital Conference (signalling)
      • Example
    • NE management and control
      • Handling of configuration data
      • Software Management
      • Fault Management
    • Interfaces for management communication
      • QX-interface:
      • F-interface:
      • Q 1 -(slave) interface:
      • Q 1 -master interface:
      • PDH ECC
      • SDH ECC
      • ECC over ATM
      • Bandwidth for the allocation of PDH and SDH ECCs
    • Alarm Interfaces
      • Alarm state outputs
      • Inputs for external alarm signals
    • Interfaces for timing signals
  • Installation
    • Prerequisites
    • Use of slots
    • Connections and cables
      • F- interface (9-pin submini D)
      • QX-interface (RJ-45 connector)
      • DIN 41 612 front connector
      • Q 1 -(slave) interface
      • Q 1 -master interface
      • Alarm interfaces
      • Synchronisation interfaces
    • Fixing the cables to the cable tray
  • Configuration and Operation
    • Overview
    • Setting basic parameters
      • Board
      • Communication IF
    • NE MCN parameters
      • Guidelines for the configuration of the NE MCN part
      • SDH ECC
• iv “Units” Part 1 1KHW001447R - OSI DCN ABB Contents © ABB Ltd - PDH ECC - IP Router
  • Setting a conference (COBUV only!)
    • Name
    • Conference
    • Input attenuation
    • Noise suppression
    • Output attenuation
  • Setting diagnostics
    • Test set-up
    • Configuration of the diagnostic function
    • Enable diagnostics
    • Bit rate
    • Test signal (data)
    • Test pattern (signalling)
    • Error insertion
    • Cross connections for diagnostics
    • Download configuration or configuration changes
  • Setting 1+1 equipment protection for COBU
    • Implementation
    • Switching criteria
  • Status/Maintenance functions
    • Board
    • Communication IF
    • NE MCN parameters
    • IP Router
    • IP Ping
    • Diagnostics
  • Operating states of the COBU
  • COBU start up
    • Cold/warm start up
    • Influence on traffic and services
  • Removal of operating COBU
  • Setting Alarm Parameters
  • Summary of UCST default parameters
    • Board layer
    • Communication IF layer
    • SDH ECC layer
    • OSI DCN layer
    • PDH ECC layer
    • IP Router
    • Conference Parties layer (COBUV only)
    • Diagnostics layer
    • Unit alarms
• Performance monitoring
  • Definition of terms
  • Filtered PM
    • Diagnostics
      • Examples of COBU PM ABB Contents © ABB Ltd
    • Unfiltered PM
  • Alarms and Notifications
    • Fault cause tables
      • Board Layer
      • Communication IF layer
      • SDH ECC layer
      • PDH ECC layer
    • Notifications
      • Notifications control unit board layer
      • Notifications NE unit board layer
      • Notifications IP router layer
      • Notifications OSI DCN layer
  • Maintenance
    • Unit top component and front panel view
    • General aspects
    • Inventory Management
    • Software Download
    • Upgrades
    • Exchange of the PC Card
      • PC Card Handling Precautions
      • PC Card exchange procedure
• vi “Units” Part 1 1KHW001447R
• Figure 1: Released Control units/FOX applications Figures
• Figure 2: Front panel view of COBU unit
• Figure 3: Block diagram of COBU unit
• Figure 4: COBU PDH clock supply and synchronisation block diagram
• Figure 5: Timing sources sample dialogue
• Figure 6: Communication structures vs. unit category
• Figure 7: Principles of traffic channel diagnostics
• Figure 8: Example of a conference party with 3 participants
• Figure 9: Example for the signalling in a conference with 3 participants
• Figure 10: Internal wiring of the alarm state relays
• Figure 11: Internal wiring of the alarm inputs
• Figure 12: Signal/pin layout for the F- interface connector
• Figure 13: COBUX/C3.1-1 cable drawing
• Figure 14: COBUX/C3.1-2 cable drawing
• Figure 15: COBUX/C3.1-3 cable drawing
• Figure 16: COBUX/C3.1-3 cable application drawing
• Figure 17: Signal/pin layout for the QX-interface connector
• Figure 18: COBUX/C2.1-1 cable drawing
• Figure 19: COBUX/C2.1-2 cable drawing
• Figure 20: Signal/pin layout for the DIN 41 612 connector
• Figure 21: COBUX/C1.4 cable drawing
• Figure 22: COBUX/C1.3 cable drawing
• Figure 23: COBUX/C1.2 cable drawing
• Figure 24: COBUX/C1.1-1 cable drawing
• Figure 25: COBUX/C1.1-3 cable drawing
• Figure 26: COBUX/C1.1-4 cable drawing
• Figure 27: COBUX/C1.1-6 cable drawing
• Figure 28: Fixing the cables to the cable tray (example for the FOX 515)
• Figure 29: Unit Configuration Parameters - Board layer dialogue
• dialogue Figure 30: Unit Configuration Parameters - Communication IF layer
• Figure 31: Flow chart configuration of the management communication
• dialogue Figure 32: Unit Configuration Parameters – Conference Part. layer
• Figure 33: Unit Configuration Parameters – Diagnostics layer dialogue
• Figure 34: Create Cross Connections dialogue
• Figure 35: NE Configuration – Add Protecting Unit dialogue
• Figure 36: Status/Maintenance - Board dialogue
• Figure 37: State messages of COBU
• Figure 38: Status/Maintenance – Communication IF dialogue
• Figure 39: Status/Maintenance – IP Router IP Ping Request dialogue
• Figure 40: Summary of analysis and quality assessment functions
• Figure 41: Diagnostics – No Status Available dialogue
• Figure 42: Status/Maintenance – Diagnostics dialogue
• Figure 43: Test set-up for timeslot monitoring
  • Figure 44: Status/Maintenance – Diagnostics dialogue Analysis of a n x ABB Contents © ABB Ltd
  • kbit/s test signal
  • Figure 45: Status/Maintenance – Diagnostics dialogue Analysis of a n x
  • kbit/s test signal, AIS on signalling
  • Figure 46: Status/Maintenance – Diagnostics dialogue Analysis of a
  • kbit/s test signal (data)
  • Figure 47: Status/Maintenance – Diagnostics dialogue Analysis of a
  • kbit/s test signal (signalling)
  • transparent test signals, no offset Figure 48: Status/Maintenance – Diagnostics dialogue Analysis of 2 Mbit/s
  • transparent test signals, with offset Figure 49: Status/Maintenance – Diagnostics dialogue Analysis of 2 Mbit/s
  • Figure 50: Test set-up for delay measurements
  • Figure 51: Status/Maintenance – Diagnostics dialogue
  • Figure 52: Status/Maintenance – Diagnostics dialogue
  • Figure 53: Status/Maintenance – Diagnostics dialogue
  • Figure 54: Status/Maintenance – Diagnostics dialogue
  • Figure 55: Operating states and NE activities indicated via the unit LED
  • Figure 56: Operating states indicated via the Unit LED
  • Figure 57: COBU - Performance Monitoring sample dialogue
  • presentation Figure 58: COBU - Performance Monitoring sample dialogue Events
  • presentation Figure 59: COBU - Performance Monitoring sample dialogue Ratio
  • Figure 60: Fault Causes and alarms of the Board Layer
  • Figure 61: Fault Causes and alarms of the Communication IF Layer
  • Figure 62: Fault Causes and alarms of the SDH ECC Layer
  • Figure 63: Fault Causes and alarms of the PDH ECC Layer
  • Figure 64: Notifications on the Control Unit Board Layer
  • COBU) Figure 65: Notifications on the NE Unit Board Layer (proxy function of the
  • Figure 66: Notifications on the IP Router Layer
  • Figure 67: Notifications on the OSI DCN Layer
  • Figure 68: COBU top component side and front panel view
  • Figure 69: To remove the PC Memory Card
  • Figure 70: To insert the PC Memory Card
• viii “Units” Part 1 1KHW001447R

ABB COBUX/COBUV^ © ABB Ltd

Introduction

Functions Common functions of the COBUX and COBUV

The COBUX and COBUV are control units for the FOX 515/512 Multiservice Access Systems. Please note, that not all control units are released for all FOX subracks (refer to the table below). With the UCST R6A the R5 and R4 control units are available for the FOX system configuration. The control units are released for the FOX and corresponding applications as follows:

Figure 1: Released Control units/FOX applications

Control Unit

Function Unit Release FOX

R5 R

40HW 128HW 40HW 128HW

COBUX 223 219 213 212 R5, R4 R5, R

COBUV 224 220 218 217 R5, R4 R5, R

The functions common to all COBUX and COBUV control units are:

• Clock supply and synchronisation for the PDH domain (PETS) for the NE
• Integration of 2 external timing signals for the synchronisation of the NE (1 PETS only and 1 SETS or PETS), 3 outputs with timing signals synchronised to PETS and 1 output SETS locked or non SETS locked.
• NE database
• NE management/control to allow: − Configuration of peripheral units − Surveillance and alarm generation for peripheral units − Provision of the NE fault list and NE alarm/event logbook − Access for local and remote management communication with the UCST (EM) via the following management interfaces: − F-interface (external) − QX-interface (external) − Q 1 -interface (external) − PDH and SDH ECC (internal) − ECC over ATM, as PDH ECC (internal) − Provision of the Q 1 -master interface (external) to manage a co-located LEGACY FOX on the local Q-Bus via the management communication of the FOX 515/512. − Handling of data transactions for the database (configuration download and upload, backup database) − Software download for the embedded software (ESW) − Autonomous restart of the NE after a power failure (no interaction by EM required) − Inventory management
• 1+1 equipment protection
• UBUS ↔ PBUS access
• UBUS digital cross connect

page 2 of 108 FOX Manual Units, Part 1 1KHW001447R

ABB COBUX/COBUV^ © ABB Ltd

The COBUX and COBUV provide a UBUS access capacity of 8 highways , each highway for traffic signals (signalling included) − 31 x 64 kbit/s (depending on the unit as a bundle access for 31 TSs or as n x 64 kbit/s TS access) − the highways access in the slots of the subrack depends on the FOX subrack.

The even numbered highways are reserved exclusively for signalling.

• PBUS access control The COBUX and COBUV provide a PBUS access capacity (signalling included) of up to 128 highways depending on the functional units, each highway configurable for traffic signals − 2 Mbit/s transparent or − 31 x 64 kbit/s (depending on the unit as a bundle access for 31 TSs or as n x 64 kbit/s TS access)
• Integrated central diagnostic function
• Integration of 4 external alarm sources in the NE fault management
• Capability to output the NE alarm status "Urgent Alarm" and "Non-urgent Alarm" by means of: − two pairs of change-over relay contacts − optical LED indicators on the control unit front panel
• Generation of 12 kHz or 16 kHz metering pulses

Conference function (COBUV only)

The COBUV control units also provide the possibility to create up to 21 bi- and uni-directional conferences, each conference with up to 64 participants (64 kbit/s traffic signals). The conferences also process the signalling associated with the traffic signals.

Functional versions (^) The UCST R6A supports 2 x 4 functional units for the COBU control unit, each with its corresponding R4 and R5 template:

• COBUX 223 − ATM, SDH and PDH functionality − PBUS capacity (signalling included): 40 highways each 2 Mbit/s equivalent to 40 x VC-12 or 1280 x 64 kbit/s − UBUS capacity (signalling included): 2 x 4 highways each 2 Mbit/s equivalent to 8 x 31 x 64 kbit/s − OBUX 213 supports additionally: − SW download for remote units (via local units)) − Compressed MIB (storage and transfer)
• COBUX 219 − ATM, SDH and PDH functionality − PBUS capacity (signalling included): 128 highways each 2 Mbit/s equivalent to 128 x VC-12 or 4096 x 64 kbit/s − UBUS capacity (signalling included): 2 x 4 highways each 2 Mbit/s equivalent to 8 x 31 x 64 kbit/s − SW download for remote units (via local units) − Compressed MIB (storage and transfer)
• COBUX 213 − SDH and PDH functionality

1KHW001447R0001 FOX Manual Units, Part 1 page 3 of 108

ABB COBUX/COBUV^ © ABB Ltd

• COBUV 217

− SDH and PDH functionality − PBUS capacity (signalling included): 128 highways each 2 Mbit/s equivalent to 128 x VC-12 or 4096 x 64 kbit/s − UBUS capacity (signalling included): 2 x 4 highways each 2 Mbit/s equivalent to 8 x 31 x 64 kbit/s − Conference function − SW download for remote units (via local units)

The list above shows only the features that are different between the three types of the control unit.

The hardware versions provided for the COBU differ in the implementation of the interfaces for synchronisation signals. The COBU templates and hardware

• COBUX 219, 223 & 212, 213: ROFBU 367 103/1 R2B R2C
• COBUV 220, 224 & 217, 218: ROFBU 367 103/2 R1A R1B

or more recent hardware provide the interfaces for synchronisation as specified in this document (i.e. 120 Ω impedance for ESI-1 and ESO-4 and galvanic isolation for ESO-1 and 4).

Definition of terms (^) In this document, the generic names

• FOX is used to name the following systems released with the UCST R6A: − FOX 515 − FOX 512
• legacy FOX is used to name the following systems: − FOX-U − FOX-U/M (-U/E)
• COBU is used to name the following control units and templates released with the UCST R6A: − COBUX 219 (R5) − COBUX 223 (R5) − COBUX 212 (R4) − COBUX 213 (R4) − COBUV 220 (R5) − COBUV 224 (R5) − COBUV 217 (R4) − COBUV 218 (R4) The FOX Manual [302] provide complementary information.

Front panel The front panel view below applies for all versions of the COBU:

1KHW001447R0001 FOX Manual Units, Part 1 page 5 of 108

ABB COBUX/COBUV^ © ABB Ltd

Figure 2: Front panel view of COBU unit

Q 1 -unit interface module (C1.4)

D-Sub 9-pin male connector (C3.1) for the F-interface

RJ-45 8-contact female connector (C2.1)

Optical Fault Indication

Unit LED (bicolor red-green) UA LED (red) Traffic LED (red) NA LED (yellow)

............ ............... ... ............ ...

Fixing screw Pull-out handle

Fixing screw

Pull-out handle

Identification (HW) label

DIN 41 612 connector type C, 2 x 32 contacts, male, 4 modules with coding

Alarm interface module (C1.2)

**- 2 x 2048 kHz clock input

• (3 + 1) x 2048 kHz clock output**

Q 1 -master interface module (C1.3)

Synchronisation interface module (C1.1)

for the QX-interface

Architectural description

The COBU function is implemented using the following functional blocks:

• CPU block with micro-controller, memory and peripheral logic
• Clock supply and synchronisation (PETS)
• Peripheral unit communication
• DXC and Highway Access
• NE Database
• Unit protection control
• OSPF Router (NE management communication)
• IS-IS Router (NE management communication)
• Metering Pulse Generator
• Diagnostics

page 6 of 108 FOX Manual Units, Part 1 1KHW001447R

ABB COBUX/COBUV^ © ABB Ltd

Block diagram^ The figure below shows the functional block diagram of the COBU unit:

Figure 3: Block diagram of COBU unit

UBUS

PBUS

UBUS IF

PBUS IF

Highway Access and DXC

Peripheral Unit Communication

Diagnostics

OSPF Router

1+1 Unit Protection control

Metering Pulse Generator

Hardware Control

ICN

uC-LAN

Master/Slave control

Metering Pulses

Clock Supply and Synchronisation (PETS)

Clock Signals for PBUS and UBUS

Clock Bus Lines 1, 2, 3, 4

ESI clock signals 2048 kHz (PETS & SETS)

ESO clock signals 2048 kHz (PETS & SETS)

Conference processing

Alarm Interfaces

Q 1 -(slave) interface

Qx -interface

NE Database PCMCIA card

Qx

F Q 1 -(slave)

Digital inputs Relay contacts outputs

Q 1 -master interface

Q 1 -master

CPU

Clock signals from SETS

F-interface

Conference processing block: COBUV only

Descriptions CPU block (^) The CPU functional block controls and monitors all the other functional blocks of the COBU. The local CPU executes the COBUX program and provides all the COBU internal functions.

Clock Supply and Synchronisation

The most important part of the Clock Supply and Synchronisation functional block is a phase locked loop (PLL) which allows the PETS system of the NE to synchronise on one of the PETS timing sources.

The Clock Supply and Synchronisation functional block provides the NE internal interfaces for the NE synchronisation to the PETS timing sources (used in conjunction with the PLL) and to allow the distribution of the clock signals within the NE. The control units provide the interfaces for the external timing signals ESI- PDH/SDH and ESO-PDH/SDH:

• Inputs: − ESI-PDH: ESI-1 and 2 − ESI-SDH: ESI-
• Outputs: − ESO-PDH: ESO-1 … 3 − ESO-SDH: ESO-

page 8 of 108 FOX Manual Units, Part 1 1KHW001447R

ABB COBUX/COBUV^ © ABB Ltd

The Clock Supply and Synchronisation functional block provides toggle or frequency detectors for the most important clock signals that are used for clock recovery and distribution.

Intra Unit Communication The Peripheral Unit Communication functional block provides the interfaces that allow the COBU to manage the peripheral units of the NE. This includes the interfaces for the management communication with the units and the control signals to monitor and reset the unit hardware.

Highway Access and DXC (^) The Highway Access and DXC functional block provides the COBU access to the UBUS and PBUS highways. The implementation of the highway access interfaces allows you to insert and remove a slave control unit without disturbing the traffic signals on the UBUS and PBUS.

Additionally, the Highway Access and DXC functional block provides the digital cross connect that allows the cross connection of traffic signals between:

• PBUS ↔ UBUS
• UBUS ↔ UBUS.

The Highway Access and DXC functional block also handles the access of the management communication (ECC) and diagnostic function to the PBUS.

NE Database The NE Database functional block holds the MIB of the NE. The MIB is physically implemented on a PC memory Card and has an assigned partition on the card.

With platform release R6, configuration information is transferred and stored in compressed format making a more efficient use of space in the PC memory Card and reducing transfer time

QX-interface The QX-interface functional block provides the

• Physical Medium Attachment (PMA) which attaches the NE to a 10 BaseT Ethernet LAN.
• Physical LAN Signalling (PLS) and the Media Access Control (MAC) as required by the QX-interface.

F-/Q 1 -interface The F-interface Q 1 -(slave) interface functional block provides the:

• Universal asynchronous receiver/transmitter (UART) which handles the data transmission over the F-interface and the Q 1 -(slave) interface.
• Transceivers which adapt the internal signals for RS-232 (F-interface) and RS-485 (Q 1 -(slave) interface) transmission. The F-interface Q 1 -(slave) interface share the same UART, thus it is only possible to use one of the two interfaces at a time.

Q 1 -master interface The Q 1 -master interface functional block provides the:

• Universal asynchronous receiver/transmitter (UART) which handles the data transmission over the Q 1 -master interface.
• Transceivers which adapt the internal signals of the Q 1 -master interface for the RS-485 transmission.

1KHW001447R0001 FOX Manual Units, Part 1 page 9 of 108