S 0221651

ABB Automation Products HPC563 RCS
3BSE 022 165R101

LAPI 2000-05-23
86(56*8,'(
9DOLGIRU+3&6:
+3&5&6237,21
&,1'&& &$9&&& &'9&& &3&9&& &&21)&&&
) RTU_N VAL1 ) RTU_N VAL ) RTU_N )
VAL RTU_N NEW_VAL ) BOARD_N COMM_ACT
) SUBRTU_N STATUS1 ) SUBRTU_N STATUS ) SUBRTU_N )
STATUS SUBRTU_N L_R_EOP ) RTU_N CONFCODE
) ) BLOCK_N ) )
)
BLOCK_N
APP_CONN
:
VAL16 ) APP_CONN VALUE>H2
BLOCK_N
POS_ACKN
BLOCK_N L_R_INT
DAY ) SUBRTU_N POS_ACK
STATUS16 VALUE>H1 UPD_REQ NEG_ACKN UPD_REQ HOUR ) RTU_TYPE NEG_ACK
PC_CONF PC_CONF VALUE<L1 MINUTE TERM_ACT
UPD_REQ POS_ACKN UPD_REQ VALUE<L2 ERRCODE SECOND E_CONF TIMESYNC
NEG_ACKN RANGEMIN ERR STATUS P_CONF IND_ERR
RANGEMAX POS_ACKN WSP RESTART ACT_COMM AV_ERR
ERRCODE CONV_PAR NEG_ACKN DSX NEW_TIME FTAB_SEQ DV_ERR
INV_TIME
ERR
WSP ERRCODE TGL_FTAB FTAB_ERR POS_ACKN EOP PCV_ERR
DSX ERR BOARD NEG_ACKN INT CMD_ERR
WSP ADDRESS EOP_TIME SETP_ERR
TGL_FTAB FTAB_ERR DSX PRIORITY ERRCODE INT_TIME GO_ERR
BOARD BLOCKED ERR TGL_SCI TERM_ERR
ADDRESS TGL_FTAB FTAB_ERR START_CH

WSP TGL_TSI AC_FAIL
PRIORITY BOARD DEADBAND
START_CH ADDRESS SCANCYCL
DSX
TGL_EOP BATT_LOW
BLOCKED CHANNEL PFORMAT TGL_FTAB FTAB_ERR TGL_INT SCI_ERR
IND_TYPE BACKCYCL NOOFBITS BOARD TGL_HIST UPDATED
S_M_MDPS CONV_CAT CONNTYPE ADDRESS HISTYEAR COMDIAG1
SER_1_0 PRIORITY CHANNEL
HISTMNTH COMDIAG2
BLOCKED PRIORITY

SER_0_1
FLT_TIME SER BLOCKED
HISTDAY
TRANS_CS LP_SER LP_EOP HISTTIME ERRCODE
CONNTYPE LPB_SER LPB_EOP ERR
TRANS_CS SAVE_INT WSP
SCANCYCL RED_FACT DSX
ABSDEADB CLR_EOP
DEADBAND CONNTYPE TGL_PRIM PRIMARY
DB_UPD PRIMSTRT
DISTFREQ
FILTFACT TGL_EVTR EVTR_ERR
CONNTYPE TGL_DEL EVTR_WSP
TGL_LIM LIM_ERR PROC_N
EN_H2 BIT_N
HI_LIM2 EVENT_T
EN_H1 DBASE_ID
&2&0'&&
) RTU_N SELECTED
HI_LIM1
EN_L1
VALUE_TR
) SUBRTU_N POS_ACKN LO_LIM1 &*2& NAME_TXT
) OBJECT_N NEG_ACKN EN_L2 ) RTU_N POS_ACKN DESC_TXT
LO_LIM2 &6(73& ) SUBRTU_N NEG_ACKN MMI_TYPE
SELECT ERRCODE HYST ) RTU_N POS_ACKN ) OBJECT_N MMI_NET
EXECUTE ERR ) SUBRTU_N NEG_ACKN ERRCODE MMI_NOD
DESELECT WSP ) OBJECT_N SND_GO ERR
IMM_EXE DSX &5&0'&& ERRCODE B0_VAL WSP TGL_CPAR CPAR_ERR
ON_OFF ) RTU_N POS_ACKN SND_SETP ERR B1_VAL DSX BAUDRATE TESTMODE
) SUBRTU_N :
) OBJECT_N
NEG_ACKN SETP_VAL WSP DUPLEX
TGL_FTAB FTAB_ERR
RANGEMIN DSX :
BOARD ERRCODE RANGEMAX B15_VAL POLLTIME
ADDRESS IMM_EXE ERR SETPTYPE ANAVAL TURNTIME
OBJBOARD ON_OFF WSP RANGEMIN POLLTOUT
CMD_TYPE DSX TGL_FTAB FTAB_ERR RANGEMAX PREAMBL
OUT_FRMT

