Professional Documents
Culture Documents
RTU560 Remote Terminal Unit: Subdevice Communication Interface With Hitachi HDLC Protocol
RTU560 Remote Terminal Unit: Subdevice Communication Interface With Hitachi HDLC Protocol
RTU560 Remote Terminal Unit: Subdevice Communication Interface With Hitachi HDLC Protocol
Revision
Document Identity: 1KGT 150 584 V001 1
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 functions of the Subdevice interface with Hitachi protocol in
the RTU560
References
[1] Hitachi Protocol Description
Appendix 6
Conventions
In this document function codes of data types according to Hitachi are marked with angel
brackets:
<Function code>
Italic fonts with the heading Parameter are references to configuration parameter in
RTUtil560. The parameter is followed by definitions in round brackets where to find this
parameter in RTUtil560. Example:
In this document references to elements of the standard will be printed bold and in
brackets: [2, 7.4]
The tables in the next chapters include lists of the functions, options and message types
supported according to the structure of the protocol Hitachi
The Hitachi protocol is a bit-oriented asynchronous protocol and can not run on a normal
UART. Possible communication interfaces are according to Table 1-1
The communication parameters (see Table 1-2) have to be set according to the physical
connection
If an octet has a bit sequence of 01111110, but is not a flag field, HLDC uses a technique
called bit-stuffing to differentiate this bit sequence from a flag field.
Once the transmitter detects that it is sending 5 consecutive 1's, it inserts a 0 bit to
prevent a "phony" flag.
At the receiving end, the receiving station inspects the incoming frame. If it detects 5
consecutive 1's it looks at the next bit. If it is a 0, it pulls it out.
Bit Send Sequence: the low order bit of a byte is sent first
Byte Send Sequence: measurements: the high order byte of a word is sent first
otherwise: the low order byte of a word is sent first
2.3 Addressing
Monitoring direction:
Every station of protocol Hitachi contains 16 groups. Every group can contain 16 words,
where every word consists of 16 bit.
Command direction:
Every station of protocol Hitachi contains 7 groups. Every group can contain 8 words,
where every word consists of 8 bit.
0 (Broadcast) 0 (Broadcast)
1 0 0 1 0 0
: :
15 7
1 0 1 0
: :
15 7
2 0 2 0
: : : :
15 0 6 0
: :
15 7
2 0 0 2 0 0
: : : : : :
255 0 0 255 0 0
: : : :
15 0 6 0
: :
15 7
1 ST1 Logic initial This command is sent directly after restart and
communication breaks.
No answer is expected
2 ST2 Start data report This command is sent directly after a ‘Logic initial’
command.
No answer is expected
3 TMS Relative timer set This command is sent cyclically according the time
given in the line parameter ‘Time sync cycle’.
The substation answers with the reflection of the
telegram received
4 FRZ Pulse data save This command is sent cyclically according the time
given in the line parameter ‘Counter freeze cycle’.
After sending this command the RTU560 will send a
‘Group data gathering’ command for reading the
counter values.
No answer is expected
7 UNU Unused
9 UNU Unused
10 UNU Unused
13 UNU Unused
15 GE2 General Enquirer 2 Used for reading data without time stamp;
answered by the substation with the words which
changed its value (max 10) since the last ‘General
Enquirer’ command;
the answer will include the group address, word
address and the data value
16 – 255 Group Data Gathering This command is used for reading the actual value of
GDG data.
Measurements are polled by the group data gathering command. The answer includes a
flag field, which indicates any changes of indications. If this flag is set, the RTU560 sends
a GE1/GE2 command for collecting these indications.
Additionally a background cycle can be specified for gathering indications (see chapter
2.1). A group data gathering command is sent cyclically, to get the actual state of the
indications.
General Enquirer GE1 and GE2 are used according to the parameter ‘Time sync cycle’
(see chapter 2.1). If the time synchronization of subordinated devices is enabled, General
Enquirer GE1 is used for data gathering, if not General Enquirer GE2 is used.
The column RTU560 Type shows the type of data with must be configured in RTUtil560.
No. of addressable elements per RTU560 is the maximum number of elements of this
data type, if all groups are configured with this data type. Please note the general
limitations of the RTU560.
Conversion of value:
RTU560 internal communication Protocol specific
Range min. 0 0
... ...
Range max. 65.535 65.535
Conversion of value:
RTU560 internal communication Protocol specific
Range min. 0 0
... ...
Range max. +63 +63
Conversion of value:
RTU560 internal communication Protocol specific
Range min. -100% -2048 (12 bit 2’s complement)
... ... …
Range max. +100% +2047
Conversion of value:
RTU560 internal communication Protocol specific
Range min. 0 0
... ... …
Range max. 65.536 65.535
Conversion of value:
RTU560 internal communication Protocol specific
Off EX: 0101
On EX: 1010
Conversion of value
RTU560 internal communication Protocol specific
Off EX: 0101
On EX: 1010
If the RTU560 shall synchronize the subordinated devices, the node must be
synchronized. The time synchronization command is sent only to subordinated devices,
which are in state ONLINE, and only if the time tag of the own RTU is valid
(synchronized).
The RTU560 sends ‘timer reset’ commands, which causes a reset of the internal ’10 ms
counter’ in the substation. The SOE messages received are time stamped with the value
of this counter. The RTU560 calculates its time stamp by adding the time stamp received
to the time of the last ‘timer reset’ command sent.
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 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) as SPI with value1 is sent to
the internal communication. On a running system this system event does not change.
The system event RTU_INOPERABLE (48) is sent as SPI to the internal communication
as a function of the state of the subordinated device:
State of the subordinated device Value of system event 48
OFFLINE 1
ONLINE 0
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.
Following interoperability definitions are copied from IEC 60870-5-101, clause 8; the
original numbering and layout is maintained.
This document defines by mark squares parameter settings and selections from the
Hitachi protocol that are supported by RTU560.
Functions and parameter with filled (black) squares are not supported by RTU560 !
(Network-specific parameter)
Balanced transmission
Unbalanced transmission
Frame length
≤ 512 Bit
Remote initialization
Clock synchronization
(Station-specific parameter)
Clock synchronization
Command transmission
(Object-specific parameter)
No additional definition (pulse duration is defined within RTU 560 individually per command object)
Short pulse duration
Long pulse duration
Persistent output