SYS 600 9 3 IEC 61850 system design

SYS 600 9 3 IEC 61850 System Design MicroSCADA Pro SYS 600 9 3 IEC 61850 System Design Contents 1 Copyrights 5 2 Introduction 6 2 1 This manual 6 2 2 Use of symbols 6 2 3 Intended audience 6 2 4 Product documentation 6 2 5 Document conventions 7 2 6 Document revisions 8 3 Safety information 9 3 1 Backup copies 9 3 2 Fault tracing 9 4 Requirements 11 4 1 Hardware requirements 11 4 2 Software requirements 11 5 Configuration 12 5 1 Components of the IEC 61850 based system 12 5 1 1 SYS 600 base syst.

1 Copyrights 5

2 Introduction 6

2.1 This manual 6

2.2 Use of symbols 6

2.3 Intended audience 6

2.4 Product documentation 6

2.5 Document conventions 7

2.6 Document revisions 8

3 Safety information 9

3.1 Backup copies 9

3.2 Fault tracing 9

4 Requirements 11

4.1 Hardware requirements 11

4.2 Software requirements 11

5 Configuration 12

5.1 Components of the IEC 61850-based system 12

5.1.1 SYS 600 base system 12

5.1.2 OPC Data Access Client 13

5.1.3 IEC 61850 OPC Server 13

5.1.4 Related engineering tools 14

5.1.5 IEC 61850 System Supervision Server 14

5.1.6 IED connectivity 15

5.1.6.1 Connectivity Packages 16

5.2 Configuration environment 17

5.3 Configuring the SYS 600 base system 18

5.4 IEC 61850 Redundancy 21

5.5 Building the physical IEC 61850 network 22

5.6 Configuring SPA-ZC 40_ 22

5.6.1 Creating a new project 23

5.6.2 Adding a device object 23

5.6.3 Importing the IEC 61850 data object model of an IED 23

5.6.4 Downloading the configuration and exporting the CID file 25

5.6.5 Restarting 26

5.6.6 Configuring report control blocks 26

5.7 Configuring IEC 61850 OPC Server 28

5.7.1 Creating a new project 29

5.7.2 Defining IEC 61850 OPC Server 29

5.7.3 Importing IED configuration 29

5.7.4 Time Synchronization 32

5.7.5 Timeout handling 35

5.8 Creating process objects 35

5.8.1 Importing SCL configuration 36

5.8.2 Importing a language translation file 39

5.8.3 Addressing process objects 39

5.9 Configuring OPC Data Access Client 41

5.9.1 Starting OPC DA Client Configuration Tool 41

5.9.2 Connecting to IEC 61850 OPC Server 42

5.9.3 Auto-configuring OPC items for process objects 43

5.9.4 Defining configuration for the IEC 61850 system 45

5.9.5 Defining the event buffer 46

5.10 Configuring an OPC Data Access Client instance 47

5.10.1 IEC 61850 Hot Stand-by system topology 47

5.10.2 Starting OPC Data Access Client instance 47

5.10.3 Stopping an OPC Data Access Client instance 48

5.11 Single-line diagram engineering 48

5.11.1 Adding objects into the display 48

5.11.2 Adding Station Local/Remote Switch 50

5.11.3 Editing data variables in the display 51

5.12 Configuring IEC 61850 System Supervision Server 53

5.12.1 Installing IEC 61850 System Supervision Server 53

5.12.2 Starting IEC 61850 System Supervision Server 53

5.12.3 Stopping IEC 61850 System Supervision Server 53

5.12.4 Configuring IEC 61850 System Supervision Server 54

5.13 Configuring IEC 61850 Redundancy diagnostics 56

5.13.1 Local machine DuoDriver status diagnostics 56

5.13.2 IED DuoDriver status diagnostics 57

6 Testing configuration 59

6.1 Testing SPA-ZC 40_ and IEC 61850 OPC Server configurations 59

6.2 Testing OPC Data Access Client start-up 60

6.3 Testing IED control commands using process display 61

6.4 Testing IEC 61850 System Supervision Server 61

7 Distributed system topologies 62

8 IEC 61850 System recommendations 64

9 Troubleshooting 65

10 Conformance statements 66

11 Terminology 71

12 Abbreviations 72

Copyrights 1.

The information in this document is subject to change without notice and should not beconstrued as a commitment by ABB Oy ABB Oy assumes no responsibility for anyerrors that may appear in this document

In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB Oy

be liable for incidental or consequential damages arising from use of any software orhardware described in this document

This document and parts thereof must not be reproduced or copied without written mission from ABB Oy, and the contents thereof must not be imparted to a third partynor used for any unauthorized purpose

per-The software or hardware described in this document is furnished under a license andmay be used, copied, or disclosed only in accordance with the terms of such license

© Copyright 2010 ABB All rights reserved

Trademarks

