Professional Documents
Culture Documents
NR, the NR logo are either registered trademarks or trademarks of NR Electric Co., Ltd. No NR
trademarks may be used without written permission. NR products appearing in this document may
be covered by P.R. China and foreign patents. NR Electric Co., Ltd. reserves all rights and benefits
afforded under P.R. China and international copyright and patent laws in its products, including but
not limited to software, firmware and documentation. NR Engineering Co., Ltd. is licensed to use
this document as well as all intellectual property rights owned or held by NR Electric Co., Ltd,
including but not limited to copyright, rights in inventions, patents, know-how, trade secrets,
trademarks and trade names, service marks, design rights, database rights and rights in data,
utility models, domain names and all similar rights.
The information in this document is provided for informational use only and does not constitute a
legal contract between NR and any person or entity unless otherwise specified. Information in this
document is subject to change without prior notice.
To the extent required the products described herein meet applicable IEC and IEEE standards, but
no such assurance is given with respect to local codes and ordinances because they vary greatly.
Although every reasonable effort is made to present current and accurate information, this
document does not purport to cover all details or variations in equipment nor provide for every
possible contingency to be met in connection with installation, operation, or maintenance. Should
further information be desired or should particular problems arise which are not covered
sufficiently for your purposes, please do not hesitate to contact us.
Preface
Preface
About This Document
This manual describes the network structures and the communication protocols supported by the
device.
To start using this manual, user should have a basic knowledge of communication in substation
automation system (SAS) and of the specific communication protocols along with the basic
operation methods of the PCS-Studio configuration tool for PCS S series IEDs.
Safety Information
This manual is not a complete index of all safety measures required for operation of the equipment
(module or device). However, it comprises important information that must be followed for
personal safety, as well as to avoid material damage. Information is highlighted and illustrated as
follows according to the degree of danger:
Indicates that property damage can result if the measures specified are not
taken.
Contact with instrument terminals can cause electrical shock that can result
in injury or death.
Use of this equipment in a manner other than specified in this manual can
impair operator safety safeguards provided by this equipment.
Have ONLY qualified personnel service this equipment. If you are not
qualified to service this equipment, you can injure yourself or others, or
cause equipment damage.
DO NOT connect power to the device until you have completed these
procedures and receive instruction to apply power. Equipment damage can
result otherwise.
Document Conventions
⚫ Menu path is connected with the right arrow "→" and bold.
For example: the access path of protection settings is: Main Menu → Settings → Protection
Settings.
⚫ Settings out of list should be placed in brackets.
For example: the system setting [Opt_SysFreq]
⚫ Cross-references are presented in italics.
For example: refer to Figure 1.1-1, refer to Table 1.1-1, reference to Section 1.1
⚫ Binary input signals, binary output signals, analogue quantities, LED lights, buttons, and other
fixed meanings, should be written in double quotes and bold.
For example: press the "ENT" button.
Warranty
This product is covered by the standard NR 10-year warranty. For warranty details, please consult
the manufacturer or agent for warranty information.
Document Structure
This manual is a comprehensive work covering all aspects of device communication interfaces
and protocols. Read the sections that pertain to your application to gain valuable information about
communication the device. To concentrate on the target sections of this manual as your job needs
and responsibilities dictate. An overview of each manual section and section topics follows.
1 Communication Modules
2 IEC 61850
Instantiation application of communication between the client and the server for substation
automation via the IEC 61850 Manufacturing Message Specification (MMS) protocol, cross
communication between devices via Generic Object-Oriented Substation Event (GOOSE)
messages and IEC 61850-9-2 SV implementation.
3 DNP3
Instruction of DNP3 protocol characteristics and properties, especially the application layer
with implementation information.
4 IEC 60870-5-103
5 Modbus
ANNEX A PICS
ANNEX B MICS
ANNEX C TICS
ANNEX D PIXIT
Version
Release Date Description of change
Document Firmware
1 Communication Modules 1
Table of Contents
This section outlines the communication modules of device. This device supports a choice of
multiple protocols via rear interfaces on communication modules. The protocols are selected and 1
configured by setting or configuration file via the configuration tool PCS-Studio.
It should be noted that the description contained within this manual do not aim to fully detail
protocols. The relevant documentation for protocols should be referred to for such goal. This
manual serves to describe the specific implementation of protocols in this device.
The NR6106 CPU module can be installed on device rack. The sub-models of this module
correspond to different communication interfaces or device variants.
3. Serial interfaces: 10-terminal connector, 2*EIA-485 ports and 1*EIA-485/TTL port for clock
synchronization
Debugging interface
Serial Interfaces
Communication interface
Physical Connection
1 × EIA-485, 3-terminal ●
1 × EIA-232/485, 3-terminal ●
1 × EIA-485/TTL, 4-terminal ●
1 × RS-232, RJ45 ●
Application
IEC 61850-9-2LE SV ● ●
IEC 60870-5-103 ● ● ●
DNP3 ● ●
Modbus ● ● ●
Printer, serial ●
Debugging interface
Serial Interfaces
Communication interface
Debugging ●
Port bonding ● ●
Devices are integrated into superior network structures via switches. Each switch provides several
interfaces to connect to devices and other switches in the superior network. The superior network
operates on the basis of RSTP (Rapid Spanning Tree Protocol) which leads to a network or a ring
of such network switches. This results in a variety of possible structures of superior network.
WLAN
Remote
Monitoring
Substation LAN
IEDs
Access path: Main Menu Settings Global Settings Comm Settings General Comm
Settings
Normal;
1-2:Normal,
3-4:HSR; The networking method of
14 B01.Opt_NetMode Normal 1-2:Normal, - - the CPU module located in
3-4:PRP; slot No.1
1-2:Normal,
3-4:RSTP;
Ensure that the device and PC are in the same network segment by setting the IP address
[IP_LAN*] and subnet mask [Mask_LAN*] of corresponding Ethernet interfaces.
1
LAN1
LAN2
LAN3
LAN4
For example, to establish a connection between PC and the device first Ethernet interface, set the
IP address and subnet mask of PC to be “198.87.96.102” and “255.255.255.0”.The IP address and
subnet mask of device should be [IP_LAN1]= 198.87.96.*** (** can be any integer from 1 to 254
except 102 or any other appeared number), [Mask_LAN1]=255.255.255.0.
For redundancy or increased throughput of the communication, dual network structure may be
adopted along with channel bonding technology. These two bonded interfaces, who share the
identical IP address and MAC address, work in Active-Standby mode. If the link via active interface
fails, the link via original standby interface will be activated automatically to ensure a reliable
communication. 1
The value of this setting represents a 4-bits binary number. Each bit represents a corresponding
Ethernet port's bonding status. Use the following map to decide the specific setting value.
Additionally, the default value "0" means the channel bonding function is deactivated.
Ethernet port 1
Port 4 Port 3 Port 2 Port 1 Setting Port 4 Port 3 Port 2 Port 1 Setting
Binary Bonding Bonding Binary
Bit 3 Bit 2 Bit 1 Bit 0 Value Bit 3 Bit 2 Bit 1 Bit 0 Value
0 0 1 1 0011 3 1 0 0 1 1001 9
Ethernet port 2
Port 4 Port 3 Port 2 Port 1 Setting Port 4 Port 3 Port 2 Port 1 Setting
Binary Bonding Bonding Binary
Bit 3 Bit 2 Bit 1 Bit 0 Value Bit 3 Bit 2 Bit 1 Bit 0 Value
0 1 0 1 0101 5 0 1 1 0 0110 6
Ethernet port 3
Port 4 Port 3 Port 2 Port 1 Setting Port 4 Port 3 Port 2 Port 1 Setting
Binary Bonding Bonding Binary
Bit 3 Bit 2 Bit 1 Bit 0 Value Bit 3 Bit 2 Bit 1 Bit 0 Value
1 0 1 0 1010 10 1 1 0 0 1100 12
Ethernet port 4
CPU Module
Take the device Ethernet ports 1 & 2 for example and assume that P1 is connected to NET1 while
P2 is connected to NET2.
⚫ After the device is powered on, only P1 is activated when both NET1 and NET2 are normal.
⚫ If NET1 is abnormal, P2 cannot be activated if NET2 is also abnormal. The device will keep
trying on P1.
⚫ If P2 is working, the device will maintain this state even if NET1 has been restored to normal.
It will be switched to P1 only if NET2 is abnormal.
1.3.5 Star-shaped
Set [B01.Opt_NetMode] to be "Normal" to activate this structure.
Only one interface of the device is connected to switch. Multiple devices are connected to the switch in
a star-shaped connection.
1 Switch1 Switch2
Substation LAN
IEDs
According to IEC 62439-3, the PRP (Parallel Redundancy Protocol) provides communication over
two independent networks simultaneously. If there is an interruption in communication on either
network A or network B, the data exchange continues without problems on the other network.
Thus, it assures that there is no interruption. It is recommended to use a non-PRP device, such as
debugging PC, with a Redundancy Box (RedBox) in a PRP network.
The PRP nodes connect to two independent networks, and send two copies of the same packet to
both networks. Both networks transmit these messages to receiving nodes, while receiving nodes
accept the first packet and discard the second. The receiving nodes make a redundant handling at
data link layer to realize redundant message receiving and then transmit data to application layer.
Switch1 Switch2 1
Substation LAN Substation LAN
IEDs
Each node has two interfaces that operate in parallel and that are attached to the same upper
layers of the communication stack through the Link Redundancy Entity (LRE). For the basic
communication, the LRE presents toward its upper layers the same interface as a non-redundant
network adapter, so the upper layers are unaware of redundancy.
When receiving a frame from the node’s upper layers, the LRE appends to the frame a
Redundancy Check Trailer (RCT) containing a sequence number and sends the frame through
both its ports at nearly the same time. The two frames are nearly identical except for the LAN
identifier (and the checksum).
When receiving frames from the network, the LRE forwards the first received frame of a pair to its
node’s upper layers and discards the duplicate frame (if it arrives). It removes the RCT if required.
This general PRP operating mode does not apply to PTP frames, since the delay suffered by a
frame is not the same in the two LANs and some frames are modified in the TCs Since the RCT of
PRP cannot be relied upon for PTP messages. As ordinary clocks don't perform duplicate discard
on them and consider the two ports as independent.
The device will automatically check whether its setting value of PRP networking mode matches
the actual network networking mode. If it does not match, the device will issue the
"Alm_NetMode_Unmatched" alarm. If there is such alarm, please check the [B01.Opt_NetMode]
setting value.
DANP 1 DANP 2
1 UDP TCP UDP TCP
upper layer hard real-time hard real-time
stack stack
network layer network layer
same data
link layer Link Redundancy Entity Link Redundancy Entity
interface
transceivers
LAN A
LAN B
According to IEC 62439-3, devices operate in hand-in-hand mode in the HSR (High Availability
Seamless Redundancy Protocol) structure to form rings with switches. If an interruption in
communication occurs in a network, a seamless switchover takes place. It is recommended to use
a non-HSR device, such as debugging PC, with a Redundancy Box (RedBox) in an HSR network.
HSR nodes send a copy of data to application layer. The data is copied at data link layer and is
transmitted from Port A and Port B via different physical link.
HSR ring transmission through two-way link ensures the redundancy of data. When a link fails, a
message can be transmitted to the receiving device from another loop, and there is no network
reconstruction time. There is no switching network, and forwarding through the device. However,
forwarding device has a forwarding delay time per level, so the total forwarding delay is great.
This operating mode does not apply to PTP frames, since the delay suffered by a frame is not the
same going clockwise or counter-clockwise in the ring. A DANH (Doubly Attached Node
implementing HSR) does not receive the same message from both ports since some messages
are modified by intermediate nodes.
Switch1 Switch2 1
HSR
Substation LAN Substation LAN
IEDs
Each HSR node has two interfaces arranged in a ring. Source nodes send packets over both
interfaces. Each node transmits unreceived frames from interface A to interface B and vice versa.
The source node removes frames it receives that it injected into the ring.
Each HSR node receives two copies of the same packet, and accepts the first packet and discards
the second. The accepted packet is transmitted to application layer.
For P2P messages (e.g. TCP messages), receiving node will stop transmitting after receiving the
message. For multicast or broadcast message, if the message comes from itself, receiving node
will stop transmitting after receiving the message. If the message comes from other nodes,
receiving node will transmit it to another interface after receiving the message, i.e., receiving
message from interface A and transmitting message to interface B.
The device will automatically check whether its setting value of PRP networking mode matches
the actual network networking mode. If it does not match, the device will issue the
"Alm_NetMode_Unmatched" alarm. If there is such alarm, please check the [B01.Opt_NetMode]
setting value.
requirements of HSR.
1
1.3.8 RSTP Ring Structure
Set [B01.Opt_NetMode] to be "1-2: Normal, 3-4: RSTP" to activate this structure with the device No.3
& 4 Ethernet interfaces.
Devices participate in a ring structure via two interfaces. Data is transmitted one by one in the ring
until it reaches its intended destination. If the ring structure breaks at a point, stars show up upon
the switch quantity. Thanks to RSTP mechanism, the communication may function continuously
without interruption. However, a second fault in one star cannot be ignored.
Switch1
RSTP Ring
IEDs
Access path: Main Menu Settings Global Settings Comm Settings General Comm
Settings
1
No. Setting Default Range Step Unit Remark
4800
9600
19200
1 Baud_Printer 19200 - bps Baud rate of printer port
38400
57600
115200
4800
9600
19200
4 Baud_RS485-1 19200 - bps Baud rate of rear RS-485 serial port 1.
38400
57600
115200
4800
9600
19200
5 Baud_RS485-2 19200 - bps Baud rate of rear RS-485 serial port 2.
38400
57600
115200
01 A
EIA-485 02 B
03 SGND
04 A
EIA-485 05 B
06 SGND
07 SYN+
EIA-485 08 SYN-
09 SGND
SYN-
TTL 10
TTL
The EIA-485 bus must have 120Ω (Ohm) ½ Watt terminating resistors fitted at either end across
the signal wires. Some devices may be able to provide the bus terminating resistors by different
connection or configuration arrangements, in which case separate external components will not be
required. However, this device does not provide such facility. If it is located at the bus terminus, an
external termination resistor will be required.
Master 120Ohm
120Ohm
The EIA-485 standard requires that each device is directly connected to the physical cable, i.e. the
communication bus. Stub and tee are expressly forbidden, such as star topology. Loop bus
topology is not part of the EIA-485 standard and is forbidden.
Two-core screened cable is recommended. The specification of the cable will be dependent on the
application, although a multi-strand 0.5mm2 per core is normally adequate. Total cable length must 1
not exceed 500m. The screen must be continuous and grounded at only one end (normally at the
master connection point). For both safety and noise reasons, it is important to avoid circulating
current, especially when the cable runs between buildings.
The signal grounding connection must have continuity for the benefit of all devices connected to
the bus. At no stage must it be connected to the cables screen or to the device chassis. This is for
both safety and noise reasons.
1.4.2.3 Biasing
It may also be necessary to bias the signal wires to prevent jabber. Jabber occurs when the signal
level has an indeterminate state because the bus is not being actively driven. This may occur
when all slaves are in receiving mode and the master is slow to turn from receiving mode to
transmitting mode. This may be because the master purposefully waits in receiving mode, or even
in a high impedance state, until it has something to transmit. Jabber causes the receiving device(s)
to miss the first bits of the first character in the packet, which results in rejecting message and no
consequential responding of slave. The symptoms of these are poor response time (due to retries),
increasing message errors, erratic communication and even a complete failure of communication.
Biasing requires that the signal wires be weakly pulled to a defined voltage level of approximate 1V.
There should only be one bias point on the bus, which is best situated at the master connection
point. The DC source used for the bias must be clean, otherwise noise will be injected. Note that
some devices may (optionally) be able to provide the bus bias, in which case external components
will not be required.
As the field voltage is much higher than that required, NR cannot assume
responsibility for any damage that may occur to a device connected to the
network as a result of incorrect application of this voltage.
Ensure that the field voltage is not being used for other purposes (i.e.
powering logic inputs) as this may cause noise to be passed to the
communication network.
2 IEC 61850
Table of Contents
2.12 Protocol Implementation eXtra Information for Testing (PIXIT) ............... 2-19
The IEC 61850 standard is the result of years of work by electric utilities and vendors of electronic
equipment to produce standardized communications systems. It is a series of standards
describing client/server and peer-to-peer communications, substation design and configuration,
testing, environmental and project standards. The complete set includes:
⚫ IEC 61850-5: Communications and requirements for functions and device models
⚫ IEC 61850-7-1: Basic communication structure for substation and feeder equipment–
Principles and models
⚫ IEC 61850-7-2: Basic communication structure for substation and feeder equipment - Abstract
communication service interface (ACSI)
⚫ IEC 61850-7-3: Basic communication structure for substation and feeder equipment–
Common data classes
⚫ IEC 61850-7-4: Basic communication structure for substation and feeder equipment–
Compatible logical node classes and data classes
⚫ IEC 61850-8-1: Specific Communication Service Mapping (SCSM) – Mappings to MMS (ISO
9506-1 and ISO 9506-2) and to ISO/IEC 8802-3
⚫ IEC 61850-9-1: Specific Communication Service Mapping (SCSM) – Sampled values over
serial unidirectional multidrop point to point link
⚫ IEC 61850-9-2: Specific Communication Service Mapping (SCSM) – Sampled values over
ISO/IEC 8802-3
These documents can be obtained from the IEC (https://www.iec.ch). It is strongly recommended
that all those involved with any IEC 61850 implementation obtain this document set.
2 Switch Electrical
or
Optical
Switch Optical
Merging Merging
Unit Unit
Electronic CB/DS
CT/VT
Use the "Edition" option to determine the IEC 61850 protocol edition through the path: Project
Name → Communication → IEC61850.
IEC61850 Settings & General Comm Settings – IP address, subnet mask and
Network
Net mode
Besides the general Ethernet network settings, such IP address, MAC address, the settings that
are relevant to this protocol are listed in the following table. Refer to the device technical manual
and setting guide for more detail about the parameterization, such as IED name, dual network
operation mode, etc.
Access path: Main Menu Settings Global Settings Comm Settings IEC61850
Settings
2
2.2 Communication Profiles
This device supports IEC 61850 server services over TCP/IP communication protocol stacks. The
TCP/IP profile requires the device to have an IP address to establish communications. These
addresses are located in the path: Main Menu → Settings→ Global Settings→ Comm Settings
→ General Comm Settings.
⚫ MMS protocol
IEC 61850 specifies the use of the Manufacturing Message Specification (MMS) at the upper
(application) layer for transfer of real-time data. This protocol has been in existence for a
number of years and provides a set of services suitable for the transfer of data within a
substation LAN environment. IEC 61850-7-2 abstract services and objects are mapped to
actual MMS protocol services in IEC 61850-8-1.
⚫ Client/server
⚫ Peer-to-peer
This mode fully conforms to IEC 61850 standard. The A and B ports of the device are independent
of each other and there is no redundancy. It is recommended to use this mode for interoperation.
When one of the networks fails, the other network port can still send the report normally without
delay. When the failed network is restored, the disconnected client will continue to receive the
report sent by the device after re-establishing the connection.
Thus, it realizes dual network redundancy communication through software. It is different from
hardware redundancy mode of PRP or HSR and does not belong to dual network redundancy
mode of IEC 61850 standard.
For a proper use of this mode, the IP address settings of clients need to follow the following
requirements: the IP addresses of the two clients that establish connection simultaneously through
the A and B ports belong to different subnets and the host addresses are the same. For example,
the IP address 198.120.0.198 and the subnet mask 255.255.0.0 of client A; the IP address
198.121.0.198 and the subnet mask 255.255.0.0 of client B.
messages, which will increase the network traffic between the device and
the client. It is NOT recommended when the number of clients is large or
interoperability is involved.
2 In this mode, the SCADA system or the gateway meeting the IP address conditions uses two
clients to connect the device through the A and B ports, among which only one port is in service at
a time, respectively. After one client enables the RCB instance, if the trigger condition of the RCB
is met, the device will send the report to the client that activates the RCB, while the other client
only maintains communication connection with the device and is in a standby state.
When there is a failure in the network forwarding report, the client in the standby state will reuse
the RCB of the previous report forwarding, and disable the RCB before enabling it. Thereafter, if
the trigger condition for RCB instance is satisfied, the device will send a report to the client that
re-enables the RCB. When the failed network is restored, the disconnected client re-establishes
the connection, does not need to operate the RCB, and becomes a standby client.
Thus, it realizes dual network redundant communication through software. The difference with
HotStdby is that at the same time, the device will only send the report to the client that enables the
RCB.
For a proper use of this mode, the IP address settings of clients need to follow the following
requirements: the IP addresses of the two clients that establish connection simultaneously through
the A and B ports belong to different subnets and the host addresses are the same. For example,
the IP address 198.120.0.198 and the subnet mask 255.255.0.0 of client A; the IP address
198.121.0.198 and the subnet mask 255.255.0.0 of client B.
Although this mode has certain redundancy effect, it does NOT fully comply
with IEC 61850 standard process and is NOT recommended.
Each IED represents one IEC 61850 physical device. The physical device contains one or more
logical device(s), and the logical device contains many logical nodes. The logical node LPHD
contains information about the IED physical device. The logical node LLN0 contains common
information about the IED logical device.
⚫ MMXU.MX.Hz: frequency
⚫ PTOC: Phase time overcurrent protection, neutral time overcurrent protection, earth fault time
overcurrent protection, negative-sequence time overcurrent protection, neutral directional
overcurrent protection, negative-sequence directional overcurrent protection, RMS
overcurrent protection, phase overcurrent SOTF protection, earth fault overcurrent SOTF
protection, broken conductor protection and arc flash protection
The protection elements listed above contain start (pickup) and operate flags, instead of any
element has its own start (pickup) flag separately, all the elements share a common start (pickup)
flags “PTRC.ST.Str.general”. The operate flag for PTOC1 is “PTOC1.ST.Op.general”. These flags
take their values from related module for the corresponding element. Similar to digital status
values, the protection trip information is reported via BRCB, and BRCB also locates in LLN0.
2 Logical node LLN0 is essential for an IEC 61850 based IED. This LN shall be used to address
common issues for Logical Devices. In this device, most of the public services, the common
settings, control values and some device-oriented data objects are available here. The public
services may be BRCB, URCB and GSE control blocks and similar global defines for the whole
device; the common settings include all the setting items of communication settings, system
settings and some of the setting items, which can be configured to 2 or more logical nodes. In
LLN0, the item Loc is a device control object, this Do item indicates the local operation for
complete logical device, when it is true, all the remote control commands to the IED will be blocked
and those commands make effective until the item Loc is changed to false. Besides the logical
nodes we described above, there are some other logical nodes below in the IEDs.
⚫ MMXU: This LN shall be used to acquire values from CTs and VTs and calculated
measurements such as RMS values for current and voltage or power flows out of the acquired
voltage and current samples. These values are normally used for operational purposes such
as power flow supervision and management, screen displays, state estimation, etc. The
requested accuracy for these functions has to be provided.
⚫ CILO: This LN shall be used to “enable” a switching operation if the interlocking conditions are
fulfilled. One instance per switching device is needed. At least all related switchgear positions
have to be subscribed. The interlocking algorithm is a local issue.
This LN is used for the interlocking function at station level and/or at bay level.
Interlocking may be totally centralized or totally decentralized. Since the interlocking rules are
basically the same on bay and station level and based on all related position indications, the
different interlocking LNs may be seen as instances of the same LN class Interlocking (IL).
⚫ MSQI: This LN is used for the sequences and imbalances, for example for stability purpose.
This LN is used to acquire values from CTs and VTs and to calculate the sequence values
and imbalances in a three/multi-phase power system.
⚫ LPHD: Physical device information, the logical node to model common issues for physical
device.
⚫ CSWI: Switch controller. This class is used to control all switching conditions of XCBR and
XSWI: A remote switching command (for example Select-Before-Operate) arrives here firstly.
⚫ XCBR: Breaker control. The XCBR logical node is directly associated with the breaker control
feature.
⚫ RDIR: The settings of the direction element and the output of the forward and reverse
direction element.
⚫ RSYN: The settings and the output of the synchronism check element
⚫ RDRE: Indicates that the fault information record is completed and the sequence number of
the fault
2.5.1 Timestamps
The Universal Time Coordinated (abbreviated as UTC) timestamp associated with all IEC61850
data items represents the latest change time of either the value or the quality flags of the data
item.
Complete names are of the form xxxxxxPTOC1, where the xxxxxx character string is configurable.
Details regarding the logical node naming rules are given in IEC61850 parts 6 and 7-2. It is
recommended that a consistent naming convention be used for an entire substation project.
2.5.3 Reporting
IEC 61850 buffered and unbuffered reporting control blocks locate in LLN0, they can be
configured to transmit information of protection trip information (in the Protection logical nodes),
binary status values (in GGIO) and analog measured/calculated values (in MMXU, MMTR and
MSQI). The reporting control blocks can be configured in CID files, and then be sent to the IED via
an IEC61850 client. The following items can be configured.
Bit 1: Data-change
Bit 4: Integrity
Bit 2: Report-time-stamp
Bit 3: Reason-for-inclusion
Bit 4: Data-set-name
Bit 5: Data-reference
Bit 8: Conf-revision
Bit 9: Segmentation
⚫ File list (the service parameter is directory name) and file attribute information (the service
parameter is file name) through "GetFileAttributeValues" service
The typical application is calling standard COMTRADE file list. MMS service compatibility
supports / and \ delimiters, such as /COMTRADE/ or \COMTRADE\. MMS file service
supports the acquisition of "FileSize" and "LastModified" attributes.
⚫ File data (the service parameter is file name) through "GetFile" service
The recommended typical process of obtaining files for clients is: Firstly, obtaining file list
information through "GetFileAttributeValues" service; Then, selecting the file name of the file
to be obtained according to the file list information; Finally, get the file data of the selected file
through "GetFile" service.
one or more data objects. Values that belong together build the SettingGroup. The SGCB model
provides services to handle different values for one or more data object.
2.5.6 Log
This device supports log service. The stored log information has the feature of no loss in case of
power failure, thus providing convenience for tracing the historical information. The device log is
2
stored in a circular overwrite mode following the First In First Out (FIFO) principle. When the log
storage reaches the maximum capacity, the new log entry will overwrite the oldest entry.
The device supports the attribute configuration of Log Control Block (LCB), which can be enabled
or disabled by modifying LogEna attribute. The device supports the client to obtain the currently
stored log range information by reading the log control block status, and supports querying log by
time QueryLogbyTime and querying log QueryLogAfter information by time and entry. It supports
obtaining specific log information through GetLogStatusValues service.
IEC61850 GOOSE services provide virtual LAN (VLAN) support, Ethernet priority tagging, and
Ether Type Application ID configuration. The support for VLANs and priority tagging allows for the
optimization of Ethernet network traffic. GOOSE messages can be given a higher priority than
standard Ethernet traffic, and they can be separated onto specific VLANs. Devices that transmit
GOOSE messages also function as servers. Each GOOSE publisher contains a “GOOSE control
block” to configure and control the transmission.
This device supports IEC61850 Generic Object Oriented Substation Event (GOOSE)
communication. All GOOSE messages contain IEC61850 data collected into a dataset. It is this
dataset that is transferred using GOOSE message services. The GOOSE related dataset is
configured in the CID file and it is recommended that the fixed GOOSE be used for
implementations that require GOOSE data transfer between devices.
For important application case, in order to ensure no loss of data during transmission, it is
recommended to configure dual network mode, and duplicated GOOSE networks of process level
are independent of the network of station level. The process level network is separated from
station level network and can ensure that important information (e.g. tripping signal) is not affected
by data of MMS network.
Duplicated protection configuration and their GOOSE networks shall be totally independent of
each other, to ensure that in case of any network fault in one set of duplicated protection
configuration, the other set will not be affected.
IEC61850 GOOSE messaging contains a number of configurable parameters, all of which must be
correct to achieve the successful transfer of data. It is critical that the configured datasets at the
transmission and reception devices are an exact match in terms of data structure, and that the
2 GOOSE addresses and name strings match exactly.
2.5.7.1 Sending
IED defines send data by defining GOOSE send dataset and GOOSE control block. GOOSE
service is directly mapped to network data link layer. To ensure important information transmission
priority, broadcast address is used for multi-channel transmission of information. GOOSE
message allows high-speed transmission of tripping signals, which has high transmission success
rate.
GOOSE message is not sent at fixed interval. When there is no GOOSE event, the sending
interval of GOOSE message is fixed and relatively long. However, after an event occurs, the
sending interval is set as the shortest. GOOSE adopts continual retransmission to realize reliable
transmission, and during this period, the sending interval will gradually increase, until the event
status becomes stable. Finally, the sending interval of GOOSE message will be restored to fixed
interval again. The whole process is shown as below:
Transmission Time
Event
Where:
T0 is retransmission in stable conditions (no event for a long time), and it is configurable (typical
value is 5000ms).
T1 is shortest retransmission time after the event, and it is configurable (typical value is 2ms).
T2 is retransmission times until achieving the stable conditions time, and it is fixed at 2T1.
T3 is retransmission times until achieving the stable conditions time, and it is fixed at 4T1.
GOOSE send adopts retransmission mechanism and has 4 transmission times: T0, T1, T2, and
T3. After an event happens, a frame message will be sent, sending again after the time interval T1,
and still sending after another time interval T1. And then, respectively sending again with the time
interval T2 and T3. The sending will be continued at the time interval T0 again if no new event
happens.
GOOSE can send not only binary quantities but also analog quantities without high real-time
requirement, such as, temperature and humidity.
2.5.7.2 Receiving
GOOSE receive is controlled by GOOSE link of corresponding serial number, and provides 2
corresponding alarm signal according to the same serial number. After receiving GOOSE data, the
GOOSE data shall be processed accordingly, including pre-setting to 0, pre-setting to 1,
maintaining if GOOSE data is invalid (refer to the next section).
This device supports SV transmission of not only P2P mode but also networking mode. For
networking mode, MUs of the whole substation realize synchronization sample in the same clock
source, and the sample data are sent to the subscriber by means of network. The subscriber
realizes synchronization of sample values via external synchronous clock. For P2P mode, MUs do
not require external synchronization signal, directly sampling in fixed interval according to its own
clock. The sampled data in the form of point to point are sent to different subscribers. According to
sampled value fixed time of SV message (When sampling in point-to-point mode, MU will record
the time delay from the acquisition to the transmission in special channel of SV message, this
value is usually a fixed value), the subscriber realizes the synchronization of sampled value using
interpolation method.
Where:
⚫ Header MAC
The destination ISO/IEC 8802-3 multicast/unicast address has to be configured for the
transmission of SV. Unique ISO/IEC 8802-3 source address shall be used. The
recommended address ranges from 01-0C-CD-04-00-00 to 01-0C-CD-04-01-FF.
Priority tagging according to IEEE 802.1Q is used to separate time critical and high priority
bus traffic for protection relevant applications from low priority busload. The structure of the
tag header is defined in figure below:
User Priority: BS3; user priority value shall be set by configuration to separate sampled values
and time critical protection relevant GOOSE messages from low priority busload. If the priority
is not configured, then the default values 4 shall be used.
CFI (Canonical Format Indicator): BS1 [0]; a single bit flag value. For this standard the CGI bit
value shall be reset (value = 0).
VID: The use of Virtual LAN support is optional. If this mechanism will be used the VLAN.
Identifier (VID) shall be set by configuration, if it is not used it shall be set to zero (0).
APPID: The APPID is used to distinguish the application association. The reserved value
range for sampled values is 0x4000 to 0x7FFF. If no APPID is configured, the default value
shall be 0x4000. The default value is reserved to indicate lack of configuration. It is strongly
recommended to have unique, source orientated SV APPID within a system.
Length: Number of octets including the Ethertype PDU header starting at APPID, and the
length of the APDU (Application Protocol Data Unit). Therefore, the value of Length shall be 8
+ m, where m is the length of the APDU and m is less than 1492.
The Reserved1 and Reserved2 are reserved for future standardized applications and shall be
set to 0 as default.
⚫ The next frame of GOOSE message is not received within 1.1 times maximum message
survival time (2 * T0, see T0 in Figure 2.3-1 GOOSE send mechanism).
⚫ SV receiving mode is network, but time synchronization signal from merging unit is lost.
⚫ Device maintenance mode is abnormal due to "Test" bit in message, please refer to the
⚫ If a message is not received within 2 times of maximum message survival time, data link
disconnection is confirmed.
Different from traditional contact signals, which can be enabled or disabled by corresponding logic
links, this device adopts the following modes to enable and disable corresponding signals after
applying GOOSE.
Through comparing the value of “Test” bit in message between the publisher and the subscriber,
the data validation of device follows the rules listed in the table below. In “Test” state, the
subscriber still has event recording and state display functions, to facilitate circuit check.
3 DNP3
Table of Contents
The DNP3 (Distributed Network Protocol) protocol supports the OSI/EPA model of the ISO
(International Organization for Standards), and it includes four parts: application layer protocol,
transport functions, data link layer protocol and data object library.
The DNP3 protocol is not described in this chapter; please refer to the DNP3 protocol standard for
the details. The description given here is intended to accompany this device, only specifies which
objects, variations and qualifiers are supported, and also specifies what data is available from this
device via DNP3.
This device operates as a DNP3 slave and supports subset level 3 of the protocol, plus some
features of level 4.
3
Please see the DNP3 protocol standard for the details about linker layer and transport functions.
Network DNP Settings & General Comm Settings – IP address, subnet mask and Net mode
Besides the general Ethernet network settings, such IP address, MAC address, the settings that
are relevant to this protocol are listed in the following table. Refer to the device technical manual
and setting guide for more detail about the parameterization, such as enabling of client, client
address, timeout, etc.
Access path: Main Menu Settings Global Settings Comm Settings DNP Settings
TCP* signifies network client 1~4, COM* signifies serial connection client 1 or 2 in the following
list.
The online
retransmission
Num_URRetry_TCP*_D number for sending
9 3 2~10 1 -
NP the unsolicited
message of the No.*
network DNP client
The offline
retransmission
t_UROfflRetry_TCP*_DN interval for sending
10 60 1~5000 1 s
P the unsolicited
message of the No.*
network DNP client
1-BIChWoutT
The “OBJ2” default
Obj02DefltVar_TCP*_DN 2-BIChWithAbsTi 2-BIChWithAbsTi
16 - - variation of the No.*
P me me network DNP client
3-BIChWithRelTim
1-AI32Int
2-AI16Int
The “OBJ30” default
Obj30DefltVar_TCP*_DN
17 3-AI32IntWoutF 3-AI32IntWoutF - - variation of the No.*
P
network DNP client
4-AI16IntWoutF
5-AI32Flt
1-AI32IntEvWoutT
The “OBJ32” default
Obj32DefltVar_TCP*_DN
18 1-AI32IntEvWoutT 2-AI16IntEvWoutT - - variation of the No.*
P
5-AI32FltEvWoutT
network DNP client
3
1-AO32Int
The “OBJ40” default
Obj40DefltVar_TCP*_DN
19 1-AO32Int 2-AO16Int - - variation of the No.*
P
network DNP client
3-AO32Flt
0 (0x00) Confirm
1 (0x01) Read
2 (0x02) Write
3 (0x03) Select
4 (0x04) Operate
Group/Variation
Description Function code Qualifier code
No.
00,01(start ~ stop)
1 1 Binary Input: Packed format 1(read)
3 06(no range, or all)
00,01(start ~ stop)
1 2 Binary Input: With flags 1(read)
06(no range, or all)
00,01(start ~ stop)
10 0 Binary output: Any Variation 1(read)
06(no range, or all)
00,01(start ~ stop)
10 0 Binary output: Any Variation 1(read)
06(no range, or all)
3(select)
4(operate) 17,28(index)
Binary Command: Control relay output block
12 1
(CROB) 5(direct op)
00,01(start ~ stop)
30 1 Analog Input:32 ~ bit with flag 1(read)
06(no range, or all)
Group/Variation
Description Function code Qualifier code
No.
Group/Variation
Description Function code Qualifier code
No.
3(select)
4(operate) 17,28(index)
3 41 1 Analog Output:32 ~ bit
5(direct op)
3(select)
4(operate) 17,28(index)
41 2 Analog Output:16 ~ bit
5(direct op)
3(select)
4(operate) 17,28(index)
41 3 Analog Output: Single ~ prec ft ~ pt
5(direct op)
1(read)
60 1 Class Objects: Class 0 data 06(no range, or all)
22(assign class)
Group/Variation
Description Function code Qualifier code
No.
20(enable unsol.)
21(disable unsol.) 06(no range, or all)
22(assign class)
Group/Variation
Description Function code Qualifier code
No.
129(response)
2 1 Binary Input Event: Without time 17,28(index)
130(unsol. resp)
129(response)
2 2 Binary Input Event: With absolute time 17,28(index)
130(unsol. resp)
129(response)
2 3 Binary Input Event: With relative time 17,28(index)
130(unsol. resp)
Group/Variation
Description Function code Qualifier code
No.
30 5 Analog Input: Single ~ prec flt ~ pt with flag 129(response) 00, 01(start ~ stop)
3 32 0 Analog Input Event: Any Variation
129(response)
32 1 Analog Input Event:32 ~ bit without time 17,28(index)
130(unsol. resp)
129(response)
32 2 Analog Input Event:16 ~ bit without time 17,28(index)
130(unsol. resp)
40 1 Analog Output Status:32 ~ bit with flag 129(response) 00, 01(start ~ stop)
40 2 Analog Output Status:16 ~ bit with flag 129(response) 00, 01(start ~ stop)
Group/Variation
Description Function code Qualifier code
No.
129(response) 07(limitedqty = 1)
50 1 Time and Data: Absolute time
51 1
Time and Data CTO: Absolute time,
synchronized
129(response)
130(unsol. resp)
07(limitedqty = 1) 3
Time and Data CTO: Absolute time, 129(response)
51 2 07(limitedqty = 1)
unsynchronized 130(unsol. resp)
The judgment method of the analog input change is as below: Calculate the difference between
the current new value and the stored history value and make the difference value multiply by the
“factor”, then compare the result with the “deadband” value. If the result is greater than the
“deadband” value, then an event message of corresponding analog input change will be created.
In normal communication process, the master can online read or modify a “deadband” value by
reading or modifying the variation in “Group34”.
Information Point Pulse On/Null Pulse On/Close Pulse On/Trip Latch On/Null Latch Off/Null
3 Remote Control Not supported Close Trip Close Trip
4 IEC 60870-5-103
Table of Contents
The IEC specification: Telecontrol Equipment and Systems, Part 5: Transmission Protocols
Section 103 defines the use of standards IEC60870-5-1 to IEC60870-5-5 to perform
communication with protective device.
The standard application of IEC60870-5-103 protocol adopts a twisted pair EIA-485 connection
over a distance up to 500m. This device also supports the NR network 103 protocol that is an
alternative to IEC 60870-5-103 and is applicable through Ethernet network. This device operates
as a slave in the communication system, responding to commands from a master station.
Network IEC103 Settings & General Comm Settings – IP address, subnet mask and Net mode
Besides the general Ethernet network settings, such IP address, MAC address, the settings that
are relevant to this protocol are listed in the following table. Refer to the device technical manual
and setting guide for more detail about the parameterization, such as enabling signal, caption
language, etc.
Access path: Main Menu Settings Global Settings Comm Settings IEC103 Settings
The link layer strictly abides by the rules defined in the IEC60870-5-103 standard.
4.3 Initialization
Whenever the device has been powered up, or if the communication parameters have been
changed, a reset command is required to initialize the communications. The device will respond to
either of the two reset commands (Reset CU or Reset FCB), the difference is that the Reset CU
will clear any unsent messages in the transmit buffer.
The device will respond to the reset command with an identification message ASDU 5, the COT
(Cause Of Transmission) of this response will be either Reset CU or Reset FCB depending on the
nature of the reset command.
If the device clock is synchronized using the IRIG-B input then it will not be possible to set the
device time using the IEC60870-5-103 interface. An attempt to set the time via the interface will
cause the protective device to create an event with the current date and time taken from the
IRIG-B synchronized internal clock.
All spontaneous events can be gained by printing, implementing submenu in the path: MainMenu
Print IEC103 Info.
numbers that will be returned during the GI cycle. The GI cycle strictly abides by the rules defined
in the IEC60870-5-103 standard. Refer to the standard to view the details about general
interrogation.
All general classification service group numbers can be gained by printing, implementing submenu
in the path: MainMenu Print IEC103 Info.
The disturbance records are stored in uncompressed format and can be extracted using the
standard mechanisms described in IEC60870-5-103.
All channel numbers (ACC) of disturbance data can be gained by printing, implementing submenu
in the path: MainMenu Print IEC103 Info.
5 Modbus
Table of Contents
The Modbus protocol is a master/slaver serial communication protocol. This device operates as a
slaver in both serial connection and electrical/optical Ethernet network systems with such protocol.
For the detailed information about Modbus protocol, please refer to “Modbus Protocol Reference
Guide (PI-MBUS-300 Rev.J)”.
⚫ Linker layer configuration: RTU communication mode, ASCII code aren't supported.
Network General Comm Settings – IP address, subnet mask and Net mode
Besides the general communication settings, there is no communication settings that are relevant
to this protocol. Refer to the device technical manual and setting guide for more detail about the
parameterization, such as baud rate, port address, etc.
ANNEX A PICS
Table of Contents
A.1 Introduction
This specification is the Protocol Implementation Conformance Statement (PICS) and shows the
Abstract Communication Service Interface (ACSI) conformance statements as defined in Annex A
of Part 7-2 of the IEC 61850 standard specifications. The following ACSI conformance statements,
including ASCI basic conformance statement, ACSI models conformance statement and ACSI
service conformance statement, are used to provide an overview and details about the device.
The statements specify the communication features mapped to IEC 61850-8-1.
Client-Server roles
SCSMs supported
M1 Logical device N Y
M2 Logical node N Y
M3 Data N Y
M4 Data set N Y
M5 Substitution N Y
Reporting
M7-1 sequence-number N Y
M7-2 report-time-stamp N Y
M7-3 reason-for-inclusion N Y
M7-4 data-set-name N Y
M7-5 data-reference N Y
A M7-6 buffer-overflow N Y
M7-7 entryID N Y
M7-8 BufTm N Y
M7-9 IntgPd N Y
M7-10 GI N Y
M7-11 conf-revision N Y
Unbuffered report
M8 N Y
control
M8-1 sequence-number N Y
M8-2 report-time-stamp N Y
M8-3 reason-for-inclusion N Y
M8-4 data-set-name N Y
M8-5 data-reference N Y
M8-6 BufTm N Y
M8-7 IntgPd N Y
M8-8 GI N Y
M8-9 conf-revision N Y
Logging N N
M9 Log control N N
M9-1 IntgPd N N
M10 Log N N
M11 Control N Y
M12 GOOSE Y Y
M13 GSSE N N
Y = service is supported
N or empty = service is not supported
Server
S1 GetServerDirectory TP N Y
Application association
S2 Associate N Y
S3 Abort N Y
S4 Release N Y
Logical device
S5 GetLogicalDeviceDirectory TP N Y
Logical node
S6 GetLogicalNodeDirectory TP N Y
S7 GetAllDataValues TP N Y
Data
S8 GetDataValues TP N Y
S9 SetDataValues TP N Y
S10 GetDataDirectory TP N Y
S11 GetDataDefinition TP N Y
Data set
S12 GetDataSetValues TP N Y
S13 SetDataSetValues TP N N
A S14 CreateDataSet TP N N
S15 DeleteDataSet TP N N
S16 GetDataSetDirectory TP N Y
Substitution
S17 SetDataValues TP N Y
S18 SelectActiveSG TP N Y
S19 SelectEditSG TP N Y
S20 SetSGValues TP N Y
S21 ConfirmEditSGValues TP N Y
S22 GetSGValues TP N Y
S23 GetSGCBValues TP N Y
Reporting
S24 Report TP N Y
S25 GetBRCBValues TP N Y
S26 SetBRCBValues TP N Y
S27 Report TP N Y
S28 GetURCBValues TP N Y
S29 SetURCBValues TP N Y
Logging
A
Log control block
S30 GetLCBValues TP N N
S31 SetLCBValues TP N N
Log
S32 QueryLogByTime TP N N
S33 QueryLogAfter TP N N
S34 GetLogStatusValues TP N N
GOOSE-CONTROL-BLOCK
S35 SendGOOSEMessage MC N Y
S36 GetGoReference TP N Y
S37 GetGOOSEElementNumber TP N N
S38 GetGoCBValues TP N Y
S39 SetGoCBValues TP N N
GSSE-CONTROL-BLOCK
S40 SendGSSEMessage MC N N
S41 GetReference TP N N
S42 GetGSSEElementNumber TP N N
S43 GetGsCBValues TP N N
S44 SetGsCBValues TP N N
Multicast SVC
S45 SendMSVMessage MC N N
S46 GetMSVCBValues TP N N
S47 SetMSVCBValues TP N N
Unicast SVC
S48 SendUSVMessage TP N N
S49 GetUSVCBValues TP N N
A
S50 SetUSVCBValues TP N N
Control
S51 Select N N
S52 SelectWithValue TP N Y
S53 Cancel TP N Y
S54 Operate TP N Y
S55 CommandTermination TP N Y
S56 TimeActivatedOperate TP N N
File transfer
S57 GetFile TP N Y
S58 SetFile TP N N
S59 DeleteFile TP N N
S60 GetFileAttributeValues TP N Y
Time
Client-Server roles
SCSMs supported
M1 Logical device N Y
M2 Logical node N Y
M3 Data N Y
M4 Data set N Y
A
M5 Substitution N Y
Reporting
M7-1 sequence-number N Y
M7-2 report-time-stamp N Y
M7-3 reason-for-inclusion N Y
M7-4 data-set-name N Y
M7-5 data-reference N Y
M7-6 buffer-overflow N Y
M7-7 entryID N Y
M7-8 BufTm N Y
M7-9 IntgPd N Y
M7-10 GI N Y
M7-11 conf-revision N Y
M8-1 sequence-number N Y
M8-2 report-time-stamp N Y
M8-3 reason-for-inclusion N Y
M8-4 data-set-name N Y
M8-5 data-reference N Y
M8-6 BufTm N Y
M8-7 IntgPd N Y
M8-8 GI N Y
M8-9 conf-revision N Y
Logging N N
M9 Log control N N
M9-1 IntgPd N N
M10 Log N N
A
M11 Control N Y
M12 GOOSE Y Y
Y = service is supported
N or empty = service is not supported
AA:Client Server
Services Comments
TP/MC (C) (S)
Server
GetServerDirectory
S1 TP N Y
(LOGICAL-DEVICE)
Application association
S2 Associate N Y
S3 Abort N Y
S4 Release N Y
Logical device
A S5 GetLogicalDeviceDirectory TP N Y
Logical node
S6 GetLogicalNodeDirectory TP N Y
S7 GetAllDataValues TP N Y
Data
S8 GetDataValues TP N Y
S9 SetDataValues TP N Y
S10 GetDataDirectory TP N Y
S11 GetDataDefinition TP N Y
Data set
S12 GetDataSetValues TP N Y
S13 SetDataSetValues TP N N
S14 CreateDataSet TP N N
S15 DeleteDataSet TP N N
S16 GetDataSetDirectory TP N Y
Substitution
S18 SelectActiveSG TP N Y
S19 SelectEditSG TP N Y
S20 SetEditSGValues TP N Y
S21 ConfirmEditSGValues TP N Y
S22 GetEditSGValues TP N Y
S23 GetSGCBValues TP N Y
Reporting
S24 Report TP N Y
S25 GetBRCBValues TP N Y
S26 SetBRCBValues TP N Y
S27 Report TP N Y
S28 GetURCBValues TP N Y
S29 SetURCBValues TP N Y
Logging
S30 GetLCBValues TP N N
S31 SetLCBValues TP N N
Log
S32 QueryLogByTime TP N N
S33 QueryLogAfter TP N N
S34 GetLogStatusValues TP N N
GOOSE
S35 SendGOOSEMessage MC N Y
GOOSE-CONTROL-BLOCK
S36 GetGoReference TP N Y
S37 GetGOOSEElementNumber TP N N
S38 GetGoCBValues TP N Y
S39 SetGoCBValues TP N N
GSSE
Multicast SV
S45 SendMSVMessage MC N N
S46 GetMSVCBValues TP N N
S47 SetMSVCBValues TP N N
Unicast SV
S48 SendUSVMessage TP N N
S49 GetUSVCBValues TP N N
S50 SetUSVCBValues TP N N
Control
S51 Select N Y
S52 SelectWithValue TP N Y
S53 Cancel TP N Y
S54 Operate TP N Y
S55 CommandTermination TP N Y
S56 TimeActivatedOperate TP N N
File transfer
S57 GetFile TP N Y
S58 SetFile TP N N
S59 DeleteFile TP N Y
S60 GetFileAttributeValues TP N Y
A
S61 GetServerDirectory (FILE-SYSTEM) TP N Y
Time
Nearest value of 2 -n in
T3 Supported TimeStamp resolution - 10 seconds
(number 0 .. 24)
ANNEX B MICS
Table of Contents
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
B.1 Introduction
This specification is the Model Implementation Conformance Statement (MICS) and presents the
IEC 61850 data model that has been implemented. Within the IEC 61850 part 7 series of
specifications, the definitions of all used Logical Nodes and their associated Common Dat a
Classes are included. For the more details on the standardized model, please compare the ICD
substation configuration file *.icd.
Date: 2020-08-04
ANNEX B MICS
LLN0 class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Controls
Settings
Date: 2020-08-04
ANNEX B MICS
LPHD class
Attribute
Attribute Name Explanation M/O/E Remarks
Type
Data
Descriptions
Status Information
Settings
Date: 2020-08-04
ANNEX B MICS
CILO class
Attribute
Attribute Name Explanation M/O/E Remarks
Type
CILO Interlocking
Data
Status Information
Date: 2020-08-04
ANNEX B MICS
GGIO class
Attribute
Attribute Name Explanation M/O/E Remarks
Type
Data
Settings
Date: 2020-08-04
ANNEX B MICS
GGIO class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Controls
PDIF class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PDIF Differential
Data
B
Beh INS Behaviour M
Status Information
Op ACT Operate M
Date: 2020-08-04
ANNEX B MICS
Settings
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
Enabling/disabling phase-segregated
PhSegEna SPG E
inter-tripping
PDOP class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Settings
PFRC class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Settings
PHAR class
Attribute Attribute
Explanation M/O/E Remarks B
Name Type
Data
Status Information
Date: 2020-08-04
ANNEX B MICS
Settings
PTOC class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Status Information
Op ACT Operate M
Settings
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
PTOF class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PTOF Overfrequency
Data
Status Information
Op ACT Operate M
Settings
B
StrVal ASG Start Value (frequency) O
Date: 2020-08-04
ANNEX B MICS
PTOV class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PTOV Overvoltage
Data
Status Information
Op ACT Operate M
Settings
Date: 2020-08-04
ANNEX B MICS
PTRC class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Controls
Status Information
B
Tr ACT Trip M
Op ACT Operate M
Settings
Date: 2020-08-04
ANNEX B MICS
PTTR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
B
Status Information
Op ACT Operate M
Settings
Date: 2020-08-04
ANNEX B MICS
PTUC class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PTUC Undercurrent
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Settings
PTUF class
B
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PTUF Underfrequency
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Settings
PTUV class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PTUV Undervoltage
Data
B
Common Logical Node Information
Status Information
Op ACT Operate M
Settings
Date: 2020-08-04
ANNEX B MICS
B.2.4.18 PVCE:
PVCE class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Date: 2020-08-04
ANNEX B MICS
PVCE
Data
Status Information
Op ACT Operate M
Settings
RBRF class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Date: 2020-08-04
ANNEX B MICS
Data
Status Information
Settings
FailTmms ING Breaker Failure Time Delay for bus bar trip O
FailDlTmms ING Breaker Failure Time Delay for bus tie trip E
B
UVBlkVal ASG Block value of phase voltage E
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
Controls
RDIR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
B
NamPlt LPL Name Plate M
Status Information
Settings
Date: 2020-08-04
ANNEX B MICS
RDRE class
Attribute
Attribute Name Explanation M/O/E Remarks
Type
Data
B Controls
Status Information
Date: 2020-08-04
ANNEX B MICS
FltDist MV Fault_Distance E
FaultI MV Fault_I E
FaultV MV Fault_V E
ReFltDist MV ReFault_Distance E
ReFaultI MV ReFault_I E
ReFaultV MV ReFault_V E
RFLO class
Attribute Attribute
Explanation M/O/E Remarks
B
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Settings
RREC class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Date: 2020-08-04
ANNEX B MICS
RREC Autoreclosing
Data
Status Information
Op ACT Operate M
Settings
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
Controls
RSYN class
Attribute Attribute
Explanation M/O/E Remarks
B
Name Type
RSYN Synchronism-check
Data
Status Information
Date: 2020-08-04
ANNEX B MICS
Settings
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
TCTR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
B
Status Information
Descriptions
Settings
Date: 2020-08-04
ANNEX B MICS
TVTR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
B
Beh INS Behaviour M
Status Information
Descriptions
Date: 2020-08-04
ANNEX B MICS
Settings
CILO (Interlocking)
MMTR (Metering)
MMXU (Measurement)
PDIF (Differential)
Date: 2020-08-04
ANNEX B MICS
PTOF (Overfrequency)
PTOV (Overvoltage)
PTUC (Undercurrent)
PTUF (Underfrequency)
PTUV (Undervoltage)
PVCE
RREC (Autoreclosing)
RSYN (Synchronism-check)
Date: 2020-08-04
ANNEX B MICS
LLN0 class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Status Information
Controls
Date: 2020-08-04
ANNEX B MICS
Settings
LPHD class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Descriptions
Date: 2020-08-04
ANNEX B MICS
Status Information
Controls
Settings
CILO class
Date: 2020-08-04
ANNEX B MICS
Name Type
CILO Interlocking
Data
Status Information
Controls
Settings
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Controls
Descriptions
Settings
Date: 2020-08-04
ANNEX B MICS
GGIO class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Controls
LGOS class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Controls
Settings
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PDIF Differential
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
B Controls
Settings
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
Enabling/disabling phase-segregated
PhSegEna SPG E
inter-tripping
PDOP class
B Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Controls
Settings
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Controls
Settings
PHAR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Controls
Settings
PTOC class B
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Controls
Settings
Date: 2020-08-04
ANNEX B MICS
PTOF class
B
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PTOF Overfrequency
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Op ACT Operate M
Controls
Settings
PTOV class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
B PTOV Overvoltage
Data
Status Information
Date: 2020-08-04
ANNEX B MICS
Op ACT Operate O
Controls
Settings
PTRC class
Date: 2020-08-04
ANNEX B MICS
Name Type
Data
Status Information
Tr ACT Trip M
Controls
Settings
Date: 2020-08-04
ANNEX B MICS
PTTR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
B
Status Information
Op ACT Operate M
Controls
Date: 2020-08-04
ANNEX B MICS
Settings
PTUC class
Date: 2020-08-04
ANNEX B MICS
Name Type
PTUC Undercurrent
Data
Status Information
Op ACT Operate M
Controls
Settings
PTUF class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Date: 2020-08-04
ANNEX B MICS
PTUF Underfrequency
Data
Status Information
Op ACT Operate M
Controls
Settings
PTUV class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PTUV Undervoltage
Date: 2020-08-04
ANNEX B MICS
Data
Status Information
Op ACT Operate M
Controls
Settings
Date: 2020-08-04
ANNEX B MICS
B.3.4.19 PVCE:
PVCE class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
PVCE
Data
Status Information
Op ACT Operate M
Settings
Date: 2020-08-04
ANNEX B MICS
RBRF class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
B
Beh ENS Behaviour M
Status Information
Date: 2020-08-04
ANNEX B MICS
Controls
Settings
FailTmms ING Breaker failure time delay for bus bar trip O
Date: 2020-08-04
ANNEX B MICS
RDIR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
B
Beh ENS Behaviour M
Status Information
Controls
Settings
Date: 2020-08-04
ANNEX B MICS
RDRE class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
B Data
Status Information
Date: 2020-08-04
ANNEX B MICS
Controls
Settings
Date: 2020-08-04
ANNEX B MICS
FltDist MV Fault_Distance E
FaultI MV Fault_I E
FaultV MV Fault_V E
ReFltDist MV ReFault_Distance E
ReFaultI MV ReFault_I E
ReFaultV MV ReFault_V E
RFLO class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
B RFLO Fault locator
Data
Status Information
Date: 2020-08-04
ANNEX B MICS
Controls
Date: 2020-08-04
ANNEX B MICS
RREC class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
RREC Autoreclosing
Data
Status Information
Date: 2020-08-04
ANNEX B MICS
Controls
Settings
B
Rec13Tmms2 ING Reclose time for evolving faults E
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
RSYN class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
RSYN Synchronism-check
Data
B
Common Logical Node Information
Status Information
Date: 2020-08-04
ANNEX B MICS
Controls
Date: 2020-08-04
ANNEX B MICS
Date: 2020-08-04
ANNEX B MICS
TCTR class
B Attribute
Name
Attribute
Type
Explanation M/O/E Remarks
Data
Status Information
Date: 2020-08-04
ANNEX B MICS
Controls
Descriptions
Settings
TVTR class
Attribute Attribute
Explanation M/O/E Remarks
Name Type
Data
Date: 2020-08-04
ANNEX B MICS
Status Information
Controls
Descriptions
Settings
Date: 2020-08-04
ANNEX C TICS
ANNEX C TICS
Table of Contents
Date: 2020-08-04
ANNEX C TICS
Date: 2020-08-04
ANNEX C TICS
C.1 Introduction
The Technical Issues Conformance Statement (TICS) is required to perform a conformance test
and is referenced on the certificate. This document gives an overview of the device conformance
level of Technical Issues (TIssue) against the IEC 61850 series of standards Edition 2.
C.2 Part 6
Date: 2020-08-04
ANNEX C TICS
1151 simulated GOOSE disappears after 1st appearance when LPHD.Sim = TRUE Y
1091 The sentence "The initial value of EditSG shall be 0", has to be stated in part 7.2 not
C
Y
in 8.1
Date: 2020-08-04
ANNEX C TICS
676 Same data object name used with different CDC N/A
677 MotStr is used with different CDC in PMMS and SOPM LN classes N/A
682 ANCR.ParColMod Y
736 PFSign Y
Date: 2020-08-04
ANNEX C TICS
Date: 2020-08-04
ANNEX D PIXIT
ANNEX D PIXIT
Table of Contents
Date: 2020-08-04
ANNEX D PIXIT
Date: 2020-08-04
ANNEX D PIXIT
D.1 Introduction
This document specifies the Protocol Implementation eXtra Information for Testing (PIXIT) of the
IEC 61850 interface in this device. Together with the PICS and MICS specifications, the PIXIT
forms the basis for conformance test according to IEC 61850-10. The PIXIT entries contain
information which is not available in the PICS, MICS, TICS document or SCL file.
Transport selector
Calling: N Called: Y
Session selector
Calling: N Called: Y
As7 1,2 What is the maximum and minimum MMS PDU size
Max MMS PDU size 65k bytes D
Min MMS PDU size 1024 bytes
Date: 2020-08-04
ANNEX D PIXIT
ID Ed Description 7
Validity:
Y Good,
Y Invalid,
N Reserved,
Y Questionable
Detail Quality
N Overflow
N OutofRange
N BadReference
Which analogue value (MX) quality bits are
Sr1 1,2
supported (can be set by server) N Oscillatory
N Failure
Y OldData
N Inconsistent
N Inaccurate
Miscellaneous:
Y Source
Y Test
Y OperatorBlocked
Validity:
Y Good,
Y Invalid,
N Reserved,
Y Questionable
Detail Quality
N BadReference
Which status value (ST) quality bits are supported
Sr2 1,2 N Oscillatory
(can be set by server)
N Failure
Y OldData
N Inconsistent
D N Inaccurate
Miscellaneous:
Y Source
Y Test
Date: 2020-08-04
ANNEX D PIXIT
ID Ed Description 7
Y OperatorBlocked
On Y
[On-]Blocked Y
Sr5 1 Which Mode values are supported Test Y
Test/Blocked Y
Off Y
What is the effect of when and how the non-volatile The value is stored into NOR FLASH in
Sg2 1,2 storage is updated IED, and after storage is completed the
(compare IEC 61850-8-1 §16.2.4) value CnfEdit is set to FALSE.
Sg4 1
What happens if the association is lost while editing a
setting group
The SE values changes are lost, the
EditSG is reset to 0 D
Sg5 1 Is EditSG value 0 allowed Y
Sg6 2 When ResvTms is not present how long is an edit Keep the state before the association is
Date: 2020-08-04
ANNEX D PIXIT
integrity Y
data change Y
The supported trigger conditions are
Rp1 1 quality change Y
(compare PICS)
data update Y
general interrogation Y
sequence-number Y
report-time-stamp Y
reason-for-inclusion Y
data-set-name Y
Rp2 1 The supported optional fields are data-reference Y
buffer-overflow Y
entryID Y
conf-rev Y
segmentation Y
What is the buffer size for each BRCB or how many 200 reports and less than50k bytes
Rp7 1,2
reports can be buffered storage memory
D Rp10 1,2
What is the scan cycle for binary events Event driven based
Is this fixed, configurable Fixed
Date: 2020-08-04
ANNEX D PIXIT
SPS
Gp3 1,2 Published FCD supported common data classes are
Arrays are not supported
Date: 2020-08-04
ANNEX D PIXIT
Gp7 1,2 What is the initial GOOSE sqNum after restart sqNum = 1
Notes: N sqNum
Gs1 1,2
• the VLAN tag may be removed by an Ethernet Y simulation / test
switch and shall not be checked Y confRev
• the simulation flag shall always be checked Y ndsCom
(Ed2)
Y numDatSetEntries
Y out-of-order dataset members
Note1:See Gs_EX1 for checking rules.
Note2:GoID only checked if different
from SCL. An Empty GoID(GoID entry
absent) is not recognized as invalid
GOOSE.
Date: 2020-08-04
ANNEX D PIXIT
Does the device subscribe to GOOSE messages Y, with the VLAN tag
Gs6 1
with/without the VLAN tag Y, without the VLAN tag
Gs_E -goID
1,2
X1 - simulation
When subscribed GOOSE messages have another
incorrect information:
- confRev All data of the messages will not be
accessed and the ‘cfg_err’ warning will
- ndsCom(true) be activated immediately.
- numDatSetEntries
- alldata (subscribed member data type mismathed)
Max. configurable
Gf3 1,2 Application logic scan cycle (ms)
Min. 0.694 Ms D
Maximum number of data attributes in GOOSE
Gf4 1 dataset (value and quality has to be counted as 256
separate attributes)
Date: 2020-08-04
ANNEX D PIXIT
Dons: Y
What control models are supported SBOns: Y
Ct1 1
(compare PICSICD file enums for Ed2) DOes: Y
SBOes: Y
Will the DUT activate the control output when the test
Ct5 1 attribute is set in the SelectWithValue and/or Operate N
request (when N test procedure Ctl2 is applicable)
Date: 2020-08-04
ANNEX D PIXIT
Y Unknown
Y Not-supported
Y Blocked-by-switching-hierarchy
N Select-failed
Y Invalid-position
Y Position-reached
N Step-limit
Y Blocked-by-Mode
Y Blocked-by-process
Y Blocked-by-interlocking
Y Blocked-by-synchrocheck
Y Command-already-in-execution
Y Blocked-by-health
Y 1-of-n-control
N Abortion-by-cancel
Y Time-limit-over
N Abortion-by-trip
Y Object-not-selected
How to force a “test-not-ok” respond with Operate SBOns: e.g. invalid orCat value
Ct12 1,2
request DOes: e.g. invalid orCat value
SBOes: e.g. invalid orCat value
D
Date: 2020-08-04
ANNEX D PIXIT
Y bay-control
Y station-control
Y remote-control
Y automatic-bay
Ct13 1,2 Which origin categories are supported / accepted
Y automatic-station
Y automatic-remote
Y maintenance
Y process
What happens if the orCat value is not supported or SBOns: Negative response
Ct14 1,2
invalid DOes: Negative response
SBOes: Negative response
DOns: N
Does the IED accept a SelectWithValue / Operate
with the same control value as the current status SBOns: N
value
Ct15 1,2 DOes: N Position-reached
SBOes: N Position-reached
Is this behaviour configurable
Configurable N
DOns: N
Ct18 1 Deprecated
Date: 2020-08-04
ANNEX D PIXIT
SBOes: 60 000
specify the timeout (in milliseconds)
DOns: Y
Ct28 Depecated
Y LeapSecondsKnown
What time quality bits are supported (may be set by
Tm1 1 N ClockFailure
the IED)
Y ClockNotSynchronized
180 seconds
What is the time server lost detection time
How long does it take to take over the new time from
Tm3 1,2 35 seconds
time server
Tm4 1,2 When is the time quality bit “ClockFailure” set Cannot be tested
Date: 2020-08-04
ANNEX D PIXIT
N OriginateTimestamp is equal
to value sent by the SNTP
Which attributes of the SNTP response packet are client as Transmit Timestamp
Tm8 1,2
validated
N RX/TX timestamp fields are
checked for reasonableness
N other (describe)
Do the COMTRADE files have local time or UTC time Local Time
Tm9 1,2
and is this configurable Not Configurable
Directories name:COMTRADE
What is the structure of files and directories
Ft2 1,2 Directory names are separated from the file name by “/”
Is the wild card supported in the MMS fileDirectory Yes, wild card = *
Ft7 1
request
Y same file
Ft8 1,2 Is it allowed that 2 clients get a file at the same time
Y different files
D Ft9 1,2 Which files can be deleted The files in the directory: COMTRADE
Date: 2020-08-04
ANNEX D PIXIT
Date: 2020-08-04
ANNEX D PIXIT
Date: 2020-08-04