microscada pro sys 600 9 - abb ltd pro sys 600 9.2 iec 61850 system design configuration manual

MicroSCADA ProSYS 600 9.2SYS 600 9.2

IEC 61850 System Design

Configuration Manual

3

Contents

Copyrights ................................................................................. 5

1. Introduction..............................................................71.1. This manual .............................................................. 71.2. Use of symbols ......................................................... 71.3. Intended audience ..................................................... 71.4. Product documentation ............................................... 81.5. Document conventions ............................................... 81.6. Document revisions.................................................... 9

2. Safety information................................................... 112.1. Backup copies..........................................................112.2. Fault tracing.............................................................11

3. Requirements .........................................................133.1. Hardware requirements............................................. 133.2. Software requirements.............................................. 13

4. Configuration..........................................................154.1. Components of the IEC 61850-based system............... 15

4.1.1. SYS 600 base system .................................. 164.1.2. OPC Data Access Client ............................... 164.1.3. IEC 61850 OPC Server ................................ 174.1.4. Related engineering tools.............................. 174.1.5. IEC 61850 System Supervision Server ............ 174.1.6. IED connectivity........................................... 19

4.1.6.1. Connectivity Packages ................... 204.2. Configuration environment......................................... 214.3. Configuring the SYS 600 base system ........................ 224.4. Building the physical IEC 61850 network ..................... 234.5. Configuring SPA-ZC 40_ ........................................... 23

4.5.1. Creating a new project.................................. 234.5.2. Adding a device object ................................. 234.5.3. Importing the IEC 61850 data object model of

an IED ....................................................... 244.5.4. Downloading configuration and exporting CID

file............................................................. 254.5.5. Restarting................................................... 274.5.6. Configuring report control blocks .................... 27

4.6. Configuring IEC 61850 OPC Server............................ 304.6.1. Creating a new project.................................. 304.6.2. Defining IEC 61850 OPC Server .................... 304.6.3. Importing IED configuration ........................... 31

MicroSCADA Pro

IEC 61850 System DesignConfiguration Manual

SYS 600 9.2SYS 600 9.21MRS756119

Issued: 23.03.2007Version: A/23.03.2007

4.6.4. Time Synchronization ................................... 324.6.5. Timeout handling ......................................... 33

4.7. Creating process objects........................................... 334.7.1. Importing SCL configuration........................... 344.7.2. Importing a language translation file................ 364.7.3. Addressing of process objects ....................... 37

4.8. Configuring OPC Data Access Client .......................... 394.8.1. Connecting to IEC 61850 OPC Server ............ 394.8.2. Auto-configuring OPC items for process

objects ....................................................... 414.8.3. Defining configuration for the IEC 61850 Hot

Stand-by system.......................................... 424.8.4. Defining the event buffer ............................... 43

4.9. Configuring an OPC Data Access Client instance ......... 444.9.1. IEC 61850 Hot Stand-by system topology........ 444.9.2. Starting an OPC Data Access Client instance... 454.9.3. Stopping an OPC Data Access Client instance... 45

4.10. Single-line diagram engineering ................................. 454.10.1. Adding objects into the display....................... 454.10.2. Adding Station Local/Remote Switch............... 474.10.3. Editing data variables in the display ................ 48

4.11. Configuring IEC 61850 System Supervision Server ....... 504.11.1. Installing IEC 61850 System Supervision

Server........................................................ 504.11.2. Starting IEC 61850 System Supervision

Server........................................................ 504.11.3. Stopping IEC 61850 System Supervision

Server........................................................ 514.11.4. Configuring IEC 61850 System Supervision

Server........................................................ 51

5. Testing configuration ..............................................555.1. Testing SPA-ZC 40_ and IEC 61850 OPC Server

configurations.......................................................... 555.2. Testing OPC Data Access Client start-up..................... 565.3. Testing IED control commands using process display .... 575.4. Testing IEC 61850 System Supervision Server ............. 57

6. Distributed system topologies..................................59

7. IEC 61850 System recommendations........................61

8. Troubleshooting......................................................63

9. Conformance statements.........................................65

10. Terminology ...........................................................69

11. Abbreviations .........................................................71

4

SYS 600 9.2SYS 600 9.2 MicroSCADA ProIEC 61850 System Design


1MRS756119

5

CopyrightsThe information in this document is subject to change without notice and should notbe construed as a commitment by ABB Oy. ABB Oy assumes no responsibility forany errors that may appear in this document.

In no event shall ABB Oy be liable for direct, indirect, special, incidental orconsequential damages of any nature or kind arising from the use of this document,nor shall ABB Oy be liable for incidental or consequential damages arising fromuse of any software or hardware described in this document.

This document and parts thereof must not be reproduced or copied without writtenpermission from ABB Oy, and the contents thereof must not be imparted to a thirdparty nor used for any unauthorized purpose.

The software or hardware described in this document is furnished under a licenseand may be used, copied, or disclosed only in accordance with the terms of suchlicense.

Copyright © 2007 ABB Oy

All rights reserved.

Trademarks

ABB is a registered trademark of ABB Group. All other brand or product namesmentioned in this document may be trademarks or registered trademarks of theirrespective holders.

Guarantee

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

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

7

1. Introduction

1.1. This manual

This manual provides thorough information on the various configuration settingsthat you have to make in order to take your SYS 600 system into use, focusing ondescribing how to configure SYS 600 for an IEC 61850 system. The manual alsodescribes how to use the configuration tools.

1.2. Use of symbols

This publication includes the following icons that point out safety-related conditionsor other important information:

The caution icon indicates important information or warning related tothe concept discussed in the text. It might indicate the presence of ahazard which could result in corruption of software or damage toequipment or property.

The information icon alerts the reader to relevant facts and conditions.

It should be understood that operation of damaged equipment could, under certainoperational conditions, result in degraded process performance leading toinformation or property loss. Therefore, comply fully with all notices.

1.3. Intended audience

This manual is intended for engineers to support configuration and engineering ofsystems and/or applications.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

1.4. Product documentation

Name of the document Document ID

SYS 600 Application Design 1MRS756170

SYS 600 OPC Data Access Client 1MRS756163

SYS 600 Process Display Design 1MRS756117

SYS 600 Picture Editing 1MRS756116

SYS 600 Status Codes 1MRS756178

IEC 61850 Master Protocol (OPC) 1MRS756230

SPA-ZC 400, SPA to IEC 61850 Gateway, Installation andCommissioning Manual

1MRS755347

SPA-ZC 402, SPA to IEC 61850 Gateway, Installation andCommissioning Manual

1MRS755380

1.5. Document conventions

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 the name of a keyboard key if it is labeled on thekeyboard. For example, press the CTRL key. Although the Enter and Shift keysare not labeled they are written in capital letters, e.g. press ENTER.

* Lowercase letters are used for the name of a keyboard key that is not labeled onthe keyboard. 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 copya 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 isdisplayed: Entered value is not valid.

You may be told to enter the string MIF349 in a field. The string is shown asfollows in the procedure: MIF349

* Variables are shown using lowercase letters: sequence name

8



1MRS756119

9

1.6. Document revisions

Version Software revisionnumber

Date History

A 9.2 23.03.2007 Document created

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

11

2. Safety informationThis chapter provides information on prevention of hazards.

2.1. Backup copies

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 anotherlocation, usually to a CD or a backup tape. A writable DVD and DAT tape arecommonly used.

Backup copying makes it easier to restore the application software in case of diskcrash or other severe failure when stored data is lost. It is therefore recommendedthat backup copies are taken regularly.

There should be at least two system backup copies and two application copies. Anew backup is copied over the oldest backup. This way the latest version is alwaysavailable, even if the backup procedure fails.

Detailed information on how to take backup copies is delivered to the customer withthe application.

System backup

Usually, a system backup is taken after the application has been configured. Itshould be taken again when changes are made to the SYS 600 system. This is thecase, for example, 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 tothe application. This is the case, for example, when pictures or databases are editedor new pictures are added.

2.2. Fault tracing

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 600Control Panel, try to end the task in Windows Task Manager.

Shutting down the base system computers by switching off the powermight damage the files.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

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. Analyzeand copy the data in this file.

