1KGT151051 IEC Conversion PDF

—
1 KG T1 51 0 5 1, JUN 2 5T H , 20 19
Application Note
Transparent Conversion of
IEC 60870-5-101 to IEC 60870-5-104 on
500NMD and 500NMS family
20 19- 06- 25 1/ 33
Table of Content
1 Introduction ................................................................................................................................... 3
1.1 Motivation ................................................................................................................................. 3
1.2 Modernization of Communication Infrastructure.............................................................. 4
1.3 Migration from IEC 60870-5-101 to IEC 60870-5-104 ........................................................ 5
1.4 Technical Background ............................................................................................................. 6
1.5 Prerequisites ........................................................................................................................... 10
2 Balanced mode .............................................................................................................................11

2.1 Setup ......................................................................................................................................... 11
2.2 Configuration of IEC-101 interface.......................................................................................12
2.3 Configuration of IEC-101 protocol parameters ................................................................ 14
2.5 Configuration of IEC-101/IEC-104 conversion .................................................................. 16
2.6 Enabling of IEC-101/IEC-104 interfaces .............................................................................. 17
2.7 Configuration File ................................................................................................................... 17
3 Unbalanced mode ....................................................................................................................... 18

3.1 Setup ........................................................................................................................................ 18
3.2 Configuration of TCP/IP ........................................................................................................ 20
3.3 Configuration of IEC-101 interface...................................................................................... 20
3.6 Configuration of IEC-101/IEC-104 conversion .................................................................. 26
3.7 Enabling of IEC-101/IEC-104 interfaces ............................................................................. 28
3.8 Configuration File .................................................................................................................. 29
4 Verifying operation .................................................................................................................... 30

4.1 Verification of configuration................................................................................................ 30
4.2 Verification of operation....................................................................................................... 30
5 Ordering Information ................................................................................................................. 31
6 References.................................................................................................................................... 32
20 19- 06- 25 2/ 33
1 Introduction
This document describes the settings required to configure an IEC 60870-5-101 (station side)
conversion to IEC 60870-5-104 (control center side). The feature is available on all EDS500
managed Ethernet products, namely 500NMD and 500NMS series of DIN rail and rack mount
Ethernet products.
1.1 Motivation
Installations regarding the energy grid are typically historically grown and follow a centralized
control approach. In this case a control center – if necessary with the help of downstream
concentrators or control devices – supervises and monitors the process of energy transmis-
sion and distribution. On the transmission level, real-time monitoring and switching of en-
ergy lines as well as determination of power quality values like voltage, current, frequency
and phase are some of the tasks covered by telecontrol protocols.
With the evolvement of decentralized energy generation and to ensure power quality require-
ments, the topics above become also valid for the distribution grid. Field automation and
communication is used to reduce outage and recovery times in modern grids. Remote control
(e.g. of Windfarms), monitoring (e.g. of short circuit indicators) or automated recovery of the
grid are typical applications.
Additionally, fundamental changes take place in the low voltage grid:
- Power generation by renewable energy sources

Energy generated by renewable sources (e.g. solar panels) are coupled via inverters
directly into the low voltage grid. The control or limitation of this energy, directly at
the source or at an adjustable local grid transformer at the medium voltage substa-
tion is desirable but not always possible due to inadequate communication connec-
tions.
- Spreading of remotely connected energy meters

Modern energy meters support remote access, often directly via powerline communi-
cation (PLC) across the low voltage grid. In this case the data of multiple meters are
collected by a concentrator typically residing in the supplying medium voltage sub-
station. Data is collected and transferred multiple times a day or hour (automated
meter reading, AMR). This enables energy suppliers to create accurate local load pro-
files for each substation.
Future changes in energy consumption habits may require changes and adaptations to en-
ergy grids:
- Increased energy demand from consumers due to new technologies

Technology steps such as the introduction of electric cars will lead to a situation
where private and corporate locations add charging poles to their premises, which is
going to significantly increase the load of the energy grid with the potential to sub-
stantially change currently established time-dependent load profiles.
- Introduction of new tariffs

Energy supplying companies will develop new tariff models not only distinguishing
night and day energy but also flexible time-dependent models with multiple price
steps to better control energy demand or to adapt the demand even dynamically to
the energy available. For this scenario not only remotely, readable energy meters are
required but also remotely supervised meters.
2 0 19- 06 - 2 5 3/33
A similar scenario would be even to offer tariffs with individual maximum current or
power ratings. The meter could react to a violation of the maximum committed cur-
rent with a higher tariff or with the disconnection of the power (programmable fuse
principle).
These changes require a highly available and reliable communication infrastructure across all
voltage levels. While on the transmission or high voltage mainly fiber optical communication
media is used, communication possibilities within the distribution grid ranging from low to
medium voltage level are heterogeneous and reaches from mobile radio solution, DSL tech-
nologies based on copper up to fiber optical solutions as well as powerline communication.
Many of the connected medium voltage substations today are still attached via serial FSK
based protocols, like V.23. However, this technology is very limited by data rate which may
lead to delayed processing and notification of process parameters.
More modern systems are based on Ethernet connections, which are realized by copper or
optical fiber and typically offer 20 to 100.000 times more data capacity than serial technolo-
gies. Ethernet furthermore can separate data streams by virtual networks (VLANs) that allow
multiple services over the same connection. This supports different applications (e.g. SCADA,
IP telephony, service access for technicians, …) to be independently operated with distin-
guishable priority. Additionally, growing security demands, e.g. the usage of IP cameras or
the authentication requirement for end devices (IEEE 802.1X) can be handled. Devices of
ABBs EDS500 series allow not only detailed monitoring of the communication infrastructure
via established protocols like SNMP or Syslog but also with telecontrol protocols IEC 60870-5-
101 and IEC 60870-5-104.
While IEC 60870-5-101 supports serial connections, IEC 60870-5-104 is based on TCP/IP tech-
nology. When installing Ethernet or TCP/IP based communication equipment, the telecontrol
protocol must typically be changed, which leads to additional cost for SCADA or control cen-
ter equipment. ABBs EDS500 series decouples this dependency.
1.2 Modernization of Communication Infrastructure

