Siemens Industrial Spares -...

SIPROTEC 5Process Bus

V6.20 and higher

Manual

C53000-X3040-C054-1

Preface

Open Source Software

Table of Contents

Process Bus 1Process-Bus Client in SCD Files 2Parameterization of the Process Bus 3Restrictions 4

Siemens Industrial Spares

https://industrialautomation.co/product-category/siemens/page/5387/

iiNOTE

For your own safety, observe the warnings and safety instructions contained in this document, if available.

Disclaimer of LiabilityThis document has been subjected to rigorous technicalreview before being published. It is revised at regular inter-vals, and any modifications and amendments are includedin the subsequent issues. The content of this documenthas been compiled for information purposes only. AlthoughSiemens AG has made best efforts to keep the documentas precise and up-to-date as possible, Siemens AG shallnot assume any liability for defects and damage whichresult through use of the information contained herein.This content does not form part of a contract or of businessrelations; nor does it change these. All obligations ofSiemens AG are stated in the relevant contractual agree-ments.Siemens AG reserves the right to revise this documentfrom time to time.Document version: C53000-X3040-C054-1.02Edition: 07.2015Version of the product described: V6.20 and higher

CopyrightCopyright © Siemens AG 2015. All rights reserved.The disclosure, duplication, distribution and editing of thisdocument, or utilization and communication of the contentare not permitted, unless authorized in writing. All rights,including rights created by patent grant or registration of autility model or a design, are reserved.Registered TrademarksSIPROTEC®, DIGSI®, SIGUARD®, SIMEAS®, and SICAM®

are registered trademarks of Siemens AG. Any unauthor-ized use is illegal. All other designations in this documentcan be trademarks whose use by third parties for their ownpurposes can infringe the rights of the owner.

Preface

Purpose of the Manual

This manual describes the hardware of the SIPROTEC 5 device family and provides general information onthe product structure, the modules and technical data.

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, 2, en_US]

• Device manualsEach Device manual describes the functions and applications of a specific SIPROTEC 5 device. Theprinted manual and the online help for the device have the same informational structure.

• Hardware manualThe Hardware manual describes the hardware building blocks and device combinations of theSIPROTEC 5 device family.

• Operating manualThe Operating manual describes the basic principles and procedures for operating and assembling thedevices of the SIPROTEC 5 range.

SIPROTEC 5, Process Bus, Manual 3C53000-X3040-C054-1, Edition 07.2015



• Communication protocol manualsThe Communication protocol manuals contain a description of a specific protocol for communicationwithin the SIPROTEC 5 device family and to higher-level network control centers.

• Product informationThe Product information includes general information about device installation, technical data, limitingvalues for input and output modules, and conditions when preparing for operation. This document isprovided with each SIPROTEC 5 device.

• Engineering GuideThe Engineering Guide describes the essential steps when engineering with DIGSI 5. In addition, theEngineering Guide shows you how to load a planned configuration to a SIPROTEC 5 device and updatethe functionality of the SIPROTEC 5 device.

• DIGSI 5 online helpThe DIGSI 5 online help contains a help package for DIGSI 5 and CFC.The help package for DIGSI 5 includes a description of the basic operation of software, the DIGSI princi-ples and editors. The help package for CFC includes an introduction to CFC programming, basic exam-ples of working with CFC, and a reference chapter with all the CFC blocks available for the SIPROTEC 5range.

• SIPROTEC 5/DIGSI 5 TutorialThe tutorial on the DVD contains brief information about important product features, more detailed infor-mation about the individual technical areas, as well as operating sequences with tasks based on prac-tical operation and a brief explanation.

• SIPROTEC 5 catalogThe SIPROTEC 5 catalog describes the system features and the devices of SIPROTEC 5.

• Selection guide for SIPROTEC and ReyrolleThe selection guide offers an overview of the device series of the Siemens protection devices, and adevice selection table.

Indication of Conformity

This product complies with the directive of the Council of the European Communi-ties on harmonization of the laws of the Member States relating to electromagneticcompatibility (EMC Council Directive 2004/108/EC) and concerning electrical equip-ment for use within specified voltage limits (Low Voltage Directive 2006/95/EC).his conformity has been proved by tests performed according to the Council Direc-tive in accordance with the product standard EN 60255-26 (for EMC directive) andwith the product standard EN 60255-27 (for Low Voltage Directive) by Siemens AG.The device is designed and manufactured for application in an industrial environ-ment.The product conforms with the international standards of IEC 60255 and theGerman standard VDE 0435.

Other Standards

IEEE Std C 37.90The technical data of the product is approved in accordance with UL.For more information about the UL database, see www.ul.comSelect Online Certifications Directory and enter E194016 as UL File Number.

IND. CONT. EQ.69CA

[ul_listed_c_us, 1, --_--]

Preface

4 SIPROTEC 5, Process Bus, ManualC53000-X3040-C054-1, Edition 07.2015

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-7000Fax: +49 (180) 524-2471E-Mail: [email protected]

Training Courses

Inquiries regarding individual training courses should be addressed to our Training Center:

Siemens AGSiemens Power Academy TD Humboldtstraße 5990459 NürnbergGermany Phone: +49 (911) 433-7415Fax: +49 (911) 433-7929E-Mail: [email protected]: www.siemens.com/poweracademy

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, aswell as to avoid material damage. Information is highlighted and illustrated as follows according to the degreeof danger:

