Remote Input / Output System

RIO 580 1MRB520192-Uen
Edition July 2001
Remote Input / Output System
p
Operating Instructions
Dezentrale Montage
Vorort-Steuerschrank
Local control cubicle
Bay unit
Feldgerät
PC-Card
PC card
LWL
Fibre optic
cable
500RER11
500RER11
LWL
Fibre optic
cable
500RIO11
500RIO11 500RIO11
500RIO11 500RIO11
500RIO11
Steuerkasten
Control housing
1997 ABB Power Automation Ltd
Baden/Switzerland
4th Edition
Valid for sw-versions:
Process bus – PC card: V3.00

500 BIM11: V3.00
RE. 216 / RE. 316*4: V6.2
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”.
RIO 580 1MRB520192-Uen / Rev. C ABB Power Automation Ltd
Contents
1. INTRODUCTION.........................................................................3
1.1. General .......................................................................................3
1.2. Abbreviations and definitions ......................................................3
1.3. Other relevant documents...........................................................5
1.4. Functional description .................................................................5
1.5. Possible means of exchanging data............................................6
1.5.1. Process bus with one RE. 216, RE. 316*4 unit ...........................6
1.5.2. Process bus with two or more RE. 216, RE. 316*4 units ............7
2. INSTALLATION AND COMMISSIONING ...................................8

2.1. Installing the PC card ..................................................................8
2.2. Interconnecting cables ..............................................................10
2.2.1. Bus termination .........................................................................11
2.2.2. Electrical bus length ..................................................................12
2.3. Entering the module addresses.................................................13
2.4. Plug-in jumper settings..............................................................20
2.4.1. Binary input module 500BIM11 .................................................20
2.4.2. Binary output module 500BOM11/12 ........................................22
2.4.3. Analogue input/output module 500AXM11................................23
2.5. Commissioning..........................................................................25
2.6. Limitations .................................................................................25
3. CONFIGURING THE MVB PROCESS BUS .............................26

3.1. Configuring the bus administrator and cycling times
(MVB-BA parameters)...............................................................26
3.2. Configuring the binary input/output modules
(MVB-RIO parameters) .............................................................29
3.3. Configuring interlocking parameters (MVB-ITL parameters) .....32
3.4. Configuring 500AXM11 modules...............................................33
3.5. Entering comments ...................................................................38
4. DIAGNOSIS, SUPERVISION AND MAINTENANCE ................41

4.1. PC card information ..................................................................41
4.2. PC card statuses and error messages ......................................41
4.2.1. PC card operating modes .........................................................41
4.2.2. PC card status...........................................................................42
4.2.3. Error messages.........................................................................42
4.2.4. PC card type .............................................................................44
4.2.5. PC card SW version..................................................................44
4.2.6. PC card counter ........................................................................44
4.2.7. Redundant bus administrators ..................................................44
4.3. RIO, PBI and ITL information ....................................................44
4.4. RIO module status ....................................................................45
1
ABB Power Automation Ltd RIO 580 1MRB520192-Uen / Rev. C
4.5. PBI module status .....................................................................46

4.6. Event list messages ..................................................................47
4.7. Significance of the module status information ...........................47
4.8. Supervision functions in the 500AXM11 module .......................47
4.9. Display of measured variables ..................................................49
4.10. Test functions / fault-finding ......................................................49
4.11. Replacing modules....................................................................49
4.12. Signals on the input/output unit 500RIO11................................49
4.12.1. Basic module 500RBM11..........................................................49
4.12.2. Binary output module 500BOM11/12 ........................................49
4.12.3. Binary input module 500BIM11 .................................................49
4.12.4. Analogue input/output module 500AXM11................................50
4.13. Signals on the star coupler unit 500RER11 ..............................50
4.13.1. Basic module 500RBM11..........................................................50
4.13.2. Star coupler module 500SCM11 ...............................................50
5. DETERMINING THE MAXIMUM POSSIBLE SYSTEM SIZE ...51

5.1. With internal bus administrator..................................................51
5.2. With external bus administrator.................................................51
6. CONFIGURATION PROCEDURE ............................................52

6.1. Setting the cycling times for the process bus ............................52
6.2. Activating individual modules ....................................................52
6.3. Checking the system.................................................................52
7. PROTECTION FUNCTION “ANALOG RIO TRIG” ....................53

7.1. Application ................................................................................53
7.2. Features....................................................................................53
7.3. Inputs and outputs.....................................................................53
7.4. Analogue RIO trigger function settings – Analog RIO Trig ........54
7.5. Setting instructions....................................................................56
7.5.1. Hardware requirements.............................................................56
7.5.2. Configuration.............................................................................56
8. INSTRUCTIONS FOR CONNECTING TO

THE INTERBAY BUS................................................................57
8.1. Analog RIO Trig 73 ...................................................................57
8.2. Analogue input/output signals ...................................................58
8.3. Binary input/output signals ........................................................58
8.3.1. Supervision signals on the analogue input/output modules ......60
8.3.2. Input/output module status information .....................................61
8.3.3. Event masks for binary inputs ...................................................63
2
1. INTRODUCTION
1.1. General
The RE. 216, RE. 316*4 unit is coupled to the process bus by an
MVB PC card which performs the slave/node and bus adminis-
trator functions.
The following remote binary input/output modules and telegrams
are supported:
• 500BIM11 (16 binary inputs)
• 500BOM11/12 (16 binary outputs)
• 500AXM11 (4 analogue inputs, 2 analogue outputs)
• Interlocking data (64 Bit telegrams)
• PBI (MVB interface module for coupling to the ABB High
Voltage Technologies Ltd., process bus).
Both the modules and the bus administrator can be configured
via the HMI of the RE. 216 or RE. 316*4.
RE. 216 units with a 216VC62 and RE. 316*4 units with a
316VC61 (revision F onwards), 316VC61a or 316VC61b can be
connected to an MVB process bus.
1.2. Abbreviations and definitions

RE. 216/bay unit PC card host: for protection cubicle or
compact version, “.” standing for either
C or G.
RE. 316*4/bay unit PC card host: RE. 316*4 unit, “.” standing
for either C, G, L or T.
RE. .16 RE. 216 / RE. 316*4
PC card personal computer card (PCC), formerly
PCMCIA.
MVB Multifunction Vehicle Bus according to
IEC 1375
BA bus administrator, see [3]
Slave-Node see [3]
MPL interface software
Device address see [3]
RIO 580 remote input/output system
3
500RIO11 remote input/output unit

500RER11 star coupler unit
500BIM11 remote binary input module for 500RIO11
500BOM11/12 remote binary output module for 500RIO11
500AXM11 remote analogue input/output module for
500RIO11
500RBM11 basic module for 500RIO11
500SCM11 remote star coupler module for 500RER11
216VC62 processor module in an RE. 216
316VC61 (a/b) processor module in an RE. 316*4
Interlocking (ITL) 64 Bit telegram (48 Bit useful data plus
data 16 Bit status information) for exchanging
data between the bay units and the
process bus
PBI Process Bus Interface HACE 437065
PBA software process bus coupling software
Bus termination prevents reflected signals on the electrical
bus
Daisy chain series connection of several units
HMI human/machine interface,
interface between the PC and
an RE. 216, RE. 316*4
Single mode Data are transferred via one channel
Redundant mode Data are transferred via two channels
IBB interbay bus (LON / MVB / SPA, …)
4
1.3. Other relevant documents

[1] Only for PBI modules: Hansjörg Öhler: Process Bus
Interface HACE 400008 (ABB High Voltage Technologies
Ltd.)
[2] IEC Multifunction Vehicle Bus (Part 3), Version 1.8.3b
(ABB High Voltage Technologies Ltd.)
[3] IEC General Architecture (Part 1), Version 1.5.2b
(ABB High Voltage Technologies Ltd.)
[4] Data Sheet

RIO500 Remote Input/Output System 1MRB520176-Ben
1.4. Functional description

When the power is switched on, the RE. .16 initialises the MVB
PC card and various subsystems are started in accordance with
the configuration. A reset signal is then transmitted to all the
500BIM11 modules by the RE. .16 units with device address 1 or
2 and the version of the software is read out. Whenever a
500BIM11 module is switched on or reset, it requests its
configuration data (e.g. input voltage, contact bounce time etc.)
from the RE. .16 (PC card) with device address 1 or 2. Once the
PC card has started, it reads the data from the 500BIM11 and
500AXM11 modules and makes them available to the RE. .16.
The RE. .16 transfers the data to the PC card which ultimately
appear at the outputs of the 500BOM11 and 500AXM11
modules.
The PC card monitors the operating condition of every module.
Should a module fail, an event is recorded in the event list and
signalled by the diagnostic function.
The input/output, synchronisation and diagnostic data are
transferred cyclically via the process bus, while events,
configuration data and commands are transferred as the need
arises.
5
1.5. Possible means of exchanging data
1.5.1. Process bus with one RE. 216, RE. 316*4 unit
The simplest case is when a bay unit (e.g. REC 316*4) is
connected to the MVB. The bus administrator software and the
PBA software are installed on the MVB PC card and are
accessible using the HMI. The bus administrator can also run
externally. 500RIO11 input data can be read and 500RIO11
output data transferred back to the outputs via the MVB PCC.
Interbay bus
(LON / MVB / SPA etc.)
IBB
interface
REC 316*4
Control unit REC 316*4
PBA +
BA
MVB process bus
el.
PC card opt.
Star coupler
500RER11
opt. opt. RS485
500RIO11 500RIO
• • • • • •
• • • • • •
Process connections
RIO cluster installed,

for example, in the
RS485 RS485 hinged frame
500RIO11 500RIO11 500RIO
• • • • • • • • •
Process connections RIO cluster installed,

for example, in the
remote cubicle
Fig. 1.1 Process bus with one RE. 316*4 unit
Caution:
500RIO11 modules may only be electrically connected
(RS485) to the 500RER11 when a redundant process bus is
not installed.
6
1.5.2. Process bus with two or more RE. 216, RE. 316*4 units
Several RE. 216 or RE. 316*4 units can be connected to a pro-
cess bus, provided there is either an external bus administrator
that cyclically polls all the addresses on the bus or a bay unit
using an internal bus administrator can be configured to poll all
the bus addresses, but only to process data from its own mod-
ules. Up to four bus administrators can operate in a redundant
configuration.
Interbay bus
(LON / MVB / SPA etc.)
IBB IBB
interface interface
REC 316*4 REC 316*4

• • • Control unit REC 316*4
PBA+ PBA+
BA BA
el. el.
PC card opt. PC card opt. MVB process bus
Star coupler
500RER11
opt. opt. RS485
500RIO11 500RIO11
• • • • • •
• • • • • •
Process connections
RIO cluster installed,

for example, in the
hinged frame
RS485 RS485
500RIO11 500RIO11 500RIO11
• • • • • • • • • RIO cluster installed,

Process connections for example, in the
remote cubicle
Fig. 1.2 Process bus with two or more RE. 216, RE. 316*4 units
Caution:
Binary input module data can be read by several RE. 216,
RE. 316*4 units, but only three RE. 216, RE. 316*4 may control
the binary output modules and only two the analogue output
modules.
7
2. INSTALLATION AND COMMISSIONING
2.1. Installing the PC card

PC card dimensions and markings may vary from those given
below (Fig. 2.1).
Top when installed
Fig. 2.1 MVB PC card
8
Caution:
Do not insert or remove the PC card while the auxiliary

supply is switched on. It can only be inserted in a RE. 216,
RE. 316*4 only in one direction (mechanically located).
• Cover unused optical channels.
• Do not plug in or unplug optical cables while the auxiliary

supply is switched on.
• Handle the PC card carefully.
• The PC card in the RE. 216 or RE. 316*4 must not be

