eim with iec 61850 user's guide-epdoc-x462-en-520a

Experion PKSRelease 520

Ethernet Interface Module with IEC 61850 User's Guide

EPDOC-X462-en-520A

June 2021

DISCLAIMERThis document contains Honeywell proprietary information. Information contained herein is to be usedsolely 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 theimplied warranties of merchantability and fitness for a purpose and makes no express warrantiesexcept 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. Theinformation and specifications in this document are subject to change without notice.

Copyright 2021 - Honeywell International Sàrl

- 2 -

CONTENTS

Chapter 1 - About this document 7

1.1 Intended audience 7

1.2 Prerequisite skill 7

1.3 Related documents 7

Chapter 2 - Introduction 9

Chapter 3 - About IEC 61850 10

3.1 About IEC 61850 protocol 10

3.2 IEC 61850 features 10

Chapter 4 - EIM terms and definitions 11

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 controlintegration 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 andevents server 21

Chapter 9 - Series C EIM with IEC 61850 Configuration 22

9.1 EIM Configuration rules-with IEC 61850 22

9.1.1 EIM with IEC 61850 Capacity 23

9.2 Initial load order guidelines 23

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.2 To create a template 29

9.4.3 To recreate a missing logical device template 33

- 3 -

9.5 Creating and configuring an IED 37

9.5.1 To create an IED instance 38

9.6 Editing IED block parameters 41


9.6.2 To edit IED block parameters 42

9.7 Adding or associating MMS Report Control blocks to an IED 43


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 50

9.7.6 Delete MMS Subscriber block from Monitor tree 51

9.8 Adding or associating logical devices to an IED 51


9.8.2 To use drag and drop method to add/associate logical devices to an IED 52

9.8.3 To use the File menu method to add/associate logical devices to an IED 52

9.9 Assigning logical devices 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.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 IEDusing the parameter connector 58

10.3 Control writes 60


10.3.2 To perform a control write 61

10.4 Configuring MMS Subscriber block reports with DSMAP Block 62


10.4.2 To configure DSMAP values 62

Chapter 11 - Communication Failures and fixing commonproblems in EIM-61850 68

- 4 -

11.1 EIM cannot communicate with a single IED 68

11.2 How to determine the number of IEDs loaded on the EIM 68

11.3 Read and write failures in EIM with IEC 61850 (EIM to IED) 69

11.4 Fixing other Common Problems 69

Chapter 12 - Viewing EIM with IEC 61850 operation status inControl Builder 70

12.1 Statistics tab –Protocol block 70

12.2 Memory tab –Protocol block 71

12.3 Statistics tab – IED block 72

Chapter 13 - EIM with IEC 61850 operation 74

Chapter 14 - Control Builder block icon descriptions for EIMwith IEC 61850 75

Chapter 15 - Control Builder block icon descriptions for EIMwith IEC 61850 PROTOCOL block 80

Chapter 16 - Control Builder block icon descriptions for EIMwith IEC 61850 MMS Subscriber block 82

Chapter 17 - Control Builder block icon descriptions for EIMwith IEC 61850 DSMAP block 84

- 5 -

ABOUT THIS DOCUMENT

Revision Date Description

A June 2021 Initial release of the document

This document provides information about planning, installing, configuring and operating the hardwareand software components associated with the EIM with IEC 61850 Interface Module.

1.1 Intended audience

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 skill

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.

- 7 -

CHAPTER

1

Document Description

Overview Provides a comprehensive overview of Experion,including basic concepts and terminology.

Control BuildingUser's Guide

Describes how to perform tasks within the ControlBuilder application such as configuring hardwaredevices, continuous control strategies, and sequentialcontrol strategies.

C300 ControllerUser’s Guide

Provides information for planning, designing,installing, operating and troubleshooting C300process controllers in an Experion system.

Control HardwarePlanning Guide

Provides an overview of things you should considerwhen planning for the installation of your Series Ccabinet.

Ethernet InterfaceModule Hardware andCommon PlatformUser’s Guide

Provides information about the Series C EIM moduleand its operation irrespective of a specific protocol.

- 8 -

Chapter 1 - About this document

INTRODUCTION

This section provides information about IEC 61850 control integration you must know beforeintroducing it in an Experion network. For more information about the Ethernet Interface Module and itsgeneral operations, irrespective of a specific protocol, please see the Ethernet Interface ModuleHardware and Common Platform User’s Guide.

- 9 -

CHAPTER

2

ABOUT IEC 61850

This section gives an overview of the IEC 61850 protocol. It also lists the available IEC 61850standards.

3.1 About IEC 61850 protocol

IEC 61850 is a global standard for the design of electrical substation automation. IEC 61850 is a part ofthe International Electrotechnical Commission's (IEC) technical committee reference architecture forelectric power systems. It enables the integration of protection, metering, monitoring and controlfunctions 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 toobtain 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 IEC 61850 features

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 forremoving the older devices.

l Supports large number of diagnostic parameters.

l Reduces costs of installation, commissioning and maintenance.

- 10 -

CHAPTER

3

http://www.iec.ch/

EIM TERMS AND DEFINITIONS

This section provides information about the terms and definitions associated with EIM used in thisdocument.

Term Definition

CDA Control Data Access The application layer protocol used for native communicationwithin Experion. It supports both parameter access response messaging andnotification messaging.

CIP Common Industrial Protocol The Common Industrial Protocol is used for industrialautomation applications. CIP provides a comprehensive suite of data communicationservices for manufacturing automation applications.

Client That node or device in a communication relationship which initiates requests toanother node or device, called the Server. Client – Server relationships exist inseveral contexts that apply to EIM operation. This is true of uplink communications aswell as downlink communications.

Dual home Dual-home/ dual homing is a network topology where a network device is built withmore than one network interface.

EIM Ethernet Interface Module

EtherNet/IP™ Ethernet Industrial Protocol EtherNet/IP is an industrial network protocol that adaptsthe Common Industrial Protocol to standard Ethernet. It is widely used in a range ofindustries including factory, hybrid and process. The EtherNet/IP and CIPtechnologies are managed by ODVA (Open DeviceNet Vendors Association).

FirmwareManagerTool

