AC 800M IEC Configuration for CI868

Transcription

1 AC 800M IEC Configuration for CI868 System Version 6.0 Power and productivity for a better world

2

3 AC 800M IEC Configuration for CI868 System Version 6.0

4 NOTICE This 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 referenced 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. TRADEMARKS 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. 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 consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC. All rights to copyrights, registered trademarks, and trademarks reside with their respective owners. Copyright by ABB. All rights reserved. Release: August 2014 Document number: 9ARD

5 Table of Contents About This User Manual User Manual Conventions...10 Feature Pack...10 Warning, Caution, Information, and Tip Icons...10 Terminology...11 Released User Manuals and Release Notes...14 Section 1 - Introduction Section 2 - CI868 Communication Interface Configuration IEC Hardware Objects...24 Generating CID / ICD file for CI868 IED...28 IEC Wizard...29 CID / ICD File Export Errors in IEC Wizard...31 Importing SCD File on CI868 IED Node...35 Handling SCD Reconfiguration and Control Builder Tree Variation...36 Features of TreeView Comparator...37 Import Rules based on CI868 Access Point Criteria...42 SCD File Import Errors in IEC Wizard...43 CCF View...46 CI868 IED as IEC MMS Client...48 CI868 Data Receive through MMS...49 CI868 Control Commands through MMS...50 IEC Protocol Information in I/O channel...56 Supported AC 800M Data Types...62 GOOSE Send and Receive...62 CI868 MMS Receive LN Representations ARD

6 Table of Contents CI868 MMS Control Commands...65 Representing CI868 Operating Status as an IED: LN0, LPHD...66 Cross Referencing IEC Data with IEC Variables...69 For Data Subscribed by CI868 (Signal in an IED to IEC )...69 For Data Published by CI868 (IEC Signal to IED)...72 Configuration...76 Data Attribute, Quality and Time Stamp for Send and Receive Data Objects...76 Data Quality for Received Data...77 Supported Logical Nodes...79 Load Shedding Applications...79 Generator Real Power Control...80 Bus Bar Change...81 Transformer Tap Control...82 Generator Reactive Power Control...83 Bus Bar Voltage Control...85 Generic Logical Nodes...86 Configuration Parameters...88 Application Redundancy...89 CI868 MMS Control Function Block with IEC IED Command Send...91 IED Status Receive...96 CI868 Support of Sequence of Event (SOE) Configuration for Generating Alarm and Events IEC Application for using External Events CI868 IED Diagnostic Information CI868 Performance Data Appendix A - MMS Logical Node Channels Appendix B - CI868 Control Builder Coexistence Compatibility CI868 Hardware Libraries Appendix C - CI868 Hardware Object Name Information Index 6 9ARD

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, IEC Wizard tool and other third party tool. The application engineers or the engineers who plan the design or implementation of IEC 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 Wizard. Section 2, CI868 Communication Interface Configuration, describes how to configure AC 800M / CI868 IED for use with IEC Appendix A, MMS Logical Node Channels, details the list of logical nodes used with IEC for MMS Client communication. Appendix B, CI868 Control Builder Coexistence Compatibility, describes the Control Builder version compatibility. 9ARD

8 User Manual Conventions About This User Manual 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 Conventions Microsoft 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. 8 9ARD

9 About This User Manual Terminology 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. Terminology Tip icon indicates advice on, for example, how to design your project or how to use a certain function. 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. A complete and comprehensive list of Terms is included in the System 800xA, Engineering Concepts instruction (3BDS100972*). 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. Term/Acronym 800xA AC 800M AC 800M Controller Description ABB automation system (extended Automation). ABB Controller 800M series, general purpose process controller series by ABB. Any controller constructed from the units and units connected to the AC 800M hardware platform. 9ARD

10 Terminology About This User Manual Term/Acronym AE CCT CDC CDC Block CI868 Module CID Control Builder DA DPC FBD GCB GOOSE HW Unit I/O ICD Alarm and Event. ABB Communication Configuration Tool for configuring signals and generating SCD files. Common Data Class as specified by IEC61850-Ed1 (Edition1) specification. CDC representation in Control Builder Project Explorer. Communication Interface Module for AC 800M controller. These modules are connected over the CEX bus and contain implementation of a specific communication protocol. Configured IED Description file, a type of SCL file as specified in IEC Edition 1 specification. Controller Builder M (Control Builder Professional or Compact Control Builder). Data Access. Double Point Controllable. CDC type, specified in IEC Edition 1 specification. Feeder Block Diagram. GOOSE Control Block. 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 compliant IEDs, also termed as Horizontal Communication. Hardware unit defined in the tree of Control Builder Project. Input and Output. Description IED Capability Description, type of SCL file as specified in IEC Edition 1 specification. 10 9ARD

11 About This User Manual Terminology Term/Acronym Description IEC IEC Ed1 IED IET LD LN MMS Node OPC International Electrotechnical Commission. IEC Ed1 (Edition1) specification. Intelligent Electronic Device. ABB Integrated Engineering Tool for generating SCD file. 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. Logical Node. 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. 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. OLE for Process Control. A set of standard interfaces based on COM technology. 9ARD

