SCL Tool. Configuration manual

REF 542plus

1MRS756342 Issued: 30.04.2007 Version: B/30.10.2009 REF 542plus Contents Copyrights... 5 1. Introduction...7 1.1. This manual... 7 1.2. Use of symbols... 7 1.3. Product documentation... 8 1.4. Document revisions... 8 2. Product overview...9 3. IEC 61850 standard...11 4. Installation...13 4.1. System requirements... 13 4.2. REF 542plus installation... 13 4.3. Uninstalling REF 542plus... 19 5. SCL files and folders...21 5.1. 61850 XML File Pool... 21 5.2. GUIData... 23 5.3. Missing Dataset FCDA Entries... 23 5.4. UserData... 23 5.5. Symbol Library... 24 5.6. SCL schema file pool... 24 5.7. XML templates... 25 6. Components...27 6.1. SCL GUI... 27 6.1.1. Menu bar... 28 6.1.2. SCL file generation... 31 6.1.3. CID/ICD Import... 64 6.1.4. SCD import... 98 6.1.5. FTP Download/Upload...105 6.1.6. Firmware download...110 6.1.7. Graphical FTP... 111 6.1.8. TELNET interface...113 6.2. SCL core component...116 6.3. ECM core component...136 7. error and exception handling... 141 7.1. Missing files...141 7.2. Configuration Tool RCA file...142 7.3. GUI Validations...143 7.3.1. SCL Generation...143 7.3.2. ECM generation...144 7.3.3. CID/ICD import...153 3

REF 542plus 1MRS756342 7.3.4. SCD import...155 7.3.5. FTP download or upload...156 7.3.6. Graphical FTP...156 8. Terminology... 157 9. Abbreviations... 159 4

1MRS756342 Copyrights REF 542plus The information in this document is subject to change without notice and should not be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any errors that may appear in this document. In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Oy be liable for incidental or consequential damages arising from the use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB Oy, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied or disclosed only in accordance with the terms of such license. Copyright 2009 ABB Oy All rights reserved. Trademarks ABB is a registered trademark of ABB Group. All other brand or product names mentioned in this document may be trademarks or registered trademarks of their respective holders. Guarantee Please inquire about the terms of guarantee from your nearest ABB representative. 5

6

1MRS756342 REF 542plus 1. Introduction 1.1. This manual This manual provides thorough information on the REF 542plus application that is used to generate IEC 61850 standard compliant REF 542plus configuration files (SCL files). The REF 542plus Protect IT multifunction feeder protection and control unit, henceforth called REF 542plus, can be adapted to the IEC 61850-based substation communication standard to achieve interoperability between ABB products and the external IEC 61850 world. In order to achieve this purpose, two major components are required: * Communication component: Ethernet communication card * IEC 61850 Configuration component: REF 542plus Engineering Tool for the Ethernet card The purpose of this document is to describe the features and the userrelated activity needed to interact with the in order to obtain the SCL files. User interface, configuration aspects, generation of SCL files and loading of SCL files into the Ethernet Board are described in this document. This information is intended for application engineers who are familiar with the REF 542plus engineering methodology and the IEC 61850-6 standard-based terminology and engineering to some extent. 1.2. Use of symbols This publication includes the following icons that point out safety-related conditions or other important information: The information icon alerts the reader to relevant facts and conditions. It should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to information or property loss. Therefore, comply fully with all notices. 7

REF 542plus 1MRS756342 1.3. Product documentation Name of the Manual Document ID Real Time Clock Synchronization, IRIG-B Input Time Master 1MRS755870 Product Guide 1MRS756269 Configuration Manual 1MRS755871 ibutton Programmer User Manual 1MRS755863 Manual Part 3, Installation and Commission 1 VTA100004 Manual Part 4, Communication 1VTA100005 Motor Protection with ATEX Certification, Manual 1MRS755862 Configuration Manual 1MRS756342 Protection Manual 1MRS755860 Technical Reference Manual 1MRS755859 Technical Reference Modbus RTU 1MRS755868 Web Manual, Installation 1MRS755865 Web Manual, Operation 1MRS755864 IEC 61850 PIXIT 1MRS756360 IEC 61850 Conformance Statement 1MRS756361 IEC61850 TISSUES Conformance Statement 1MRS756362 Lifecycle Service Tool 1MRS756725 1.4. Document revisions Version IED Revision Date Comment number A 2.5 31.05.2007 First release B 2.6 30.10.2009 Release 2.6 Applicability This manual is applicable to REF 542plus Release 2.6, software version V4F06x. 8

1MRS756342 REF 542plus 2. Product overview The REF 542plus is connected to the substation bus, which is based on the IEC 61850 standard, along with other devices like MicroSCADA (Substation Monitoring/Control Human Machine Interface), PCM 600 (IED Configuration Manager), COM 600 (Substation Gateway) and other ABB and or 3rd party protection and control devices through an Industrial grade Ethernet switch, see Fig. 2.-1. Any generic 3rd party IEC 61850 client can also be connected to the network to access the IEC 61850 configuration and real-time data from the REF 542plus. Fig. 2.-1 Connection diagram A070199 The IEC 61850 standard requires that data from the REF 542plus is available in structured formats (data models/classes and so on). The prescribed way of achieving this objective is through files in XML-based format, termed as Substation Configuration description Language (SCL). The REF 542plus generates an SCL file, containing generic and project specific data (from/to REF 542plus) and mapping information between REF 542plus ETHERNET BOARD and IEC 61850. The provides a graphical user interface (GUI) where the application engineer can choose the desired REF 542plus functions. The uses this information and automatically generates a project specific SCL file. The final form of this file is downloaded to the REF 542plus Ethernet board. 9

10

1MRS756342 REF 542plus 3. IEC 61850 standard The IEC 61850 standard defines the communication between the IEDs in substations. The IEDs support the following functions: * Protection and control * Integration of innovative sensor and switch technologies * Metering, supervisory control and data acquisition (SCADA) * Remote monitoring and fault diagnostics * Automated dispatch and control * Asset management * Condition monitoring and diagnostics IEC 61850 provides: * Standardized information models for all kinds of protection relays, controllers, disconnectors, earthing switches, circuit breakers, transformers and so on. * Information exchange methods to access the information model s data: report sequences of events, log historical data, control devices, sampled value distribution, fast peer-to-peer process data exchange and so on. * A unified system configuration language (XML-based) and device on-line self description. Compared to other communication standards for Substation Automation, the IEC 61850 standard defines data modeling and communication services for this specific domain. Data modeling is mapped to a communication protocol, Manufacturing Message Specification (MMS, ISO 9506 protocol), which uses TCP/ IP and Ethernet. In addition to the communication specifications, engineering information exchange is defined in SCL, which is an XML-based language. 11

12

1MRS756342 REF 542plus 4. Installation 4.1. System requirements The system requirements for the are as follows: * Hardware requirements * Pentium III, 800MHz or higher * 128MB RAM or higher * 13MB free hard disk space * Software requirements * Operating System: Windows 98/Windows 2000/Windows XP * MSXML 4.0 * Microsoft.NET Framework 2.0 The is compatible with the following versions: * REF 542plus hardware Firmware version 2.5 SP1 * REF 542plus Configuration Tool version V4E04x 4.2. REF 542plus installation Follow these steps to install the : 1. Close all applications. 2. Open the installation package which contains the two items shown in Fig. 4.2.-1. Fig. 4.2.-1 installation package A070200 3. Double-click on the Setup.exe file to start the installation. The REF 542plus SCL tool setup wizard dialog opens. 13

REF 542plus 1MRS756342 Fig. 4.2.-2 setup wizard dialog A070201 4. Click Next. The Installation folder selection dialog opens. 14

1MRS756342 REF 542plus Fig. 4.2.-3 Installation folder selection dialog A070202 5. To exit the installation, click Cancel in any dialog during the installation. Fig. 4.2.-4 Cancel confirmation dialog A070203 6. In the cancel confirmation dialog, click Yes to exit the installation or Click No to continue the installation. 7. Select the folder in which the application is to be installed. 8. Click Browse to select a different folder. 15

REF 542plus 1MRS756342 Fig. 4.2.-5 Browse for folder dialog A070204 9. Select the folder to install the application in and click OK. 10.Click the Disk Cost button to see the disk space that the requires Fig. 4.2.-6 Disk Space dialog A070205 11.Click OK to return to the previous dialog. 12.Click Next to go to the next dialog. 16

1MRS756342 REF 542plus Fig. 4.2.-7 Confirm Installation dialog A070206 13.Click Next to confirm the installation. Fig. 4.2.-8 Installing A070207 17

REF 542plus 1MRS756342 Fig. 4.2.-9 Installation complete dialog A070208 14.Click Close to exit from the installation. An icon is set up on the local machine desktop to launch the Application. Fig. 4.2.-10 REF 542plus application icon A070209 15.To start the application, double-click the REF 542plus icon or In the Windows task bar, select Start > Programs > REF 542plus 18

1MRS756342 REF 542plus 4.3. Uninstalling REF 542plus Follow the steps below to uninstall the REF 542plus 1. In the Windows task bar, select Start > Settings > Control Panel > Add or Remove Programs The Add or Remove Programs dialog opens. 2. Select the REF 542plus Ver2.1 file. 3. Click Remove. Fig. 4.3.-1 Add or Remove Programs dialog A070210 4. Verify that the icon on the desktop and selection option in Start > Programs have been removed. The uninstallation only removes the. It does not remove the. NET Framework. 19

20

1MRS756342 REF 542plus 5. SCL files and folders Some of the critical folders and files that get installed by the installation wizard are listed and described in the following. 5.1. 61850 XML File Pool The 61850 XML file pool, as the name suggests, is a collection of XML files in the program folder. The folder is the super set of all available functions in the REF 542plus with their respective SCL tree structures, logical devices (LD), logical nodes (LN), data objects (DO), data attributes (DA), data type templates for the LNs, DOs, DAs and so on. In short, the entire SCL structure (split into various files) required to configure a project specific IEC 61850 compliant REF 542plus IED configuration is present in this file pool. The 61850 XML file pool consists of the files shown in the Fig. 5.1.-1 and are as a whole listed below: Fig. 5.1.-1 61850 XML file pool * REF542plus. XML A070211 This file consists of scaling functions to convert SPA data values to IEC 61850 standard values, and of the logical node zero of REF 542plus (LLN0) and logical node for REF 542plus physical device information (LPHD). * Substation and Communication. XML This consists of the substation and communication parts with default data. The default data are updated from the user data when the SCL generator is invoked for execution. 21