! DANGERDANGER 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.

! WARNINGWARNING 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.

! CAUTIONCAUTION 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.

Preface



mailto:[email protected]

mailto:[email protected]

http://www.siemens.com/poweracademy


NOTICENOTICE means that property damage can result if the measures specified are not taken.

² Comply with all instructions, in order to avoid property damage.

iiNOTE

Important information about the product, product handling or a certain section of the documentation whichmust be given particular attention.

Qualified Electrical Engineering Personnel

Only qualified electrical engineering personnel may commission and operate the equipment (module, device)described in this document. Qualified electrical engineering personnel in the sense of this manual are peoplewho can demonstrate technical qualifications as electrical technicians. These persons may commission,isolate, ground and label devices, systems and circuits according to the standards of safety engineering.

Proper Use

The equipment (device, module) may be used only for such applications as set out in the catalogs and thetechnical description, and only in combination with third-party equipment recommended and approved bySiemens.Problem-free and safe operation of the product depends on the following:• Proper transport

• Proper storage, setup and installation

• Proper operation and maintenance

When electrical equipment is operated, hazardous voltages are inevitably present in certain parts. If properaction is not taken, death, severe injury or property damage can result:• The equipment must be grounded at the grounding terminal before any connections are made.

• All circuit components connected to the power supply may be subject to dangerous voltage.

• 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 theequipment, 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 duringtesting and commissioning.

Preface


Open Source Software

Among other things, this product contains Open Source Software that was developed by third parties. TheOpen Source Software included with this product and the relevant Open Source Software license agreementcan be found in Readme_OSS. The Open Source Software program is protected by copyright. You arepermitted to use the Open Source Software according to the Open Source Software license agreement.Should contradictions occur between the Open Source Software license conditions and the Siemens licenseconditions applicable to the product, the Open Source Software license agreement with respect to the OpenSource Software shall prevail. The Open Source Software is provided free of charge. If stipulated by theOpen Source Software license agreement, the source text of the software is available until the end of the thirdyear after purchasing the product. Shipping charges will apply separately. We are liable for the productincluding the Open Source Software according to the license agreement for the product. Any liability arisingfrom the use of the Open Source Software that exceeds the intended program flow of the product, as well asliability for defects that were caused by changes made to the Open Source Software, is excluded. If theproduct was modified, we cannot provide technical support.When using DIGSI 5 in online mode, you are provided with the option to go to the main menu Show Opensource information and read and display the Readme_OSS file containing the original license text and copy-right information. To do this, a PDF viewer must be installed on the computer. In order to operate SIPROTEC5 devices, a valid DIGSI 5 license is required (trial, full, or compact version).




Table of Contents

Preface................................................................................................................................................................3

Open Source Software........................................................................................................................................7

1 Process Bus......................................................................................................................................................111.1 Overview...............................................................................................................................121.2 IID Files.................................................................................................................................131.2.1 Introduction..................................................................................................................... 131.2.2 Structure of the Merging-Unit IID File............................................................................. 131.2.3 Information in IED Nodes................................................................................................151.2.3.1 Introduction................................................................................................................151.2.3.2 IED-Node Attributes.................................................................................................. 161.2.4 IED Subnodes.................................................................................................................161.2.4.1 Required Information in an SMV Control Block.........................................................161.2.4.2 Required Information in an SMV Dataset..................................................................171.2.4.3 Required Information in an LN TCTR Providing SMV Data...................................... 171.2.4.4 Required Information in an LN TVTR Providing SMV Data.......................................181.2.5 Required Information in the Communication Node......................................................... 201.3 Special Case IEC 61850-9-2 LE...........................................................................................23

2 Process-Bus Client in SCD Files...................................................................................................................... 252.1 Introduction...........................................................................................................................262.2 Export from DIGSI 5............................................................................................................. 272.3 Definition of Client Access Points.........................................................................................312.4 System Configurator.............................................................................................................322.5 Import into DIGSI 5...............................................................................................................36

3 Parameterization of the Process Bus................................................................................................................433.1 Parameterizing the Merging Unit 7SC805 in DIGSI 4...........................................................443.2 Parameterizing in the IEC 61850 System Configurator........................................................493.3 Parameterizing in ProConf....................................................................................................543.4 Working with the PB201 Homepage.....................................................................................57

4 Restrictions....................................................................................................................................................... 634.1 Restrictions...........................................................................................................................64




Process Bus

1.1 Overview 12

1.2 IID Files 131.3 Special Case IEC 61850-9-2 LE 23

1




Overview

This document describes the usage of SIPROTEC 5 devices in a process-bus environment.SIPROTEC 5 provides the process-bus I/O module PB201. With this module, SIPROTEC 5 provides aprocess-bus client. The module PB201 allows a subscription of current and voltage signals provided by amerging unit (MU) complying with the IEC 61850-9-2 standard.

The following figure shows the general approach of the IEC 61850-9-2 standard for interconnection a mergingunit providing Sampled Measured Values (SMV) and a process-bus client that uses these Sampled MeasuredValues.

[dw_overview, 1, en_US]

Figure 1-1 Overview

SE Sensor electronicFO Fiber opticMU Merging unitIED Intelligent Electronic Device

