RE. 316*4 and RE.

216 1MRB520270-Uen
Edition August 2001

Coupling to the MVB Interbay Bus

p
Operating Instructions

ICC
COM581 SCS

MVB Interbay Bus

PC
PC-Card
Card PC
PC-Card
Card BA + SC

RE. .16
RE..16 RE. .16 RER 581

PC
PC-Card
Card PC
PC-Card
Card

MVB Process Bus

500BOM11 500BIM11
BIM
 2000 ABB Power Automation Ltd
Baden/Switzerland

2nd Edition

from Version 4.4

All rights with respect to this document, including applications for patent and
registration of other industrial property rights, are reserved. Unauthorised use, in
particular reproduction or making available to third parties, is prohibited.

This document has been carefully prepared and reviewed. Should in spite of this
the reader find an error, he is requested to inform us at his earliest convenience.

The data contained herein purport solely to describe the product and are not a
warranty of performance or characteristic. It is with the best interest of our
customers in mind that we constantly strive to improve our products and keep
them abreast of advances in technology. This may, however, lead to discrep-
ancies between a product and its Technical Description or 'Operating Instructions'.
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

Contents

1. INTRODUCTION.........................................................................3
1.1. General .......................................................................................3
1.2. Abbreviations and definitions ......................................................3
1.3. References..................................................................................4
1.4. Application in the system ............................................................5

2. INSTALLATION AND COMMISSIONING ...................................6

2.1. Installation of the PC Card ..........................................................6
2.2. Connecting the components .......................................................8
2.3. Commissioning............................................................................8

3. SYSTEM ENGINEERING INSTRUCTIONS ...............................9

3.1. Assignment to the MVB data transfer modes..............................9
3.2. Application layer addresses ......................................................10
3.2.1. Signal addresses (events and commands) ...............................10
3.2.2. Process variable addresses ......................................................12
3.3. Transparent data on the SPA bus .............................................13
3.4. Relationship between cycling time and signal duration .............14
3.4.1. Normal operation.......................................................................14
3.4.2. Signal acquisition ......................................................................14

4. MVB INTERBAY BUS CONFIGURATION ................................16

4.1. Basic principles .........................................................................16
4.2. Settings provided ......................................................................17
4.2.1. Node/device address ................................................................17
4.2.2. Choice of processor (RE. 216 only) ..........................................17
4.3. Special interbay bus settings.....................................................17
4.4. Interlocking data configuration ..................................................21
4.5. Documentation function ............................................................22

5. DIAGNOSTICS, SUPERVISION AND MAINTENANCE ...........24

5.1. Diagnostics................................................................................24
5.1.1. Operating mode ........................................................................25
5.1.2. Status (PC Card Status)............................................................25
5.1.3. Error message (PC Card error) .................................................26
5.1.4. PC Card type.............................................................................26
5.1.5. Software version (PC Card SW vers)........................................26
5.1.6. PCC counter (PC Card heartbeat) ............................................26
5.1.7. Driver status ..............................................................................27
5.1.8. Driver counter (Driver heartbeat)...............................................27
5.1.9. Number of messages received (No. of received messages).....27
5.1.10. Number of messages transmitted
(No. of transmitted messages) ..................................................27

1
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

5.1.11. Number of transmission failures (No. of transmission fails) ......27

5.1.12. Number of lost incoming messages ..........................................28
5.2. Deleting diagnostic information .................................................28
5.3. Event masks..............................................................................28
5.4. Presentation of variable data ....................................................29
5.4.1. General .....................................................................................29
5.4.2. Reading messages ...................................................................29
5.5. Checking event transmission ....................................................29
5.6. Checking time synchronisation..................................................30

6. INDEX .......................................................................................31

2
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

1. INTRODUCTION

1.1. General
The RE. .16 is coupled to the MVB which is used as interbay bus
by an MVB personal computer card (PCC). This provides the
slave functions that are needed to exchange data with the
COM581 and interlocking data between the various RE. .16
units.
Interlocking data can be exchanged in binary form between
RE. .16 units connected to the same MVB interbay or process
bus.
The user thus has the possibility of transferring process control
data and data between RE. .16 units and between an RE. .16
unit and the station automation system (SCS).
This document describes the operation of the MVB interbay bus
software from Version V4.4 onwards. A corresponding descrip-
tion of the software for the MVB process bus is to be found in [6].

1.2. Abbreviations and definitions

BA Bus administrator
Bay Unit Unit containing the control and protection de-
vices for a switchgear bay
BIM, BOM Binary Input Module 500BIM11 /
Binary Output Module 500BOM11
(distributed input/output system RIO580), de-
vices connected to the process bus
COM581 Communication device for operating the MVB
IBB
HMI Human/machine interface, i.e. the operator
program running on a PC
IBB Interbay bus
ITL Interlocking data:
64 Bit telegram (48 Bit useful data and
16 Bit status information) for exchanging data
between bay units
MVB Multifunction Vehicle Bus, IEC 1378
Node address Bus ID for a device connected to it
PBI Process bus interface, I/O device for receiv-
ing and transmitting binary signals via the
process bus

3
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

PCC Personal Computer Card, formerly PCMCIA

card
RBI, RBO Binary input/output module for receiving and
transmitting binary signals via the process
bus (alternative designation for BIM and BOM
used in HMI program)
RE. .16/bay unit Type RE. .16 device, the first dot standing for
either C, G, L or T and the second for either 2
or 3 (e.g. REG 216, REL 316*4).
These units serve as hosts for the PCC.
RER581 Star-coupler for optical fibre cable buses
SA Substation automation
SC Star-coupler
SCS Station Automation System
Slot Socket for a PCC, module or board inserted
in an RE. .16 device
SOE Sequence of events (time-stamped record of
an system event)
216VC62(a) Processor unit used in an RE. 216 device
316VC61(a/b) Processor unit used in an RE. 316*4 device