LP_CMD
CHK_CARD TGL_FTAB FTAB_ERR
BOARD
ADDRESS
POSTAMBL
CHK_CIRK BOARD CHANNEL TGL_FTAB FTAB_ERR TSI_TIME
P_LENGTH ADDRESS STROBBRD BOARD TGL_SYSM
RESP_BLK OBJBOARD STROBADR ADDRESS SYSMESS
RESP_BIT P_LENGTH STROBCHA CHANNEL ACT_TEST
CONNTYPE CONNTYPE CONNTYPE CONNTYPE TEST
SUMMARY :
This Users Guide describes the application of the HPC563 Remote Control Server (RCS) option in
control and monitoring systems using Advant Controller 400 process computers. The RCS Option
communicates with underlying RTUs by means of the RP570 or RP571 protocol and has a function block
oriented application interface. HPC563 RCS is the master in the master/slave relationship between the
HPC563 RCS system and its connected RTUs.
This document and parts thereof must not be reproduced or copied without ABB Automation Products
ABs written permission, and the contents thereof must not be imparted to a third party nor be used for
any unauthorized purpose. Contravention will be prosecuted.
3BSE 022 165R101 COPYRIGHT $%%$XWRPDWLRQ3URGXFWV$% 2000
ABB Automation Products AB HPC563 RCS
&217(176
1. ,1752'8&7,21
1.1 *(1(5$/,1)250$7,21
1.2 7$5*(7*5283
1.3 $%%5(9,$7,216$1'&219(17,216
2. &21),*85$7,216
2.1 3266,%/(5&66<67(0&21),*85$7,216
2.1.1 SYSTEM EXAMPLES 7
2.2 +3&5&66<67(0/,0,7$7,216
3. 5&6+$5':$5($1'62)7:$5(
3.1 ,1752'8&7,21
3.1.1 GENERAL INFORMATION 10
3.1.2 FREE PROGRAMMABLE MVI BOARD CI535 10
3.1.3 PROGRAM CARD INTERFACE BOARD MB510 AND PCMCIA FLASH PROM 10
3.2 $33/,&$7,210($685(6
3.2.1 FREE PROGRAMMABLE MVI BOARD CI535 10
3.2.2 PROGRAM CARD INTERFACE BOARD MB510 11
3.3 25'(5,1*,16758&7,216
4. &20081,&$7,2135272&2/6
4.1 ,1752'8&7,21
4.2 6833257('0(66$*(6,17+(5335272&2/
4.2.1 MESSAGES FROM HPC563 RCS TO RTU 12
4.2.1.1 Data request commands 12
4.2.1.2 Process commands 12
4.2.1.3 RTU commands 13
4.2.2 MESSAGES FROM RTU TO HPC563 RCS 13
4.2.2.1 Acknowledgements from RTU 13
4.2.2.2 Process command responses 13
4.2.2.3 Data request responses 14
4.2.2.4 RTU status responses 14
4.3 6833257('0(66$*(6,17+(5335272&2/
4.3.2 MESSAGES FROM HPC563 RCS TO RTU 15
4.3.2.1 RTU commands 15
4.3.3 MESSAGES FROM RTU TO HPC563 RCS 15
4.3.3.1 Acknowledgements from RTU 15
4.3.3.2 RTU status responses 15
4.4 $'$37$7,2172$/,(135272&2/6
3BSE 022 165R101 1

HPC563 RCS ABB Automation Products AB
5. &20081,&$7,21&21),*85$7,216
5.1 *(1(5$/,1)250$7,21
5.2 $33/,&$7,210($685(6
5.2.2 THE RS232 PROTOCOL 17
6. '(),1,7,21$1')81&7,21$/,7<2)5(027(&21752/6,*1$/6
6.1 *(1(5$/,1)250$7,21
6.2 $33/,&$7,210($685(6
6.2.1 DATA BASE POPULATION 19
6.2.1.1 General information 19
6.2.1.2 Creating and updating MVIx in AC410 19
6.2.1.3 Creating and updating MVIx in AC450 20
6.2.2 HPC563 RCS PC-PROGRAM 21
6.2.2.2 HPC563 RCS system configuration 22
6.2.2.2.1 RCS system configuration (the C-CONF pc-element) 22
6.2.2.3 Data acquisition 32
6.2.2.3.1 RTU indications (the C-IND pc-element) 32
6.2.2.3.2 RTU analog values (the C-AV pc-element) 35
6.2.2.3.3 RTU digital values (the C-DV pc-element) 42
6.2.2.3.4 RTU pulse counter values (the C-PCV pc-element) 45
6.2.2.4 Process commands 48
6.2.2.4.1 RTU object command (the C-OCMD pc-element) 48
6.2.2.4.2 RTU regulation command (the C-RCMD pc-element) 51
6.2.2.4.3 RTU setpoint data (the C-SETP pc-element) 54
6.2.2.4.4 RTU general output data (the C-GO pc-element) 57
6.2.2.5 Error codes in RCS pc-elements 61
6.2.2.7 Error codes during normal operation (ERR = 0) 61
6.2.2.8 Error codes due to RCS system errors (ERR = 0) 61
6.2.2.9 Error codes due to RCS system errors (ERR = 1) 62
7. &/2&.6<1&+521,=$7,21
7.1 *(1(5$/,1)250$7,21
7.2 $33/,&$7,210($685(6
2 3BSE 022 165R101

0$10$&+,1(&20081,&$7,21
8.1 $/$50$1'(9(17+$1'/,1*
8.1.2 NORMAL EVENT HANDLING 64
8.1.2.1 Event handling description 64
8.1.2.2 Application measures 65
8.1.3 HPC563 RCS ALARM AND EVENT HANDLING 65
8.1.3.1 Event handling description 65
8.1.3.2 Application measures 66
8.1.3.2.1 General information 66
8.1.3.2.2 Indication events (ERMI telegrams) 67
8.1.3.2.3 Terminal status information (TSTA telegrams) 68
8.1.3.2.4 Terminal event information (TEV telegrams) 69
8.2 (9(17+$1'/,1*72:$5'6+3&/2&$/35,17287)81&7,21
9. +3&6<67(0,17(*5$7,21
9.1 ,17(*5$7,2172:$5'67+(+3&578237,21
9.1.2 APPLICATION MEASURES 72
9.1.2.1 Event integration 72
9.1.2.2 Function table integration 73
10. 5&635,17287)81&7,21
10.1 *(1(5$/,1)250$7,21
10.2 $33/,&$7,210($685(6
10.2.1 MODIFICATION OF PROPERTIES IN AC400 DATA BASE 74
10.2.2 MODIFICATION OF THE PRINTER_DESC FILE 74
10.2.3 MODIFICATION OF THE CAP1.1 FILE 75
11. +3&5&66<67(0+$1'/,1*
11.1 5&66<67(0&21),*85$7,21
11.2 5(67$572)$&12'(
11.3 5(67$572)5&63&(/(0(176
11.3.2 RESTART OF RCS SCADA PC-ELEMENTS 77
11.3.3 RESTART OF C-CONF PC-ELEMENTS 77
3BSE 022 165R101 3

683(59,6,21$1'(5525+$1'/,1*
12.1 *(1(5$/,1)250$7,21
12.2 683(59,6,2187,/,=,1*)$&,/,7,(6,153
12.3 683(59,6,21)81&7,216,17+(3&(/(0(176
12.4 6<67(00(66$*(6
12.5 683(59,6,21%<$33/,&$7,21352*5$00,1*
13. 67$572)+3&5&66<67(0
13.1 &2/'67$57
13.2 :$5067$57
14. 0(025<&2168037,21$1'6<67(0/2$'
14.1 *(1(5$/,1)250$7,21
14.2 %$6,&6<67(0
14.2.2 MEMORY CONSUMPTION 81
14.2.3 SYSTEM LOAD 82
14.2.3.2 Quiet system 82
14.2.3.3 Event burst 82
14.3 +3&5&63&(/(0(176
14.3.1 MEMORY CONSUMPTION 82
14.3.2 SYSTEM LOAD 83
15. 5()(5(1&('2&80(176
16. 5(9,6,216
4 3BSE 022 165R101

1. ,1752'8&7,21
1.1 *(1(5$/,1)250$7,21
The HPC563 RCS Option is the software and hardware which are added to a standard AC400 in the form
of option modules and a communication board to establish the following functions:
Definition and supervision of the HPC563 RCS Option by means of the pc-element
C-CONF.
Interface for the data exchange with the RCS pc-elements.
Transmission of data to and from RTUs according to the RP570 and RP571 protocols.
Definition of remote signals by means of RCS SCADA pc-elements.
The HPC563 RCS option does not involve any limitations with regard to the ordinary functionality of
AC400, nor does it exclude the use of other options such as HPC563 RTU, HPC563 SPA Server, HIST-
REG, CALC-REG etc.
1.2 7$5*(7*5283
The Users Guide addresses the staff responsible for application engineering in the first place. It might,
however, be of some use also for those who are responsible for testing, commissioning and maintenance.
1.3 $%%5(9,$7,216$1'&219(17,216
AC400 New generation of process computers made by ABB Industrial Systems. The RCS
option can be implemented both in the AC410 and in the AC450 process computer.
AVM Analog value message without status. Response from RCS with information from
up to 7 measured values.
AVS Analog value message with status. Response from RCS with an analog measurement
and status of the measurement.
HPC563 RTU Remote terminal unit option made by ABB Generation which can be installed in
Option AC400 process computers. The AC400 stands as an RTU in the communication
network.
HPC563 RCS Remote control server option made by ABB Generation which can be installed in
Option AC400 process computers. The AC400 stands as a dispatch center in the
communication network.
HPC563 SPA SPABUS protocol server option made by ABB Generation which can be installed in
Server Option AC400 process computers. . The AC400 stands as a Master in the SPABUS-
communication network.
MP200/1 Old generation of process computers made by ABB Industrial System (former ABB
Automation).
C-IND HPC563 RCS indication pc-element. The C-IND pc-elements are used to receive
IDM, IDS and ERMI telegrams from the connected RTUs.
C-AV HPC563 RCS analog value pc-element. The C-AV pc- elements are used to receive
AVM, AVS and ERMA telegrams from the connected RTUs.
C-DV HPC563 RCS digital value pc-element. The C-DV pc- elements are used to receive
DVM and DVL telegrams from the connected RTUs.
C-PCV HPC563 RCS pulse counter pc-element. The C-PCV pc- elements are used to
receive PCM and PCT telegrams from the connected RTUs.
3BSE 022 165R101 5

C-OCMD HPC563 RCS object command pc-element. The C-OCMD pc-elements are used to
transmit IXC, CBXC, EXC and IHC process commands to the connected RTUs.
C-RCMD HPC563 RCS regulation command pc-element. The C-RCMD pc- elements are
used to transmit IXC process commands to the connected RTUs.
C-SETP HPC563 RCS setpoint pc-element. The C-SETP pc- elements are used to transmit
SPM process commands to the connected RTUs.
C-GO HPC563 RCS general output data pc-element. The C-GO pc- elements are used to
transmit GOM process commands to the connected RTUs.
RP570 Official ABB communication protocol developed by ABB Network Control to be
used in S.P.I.D.E.R. networks without router-RTUs.
RP571 Official ABB communication protocol developed by ABB Network Control to be
used in S.P.I.D.E.R. networks with router RTUs.
RTU Remote terminal unit. Unit which can be controlled remotely from a dispatch
center. An MP200/1 or AC400 with HPC560/3 RTU software is by the HPC563
RCS system regarded as an RTU.
RCS_WD RCS system task (OHAB250) for configuration and monitoring of the RCS SCADA
pc-elements.
RCS_GCI RCS system task (OHAB260) which is the communication interface between the
RCS MVI communication board and the RCS SCADA pc-elements.
RCS_ALEV RCS system task (OHAC630) which performs the RCS alarm and event handling
towards an Advant Operator Station or HPC563 Local Event Printout function.
RCS_MVI Multi Vendor Interface communication board where the master part of the RP570/1
protocol is implemented. The RCS_MVI board represent the software and
hardware interface with the S.P.I.D.E.R. network.
SCADA Superior control and data acquisition. Concept commonly used when discussing
remote control networks.
Symbolic A symbolic translation is a function which finds the cross reference between the C-
translation IND or C-AV value outputs and logical records in the DI and AI database
respectively. The function is performed by the C-IND and C-AV pc-elements after
a request from the RCS_WD task.
Terminal A computer which is remotely controlled by Front End. The same meaning as RTU.
6 3BSE 022 165R101

2. &21),*85$7,216
2.1 3266,%/(5&66<67(0&21),*85$7,216
2.1.1 6\VWHPH[DPSOHV
In figure 1 it is shown a HPC200 system
Figure 1
M M I panel application containing only a AC400 computer
equipped with the RCS option.
Local event
AC400
(RCS) printer
The station controls three RTUs by means of the
HPC563 RCS option. The RP570 protocol is
RP570 used on the communication network.
Note that it is possible to attach a printer for

local event printout handling by means of the
RTU210 RTU210
HPC563 LEP 1 option. Events from the
AC400
(RTU CSN + CM N) underlying RTUs can also be forwarded to the
printer.
Figure 2 shows a HPC200 application

Figure 2 containing a AC400 computer equipped with the
A dvant
Operator station RCS and RTU options.
M B300 The station controls three RTUs by means of the

RP570
HPC563 RCS option. The RP570 protocol is
A C400
(RCS and used on the communication network.
RTU CSN + CM N)
S.P.I.D.E.R.
dispatch centre
RP570 The information received from the underlying
RTUs and local process information is
forwarded to the local Advant Operator Station
and to the dispatch center by means of the
RTU210 RTU210
HPC563 RTU option.
A C400
(RTU CSN + CM N)
In big stations, the HPC 300 system with

SPIDER
Figure 3 dispatch distributed computers on a local network is the
centre
most common solution.
RP570
The station controls three underlying RTUs by

AC400
Advant
Operator Local event means of the HPC563 RCS option. The RP570
(RTU CSN + CMN) printer
Statioon
protocol is used on the communication network.
MB300
The information received from the underlying

RTUs and local process information is
AC400
AC400
(RTU CSN
AC400 AC400 forwarded to the local Advant Operator Station
(RTU CSN) (RTU CSN) (RTU CSN)
and RCS) and to the dispatch center by means of the
RP570 HPC563 RTU option.
Note that MB300 must be used for the local

RTU210 RTU210 network due to performance and flexibility
AC400 reasons.
(RTU CSN + CMN)
1 HPC563 Local Event Printout Option, for details please see the Users Guide (5761 056-58/0).
3BSE 022 165R101 7

All three HPC563 Options, i.e. RCS, RCS and

SPIDER
Figure 4
dispatch SPA Server, can be present in the same system
centre
as shown in figure 4.
RP570
A total of two SPA nodes are connected to the

Advant AC400 with SPA Server and RTU CSN
Operator AC400
Station (RTU CSN + CMN) software, while two RTUs are connected to the
MB300
AC400 with RCS software.
Process point information and events from the

AC400
AC400 AC400
(RTU CSN)
(RCS SPA nodes and from the underlying RTUs can
(SPA Server
and RTU CSN)
and RTU CSN) be forwarded to the dispatch center and to the
SPABUS REL 100
AC400
(RTU CSN + CMN)
Advant Operator Station.
SPA node 1
SPA modem
SAC0 16D3
RP570 Note that MB300 must be used for the local
RTU210
SPA node 2 network due to performance and flexibility
reasons.
All three HPC563 Options, RTU, RCS and SPA

SPIDER
Figure 5
dispatch Server can also present in one AC400 node 2.
centre
RP570 Note also that multiple RCS MVI boards can be

implemented in the same AC400 node. It is
AC400
(RTU CSN + CMN,
MB300
Advant also, as shown in figure 5, possible to mix RCS
RCS and SPA Server) Operator
Station MVI boards with the RP570 and the RP571
SPABUS REG 216
protocol respectively in the same AC400 node.
RP570 SPA node 1
SPA modem
REL 521
The AC400 controls three RTUs by means of
RP571 SPA node 2
the RP570 protocol and three RTUs by means of
the RP571 protocol and the router-RTU 200. In
RTU200
RTU210 RTU210 RTU210
addition are two SPA node controlled from the
RP570 AC400 node.
Process point information and events from the

RTU210 RTU210 SPA nodes and from the underlying RTUs can
AC400
(RTU CSN + CMN)
be forwarded to the dispatch center and to the
Advant Operator Station.
Note that only MB 300 is possible for the local network. It gives the highest performance and the highest
flexibility.
In all alternatives of figure 3, 4 and 5 a number of local printout alternatives can be applied. For further
information about available printout facilities, please refer to Users Guide for Local Event Printout
Option HPC 56x, 5761 056-58/0.
2 The AC450 process computer should be used with such configurations.
8 3BSE 022 165R101

2.2 +3&5&66<67(0/,0,7$7,216
The following limitations are introduced in the HPC563 RCS system in order to reduce the complexity of
the system and to limit the overall AC400 load (application programming limitations) :
Maximum number of RCS MVI boards per AC400 node: 5
Maximum number of RTUs connected via RCS MVI boards per AC400 node 40
Maximum recommended number of RTUs / or number of process points connected via one RCS 8 / 1000
MVI board with RP570 protocol:
Maximum number of sub-RTUs connected to one router-RTU in the S.P.I.D.E.R. network: 48
Maximum number of indication process points per AC400 node: 4000
Maximum number of RCS pc-elements per AC400 node : 2000
The maximum number of RCS MVI boards per AC400 node, maximum number of RTUs connected via
RCS MVI boards per AC400 node and the maximum number of sub-RTUs connected to one RCS MVI
board with RP571 are restrictions which are implemented in the RCS software.
Note that the limitation of maximum number of indication process points per AC400 node and maximum
number of RCS pc-elements per AC400 node are instructive in order to reduce the load on the MB300
network. The restrictions are however, not implemented in the RCS software.
3BSE 022 165R101 9

3. 5&6+$5':$5($1'62)7:$5(
3.1 ,1752'8&7,21
3.1.1 *HQHUDOLQIRUPDWLRQ
A prerequisite for the HPC563 RCS option in the AC400 is the basic system QC01-BAS11*7.0/0B5/4 or
later.
The HPC563 RCS Option requires the hardware and software specified below. The RCS software
consists of two parts, system software and communication software, which must be added to the ordinary
software in the AC400 computer. In addition an application program must be made in the AC400
computer in order to obtain the desired functionality for the communication towards the protection units.
3.1.2 )UHHSURJUDPPDEOH09,ERDUG&,
The communication with the dispatch center takes place by means of the free programmable MVI board
CI535. The RCS communication software is in the form of PROM modules to be mounted on the free
programmable MVI board.
3.1.3 3URJUDPFDUGLQWHUIDFHERDUG0%DQG3&0&,$IODVK3520
The MB510 board is a program card interface for system software. The HPC563 RCS system software is
available in the form of a 2 Mbyte PCMCIA Flash card to be inserted in the MB510 interface board. The
RCS option software represent an extension of the basis system software in the AC400 computer.
3.2 $33/,&$7,210($685(6
3.2.1 )UHHSURJUDPPDEOH09,ERDUG&,
The CI535 board shall be placed in one of the four submodule positions on the main processor module
PM 150 in the AC410 or in one of the slots on a carrier board in the AC450.
A MVIx database element must be created, where x is the order of the CI535 board. Input data have to be
filled in to correspond to the actual position of the CI535 board.
10 3BSE 022 165R101

3.2.2 3URJUDPFDUGLQWHUIDFHERDUG0%
The MB510 board shall be placed in one of the four submodule positions on the main processor module
PM 150 in the AC410 or in one of the slots on a carrier board in the AC450.
There exists no database elements related to the MB510 board.
3.3 25'(5,1*,16758&7,216
Ordering instructions for MB510 are found in ABB Industrial Systems price list of AC400 standard
products. The board must be ordered from ABB Industrial Systems.
The MVI communication board, CI535, with RCS communication software and a PCMCIA flash PROM
containing RCS system software must be ordered from ABB Automation Products AB in Vsters,
Sweden. Ordering instructions for the HPC563 RCS software and hardware are as follows :
0RGXOH 2UGHUQXPEHU
HPC563 RCS software PCMCIA flash PROM
Communication board CI535 with HPC563 RCS communication software
3BSE 022 165R101 11

4. &20081,&$7,2135272&2/6
4.1 ,1752'8&7,21
In this chapter is given an account for the messages within RP570 and RP571 which are supported by
HPC563 RCS. Recommendations for adaptation to alien protocols are also given.
It should be noted that the RCS option has a limited functionality with regard to the FCOM, FTAB, TSTA
and TEV messages compared with the available functionality in the RP570 and RP571 protocol. Other
messages are not supported.
No messages concerning satellites are supported.
4.2 6833257('0(66$*(6,17+(5335272&2/
4.2.1 0HVVDJHVIURP+3&5&6WR578
4.2.1.1 Data request commands
Message : Interpretation : Remarks :

RA Request A. Not supported.
RB Request B. Implemented.
RX Request X. Limited functionality.
The following request X commands are implemented :
0) Request for indications
1) Request for pulse counter values
2) Request for analog values
3) Request for digital values
4.2.1.2 Process commands

IXC Immediate execute command. Implemented
CBXC Check back before execute command. Implemented
EXC Execute command. Implemented
IHC Inhibit command. Implemented
SPM Setpoint message. Implemented
GOM General output message. Implemented
12 3BSE 022 165R101

4.2.1.3 RTU commands

SCI Status check instruction. Implemented
RSEQ Reset sequence counter. Implemented
TSI Time synchronizing instruction. Implemented
FCOM Function command. Limited functionality.
The following function commands are implemented :
1) Cold start
2) Activate RTU
3) Intermediate/end-of-period reading of pulse counters
17) Reading of historical pulse counter values
18) Deactivate RTU. Accept a complete set of FTABs.
19) Database version.
FTAB Function table. Limited functionality.
The following function tables are implemented :
- basic function table for indications
- basic function table for analog measured values
- extended function table for analog values, limit supervision
- basic function table for digital measured values 3
- basic function table for pulse counter values
- basic function table for object commands
- basic function table for regulation commands
- basic function table for setpoint values
- basic function table for general output values
- basic function table for terminal information
TDC Transparent data in command direction. Not supported.
4.2.2 0HVVDJHVIURP578WR+3&5&6
4.2.2.1 Acknowledgements from RTU

CCR1 Cycle complete response priority 1. Not supported
CCR2 Cycle complete response priority 1 and 2. Implemented
EXR Executed response. Implemented
EXRR Executed response, RTU restarted. Implemented
NXR Not executed response. Implemented
4.2.2.2 Process command responses

CBR Check back response. Implemented
3 Properties for digital event handling not supported.
3BSE 022 165R101 13

4.2.2.3 Data request responses

IDM Indication message without status. Implemented
IDS Indication message with status. Implemented
AVM Analog value without status. Implemented
AVS Analog value message with status. Implemented
DVM Digital value message. Implemented
DVL Digital value long message . Implemented
PCM Pulse counter message. Implemented
PCT Pulse counter telegram. Implemented
ERMI Event recording message, indication. Implemented
ERMIR Event recording message for indications with relative time. Not supported.
ERMA Event recording message, analog value. Implemented
ERMD Event recording message, digital value. Not supported.
ERMFD Event recording message, Fault Distance. Not supported.
ERMC Event recording message for commands. Not supported.
PMRI Post mortem review message, initiating event. Not supported.
PMRV Post mortem review message, values. Not supported.
TDR Transparent data in response direction. Not supported.
4.2.2.4 RTU status responses

PRI Polling request instruction. Not supported.
TSTA Terminal status message. Limited functionality
4
The following TSTA flags are implemented : .
ID = 1 D0 (at least one indication is faulty)
D1 (at least one analog value is faulty)
D2 (at least one digital value is faulty)
D3 (at least one pulse counter value is faulty)
D7 (RTU is faulty)
D8 (RTU is active)
D9 (RTU is synchronized)
D13 (AC fail, RTU running on backup battery supply)
D14 (Battery low, RTU is running on last battery
reserve. Object commands are not executed).
TSTS Terminal status message, satellites. Not supported.
TEV Terminal event message. Limited functionality
5
The following terminal events are implemented : .
1) RTU restarted
23) RTU restarted, conditional down line loading (FTABs)
TEVS Terminal event message, satellites. Not supported.
MCM Memory contents message. Not supported.
SYSM System message telegram. Not supported.
4 Full funtionality for TSTA information can be implemented by means of the HPC563 RCS alarm and event handling, see chapter
ALARM AND EVENT HANDLING and the description of pc-element C-CONF.

5 An extended funtionality for TEV information can be implemented by means of the HPC563 RCS alarm and event handling, see
chapter ALARM AND EVENT HANDLING and the description of pc-element C-CONF.
14 3BSE 022 165R101

4.3 6833257('0(66$*(6,17+(5335272&2/
The RP571 protocol is a extension of the RP570 protocol. The HPC563 RCS option therefore supports
all RP571 messages which corresponds to the implemented RP570 messages shown in the previous
chapter. In addition the messages below are supported.
4.3.2 0HVVDJHVIURP+3&5&6WR578
4.3.2.1 RTU commands

FCOM Function command. Limited functionality.
The following function commands are implemented :
13) Subordinate RTU in/out of service
23) Set primary mode
4.3.3 0HVVDJHVIURP578WR+3&5&6
4.3.3.1 Acknowledgements from RTU

ACK Acknowledge Implemented
NACK Negative acknowledge Limited functionality.
The following negative acknowledge messages are implemented :
1) Sub-RTU does not exist.
2) Sub-RTU does not answer.
3) Sub-RTU out of service.
4) Unexpected answer from sub-RTU
5) Next level router-RTU does not answer.
6) Next level router-RTU out of service.
7) Unexpected answer from next level router-RTU
8) Command/FTAB buffer overflow in router-RTU
4.3.3.2 RTU status responses

TSTA Terminal status message. Limited functionality.
The following TSTA flags are implemented :
ID = 3 D0 (subordinate RTU is inoperable)
D1 (subordinate RTU is out of service)
D8 (This Central Station is primary CS)
4.4 $'$37$7,2172$/,(135272&2/6
In case the RTU equipment communicates according to an alien protocol, a protocol converter to/from
RP570 is the best solution. In the matter of protocol conversion is recommended to address the HPC563
RCS suppliers for advice.
It is important, of course, to specify clearly the functionality of the converter with respect to the actual
messages, see previous chapter.
3BSE 022 165R101 15

5. &20081,&$7,21&21),*85$7,216
5.1 *(1(5$/,1)250$7,21
The advantage of using the communication board CI535 in HPC 563 is that AC 400 without any special
measures can be linked to remote terminal units that use the RP570 protocol.
The figures below shows the configurations which are considered to be the most commonly used for hydro
power plant applications.
POINT-TO-POINT MULTIDROP
AC400
AC400 (RCS)
(RCS)
Modem
Modem
Modem
RP570 RP570 RTU210
AC400
Modem Modem
(CMN + CSN)
RTU210
Modem
RTU210
STA R S.P.I.D.E.R. NETWORK
AC400
(RCS)
S.P.I.D.E.R
.
RP571
Line split unit
Router-RTU AC400
Modem RP570
RTU200 (RCS)
RP570
RP570
Sub-RTU
Modem RTU210
Sub-RTU
RTU210
AC400
RTU210 RTU210
(CMN + CSN) Sub-RTU
AC400
(CMN + CSN)
Note that it is not recommended to use multidrop communication line because this configuration is yet not
implemented in the RCS system.
16 3BSE 022 165R101

5.2 $33/,&$7,210($685(6
The user should find out the intended communication alternative according to the figure above and make
sure that the V 24 ports of CI535 will be connected to the communication channels via suitable modems.
Wherever applicable the user shall order modems and connection cables from some well-established
manufacturer.
5.2.2 7KH56SURWRFRO
The CI535 board uses the RC232 protocol for communication through port 1. The port has a nine pin
female interface.
9 pin interface : 25 pin interface :
Pin # Signal name Pin # Signal name

1-------<--------Data carrier detect (DCD) 8-------<--------Data carrier detect (DCD)
2-------<--------Receive data (RXD) 3-------<--------Receive data (RXD)
3------->--------Transmitt data (TXD) 2------->--------Transmitt data (TXD)
4------->--------Data terminal ready (DTR) 20------>--------Data terminal ready (DTR)
5----------------Ground (GND) 7----------------Ground (GRD)
6-------<--------Data set ready (DSR) 6-------<--------Data set ready (DSR)
7------->--------Request to send (RTS) 4------->--------Request to send (RTS)
8-------<--------Clear to send (CTS) 5-------<--------Clear to send (CTS)
The most commonly used pins in the RC232 interface has the interpretation shown above. The direction
of the signal is seen from the communication port.
3BSE 022 165R101 17

6. '(),1,7,21$1')81&7,21$/,7<2)5(027(&21752/6,*1$/6
6.1 *(1(5$/,1)250$7,21
Definition of remote signals takes place via a set of pc-elements which constitute a cross reference table
between the databases in the local control system and the subordinate systems in the connected RTUs. The
remote signals are normally listed in a so-called point list where they are assigned a block or object
number and where applicable also a value number within the block. A complete point list is the necessary
basic document when the pc-programming work shall start.
The following SCADA pc-element types for defining remote control signals are found in the HPC563
RCS system :
- C-IND : 16 indication measurements
- C-AV : Analog value measurement
- C-DV : Digital value measurement
- C-PCV : Pulse counter value measurement
- C-OCMD : Object command
- C-RCMD : Regulation command
- C-SETP : Setpoint data
- C-GO : General output data
In addition to these eight types of SCADA pc-elements, a particular RCS system pc-element type,
C-CONF, is made for configuration, start-up and supervision of communication towards the connected
RTUs.
An RCS SCADA pc-element is identified by the combination of the following components :

Pc-element type : C-IND, C-AV, C-DV, C-PCV, C-OCMD, C-RCMD, C-SETP or C-GO.
RTU number (F1): an integer from 1 to 255
SUBRTU number (F2): an integer from 1 to 255
Block/object number (F3): an integer from 1 to 255
This means that each connected RTU can have maximum 255 PC-elements of each type.
18 3BSE 022 165R101

6.2 $33/,&$7,210($685(6
6.2.1 'DWDEDVHSRSXODWLRQ
6.2.1.1 General information
The general prerequisite is that the user has already filled in the local database in the AC400 node before
the RCS application starts.
A database element of the type MVIx 6 per RCS MVI board has to be created and properties have to be
filled in. The updating of the MVIx database element properties is dependent of the type of AC400
computer.
The requirements from the HPC 563 system are that all digital and analog signals that shall be event
recorded must be connected to DIC or AIC database elements. The DIC and AIC elements must not have
the property NORM_TR set to 1 because HPC 563 will generate virtual events.
6.2.1.2 Creating and updating MVIx in AC410
C o n n e c t io n o f A d v a n t S t a t io n 1 0 0 E S
P r o g ra m C a r d In te r fa c e C o n n e c t io n o f M a s t e r V ie w 3 2 0
fo r s y s te m s o ftw a re
x x x x x x x xx x x x x x x xx x x x x x xx x x x x x x xx x x x x x x xx x x x x x x xx x x x x x x x x x x x x x xx x x x x x x xx x x x x x x
x xx x x x x x x x x x x x xx x x xx x x x x xxxxxxxx x x x x xx x x xx x x x x x x x x x x x xx x

P r o c e s s o r M o d u le P M 1 5 0 S 1 0 0 P r o c e s s I/O
1 . . 4 in d ic a t e s s u b m o d u le p o s it io n s
C o n n e c t io n o f p r in t e r
Make the following command in order to create a MVIx database element:

#CRDB CI535
A database element MVIx will be created.
Fill in the properties due to the following description :

POSITION : The position of the CI535 board. Shall always be fixed to 1.
SUBPOS : The subposition of the CI535 board in the rack (1-4), see figure above.
NODE : The node number of the AC410 node in the MB300 network.
Should be fixed at 1 in case of no MB300 connection
NET1 : Not used. Should be fixed at 1.
SET_NET1 : Not used. Should be fixed at 1.
6 In AC410 maximum two MVI board can be used, x = 1 or 2.

In AC450 maximum five MVI board can be used, x = 1,2,3,4 or 5.
3BSE 022 165R101 19

6.2.1.3 Creating and updating MVIx in AC450
P r o g r am C a r d I n ter f a c e
f o r sy stem so f tw a r e
B o ar d su b p o si ti o n
PM PM SR 511 SR 511
510 510

V o l ta g e V o l ta g e
R eg u lato r A . R eg u l ato r A .
SB 511 SB 511 TC
520
(op-
tio n )
B ack up B ack up S u p er
P o w er P o w er v isio n
Supply A Supply B
( o p ti o n )
B o ard p ositio n
B u s ex ten sio n to S 1 0 0 I /O
C o n n ec ti o n o f A d v a n t S tatio n 1 0 0 E S
Make the following command in order to create a MVIx database element:

#CRDB CI535
A database element MVIx will be created.
Fill in the properties due to the following description :

POSITION : The position (1-8) of the CI535 board, see figure above. Choose a number
between 4 and 8 (Board position 1 and 2 are reserved for processor units,
while position 3 is reserved for system software and bus extension to S100
I/0).
SUBPOS : The subposition (1-2) of the CI535 board in the rack, see figure above.
NODE : The node number of the AC450 node in the MB300 network.
Should be fixed at 1 in case of no MB300 connection
NET1 : Not used. Should be fixed at 1.
SET_NET1 : Not used. Should be fixed at 1.
20 3BSE 022 165R101

6.2.2 +3&5&6SFSURJUDP
The user shall create and fill in the pc-elements which are required with regard to the point list. Below are
listed all pc-elements together with instructions for the data to be given by the user at each terminal.
The following rules should be followed when a RCS application is designed in order to obtain maximum
flexibility for supervision and maintenance of the RCS application :
All SCADA RCS pc-element related to one RTU should be gathered in one pc-program.
Each type of RCS SCADA pc-element should be gathered in their own control module.
The C-CONF pc-element should be gathered in a separate control module.
Note that from a technical point of view it is fully possible to distribute the pc-elements among existing
pc-programs. But, before such a decision is taken, the consequences with regard to technical
administration, maintenance and service should be considered carefully.
The rules below apply on the cyclicity of control modules containing HPC563 RCS pc-elements in order
to reduce the overall CPU-load caused by the pc-elements:
0LQLPXP 5HFRPPHQGHG
- Cyclicity of control module with C-CONF elements : 2000 2000
- Cyclicity of control module with C-IND elements 7: 500 1000
- Cyclicity of control module with C-AV elements 8: 500 1000
8
- Cyclicity of control module with C-DV elements : 500 2000
- Cyclicity of control module with C-PCV elements : 500 2000
- Cyclicity of control module with C-OCMD elements : 500 2000
- Cyclicity of control module with C-RCMD elements: 500 2000
- Cyclicity of control module with C-SETP elements: 500 2000
- Cyclicity of control module with C-GO elements: 500 2000
It is, of course, also possible to execute the RCS pc-element with a cyclicity faster than the recommended
values given above. Note however that the RCS pc-elements are quite load consuming and therefore must
the overall CPU-load in the AC400 node be carefully watched.
7 Note that transmission of indication events received from the underlying RTUs towards the Advant Operator Station (and
HPC563 RTU option) is not affected by the cyclicity of the C-IND pc-elements.
8 Note that most of the analog and digital values are subject to deadband handling in the RTUs anyway.
3BSE 022 165R101 21

6.2.2.2 HPC563 RCS system configuration

6.2.2.2.1 RCS system configuration (the C-CONF pc-element)
Summary :
The C-CONF pc-element is used to enable/disable the configuration of the RCS SCADA pc-elements and
to control and supervise the communication towards the underlying RTU. The functionality of the system
messages from the RCS system and the RCS test function are also controlled from C-CONF.
,WLVQHFHVVDU\WRSURJUDPRQH&&21)SFHOHPHQWSHU578 in the communication network connected to

the RCS MVI board(s) in the AC400 node.
,W LV SRVVLEOH WR FRQQHFW PD[LPXP 53 578V RU URXWHU578V WR RQH $& QRGH. Therefore
maximum 40 instances of the C-CONF pc-element can be present to configure one RTU or router-RTU
directly connected to the RCS MVI board(s) in the AC400 node.
,WLVSRVVLEOHWRFRQQHFWPD[LPXPVXE578VWRHDFKURXWHU578LQWKHV\VWHP. Therefore maximum

48 instances of the C-CONF pc-element can be present per router-RTU to configure sub-RTUs 9.
7KH FDOO SDUDPHWHU & LV XVHG WR GHILQH URXWHU578V ,I WKH FDOO SDUDPHWHU LV IL[HG DW WKH
FRUUHVSRQGLQJ578LVDURXWHU5787KHFDOOSDUDPHWHUWHUPLQDOVLVXVHGWRGHILQHZKHWKHURUQRWWKH
5&609,)URQW(QGVKDOOEHSULPDU\)URQW(QGIRUWKHURXWHU578LQWKH63,'(5QHWZRUN
,IWKH5&6DODUPDQGHYHQWKDQGOLQJVKDOOEHXVHGIRULQGLFDWLRQHYHQWVWHUPLQDOHYHQWVDQGRUWHUPLQDO
VWDWXVLQIRUPDWLRQUHFHLYHGIURPWKH578WKHFDOOSDUDPHWHU&PXVWEHIL[HGDW. The call parameter
inputs are used to define a cross reference table between event handling in the Advant system and related
process point addresses in the RTU.
2QH&&21)SFHOHPHQWSHU5&609,ERDUG must have the call parameter C3 fixed at 1. This element is

called the Master C-CONF element and defines communication parameters for the RP570/1 line such as
baudrate, duplex, time interval between TSI telegrams, time interval between polls and system message
and test information.
Note that only C-CONF pc-elements related to RTUs directly connected to the RCS MVI board (i.e. not
C-CONF elements related to sub-RTUs) can be defined as Master C-CONF pc-elements.
9 Note the C-CONF pc-element used to configure sub-RTUs must have the C1 and C3 parameters fixed at 0.
22 3BSE 022 165R101

&&21)&&&
) BOARD_N COMM_ACT
) RTU_N CONFCODE
) SUBRTU_N POS_ACK
) RTU_TYPE NEG_ACK
TERM_ACT
E_CONF TIMESYNC
P_CONF IND_ERR
ACT_COMM AV_ERR
FTAB_SEQ DV_ERR
EOP PCV_ERR
INT CMD_ERR
EOP_TIME SETP_ERR
INT_TIME GO_ERR
TGL_SCI TERM_ERR
TGL_TSI AC_FAIL
TGL_EOP BATT_LOW
TGL_INT SCI_ERR
TGL_HIST UPDATED
HISTYEAR COMDIAG1
HISTMNTH COMDIAG2
HISTDAY
HISTTIME ERRCODE
ERR
WSP
DSX
TGL_PRIM PRIMARY
PRIMSTRT
TGL_EVTR EVTR_ERR

TGL_DEL EVTR_WSP
PROC_N
BIT_N
EVENT_T
DBASE_ID
VALUE_TR
NAME_TXT
DESC_TXT
MMI_TYPE
MMI_NET
MMI_NOD
TGL_CPAR CPAR_ERR
BAUDRATE TESTMODE
DUPLEX
POLLTIME
TURNTIME
POLLTOUT
PREAMBL
POSTAMBL
TSI_TIME
TGL_SYSM
SYSMESS
ACT_TEST
TEST
3BSE 022 165R101 23

Code parameters :
Parameter : Interpretation : Permitted values :
C1 Call parameter for defining router-RTUs. 0, 1
0 = The corresponding RTU is an ordinary RTU. Default : 0
1 = The corresponding RTU is a router-RTU.
C2 Call parameter for defining alarm and event handling parameters. 0, 1
0 = no parameters Default : 0
1 = alarm and event handling parameters available
C3 Call parameter for defining communication line parameters for one 0, 1
RCS MVI board. Default : 0
0 = no communication parameters.
1 = communication parameters available (Master C-CONF)
Note that C-CONF pc-elements corresponding to sub-RTUs can

not be defined as Master C-CONF.
Function parameters :
No : Name : Type : Application :
F1 BOARD_N II Board identity number (1-5) eq. to MVIx.
F2 RTU_N II RTU identity number in the communication network (1-255).
RP570 : Ordinary RTU identity number.
RP571 : Router-RTU identity number in the comm. network
F3 SUBRTU_N II Sub-RTU identity number in the communication network (1-255).
RP570 : Set to 0 (not used).
RP571 : Sub-RTU identity number in the communication network.
Note ! If the RTU addressed is a router-RTU, the input must be

fixed at 0.
F4 RTU_TYPE II Selection of RTU type due to following choices :
0 = HPC563 RTU version 2.0/0 or later
1 = HPC560 RTU or HPC563 RTU version 1.0/0
2 = RTU 200
3 = RTU 210
4 = RTU 400
5 -> = arbitrary RTU. No function table parameter testing.
24 3BSE 022 165R101

Connections :
1 E_CONF IB Enable configuration. Dynamic input at which a 0 -> 1 transition
starts RCS configuration and a start-up sequence of the specified
terminal.
A 1 -> 0 change removes the configuration and stops the polling
of the terminal.
2 P_CONF IB Part configuration. Dynamic input at which a 0 -> 1 change
updates the pc-element workspace with new values read from the
inputs 4 - 10. A restart of CI535 is performed.
3 ACT_COMM IB Activate communication. Dynamic input at which a 0 -> 1
transition toggles the communication towards the RTU and
initiates a start-up sequence. A 1 -> 0 change removes the
communication towards the terminal.
Note ! This function is only available if the RCS system is
configured.
4 FTAB_SEQ IB Function tables are included/ignored in the starting sequence for the
terminal.
0 = ignore function tables in start-up sequence
1 = include function tables in start-up sequence
5 EOP IB Enable end of period reading of pulse counter values.
Common parameter to be included in all basic function tables for
pulse counter values (FT$PCV).
6 INT IB Enable intermediate reading of pulse counter values.
7 EOP_TIME IT Time period for end of period reading of pulse counters.
Resolution : 1 minute. Common parameter to be included in all
basic function tables for pulse counter values (FT$PCV).
8 INT_TIME IT Time period for intermediate reading of pulse counters. Resolution
: one second (for int_time <= 255 seconds) or one minute.
9 TGL_SCI IB Toggle status check instruction. Dynamic input (0 -> 1 transition)
to initiate the transmission of a SCI telegram to the terminal.
10 TGL_TSI IB Toggle time synchronization instruction. Dynamic input (0 -> 1
transition) to initiate the transmission of a TSI telegram to the
terminal.
11 TGL_EOP IB Toggle end of period reading. Dynamic input (0 -> 1 transition)
to initiate the transmission of a function command for end of
period reading to the terminal.
12 TGL_INT IB Toggle intermediate reading. Dynamic input (0 -> 1 transition) to
initiate the transmission of a function command for intermediate
reading to the terminal.
13 TGL_HIST IB Toggle historical pulse counter reading. Dynamic input (0 -> 1
transition) to initiate the transmission of a function command for
historical pulse counter reading to the terminal.
1RWH This function requires that a printer is attached to the

AC400 node .
3BSE 022 165R101 25

14 HISTYEAR II Year for read of historical pulse counters. (for instance 1996).
1RWH If the user want to write out a report which contains all
buffered pulse counter measurements in the RTU, the HISTYEAR
input must be fixed at 0.
15 HISTMNTH II Month for read of historical pulse counters. (1-12).
16 HISTDAY II Day for read of historical pulse counters. (1-31).
17 HISTTIME II Time for read of historical pulse counters. (1-12).
40 COMM_ACT OB Communication active. Output which is set to true when the
communication with the terminal is active.
41 CONFCODE OI Configuration code. Output specifying configuration progress and
adversity according to the CONFCODE table below.
42 POS_ACK OB The output is set to true when the terminal reports positive
acknowledgment after a FCOM or FTAB command. The output is
active in one execution cycle only.
43 NEG_ACK OB The output is set to true when the terminal reports negative
acknowledgment after a FCOM or FTAB command. The output is
44 TERM_ACT OB Terminal active. Output which is set to true if the terminal is in
active state.
TSTA ID=1 flag D8 is set.
45 TIMESYNC OB Time synchronization. Output which is set to true if the terminal is
time synchronized.
46 IND_ERR OB Indication error. Output which is set to true when at least one
indication is faulty.
47 AV_ERR OB Analog value error. Output which is set to true when at least one
analog value meas. Is faulty.
48 DV_ERR OB Digital value error. Output which is set to true when at least one
digital value meas. Is faulty.
49 PCV_ERR OB Pulse counter value error. Output which is set to true when at least
one pulse counter value measurement is faulty.
50 CMD_ERR OB Command output error. Output which is set to true when at least one
object or regulation command output is faulty.
HPC560/3 : No supervision of command outputs (output is
always false)
51 SETP_ERR OB Setpoint output error. Output which is set to true when at least one
setpoint output is faulty.
HPC560/3 : No supervision of setpoint outputs (output is always
false)
52 GO_ERR OB General output error. Output which is set to true when at least one
general output is faulty.
HPC560/3 : No supervision of general outputs (output is always
false)
53 TERM_ERR OB Terminal error. Output which is set to true when the RTU is reported
faulty.
HPC560/3 : No error-marking of terminal (output is always
false)
26 3BSE 022 165R101

54 AC_FAIL OB AC supply fail.. Output which is set to true when the AC supply in the
RTU fails and the RTU is running on battery supply.
false)
55 BATT_LOW OB Battery low.. Output which is set to true when the battery in the RTU
is low and the RTU is running on last battery reserve. Object
commands are not executed.
false)
56 SCI_ERR OB The output is set to TRUE when an error in a SCI-sequence is
detected, either are some process points not updated or signals from
unknown process points are received. The output is active in one
execution cycle only.
57 UPDATED OB Data acquisition pc-element updated. The output is set to true for
one execution cycle when a RCS SCADA pc-element related to the
RTU is updated with new information received from the RTU.
58 COMDIAG1 OI For system maintenance only !
59 COMDIAG2 OI For system maintenance only !
80 ERRCODE OI Output which shows the current state of the pc-element in the RCS
system. For error codes : see chapter Error codes in RCS pc-
elements.
81 ERR OB Output is set to true after a fatal error in the pc-element. The pc-
element has stopped its execution.
82 WSP OIL For system maintenance only !
83 DSX OI For system maintenance only !
100 TGL_PRIM IB Toggle primary command. Dynamic input (0 -> 1 transition) to

initiate the transmission of a function command to configure the
router-RTU to consider the HPC563 RCS Front End as primary
Front End in the S.P.I.D.E.R. system.
101 PRIMSTRT IB Primary at Start input. Fix input at 1 if the router-RTU shall
consider the HPC563 RCS Front End as primary Front End in the
S.P.I.D.E.R. system after a start-up sequence is performed towards
the router-RTU.
105 PRIMARY OB Primary. The input shows the state of the HPC563 RCS Front End
in the S.P.I.D.E.R. system. If the HPC563 RCS Front End is
regarded as primary Front End by the related router-RTU, the output
is fixed at 1.
110 TGL_EVTR IB Toggle of alarm event treatment cross reference information.

Dynamic input (0 -> 1 transition) to initiate the reading and storing
of inputs 102-121 10.
111 TGL_DEL IB Remove event treatment cross reference information. Dynamic input
(0 -> 1 transition) to reset the event treat handling information.
112 PROC_N II Process point identity number (0-255). The number can refer to the
block or object number of a process point, a terminal event identity
number (1-) or a terminal status identity number (0-4).
113 BIT_N II Bit number (1-.16). The number can refer to a measurement in a
indication block, to a terminal status flag or to terminal event
information..
10 For further information, see chapter ALARM AND EVENT HANDLING.
3BSE 022 165R101 27

114 EVENT_T II Event type. Definition of event type due to the following
interpretation :
1 = single indication, ON event
2 = single indication, OFF event
3 = double indication, ON event (01)
4 = double indication, OFF event (10)
5 = double indication, midposition event (00)
6 = double indication, midposition error event (11)
7 = terminal event telegram
8 = terminal status, ON event
9 = terminal status, OFF event
115 DBASE_N II Database identity number (1-2000). Each process point which shall
have RCS alarm and event handling, must be given an unique
database identity number. The same database identity number
must be used for the ON and OFF event.
Note that for handling of double indication events, three different

database identity numbers must be used, one for the ON and OFF
event, one for midposition event (00) and one for midposition error
event (11).
116 VALUE_TR II Value treat. Integer parameter (1-350) to be written into the
VALUE_TR property of the virtual alarm or event signal which is
transmitted to the Advant Operator Station.
117 NAME_TXT IA20 Name text. Text string of maximum 20 characters to be written into
the NAME property of the virtual alarm or event signal which is
transmitted to the Advant Operator Station.
118 DESC_TXT IA28 Description text. Text string of maximum 28 characters to be
written into the DESCR property of the virtual alarm or event signal
which is transmitted to the Advant Operator Station.
119 MMI_TYPE II Type of Man Machine Interface. The following choices are
available :
1: Advant Operator Station
2: HPC563 Local Event Printout Option
120 MMI_NET II Man Machine Interface network number on the MB300 network (0-
127).
121 MMI_NOD II Man Machine Interface node number on the MB300 network (0-
127).
130 EVTR_ERR OI Output shows a value <> 0 when an error is found in the current
event treat parameters. Convert the output integer to a hexadecimal
number. If a bit is true, the corresponding signal handling parameter
is faulty :
- bit 1 : = not used
- bit 2 : = PROC_N
- bit 3 : = BIT_N
- bit 4 : = EVENT_T
- bit 5 : = DBASE_N
- bit 6 : = VALUE_T
- bit 7 - 8: = not used
- bit 9 : = MMI_TYPE
- bit 10 : = MMI_NOD
- bit 11 : = MMI_NET
- bit 12 -16: = not used
131 EVTR_WSP OIL For system maintenance only !
28 3BSE 022 165R101

140 TGL_CPAR IB Toggle of communication parameters. Dynamic input (0 -> 1

transition) to initiate the restart of the MVI board with new
communication parameters (input 141-146).
Warning ! This input initiates a restart of the MVI board. After the
restart of the board, all connected RTUs must be started by means of
new start-up sequences.
141 BAUDRATE II Communication baudrate. Available baudrate are in the interval 150
- 19200, see table of available baudrates below.
142 DUPLEX IB Communication duplex type.
0 = Half duplex, RTS active at transmission
1 = Full duplex, RTS continuously active
143 POLLTIME IT Time between poll. The input specifies the time interval between
two consecutive data requests from the HPC563 RCS system.
Resolution : 0.1 second
0 = No limitations on poll speed.
144 TURNTIME IT Turnaround time. Time to wait as from the last bit in the command
until the first bit in the reply, i.e. the time-out interval the RCS MVI
board waits for a response from an RTU. Recommended value = 5
sec.
145 POLLTOUT IT Poll time-out. Specifies the time to wait for response from RTU
after data request command. Recommended value = 3 sec.
146 PREAMBL II Preamble delay. The input specifies a delay in bytes to wait before
the start of transmission of an arbitrary signal towards a terminal.
0 = No preamble delay.
Note ! Only to be specified <> 0 in case of half duplex.

147 POSTAMBL II Postamble delay. The input specifies a delay in bytes to wait after
the end of transmission of an arbitrary signal towards a terminal.
0 = No postamble delay.
Note ! Only to be specified <> 0 in case of half duplex.

148 TSI_TIME IT Time between TSI commands. The input specifies the time interval
between two consecutive TSI commands from the HPC563 RCS
system.
Requirement : TSI_TIME >= five minutes.
0 = No cyclical transmission of TSI telegrams from the HPC563
RCS system.
149 TGL_SYSM IB Toggle system message information. Dynamic input (0 -> 1 transition)
to initiate the reading of system message handling information from
the SYSMESS input.
150 SYSMESS II System message handling parameter for all system messages related to
the RCS systerm. The following choices are available :
0: No system messages are generated.
1: Only one system message per error/event is generated.
2: All system messages are generated.
10: Print system message buffer.
151 ACT_TEST II For system maintenance only !
152 TEST IIL For system maintenance only !
160 CPAR_ERR II Output shows a value <> 0 when an error is found in a

communication parameter. Convert the output integer to a
hexadecimal number. If a bit is true, the corresponding
communication parameter is faulty:
bit 1 = BAUDRATE
bit 2-16 = not used
3BSE 022 165R101 29

Tables :
CONFCODE table :
Codes during a successful configuration and start-up sequence :
= &RQWDFW LV HVWDEOLVKHG EHWZHHQ WKH &&21) SFHOHPHQW DQG WKH 5&6 V\VWHP VRIWZDUH 7KH &
&21)HOHPHQWLVUHDG\WRFRQILJXUH
= 7KH 5&6 V\VWHP VRIWZDUH KDV UHFHLYHG D VWDUW FRQILJXUDWLRQ FRPPDQG IURP WKH &&21) SF
HOHPHQWDQGD5&6FRQILJXUDWLRQLVLQSURJUHVV
= &RQWDFWLVHVWDEOLVKHGEHWZHHQWKHWZR5&6V\VWHPWDVNV5&6B:'DQG5&6B*&,
= 0HPRU\DUHDVIRUWKHLQWHUQDO5&6V\VWHPWDEOHVDUHDOORFDWHGDQGWKHWDEOHVDUHLQLWLDOL]HG
= 7KHFRQILJXUDWLRQRIWKH5&66&$'$SFHOHPHQWVFRQQHFWHGWRWKHWHUPLQDOKDVVWDUWHG
= 7KH SRLQWHUV WR WKH LQWHUQDO 5&6 V\VWHP WDEOHV DQ WR WKH &&21) ZRUNVSDFH DUH VXFFHVVIXOO\
WUDQVPLWWHGWRWKH5&6B*&,WDVN
= 7KHFRQQHFWLRQVEHWZHHQWKH&,1'$9SFHOHPHQWVDQGWKH',$,GDWDEDVHDUHFKHFNHGDQGQR
HUURUVZKHUHGHWHFWHG
= 7KH5&66&$'$SFHOHPHQWVDUHVXFFHVVIXOO\FRQILJXUHG
= 6WDUWXSVHTXHQFHWRZDUGVWKHWHUPLQDOLVVWDUWHG
= 6WDUWXSVHTXHQFHLVVXFFHVVIXOO\FDUULHGRXW7KHWHUPLQDOLVDFWLYDWHG
Error codes for the configuration and start-up sequence :

= 1RPRUH578VFDQEHLQWURGXFHGLQWKHQRGH!
= 1RDQVZHUIURPWKH5&6B*&,WDVNDIWHUDFRQILJXUDWLRQRUGHUIURPWKH5&6B:'WDVN
= 1RIUHHPHPRU\DUHDDYDLODEOHIRUWKHLQWHUQDO5&6V\VWHPWDEOHV
= 7KH5&6B*&,WDVNUHMHFWVDSRLQWHUWRDQLQWHUQDO5&6V\VWHPWDEOHRUWKH&&21)ZRUNVSDFH
= ,QWHUQDOFRQILJXUDWLRQFRPPDQGORVWGXHWRLQWHUQDOHUURUVLQWKHLQWHUIDFHEHWZHHQWKH&&21)
SFHOHPHQWDQGWKH5&6B:'WDVN
= (UURUGHWHFWHGLQWKHFRQQHFWLRQEHWZHHQ&,1'$9SFHOHPHQWVDQG',$,GDWDEDVH
0RVWFRPPRQHUURUUHDVRQ
$',&$,&GDWDEDVHHOHPHQWKDVEHHQFRQQHFWHGWRPRUHWKDQRQH&,1'UHVSHFWLYHO\&$9SF
HOHPHQWRXWSXW
= (UURULQ&&21)ZRUNVSDFHGXULQJ5&6V\VWHPFRQILJXUDWLRQ
= 1R$&V\VWHPUHVRXUFHVDYDLODEOHIRUVHQGLQJ'6;VLJQDOVGXULQJ5&6V\VWHPFRQILJXUDWLRQ
= 1R 0DVWHU &&21) SFHOHPHQW ZLWK & GHILQHG IRU WKH 5&6 09, ERDUG 7KHUHIRUH QR
FRPPXQLFDWLRQSDUDPHWHUVDUHDYDLODEOH
= 578LVLQDFWLYHDQGPXVWEHUHVWDUWHG
= 1RWSRVVLEOHWRHVWDEOLVKFRQWDFWFRQWDFWORVWZLWKWKH5&609,ERDUG
= 1RWSRVVLEOHWRHVWDEOLVKFRQWDFWFRQWDFWORVWZLWKWKHWHUPLQDOWKH578GRHVQRWUHVSRQGWR6&,
FRPPDQGV
= 1HJDWLYHDFNQRZOHGJPHQWDIWHUGHDFWLYDWLRQFRPPDQG)&20GHDFWLYDWH578
= 1HJDWLYHDFNQRZOHGJPHQWDIWHUGDWDEDVHYHUVLRQFRPPDQG)&20GDWDEDVHYHUVLRQ
= 1HJDWLYHDFNQRZOHGJPHQWDIWHUIXQFWLRQWDEOHFRPPDQG$V\VWHPPHVVDJHIURPWKH5&6
VRIWZDUHZLOOSRLQWRXWWKHIDXOW\IXQFWLRQWDEOH
= 1RUHVSRQVHIURPWKH5&6B*&,WDVNDIWHUIXQFWLRQWDEOHUHTXHVWFRPPDQGIURPWKH09,ERDUG
= 1RUHVSRQVHIURP578DIWHUIXQFWLRQWDEOHFRPPDQG
= 7KH578LVQRWUHVWDUWHGDIWHUDFROGVWDUWFRPPDQG
= (UURUGHWHFWHGLQLQWHUQDO5&6V\VWHPWDEOHGXULQJVWDUWXSVHTXHQFH
30 3BSE 022 165R101

= 1HJDWLYHDFNQRZOHGJPHQWDIWHUDFWLYDWLRQFRPPDQG)&20DFWLYDWH578
= (UURUGHWHFWHGLQFRPPXQLFDWLRQEDXGUDWHSDUDPHWHU7KHUHTXHVWHGEDXGUDWHLVQRWDYDLODEOH
= 1RPHPRU\DYDLODEOHLQWKHIUHHVSDFHSROORIWKH$&QRGHIRUDOORFDWLRQRIPHPRU\IRUWKH
LQWHUQDOVXE578LQIRUPDWLRQWDEOH
= 7KHFRPPXQLFDWLRQWRZDUGVWKHURXWHU578LVQRWLQQRUPDORSHUDWLRQWKHFRPPXQLFDWLRQ
WRZDUGVWKHVXE578VFDQQRWEHVWDUWHGXQWLOWKHFRPPXQLFDWLRQWRZDUGVWKHUHODWHGURXWHU578
LVLQQRUPDORSHUDWLRQ
$YDLODEOHEDXGUDWHV
150
300
600
1200
2400
4800
9600
19200
3BSE 022 165R101 31

6.2.2.3 Data acquisition

6.2.2.3.1 RTU indications (the C-IND pc-element)
Summary :
The C-IND pc-element is used to configure an indication measurement in a RTU and to receive the
following RP570 telegrams from the RTU:
- IDM, Indication Message without status (16 indications per message). The telegram is sent after a
change in an indication value.
- IDS, Indication Message with Status (16 indications per message). The telegram is sent after a
change in an indication status.
- ERMI, Event Recording Message for Indications (1 indication per message). A time-tagged ERMI
telegram is sent each time an indication change, which is defined for event treatment, has occurred.
All telegrams originating to and from a specific C-IND element are identified by means of the pc-element
router-RTU, sub-RTU and block identity number. Note in the case of RP570 protocol or if the C-IND pc-
element is related to a router-RTU , the sub-RTU identity number is fixed at 0.
&,1'&&
) RTU_N VAL1
) SUBRTU_N STATUS1
) BLOCK_N :
) APP_CONN VAL16
STATUS16
PC_CONF
UPD_REQ POS_ACKN
NEG_ACKN
ERRCODE
ERR
WSP
DSX
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
PRIORITY
START_CH
BLOCKED
IND_TYPE
S_M_MDPS
SER_1_0
SER_0_1
FLT_TIME
TRANS_CS
CONNTYPE
32 3BSE 022 165R101

Code parameters :
C1 Call parameter for basic function table. 0, 1
0 = no function table. Default : 1
1 = basic function table to a HPC563 RTU. Terminals 100, 103, 105,
106, 107, 108, 109, 111 and 120 are implemented.
C2 Call parameters for basic function table. 0, 1
0 = no function tables. Default : 0
1 = basic function tables to a conventional RTU (terminals 100-120
implemented)
Note : C1 must be fixed at 1.
F1 RTU_N II RTU identity number (1-255).
RP571 : Router-RTU identity number in the communication
network.
F2 SUBRTU_N II Sub-RTU identity number (1-255).
RP571 : Sub-RTU identity number in the communication
network.
Note ! If the indication block addressed is in a router-RTU, the
F3 BLOCK_N II Process point identity number (1-255)
F4 APP_CONN IB Application connection. The following choices are available :
0 = VALx outputs connected to DI database.
1 = No event handling. ERMI telegrams from the RTU
are ignored.
2-4 = Spare
5 = HPC563 RCS alarm and event handling.
Information from ERMI telegrams shall be
forwarded directly to the chosen MMI by means of
the HPC563 RCS alarm and event handling 11.
Connections :
1 PC_CONF IB Dynamic input (0 -> 1 transition) to initiate a configuration of the
pc_element after change of VAL output connections.
2 UPD_REQ IB Dynamic input (0 -> 1 transition) to initiate the sending of an RX
telegram to the RTU in order to update the C-IND output
information. The RTU respond the command by means of an IDS
telegram.
40 VAL1 OB Value of bit 1. First indication value output for connection to

DIC, DAT or pc-element.
41 STATUS1 OB Status of bit 1. The status is set to true if the indication bit 1 is
faulty or blocked.
: : : :
70 VAL16 OB Value of bit 16. Last indication value output for connection to
DIC, DAT or pc-element.
11 For further information, see chapter ALARM AND EVENT HANDLING.
3BSE 022 165R101 33

71 STATUS16 OB Status of bit 16. The status is set to true if the indication bit 16 is
faulty or blocked.
72 POS_ACKN OB The output is set to true when the terminal reports positive
acknowledgement after a FTAB command. The output is active
in one execution cycle only.
73 NEG_ACKN OB The output is set to true when the terminal reports negative
acknowledgement after a FTAB command. The output is active
elements.
100 TGL_FTAB IB Dynamic input (0 -> 1 transition) to initiate the sending of a basic
function table to the RTU.
101 BOARD II Type of board/connection in RTU.
RTU 400 : Type of circuit board :
1 = DSDI 110
2 = DSDI 120
32 = DSDI 150 mode 1
33 = DSDI 150 mode 2
RTU 200/210 : Local connection = 128 (H80)
Calculated values = 0
102 ADDRESS II Bus/connection address in RTU.
RTU 400 : Bus Address
RTU 200/210 : Local connection = Rack and slot
103 PRIORITY II Telegram priority (available levels : 1-3).
104 START_CH II First channel on DI-board for this block in RTU.
RTU 400 : DSDI 110 : 1,17
DSDI 120 : 1,17
DSDI 150 : 1,17,33..321
RTU 200/210 : Single ind. : 1,2,3,..,16
Double ind: : 1,3,5,..,15
105 BLOCKED IA Blocking/deblocking of individual value when corresponding bit
in the format is set to true respectively false
Format : bit 16 xxxx xxxx xxxx xxxx bit 1
Example : D=0001 0000 0000 0010, i.e. bit 2 and 13 are to be
blocked
106 IND_TYPE IA Indication type. Definition of single and double indications.
Double indication : 11
Single indication : 00 (always two by two)
01 and 10 are not accepted combinations
107 S_M_MDPS IA Suppression of momentary midposion. When the bits
corresponding to a double indication in the format are set to true,
reporting of middle positions lasting less than the suppression
time specified in the RTU, will be suppressed.
34 3BSE 022 165R101

108 SER_1_0 IA Sequential event recording at change 1 -> 0 12. Time tagging will
take place when the corresponding bit in the format is set to true.
Recommended setting : D = 1111 1111 1111 1111
109 SER_0_1 IA Sequential event recording at change 0 -> 1 12. Time tagging will
take place when the corresponding bit in the format is set to true.
Recommended setting : D = 1111 1111 1111 1111
110 FLT_TIME II Filter time for DI board in ms (1-255).
111 TRANS_CS IA Transmission to Central Station. FTAB property for transmission
of sequence of event recording to Front End.
112 CONNTYPE II Connection type in RTU.
RTU 200/210/400 : 0 = Local connection
1 = Satellite conn. (not RTU 200/210)
2 = Calculated (not RTU 400)
120 FTAB_ERR OI Output shows a value <> 0 when an error is found in a basic
function table parameter. Convert the output integer to a
hexadecimal number. If a bit is true, the corresponding function
table parameter is faulty:
bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = PRIORITY
bit 4 = START_CH
bit 5 = BLOCKED
bit 6 = IND_TYPE
bit 7 = S_M_MDPS
bit 8 = SER_1_0
bit 9 = SER_0_1
bit 10 = FLT_TIME
bit 11 = TRANS_CS
bit 12 = CONNTYPE
bit 13 = not used
bit 14 = not used
bit 15 = C-CONF input RTU_TYPE and FTAB_SEQ requires
that C1/C2 = 1
bit 16 = C-CONF input FTAB_SEQ requires that C1 = 1 or
C/C2 = 1.
6.2.2.3.2 RTU analog values (the C-AV pc-element)
Summary :
The C-AV pc-element is used to configure an analog value measurement in a RTU and to receive the
- AVM, analog value message without status. The measurement value of an analog block is
transmitted when the value has exceeded the deadband of the measurement.
- AVS, analog value message with status. An AVS telegram with measurement value and status
information is transmitted if the measurement value breaks a defined limit or after a change of
measurement quality (error-marking).
- ERMA, event recording message, analog measurement. An ERMA telegram with time-tagged
information about an analog measurement is transmitted after the measurement value having
broken a defined limit or the measurement having been error-marked in the RTU.
12 If sequence event recording shall be used, the RCS system requires that both change 1 -> 0 and 0 -> 1 must be activated.
3BSE 022 165R101 35

Alarm and warning limits for analog measurements are sent to the RTU by means of FTABs or can be
written directly into the RTUs database.
All telegrams originating to a specific C-AV element are identified by means of the pc-element router-
RTU, sub-RTU and block identity number. Note in the case of RP570 protocol, the sub-RTU identity
number is fixed at 0.
&$9&&&
) RTU_N VAL
) SUBRTU_N STATUS
) BLOCK_N
) APP_CONN VALUE_H2
VALUE_H1
PC_CONF VALUE_L1
UPD_REQ VALUE_L2
RANGEMIN
RANGEMAX POS_ACKN
CONV_PAR NEG_ACKN
ERRCODE
ERR
WSP
DSX
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
CHANNEL
BACKCYCL
CONV_CAT
PRIORITY
BLOCKED
SER
LP_SER
LPB_SER
TRANS_CS
SCANCYCL
ABSDEADB
DEADBAND
DB_UPD
DISTFREQ
FILTFACT
CONNTYPE
TGL_LIM LIM_ERR
EN_H2
HI_LIM2
EN_H1
HI_LIM1
EN_L1
LO_LIM1
EN_L2
LO_LIM2
HYST
36 3BSE 022 165R101

Code parameters :
1 = basic function table to a HPC563 RTU. Terminals 100, 106,
107, 111, 113, 114 and 120 are implemented
are implemented).
C3 Call parameter for extended function table, limit supervision 0, 1
1 = extended function table, limit supervision to all RTU types
(terminals 130-140 are implemented)
Note : C3 must be fixed at 1 to insure correct handling of analog
time-tagged events received from the RTU in ERMA telegrams.
RP571 : Router-RTU identity number in the communication
network.
network.
Note ! If the analog value measurement addressed is in a router-
RTU, the input must be fixed at 0.
F4 APP_CONN IB Application connection. The following choices are available :
0 = VAL outputs connected to an AI database element.
1 = No event handling. ERMA telegrams from the RTU
are ignored.
3BSE 022 165R101 37

Connections :
1 PC_CONF IB Configuration of pc_element after change of VAL output
connections.
telegram to the RTU in order to update the C-AV output
information. The RTU respond the command by means of an
AVS telegram.
3 RANGEMIN II Range minimum. Input for specification of minimum of measured
value. The input is used for scaling of the analog measured
values.
4 RANGEMAX II Range maximum. Input for specification of maximum of
measured value. The input is used for scaling of the analog
measured values.
5 CONV_PAR II Conversion parameter. Description of measured value input
characteristics. The input is used for scaling of the analog
measured values. See conversion parameter table below.
40 VAL OR Value output for connection to AIC, DAT or pc-element.

41 STATUS OB Status. The status is set to true if the analog measurement is faulty
or blocked.
42 VALUE_H2 OB Value > High limit 2 (alarm limit). The output is set to true when
the measured value is higher than the high alarm limit defined in
the RTU.
43 VALUE_H1 OB Value > High limit 1 (warning limit). The output is set to true
when the measured value is higher than the high warning limit
defined in the RTU.
44 VALUE_L1 OB Value < Low limit 1 (warning limit). The output is set to true
when the measured value is lower than the low warning limit
defined in the RTU.
45 VALUE_L2 OB Value < Low limit 2 (alarm limit). The output is set to true when
the measured value is lower than the low alarm limit defined in
the RTU.
acknowledgment after a FTAB command. The output is active in
one execution cycle only.
acknowledgment after a FTAB or RX command. The output is
elements.
101 BOARD II Type of board/connection in RTU :
10 = DSAI 110
11 = DSAI 120
12 = DSAI 130
RTU 200/210 : Local connection = 168 (HA8)
38 3BSE 022 165R101

102 ADDRESS II Bus/connection address in RTU :

103 CHANNEL II Channel number within board for this measured value :
RTU 400 : DSAI 110 = 1-32
DSAI 120 = 1-32
DSAI 130 = 1-16
RTU 210 : 1-6
RTU 200 : 1-8
104 BACKCYCL II Background cycle for this measured value :
RTU 400 : No selection of backgr. Cycle = 0
RTU 200/210 : See background cycle table.
105 CONV_CAT II Conversion category. To be fixed at 0 (ordinary analog input).
107 BLOCKED IB Blocking/deblocking of measured analog value
0 = the measured value is deblocked
1 = the measured value is blocked
108 SER IB Choice to activate/deactivate the sequential event recording in the
RTU :
0 = the sequential event recording is deactivated
1 = the sequential event recording is activated
109 LP_SER IB Local printout of sequence event recording.
110 LPB_SER IB Local printout of sequence event recording only if communication
is lost.
111 TRANS_CS IB FTAB property for transmission of sequence event recording to
RCS system
112 SCANCYCL II Scan cycle (time between A/D conversion) for this measured
value : See scan cycle table.
113 ABSDEADB IB Absolute deadband.
0 = deadband is the reference value for an integrator algorithm.
1 = deadband is an absolute value for deadband supervision..
114 DEADBAND II Deadband (threshold) in percent of measured value range for
report to FE (>= 0).
115 DB_UPD IB Database update :
RTU 200/210/400 : 0 = the RTUs database is updated only when the
MV shall be reported
1 = update RTUs database according to
scancycle.
116 DISTFREQ II Frequency of disturbances.
RTU 200/210/400 : 0 = 50 Hz
1 = 60 Hz
2 = 50 Hz
3 = 16 2/3 Hz
117 FILTFACT II Filter factor for the software filter algorithm.
RTU 400 : 0 - 127 (0 = no smoothing)
RTU 200/210 : 0, 1, 2, 4 ,8, 16, 32, 64, 128
(0 and 1 = no smoothing)
118 CONNTYPE II Connection type in RTU.
3BSE 022 165R101 39

bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = CHANNEL
bit 4 = BACKCYCL
bit 5 = CONV_PAR
bit 6 = PRIORITY
bit 7 = not used
bit 8 = DISTFREQ
bit 9 = FILTFACT
bit 10 = CONNTYPE
bit 11 = not used
bit 12 = SCANCYCL
bit 13 = not used
bit 14 = DEADBAND
bit 15 = C-CONF input RTU_TYPE and FTAB_SEQ
requires that C1/C2 = 1
bit 16 = C-CONF input FTAB_SEQ requires that
C1 = 1 or C/C2 = 1.
130 TGL_LIM IB Dynamic input (0 -> 1 transition) to initiate the sending of an

extended function table, limit supervision to the RTU.
131 EN_H2 IB Enable high limit 2.
132 HI_LIM2 II High limit 2, i.e. high alarm limit.
133 EN_H1 IB Enable high limit 1.
134 HI_LIM1 II High limit 1, i.e. high warning limit.
135 EN_L1 IB Enable low limit 1.
136 LO_LIM1 II Low limit 1, i.e. low warning limit.
137 EN_L2 IB Enable low limit 2.
138 LO_LIM2 II Low limit 2, i.e. low alarm limit.
139 HYST II Hysteresis.
140 LIM_ERR OI Output shows a value <> 0 when an error is found in an extended
bit 1 = not used
bit 2 = HI_LIM2
bit 3 = not used
bit 4 = HI_LIM1
bit 5 = not used
bit 6 = LO_LIM1
bit 7 = not used
bit 8 = LO_LIM2
40 3BSE 022 165R101

Tables :
Background cycle table :

0 = No background transmission
1 = 10 seconds
2 = 20 seconds
3 = 30 seconds
4 = 1 minute
5 = 2 minutes
6 = 3 minutes
7 = 5 minutes
8 = 10 minutes
9 = 15 minutes
10 = 20 minutes
11 = 30 minutes
12 = Spare
13 = Spare
14 = Spare
15 = Spare
Conversion parameters table :

Supported by
Input : RangeMin : RangeMax : Unit : 400 200 210 HPC560/3
00 = -10 -> 10 V x x x
01 = -5 -> 5 V x x
02 = - 2.5 -> 2.5 V x x
03 = - 1.25 -> 1.25 V x x
04 = 0 -> 10 V x x x
05 = 0 -> 5 V x x
06 = 0 -> 2.5 V x x
07 = 0 -> 1.25 V x x
08 = 2 -> 10 V x x
09 = 1 -> 5 V x
10 = 0.5 -> 2.5 V x
11 = 0.25 -> 1.25 V x
17 = - 20 -> 20 mA x x x x
18 = - 10 -> 10 mA x x x x
19 = -5 -> 5 mA x x x x
21 = 0 -> 20 mA x x x
22 = 0 -> 10 mA x x x
23 = 0 -> 5 mA x x x
25 = 4 -> 20 mA x x x
26 = 2 -> 10 mA x x
27 = 1 -> 5 mA x x
31 = -1 -> 1 V x x x
32 = - 2.5 -> 2.5 mA x x x
35 = 0 -> 1 V x x
36 = 0 -> 2.5 mA x x
39 = 0.2 -> 1 V x
40 = 0.5 -> 2.5 mA x
3BSE 022 165R101 41

Scan cycle table :

1 = 0.1 seconds (not RTU 200/210)
2 = 0.5 seconds (not RTU 200/210)
3 = 1.0 seconds
4 = 2.0 seconds
5 = 4.0 seconds
6 = 8.0 seconds
7 = 30.0 seconds
8 = 1 minute
6.2.2.3.3 RTU digital values (the C-DV pc-element)
Summary :
The C-DV pc-element is used to configure a digital value measurement in a RTU and to receive the
- DVM, Digital Value Message. The measurement value with status is transmitted from the RTU when
the measured value has exceeded the deadband defined in the RTU and after a change in status of the
measurement.
All telegrams originating to a specific C-DV element are identified by means of the pc-element router-
ERMD (Event Recording Message, Digital value) is not handled by the RCS software.
&'9&&
) RTU_N VAL
) SUBRTU_N STATUS
) BLOCK_N
POS_ACKN
UPD_REQ NEG_ACKN
ERRCODE
ERR
WSP
DSX
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
PRIORITY
BLOCKED
START_CH
DEADBAND
SCANCYCL
PFORMAT
NOOFBITS
CONNTYPE
42 3BSE 022 165R101

Code parameters :
104, 106a 108 and 120 are implemented
are implemented)
RP571 : Sub-RTU identity number in the communication network.
Note ! If the digital measurement addressed is in a router-RTU, the
Connections :
telegram to the RTU in order to update the C-DV output
DVM telegram.
40 VAL OIL Value. Value output for connection to DAT or pc-element.
41 STATUS OB The status is set to true if the digital value is faulty or blocked.
80 ERRCODE OI Output which shows the current state of the pc-element in the
RCS system. For error codes : see chapter Error codes in RCS
pc-elements.
1 = DSDI 110
2 = DSDI 120
3 = DSDI 131
4 = DSDI 141
3BSE 022 165R101 43


104 BLOCKED IB Blocking/deblocking of measured digital value
105 START_CH II Start channel on RTU DI-board for LSB.
RTU 400 : DSDI 110 : 1,17
DSDI 120 : 1,17
DSDI 131 : 1
DSDI 141 : 1
RTU 200/210 : 1, 9 (only 8 bit value)
106 DEADBAND II Deadband for report to FE (>= 0).
RTU 200/210/400 : Relevant when PFORMAT = 2 (4 dec. BCD)
HPC560/3 : See table of allowed deadbands.
107 SCANCYCL II Scan cycle (time between scanning of the input value) for this
measured value :
RTU 200/210/400 : See scan cycle table.
108 PFORMAT II Format code of input data :
0 = Transparent data
1 = Spare
2 = 4 decades BCD
3-15 = Spare
109 NOOFBITS II Number of bits in DVM/DVL telegram (8, 16 or 32)
Note : 8 and 32 are not supported by RTU400/HPC560/3
110 CONNTYPE II Connection type in RTU :
bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = PRIORITY
bit 4 = not used
bit 5 = START_CH
bit 6 = DEADBAND
bit 7 = SCANCYCL
bit 8 = PFORMAT
bit 9 = NOOFBITS
bit 10 = CONNTYPE
bit 11-14 = not used
that C1/C2 = 1
bit 16 = C-CONF input FTAB_SEQ requires that
C1 = 1 or C/C2 = 1.
44 3BSE 022 165R101

Tables :
Scan cycle table :
1 = 0.1 seconds
2 = 0.5 seconds
3 = 1.0 seconds
4 = 2.0 seconds
5 = 4.0 seconds
6 = 8.0 seconds
7 = 30.0 seconds (not RTU 200/210)
8 = 1 minute (not RTU 200/210)
9 = 25.5 seconds (not RTU 400)
The input value must be stable for two consecutive scanning to be treated further. Therefore the
SCANCYCL parameter also implicitly gives the settling time.
6.2.2.3.4 RTU pulse counter values (the C-PCV pc-element)
Summary :
The C-PCV pc-element is used to configure a pulse counter value measurement in a RTU and to receive
the following RP570 telegrams from the RTU:
- PCM, Pulse Counter Message. The measurement value with status is transmitted from the RTU at the
end of intermediate and end-of-period intervals and after a change in status of the measurement. A
PCM telegram contains information of the measurement value, type, status, parity, time, date and
quality.
All telegrams originating to a specific C-PCV element are identified by means of the pc-element router-
&3&9&&
) RTU_N NEW_VAL
) SUBRTU_N L_R_EOP
) BLOCK_N L_R_INT
DAY
UPD_REQ HOUR
MINUTE
SECOND
STATUS
RESTART
NEW_TIME
INV_TIME
POS_ACKN
NEG_ACKN
ERRCODE
ERR
WSP
DSX
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
CHANNEL
PRIORITY
BLOCKED
LP_EOP
LPB_EOP
SAVE_INT
RED_FACT
CLR_EOP
CONNTYPE
3BSE 022 165R101 45

Code parameters :
105, 110 and 120 are implemented.
are implemented).
network.
Note ! If the digital measurement addressed is in a router-RTU,
the input must be fixed at 0.
Connections :
telegram to the RTU in order to update the C-DV output
PCM telegram.
40 NEW_VAL OIL New value strobe pulse

41 L_R_EOP OIL Last reported end-of-period value.
42 L_R_INT OIL Last reported intermediate value.
43 DAY OI Day of last reported measurement. The day is to be interpreted as
day of current month (1-31).
44 HOUR OI Hour of last reported measurement (0-23).
45 MINUTE OI Minute of last reported measurement (0-59).
46 SECOND OI Second of last reported measurement
47 STATUS OB The status is set to true if the pulse counter measurement is faulty
or blocked.
48 RESTART OB The output is set to true if the pulse counter is restarted (at restart
of the RTU or deblocking of pulse counter block).
49 NEW_TIME OB The output is set to true if the time in the terminal is significantly
changed (corrected).
RTU 400 : >= 1 minute
RTU 200/210 : >= 5 seconds
HPC560/3 : >= 1 minute
50 INV_TIME OB The output is set to true if the time in the message is invalid.
46 3BSE 022 165R101

pc-elements.
RTU400: Type of circuit board,
25 = DSDP 110
26 = DSDP 115
RTU400: Bus Address
103 CHANNEL II Channel number within board for this value.
RTU400: 1 - 28
RTU 200/210 : 1 - 16
105 BLOCKED IB Blocking/deblocking of measured pulse counter value
106 LP_EOP IB Local printout of EOP readings.
107 LPB_EOP IB Local printout of EOP readings only if comm. is lost
108 SAVE_INT IB Save INT readings even if communication is down.
109 RED_FACT II Reduction factor for spont. Transmission of PCVs on local buss.
110 CLR_EOP IB Clear end of period. Input which is set to true if the counter shall
be cleared after end-of-period reading.
120 FTAB_ERR OI Output shows a value <> 0 when an error is found in a basic function
table parameter. Convert the output integer to a hexadecimal number. If
a bit is true, the corresponding function table parameter is faulty:
bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = CHANNEL
bit 4 = PRIORITY
bit 5-8 = not used
bit 9 = RED_FACT
bit 10 = not used
bit 11 = CONNTYPE
C1/C2 = 1.
3BSE 022 165R101 47

REMARKS
The following common function table parameters for pulse counter value handling shall be defined in the
C-CONF pc-element:
- EOP (IB) Enable/disable end-of-period pulse counter reading.
- INT (IB) Enable/disable intermediate pulse counter reading.
- EOP_TIME (IT) End-of-period pulse counter reading interval
- INT_TIME (IT) Intermediate pulse counter reading interval
6.2.2.4 Process commands
6.2.2.4.1 RTU object command (the C-OCMD pc-element)
Summary :
The C-OCMD pc-element is used to configure an object command in the RTU and to transmit the
following RP570 process command telegrams to the RTU :
- SELECT, Check back before execute command. The command is used to select an object on which a
execute command can be carried out.
- EXECUTE, Execute command. ON- or OFF-command to a selected object in the terminal.
- DESELECT, Command to inhibit a two-step command sequence. The effect of the DESELECT-
command is to de-select the object selected in the terminal.
- IMM_EXE, Immediate execute command. One-step ON- or OFF-commands which can be used both
as object and as regulation command. IXC used as object command always implies the selection of an
object in the terminal.
All commands are sent in dialogue mode.
The object in the terminal to be controlled is identified by means of the pc-element router-RTU, sub-RTU
and object identity number. Note in the case of RP570 protocol, the sub-RTU identity number is fixed at
0.
&2&0'&&
) RTU_N SELECTED
) SUBRTU_N POS_ACKN
) OBJECT_N NEG_ACKN
SELECT ERRCODE

EXECUTE ERR
DESELECT WSP
IMM_EXE DSX
ON_OFF
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
OBJBOARD
ONLY2STP
LP_CMD
CHK_CARD
CHK_CIRK
P_LENGTH
RESP_BLK
RESP_BIT
CONNTYPE
48 3BSE 022 165R101

Code parameters :
108 and 120 are implemented.
are implemented).
network.
Note ! If the object command addressed is in a router-RTU, the
F3 OBJECT_N II Process point identity number (1-255)
Connections :
1 SELECT IB Dynamic input (0 -> 1 transition) to initiate the sending of a
CBXC command. The terminal respond the command by means
of an CBR command response or an NXR acknowledgment.
2 EXECUTE IB Dynamic input (0 -> 1 transition) to initiate the sending of EXC
command to the terminal.. The terminal respond the command by
means of an EXR or NXR acknowledgment.
3 DESELECT IB Dynamic input (0 -> 1 transition) to initiate the sending of IHC
4 IMM_EXE IB Dynamic input (0 -> 1 transition) to initiate the sending of IXC
Note ! The terminal object must be configured to handle also one-
step commands (the CMD_TYPE input). Otherwise an NXR
acknowledgment is automatically transmitted from the terminal.
5 ON_OFF IB 0 = OFF command
1 = ON command
40 SELECTED OB The output is set to true when the terminal reports that the object is
selected after a CBXC command. The output is active until the
command sequence is finished, but maximum 30 seconds.
acknowledgment after an object command. The output is active
3BSE 022 165R101 49

acknowledgment after an object command. The output is active
pc-elements.
24 = DSD0 160
RTU 200 : Local conn. = 189 (HBD) = Matrix
= 181 (HB5) = 1 pole
= 182 (HB6) = 1,5 pole
= 183 (HB7) = 2 pole
RTU 210 : Local conn. = 117 (H75) = 1 pole
= 118 (H76) = 1,5 pole
= 119 (H77) = 2 pole
103 OBJBOARD II Object number within board for this command. One object
consists of two output channels.
RTU 400 : 1 - 128
RTU 200 : Matrix : 1-32
1 pole : 1-8
1,5 pole : 1-8
2 pole : 1-4
Calc. Val. : 0
RTU 210 : 1 pole : 1-4
1,5 pole : 1-4
2 pole : 1-2
Calc. Val. : 0
104 ONLY2STP IB 0 = Both one step and two step commands are allowed
1 = Only two step commands are allowed
105 LP_CMD IB Local printout of commands.
106 CHK_CARD IB Check card number.
107 CHK_CIRK IB Check circuit number.
108 P_LENGTH IT Pulse length for this object (0.1 second resolution).
109 RESP_BLK II Block number for response indication connected to this
command
110 RESP_BIT II Bit number for response indication connected to this command
50 3BSE 022 165R101

bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = OBJBOARD
bit 4 = not used
bit 5 = not used
bit 6 = CHK_CARD
bit 7 = CHK_CIRK
bit 8 = P_LENGTH
bit 9 = RESP_BLK
bit 10 = RESP_BIT
bit 11 = CONNTYPE
C1/C2 = 1.
6.2.2.4.2 RTU regulation command (the C-RCMD pc-element)
Summary :
The C-RCMD pc-element is used to configure a regulation command in the RTU and to transmit the
following RP570 process command telegram to the RTU :
- IMM_EXE, Immediate execute command. One-step ON- or OFF-commands which can be used both
as object and as regulation command. IMM_EXE used as regulation command does not imply the
selection of an object in the terminal.
The command is sent in dialogue mode.
0.
&5&0'&&
) RTU_N POS_ACKN
) SUBRTU_N NEG_ACKN
) OBJECT_N
ERRCODE
IMM_EXE ERR
ON_OFF WSP
DSX
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
OBJBOARD
P_LENGTH
CONNTYPE
3BSE 022 165R101 51

Code parameters :
1 = basic function table to a HPC563 RTU. Inputs 100, 104 and
120 are implemented.
are implemented).
network.
Note ! If the regulation command addressed is in a router-RTU,
the input must be fixed at 0.
Connections :
1 IMM_EXE IB Dynamic input (0 -> 1 transition) to initiate the sending of IXC
command to the terminal.. The terminal respond the command
by means of an EXR or NXR acknowledgment.
2 ON_OFF IB 0 = OFF command
1 = ON command
acknowledgment after the IXC command. The output is active in
acknowledgment after the IXC command. The output is active in
pc-elements.
52 3BSE 022 165R101


24 = DSD0 160
RTU 200 : Local conn. = 181 (HB5) = 1 pole
= 183 (HB7) = 2 pole
RTU 210 : Local conn. = 117 (H75) = 1 pole
= 119 (H77) = 2 pole
103 OBJBOARD II Object number within board for this command. One object
consists of two output channels.
RTU 400 : 1 - 128
RTU 200 : 1 pole : 1-8
2 pole : 1-4
Calc. Val. : 0
RTU 210 : 1 pole : 1-4
2 pole : 1-2
Calc. Val. : 0
104 P_LENGTH IT Pulse length for this object (0.1 second intervals).
bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = OBJBOARD
bit 4 = P_LENGTH
bit 5 = CONNTYPE
bit 6-14 = not used
that C1/C2 = 1
bit 16 = C-CONF input FTAB_SEQ requires that C1/(C2) =
1.
3BSE 022 165R101 53

6.2.2.4.3 RTU setpoint data (the C-SETP pc-element)
Summary :
The C-SETP pc-element is used to configure a setpoint object in the RTU and to transmit the following
RP570 process command telegram to the RTU :
- SPM, Setpoint message. A setpoint is transmitted to a specified object in the terminal. The setpoint
may be a real or an integer. The change of setpoint value does also generate a strobe pulse in the
terminal.
0.
&6(73&
) RTU_N POS_ACKN
) SUBRTU_N NEG_ACKN
) OBJECT_N
ERRCODE
SND_SETP ERR
SETP_VAL WSP
RANGEMIN DSX
RANGEMAX
SETPTYPE
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
CHANNEL
STROBBRD
STROBADR
STROBCHA
CONNTYPE
Code parameters :
C1 Call parameters for basic function tables. 0, 1
0 = no function tables (default value). Default : 0
are available)
54 3BSE 022 165R101

