Abb Fox Eoc r8 Rb 1khw002011

ABB Power Systems

FOX515 EOC (Embedded Operation Channel) User Manual

FOX EOC Platform Release (R8)

FOX EOC (Embedded Operation Channel)

Platform FOX515 Release R8

Release History: Release 7B: February 2007 Release 8B: December 2008 Release 8C: August 2009 December 2009 May 2010

Copyright and Confidentiality: All rights of this document remain with ABB Ltd (ABB). 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: 1KHW002011 ABB Ltd Power Systems Bruggerstrasse 72 5400 Baden – Switzerland © ABB Switzerland Ltd, 2010 The right to modifications or deviations due to technical progress is reserved.

1KHW002011 page 2 of 58 ABB


Contents i Precautions and safety 6 Referenced documents 6

1 Introduction 9 Overview 9 Definition of terms and documentation 9

2 Application of the EOC 11

3 Incorporating FOX -U/M -U in an O&M system 13

4 Communication principles 15

5 Detailed description of the communication 17 Establishment of connection 17 Addressing the requested subscriber 19 Reaction of the addressed subscriber 19 Through-connection «Reply channel» (SIFOX) 19 Through-connection «Reply channel» (O & M system) 19 Data exchange 19 Clearing a connection 19

6 Implementation 21 Summary 21 Configuration of SIFOX 21 Configuration of the NE 23 Connecting the EM(S) to the NE 32

7 Examples of EOC configuration 39 Generic example 39 Extending EOC via TUNOS / TUNOL V.11 OHC 53

ABB page 3 of 58 1KHW002011


Figures

Figure 1: Management communication with EOC 11 Figure 2: Line network with EOC in a FOX -U environment 14 Figure 3: meshed EOC network 18 Figure 4: "Unit Configuration Parameters" UCST mask 22 Figure 5: "EOC Parameters" UCST mask 23 Figure 6: "Parameters" UCST mask 23 Figure 7: Communication links of the EOC inside a NE (gateway) 24 Figure 8: Configuration of the network connections for an EOC 25 Figure 9: Setting of the HDLC address for the F-interface (CENCA) 26 Figure 10: IP address settings for the COBU<X> 27 Figure 11: Parameter setup in the "Add Management Network Agent" field for an FOX-U/M and FOX-U/E gateway 28 Figure 12: Parameter setup in the "Add Management Network Agent" field for an FOX515 gateway 29 Figure 13: Addition of an FOX515 to an EOC management network 30 Figure 14: Addition of an FOX-U to the EOC management network 31 Figure 15: NE's added to the EOC management communication network 32

Figure 16: Wiring schematic connection CENCA SIFOX 33

Figure 17: Wiring diagram Connection Interface Converter SIFOX 34

Figure 18: Connection of the O & M system SIFOX (passive converter) 35 Figure 19: Wiring schematic of the passive EOC converter 35

Figure 20: Connection of the O & M system SIFOX (active converter) 36 Figure 21: Connection diagram of the Modem-SIFOX Converter long distance 37 Figure 22: Wiring schematic of the Modem-SIFOX Converter long distance 37 Figure 23: Connection diagram of the Modem-SIFOX Converter short distance 38 Figure 24: Wiring schematic of the Modem-SIFOX Converter short distance 38 Figure 25: Example of an EOC network 39 Figure 26: Settings of the "Management Network Parameters" 40 Figure 27: NE parameters for NE1 41 Figure 28: List of all managed NE's in the EOC network 41 Figure 29: Declaration of subunit 1 and 2 for EOC operation 42 Figure 30: Set-up of the EOC parameters for SIFOX, subunit 1 42 Figure 31: Set-up of the EOC parameters for SIFOX, subunit 2 43 Figure 32: Set-up of the common parameters for subunit 1and 2 43 Figure 33: Set-up of the F-interface in control unit CENCA 44 Figure 34: Cross connections for the EOC in NE1 45 Figure 35: Declaration of subunit 1 for EOC operation 46 Figure 36: Set-up of the EOC parameters for SIFOX, subunit 1 46 Figure 37: Set-up of the common parameters for subunit 1 47 Figure 38: Set-up of the F-interface in control unit CENCA in NE2 47 Figure 39: Cross connections for the EOC in NE2 48 Figure 40: Declaration of the subunits 1-4 for EOC operation 49 Figure 41: Set-up of the EOC parameters for SIFOX, subunits 1-4 49 Figure 42: Set-up of the common parameters for subunits 1-4 50 Figure 43: Set-up of the F-interface in control unit CENCA in NE3 50 Figure 44: Cross connections for the EOC in NE3 51



Figure 45: Set-up of the F-interface in control unit CENCA in NE4 52 Figure 46: Set-up of the F-interface in control unit CENCA in NE5 52 Figure 47: Set-up of the F-interface in control unit SUCO in NE6 53 Figure 48: FOX network with peripheral NE's 53 Figure 49: Cables required for installation at the NEs 54

Figure 50: Pin allocation of the cable SIFOX V.11 interface TUNOS 55

Figure 51: Pin allocation of the cable SIFOX V.11 interface TUNOL 55 Figure 52: Pin allocation and wiring schematic for cable 2 for TUNOS. 56 Figure 53: Pin allocation and wiring schematic for cable 2 for TUNOL. 56



Precautions and safety

For generic information on precautions and safety refer to the manual “pre-cautions and safety”.

Referenced documents

1KHW002057 FOX 515 Technical Description

1KHW002058 FOX 512 Technical Description

1KHW002013 COBUX 145, 146 & COBUV 137, 237 COBUX 212, 213 & COBUV 217, 218 User Guide

1KHW002059 FOX User Guide

1KHW002060 UCST/System Operation Basics User Guide

1KHW002009 UCST Installation & Commissioning User Guide

1KHW002061 FOX Management Communication Networks User Guide



Technical support ABB Technical Support is available as follows:

ABB Switzerland Ltd

Power Systems

Utility Communications

Bruggerstrasse 72

5400 Baden

Switzerland

Phone: +41 58 589 37 35

or: +41 844 845 845 (Call Center)

Fax: +41 58 585 16 82

E-Mail: [email protected]

URL: www.abb.com/utilitycommunications


mailto:[email protected]

http://www.abb.com/utilitycommunication



FOX EOC Platform Release (R8) Introduction

1 Introduction

Overview The management communication via an EOC (Embedded Operation Chan-nel) is suitable for the legacy members of the FOX platform such as the FOX -U/M -U and the DSL system.

