MicroSCADA Pro. IEC System Design. Configuration Manual

Transcription

1 SYS

2

3 1MRS Issued: Version: A/ SYS Contents Copyrights Introduction This manual Use of symbols Intended audience Product documentation Document conventions Document revisions Safety information Backup copies Fault tracing Requirements Hardware requirements Software requirements Configuration Components of the IEC based system SYS 600 base system OPC Data Access Client IEC OPC Server Related engineering tools IEC System Supervision Server IED connectivity Connectivity Packages Configuration environment Configuring the SYS 600 base system Building the physical IEC network Configuring SPA-ZC 40_ Creating a new project Adding a device object Importing the IEC data object model of an IED Downloading configuration and exporting CID file Restarting Configuring report control blocks Configuring IEC OPC Server Creating a new project Defining IEC OPC Server Importing IED configuration

4 SYS MRS Time Synchronization Timeout handling Creating process objects Importing SCL configuration Importing a language translation file Addressing of process objects Configuring OPC Data Access Client Connecting to IEC OPC Server Auto-configuring OPC items for process objects Defining configuration for the IEC Hot Stand-by system Defining the event buffer Configuring an OPC Data Access Client instance IEC Hot Stand-by system topology Starting an OPC Data Access Client instance Stopping an OPC Data Access Client instance Single-line diagram engineering Adding objects into the display Adding Station Local/Remote Switch Editing data variables in the display Configuring IEC System Supervision Server Installing IEC System Supervision Server Starting IEC System Supervision Server Stopping IEC System Supervision Server Configuring IEC System Supervision Server Testing configuration Testing SPA-ZC 40_ and IEC OPC Server configurations Testing OPC Data Access Client start-up Testing IED control commands using process display Testing IEC System Supervision Server Distributed system topologies IEC System recommendations Troubleshooting Conformance statements Terminology Abbreviations

5 1MRS Copyrights SYS The information in this document is subject to change without notice and should not be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any errors that may appear in this document. In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential 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 from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB Oy, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. Copyright 2007 ABB Oy All rights reserved. Trademarks ABB is a registered trademark of ABB Group. All other brand or product names mentioned in this document may be trademarks or registered trademarks of their respective holders. Guarantee Please inquire about the terms of guarantee from your nearest ABB representative. 5

6 6

7 1MRS SYS Introduction 1.1. This manual This manual provides thorough information on the various configuration settings that you have to make in order to take your SYS 600 system into use, focusing on describing how to configure SYS 600 for an IEC system. The manual also describes how to use the configuration tools Use of symbols This publication includes the following icons that point out safety-related conditions or other important information: The caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could result in corruption of software or damage to equipment or property. The information icon alerts the reader to relevant facts and conditions. It should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to information or property loss. Therefore, comply fully with all notices Intended audience This manual is intended for engineers to support configuration and engineering of systems and/or applications. 7

8 SYS MRS Product documentation Name of the document SYS 600 Application Design SYS 600 OPC Data Access Client SYS 600 Process Display Design SYS 600 Picture Editing SYS 600 Status Codes IEC Master Protocol (OPC) SPA-ZC 400, SPA to IEC Gateway, Installation and Commissioning Manual SPA-ZC 402, SPA to IEC Gateway, Installation and Commissioning Manual Document ID 1MRS MRS MRS MRS MRS MRS MRS MRS 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 a dialog, 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 the keyboard. For example, press the CTRL key. Although the Enter and Shift keys are 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 on the keyboard. For example, the space bar, comma key and so on. * Press CTRL+C indicates that you must hold down the CTRL key while pressing the 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 8

9 1MRS SYS Document revisions Version Software revision Date History number A Document created 9

10 10

11 1MRS SYS Safety information This chapter provides information on prevention of hazards Backup copies We suggest that you take backup copies before making any changes, especially ones that 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 backup copies are taken regularly. There should be at least two system backup copies and two application copies. A new backup 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 the application. 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, 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 the application has been configured. It should be taken again when changes are made to the application. This is the case, for example, when pictures or databases are edited or new pictures are added Fault tracing A fatal error is an error that causes a breakdown or a locked situation in the SYS 600 program 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 Control Panel, try to end the task in Windows Task Manager. Shutting down the base system computers by switching off the power might damage the files. 11