operated without the holder supplied.
In a non-redundant configuration, the PC card uses line A and in

a redundant configuration lines A and B.
Each RE. 316*4 has four PCMCIA slots (Type 2). The mounting
supports can however support only two MVB PCC’s to be plugged
into the 316VC61a/b (slots A and B). If a LON, IEC 60870-5-103
or SPA bus is in use, then only slot B can be used for the
process bus. The slot where the PCC is located must be set in
the configuration data with the HMI.
Slot C Slot A
Slot D Slot B
Fig. 2.2 Arrangement of the PC card slots on the back of the

316VC61a/b module
9
Each RE. 216 has two PCMCIA slots (Type 2) in a RE. 216. The
mounting support can however support only one MVB PCC to be
plugged into the 216VC62a. The slot where the PCC is located
must be entered into the configuration data with the HMI.
Slot A
Slot B
Fig. 2.3 Arrangement of the PC card slots on the back of the

216VC62a module
In order to use two PC cards in a RE. 216 unit, a second

216VC62a module is necessary. In this case, the process bus is
connected to the second 216VC62a module.
2.2. Interconnecting cables

An optical fibre cable with a 62.5 µm diameter core is required to
connect the PC card to a bus or star coupler or the input/output
units.
The optical fibre cables between the PC card and the bus or star
coupler have to be transposed, i.e. the optical output TX on the
card must be connected to the optical input RX on the star
coupler and vice versa.
500RIO11 modules are equipped with one redundant optical
connector and two redundant electrical connectors can be used
to interconnect several 500RIO11 modules.
RS485 cable is used to electrically connect up to two 500RER11
star couplers and up to ten 500RIO11 input/output units (see
[4]).
If a 500RER11 star coupler is used in conjunction with MVB line
B, the electrical RS485 bus must not be connected to another
star coupler operating on MVB line A.
10
Input/output module 500RIO11

Module slots
Basic module: supply Optical connectors RS485-connectors
ABB ABB Power Automation

DC1 DC2 RxA TxA RxB TxB Y1 Y2
Address
Slot 3
2 16
C D Slot 2
1 15 1 15 1 15
2 16
A B Slot 1
1 15 1 15 1 15
Slot 3: Basic module with supply and communication interfaces

Slot 1 und 2: Input/output modules
Fig. 2.4 Module slots on a 500RIO11
PBI modules are equipped with an electrical connector and can

optionally be supplied with an optical connector.
2.2.1. Bus termination

Where several 500RIO11 units are connected via an RS485
cable, the two ends must be appropriately terminated with
dummy loads.
Local control cubicle
Bay
unit
PC card
Optical Dummy load

fibre
RS485
500RIO11 500RIO11 500RIO11
Input/output unit
HEST 985001 PP
Fig. 2.5 Bus terminations for units connected by a daisy

chain
11
Where individual 500RIO11 units are operated in a distributed

configuration, each must be fitted with two bus dummy loads.
Vorortsteuerschrank
Bay unit
PC card
Optical
fibre
500RER11
Optical Dummy load

fibre
500RIO11 500RIO11 500RIO11
Control box
HEST 985002 PP
Fig. 2.6 Bus terminations for a distributed configuration
2.2.2. Electrical bus length

As described in [4], the length of the electrical bus must not
exceed 20 m.
12
2.3. Entering the module addresses

A unique device address has to be configured for every module
before the input/output modules can operate in conjunction with
the MVB process bus. The addresses are set on the DIP
switches on the front of each device.
Caution:
• 500BIM11 modules only read their address once when
the auxiliary supply is switched on.
• 500BIM11 modules only read the configuration (BIM
software Version 2.04 onwards) from the RE. .16 with
device address 1 or 2.
Fig. 2.7 Location of the DIP switches for setting the device
address (extract from drawing 1MRB400242)
The device address for the module in slot 1 is set as a binary

number on DIP switches 1…8 (Table 2.1). DIP switch 1 does not
normally perform any function. Bit 1 of the device address is
determined largely by the slot or the positions of the plug-in
jumpers on the individual input/output modules. DIP switch 1
must therefore be set to OFF which means that only odd device
addresses can be set. Only in exceptions (large number of
500RIO11 modules or only one BIM, BOM or AXM) is it
necessary to set even device addresses.
Note: A DIP switch is ON when it is up (towards the Bit
number) and OFF when it is down.
Refer to the document [1] for how to set the address on PBI
modules.
13
The following addresses are assigned to the active modules

using the HMI. The second column is used when commissioning
and the third column is utilised for an external bus administrator.
The grey DIP switch is needed when only one module per
500RIO11 is fitted. It must be in the OFF position when two
modules are installed in each 500RIO11.
500AXM11, 500BIM11 DIP switch (S1) MVB data set number

or 500BOM11/12 settings on the and size
device addresses 500RIO11
1 1 8 ON 1024 and 1024 + data set
OFF
offset (16 Bit)
2 1040 and 1040 + data set
offset (16 Bit)
3 1056 and 1056 + data set
offset (16 Bit)
4 1072 and 1072 + data set
offset (16 Bit)
5 1088 and 1088 + data set
offset (16 Bit)
6 1104 and 1104 + data set
offset (16 Bit)
7 1120 and 1120 + data set
offset (16 Bit)
8 1136 and 1136 + data set
offset (16 Bit)
9 1152 and 1152 + data set
offset (16 Bit)
10 1168 and 1168 + data set
offset (16 Bit)
11 1184 and 1184 + data set
offset (16 Bit)
12 1200 and 1200 + data set
offset (16 Bit)
13 1216 and 1216 + data set
offset (16 Bit)
14 1232 and 1232 + data set
offset (16 Bit)
15 1248 and 1248 + data set
offset (16 Bit)
16 1264 and 1264 + data set
offset (16 Bit)
17 1280 and 1280 + data set
offset (16 Bit)
18 1296 and 1296 + data set
offset (16 Bit)
14

19 1312 and 1312 + data set
offset (16 Bit)
20 1328 and 1328 + data set
offset (16 Bit)
21 1344 and 1344 + data set
offset (16 Bit)
22 1360 and 1360 + data set
offset (16 Bit)
23 1376 and 1376 + data set
offset (16 Bit)
24 1392 and 1392 + data set
offset (16 Bit)
25 1408 and 1408 + data set
offset (16 Bit)
26 1424 and 1424 + data set
offset (16 Bit)
27 1440 and 1440 + data set
offset (16 Bit)
28 1456 and 1456 + data set
offset (16 Bit)
29 1472 and 1472 + data set
offset (16 Bit)
30 1488 and 1488 + data set
offset (16 Bit)
31 1504 and 1504 + data set
offset (16 Bit)
32 1520 and 1520 + data set
offset (16 Bit)
33 1536 and 1536 + data set
offset (16 Bit)
34 1552 and 1552 + data set
offset (16 Bit)
35 1568 and 1568 + data set
offset (16 Bit)
36 1584 and 1584 + data set
offset (16 Bit)
37 1600 and 1600 + data set
offset (16 Bit)
38 1616 and 1616 + data set
offset (16 Bit)
39 1632 and 1632 + data set
offset (16 Bit)
40 1648 and 1648 + data set
offset (16 Bit)
41 1664 and 1664 + data set
offset (16 Bit)
15

42 1680 and 1680 + data set
offset (16 Bit)
43 1696 and 1696 + data set
offset (16 Bit)
44 1712 and 1712 + data set
offset (16 Bit)
45 1728 and 1728 + data set
offset (16 Bit)
46 1744 and 1744 + data set
offset (16 Bit)
47 1760 and 1760 + data set
offset (16 Bit)
48 1776 and 1776 + data set
offset (16 Bit)
49 1792 and 1792 + data set
offset (16 Bit)
50 1808 and 1808 + data set
offset (16 Bit)
51 1824 and 1824 + data set
offset (16 Bit)
52 1840 and 1840 + data set
offset (16 Bit)
53 1856 and 1856 + data set
offset (16 Bit)
54 1872 and 1872 + data set
offset (16 Bit)
55 1888 and 1888 + data set
offset (16 Bit)
56 1904 and 1904 + data set
offset (16 Bit)
57 1920 and 1920 + data set
offset (16 Bit)
58 1936 and 1936 + data set
offset (16 Bit)
59 1952 and 1952 + data set
offset (16 Bit)
60 1968 and 1968 + data set
offset (16 Bit)
61 1984 and 1984 + data set
offset (16 Bit)
62 2000 and 2000 + data set
offset (16 Bit)
63 2016 and 2016 + data set
offset (16 Bit)
64 2032 and 2032 + data set
offset (16 Bit)
16
Interlocking telegram - MVB data set number

number and size
1. ITL - 2064 (64 Bit)
2. ITL - 2065 (64 Bit)
3. ITL - 2066 (64 Bit)
4. ITL - 2067 (64 Bit)
...
64. ITL - 2127 (64 Bit)
Redundant BA - 1 ... 63 (16 Bits) max. 4
supervison data sets
PBI device addresses DIP switch (S1) MVB data set number
settings on the PBI and size
1 2128 (32 Bit), 2136 (all
others 16 Bit), 2137,
2138, 2140
2 2144 (32 Bit), 2152 (all
others 16 Bit), 2153, 2154
2156
3 2160 (32 Bit), 2168 (all
2170, 2172
4 2176 (32 Bit), 2184 (all
2186, 2188
...
80 3392 (32 Bit), 3400 (all
3402, 3403
Table 2.1 Setting the device addresses for the modules
17
Calculation of the MVB data set number:

500BIM11:
Input data
(BIM number + 63) * 16
Diagnostic telegram
(BIM number + 63) * 16 + 1 (data set offset = 1)
500BOM11/12:
Trip circuit supervision
(BOM number + 63) * 16
Output data, Port 8
(BOM number + 63) * 16 + 8 (data set offset = 8)
Output data, Port 9
Output data, Port A
500AXM11:
Input data for Channel 1 to 4 Port 0 to 3
(AXM number + 63) * 16 + channel number - 1 (data set offset =
channel number - 1)
Supervision data Port 4
(AXM number + 63) * 16 + 4 (data set offset = 4)
ID data Port 5
Output data for Channel 1 Port 8
Output data for Channel 2 Port 9
Setting data for a communication failure for Channel 1 Port 10
Setting data for a communication failure for Channel 2 Port 11
Redundant output data for Channel 1 Port 14
Redundant output data for Channel 2 Port 15
18
PBI:
(PBI number * 16) + 2112 + data set offset = 0, 8, 9, A or C)
ITL:
(ITL telegram number + 2063)
19
2.4. Plug-in jumper settings
Caution:
The plug-in jumpers discussed below are inside the
input/output modules and do not normally need to be
changed.
Providing a module is ordered by order code in the data
sheet, all the plug-in jumpers are already correctly set when
it is delivered. The corresponding order code is quoted on
the label on the front of the module.
2.4.1. Binary input module 500BIM11

Each binary input module 500BIM11 has three plug-in jumpers.
Jumpers
Fig. 2.8 Plug-in jumpers on PCB 500BIM11
Jumper X700-702 is intended for the possibility of fitting the

module with larger flash EEPROM’s and must be left in its
default position X700-701.
20
Jumper X703-X704 protects the boot block of the flash

EEPROM’s and must not be fitted (default). It is only ever
inserted for programming, i.e. for deleting the boot block, which
is necessary when updating the SiMon supervision program. It
must be removed immediately afterwards.
Jumper X400-403 is for setting Bit 1 of the device address. Its
position depends on the slot the module occupies in the
500RIO11 unit.
Fig. 2.9 Plug-in jumpers X401-403 on PCB 500BIM11
Number of Slot Jumper Device address

modules fitted offset
2 1 X401-402 0
2 2 X401-400 1
1 1 X401-403 DIP switch Bit 1
Table 2.2 Plug-in jumpers X400-403 on PCB 500BIM11
Normally the first two positions (X401-X402 and X401-X400) are

used. The third position (X401-X403) is only needed in
exceptions (large number of 500RIO11 units with only one
module). On no account may the jumper be in position X401-
X403 when two modules are inserted in one 500RIO11 unit.
21
2.4.2. Binary output module 500BOM11/12

The binary output module 500BOM11/12 has only one plug-in
jumper.
Jumper
Fig. 2.10 Plug-in jumper on PCB 500BOM11/12

500RIO11 unit (see Table 2.3).
Fig. 2.11 Plug-in jumpers X301-303 on PCB 500BOM11/12
22
Number of Slot Jumper Device address

modules fitted offset
2 1 none 0
2 2 X302-303 1
Table 2.3 Plug-in jumpers X301-303 on PCB 500BOM11/12
Normally the first two positions (no jumper or X302-X303) are

module). On no account may the jumper be in this position when
two modules are inserted in one 500RIO11 unit.
2.4.3. Analogue input/output module 500AXM11

The analogue input/output module 500AXM11 has five plug-in
jumpers.
Fig. 2.12 Plug-in jumpers on PCB 500AXM11

500RIO11 unit (see Table 2.4).
23
Fig. 2.13 Plug-in jumpers X304-306 on PCB 500AXM11
Modules Device address

Slot Jumper
fitted offset
1 or 2 1 none 0
2 2 X304-306 1
Table 2.4 Plug-in jumpers X304-306 on PCB 500AXM11
Normally the first two positions (no jumper or X304-X306) are

module). On no account may the jumper be in this position when
two modules are inserted in one 500RIO11 unit.
There is a plug-in jumper for each of the four input channels that
has to be inserted when using a Pt1000 or Ni1000 temperature
feeler.
Sensor type Channel 1 Channel 2 Channel 3 Channel 4
Pt100, Ni100 none none none none