The EOC is a proprietary communication structure based on the SIFOX unit and requires a 64 kbit/s timeslot in the transmission network. The net trans-mission rate of the EOC is limited to 9600 kbit/s for legacy FOX.

The EOC can be used for access networks with mixed types of FOX equip-ment since it is also fully implemented for the FOX515/512 and remains compatible, provided you have UCST/FOXMAN-UN R4E (or higher re-leases).

In mixed networks with FOX515/512 and FOX-U/M /-U and DSL systems it is recommended that you establish separate management communication facilities via the EOC and ECC (Embedded Communication Channel):

The EOC fits to the management application of the legacy FOX -U/M -U multiplexers and the DSL system.

The ECC covers the management application of FOX515/512 multiser-vice access systems.

The download of embedded SW to the FOX515/512 and extended man-agement possibilities require more transmission performance than the EOC is able to provide.

Thus, the implementation of the ECC is highly recommended for all man-agement communication with the FOX515/512.

Accordingly, the description of the EOC in this chapter focus' applications in the legacy FOX -U/M -U environment.

For more information of the ECC implementation with the FOX515/512, refer to FOX Management Communication Networks User Guide.

Definition of terms and documentation

Network elements The control units defines the FOX type. The generic name

FOX is used to name the following legacy FOX systems: FOX -U (CENCA) FOX FOX –U/E (CENCA)

DSL system is used to name the legacy DSL system: DSL rack system (SUCO)

FOX515/512 is used to name the following systems released with the UCST R5C: FOX515 FOX512


Introduction FOX EOC Platform Release (R8)

1KHW002011 page 10 of 58

The following units are involved for the EOC implementation: Units

COBU<X> is used to name the following control units and templates re-leased with the UCST R5C: COBUX 145 (R3) COBUX 146 (R3) COBUX 212 (R4) COBUX 213 (R4)

COBUV 137 (R3) COBUV 237 (R3) COBUV 217 (R4) COBUV 218 (R4)

For the COBU<X> Technical Description and User Guide, refer to COBUX 145, 146 & COBUV 137, 237 COBUX 212, 213 & COBUV 217, 218 User Guide.

COBUL 215 (R3) COBUQ 144 (R3) COBUV 216 (R4)

Both control units have their own technical description. For the

COBUL 215, 216 COBUQ 144

The COBU<X>, COBUL and COBUQ are not compatible with the FOX-U/M and FOX-U/E.

The CENCA is the control unit for the FOX-U/M and FOX-U/E and not compatible with the FOX515/512.

The SIFOX is a UBUS unit, initially released for the FOX-U/M and FOX-U/E.

The UCST R5C provides a unified layering model for internal and external traffic signals and the alarm reporting in the NE Fault List. There are some changes to the naming of tabs, subunits and text in the UCST R5C dia-logues.

For details of the UCST, refer to UCST/System Operation Basics User Guide.

ABB

FOX EOC Platform Release (R8) Application of the EOC

2 Application of the EOC

The EOC (Embedded Operation Channel) provides a dedicated communica-tion structure for management communication within a network of FOX mul-tiplexers. The EOC is implemented by means of the SIFOX UBUS unit and the F-interfaces of the control units. A communication channel is built up from the EM(s) throughout the EOC network to the NE addressed. EOC ad-dresses are used for this purpose. The EM(S) accesses the EOC manage-ment communication via a serial port of the SIFOX (gateway), operated in the corresponding EOC (master) mode.

The SIFOX provides interfaces to connect the F-interfaces of local NEs and connects the EOC to the (UBUS) for transmission to other NEs.

A dedicated 64 kbit/s channel (normally a TS in the aggregate signal be-tween two NEs with SIFOX gateway) is configured between the gateway SIFOX and remote SIFOX. All NEs connected to the EOC must have access to a SIFOX interface operated in the EOC slave mode. The EOC is released as soon as a particular communication channel is no longer needed.

The EOC can be optimised for various sizes of networks and provides a net bit rate of 9600 bit/s.

Figure 1 shows an example for the management communication via the EOC in a mixed FOX network.

Figure 1: Management communication with EOC


Application of the EOC FOX EOC Platform Release (R8)


The QX-interface of the FOX515/512 can be used in parallel to the EOC manage-ment communication for local management access or access to the ECC.

An EOC communication structure can be implemented in networks with FOX515/512 for legacy NEs (such as the FOX-U/M and FOX-U/E) inde-pendent of the ECC implemented for the FOX515/512. In order to generate the EOC the FOX515/512 subrack close to the EM must be equipped with the SIFOX unit.

FOX EOC Platform Release (R8) Incorporating FOX –U/M/-U in an O&M system

3 Incorporating FOX-U/M/-U in an

O&M system The FOX is configured and the alarm status is scanned via the «F interface» (front-mounted connector of the CENCA unit). For the transmission of the configuration data and alarm status between the CENCA and the remote O & M system via the EOC, you need a SIFOX unit. Up to four CENCA units can be connected to a SIFOX unit. A mixed operating mode, such as for ex-ample one FOX (CENCA) and three X.24 data interfaces, is the standard configuration.

You must configure the SIFOX interface which is connected to the CENCA unit for EOC mode (for control of the communication).

The O & M system is connected via an interface converter to the local SIFOX. Configure the SIFOX interface to which the O & M system is con-nected as the «Master» and the SIFOX interface to which the CENCA unit is connected as the «Slave», both in the local and in the remote FOX. The communication protocol works on a Master-Slave principle and permits only one «Master» in the network.

The EOC data are transmitted via the SIFOX in a defined time slot (normally TS 31) together with the information signals. In every FOX located in the network, this data is transmitted via the SIFOX to a CENCA. Irrespective of the number of «Slaves» in the network, the EOC occupies only one time slot (duplex).

Figure 2 shows part of a line network with four FOX sites. This subnetwork can be remotely configured and monitored by FOX 1. Each FOX is fitted with a SIFOX unit. The interface of the SIFOX unit which is going to be used for the EOC channel, has to be configured either as EOC Master or as EOC Slave.


Incorporating FOX –U/M/-U in an O&M system FOX EOC Platform Release (R8)

1KHW002011 page 14 of 58

Figure 2: Line network with EOC in a FOX -U environment

Direction of transmission Request (Master to Slave)

Direction of transmission Reply (Slave to Master)

ABB

FOX EOC Platform Release (R8) Communication principles

4 Communication principles

The communication principles of an EOC network are described for a pure FOX -U/M -U network environment.

For the local configuration and alarm polling of a FOX, a PC running the UCST software is connected to the F interface of the CENCA.

