Professional Documents
Culture Documents
1KGT151051 IEC Conversion
1KGT151051 IEC Conversion
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
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.
Future changes in energy consumption habits may require changes and adaptations to en-
ergy grids:
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.
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.
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.
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.
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).
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
41..44 TYPE_41..44 Reserved (standardized area) 41..44 41..44 41..44 41..44
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
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.
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.
Parameter Setting
20 19- 06- 25 1 1/ 33
Protocol parameters given for IEC-104
Parameter Setting
Tasks
Description
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”
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
CLI command Webserver command
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 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.
set iec101 interface 1 convert no - not supported -
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
Tasks
Description
Optional: Set IEC-104 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 iec104 interface 1 object IEC-101/104
structure 8-8-8 iec 104 interface 1
Protocol settings ”Object structure: 8-8-8”
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
CLI command Webserver command
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.
set iec104 interface 1 convert no - not supported -
acknowledge
Optional: Disable conversion of IEC-104 ASDU types not supported natively with IEC-101 in
direction IEC-104 to IEC-101.
set iec104 interface 1 convert no - not supported -
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.
set iec101 interface 1 convert no - not supported -
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
Tasks
Description
CLI command Webserver command
! 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 no asdu-types (optional)
set iec104 interface 1 convert no timestamps (optional)
set iec104 interface 1 convert obj-adr-zero-byte high
set iec104 interface 1 convert to iec101 interface 1
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 iec104 interface 1 no shutdown
set switch port1 no shutdown
set switch port2 no shutdown
set switch port3 no shutdown
set switch port4 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.
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.
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.
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
20 19- 06- 25 1 9/ 33
Protocol parameters given for IEC-104
Parameter Setting
Tasks
Description
CLI command Webserver command
Description
20 19- 06- 25 20 / 33
Set parity to ’even’.
set interface console0 parity even Interfaces
console0
Interface parameters ”Parity: even”
Description
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”
Description
20 19- 06- 25 22 / 33
Set IEC-101 object address length to 2 bytes.
set iec101 interface 1 length IEC-101/104
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 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 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
Description
20 19- 06- 25 2 3/ 33
Set IEC-101 station address length to 2 bytes.
set iec101 interface 2 length IEC-101/104
station-address 2 iec 101 interface 1
Protocol settings ”Station 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 2 object IEC-101/104
structure 8-8 iec 101 interface 1
Protocol settings ”Object structure: 8-8”
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 2 single- IEC-101/104
character none iec 101 interface 1
Protocol settings ”Single character: none”
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”.
set iec101 interface 2 remote- - not supported -
station address 0x8014 link
address 20
set iec101 interface 2 remote- - not supported -
station address 0x8015 link
address 21
20 19- 06- 25 24 / 33
3.5 Configuration of IEC-104 protocol parameters
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”.
Description
CLI command Webserver command
Optional: Set IEC-104 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 iec104 interface 1 object IEC-101/104
structure 8-8-8 iec 104 interface 1
Protocol settings ”Object structure: 8-8-8”
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.
set iec104 interface 1 remote- - not supported -
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”.
set iec104 interface 2 remote- - not supported -
station address 0x8014 ip-address
192.168.1.52
set iec104 interface 2 remote- - not supported -
station address 0x8015 ip-address
192.168.1.53
Tasks
Description
CLI command Webserver command
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.
set iec101 interface 1 convert no - not supported -
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.
set iec104 interface 1 convert no - not supported -
acknowledge
Optional: Disable conversion of IEC-104 ASDU types not supported natively with IEC-101 in
direction IEC-104 to IEC-101.
set iec104 interface 1 convert no - not supported -
asdu-types
Optional: Disable conversion or insertion of timestamps.
set iec101 interface 1 convert no - not supported -
timestamps
Optional: Disable conversion or insertion of timestamps.
set iec104 interface 1 convert no - not supported -
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
Tasks
Description
CLI command Webserver command
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 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 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 convert no asdu-types (optional)
set iec101 interface 2 convert no timestamps (optional)
set iec101 interface 2 convert to iec104 interface 2
set iec101 interface 2 function master
set iec101 interface 2 length link-address 1
set iec101 interface 2 object structure 8-8 (optional)
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 control-center multiple-active (optional)
set iec104 interface 1 convert no acknowledge
set iec104 interface 1 convert no asdu-types (optional)
set iec104 interface 1 convert no timestamps (optional)
set iec104 interface 1 convert obj-adr-zero-byte high
set iec104 interface 1 convert to iec101 interface 1
set iec104 interface 1 local-station no enable
set iec104 interface 1 object structure 8-8-8 (optional)
set iec104 interface 1 remote-station address 0x800a ip-address 192.168.1.51
set iec104 interface 2 control-center multiple-active (optional)
set iec104 interface 2 convert no acknowledge
set iec104 interface 2 convert no asdu-types (optional)
set iec104 interface 2 convert no timestamps (optional)
set iec104 interface 2 convert obj-adr-zero-byte high
set iec104 interface 2 convert to iec101 interface 2
set iec104 interface 2 local-station no enable
set iec104 interface 2 object structure 8-8-8 (optional)
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 console0 baudrate 1200
set interface console0 mode iec101
set interface console0 parity even
set interface console1 baudrate 1200
set interface console1 dcd-follow-up 5 (optional)
set interface console1 dcd-setup 10 (optional)
set interface console1 mode iec101
set interface console1 parity even
set system web-server enable
! interface state
set iec101 interface 1 no shutdown
set iec101 interface 2 no shutdown
set iec104 interface 1 no shutdown
set iec104 interface 2 no shutdown
set switch port1 no shutdown
set switch port2 no shutdown
set switch port3 no shutdown
set switch port4 no shutdown
20 19- 06- 25 2 9/ 33
4 Verifying operation
There are several commands to verify the operation of IEC conversion.
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.
2 0 19- 06 - 2 5 3 1/ 3 3
6 References
Product Reference(s)
500NMDxx Presentation
500NMDxx Brochure
Contact
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.