Pt250, Ni250 none none none none
Pt1000, X700-701 X1100-1101 X1500-1501 X1900-1901
Ni1000
Table 2.5 Plug-in jumpers X700-1901 on PCB 500AXM11
24
2.5. Commissioning
Take care during commissioning that the number of modules
activated in the HMI is not higher than the number actually
connected to the process bus. Superfluous active modules
unnecessarily load the PCC software.
The HMI diagnostic function provides facility for checking
whether the PC card has started correctly (PC_Card_Status:
Ready, PC_Card_Error: No error) and that all the modules
configured are actually connected (see Section 4).
Data may be lost if the electrical bus is not correctly terminated
with a dummy load (see Section 2.2.1).
2.6. Limitations
1) A maximum of four different cycle times may be set.
2) The ‘Operating Instructions’ refer to software versions:
RE. 216, RE. 316*4 HMI/Firmware: V6.2 onwards
PC card process bus: V3.00 onwards
500BIM11 software: V3.00 onwards
3) Up to four redundant bus administrators can be in operation.
4) It takes about 30 seconds for an RE. 216 or RE. 316*4 unit
and a PC card to start. The starting time of the 500BIM11
modules has to be added to this.
5) The diagnostic telegrams of the redundant bus
administrators are only supervised if they were previously
configured by the HMI.
6) 500BIM11 modules from Version 2.04 onwards request their
configuration from RE. .16 units with device address 1 or 2.
7) 500BIM11 modules (software Version 2.04 onwards) send
their events to the die RE. .16 with the device address 1 to 3.
8) Time synchronisation of the MVB process bus is performed
by the PC card Version 2.03 in RE. .16 units with device
addresses 1 and 2 in a redundant configuration.
25
3. CONFIGURING THE MVB PROCESS BUS
3.1. Configuring the bus administrator and cycling times

(MVB-BA parameters)
Select this menu item to set the cycling times for the various
modules (see Fig. 3.1) and select the modules to be polled by
the bus administrator. The modules are in groups of eight, but
not all the modules in a group have to be activated. This menu
item also permits modules to be activated that should not be
read by their own RE. .16, but by another RE. .16. Up to four
different cycling times are supported.
Either an internal bus administrator (the PC card includes a bus
administrator) or an external bus administrator can be selected.
The bus administrator on the PC card can also be operated in a
redundant configuration.
Provision is made for supervising a maximum of four bus
administrators (internal and external). For this purpose, the
device addresses of the bus administrators have to be entered in
the RE. 216 or RE. 316*4 HMI.
Internal bus administrator:
Select this menu item to set the module cycling times when
using an internal bus administrator. It is also used for selecting
the modules to be connected to the process bus.
Every RE. 216 or RE. 316*4 sends bus administrator diagnostic
telegram to the first device address entered in the HMI. The
RE. 216 or RE. 316*4 units receive bus administrator diagnostic
telegrams from all other device addresses entered. Where “0” is
entered as the device address, diagnostic telegrams are neither
transmitted nor received.
External bus administrator:
The module cycling times also have to be set as configured on
the PCC when using an external bus administrator.
26
The following system configurations are possible:

a) One internal BA and one RE. 216 or RE. 316*4 units
b) One external BA and one RE. 216 or RE. 316*4 units
c) Several internal BA’s and several RE. 216 or RE. 316*4 units
d) Several external BA’s and several RE. 216 or RE. 316*4 units

^__=méñÉë=^îìéå~ìáéç=iìÇob`PNSGQ=J=`éçìëéä=rçáì

bÇáì=cîçÅìáéç=m~ë~åÉìÉëí!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=f__Lofl=`éçÑáÖK=============G==G===========================================#
#============================================================================#
#==m_J_îí^Çåíìë~ìé=============éç=m`J`~ëÇ====================pÉäÉÅì==========#
#==_îí^ÇåN|^ÇÇë================N=============================================#
#==_îí^ÇåO|^ÇÇë================O=============================================#
#==_îí^ÇåP|^ÇÇë================M=============================================#
#==_îí^ÇåQ|^ÇÇë================M=============================================#
#==ofl==NKK=U==================_NMMMMMTU=====================~ÅìáïÉ=E[MF=====#
#==`òÅäÉ=======================PO=åí=========================pÉäÉÅì==========#
#==ofl==VKKNS==================_MMPMMMMM=====================~ÅìáïÉ=E[MF=====#
#==`òÅäÉ=======================PO=åí=========================pÉäÉÅì==========#
#==ofl=NTKKOQ==================_MMMMMMMM=====================~ÅìáïÉ=E[MF=====#
#==`òÅäÉ=======================PO=åí=========================pÉäÉÅì==========#
#==ofl=ORKKPO==================_MMPMMMMM=====================~ÅìáïÉ=E[MF=====#
#==`òÅäÉ=======================PO=åí=========================pÉäÉÅì==========#
#åéëÉKKK=====================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8