1.3. References
[1] 1MRB520050-Ude: Operating Instructions REL 316*4
[2] 1MRB520051-Ude: Operating Instructions RET 316*4
[3] 1MRB520049-Ude: Operating Instructions REG 316*4
[4] 1MRB520044-Ude: Operating Instructions REC 316*4
[5] 1MDU02005-DE: Operating Instructions RE. 216
[6] 1MRB520192-Ude: Operating Instructions RIO 580
[7] IEC TC9 WG22: Train Communication Network, Parts 1 - 6,
Specification of the Multifunction Vehicle Bus and Wire
Train Bus, Edition November 95
[8] IEC 60870-5-101: Telecontrol Equipment and Systems,
Transmission Protocols, Companion Standard for Basic
Telecontrol Tasks, 1994
[9] MVB Application Guidelines for Substation Automation
(Interbay Bus) Version 2.0

4
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

1.4. Application in the system

ICC
COM581 SCS

MVB interbay bus

PC
PC-Card
Card PC
PC-Card
Card BA + SC

RE. .16
RE..16 RE. .16 RER 581

PC
PC-Card
Card PC
PC-Card
Card

MVB process bus

500BOM11 500BIM11
BIM

Figure 1.1 System with interbay and process buses

The interbay bus is used for exchanging data between the intel-
ligent communication controllers (COM 581) and the bay units
(e.g. REC 216) and between the bay units themselves. The bus
administrator runs on an RER 581 device which also includes
the star-coupler for the optical fibre cable bus.

5
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

2. INSTALLATION AND COMMISSIONING

2.1. Installation of the PC Card

The dimensions and marking of the PC Card (Figure 2.1) are
only typical and not binding.
When fitted at the top:

Figure 2.1 MVB PC Card

The PCC is active on Line A in a non-redundant configuration

and on Lines A and B in a redundant configuration.

6
MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

The RE. 316*4 has four Type 2 PCC slots (Figure 2.2). The MVB
PCC’s can be inserted in slots A and B.

Slot C Slot A

Slot D Slot B

Figure 2.2 Layout of the PCC slots on the back of the

316VC61(a/b) modules

The RE. 216 has two Type 2 PCC slots per 216VC62(a) (Figure
2.3). However, because of mechanical restrictions, the MVB
PCC can only be inserted in Slot A and a second 216VC62(a)
has to be fitted where two PCC’s are necessary (e.g. for the
MVB process bus).

Slot B Slot A

Figure 2.3 Layout of the PCC slots on the back of the

216VC62(a)

Caution:
• Do not insert or withdraw an MVB PCC while the supply is
switched on.
• An MVB PCC can only be inserted in an RE. 216 or
RE. 316*4 unit the one way round (mechanical key).
• Cover optical channels that are not in use.
• Take care to secure the MVB PCC in the RE. 216 /
RE. 316*4 using the holder supplied.
• Always handle the MVB PCC carefully.

7
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

2.2. Connecting the components