ABB is a registered trademark of ABB Group All other brand or product names tioned in this document may be trademarks or registered trademarks of their respectiveholders

men-Guarantee

Please inquire about the terms of guarantee from your nearest ABB representative

Introduction 2.

This manual 2.1.

This manual provides thorough information on the MicroSCADA Pro software andhardware installation: base systems, LAN connections, process communication systems,workplaces and peripherals

This manual provides thorough information on the various configuration settings thatyou have to make in order to take your SYS 600 system into use, focusing on describinghow to configure SYS 600 for an IEC 61850 system The manual also describes how touse the configuration tools

Use of symbols 2.2.

This publication includes the following icons that point out safety-related conditions orother important information:

The caution icon indicates important information or warningrelated to the concept discussed in the text It might indicatethe presence of a hazard which could result in corruption ofsoftware or damage to equipment or property

The information icon alerts the reader to relevant facts andconditions

Intended audience 2.3.

This manual is intended for engineers to support configuration and engineering of systemsand/or applications

Product documentation 2.4.

Document ID Name of the document

1MRS756669 SYS 600 9.3 System Administration

1MRS756646 SYS 600 9.3 System Configuration

1MRS756637 SYS 600 9.3 Application Design

1MRS756647 SYS 600 9.3 External OPC Data Access Client

Document ID Name of the document

1MRS756636 SYS 600 9.3 Process Display Design

1MRS756643 SYS 600 9.3 Picture Editing

1MRS756663 SYS 600 9.3 Status Codes

1MRS756632 SYS 600 9.3 IEC 61850 Master Protocol (OPC)

1MRS756638 SYS 600 9.3 Connecting LONWORKS Devices

1MRS756662 SYS 600 9.3 System Objects

1MRS755359 LIB 500 *4.2 Operation Manual

1MRS755360 LIB 500 *4.2 Configuration Manual

1MRS750104-MUM RER 111 Technical Reference Manual

1MRS755347 SPA-ZC 400, SPA to IEC 61850 Gateway, Installation and Commis-

sioning Manual

1MRS755380 SPA-ZC 402, SPA to IEC 61850 Gateway, Installation and Commis-

sioning Manual

Other related documents:

• Citrix documentation

• LONWORKS PCLTA-20 PCI LonTalk Adapter, User's Guide

• Microsoft Windows documentation

• PC/TCP documentation

• Product documentation of the used multiport serial card

• Product documentation of the used network adapter card

• Product documentation of the used PCLTA-10 card

• RTU documentation

Document conventions 2.5.

The following conventions are used for the presentation of material:

• The words in names of screen elements (for example, the title in the title bar of adialog, the label for a field of a dialog box) are initially capitalized

• Capital letters are used for file names

• Capital letters are used for the name of a keyboard key if it is labeled on the keyboard.For example, press the CTRL key Although the Enter and Shift keys are not labeledthey are written in capital letters, e.g press ENTER

• Lowercase letters are used for the name of a keyboard key that is not labeled on thekeyboard For example, the space bar, comma key and so on

• Press CTRL+C indicates that you must hold down the CTRL key while pressingthe C key (to copy a selected object in this case)

• Press ALT E C indicates that you press and release each key in sequence (to copy

a selected object in this case)

• The names of push and toggle buttons are boldfaced For example, click OK.

• The names of menus and menu items are boldfaced For example, the File menu.

• The following convention is used for menu operations: Menu Name > Menu Item

> Cascaded Menu Item For example: select File > Open > New Project.

• The Start menu name always refers to the Start menu on the Windows Task Bar.

• System prompts/messages and user responses/input are shown in the Courier font.For example, if you enter a value out of range, the following message is displayed:

Entered value is not valid.

You may be told to enter the string MIF349 in a field The string is shown as follows

in the procedure: MIF349

• Variables are shown using lowercase letters: sequence name

Document revisions 2.6.

History Date

Software revision number Version

New document 31.3.2010

9.3 A

Safety information 3.

This chapter provides information on prevention of hazards

Backup copies 3.1.

We suggest that you take backup copies before making any changes, especially onesthat might have side effects Software and data need to be copied to another location,usually to a CD or a backup tape A writable DVD and DAT tape are commonly used.Backup copying makes it easier to restore the application software in case of disk crash

or other severe failure when stored data is lost It is therefore recommended that backupcopies are taken regularly

There should be at least two system backup copies and two application copies A newbackup is copied over the oldest backup This way the latest version is always available,even if the backup procedure fails

Detailed information on how to take backup copies is delivered to the customer with theapplication

System backup

Usually, a system backup is taken after the application has been configured It should

be taken again when changes are made to the SYS 600 system This is the case, forexample, when the driver configuration or the network setup is changed

Application backup

An application backup is taken at the same time with the system backup after theapplication has been configured It should be taken again when changes are made to theapplication This is the case, for example, when pictures or databases are edited or newpictures are added

