Comms Interface Manual
Comms Interface Manual
REVISION HISTORY
ISSUE 13
Section 7.1
Measurands with relative time added to Argus section. Numbers all are Function Type (FUN) 164, Information
(INF) numbers 240-248.
New General commands added to Argus section, FUN = 164 and INF = 129, 130.
New event 'CT Failure' added to Argus section. FUN = 164, INF = 97.
Updated Argus measurand numbers FUN=160, INF = 144, 148.
Updated Argus event 'CB on by auto-reclose' to make it double point.
Updated Argus table of Actual Channel (ACC) numbers for the disturbance recorder.
Section 7.5
The tables for Duobias-M containing event and command numbers have been updated. A table of Actual Channel
numbers has been added.
ISSUE 14
Section 7.9
Events numbers 128, 73 and 130, 73-74 used by Ohmega corrected the type to 4.
Page 2 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
TABLE OF CONTENTS
1 INTRODUCTION.........................................................................................................................................................8
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 3 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 4 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
13 DIAGRAMS ............................................................................................................................................................53
14 FIBRE-OPTIC DATA.............................................................................................................................................53
14.1 LAUNCH POWER (DBM) .....................................................................................................................................53
14.2 RECEIVER SENSITIVITY (DBM) ........................................................................................................................53
14.3 DISTANCE CALCULATION ...............................................................................................................................53
14.4 DISTANCES.........................................................................................................................................................53
LIST OF FIGURES
FIGURE 1 - HANDSHAKING FOR DIALOGUE TYPE INFORMATION EXCHANGE ............................................................................53
FIGURE 2 - BASIC COMMUNICATIONS CONFIGURATION ...........................................................................................................53
FIGURE 3 - BASIC COMMUNICATIONS CONFIGURATION (REMOTE)...........................................................................................53
FIGURE 4 - COMMUNICATIONS USING REYROLLE SIGMA 1 IN STAR CONFIGURATION................................................................53
FIGURE 5 - COMMUNICATION USING REYROLLE SIGMA 3 IN OPTICAL RING CONFIGURATION ...................................................53
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 5 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
REFERENCES
[1] IEC60870-5-103 - Telecontrol equipment and systems, Part 5-103: Transmission protocols. Companion
standard for the informative interface of protection equipment.
[2] IEC60870-5-1 - Telecontrol equipment and systems, Part 5: Transmission protocols. Section One -
Transmission frame formats, First edition, Feb. 1990.
[3] IEC60870-5-2 - Telecontrol equipment and systems, Part 5: Transmission protocols. Section 2 - Link
transmission procedures, First edition, Apr. 1992.
[4] IEC60870-5-3 - Telecontrol equipment and systems, Part 5: Transmission protocols. Section 3 - General
structure of application data, First edition, Sep. 1992.
[5] IEC60870-5-4 - Telecontrol equipment and systems, Part 5: Transmission protocols. Section 4 - Definition
and coding of application information elements, First edition, Aug. 1993.
[6] IEC60870-5-5 - Telecontrol equipment and systems, Part 5: Transmission protocols. Section 5 - Basic
application functions, First edition, June 1995.
[7] Reyrolle Technical Information Report - 434tir007 Remote Communication to Argus Relays
The Copyright and other intellectual property rights in this document and
in any model or article produced from it (and including any Registered or
unregistered design rights) are the property of VA TECH Reyrolle ACP Ltd.
Neither this document nor any part of it shall be reproduced or modified or
stored in another form, in any data retrieval system without the permission
of VA TECH Reyrolle ACP Ltd., nor shall any model or article be
reproduced from this document unless VA TECH Reyrolle ACP Ltd.
consent.
Page 6 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
GLOSSARY
ASDU Application Service Data Unit
Baud Rate See bits per second.
Bit The smallest measure of computer data.
Bits Per Second (BPS) Measurement of data transmission speed.
Byte Series of bits, usually eight.
Data Bits A number of bits containing the data. Sent after the start bit.
Frame A block of information to be transmitted. Includes the destination address and error correction
information.
Least Significant Bit (LSB) In a Byte, octet etc. the bit of least numerical value.
Parity Method of error checking by counting the value of the bits in a sequence, and adding a parity
bit to make the outcome, for example, even.
Parity Bit Bit used for implementing parity checking. Sent after the data bits.
Primary Station The device controlling the communication.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 7 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
1 INTRODUCTION
This document describes the informative communication interface, its features, how it is accessed and provides
guidance for writing software to utilise it. The interface complies with [1] IEC60870-5-103.
The features are in two distinct types. Firstly standard features, for example, Events, Metering and General
Interrogation as defined in [1] IEC60870-5-103. Secondly private commands to access additional features, for
example, waveform data records and altering the settings database.
The document is split into the following sections. Section 2 describes how the relay is physically connected to the
control system. Section 3 describes the protocol requirements of the link layer as defined in [1] IEC60870-5-103
Section 4 describes the private commands and the data they return. Section 5 describes the Reyrolle Protection
Settings Description Language. The appendices contain information referenced throughout the document, including
codes defined by [1] IEC60870-5-103.
Page 8 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Comms Baud Rate 75, 110, 150, 300, 19200 Communications speed defined in bits per second (BPS). Only 19200
600, 1200, 2400, and 9600 BPS are defined in [1] IEC60870-5-103, the additional rates
4800, 9600, 19200 are provided for local or modem communications.
Comms Parity None, Even Even [1] IEC60870-5-103 defines the method of transmission as using Even
Parity. However, in some configurations the parity needs to be None.
Relay Address 0 … 254 0 The address of the relay must be set to a value between 1 and 254
before communication. Setting the address to zero disables
communications to the relay. All relays on a network, for example, as
illustrated in section 13, must have a unique address. Address 255 is
reserved as a global broadcast address.
Line Idle Light Off Light Off [1] IEC60870-5-103 defines the line idle state as Light On. This setting
allows an alternative of Light Off to be selected.
Light On
The line idle setting must be set to be compatible with the hardware
Device Setting connected to the relay. The Sigma range of products for connecting to
the fibre-optic ports on the relays support either Light ON or OFF. All
HFM5500-AAM, HFM5500-AAF Light Off sigma units are supplied Light Off. Sigma 1 has internal switches to set
the condition for each fibre optic channel, Sigma 3 and 4 have an internal
HFM5500-BAM, HFM5500-BAF Light On
jumper to set the state of their fibre optic channel. Refer to section 13
Sigma 1, 3, 4 Settable DIAGRAMS. The table to the left shows the line-idle settings for use with
the Honeywell type HFM5500 fibre-optic to RS232 converters.
Data Echo Off Off Communication networks can be connected in star or ring format. Ring
connections require data to be passed from relay to relay. When using
On this configuration all relays in the ring must have Data Echo set to ON.
Otherwise this setting should OFF. Figure 2 to Figure 5 illustrate a
number of network arrangements
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 9 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
COMMUNICATIONS MENU
Station Address 0 … 254 0 The address of the relay must be set to a value between 1 and 254
before communication. Setting the address to zero disables
communications to the relay. All relays on a network, for example, as
illustrated in section 13, must have a unique address. Address 255 is
reserved as a global broadcast address.
IEC870 on port Com1, Com2, Auto, Com1 The port to which the IEC60870 protocol is directed. The Auto option
None enables detection of the active port. This option can be used if
redundancy is required and both channels are connected to the same
source. The option None switches all communications off.
Line Switch Time 1 … 60 seconds 30 If the Auto option is set in the IEC870 on port setting (see above) this is
the amount of time the device waits after communications has ceased on
a channel before switching channels.
Com1 Baud Rate 75, 110, 150, 300, 19200 Communications speed defined in bits per second (BPS) for each port.
600, 1200, 2400, Only 19200 and 9600 BPS are defined in [1] IEC60870-5-103, the
Com2 Baud Rate 4800, 9600, 19200, 19200 additional rates are provided for local or modem communications.
38400, 57600,
115200
Com1 Parity None, Even, Odd Even Parity setting for each port. [1] IEC60870-5-103 defines the method of
transmission as using Even Parity. However, in some configurations the
Com2 Parity None parity needs to be None.
Com1 Line Idle Light Off, Light Off Idle state setting for each port. [1] IEC60870-5-103 defines the line idle
state as Light On. This setting allows an alternative of Light Off to be
Com2 Line Idle Light On Light Off selected.
Device Setting The line idle setting must be set to be compatible with the hardware
connected to the relay. The Sigma range of products for connecting to
HFM5500-AAM, HFM5500-AAF Light Off the fibre-optic ports on the relays support either Light ON or OFF. All
HFM5500-BAM, HFM5500-BAF Light On sigma units are supplied Light Off. Sigma 1 has internal switches to set
the condition for each fibre optic channel, Sigma 3 and 4 have an internal
Sigma 1, 3, 4 Settable jumper to set the state of their fibre optic channel. Refer to section 13
DIAGRAMS. The table to the left shows the line-idle settings for use with
the Honeywell type HFM5500 fibre-optic to RS232 converters.
Com1 Data Echo Off, On Off Echo mode setting for each port. Communication networks can be
connected in star or optical ring format. The Optical Ring architecture
Com2 Data Echo Off requires data to be passed from relay to relay. When using this
configuration all relays in the ring must have Data Echo set to ON.
Otherwise this setting should OFF. Figure 2 to Figure 5 illustrate a
number of network arrangements
Com2 Direction Auto-Detect Auto- A Modular II relay has two Com2 ports, a pair of fibre optic connectors on
Detect the rear; and a 25 way female D-Type socket on the front fascia. This
Front Port setting specifies which Com2 port will be active. Choosing front or rear
Rear Port forces that port active. Choose Auto-Detect and the rear port will be
active until a device is connected to the front port, which then becomes
active. When the device is removed the Rear port will again activate.
2.3 Modems
The communications interface has been designed to allow data transfer over a telephone system via modems.
Information concerning using and installing modems in detailed in the document [7] Reyrolle Technical Information
Report - 434tir007.
Page 10 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
3 LINK LAYER
3.1 Introduction
This protocol uses Frame Type FT1.2 as defined by [2] IEC60870-5-1. These frames consist of octets (8 bits)
transmitted least significant bit first, without any idle time between bits. Unbalanced transmission is used i.e.
communication can only be initiated from the Primary (Master) Station, for example, a Control System or Remote
Access Point communication program, never from the Secondary (Slave i.e. the relay). Sections 5.2 "Unbalanced
transmission services" and 5.3 "Unbalanced transmission procedures" of [3] IEC60870-5-2 fully apply. The
Application Service Data Units (ASDU) are taken from [1] IEC60870-5-103. Two types of frame are used; one of
fixed length 5 octets and a variable length frame of up to 256 octets, both are described below. Note the following
description will use hexadecimal notation to denote some constants, for example 10h (equal to decimal 16).
Numbers without the ‘h’ suffix are decimal.
3.2 Fixed Length Message Frame
Start Information Field Checksum End
Control Address
10h c A x 16h
A fixed length frame contains 5 octets. It begins with a Start octet of 10h and is terminated by an End octet of 16h.
The octet immediately preceding the End is the Checksum. The Information Field comprising two octets, Control,
as defined in [3] IEC60870-5-2 section 5.12 and section 3.4, and Address, is located between the Start Flag and
the Checksum field. The Checksum is calculated by performing modulo 256 addition of the octets in the Information
Field. A modulo 256 addition involves adding all the octets and then taking the remainder after dividing by 256.
3.3 Variable Length Message Frame
Start Length Length Start Information Field Checksum End
A variable length frame begins with a Start octet of 68h and is terminated by an End octet of 16h. The Start octet is
followed by an octet indicating the number of octets in the Information Field, which is then repeated in the following
octet. The frame header is completed by a second Start octet. The octet immediately preceding the End octet is a
Checksum, again calculated by performing modulo 256 addition of the octets in the Information Field. The
Information Field is located between the second Start octet and the Checksum, and has a maximum length of 250
octets, which corresponds to a maximum frame length of 256 octets.
Information Field
The information field of a variable length frame starts with a Control Octet followed by an Address Octet. These
serve the same purpose as those in the fixed length frame. Then there are 4 octets that constitute the Data Unit
Identifier, as defined in [4] IEC60870-5-3. These octets are Type Identification, Variable Structure Identifier, Cause
of Transmission, and Common Address of ASDU. Two octets comprising the Information Object Identifier, whose
octets are respectively Information Object Type (Function Type) and Information Object Address (Information
Number) follow the Data Unit Identifier. The contents of the Data Field are dependent on the type of frame. The
octets of the Data Unit Identifier, Object Identifier and Data Field constitute the ASDU. They are selected from a set
of Application Information Elements as defined in [5] IEC60870-5-4 . The types used are defined below. The Data
Field is totally transparent and the information can have any form and contain any binary bit combination.
3.4 Control Octet
MSB Bit Number LSB
7 6 5 4 3 2 1 0
For either type of frame the most significant 4 bits of this octet contain the control code and the least significant 4
bits the function code. They are defined in [3] IEC60870-5-2, section 5.1.2 and [1] IEC60870-5-103, section 6.3,
and described below.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 11 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
7 6 5 4 3 2 1 0
In the primary direction i.e. from the primary to the secondary, the Control codes shown above apply.
MSB Bit Number LSB
7 6 5 4 3 2 1 0
Reserved Primary Access Data Flow Function Code
Direction =0 Demand Control
In the secondary direction i.e. from the secondary to the primary, the Control codes shown above apply.
Control Bit Definitions Description
Primary Direction(PRM) Signifies which station generated the frame. If generated by the Primary station this bit is set
(=1), if the secondary it is clear (=0).
Frame Count Bit (FCB) The purpose of the Frame Count Bit (FCB) is to allow the secondary station to detect when a
frame is being retransmitted. For the majority of data exchanges the Master station alternates
the value of the FCB in the Control Octets of the frames. In the case of a missing or
corrupted response from the Secondary the Master sends the same frame with the same
value of FCB. When the Relay sees a frame with the same value of FCB as the previous
frame it assumes that the previous response frame it sent has been corrupted or lost and will
transmit the previous frame again even if there is already a new message in the output
buffer. After a predefined maximum number of attempts (usually 5) have failed the Master
indicates a communication link failure and ceases transmission. The secondary station only
tests this bit if the Frame Count Valid (FCV) bit is set. Refer below. Initially, or after a reset,
the secondary station expects the first frame sent by the Master to have the FCB set.
Frame Count Valid (FCV) Set by the primary station if the value of Frame Count Bit is to be tested.
Access Demand Bit (ACD) Set by the secondary station if it has a Data Class 1 frame available for downloading.
Data Flow Control (DFC) Set by the secondary station when it is processing a command. It cannot process any further
commands, and will ignore any sent while it is set.
Reset Communications Unit 0 Send Resets the communications unit, Frame Count Bit and all buffers.
Relay expects next frame’s FCB bit to be set
Send / Confirm Expected 3 Send Send data, secondary station to confirm receipt.
Send / NO Confirm Expected 4 Send Send data, no confirmation from secondary station
Reset Frame Count Bit 7 Send Only Resets the Frame Count Bit. Relay expects next frame’s
FCB bit to be set
Page 12 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Negative Confirm To Send 1 Confirm Negative acknowledgement (data could not be processed -
interface busy)
Link service not functioning 14 Respond Malfunction, cannot process primary function code
Link service not implemented 15 Respond Unknown primary function code received
Possible Function Codes sent by the secondary station in response to a request from the primary
Function Code From Primary 0 3 4 7 9 10 11
The first access of the relay after start/restart or hardware/software reset must be with a Request for
Communication Unit reset or Request for Frame Count Bit reset. The relay will not respond to any message even if
correctly addressed unless either has been successfully executed. On successful reception of this command the
relay will acknowledge it, see 3.7.1, and prepare an initialisation response, see 3.7.11.
3.6.2 Request for Frame Count Bit Reset
10h 47h 1h 48h 16h Control = PRM + Reset Frame Count Bit = 47h
The relay will acknowledge this request, see 3.7.1, and prepare an initialisation response, see 3.7.11.
3.6.3 Request for Link Status
10h 49h 1h 4Ah 16h Control = PRM + Link Status Request = 49h
The relay will respond with a Link Status Acknowledge message, see section 3.7.5.
3.6.4 Request for Data Class 1
10h 7Ah 1h 7Bh 16h Control = PRM + FCB + FCV + Data Class 1 Request = 7Ah
10h 5Ah 1h 5Bh 16h Control = PRM + FCV + Data Class 1 Request = 5Ah
The relay will respond with the next class 1 message if available, or a Data Not Available message, see 3.7.4.
3.6.5 Request for Data Class 2
10h 7Bh 1h 7Ch 16h Control = PRM + FCB + FCV + Data Class 2 Request = 7Bh
10h 5Bh 1h 5Ch 16h Control = PRM + FCV + Data Class 2 Request = 5Bh
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 13 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
The relay will respond with the next class 2 message if available, or a Data Not Available message, see 3.7.4.
3.6.6 Time Synchronisation - ASDU Type 6
Octet No. Value Global Value Individual Description
12 0 0 Information number
17 4 4 Days
18 6 6 Months
19 97 97 Years
20 Checksum
The time synchronise command sent by the primary station to the secondary complies with that defined [1]
IEC60870-5-103 section 7.4.2 Time Synchronisation. It comprises the information shown in the above table within
a variable length frame of type 6.
Usually, the time synchronise command is used to synchronise all secondary devices on a network. To achieve this
we set the destination address to be Global (255), and the control field to PRM + Send / NO Confirm Expected =
44h signifying we do not want replies from the secondary stations.
You can also use the time synchronise command to set the time of an individual secondary station. In this case the
address of the secondary station (e.g. 1) is used and the control field typically set to PRM + FCB (alternating) +
FCV + Send / Confirm Expected = 73h or 53h. An acknowledgement, see 3.7.1, from the secondary is followed
by a time synchronise confirmation message, see 3.7.12.
Some typical values for the fields are shown in the above table in respectively the value global and value individual
columns. The example time in the above table is 10:27:30.000 and the date the 4th June 1997, it is encoded as
follows. The seconds are stored as a number of milliseconds, 0 to 59,999, in a 16-bit word. This is split into a low
octet and a high octet, for example, in this case milliseconds = 30,000 = 7530h, therefore low = 30h and high 75h.
The minutes, 0 to 59, are set in a single octet. In this example minutes = 27 = 1Bh. Note, the Most Significant Bit
(MSB) of the minutes octet is used to signify the status of the invalid flag, however in this instance as we are
sending a time it is irrelevant.
The invalid flag, 0 represents valid, 1 invalid, is used to signify whether the time has been set within the last
23 hours. Frames from the secondary device that have a time stamp include the invalid flag. After 23 hours
have elapsed since the last setting of the time, the secondary station sets the invalid flag to signify the time
may be invalid. When the time is synchronised this flag is cleared allowing an invalid time to be detected.
The hours, 0 to 23, are set in a single octet. Note, the Most Significant Bit (MSB) is used to hold the summer time
flag. In this example with the summer time flag cleared hours = 10 = 0Ah, with it set the octet would be set to 80h +
0Ah = 8Ah. The table shows the summer time flag set.
Page 14 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
The summertime flag, 0 represents normal time and 1 that daylight saving time is in operation. When the
time is synchronised this flag is set or cleared depending on the value of this bit. Frames from the secondary
device that have a time stamp include the summer time flag.
The octets containing the date are simply set to the numeric value of the content, i.e. day = 1 to 31. Month 1
(January) to 12 (December) and years without the century, therefore, for the above example Day = 4, Month = 6
and year = 97.
The following shows the values in a typical global time synchronise frame, note the summer time flag is set.
Example Frame
68h Fh Fh 68h 44h FFh 6h 81h 8h FFh FFh 0h 30h 75h 1Bh 8Ah 4h 6h 61h 85h 16h
12 0 Information number
The General Interrogation procedure complies with that defined in [1] IEC60870-5-103, Section 7.4.3 - General
Interrogation. General Interrogation is used to retrieve the state of certain events at the time of the interrogation. A
General Interrogation Cycle is initiated by sending an Initialisation of General Interrogation ASDU of type 7, shown
above, to the address of the station to interrogate. The scan number, octet 13 above, is an arbitrary number (0 to
255) sent by the control system, which is copied to the response message by the relay and thus used to tie a
response to the request.
Each event is in the form of type 1 or 2 ASDU, see 3.7.7 or 3.7.8. The completion of a general interrogation cycle
will be signified by a General Interrogation Termination message, frame type 8, see 3.7.13. These frames are
retrieved in response to a request for class 1 data; therefore after initialisation of general interrogation the relay
should be polled for class 1 data, see 3.6.4.
If you sent a General Interrogation Initialisation during a General Interrogation cycle, the present cycle will be
aborted, without the termination message and a new one started.
A General Interrogation will typically be sent after a system reset to obtain the present state of the events.
The following shows the values in a typical General Interrogation Initialisation Frame.
Example Frame
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 15 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
12 Command number
A General Command comprises the information shown in the above table within a variable length frame containing
an ASDU type 20. The command number is defined by [1] IEC60870-5-103 section 7.2.5 Table 17 and by Reyrolle.
A command is either double (turns an item on or off, for example an auto-recloser), or single (turns an item on, for
example, a characteristic) action. The Double Command Information used with certain commands is either OFF (1)
or ON (2), for single action commands this should be set to ON (2).
Double Command Information Description (Refer to [1] IEC60870-5-103 section 7.2.6.4)
0 Not Used
1 OFF
2 ON
3 Not Used
Return Information Identifier, octet 14 above, is an arbitrary number sent by the control system. It is copied to the
response message and thus used to tie responses to commands.
The response is with a Command Acknowledge Message in a Type 1 Frame, see 3.7.7.
Information about general commands can be obtained via the “IG” command, see section 4.10.3.
The following shows the values in a typical General Command.
Example Frame
68h Ah Ah 68h 73h 1h 14h 81h 14h 1h FFh 13h 2h 2Ah 5Ch 16h
Page 16 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
12 Not Used
An order for disturbance data transmission comprises the information shown in the above table within a variable
length frame of type 24. The disturbance data is transmitted in several parts. Each part is requested in this type of
frame. The Type of order number for each part is defined by [1] IEC60870-5-103 section 7.2.6.26, The subset of
TOO codes used in a type 24 frame are shown below.
Type of Order Code Description
1 Selection of fault
4…7 Reserved
9 Abortion of channel
10…15 Reserved
16 Request for tags
17 Abortion of tags
18…23 Reserved
25…31 Reserved
The type of value parameter is defined by [1] IEC60870-5-103 section 7.2.6.27 and shown below.
Type of Order Code Description
0 Not Used
1 Instantaneous Values
The fault number is supplied by the relay in a List of Recorded Disturbances - Frame Type 23, see 3.7.15. Frame
type 23 is generated by the relay when a fault is stored, or after an order for disturbance data request with TOO =
24.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 17 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
The actual channel numbers are defined by [1] IEC60870-5-103, section 7.2.6.1 and Reyrolle and are shown in
APPENDIX B- PUBLIC AND PRIVATE CODES.
The following shows the values in an order for disturbance data request with TOO = 24.
Example Frame
68h dh dh 68h 73h 1h 18h 81h 1fh 1h a0h 0h 18h 1h 0h 0h 0h 50h 16h
9 31 Cause of transmission
10 Common address of ASDU (1 - 254)
11 Function type
12 Not Used
An acknowledgement of disturbance data transmission comprises the information shown in the above table within a
variable length frame of type 25. The disturbance data is transmitted in several parts. Each part is acknowledged in
this type of frame. The type of order number for each part is defined by [1] IEC60870-5-103 section 7.2.6.26, The
subset of TOO codes used in a type 25 frame are shown below.
Type of Order Code Description
41…63 Reserved
The type of value, fault number and actual channel parameters are copied from the frames being acknowledged.
The following shows the values in an acknowledgement of disturbance data request with TOO = 32.
Example Frame
68h dh dh 68h 73h 1h 19h 81h 1fh 1h a0h 0h 20h 1h 40h 5h 0h 34h 16h
Page 18 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
3.6.11 Send Private Data to Relay Frame Types 254 and 255
Octet Value Description
This section describes how private data is sent, using variable length frames, to the relay. Typically this data will be
one of the Reyrolle private commands described in section 4. Unlike the other variable length frames defined,
these frames do not have the 4 byte Data Unit Identifier or the Object Identifier described in section 3.3. Instead
they have a single Type Identifier octet defined as either 255 (FFh) or 254 (FEh), respectively the last segment of
data and not the last segment of data. This allows data to be sent to the relay that will occupy multiple frames i.e.
more than the maximum 247 octets per frame of data. All the frames excluding the last one are marked as type
254, with the last, signifying the data is now complete as type 255.
Each frame sent to the relay is acknowledged, see section 3.7.1. After the acknowledgement is received the next
data frame can be transmitted. After sending the last data frame, the relay should be polled for class 1 data to
retrieve any response messages.
The following show examples of a single data frame being sent. The data sent is the string HELP, ASCII characters
48h, 45h, 4Ch and 50h. As it is the only frame it is marked last frame ffh.
Example Frame with Control Octet = PRM + FCB + FCV + Send / Confirm Expected
68h 7h 7h 68h 73h 1h ffh 48h 45h 4Ch 50h 9Ch 16h
Example Frame with Control Octet = PRM + FCV + Send / Confirm Expected
68h 7h 7h 68h 53h 1h ffh 48h 45h 4Ch 50h 7Ch 16h
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 19 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
10h 0h 1h 1h 16h 10h 20h 1h 21h 16h 10h 30h 1h 31h 16h
3.7.3 Positive acknowledgement (confirm) of request received by relay, requested data available
The function code 8 is sent by the relay in the data frame containing the requested data. The data frame will be one
of the types listed below in section 3.7.7 onwards. Note if the ACD bit is set to accompany this response there is
more class 1 data ready in the relay for which you can poll immediately.
3.7.4 Negative acknowledgement (confirm) of request received by relay, requested data not available
The function code 9 is sent in a short frame to signify that the requested class 1 or 2 data is not available. If you are
expecting this data to be available, for example, as the response to a command, then the relay may not have had
time to produce it yet and you should continue polling. An example is shown below.
10h 09h 1h 0Ah 16h
Page 20 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
12 Information number
18 Supplementary Information
19 Checksum (sum of fields 5 to 18 modulo 256)
Time tagged frame used to return Events, General Interrogation and General Command Responses, as defined in
[1] IEC60870-5-103, section 7.3.1.1. They are extracted as the response to a request for class 1 data, see section
3.6.4. The type of information being returned can be determined by checking the cause of transmission (COT)
octet, the supplementary information octet is dependent on the COT octet, see table below.
Description COT Supplementary Information
Spontaneous Events 1 0
Table Showing Cause of Transmission and Supplementary Information value for various events
0 Travelling (Transitional)
1 OFF
2 ON
3 Invalid
For Spontaneous Events and General Interrogation messages the function type and information number are from
the Function Type and Event Codes shown in APPENDIX A - IEC60870 CODE DEFINITIONS and APPENDIX B-
PUBLIC AND PRIVATE CODES. The Double Point Information (DPI) octet is set to the actual state of the
corresponding event; it is not relevant for command acknowledgements. For the command acknowledgements the
function type and information number (command code) are defined in APPENDIX B- PUBLIC AND PRIVATE
CODES.
An example of a spontaneous event frame is shown below; the function type is 160, event LED Reset information
number is 19 and time 9:34:27.950 with the summer time flag set.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 21 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Example Frame
68h Eh Eh 68h 08h 1h 1h 81h 1h 1h A0h 13h 2h 2Eh 6Dh 22h 89h 0h 88h 16h
7 2 Type identification
9 Cause of transmission
10 Common address of ASDU (1 - 254 - identical to octet 6)
11 Function type
12 Information number
22 Supplementary Information
Time tagged frame with relative time, extracted as the response to a request for class 1 data, see section 3.6.4.
The structure and meaning are basically the same as for Type 1 frames except for additional 4 octets between the
DPI information and the milliseconds low octets. The relative time is relative to the start/pickup of the protection
equipment and is given in milliseconds. The fault number is used to tag events giving a relationship between
events and faults. The fault number will be incremented each time a new fault occurs. Relative time and the Fault
Number are not relevant for general interrogation. Any general interrogation responses that are returned in this
type of frame will have these values set to zero. No Command responses will be returned in this type of frame. An
example of a spontaneous event type 2 frame is shown below, the function code is 160, event A-Starter 64, the
Relative Time Stamp is 5 milliseconds, the fault number is 3 and time 9:34:27.950 with the summer time flag set.
Example Frame
68h 12h 12h 68h 08h 1h 2h 81h 1h 1h A0h 40h 2h 5h 0h 3h 0h 2Eh 6Dh 22h 89h 0h BEh 16h
Page 22 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Type 3 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.3, provide groups of measured values. The
Function Type and the Information Number (INF) define the type of measurand. The number of values in a
measurand is given by the Variable Structure Identifier (VSI) octet. The public measurands returned in this type of
frame are defined in [1] IEC60870-5-103 section 7.2.5.2 table 14, and are duplicated below.
Information Number (inf) Variable Structure Identifier (VSI) Description
144 1 Measurand I
145 2 Measurands I, V
146 4 Measurands I, V, P, Q
The table above shows the measurand octets and the end of a frame when the INF is 144 and the VSI 1.
Octet Value Description
The table above shows the measurand octets at the end of a frame when the INF 145 and the VSI 2.
If available, a type 3 measurand is extracted from the relay by means of the Request Data Class 2 command, see
section 3.6.5. The Measurands Returned depend on the type of the relay. APPENDIX B- PUBLIC AND PRIVATE
CODES shows the measurands returned for the specific types of relays.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 23 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Each measurand is returned as two octets, low then high, that are combined to form the 16 bit word as shown
above. It is defined in [1] IEC60870-5-103 section 7.2.6.8. Bits V1 to V12 comprise the 12 bit normalised value,
which uses 2’s complement format, RES is a reserved bit, ERR is an error bit and OV is the overflow bit. The
definition also states the maximum normalised value as being 1.2x or 2.4x the rated value of the relay. If the value
exceeds this maximum the overflow bit will be set and the value will be the maximum that can be represented, i.e.
for positive values bits V1 to V12 are set, for negative values the sign bit is set and bits V1 to V12 cleared. Whether
the relay uses 1.2x or 2.4x must either be settable, or declared for a particular relay. By default Reyrolle relays use
1.2x.
The relay calculates the Normalised value as follows
MeasuredValue * 212
Normalised Value =
RatedValue *1.2
The example below shows a frame containing a single measurand, information number 150 (96h), and Variable
structure identifier 1. The value of the measurand is 3413 (hex = d55) placed in positions V1 to V12. The flags
Sign, RES, ERR, OV are cleared as follows:
High Octet Low Octet
0 1 1 0 1 0 1 0 1 0 1 0 1 0 0 0
0 d 5 5 0 0 0
6 A A 8
The following frame shows this example, note the measurand octets reversed for transmission.
Example Frame
The next example shows the same measurand with a value of -3413.
1 0 0 1 0 1 0 1 0 1 0 1 1 0 0 0
1 2 A B 0 0 0
9 5 5 8
The following frame shows this example, note the measurand octets reversed for transmission.
Example Frame
Page 24 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
14
15
16 Measurand – most significant octet
Type 4 data frames provide measurands as defined in [1] IEC60870-5-103 section 7.3.1.4. The Function Type and
the Information Number define the type of measurand. There is only 1 measurand per frame. The public
measurands returned in this type of frame are defined in [1] IEC60870-5-103 section 7.2.5.2 table 12, and are
duplicated below.
Information Number Description
This ASDU is also used to send events with a real value. For example, the description shown below is taken from
the Solkor-N events list in section 7.11; it shows two Trip count alarm events. The TYP column shows the type of
ASDU used to send the event. ASDU 1 is used to send the event when the alarm is raised or cleared; this would be
after a threshold has been reached. ASDU 4 is used to send the count each time it changes. In this example, both
are also sent during a GI sequence.
FUN INF Description GI / TYP COT DIR
COM
196 70 Trip count alarm x 1 1, 9 RC
196 70 Trip count alarm x 4 1, 9 M
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 25 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
13 2 Compatibility Level
14 82 'R'
15 69 'E'
16 89 'Y'
17 82 'R'
18 79 'O'
19 76 'L'
20 76 'L'
21 69 'E'
22 id Manufacturers Internal Software Identifier 1
Type 5 data frames provide identification messages as defined in [1] IEC60870-5-103 section 7.3.1.5. These
messages are returned in response to the events Reset Communications Unit refer section 3.6.1, and Reset Frame
Count Bit refer section 3.6.2 and a Start Restart of the relay. They are extracted as the response to a request for
class 1 data, see section 3.6.4.
FUN INF Description GI / TYP COT
COM
? 2 Reset Frame Count Bit - 5 3
? 3 Reset Communication Unit - 5 4
? 4 Start / Restart - 5 5
? 5 Power On - 5 6
Table Showing Cause of Transmission and Information Number values for the events described above.
After the initial reset command to the relay it will prepare two events in type 5 frames, which will be the initial class
1 responses. The first will have COT = 4, INF = 3 if the command was a Reset Communications Unit, otherwise
Page 26 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
COT = 3, INF = 2 if a Reset Frame Check Bit. The second frame will always have COT = 5, INF = 4, signifying a
restart. This procedure complies with [1] IEC60870-5-103 Section 7.4.1 - Initialisation Procedure.
When the user or control system requests Reset Communications Unit or Reset Frame Count a single type 5
response frame will be generated with COT and INF as described above for the respective commands. Again these
have to be extracted with a request for class 1 data, see section 3.6.4
The following frame shows an example of a type 5 frame with cause of transmission Reset Frame Count Bit.
Example Frame
68h 15h 15h 68h 08h 1h 5h 81h 3h 1h A0h 2h 2h 52h 45h 59h 52h 4Fh 4Ch 4Ch 45h 0h 0h 0h 0h A5h 16h
7 8 Type identification
8 81h Variable structure identifier
9 10 Cause of transmission
10 Common address of ASDU (1 - 254 - identical to octet 6)
12 0 Information number
The last frame sent from the relay in one general interrogation scan. This frame has a Data Unit Type Identification
of 8 and a Cause of Transmission of 10. The Scan Number is copied from the GI initialisation frame, refer section
3.6.7, and is the only data added to the standard application header in this frame. Again this type of frame is
extracted as the response to a request for class 1 data, see section 3.6.4.
An example of a type 8 frame is shown below, the scan number is F5h.
Example Frame
68h 09h 09h 68h 08h 01h 08h 81h 0Ah 01h FFh 00h F5h 91h 16h
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 27 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Type 9 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.8, provide groups of measured values. The
Function Type and the Information Number define the type of measurand. The number of values in a measurand is
given by the Variable Structure Identifier (VSI) octet. The public measurands returned in this type of frame are
defined in [1] IEC60870-5-103 section 7.2.5.2 table 14, and are duplicated below.
Information Number Var. Structure ID Description
Type 9 data frames are very similar to type 3, see section 3.7.9, except that not all the measurands need be sent.
By specifying the exact number of measurands being sent in the variable structure identifier octet and always
starting at IL1 the measurands can be truncated, for example, 4 would mean we are sending IL1,2,3, VL1. The length
of frame byte would be correspondingly shortened, in this case to 16. See example below.
Example Frame
68h 10h 10h 68h 8h 1h 9h 4h 2h 1h 80h 94h 10h 0h 10h 0h 10h 0h 20h 0h 7Dh 16h
The values of the measurands are encoded as for a type 3 frame, see section 3.7.9, and like that frame, if available
type 9 frames are extracted from the relay by means of the Request Data Class 2, refer section 3.6.5.
Page 28 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
12 0 Not Used
4 Days
6 Months
97 Years
Type 23 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.11, list the disturbance records held in the
device. These frames are prepared either automatically when a new record is stored, or after a request by the
controller using an ASDU 24 frame (section 3.6.9), with TOO = 24. They are extracted using class 1 data requests
(section 3.6.4). The Variable Structure Identifier octet states how many records are stored in the device. This can
be up to 8 and can also be zero. If there are records available, their details are listed from octet 13. Each record’s
details occupy 10 octets, and consist of a 2 octet fault number, a status of fault octet and a standard seven octet
time stamp. The fault number corresponds to that sent by the events in type 2 frames, refer section 3.7.8. The
status of fault uses bit notation as follows.
8 7 6 5 4 3 2 1
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 29 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Example Frame
68h 12h 12h 68h 8h 1h 17h 1h 1Fh 1h A0h 0h 27h 01h 9h 30h 75h 1bh 8ah 4h 6h 61h adh 16h
7 26 Type identification
11 ft Function type
12 0 Not Used
13 0 Not Used
Type 26 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.12, announce that a disturbance record file is
ready for requesting. These are prepared in response to a request for data in an ASDU 24 message (section 3.6.9)
with TOO = 1, and are extracted using class 1 data requests (section 3.6.4). Information in this frame states
constants that apply to the whole data record. The interval between information elements (INT) states the time
between samples in microseconds. The number of information elements per channel (NOE) and the number of
analogue channels (NOC). The number of grid faults (NOF) is used to indicate when a grid fault causes several
faults to occur. For each fault the fault number will increase the grid fault would remain constant.
Example Frame
68h 17h 17h 68h 8h 1h 1ah 81h 1Fh 1h A0h 0h 0h 1h 9h 30h 10h 31h 4h 20h 3h 9ch 4h 30h 75h 1bh 8ah f0h 16h
Page 30 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
12 0 Not Used
13 0 Not Used
A Type 27 data frame, as defined in [1] IEC60870-5-103 section 7.3.1.13, announces a disturbance record
analogue channel is available. This is initially prepared after the tags have been acknowledged (ASDU 25,
TOO=68) or aborted (ASDU 25, TOO=69). After each analogue channel has been acknowledged (ASDU 25,
TOO=66) or aborted (ASDU 25, 67) further ASDU 27’s are prepared to announce any remaining channels. Again
they are extracted using class 1 data requests (section 3.6.4).
Information in this frame states constants that apply to the channel. The Rated Primary Value (RPV), Rated
Secondary Value (RSV) and Reference Factor (RFA) are all sent as 32 bit (4 octet) floating point values,
conforming to the standard 23 bit mantissa, 8 bit exponent and 1 bit sign format. The relationship between these
values and the sample point x is shown below.
x RPV
SecondaryValue = PrimaryVal ue = SecondaryValue ×
RFA RSV
The following example frame shows a type 27 ASDU when the RPV = 300.0, RSV = 1.0 and the RFA = 600.0
Example Frame
68h 19h 19h 68h 8h 1h 1bh 81h 1fh 1h a8h 0h 0h 1h 0h 0h 1h 0h 0h 96h 43h 0h 0h 80h 3fh 0h 0h 16h 44h 25h 16h
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 31 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
12 0 Not Used
13 0 Not Used
14 0 Not Used
Type 28 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.14, announce that tags are ready for
requesting. These are sent in response to a request for data in an ASDU 24 message, refer section 3.6.9, and are
extracted using class 1 data requests (section 3.6.4).
Example Frame
Page 32 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
12 0 Not Used
Type 29 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.15, indicate the status of the tags. These are
sent in response to a request for data in an ASDU 24 message, refer section 3.6.9, and are extracted using class 1
data requests (section 3.6.4). Each Tag consists of three octets, a Function Type, Information Number and DPI
State. The number of tags (NOT) octet specifies the number of tags in the ASDU, up to a maximum of 25 per
ASDU. The Tag at Position (TAP) value gives the position of the tags in the disturbance record. An ASDU only
holds tags at one position. Initially the state of all tags at TAP position zero is transmitted. Subsequently only tags
that change state in the disturbance record are transmitted. The following example shows a frame with three tags
at position 96.
Example Frame
68h 16h 16h 68h 8h 1h 1dh 81h 1fh 1h a0h 0h 27h 1h 3h 60h 0h a4h 33h 1h a4h 35h 2h a4 3bh 2h 86h 16h
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 33 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
12 0 Not Used
13 0 Not Used
…
Value n – low octet
Value n – High octet
Type 30 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.16, provide the raw disturbance values.
These are sent in response to a request for data in an ASDU 24 message, refer section 3.6.9, and are extracted
using class 1 data requests (section 3.6.4).
Each data value is a 16 bit fixed point number, transmitted as low octet followed by high octet. The number of
disturbance values (NDV) octet specifies the number of values in the ASDU, up to a maximum of 25 per ASDU.
Each channel is transmitted in several ASDU 30’s. The Number of First Element (NFE) value gives the index of the
first data value in the channel of the disturbance record. The following example shows a frame with four values with
a starting position of 500 (1f4).
Example Frame
68h 18h 18h 68h 8h 1h 1eh 81h 1fh 1h a0h 0h 0h 1h 27h 1h 2h 4h f4h 1h 0h 0h 9h 0h 1bh 0h 2ah 0h 71h 16h
Page 34 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
12 0 Not Used
Type 31 data frames, as defined in [1] IEC60870-5-103 section 7.3.1.17, signify the end of a transmission stage,
whether it was successful or unsuccessful. These are sent in response to a request for data in an ASDU 24
message, refer section 3.6.9, and are extracted using class 1 data requests (section 3.6.4). The Type of order
number for each stage is defined by [1] IEC60870-5-103 section 7.2.6.26. The subset of TOO codes used in a type
31 message are shown below.
Type of Order Code Description
70…255 Reserved
68h dh dh 68h 8h 1h 1fh 81h 1fh 1h a0h 0h 40h 1h 27h 1h 4h d6h 16h
3.7.22 Response With Private Data From Relay Frame Types 254 and 255
These frames are identical to those to send private data described in section 3.6.11, except that the Control field
will signify it is being sent by the secondary station, i.e. its value is 08h optionally ACD + DFC. The Frames are
extracted as the response to a request for class 1 data, see section 3.6.4. The resultant data may occupy several
frames i.e. multiple frames of type 254 then one of 255. You must concatenate this user data together until you
receive the final frame. Single frame responses are type 255. Section 4 describes the data received. The frames
might not be contiguous they may be interrupted by frames of a higher priority, see section 3.8.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 35 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
This frame is sent by the relay when data transmission has been terminated before completion. It is an addition to
the private data frames of 254 and 255. An example of when it would be sent is if the data being downloaded
becomes unavailable due to a new record being stored. If this frame is sent the download is complete, i.e. there will
be no more 254 or 255 frames. Any user data already received in 254 type frames should be discarded, as it will be
incomplete. Only the user data sent in this frame should be returned.
Example Frame
3.8 Priorities
As there are several forms of class 1 data, for example, events, general interrogation and private data, there may
be several types waiting to be downloaded, therefore they have been prioritised, see table below.
Priority Description Frame Type Refer To Section
Thus if there is an event and a general interrogation response waiting to be downloaded when you request class 1
data you will get the event. The next time you request class 1 data you will get the general interrogation response.
However, if an event occurs between the first and second polls, that event will be returned as the response to the
second poll.
3.9 Philosophy
The informative interface complying with [1] IEC60870-5-103 is designed for automatic interrogation by a control
system, or manually with user intervention. With a control system the standard format frames, all except types 253,
254 and 255, will be used. For a control system to use the private commands (see section 4) issued and received
in frames 253, 254 and 255, requires software in addition to that for the standard [1] IEC60870-5-103 usage.
Manual interrogation involves a user driving a communications application, for example, Reydisp Evolution, which
has the ability to download and process the information produced by the private commands.
All communication is initiated by the primary station i.e. the control system or user, never the secondary i.e. the
relay. In either case, before a conversation can take place the defined communication protocol initialisation
procedure, [1] IEC60870-5-103 Section 7.4.1 has to be completed. This requires sending either Reset
Communication Unit (see section 3.6.1) or Reset Frame Count Bit (see section 3.6.2). Once this is complete the
relay can be polled for data.
The two types of data which can be polled by the primary station are class 1 (see section 3.6.4) and class 2 (see
section 3.6.5). Class 2 is the measurands, frame type 3 (see section 3.7.9) and 9 (see section 3.7.14), all the
others are class 1. Polling is performed cyclically at time intervals of for example, 50 milliseconds. This interval
Page 36 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
should be as short as is practicable as you should download events in as close to real time as is possible. There
are two ways you can poll. Firstly you can poll for class 1 data (see section 3.6.4) if any is available it will be
returned as described above, if not the negative acknowledgement (data not available) will be returned (see section
3.7.4). Alternately, you can poll for class 2 data (see section 3.6.5) and test if the ACD bit of the control code in the
returned frame is set. If it is you should now poll for any class 1 data before returning to poll for class 2. If the ACD
bit is set in a class 1 response frame, you can immediately poll again for class 1 without waiting for the cyclical
polling period. This will speed up the response time of your communications.
Note, if the relay is connected to a control system and you wish to access the data manually there must be a
method of excluding the relay (s) from being polled by the control system, for example, a passive substation switch.
It is beyond the scope of this document to discuss this further.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 37 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Description HELP.
This command provides help about all user commands within the relay. For a summary of the
commands use HELP on its own. To get extra help about a specific command use HELPxx
where xx is the name of the command. E.g. to get help on the Adjust Time function use
HELPAT.
See Also
Security NONE
See Also
Security NONE
Page 38 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Description PassWord.
This command enables the user to log in to the relay so all protected commands can be used.
Xxxx is the password to use. E.g. PWTEST - log in using TEST as the password.
See Also LO
Security NONE
Response OK
Example OK
Security NONE
Response OK
Example OK
Security NONE
Example
Security NONE
Response <Low Set. 1><Hign Set. 1><Low Set. 2><Hign Set. 2>…<Low Set. Last><Hign Set Last>
Example <01h><00h><07h><03h>...<05h><01h>
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 39 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
<Setting Number> The setting number to change (2 octets – low octet, high octet)
<Setting Value> The new value for the setting. The number of octets this field occupies is
dependent on the setting type (usually 2). See SSn for information on the
number of octets per setting.
Response OK
Example OK
Security NONE
Response For each relay setting:
<Text String For The Setting><CR, LF>
Example
Security NONE
Response ACTIVE SETTINGS GROUP = n
where n = 1 to maximum .number settings groups
Response OK
Example OK
Superseded This command has been superseded by the “XIE” command. Applications should check that
“XIE” command is implemented in the relay and if so use it.
Security NONE
Page 40 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Security NONE
Response For each evaluation period the octet format of the events are:
Octet Description
1 Number of events in this evaluation period - n (1 octet)
2e Number of the e-th event - e = 1 ... n (1 octet)
2e+1 Attribute of the e-th event (bit 0 = CLEARED, bit 1 = RAISED, bit 7 =
PRIVATE_CODE) (1 octet)
2e+2 Lower octet of ms absolute time tag (1 octet)
2e+3 Higher octet of ms absolute time tag (1 octet)
2e+4 Minutes of absolute time tag (1 octet)
2e+5 Hours of absolute time tag (1 octet)
2e+6 Days of absolute time tag (1 octet)
2e+7 Months of absolute time tag (1 octet)
2e+8 Years of absolute time tag (1 octet)
Note: See Appendices C & D for meanings of individual event codes.
Response OK
Example OK
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 41 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
the function types used, in the form #number, description. Then there are descriptions of the
events, consisting of the function type, event number, the direction and the event name. On
the basis of this information the controlling device can recognise event codes received as part
of spontaneous event data packets and / or as the response data for the SE or XSE
commands, and display appropriate text strings.
Security NONE
Response If this command does not exist the response will be “ERROR”, otherwise,
The descriptions of the function types:
#<Function Type>,<Description><CR, LF>
where
<Function Type> Specifies the type of relay the event is from, in the range 0-255.
< Description > Text string describing the function type.
Then for each event:
<Function Type>,<Event Number>,<Direction>,<Event Name><CR, LF>
where
<Function Type> Specifies the type of relay the event is from, in the range 0-255.
<Event Number> Specifies the number of the event, in the range 0 –255.
<Direction> 1 if the event can be raised and cleared. 0 if it can only be raised.
<Event Name> Text string describing the event.
Example #160,Overcurrent<CR><LF>
#164,Reyrolle Overcurrent<CR><LF>
#166,Reyrolle GCB Synchronising<CR><LF>
160,68,0,General Trip<CR><LF>
164,80,1,Waveform Stored<CR><LF>
Response If this command does not exist the response will be “ERROR”, otherwise,
For each evaluation period the octet format of the events are:
Octet Description
1 Number of events in this evaluation period - n (1 octet)
2e Function Type of the event
2e+1 Number of the e-th event - e = 1 ... n (1 octet)
2e+2 Attribute of the e-th event, 0 = Travelling, 1 = Cleared, 2 = Raised, 3 = Error Detected
2e+3 Lower octet of ms absolute time tag (1 octet)
2e+4 Higher octet of ms absolute time tag (1 octet)
2e+5 Minutes of absolute time tag (1 octet)
2e+6 Hours of absolute time tag (1 octet)
2e+7 Days of absolute time tag (1 octet)
2e+8 Months of absolute time tag (1 octet)
2e+9 Lower octet of Years of absolute time tag (1 octet)
2e+10 Higher octet of Years of absolute time tag (1 octet)
Note: See Appendices C & D for meanings of individual event codes.
Page 42 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
<02><A8><33><02><A8><FD><02><05><00><00><00><01><01><BC><07>
<01><A8><59><02><23><00><00><00><01><01><BC><07>
<01><A8><59><01><B9><0F><00><00><01><01><BC><07>
Response OK
Example OK
Example OK
Security NONE
Description Send waveform Data record n where n = 1 to last data record. Record 1 is always the newest.
See Also DD, RS, TS
Security NONE
Response Relay sends the requested waveform record in the format below.
<Relay Type> <User Defined Identifier>,<Station Address><CR, LF>
<Total Channels>,<Analogue Channels>A,<Digital Channels>D<CR, LF>
For each analogue channel:
<Channel Number>,,<Channel Name>,,<Units>,<Multiplication Factor>,,,,<CR, LF>
For each digital channel:
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 43 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 44 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
11/18/95,07:45:32.672500
11/18/95,07:45:32.685000
BINARY - PHASE BY PHASE
<Analogue Channel 1>
<Analogue Channel 2>
<Analogue Channel 3>
<Packed Digital 1>
<Packed Digital 2>
Security NONE
See Also IM
Security NONE
Response Relay sends the requested measurand in ASCII format as a text string.
Example The response for the time measurand will be in the form
08:15:26
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 45 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
command.
Example OK
Response OK
Example OK
Security NONE
Response DATE dd/mm/yy, TIMEhh:mm:ss
Response OK
Example OK
Security NONE
Response For each fault record.
<Fault Number> <Time Stamp> <Fault Information><CR,LF>
Example FAULT 2 04/01/94 23:29:20.8200 PHASE A LS IDMTL HS1 IA=22.85xIn PHASE B LS IDMTL
HS1 IB=44.19xIn PHASE C LS IDMTL HS1 IC=43.46xIn
FAULT 1 04/01/94 23:29:21.0300 PHASE A LS IDMTL HS1 IA=31.45xIn PHASE B LS IDMTL
HS1 IB=60.96xIn PHASE C LS IDMTL HS1 IC=59.58xIn
Page 46 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Example OK
See Also
Security NONE
Example 160,164
Reset Flag & Outputs,160,19,1
Trigger waveform Storage,164,80,1
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 47 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
.
Setting n Text Display Setting n Value Description Setting n Display Condition.
Each text line can consist of a combination of text and field codes. These field codes specify where the editable
fields for the setting are to be displayed, i.e. if the line is <Description><Field><Unit> the field specifies the setting
is to be displayed between the description and the unit. The format for the field code is as follows; a start character
7 followed by a character denoting the field number. Then the text presently displayed in the field followed by a
terminating character again 7, thus
|07h|01h|<field text 1>|07h|<Displayable Text>|07h|02h|<field text 2>|07h|<Displayable Text>
The end of a setting text display is determined by the start of the setting value description, which is always an
opening square bracket '['.
5.2.2 Setting Value Description
The Setting Value Description is used for converting machine-readable settings into human readable settings. It
consists of a set of square braces containing information about one or more editable fields, each of which are also
enclosed in square braces. An optional '@' before the first field indicating that the setting is read-only - i.e. it can
be interpreted and displayed but not modified
[<@>[Field 1]<[Field 2]...[Field n]>]
Page 48 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
- An optional minus sign ‘-’ which, if present, signifies that the units information should be
suppressed for this field.
[ww] An optional field width, enclosed within square brackets “[ ]”, representing the number of bits
used to store the field value. This is only required on multiple field settings, otherwise a default
value of 16 applies.
Setting Type The format of the rest of the field depends on the type of setting, see next table.
Bit mask A hash sign ‘#’ followed by a value representing the number of bit fields within the mask.
These bits are continuous starting with the least significant bit. A hexadecimal number
enclosed within square brackets, which is a mask representing the bit positions that can be
modified follows this value. Labels for all bit positions follow it. The labels are double-
quoted strings within a set of braces, similar to those of a string setting value description.
The first label corresponds to the least significant bit. For example, a bit mask setting
consisting of 5 bit fields labelled Status1 to Status5. The mask of 1C (11100 in binary)
means that the value of the last two bit fields (Status4 and Status5) should not be modified.
#5[1C]{"Status1"}{"Status2"}{"Status3"}{"Status4"}{"Status5"}
Sub-menu title [MENU]
Calendar date [DATE]
Clock time [TIME]
Password [PASSWORD]
Non-editable The body of the field is empty, i.e. [ ]
All other One or more range descriptions. A range description consists of a number followed by
either a label (in the same format as a bit-field label) or a reverse-polish setting value
description contained within a set of braces. The number represents the maximum internal
value of the setting for which this range description is applicable. See Appendix H for a
description of the reverse polish notation.
[[0{"OFF"}10{?10*}]] All internal values up to and including zero (i.e. just the value zero), represent the label
“OFF” and all values greater than zero but less than or equal to 10 (i.e. the values 1 to
10) are converted using the reverse polish formula ?10* - which would simply multiply the
internal value by 10. All internal values greater than 10 are invalid, see below :
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 49 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
[[48{?2+20/}]] One field and one range. An internal value from 0 to 48 is translated using the formula
'?2+20/'. Values greater than 48 are invalid. The formula simply adds 2 to the internal
value then divides the result by 20, i.e.
Value Displayed 0.1 0.15 0.2 0.25 … 2.4 2.45 2.5 invalid
[[-0{"INST"}60{?}]] One field and two ranges. An internal value of 0 represents 'INST'. Internal values from
1 to 60 inclusive represent actual values of 1-60. Internal values greater than 60 are
invalid. This setting is actually used for the relay reset delay, where values can range
from 'INST' then '1 sec' to '60 sec'. The minus sign in front of the first range is used to
ensure that 'INST' would be displayed and not 'INST sec'.
[@[0{75}1{110}9{2?2-^150*}]] One field and three ranges. An internal value of zero represents 75. An internal
value of 1 represents 110. Internal values from 2 to 9 are converted using the
formula '2?2-^150*', or in standard infix notation: 2 n− 2 × 150 where n
represents the internal setting value, giving :
Value Displayed 75 110 150 300 600 1200 2400 4800 9600 19200 invalid
[[#3[7]{"STA"}{"P/F"}{"E/F"}]] One bit mask field consisting of 3 bit fields named “STA”, “P/F” and “E/F”. The
mask of 7 (111 in binary) means that all bit fields can be edited.
Value Displayed STA P/F STA+P/F E/F STA+E/F P/F+E/F STA+P/F+E/F invalid
[[[15]1999{?1+5*}][[1]1{?4*1+}]] Two fields each with only one range. The first field occupies the highest 15 bits
of the word and the second field occupies the final (i.e. the least significant) bit.
In the first field, all values from zero to 1999 are converted by adding one to the
internal value then multiplying the result by five. In the second field, the values
zero and one are converted by multiplying the internal value by four then
adding one to the result. This would give :
Further examples are shown in appendix G and the complete reverse polish described in appendix H.
5.2.3 Setting Display Condition
The Setting Display Condition is a logical expression that determines whether the setting should be displayed for
the present configuration of the relay. For example, a Highset Time Delay setting should not be displayed if the
Highset Setting is turned off
The Setting Display Condition consists of a set of square brackets containing a reverse polish logical expression
that is evaluated to give TRUE or FALSE, respectively display or do not display the setting. See appendix J.
The logical expression is able to compare settings with other settings or with constant values. The letter S
immediately followed by the index of the setting represents the setting. The letter V immediately followed by the
constant number represents a value.
The following ANSI ‘C’ logical operators are supported
&& And || Or
== Equals != Not Equal To
Page 50 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
[S20 S21 == S27 V50 >= S27 V60 <= && ||] Display setting if setting number 20 equals setting number 21 or
setting number 27 is between 50 and 60 inclusive.
[] Always display this setting.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 51 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
60 Reyrolle Modular II
1 Spontaneous Events
2 Cyclic
5 Start Restart
6 Power On
7 Test Mode
8 Time Synchronisation
9 General Interrogation
11 Local Operation
12 Remote Operation
Page 52 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Event Codes
Measurand Codes
KEY
FUN Function Type (defined in [1] IEC60870-5-103 section 7.2.5.1) and by Reyrolle in appendix A
INF Information Number (defined in [1] IEC60870-5-103 section 7.2.5.2) and by Reyrolle for each relay in appendix B
TYP ASDU Type (defined in [1] IEC60870-5-103 sections 7.3.1 and 7.3.2)
GI Event supports General Interrogation x = supported (defined in [1] IEC60870-5-103 section 7.2.5.2) and by Reyrolle in appendix B
COM Type of command single (ON only) or double (ON/OFF) (defined in [1] IEC60870-5-103 section 7.2.5.2) and by Reyrolle in appendix B
COT Cause of Transmission (defined in [1] IEC60870-5-103 section 7.2.3, table 5)
DIR Direction of event Raised Only (RO), Raised / Cleared (RC) or Double Point Travelling, Cleared, Raised or Unknown (DP)
x Supported, - Not supported.
7.1 ARGUS 1 - 6
FUN INF Description GI TYP COT DIR
Argus 2 - 500
Argus 1 & 2
Argus 3 - 6
160 2 Reset FCB - 5 3 RO x x x
160 3 Reset CU - 5 4 RO x x x
160 4 Start/Restart - 5 5 RO x x x
160 5 Power On - 5 6 RO x x x
160 27 Input 1 x 1 1, 9 RC x x x
160 28 Input 2 x 1 1, 9 RC x x x
160 29 Input 3 x 1 1, 9 RC x x x
160 30 Input 4 x 1 1, 9 RC x x x
160 64 A-starter x 2 1, 9 RC x x x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 53 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Argus 2 - 500
Argus 1 & 2
Argus 3 - 6
160 65 B-starter x 2 1, 9 RC x x x
160 66 C-starter x 2 1, 9 RC x x x
160 67 E-starter x 2 1, 9 RC x x x
160 68 General trip - 2 1 RO x x x
i
160 144 Measurand I - 3.1 2,7 - x x x
160 148 Measurand IL1,2,3, VL1,2,3, P, Q, F - 9 2,7 - x x x
i
One of Ia, Ib, Ie, Isef depending on relay type
Page 54 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Argus 2 - 500
Argus 1 & 2
Argus 3 - 6
164 18 B-HS2 trip - 2 1 RO x x x
164 19 C-HS2 trip - 2 1 RO x x x
164 20 E-HS2 trip - 2 1 RO x x x
164 21 SEF/REF starter x 2 1, 9 RC x x x
164 45 Input 5 x 1 1, 9 RC x x x
164 46 Input 6 x 1 1, 9 RC x x x
164 47 Input 7 x 1 1, 9 RC x x x
164 48 Input 8 x 1 1, 9 RC x x x
164 49 Input 9 x 1 1, 9 RC x x x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 55 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Argus 2 - 500
Argus 1 & 2
Argus 3 - 6
164 60 Output 10 x 1 1, 9, 12, 20, 21 RC x x
164 61 Output 11 x 1 1, 9, 12, 20, 21 RC x x
164 62 Forward A x 2 1, 9 RC x x x
164 63 Reverse A x 2 1, 9 RC x x x
164 64 Forward B x 2 1, 9 RC x x x
164 65 Reverse B x 2 1, 9 RC x x x
164 66 Forward C x 2 1, 9 RC x x x
164 67 Reverse C x 2 1, 9 RC x x x
164 68 Forward E x 2 1, 9 RC x x x
164 69 Reverse E x 2 1, 9 RC x x x
164 70 Trip count alarm x 1 1, 9 RC x x x
164 88 Reclaim x 1 1, 9 RC x
164 89 Lockout x 1 1, 9 RC x
164 90 Forward SEF x 2 1, 9 RC x x
164 91 Reverse SEF x 2 1, 9 RC x x
164 92 Power On Counter Alarm x 1 1, 9 RC x x x
164 97 CT Failure x 1 1, 9 RC x x x
Page 56 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Argus 2 - 500
Argus 1 & 2
Argus 3 - 6
164 110 SEF off x 1 1, 9, 12, 20, 21 RC x
164 111 All ARC off x 1 1, 9 RC x
164 112 P/F ARC off x 1 1, 9, 12, 20, 21 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 57 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Argus 2 - 500
Argus 1 & 2
Argus 3 - 6
160 16 Auto-recloser ON/OFF ON/OFF 20 20 - - x
Page 58 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Argus 2 - 500
Argus 1 & 2
Argus 3 - 6
164 116 P/F Instantaneous ON/OFF 20 20 - - x
164 117 E/F Instantaneous ON/OFF 20 20 - - x
164 118 SEF Instantaneous ON/OFF 20 20 - - x
164 119 Hot line working ON/OFF 20 20 - - x
The following table shows the Actual Channel Numbers used for each configuration of relay. The abbreviated used are nP number of
standard poles, E earth fault pole, SEF sensitive earth fault pole. For example, a 4 pole relay may be a 2P + E + SEF.
164 1 I I Ia Ia Ia Ia Ia Ia Ia Ia Ia
164 2 Ib Ie Ib Ie Ib Ib Ib Ib Ic
164 3 Ic Ic Ise Ic Ic Ic Ic Ic Ie
164 4 Ise Ie Ise Ie Isef Isef
164 5 Va Va Va
164 6 Vb Vb Vb
164 7 Vc Vc Vc
164 8 Vn Vn Vn
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 59 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
7.2 ARGUS 7
FUN INF Description GI TYP COT DIR Argus 7
166 28 Input 2 x 1 1, 9 RC x
166 29 Input 3 x 1 1, 9 RC x
166 30 Input 4 x 1 1, 9 RC x
166 83 Lockout - 1 1 RC x
166 84 Reset Lockout Mode - 1 1 RO x
Page 60 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
ii
166 148 Measurand IL1,2,3, VL1,2,3, P, Q, F - 9 2,7 - x
ii
Only VL1, VL2, and F are valid, all other fields returned as zero.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 61 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 62 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
7.3 ARGUS 8
FUN INF Description GI TYP COT DIR Argus 8
167 27 Input 1 x 1 1, 9 RC x
167 28 Input 2 x 1 1, 9 RC x
167 29 Input 3 x 1 1, 9 RC x
167 30 Input 4 x 1 1, 9 RC x
167 45 Input 5 x 1 1, 9 RC x
167 46 Input 6 x 1 1, 9 RC x
167 47 Input 7 x 1 1, 9 RC x
167 48 Input 8 x 1 1, 9 RC x
167 49 Input 9 x 1 1, 9 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 63 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
iii
167 148 Measurand IL1,2,3, VL1,2,3, P, Q, F - 9 2,7 - x
iii
Only VL1, VL2, VL3 and F are valid, all other fields returned as zero.
Page 64 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 65 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
167 2 Vbc V0 V0 Vb
167 3 Vca
167 3 Vca V0 Vc
Page 66 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
7.4 DELTA
FUN INF Description GI TYP COT DIR Delta
70 5 Status Input 5 x 1 1 RC x
70 6 Status Input 6 x 1 1 RC x
70 7 Status Input 7 x 1 1 RC x
70 8 Status Input 8 x 1 1 RC x
70 9 Status Input 9 x 1 1 RC x
70 10 Status Input 10 x 1 1 RC x
70 11 Status Input 11 x 1 1 RC x
70 12 Status Input 12 x 1 1 RC x
70 13 Status Input 13 x 1 1 RC x
70 14 Status Input 14 x 1 1 RC x
70 15 Status Input 15 x 1 1 RC x
70 16 Status Input 16 x 1 1 RC x
70 17 Status Input 17 x 1 1 RC x
70 18 Status Input 18 x 1 1 RC x
70 19 Status Input 19 x 1 1 RC x
70 20 Status Input 20 x 1 1 RC x
70 21 Status Input 21 x 1 1 RC x
70 22 Status Input 22 x 1 1 RC x
70 23 Status Input 23 x 1 1 RC x
70 24 Status Input 24 x 1 1 RC x
70 25 Status Input 25 x 1 1 RC x
70 26 Status Input 26 x 1 1 RC x
70 27 Status Input 27 x 1 1 RC x
70 28 Status Input 28 x 1 1 RC x
70 29 Status Input 29 x 1 1 RC x
70 30 Status Input 30 x 1 1 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 67 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
70 31 Status Input 31 x 1 1 RC x
70 32 Status Input 32 x 1 1 RC x
Page 68 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
iv
160 148 Measurand IL1,2,3, VL1,2,3, P, Q, F - 9 2,7 - x
iv
The voltages returned are phase to neutral.
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 69 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 70 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
168 61 SEF-Reverse x 2 1 RC x
168 62 NPS-lowset starter - 2 1 RC x
168 63 NPS-lowset trip - 2 1 RO x
168 64 NPS-HS1 trip - 2 1 RO x
168 65 NPS-HS2 trip - 2 1 RO x
168 88 Reclaim x 1 1 RC x
168 89 Lockout x 1 1 RC x
168 90 Thermal Overload Trip - 1 1 RO x
168 91 Thermal Capacity Alarm - 1 1 RC x
168 92 Load Increase Alarm - 1 1 RC x
168 93 Thermal Overload Alarm - 1 1 RC x
168 94 Phase A CT Failed - 1 1 RC x
168 95 Phase B CT Failed - 1 1 RC x
168 96 Phase C CT Failed - 1 1 RC x
168 97 CT Failed - 1 1 RC x
168 98 Successful Close x 1 1 RO x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 71 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 72 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
200 1 CB 1 x 1 1, 20, 21 DP x
200 2 CB 2 x 1 1, 20, 21 DP x
200 3 CB 3 x 1 1, 20, 21 DP x
200 4 CB 4 x 1 1, 20, 21 DP x
200 5 CB 5 x 1 1, 20, 21 DP x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 73 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
200 1 CB 1 ON/OFF 20 20 x
200 2 CB 2 ON/OFF 20 20 x
200 3 CB 3 ON/OFF 20 20 x
200 4 CB 4 ON/OFF 20 20 x
200 5 CB 5 ON/OFF 20 20 x
Page 74 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 75 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
7.5 Duobias-M
FUN INF Description GI TYP COT DIR Duobias-M
176 4 Start/Restart - 5 5 RO x
176 5 Power On - 5 6 RO x
176 64 Start/Pick-up L1 x 2 1 RC x
176 65 Start/Pick-up L2 x 2 1 RC x
176 66 Start/Pick-up L3 x 2 1 RC x
176 67 Start/Pick-up N x 2 1 RC x
176 68 General Trip - 2 1 RO x
176 69 Trip L1 - 2 1 RO x
176 70 Trip L2 - 2 1 RO x
176 71 Trip L3 - 2 1 RO x
Page 76 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 77 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 78 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 79 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 80 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
178 0 Global
178 1 W1 Ia
178 2 W1 Ib
178 3 W1 Ic
178 4 W1 EF
178 5 W2 Ia
178 6 W2 Ib
178 7 W2 Ic
178 8 W2 EF
178 9 W3 Ia
178 10 W3 Ib
178 11 W3 Ic
178 12 W3 EF
178 13 W4 Ia
178 14 W4 Ib
178 15 W4 Ic
178 16 W4 EF
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 81 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
7.6 Iota
FUN INF Description GI TYP COT DIR Iota
60 130 Re-Start - 1 0 RO x
70 1 Status Input 1 x 1 1 RC x
70 2 Status Input 2 x 1 1 RC x
70 3 Status Input 3 x 1 1 RC x
70 4 Status Input 4 x 1 1 RC x
70 5 Status Input 5 x 1 1 RC x
70 6 Status Input 6 x 1 1 RC x
70 7 Status Input 7 x 1 1 RC x
70 8 Status Input 8 x 1 1 RC x
70 9 Status Input 9 x 1 1 RC x
70 10 Status Input 10 x 1 1 RC x
70 11 Status Input 11 x 1 1 RC x
70 12 Status Input 12 x 1 1 RC x
70 13 Status Input 13 x 1 1 RC x
70 14 Status Input 14 x 1 1 RC x
70 15 Status Input 15 x 1 1 RC x
70 16 Status Input 16 x 1 1 RC x
70 17 Status Input 17 x 1 1 RC x
70 18 Status Input 18 x 1 1 RC x
70 19 Status Input 19 x 1 1 RC x
70 20 Status Input 20 x 1 1 RC x
70 21 Status Input 21 x 1 1 RC x
70 22 Status Input 22 x 1 1 RC x
70 23 Status Input 23 x 1 1 RC x
Page 82 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
70 24 Status Input 24 x 1 1 RC x
70 25 Status Input 25 x 1 1 RC x
70 26 Status Input 26 x 1 1 RC x
70 27 Status Input 27 x 1 1 RC x
70 28 Status Input 28 x 1 1 RC x
70 29 Status Input 29 x 1 1 RC x
70 30 Status Input 30 x 1 1 RC x
70 31 Status Input 31 x 1 1 RC x
70 32 Status Input 32 x 1 1 RC x
70 33 Status Input 33 x 1 1 RC x
70 34 Status Input 34 x 1 1 RC x
70 35 Status Input 35 x 1 1 RC x
70 36 Status Input 36 x 1 1 RC x
70 37 Status Input 37 x 1 1 RC x
70 38 Status Input 38 x 1 1 RC x
70 39 Status Input 39 x 1 1 RC x
70 40 Status Input 40 x 1 1 RC x
70 41 Status Input 41 x 1 1 RC x
70 42 Status Input 42 x 1 1 RC x
70 43 Status Input 43 x 1 1 RC x
70 44 Status Input 44 x 1 1 RC x
70 45 Status Input 45 x 1 1 RC x
70 46 Status Input 46 x 1 1 RC x
70 47 Status Input 47 x 1 1 RC x
70 48 Status Input 48 x 1 1 RC x
70 49 Status Input 49 x 1 1 RC x
70 50 Status Input 50 x 1 1 RC x
70 51 Status Input 51 x 1 1 RC x
70 52 Status Input 52 x 1 1 RC x
70 53 Status Input 53 x 1 1 RC x
70 54 Status Input 54 x 1 1 RC x
70 55 Status Input 55 x 1 1 RC x
70 56 Status Input 56 x 1 1 RC x
70 57 Status Input 57 x 1 1 RC x
70 58 Status Input 58 x 1 1 RC x
70 59 Status Input 59 x 1 1 RC x
70 60 Status Input 60 x 1 1 RC x
70 61 Status Input 61 x 1 1 RC x
70 62 Status Input 62 x 1 1 RC x
70 63 Status Input 63 x 1 1 RC x
70 64 Status Input 64 x 1 1 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 83 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 84 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
200 1 CB 1 x 1 1 DP x
200 2 CB 2 x 1 1 DP x
200 3 CB 3 x 1 1 DP x
200 4 CB 4 x 1 1 DP x
200 5 CB 5 x 1 1 DP x
200 21 Iso 1 x 1 1 DP x
200 22 Iso 2 x 1 1 DP x
200 23 Iso 3 x 1 1 DP x
200 24 Iso 4 x 1 1 DP x
200 25 Iso 5 x 1 1 DP x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 85 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 86 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
7.7 MicroTAPP
FUN INF Description GI TYP COT DIR MicroTAPP
60 0 Data lost - 1 1 RO x
60 130 Re-Start - 1 0 RO x
70 5 Status Input 5 x 1 1 RC x
70 6 Status Input 6 x 1 1 RC x
70 7 Status Input 7 x 1 1 RC x
70 8 Status Input 8 x 1 1 RC x
70 9 Status Input 9 x 1 1 RC x
70 10 Status Input 10 x 1 1 RC x
70 11 Status Input 11 x 1 1 RC x
70 12 Status Input 12 x 1 1 RC x
70 13 Status Input 13 x 1 1 RC x
70 14 Status Input 14 x 1 1 RC x
70 15 Status Input 15 x 1 1 RC x
70 16 Status Input 16 x 1 1 RC x
70 17 Status Input 17 x 1 1 RC x
70 18 Status Input 18 x 1 1 RC x
70 19 Status Input 19 x 1 1 RC x
70 20 Status Input 20 x 1 1 RC x
70 21 Status Input 21 x 1 1 RC x
70 22 Status Input 22 x 1 1 RC x
70 23 Status Input 23 x 1 1 RC x
70 24 Status Input 24 x 1 1 RC x
70 25 Status Input 25 x 1 1 RC x
70 26 Status Input 26 x 1 1 RC x
70 27 Status Input 27 x 1 1 RC x
70 28 Status Input 28 x 1 1 RC x
70 29 Status Input 29 x 1 1 RC x
70 30 Status Input 30 x 1 1 RC x
70 31 Status Input 31 x 1 1 RC x
70 32 Status Input 32 x 1 1 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 87 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 88 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 89 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
v
These are per unit values and sent as fractions of the system rating. Please note that frequency rating is always 60 Hz, therefore the value will
be approximately 0.83 on a 50 Hz system. The transformer and group load use the System group capacity, and the angle is sent as a fraction of
360 degrees. The tap position is sent as a fraction of the total tap range.
Page 90 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
7.8 MSCDN
FUN INF Description GI TYP COT DIR MSCDN
60 0 Data lost - 1 1 RO x
60 1 IEC870 Active Com1 x 1 1 RC x
70 1 Status Input 1 x 1 1 RC x
70 2 Status Input 2 x 1 1 RC x
70 3 Status Input 3 x 1 1 RC x
70 4 Status Input 4 x 1 1 RC x
70 5 Status Input 5 x 1 1 RC x
70 6 Status Input 6 x 1 1 RC x
70 7 Status Input 7 x 1 1 RC x
70 8 Status Input 8 x 1 1 RC x
70 9 Status Input 9 x 1 1 RC x
70 10 Status Input 10 x 1 1 RC x
70 11 Status Input 11 x 1 1 RC x
70 12 Status Input 12 x 1 1 RC x
70 13 Status Input 13 x 1 1 RC x
70 14 Status Input 14 x 1 1 RC x
70 15 Status Input 15 x 1 1 RC x
70 16 Status Input 16 x 1 1 RC x
70 17 Status Input 17 x 1 1 RC x
70 18 Status Input 18 x 1 1 RC x
70 19 Status Input 19 x 1 1 RC x
70 20 Status Input 20 x 1 1 RC x
70 21 Status Input 21 x 1 1 RC x
70 22 Status Input 22 x 1 1 RC x
70 23 Status Input 23 x 1 1 RC x
70 24 Status Input 24 x 1 1 RC x
70 25 Status Input 25 x 1 1 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 91 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
70 26 Status Input 26 x 1 1 RC x
70 27 Status Input 27 x 1 1 RC x
70 28 Status Input 28 x 1 1 RC x
70 29 Status Input 29 x 1 1 RC x
70 30 Status Input 30 x 1 1 RC x
70 31 Status Input 31 x 1 1 RC x
70 32 Status Input 32 x 1 1 RC x
Page 92 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
180 69 Trip L1 - 2 1 RO x
180 70 Trip L2 - 2 1 RO x
180 71 Trip L3 - 2 1 RO x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 93 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 94 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
7.9 OHMEGA
FUN INF Description GI TYP COT DIR Ohmega Ohmega
3xx 4xx
128 64 Start/Pick-up L1 x 2 1 RC x
128 65 Start/Pick-up L2 x 2 1 RC x
128 66 Start/Pick-up L3 x 2 1 RC x
128 67 Start/Pick-up N x 2 1 RC x
128 68 General Trip - 2 1 RO x x
128 69 Trip L1 - 2 1 RO x x
128 70 Trip L2 - 2 1 RO x x
128 71 Trip L3 - 2 1 RO x x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 95 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
130 100 Z1 AE - 2 1 RO x x
130 101 Z1 BE - 2 1 RO x x
130 102 Z1 CE - 2 1 RO x x
130 103 Z1 AB - 2 1 RO x x
130 104 Z1 BC - 2 1 RO x x
130 105 Z1 CA - 2 1 RO x x
130 106 Z2 AE - 2 1 RO x x
Page 96 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
130 107 Z2 BE - 2 1 RO x x
130 108 Z2 CE - 2 1 RO x x
130 109 Z2 AB - 2 1 RO x x
130 110 Z2 BC - 2 1 RO x x
130 111 Z2 CA - 2 1 RO x x
130 112 Z3 AE - 2 1 RO x x
130 113 Z3 BE - 2 1 RO x x
130 114 Z3 CE - 2 1 RO x x
130 115 Z3 AB - 2 1 RO x x
130 116 Z3 BC - 2 1 RO x x
130 117 Z3 CA - 2 1 RO x x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 97 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 98 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 99 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
7.10 Rho 3
FUN INF Description GI TYP COT DIR Rho 3
165 29 Input 3 x 1 1 RC x
165 30 Input 4 x 1 1 RC x
Page 100 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
165 46 Input 6 x 1 1 RC x
165 47 Input 7 x 1 1 RC x
165 48 Input 8 x 1 1 RC x
165 49 Input 9 x 1 1 RC x
165 50 E/F Inhibit x 1 1 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 101 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
vi
165 148 Measurand IL1,2,3, VL1,2,3, P, Q, F - 9 2,7 - x
vi
Only IL1, IL2, IL3 and F are valid, all other fields returned as zero.
Page 102 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 103 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
165 1 IA x
165 2 IB x
165 3 IC x
165 4 IE x
Page 104 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
7.11 SOLKOR-N
FUN INF Description GI TYP COT DIR Solkor N
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 105 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
192 5 Power On - 5 6 RO x
192 29 Input 3 x 1 1 RC x
192 30 Input 4 x 1 1 RC x
192 47 Alarm x 1 1 RO x
Page 106 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
196 45 Input 5 x 1 1 RC x
196 46 Input 6 x 1 1 RC x
196 47 Input 7 x 1 1 RC x
196 48 Input 8 x 1 1 RC x
196 49 Input 9 x 1 1 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 107 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
vii
At present Remote EF returns zero.
Page 108 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
196 1 A
196 2 B
196 3 C
196 4 E
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 109 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 110 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
7.12 TAU
FUN INF Description GI TYP COT DIR TAU
70 5 Status Input 5 x 1 1 RC x
70 6 Status Input 6 x 1 1 RC x
70 7 Status Input 7 x 1 1 RC x
70 8 Status Input 8 x 1 1 RC x
70 9 Status Input 9 x 1 1 RC x
70 10 Status Input 10 x 1 1 RC x
70 11 Status Input 11 x 1 1 RC x
70 12 Status Input 12 x 1 1 RC x
70 13 Status Input 13 x 1 1 RC x
70 14 Status Input 14 x 1 1 RC x
70 15 Status Input 15 x 1 1 RC x
70 16 Status Input 16 x 1 1 RC x
70 17 Status Input 17 x 1 1 RC x
70 18 Status Input 18 x 1 1 RC x
70 19 Status Input 19 x 1 1 RC x
70 20 Status Input 20 x 1 1 RC x
70 21 Status Input 21 x 1 1 RC x
70 22 Status Input 22 x 1 1 RC x
70 23 Status Input 23 x 1 1 RC x
70 24 Status Input 24 x 1 1 RC x
70 25 Status Input 25 x 1 1 RC x
70 26 Status Input 26 x 1 1 RC x
70 27 Status Input 27 x 1 1 RC x
70 28 Status Input 28 x 1 1 RC x
70 29 Status Input 29 x 1 1 RC x
70 30 Status Input 30 x 1 1 RC x
70 31 Status Input 31 x 1 1 RC x
70 32 Status Input 32 x 1 1 RC x
70 33 Status Input 33 x 1 1 RC x
70 34 Status Input 34 x 1 1 RC x
70 35 Status Input 35 x 1 1 RC x
70 36 Status Input 36 x 1 1 RC x
70 37 Status Input 37 x 1 1 RC x
70 38 Status Input 38 x 1 1 RC x
70 39 Status Input 39 x 1 1 RC x
70 40 Status Input 40 x 1 1 RC x
70 41 Status Input 41 x 1 1 RC x
70 42 Status Input 42 x 1 1 RC x
70 43 Status Input 43 x 1 1 RC x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 111 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 112 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
210 3 Reset CU - 2 4 RO x
210 4 Start/Restart - 2 5 RO x
210 5 Power On - 5 6 RO
210 6 Fx One In Service - 1 1 RO x
210 70 Trip L2 - 2 1 RO x
210 71 Trip L3 - 2 1 RO x
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 113 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 114 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 115 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 116 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
Positive Acknowledgement
Positive Acknowledgement
Type 1 or 2 Event
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 117 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 118 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
2 n− 2 × 150
((2^(n-2)) * 150) written in fully parenthesised infix form
(n 2 -) convert inner-most level
(2 (n 2 -) ^) next level
((2 (n 2 -) ^) 150 *) final level
remove braces and replace the 'n' with a '?' and the reverse polish form is:
2 ? 2 - ^ 150 *
The following operators can currently be processed by the settings parser
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 119 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
Page 120 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 121 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
13 DIAGRAMS
Rx Tx
Local
Sigma 4 Tx
(SG4-10x) Rx
Laptop computer
Rx Tx
Local
Telephone Sigma 4 Tx
Network (SG4-10x) Rx
Modem Modem
Laptop computer
Control System
or Master Serial Optical Link
Sigma 1
Sigma 3 Up to 29 Serial Optical Links to relays
(SG1-10x)
or
Sigma 4
Note, each Serial Optical Link consists of two fibres, a transmit and a receive
Control System
Rx Tx Rx Tx
Sigma 3
System
Optical link
(SG3-10x)
Local
Tx
Rx Tx Rx Tx Rx
Laptop computer
Note that in the case of the optical ring configuration, the Data Echo feature must be switched ON in
the communication settings menu of the relay. In all other cases this setting should be OFF
Page 122 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED
IEC60870-5-103 Communication Interface 434/TM/5/14
14 FIBRE-OPTIC DATA
Note. This data refers to the fibre optic data communications port only. It does not refer to the protection
signalling of the Solkor-N relay. Refer to the Solkor-N manual for further information. All products are
optimised for use with glass fibre cable, except where polymer (p) is stated.
14.1 LAUNCH POWER (dBm)
The amount of light that can be focussed into the fibre.
SOURCE
CABLE TYPE
Argus (p) Argus Modular I Modular II Sigma 1 Sigma 3 (p) Sigma 3 Sigma 4 (p) Sigma 4
1 mm polymer -10.5 -7 -10 -7 -7 14.8 -14.6 10.6 -14.6
200 µm PCS -14.4 -6.2 -11.7 -6.2 -6.2 21.8 -13.4 21.7 -13.4
62.5 / 125 µm glass -29 -16 -20 -16 -16 -22.7 -22.7
50 / 125 µm glass -32.6 -19.8 -22.8 -19.8 -19.8 -26.2 -26.2
DESTINATION
Argus (p) Argus Modular I Modular II Sigma 1 Sigma 3 (p) Sigma 3 Sigma 4 (p) Sigma 4
Sensitivity (dBm) -20 -24 -24 -24 -24 -20 -25.4 -25.4 -25.4
Sigma 1 transmits to an Argus (g) using 62.5µm glass fibre cable (loss 2.8 dB / km) and a safety margin
of 3dB.
(−16) − (−24) − 3 − 0
d (km) =
2.8
5
d (km) =
2.8
d (km) = 1.7857
CIRCULATION APPROVED © 1996 - 2004 VA TECH Reyrolle ACP Ltd. Page 123 of 124
434/TM/5/14 Communication Interface IEC60870-5-103
14.4 DISTANCES
These figures are based on manufacturers’ data and may be subject to change without notice. No account is taken
of minimum distances. With certain fibres, it is possible to overload the receivers thus causing errors. All distances
are in metres, and are maximum figures, allowing for LED degradation. All products are optimised for use with
glass fibre cable, except where polymer (p) is stated.
1mm polymer
SOURCE DESTINATION
Argus (p) Argus Modular I Modular II Sigma 1 Sigma 3 (p) Sigma 3 Sigma 4 (p) Sigma 4
Argus (p) 40 70 0 70 70 40 80 80 80
Argus 4.5 6.5 0 6.5 6.5 4.5 6.0 7.0 6.0
Modular I 0 0 5.5 0 0 3.5 6.0 6.0 6.0
Modular II 4.5 6.5 0 6.5 6.5 4.5 6.0 7.0 6.0
Sigma 1 4.5 6.5 0 6.5 6.5 4.5 7.0 7.0 7.0
Sigma 3 (p) 10.0 35 35 35 35 10.0 45 45 45
Sigma 3 2.5 4.5 4.5 4.5 4.5 2.5 5.0 5.0 5.0
Sigma 4 (p) 38 65 65 65 65 35 75 75 75
Sigma 4 2.5 4.5 4.5 4.5 4.5 2.5 5.0 5.0 5.0
200µm PCS
SOURCE DESTINATION
Argus (p) Argus Modular I Modular II Sigma 1 Sigma 3 (p) Sigma 3 Sigma 4 (p) Sigma 4
Argus (p) 100 260 0 260 260 100 320 320 320
Argus 1540 2110 0 2110 2110 1540 2310 2310 2310
Modular I 0 0 1320 0 0 750 1520 1520 1520
Modular II 1540 2110 0 2110 2110 1540 2310 2310 2310
Sigma 1 1540 2110 0 2110 2110 1540 2310 2310 2310
Sigma 3 (p) 0 0 0 0 0 0 0 0 0
Sigma 3 370 940 940 940 940 370 1140 1140 1140
Sigma 4 (p) 0 0 0 0 0 0 0 0 0
Sigma 4 370 940 940 940 940 370 1140 1140 1140
62.5/125 µm glass
SOURCE DESTINATION
Argus (p) Argus Modular I Modular II Sigma 1 Sigma 3 (p) Sigma 3 Sigma 4 (p) Sigma 4
Argus (p) 0 0 0 0 0 0 0 0 0
Argus 350 1780 0 1780 1780 350 2280 2280 2280
Modular I 0 0 350 0 0 0 850 850 850
Modular II 350 1780 0 1780 1780 350 2280 2280 2280
Sigma 1 350 1780 0 1780 1780 350 2280 2280 2280
Sigma 3 (p) 0 0 0 0 0 0 0 0 0
Sigma 3 0 0 0 0 0 0 0 0 0
Sigma 4 (p) 0 0 0 0 0 0 0 0 0
Sigma 4 0 0 0 0 0 0 0 0 0
50/125 µm glass
SOURCE DESTINATION
Argus (p) Argus Modular I Modular II Sigma 1 Sigma 3 (p) Sigma 3 Sigma 4 (p) Sigma 4
Argus (p) 0 0 0 0 0 0 0 0 0
Argus 0 420 0 420 420 0 920 920 920
Modular I 0 0 0 0 0 0 0 0 0
Modular II 0 420 0 420 420 0 920 920 920
Sigma 1 0 420 0 420 420 0 920 920 920
Sigma 3 (p) 0 0 0 0 0 0 0 0 0
Sigma 3 0 0 0 0 0 0 0 0 0
Sigma 4 (p) 0 0 0 0 0 0 0 0 0
Sigma 4 0 0 0 0 0 0 0 0 0
Example:
A ring of relays with a Sigma 4p is required to communicate with a PC. The ring consists of an Argus relay and a
MicroTAPP. From the Transmitter of the Sigma 4p to the Receiver of the Argus, using 1mm polymer fibre, the
maximum distance is 38m. From the Transmitter of the Argus to the Receiver of the MicroTAPP (Modular II) using
1mm polymer fibre, the maximum distance is 70m. From the Transmitter of the MicroTAPP to the Receiver of the
Sigma 4p, the maximum distance is only 7m with 1mm polymer fibre. However, using 200PCS, the maximum
distance is extended to 2.3km! (There is a minimum distance associated with this configuration, however, of around
1.5km).
Page 124 of 124 © 1996 - 2004 VA TECH Reyrolle ACP Ltd. CIRCULATION APPROVED