12 Released User Manuals and Release Notes About This User Manual Term/Acronym PA PGS PM PMS RCB SA SBO SCADA SCD SCL SLD XML Process Automation. Power Generation Solutions. Processor Module of AC 800M controller. Power Management Solutions. Report Control Block. Substation Automation. Select Before Operate Command. Supervisory Control And Data Acquisition. Substation Configuration Description, type of SCL file defined by IEC Ed1 specification. Substation Configuration Language defined in IEC Ed1 specification. Single Line Diagram. Description extensible Markup Language. Released User Manuals and Release Notes A complete list of all User Manuals and Release Notes applicable to System 800xA is provided in System 800xA Released User Manuals (3BUA000263*). System 800xA Released User Manuals (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. 12 9ARD

13 About This User Manual Released User Manuals and Release Notes 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 Manuals (3BUA000263*) is updated and published to ABB SolutionsBank. 9ARD

14 Released User Manuals and Release Notes About This User Manual 14 9ARD

15 Section 1 Introduction This section gives an overview of the complete engineering workflow of IEC integrated with 800xA system. Figure 1 and Figure 2shows the simplified IEC engineering workflow integrated with 800xA system. ICD File for IHMI IEC OPC Server C:\ProgramFiles(x86)\ABB\61850 OPCServer OPC Server with 1 sub network.icd OPC Server with 16 sub network.icd Substation Automation Engineering CI868 IED Engineering Control Builder Export CID/ICD Fi l e Configure CI868 IED Template IED Application Engineering PCM 600 Export IED Configuration + Import CID File Substation Configuration Substation Structure Single Line diagram Station Configuration Diagram Feeder Block Diagram Communication Configuration Import CID File Data Set Configuration Assign LN to Conductive Equipment RCB Configuration GCB Configuration Export SCD File Third Party CID File, specified by vendors. Figure xA IEC Substation Engineering Workflow 1 & 2 9ARD

16 Section 1 Introduction Plant Explorer Upload SCD File for IEC Connect Control & Functional Structure Creation CET for IEC OPC Server Import SCD File + Import SCD File Configuration IEC OPC Server IEC Alarms & Events Control Builder for CI 868 IED Import SCD File Download CI868 Configuration into AC 800M Controller PCM600 for ABB IEDs Download Configuration to IED Figure xA IEC Substation Engineering Workflow 3 The engineering workflow for IEC configuration in 800xA systems comprise of the following application tools/components: IEC Substation Engineering with Communication Configuration with ABB IET600 or CCT600 or 3rd party IEC engineering tools Control Builder with IEC Wizard Control Builder Control Builder with IEC Wizard is used to configure CI868 as an IED and download the configuration to the CI868 module. It is also used to connect IEC variables to the IEC data. 16 9ARD

17 Section 1 Introduction Use IEC Wizard tool available in Control Builder 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 engineering tool Generate configuration files for each CI868 access point Create Hardware Tree structure in Control Builder representing CI868 as an IED in the IEC61850 network. IET600 / CCT600 IET600 / CCT600 is an IEC engineering tool to perform IEC 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 Engineering Workflow (9ARD171384*) Manual. 9ARD

18 Section 1 Introduction 18 9ARD

19 Section 2 CI868 Communication Interface Configuration Section 2 CI868 Communication Interface Configuration The IEC for Substation Automation System (SAS) defines communication between Intelligent Electronic Devices (IED) in the substation and other related equipment. The CI868 Module is designed as IED and supports GOOSE and MMS Client communication on IEC network and works as an interface between IEC network and process controller running IEC applications. IEC MMS Client constitutes the following: Support of CSWI and XCBR LNs for sending MMS Control Commands to other IEDs. Support for receiving MMS Signals using RCB data from other IEDs. MMS Diagnostic data can be viewed in Control Builder. User can now view the diagnostic information of a MMS hardware object in the editor window. Support of 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 programing. Support of incoming Add Cause Negative responses that are available from IEC61850 Stack for MMS signals. Support of printing errors and warnings into the CI log that are generated from the IEC61850 stack log. CI868 Logical Node LN0 displays Mod channel in the hardware editor and also generate Protocol info for Mod channel of LN0 object. Supports flexible RCB dataset engineering that contains Data objects from LN0 and LPHD logical nodes assigned to CI868. 9ARD

20 Section 2 CI868 Communication Interface Configuration 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 Engineering Workflow for substation automation: Support of 12 CI868 modules per AC 800M controller. Engineering with Control Builder and CCT 600only, thereby minimal usage of external third party tools. Compatible with PCM Tool. Compatible with IET Tool. Defining CI868 as an IED instead of AC 800M in Control Builder. Editable hardware tree under CI868 level to define CI868 as IED in Control Builder 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 hardware tree with SCD file before downloading the SCD file. IEC61850 Wizard tool improvements: 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 project name and the substation name in the SCD file during import. Storage and retrieval of SCD file from Control Builder 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. 20 9ARD

21 Section 2 CI868 Communication Interface Configuration 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. 9ARD

22 IEC Hardware Objects Section 2 CI868 Communication Interface Configuration IEC Hardware Objects Each CI868 is represented as IED with one access point. The access point is the position of CI868 in the Control Builder tree structure and is represented in the hardware object MyIED as shown in Figure ARD

23 Section 2 CI868 Communication Interface Configuration IEC Hardware Objects Figure 3. Communication Interface CI868 IED Tree view 9ARD

24 IEC Hardware Objects Section 2 CI868 Communication Interface Configuration CI868 IED and all the IEC related elements are designed as hardware objects in a hardware library to be configured under Control Builder. Table 1 details the hardware object in Control Builder. Figure 3 represents Control Builder hardware tree view under CI868. Control Builder supports maximum of 5000 Hardware objects in a Controller. It is recommended to configure the hardware objects within the limit to avoid problem during downloading project to the controller. Table 1. Control Builder Hardware Object Hardware Object CI868 MyIED IED LD Description 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 network. MyIED object is the representation of CI868 in IEC 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 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. The logical device contains the list of supported configured logical nodes that are configured in the respective IEDs. 24 9ARD

25 Section 2 CI868 Communication Interface Configuration IEC Hardware Objects Table 1. Control Builder Hardware Object Hardware Object LN Diag Description 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. MMS Diagnostics Object: MMS Diagnostic hardware object that displays IED level MMS diagnostic information. 9ARD

26 Generating CID / ICD file for CI868 IED Section 2 CI868 Communication Interface Configuration Generating CID / ICD file for CI868 IED CI868 IED hardware objects are configured in Control Builder 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 IED in Control Builder with all supported LNs 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. 26 9ARD

27 Section 2 CI868 Communication Interface Configuration IEC Wizard IEC Wizard The IEC 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 and also used for generating the CI868 Configuration data. IEC Wizard is used for, Exporting ICD / CID file for CI868 IED, refer to Generating CID / ICD file for CI868 IED on page 26. Importing SCD file generated from CCT or any other IEC61850 engineering tool, refer to Importing SCD File on CI868 IED Node on page 33. Creating IEC Hardware Objects Tree structure in Control Builder representing CI868 as an IED in the IEC network, refer to IEC Hardware Objects on page 22. IEC Wizard is available from the context menu of CI868 module object as shown in Figure 5. 9ARD

28 IEC Wizard Section 2 CI868 Communication Interface Configuration Figure 5. CI868 Module - IEC61850 Wizard 28 9ARD

29 Section 2 CI868 Communication Interface Configuration CID / ICD File Export Errors in IEC 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 Wizard can be viewed by rightclicking and choosing View Log option in IEC Wizard window or by opening the IEC ImportWizard.log file located in the following folder. For Compact Control Builder: C:\ABB Industrial IT Data\Engineer IT Data\Compact Control Builder AC 800M\LogFiles\Importwizard.log For Control Builder Professional: C:\ABB Industrial IT Data\Engineer IT Data\ Control Builder M Professional\LogFiles\Importwizard.log CID / ICD File Export Errors in IEC Wizard IEC Wizard tool displays error messages while exporting CID / ICD file. These errors occur when the CI868 communication parameters are not configured in Control Builder before export. Table 2 lists the possible IEC Wizard error messages during export operation. 9ARD

30 CID / ICD File Export Errors in IEC Wizard Section 2 CI868 Communication Interface Table 2. IEC Wizard Error Messages - CID / ICD Export CI868 Configuration Error Scenario CI868 configured without MyIED object. CI868 configured with empty MyIED field in MyIED object. CI868 configured with MyIED field containing space character. CI868 configured without any Logical Devices (LDs). CI868 configured with Logical Devices (LDs) name is blank or has a space. Error message displayed during ICD / CID Export Configuration Incomplete. Mandatory node (MyIED) not configured. Export will abort Invalid name for MyIED - Empty field not allowed Export will abort Invalid name for MyIED - Space characters not allowed Export will abort Configuration Incomplete. Mandatory node (LD) not configured. Export will abort 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 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 30 9ARD

31 Section 2 CI868 Communication Interface Configuration CID / ICD File Export Errors in IEC Table 2. IEC Wizard Error Messages - CID / ICD Export CI868 Configuration Error Scenario CI868 configured without mandatory LPHD under LD. CI868 configured without Mandatory LNs (LN0, LPHD). CI868 configured with Logical Node (LNs) and Logical Device (LD) having; Invalid Name, Duplicate name, Space Character, or Special Symbols. Error message displayed during ICD / CID Export LPHD node not configured under <LD name> Make sure that LN0 and LPHD LNs are configured under each LD Export will abort Configuration Incomplete: Mandatory logical nodes (LN0, LPHD) missing under <LD name> Make sure that LN0 and LPHD LNs are configured under each LD Export will abort 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 IEC 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. 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. During export of ICD file, the IEC wizard prioritizes the logical nodes if configured in the following order to create default dataset. GF GGIO = 1 LS PTRC = 2 BB GAPC = 3 LS GAPC = 4 PC GAPC = 5 TC1 ATCC = 6 9ARD

32 CID / ICD File Export Errors in IEC Wizard Section 2 CI868 Communication Interface 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 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 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 is same as the Access Point name under CI868 or AC 800M IED. Checks if Logical Device name configuration in Control Builder 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 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 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. If CI868 position, MyIED, and LD name is modified, the exported CID file contains the default Dataset and GSEControl blocks. 32 9ARD

33 Section 2 CI868 Communication Interface Configuration Importing SCD File on CI868 IED Node The generated individual configured ICD / CID file is further used for creating SCD file with IEC communication engineering tools such as CCT600. When exporting CI868 configuration into existing CCT600 project already 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. Importing SCD File on CI868 IED Node IEC61850 Wizard Tool imports the configured SCD file into Control Builder 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. Figure 7 represents the SCD Import tab in IEC61850 Wizard Tool. Figure 7. IEC Wizard - SCD Import 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 9ARD

34 Handling SCD Reconfiguration and Control Builder Tree Variation Section 2 CI868 Communication selected access point of the.scd file during verification, they are logged in the IEC61850.log file. A generic message is displayed to refer the IEC61850 Import Wizard log file. 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, q SCD 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 After successful import, the SCD file is stored in Control Builder 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 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. Handling SCD Reconfiguration and Control Builder Tree Variation To override / append / delete the IEC GOOSE / MMS communication representation that exists in Control Builder by importing a modified SCD file. 34 9ARD

35 Section 2 CI868 Communication Interface ConfigurationHandling SCD Reconfiguration and Control To import the modified SCD file, system displays the difference between existing IEC 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. 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 Black Pink Light Green Red Blue Description To represent the node that is fixed and does not get affect by IEC Import Wizard. To represent the node that is identical on both sides. To represent the new node that is added in the current SCD file. To represent the changed node that is available on both sides. To represent the node (that is available under CI868) in Control Builder that will be deleted during the updation SCD file content into the Control Builder. 9ARD

36 Handling SCD Reconfiguration and Control Builder Tree Variation Section 2 CI868 Communication Figure 8. TreeView Comparator 36 9ARD

37 Section 2 CI868 Communication Interface ConfigurationHandling SCD Reconfiguration and Control 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, this controller and its sub tree will be considered as newly created in the SCD file. Suppose it is matching, controller node in the comparator will be shown that it is identical. Suppose the controller is available in the Control Builder and is not available in the tree which is created from the SCD file content. Light Green Pink Black 9ARD

38 Handling SCD Reconfiguration and Control Builder Tree Variation Section 2 CI868 Communication Table 4. Basic Rule of the Comparison for each Hardware Unit Type Representation Comparison Rule Color 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, this CI868 and its sub tree will be considered as newly created in the SCD file. Suppose CI868 is available in the Control Builder and does not available in the SCD file, this CI868 and sub tree (MyIED, LN and CDC Group Hardware Unit) will be shown as Black. Light Green 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. Otherwise the node is knows as same but the contents are different. Pink 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. The value of that parameter is not same. Pink Red 38 9ARD

39 Section 2 CI868 Communication Interface ConfigurationHandling SCD Reconfiguration and Control Table 4. Basic Rule of the Comparison for each Hardware Unit Type Representation Comparison Rule Color LD The MyIED has only one LD. Hence, the contents will be compared. The value of the LD Name parameter will be compared. The value of that parameter is same. The value of that parameter is not same. Pink Red 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, 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. Otherwise the node is knows as same but the contents are different. Pink 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. The value of that parameter is same. The value of that parameter is not same. Pink Red 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 9ARD

40 Import Rules based on CI868 Access Point Criteria Section 2 CI868 Communication Interface 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 5 describes the rules for importing SCD file based on CI868 Access Point criteria. Table 5. Import Rules based on CI868 Access Point Criteria Action Invoke IEC61850 Wizard from Control Builder Select CI868 Access Point from SCD file in IEC61850 Wizard Description From CI868 IED at position n. 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. 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. 40 9ARD

41 Section 2 CI868 Communication Interface Configuration SCD File Import Errors in IEC SCD File Import Errors in IEC Wizard IEC 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 Wizard errors applicable during SCD file import operation. Table 6. IEC Wizard Error Messages - SCD Import Inconsistent SCD file Scenario IEC Wizard is opened with corrupted or missing dll file. SCD file in the text file format. More than one access point is available in CI868 IED. SCD file does not contain CI868 IED or AC800M IED. Access point is not available in SCD File. Excess no. of GOOSE Control Blocks per CI868. LD is not available in SCD File. Excess no. of LN in a LD. Error message displayed during SCD file import Could not load file or assembly ABB.AC800M.IEC61850ET.SCDImporter, Version= , Culture=neutral, PublicKeyToken=null or one of its dependencies. The system cannot find the file specified. Invalid SCD File There is more than one access point available under CI868 IED in the SCD File. SCD file does not contain AC800M IED or CI868 IED. There is no access point available under IED in the SCD File. 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. Error while importing the SCD file. SCD Import is cancelled. LN Instance count exceeds the Max allowed (253) in the given SCD file. SCD Import is cancelled. 9ARD

42 SCD File Import Errors in IEC Wizard Section 2 CI868 Communication Interface Table 6. IEC Wizard Error Messages - SCD Import Inconsistent SCD file Scenario LD0 is not available in CI868 IED. LN0 is not available in a LDevice. LPHD is not available in a LDevice. Server information is not available in Access Point. SCD file has two CI868 IEDs having same instance name. Excess number of Data Set entries per Data Set. Excess number of Data Attribute instances per CI868. SCD file with an unsupported LN. SCD file with identical LNs under same LD. SCD file has more than 10 LDs under a CI868 IED. Error message displayed during SCD file import Error while importing the SCD file. SCD Import cancelled Invalid SCD File Aborting SCD File Import! LPHD is not available under Logical Device Server is not available under access point 1 for IED AC800M in the SCD file. SCD Import is cancelled. Invalid SCD File Excess number of FCDA for AccessPoint <CI868 IED> in <Data Set Name>. The maximum FCDA allowed for an Dataset is 150 only. SCD Import is cancelled. Excess number of DAI for Accesspoint <CI868 IED>. The maximum DAI allowed for an AccessPoint is 5500 only. SCD Import is cancelled. Error while creating the LN Node into the Tree Model. SCD import is cancelled. Invalid SCD File Number of LDs is more than 10 for AccessPoint <access point number>. SCD import is cancelled 42 9ARD

43 Section 2 CI868 Communication Interface Configuration SCD File Import Errors in IEC Table 6. IEC Wizard Error Messages - SCD Import Inconsistent SCD file Scenario SCD file has more than 100 IED per CI868. SCD file has more than 50 LDs configured for CI868 MMS Receive per IED. Signal and Quality attribute is not configured in the SCD file. Excess number of LNs in the imported SCD file. IAL mapping template for Gateway Client is deleted from the running path of project. CCF file of CI868 is missing from the Control Builder project folder. Importing SCD file with ITCI LN, RCBs configured to CI868 using CI868 Hardware Library version less than or equal to 2.x. Error message displayed during SCD file import Excess number of IEDs under the accesspoint <access point number>. SCD Import is cancelled. Number of MMS Ldevices is more than 50 in IED. SCD Import is cancelled. 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. LN instance count exceeds the Max allowed (253) in the given SCD file. SCD Import is cancelled. 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 is not created for the CI868 instance <CI868 IED > under controller < Controller name> in Control Builder. CCF View is Cancelled. Connected CI868 hardware library is not compatible with selected MMS configured SCD file. SCD Import cancelled. 9ARD

44 CCF View Section 2 CI868 Communication Interface Configuration Table 6. IEC Wizard Error Messages - SCD Import Inconsistent SCD file Scenario IAL Mapping file is missing from its location. Error message while creating Control Builder Hardware Tree without installing Hardware Library. Error message displayed during SCD file import 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 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 hwl does not exist. CCF View The CCF view function helps in viewing the CCF file generated by IEC Wizard after successful SCD import. The CCF file is further used during restart of CI868 module to initialize IEC61850 stack. 44 9ARD

45 Section 2 CI868 Communication Interface Configuration CCF View CCF tab view is displayed in IEC Wizard (see Figure 9). The All CCF Files panel displays the list of available CCF files / CI868 node for all the AC 800M controller in the tree view. Figure 9. CCF View Select the CCF file of the access point to verify the number of datasets available in the corresponding CCF file. Figure 10. CCF View Datasets 9ARD

46 CI868 IED as IEC MMS Client Section 2 CI868 Communication Interface Configuration 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. 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 as shown Figure 11. Figure 11. CCF File Tree Structure CI868 IED as IEC MMS Client CI868 module supports MMS client functionality on IEC network. MMS client is defined on each IED MMS server with definition of RCBs. A single IEC subnetwork is configured with one CI868 module. Additional CI868 is used for same IEC subnetwork for handling data transfer beyond the recommended limits per CI868. IEC Wizard tool imports the SCD files configured with CI868 as RCB client and generate hardware tree in Control Builder containing MMS objects. Each MMS client (CI868 through ITCI) can be connected to these RCBs during communication configuration. 46 9ARD

47 Section 2 CI868 Communication Interface Configuration CI868 Data Receive through 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 network (CI868) with AC 800M Control network. 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 control application program. 9ARD

48 CI868 Control Commands through MMS Section 2 CI868 Communication Interface Configuration CI868 Control Commands through MMS LN ITCI (Telecontrol Interface) when configured under CI868 module represents CI868 IED as MMS client in an IEC 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 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 Direct and Select Before Operate type of control commands (send). Figure 12 represents hardware editor of XCBR logical node. Figure 12. XCBR Hardware Editor - Control Command 48 9ARD

49 Section 2 CI868 Communication Interface Configuration CI868 Control Commands through MMS Table 7. 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 9ARD

50 CI868 Control Commands through MMS Section 2 CI868 Communication Interface Configuration Table 7. XCBR Control Commands Channels (Continued) Control Builder Channel Name Data Type / Direction IEC61850 Data Object Description 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. 50 9ARD

51 Section 2 CI868 Communication Interface Configuration CI868 Control Commands through MMS Figure 13 represents hardware editor of CSWI logical node. Figure 13. 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. 9ARD

52 CI868 Control Commands through MMS Section 2 CI868 Communication Interface Configuration Table 8. CSWI Switch Position Control Channels Control Builder Channel Name Data Type / Direction IEC61850 Data Object 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 52 9ARD

53 Section 2 CI868 Communication Interface Configuration CI868 Control Commands through MMS Table 8. CSWI Switch Position Control Channels (Continued) Control Builder Channel Name Data Type / Direction IEC61850 Data Object Description 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. 9ARD

54 IEC Protocol Information in I/O channel Section 2 CI868 Communication Interface IEC 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 as shown in Figure 14, Figure 15 and Figure ARD

55 Section 2 CI868 Communication Interface Configuration IEC Protocol Information in I/O Figure 14. SCD file - Logical Node ATCC, DataSet Level 9ARD

56 IEC Protocol Information in I/O channel Section 2 CI868 Communication Interface Figure 15. SCD file - Logical Node ATCC, Inputs Section level 56 9ARD

57 Section 2 CI868 Communication Interface Configuration IEC Protocol Information in I/O Figure 16. SCD file - Logical Node ATCC, LN Level 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 network. Protocol information for the GOOSE Send under MyIED is in the following format: SubNetworkName.IEDName. 9ARD

58 IEC Protocol Information in I/O channel Section 2 CI868 Communication Interface Figure 17. 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. Protocol information for GOOSE receive blocks under IED is in the following format: SubNetworkName.IEDName.LogicalDeviceName.LogicalNodeName.DataObj ectname. Figure 18. 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.attribute name. 58 9ARD

59 Section 2 CI868 Communication Interface Configuration IEC Protocol Information in I/O Figure 19. Hardware Editor - Protocol Information of MMS Signals Protocol Info field is left empty, if the data on the sending and receiving channel are not subscribed. 9ARD

60 Supported AC 800M Data Types Section 2 CI868 Communication Interface Configuration Supported AC 800M Data Types Following data types are supported by IEC 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. Table 9 lists GOOSE Logical Node CDC types mapped into IEC variable. Table 9. Data Type Mapping for GOOSE Send and Receive LNs in Control Builder IEC61850 Attr. Type (CDC Type) Supported DAs IEC Variable Type GOOSE Send SPS stval BoolIO q t DPS stval DintIO q t INS stval DintIO q t GOOSE Receive 60 9ARD

61 Section 2 CI868 Communication Interface Configuration GOOSE Send and Receive Table 9. Data Type Mapping for GOOSE Send and Receive LNs in Control Builder IEC61850 Attr. Type (CDC Type) MV mag.f RealIO q t ACT general BoolIO q t ACD general BoolIO q t SPC stval BoolIO q t DPC stval DintIO q t INC stval DintIO q t BSC stval DintIO q t Supported DAs IEC Variable Type GOOSE Send GOOSE Receive 9ARD

62 CI868 MMS Receive LN Representations Section 2 CI868 Communication Interface Configuration Quality is internally set by the Communication Interface firmware based on error conditions. IEC Stack updates the Time while sending. It cannot be set from IEC application. 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. For more information on supported CDC type and the logical node channels, refer to Appendix A, MMS Logical Node Channels. Figure 20. CSWI Hardware Editor 62 9ARD

63 Section 2 CI868 Communication Interface Configuration CI868 MMS Control Commands CI868 MMS Control Commands MMS control commands supports DPC CDC type. Table 10 Lists MMS control command CDC type mapped into IEC variable. Table 10. Data-type Mapping for Control Commands in Control Builder IEC61850 CDC Type Supported DAs IEC 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 9ARD

64 Representing CI868 Operating Status as an IED: LN0, LPHD Section 2 CI868 Communication 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 application by collecting information about the operation status of the AC 800M in general. In addition to the IEC specific Data Object channels, LN0 also contain diagnostic channels. For details, refer to CI868 IED Diagnostic Information on page 105. LN0 is the Controlling Logical Node for all Logical Nodes under a Logical Device. It has the Data Objects/channels as shown in Table 11. Table 11. LN0 Channel Details CI868 Channel Name IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type Mod Mode Output. INC DintIO This represents the mode of LD. Beh Behavior INS DintIO Health Health INS DintIO GOOSE Values Received - - DintIO GOOSE Values Sent - - DintIO GOOSE Values Received Per Second - - DintIO 64 9ARD

65 Section 2 CI868 Communication Interface Configuration Representing CI868 Operating Status as CI868 Channel Name 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 Number of IEDs Configured for Reporting Number of IEDs Connected for Reporting Number of Buffered Report Control Blocks Configured Number of Buffered Report Control Blocks Enabled Number of Unbuffered Report Control Blocks Configured Number of Unbuffered Report Control Blocks Enabled Table 11. LN0 Channel Details (Continued) IEC Attr. Name Explanation IEC Attr. Type (CDC Type) - - DintIO - - DintIO - - DintIO - - DintIO - - DintIO - - DintIO - - DintIO IEC Variable Type 9ARD

66 Representing CI868 Operating Status as an IED: LN0, LPHD Section 2 CI868 Communication LPHD is the Logical Node with Physical Device Information. It has the Data Objects/channels as shown in Table 12. CI868 Channel Name Table 12. LPHD Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) PhyHealth Physical Health INS IntIO IEC Variable Type 66 9ARD