An HMI tool, newly introduced into Experion R501, which supports the download offirmware images to the EIM as well as the upload of diagnostic information from theEIM. The Firmware Manager Tools is compatible with the EIM’s communicationtechnology whereas the Series C “CTools” tool is not.

FTE Fault Tolerant Ethernet FTE is the Ethernet-based, redundant control network ofExperion.

HSR High Availability Seamless Redundancy High Availability Seamless Redundancyprotocol is a refinement of PRP standardized in IEC 62439-3 clause 5 which isspecific to ring topologies and provides zero switch-over time. HSR is one of 3possible 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 systemsestablished by the International Electrotechnical Commission's (IEC). The standardmaps to multiple protocols include MMS (Manufacturing Message Specification) andGOOSE (Generic Object Oriented Substation Event).

NTP Network Time Protocol NTP is a standardized internet networking protocol used forsynchronizing computer clock times in a distributed network of computers. On the FTEuplink, the EIM supports time synchronization by NTP or PTP.

- 11 -

CHAPTER

4

Term Definition

PlatformBlock

The object at the top of the EIM’s data organization hierarchy. It presents CDAparameters which allow for the configuration of EIM properties common to allsupported downlink protocols. It presents system operational parameters which allowfor the control of key behaviors such as redundancy. It also presents statisticalparameters which allow for the view of runtime performance metrics.

ProtocolBlock

The object at the second level in the EIM’s data organization which presentsinformation specific to the supported downlink protocol as CDA parameters. Thisincludes statistical parameters and in some cases may also include configurationparameters. In R501, the EIM supports two alternate protocol blocks: the IEC 61850protocol block and the EIP protocol block.

PRP Parallel Redundancy Protocol PRP provides layer 2 network redundancy by sendingtwo copies of the same frame over two independent networks. A Redundancy ControlTrailer (RCT) is added to each frame (which includes a sequence number to supportdetection of duplicate messages so that one may be discarded.) It supports zeroswitchover time. PRP is one of 3 possible downlink network redundancy optionsconfigured on the EIM platform block. PRP is used only with the IEC 61850 EIMapplication image.

PTP Precision Time Protocol PTP is a standardized internet networking protocol used forsynchronizing computer clock times in a distributed network of computers. PRPprovides higher precision than NTP. On the FTE uplink, the EIM supports timesynchronization by NTP or PTP.

SAS Safety and Automation System A term used to describe both the Safety InstrumentedSystem and Process Control System taken together as a component of theautomation architecture of a manufacturing or production site. The process controlsystem is composed of a basic process control system which can include subsystemsrelated to power distribution and management as well as process control. The powermanagement system is responsible for load shed control.

Server That node or device in a communication relationship which responds to requestsinitiated by another node or device, called the Client. Client – Server relationshipsexist in several contexts that apply to EIM operation. This is true of uplinkcommunications as well as downlink communications.

- 12 -

Chapter 4 - EIM terms and definitions

IEC 61850 NETWORK DEVICE AND IEDSUPPORT POLICY

EIM supports IEC 61850 complaint switches and IEC 61850 edition 1 and edition 2- compliant IEDs. Itcan connect to any IEC 61850 complaint switch using Redbox. Honeywell is not restricting users toIEDs or device types.

Following is a list of network switches and IED devices used by Honeywell for EIM integration andqualification, for your reference.

Honeywell does not restrict users to any particular IED vendors or types or IEC 61850 compliantswitches.

- 13 -

CHAPTER

5

Device/switch model Vendor

IEC61850edition

Communication ports

REU615-A (Voltageprotection and Control)

ABB 1 Dual RJ45 ports formaking HSR ring andsingle optic fibre port

RET615-D (Transformerprotection and Control)

ABB 1 Single RJ45 port andconnect throughRedbox to be part ofHSR ring or PRPnetwork

REF620-A (feederprotection and Control)

ABB 1 Dual RJ45 ports formaking HSR ring andsingle optic fibre port

REM615-A (Motorprotection and Control)


REF615A (feederprotection)


RSP25 Hirschman N/A Redbox

PT-G503-PHR-PTP-HV MOXA N/A Redbox

PT7528 MOXA N/A IEC 61850 compliantswitch

GE Multilin M60 – MotorProtection System

GE N/A IEC 61850 compliantswitch

SEL 787 – TransformerProtection Relay

l SiemensSepamSeries

l

Schneider

N/A IEC 61850 compliantswitch

SIPROTEC 7SJ82 – Over Siemens 1 Dual RJ45 ports

- 14 -

Chapter 5 - IEC61850 network device and IED support policy

Chapter 5 - IEC61850 network device and IED support policy

Device/switch model Vendor

IEC61850edition

Communication ports

current protection Configurable for PRPcommunication or HSRring communication

SIPROTEC 7SJ84 – Overcurrent protection

Siemens 1 Dual RJ45 ports.Configurable for PRPcommunication or HSRring communication

Multilin F35 – Feederprotection System

GE 1 Dual RJ45 ports.Configurable for PRPcommunication or HSRring communication

SEL-451 ProtectionAutomation Control

SEL-451ProtectionAutomationControl

1 Dual RJ45 ports.Configurable for PRPcommunication or HSRring communication

REF615A(feederprotection)

ABB 2 Dual optical fiberEthernet ports andConfigurable for PRPcommunication or HSRring communication

Dual optical fiber Ethernetports and Configurable forPRP communication orHSR ring communication

ABB 2 Dual optical fiberEthernet ports andConfigurable for PRPcommunication or HSRring communication

- 15 -

IEC 61850 CONTROL INTEGRATIONTOPOLOGIES

This section provides information about the different topologies for IEC 61850 control integration.

6.1 Network recommendations for creating IEC 61850 controlintegration topologies

l The IEC 61850 network should not be directly connected to an L3 router. If access to L3 isrequired, it is recommended to use an L 2.5 router to connect FTE and IEC 61850 networkstogether. 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 theSCADA Server:

o Ensure lower MAC address is selected for FTE network installation. If Experion isinstalled 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 networkconnections. If you have additional dual NICs on 2 NIC built-in type servers, ensure thatlower MAC address NIC is selected for FTE. With this setup, Experion installationautomatically selects the lower MAC interfaces ( 1st two interface of built-in NICs) for FTEand 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 eitherinterface, 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.