In a network with several FOXs (each fitted with a SIFOX) they are linked via an EOC and are connected to an O & M system, which can be situated at any position in the network. With the exception of a full software down load, the same UCST functions can be performed from a remote FOX as with the local configuration.

In idle mode the «Request» and «Reply» connections are not switched through, but set up only as a partial connection from FOX to FOX.

The O & M system controls the setting up of the connection in that it sends a request to communicate via the SIFOX and the EOC. Subsequently the EOC in each SIFOX is connected through («Request» connecting direction).

Shortly after, the O & M system (Master) sends a «Connect Command» with the address of the desired FOX (Slave). The addressed FOX now estab-lishes a «Reply channel» to the Master by activating its F interface.

It is assumed that the O & M system has addressed FOX 3 (Fig. 3). First, the request to communicate is received in each CENCA via its SIFOX. Only in FOX 3 does the CENCA recognize its own address and acknowledge this by activating its F interface. During cyclic testing the SIFOX of FOX 3 recog-nizes the request from the CENCA for a connection. This causes an instant through-connection of the «Reply channel» via FOX 2 and FOX 1 to the O & M system.

Finally, the «Reply channel» in FOX 1 is connected through to the O& M system. The exchange of information can now start.

This point-to-point connection between the O & M system and the CENCA in FOX 3 will be cleared down by the O & M system.


Communication principles FOX EOC Platform Release (R8)


FOX EOC Platform Release (R8) Detailed description of the communication

5 Detailed description of the

communication The through-connection of the EOC for the exchange of data between the O & M system and the addressed FOX comprises the following procedures:

Establishment of a connection in the direction «Master» «Slave» (Request)

Addressing a desired Subscriber (Connect)

Establishment of a connection in the direction «Slave» «Master» (Reply)

Exchange of data

Clearance of connection in both directions if necessary

Establishment of connec-tion

An O & M system (FOXMAN-UN or UCST) with a V.24 interface is used as Master. The communication is controlled by the signals RTS (Request To Send) and CTS (Clear To Send).

To show all the characteristics of the EOC, a meshed network as shown in Figure 3. is used as an example. In this network example the operating safe-ty is increased with a supplementary connection between FOX1 FOX3, FOX2 FOX3 and FOX3 FOX4.

The nodes FOX5, FOX6 and FOX7 are located very close to FOX4 (installed in the same rack). If no further EOC distribution is required in this location, the nodes FOX5, FOX6 and FOX7 can be connected via the "SIFOX 4 EOC" cable to the SIFOX unit inserted in FOX4. This configuration permits the connection to 4 FOX nodes using one SIFOX board only.

The distribution of an EOC management communication is not supported in the DSL system. The above mentioned configuration permits you to integrate DSL system subracks, if the F-interface of the SUCO2 control unit is connected via a SIFOX cable to the SIFOX inserted in FOX4. In this case a DSL system can be man-aged remotely via the EOC from a central EM (UCST, FOXMAN-UN) as single NE.


Detailed description of the communication FOX EOC Platform Release (R8)

Figure 3: meshed EOC network

From Figure 3 it is evident that all the channels for both connecting direc-tions, «Request» as well as «Reply», are connected to the SIFOX unit in each FOX.

With the configuration of the SIFOX in EOC mode, it is possible to have up to eight channels wired to a SIFOX unit. A typical situation is shown in Fig-ure 3 with the SIFOX of FOX 3 which has four channels connected.

If the O & M system as «Master» wishes to communicate with a FOX (CENCA) as «Slave», it first sets its «RTS» control signal to «active» and keeps it in this state until the end of the communication.

The SIFOX connected to the «Master» recognizes the RTS signal and sends the bit pattern SOM (Start Of Message) on all channels in the " «Slave» direction. All incoming channels from the «Master» direction are cyclically checked in each SIFOX for this bit pattern. The channel in which this bit pattern is first detected, will be through-connected to all channels in the slave direction (including the local interface of the SIFOX in the CENCA). Based on this principle, all CENCA units are connected on the receive side


FOX EOC Platform Release (R8) Detailed description of the communication

with the O & M system one after another. This step-by-step connecting pro-cedure takes a certain amount of time, which depends on the number of cascaded SIFOX units in the network. During this time span, which can be defined by the user, the SOM signal is constantly transmitted. When the time has elapsed, after all channels in the direction «Master to Slave» have been connected through, the SIFOX to which the O & M system is connected, ac-tivates the control signal «CTS».

Addressing the requested subscriber

After receiving the CTS signal the O & M system sends a «Connect Com-mand» with the address of the desired subscriber.

Reaction of the addressed subscriber

The addressed FOX (CENCA) recognizes its own address, sends an RTS control signal to its SIFOX and waits for the SIFOX to return its CTS control signal.

Through-connection «Reply channel» (SIFOX)

After receiving the RTS control signal, the SIFOX sends the bit pattern SOM on all the «Reply channels» in the «Master» direction until a through-connection of the «Reply channel» to the O & M system has been estab-lished. You can determine the duration of this time span which depends on the number of cascaded SIFOX units in the network.

Through-connection «Reply channel» (O & M system)

All incoming channels from the «Slave» direction, are checked cyclically in every SIFOX for the bit pattern SOM. The channel in which this bit pattern is first detected, is switched through to the outgoing «Reply channels».

The SOM bit patterns reach the SIFOX interface which leads to the O& M system via various channels. The channel on which this bit pattern is first detected is switched through to this SIFOX interface.

Data exchange Once the set time has elapsed, the SIFOX in the called FOX sends a control signal CTS to its CENCA. The communication can start now. During this communication, the RTS control signal of the CENCA remains active.

Clearing a connection The clearing of the connection is controlled by the «Master» using the «Dis-connect» command. Once this command is received, the «Slave» switches off its RTS control signal. This causes its SIFOX interface to transmit an EOM bit pattern (End Of Message) on all channels towards the «Master». After this bit pattern is received, each SIFOX will re-start the cyclical check for the SOM bit pattern on all connected channels.

After the «Disconnect» command the O & M system also switches off its RTS control signal and its SIFOX sends the bit pattern EOM on all channels in the direction of the «Slave». After this bit pattern is received each SIFOX clears down the «Request channel» and cyclical checking for the bit pattern SOM is re-established on all connected channels .


Detailed description of the communication FOX EOC Platform Release (R8)


FOX EOC Platform Release (R8) Implementation

6 Implementation

Summary The implementation of the EOC management communication in a complex network consisting of FOX -U/M -U nodes and FOX515/512 nodes requires previous careful network planning. Depending on the size of the network more than one EOC channel may required to address all the FOX -U/M -U nodes, because the maximum number of network elements per EOC is lim-ited to 254 nodes.