67 Section 2 CI868 Communication Interface Configuration Cross Referencing IEC Data with Cross Referencing IEC Data with IEC Variables For Data Subscribed by CI868 (Signal in an IED to IEC ) The steps involved in making a cross reference between IEC data, subscribed by CI868 from other IEDs, and the IEC variables used in the logic are explained below: 1. Operate Data of Logical Node PHPIOC from IED AA12 is sent to CI868. Figure 21. CCT with Operate Data 2. Operate Data is the part Dataset StatNrml. 9ARD

68 For Data Subscribed by CI868 (Signal in an IED to IEC ) Section 2 CI868 Communication 3. AA1A1 is the AC 800M IED that receives Operate Data. This data is reflected as shown in Figure 22. Figure 22. CCT with Client IED 4. AA1A1 is part of the client IED. This can be verified by checking the input section of AA1A1 IED as shown in Figure 23. Figure 23. CCT with Input Section 68 9ARD

69 Section 2 CI868 Communication Interface Configuration For Data Subscribed by CI868 (Signal in 5. The SCD file is represented in the IEC wizard as shown Figure 24. The IED that sends the data (in this case it is AA12) is shown in small circle in Figure 24. Figure 24. TreeView Comparator with IED and Protocol Information 6. Under Protocol Information in Figure 24, each protocol info field shows which IED positioned in which Substation / Voltage / Bay is providing the data to the CI868 IED. 9ARD

70 For Data Published by CI868 (IEC Signal to IED) Section 2 CI868 Communication 7. In Control Builder tree structure, IED AA12 is populated as shown in Figure 25. The protocol information field shows the details of the data from where it is being sent. Figure 25. Control Builder with IED AA12 8. Connect IEC variable in the variable field. The data from the IED is presented to the IEC application running in the AC 800M controller. For Data Published by CI868 (IEC Signal to IED) The steps involved in making a cross reference between IEC variables used in the logic and published by AC 800M to other IEDs over IEC are explained: 70 9ARD

71 Section 2 CI868 Communication Interface ConfigurationFor Data Published by CI868 (IEC Operate Data of Logical Node LS PTRC of AC 800M IED (AA1A1) is sent to IEDs. Figure 26. CCT with Operate Data for Sending 2. Operate Data is the part of Dataset AA1A1_DS. 9ARD

72 For Data Published by CI868 (IEC Signal to IED) Section 2 CI868 Communication 3. IED AA11, AA12 and AA13 are the receiving IEDs as shown under Client IED in Figure 27. Figure 27. CCT with Operate Data for Receiving 4. The SCD file is represented in the IEC Import wizard as shown in Figure 28. IED that sends the data (in this case it is AA1A1) is shown in a 72 9ARD

73 Section 2 CI868 Communication Interface ConfigurationFor Data Published by CI868 (IEC circle. The data from LS PTRC is sent to the IEDs as shown in the protocol information field. Figure 28. TreeView Comparator with IED AA1A1 5. The protocol info field shows which IEDs positioned in which Substation / Voltage / Bay is receiving the data to the CI868. 9ARD

74 Configuration Section 2 CI868 Communication Interface Configuration 6. In Control Builder tree structure, MyIED AA1A1 is populated as shown in Figure 29. The protocol information field shows the details of the data to where it is being sent. Configuration Figure 29. Hardware Editor 7. Data from CI868 is being sent to the Partner IED in the network. 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. 74 9ARD

75 Section 2 CI868 Communication Interface Configuration Data Quality for Received Data Timestamp (optional): User can decide if the Data attribute needs to be sent with or without timestamp. In IEC 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 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 application. Data Quality for Received Data Table 13 shows the quality bits that are used in GOOSE messages for SPS, DPS, INS and measured values. IEC protocol column specifies the quality bit as per the standards. Table Quality Bits IEC Quality signal Bit Position Description of Bit 0 Validity 00=Good 01=Bad 1 2 Overflow 3 OutOfRange 4 Bad Reference 5 Oscillatory 6 Failure 9ARD

76 Data Quality for Received Data Section 2 CI868 Communication Interface Configuration Table Quality Bits (Continued) 7 Old Data 8 Inconsistent 9 Inaccurate 10 Source 11 Test 12 Operator Blocked Channel status, when the incoming GOOSE message quality is bad: 0x (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. 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 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 quality bits (0-9) (see Table 13) is set, the I/O copy routine will be informed to set the IEC 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. 76 9ARD

77 Section 2 CI868 Communication Interface Configuration Supported Logical Nodes Supported Logical Nodes Among the types of Logical Nodes that IEC 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 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. Load Shedding Applications Two Logical Nodes for Load Shedding applications: LS GAPC is a GAPC with the Data Objects/channels as shown in Table 14. AC 800M Channel Name Table 14. LS GAPC Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) Str Start of Operation ACD BoolIO Op Operate of Function ACT BoolIO AC 800M Channel Name Table 15. LS PTRC Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) Op Operate of Function ACT BoolIO Tr1 Trip Signal ACT BoolIO Tr2 Trip Signal ACT BoolIO Tr3 Trip Signal ACT BoolIO Tr4 Trip Signal ACT BoolIO IEC Variable Type IEC Variable Type 9ARD

78 Supported Logical Nodes Section 2 CI868 Communication Interface Configuration Table 15. LS PTRC Channel Details (Continued) Tr5 Trip Signal ACT BoolIO Tr6 Trip Signal ACT BoolIO Tr7 Trip Signal ACT BoolIO Tr8 Trip Signal ACT BoolIO Tr9 Trip Signal ACT BoolIO Tr10 Trip Signal ACT BoolIO Generator Real Power Control PC GAPC is a GAPC for Generator Real Power Control with the Data Objects/channels as shown in Table 16. AC 800M Channel Name Table 16. PC GAPC Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type Str Start of Operation ACD BoolIO Op Operate of Function ACT BoolIO SPCSO1 SPCSO2 Watt Hz Frequency (Speed) Raise Command Information Frequency (Speed) Lower Command Information Real Power set Point Information Frequency Set Point Information SPC SPC MV MV BoolIO BoolIO RealIO RealIO 78 9ARD

79 Section 2 CI868 Communication Interface Configuration Supported Logical Nodes Bus Bar Change BB GAPC is a GAPC for Bus Bar Change with the Data Objects/channels as shown in Table 17. Table 17. BB GAPC Channel Details AC 800M Channel Name Str Op SPCSO1 SPCSO2 SPCSO3 SPCSO4 SPCSO5 SPCSO6 SPCSO7 IEC Attr. Name Explanation Start of Operation Operate of Function Bay Control Command Information Bay Control Command Information Bay Control Command Information Bay Control Command Information Bay Control Command Information Bay Control Command Information Bay Control Command Information IEC Attr. Type (CDC Type) ACD ACT SPC SPC SPC SPC SPC SPC SPC IEC Variable Type BoolIO BoolIO BoolIO BoolIO BoolIO BoolIO BoolIO BoolIO BoolIO 9ARD

80 Supported Logical Nodes Section 2 CI868 Communication Interface Configuration Table 17. BB GAPC Channel Details (Continued) SPCSO8 Bay Control Command Information SPC BoolIO SPCSO9 Bay Control Command Information SPC BoolIO SPCSO10 Bay Control Command Information SPC BoolIO Transformer Tap Control TC1 ATCC is an ATCC for Transformer Tap Control with the Data Objects/channels as shown in Table 18. Table 18. TC1 ATCC Channel Details AC 800M Channel Name IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type Loc Local operation SPS BoolIO ParOp Parallel/ DPC DintIO Independent operation CtlV Voltage Set Point Information MV RealIO SPCSO1 Tap Raise Command Information SPS BoolIO 80 9ARD

81 Section 2 CI868 Communication Interface Configuration Supported Logical Nodes Table 18. TC1 ATCC Channel Details (Continued) SPCSO2 Tap Lower Command Information SPS BoolIO SPCSO3 Stop Command Information SPS BoolIO TC2 ATCC is an ATCC for Transformer Tap Control with the Data Objects/channels as shown in Table 19. AC 800M Channel Name Table 19. TC2 ATCC Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type Loc Local operation SPS BoolIO ParOp Mode of Operation DPC DintIO CtlV ISCSO Voltage Set Point Information Tap Position Command Information MV INC RealIO DintIO Generator Reactive Power Control QC ARCO is an ARCO for Generator Reactive Power Control with the Data Objects/channels as shown in Table 20. Channel (Data Object) Table 20. QC ARCO Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type Loc Local operation SPS BoolIO 9ARD

82 Supported Logical Nodes Section 2 CI868 Communication Interface Configuration Table 20. QC ARCO Channel Details Str Start of Operation ACD BoolIO Op Operate of Function ACT BoolIO SPCSO1 Voltage Raise Command Information SPC BoolIO SPCSO2 Voltage Raise Command Information SPC BoolIO Vol Voltage Set Point Information MV RealIO VolAmpr Reactive Power set Point Information MV RealIO PwrFact Power Factor Set Point Information MV RealIO QC1 ARCO is an ARCO for Generator Reactive Power Control with the Data Objects/channels as shown in Table 21. Table 21. QC1 ARCO Channel Details Channel (Data Object) IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type Loc Local operation SPS BoolIO Str Start of Operation ACD BoolIO Op Operate of Function ACT BoolIO Vol Voltage Set Point Information MV RealIO VolAmpr Reactive Power set Point Information MV RealIO 82 9ARD

83 Section 2 CI868 Communication Interface Configuration Supported Logical Nodes Table 21. QC1 ARCO Channel Details Channel (Data Object) IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type PwrFact Power Factor Set Point Information MV RealIO TapChg Change reactive power. BSC DintIO Bus Bar Voltage Control VC AVCO is an AVCO for Bus bar voltage control with the Data Objects/channels as shown in Table 22. Channel (Data Object) Table 22. VC AVCO Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) Loc Local Operation SPS BoolIO Str Start of Operation ACD BoolIO Op Operate of Function ACT BoolIO SPCSO1 SPCSO2 SPCSO3 Vol Voltage Raise Command Information Voltage Raise Command Information Stop Command Information Voltage Set Point Information SPC SPC SPC MV IEC Variable Type BoolIO BoolIO BoolIO RealIO 9ARD

84 Supported Logical Nodes Section 2 CI868 Communication Interface Configuration VC1 AVCO is an AVCO for Bus bar voltage control with the Data Objects/channels as shown in Table 23. Channel (Data Object) Table 23. VC1 AVCO Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) Loc Local Operation SPS BoolIO Str Start of Operation ACD BoolIO Op Operate of Function ACT BoolIO Vol TapChg Voltage Set Point Information Change reactive power. MV BSC IEC Variable Type RealIO DintIO Channel (Data Object) Generic Logical Nodes GF GGIO is a GGIO for General Purpose with the Data Objects/channels as shown in Table 24. Table 24. GF GGIO Channel Details IEC Attr. Name Explanation IEC Attr. Type (CDC Type) IEC Variable Type SPCSO1 Single Point Command Information SPS BoolIO SPCSO2 Single Point Command Information ACD BoolIO SPCSO3 Single Point Command Information ACT BoolIO SPCSO4 Single Point Command Information SPC BoolIO SPCSO5 Single Point Command Information SPC BoolIO DPCSO1 Double Point Command Information DPC DintIO DPCSO2 Double Point Command Information DPC DintIO 84 9ARD

