Remote Input / Output System

8/14/2019 Remote Input / Output System

1/76

p

RIO 580

Remote Input / Output System

Operating Instructions

1MRB520192-UenEdition July 2001

Dezentrale Montage

500RER11

Feldgert

PC-Card

LWL

500RIO11 500RIO11 500RIO11

Vorort-Steuerschrank

Steuerkasten

LWL

500RER11

Bay unit

PC card

Fibre opticcable

500RIO11 500RIO11 500RIO11

Local control cubicle

Control housing

Fibre opticcable


2/76

1997 ABB Power Automation LtdBaden/Switzerland

4th Edition

Valid for sw-versions:

Process bus PC card: V3.00

500 BIM11: V3.00RE. 216 / RE. 316*4: V6.2

All rights with respect to this document, including applications for patent andregistration 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 itsTechnical Description or Operating Instructions.


3/76

RIO 580 1MRB520192-Uen / Rev. C ABB Power Automation Ltd

1

Contents

1. INTRODUCTION.........................................................................31.1. General .......................................................................................31.2. Abbreviations and definitions ......................................................3

1.3. Other relevant documents...........................................................51.4. Functional description .................................................................51.5. Possible means of exchanging data............................................61.5.1. Process bus with one RE. 216, RE. 316*4 unit...........................61.5.2. Process bus with two or more RE. 216, RE. 316*4 units ............7

2. INSTALLATION AND COMMISSIONING ...................................82.1. Installing the PC card ..................................................................82.2. Interconnecting cables ..............................................................102.2.1. Bus termination .........................................................................11

2.2.2. Electrical bus length ..................................................................122.3. Entering the module addresses.................................................132.4. Plug-in jumper settings..............................................................202.4.1. Binary input module 500BIM11.................................................202.4.2. Binary output module 500BOM11/12 ........................................222.4.3. Analogue input/output module 500AXM11................................232.5. Commissioning..........................................................................252.6. Limitations.................................................................................25

3. CONFIGURING THE MVB PROCESS BUS.............................263.1. Configuring the bus administrator and cycling times

(MVB-BA parameters)...............................................................263.2. Configuring the binary input/output modules

(MVB-RIO parameters) .............................................................293.3. Configuring interlocking parameters (MVB-ITL parameters) .....323.4. Configuring 500AXM11 modules...............................................333.5. Entering comments ...................................................................38

4. DIAGNOSIS, SUPERVISION AND MAINTENANCE ................414.1. PC card information ..................................................................414.2. PC card statuses and error messages ......................................41

4.2.1. PC card operating modes .........................................................414.2.2. PC card status...........................................................................424.2.3. Error messages.........................................................................424.2.4. PC card type .............................................................................444.2.5. PC card SW version..................................................................444.2.6. PC card counter ........................................................................444.2.7. Redundant bus administrators ..................................................444.3. RIO, PBI and ITL information....................................................444.4. RIO module status ....................................................................45


4/76

ABB Power Automation Ltd RIO 580 1MRB520192-Uen / Rev. C

2

4.5. PBI module status .....................................................................464.6. Event list messages ..................................................................474.7. Significance of the module status information...........................474.8. Supervision functions in the 500AXM11 module.......................474.9. Display of measured variables..................................................494.10. Test functions / fault-finding ......................................................494.11. Replacing modules....................................................................494.12. Signals on the input/output unit 500RIO11................................494.12.1. Basic module 500RBM11..........................................................494.12.2. Binary output module 500BOM11/12 ........................................494.12.3. Binary input module 500BIM11 .................................................494.12.4. Analogue input/output module 500AXM11................................504.13. Signals on the star coupler unit 500RER11 ..............................504.13.1. Basic module 500RBM11..........................................................504.13.2. Star coupler module 500SCM11...............................................50

5. DETERMINING THE MAXIMUM POSSIBLE SYSTEM SIZE ...515.1. With internal bus administrator..................................................515.2. With external bus administrator.................................................51

6. CONFIGURATION PROCEDURE ............................................526.1. Setting the cycling times for the process bus ............................526.2. Activating individual modules....................................................526.3. Checking the system.................................................................52

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

7.1. Application ................................................................................537.2. Features....................................................................................537.3. Inputs and outputs.....................................................................537.4. Analogue RIO trigger function settings Analog RIO Trig........547.5. Setting instructions....................................................................567.5.1. Hardware requirements.............................................................567.5.2. Configuration.............................................................................56

8. INSTRUCTIONS FOR CONNECTING TOTHE INTERBAY BUS................................................................57

8.1. Analog RIO Trig 73 ...................................................................578.2. Analogue input/output signals ...................................................588.3. Binary input/output signals........................................................588.3.1. Supervision signals on the analogue input/output modules ......608.3.2. Input/output module status information .....................................618.3.3. Event masks for binary inputs ...................................................63


5/76


3

1. INTRODUCTION

1.1. General

The RE. 216, RE. 316*4 unit is coupled to the process bus by anMVB PC card which performs the slave/node and bus adminis-trator functions.

The following remote binary input/output modules and telegramsare 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 HighVoltage Technologies Ltd., process bus).

Both the modules and the bus administrator can be configuredvia the HMI of the RE. 216 or RE. 316*4.

RE. 216 units with a 216VC62 and RE. 316*4 units with a316VC61(revision F onwards), 316VC61a or 316VC61b can beconnected to an MVB process bus.

1.2. Abbreviations and definitions

RE. 216/bay unit PC card host: for protection cubicle orcompact version, . standing for eitherC or G.

RE. 316*4/bay unit PC card host: RE. 316*4 unit, . standingfor either C, G, L or T.

RE. .16 RE. 216 / RE. 316*4

PC card personal computer card (PCC), formerlyPCMCIA.

MVB Multifunction Vehicle Bus according toIEC 1375

BA bus administrator, see [3]

Slave-Node see [3]

MPL interface software

Device address see [3]

RIO 580 remote input/output system


6/76