REF 542plus 1MRS756342 * Protection. XML This file consists of all LNs designated for protection functions with SPA (SPA- OPC server modeling) address mapping. All standard data is allocated to LNs as per the IEC 61850 standard. Additional information from protection functions are mapped to LN GGIOs. * Measurement. XML This consists of all probable measurement DOIs in a REF 542plus device. These DOIs (filtered and based on the configuration information in the.rca file) are added to the Measurement LN MMXU with filtering attributes. * Primary Switch. XML This consists of typical LNs for Primary Switch functions like Interlocking open/ close (LN CILO), for control/no control (LN CSWI), for Disconnector / Earth Switch (LN XSWI), for Circuit Breaker (LN XCBR). These LNs / DOIs have default data that is updated from the user data when the SCL generator is invoked for execution. * General Status and Control. XML This comprises all the possible DOIs that can be associated with general I/O functions, allocated under a LN class GGIO (Generic process I/O). The LN/DOIs have default data that is updated from the user data when the SCL generator is invoked for execution. * SIMG. XML This comprises all the possible DOIs that can be associated with the general I/O functions, allocated under an LN class SIMG. The LN/DOIs have default data that is updated from the user data when the SCL generator is invoked for execution. * Data Type Templates. XML This comprises of all possible LNTypes, DOTypes, DATypes, and Enumeration definitions for the LNs defined in the above files, except for the General Status and Control and Measurement functions. * Data Set. XML This comprises of data set definitions for measurement and protection functions besides the status of protection functions (LNs). * Report Control Block. XML This comprises of report control block definitions for all data sets that can be configured. The report control block have default parameters that would be updated from the user data when the SCL generator is invoked for execution. * FBDescription. XML 22

1MRS756342 REF 542plus This part is not required for the standalone version of the REF 542plus but is required for PCM ConnPack. FB (as configured in FUPLA) references along with their respective Function Group assignment, PCM tree structure names and the like for protection, measurement, monitoring and control functions along with necessary filtering attributes are defined in the file. * FunctionListDescriptions. XML This part too is not required for the standalone version of the REF 542plus SCL Tool but is required for PCM ConnPack. For all the FBs defined in the FBDescription. XML file a unique FB reference number is allocated along with necessary filtering attributes. This FB number reference is also made in the Protection.XML, Measurement.XML, Primary Switch.XML and General Status and Control.XML files. 5.2. GUIData This folder comprises the Folderpath.xml and Language.xml files. The Folderpath. xml file is used to store the RCA file path information, while the Language.xml file is used to store the language setting used by the user. 5.3. Missing Dataset FCDA Entries During the SCL Generation, if the FCDA entries in a dataset exceeds the maximum limit, the excess FCDA entries are collected into an XML file. This XML file is saved in this folder. 5.4. UserData This folder is used to save the temporary file which is created when the SCL File generation process starts (by clicking the Generate button). This file is automatically deleted on completion of the SCL File generation process. One such file is created for every REF 542plus configuration. This file contains both GUI and imported RCA file data. 23

REF 542plus 1MRS756342 Fig. 5.4.-1 UserData folder A070212 5.5. Symbol Library This folder contains the SymbolLibrary.xml file. The file contains information for mapping the symbols in the REF Configuration Tool to the COM600 Tool symbols. Fig. 5.5.-1 Symbol Library folder A070574 5.6. SCL schema file pool This comprises a set of IEC 61850 standard XSD (XML Schema Definition) files that is to be used by the REF 542plus Core Component (explained later) to validate every SCL file created by the REF 542plus. 24

1MRS756342 REF 542plus Fig. 5.6.-1 SCL schema file pool A070213 The SCL schema file pool consists of the following files: * SCL.XSD: Comprises references to SCL_Substation.XSD, SCL_IED.XSD, SCL_Communication.XSD and SCL_DataTypeTemplates.XSD. * SCL_Substation.XSD: Schema file for the Substation section of the SCL file. * SCL_Communication.XSD: Schema file for the communication section of the SCL file. * SCL_IED.XSD: Schema file for the IED section of the SCL file. * SCL_DataTypeTemplates.XSD: Schema file for the data type templates section of the SCL file. 5.7. XML templates This folder comprises the following XML templates (file structures) used by the SCL tool to generate the CID/ICD file. * BaseTemplateforCID.xml: Used when generating the CID file. * BaseTemplateforICD.xml: Used when generating the ICD file 25

REF 542plus 1MRS756342 Fig. 5.7.-1 XML templates A070214 26

1MRS756342 REF 542plus 6. Components The can be divided into two major components: * SCL GUI * SCL Core Component 6.1. SCL GUI The GUI component of the contains: * Menu bar: Composed of five menu items, namely File, View, Tools, Window and Help * SCL File Operations Tab strip: Composed of three tabs, namely SCL Generation, SCL Import and FTP Download or Upload. When double-clicking the application icon on the desktop, the application opens and a window is displayed as shown in Fig. 6.1.-1. The user can select any one of the three tabs in the SCL File Operations Tab strip described in the following: * SCL Generation: In this tab, the user can enter the required configuration information for the REF device and generate the SCL files. Thus this tab aids in the creation of an SCL file. * SCL Import: In this tab, the user can import an existing CID/ICD file, modify LNs and then export the same to an SCL file. Thus this tab aids in modification of an SCL file. * FTP Upload or Download: In this tab, the user can download (move a CID file from the system hard disk to the REF 542plus Ethernet board) or upload (move a CID file from the REF 542plus Ethernet board to the system hard disk) via FTP. Thus this tab aids in adding a new configuration file to the Ethernet board or changing the configuration file already present on the Ethernet board. By default the SCL Generation tab is selected, see Fig. 6.1.-1. 27

REF 542plus 1MRS756342 Fig. 6.1.-1 SCL Generation tab A070215 6.1.1. Menu bar The menu bar contains the following main menus: * File The File menu has the following menu commands: * Import Configuration File - To import the REF 542plus Configuration Tool XML file for the SCL Generation tab * Generate SCL - To generate the SCL file for the SCL Generation tab * Import SCL File - To import the SCL file for the SCL Import tab * Export SCL File to Hard Disk - To export the SCL file for the SCL Import tab * Exit To exit from the Depending on the tab selected, the menu commands are enabled or disabled. 28

1MRS756342 REF 542plus Fig. 6.1.1.-1 File menu A070216 * View The View menu has a Project Explorer menu command that can be used to activate the project explorer for SCL Import. The menu command is enabled if the selected tab is SCL Import. Otherwise it is disabled. Fig. 6.1.1.-2 View menu A070217 * Tools The Tools menu consists of two types of menu commands, the default and dynamic menu commands. The default menu commands are always displayed while the dynamic menu commands are displayed depending on the selected tree node in the Project explorer of the SCL Import tab. The default menu commands include: * SCL Generator - Selects the SCL Generator tab * SCL File Import - Selects the SCL Import tab * SCD file import - Selects the SCD Import tab * FTP Download - Selects the FTP Download or Upload tab * Language Handling - Opens a window where the language supported by can be chosen * Firmware download - Selects the Firmware Download tab * TELNET - Opens a window (TELNET) where the TELNET interface can be used Dynamically a menu command is added to the Tools menu depending on the node selected in the Project Explorer of the SCL Import tab. 29

REF 542plus 1MRS756342 If the selected tree node is * LD1, LN Wizard is displayed. Select LN Wizard to open a dialog to add LNs. * LN, DO Wizard is displayed. Select DO Wizard to open a dialog to add DOIs. * DOI, DOI Editor is displayed. Select DOI Editor to open a dialog to edit the attributes for the respective DOI. * DS, Dataset Editor is displayed. Select Dataset Editor to open a dialog to add FCDAs to a dataset. Fig. 6.1.1.-3 Tools menu A070218 * Window The Window menu displays all opened windows as menu commands for the CID/ICD and SCD Import tab. For each instance of a wizard/editor, the respective menu command is displayed in the Window menu. 30

1MRS756342 REF 542plus Fig. 6.1.1.-4 Window menu A070219 * Help The Help menu is provided to help learn more about the. It consists of one menu command. * About Directs to the help documents for the. Fig. 6.1.1.-5 Help menu A070220 6.1.2. SCL file generation 1. Double-click the application icon on the desktop. 2. Select the SCL Generation tab in the SCL File Operations tab strip. The SCL Generation tab contains the 6 tabbed pages listed below which have fields to configure for a REF 542plus device. Some of the fields (configuration information) are filled in by the user and the others are filled by the application after parsing the REF 542plus Configuration Tool XML file. * Files and Folders * Substation Relationship and Time Settings 31

REF 542plus 1MRS756342 * Sensor configuration and Protection * Measurement * Primary Switches * General Status and Control I/Os * Report Control Blocks Fig. 6.1.2.-1 SCL Generation tab A070221 3. Select the Files and Folders tab. The fields in the tab are displayed. Fig. 6.1.2.-2 Files and folders tab A070222 4. Click Import. The Open File dialog box is displayed. The REF 542plus Configuration RCA file to be imported can be selected. 32

1MRS756342 REF 542plus Fig. 6.1.2.-3 RCA file browser A070223 5. Select the REF 542plus Configuration RCA file to be imported to parse it. If any of the mandatory system and protection events is not configured in the RCA file, pops up a window to inform about missing events. This information can be saved with the Save As and Print buttons. Fig. 6.1.2.-4 Event checking information A090130 33