4. Restart the system.

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

Error messages in SCIL are called status codes. A list of status codes and shortexplanations can be found in the Status Codes manual.

12



1MRS756119

13

3. RequirementsThe installation and configuration of the devices that use the IEC 61850-8-1protocol consist of:

* Hardware installation* Software installation

3.1. Hardware requirements

The hardware components listed below are usually required in IEC 61850 systems.In addition to the hardware itself, this equipment may require the configuration ofthe appropriate driver in the appropriate operating system.

* Time synchronization device with SNTP Server (for example MeinbergLANTIME/GPS)

* RuggedCom RS1600/8000 or RSG 2100, for example. For more information,see http://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 converter

Printer Server usually provides diagnostics information in Ethernet via the SNMPprotocol. The proposed way to include this information into SYS 600 is to convert itinto OPC item updates using a third-party SNMP to the OPC Server component.The OPC item updates are then mapped to the SYS 600 process database via OPCDA Client.

3.2. Software requirements

The following software is required:

* MicroSCADA Pro SYS 600 9.2

The following software is optional:

* IED configuration tools (for example Communication Engineering Tool for SPA-ZC 40x version 2.0 or later)

* PCM 600* Connectivity Packages for IEDs (for example REF 541/543/545 Connectivity

Package version 2.0 or later)

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

15

4. Configuration

4.1. Components of the IEC 61850-based system

The related components of the IEC 61850-based system (see Fig. 4.1.-1) aredescribed in the following sections:

* 4.1.1. SYS 600 base system* 4.1.2. OPC Data Access Client* 4.1.3. IEC 61850 OPC Server* 4.1.4. Related engineering tools* 4.1.5. IEC 61850 System Supervision Server* 4.1.6. IED connectivity

��

��

��

��

��

��

� ��!"#��#$#��%

�� &�##'"�"!"#�

(�#�#

��"�� )�&�*��#

�� &�##�'�#)�"$#

��+��+� ��

��

��

A060436

Fig. 4.1.-1 Related components of the IEC 61850-based system

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

4.1.1. SYS 600 base system

Station pictures, process displays and lists, providing the operator with informationon the SYS 600 base system, are found in process and report databases within thesystem. In the SYS 600 system, each signal update from an IED is represented witha unique addressing based on station (Unit Number) and object addressing (Blockand Bit number).

OPC DA Client interacts with the base system through a node connected to theTCP/IP link. Thus the underlying IEDs using the IEC 61850-8-1 protocol arerepresented as communication stations in the system.

Consequently, the related base system objects, that is link, node and station(s), mustbe introduced 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 thefile \sc\sys\active\sys_\sys_bascon.com.

4.1.2. OPC Data Access Client

OPC DA Client is configured by using OPC DA Client Configuration Tool. In thistool, configuration related to IEC 61850 OPC Server, SYS 600 base system objectsand application engineering is defined.

IEC 61850 OPC Server

* IEC 61850 OPC Server CLSID and its location (Local or Remote Server) areassigned 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.

Signal engineering

* OPC items exposed by IEC 61850 OPC Server are mapped to SYS 600 processobjects.

* Each OPC item is defined to belong to a specific OPC group and communicationstation representative. Position indications (binary signals) usually belong to anOPC group with an update rate of 0 ms, which is supported by IEC 61850 OPCServer. In this case, all signal changes are immediately sent to OPC DA Client.Measurements (analog signals) usually belong to an OPC group with an updaterate of 1000 ms. In this case, signal changes shorter than 1000 ms are not sent toOPC DA Client.

16



1MRS756119

17

4.1.3. IEC 61850 OPC Server

IEC 61850 OPC Server is configured by using CET for IEC 61850 OPC Server andinteracts in real time with IEC 61850 process devices and OPC DA Client.

4.1.4. Related engineering tools

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

4.1.5. IEC 61850 System Supervision Server

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 61850process objects and is configurable with SCL. To be able to generate events throughIEC 61850, the SSS must receive the data changes from the OPC server with OPCitem updates, as IEC 61850 does no explicit reading. IEC 61850 SSS requires anIEC 61850 license (SYS or COM). OPC Server-related components are presented inFig. 4.1.5.-1.

��

� ��

� ��

��

� ��

! ��"��#��

� ��

��+

��

�� &�##��"�"!"#�

A060813

Fig. 4.1.5.-1 OPC Server-related components

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

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

reporting service.* Value overrides (GOOD and BAD). The value GOOD overrides all updated

values, whereas BAD is used in case of errors (disconnect).* Event update timer (TIMER)

* 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 withreporting service.

* 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 61850ACSI conformance

The compliance with IEC 61850 in terms of service, modeling and engineeringinterfaces is defined as follows (those listed are supported):

ACSI basic conformance statement

Client-Server roles

Server side (of TWO-PARTY-APPLICATION-ASSOCIATION)

SCSMs supported

SCSM: IEC 61850-8-1 used

ACSI models conformance statement

Server

Logical device

Logical node

Data

Data set

Reporting

Buffered report control

Unbuffered report control

18



1MRS756119

19

ACSI service conformance statement

Server

ServerDirectory

Application Association

Associate

Abort

Release

Logical device

LogicalDeviceDirectory

Logical node

LogicalNodeDirectory

GetAllDataValues

Data

GetDataValues

GetDataDirectory

GetDataDefinituion

Data set

GetDataSetValues

GetDataSetDirectory

Reporting

BRCB

Report

GetBRCBValues

SetBRCBValues

URCB

Report

GetURCBValues

SetURCBValues

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 CDCsAddrs).

5. Starts the IEC 61850 server for IEC 61850 clients.

4.1.6. IED connectivity

The concept of Connectivity Packages has been introduced together withMicroSCADA Pro SYS 600 and will gradually replace the role of the LIB packagesin IED engineering. Unlike the LIB packages, the connectivity packages do notinclude IED tools. Instead, PCM 600 can be integrated and used together withSYS 600. However, the IED tools included in the LIB packages can also be used

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

together with SYS 600 and Monitor Pro process displays. For further information onintegrating IED tools, refer to the Application Design manual and Process DisplayDesign manual.

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 ofengineering definitions related to process database and graphical user interface.

In the graphical user interface, the common user interface components of SA-LIB(for example control dialogs) are used to interact with the process database. Duringsingle-line diagram engineering, the application-related set of process displaysymbols has been selected 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

4.1.6.1. Connectivity Packages

The concept of Connectivity Packages for IEDs provides harmonized engineeringand minimizes the dependencies between different releases of IEDs, systemproducts and tools. IED configuration management of parameters, measurementsand functions can be realized by importing IED descriptions. This information isincluded together with the IED when integrating the IED into system products andtools; see Fig. 4.1.6.1.-1.

A060648

Fig. 4.1.6.1.-1 IED connectivity

20



1MRS756119

21

Achieving full IED connectivity in SYS 600 requires that the application's processdatabase contains the following process object models:

* control and supervision* protection functions

The process database model of control and supervision consists of positionindications, commands and measurements, whereas the process database model ofprotection functions consists of protection events. Connectivity Packages are used toconstruct this information in a reliable way into the process database and to achieveeffective engineering without additional manual work.

Each Connectivity Package includes all the information and functionality requiredfor efficient integration of the IED into system level products and tools. TheConnectivity Package description of an IED is according to IEC 61850 andcontains:

* data signal description* parameter description* protocol addresses* documentation* IED interface modules, for example for disturbance file handling

The amount of IED information may differ depending on the service level of theconnectivity package. The supported protocols (this manual focuses on theIEC 61850 protocol) and service level of a specific connectivity package is definedseparately for each IED.

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 thecase when SCL Importer is used for importing the SCL information either from CIDor SCD files into the application. The created process database is connected to theSA-LIB process symbols during display engineering and interacts with the Controldialog boxes of SYS 600 at run-time.

To understand the process object model of SA-LIB through the IEC 61850modeling, refer to Chapter 9. Conformance statements for the logical nodessupported by SA-LIB.

4.2. Configuration environment

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

* IED (SPA-ZC 40_ if used)* IEC 61850 OPC Server* OPC Data Access Client* SYS 600 process database and HMI

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