To measure currents and voltages in a primary system, a merging unit can use a vendor-specific primaryequipment. The merging unit provides the measured signals as Ethernet data packets as defined in theIEC 61850-9-2 standard. To use these signals as voltage or current inputs in a SIPROTEC 5 device, thedevice 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-businputs. 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.1

Process Bus1.1 Overview


IID Files

Introduction

IID files deliver an IEC 61850 standard-compliant description of the SMV data packets provided by a partic-ular merging unit (MU). This IID file is required for every MU instance, because the data delivered by amerging unit depend on configuration settings like primary rated values in a concrete installation and othersettings.This IID file provides a manufacturer-independent self description of a particular MU. This self descriptioncontains 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 followingchapters)

• Description of current transformers (CT)/voltage transformers (VT) providing signals

• Description of data packets delivered by an MU

These IID files are used in a System Configurator in order to interconnect current and voltage signalsprovided by merging units to devices that are consuming these MU signals. This is done in order to substitutelocal CT/VT inputs with data streams received from an MU. These devices are further named as process-busclients.These process-bus clients also provide an IID file describing the required CT/VT inputs.You use the System Configurator tool to interconnect the required CT/VT inputs of process-bus clients to thesignals provided by a merging unit.

[dw_Process_Bus_Egineering, 1, en_US]

Figure 1-2 Basic Engineering Workflow Defined in IEC 61850

Structure of the Merging-Unit IID File

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 filecomplies to this definition.

1.2

1.2.1

1.2.2

Process Bus1.2 IID Files




[dw_Structure_IID_File, 1, en_US]

Figure 1-3 Top-Level Structure of IID Files

The IID file contains the following nodes:• Substation

The Substation node contains definitions regarding the assignment of a particular MU to a primary-system equipment like voltage level, bay, and primary CTs or VTs.

• CommunicationThe Communication node contains the assignment of the access points provided by the MU to thecommunication-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 dataThese addresses are multicast or unicast addresses.

• IEDThe IED node contains the definition of the IED functions like provided CTs, VTs, and their settings. TheIED 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 representedby data objects (DOs).Every logical device contains an LN0 node with definitions that are valid for the whole logical device. TheLN0 node contains the definition of every SMV stream sent out by the merging unit. This includes overalldefinitions for this stream like sampling rate and the assembly of CT/VT signals included in this stream.

• DataTypeTemplatesThe 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



Information in IED Nodes

Introduction

[dw_Structure_IED_Node, 1, en_US]

Figure 1-4 Basic Structure of an IED Node in an IID File

For each access point providing SMV streams, the IED node contains an Access Point node with a Servernode 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 MeasuresControl Block) per SMV data stream provided. The SMVCB node contains a reference to the DataSet. TheDataSet 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. Aparticular LN instance is characterized by the following attributes:

Table 1-1 Attributes of an LN Instance

Attribute DescriptionInst 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)

1.2.3

1.2.3.1





Attribute DescriptionlnType Assigned type template

A particular LN instance cannot define DO instances that are not prede-fined in the assigned type template. LN instances include all DO instancesthat are defined in the assigned type template (even if the instance doesnot contain a DOI definition).

desc Short text describing the particular instance

IED-Node Attributes

IEC 61850 defines optional attributes for the vendor and the revision at the IED node. In order to identify thevendor of a particular merging unit, these attributes must be filled. Otherwise, merging units that comply withIEC 61850-9-2 LE (Lite Edition) and that are using a static IID file for self description cannot be distinguishedbetween different vendors.

IED Subnodes

Required Information in an SMV Control Block

An LN0 of a particular logical device contains SMV control blocks. An SMV control block must be defined forevery SMV data stream sent out by a merging unit.

Table 1-2 Required Information in an SMV Control Block

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. Clientsreceiving merging-unit data use the SMV ID to distinguish different datastreams.

@smpRate Sampling rateThe unit of the sampling rate depends on the setting of the smpModattribute:• 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 rateWhen the attribute is missing, samples per period (SmpPerPeriod) areassumed.

@datSet Dataset name defining the transmitted SMV valuesSmvOpts/@* 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 thesampling rate (attribute smpRate) or changing the dataset content.

1.2.3.2

1.2.4

1.2.4.1



Required Information in an SMV Dataset

The definition of the SMV dataset describes the SMV data included in the datagram of the SMV control blockthat references the dataset. It defines also the content of the sent data stream.There are 2 methods for selecting the contained data:• The 1st method addresses a particular data attribute included in the sent SMV datagram by the attribute

name.

• The 2nd method addresses contained attributes using a functional constraint (FC). This functionalconstraint must be defined in the DO type assigned to the referenced data-object instance (DOI).

Every dataset entry is included in an FCDA node.

Table 1-3 Attributes of a Dataset Entry

Attribute DescriptionInst Instance name of the parent LD of the referenced LNPrefix 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 LNdoName DOI name of the referenced DO instancedaName Referenced data attribute within the DO instance, mutually exclusive to the

Fc attributeFc 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• doNameEach attribute having an identical Fc attribute in the DO type is assigned tothe SMV data stream.

Required Information in an LN TCTR Providing SMV Data

The following table describes the required settings in an LN TCTR used in a merging unit in order to describethe provided sample data.