lç=J=iáçÉ=VSMM=Äèí===p`pWilksSKO=ú=sSKO
Fig. 3.1 Configuring the cycling times and the bus

administrators
Selecting the module on the bus administrator:
If the internal bus administrator is used, the bus administrator

parameters must include the modules that are connected and
the associated ports to be controlled. As Fig. 3.2 shows, a
choice can be made between a 500BIM11, the 500BOM11 ports
to be controlled (only port 8, ports 8 and 9, or ports 8, 9 and A)
and the 500AXM11 ports to be controlled (active = Ports 8 and 9,
active + standby = ports 8 and 9 and ports E and F).
27


?bÇáì=ofl|_^Jm~ë~åÉìÉëí@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@A
⌐================================================pÉäÉÅì!!!!!!!!!!!!!!!"=====⌐
⌐=ofl=aÉïkëK==R===G==G===========================#=====================#=====⌐
⌐================================================#=[==_fjJjéÇîäÉ=======#=====⌐
⌐==lîìméëìpÉäÉÅì===============_fjJjéÇîäÉ========#====_ljWméëì=U=======#=====⌐
⌐==obqrokLbkqbo==================================#====_ljWméëì=UIV=====#=====⌐
⌐================================================#====_ljWméëì=UV^=====#=====⌐
⌐================================================#====ûjW=eéìEUVF=====#=====⌐
⌐================================================#====ûjW=eéìpì_ò=====#=====⌐
⌐================================================#=====================#=====⌐
⌐================================================7!!!!!!!!!!!!!!!!!!!!!8=====⌐
⌐============================================================================⌐
⌐============================================================================⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J
⌐==`òÅäÉ=======================NS=åí=============⌐I@@I@@I@@I@@I@@I@@I@@I@@J⌐=⌐
⌐==ofl=ORKKPO==================_MMMMMMMM=========⌐=========================⌐=⌐
⌐==`òÅäÉ=======================NMOQ=åí===========⌐=========================⌐=⌐
⌐åéëÉKKK=========================================I@@@@@@@@@@@@@@@@@@@@@@@@@J=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J

Fig. 3.2 Configuring the module and port for the internal
bus administrator
Similarly, the HMI provides facility for determining whether the

bus administrator just polls Port 8, Ports 8 and 9 or Ports 8, 9
and A (=10) for the PBI’s that are connected. This setting only
applies for internal bus administrators.


?bÇáì=m_f=_^Jm~ë~åÉìÉëí@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@A
⌐================================================pÉäÉÅì!!!!!!!!!!!!!!!"=====⌐
⌐=m_f=aÉïkëK==V===G==G===========================#=====================#=====⌐
⌐================================================#=[==méëì=U=éçäò======#=====⌐
⌐==lîìméëìpÉäÉÅì===============méëì=U=éçäò=======#====méëì=U=~çÇ=V=====#=====⌐
⌐==obqrokLbkqbo==================================#====méëì=UIV=H=^=====#=====⌐
⌐================================================#=====================#=====⌐
⌐================================================7!!!!!!!!!!!!!!!!!!!!!8=====⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J
⌐==`òÅäÉ=======================NMOQ=åí===========⌐I@@I@@I@@I@@I@@I@@I@@I@@J⌐=⌐
⌐==m_f=NTKKOQ==================_MMMMMMMM=========⌐=========================⌐=⌐
⌐==`òÅäÉ=======================NMOQ=åí===========⌐=========================⌐=⌐
⌐åéëÉKKK=========================================I@@@@@@@@@@@@@@@@@@@@@@@@@J=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J

Fig. 3.3 Configuring a PBI port for the internal bus

administrator
The bus administrator settings and cycling times are saved in a

file called mbaXX.par that can be loaded in another RE. 216 or
RE. 316*4 (only using the internal bus administrator). Insert the
PB device address for XX.
28
3.2. Configuring the binary input/output modules

(MVB-RIO parameters)
The slot where the PC card is located is entered for ‘PB-PCC-
Slot’. A unique device address must be assigned to every
RE. 216 or RE. 316*4 connected to the process bus. This is
entered for ‘PB-DeviceAddress’. Where the PB is just one optical
fibre cable (line A), ‘RedundSupVis’ has to be set to ‘none’. The
redundant bus supervision functions has to be activated, on the
other hand, where a redundant PB is installed. Either ‘only_RIO’,
‘only_PBI’ or ‘RIO and PBI’ has to be selected in accordance
with the modules connected. ‘TimeSync’ determines whether the
respective RE. .16 shall synchronise the 500BIM11 modules.
Redundant time synchronisation by units with device addresses
1 and 2 only makes sense if both are synchronised to the same
reference source via the Interbay bus. The modules (500BIM11,
500BOM11/12, 500AXM11 and PBI’s) that communicate with the
respective RE. 216 or RE. 316*4 have to be selected via this
menu (see Fig. 3.4).


?bÇáì=cîçÅìáéç=m~ë~åÉìÉëí@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@A
⌐============================================================================⌐
⌐=f__Lofl=`éçÑáÖK=============G==G===========================================⌐
⌐============================================================================⌐
⌐==m_Jm``Jpäéì=================_=============================pÉäÉÅì==========⌐
⌐==m_JaÉïáÅÉ^ÇÇëÉí=============N=============================================⌐
⌐==oÉÇîçÇpîèsáí================képîèsáí======================pÉäÉÅì==========⌐
⌐==qáåÉpòçÅ====================éç============================pÉäÉÅì==========⌐
⌐==oflLm_f==NKK=U==============_NMMMMMTU=====================~ÅìáïÉ=E[MF=====⌐
⌐==oflLm_f==VKKNS==============_MMMMMMMM=========!!!!!!!!!!!!!!!!!!!!!!!!!"=⌐
⌐==oflLm_f=NTKKOQ==============_MMMMMMMM=========#=========================#=⌐
⌐==oflLm_f=ORKKPO==============_MMMMMMMM=========#?@@?@@?@@?@@?@@?@@?@@?@@A#=⌐
⌐==oflLm_f=PPKKQM==============_MMMMMMMM=========#⌐=N⌐=O⌐=P⌐=Q⌐=R⌐=S⌐=T⌐=U⌐#=⌐
⌐==oflLm_f=QNKKQU==============_MMMMMMMM=========#⌐u=⌐==⌐==⌐==⌐==⌐==⌐u=⌐u=⌐#=⌐
⌐==oflLm_f=QVKKRS==============_MMMMMMMM=========#I@@I@@I@@I@@I@@I@@I@@I@@J#=⌐
⌐==oflLm_f=RTKKSQ==============_MMMMMMMM=========#=========================#=⌐
⌐==m_f=SRKKTO==================_MMMMMMMM=========#=========================#=⌐
⌐åéëÉKKK=========================================7!!!!!!!!!!!!!!!!!!!!!!!!!8=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J


Fig. 3.4 Configuring an RIO
When a module is activated, a dialogue opens to configure it

(see Fig. 3.5). Upon selecting the type of module for parameter
‘DeviceType’, its parameter settings appear in the dialogue.
In the case of 500BIM11 modules, there are settings for bounce
filter time (debounce) for the inputs (0 to 30 ms in steps of 2 ms)
and the rated input signal voltage (24, 48, 60, 110, 125, 220 or
250 V).
29


bÇáì=ofl=m~ë~åÉìÉëí!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=ofl=m~ë~åÉìÉëí=aÉïkëK==O===G==G============================================#
#============================================================================#
#==aÉïáÅÉqòèÉ==================fçèîì=_fj=====================pÉäÉÅì==========#
#==aÉÄéîçÅÉqáåÉW===============Q=============================åí==============#
#==fçèséäì~ÖÉ==================QU=s==========================pÉäÉÅì==========#
#==obqrokLbkqbo==============================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8
⌐==oflLm_f=QVKKRS==============_MMMMMMMM=========⌐I@@I@@I@@I@@I@@I@@I@@I@@J⌐=⌐
⌐==oflLm_f=RTKKSQ==============_MMMMMMMM=========⌐=========================⌐=⌐
⌐==m_f=SRKKTO==================_MMMMMMMM=========⌐=========================⌐=⌐
⌐åéëÉKKK=========================================I@@@@@@@@@@@@@@@@@@@@@@@@@J=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J

Fig. 3.5 500BIM11 configuration parameters
An HMI entry has to be made for each 500BOM11/12 module

stating to which port (Port 8, Port 9 or Port A) the RE. .16 has to
send its data. A 500BOM11/12 module has three ports
connected to an OR gate (see Fig. 3.6).


?bÇáì=ofl=m~ë~åÉìÉëí@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@A
⌐================================================pÉäÉÅì!!!!!!!!!!!!!!!"=====⌐
⌐=ofl=m~ë~åÉìÉëí=aÉïkëK==V===G==G================#=====================#=====⌐
⌐================================================#=[==méëì=U===========#=====⌐
⌐==aÉïáÅÉqòèÉ==================lîìèîì=_lj========#====méëì=V===========#=====⌐
⌐==lîìèîìméëì==================méëì=U============#====méëì=^===========#=====⌐
⌐==obqrokLbkqbo==================================#=====================#=====⌐
⌐================================================7!!!!!!!!!!!!!!!!!!!!!8=====⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J
⌐åéëÉKKK=========================================I@@@@@@@@@@@@@@@@@@@@@@@@@J=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J

Fig. 3.6 500BOM11/12 configuration
For a 500AXM11 it is also necessary to state whether the

RE. .16 sets its outputs as the main (=active) or backup
(=standby) device. The main device sends the data of output
channels 1 and 2 via Ports 8 and 9, while the backup unit uses
Ports E (=14) and F (=15). The 500AXM11 normally accepts the
data from Ports 8 and 9 and only when no data are received
from them from Ports E and F (see Fig. 3.7).
30


?bÇáì=ofl=m~ë~åÉìÉëí@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@A
⌐================================================pÉäÉÅì!!!!!!!!!!!!!!!"=====⌐
⌐=ofl=m~ë~åÉìÉëí=aÉïkëK=ON===G==G================#=====================#=====⌐
⌐================================================#=[==eéìEméëìUIVF=====#=====⌐
⌐==aÉïáÅÉqòèÉ==================ûjJaÉïáÅÉ========#====pì~çÇ_òEbIcF=====#=====⌐
⌐==lîìméëìpÉäÉÅì===============eéìEméëìUIVF======#=====================#=====⌐
⌐==obqrokLbkqbo==================================7!!!!!!!!!!!!!!!!!!!!!8=====⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
⌐============================================================================⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J
⌐åéëÉKKK=========================================I@@@@@@@@@@@@@@@@@@@@@@@@@J=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J

Fig. 3.7 500AXM11 configuration
Supplementary information such as contact bounce time, writing

mode, print code and output port has to be entered for PBI’s via
the HMI (see Fig. 3.8). A detailed description of the PBI modules
is to be found in document [1] “Process Bus Interface” HACE
400008.


bÇáì=ofl=m~ë~åÉìÉëí!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=ofl=m~ë~åÉìÉëí=aÉïkëK=PR===G==G============================================#
#============================================================================#
#==aÉïáÅÉqòèÉ==================m_fJaÉïáÅÉ====================pÉäÉÅì==========#
#==aÉÄéîçÅÉqáåÉW===============U=============================åí==============#
#==tëáìÉjéÇÉW==================méëì=U=éçäò===================pÉäÉÅì==========#
#==mëáçì`éÇÉ===================N=============================================#
#==lîìèîìméëì==================méëì=U========================pÉäÉÅì==========#
#==obqrokLbkqbo==============================================================#
#============================================================================#
#============================================================================#
#============================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8
⌐åéëÉKKK=========================================I@@@@@@@@@@@@@@@@@@@@@@@@@J=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J

Fig. 3.8 Additional PBI configuration
31
3.3. Configuring interlocking parameters

(MVB-ITL parameters)
The parameter ITL-PCC-Slot (Fig. 3.9) determines which bus
(interbay or process) is used for transferring the interlocking
data.
Every RE. 216 or RE. 316*4 can transmit one interlocking
telegram and receive 63 telegrams. The ITLIn settings determine
which interlocking telegrams may be received.


?bÇáì=cîçÅìáéç=m~ë~åÉìÉëí@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@A
⌐============================================================================⌐
⌐=f__Lofl=`éçÑáÖK=============G==G===========================================⌐
⌐============================================================================⌐
⌐==fqiJm``Jpäéì================éç=js_Jofl====================pÉäÉÅì==========⌐
⌐==fqifç==NKK=U================_MMPMMMMM=====================~ÅìáïÉ=E[MF=====⌐
⌐==fqifç==VKKNS================_MMMMMMMM=====================~ÅìáïÉ=E[MF=====⌐
⌐==fqifç=NTKKOQ================_MMMMMMMM=====================~ÅìáïÉ=E[MF=====⌐
⌐==fqifç=ORKKPO================_MMMMMMMM=====================~ÅìáïÉ=E[MF=====⌐
⌐==fqifç=PPKKQM================_MMMMMMMM=========!!!!!!!!!!!!!!!!!!!!!!!!!"=⌐
⌐==fqifç=QNKKQU================_MMMMMMMM=========#=========================#=⌐
⌐==fqifç=QVKKRS================_MMMMMMMM=========#?@@?@@?@@?@@?@@?@@?@@?@@A#=⌐
⌐==fqifç=RTKKSQ================_MMMMMMMM=========#⌐=N⌐=O⌐=P⌐=Q⌐=R⌐=S⌐=T⌐=U⌐#=⌐
⌐==obqrokLbkqbo==================================#⌐J=⌐==⌐u=⌐==⌐==⌐==⌐==⌐==⌐#=⌐
⌐================================================#I@@I@@I@@I@@I@@I@@I@@I@@J#=⌐
⌐================================================#=========================#=⌐
⌐================================================#=========================#=⌐
⌐================================================7!!!!!!!!!!!!!!!!!!!!!!!!!8=⌐
I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J

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

Fig. 3.9 Configuring interlocks
32
3.4. Configuring 500AXM11 modules

Additional settings are possible via the HMI for the individual
inputs and outputs on 500AXM11 modules. They are located in
the two submenus “Edit Analog Inputs” and “Edit Analog
Outputs” listed in the “Edit Hardware Functions” menu.
Edit Analog Inputs:
Submenu “Edit Analog Inputs” gives access to two further
submenus (see Fig. 3.10):


?j~áç=jÉçî@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=?bÇáìéë@@@@@@@@@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=?bÇáì=e~ëÇñ~ëÉ=cîçÅìáéçí@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=^ç~äéÖ=fçèîìí!!!!!!!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=fçèîì=qòèÉ==============#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=`Ü~ççÉä=m~ë~åÉìÉëí======#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=`éååÉçì=================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=obqrok=======================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
I@I@⌐=bÇáì=f__Lofl=`éçÑáÖîë~ìáéç===⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐=obqrok=======================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐==============================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧


Fig. 3.10 Edit Analog Inputs
Once one or more 500AXM11 modules have been configured,

the type of signal has to be specified for each input (Edit Input
Type). Other parameters in the menu “Edit Channel Parameters”
can then be changed. All the parameters are listed and
explained in the following tables.
Summary of parameters
Submenu “Edit Input Type”
Text Units Default Min. Max. Step
Input Type R x/1 4..20 mA (Select)

33
Note: “x” denotes the device address of the 500AXM11 that has
been configured. Where there are several AXM modules, all the
respective inputs are displayed and if no AXM’s are configured,
the parameter dialogue is empty. The number following the slash
is that of the associated input channel to which the parameter
applies.
Submenu “Edit Channel Parameters”
Calibration R x/1 1.000 0.500 2.000 0.001

1) 2) 2) 2)
Offset R x/1 mA/V/°C 0.00 -20.00 20.00 0.01
Calibration R x/2 1.000 0.500 2.000 0.001
1) 2) 2) 2)
Offset R x/2 mA/V/°C 0.00 -20.00 20.00 0.01
Calibration R x/3 1.000 0.500 2.000 0.001
1) 2) 2) 2)
Offset R x/3 mA/V/°C 0.00 -20.00 20.00 0.01
Calibration R x/4 1.000 0.500 2.000 0.001
1) 2) 2) 2)
Offset R x/4 mA/V/°C 0.00 -20.00 20.00 0.01
1)
The unit of this parameter depends on the type set for the input, i.e. “mA”
for a current signal, “V” for a voltage and “°C” for a temperature.
2)
The setting range depends on the type set for the input.
respective inputs are displayed and if no AXM’s are configured,
applies.
Input Type R x/y
determines the type of analogue input signal (x = 500AXM11
device address, y = channel number). The following settings
are available:
- 0..20 mA
- 4..20 mA
- -20..20 mA
- 0..10 V
- -10..10 V
- Pt100
- Pt250
- Pt1000
- Ni100
34
- Ni250
- Ni1000
Calibration R x/y
determines the factor by which the input signal is multiplied.
The default setting is 1.000.
Offset R x/y
determines the value of the offset added to the input signal (x
= 500AXM11 device address, y = channel number). The
default setting is 0.00. Unit, setting range and step
(increment) depend on the type of input signal:
- Current: -20 to 20 mA in steps of 0.01 mA
- Voltage: -10 to 10 V in steps of 0.01 V
- Temperature: -200 to 200°C in steps of 0.1 °C
The offset entered is added to the input signal multiplied by any
factor entered.
Edit Analog Outputs:

Submenu “Edit Analog Outputs” also gives access to two further
submenus (see Fig. 3.11).


?j~áç=jÉçî@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=?bÇáìéë@@@@@@@@@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=^ç~äéÖ=lîìèîìí!!!!!!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=lîìèîì=qòèÉí=EoflF======#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=`Ü~ççÉä=m~ë~åÉìÉëí======#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=`éååÉçì=================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=obqrok=======================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐=obqrok=======================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐==============================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧

Fig. 3.11 Edit Analog Outputs
Once one or more 500AXM11 modules have been configured,

the type of signal has to be specified for each output (Edit Output
Types (RIO)). Other parameters in the menu “Edit Channel
Parameters” can then be changed. All the parameters are listed
and explained in the following tables.
35
Submenu “Edit Output Types (RIO)”
Output Type R x/1 4..20 mA (Select)

Output Type R x/2 4..20 mA (Select)
respective outputs are displayed and if no AXM’s are configured,
applies.
Submenu “Edit Channel Parameters”
Channel R x/y MWAInp 0

MinValue R x/y % 0.00 -320.00 320.00 0.01
MaxValue R x/y % 100.00 -320.00 320.00 0.01
OutputMode R x/y Keep Last (Select)
1) 2) 2)
Setpoint R x/y mA / V 0.00 -20.00 20.00 0.01
1)
The unit of this parameter depends on the type set for the output, i.e. “mA”
for a current signal and “V” for a voltage.
2)
The setting range depends on the type set for the output.
respective outputs are displayed and if no AXM’s are configured,
applies.
Output Type R x/y
determines the type of analogue output signal (x =
500AXM11 device address, y = channel number). The
following settings are available:
- 0..20 mA
- 4..20 mA
- -20..20 mA
- 0..10 V
- -10..10 V
36
Channel R x/y
specifies the signal source for the analogue output channel (x
= 500AXM11 device address, y = channel number). A
measured variable of a protection function, an AXM module
or from the Interbay bus (“Input from SCS”) can be set.
MinValue R x/y
determines the minimum output value for the measured
variable (see explanation below).
MaxValue R x/y
determines the maximum output value for the measured
variable (see explanation below).
OutputMode R x/y
determines the response of the output in the event of
communication failure between the RE. .16 and the
500AXM11. The following settings are available:
- Keep Last: The last value received appears at the output.
- Use Setpoint: The predefined value appears at the output.
Note: If a redundant (backup) RE. .16 is connected to the
process bus for relaying analogue output signals, it is
activated as soon as the active RE. .16 (main unit) fails and
before the output mode becomes effective.
Setpoint R x/y
determines the value at the output when communication
between the RE. .16 and the 500AXM11 has failed. The unit
and setting range of the parameter vary according to the type
of output signal set:
- Current: -20..20 mA in steps of 0.01 mA
- Voltage: -10 V..10 V in steps of 0.01 V
Note: If a redundant (backup) RE. .16 is connected to the
process bus for relaying analogue output signals, it is
activated as soon as the active RE. .16 (main unit) fails and
before the setpoint becomes effective (“OutputMode” must be
set to “Use Setpoint”).
37
Explanation of parameters “MinValue” and “MaxValue”:

The settings of these two parameters determine the ratio of the
output range to the measuring range of the measured variable.
This is illustrated by the following two examples.
Example 1:
The measured variable is a current measured by a protection
function. The range of 0 to 2.00 IN has to be transferred to an
analogue output type 4…20 mA, 0.00 IN corresponding to 4 mA
and 2.00 IN to 20 mA.
0.00 IN → 4 mA MinValue = 0.00 %
2.00 IN → 20 mA MaxValue = 200.00 %
Example 2:
The measured variable is a power measured by a protection
function. The range of –0.5 to 1.50 PN has to be transferred to
an analogue output type 0...20 mA, 0.50 PN corresponding to
0 mA and 1.50 PN to 20 mA. Thus a value of 0.00 PN
corresponds to an output of 5 mA.
-0.50 PN → 0 mA MinValue = -50.00 %
1.50 PN → 20 mA MaxValue = 150.00 %
3.5. Entering comments

The user has the possibility of entering a comment for every
input and output signal via the HMI. This simplifies the
identification of the various signals because the associated
comment is displayed whenever a particular signal is used.
The procedure for entering comments is similar for all the signals
of an RIO580 system. The following example for a binary input
signal on a 500BIM11 module therefore applies to all other
signals.
38
First select the menu item “Edit Binary Inputs” in the “Edit
Hardware Functions” submenu and then “Edit Comment”.


?j~áç=jÉçî@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=?bÇáìéë@@@@@@@@@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=bÇáì=_áç~ëò=fçèîìí!!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=bç~ÄäÉ=L=bïÉçìå~íâ======#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=`éååÉçì=================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=bÇáì=aéîÄäÉfçÇáÅ~ìáéç========#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#=obqrok=======================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐=obqrok=======================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐==============================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧

Fig. 3.12 Edit Binary Inputs
After selecting this submenu, a choice is presented between

editing local inputs and signals available via the process bus.


?j~áç=jÉçî@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=?bÇáìéë@@@@@@@@@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=?bÇáì=_áç~ëò=fçèîìí@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=pÉäÉÅì=i_f=éë=o_f!!!!!!!!!!!!!"₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=#=iéÅ~ä=fçèîìí=================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=#=oÉåéìÉ=fçèîìí================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=#=obqrok=======================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=#==============================#₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=I@7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐=obqrok=======================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧⌐==============================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧

Fig. 3.13 Edit Comment
39
After selecting the process bus inputs, a device address for the
respective input module is requested. This can be any number
from 1 to 80. Modules which have not been configured can also
be selected and comments for their inputs entered.