85 Section 2 CI868 Communication Interface Configuration Supported Logical Nodes Table 24. GF GGIO Channel Details (Continued) DPCSO3 Double Point Command Information DPC DintIO DPCSO4 Double Point Command Information DPC DintIO DPCSO5 Double Point Command Information DPC DintIO ISCSO1 ISCSO2 ISCSO3 ISCSO4 ISCSO5 Integer Value Set Point Command Information Integer Value Set Point Command Information Integer Value Set Point Command Information Integer Value Set Point Command Information Integer Value Set Point Command Information INC INC INC INC INC DintIO DintIO DintIO DintIO DintIO AnIn1 Real Value Information MV RealIO AnIn2 Real Value Information MV RealIO AnIn3 Real Value Information MV RealIO AnIn4 Real Value Information MV RealIO AnIn5 Real Value Information MV RealIO 9ARD

86 Configuration Parameters Section 2 CI868 Communication Interface Configuration Configuration Parameters All applicable configuration of the CI868 and the hardware units under the CI868 tree is done by the IEC Wizard, based on the imported SCD file. Table 25 to Table 28 shows the configuration parameters of the hardware units imported. Table 25. CI868 IED Communication Configuration Parameter Access Point Name IP Address Subnet Mask SCD File Identification Subnetwork Name IP Address Description Access point number Primary CI868 IP Address Primary Subnet Mask SCD modified date and time Name of the Subnetwork IP Address for the IED. Table 26. Project IED Name Configuration Parameter MYIED name Description Description IED name given to the CI868 IED Description used for the ICD file export Table 27. LD Configuration Parameters LD Name Parameter Description Description Name for the Logical device. Description used for the ICD file export 86 9ARD