Table 1-4 Settings of a CT (LN TCTR)

DOI SDI DAI DescriptionAmpSv sVC scaleFactor The scale factor defines the fractional of 1 A representing the value of

1 LSBFor example: a value of 0.01 means that a primary value of 1 A isrepresented by a value of 100 LSB in the datagram sent by the mergingunit.

Offset Currently not used for process-bus client configurationReserved for offset compensation values inside the merging unit

1.2.4.2

1.2.4.3





DOI SDI DAI DescriptionARtg setMag F Primary rated current with unit defined in SIUnit and multiplier defined in

multiplierUnits SIUnit Unit shall be A.

Other units lead to warnings during the import.multiplier Defines the scaling of the setMag value

The following value results:val = setMag ⋅ 10multiplier

minVal F Minimum possible setting valuemaxVal F Maximum possible setting valuestepSize – Only required for merging-unit configuration

Not used in process-bus client configurationHzRtg setMag F Rated frequency for the current input

This attribute is required, if the smpMod attribute of the referencingSMV control block is set to SmpPerPeriod (default value, if the smpModattribute is missing). If smpMod is set to another value, this attribute canbe missed.

Units SIUnit Unit Hz is expected.Another value or a missing unit value leads to warnings during theSCD/CID import.

multiplier –Acc setVal Setting is contained in the data name space SIEMENS EXT

Rated accuracy class of the current input according to definitions inIEC 61869-90.2S/1P, for example, means the following:• Class 0.2 for the measuring range• Class 1P for the protection range

Clip setMag F Clipping value as defined in IEC 61869-9If unit A is used, this setting means an absolute primary current.If the empty unit is used, this setting means the overcurrent factor rela-tive to the rated current.The full-scale value of the ADC used in a merging unit shall correspondto:• Sqrt(2)1 ⋅ Clip (with unit A)• Sqrt(2) ⋅ Clip ⋅ ARtg (with empty unit)

Units SIUnit Unit of the clipping value: A or empty is allowed.Another value leads to a warning during the import.

multiplier –TdMax setMag F Setting is contained in the data name space SIEMENS EXT

Maximum time delay as defined in IEC 61869-9TdMin setMag f Setting is contained in the data name space SIEMENS EXT

Minimum time delay as defined in IEC 61869-9

Required Information in an LN TVTR Providing SMV Data

The following table describes the required settings in an LN TCTR used in a merging unit in order to describethe provided sample data.

1.2.4.4

1 Sqrt = square root



Table 1-5 Settings of a VT (LN TVTR)

DOI SDI DAI DescriptionVolSv sVC scaleFactor Scale factor for calculation of the resolution of the transmitted voltage

valuesThe scale factor defines the value of 1 LSB of the sent sample values:LSB = 1 V ⋅ scaleFactor

offset Currently not used for process-bus client configurationReserved for offset compensation values inside the merging unit.

VRtg setMag f Primary rated voltage with unit defined in SIUnit and multiplier definedin multiplier

Units SIUnit Unit shall be V.Other units lead to warnings during the import.

multiplier Defines the scaling of the setMag valueThe following value results:val = setMag ⋅ 10multiplier

minVal f Minimum possible setting valuemaxVal f Maximum possible setting valuestepSize - Only required for merging-unit configuration

Not used in process-bus client configurationHzRtg setMag f Rated frequency for this voltage input

This attribute is required, if the smpMod attribute of the referencingSMV control block is set to SmpPerPeriod (default value, if the smpModattribute is missing). If smpMod is set to another value, this attribute canbe missed.

Units SIUnit Unit Hz is expected.Another value or a missing unit value leads to warnings during theSCD/CID import.

multiplier Defines the scaling of the setMag valueThe following value results:val = setMag ⋅ 10multiplier

Acc setVal Setting is contained in the data name space SIEMENS EXTRated accuracy class of voltage input according to definitions inIEC 61869-9For example, 0.2S means class 0.2 for the measuring range.

Clip setMag f Setting is contained in the data name space SIEMENS EXTClipping value as defined in IEC 61869-9If unit V is used, this setting means an absolute primary voltage.If the empty unit is used, this setting means the overvoltage factor rela-tive to the rated voltage.The full-scale value of the ADC used in a merging unit shall correspondto:• Sqrt(2) ⋅ Clip (with unit V)• Sqrt(2) ⋅ Clip ⋅ ARtg (with empty unit)

Units SIUnit Unit of the clipping value: V or empty is expected.See the preceding sections for information on the meaning.

multiplier Defines the scaling of the setMag value.The following value results:val = setMag ⋅ 10multiplier





DOI SDI DAI DescriptionTdMax setMag f Setting is contained in the data name space SIEMENS EXT

Maximum time delay as defined in IEC 61869-9If the value is not available, the worst case is assumed and MUsamples will be delayed.

TdMin setMag f Setting is contained in the data name space SIEMENS EXTMinimum time delay as defined in IEC 61869-9

Required Information in the Communication Node

Structure

The Communication node contains a subnode Subnetwork.

[dw_Communication_Node, 1, en_US]

Figure 1-5 Structure of the Communication Node

Subnetworks

IEC 61850 defines the use of named subnetworks for isolated network segments. The following figure givesan example for a physical network interconnection between 5 merging units and 2 devices consuming theSMV data streams provided by the merging units.