?j~áç=jÉçî@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=?bÇáìéë@@@@@@@@@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=?pÉäÉÅì=i_f=éë=o_f@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=⌐==============================⌐₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=⌐=iéÅ~ä=fçèîìí===========pÉäÉÅì=o_fJkëK!!!!!!!!!!!!!!!!!!!!!!!!"₧₧₧₧₧
⌐=⌐=⌐=⌐=⌐=oÉåéìÉ=fçèîìí==========#======================================#₧₧₧₧₧
⌐=⌐=⌐=⌐=⌐=obqrok=================#=[==N=================================#₧₧₧₧₧
⌐=⌐=⌐=⌐=⌐========================#======================================#₧₧₧₧₧
⌐=⌐=⌐=I@I@@@@@@@@@@@@@@@@@@@@@@@@#=rí~ÄäÉ=ofl=dëéîèí====================#₧₧₧₧₧
I@I@⌐=bÇáì=f__Lofl=`éçÑáÖîë~ìáéç=#======================================#₧₧₧₧₧
₧₧₧₧⌐=obqrok=====================#====NKKUM=============================#₧₧₧₧₧
₧₧₧₧⌐============================#======================================#₧₧₧₧₧
₧₧₧₧I@@@@@@@@@@@@@@@@@@@@@@@@@@@@7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧

Fig. 3.14 Selecting the device address
An input can be selected following the entry of the device

address. The <Insert> key is then pressed and the comment
entered.


?j~áç=jÉçî@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=?bÇáìéë@@@@@@@@@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=?pÉäÉÅì=i_f=éë=o_f@@@@@@@@@@@@@A₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧
⌐=⌐=⌐=⌐=⌐==============================⌐₧₧₧?pÉäÉÅì=`Ü~ççÉä@@@@@@@@@@@@@@@@@A₧₧
⌐=⌐=⌐=⌐=⌐=iéÅ~ä=fçèîìí===========?pÉäÉÅì=o_⌐===============================⌐₧₧
⌐=⌐=⌐=⌐=⌐=oÉåéìÉ=fçèîìí==========⌐=========⌐?@@?@@?@@?@@?@@?@@?@@?@@?@@?@@A⌐₧₧
⌐=⌐=⌐=⌐=⌐=obqrok=================⌐=[==N====⌐⌐=N⌐=O⌐=P⌐=Q⌐=R⌐=S⌐=T⌐=U⌐=V⌐NM⌐⌐₧₧
⌐=⌐=⌐=⌐=⌐========================⌐=========⌐⌐==⌐==⌐==⌐==⌐==⌐==⌐==⌐==⌐==⌐==⌐⌐₧₧
⌐=⌐=⌐=I@I@@@@@@@@@@@@@@@@@@@@@@@@⌐=rí~ÄäÉ=o⌐I@@I@@I@@I@@I@@I@@I@@I@@I@@I@@J⌐₧₧
I@I@⌐=bÇáì=f__Lofl=`éçÑáÖîë~ìáéç=⌐=========⌐?@@?@@?@@?@@?@@?@@A============⌐₧₧
₧₧₧₧⌐=obqrok=====================⌐====NKKUM⌐⌐NN⌐NO⌐NP⌐NQ⌐NR⌐NS⌐============⌐₧₧
₧₧₧₧⌐============================⌐=====`Ü~ççÉäí=`éååÉçì!!!!!!!!!!!!!!!!!!"⌐₧₧
₧₧₧₧I@@@@@@@@@@@@@@@@@@@@@@@@@@@@I@@@@@#=[=ríÉë=ÅéååÉçì===================#⌐₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8⌐₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧⌐===============================⌐₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧I@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@J₧₧
₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧₧

Fig. 3.15 Entering a comment for the input
40
4. DIAGNOSIS, SUPERVISION AND MAINTENANCE
4.1. PC card information

Select this menu item to view the current status of the PC card
(see Fig. 4.1).


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=js_JoflJaá~ÖfçÑéW==========================================================#
#============================================================================#
#téëâáçÖ=jéÇÉW========mëéÅÉííÄîí=ñáìÜ=_îí^Çåáçáíìë~ìéë=======================#
#m`J`~ëÇ=pì~ìîíW======oÉ~Çò==================================================#
#m`J`~ëÇ=bëëéëW=======ké=bëëéë===============================================#
#m`J`~ëÇ=qòèÉW========mëéÅÉííÄîí=============================================#
#m`J`~ëÇ=ptJsÉëíW=======PKMM==OMMNJMNJMU=====================================#
#m`J`~ëÇ=eÉ~ëì_É~ìW=====QNSOT================================================#
#iáçÉ=^=éâ>=L=iáçÉ=_=éâ>=L=MM================================================#
#_îí^Çåáçáíìë~ìéë|NW=oÉ~Çò===================================================#
#_îí^Çåáçáíìë~ìéë|OW=oÉ~Çò===================================================#
#_îí^Çåáçáíìë~ìéë|PW=kéì=oÉ~Çò===============================================#
#_îí^Çåáçáíìë~ìéë|QW=kéì=oÉ~Çò===============================================#
#============================================================================#
#============================================================================#
#============================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8


Fig. 4.1 PC card diagnosis
4.2. PC card statuses and error messages
4.2.1. PC card operating modes
Operating mode Function / Significance
None The PC card is not configured or the

configured slot is empty.
Process bus The PC card was initialised as a
process bus.
Process bus with bus administrator The PC card was initialised as process
bus with an internal bus administrator.
Table 4.1 PC card operating modes
41
4.2.2. PC card status
Status Function / Significance
None There is no PC card in the RE. 216,

RE. 316*4 slot configured.
Not Ready The PC card is not ready.
Initialising The PC card is starting.
Ready The system is ready.
Minor error An error occurred while starting or

during operation, but the system is still
operational (e.g. configured modules
missing or too many modules
configured).
Fatal error An error occurred while starting or

during operation (e.g. PCC and RE. .16
software are incompatible or wrong
MVBC on the PCC). The PC card will
continue to be reset and restart until the
fault is corrected.
Table 4.2 PC card status
4.2.3. Error messages

The error messages of consequence to the user are in bold print.
Error messages / Function / Significance

RE. .16 error code
No error No error has occurred.
Unknown error / 1H An unknown error has occurred.

Possibly too many modules configured.
No bus reply / 2H MVB problem.
Error during init. / 3H An error occurred during initialisation.

The configuration is probably incorrect
(e.g. too many update periods or too
many or no modules configured). See
Section 5.
42
Error messages / Function / Significance

RE. .16 error code
Some devices not Either the bus is not connected or one

connected / 6H of the modules configured is defective
or not available, 500BIM11 could not
start.
Status supervision too slow / 7H Too little CPU time for the MPL sink
time supervision function (too many
modules configured or cycling time set
too short).
Supervision task too slow / AH The is not enough computing time to

supervise the modules. The system as
a whole is too big or the cycling time is
too short. The transfer of data functions
correctly.
Copy task too slow / 5H The system as a whole is too big or the
cycling time is too short. Data may be
lost.
Supervision task terminated / 9H An error has occurred in the task

supervising the modules and it has
therefore aborted.
Copy task terminated / BH An error has occurred in the task that

copies the data and it has therefore
aborted.
Heartbeat task terminated / CH An error has occurred in the PC cards

diagnostic function.
MPL subsystem error / DH An error has occurred in the MPL

subsystem.
BA subsystem error / EH An error has occurred in the BA

subsystem (e.g. invalid configuration).
TIM subsystem error / 10H An error has occurred in the TIM
subsystem (time synchronisation). The
system times are therefore not
synchronised. This occurs when too
many modules are configured or the
cycling time is set too short.
EVA subsystem error / 11H An error has occurred in the EVA

subsystem (event and alarm handling).
DBS subsystem error / 12H An error has occurred in the data base
subsystem.
Table 4.3 PC card error messages
43
4.2.4. PC card type

Process or interbay bus
4.2.5. PC card SW version

Software Version and —Year—Month—Day
4.2.6. PC card counter

A ring counter is cyclically incremented and this indicates that
the PC card is active.
4.2.7. Redundant bus administrators

Every bus administrator that is configured transmits a diagnostic
telegram which all the RE. 216 or RE. 316*4 units can read. If
the diagnostic telegrams that have been configured are not
received or the software determines that the redundant bus
administrators are not ready, the statuses of the bus
administrators are set to “Not ready”.
4.3. RIO, PBI and ITL information

After the PC card has started and is in the “Ready” state, the
500BIM11, 500BOM11/12 and PBI modules are checked to
determine whether they are connected to the process bus and
the ITL data sets are checked to determine whether data are still
being transferred. The results are displayed in the RIO
diagnostic window. A hyphen “-” indicates a module that has not
been configured, a zero “0” a module that has been configured,
but is not connected, and an “X” a module that is both configured
and connected (see Fig. 4.2).


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=oflJaÉïáÅÉí=ëÉíèéçÇáçÖW====================================================#
#============================================================================#
#=këK=éÑ=oÉíÉìíW======M======================================================#
#============================================================================#
#=aÉïáÅÉí==NKK=UW=uJJJJJuu===================================================#
#=aÉïáÅÉí==VKKNSW=JJuJJJJJ===================================================#
#=aÉïáÅÉí=NTKKOQW=JJJJJJJJ===================================================#
#=aÉïáÅÉí=ORKKPOW=JJuJJJJJ===================================================#
#=aÉïáÅÉí=PPKKQMW=JJJJJJJJ===================================================#
#=aÉïáÅÉí=QNKKQUW=JJJJMMJJ===================================================#
#=aÉïáÅÉí=QVKKRSW=JJJJJJJJ===================================================#
#=aÉïáÅÉí=RTKKSQW=JJJJJJJu===================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8


Fig. 4.2 RIO supervision
44
After switching on the auxiliary supply of an RE. 216 or

RE. 316*4 unit, the reset counter is set to “0” (see Fig. 4.2 and
Fig. 4.5). It is then incremented by 1 every time the PC card is
restarted. The PC card is also restarted after changing the HMI
settings.
4.4. RIO module status

Every time the system is restarted, the RE. .16 reads the
software version of every 500BIM11 module (see Fig. 4.3) and
displays whether the device responds and the status of the
redundant line.


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=oflJpì~ìîíJfçÑéW===========================================================#
#============================================================================#
#=këK=éÑ=oÉíÉìíW======M======================================================#
#=aÉïáÅÉ=këK==OO=============================================================#
#=aÉïáÅÉ=ëÉíèéçÇáçÖ>=========================================================#
#=iáçÉ=^=éâ>=L=iáçÉ=_=éâ>=L=MM===============================================#
#=qÜÉ=_fj=jéÇîäÉ=pì~ìÉW=oÉ~Çò=====`éîçìÉë=s~äîÉW==NV=========================#
#=ptJsÉëíáéçW===PKMM=========================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8


Fig. 4.3 500BIM11 software ID and module status information
Similarly, the RE. .16 reads the version of every 500AXM11

module (see Fig. 4.4).
45


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=oflJpì~ìîíJfçÑéW===========================================================#
#============================================================================#
#=këK=éÑ=oÉíÉìíW======M======================================================#
#=aÉïáÅÉ=këK==ON=============================================================#
#=fí=~ç=ûjJjéÇîäÉ>==========================================================#
#=ûjJfaW=NMM===sÉëíáéçW=MMMN================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8


Fig. 4.4 500AXM11 software ID and module status information
4.5. PBI module status

Because the PBI modules have many parameters that have to
be set and the settings can be read, the information is available
to enable the input and output statuses of every PBI module to
be displayed.


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
#============================================================================#
#=m_fJpì~ìîíJfçÑéW===========================================================#
#============================================================================#
#=këK=éÑ=oÉíÉìíW======M======================================================#
#=aÉïáÅÉ=këK===N=============================================================#
#=aÉïáÅÉ=oÉ~Çò===============================================================#
#fçèîì=pì~ìîíW===============lîìèîì=pì~ìîíW==================================#
#==aÉÄéîçÅÉqáåÉW====U==========aÉÄéîçÅÉqáåÉW====U============================#
#==mëáçì`éÇÉW=======P==========tëáìÉjéÇÉW=======N============================#
#==tëáìÉjéÇÉW=======N==========lîìèîìméëìW======U============================#
#==cmd^`éÇÉW========N========================================================#
#============================================================================#
#============================================================================#
#============================================================================#
#============================================================================#
7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!8


Fig. 4.5 PBI status information
46
4.6. Event list messages

The PC card generates messages that can be configured via the
HMI system parameter menu (see Section 3.4 in the RE. .16
Operating Instructions) to be recorded as events.
The process bus error message ‘MVB_PB_Warn’ is displayed
should not all the modules respond that have been configured.
The message means that there is no communication via the
process bus, i.e. none of the devices responds.
‘PB_BA1Ready’ … ‘PB_BA4Ready’ indicate that the bus
administrators that have been configured are standing by.
Where the system includes a redundant process bus and the
corresponding supervision function is activated (see Section 3.2),
the error messages ‚PB LA faulty‘ and ‚PB LB faulty‘, indicate
that the PC card has detected an interruption of line A or B.
4.7. Significance of the module status information

Every device connected to the process bus supplies information
as to whether it can communicate via the system and whether
the redundant line has failed. This is also in the form of
information that can be processed by the RE. .16 (e.g. by a
FUPLA logic). For this purpose, it is necessary to select the
menu item ‘Input from RBI’s’ in the ‘Select Binary Input’ menu in
order to change the wiring of a binary input (e.g. the binary
FUPLA input). Diagnostic information is then available at Bit
numbers 17, 18 and 19.
Bit 17:“Device connected”: This Bit is at logical 1 when the
device can communicate.
Bit 18:“Line A faulty”: The RIO module has detected an error on
redundant line A.
Bit 19:“Line B faulty”: The RIO module has detected an error on
redundant line B.
4.8. Supervision functions in the 500AXM11 module

The 500AXM11 module supplies information on the status of its
external wiring which is recorded in the event list and can be
viewed by selecting “Display RBI Status” in the “Measurement
Values” menu. This information is also available as process
information and input signals of protection functions (e.g.
FUPLA). The information provided by the various Bits is as
follows:
47
Bit 1: “Broken wire Out-Channel 1”: The connection to output 1

is open-circuit (4..20 mA only).
Bit 2: “Broken wire Out-Channel 2”: The connection to output 2
is open-circuit (4..20 mA only).
Bit 3: Not used.
Bit 4: “Update missing channel 1”: No data being received for
channel 1 from the active RE. .16 unit (main unit).
Bit 5: “Update missing channel 2”: No data being received for
channel 2 from the active RE. .16 unit (main unit).
Bit 6: “Supply short-circuit (Ch1)”: The supply of input 1 sensor
is short-circuited.
is short-circuited.
is short-circuited.
is short-circuited.
Bit 10: “Update missing Red.Chan 1”: No data being received for
channel 1 from the redundant RE. .16 unit (standby unit).
Bit 11: “Update missing Red.Chan 2”: No data being received for
channel 2 from the redundant RE. .16 unit (standby unit).
Bit 13: “Broken wire In-Channel 1”: The connection to input 1 is
open-circuit (4..20 mA and temperature only).
Bits 13 to 16 are generated by the RE. .16 when the input falls
below 3.8 mA, respectively –100 °C or exceeds 500 °C.
48
4.9. Display of measured variables

The values of all the inputs and outputs can be viewed via the
“Measurement Values” menu. Refer to Section 5.7 of the RE. .16
Operating Instructions for further details.
4.10. Test functions / fault-finding

The test functions “Set test data” and “Perform selected test”
enable test data to be transmitted to the 500BOM11/12 and
500AXM11 modules, PBI’s and ITL.
4.11. Replacing modules

500RIO11 units: Note that replacing 500RIO11 units in
operation that are linked by an RS485
daisy chain will interrupt the bus and cause
data to be lost.
PBI units: Refer to document [1] “Process Bus
Interface HACE 400008” before replacing
PBI units.
4.12. Signals on the input/output unit 500RIO11
4.12.1. Basic module 500RBM11

The green LED ‘DC’ is lit providing the input voltage is within the
range 36 VDC…312 VDC and the internal auxiliary supplies are in
tolerance.
The four yellow LED’s (RxA, TxA, RxB and TxB) light when data
are being transferred via line A or B of the electrical MVB bus.
If the MVB bus is used non redundant, the LED’s RxA and both
TxA and TxB light.
All four LED’s light if there are redundant MVB buses.
4.12.2. Binary output module 500BOM11/12

Each output has its own yellow LED which lights when it is
activated.
4.12.3. Binary input module 500BIM11

Each input has its own yellow LED which lights when it is
activated.
49
4.12.4. Analogue input/output module 500AXM11

This module has six green LED’s that all light in normal
operation and do not all light in the following cases:
LED’s 1..4: A LED does not light when the supply to the
respective sensor is short-circuited.
LED’s 5 and 6: The associated LED does not light when a circuit
is open, e.g. because an external lead is interrupted. A circuit
which is not needed must be short-circuited. Both LED’s go out if
no valid data are received for more than 1.1 s.
4.13. Signals on the star coupler unit 500RER11
4.13.1. Basic module 500RBM11

The green LED ‘DC’ is lit providing the input voltage is within the
range 36 VDC…312 VDC and the internal auxiliary supplies are in
tolerance.
Since only MVB line A is used by the star coupler, only the two
LED’s RX1 and TX1 on the left are of consequence and light
when data are being transferred via line A of the electrical MVB
bus.
4.13.2. Star coupler module 500SCM11

The star coupler module 500SCM11 is equipped with six optical
channels. The associated yellow LED Rx lights for every channel
to which an optical cable is connected and data are being
received. Depending on whether one or several 500SCM11 are
installed, the LED’s Tx1 to Tx7, respectively Tx13 all light when
data are being transmitted.
50
5. DETERMINING THE MAXIMUM POSSIBLE SYSTEM SIZE
5.1. With internal bus administrator

The internal bus administrator (BA) occupies a part of the PC
card computing capacity and to ensure that the PC card is not
overloaded, the following equation has to be satisfied.
b 4 + 3 * a 4 + 5 * p 4 + I 4 b 8 + 3 * a 8 + 5 * p 8 + I8 b + 3 * a 1024 + 5 * p 1024 + I1024

+ + ... + 1024 ≤1
4 8 1024
b4, b8, b16, ... b1024 = number of binary input/output modules

(500BIM11/500BOM11/12) with cycling times of
4 ms, 8 ms...1024 ms
a4, a8, ... a1024 = number of analogue input/output modules

(500AXM11) with cycling times of 4 ms,
8 ms...1024 ms
p4, p8, ... p1024 = number of PBI modules with cycling times of 4 ms,
8 ms...1024 ms
I4, I8, ... I1024 = number of interlock telegrams with cycling times of
4 ms, 8 ms...1024 ms
5.2. With external bus administrator

More modules can be configured using an external bus
administrator than using an internal one. To ensure that the PC
card is not overloaded, the following equation has to be satisfied.
b 4 + 3 * a 4 + 5 * p 4 + I 4 b 8 + 3 * a 8 + 5 * p 8 + I8 b + 3 * a 1024 + 5 * p 1024 + I1024

+ + ... + 1024 ≤ 1 .7
4 8 1024
b4, b8, ... b1024 = number of modules (500BIM11/500BOM11) with

cycling times of 4 ms, 8 ms ... 1024 ms
a4, a8, ... a1024 = number of analogue input/output modules

(500AXM11) with cycling times of 4 ms,
8 ms...1024 ms
p4, p8, ... p1024 = number of PBI modules with cycling times of 4 ms,
8 ms...1024 ms
I4, I8, ... I1024 = number of interlock telegrams with cycling times of
4 ms, 8 ms...1024 ms
51
6. CONFIGURATION PROCEDURE
The procedure for configuring the process bus is as follows:

Assuming a process bus has to be configured for a system
comprising three RE. 216 or RE. 316*4 units (e.g. RE. 316*4 A,
RE. 316*4 B and RE. 316*4 C), the RE. 316*4 A, for example,
additionally performs the bus administrator function (internal BA).
Thus the 500BIM11 and 500BOM11 modules, the PBI’s and the
interlocking telegrams have to be configured.
6.1. Setting the cycling times for the process bus

First activate the internal bus administrators of the RE. 316*4 A
and set the cycling times for the various module groups (see
Section 3.1). In the same window, active all the modules that
have to be connected to the process bus, i.e. all modules
processed by the RE. 316*4 A, B and C units. The
corresponding data are saved in the file mbaXX.par (the
respective device address is inserted for XX). The file
mbaXX.par can then be copied to the two other RE. 316*4 units
so that the module cycling times and the ITL data sets only have
to be entered once in one RE. 316*4. If a different device
address to the one in RE. 316*4 A is detected when copying the
configuration file mbaXX.par to RE. 316*4 B and C, the system
switches automatically to the external BA mode. Should you
wish to operate the internal BA’s in a redundant configuration,
you must switch back to the internal BA mode.
6.2. Activating individual modules

After you have set the cycling times for the three RE. 316*4
units, the next thing is to configure the modules in the RE. 316*4
units that are processed by all of them as described in Sections
3.2 and 3.3.
The entire 500RIO11 configuration (input voltage, contact bounce
time etc.) can be saved and retrieved again.
6.3. Checking the system

After completing the configuration of the system, run it and check
the PC card and the modules connected to the process bus
using the diagnostic function (see Section 3.4).
52
7. PROTECTION FUNCTION “ANALOG RIO TRIG”
7.1. Application
Supervision of the analogue input signals on the 500AXM11
module.
7.2. Features
• Supervises an analogue input signal on a 500AXM11 module
• Displays percentages for voltage and current signals
• Displays °C for temperature sensors
• Supervision of maximum or minimum limits
7.3. Inputs and outputs

I. C.t./v.t. inputs:
• Current, voltage and temperature signals generated by the
500AXM11 module.
II. Binary outputs:
• Blocking
III. Binary inputs:
• Start
• Trip
• Alarm
IV. Measurements:
• Percentages for voltage and current signals;
°C for temperature sensor signals
Note:
The unit applicable for a measurement and the settings of the
alarm and tripping parameters depend on the type that has been
set for the analogue input on the 500AXM11 module. Where a
current or voltage input is concerned the value is displayed as a
percentage and where a temperature sensor is concerned in
degrees Celsius.
53
7.4. Analogue RIO trigger function settings – Analog RIO Trig

Submenu “Select Analog Input”
MWAInp MWAInp 0
Submenu “Edit Settings”

ParSet 4..1 P1 (Select)

Trip 00000000
1) 1) 1)
AlarmLevel % / °C 50.0 -100.0 / -50.0 100.0 / 300.0 0.1
1) 1) 1)
TripLevel % / °C 80.0 -100.0 / -50.0 100.0 / 300.0 0.1
MinMax Max (Select)
Delay s 10.0 0.0 60.0 0.1
ResetDelay s 10.0 0.0 60.0 0.1
BlockInp BinaryAddr F
Trip SignalAddr ER
Start SignalAddr ER
Alarm SignalAddr ER
Blocked SignalAddr ER
1)
The unit of this parameter depends on the type set for the input. For current
and voltage signals at inputs on the 500AXM11 the value is displayed as a
percentage (%), while the value of a signal from a temperature feeler is
displayed in degrees Celsius (°C).
Explanation of parameters:
MWAInp
defines the input signal from the 500AXM11.
ParSet 4..1
parameter for determining in which set of parameters a par-
ticular function is active.
Trip
defines the tripping channel activated by the tripping O/P of
the function (matrix tripping logic).
54
AlarmLevel
set operating value for giving alarm.
TripLevel
set operating value of the starting signal or tripping command.
MinMax
defines the operating mode. The following settings are possible:
− Max: Alarm, start and trip when the input exceeds the set
limit.
− Min: Alarm, start and trip when the input falls below the
set limit.
Delay
Time between the function picking up and tripping.
ResetDelay
Time between the input resuming a value lower than max.
respectively higher than min. and the resetting of the starting
signal or tripping command.
BlockInp
Binary address of the blocking input.
(F→FALSE, T→TRUE, binary input or output of a protection
function)
Trip
Tripping signal.
Start
Pick-up signal.
Alarm
Output for signalling operation of the alarm.
Blocked
Output for signalling that the function is blocked.
Operation of the function is blocked when
• the blocking signal input is activated
• the corresponding 500AXM11 is not responding
• the supply for the sensor connected to the input is short-
circuited
• an open-circuit of the leads connected to the input has
been detected.
55
7.5. Setting instructions
7.5.1. Hardware requirements