4

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 for500RIO11

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)data

64 Bit telegram (48 Bit useful data plus16 Bit status information) for exchangingdata between the bay units and theprocess bus

PBI Process Bus Interface HACE 437065

PBA software process bus coupling software

Bus termination prevents reflected signals on the electricalbus

Daisy chain series connection of several units

HMI human/machine interface,interface between the PC andan 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, )


7/76


5

1.3. Other relevant documents

[1] Only for PBI modules: Hansjrg hler: Process BusInterface HACE 400008 (ABB High Voltage TechnologiesLtd.)

[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 SheetRIO500 Remote Input/Output System 1MRB520176-Ben

1.4. Functional description

When the power is switched on, the RE. .16 initialises the MVBPC card and various subsystems are started in accordance withthe configuration. A reset signal is then transmitted to all the500BIM11 modules by the RE. .16 units with device address 1 or2 and the version of the software is read out. Whenever a500BIM11 module is switched on or reset, it requests itsconfiguration data (e.g. input voltage, contact bounce time etc.)from the RE. .16 (PC card) with device address 1 or 2. Once thePC card has started, it reads the data from the 500BIM11 and500AXM11 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 500AXM11modules.

The PC card monitors the operating condition of every module.Should a module fail, an event is recorded in the event list andsignalled by the diagnostic function.

The input/output, synchronisation and diagnostic data aretransferred cyclically via the process bus, while events,configuration data and commands are transferred as the needarises.


8/76


6

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) isconnected to the MVB. The bus administrator software and the

PBA software are installed on the MVB PC card and areaccessible using the HMI. The bus administrator can also runexternally. 500RIO11 input data can be read and 500RIO11output data transferred back to the outputs via the MVB PCC.

Star coupler500RER11

opt.

MVB process bus

Interbay bus(LON / MVB / SPA etc.)

Control unit REC 316*4

500RIO11 500RIO500RIO11

RS485

RS485

opt.

REC 316*4

PBA +

BA

IBBinterface

el.opt.

500RIO11 500RIO

RS485

Process connections

RIO cluster installed,for example, in the

hinged frame

PC card

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.


9/76


7

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 administratorthat cyclically polls all the addresses on the bus or a bay unitusing 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 redundantconfiguration.

PC card

Star coupler500RER11

500RIO11 500RIO11

opt.


remote cubicle

MVB process bus

Interbay bus(LON / MVB / SPA etc.)

Control unit REC 316*4

500RIO11 500RIO11500RIO11

RS485

RS485opt.

REC 316*4

PBA+BA

IBBinterface

el.opt.

Process connections

REC 316*4

PBA+BA

el.opt. PC card

Process connections

IBBinterface


hinged frameRS485

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 controlthe binaryoutput modules and only two the analogue outputmodules.


10/76


8

2. INSTALLATION AND COMMISSIONING

2.1. Installing the PC card

PC card dimensions and markings may vary from those givenbelow (Fig. 2.1).

Top when installed

Fig. 2.1 MVB PC card


11/76


9

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 auxiliarysupply is switched on.

Handle the PC card carefully.

The PC card in the RE. 216 or RE. 316*4 must not beoperated without the holder supplied.

In a non-redundant configuration, the PC card uses line A and ina redundant configuration lines A and B.

Each RE. 316*4 has four PCMCIA slots (Type 2). The mountingsupports can however support only two MVB PCCs to be pluggedinto the 316VC61a/b (slots A and B). If a LON, IEC 60870-5-103or SPA bus is in use, then only slot B can be used for theprocess bus. The slot where the PCC is located must be set inthe configuration data with the HMI.

Slot A

Slot D Slot B

Slot C

Fig. 2.2 Arrangement of the PC card slots on the back of the316VC61a/b module


12/76


10

Each RE. 216 has two PCMCIA slots (Type 2) in a RE. 216. Themounting support can however support only one MVB PCC to beplugged into the 216VC62a. The slot where the PCC is locatedmust 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 the216VC62a 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 isconnected to the second 216VC62a module.

2.2. Interconnecting cables

An optical fibre cable with a 62.5 m diameter core is required toconnect the PC card to a bus or star coupler or the input/outputunits.

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 thecard must be connected to the optical input RX on the starcoupler and vice versa.

500RIO11 modules are equipped with one redundant opticalconnector and two redundant electrical connectors can be usedto interconnect several 500RIO11 modules.

RS485 cable is used to electrically connect up to two 500RER11star couplers and up to ten 500RIO11 input/output units (see[4]).

If a 500RER11 star coupler is used in conjunction with MVB lineB, the electrical RS485 bus must not be connected to anotherstar coupler operating on MVB line A.


13/76


11

Fig. 2.4 Module slots on a 500RIO11

PBI modules are equipped with an electrical connector and canoptionally be supplied with an optical connector.

2.2.1. Bus termination

Where several 500RIO11 units are connected via an RS485cable, the two ends must be appropriately terminated withdummy loads.

Bayunit

PC card

500RIO11 500RIO11

Opticalfibre

Input/output unit

500RIO11

Local control cubicle

RS485

Dummy load

HEST 985001 PP

Fig. 2.5 Bus terminations for units connected by a daisychain

Basic module: supply

ABB ABB Power AutomationDC1 DC2 RxA TxA RxB TxB Y1 Y2

Address

1

2

15

16

2 16

1 15

A

C D

B

1 15 151

1 115 15

Slot 1

Slot 2

Slot 3

Input/output module 500RIO11

Module slots

Slot 3: Basic module with supply and communication interfacesSlot 1 und 2: Input/output modules

Optical connectors RS485-connectors


14/76


12

Where individual 500RIO11 units are operated in a distributedconfiguration, each must be fitted with two bus dummy loads.

HEST 985002 PP

Vorortsteuerschrank

PC card

500RIO11 500RIO11 500RIO11

Control box

Bay unit

Opticalfibre

Dummy load

500RER11

Opticalfibre

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 notexceed 20 m.