87 Section 2 CI868 Communication Interface Configuration Application Redundancy Table 28. LN configuration parameters LN Name Parameter Description Description Name for the Logical node. Description used for the ICD file export Application Redundancy Application 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. 9ARD

88 CI868 MMS Control Function Block with IEC Section 2 CI868 Communication Interface CI868 MMS Control Function Block with IEC ProcessObjectBasicLib 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 Application connects and controls the IO channels of the node objects to IEC 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. 88 9ARD

89 Section 2 CI868 Communication Interface Configuration IED Command Send IED Command Send IEDCommandSend function block is represented as shown in Figure 30. Figure 30. IED Command Send Table 29 lists the IEDCommandSend function block parameters. Table 29. IEDCommandSend function block parameters Pin Name Control 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 9ARD

90 IED Command Send Section 2 CI868 Communication Interface Configuration Table 29. IEDCommandSend function block parameters (Continued) Pin Name Control Builder Datatype Initial Value Attributes Direction Definition 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 90 9ARD

91 Section 2 CI868 Communication Interface Configuration IED Command Send Table 29. IEDCommandSend function block parameters (Continued) Pin Name Control Builder Datatype Initial Value Attributes Direction Definition 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 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 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. 9ARD

92 IED Command Send Section 2 CI868 Communication Interface Configuration 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 application. Figure 31 shows a detailed sequence flow of IEDCommandSend function block. 92 9ARD