The function runs on all RE. 316*4 and RE. 216 units providing
they are connected to a process bus with PC card and at least
one 500AXM11 as signal source for the analogue input.
7.5.2. Configuration
The computing load on the processor (value used by the HMI
program) is 2%.
Several instances of the function may be configured. Where this
is the case and multiple instances are connected to the same
input, the computing load is increased by the amount required
for the first instance.
The function is one of the basic functions and available for all
software keys.
It is executed at the lowest repetition rate.
There is only one submenu, i.e. “Select Analog Input”, when the
function is configured for the first time, but two submenus, i.e.
“Select Analog Input” and “Edit Settings”, if already selected or
when editing an existing instance of the function.
56
8. INSTRUCTIONS FOR CONNECTING TO THE

INTERBAY BUS
8.1. Analog RIO Trig 73

Basic channel No.: 14
Overview of parameters:
Addres Access Text Units Default Min. Max. Step
14S2 R CPU No. <Select> CPU 1 1 2 1
CPU1 1
CPU2 2
14S4 R ParSet4..1 <Select> P1 00000010B 00011110B
14S5 R Trip 01-08 00000000B
14S6 R Trip 09-16 00000000B
14S7 R Trip 17-24 00000000B
14S8 R Trip 25-32 00000000B
1)
14S9 R AlarmLevel % / °C 50.0 -100.0 300.0 0.1
1)
14S10 R TripLevel % / °C 80.0 -100.0 300.0 0.1
14S11 R MinMax <Select> Max 0 1 1
Max 0
Min 1
14S12 R Delay s 10.00 0.0 60.0 0.1
14S13 R ResetDelay s 10.00 0.0 60.0 0.1
Measurements
Address Access Text Dec.
1)
14V1 R % / °C 2/1
Tripping measurements
Address Access Text Dec.

1)
14Q1 R % / °C 2/1
1)
The unit of this parameter and its measurement depend on the type of input
signal that has been set. For current and voltage signals at inputs on the
500AXM11 the value is displayed as a percentage (%), while the value of a
signal from a temperature feeler is displayed in degrees Celsius (°C).
57
Event list
Event No. Cause Event mask Release code Status

14E1 Trip Set V155 1 14I1
14E2 Dito Reset V155 2
14E3 Start Set V155 4 14I2
14E5 Alarm Set V155 16 14I3
14E7 Blocked Set V155 64 14I4
8.2. Analogue input/output signals

The function 9 (IBB I/O) offers measured values. The number of
measured values is limited to 64.
Address Access Text Format
9V1 R IBBMW 1 Long integer

9Vn R IBBMW n Long integer
9V64 R IBBMW 64 Long integer
8.3. Binary input/output signals

16 signals from 2 consecutive input/output modules are
transferred per channel.
Channel Inputs Outputs Events Module addresses
153 I1 – I32 O1 – O32 E1 – E64 1 and 2

154 I1 – I32 O1 – O32 E1 – E64 3 and 4
155 I1 – I32 O1 – O32 E1 – E64 5 and 6
156 I1 – I32 O1 – O32 E1 – E64 7 and 8

157 I1 – I32 O1 – O32 E1 – E64 9 and 10
158 I1 – I32 O1 – O32 E1 – E64 11 and 12
159 I1 – I32 O1 – O32 E1 – E64 13 and 14
160 I1 – I32 O1 – O32 E1 – E64 15 and 16

161 I1 – I32 O1 – O32 E1 – E64 17 and 18
162 I1 – I32 O1 – O32 E1 – E64 19 and 20
58
Channel Inputs Outputs Events Module addresses
163 I1 – I32 O1 – O32 E1 – E64 21 and 22