network.
Note ! If the setpoint process point addressed is in a router-
RTU, the input must be fixed at 0.
Connections :
1 SND_SETP IB Dynamic input (0 -> 1 transition) to initiate the sending of a
setpoint telegram to the terminal. The terminal respond the
command by means of an POS_ACKN or NEG_ACKN
acknowledgment.
Note ! The format of the setpoint is chosen by means of the
SETPTYPE input.
2 SETP_VAL IR Setpoint value to be transmitted to the terminal.
Note ! The input setpoint value is always a real, independent of the

setpoint format defined by the SETPTYPE input.
3 RANGEMIN IR Range minimum. Input for specification of minimum range. The
input is used for scaling.
4 RANGEMAX IR Range maximum. Input for specification of maximum range. The
5 SETPTYPE II Data type of setpoint message.
0 = Digital setpoint value (note that only setpoint values
between 0 and 2000 can be used, no scaling available).
1 = Analog unipolar or bipolar setpoint value (not RTU 210)
2 = Analog live zero setpoint value (only RTU 200)
acknowledgment after the SPM command. The output is active
acknowledgment after the SPM command. The output is active
pc-elements.
3BSE 022 165R101 55

5 = DSD0 110
6 = DSD0 120
17 = DSA0 110
18 = DSA0 120
19 = DSA0 130
RTU 200 : Local conn. = 185 (HB9) = digital
= 224 (HE0) = unip. Anal.
= 240 (HF0) = bip./unip. Analog
RTU 210 : Local conn. = 120 (H78) = digital
103 CHANNEL II Channel number within board for LSB (digital setpoint) or
analog channel within board.
RTU 400 : DSDO 110 : 1,17
DSDO 120 : 1,
DSAO 110 : 1-4
DSAO 120 : 1-8
DSAO 130 : 1-16
RTU 200 : Digital :1
Analog : 1-2
Calc. Val. : 0
RTU 210 : Digital :1
Calc. Val. : 0
104 STROBBRD II Type of board/connection for strobe pulse in RTU.
RTU 400 : Type of circuit board for strobe :
5 = DSD0 110
6 = DSD0 120
RTU 200 : Local connection = 178 (HB2)
RTU 210 : Local connection = 121 (H79)
105 STROBADR II Bus/connection address for strobe in RTU.
106 STROBCHA II Channel number within board for strobe pulse.
RTU 400 : DSDO 110 : 1-32
DSDO 120 : 1-16
RTU 200 : 1-16