15/76


13

2.3. Entering the module addresses

A unique device address has to be configured for every modulebefore the input/output modules can operate in conjunction withthe MVB process bus. The addresses are set on the DIPswitches on the front of each device.

Caution:

500BIM11 modules only read their address once whenthe auxiliary supply is switched on.

500BIM11 modules only read the configuration (BIMsoftware 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 deviceaddress (extract from drawing 1MRB400242)

The device address for the module in slot 1 is set as a binarynumber on DIP switches 18 (Table 2.1). DIP switch 1 does notnormally perform any function. Bit 1 of the device address isdetermined 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 deviceaddresses can be set. Only in exceptions (large number of500RIO11 modules or only one BIM, BOM or AXM) is itnecessary to set even device addresses.

Note: A DIP switch is ON when it is up (towards the Bitnumber) and OFF when it is down.

Refer to the document [1] for how to set the address on PBImodules.


16/76


14

The following addresses are assigned to the active modulesusing the HMI. The second column is used when commissioningand the third column is utilised for an external bus administrator.

The grey DIP switch is needed when only one module per500RIO11 is fitted. It must be in the OFF position when two

modules are installed in each 500RIO11.

500AXM11, 500BIM11

or 500BOM11/12

device addresses

DIP switch (S1)

settings on the

500RIO11

MVB data set number

and size

1 1 8 ONOFF

1024 and 1024 + data setoffset (16 Bit)

2 1040 and 1040 + data setoffset (16 Bit)

3

1056 and 1056 + data set

offset (16 Bit)4 1072 and 1072 + data set

offset (16 Bit)
















17/76


15

500AXM11, 500BIM11

or 500BOM11/12

device addresses

DIP switch (S1)

settings on the

500RIO11

MVB data set number

and size


20
























18/76


16

500AXM11, 500BIM11

or 500BOM11/12

device addresses

DIP switch (S1)

settings on the

500RIO11

MVB data set number

and size


43
























19/76


17

Interlocking telegram

number

- MVB data set 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 BAsupervison

- 1 ... 63 (16 Bits) max. 4data sets

PBI device addresses DIP switch (S1)

settings on the PBI

MVB data set number

and size1 2128 (32 Bit), 2136 (all

others 16 Bit), 2137,2138, 2140

2 2144 (32 Bit), 2152 (allothers 16 Bit), 2153, 21542156

3 2160 (32 Bit), 2168 (allothers 16 Bit), 2169,2170, 2172


...


Table 2.1 Setting the device addresses for the modules


20/76


18

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(BOM number + 63) * 16 + 9 (data set offset = 9)

Output data, Port A(BOM number + 63) * 16 + 10 (data set offset = 10)

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(AXM number + 63) * 16 + 5 (data set offset = 5)

Output data for Channel 1 Port 8(AXM number + 63) * 16 + 8 (data set offset = 8)

Output data for Channel 2 Port 9(AXM number + 63) * 16 + 9 (data set offset = 9)

Setting data for a communication failure for Channel 1 Port 10(AXM number + 63) * 16 + 10 (data set offset = 10)

Setting data for a communication failure for Channel 2 Port 11(AXM number + 63) * 16 + 11 (data set offset = 11)

Redundant output data for Channel 1 Port 14(AXM number + 63) * 16 + 14 (data set offset = 14)

Redundant output data for Channel 2 Port 15(AXM number + 63) * 16 + 15 (data set offset = 15)


21/76


19

PBI:

(PBI number * 16) + 2112 + data set offset = 0, 8, 9, A or C)

ITL:

(ITL telegram number + 2063)


22/76


20

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 themodule with larger flash EEPROMs and must be left in itsdefault position X700-701.


23/76


21

Jumper X703-X704 protects the boot block of the flashEEPROMs and must not be fitted (default). It is only everinserted for programming, i.e. for deleting the boot block, whichis necessary when updating the SiMon supervision program. Itmust be removed immediately afterwards.

Jumper X400-403 is for setting Bit 1 of the device address. Itsposition depends on the slot the module occupies in the500RIO11 unit.

Fig. 2.9 Plug-in jumpers X401-403 on PCB 500BIM11

Number of

modules fitted

Slot Jumper Device address

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) areused. The third position (X401-X403) is only needed inexceptions (large number of 500RIO11 units with only onemodule). On no account may the jumper be in position X401-X403 when two modules are inserted in one 500RIO11 unit.


24/76


22

2.4.2. Binary output module 500BOM11/12

The binary output module 500BOM11/12 has only one plug-injumper.

Jumper

Fig. 2.10 Plug-in jumper on PCB 500BOM11/12

Jumper X301-303 is for setting Bit 1 of the device address. Its

position depends on the slot the module occupies in the500RIO11 unit(see Table 2.3).

Fig. 2.11 Plug-in jumpers X301-303 on PCB 500BOM11/12


25/76


23

Number of

modules fitted

Slot Jumper Device address

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) areused. The third position (X301-X303) is only needed inexceptions (large number of 500RIO11 units with only onemodule). On no account may the jumper be in this position whentwo modules are inserted in one 500RIO11 unit.

2.4.3. Analogue input/output module 500AXM11

The analogue input/output module 500AXM11 has five plug-injumpers.

Fig. 2.12 Plug-in jumpers on PCB 500AXM11

Jumper X304-306 is for setting Bit 1 of the device address. Itsposition depends on the slot the module occupies in the500RIO11 unit (see Table 2.4).


26/76


24

Fig. 2.13 Plug-in jumpers X304-306 on PCB 500AXM11

Modules

fittedSlot Jumper

Device address

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) areused. The third position (X305-X306) is only needed inexceptions (large number of 500RIO11 units with only onemodule). On no account may the jumper be in this position whentwo modules are inserted in one 500RIO11 unit.

There is a plug-in jumper for each of the four input channels thathas to be inserted when using a Pt1000 or Ni1000 temperaturefeeler.