1.2.5



[dw_network_topology, 1, en_US]

Figure 1-6 Example of a Network Topology

The following table contains the resulting subnetworks including the assigned access points.

Table 1-6 Subnetwork Assignment of Access Points for a Given Example

Subnetwork Device Access Point RemarkSwitched1 MU1 AP1 Source

MU2 AP1 SourceMU3 AP1 SourceDev1 PB3_A DestinationDev2 PB3_A Destination

PTP_NET MU1 AP1 SourceDev2 PB3_B Destination

RING_NET MU4 AP1 SourceMU5 AP1 SourceDev2 PB3_C Destination

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 Subnetworknodes for the subnetworks Switched1 and PTP_NET.





The resulting XML file look as follows:

[sc_XML, 1, --_--]

Figure 1-7 XML Structure



Special Case IEC 61850-9-2 LE

IEC 61850-9-2 LE (Lite Edition) was defined in order to simplify the device engineering for merging units. Theintention was to use static IID files for merging units having a fixed configuration with the following properties:• Fixed dataset with 4 currents and 4 voltages

• Fixed SMV configuration with 4-kHz sampling rate (fn = 50 Hz) or 4.8-kHz sampling rate (fn = 60 Hz)

• Fixed sample scaling

However, you must configure the following data also for IEC 61850-9-2 LE installations:• TCTR/TVTR settings

• Multicast/Unicast addresses

• SMV ID

• App ID

Therefore, using IEC 61850-9-2 LE simplifications allows an easier MU engineering, as the device engi-neering 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 LEdevices:• 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

1.3

Process Bus1.3 Special Case IEC 61850-9-2 LE




Process-Bus Client in SCD Files

2.1 Introduction 26

2.2 Export from DIGSI 5 272.3 Definition of Client Access Points 31

2.4 System Configurator 322.5 Import into DIGSI 5 36

2




Introduction

This chapter describes the integration of the SIPROTEC 5 process-bus client board into substation engi-neering 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 importfrom 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 aparticular 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 betweenmerging units and process-bus clients for the whole substation. DIGSI 5 must extract the mapping from theclient device of the current device project.Particular process-bus client modules have multiple access points. Therefore, the mapping of current andvoltage channels to access points is also described in chapter 2.4 System Configurator.

2.1

Process-Bus Client in SCD Files2.1 Introduction


Export from DIGSI 5

In order to use a SIPROTEC 5 device as a process-bus client, you must configure the process-bus support ina device first.

Adding a Process-Bus Module to a Device

² Drag a process-bus module PB201 into the device HW configuration as shown in the following figure.

[sc_Adding_process_bus_client, 1, en_US]

Figure 2-1 Adding a Process-Bus Client Support into a SIPROTEC 5 Device

If you drag the process-bus module PB201 to the next free IO module slot, a process-bus support is added tothe device.If you add a process-bus module, 24 additional analog inputs are added to the device. A maximum of2 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 inputsprovided by an IO module with CTs and/or VTs.

Using Process-Bus Signals

² To use process-bus signals in a SIPROTEC 5 device, add available channels from a process-bus clientmodule to a measuring point in the Measuring-points routing matrix.If you configure a process-bus module in the hardware configuration, 12 columns are added to theCurrent-measuring points and to the Voltage-measuring points routing matrix for each process-busmodule.

2.2

Process-Bus Client in SCD Files2.2 Export from DIGSI 5




[sc_Process_bus_Measuring-points_routing, 1, en_US]

Figure 2-2 Example for Measuring-Points Routing for Process-Bus Inputs

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.

Configuring IEC 61850

If a device uses the process bus, you must configure at least 1 IEC 61850-8-1 interface in order to enable theIID/CID export. To configure the IEC 61850 interface, proceed as follows:² Select the Ethernet interface for which you want to enable the IEC 61850-8-1 support.

In the following figure, this is shown as an example for port J.

² In the Properties tab, in the Communication protocols section, activate the IEC 61850-8-1 support byactivating the related check box.



[sc_Enable_IEC61850_support, 1, en_US]

Figure 2-3 Enabling IEC 61850-8-1 Support

Exporting an IID File

If you have finished the device configuration, you must export an IID file from the device project in order toprovide the required process-bus inputs for this device to the substation engineering. To export the IID file,proceed as follows:² Right-click the device in the project tree and select Export… in the context menu.





The following export dialog appears:

[sc_IEC61850_IID_Export, 1, en_US]

Figure 2-4 IEC 61850 IID Export

² 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 theIEC 61850 System Configurator.



Definition of Client Access Points

To allow a mapping between process-bus module slots used in DIGSI 5 and in the IEC 61850 System Config-urator, a naming convention is required. Access-point names are assigned only in DIGSI 5 during device HWconfiguration.This naming convention allows to reassign a particular access-point name in an SCD file exported by theIEC 61850 System Configurator to a particular process-bus module slot in ProConf and DIGSI 5.The following access-point name syntax is defined:PB<Slot ID>_<Port ID>With:

Slot ID Position of the process-bus module in the configured device hardware:• Position 0: Reserved for the CPU• Position 1: IO module in the base module• Position 2: Power-supply module in the base module• Position 3: 1st expansion module• Position 4: 2nd expansion module, …