The maximum number of NEs for one EOC is limited to 254, but this is a theoretical value. In order to avoid too long response times in practice the total number of NEs should not exceed 60.

Each NE to which the EOC management communication applies must be provided with a unique address for the F-interface.

All configurations for the EOC set-up must be carried via a direct access to the F-interface of the control unit. If a FOX515/512 should be prepared for an EOC management communication, the Qx-interface can be used as an alternative.

Configuration of SIFOX The SIFOX unit consists of 4 full duplex synchronous 64 kbit/s channels. Each of them can be configured for data transmission or as an EOC.

After powering on, the SIFOX is automatically initialized. The SIFOX micro-controller fetches the configuration data out of the CENCA data base and sets them in the unit. The parameters can be written and read in the UCST masks. To read and to configure these masks, firstly select the slot position of the SIFOX. This activates the "Unit Configuration menu . "Parameters" provides access to the SIFOX unit parameters.

Figure 4 shows the "Unit Configuration Parameters" UCST mask, which shows the configuration possibilities for all 4 subunits. For the configuration of the EOC parameters the 2 submenus "Parameters" and "EOC Parame-ters" must be selected. If the selected subunit should be configured for EOC purposes the CAS option must always be switched off.


Implementation FOX EOC Platform Release (R8)

Figure 4: "Unit Configuration Parameters" UCST mask

The EOC parameters are set in the "EOC Parameters" UCST mask shown in Figure 5. In this example, "Enabled" is set under "EOC Functions" and "Master (PC)" is set under "Interface". This means that an O & M system is connected to this interface.

The time taken to establish an EOC, is determined by the number of cas-caded SIFOX units. Depending on the size of the network, "Small", "Me-dium" or "Large" has to be set under "Network Size".

Only the EOC network has to be considered under "Network Size", which means that:

For each FOX the number of cascaded SIFOX units between the FOX and the O & M system will be determined (including its own SIFOX). The highest number serves to determine the network size, in accordance with the follow-ing table:

Number of cascaded SIFOX

units: Network size: EOC set-up time:

1 - 10 small 200 ms

11 - 50 medium 800 ms

50 - 254 large 2800 ms



Figure 5: "EOC Parameters" UCST mask

As with data transmission, in the EOC application channel-specific parame-ters have to be set in the UCST mask. The "Parameters" UCST mask is shown in Figure 6. For the EOC, set "X [From DTE]" under "Transmit clock source" and "Enabled" under "Use of control signals".

Figure 6: "Parameters" UCST mask

Configuration of the NE General

The EOC provides a point to multi-point operation with multiple routing espe-cially for meshed FOX-U/M and FOX-U/E networks.

Only in exceptional circumstances should the EOC be used in FOX515 net-works, because the data rate limitation of the EOC to 9600 kbit/s can cause a long response time during SW downloads.

Remote NEs in a FOX network can be accessed by the UCST using a SIFOX channel as an Embedded Operation Channel (EOC) in a dedicated timeslot of a 2 Mbit/s signal.



In this mode of operation, a point to multi-point master/slave polling opera-tion is used. The UCST operates as a master DTE, and the control units (CENCA, COBU<X>) in the network operate as slave DTEs

The UCST is connected (via a Modem when necessary) to a SIFOX channel of one of the FOX NEs in the FOX network. A second SIFOX channel (with the same timeslot) is connected to the control unit. Each FOX along the net-work is connected to a SIFOX channel using this common timeslot (EOC).

The UCST broadcasts data that is received by all the control units (polling). The control units recognize their individual FOX System Address as defined by the F-Interface Address. Using the C control line the FOX can individually access the common timeslot (EOC) to send data to the UCST.

Up to 8 timeslots (connection points) per subunit can be defined to allow multiple routing. Each timeslot means a separate routing direction.

To configure the NE for the EOC setup take into account some design rules described in the following paragraphs. The EOC communication follows a "Master-Slave"-protocol which is valid for all NEs participating in the EOC link. For one EOC only one NE is to be configured as "Master". For this sin-gle EOC the remaining NEs can be considered as "Slaves" This convention plays an important role for the definition of the network connections to feed the EOC into a dedicated channel of a transmission link to the next network element.

Internal network connections for the EOC setup

An NE, to which the O&M system (UCST, FOXMAN-UN) is connected is established as a gateway for the EOC to the network. The following EOC setup is given for an EOC gateway, but the basic rules how to set up the connections for the EOC are valid for each NE connected to an EOC link. The internal links of the EOC and its directions of the gateway are shown in Fig. 7.

Figure 7: Communication links of the EOC inside a NE (gateway)

The subunit used for the connection to the PC (subunit 2) must be config-ured as "Master" in the UCST mask "EOC Parameters" as described in sub-clause Subunit 1 represents the connections to the network and to the con-



trol unit (COBU<X>, CENCA) and must be configured as the "Slave". To build up all the necessary communication links the following network con-nections must be established:

1. SIFOX Traffic-1 (to "Master") SIFOX Traffic-2 (to "Slave")

2. SIFOX Traffic-1.(to "Slave") MEGIF Traffic-1.

3. SIFOX Traffic-1.(to "Slave") MEGIF Traffic-2.

Network connection 1 builds up the connection from the PC via subunit 2 of the SIFOX unit up to subunit 1 of the SIFOX unit. Network connection 2 and 3 feeds the EOC into the transmission network. How to configure this net-work connections is shown in Fig. 8.

Figure 8: Configuration of the network connections for an EOC

A configuration such as that shown in the Fig. 8 must be carried out for each NE connected to the EOC link. Further details regarding the setup of NEs representing intermediate NEs or terminals are described in the subclause "Generic example of an EOC network".

Configuration of the F-address of the NE

Each NE connected to the EOC management communication requires its own unique F-address. For the FOX-U/M /-U only the HDLC address must be specified, because this type of NE uses a different protocol stack of the communication from that used by the FOX515/512. The NE communication stack of the CENCA board used in the FOX-U/M /-U environment uses a proprietary derived HDLC protocol in the data link layer which provides the access to the transport layer and higher layers.

As the management communication protocol in the COBU<X> control unit of the FOX515 is based on TCP/IP, the data link layer of the protocol stack must also support PPP to provide the access to the network layer (IP, OSPF) and to the transport layer (TCP/UDP). This causes different configu-



ration procedures to prepare a FOX515 NE for the EOC management com-munication.

To define the F-address for a FOXFOX -U NE carry out the following steps:

1. Select slot 9 for the CENCA unit. This activates the menu "Unit Con-figuration"

