Professional Documents
Culture Documents
3
IEC 61850 System Design
1MRS756664
MicroSCADA Pro
Issued: 31.3.2010
Version: A/31.3.2010
Contents:
1.
2.
Copyrights ............................................................................................... 5
Introduction ............................................................................................. 6
2.1.
2.2.
2.3.
2.4.
2.5.
2.6.
3.
4.
Requirements ........................................................................................ 11
4.1.
4.2.
5.
Configuration ........................................................................................ 12
5.1.
5.2.
5.3.
5.4.
5.5.
5.6.
5.7.
MicroSCADA Pro
1MRS756664
5.8.
5.9.
5.10.
5.11.
5.12.
5.13.
6.
7.
8.
9.
10.
11.
12.
5.7.4.
Time Synchronization .................................................... 32
5.7.5.
Timeout handling ........................................................... 35
Creating process objects ............................................................. 35
5.8.1.
Importing SCL configuration ......................................... 36
5.8.2.
Importing a language translation file ............................. 39
5.8.3.
Addressing process objects .......................................... 39
Configuring OPC Data Access Client .......................................... 41
5.9.1.
Starting OPC DA Client Configuration Tool ................... 41
5.9.2.
Connecting to IEC 61850 OPC Server ......................... 42
5.9.3.
Auto-configuring OPC items for process objects .......... 43
5.9.4.
Defining configuration for the IEC 61850 system .......... 45
5.9.5.
Defining the event buffer ............................................... 46
Configuring an OPC Data Access Client instance ....................... 47
5.10.1. IEC 61850 Hot Stand-by system topology .................... 47
5.10.2. Starting OPC Data Access Client instance ................... 47
5.10.3. Stopping an OPC Data Access Client instance ............ 48
Single-line diagram engineering .................................................. 48
5.11.1. Adding objects into the display ..................................... 48
5.11.2. Adding Station Local/Remote Switch ............................ 50
5.11.3. Editing data variables in the display .............................. 51
Configuring IEC 61850 System Supervision Server .................... 53
5.12.1. Installing IEC 61850 System Supervision Server ......... 53
5.12.2. Starting IEC 61850 System Supervision Server ........... 53
5.12.3. Stopping IEC 61850 System Supervision Server ......... 53
5.12.4. Configuring IEC 61850 System Supervision Server ..... 54
Configuring IEC 61850 Redundancy diagnostics ........................ 56
5.13.1. Local machine DuoDriver status diagnostics ................ 56
5.13.2. IED DuoDriver status diagnostics ................................. 57
1MRS756664
MicroSCADA Pro
1.
Copyrights
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 2010 ABB. 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.
1MRS756664
MicroSCADA Pro
IEC 61850 System Design
2.
Introduction
2.1.
This manual
This manual provides thorough information on the MicroSCADA Pro software and
hardware installation: base systems, LAN connections, process communication systems,
workplaces and peripherals.
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 61850 system. The manual also describes how to
use the configuration tools.
2.2.
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.
2.3.
Intended audience
This manual is intended for engineers to support configuration and engineering of systems
and/or applications.
2.4.
Product documentation
Name of the document
Document ID
1MRS756669
1MRS756646
1MRS756637
1MRS756647
1MRS756664
MicroSCADA Pro
Document ID
1MRS756636
1MRS756643
1MRS756663
1MRS756632
1MRS756638
1MRS756662
1MRS755359
1MRS755360
1MRS750104-MUM
SPA-ZC 400, SPA to IEC 61850 Gateway, Installation and Commissioning Manual
1MRS755347
SPA-ZC 402, SPA to IEC 61850 Gateway, Installation and Commissioning Manual
1MRS755380
2.5.
Citrix documentation
LONWORKS PCLTA-20 PCI LonTalk Adapter, User's Guide
Microsoft Windows documentation
PC/TCP documentation
Product documentation of the used multiport serial card
Product documentation of the used network adapter card
Product documentation of the used PCLTA-10 card
RTU documentation
Document conventions
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 file names.
Capital letters are used for the name of a keyboard key if it is labeled on the keyboard.
For example, press the CTRL key. Although the Enter and Shift keys are not 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).
1MRS756664
MicroSCADA Pro
IEC 61850 System Design
2.6.
The names of push and toggle buttons are boldfaced. For example, click OK.
The names of menus and menu items are boldfaced. For example, the File menu.
The following convention is used for menu operations: Menu Name > Menu Item
> Cascaded Menu Item. For example: select File > Open > New Project.
The Start menu name always refers to the Start menu on the Windows Task Bar.
System prompts/messages and user responses/input are shown in the Courier font.
For example, if you enter a value out of range, the following message is displayed:
Entered value is not valid.
You may be told to enter the string MIF349 in a field. The string is shown as follows
in the procedure: MIF349
Variables are shown using lowercase letters: sequence name
Document revisions
Version
Software revision
number
Date
9.3
31.3.2010
History
New document
1MRS756664
MicroSCADA Pro
3.
Safety information
This chapter provides information on prevention of hazards.
3.1.
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.
3.2.
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.
MicroSCADA Pro
1MRS756664
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.
3. 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 SYS 600 Status Codes.
10
1MRS756664
MicroSCADA Pro
4.
Requirements
The installation and configuration of the devices that use the IEC 61850-8-1 protocol
consist of:
4.1.
Hardware installation
Software installation
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 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
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 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.
4.2.
Software requirements
The following software is required:
IED configuration tools (for example Communication Engineering Tool for SPAZC 40x version 2.0 or later)
PCM600
Connectivity Packages for IEDs (for example REF 541/543/545 Connectivity
Package version 2.0 or later)
11
MicroSCADA Pro
1MRS756664
5.
Configuration
5.1.
A060436
5.1.1.
12
1MRS756664
MicroSCADA Pro
Consequently, the related base system objects, that is link, node and station(s), must be
introduced through system configuration:
These definitions are usually included in the system configuration and found in the file
\sc\sys\active\sys_\sys_bascon.com.
5.1.2.
IEC 61850 OPC Server CLSID and its location (Local or Remote Server) are assigned
in Server Properties.
Signal engineering
5.1.3.
OPC items exposed by IEC 61850 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 61850 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.
13
MicroSCADA Pro
1MRS756664
5.1.4.
5.1.5.
A060813
14
1MRS756664
MicroSCADA Pro
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 61850 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.
5.1.6.
IED connectivity
The concept of Connectivity Packages has been introduced together with MicroSCADA
Pro SYS 600 and will gradually replace the role of the LIB packages in IED engineering.
Unlike the LIB packages, the connectivity packages do not include IED tools. Instead,
PCM600 can be integrated and used together with SYS 600. However, the IED tools
included in the LIB packages can also be used together with SYS 600 and Monitor Pro
process displays. For further information on integrating IED tools, see SYS 600
Application Design and SYS 600 Process Display Design.
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 singleline diagram engineering, the application-related set of process display symbols has been
selected to be used in process displays.
15
MicroSCADA Pro
1MRS756664
The process database definitions contain instantiated SA-LIB standard functions and
have been created by the following means:
5.1.6.1.
Connectivity Packages
Load files provided by Integrated Engineering Toolbox
Object Navigator approach
List-Based Engineering Tool
SCL Importer
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 Figure5.1.6.1-1.
A060648
Figure5.1.6.1-1IED connectivity
Achieving full IED connectivity in SYS 600 requires that the application's process
database contains the following process object models:
16
1MRS756664
MicroSCADA Pro
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 61850 and contains:
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 61850 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 61850 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 dialogs of SYS 600
at run-time. For more information on SCL Importer, see 5.8,Creating process objects
and SYS 600 Application Design.
To understand the process object model of SA-LIB through the IEC 61850 modeling,
see 10,Conformance statements for the logical nodes supported by SA-LIB.
5.2.
Configuration environment
In IEC 61850-based systems, the following components need to be configured:
17
MicroSCADA Pro
1MRS756664
5.3.
a070121.png
5.
6.
18
1MRS756664
MicroSCADA Pro
Traditionally, the configuration related to the SYS 600 base system is defined in the
sys_bascon.com file. In IEC 61850-based systems, this means that the base system
definitions related to the LAN link, the External OPC DA Client node and the communication station(s) are configured for both SYS 600 redundancy systems. The following
steps guide you through the base system configuration using the included configuration
tools.
To configure the system using System Configuration Wizard:
1. Open SYS 600 Control Panel.
2. In the SYS 600 Control Panel dialog, click Admin and then Wizard.
3. The System Configuration dialog appears. Follow the wizard and make the necessary
configurations.
4.
The Base System Node Number and Station Address are used
when configuring CPI Node Properties for the OPC Data
Access Client.
19
MicroSCADA Pro
1MRS756664
3.
4.
5.
6.
20
1MRS756664
MicroSCADA Pro
7.
8.
5.4.
21
MicroSCADA Pro
1MRS756664
DuoDriver (v2.2 or later) with PRP and compatible network interface cards (NIC) are
used for IEC 61850 communication redundancy. Using DuoDriver and PRP with SYS
600 requires that the connected IEDs also support DuoDriver for communication
redundancy.
Installing DuoDriver
To install and configure DuoDriver:
1. Install and configure the NICs used for redundant IEC 61850 communication before
installing the DuoDriver. The NICs to-be-paired must be named appropriately.
2. Set the static IP address.
For Windows XP SP2 (and earlier), set a static IP address for NIC A manually,
and disable TCP/IP protocol for NIC B.
For Windows Vista, Server 2008 and XP SP3, configure a static IP address for
both NICs (IP of NIC B not used). Disable IPv6. The IP address of NIC A is
used for both paired NICs.
The configuration of DuoDriver requires that all redundant NICs are plugged into an active switch/router during
the installation.
3.
4.
5.5.
Install DuoDriver by executing the DuoDriver install package included in SYS 600
installation (e.g. C:\sc\Setup\DuoDriver\setup.exe).
DuoDriver is configured during the installation. To change the configuration, the
driver must be reinstalled. The DuoDriver setup names the paired instance of
DuoDriver, pairs the NICs, and clones the MAC address of the paired NICs. The
configured instance name and NIC name are used in the IEC 61850 OPC Server
namespace to identify the DuoDriver diagnostics.
After installation disable DuoDriver for other Ethernet interfaces.
5.6.
22
1MRS756664
MicroSCADA Pro
5.6.1.
5.6.2.
A040023B
Ensure that the new IED name is unique within the planned network by renaming the
IED, for example REF545_F1.
5.6.3.
The file, which is a compressed archive file with the file extension .AR, is imported from
CAP 505 Application Library to the specified directory.
23
MicroSCADA Pro
1MRS756664
CET for SPA-ZC 40x converts the project files to an IEC 61850 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 61850 structure are reported
after import.
CET for SPA-ZC 40x imports default data sets and RCBs to the logical device LD0; see
Figure5.6.3-1. A data set includes data attributes selected from an IED's IEC 61850 data
model. The data sets are used in the IEC 61850 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 61850 client. If the data
set is not used in an RCB, the IEC 61850 client reads the data separately.
After adding a new IED, give it a unique name in the network.
Spaces are not allowed in the IED's name. Renaming can be
done in Project Explorer; see Figure5.6.3-1.
A040026B
24
1MRS756664
MicroSCADA Pro
5.6.4.
Right-click the IEC 61850 device object and select CID Export.
If you download configuration to SPA-ZC40_ for the first time, replace the default
IP address 192.168.2.10 with a new address according to the planned network
structure.
When the new configuration is being downloaded to SPA-ZC40_, 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-ZC40_ uses the
old IP addresses from the previous configuration.
A040029B
25
MicroSCADA Pro
1MRS756664
A060129
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 61850 client.
5.6.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.
A060396
Figure5.6.5-1Restarting
2.
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, SPAZC 40_ is automatically restarted.
5.6.6.
26
1MRS756664
MicroSCADA Pro
COM600
SYS 600 IEC 61850 client.
RCBs are located under the logical device LD0 and logical node LLN0; see Figure5.6.61. For information on RCB dedication, see SYS 600 IEC 61850 Master Protocol (OPC).
A060032
Figure5.6.6-1Reporting model
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 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 61850 standard.
Trigger Options
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.
27
MicroSCADA Pro
1MRS756664
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.
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 the received
revision to the file configuration revision.
5.7.
28
1MRS756664
MicroSCADA Pro
2.
3.
5.7.1.
5.7.2.
5.7.3.
29
MicroSCADA Pro
1MRS756664
a070122
30
1MRS756664
MicroSCADA Pro
To allow multiple IEC 61850 clients to receive the same data values from the IED,
multiple instances of the report control classes must be made available. Specify the RCB
instances using Report Enabled and Report Client and dedicate them to clients using
Report Client.
To enable IEC 61850 OPC Server to use the server-specific RCB instances and thus
receive spontaneous events, the Report Control Identity object property of the OPC
Server must match one of the Report Client fields in the device's RCB configurations.
All configured RCBs without a Report Enabled field are used with as is RCB naming.
The RCBs without instances specified for the IEC 61850 OPC Server are discarded. For
more information, see IEC 61850 Master Protocol (OPC) manual.
a070100.png
31
MicroSCADA Pro
1MRS756664
a070101.png
Figure5.7.3-3Management pane
5.7.4.
Time Synchronization
IEC 61850 OPC Server can act as an SNTP client and server for time synchronization.
For more information, see IEC 61850 Master Protocol (OPC) manual.
SNTP Client
When the IEC 61850 OPC Server is configured as a time synchronization client, it updates
the operating system time of the workstation. SNTP Client supports maximum 4 alternative SNTP servers.
When using the SNTP Client, also disable Windows Date and Time Properties automatic
time synchronization.
32
1MRS756664
MicroSCADA Pro
a070102.png
SNTP Server
When the IEC 61850 OPC Server is configured as a time synchronization server, it
responds to synchronization requests of the SNTP clients with the operating system time
of the workstation.
In order for SNTP Server to work in the IEC 61850 OPC
Server, the Windows time synchronization service (Windows
Time) must be disabled since it occupies the SNTP server port
of the workstation.
33
MicroSCADA Pro
1MRS756664
a070103.png
To set the daylight saving time, enable Windows Date and Time Properties to automatically adjust the time for daylight saving changes.
a070104.png
34
1MRS756664
MicroSCADA Pro
5.7.5.
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 61850 OPC Server, the default SPA TCP timeout is 3 seconds.
To enable fluent interaction in case of possible communication failures during relay toolspecific 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).
5.8.
The object text for protection process objects can be, for example, translated into a
selected language by describing it in the SCL file with a key, such as
PTOC_NOC3LOW_OP. The translated object text is available after importing a 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.
35
MicroSCADA Pro
1MRS756664
5.8.1.
a070105.png
3.
4.
36
To define the Active File, click '...' to locate the SCL file (.CID).
Click Open and fill in the Object Identification information as in Figure5.8.1-2.
1MRS756664
MicroSCADA Pro
a070106.png
5.
37
MicroSCADA Pro
1MRS756664
a070107.png
Figure5.8.1-3Import Preview
6.
Click Import and select the unit number for the IED.
a070108.png
7.
38
Click OK and configure the External OPC DA Client. Select the IEC 61850 OPC
Server instance in which the IED is configured. Configure the External OPC DA
Client configuration file name and the CPI node number.
1MRS756664
MicroSCADA Pro
a070109.png
8.
5.8.2.
Click OK. The process objects for the IED are created and the External OPC DA
Client configuration is generated.
5.8.3.
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 select the station number selected in the base system
configuration.
39
MicroSCADA Pro
1MRS756664
a070110.png
3.
4.
a070111.png
5.
6.
40
Select Assign new block address and bit number and click Save. The start range
for the block is from 1 to 4094, depending on the number of the process objects on
the list. If the start range is more than 4095, a notification message is displayed. The
default start range is 1.
If you did not select Assign new block address and bit number above, the process
objects do not contain the addressing information, and the dialog in Figure5.8.3-3
is displayed when you click Save. Click OK for All to automatically generate all
the block and bit addresses, and close OPC PO List Tool. The start range for the
block is from 1 to 4094, depending on the number of the process objects on the list.
If the start range is more than 4095, a notification message is displayed. The default
start range is 1.
1MRS756664
MicroSCADA Pro
a070112.png
5.9.
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 DA Client.
Each OPC DA Client configuration file usually contains the connection to one IEC 61850
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 61850 OPC Server.
Consequently, OPC DA Client may subscribe to only part of the IEC 61850 OPC Server
signals representing only part of the system, for example OPC items related to only
medium- or high-voltage process devices. One IEC 61850 OPC Server can thus serve
several OPC DA Client instances at runtime.
5.9.1.
41
MicroSCADA Pro
1MRS756664
5.9.2.
A060446
4.
42
Click Next and fill in CPI Node Properties according to the previously made
sys_bascon.com definitions, see Figure5.9.2-2.
In the IEC 61850 HSB system, it is sufficient to define only the primary SYS 600
settings. In this case, use the default Base IP Address 127.0.0.1.
1MRS756664
MicroSCADA Pro
a070113.png
5.
5.9.3.
Click OK to finish.
43
MicroSCADA Pro
1MRS756664
AutoConfigure1a
4.
A060449
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 Figure5.9.3-3.
44
1MRS756664
MicroSCADA Pro
A060450
One or multiple OPC groups are defined for each communication station representing
an IEC 61850 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 61850 OPC Server. An update rate of 0 ms means that no events are lost
and the functionality is supported by IEC 61850 OPC Server.
5.9.4.
45
MicroSCADA Pro
1MRS756664
a070114.png
5.9.5.
A060453
2.
3.
46
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.
Click OK to close OPC DA Client Tool, and save the configuration file.
1MRS756664
MicroSCADA Pro
5.10.
5.10.1.
A060454
IEC 61850 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 Figure5.10.1-1, the IEC 61850 OPC Servers and External OPC DA Clients are active
both in the primary (including HOT application) and the stand-by (including the shadowing application) computer. This way the latest data from IEC 61850 process devices is
always available on the IEC 61850 OPC Servers. The changes are stored into the buffers
of both External OPC DA Clients to prevent event loss during switchover. When the
main application is COLD the shadowing state of the application is HOT_RC, the buffering of the data updates is made in SYS 600.
The External OPC DA Client should be located on the same computer as where the base
system is running. The External OPC DA Client should be configured according to the
application initialization procedures (APL_INIT_*), as defined in 5.10.2,Starting OPC
Data Access Client instance.
5.10.2.
47
MicroSCADA Pro
1MRS756664
triggered from the applications event channel APL_INIT_1. The External OPC DA
Client instance starts automatically when the SYS 600 system is starting up.
APL_INIT_1:C
; Start External 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_\OPCDAC.ini -trace off, 0 )
5.10.3.
2.
5.11.
5.11.1.
48
1MRS756664
MicroSCADA Pro
2.
3.
4.
5.
A060455
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.
For process symbols representing IEC 61850 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 61850-related process symbols during
single-line diagram engineering. Further, if an application's single-line diagram contains several IEC 61850
49
MicroSCADA Pro
1MRS756664
Select File > Save As to save the display, and close Display Builder.
For more information on process display engineering, see SYS 600 Process Display
Design.
5.11.2.
50
Open Object Navigator from Monitor Pro by selecting Tools > System Tools >
Tool Manager. Object Navigator is located on the Application Objects tab.
Select Object > Install Standard Function to open Standard Function Tool.
Select Station and click Install; see Figure5.11.2-1
1MRS756664
MicroSCADA Pro
A060456
4.
5.
6.
7.
8.
9.
5.11.3.
51
MicroSCADA Pro
1MRS756664
A060457
3.
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 61850-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 0.
4.
52
Save the display file by selecting File > Save As and close Display Builder.
1MRS756664
MicroSCADA Pro
5.12.
5.12.1.
5.12.2.
A070090
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
5.10.2,Starting OPC Data Access Client instance.
5.12.3.
53
MicroSCADA Pro
1MRS756664
5.12.4.
Timer
If configured as Timer, the values are received from the OPC Server, and the quality
and timestamp are set according to the quality and timestamp of the received OPC item.
If the timer expires or the OPC Server disconnects, the CDC value is set to 0 and the
quality to BAD. The values can be overridden by good (Good Value) or bad (Bad Values)
values. Good values are always used when updates are received from the OPC Server.
Bad values are used if the timer expires or the OPC Server disconnects.
A Timer object creates an OPC group for mapped items with group update rate = Update
Rate. It expects an update of the specified item within Time Out msec. 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).
Update
If configured as Update, the values are received from the 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. This value is used
for all updated values, that is, every updated value from OPC Server is overridden. If
the OPC Server is disconnected, the CDC quality is set to BAD (if Bad Value is configured, the value is overridden).
The following example shows how to configure status information of the local DuoDriver
to be reported by the IEC 61850 System Supervision Server. By default the SSS is configured to connect to the MicroSCADA OPC Server (ABB.MicroSCADA.OPC.Server.DA).
1.
2.
3.
4.
54
Start CET for IEC 61850 OPC Server and open the project created for SYS 600.
Right-click the computer node and select New > SSS > SSS Server to add a System
Supervision Server. Only one SSS Server is supported.
Right-click the SSS Server and select New > SSS > SSS Subnetwork to add a
System Supervision Server Subnetwork. Only one SSS Subnetwork is supported.
Right-click the SSS Subnetwork and select New > SSS > SSS IED Template to
add a System Supervision Server IED. Rename the SSS IED with a max 8 letter
length name (e.g. Micro) without white space. Only one SSS IED is supported.
1MRS756664
MicroSCADA Pro
5.
Right-click the SSS IED.SCADA.LLN0 and select New > Data objects > RSS to
add a redundancy supervision status object. Rename as SrcSt. Select SrcSt Basic
type Update and configure DuoDriver diagnostic item paths to OPC Item ID paths
for stValA and stValB.
6.
To enable spontaneous updates for the status items, the added data object needs to
be included in the dataset. Open the dataset editor for dsSCADA by right-clicking
the dataset and selecting Dataset Editor. Drag-and-drop the SrcSt to the Dataset
Editor pane to include it in the dataset. Click Apply. The dataset cannot be empty
when starting SSS.
55
MicroSCADA Pro
1MRS756664
7.
Use the Management tool from the Computer Node to register and configure the
SSS.
5.13.
5.13.1.
56
1MRS756664
MicroSCADA Pro
and NIC names, and creates the required process objects to the database. The created
process objects need to be configured for the DuoDriver station.
a070118.png
The local DuoDriver status information has a symbol for Monitor Pro for on-screen
monitoring. The symbol can be added through Display Builders Object Browser.
a070119.png
5.13.2.
57
MicroSCADA Pro
1MRS756664
MicroSCADA SCL Import Tool configures the External OPC DA Client and adds
MicroSCADA process objects for the IED DuoDriver status diagnostics automatically.
The import tool checks if the SrcSt data object is found in the IED configuration and
creates the required process objects and mapping for the External DA Client configuration.
The local DuoDriver status information has a symbol for Monitor Pro for on-screen
monitoring. The symbol can be added through Display Builders Object Browser.
a070120.png
58
1MRS756664
MicroSCADA Pro
6.
Testing configuration
6.1.
A060458
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
Table6.1-1.
Table 6.1-1 StVal settings
Circuit breaker
00 Undefined
stVal
0
59
1MRS756664
MicroSCADA Pro
IEC 61850 System Design
Circuit breaker
6.2.
stVal
10 Open
01 Closed
11 Undefined
A060459
However, if an instance is not successfully started, the reason may be one of the following:
60
1MRS756664
MicroSCADA Pro
6.3.
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 61850 OPC Server has not been correctly configured. Use Management Tool
in CET for IEC 61850 OPC Server to update and reload the configuration.
Open Object Navigator and select the appropriate process object related to the Bay
L/R standard function.
Select Object > Standard Function Properties.
Verify that the attribute LR_REMOTELY_CONTROLLABLE is set and click
Apply.
Select the Tools tab to open Process Object Tool and click Create All.
Click Close and then OK.
Close the Object Navigator.
Select Tools > Options.
Change the system location to Substation control system and click OK.
You can now test the controllable symbols of the engineered display. Verify that they
interact with the system correctly.
6.4.
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 SCL configuration or IEC 61850-related errors.
In case of major errors, IEC 61850 System Supervision Server generates printouts
to command prompt.
61
MicroSCADA Pro
1MRS756664
7.
A060523
It is also possible for OPC DA Client and .png OPC Server to be located on separate
computers, as is the case in the system topology presented in Figure7-2.
62
1MRS756664
MicroSCADA Pro
A060524
63
1MRS756664
MicroSCADA Pro
IEC 61850 System Design
8.
Number Comment
160
40
16
64
200
1MRS756664
MicroSCADA Pro
9.
Troubleshooting
The following chapter describes what you need to know to effectively troubleshoot IEC
61850 systems.
Problem
Solution
When I unplug the network cable while using Ensure that the timeouts for External OPC Data
the parametrization or disturbance upload tool, Access Client and the IEC 61850 OPC Server
the situation is not handled properly.
have been correctly set. Check the timeout
settings as described in 5.7.5, Timeout handling.
When the SNMP OPC Server is connected to
MicroSCADA Pro, the related process objects
appear as not sampled, i.e. process object
statuses and values are not reflecting the
appropriate OPC items from the SNMP OPC
Server.
65
1MRS756664
MicroSCADA Pro
IEC 61850 System Design
10.
Conformance statements
For further information on IEC 61850 OPC Server and SPA-ZC 40_ conformance, see
the following manuals:
The logical nodes supported by SA LIB and SCL Importer are listed in Table10-1. When
a logical node is supported, it is possible to create process objects into the SYS 600
process database either with SCL Importer or by installing SA LIB objects using the
Installation Tool.
All data attributes within a logical node are not necessarily
supported.
Table 10-1 Logical nodes supported by SA LIB/SCL Importer
LN
66
Description
Supported by SA
LIB
Supported by
SCL Importer
LPHD
LLN0
PDIF
Differential
PDIR
Direction comparison
PDIS
Distance
PDOP
Directional overpower
PDUP
Directional underpower
PFRC
PHAR
Harmonic restraint
PHIZ
Ground detector
PIOC
Instantaneous overcurrent
PMRI
PMSS
POPF
PPAM
PSCH
Protection scheme
PSDE
PTEF
PTOC
Time overcurrent
PTOF
Overfrequency
1MRS756664
MicroSCADA Pro
LN
Description
Supported by SA
LIB
Supported by
SCL Importer
PTOV
Overvoltage
PTRC
PTTR
Thermal overload
PTUC
Undercurrent
PTUV
Undervoltage
PUPF
Underpower factor
PTUF
Underfrequency
PVOC
PVPH
Volts per Hz
PZSU
RDRE
RADR
RBDR
RDRS
RBRF
Breaker failure
RDIR
Directional element
RFLO
Fault locator
RPSB
RREC
Autoreclosing
RSYN
Synchronism-check or synchronizing
CALH
Alarm handling
CCGR
CILO
Interlocking
CPOW
Point-on-wave switching
CSWI
Switch controller
GAPC
GGIO
GSAL
IARC
Archiving
IHMI
ITCI
Telecontrol interface
ITMI
Telemonitoring interface
ANCR
67
1MRS756664
MicroSCADA Pro
IEC 61850 System Design
LN
68
Description
Supported by SA
LIB
Supported by
SCL Importer
ARCO
ATCC
AVCO
Voltage control
MDIF
Differential measurements
MHAI
Harmonics or interharmonics
MHAN
MMTR
Metering
MMXN
MMXU
Measurement
MSQI
MSTA
Metering Statistics
SARC
SIMG
SIML
SPDC
XCBR
Circuit breaker
XSWI
Circuit switch
TCTR
Current transformer
TVTR
Voltage transformer
YEFN
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
ZLIN
1MRS756664
MicroSCADA Pro
LN
Description
ZMOT
Motor
ZREA
Reactor
ZRRC
ZSAR
Surge arrestor
ZTCF
ZTCR
Supported by SA
LIB
Supported by
SCL Importer
69
MicroSCADA Pro
IEC 61850 System Design
GetDataValues
GetDataDirectory
GetDataDefinituion
Data set
GetDataSetValues
GetDataSetDirectory
Reporting
BRCB
Report
GetBRCBValues
SetBRCBValues
URCB
Report
GetURCBValues
SetURCBValues
70
1MRS756664
1MRS756664
MicroSCADA Pro
11.
Terminology
Term
Description
IP Address
Logical Device
71
1MRS756664
MicroSCADA Pro
IEC 61850 System Design
12.
72
Abbreviations
Abbreviation
Description
ACSI
BRCB
CDC
CET
CID
CPI
DCOM
DOI
FCD
HMI
Human-machine interface
HSB
Hot Stand-by
ICD
IEC
IED
IP
Internet protocol
LAN
L/R
Local/Remote
MMS
NIC
OPC
PRP
RCB
RSTP
SCD
SCIL
SCL
SNMP
SNTP
SSS
ABB Oy
Substation Automation Products
P.O. Box 699
FI-65101 VAASA, FINLAND
Tel. +358 10 22 11
Fax. +358 10 224 1094
www.abb.com/substationautomation
Contact us