Port ID Name of the physical Ethernet port printed on the rear plate of a PB201 moduleValid names: A, B, CPort D is reserved for the service interface.

2.3

Process-Bus Client in SCD Files2.3 Definition of Client Access Points




System Configurator

The following figure describes the basic principle for signal interconnection between an MU input and aprocess-bus client input in a SIPROTEC 5 device.

[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 interconnectedto a merging unit. Current and voltage signals are represented by TCTR and TVTR instances within theIID 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 instancesThe CT/VT instances are collected in a dataset assigned to an SMV control block.This SMV control block is located at this access point.

• LN class and LN instance of a particular LN instance

If provided by the IED configurator of a merging unit, the substation section of the IID file describes the rela-tion between the primary equipment and the LN instances.The IEC 61850 System Configurator is used to interconnect LN instances provided by merging units to LNinstances in a process-bus client representing defined measuring points of a SIPROTEC 5 device. TheLN instances are provided by merging units via the IEC 61850-9-2 SMV protocol.

2.4

Process-Bus Client in SCD Files2.4 System Configurator


[sc_SystemConfigurator_Device_View, 1, en_US]

Figure 2-6 IEC 61850 System Configurator Devices View

Importing an IID File

² To import an IID file to a merging unit or process-bus client device, right-click the station in the Namecolumn and select Add IEC 61850 device(s).

² After importing devices that must be interconnected, change to the SMV view.





[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 multipledestinations.



iiNOTE

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.





Import into DIGSI 5

To allow process-bus configuration in DIGSI 5, an intermediate solution with an external tool named ProConfis used.You can import IID, CID, or SCD files to ProConf.You can find more information on working with ProConf in chapter 3.3 Parameterizing in ProConf .

Importing and Processing SCD Files

² Open the ProConf tool.

² Click File > Import > SCD.

[sc_ProConf_Import_SCD_file, 1, en_US]

Figure 2-8 Importing an SCD File in ProConf

² Select the SCD file to be imported.

The Signals tab is filled with all process-bus channels provided by merging units that are contained in theimported SCD file.

2.5

Process-Bus Client in SCD Files2.5 Import into DIGSI 5


[sc_ProConf_Imported_SCD_file, 1, en_US]

Figure 2-9 Imported SCD File in ProConf

² To select the Client PB Module (Client Process-Bus Module) to be configured, click the correspondingmodule 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 and change the routings made in the IEC 61850 System Configuratorin the ChMap column.

[sc_ProConf_Select_process_bus_module, 1, en_US]

Figure 2-10 Selecting the Process-Bus Module in ProConf

² In the Network tab, you can check and change the network topology.





[sc_ProConf_Network_configuration, 1, en_US]

Figure 2-11 Network Configuration in ProConf

iiNOTE

If you change data like SMVid or MulticastAddresses, change these data also in the merging-unit configu-rations.

Importing and Processing IID or CID Files

If you import IID or CID files directly in ProConf, you can avoid assigning channels provided by a merging unitand channels needed in a process-bus client module. You can import several IID or CID files.² Open the ProConf tool.

² Click File > Import > IID.

- or -

² Click File > Import > CID.

² To assign a signal provided by a merging unit to a particular channel on a PB201 module, select theSignals tab and enter the PB201 channel number in the ChMap column.You can find the PB201 channel number in the DIGSI 5 Measuring-points routing view. The PB201channels are displayed in the DIGSI 5 Measuring-points routing view as columns of available inputsignals. The channel number is displayed with the following column name in the DIGSI 5 Measuring-points routing view (see 2.2 Export from DIGSI 5):

Column Name in Measuring-Points Routing View Channel Number<N>PBA1 1<N>PBA2 2<N>PBA3 3<N>PBA4 4<N>PBA5 5<N>PBA6 6<N>PBA7 7<N>PBA8 8<N>PBA9 9<N>PBA10 10<N>PBA11 11<N>PBA12 12<N>PBV1 13<N>PBV2 14<N>PBV3 15



Column Name in Measuring-Points Routing View Channel Number<N>PBV4 16<N>PBV5 17<N>PBV6 18<N>PBV7 19<N>PBV8 20<N>PBV9 21<N>PBV10 22<N>PBV11 23<N>PBV12 24

In this table, <N> stands for the mounting position of the PB201 module. In the DIGSI 5 Measuring-pointsrouting 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 thebasic characteristics of CTs and VTs for a particular merging-unit type.² Open a metafile.

[sc_ProConf_open_Meta_File, 1, en_US]

Figure 2-12 Opening a Metafile

² Select the Meta Data tab.





[sc_ProConf_MU_specific_data, 1, en_US]

Figure 2-13 Editor for MU-Specific Data in ProConf

The current version of IEC 61850-9-2 does not support the exchange of measuring ranges and does notsupport CT or VT transfer function data. These data can be maintained in a meta-data storage. These dataare 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 consideredwithin 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]

Figure 2-14 Documentation of a Client PB Module Configuration in ProConf

² Store a finished configuration in a Process Bus Configuration file (*.pcf).

² Load this file on a client PB module with a Web browser using the homepage of the client PB module.





Parameterization of the Process Bus

3.1 Parameterizing the Merging Unit 7SC805 in DIGSI 4 44

3.2 Parameterizing in the IEC 61850 System Configurator 493.3 Parameterizing in ProConf 54

3.4 Working with the PB201 Homepage 57

3




Parameterizing the Merging Unit 7SC805 in DIGSI 4

² Open the DIGSI 4 Manager.

² Open the device in Offline mode.

[sc_DIGSI4_Offline_Device_Settings, 1, --_--]

Figure 3-1 Offline View of a Device

² Double-click Settings.

[sc_DIGSI4_Offline_Device_Settings_Select _Function, 1, --_--]

Figure 3-2 Settings of a Device

² Double-click Power System Data 1.

Parameterizing the Power System Data 1

² Set the values in the Power System Data 1 dialog.

iiNOTE

In the tab SMV-settings, set the parameter 0454A Number of ASDU to 1.

3.1

Parameterization of the Process Bus3.1 Parameterizing the Merging Unit 7SC805 in DIGSI 4


[sc_DIGSI_PowerSystemData1, 1, en_US]

Figure 3-3 Power System Data Dialog

Parameterizing the Time Synchronization

² In the DIGSI 4 Manager, select Time Synchronization.

² Set the values for the time synchronization as follows:





[sc_DIGSI_TimeSynchronization, 1, en_US]

Figure 3-4 Time Synchronization & Time Format Dialog

Parameterizing the Device Properties

² In the DIGSI 4 Manager, right-click in the right window section and select Object Properties...

² In the IEC 61850 settings tab, select the IEC 61850 Edition 2.

² Open the Communication parameters tab to see the following data:



[sc_DIGSI_properties, 1, en_US]

Figure 3-5 Communication Parameters Tab

² Enter an IED name.

² Click OK.

IEC 61850 station

² In DIGSI 4, right-click the device and select Insert New Object > IEC 61850 station.

² Right-click the IEC 61850 station and select Properties....

² Change the edition of the IEC 61850 station to IEC 61850 Edition 2 and click Convert Edition.

[sc_DIGSI4_IECEdition, 1, --_--]

Figure 3-6 Changing the IEC 61850 Edition for the IEC 61850 Station

² Open the Communicator tab and select the MUs.





[sc_DIGSI4_Communicator_tab, 1, --_--]

Figure 3-7 Communicator Tab

² Click Add and then click OK.

² Open the IEC 61850 station and enter a storage path for the SCD file.

The IEC 61850 System Configurator opens.



Parameterizing in the IEC 61850 System Configurator

² Open the IEC 61850 station in the IEC 61850 System Configurator.

[sc_SystemConfigurator_Devices_View, 1, --_--]

Figure 3-8 Devices View

² Open the SMV view.

Only 1 MU is displayed.² Close the IEC 61850 station and reopen it again from DIGSI 4.

The IEC 61850 station now contains all MUs.A report opens indicating that the MAC address is not unique.

[sc_SystemConfigurator_Report, 1, --_--]

Figure 3-9 Report

² Open the MU.

² In the Properties section under Parameter, click ....

3.2

Parameterization of the Process Bus3.2 Parameterizing in the IEC 61850 System Configurator




[sc_SystemConfigurator_SMV_view, 1, en_US]

Figure 3-10 SMV View - Properties

The following dialog opens:

[sc_SystemConfigurator_configuration, 1, en_US]

² Change the MAC addresses.

² Check the SMV ID and the Config revision.

iiNOTE

The Config revision is used as a filter criterion in the PB201 process-bus client module. If the configurationrevision imported via an IID/CID file into the PB201 configuration and the configuration revision sent by themerging unit do not match, the sent SMV data are blocked.

² Save the changes.



As IEC 61850-relevant data have been changed, the following dialog opens:

[sc_SystemConfigurator_Save_IECstation, 1, --_--]

Figure 3-11 Save IEC 61850 Station Prompt Dialog

² Confirm this dialog with OK.

² Close the IEC 61850 System Configurator and switch back to DIGSI 4.

² Right-click the device and select Object Properties...

² Select the Update tab.

The check boxes of the MUs are checked.





[sc_DIGSI4_Update_tab, 1, --_--]

Figure 3-12 Update Tab

² Click Update selected parameter sets and then click OK.

Exporting CID files

² In the IEC 61850 System Configurator, right-click the IEC 61850 station (for example, MU01 in thefollowing figure) and select Export IEC 61850 device configuration.



[sc_SystemConfigurator_Export_IEC_deviceconfig, 1, --_--]

Figure 3-13 Exporting to CID File

² Select a storage path for the CID file and click Save.





Parameterizing in ProConf

Importing the CID file into ProConf

² Open ProConf.

² Click File > Import...-> CID and select the CID file.

[sc_ProConf_Imported_CID, 1, --_--]

Figure 3-14 CID File Imported

² Map the channel in the column ChMap manually or automatically.Use the manual mapping, for example, if only TCTRs are needed. Otherwise, use the Preset sequential.To do the mapping, right-click the cell in the ChMap column and select Preset sequential.

The Client PB Module name is created as a default.

[sc_ProConf_ChMap, 1, en_US]

Figure 3-15 Changed ChMap

Parameterizing in the Network Tab

² Open the Network tab.

[sc_ProConf_Network, 1, en_US]

Figure 3-16 Network Tab

3.3

Parameterization of the Process Bus3.3 Parameterizing in ProConf


² 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, --_--]