Serial SCADA communication is usually based on IEC 60870-5-101 or similar protocols (e.g.
DNP3) and may be operated in partyline mode. In this mode multiple modems are connected
to the same physical wire (unbalanced, bus operation or multipoint-to-multipoint). In many
cases an upgrade of the complete partyline is not desired. With ABBs EDS500 a step-by-step
exchange is possible, without replacing the SCADA equipment or even changing the configu-
ration of this equipment.
In the first step some serial modems of the partyline can be replaced by DSL switches. The
existing SCADA equipment is connected to the serial port of the DSL switches instead. The
remaining partyline is connected to the DSL switch via the second serial interface which is
correctly configured with the appropriate timing. The serial interfaces of the new switches
are emulating partyline communication.
20 19- 06- 25 4/ 33
Figure 1: Step-by-step replacement of communication
In the last step the complete partyline can be replaces by DSL technology enabled switches.
Existing SCADA equipment can remain operating, while additional bandwidth is now availa-
ble. If SCADA equipment is replaced successively, it can be easily replaced by Ethernet-ena-
bled devices based on IEC 60870-5-104, IEC 61850 or others.
1.3 Migration from IEC 60870-5-101 to IEC 60870-5-104

For SCADA system migration on the long-term to Ethernet, a protocol change to IEC 60870-5-
104, IEC 61850 or Ethernet based DNP3 is typically decided. ABBs Ethernet switches of the
500NMD series (part of EDS500 family) offer an integrated conversion functionality to IEC
60870-5-104. In this case the serial interfaces of the switch are connected to one or more
SCADA devices. The connection of multiple devices can be realized via an existing partyline
installation based on FSK modems. A requirement is the support of IEC 60870-5-101 at the
SCADA device.
For every attached SCADA device, the Ethernet switch provides an additional unique IP ad-
dress, to which one or multiple control centers can connect via IEC 60870-5-104. If necessary
a conversion of telegram types, address formats or timestamps is performed. To enable con-
version in unbalanced mode a relation ASDU address (station address) to link address (IEC
60870-5-101 specific) as well as to local IP address (the control center connects to) must be
configured. There is no need to configure IEC objects (addresses of inputs, outputs, values,
…), these are converted transparently.
Figure 2: Conversion IEC-101 to IEC-104
20 19- 06- 25 5/ 33
If detailed time information in millisecond or better accuracy is required (e.g. for leakage lo-
calization for pipelines), a radio-controlled clock is required at the local SCADA device.
1.4 Technical Background

