Professional Documents
Culture Documents
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
CMU Communication and Data Processing Unit
CS Control System
PB Peripheral Bus
Introduction
Preface
This document describes the functions of the subdevice interface in RTU560 according to
Modbus communication protocol for serial line, and Ethernet based communication.
References
[1] Modicon
Modbus Protocol Reference Guide Revision Y June 1996
[2] Modicon
Modbus Application Protocol Specification Version 1.1a June 2004
[3] Modicon
Modbus Messaging on TCP/IP Guideline Version 1.0a June 2004
Conventions
The Modbus communication protocol as described in Modicon’s documentation is called
Modbus or Modbus protocol in this document. This convention encloses Modbus TCP.
In this document function codes of data types according to the Modbus protocol are put in
angle brackets:
<Function code>
Italic fonts with the heading Parameter are references to configuration parameter in
RTUtil 560. The parameter is followed by definitions in parentheses indicating where this
parameter can be found in RTUtil 560.
Example:
In this document references to elements of the Modbus protocol reference guide will be
printed bold and put in brackets: [1]
The tables in the next chapters include lists of functions, options and message types
supported according to the protocol structure given in IEC 60870-5 (EPA three-layer
model) for
• the physical layer
• the link layer
RS232C RS232C
560ETH03
RS485 RS485
For optical interfaces opto-electrical conversion is needed. In this case fiber optic coupler
23OK24 is recommended. If more than one IED should be connected, 23OK24-fibre optic
couplers can be configured as star.
For possible connection diagrams see description ‘RTU560 - 23OK24 Connections and
settings’ (1KGT150 568).
For the master, the subdevice communication interface, there are 3 parameter available
which are used for all stations on the line.
Using the IP- based communication the master (subdevice communication interface) tries
to connect a slave with a given IP address and port number. The slave (subdevice)
should be prepared to accept a connection on the given port. If a connection is
established the connection will be maintained until an error occurs. If the master
recognizes an error it will close the active connection and tries to establish a new one.
The parameter IP address and port number used for this connection type can be
specified for each station on a line
2.1 General
Modbus does not define a Link Layer, but the Link Layer depends on the different
implementations of the protocol. Therefore, a separated description of this Layer is given
for serial- and IP-based communication.
For serial communication only global parameters have to be configured for the
communication lines.
These parameters could be configured in the line folder of RTUtil 560 separately for
every line. Parameter: General parameter (RTU560 – General parameter)
Communication primitives like the framing of messages and parity checks are handled by
the telecontrol protocol. Data polling and retransmissions are handled by the subdevice
communication interface of RTU560. These tasks are executed in the link layer that
connects RTUs and Modbus-IEDs.
• ASCII mode
1 start-bit, 7 data bits, 1/2 stop bit(s) and 1 parity bit (even / odd) or no parity.
• RTU mode
1 start-bit, 8 data bits, 1/2 stop bit(s) and 1 parity bit (even / odd) or no parity.
The difference between these two framing modes, is that in the RTU mode 8 bits are
represented by one 8-bit character and in the ASCII mode by two 7-bit ASCII character.
The start characters and error checking are different in both modes as described in [1].
Modbus does not support a defined link handling. Therefore the link is checked by
sending a query for a configured data point. If query auto-packing mode is enabled, only
the data point with the lowest function code and the lowest address index of a
slave/server device is polled. Otherwise if disabled, the complete query range configured
for that data point is polled.
If a response is received, the slave device is marked online and all data points of this
slave device will be polled in the next polling cycle.
These parameters can be configured in the IED folder of RTUtil 560 separately for each
IED.
Parameter:
Slave address
(IED Parameter Modbus)
Note:
If Measured Float Information (MFI) are used in
an IED, the query auto-packing mode has to be
disabled.
Parameter:
Query auto-packing mode
(IED parameter – Modbus)
Because of the fact that all data of Modbus devices is polled, the response time of data
changes in a slave device depends on the following factors:
• Transmission rate
• Framing type
Therefore you must be aware of these factors, if defined response times are required.
The IP-based communication is based in part upon reference RFC1122. One of the main
functions of the messaging service is to manage communication establishment and
ending, and to manage the data flow on established TCP connections.
No parameters are required for this implementation since the TCP/IP stack is responsible
of the management of communication. (speed, duplex, time-to-live, number of hops, time-
outs, window-size, three-way-handshaking, etc).
The Link in Ethernet communication is based on the TCP/IP stack. Once the stack
connects a target device, the connection is monitored by the stack and remains
connected until a reset or a close request is received.
In Ethernet networks the time of a reset could take up to 2 hours. Therefore the activity
sends permanent queries in order to monitor the connection with the device.
These parameters can be configured in the IED folder of RTUtil 560 separately for each
IED.
Parameter:
IP address
(IED Parameter Modbus)
Parameter:
TCP Port
Size of Tx Buffer Integer Range 1…16 5
Quantity of queries allowed to transmit without
waiting for a response.
Parameter:
Size of Tx Buffer
Cycle Time Integer Range 1….500 10
Polling time to request monitoring information in
steps of 10 ms.
Parameter:
Cycle Time
Timeout Integer Range 1…50 10
Time (in seconds) before a query that has not
been replied is discarded
Parameter:
Timeout
Query auto-packing mode Enabled / disabled Enabled
Same as for serial
Data in command direction is written directly into the registers or coils of the slave
devices.
Modbus does not support select before operate mechanisms, therefore this is handled in
the subdevice communication interface. If a select command is received, the subdevice
communication interface will check, if the corresponding slave device is offline or online
and select will be confirmed according to the result of this check, negative or positive.
The following execute command will be sent directly to the slave device.
2.6 Restrictions
The column RTU560 Type shows the type of data which can be configured in RTUtil 560.
Selection according to [1][2]. The sizes of the addressing fields are fixed.
Parameter:
Function code
(Data point parameter – Modbus)
Index Integer Range: 0 ... 65535
Parameter:
Index
(Data point parameter – Modbus)
Query range Integer Range: 1 ... 32
Note:
This parameter will be ignored, if the IED-parameter query auto-
packing mode is enabled (see chapter 2.3).
Parameter:
Query range
(Data point parameter – Modbus)
A value of 16 is recommended.
Parameter:
Function Code (SPI-protocol address and parameter)
Index (SPI-protocol address and parameter)
Query Range (SPI-protocol address and parameter)
(if auto-packing mode is disabled)
Additional None
Conversion of value
RTU560 internal communication Protocol-specific
Off 0
On 1
Parameter:
Function Code (DPI-protocol address and parameter)
Index (DPI-protocol address and parameter)
Query Range (DPI-protocol address and parameter)
(if auto-packing mode is disabled)
Additional None
Conversion of value
RTU560 internal communication Protocol-specific
intermediate 00
off 01
on 10
indeterminate 11
Binary process information indicated by two bits and a relative time tag (used by
protection relays).
Parameter:
Function Code (STI-protocol address and parameter)
Index (STI-protocol address and parameter)
Query Range (STI-protocol address and parameter)
(if auto-packing mode is disabled)
Additional None
Conversion of value
RTU560 internal communication Protocol-specific
Range min. -63 -63
... ...
Range max. +63 +63
Parameter:
Function Code (BSI-protocol address and parameter)
Index (BSI-protocol address and parameter)
Query Range (BSI-protocol address and parameter)
(if auto-packing mode is disabled)
Additional Position byte (BSI8 only) Low: Low Byte of register is value
High: High Byte of register is value
Parameter:
Process Data Sub Sub (BSI - Protocol Address and Parameter)
Conversion of value
RTU560 internal communication Protocol-specific
Range min. 0 0
... ...
Range max. BSI8: Bit mask of 8 bits; 255
range ... 255
BSI16: Bit mask of 16 bits; 65535
range ... 65535
Parameter:
Function Code (ITI-protocol address and parameter)
Index (ITI-protocol address and parameter)
Query Range (ITI-protocol address and parameter)
(if auto-packing mode is disabled)
Additional None
Conversion of value
RTU560 internal communication Protocol-specific
Range min. 0 0
... ...
Range max. 65535 65535
Binary process information indicated by 8 or 16 bits used as a measured value from the
digital inputs in normalized format.
Parameter:
Function Code (DMI-protocol address and parameter)
Index (DMI-protocol address and parameter)
Query Range (DMI-protocol address and parameter)
(if auto-packing mode is disabled)
Parameter:
Process Data Sub Sub (DMI - Protocol Address and Parameter)
Conversion of value
RTU560 internal communication Protocol-specific
Range min. -100% -32768
... ...
Range max. +100% +32767
Analog process information used as a measured value from the analog inputs in
normalized or scaled format.
Parameter:
Function Code (AMI-protocol address and parameter)
Index (AMI-protocol address and parameter)
Query Range (AMI-protocol address and parameter)
(if auto-packing mode is disabled)
Parameter:
Process Data Sub Sub (AMI - Protocol Address and Parameter)
Conversion of value
RTU560 internal communication Protocol-specific
Range min. -100% -32768
... ...
Range max. +100% +32767
Parameter:
Function Code (MFI-protocol address and parameter)
Index (MFI-protocol address and parameter)
Query Range (MFI-protocol address and parameter)
(if auto-packing mode is disabled)
38
Value type R32-IEEE STD 754; range –3,4•10 ... +3,4•1038
Deadband 0 .. 100
The value specified is
multiplicated by 10 and taken as
absolut deadband value for
threshold supervision
Note:
0 means that every change is
transmitted
Parameter:
Sign/exponent - (MFI – Protocol address and parameter)
Conversion of value
RTU560 internal communication Protocol-specific
Range min. -100% -3,4•1038
... ...
Range max. +100% +3,4•1038
Sequence of transmission
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
Sequence of transmission
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
Command None
authority
Additional None
Conversion of value
RTU560 internal communication Protocol-specific
off 0x0000
on 0xFF00
Command None
authority
Additional None
Conversion of value
RTU560 internal communication Protocol-specific
off 01
on 10
Command None
authority
Conversion of value
RTU560 internal communication Protocol-specific
Lower 01
Higher 10
Command None
authority
Parameter:
Process Data Sub Sub (ASO - Protocol Address and Parameter)
Conversion of value
RTU560 internal communication Protocol-specific
Range min. -100% -32768
... ...
Range max. +100% +32767
Command None
authority
Parameter:
Process Data Sub Sub (DSO - Protocol Address and Parameter)
Conversion of value
RTU560 internal communication Protocol-specific
Range min. -100% -32768
... ...
Range max. +100% +32767
Command None
authority
Additional None
Conversion of value
RTU560 internal communication Protocol-specific
Range min. 0 0
... ...
Range max. 65535 65535
The general interrogation of the subordinated devices is done directly after the
initialization of the RTU560 and on every change of the subordinated link from state
OFFLINE to state ONLINE.
A general interrogation is done by polling all data configured for one subordinated device.
If this polling cycle is finished, the general interrogation is considered to be terminated.
The subdevice communication interface manages internal status messages for every
device connected to this line. These status messages are created from the subdevice
communication interface itself for every connected device. The subdevice communication
interface supports the following system events
Description of system event Firmware Shortcut
Device active #024
Device inoperable #048
If a fix system event address schema is configured for the system events of a
subordinated device the system events shortcut is used as address offset. Every system
event can be configured with an individual process address. The ease the configuration
and for compatibility reasons fix system event schema is available.
Conversion of Value
Description RTU560 Protocol Specific
internal
Device Active off Device not Active
on Device Active
Device inoperable off Device operable
on Device inoperable
While initialization the value of system event ‘Device is active’ (#024) is set to ON. On a
running system this system event doesn’t change anymore.
The system event RTU_INOPERABLE (48) with value 0 is sent as SPI to the internal
communication for every device that changed the state.
If the status of a subordinated 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 its own RTU.
The system event RTU_INOPERABLE (48) with value 1 is sent as SPI to the internal
communication for every device that changed the state.
In this document parameter settings and selections of the Modbus protocol that are
supported by RTU560 are marked by squares with a tick
Functions and parameter with filled (black) squares are not supported by RTU560 !
(network-specific parameter)
RS-232
Ethernet
NOTE - EIA RS-485 standard defines unit loads so that 32 of them can be operated on one line. For detailed information refer to
clause 3 of EIA RS-485 standard.
Transmission settings are defined according to the chosen framing type. (serial only)
Message length
≤ 255 Maximum length L (number of characters)
< 01 > Read Coil Status < 02 > Read Input Status
< 03 > Read Holding Registers < 04 > Read Input Registers
< 05 > Force Single Coil < 06 > Preset Single Register
< 11 > Fetch Communication Event Counter < 12 > Fetch Communication Event Log
< 15 > Force Multiple Coils < 16 > Preset Multiple Coils
< 19 > Reset Communication Link < 20 > Read General Reference
< 21 > Write General Reference < 22 > Mask Write 4X Register
Command transmission
Direct command transmission
Select and execute command (Note: Select is internally simulated by RTU560-SCI)