Figure 3-17 Network Tab - Dest. Port Highlighted

² 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, --_--]

Figure 3-18 Network Tab - Changed SubNet Name

Parameterizing in the Sync Tab

² If you use more than 1 MU, open the Sync tab and activate the Start Synchronously on all channelscheck box.

[sc_ProConf_Sync, 1, en_US]

Figure 3-19 Sync Tab

iiNOTE

All configured channels receive data. If the channels do not receive data, for example, because the MUhas a different frequency, no channel works.The settings in the Sync tab are the same as the settings in the taskbar Settings -> Synchronization andStartup.

Saving a PCF File

² Select File > Save PCF to save the PCF file.

² Select a file type.





iiNOTE

Make sure you select the file type *.pcf and not *.pcfx.The file name must be device.pcf.

² Select a storage path for the file.

² Close ProConf and reopen it.

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, --_--]

Figure 3-20 Documentation Tab

The version numbers indicated in the preceding figure are only examples.² Open the homepage of PB201 now.



Working with the PB201 Homepage

Structure of the Homepage

The tree in the homepage contains the following parts:• PB status:

Shows configuration and state information

• Upload configuration:Loads the configuration to the process bus

• Upload firmware:Loads the firmware to the process bus

• Print the set configuration (raw):Prints the configuration data separated with delimiters

