AC 800M IEC 61850 Engineering & Configuration · AC 800M IEC 61850 Configuration for CI868 System...

Power and productivity

for a better world™

AC 800MIEC 61850Configuration for CI868

System Version 6.0

AC 800M IEC 61850

Configuration for CI868

System Version 6.0

NOTICEThis document contains information about one or more ABB products and may include a description of or a reference to one or more standards that may be generally relevant to the ABB products. The presence of any such description of a standard or reference to a standard is not a representation that all of the ABB products referenced in this document support all of the features of the described or ref-erenced standard. In order to determine the specific features supported by a particular ABB product, the reader should consult the product specifications for the particular ABB product.

ABB may have one or more patents or pending patent applications protecting the intellectual property in the ABB products described in this document.

The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.

Products described or referenced in this document are designed to be connected, and to communicate information and data via a secure network. It is the sole responsibility of the system/product owner to provide and continuously ensure a secure connection between the product and the system network and/or any other networks that may be connected.

The system/product owners must establish and maintain appropriate measures, including, but not lim-ited to, the installation of firewalls, application of authentication measures, encryption of data, installa-tion of antivirus programs, and so on, to protect the system, its products and networks, against security breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information.

ABB verifies the function of released products and updates. However system/product owners are ulti-mately responsible to ensure that any system update (including but not limited to code changes, con-figuration file changes, third-party software updates or patches, hardware change out, and so on) is compatible with the security measures implemented. The system/product owners must verify that the system and associated products function as expected in the environment they are deployed.

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

This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized pur-pose.

The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. This product meets the require-ments specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC.

TRADEMARKSAll rights to copyrights, registered trademarks, and trademarks reside with their respective owners.

Copyright © 2003-2016 by ABB.All rights reserved.

Release: April 2016Document number: 9ARD171385-600 A

9ARD171385-600 A 5

Table of Contents

About This User ManualUser Manual Conventions .................................................................................................8

Feature Pack ...........................................................................................................8

Warning, Caution, Information, and Tip Icons ......................................................8

Terminology.......................................................................................................................9

Released User Manuals and Release Notes.....................................................................13

Section 1 - Introduction

Section 2 - CI868 ConfigurationCI868 IED Hardware Objects..........................................................................................21

IEC 61850 Wizard ...........................................................................................................24

Generating CID / ICD file for CI868 IED............................................................25

Importing SCD File on CI868 IED Node ............................................................29

CCF View.............................................................................................................31

Handling SCD Re-configuration and Control Builder Tree Variation .................33

IEC 61850 Wizard Errors.....................................................................................39

Section 3 - CI868 Application EngineeringCI868 MMS Control Function Block with IEC 61131-3 ................................................45

IED Command Send ............................................................................................46

IED Status Receive...............................................................................................51

CI868 Support for Sequence of Event (SOE)..................................................................55

Configuration for Alarm and Events ....................................................................57

IEC 61131 -3 Application for External Events ....................................................58

Table of Contents

6 9ARD171385-600 A

Section 4 - CI868 EngineeringRepresenting CI868 Operating Status as an IED: LN0, LPHD ...................................... 63

Cross Referencing IEC 61850 Data with IEC 61131-3 Variables .................................. 65

For Data Subscribed by CI868 (Signal in an IED to IEC 61131-3) .................... 65

For Data Published by CI868 (IEC 61131-3 Signal to IED) ............................... 70

CI868 IED as IEC 61850 MMS Client ........................................................................... 72

CI868 Data Receive through MMS ..................................................................... 73

CI868 Control Commands through MMS ........................................................... 74

IEC 61850 Protocol Information in I/O channel ................................................. 80

Supported AC 800M Data Types .................................................................................... 85

GOOSE Send and Receive................................................................................... 85

CI868 MMS Receive LN Representations........................................................... 87

CI868 MMS Control Commands......................................................................... 89

CI868 Configuration Parameters..................................................................................... 90

Data Attribute, Quality and Time Stamp for Send and Receive Data Objects .... 90

Data Quality for Received Data ........................................................................... 91

CI868 IED Parameters ......................................................................................... 92

Supported Logical Nodes..................................................................................... 93

Application Redundancy ............................................................................................... 102

CI868 IED Diagnostic Information............................................................................... 102

CI868 Performance Data............................................................................................... 105

Appendix A - MMS Logical Node Channels

Appendix B - CI868 Control Builder Coexistence CompatibilityCI868 Hardware Libraries............................................................................................. 131

Appendix C - CI868 Hardware Object Name Information

Revision HistoryUpdates in Revision Index A......................................................................................... 141

Index

9ARD171385-600 A 7

About This User Manual

Any security measures described in this User Manual, for example, for user access, password security, network security, firewalls, virus protection, etc., represent possible steps that a user of an 800xA System may want to consider based on a risk assessment for a particular application and installation. This risk assessment, as well as the proper implementation, configuration, installation, operation, administration, and maintenance of all relevant security related equipment, software, and procedures, are the responsibility of the user of the 800xA System.

This book describes the Engineering and Configuration of the CI868 IED using Control Builder M, IEC 61850 Wizard tool and other third party tool.

The application engineers or the engineers who plan the design or implementation of IEC 61850 as a part of substation automation, are intended to use this book. User is expected to be familiar with the hardware and software functionalities of the 800xA system products.

The following sections are included in this book.

– Section 1, Introduction, provides a brief overview of IET 600, CCT600 and IEC 61850 Wizard.

– Section 2, CI868 Configuration, describes how to configure AC 800M / CI868 IED used for IEC 61850.

– Section 3, CI868 Application Engineering, describes how to configure and use CI868 MMS Control Function Block with IEC 61131-3.

– Section 4, CI868 Engineering, describes the engineering of AC 800M / CI868 IED used for IEC 61850.

– Appendix A, MMS Logical Node Channels, details the list of logical nodes used with IEC 61850 for MMS Client communication.

User Manual Conventions About This User Manual

8 9ARD171385-600 A

– Appendix B, CI868 Control Builder Coexistence Compatibility, describes the Control Builder M version compatibility.

– Appendix C, CI868 Hardware Object Name Information, describes the location of CI868 Hardware object when System Alarms displays an error at CI868 Hardware object level.

User Manual ConventionsMicrosoft Windows conventions are normally used for the standard presentation of material when entering text, key sequences, prompts, messages, menu items, screen elements, etc.

Feature Pack

The Feature Pack content (including text, tables, and figures) included in this User Manual is distinguished from the existing content using the following two separators:

Feature Pack Functionality______________________________________________________________________

<Feature Pack Content>

___________________________________________________________________________________________

Feature Pack functionality included in an existing table is indicated using a table footnote (*):

* Feature Pack Functionality

Unless noted, all other information in this User Manual applies to 800xA Systems with or without a Feature Pack installed.

Warning, Caution, Information, and Tip Icons

This User Manual includes Warning, Caution, and Information where appropriate to point out safety related or other important information. It also includes Tip to point out useful hints to the reader. The corresponding symbols should be interpreted as follows:

Electrical warning icon indicates the presence of a hazard that could result in electrical shock.

Warning icon indicates the presence of a hazard that could result in personal injury.

Caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard that could result in corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to use a certain function.

About This User Manual Terminology

9ARD171385-600 A 9

Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to personal injury or death. Therefore, fully comply with all Warning and Caution notices.

TerminologyA complete and comprehensive list of Terms is included in the System 800xA System Guide Functional Description (3BSE038018*). The listing includes terms and definitions that apply to the 800xA System where the usage is different from commonly accepted industry standard definitions and definitions given in standard dictionaries such as Webster’s Dictionary of Computer Terms. Terms that uniquely apply to this User Manual are listed in the following table.

Terminology About This User Manual

10 9ARD171385-600 A

Term/Acronym Description

800xA ABB automation system (eXtended Automation).

AC 800M ABB Controller 800M series, general purpose process controller series by ABB.

AC 800M Controller Any controller constructed from the units and units connected to the AC 800M hardware platform.

AE Alarm and Event.

CCT ABB Communication Configuration Tool for configuring signals and generating SCD files.

CDC Common Data Class as specified by IEC61850-Ed1 (Edition1) specification.

CDC Block CDC representation in Control Builder M Project Explorer.

CI868 Module Communication Interface Module for AC 800M controller. These modules are connected over the CEX bus and contain implementation of a specific communication protocol.

CID Configured IED Description file, a type of SCL file as specified in IEC 61850 Edition 1 specification.

Control Builder Controller Builder M (Control Builder Professional or Compact Control Builder).

DA Data Access.

DPC Double Point Controllable. CDC type, specified in IEC 61850 Edition 1 specification.

FBD Feeder Block Diagram.

GCB GOOSE Control Block.

About This User Manual Terminology

9ARD171385-600 A 11

GOOSE Generic Object Oriented Substation Event. Based on the VLAN and priority tagging, GOOSE is used for very fast peer-to-peer data exchange between IEC 61850 compliant IEDs, also termed as Horizontal Communication.

HW Unit Hardware unit defined in the tree of Control Builder M Project.

I/O Input and Output.

ICD IED Capability Description, type of SCL file as specified in IEC 61850 Edition 1 specification.

IEC International Electrotechnical Commission.

IEC 61850-Ed1 IEC 61850-Ed1 (Edition1) specification.

IED Intelligent Electronic Device.

IET ABB Integrated Engineering Tool for generating SCD file.

LD Logical Device: A virtual device which enables aggregation of Logical Nodes and Data sets for communication purposes. It is a grouping criteria for common signals such as, switch status, interlocking or protection signals per IED. Additionally, Logical Devices contain convenient lists of frequently accessed or referred to information. For example, data sets.

LN Logical Node.


Terminology About This User Manual

12 9ARD171385-600 A

MMS Manufacturing Message Specification (MMS) is an international standard (ISO 9506) dealing with messaging system for transferring real time process data and supervisory control information between network devices and/or computer applications. MMS defines the following:

• A set of standard objects which must exist in every device, on which operations like read, write, event signaling, can be executed

• A set of standard messages exchanged between a client and a server stations for the purpose of monitoring and/or controlling these objects

• A set of encoding rules for mapping these messages to bits and bytes when transmitted.

Node A computer communicating on a network, for example the Internet, Plant, Control or IO network. Each node typically has a unique node address with a format depending on the network it is connected to.

OPC OLE for Process Control. A set of standard interfaces based on COM technology.

PA Process Automation.

PGS Power Generation Solutions.

PM Processor Module of AC 800M controller.

PMS Power Management Solutions.

RCB Report Control Block.

SA Substation Automation.

SBO Select Before Operate Command.

SCADA Supervisory Control And Data Acquisition.

SCD Substation Configuration Description, type of SCL file defined by IEC 61850 Ed1 specification.


About This User Manual Released User Manuals and Release Notes

9ARD171385-600 A 13

Released User Manuals and Release NotesA complete list of all User Manuals and Release Notes applicable to System 800xA is provided in System 800xA Released User Documents (3BUA000263*).

System 800xA Released User Documents (3BUA000263*) is updated each time a document is updated or a new document is released. It is in pdf format and is provided in the following ways:

• Included on the documentation media provided with the system and published to ABB SolutionsBank when released as part of a major or minor release, Service Pack, Feature Pack, or System Revision.

• Published to ABB SolutionsBank when a User Manual or Release Note is updated in between any of the release cycles listed in the first bullet.

A product bulletin is published each time System 800xA Released User Documents (3BUA000263*) is updated and published to ABB SolutionsBank.

SCL Substation Configuration Language defined in IEC 61850 Ed1 specification.

SLD Single Line Diagram.

XML eXtensible Markup Language.


Released User Manuals and Release Notes About This User Manual

14 9ARD171385-600 A

9ARD171385-600 A 15

Section 1 Introduction

This section gives an overview of the complete engineering workflow of IEC 61850 integrated with 800xA system.

Figure 1 and Figure 2shows the simplified IEC 61850 engineering workflow integrated with 800xA system.

Figure 1. 800xA IEC 61850 Substation Engineering Workflow

Substati on Automati on Engi neeri ng

Substati on Structure

Substat ion Conf igurat ion

Si ngle Li ne diagram

Stati on Confi gurati on Di agram

Feeder Bl ock Di agram

Impor t CID Fi l e

Communicat ion Conf igurat ion

Data Set Confi gurati onAssi gn LN to Conducti ve Equi pment RCB Confi gurati on GCB Confi gurati on

Confi gure CI868 IED Templ ate

C:\ProgramFi l es(x86) \ABB\61850 OPCServer

CI 868 IED Engineering

Expor t CID/ICD Fi l e

Control Builder

I CD Fi l e for I HMI

IEC 61850 OPC Server

OPC Server wi th 1 sub network. i cd OPC Server wi th 16 sub network.i cd

Thi rd Par ty CID Fi l e, speci f i ed by vendors.

Impor t CID Fi l e

I ED Appl ication Engineering

Expor t IED Confi gurati on

PCM 600

+

Export SCD F i le


16 9ARD171385-600 A

The engineering workflow for IEC 61850 configuration in 800xA systems comprise of the following application tools/components:

• IEC 61850 Substation Engineering with Communication Configuration with ABB IET600 or CCT600 or 3rd party IEC 61850 engineering tools

• Control Builder M with IEC 61850 Wizard

Control Builder M

• Control Builder M with IEC 61850 Wizard is used to configure CI868 as an IED and download the configuration to the CI868 module. It is also used to connect IEC 61131-3 variables to the IEC 61850 data.

Figure 2. 800xA IEC 61850 Substation Engineering Workflow

Confi gurati on

CET for IEC 61850 OPC Server

Impor t SCD Fi l e

IEC 61850 OPC Server IEC 61850 Alarms & Events

PCM600 for ABB IEDs

Download Confi gurati on to IED

Impor t SCD Fi l e +

Control & Functi onal Structure Creati on

Plant Explorer

Upload SCD Fi l e for IEC 61850 Connect