2. Select "Parameters". This opens the "Unit Configuration Parameters" window.

3. Insert the required HDLC address value for the F-interface taken from the network plan in the field "Serial Interface" as shown in Fig. 9

Figure 9: Setting of the HDLC address for the F-interface (CENCA)

To prepare a COBU<X> unit for the EOC management communication the steps to be carried are slightly different:

1. Select slot 11 for the COBU<X> unit. This activates the "Unit Configu-ration" menu.

2. Select "Parameters". This opens the "Unit Configuration Parameters" window.

3. Open the submenu for the "Communication IF" and modify the pa-rameter settings in the field "Serial Interface".

4. Insert the required IP Host Address (Node Id) taken from the network plan.

5. Insert the required HDLC address value for the F-interface taken from the network plan.

6. Modify the default speed to the EOC data rate of 9600 kbit/s. 7. Insert a host name according to your network plan in the field "Host

Name".

All settings are shown in Fig. 10.



Figure 10: IP address settings for the COBU<X>

Configuration of the Man-agement Network Agent

A further important step is to initialize all the connected NEs in the manage-ment communication. For this configuration select the "Setup/Connect" op-tion in the "Management Communication" menu.

Assuming the gateway to the EOC network is covered by a FOX-U/M and FOX-U/E and the complete network does not contain an FOX515, the "Setup/Connect" option can be configured as follows:

1. Select the "Setup/Connect" option in the "Management Com-munication" menu

2. Activate "Add" in the "Network Management Parameters" win-dow

3. Insert the required parameters in the "Add Management Net-work Agent" field as shown in Fig. 11



Figure 11: Parameter setup in the "Add Management Network Agent" field for an FOX-U/M and FOX-U/E gateway

If only such NEs using HDLC communication protocol as the FOX -U/M -U are established in the network, the "Management Network Parameters" can be set as follows:

1. Name: Specify a name for the Management Network Agent

2. Type: Select "SIFOX" for a management communication via EOC

3. Supported NEs: If the management communication of all the NEs is based on HDLC protocol (valid for FOX-U/M /-U only) select the option "HDLC only"

4. Serial Port Identifies the serial port of the connect EM

5. Serial Speed This setting selects the data speed for the serial port. For an EOC the data speed is limited to 9600 kbit/s.

The settings in the fields "Host Name" and "Host Type" in the "Agent Host" window are mandatory and cannot be changed.

If NEs such as the FOX515 are connected to an EOC link then the Man-agement communication is based on the TCP/IP protocol. They require dif-ferent management network parameters.

If the gateway to the EOC network is covered by a FOX515/512 and the complete network contains further FOX515/512 NEs the "Setup/Connect" can be configured as shown in Fig. 12.



Figure 12: Parameter setup in the "Add Management Network Agent" field for an FOX515 gateway

The management communication of the FOX515/512 is based on the TCP/IP protocol. If you design a mixed network consisting of FOX515/512 and FOX -U/M -U NEs select the option "Any" in the field "Supported NE's" must be selected. IP-based management communication requires a Man-ager Id which identifies the connected EM for its IP address. The previous installation of the Windows Dial-up Networking Package provides the set-tings in the fields "Interface" and "Modem Device" automatically. The set-tings in the "Host Name" and "Host Type" fields in the "Agent Host" window are mandatory and cannot be changed.



In order to access all the NEs which are configured for the same EOC net-work, these NEs must be added in the list of "Managed NE's" in the "Net-work Communication Setup" main window. A mandatory prerequisite is the local EOC setup for each NE which should appear in the list. To add NEs in the list activate the "Add" button. For the examples shown in Fig. 13 and Fig. 14 it's assumed that the gateway is covered by a FOX515 NE and the "Man-agement Network Agent" supports any NE.

Addition of configured NE's to the EOC network

Figure 13: Addition of an FOX515 to an EOC management network

For this configuration, in which a FOX515/512 NE is used as a gateway for the EOC network carry out the following steps:

1. Select the FOX type which is used for this NE 2. Insert the IP address according to your network plan, if a FOX515/512

is chosen for this particular NE (in the example the default value 10.1.1.1 is used)

3. Type a name for the NE in the "Name" field 4. Insert a value for the "HDLC Address" (Address for the F-interface)

according to your network plan



Figure 14: Addition of an FOX-U to the EOC management network

The configuration steps are slightly different for a FOX-U:

1. Select the FOX type which is used for this NE 2. Type a name for the NE in the "Name" field 3 Insert a value for the "HDLC Address" (Address for the F-interface)

according to your network plan

The settings for the HDLC Router Parameters are only valid and must be set if the FOX-U is connected to a Q1-master interface of a FOX515/512. The Q1-master interface requires the management communication via ECC or via LAN and is described in chapter 4.

All NEs of the same EOC management network can be integrated in the manner described above. The appearance of added NEs is shown in Fig. 15.



Figure 15: NE's added to the EOC management communication net-work

Connecting the EM(S) to the NE General

As the EOC management communication is preferred for a FOX-U/M and FOX-U/E network the connection possibilities should be considered exclu-sively for a FOX-U/M and FOX-U/E environment under this subclause. Ex-ceptionally you may have to manage an FOX515 via the EOC due to the re-quired bandwidth for SW download and extended configuration files.

The first connection for the EM NE link must be physically established be-tween the PC (UCST) or WS (FOXMAN-UN) and the corresponding subunit of the SIFOX configured as the "Master". To reach the control unit of the NE a second connection must be physically established between the CENCA and the corresponding subunit of the SIFOX configured as the "Slave".

The EOC function is integrated in the SIFOX software as an additional func-tion. Each SIFOX can be used as an interface for data transmission with four X.24/V.11 interfaces, or for the implementation of up to four EOC interfaces. If the EOC function is activated at one of the interfaces, the three remaining interfaces operate as normal X.24/V.11 interfaces. The interface with the EOC function is generally connected to the F interface of the CENCA.



The CENCA F interface corresponds to the CCITT V.28 recommendation which has only one signaling line per logic signal. The SIFOX interface, how-ever, has two signaling lines per logic signal in accordance with V.11. Never-theless it is possible to connect the two interfaces directly together without a converter, as long as the cable is only a few meters in length.

Cable Connection control unit CENCA to SIFOX

Figure 16: Wiring schematic connection CENCA SIFOX

CENCA interface SIFOX interface unit 1

TxD

RTS

RxD

CTS

DTR

DSR

GND

TATBGNDCABA

RA

IA

SASBXAXB

CB

(25 pin F connector) (Cable connector)

Pin: Pin:

2

1

4

3

5

20

6

7

8/a7/a1/a6/a