REF 542plus 1MRS756342 Once the file is selected, this REF 542plus Configuration XML/RCA file is parsed for the communication, measurement, protection functions and switching objects-related information. If any of the above data is not configured in the rca file, a dialog box pops up. For example if the protection functions are not configured, the dialog box shown in Fig. 6.1.2.-5 is displayed. Fig. 6.1.2.-5 RCA file configuration information A070224 Once the file is imported, the entire directory text of the REF 542plus configuration RCA file appears in the text box and the file name appears in the Device Reference field. 34

1MRS756342 REF 542plus Fig. 6.1.2.-6 RCA file import A070225 6. Click Import GUI Data to use previously saved GUI data. When this file is imported, the fields that can be edited in all the tabs are filled with the data from the GUD file. 7. Click Open as shown in Fig. 6.1.2.-7 to select a GUD file. Fig. 6.1.2.-7 Select GUD file import A070226 8. Click Browse to select the SCL folder. The generated SCL file is saved to this folder. 9. Click Make New Folder to create a new project folder or choose an existing folder. 35

REF 542plus 1MRS756342 Fig. 6.1.2.-8 SCL file folder browser A070227 10.When the project folder is chosen, the entire directory text appears in the text box, see Fig. 6.1.2.-9. Fig. 6.1.2.-9 SCL file folder path A070228 11.Select the type of SCL file to be generated, see Fig. 6.1.2.-10. Fig. 6.1.2.-10 Selecting SCL file type A070229 12.Select *.ICD to generate an ICD file and *.CID to generate a CID file. The SCL tool can be used to create only one type of file(s) in a cycle. Moving to other tabs in the SCL generation tab is only possible if all fields in the Files and Folders tab are filled. 13.Click Import SVG to open the Open Dialog box where the SVG file containing the SLD information to be imported can be selected. 36

1MRS756342 REF 542plus Fig. 6.1.2.-11 Selecting SVG file A070556 Once the file is selected, the entire file is parsed for SLD-related information. 14.Select the Substation Relationship and Communication Settings tab to define the REF 542plus device s relationship to the Substation and to view the protocol information. 37

REF 542plus 1MRS756342 Fig. 6.1.2.-12 Substation Relationship and Communication Settings tab A070232 38

1MRS756342 REF 542plus Enter the definitions for the following fields: * Substation Name: If the check box for the IED Name is not checked, define a substation name not longer than 15 characters. If the IED Name check box is checked to automate the IED Name generation, enter the substation name up to 3 characters, see Fig. 6.1.2.-13. Fig. 6.1.2.-13 Entering a substation name A070233 Fig. 6.1.2.-14 Entering a substation name for the automated IED name A070557 * Voltage Level Designation: Select the voltage level designation from a dropdown list. 39

REF 542plus 1MRS756342 Fig. 6.1.2.-15 Selecting the voltage level designation A070234 * Voltage Level Index: Select the voltage level index from a drop-down list. Fig. 6.1.2.-16 Selecting the voltage level index A070546 * Voltage Level Value: Depending on the voltage level selected, enter the voltage value. A tool tip appears to show the voltage value range applicable for the selected voltage level. 40

1MRS756342 REF 542plus Fig. 6.1.2.-17 Entering the voltage value A070235 * If the check box for IED Name is not checked, enter the Bay Designation up to 10 characters. If the IED Name check box is checked to automate the IED Name generation, enter the Bay Designation up to 3 characters, see Fig. 6.1.2.-18. Fig. 6.1.2.-18 Entering the bay designation A070236 41

REF 542plus 1MRS756342 Fig. 6.1.2.-19 Entering the bay designation for automated IED name A070558 * Enter the IED Designation up to 2 characters. If the IED Name check box is selected to automate the IED name generation, the IED Designation field is enabled. If the IED Name check box is not selected, the IED Designation field is disabled. Fig. 6.1.2.-20 Entering the IED Designation for automated IED name A070547 * If the IED Name check box is unchecked, IED Name field is enabled. Enter the IED Name up to 10 characters. 42

1MRS756342 REF 542plus Fig. 6.1.2.-21 Entering the IED name A070237 * If the IED Name check box is checked, IED Name fills in automatically the Substation Name, Voltage Level Designation, Voltage Level Index, Bay Designation, and IED Designation values. The Substation Name and Bay Designation values are replaced with the first 3 characters if their lengths are greater than 3. Fig. 6.1.2.-22 Automated IED name A070559 * Enter the IP addresses for the SNTP servers 1, 2, 3 and 4. This is used by the REF 542plus ETHERNET BOARD as communication parameters for communication with IEC61850 clients. 43

REF 542plus 1MRS756342 Fig. 6.1.2.-23 Entering the IP address A070238 * Select the DST Correction from the drop-down list. It ranges from 0.00 hour to 2.00 hour. If the user selects a value other than 0.00, then the Start of DST and End of DST group boxes are enabled. Fig. 6.1.2.-24 Selecting the DST correction A070239 * Select Week Day, Month, After Month Day, Hour, Minute and Second for both Start of DST and End of DST. 44

1MRS756342 REF 542plus Fig. 6.1.2.-25 Selecting the start and end of DST A070241 * Enter the Time zone correction factor, which varies from +13hours to - 12hours coordinated universal time. This setting only influences the local HMI time display and events. REF 542plus, in accordance with IEC 61850, sends data time-stamped according to UTC. Fig. 6.1.2.-26 Selecting the time zone correction A070242 * Submit the SNTP information by clicking OK. Click Cancel to cancel the submitting. * Click Generate ECM. The Save As dialog box opens in which the file name can be entered. 45

REF 542plus 1MRS756342 Fig. 6.1.2.-27 Saving dialog for ECM A090132 This starts the ECM file generation process, and after a successful creation of the ECM file, a popup window appears. Fig. 6.1.2.-28 ECM File generated A090134 * Click Import ECM to import the ECM file. This opens the Open File dialog box, in which the ECM file containing the ECM information to be imported can be selected. 46

1MRS756342 REF 542plus Fig. 6.1.2.-29 Open dialog for the ECM import A090136 Once the file is selected, it is parsed for the ECM information. Fields in the ECM information section are parsed according to the parsed information. * After a successful import of the ECM file, a popup window appears. Fig. 6.1.2.-30 ECM file imported A090138 15.Click the Sensor Configuration and Protection tab to view the sensor information and the protection functions configured in the imported REF 542plus Configuration RCA file. 47

REF 542plus 1MRS756342 Fig. 6.1.2.-31 Sensor Configuration and Protection tab A090140 16.Click the Measurement tab. It displays the measurement configuration in the imported REF 542plus Configuration file. Fig. 6.1.2.-32 Measurement tab A090142 Values in the Signal Designation, IEC 61850 Enabled and DS Allocation columns can be edited. When a box in the IEC 61850 Enabled column is selected or cleared, the corresponding DS Allocation column box is automatically selected or cleared. * By default, the IEC 61850 Enabled and DS Allocation columns are cleared for neut calculated. * Either the neut or neut calculated field has to be selected or cleared, both cannot be selected or cleared at the same time. 48

1MRS756342 REF 542plus * Reset All clears all check boxes. * Set All selects all check boxes. 17.Select the Primary Switches tab. It displays all the configured switching devices and the respective FUPLA object types in a table. Fig. 6.1.2.-33 Primary Switches tab A070244 With the IEC 61850 enabled, the designation and controllable columns can be edited. In case of the ICD file generation, the Designation column is hidden. By default, the columns IEC 61850 Enabled and Controllable are selected. The IEC 61850 Enabled column can be selected or cleared only for Switching Object 2-2. Selecting them results in enabling further fields for user entry, whereas clearing them results in the rest of the fields turning gray (cannot be edited) and the respective entry is not configured in the SCL file. 49

REF 542plus 1MRS756342 Fig. 6.1.2.-34 Primary Switches table A070245 * Enter the designation of up to 10 characters. Fig. 6.1.2.-35 Entering the designation A070246 * Select or clear the Controllable column to confirm whether the switch is controllable or not. Fig. 6.1.2.-36 Controllable option for primary switches A070247 18.Click the General I/O tab. The tab shows the FUPLA object reference, the Spa channel/data number parsed from the REF 542plus configuration tool RCA file in a table. 50

1MRS756342 REF 542plus Fig. 6.1.2.-37 General I/Os tab A070248 51

REF 542plus 1MRS756342 * The table can be filtered on the basis of the FUPLA object reference by using a drop-down list. Fig. 6.1.2.-38 General I/Os tab with Filter By A090144 * A Spa channel number can be searched for by using the search option. Fig. 6.1.2.-39 General I/Os tab with the Search option A090146 * Sort data by right-clicking on the LN Instance Number or LN Prefix column and selecting Ascending or Descending. Data can be sorted on the basis of LN Prefix or LN Instance Number. 52

1MRS756342 REF 542plus Fig. 6.1.2.-40 Sorting by LN Instance Number A090148 Fig. 6.1.2.-41 Sorting by LN Prefix A090150 * Click a row once to select the entire row. * Enter data for the corresponding FUPLA Object Reference by doubleclicking a row. The SCL tool pops up the GGIO Data window to fill the data. * By default, the IEC 61850 check box is selected. Fig. 6.1.2.-42 GGIO data window A090152 * Enter the signal designation of up to 20 characters. 53

REF 542plus 1MRS756342 Fig. 6.1.2.-43 Signal Designation A090154 * Enter the LN Prefix of up to four characters. * For LNName "XCBR," the LN Prefix is updated as per Designation value for the circuit breaker on the Primary Switches tab. * For LNName "XCBR," the LN Prefix is Read only. * For LNName "SIMG," the default LN Prefix is "SF6." * For LNName "GGIO" for the AI20mA sensors, the default LN Prefix is "GEN." Fig. 6.1.2.-44 LN Prefix A090156 * Select LN Name by using the drop-down list which is filled by considering the FUPLA object reference. The following options are available for different FUPLA Object References: * For a Binary Read/Switching Object 0-1 FUPLA object, GGIO, SIMG or XCBR LN Name can be selected. * For a 16-bit read or write, a Binary write, a Switching object 1-0, a Direct Read Write, a Switching object 1-1 or a General purpose sensor and the corresponding warnings, only the GGIO option can be selected. * For a Trafag or Density sensor and the corresponding warnings, only LN SIMG option can be selected. * For Coil supervision, only the XCBR option can be selected. Fig. 6.1.2.-45 LN Name A090158 54

