Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
FOX515
EOC (Embedded Operation Channel)
User Manual
Release History:
Release 7B:
Release 8B:
Release 8C:
February 2007
December 2008
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
6
6
1 Introduction
Overview
Definition of terms and documentation
11
13
4 Communication principles
15
17
Establishment of connection
Addressing the requested subscriber
Reaction of the addressed subscriber
Through-connection Reply channel (SIFOX)
Through-connection Reply channel (O & M system)
Data exchange
Clearing a connection
6 Implementation
17
19
19
19
19
19
19
21
Summary
Configuration of SIFOX
Configuration of the NE
Connecting the EM(S) to the NE
ABB
9
9
page 3 of 58
21
21
23
32
39
39
53
1KHW002011
Figures
Figure 1: Management communication with EOC
Figure 2: Line network with EOC in a FOX -U environment
Figure 3: meshed EOC network
Figure 4: "Unit Configuration Parameters" UCST mask
Figure 5: "EOC Parameters" UCST mask
Figure 6: "Parameters" UCST mask
Figure 7: Communication links of the EOC inside a NE (gateway)
Figure 8: Configuration of the network connections for an EOC
Figure 9: Setting of the HDLC address for the F-interface (CENCA)
Figure 10: IP address settings for the COBU<X>
Figure 11: Parameter setup in the "Add Management Network Agent"
field for an FOX-U/M and FOX-U/E gateway
Figure 12: Parameter setup in the "Add Management Network Agent"
field for an FOX515 gateway
Figure 13: Addition of an FOX515 to an EOC management network
Figure 14: Addition of an FOX-U to the EOC management network
Figure 15: NE's added to the EOC management communication network
Figure 16: Wiring schematic connection CENCA SIFOX
Figure 17: Wiring diagram Connection Interface Converter SIFOX
Figure 18: Connection of the O & M system SIFOX (passive converter)
Figure 19: Wiring schematic of the passive EOC converter
Figure 20: Connection of the O & M system SIFOX (active converter)
Figure 21: Connection diagram of the Modem-SIFOX Converter long distance
Figure 22: Wiring schematic of the Modem-SIFOX Converter long distance
Figure 23: Connection diagram of the Modem-SIFOX Converter short distance
Figure 24: Wiring schematic of the Modem-SIFOX Converter short distance
Figure 25: Example of an EOC network
Figure 26: Settings of the "Management Network Parameters"
Figure 27: NE parameters for NE1
Figure 28: List of all managed NE's in the EOC network
Figure 29: Declaration of subunit 1 and 2 for EOC operation
Figure 30: Set-up of the EOC parameters for SIFOX, subunit 1
Figure 31: Set-up of the EOC parameters for SIFOX, subunit 2
Figure 32: Set-up of the common parameters for subunit 1and 2
Figure 33: Set-up of the F-interface in control unit CENCA
Figure 34: Cross connections for the EOC in NE1
Figure 35: Declaration of subunit 1 for EOC operation
Figure 36: Set-up of the EOC parameters for SIFOX, subunit 1
Figure 37: Set-up of the common parameters for subunit 1
Figure 38: Set-up of the F-interface in control unit CENCA in NE2
Figure 39: Cross connections for the EOC in NE2
Figure 40: Declaration of the subunits 1-4 for EOC operation
Figure 41: Set-up of the EOC parameters for SIFOX, subunits 1-4
Figure 42: Set-up of the common parameters for subunits 1-4
Figure 43: Set-up of the F-interface in control unit CENCA in NE3
Figure 44: Cross connections for the EOC in NE3
1KHW002011
page 4 of 58
11
14
18
22
23
23
24
25
26
27
28
29
30
31
32
33
34
35
35
36
37
37
38
38
39
40
41
41
42
42
43
43
44
45
46
46
47
47
48
49
49
50
50
51
ABB
ABB
page 5 of 58
52
52
53
53
54
55
55
56
56
1KHW002011
Referenced documents
1KHW002011
1KHW002057
1KHW002058
1KHW002013
1KHW002059
1KHW002060
1KHW002009
1KHW002061
page 6 of 58
ABB
Technical support
ABB Technical Support is available as follows:
ABB
Phone:
+41 58 589 37 35
or:
Fax:
+41 58 585 16 82
E-Mail:
utility.communication@ch.abb.com
URL:
www.abb.com/utilitycommunications
page 7 of 58
1KHW002011
1KHW002011
page 8 of 58
ABB
1
Overview
Introduction
Introduction
The management communication via an EOC (Embedded Operation Channel) 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 transmission 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 equipment since it is also fully implemented for the FOX515/512 and remains
compatible, provided you have UCST/FOXMAN-UN R4E (or higher releases).
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 multiservice access systems.
The download of embedded SW to the FOX515/512 and extended management possibilities require more transmission performance than the
EOC is able to provide.
Thus, the implementation of the ECC is highly recommended for all management 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.
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
ABB
page 9 of 58
1KHW002011
Introduction
Units
Both control units have their own technical description. For the
The COBU<X>, COBUL and COBUQ are not compatible with the FOXU/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 FOXU/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 dialogues.
For details of the UCST, refer to UCST/System Operation Basics User
Guide.
1KHW002011
page 10 of 58
ABB
ABB
page 11 of 58
1KHW002011
The QX-interface of the FOX515/512 can be used in parallel to the EOC management 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) independent 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.
1KHW002011
page 12 of 58
ABB
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 example 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 connected 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.
ABB
page 13 of 58
1KHW002011
1KHW002011
page 14 of 58
ABB
Communication principles
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 establishes 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 recognizes 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.
ABB
page 15 of 58
1KHW002011
Communication principles
1KHW002011
page 16 of 58
ABB
Establishment of connection
ABB
page 17 of 58
1KHW002011
From Figure 3 it is evident that all the channels for both connecting directions, 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 Figure 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
1KHW002011
page 18 of 58
ABB
with the O & M system one after another. This step-by-step connecting procedure 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, activates the control signal CTS.
After receiving the CTS signal the O & M system sends a Connect Command with the address of the desired 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 After receiving the RTS control signal, the SIFOX sends the bit pattern SOM
on all the Reply channels in the Master direction until a throughchannel (SIFOX)
connection of the Reply channel to the O & M system has been established. You can determine the duration of this time span which depends on
the number of cascaded SIFOX units in the network.
Through-connection Reply 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
channel (O & M system)
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 Disconnect 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 .
ABB
page 19 of 58
1KHW002011
1KHW002011
page 20 of 58
ABB
6
Summary
Implementation
Implementation
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 limited 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
ABB
page 21 of 58
1KHW002011
Implementation
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 cascaded SIFOX units. Depending on the size of the network, "Small", "Medium" 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 following table:
1KHW002011
Network size:
1 - 10
small
200 ms
11 - 50
medium
800 ms
50 - 254
large
2800 ms
page 22 of 58
ABB
Implementation
As with data transmission, in the EOC application channel-specific parameters 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".
Configuration of the NE
General
The EOC provides a point to multi-point operation with multiple routing especially for meshed FOX-U/M and FOX-U/E networks.
Only in exceptional circumstances should the EOC be used in FOX515 networks, 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.
ABB
page 23 of 58
1KHW002011
Implementation
In this mode of operation, a point to multi-point master/slave polling operation 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 network 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 single 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
The subunit used for the connection to the PC (subunit 2) must be configured as "Master" in the UCST mask "EOC Parameters" as described in subclause Subunit 1 represents the connections to the network and to the con-
1KHW002011
page 24 of 58
ABB
Implementation
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 Faddress of the NE
ABB
page 25 of 58
1KHW002011
Implementation
Select slot 9 for the CENCA unit. This activates the menu "Unit Configuration"
Select "Parameters". This opens the "Unit Configuration Parameters"
window.
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
Select slot 11 for the COBU<X> unit. This activates the "Unit Configuration" menu.
Select "Parameters". This opens the "Unit Configuration Parameters"
window.
Open the submenu for the "Communication IF" and modify the parameter settings in the field "Serial Interface".
Insert the required IP Host Address (Node Id) taken from the network
plan.
Insert the required HDLC address value for the F-interface taken from
the network plan.
Modify the default speed to the EOC data rate of 9600 kbit/s.
Insert a host name according to your network plan in the field "Host
Name".
1KHW002011
page 26 of 58
ABB
Implementation
Figure 10:
A further important step is to initialize all the connected NEs in the management communication. For this configuration select the "Setup/Connect" option 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.
2.
3.
ABB
page 27 of 58
1KHW002011
Implementation
Figure 11:
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 Management communication is based on the TCP/IP protocol. They require different 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.
1KHW002011
page 28 of 58
ABB
Figure 12:
Implementation
ABB
page 29 of 58
1KHW002011
Implementation
Addition of configured NE's to In order to access all the NEs which are configured for the same EOC network, these NEs must be added in the list of "Managed NE's" in the "Netthe EOC network
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 "Management Network Agent" supports any NE.
Figure 13:
3.
4.
1KHW002011
page 30 of 58
ABB
Implementation
Figure 14:
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.
ABB
page 31 of 58
1KHW002011
Implementation
Figure 15:
1KHW002011
page 32 of 58
ABB
Implementation
Cable Connection control unit The CENCA F interface corresponds to the CCITT V.28 recommendation
which has only one signaling line per logic signal. The SIFOX interface, howCENCA to SIFOX
ever, has two signaling lines per logic signal in accordance with V.11. Nevertheless 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.
Figure 16:
Pin:
TxD
8/ a
7/ a
1/ a
6/ a
RTS
TA
TB
GND
CA
BA
RxD
RA
8/ c
CTS
IA
6/ c
20
DTR
DSR
SA
SB
XA
XB
4/ c
3/ c
4/ a
3/ a
GND
CB
5/ a
2
1
2/ a
The following cabling options are available for implementing the EOC application:
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 options are available:
ABB
page 33 of 58
1KHW002011
Implementation
Jumper
Jumper
T
Second SIFOX int erf ace
Pi
Pi
2
14
3
15
4
16
5
17
1
7
20
18
9
6
16a
15a
16c
15c
14a
13a
14c
13c
9a
10a
11a
11c
12a
12c
T
R
C
I
Screen
Ground
Jumper
Jumper
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.
1KHW002011
page 34 of 58
ABB
Implementation
Figure 18:
The wiring of this passive short distance converter RS232/RS422 and its pin
connections are shown in Fig. 19
Figure 19:
female
D-Sub-connector
25 pins
20
14
male
D-Sub-connector
25 pins
15
16
17
ABB
page 35 of 58
1KHW002011
Implementation
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 converter RS232 / RS422 must be taken together with the special box connector for long distances. A principle wiring schematic is shown in Fig.
21.
1KHW002011
page 36 of 58
ABB
Implementation
Figure 21:
S
I
F
O
X
max. 15 m
Serial cable
C
E
N
C
A
P
O
S
U
P
Slot 9
Slot 19
M odem2
RS232/ 422
convert er
Serial cable
max. 15 m
Telephone lines
female
RS485B or RS422
male
20
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.
ABB
page 37 of 58
1KHW002011
Implementation
S
I
F
O
X
1...5 m
Serial cable
M odem1
C
E
N
C
A
P
O
S
U
P
Slot 9
Slot 19
M odem2
SIFOX EOC cable 5 m
Serial cable
max. 15 m
Telephone lines
Figure 24:
female
SIFOX cable
male
14
15
20
16
(only for short distance)
1KHW002011
page 38 of 58
ABB
7
Generic example
ABB
page 39 of 58
1KHW002011
Figure 26:
1KHW002011
Insert all relevant NEs for this particular EOC in the list of "Managed
NE's" by activating the "Add" button
Insert all relevant NE parameters for NE1 as shown in Fig 27
page 40 of 58
ABB
Figure 27:
7.
After the insertion of all Nes, the list of the "Managed NEs" looks as shown
in Fig. 28.
Figure 28:
ABB
page 41 of 58
1KHW002011
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:
1.
1KHW002011
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:
Figure 30:
page 42 of 58
ABB
2.
Figure 31:
3.
Figure 32:
4.
ABB
Set up the HDLC address (for the F-interface) in the control unit
(CENCA) as shown in Fig. 33.
page 43 of 58
1KHW002011
Figure 33:
5.
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 connection points which can be configured as EOC Ms or EOC
SL individually.
1KHW002011
page 44 of 58
ABB
Figure 34:
ABB
page 45 of 58
1KHW002011
1KHW002011
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:
Figure 36:
page 46 of 58
ABB
2.
Figure 37:
3.
Set up the HDLC address (for the F-interface) in the control unit
(CENCA) as shown in Fig. 38.
Figure 38:
4.
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.
ABB
page 47 of 58
1KHW002011
1KHW002011
page 48 of 58
ABB
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:
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:
Figure 41:
2.
ABB
page 49 of 58
1KHW002011
Figure 42:
3.
Set up the HDLC address (for the F-interface) in the control unit
(CENCA) as shown in Fig. 43
Figure 43:
4.
The subunits 1-4 of the SIFOX, which are configured for EOC purposes offers 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.
1KHW002011
page 50 of 58
ABB
ABB
page 51 of 58
1KHW002011
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:
1.
2.
3.
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.
1KHW002011
Figure 45:
Figure 46:
page 52 of 58
ABB
Figure 47:
ABB
page 53 of 58
1KHW002011
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 alternatively 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:
Cable 1
Cable 2
CENCA
SIFOX SbU
SIFOX SbU
CENCA
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.
1KHW002011
page 54 of 58
ABB
Figure 50:
Cable 1
TUNOS
c
SIFOX
1
2
9
10
11
12
T (a)
T (a)
T (b)
R (a)
C (a)
T (b)
bl
C (b)
R (b)
bl
R (a)
C (a)
R (b)
I (a)
I (a)
C (b)
og
I (b)
I (b)
og
24
23
22
21
20
15
G
8
15 pin
female
19
15 pin male
G bn
(w)
B (a)
18
Screen bn
17
bn
32 pin female
Cable 1
TUNOL
a
c
SIFOX
3
4
6
I (a)
I (b)
R (a)
R (b)
C (a)
C (b)
T (a)
T (b)
T (a)
24
R (a)
T (b)
r
bl
23
R (b)
bl
C (a)
I (a)
w
r
22
C (b)
og
21
I (b)
og
20
19
15 pin
female
15 pin male
G bn
(w)
B (a)
18
Screen bn
B (b) bn
17
32 pin female
ABB
page 55 of 58
1KHW002011
1.
2.
3.
Add two wire wraps to the 32 pin SIFOX connector (19a-19c, and
20a-20c for SbU3) as shown in the Fig. 51.
TUNOS
CENCA
1
1
9
2
TD
TD
RD
RD
RTS
10
11
12
15
CTS
DSR
GND
GND
15 pin
female
15 pin
male
DTR
20
25
15 pin
male
15 pin
female
Cable 2
TUNOL
CENCA
TD
RD
RD
RTS
5
6
CTS
TD
DSR
GND
GND
DTR
20
25
15 pin
male
1KHW002011
page 56 of 58
15 pin
female
ABB
The SIFOX SbU connecting to the TUNOS / TUNOL V.11 OHC is configured
for EOC operation as follows:
Configuration of TUNOS /
TUNOL
CAS
Parameters Transmit clock source
Parameters Use of control signals
EOC Parameters Function
EOC Parameters Interface
Connection points
:
:
:
:
:
:
OFF
X (From DTE)
Enabled
Enabled
Slave (CENCA)
Direction to Master
The TUNOS / TUNOL V.11 OHC used for the EOC on all FOX NEs are configured as follows:
Mode: Service Channel and EOC
Once this is made, the following parameters are automatically set by
UCST:
:
:
:
:
:
:
:
OFF
ON
OFF
OFF
0 ... 9.6 kbit/s
Free running
TUNOS / TUNOL local
Special Note:
The UCST does not allow SIFOX channels that are configured for EOC operation 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 further EOC access to that TUNOS / TUNOL.
ABB
page 57 of 58
1KHW002011