Download CI868 Confi gurati on i nto AC 800M Control l er

Control Builder for CI 868 IED

Impor t SCD Fi l e


9ARD171385-600 A 17

• Use IEC 61850 Wizard tool available in Control Builder M to:

– Create and Export ICD file as a template for CI868 IED– Generate and Export configured CID file for CI868 IED– Import SCD file generated from CCT or any other IEC 61850 engineering

tool

– Generate configuration files for each CI868 access point– Create Hardware Tree structure in Control Builder M representing CI868

as an IED in the IEC61850 network.

IET600 / CCT600

IET600 / CCT600 is an IEC 61850 engineering tool to perform IEC 61850 communication configuration on ICD and CID files of imported IEDs and deliver the resultant substation configuration file (.scd file).

A detailed explanation on configuring SCD file using IET 600 / CCT 600 tool is explained in System 800xA IEC 61850 Engineering Workflow (9ARD171384*) Manual.

Following are the improvements made in CI868, IEC61850 Wizard and 800xA IEC 61850 Engineering Workflow:

IEC 61850 MMS Client constitutes the following:

• CSWI and XCBR LNs for sending MMS Control Commands to other IEDs.

• Receiving MMS Signals using RCB data from other IEDs.

• MMS Diagnostic data can be viewed in Control Builder M. User can now view the diagnostic information of a MMS hardware object in the editor window.

• Process Alarm and Events with IED Timestamp (with AlarmCond function block).

• IEDCommandSend and IEDStatusReceive function blocks in ProcessObjBasicLib application library to support SBO functionality in IEC 61131-3 programing.

• Incoming Add Cause Negative responses that are available from IEC61850 Stack for MMS signals.

• Printing errors and warnings into the CI log that are generated from the IEC61850 stack log.


18 9ARD171385-600 A

• CI868 Logical Node LN0 displays Mod channel in the hardware editor and also generate Protocol info for Mod channel of LN0 object.

• Flexible RCB dataset engineering that contains Data objects from LN0 and LPHD logical nodes assigned to CI868.

• CI868 hardware modules supports Essential Automation (eA) in System 800xA. CI868 Firmware detects the CI868 module type eA (grey module) or xA (white module) and updates the same in CI868 Hardware Object under the Extended Status.

Simplified 800xA IEC 61850 Engineering Workflow for substation automation:

• Support of 12 CI868 modules per AC 800M controller.

• Engineering with Control Builder M and CCT 600only, thereby minimal usage of external third party tools.

• Compatible with PCM600 2.4 Tool.

• Compatible with IET600 5.2 Tool.

• Defining CI868 as an IED instead of AC 800M in Control Builder M.

• Editable hardware tree under CI868 level to define CI868 as IED in Control Builder M to generate CI868 CID / ICD file using IEC61850 Wizard tool.

• Import one SCD file per CI868 module for a complete configured substation, enabling the user to have a flexible and distributed engineering to work on different SCD files.

• Consistency check of Control Builder M hardware tree with SCD file before downloading the SCD file.

IEC61850 Wizard tool improvements:

• Dynamic Generation of CI868 User Hardware Library containing Hardware objects and IO channels based on GCB and RCB Dataset signals assigned to CI868 as configured in SCD file.

• There is no dependency of Substation section in the SCD file during import, thereby reducing the additional effort in engineering workflow.

• There is no dependency of Control Builder M project name and the substation name in the SCD file during import.


9ARD171385-600 A 19

• Storage and retrieval of SCD file from Control Builder M to provide a backup of a fully configured SCD file for each CI868 IED module.

• Use of new SCL libraries for optimized SCD parsing while import.

• Generate CI868 CID / ICD file from configured hardware tree under CI868.

• Improved handling of q, t and optional Data Attributes during the SCD file import.

• Support of all Data Object names if CDC type is one out of the existing supported types: SPS, ACD, ACT, DPS, MV, INS and also support of CDC types SEQ, WYE, DEL.

• Exit button in the IEC61850 Wizard is disabled when import is started, thereby user can only use Cancel instead of exiting the import at any point of time.


20 9ARD171385-600 A

9ARD171385-600 A 21

Section 2 CI868 Configuration

The IEC 61850 for Substation Automation System (SAS) defines communication between Intelligent Electronic Devices (IED) in the substation and other related equipment.

The CI868 interface module is designed as an IED to support GOOSE and MMS client communication on IEC 61850 network. It works as an interface between IEC 61850 network and process controller running on IEC 61131-3 applications.

CI868 IED Hardware ObjectsEach CI868 is represented as IED with one access point. The access point is the position of CI868 in the Control Builder M tree structure and is represented in the hardware object MyIED (see Figure 3).

Figure 3. Communication Interface CI868 IED Tree view

CI868 IED Hardware Objects Section 2 CI868 Configuration

22 9ARD171385-600 A

Section 2 CI868 Configuration CI868 IED Hardware Objects

9ARD171385-600 A 23

CI868 IED and all the IEC 61850 related elements are designed as hardware objects in a hardware library configured under Control Builder M.

Table 1 details the hardware object in Control Builder M.

Control Builder M supports maximum of 5000 Hardware objects in a Controller.

It is recommended to configure the hardware objects within the limit to avoid errors during downloading project to the controller.

Table 1. Control Builder M Hardware Object

Hardware Object

Description

CI868 CI868 is modelled as an IED with one access point. CI868 object have two types of IED objects (MyIED and IED).

MyIED object represents CI868 module. IED object represents other IEDs in IEC 61850 network.

MyIED MyIED object is the representation of CI868 in IEC 61850 network as an IED. Only GOOSE Send LNs and MMS Client (ITCI LN) is represented under this object.

Only one instance of MyIED object must be present in the first position for each CI868 IEDs.

IED IED objects are placed under CI868 during import of SCD file. These objects represent other IEDs that contain the signals or values that communicate with CI868 IEDs using GOOSE or MMS protocol.

LD The logical device contains the list of supported configured logical nodes that are configured in the respective IEDs.

IEC 61850 Wizard Section 2 CI868 Configuration

24 9ARD171385-600 A

IEC 61850 Wizard The IEC 61850 Wizard is a graphical interface used for populating the CI868 Communication Interface tree representation for IEC61850 GOOSE and MMS Client communication in the Control Builder M and also used for generating the CI868 Configuration data.

Right click the CI868 module to open the IEC 61850 Wizard tool (see Figure 4). It is used for,

• exporting ICD / CID file for CI868 IED, refer to Generating CID / ICD file for CI868 IED on page 25.

• importing SCD file generated from CCT or any other IEC61850 engineering tool, refer to Importing SCD File on CI868 IED Node on page 29.

• creating IEC 61850 Hardware Objects Tree structure in Control Builder M representing CI868 as an IED in the IEC 61850 network, refer to CI868 IED Hardware Objects on page 21.

LN GOOSE Send Object: Represents the logical node for sending GOOSE signals to other IEDs.

MMS Client Activation: The logical node ITCI represents CI868 as MMS Client that supports receiving RCBs from other IEDs.

GOOSE Receive Object: Represented by Receive Data Blocks, for GOOSE receive signals from other IEDs.

MMS Receive Object: Represented by logical nodes that contain MMS signals data.

MMS Receive and Command Object: Represented by logical node that contains MMS Control Commands and MMS Reporting data.

Diag MMS Diagnostics Object: MMS Diagnostic hardware object that displays IED level MMS diagnostic information.

Table 1. Control Builder M Hardware Object

Hardware Object

Description

Section 2 CI868 Configuration Generating CID / ICD file for CI868 IED

9ARD171385-600 A 25

Generating CID / ICD file for CI868 IED

CI868 IED hardware objects are configured in Control Builder M hardware tree to generate CID / ICD file. The generated CID / ICD file contains: Header, Communication, IED, and Data type Templates. The generated file is imported into CCT / IET tool for configuring GOOSE and MMS signals.

Figure 4. CI868 Module - IEC61850 Wizard

Generating CID / ICD file for CI868 IED Section 2 CI868 Configuration

26 9ARD171385-600 A

IEC61850 Wizard (see Figure 6) is opened using the CI868 context menu. In the ICD / CID Export tab, click Browse to save and export the ICD / CID file on the selected path.

Figure 5. CI868 IED in Control Builder M with all supported LNs

Section 2 CI868 Configuration Generating CID / ICD file for CI868 IED

9ARD171385-600 A 27

DataSets and GSE Control Blocks for ICD File Generation

If the generated file is CI868 ICD, it contains a default dataset and GSE Control block. The default dataset contains the signals of the logical nodes configured in the Control Builder M. During export of ICD file, the IEC 61850 wizard prioritizes the logical nodes if configured in the following order to create default dataset.

Figure 6. IEC61850 Wizard - CI868 CID File Export

The Version and Revision file are generated while exporting the CID / ICD files. These values can be edited or updated, whenever the CID file is modified.

The log messages generated by IEC 61850 Wizard can be viewed by right-clicking and choosing View Log option in IEC 61850 Wizard window or by opening the IEC 61850 ImportWizard.log file located in.

C:\ABB Industrial IT Data\Engineer IT Data\Compact Control Builder AC 800M\LogFiles\Importwizard.log - For Compact Control Builder M.

C:\ABB Industrial IT Data\Engineer IT Data\ Control Builder M Professional\LogFiles\Importwizard.log - For Control Builder Professional.

Generating CID / ICD file for CI868 IED Section 2 CI868 Configuration

28 9ARD171385-600 A

• GF GGIO = 1• LS PTRC = 2• BB GAPC = 3• LS GAPC = 4• PC GAPC = 5• TC1 ATCC = 6• TC2 ATCC = 7• QC1 ARCO = 8• VC1 AVCO = 9• QC ARCO = 10• VC AVCO = 11

For Logical Nodes that are configured more than once, the default DataSet contains signals of the first configured logical node instance.

Retaining Data Set and GCB in CID File

When the CI868 configuration is exported as CID file, IEC 61850 Wizard checks from any previously imported SCD file and retains the configured CI868 Data Sets and GOOSE Control Blocks.

During the CID file export, IEC 61850 Wizard validates the configured CID file with the previous imported SCD file stored in the project folder for the following:

• Checks if the CI868 position in Control Builder M is same as the Access Point name under CI868 or AC 800M IED.

• Checks if Logical Device name configuration in Control Builder M is present under this Access Point.

• Checks if LN0 is present under that LD.

• Checks if Data Sets and GSE Control block is present.

If the above conditions are met, the configured DataSets signals and GSE control blocks are retained in the exported CID file. If any one of the conditions are not met, a default DataSet and GCB for the CID file is generated.

Before exporting the CID file from IEC61850 Wizard, if the name of logical node is modified or deleted under the corresponding logical device, the DataSets retained by IEC 61850 Wizard for that logical device does not detect the modifications, and will contain the contents of DataSets as per the configured SCD file.

The signals of the default dataset that are not matching with the LNs of CI868 are filtered out in CCT tool during signal configuration.

Section 2 CI868 Configuration Importing SCD File on CI868 IED Node

9ARD171385-600 A 29

If CI868 position, MyIED, and LD name is modified, the exported CID file contains the default Dataset and GSEControl blocks.

The generated individual configured ICD / CID file is further used for creating SCD file with IEC 61850 communication engineering tools such as CCT600.

Importing SCD File on CI868 IED Node

IEC61850 Wizard Tool (see Figure 7) imports the configured SCD file into Control Builder M under the selected CI868-IED node to create the IEC61850 GOOSE and MMS communication representation. The SCD file contains the configuration of GOOSE and MMS communication between CI868 IED and other IEDs.

Before importing the SCD file, click Verify to validate any errors for the selected CI868 IED access point in the configured SCD file. If errors are found in the selected access point of the .scd file during verification, they are logged in the

When exporting CI868 configuration into existing CCT600 project containing the CI868 module with the same name, it is recommended to export the CI868 configuration as CID file to retain previously configured datasets in CI868. Incase of exporting the ICD file the Data Set informations are not retained.

Figure 7. IEC 61850 Wizard - SCD Import

Importing SCD File on CI868 IED Node Section 2 CI868 Configuration

30 9ARD171385-600 A

IEC61850.log file. A generic message is displayed to refer the IEC61850 Import Wizard log file.

After successful import, the SCD file is stored in Control Builder M project folder (Compact Control Builder) or in the Aspect Directory (Control Builder professional). For every subsequent import, the SCD file is overridden and only the last imported file is available.

Deleting the CI868 object in the Control Builder M tree structure removes the stored SCD file.

The Get SCD button in the IEC61850 Wizard window retrieves the last imported SCD file and this SCD file is used for retaining configured Data set and GOOSE Control Blocks during CID file export. For more information, refer to Retaining Data Set and GCB in CID File. One SCD file is stored per CI868 IED module, irrespective of common SCD file with multiple CI868 IED modules.

It is recommended Not to configure RCB or GCB datasets containing Data Objects and Data Attributes of Functional Constraint type CO as it is used for Control purpose.

Following precaution should be handled in the configured SCD file during Communication Engineering:

• For GCB Data Set, the signals must be assigned at Data Attribute (DA) level. Ensure that for each configured GCB Data Set, Quality (q), Time (t), and Signal Attribute is available. Time attribute is optional for GOOSE signals.For example: stVal, ctlModel, qSCD file import is cancelled, if the configured SCD file does not contain Signal Attribute.

• For RCB Data Set, the signals must be assigned at Data Object (DO) level that includes the attributes of the DO (Signal, Quality (t), and Time (t)).For example: Pos, EnaOpn, EnaCls

Section 2 CI868 Configuration CCF View

9ARD171385-600 A 31

Import Rules based on CI868 Access Point Criteria

For import of SCD file with multiple CI868 IEDs, right instance (access point) of CI868 IED must be selected in Control Builder. Table 2 describes the rules for importing SCD file based on CI868 Access Point criteria.

CCF View