6.2 HSR topology model

This diagram portrays the HSR ring topology configuration for the various physical components for anEIM with IEC 61850 and the related Experion L2 nodes, L1 embedded nodes, FTE and IEC 61850network equipment.

TIP

Non-Redundant EIM is shown here, but a Redundant EIM can be used with a non-redundantnetwork as well

- 16 -

CHAPTER

6

Figure 6.1 HSR topology model

The following is a simple IEC 62439 High-availability Seamless Redundancy (HSR) Ring topologyexample.

- 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 componentsfor an EIM with IEC 61850 and the related Experion L2 nodes, L1 embedded nodes, FTE and IEC61850 network equipment. This is a simple IEC 62439 Parallel Redundancy Protocol (PRP) topologyexample.

- 18 -

Figure 6.3 PRP topology model

- 19 -


DUAL HOME CONFIGURATIONS FORSCADA SERVER

For information about IEC61850 SCADA, refer to the ILMS solution which supports PRP and HSRdrivers.

- 20 -

CHAPTER

7

IEC 61850 SCADA SERVER ACTING ASALARM AND EVENTS SERVER

The IEC 61850 SCADA server supports configuration of events and alarms. For information aboutconfiguring events and alarms, refer to the IEC 61850 SCADA Configuration Reference document inthe Experion User Assistance library.

- 21 -

CHAPTER

8

SERIES C EIM WITH IEC 61850CONFIGURATION

This section includes the tasks associated with configuring EIM with IEC 61850.

That includes information and tasks associated with Control Builder creation, configuration and loadingof 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 tocreate an EIM block in Control Builder. Creating an EIM is not protocol-specific. The hardware andcommon 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, navigatingand interacting with the application. Also, note that menus, selections, tree views, and configurationforms 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

9.1 EIM Configuration rules-with IEC 61850

o The EIM with IEC 61850 supports CDA P2P connections with the C300 controller and alsoPCNT02 version C300 controller with Enhanced Functionality.

- 22 -

CHAPTER

9

o The EIM with IEC 61850 supports DSIN Block connections only with the PCNT02 version C300controller.

o Each EIM supports 2 downlink connection to an IEC 61850 Network. For IEC62439 HSR RingNetworks or PRP Networks, each EIM should be connected to HSR ring in series or to both sidesof the PRP network. For connections to a non-redundant IEC 61850 network, the EIM can beconfigured to turn off HSR/PRP and only use the single LAN A port.

o The Ethernet Subnet Domain used for the IEC 61850 network must be configured to be a separateSubnet Domain from the FTE Network that the IEC 61850 Interface Module is connected to.

o If the IEC 61850 Network must be connected to L3 (Not Recommended), it is suggested that anL2.5 Router(s) (not shown) be placed between the L3 Router and the IEC 61850 Network and thenthe L2.5 router connected to L3. If routing to the FTE Network from the IEC 61850 network isrequired, the FTE Network could also be connected to this L2.5 Router and ACLs be configured toseverely limit the required traffic to only the nodes & protocols required.

o The Series C EIM with IEC 61850 does not support retention restart or checkpoint restore. All IEDblocks and related configuration must be reloaded from Control Builder, after a non-redundantEIM-61850, or both devices within a redundant EIM-61850, pair are restarted.

9.1.1 EIM with IEC 61850 Capacity

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 1EIM

Maximum Number of EIMs per C300 5 EIM peer connections to 1C300

Maximum Number of connected IEDs per EIM 64 IEDs(2)

Maximum Number of IEDs resident on an IEC61850Network

unlimited IEDs

Notes

(1) A single Experion server with its associated stations and controllers is referred to as a cluster orExperion cluster

(2) Physical IED Nodes with a unique IP Address on the IEC61850 network with reference blocksloaded to a single EIM

9.2 Initial load order guidelines

Perform the initial load of control strategy components from the Project view in the following order tominimize possible load interaction generated error messages.

Order Component

1 IEC61850M

2 IEC61850LINK

Table 9.1 Initial load order guidelines

- 23 -

Chapter 9 - Series C EIM with IEC 61850 Configuration


Order Component

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 thedownlink. To create an instance of the IEC 61850 Protocol, user has to open the configuration form forthe EIM instance. On the Main tab there is a Protocols grid available. The grid will list all the protocolssupported by EIM. In the R501 release, EIM will support only EtherNet/IP and IEC 61850 based MMSprotocols.

Considerations

l Click the + sign in front of the EIM icon to open its directory tree and represent its icons. With theHierarchal Building license option, you must have the Assignment View active to view EIM and itsPROTOCOL blocks.

l In a redundant EIM, the PROTOCOL blocks are shown with the primary EIM block only.

l Considerations for Tag Nameo 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 Nameo Must not exceed 40 characters


9.3.1 Prerequisites

You have added an EIM block to the Project tree.

- 24 -

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 EIMParameters form is displayed, with the Tag Name text box highlighted. Enter the preferred blocktag 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 EnterpriseModel Builder hierarchy.

3. In the Description text box, and enter the preferred description. The description appears in thedetail displays and group displays associated with this block. Note that the Description text box isunder 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 onthe Server History, Server Display, Control Confirmation, and Identification tabs. Refer to the “EIMoperation status in Control Builder” in the Operations section of the EIM Hardware and CommonPlatform 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 -



7. An instance of the IEC 61850 protocol block will be created and assigned under the EIM in theproject tree. Note that IEC 61850 Protocol cannot be supported on an EIM with EtherNet/IPProtocol. The system will restrict the user from creating and assigning an IEC 61850 protocolinstance on an EIM that already has an instance of EtherNet/IP protocol assigned to it.

- 26 -

9.3.3 Load IEC 61850 Protocol Block

To load an instance of the IEC61850 Protocol Block, select the EIM and perform the load operation for theEIM. The load of the EIM will add the protocol block instance to the load dialog. The protocol instancesconfiguration will be loaded to the EIM hardware along with the EIM instance.

9.3.4 Delete IEC 61850 Protocol Block