Fig. 4.1.-1 illustrates the software components, including their interrelationshipsand underlying communication architecture. The SYS 600 base system, OPC DAClient and IEC 61850 OPC Server are usually all located on the same computer.

4.3. Configuring the SYS 600 base system

Traditionally, 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 OPC DA Client node and thecommunication station(s) are configured for both SYS 600 redundancy systems.

1. Open SYS 600 Control Panel.

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

3. In the sys_bascon.com file, scroll down to section Communication Links andadd the LAN link LIN1.

...;Communication Links;NOTE! Use the system configuration tool to create a link for the PC-NET!......;Begin LIN for TCP/IP Communication#CREATE LIN:V = LIST(- ;Link (requires TCP/IP)

LT = "LAN") ; Link type#CREATE LIN2:B = %LIN; End LIN for TCP/IP Communication...

4. Scroll down to section Node objects and add the OPC DA Client node NOD8....; Node objects (NET’s and SYS’s); NOTE! Use the system configuration tool to create nodes; for the PC-NET!......; Begin OPC DA Client NOD for IEC 61850 OPC Server#CREATE NOD:V =LIST(- ; Client node

LI = 2,- ;Client Link numberSA = 208,- ; Node addressNN = "SYS1",- ; Name of the basesystemDT = 10) ; Diagnostic interval

#CREATE NOD8:B = %NOD ; Creating node; End OPC DA Client NOD for IEC 61850 OPC Server…

5. Scroll down to section Other stations and add the communication station STA60....; Otherstations; NOTE! Use the system configuration tool to create; stations for the PC-NET!......; Begin OPC DA Client STA for IEC 61850 OPC Server#CREATE STA:V = LIST(-

TT = "EXTERNAL", -ST = "SPA", -TR = "UTC", -ND = 8,-TN = 60)

#CREATE STA60:B = %STA; End OPC DA Client STA for IEC 61850 OPC Server...

6. Save the sys_bascon.com file. The changes take effect the next time SYS 600 isstarted. Possible configuration errors will appear in SYS 600 NotificationWindow.

22



1MRS756119

23

The contents of the sys_bascon.com file is identical for both HSBsystems, with the exception of the unique node and station numbers.

4.4. Building the physical IEC 61850 network

The devices in the IEC 61850 network should first become connected in systemaccording to the wiring diagrams and layout pictures. Setting up the devices mayrequire that their addresses and the protocols in question are configured according tothe system requirements.

4.5. Configuring SPA-ZC 40_

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

4.5.1. Creating a new project

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.

4.5.2. Adding a device object

A project can contain several IEC 61850 device objects. All substation feederconfigurations and exported communication, for example, must be done separatelyfor each device. To add an IEC 61850 device object to the project, right-click theproject and select New > IEC 61850 > SPA-ZC 40_; see Fig. 4.5.2.-1.

A040023B

Fig. 4.5.2.-1 Adding an IEC 61850 device object

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

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

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

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 importedfrom CAP 505 Application Library to the specified directory.

CET for SPA-ZC 40x converts the project files to an IEC 61850 data object modelusing connectivity packages. However, the connectivity packages do not necessarilysupport all the functions of an IED. Functions not mapped to the IEC 61850structure are reported after import.

CET for SPA-ZC 40x imports default data sets and RCBs to the logical device LD0;see Fig. 4.5.3.-1. A data set includes data attributes selected from an IED'sIEC 61850 data model. The data sets are used in the IEC 61850 event reportingmodel. If the same data attributes that have been selected to be included in a data setare used in an RCB, the data set generates a spontaneous event which is sent to theIEC 61850 client. If the data set is not used in an RCB, the IEC 61850 client readsthe data separately.

After adding a new IED, give it a unique name in the network. Spacesare not allowed in the IED's name. Renaming can be done in ProjectExplorer; see Fig. 4.5.3.-1.

24



1MRS756119

25

A040026B

Fig. 4.5.3.-1 Project Explorer in the Communication Engineering Tool window

4.5.4. Downloading configuration and exporting CID file

After you have built the IEC 61850 data object model and configured thecommunication addressing, you can download the configuration to SPA-ZC 40_;see Fig. 4.5.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 thedefault IP address 192.168.2.10 with a new address according to the plannednetwork structure.

When the new configuration is being downloaded to SPA-ZC 40_, CET checks ifthe basic IP addresses are changed. If a change is detected, CET asks whether youwant to take the new addresses into use. If you do not accept the changes,SPA-ZC 40_ uses the old IP addresses from the previous configuration.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

A040029B

Fig. 4.5.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 exportfile accordingly. If a connection to the system cannot be established, prompt thecorrect version to be exported; see Fig. 4.5.4.-2.

A060129

Fig. 4.5.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. Forexample, if you select to export a data set at the FCD level, an information reportfrom SPA-ZC 40_ always contains value, quality and time in one structure. You canalso export the CID or ICD file to your workstation's file system and use it in systemlevel tools, for example to configure your IEC 61850 client.

26



1MRS756119

27

4.5.5. Restarting

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

1. Select IED and then Tools > Reset Tool to open the restart pane; see Fig. 4.5.5.-1.

2. Click Reset.

The results are reported in the UI text box.

Do not use the restart function while downloading configuration toSPA-ZC 40_. When the download is complete, SPA-ZC 40_ isautomatically restarted.

A060396

Fig. 4.5.5.-1 Restarting

4.5.6. Configuring report control blocks

RCBs control the spontaneous event reporting. The client can modify the eventreporting by setting RCB attributes. Both buffered and unbuffered RCBs aresupported. The RCB attributes' default values are suitable for the following ABBproducts:

* COM 610* SYS 600 IEC 61850 client.

RCBs are located under the logical device LD0 and logical node LLN0; see 4.5.6.-1.For information on RCB dedication, refer to the IEC 61850 Master Protocol (OPC)manual.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

,�) ��-"�'��.

��+ �� .

,�) ��

��

& �� #& �� #

/"#�"## &�"��

,�) ��#

0��1��) ��& �� "��!*��"�*�#�*!#&��!��2 ��) ��3

.�� &"��##*�

�"�"��

��

��

��

�"�"��

��

��

��

��

��

��

,�"��"�"

A060032

Fig. 4.5.6.-1 Reporting model

RCBs have the following properties:

* Buffered reporting

IEC 61850 buffers events also during a communication break.

* Buffer Time

The default value is 100 ms. Consequently, the RCB waits 100 ms for otherevents after the first change before sending the report.

* Integrity Period

The 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 isnot enabled by default, because it causes excessive load to the server and thenetwork.

* Report ID

SPA-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 Fields

Defines 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.

* Max

Defines how many clients use the RCB, that is the number of required RCBinstances. If two clients for buffered reporting are defined, Max has to be set to 2.SPA-ZC 40_ creates two instances of the RCB name, for example rcbStatNrml01and rcbStatNrml02. For unbuffered reporting, Max has to be the same or higheras the number of defined clients in accordance with the IEC 61850 standard.

* Trigger Options

28



1MRS756119

29

Data Change, Data Update and Quality Change triggers are used by default.Consequently, changes in value and quality generate information reports. Aperiod trigger is not used by default.

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

A040134B

Fig. 4.5.6.-2 Report control block

Buffered reporting requires that clients are defined. Report Client definitions link acertain RCB to a certain client. The client can import the CID file to check whichRCB instance it has to use. If Max is set to 2, the configuration must have twoclients with buffered reporting. The first client on the list uses the first RCB instance(rcb name ...01) and the second client the second instance (rcb name ...02 ).

Unbuffered reporting does not require that clients are defined, but it isrecommended for clarity. Client IED Name has to match with the client name inSCL.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

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

4.6. Configuring IEC 61850 OPC Server

IEC 61850 OPC Server is configured using CET for IEC 61850 OPC Server in SYS600. With this tool, the hierarchically structured models of a substation or a systemare built and loaded into configuration files of IEC 61850 OPC Server.

To start CET for IEC 61850 OPC Server:

1. Open MicroSCADA Pro Control System SYS 600.

2. Open IEC 61850 OPC Server.

3. Double-click Communication Engineering Tool for IEC 61850 OPC Server.