The CCF view function helps in viewing the CCF file generated by IEC 61850 Wizard after successful SCD import. The CCF file is further used during restart of CI868 module to initialize IEC61850 stack.

Table 2. Import Rules based on CI868 Access Point Criteria

Action

DescriptionInvoke IEC61850 Wizard from Control

Builder

Select CI868 Access Point from SCD file in

IEC61850 Wizard

From CI868 IED at position n.

CI868 IED access point n. The CI868 access point n configuration from SCD file is updated to CI868 hardware position n in Control Builder.

From CI868 IED at position n.

CI868 IED access point x. Where x is not equal to n.

In Control Builder if there is no hardware object in position x, the SCD file is imported.

The Control Builder hardware objects of CI868 IED in position n is replaced by CI868 configuration from SCD file and CI868 hardware object position is changed to x.

In Control Builder if the hardware object is already existing in position x, the SCD file import is stopped.

IEC61850 Wizard displays a message, Aborting SCD file import. Control Builder contains other CI868 module with instance x.

CCF View Section 2 CI868 Configuration

32 9ARD171385-600 A

CCF tab view is displayed in IEC 61850 Wizard (see Figure 8). The All CCF Files panel displays the list of available CCF files / CI868 node for all the AC 800M controller in the tree view.

Select the CCF file of the access point to verify the number of datasets available in the corresponding CCF file.

Figure 8. CCF View

Figure 9. CCF View Datasets

Section 2 CI868 Configuration Handling SCD Re-configuration and Control Builder Tree Variation

9ARD171385-600 A 33

Click Ok to open the CCF file as a tree structure in the Selected CCF File tree view. Select the object or node in the CCF File tree structure, contents of the object are displayed in the property view (see Figure 10).

Handling SCD Re-configuration and Control Builder Tree Variation

To override / append / delete the IEC 61850 GOOSE / MMS communication representation that exists in Control Builder by importing a modified SCD file.

To import the modified SCD file, system displays the difference between existing IEC 61850 GOOSE / MMS communication representation in Control Builder and the gathered information from the SCD file.

Color codes are used in the TreeView Comparator for representing the variations.

It is recommended to have maximum of 150 datasets assigned to a single CI868 module (GCBs and RCBs) in SCD file.

A caution is displayed in CCF view, when the assigned datasets in CI868 exceeds 150.

Figure 10. CCF File Tree Structure

Handling SCD Re-configuration and Control Builder Tree Variation Section 2 CI868 Configuration

34 9ARD171385-600 A

Features of TreeView Comparator

The TreeView Comparator shows the Control Builder content and the new/updated content, gathered from the SCD file. These are presented on the left and right parts of the dialog.

The changed node has the option to view the changed parameter details (such as ProtocolInfo details of LN and CDC types). The details are displayed in property comparator dialog.

Different Color codes are used for representing the differences and commonalities between the two sides. The Color codes are:

Table 3. Color Codes

Color Description

Black Represents the node that is fixed and does not get affected by IEC61850 Import Wizard.

Pink Represents the node that is identical on both sides.

Light Green Represents a new node that is added in the current SCD file.

Red Represents a changed node that is available on both sides.

Blue Represents the node (available under CI868) in Control Builder M that will be deleted during the updation of SCD file content into the Control Builder M.

Figure 11. TreeView Comparator


9ARD171385-600 A 35


36 9ARD171385-600 A

Table 4 shows the basic rule of the comparison for each Hardware unit type.

Table 4. Basic Rule of the Comparison for each Hardware Unit Type

Representation Comparison Rule Color

Project Project name is always same on both sides. Black

Controllers No comparison will happen. Also this is fixed node. Black

Controller and Hardware AC 800M

Controller/AC 800M IED name will be used to identify the controller whether it is available on both sides.

Suppose controller (collected from SCD file) is not available in the Control Builder M, this controller and its sub tree will be considered as newly created in the SCD file.

Light Green

Suppose it is matching, controller node in the comparator will be shown that it is identical.

Pink

Suppose the controller is available in the Control Builder M and is not available in the tree which is created from the SCD file content.

Black


9ARD171385-600 A 37

CI868 The Access point/CI868 name will be used to identify the CI868 whether it is available on both sides in the same controller.

Suppose Access point/CI868 name (collected from SCD file) does not match with any CI868 (same controller) in the Control Builder M, this CI868 and its sub tree will be considered as newly created in the SCD file.

Light Green

Suppose CI868 is available in the Control Builder M and is not available in the SCD file, this CI868 and sub tree (MyIED, LN and CDC Group Hardware Unit) is shown in Black.

Black

Suppose Access point/CI868 is available on both sides, then the following details will be compared.

1. Access Point name.

2. IP Address.

3. Sub net mask.

4. Default Gateway.

5. SNTP Server 1 IP Address.

6. SNTP Server 2 IP Address.

If CI868 contents are same, the node is identical. Pink

Otherwise the node is knows as same but the contents are different.

Red

MyIED The CI868 has only one MyIED. Hence, the contents will be compared.

The value of the MyIED Name parameter will be compared.

The value of that parameter is same. Pink

The value of that parameter is not same. Red




38 9ARD171385-600 A

LD The MyIED has only one LD. Hence, the contents will be compared.

The value of the LD Name parameter will be compared.



LN The LN Name parameter will be used to identify the LN whether it is available on both sides in the same LD.

Suppose LN name (collected from SCD file) does not match with any LN (same LD) in the Control Builder M, this LN will be considered as newly created in the SCD file.

Light Green

Suppose LN is available on both sides, then the following details will be compared.

All the ‘protocol info’ parameters for the identified LN Type

Suppose LN contents are same, the node is identical. Pink

Otherwise the node is knows as same but the contents are different.

Red

IED The IED Name parameter will be used to identify the IED whether it is available on both sides in the same CI868.

The value of the IED Name parameter will be compared.



Receive Data block

All the ‘protocol info’ parameters for the identified Receive Data block Type.

Suppose Receive Data block contents are same, the node is identical.

Pink

Otherwise the node will be displayed as modified node. Red



Section 2 CI868 Configuration IEC 61850 Wizard Errors

9ARD171385-600 A 39

IEC 61850 Wizard Errors

IEC 61850 Wizard tool displays error messages while exporting CID / ICD file. These errors occur when the CI868 communication parameters are not configured in Control Builder M before export.

CID / ICD File Export Errors in IEC 61850 Wizard

Table 5 lists the possible IEC 61850 Wizard error messages during export operation.

Table 5. IEC 61850 Wizard Error Messages - CID / ICD Export

CI868 Configuration Error ScenarioError message displayed during ICD / CID

Export

CI868 configured without MyIED object. Configuration Incomplete.

Mandatory node (MyIED) not configured. Export will abort

CI868 configured with empty MyIED field in MyIED object.

Invalid name for MyIED - Empty field not allowed Export will abort

CI868 configured with MyIED field containing space character.

Invalid name for MyIED - Space characters not allowed

Export will abort

CI868 configured without any Logical Devices (LDs).

Configuration Incomplete.

Mandatory node (LD) not configured. Export will abort

CI868 configured with Logical Devices (LDs) name is blank or has a space.

Configuration invalid at LD node(s).

Refer IEC61850ImportWizard.log (C:\ABB Industrial IT Data\Engineer IT Data\Control Builder M Professional\LogFiles) for list of errors.

Export will abort

IEC 61850 Wizard Errors Section 2 CI868 Configuration

40 9ARD171385-600 A

IEC 61850 Wizard tool has an option to generate ICD or CID file. Based on the type of file selected, DataSets and GSEControl blocks are created under LN0 node of each logical device.

CI868 configured without Logical Nodes (LNs). Configuration invalid at LN node(s).

Refer IEC61850ImportWizard.log (C:\ABB Industrial IT Data\Engineer IT Data\Control Builder M Professional\LogFiles) for list of errors.Export will abort

CI868 configured without mandatory LN0. under LD

LN0 node not configured under <LD name>

Make sure that LN0 and LPHD LNs are configured under each LD

Export will abort

CI868 configured without mandatory LPHD under LD.

LPHD node not configured under <LD name>


Export will abort

CI868 configured without Mandatory LNs (LN0, LPHD).

Configuration Incomplete:

Mandatory logical nodes (LN0, LPHD) missing under <LD name>


Export will abort

CI868 configured with Logical Node (LNs) and Logical Device (LD) having; Invalid Name, Duplicate name, Space Character, or Special Symbols.

Configuration invalid in LD and LN nodes.

Refer IEC61850ImportWizard.log (C:\ABB Industrial IT Data\Engineer IT Data\Control Builder M Professional\LogFiles) for list of errors.

Export will abort

Table 5. IEC 61850 Wizard Error Messages - CID / ICD Export

CI868 Configuration Error ScenarioError message displayed during ICD / CID

Export


9ARD171385-600 A 41

SCD File Import Errors in IEC 61850 Wizard

IEC 61850 Wizard tool displays various errors while importing inconsistent SCD file. These errors occur when the CI868 communication parameters are not configured. Table 6 lists of IEC 61850 Wizard errors applicable during SCD file import operation.

Table 6. IEC 61850 Wizard Error Messages - SCD Import

Inconsistent SCD file Scenario Error message displayed during SCD file

import

IEC 61850 Wizard is opened with corrupted or missing dll file.

Could not load file or assembly ‘ABB.AC800M.IEC61850ET.SCDImporter, Version=5.1.1004.18, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system cannot find the file specified.

SCD file in the text file format. Invalid SCD File

More than one access point is available in CI868 IED.

There is more than one access point available under CI868 IED in the SCD File.

SCD file does not contain CI868 IED or AC800M IED.

SCD file does not contain AC800M IED or CI868 IED.

Access point is not available in SCD File. There is no access point available under IED in the SCD File.

Excess no. of GOOSE Control Blocks per CI868.

Excess number GOOSE Control Blocks for AccessPoint1 in CI868. The maximum Number of Goose Control Blocks allowed for an Accesspoint is 100 only.

SCD Import is cancelled.

LD is not available in SCD File. Error while importing the SCD file.


Excess no. of LN in a LD. LN Instance count exceeds the Max allowed (253) in the given SCD file.



42 9ARD171385-600 A

LD0 is not available in CI868 IED. Error while importing the SCD file.

SCD Import cancelled

LN0 is not available in a LDevice. Invalid SCD File

LPHD is not available in a LDevice. Aborting SCD File Import!

LPHD is not available under Logical Device

Server information is not available in Access Point.

Server is not available under access point 1 for IED AC800M in the SCD file.


SCD file has two CI868 IEDs having same instance name.

Invalid SCD File

Excess number of Data Set entries per Data Set.

Excess number of FCDA for AccessPoint <CI868 IED> in <Data Set Name>. The maximum FCDA allowed for an Dataset is 150 only.


Excess number of Data Attribute instances per CI868.

Excess number of DAI for Accesspoint <CI868 IED>. The maximum DAI allowed for an AccessPoint is 5500 only.


SCD file with an unsupported LN. Error while creating the LN Node into the Tree Model.

SCD import is cancelled.

SCD file with identical LNs under same LD. Invalid SCD File

SCD file has more than 10 LDs under a CI868 IED.

Number of LDs is more than 10 for AccessPoint <access point number>.

SCD import is cancelled



import


9ARD171385-600 A 43

SCD file has more than 100 IED per CI868. Excess number of IEDs under the accesspoint <access point number>.


SCD file has more than 50 LDs configured for CI868 MMS Receive per IED.

Number of MMS Ldevices is more than 50 in IED.


Signal and Quality attribute is not configured in the SCD file.

Refer IEC61850 Log for details of Data objects with missing Signal and quality attributes.

Due to missing Signal and q attribute in input section

SCD import is cancelled.

Excess number of LNs in the imported SCD file.

LN instance count exceeds the Max allowed (253) in the given SCD file.


IAL mapping template for Gateway Client is deleted from the running path of project.

IAL Mapping Template (.ICD) file not found at path C:\Program Files\ABB Industrial IT\Engineer IT\Compact Control Builder AC 800M 5.1\bin\IEC61850 Import Wizard\ICDFile\ISS.CDC.IALMappingTemplate_GatewayClient.icd

CCF file of CI868 is missing from the Control Builder M project folder.

CCF file is not created for the CI868 instance <CI868 IED > under controller < Controller name> in Control Builder.

CCF View is Cancelled.

Importing SCD file with ITCI LN, RCBs configured to CI868 using CI868 Hardware Library version less than or equal to 2.x.

Connected CI868 hardware library is not compatible with selected MMS configured SCD file.

SCD Import cancelled.



import


44 9ARD171385-600 A

IAL Mapping file is missing from its location. IAL Mapping Template (.ICD) file not found at path C:\Program Files\ABB Industrial IT\Engineer IT\Compact Control Builder AC 800M 5.1\bin\IEC61850 Import Wizard\ICDFile\ISS.CDC.IALMappingTemplate_GatewayClient.icd

Error message while creating Control Builder M Hardware Tree without installing Hardware Library.

The source code could not be read.

The object may have been deleted from another engineering station.

Refreshing the project may remedy this error.

SourceBlock: CI868IEC61850HwLib

Errormessage: The file C:\Program Files\ABB Industrial IT\Engineer IT\Compact Control Builder AC 800M 5.1\HWLibraries\CI868IEC61850HwLib-3-0-5.hwl does not exist.



import

9ARD171385-600 A 45

Section 3 CI868 Application Engineering

This section describes the application engineering for CI868 using Process Object Basic Lib Library. This library contains IEDCommandSend and IEDStatusReceive function blocks, that support SBO functionality in IEC 61131-3 programing.

CI868 MMS Control Function Block with IEC 61131-3ProcessObjectBasicLib Library provides IEDCommandSend and IEDStatusReceive function blocks.

IEDCommandSend object performs MMS based Select Before Operate function sequence to control Circuit Breakers or Switches and generate feedback timeout error boolean signals.

IEDStatusReceive object is used to receive status from IED devices and delivers actual feedback status to process object device blocks.