12 SYS MRS In Windows, the data kept in the main memory at the moment of a fatal error is placed in the drwtsn32.log file in a system folder, for example WINNT. Analyze and copy the data in this file. 4. Restart the system. 5. Report the program breakdown together with possible the SYS 600 error messages and 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 explanations can be found in the Status Codes manual. 12

13 1MRS SYS Requirements The installation and configuration of the devices that use the IEC protocol consist of: * Hardware installation * Software installation 3.1. Hardware requirements The hardware components listed below are usually required in IEC systems. In addition to the hardware itself, this equipment may require the configuration of the appropriate driver in the appropriate operating system. * Time synchronization device with SNTP Server (for example Meinberg LANTIME/GPS) * RuggedCom RS1600/8000 or RSG 2100, for example. For more information, see * OnTime FST208 Industrial Switch * Allied Telesyn AT-8016F/MT * Intel PRO/1000 MT Dual Port. For more information, see * Printer Server * Media converter Printer Server usually provides diagnostics information in Ethernet via the SNMP protocol. The proposed way to include this information into SYS 600 is to convert it into 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 OPC DA Client Software requirements The following software is required: * SYS 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) 13

14 14

15 1MRS SYS Configuration 4.1. Components of the IEC based system The related components of the IEC based system (see Fig ) are described in the following sections: * SYS 600 base system * OPC Data Access Client * IEC OPC Server * Related engineering tools * IEC System Supervision Server * IED connectivity PC SYS 600 base system Station pictures Process database Process displays Lists ACP (on TCP/IP) OPC DA Client OPC (COM/DCOM on TCP/IP) IEC OPC Server IEC (on TCP/IP) SPA-ZC 40_ IED IEC IED Fig Related components of the IEC based system A

16 SYS MRS SYS 600 base system Station pictures, process displays and lists, providing the operator with information on the SYS 600 base system, are found in process and report databases within the system. In the SYS 600 system, 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/IP link. Thus the underlying IEDs using the IEC protocol are represented as communication stations in the system. Consequently, the related base system objects, that is link, node and station(s), must be 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 the file \sc\sys\active\sys_\sys_bascon.com OPC Data Access Client OPC DA Client is configured by using OPC DA Client Configuration Tool. In this tool, configuration related to IEC OPC Server, SYS 600 base system objects and application engineering is defined. IEC OPC Server * IEC 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 600 base system objects are assigned in CPI Node Properties. Signal engineering * OPC items exposed by IEC OPC Server are mapped to SYS 600 process objects. * Each OPC item is defined to belong to a specific OPC group and communication station representative. Position indications (binary signals) usually belong to an OPC group with an update rate of 0 ms, which is supported by IEC OPC Server. In this case, all signal changes are immediately sent to OPC DA Client. Measurements (analog signals) usually belong to an OPC group with an update rate of 1000 ms. In this case, signal changes shorter than 1000 ms are not sent to OPC DA Client. 16

17 1MRS SYS IEC OPC Server IEC OPC Server is configured by using CET for IEC OPC Server and interacts in real time with IEC process devices and OPC DA Client Related engineering tools When creating process objects into the application, IEC engineering involves using 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 System Supervision Server IEC SSS is a stand-alone executable OPC Client IEC server (opcc_iec61850.exe) with a built-in OPC server for DCOM start-up and diagnostics. IEC SSS enables mapping of SYS 600 OPC Server items to IEC process objects 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, as IEC does no explicit reading. IEC SSS requires an IEC license (SYS or COM). OPC Server-related components are presented in Fig SYS 600 OPC Server (OPC Server) SYS 600 Process Database External OPC DA Client (OPC Client) DCOM IEC System Supervision Server (OPC Client IEC Server) IEC OPC Server (IEC Client OPC Server) IEC E.g. COM 581, SYS 600 (IEC Client) IED (IEC Server) Fig OPC Server-related components A

18 SYS MRS IEC SSS features IEC SSS maps the following OPC items to IEC 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 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 timeout milliseconds. * Creates an OPC group for mapped items with a group update rate of timeout milliseconds. * Sends events received as OPC item updates to IEC clients with reporting service. * If the OPC item update interval exceeds the timeout, the quality (the value of the q-attribute) of the CDC is set to BAD. * Value overrides (GOOD and BAD). The value GOOD overrides all updated values, 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 in terms of service, modeling and engineering interfaces 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 used ACSI models conformance statement Server Logical device Logical node Data Data set Reporting Buffered report control Unbuffered report control 18