164 I1 – I32 O1 – O32 E1 – E64 23 and 24
165 I1 – I32 O1 – O32 E1 – E64 25 and 26

166 I1 – I32 O1 – O32 E1 – E64 27 and 28
167 I1 – I32 O1 – O32 E1 – E64 29 and 30
168 I1 – I32 O1 – O32 E1 – E64 31 and 32
169 I1 – I32 O1 – O32 E1 – E64 33 and 34

170 I1 – I32 O1 – O32 E1 – E64 35 and 36
171 I1 – I32 O1 – O32 E1 – E64 37 and 38
172 I1 – I32 O1 – O32 E1 – E64 39 and 40
173 I1 – I32 O1 – O32 E1 – E64 41 and 42

174 I1 – I32 O1 – O32 E1 – E64 43 and 44
175 I1 – I32 O1 – O32 E1 – E64 45 and 46
176 I1 – I32 O1 – O32 E1 – E64 47 and 48
177 I1 – I32 O1 – O32 E1 – E64 49 and 50

178 I1 – I32 O1 – O32 E1 – E64 51 and 52
179 I1 – I32 O1 – O32 E1 – E64 53 and 54
180 I1 – I32 O1 – O32 E1 – E64 55 and 56
181 I1 – I32 O1 – O32 E1 – E64 57 and 58

182 I1 – I32 O1 – O32 E1 – E64 59 and 60
183 I1 – I32 O1 – O32 E1 – E64 61 and 62
184 I1 – I32 O1 – O32 E1 – E64 63 and 64
185 I1 – I32 O1 – O32 E1 – E64 65 and 66

186 I1 – I32 O1 – O32 E1 – E64 67 and 68
187 I1 – I32 O1 – O32 E1 – E64 69 and 70
188 I1 – I32 O1 – O32 E1 – E64 71 and 72
189 I1 – I32 O1 – O32 E1 – E64 73 and 74

190 I1 – I32 O1 – O32 E1 – E64 75 and 76
191 I1 – I32 O1 – O32 E1 – E64 77 and 78
192 I1 – I32 O1 – O32 E1 – E64 79 and 80
59
The binary input/output modules 500BIM11 and 500BOM11/12

provide information on the statuses of their inputs and outputs
and the 500BIM11 also on events.
In the case of the analogue input/output module 500AXM11 the
statuses and events of the supervision signals are made available
(see Section 4.8).
8.3.1. Supervision signals on the analogue input/output modules

The allocation of supervisions signals is illustrated by an
example for channel 153.
Module address Input Cause Event Event No.
1 153I1 Broken wire Out-Channel 1 On 153E1

Off 153E2
153I2 Broken wire Out-Channel 2 On 153E3

Off 153E4
153I3 --- 153E5
153E6
153I4 Update missing On 153E7

Channel 1
Off 153E8
153I5 Update missing On 153E9
Channel 2
Off 153E10
153I6 Supply short-circuit (Ch1) On 153E11

Off 153E12
Off 153E14

Off 153E16
Off 153E18
153I10 Update missing Red.Chan 1 On 153E19

Off 153E20
153I11 Update missing Red.Chan 2 On 153E21
Off 153E22
153I12 --- 153E23

153E24
60
1 153I13 Broken wire In-Channel 1 On 153E25

Off 153E26
153I14 Broken wire In-Channel 2 On 153E27

Off 153E28
Off 153E30

Off 153E32
2 153I17 Broken wire Out-Channel 1 On 153E33
Off 153E34
153I18 Broken wire Out-Channel 2 On 153E35

Off 153E36
… …
…

Off 153E64
8.3.2. Input/output module status information

The statuses and module status events are made available (see
Section 4.7).
Channel Inputs Events Module addresses
193 I1 – I32 E1 – E64 1 to 8

194 I1 – I32 E1 – E64 9 to 16
195 I1 – I32 E1 – E64 17 to 24
196 I1 – I32 E1 – E64 25 to 32

197 I1 – I32 E1 – E64 33 to 40
198 I1 – I32 E1 – E64 41 to 48
199 I1 – I32 E1 – E64 49 to 56
200 I1 – I32 E1 – E64 57 to 64

201 I1 – I32 E1 – E64 65 to 72
202 I1 – I32 E1 – E64 73 to 80
61
The allocation of the module status information is illustrated by

an example for channel 193.
1 193I1 Device connected On 193E1

Off 193E2
193I2 Line A faulty On 193E3

Off 193E4
193I3 Line B faulty On 193E5
Off 193E6
193I4 --- 193E7

193E8
Off 193E10

Off 193E12
Off 193E14
193I8 --- On 193E15

Off 193E16
... … …
…

Off 193E58
Off 193E60

Off 193E62
193I32 --- On 193E63
Off 193E64
The following formulas generally apply:

Channel No. = (Module address– 1) DIV 8 + 193
Input No. = ((Module address – 1) MOD 8) * 4 + I
Event No. = ((Module address – 1) MOD 8) * 8 + E + K
62
where: I = 1, E = 1 for “Connect device”

I = 2, E = 3 for “Line A failure”
I = 3, E = 5 for “Line B failure”
K = 0 for “On”
K = 1 for “Off”
8.3.3. Event masks for binary inputs

Event masks (exclusion from being recorded as an event) apply
to both binary input signals, supervision signals and module
status information.
Input Event Event No. Mask Release code
I1 On E1 V155 1
Off E2 V155 2
I2 On E3 V155 4
Off E4 V155 8
I3 On E5 V155 16
Off E6 V155 32
I4 On E7 V155 64
Off E8 V155 128
I5 On E9 V155 256
Off E10 V155 512
I6 On E11 V155 1024

Off E12 V155 2048
I7 On E13 V155 4096
Off E14 V155 8192
I8 On E15 V155 16384

Off E16 V155 32768
I9 On E17 V156 1
Off E18 V156 2
I10 On E19 V156 4

Off E20 V156 8
I11 On E21 V156 16
Off E22 V156 32
I12 On E23 V156 64

Off E24 V156 128
63
I13 On E25 V156 256

Off E26 V156 512
I14 On E27 V156 1024

Off E28 V156 2048
I15 On E29 V156 4096
Off E30 V156 8192
I16 On E31 V156 16384

Off E32 V156 32768
I17 On E33 V157 1
Off E34 V157 2
I18 On E35 V157 4

Off E36 V157 8
I19 On E37 V157 16
Off E38 V157 32
I20 On E39 V157 64

Off E40 V157 128
I21 On E41 V157 256
Off E42 V157 512
I22 On E43 V157 1024

Off E44 V157 2048
I23 On E45 V157 4096
Off E46 V157 8192
I24 On E47 V157 16348

Off E48 V157 32768
I25 On E49 V158 1
Off E50 V158 2
I26 On E51 V158 4

Off E52 V158 8
I27 On E53 V158 16
Off E54 V158 32
I28 On E55 V158 64

Off E56 V158 128
64
I29 On E57 V158 256

Off E58 V158 512
I30 On E59 V158 1024

Off E60 V158 2048
I31 On E61 V158 4096
Off E62 V158 8192
I32 On E63 V158 16348

Off E64 V158 327680
In the case of double signals, the significance of the events

changes as illustrated by the following example for inputs 2 and
3 which are configured as a double signal.
Input Event No. Significance Significance for a
double signal
I2 E3 On 1-0
E4 Off 0-1
I3 E5 On 0-0
E6 Off 1-1
65
Daten löschen
Notification Form for Errors in this Document
Dear User,
We are always endeavouring to improve the quality of our 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 / 733/3
CH-5401 Baden
Switzerland
Telefax +41 56 205 28 00
---------------------------------------------------------------------------------------------------------------
Concerns publication: 1MRB520192-Uen (RIO 580)
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, please 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.

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.

Software Support Group NSS
Haselstrasse 16/122
CH-5401 Baden
Telefax +41 56 205 86 57
e-mail: SA-LEC-Support@ch.abb.com
---------------------------------------------------------------------------------------------------------------
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 contained in
these operating instructions are adhered to.
It is scarcely possible for the instructions to cover every eventuality 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 performed 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 Ltd ABB Automation Products AB ABB Transmit Oy ABB Power T&D Co.
Haselstrasse 16/122 S-72171 Västerås, Sweden Relays and Network Control 4300 Coral Ridge Drive
CH-5401 Baden/Switzerland Phone +46 21 32 13 00 P.O.Box 699 Coral Springs, Fla. 33065
Phone +41 56 205 77 44 Fax +46 21 14 69 18 FIN -65101 Vaasa, Finland USA
Fax +41 56 205 55 77 Phone +358 10 224 000 Phone +1 954 752 6700 ext. 2461
www.abb.com/substationautomation Fax +358 10 224 1094 Fax +1 954 345 5329
Printed in Switzerland (0109-0XXX-0)

Remote Input / Output System

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Remote Input / Output System

Transféré par

Droits d'auteur :

Formats disponibles

RIO 580 1MRB520192-Uen

Edition July 2001

Remote Input / Output System

Valid for sw-versions:

Process bus – PC card: V3.00

2. INSTALLATION AND COMMISSIONING ...................................8

3. CONFIGURING THE MVB PROCESS BUS .............................26

4. DIAGNOSIS, SUPERVISION AND MAINTENANCE ................41

4.5. PBI module status .....................................................................46

5. DETERMINING THE MAXIMUM POSSIBLE SYSTEM SIZE ...51

6. CONFIGURATION PROCEDURE ............................................52

7. PROTECTION FUNCTION “ANALOG RIO TRIG” ....................53

8. INSTRUCTIONS FOR CONNECTING TO

1.2. Abbreviations and definitions

500RIO11 remote input/output unit

1.3. Other relevant documents

[4] Data Sheet

1.4. Functional description

1.5. Possible means of exchanging data

opt. opt. RS485

RIO cluster installed,

500RIO11 500RIO11 500RIO

Process connections RIO cluster installed,

Fig. 1.1 Process bus with one RE. 316*4 unit

REC 316*4 REC 316*4

opt. opt. RS485

RIO cluster installed,

500RIO11 500RIO11 500RIO11

• • • • • • • • • RIO cluster installed,

2. INSTALLATION AND COMMISSIONING

2.1. Installing the PC card

Top when installed

Fig. 2.1 MVB PC card

Do not insert or remove the PC card while the auxiliary

• Cover unused optical channels.

• Do not plug in or unplug optical cables while the auxiliary

• Handle the PC card carefully.

• The PC card in the RE. 216 or RE. 316*4 must not be

In a non-redundant configuration, the PC card uses line A and in

Fig. 2.2 Arrangement of the PC card slots on the back of the

Fig. 2.3 Arrangement of the PC card slots on the back of the

In order to use two PC cards in a RE. 216 unit, a second

2.2. Interconnecting cables

Input/output module 500RIO11

Basic module: supply Optical connectors RS485-connectors

ABB ABB Power Automation

Slot 3: Basic module with supply and communication interfaces

Fig. 2.4 Module slots on a 500RIO11

PBI modules are equipped with an electrical connector and can

2.2.1. Bus termination

Optical Dummy load

500RIO11 500RIO11 500RIO11

Fig. 2.5 Bus terminations for units connected by a daisy

Where individual 500RIO11 units are operated in a distributed

Optical Dummy load

500RIO11 500RIO11 500RIO11

Fig. 2.6 Bus terminations for a distributed configuration

2.2.2. Electrical bus length

2.3. Entering the module addresses

The device address for the module in slot 1 is set as a binary

The following addresses are assigned to the active modules

500AXM11, 500BIM11 DIP switch (S1) MVB data set number

500AXM11, 500BIM11 DIP switch (S1) MVB data set number

500AXM11, 500BIM11 DIP switch (S1) MVB data set number

REC 3164 REC 3164