CI868 MMS control functionality is intended to perform operator commands from CI868 to other IEDs. This is achieved using CSWI and XCBR Logical Node objects available in CI868 hardware library.

The IEDCommandSend and IEDStatusReceive function blocks used in the Controller IEC 61131-3 Application connects and controls the IO channels of the node objects to IEC 61131-3 variables.

IEDCommandSend and IEDStatusReceive function blocks are the interface between standard Motor function blocks of other libraries (used in industries such as; Power Management Solutions, Pulp and Paper, Oil and Gas, and Process Control. etc) and the Hardware IO objects of CI868 module. These cannot be used as standalone function block.

The function blocks have no operator interaction, and have no faceplate or graphic element aspects. It has the safety level of Non-SIL.

IED Command Send Section 3 CI868 Application Engineering

46 9ARD171385-600 A

IED Command Send

IEDCommandSend representation in a function block (see Figure 12).

Table 7 lists the IEDCommandSend function block parameters.

Figure 12. IED Command Send

Table 7. IEDCommandSend function block parameters

Pin NameControl Builder

Datatype

Initial Value

Attributes Direction Definition

Mode Dint 2 Retain In Control Mode.

• 1: Direct Mode

• 2: SBO Mode.

Open Bool - Retain In Command Open / Off

Close Bool - Retain In Command Close / On

Cancel Bool - Retain In Cancel Selection

Section 3 CI868 Application Engineering IED Command Send

9ARD171385-600 A 47

Test Bool - Retain In Test Mode

ITL Bool - Retain In Run Interlock Check

SYN Bool - Retain In Run Synchro Check

SelStatus BoolIO - Retain In Selection status (Pos.stSeld)

PosStatus DintIO - Retain In Circuit Breaker position.

• 0: Intermediate

• 1: Open

• 2: Closed

• 3: Fault

SelTimeout Time 1s Coldretain In Selection timeout value in msec.

PosTimeout Time 1s Coldretain In Circuit Breaker position timeout value in msec.

CancelTimeout Time 0s Coldretain In Circuit Breaker cancel timeout value in msec.

CTLCMD DwordIO - Retain Out Output.

• Bit0: Select

• Bit1: Operate

• Bit2: Cancel

• Bit3: Test

• Bit4: ITL Run Interlock Chk

• Bit5: SYN Run Synchro Chk

• Bit11: Open

• Bit12: Close

Table 7. IEDCommandSend function block parameters (Continued)


Datatype

Initial Value



48 9ARD171385-600 A

IEDCommandSend functionality has two modes of operation.

• Direct Mode - Is active when Mode is 1

• SBO Control Mode - Is active when Mode is 2

– Direct Mode

In Direct mode, the function block reads the Open or Close input command from IEC 61131-3 application logic and operates irrespective of selection status feedback (SelStatus). The status of the feedback is monitored and compared to the actual output commands.

Mismatch is generated as Boolean outputs (CloseFailed or OpenFailed) after the configured time limit expires (PosTimeout).

– SBO Control Mode

In SBO Control mode, the function block generates Select and Cancel or Operate on Open or Close input command to confirm the selection of IED device.

On input command, the select output pulse is generated and the status is monitored. Select timeout output is generated after a time delay (SelTimeout) on failure of select status feedback, then the Cancel command input generates the Cancel output pulse, else the Operate output pulse is generated.

SelectFailed Bool - Retain Out Select Operation Failed

CloseFailed Bool - Retain Out Close Operation Failed

OpenFailed Bool - Retain Out Open Operation Failed

IOError Bool - Retain Out Input Channel Error

Table 7. IEDCommandSend function block parameters (Continued)


Datatype

Initial Value


Section 3 CI868 Application Engineering IED Command Send

9ARD171385-600 A 49

On generation of Operate output, the corresponding Open or Close output is generated based on Open/Close command input. The status of the feedback is monitored and compared to the output commands.

Mismatch is generated as Boolean outputs (CloseFailed/OpenFailed) after the configured time limit expires (PosTimeout).

Alarms and events are not generated from IEDCommandSend function block.

The error condition due to timeout and IO Channel are generated as Boolean output signals that can be connected the relevant standard Alarm / Event Function blocks in IEC 61131 -3 application.

Figure 13 shows a detailed sequence flow of IEDCommandSend function block.

Figure 13. IEDCommandSend Flowchart


50 9ARD171385-600 A

Section 3 CI868 Application Engineering IED Status Receive

9ARD171385-600 A 51

IED Status Receive

IED Status Receive representation in a function block (see Figure 14).

Table 8 lists the IEDStatusReceive Function Block parameters.

IED Status Receive function block receives status information from IED logical node through I/O channel and delivers the actual feedback status FB0 and FB1 with respect to input status (PosStatus). The quality status of the input (PosStatus) is copied into outputs FB0 and FB1.

Open feedback status (FB0) is set when PosStatus =1

Close feedback status (FB1) is set when PosStatus =2

Figure 14. IED Status Receive

Table 8. IED Status Receive Function Block parameters

Pin Name Datatype Initial value Attributes Direction Description

PosStatus DintIO - Retain In Command Status Input.

• 0: Intermediate

• 1: Open

• 2: Closed

• 3: Fault

FB0 BoolIO - Retain Out IED Open Feedback Status

FB1 BoolIO - Retain Out IED Close Feedback Status

Alarms and Events are not generated from IED Status Receive function block.

IED Status Receive Section 3 CI868 Application Engineering

52 9ARD171385-600 A

Following screen shot (see Figure 15) shows a sample IEC 61131 -3 Application based on UniSimple_1 function blocks for Select Before Operate (SBO) command, used for application logic to control circuit breakers.

The Out0 and Out1 parameter of UniSimple function block sends Open and Close command respectively, which is received by Open and Close input parameter of IEDCommandSend_1 function block. The CTLCMD parameter in IEDCommandSend function block sends the necessary Control Commands to the respective IED. The feedback from the IED is received by PosStatus parameter of

Figure 15. SBO Function Block - Offline

Section 3 CI868 Application Engineering IED Status Receive

9ARD171385-600 A 53

IEDStatusReceive function block and further sent to the UniSimple function block as actual feedback.

IEDCommandSend function block has additional monitoring outputs SelectFailed, CloseFailed, OpenFailed and IOError can be connected to AlarmCond, AlarmCondBasic or SimpleEventDetector external function blocks to generate Alarms and Events as per project requirements.

CancelTimeout is used to delay the operate command, when selected feedback from IED is active.

• If the Cancel input is received within CancelTimeout time:

– Cancel with Open commands are sent

or

– Cancel with Close commands are sent.

• If the Cancel input is received after CancelTimeout time:

– Operate with Open commands are sent

or

– Operate with Close commands are sent.

The configured value for CancelTimeout must be lower than the duration of stSeld staying active on a selection in respective IED.

The configured value in the IEDCommandSend function block for SelTimeout must be greater than the duration of stSeld staying active on a selection in respective IED.

The configured value IEDCommandSend function block for PosTimeout must be greater than the duration of configured SelTimeout value.

IED Status Receive Section 3 CI868 Application Engineering

54 9ARD171385-600 A

Figure 16. SBO Function Block - Online

Section 3 CI868 Application Engineering CI868 Support for Sequence of Event (SOE)

9ARD171385-600 A 55

CI868 Support for Sequence of Event (SOE) CI868 module supports Sequence of Events for incoming Circuit Breaker position status containing IED Time Stamps (External Time Stamp) reported from other IED.

The IEDs associated with the Circuit Breaker IEDs adds a time stamp value along with status value and updated in RCB dataset whenever a change in Circuit Breaker position is detected.

CI868 module captures this status and external time stamp value assigned as IEC 61131 - 3 variable in CSWI or XCBR LN objects and generates respective External Events.

These External Events can be used as input for AlarmCond and SimpleEventDetector function block in IEC 61131 -3 application to generate Alarm and Events.

In this way the Alarm and Events generated from External Events will have the following attribute:

• Alarm and Event with Time stamp of IED instead of AC 800M Controller.

• Alarm and Events with source objects mapped to the process Object or Conducting Equipment instead of CSWI or XCBR hardware object library in Control Builder tree.

• Alarm and Events generated as process Alarm and process Events instead of System Alarm and System Events, thereby allowing further categorization of process Alarm and Event in Alarm and Event list.

Table 9 describes the External Events that are generated for each Circuit Breaker associated with CSWI or XCBR hardware object.

Each CSWI hardware object has IO channels that can be associated to four Circuit Breaker such as; Pos, PosA, PosB, and PosC.

CI868 Support for Sequence of Event (SOE) Section 3 CI868 Application Engineering

56 9ARD171385-600 A

CI868 Module also includes functionality to generate Signal IDs.

• Signal ID Hardware Address format:

CIPos(1-12).IEDPos(1-n).LDPos(1-n).CSWI_LNPos(1-n).BreakerNumber(1-4)

• Signal ID Breaker Number format:

Breaker Num (1-4)

For example. 1.2.201.9.E_Cls

Table 9. AC 800M Controller External Events

Circuit Breaker Position value

External Event External Event Signal ID

Circuit Breaker position - Faulty

Faulty Alarm <HwAddress>.<BreakerNumber>.A_Flt

for example: 1.2.201.9.1.A_Flt

Circuit Breaker position - Close

Close Event <HwAddress>.<BreakerNumber>.E_Cls

for example: 1.2.201.9.1.E_Cls

Circuit Breaker position - Open

Open Event <HwAddress>.<BreakerNumber>.E_Opn

for example: 1.2.201.9.1.E_Opn

Circuit Breaker position - Intermediate

Intermediate Event <HwAddress>.<BreakerNumber>.E_Int

for example: 1.2.201.9.1.E_Int

Circuit Breaker Selection Status

Selection Event <HwAddress>.<BreakerNumber>.E_Sel

for example: 1.2.201.9.1.E_Sel

The external timestamp is available only for Circuit Breaker Pos.Status and is not supported for Circuit Breaker Selection Status.

Section 3 CI868 Application Engineering Configuration for Alarm and Events

9ARD171385-600 A 57

Configuration for Alarm and Events

Following screen shot (see Figure 17) depicts the overall CI868 configuration applicable to generate External Events for Circuit Breaker position Status.

Further the Generate Alarms parameter for the respective IED is set to Enabled, which is also the default setting. Setting to Disabled does not generate any External Events from the respective IED.

Figure 17. Hardware Address and Signal ID Mapping

Any changes done under a particular CI868 Hardware Object in the Control Builder tree structure will restart the CI868 module.

IEC 61131 -3 Application for External Events Section 3 CI868 Application Engineering

58 9ARD171385-600 A

IEC 61131 -3 Application for External Events

Following screen shot (see Figure 19 and Figure 21) shows a sample IEC 61131 -3 Application to generate Process Alarms and Events out of External Events.

Figure 18. Generate Alarms in IED Hardware object

Figure 19. Alarm Condition Function Block - Offline

Section 3 CI868 Application Engineering IEC 61131 -3 Application for External Events

9ARD171385-600 A 59

Figure 20. Alarm Condition Function Block - Online


60 9ARD171385-600 A

Figure 21. Simple Event Detector Function Block - Offline

Section 3 CI868 Application Engineering IEC 61131 -3 Application for External Events

9ARD171385-600 A 61

Figure 22. Simple Event Detector Function Block - Online

The External Events appear as System Events with the hardware address of circuit breaker as Object Source and Controller Timestamp, without the IEC 61131 -3 application.


62 9ARD171385-600 A

9ARD171385-600 A 63

Section 4 CI868 Engineering

Representing CI868 Operating Status as an IED: LN0, LPHD

All Logical Devices must contain a Controlling Logical Node named LN0. It contains the Data Objects Behavior and Health that can be published with GOOSE.

A Logical Device can also contain a Logical Node that represents the physical device named LPHD.

LPHD contains the Data Object Device Health that can be published with GOOSE. There are hardware units representing LN0 and LPHD. These can be placed as subunits to the Logical Devices like any Logical Node.

User can decide to use the hardware units for LN0 and LPHD in the IEC 61131-3 application by collecting information about the operation status of the AC 800M in general. In addition to the IEC 61850 specific Data Object channels, LN0 also contain diagnostic channels. For details, refer to CI868 IED Diagnostic Information on page 102.

Representing CI868 Operating Status as an IED: LN0, LPHD Section 4 CI868 Engineering

64 9ARD171385-600 A

LN0 is the Controlling Logical Node for all Logical Nodes under a Logical Device. It has the Data Objects/channels (see Table 10).

Table 10. LN0 Channel Details

CI868 Channel NameIEC 61850 Attr. Name

Explanation

IEC 61850 Attr. Type (CDC

Type)

IEC 61131-3 Variable Type

Mod Mode Output: This represents the mode of the Logical Device (LD).

INC DintIO

Beh Behavior INS DintIO

Health Health INS DintIO

GOOSE Values Received - - DintIO

GOOSE Values Sent - - DintIO

GOOSE Values Received Per Second

- - DintIO

GOOSE Values Sent Per Second

- - DintIO

CPU Load - - DintIO

Sender Cycles Per Second - - DintIO

MMS Values Received - - DintIO

MMS Commands Sent - - DintIO

Report Control Blocks Received Per Second

- - DintIO

Number of IEDs Configured for Reporting

- - DintIO

Number of IEDs Connected for Reporting

- - DintIO

Number of Buffered Report Control Blocks Configured

- - DintIO

Section 4 CI868 Engineering Cross Referencing IEC 61850 Data with IEC 61131-3 Variables

9ARD171385-600 A 65

LPHD is the Logical Node with Physical Device Information. It has the Data Objects/channels (see Table 11).

Cross Referencing IEC 61850 Data with IEC 61131-3 Variables

For Data Subscribed by CI868 (Signal in an IED to IEC 61131-3)

The steps involved in making a cross reference between IEC 61850 data, subscribed by CI868 from other IEDs, and the IEC 61131-3 variables used in the logic are explained below:

Number of Buffered Report Control Blocks Enabled

- - DintIO

Number of Unbuffered Report Control Blocks Configured

- - DintIO

Number of Unbuffered Report Control Blocks Enabled

- - DintIO

Table 11. LPHD Channel Details

CI868 ChannelName

IEC 61850Attr. Name

Explanation

IEC 61850Attr. Type

(CDC Type)

IEC 61131-3Variable

Type

PhyHealth Physical Health INS IntIO

Table 10. LN0 Channel Details (Continued)

CI868 Channel NameIEC 61850 Attr. Name

Explanation

IEC 61850 Attr. Type (CDC

Type)


For Data Subscribed by CI868 (Signal in an IED to IEC 61131-3) Section 4 CI868 Engineering

66 9ARD171385-600 A

1. Operate Data of Logical Node PHPIOC from IED AA12 is sent to CI868.

Figure 23. CCT with Operate Data

2. Operate Data is the part Dataset StatNrml.

3. AA1A1 is the AC 800M IED that receives Operate Data. This data is reflected as shown in Figure 24.

Figure 24. CCT with Client IED

Section 4 CI868 Engineering For Data Subscribed by CI868 (Signal in an IED to IEC 61131-3)

9ARD171385-600 A 67

4. AA1A1 is part of the client IED. This can be verified by checking the input section of AA1A1 IED (see Figure 25.

Figure 25. CCT with Input Section

5. The SCD file is represented in the IEC 61850 wizard (see Figure 26). The IED that sends the data (in this case it is AA12) is shown in small circle in

For Data Subscribed by CI868 (Signal in an IED to IEC 61131-3) Section 4 CI868 Engineering

68 9ARD171385-600 A

Figure 26.

Figure 26. TreeView Comparator with IED and Protocol Information

6. Under Protocol Information (see Figure 26), each protocol info field shows which IED positioned in which Substation / Voltage / Bay is providing the data to the CI868 IED.

Section 4 CI868 Engineering For Data Subscribed by CI868 (Signal in an IED to IEC 61131-3)

9ARD171385-600 A 69

7. In Control Builder tree structure IED AA12 is populated (see Figure 27). The protocol information field shows the details of the data from where it is being sent.

Figure 27. Control Builder with IED AA12

8. Connect IEC 61131-3 variable in the variable field. The data from the IED is presented to the IEC 61131-3 application running in the AC 800M controller.

For Data Published by CI868 (IEC 61131-3 Signal to IED) Section 4 CI868 Engineering

70 9ARD171385-600 A

For Data Published by CI868 (IEC 61131-3 Signal to IED)

The steps involved in making a cross reference between IEC 61131-3 variables used in the logic and published by AC 800M to other IEDs over IEC 61850 are explained:

1. Operate Data of Logical Node LS PTRC of AC 800M IED (AA1A1) is sent to IEDs.

Figure 28. CCT with Operate Data for Sending

2. Operate Data is the part of Dataset AA1A1_DS.

Section 4 CI868 Engineering For Data Published by CI868 (IEC 61131-3 Signal to IED)

9ARD171385-600 A 71

3. IED AA11, AA12 and AA13 are the receiving IEDs as shown under Client IED (see Figure 29).

Figure 29. CCT with Operate Data for Receiving

4. The SCD file is represented in the IEC 61850 wizard (see Figure 30). IED that sends the data (in this case it is AA1A1) is shown in a circle. The data from LS PTRC is sent to the IEDs as shown in the protocol information field.

Figure 30. TreeView Comparator with IED AA1A1

CI868 IED as IEC 61850 MMS Client Section 4 CI868 Engineering

72 9ARD171385-600 A

5. The protocol info field shows which IEDs positioned in which Substation / Voltage / Bay is receiving the data to the CI868.

6. In Control Builder tree structure MyIED AA1A1 is populated (see Figure 31). The protocol information field shows the details of the data to where it is being sent.

Figure 31. Hardware Editor

7. Data from CI868 is being sent to the Partner IED in the network.

CI868 IED as IEC 61850 MMS ClientCI868 module supports MMS client functionality on IEC 61850 network. MMS client is defined on each IED MMS server with definition of RCBs. A single IEC 61850 subnetwork is configured with one CI868 module. Additional CI868 is used for same IEC 61850 subnetwork for handling data transfer beyond the recommended limits per CI868.

IEC 61850 Wizard tool imports the SCD files configured with CI868 as RCB client and generate hardware tree in Control Builder containing MMS objects. Each MMS

AC 800M Process module communicates through MMS for inter-controller and Control Builder communication. With MMS functionality now included on CI868, it is recommended not to combine IEC 61850 network (CI868) with AC 800M Control network.

Section 4 CI868 Engineering CI868 Data Receive through MMS

9ARD171385-600 A 73

client (CI868 through ITCI) can be connected to these RCBs during communication configuration.

CI868 Data Receive through MMS

MMS Reporting is receiving the Report Control Block from the IEDs to CI868 IED. Hardware file containing all Data objects (Mandatory and Optional) are created to support the LN representations for MMS Reporting.

SCD file contains the Report Control Blocks that are configured during communication engineering. IEC61850 Wizard tool creates logical node representation for MMS Signal along with GOOSE Receive Blocks in the Control Builder tree view for the IEDs that are sending data through MMS to CI866 IED. The logical node (for example. PTOC, PTTR etc) contains only the MMS signals that are received by CI868 IED (only those signals for which CI868 IED is a MMS client).

In Control Builder CI868 IED Tree view (see Figure 3), the Logical Nodes LLN0 and LPHD appear under other IEDs.

This indicates that CI868 IED receives signals from LPHD and LLN0 Logical Nodes assigned to CI868.

CSWI and XCBR LN representation supports both receive signal information and send command.

From each data object received through MMS, the attributes stVal and q can be used for the controller application.

The attribute t is not supported for IEC 61131-3 control application program.

CI868 Control Commands through MMS Section 4 CI868 Engineering

74 9ARD171385-600 A

CI868 Control Commands through MMS

LN ITCI (Telecontrol Interface) when configured under CI868 module represents CI868 IED as MMS client in an IEC 61850 network.

MMS Control commands are supported only for Pos in CSWI and XCBR logical node. CSWI and XCBR data object belongs to DPC object type and so only DPC is supported for control commands. If LN representation supports Control Commands, it can send MMS commands to other IED as well as receive RCBs.

MMS Control functionality is available for IEC 61131-3 function blocks such as motor control to send ON/OFF commands via CI868 IED to other IEDs with motor feeder application to control the Circuit Breaker for ON/OFF. For this process, the MMS Client functionality supports IEC 61850 Direct and Select Before Operate type of control commands (send).

Figure 32 represents hardware editor of XCBR logical node.

Figure 32. XCBR Hardware Editor - Control Command

Section 4 CI868 Engineering CI868 Control Commands through MMS

9ARD171385-600 A 75

Table 12. XCBR Control Commands Channels

Control Builder Channel

Name

Data Type / Direction

IEC61850 Data Object

Description

Pos_CTLCMD DwordIO / Out

XCBR.Pos.SBOw/Oper/Cancel

• Bit 0 = Select

• Bit 1 = Operate

• Bit 2 = Cancel

• Bit 3 = Test

• Bit 4 = ITL Run Interlock Check

• Bit 5 = SYN Run Synchro Check

• Bit 6 to 10 = Reserved

• Bit 11 = Open Command

• Bit 12 = Close Command

• Bit 13 to 31 = Not Used


76 9ARD171385-600 A

Pos_stSeld BoolIO / In XCBR.Pos.stSeld stSeld is part of the SBO (Select Before Operate) sequence.

This is the feedback channel for Control command.

IED Selection Status

• True = Selected

• False = Not Selected

Pos_stVal DintIO / In XCBR.Pos.stVal This is the feedback channel for Control command.

Circuit Breaker Position Status

• 0 = Intermediate

• 1 = Open

• 2 = Closed

• 3 = Fault

stVal is a reference for all other actions. It shows the actual status of LN functionality.

Updates controller application (e.g. Motor/Pump-FP).

Controls the function via controller application (e.g. Motor/Pump-FP) from process operation faceplate.

Other channel names are not applicable for operational functionality.

Table 12. XCBR Control Commands Channels (Continued)


Name



Description


9ARD171385-600 A 77

Figure 33 represents hardware editor of CSWI logical node.

Figure 33. CSWI Hardware Editor - Switch Position

CSWI and XCBR logical node support both MMS Control commands and MMS Receive, all the other LN representations (for eg: PTRC, MMXU) support only receiving RCBs. Sending Control Commands is possible only from data attribute Pos of CSWI and XCBR.


78 9ARD171385-600 A

Table 13. CSWI Switch Position Control Channels


Name



Description

Pos_CTLCMD DwordIO / Out

CSWI.Pos.SBOw/Oper/Cancel

• Bit 0 = Select

• Bit 1 = Operate

• Bit 2 = Cancel

• Bit 3 = Test

• Bit 4 = ITL Run Interlock Check

• Bit 5 = SYN Run Synchro Check

• Bit 6 to 10 = Reserved

• Bit 11 = Open Command

• Bit 12 = Close Command

• Bit 13 to 31 = Not Used


9ARD171385-600 A 79

Pos_stSeld BoolIO / In CSWI.Pos.stSeld stSeld is part of the SBO (Select Before Operate) sequence.

This is the feedback channel for Control command.

IED Selection Status

• True = Selected

• False = Not Selected

Pos_stVal DintIO / In CSWI.Pos.stVal This is the feedback channel for Control command.

Circuit Breaker Position Status

• 0 = Intermediate

• 1 = Open

• 2 = Closed

• 3 = Fault

stVal is a reference for all other actions. It shows the actual status of LN functionality.

Updates controller application (e.g. Motor/Pump-FP).

Controls the function via controller application (e.g. Motor/Pump-FP) from process operation faceplate.

Other channel names are not applicable for operational functionality.

Table 13. CSWI Switch Position Control Channels (Continued)


Name



Description

IEC 61850 Protocol Information in I/O channel Section 4 CI868 Engineering

80 9ARD171385-600 A

IEC 61850 Protocol Information in I/O channel

IEC61850 Wizard updates the protocol info column for each hardware object with SCD file import. Protocol Info for a particular I/O channel displays the recipients of sent data and the source of received data in the hardware editor. This field provides the complete identification of the receiving and sending IEDs as configured in the SCD file. I/O channel receives and sends the data only if the variable is manually assigned.

Use the Hide Unused Channels option to hide the IO channels that have empty Protocol Info for all the Hardware objects in CI868 hardware library.

Control Builder hardware object LN-ATCC Data Object name attribute is corrected from Vol to CtlV according to IEC61850 specification.

When a Control Builder project is migrated from previous version, the ATCC LN Hardware Object (under CI868 MyIED object) containing Vol channel is automatically updated to new CtlV channel and the previously connected Protocol info for the Vol channel is retained in the new CtlV channel.

However after migration, if scd file containing ATCC LN as Data Object name Vol is imported in new Control Builder version, the protocol info for CtlV channel under ATCC LN Hardware Object is missing due to the correction implemented in ATCC LN Hardware Object.

To retain the communication for the ATCC CtlV channel, before importing SCD file, ensure that the Data Object name under ATCC LN is corrected from Vol to CtlV in SCD file via XML Marker tool (see Figure 34, Figure 35 and Figure 36).

Section 4 CI868 Engineering IEC 61850 Protocol Information in I/O channel

9ARD171385-600 A 81

Figure 34. SCD file - Logical Node ATCC, DataSet Level


82 9ARD171385-600 A

Figure 35. SCD file - Logical Node ATCC, Inputs Section level

Section 4 CI868 Engineering IEC 61850 Protocol Information in I/O channel

9ARD171385-600 A 83

Protocol information for each Data Object (channel) in the logical nodes under MyIED is in the following format:

• Logical Node

Logical Node channel displays the GOOSE Send signals from CI868 to other IEDs on IEC 61850 network.

Protocol information for the GOOSE Send under MyIED is in the following format: SubNetworkName.IEDName.

Figure 36. SCD file - Logical Node ATCC, LN Level


84 9ARD171385-600 A

Protocol information for GOOSE receive blocks under IED is in the following format:

SubNetworkName.IEDName.LogicalDeviceName.LogicalNodeName.DataObjectName.

Figure 38. Hardware Editor - Protocol Information of GOOSE Receive Signals

Protocol information for MMS is assigned under respective IO channel of LN object and is in the following format: SubNetworkName.IEDName.LogicalDeviceName.LogicalNodeName.attributename.

Figure 37. Hardware Editor - Protocol Information of GOOSE Send Signals

For GOOSE Command Send from CI868 to multiple IEDs, the protocol info for all IEDs are concatenated in the same IO channel.

Figure 39. Hardware Editor - Protocol Information of MMS Signals

Protocol Info field is blank, if the data on the sending and receiving channel are not subscribed.

Section 4 CI868 Engineering Supported AC 800M Data Types

9ARD171385-600 A 85

Supported AC 800M Data TypesFollowing data types are supported by IEC 61131-3 application for I/O variables.

• BoolIO

• DintIO

• RealIO

• DwordIO

GOOSE Send and Receive

GOOSE Send and Receive supports the following CDC types:

• GOOSE Send - SPS, DPS, INS, MV, ACT, ACD, SPC, DPC, INC and BSC.

• GOOSE Receive - SPS, DPS, INS, MV, ACT and ACD.

GOOSE Send and Receive Section 4 CI868 Engineering

86 9ARD171385-600 A

Table 14 lists GOOSE Logical Node CDC types mapped into IEC 61131-3 variable.

Table 14. Data Type Mapping for GOOSE Send and Receive LNs in Control Builder

IEC61850 Attr. Type (CDC Type)

Supported DAsIEC 61131-3

Variable TypeGOOSE

SendGOOSE Receive

SPS stVal BoolIO

q

t

DPS stVal DintIO

q

t

INS stVal DintIO

q

t

MV mag.f RealIO

q

t

ACT general BoolIO

q

t

ACD general BoolIO

q

t

Section 4 CI868 Engineering CI868 MMS Receive LN Representations

9ARD171385-600 A 87

CI868 MMS Receive LN Representations

For MMS receive signals, the LN hardware object are instantiated under the CI868 Control Builder hardware tree. All LNs under IEC61850 specification (Edition -1) are available as hardware object for instantiation. Under each LN, mandatory and optional Data Objects are supported. Under each data Object, only mandatory Data Attributes are supported.

SPC stVal BoolIO

q

t

DPC stVal DintIO

q

t

INC stVal DintIO

q

t

BSC stVal DintIO

q

t

Quality is internally set by the Communication Interface firmware based on error conditions.

IEC 61850 Stack updates the Time while sending. It cannot be set from IEC 61131-3 application.

Table 14. Data Type Mapping for GOOSE Send and Receive LNs in Control Builder


Supported DAsIEC 61131-3

Variable TypeGOOSE

SendGOOSE Receive

CI868 MMS Receive LN Representations Section 4 CI868 Engineering

88 9ARD171385-600 A

For more information on supported CDC type and the logical node channels, refer to Appendix A, MMS Logical Node Channels.

Figure 40. CSWI Hardware Editor

Section 4 CI868 Engineering CI868 MMS Control Commands

9ARD171385-600 A 89

CI868 MMS Control Commands

Table 15. Data-type Mapping for Control Commands in Control Builder

IEC61850 CDC Type Supported DAs IEC 61131-3 Variable Type

DPC SBOw.ctlVal DwordIO

SBOw.origin.orCat

SBOw.origin.orIdent

SBOw.ctlNum

SBOw.T

SBOw.Test

SBOw.Check

Oper.ctlVal

Oper.origin.orCat

Oper.origin.orIdent

Oper.ctlNum

Oper.T

Oper.Test

Oper.Check

Cancel.ctlVal

Cancel.origin.orCat

Cancel.origin.orIdent

Cancel.ctlNum

Cancel.T

Cancel.Test

MMS control commands supports DPC CDC type. Table 15 Lists MMS control command CDC type mapped into IEC 61131-3 variable.

CI868 Configuration Parameters Section 4 CI868 Engineering

90 9ARD171385-600 A

CI868 Configuration Parameters

Data Attribute, Quality and Time Stamp for Send and Receive Data Objects

Data Objects are not simple values. A Data Object consists of Data Attribute, Quality and Timestamp.

For GOOSE communication, three attributes are relevant:

• Actual value (Data attribute).

• Quality.

• Timestamp (optional): User can decide if the Data attribute needs to be sent with or without timestamp.

In IEC 61850 systems, the function that produces a value is also responsible for producing a corresponding quality information. The quality contains a number of flags.

The GOOSE data is sent from the AC 800M IED without status.

The implementation does not support writing timestamp of the data from the IEC 61131-3 application. However, there is a possibility for the system engineer to decide if the Data Object signal should be sent with timestamps by choosing the time data attribute of the object included in the GOOSE dataset in CCT.

The implementation does not have the ability to read anything other than the data value and its status. The receiving timestamp of the Data Object from other IED cannot be brought into the IEC 61131-3 application.

Section 4 CI868 Engineering Data Quality for Received Data

9ARD171385-600 A 91

Data Quality for Received Data

Table 16 shows the quality bits that are used in GOOSE messages for SPS, DPS, INS and measured values. IEC 61850 protocol column specifies the quality bit as per the standards.

Table 16. 61850 Quality Bits

IEC 61850 Quality signal Bit Position

Description of Bit

0 Validity00=Good 01=Bad

1

2 Overflow

3 OutOfRange

4 Bad Reference

5 Oscillatory

6 Failure

7 Old Data

8 Inconsistent

9 Inaccurate

10 Source

11 Test

12 Operator Blocked

Channel status, when the incoming GOOSE message quality is bad: 0x100010 (quality bits 6 - 7 are set to 0 and 1 respectively and ISP /OSP (bit 20) is set during channel error).

Channel status, when the incoming GOOSE message quality is good: 0xC0 (quality bits 6 - 7 are set to 1 and 1 respectively).

The reserved bits are not shown in the table above.

CI868 IED Parameters Section 4 CI868 Engineering

92 9ARD171385-600 A

The quality value for the data that AC 800M receives from other IEDs is shown in the status component of the I/O variable type connected to the receive block channels.

Data and status of a particular channel in a Logical Node can be viewed by connecting the IEC 61131-3 I/O type variable to the channel. I/O Status register can indicate only good or bad (channel error) channel status.

The mask value for the status is given in such a way that, whenever any one of the IEC 61850 quality bits (0-9) (see Table 16) is set, the I/O copy routine will be informed to set the IEC 61131-3 status of the channel to channel error with the ISP bit set (0x100010). When none of the above bits (0-9) are set, it will be informed to set the status to good (0xC0).

Bit 11(Test bit) and Bit 12(Operator blocked) of the receiving GOOSE are obtained by subscribing to the behavior Data Object of the LN0 node. Bit 10(substituted or source) is ignored.

CI868 IED Parameters

All applicable configuration of the CI868 and the hardware units under the CI868 tree is done by the IEC 61850 Wizard, based on the imported SCD file. Table 17 to Table 20 shows the configuration parameters of the hardware units imported.

Table 17. CI868 IED Communication Configuration

Parameter Description

Access Point Name Access point number

IP Address Primary CI868 IP Address

Subnet Mask Primary Subnet Mask

SCD File Identification SCD modified date and time

Subnetwork Name Name of the Subnetwork

IP Address IP Address for the IED.

Section 4 CI868 Engineering Supported Logical Nodes

9ARD171385-600 A 93

Supported Logical Nodes

Among the types of Logical Nodes that IEC 61850 -Ed1 (Edition1) standard describes, only a certain number of them are considered to be relevant for an AC 800M to implement. For different types of applications, different types of Logical Nodes are considered relevant to be used. The types of Data Objects used in the Logical Nodes also differs between applications.

A number of types of applications with communication to IEC 61850 IEDs are foreseen to be relevant to implement in an AC 800M controller. For each type of application, one or more relevant Logical Nodes are foreseen with a fixed set of Data Objects. For these, there are specific HWD files. The following sections describe the Logical Nodes that are implemented.

Table 18. Project IED Name Configuration


MYIED name IED name given to the CI868 IED

Description Description used for the ICD file export

Table 19. LD Configuration Parameters


LD Name Name for the Logical device.


Table 20. LN configuration parameters


LN Name Name for the Logical node.


Supported Logical Nodes Section 4 CI868 Engineering

94 9ARD171385-600 A

Load Shedding Applications

Two Logical Nodes for Load Shedding applications:

LS GAPC is a GAPC logical node with the Data Objects/channels (see Table 21).

Table 21. LS GAPC Channel Details

AC 800M Channel Name

IEC 61850 Attr. Name Explanation

IEC 61850 Attr. Type (CDC Type)


Str Start of Operation ACD BoolIO

Op Operate of Function ACT BoolIO

Table 22. LS PTRC Channel Details






Tr1 Trip Signal ACT BoolIO

Tr2

Tr3

Tr4

Tr5

Tr6

Tr7

Tr8

Tr9

Tr10


9ARD171385-600 A 95

Generator Real Power Control

PC GAPC is a GAPC logical node for Generator Real Power Control with the Data Objects/channels (see Table 23).

Table 23. PC GAPC Channel Details







SPCSO1 Frequency (Speed) Raise Command Information

SPC BoolIO

SPCSO2

Watt Real Power set Point Information

MV RealIO

Hz Frequency Set Point Information

MV RealIO


96 9ARD171385-600 A

Bus Bar Change

BB GAPC is a GAPC logical node for Bus Bar Change with the Data Objects/channels (seeTable 24).

Table 24. BB GAPC Channel Details







SPCSO1 Bay Control Command Information

SPC BoolIO

SPCSO2

SPCSO3

SPCSO4

SPCSO5

SPCSO6

SPCSO7

SPCSO8

SPCSO9

SPCSO10


9ARD171385-600 A 97

Transformer Tap Control

TC1 ATCC is an ATCC logical node for Transformer Tap Control with the Data Objects/channels (see Table 25).

TC2 ATCC is an ATCC logical node for Transformer Tap Control with the Data Objects/channels (see Table 26).

Table 25. TC1 ATCC Channel Details




IEC 61131-3 Variable

Type

Loc Local operation SPS BoolIO

ParOp Parallel/ Independent operation

DPC DintIO

CtlV Voltage Set Point Information

MV RealIO

SPCSO1 Tap Raise Command Information

SPS BoolIO

SPCSO2 Tap Lower Command Information

SPCSO3 Stop Command Information







ParOp Mode of Operation DPC DintIO


98 9ARD171385-600 A

Generator Reactive Power Control

QC ARCO is an ARCO logical node for Generator Reactive Power Control with the Data Objects/channels (see Table 27).

CtlV Voltage Set Point Information

MV RealIO

ISCSO Tap Position Command Information

INC DintIO

Table 27. QC ARCO Channel Details

Channel (Data Object)







SPCSO1 Voltage Raise Command Information

SPC BoolIO

SPCSO2

Vol Voltage Set Point Information

MV RealIO

VolAmpr Reactive Power set Point Information

MV RealIO

PwrFact Power Factor Set Point Information

MV RealIO



9ARD171385-600 A 99

QC1 ARCO is an ARCO logical node for Generator Reactive Power Control with the Data Objects/channels (see Table 28).

Bus Bar Voltage Control

VC AVCO is an AVCO logical node for Bus bar voltage control with the Data Objects/channels (see Table 29).

Table 28. QC1 ARCO Channel Details









MV RealIO

VolAmpr Reactive Power set Point Information

MV RealIO

PwrFact Power Factor Set Point Information

MV RealIO

TapChg Change reactive power. BSC DintIO

Table 29. VC AVCO Channel Details





Loc Local Operation SPS BoolIO



SPCSO1 Voltage Raise Command Information

SPC BoolIO

SPCSO2


100 9ARD171385-600 A

VC1 AVCO is an AVCO logical node for Bus bar voltage control with the Data Objects/channels (see Table 30).

SPCSO3 Stop Command Information

SPC BoolIO


MV RealIO

Table 30. VC1 AVCO Channel Details





Loc Local Operation SPS BoolIO




MV RealIO

TapChg Change reactive power. BSC DintIO

Table 29. VC AVCO Channel Details


9ARD171385-600 A 101

Generic Logical Nodes

GF GGIO is a GGIO logical node for General Purpose with the Data Objects/channels (see Table 31).

Table 31. GF GGIO Channel Details





SPCSO1 Single Point Command Information

SPS BoolIO


ACD

SPCSO3 ACT


SPC

SPCSO5 SPC

DPCSO1 Double Point Command Information

DPC DintIO

DPCSO2

DPCSO3

DPCSO4

DPCSO5

ISCSO1 Integer Value Set Point Command Information

INC DintIO

ISCSO2

ISCSO3

ISCSO4

ISCSO5

Application Redundancy Section 4 CI868 Engineering

102 9ARD171385-600 A

Application RedundancyApplication redundancy is achieved by using two CI868 modules such as, AC 800M with two access points, connected in the same sub network and cable redundancy using external switches which supports rapid spanning tree protocol.

• Create a Feeder Block Diagram with the sending logical nodes in IET and connect the FBD to one Access point, copy the same FBD and connect to the second access point which is in the same sub network as the first one.

• Export the configuration to communication configuration tool and create the same datasets under LN0 for the two access points.

• Create the same input under LN0 of the access points by dragging the subscribed IED to the two access points respectively.

• The Wizard creates the tree structure with two CI868 in the Control builder.

• Create an application to receive data from one access point and switch to another access point data in case of channel error or CI868 failure.

• The application writes the data to both the access points but read from only one of the two access points.

CI868 IED Diagnostic InformationDiagnostic information is available in LN0 hardware object. To view diagnostics, traverse to the LN0 hardware unit to open the Hardware editor and click the connection tab to view the diagnostic information.

AnIn1 Real Value Information MV RealIO

AnIn2

AnIn3

AnIn4

AnIn5

Table 31. GF GGIO Channel Details (Continued)

Section 4 CI868 Engineering CI868 IED Diagnostic Information

9ARD171385-600 A 103

The Diagnostic information contains details about RCBs and GOOSE Signal provided by IEC61850 stack.

Further individual IED level diagnostics for MMS is available under Diag object under each IED.

Figure 41. LN0 Hardware Editor With Diagnostics Information

Figure 42. Diag Hardware Editor With Diagnostics Information

CI868 IED Diagnostic Information Section 4 CI868 Engineering

104 9ARD171385-600 A

Table 32 describes the MMS diagnostics information available.

Table 32. LN0 and Diag Hardware editor diagnostics information

Diagnostics Information Description

LN0 Diag info

GOOSE values received Number of GOOSE data values received from other IEDs.

GOOSE Values Sent Number of GOOSE data values sent to other IEDs.

GOOSE Values Received Per second

Number of GOOSE values received from other IEDs per second.

GOOSE Values Sent Per Second

Number of GOOSE values sent to other IEDs per second.

CPU Load CPU load of the CI868 module in percentage updated every minute.

Sender Cycles per Second Number of times the sender task has traversed the send list containing the Data object, to be sent out on change.

MMS Values Received Number of MMS data values received from other IEDs.

MMS Commands Sent Number of MMS data values sent to other IEDs.

MMS Values Received Per Second

Number of MMS values received from other IEDs per second.

Report Control Blocks Received Per Second

Number of RCBs received per second.

Number of IEDs Configured for Reporting

Number of IEDs configured for MMS Reporting.

Number of IEDs Connected for Reporting

Number of IEDs connected for MMS Reporting.

Number of Buffered Report Control Blocks Configured

Number of Buffered RCBs configured.

Number of Buffered Report Control Blocks Enabled

Number of Buffered RCBs enabled.

Section 4 CI868 Engineering CI868 Performance Data

9ARD171385-600 A 105

CI868 Performance Data

Configuration and Performance parameters related to CI868 module for GOOSE, MMS Client, and GOOSE combined with MMS Client protocol usage is explained in System 800xA System Guide Technical Data and Configuration (3BSE041434*) Manual.

Number of Unbuffered Report Control Blocks Configured

Number of Unbuffered RCBs configured.

Number of Unbuffered Report Control Blocks Enabled

Number of Unbuffered RCBs enabled.

MMS Diag info

Number of Report Control Blocks Configured

Total number of RCBs configured.

Number of Report Control Blocks Enabled

Total number of RCBs enabled.

Table 32. LN0 and Diag Hardware editor diagnostics information

Diagnostics Information Description

CI868 Performance Data Section 4 CI868 Engineering

106 9ARD171385-600 A

9ARD171385-600 A 107

Appendix A MMS Logical Node Channels

This appendix provides the list of all Logical Node channels and also the supported CDC types for MMS receive on CI868 Module.

Table 33. Logical Node Channels based on IEC 61850 specification - Edition 1

SI No.Logical Node

NameControl I/O Channel

NumberControl I/O Channel

NameCDC Type

1 ATCC 1 Loc_stVal SPS2 OpCntRs_stVal INC3 TapChg_valWtr BSC4 TapPos_valWtr ISC5 ParOp_stVal DPC6 LTCBlk_stVal SPC7 LTCDragRs_stVal8 VRed1_stVal9 VRed2_stVal SPC10 CtlV_mag MV11 LodA_mag MV12 CircA_mag MV13 LoCtlV_mag MV14 HiDmdA_mag MV15 Auto_stVal SPS16 HiTapPos_stVal INS17 LoTapPos_stVal INS

2 CALH 1 GrAlm_stVal SPS2 GrWrn_stVal

3 AlmLstOv_stVal

3 CCGR 1 EEHealth_stVal INS2 OpTmh_stVal


108 9ARD171385-600 A

3 EnvTmp_mag MV

4 OilTmpIn_mag

5 OilTmpOut_mag

6 OilMotA_mag

7 FanFlw_mag

8 FanA_mag

9 CECtl_stVal SPC

10 PmpCtlGen_stVal INC

11 PmpCtl_stVal

12 FanCtlGen_stVal

13 FanCtl_stVal

14 Auto_stVal SPS

15 FanOvCur_stVal

16 PmpOvCur_stVal

17 PmpAlm_stVal

4 CILO 1 EnaOpn_stVal2 EnaCls_stVal

5 CSWI 1 Loc_stVal SPS2 OpCntRs_stVal INC3 Pos_stVal DPC4 Pos_stSeld5 PosA_stVal6 PosA_stSeld7 PosB_stVal8 PosB_stSeld9 PosC_stVal

10 PosC_stSeld

11 OpOpn_general ACT

12 OpCls_general

Table 33. Logical Node Channels based on IEC 61850 specification - Edition 1 (Continued)

SI No.Logical Node



NameCDC Type


9ARD171385-600 A 109

13 Pos_CTLCMD DPC

14 PosA_CTLCMD

15 PosB_CTLCMD

16 PosC_CTLCMD

6 GAPC 1 Loc_stVal SPS2 OpCntRs_stVal INC

3 SPCSO_stVal SPC

4 DPCSO_stVal DPC

5 ISCSO_stVal INC

6 Auto_stVal SPS

7 Str_general ACD

8 Str_dirGeneral

9 Op_general ACT

7 GGIO 1 EEHealth_stVal INS2 Loc_stVal SPS3 OpCntRs_stVal INC4 AnIn1_mag MV5 AnIn2_mag6 AnIn3_mag

7 AnIn4_mag

8 AnIn5_mag

9 SPCSO1_stVal SPC

10 SPCSO2_stVal

11 SPCSO3_stVal

12 SPCSO4_stVal

13 SPCSO5_stVal


SI No.Logical Node



NameCDC Type


110 9ARD171385-600 A

14 DPCSO1_stVal DPC

15 DPCSO2_stVal

16 DPCSO3_stVal

17 DPCSO4_stVal

18 DPCSO5_stVal

19 ISCSO1_stVal INC

20 ISCSO2_stVal

21 ISCSO3_stVal

22 ISCSO4_stVal

23 ISCSO5_stVal

24 IntIn_stVal INS

25 Alm_stVal SPS

26 Ind_stVal

8 GSAL 1 OpCntRs_stVal INC2 NumCntRs_stVal

9 MDIF 1 OpARem_phsA WYE2 OpARem_phsB

3 OpARem_phsC

4 OpARem_neut

5 OpARem_net

6 OpARem_res

7 Amp1_instMag SAV

8 Amp2_instMag

9 Amp3_instMag

10 MMXN 1 EEHealth_stVal INS


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 111

2 Amp_mag MV

3 Vol_mag

4 Watt_mag

5 VolAmpr_mag

6 VolAmp_mag

7 PwrFact_mag

8 Imp_cVal CMV

9 Hz_mag MV

11 MMXU 1 EEHealth_stVal INS2 TotW_mag MV

3 TotVAr_mag

4 TotVA_mag

5 TotPF_mag

6 Hz_mag

7 PPV_phsAB DEL

8 PPV_phsBC

9 PPV_phsCA


SI No.Logical Node



NameCDC Type


112 9ARD171385-600 A

10 PhV_phsA WYE11 PhV_phsB

12 PhV_phsC

13 PhV_neut

14 PhV_net

15 PhV_res

16 A_phsA

17 A_phsB

18 A_phsC

19 A_neut

20 A_net

21 A_res


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 113

22 W_phsA WYE23 W_phsB

24 W_phsC

25 W_neut

26 W_net

27 W_res

28 VAr_phsA

29 VAr_phsB

30 VAr_phsC

31 VAr_neut

32 VAr_net

33 VAr_res

34 VA_phsA

35 VA_phsB

36 VA_phsC

37 VA_neut

38 VA_net

39 VA_res

40 PF_phsA

41 PF_phsB


SI No.Logical Node



NameCDC Type


114 9ARD171385-600 A

42 PF_phsC WYE43 PF_neut

44 PF_net

45 PF_res

46 Z_phsA

47 Z_phsB

48 Z_phsC

49 Z_neut

50 Z_net

51 Z_res

12 MSQI 1 EEHealth_stVal INS2 SeqA_c1 SEQ

3 SeqA_c2

4 SeqA_c3

5 SeqA_seqT

6 SeqV_c1

7 SeqV_c2

8 SeqV_c3

9 SeqV_seqT

10 DQ0Seq_c1

11 DQ0Seq_c2 SEQ

12 DQ0Seq_c3

13 DQ0Seq_seqT


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 115

14 ImbA_phsA WYE15 ImbA_phsB

16 ImbA_phsC

17 ImbA_neut

18 ImbA_net

19 ImbA_res

20 ImbNgA_mag MV

21 ImbNgV_mag

22 ImbPPV_phsAB DEL

23 ImbPPV_phsBC

24 ImbPPV_phsCA

25 ImbV_phsA WYE

26 ImbV_phsB

27 ImbV_phsC

28 ImbV_neut

29 ImbV_net

30 ImbV_res

31 ImbZroA_mag MV

32 ImbZroV_mag

33 MaxImbA_mag

34 MaxImbPPV_mag

35 MaxImbV_mag

13 MSTA 1 EEHealth_stVal INS


SI No.Logical Node



NameCDC Type


116 9ARD171385-600 A

2 AvAmps_mag MV

3 MaxAmps_mag

4 MinAmps_mag

5 AvVolts_mag

6 MaxVolts_mag

7 MinVolts_mag

8 AvVA_mag

9 MaxVA_mag

10 MinVA_mag

11 AvW_mag

12 MaxW_mag

13 MinW_mag

14 AvVAr_mag

15 MaxVAr_mag

16 MinVAr_mag

17 EvStr_stVal SPC

14 PDIF 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 117

5 DifAClc_phsA WYE

6 DifAClc_phsB

7 DifAClc_phsC

8 DifAClc_neut

9 DifAClc_net

10 DifAClc_res

11 RstA_phsA

12 RstA_phsB

13 RstA_phsC

14 RstA_neut

15 RstA_net

16 RstA_res

15 PDIR 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

16 PDIS 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

17 PDOP 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

18 PDUP 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT


SI No.Logical Node



NameCDC Type


118 9ARD171385-600 A

19 PFRC 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

5 BlkV_stVal SPS

20 PHAR 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

21 PHIZ 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

22 PIOC 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

23 PMRI 1 OpCntRs_stVal INC2 Op_general ACT

3 StrInh_stVal SPS

4 StrInhTmm_stVal INS

24 PMSS 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

25 PPAM 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

26 PSCH 1 OpCntRs_stVal INC


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 119

2 ProTx_stVal SPS

3 ProRx_stVal

4 Str_general ACD

5 Str_dirGeneral

6 Op_general ACT

7 CarRx_general

8 LosOfGrd_stVal SPS

9 Echo_general ACT

10 WeiOp_general

11 RvABlk_general

12 GrdRx_stVal SPS

27 PSDE 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

28 PTEF 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

29 PTOC 1 OpCntRs_stVal INC2 Str_general ACD3 Str_dirGeneral4 Op_general ACT

30 PTOF 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

5 BlkV_stVal SPS

31 PTOV 1 OpCntRs_stVal INC


SI No.Logical Node



NameCDC Type


120 9ARD171385-600 A

2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

32 PTRC 1 OpCntRs_stVal INC2 Tr1_general ACT

3 Tr2_general

4 Tr3_general

5 Tr4_general

6 Tr5_general

7 Tr6_general

8 Tr7_general

9 Tr8_general

10 Tr9_general

11 Tr10_general

12 Op_general

13 Str_general ACD

14 Str_dirGeneral

33 PTTR 1 OpCntRs_stVal INC2 Amp_mag MV3 Tmp_mag4 TmpRl_mag5 LodRsvAlm_mag6 LodRsvTr_mag7 AgeRat_mag8 Str_general ACD9 Str_dirGeneral10 Op_general ACT11 AlmThm_general

34 PTUC 1 OpCntRs_stVal INC


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 121

2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

35 PTUF 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

5 BlkV_stVal SPS

36 PTUV 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

37 PUPF 1 OpCntRs_stVal INC2 Str_general ACD3 Str_dirGeneral4 Op_general ACT5 BlkA_stVal SPS6 BlkV_stVal

38 PVOC 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 Op_general ACT

39 PVPH 1 OpCntRs_stVal INC2 Str_general ACD3 Str_dirGeneral4 Op_general ACT

40 RADR 1 OpCntRs_stVal ?2 ChTrg_stVal ?

41 RBDR 1 OpCntRs_stVal ?


SI No.Logical Node



NameCDC Type


122 9ARD171385-600 A

2 ChTrg_stVal ?

42 RBRF 1 OpCntRs_stVal INC2 Str_general ACD

3 Str_dirGeneral

4 OpEx_general ACT

5 OpIn_general

43 RDIR 1 Dir_general ACD2 Dir_dirGeneral

44 RDRE 1 OpCntRs_stVal INC2 RcdTrg_stVal SPC3 MemRs_stVal4 MemClr_stVal5 RcdMade_stVal SPS6 FltNum_stVal INS7 GriFltNum_stVal8 RcdStr_stVal SPS9 MemUsed_stVal INS

45 RFLO 1 OpCntRs_stVal INC2 FltZ_cVal CMV

3 FltDiskm_mag MV

4 FltLoop_stVal INS

46 RPSB 1 OpCntRs_stVal INC2 Str_general ACD3 Str_dirGeneral4 Op_general ACT5 BlkZn_stVal SPS

47 RREC 1 OpCntRs_stVal INC2 BlkRec_stVal SPC

3 ChkRec_stVal

4 Auto_stVal SPS


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 123

5 Op_general ACT

6 AutoRecSt_stVal INS

48 RSYN 1 RHz_stVal SPC2 LHz_stVal3 RV_stVal4 LV_stVal5 Rel_stVal SPS6 VInd_stVal7 AngInd_stVal8 HzInd_stVal9 SynPrg_stVal10 DifVClc_mag MV11 DifHzClc_mag12 DifAngClc_mag

49 SARC 1 EEHealth_stVal INS2 OpCntRs_stVal INC

3 FACntRs_stVal

4 FADet_stVal SPS

5 ArcCntRs_stVal INC

6 SwArcDet_stVal SPS

50 SIMG 1 EEHealth_stVal INS2 Pres_mag MV3 Den_mag4 Tmp_mag


SI No.Logical Node



NameCDC Type


124 9ARD171385-600 A

5 InsAlm_stVal SPS

6 InsBlk_stVal

7 InsTr_stVal

8 PresAlm_stVal

9 DenAlm_stVal

10 TmpAlm_stVal

11 InsLevMax_stVal

12 InsLevMin_stVal

51 SIML 1 EEHealth_stVal INS2 Tmp_mag MV3 Lev_mag4 Pres_mag5 H2O_mag6 H2OTmp_mag7 H2_mag8 InsAlm_stVal SPS9 InsBlk_stVal10 InsTr_stVal11 TmpAlm_stVal12 PresTr_stVal13 PresAlm_stVal14 GasInsAlm_stVal15 GasInsTr_stVal16 GasFlwTr_stVal17 InsLevMax_stVal18 InsLevMin_stVal19 H2Alm_stVal20 MstAlm_stVal

52 TCTR 1 EEHealth_stVal INS2 OpTmh_stVal


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 125

3 Amp_instMag SAV

53 TVTR 1 EEHealth_stVal INS2 OpTmh_stVal3 Vol_instMag SAV4 FuFail_stVal SPS

54 XCBR 1 Loc_stVal2 EEHealth_stVal INS3 OpCnt_stVal4 Pos_stVal DPC5 Pos_stSeld6 BlkOpn_stVal SPC7 BlkCls_stVal8 ChaMotEna_stVal9 CBOpCap_stVal INS10 POWCap_stVal11 MaxOpCap_stVal12 Pos_CTLCMD DPC

55 XSWI 1 Loc_stVal SPS2 EEHealth_stVal INS3 OpCnt_stVal4 Pos_stVal DPC5 BlkOpn_stVal SPC6 BlkCls_stVal7 ChaMotEna_stVal8 SwTyp_stVal INS9 SwOpCap_stVal10 MaxOpCap_stVal6 ColPos_setMag APC

56 YLTC 1 EEHealth_stVal INS2 OpCnt_stVal


SI No.Logical Node



NameCDC Type


126 9ARD171385-600 A

3 Torq_mag MV4 MotDrvA_mag5 TapPos_valWtr ISC6 TapChg_valWtr BSC7 EndPosR_stVal SPS8 EndPosL_stVal9 OilFil_stVal5 HPTmpTr_stVal

6 OANL_stVal

7 OpOvA_stVal

8 OpOvV_stVal

9 OpUnV_stVal

10 CGAlm_stVal

57 ZAXN 1 EEHealth_stVal INS2 OpTmh_stVal

3 Vol_mag MV

4 Amp_mag

58 ZBAT 1 EEHealth_stVal INS2 OpTmh_stVal

3 Vol_mag MV

4 VolChgRte_mag

5 Amp_mag

6 BatTest_stVal SPC

7 TestRsl_stVal SPS

8 BatHi_stVal

9 BatLo_stVal


SI No.Logical Node



NameCDC Type


9ARD171385-600 A 127

Table 34 Lists MMS Receive CDC types mapped into IEC 61131-3 variable.

Table 34. Data-type Mapping for MMS LN Representations in Control Builder


Mandatory Control,Status and Measured DAs


SPS stVal BoolIO

q

t

DPS stVal DintIO

q

t

INS stVal DintIO

q

t

ACT general BoolIO

q

t

ACD.general(1) general BoolIO

q

t

ACD.dirGeneral(1) (q and t of base DA is used)

dirGeneral DintIO

MV mag.f RealIO

q

t


128 9ARD171385-600 A

CMV cVal.mag.f RealIO

q

t

SAV instMag.f RealIO

q

WYE.phsA(1) cVal.mag.f RealIO

q

t

WYE.phsB(1) cVal.mag.f RealIO

q

t

WYE.phsC(1) cVal.mag.f RealIO

q

t

WYE.neut(1) cVal.mag.f RealIO

q

t

WYE.net(1) cVal.mag.f RealIO

q

t






9ARD171385-600 A 129

WYE.res(1) cVal.mag.f RealIO

q

t

DEL.phsAB(1) cVal.mag.f RealIO

q

t

DEL.phsBC(1) cVal.mag.f RealIO

q

t

DEL.phsCA(1) cVal.mag.f RealIO

q

t

SEQ.c1(1) cVal.mag.f RealIO

q

t


q

t


q

t

SEQ.seqT(1) seqT DintIO






130 9ARD171385-600 A

SPC stVal BoolIO

q

t

DPC stVal DintIO

q

t

INC stVal DintIO

q

t

BSC valWtr DintIO

q

t

ISC valWtr DintIO

q

t

APC setMag.f DintIO

q

t

(1) This CDC type is split into multiple channels to fit into IEC 61131-3 variable type.





9ARD171385-600 A 131

Appendix B CI868 Control Builder Coexistence Compatibility

CI868 Control Builder Coexistence Compatibility is applicable only while upgrading from System Version 5.0 or 5.1 to System Version 6.0.

AC 800M Controllers with different firmware versions can co-exist in the same network, and newer versions of Control Builder can connect to controllers of older versions (not older than Version 5.0).

CI868 Hardware LibrariesCI868 hardware library 1.x version supports IEC 61850 GOOSE communication. If CI868 hardware library 1.x version is needed, then the correct coexistence system extension must be loaded into the system.

CI868 hardware library 2.x version supports IEC 61850 GOOSE communication and is installed by default in System Version 6.0.

The CI868 hardware library 3.x version supports IEC 61850 GOOSE and MMS Client Communication and is installed by default in System Version 6.0.

CI868 and AC 800M Controller Compatibility:

The CI868 Hardware Library under the Connected Libraries in Control Builder project must be selected as per the following criteria.

• CI868 Hardware Library 1.x version is compatible with AC 800M Controller running SV5.0 SP2 firmware.

• CI868 Hardware Library 2.x and 3.x version available in System Version 6.0 are compatible with AC 800M Controller running SV5.0 SP2 / SV5.1 / RU1 / RU2 / RU3 / FP4 and SV6.0 firmware.

CI868 Hardware Libraries Appendix B CI868 Control Builder Coexistence Compatibility

132 9ARD171385-600 A

CI868 Firmware Upgrade to Hardware Library 3.x Version:

CI868 configuration file in existing projects generated using CI868 Hardware Library 1.x or 2.x version is Not compatible with CI868 Hardware Library 3.x version.

Thereby after upgrading CI868 Firmware in the module from Hardware library 1.x or 2.x to Hardware library 3.x version, it is Mandatory to re-import the valid SCD file and download the project to Controller in order to generate new CI868 configuration data compatible with new CI868 firmware.

Table 35 describes CI868 Firmware Upgrade scenarios applicable during Control Builder project migration from earlier versions to System Version 6.0.

Table 35. CI868 Firmware Upgrade Scenarios

ScenarioControl Builder

Hardware Library Upgrade

ConnectedCI868

Hardware Library in Control Builder

CI868 Hardware Library in Running

CI868 Module

SCD Import

Control Builder Online before

Downloading Project

Control Builder

Download Project & Go Online

Remarks

Control Builder project Upgrade from SV5.0 SP2 / SV5.1 / RU1 / RU2 / RU3 to SV6.0:

Unchanged SCD file with GOOSE signals.

1A No 1.x / 2.x 1.x / 2.x No Allowed Allowed -

1B Yes.

Online / Manual Firmware upgrade with CI868

3.x 3.x Yes.

Mandatory

Not Allowed Allowed Re-import of SCD file is required.

1C Yes.

Manual Firmware upgrade without CI868.

For Online Firmware upgrade in SV6.0, CI868 firmware option is selected and greyed out.

3.x 1.x / 2.x No Not allowed for Manual Firmware upgrade, as Controller application must be downloaded.

Allowed Importing of SCD file is not recommended.

Appendix B CI868 Control Builder Coexistence Compatibility CI868 Hardware Libraries

9ARD171385-600 A 133

Control Builder Project Upgrade from SV5.0 SP2 / SV5.1 / RU1 / RU2 / RU3 to SV6.0:

Updated SCD file with GOOSE signals on Existing / New CI868.

2ANo 1.x / 2.x 1.x / 2.x Yes Not Allowed Allowed Re-importing of

SCD file is required for signal changes.

2B Yes.


3.x 3.x Yes. Not Allowed Allowed Re-importing of SCD file is required for signal changes.

2C Yes.



3.x 1.x / 2.x No. Not Allowed Not Allowed

Importing of SCD file is not recommended. Instead perform scenario 2B.




ConnectedCI868



CI868 Module

SCD Import


Downloading Project

Control Builder


Remarks


134 9ARD171385-600 A

Control Builder Project Upgrade from SV5.0 SP2 / SV5.1 / RU1 / RU2 / RU3 to SV6.0:

Updated SCD file with GOOSE / MMS signals on Existing / New CI868.

3A

No 1.x / 2.x 1.x / 2.x Not Allowed

Not Applicable

Not Applicable.

Importing of SCD file with MMS signal is not allowed with CI868 hardware library 1.x / 2.x version present as connected CI868 hardware library.

3B Yes.


3.x 3.x Yes. Not Allowed Allowed Re-importing of SCD file is required for signal changes.

3C Yes.



3.x 1.x / 2.x No. Not Allowed Not Allowed

Importing SCD file with MMS signal is not allowed with CI868 hardware library 1.x / 2.x version present as connected CI868 hardware library and in running CI868 module.

Instead perform scenario 3B.




ConnectedCI868



CI868 Module

SCD Import


Downloading Project

Control Builder


Remarks

Appendix B CI868 Control Builder Coexistence Compatibility CI868 Hardware Libraries

9ARD171385-600 A 135

Control Builder project Upgrade from SV5.1 FP4 to SV6.0:

Unchanged SCD file with GOOSE / MMS signals

4A No 3.10-x 3.0-x No Allowed. Allowed -

4B Yes.


3.10-x 3.10-x No Allowed for Online Firmware upgrade.

Not allowed for Manual Firmware upgrade, as Controller application must be downloaded.

Allowed -

4C Yes.



3.10-x 3.0-x No Not allowed for Manual Firmware upgrade, as Controller application must be downloaded.

Allowed -




ConnectedCI868



CI868 Module

SCD Import


Downloading Project

Control Builder


Remarks


136 9ARD171385-600 A

Control Builder Project Upgrade from SV5.1 FP4 to SV6.0:

Updated SCD file with GOOSE / MMS signals on Existing / New CI868.

5A No 3.10-x 3.0-x Yes Not Allowed Allowed Re-importing of SCD file is required for signal changes.

5B Yes.

Online / Manual Firmware upgrade with CI868.

3.10-x 3.10-x Yes Not Allowed Allowed Re-importing of SCD file is required for signal changes.

5C Yes.



3.10-x 3.0-x Yes Not Allowed Allowed Re-importing of SCD file is required for signal changes.

The version of CI868 Hardware Library connected in Control Builder project must always be higher or equal to CI868 Hardware Library version running in the CI868 Module.

It is mandatory to have only one CI868 Hardware Library under Control Builder Project Connected Libraries. That is, either CI868 hardware library 1.x or 2.x or 3.x version must be connected.

During CI868 Firmware Upgrade, IEC 61850 Communication is interrupted, Control Builder Project is downloaded to the Controller, and CI868 module is up and running.




ConnectedCI868



CI868 Module

SCD Import


Downloading Project

Control Builder


Remarks

9ARD171385-600 A 137

Appendix C CI868 Hardware Object Name Information

This section explains the location of the CI868 Hardware object when System Alarms displays an error at CI868 Hardware object level.

When an error is detected in the CI868 Hardware Object, the name of the object is displayed in the ObjectName column, However, in case of CI868 MMS LN objects only the prefix is shown in the Alarm Event ObjectName column, as there is a space between the LN prefix and LN type (see Figure 43). The complete location of the object is displayed in the SourceName column that specifies the address in the ControllerIP-HardwareObjectAddress format (see Figure 44).

For errors that are detected at IED level, the prefix name of the IED is displayed in ObjectName column.


138 9ARD171385-600 A

Figure 43. Control Builder Hardware Tree


9ARD171385-600 A 139

Figure 44. System Alarm list - Object Name


140 9ARD171385-600 A

9ARD171385-600 A 141

Revision History

This section provides information on the revision history of this User Manual.

The following table lists the revision history of this User Manual.

Updates in Revision Index AThe following table shows the updates made in this User Manual for 800xA 6.0.2.

Revision Index

Description Date

- Published for System 800xA 6.0 August 2014

A Published for System 800xA 6.0.2 April 2016

Updated Section/Sub-section Description of Update

All sections Content and Topic across the document has been restructured.

Updates in Revision Index A

142 9ARD171385-600 A

9ARD171385-600 A 143

AAbout 7About This Book 7Application Redundancy 102

BBus Bar Change 96Bus Bar Voltage Control 99

CCCT600 17CI868 23CI868 IED Diagnostic Information 102CI868 MMS Control Function Block with IEC

61131-3 45CI868 module 72CI868 Performance Data 105CI868 position 28CI868 Support of Sequence of Event (SOE 55CI868 via ITCI 73CID File Generation 28Configuration for Generating Alarm and Events 57configured default Data Sets 28Consistency check 18Control Builder 16

DData Attribute, Quality and Time Stamp for Send

and Receive Data Objects 90Data Object names 19Data Quality for Received Data 91Data received via MMS 73Data Send via MMS 74

Data Sets and GSE Control block 28Diag 24diagnostics 102Direct mode 48DPC CDC type Control Commands 89

GGenerator Reactive Power Control 98Generator Real Power Control 95Generic Logical Nodes 101Get SCD 30GOOSE Control Block 28GOOSE Send and Receive LN CDC types 85GOOSE Send Protocol information 83

HHandling SCD Reconfiguration and Control

Builder Tree Variation 33

IICD File Generation 27IEC 61131 -3 Application for using External

Events 58IEC 61850 ImportWizard.log 27IEC 61850 Wizard 17IED 23Importing SCD File on CI868 IED Node 29Introduction 15

LLD 23LN 24LN0 28

Index

Index

144 9ARD171385-600 A

Index

144 9ARD171385-600 A

Load Shedding Applications 94Logical Device name configuration 28logical nodes priority 27

MMMS Control Commands 17, 74MMS Diagnostic data 17MMS diagnostics information 104MMS Diagnostics Object 24MMS Reporting 73MMS Reporting Data 73multiple CI868 IEDs 31MyIED 23

Ooptional Data Attributes 19

PProcessObjBasicLib application library 17Protocol Info 80Protocol Information 80

SSBO Control Mode 48SCL libraries 19Select Before Operate (SBO) command 52Supported Logical Nodes 93

TTerminology 9Transformer Tap Control 97

Vversion and revision file 27View Log 27

Index

9ARD171385-600 A 145

Index

146 9ARD171385-600 A

Index

146 9ARD171385-600 A

AC 800M IEC 61850 Engineering & Configuration · AC 800M IEC 61850 Configuration for CI868 System...

Documents

Transcript of AC 800M IEC 61850 Engineering & Configuration · AC 800M IEC 61850 Configuration for CI868 System...