Fault tracing 3.2.

A fatal error is an error that causes a breakdown or a locked situation in the SYS 600program execution

In case of a fatal error:

1 Write down the possible SYS 600 error messages

2 Shut down the SYS 600 main program If this cannot be done in SYS 600 ControlPanel, try to end the task in Windows Task Manager.

Shutting down the base system computers by switching offthe power might damage the files

3 In Windows, the data kept in the main memory at the moment of a fatal error isplaced in the drwtsn32.log file in a system folder, for example WINNT Analyze andcopy the data in this file

4 Restart the system

5 Report the program breakdown together with possible the SYS 600 error messagesand the information from the drwtsn32.log file to the SYS 600 supplier

Error messages in SCIL are called status codes A list of status codes and short tions can be found in SYS 600 Status Codes

explana-Requirements 4.

The installation and configuration of the devices that use the IEC 61850-8-1 protocolconsist of:

• Hardware installation

• Software installation

Hardware requirements 4.1.

The hardware components listed below are usually required in IEC 61850 systems Inaddition to the hardware itself, this equipment may require the configuration of theappropriate driver in the appropriate operating system

• Time synchronization device with SNTP Server (for example Meinberg TIME/GPS)

LAN-• RuggedCom RS1600/8000 or RSG 2100, for example For more information, seehttp://www.ruggedcom.com

• OnTime FST208 Industrial Switch

• Allied Telesyn AT-8016F/MT

• Intel PRO/1000 MT Dual Port For more information, see http://www.intel.com

• Printer Server

• Media converterPrinter Server usually provides diagnostics information in Ethernet via the SNMP pro-tocol The proposed way to include this information into SYS 600 is to convert it intoOPC item updates using a third-party SNMP to the OPC Server component The OPCitem updates are then mapped to the SYS 600 process database via OPC DA Client

Software requirements 4.2.

The following software is required:

• MicroSCADA Pro SYS 600 9.3The following software is optional:

• IED configuration tools (for example Communication Engineering Tool for

SPA-ZC 40x version 2.0 or later)

• PCM600

• Connectivity Packages for IEDs (for example REF 541/543/545 ConnectivityPackage version 2.0 or later)

Configuration 5.

Components of the IEC 61850-based system 5.1.

The related components of the IEC 61850-based system (see Figure 5.1-1) are described

in the following sections:

• 5.1.1, SYS 600 base system

• 5.1.2, OPC Data Access Client

• 5.1.3, IEC 61850 OPC Server

• 5.1.4, Related engineering tools

• 5.1.5, IEC 61850 System Supervision Server

• 5.1.6, IED connectivity

A060436

Figure 5.1-1 Related components of the IEC 61850-based system

SYS 600 base system 5.1.1.

Process displays and lists, providing the operator with information on the SYS 600 basesystem, are found in process and report databases within the system In the SYS 600system, each signal update from an IED is represented with a unique addressing based

on station (Unit Number) and object addressing (Block and Bit number)

OPC DA Client interacts with the base system through a node connected to the TCP/IPlink Thus the underlying IEDs using the IEC 61850-8-1 protocol are represented ascommunication stations in the system

Consequently, the related base system objects, that is link, node and station(s), must beintroduced through system configuration:

• LAN link (LINn:B)

• Node (NODn:B)

• Station(s) (STAn:B)These definitions are usually included in the system configuration and found in the file

IEC 61850 OPC Server

• IEC 61850 OPC Server CLSID and its location (Local or Remote Server) are assigned

in Server Properties

SYS 600 base system objects

• Configuration related to OPC DA Client Node and Primary/Secondary SYS 600base system objects are assigned in CPI Node Properties

of 1000 ms In this case, signal changes shorter than 1000 ms are not sent to OPC

Related engineering tools 5.1.4.

When creating process objects into the application, IEC 61850 engineering involvesusing tools like SCL Importer and OPC PO List During single-line diagram engineering,Display Builder (Monitor Pro) or Picture Editor (Classic Monitor) can be used Further,additional IED configuration tools such as CAP 505 may be required

IEC 61850 System Supervision Server 5.1.5.

IEC 61850 SSS is a stand-alone executable OPC Client IEC 61850 server(opcc_iec61850.exe) with a built-in OPC server for DCOM start-up and diagnostics.IEC 61850 SSS enables mapping of SYS 600 OPC Server items to IEC 61850 processobjects and is configurable with SCL To be able to generate events through IEC 61850,the SSS must receive the data changes from the OPC server with OPC item updates, asIEC 61850 does no explicit reading IEC 61850 SSS requires an IEC 61850 license (SYS

or COM) OPC Server-related components are presented in Figure 5.1.5-1

A060813

Figure 5.1.5-1 OPC Server-related components

IEC 61850 SSS features

IEC 61850 SSS maps the following OPC items to IEC 61850 7-3 CDC attributes:

• Event update (UPDATE)

• Creates an OPC group for mapped items with a group update rate of 0 ms

• Sends events received as OPC item updates to IEC 61850 clients with reportingservice

• Value overrides (GOOD and BAD) The value GOOD overrides all updatedvalues, whereas BAD is used in case of errors (disconnect)

• Expects an update of a specified OPC item from OPC Server within timeoutmilliseconds.

• Creates an OPC group for mapped items with a group update rate of timeoutmilliseconds

• Sends events received as OPC item updates to IEC 61850 clients with reportingservice

• If the OPC item update interval exceeds the timeout, the quality (the value ofthe q-attribute) of the CDC is set to BAD

• Value overrides (GOOD and BAD) The value GOOD overrides all updatedvalues, whereas BAD is used in case of errors (disconnect and timeout)

• On OPC Server disconnect, all the mapped CDC qualities are set to BAD.The following values remain constant:

• Configured values for CDC attributes

IEC 61850 SSS start-up

When IEC 61850 SSS starts up, it will automatically perform the following tasks:

1 Reads the configuration (SCL, Systemc.xml)

2 Builds an IEC 61850 namespace according to SCL

3 Connects to SYS 600 OPC Server (configured in SCL Communication ProgID)

4 Connects to OPC Items on SYS 600 OPC Server (configured in SCL CDC sAddrs)

5 Starts the IEC 61850 server for IEC 61850 clients

IED connectivity 5.1.6.

The concept of Connectivity Packages has been introduced together with MicroSCADAPro SYS 600 and will gradually replace the role of the LIB packages in IED engineering.Unlike the LIB packages, the connectivity packages do not include IED tools Instead,PCM600 can be integrated and used together with SYS 600 However, the IED toolsincluded in the LIB packages can also be used together with SYS 600 and Monitor Proprocess displays For further information on integrating IED tools, see SYS 600Application Design and SYS 600 Process Display Design

The same requirements apply to the connectivity packages in SYS 600 as to the LIBpackages Consequently, IED connectivity in SYS 600 appears in the form of engineeringdefinitions related to process database and graphical user interface

In the graphical user interface, the common user interface components of SA-LIB (forexample control dialogs) are used to interact with the process database During single-line diagram engineering, the application-related set of process display symbols has beenselected to be used in process displays

The process database definitions contain instantiated SA-LIB standard functions andhave been created by the following means:

• Connectivity Packages

• Load files provided by Integrated Engineering Toolbox

• Object Navigator approach

• List-Based Engineering Tool

• SCL Importer

Connectivity Packages 5.1.6.1.

The concept of Connectivity Packages for IEDs provides harmonized engineering andminimizes the dependencies between different releases of IEDs, system products andtools IED configuration management of parameters, measurements and functions can

be realized by importing IED descriptions This information is included together withthe IED when integrating the IED into system products and tools; see Figure 5.1.6.1-1

The process database model of control and supervision consists of position indications,commands and measurements, whereas the process database model of protection functionsconsists of protection events Connectivity Packages are used to construct this information

in a reliable way into the process database and to achieve effective engineering withoutadditional manual work

Each Connectivity Package includes all the information and functionality required forefficient integration of the IED into system level products and tools The ConnectivityPackage description of an IED is according to IEC 61850 and contains:

• data signal description

Consequently, in SYS 600, the process database of the IEC 61850 system is createdusing SA-LIB standard functions with default event and alarm handling This is the casewhen SCL Importer is used for importing the SCL information either from CID or SCDfiles into the application The created process database is connected to the SA-LIB processsymbols during display engineering and interacts with the Control dialogs of SYS 600

at run-time For more information on SCL Importer, see 5.8, Creating process objectsand SYS 600 Application Design

To understand the process object model of SA-LIB through the IEC 61850 modeling,see 10, Conformance statements for the logical nodes supported by SA-LIB

Configuration environment 5.2.

In IEC 61850-based systems, the following components need to be configured:

• IED (SPA-ZC 40_ if used)

• IEC 61850OPC Server

• OPC Data Access Client

• SYS 600 process database and HMIFigure 5.1-1 illustrates the software components, including their interrelationships andunderlying communication architecture The SYS 600 base system, OPC DA Client andIEC 61850 OPC Server are usually all located on the same computer

Configuring the SYS 600 base system 5.3.

The SYS 600 base system is configured with the System Configuration Tool This meansthat the base system definitions related to the LAN link, the OPC DA Client node andthe communication station(s) are configured with the System Configuration Tool It isalso possible to include the configuration of the SYS 600 base system in the sys_bas-con.com file manually, but configuration using the System Configuration Tool isrecommended

To configure the SYS 600 base system with the System Configuration Tool:

1 Open System Configuration Tool from Tool Manager

2 Select the MicroSCADA Configuration object Insert New LAN Link Object