2/a

8/c

6/c

4/c3/c4/a3/a

5/a

The following cabling options are available for implementing the EOC appli-cation:

One EOC per SIFOX (cable: SIFOX-1 EOC) The first interface is connected to the CENCA of the same FOX using a short cable. The three remaining X.24/V.11 interfaces are available for data transmission. This is the most widely used version of cabling.

Two EOC per SIFOX (cable: SIFOX-2 EOC) The first two interfaces are connected using short cables, one to the CENCA of the same FOX and the other to the CENCA of the second FOX in the same rack. The two remaining X.24/V.11 interfaces are available for data transmission.

Three or four EOC per SIFOX (cables: SIFOX-3 EOC+1 PC, SIFOX-4 EOC)

Three or four CENCAs are connected to one SIFOX. A prerequisite is that all FOXs are located within the same rack.

Cables for connecting O & M systems to SIFOX

All SIFOX cables are equipped with the relevant data connectors on one side. Very close to each data connector its cable to the SIFOX is marked with the number of the relevant subunit of the SIFOX.

For connecting an O & M system to the SIFOX the following two cabling op-tions are available:



SIFOX-1 EOC + 1 PC+2 X.24: The first interface (SIFOX subunit 1) is intended for the CENCA and the sec-ond (SIFOX subunit 2) for the O & M system. The two remaining X.24/V.11 interfaces (SIFOX subunits 3 and 4)are available for data transmission..

• SIFOX-3 EOC + 1 PC: The first three interfaces are intended for CENCA connections (SIFOX sub-unit 1 – 3) and the fourth (SIFOX subunit 4) is for connecting the O & M sys-tem.

Connection Interface Converter SIFOX The SIFOX-EOC (5 m) interface cable for connecting the O&M systems to the SIFOX interface has the pin allocations as shown in Fig. 17.

Figure 17: Wiring diagram Connection Interface Converter SIFOX

Interfacet

Second SIFOX interface(SIFOX side, 25 pin, D-Sub connector female)

Pi Pi

21431541651717201896

16a15a16c15c14a13a14c13c9a10a11a11c12a12c

TRCI

JumperJumper

ScreenGround

Jumper

Jumper

T T

O & M system SIFOX Depending on the application the O & M system can be activated on short, medium or large distances to the gateway - FOX to which it is connected. For each distance range you can chose the appropriate connection solution. For all solutions: besides the connector boxes and interface converter that are indicated in the diagrams here, no null modems are used.

Connection on short distance Up to a distance of a few meters (6...10 m) between the SIFOX and the O &

M system you can use a passive short distance interface converter RS232 / RS422.

The proper function of this solution depends on the V.24 interface of the PC and cannot be guaranteed. Therefore a precise distance up to which it works cannot be specified.

A principle wiring diagram of the connection is shown in Fig. 18.



Figure 18: Connection of the O & M system SIFOX (passive con-verter)

The wiring of this passive short distance converter RS232/RS422 and its pin connections are shown in Fig. 19

Figure 19: Wiring schematic of the passive EOC converter

7

6

5

4

3

2

1

20

7

6

5

4

3

2

1

16

15

14

17

RS232 Signal from PC RS422 Signal from SIFOX

female maleD-Sub-connector25 pins

D-Sub-connector25 pins



For distances up to 1 km you need an active interface converter RS232 / RS 422. These converters are commercially available and must be powered by an external mains power supply. It is used instead of the short range inter-face converter. The maximum distance between the converter and SIFOX is 1 km. The maximum distance between the converter and the O & M system is 15 m. A principle wiring schematic of this connection is shown in Fig. 20.

Connection on medium dis-tance

Figure 20: Connection of the O & M system SIFOX (active con-verter)

Connection on large distance If the distance between the O & M system and SIFOX is more than 1 km, modems must be used for the transmission. For small FOX networks the following solutions are suitable:

Solution a: If modem 2 is f more than a few meters from the SIFOX an interface con-verter RS232 / RS422 must be taken together with the special box con-nector for long distances. A principle wiring schematic is shown in Fig. 21.




Figure 21: Connection diagram of the Modem-SIFOX Converter long distance

Modem1 Modem2

Serial cable

Telephone lines

SIFOX

CENCA

POSUP

Slot9 Slot19

SIFOX EOC cable1

RS232/422converter

SIFOX EOC cable 5 m

max. 15 m

Modem-SIFOX Converter long-distance(a special passive converter box,the w iring is show n in the follow ing f ig.)

Serial cablemax. 15 m

The long-distance Modem-SIFOX Converter is a small connector box and is required for the connections by modem with the Q and the EOC interfaces. It must be connected between the modem and the RS485B or RS422 con-verter. The wiring diagram is shown in Fig. 22.

Figure 22: Wiring schematic of the Modem-SIFOX Converter long dis-tance

8

7

6

5

4

3

2

1

20

8

7

6

5

4

3

2

1

Modem RS485B or RS422

female male

Solution b: if modem 2 is within a distance of a few meters (6...10 m) to the SIFOX it is sufficient to use a special box connector for short distances.


1KHW002011 page 38 of 58

The proper function of the solution depends on the V.24 interface of the modem and cannot be guaranteed. Therefore a precise dis-tance up to which it works cannot be specified.

Figure 23: Connection diagram of the Modem-SIFOX Converter short distance

Modem1

Serial cable

Modem2

Serial cable

Telephone lines

SIFOX

CENCA

POSUP

Slot9 Slot19

SIFOX EOC cable1

SIFOX EOC cable 5 m

1...5 m

max. 15 m Modem-SIFOX Converter short -distance(special passive box, for w iring see follow ing Fig.)

Figure 24: Wiring schematic of the Modem-SIFOX Converter short dis-tance

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

Modem2 SIFOX cable

female male

(only for short distance)

14

15

20 16

ABB

FOX EOC Platform Release (R8) Examples of EOC configuration

7 Examples of EOC configuration

Generic example Itshows a FOX network, for which the EOC management network configura-tion follows.

Figure 25: Example of an EOC network


Examples of EOC configuration FOX EOC Platform Release (R8)

The first step to build up the EOC management communication network to the NEs 1-6 is the set-up of the EM as described in subclause «Configura-tion of the Management Network Agent». The following steps must be car-ried out:

EOC set-up for the EM (UCST/FOXMAN-UN)

1. Create the UCST mask for a FOX-U 2. Choose "Management Network" 3. Activate the "Add" button in "Network management parameters" 4. If no FOX515/512 NEs are included in the EOC management com-

munication, the settings are as shown in Fig. 26.