• Print the set configuration (formatted):Prints the configuration data formatted in tables and hyperlinked

• Print memory hex dump:Prints a memory dump beginning with the specified address

• Patch configuration (none persistent):Patches the Sync and the MAC filter

• Status and statistics for Port A to D

• Show event log:Prints the event log

• Delete event log entries:Erases the event log

• Login/Logout for restricted functionality

• Rebooting the device:Triggers a device reboot

Connecting to the PB201 Homepage

² To connect to the PB201 homepage, enter 10.0.0.110.

iiNOTE

The homepage is optimized for Firefox and Internet Explorer 10.

Uploading Configuration

² Select Upload configuration to upload a PCF file.

3.4

Parameterization of the Process Bus3.4 Working with the PB201 Homepage




[sc_PB201Homepage_Uploadconfiguration, 1, --_--]

Figure 3-21 Upload Configuration

² Click Browse..., select the desired PCF file, and click Upload.

² Reboot the device via Rebooting the device.

[sc_PB201Homepage_RebootingDevice, 1, --_--]

Figure 3-22 Rebooting the Device



After the reboot, the Home window appears:

[sc_PB201Homepage_Welcome, 1, --_--]

Figure 3-23 Home Screen

Indicating PB Status

² Select PB Status to check the data.





[sc_PB201Homepage_PBStatus, 1, --_--]

Figure 3-24 PB Status

iiNOTE

If the communication does not work correctly, check the following:• Group configuration:

– Does it show the expected SV_Ids?

– Is the CONF_REV (configuration revision number) the same in the complete system configura-tion?

• 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, --_--]

Figure 3-25 Upload Firmware

Printing the Set Configuration

² Select Print the set configuration (formatted).

[sc_PB201Homepage_Print, 1, --_--]

Figure 3-26 Print the Set Configuration (Formatted)

The data are displayed here in the same way as in ProConf in the Documentation tab.





Restrictions

4.1 Restrictions 64

4




Restrictions

SIPROTEC 5 Process-Bus Module PB201 V6.20

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 (7SC805 with PPS input)and conventional CTs /VTs only.

• Maximum allowed number of merging units per SIPROTEC 5 device: 3

• Maximum allowed number of PB201 per SIPROTEC 5 device: 1

• Maximum allowed number of I/O extension modules additionally to 1 PB201 per SIPROTEC 5 device: 1

• Limited support of the HSR and PRP protocols at the ports A and BNo redundancy on port C

• Limited support of 1-phase measurements

• No capacitor-bank protection, phasor-measurement function, synchrocheck, and transient ground-faultfunction

• No combination of SM values with values from conventional CTs/VTs

• Maximum allowed number of SMV channels: 24

• 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 and4 VTs

• To use the IEC 61850 System Configurator for IEC 61850-9-2 Engineering, IEC 61850-8-1 must beused in the SIPROTEC 5 device.

• At the moment, the IEC 61850 System Configurator only supports SIPROTEC 4-like premapping.

• The IP address of the service interface of PB201 is fixed. Therefore, max. 1 PB201 can be connected toa PC at the same time.

• Limited support of protection functions.

• Limited integration of process-bus engineering in DIGSI 5.

• Diagnostics, FW update, and configuration update are possible via the PB201 homepage.

Siemens MU 7SC805

The following components must be used for synchronization:• 7XV5664-1AA00: GPS clock incl. accessories

• 7XV5450-0BA00: Mini Star-Coupler

• 7XV5654-0BA00: Sync transceiver

• 7XV5105-0AAxx: Y bus cable xxm

The following restrictions are known:• Very sensitive time synchronization

• 2 ASDUs (Application Service Data Units) are not supported

• Limited environmental capabilities of the Mini Star-Coupler

4.1

Restrictions4.1 Restrictions


iiNOTE

Do not use other components.

For more information on restrictions, contact the Customer Support Center.

Restrictions4.1 Restrictions




Siemens Industrial Spares -...

Documents

Transcript of Siemens Industrial Spares -...