4.6.1. Creating a new project

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.

4.6.2. Defining IEC 61850 OPC Server

Define IEC 61850 OPC Server as follows:

1. Right-click the project and select New > Communication > Computer Node toadd a computer node to the project.

2. Select View > Object Properties to open Object Properties.

3. Select the computer node and define Node Name as 127.0.0.1.

4. Right-click the computer node and select New > IEC 61850 > IEC 61850 OPCServer to add an IEC 61850 OPC server.

Define Client1 as the Report Control Identity for the IEC 61850 OPC server.

5. Right-click IEC 61850 OPC Server and select New > IEC 61850 > IEC 61850Subnetwork to add an IEC 61850 subnetwork to the IEC 61850 OPC server.

6. Right-click IEC 61850 Subnetwork and select New > IEC 61850 Subnetwork >IEC 61850 IED to add an IEC 61850 IED to the IEC 61850 subnetwork.

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

30



1MRS756119

31

4.6.3. Importing IED configuration

To import IED configuration:

1. Right-click IEC 61850 IED and select SCL Import.

2. In the SCL Import pane, click Choose File.

3. Select the IED SCL configuration file (for SPA-ZC 40_ the .CID file previouslycreated with CET for SPA-ZC 40x) and click Open.

4. Click Import and close the pane; see Fig. 4.6.3.-1.

A060440

Fig. 4.6.3.-1 SCL Import pane

To allow multiple clients to receive the same data values, multiple instances of thereport control classes must be made available. Specify the RCB instances usingReport Enabled and Report Client and dedicate them to clients using Report Client.For further information, refer to the IEC 61850 Master Protocol (OPC) manual. Allconfigured RCBs without instances specified for IEC 61850 OPC Server arediscarded.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

To enable IEC 61850 OPC Server to use the server-specific RCB instances and thusreceive spontaneous events, the Report Control Identity field must match one of theReport Enabled fields in the device's RCB configurations. If the fields do not match,the configured RCB instance is discarded.

Update IEC 61850 OPC Server as follows (see Fig. 4.6.3.-2):

1. Right-click Computer Node and select Management.

2. Click Update Configuration and then Reload Configuration.

3. Close the Management pane.

A060441

Fig. 4.6.3.-2 Management pane

4.6.4. Time Synchronization

IEC 61850 OPC Server can act as an SNTP client and server for timesynchronization.

SNTP Client

Supports four alternative SNTP servers. For further information, refer to theIEC 61850 Master Protocol (OPC) manual.

32



1MRS756119

33

SNTP Server

When IEC 61850 OPC Server is configured for time synchronization, it updates theoperating system time of the workstation. For further information, refer to theIEC 61850 Master Protocol (OPC) manual.

In order for SNTP Server to work in IEC 61850 OPC Server, theWindows time synchronization service (Windows Time) must bedisabled since it occupies the SNTP server port of the workstation.

4.6.5. Timeout handling

When parameter setting or disturbance upload operations are performed by usingrelay tools such as CAP, SMS or LIB, their default timeout of 5 seconds is used. InCET for IEC 61850 OPC Server, the default SPA TCP timeout is 3 seconds.

To enable fluent interaction in case of possible communication failures during relaytool-specific operations, it is recommended not to change the default SPA TCPtimeout. The configuration parameters should be defined according to the followingprinciple: SPA TCP Timeout (3 seconds) < Read/Write timeout of OPC DA Client(4 seconds) < default timeout of relay tools (5 seconds).

4.7. Creating process objects

In the IEC 61850-based system, SCL Importer usually creates the applicationobjects into the SYS 600 process database from the files following the SCL model.The prerequisite is that the SCL files contain the Substation section, whose contentsis further applied to the Object Identification attribute values, which in turn areassigned to the process objects. Before importing the SCL file:

* Ensure that the subnetwork matches the definition in CET for IEC 61850 OPCServer.

* Fill in Substation, Voltage Level and Bay.

If the substation is given another name than TEMPLATE in the SCLfile, SCL Importer assumes that Substation, Voltage Level, Bay andSubnetwork are already defined in the file. In this case, these fields aredisabled. If Substation, Voltage Level, Bay and Subnetwork need to beredefined before importing, select the file type Configured IEDDescription Files (.cid) in the file selection dialog box.

The object text for protection process objects, for example, can be translated into aselected language by describing it in the SCL file with a key such asPTOC_NOC3LOW_OP. The translated object text will then be available after

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

importing a language file that includes the values for the used keys, for examplePTOC_NOC3LOW_OP="3I> trip". If the translated text is used in the SCL file, therelated default language file (English) is delivered with the connectivity package.

The process objects created with SCL Importer are further adjusted at a later stagevia the operations performed with OPC PO List Tool.

4.7.1. Importing SCL configuration

To import SCL configuration:

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

2. Click Browse to locate the SCL file (.CID).

3. Click Open and fill in the Object Identification information as in Fig. 4.7.1.-1.

Ensure that the Subnetwork field contains exactly the text “IEC61850Subnetwork”, as it appears later in OPC DA Client-related configuration tools.

34



1MRS756119

35

A060442

Fig. 4.7.1.-1 Main view of SCL Importer

4. Click Preview to open a preview of the objects to be created; see Fig. 4.7.1.-2.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

A060691

Fig. 4.7.1.-2 Import Preview

5. Click Import and close the tool.

Some names of process objects created with SCL Importer might betoo long (> 10 characters) for Classic Monitor station pictures. In thiscase, rename the process object using no more than 10 characters.

4.7.2. Importing a language translation file

To import a language translation file:

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

2. Click Browse to open the file type and name selection dialog box.

3. Select the file type Connectivity Package Language Files (.txt) and locate thelanguage file (for example C:\Program Files\ABB\Connectivity Packages\REF541_3_5\2.0\Communication\Language Support\EN\IEC\EN_IEC.txt).

4. Click Open.

5. Click Import and close the tool.

36



1MRS756119

37

4.7.3. Addressing of process objects

OPC PO List Tool facilitates the creation of mappings between OPC items and SYS600 process object addresses. OPC PO List Tool creates an output file in whichavailable process objects are listed and later recognized by OPC DA ClientConfiguration Tool.

To address process objects:

1. Open OPC PO List Tool from the System Configuration tab in Tool Manager.

2. Select Edit > Include All and click OK to accept the proposed station number;see Fig. 4.7.3.-1.

A060443

Fig. 4.7.3.-1 Main view of OPC PO List

3. Select File > Save As and save the file with the default file name OPCPOLIST.PL by clicking OK.

4. Before the save occurs, the dialog box in Fig. 4.7.3.-2 is displayed. Select theAssign new block address and bit number check box and click Save.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

A060444

Fig. 4.7.3.-2 Defining process objects to be saved

5. Because the process objects do not yet contain the addressing information, thedialog box in Fig. 4.7.3.-3 is displayed during the save operation. Click OK forAll to automatically generate all the block and bit addresses, and close OPC POList Tool.

A060445

Fig. 4.7.3.-3 Invalid process object address

38



1MRS756119

39

4.8. Configuring OPC Data Access Client

OPC DA Client is used for receiving communication from IEC 61850 OPC Server.The relationship to IEC 61850 OPC Server is defined when configuring OPC DAClient.

Each OPC DA Client configuration file usually contains the connection to oneIEC 61850 OPC server. However, the related configuration to be included into eachOPC DA Client may also be a subset of the overall OPC Namespace found inIEC 61850 OPC Server. Consequently, OPC DA Client may subscribe to only partof the IEC 61850 OPC Server signals representing only part of the system, forexample OPC items related to only medium- or high-voltage process devices. OneIEC 61850 OPC Server can thus serve several OPC DA Client instances at runtime.

To start OPC DA Client Configuration Tool:


2. Open OPC DA Client and double-click OPC DA Client Configuration Tool.

4.8.1. Connecting to IEC 61850 OPC Server

To connect to the OPC Server:

1. Select File > New to open Server Properties.

2. Click Browse to locate IEC 61850 OPC Server Data Access V2 in the list ofavailable servers.

3. Click Local Server if OPC DA Client and SYS 600 base system are located inthe same computer, as is the case in the typical IEC 61850 HSB system, andclick OK; see Fig. 4.8.1.-1.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