1MRS756342 REF 542plus * Enter the LN Instance number between 1 and 255. * For the LNName "XCBR," the LN Instance Number is updated as per the SPA Channel value for the circuit breaker on the Primary Switches tab. It is read only for XCBR. Fig. 6.1.2.-46 LN Instance Number A090160 * Select DOI Name from the drop-down list which is filled considering the FUPLA object reference. The following options are available for different FUPLA Object References: * GGIO LNName: * For a Binary Read/Switching Object 0-1 FUPLA object, an Alm (Alarm), Ind (Indication) or SPSCO (Single Point Controllable Status Output) DOI can be selected. * For a 16-bit Read FUPLA object, an IntIn (Integer Status) or ISCSO (Integer Status Controllable Status Output) DOI can be selected. * For a 16-bit Write FUPLA object, only an ISCSO (Integer Status Controllable Status Output) DOI can be selected. * For a Binary Write, a Switching object 1-0, a Direct Read Write or a Switching object 1-1 FUPLA object, only an SPSCO (Single Point Controllable Status Output) DOI can be selected. * For a general purpose sensor, only an AnIn (Analog input) can be selected. For the corresponding warnings, an EEHealth (External Equipment Health), Ind (Indication) or Alm (Alarm) DOI can be selected. * SIMG LNName: * For a Trafag sensor FUPLA object, a Pres (Pressure) or a Tmp (Temperature) and PresAv (Average pressure) DOI can be selected. For the corresponding warnings, an EEHealth (External Equipment Health), InsAlm (Insulation gas critical (refill isolation medium)) or InsBlk (Insulation gas not safe (block device operation)) DOI can be selected. * For a Density sensor FUPLA object, a Pres (Pressure) or a PresAv (Average pressure) DOI can be selected. For the corresponding warnings, an EEHealth (External Equipment Health), InsAlm (Insulation gas critical (refill isolation medium)) or InsBlk (Insulation gas not safe (block device operation)) DOI can be selected. * For the Binary Read/Switching Object 0-1 FUPLA object, an InsAlm (Insulation gas critical (refill isolation medium)), InsBlk (Insulation gas not safe (block device operation)), InsTr (Insulation gas dangerous (trip for device isolation)), InsLevMax (Insulation gas level maximum) or InsLevMin (Insulation gas level Minimum) DOI can be selected. 55

REF 542plus 1MRS756342 * If "InsAlm" is selected as the DOI name for the Trafag or Density sensor, a new row under the InsAlm entry with the same entries as InsAlm except for the DOI name, that is, DenAlm (Isolation gas density alarm) conditional DO is added. If the InsAlm is not configured, DenAlm is also removed. * If "InsAlm" is selected as the DOI name for Binary Read/Switching Object 0-1, a new row under the InsAlm entry with the same entries as InsAlm except for the DOI Name, that is, either DenAlm (Isolation gas density alarm), PresAlm (Isolation gas pressure alarm) or TmpAlm (Isolation gas temperature alarm) conditional DO is added. By default, DenAlm is selected. If the InsAlm is not configured, the conditional DO is also removed. * XCBR LNName: * For an XCBR LN Name, a ClsColFlt or OpnColFlt DOI can be selected. Fig. 6.1.2.-47 DOI Name A090162 * Enter the DOI number of up to two digits. Fig. 6.1.2.-48 DOI Number A090164 * Select or clear the DS Allocation check box. When selected, the corresponding DOI entry (along with the LN class, LN instance number and LD) is included in the DS. When cleared, the DOI entry is not included in the DS. Fig. 6.1.2.-49 DS Allocation A090166 56

1MRS756342 REF 542plus * Submit the data by clicking OK in the GGIO data window for a particular FUPLA object. * Edit the data by double-clicking the selected row. 19.Click the Report Control Blocks tab displaying the information about the default report control blocks by parsing the Report Control Block.xml from the 61850 file pool. By default, the fourth and fifth client can be inserted in the SCL Import section with the context menu under the enabled report (New/Report Client). Fig. 6.1.2.-50 Report Control Blocks tab for the CID file type A090168 All the columns can be edited against each dataset. In case of the ICD file generation, the client table is not available. 57

REF 542plus 1MRS756342 Fig. 6.1.2.-51 Report Control Blocks tab for the ICD file type A090170 * The Buffer Enable column values can be edited. Fig. 6.1.2.-52 Report Control: Buffer Enable A090172 * A Buffer Time of up to three digits can be given. Fig. 6.1.2.-53 Report Control: Buffer Time A090174 * Select the maximum number of subscribing clients from the drop-down list. 58

1MRS756342 REF 542plus Fig. 6.1.2.-54 RptEnabled: Number of Subscribing Clients A090176 * Enter a Configuration Revision value of up to two digits. Fig. 6.1.2.-55 Report Control: Configuration Revision A090178 * Select Sequence Number Enable with the check box. Fig. 6.1.2.-56 OptFields: Sequence Number Enable A090180 * Select TimeStamp Enable with the check box. Fig. 6.1.2.-57 OptFields: TimeStamp Enable A090182 * Select DataSet Enable with the check box. Fig. 6.1.2.-58 OptFields: DataSet Enable A090184 59

REF 542plus 1MRS756342 * Select ReasonCode Enable with the check box. Fig. 6.1.2.-59 OptFields: ReasonCode Enable A090186 * Select the maximum DataRef Enable with the check box. Fig. 6.1.2.-60 OptFields: DataRef Enable A090188 * Select EntryID Enable with the check box. Fig. 6.1.2.-61 OptFields: EntryID Enable A090190 * Select ConfigRef Enable with the check box. Fig. 6.1.2.-62 OptFields: ConfigRef Enable A090192 To define the IP, IP Subnet and IP Gateway for the four clients under the communication section, a second table is provided with the default values. The columns can be edited. 60

1MRS756342 REF 542plus Fig. 6.1.2.-63 RCB Client Information Table A090194 * Enter a client IED name of up to seven characters in the second table. Fig. 6.1.2.-64 Client IED Name A090196 * Enter an IP address other than 0.0.0.0 or 255.255.255.255. Fig. 6.1.2.-65 Client IP address A090198 * Enter an IP Subnet address other than 0.0.0.0 or 255.255.255.255. Fig. 6.1.2.-66 Client IED IP Subnet A090200 * Enter an IP Gateway address other than 0.0.0.0 or 255.255.255.255. 61

REF 542plus 1MRS756342 Fig. 6.1.2.-67 Client IED IP Gateway A090202 20.Select CID as the file type to make the SCL tool to generate an ECM file also with the same name as the SCL fil (.cid) with the extension.ecm in the same directory. However, in case of ICD, only the SCL file (.icd) is generated. * Click Generate SCL & ECM. The SCL tool checks the mandatory events of the configured general I/Os and primary switches. If those events are not configured in the.rca file, the SCL tool pops up a window to inform about mandatory events and block any further processing of the SCL generation. This information can be saved as a text file or printed out. Fig. 6.1.2.-68 Missing events information A090204 * Click Yes or No when the SCL tool prompts to save the data that was entered in the GUI. 62

1MRS756342 REF 542plus Fig. 6.1.2.-69 Save GUI Data message a090206 * Click Yes to open one more popup to select a folder for the GUI data and to enter the file name. By default, the path for GUD is set as that of the RCA file path. Fig. 6.1.2.-70 Save GUI Data information dialog A090208 * Enter a file name of up to 16 characters. Fig. 6.1.2.-71 GUD file name A090210 * Click OK to save the data entered in the GUI in the "Test.GUD" file. This starts the SCL generation process and after the successful creation of the SCL file(s), displays a message for validation. 63

REF 542plus 1MRS756342 Fig. 6.1.2.-72 SCL File Generated and Validated message A090212 6.1.3. CID/ICD Import 1. Click the CID/ICD Import tab. The SCL file import section of the application opens. Fig. 6.1.3.-1 CID/ICD Import tab A090214 The Project Explorer on the left side displays the header node REF542plus. 2. Right-click the REF542plus node under "Project Explorer" to import an SCL file. 64

1MRS756342 REF 542plus Fig. 6.1.3.-2 Import SCL file A090216 3. Select Import SCL File to open a dialog to choose a file and import. Fig. 6.1.3.-3 Select SCL file A090218 4. Click Select SCL File to browse for the file. 65

REF 542plus 1MRS756342 Fig. 6.1.3.-4 SCL file dialog A070282 5. Select the file and click Open to import the file. Fig. 6.1.3.-5 Progress bar navigation for the SCL file import A070283 66

1MRS756342 REF 542plus After the SCL file has been imported, the SCL tool checks the mandatory events in the SCL file. If the events are not configured in the SCL file, the SCL tool pops up a window to inform about the mandatory events. The events can be corrected via a property window for particulars. The information can be saved as a text file or printed out. Fig. 6.1.3.-6 Missing even information A090220 Once the file is imported, the IED node is added as a child node under the REF542plus node in the tree structure in the project explorer. The IED has LD0 and LD1 as child nodes. Fig. 6.1.3.-7 Tree structure navigation A090222 6. Right-click LD0 and select Expand. 67

REF 542plus 1MRS756342 Fig. 6.1.3.-8 Expand tree node A070285 Fig. 6.1.3.-9 Expanded tree node A070286 7. Right-click LD1 and select Expand. All the LNs under LD1 are displayed. 68

1MRS756342 REF 542plus Fig. 6.1.3.-10 LN tree node navigation A070287 8. Expand an LN to view its DOIs. 69

REF 542plus 1MRS756342 Fig. 6.1.3.-11 Expanded LN tree node navigation A070288 9. Right-click any of the DOIs to view the available options for editting a DOI. 70

1MRS756342 REF 542plus Fig. 6.1.3.-12 DOIEditor tool option A070289 10.Select Properties to open the property window for the DOI. 71

REF 542plus 1MRS756342 Fig. 6.1.3.-13 DOI property bar navigation A070290 11.Right-click and select DOIEditor to open the DOI editor window to view or edit the DOI attributes. 72