RTU 210 : 9
56 3BSE 022 165R101

bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = CHANNEL
bit 4 = STROBBRD
bit 5 = STROBADR
bit 6 = STROBCHA
bit 7 = CONNTYPE
bit 8-13 = not used
bit 14 = SETPTYPE
bit 15 = not used
bit 16 = C-CONF inputs RTU_TYPE and FTAB_SEQ
requires that C1 = 1.
6.2.2.4.4 RTU general output data (the C-GO pc-element)
Summary :
The C-GO pc-element is used to configure a general output object in the RTU and to transmit the
following RP570 process command telegram to the RTU :
- GOM, General output message. General output data is transmitted to a specified object in the
terminal. The general output data may be real or 16 bit Boolean.
0.
&*2&
) RTU_N POS_ACKN
) SUBRTU_N NEG_ACKN
) OBJECT_N
ERRCODE
SND_GO ERR
B0_VAL WSP
B1_VAL DSX
:
:
B15_VAL
ANAVAL
RANGEMIN
RANGEMAX
OUT_FRMT
TGL_FTAB FTAB_ERR
BOARD
ADDRESS
CHANNEL
CONNTYPE
Code parameters :
C1 Call parameters for basic function tables. 0, 1
0 = no function tables (default value). Default : 0
are available).
3BSE 022 165R101 57