l Delete from Project Tree: To delete an instance of the IEC61850 Protocol block from the projecttree, open the configuration form of the EIM and uncheck the the IEC 61850 protocol option in thegrid 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 monitortree, delete the EIM from the monitor tree. This behavior is similar to the delete of CEE blocks fromC300.

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/CIDfiles. This section also describes tasks to recreate missing logical device(s) templates. You can recreate

- 27 -



missing logical device(s) templates by selecting the missing logical device(s) from the ICD/CID file inthe 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: <UserSelectedDirectory>\Third Party

Files\SCL files\

l You need not perform this task if a block for the given device type already exists in the ControlBuilder Library database.

l It is recommended to use the ICD files for template creation. If you use ICD/CID file, you haveensure 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 ofcharacters allowed for Library name in Control Builder.

o According to Control Builder tag naming criteria, the following characters are not allowedfor 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 amandatory field.

o The logical device template name displayed in the library tree is formed as <TemplatePrefix> <InstName attribute of LDevice> is a numeric value starting from 1. For example,the device type is IED670 and the logical device instance name is EF4_1, then the logicaldevice template name is formed as IED670_1_EF4_1.

o Maximum number of characters allowed for vendor template in Control Builder is 16.Hence, to accommodate the above naming schema, maximum number of charactersallowed for device type is 6.