Figure 26: Settings of the "Management Network Parameters"

If only FOX-U/M and FOX-U/E and DSL systems are connected to the EOC network the option "Supported NE's" should be "HDLC only"

5 Insert all relevant NEs for this particular EOC in the list of "Managed NE's" by activating the "Add" button

6 Insert all relevant NE parameters for NE1 as shown in Fig 27



Figure 27: NE parameters for NE1

7. Repeat the operation as described above for the NEs 2-6

After the insertion of all Nes, the list of the "Managed NEs" looks as shown in Fig. 28.

Figure 28: List of all managed NE's in the EOC network



The FOX-U which is designated as NE1 represents the gateway for the EOC management communication network. This NE is connected to EM (UCST, FOXMAN-UN) directly. The optical link of 8 Mbit/s to NE2 consists of an optical transmission unit TUNOL in NE1 and NE2. One of the 4x2 Mbit/s bundles carries the EOC in timeslot 31. For this configuration the following steps must be carried out:

EOC set-up for NE1 in loca-tion1

1. Set up the EOC parameters for Subunit 1 of the SIFOX unit, which builds up the link to the CENCA control unit and further links into the network. This subunit must be configured as the "Slave" and the "CAS" option must be switched off. The required settings are shown in Fig. 29 and Fig. 30.

Figure 29: Declaration of subunit 1 and 2 for EOC operation

Figure 30: Set-up of the EOC parameters for SIFOX, subunit 1



2. Set up the EOC parameters of Subunit 2 of the SIFOX unit which builds up the link to the EM. This subunit must be configured as the "Master" and the "CAS" option must be switched off. The required set-tings are shown in Fig. 31.


3. Set-up of the common parameters for subunit 1 and 2 as shown in Fig. 32.

Figure 32: Set-up of the common parameters for subunit 1and 2

4. Set up the HDLC address (for the F-interface) in the control unit (CENCA) as shown in Fig. 33.



Figure 33: Set-up of the F-interface in control unit CENCA

5. Set up the cross connections for the EOC link

The necessary cross connections for the EOC link must be set up according to the convention as described in subclause «Internal network connections for the EOC setup». The subunits of the SIFOX, which are configured for EOC purposes offer connection points in the following directions:

Direction to Master.

The "Direction to master" means the link towards the PC for the EOC.

Direction to Slave.

The "Direction to Slave" means the link into the network to further NEs for the EOC.

Following the convention as described above the cross connections must be designed as shown in Fig. 34.

Each subunit of the SIFOX configured for EOC offers up to 8 con-nection points which can be configured as EOC Ms or EOC SL individually.



Figure 34: Cross connections for the EOC in NE1



The FOX-U which is designated as NE2 represents an intermediate node for the EOC management communication network. NE2 receives the EOC lo-cated in timeslot 31 in one of the 4 x 2 Mbit/s bundles and forwards it to NE3 in timeslot 31 of the 2 Mbit/s link. The steps to prepare this NE for the EOC are similar to the configuration for NE1:

EOC set-up for NE2 in location 2

1. Set up the EOC parameters for Subunit 1 of the SIFOX unit, which builds up the link to the CENCA control unit and further links into the network. This subunit must be configured as the "Slave" and the "CAS" option must be switched off. The EOC must be routed back to the PC and forward to NE3, therefore it's sufficient to configure one subunit for EOC purposes. The required settings are shown in Fig. 35 and Fig. 36.

Figure 35: Declaration of subunit 1 for EOC operation




2. Set up the common parameters for subunit 1 as shown in Fig. 37.

Figure 37: Set-up of the common parameters for subunit 1

3. Set up the HDLC address (for the F-interface) in the control unit (CENCA) as shown in Fig. 38.

Figure 38: Set-up of the F-interface in control unit CENCA in NE2


The subunit 1 of the SIFOX, which is configured for EOC purposes offers connection points in the following directions:

Direction to Master. The "Direction to master" means the link to NE1 and to the PC for the EOC via 8 Mbit/s optical transmission.

Direction to Slave. The "Direction to Slave" means the link into the network to further NEs for the EOC via 2 Mbit/s electrical transmission.



Following the convention as described above, design the cross connections as shown in Fig. 39.




The FOX-U which is designated as NE3 represents the terminal node for the EOC management communication network. NE3 receives the EOC located in timeslot 31 of the 2 Mbit/s link. NE3 – NE6 are located in same rack in location 3. Therefore only one SIFOX is necessary to manage NE3 – NE6.To prepare this NE for the EOC the following steps must be carried out:

EOC set-up for NE3 in location 3

1. Set up the EOC parameters for subunit 1-4 of the SIFOX unit, which build up the links to the control units in NE3 - NE6. All 4 subunits must be configured as "Slave" and the "CAS" option must be switched off. The required settings are shown in Fig. 40 and Fig. 41.

Figure 40: Declaration of the subunits 1-4 for EOC operation

Figure 41: Set-up of the EOC parameters for SIFOX, subunits 1-4

2. Set up the common parameters for subunits 1-4 as shown in Fig. 42.



Figure 42: Set-up of the common parameters for subunits 1-4

3. Set up the HDLC address (for the F-interface) in the control unit (CENCA) as shown in Fig. 43



The subunits 1-4 of the SIFOX, which are configured for EOC purposes of-fers connection points in the following directions:

Direction to Master. The "Direction to master" means the link to NE2 and to the PC for the EOC via 2 Mbit/s optical transmission. In each subunit one connection point must be routed in the "Direction to Master" (subunit 1-4)

Direction to Slave. The "Direction to Slave" means the link to the SIFOX subunits 2-4, to which the local control units of the NEs 4-6 are connected. That means, that 3 connection points of subunit 1 must be configured in the "Direction to Slave" in order to establish the connections to the subunits 2-4 of the SIFOX.



Following the convention as described above the cross connections must be designed as shown in Fig. 44.




To connect the NEs 4 – 6 to the EOC network only the physical connection from their control units to the SIFOX in NE3 must be established via the SIFOX 4 EOC cable as follows:

EOC set-up for NE4 - NE6 in location 3

1. SIFOX NE3 subunit 2 CENCA NE4

2. SIFOX NE3 subunit 3 CENCA NE5

3. SIFOX NE3 subunit 4 SUCO NE6

Furthermore the set-up of the HDLC addresses (for the F-interfaces) in the control units (CENCA, SUCO) for NE4 – NE6 must be carried out as shown in the Figures 45 – 47.





Figure 47: Set-up of the F-interface in control unit SUCO in NE6

Extending EOC via TUNOS / TUNOL V.11 OHC Introduction