network.
Note ! If the general output data process point addressed is in a
router-RTU, the input must be fixed at 0.
Connections :
1 SND_GO IB Dynamic input (0 -> 1 transition) to initiate the sending of a general
output telegram to the terminal. The terminal respond the
command by means of an EXR or NXR acknowledgement.
Note ! The format of the general output data is chosen by means of
the OUT_FRMT input.
2 B0_VAL IB Bit 0 of Boolean input value to be transmitted to the
terminal.
3 B1_VAL IB Bit 1 of Boolean input value to be transmitted to the
terminal.
: : : :
17 B15_VAL IB Bit 15 of Boolean input value to be transmitted to
the terminal.
18 ANAVAL IR Analog general output value (real) to be transmitted
to the terminal.
19 RANGEMIN IR Range minimum. Input for specification of minimum range. The
20 RANGEMAX IR Range maximum. Input for specification of maximum range. The
21 OUT_FRMT II Data type of general output message.
1 = Unipolar analog output (not sub-RTU 210)
2 = Bipolar analog output (not RTU 210)
3 = Single indication output
4 = Double indication output
5 = 16 bit transparent digital output (8 bit in RTU 210)
6 = 16 bit transparent digital pulsed output, i.e. the outputs are active in
only one execution cycle of the R-GO element (only HPC560/3)
8 = Live zero analog output (0-2000) (only RTU 200)
acknowledgment after the GOM command. The output is active
acknowledgment after the GOM command. The output is active in one
execution cycle only.
elements.
58 3BSE 022 165R101