1MRS756342 REF 542plus Fig. 6.1.3.-14 DOIEditor tool option A070291 73

REF 542plus 1MRS756342 Fig. 6.1.3.-15 DOI editor navigation A070292 12.Update the saddr of the DOI by using the properties grid. When changes are made in the properties, this reflects automatically in the DOI editor. 74

1MRS756342 REF 542plus Fig. 6.1.3.-16 Updating of saddress A090224 13.Select Delete from the shortcut menu to delete the DOI from the LN. The delete option is available only for the DOIs under the LNs of the GGIO type. 75

REF 542plus 1MRS756342 Fig. 6.1.3.-17 DOI deletion A070293 14.Click Yes to delete the DOI from the LN. 76

1MRS756342 REF 542plus Fig. 6.1.3.-18 Updated tree structure after the DOI deletion A070294 15.Right-click any LN of the GGIO type and select DOWizard to add a DOI to the LN. 77

REF 542plus 1MRS756342 Fig. 6.1.3.-19 DOWizard tool option A070295 16.Select the DOI name from the selection list and enter the DOI number. Fig. 6.1.3.-20 DOWizard A070296 The possible DOI names with the DOType and CDC are given in the following table. 78

1MRS756342 REF 542plus Serial No DOI Name DO Type CommonData- Class 1 Alm SPS SPS 2 AnIn MV_simple MV 3 Ind SPS SPS 4 IntIn INS_int INS 5 ISCSO INC_control_int INC 6 SPCSO SPC_control SPC 17.Enter the DOI number and click Add DOI to add the DOI to the LN. The newly added DOI is highlighted in the Project Explorer field. Fig. 6.1.3.-21 Added DOI navigation A070297 18.Right-click LD1 and select LNWizard to add an LN of the GGIO type to LD1. 79

REF 542plus 1MRS756342 Fig. 6.1.3.-22 LNWizard tool option A070298 80

1MRS756342 REF 542plus Fig. 6.1.3.-23 LNWizard navigation A070299 19.Enter the prefix and LN instant number. Fig. 6.1.3.-24 LNWizard: field navigation A070300 20.Click Add LN to add the LN to LD1. The LN "T1GGIO1" is added at the end of the tree structure. 81

REF 542plus 1MRS756342 Fig. 6.1.3.-25 Added LN navigation A070301 21.Expand LLN0 under LD0 to view the datasets and Report control blocks. 82

1MRS756342 REF 542plus Fig. 6.1.3.-26 Dataset and the Report control blocks navigation A070302 22.Right-click any LLN0 and select Add Dataset to add a dataset and its corresponding RCB node. The maximum allowed number of datasets is 6. 83

REF 542plus 1MRS756342 Fig. 6.1.3.-27 Add Dataset option A070303 23.Click StatUrgB to add the dataset. The dataset StatUrgB is added along with its corresponding RCB rcb_ab at the end. 84

1MRS756342 REF 542plus Fig. 6.1.3.-28 Added dataset navigation A070304 24.Right-click the dataset and select Delete to delete the dataset and its corresponding RCB. 85

REF 542plus 1MRS756342 Fig. 6.1.3.-29 Delete Dataset A070305 86

1MRS756342 REF 542plus Fig. 6.1.3.-30 Updated tree structure navigation after the DS deletion A070306 25.Right-click any dataset and select DataSet Editor to view the list of FCDAs under that particular dataset. 87

REF 542plus 1MRS756342 Fig. 6.1.3.-31 DataSet Editor tool option A070307 88

1MRS756342 REF 542plus Fig. 6.1.3.-32 DataSet Editor navigation A070308 26.Expand any LN. Drag and drop any DOI in it to the DataSet Editor. The FCDAs corresponding to the DOI are added at the end of the DataSet Editor table. 89

REF 542plus 1MRS756342 Fig. 6.1.3.-33 FCDAs added at the end of the DataSet Editor A070309 27.Delete an entry from the DataSet editor by right-clicking a row and selecting Delete. Fig. 6.1.3.-34 Delete FCDA entries from dataset A090226 90

1MRS756342 REF 542plus Fig. 6.1.3.-35 Updated DataSet editor after deleting the selected FCDA entry A090228 28.Expand an RCB. 29.Expand the ReportEnabled node under the RCB. 30.Right-click to add Report Client. 91

REF 542plus 1MRS756342 Fig. 6.1.3.-36 Adding an RCB client A070310 If the newly added Report Client is the fifth client, a dialog box is displayed with the IP details of Client 5. Fig. 6.1.3.-37 RCB client information A070311 31.Click OK to save the IP addresses entered for the Client 5 node. The Client is then added as shown in Fig. 6.1.3.-38. 92

1MRS756342 REF 542plus Fig. 6.1.3.-38 Updated tree structure after the RCB client addition A070312 32.Set the properties for the added Client using the property field. The IED Name property consists of IED names. 93

REF 542plus 1MRS756342 Fig. 6.1.3.-39 RCB Client properties navigation A070560 33.Right-click the root node "REF542plus" and select Export SCL File to Hard Disk to open a window to export the modified SCL file to the hard disk. Fig. 6.1.3.-40 SCL file export option navigation A070313 94

1MRS756342 REF 542plus Fig. 6.1.3.-41 SCL file export window navigation A070314 34.Click Write to browse for the file name or type the file name to save the SCL file. 95

REF 542plus 1MRS756342 Fig. 6.1.3.-42 Save file dialog for exporting the SCL file A070315 checks the mandatory events in the SCL file. If the events are not configured in the SCL file, the SCL tool pops up a dialog to inform about the mandatory events. The events can be corrected via the property window for particulars and export again. The information can be saved as a text file or printed out. Fig. 6.1.3.-43 Event checking for exporting file A090320 A dialog is displayed once the file is exported successfully. 96

1MRS756342 REF 542plus Fig. 6.1.3.-44 Progress bar navigation for the SCL file export A090232 97

REF 542plus 1MRS756342 6.1.4. SCD import 1. Click the "SCD Import" tab. The SCD file import section of the application opens. An SCD file which consists of one or more REF 542plus IEDs can be imported. A CID file can be created for each IED. Fig. 6.1.4.-1 SCD import tab A090234 2. Right-click the SCD node under Project Explorer on the left. Fig. 6.1.4.-2 Import SCD file A090236 3. Select Import SCD File to open a dialog for choosing the file and importing. 98

1MRS756342 REF 542plus Fig. 6.1.4.-3 Select SCD File A090238 4. Click Select SCD File to browse for the file. Fig. 6.1.4.-4 SCD File dialog A090240 5. Select the file and click Open to import the file. 99

REF 542plus 1MRS756342 Fig. 6.1.4.-5 Progress bar navigation for the SCD File import A090242 Once the file is imported, the IED nodes are added as child nodes to the SCD header node and the SCD header text is updated with the substation name. The IED nodes have LD0 and LD1 as child nodes. Fig. 6.1.4.-6 Tree structure navigation A090244 6. Right-click LD0 and select Expand. Fig 6.1.4.-7 displays all the LNs under LD0. 100

1MRS756342 REF 542plus Fig. 6.1.4.-7 Expand tree node A090246 Fig. 6.1.4.-8 Expanded tree node A090248 7. Right-click LD1 to expand and display all the LNs under LD1. 101

REF 542plus 1MRS756342 Fig. 6.1.4.-9 LN tree node navigation A090250 8. Expand any of the LNs to view its DOIs. 102

1MRS756342 REF 542plus Fig. 6.1.4.-10 Expanded LN tree node navigation A090252 9. Right-click the selected IED node and select Export CID File to Hard Disk to open a window to export thecid file to hard disk. Fig. 6.1.4.-11 CID File export option navigation A090254 103

REF 542plus 1MRS756342 Fig. 6.1.4.-12 CID File export window navigation A090256 10.Click Write to browse for file name or type the file name to save the CID file. The IED name is the default file name. Fig. 6.1.4.-13 Save File dialog for exporting the SCL file A090258 11.A popup is displayed once the file is exported successfully. 104

1MRS756342 REF 542plus Fig. 6.1.4.-14 Progress bar navigation for CID File export A090260 6.1.5. FTP Download/Upload 1. Click the FTP Download/Upload tab. By default, The Download option is selected. By default, the SCL folder is the same as the folder where the REF 542plus SCL Tool-generated CID files are stored. 2. Browse the folder where the CID and ECM files are by clicking Browse. Names of all the CID and ECM files in the folder come under the Device Reference (File Name) list box. 3. Select the CID or ECM file for download. After the required CID file is selected, the IP addresses 1 and 2 appear automatically in the IP address drop-down box. 105

REF 542plus 1MRS756342 Fig. 6.1.5.-1 FTP Download or Upload tab A070317 4. Select an IP address (primary or secondary IP address) for the CID file. After selecting the ECM file, the IP text box appears. 106

1MRS756342 REF 542plus Fig. 6.1.5.-2 IP textbox for the ECM file A090262 5. Enter the IP address of the REF 542plus EB. 6. Enter the user name and password (abb for REF 542plus EB). 107

REF 542plus 1MRS756342 Fig. 6.1.5.-3 Filling user ID and password for the FTP download A090264 7. Click Download to initiate the FTP connectivity and start the CID file transfer from the hard disk to the REF 542plus EB. A notification appears after a successful file transfer to indicate that the is resetting the REF 542plus EB to recognize the newly loaded file. Fig. 6.1.5.-4 Notification after the download A070319 8. Click Upload. 108

1MRS756342 REF 542plus 9. Click Browse to select the destination folder for the uploaded file in the hard disk. 10.Select the type of file to upload from the IED. The options "CID," "ECM" and "Both" are available in the File Type selection list. By default, "CID" is selected. Fig. 6.1.5.-5 File type to upload A090266 11.Enter the IP address of the REF 542plus EB. 12.Enter the user name and password (abb for REF 542plus EB). A notification appears after a successful file transfer into the selected destination folder. 109