19 1MRS SYS 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 SSS start-up When IEC SSS starts up, it will automatically perform the following tasks: 1. Reads the configuration (SCL, Systemc.xml). 2. Builds an IEC 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 server for IEC clients IED connectivity The concept of Connectivity Packages has been introduced together with 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, PCM 600 can be integrated and used together with SYS 600. However, the IED tools included in the LIB packages can also be used 19

20 SYS MRS together with SYS 600 and Monitor Pro process displays. For further information on integrating IED tools, refer to the Application Design manual and Process Display Design manual. The same requirements apply to the connectivity packages in SYS 600 as to the LIB packages. Consequently, IED connectivity in SYS 600 appears in the form of engineering 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. During single-line diagram engineering, the application-related set of process display symbols has been selected to be used in process displays. The process database definitions contain instantiated SA-LIB standard functions and have been created by the following means: * Connectivity Packages * Load files provided by Integrated Engineering Toolbox * Object Navigator approach * List-Based Engineering Tool Connectivity Packages The concept of Connectivity Packages for IEDs provides harmonized engineering and minimizes the dependencies between different releases of IEDs, system products and tools. IED configuration management of parameters, measurements and functions can be realized by importing IED descriptions. This information is included together with the IED when integrating the IED into system products and tools; see Fig Fig IED connectivity A

21 1MRS SYS Achieving full IED connectivity in SYS 600 requires that the application's process database contains the following process object models: * control and supervision * protection functions The process database model of control and supervision consists of position indications, commands and measurements, whereas the process database model of protection functions consists of protection events. Connectivity Packages are used to construct this information in a reliable way into the process database and to achieve effective engineering without additional manual work. Each Connectivity Package includes all the information and functionality required for efficient integration of the IED into system level products and tools. The Connectivity Package description of an IED is according to IEC and contains: * 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 the connectivity package. The supported protocols (this manual focuses on the IEC protocol) and service level of a specific connectivity package is defined separately for each IED. Consequently, in SYS 600, the process database of the IEC system is created using SA-LIB standard functions with default event and alarm handling. This is the case when SCL Importer is used for importing the SCL information either from CID or SCD files into the application. The created process database is connected to the SA-LIB process symbols during display engineering and interacts with the Control dialog boxes of SYS 600 at run-time. To understand the process object model of SA-LIB through the IEC modeling, refer to Chapter 9. Conformance statements for the logical nodes supported by SA-LIB Configuration environment In IEC based systems, the following components need to be configured: * IED (SPA-ZC 40_ if used) * IEC OPC Server * OPC Data Access Client * SYS 600 process database and HMI 21

22 SYS MRS Fig illustrates the software components, including their interrelationships and underlying communication architecture. The SYS 600 base system, OPC DA Client and IEC OPC Server are usually all located on the same computer Configuring the SYS 600 base system Traditionally, configuration related to the SYS 600 base system is defined in the sys_bascon.com file. In IEC based systems, this means that the base system definitions related to the LAN link, the OPC DA Client node and the communication 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 and add 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 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 OPC Server #CREATE NOD:V =LIST(- ; Client node LI = 2,- ;Client Link number SA = 208,- ; Node address NN = "SYS1",- ; Name of the basesystem DT = 10) ; Diagnostic interval #CREATE NOD8:B = %NOD ; Creating node ; End OPC DA Client NOD for IEC OPC Server 5. Scroll down to section Other stations and add the communication station STA ; Otherstations ; NOTE! Use the system configuration tool to create ; stations for the PC-NET! ; Begin OPC DA Client STA for IEC 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 OPC Server Save the sys_bascon.com file. The changes take effect the next time SYS 600 is started. Possible configuration errors will appear in SYS 600 Notification Window. 22

23 1MRS SYS The contents of the sys_bascon.com file is identical for both HSB systems, with the exception of the unique node and station numbers Building the physical IEC network The devices in the IEC network should first become connected in system according to the wiring diagrams and layout pictures. Setting up the devices may require that their addresses and the protocols in question are configured according to the system requirements Configuring SPA-ZC 40_ Before configuring SPA-ZC 40_, ensure that the correct connectivity packages have been installed and taken into use in Connectivity Package Manager 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 Adding a device object A project can contain several IEC device objects. All substation feeder configurations and exported communication, for example, must be done separately for each device. To add an IEC device object to the project, right-click the project and select New > IEC > SPA-ZC 40_; see Fig Fig Adding an IEC device object A040023B 23