Number 1, and click OK to add LIN1.

3 Select the LIN1 object Insert New IEC 61850 Node Object Number 8, and click

OK to add NOD8.

4 Select the NOD8 object Insert New SPA Station Object Number 60, and click OK

to add STA60 The configuration in tool is shown in Figure 5.3-1

a070121.png

Figure 5.3-1 SYS 600 base system configuration in System Configuration Tool

5 Select Configuration > Save to save the configuration.

6 The changes take effect the next time SYS 600 is started Possible configurationerrors appear in the SYS 600 Notification Window

Traditionally, the configuration related to the SYS 600 base system is defined in thesys_bascon.com file In IEC 61850-based systems, this means that the base systemdefinitions related to the LAN link, the External OPC DA Client node and the commu-nication station(s) are configured for both SYS 600 redundancy systems The followingsteps guide you through the base system configuration using the included configurationtools.

To configure the system using System Configuration Wizard:

1 Open SYS 600 Control Panel

2 In the SYS 600 Control Panel dialog, click Admin and then Wizard.

3 The System Configuration dialog appears Follow the wizard and make the necessaryconfigurations

For a single system use e.g the following configuration:

• Select Base System Type Single System and Monitor Pro and OPC Data

Access Server enabled for OPC Data Access Server.

• Use Node Name SYS_1, Node Number 9 and Station Address 209 for Base

System Information

• Use Application Name MAIN for Application Information.

4 After completing the configurations, select Start the application and click Finish.

The Base System Node Number and Station Address are usedwhen configuring CPI Node Properties for the OPC DataAccess Client

Creating a LAN link

The SYS 600 base system is configured with the System Configuration Tool This meansthat the base system definitions related to the LAN link, the OPC DA Client node andthe communication station(s) are configured with the System Configuration Tool It isalso possible to include the configuration of the SYS 600 base system in the sys_bas-con.com file manually, but configuration using the System Configuration Tool isrecommended

To create the LAN link, the External OPC DA Client node and the communication tion(s) using System Configuration Tool (LAN link LIN1, External OPC DA Client nodeNOD8 and station STA60 are created here as an example):

sta-1 Start SYS 600 Monitor

2 Start System Configuration Tool (System Conf) from System Configuration tab

in Tool Manager

3 Open the active configuration for editing

In the System Configuration Tool, select Configuration > Open Active.

4 Add LAN link 1 LIN1.

• Right-click MicroSCADA Configuration and select New.

• Select Object Type LAN Link and click Insert.

• Insert New Link Object Number 1 for the object and click OK to add LIN1.

5 Create an External OPC DA Client node 8 NOD8

• Right-click Link 1 and select New.

• Select Object Type IEC 61850 Node and click Insert.

• Insert New Node Object Number 8 for the object and click OK to create NOD8.

6 Create a communication station 60 STA60

A single station should be used to represent a single IEC 61850 IED To add morestation objects repeat this step with unique station numbers

• Right-click Node 8 and select New.

• Select Object Type IEC 61850 Station and click Insert.

• Insert New SPA Station Number 60 for the object and click OK to create STA60.

7 Select Configuration > Save Active to save the modified configuration.

8 Configuration of the LAN link, External OPC DA Client node and a single nication station is now finished The changes take effect the next time SYS 600 isstarted Possible configuration errors appear in the SYS 600 Notification Window

commu-The contents of the sys_bascon.com file are identical for bothHSB systems, with the exception of the unique node and sta-tion numbers

IEC 61850 Redundancy 5.4.

Redundancy in the nodes (Station and IED) is achieved by attaching two different,redundant networks by two ports to each node Each node selects independently thenetwork to use The nodes are the only non-redundant parts IEC 62439-3 specifies thePRP (Parallel Redundancy Protocol), a "redundancy in the nodes" solution, in whichnodes use both networks simultaneously PRP is based on full duplication and paralleloperation of two redundant networks PRP nodes send signals to and receive signalsfrom both networks at the same time, providing bumpless recovery This offers zerorecovery time, making PRP suited for all real time applications

Redundancy in the network (LAN) is achieved using RSTP (Rapid Spanning Tree tocol) The RSTP standard provides at best a 2 second recovery time

Pro-DuoDriver (v2.2 or later) with PRP and compatible network interface cards (NIC) areused for IEC 61850 communication redundancy Using DuoDriver and PRP with SYS

600 requires that the connected IEDs also support DuoDriver for communicationredundancy

Installing DuoDriver

To install and configure DuoDriver:

1 Install and configure the NICs used for redundant IEC 61850 communication beforeinstalling the DuoDriver The NICs to-be-paired must be named appropriately

2 Set the static IP address

• For Windows XP SP2 (and earlier), set a static IP address for NIC A manually,and disable TCP/IP protocol for NIC B

