EXPERION PKS RELEASE 516
Ethernet Interface Module with IEC 61850 User Guide
EPDOC-X462-en516A August 2020 Disclaimer
This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice.
Copyright 2020 - Honeywell International Sàrl
- 2 - Contents 3 Chapter 1 - About this document 6 1.1 Intended audience 6 1.2 Prerequisite skills 6 1.3 Related documents 6 Chapter 2 - Introduction 8 Chapter 3 - About IEC 61850 9 3.1 About IEC 61850 protocol 9 3.2 IEC 61850 features 9 Chapter 4 - EIM terms and definitions 10 Chapter 5 - IEC 61850 network device and IED support policy 13 Chapter 6 - IEC 61850 control integration topologies 16 6.1 Network recommendations for creating IEC 61850 control integration topologies 16 6.2 HSR topology model 16 6.3 PRP topology model 18 Chapter 7 - Dual home configurations for SCADA server 20 Chapter 8 - IEC 61850 SCADA server acting as alarm and events server 21 Chapter 9 - Series CEIM with IEC 61850 Configuration 22 9.1 EIM Configuration rules-with IEC61850 23
9.1.1 EIM with IEC61850 Capacity 23 9.2 Initial load order guidelines 24 9.3 Configuring and Loading IEC61850 PROTOCOL Block 24
9.3.1 Prerequisites 24
9.3.2 To configure PROTOCOL Block (“PB_61850”) values 25 9.3.3 Load IEC 61850 Protocol Block 27
9.3.4 Delete IEC 61850 Protocol Block 27 9.4 Creating templates for logical devices and logical nodes 27
9.4.1 Prerequisites 28
9.4.2 To create a template 29 9.4.3 To recreate a missing logical device template 33 9.5 Creating and configuring an IED 37
9.5.1 To create an IED instance 38
- 3 - 9.6 Editing IED block parameters 41
9.6.1 Prerequisites 41
9.6.2 To edit IED block parameters 42 9.7 Adding or associating MMS Report Control blocks to an IED 44
9.7.1 Prerequisites 44 9.7.2 Steps to create MMS Report instance 44 9.7.3 Assign MMS Report instance to IED 47
9.7.4 Report definition for an MMS Report instance 47 9.7.5 Load MMS Report Instance 49 9.7.6 Delete MMS Subscriber block from Monitor tree 50 9.8 Adding or associating logical devices to an IED 51
9.8.1 Prerequisites 51
9.8.2 To use drag and drop method to add/associate logical devices to an IED 51 9.8.3 To use the File menu method to add/associate logical devices to an IED 51 9.9 Assigning logical devices 53
9.9.1 Prerequisites 54 9.9.2 To assign logical devices to an IED instance 54 9.10 To instantiate logical nodes associated with a logical device 54 9.11 Checking IED configuration 55
9.11.1 Prerequisites 56 9.11.2 To check IED configuration 56 9.12 Reloading EIM instance 56 Chapter 10 - Configure control strategies 57 10.1 Prerequisites 57 10.2 To configure Control Strategy which reads parameters from IED using the parameter connector 58 10.3 Control writes 60
10.3.1 Prerequisites 61
10.3.2 To perform a control write 61 10.4 Configuring MMS Subscriber block reports with DSMAP Block 62
10.4.1 Prerequisites 62 10.4.2 To configure DSMAP values 63 Chapter 11 - Communication Failures and fixing common problems in EIM- 61850 65 11.1 EIM cannot communicate with a single IED 65
- 4 - 11.2 How to determine the number of IEDs loaded on the EIM 66 11.3 Read and write failures in EIM with IEC 61850 (EIM to IED) 66 11.4 Fixing other Common Problems 66 Chapter 12 - Viewing EIM with IEC 61850 operation status in Control Builder 67 12.1 Statistics tab –Protocol block 67 12.2 Memory tab –Protocol block 68 12.3 Statistics tab – IED block 70 Chapter 13 - EIM with IEC 61850 operation 72 Chapter 14 - Control Builder block icon descriptions for EIM with IEC 61850 73 Chapter 15 - Control Builder block icon descriptions for EIM with IEC 61850 PROTOCOL block 76 Chapter 16 - Control Builder block icon descriptions for EIM with IEC 61850 MMS Subscriber block 77 Chapter 17 - Control Builder block icon descriptions for EIM with IEC 61850 DSMAP block 79
- 5 - CHAPTER
1 ABOUT THIS DOCUMENT
Revision Date Description
A August 2020 Initial release of the document.
This document provides information about planning, installing, configuring and operating the hardware and software components associated with the EIM with IEC 61850 Interface Module.
1.1 Intendedaudience
This guide is intended for engineers who configure the following:
l Integration of EIM with IEC 61850 into the Experion system using the EIM Interface Module.
l Intelligent Electronic Device(IED) communication with C300 Controller.
1.2 Prerequisite skills
l Familiar with working in a Microsoft Windows operating environment.
l Familiar with Experion system topology and using Experion applications.
l Familiar with using Control Builder.
l Familiar with basic principles of IEC 61850 technology and standards.
1.3 Related documents
You may also refer to the following related Experion documents.
- 6 - Chapter 1 - About this document
Document Description Overview Provides a comprehensive overview of Experion, including basic concepts and terminology.
Control Building Describes how to perform tasks within the Control User's Guide Builder application such as configuring hardware devices, continuous control strategies, and sequential control strategies.
C300 Controller Provides information for planning, designing, User’s Guide installing, operating and troubleshooting C300 process controllers in an Experion system.
Control Hardware Provides an overview of things you should consider Planning Guide when planning for the installation of your Series C cabinet.
Ethernet Interface Provides information about the Series C EIM module Module Hardware and and its operation irrespective of a specific protocol. Common Platform User’s Guide
- 7 - CHAPTER
2 INTRODUCTION
This section provides information about IEC 61850 control integration you must know before introducing it in an Experion network. For more information about the Ethernet Interface Module and its general operations, irrespective of a specific protocol, please see the Ethernet Interface Module Hardware and Common Platform User’s Guide.
- 8 - CHAPTER
3 ABOUT IEC 61850
This section gives an overview of the IEC 61850 protocol. It also lists the available IEC 61850 standards.
3.1 AboutIEC61850protocol
IEC 61850 is a global standard for the design of electrical substation automation. IEC 61850 is a part of the International Electrotechnical Commission's (IEC) technical committee reference architecture for electric power systems. It enables the integration of protection, metering, monitoring and control functions with one common protocol. It supports a comprehensive set of substation functions. This protocol runs over TCP/IP networks or substation LAN using high speed switched Ethernet to obtain the necessary response times for protective relaying. The IEC 61850 standards specification document is available in the IEC website (http://www.iec.ch).
3.2 IEC61850features
Some of the features of IEC 61850 include:
l Enables use of multi-vendor electrical devices on a common bus network facilitating integration, device engineering and fast response.
l Ensures easy introduction of newer devices into the electrical network without the need for removing the older devices.
l Supports large number of diagnostic parameters.
l Reduces costs of installation, commissioning and maintenance.
- 9 - CHAPTER
4 EIM TERMS AND DEFINITIONS
This section provides information about the terms and definitions associated with EIM used in this document.
Term Definition CDA Control Data Access The application layer protocol used for native communication within Experion. It supports both parameter access response messaging and notification messaging.
CIP Common Industrial Protocol The Common Industrial Protocol is used for industrial automation applications. CIP provides a comprehensive suite of data communication services for manufacturing automation applications.
Client That node or device in a communication relationship which initiates requests to another node or device, called the Server. Client – Server relationships exist in several contexts that apply to EIM operation. This is true of uplink communications as well as downlink communications.
Dual home Dual-home/ dual homing is a network topology where a network device is built with more than one network interface.
EIM Ethernet Interface Module
EtherNet/IP™ Ethernet Industrial Protocol EtherNet/IP is an industrial network protocol that adapts the Common Industrial Protocol to standard Ethernet. It is widely used in a range of industries including factory, hybrid and process. The EtherNet/IP and CIP technologies are managed by ODVA (Open DeviceNet Vendors Association).
Firmware An HMI tool, newly introduced into Experion R501, which Manager supports the download of firmware images to the EIM as well Tool as the upload of diagnostic information from the EIM. The Firmware Manager Tools is compatible with the EIM’s communication technology whereas the Series C “CTools” tool is not.
FTE Fault Tolerant Ethernet
- 10 - Chapter 4 - EIM terms and definitions
Term Definition FTE is the Ethernet-based, redundant control network of Experion.
HSR High Availability Seamless Redundancy High Availability Seamless Redundancy protocol is a refinement of PRP standardized in IEC 62439-3 clause 5 which is specific to ring topologies and provides zero switch-over time. HSR is one of 3 possible downlink network redundancy options configured on the EIM platform block. HSR is used only with the IEC 61850 EIM application image.
IEC 61850 IEC 61850 is a communication standard for electrical substation automation systems established by the International Electrotechnical Commission's (IEC). The standard maps to multiple protocols include MMS (Manufacturing Message Specification) and GOOSE (Generic Object Oriented Substation Event).
NTP Network Time Protocol NTP is a standardized internet networking protocol used for synchronizing computer clock times in a distributed network of computers. On the FTE uplink, the EIM supports time synchronization by NTP or PTP.
Platform The object at the top of the EIM’s data organization hierarchy. It Block presents CDA parameters which allow for the configuration of EIM properties common to all supported downlink protocols. It presents system operational parameters which allow for the control of key behaviors such as redundancy. It also presents statistical parameters which allow for the view of runtime performance metrics.
Protocol The object at the second level in the EIM’s data organization Block which presents information specific to the supported downlink protocol as CDA parameters. This includes statistical parameters and in some cases may also include configuration parameters. In R501, the EIM supports two alternate protocol blocks: the IEC 61850 protocol block and the EIP protocol block.
PRP Parallel Redundancy Protocol PRP provides layer 2 network redundancy by sending two copies of the same frame over two independent networks. A Redundancy Control Trailer (RCT) is added to each frame (which includes a sequence number to support detection of duplicate messages so that one may be discarded.) It supports zero failover time. PRP is one of 3 possible downlink network redundancy options configured on the EIM platform block.
- 11 - Chapter 4 - EIM terms and definitions
Term Definition PRP is used only with the IEC 61850 EIM application image.
PTP Precision Time Protocol PTP is a standardized internet networking protocol used for synchronizing computer clock times in a distributed network of computers. PRP provides higher precision than NTP. On the FTE uplink, the EIM supports time synchronization by NTP or PTP.
SAS Safety and Automation System A term used to describe both the Safety Instrumented System and Process Control System taken together as a component of the automation architecture of a manufacturing or production site. The process control system is composed of a basic process control system which can include subsystems related to power distribution and management as well as process control. The power management system is responsible for load shed control.
Server That node or device in a communication relationship which responds to requests initiated by another node or device, called the Client. Client – Server relationships exist in several contexts that apply to EIM operation. This is true of uplink communications as well as downlink communications.
- 12 - CHAPTER
5 IEC 61850 NETWORK DEVICE AND IED SUPPORT POLICY
EIM supports IEC 61850 complaint switches and IEC 61850 edition 1 and edition 2- compliant IEDs. It can connect to any IEC 61850 complaint switch using Redbox. Honeywell is not restricting users to IEDs or device types. Following is a list of network switches and IED devices used by Honeywell for EIM integration and qualification, for your reference.
ATTENTION Honeywell does not restrict users to any particular IED vendors or types or IEC 61850 compliant switches.
- 13 - Chapter 5 - IEC61850 network device and IED support policy
IEC 61850 Device/switch model Vendor edition Communication ports REU615-A (Voltage ABB 1 Dual RJ45 ports for protection and Control) making HSR ring and single optic fibre port
RET615-D (Transformer ABB 1 Single RJ45 port and protection and Control) connect through Redbox to be part of HSR ring or PRP network
REF620-A (feeder ABB 1 Dual RJ45 ports for protection and Control) making HSR ring and single optic fibre port
REM615-A (Motor ABB 1 Single RJ45 port and protection and Control) connect through Redbox to be part of HSR ring or PRP network
REF615A (feeder ABB 1 Single RJ45 port and protection) connect through Redbox to be part of HSR ring or PRP network
RSP25 Hirschman N/A Redbox
PT-G503-PHR-PTP-HV MOXA N/A Redbox
PT7528 MOXA N/A IEC 61850 compliant switch
GE Multilin M60 – Motor GE N/A IEC 61850 compliant Protection System switch
SEL 787 – Transformer N/A IEC 61850 compliant l Siemens Protection Relay Sepam switch Series
l Schneide r
SIPROTEC 7SJ82 – Over Siemens 1 Dual RJ45 ports current protection Configurable for PRP communication or HSR ring communication
SIPROTEC 7SJ84 – Over Siemens 1 Dual RJ45 ports. current protection Configurable for PRP
- 14 - Chapter 5 - IEC61850 network device and IED support policy
IEC 61850 Device/switch model Vendor edition Communication ports communication or HSR ring communication
Multilin F35 – Feeder GE 1 Dual RJ45 ports. protection System Configurable for PRP communication or HSR ring communication
SEL-451 Protection SEL-451 1 Dual RJ45 ports. Automation Control Protection Configurable for PRP Automation communication or HSR Control ring communication
REF615A(feeder ABB 2 Dual optical fiber protection) Ethernet ports and Configurable for PRP communication or HSR ring communication
Dual optical fiber Ethernet ABB 2 Dual optical fiber ports and Configurable for Ethernet ports and PRP communication or Configurable for PRP HSR ring communication communication or HSR ring communication
- 15 - CHAPTER
6 IEC 61850 CONTROL INTEGRATION TOPOLOGIES
This section provides information about the different topologies for IEC 61850 control integration.
6.1 Network recommendations for creating IEC 61850 control integration topologies
l The IEC 61850 network should not be directly connected to an L3 router. If access to L3 is required, it is recommended to use an L 2.5 router to connect FTE and IEC 61850 networks together. The L 2.5 router should connect to the L3 router.
l To disable Microsoft Windows Client and File Sharing options for the IEC 61850 ports on the SCADA Server: o Ensure lower MAC address is selected for FTE network installation. If Experion is installed on servers like Dell 320, then this machine consists of 4 built-in NIC interfaces, Use the first two NICs for FTE connection and other two NICs for IEC 61850 network connections. If you have additional dual NICs on 2 NIC built-in type servers, ensure that lower MAC address NIC is selected for FTE. With this setup, Experion installation automatically selects the lower MAC interfaces ( 1st two interface of built-in NICs) for FTE and System Management and also sets proper binding order that FTEMUX is on top. o Also, need to interface TCP/IPv4 metric on both the IEC 61850 interfaces to 5 and 10. o Disable NETBIOS on both IEC 61850 interfaces. o In addition, the IEC 61850 settings must not include a gateway address on either interface, assuming that there is a gateway address on the FTEMUX.
l Do not connect IEC 61850 network to the FTE ports.
l Enable the Flow Control option on the IEC 61850 switch ports connected to the EIMs
l HSR topology model
l PRP topology model
6.2 HSR topology model
This diagram portrays the HSR ring topology configuration for the various physical components for an EIM with IEC 61850 and the related Experion L2 nodes, L1 embedded nodes, FTE and IEC 61850 network equipment.
- 16 - Chapter 6 - IEC 61850 controlintegration topologies
TIP Non-Redundant EIM is shown here, but a Redundant EIM can be used with a non- redundant network as well
Figure 6.1 HSR topology model
The following is a simple IEC 62439 High-availability Seamless Redundancy (HSR) Ring topology example.
- 17 - Chapter 6 - IEC 61850 controlintegration topologies
Figure 6.2 EIM with IEC 61850 HSR Topology
6.3 PRP topology model
This diagram portrays the deployment PRP topology configuration for the various physical components for an EIM with IEC 61850 and the related Experion L2 nodes, L1 embedded nodes, FTE and IEC 61850 network equipment. This is a simple IEC 62439 Parallel Redundancy Protocol (PRP) topology example.
- 18 - Chapter 6 - IEC 61850 controlintegration topologies
Figure 6.3 PRP topology model
- 19 - CHAPTER
7 DUAL HOME CONFIGURATIONS FOR SCADA SERVER
For information about IEC61850 SCADA, refer to the ILMS solution which supports PRP and HSR drivers.
- 20 - CHAPTER
8 IEC 61850 SCADA SERVER ACTING AS ALARM AND EVENTS SERVER
The IEC 61850 SCADA server supports configuration of events and alarms. For information about configuring events and alarms, refer to the IEC 61850 SCADA Configuration Reference document in the Experion PDF Collection.
- 21 - CHAPTER
9 SERIES CEIM WITH IEC 61850 CONFIGURATION
This section includes the tasks associated with configuring EIM with IEC 61850. That includes information and tasks associated with Control Builder creation, configuration and loading of the IEC61850 PROTOCOL Block , IEDs, logical devices and logical nodes used in control strategies. As a first step, consult the Ethernet Interface Module Hardware and Common Platform User Guide to create an EIM block in Control Builder. Creating an EIM is not protocol-specific. The hardware and common platform guide also includes a general explanation about Control Builder loading operations. Refer to the Control Building User's Guide for basic functionality details about calling up, navigating and interacting with the application. Also, note that menus, selections, tree views, and configuration forms may vary depending upon the licensed options installed on your system. The EIM act as an IEC 61850 gateway for MMS reports. The figure below illustrates the flow of data.
Figure 9.1 EIM as IEC 61850 Gateway
l EIM Configuration rules-with IEC61850
l Initial load order guidelines
l Configuring and Loading IEC61850 PROTOCOL Block
l Creating templates for logical devices and logical nodes
l Creating and configuring an IED
l Editing IED block parameters
l Adding or associating MMS Report Control blocks to an IED
l Adding or associating logical devices to an IED
- 22 - Chapter 9 - Series CEIM with IEC 61850 Configuration
l Assigning logical devices
l To instantiate logical nodes associated with a logical device
l Checking IED configuration
l Reloading EIM instance
9.1 EIM Configuration rules-with IEC61850
o The EIM with IEC61850 supports CDA P2P connections with the C300 controller and also PCNT02 version C300 controller with Enhanced Functionality. o The EIM with IEC61850 supports DSIN Block connections only with the PCNT02 version C300 controller. o Each EIM supports 2 downlink connection to an IEC61850 Network. For IEC62439 HSR Ring Networks or PRP Networks, each EIM should be connected to HSR ring in series or to both sides of the PRP network. For connections to a non-redundant IEC61850 network, the EIM can be configured to turn off HSR/PRP and only use the single LAN A port. o The Ethernet Subnet Domain used for the IEC61850 network must be configured to be a separate Subnet Domain from the FTE Network that the IEC61850 Interface Module is connected to. o If the IEC61850 Network must be connected to L3 (Not Recommended), it is suggested that an L2.5 Router(s) (not shown) be placed between the L3 Router and the IEC61850 Network and then the L2.5 router connected to L3. If routing to the FTE Network from the IEC61850 network is required, the FTE Network could also be connected to this L2.5 Router and ACLs be configured to severely limit the required traffic to only the nodes & protocols required.
9.1.1 EIMwithIEC61850Capacity
Specification Limit EIMs with IEC61850/Cluster Maximum Number of EIMs per Cluster 64 EIMs/Cluster(1)
Maximum Number of C300s per EIM 5 C300 peer connections to 1 EIM
Maximum Number of EIMs per C300 5 EIM peer connections to 1 C300
Maximum Number of connected IEDs per 64 IEDs(2) EIM
Maximum Number of IEDs resident on an unlimited IEDs IEC61850 Network
Notes (1) A single Experion server with its associated stations and controllers is referred to as a cluster or Experion cluster (2) Physical IED Nodes with a unique IP Address on the IEC61850 network with reference blocks loaded to a single EIM
- 23 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.2 Initial load order guidelines
Perform the initial load of control strategy components from the Project view in the following order to minimize possible load interaction generated error messages.
Table 9.1 Initial load order guidelines Order Component 1 IEC61850M
2 IEC61850LINK
3 IED
4 Logical device
5 Logical Node
5 CM or SCM*
* Refer to the Control Building User's Guide for information about loading these components.
9.3 Configuring and Loading IEC61850 PROTOCOL Block
The IEC 61850 protocol block is required for the EIM to communicate with the IEC 61850 devices on the downlink. To create an instance of the IEC 61850 Protocol, user has to open the configuration form for the EIM instance. On the Main tab there is a Protocols grid available. The grid will list all the protocols supported by EIM. In the R501 release, EIM will support only EtherNet/IP and IEC 61850 based MMS protocols. Considerations
l Click the + sign in front of the EIM icon to open its directory tree and represent its icons. With the Hierarchal Building license option, you must have the Assignment View active to view EIM and its PROTOCOL blocks.
l In a redundant EIM, the PROTOCOL blocks are shown with the primary EIM block only.
l Considerations for Tag Name o Must not exceed 40 characters o Must contain at least one letter (A-Z) o Must not contain an embedded space or leading space
l Considerations for Item Name o Must not exceed 40 characters o Must contain at least one letter (A-Z)
9.3.1 Prerequisites
You have added an EIM block to the Project tree.
- 24 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.3.2 To configure PROTOCOL Block (“PB_61850”) values
1. Right-click the PROTOCOL Block icon and choose Module Properties from the list. The EIM Parameters form is displayed, with the Tag Name text box highlighted. Enter the preferred block tag name or accept the default value.
2. In the Item Name text box, enter the name of the item this object is associated to in the Enterprise Model Builder hierarchy. 3. In the Description text box, and enter the preferred description. The description appears in the detail displays and group displays associated with this block. Note that the Description text box is under the 'Identification' tab. 4. Select the IEC 61850 protocol option in the grid. 5. Refer to the Control Building User's Guide and/or the online help to complete configuration data on the Server History, Server Display, Control Confirmation, and Identification tabs. Refer to the “EIM operation status in Control Builder” in the Operations section of the EIM Hardware and Common Platform User’s Guide for information on Statistics and Memory tabs. 6. After entering the configuration data, click OK to close the PROTOCOL Block Parameters form.
- 25 - Chapter 9 - Series CEIM with IEC 61850 Configuration
7. An instance of the IEC 61850 protocol block will be created and assigned under the EIM in the project tree. Note that IEC 61850 Protocol cannot be supported on an EIM with EtherNet/IP Protocol. The system will restrict the user from creating and assigning an IEC 61850 protocol instance on an EIM that already has an instance of EtherNet/IP protocol assigned to it.
- 26 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.3.3 Load IEC61850ProtocolBlock
To load an instance of the IEC61850 Protocol Block, select the EIM and perform the load operation for the EIM. The load of the EIM will add the protocol block instance to the load dialog. The protocol instances configuration will be loaded to the EIM hardware along with the EIM instance.
9.3.4 DeleteIEC61850 ProtocolBlock
l Delete from Project Tree: To delete an instance of the IEC61850 Protocol block from the project tree, open the configuration form of the EIM and uncheck the the IEC 61850 protocol option in the grid and click on OK to save the changes. The protocol block will be deleted from project tree.
l Delete from Monitor Tree: To delete an instance of the IEC61850 Protocol block from the monitor tree, delete the EIM from the monitor tree. This behavior is similar to the delete of CEE blocks from C300.
9.4 Creating templates for logical devices and logical nodes
This section describes tasks to create templates for logical devices and logical nodes using ICD/CID
- 27 - Chapter 9 - Series CEIM with IEC 61850 Configuration
files. This section also describes tasks to recreate missing logical device(s) templates. You can recreate missing logical device(s) templates by selecting the missing logical device(s) from the ICD/CID file in the IEC 61850IED Device Description Import dialog box and importing it back to the Control Builder. Considerations for creating templates
l Ensure that an approved antivirus application is installed on the node used to import ICD/CID files.
l The ICD/CID file must be stored in the following directory location. o Default path: C:\ProgramData\Third Party Files\SCL files\ o Custom installation path:
l You need not perform this task if a block for the given device type already exists in the Control Builder Library database.
l It is recommended to use the ICD files for template creation. If you use ICD/CID file, you have ensure to use appropriate device to import the template. Otherwise, the template is not created.
l Considerations for the Manufacturer field. o Manufacturer name is used for creating Library name in Control Builder. Hence, it is a mandatory field. o Maximum number of characters allowed is 40, which is the maximum number of characters allowed for Library name in Control Builder. o According to Control Builder tag naming criteria, the following characters are not allowed for Manufacturer field. `~!@#$%^&*+-=(){}[]|\\:;'<>,.?/ \"\t
l Considerations for the Type field. o Default value of Template Prefix is the value in the Type column. o You can also configure the Template Prefix if required. o The Type field is used for generating logical device template name. Hence, it is a mandatory field. o The logical device template name displayed in the library tree is formed as
9.4.1 Prerequisites
You must have the ICD/CID file for the IED device from vendor's IED configuration tool.
- 28 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.4.2 Tocreateatemplate
1. You can open the IEC 61850IED Device Description Import dialog box in one of the following ways.
Option Description IEC In the Control Builder, click on the IEC 61850IED Device 6185 0IED Description Import icon. Devic e Descr iption Impo rt icon
From On the File menu, click New > Type > IEC 61850 Device. the File menu
The IEC 61850IED Device Description Import dialog box appears.
Figure 9.2 IEC 61850 Device Type dialog box
- 29 - Chapter 9 - Series CEIM with IEC 61850 Configuration
2. Click to browse for the applicable ICD/CID file, and navigate to the location of the required file.
ATTENTION These files are saved in the following location. Ensure that this folder or sub-folder is NOT excluded from virus scanning.
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: %User Selected Path%\Third party files\SCL files
Examples of the directory path:
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: C:\2 RUNTIME_CIP-VM\Third party files\SCL files
After the ICD/CID file is selected, the details of the manufacturer and the device type are displayed in the Device Information section.
3. Select the ICD/CID files you want to import. The Library Name and Template Prefix fields display the information from the ICD/CID files.
- 30 - Chapter 9 - Series CEIM with IEC 61850 Configuration
4. Click Create. The creation of logical device templates of an IED in the Control Builder library begins. The progress bar displays the current status of logical device template creation. The Status field displays one of the following status during template creation.
Status Description
In Progress Logical device template creation is in progress
Saving changes Logical device templates are getting saved in ERDB
Completed Logical device template created successfully
Failed Logical device template creation failed
Cancelled Logical device template creation is cancelled by the user
5. After completion, the Status field in the progress bar displays the status as Completed. 6. Click Close. In the Library tree, a new device block type is created and the ICD/CID files with logical devices and logical nodes are listed. The logical nodes associated with the logical devices are listed under their respective logical device template.
- 31 - Chapter 9 - Series CEIM with IEC 61850 Configuration
Figure 9.3 Logical devices and logical nodes in Library tree
The File menu is also updated with the menu options to instantiate the newly created templates for the logical devices. All the IEC 61850 logical devices are listed in the File >New >IEC 61850 Devices menu.
- 32 - Chapter 9 - Series CEIM with IEC 61850 Configuration
Figure 9.4 Logical devices and logical nodes in File menu
9.4.3 To recreate a missing logicaldevice template
1. On the File menu, click New > Type > IEC 61850 Device. The IEC 61850IED Device Description Import dialog box appears.
Figure 9.5 IEC 61850 Device Type dialog box
- 33 - Chapter 9 - Series CEIM with IEC 61850 Configuration
2. Click to browse for the ICD/CID file, and navigate to the location of the file which contains the definition of the missing logical device(s).
ATTENTION These files are saved in the following location. Ensure that this folder or sub-folder is NOT excluded from virus scanning.
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: %User Selected Path%\Third party files\SCL files
Examples of the directory path:
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: C:\2 RUNTIME_CIP-VM\Third party files\SCL files
After the ICD/CID file is selected, the details of the manufacturer and the device type are displayed in the Device Information section.
3. Select the ICD/CID files you want to import. The Library Name and Template Prefix fields display the information from the ICD/CID files.
- 34 - Chapter 9 - Series CEIM with IEC 61850 Configuration
4. Click Create. The Device already exists dialog box appears. The missing logical devices are listed in the Missing Devices column.
- 35 - Chapter 9 - Series CEIM with IEC 61850 Configuration
5. Select the required logical device(s), and click Create Missing. The ICD/CID file is imported and the missing logical device is added in the Library tree.
- 36 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.5 Creatingandconfiguringan IED
This section includes task to create an instance of Intelligent Electronic Device (IED) and add it to the Project tree. An IED instance can also be created from the Library by dragging and dropping an IED instance to the Project tree. Considerations Ensure that an approved antivirus application is installed on the node used to import ICD/CID files.
- 37 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.5.1 TocreateanIEDinstance
1. On the File menu, click New >IEC 61850 Devices > IED - Intelligent Electronic Device. The Parameter configuration form for the IED instance appears. 2. In the Tag Name text box, enter the preferred block tag name or accept the default value. 3. In the Item Name text box, enter the name of the item this object is associated to in the Enterprise Model Builder hierarchy. 4. In the Keyword Description text box, enter the preferred description. The description appears in the detail displays and group displays associated with this block. 5. Refer to the online help to complete configuration data on the Server History, Server Display, QVCS and Identification tabs Refer to the “Viewing_EIM_operation_status_in_Control_Builder” section for information on Statistics tab. 6. When you complete entering configuration data, click OK to close the configuration form. A new instance of the IED is created in the Project tree under the Unassigned category. 7. Draganddropthe IED instance under the Unassigned tree to the PROTOCOL Block instance in the Project tree.
Figure 9.6 IED instance assigned to PROTOCOL Block
TIP You can also assign an IED instance to a PROTOCOL Block. See “Instantiating logical nodes associated with a logical device.”
- 38 - Chapter 9 - Series CEIM with IEC 61850 Configuration
8. Associate an ICD/CID file to the IED instance. a. Right-click an IED instance (assigned to a PROTOCOL Block), and choose Associate ICD/CID. The Associate ICD/CID-
b. In the Select New Association section, click to browse for the applicable ICD/CID file, and navigate to the location of the required file.
ATTENTION These files are saved in the following location. Ensure that this folder or sub- folder is NOT excluded from virus scanning.
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: %User Selected Path%\Third party files\SCL files
Examples of the directory path:
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: C:\2 RUNTIME_CIP-VM\Third party files\SCL files
c. Select the required file and click Open. The list of available ICD/CIDs are listed in the Available IEDs section.
Figure 9.7 List of available IEDs in an ICD/CID file
- 39 - Chapter 9 - Series CEIM with IEC 61850 Configuration
d. Select the IED you want to associate to this IED instance by clicking the check box in the Select column, and click OK.
l The Select Configuration form associated ICD/CID file is configured on IED instance. All related parameters are updated on the IED instance.
l The following message appears after all the IEDs are successfully imported.
Figure 9.8 Message displayed after successful import
9. Open the parameter configuration form for the IED instance, and select the Main tab.
l The Device Configuration, Device Information, CID information, IED Information, and Logical Device Information sections display the information of associated ICD/CID file, as shown in the figure.
l The Assigned Instances column in the Logical Device Information section displays the assigned logical device to that IED.
Figure 9.9 ICD/CID file association details in the Main tab
- 40 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.6 Editing IED block parameters
This section describes tasks to edit IED block parameters to an IED instance. You can either reconfigure IED block parameters or associate new set of IED block parameters to an IED instance. Considerations
l You cannot reconfigure IED with a ICD/CID file of different IED name or IP address or IED type if the IED has a logical device associated to it.
l You cannot reconfigure IED with ICD/CID file with different IED name or IP address or IED type if the IED is loaded.
l If you have the modified version of an ICD/CID file which is compatible with an IED instance, you can associate the new ICD/CID file.
l Ensure that an approved antivirus application is installed on the node used to import ICD/CID files.
9.6.1 Prerequisites
You must have templates of the logical devices and logical nodes for IED block available in the Library tree. ()
- 41 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.6.2 ToeditIEDblockparameters
1. Right-click the IED instance (assigned to an IEC61850LINK), and choose Associate ICD/CID. The Associate ICD/CID-
Option Description Asso Go To Step 3 ciate a new ICD/ ATTENTION CID When you associate a new ICD/CID file, the existing file IED block parameters are replaced with the new IED block parameters.
Reco a. Click the Reset button. nfigu The following message appears after all the IEDs are re successfully removed. IED
block Figure 9.10 Message displayed after successful reset para meter s
b. Associate a new ICD/CID file. Go To Step 3
3. In the Select New Association section, click to browse for the applicable ICD/CID file, and navigate to the location of the required file.
ATTENTION These files are saved in the following location. Ensure that this folder or sub-folder is NOT excluded from virus scanning.
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: %User Selected Path%\Third party files\SCL files
Examples of the directory path:
- 42 - Chapter 9 - Series CEIM with IEC 61850 Configuration
l Default path: C:\ProgramData\Third party files\SCL files
l Custom installation path: C:\2 RUNTIME_CIP-VM\Third party files\SCL files
4. Select the required file and click Open. The list of available IEDs are listed in the Available IEDs section.
Figure 9.11 List of available IEDs in an ICD/CID file
5. Select the IEDs you want to associate to this IED instance by clicking on the check box in the Select column, and click OK.
l The Control Builder library begins importing the ICD/CID file .
l The following message appears after all the IEDs are successfully imported.
Figure 9.12 Message displayed after successful import
- 43 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.7 Adding or associating MMS Report Control blocks to an IED
To represent an MMS Report in Control Builder, an instance of the MMSSUBS need to be created and associated with an MMS Report.
9.7.1 Prerequisites
l For MMS Subscriber Block under a redundant EIM, make sure at least two connection instances (available client connections) for the IED are available. For a non-redundant EIM, at least one instance should be available.
l IED must be created and configured.
9.7.2 Steps tocreateMMS Report instance
1. To create an MMS Report instance, open the configuration form of an IED instance that has been configured with a CID/ICD file. Double click on the IED block. Below is the Configuration form of a configured IED instance. You can rename the block and add configuration details. Refer to the Control Builder User’s Guide or online help to complete data entry on various tabs shown below.
CAUTION To update a CID file, the Subscribe block must first be dissociated (deleted), and then associated again.
- 44 - Chapter 9 - Series CEIM with IEC 61850 Configuration
If you change the name in Subscriber block, but the block is already associated with DSIN block, then you must also double click and change the name in the DSIN block.
2. Navigate to the “Subscriber Blocks” Tab. See the list of the MMS Report read from the CID/ICD. The MMS Report grid will list the MMS Reports. Following is an example of the IED Subscriber Blocks tab.
- 45 - Chapter 9 - Series CEIM with IEC 61850 Configuration
3. The grid has various columns that represent the different attributes of the ReportControl read from the IED configuration file. The below table describes the columns and the mapping to the ReportControl attributes.
4. To create MMS Report instance representation in Control Builder, select the “Associate” check box for the MMS Report that need to be instantiated.
- 46 - Chapter 9 - Series CEIM with IEC 61850 Configuration
5. Click on OK to save the changes. An instance of MMSSUBS will be created and assigned to the IED.
9.7.3 AssignMMSReportinstancetoIED
Drag MMSSUBS instance in the “Unassigned” and drop onto an IED instance in Control Builder project tree. Instance of MMSSUBS will be assigned to the IED instance.
9.7.4 Report definition for an MMS Report instance
1. To view the details of the data set supported in the MMSSUBS instance, first open the configuration form of the MMS Report instance. The Main tab contains the parameters that describe the various attributes of the report definition read from the IED configuration file associated with the parent IED instance in the project tree. 2. Navigate to the “Data Set” tab to view the data set parameter details associated with the report.
The upper grid of the dual grid has various columns that provide information related to the data set parameters.
- 47 - Chapter 9 - Series CEIM with IEC 61850 Configuration
The lower grid of the dual grid has the States Description parameter. For the data attributes which are supported for SOE, user can specify their own state descriptions. Depending on the data type of the data attribute in the dataset, the number of states will vary.
3. Additionally, the user can specify their own alias names for the parameters of the data set definition in the MMS Report instance. 4. Click on OK to save the changes.
- 48 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.7.5 LoadMMSReportInstance
To perform load of the MMS Report instance select the MMSSUBS instance in “Assigned” state under the IED and right click on it. Select the load option. The load dialog will be launched.
CAUTION System will restrict the user from loading an MMS Report instance whose parent IED is not loaded to the EIM.
- 49 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.7.6 Delete MMS Subscriber block from Monitor tree
l To delete the MMS Subscriber block from the monitor tree, select the block instance and select the Delete menu option or the delete button on the Tool bar. The delete of the MMSSUBS will also delete the DSMAP blocks under it.
l Delete Selected Object(s) dialog will be shown. Click on “Delete Selected Object(s)” button to delete the instance. The MMSSUBS will be removed from the project tree.
ATTENTION You can also disassociate an MMS Report Instance through the IED Configuration form. Open the configuration form of the parent IED block.
- 50 - Chapter 9 - Series CEIM with IEC 61850 Configuration
Navigate to the Subscriber Blocks tab. Uncheck / De-Select the Associate check box for the Reports that you want to delete from the project tree. Click on Ok to save the changes. The selected MMSSUBS instances will be deleted from the project tree.
9.8 Addingorassociating logical devices to an IED
This section includes tasks to add or associate a logical devices to an IED. Considerations
l Use drag and drop or menu selections method to assign a logical device to an IED in the Project tree.
l It is recommended to check the block configuration parameters after the device is assigned to IED.
9.8.1 Prerequisites
l You must have templates of the logical devices and logical nodes for IED block available in the Library tree. Find the description test box under the 'Identification' tab. ()
l You must have configured the IED device with appropriate CID files to add a logical device to IED device from Project tree.
9.8.2 To usedrag and drop method to add/associatelogical devices to an IED
1. In the Library tree directory, click sign in front of the required IED type to show stored device block types. 2. Drag the IED icon to an open area in the Project tree. (Note that cursor appears with + sign, when positioned in a valid location). The Name New Function Block(s) dialog box is displayed. 3. In the Destination text box, enter the IED name or accept the default IED name. 4. Click Finish. The device instance with given name is created in Project tree under the Unassigned category. 5. Drag and drop the logical device instance on to the IED device instance in the Project tree.
9.8.3 To use the File menu method to add/associate logical devices to an IED
1. On the File menu, click New > IEC 61850 Devices. Select a logical device associated to an IED. The Parameters configuration form for the selected logical device appears with the Text Name text box highlighted. 2. In the Tag Name text box, enter the required name of the device or accept the default name.
- 51 - Chapter 9 - Series CEIM with IEC 61850 Configuration
3. In the Item Name text box and enter the name of the entity that this object is associated with in the Enterprise Model Builder hierarchy. 4. In the Description text box and enter the required description for the device. 5. Refer to the Control Building User's Guide and/or the online help to complete configuration data on the Server History, Server Display, QVCS, Control Confirmation and Identification tabs. 6. When you complete entering configuration data, click OK to close the configuration form. The device instance with the given name is created in the Project tree under the Unassigned category. The logical nodes associated with the logical device are created and assigned under the logical device.
Figure 9.13 Logical device instance in Project tree.
7. Drag and drop the logical device instance into the Project tree.
- 52 - Chapter 9 - Series CEIM with IEC 61850 Configuration
Figure 9.14 Logical device instance in the Project tree
TIP Logical devices can also be assigned using information in the next section, “Assigning logical devices.”
9.9 Assigninglogicaldevices
This section describes tasks to assign logical devices to an IED instance. Considerations
l If duplicate address error message appears, refer to the “Checking IED configuration” section for details on changing the device's network node address. The device addresses can be set to the default value of 20.
ATTENTION The number of logical devices that are loaded and logical nodes that are assigned will consume memory and reach the EIM limit. If IEDs have large logical node definitions, we may attain the limit much before the maximum limit number.
- 53 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.9.1 Prerequisites
An EIM block is created in the Project tree, and has an IED instance associated to it.
9.9.2 Toassign logicaldevices toan IEDinstance
1. Click Edit > Execution Environment Assignment or click the in the tool bar. The Execution Environment Assignments dialog box appears. 2. Click the Devices tab. The IEDs in the Project tree are listed. 3. Select the logical device you want to associate to an IED. 4. Verify that the required IED is selected in the Assign To list box. 5. Click Assign→ to assign the selected logical device to the selected IED. 6. Ensure that the logical device is added to the Assigned Modules list box with the assign state
icon . 7. Drag and drop the logical device instance on to the IED device instance in the Project tree. 8. Repeat the above steps to assign other logical devices. 9. Click Close after assigning the required devices.
9.10 To instantiate logical nodes associated with a logical device
Considerations
l Number of logical devices and logical nodes per EIM is about 850.
ATTENTION The number of logical devices that are loaded and logical nodes that are assigned will consume memory and reach the EIM limit. If IEDs have large logical node definitions, we may attain the limit much before the maximum limit number
l Logical nodes cannot be removed from the associated logical devices if they are loaded.
1. In the Project tree, double-click a logical device instance. The Parameters Configuration form appears. 2. In the Logical Nodes tab, select or remove the logical node you want to associate/dissociate with this logical device instance, by clicking on the check box in the Create column.
- 54 - Chapter 9 - Series CEIM with IEC 61850 Configuration
Figure 9.15 List of logical nodes in the Logical Nodes tab
3. Click OK. The selected logical node instances are listed under the logical device instance in the Project tree.
9.11 Checking IED configuration
Considerations
l While the IED is assigned to a PROTOCOL block, it is the offline configuration of a matching physical device that must be connected to this PROTOCOL block.
l Each device on the link must have a unique physical device tag (PD_TAG) that the IEC 61850 system relates to a node address. The physical device tag, node address, and the manufacturer device identifier (DEV_ID) are used to match a configured device to a physical device.
l In the Experion system, each independent component in the control strategy must have a unique tag name (NAME). This is automatically enforced through the Control Builder application. The unique name that was assigned to the device when it was created in Project is also assigned as the device's physical device tag. This is done to assure that the names are unique within the system. This means a change in NAME results in an automatic change in PD_TAG to keep them the same. However, a change in PD_TAG does not result in an automatic change in the assigned NAME.
l While checking the IED configuration, you can only edit the Tag Name, Item Name and Key Description fields.
- 55 - Chapter 9 - Series CEIM with IEC 61850 Configuration
9.11.1 Prerequisites
You have assigned the IED to a PROTOCOL block in the Project tree.
9.11.2 To check IED configuration
1. Double-click the IED icon in the Project tree. The Parameter Configuration form appears with Tag Name highlighted. 2. Accept the assigned name or enter new name, which is unique within the system. 3. In the Item Name text box and enter the name of the entity that this object is associated with in the Enterprise Model Builder hierarchy. 4. In the Key Description text box and enter the required description for the device. 5. Refer to the Control Building User's Guide and/or the online help to complete configuration data on the Server History, Server Display, Control Confirmation and Identification tabs. Refer to the Viewing EIM operation status in the Control Builder section in this document for information on Statistics and Memory tabs. 6. When you complete entering configuration data, click OK to close the Parameter Configuration dialog box.
9.12 ReloadingEIMinstance
Reloading component configuration is required when you make changes to the component or function block configuration, or after you replace a failed IED. You can use the applicable load procedure to reload data to components from the Project or Monitor tab. It is recommended to invoke the following commands through the Controller menu after a reload operation.
l Upload to the Monitoring Database
l Update to Project
Click Yes to proceed with reload.
- 56 - CHAPTER
10 CONFIGURE CONTROL STRATEGIES
This section describes tasks to create a control strategy to control IED parameters through a C300 Controller. The Project Engineer builds a library of the IED blocks in Control Builder. The Project Engineer then creates control strategies that use the instances of the IED blocks. The control strategies and the IED are used to control the IED after they are loaded to the C300 Controller and EIM. You can also configure parameters using the Series C Universal I/O module. For information about configuring strategies using the Series C Universal I/O module, refer to the Control Building User's Guide. Considerations
l The navigation from the hyperlinked parameter is available to a parameter connector, which is for an Input/Output parameter of a block.
l You can navigate to a parameter in other charts that belong to a different controller. Therefore, this navigation improvement can be used to traverse between peer-to-peer connections across controllers.
l In the Project mode, double-click on the parameter to edit the parameter name in the parameter connector. An edit box appears which allows you to change the parameter name.
l If the parameter belongs to a tagged block or a function block within a tagged block that does not exist, you cannot navigate to the source parameter and hence the hyperlink for such parameters does not exist.
l You can write a parameter to an IED only through a PUSH block or SCM block.
l Use the DSIN block to configure any IED device parameter.
l To configure Control Strategy which writes parameters to IED, refer to the Control Building User's Guide.
10.1 Prerequisites
l Control Builder is running and the tree windows are open.
l You have created and loaded a physical device on a C300 Controller. The physical device has associated logical devices and it’s and logical nodes.
l You have created a Control Module to associate the physical device to. Refer to the C300 Controller User's Guide to create a Control Module.
l You have identified the data type of IED data attributes that you want to connect to a Experion block that support the data type.
- 57 - Chapter 10 - Configure control strategies
10.2 To configure Control Strategy which reads parameters from IED using the parameter connector
1. Click the parameter connector button. The pointer turns into a cross-hair. 2. Click on the desired input block pin. 3. Double-click outside the block at the required parameter connector location. The parameter connector appears.
TIP Clicking in different places outside the block symbol results in the parameter connector being placed in different locations. Click once to establish a path to a desired location before double-clicking. Press the ESC key to cancel the operation and start over if required.
4. Use one of the following methods to specify the name of the block connection.
Option Procedure Optio Enter the full name of the desired block connection, including n 1 Control Module, Block Name (Tag), Parameter and then press the ENTER key.
Optio a. Click on the button with the dot leader icon (three dots) to n 2 access the Point Selection dialog. b. Find the desired point name and parameter and then click on Select to insert the specified parameter into the parameter connection field. c. Click Close on the top right-hand corner of the Point Selection dialog box to close the dialog and return to the control drawing.
After you create a parameter connector, the parameter appears as hyperlink. When you click on the hyperlinked parameter with the Control key pressed, the chart/configuration form appears for the tagged block
ATTENTION
- 58 - Chapter 10 - Configure control strategies
EIM with IEC 61850 supports IEC 61850 edition 2 data types. You can read/write parameters from the Project to the IEC 61850 edition 1 data types only. Parameters that have enumeration value beyond 64 have negative values. Perform the following workaround while reading and writing such parameters. Reading negative enumerations 1. Read the value as a large positive value from ERDB. 2. Calculate the negative value. 3. Use the negative integer value in CM.
Example
l IEDvalue =–2
l Block in CM = AUXCALC block
1. Read the IED value as a large positive: 65534 (65536-2)
2. Calculate the negative value using the AUXCALC block, as shown below.
isnan( CM_IEC61850_ENUM.AUXCALC10.C[2] ) ? 0.0 : (CM_IEC61850_ENUM.AUXCALC10.C[2] > 32767) ? CM_IEC61850_ENUM.AUXCALC10.C[2]-65536 : CM_IEC61850_ENUM.AUXCALC10.C[2] The expression appears as follows, in the Control Builder
- 59 - Chapter 10 - Configure control strategies
3. Use the negative integer value in the CM.
Writing negative enumerations 1. Read the negative value. 2. Calculate the negative value to ENUM64. 3. Use the SCM/CAB block to write the ENUM64 value to an IED.
Example
l Control writes
l Configuring MMS Subscriber block reports with DSMAP Block
10.3 Controlwrites
EIM with IEC 61850 supports the control model states defined in the IEC 61850 Specification Part 7.2 (edition 1) to operate on IED data with data attribute having the functional constraint FC. EIM with IEC 61850 supports direct control with normal security (direct-operate) control model. Control Builder supports configuration of control strategies in C300 Controller to write data to IED controllable status and analog data attributes of common data class specifications defined in the IEC 61850 Specification Part 7.2 (edition 1). You can write control data structures that send the control structure format and its data. Any logical node which contains data object with data attribute Oper requires a control write. Considerations
- 60 - Chapter 10 - Configure control strategies
l Experion currently supports direct control with normal security (direct-operate) control model only.
l When a control write is performed, the timestamp is stored/recorded.
l The sequence number increments and is reset/rolls over to 0 when the value crosses 255.
l It is recommended to specify the name of the EIM with IEC 61850 instance in the Modoper_ origin_orident field.
l The Modoper_origin_orident is displayed as an ASCII value, but it is an octet string parameter type.
10.3.1 Prerequisites
l Control Builder is running and the tree windows are open.
l You have created and loaded an IED on an EIM with IEC 61850. The IED has associated logical devices and it's and logical nodes.
l You have created a Control Module to associate the IED to. (Refer to the C300 Controller User's Guide to create a Control Module).
l Do not write the control value from the functional constraint FC tab of the logical node (associated with an IED). When IED control parameters are configured to write from control strategies, it might result in write failures. Special considerations are required to write to IED data attributes that has negative enumerations. Refer the negative enumeration workaround
l Configure IED with a control model from the supported control models and ctlModel. Use 3rd IED configuration or IED front panel display to set the control model.
10.3.2 Toperform a controlwrite
1. Project side configuration of logical node. a. Double-click the required logical node instance The Parameters form appears. b. Configure the mandatory data attributes of the classes having the functional constraint FC of the IED with a control model in Control Builder and load the IED to EIM with IEC 61850.
l Mod_oper_origin_orcat: accept the default value or change the value
l Modoper_origin_orident: accept the default value or change the value
l Mod_oper_test: applicable only test status to test the control model
l Mod_oper_check: synchrocheck/ interlock-check-Applicable for DPC (double-point control) class only
c. Click OK. 2. Writing a control value a. Configure control strategies in C300 Controller to write to IED controllable data attributes of the common data classes to PUSH blocks. for example, CtlVal). b. Configure control strategies in C300 Controller to write to IED controllable data attributes of the common data classes to SCM blocks. The Oper control parameter attributes of the logical device are updated.
- 61 - Chapter 10 - Configure control strategies
ATTENTION The attributes that were set up while configuring the logical node in the Project side are not written to the IED until the CtlVal parameters are written.
3. This results in a change in the output status of an IED connected device, such as a relay or a switch.
ATTENTION If write is not successful due to invalid control model configuration for which IED reject the write, EIM with IEC 61850 reports appropriate error message to C300 Controller. See trouble shooting section for more.
10.4 Configuring MMS Subscriber block reports with DSMAP Block
The DSMAP is a block representation of the subsystem by the same name that takes Subscriber block report data and forwards it to the DS_IN block on a C300. Only when the DS_IN and Subscriber blocks have been associated will the DSMAP appear in the Project Assignment panel of Control Builder. DSMAP is not created but rather a result of the DS_IN setup process. Considerations
l Considerations for Tag Name o Must not exceed 40 characters o Must contain at least one letter (A-Z) o Must not contain an embedded space or leading space
l Considerations for Item Name o Must not exceed 40 characters o Must contain at least one letter (A-Z)
10.4.1 Prerequisites
Control Builder is running and the tree windows are open. You have created and loaded a physical device on C300 controller. You have created a Control Module with which to associate the physical device. Refer to the “C300 Controller User’s Guide” to create a Control Module. You have identified the data type for the IED data attributes that you want to connect to an Experion block. You have created EIM block in project assignment. IED block must exist in Project Assignment. Subscriber block must exist in Project Assignment. C300 Controller must appear in Project Assignment.
- 62 - Chapter 10 - Configure control strategies
10.4.2 To configureDSMAP values
1. Select the subscriber block module properties for EIM by double clicking or right clicking and selecting “Module Properties” in the context menu. 2. On the third tab labeled “Data Set” select the dataset(s) to be subscribed to by clicking the checkbox under the "Associate" column. 3. In Control Builder’s Project Assignment View, create a new Control Module and add it to CEE. 4. Open the Control Module and add the DSIN block(s) in the Library under Dataset. The DSIN block transfers the MMS Report data from the EIM to the C300.
5. Configure the DSIN block by double clicking it or right clicking the DSIN block and selecting “Configure Parameters... DSIN Block Object” from the context menu. You can change the name of the DSIN block if required. Check SHED Hold if required.
CAUTION Once the DSIN Block is created, it cannot be renamed. Renaming the DSIN block, which has connections to other blocks, may cause the other blocks to lose their connections.
6. From here select the second tab labeled “DataSet”.
7. Click the ellipsis “...” button to find the Subscriber block.
8. Select the Subscriber.
9. To finalize the selection after hitting ok, deselect the “DataSet Source Block” textbox.
10. Click the “Populate DataSet” button next to the “DataSet Souce block” textbox that was just filled in.
11. Select one or more required parameters for your control strategy.
12. Click “OK” on the DSIN “Configure Parameters... DSIN Block Object” dialog window or assign Block Pins and Parameter Monitoring as required. If you choose the Block Pins tab, select the Alias (parameter) Name and add as Output. Block pins will appear as output pins on the right- hand-side of the screen. For multiple parameters, repeat Alias Name selection as required. Click “OK.”
- 63 - Chapter 10 - Configure control strategies
13. Save the Control Module (button at the top of the screen) and the DSMAP will now appear under the associated Subscriber block.
TIP You can select multiple data types to populate data sets by pressing and holding shift or control. If you want to modify an alias name, you must modify it under your parameter data set.
- 64 - CHAPTER
11 COMMUNICATION FAILURES AND FIXING COMMON PROBLEMS IN EIM-61850
11.1 EIMcannot communicate with asingle IED
1. In the Monitoring tree, double-click the IED icon in the Project tree. The Parameter Configuration form appears.
2. In the Main tab, verify the following fields:
l In the Device Information section, verify that the Device IP Address IP address listed is the same as the IP address of the physical IED.
l In the IED Information section, verify that the IED information is correct and matches the physical IED.
l In the CID Information section, verify that the CID load status is SUCCESS. The CID load More Info displays an error number if the load of the CID file failed. In a success case this should display 0. Inform the DEE know if any other value is displayed here.
l Verify the number of devices making MMS connections to an IED. If MMS connections are limited, it is possible the IED cannot accept another connection.
- 65 - Chapter 11 - Communication Failures and fixing common problems in EIM-61850
11.2 How to determine the numberof IEDs loadedon the EIM
1. In the Monitoring tree, double-click the required Protocol block. The Protocol Block Parameters form appears. 2. In the Statistics tab, in the IEC 61850 Network section, the Total IEDs field indicates the number of IEDs loaded on the EIM.
11.3 Read and write failures in EIMwith IEC 61850 (EIMto IED)
1. Collect the error code reported in control strategy. 2. Collect EIM and IED communication statistics from Control Builder and from IED local display/configuration tool. 3. For write failures, ensure that the control model is properly configured in the physical device that match with the Control Builder configuration.
TIP For general EIM communication failure cases, consult the Ethernet Interface Module Hardware and Common Platform User’s Guide.
11.4 FixingotherCommon Problems
IED template creation failure The IED template creation fails.
Diagnostic IED template creation fails. Check
Cause Usage of incorrect Data types, usage of data types that are not according to IEC 61850 standards
Solution Correct the data type in the ICD file or contact the IED manufacturer to get the corrected IED ICD file.
- 66 - CHAPTER
12 VIEWING EIM WITH IEC 61850 OPERATION STATUS IN CONTROL BUILDER
The Monitoring tab in Control Builder can be used to view the operation and status of any of the various EIM components represented as icons in the Monitoring tree.
12.1 Statistics tab –Protocol block
The Statistics tab shows messages details exchanged between the EIM and the IED. The following table summarizes the parameter data you can monitor and/or configure on the Statistics tab of the configuration form for the selected Protocol block.
Plain Text Parameter Name User Notes Configurable Statistics
Reset All STATSRESET No Button to initiate reset in Statistics Monitoring mode.
Notification Statistics
Notifications NUMNTFRQUAVG No The number of Notification Rate Requests per second average.
Maximum NUMNTFRQUMAX No The number of Notification Notifications Requests per second Rate maximum.
Responder Statistics
Total NUMPARRSPAVG No The average number of Responder parameter get/store Rate responses per second.
Maximum NUMPARRSPMAX No The maximum number of Total parameter get/store Responder responses per second. Rate
Peer CPEERAVGPPS [ ] No The average number of peer Responder parameters per second Rate processed by the IEC61850LINK.
- 67 - Chapter 12 - Viewing EIM with IEC 61850 operation status in Control Builder
Plain Text Parameter Name User Notes Configurable Maximum CPEERMAXPPS [ No The maximum number of Peer ] peer parameters per second Responder processed by the Rate IEC61850LINK.
Display CDISPAVGPPS [ ] No The average number of Responder display peer parameters per Rate second processed by the IEC61850LINK.
Maximum CDISPMAXPPS [ ] No The maximum number of Display display peer parameters per Responder second processed by the Rate IEC61850LINK.
IEC 61850 Network
Total IEDs NUMIEDS No The number of IEDs configured in an IEC 61850 network per second.
MMS Request MMSRPS No The number of data sets read Rate operations between IEC61850M and IED per second.
MMS Store MMSSTORERPS No The number of read Rate operations between IEC61850M and IED per second.
12.2 Memory tab–Protocolblock
The Memory tab contains data on general memory usage in the EIM. It also shows memory usage parameters in terms of internal memory units: descriptors and blocks. The following table summarizes the parameter data you can monitor on the Memory tab of the configuration form for the selected Protocol block.
Plain Text Parameter Name User Notes Configurable Memory Usage in KBytes
Total User TOTALMEMINK No Shows the total size of user Memory(kb) memory pool, in kilobytes.
Currently USEDMEMINK No The total amount of used Used memory in user memory Memory(kb) pool, in kilobytes.
- 68 - Chapter 12 - Viewing EIM with IEC 61850 operation status in Control Builder
Plain Text Parameter Name User Notes Configurable Currently FREEMEMINK No Amount of free memory in Free user memory pool, in Memory(kb) kilobytes.
Largest MAXFREEINK No The size of largest contiguous Free memory block in user Memory memory pool, in kilobytes. Block Size (kb)
Memory Usage in Bytes
Total User TOTALMEM No Total size of user memory Memory(b) pool, in bytes.
Currently USEDMEM No Total amount of used Used memory in user memory Memory(b) pool, in bytes.
Currently FREEMEM No Current amount of free Free memory in user memory Memory(b) pool, in bytes.
Largest MAXFREEBLKSZ No Shows size of largest Free contiguous memory block in Memory user memory pool, in bytes. Block Size (b)
Memory Descriptors
Total NTOTMEMDESC No Total number of memory Memory descriptors available. Descriptors
Free NUMFREEDESC No Number of free (available) Memory memory descriptors. Descriptors
Registered NUMREGDESC No Number of registered Memory memory descriptors. Descriptors
Used NUMUSEDDESC No Number of used memory Memory descriptors. Descriptors
Memory Blocks
Used NUMUSEDBLKS No Number of used memory Memory blocks. Blocks
- 69 - Chapter 12 - Viewing EIM with IEC 61850 operation status in Control Builder
Plain Text Parameter Name User Notes Configurable Free NUMFREEBLKS No Number of free (available) Memory memory blocks. Blocks
External NUMEXTBLKS No Number of external memory Memory blocks. Blocks
Driver Memory Usage
Reserved DRVMEMRESERVED No The amount of reserved (kb) memory in kilobytes for EIM hardware.
Used (kb) No The amount of memory in kilobytes used by the EIM hardware.
Free (kb) No The amount of memory in kilobytes available for EIM hardware. (The value is calculated by Memory pools free + DRVMEMRESERVED – Pools RAM used).
Fragmented No Free (kb)
Largest No Free(kb)
Free No Fragment Count
12.3 Statisticstab–IEDblock
The Statistics tab shows the response details of an IED during its interaction with EIM.
Plain Text Parameter User Notes Name Configurable Statistics
Reset All STATSRESET No Button to initiate reset in Statistics Monitoring mode.
IEC 61850 Comm Performance
Average RESPTIMEAVG No The average response time of an
- 70 - Chapter 12 - Viewing EIM with IEC 61850 operation status in Control Builder
Plain Text Parameter User Notes Name Configurable Response IED to a request sent from an Time (ms) EIM.
Fastest RESPTIMEMIN No The number of data sets read Response operations between an EIM and Time (ms) IED per second.
Slowest RESPTIMEMAX No The number of read operations Response between an EIM and IED per Time (ms) second.
- 71 - CHAPTER
13 EIM WITH IEC 61850 OPERATION
This section includes information specific to using the EIM with IEC 61850 protocol. For more operation information and behaviors which characterize the EIM Platform and are common across the different EIM downlink protocols, see the EIM Hardware and Common Platform User’s Guide. These common characteristics include faceplate displays and indications, startup, shutdown, using station displays, EIM overload, bulk configuration tools, viewing EIM platform operation status in Control Builder and commands including EIM synchronization, become primary, and switchover.
- 72 - CHAPTER
14 CONTROL BUILDER BLOCK ICON DESCRIPTIONS FOR EIM WITH IEC 61850
Adding an EIM block (non-redundant or redundant) to the Control Builder Project tab results in the appearance of an icon that represents a single EIM or redundant controller pair. Once the EIM block is loaded, the EIM icon appears in the Monitoring tab. When a single EIM is defined, the icon appears as a single icon. When a redundant EIM is defined, two icons appear, one representing the primary on the left and the icon representing the secondary on the right. The appearance of either icon on top in a redundant controller pair indicates the active controller. The following table shows the various appearances that the EIM block icon assumes based on its current state and status in IEC 61850 protocol.
Table 14.1 EIM with IEC 61850 icon indications in Control Builder Icon Represents . . . EIM state Project Tab
EIM configured for non-redundant operation. N/A
(gray) EIM Primary configured for redundant N/A operation. (gray & white) EIM Secondary configured for redundant N/A operation. (white & gray) Monitor Tab
EIM is non-redundant and not communicating No Communication (red) (Offnet)
Primary EIM is not communicating. No Communication (red & white) (Offnet)
Secondary EIM is not communicating. No Communication (white & red)
- 73 - Chapter 14 - Control Builder block icon descriptions for EIM with IEC 61850
Icon Represents . . . EIM state (Offnet)
EIM is non-redundant No Database
(yellow) Primary EIM is not synchronized and partner No Database EIM is visible (yellow & yellow) Primary EIM is not synchronized and partner No Database EIM is absent or incompatible (yellow & shadow) EIM is non-redundant Run or OK
(green) Primary EIM is synchronized Run or OK
(green & white) Primary EIM, standby synchronization Run or OK
(green & white, pause) Primary EIM is not synchronized and partner Run or OK EIM is visible (green & yellow) Primary EIM is not synchronized and partner Run or OK EIM is absent or incompatible (green & shadow) Secondary EIM is synchronized Backup
(white & green) Secondary EIM, standby synchronization Backup
(white & green, pause)
Secondary EIM is not synchronized and Backup partner EIM is visible (yellow &
- 74 - Chapter 14 - Control Builder block icon descriptions for EIM with IEC 61850
Icon Represents . . . EIM state yellow) Secondary EIM is not synchronized and Backup partner EIM is absent or incompatible. (shadow & yellow) EIM is non-redundant Run Soft Fail or OK Soft Fail (green) Primary EIM is synchronized Run Soft Fail or OK Soft Fail (green & white) Primary EIM, standby synchronization Run Soft Fail or OK Soft Fail (green & white, pause) Primary EIM is not synchronized and partner Run Soft Fail or EIM is visible OK Soft Fail (green & yellow) Primary EIM is not synchronized and partner Run Soft Fail or EIM is absent or incompatible OK Soft Fail (green & shadow) Secondary EIM is synchronized Backup Soft Fail
(white & green) Secondary EIM, standby synchronization Backup Soft Fail
(white & green, pause)
Secondary EIM is not synchronized and Backup Soft Fail partner EIM is visible partner present. (yellow & yellow) Secondary EIM is not synchronized and Backup Soft Fail partner EIM is absent or incompatible (shadow & yellow)
- 75 - CHAPTER
15 CONTROL BUILDER BLOCK ICON DESCRIPTIONS FOR EIM WITH IEC 61850 PROTOCOL BLOCK
Creating and assigning an instance of the IEC 61850 PROTOCOL block under the EIM on the project side in Control Builder results in the appearance of the PROTOCOL block (“PB_61850” )icon. The following table shows the various appearances that the PROTOCOL block (PB_61850) icon assumes in the project and monitoring tree, based on its current state and status.
Table 15.1 EIM with IEC 61850PROTOCOL block icon indications in Control Builder Icon Represents . . .
..(gray) Project side icon
..(red) Error in monitoring side
..(green) Online
..(blue) Idle
..(yellow) Not synchronized
..(red) Offline
- 76 - CHAPTER
16 CONTROL BUILDER BLOCK ICON DESCRIPTIONS FOR EIM WITH IEC 61850 MMS SUBSCRIBER BLOCK
Adding an MMS Subscriber block to a PB_61850 block on the project side in Control Builder results in the appearance of the MMS Subscriber block icon. The following table shows the various appearances that the MMS Subscriber block icon assumes based on its current state and status.
Table 16.1 EIM with IEC 61850 MMS Subscriber block icon indications in Control Builder Icon Represents . . . Project Tab
MMS Subscriber block project side
..(gray) Error in Monitoring Side
..(red) Inactive
..(blue) Fail
..(red) Active
- 77 - Chapter 16 - Control Builder block icon descriptions for EIM with IEC 61850 MMS Subscriber block
Icon Represents . . . ..(green) Active with error
Active with synchronization fail
- 78 - CHAPTER
17 CONTROL BUILDER BLOCK ICON DESCRIPTIONS FOR EIM WITH IEC 61850 DSMAP BLOCK
Creating a DSMAP instance under the MMS Subscriber block on the project side in Control Builder results in the appearance of the DSMAP block icon. The following table shows the various appearances that the DSMAP block icon assumes based on its current state and status.
Table 17.1 EIM with IEC 61850DSMAP block icon indications in Control Builder Icon Represents . . . Project Tab
DSMAP Project side icon
..(gray) Error in monitoring side
..(red) Inactive
..(blue) Active
..(green)
- 79 - Notices Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intention of trademark infringement. Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The third party materials may be subject to licenses, notices, restrictions and obligations imposed by the licensor. The licenses, notices, restrictions and obligations, if any, may be found in the materials accompanying the product, in the documents or files accompanying such third party materials, in a file named third_party_licenses on the media containing the product, or at http://www.honeywell.com/ps/thirdpartylicenses. Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website at: http://www.honeywellprocess.com/support If you have comments about Honeywell Process Solutions documentation, send your feedback to: [email protected] Use this email address to provide feedback, or to report errors and omissions in the documentation. For immediate help with a technical problem, contact your local Honeywell Technical Assistance Center (TAC). How to report a security vulnerability
For the purpose of submission, a security vulnerability is defined as a software defect or weakness that can be exploited to reduce the operational or security capabilities of the software. Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services. To report a potential security vulnerability against any Honeywell product, please follow the instructions at: https://www.honeywell.com/product-security Support
For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find your local CCC visit the website, https://www.honeywellprocess.com/en-US/contact- us/customer-support-contacts/Pages/default.aspx. Training classes
Honeywell holds technical training classes that are taught by process control systems experts. For more information about these classes, contact your Honeywell representative, or see http://www.automationcollege.com.
- 80 -