The protocols IEC 60870-5-101 (short IEC-101) and IEC 60870-5-104 (short IEC-104) are both
used to transmit SCADA data. While IEC-101 is based on a serial transmission of data (e.g. us-
ing RS-232 and FSK based modems), IEC-104 is packet oriented and is based on TCP/IP trans-
mission. Regarding protocol design both know an application protocol data unit (APDU). In
the case of IEC-101 this is embedded in a FT1.2 (defined in IEC 60870-5-2) data frame, in the
case of IEC-104 the transmission control protocol (TCP) with port number 2404 is used. Both
protocols divide a telegram into control information (start byte, length of telegram, control
information) and application data. With IEC-104 the control information is called application
protocol control information (APCI); For IEC-101 this is part of the FT1.2 frame definition. The
format of the application data is – except for some minor differences – identical and is called
application service data unit (ASDU).
The control information is fundamentally different for both protocols. While IEC-101 supports
partyline (polling, multipoint, multidrop, unbalanced) as well as point-to-point (balanced) op-
erating mode, IEC-104 is only defined for point-to-point operation. The tasks of the control
information are connection establishment, retransmission and acknowledge of data as well
as flow control. This is true for both protocols although TCP is already supporting a reliable
end-to-end connection that handles errors and packet loss.
The addressing of end devices for IEC-101 is defined by a one or two byte so called link ad-
dress. The primary station (e.g. control center) uses the link address to select the target sta-
tion (link address is destination address) and sends the telegram. In the case polling (or un-
balanced) mode is used, all connected devices of a line of stations receive the telegram and
the addressed device answers and uses the own address as link address (link address is
source address). While in polling mode a sending approval is given to the addressed station,
this is not required in point-to-point or balanced mode. Primary station and device (or sec-
ondary station) can always send directly.
With IEC-104 the addressing is done by IP address and TCP port number. There are no further
protocol specific addresses. TCP defines a point-to-point connection; Polling mode is no
longer allowed.
To test the availability and correct operation of a substation there are test functions used
with IEC-101 (test function for link layer, linktest) as well as IEC-104 (Test-APDU, TESTFR, test-
frame). If errors are detected, the connection is terminated and re-established.
The definition of an ASDU is identical for both protocols and contains always exactly one
identification field of the data unit as well as one or more information objects. The identifica-
tion field of the data unit specifies the type of the following information objects (type), a var-
iable structure qualifier (amount of transmitted information objects within the ASDU), a
transmission cause (interrogation, command, spontaneous) as well as the common address
of the ASDU (station address). For IEC-101 the transmission cause can have a size of one or
two bytes. If two bytes are used, the second byte specifies the source address. With IEC-104
there are always two bytes. If the source address is not used, the byte is set to zero. The sta-
tion address can also contain one or two bytes with IEC-101, while with IEC-104 always two
bytes are used.
The type identifier defines the structure of the transmitted information objects. This in-
cludes for example single point information and commands (one-bit information), double
point information and commands, bit strings, measured values, counters, and many more,
defined in multiple type with and without timestamps. There is a certain overlap in type iden-
tifiers supported by IEC-101 and IEC-104. However, some IEC-101 types are no longer used in
20 19- 06- 25 6/ 33
IEC-104, on the other hand some IEC-104 types are not supported in IEC-101. The differences
are mainly in the representation of timestamp information. While IEC-101 uses timestamp of
type CP24Time2a, that can represent timing information from one hour down to a millisec-
ond, IEC-104 uses CP56Time2a which extends the one hour to 100 years with the same granu-
larity of one millisecond.
If control centers and devices are strictly following the IEC standards (only the type identifi-
ers for the selected protocol are allowed), a conversion must be done not only regarding the
transmission format, but also regarding the type identifiers. The conversion of type identifi-
ers is listed on the following pages in command as well as in monitoring direction. There is
the option to switch this conversion on or off. With the type conversion switched on, there
are some options in handling the timestamps:
- Do not perform any changes to the timestamp of the substation / device. With this
setting the year, month, day, weekday and hour information are set to zero and the
original incoming timestamp information (minutes and milliseconds) is retained
(CP24Time2A is coped to CP56Time2A. In this case the CP56Time2A is always de-
coded to the range 01.01.2000 00:00:00.000 to 01.01.2000 00:59:59:999 (the date
definition is only shown to complete the definition and is decoded from the bytes set
to zero).
- Replacement of the timestamp of the substation / device during the conversion. In

this case the system time of the switch (must be synchronized via SNTP) is used to
write the timestamp. In the scope of the IEC-standard this is seen as a substituted
time; Accordingly, the bit RES1 (realtime or substituted time) of the timestamp
CP56Time2a is set. If the converting switch does not have valid time information (e.g.
no sync with SNTP time server) the timestamp is marked invalid (bit IV set).
Installation of a conversion solution typically involves an as-is analysis (which covers the pro-
tocol parameters) as well as a conversion concept (which specifies the free parameters of the
conversion, like addresses, types and timestamps).
20 19- 06- 25 7/ 33
Control direction Monitoring direction
Type identifiers IEC-101 / IEC-104 Conversion to IEC-101 type Conversion to IEC-104 type
(default) iec104 iec104 (default) iec101 iec101
convert asdu-types convert no asdu-types convert asdu-types convert no asdu-types
0 UNDEF Not used 0 0 0 0
1 M_SP_NA_1 Single point information 1 1 1 1
2 M_SP_TA_1 Single point information with time tag CP24Time2a 2 2 30 2
3 M_DP_NA_1 Double point information 3 3 3 3
4 M_DP_TA_1 Double point information with time tag CP24Time2a 4 4 31 4
5 M_ST_NA_1 Step position information 5 5 5 5
6 M_ST_TA_1 Step position information with time tag CP24Time2a 6 6 32 6
7 M_BO_NA_1 Bit string of 32 bit 7 7 7 7
8 M_BO_TA_1 Bit string of 32 bit with time tag CP24Time2a 8 8 33 8
9 M_ME_NA_1 Measured value, normalized value 9 9 9 9
10 M_ME_TA_1 Measured value, normalized value with time tag CP24Time2a 10 10 34 10
11 M_ME_NB_1 Measured value, scaled value 11 11 11 11
12 M_ME_TB_1 Measured value, scaled value with time tag CP24Time2a 12 12 35 12
13 M_ME_NC_1 Measured value, short floating point value 13 13 13 13
14 M_ME_TC_1 Measured value, short floating point value and time tag CP24Time2a 14 14 36 14
15 M_IT_NA_1 Integrated totals 15 15 15 15
16 M_IT_TA_1 Integrated totals with time tag CP24Time2a 16 16 37 16
17 M_EP_TA_1 Event of protection equipment with time tag CP24Time2a 17 17 38 17
18 M_EP_TB_1 Packed start events of protection equipment with time tag CP24Time2a 18 18 39 18
Packed output circuit information of protection equipment with time tag
19 M_EP_TC_1 19 19 40 19
CP24Time2a
20 M_PS_NA_1 Packed single-point information with status change detection 20 20 20 20
21 M_ME_ND_1 Measured value, normalized value without quality descriptor 21 21 21 21
22..29 TYPE_22..29 Reserved (standardized area) 22..29 22..29 22..29 22..29
30 M_SP_TB_1 Single point information with time tag CP56Time2a 30 30 30 30
31 M_DP_TB_1 Double point information with time tag CP56Time2a 31 31 31 31
32 M_ST_TB_1 Step position information with time tag CP56Time2a 32 32 32 32
33 M_BO_TB_1 Bit string of 32 bit with time tag CP56Time2a 33 33 33 33
34 M_ME_TD_1 Measured value, normalized value with time tag CP56Time2a 34 34 34 34
35 M_ME_TE_1 Measured value, scaled value with time tag CP56Time2a 35 35 35 35
36 M_ME_TF_1 Measured value, short floating point value and time tag CP56Time2a 36 36 36 36
37 M_IT_TB_1 Integrated totals with time tag CP56Time2a 37 37 37 37
38 M_EP_TD_1 Event of protection equipment with time tag CP56Time2a 38 38 38 38
39 M_EP_TE_1 Packed start events of protection equipment with time tag CP56Time2a 39 39 39 39
Packed output circuit information of protection equipment with time tag
40 M_EP_TF_1 40 40 40 40
CP56Time2a
45 C_SC_NA_1 Single command 45 45 58 45
46 C_DC_NA_1 Double command 46 46 59 46
47 C_RC_NA_1 Regulating step command 47 47 60 47
48 C_SE_NA_1 Setpoint command, normalized value 48 48 61 48
20 19- 06- 25 8/33

49 C_SE_NB_1 Setpoint command, scaled value 49 49 62 49
50 C_SE_NC_1 Setpoint command, short floating point value 50 50 63 50
51 C_BO_NA_1 Bit string of 32 bit 51 51 64 51
58 C_SC_TA_1 Single command with time tag CP56Time2a 45 58 58 58
59 C_DC_TA_1 Double command with time tag CP56Time2a 46 59 59 59
60 C_RC_TA_1 Regulating step command with time tag CP56Time2a 47 60 60 60
61 C_SE_TA_1 Setpoint command, normalized value with time tag CP56Time2a 48 61 61 61
62 C_SE_TB_1 Setpoint command, scaled value with time tag CP56Time2a 49 62 62 62
63 C_SE_TC_1 Setpoint command, short floating point value and time tag CP56Time2a 50 63 63 63
64 C_BO_TA_1 Bit string of 32 bit with time tag CP56Time2a 51 64 64 64
70 M_EI_NA_1 End of initialization 70 70 70 70
100 C_IC_NA_1 (General-, Station-) Interrogation command 100 100 100 100
101 C_CI_NA_1 Counter interrogation command 101 101 101 101
102 C_RD_NA_1 Read command 102 102 102 102
103 C_CS_NA_1 Clock synchronization command 103 103 103 103
104 C_TS_NA_1 Test command 104 104 107 104
105 C_RP_NA_1 Reset process command 105 105 105 105
106 C_CD_NA_1 Delay acquisition command 106 106 106 106
107 C_TS_TA_1 Test command with time tag CP56Time2a 104 107 107 107
110 P_ME_NA_1 Parameter of measured value, normalized value 110 110 110 110
111 P_ME_NB_1 Parameter of measured value, scaled value 111 111 111 111
112 P_ME_NC_1 Parameter of measured value, short floating point value 112 112 112 112
113 P_AC_NA_1 Parameter activation 113 113 113 113
120 F_FR_NA_1 File ready 120 120 120 120
121 F_SR_NA_1 Section ready 121 121 121 121
122 F_SC_NA_1 Call directory, select file, call file, call section 122 122 122 122
123 F_LS_NA_1 Last section, last segment 123 123 123 123
124 F_FA_NA_1 Ack file, Ack section 124 124 124 124
125 F_SG_NA_1 Segment 125 125 125 125
126 F_DR_TA_1 Directory 126 126 126 126
127..255 TYPE_127..255 Reserved (user-defined area) 127..255 127..255 127..255 127..255
2 0 19- 06 - 2 5 9/33
1.5 Prerequisites
This application note references to 500NMDxx firmware version 2.0.8 (or later), the device
used in this example is ABBs DIN-rail Ethernet and SHDSL switch series 500NMDxx.
20 19- 06- 25 1 0/ 33
2 Balanced mode
2.1 Setup
Chapter 2 describes a balanced (or point-to-point) setup. The IEC protocol relies on a full du-
plex (data can be sent in both directions simultaneously) RS-232 (V.24) based communication.
In the example the substation shall be upgraded to Ethernet without the change of the
SCADA equipment. Therefore, an Ethernet switch of the 500NMD series is installed (500NMD
switches can include copper or fiber optical WAN communication ports). According to the
long-term strategy of the energy supplier all Ethernet-enabled substations shall communi-
cate with IEC-104.
Figure 3: IEC conversion setup
The SCADA equipment installed is an RTU (Remote Telecontrol Unit) operating with IEC-101.
The IEC-101 link address is 20.
The following chapter describes the configuration tasks required to setup conversion from
RTU (IEC-101 side) to the control center (IEC-104 side); Configuration tasks for general con-
nectivity (IP Addresses, SNMP, VLANs, …) are not covered.
The configuration references to the protocol settings defined by the energy supplier as fol-
lowing.
Protocol parameters given for IEC-101
Parameter Setting
Network configuration Point-to-point

Transmission speed 1200 bps
Data bits 8
Parity even
Stop bits 1
Link transmission procedure Balanced transmission
Address field of the link One octet
Common address of ASDU Two octets
Information object address Two octets, structured 8-8
Cause of transmission One octet
Use of single control character E5 Not used
Timeout monitoring 10 s
Link address 20
20 19- 06- 25 1 1/ 33
Parameter Setting

Information object address Three octets, structured 8-8-8
Cause of transmission Two octets
Timeout monitoring (T0/T1/T2/T3) 30/15/10/20 s
Unacknowledged APDUs k 12
Unackownledged APDUs before Ack w 8
2.2 Configuration of IEC-101 interface

For a connection to be established via IEC-101 a serial (RS-232 or RS-485) interface is required
to be configured to match the configuration of the end device (RTU, PLC or IED). The typical
RS-232 parameters for IEC-101 are 1200 Baud, 8 data bits, even parity, 1 stop bit.
Tasks
Description
CLI command Webserver command
Set baudrate to ’1200’.

set interface console0 baudrate Interfaces
1200  console0
 Interface parameters ”Baudrate: 1200”
Set parity to ’even’.

set interface console0 parity even Interfaces
 console0
 Interface parameters ”Parity: even”
Set number of databits to ’8’.

set interface console0 databits 8 Interfaces
 console0
 Interface parameters ”Databits: 8”
Set number of stopbit(s) to ’1’.

set interface console0 stopbits 1 Interfaces
 console0
 Interface parameters ”Stopbits: 1”
Set dcd mode to active while data is transmitted. This means that the DCD signal is asserted
together with the data transmitted.
set interface console0 dcd while- Interfaces
tx  console0
 Interface parameters ”DCD: while-tx”
20 19- 06- 25 12 / 33
Optional: Assert the DCD signal 10 milliseconds before the first byte of data is transmitted.
This can be used to buffer data to prevent gaps in the transmission or to control the carrier
signal on a leased-line modem based on FSK technology.
set interface console0 dcd-setup Interfaces
10  console0
 Interface parameters ”DCD setup time: 10”
Optional: Keep the DCD signal asserted 5 milliseconds after the last byte of data is
transmitted. The setting might be needed to assure the last bytes is correctly handled by the
end device. It can be also used for carrier control on a leased-line modem based on FSK
technology.
set interface console0 dcd-follow- Interfaces
up 5  console0
 Interface parameters ”DCD follow up time: 5”
Change the interface mode to handle IEC-101 data.

set interface console0 mode iec- Interfaces
101  console0
 Interface mode ”IEC-101”
20 19- 06- 25 1 3/ 33
2.3 Configuration of IEC-101 protocol parameters
For IEC-101 several parameters controlling the protocol need to be set. This includes mainly
the length of addresses, in this example typical values are used. EDS500 offers two independ-
ent IEC-101 interfaces, the example below references to configuring the first interface.
In balanced mode there is no need for configuration of ASDU addresses, since these (and the
object addresses) are converted transparently.
Tasks
Description
Set the function of the device to be link master.

set iec101 interface 1 function IEC-101/104
master  iec 101 interface 1
 Interface settings ”function: master”
Attach virtual ”iec101 interface 1” to a physical interface (console0)

set iec101 interface 1 attach IEC-101/104
console0 balanced  iec 101 interface 1
 Interface attachment (check balanced)
Set IEC-101 link address length to 1 byte.

set iec101 interface 1 length IEC-101/104
link-address 1  iec 101 interface 1
 Protocol settings ”Link address: 1”
Set IEC-101 station address length to 2 bytes.

station-address 2  iec 101 interface 1
 Protocol settings ”Station address: 2”
Set IEC-101 object address length to 2 bytes.

object-address 2  iec 101 interface 1
 Protocol settings ”Object address: 2”
Optional: Set IEC-101 object address structure. This is only used for presentation purposes to
the user. The number of total bits must be represented in a structure delimeted by ’-’.
set iec101 interface 1 object IEC-101/104
structure 8-8  iec 101 interface 1
 Protocol settings ”Object structure: 8-8”
Set IEC-101 cause of transmission (COT) length to 1 byte.

transmission-cause 1  iec 101 interface 1
 Protocol settings ”Transmission cause: 1”
Set usage of single character acknowledgement to ’none’. Alternatives are used from station
’rx’, used in send and receive direction ’rx-tx’ or in send and receive direction as well as
acknownledge if no data is available ’nodata-rx-tx’.
set iec101 interface 1 single- IEC-101/104
character none  iec 101 interface 1
 Protocol settings ”Single character: none”
Set the conversion scheme for ASDU types. Automated conversion of types is disabled.
20 19- 06- 25 14 / 33
set iec101 interface 1 convert no - not supported -
asdu-types
Set the conversion scheme for timestamps. Automated conversion of timestamps is disabled.
timestamps
Set the link adress of the station. In this example the link adress is ’20’ (decimal).
set iec101 interface 1 link - not supported -
address 20

For IEC-104 several parameters controlling the protocol need to be set. This includes mainly
the length of addresses, in this example typical values are used. EDS500 offers two independ-
ent IEC-104 interfaces, the example below references to configuring the first interface.
Tasks
Description


structure 8-8-8  iec 104 interface 1
 Protocol settings ”Object structure: 8-8-8”
Set IEC-101 cause of transmission (COT) length to 2 bytes.

20 19- 06- 25 15 / 33
2.5 Configuration of IEC-101/IEC-104 conversion
After configuring the interface and protocol parameters the conversion itself must be config-
ured.
Tasks
Description
Set conversion relation IEC-101 to IEC-104.

set iec101 interface 1 convert to - not supported -
iec104 interface 1
iec101 interface 1
Conversion scheme to convert 2 bytes IEC-101 object adresses to 3 bytes IEC-104 object
adresses. One of the three octets of IEC-104 must be set to zero in IEC-101 to IEC-104
conversion. This octet will be ignored in conversion direction IEC-104 to IEC-101. The setting
’high’ means to ignore the high-order byte (a-b becomes 0-a-b), ’middle’ ignores the 2nd octet
(a-b becomes a-0-b), while ’low’ ignored the low-order byte (a-b becomes a-b-0). In the case of
setting the value to ’high’ the decimal representation will change if only 16 bits are used for
addressing.
set iec104 interface 1 convert - not supported -
obj-adr-zero-byte high
Disable the switch station (for monitoring via IEC-104) itself to answer IEC-104 requests as
local station.
set iec104 interface 1 local- IEC-101/104
station no enable  iec 104 interface 1
 Local station settings ”disable”
Disable the conversion of ACKs from IEC-104 side to IEC-101. This allows the IEC-101 side to
acknowledge frames even if no acknowledge from IEC-104 has been received. The setting is
necessary, because otherwise IEC-101 side would be blocked until a IEC-104 acknowledge is
received. If this is not desired the value window size ”w” for IEC-104 must be set to ”1” in the
IEC-104 contol center or master station.
acknowledge
Optional: Disable conversion of IEC-104 ASDU types not supported natively with IEC-101 in
direction IEC-104 to IEC-101.
asdu-types
Optional: Disable conversion of IEC-101 ASDU types to new IEC-104 ASDU types. This includes
conversion of IEC-101 confirm messages in direction IEC-101 to IEC-104.
asdu-types
Optional: Allow multiple masters (control centers) to be active (StartDT act) at the same time.
Incoming station data is sent to all control centers if this setting is active. If the setting is not
active the second master is declined as soon as a second StartDT act is issued.
set iec104 interface 1 control- - not supported -
center multiple-active
20 19- 06- 25 16/ 33

2.6 Enabling of IEC-101/IEC-104 interfaces
After all settings are done, the IEC interfaces can be activated to apply the configuration.
Nevertheless configuration changes “on the fly” are possible even with activated interfaces.
However, this may lead to unpredictable behavior due to non-awareness of station and con-
trol center.
Tasks
Description
Enable IEC-104 interface.

set iec101 interface 1 no shutdown IEC-101/104
 iec 104 interface 1
 Interface settings ”Admin state: up”
Enable IEC-104 interface.

2.7 Configuration File

The listing below represents the configuration file.
! version 2.0
! common
set iec101 interface 1 attach console0 balanced
set iec101 interface 1 convert no asdu-types (optional)
set iec101 interface 1 convert no timestamps (optional)
set iec101 interface 1 convert to iec104 interface 1
set iec101 interface 1 function master
set iec101 interface 1 length link-address 1
set iec101 interface 1 link address 20
set iec101 interface 1 object structure 8-8 (optional)
set iec104 interface 1 control-center multiple-active (optional)
set iec104 interface 1 convert no acknowledge
set iec104 interface 1 convert obj-adr-zero-byte high
set iec104 interface 1 local-station no enable
set iec104 interface 1 object structure 8-8-8 (optional)
set interface console0 baudrate 1200
set interface console0 dcd-follow-up 5 (optional)
set interface console0 dcd-setup 10 (optional)
set interface console0 mode iec101
set interface console0 parity even
set system web-server enable
! interface state
set iec101 interface 1 no shutdown
set switch port1 no shutdown
20 19- 06- 25 17 / 33
3 Unbalanced mode
3.1 Setup
Chapter 3 describes an unbalanced (or multipoint, also referenced as multidrop of partyline)
setup. The IEC protocol relies on a half-duplex multidrop lines using FSK based analogue mo-
dems and an aggregation ring using PDH multiplexer with copper and fiber optical connec-
tions. The energy supplier’s migration path to Ethernet includes replacing the PDH ring by
Ethernet switches, but leaving the multidrop lines including the analogue modems un-
touched.
Figure 4: As-Is Setup
The PDH ring connects several substations which all use a similar setup then the substation
named “University”. The substation consists of a directly connected RTU to the PDGH multi-
plexer and two additional RTUs connected by analogue modems to remote locations.
Figure 5: Target Setup
The targeted Ethernet based ring is based on ABBs 500NMD series. These devices can pro-
vide connection via copper or fiber optical media and are able to convert from (SCADA equip-
ment side) IEC 60870-5-101 to (control center side) IEC 60870-5-104.
20 19- 06- 25 18 / 33
The different conversion targets are identified by its common address of the ASDU (station
address). On the IEC-101 side the station address is mapped to a link address. On the IEC-104
side it is mapped to a local IP address.
Figure 6: Operation of conversion
The following chapter describes the configuration tasks required to setup the conversion
from the multidrop line and the directly connected RTU (IEC-101 side) to the control center
(IEC-104 side). Configuration tasks for general connectivity (SNMP, VLANs, …) are not cov-
ered.
The configuration references to the protocol settings defined by the energy supplier as fol-
lowing.
Parameter Setting
Network configuration Multipoint-partyline

Transmission speed 1200 bps
Data bits 8
Parity even
Stop bits 1
Link transmission procedure Unbalanced transmission
Address field of the link One octet
Information object address Two octets, structured 8-8
Cause of transmission One octet
Use of single control character E5 Not used
Timeout monitoring 10 s
Link addresses 10, 20, 21
ASDU addresses 0x800a, 0x8014, 0x8015
Data type send Data 1 and Data 2
20 19- 06- 25 1 9/ 33
Parameter Setting

Information object address Three octets, structured 8-8-8
Cause of transmission Two octets
Timeout monitoring (T0/T1/T2/T3) 30/15/10/20 s
Unacknowledged APDUs k 12
Unackownledged APDUs before Ack w 8
3.2 Configuration of TCP/IP

The IEC conversion implies conversion from multipoint (IEC-101) to point-to-point (IEC-104).
Therefore, every IEC-101 equipment requires one unique IP address the control center can
connect to.
Tasks
Description
Provide IP addresses for IEC-101 equipment

set system ip 192.168.1.51 - not supported -
192.168.1.53
3.3 Configuration of IEC-101 interface

For a connection to be established via IEC-101 a serial (RS-232) interface is required to be con-
figured to match the configuration of the end device (RTU, PLC or IED). The typical RS-232 pa-
rameters for IEC-101 are 1200 Baud, 8 data bits, even parity, 1 stop bit.
In the example the RTU that has been connected directly to the PDH is connected to this first
serial port of the 500NMD (Console0). The two RTUs connected via analogue FSK based mo-
dems are connected to Console1, therefore Console1 is connected to an analogue FSK mo-
dem.
Tasks – Console0 (directly connected RTU)
Description

1200  console0
20 19- 06- 25 20 / 33
 console0

 console0

 console0

101  console0
Tasks – Console1 (connected to FSK modem)
Description

1200  console0

 console0

 console0

 console0
Set dcd mode to active while data is transmitted. This means that the DCD signal is asserted
together with the data transmitted.
set interface console0 dcd while- Interfaces
tx  console0
 Interface parameters ”DCD: while-tx”
20 19- 06- 25 21 / 33
Optional: Assert the DCD signal 10 milliseconds before the first byte of data is transmitted.
This can be used to buffer data to prevent gaps in the transmission or to control the carrier
signal on a leased-line modem based on FSK technology.
set interface console0 dcd-setup Interfaces
10  console0
 Interface parameters ”DCD setup time: 10”
Optional: Keep the DCD signal asserted 5 milliseconds after the last byte of data is
transmitted. The setting might be needed to assure the last bytes is correctly handled by the
end device. It can be also used for carrier control on a leased-line modem based on FSK
technology.
set interface console0 dcd-follow- Interfaces
up 5  console0
 Interface parameters ”DCD follow up time: 5”

101  console0

To configure the IEC protocols, virtual interfaces are generated within the 500NMD switch.
These represent the set of parameters used to control the IEC protocol. The setting must be
performed for IEC-101 and IEC-104 separately; For conversion the set of parameters for IEC-
101 and IEC-104 are linked together. In the example we create two IEC-101 interfaces: One for
the directly connected RTU (“iec101 interface 1”) and one for the remaining partyline (“iec101
interface 2”).
Tasks – IEC-101 interface 1 (directly connected RTU)
Description


console0 unbalanced  iec 101 interface 1
 Interface attachment


20 19- 06- 25 22 / 33

Set the type of data polling. Polling is possible for ”data1”, ”data2” or automatically switched
”auto”.
set iec101 interface 1 poll auto - not supported -
Create the ASDU (station) address to link adress relation. In this example station address of
substation ”University” 0x8014 (hexadecimal) is linked to link adress is ’20’ (decimal).
set iec101 interface 1 remote- - not supported -
station address 0x800a link
address 10
Tasks – IEC-101 interface 2 (directly connected RTU)
Description


console1 unbalanced  iec 101 interface 1
 Interface attachment

20 19- 06- 25 2 3/ 33


Set the type of data polling. Polling is possible for ”data1”, ”data2” or automatically switched
”auto”.
set iec101 interface 2 poll auto - not supported -
Create the ASDU (station) address to link adress relation. In this example the station
addresses of the substations ”University – Campus West” 0x800a (hexadecimal) and
”University – Campus East” 0x800b (hexadecimal) are linked to link adresses is ’10’ (decimal)
for ”Campus West” and ’11’ for ”Campus East”.
station address 0x8014 link
address 20
station address 0x8015 link
address 21
20 19- 06- 25 24 / 33
As for IEC-101, two IEC-104 interfaces must be configured as conversion counterpart to IEC-
101. The configuration includes mainly address lengths. The configuration is identical for
“iec104 interface 1” and “iec104 interface 2”. The task list represents “interface 1” and must be
repeated for “interface 2”.
Tasks – IEC-104 interface 1 and IEC-104 interface 2
Description


structure 8-8-8  iec 104 interface 1
 Protocol settings ”Object structure: 8-8-8”
Set IEC-101 cause of transmission (COT) length to 2 bytes.

The station addresses (ASDU addresses) must be configured per interface.
20 19- 06- 25 25/ 33

Tasks – Configure ASDU addresses
Description
Create the ASDU (station) address to local IP adress relation for interface 1. In this example the
station addresses of the substation ”University” 0x8014 (hexadecimal) is linked to local IP
adresses 192.168.1.51.
station address 0x800a ip-address
192.168.1.51
Create the ASDU (station) address to local IP adress relation for interface 2. In this example the
station addresses of the substations ”University – Campus West” 0x800a (hexadecimal) and
”University – Campus East” 0x800b (hexadecimal) are linked to local IP adresses 192.168.1.52
for ”Campus West” and 192.168.1.53 for ”Campus East”.
station address 0x8014 ip-address
192.168.1.52
station address 0x8015 ip-address
192.168.1.53
3.6 Configuration of IEC-101/IEC-104 conversion

After configuring the interface and protocol parameters the conversion itself must be config-
ured. The configuration is identical for “iec104 interface 1” and “iec104 interface 2”. The task
list represents “interface 1” and must be repeated for “interface 2”.
Tasks
Description

iec104 interface 1
iec101 interface 1
Conversion scheme to convert 2 bytes IEC-101 object adresses to 3 bytes IEC-104 object
adresses. One of the three octets of IEC-104 must be set to zero in IEC-101 to IEC-104
conversion. This octet will be ignored in conversion direction IEC-104 to IEC-101. The setting
’high’ means to ignore the high-order byte (a-b becomes 0-a-b), ’middle’ ignores the 2nd octet
(a-b becomes a-0-b), while ’low’ ignored the low-order byte (a-b becomes a-b-0). In the case of
setting the value to ’high’ the decimal representation will change if only 16 bits are used for
addressing.
set iec104 interface 1 convert - not supported -
obj-adr-zero-byte high
Disable the switch station (for monitoring via IEC-104) itself to answer IEC-104 requests as
local station.
20 19- 06- 25 26/ 33

set iec104 interface 1 local- IEC-101/104
station no enable  iec 104 interface 1
 Local station settings ”disable”
Optional: Disable conversion of IEC-101 ASDU types to new IEC-104 ASDU types. This includes
conversion of IEC-101 confirm messages in direction IEC-101 to IEC-104.
asdu-types
Disable the conversion of ACKs from IEC-104 side to IEC-101. This allows the IEC-101 side to
acknowledge frames even if no acknowledge from IEC-104 has been received. The setting is
necessary, because otherwise IEC-101 side would be blocked until a IEC-104 acknowledge is
received. If this is not desired the value window size ”w” for IEC-104 must be set to ”1” in the
IEC-104 contol center or master station.
acknowledge
Optional: Disable conversion of IEC-104 ASDU types not supported natively with IEC-101 in
direction IEC-104 to IEC-101.
asdu-types
Optional: Disable conversion or insertion of timestamps.
timestamps
Optional: Disable conversion or insertion of timestamps.
timestamps
Optional: Allow multiple masters (control centers) to be active (StartDT act) at the same time.
Incoming station data is sent to all control centers if this setting is active. If the setting is not
active the second master is declined as soon as a second StartDT act is issued.
set iec104 interface 1 control- - not supported -
center multiple-active
20 19- 06- 25 27/ 33

3.7 Enabling of IEC-101/IEC-104 interfaces
After all settings are done, the IEC interfaces can be activated to apply the configuration.
Nevertheless, configuration changes “on the fly” are possible even with activated interfaces.
However, this may lead to unpredictable behavior due to non-awareness of station and con-
trol center.
Tasks
Description
Enable IEC-104 interface 1.




20 19- 06- 25 28 / 33
3.8 Configuration File
The listing below represents the configuration file.
! version 2.0
! common
set iec101 interface 1 attach console0 unbalanced
set iec101 interface 1 link address 20
set iec101 interface 1 poll auto
set iec101 interface 1 remote-station address 0x800a link address 10
set iec101 interface 2 attach console1 unbalanced
set iec101 interface 2 poll auto
set iec101 interface 2 remote-station address 0x8014 link address 20
set iec101 interface 2 remote-station address 0x8015 link address 21
set iec104 interface 1 remote-station address 0x800a ip-address 192.168.1.51
set iec104 interface 2 remote-station address 0x8014 ip-address 192.168.1.52
set iec104 interface 2 remote-station address 0x8015 ip-address 192.168.1.53
set interface console1 dcd-follow-up 5 (optional)
set interface console1 dcd-setup 10 (optional)
set system web-server enable
! interface state
20 19- 06- 25 2 9/ 33
4 Verifying operation
There are several commands to verify the operation of IEC conversion.
4.1 Verification of configuration

Description

Display IEC-101 information on protocol settings.
show iec101 IEC-101/104
Display IEC-104 information on protocol settings.
show iec104 IEC-101/104
Display IEC-101 conversion information.
show iec101 converter IEC-101/104
Display IEC-104 conversion information.
show iec104 converter IEC-101/104
4.2 Verification of operation

Description
To monitor the operation of the IEC conversion on any CLI interface (Console, Telnet, SSH) the
command ’terminal monitor’ must be issued in enabled mode to monitor events on the
connected CLI.
terminal monitor - not supported -
Enable the generation of IEC-101 events.
debug iec101 - not supported -
Enable the generation of IEC-104 events.
debug iec104 - not supported -
After all events are collected event generation should be disabled for each protocol, or for all
events (clear debug).
debug no iec101 - not supported -
debug no iec104
clear debug
The general logging of events at the connected CLI can be terminated.
terminal no monitor - not supported -
2 0 19- 06 - 2 5 3 0/ 3 3
5 Ordering Information
For order numbers regarding 500NMDxx the table below can be used. To connect IEC-101 via
RS-232 a shielded serial cable (e.g. 500CAB05 or 500CAB06) is recommended.
Product Ident no Description
500NMD01 R0002 1KHW025096R0002 4xRJ-45, 1xSHDSL, 1xRS-232

500NMD02 R0002 1KHW025097R0002 4xRJ-45, 2xSHDSL, 2xRS-232
500NMD11 R0002 1KHW027869R0002 4xRJ-45, 1xSHDSL, 1xSFP, 2xRS-232
500NMD20 R0002 1KHW025098R0002 4xRJ-45, 2xSFP, 2xRS-232
500NMD30 R0002 1KGT038890R0002 4xRJ-45, 1xRS-232
500NMD40 R0001 1KGT038891R0001 4xRJ-45, 1xRS-232, POE 280W
500NMD40 R0002 1KGT038891R0002 4xRJ-45, 1xRS-232, POE 36W
500NMD41 R0001 1KGT038892R0001 4xRJ-45, 1xSHDSL, 1xRS-232,
POE 280W
POE 36W
POE 280W
POE 36W
500NMD43 R0001 1KGT038894R0001 4xRJ-45, 1xSHDSL, 1xSFP, 2xRS-232,
POE 280W
500NMD43 R0002 1KGT038894R0002 4xRJ-45, 1xSHDSL, 1xSFP, 2xRS-232,
POE 36W
500NMD44 R0001 1KGT038895R0001 4xRJ-45, 2xSFP, 2xRS-232, POE
280W
500NMD44 R0002 1KGT038895R0002 4xRJ-45, 2xSFP, 2xRS-232, POE 36W
500CAB03 R0001 1KGT038909R0001 Serial configuration cable DB9-F
500CAB05 R0001 1KGT038911R0001 Shielded serial cable DB25-F
500CAB06 R0001 1KGT038912R0001 Shielded serial cable DB9-F
500CAB09 R0001 1KGT038916R0001 RTU500 connection cable RJ-45
500NMA01 R0001 1KGT038909R0001 Configuration stick
2 0 19- 06 - 2 5 3 1/ 3 3
6 References
Product Reference(s)
500NMDxx Presentation
500NMDxx Brochure
Contact
Technical questions: de-eds-sales-support@abb.com

Comercial topics, orders: substationautomation-products@de.abb.com
2 0 19- 06 - 2 5 32/33
—
ABB AG
Power Grids
Postfach 10 03 51
68128 Mannheim
Deutschland
solutions.abb/eds500
—
We reserve the right to at all times make technical changes as well as changes
to the contents of this document without prior notice.
The detailed specifications agreed to at the time of ordering apply to all orders.
ABB accepts no responsibility for possible errors or incompleteness in this
document.
We reserve all rights to this document and the topics and illustrations contained
therein. The document and its contents, or extracts thereof, must not be
reproduced, transmitted or reused by third parties without prior written consent
by ABB.
All rights reserved.

1KGT151051 IEC Conversion PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

1KGT151051 IEC Conversion PDF

Încărcat de

Drepturi de autor:

Formate disponibile

—

2 Balanced mode .............................................................................................................................11

3 Unbalanced mode ....................................................................................................................... 18

4 Verifying operation .................................................................................................................... 30

5 Ordering Information ................................................................................................................. 31

Additionally, fundamental changes take place in the low voltage grid:

- Power generation by renewable energy sources

- Spreading of remotely connected energy meters

- Increased energy demand from consumers due to new technologies

- Introduction of new tariffs

1.2 Modernization of Communication Infrastructure

1.3 Migration from IEC 60870-5-101 to IEC 60870-5-104

Figure 2: Conversion IEC-101 to IEC-104

1.4 Technical Background

- Replacement of the timestamp of the substation / device during the conversion. In

20 19- 06- 25 8/33

Figure 3: IEC conversion setup

Protocol parameters given for IEC-101

Network configuration Point-to-point

Common address of ASDU Two octets

2.2 Configuration of IEC-101 interface

CLI command Webserver command

Set baudrate to ’1200’.

Set parity to ’even’.

Set number of databits to ’8’.

Set number of stopbit(s) to ’1’.

Change the interface mode to handle IEC-101 data.

Set the function of the device to be link master.

Attach virtual ”iec101 interface 1” to a physical interface (console0)

Set IEC-101 link address length to 1 byte.

Set IEC-101 station address length to 2 bytes.

Set IEC-101 object address length to 2 bytes.

Set IEC-101 cause of transmission (COT) length to 1 byte.

2.4 Configuration of IEC-104 protocol parameters

CLI command Webserver command

Set IEC-104 station address length to 2 bytes.

Set IEC-101 object address length to 3 bytes.

Set IEC-101 cause of transmission (COT) length to 2 bytes.

Set conversion relation IEC-101 to IEC-104.

20 19- 06- 25 16/ 33

Enable IEC-104 interface.

Enable IEC-104 interface.

2.7 Configuration File

Figure 4: As-Is Setup

Figure 5: Target Setup

Figure 6: Operation of conversion

Protocol parameters given for IEC-101

Network configuration Multipoint-partyline

Common address of ASDU Two octets

3.2 Configuration of TCP/IP

Provide IP addresses for IEC-101 equipment

3.3 Configuration of IEC-101 interface

Tasks – Console0 (directly connected RTU)

CLI command Webserver command

Set baudrate to ’1200’.

Set number of databits to ’8’.

Set number of stopbit(s) to ’1’.

Change the interface mode to handle IEC-101 data.

Tasks – Console1 (connected to FSK modem)

CLI command Webserver command

Set baudrate to ’1200’.

Set parity to ’even’.

Set number of databits to ’8’.