For some applications you need to connect a peripheral FOX in order to access remote subscribers via an optical link to an existing FOX network. This peripheral node can be considered as a remote terminal node to which only tributaries (subscriber interfaces) are connected. In order to save band-width and costs for a further SIFOX in that particular FOX NE, the V.11 OHC of the optical transmission units TUNOS and TUNOL can be used. Such an application is shown in Fig.48.

Figure 48: FOX network with peripheral NE's



Each of the FOX NEs in a FOX network configured for multi-routing of the EOC must be equipped with a SIFOX channel. Each EOC route uses a 64 kb/s capacity from the bandwidth normally reserved for user data.

The FOX NEs at the peripheral of the FOX network that terminate the EOC and thus do not provide multi-routing of the EOC (ie. last links) can alterna-tively use the V.11 OHC channel of the TUNOS / TUNOL for carrying the EOC with the following benefits:

The SIFOX unit does not need to be installed in the peripheral FOX

V.11 OHC channel is transmitted in the 8 Mb/s optical signal without using any of the user data bandwidth.

Figure 49: Cables required for installation at the NEs

CENCA

SIFOX SbUSIFOX SbU

Modified SIFOX Cable

CENCA

Cable 1

msm

Cable 2

Two types of cables have to be made as shown in the above figure in order to use the V.11 OHC to carry the EOC.

Cable 1 Cable 1 is a modified SIFOX cable used in FOX NEs communicating with peripheral FOX NEs to connect the SIFOX subunit to the TUNOS / TUNOL V.11 OHC.

Cable 2 Cable 2 is a null modem cable used in peripheral FOX NEs to connect the TUNOS / TUNOL V.11 OHC with the CENCA F-interface.



Design and pin allocation of the cables

Cable 1 for TUNOS Modify one of the X.24 sections of a SIFOX cable as follows: (figure below shows modification to X.24 connection to SbU3)

Figure 50: Pin allocation of the cable SIFOX V.11 interface TUNOS

TUNOS

9

10

11

12

15

1

2

3

4

5

8

SIFOX

24

23

22

21

20

19

18

17

T

R r

w

T bl

bl

w

r

og

og

(w)

r

bn

bn

R

C

I

C

I

G bn

B

Screen

B

T

T

C

C

R

R

I

I

G

32 pin female

15 pin male15 pin female

Cable 1a b c

(a)

(b)

(a)

(b)

(a)

(b)

(a)

(b)

(a)

(a)

(b)

(b)

(a)

(a)

(b)

(b)

(a)

Cable 1 for TUNOL Modify one of the X.24 sections of a SIFOX cable as follows: (figure below shows modification to X.24 connection to SbU3)

Figure 51: Pin allocation of the cable SIFOX V.11 interface TUNOL

(a)

TUNOL

3

4

6

7

8

SIFOX

24

23

22

21

20

19

18

17

32 pin female

15 pin male15 pinfemale

Cable 1a b c

a b c

T

R r

w

T bl

bl

w

r

og

og

(w)

r

bn

bn

R

C

I

C

I

G bn

B

Screen

B

I

I

R

R

C

C

T

T

G

(b)

(a)

(b)

(a)

(b)

(a)

(b)

(a)

(a)

(b)

(b)

(a)

(a)

(b)

(b)

(a)

(b)



1. Cut off X.24 15 pin female sub-D connector Steps to prepare the cable 1(SIFOX V.11 OHC) 2. Reconnect wires to new TUNOS or TUNOL connector as shown in the

figure. Because the V.11 OHC and the SIFOX are both configured as DCE, the T and R lines and the C and I lines must be crossed.

3. Add two wire wraps to the 32 pin SIFOX connector (19a-19c, and 20a-20c for SbU3) as shown in the Fig. 51.

Design of cable 2 for TUNOS The Cable 2 should be made as shown in Fig. 52.

Figure 52: Pin allocation and wiring schematic for cable 2 for TUNOS.

TUNOS

1

3

5

CENCA

TD

C

RD

I

GND

15 pinmale

15 pinfemale

Cable 2

2

4

8

9

12

15

1

3

5

2

4

25

6

7

DSR

11

10

20

TD

RD

RTS

CTS

15 pinmale

15 pinfemale

DTR

GND

Design of cable 2 for TUNOL The Cable 2 should be made as shown in Fig 53.

Figure 53: Pin allocation and wiring schematic for cable 2 for TUNOL.

TUNOL CENCA

I

RD

Cable 2

3

6

5

4

a b c

2

8

7 TD

GND

1

3

5

2

4

25

6

7

DSR

20

TD

RD

RTS

CTS

15 pinmale

15 pinfemale

DTR

GND

C



page 57 of 58 1KHW002011

The SIFOX SbU connecting to the TUNOS / TUNOL V.11 OHC is configured for EOC operation as follows:

Configuration of the SIFOX

CAS : “OFF“

Parameters Transmit clock source : “X (From DTE)“

Parameters Use of control signals : “Enabled“

EOC Parameters Function : “Enabled“

EOC Parameters Interface : “Slave (CENCA)“

Connection points : “Direction to Master“

Configuration of TUNOS / TUNOL

The TUNOS / TUNOL V.11 OHC used for the EOC on all FOX NEs are con-figured as follows:

Mode: “Service Channel“ and “EOC“ Once this is made, the following parameters are automatically set by UCST:

Service Channel Partyline : “OFF“ Service Channel Monitored : “ON“ T Monitored : “OFF“ T=1 (Timeout Partyline) : “OFF“ Bitrate : “0 ... 9.6 kbit/s“ R Default : “Free running“ Clock Source : “TUNOS / TUNOL local“

Special Note: The UCST does not allow SIFOX channels that are configured for EOC op-eration to be changed via the EOC. This prevents any changes that would inadvertently unconfigure channels used by the EOC, in effect interrupting the EOC circuit.

When extending the EOC via the TUNOS / TUNOL V.11 OHC, the SIFOX is not used, and this self protecting feature for the EOC is not available.

This means that it is possible to reconfigure the TUNOS / TUNOL V.11 OHC via the EOC to unconfigure the EOC extension, in effect preventing any fur-ther EOC access to that TUNOS / TUNOL.

ABB

For more information please contact: ABB Switzerland Ltd Power Systems Utility Communications Bruggerstrasse 72 5400 Baden Switzerland Phone: +41 58 589 37 35 or: +41 844 845 845 (Call Center) Fax: +41 58 585 16 82 E-Mail: [email protected] www.abb.com/utilitycommunications

mailto:[email protected]

Documents

Abb Fox Eoc r8 Rb 1khw002011