REF 542plus 1MRS756342 Fig. 6.1.5.-6 Notification after the upload A070320 13.Click OK. The REF542plus.cid file is in the destination folder. Fig. 6.1.5.-7 Uploaded CID File navigation A070321 6.1.6. Firmware download 1. Click the Firmware Download tab. The Ethernet Firmware File (*.bin) can be downloaded to a given range of IP addresses. 110

1MRS756342 REF 542plus Fig. 6.1.6.-1 Firmware download A090268 2. Select the file by using Browse. 3. Enter the lower and upper limit IP addresses. 4. Enter the FTP user ID and password to download the file. 5. Click Download after filling in all the appropriate information. The Ethernet firmware file is downloaded on the given range of the IED Ethernet board. 6.1.7. Graphical FTP 1. Click the FTP Download/Upload tab. 2. Click View File in IED for the Graphical FTP window. 111

REF 542plus 1MRS756342 Fig. 6.1.7.-1 Access to Graphical FTP A090270 Fig. 6.1.7.-2 Graphical FTP A090272 3. Enter the IP address of the IED, user name and password. 112

1MRS756342 REF 542plus 4. Click List File Details to view the files in the IED. Fig. 6.1.7.-3 Graphical FTP progress bar A090274 5. See the tree view of the files available in the IED. 6.1.8. TELNET interface 1. On the Tools menu, click TELNET. Fig. 6.1.8.-1 TELNET A090276 The TELNET interface window appears. By default, the value of Port is 23. 113

REF 542plus 1MRS756342 Fig. 6.1.8.-2 TELNET interface A090278 2. Type the IP address for the host and click Connect. Fig. 6.1.8.-3 TELNET interface connect A090280 3. Type the user name in the Command text box and click Execute. 114

1MRS756342 REF 542plus Fig. 6.1.8.-4 TELNET interface user name A090282 4. Type the password in the Command text box and click Execute. Fig. 6.1.8.-5 TELNET interface password A090284 5. Type in the TELNET command and click Execute. Status/Result shows in the window. 115

REF 542plus 1MRS756342 Fig. 6.1.8.-6 TELNET command execution A090286 6.2. SCL core component The core component interacts with the two XML file pools which are generated to construct the REF 542plus SCL file(s) as per user configuration. The file pools are the User data XML file pool with the REF542plusconfiguration.xml file, and the 61850 XML file pool. A brief explanation is given to help understand where exactly the user information is used in the SCL files. The user entries in the GUI are compared to the final form of the SCL files. 116

1MRS756342 REF 542plus * In the SCL file s header section, the "id" attribute shows the name of the used rca and gud files, "version" attribute shows the version number and "toolid" attribute displays the current version of. Fig. 6.2.-1 Header ID navigation A070322 * Substation section (applicable to CID files only): The Substation Relationship and Time Settings tab along with the relevant part of the SCL file. Fig. 6.2.-2 Substation relationship GUI information update A070323 As shown in Fig. 6.2.-2, the following entries are updated: * Substation name * Voltage Level Designation * Voltage Level Index * Voltage in kv * Bay Designation * IED Designation * IED Name * Communication section (applicable to CID files only): The SNTP IP addresses section along with the relevant parts of the SCL file, see Fig. 6.2.-3. 117

REF 542plus 1MRS756342 Fig. 6.2.-3 SNTP server IP information update A070324 As shown in Fig. 6.2.-3, the following entries are updated for the Uplink communication in the SCL file: * SNTP Server -1 IP address * SNTP Server -2 IP address * SNTP Server -3 IP address * SNTP Server -4 IP address * Time settings section The time settings section along with the relevant part of the SCL file are shown in Fig. 6.2.-4. 118

1MRS756342 REF 542plus Fig. 6.2.-4 Time settings information update A070325 As shown in Fig. 6.2.-4, the following entries are updated for the Uplink communication in the SCL file: * DST Correction * Time Zone Correction * StartDSTWeekDay * StartDSTMonthDay * StartDSTMonth * StartDSTHour * StartDSTMinute * StartDSTSecond * EndDSTWeekDay * EndDSTMonthDay * EndDSTMonth 119

REF 542plus 1MRS756342 * EndDSTHour * EndDSTMinute * EndDSTSecond * Measurement section The measurement data in GUI along with the relevant part of the SCL file are shown in Fig. 6.2.-5. Fig. 6.2.-5 Measurement configuration information update A090288 As shown in Fig. 6.2.-5, the LN Instance number 1 in the GUI results in one instance of LN MMXU. The LN Prefix UI in the GUI results in the prefix of LN MMXU. The DOI Names in the GUI results in the DOI of LN MMXU, The saddr fields of DAI updated according to SPA Channel in the GUI are as shown in 6.2.-6 120

1MRS756342 REF 542plus Fig. 6.2.-6 Measurement configuration saddr information update A090290 * Primary Switch section An entry for a circuit breaker CB with a FUPLA object Switching object 2-2, with control option Enabled and SPA channel number 9 result in the following if the IEC 61850 enable option is Enabled: The primary switches tab along with the relevant part of the SCL file are shown in Fig. 6.2.-7. Fig. 6.2.-7 Primary switches information update A070328 121

REF 542plus 1MRS756342 The explanation for the primary switches part is as follows: * 1 LN CILO with the prefix CB, instance number 9 and description Switching object 2-2 CircuitBreaker CB1. Fields updated with 9, apart from the LN instance, are SPA channel number fields in the saddr attributes of a DAI. SPA on-event and off-event codes are directly parsed from the RE542plusConfiguration.xml file and updated in LN CILO. Fig. 6.2.-8 Channel number update for CILO A070329 * 1 LN CSWI with the prefix CB, instance number 9 and description Switching object 2-2 CircuitBreaker CB1. Fields updated with 9, apart from the LN instance, are SPA channel number fields in the saddr attributes of a DAI. saddr for Pos contains both the control and status part. Fig. 6.2.-9 Channel number update for CSWI A070330 * 1 LN XCBR with the prefix CB, instance number 9 and description Switching object 2-2 CircuitBreaker CB1. Besides the SPA channel numbers updated with 9 as in the earlier LNs, the operational capability SPA data number is updated in the CB operational capability DOI/DAI/sAddr. 122

1MRS756342 REF 542plus Fig. 6.2.-10 Channel number update for XCBR A070331 An entry for a circuit breaker CB with the FUPLA object Switching object 2-2 and with the control option Not Enabled and SPA channel number 9 results in the following if the IEC 61850 enable option is Enabled: The primary switches tab along with the relevant part of the SCL file are shown in Fig. 6.2.-11. Fig. 6.2.-11 LN creation for non-controllable primary switches A070332 123

REF 542plus 1MRS756342 The explanation for the primary switches part is as follows: * 1 LN CSWI with the prefix CB, instance number 9 and description Switching object 2-2 CircuitBreaker CB1. Fields updated with 9, apart from the LN instance, are SPA channel number fields in the saddr attributes of a DAI. saddr for Pos contains only the status part. Fig. 6.2.-12 Channel number update for CSWI A070333 * 1 LN XCBR with prefix CB, instance number 9 and description Switching object 2-2 CircuitBreaker CB1. Besides the SPA channel numbers updated with 9 as in earlier LNs, the operational capability SPA data number is updated in the CB operational capability DOI/DAI/sAddr. 124

1MRS756342 REF 542plus Fig. 6.2.-13 Channel number update for XCBR A070334 If coil supervision is configured for the circuit breaker on the General I/Os tab page, the respective DOIs added under XCBR LN are as shown in 6.2.-14. 125

REF 542plus 1MRS756342 Fig. 6.2.-14 Coil supervision update for XCBR A090292 * Protection section The protection functions along with the relevant part of the SCL file are shown in Fig. 6.2.-15. 126

1MRS756342 REF 542plus Fig. 6.2.-15 LN creation for the protection functions A070335 As shown above, the following data are updated: * Depending on the SPA channel parsed from the REF542plusConfiguration. xml file, the corresponding protection LNs are included. For example, "Inrush Harmonic" has a SPA channel number 50, and hence two LNs of the PIOC class and GGIO class with the instance number 50 are included. * General I/Os section The general status and control sheet along with the relevant part of the SCL file are shown in the figure below. 127

REF 542plus 1MRS756342 Fig. 6.2.-16 LN creation for GGIO A070337 As shown above, the following data are updated: * LN prefix, instance number and InClass data from the GUI into the LN GGIO * The FUPLA object name is updated in the DAI description field * The SPA data number in the saddr attribute of the DOI/DAI * The signal designation in the DAI Val attribute * The combined DOI name and number as the DOI name attribute * The Data set-enabled results in the addition of the DOI in the dataset * Combined DOIs in the general status and control section The DOIs configured for LNs in the general status and control section are combined in case of SPCSO and ISCSO DO types. Two FUPLA object references are combined to form a DOI in the LN. The two FUPLA objects with the following combinations must have the same LN prefix, LN instance number and DOI number for forming a combined DOI: 128

1MRS756342 REF 542plus DO Type First FUPLA Object Reference Second FUPLA Object Reference SPCSO Binary Read Binary Write SPCSO Binary Write Binary Read SPCSO Binary Write Switching Object 0-1 SPCSO Binary Read Switching Object 1-0 SPCSO Switching Object 0-1 Switching Object 1-0 SPCSO Switching Object 1-0 Switching Object 0-1 ISCSO 16 Bit Read 16 Bit Write ISCSO 16 Bit Write 16 Bit Read An example of combined object is shown in Fig. 6.2.-17: Fig. 6.2.-17 DOI creation for GGIO LN A070338 Here the SPCSO Binary Write Binary Read FUPLA object references are combined to form one DOI under the LN. * Report control blocks section The report control blocks along with the relevant parts of the SCL file are shown in Fig. 6.2.-18, Fig. 6.2.-19 and Fig. 6.2.-20. 129

REF 542plus 1MRS756342 Fig. 6.2.-18 Report control creation A070339 130

1MRS756342 REF 542plus Fig. 6.2.-19 Properties update for RCB A070340 Fig. 6.2.-20 Properties for RCB A070341 131