24 SYS MRS Ensure that the new IED name is unique within the planned network by renaming the IED, for example REF545_F Importing the IEC data object model of an IED To import the IEC 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 from CAP 505 Application Library to the specified directory. CET for SPA-ZC 40x converts the project files to an IEC data object model using connectivity packages. However, the connectivity packages do not necessarily support all the functions of an IED. Functions not mapped to the IEC structure are reported after import. CET for SPA-ZC 40x imports default data sets and RCBs to the logical device LD0; see Fig A data set includes data attributes selected from an IED's IEC data model. The data sets are used in the IEC event reporting model. If the same data attributes that have been selected to be included in a data set are used in an RCB, the data set generates a spontaneous event which is sent to the IEC client. If the data set is not used in an RCB, the IEC 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 be done in Project Explorer; see Fig

25 1MRS SYS Fig Project Explorer in the Communication Engineering Tool window A040026B Downloading configuration and exporting CID file After you have built the IEC data object model and configured the communication addressing, you can download the configuration to SPA-ZC 40_; see Fig Right-click the IEC device object and select CID Export. 2. If you download configuration to SPA-ZC 40_ for the first time, replace the default IP address with a new address according to the planned network structure. When the new configuration is being downloaded to SPA-ZC 40_, CET checks if the basic IP addresses are changed. If a change is detected, CET asks whether you want 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. 25

26 SYS MRS Fig Downloading device configuration A040029B If the connection to the system, to which SPA-ZC 40_ is connected, is enabled, the Export function tries to determine the SPA-ZC 40_ version and exports the export file accordingly. If a connection to the system cannot be established, prompt the correct version to be exported; see Fig Fig Selecting the correct SPA-ZC 40_ version to be exported A 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 you select 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 client. 26

27 1MRS SYS 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 Click Reset. The results are reported in the UI text box. Do not use the restart function while downloading configuration to SPA-ZC 40_. When the download is complete, SPA-ZC 40_ is automatically restarted. Fig Restarting A Configuring report control blocks 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 attributes' default values are suitable for the following ABB products: * COM 610 * SYS 600 IEC client. RCBs are located under the logical device LD0 and logical node LLN0; see For information on RCB dedication, refer to the IEC Master Protocol (OPC) manual. 27

28 SYS MRS Data Set Get, Set report control attribute values Subscribe for reporting Report Control has association Data Set DO DO DO DO Real Data controls controls DO DO Reports Report Handler* event Event Monitor* DO DO DO Fig * local issue Reporting model A RCBs have the following properties: * Buffered reporting IEC buffers events also during a communication break. * Buffer Time The default value is 100 ms. Consequently, the RCB waits 100 ms for other events 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 a report with all data listed in the linked data set within this period. This feature is not enabled by default, because it causes excessive load to the server and the network. * Report ID SPA-ZC 40_ uses the Report ID as the MMS address of the RCB. Report ID is empty 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 sequence number, and allows segmentation by default. Other fields are RCB configuration version, data reference in the MMS address format, name of the used data set and report sending time. * Max Defines 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-ZC 40_ creates two instances of the RCB name, for example rcbstatnrml01 and rcbstatnrml02. For unbuffered reporting, Max has to be the same or higher as the number of defined clients in accordance with the IEC standard. * Trigger Options 28

29 1MRS SYS Data Change, Data Update and Quality Change triggers are used by default. Consequently, changes in value and quality generate information reports. A period trigger is not used by default. To edit the properties, right-click the dataset and select Properties. Fig Report control block A040134B Buffered reporting requires that clients are defined. Report Client definitions link a certain RCB 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 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 is recommended for clarity. Client IED Name has to match with the client name in SCL. 29

30 SYS MRS Every modification in an RCB increases the RCB configuration revision by one. Each revision generates a CID file, enabling the IEC client to compare the received revision to the file configuration revision Configuring IEC OPC Server IEC OPC Server is configured using CET for IEC OPC Server in SYS 600. With this tool, the hierarchically structured models of a substation or a system are built and loaded into configuration files of IEC OPC Server. To start CET for IEC OPC Server: 1. Open Control System SYS Open IEC OPC Server. 3. Double-click Communication Engineering Tool for IEC OPC Server Creating a new project To create a new project: 1. Start CET for IEC 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 OPC Server Define IEC OPC Server as follows: 1. Right-click the project and select New > Communication > Computer Node to add 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 Right-click the computer node and select New > IEC > IEC OPC Server to add an IEC OPC server. Define Client1 as the Report Control Identity for the IEC OPC server. 5. Right-click IEC OPC Server and select New > IEC > IEC Subnetwork to add an IEC subnetwork to the IEC OPC server. 6. Right-click IEC Subnetwork and select New > IEC Subnetwork > IEC IED to add an IEC IED to the IEC subnetwork. IEC OPC Server and IEC Subnetwork can be renamed if required. 30