Sensor type Channel 1 Channel 2 Channel 3 Channel 4

Pt100, Ni100 none none none none

Pt250, Ni250 none none none none

Pt1000,Ni1000

X700-701 X1100-1101 X1500-1501 X1900-1901

Table 2.5 Plug-in jumpers X700-1901 on PCB 500AXM11


27/76


25

2.5. Commissioning

Take care during commissioning that the number of modulesactivated in the HMI is not higher than the number actuallyconnected to the process bus. Superfluous active modulesunnecessarily load the PCC software.

The HMI diagnostic function provides facility for checkingwhether the PC card has started correctly (PC_Card_Status:Ready, PC_Card_Error: No error) and that all the modulesconfigured are actually connected(see Section 4).

Data may be lost if the electrical bus is not correctly terminatedwith 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 onwardsPC card process bus: V3.00 onwards500BIM11 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 unitand 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 previouslyconfigured by the HMI.

6) 500BIM11 modules from Version 2.04 onwards request theirconfiguration from RE. .16 units with device address 1 or 2.

7) 500BIM11 modules (software Version 2.04 onwards) sendtheir events to the die RE. .16 with the device address 1 to 3.

8) Time synchronisation of the MVB process bus is performedby the PC card Version 2.03 in RE. .16 units with deviceaddresses 1 and 2 in a redundant configuration.


28/76


26

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 variousmodules (see Fig. 3.1) and select the modules to be polled bythe bus administrator. The modules are in groups of eight, butnot all the modules in a group have to be activated. This menuitem also permits modules to be activated that should not beread by their own RE. .16, but by another RE. .16. Up to fourdifferent cycling times are supported.

Either an internal bus administrator (the PC card includes a busadministrator) 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 busadministrators (internal and external). For this purpose, thedevice addresses of the bus administrators have to be entered inthe RE. 216 or RE. 316*4HMI.

Internal bus administrator:

Select this menu item to set the module cycling times whenusing an internal bus administrator. It is also used for selectingthe modules to be connected to the process bus.

Every RE. 216 or RE. 316*4sends bus administrator diagnostictelegram to the first device address entered in the HMI. TheRE. 216 or RE. 316*4 units receive bus administrator diagnostictelegrams from all other device addresses entered. Where 0 isentered as the device address, diagnostic telegrams are neithertransmitted nor received.

External bus administrator:

The module cycling times also have to be set as configured onthe PCC when using an external bus administrator.


29/76


27

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 BAs and several RE. 216 or RE. 316*4unitsd) Several external BAs and several RE. 216 or RE. 316*4units

^__=m=^~=iob`PNSGQ=J=`=rb=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=====================================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.1 Configuring the cycling times and the busadministrators

Selecting the module on the bus administrator:

If the internal bus administrator is used, the bus administratorparameters must include the modules that are connected andthe associated ports to be controlled. As Fig. 3.2 shows, achoice can be made between a 500BIM11, the 500BOM11 portsto 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).


30/76


28