REF 542plus 1MRS756342 As shown above, the following data are updated under each report control block: * Buffer enable * Buffer time * Maximum number of subscribing clients * Configuration revision * Sequence enable * Time stamp enable * Dataset enable * Reason code enable * DataRef enable * Entry ID enable * ConfigRef enable The data in the second table are used to update the Report Control Blocks tab as shown in Fig. 6.2.-21. Fig. 6.2.-21 RCB client update A070342 As shown above, the following information is updated under each client: * IED Name * IP Address 132

1MRS756342 REF 542plus * IP Subnet * IP Gateway * In the Import section of the SCL tool, the addition of the fifth client under an RCB client list results in a Client node creation. The entered IP addresses are updated in the node as shown in Fig. 6.2.-22. Fig. 6.2.-22 RCB client IP addresses update A070343 * Additional miscellaneous information in the SCL file The device reference as entered in the GUI in the Files and Folders tab is updated in the REF 542plus LDevice node of the SCL file as the value of its description attribute, see Fig. 6.2.-23. 133

REF 542plus 1MRS756342 Fig. 6.2.-23 Device reference update A070344 The revision information of the and the configuration file information and version are updated as the value content of the configrev element under the REF 542plus LLN0 node, see Fig. 6.2.-24. 134

1MRS756342 REF 542plus Fig. 6.2.-24 version information A070345 * SLD Information Addition The SLD information derived by parsing the SVG file is added to Bay Node in the SCL (ICD/ CID) file. The SVG file data along with the SLD information in the SCL file are shown below: * Symbol Information: Symbol type, subtype and direction are derived from the nameid field in the SVG file and placed in the SCL file as shown below. The nameid is used to get the above information from the SymbolsLibrary.xml file. Coordinates are derived from the transform attribute. These coordinates are scaled by 3 and snapped to the grid for a better viewing in COM600 SLD Editor. The Terminal information is derived from the intersection points between Symbols and Lines. Fig. 6.2.-25 Symbol information in the SCL file A070562 * Text Information: Text to be displayed and the coordinates are derived for an Annotation as shown in Fig. 6.2.-26. Here, too, the coordinates are scaled and then snapped to grid for a better viewing in COM600 SLD Editor. 135

REF 542plus 1MRS756342 Fig. 6.2.-26 Annotation information in the SCL file. A070563 * ConnectivityNode Information: ConnectivityNode s coordinates are determined from the intersection points and then added to the SCL file as shown in Fig. 6.2.-27. Fig. 6.2.-27 ConnectivityNode information in the SCL file A070564 6.3. ECM core component A brief description is given to help understand where the user information is used in the ECM files. The user entries in the GUI are compared to the final form of the ECM files. * In the ECM file's Header section, the FileId attribute shows the file type identifier, FileVersion attribute identifies the file version. Fig. 6.3.-1 Header information of the ECM file A090294 * The Description section shows the substation information. 136

1MRS756342 REF 542plus Fig. 6.3.-2 Description field of the ECM file A090296 * The General section indicates the active application protocols. Fig. 6.3.-3 General section (Protocols) information of the ECM file A090298 * The MODTCP section shows the MODBUS-TCP information. Fig. 6.3.-4 MODBUS-TCP section of the ECM file A090300 The following information is available under the MODTCP section: 137

REF 542plus 1MRS756342 * Version attribute indicates the MODBUS/TCP section version * AccessModuleEnabled attribute indicates if the access to the Modbus server is restricted to the listed client address. * AuthorizedClientAddress attribute indicates the authorized clients' IP addresses * PriorityClientAddresses attribute indicates the high-priority client IP addresses * PriorityClientConnectMax attribute indicates the maximum number of simultaneous connections for the client * NotPriorityClientConnectMax attribute indicates the number on available non-priority client connections * The SNTP section shows the SNTP data information. Fig. 6.3.-5 SNTP section in the ECM file A090302 The following information is available under the SNTP section: * Enabled attribute indicates if the SNTP client is enabled * Version attribute indicates the SNTP section version * SntpMode attribute indicates the SNTP client interrogation mode * TimeZoneCorrection attribute indicates the value of the time zone correction in seconds * DstCorrection attribute indicates the value of the daylight-saving time correction in seconds * StartDSTwDay attribute indicates the starting DST day of the week (Sunday... Saturday) * StartDSTrule attribute indicates the starting DST week number of the month (First, Second...Last) * StartDSTmonth attribute indicates the starting DST month (January... December) * StartDSThour attribute indicates the starting DST hour of the day (00...23) * StartDSTmin attribute indicates the starting DST minute of the day (0...59) * StartDSTsec attribute indicates the starting DST second of the day (0...59) * EndDSTwDay attribute indicates the ending DST day of the week (Sunday... Saturday) 138

1MRS756342 REF 542plus * EndDSTrule attribute indicates the ending week number of the month (First... Last) * EndDSTmonth attribute indicates the ending DST month (January... December) * EndDSThour attribute indicates the ending DST hour of the day (00...23) * EndDSTmin attribute indicates the ending DST minute of the day (00...59) * EndDSTsec attribute indicates the ending DST second of the day (00...59) * ServerAddress attributes indicate the SNTP Time Server IP address * The HTTP section indicates the web server protocol information, the Version attribute indicates the HTTP section version. Fig. 6.3.-6 HTTP section in the ECM file A090304 * The SPA TCP section shows the SPATCP information. Fig. 6.3.-7 SPA TCP section in the ECM file A090306 The following information is available under the SNTP section: * Enabled attribute indicates if the SPA TCP server is enabled * Version attribute indicates the SPA TCP section version * AccessModuleEnabled attribute indicates if access to the SPA TCP server is restricted to the listed client addresses * AuthorizedClientAddress indicates the SPA TCP client IP address * The Security section shows the user information 139

REF 542plus 1MRS756342 Fig. 6.3.-8 Security section in the ECM file A090308 The following information is available under the SNTP section. * Enabled attribute indicates if Security is enabled * Version attribute indicates the Security section version * UserName attribute indicates the user name * UserPassword attribute indicates the user password * ServicePassword attribute indicates the service password 140

1MRS756342 REF 542plus 7. error and exception handling 7.1. Missing files checks for the files that are required for the SCL generation in their respective folders. If the file is not found, an appropriate message is displayed. The following folders are checked by the : * 61850 file pool If a 61850 file pool file is missing, an exception message is shown by the SCL Tool. Fig. 7.1.-1 shows the displayed error message when detects that the folder is missing the Protection.xml file. Fig. 7.1.-1 Missing file information in the 61850 file pool A070346 * SCL schema file pool If an SCL schema file pool file is missing, an exception message is shown by. Fig. 7.1.-2 shows the error message displayed when the detects that the folder is missing the CommonSA.xsd file. Fig. 7.1.-2 Missing file information in the SCL schema file pool A070347 141

REF 542plus 1MRS756342 7.2. Configuration Tool RCA file The following messages are displayed when the.rca file is not configured properly: * The detects if the communication board is configured as ETHERNET in the configuration tool RCA file. If it is not configured, the following message is displayed (see Fig. 7.2.-1). Fig. 7.2.-1 Communication board error in the RCA file A070348 * The detects if the imported configuration file is not well formed. If the file does not adhere to the standards, the tool displays a message with the error type as shown in Fig. 7.2.-2. Fig. 7.2.-2 RCA file format error A070349 * The SCL tool detects if the imported configuration file does not have protocol information. The tool displays a message with the error type. Fig. 7.2.-3 Protocol information missing A090310 142

1MRS756342 REF 542plus 7.3. GUI Validations 7.3.1. SCL Generation * An error message is displayed if one of the fields in the Files and Folders tab is not filled. For example, if the user selects another tab in the SCL Generation section without filling in the device reference, an error message is displayed as shown in Fig. 7.3.1.-1. Fig. 7.3.1.-1 Device reference error A090312 * An error message is displayed when an improper SVG file for loading SLD information is imported. For example, if an SVG file without the nameid Information for a symbol is imported, an error message is displayed as shown in Fig. 7.3.1.-2. Fig. 7.3.1.-2 Invalid SVG file import error A090314 * If a voltage level designation (for example, level B) is selected and a correct voltage level value (greater than 420kV) according to the designation is not filled in in the Substation and Communication tab, an error message is displayed as shown in Fig. 7.3.1.-3. Fig. 7.3.1.-3 Voltage level value error A070351 * If the substation name is typed with a numeric value in the Substation and Communication tab, an error message is displayed as shown in Fig. 7.3.1.-4. 143

REF 542plus 1MRS756342 Fig. 7.3.1.-4 Substation name error A090316 7.3.2. ECM generation * If an ECM file where the protocol information is different from the configuration file is imported, an error message is displayed. Fig. 7.3.2.-1 Protocol type error A090318 * If an invalid ECM file (for example, the IP address not in the correct format or some information is wrong) is imported, an error message is displayed. Fig. 7.3.2.-2 Validation error A090320 * If an IP address is moved in the MODBUS section from the Authorized IP list to the Priority pool when the NotPriorityClientConnectMax value equals zero, a warning message is displayed. 144

1MRS756342 REF 542plus Fig. 7.3.2.-3 IP address moving error A090322 * If an IP address of "0.0.0.0" or "255.255.255.255" is given in the Modbus, SPA TCP or SNTP sections, a warning message is displayed. Fig. 7.3.2.-4 IP address error A090324 * If information like user name or user password that is less than six characters is typed in the security section, an error message is displayed. Fig. 7.3.2.-5 Security information error A090326 * If a form is submitted in the SNTP section without the SNTP IP being filled in, an error message is displayed. Fig. 7.3.2.-6 SNTP form validation error A090328 * If in the Substation and Communication Settings tab the SPA TCP is not enabled and an ECM or SCL file is generated, an information message is displayed. 145

REF 542plus 1MRS756342 Fig. 7.3.2.-7 Parameter reading and writing validation error A090330 * If in the Substation and Communication Settings tab SNTP is not configured and an SCL file is generated, an error message is displayed. Fig. 7.3.2.-8 SNTP server validation error A090332 * If in the Substation and Communication Settings tab none of the enabling fields is filled in (for example, substation name) and an SCL file is generated, an error message is displayed. Fig. 7.3.2.-9 Substation name error A090334 * If in the Primary Switches tab none of the enabling fields is filled in (for example, designation) and an SCL file is generated, an error message is displayed. Fig. 7.3.2.-10 Primary switches designation error A090336 146