31 1MRS SYS Importing IED configuration To import IED configuration: 1. Right-click IEC 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 previously created with CET for SPA-ZC 40x) and click Open. 4. Click Import and close the pane; see Fig Fig SCL Import pane A To allow multiple clients to receive the same data values, multiple instances of the report control classes must be made available. Specify the RCB instances using Report Enabled and Report Client and dedicate them to clients using Report Client. For further information, refer to the IEC Master Protocol (OPC) manual. All configured RCBs without instances specified for IEC OPC Server are discarded. 31

32 SYS MRS To enable IEC OPC Server to use the server-specific RCB instances and thus receive spontaneous events, the Report Control Identity field must match one of the Report Enabled fields in the device's RCB configurations. If the fields do not match, the configured RCB instance is discarded. Update IEC OPC Server as follows (see Fig ): 1. Right-click Computer Node and select Management. 2. Click Update Configuration and then Reload Configuration. 3. Close the Management pane. Fig Management pane A Time Synchronization IEC OPC Server can act as an SNTP client and server for time synchronization. SNTP Client Supports four alternative SNTP servers. For further information, refer to the IEC Master Protocol (OPC) manual. 32

33 1MRS SYS SNTP Server When IEC OPC Server is configured for time synchronization, it updates the operating system time of the workstation. For further information, refer to the IEC Master Protocol (OPC) manual. In order for SNTP Server to work in IEC OPC Server, the Windows time synchronization service (Windows Time) must be disabled since it occupies the SNTP server port of the workstation Timeout handling When parameter setting or disturbance upload operations are performed by using relay tools such as CAP, SMS or LIB, their default timeout of 5 seconds is used. In CET for IEC OPC Server, the default SPA TCP timeout is 3 seconds. To enable fluent interaction in case of possible communication failures during relay tool-specific operations, it is recommended not to change the default SPA TCP timeout. The configuration parameters should be defined according to the following principle: SPA TCP Timeout (3 seconds) < Read/Write timeout of OPC DA Client (4 seconds) < default timeout of relay tools (5 seconds) Creating process objects In the IEC based system, SCL Importer usually creates the application objects 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 contents is further applied to the Object Identification attribute values, which in turn are assigned to the process objects. Before importing the SCL file: * Ensure that the subnetwork matches the definition in CET for IEC OPC Server. * Fill in Substation, Voltage Level and Bay. If the substation is given another name than TEMPLATE in the SCL file, SCL Importer assumes that Substation, Voltage Level, Bay and Subnetwork are already defined in the file. 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 box. The object text for protection process objects, for example, can be translated into a selected language by describing it in the SCL file with a key such as PTOC_NOC3LOW_OP. The translated object text will then be available after 33

34 SYS MRS importing a language file 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. The process objects created with SCL Importer are further adjusted at a later stage via the operations performed with OPC PO List Tool 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 Ensure that the Subnetwork field contains exactly the text IEC61850 Subnetwork, as it appears later in OPC DA Client-related configuration tools. 34

35 1MRS SYS Fig Main view of SCL Importer A Click Preview to open a preview of the objects to be created; see Fig

36 SYS MRS Fig Import Preview A Click Import and close the tool. Some names of process objects created with SCL Importer might be too long (> 10 characters) for Classic Monitor station pictures. In this case, rename the process object using no more than 10 characters 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 the language file (for example C:\Program Files\ABB\Connectivity Packages\REF 541_3_5\2.0\Communication\Language Support\EN\IEC\EN_IEC.txt). 4. Click Open. 5. Click Import and close the tool. 36

37 1MRS SYS Addressing of process objects OPC PO List Tool facilitates the creation of mappings between OPC items and SYS 600 process object addresses. OPC PO List Tool creates an output file in which available process objects are listed and later recognized by OPC DA Client Configuration 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 Fig Main view of OPC PO List A 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 is displayed. Select the Assign new block address and bit number check box and click Save. 37