^__=m=^~=iob`PNSGQ=J=`=rb=ofl|_^Jm~~================================================p======ofl=akK==R===G==G======================================================================================================[==_fjJj==============lmp===============_fjJj============_ljWm=U==============obqrokLbkqbo======================================_ljWm=UIV==============================================================_ljWm=UV^==========

====================================================^ujW=eEUVF==============================================================^ujW=ep_===================================================================================================================================================================================================================================================================================================`=======================NS=================ofl=ORKKPO==================_MMMMMMMM=====================================`=======================NMOQ======================================KKK==========================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.2 Configuring the module and port for the internalbus administrator

Similarly, the HMI provides facility for determining whether thebus administrator just polls Port 8, Ports 8 and 9 or Ports 8, 9and A (=10) for the PBIs that are connected. This setting onlyapplies for internal bus administrators.

^__=m=^~=iob`PNSGQ=J=`=rb=m_f=_^Jm~~================================================p======m_f=akK==V===G==G=====================================================

=================================================[==m=U==============lmp===============m=U============m=U=~=V============obqrokLbkqbo======================================m=UIV=H=^=======================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================`=======================NMOQ===============m_f=NTKKOQ==================_MMMMMMMM=====================================`=======================NMOQ======================================KKK==========================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.3 Configuring a PBI port for the internal busadministrator

The bus administrator settings and cycling times are saved in afile called mbaXX.par that can be loaded in another RE. 216 orRE. 316*4 (only using the internal bus administrator). Insert thePB device address for XX.


31/76


29

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 everyRE. 216 or RE. 316*4 connected to the process bus. This is

entered for PB-DeviceAddress. Where the PB is just one opticalfibre cable (line A), RedundSupVis has to be set to none. Theredundant bus supervision functions has to be activated, on theother hand, where a redundant PB is installed. Either only_RIO,only_PBI or RIO and PBI has to be selected in accordancewith the modules connected. TimeSync determines whether therespective RE. .16 shall synchronise the 500BIM11 modules.Redundant time synchronisation by units with device addresses1 and 2 only makes sense if both are synchronised to the samereference source via the Interbay bus. The modules (500BIM11,

500BOM11/12, 500AXM11 and PBIs) that communicate with therespective RE. 216 or RE. 316*4 have to be selected via thismenu (see Fig. 3.4).

^__=m=^~=iob`PNSGQ=J=`=rb=c=m~~=============================================================================f__Lofl=`K=============G==G=========================================================================================================================m_Jm``Jp=================_=============================p============m_Ja^=============N===============================================ops================kps======================p============qp================================================p============oflLm_f==NKK=U==============_NMMMMMTU=====================~=E[MF=====

==oflLm_f==VKKNS==============_MMMMMMMM============oflLm_f=NTKKOQ==============_MMMMMMMM=====================================oflLm_f=ORKKPO==============_MMMMMMMM============oflLm_f=PPKKQM==============_MMMMMMMM==========N=O=P=Q=R=S=T=U===oflLm_f=QNKKQU==============_MMMMMMMM=========u===========u=u====oflLm_f=QVKKRS==============_MMMMMMMM============oflLm_f=RTKKSQ==============_MMMMMMMM=====================================m_f=SRKKTO==================_MMMMMMMM===================================KKK==========================================l=J=i=VSMM====p`pWilksSKO==sSKO

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 parameterDeviceType, its parameter settings appear in the dialogue.

In the case of 500BIM11 modules, there are settings for bouncefilter 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 or250 V).


32/76


30

^__=m=^~=iob`PNSGQ=J=`=rb=ofl=m~~=============================================================================ofl=m~~=akK==O===G==G==========================================================================================================================aq==================f=_fj=====================p============aqW===============Q=============================================fs~==================QU=s==========================p==========

==obqrokLbkqbo============================================================================================================================================================================================================================================================================================================================================================================================================================================================oflLm_f=QVKKRS==============_MMMMMMMM============oflLm_f=RTKKSQ==============_MMMMMMMM=====================================m_f=SRKKTO==================_MMMMMMMM===================================KKK==========================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.5 500BIM11 configuration parameters

An HMI entry has to be made for each 500BOM11/12 modulestating to which port (Port 8, Port 9 or Port A) the RE. .16 has tosend its data. A 500BOM11/12 module has three portsconnected to an OR gate (see Fig. 3.6).

^__=m=^~=iob`PNSGQ=J=`=rb=ofl=m~~================================================p======ofl=m~~=akK==V===G==G===========================================================================================[==m=U==================aq==================l=_lj============m=V==================lm==================m=U================m=^================

==obqrokLbkqbo===============================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================oflLm_f=QVKKRS==============_MMMMMMMM============oflLm_f=RTKKSQ==============_MMMMMMMM=====================================m_f=SRKKTO==================_MMMMMMMM===================================KKK==========================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.6 500BOM11/12 configuration

For a 500AXM11 it is also necessary to state whether theRE. .16 sets its outputs as the main (=active) or backup(=standby) device. The main device sends the data of outputchannels 1 and 2 via Ports 8 and 9, while the backup unit usesPorts E (=14) and F (=15). The 500AXM11 normally accepts thedata from Ports 8 and 9 and only when no data are receivedfrom them from Ports E and F(see Fig. 3.7).


33/76


31

^__=m=^~=iob`PNSGQ=J=`=rb=ofl=m~~================================================p======ofl=m~~=akK=ON===G==G===========================================================================================[==eEmUIVF============aq==================^ujJa============p~_EbIcF============lmp===============eEmUIVF==================================obqrokLbkqbo=======================================

==========================================================================================================================================================================================================================================================================================================================================================================================================================================================================oflLm_f=QVKKRS==============_MMMMMMMM============oflLm_f=RTKKSQ==============_MMMMMMMM=====================================m_f=SRKKTO==================_MMMMMMMM===================================KKK==========================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.7 500AXM11 configuration

Supplementary information such as contact bounce time, writingmode, print code and output port has to be entered for PBIs viathe HMI (see Fig. 3.8). A detailed description of the PBI modulesis to be found in document [1] Process Bus Interface HACE400008.

^__=m=^~=iob`PNSGQ=J=`=rb=ofl=m~~=============================================================================ofl=m~~=akK=PR===G==G========================================================================================================================

==aq==================m_fJa====================p============aqW===============U=============================================tjW==================m=U====================p============m`===================N===============================================lm==================m=U========================p============obqrokLbkqbo====================================================================================================================================================================================================================================================================================================oflLm_f=QVKKRS==============_MMMMMMMM============oflLm_f=RTKKSQ==============_MMMMMMMM=====================================m_f=SRKKTO==================_MMMMMMMM===================================KKK==========================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.8 Additional PBI configuration


34/76


35/76


33

3.4. Configuring 500AXM11 modules

Additional settings are possible via the HMI for the individualinputs and outputs on 500AXM11 modules. They are located inthe two submenus Edit Analog Inputs and Edit AnalogOutputs listed in the Edit Hardware Functions menu.

Edit Analog Inputs:

Submenu Edit Analog Inputs gives access to two furthersubmenus (see Fig. 3.10):

^__=m=^~=iob`PNSGQ=J=`=rj~=j=b==b=e~~=c===^~=f=====================================b=f=q==================b=`~=m~~======

====b=`=====================obqrok============================================================b=f__Lofl=`~====obqrok=====================================================l=J=i=VSMM====p`pWilksSKO==sSKO

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 InputType). Other parameters in the menu Edit Channel Parameterscan then be changed. All the parameters are listed andexplained 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)





36/76


34

Note: x denotes the device address of the 500AXM11 that hasbeen configured. Where there are several AXM modules, all therespective inputs are displayed and if no AXMs are configured,the parameter dialogue is empty. The number following the slashis that of the associated input channel to which the parameterapplies.

Submenu Edit Channel Parameters


Calibration R x/1 1.000 0.500 2.000 0.001

Offset R x/1 mA/V/C 1) 0.00 -20.00 2) 20.00 2) 0.01 2)

Calibration R x/2 1.000 0.500 2.000 0.001

Offset R x/2 mA/V/C 1) 0.00 -20.00 2) 20.00 2) 0.01 2)

Calibration R x/3 1.000 0.500 2.000 0.001

Offset R x/3 mA/V/C 1) 0.00 -20.00 2) 20.00 2) 0.01 2)

Calibration R x/4 1.000 0.500 2.000 0.001

Offset R x/4 mA/V/C 1) 0.00 -20.00 2) 20.00 2) 0.01 2)

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.

Note: x denotes the device address of the 500AXM11 that hasbeen configured. Where there are several AXM modules, all therespective inputs are displayed and if no AXMs are configured,the parameter dialogue is empty. The number following the slashis that of the associated input channel to which the parameterapplies.


Input Type R x/ydetermines the type of analogue input signal (x = 500AXM11device address, y = channel number). The following settingsare available:

- 0..20 mA- 4..20 mA- -20..20 mA- 0..10 V- -10..10 V- Pt100- Pt250- Pt1000- Ni100


37/76


35

- Ni250- Ni1000

Calibration R x/ydetermines the factor by which the input signal is multiplied.The default setting is 1.000.

Offset R x/ydetermines the value of the offset added to the input signal (x= 500AXM11 device address, y = channel number). Thedefault 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 200C 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 furthersubmenus (see Fig. 3.11).

^__=m=^~=iob`PNSGQ=J=`=rj~=j=b==b=e~~=c===^~=l

=====================================b=l=q=EoflF==========b=`~=m~~==========b=`=====================obqrok============================================================b=f__Lofl=`~====obqrok=====================================================l=J=i=VSMM====p`pWilksSKO==sSKO

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 OutputTypes (RIO)). Other parameters in the menu Edit ChannelParameters can then be changed. All the parameters are listedand explained in the following tables.


38/76


36


Submenu Edit Output Types (RIO)


Output Type R x/1 4..20 mA (Select)

Output Type R x/2 4..20 mA (Select)

Note: x denotes the device address of the 500AXM11 that hasbeen configured. Where there are several AXM modules, all therespective outputs are displayed and if no AXMs are configured,the parameter dialogue is empty. The number following the slashis that of the associated input channel to which the parameterapplies.

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)

Setpoint R x/y mA / V 1) 0.00 -20.00 2) 20.00 2) 0.011) 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.

Note: x denotes the device address of the 500AXM11 that hasbeen configured. Where there are several AXM modules, all therespective outputs are displayed and if no AXMs are configured,the parameter dialogue is empty. The number following the slashis that of the associated input channel to which the parameterapplies.


Output Type R x/ydetermines the type of analogue output signal (x =500AXM11 device address, y = channel number). Thefollowing settings are available:- 0..20 mA- 4..20 mA- -20..20 mA- 0..10 V- -10..10 V


39/76


37

Channel R x/yspecifies the signal source for the analogue output channel (x= 500AXM11 device address, y = channel number). Ameasured variable of a protection function, an AXM moduleor from the Interbay bus (Input from SCS) can be set.

MinValue R x/ydetermines the minimum output value for the measuredvariable (see explanation below).

MaxValue R x/ydetermines the maximum output value for the measuredvariable (see explanation below).

OutputMode R x/ydetermines the response of the output in the event ofcommunication 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 theprocess bus for relaying analogue output signals, it isactivated as soon as the active RE. .16 (main unit) fails andbefore the output mode becomes effective.

Setpoint R x/ydetermines the value at the output when communicationbetween the RE. .16 and the 500AXM11 has failed. The unitand setting range of the parameter vary according to the typeof 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 theprocess bus for relaying analogue output signals, it isactivated as soon as the active RE. .16 (main unit) fails andbefore the setpoint becomes effective (OutputMode must beset to Use Setpoint).


40/76


38

Explanation of parameters MinValue and MaxValue:

The settings of these two parameters determine the ratio of theoutput 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 protectionfunction. The range of 0 to 2.00 IN has to be transferred to ananalogue output type 420 mA, 0.00 IN corresponding to 4 mAand 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 toan analogue output type 0...20 mA, 0.50 PN corresponding to0 mA and 1.50 PN to 20 mA. Thus a value of 0.00 PNcorresponds 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 everyinput and output signal via the HMI. This simplifies the

identification of the various signals because the associatedcomment is displayed whenever a particular signal is used.

The procedure for entering comments is similar for all the signalsof an RIO580 system. The following example for a binary inputsignal on a 500BIM11 module therefore applies to all othersignals.


41/76


39

First select the menu item Edit Binary Inputs in the EditHardware Functions submenu and then Edit Comment.

^__=m=^~=iob`PNSGQ=J=`=rj~=j=b==b=e~~=c===b=_~=f=====================================b=b~=L=b~==========b=`=====================b=af~============obqrok============================================================b=f__Lofl=`~====obqrok=====================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.12 Edit Binary Inputs

After selecting this submenu, a choice is presented betweenediting local inputs and signals available via the process bus.

^__=m=^~=iob`PNSGQ=J=`=rj~=j=b==b=e~~=c===b=_~=f====p=i_f==o_f=======================================i~=f======================o=f=====================obqrok=============================================================b=f__Lofl=`~====obqrok=====================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.13 Edit Comment


42/76


40

After selecting the process bus inputs, a device address for therespective input module is requested. This can be any numberfrom 1 to 80. Modules which have not been configured can alsobe selected and comments for their inputs entered.

^__=m=^~=iob`PNSGQ=J=`=r

j~=j=b==b=e~~=c===b=_~=f====p=i_f==o_f=======================================i~=f===========p=o_fJkK=====o=f=====================================================obqrok==================[==N=======================================================================================================r~=ofl=d=====================b=f__Lofl=`~========================================obqrok=========================NKKUM===============================================================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.14 Selecting the device address

An input can be selected following the entry of the deviceaddress. The key is then pressed and the commententered.

^__=m=^~=iob`PNSGQ=J=`=r

j~=j=b==b=e~~=c===b=_~=f====p=i_f==o_f==================================p=`~=====i~=f===========p=o_====================================o=f========================obqrok==================[==N=====N=O=P=Q=R=S=T=U=VNM=============================================================r~=o=b=f__Lofl=`~=======================obqrok=========================NKKUMNNNONPNQNRNS=============================================`~=`=[=r===================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 3.15 Entering a comment for the input


43/76


41

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).

^__=m=^~=iob`PNSGQ=J=`=r=============================================================================js_JoflJa~fW======================================================================================================================================t=jW========m==_^~=======================m`J`~=p~W======o~==================================================m`J`~=bW=======k=b===============================================m`J`~=qW========m=============================================m`J`~=ptJsW=======PKMM==OMMNJMNJMU=====================================m`J`~=e~_~W=====QNSOT================================================i=^=>=L=i=_=>=L=MM================================================_^~|NW=o~===================================================_^~|OW=o~===================================================_^~|PW=k=o~===============================================

_^~|QW=k=o~===================================================================================================================================================================================================================================================================================l=J=i=VSMM====p`pWilksSKO==sSKO

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 theconfigured slot is empty.

Process bus The PC card was initialised as aprocess 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


44/76


42

4.2.2. PC card status

Status Function / Significance

None There is no PC card in the RE. 216,RE. 316*4slot 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 stilloperational (e.g. configured modulesmissing or too many modulesconfigured).

Fatal error An error occurred while starting or

during operation (e.g. PCC and RE. .16software are incompatible or wrongMVBC on the PCC). The PC card willcontinue to be reset and restart until thefault 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 /

RE. .16 error code

Function / Significance

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 toomany or no modules configured). SeeSection 5.


45/76


43

Error messages /

RE. .16 error code

Function / Significance

Some devices not

connected / 6H

Either the bus is not connected or oneof the modules configured is defectiveor not available, 500BIM11 could not

start.Status supervision too slow / 7H Too little CPU time for the MPL sink

time supervision function (too manymodules configured or cycling time settoo short).

Supervision task too slow / AH The is not enough computing time tosupervise the modules. The system asa whole is too big or the cycling time istoo short. The transfer of data functionscorrectly.

Copy task too slow / 5H The system as a whole is too big or thecycling time is too short. Data may belost.

Supervision task terminated / 9H An error has occurred in the tasksupervising the modules and it hastherefore aborted.

Copy task terminated / BH An error has occurred in the task thatcopies the data and it has thereforeaborted.

Heartbeat task terminated / CH An error has occurred in the PC cardsdiagnostic function.

MPL subsystem error / DH An error has occurred in the MPLsubsystem.

BA subsystem error / EH An error has occurred in the BAsubsystem (e.g. invalid configuration).

TIM subsystem error / 10H An error has occurred in the TIMsubsystem (time synchronisation). Thesystem times are therefore notsynchronised. This occurs when toomany modules are configured or thecycling time is set too short.

EVA subsystem error / 11H An error has occurred in the EVAsubsystem (event and alarm handling).

DBS subsystem error / 12H An error has occurred in the data basesubsystem.

Table 4.3 PC card error messages


46/76


44

4.2.4. PC card type

Process or interbay bus

4.2.5. PC card SW version

Software Version and YearMonthDay

4.2.6. PC card counter

A ring counter is cyclically incremented and this indicates thatthe PC card is active.

4.2.7. Redundant bus administrators

Every bus administrator that is configured transmits a diagnostictelegram which all the RE. 216 or RE. 316*4 units can read. Ifthe diagnostic telegrams that have been configured are not

received or the software determines that the redundant busadministrators are not ready, the statuses of the busadministrators are set to Not ready.

4.3. RIO, PBI and ITL information

After the PC card has started and is in the Ready state, the500BIM11, 500BOM11/12 and PBI modules are checked todetermine whether they are connected to the process bus andthe ITL data sets are checked to determine whether data are stillbeing transferred. The results are displayed in the RIO

diagnostic window. A hyphen - indicates a module that has notbeen configured, a zero 0 a module that has been configured,but is not connected, and an X a module that is both configuredand connected (see Fig. 4.2).

^__=m=^~=iob`PNSGQ=J=`=r=============================================================================oflJa=W=================================================================================================================================kK==oW======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===================================================================================================================================================================================================================================================================================================================================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 4.2 RIO supervision


47/76


45

After switching on the auxiliary supply of an RE. 216 orRE. 316*4 unit, the reset counter is set to 0 (see Fig. 4.2 andFig. 4.5). It is then incremented by 1 every time the PC card isrestarted. The PC card is also restarted after changing the HMIsettings.

4.4. RIO module status

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

^__=m=^~=iob`PNSGQ=J=`=r=============================================================================oflJp~JfW===========================================================

=============================================================================kK==oW======M=======================================================a=kK==OO==============================================================a=>==========================================================i=^=>=L=i=_=>=L=MM================================================q=_fj=j=p~W=o~=====`=s~W==NV==========================ptJsW===PKMM=========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 4.3 500BIM11 software ID and module status information

Similarly, the RE. .16 reads the version of every 500AXM11module (see Fig. 4.4).


48/76


46

^__=m=^~=iob`PNSGQ=J=`=r=============================================================================oflJp~JfW========================================================================================================================================kK==oW======M=======================================================a=kK==ON==============================================================a=>=========================================================

=i=^=>=L=i=_=>=L=MM================================================f=~=^ujJj>===========================================================^ujJfaW=NMM===sW=MMMN================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 4.4 500AXM11 software ID and module statusinformation

4.5. PBI module status

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

^__=m=^~=iob`PNSGQ=J=`=r=============================================================================m_fJp~JfW===========================================================

=============================================================================kK==oW======M=======================================================a=kK===N==============================================================a=>==========================================================i=^=>=L=i=_=>=L=MM================================================a=o~===============================================================f=p~W===============l=p~W====================================aqW====U==========aqW====U==============================m`W=======P==========tjW=======N==============================tjW=======N==========lmW======U==============================cmd^`W========N========================================================================================================================================================================================================================================================================================================================================================================l=J=i=VSMM====p`pWilksSKO==sSKO

Fig. 4.5 PBI status information


49/76


47

4.6. Event list messages

The PC card generates messages that can be configured via theHMI system parameter menu (see Section 3.4 in the RE. .16Operating Instructions) to be recorded as events.

The process bus error message MVB_PB_Warn is displayedshould not all the modules respond that have been configured.The message means that there is no communication via theprocess bus, i.e. none of the devices responds.

PB_BA1Ready PB_BA4Ready indicate that the busadministrators that have been configured are standing by.

Where the system includes a redundant process bus and thecorresponding supervision function is activated (see Section 3.2),the error messages PB LA faulty and PB LB faulty, indicatethat 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 informationas to whether it can communicate via the system and whetherthe redundant line has failed. This is also in the form ofinformation that can be processed by the RE. .16 (e.g. by aFUPLA logic). For this purpose, it is necessary to select themenu item Input from RBIs in the Select Binary Input menu inorder to change the wiring of a binary input (e.g. the binaryFUPLA 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 itsexternal wiring which is recorded in the event list and can beviewed by selecting Display RBI Status in the MeasurementValues menu. This information is also available as processinformation and input signals of protection functions (e.g.FUPLA). The information provided by the various Bits is asfollows:


50/76


48

Bit 1: Broken wire Out-Channel 1: The connection to output 1is open-circuit (4..20 mA only).

Bit 2: Broken wire Out-Channel 2: The connection to output 2is 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.Bit 7: Supply short-circuit (Ch2): The supply of input 2 sensor



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).Bit 14: Broken wire In-Channel 2: The connection to input 2 is



open-circuit (4..20 mA and temperature only).Bits 13 to 16 are generated by the RE. .16 when the input fallsbelow 3.8 mA, respectively 100 C or exceeds 500 C.


51/76


49

4.9. Display of measured variables

The values of all the inputs and outputs can be viewed via theMeasurement Values menu. Refer to Section 5.7 of the RE. .16Operating Instructions for further details.

4.10. Test functions / fault-finding

The test functions Set test data and Perform selected testenable test data to be transmitted to the 500BOM11/12 and500AXM11 modules, PBIs and ITL.

4.11. Replacing modules

500RIO11 units: Note that replacing 500RIO11 units inoperation that are linked by an RS485daisy chain will interrupt the bus and causedata to be lost.

PBI units: Refer to document [1] Process BusInterface HACE 400008 before replacingPBI 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 therange 36 VDC312 VDC and the internal auxiliary supplies are intolerance.

The four yellow LEDs (RxA, TxA, RxB and TxB) light when dataare being transferred via line A or B of the electrical MVB bus.

If the MVB bus is used non redundant, the LEDs RxA and bothTxA and TxB light.

All four LEDs 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 isactivated.

4.12.3. Binary input module 500BIM11

Each input has its own yellow LED which lights when it isactivated.


52/76


50

4.12.4. Analogue input/output module 500AXM11

This module has six green LEDs that all light in normaloperation and do not all light in the following cases:

LEDs 1..4: A LED does not light when the supply to therespective sensor is short-circuited.

LEDs 5 and 6: The associated LED does not light when a circuitis open, e.g. because an external lead is interrupted. A circuitwhich is not needed must be short-circuited. Both LEDs go out ifno 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 VDC312 VDC and the internal auxiliary supplies are intolerance.

Since only MVB line A is used by the star coupler, only the twoLEDs RX1 and TX1 on the left are of consequence and lightwhen data are being transferred via line A of the electrical MVBbus.

4.13.2. Star coupler module 500SCM11

The star coupler module 500SCM11 is equipped with six opticalchannels. The associated yellow LED Rx lights for every channelto which an optical cable is connected and data are beingreceived. Depending on whether one or several 500SCM11 areinstalled, the LEDs Tx1 to Tx7, respectively Tx13 all light whendata are being transmitted.


53/76


51

5. DETERMINING THE MAXIMUM POSSIBLE SYSTEM SIZE

5.1. With internal bus administrator

The internal bus administrator (BA) occupies a part of the PCcard computing capacity and to ensure that the PC card is not

overloaded, the following equation has to be satisfied.

11024

Ip*5a*3b...

8

Ip*5a*3b

4

Ip*5a*3b 102410241024102488884444

+++++

++++

+++

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 busadministrator than using an internal one. To ensure that the PCcard is not overloaded, the following equation has to be satisfied.

7.11024

Ip*5a*3b...

8

Ip*5a*3b

4

Ip*5a*3b 102410241024102488884444

+++++

++++

+++

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


54/76


52

6. CONFIGURATION PROCEDURE

The procedure for configuring the process bus is as follows:Assuming a process bus has to be configured for a systemcomprising three RE. 216 or RE. 316*4units (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 PBIs and theinterlocking 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 Aand set the cycling times for the various module groups (seeSection 3.1). In the same window, active all the modules thathave to be connected to the process bus, i.e. all modules

processed by the RE. 316*4 A, B and C units. Thecorresponding data are saved in the file mbaXX.par (therespective device address is inserted for XX). The filembaXX.par can then be copied to the two other RE. 316*4 unitsso that the module cycling times and the ITL data sets only haveto be entered once in one RE. 316*4. If a different deviceaddress to the one in RE. 316*4 A is detected when copying theconfiguration file mbaXX.par to RE. 316*4 B and C, the systemswitches automatically to the external BA mode. Should youwish to operate the internal BAs 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*4units, the next thing is to configure the modules in the RE. 316*4units that are processed by all of them as describedin Sections3.2and3.3.

The entire 500RIO11 configuration (input voltage, contact bouncetime etc.) can be saved and retrieved again.

6.3. Checking the system

After completing the configuration of the system, run it and checkthe PC card and the modules connected to the process bususing the diagnostic function(see Section 3.4).


55/76


53

7. PROTECTION FUNCTION ANALOG RIO TRIG

7.1. Application

Supervision of the analogue input signals on the 500AXM11module.

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 the500AXM11 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 thealarm and tripping parameters depend on the type that has beenset for the analogue input on the 500AXM11 module. Where acurrent or voltage input is concerned the value is displayed as apercentage and where a temperature sensor is concerned in

degrees Celsius.


56/76


54

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

AlarmLevel % / C 1) 50.0 -100.0 / -50.0 1) 100.0 / 300.0 1) 0.1

TripLevel % / C 1) 80.0 -100.0 / -50.0 1) 100.0 / 300.0 1) 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

Remote Input / Output System

Documents

Transcript of Remote Input / Output System