1MRS756342 REF 542plus * If in the Primary Switches tab IEC61850 Enable is cleared for circuit breaker when coil supervision has been configured in the General I/Os tab, an information message is displayed. Fig. 7.3.2.-11 Circuit breaker information message A090338 * In the General I/Os tab, values can only be typed for LNGGIO Instance Number or DOI Number, otherwise an error message is displayed. Fig. 7.3.2.-12 Validation message for Instance Number and DOI Number A090340 * In the General I/Os tab, the LNGGIO prefix can be started with alphabets only, otherwise an error message is displayed. Fig. 7.3.2.-13 Validation message for GGIO prefix A090342 * If in the General I/Os tab no other fields (for example, LN Name) than Prefix is filled in and the form is submitted, an error message is displayed. 147

REF 542plus 1MRS756342 Fig. 7.3.2.-14 Error message for LN Name A090344 * If in the General I/Os tab none of the Enabled fields is filled (for example, Signal Designation) and an SCL file is generated, an error message is displayed. Fig. 7.3.2.-15 Validation for the Enabled field A090346 * In the General I/Os tab, only SPCSO- and ISCSO-type of duplicate entries for DOI can be entered. If the same data are entered for LN Prefix, LN Instance Number, DOI Type and DOI Number and SCL Generate is clicked, an error message is displayed. Fig. 7.3.2.-16 Validation for identical information for GGIO A090348 * If in the General I/Os tab SPCSO/ISCSO is selected for the Read FUPLA object and there is no corresponding Write FUPLA object, an error message notifies that the possible DO Type for the FUPLA Reference object is other than SPCSO/ ISCSO. 148

1MRS756342 REF 542plus Fig. 7.3.2.-17 Validation for the DOI name A090350 * If in the General I/Os tab the coil supervision is already configured but it is reconfigured, an information message is displayed. Fig. 7.3.2.-18 Validation for coil supervision DOIs A090352 * In the Report Control Blocks tab only numbers can be typed in the Buffer Time and Configuration Revision fields. Otherwise, an error message is displayed. Fig. 7.3.2.-19 Validation for the RCB properties A090354 * If in the Report Control Blocks tab a wrong IP/IP Subnet/IP Gateway address is typed, an error message is displayed. Fig. 7.3.2.-20 Validation for the IP address A090356 149

REF 542plus 1MRS756342 * If in the Report Control Blocks tab none of the Enabled fields (for example, Buffer Time) is filled in and the SCL file is generated, an error message is displayed. Fig. 7.3.2.-21 Error message for Buffer Time A090358 * The FCDA entries are restricted based on the DOI entries. If the DOI entries reach a maximum of 250, the adding of FCDAs is stopped. If there still are any FCDAs left after the limit has been reached, they are collected and added to the next dataset element StatNrmIB and so on. A new dataset, such as StatNrmIC, is added if B also overflows. The maximum number of datasets for the Protection events is six. In case of a dataset overflow, a notification is displayed. Fig. 7.3.2.-22 Dataset overflow notification A090360 * If an error occurs due to invalid data while adding the SLD information during the generation of the SCL (IDC/CID) file, an error message is displayed. Fig. 7.3.2.-23 SLD addition error message A090362 * If in the General I/OsUI page the DS allocation is changed but the Configuration Revision of RCB "rcb_a" corresponding to the StatUrg dataset is not changed, prompts to change Configuration Revision if required when the SCL file is generated. Clicking Yes takes directly to the desired field in the RCB section of the GUI, and clicking No continues the SCL Generation process. 150

1MRS756342 REF 542plus Fig. 7.3.2.-24 Configuration revision change information A090364 * If in the RCB client the Client IED name is typed as "Dummy," an error message is displayed. Fig. 7.3.2.-25 Client IED name validation A090366 * If in the General I/Os tab two same DOIs (for example, Alm, Ind) are configured for one LN where one DOI is configured with the DOI number but the second DOI is not configured with the number and Generate SCL & ECM is clicked, an error message is displayed. Fig. 7.3.2.-26 DOI number validation A090368 * In the General I/Os tab only ISO646 string characters can be typed in the Signal Designation field. Otherwise, an error message is displayed. Fig. 7.3.2.-27 Signal Designation character validation A090370 * Clicking "details" displays the table for the ISO646 string. 151

REF 542plus 1MRS756342 Fig. 7.3.2.-28 ISO646 characters table A090372 * If in the General I/Os tab the same DOI is reconfigured for the same LN for SIMG LN Name, an information message is displayed. Fig. 7.3.2.-29 DOI validation message A090374 * If in the General I/Os tab the AI20mA sensor is configured without a mandatory DO, an error message is displayed and focus is set on the mandatory DOI row. 152

1MRS756342 REF 542plus Fig. 7.3.2.-30 Mandatory DOI validation A090376 * If in the General I/Os tab two different type of FUPLA objects are configured with the same LN prefix, LN name and LN instance number, an error message is displayed. Fig. 7.3.2.-31 LN generation validation A090378 * In the General I/Os tab only alphanumeric characters can be typed in for the LN prefix. Otherwise, an error message is displayed. Fig. 7.3.2.-32 LN prefix character validation A090380 7.3.3. CID/ICD import * If in LN Wizard an LN is added and its prefix does not start with an alphabet, an error message shown in Fig. 7.3.3.-1 is displayed. Fig. 7.3.3.-1 Validation for LNGGIO prefix A070572 153

REF 542plus 1MRS756342 * If in the Dataset editor the addition of DOI results in an overflow, a notification as shown in Fig. 7.3.3.-2 is displayed. Fig. 7.3.3.-2 DataSet overflow notification A070428 * If any property of an IED node of an ICD file is changed in the property grid, an error message as shown in Fig. 7.3.3.-3 is displayed. Fig. 7.3.3.-3 Validation for IED properties A070429 * If an IP address is changed to either 0.0.0.0 or 255.255.255.255 in the property grid, a warning message as shown in Fig. 7.3.3.-4 is displayed. Fig. 7.3.3.-4 Validation for IP address A070430 * If in the property field another IED Name is typed for the RCB client than in the available list, an error message shown in Fig. 7.3.3.-5 is displayed. 154

1MRS756342 REF 542plus Fig. 7.3.3.-5 Validation for client IED name A070573 * If another SCL file is imported over the previous file, a warning message is displayed. Fig. 7.3.3.-6 SCL file import notification A090382 7.3.4. SCD import * If another SCD file is imported over the previous file, a warning message is displayed. Fig. 7.3.4.-1 SCD file import warning A090384 * If the same IED node is exported again, an information message is displayed. Fig. 7.3.4.-2 SCD file export notification A090386 155

REF 542plus 1MRS756342 7.3.5. FTP download or upload * If the FTP connection is not established in the FTP download or upload section, an error message as shown in Fig. 7.3.5.-1 is displayed. Fig. 7.3.5.-1 FTP connection not established A070431 * If the FTP connection is not able to connect in the FTP download or upload section, an error message is shown. Fig. 7.3.5.-2 FTP connection error A090388 7.3.6. Graphical FTP * If an FTP cpnnection cannot be formed in the Graphical FTP section, an error message is displayed. Fig. 7.3.6.-1 Connection error A090390 156

1MRS756342 REF 542plus 8. Terminology Term Configuration Tool Data Set Ethernet Firmware Report Control Block saddr SPA Substation Configuration description Language Description Software program to configure the REF 542plus. This program runs on a PC. The data set is the content basis for reporting and logging. The data set contains references to the data and data attribute values. Physical communication network to transfer Internet data of the REF 542plus to the PC and back. The base software programs stored inside the REF 542plus. Among them, there are the FUPLA file interpreter and the protection functions programs. The report control block controls the reporting process for event data as they occur. The reporting process continues as long as the communication is available. Short Address InformationThe saddr attribute allows the allocation of a short address to DO attributes. Short addresses can be used within the communication to be more efficient either in the communication, or in the handling of messages at client or server. Furthermore, they can be used as IED internal identification for the attribute. Data communication protocol developed by ABB Also known as SCL. XML-based description language for configurations of electrical substation IEDs. Defined in the IEC 61850 standard. 157

158

1MRS756342 REF 542plus 9. Abbreviations Abbreviation CB CDC CID DO DOI DS FTP FUPLA GUI HMI I/O ICD IEC IEC 61850 IED IP LD LN LN CSWI LN CILO LN GGIO LN MMXU LN SIMG LN XCBR LN XSWI MMS RAM RCB saddr SCADA SCD SCL SLD SNTP Description Circuit-breaker Common data class Configured IED description Data object Data object instance Data set File transfer protocol Function block programming language; Functional programming language; Function plan; Function chart Graphical user interface Human-machine interface Binary input and output IED capability description International Electrotechnical Commission International standard for substation communication and modelling Intelligent electronic device Internet protocol Logical device Logical node Type of LN; for Switch controller Type of LN; for Interlocking Type of LN; for Generic process Inputs and Outputs Type of LN; for Measurement Type of LN; Insulation medium supervision (gas) Type of LN; for Circuit Breaker Type of LN; for Circuit Switch Manufacturing message specification Random access memory Report Control Block Short Address InformationThe saddr attribute allows the allocation of a short address to the DO attributes. Short addresses can be used within the communication to be more efficient either in the communication or in the handling of messages at client or server. Furthermore, they can be used as the IED internal identification for the attribute. Supervision, control and data acquisition System configuration descriptionsubstation Configuration Description Substation configuration description language (defined by IEC 61850) Single-line diagram Simple Network Time Protocol 159

REF 542plus 1MRS756342 SPA TCP UTC XML Data communication protocol developed by ABB Transmission Control Protocol Universal time clock; Universal Time Coordinated Extensible markup language 160

ABB Oy Distribution Automation P.O. Box 699 FI-65101 Vaasa FINLAND +358 10 22 11 +358 10 22 224 1094 http://www.abb.com/substationautomation 1MRS756342 EN 10/2009