5 = DSD0 110
6 = DSD0 120
17 = DSA0 110
18 = DSA0 120
19 = DSA0 130
RTU 200 : Local conn. = 185 (HB9) = digital
= 224 (HE0) = unip. Anal.
= 240 (HF0) = bip./unip. Analog
RTU 210 : Local conn. = 114 (H72) = single ind.
= 120 (H78) = 8 bit
103 CHANNEL II Analog output channel within board or digital output channel for
LSB.
RTU 400 : Output format 1 :
DSAO 110 : 1-4
DSAO 120 : 1-8
DSAO 130 : 1-16
Output format 2 :
DSAO 110 : 1-4
DSAO 120 : 1-8
Output format 3 :
DSDO 110 : 1-32
DSDO 120 : 1-16
Output format 4 :
DSDO 110 : 1-31
DSDO 120 : 1-15
Output format 5 :
DSDO 110 : 1,17
DSDO 120 : 1
RTU 200 : Output format 1,2 : 1-2
Output format 3 : 1-16
Output format 4 : 1,3,5,7,9,11,13,15
Output format 5 : 1
Output format 8 : 1-2
RTU 210 : Output format 3 : 1-8
Output format 4 : 1,3,5,7
Output format 5 : 1
3BSE 022 165R101 59

120 FTAB_ERR OI Output shows a value <> 0 when an error is found in a basic function table
parameter. Convert the output integer to a hexadecimal number. If a bit is
true, the corresponding function table parameter is faulty:
bit 1 = BOARD
bit 2 = ADDRESS
bit 3 = CHANNEL
bit 4 = CONNTYPE
bit 5-13 = not used
bit 14 = OUT_FRMT
bit 15 = not used
bit 16 = C-CONF inputs RTU_TYPE and FTAB_SEQ
requires that C1 = 1.
60 3BSE 022 165R101

6.2.2.5 Error codes in RCS pc-elements
The general information about error status for the pc-elements is given by the terminal ERR, which is set to
true in case of fatal errors in the pc-elements, i.e. errors which causes the element to stop its execution. A
specification of the error in the form of an integer value is found on the SPA node ERRCODE. However,
certain information is presented at the ERRCODE SPA node even if ERR is set to false. An account for the
different codes is given below.
It is advisable to monitor the RCS pc-elements and possible system messages from the RCS software when
a pc-program including RCS pc-programs is started up for the first time. It exists a set of errors which are
detected at RCS pc-element start-up time which causes the element to stop its execution. The user must
watch the pc-element and system messages also during HPC563 RCS system configuration.
6.2.2.7 Error codes during normal operation (ERR = 0)

