Documente Academic
Documente Profesional
Documente Cultură
Table of Contents
C53000-H3040-C054-2
NOTE
i For your own safety, observe the warnings and safety instructions contained in this document, if available.
Target Audience
Protection system engineers, commissioning engineers, persons entrusted with the setting, testing and main-
tenance of automation, selective protection and control equipment, and operational crew in electrical installa-
tions and power plants.
Scope
This manual applies to the SIPROTEC 5 device family.
Further Documentation
[dwprefhw-221012-01.tif, 3, en_US]
• Device manuals
Each Device manual describes the functions and applications of a specific SIPROTEC 5 device. The printed
manual and the online help for the device have the same informational structure.
• Hardware manual
The Hardware manual describes the hardware building blocks and device combinations of the SIPROTEC 5
device family.
• Operating manual
The Operating manual describes the basic principles and procedures for operating and assembling the
devices of the SIPROTEC 5 range.
• Product information
The Product information includes general information about device installation, technical data, limiting
values for input and output modules, and conditions when preparing for operation. This document is
provided with each SIPROTEC 5 device.
• Engineering Guide
The Engineering Guide describes the essential steps when engineering with DIGSI 5. In addition, the Engi-
neering Guide shows you how to load a planned configuration to a SIPROTEC 5 device and update the
functionality of the SIPROTEC 5 device.
• SIPROTEC 5 catalog
The SIPROTEC 5 catalog describes the system features and the devices of SIPROTEC 5.
Indication of Conformity
This product complies with the directive of the Council of the European Communities
on harmonization of the laws of the Member States relating to electromagnetic
compatibility (EMC Directive 2014/30/EU) and concerning electrical equipment for use
within specified voltage limits (Low Voltage Directive 2014/35/EU).
This conformity has been proved by tests performed according to the Council Directive
in accordance with the product standard EN 60255-26 (for EMC directive) and with the
product standard EN 60255-27 (for Low Voltage Directive) by Siemens AG.
The device is designed and manufactured for application in an industrial environment.
The product conforms with the international standards of IEC 60255 and the German
standard VDE 0435.
Other Standards
IEEE Std C 37.90
The technical data of the product is approved in accordance with UL.
For more information about the UL database, see certified.ul.com
Select Online Certifications Directory and enter E194016 as UL File Number.
[ul_listed_c_us, 1, --_--]
Additional Support
For questions about the system, please contact your Siemens sales partner.
Support
Our Customer Support Center provides a 24-hour service.
Phone: +49 (180) 524-7000
Fax: +49 (180) 524-2471
E-Mail: support.energy@siemens.com
Training Courses
Inquiries regarding individual training courses should be addressed to our Training Center:
Siemens AG
Siemens Power Academy TD
Humboldtstraße 59
90459 Nürnberg
Germany
Notes on Safety
This document is not a complete index of all safety measures required for operation of the equipment (module
or device). However, it comprises important information that must be followed for personal safety, as well as
to avoid material damage. Information is highlighted and illustrated as follows according to the degree of
danger:
! DANGER
DANGER means that death or severe injury will result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! WARNING
WARNING means that death or severe injury may result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! CAUTION
CAUTION means that medium-severe or slight injuries can occur if the specified measures are not taken.
² Comply with all instructions, in order to avoid moderate or minor injuries.
NOTICE
NOTICE means that property damage can result if the measures specified are not taken.
² Comply with all instructions, in order to avoid property damage.
NOTE
i Important information about the product, product handling or a certain section of the documentation
which must be given particular attention.
Proper Use
The equipment (device, module) may be used only for such applications as set out in the catalogs and the
technical description, and only in combination with third-party equipment recommended and approved by
Siemens.
Problem-free and safe operation of the product depends on the following:
• Proper transport
• Proper storage, setup and installation
• Hazardous voltages may be present in equipment even after the supply voltage has been disconnected
(capacitors can still be charged).
• Operation of equipment with exposed current-transformer circuits is prohibited. Before disconnecting the
equipment, ensure that the current-transformer circuits are short-circuited.
• The limiting values stated in the document must not be exceeded. This must also be considered during
testing and commissioning.
The product contains, among other things, Open Source Software developed by third parties. The Open
Source Software used in the product and the license agreements concerning this software can be found in the
Readme_OSS. These Open Source Software files are protected by copyright. Your compliance with those
license conditions will entitle you to use the Open Source Software as foreseen in the relevant license. In the
event of conflicts between Siemens license conditions and the Open Source Software license conditions, the
Open Source Software conditions shall prevail with respect to the Open Source Software portions of the soft-
ware. The Open Source Software is licensed royalty-free. Insofar as the applicable Open Source Software
License Conditions provide for it you can order the source code of the Open Source Software from your
Siemens sales contact - against payment of the shipping and handling charges - for a period of at least 3 years
since purchase of the Product. We are liable for the Product including the Open Source Software contained in
it pursuant to the license conditions applicable to the Product. Any liability for the Open Source Software
beyond the program flow intended for the Product is explicitly excluded. Furthermore any liability for defects
resulting from modifications to the Open Source Software by you or third parties is excluded. We do not
provide any technical support for the Product if it has been modified.
When using DIGSI 5 in online mode, you are provided with the option to go to the main menu Show open
source software information and read and display the Readme_OSS file containing the original license text
and copyright information.
To do this, the following steps are necessary:
• Switch to online mode.
• Select the device.
NOTE
i To read the Readme_OSS file, a PDF viewer must be installed on the computer.
In order to operate SIPROTEC 5 devices, a valid DIGSI 5 license is required.
Preface.......................................................................................................................................................... 3
1 Process Bus................................................................................................................................................. 11
1.1 System Overview.............................................................................................................. 12
1.2 Configuration................................................................................................................... 13
1.2.1 Introduction................................................................................................................ 13
1.2.2 Structure of the Merging-Unit IID File........................................................................... 13
1.2.3 Information in IED Nodes............................................................................................. 15
1.2.3.1 Introduction...........................................................................................................15
1.2.3.2 IED-Node Attributes............................................................................................... 16
1.2.4 IED Subnodes.............................................................................................................. 16
1.2.4.1 Required Information in an SMV Control Block based on IEC 61850-7-4...................16
1.2.4.2 Required Information in an SMV Dataset based on IEC 61850-7-4........................... 17
1.2.4.3 Required Information in an LN TCTR Providing SMV Data.........................................17
1.2.4.4 Required Information in an LN TVTR Providing SMV Data.........................................18
1.2.5 Required Information in the Communication Node.......................................................20
1.3 Special Case IEC 61850-9-2 LE........................................................................................... 22
4 Restrictions................................................................................................................................................. 61
4.1 Restrictions....................................................................................................................... 62
[dw_overview, 2, en_US]
SE Sensor electronic
MU Merging unit
IED Intelligent Electronic Device
You can find more information on the connection possibilities of the different components and on the config-
uration in chapter 3 Parameterization of the Process Bus.
To measure currents and voltages in a primary system, a merging unit can use a vendor-specific primary
equipment. The merging unit provides the measured signals as Ethernet data packets as defined in the
IEC 61850-9-2 standard. To use these signals as voltage or current inputs in a SIPROTEC 5 device, the device
must subscribe to signals provided by the merging unit.
In this document, you can find information on how to configure a SIPROTEC 5 device that uses process-bus
inputs. To do this, IID files provided by a merging unit are used.
The IID files contain the following information:
• Self description of the signals provided by a merging unit
• Data-packet formats sent out by a merging unit in a standardized format
Every merging unit complying with the IEC 61850-9-2 standard can be used.
1.2 Configuration
1.2.1 Introduction
IID files deliver an IEC 61850 standard-compliant description of the SMV data packets provided by a particular
merging unit (MU). This IID file is required for every MU instance, because the data delivered by a merging
unit depend on configuration settings like primary rated values in a concrete installation and other settings.
This IID file provides a manufacturer-independent self description of a particular MU. This self description
contains the following major parts:
• Ethernet ports (referred to as access points in the following sections) provided by an MU and their
configuration data
• Assignment of access points to separated network sections (referred to as subnetworks in the following
chapters)
[dw_process-bus_egineering, 1, en_US]
IID files are XML files with a predefined structure. This structure is defined by a so-called XML schema.
This XML schema contains a detailed structure definition and allows a syntax check to see whether an IID file
complies to this definition.
[dw_Structure_IID_File, 1, en_US]
• Communication
The Communication node contains the assignment of the access points provided by the MU to the
communication-network topology.
The following data are defined in this node:
– IP addresses
– Assignment of access points to subnetworks
– MAC addresses used by the MU for sending SMV data
These addresses are multicast or unicast addresses.
• IED
The IED node contains the definition of the IED functions like provided CTs, VTs, and their settings. The
IED node is structured in so-called logical devices (LDs). These logical devices contain logical nodes (LNs).
Every CT or VT is represented by an LN. Every LN has a list of settings and outputs represented by data
objects (DOs).
Every logical device contains an LN0 node with definitions that are valid for the whole logical device. The
LN0 node contains the definition of every SMV stream sent out by the merging unit. This includes overall
definitions for this stream like sampling rate and the assembly of CT/VT signals included in this stream.
• DataTypeTemplates
The DataTypeTemplates node contains a hierarchical definition of the following types:
– LN types
– DO types used in a particular LN
– DA types (data-attribute types) used as data structures in a particular DO type
1.2.3.1 Introduction
[dw_Structure_IED_Node, 1, en_US]
For each access point providing SMV streams, the IED node contains an Access Point node with a Server node
as child node (1 access point per Ethernet port).
The Server node contains at least 1 LDevice node.
The LDevice node provides the SMV data stream. This node contains 1 SMVCB node (Sampled Measures
Control Block) per SMV data stream provided. The SMVCB node contains a reference to the DataSet. The
DataSet defines the CT/VT signals included in the data stream.
Each DataSet entry contains a reference to an SMV data object included in an LN TCTR or LN TVTR. A partic-
ular LN instance is characterized by the following attributes:
Attribute Description
Inst Instance number of the LN
This number must be unique within the instances of an LN class.
lnClass The LN class characterizes a particular class of LNs.
For merging units, at least the following classes are required:
• TCTR (current transformer)
• TVTR (voltage transformer)
• LPHD (name plate and health description)
Attribute Description
lnType Assigned type template
A particular LN instance cannot define DO instances that are not predefined
in the assigned type template. LN instances include all DO instances that are
defined in the assigned type template (even if the instance does not contain
a DOI definition).
desc Short text describing the particular instance
xPath Description
@name Name of the SMV control block
The name must be unique within a particular IED instance.
@smvID Name of the SMV data source
The name must be unique within the whole SCD file.
The merging unit uses the SMV ID in the sent data stream. Clients receiving
merging-unit data use the SMV ID to distinguish different data streams.
@smpRate Sampling rate
The unit of the sampling rate depends on the setting of the smpMod
attribute:
• SmpPerPeriod:
Samples per signal period of the rated frequency
• SmpPerSec:
Samples per s or Hz
• SecPerSmp:
Sampling interval in s
@ nofASDU Number of sample blocks transmitted in the same datagram
@ multicast The MU transmits SMV values using a multicast address.
The address range must be within 01:0C:CD:04:00:00 and 01:0C:CD:
04:FF:FF.
@smpMod Defines the unit for the sampling rate
When the attribute is missing, samples per period (SmpPerPeriod) are
assumed.
@datSet Dataset name defining the transmitted SMV values
SmvOpts/@* Attributes are not used for the client configuration, but shall be used in the
IEC 61850 System Configurator in order to allow or deny changing the
sampling rate (attribute smpRate) or changing the dataset content.
• The 2nd method addresses contained attributes using a functional constraint (FC). This functional
constraint must be defined in the DO type assigned to the referenced data-object instance (DOI).
Every dataset entry is included in an FCDA node.
Attribute Description
Inst Instance name of the parent LD of the referenced LN
Prefix A name grouping a set of LNs into an addressable group
The referenced LN must belong to this group.
lnClass LN class of referenced LN instance
LN classes are defined in IEC 61850-7-4.
For an MU application, at least the following LN classes are relevant:
• TCTR (current transformer)
• TVTR (voltage transformer)
• LPHD (name plate and health description)
lnInst LN instance number of the referenced LN
doName DOI name of the referenced DO instance
daName Referenced data attribute within the DO instance, mutually exclusive to the
Fc attribute
Fc Functional constraint name of assigned data attributes
This functional constraint is defined in the DO type assigned to the refer-
enced DOI characterized by the following attributes:
• ldInst
• prefix
• lnClass
• lnInst
• doName
Each attribute having an identical Fc attribute in the DO type is assigned to
the SMV data stream.
Structure
The Communication node contains a subnode Subnetwork.
[dw_Communication_Node, 1, en_US]
Subnetworks
IEC 61850 defines the use of named subnetworks for isolated network segments. The following figure gives
an example for a physical network interconnection between 5 merging units and 2 devices consuming the
SMV data streams provided by the merging units.
[dw_network-topology, 1, en_US]
The following table contains the resulting subnetworks including the assigned access points.
Every subnetwork must have a Subnetwork node under the Communication node.
An IID file contains only the own ports of a device. Therefore, the IID file for MU1 contains 2 Subnetwork
nodes for the subnetworks Switched1 and P2P_NET.
• SMV ID
• App ID
Therefore, using IEC 61850-9-2 LE simplifications allows an easier MU engineering, as the device engineering
tools must not handle structural changes in IID files.
The following minimum requirements must also be handled during configuration of the IEC 61850-9-2 LE
devices:
• IID export resulting in an IID file
This IID file contains the setting values that are currently configured.
• SCD/CID import in order to adapt settings changed in the substation configuration, for example:
– Multicast addresses
– SMV ID
– App ID
2.1 Introduction 24
2.2 Export from DIGSI 5 25
2.3 Definition of Client Access Points 29
2.4 System Configurator 30
2.5 Import into DIGSI 5 34
2.1 Introduction
This chapter describes the integration of the SIPROTEC 5 process-bus client board into substation engineering
with the following programs:
• DIGSI 5
• IEC 61850 System Configurator
You must distinguish between the export from DIGSI 5 to the IEC 61850 System Configurator and the import
from the IEC 61850 System Configurator into DIGSI 5.
The export from DIGSI 5 to the IEC 61850 System Configurator provides the required CT/VT channels by a
particular client device. You must interconnect these channels in the IEC 61850 System Configurator.
The import from the IEC 61850 System Configurator to DIGSI 5 provides the interconnections between
merging units and process-bus clients for the whole substation. DIGSI 5 must extract the mapping from the
client device of the current device project.
Particular process-bus client modules have multiple access points. Therefore, the mapping of current and
voltage channels to access points is also described in chapter 2.4 System Configurator.
[sc_Adding_process_bus_client, 1, en_US]
If you drag the process-bus module PB201 to the next free IO module slot, a process-bus support is added to
the device.
If you add a process-bus module, 24 additional analog inputs are added to the device. A maximum of
2 process-bus modules can be added to a device. You can find more information in chapter 4.1 Restrictions.
The analog inputs provided by a process-bus module can be used in the same manner as local analog inputs
provided by an IO module with CTs and/or VTs.
[sc_Process_bus_Measuring-points_routing, 1, en_US]
Signals provided by the process-bus module or by analog IO modules are visible as columns in this matrix. The
red rectangle shows currents from the process-bus module in expansion module 3 as an example.
² Click Add new to add a measuring point and select a connection type that complies to the process bus
(red ellipsis).
You can add entries in the signal columns from a process-bus module.
If no analog signals are used, you can use the measuring point that is already given for the compliant connec-
tion type.
[sc_Enable_IEC61850_support, 1, en_US]
[sc_IEC61850_IID_Export, 1, en_US]
² Select IID.
² To select the file path, click the … button.
- or -
² Change the file path manually.
² Click Export.
The exported IID file provides the required inputs to be interconnected to merging-unit signals using the
IEC 61850 System Configurator.
[dw_runtime-signal-flow, 1, en_US]
Figure 2-5 Runtime Signal Flow from a Merging Unit to a SIPROTEC 5 Application
The first mapping is done within the merging unit. Signals from the primary CTs and VTs are interconnected to
a merging unit. Current and voltage signals are represented by TCTR and TVTR instances within the IID file
describing the merging-unit instance.
A particular CT or VT can be identified by the following data:
• IED name of the merging-unit instance
• Access-point name providing the CT/VT instances
The CT/VT instances are collected in a dataset assigned to an SMV control block.
This SMV control block is located at this access point.
[sc_SystemConfigurator_Device_View, 1, en_US]
[sc_SystemConfigurator_routing_process_bus_connections, 1, en_US]
Figure 2-7 Routing of Process-Bus Connections in the IEC 61850 System Configurator
Interconnecting Signals
In the SMV view, you can interconnect CT or VT signals provided by a merging unit to an input of a process-
bus client.
The Destination catalog lists the devices containing a process-bus client.
Merging units providing signals are listed in the SMV messages table.
² To connect a source signal to an MU process-bus client, drag a signal from the Destination catalog into
the SMV messages table.
Drop the destination signal in the row of the source signal that must be connected to this destination.
The row containing the source signal is doubled. In this way, a source signal can be connected to multiple
destinations.
NOTE
i A signal can only be dropped, when both source and destination port are part of the same subnetwork.
If not, you can change the network configuration in the Network view. This view shows all defined subnet-
works.
[sc_ProConf_Import_SCD_file, 1, en_US]
[sc_ProConf_Imported_SCD_file, 1, en_US]
² To select the Client PB Module (Client Process-Bus Module) to be configured, click the corresponding
module name in the Client PB Module list.
Client PB Module names consist of the device name and the module mounting position in the device.
² In the Signals tab, you can check the routings made in the IEC 61850 System Configurator in the ChMap
column.
[sc_ProConf_Select_process_bus_module, 1, en_US]
NOTE
i Changes are supported for advanced users only and must be done via Syscon.
² In the Network tab, you can check and change the network topology.
[sc_ProConf_Network_configuration, 1, en_US]
NOTE
i If you change data like SMVid or MulticastAddresses, change these data also in the merging-unit configu-
rations.
Changes are supported for advanced users only and must be done via Syscon.
In this table, <N> stands for the mounting position of the PB201 module. In the DIGSI 5 Measuring-points
routing view, the mounting position of the PB201 module is displayed instead of <N>.
Interoperability
To allow interoperability between different CT and VT types used in merging units, you can configure the basic
characteristics of CTs and VTs for a particular merging-unit type.
² Open a metafile.
[sc_ProConf_open_Meta_File, 1, en_US]
[sc_ProConf_MU_specific_data, 1, en_US]
The current version of IEC 61850-9-2 does not support the exchange of measuring ranges and does not
support CT or VT transfer function data. These data can be maintained in a meta-data storage. These data are
evaluated during an interoperability test for a specific MU type. The shown data are only for information.
Siemens recommends not to change these data.
To provide interoperability between merging using different CT or VT technologies, these data are considered
within SIPROTEC 5.
The following figure shows an example for data of a configured client PB module in the Documentation tab.
[sc_ProConf_Documentation_PB_client_configuration, 1, en_US]
• Y cables
• PPS generators/clocks
• Merging units
• SIPROTEC 5 devices
[dw_components_overview, 1, en_US]
[sc_DIGSI4_Offline_Device_Settings, 1, --_--]
² Double-click Settings.
[sc_DIGSI_PowerSystemData1, 1, en_US]
NOTE
[sc_DIGSI_TimeSynchronization, 1, en_US]
[sc_DIGSI_properties, 1, en_US]
[sc_DIGSI4_IECEdition, 1, --_--]
Figure 3-7 Changing the IEC 61850 Edition for the IEC 61850 Station
[sc_DIGSI4_Communicator_tab, 1, --_--]
[sc_SystemConfigurator_Devices_View, 1, --_--]
[sc_SystemConfigurator_Report, 1, --_--]
[sc_SystemConfigurator_SMV_view, 1, en_US]
[sc_SystemConfigurator_configuration, 1, en_US]
NOTE
i The Config revision is used as a filter criterion in the PB201 process-bus client module. If the configuration
revision imported via an IID/CID file into the PB201 configuration and the configuration revision sent by the
merging unit do not match, the sent SMV data are blocked.
As IEC 61850-relevant data have been changed, the following dialog opens:
[sc_SystemConfigurator_Save_IECstation, 1, --_--]
[sc_DIGSI4_Update_tab, 1, --_--]
[sc_SystemConfigurator_Export_IEC_deviceconfig, 1, --_--]
² Select a storage path for the CID file and click Save.
3.4.1 Parameterizing
[sc_ProConf_Imported_CID, 1, --_--]
[sc_ProConf_ChMap, 1, en_US]
NOTE
i Choosing another PB client will lead to a loss of the current channel mapping, because the previous
channel mapping belongs to another client.
[sc_ProConf_Network, 1, en_US]
² In this tab, you can change the destination port Dest. Port.
If you change the Dest. Port, this cell gets highlighted as then, 2 ports are in the same subnetwork.
[sc_ProConf_Network_tab_DestPort, 1, --_--]
² Change the SubNet by typing the desired name into the SubNet column.
The highlighting of the Dest. Port cell disappears as the 2 ports are in different subnetworks now.
[sc_ProConf_Network_tab_SubNet, 1, --_--]
[sc_ProConf_Sync, 1, en_US]
NOTE
i All configured channels receive data. If the channels do not receive data, for example, because the MU has
a different frequency, no channel works.
The settings in the Sync tab are the same as the settings in the taskbar Settings -> Synchronization and
Startup.
Synchronization Modes
There are 2 synchronization modes:
• Use Buffer Level (BLC mode - Buffer Level Control Mode):
This mode is the basic sync mode for applications with 1 or 2 Siemens Merging Units. If you use this
mode, only the MU needs to be synchronized via PPS or IRIG-B
NOTE
i Make sure you select the file type *.pcf and not *.pcfx.
The file name must be device.pcf.
Documentation Tab
² Open the PCF file and change to the Documentation tab.
The Documentation tab is empty.
² To fill the Documentation tab, click View > Update Documentation.
[sc_ProConf_Documentation_tab, 1, --_--]
The version numbers indicated in the preceding figure are only examples.
² Open the homepage of PB201 now.
• Upload configuration:
Loads the configuration to the process bus
• Upload firmware:
Loads the firmware to the process bus
NOTE
Uploading Configuration
² Select Upload configuration to upload a PCF file.
[sc_PB201Homepage_Uploadconfiguration, 1, --_--]
² Click Browse..., select the desired PCF file, and click Upload.
² Reboot the device via Rebooting the device.
[sc_PB201Homepage_RebootingDevice, 1, --_--]
[sc_PB201Homepage_Welcome, 1, --_--]
Indicating PB Status
² Select PB Status to check the data.
[sc_PB201Homepage_PBStatus, 1, --_--]
NOTE
• Communication HW status:
– The shown SMV status should be OK.
– The columns from Channel (enabled) on display the received channel. They can all be config-
ured to port A, B, or C.
Uploading Firmware
² Select Upload firmware.
The selected files must have exactly the names indicated in this window.
[sc_PB201Homepage_UploadFirmware, 1, --_--]
[sc_PB201Homepage_Print, 1, --_--]
The data are displayed here in the same way as in ProConf in the Documentation tab.
4.1 Restrictions 62
4.1 Restrictions
SIPROTEC 5 Process-Bus Module PB201 V6.20 and higher
The following restrictions are known:
• The following versions are required:
– SIPROTEC 5 device firmware: at least V6.20 (06.04 7SL8)
– DIGSI 5: at least V6.20
– DIGSI 4 for MU: at least V04.90
• The process-bus functionality is approved with the Siemens EA merging unit (6MU805 with PPS input)
and conventional CTs /VTs only.
• Maximum allowed number of I/O extension modules additionally to 1 PB201 per SIPROTEC 5 device: 1
• No combination of SM values with values from conventional CTs/VTs due to needed synchronization
enhancement
• In normal operation, the transceiver must be removed from the service interface.
Close the cage with a dust cover.
• A minimum of 4 subsequent channels must be mapped via the configuration tool ProConf: 4 CTs or 4 VTs
• To use the IEC 61850 System Configurator for IEC 61850-9-2 Engineering, IEC 61850-8-1 must be used in
the SIPROTEC 5 device.
• The IP address of the service interface of PB201 is fixed. Therefore, max. 1 PB201 can be connected to a
PC at the same time.
You can find more information in chapter 3.5 Working with the PB201 Homepage.
• Diagnostics, FW update, and configuration update are possible only via the PB201 homepage.
Siemens MU 6MU805
The following components must be used for synchronization:
• 7XV5664-1AA00: GPS clock incl. accessories
• 7XV5450-0BA00: Mini Star-Coupler
NOTE