A060446

Fig. 4.8.1.-1 Locating the server

4. Click Next and fill in CPI Node Properties according to the previously madesys_bascon.com definitions; see Fig. 4.8.1.-2.

In the IEC 61850 HSB system, it is sufficient to define only the primary SYS600 settings. In this case, use the default Base IP Address 127.0.0.1.

A060447

Fig. 4.8.1.-2 Defining CPI Node Properties

5. Click OK to finish.

40



1MRS756119

41

4.8.2. Auto-configuring OPC items for process objects

To auto-configure OPC items:

1. Select File > Auto Configure and click Browse to locate the PO List filepreviously created with OPC PO List Tool.

2. Click Open after locating the file, which by default is located in the folder \sc\sys\active\sys_ with the name OPCPOLIST.PL.

3. Fill in Auto Configure and click Configure; see Fig. 4.8.2.-1.

A060448

Fig. 4.8.2.-1 Auto-configuring OPC items

4. If a warning appears, click Yes to continue the operation; see Fig. 4.8.2.-2.

This is the case when OPC DA Client Configuration Tool cannot validate thecreated OPC item in IEC 61850 OPC Server.

A060449

Fig. 4.8.2.-2 Warning of validation failure

All the non-validated OPC items are found in the file with the extension .trc in thefolder \sc\sys\active\sys_. When the auto-configuring is complete, the OPC DAClient configuration is displayed as in Fig. 4.8.2.-3.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

A060450

Fig. 4.8.2.-3 Main view of OPC DA Client Configuration Tool

One or multiple OPC groups are defined for each communication stationrepresenting an IEC 61850 process device. For OPC groups containing items relatedto position indication and control commands, the update rate should be 0 ms. ForOPC groups containing measurement values, however, an update rate of forexample 1000 ms is accepted. The Update rate setting specifies the interval time forOPC DA Client's polling of OPC items from IEC 61850 OPC Server. An update rateof 0 ms means that no events are lost and the functionality is supported byIEC 61850 OPC Server.

4.8.3. Defining configuration for the IEC 61850 Hot Stand-by system

To define the configuration for IEC 61850HSB System in OPC DA ClientConfiguration Tool, right-click CPI Node and select IEC 61850 in HSB system; seeFig. 4.8.3.-1.

42



1MRS756119

43

A060452

Fig. 4.8.3.-1 Turning on IEC 61850 in HSB System

4.8.4. Defining the event buffer

In IEC 61850 HSB systems, define the event buffer as follows:

1. Right-click CPI Node and select Buffering Settings; see Fig. 4.8.4.-1.

A060453

Fig. 4.8.4.-1 Event Buffering settings

2. Under Buffering Type, click Circular Buffering and set the parameter Keepevents (deltaT).

Keep events (deltaT) specifies the maximum amount of time in seconds for theevents buffered by OPC DA Client and should be adjusted to the switch-overtime.

3. Click OK to close OPC DA Client Tool, and save the configuration file.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

4.9. Configuring an OPC Data Access Client instance

4.9.1. IEC 61850 Hot Stand-by system topology

The configuration of the IEC 61850 communication system in the SYS 600 HSBenvironment is presented in Fig. 4.9.1.-1. In HSB systems that include IEC 61850process devices, OPC DA Client and IEC 61850 OPC Server are usually bothlocated in the same computer, together with the SYS 600 base system.

��+�4��,�� +�4��,�5

5�� +

5�� +

-�5

��

��

��

��

��&��6� ��&��67 888A060454

Fig. 4.9.1.-1 Topology of a typical HSB system with IEC 61850 process communication

IEC 61850 process devices of a physical network are configured to have twomasters, one in Computer A and another in Computer B. When a fault occurs in theprimary base system (computer A), including the HOT application, the shadowingapplication in the stand-by base system (computer B) starts and takes over all theoperational functions. In HSB systems, there is usually a need to minimize theswitch-over time.

In Fig. 4.9.1.-1, the IEC 61850 OPC servers are active both in the primary(including HOT application) and the stand-by (including the shadowing application)computer. This enables data coming from IEC 61850 process devices to always bestored into buffers of both IEC 61850 OPC servers.

Further, OPC DA Client should be located in the same computer as where the basesystem is running. When the application state changes to HOT, OPC DA Clientshould be configured according to the application initialization procedures(APL_INIT_*) as defined in Section 4.9.2. Starting an OPC Data Access Clientinstance.

44



1MRS756119

45

4.9.2. Starting an OPC Data Access Client instance

The OPC DA Client instance is usually started via the additional application,START_COMM. This also applies to the other communication components, forexample PC-NET. Technically, it is also possible to use the watchdog application forthe same purpose. However, it should be remembered that the watchdog applicationshould be dedicated to its main task alone, that is the watchdog functionalitybetween HSB partners.

At the same time as the SYS 600 system is starting up, the OPC DA Client instanceautomatically starts, provided that the application objects of the previouslymentioned additional application have been configured accordingly.

APL_INIT_1:C; This is executed when applications goes hot; Start OPC DA Client after a delay#exec_after 10 start_opc_da_client_instance:c

START_OPC_DA_CLIENT_INSTANCE:C#error ignore@abb = ops_call(“C:\sc\prog\OPC_Client\DA_Client\daopccl.exe –id “”iec61850”” –start “”C:\sc\sys\active\sys_\iec61850.ini”” –trace normal”, 0)

4.9.3. Stopping an OPC Data Access Client instance

When SYS 600 is shutting down, the corresponding instance of an OPC DA Clientshould be stopped.

1. Use the following statement in the APL_CLOSE command procedure:; Stop OPC DA Client instance#do STOP_OPC_DA_CLIENT_INSTANCE:C

2. Create the related command procedure.STOP_OPC_DA_CLIENT_INSTANCE:C#error ignore@abb = ops_call(“C:\sc\prog\OPC_Client\DA_Client\Daopccl.exe –id “”iec61850”” –stop”, 0)

4.10. Single-line diagram engineering

Single-line diagram engineering is required to connect the process objects to processdisplays or station pictures. This is done either by using Display Builder or PictureEditor, depending on whether Classic Monitor or Monitor Pro graphics are used inthe system.

The overall documentation for Display Builder in Monitor Pro is included in theProcess Display Design manual. For Picture Editor in Classic Monitor, refer to thePicture Editing manual.

This chapter provides an overall understanding of single-line diagram engineeringrelated to Monitor Pro and some details related to IEC 61850 display engineering.

4.10.1. Adding objects into the display

To add objects into the display:

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

1. Start Display Builder from Monitor Pro by selecting Tools > System Tools >Display Builder.

2. Select File > New to create a new display.

3. Select Actions > Object Browser to open Object Browser.

4. Select the main application and click Select to list all objects from the selectedapplication.

5. Select Bay from the Object Browser list and click Create to add a Station Local/Remote switch to the display; see Fig. 4.10.1.-1. Alternatively, drag and drop theitem into the display file.

A060455

Fig. 4.10.1.-1 Main view of Display Builder.

Proceed in the same way to add position indications for the circuit breaker,disconnectors and the earth-switch. Also add phase current and neutral currentmeasurements.

46



1MRS756119

47

For process symbols representing IEC 61850 process devices, thepolarity of the position indication is different compared to devicescommunicating via other protocols, such as LON and SPA.Consequently, value swapping is required for IEC 61850-relatedprocess symbols during single-line diagram engineering.

Further, if an application's single-line diagram contains several IEC61850 process symbols, it is recommended to adjust the defaultpolarity of the position indication in Object Browser accordingly. Forfurther information, refer to the Application Design manual.

6. Select File > Save As to save the display, and close Display Builder.

For further information on process display engineering, refer to the Process DisplayDesign manual.

4.10.2. Adding Station Local/Remote Switch

The Station Local/Remote switch is used by the process display at run-time. To adda Station Local/Remote switch to the application:

1. Open Object Navigator from Monitor Pro by selecting Tools > System Tools >Tool Manager. Object Navigator is located on the Application Objects tab.

2. Select Object > Install Standard Function to open Standard Function Tool.