Use optical fibre cables with 62.5 µm diameter cores and fitted
with connectors Type BFOC/2,5 to connect the MVB PCC to the
star-coupler.
The transmit and receive cores have to be crossed between two
devices (i.e. connect the optical output TX from the MVB PCC to
the optical input RX on the star-coupler or SCS and the optical
output TX from the star-coupler or SCS to optical input RX on
the MVB PCC.

TX TX
PC Card Star-coupler

RX RX

Figure 2.4 Optical fibre cable interconnections between units

2.3. Commissioning
Using the HMI, firstly check that all the settings have be set to
the values determined when engineering the project. It is most
important to make sure that the MVB PCC is inserted in the cor-
rect slot. A PCC for the process bus must not be active in the
same slot.
Use the HMI diagnostic function to determine that the PCC soft-
ware runs properly (after initialisation, Ready and No error must
be display for PCC status and PCC error respectively).

8
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

3. SYSTEM ENGINEERING INSTRUCTIONS

3.1. Assignment to the MVB data transfer modes

In accordance with [7], process variables are transferred cycli-
cally and signals sporadically. The corresponding definitions are
listed in the following table. An additional rule applicable to
RE. .16 devices is that commands are transferred as signals;
there are no step positions for system supervision signals. This
conforms to the definitions in [9].

Information type MVB process variable MVB signal

(cyclic transfer) (sporadic transfer)

Process image (binary Yes No

signals)
Measured variables Yes No

Events (SOE) No Yes

Commands No Yes

Interlocking Yes No

Node supervision Yes No

Time synchronisation Yes No

Transparent data No Yes

Table 3.1 MVB data transfer modes

9
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

3.2. Application layer addresses

The addresses of signals and process variables are as given in
[7] which lists the definitions for RE. .16. Further information is
given in [9].

3.2.1. Signal addresses (events and commands)

The signals have addresses comprising a total of five Bytes, two for
the device address (unit address) and three designating the signal
itself (object address), as specified in IEC 60870-5-101 [8]:
Octet 1 (MSB) Octet 0 (LSB) Octet 2 (MSB) Octet 1 Octet 0 (LSB)

IEC 60870-5-101 Unit Address Object Address

MVB application Bus Node address Station address REB Signal ID

Address format (8 Bit) (6 Bit) (8 Bit) Node (12 Bit)

RE. .16 Bus SPA slave number SPA channel 0 SPA

Address format (8 Bit) number item number

Note:
The node address identifies a device connected to the interbay
bus. Of the available eight Bits, only six are used at present
(0...63).
Bus refers to the MVB segment.
Reference is also made to the RE. .16 address format and in this
respect, note should be taken of the following:
The SPA slave number of an RE. .16 unit is the same as the
node number and has to be in the range 1...63. The Byte ‘Bus’
always has to be set to 1.
The station address is the SPA channel number. As far as pos-
sible, the numbers defined for the SPA bus are used (with ex-
tensions in some cases):
101 ... 116 Input signal events: RE. 216, Slots 6 ... 21
and RE. 316*4, Slots 1 ... 4
71 ... 88 Protection function events
121 ... 126 Protection function events
129 ... 134 Double commands to the FUP
153 ... 192 Events from a device connected to the pro-
cess bus (BIM, PBI)

10
MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

Numbers (device numbers 1…80) are assigned to the input de-

vices connected to the process bus (BIM). There are two devices
per SPA channel resulting in the channel numbers given above:
SPA Channel No. = (Device number – 1) DIV 2 + 153. The event
numbers are 1…16 for the first device and 17...32 for the sec-
ond.
The general rule for the signal ID (event number) in the case of
RE. .16 is that it corresponds to the SPA signal or data number.
The data number is not multiplied by 2 as for SPA, in which case
the last Bit indicates whether the signal picks up or resets, but is
the correct number and whether the signal has picked up or re-
set is indicated separately in the data.
Example 1
Assuming the Input 3 of Device 2 in Slot 2 of an RE. 316*4 picks
up:
SPA event message: 102E5
MVB address: Channel No. = 102,
Signal ID = 3,
Event ID = ‘picks up.
Example 2
Assuming the Input 3 of Device 2 in Slot 2 of an RE. 316*4 re-
sets:
SPA event message: 102E6
MVB address: Channel No. = 102,
Signal ID = 3,
Event ID = ‘resets.
When a function requests an event message via the MVB, the
respective output has to be connected to a process variable
(signal to the SCS) and event recording switched on.

11
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

3.2.2. Process variable addresses

A piece of information that is transferred as a process variable is
uniquely identified by the dataset containing it and its position in
the dataset.
The addresses of process variables are assigned as follows:

Dataset No. Type Length (Bits) Utilisation

0 LBI_Set [1] 256 RE. 316*4: Input slots 1...4

RE. 216: Input slots 6...13

1 LBI_Set [2] 256 RE. 216: Input slots 14...16

2 BIM_Set [1] 256 BIM devices 1..16

3 BIM_Set [2] 256 BIM devices 17..32

4 BIM_Set [3] 256 BIM devices 33..48

5 BIM_Set [4] 256 BIM devices 49..64

6 SCSO_Set [1] 256 Function outputs

7 SCSO_Set [2] 256 Function outputs

8 SCSO_Set [3] 256 Function outputs

9 ITL_Set [1] 64 Interlock data (outputs)

10 MVO_Set [1] 256 Measured variables from func-

tions

11 Spare

12 Spare

13 Spare

14 Spare

15 DIA_Set [1] 16 Diagnostic data

Note:
Input signals received from the process are automatically con-
nected to the corresponding Bit in the dataset. Function outputs
and measured variables, on the other hand, have to be assigned
to the respective dataset using the HMI.
The address actually used for a dataset on the MVB interbay bus
is determined from: MVB address = 16 * Node No. + Dataset No.
An RE. 216 input module uses 32 Bits and an RE. 316*4 16 Bits.
A BIM module also uses 16 Bits.
The first input of an input module is always transferred at the first
position of the dataset for the corresponding slot.
Example: RE. 316*4 Input 1, Slot 2: Bit 16 in LBI_Set [1].

12
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

3.3. Transparent data on the SPA bus

SPA signals (commands, read and write instructions) and their
respective responses can be transferred via the MVB interbay
bus as explicit signals.
The ASCII character code must be structured as follows:
<SA><OP><KN><DT><D/E>:<WE>:
SA = Slave / not address
OP = Operation
KN = SPA channel No.
DT = Data type
D/E = Data/event No.
WE = Value.

• Slave / node address (SA):

The slave / node address corresponds to the device address.
• Operations (OP):
Possible operations are: R (read) to upload data from a device
and W (write) to download data to a device.
• SPA channel No. (KN):
The Channel No. Identifies the active functions.
• Data type (DT):
S Settings
I Binary and analogue inputs
O Binary and analogue outputs
E Individual events
V Measured variables, system variables and event masking
(exclusion from event recording)
Q Measured variables saved at the instant of tripping
T Time
D Date
L Event memory
B Backup event memory.

• Value (WE):
The value to be downloaded in the case of a write command.

13
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

Example 1
Assuming the first signal relay on the first binary board of an
RE. 316*4 has to be set, the device address (slave / node ad-
dress) is 8:
Command: 8W101O1:1:
Response: 8A:Checksum

Example 2
Assuming the second binary input on the first binary input board
of an RE. 316*4 has to be read, the device address (slave / node
address) is 6:
Command: 6R101I2:
Response: 6D:Value:Checksum

3.4. Relationship between cycling time and signal duration

3.4.1. Normal operation

As shown in Section 3.1, the statuses of binary signals are
transferred cyclically as process data. The cycling times and
thus also the signal length for which a status can be reliably
transferred are defined in the bus administrator. They must sat-
isfy the condition that the shortest signal length must be longer
than the cycling time setting.
Example
Assuming the cycling time is set to 64 ms, the status of a binary
signal will only be reliably transferred if it is maintained for longer
than 64 ms.

3.4.2. Signal acquisition

To ensure that all signal transitions including short ones are
transferred in spite of a relatively long cycling time, use can be
made of a special setting at the function outputs. Normally, bi-
nary outputs from the functions which are transferred as process
data via the interbay bus are connected to a data point “Signal to
the SCS” in one of the 24 48 Bit-long groups available.
This signal acquisition mode is activated by connecting the out-
put to a data point in groups 1c to 24c (c stands for “capture”, i.e.
acquisition).

14
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































bÇáì=cîçÅìáéç=m~ë~åÉìÉëí!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"


⌐============================================================================⌐


⌐=cîçÅ=kë=N=J=`îëëÉçìJaq==================G==G===============================⌐


⌐============================================================================⌐


⌐==m~ëpÉìQKKN================pÉäÉÅì=_áç~ëò=lîìèîì!"=========pÉäÉÅì==========⌐


⌐==qëáè======================⌐=====================⌐=========================⌐


⌐==aÉä~ò=====================⌐=pá,pÉäÉÅì=p`pJdëéîè....................../====⌐


⌐==fJpÉììáçÖ=================⌐=pá2======================================2====⌐


⌐==j~ójáç====================⌐=bï2=[==N=================================2====⌐


⌐==këlÑmÜ~íÉí================⌐=që2======================================2====⌐


⌐==`îëëÉçìfçè================⌐=pá2=rí~ÄäÉ=p`pJdëéîè=====================2====⌐


⌐==_äéÅâfçè==================⌐=lî2======================================2====⌐


⌐==qëáè======================⌐=lî2====NKKOQINÅKKOQÅ=====================2====⌐


⌐==pì~ëì=====================⌐=ob2======================================2====⌐


⌐==obqrokLbkqbo==============⌐===>......................................?====⌐


⌐============================@!!!!!!!!!!!!!!!!!!!!!A=========================⌐


⌐============================================================================⌐


⌐============================================================================⌐


@!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!A



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKO=ú=sSKO

Figure 3.1 Connection with and without signal acquisition

Note:
Signal acquisition is only available for signals generated by func-
tions and not for binary signals directly connected from the input
boards.

15
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

4. MVB INTERBAY BUS CONFIGURATION

4.1. Basic principles

The following figures illustrate how the user navigates to the
menu item in the HMI program for making the desired MVB in-
terbay bus settings.


















































































^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































j~áç=jÉçî!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=bÇáìéë!!!!!!!!!!!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=,bÇáì=e~ëÇñ~ëÉ=cîçÅìáéçí......./₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2==============================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=bÇáì=oÉä~ò=`éçÑáÖîë~ìáéç=====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=bÇáì=^ç~äéÖ=E`qLsqF=`Ü~ççÉäí=2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=bÇáì=_áç~ëò=fçèîìí===========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=bÇáì=qëáè=lîìèîìí============2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=bÇáì=páÖç~ä=lîìèîìí==========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=bÇáì=^ç~äéÖ=fçèîìí===========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=bÇáì=^ç~äéÖ=lîìèîìí==========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


@!@!2=bÇáì=f__Lofl=`éçÑáÖîë~ìáéç===2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧2=obqrok=======================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧2==============================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧>..............................?₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKO=ú=sSKO

Figure 4.1 ‘Edit hardware functions’ menu

All the submenus needed to make the settings are accessed via
the menu item ‘Edit IBB/RIO configuration’.

^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































j~áç=jÉçî!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=bÇáìéë!!!!!!!!!!!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=bÇáì=e~ëÇñ~ëÉ=cîçÅìáéçí!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=,f__=`éçÑáÖK................/₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=2===========================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=2=dÉçÉë~ä=f__=m~ë~åÉìÉëí====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=2=pm^=m~ë~åÉìÉëí============2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=2=ilk=m~ë~åÉìÉëí============2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=2=js_Jf__=m~ë~åÉìÉëí========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=2=js_Jofl=m~ë~åÉìÉëí========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=⌐=2=js_Jfqi=m~ë~åÉìÉëí========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


@!@!⌐=2=js_J_^=m~ë~åÉìÉëí=========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧@!2=ié~Ç=j_^m~ëí=Ñëéå=cáäÉ====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧2=p~ïÉ=oflJm~ëí=ìé=cáäÉ=====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧2=ié~Ç=oflJm~ëí=Ñëéå=cáäÉ===2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧2=obqrok====================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧2===========================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧>...........................?₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKO=ú=sSKO

Figure 4.2 ‘IBB configuration’ menu

16
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

4.2. Settings provided

4.2.1. Node/device address

Select ‘General IBB parameters’ to access the node address
settings. Every bay unit is assigned a number between 1 and 63.
(Note: The HMI will accept a value up to 255, but the full range
may not be used for devices connected to the MVB.)

4.2.2. Choice of processor (RE. 216 only)

RE. 216 units can have several processors (216VC62) in the
same rack. This menu item is therefore needed to specify by
virtue of the setting for parameter ‘IBB_CPUNr’, in which proces-
sor the PCC (numbering from left to right) is fitted.

4.3. Special interbay bus settings

All the parameters needed for the operation of the interbay bus
are accessed via the menu item ‘MVB IBB parameters’.
List of parameters:
Text Unit Default Min. Max. Step
IBB-PCC-Slot notUsed (Select)
IBB-TimeSync no (Select)
SOE-DestAddr1 1 0 64 1
SOE-DestAddr2 0 0 64 1
SOE-DestAddr3 0 0 64 1
SOE-DestAddr4 0 0 64 1
BusSegNr 1 0 4095 1
Cycle ms 1024 (Select)
Block SCSCmd BinaryAddr F
BlockProcDat BinaryAddr F
BlckPrDatSig SignalAddr ER
IBB-MW 1 MeasVariable
DeltaVal 1 Percent 1 1 32000 1
IBB-MW 2 MeasVariable
DeltaVal 2 Percent 1 1 32000 1
.
.
IBB-MW 15 MeasVariable
DeltaVal 15 Percent 1 1 32000 1

17
ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

Explanation of parameters:
IBB-PCC-Slot
Defines the slot into which the PCC for the interbay bus is in-
serted. The following settings are possible:
• notUsed
• A
• B
• C (RE. 316*4 only)
• D (RE. 316*4 only)

IBB-TimeSync
The setting of this parameter switches the time synchronisation
on and off. The following settings are possible:
• no: Time synchronisation is switched off
• yes: Time synchronisation is switched on

SOE-DestAddr1...4
These four parameters define the target nodes to which the
events (SOE) have to be transmitted. Up to four target nodes
can be defined (addresses 1 to 4). A value of ‘0’ for a target ad-
dress means that no events are transferred to the interbay bus.
Normally the COM581 node address(es) is (are) displayed here.
BusSegNr
Defines to which bus segment an RE. .16 is connected.
Cycle
Defines the refresh rate for measured variables transmitted via
the interbay bus. Note: The actual cycling time for process data is
determined by the configuration of the bus administrators. The re-
fresh rate defined by this parameter should agree with the one
actually measure. The following settings are possible:
• 4 ms
• 8 ms
• 16 ms
• 32 ms
• 64 ms
• 128 ms
• 256 ms
• 512 ms
• 1028 ms.

18
MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

Block SCSCmd
This parameter defines a binary signal which if TRUE, blocks
commands received via the interbay bus.
F: - Not blocked
T: - Blocked
xx: - All binary inputs or outputs of a protection function

BlockProcDat
This parameter defines a binary signal which if TRUE, blocks the
transfer of process data which have changed and SOE’s via the
interbay bus.
F: - Not blocked
T: - Blocked
xx: - All binary inputs or outputs of a protection function

BlckPrDatSig
A binary signal for reporting the status of the BlockProcDat sig-
nal. It is TRUE when the transfer of process data is blocked.

IBB-MW 1...15
These parameters are for selecting up to 15 measured variables
from protection functions and/or FUP programs for transfer as
process data via the interbay bus.

DeltaVal 1...15
These parameters enable a value, the so-called delta, to be de-
fined for each measured variable in order to reduce the number
of changes that have to be transferred. A new value is then only
transferred when it varies in relation to the last value transferred
by the amount of the setting for this parameter.
Nothing is transferred if the measured variable is lower than half
of the setting (suppresses small fluctuations of measure vari-
ables).
The principle of transferring measured variables is shown sche-
matically in Figure 4.3.

19
ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

The following relationship applies:

diff = diff + | NewValue – OldValue |
if | diff | > DeltaVal
then
diff = 0
if | NewValue | < 0.5 * DeltaVal
then
OldValue = 0,
send 0
else
OldValue = NewValue
send NewVal
where: ‘OldValue’ is saved internally.

Measured variable

t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t

Figure 4.3 Principle of transferring measured variables

In the above diagram, ∆ = DeltaVal and a value of zero is trans-

ferred at t11.
A scaling factor of 100 is applied to the setting for ‘DeltaVal’
which is then compared directly with the value of the measured
variable. In the case of percentages, a setting of 100 means that
a new value is sent if the value changes be 1 percent. If the
measured variable is normalised, a setting of 100 means that the
value has to change by 1 percent of the normalised value before
it is transferred.

20
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

4.4. Interlocking data configuration

The parameters for configuring the transfer of interlocking data
are accessed via the menu item ‘MVB ITL parameters’.
List of parameters:
Text Unit Default Min. Max. Step

ITL-PCC-Slot Not used (Select)

ITLIn 1…8 active (>0) B00000000
ITLIn 9…16 active (>0) B00000000
.
.
ITLIn 57…64 active (>0) B00000000

ITL-PCC-Slot
This parameter determines whether ITL data are used or not and
if so, via which bus they are transferred. The following settings
are possible:
• notUsed
• on MVB-RBIO (transferred via process bus)
• on MVB-IBB (transferred via interbay bus).

ITLIn 1...8 to 57...64

This parameter determines which nodes receive ITL data.
Note:
To keep the PCC and RE. .16 processing load to a minimum,
only configure those nodes which are actually needed.

21
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

4.5. Documentation function

The HMI provides facility for saving all the settings in files which
can then be used for configuring other devices connected to the
interbay bus:


















































































^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































,j~áç=jÉçî.........../₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2====================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=bÇáìéë=============2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=bïÉçì=e~çÇäáçÖ=====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=jÉ~íîëÉåÉçì=s~äîÉí=2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=qÉíì=cîçÅìáéçí=====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=aá~ÖçéíìáÅí========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=pjpMNMJbÇáìéë======2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=aéÅîåÉçì~ìáéç======2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2=obqrok=============2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


2====================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


>....................?₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKO=ú=sSKO

Figure 4.4 Main menu

The menu item Documentation permits a number of files to be

created: REaxx.EVT, REaxx.INP, REaxx.OUT, REaxx.PBI and
REaxx.SIG. “a” stands for the letter L, G, T or C (i.e. REL 316*4,
REG 316*4 etc.) and “xx” for the device address of the RE. .16
unit.

REaxx.EVT
This file contains a list of all the events transferred via the inter-
bay bus. All the events configured for an RE. .16 are set to “ON”
and the others to “OFF”. This file can be edited in cases where
fewer events have to be transferred via the IBB as recorded in
RE. .16 (replace “ON” by “OFF”). The edited file can be down
loaded to the RE. .16 using the menu item ‘Load SCS masks’ (see
Figure 5.1).

REaxx.INP
This is a text file with sections separated by dash-dot lines. It
contains information on all the inputs connected to data points
controlled by the SCS and can be edited using MS EXCEL.

22
MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

REaxx.OUT
This is a text file with sections separated by dash-dot lines. It
contains information on all the system’s binary output signals
connected to local relay outputs or SCS data points and can be
edited using MS EXCEL.

REaxx.PBI
This is a text file with sections separated by dash-dot lines. It
contains information on all the system’s binary output signals
connected to a relay in a BOM or PBI module and can be edited
using MS EXCEL.

REaxx.SIG
This is a text file with sections separated by dash-dot lines. It
contains information on all the system’s binary signals and all
protection and control functions and can be edited using MS
EXCEL.

23
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

5. DIAGNOSTICS, SUPERVISION AND MAINTENANCE

5.1. Diagnostics
The menu items ‘Diagnostics’, ‘IBB information’ and ‘MVB-
DiagnosisInfo’ enable various details of the PCC and the status
of the connection to it to be viewed.

^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































j~áç=jÉçî!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=,aá~ÖçéíìáÅí........../₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=====================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=iáíì=aá~ÖfçÑé=======2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=dÉì=eÉó=aîåè========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=`äÉ~ë=eÉó=aîåè======2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=f__JfçÑéëå~ìáéç=====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=oflJfçÑéëå~ìáéç=====2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=oÉíÉì=p`pJfçèîìÇ~ì~=2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=ié~Ç=p`pJj~íâí======2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=2=obqrok==============2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


@!2=====================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧>.....................?₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKO=ú=sSKO

Figure 5.1 ‘Diagnostics’ submenus

^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































j~áç=jÉçî!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=aá~ÖçéíìáÅí!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=,f__JfçÑéëå~ìáéç........../₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=========================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=dÉì=js_Jaá~ÖçéíáífçÑé===2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=`äÉ~ë=js_Jaá~ÖçéíáífçÑé=2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=dÉì=js_=jÉíí~ÖÉí========2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=obqrok==================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=2=========================2₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=>.........................?₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


⌐=⌐=obqrok==============⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


@!⌐=====================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧@!!!!!!!!!!!!!!!!!!!!!A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKO=ú=sSKO

Figure 5.2 Submenus of ‘IBB information’

24
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































,............................................................................/


2============================================================================2


2=js_Jf__Jaá~ÖfçÑéW==========================================================2


2============================================================================2


2téëâáçÖ=jéÇÉW========fçìÉëÄ~ò_îí============================================2


2m`J`~ëÇ=pì~ìîíW======oÉ~Çò==================================================2


2m`J`~ëÇ=bëëéëW=======ké=bëëéë===============================================2


2m`J`~ëÇ=qòèÉW========fçìÉëÄ~ò_îí============================================2


2m`J`~ëÇ=ptJsÉëíW=======NKMO==NVVUJNNJMU=====================================2


2m`J`~ëÇ=eÉ~ëì_É~ìW======QTPO================================================2


2aëáïÉë=pì~ìÉW==================ëÉ~Çò========================================2


2aëáïÉë=eÉ~ëìÄÉ~ìW=========QP================================================2


2këK=éÑ=ëÉÅÉáïÉÇ=jÉíí~ÖÉíW===========O=======================================2


2këK=éÑ=ìë~çíåáììÉÇ=jÉíí~ÖÉíW=======ON=======================================2


2këK=éÑ=që~çíåáííáéç=c~áäíW==========M=======================================2


2këK=éÑ=äéíì=áçÅéåáçÖ=jÉíí~ÖÉíW======M=======================================2


2============================================================================2


2============================================================================2


>............................................................................?



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKM=J=sSKM

Figure 5.3 Diagnostic information available via the MVB inter-

bay bus

5.1.1. Operating mode

Possible statuses:
Operating mode Function / Significance

not connected The PCC has not been configured or initialised,

or there is no PCC in the designated slot.

InterbayBus The PCC is configured for use on the interbay

bus.

5.1.2. Status (PC Card Status)

Possible statuses:
Status Function / Significance

No State A PCC is not inserted in the designated slot of

the RE. .16.
Not Ready The PCC is not ready.

Initialising The PCC is in the process of starting.

Ready The PCC is ready and is transmitting the data as

configured.

Minor Error An error occurred while starting or during opera-

tion, but the PCC is nevertheless in the Ready
status.

25
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

Status Function / Significance

Major Error An error occurred while starting or during opera-

tion. The PCC is being reset and restarted. This
procedure is repeated for as long as the fault
persists. The PCC is not standing by.

5.1.3. Error message (PC Card error)

Possible statuses:

Error message Function / Significance

No Error No error has occurred.

Unknown Error An unspecified error has occurred.

Error during Init An error occurred during initialisation.

No BusReply There is no communication between the PCC
and the interbay bus. Probably the bus adminis-
trator is inactive or has not been configured for
the address of the particular bay unit.

SubsystemError(s) A PCC software subroutine reports an error.

5.1.4. PC Card type

If a card is being used for the interbay bus, ‘InterbayBus’ must
be selected here.

5.1.5. Software version (PC Card SW vers)

Details of the version and the release date of the PCC software
reported by the PCC.

5.1.6. PCC counter (PC Card heartbeat)

A counter on the PCC is incremented cyclically in the range
0...65535. A continuously changing count is an indication that
the PCC is active.

26
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

5.1.7. Driver status

Possible statuses:

Status Function / Significance

No State The RE. .16 driver software did not start. A likely
cause is that the slot for the PCC has not been
configured.
Not Ready The RE. .16 driver software is not ready. Probably
there is no PCC in the slot configured.

Initializing The RE. .16 driver software is in the process of

starting.

Ready The PCC is ready, transmitting process data and

standing by to receive messages.

Minor Error An error occurred while starting or during opera-

tion of the RE. .16 driver software, but the system
is nevertheless standing by.

Major Error An error occurred while starting or during opera-

tion. Probably the PCC is not functioning cor-
rectly and is being reset. No data is being trans-
ferred.

5.1.8. Driver counter (Driver heartbeat)

A counter in the RE. .16 driver software is incremented cyclically in
the range 0...255. A continuously changing count is an indication
that the driver software is active.

5.1.9. Number of messages received (No. of received messages)

A counter counts all the messages, i.e. commands and trans-
parent SPA mode data, that are received.

5.1.10. Number of messages transmitted (No. of transmitted mes-

sages)
A counter counts all the outgoing messages, i.e. responses to
commands received, events (SOE’s) and responses of the
transparent SPA mode.

5.1.11. Number of transmission failures (No. of transmission fails)

A counter counts all the transmission errors detected by the
driver software.

27
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

5.1.12. Number of lost incoming messages

A counter counts all the lost messages. Events can be lost if in
response to an internally stored event, the driver software has to
transmit several events via the interbay bus (e.g. complex
measured variables generated by the distance protection func-
tion) and the PCC cannot do so successfully in a given time.

5.2. Deleting diagnostic information

The counters maintained by the driver software (see Sections
5.1.9. to 5.1.12.) can be reset by selecting the menu item ‘Clear
MVB-DiagnosisInfo’.

5.3. Event masks

Where fewer events than RE. .16 records have to be transferred
via the MVB interbay bus, select the menu item ‘Load SCS
masks’, which permits a file to be written in RE. .16 (see Section
4.5). To delete all the masks, select the menu item ‘Reset SCS
Inputdata’.

28
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

5.4. Presentation of variable data

5.4.1. General
Process data transferred via the MVB interbay bus can be
viewed using the HMI (see [1] to [5], Section 5.7.).

5.4.2. Reading messages

By selecting the menu item ‘Get MVB messages’ in the diag-
nostic submenu ‘IBB information’, the last message received and
the last message and event (SOE) transmitted can be viewed.
They are displayed as binary data in hexadecimal format and
can be analysed using [9].


















































































^__=méñÉë=^îìéå~ìáéç=iìÇ






























ob`PNSGQ=J=`éçìëéä=rçáì



















































































,............................................................................/


2============================================================================2


2============================================================================2


2jÉíí~ÖÉ|fç====jÉíí~ÖÉ|lîì=========bïÉçì|lîì=================================2


2MMMMMMMM=MM===MMMMMMMM=MM==========fMMMffMM=U`===MMfMMffM=OS================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMMf=MN===MMMMffff=Mc================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMff=MP===MMfffMMf=PV================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMMf=MN===fMfMfMMf=^V================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMfM=MO===MffMffff=Sc================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMMM=MM===MMMMMMMM=MM================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MffffMMf=TV==============================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMfMM=MQ==============================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMMf=MN==============================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMMf=MN==============================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMMM=MM==============================2


2MMMMMMMM=MM===MMMMMMMM=MM==========MMMMMMff=MP==============================2


2============================================================================2


2============================================================================2


>............................................................................?



















































































lç=J=iáçÉ=VSMM=Äèí===p`pWjs_






































sSKO=ú=sSKO

Figure 5.4 Viewing messages transferred via the MVB interbay

bus

5.5. Checking event transmission

The last event (SOE) to be transferred can be read in binary
form (see Section 5.4.2.). Detailed analysis is possible with the
aid of [9]. The counter ‘No. of transmitted messages’ (see Sec-
tion 5.1.10.) also gives indication of how many messages have
already been transmitted.

29
 ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

Caution:
Event information can be lost when events are generated in
the test mode (and the menu item “Test functions” is se-
lected in the HMI), because the monitor that checks whether
the COM581 has accepted the last event to be transmitted is
switched off in the test mode. Thus the generation of events
can be checked even though no COM581 is active.

5.6. Checking time synchronisation

Systems that include COM581 units cannot necessarily be checked
to ensure that their clocks are properly synchronised.
The following relatively simple procedure is therefore recom-
mended:
Set the parameter “IBB-TimeSync” to “no” to switch off the time
synchronisation function via the interbay bus. Then set the sys-
tem function parameter “TimeSynchByPC” to “on”. Restart the
RE. .16 to break the connection to the HMI. Now change the
time on the PC running the HMI to differ from the actual time.
Re-establish the connection between the HMI and the RE. .16
and check that the RE. .16 synchronises to the changed time on
the PC by selecting the menu item ‘Measurement values’ in the
‘Display AD channels‘ menu.
Now set the parameter “IBB-TimeSync” to “yes”. Restart the
PCC after downloading the parameters to the RE. .16. As soon
as it is ready, the RE. .16 should synchronise to the time trans-
mitted via the die IBB. This can once again be checked by se-
lecting the menu item ‘Measurement values’ in the ‘Display AD
channels’ menu.

30
 MVB Interbay Bus 1MRB520270-Uen / Rev. A ABB Power Automation Ltd

6. INDEX

Addresses, application layer, 10

Addresses, commands, 10
Addresses, datasets, 12
Addresses, devices, 17
Addresses, events, 10
Addresses, process variables, 12
Addresses, signals, 10
Application layer, addresses, 10

Checking event transmission, 29

Checking time synchronisation, 30
Command addresses, 10
Cycling time, measured variables, 18

Dataset addresses, 12
Device addresses, 17
Diagnostics, PCC, 25

Event addresses, 10
Event mask file, 22
Event masks, loading and deleting, 28
Event target address, 18
Event transmission, checking, 29
Events, viewing, 29

Measured variables, cycling time, 18

Messages, viewing, 29

Optical fibre cables, core connections, 8

Optical fibre cables, type, 8

PC Card handling instructions, 7

PC Card installation, 6
PC Card slot setting, 18
PC Card slots, 7
PCC diagnostics, 25
Process variable addresses, 12

Signal acquisition, cycling time, 14

Signal addresses, 10
Signal diagnostics, 27
SPA signals, 13

Target address, 18

31
ABB Power Automation Ltd MVB Interbay Bus 1MRB520270-Uen / Rev. A

Time synchronisation setting, 18

Time synchronisation, checking, 30

Viewing events, 29

32
 Daten löschen

Notification Form for Errors in this Document

Dear User,

We are always endeavouring to improve the quality of out technical publications

and would like to hear your suggestions and comments. Would you therefore please
fill in this questionnaire and return it to the address given below.

ABB Power Automation Ltd

Technical Publications Dept. NSB-5
Haselstrasse 16 / 65/1
CH-5401 Baden
Switzerland
Telefax +41 56 205 28 00
---------------------------------------------------------------------------------------------------------------

Concerns publication: 1MRB520270-Uen (RE.316*4, RE.216 MVB Interbay Bus)

Have you discovered any mistakes in this publication? If so, please note here the
pages, sections etc.

Do you find the publication readily understandable and logically structured? Can you
make any suggestions to improve it?

Is the information sufficient for the purpose of the publication? If not, what is missing
and where should it be included?

Name Date

Company

Postal code Town Country

Notification Form for Equipment Faults and Problems

Dear User,

Should you be obliged to call on our repair service, we kindly ask you to attach a note
to the unit describing the fault as precisely as possible. This will assist us to carry out
the repair swiftly and reliably and you will gain the benefit.
Please attach a completed form to every unit and forward them to the address below.

ABB Power Automation Ltd

Repair Center NAA-P
Eingang West, Warenannahme Terminal CA
CH-5401 Baden
Switzerland

---------------------------------------------------------------------------------------------------------------

Equipment data:

Unit type:
Serial No.: HE ..................................
In operation since:

Reason for return: (tick where applicable)

❑ Overfunction
❑ No function
❑ Outside tolerance
❑ Abnormal operating temperature
❑ Sporadic error
❑ Unit for checking

Remarks/Description of fault:

Customer: Date:

Address:

Please contact: Phone: Fax:

Notification Form for Software Errors and Problems

Dear User,

It is common experience that software does not always function as expected for all
applications. A precise description of the problem and observations will help us to
improve and maintain the software to your benefit. Please complete this form and
send it together with any supporting information or documents to the address below.

ABB Power Automation Ltd

Software Support Group NSS
Haselstrasse 16/122
CH-5401 Baden
Switzerland
Telefax +41 56 205 35 82
---------------------------------------------------------------------------------------------------------------

Unit/ ❑ REC 316*4 SW version: ❑ REC 216 SW version:

System: ❑ REG 316*4 SW version: ❑ REG 216 SW version:
❑ REL 316*4 SW version: ❑ HMI SW version:
❑ RET 316*4 SW version: ❑ other: SW version:

Problem: ❑ Program error (unit/system) ❑ Program error (HMI /PC)

❑ Manual error ❑ Suggestion for improvement
❑ other:

Can the error be reproduced at will? ❑ yes ❑ no

Particulars of hardware and software (unit/system configuration including jumper

positions, type of PC etc.):

Problem located? ❑ yes ❑ no

Suggested changes enclosed? ❑ yes ❑ no

The following are enclosed (floppy with settings etc.):

❑ Floppy ❑ Unit/system settings, file name:

❑ other:

Description of problem:

Customer: Date:

Address:

Please contact: Phone: Fax:

DESCRIPTION OF PROBLEM: (continuation)

___________________________________________________________________
ACTION (internal use of ABB Power Automation Ltd, Dept. NSS only)

Received by: Date:

Answered by: Date:

Problem solved? ❑ yes ❑ no

Week Name Position Consequence

---------------------------------------------------------------------------------------------------------------
 IMPORTANT NOTICE!

Experience has shown that reliable operation of our products is

assured, providing the information and recommendations con-
tained in these Operating Instructions are adhered to.

It is scarcely possible for the instructions to cover every event-

uality that can occur when using technical devices and systems.
We would therefore request the user to notify us directly or our
agent of any unusual observations or of instances, in which
these instructions provide no or insufficient information.

In addition to these instructions, any applicable local regulations

and safety procedures must always be strictly observed both
when connecting up and commissioning this equipment.

Any work such as insertion or removal of soldered jumpers or

setting resistors, which may be necessary, may only be per-
formed by appropriately qualified personnel.

We expressly accept no responsibility for any direct damage,

which may result from incorrect operation of this equipment,
even if no reference is made to the particular situation in the
Operating Instructions.
ABB Power Automation
ABB Power Automation AG
Haselstrasse 16/122
CH-5401 Baden/Schweiz
Telefon +41 56 205 77 44
Telefax +41 56 205 55 77
www.abb.com/substationautomation
Gedruckt in der Schweiz (0108-0XXX-0)
ABB Automation Products AB ABB Transmit Oy ABB Power T&D Co.
S-72171 Västerås, Schweden Relays and Network Control 4300 Coral Ridge Drive
Telefon +46 21 32 13 00 P.O.Box 699 Coral Springs, Fla. 33065
Telefax +46 21 14 69 18 FIN-65101 Vaasa, Finland USA
Telefon +358 10 224 000 Telefon +1 954 752 6700 ext. 2461
Telefax +358 10 224 1094 Telefax +1 954 345 5329