• For Windows Vista, Server 2008 and XP SP3, configure a static IP address forboth NICs (IP of NIC B not used) Disable IPv6 The IP address of NIC A isused for both paired NICs

The configuration of DuoDriver requires that all ant NICs are plugged into an active switch/router duringthe installation

redund-3 Install DuoDriver by executing the DuoDriver install package included in SYS 600installation (e.g C:\sc\Setup\DuoDriver\setup.exe)

DuoDriver is configured during the installation To change the configuration, thedriver must be reinstalled The DuoDriver setup names the paired instance ofDuoDriver, pairs the NICs, and clones the MAC address of the paired NICs Theconfigured instance name and NIC name are used in the IEC 61850 OPC Servernamespace to identify the DuoDriver diagnostics

4 After installation disable DuoDriver for other Ethernet interfaces

Building the physical IEC 61850 network 5.5.

The devices in the IEC 61850 network should first become connected in systemaccording to the wiring diagrams and layout pictures Setting up the devices may requirethat their addresses and the protocols in question are configured according to the systemrequirements

Configuring SPA-ZC 40_

5.6.

Before configuring SPA-ZC 40_, ensure that the correct connectivity packages havebeen installed and taken into use in Connectivity Package Manager

Creating a new project 5.6.1.

To create a new project:

1 Start CET for SPA-ZC 40x

2 Select File > Open/Manage Project.

3 Click New Project and fill in the required project information.

4 Click Create.

5 Select the project and click Open.

Adding a device object 5.6.2.

A project can contain several IEC 61850 device objects All substation feeder ations and exported communication, for example, must be done separately for eachdevice To add an IEC 61850 device object to the project, right-click the project and

configur-select New > IEC 61850 > SPA-ZC 40_; see Figure 5.6.2-1.

A040023B

Figure 5.6.2-1 Adding an IEC 61850 device object

Ensure that the new IED name is unique within the planned network by renaming theIED, for example REF545_F1

Importing the IEC 61850 data object model of an IED 5.6.3.

To import the IEC 61850 data object model of an IED:

1 Right-click to select a Logical Device object (for example REF 541/3/5)

2 Import the project created with CAP 505 (Relay Product Engineering Tool).The file, which is a compressed archive file with the file extension AR, is imported fromCAP 505 Application Library to the specified directory

CET for SPA-ZC 40x converts the project files to an IEC 61850 data object model usingconnectivity packages However, the connectivity packages do not necessarily supportall the functions of an IED Functions not mapped to the IEC 61850 structure are reportedafter import.

CET for SPA-ZC 40x imports default data sets and RCBs to the logical device LD0; seeFigure 5.6.3-1 A data set includes data attributes selected from an IED's IEC 61850 datamodel The data sets are used in the IEC 61850 event reporting model If the same dataattributes that have been selected to be included in a data set are used in an RCB, thedata set generates a spontaneous event which is sent to the IEC 61850 client If the dataset is not used in an RCB, the IEC 61850 client reads the data separately

After adding a new IED, give it a unique name in the network

Spaces are not allowed in the IED's name Renaming can bedone in Project Explorer; see Figure 5.6.3-1

A040026B

Figure 5.6.3-1 Project Explorer in the Communication Engineering Tool window

Downloading the configuration and exporting the CID file 5.6.4.

After you have built the IEC 61850 data object model and configured the communicationaddressing, you can download the configuration to SPA-ZC 40_, see Figure 5.6.4-1

1 Right-click the IEC 61850 device object and select CID Export.

2 If you download configuration to SPA-ZC 40_ for the first time, replace the default

IP address 192.168.2.10 with a new address according to the planned networkstructure

When the new configuration is being downloaded to SPA-ZC 40_, CET checks if thebasic IP addresses are changed If a change is detected, CET asks whether you want totake the new addresses into use If you do not accept the changes, SPA-ZC 40_ uses theold IP addresses from the previous configuration

A040029B

Figure 5.6.4-1 Downloading device configuration

If the connection to the system, to which SPA-ZC 40_ is connected, is enabled, theExport function tries to determine the SPA-ZC 40_ version and exports the export fileaccordingly If a connection to the system cannot be established, prompt the correctversion to be exported; see Figure 5.6.4-2

Figure 5.6.4-2 Selecting the correct SPA-ZC 40_ version to be exported

With CID Export, you can export a configuration in CID format to the hard drive Further,

it is possible to export a data set in SCL files at different levels For example, if youselect to export a data set at the FCD level, an information report from SPA-ZC 40_always contains value, quality and time in one structure You can also export the CID

or ICD file to your workstation's file system and use it in system level tools, for example

to configure your IEC 61850 client

Restarting 5.6.5.

When you need to restart SPA-ZC 40_ at runtime:

1 Select IED and then Tools > Reset Tool to open the restart pane.

A060396

Figure 5.6.5-1 Restarting

2 Click Reset.

The results are reported in the UI text box