3. Select Station and click Install; see Fig. 4.10.2.-1

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

A060456

Fig. 4.10.2.-1 Installing station standard function

4. Fill in the correct information and click Apply.

5. Select the Tools tab to open Process Object Tool and click Create All.

6. Click Close and then OK.

7. Close Standard Function Tool.

The process objects related to Station Local/Remote Switch have now beencreated into the application.

8. Close Object Navigator.

9. Start Display Builder again and drag and drop the IEC 61850 item from ObjectBrowser to add a Station Local/Remote switch to the display.

4.10.3. Editing data variables in the display

Edit the data variables for bay and controllable objects in the display as follows:

1. Select Edit > Data Variables.

2. Under Value swapping for state indication, change the value swapping for stateindication for the IEC 61850 bay-related data variable from None to Swap values0 and 1 and click Apply; see Fig. 4.10.3.-1.

48



1MRS756119

49

A060457

Fig. 4.10.3.-1 Defining data variables

3. Change the value swapping for the data variables related to circuit-breakerposition from Swap values 0 and 1 to None and click Apply.

Make the same change to the data variables related to the disconnector and earth-switch.

When creating process displays that contain mainly symbols connectedto IEC 61850-signals, it is recommended to change the default value ofstate indication value swapping, as values are swapped by default.When swapping is selected, the state indication value 1 coming fromprocess objects is changed to 2 and the value 2 to 1. To take swappingout of use, change UsesReversedSingleIndications in objnav.ini to 0.

4. Save the display file by selecting File > Save As and close Display Builder.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

4.11. Configuring IEC 61850 System Supervision Server

4.11.1. Installing IEC 61850 System Supervision Server

To install IEC 61850 SSS:

1. Start command prompt in the folder sc\prog\IEC61850SystemSupervisionServer\bin.

2. Create an instance for DCOM registration by executing "makeinstOPCC_IEC61850 1" in cmd prompt. This creates a new folder,OPCC_IEC61850_1, with a unique CLSID for IEC 61850 SSS.

3. Register IEC 61850 SSS to be started by DCOM, either by executingopcc_iec61850.exe /regserver to run IEC 61850 SSS as a logged user, or byexecuting opcc_iec61850.exe /regserver /user [username] /pwd [password] torun IEC 61850 SSS as a different user (remove [ and ]).

4. Create the configuration file (Systemc.xml) into the folder OPCC_IEC61850_1.

After installation, the configuration template file Systemc$xml is found in the folderC:\sc\prog\IEC61850SystemSupervisionServer\bin\.

4.11.2. Starting IEC 61850 System Supervision Server

Configure OPC DA Client for IEC 61850 SSS OPC Server using OPC DA ClientConfiguration Tool; see Fig. 4.11.2.-1 (for configuring OPC Data Access Client,also refer to Section 4.8. Configuring OPC Data Access Client). SSS is registeredwith Prog ID: ABB.IEC61850_Slave_OPC_DA_Server.Instance[1].1.

A070090

Fig. 4.11.2.-1 Configuring OPC DA Client for IEC 61850 SSS OPC Server

Continue by configuring the OPC DA Client instance to start automatically whenthe SYS 600 system is starting up. The same configuration principles can befollowed as in Section 4.9.2. Starting an OPC Data Access Client instance.

50



1MRS756119

51

4.11.3. Stopping IEC 61850 System Supervision Server

Stop IEC 61850SSS by shutting down the SYS 600 OPC DA Client instanceconfigured for SSS. IEC 61850 SSS will shut down (provided that it was startedthrough DCOM) when all OPC clients have been disconnected. The sameconfiguration principles can be followed as in Section 4.9.3. Stopping an OPC DataAccess Client instance.

4.11.4. Configuring IEC 61850 System Supervision Server

IEC 61850 SSS is configured using SCL in the file Systemc.xml, which is to belocated in sc\prog\IEC61850SystemSupervisionServer\bin\OPCC_IEC61850_1. Atleast the bolded parts are to be configured, and the underlined parts are to remainconstant.

Communication

* The type must be ABB-OPC.* iedName = device name* apName = access point name* ProgId = OPC Server Prog ID (DCOM registered)* IP = local IP address of running workstation (127.0.0.1 can be used)

<Communication><SubNetwork name="NET" type="ABB-OPC">

<ConnectedAP iedName="SysSupSrv" apName="S1"><Address><!– Prog ID of a DCOM registered OPC Server to be connected –>ABB.MicroSCADA.OPC.Server.DA23192.168.2.200010001000000011,3,9999,23

</Address></ConnectedAP>

</SubNetwork></Communication>

IED

* name = device name* The type must be OPC Client.<IED name="SysSupSrv" type="OPC Client">* AccessPoint = access point<AccessPoint name="S1">* DataSet name = data set name* FCDA = CDC to be reported (required if spontanious updates of CDC are

required)

<DataSet name="DataSetSCADA"><FCDA ldInst="SCADA" prefix="" lnInst="1" lnClass="LPHD" doName="PhyHealth"fc="ST"/><FCDA ldInst="SCADA" prefix="" lnInst="1" lnClass="LPHD" doName="Timer1"fc="ST"/><FCDA ldInst="SCADA" prefix="" lnInst="1" lnClass="LPHD" doName="Timer2"fc="ST"/><FCDA ldInst="SCADA" prefix="" lnInst="1" lnClass="LPHD" doName="Update1"fc="ST"/><FCDA ldInst="SCADA" prefix="" lnInst="1" lnClass="LPHD" doName="Update2"fc="ST"/>

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

<FCDA ldInst="SCADA" prefix="" lnInst="1" lnClass="LPHD" doName="Update3"fc="ST"/>

</DataSet>

* ReportControl name = name of the report control block* ReportControl datSet = data set name

<ReportControl name="urcbRCB" rptID="uRCB" datSet="DataSetSCADA" confRev="0"buffered="false" bufTime="0">

<TrgOps dchg="true" qchg="true" dupd="true" period="false"/><OptFields seqNum="true" timeStamp="true" dataSet="false"reasonCode="true" dataRef="false" bufOvfl="false" entryID="true"configRef="false" segmentation="true"/><RptEnabled max="5">

<ClientLN iedName="Client1" ldInst="LD0" lnInst="1" lnClass="LLN0"/></RptEnabled>

</ReportControl>

* LDevice inst = logical device name<LDevice inst="SCADA">

DOI (CDC configuration and mapping)

* Constant values

If configured as constant, the values are always constant with GOOD quality.

<DOI name="Beh"><DAI name="stVal">

<Val>0</Val></DAI>

</DOI><DOI name="Health">

<DAI name="stVal"><Val>0</Val>

</DAI></DOI><DOI name="NamPlt">

<DAI name="vendor"><Val>ABB</Val>

</DAI><DAI name="swRev">

<Val>0</Val></DAI><DAI name="d">

<Val>MicroSCADA</Val></DAI><DAI name="configRev">

<Val>0</Val></DAI>

</DOI>

* Mapped timer values

If configured as timer, the values are received from IEC 61850 OPC Server, andthe quality and timestamp are set according to the quality and timestamp of thereceived OPC item. In case of timer expire or IEC 61850 OPC Serverdisconnect, the CDC value is set to 0 and the quality to BAD. The values can beoverridden by good or bad values. Good values are always used when updatesare received from IEC 61850 OPC Server, and bad values if the timer expires orIEC 61850 OPC Server disconnects.

* Mapped indication values

If configured as indication (UPDATE), the values are received from IEC 61850OPC Server, and the quality and timestamp are set according to the quality andtimestamp of the received OPC item. The indication value can be overridden byconfiguring a good value (GOOD=?). This value is used for all updated values,

52



1MRS756119

53

that is, every updated value from IEC 61850 OPC Server is overridden. In caseof IEC 61850 OPC Server disconnect, the CDC quality is set to BAD (if badvalue (BAD=?) is configured, the value will be overridden).

<!– MAPPED –><!– These are examples of how to configure mapped attributes from IEC 61850 OPCServer to IEC 61850 SSS. –><!– For IEC 61850 Clients to receive events, the mapped DOI must also beconfigured to a reporting dataset. –>