93 Section 2 CI868 Communication Interface Configuration IED Command Send Figure 31. IEDCommandSend Flowchart 9ARD

94 IED Status Receive Section 2 CI868 Communication Interface Configuration IED Status Receive IEDStatusReceive function block is represented as shown in Figure 32. Figure 32. IED Status Receive Table 30 lists the IEDStatusReceive Function Block parameters. Table 30. 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 IEDStatusReceive 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 Alarms and Events are not generated from IEDStatusReceive function block. 94 9ARD

95 Section 2 CI868 Communication Interface Configuration IED Status Receive Figure 33 displays a sample IEC Application based on UniSimple_1 function blocks for Select Before Operate (SBO) command, used for application logic to control circuit breakers. Figure 33. SBO Function Block - Offline 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 9ARD

96 IED Status Receive Section 2 CI868 Communication Interface Configuration 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. 96 9ARD

97 Section 2 CI868 Communication Interface Configuration IED Status Receive Figure 34. SBO Function Block - Online 9ARD

98 CI868 Support of Sequence of Event (SOE) Section 2 CI868 Communication Interface CI868 Support of 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 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 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 31 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. 98 9ARD

99 Section 2 CI868 Communication Interface Configuration CI868 Support of Sequence of Event Table 31. AC 800M Controller External Events Circuit Breaker Position value Circuit Breaker position - Faulty Circuit Breaker position - Close Circuit Breaker position - Open Circuit Breaker position - Intermediate Circuit Breaker Selection Status External Event Faulty Alarm Close Event Open Event Intermediate Event Selection Event External Event Signal ID <HwAddress>.<BreakerNumber>.A_Flt for example: A_Flt <HwAddress>.<BreakerNumber>.E_Cls for example: E_Cls <HwAddress>.<BreakerNumber>.E_Opn for example: E_Opn <HwAddress>.<BreakerNumber>.E_Int for example: E_Int <HwAddress>.<BreakerNumber>.E_Sel for example: E_Sel 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 E_Cls The external timestamp is available only for Circuit Breaker Pos.Status and is not supported for Circuit Breaker Selection Status. 9ARD

