Beruflich Dokumente
Kultur Dokumente
IEC61850forBitronics70Series
Manual
Mx7x
IEC61850 for Bitronics 70 Series
Publication Reference: Mx7xI/EN/M/J
Mx7xI/EN/M/J2012.ALSTOM,theALSTOMlogoandanyalternativeversionthereofaretrademarksandservicemarksofALSTOM.Theothernames
mentioned,registeredornot,arethepropertyoftheirrespectivecompanies.Thetechnicalandotherdatacontainedinthisdocumentisprovidedfor
information only.NeitherALSTOM, its officers or employeesacceptresponsibilityfor, orshould be takenasmakinganyrepresentation or warranty
(whetherexpressorimplied),astotheaccuracyorcompletenessofsuchdataortheachievementofanyprojectedperformancecriteriawheretheseare
indicated.ALSTOMreservestherighttoreviseorchangethisdataatanytimewithoutfurthernotice.
GRID
Mx7xI/EN M/J
70 series
Page 1
CONTENTS
1.
1.1
Introduction
1.2
1.3
11
1.4
15
1.5
15
1.6
15
1.7
Ethernet functionality
17
2.
2.1
Introduction
18
2.2
18
2.3
19
2.4
20
3.
24
3.1
Introduction
24
3.2
Objective
24
3.3
24
3.4
43
3.5
72
3.6
86
3.7
88
3.8
91
4.
4.1
Introduction
92
4.2
Tissues considered
92
4.3
Document structure
93
4.4
93
4.5
Part 5 Standard
94
4.6
Part 6 Standard
94
4.7
97
4.8
98
4.9
110
4.10
113
4.11
117
4.12
121
4.13
121
ISSUES
(TISSUES)
CONFORMANCE
92
Mx7xI/EN M/J
Page 2
4.14
Part 10 Standard
122
5.
5.1
Introduction
123
5.2
Document structure
123
5.3
123
5.4
Server Model
125
5.5
126
5.6
126
5.7
126
5.8
Reporting Model
127
5.9
128
5.10
129
5.11
132
5.12
Control Model
132
5.13
134
5.14
135
5.15
136
5.16
IED Configuration
136
Mx7xI/EN M/J
70 series
Page 3
DSP
Firmware
2.1/3.0*
1.210
2.050
2.31
2.43
03/24/06
2.1/3.0*
"
2.060
2.32
2.44
04/14/06
2.1/3.0*
1.240
2.120
2.39
2.50
10/01/06
2.1/3.0*
1.240
2.150
2.41
2.52
12/18/06
3.40
1.30
2.170
2.43
2.56
12/21/07
3.40
1.30
2.18
3.00A
2.57
10/17/08
3.40
1.31
2.19
3.02
2.58
09/30/09
3.40
1.30
3.01.0
3.01
3.01
1/30/09
Description
Host
Firmware
Configu Utilities
rator
CD
Release
Date
M870 Family
Mx7x Product Release,
Mx7xI/EN M/J
Page 4
70 series
Firmware Versions
Description
Bios
Version
DSP
Firmware
Host
Firmware
Configu Utilities
rator
CD
Release
Date
3.40
1.31
3.02
3.02
3.02
09/30/09
3.40
1.31
3.04
3.04
3.04
10/15/10
3.40
1.32
3.05
3.05
3.05
2/28/11
3.40
1.32
3.07
3.07
3.07
11/11/11
3.40
1.32
3.07.3
3.07
3.07
2/1/2012
3.40
1.32
3.07.4
3.07
3.07
2/15/2012
3.40
1.32
3.07.6
3.07
3.07
3/13/2012
3.40
1.32
3.07.7
3.07
3.07
3/15/2012
* H10/H11
Mx7xI/EN M/J
Page 5
CERTIFICATION
Alstom Grid certifies that the calibration of our products is based on measurements using
equipment whose calibration is traceable to the United States National Institute of Standards
Technology (NIST).
ASSISTANCE
For assistance, contact the Alstom Grid Worldwide Contact Centre:
http://www.alstom.com/grid/contactcentre/
Tel: +44 (0) 1785 250 070
SAFETY SECTION
Please refer to the M87x and M57x User Manuals for information regarding safety,
installation, commissioning and decommissioning.
Mx7xI/EN M/J
Page 6
70 series
COPYRIGHT NOTICE
This manual is copyrighted and all rights are reserved. The distribution and sale of this
manual is intended for the use of the original purchaser or his agents. This document may
not, in whole or part, be copied, photocopied, reproduced, translated or reduced to any
electronic medium or machine-readable form without prior consent of Alstom Grid, except for
use by the original purchaser.
This manual incorporates information protected by copyright and owned by
Bitronics LLC, 261 Brodhead Road, Bethlehem, PA 18017.
Copyright 2011 Bitronics, LLC. All rights reserved.
The product described by this manual contains hardware and software that is protected by
copyrights owned by one or more of the following entities:
Bitronics LLC, 261 Brodhead Road, Bethlehem, PA 18017;
IntervalZero, Inc., 400 Fifth Avenue, 4th Floor, Waltham, MA 02451;
SISCO, Inc., 6605 192 Mile Road, Sterling Heights, MI 48314-1408;
General Software, Inc., Box 2571, Redmond, WA 98073;
Schneider Automation, Inc., One High Street, North Andover, MA 01845;
Triangle MicroWorks, Inc., 2213 Middlefield Court, Raleigh, NC 27615
Greenleaf Software Inc., Brandywine Place, Suite 100, 710 East Park Blvd, Plano, TX 75074
TRADEMARKS
The following are trademarks or registered trademarks of Alstom Grid:
Alstom Grid
Bitronics
The following are trademarks or registered trademarks of the DNP User's Group:
DNP
DNP3
The following are trademarks or registered trademarks of the Electric Power Research
Institute (EPRI):
UCA
The following are trademarks or registered trademarks of Schneider Automation, Inc.:
MODSOFT
PLC
Modicon
Modbus Plus
Modbus
Compact 984
MMS-EASE Lite
AX-S4MMS
the GS logo
EMBEDDED BIOS
Embedded
The following are trademarks or registered trademarks of the PCI Industrial Computer
Manufacturers Group:
CompactPCI
Mx7xI/EN M/J
70 series
Page 7
1.
1.1
Introduction
IEC 61850 is the international standard for Ethernet-based communication in substations. It
enables integration of all protection, control, measurement and monitoring functions within a
substation, and additionally provides the means for interlocking and inter-tripping. It
combines the convenience of Ethernet with the security which is essential in substations
today.
Alstom Grid has been involved in the Working Groups which formed the standard, building
on experience gained with UCA2.0, the predecessor of IEC 61850. Operability of the
UCA2.0 protocol is still supported in 70 Series devices.
The 70 Series measurement IEDs, models M57x and M87x, support the IEC 61850, protocol
over the Ethernet interface. M57x and M87x models are designed to integrate with
substation control systems (ie. Alstom MiCOM protection relays integrated with PACiS
substation control systems).
1.2
Standardized models for IEDs and other equipment within the substation
The standard includes mapping of data onto Ethernet. Using Ethernet in the substation
offers many advantages, but most significantly, including:
1.2.1
High-speed data rates (currently 100 Mbits/s, rather than 10s of kbits/s or less used
by most serial protocols)
Interoperability
A major benefit of IEC 61850 is interoperability. IEC 61850 standardizes the data model of
substation IEDs. This responds to the utilities desire of having easier integration for different
vendors products, i.e. interoperability. It means that data is accessed in the same manner in
different IEDs from either the same or different IED vendors, even though, for example, the
measurement and protection algorithms of different vendors IED (or device) types remain
different.
When a device is described as IEC 61850-compliant, this does not mean that it is
interchangeable, but it does mean that it is interoperable. You cannot simply replace one
product with another, however the terminology is pre-defined and anyone with prior
knowledge of IEC 61850 should be able to very quickly integrate a new device without the
need for mapping of all of the new data. IEC 61850 will inevitably bring improved substation
communications and interoperability, at a lower cost to the end user.
Mx7xI/EN M/J
Page 8
1.2.2
70 series
Summary of 70Series IEC 61850 Features (Based on part 7-2 of the IEC 61850 standard)
This table summarizes the IEC 61850 features for M57x or M87x type devices.
Section 6
Server Model
3 logical devices Measurements, Records, System
1 File Directory (of COMTRADE files)
Section 7
Association
Two Party Application Association Model used for normal data and (non -GOOSE)
reporting. Includes a simple method to inhibit writing for view-only applications
Multicast Association Model used for GOOSE messaging
Section 8
Logical Device
Mx7x Measurement IEDs
Section 9
Logical Nodes
50+ Logical Nodes as defined in the Model Implementation Conformance Statement
(MICS). Exact Count is dependent upon device configuration (for example, number
of physical I/O points, which can vary based on the installed options )
No pre-defined datasets
32 pre-defined URCBs (Unbuffered Report Control Blocks) in System/LLN0
4 pre-defined BCRBs (Buffered Report Control Blocks) in System/LLN0
8 pre-defined GoCB (GOOSE Control Blocks) in System/LLN0
Section 10
Data
Includes all features except access controls (however, the ability to write to points
depends upon association parameters)
Section 11
Datasets
26 definable datasets with FCD/FCDA capability. (A dataset consists of a named list
of variables)
Section 12
Substitution
NOT SUPPORTED in 70Series
Section 13
Settings Groups
NOT SUPPORTED in 70Series
Section 14
Mx7xI/EN M/J
70 series
Section 15
Page 9
Generic Substation Events GSE ( and GOOSE)
8 publishing GOOSEs (with GOOSE Control Block - GoCB)
Power-on configurability includes Control Block name (cbName), Dataset (DatSet),
Application ID (AppID), Configuration Revision (confRev) and Dataset Address
(DstAddress).
No Dynamic Configurability - only Report Enable (rptEna) can be changed.
32 subscribing GOOSEs, with 32 booleans and 32 integers/ enumerations and 32
floating points (floats) populated in the internal 70Series database.
No GOOSE management capabilities (these are GetGoReference and
GetGOOSEElement).
Section 16
Section 17
Section 18
Time Synchronization
Up to 2 SNTP servers using optional many-cast (or any-cast) mode of operation are
supported along with configurable polling times. SNTP servers can be polled for
configurable time, but only one at a time.
Section 20
Files
COMTRADE files are supported.
Mx7xI/EN M/J
Page 10
1.2.3
70 series
The data model
To ease understanding, the data model of any IEC 61850 IED can be viewed as a hierarchy
of information. The categories and naming of this information is standardized in the IEC
61850 specification.
Data Attribute
stVal
Mag
SPCSO
TotW
Data Object
LN1
(GGIO)
LN2
(MMXU)
Logical Node
Logical Device
(IED1)
(1 to n)
Logical Device
(1 to n)
Physical Device
(network address)
Physical Device
M0183ENa
- Logical Device
Mx7xI/EN M/J
70 series
1.3
Page 11
- Data Object
- Data Attribute
the Host board must have been manufactured with 64M RAM,
It is necessary that the Host board has a compact Flash card installed
The Host firmware version must be version v3.00.0 (or later) which is the version that
implements the IEC 61850 communications protocol.
The 70Series Configurator software must be the proper version in order to support:
Creation of new initialization (INI) files: The INI files are required in order to
configure the Mx70 device. The 70 Series Configurator creates these INI files
and stores them on the Mx70 device in the folder C:\Config.
Creation of the IED Capability Description (ICD) file: The 70 Series ICD file is
an IEC 61850 Substation Configuration Language (SCL) file which contains
the IEC 61850 'capability' description of the particular 70 Series IED. It is
created by the 70 Series Configurator tool and then used by the IEC 61850
IED Configurator tool to perform an IEC 61850 configuration. After a new
device configuration is created, the 70 Series Configurator tool automatically
installs the ICD file in the "C:\Config" folder on the Mx70 device. In addition,
the 70 Series Configurator places a second copy of the ICD file in a userdefinable location on the local personal computer (PC) for use by the IEC
61850 IED Configurator tool. This user-definable location can be set using
the "File->Set Templates directory" option in the 70 Series Configurator tool
menu. It is recommended this option be set to the location of the "Templates"
folder used by the IEC 61850 IED Configurator tool (i.e. "..\IED
Configurator\Templates"). If necessary, the 70 Series Configurator tool will
automatically create two sub-folders named "M57X" and "M87X" where it will
place the ICD files specific to each of the M57x and M87x family of devices,
respectively.
Mx7xI/EN M/J
Page 12
70 series
address of the device. Two configurations are supported; 'active' and
'inactive'. The program will then prompt the user if they would like the current
configuration to be made the active configuration. The two configurations
correspond to the following filenames;
Finally, the user will be prompted if they would like the Mx70 IED to be
automatically restarted. The user should answer 'yes' in order for the active
bank switch to take effect during the next power cycle.
The user should also make a backup copy of their configuration. This
can be done using the "File-Save" or "File->Save As" menu options
which saves a backup copy of the MCL file to the local PC. It should
be noted that in addition to creating 'new' IEC 61850 configurations
using ICD template files, the IED Configurator tool gives the user the
ability to import and export the following types of IEC 61850 SCL
files;
Importing
Exporting
In order to communicate with an IEC 61850 device, it is necessary to set its Ethernet IP
address. Before configuring an Mx70 device on the TCP/IP network you will need to
determine the IP address for the device. An IP address is needed to enter a configuration
for an Mx70 device, using the 70Series Configurator and the IEC 61850 IED Configurator
software tools. The IP address can be retrieved or changed though the P1 service port
(serial port) by establishing a connection through Hyperterminal. (Refer to the relevant Host
section in either the M87x or M57x user manual if you need to acquaint yourself with the
connection to and operation over the service port P1.) It is recommended that before
establishing a TCP/IP connection that the IP address be changed from the factory default
address of 192.168.0.254 to the IP address to be assigned for the IED.
A serial connection to the Mx70 devices P1 service port can be used to obtain the IP
address from an Mx70 device. The service port operating with Hyperterminal allows the IP
address to be retrieved and changed by typing the ip command. You are prompted to enter
a new IP address.
During the configuration process you will enter the devices IP address. The IP address is
entered starting with the 70Series Configurator while in the Identity menu page. On the
Identity menu page, a radio button allows the user to select the source from which the IP
address (and SNTP addressing) will be loaded. The IP address can be obtained by either
loading it from the INI file or the MCL file.
If any change is made to the IP address by way
of the IEC 61850 IED Configurator, the IP address may not be written to the Mx70 devices
IDENTITY INI file. As a result, it is possible that the 70Series Configurator Identity page may
not indicate the actual IP address. It is always a good practice to determine the IP address
before the configuration process is initiated.
In order to communicate with an IEC 61850 device, it is necessary to know its Ethernet
address. This IP address can then be configured into either:
1.3.1
Mx7xI/EN M/J
Page 13
An IEC 61850 client (or master). For example a computer or Human Machine
Interface (HMI).
An MMS browser, with which the full data model can be retrieved from the IED.
Note that an MMS browser, such as SISCOs MMS Object Explorer, may be required
in order to browse and verify IEC 61850 objects that have been configured for the
Mx70 device.
Capability
The IEC 61850 interface provides the following capabilities:
1.
2.
3.
4.
Mx7xI/EN M/J
Page 14
70 series
5.
Setting changes are not supported in the current IEC 61850 implementation. In order to
keep this process as simple as possible, such setting changes would be done using the
70Series Configurator and the IEC 61850 IED Configurator (MiCOM S1 support software)
over the Ethernet link. A reboot of the device is necessary for the configuration to take effect
after changing any of the configurable parameters for an Mx70 device.
1.3.2
1.3.2.1
Configuration Banks
To promote version management and minimize down-time during system upgrades and
maintenance, the Mx70 devices utilize a storage mechanism consisting of multiple
configuration banks. These configuration banks are categorized as:
Inactive Configuration Bank (MC2 file is previous configuration file stored in E:\Config
on Mx70 device)
Any new configuration to the Mx70 device will be automatically stored into the inactive
configuration bank, therefore not immediately affecting the current configuration
When the upgrade or maintenance stage is complete, the 61850 IED Configurator tool will
prompt the user to make the configuration (to a single IED) active. A reboot of the Mx70
device is necessary in order for the configuration to be activated, authorizing the activation of
Mx7xI/EN M/J
70 series
Page 15
the new configuration contained in the inactive configuration bank, by switching the active
and inactive configuration banks. This technique ensures that the system down-time is
minimized while enabling the new configuration.
1.3.2.2
Network connectivity
NOTE:
Configuration of the relay IP parameters (IP Address, Subnet Mask, Gateway) and SNTP
time synchronization parameters (SNTP Server 1, SNTP Server 2, and polling interval) is
performed by the IED Configurator tool, so if these parameters are not available via an SCL
file, they must be configured manually.
If the assigned IP address is duplicated elsewhere on the same network, the remote
communications will operate in an indeterminate way. However, a check is performed for a
conflict on every IP configuration change and at power up. The Mx70 allows other devices
to perform duplicate IP address detection.
An Mx70 device can be configured to accept data from networks other than the local network
by using the Gateway setting.
1.4
1.5
1.6
When a device detects a change in one of its monitored status points it publishes (i.e. sends)
a new message. Any device that is interested in the information subscribes (i.e. listens) to
the data it contains.
Each new message is re-transmitted at user-configurable intervals until the maximum
interval is reached, in order to overcome possible corruption due to interference, and
congestion.
Mx7xI/EN M/J
Page 16
1.6.1
70 series
Scope (GOOSE messages)
In the Mx70 device database, a maximum of 32 GOOSE binary inputs, 32 GOOSE integer
inputs, and 32 GOOSE float (floating point) inputs are available to be mapped directly up to a
published dataset in a GOOSE message. All Mx70 published GOOSE signals may contain
BOOLEAN, Integer, and Float values. These signals are referred to by the following names:
GOOSE Analogue Input - AnIn# (floating point), where # will be a number between 132,
These inputs for a GOOSE message would be mapped in the IEC 61850 IED Configurator.
The 61850 IED Configurator tool is used to configure GOOSE publishing and GOOSE
subscribing. It is only possible to publish a GOOSE from System/LLN0.in the IEC 61850
IED Configurator. To subscribe to a GOOSE, use System/GosGGIO1 to configure the
GOOSE form the IEC 61850 IED Configurator tool.
Each GOOSE signal contained in a subscribed GOOSE message can be mapped to any of
the 32 GOOSE binary inputs, 32 GOOSE integer inputs, and 32 GOOSE float inputs. These
virtual inputs used by the GOOSE message allow the mapping to internal logic functions for
protection control, directly to output contacts, or to LEDs for monitoring.
Once the binary, integer, and analogue points are mapped in a particular application a
GOOSE message should be usable in order to cause trigger conditions for other devices
nd
IED is configured by
(e.g cross triggering between Mx70 devices), where a 2
programming a trigger condition expected to be contained in the dataset received in a
GOOSE message. When the trigger occurs (such as a binary state change) a GOOSE
message results, containing a dataset that can be mapped to the 2nd IEDs GOOSE inputs
(either the binary inputs, integer inputs, or analogue floating point inputs) and used to trigger
that IED on the network, based on the values or measurements contained in the dataset
The Mx70 IEDs can subscribe to all GOOSE messages but only the following data types can
be decoded and mapped to the inputs (binary, integer, and float) supported by the GOOSE.
BOOLEAN
BSTR2
INT16
INT32
INT8
INT16U
INT32U
INT8U
FLOAT32
SPS
DPS
Mx7xI/EN M/J
Page 17
1.7
Ethernet functionality
1.7.1
Ethernet disconnection
IEC 61850 associations are unique and made to the IED between the client (master) and
server (IEC 61850 device). In the event that the Ethernet is disconnected, such associations
are lost, and will need to be re-established by the client. The TCP_KEEPALIVE function is
implemented in Mx70 devices to monitor each association, and terminate any which are no
longer active.
1.7.2
Loss of power
Mx70 devices allow the re-establishment of associations by the client without a negative
impact on the IEDs operation after having its power removed. As the Mx70 device acts as a
server in this process, the client must request the association. When power is lost, reports
requested by connected clients are reset and must be re-enabled by the client when it next
creates the new association to the IED.
Mx7xI/EN M/J
Page 18
70 series
2.
2.1
Introduction
This section is the Protocol Implementation Conformance Statement (PICS) and presents
the ACSI conformance statements as defined in Annex A of Part 7-2 of the IEC 61850
standard.
The 70 Series IEC 61850 standard implementation shall conform to the Protocol
Implementation Conformance Statement below:
2.2
Server/
Publisher
Client-Server roles
B11
c1
B12
c1
SCSMs supported
B21
B22
B23
B24
SCSM: other
Publisher side
B32
Subscriber side
Publisher side
B42
Subscriber side
Value/Comments
Mx7xI/EN M/J
70 series
2.3
Page 19
ACSI models conformance statement
The ACSI models conformance statement shall be as defined in Table 2.
Client/
Subscriber
Server/
Publisher
Logical device
c2
c2
M2
Logical node
c3
c3
M3
Data
c4
c4
M4
Data set
c5
c5
M5
Substitution
M6
Reporting
M7
M7-1
sequence-number
M7-2
report-time-stamp
M7-3
reason-for-inclusion
M7-4
data-set-name
M7-5
data-reference
M7-6
buffer-overflow
M7-7
entryID
M7-8
BufTim
M7-9
IntgPd
M7-10
GI
M7-11
M8
entry)
O
M8-1
sequence-number
M8-2
report-time-stamp
M8-3
reason-for-inclusion
M8-4
data-set-name
M8-5
data-reference
M8-6
BufTim
M8-7
IntgPd
M8-8
GI
M8-9
entry)
Logging
M9
Log control
M9-1
M10
M11
IntgPd
Log
Control
GOOSE
M12-1
M12-2
entry)
row
entry)
M13
GSSE
Value/Comments
Mx7xI/EN M/J
Page 20
70 series
Client/
Subscriber
Server/
Publisher
M14
Multicast SVC
M15
Unicast SVC
M16
Time
M17
File Transfer
Value/Comments
AA:
TP/MC
Client/
Subscriber
Server/
Publisher
Server (clause 6)
S1
ServerDirectory
TP
Associate
S3
Abort
S4
Release
TP
LogicalDeviceDirectory
LogicalNodeDirectory
TP
S7
GetAllDataValues
TP
GetDataValues
TP
S9
SetDataValues
TP
S10
GetDataDirectory
TP
S11
GetDataDefinition
TP
Comments
Mx7xI/EN M/J
70 series
Page 21
Services
AA:
TP/MC
Client/
Subscriber
Server/
Publisher
GetDataSetValues
TP
S13
SetDataSetValues
TP
S14
CreateDataSet
TP
S15
DeleteDataSet
TP
S16
GetDataSetDirectory
TP
TP
SetDataValues
SelectActiveSG
TP
S19
SelectEditSG
TP
S20
SetSGValues
TP
S21
ConfirmEditSGValues
TP
S22
GetSGValues
TP
S23
GetSGCBValues
TP
TP
c6
c6
Report
S24-1
data-change (dchg)
S24-2
qchg-change (qchg)
S24-3
data-update (dupd)
S25
GetBRCBValues
TP
c6
c6
S26
SetBRCBValues
TP
c6
c6
TP
c6
c6
Report
S27-1
data-change (dchg)
S27-2
qchg-change (qchg)
S27-3
data-update (dup)
S28
GetURCBValues
TP
c6
c6
S29
SetURCBValues
TP
c6
c6
Comments
Mx7xI/EN M/J
Page 22
70 series
Services
AA:
TP/MC
Client/
Subscriber
Server/
Publisher
GetLCBValues
TP
S31
SetLCBValues
TP
S32
QueryLogByTime
TP
c7
S33
QueryLogAfter
TP
c7
S34
GetLogStatusValues
TP
Log
SendGOOSEMessage
MC
c8
c8
S36
GetGoReference
TP
c9
S37
GetGOOSEElementNumber
TP
c9
S38
GetGoCBValues
TP
S39
SetGoCBValues
TP
GSSE-CONTROL-BLOCK
S40
SendGSSEMessage
MC
c8
c8
S41
GetGsReference
TP
c9
S42
GetGSSEElementNumber
TP
c9
S43
GetGsCBValues
TP
S44
SetGsCBValues
TP
SendMSVMessage
MC
c10
c10
S46
GetMSVCBValues
TP
S47
SetMSVCBValues
TP
Unicast SVC
S48
SendUSVMessage
TP
c10
c10
S49
GetUSVCBValues
TP
S50
SetUSVCBValues
TP
Comments
Mx7xI/EN M/J
70 series
Page 23
Services
AA:
TP/MC
Client/
Subscriber
Server/
Publisher
Y
Y
Comments
Select
S52
SelectWithValue
TP
S53
Cancel
TP
S54
Operate
TP
S55
CommandTermination
TP
S56
TimeActivated-Operate
TP
GetFile
TP
S58
SetFile
TP
S59
DeleteFile
TP
S60
GetFileAttributeValues
TP
Time (5.5)
T1
T2
20 (1s)
nearest
negative
power of 2 in
seconds
T0
T1
14 (100s)
T2
T3
T4
T5
T3
20 (1s)
Nearest value
of 2**-n in
seconds
according to
5.5.3.7.3.3
Mx7xI/EN M/J
Page 24
70 series
3.
3.1
Introduction
This specification is the Model Implementation Conformance Statement (MICS) and presents
the top-level IEC 61850 data model that has been implemented. The definitions of all used
Logical Nodes and their associated Common Data Classes, components and associated
enumerated values are also included for completeness.
The reader is expected to be conversant with the terminology presented within the IEC
61850 part 7 series of specifications.
3.2
Objective
To provide comprehensive details of the standard data object model elements supported by
each one of the logical devices - M571, M572 (Dual Feeder), M572 (Breaker & ), M871,
M872 (Dual Feeder), and M872 (Breaker & .). The MICS is conformant to the devices
associated ICD (Substation Configuration Language) file, according to part 6 of the IEC
61850 standards. The layout of the presented tables within this document is conformant to
the Part 7 series of the IEC 61850 standard specifications with the following exceptions:
3.3
The "Trigger Options" field is not presented within the data object tables.
The "M/O" (Mandatory/Optional) field is not present in the data object tables, as the
definitions are as deployed within the models
An additional column "X" is used to signify Alstom Grid custom objects or attributes
Comment/Usage
Control
Measurements
Mx70 Series Measurements Domains: Measurement Domains are used for each
Measurements Logical Devices. The following list indicates the 6 types of 70 Series
Measurements Logical devices possible:
M571, M572 Dual Feeder, M572 Breaker &
M871, M872 Dual Feeder, M872 Breaker &
Protection
Records
System
Mx7xI/EN M/J
70 series
3.3.1
Page 25
IEC 61850 logical device data model
The IEC 61850 Logical Device top-level data model consists of instances of Logical Nodes.
The data model name for a Logical Node instance is constructed from an optional prefix
(known as the wrapper), the Logical Node name, and an instance ID (or suffix).
The data models for each of the logical devices are presented in this document. The logical
order is used to describe each of the physical devices. However, when it comes to the data
objects, data attributes and enumeration tables these are alphabetically sorted so that
searching is made easier.
The following Tables indicate the Logical Node Description Lists. The LN Types that are
used for all Mx70 measurement products are found in Tables 4-9. It is necessary to use the
LN Types indicated to create the mapping necessary for the LN Instance. There are
tables for each of the following: M571, M572 Dual Feeder, M572 Breaker & , M871, M872
Dual Feeder, and M872 Breaker & . LN Type is remapped to LN Instance in order to
define each Logical Node per the standard, IEC 61850 Part 7. Tables 4-9 define the logical
devices, while table 10 defines the LN Types.
NOTE:
Mx7xI/EN M/J
Page 26
LD
70 series
LN Instance
LN Type
Description
LLN0
LLN0_0
LPHD
LPHD_0
MMXU1
MMXU_10
Measurements
MMXU_11
FndMMXU1
MMXU_7
FndMMXU2
MMXU_8
DmdMMXU1
MMXU_1
DmdMMXU2
MMXU_2
DmnMMXU1
MMXU_3
DmnMMXU2
MMXU_2
DmxMMXU1
MMXU_1
DmxMMXU2
MMXU_2
FndDmdMMXU1
MMXU_5
FndDmxMMXU1
MMXU_5
MMTR1
MMTR_0
MSQI1
MSQI_0
MSQI2
MSQI_1
MHAI1
MHAI_2
MHAI2
MHAI_3
MHAI_0
DmdMHAI2
MHAI_1
DmnMHAI1
MHAI_1
DmnMHAI2
MHAI_1
DmxMHAI1
MHAI_0
DmxMHAI2
MHAI_1
MLFK1
MLFK_0
MLFK2
MLFK_0
MSYN1
MSYN_0
MSYN2
MSYN_0
MSYN3
MSYN_0
MADV1
MADV_0
MFLO1
MFLO_0
MTMP1
MTMP_0
Mx7xI/EN M/J
70 series
LD
Page 27
LN Instance
LN Type
Description
LLN0
LLN0_0
LPHD
LDHD_0
WrxRDRE1
RDRE_0
Waveform Recorder 1
WrxRDRE2
RDRE_0
Waveform Recorder 2
DrxRDRE1
RDRE_0
Disturbance Recorder 1
DrxRDRE2
RDRE_0
Disturbance Recorder 2
LLN0
LLN0_1
Measurements
Records
System
System Logical Device
Can only Publish GOOSE in System/LLN0
LPHD
LPHD_0
GosGGIO1
GGIO_8
TVTR1
TVTR_0
TVTR2
TVTR_0
TVTR3
TVTR_0
TVTR4
TVTR_0
TVTR5
TVTR_0
TVTR6
TVTR_0
TVTR7
TVTR_0
TVTR8
TVTR_0
TCTR1
TCTR_0
TCTR2
TCTR_0
TCTR3
TCTR_0
No GGIO option
No GGIO option
Choose option
based on logical
slot configuration
GGIO1
GGIO_0
Choose option
based on logical
slot configuration
GGIO1
Choose option
based on logical
slot configuration
GGIO1
GGIO_3
GGIO_6
GGIO2
GGIO_9
TABLE 3 - M571
Mx7xI/EN M/J
Page 28
LD
70 series
LN Instance
LN Type
Description
LLN0
LLN0_0
LPHD
LPHD_0
MMXU1
MMXU_10
Measurements
MMXU_10
MMXN1
MMXN_0
MMXN2
MMXN_0
FndMMXU1
MMXU_7
FndMMXU2
MMXU_7
DmdMMXU1
MMXU_1
DmdMMXU2
MMXU_1
DmnMMXU1
MMXU_3
DmnMMXU2
MMXU_3
DmxMMXU1
MMXU_1
DmxMMXU2
MMXU_1
FndDmdMMXU1
MMXU_5
FndDmdMMXU2
MMXU_5
FndDmxMMXU1
MMXU_5
FndDmxMMXU2
MMXU_5
MMTR1
MMTR_0
MMTR2
MMTR_0
MSQI1
MSQI_0
MSQI2
MSQI_0
MHAI1
MHAI_2
MHAI2
MHAI_2
DmdMHAI1
MHAI_0
DmdMHAI2
MHAI_0
DmnMHAI1
MHAI_1
DmnMHAI2
MHAI_1
DmxMHAI1
MHAI_0
DmxMHAI2
MHAI_0
MLFK1
MLFK_0
MLFK2
MLFK_0
Mx7xI/EN M/J
70 series
LD
Page 29
LN Instance
LN Type
Description
MSYN1
MSYN_0
MSYN2
MSYN_0
MSYN3
MSYN_0
MSYN4
MSYN_0
MSYN5
MSYN_0
MSYN6
MSYN_0
MADV1
MADV_0
MADV2
MADV_0
MFLO1
MFLO_0
MFLO2
MFLO_0
MTMP1
MTMP_0
LLN0
LLN0_0
LPHD
LDHD_0
WrxRDRE1
RDRE_0
Waveform Recorder 1
WrxRDRE2
RDRE_0
Waveform Recorder 2
DrxRDRE1
RDRE_0
Disturbance Recorder 1
DrxRDRE2
RDRE_0
Disturbance Recorder 2
LLN0
LLN0_1
Measurements
Records
System
LPHD_0
GosGGIO1
GGIO_8
TVTR1
TVTR_0
TVTR2
TVTR_0
TVTR3
TVTR_0
TVTR4
TVTR_0
TVTR5
TVTR_0
TVTR6
TVTR_0
TVTR7
TVTR_0
TVTR8
TVTR_0
TVTR9
TVTR_0
TVTR10
TVTR_0
TCTR1
TCTR_0
TCTR2
TCTR_0
TCTR3
TCTR_0
TCTR5
TCTR_0
TCTR6
TCTR_0
TCTR7
TCTR_0
Mx7xI/EN M/J
Page 30
70 series
LD
LN Instance
LN Type
Description
Measurements
System
Choose option
based on logical
slot configuration
No GGIO option
No GGIO option
Choose option
based on logical
slot configuration
GGIO1
GGIO_0
Choose option
based on logical
slot configuration
GGIO1
Choose option
based on logical
slot configuration
GGIO1
GGIO_3
GGIO_6
GGIO2
GGIO_9
Mx7xI/EN M/J
70 series
LD
Page 31
LN Instance
LN Type
Description
LLN0
LLN0_0
LPHD
LPHD_0
MMXU1
MMXU_10
Measurements
MMXU_10
FndMMXU1
MMXU_7
FndMMXU2
MMXU_7
DmdMMXU1
MMXU_1
DmdMMXU2
MMXU_1
DmnMMXU1
MMXU_3
DmnMMXU2
MMXU_3
DmxMMXU1
MMXU_1
DmxMMXU2
MMXU_1
FndDmdMMXU1
MMXU_5
FndDmdMMXU2
MMXU_5
FndDmxMMXU1
MMXU_5
FndDmxMMXU2
MMXU_5
MMTR1
MMTR_0
MMTR2
MMTR_0
MSQI_0
MSQI2
MSQI_0
MHAI1
MHAI_2
MHAI2
MHAI_2
DmdMHAI1
MHAI_0
DmdMHAI2
MHAI_0
DmnMHAI1
MHAI_1
DmnMHAI2
MHAI_1
DmxMHAI1
MHAI_0
DmxMHAI2
MHAI_0
MLFK1
MLFK_0
MLFK2
MLFK_0
MSYN1
MSYN_0
Mx7xI/EN M/J
Page 32
LD
70 series
LN Instance
LN Type
Description
MSYN2
MSYN_0
MSYN3
MSYN_0
MADV1
MADV_0
MADV2
MADV_0
MFLO1
MFLO_0
MFLO2
MFLO_0
MTMP1
MTMP_0
LLN0
LLN0_0
LPHD
LDHD_0
WrxRDRE1
RDRE_0
Waveform Recorder 1
WrxRDRE2
RDRE_0
Waveform Recorder 2
DrxRDRE1
RDRE_0
Disturbance Recorder 1
DrxRDRE2
RDRE_0
Disturbance Recorder 2
LLN0
LLN0_1
Measurements
Records
System
LPHD_0
GosGGIO1
GGIO_8
TVTR1
TVTR_0
TVTR2
TVTR_0
TVTR3
TVTR_0
TVTR4
TVTR_0
TVTR5
TVTR_0
TVTR6
TVTR_0
TVTR7
TVTR_0
TVTR8
TVTR_0
TCTR1
TCTR_0
TCTR2
TCTR_0
TCTR3
TCTR_0
TCTR5
TCTR_0
TCTR6
TCTR_0
TCTR7
TCTR_0
Mx7xI/EN M/J
70 series
Page 33
LD
LN Instance
LN Type
Description
Measurements
System
Choose option
based on logical
slot configuration
No GGIO option
No
GGIO
option
Choose option
based on logical
slot configuration
GGIO1
GGIO_0
Choose option
based on logical
slot configuration
GGIO1
Choose option
based on logical
slot configuration
GGIO1
GGIO_3
GGIO_6
GGIO2
GGIO_9
Mx7xI/EN M/J
Page 34
LD
70 series
LN Instance
LN Type
Description
LLN0
LNN0_0
LPHD
LPHD_0
MMXU1
MMXU_9
Measurements
MMXU_11
MMXN1
MMXN_0
MMXN2
MMXN_0
MMXN3
MMXN_0
FndMMXU1
MMXU_6
FndMMXU2
MMXU_8
DmdMMXU1
MMXU_0
DmdMMXU2
MMXU_2
DmnMMXU1
MMXU_3
DmnMMXU2
MMXU_2
DmxMMXU1
MMXU_0
DmxMMXU2
MMXU_2
FndDmdMMXU1
MMXU_4
FndDmxMMXU1
MMXU_4
MMTR1
MMTR_0
MSQI_0
MSQI2
MSQI_1
MHAI1
MHAI_2
MHAI2
MHAI_3
DmdMHAI1
MHAI_0
DmdMHAI2
MHAI_1
DmnMHAI1
MHAI_1
DmnMHAI2
MHAI_1
DmxMHAI1
MHAI_0
DmxMHAI2
MHAI_1
MLFK1
MLFK_0
MLFK2
MLFK_0
MSYN1
MSYN_0
MSYN2
MSYN_0
MSYN3
MSYN_0
MADV1
MADV_0
Mx7xI/EN M/J
70 series
LD
Page 35
LN Instance
LN Type
Description
MFLO1
MFLO_0
MTMP1
MTMP_0
LLN0
LLN0_0
LPHD
LDHD_0
WrxRDRE1
RDRE_0
Waveform Recorder 1
WrxRDRE2
RDRE_0
Waveform Recorder 2
DrxRDRE1
RDRE_0
Disturbance Recorder 1
DrxRDRE2
RDRE_0
Disturbance Recorder 2
LLN0
LLN0_1
Measurements
Records
System
System Logical Device
Can only Publish GOOSE in System/LLN0
LPHD
LPHD_0
GosGGIO1
GGIO_8
TVTR1
TVTR_0
TVTR2
TVTR_0
TVTR3
TVTR_0
TVTR4
TVTR_0
TVTR5
TVTR_0
TVTR6
TVTR_0
TVTR7
TVTR_0
TVTR8
TVTR_0
TVTR9
TVTR_0
TVTR10
TVTR_0
TVTR11
TVTR_0
TCTR1
TCTR_0
TCTR2
TCTR_0
TCTR3
TCTR_0
TCTR4
TCTR_0
Mx7xI/EN M/J
Page 36
System
70 series
I/O Options (GGIO Logical slot numbers may range from 1 -7).
No GGIO option
No GGIO option
GGIOx
GGIO_1
GGIOx
GGIOx
GGIOx
GGIOx
(see Note 1)
GGIO_2
(see Note 1)
GGIO_4
(see Note 1)
GGIO_5
(see Note 1)
GGIO_7
(see Note 1)
GGIO2
GGIO_9
TABLE 6 - M871
Mx7xI/EN M/J
70 series
LD
Page 37
LN Instance
LN Type
Description
LLN0
LLN0_0
LPHD
LPHD_0
MMXU1
MMXU_10
Measurements
MMXU_10
MMXN1
MMXN_0
MMXN2
MMXN_0
FndMMXU1
MMXU_7
FndMMXU2
MMXU_7
DmdMMXU1
MMXU_1
DmdMMXU2
MMXU_1
DmnMMXU1
MMXU_3
DmnMMXU2
MMXU_3
DmxMMXU1
MMXU_1
DmxMMXU2
MMXU_1
FndDmdMMXU1
MMXU_5
FndDmdMMXU2
MMXU_5
FndDmxMMXU1
MMXU_5
FndDmxMMXU2
MMXU_5
MMTR1
MMTR_0
MMTR2
MMTR_0
MSQI1
MSQI_0
MSQI2
MSQI_0
MHAI1
MHAI_2
MHAI2
MHAI_2
DmdMHAI1
MHAI_0
DmdMHAI2
MHAI_0
DmnMHAI1
MHAI_1
DmnMHAI2
MHAI_1
DmxMHAI1
MHAI_0
DmxMHAI2
MHAI_0
MLFK1
MLFK_0
MLFK2
MLFK_0
MSYN1
MSYN_0
Mx7xI/EN M/J
Page 38
LD
70 series
LN Instance
LN Type
Description
MSYN2
MSYN_0
MSYN3
MSYN_0
MSYN4
MSYN_0
MSYN5
MSYN_0
MSYN6
MSYN_0
MADV1
MADV_0
MADV2
MADV_0
MFLO1
MFLO_0
Measurements
MFLO2
MFLO_0
MTMP1
MTMP_0
LLN0
LLN0_0
LPHD
LDHD_0
WrxRDRE1
RDRE_0
Waveform Recorder 1
WrxRDRE2
RDRE_0
Waveform Recorder 2
DrxRDRE1
RDRE_0
Disturbance Recorder 1
DrxRDRE2
RDRE_0
Disturbance Recorder 2
LLN0
LLN0_1
Records
System
LPHD_0
GosGGIO1
GGIO_8
TVTR1
TVTR_0
TVTR2
TVTR_0
TVTR3
TVTR_0
TVTR4
TVTR_0
TVTR5
TVTR_0
TVTR6
TVTR_0
TVTR7
TVTR_0
TVTR8
TVTR_0
TVTR9
TVTR_0
TVTR10
TVTR_0
TCTR1
TCTR_0
TCTR2
TCTR_0
TCTR3
TCTR_0
TCTR5
TCTR_0
TCTR6
TCTR_0
TCTR7
TCTR_0
Mx7xI/EN M/J
70 series
System
Page 39
I/O Options (GGIO Logical slot numbers may range from 1-7).
Choose option
based on logical
slot configuration
No GGIO option
No GGIO option
Choose option
based on logical
slot configuration
GGIOx
GGIO_1
Choose option
based on logical
slot configuration
GGIOx
Choose option
based on logical
slot configuration
GGIOx
Choose option
based on logical
slot configuration
GGIOx
Choose option
based on logical
slot configuration
GGIOx
(see Note 1)
(see Note 1)
GGIO_4
(see Note 1)
GGIO_5
(see Note 1)
GGIO_7
(see Note 1)
GGIO2
GGIO_9
Mx7xI/EN M/J
Page 40
LD
70 series
LN Instance
LN Type
Description
LLN0
LLN0_0
LPHD
LPHD_0
MMXU1
MMXU_10
Measurements
MMXU_10
FndMMXU1
MMXU_7
FndMMXU2
MMXU_7
DmdMMXU1
MMXU_1
DmdMMXU2
MMXU_1
DmnMMXU1
MMXU_3
DmnMMXU2
MMXU_3
DmxMMXU1
MMXU_1
DmxMMXU2
MMXU_1
FndDmdMMXU1
MMXU_5
FndDmdMMXU2
MMXU_5
FndDmxMMXU1
MMXU_5
FndDmxMMXU2
MMXU_5
MMTR1
MMTR_0
MMTR2
MMTR_0
MSQI_0
MSQI2
MSQI_0
MHAI1
MHAI_2
MHAI2
MHAI_2
DmdMHAI1
MHAI_0
DmdMHAI2
MHAI_0
DmnMHAI1
MHAI_1
DmnMHAI2
MHAI_1
DmxMHAI1
MHAI_0
DmxMHAI2
MHAI_0
MLFK1
MLFK_0
MLFK2
MLFK_0
MSYN1
MSYN_0
MSYN2
MSYN_0
Mx7xI/EN M/J
70 series
LD
Page 41
LN Instance
LN Type
Description
MSYN3
MSYN_0
MADV1
MADV_0
MADV2
MADV_0
MFLO1
MFLO_0
MFLO2
MFLO_0
MTMP1
MTMP_0
LLN0
LLN0_0
LPHD
LDHD_0
WrxRDRE1
RDRE_0
Waveform Recorder 1
WrxRDRE2
RDRE_0
Waveform Recorder 2
DrxRDRE1
RDRE_0
Disturbance Recorder 1
DrxRDRE2
RDRE_0
Disturbance Recorder 2
LLN0
LLN0_1
Measurements
Records
System
System Logical Device
Can only Publish GOOSE in System/LLN0
LPHD
LPHD_0
GosGGIO1
GGIO_8
TVTR1
TVTR_0
TVTR2
TVTR_0
TVTR3
TVTR_0
TVTR4
TVTR_0
TVTR5
TVTR_0
TVTR6
TVTR_0
TVTR7
TVTR_0
TVTR8
TVTR_0
TCTR1
TCTR_0
TCTR2
TCTR_0
TCTR3
TCTR_0
TCTR5
TCTR_0
TCTR6
TCTR_0
TCTR7
TCTR_0
Mx7xI/EN M/J
Page 42
System
70 series
I/O Options (GGIO Logical slot numbers may range from 1 -7).
Choose option
based on logical
slot configuration
No GGIO option
No GGIO option
Choose option
based on logical
slot configuration
GGIOx
GGIO_1
Choose option
based on logical
slot configuration
GGIOx
Choose option
based on logical
slot configuration
GGIOx
Choose option
based on logical
slot configuration
GGIOx
Choose option
based on logical
slot configuration
GGIOx
(see Note 1)
(see Note 1)
GGIO_4
(see Note 1)
GGIO_5
(see Note 1)
GGIO_7
(see Note 1)
GGIO2
GGIO_9
/8AI
Mx7xI/EN M/J
70 series
3.4
Page 43
Logical Node definitions
The definition tables for each of the Logical Nodes in the top-level data model are presented
in the following sub-sections.
The following table presents a summary of the Logical Node templates used across the
Logical Devices within the overall IEC 61850 product data model:
LN Type
(LN Class)
Description
Name Space
GGIO_0
(GGIO)
IEC 61850-7-4:2003
GGIO_1
(GGIO)
IEC 61850-7-4:2003
GGIO_2
(GGIO)
IEC 61850-7-4:2003
GGIO_3
(GGIO)
IEC 61850-7-4:2003
GGIO_4
(GGIO)
IEC 61850-7-4:2003
GGIO_5
(GGIO)
IEC 61850-7-4:2003
GGIO-6
(GGIO)
IEC 61850-7-4:2003
GGIO_7
(GGIO)
IEC 61850-7-4:2003
GGIO_8
(GGIO)
IEC 61850-7-4:2003
GGIO_9
(GGIO)
IEC 61850-7-4:2003
LLN0_0
(LLN0)
IEC 61850-7-4:2003
LLN0_1
(LLN0)
IEC 61850-7-4:2003
LPHD_0
(LPHD)
IEC 61850-7-4:2003
MADV_0
(MADV)
Advanced Measurements
Bitronics NS
Not Standard
Flicker measurements
Bitronics NS
Not Standard
Bitronics NS
Not Standard
MFLK_0
MFLO_0
(MFLK)
(MFLO)
MHAI_0
(MHAI)
IEC 61850-7-4:2003
MHAI_1
(MHAI)
IEC 61850-7-4:2003
MHAI_2
(MHAI)
IEC 61850-7-4:2003
(MHAI)
IEC 61850-7-4:2003
(MMTR)
Energy measurements
(Provides for acquiring of polyphase metering values
pertaining to a field device or circuit.)
(LN is extended to include custom measurements)
IEC 61850-7-4:2003
Mx7xI/EN M/J
Page 44
70 series
LN Type
(LN Class)
Description
Name Space
MMXN_0
(MMXN)
IEC 61850-7-4:2003
MMXU_0
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
Standard Measurements:
Fundamental (Fourier) values Bus 1 (M871)
(Provides measurements of single phase or polyphase
analogue values pertaining to a wye or delta connected field
device or circuit.)
IEC 61850-7-4:2003
Mx7xI/EN M/J
70 series
Page 45
LN Type
(LN Class)
Description
Name Space
MMXU_7
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
Standard Measurements:
IEC 61850-7-4:2003
(MMXU)
IEC 61850-7-4:2003
(MMXU)
Standard measurements
IEC 61850-7-4:2003
(MMXU)
IEC 61850-7-4:2003
(MSQI)
IEC 61850-7-4:2003
(MSQI)
IEC 61850-7-4:2003
(MSYN)
Synchronism check
Bitronics NS
Not Standard
(MTMP)
Not Standard
RDRE_0
(RDRE)
IEC 61850-7-4:2003
TCTR_0
TCTR
IEC 61850-7-4:2003
TVTR_0
TVTR
IEC 61850-7-4:2003
Bitronics NS
Mx7xI/EN M/J
Page 46
3.4.1
70 series
Logical Node: GGIO_0
Description:
Generic Process I/O M57x with option of 4 Digital Inputs / 4 Digital Outputs
LN Class:
GGIO
Attribute
3.4.2
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
SPCSO1
SPC_3
Digital Output 1
SPCSO2
SPC_3
Digital Output 2
SPCSO3
SPC_3
Digital Output 3
SPCSO4
SPC_3
Digital Output 4
Ind1
SPS_0
Digital Input 1
Ind2
SPS_0
Digital Input 2
Ind3
SPS_0
Digital Input 3
Ind4
SPS_0
Digital Input 4
Generic Process I/O M87x with option of 8 Digital Inputs/4 Digital Outputs
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
SPCSO1
SPC_3
Digital Output 1
SPCSO2
SPC_3
Digital Output 2
SPCSO3
SPC_3
Digital Output 3
SPCSO4
SPC_3
Digital Output 4
Ind1
SPS_0
Digital Input 1
Ind2
SPS_0
Digital Input 2
Ind3
SPS_0
Digital Input 3
Ind4
SPS_0
Digital Input 4
Ind5
SPS_0
Digital Input 5
Ind6
SPS_0
Digital Input 6
Ind7
SPS_0
Digital Input 7
Ind8
SPS_0
Digital Input 8
Mx7xI/EN M/J
70 series
3.4.3
Page 47
Logical Node: GGIO_2
Description:
Generic Process I/O M87x with option of 16 Digital inputs/4 Digital outputs
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
SPCSO1
SPC_3
Digital Output 1
SPCSO2
SPC_3
Digital Output 2
SPCSO3
SPC_3
Digital Output 3
SPCSO4
SPC_3
Digital Output 4
Ind1
SPS_0
Digital Input 1
Ind2
SPS_0
Digital Input 2
Ind3
SPS_0
Digital Input 3
Ind4
SPS_0
Digital Input 4
Ind5
SPS_0
Digital Input 5
Ind6
SPS_0
Digital Input 6
Ind7
SPS_0
Digital Input 7
Ind8
SPS_0
Digital Input 8
Ind9
SPS_0
Digital Input 9
Ind10
SPS_0
Digital Input 10
Ind11
SPS_0
Digital Input 11
Ind12
SPS_0
Digital Input 12
Ind13
SPS_0
Digital Input 13
Ind14
SPS_0
Digital Input 14
Ind15
SPS_0
Digital Input 15
Ind16
SPS_0
Digital Input 16
Mx7xI/EN M/J
Page 48
3.4.4
70 series
Logical Node: GGIO_3
Description:
Generic Process I/O M57x with option of 4 Digital Inputs/ 4 Digital Outputs/ 4
Analogue Inputs
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
AnIn1
MV_0
Analogue input 1
AnIn 2
MV_0
Analogue input 2
AnIn 3
MV_0
Analogue input 3
AnIn 4
MV_0
Analogue input 4
SPCSO1
SPC_3
Digital Output 1
SPCSO2
SPC_3
Digital Output 2
SPCSO3
SPC_3
Digital Output 3
SPCSO4
SPC_3
Digital Output 4
Ind1
SPS_0
Digital Input 1
Ind2
SPS_0
Digital Input 2
Ind3
SPS_0
Digital Input 3
Ind4
SPS_0
Digital Input 4
Mx7xI/EN M/J
70 series
3.4.5
Page 49
Logical Node: GGIO_4
Description:
Generic Process I/O M87x with options of 8 Digital inputs / 4 Digital outputs /
8 Analogue inputs
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
AnIn1
MV_0
Analogue input 1
AnIn 2
MV_0
Analogue input 2
AnIn 3
MV_0
Analogue input 3
AnIn 4
MV_0
Analogue input 4
AnIn5
MV_0
Analogue input 5
AnIn 6
MV_0
Analogue input 6
AnIn 7
MV_0
Analogue input 7
AnIn 8
MV_0
Analogue input 8
SPCSO1
SPC_3
Digital Output 1
SPCSO2
SPC_3
Digital Output 2
SPCSO3
SPC_3
Digital Output 3
SPCSO4
SPC_3
Digital Output 4
Ind1
SPS_0
Digital Input 1
Ind2
SPS_0
Digital Input 2
Ind3
SPS_0
Digital Input 3
Ind4
SPS_0
Digital Input 4
Ind5
SPS_0
Digital Input 5
Ind6
SPS_0
Digital Input 6
Ind7
SPS_0
Digital Input 7
Ind8
SPS_0
Digital Input 8
Mx7xI/EN M/J
Page 50
3.4.6
70 series
Logical Node: GGIO_5
Description:
Generic Process I/O M87x with options of 16 Digital inputs / 4 Digital outputs
/ 8 Analogue inputs
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
AnIn 1
MV_0
Analogue input 1
AnIn 2
MV_0
Analogue input 2
AnIn 3
MV_0
Analogue input 3
AnIn 4
MV_0
Analogue input 4
AnIn 5
MV_0
Analogue input 5
AnIn 6
MV_0
Analogue input 6
AnIn 7
MV_0
Analogue input 7
AnIn 8
MV_0
Analogue input 8
SPCSO1
SPC_3
Digital Output 1
SPCSO2
SPC_3
Digital Output 2
SPCSO3
SPC_3
Digital Output 3
SPCSO4
SPC_3
Digital Output 4
Ind1
SPS_0
Digital Input 1
Ind2
SPS_0
Digital Input 2
Ind3
SPS_0
Digital Input 3
Ind4
SPS_0
Digital Input 4
Ind5
SPS_0
Digital Input 5
Ind6
SPS_0
Digital Input 6
Ind7
SPS_0
Digital Input 7
Ind8
SPS_0
Digital Input 8
Ind9
SPS_0
Digital Input 9
Ind10
SPS_0
Digital Input 10
Ind11
SPS_0
Digital Input 11
Ind12
SPS_0
Digital Input 12
Ind13
SPS_0
Digital Input 13
Ind14
SPS_0
Digital Input 14
Ind15
SPS_0
Digital Input 15
Ind16
SPS_0
Digital Input 16
Mx7xI/EN M/J
70 series
3.4.7
Page 51
Logical Node: GGIO_6
Description:
LN Class:
GGIO
Attribute
3.4.8
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
AnIn 1
MV_0
Analogue input 1
AnIn 2
MV_0
Analogue input 2
AnIn 3
MV_0
Analogue input 3
AnIn 4
MV_0
Analogue input 4
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
AnIn 1
MV_0
Analogue input 1
AnIn 2
MV_0
Analogue input 2
AnIn 3
MV_0
Analogue input 3
AnIn 4
MV_0
Analogue input 4
AnIn 5
MV_0
Analogue input 5
AnIn 6
MV_0
Analogue input 6
AnIn 7
MV_0
Analogue input 7
AnIn 8
MV_0
Analogue input 8
Mx7xI/EN M/J
Page 52
3.4.9
70 series
Logical Node: GGIO_8
Description:
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
AnIn 1
MV_1
AnIn 2
MV_1
AnIn 3
MV_1
AnIn 4
MV_1
AnIn 5
MV_1
AnIn 6
MV_1
AnIn 7
MV_1
AnIn 8
MV_1
AnIn 9
MV_1
AnIn 10
MV_1
AnIn 11
MV_1
AnIn 12
MV_1
AnIn 13
MV_1
AnIn 14
MV_1
AnIn 15
MV_1
AnIn 16
MV_1
AnIn 17
MV_1
AnIn 18
MV_1
AnIn 19
MV_1
AnIn 20
MV_1
AnIn 21
MV_1
AnIn 22
MV_1
AnIn 23
MV_1
AnIn 24
MV_1
AnIn 25
MV_1
AnIn 26
MV_1
AnIn 27
MV_1
AnIn 28
MV_1
AnIn 29
MV_1
AnIn 30
MV_1
AnIn 31
MV_1
AnIn 32
MV_1
IntIn1
INS_3
IntIn2
INS_3
IntIn3
INS_3
IntIn4
INS_3
IntIn5
INS_3
Mx7xI/EN M/J
70 series
Page 53
Attribute
Attr. Type
Explanation
IntIn6
INS_3
IntIn7
INS_3
IntIn8
INS_3
IntIn9
INS_3
IntIn10
INS_3
IntIn11
INS_3
IntIn12
INS_3
IntIn13
INS_3
IntIn14
INS_3
IntIn15
INS_3
IntIn16
INS_3
IntIn17
INS_3
IntIn18
INS_3
IntIn19
INS_3
IntIn20
INS_3
IntIn21
INS_3
IntIn22
INS_3
IntIn23
INS_3
IntIn24
INS_3
IntIn25
INS_3
IntIn26
INS_3
IntIn27
INS_3
IntIn28
INS_3
IntIn29
INS_3
IntIn30
INS_3
IntIn31
INS_3
IntIn32
INS_3
Ind1
SPS_0
Ind2
SPS_0
Ind3
SPS_0
Ind4
SPS_0
Ind5
SPS_0
Ind6
SPS_0
Ind7
SPS_0
Ind8
SPS_0
Ind9
SPS_0
Ind10
SPS_0
Ind11
SPS_0
Ind12
SPS_0
Ind13
SPS_0
Ind14
SPS_0
Ind15
SPS_0
Ind16
SPS_0
Ind17
SPS_0
Ind18
SPS_0
Mx7xI/EN M/J
Page 54
3.4.10
70 series
Attribute
Attr. Type
Explanation
Ind19
SPS_0
Ind20
SPS_0
Ind21
SPS_0
Ind22
SPS_0
Ind23
SPS_0
Ind24
SPS_0
Ind25
SPS_0
Ind26
SPS_0
Ind27
SPS_0
Ind28
SPS_0
Ind29
SPS_0
Ind30
SPS_0
Ind31
SPS_0
Ind32
SPS_0
LN Class:
GGIO
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Ind1
SPS_0
Ind2
SPS_0
Ind3
SPS_0
Ind4
SPS_0
Ind5
SPS_0
Ind6
SPS_0
Ind7
SPS_0
Ind8
SPS_0
Ind9
SPS_0
Ind10
SPS_0
Ind11
SPS_0
Ind12
SPS_0
Ind13
SPS_0
Ind14
SPS_0
Ind15
SPS_0
Ind16
SPS_0
Ind17
SPS_0
Ind18
SPS_0
Ind19
SPS_0
Ind20
SPS_0
Mx7xI/EN M/J
70 series
3.4.11
3.4.12
Page 55
Attribute
Attr. Type
Explanation
Ind21
SPS_0
Ind22
SPS_0
Ind23
SPS_0
Ind24
SPS_0
Ind25
SPS_0
Ind26
SPS_0
Ind27
SPS_0
Ind28
SPS_0
Ind29
SPS_0
Ind30
SPS_0
Ind31
SPS_0
Ind32
SPS_0
LN Class:
LLN0
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_1
Name Plate
LN Class:
LLN0
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_1
Name Plate
Mx7xI/EN M/J
Page 56
3.4.13
70 series
Logical Node: LPHD_0
Description:
LN Class:
LPHD
Attribute
3.4.14
Attr. Type
Explanation
PhyNam
DPL_0
PhyHealth
INS_2
Proxy
SPS_0
NumPwrUp
INS_3
WrmStr
INS_3
WacTrg
INS_3
Logical Node: MADV_0 (Custom LN not contained in IEC 61850 part 7-4 definitions)
Description:
Advanced Measurements
LN Class:
MADV (Custom LN Class not contained in IEC 61850 part 7-4 definitions)
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_0
Health
NamPlt
LPL_2
Name Plate
TotVAa
MV_0
TotVAv
MV_0
TotVAaFund
MV_0
TotVAvFund
MV_0
TotPFa
MV_0
TotPFv
MV_0
DF
WYE_1
TotDFa
MV_0
TotDFv
MV_0
Ires
MV_0
Residual current
Mx7xI/EN M/J
70 series
3.4.15
Page 57
Logical Node: MLFK_0 (Custom LN not contained in IEC 61850 part 7-4 definitions)
Description:
Flicker Measurements
LN Class:
MFLK (Custom LN Class not contained in IEC 61850 part 7-4 definitions)
This LN shall be used for calculation of flicker including voltage fluctuations according to IEC
Standard 61000-4-15. The main use is for operative applications
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_0
Health
NamPlt
LPL_2
Name Plate
Pst
DEL_0
DEL_0
DEL_0
NOTE:
3.4.16
Logical Node: MLFO_0 (Custom LN not contained in IEC 61850 part 7-4 definitions)
Description:
LN Class:
MFLO (Custom LN Class not contained in IEC 61850 part 7-4 definitions)
This LN shall be used for calculation of flicker including voltage fluctuations according to IEC
Standard 61000-4-15. The main use is for operative applications
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_0
Health
NamPlt
LPL_2
Name Plate
FltDiskm
MV_0
Fault Distance
(Use the 70Series Configurator to program the unit of
measure. IEC 61850 protocol has standardized on a unit of
measure in kilometers If during configuration another unit
of measure is programmed the user, then the value for
Farult Distance will be measured in that unit of measure.)
Mx7xI/EN M/J
Page 58
3.4.17
3.4.18
70 series
Logical Node: MHAI_0
Description:
LN Class:
MHAI
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TddA
WYE_0
ThdPhV
WYE_1
ThdPPV
DEL_0
LN Class:
MHAI
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
ThdPhV
WYE_1
ThdPPV
DEL_0
Mx7xI/EN M/J
70 series
3.4.19
Page 59
Logical Node: MHAI_2
Description:
LN Class:
MHAI
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Hz
MV_0
Basic Frequency
HA
HWYE_0
HPhV
HWYE_0
HPPV
HDEL_0
HKf
WYE_0
TddA
WYE_0
TddOddA
WYE_0
TddEvnA
WYE_0
ThdPhV
WYE_1
ThdOddPhV
WYE_1
ThdEvnPhV
WYE_1
ThdPPV
DEL_0
ThdOddPPV
DEL_0
ThdEvnPPV
DEL_0
NomA1
ASG_0
NomA2
ASG_0
NomA3
ASG_0
DmdIntH
ASG_1
RsDmdH
SPC_0
Mx7xI/EN M/J
Page 60
3.4.20
3.4.21
70 series
Logical Node: MHAI_3
Description:
LN Class:
MHAI
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Hz
MV_0
Basic Frequency
HPhV
HWYE_0
HPPV
HDEL_0
ThdPhV
WYE_1
ThdOddPhV
WYE_1
ThdEvnPhV
WYE_1
ThdPPV
DEL_0
ThdOddPPV
DEL_0
ThdEvnPPV
DEL_0
DmdIntH
ASG_1
RsDmdH
SPC_0
Energy measurements
LN Class:
MMTR
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotVAh
BCR_0
SupWh
BCR_0
SupVArh
BCR_0
DmdWh
BCR_0
DmdVArh
BCR_0
RsEnergy
SPC_0
Reset Energy
Mx7xI/EN M/J
70 series
3.4.22
3.4.23
Page 61
Logical Node: MMXN_0
Description:
LN Class:
MMXN_0
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Vol
MV_0
LN Class:
Bus 1 (M871)
Bus 1 (M871)
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotW
MV_0
TotVAr
MV_0
TotVA
MV_0
PPV
DEL_0
PhV
WYE_2
WYE_3
WYE_1
VAr
WYE_1
VA
WYE_1
Mx7xI/EN M/J
Page 62
3.4.24
70 series
Logical Node: MMXU_1
Description:
Standard measurements
Present Thermal Demands -
3.4.25
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotW
MV_0
TotVAr
MV_0
TotVA
MV_0
PPV
DEL_0
PhV
WYE_2
WYE_0
WYE_1
VAr
WYE_1
VA
WYE_1
LN Class:
Standard measurements
Present Thermal Demands,
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
PPV
DEL_0
PhV
WYE_2
Mx7xI/EN M/J
70 series
3.4.26
Page 63
Logical Node: MMXU_3
Description:
LN Class:
3.4.27
Standard measurements
Minimum Thermal Demands,
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotW
MV_0
TotVAr
MV_0
TotVA
MV_0
PPV
DEL_0
PhV
WYE_2
WYE_1
VAr
WYE_1
VA
WYE_1
Standard measurements
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
WYE_3
Mx7xI/EN M/J
Page 64
3.4.28
70 series
Logical Node: MMXU_5
Description:
Standard measurements
LN Class:
3.4.29
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
WYE_0
LN Class:
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotW
MV_0
TotVAr
MV_0
TotVA
MV_0
TotPF
MV_0
Hz
MV_0
Frequency
PPV
DEL_0
PhV
WYE_1
WYE_3
WYE_1
VAr
WYE_1
VA
WYE_1
PF
WYE_1
Mx7xI/EN M/J
70 series
3.4.30
3.4.31
Page 65
Logical Node: MMXU_7
Description:
LN Class:
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotW
MV_0
TotVAr
MV_0
TotVA
MV_0
TotPF
MV_0
Hz
MV_0
Frequency
PPV
DEL_0
PhV
WYE_1
WYE_0
WYE_1
VAr
WYE_1
VA
WYE_1
PF
WYE_1
LN Class:
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Hz
MV_0
Frequency
PPV
DEL_0
PhV
WYE_1
Mx7xI/EN M/J
Page 66
3.4.32
70 series
Logical Node: MMXU_9
Description:
LN Class:
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotW
MV_0
TotVAr
MV_0
TotVA
MV_0
TotPF
MV_0
Hz
MV_0
Frequency
PPV
DEL_0
PhV
WYE_2
WYE_3
WYE_1
VAr
WYE_1
VA
WYE_1
PF
WYE_1
WYE_1
Phase Impedance
DmdIntA
ASG_1
DmdIntP
ASG_1
DmdIntV
ASG_1
RsDmdA
SPC_0
RsDmdP
SPC_0
RsDmdV
SPC_0
Mx7xI/EN M/J
70 series
3.4.33
Page 67
Logical Node: MMXU_10
Description:
LN Class:
MMXU
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
TotW
MV_0
TotVAr
MV_0
TotVA
MV_0
TotPF
MV_0
Hz
MV_0
Frequency
PPV
DEL_0
PhV
WYE_2
WYE_0
WYE_1
,VAr
WYE_1
VA
WYE_1
PF
WYE_1
WYE_1
Phase Impedance
DmdIntA
ASG_1
DmdIntP
ASG_1
DmdIntV
ASG_1
RsDmdA
SPC_0
RsDmdP
SPC_0
RsDmdV
SPC_0
Mx7xI/EN M/J
Page 68
3.4.34
70 series
Logical Node: MMXU_11
Description:
LN Class:
MMXU
Attribute
3.4.35
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Hz
MV_0
Frequency
PPV
DEL_0
PhV
WYE_2
DmdIntA
ASG_1
DmdIntP
ASG_1
DmdIntV
ASG_1
RsDmdA
SPC_0
RsDmdP
SPC_0
RsDmdV
SPC_0
Sequence and imbalance for Volts and Amps (Pos, Neq, Zero)
LN Class:
MSQI
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
SeqA
SEQ_0
SeqV
SEQ_0
ImbNgA
MV_0
ImbNgV
MV_0
ImbZroA
MV_0
ImbZroV
MV_0
Mx7xI/EN M/J
70 series
3.4.36
Page 69
Logical Node: MSQI_1
Description:
LN Class:
MSQI
Attribute
3.4.37
3.4.38
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
SeqV
SEQ_0
ImbNgV
MV_0
ImbZroV
MV_0
Logical Node: MSYN_0 (Custom LN not contained in IEC 61850 part 7-4 definitions)
Description:
LN Class:
MSYN (Custom LN Class not contained in IEC 61850 part 7-4 definitions)
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_0
Health
NamPlt
LPL_2
Name Plate
DifVClc
MV_0
DifHzClc
MV_0
DifAngClc
MV_0
Logical Node: MTMP_0 (Custom LN not contained in IEC 61850 part 7-4 definitions)
Description:
LN Class:
MTMP (Custom LN Class not contained in IEC 61850 part 7-4 definitions)
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_0
Health
NamPlt
LPL_2
Name Plate
TmpVal
MV_0
Mx7xI/EN M/J
Page 70
3.4.39
70 series
Logical Node: RDRE_0
Description:
LN Class:
RDRE
Attribute
3.4.40
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
RcdTrg
SPC_1
RcdMade
SPS_0
Recording made
FltNum
INS_3
Fault number
RcdStr
SPS_0
Recording started
MemUsed
INS_3
Memory Used in %
PreTmms
ING_0
PstTmms
ING_0
MemFull
ING_0
OpMod
ING_1
FullSt
SPS_1
Current Transformer
LN Class:
TCTR
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Rat
ASG_0
Cor
ASG_0
AngCor
ASG_0
Mx7xI/EN M/J
70 series
3.4.41
Page 71
Logical Node: TVTR_0
Description:
Voltage Transformer
LN Class:
TVTR
Attribute
Attr. Type
Explanation
Mod
INC_0
Mode
Beh
INS_0
Behaviour
Health
INS_1
Health
NamPlt
LPL_0
Name Plate
Rat
ASG_0
Cor
ASG_0
AngCor
ASG_0
Mx7xI/EN M/J
Page 72
3.5
70 series
Common Data Class definitions
The definition tables for each of the Common Data Classes used in the Logical Node
definitions are presented in the following sub-sections.
From an application point-of-view the data attributes of a Common Data Class are classified
according to their specific use. The characterization of data attributes, and the services that
they support/provide, will be through the use of 'Functional Constraints'. The Functional
Constraints are specified by the table below:
FC Name
Semantic
Source Definition
BR
Buffered reports
IEC 61850-7-2
CF
Configuration
IEC 61850-7-2
CO
Control
IEC 61850-7-2
DC
Description
IEC 61850-7-2
EX
Extended Definition
IEC 61850-7-2
GO
GOOSE Control
IEC 61850-7-2
GS
IEC 61850-7-2
LG
IEC 61850-7-2
MS
IEC 61850-7-2
MX
IEC 61850-7-2
RP
Unbuffered reports
IEC 61850-7-2
SE
IEC 61850-7-2
SG
Setting Group
IEC 61850-7-2
SP
Set Point
IEC 61850-7-2
ST
Status Information
IEC 61850-7-2
SV
IEC 61850-7-2
US
IEC 61850-7-2
XX
IEC 61850-7-2
To elaborate on the data types used in the common data classes (or CDCs), the data
attributes, as defined in the tables, reflect the revised attribute types in order to correspond
with the data having either an integer value of 32 bits (INT32), or an enumerated value of 8
bits (ENUMERTED8). The attribute types defined for the common data classes, INC, ING
and INS, have been revised, with the values shown in parentheses to indicate the types that
have been replaced in standard IEC 61850, 1st edition. It was necessary to eliminate some
confusion that existed in the data definitions. The corresponding data objects of Mod, Beh,
Health, and PhyHealth use the enumerated versions for the CDCs. All other uses of the 3
CDCs use the INT32 version. An 8 bit enumeration is possible, because all enumerations
(so far) have less the 128 possible standardized values.
3.5.1
Analogue Setting
CDC Class:
ASG
Attribute
Type
FC
setMag
AnalogueValue_0
SP
Analogue Value
VISIBLE_STRING255
DC
Enumeration
Comment
Mx7xI/EN M/J
70 series
3.5.2
3.5.3
3.5.4
Page 73
Common Data Class: ASG_1
Description:
CDC Class:
ASG
Attribute
Type
setMag
AnalogueValue_0
SP
Analogue Value
VISIBLE_STRING255
DC
dataNs
VISIBLE_STRING255
EX
FC
Enumeration
Comment
CDC Class:
BCR
Attribute
Type
FC
actVal
INT64
ST
Quality
ST
TimeStamp
ST
pulsQty
FLOAT32
CF
VISIBLE_STRING255
DC
Enumeration
Comment
CDC Class:
CMV
Attribute
Type
FC
instCVal
Vector_0
MX
Instantaneous complex
measured vector
cVal
Vector_0
MX
Deadbanded Complex
measured vector value
(Magnitude only), however, the
value of cVal is updated to the
current value of instCVal. cVAl
will track to instCVal since
deadbanded values arent
supported in Mx70 devices.
Enumeration
Comment
Quality
MX
TimeStamp
MX
Mx7xI/EN M/J
Page 74
3.5.5
70 series
Common Data Class: CMV_1
Description:
CDC Class:
CMV
Attribute
Type
FC
instCVal
Vector_1
MX
Instantaneous complex
measured vector
cVal
Vector_1
MX
Deadbanded Complex
measured vector value
(Magnitude and Phase),
however, the value of cVal is
updated to the current value of
instCVal. cVAl will track to
instCVal since deadbanded
values arent supported in
Mx70 devices.
Enumeration
Comment
3.5.6
3.5.7
Quality
MX
TimeStamp
MX
CDC Class:
DEL
Attribute
Type
FC
phsAB
CMV_0
--
phsBC
CMV_0
--
phsCA
CMV_0
--
VISIBLE_STRING25
5
DC
Enumeration
Comment
CDC Class:
DPL
Attribute
Type
FC
vendor
VISIBLE_STRING255
DC
hwRev
VISIBLE_STRING255
DC
Hardware revision
swRev
VISIBLE_STRING255
DC
Software revision
serNum
VISIBLE_STRING255
DC
Serial Number
Enumeration
Comment
model
VISIBLE_STRING255
DC
Model Number
location
VISIBLE_STRING255
DC
Mx7xI/EN M/J
70 series
3.5.8
Page 75
Common Data Class: HWYE_0
Description:
CDC Class:
HWYE
Harmonic value for Wye represents the harmonic content of phase-to-neutral and neutral-toground quantities. Both magnitudes and phase angles are represented as arrays of floating
point quantities. The first index (index=0) of each array represents the DC component and
index=N represents the component at FREQ = N * f , where "f" is the fundamental
frequency.
Attribute
Type
FC
Enumeration
Quality
MX
TimeStamp
MX
phsAHar
Vector_1[64]
MX
phsBHar
Vector_1[64]
MX
phsCHar
Vector_1[64]
MX
numHar
INT16U
CF
evalTm
INT16U
CF
frequency
FLOAT32
CF
Frequency
hvRef
ENUMERATED8
CF
numCyc
INT16U
CF
VISIBLE_STRING255
DC
hvRef
Comment
Mx7xI/EN M/J
Page 76
3.5.9
70 series
Common Data Class: HDEL_0
Description:
CDC Class:
HWYE
The Harmonic value for Delta represents the harmonic content of phase-to-phase quantities.
Both magnitudes and phase angles are represented as arrays of floating point quantities.
The first index (index=0) of each array represents the DC component and index=N
represents the component at FREQ = N * f , where "f" is the fundamental frequency.
3.5.10
Attribute
Type
FC
Enumeration
Quality
MX
TimeStamp
MX
phsABHar
Vector_1[64]
MX
phsBCHar
Vector_1[64]
MX
phsCAHar
Vector_1[64]
MX
numHar
INT16U
CF
evalTm
INT16U
CF
frequency
FLOAT32
CF
Frequency
hvRef
ENUMERATED8
CF
numCyc
INT16U
CF
VISIBLE_STRING255
DC
hvRef
Comment
CDC Class:
INC
Attribute
Type
FC
Enumeration
Comment
stVal
ENUMERATED8
ST
Mod
Quality
ST
TimeStamp
ST
ctlModel
ENUMERATED8
CF
ctlModel
Mx7xI/EN M/J
70 series
3.5.11
Page 77
Common Data Class: ING_0
Description:
CDC Class:
ING
Attribute
Type
FC
stVal
INT32
SP
DC
Enumeration
Comment
3.5.12
VISIBLE_STRING255
CDC Class:
ING
Attribute
Type
FC
stVal
ENUMERATED8
SP
DC
Enumeration
Comment
3.5.13
VISIBLE_STRING255
CDC Class:
INS
Attribute
Type
FC
Enumeration
Comment
stVal
ENUMERATED8
ST
Beh
3.5.14
Quality
ST
TimeStamp
ST
CDC Class:
INS
Attribute
Type
FC
Enumeration
Comment
stVal
ENUMERATED8
ST
Health
Quality
ST
TimeStamp
ST
Mx7xI/EN M/J
Page 78
3.5.15
70 series
Common Data Class: INS_2 (Ed2: Dataclass would be called ENS_2)
Description:
CDC Class:
INS
Attribute
Type
FC
Enumeration
Comment
stVal
ENUMERATED8
ST
PhyHealth
3.5.16
Quality
ST
TimeStamp
ST
VISIBLE_STRING255
DC
CDC Class:
INS
Attribute
Type
FC
stVal
INT32
ST
Enumeration
Comment
3.5.17
Quality
ST
TimeStamp
ST
VISIBLE_STRING255
DC
Standard (or Basic) Logical Node Name Plate for the Measurements Logical
Device
CDC Class:
LPL
Attribute
Type
FC
vendor
VISIBLE_STRING255
DC
swRev
VISIBLE_STRING255
DC
Software revision
VISIBLE_STRING255
DC
Enumeration
Comment
Mx7xI/EN M/J
70 series
3.5.18
3.5.19
Page 79
Common Data Class: LPL_1
Description:
CDC Class:
LPL
Attribute
Type
FC
vendor
VISIBLE_STRING255
DC
swRev
VISIBLE_STRING255
DC
Software revision
VISIBLE_STRING255
DC
configRev
VISIBLE_STRING255
DC
ldNs
VISIBLE_STRING255
EX
Enumeration
Comment
CDC Class:
LPL
Attribute
Type
FC
vendor
VISIBLE_STRING255
DC
swRev
VISIBLE_STRING255
DC
Software revision
VISIBLE_STRING255
DC
ldNs
VISIBLE_STRING255
EX
Enumeration
Comment
Mx7xI/EN M/J
Page 80
3.5.20
3.5.21
70 series
Common Data Class: MV_0
Description:
CDC Class:
MV
Attribute
Type
FC
instMag
AnalogueValue_0
MX
mag
AnalogueValue_0
MX
Quality
MX
TimeStamp
MX
VISIBLE_STRING255
DC
Enumeration
Comment
CDC Class:
MV
Attribute
Type
FC
mag
AnalogueValue_0
Enumeration
Comment
MX
Quality
MX
TimeStamp
MX
VISIBLE_STRING255
DC
Mx7xI/EN M/J
70 series
3.5.22
Page 81
Common Data Class: SEQ_0
Description:
CDC Class:
SEQ
Attribute
Type
FC
c1
CMV_1
--
Sequence component 1
(Positive)
c2
CMV_1
--
Sequence component 2
(Negative)
c3
CMV_1
--
seqT
ENUMERATED8
MX
Enumeration
seqT
3.5.23
VISIBLE_STRING255
DC
Comment
Sequence quantity
measurement type (Pos-NegZero or Dir-Quad-Zero)
Description of the status
element. Textual description of
the data
CDC Class:
SPC
Attribute
Type
FC
Oper
Oper BOOL_0
CO
stVal
BOOLEAN
ST
Qualty
ST
TimeStamp
ST
stSeld
BOOLEAN
ST
ctlModel
ENUMERATED8
CF
Enumeration
ctlModel
Comment
VISIBLE_STRING255
DC
dataNs
VISIBLE_STRING255
EX
Mx7xI/EN M/J
Page 82
3.5.24
70 series
Common Data Class: SPC_1
Description:
CDC Class:
SPC
Attribute
Type
FC
Oper
Oper BOOL_0
CO
stVal
BOOLEAN
ST
Qualty
ST
TimeStamp
ST
stSeld
BOOLEAN
ST
ctlModel
ENUMERATED8
CF
VISIBLE_STRING255
DC
Enumeration
ctlModel
Comment
Mx7xI/EN M/J
70 series
3.5.25
Page 83
Common Data Class: SPC_3
Description:
CDC Class:
SPC
Attribute
Type
FC
SBO
VISIBLE_STRING64
CO
Oper
Oper BOOL_0
CO
Enumeration
Comment
Cancel
CancelBOOL_0
CO
stVal
BOOLEAN
ST
Qualty
ST
TimeStamp
ST
stSeld
BOOLEAN
ST
ctlModel
ENUMERATED8
CF
sboTimeout
INT32U
CF
ctlModel
sboClass
Enumerated8
CF
VISIBLE_STRING255
DC
Mx7xI/EN M/J
Page 84
3.5.26
3.5.27
3.5.28
70 series
Common Data Class: SPS_0
Description:
CDC Class:
SPS
Attribute
Type
FC
stVal
BOOLEAN
ST
Quality
ST
TimeStamp
ST
VISIBLE_STRING255
DC
Enumeration
Comment
CDC Class:
SPS
Attribute
Type
FC
stVal
BOOLEAN
ST
Quality
ST
TimeStamp
ST
VISIBLE_STRING255
DC
dataNs
VISIBLE_STRING255
EX
Enumeration
Comment
CDC Class:
WYE
Attribute
Type
FC
phsA
CMV_0
--
phsB
CMV_0
--
phsC
CMV_0
--
res
CMV_0
VISIBLE_STRING255
Enumeration
Comment
Mx7xI/EN M/J
70 series
3.5.29
3.5.30
3.5.31
Page 85
Phase A,B,C + Neutral Common Data Class: WYE_1
Description:
CDC Class:
WYE
Attribute
Type
FC
phsA
CMV_0
--
phsB
CMV_0
--
phsC
CMV_0
--
VISIBLE_STRING255
DC
Enumeration
Comment
CDC Class:
WYE
Attribute
Type
FC
phsA
CMV_0
--
phsB
CMV_0
--
phsC
CMV_0
--
neut
CMV_0
--
VISIBLE_STRING255
DC
Enumeration
Comment
CDC Class:
WYE
Attribute
Type
FC
phsA
CMV_0
--
phsB
CMV_0
--
phsC
CMV_0
--
neut
CMV_0
--
res
CMV_0
VISIBLE_STRING255
Enumeration
Comment
Mx7xI/EN M/J
Page 86
3.6
70 series
Common data attribute type definitions
Common data attribute types, known herein as components, are defined for use in the
Common Data Classes defined in the sections above.
3.6.1
Component: AnalogueValue_0
Comment:
3.6.2
Attribute
Type
FLOAT32
Enumeration
Comment
Component: CancelBOOL_0
Comment:
(Control) Cancel
3.6.3
Attribute
Type
Enumeration
Comment
ctlVal
BOOLEAN
origin
Originator_0
Origin
ctlNum
INT8U
Timestamp
Test
BOOLEAN
Component: Originator_0
Comment:
Type
Enumeration
Comment
orCat
Enumerated8
orIdent
OCTET_STRING64
Mx7xI/EN M/J
70 series
3.6.4
Page 87
Component: OperBOOL_0
Comment:
3.6.5
Attribute
Type
Enumeration
Comment
ctlVal
BOOLEAN
origin
Originator_0
Origin
ctlNum
INT8U
Timestamp
Test
BOOLEAN
Check
Check
Component: Vector_0
Comment:
3.6.6
Attribute
Type
mag
AnalogueValue_0
Enumeration
Comment
Component: Vector_1
Comment:
Type
Enumeration
Comment
mag
AnalogueValue_0
ang
AnalogueValue_0
Mx7xI/EN M/J
Page 88
3.7
70 series
Enumerated type definitions
The following sub-sections specify the enumerations that are associated to some Common
Data Class attributes. The definition of the enumerations is according to IEC 61850-7-3 and
IEC 61850-7-4 unless otherwise stated.
3.7.1
3.7.2
Behaviour
Ordinal
Semantic
on
blocked
test
test/blocked
off
3.7.3
Check specifies the kind of checks a control object shall perform before
issuing the control operation.
Ordinal
Semantic
No-check
synchrocheck
Interlocking-check
both
Control Model
Ordinal
Semantic
status-only *
direct-with-normal-security *
sbo-with-normal-security *
* NOTE:
3.7.4
ONLY the Status only and normal security control modes are
supported in Mx70 devices
Health
Ordinal
Semantic
Ok
Warning
Alarm
Mx7xI/EN M/J
70 series
3.7.5
Page 89
Enumerated type: hvRef
Description:
the data
3.7.6
3.7.7
Ordinal
Semantic
fundamental
rms
absolute
Mode
Ordinal
Semantic
on
blocked
test
test/blocked
off
Ordinal
Semantic
Explanation
not-supported
bay-control
station-control
remote-control
automatic-bay
automatic-station
automatic-remote
maintenance
process
Mx7xI/EN M/J
Page 90
3.7.8
70 series
Enumerated type: sboClass
Description:
3.7.9
Ordinal
Semantic
operate-once
operate-many
Ordinal
Semantic
pos-neg-zero
dir-quad-zero
Mx7xI/EN M/J
70 series
3.8
Page 91
MMS data-type conversions
The following table shows the relationships between the Part 7 and Part 8-1 data types. The
definitions presented above use Part 7 data types, however these are subject to 'translation'
when exposed over an MMS (Part 8-1) interface:
Part 7 Type
MMS Type
Part 7 Description
BOOLEAN
Bool
BVstring13
BVstring13
CODED_ENUM
Byte
Coded enumeration
CODED_ENUM2
Byte
EntryTime
Btime6
ENUMERATED8
Byte
FLOAT32
Float
FLOAT64
Double
INT128
Long
INT16
Short
INT16U
Ushort
INT24U
Ulong
INT32
Long
INT32U
Ulong
INT8
Byte
INT8U
Ubyte
OCTET_STRING6
Ostring6
OCTET_STRING64
Ostring64
OCTET_STRING8
Ostring8
Quality
BVstring13
TimeStamp
Utctime
UNICODE_STRING255
UTF8Vstring255
UTC_TM
Utctime
UTC Timestamp
VISIBLE_STRING255
Vstring255
VISIBLE_STRING64
Vstring64
64 character string
VISIBLE_STRING65
Vstring65
65 character string
VISIBLE_STRING97
Vstring97
97 character string
Mx7xI/EN M/J
Page 92
70 series
4.
4.1
Introduction
This Technical Issues Conformance Statement (TICS) specifies the conformance level
attributed to Mx70 Series of Intelligent Electronic Devices (Mx70 IEDs) with respect to the
Technical Issues (TISSUES) logged against the various parts of the IEC 61850 standard.
This document, along with the Protocol Implementation eXtra Information for Testing
document (PIXIT), defines the basis for conformance testing in accordance with part 10 of
the IEC 61850 standard specifications.
This document identifies numerous Tissues that have an impact on conformance testing of
the Mx70 IED. TISSUES have been classed into the following categories:
Tissues identified as either editorial, or related to the XML schema or a client, Tissues
that are not applicable to the IEC 61850 implementation in the Mx70 devices are
grouped in this class.
Tissues that have not completed or closed within the last year or Tissues that have a
status other then Green. These Tissues may or may not be listed in the conformance
tables. Their numbers are included for completeness, and for tracking Tissues
requiring future consideration.
Technical issues with applicability under the IEC 61850 implementation in the Mx70
devices.
According to the UCA IUG QAP the Tissue conformance statement is required to perform a
conformance test and is referenced on the certificate
For more details on the logged Technical Issues, refer to the website:
http://www.tissues.iec61850.com
4.2
Tissues considered
This document incorporates Tissues closed prior to April-2007. Tissues that have closed
within the last year are not necessarily considered for the Edition 1 implementation of the
IEC 61850 standard.
Mx7xI/EN M/J
70 series
4.3
Page 93
Document structure
This document is broken down into several sub-sections; one per part of the IEC 61850
standard specifications.
Each subsection contains:
Meaning
Mx.y
TISSUE is not yet included in the UCA Device conformance test procedures,
or its a recommendation, or its optional in the IEC 61850 documents.
tbd
Meaning
N/A
4.4
Date
Note
24-June-2008
Firmware Applicablility
This manual is applicable to IEC 61850 for M57x/M87x firmware version v3.00.0 and later.
Mx7xI/EN M/J
Page 94
70 series
4.5
Part 5 Standard
4.5.1
Specification scope
The scope of part 5 of the IEC 61850 standards covers the communication requirements for
functions and device models.
4.5.2
4.5.3
4.5.4
Technical Issues
At the time of writing there are no logged technical issues against part 5.
4.6
Part 6 Standard
4.6.1
Specification scope
The scope of part 6 of the IEC 61850 standards covers the configuration description
language for communication in electrical substations related to IEDs.
4.6.2
4.6.3
Num
Doc. Ref.
Subject
Status
Comment
Annex A5
Syntax
Green
Annex B
Missing ENUMs
Green
Supported
Technical Issues
Conformance
4.6.4
9
M1.1
N/A
Annex A
tExtensionAttributeNa
meEnum is restricted
Green
tbd
?
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
SCL
schema
ReportControl/OptFields
Green
Supported
Page 95
Conformance
70 series
tbd
SCL
schema
Annex B
Annex A
Duplication of
attributes.
Green
SIUnit enumeration
for W
Green
Green
N/A
O
N/A
O
9
Annex A
Green
N/A
SCL
schema
Green
17
Schema
DAI/SDI elements
syntax
Green
18
9.3.4,
Functional naming
and LDevice
Green
M1.1
Table 14
130
169
General
p. 119,
Appendix B
LDName length
Ordering of enum
differs from 7-3
Green
Green
N/A
N/A
N/A
N/A
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
186
Table 21
Definition of DataSet
Members
Green
Supported
70 series
Conformance
Page 96
M1.1
N/A
N/A
Green
243
272
p. 65,
9.3.8
RCB Naming
p. 23,
8.2.6
Green
Green
307
P 58,
9.3.7
Attributes
of the
FCDA
element
9.3.2
Flag
buffered/unbuffered
reporting in element
service
Green
Number of client
associations
Green
315
Green
Note:
p. 118,
Annex B
(normative)
Sev
Green
N/A
529
N/A
Mx7xI/EN M/J
70 series
Page 97
4.7
4.7.1
Specification scope
The scope of part 7-1 of the IEC 61850 standards covers the architecture for communication
and interactions between substation devices such as protection devices, breakers,
transformers, substation hosts etc.
4.7.2
4.7.3
Num
Doc. Ref.
Subject
129
13.2.2,
Table 13
Coming/Going
events?
Status
Comment
Supported
Technical Issues
Conformance
4.7.4
tbd-
p.75,
13.2.2
Green
Mx7xI/EN M/J
Page 98
70 series
4.8
4.8.1
Specification scope
The scope of part 7-2 of the IEC 61850 standards covers the layered substation
communication architecture principles.
4.8.2
4.8.3
4.8.4
Conformance
4.8.5
Doc. Ref.
Subject
Status
Comment
30
17.5.2.3
Control parameter T
Green
N/A
31
32
14.2.3.2.3
.2
Typo
14.2.2.1
14.4.2.1
Typo in syntax
Green
Green
Supported
Num
34
15.1
Publish.request
explanation
Green
M1.
1
35
17.5.2.3,
Table 36
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
36
15.2.2.3,
15.2.2.4
Syntax parameter
DSet-Ref missing
Green
Supported
Page 99
Conformance
70 series
N/A
15.2.3.1
Green
M1.
1
M1.
1
M1.
1
M1.
1
N/A
N/A
15.2.1
15.2.1.4
Syntax "AppID" or
"GoID"
Green
39
15.2.1
Green
40
15.2.3.1
15.2.3.3
GOOSE Message
AppID to GoID
Green
41
15.3.1
15.3.4.1
Green
42
43
p.138,
16.4
SV timestamp:
EntryTime to
TimeStamp.
Green
p.148,
17.5.2.3
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
44
17
AddCause - Object
not sel
Green
Supported
70 series
Conformance
Page 100
N/A
AddCause is used only for EnhancedSecurity Control. Mx70 devices use only
Normal-Security Controls.
45*
17.5.2.6
Missing AddCauses
Red
46
17.3.3
Green
N/A
47
19.2,
Figure 40
"." in LD Name?
Green
48
17.2.1,
Figure 30
Syntax in state
machine
Green
49
14.2.2.16
BRCB TimeOfEntry
Green
N/A
19.2
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
51
5.5.2
ARRAY [0..num]
missing
Status
Comment
Supported
Page 101
Conformance
70 series
N/A
15.2.3.6
Ambiguity GOOSE
SqNum
Green
53
15.3.1,
16.2.1,
Table
30,32
Add DstAddr to
GsCB, SV
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
150
p.58
Green
11.2.2.3
Attributes of Control
Blocks as members of
DataSets
p.156157, 19.2
Green
151
Comment
Supported
70 series
Conformance
Page 102
N/A
N/A
N/A
N/A
N/A
Tbd
N/A
N/A
N/A
163
10.2.2.4.3
Green
166
14.3.3.2.7.3
DataRef attribute in
Log
Green
180
12
Figure 16
Figure substitution
misleading
Green
185
14.3.3.2.7.3
Logging - Integrity
period
Green
187
16
OptFlds in SV CB's
not exposed for client
specification
Green
188
189
p.138,
16.4.
Table 34
SV Format
p. 134,
16.4,
Table 34
SV Format
Green
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
190
p.77,
14.2.2.1
Green
Supported
Page 103
Conformance
70 series
TimeOfEntry in GetBRCBValues:
"The value, returned in a GetBRCBValues
response, shall provide the time stamp of
the EntryID whose value is exposed in the
control block. The value exposed for
TimeOfEntry, when the value of EntryID is
zero(0), is a local issue."
191
p.78/81,
14.2.2.5
14.2.2.12
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
220
p.48,
10.2.2.4.2,
Table 18
FC SP
Green
Supported
70 series
Conformance
Page 104
p.21,
5.5.2
Green
236
19.2
Name length
Green
261
19
Red
278
p.82,
14.2.2.15
Green
Ed2:
Mx7xI/EN M/J
Doc. Ref.
Subject
Status
289
10 and 19
Instatiation of DATA
Comment
297
14.2.2.10
Sequence number
Green
N/A
Definition of SqNum:
"The BRCB that has report enable set to
TRUE shall maintain the parameter
SqNum. This number shall be
incremented by the BRCB for each report
generated and sent on the basis of the
BRCB. The increment shall occur once
the BRCB has formatted the report for
transmission. The first report following the
setting of the report enable to TRUE shall
contain sequence number 0. The
sequence number shall roll over to 0 at its
maximal value."
298
300
Table 23
& 25
Type of SqNum
p.77
Attribute Resv in
BRCB
14.2.2.1
Green
Green
Table 23
305
322
325
p. 80,
p.85,
14.2.2.9,
14.2.3.2.2
.9
Reporting with
BufTm=0
14.2.2.1
&
14.2.4.1
Write Configuration
attribute of BRCBs
p.24,
5.5.3.7.2
TimeStamp definition
Table 7
Supported
Num
Page 105
Conformance
70 series
Green
Green
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
329
P.85,
14.2.3.2.2.8
Para 1
Green
Supported
70 series
Conformance
Page 106
332
333
334
p.143,
17.2.2
Para. d)
p.88,
14.2.3.2.3.2
Ambiguity in use of
trigger options
Green
p.110,
15.2.1.3
Enabling of an
incomplete GoCB
Green
p.142,
17.3.3
Green
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
335
p. 85,
14.2.3.2.2.8
Clearing of Bufovfl
Green
337
p.164,
Annex A,
Table
A.2, M7
and M8
Configuration
Revision option
missing
Green
Supported
Page 107
Conformance
70 series
349
p.92, 93,
14.2.4,
Para
14.2.5.2
Green
p.75,
Para.
14.2.2.16,
14.2.3.2.2.9
BRCB TimeOfEntry
has two definitions
Green
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
370
p.146,147
Time-activated
operate and further
conditions like mode
Final
proposal
17.4
Procedure
b)
Supported
70 series
Conformance
Page 108
N/A
N/A
N/A
N/A
N/A
N/A
p.64,
clause 12
Substitution subVal
and subID
Green
374
p.64,
clause 12
Over-write
substitution values
Green
384
386
391
405
417
p.18,
5.3,
Figure 3
Conceptual service
model in 5.3
Green
p.54,
10.4.2.3
GetDataValues - leafs
not access
Green
p.21,
5.5.2,
Table 2
Green
p.160 &
161
20.2.2
SetFile
p.120,
GSSE service
Green
Green
Mx7xI/EN M/J
426
Doc. Ref.
Subject
15.3.3.1
definitions
p.58,
11.2.1
Dataset contents
configurability
Status
Comment
Green
Supported
Num
Page 109
Conformance
70 series
Clause
17
Cancelling a started
control sequence
Green
Mx7xI/EN M/J
Page 110
70 series
4.9
4.9.1
Specification scope
The scope of part 7-3 of the IEC 61850 standards covers the abstract common data class
definitions.
4.9.2
4.9.3
Conformance
4.9.4
Doc. Ref.
Subject
Status
Comment
28
7.6.2
Definition of APC
Green
N/A
54
6.11
Green
N/A
55
7.4.5
Table 25
Ineut = Ires ?
Green
N/A
Supported
Num
Table
13/21 and
Services missing in
Green
Mx7xI/EN M/J
63
65
Doc. Ref.
Subject
other
tables
General
General
Status
Comment
Supported
Num
Page 111
Conformance
70 series
Deadband calculation
of a Vector and trigger
option
Green
N/A
N/A
N/A
68
General
Green
164
6.5
Deadband on range
limits
Green
171
p.24,p.40
p.46
Green
204
7.7 and
7.8
Reporting of setting
values
Green
205
p.42 7.9.2
table 46
Green
Green
N/A
N/A
Tbd
N/A
N/A
N/A
217
219
7.3.5
Table 17
operTm in ACT
Green
239
p.22,
clause
7.2, Table
12
Conflict of LPL
definitions with
requirements of
Namespace
Green
240
p.61,
Table A.4
Green
247
p.60-62,
Table A
Miss % representation
Green
265
6.2.1
Quality extension
Red
266
p.28, and
more,
7,4,2 and
more,
Table 22
and more
Open Enumeration of
range
Green
p.31,
clauses
7.4.5,
7.4.6
270
Green
327
p.61,
Table A.4
Green
N/A
328
p.61,
Green
N/A
Mx7xI/EN M/J
Doc. Ref.
Subject
Status
Table A.4
frequency functions
330
7.4.8 thru
7.4.10
Green
375
p.25,
7.3.6
Directional loop
activation information
Green
439
p.47,
7.8.2
(ASG)
Table 43
Lower limit of
stepSize in ASG
Green
469
Green
482
p.29,
7.4.3,
Table 23
Quality evaluation of a
Vector
Yellow
519
Annex A
Green
525
7.4.2,
Table 22
Final
proposal
582
p.26,
7.3.8
Green
615
p.22,
Table 12
Red
Comment
Supported
Num
70 series
Conformance
Page 112
N/A
N/A
N/A
N/A
N/A
Mx7xI/EN M/J
70 series
Page 113
4.10
4.10.1
Specification scope
The scope of part 7-4 of the IEC 61850 standards covers the compatible Logical Node class
and data class definitions.
4.10.2
4.10.3
Num
Doc. Ref.
Subject
Status
Comment
Supported
Technical Issues
Conformance
4.10.4
72
General
Green
M1.1
N/A
5.11.3
5.11.4
Instances of LN SIMG
(SIML)
Green
Tbd
N/A
Clause 6
PresTr
Green
73
74
75
5.7.1
Str and Op
Green
N/A
Tbd
N/A
N/A
N/A
76
Clause 6
CBOpCap and
SwOpCap
Green
79
Clause 6,
Table 9
AutoRecSt and
Lockout
Green
80
5.13
Green
82
5.10
Green
N/A
83
5.6.6
Operation by CSWI.
Green
N/A
84
Clause 6,
Table 9
Green
N/A
85
Clause 6,
Table 9
RsStat - device
security statistics
Green
N/A
86
Clause 6,
Table 9
PwrSupAlm and
EEHealth
Green
N/A
90
5.6.5
Green
TBD
N/A
91
5.11.3
Green
TBD
N/A
Mx7xI/EN M/J
Conformance
Page 114
Doc. Ref.
Subject
Status
Comment
92
5.11.4
Green
TB
D
N/A
94
5.3.4
Green
TB
D
N/A
95
5.3.4
Proposed called
BlkStat.
Green
TB
D
N/A
96
5.7.3
LN GSAL - OpCntRs
Green
TB
D
N/A
97
5.8.1
LN IARC and
OpCntRs
Green
TB
D
N/A
98
5.7.3
GSAL/IARC and
NumCntRs
Green
TB
D
N/A
NamPlt of LLN0
Green
N/A
5.8.1
99
Clause 6
Supported
Num
101
5.5.2
LevMod - disturbance
recorder
Green
102
5.5.2
Green
N/A
104
5.6.6
LN CSWI - open/close
Green
N/A
105
5.10.
LN Group M EEHealth
Green
N/A
106
5.10.7.
MMXU EEHealth
Green
N/A
132
5.12.4
SwARsAlm in XCBR
Green
LN RREC
Unsuccesfull
Green
N/A
LN GGIO
Green
N/A
N/A
N/A
N/A
133
134
147
5.7.2
p.80,
clause 6,
Mod
Green
Table 9
148
5.7.3,
5.8.1
OpCntRs
Green
152
5.9.3,
5.9.4,
5.9.5
Automatic Voltage
Control - AVCO,
ATCC, ARCO
on hold
153
Missing Automatic
Infeed Switching
on hold
199
Green
208
5.7.3,
5.8.1
NumCntRs - Control?
Green
209
p.46,
5.7.3
Authorisation Failure
Green
216
5.3.3
Description of LN
inputs
Green
252
p.31,
5.4.22
PTTR.AlmThm
256
p.55,
N/A
Tbd
NA
Green
NA
Green
Mx7xI/EN M/J
Doc. Ref.
Subject
Status
5.10.7
Comment
Supported
Num
Page 115
Conformance
70 series
257
5.10.2
263
264
268
General
on hold
Green
Green
p.29,
5.4.18
PTOC Enabling
Blocking by Harmonic
restraint
Green
269
p.30,
5.4.21
Green
281
p.40,
5.5.9
LN RPSB
Green
283
p.27
SchTyp in LN PSCH
on hold
288
p.36,
5.5.2
RDRE.RcdTrg
Green
N/A
N/A
N/A
N/A
N/A
N/A
N/A
304
306
309
311
Clause 4
Assignment of new
letters for logical
nodes
on hold
Local / Remote
Green
on hold
on hold
319
71 5.3.3
'behaviour' attribute is
not required for LLN0
Green
N/A
320
p.91,
clause
A.1.1.2,
Para.2
Numbering of
extended data
Green
324
p.27,
5.4.15
Str in LN PSCH
on hold
343
p.48,
5.9.4
ATCC.ParOp
Green
N/A
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
360
p.48-49
5.9.4
ATCC.LTCBlk <-->
ATCC.Auto
Green
SP versus DP on
electrical IED inputs
Green
362
363
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Green
p.45,
5.7.2,
Para 1
GGIO -- Limitation of
Floating point set
point
Green
468
p.37,
5.5.3.5.5.4
DR -- Requires more
explanation
Green
475
p.92,
Annex
A.3 all
para.
Specialisation of data
by use of the number
extension
Final
proposal
476
p.49,
5.9.4
ATCC.BlkVLo / BlkVHi
Green
477
p.59,
5.12.1
XCBR.HeatAlm
Green
478
p.46,
5.8.2
emergency off,
IHMI.EmgOff
Green
479
%-change of
measured values
Green
480
p.58,
5.11.4
SIML.TmpAlm
Green
488
Final
proposal
467
Comment
Supported
70 series
Conformance
Page 116
539
Dynamic Protection
Blocking
Final
proposal
584
p.36,
5.5.2
Final
proposal
585
p.36,
5.5.2
Final
proposal
591
SIML
Final
proposal
Mx7xI/EN M/J
70 series
Page 117
4.11
4.11.1
Specification scope
The scope of part 8-1 of the IEC 61850 standards covers the specific communication service
mapping (SCSM) to the MMS protocol.
4.11.2
4.11.3
4.11.4
4.11.5
Tissues Unresolved:
246,527,528,535,541,547,583,596
Num
Doc. Ref.
Subject
Status
114
17.1.1.1
&
17.1.1.2
Naming URCB
Green
8.2.1.3,
9.2.2.3
GetNameList with
empty response?
116
Comment
N/A
N/A
The GetLogicalDeviceDirectory
response- should be an MMS
GetNamedList response+ with
moreFollows=FALSE and a NULL List.
If the GetNamedList service is issued for
a Domain scoped object and the Domain
does not exist, then a Confirmed-Error
response with object-non-existent shall
be returned.
117
118
119
18.1.2.5
23.1
Green
File directory
Green
MMS
GetCapabilityList
required?
Green
122
25.1.1.1,
Table 111
Supported
Technical Issues
Conformance
4.11.6
Green
Mx7xI/EN M/J
Conformance
Page 118
Doc. Ref.
Subject
Status
Comment
128
18, 19
Add DstAddr to
GsCB, SV
Green
N/A
165
p.47
14.3.1
Improper Error
Response for
GetDataSetValues
Green
Order of attributes in
MMS components
Green
Tbd
168
177
183
p.32
7.3.2
Para 2
p.52
17.1.1.2
Table 39
p. 39
9.3
Table 17
GetNameList error
handling
Green
Green
196
Annex E
Green
198
see
tissue
#114
Instantiation of URCB
Green
8.1.3.2
Extension of Name
length
235
Supported
Num
Mx7xI/EN M/J
Num
Doc. Ref.
Subject
Status
Comment
260
p.93
23.2.4
Para 1
GetFileAttributeValues
Green
Supported
Page 119
Conformance
70 series
N/A
p.88
20.8
LastApplError Error
codes
Green
292
p. 18
clause 4
Explanation of r and w
Green
368
p.84,
p.86,
20.5,
20.7,
20.7.1.3
Mapping of analogue
setpoints (SP)
Green
Mx7xI/EN M/J
Conformance
Page 120
Doc. Ref.
Subject
Status
Comment
422
p.34
7.3.1
Order of extension
data objects and data
attributes
Green
433
438
446
545
p.122126
Clause
E.4
Order of attributes in
specialized CDCs for
control service
mapping
Green
p.36
8.1.3.7
EntryTime base
should be GMT
Green
Blue
p. 89
Clause
23.1
File directories
Green
586
Blue
587
p.33,
8.1.1
Green
609
p.125
clause
E.4.2
Blue
Supported
Num
Mx7xI/EN M/J
Page 121
4.12
4.12.1
Specification scope
The scope of part 9-1 of the IEC 61850 standards covers the specific communication service
mapping (SCSM) for sampled values over a serial unidirectional multidrop point to point link.
4.12.2
Technical Issues
The Mx70 IED devices do not support part 9-1 of the IEC 61850 standards. TISSUES
relating to this part therefore do not affect the application implementation; hence Tissues are
not listed in this section.
4.13
4.13.1
Specification scope
The scope of part 9-2 of the IEC 61850 standards covers the specific communication service
mapping (SCSM) for sampled values over ISO/IEC 8802-3
4.13.2
Technical Issues
The Mx70 IED devices do not support part 9-2 of the IEC 61850 standards. TISSUES
relating to this part therefore do not affect the application implementation; hence Tissues are
not listed in this section.
Mx7xI/EN M/J
Page 122
70 series
4.14
Part 10 Standard
4.14.1
Specification scope
The scope of part 10 of the IEC 61850 standards covers the conformance testing of a
device.
4.14.2
4.14.3
Num
Doc. Ref.
Subject
Status
206
5.4.1,
6.2.4.5,
5.5
Add Conformance
Blocks
White
Red
218
336
Clause 5.5,
last
paragraph
Test context
Red
Comment
Supported
Technical Issues
Conformance
4.14.4
N/A
N/A
376
p.25,
6.2.4.9.2
White
420
p.20,
6.2.4.3
Red
421
p.20,
6.2.4.3
Versioning of schema
for configuration files
White
594
p.35,
Table 28
Para. CtlN3
Red
p.35,
Table 27
TimeActivatedOperate
in 61850-7-2 is not the
same to TimeActivation
of 61850-8-1
White
597
Mx7xI/EN M/J
70 series
Page 123
5.
5.1
Introduction
This document specifies the Protocol Implementation eXtra Information for Testing (PIXIT) of
the IEC 61850 interface for the Mx70 family of IED measurement devices. Together with the
PICS and MICS specifications the PIXIT forms the basis for conformance testing in
accordance with part 10 of the IEC 61850 standard specifications.
5.2
Document structure
Each section within this specification specifies the PIXIT for each supported ACSI service
model as structured in parts 7-2 and 10 of the IEC 61850 standard specifications.
5.3
5.3.1
5.3.2
5.3.3
Authentication
Authentication for IEC 61850 is not supported. Refer to paragraph 2.4
5.3.4
Association parameters
The following parameters are required to be specified when attempting to initiate an
association with Mx70 IEDs:
Parameter
Value
Transport selector
(tsel)
00 01
Session selector
(ssel)
00 01
00 00 00 01
The following parameters are only required if write permission should be granted. The values
are not checked, only the presence of the parameters is used to grant complete write
permission. Unless both parameters are present, writes to many objects are disallowed.
Parameter
Value
AP Title
1,3,9999,10
6
AE Qualifier
33
Mx7xI/EN M/J
Page 124
5.3.5
Aborting associations
When a client aborts its association the TCP/IP socket is not immediately closed down by
the IED. This is a standard operating principle to ensure that any delayed or out-of-order
frames are correctly processed before closing down the socket.
The time-out period for aborted sockets is approximately sixty (60) seconds. For the duration
of this time-out period the socket resources are unavailable for new client association
requests.
A total of 100 sockets are available but it should be noted that these resources are shared
with other network tasks (for example SNTP time synchronisation). If no sockets are
available the IED will refuse new association requests from a client.
5.3.6
5.3.7
5.3.8
Startup time
The typical start-up time of basic Ethernet services, following an interruption to the power
supply, is approximately seventy-five (75) seconds. Full IEC 61850 services are available
after an approximate start-up time of seventy-five (75) seconds.
Mx7xI/EN M/J
70 series
5.4
Page 125
Server Model
Description
Value/Clarification
Validity:
Y
Y
N
Y
good
invalid
reserved
questionable
Detailed Quality:
N
N
N
N
N
N
N
Y
overflow
outOfRange
badReference
oscillatory
failure
oldData
inconsistent
inaccurate
Source:
Y
N
N
N
Which status value (ST) quality bits
are supported (can be set by server)?
process
substituted
test
operatorBlocked
Validity:
Y
Y
N
N
good
invalid
reserved
questionable
Detail Quality:
N
overflow
N
outOfRange
N
badReference
N
oscillatory
N
failure
N
oldData
N
inconsistent
N
inaccurate
Source:
Y
N
N
N
process
substituted
test
operatorBlocked
Mx7xI/EN M/J
Page 126
5.4.2
70 series
The total length of all ObjectReferences to be included within the service request
That is to say, the total length of all ObjectReferences must be less than the maximum
supported MMS PDU size, taking into account any relevant header information.
5.4.3
5.4.4
Non-IEC61850 Domains
It should be noted that the 70 Series IED contains two (2) non-IEC61850 MMS Domains;
LD0 and UCADevice. These domains are outside of the scope of the IEC61850 standard
and, as such, should not be included in any conformance testing to it.
For testing purposes, it is suggested that the 70 Series device be configured with an IED
Name that begins with a letter that appears before L in the alphabet. That way the
IEC61850 domains; Measurement, Records, and System will appear before the nonIEC61850 domains when interrogating the device.
5.5
Value/Clarification
5.6.1
5.7
Mx7xI/EN M/J
70 series
5.7.1
Page 127
Configuration
Mx70 devices do not support on-line setting changes of elements over the IEC 61850
interface
Configuration of Mx70 devices is achieved through the use of the following software tools
that are provided:
5.8
Reporting Model
Description
Value/Clarification
data-change
Y
quality-change
N
data-update
N
integrity
Y
general-interrogation Y
Attempts to enable trigger conditions that
are not supported (N) will result in a
negative response being returned.
The supported trigger options are set in the
devices IED Capability Description (ICD)
file to define the IEDs reporting capability.
This is not to be confused with the actual
devices configuration, which would
normally be represented in a Configured
IED Description (CID) file
Y
Y
Y
Y
Y
Y (buffered only)
Y (buffered only)
Y
N (not optional)
Yes
Reports will be segmented, and sent with
sub-sequence numbers, if the data is too
big to fit into a single MMS frame. In this
case the segmentation bit in the Reported
OptFlds will be set to 1
Mx7xI/EN M/J
Page 128
70 series
Description
Value/Clarification
Yes
<configuration revision>
5.9
5.9.1
Event logging
Mx70 devices do not support IEC 61850 logging services, hence there are no Log Control
Blocks (LCB) exposed within the data model.
For Mx70 devices there is an existing measurement event log that is used to store historical
data. This is only available through the soelog.txt file.
Mx7xI/EN M/J
Page 129
5.10
5.10.1
5.10.2
SendGOOSEMessage
GetGoReference
GetGoCBValues
The SetGoCBValues service is not supported, although it is possible for connected clients to
change the GoEna attribute online.
5.10.3
5.10.3.1
Message validation
The following elements of a GOOSE message header are checked in order to determine the
messages validity prior to processing its data within the IEDs GOOSE scheme:
Frame Ethertype,
AppID
Time Allowed to Live, which is expected to be a value greater than zero (0).
DatSet, which is expected to be a valid reference as taken from the publishing devices
GoCB during device configuration (from SCL) and not a NULL value.
GoID, which is expected to be a valid reference as taken from the publishing devices
GoCB during device configuration (from SCL) and not a NULL value.
ConfRev, which is expected to match the publishing devices GoCB as set during
device configuration (from SCL).
numDatSetEntries, but only after an initial message from the publishing device has
been received and the device has been enrolled. At this point each subsequent
message must contain the same number of data set elements as the first received
message.
The following elements of the GOOSE message header are not checked during validation of
received messages:
Mx7xI/EN M/J
Page 130
5.10.4
70 series
Data processing
The data received in a GOOSE message is only processed when a change in status number
(stNum), taken from the GOOSE message header, is detected. No validation checks are
made to ensure the data has changed inline with the stNum increment and it is accepted and
processed as per the normal procedure given below.
The data is transferred onto Boolean, Integer, and Float values. Boolean and Integer input
values can be converted to Boolean values when the data subscription parameters are met:
Virtual Input State
Criteria
True
On
The received data value matches the virtual inputs target value in
accordance with its comparison operator.
False |
Off
The received data value does not match the virtual inputs target
value in accordance with its comparison operator.
Mx70 IEDs support thirty-two (32) each of Boolean, Integer, and Float virtual input signals
each with their own GOOSE data set attribute index, target value and comparison operator.
The following comparison operators are supported:
Only the following basic data attributes of a basic data-type can be decoded from the
incoming GOOSE data set elements:
Unsigned integer
Signed integer
Boolean
Bit-string 2
5.10.4.1
5.10.4.2
Mx7xI/EN M/J
70 series
5.10.4.3
Page 131
Needs commissioning and Test flags
If a GOOSE message is received and the NdsCom and/or test flags are set the message will
be accepted as valid [The TAL will be updated thus ensuring the device is classed as fully
subscribed within the relays GOOSE scheme], however the message data will not be
extracted nor processed within the IEDs GOOSE scheme logic.
Any Virtual Input that is driven by the incoming GOOSE message (flagged as NdsCom or
test) will revert to its configured default value.
5.10.4.4
5.10.4.5
Default values
For the following conditions, a virtual inputs value will be forced to its configured default
value:
5.10.5
Publication
5.10.5.1
Pre-configured attributes
The following pre-configured attributes of the GOOSE Control Block (GoCB) can not be
changed, either during device configuration (from SCL) or online by a connected client:
DatSet
NdsCom
The DstAddress (Destination Address) data object of the GoCB is configurable from SCL but
can not be changed online by a connected client.
5.10.5.2
Commissioning
The data set assigned to the GOOSE Control Block is pre-configured and can not be
modified at system configuration time or by a connected client. As such the NdsCom (Needs
commissioning) attribute is fixed to FALSE.
5.10.5.3
5.10.5.4
Mx7xI/EN M/J
Page 132
70 series
5.11
5.11.1
5.12
Control Model
5.12.1
Modes of operation
Description
Value/Clarification
Y
Y
Y
N
N
No functionality
No functionality
Is operate-many supported?
(via configuration)
N
N
synchrocheck
interlock-check
N
N
Y
N
N
N
N
N
N
Y
N
N
instance-not-available
instance-in-use
access-violation
access-not-allowed-in-current-state
parameter-value-inappropriate
parameter-value-inconsistent
class-not-supported
instance-locked-by-other-client
control- must-be-locked
type-conflict
failed-due-to-communications
constraint failed-due-to-serverconstraint
status-only
direct-with-normal-security
sbo-with-normal-security
direct-with-enhanced-security
sbo-with-enhanced-security
Mx7xI/EN M/J
70 series
Page 133
Description
Value/Clarification
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Not possible
Yes
DOns=Y
SBOns=N
DOes=N/A
SBOes=N/A
Selection of objects
Command checking
Unknown
Blocked-by-switching-hierarchy
Select-failed
Invalid-position
Position-reached
Parameter-change-in-execution
Step-limit
Blocked-by-Mode
Blocked-by-process
Blocked-by-interlocking
Blocked-by-synchrocheck
Command-already-in-execution
Blocked-by-health
1-of-n-control
Abortion-by-cancel
Time-limit-over
Abortion-by-trip
Object-not-selected
Mx7xI/EN M/J
Page 134
5.13
70 series
Value/Clarification
N LeapSecondsKnown
N ClockFailure
Y ClockNotSynchronized
ClockNotSynchronized set?
SNTP Request interval
Time quality
Historical data logged by Mx70 IEDs includes a limited subset of TiomeQuality information
with respect to timestamps. For this reason only ClockNotSynchronized bit is supported.
TimeQuality bits LeapSecondKnown and ClockFailure are not supported and are fixed at a
value of zero (0).
5.13.2
Time accuracy
The time accuracy of Mx70 IEDs is to fourteen (14) significant bits of the FractionOfSecond
attribute. This equates to approximately one hundred (100) microseconds, meeting the
requirements of performance class T2 as defined in Part 5 of the IEC 61850 standard.
5.13.3
External synchronization
Mx70 IEDs can be configured with two (2) external time synchronization servers, of which
only 1 is ever the active time synchronisation source.
If an external source fails to respond to a client synchronisation request, or responds with
and invalid/unsupported message, the IED will automatically switch to the unused source, if
configured.
Manycast mode of SNTP is fully supported but users are strongly cautioned to verify
behaviour of their systems before enabling the manycast mode.
5.13.4
5.13.5
IRIG-B
If IRIG-B is enabled (via configuration) and a valid signal is being received by the IED, then
SNTP server responses will be ignored as IRIG-B is deemed to be the primary source of
time synchronisation.
If IRIG-B becomes unavailable during normal operating conditions, SNTP will become the
active time synchronisation source until such time that IRIG-B becomes available once
again. However, it is recommended that only a single time source type to be used.
Mx7xI/EN M/J
70 series
5.14
Page 135
File Transfer Model
Description
Value/Clarification
256
No
Yes
Mx7xI/EN M/J
Page 136
5.15
5.15.1
Conformance level
70 series
Mx70 IEDs are conformant to SCL.1 as defined by part 8 of the IEC 61850 standards; annex
D.
ICD template files are available within the MiCOM S1 IED Configurator application.
5.15.2
Private data
Mx70 ICD files contain private SCL data. This is required by the IED Configurator tool in
order to correctly extract, process and configure a device.
Any tool that imports Mx70 ICD files is required to preserve the private data in accordance
with part 6 of the IEC 61850 standards.
5.15.3
IED Name
The Sub-station Configuration Language (SCL) allows customisable IED names. Mx70 IEDS
support user-definable IED names. It is recommended, however, that these names be
restricted to a maximum of eight (8) characters in length.
5.16
IED Configuration
5.16.1
Configuration banks
Mx70 devices support two (2) configuration banks for holding IED configurations taken from
SCD or CID Substation Configuration Language (SCL) files. This includes IP configuration,
SNTP, GOOSE publishing/subscription parameters etc.
The IED Configurator tool only allows a configuration to be downloaded to the inactive bank.
The IED Configurator will prompt the user if he/she desires to make the configuration active.
PXXX
ProductDescription
Alstom Grid
- ALSTOM 2012. ALSTOM, the ALSTOM
logo and any alternative version thereof are
trademarks and service marks of ALSTOM.
The other names mentioned, registered or
not, are the property of their respective
companies. The technical and other data
contained in this document is provided for
information only. Neither ALSTOM, its officers
or employees accept responsibility for, or
should be taken as making any representation
or warranty (whether express or implied), as
to the accuracy or completeness of such data
or the achievement of any projected
performance criteria where these are
indicated. ALSTOM reserves the right to
revise or change this data at any time without
further notice.
Alstom Grid Worldwide Contact Centre
www.grid.alstom.com/contactcentre/
Tel: +44 (0) 1785 250 070
www.alstom.com
GRID