<!– Configuration parameters (sAddr): mapping,updaterate,type{,timeout}[,BAD=badvalue][,GOOD=goodvalue] –><!– where: –><!– mapping = IEC 61850 OPC Server full path name of the mapped item tag–><!– updaterate = OPC Group Update Rate (milliseconds) –><!– type = Mapping type ('UPDATE' for indication events, 'TIMER' for timedevents –><!– timeout = Timer timeout (only valid for TIMER, remove if using UPDATE)(milliseconds) –>

<!– badvalue = Bad value to be updated (overrides a value when disconnected ortimer expires) –>

<!– goodvalue = Good value to be updated (overrides a value from IEC 61850 OPCServer) –><!– NOTE! Use numeric values for bad and good values. –>

<!– Timer –>

<!– TIMER –><!– - creates an OPC group for mapped items with Group Update Rate =update rate –><!– - expects an update of the specified item within timeout msecs –><!– - if an update is not received, the quality is set to BAD (and the value isupdated with bad value if configured) –>

<!– - if an update is received, the value is updated (overridden by good value ifconfigured) –>

<!– The PhyHealth item executes the SCIL program for SCADA every 30000 msec andexpects an update –>

<!– - if an update is received within 35000 msec, the value is updated to 1 (ok)–><!– - in other cases, the value is updated to 3 (alarm) –>

<DOI name="PhyHealth"><DAI name="stVal" sAddr="\\APL\1\SCIL PROGRAM\#return second,30000,TIMER,35000,GOOD=1,BAD=3"></DAI>

</DOI>

<!– These are here for information purposes. ER and DM are not changed periodically,resulting in timer 1 and 2 entering the bad state. –>

<DOI name="Timer1"><DAI name="stVal" sAddr="\\SYS:ER,0,TIMER,30000"> <!– Enable Routing –></DAI>

</DOI>

<DOI name="Timer2"><DAI name="stVal" sAddr="\\SYS:DM,0,TIMER,30000,GOOD=1,BAD=0"><!– Debug Mode –></DAI>

</DOI>

<!– Indication –>

<!– Configuration parameters (sAddr): mapping,updaterate[,UPDATE[,BAD=badvalue][,GOOD=goodvalue]] –><!– mapping: IEC 61850 OPC Server full path name of the mapped item tag –><!– updaterate = OPC Group Update Rate (milliseconds) –><!– type = Mapping type ('UPDATE' for indication events, 'TIMER' for timedevents –>

<!– badvalue = Bad value to be updated (overrides a value when disconnected ortimer expires). –>

<!– goodvalue = Good value to be updated (overrides a value from IEC 61850 OPCServer). –><!– NOTE! Use numeric values for bad and good values. –>

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

<DOI name="Update1"><DAI name="stVal" sAddr="\\APL\1:AT,0"> <!– Alarm Tag –></DAI>

</DOI>

<DOI name="Update2"><DAI name="stVal" sAddr="\\APL\1:EE,0,UPDATE,GOOD=1,BAD=0"> <!– SystemEvent Enabled –></DAI>

</DOI>

<DOI name="Update3"><DAI name="stVal" sAddr="\\SYS:SH,0,UPDATE"> <!– Shadowing –></DAI>

</DOI>

Data type templates

<DataTypeTemplates>

<LNodeType id="LN0" lnClass="LLN0"><DO name="Mod" type="INC"/><DO name="Beh" type="INS"/><DO name="Health" type="INS"/><DO name="NamPlt" type="LPL_LN0"/>

</LNodeType>

<LNodeType id="LPHDa" lnClass="LPHD"><DO name="PhyNam" type="DPL"/><DO name="PhyHealth" type="INS"/><DO name="Proxy" type="SPS"/><DO name="Timer1" type="INS"/><DO name="Timer2" type="SPS"/><DO name="Update1" type="INS"/><DO name="Update2" type="SPS"/><DO name="Update3" type="INS"/>

</LNodeType>

IED (SSS manufacturer-specific settings)

* IED name = device name* The IED type must be OPC Client.* commonSA:Object type must be OPC Client¨.* commonSA:Name = device name* commonSA:Value (Treedelimiter) = OPC Server tree delimiter

<IED name="SysSupSrv" type="OPC Client" configVersion=""><Private type="ABB_CommonSA_OPCConfiguration"><commonSA:SAObjects><commonSA:Object type="OPC Client"><commonSA:Name>SysSupSrv</commonSA:Name>

<commonSA:Parameter name="TreeDelimiter"><commonSA:Value>\</commonSA:Value><commonSA:AttributeName>TreeDelimiter</commonSA:AttributeName>

</commonSA:Parameter>

54



1MRS756119

55

5. Testing configuration

5.1. Testing SPA-ZC 40_ and IEC 61850 OPC Server configurations

Use the Online diagnostics window in CET for IEC 61850 OPC Server to test thatthe individual IEC 61850 process device signals are updated accordingly.

For example, test that the circuit-breaker position indication is correctly updated inthe system:

1. Open SPA-ZC 40_ in the project structure.

2. Open the logical device LD1 and select the logical node CBCSWI120.

3. Right-click OPC Pos and select Online diagnostics; see Fig. 5.1.-1.

A060458

Fig. 5.1.-1 Opening the Online diagnostics window

When the process device signal is changed for the circuit-breaker position indicationby using a simulator, stVal is to be changed according to the position of the signal asin Table 5.1.-1.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

Table 5.1.-1 StVal settings

Circuit breaker stVal

00 Undefined 0

10 Open 1

01 Closed 2

11 Undefined 3

5.2. Testing OPC Data Access Client start-up

To test the OPC DA Client start-up:


2. Open OPC DA Client and OPC DA Client Control Panel.

3. Click New Instance and then Browse to specify the location of the OPC DAClient Configuration file.

4. Select the correct file and click Open.

5. Click OK to close the dialog box.

OPC DA Client is now starting up an instance according to the selectedconfiguration. When an instance is successfully started, it is found in List of OPCDA Client Instances; see Fig. 5.2.-1.

A060459

Fig. 5.2.-1 Starting up an OPC Data Access Client instance

However, if an instance is not successfully started, the reason may be one of thefollowing:

* CPI Node Properties of OPC DA Client Configuration does not match with thedefinitions defined in the sys_bascon.com file. Verify that the configurations areidentical in CPI Node Properties and the sys_bascon.com file.

* IEC 61850 OPC Server has not been correctly configured. Use ManagementTool in CET for IEC 61850 OPC Server to update and reload the configuration.

56



1MRS756119

57

5.3. Testing IED control commands using process display

Start by testing that it is possible to control the Bay L/R symbols using the processdisplay in Monitor Pro. If not:

1. Open Object Navigator and select the appropriate process object related to theBay L/R standard function.

2. Select Object > Standard Function Properties.

3. Verify that the attribute LR_REMOTELY_CONTROLLABLE is set and clickApply.

4. Select the Tools tab to open Process Object Tool and click Create All.

5. Click Close and then OK.

6. Close the Object Navigator.

7. Select Tools > Options.

8. Change the system location to Substation control system and click OK.

You can now test the controllable symbols of the engineered display. Verify thatthey interact with the system correctly.

5.4. Testing IEC 61850 System Supervision Server

When the OPC item Attributes\Device connection status, which indicates the stateof the connection to the IEC 61850 OPC server, has been configured, either of thefollowing occurs:

* IEC 61850 System Supervision Server generates either the log file EventLog.txt,in case of OPC DA Client-related errors, or the log file mms.log, in case of SCLconfiguration or IEC 61850-related errors.

* In case of major errors, IEC 61850 System Supervision Server generatesprintouts to command prompt.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

59

6. Distributed system topologiesThe proposed system topology for the IEC 61850 system is presented in Fig. 4.9.1.-1, including the SYS 600 HSB pair with dedicated OPC DA Client and IEC 61850OPC Server components. Technically, it is also possible for either OPC DA Client,IEC 61850 OPC Server or both to be located on different computers in the sameoffice network.

Fig. 6.-1 describes the system topology where OPC DA Client and IEC 61850 OPCServer are located on the same computer and the SYS 600 base systems on separatecomputers on the LAN network. The communication between the SYS 600 basesystem and OPC DA Client is based on the proprietary ACP protocol over TCP/IP.

5�� +

��+�4��,�� +�4��,�5

5�� +-�5

(�9��+�4��,�� +�4��,��

��

��

��

��

��&��6� ��&��67 888

A060523

Fig. 6.-1 Distributed topology, example 1

It is also possible for OPC DA Client and IEC 61850 OPC Server to be located onseparate computers, as is the case in the system topology presented in Fig. 6.-2.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

��+�4��,�� +�4��,�5

��+�4��,�� +�4��,��

��+�4��,�� +�4��,�:

5�� +

5�� +-�5

(�9

��

��

��

��

��&��6� ��&��67 888

A060524

Fig. 6.-2 Distributed topology, example 2

In this topology, there are more computer-to-computer connections. DCOM-basedcommunication occurs over the network between separate OPC DA Client andIEC 61850 OPC Server computers. This may result in uncontrollability of timeoutsand re-sending of data becoming a problem if the used LAN network is not welldesigned and reliable. However, in a reliable LAN network, the DCOM is as goodas any other protocol.

60



1MRS756119

61

7. IEC 61850 System recommendationsThe recommendations for the IEC 61850 system are presented in Table 7.-1.

Table 7.-1 Recommended limits

SYS 600 PC* Maximum number of IEDs 120* Maximum number of IEC 61850 Clients (OPC Servers) 4* Maximum number of IEC 61850 System Supervision Servers 1a)

IEC 61850 Client (OPC Server)* Maximum number of IEDs 30b)

* Maximum number of ethernet links 1c)

* Maximum number of IEC 61850 subnetworks 1d)e)