Do not use the restart function while downloading tion to SPA-ZC 40_ When the download is complete, SPA-

configura-ZC 40_ is automatically restarted

Configuring report control blocks 5.6.6.

RCBs control the spontaneous event reporting The client can modify the event reporting

by setting RCB attributes Both buffered and unbuffered RCBs are supported The RCB

• COM600

• SYS 600 IEC 61850 client

RCBs are located under the logical device LD0 and logical node LLN0; see

Figure 5.6.6-1 For information on RCB dedication, see SYS 600 IEC 61850 Master Protocol (OPC)

A060032

Figure 5.6.6-1 Reporting model

RCBs have the following properties:

• Buffered reportingIEC 61850 buffers events also during a communication break

• Buffer TimeThe default value is 100 ms Consequently, the RCB waits 100 ms for other eventsafter the first change before sending the report

• Integrity PeriodThe default value is 0 ms If the integrity period is > 0 ms, SPA-ZC 40_ sends areport with all data listed in the linked data set within this period This feature is notenabled by default, because it causes excessive load to the server and the network

• Report IDSPA-ZC 40_ uses the Report ID as the MMS address of the RCB Report ID isempty by default At the default value, a default RCB MMS path name is used

• Option FieldsDefines what information is sent in the report

SPA-ZC 40_ adds information on buffer overflow, report entry ID and sequencenumber, and allows segmentation by default Other fields are RCB configurationversion, data reference in the MMS address format, name of the used data set andreport sending time

• MaxDefines how many clients use the RCB, that is the number of required RCB instances

If two clients for buffered reporting are defined, Max has to be set to 2 SPA-ZC40_ creates two instances of the RCB name, for example rcbStatNrml01 and rcbStat-Nrml02 For unbuffered reporting, Max has to be the same or higher as the number

of defined clients in accordance with the IEC 61850 standard

• Trigger OptionsData Change, Data Update and Quality Change triggers are used by default Con-sequently, changes in value and quality generate information reports A periodtrigger is not used by default

To edit the properties, right-click the dataset and select Properties.

Figure 5.6.6-2 Report control block

Buffered reporting requires that clients are defined Report Client definitions link a certainRCB to a certain client The client can import the CID file to check which RCB instance

it has to use If Max is set to 2, the configuration must have two clients with bufferedreporting The first client on the list uses the first RCB instance (rcb name 01) and thesecond client the second instance (rcb name 02 )

Unbuffered reporting does not require that clients are defined, but it is recommendedfor clarity Client IED Name has to match with the client name in SCL

Every modification in an RCB increases the RCB configuration revision by one Eachrevision generates a CID file, enabling the IEC 61850 client to compare the receivedrevision to the file configuration revision

Configuring IEC 61850 OPC Server 5.7.

IEC 61850 OPC Server is configured using CET for IEC 61850 OPC Server in SYS

600 With this tool, the hierarchically structured models of a substation or a system arebuilt and loaded into configuration files of IEC 61850 OPC Server

To start CET for IEC 61850 OPC Server:

2 Open 61850 OPC Server.

3 Double-click Communication Engineering Tool.

Creating a new project 5.7.1.

To create a new project:

1 Start CET for IEC 61850 OPC Server

2 Select File > Open/Manage Project.

3 Click New Project and fill in the required project information.

4 Click Create.

5 Select the project and click Open.

Defining IEC 61850 OPC Server 5.7.2.

To define IEC 61850 OPC Server:

1 Right-click the project and select New > Communication > Computer Node to

add a computer node to the project

2 Right-click the Computer Node and select View > Object Properties to open Object

Properties

3 Right-click the Computer Node and select New > IEC61850 > IEC61850 OPC

Server to add an IEC 61850 OPC server.

4 Right-click the IEC61850 OPC Server and select New > IEC61850 > IEC61850

Subnetwork to add an IEC 61850 subnetwork to the IEC 61850 OPC server.

5 Right-click IEC61850 Subnetwork and select New > IEC61850 > IEC61850 IED

to add an IEC 61850 IED to the IEC 61850 subnetwork

The IEC 61850 OPC Server and IEC 61850 Subnetwork can be renamed if required

Importing IED configuration 5.7.3.

To import IED configuration:

1 Right-click IEC61850 IED and select SCL Import.

2 In the SCL Import pane, click Select File.

3 Select the IED SCL configuration file (for SPA-ZC 40_ the CID file previously

created with CET for SPA-ZC 40x) and click Open.

4 Click Import and close the pane; see Figure 5.7.3-1.

Figure 5.7.3-1 SCL Import pane

The following communication options are available:

objects being imported If a data object does not belong to any data set, it is notimported Some IEDs can provide huge amounts of data that is not reported, that is,not updated in COM600 HMI Performance can be enhanced by checking this option

on objects affected by the import operation Select this option only if you know thatthe importable file contains better descriptions than your current configuration