38 SYS MRS Fig Defining process objects to be saved A Because the process objects do not yet contain the addressing information, the dialog box in Fig is displayed during the save operation. Click OK for All to automatically generate all the block and bit addresses, and close OPC PO List Tool. Fig Invalid process object address A

39 1MRS SYS Configuring OPC Data Access Client OPC DA Client is used for receiving communication from IEC OPC Server. The relationship to IEC OPC Server is defined when configuring OPC DA Client. Each OPC DA Client configuration file usually contains the connection to one IEC OPC server. However, the related configuration to be included into each OPC DA Client may also be a subset of the overall OPC Namespace found in IEC OPC Server. Consequently, OPC DA Client may subscribe to only part of the IEC OPC Server signals representing only part of the system, for example OPC items related to only medium- or high-voltage process devices. One IEC OPC Server can thus serve several OPC DA Client instances at runtime. To start OPC DA Client Configuration Tool: 1. Open Control System SYS Open OPC DA Client and double-click OPC DA Client Configuration Tool Connecting to IEC OPC Server To connect to the OPC Server: 1. Select File > New to open Server Properties. 2. Click Browse to locate IEC OPC Server Data Access V2 in the list of available servers. 3. Click Local Server if OPC DA Client and SYS 600 base system are located in the same computer, as is the case in the typical IEC HSB system, and click OK; see Fig

40 SYS MRS Fig Locating the server A Click Next and fill in CPI Node Properties according to the previously made sys_bascon.com definitions; see Fig In the IEC HSB system, it is sufficient to define only the primary SYS 600 settings. In this case, use the default Base IP Address Fig Defining CPI Node Properties A Click OK to finish. 40

41 1MRS SYS 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 file previously 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 Fig Auto-configuring OPC items A If a warning appears, click Yes to continue the operation; see Fig This is the case when OPC DA Client Configuration Tool cannot validate the created OPC item in IEC OPC Server. Fig Warning of validation failure A All the non-validated OPC items are found in the file with the extension.trc in the folder \sc\sys\active\sys_. When the auto-configuring is complete, the OPC DA Client configuration is displayed as in Fig

42 SYS MRS Fig Main view of OPC DA Client Configuration Tool A One or multiple OPC groups are defined for each communication station representing an IEC process device. For OPC groups containing items related to position indication and control commands, the update rate should be 0 ms. For OPC groups containing measurement values, however, an update rate of for example 1000 ms is accepted. The Update rate setting specifies the interval time for OPC DA Client's polling of OPC items from IEC OPC Server. An update rate of 0 ms means that no events are lost and the functionality is supported by IEC OPC Server Defining configuration for the IEC Hot Stand-by system To define the configuration for IEC 61850HSB System in OPC DA Client Configuration Tool, right-click CPI Node and select IEC in HSB system; see Fig

43 1MRS SYS Fig Turning on IEC in HSB System A Defining the event buffer In IEC HSB systems, define the event buffer as follows: 1. Right-click CPI Node and select Buffering Settings; see Fig Fig Event Buffering settings A Under Buffering Type, click Circular Buffering and set the parameter Keep events (deltat). Keep events (deltat) specifies the maximum amount of time in seconds for the events buffered by OPC DA Client and should be adjusted to the switch-over time. 3. Click OK to close OPC DA Client Tool, and save the configuration file. 43

44 SYS MRS Configuring an OPC Data Access Client instance IEC Hot Stand-by system topology The configuration of the IEC communication system in the SYS 600 HSB environment is presented in Fig In HSB systems that include IEC process devices, OPC DA Client and IEC OPC Server are usually both located in the same computer, together with the SYS 600 base system. COMPUTER A COMPUTER B BASE SYSTEM OPC DA Client IEC OPC Server HSB BASE SYSTEM OPC DA Client IEC OPC Server IEC Device #1 Device #2... Fig A Topology of a typical HSB system with IEC process communication IEC process devices of a physical network are configured to have two masters, one in Computer A and another in Computer B. When a fault occurs in the primary base system (computer A), including the HOT application, the shadowing application in the stand-by base system (computer B) starts and takes over all the operational functions. In HSB systems, there is usually a need to minimize the switch-over time. In Fig , the IEC 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 process devices to always be stored into buffers of both IEC OPC servers. Further, OPC DA Client should be located in the same computer as where the base system is running. When the application state changes to HOT, OPC DA Client should be configured according to the application initialization procedures (APL_INIT_*) as defined in Section Starting an OPC Data Access Client instance. 44