o According to the Control Builder tag naming criteria, following characters are not allowedfor Device Type field. `~!@#$%^&*+-=(){}[]|\\:;'<>,.?/ \"\t

9.4.1 Prerequisites

You must have the ICD/CID file for the IED device from vendor's IED configuration tool.

- 28 -

9.4.2 To create a template

1. You can open the IEC 61850IED Device Description Import dialog box in one of the followingways.

Option Description

IEC 61850IED DeviceDescription Import icon

In the Control Builder, click on the IEC

61850IED Device Description Importicon.

From the File menu On the File menu, click New > Type > IEC61850 Device.

The IEC 61850IED Device Description Import dialog box appears.

Figure 9.2 IEC 61850 Device Type dialog box

2. Click to browse for the applicable ICD/CID file, and navigate to the location of the required file.

These files are saved in the following location. Ensure that this folder or sub-folder is NOTexcluded from virus scanning.

After the ICD/CID file is selected, the details of the manufacturer and the device type are displayedin the Device Information section.

- 29 -



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.

4. Click Create.

The creation of logical device templates of an IED in the Control Builder library begins. Theprogress bar displays the current status of logical device template creation. The Status fielddisplays one of the following status during template creation.

- 30 -

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 theuser

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 devicesand logical nodes are listed. The logical nodes associated with the logical devices are listed undertheir respective logical device template.

- 31 -



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 forthe logical devices. All the IEC 61850 logical devices are listed in the File >New >IEC 61850Devices menu.

- 32 -

Figure 9.4 Logical devices and logical nodes in File menu

9.4.3 To recreate a missing logical device 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 -



2. Click to browse for the ICD/CID file, and navigate to the location of the file which contains thedefinition of the missing logical device(s).

These files are saved in the following location. Ensure that this folder or sub-folder is NOT excludedfrom virus scanning.

After the ICD/CID file is selected, the details of the manufacturer and the device type are displayedin 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 -

4. Click Create.

The Device already exists dialog box appears. The missing logical devices are listed in theMissing Devices column.

- 35 -



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 -

9.5 Creating and configuring an IED

This section includes task to create an instance of Intelligent Electronic Device (IED) and add it to theProject tree.

An IED instance can also be created from the Library by dragging and dropping an IED instance to theProject tree.

Considerations

Ensure that an approved antivirus application is installed on the node used to import ICD/CID files.

- 37 -



9.5.1 To create an IED instance

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 EnterpriseModel Builder hierarchy.

4. In the Keyword Description text box, enter the preferred description. The description appears in thedetail 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. Drag and drop the IED instance under the Unassigned tree to the PROTOCOL Block instance inthe 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 logicalnodes associated with a logical device.”

- 38 -

8. Associate an ICD/CID file to the IED instance.

a. Right-click an IED instance (assigned to a PROTOCOL Block), and choose AssociateICD/CID.

The Associate ICD/CID-<IED name> dialog box appears.

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.

These files are saved in the following location. Ensure that this folder or sub-folder is NOTexcluded from virus scanning.

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 -



d. Select the IED you want to associate to this IED instance by clicking the check box in theSelect column, and click OK.

l The Select Configuration form associated ICD/CID file is configured on IED instance. Allrelated 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 LogicalDevice Information sections display the information of associated ICD/CID file, as shown in thefigure.

l The Assigned Instances column in the Logical Device Information section displays theassigned logical device to that IED.

Figure 9.9 ICD/CID file association details in the Main tab

- 40 -

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 anIED instance.

Considerations

l You cannot reconfigure IED with a ICD/CID file of different IED name or IP address or IED type ifthe 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 ifthe IED is loaded.

l If you have the modified version of an ICD/CID file which is compatible with an IED instance, youcan 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 Librarytree. ()

- 41 -



9.6.2 To edit IED block parameters

1. Right-click the IED instance (assigned to an IEC61850LINK), and choose Associate ICD/CID.

The Associate ICD/CID-<IED name> dialog box appears.

2. You can edit the IED block parameters using one of the following methods.

Option Description

Associate anew ICD/CIDfile

Go To Step 3 When you associate a new ICD/CID file,the existing IED block parameters are replaced with thenew IED block parameters.

ReconfigureIED blockparameters

a. Click the Reset button. The following messageappears after all the IEDs are successfullyremoved.

Figure 9.10 Message displayed after successful reset

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, andnavigate to the location of the required file.

These files are saved in the following location. Ensure that this folder or sub-folder is NOT excludedfrom virus scanning.

4. Select the required file and click Open.

The list of available IEDs are listed in the Available IEDs section.

- 42 -

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 theSelect 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

9.7 Adding or associating MMS Report Control blocks to anIED

To represent an MMS Report in Control Builder, an instance of the MMSSUBS need to be created andassociated with an MMS Report.

9.7.1 Prerequisites

- 43 -



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 oneinstance should be available.

l IED must be created and configured.

9.7.2 Steps to create MMS Report instance

1. To create an MMS Report instance, open the configuration form of an IED instance that has beenconfigured with a CID/ICD file. Double click on the IED block. Below is the Configuration form of aconfigured IED instance. You can rename the block and add configuration details. Refer to theControl 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 thenassociated again.

If you change the name in Subscriber block, but the block is already associated withDSIN block, then you must also double click and change the name in the DSIN block.

- 44 -

2. Navigate to the “Subscriber Blocks” Tab. See the list of the MMS Report read from the CID/ICD. TheMMS Report grid will list the MMS Reports. Following is an example of the IED Subscriber Blockstab.

3. The grid has various columns that represent the different attributes of the ReportControl read fromthe IED configuration file. The below table describes the columns and the mapping to theReportControl attributes.

- 45 -



4. To create MMS Report instance representation in Control Builder, select the “Associate” check boxfor the MMS Report that need to be instantiated.

5. Click on OK to save the changes. An instance of MMSSUBS will be created and assigned to theIED.

- 46 -

9.7.3 Assign MMS Report instance to IED

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 configurationform of the MMS Report instance. The Main tab contains the parameters that describe the variousattributes of the report definition read from the IED configuration file associated with the parent IEDinstance in the project tree.

- 47 -



2. Navigate to the “Data Set” tab to view the data set parameter details associated with the report.

Theupper grid of the dual grid has various columns that provide information related to the data setparameters.

- 48 -

3. The lower grid of the dual grid has the States Description parameter. For the data attributes whichare supported for SOE, user can specify their own state descriptions. Depending on the data typeof the data attribute in the dataset, the number of states will vary.

4. Additionally, the user can specify their own alias names for the parameters of the data set definitionin the MMS Report instance.

5. Click on OK to save the changes.

- 49 -



9.7.5 Load MMS Report Instance

To perform load of the MMS Report instance select the MMSSUBS instance in “Assigned” state under theIED 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 notloaded to the EIM.

- 50 -

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 theDelete menu option or the delete button on the Tool bar. The delete of the MMSSUBS will alsodelete the DSMAP blocks under it.

l Delete Selected Object(s) dialog will be shown. Click on “Delete Selected Object(s)” button todelete the instance. The MMSSUBS will be removed from the project tree.

You can also disassociate an MMS Report Instance through the IED Configuration form.

9.8 Adding or associating logical devices to an IED

This section includes tasks to add or associate a logical devices to an IED.

Considerations

- 51 -



l Use drag and drop or menu selections method to assign a logical device to an IED in the Projecttree.

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 theLibrary 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 IEDdevice from Project tree.

9.8.2 To use drag and drop method to add/associate logical devicesto an IED

1. In the Library tree directory, click sign in front of the required IED type to show stored deviceblock types.

2. Drag the IED icon to an open area in the Project tree. (Note that cursor appears with + sign, whenpositioned 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 devicesto 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 textbox highlighted.

2. In the Tag Name text box, enter the required name of the device or accept the default name.

3. In the Item Name text box and enter the name of the entity that this object is associated with in theEnterprise 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 onthe 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 Unassignedcategory. The logical nodes associated with the logical device are created and assigned under thelogical device.

- 52 -

Figure 9.13 Logical device instance in Project tree.

7. Drag and drop the logical device instance into the Project tree.

Figure 9.14 Logical device instance in the Project tree

- 53 -



TIP

Logical devices can also be assigned using information in the next section, “Assigninglogical devices.”

9.9 Assigning logical devices

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 fordetails on changing the device's network node address. The device addresses can be set to thedefault value of 20. The number of logical devices that are loaded and logical nodes that areassigned 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.

9.9.1 Prerequisites

An EIM block is created in the Project tree, and has an IED instance associated to it.

9.9.2 To assign logical devices to an IED instance

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 logicaldevice

Considerations

l Number of logical devices and logical nodes per EIM is about 850. The number of logical devicesthat 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 limitnumber

l Logical nodes cannot be removed from the associated logical devices if they are loaded.

- 54 -

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 withthis logical device instance, by clicking on the check box in the Create column.

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 matchingphysical 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 61850system relates to a node address. The physical device tag, node address, and the manufacturerdevice 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 uniquetag name (NAME). This is automatically enforced through the Control Builder application. Theunique name that was assigned to the device when it was created in Project is also assigned asthe device's physical device tag. This is done to assure that the names are unique within thesystem. This means a change in NAME results in an automatic change in PD_TAG to keep themthe same. However, a change in PD_TAG does not result in an automatic change in the assignedNAME.

l While checking the IED configuration, you can only edit the Tag Name, Item Name and KeyDescription fields.

9.11.1 Prerequisites

You have assigned the IED to a PROTOCOL block in the Project tree.

- 55 -



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 theEnterprise 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 onthe Server History, Server Display, Control Confirmation and Identification tabs. Refer to theViewing EIM operation status in the Control Builder section in this document for information onStatistics and Memory tabs.

6. When you complete entering configuration data, click OK to close the Parameter Configurationdialog box.

9.12 Reloading EIM instance

Reloading component configuration is required when you make changes to the component or functionblock configuration, or after you replace a failed IED. You can use the applicable load procedure toreload data to components from the Project or Monitor tab. It is recommended to invoke the followingcommands 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 -

CONFIGURE CONTROL STRATEGIES

This section describes tasks to create a control strategy to control IED parameters through a C300Controller.

The Project Engineer builds a library of the IED blocks in Control Builder. The Project Engineer thencreates control strategies that use the instances of the IED blocks. The control strategies and the IEDare 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 aboutconfiguring strategies using the Series C Universal I/O module, refer to the Control Building User'sGuide.

Considerations

l The navigation from the hyperlinked parameter is available to a parameter connector, which is foran Input/Output parameter of a block.

l You can navigate to a parameter in other charts that belong to a different controller. Therefore, thisnavigation improvement can be used to traverse between peer-to-peer connections acrosscontrollers.

l In the Project mode, double-click on the parameter to edit the parameter name in the parameterconnector. 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 notexist, you cannot navigate to the source parameter and hence the hyperlink for such parametersdoes 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'sGuide.

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 hasassociated logical devices and it’s and logical nodes.

l You have created a Control Module to associate the physical device to. Refer to the C300Controller 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 Experionblock that support the data type.

- 57 -

CHAPTER

10

10.2 To configure Control Strategy which reads parametersfrom 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 connectorbeing placed in different locations. Click once to establish a path to a desired locationbefore double-clicking. Press the ESC key to cancel the operation and start over ifrequired.

4. Use one of the following methods to specify the name of the block connection.

Option Procedure

Option 1

Enter the full name of the desired block connection, includingControl Module, Block Name (Tag), Parameter and then pressthe ENTER key.

Option 2

a. Click on the button with the dot leader icon (three dots)to access the Point Selection dialog.

b. Find the desired point name and parameter and thenclick on Select to insert the specified parameter into theparameter connection field.

c. Click Close on the top right-hand corner of the PointSelection dialog box to close the dialog and return to thecontrol drawing.

After you create a parameter connector, the parameter appears as hyperlink. When you click on thehyperlinked parameter with the Control key pressed, the chart/configuration form appears for thetagged block

ATTENTION

- 58 -

Chapter 10 - Configure control strategies


EIM with IEC 61850 supports IEC 61850 edition 2 data types. You can read/writeparameters from the Project to the IEC 61850 edition 1 data types only. Parameters thathave enumeration value beyond 64 have negative values. Perform the followingworkaround 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 IED value = – 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 -

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 Control writes

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 IEC61850 supports direct control with normal security (direct-operate) control model. Control Buildersupports configuration of control strategies in C300 Controller to write data to IED controllable statusand analog data attributes of common data class specifications defined in the IEC 61850 SpecificationPart 7.2 (edition 1).

You can write control data structures that send the control structure format and its data. Any logical nodewhich contains data object with data attribute Oper requires a control write.

Considerations

- 60 -



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.


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 logicaldevices and it's and logical nodes.

l You have created a Control Module to associate the IED to. (Refer to the C300 Controller User'sGuide to create a Control Module).

l Do not write the control value from the functional constraint FC tab of the logical node (associatedwith an IED). When IED control parameters are configured to write from control strategies, it mightresult in write failures. Special considerations are required to write to IED data attributes that hasnegative enumerations. Refer the negative enumeration workaround

l Configure IED with a control model from the supported control models and ctlModel. Use 3rd IEDconfiguration or IED front panel display to set the control model.

10.3.2 To perform a control write

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 ofthe 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-pointcontrol) class only

c. Click OK.

2. Writing a control value

a. Configure control strategies in C300 Controller to write to IED controllable data attributes ofthe common data classes to PUSH blocks. for example, CtlVal).

b. Configure control strategies in C300 Controller to write to IED controllable data attributes ofthe common data classes to SCM blocks.

The Oper control parameter attributes of the logical device are updated.

The attributes that were set up while configuring the logical node in the Project side are notwritten to the IED until the CtlVal parameters are written.

- 61 -

3. This results in a change in the output status of an IED connected device, such as a relay or aswitch.

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 shootingsection for more.

10.4 Configuring MMS Subscriber block reports with DSMAPBlock

The DSMAP is a block representation of the subsystem by the same name that takes Subscriber blockreport data and forwards it to the DS_IN block on a C300. Only when the DS_IN and Subscriber blockshave 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 Nameo Must not exceed 40 characters


o Must not contain an embedded space or leading space

l Considerations for Item Nameo Must not exceed 40 characters



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 ControlModule with which to associate the physical device. Refer to the “C300 Controller User’s Guide” tocreate a Control Module.

You have identified the data type for the IED data attributes that you want to connect to an Experionblock.

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.

10.4.2 To configure DSMAP values

1. Select the subscriber block module properties for EIM by double clicking or right clicking andselecting “Module Properties” in the context menu.

2. On the third tab labeled “Data Set” select the dataset(s) to be subscribed to by clicking thecheckbox under the "Associate" column.

3. In Control Builder’s Project Assignment View, create a new Control Module and add it to CEE.

- 62 -



4. Open the Control Module and add the DSIN block(s) in the Library under Dataset. The DSIN blocktransfers 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 ofthe 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 theirconnections.

- 63 -

6. From here select the second tab labeled “DataSet”.

7. Click the ellipsis “...” button to find the Subscriber block.

8. Select the Subscriber.

- 64 -



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.

- 65 -

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 BlockPins 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-sideof the screen. For multiple parameters, repeat Alias Name selection as required. Click “OK.”

- 66 -



13. Save the Control Module (button at the top of the screen) and the DSMAP will now appear underthe associated Subscriber block.

TIP

You can select multiple data types to populate data sets by pressing and holding shift orcontrol.

If you want to modify an alias name, you must modify it under your parameter data set.

- 67 -

COMMUNICATION FAILURES AND FIXINGCOMMON PROBLEMS IN EIM-61850

11.1 EIM cannot communicate with a single IED

1. In the Monitoring tree, double-click the IED icon in the Project tree. The Parameter Configurationform 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 thesame as the IP address of the physical IED.

l In the IED Information section, verify that the IED information is correct and matches thephysical IED.

l In the CID Information section, verify that the CID load status is SUCCESS. The CID loadMore Info displays an error number if the load of the CID file failed. In a success case thisshould 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 arelimited, it is possible the IED cannot accept another connection.

11.2 How to determine the number of IEDs loaded on the EIM

- 68 -

CHAPTER

11

1. In the Monitoring tree, double-click the required Protocol block. The Protocol Block Parametersform appears.

2. In the Statistics tab, in the IEC 61850 Network section, the Total IEDs field indicates the number ofIEDs loaded on the EIM.

11.3 Read and write failures in EIM with IEC 61850 (EIM toIED)

1. Collect the error code reported in control strategy.

2. Collect EIM and IED communication statistics from Control Builder and from IED localdisplay/configuration tool.

3. For write failures, ensure that the control model is properly configured in the physical device thatmatch with the Control Builder configuration.

TIP

For general EIM communication failure cases, consult the Ethernet Interface Module Hardwareand Common Platform User’s Guide.

11.4 Fixing other Common Problems

IED template creation failure

The IED template creation fails.

DiagnosticCheck

IED template creation fails.

Cause Usage of incorrect Data types, usage of data types that are not according to IEC61850 standards

Solution Correct the data type in the ICD file or contact the IED manufacturer to get thecorrected IED ICD file.

- 69 -

Chapter 11 - Communication Failures and fixing common problems in EIM-61850

VIEWING EIM WITH IEC 61850OPERATION STATUS IN CONTROL BUILDER

The Monitoring tab in Control Builder can be used to view the operation and status of any of thevarious 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 followingtable summarizes the parameter data you can monitor and/or configure on the Statistics tab of theconfiguration form for the selected Protocol block.

Plain Text Parameter Name UserConfigurable

Notes

Statistics

Reset All Statistics STATSRESET No Button to initiate reset in Monitoring mode.

Notification Statistics

Notifications Rate NUMNTFRQUAVG No The number of Notification Requests persecond average.

MaximumNotifications Rate

NUMNTFRQUMAX No The number of Notification Requests persecond maximum.

Responder Statistics

Total ResponderRate

NUMPARRSPAVG No The average number of parameter get/storeresponses per second.

Maximum TotalResponder Rate

NUMPARRSPMAX No The maximum number of parameterget/store responses per second.

Peer ResponderRate

CPEERAVGPPS [ ] No The average number of peer parametersper second processed by theIEC61850LINK.

Maximum PeerResponder Rate

CPEERMAXPPS [ ] No The maximum number of peer parametersper second processed by theIEC61850LINK.

DisplayResponder Rate

CDISPAVGPPS [ ] No The average number of display peerparameters per second processed by theIEC61850LINK.

Maximum DisplayResponder Rate

CDISPMAXPPS [ ] No The maximum number of display peerparameters per second processed by the

- 70 -

CHAPTER

12


Notes

IEC61850LINK.

IEC 61850 Network

Total IEDs NUMIEDS No The number of IEDs configured in an IEC61850 network per second.

MMS RequestRate

MMSRPS No The number of data sets read operationsbetween IEC61850M and IED per second.

MMS Store Rate MMSSTORERPS No The number of read operations betweenIEC61850M and IED per second.

12.2 Memory tab –Protocol block

The Memory tab contains data on general memory usage in the EIM. It also shows memory usageparameters in terms of internal memory units: descriptors and blocks. The following table summarizesthe parameter data you can monitor on the Memory tab of the configuration form for the selectedProtocol block.


Notes

Memory Usage in KBytes

Total UserMemory(kb)

TOTALMEMINK No Shows the total size of user memory pool, inkilobytes.

CurrentlyUsed Memory(kb)

USEDMEMINK No The total amount of used memory in usermemory pool, in kilobytes.

CurrentlyFree Memory(kb)

FREEMEMINK No Amount of free memory in user memory pool,in kilobytes.

Largest FreeMemory BlockSize(kb)

MAXFREEINK No The size of largest contiguous memory blockin user memory pool, in kilobytes.

Memory Usage in Bytes

Total UserMemory(b)

TOTALMEM No Total size of user memory pool, in bytes.

CurrentlyUsed Memory(b)

USEDMEM No Total amount of used memory in user memorypool, in bytes.

CurrentlyFree Memory(b)

FREEMEM No Current amount of free memory in usermemory pool, in bytes.

Largest FreeMemory Block

MAXFREEBLKSZ No Shows size of largest contiguous memoryblock in user memory pool, in bytes.

- 71 -

Chapter 12 - Viewing EIM with IEC 61850 operation status in Control Builder



Notes

Size(b)

Memory Descriptors

Total MemoryDescriptors

NTOTMEMDESC No Total number of memory descriptors available.

Free MemoryDescriptors

NUMFREEDESC No Number of free (available) memorydescriptors.

RegisteredMemoryDescriptors

NUMREGDESC No Number of registered memory descriptors.

Used MemoryDescriptors

NUMUSEDDESC No Number of used memory descriptors.

Memory Blocks

Used MemoryBlocks

NUMUSEDBLKS No Number of used memory blocks.

Free MemoryBlocks

NUMFREEBLKS No Number of free (available) memory blocks.

ExternalMemoryBlocks

NUMEXTBLKS No Number of external memory blocks.

Driver Memory Usage

Reserved (kb) DRVMEMRESERVED No The amount of reserved memory in kilobytesfor EIM hardware.

Used (kb) No The amount of memory in kilobytes used bythe EIM hardware.

Free (kb) No The amount of memory in kilobytes availablefor EIM hardware. (The value is calculated byMemory pools free + DRVMEMRESERVED –Pools RAM used).

FragmentedFree (kb)

No

Largest Free(kb)

No

FreeFragmentCount

No

12.3 Statistics tab – IED blockThe Statistics tab shows the response details of an IED during its interaction with EIM.

- 72 -

Plain Text ParameterName

UserConfigurable

Notes

Statistics

Reset All Statistics STATSRESET No Button to initiate reset in Monitoring mode.

IEC 61850 Comm Performance

Average ResponseTime (ms)

RESPTIMEAVG No The average response time of an IED to arequest sent from an EIM.

Fastest ResponseTime (ms)

RESPTIMEMIN No The number of data sets read operationsbetween an EIM and IED per second.

Slowest ResponseTime (ms)

RESPTIMEMAX No The number of read operations between anEIM and IED per second.

- 73 -


EIM WITH IEC 61850 OPERATION

This section includes information specific to using the EIM with IEC 61850 protocol. For more operationinformation and behaviors which characterize the EIM Platform and are common across the differentEIM downlink protocols, see the EIM Hardware and Common Platform User’s Guide. These commoncharacteristics include faceplate displays and indications, startup, shutdown, using station displays,EIM overload, bulk configuration tools, viewing EIM platform operation status in Control Builder andcommands including EIM synchronization, become primary, and switchover.

- 74 -

CHAPTER

13

CONTROL BUILDER BLOCK ICONDESCRIPTIONS FOR EIM WITH IEC 61850

Adding an EIM block (non-redundant or redundant) to the Control Builder Project tab results in theappearance of an icon that represents a single EIM or redundant controller pair. Once the EIM block isloaded, 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, twoicons appear, one representing the primary on the left and the icon representing the secondary on theright. 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 itscurrent state and status in IEC 61850 protocol.

Icon Represents . . . EIM state

Project Tab

(gray)

EIM configured for non-redundant operation. N/A

(gray & white)

EIM Primary configured for redundant operation. N/A

(white & gray)

EIM Secondary configured for redundant operation. N/A

Monitor Tab

EIM is non-redundant and not communicating No Communication

Table 14.1 EIM with IEC 61850 icon indications in Control Builder

- 75 -

CHAPTER

14


(red) (Offnet)

(red & white)

Primary EIM is not communicating. No Communication(Offnet)

(white & red)

Secondary EIM is not communicating. No Communication(Offnet)

(yellow)

EIM is non-redundant No Database

(yellow & yellow)

Primary EIM is not synchronized and partner EIM isvisible

No Database

(yellow &shadow)

Primary EIM is not synchronized and partner EIM isabsent or incompatible

No Database

(green)

EIM is non-redundant Run or OK

Primary EIM is synchronized Run or OK

- 76 -

Chapter 14 - Control Builder block icon descriptions for EIM with IEC 61850



(green & white)

(green & white,pause)

Primary EIM, standby synchronization Run or OK

(green & yellow)


Run or OK

(green &shadow)


Run or OK

(white & green)

Secondary EIM is synchronized Backup

(white & green,pause)

Secondary EIM, standby synchronization Backup

(yellow & yellow)

Secondary EIM is not synchronized and partner EIM isvisible

Backup

Secondary EIM is not synchronized and partner EIM isabsent or incompatible.

Backup

- 77 -


(shadow &yellow)

(green)

EIM is non-redundant Run Soft Fail or OKSoft Fail

(green & white)

Primary EIM is synchronized Run Soft Fail or OKSoft Fail

(green & white,pause)

Primary EIM, standby synchronization Run Soft Fail or OKSoft Fail

(green & yellow)


Run Soft Fail or OKSoft Fail

(green &shadow)


Run Soft Fail or OKSoft Fail

(white & green)

Secondary EIM is synchronized Backup Soft Fail

Secondary EIM, standby synchronization Backup Soft Fail

- 78 -




(white & green,pause)

(yellow & yellow)

Secondary EIM is not synchronized and partner EIM isvisible partner present.

Backup Soft Fail

(shadow &yellow)

Secondary EIM is not synchronized and partner EIM isabsent or incompatible

Backup Soft Fail

- 79 -

CONTROL BUILDER BLOCK ICONDESCRIPTIONS FOR EIM WITH IEC 61850PROTOCOL BLOCK

Creating and assigning an instance of the IEC 61850 PROTOCOL block under the EIM on the projectside 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) iconassumes in the project and monitoring tree, based on its current state and status.

IconRepresents . . .

..(gray) Project side icon

..(red) Error in monitoring side

..(green) Online

Idle

Table 15.1 EIM with IEC 61850PROTOCOL block icon indications in Control Builder

- 80 -

CHAPTER

15

IconRepresents . . .

..(blue)

..(yellow) Not synchronized

..(red) Offline

- 81 -

Chapter 15 - Control Builder block icon descriptions for EIM with IEC 61850 PROTOCOL block

CONTROL BUILDER BLOCK ICONDESCRIPTIONS FOR EIM WITH IEC 61850MMS SUBSCRIBER BLOCK

Adding an MMS Subscriber block to a PB_61850 block on the project side in Control Builder results inthe appearance of the MMS Subscriber block icon.

The following table shows the various appearances that the MMS Subscriber block icon assumesbased on its current state and status.

Icon Represents . . .

Project Tab

..(gray)

MMS Subscriber block project side

..(red)

Error in Monitoring Side

..(blue)

Inactive

..(red)

Fail

Table 16.1 EIM with IEC 61850 MMS Subscriber block icon indications in Control Builder

- 82 -

CHAPTER

16


..(green)

Active

Active with error

Active with synchronization fail

- 83 -

Chapter 16 - Control Builder block icon descriptions for EIM with IEC 61850 MMS Subscriber block

CONTROL BUILDER BLOCK ICONDESCRIPTIONS FOR EIM WITH IEC 61850DSMAP BLOCK

Creating a DSMAP instance under the MMS Subscriber block on the project side in Control Builderresults in the appearance of the DSMAP block icon.

The following table shows the various appearances that the DSMAP block icon assumes based on itscurrent state and status.


Project Tab

..(gray)

DSMAP Project side icon

..(red)

Error in monitoring side

..(blue)

Inactive

..(green)

Active

Table 17.1 EIM with IEC 61850DSMAP block icon indications in Control Builder

- 84 -

CHAPTER

17

- 85 -

Chapter 17 - Control Builder block icon descriptions for EIM with IEC 61850 DSMAP block

NOTICES

TrademarksExperion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks ofHoneywell International, Inc.

ControlEdge™ is a trademark of Honeywell International, Inc.

OneWireless™ is a trademark of Honeywell International, Inc.

Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon International is abusiness unit of Honeywell International, Inc.

Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit ofHoneywell International, Inc.

Other trademarksMicrosoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in theUnited States and/or other countries.

Other brands or trademarks are trademarks of their respective owners.

Trademarks that appear in this document are used only to the benefit of the trademark owner, with nointention of trademark infringement.

Third-party licensesThis product may contain or be derived from materials, including software, of third parties. The thirdparty 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 accompanyingthe product, in the documents or files accompanying such third party materials, in a file named third_party_licenses on the media containing the product.

Documentation feedbackYou 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. Forimmediate help with a technical problem, contact HPS Technical Support through your local CustomerContact Center, or by raising a support request on the Honeywell Process Solutions Support website.

How to report a security vulnerabilityFor the purpose of submission, a security vulnerability is defined as a software defect or weakness thatcan 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 instructionsat:

https://www.honeywell.com/en-us/product-security.

Support

- 86 -

http://www.honeywellprocess.com/support

mailto:[email protected]

https://www.honeywell.com/en-us/product-security

For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To findyour local CCC visit the website, https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx.

Training classesHoneywell holds technical training classes that are taught by process control systems experts. For moreinformation about these classes, contact your Honeywell representative, or seehttp://www.automationcollege.com.

- 87 -

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

http://www.automationcollege.com/

eim with iec 61850 user's guide-epdoc-x462-en-520a

Documents