IEC 61850 System Supervision Server* Maximum number of OPC Server Connections 1d)

* Maximum number of OPC Client Connections 1* Maximum number of IEC 61850 Client Connections 5* Maximum number of mapped OPC items 200a) IEC 61850 SSS requires MMS port 102 for TCP communication.b) 1 IED = 2 LDs, 20 LNs, 180 CDCs, 820 Attributes, 3 DataSets and 3 RCBs.c) Several IEC 61850 clients can use the same ethernet link.d) True limit.e) Several IEC 61850 clients can use the same subnetwork.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

63

8. TroubleshootingThe following chapter describes what you need to know to effectively troubleshootIEC 61850 systems.

Problem: When I unplug the network cable while using the parametrization or disturbanceupload tool, the situation is not handled properly.

Solution: Ensure that the timeouts for External OPC Data Access Client and IEC 61850OPC Server have been correctly set. Check the timeout settings as described inSection 4.6.5. Timeout handling.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

65

9. Conformance statementsFor further information on IEC 61850 OPC Server and SPA-ZC 40_ conformance,refer to the following manuals:

* IEC 61850 OPC Server: IEC 61850 Master Protocol (OPC)* SPA-ZC 40_: Installation and Commissioning Manual

The logical nodes supported by SA LIB and SCL Importer are listed in Table 9.-1.When a logical node is supported, it is possible to create process objects into theSYS 600 process database either with SCL Importer or by installing SA LIB objectsusing the Installation Tool.

All data attributes within a logical node are not necessarily supported.

Table 9.-1 Logical nodes supported by SA LIB/SCL Importer

LN Description Supported bySA LIB

Supported bySCL Importer

LPHD Physical device information

LLN0 Logical node zero x

PDIF Differential x

PDIR Direction comparison x

PDIS Distance x

PDOP Directional overpower x

PDUP Directional underpower x

PFRC Rate of change of frequency x

PHAR Harmonic restraint x

PHIZ Ground detector x

PIOC Instantaneous overcurrent x

PMRI Motor restart inhibition x

PMSS Motor starting time supervision x

POPF Over power factor x

PPAM Phase angle measuring x

PSCH Protection scheme x

PSDE Sensitive directional earthfault x

PTEF Transient earth fault x

PTOC Time overcurrent x

PTOF Overfrequency x

PTOV Overvoltage x

PTRC Protection trip conditioning x

PTTR Thermal overload x

PTUC Undercurrent x

PTUV Undervoltage x

PUPF Underpower factor x

PTUF Underfrequency x

PVOC Voltage controlled time overcurrent x

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

Table 9.-1 Logical nodes supported by SA LIB/SCL Importer (Continued)



PVPH Volts per Hz x

PZSU Zero speed or underspeed x

RDRE Disturbance recorder function x

RADR Disturbance recorder channel analogue x

RBDR Disturbance recorder channel binary x

RDRS Disturbance record handling x

RBRF Breaker failure x

RDIR Directional element x

RFLO Fault locator x

RPSB Power swing detection/blocking x

RREC Autoreclosing x x

RSYN Synchronism-check or synchronising x x

CALH Alarm handling

CCGR Cooling group control

CILO Interlocking x

CPOW Point-on-wave switching

CSWI Switch controller x

GAPC Generic automatic process control

GGIO Generic process I/O x x

GSAL Generic security application

IARC Archiving

IHMI Human machine interface

ITCI Telecontrol interface

ITMI Telemonitoring interface

ANCR Neutral current regulator

ARCO Reactive power control

ATCC Automatic tap changer controller x

AVCO Voltage control

MDIF Differential measurements

MHAI Harmonics or interharmonics

MHAN Non phase related harmonics orinterharmonics

MMTR Metering x x

MMXN Non phase related Measurement

MMXU Measurement x x

MSQI Sequence and imbalance

MSTA Metering Statistics

SARC Monitoring and diagnostics for arcs

SIMG Insulation medium supervision (gas)

SIML Insulation medium supervision (liquid)

SPDC Monitoring and diagnostics for partialdischarges

XCBR Circuit breaker

66



1MRS756119

67

Table 9.-1 Logical nodes supported by SA LIB/SCL Importer (Continued)



XSWI Circuit switch

TCTR Current transformer

TVTR Voltage transformer

YEFN Earth fault neutralizer (Petersen coil)

YLTC Tap changer

YPSH Power shunt

YPTR Power transformer

ZAXN Auxiliary network

ZBAT Battery

ZBSH Bushing

ZCAB Power cable

ZCAP Capacitor bank

ZCON Converter

ZGEN Generator

ZGIL Gas insulated line

ZLIN Power overhead line

ZMOT Motor

ZREA Reactor

ZRRC Rotating reactive component

ZSAR Surge arrestor

ZTCF Thyristor controlled frequency converter

ZTCR Thyristor controlled reactive component

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

69

10. Terminology

Term Description

IP Address An IP (Internet Protocol) address is a unique identifier for anode or host connection on an IP network. An IP address isrepresented as 4 decimal values separated by decimalpoints. This is known as "dotted decimal" notation.Example: 140.179.220.200 The IP address and the subnetmask determine which part belongs to the network addressand which part belongs to the node address.

Logical Device Representation of a group of functions. Each function isdefined as a logical node. A physical device has one orseveral LDs.

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

71

11. Abbreviations

Abbreviation Description

ACSI Abstract communication service interface

BRCB Buffered Report Control Block

CDC Common data class

CET Communication Engineering Tool

CID Configured IED description

CPI Communication Protocol Interface

DCOM Distributed Common Object Model

DOI Data object instance

FCD Function capability description

HMI Human-machine interface

HSB Hot Stand-by

ICD IED capability description

IEC International Electrotechnical Commission

IED Intelligent electronic device

IP Internet protocol

LAN Local area network

L/R Local/Remote

MMS Manufacturing message specification

OPC OLE (Object linking and embedding) for process control

RCB Report Control Block

SCD System configuration description

SCIL Supervisory Control Implementation Language

SCL Substation configuration description language (defined byIEC 61850)

SNMP Simple Network Management Protocol

SNTP Simple Network Time Protocol

SSS System Supervision Server

MicroSCADA Pro


SYS 600 9.2SYS 600 9.21MRS756119

ABB OySubstation Automation ProductsP.O. Box 699FI-65101 VaasaFINLAND+358 10 2211+358 10 224 1094www.abb.com/substationautomation

1MRS75611

9EN

3/200

7

microscada pro sys 600 9 - abb ltd pro sys 600 9.2 iec 61850 system design configuration manual

Documents