45 1MRS SYS 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, for example PC-NET. Technically, it is also possible to use the watchdog application for the same purpose. However, it should be remembered that the watchdog application should be dedicated to its main task alone, that is the watchdog functionality between HSB partners. At the same time as the SYS 600 system is starting up, the OPC DA Client instance automatically starts, provided that the application objects of the previously mentioned 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 = ops_call( C:\sc\prog\OPC_Client\DA_Client\ daopccl.exe id iec61850 start C:\sc\sys\ active\sys_\iec61850.ini trace normal, 0) Stopping an OPC Data Access Client instance When SYS 600 is shutting down, the corresponding instance of an OPC DA Client should 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 = ops_call( C:\sc\prog\OPC_Client\DA_Client\ Daopccl.exe id iec61850 stop, 0) Single-line diagram engineering Single-line diagram engineering is required to connect the process objects to process displays or station pictures. This is done either by using Display Builder or Picture Editor, depending on whether Classic Monitor or Monitor Pro graphics are used in the system. The overall documentation for Display Builder in Monitor Pro is included in the Process Display Design manual. For Picture Editor in Classic Monitor, refer to the Picture Editing manual. This chapter provides an overall understanding of single-line diagram engineering related to Monitor Pro and some details related to IEC display engineering Adding objects into the display To add objects into the display: 45

46 SYS MRS 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 selected application. 5. Select Bay from the Object Browser list and click Create to add a Station Local/ Remote switch to the display; see Fig Alternatively, drag and drop the item into the display file. Fig Main view of Display Builder. A Proceed in the same way to add position indications for the circuit breaker, disconnectors and the earth-switch. Also add phase current and neutral current measurements. 46

47 1MRS SYS For process symbols representing IEC process devices, the polarity of the position indication is different compared to devices communicating via other protocols, such as LON and SPA. Consequently, value swapping is required for IEC related process symbols during single-line diagram engineering. Further, if an application's single-line diagram contains several IEC process symbols, it is recommended to adjust the default polarity of the position indication in Object Browser accordingly. For further 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 Display Design manual Adding Station Local/Remote Switch The Station Local/Remote switch is used by the process display at run-time. To add a 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

48 SYS MRS Fig Installing station standard function A 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 been created into the application. 8. Close Object Navigator. 9. Start Display Builder again and drag and drop the IEC item from Object Browser to add a Station Local/Remote switch to the display 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 state indication for the IEC bay-related data variable from None to Swap values 0 and 1 and click Apply; see Fig

49 1MRS SYS Fig Defining data variables A Change the value swapping for the data variables related to circuit-breaker position from Swap values 0 and 1 to None and click Apply. Make the same change to the data variables related to the disconnector and earthswitch. When creating process displays that contain mainly symbols connected to IEC signals, it is recommended to change the default value of state indication value swapping, as values are swapped by default. When swapping is selected, the state indication value 1 coming from process objects is changed to 2 and the value 2 to 1. To take swapping out of use, change UsesReversedSingleIndications in objnav.ini to Save the display file by selecting File > Save As and close Display Builder. 49

50 SYS MRS Configuring IEC System Supervision Server Installing IEC System Supervision Server To install IEC SSS: 1. Start command prompt in the folder sc\prog\iec61850systemsupervisionserver \bin. 2. Create an instance for DCOM registration by executing "makeinst OPCC_IEC " in cmd prompt. This creates a new folder, OPCC_IEC61850_1, with a unique CLSID for IEC SSS. 3. Register IEC SSS to be started by DCOM, either by executing opcc_iec61850.exe /regserver to run IEC SSS as a logged user, or by executing opcc_iec61850.exe /regserver /user [username] /pwd [password] to run IEC 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 folder C:\sc\prog\IEC61850SystemSupervisionServer\bin\ Starting IEC System Supervision Server Configure OPC DA Client for IEC SSS OPC Server using OPC DA Client Configuration Tool; see Fig (for configuring OPC Data Access Client, also refer to Section 4.8. Configuring OPC Data Access Client). SSS is registered with Prog ID: ABB.IEC61850_Slave_OPC_DA_Server.Instance[1].1. Fig Configuring OPC DA Client for IEC SSS OPC Server A Continue by configuring the OPC DA Client instance to start automatically when the SYS 600 system is starting up. The same configuration principles can be followed as in Section Starting an OPC Data Access Client instance. 50