The following error codes shows the state of the pc-elements in the HPC563 RCS system during normal
operation. They are not result of errors in the RCS system.
ERRCODE during pc-element start-up (only after #DIBM) :

ERRCODE = 101 The pc-element has allocated workspace successfully
ERRCODEs during normal operation 13 :

ERRCODE = 1 The pc-element is configured.
ERRCODE = 2 The pc-element is under configuration.
ERRCODE = 3 Contact is established between the pc-element and the HPC563 RCS system software.
6.2.2.8 Error codes due to RCS system errors (ERR = 0)

These error codes are caused by detected faults in the RCS system.
ERRCODEs during pc-element start-up (only after #DIBM) :

ERRCODE = 70 No contact established with the HPC563 RCS software.
ERRCODEs during RCS system configuration/normal operation : 14

ERRCODE = 62 A logical record in the DI data base has been connected to more than one C-IND
block/bit combinations
ERRCODE = 63 A logical record in the AI data base has been connected to more than one C-AV
ERRCODE = 64 The C-IND element has been connected to a logical record out of range for the
HPC563 RCS system logical record > 4080)
ERRCODE = 65 The C-AV element has been connected to a logical record out of range for the HPC563
RCS system (logical record > 1000)
13 These error codes are not available in the C-CONF pc-element.

14 These error codes are only available in the C-IND and C-AV pc-elements.
3BSE 022 165R101 61

6.2.2.9 Error codes due to RCS system errors (ERR = 1)
ERRCODEs during pc-element start-up (only after #DIBM) :

ERRCODE = 11 No more RTUs can be introduced in the AC400 node (20 RTUs, which are directly
connected to the AC400 node, are already present in the AC400 node). The pc-element
has stopped its execution.
ERRCODE = 51 The same block number has been used for two pc-elements of the same type connected
to the same RTU. The pc-element has stopped its execution.
ERRCODE = 99 No free memory for internal CRT table element in the OHAB250 task.
There is not enough free space in the free space pool in the AC400 computer to allocate
an element in the internal CRT table in the OHAB250 task. Please free space from the
database or pc-program pool by means of a reconfiguration of the AC400 computer..
The pc-element has stopped its execution.
ERRCODE = 100 No workspace is allocated. The pc-element has stopped its execution.
ERRCODE after a fatal error in the pc-element workspace :

ERRCODE = 200 Fatal error in the pc-element workspace fingerprints (detected from pc-element
assembly part). The pc-element has stopped its execution.
ERRCODE = 83 Fatal error in the pc-element workspace(detected from pc-element Pascal part). The
pc-element has stopped its execution.
62 3BSE 022 165R101

&/2&.6<1&+521,=$7,21
7.1 *(1(5$/,1)250$7,21
The HPC 563 synchronizes the remote stations by means of the Time Sync Instruction (TSI) message,
which is sent out at regular intervals.
7.2 $33/,&$7,210($685(6
The user shall fill in the value of the terminal TSI_TIME of the master C-CONF pc-element to the desired
interval between time synchronization messages. The interval between TSI telegrams are then common
for towards all RTUs connected to the RCS MVI board.
It is however also possible to control the TSI sequences towards each terminal individually by means of
application programming. The TSI control algorithm must then be made with the aid of C-CONF input
TGL_TSI and by means of additional application programming. The master C-CONF input TSI_TIME
must be fixed at 0 if individual TSI sequences are used.
3BSE 022 165R101 63

8. 0$10$&+,1(&20081,&$7,21
8.1 $/$50$1'(9(17+$1'/,1*
AC400 DI
object handler
Advant Operator Station
AC400 AI object
handler
AC400
database Alarm and
(DIC and AIC event signals
database
elements)
Analog events
HPC563 53
AMPL-program RCS General
Indication events
with HPC563 RCS Communication
pc-elements Interface RTU
There exist two methods of handling of event information from the underlying RTUs in the HPC563 RCS
system.
The easiest method involve the use of one DIC/AIC database element per process point in the RTU which
shall have event treatment. The method makes use of the alarm and event handling in the AC400
operating system.
In addition there exist a special alarm and event handling for indication events and TSTA and TEV
information in the HPC563 RCS system. In this method no database elements in the AC400 node are
involved in the alarm and event handling. The HPC563 RCS system generates alarm or event signals
based on user-defined texts and event handling and transmits the virtual alarm and event signals to the
chosen Man Machine Interface (Advant Operator Station or HPC563 Local Event Printout function).
It is, of course, possible to use both methods of event handling simultaneously in a AC400 node.
Note that is a prerequisition for the alarm and event handling in the RCS system towards the Operator
station that sequence event recording is activated for both indication value changes 0 -> 1 and 1 -> 0 in
the connected RTU (i.e. indication function table parameters SER_1_0 and SER_0_1 must be fixed at 1
for all indications which shall have event and alarm handling in the Operator Station).
8.1.2 1RUPDOHYHQWKDQGOLQJ
8.1.2.1 Event handling description
The normal method of event treatment in the HPC563 RCS Option involve the use of one DIC/AIC
database element per process point in the RTU which shall have event treatment.
Event information received from the RTUs by means of ERMI and ERMA telegrams are used by the RCS
software as basis for generating virtual events in the Advant system. These virtual events has event
information (i.e. event type and time) fetched from the event messages and database information (i.e.
name, description and value treat) collected from the AC400 database. These virtual event signals are
transmitted to the ordinary DI and AI Object handler task in the AC400 operating system, which forward
the event information with additional database information to the target Advant Operator Station.
Seen from the Advant Station there is no difference between virtual events created by the RCS software
and common events generated in the AC400 database.
This function requires that the DIC/AIC database elements connected to SPA-IND/AV pc-elements do not
generate any events themselves.
64 3BSE 022 165R101

8.1.2.2 Application measures
DI Calculated AI Calculated
(8.21) (6.15)
NAME VAL NAME VAL

ACT CALC_VAL ACT CALC_VAL
BLOCKED ERR BLOCKED ERR
C-IND C-AV(0,0,1)
SCANT UPDATED SCANT UPDATED
TESTED TESTED RTU_N VAL
RTU_N VAL1 SUBRTU_N STATUS
SUBRTU_N STATUS1 BLOCK_N VALUE_H2
DESCR BLOCK_N VAL2 1 EN_H2 VALUE>H2
0 APP_CONN VALUE_H1
0 NORM_TR 0 APP_CONN STATUS2 675.9 HI_LIM2 VALUE>H1
VALUE_L1
... 1 EN_H1 VALUE>L1
... PC_CONF VALUE_L2
PC_CONF 633.0 HI_LIM1 VALUE>L2
UPD_REQ
UPD_REQ 1 EN_L1
Group Alarm ...
... 245.5 LO_LIM1
1 EN_L2 TGL_LIM LIM_ERR
210.1 LO_LIM2 EN_H2
1.1 HYST HI_LIM2
EN_H1
DESCR HI_LIM1
DISP_MAX EN_L1
DISP_MIN LO_LIM1
DEC EN_L2
0 NORM_TR LO_LIM2
...
Group Alarm
All indication and analog value process point in the RTU which shall have event treatment must be
connected to DIC or AIC database element in the AC400 database (i.e. the VALx outputs of the
C-IND/AV pc-element must be directly connected to the DI or AI database respectively).
The APP_CONN format parameter of the C-IND and C-AV must be fixed at 0 (database connection).
The NORM_TR property of the DIC and AIC database elements must be fixed at 0 (i.e. no additional
events are generated from the DI or AI database elements).
The database element properties NAME, DESCR and VALUE_TR (LIM_1_TR and LIM_2_TR for AIC
database elements) must be updated in order to define the alarm and event handling in the MMI system.
Note that it is also necessary to update the limit check properties (EN_H2, HI_LIM2, EN_H1, HI_LIM1,
EN_L1, LO_LIM1, EN_L2, LO_LIM2 and HYST) in order to be able to forward the correct limit value
to the MMI system when ERMA telegrams are handled in the RCS software.
8.1.3 +3&5&6DODUPDQGHYHQWKDQGOLQJ
8.1.3.1 Event handling description
There exist also a second alternative for handling of information received in ERMI, TSTA and TEV
telegrams in the HPC563 RCS system. The HPC563 RCS system is able to generate alarm or event signals
based on user-defined texts and event handling and transmit the alarm and event information directly to
the chosen Man Machine Interface (Advant Operator Station or HPC563 Local Event Printout function).
This method of alarm and event treatment is performed without connections to the local database in the
AC400 node. The method does, however, require that the user builds a cross reference table of event
treatment information by means of the C-CONF event treatment inputs (call parameter C2).
Seen from the Advant Station there is no difference between virtual alarm and event signals forwarded
directly from the HPC563 RCS system and signals from the DI and AI object handler tasks in the AC400
node.
3BSE 022 165R101 65

8.1.3.2 Application measures

8.1.3.2.1 General information
The events and terminal information transmitted from the RTUs to the HPC563 RCS system by means of
ERMI, TSTA and TEV telegrams contains normally process point address, event information and time
and date of the event. In addition to this information, an Advant system event signal to the operator
station contains additional process point information such as name (20 character text string) and
description (28 characters text string) and additional event treatment information (value treat) for the
event treatment in the target MMI system. Therefore a event treat cross reference table which contains
process point address and this additional event treatment information must be build in order to be able to
handle the events in the RCS system.
The cross references between event information and process point/terminal information are unique for
each RTU. Therefore one event treat cross reference table must be built per RTU which have process
points that should be handled by means of the RCS alarm and event handling.
The event treat cross reference list is build by means of the C-CONF inputs related to call parameter C2.
Note that an unique database identity number (DBASE_N) between 1 and 2000 must be assigned to
each process point/terminal information point in the RTU. This must be done in order to make it possible
for the Advant Operator Station to perform its alarm handling.
When an event treat cross reference table is written into the RCS system, it can be removed only by means
of toggling the TGL_DEL input or after a cold start of the AC400 node. The cross reference list can be
changed on-line.
The best way of writing the event treat cross reference table into a C-CONF pc-element is the generate an
application pc-program containing counter algorithms and additional MUX-I and MUXA-I pc-element.
1RWHWKDWWKHVWDUWRIWKHFRXQWHUDOJRULWKPPXVWEHGHOD\HGIRUDERXWVHFRQGVDIWHUWKHVWDUWRIWKH&
&21)SFHOHPHQW.
66 3BSE 022 165R101

8.1.3.2.2 Indication events (ERMI telegrams)

In order to be able to perform the RCS alarm and event handling for indication events the APP_CONN
format parameter of the C-IND pc-element must be fixed at 5.
There exist no limitations how C-IND pc-elements with APP_CONN fixed at 5 can be connected. A
typical solution is to connect the VALx outputs of the C-IND pc-elements to the DAT database in order to
be able to use the information received from the RTUs in other application programs in the AC400 node.
C-CONF(0,1,0)
BOARD_N
14 RTU_N
150 SUBRTU_N
RTU_TYPE
...
0 -> 1 TGL_EVTR EVTR_ERR

0 TGL_DEL EVTR_WSP
17 PROC_N
7 BIT_N
2 EVENT_T
201 DBASE_N
5 VALUE_TR
CHA10EW008XN11 NAME_TXT
CIRC BREAKER OFF DESC_TXT
1 MMI_TYPE
15 MMI_NET
8 MMI_NOD
Above is shown the cross reference between single indication OFF event related to indication block 17,
bit 7 generated in sub-RTU 150 connected to router-RTU 14 and information for the event treatment in
the local Advant system (value treat, name and description). An Advant Operator Station is used as target
MMI system and the MB300 network address MMI system is network 15, node 8.
C-CONF(0,1,0) C-CONF(0,1,0) C-CONF(0,1,0)
BOARD_N BOARD_N BOARD_N

14 RTU_N 14 RTU_N 14 RTU_N
150 SUBRTU_N 150 SUBRTU_N 150 SUBRTU_N
RTU_TYPE RTU_TYPE RTU_TYPE
... ... ...
0 -> 1 TGL_EVTR EVTR_ERR 0 -> 1 TGL_EVTR EVTR_ERR 0 -> 1 TGL_EVTR EVTR_ERR

0 TGL_DEL EVTR_WSP 0 TGL_DEL EVTR_WSP 0 TGL_DEL EVTR_WSP
25 PROC_N 25 PROC_N 25 PROC_N
11 BIT_N 11 BIT_N 11 BIT_N
3 EVENT_T 5 EVENT_T 6 EVENT_T
575 DBASE_N 576 DBASE_N 577 DBASE_N
67 VALUE_TR 78 VALUE_TR 78 VALUE_TR
CHA10EW008XDOUBLE NAME_TXT CHA10EW008XDOUBLE NAME_TXT CHA10EW008XDOUBLE NAME_TXT
POWER BREAKER ON DESC_TXT POWER BREAKER MP0 DESC_TXT POWER BREAKER MP1 DESC_TXT
1 MMI_TYPE 1 MMI_TYPE 1 MMI_TYPE
15 MMI_NET 15 MMI_NET 15 MMI_NET
8 MMI_NOD 8 MMI_NOD 8 MMI_NOD
The handling of double indications is somewhat more complicated. Maximum three database identity
numbers can be assigned for the handling of one double indication process point, i.e. one DBASE_N
(575) for the ON and OFF event, one DBASE_N (576) for midposition event (00) and one DBASE_N
(577) for midposition error event (11) as shown above.
3BSE 022 165R101 67

8.1.3.2.3 Terminal status information (TSTA telegrams)
In order to be able to perform the RCS alarm and event handling for terminal status information received
in TSTA telegrams from the RTU, the event treat cross reference information must be toggled into the
corresponding C-CONF pc-element. No further preparations are necessary.
C-CONF(0,1,0)
BOARD_N
14 RTU_N
150 SUBRTU_N
RTU_TYPE
...

0 TGL_DEL EVTR_WSP
1 PROC_N
10 BIT_N
8 EVENT_T
917 DBASE_N
159 VALUE_TR
TERMINAL STATUS NAME_TXT
RTU SYNCHRONIZED DESC_TXT
1 MMI_TYPE
15 MMI_NET
8 MMI_NOD
Above is shown the event treat cross reference information for terminal status telegram TSTA ID=1, bit
D9 (RTU is synchronized), when bit D9 is true (TSTA ON event). Note that the bit number in the TSTA
telegram (D9) correspond to BIT_N 10 in the cross reference table.
Note also that the event time transmitted to the MMI system is the AC400 time when the TSTA telegram
was received.
68 3BSE 022 165R101

8.1.3.2.4 Terminal event information (TEV telegrams)
In order to be able to perform the RCS alarm and event handling for terminal event information received
in TEV telegrams from the RTU, the event treat cross reference information must be toggled into the
corresponding C-CONF pc-element. No further preparations are necessary.
C-CONF(0,1,0)
BOARD_N
14 RTU_N
150 SUBRTU_N
RTU_TYPE
...

0 TGL_DEL EVTR_WSP
2 PROC_N
0 BIT_N
7 EVENT_T
1723 DBASE_N
243 VALUE_TR
TERMINAL EVENT NAME_TXT
SER OVERFLOW DESC_TXT
1 MMI_TYPE
15 MMI_NET
8 MMI_NOD
Above is shown the event treat cross reference information for terminal event telegram TEV 2 (SER
message overflow).
The BIT_N input terminal is used to define the INFO1 and INFO2 or INFO3 properties in the TEV
telegram. For use of the BIT_N input, see table below 15:
7HUPLQDOHYHQW %,7B1 ,1)2,1)2DQG,1)2LQ7(9 7LPH
WHOHJUDP
1 = RTU restarted 0 INFO 1 - 6 : Not used. AC400
2 = SER message overflow 0 INFO 1 - 6 : Date and time of TEV. RTU
3 = PMR freeze failed in 0 or INFO1 INFO1 = PMR group number AC400
database
4 = Queue for terminal event is 0 INFO 1 - 6 : Date and time of TEV. AC400
full
5 = Insufficient space in database 0 or INFO1 INFO1 = Logical file number AC400
6 = Prom version identification ----- Not available in RCS system -----
7 = Status of central ADC 0 or INFO1 INFO1 : 1 = erroneous AC400
2 = correct after error
8 = SER active again (after 0 INFO 1 - 6 : Date and time of TEV. RTU
overflow)
9 = Indication blocked due to 0 or INFO1 INFO1 : 1 = blocked AC400
oscillation or deblocked after or INFO1+2 2 = deblocked
oscillation stopped INFO2 : Block number
10 = Local block/deblock 0 or INFO1 INFO1 : 1 = blocked AC400
or INFO1+2 2 = deblocked
INFO2 : 0 = indication
1 = pulse counter value
2 = analog value
3 = digital value
11 = Insufficient memory for 0 or INFO1 INFO1 : PMR group number AC400
PMR or INFO1+2 INFO2 : Freeze group number
12 = Mobile radio connection 0 or INFO1 INFO1 : Line number AC400
failed
15 Note that INFO1 + 2 means that INFO1 is pleased in the most significant bit of BIT_N and INFO2 in the least significant bit.
3BSE 022 165R101 69

13 = Command failed 0 or INFO1 INFO1 : 1 = object command AC400

or INFO1+3 2 = regulation command
3 = setpoint command
4 = general output command
INFO3 : Object number
14 = Topology build up failed. ----- Not available in RCS system -----
Satellite function will not
start.
15 = FTAB loading failed 0 or INFO1 INFO1 : Line number AC400
or INFO1+2 INFO2 : RTU number
16 = Line statistics ----- Not available in RCS system -----
17 = Communication equipment 0 or INFO1 INFO1 : Line number AC400
faulty. Line will not be used. or INFO1+2 INFO2 : 1 = hardware error DSDX110
2 = hardware error DSCA114
18 = Communication inoperable 0 or INFO1 INFO1 : Line number AC400
or INFO1+2 INFO2 : 3 = no CTS from modem
4 = no DSR from modem
5 = CD from modem set
6 = no CTS from mobile radio
7 = mobile radio not connected
19 = Spare ----- Not available in RCS system -----
20 = At least one intermediate 0 INFO 1 - 6 : Date and time of TEV. RTU
pulse counter value is
discarded due to
communication bread
21 = At least one intermediate 0 INFO 1 - 6 : Date and time of TEV. RTU
pulse counter value is lost
due to full queue
22 = At least one end-of-period 0 INFO 1 - 6 : Date and time of TEV. RTU
pulse counter value is lost
due to full queue
23 = RTU restarted, conditional INFO 1 - 6 : Date and time of last loaded RTU
down line loading (FTAB or database
FE-dump)
24 = RTU operable, conditional 0 INFO 1 - 6 : Date and time of TEV. RTU
down line loading (FTAB or
FE-dump)
25 = Communication with sub- 0 or INFO1 INFO1 : Line number AC400
RTU is faulty. or INFO1+2 INFO2 : RTU number of faulty RTU
26 = Sub-RTU queue overflow 0 INFO 1 - 6 : Date and time of TEV. RTU
27 = Sub-RTU queue in normal 0 INFO 1 - 6 : Date and time of TEV. RTU
operation again
28 = Command initiated by 0 or INFO1 INFO1 : 1 = object command AC400
external host or INFO1+3 2 = regulation command
3 = setpoint command
4 = general output command
INFO3 : Object number
29 = State of hosts 0 or INFO1 INFO1 : State of host 1 (NFK) AC400
or INFO1+2 INFO2 : State of host 2 (CPA)
8.2 (9(17+$1'/,1*72:$5'6+3&/2&$/35,17287)81&7,21
There is no difference between virtual events created by the RCS software and common events generated
in the AC400 database. Therefore also virtual events from the HPC563 RCS system can be printed out by
the HPC563 Local Printout Function.
70 3BSE 022 165R101

9. +3&6<67(0,17(*5$7,21
9.1 ,17(*5$7,2172:$5'67+(+3&578237,21
HPC563 RTUDI
object handler HPC563 RTU 53
General
Communication
HPC563 RTUAI Interface
object handler S.P.I.D.E.R.
dispatch centre
AC400
database AMPL-program
(DIC and AIC with HPC563 RTU
database pc-elements
elements)
HPC563 53
AMPL-program RCS General
with HPC563 RCS Communication
pc-elements Interface RTU
There are two types of integration between the HPC563 RTU and RCS option which must be prepared by
means of application programming, event integration and function table integration.
The event integration towards the HPC563 RTU option comprise that indication and analog value events
from the RTUs connected to the HPC563 RCS system are handled as common events in the AC400
node 16.
To make the event integration possible, the handling of events from the RTUs in the HPC563 RCS system
must be adjusted to the event handling in the AC400 node as described in the chapter 8.1.2 Normal
event handling. The HPC563 RTU DI and AI object handlers operate in parallel with the AC400 DI and
AI object handlers and receive the same information as the ordinary object handlers.
The event integration requires that the HPC563 indication and analog value pc-elements R-IND and R-
AV are connected to the same DIC/AIC database element as the C-IND and C-AV pc-element
respectively.
The function table integration gives the user a possibility to automatically forward function table
information received from a dispatch center by means of the HPC563 RTU option to the HPC563 RCS
option and further to the underlying RTUs. This integration requires, however, that the HPC563 RCS and
RTU pc-element are gathered in the same pc-program in the AC400 node.
16Normal event handling must be performed for all process points which information also shall be forwarded to a Dispatch Center
by means of the HPC563 RTU option. 5&6DODUPDQGHYHQWKDQGOLQJFDQQRWEHXVHG.
3BSE 022 165R101 71

9.1.2 $SSOLFDWLRQPHDVXUHV
9.1.2.1 Event integration
R-AV
BLOCK_N
DEST_NET
DEST_NOD
0 APP_CONN
R-IND PC_CONF
VAL
BLOCK_N
STATUS
DEST_NET
RANGEMIN
DEST_NOD
RANGEMAX
2 APP_CONN
EN_H2
VLAUE_H2
EN_H1
PC_CONF
VALUE_H1
OSC_PROT
EN_L1
VALUE_L1
VAL1
EN_L2
STATUS1
VALUE_L2
...
...
DI Calculated AI Calculated
(8.21) (6.15)
NAME VAL NAME VAL

ACT CALC_VAL ACT CALC_VAL
BLOCKED ERR BLOCKED ERR
C-AV(0,0,1)
SCANT UPDATED C-IND(0) SCANT UPDATED
RTU_N VAL
TESTED TESTED
RTU_N VAL1 SUBRTU_N STATUS
SUBRTU_N STATUS1 BLOCK_N VALUE_H2
DESCR BLOCK_N Limit Check 0 APP_CONN
VAL2 VALUE_H1
0 NORM_TR APP_CONN VALUE_L1
0 STATUS2
... DESCR PC_CONF VALUE_L2
...
... PC_CONF DISP_MAX UPD_REQ ...
UPD_REQ DISP_MIN
Group Alarm
... DEC
0 NORM_TR TGL_LIM LIM_ERR
... 1 EN_H2
... HI_LIM2
Group Alarm 0 EN_H1
HI_LIM1
1 EN_L1
LO_LIM1
0 EN_L2
LO_LIM2
The figure above shows how a correct connection between a HPC563 RCS application and a HPC563
RTU application is carried out.
The value output of the RCS pc-elements are connected to the CALC_VAL output of the DIC/AIC
database element, while the value inputs of the RTU pc-elements are connected to the VAL output of the
same database element.
The status outputs of the RCS pc-elements are connected directly to the status inputs of the corresponding
RTU pc-elements.
In order to obtain correct functionality with regard to analog value status handling in the HPC563 RTU
system, the limit treat inputs and outputs of the C-AV pc-element must be connected to the corresponding
inputs of the R-AV pc-element as shown in the figure above (only limit H2 and L1 are active).
Note that the RTU R-IND pc-element must have the input format parameter APP_CONN fixed at 2 in
order to handle the events from the HPC563 RCS system properly. The RTU system R-AV pc-element
must, however, have the input format parameter APP_CONN fixed at 0.
72 3BSE 022 165R101

9.1.2.2 Function table integration
5,1'& &,1'&&

) BLOCK_N TESTMODE
) DEST_NET ) RTU_N VAL1
) DEST_NOD C_PRI ) SUBRTU_N STATUS1
) APP_CONN C_BLK ) BLOCK_N :
C_INDTP ) APP_CONN VAL16
PC_CONF C_SMMDPS STATUS16
OSC_PROT C_SER10 PC_CONF
VAL1 C_SER20 UPD_REQ POS_ACKN
STATUS1 C_TR_CS NEG_ACKN
: FTAB_STB
VAL16 ERRCODE
STATUS16 ERRCODE ERR
ERR WSP
TGL_TEST WSP
TEST_PAT DSX DSX
TEST_VAL TGL_FTAB FTAB_ERR
BOARD
TGL_FTAB FTAB_ERR ADDRESS
PRIORITY PRIORITY
BLOCKED START_CH
IND_TYPE
BLOCKED
S_M_MDPS
SER_1_0 IND_TYPE
SER_0_1 S_M_MDPS
TRANS_CS SER_1_0
SER_0_1
FLT_TIME
TRANS_CS
CONNTYPE
The figure above shows how the function table integration between the HPC563 RTU and RCS option can
be carried out. The current function table parameter outputs of the HPC563 RTU pc-elements are
connected to their corresponding function table parameter inputs of the HPC563 RCS pc-element.
In addition is the function table strobe output (FTAB_STB) of the HPC563 RTU pc-elements connected
to the toggle function table (TGL_FTAB) of the HPC563 RCS pc-element in order to be able to trig the
transmission of function table from the RCS system when new function table parameters are received from
the Dispatch center.
3BSE 022 165R101 73