100 Configuration for Generating Alarm and Events Section 2 CI868 Communication Interface Configuration for Generating Alarm and Events Figure 35 depicts the overall CI868 configuration applicable to generate External Events for Circuit Breaker position Status. Figure 35. Hardware Address and Signal ID Mapping 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. Any changes done under a particular CI868 Hardware Object in the Control Builder tree structure will restart the CI868 module ARD

101 Section 2 CI868 Communication Interface Configuration Configuration for Generating Alarm and Figure 36. Generate Alarms in IED Hardware object 9ARD

102 IEC Application for using External Events Section 2 CI868 Communication Interface IEC Application for using External Events Figure 37 and Figure 39displays a sample IEC Application to generate Process Alarms and Events out of External Events. Figure 37. Alarm Condition Function Block - Offline Figure 38. Alarm Condition Function Block - Online 102 9ARD

103 Section 2 CI868 Communication Interface ConfigurationIEC Application for using External Figure 39. Simple Event Detector Function Block - Offline 9ARD

104 IEC Application for using External Events Section 2 CI868 Communication Interface Figure 40. Simple Event Detector Function Block - Online Without the IEC application, the External Events appear as System Events with the hardware address of Circuit breaker as Object Source and Controller Timestamp 104 9ARD

105 Section 2 CI868 Communication Interface Configuration CI868 IED Diagnostic Information CI868 IED Diagnostic Information Diagnostic 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. The Diagnostic information contains details about RCBs and GOOSE Signal provided by IEC61850 stack. Figure 41. LN0 Hardware Editor With Diagnostics Information 9ARD

106 CI868 IED Diagnostic Information Section 2 CI868 Communication Interface Configuration Further individual IED level diagnostics for MMS is available under Diag object under each IED. Figure 42. Diag Hardware Editor With Diagnostics Information Table 32 describes the MMS diagnostics information available. Table 32. LN0 and Diag Hardware editor diagnostics information Diagnostics Information LN0 Diag info GOOSE values received GOOSE Values Sent GOOSE Values Received Per second GOOSE Values Sent Per Second CPU Load Sender Cycles per Second MMS Values Received MMS Commands Sent Description Number of GOOSE data values received from other IEDs. Number of GOOSE data values sent to other IEDs. Number of GOOSE values received from other IEDs per second. Number of GOOSE values sent to other IEDs per second. CPU load of the CI868 module in percentage updated every minute. Number of times the sender task has traversed the send list containing the Data object, to be sent out on change. Number of MMS data values received from other IEDs. Number of MMS data values sent to other IEDs ARD