51 1MRS SYS Stopping IEC System Supervision Server Stop IEC 61850SSS by shutting down the SYS 600 OPC DA Client instance configured for SSS. IEC SSS will shut down (provided that it was started through DCOM) when all OPC clients have been disconnected. The same configuration principles can be followed as in Section Stopping an OPC Data Access Client instance Configuring IEC System Supervision Server IEC SSS is configured using SCL in the file Systemc.xml, which is to be located in sc\prog\iec61850systemsupervisionserver\bin\opcc_iec61850_1. At least the bolded parts are to be configured, and the underlined parts are to remain constant. 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 ( 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 > <P type="progid">abb.microscada.opc.server.da</p> <P type="osi-ap-qualifier">23</p> <P type="ip"> </p> <P type="osi-ssel">0001</p> <P type="osi-psel">0001</p> <P type="osi-tsel"> </p> <P type="osi-ae-title">1,3,9999,23</p> </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"/> 51

52 SYS MRS <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 OPC Server, and the quality and timestamp are set according to the quality and timestamp of the received OPC item. In case of timer expire or IEC OPC Server disconnect, the CDC value is set to 0 and the quality to BAD. The values can be overridden by good or bad values. Good values are always used when updates are received from IEC OPC Server, and bad values if the timer expires or IEC OPC Server disconnects. * Mapped indication values If configured as indication (UPDATE), the values are received from IEC OPC Server, and the quality and timestamp are set according to the quality and timestamp of the received OPC item. The indication value can be overridden by configuring a good value (GOOD=?). This value is used for all updated values, 52

53 1MRS SYS that is, every updated value from IEC OPC Server is overridden. In case of IEC OPC Server disconnect, the CDC quality is set to BAD (if bad value (BAD=?) is configured, the value will be overridden). <! MAPPED > <! These are examples of how to configure mapped attributes from IEC OPC Server to IEC SSS. > <! For IEC Clients to receive events, the mapped DOI must also be configured to a reporting dataset. > <! Configuration parameters (saddr): mapping,updaterate,type{,timeout} [,BAD=badvalue][,GOOD=goodvalue] > <! where: > <! mapping = IEC 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 timed events > <! timeout = Timer timeout (only valid for TIMER, remove if using UPDATE) (milliseconds) > <! badvalue = Bad value to be updated (overrides a value when disconnected or timer expires) > <! goodvalue = Good value to be updated (overrides a value from IEC OPC Server) > <! 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 is updated with bad value if configured) > <! - if an update is received, the value is updated (overridden by good value if configured) > <! The PhyHealth item executes the SCIL program for SCADA every msec and expects an update > <! - if an update is received within 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 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 timed events > <! badvalue = Bad value to be updated (overrides a value when disconnected or timer expires). > <! goodvalue = Good value to be updated (overrides a value from IEC OPC Server). > <! NOTE! Use numeric values for bad and good values. > 53

54 SYS MRS <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"> Event Enabled > </DAI> </DOI> <! System <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

55 1MRS SYS Testing configuration 5.1. Testing SPA-ZC 40_ and IEC OPC Server configurations Use the Online diagnostics window in CET for IEC OPC Server to test that the individual IEC process device signals are updated accordingly. For example, test that the circuit-breaker position indication is correctly updated in the system: 1. Open SPA-ZC 40_ in the project structure. 2. Open the logical device LD1 and select the logical node CBCSWI Right-click OPC Pos and select Online diagnostics; see Fig Fig Opening the Online diagnostics window A When the process device signal is changed for the circuit-breaker position indication by using a simulator, stval is to be changed according to the position of the signal as in Table

56 SYS MRS Table StVal settings Circuit breaker stval 00 Undefined 0 10 Open 1 01 Closed 2 11 Undefined Testing OPC Data Access Client start-up To test the OPC DA Client start-up: 1. Open Control System SYS Open OPC DA Client and OPC DA Client Control Panel. 3. Click New Instance and then Browse to specify the location of the OPC DA Client 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 selected configuration. When an instance is successfully started, it is found in List of OPC DA Client Instances; see Fig Fig Starting up an OPC Data Access Client instance A However, if an instance is not successfully started, the reason may be one of the following: * CPI Node Properties of OPC DA Client Configuration does not match with the definitions defined in the sys_bascon.com file. Verify that the configurations are identical in CPI Node Properties and the sys_bascon.com file. * IEC OPC Server has not been correctly configured. Use Management Tool in CET for IEC OPC Server to update and reload the configuration. 56