structure It can be used if you only must update the communication configuration

to select a template that provides the substation configuration It is useful, if thereare several identical configurations and you have created a good template for thesubstation information

If this option is selected, both the object tree and protocol configuration are done

If this is not selected, only the object tree structure is created

selected, none of the data objects without protocol configuration information arecreated to the object tree

It is important to dedicate specific instances of the IED ReportControl Blocks for specific IEC 61850 clients Multiple IEC

61850 clients cannot enable reporting from a single RCBinstance and will cause communication failures.

To allow multiple IEC 61850 clients to receive the same data values from the IED,multiple instances of the report control classes must be made available Specify the RCBinstances using Report Enabled and Report Client and dedicate them to clients usingReport Client

To enable IEC 61850 OPC Server to use the server-specific RCB instances and thusreceive spontaneous events, the Report Control Identity object property of the OPCServer must match one of the Report Client fields in the device's RCB configurations.All configured RCBs without a Report Enabled field are used with as is RCB naming.The RCBs without instances specified for the IEC 61850 OPC Server are discarded Formore information, see IEC 61850 Master Protocol (OPC) manual

a070100.png

Figure 5.7.3-2 Report Control Identity and RCB dedication

Updating IEC 61850 OPC Server

To update IEC 61850 OPC Server (see Figure 5.7.3-3):

1 Right-click the Computer Node and select Management.

2 Click Update Configuration and then Reload Configuration.

3 Close the Management pane

Figure 5.7.3-3 Management pane

Time Synchronization 5.7.4.

IEC 61850 OPC Server can act as an SNTP client and server for time synchronization.For more information, see IEC 61850 Master Protocol (OPC) manual

SNTP Client

When the IEC 61850 OPC Server is configured as a time synchronization client, it updatesthe operating system time of the workstation SNTP Client supports maximum 4 altern-ative SNTP servers

When using the SNTP Client, also disable Windows Date and Time Properties automatictime synchronization

of the workstation.

Figure 5.7.4-2 Windows Time service disabled

To set the daylight saving time, enable Windows Date and Time Properties to ically adjust the time for daylight saving changes

automat-a070104.png

Figure 5.7.4-3 Windows automatic daylight saving time adjust enabled

Timeout handling 5.7.5.

When parameter setting or disturbance upload operations are performed by using relaytools such as CAP, SMS or LIB, their default timeout of 5 seconds is used In CET forIEC 61850 OPC Server, the default SPA TCP timeout is 3 seconds

To enable fluent interaction in case of possible communication failures during relay specific operations, it is recommended not to change the default SPA TCP timeout Theconfiguration parameters should be defined according to the following principle: SPATCP Timeout (3 seconds) < Read/Write timeout of OPC DA Client (4 seconds) < defaulttimeout of relay tools (5 seconds)

tool-Creating process objects 5.8.

In the IEC 61850-based system, SCL Importer usually creates the application objectsinto the SYS 600 process database from the files following the SCL model The prerequis-ite is that the SCL files contain the Substation section, whose content is further applied

to the Object Identification attribute values, which in turn are assigned to the processobjects

Before importing the SCL file, ensure that the Subnetworkfield contains exactly the same subnetwork name as the con-figured IED in the IEC 61850 OPC Server in CET (e.g text

“IEC61850 Subnetwork”) The subnetwork name appearslater in the External OPC DA Client configuration Also fill

in the Substation, Voltage Level and Bay fields

If the substation is given another name than TEMPLATE inthe SCL file, SCL Importer assumes that Substation, VoltageLevel, Bay and Subnetwork objects are already defined in thefile In this case, these fields are disabled If Substation,Voltage Level, Bay and Subnetwork need to be redefined

before importing, select the file type Configured IED

Description Files (.cid) in the file selection dialog.

The object text for protection process objects can be, for example, translated into aselected language by describing it in the SCL file with a key, such as

PTOC_NOC3LOW_OP The translated object text is available after importing a languagefile that includes the values for the used keys, for example PTOC_NOC3LOW_OP="3I>trip" If the translated text is used in the SCL file, the related default language file(English) is delivered with the connectivity package

Importing SCL configuration 5.8.1.

The SCL Importer can be used to automatically generate the process objects and theExternal OPC DA Client configuration for the IED

To import SCL configuration:

1 Open SCL Importer from the Application Objects tab in Tool Manager.

2 Select Tools > Importing Options and configure the options as in Figure 5.8.1-1 and click OK The settings are stored and need to be configured only once.

a070105.png

Figure 5.8.1-1 SCL Importer Options

3 To define the Active File, click ' ' to locate the SCL file (.CID)

4 Click Open and fill in the Object Identification information as in Figure 5.8.1-2.

Figure 5.8.1-2 Main view of SCL Importer

5 Click Preview to open a preview of the objects to be created; see Figure 5.8.1-3.