E560 RP570-71 Sub
E560 RP570-71 Sub
Revision
We reserve all rights in this document and in the information contained therein.
Reproduction, use or disclosure to third parties without express authority is strictly
forbidden.
Contents
CONTENTS ...............................................................................................V
ABBREVIATIONS....................................................................................VII
INTRODUCTION.......................................................................................IX
Preface ....................................................................................................................... ix
References.................................................................................................................. ix
Conventions ................................................................................................................ ix
Abbreviations
AMI Analog Measured value Input
CS Control System
PB Peripheral Bus
Introduction
Preface
This document describes the subdevice communication interface in RTU560 with
communication protocol RP570/71.
References
[1] S.P.I.D.E.R. RTU PROTOCOL 570 and 571 (RP570 and RP571)
1KSE 300000-VW WKA006 Variant: A
Conventions
In this document function codes of data messages according to RP570/71 are put in
pointed brackets.
<Function code>
References to configuration parameters in RTUtil 560 are written in italic under the
heading parameter. The parameter is followed by definitions put in parentheses, which
indicate where this parameter can be found in RTUtil 560. Example:
In this document references to elements of the protocol specification are printed in bold
type and put in brackets: [1, 2.3]
The tables in the next chapters include lists of the functions, options and message types
supported by the protocol structure of RP570/71 for
1.1 General
Different transmission speeds in control and in monitoring direction are not supported by
RTU560. Possible communication interfaces according to Table 1-1:
Interface
CP1 CP2 CPA CPB
Device
RS232C RS232C RS232C RS232C
560SLI02
RS422 RS422 RS485 RS485
RS232C RS232C
560ETH0x
RS485 RS485
A link address model is used for all RTU560 subdevice communication interfaces. The
basic procedures for data transfer, protection against loss and duplication and flow
control are described in [2].
These parameters can be configured in the line folder of RTUtil 560 separately for every
line.
Overview of the data message types for the data elements of the application layer
defined in [2] and supported by RTU560.
The column RTU560 Type shows the type of data to be configured in RTUtil 560.
Parameter:
Router
(datapoint parameter – RP570/71)
Process RTU number 1 octet
Note:
Using RP570, this address parameter will not be available.
Parameter:
Station
(datapoint parameter – RP570/71)
Block number 1 octet
Parameter:
Block
(datapoint parameter – RP570/71)
Bit number Range: 1 ... 16
Parameter:
Bit
(datapoint parameter – RP570/71)
Parameter:
Router
(datapoint parameter – RP570/71)
Process RTU number 1 octet
Note:
Using RP570, this address parameter will not be available.
Parameter:
Station
(datapoint parameter – RP570/71)
Object number Range: 1 ... 2047 (for SCO, DCO)
1 … 255 (for RCO, ASO, DSO)
Parameter:
Object
(datapoint parameter – RP570/71)
Parameter:
Wait for ERMI - (SPI parameters)
Meaning:
If enabled, ERMI and IDS telegrams will be processed. Otherwise only IDS
and IDM telegrams will be processed.
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Off 0 ERMI: 10
On 1 ERMI: 01
Parameter:
Wait for ERMI - (DPI parameters)
Meaning:
If enabled, ERMI and IDS telegrams will be processed. Otherwise only IDS
and IDM telegrams will be processed.
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Intermediate 00
On 01
Off 10
Indeterminate 11
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Range min. -63 -63
... ...
Range max. +63 +63
Conversion of values
RTU560 internal communication Protocol-specific
Range min. 0 0
... ...
Range max. 65535 65535
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Range min. -231 -231
... ...
Range max. +231-1 +231-1
Binary process information indicated by 8 or 16 bits used as measured value from digital
inputs in normalized format.
Supported Data < DVM > 16-bit transparent data
Types without time stamp
without status
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Range min. -100% -32768
... ...
Range max. +100% +32767
Conversion of values
RTU560 internal communication Protocol-specific
Range min. -100% -2000
... ...
Range max. +100% +2000
100 % Overflow
Value on internal
communication
Example:
Maximum Value = 1000
Minimum Value = -1000
Measured Value,
External Protocol
Overflow - 100 %
Analog process information indicated by 32 bits used as a measured value from analog
inputs in floating format.
Restrictions:
Fault number (FAN) and relative time (RET) are not supported in MFI data type.
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Range min. -3.4 1038 -3.4 1038
... ...
Range max. +3.4 1038 +3.4 1038
Conversion of values
RTU560 internal communication Protocol-specific
Intermediate 00
On 01
Off 10
Indeterminate 11
Parameter:
Select before execute (SCO - protocol address and parameters)
Note:
Only one command can be selected or executed at the same time per
subordinate device.
Command None
Authority
Additional
Conversion of values
RTU560 internal communication Protocol-specific
Off 0
on 1
Parameter:
Select before operate (DCO - protocol address and parameters)
Note:
Only one command can be selected or executed at the same time per
subordinate device.
Command None
Authority
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
On 01
Off 10
Command None
Authority
Additional Note:
Regulating step commands are in principle retriggerable commands.
Conversion of values
RTU560 internal communication Protocol-specific
Lower 01
Higher 10
Command None
Authority
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Range min. -100% -2000
... ...
Range max. +100% +2000
Command None
Authority
Additional None
Conversion of values
RTU560 internal communication Protocol-specific
Range min. -100% Not allowed
… …
0 0
… …
Range max. +100% +32767
Conversion of values
RTU560 internal communication Protocol-specific
Range min. 0 0
… …
Range max. 65535 65535
FCOM #1 is not generated by the subdevice communication interface, but will be routed
through the system.
Values 1
Command None
Authority
Additional The function command received from the following host interfaces will
be routed through the subdevice communication interface as FCOM #1:
Values 2
Command None
Authority
Important note:
The time synchronization command is only sent to subordinated devices which are
ONLINE and only if the time tag of the own RTU is valid (synchronized).
Command None
Authority
Additional None
The subdevice interface manages internal status messages for every device connected
to this line. These status messages are created by the subdevice interface itself for every
connected device.
During initialization the system event RTU_IS_ACTIVE (24) is sent as SPI with value 1 to
the internal communication. In a running system this system event does not change
anymore.
The system event RTU_INOPERABLE (48) is sent as SPI to the internal communication
as a function of the state of the subordinate device:
Parameter:
Complete SEV block (IED/RTU560 - protocol address and parameters)
The system event RTU_INOPERABLE (48) with value 0 is sent as SPI to the internal
communication for every device that has changed its state to ‘online’, and is transmitted
by a Host Communication Interface with RP570/71 Protocol as TSTA 3 Bit 0 with the
address of the subdevice.
If the status of a subordinate device or line changes from ONLINE to OFFLINE all
configured data points connected to this device are sent to the internal communication
with the actual state, marked as INVALID and with the time stamp of the own RTU.
The system event RTU_INOPERABLE (48) with value 1 is sent as SPI to the internal
communication for every device that has changed its state to ‘offline’, and is transmitted
by a Host Communication Interface with RP570/71 Protocol as TSTA 3 Bit 0 with the
address of the subdevice.
The following interoperability definitions are copied from RP570/71, the original
numbering and layout is maintained.
This document defines by mark squares parameter settings and selections from the
standard RP570/71 that are supported by RTU560.
Functions and parameters with filled (black) squares are not supported by RTU560 !
(network-specific parameter)
(network-specific parameter)
(network-specific parameter)
(system-specific parameter)
Block address
Range: 1.. 255
Bit number
Range: 1.. 16
Object address
Object address
Data Requests
:= Request A RA
:= Request B RB
:= Request X RX
Process Commands
:= Immediate execute command IXC
:= Check back before execute command CBXC
:= Execute command EXC
:= Inhibit command IHC
:= Setpoint message SPM
:= General output message GOM
RTU Commands
:= Status check instruction SCI
:= Reset sequence number RSEQ
:= Time sync instruction TSI
:= Function command (FCOM #1,2 only) FCOM
:= Function table FTAB
:= Transparent date in command direction TDC