5&635,17287)81&7,21
10.1 *(1(5$/,1)250$7,21
The RCS Printout function handles the following information from the RCS system :
Historical pulse counter reports (this function must be trigged by means of the C-CONF input
TGL_HIST).
The printout language is English.
The definition of a RCS Printout function requires modifications of the AC400 database.
10.2 $33/,&$7,210($685(6
10.2.1 0RGLILFDWLRQRISURSHUWLHVLQ$&GDWDEDVH
Some properties in the data base of AC400 must be modified in order to perform the HPC563 RCS
Printout function. The PRINTER_DESC and CAP1.1 files in the AC400 must be modified in order to
adapt to the desired printout format. The modifications require a MA220 or AS120ES connected to the
AC400.
10.2.2 0RGLILFDWLRQRIWKH35,17(5B'(6&ILOH
3ULQWHUSRVLWLRQ 0HDQLQJ 5HPDUNV

1 - 3 RTU identity number 1-255
4 - 7 Space
8 - 13 RCS pc-element type C-PCV
14 - 15 Space
16 18 Terminal process point identity number 1-255
19 23 Space
24 85 RCS communication system information
86 88 Space
89 96 Date YEAR-MNTH-DAY
97 98 Space
99 112 Time HOUR:MIN:SEC.FRAC
/DQGVFDSH is the only one available printout format available for the RCS Printout function. The user
must prepare the printout by means of editing the PRINTER_DESC file in the AC400 database.
The modification described below must be done in those AC400 nodes, which are to perform the RCS
Printout function. The modification 17 is done with a MA220 or AS120ES loaded with the system and
data base maintenance or expert commands.
Commands to be given via MA220/AS120ES:
# FINS 98,1 <CR>

# MPRO <CR>
17 Note ! The AC400 must be in configuration mode during the modification, otherwise the AC400 printout task will be aborted!
74 3BSE 022 165R101

Step through the table of properties and fill in data according to the desired printout format alternative:
3URSHUWLHV
1 = I*1 : 0
2 = BOOLEAN : TRUE
3 = BOOLEAN : FALSE
4 = BOOLEAN : FALSE
5 = I*1 : 1
6 = I*1 : 60
7 = I*2 : 120
8 = I*2 : 1200
9 (10:1)I*1 : -1
9 (10:2)I*1 : 0
9 (10:3)I*1 : 0
9 (10:4)I*1 : 0
9 (10:5)I*1 : 0
9 (10:6)I*1 : 0
9 (10:7)I*1 : 0
9 (10:8)I*1 : 0
9 (10:9)I*1 : 0
9 (10:10)I*1 : 0
10 (10:1)I*1 : 1
10 (10:2)I*1 : 8
10 (10:3)I*1 : 16
10 (10:4)I*1 : 24
10 (10:5)I*1 : 50
10 (10:6)I*1 : 74
10 (10:7)I*1 : 89
10 (10:8)I*1 : 99
10 (10:9)I*1 : 112
10 (10:10)I*1 : !
10.2.3 0RGLILFDWLRQRIWKH&$3ILOH
The CAP1.1 file must be modified 18 in order to start the AC400 printout software. In fact, the RCS
printout function uses the standard AC400 printout software to print out the system information .
Commands to be given via MA220/AS120ES:
# MDB CAP1.1 <CR>

? <CR>
? M <CR>
ACT=0 New value=1 <CR>
? END <CR>
18Note ! The modification described below must be done while the AC400 is in configuration mode, otherwise the AC400 printout
task will be aborted.
3BSE 022 165R101 75

11. +3&5&66<67(0+$1'/,1*
11.1 5&66<67(0&21),*85$7,21
When the AC400 database is populated and the RCS pc-program is programmed, the first configuration of
the RCS system can be started.
The first configuration of the RCS system should follow the following steps :
1) Start and control the RCS pc-elements related to one RTU at a time. Observe possible system
messages from the RCS software during pc-program start-up. Correct all mistakes before the RCS
system configuration is started.
2) Start RCS system configuration by means of setting the C-CONF input E_CONF to 1 and get dynamic
update of the C-CONF element on MA220/AS110ES. Check that the CONFCODE output counts
downwards.
3) If the CONFCODE output reaches 3, it means that there was not detected any errors in the RCS pc-
program that can influence on the configuration. However, normal operation is not reached until a
correct start-up sequence towards the RTU is executed and the CONFCODE output is fixed at 1.
4) If the CONFCODE output suddenly indicates a number higher than 10, an error has occurred and the
configuration is stopped. In cases of error, the RCS software will transmit a system message about the
source of the error. The mistake must be corrected before a new RTU configuration can be started.
5) Step 4 is repeated until the configuration and start-up of the HPC563 RCS system towards the RTU
functions perfectly.
Multiple RCS system configurations can be active at a time. The communication towards the RTUs must,
however, be activated for one RTU at the time. If the user tries to perform a start-up sequence towards
multiple RTUs simultaneously, the C-CONF elements, which are not related to starting RTU, are brought
into a wait state. When a start-up sequence is finished (with or without success), the communication
towards the next RTU in queue is activated.
The STATUS output of the RCS data acquisition pc-elements (C-IND, C-AV, C-DV and C-PCV) are
fixed at 1 (error-marked) during and after RCS system configuration. The error-marking of a pc-element
is removed when it receives the first message with process information from the related process point in
the RTU.
11.2 5(67$572)$&12'(
Restarting a AC400 node means
a hot init of the AC400 node
restart after AC400 power failure
restart after ECONFIG/DICONFIG command sequence (the AC400 node has been in configuration
mode)
After a restart of the AC400 node, the RCS SCADA pc-elements will be in not configured state and the
two RCS task, RCS_WD and RCS_GCI, will be initialized. The RCS_MVI board will be restarted.
A new RCS system configurations and start-up sequences will be started automatically from the
C-CONF pc-elements if the C-CONF E_CONF and ACT_COMM inputs are fixed at 1.
1RWHWKDWWKHYDOXHRXWSXWVRIWKH5&6GDWDDFTXLVLWLRQSFHOHPHQWZLOOEHSUHVHUYHGGXULQJWKHUHVWDUW
VHTXHQFH7KHVWDWXVRIWKH5&6GDWDDFTXLVLWLRQSFHOHPHQWVZLOOKRZHYHUEHIL[HGDWLHHUURU
76 3BSE 022 165R101

11.3 5(67$572)5&63&(/(0(176
Restarting of RCS pc-elements means
that a pc-program containing RCS pc-elements is restarted due to a EBM/DIBM/DBL sequence
that a pc-program or control module containing RCS pc-elements is restarted due to a BL/DBL
sequence
11.3.2 5HVWDUWRI5&66&$'$SFHOHPHQWV
Restart after a EBM/DIBM/DBL sequence :
After the EBM/DIBM/DBL sequence, , the RCS software immediately brings the RCS SCADA pc-
elements into the same state as before the EBM command.
The EBM/DIBM/DBL sequence of the RCS SCADA pc-elements does not influence of the state of the
RCS system.
When the SCADA pc-elements are activated by means of the DBL commands, the outputs are updated
with the freshest information received from the RTU.
Restart after a BL/DBL sequence :

A BL/DBL sequence has no influence on the state of the SCADA pc-elements.
When the SCADA pc-elements are activated by means of the DBL commands, the outputs are updated
11.3.3 5HVWDUWRI&&21)SFHOHPHQWV
Restart after a EBM/DIBM/DBL sequence :
After the EBM/DIBM/DBL sequence, , the RCS software immediately brings the C-CONF pc-elements
into the same state as before the EBM command.
The EBM/DIBM/DBL sequence of the C-CONF pc-element does not influence of the state of the RTU
system.
When the C-CONF pc-elements are activated by means of the DBL commands, the outputs are updated
Restart after a BL/DBL sequence :

The BL/DBL sequence has no impact on the state of the C-CONF pc-elements and no particular action is
taken in the RCS software.
When the C-CONF pc-elements are activated by means of the DBL commands, the outputs are updated
3BSE 022 165R101 77

683(59,6,21$1'(5525+$1'/,1*
12.1 *(1(5$/,1)250$7,21
Four separate supervision and error handling possibilities are available in connection with the HPC563
RCS system.
In the first place it is taken advantage of the standard supervisory mechanisms available in the RP570
protocol. Moreover, the pc-elements, which are the main items of an HPC563 RCS system, have built-in
supervision facilities. The third possibility is the system messages, which are intended to form a tracking
aid for advanced fault localization and maintenance. Finally there is the possibility for the user to
implement further supervision functions by means of application programming.
12.2 683(59,6,2187,/,=,1*)$&,/,7,(6,153
The faults which are supervised and presented via the regular facilities of the remote control system
appears from the specifications under TSTA, Terminal Status Message and TEV, Terminal Event
Message in the chapter Supported messages in the RP570/1 protocol
The messages AVS, IDS, PCM and DVM bring not only information about actual value(s) but also
information about STATUS.
There are no specific application measures necessary.
12.3 683(59,6,21)81&7,216,17+(3&(/(0(176
The RCS pc-elements use the ERRCODE and ERR outputs to describe the state of the pc-element.
In chapter Error codes in RCS pc-elements, a table describing the meaning of the possible ERRCODE
and ERR combinations is found.
There are no specific applications necessary.
78 3BSE 022 165R101

12.4 6<67(00(66$*(6
System messages are sent from the HPC563 RCS system when errors are detected. The system messages
are listed in the document System messages, HPC563 RCS Option, see chapter REFERENCE
DOCUMENTS on page 84. In the document the meaning of each message is explained.
The system messages can only be read and printed out by means of a MA220/AS110ES. The printout
requires a printer attached to the MA220/AS110ES.
There are no specific application measures necessary from the users part.
12.5 683(59,6,21%<$33/,&$7,21352*5$00,1*
It is recommended that all pc-programs in every AC 400 on the local network are supervised with regard
to their RUN-signal. The supervision can take place by means of an OR-gate with inverted inputs. The
output is written into a DIC-object which will give an alarm to the operator either locally or remote.
Finally is recommended to supervise, with regard to redundancy, those computers on the local network
which are equipped with redundant CPU and memory, redundant power supply and redundant fans. The
pc-element STATUS shall be used for the supervision. The output signals are written into DIC-objects
which will give an alarm to the operator either locally or remote.
In the pc-element C-CONF a signal COMM_ACT is available which can be used to give an alarm when
the communication with the Dispatch Center is lost. The outputs TERM_ACT,IND_ERR, AV_ERR,
DV_ERR, PCV_ERR, CMD_ERR, SETP_ERR, GO_ERR, TERM_ERR, AC_FAIL, BATT_LOW and
SCI_ERR are also recommended to supervise.
The user shall create and connect the OR-gates, the DIC-objects and connect the DIC-objects either to
local MMC or to remote system for the supervision of RUN-signals.
The user shall also create and connect the STATUS pc-elements, the DIC-objects for the redundancy
supervision. It should be noted that the use of the pc-element STATUS requires the presence of a bus
extension board.
3BSE 022 165R101 79

67$572)+3&5&66<67(0
13.1 &2/'67$57
1. Prepare the MVI communication board CI535 and the program card interface board MB510 according
to the instructions given in the chapter RCS HARDWARE and software. Switch off the voltage
supply to the actual AC400 computers and insert the boards in the respective racks. Set the start mode
selector of the AC400 processor boards in position CLEAR, reconnect the voltage supplies and press
the INIT buttons in turn.
2. Create one MVIx database element per RCS MVI board according to the instructions given in the
chapter 6.2.1 Data base population. The creation and updating of the MVIx database
element must be done when the AC400 node is in configuration mode (P2).
3. The RCS pc-elements which shall be used for the definition of RP570/1 signals must be created and
connected according to the instructions given in chapter DEFINITION AND FUNCTIONALITY OF
REMOTE CONTROL SIGNALS.
4. Next step is to toggle the C-CONF input E_CONF 0->1 in order to start the RCS SCADA pc-element
configuration. The configuration of the RCS SCADA pc-elements is completed when CONFCODE is
set to 3. In case of unsuccessful configuration the CONFCODE number will refer to detailed
information about the reason.
Note ! Multiple RCS SCADA pc-element configurations can be performed simultaneously.
5. In order to start the start-up sequence towards the terminal, the ACT_COMM must be toggled 0->1. If
the ACT_COMM input is fixed at 1 when the RCS SCADA pc-element configuration is finished, the
start-up sequence will start automatically. The start-up sequence is complete when CONFCODE
reaches 1. In case of unsuccessful start-up sequence, the CONFCODE number will refer to detailed
information about the reason.
Note ! Only a start-up sequence towards one terminal can be performed simultaneously.
13.2 :$5067$57
If the AC400 node is restarted and the inputs E_CONF and ACT_COMM for all C-CONF pc-elements
are fixed at 1, new RCS SCADA pc-element configurations and start-up sequences towards the terminals
are started automatically.
Note that the value outputs of the RCS data acquisition pc-element are preserved during the restart and
configuration sequence. The status of the pc-elements are, however, set to 1, i.e. error. The error-marking
of a pc-element is removed when it receives the first message with process information from the related
process point in the RTU.
80 3BSE 022 165R101

0(025<&2168037,21$1'6<67(0/2$'
14.1 *(1(5$/,1)250$7,21
In each AC400 node which shall communicate with underlying RTUs, the HPC563 RCS software on
PCMCIA flash PROM must be installed in addition to the CI535 MVI communication board with RCS
communication software.
The CI535 MVI communication board does not influence on the memory or CPU load resources in the
AC400 node.
14.2 %$6,&6<67(0
The basic system means the HPC563 RCS system configuration tasks in the AC400 computer, i.e. the
RCS_WD and the RCS_GCI tasks. The tasks on the CI535 MVI communication board are not included
in the basic system concept.
14.2.2 0HPRU\FRQVXPSWLRQ
The RCS system tasks will have approximately the following memory consumption requirement :
6RIWZDUHDQGGDWDVWUXFWXUH 5HT%\WHV578 5HT%\WHVPD[
&RQILJ
OHAB250 program area 30.000 30.000
OHAB250 task stack and heap 48.000 48.000
OHAB260 program area 30.000 30.000
OHAB260 task stack and heap 2.000 2.000
19
Task interface free space requirement 8.800 176.000
Normal event handling free space requirement 13.350 13.350
20
RCS alarm and event handling free space req. 9.290 462.000
7RWDO
The following assumptions were made in order to calculate the amount of required bytes :
all types of RCS pc-elements are represented in all RTUs.
250 RCS SCADA pc-elements are related to each RTU, i.e. about 30 elements of each SCADA pc-
element type.
a maximal configuration consists of 2.000 RCS pc-elements related to 50 RTUs or router-RTUs.
100 process point in each RTU shall have event treatment by means of the RCS alarm and event
handling 21.
The whole RWM area in the AC400 is not allocated until the HPC563 RCS Option is successfully started
the first time after a cold start of the AC400. This area is taken from the free space in system which is
not included in the area allocated by the PC and DB dimensioning. This means that a sufficient data area
must be left as Free space when the PC and DB is being dimensioned.
19 Task interface area : (1100 * x), where x is number of RCS SCADA pc-element types in the RTU (i.e. 1-8).
20 RCS alarm and event handling area = x * (1040 + y*82), where x is number of different RTUs and y is number of used events
per RTU.
21 Note that all RTUs in theAC400 node can have event treatment by means of RCS alarm and event handling.
3BSE 022 165R101 81

14.2.3 6\VWHPORDG
The load of the RCS tasks RCS_WD and RCS_GCI was measurement in an AC450 computer 22 with two
different message frequencies on the RP570 line. The measurement was performed on a system
containing 10 RCS SCADA pc-elements of each type.
14.2.3.2 Quiet system
Only one analog value measurement was transmitted from the RCS system to the dispatch center per
second. The following task loads was measured 23:
7DVN /RDG
OHAB250 0.53
OHAB260 0.31
14.2.3.3 Event burst
Ten indication events and one cyclic analog value measurement were transmitted from the RCS system to
the dispatch center per second. The following task loads was measured:
7DVN /RDG
OHAB250 0.53
OHAB260 1.89
14.3 +3&5&63&(/(0(176
14.3.1 0HPRU\FRQVXPSWLRQ
The RCS pc-elements use memory both from the pc-program memory pool and from the free space memory
poll. The pc-elements will have approximately the following memory consumption requirement in bytes :
7\SH $UHDIURPSFSURJUDPSRRO $UHDIURPIUHHVSDFHSRRO

C-CONF 322
C-IND 130
C-AV 110
C-DV 80
C-PCV 88
C-OCMD 86
C-RCMD 82
C-SETP 70
C-GO 74
22The task load in an AC410 computer caused by the same RCS system would be about 2 times the load in AC450.
23The task load is given in percent of total task load. The task load in the AC410 computer caused by the same RCS system
would be about 2 times the load in AC450.
82 3BSE 022 165R101

14.3.2 6\VWHPORDG
The system load required by the RCS pc-elements can probably be similar to that of the related HPC563
RCS pc-elements :
7\SH %DVLFORDGLQVWDQFH&21750 PV

C-CONF 0,24 %
C-IND 0,11 %
C-AV 0,11 %
C-DV 0,11 %
C-PCV 0,11 %
C-OCMD 0,11 %
C-RCMD 0,11 %
C-SETP 0,11 %
C-GO 0,09 %
3BSE 022 165R101 83

5()(5(1&('2&80(176
'RFXPHQW ,GHQWLW\QXPEHU
1. Functional description
HPC563 RCS Option 5761 056-84
2. Redesign description
Redesign of HPC563 RCS 1.0/0 (impl. In version 2.0/0) HDC6-014
3. System messages
HPC563 RCS Option 5671 056-99
84 3BSE 022 165R101

5(9,6,216
3$*(3 '$7(
9(55(9 &+$37& '(6&5,37,21 '(376,*1
A/0 Whole doc First edition 950123
HDC / NL
CI536 changed to CI535. Database element 950713
MVI1 explained further. HDC / NL
C-AV element changed.
B/0 Whole doc The document is rewritten and transformed to 961203
MS-WORD format Garberg PUAS/StiG
B/1 Whole doc Minor changes 970205
HDC / BoL
B/2 Whole doc Minor changes 971015
Garberg PUAS/StiG
Whole doc. Adapted to release HPC563 SW*3.1/0. 980309
B/3 GEN / HDC / BoL
Whole doc. Adapted to ABB Automation Systems AB 990806
B/4 Minor changes ASY / PDA / BoL
P 10 Max RTUs on RP570 comm. board eq. 8. 20000405
B/5 ASY / PFVD / BoL
Whole doc. Adapted to ABB Automation Products AB 20000523
R101 and release 3.2/0. APR / LAPI / BoL
3BSE 022 165R101 85

86 3BSE 022 165R101

3BSE 022 165R101 June 2000

S 0221651

Transféré par

Informations du document

Titre original

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

S 0221651

Transféré par

Droits d'auteur :

Formats disponibles

ABB Automation Products HPC563 RCS

3BSE 022 165R101

3BSE 022 165R101 1

2 3BSE 022 165R101

3BSE 022 165R101 3

4 3BSE 022 165R101

3BSE 022 165R101 5

6 3BSE 022 165R101

Note that it is possible to attach a printer for

Figure 2 shows a HPC200 application

M B300 The station controls three RTUs by means of the

In big stations, the HPC 300 system with

The station controls three underlying RTUs by

The information received from the underlying

Note that MB300 must be used for the local

3BSE 022 165R101 7

All three HPC563 Options, i.e. RCS, RCS and

A total of two SPA nodes are connected to the

Process point information and events from the

All three HPC563 Options, RTU, RCS and SPA

RP570 Note also that multiple RCS MVI boards can be

Process point information and events from the

2 The AC450 process computer should be used with such configurations.

8 3BSE 022 165R101

3BSE 022 165R101 9

10 3BSE 022 165R101

There exists no database elements related to the MB510 board.

3BSE 022 165R101 11

No messages concerning satellites are supported.

Message : Interpretation : Remarks :

4.2.1.2 Process commands

Message : Interpretation : Remarks :

12 3BSE 022 165R101

4.2.1.3 RTU commands

Message : Interpretation : Remarks :

Message : Interpretation : Remarks :

4.2.2.2 Process command responses

Message : Interpretation : Remarks :

3 Properties for digital event handling not supported.

3BSE 022 165R101 13

4.2.2.3 Data request responses

Message : Interpretation : Remarks :

4.2.2.4 RTU status responses

Message : Interpretation : Remarks :

ALARM AND EVENT HANDLING and the description of pc-element C-CONF.

14 3BSE 022 165R101

Message : Interpretation : Remarks :

Message : Interpretation : Remarks :

4.3.3.2 RTU status responses

Message : Interpretation : Remarks :

3BSE 022 165R101 15

RP570 RP570 RTU210

STA R S.P.I.D.E.R. NETWORK

16 3BSE 022 165R101

Pin # Signal name Pin # Signal name

3BSE 022 165R101 17

An RCS SCADA pc-element is identified by the combination of the following components :

18 3BSE 022 165R101

6.2.1.2 Creating and updating MVIx in AC410

Make the following command in order to create a MVIx database element:

A database element MVIx will be created.

Fill in the properties due to the following description :

6 In AC410 maximum two MVI board can be used, x = 1 or 2.

,WLVQHFHVVDU\WRSURJUDPRQH&&21)SFHOHPHQWSHU578 in the communication network connected to

,WLVSRVVLEOHWRFRQQHFWPD[LPXPVXE578VWRHDFKURXWHU578LQWKHV\VWHP. Therefore maximum

2QH&&21)SFHOHPHQWSHU5&609,ERDUG must have the call parameter C3 fixed at 1. This element is

TGL_EVTR EVTR_ERR

SELECT ERRCODE