Professional Documents
Culture Documents
E560 IEC60870-5-104 Host
E560 IEC60870-5-104 Host
We reserve all rights in this document and in the information contained therein.
Reproduction, use or disclosure to third parties without express authority is strictly
forbidden.
CONTENTS ...............................................................................................V
ABBREVIATIONS....................................................................................VII
INTRODUCTION.......................................................................................IX
Preface ix
References.................................................................................................................. ix
Conventions ................................................................................................................ ix
2 LINK LAYER....................................................................................2-1
2.1 General.........................................................................................................2-1
2.2 Verification mode of command age .............................................................2-3
2.3 Multi-Host Connection..................................................................................2-3
2.3.1 Configuration with one Ethernet Interface .........................................2-3
2.3.2 Configuration with two Ethernet Interfaces........................................2-3
CS Control System
PB Peripheral Bus
Preface
This document describes the functions of the host interface in RTU560 according to
IEC 60870-5-104
References
[1] Telecontrol equipment and systems - Part 5-104
Transmission protocols -
Network access for IEC60870-5-101
using standard transport profiles Second edition 06-2006
Conventions
In this document function codes of data types according to IEC 60870-5-104 are marked
with angel brackets:
<Function code>
Italic fonts with the heading Parameter are references to configuration parameter in
RTUtil560. The parameter is followed by definitions in round brackets where to find this
parameter in RTUtil560.
Example:
In this document references to elements of the standard will be printed bold and in
brackets: [1, 7.4]
The tables in the next chapters include lists of the functions, options and message types
supported according to the protocol structure given in IEC 60870-5 (EPA three layer
model) for
The protocol IEC 60870-5-104 is running on the Ethernet-Interfaces of the CMU. For
more details see [2].
The IEC 60870-5-104 Host Interface Parameter have to be configured according to the
system requirements (see Table 1-1).
Option / Parameter Range of Values / Explanations Default
Host number 1 … 16 1
Buffer size for prio 1 data points 100 … 3 000 entries 500
Buffer size for prio 2 data points 100 … 3 000 entries 500
Buffer size for integrated totals 10 … 10 000 entries 1 000
Priority of ITI queue 1 or 2 2
Buffer size of spontaneous AMI 100 … 3 000 entries 500
Queue storage timeout Enable / Disable Enabled
If enabled: 120 min
If a host becomes offline, the queues will be
cleared after Queue storage timeout
(except the ITI queue)
Interlock with local control Enable / Disable Disabled
authority If enabled:
If the control authority is requested by the
Integrated HMI, commands are rejected from
this Host System
2.1 General
One or more Master IP Address is necessary, if more than one master station is
connected to the network. For more details see chapter 2.3.
If more than one host is connected to the same Ethernet interface (see chapter 2.3.1),
responses to the (redundant) hosts are sent with the same sequence number, if the
parameter ‘Send same sequence number’ is enabled.
The parameters in Table 2-1 have to be calculated regarding the real communication
technology. All parameter are preset to the default values from [1, 9.5].
The protocol IEC 60870-5-104 allows also commands with time stamp [ASDU 58 ...
64].The RTU560 can verify this time stamp, and rejects commands with ‘old’ time stamp.
For the verification a time window between 1 and 65535 seconds is used.
1st case: RTU560 is not time-synchronized: The time stamp of the command is not
verified
2nd case: RTU560 is time-synchronized: The time stamp is verified. The time difference
may not exceed ‘Max. accepted time window’.
2nd case: RTU560 is time-synchronized: The time stamp is verified. The time difference
may not exceed ‘Max. accepted time window’.
Up to 16 hosts (NCC) can be connected to one RTU560 system. In this case the RTU560
needs the IP addresses of the NCCs in order to distinguish the logical connections.
For this configuration two physical Ethernet interfaces are needed with separate IP
addresses. The two interfaces communicate with independent host lines. Dependant on
the used RTU560 hardware, the IP addresses of the links to the controlling station (NCC)
have to be in different subnets or not.
Overview on type identifications for data elements of the application layer defined in [1].
The column RTU560 Type shows the type of data with must be configured in RTUtil560.
ASDUs Description Function RTU560
Code Types
M_SP_NA_1 Single-point information 1 SPI
M_SP_TB_1 Single-point information with time tag CP56Time2a 30 SPI
M_DP_NA_1 Double-Point information 3 DPI
M_DP_TB_1 Double-Point information with time tag CP56Time2a 31 DPI
M_ST_NA_1 Step position information 5 STI
M_ST_TB_1 Step position information with time tag CP56Time2a 32 STI
M_BO_NA_1 Bitstring of 32 bit 7 BSI8/16/32
M_BO_TB_1 Bitstring of 32 bit with time tag CP56Time2a 33 BSI8/16/32
M_ME_NA_1 Measured value, normalized value 9 AMI
DMI8/16
M_ME_TD_1 Measured value, normalized value with time tag 34 AMI
CP56Time2a DMI8/16
M_ME_NB_1 Measured value, scaled value 11 AMI
M_ME_TE_1 Measured value, scaled value with time tag 35 AMI
CP56Time2a
M_ME_NC_1 Measured value, short floating point 13 MFI
M_ME_TF_1 Measured value, short floating point value with time 36 MFI
tag CP56Time2a
M_IT_NA_1 Integrated totals 15 ITI
M_IT_TB_1 Integrated totals with time tag CP56Time2a 37 ITI
M_EP_TD_1 Event of protection equipment with time tag 38 EPI
CP56Time2a
If disabled:
Element is ignored and not processed by
HCI.
Parameter:
In Use (Protocol address and parameter)
(available for all configurable elements)
If enabled:
Transmission can be blocked in
monitoring direction.
This parameter is obsolete and replaced
by the parameter ‘In Use’, but still
included for compatibility reasons.
Parameter:
Filter (Protocol address and parameter)
(available for all configurable data points
in monitoring direction)
Parameter:
Group number
(Protocol address and parameter)
(available for all configurable data points
in monitoring direction)
Selection according to [1]. The address fields have the following size:
The highest possible address value (65535) is reserved for broadcast calls in control
direction and therefore must not be used as station address.
Conversion of value
RTU560 internal communication Protocol specific
off 0
on 1
Conversion of value
RTU560 internal communication Protocol specific
intermediate 0
off 1
on 2
indeterminate 3
Binary process information indicated by two bits and relative time-tag (used by protection
relays).
Supported M_EP_TD_1 <38> with timestamp CP56Time2a
Data Types Parameter:
Transmit with timestamp (EPI- Protocol Address and Parameter)
Additional The EPI contents a elapsed time tag of the protection event with the range
of 0 ... 59999 m sec.
Conversion of value
RTU560 internal communication Protocol specific
intermediate 0
off 1
on 2
indeterminate 3
Conversion of value
RTU560 internal communication Protocol specific
Range min. -63 -63
... ...
Range max. +63 +63
Conversion of value
RTU560 internal communication Protocol specific
Range min. 0 0
... ...
BSI8: Bit mask of 8 bit; 255
range ... 255
BSI16: Bit mask of 16 bit;
Range max. 65.535
range ... 65.535
BSI32: Bit mask of 32 bit;
4.294.967.295
range ... 4.294.967.295
Conversion of value
RTU560 internal communication Protocol specific
Range min. 0 0
... ... …
Range max. 2.147.483.647 2.147.483.647
Binary process information indicated by 8 or 16 bit used as a measured value from digital
inputs in normalized format.
Supported M_ME_NA_1 <9> without timestamp
Data Types Parameter:
Transmit with timestamp (DMI- Protocol Address and Parameter)
Conversion of value
RTU560 internal communication Protocol specific
Range min. -100% -1
... ...
Range max. +100% +1-2-15
Analog process information used as a measured value from analog inputs in normalized
or scaled format.
Supported M_ME_NA_1 <9> normalized without timestamp
Data Types Parameter:
Transmit with timestamp (AMI- Protocol Address and Parameter)
Transmission format (AMI- Protocol Address and Parameter)
Background cycle
If the parameter background cycle is set the concerning AMI is send to
the NCC with the actual value after the configured time period only.
Parameter:
Background cycle (AMI- Protocol Address and Parameter)
It is possible to set both parameter at the same AMI. That means that the
concerning AMI is directly send to the NCC on every change and
additional after the configured time period.
Maximum Value:
+100% within the internal communication will be converted to `Maximum
Value´ in the external communication protocol.
Parameter:
Maximum Value (AMI – Protocol Address and Parameter)
Minimum Value:
-100% within the internal communication will be converted to `Minimum
Value´ in the external communication protocol.
Parameter:
Minimum Value (AMI- Protocol Address and Parameter)
Conversion of value
RTU560 internal communication Protocol specific
Normalized : -1
Range min. -100%
Scaled : -32.768
... ...
-15
Normalized : +1-2
Range max. +100%
Scaled : +32.767
Measured Value,
+ Range
External Protocol
2047
(Max. Value)
Value on internal
communication
- 100 % + 100 %
Example:
Maximum Value = 2047
- 2048
(Min. Value)
Analog process information indicated by 32 bit used as a measured value from analog
inputs in float format.
Supported M_ME_NC_1 <13> without timestamp
Data Types Parameter:
Transmit with timestamp (MFI- Protocol Address and Parameter)
Background cycle
If the parameter background cycle is set the concerning MFI is send to the
NCC after the configured time period only.
Parameter:
Background cycle (MFI- Protocol Address and Parameter)
It is possible to set both parameter at the same MFI. That means that the
concerning MFI is directly send to the NCC on every change and
additional after the configured time period
Conversion of value
RTU560 internal communication Protocol specific
Range min. -3.41038 -3.41038
...
Range max. + 3.41038 + 3.41038
Conversion of value
RTU560 internal communication Protocol specific
off 0
on 1
Conversion of value
RTU560 internal communication Protocol specific
off 1
on 2
Conversion of value
RTU560 internal communication Protocol specific
Lower 1
Higher 2
Conversion of value
RTU560 internal communication Protocol specific
Normalized : -1
Range min. -100%
Scaled : -32.768
... ...
-15
Normalized : +1-2
Range max. +100%
Scaled : +32.767
Conversion of value
RTU560 internal communication Protocol specific
Range min. -100% -1
... ...
Range max. +100% +1-2-15
Floating point process command (32 bit short floating point number)
Supported C_SE_NC_1 <50>
Data Types C_SE_TC_1 <63> with timestamp CP56Time2a
Command See also parameter ‘Interlock with local control authority’
Authority (Table 1-1: Interface Parameter
Additional
Conversion of value
RTU560 internal communication Protocol specific
Range min. - 3.41038 - 3.41038
... ...
Range max. + 3.41038 + 3.41038
Conversion of value
RTU560 internal communication Protocol specific
Range min. 0 0
... ...
Range max. 4.294.967.295 4.294.967.295
Several type identifications of the private range have been selected to enable transparent
data transfer through the RTU560.
With the “Transparent Data Message C_TD_NA_1” the Controlling Station is able to
request data from the Remote Terminal Unit.
The Type Ident is 145, ASDU address and the Information object address must be
configured by RTUtil560.
When the message is accepted by the RTU (message can be processed by the RTU and
device answers to the request message), the RTU sends a “positive confirmation”
ACTCON, otherwise (message cannot be processed by the RTU) the RTU sends a
“negative confirmation” ACTCON.
The data bytes are extracted and transmitted, but not interpreted or modified by RTU560.
The user has to take care about the data. For further information about the format of the
user data please refer to the corresponding subdevice communication interface
description.
Every transparent data command is checked on link address, ASDU address, information
object address and “No of Data Bytes in Current Segment“.
If the ASDU address or information object address doesn’t match to the configuration in
RTUtil560 or the “No of Data Bytes in Current Segment” is higher than 200, the command
is confirmed negative.
With the “Transparent Data Response M_TD_NA_1”, the RTU is able to transmit any
data as transparent data to a Controlling Station.
The Type Ident is 146, ASDU address and the Information object address must be
configured by RTUtil560. They are equal to the one used in command direction.
The maximum amount of segments is 255, each of them contains up to 200 data bytes.
If all data can be sent in one message (data segmentation not necessary), the contents
of both segmentation control fields are set to 1.
Controlling
RTU560
station
Transparent data C_TD_NA_1.act
channel command - RTU checks, if
activation corresponding
command is possible
Transparent data to transmit.
C_TD_NA_1.act_con P/N
channel command -
activation
User data will be send
to target, reply(s) will
be send as answer
with
COF = REQUESTED
Transparent data
M_TD_NA_1.requested (segment 1)
channel information –
Requested
. If reply is larger than
. max. User data size
in M_TD_NA_1, user
. data will be
Transparent data segmented in
M_TD_NA_1.requested (segment n)
channel information – several telegrams.
Requested
7.2.1 General
With the “Transparent Data Message C_SB_NA_1” the Controlling Station is able to
request data and execute commands of a SPAbus device connected to a RTU560.
The Type Ident is 133, the ASDU address and the Information object address must be
configured by RTUtil560.
The “Transparent Data Message C_SB_NA_1” will be answered from RTU by sending
the message back to Central System with Cause of Transmission 7 (Activation
confirmation).
When the message is accepted by the RTU560 (message can be processed by the RTU
and device answers to the request message), the RTU sends a “positive confirmation”
ACTCON with the reply data included, otherwise (message cannot be processed by the
RTU) the RTU sends a “negative confirmation” ACTCON.
Every transparent data command is checked on link address, ASDU address, information
object address and “No of Data Bytes in Current Segment“.
If the ASDU address, information object address or “No of Data Bytes” doesn’t match to
the configuration in RTUtil560, the command is confirmed negative.
Controlling
RTU560
station
Encapsulated C_SB_NA_1.act
SPAbus command - RTU checks, if
activation corresponding
command is possible
to transmit.
User data will be
send to target, reply
will be send as
Encapsulated
SPAbus command – activation
C_SB_NA_1.act_con P/N
activation confirmation
fi ti
The file transfer is used for exchanging files between a control center and a RTU560 or a
subordinated device.
Before starting file transfer to an RTU, the control center can deactivate the RTU (stop
periodic measurements), in order to have highest possible bandwidth for the file transfer.
If no new configuration files are loaded into the RTU between deactivation and reset
command, the RTU restarts with the same configuration data as before.
If a file transfer is started without preceding deactivation command, the RTU will continue
its normal operation during the complete file transfer process. The downloaded
configuration will become active only after a restart of the RTU.
The file name in the protocol is fixed for all supported file types to 1 (transparent file).
Supported file types
GCD-configuration file
IOD-configuration file
OAD-configuration file
PTX-configuration file
PRO-configuration file (PLC boot project file)
Disturbance recorder of various protocols and device types. See corresponding SCI
description for details.
UNDEF-file not specified in greater detail
8.1 Download
The download of configuration files does not trigger any restarting mechanism in the
RTU560. For activating the new configuration file, the control center has to issue a Reset
Process Command (C_RP_NA_1, TI 105) after writing the files to the RTU560.
The IOD- and GCD-configuration files are distributed to every CMU board in the system
concerned after download is completed. Configuration file distribution will only be done, if
the file belongs to the RTU560 itself. Otherwise the file transfer will only be routed to the
subordinated device it belongs to. In this case the file transfer handling is done by the
subordinated device (e.g. a RTU560).
PTX- and PRO-configuration files are only stored local these download is completed.
This means, that archive or PLC functions using this configuration files have to be located
on the same CMU-board where the host communication interface handling the file
transfer is located.
The distribution is done between the message F_LS_NA_1 and the message
F_AF_NA_1 and may last a couple of seconds.
The message F_AF_NA_1 is only acknowledged positively when file transfer and file
distribution were successful. If a file transfer to a RTU560 is confirmed negatively the
downloaded file was not stored and the previous file is not deleted or overwritten.
8.2 Upload
All supported file types can also be uploaded from a RTU560 or subordinated devices.
The general interrogation includes single point information, double point information, step
positions, measured values, bitstrings and RTU system events, whereas integrated totals
are excluded. The interrogation of a selected part of the process information by a group
interrogation is supported. The process values transmitted in the course of the
interrogation are marked with the cause of transmission 20 (General Interrogation) or 21
to 36.
When events occur during a running general interrogation, they are sent spontaneous
within the general interrogation.
A General Interrogation (with QOI=20) can be generated also by the Function Block
GI_OUT of a PLC program. All process data points will be transmitted to the NCC with
COT=20.
Only counter data from the local PDP is readable. The counter
interrogation command for subordinated devices is not supported.
The eight time masters have their own priority. If a higher prior master will fail, the time
master with the lower priority will synchronize the RTU560. If the higher prior master is
available again, he will continue synchronizing.
Parameter loading is used to change parameters of measured values, which are locally
connected to the analog input boards of the RTU560. A routing to subordinated devices
is not supported by RTU560.
The host interface manages internal status messages of the RTU560. These status
messages can be created from the host itself or other activities of the RTU560. The
system events of other activities are sent via internal communication and are processed
by the HCI. The system events of a RTU are sent as SPI messages through the IEC 870-
5-104 protocol. Therefore an own information object address is needed.
This information address is the address for the system event. System events are sent
spontaneous as SPI with or without timestamp:
Description of system event Address
At least one indication faulty #016
At least one analog value faulty #017
At least one digital value faulty #018
At least one pulse counter value faulty #019
At least one command is faulty #020
At least one setpoint command is faulty #021
At least one digital output is faulty #022
RTU is faulty #023
RTU is active #024
RTU is synchronized #025
External clock is inoperable #026
Local printer is offline #027
At least one indication oscillating #028
System battery low (RTU560E only) #029
AC power supply failed (RTU560E only) #030
At least one DCE faulty #044
Device connected #045
At least one PLC function not running #046
At least one PLC function cycle time exceeded #047
RTU is inoperable #048
RTU is out of service #049
Power supply failure in communication sub rack (CSR) #059
Command supervision circuit z disconnected or faulty, 1 ≤ z ≤ 32 #064 ... #095
SNTP client 1 is synchronized #096
SNTP client 2 is synchronized #097
Local control authority active #100
Host x is Online, 1 ≤ x ≤ 16 #101 ... #116
Host interface x: At least one change of information lost, 1 ≤ x ≤ 16 #117 … #132
Host Interface x: At least one pulse counter lost, 1 ≤ x ≤ 16 #133 … #148
CMU in rack 0, slot x is inoperable, 1 ≤ x ≤ 8 #149 … #156
CMU in rack 1, slot x is inoperable, 1 ≤ x ≤ 8 #157 … #164
CMU in rack 1, slot 10 is inoperable (23ET24S only) #166
Device reachable on redundant line x, 1 ≤ x ≤ 4 #180 … #183
Device active on redundant line x, 1 ≤ x ≤ 4 #184 … #187
Device preferred on redundant line x, 1 ≤ x ≤ 4 #188 … #191
Network element x is operable, 1 ≤ x ≤ 32 #192 … #223
CMU in rack 0, slot x is active, 1 ≤ x ≤ 8 #224 … #231
CMU in rack 1, slot x is active, 1 ≤ x ≤ 8 #232 … #239
CMU in rack 1, slot 10 is active (23ET24 only) #240
Process command collision with host X, 1 ≤ x ≤ 16 #242-#257
Process command collision with Integrated HMI #258
Process command collision with webserver #259
Process command collision with PLC #260
System event which are not sent spontaneous but send in a general interrogation with
timestamp:
Description of system event Address
Database identity tag #174
System Single Commands (SSC) are accepted by the host communication interface with
protocol IEC 60870-5-104 and routed to the subdevice communication interfaces.
A black check box indicates that the option cannot be selected in this companion standard.
System definition
Point-to-point Multipoint-partyline
Two octets
Frame length
Structured
When using an unbalanced link layer, the following ASDU types are returned in class 2 messages
(low priority) with the indicated causes of transmission:
Cause of transmission
(system-specific parameter)
Length of APDU
(system-specific parameter)
The maximum length of APDU for both directions is 253. It is a fixed system parameter.
<18> := Packed start events of protection equipment with time tag M_EP_TB_1
<19> := Packed output circuit information of protection equipment with time tag M EP TC 1
X <34> := Measured value, normalized value with time tag CP56Time2a M_ME_TD_1
X <35> := Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
X <36> := Measured value, short floating point value with time tag CP56Time2a M_ME_TF_1
<39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1
<40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1
In this companion standard only the use of the set <30> – <40> for ASDUs with time tag is permitted.
X <61> := Set point command, normalized value with time tag CP56Time2a C_SE_TA_1
X <62> := Set point command, scaled value with time tag CP56Time2a C_SE_TB_1
<63> := Set point command, short floating point value with time tag CP56Time2a C_SE_TC_1
X
X <64> := Bitstring of 32 bit with time tag CP56Time2a C_BO_TA_1
Either the ASDUs of the set <45> – <51> or of the set <58> – <64> are used.
File transfer
(station-specific parameter)
<2> M_SP_TA_1
<3> M_DP_NA_1 X X X X
<4> M_DP_TA_1
<5> M_ST_NA_1 X X X X
<6> M_ST_TA_1
<7> M_BO_NA_1 X X X X
<8> M_BO_TA_1
<9> M_ME_NA_1 X X X X X
<10> M_ME_TA_1
<11> M_ME_NB_1 X X X X X
<12> M_ME_TB_1
<13> M_ME_NC_1 X X X X X
<14> M_ME_TC_1
<15> M_IT_NA_1 X X X
<16> M_IT_TA_1
<17> M_EP_TA_1
(X) Functionality ‘Local’ or ‘Remote’ can be assigned by PLC
<31> M_DP_TB_1 X X
<32> M_ST_TB_1 X X
<33> M_BO_TB_1 X X
<34> M_ME_TD_1 X X
<35> M_ME_TE_1 X X
<36> M_ME_TF_1 X X
<37> M_IT_TB_1 X X X
<38> M_EP_TD_1 X
<39> M_EP_TE_1
<40> M_EP_TF_1
<45> C_SC_NA_1 X X X X X X X X
<46> C_DC_NA_1 X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1 X X X X X X
<58> C_SC_TA_1 X X X X X X X X
<59> C_DC_TA_1 X X X X X X X X
<60> C_RC_TA_1 X X X X X X X X
<61> C_SE_TA_1 X X X X X X X X
<62> C_SE_TB_1 X X X X X X X X
<63> C_SE_TC_1 X X X X X X X X
<64> C_BO_TA_1 X X X X X X
<70> M_EI_NA_1* X
<100> C_IC_NA_1 X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X X X X
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1
<105> C_RP_NA_1 X X X X X
<106> C_CD_NA_1
<107> C_TS_TA_1 X X X X X
<110> P_ME_NA_1 X X X X X
<111> P_ME_NB_1 X X X X X
<112> P_ME_NC_1 X
<113> P_AC_NA_1 X
<120> F_FR_NA_1 X X X X
<121> F_SR_NA_1 X X X X
<122> F_SC_NA_1 X X X X X
<123> F_LS_NA_1 X X X X
<124> F_AF_NA_1 X X X X
<125> F_SG_NA_1 X X X X
<126> F_DR_TA_1* X X
<127> F_SC_NB_1* X
* Blank or X only
Station initialization
station-specific parameter)
X Remote initialization
Read procedure
(station-specific parameter)
X Read procedure
Spontaneous transmission
(station-specific parameter)
X Spontaneous transmission
The following type identifications may be transmitted in succession caused by a single status change
of an information object. The particular information object addresses for which double transmission is
enabled are defined in a project-specific list.
Station interrogation
(station-specific parameter)
X global
X group 1 X group 7 X group 13
X group 2 X group 8 X group 14
X group 3 X group 9 X group 15
X group 4 X group 10 X group 16
X group 5 X group 11
Information object addresses assigned to each
X group 6 X group 12 group must be shown in a separate table.
Clock synchronization
(station-specific parameter)
X Clock synchronization
Command transmission
(object-specific parameter)
X No additional definition
Short-pulse duration (duration determined by a system parameter in the outstation)
Long-pulse duration (duration determined by a system parameter in the outstation)
X Persistent output
X Supervision of maximum delay in command direction of commands and set point commands
65535 sec Maximum allowable delay of commands and set point commands
X Counter read
X Counter freeze without reset
X Counter freeze with reset
Counter reset
Parameter loading
(object-specific parameter)
X Threshold value
X Smoothing factor
Low limit for transmission of measured values
High limit for transmission of measured values
Parameter activation
(object-specific parameter)
Test procedure
(station-specific parameter)
X Test procedure
File transfer
(station-specific parameter)
File transfer in monitor direction
X Transparent file
X Transmission of disturbance data of protection equipment
Transmission of sequences of events
X Transparent file
Background scan
station-specific parameter)
X Background scan
Maximum number of outstanding I format APDUs k and latest acknowledge APDUs (w)
Portnumber
Redundant connections
X
Ethernet 802.3