REF542plus CM 756342 ENb

REF 542plus
SCL Tool
Configuration manual
1MRS756342 REF 542plus
SCL Tool
Issued: 30.04.2007
Version: B/30.10.2009 Configuration manual
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 SCL Tool installation .............................. 13
4.3. Uninstalling REF 542plus SCL Tool............................. 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. SCL Tool 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. SCL Tool 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
SCL Tool
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
SCL Tool
Copyrights
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
SCL Tool
1. Introduction
1.1. This manual
This manual provides thorough information on the REF 542plus SCL Tool
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 SCL Tool features and the user-
related activity needed to interact with the SCL Tool 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
SCL Tool
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
SCL Tool 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
SCL Tool
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.
A070199
Fig. 2.-1 Connection diagram
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 SCL Tool 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 SCL Tool provides a
graphical user interface (GUI) where the application engineer can choose the desired
REF 542plus functions. The SCL Tool 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
SCL Tool
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
SCL Tool
4. Installation
4.1. System requirements
The system requirements for the SCL Tool 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 SCL Tool is compatible with the following versions:

* REF 542plus hardware Firmware version 2.5 SP1
* REF 542plus Configuration Tool version V4E04x
4.2. REF 542plus SCL Tool installation
Follow these steps to install the SCL Tool:

1. Close all applications.
2. Open the SCL Tool installation package which contains the two items shown in
Fig. 4.2.-1.
A070200
Fig. 4.2.-1 SCL Tool installation package
3. Double-click on the Setup.exe file to start the SCL Tool installation.

The REF 542plus SCL tool setup wizard dialog opens.
13
SCL Tool
A070201
Fig. 4.2.-2 SCL Tool setup wizard dialog
4. Click Next.
The Installation folder selection dialog opens.
14
SCL Tool
A070202
Fig. 4.2.-3 Installation folder selection dialog
5. To exit the installation, click Cancel in any dialog during the installation.
A070203
Fig. 4.2.-4 Cancel confirmation dialog
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 SCL Tool application is to be installed.
8. Click Browse to select a different folder.
15
SCL Tool
A070204
Fig. 4.2.-5 Browse for folder dialog
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 SCL Tool requires
A070205
Fig. 4.2.-6 Disk Space dialog
11.Click OK to return to the previous dialog.

12.Click Next to go to the next dialog.
16
SCL Tool
A070206
Fig. 4.2.-7 Confirm Installation dialog
13.Click Next to confirm the installation.
A070207
Fig. 4.2.-8 Installing SCL Tool
17
SCL Tool
A070208
Fig. 4.2.-9 Installation complete dialog
14.Click Close to exit from the installation.

An icon is set up on the local machine desktop to launch the SCL Tool
Application.
A070209
Fig. 4.2.-10 REF 542plus SCL Tool application icon
15.To start the SCL Tool application, double-click the REF 542plus SCL Tool icon
or
In the Windows task bar, select Start > Programs > REF 542plus SCL Tool
18
SCL Tool
4.3. Uninstalling REF 542plus SCL Tool
Follow the steps below to uninstall the REF 542plus SCL Tool
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 SCL Tool Ver2.1 file.
3. Click Remove.
A070210
Fig. 4.3.-1 Add or Remove Programs dialog
4. Verify that the icon on the desktop and SCL Tool selection option in Start >
Programs have been removed.
The uninstallation only removes the SCL Tool. It does not remove the .
NET Framework.
19
20
SCL Tool
5. SCL files and folders

Some of the critical folders and files that get installed by the SCL Tool 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
SCL Tool 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:
A070211
Fig. 5.1.-1 61850 XML file pool

* REF542plus. XML
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
SCL Tool
* 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
SCL Tool
This part is not required for the standalone version of the REF 542plus SCL Tool
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
SCL Tool
A070212
Fig. 5.4.-1 UserData folder
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.
A070574
Fig. 5.5.-1 Symbol Library folder
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 SCL Tool Core Component (explained later)
to validate every SCL file created by the REF 542plus SCL Tool.
24
SCL Tool
A070213
Fig. 5.6.-1 SCL schema file pool
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
SCL Tool
A070214
Fig. 5.7.-1 XML templates
26
SCL Tool
6. SCL Tool Components

The SCL Tool can be divided into two major components:
* SCL GUI
* SCL Core Component
6.1. SCL GUI
The GUI component of the SCL Tool 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
SCL Tool
A070215
Fig. 6.1.-1 SCL Generation tab
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 SCL Tool
Depending on the tab selected, the menu commands are enabled or disabled.
28
SCL Tool
A070216
Fig. 6.1.1.-1 File menu
* 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.
A070217
Fig. 6.1.1.-2 View menu
* 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
SCL Tool 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
SCL Tool
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.
A070218
Fig. 6.1.1.-3 Tools menu
* 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
SCL Tool
A070219
Fig. 6.1.1.-4 Window menu
* Help
The Help menu is provided to help learn more about the SCL Tool. It consists of
one menu command.
* About SCL Tool – Directs to the help documents for the SCL Tool.
A070220
Fig. 6.1.1.-5 Help menu
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
SCL Tool
* Sensor configuration and Protection

* Measurement
* Primary Switches
* General Status and Control I/Os
* Report Control Blocks
A070221
Fig. 6.1.2.-1 SCL Generation tab
3. Select the Files and Folders tab.

The fields in the tab are displayed.
A070222
Fig. 6.1.2.-2 Files and folders tab
4. Click Import.
The Open File dialog box is displayed. The REF 542plus Configuration RCA
file to be imported can be selected.
32
SCL Tool
A070223
Fig. 6.1.2.-3 RCA file browser
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, SCL Tool pops up a window to inform about missing events. This
information can be saved with the Save As and Print buttons.
A090130
Fig. 6.1.2.-4 Event checking information
33
SCL Tool
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.
A070224
Fig. 6.1.2.-5 RCA file configuration information
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
SCL Tool
A070225
Fig. 6.1.2.-6 RCA file import
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.
A070226
Fig. 6.1.2.-7 Select GUD file import
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
SCL Tool
A070227
Fig. 6.1.2.-8 SCL file folder browser
10.When the project folder is chosen, the entire directory text appears in the text
box, see Fig. 6.1.2.-9.
A070228
Fig. 6.1.2.-9 SCL file folder path
11.Select the type of SCL file to be generated, see Fig. 6.1.2.-10.
A070229
Fig. 6.1.2.-10 Selecting SCL file type
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
SCL Tool
A070556
Fig. 6.1.2.-11 Selecting SVG file
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
SCL Tool
A070232
Fig. 6.1.2.-12 Substation Relationship and Communication Settings tab
38
SCL Tool
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.
A070233
Fig. 6.1.2.-13 Entering a substation name
A070557
Fig. 6.1.2.-14 Entering a substation name for the automated IED name
* Voltage Level Designation: Select the voltage level designation from a drop-
down list.
39
SCL Tool
A070234
Fig. 6.1.2.-15 Selecting the voltage level designation
* Voltage Level Index: Select the voltage level index from a drop-down list.
A070546
Fig. 6.1.2.-16 Selecting the voltage level index
* 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
SCL Tool
A070235
Fig. 6.1.2.-17 Entering the voltage value
* 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.
A070236
Fig. 6.1.2.-18 Entering the bay designation
41
SCL Tool
A070558
Fig. 6.1.2.-19 Entering the bay designation for automated IED name
* 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.
A070547
Fig. 6.1.2.-20 Entering the IED Designation for automated IED name
* If the IED Name check box is unchecked, IED Name field is enabled. Enter
the IED Name up to 10 characters.
42
SCL Tool
A070237
Fig. 6.1.2.-21 Entering the IED name
* 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.
A070559
Fig. 6.1.2.-22 Automated IED name
* 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
SCL Tool
A070238
Fig. 6.1.2.-23 Entering the IP address
* 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.
A070239
Fig. 6.1.2.-24 Selecting the DST correction
* Select Week Day, Month, After Month Day, Hour, Minute and Second for
both Start of DST and End of DST.
44
SCL Tool
A070241
Fig. 6.1.2.-25 Selecting the start and end of DST
* 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.
A070242
Fig. 6.1.2.-26 Selecting the time zone correction
* 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
SCL Tool
A090132
Fig. 6.1.2.-27 Saving dialog for ECM
This starts the ECM file generation process, and after a successful creation of
the ECM file, a popup window appears.
A090134
Fig. 6.1.2.-28 ECM File generated
* 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
SCL Tool
A090136
Fig. 6.1.2.-29 Open dialog for the ECM import
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.
A090138
Fig. 6.1.2.-30 ECM file imported
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
SCL Tool
A090140
Fig. 6.1.2.-31 Sensor Configuration and Protection tab
16.Click the Measurement tab. It displays the measurement configuration in the

imported REF 542plus Configuration file.
A090142
Fig. 6.1.2.-32 Measurement tab
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
SCL Tool
* 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.
A070244
Fig. 6.1.2.-33 Primary Switches tab
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
SCL Tool
A070245
Fig. 6.1.2.-34 Primary Switches table
* Enter the designation of up to 10 characters.
A070246
Fig. 6.1.2.-35 Entering the designation
* Select or clear the Controllable column to confirm whether the switch is

controllable or not.
A070247
Fig. 6.1.2.-36 Controllable option for primary switches
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
SCL Tool
A070248
Fig. 6.1.2.-37 General I/Os tab
51
SCL Tool
* The table can be filtered on the basis of the FUPLA object reference by using
a drop-down list.
A090144
Fig. 6.1.2.-38 General I/Os tab with Filter By
* A Spa channel number can be searched for by using the search option.
A090146
Fig. 6.1.2.-39 General I/Os tab with the Search option
* 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
SCL Tool
A090148
Fig. 6.1.2.-40 Sorting by LN Instance Number
A090150
Fig. 6.1.2.-41 Sorting by LN Prefix
* Click a row once to select the entire row.

* Enter data for the corresponding FUPLA Object Reference by double-
clicking a row.
The SCL tool pops up the GGIO Data window to fill the data.
* By default, the IEC 61850 check box is selected.
A090152
Fig. 6.1.2.-42 GGIO data window
* Enter the signal designation of up to 20 characters.
53
SCL Tool
A090154
Fig. 6.1.2.-43 Signal Designation
* 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."
A090156
Fig. 6.1.2.-44 LN Prefix
* 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.
A090158
Fig. 6.1.2.-45 LN Name
54
SCL Tool
* 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.
A090160
Fig. 6.1.2.-46 LN Instance Number
* 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
SCL Tool
* 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.
A090162
Fig. 6.1.2.-47 DOI Name
* Enter the DOI number of up to two digits.
A090164
Fig. 6.1.2.-48 DOI Number
* 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.
A090166
Fig. 6.1.2.-49 DS Allocation
56
SCL Tool
* 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).
A090168
Fig. 6.1.2.-50 Report Control Blocks tab for the CID file type
All the columns can be edited against each dataset. In case of the ICD file
generation, the client table is not available.
57
SCL Tool
A090170
Fig. 6.1.2.-51 Report Control Blocks tab for the ICD file type
* The Buffer Enable column values can be edited.
A090172
Fig. 6.1.2.-52 Report Control: Buffer Enable
* A Buffer Time of up to three digits can be given.
A090174
Fig. 6.1.2.-53 Report Control: Buffer Time
* Select the maximum number of subscribing clients from the drop-down list.
58
SCL Tool
A090176
Fig. 6.1.2.-54 RptEnabled: Number of Subscribing Clients
* Enter a Configuration Revision value of up to two digits.
A090178
Fig. 6.1.2.-55 Report Control: Configuration Revision
* Select Sequence Number Enable with the check box.
A090180
Fig. 6.1.2.-56 OptFields: Sequence Number Enable
* Select TimeStamp Enable with the check box.
A090182
Fig. 6.1.2.-57 OptFields: TimeStamp Enable
* Select DataSet Enable with the check box.
A090184
Fig. 6.1.2.-58 OptFields: DataSet Enable
59
SCL Tool
* Select ReasonCode Enable with the check box.
A090186
Fig. 6.1.2.-59 OptFields: ReasonCode Enable
* Select the maximum DataRef Enable with the check box.
A090188
Fig. 6.1.2.-60 OptFields: DataRef Enable
* Select EntryID Enable with the check box.
A090190
Fig. 6.1.2.-61 OptFields: EntryID Enable
* Select ConfigRef Enable with the check box.
A090192
Fig. 6.1.2.-62 OptFields: ConfigRef Enable
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
SCL Tool
A090194
Fig. 6.1.2.-63 RCB Client Information Table
* Enter a client IED name of up to seven characters in the second table.
A090196
Fig. 6.1.2.-64 Client IED Name
* Enter an IP address other than 0.0.0.0 or 255.255.255.255.
A090198
Fig. 6.1.2.-65 Client IP address
* Enter an IP Subnet address other than 0.0.0.0 or 255.255.255.255.
A090200
Fig. 6.1.2.-66 Client IED IP Subnet
* Enter an IP Gateway address other than 0.0.0.0 or 255.255.255.255.
61
SCL Tool
A090202
Fig. 6.1.2.-67 Client IED IP Gateway
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.
A090204
Fig. 6.1.2.-68 Missing events information
* Click Yes or No when the SCL tool prompts to save the data that was entered
in the GUI.
62
SCL Tool
a090206
Fig. 6.1.2.-69 Save GUI Data message
* 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.
A090208
Fig. 6.1.2.-70 Save GUI Data information dialog
* Enter a file name of up to 16 characters.
A090210
Fig. 6.1.2.-71 GUD file name
* 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), SCL Tool displays a message for validation.
63
SCL Tool
A090212
Fig. 6.1.2.-72 SCL File Generated and Validated message
6.1.3. CID/ICD Import

1. Click the CID/ICD Import tab.
The SCL file import section of the application opens.
A090214
Fig. 6.1.3.-1 CID/ICD Import tab
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
SCL Tool
A090216
Fig. 6.1.3.-2 Import SCL file
3. Select Import SCL File to open a dialog to choose a file and import.
A090218
Fig. 6.1.3.-3 Select SCL file
4. Click Select SCL File to browse for the file.
65
SCL Tool
A070282
Fig. 6.1.3.-4 SCL file dialog
5. Select the file and click Open to import the file.
A070283
Fig. 6.1.3.-5 Progress bar navigation for the SCL file import
66
SCL Tool
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.
A090220
Fig. 6.1.3.-6 Missing even information
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.
A090222
Fig. 6.1.3.-7 Tree structure navigation
6. Right-click LD0 and select Expand.
67
SCL Tool
A070285
Fig. 6.1.3.-8 Expand tree node
A070286
Fig. 6.1.3.-9 Expanded tree node
7. Right-click LD1 and select Expand. All the LNs under LD1 are displayed.
68
SCL Tool
A070287
Fig. 6.1.3.-10 LN tree node navigation
8. Expand an LN to view its DOIs.
69
SCL Tool
A070288
Fig. 6.1.3.-11 Expanded LN tree node navigation
9. Right-click any of the DOIs to view the available options for editting a DOI.
70
SCL Tool
A070289
Fig. 6.1.3.-12 DOIEditor tool option
10.Select Properties to open the property window for the DOI.
71
SCL Tool
A070290
Fig. 6.1.3.-13 DOI property bar navigation
11.Right-click and select DOIEditor to open the DOI editor window to view or edit
the DOI attributes.
72
SCL Tool
A070291
Fig. 6.1.3.-14 DOIEditor tool option
73
SCL Tool
A070292
Fig. 6.1.3.-15 DOI editor navigation
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
SCL Tool
A090224
Fig. 6.1.3.-16 Updating of sAddress
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
SCL Tool
A070293
Fig. 6.1.3.-17 DOI deletion
14.Click Yes to delete the DOI from the LN.
76
SCL Tool
A070294
Fig. 6.1.3.-18 Updated tree structure after the DOI deletion
15.Right-click any LN of the GGIO type and select DOWizard to add a DOI to the
LN.
77
SCL Tool
A070295
Fig. 6.1.3.-19 DOWizard tool option
16.Select the DOI name from the selection list and enter the DOI number.
A070296
Fig. 6.1.3.-20 DOWizard
The possible DOI names with the DOType and CDC are given in the following
table.
78
SCL Tool
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.
A070297
Fig. 6.1.3.-21 Added DOI navigation
18.Right-click LD1 and select LNWizard to add an LN of the GGIO type to LD1.
79
SCL Tool
A070298
Fig. 6.1.3.-22 LNWizard tool option
80
SCL Tool
A070299
Fig. 6.1.3.-23 LNWizard navigation
19.Enter the prefix and LN instant number.
A070300
Fig. 6.1.3.-24 LNWizard: field navigation
20.Click Add LN to add the LN to LD1. The LN "T1GGIO1" is added at the end of
the tree structure.
81
SCL Tool
A070301
Fig. 6.1.3.-25 Added LN navigation
21.Expand LLN0 under LD0 to view the datasets and Report control blocks.
82
SCL Tool
A070302
Fig. 6.1.3.-26 Dataset and the Report control blocks navigation
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
SCL Tool
A070303
Fig. 6.1.3.-27 Add Dataset option
23.Click StatUrgB to add the dataset.

The dataset StatUrgB is added along with its corresponding RCB rcb_AB at the
end.
84
SCL Tool
A070304
Fig. 6.1.3.-28 Added dataset navigation
24.Right-click the dataset and select Delete to delete the dataset and its
corresponding RCB.
85
SCL Tool
A070305
Fig. 6.1.3.-29 Delete Dataset
86
SCL Tool
A070306
Fig. 6.1.3.-30 Updated tree structure navigation after the DS deletion
25.Right-click any dataset and select DataSet Editor to view the list of FCDAs
under that particular dataset.
87
SCL Tool
A070307
Fig. 6.1.3.-31 DataSet Editor tool option
88
SCL Tool
A070308
Fig. 6.1.3.-32 DataSet Editor navigation
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
SCL Tool
A070309
Fig. 6.1.3.-33 FCDAs added at the end of the DataSet Editor
27.Delete an entry from the DataSet editor by right-clicking a row and selecting
Delete.
A090226
Fig. 6.1.3.-34 Delete FCDA entries from dataset
90
SCL Tool
A090228
Fig. 6.1.3.-35 Updated DataSet editor after deleting the selected FCDA entry
28.Expand an RCB.
29.Expand the ReportEnabled node under the RCB.
30.Right-click to add Report Client.
91
SCL Tool
A070310
Fig. 6.1.3.-36 Adding an RCB client
If the newly added Report Client is the fifth client, a dialog box is displayed with
the IP details of Client 5.
A070311
Fig. 6.1.3.-37 RCB client information
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
SCL Tool
A070312
Fig. 6.1.3.-38 Updated tree structure after the RCB client addition
32.Set the properties for the added Client using the property field. The IED Name
property consists of IED names.
93
SCL Tool
A070560
Fig. 6.1.3.-39 RCB Client properties navigation
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.
A070313
Fig. 6.1.3.-40 SCL file export option navigation
94
SCL Tool
A070314
Fig. 6.1.3.-41 SCL file export window navigation
34.Click Write to browse for the file name or type the file name to save the SCL
file.
95
SCL Tool
A070315
Fig. 6.1.3.-42 Save file dialog for exporting the SCL file
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 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.
A090320
Fig. 6.1.3.-43 Event checking for exporting file
A dialog is displayed once the file is exported successfully.
96
SCL Tool
A090232
Fig. 6.1.3.-44 Progress bar navigation for the SCL file export
97
SCL Tool
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.
A090234
Fig. 6.1.4.-1 SCD import tab
2. Right-click the SCD node under Project Explorer on the left.
A090236
Fig. 6.1.4.-2 Import SCD file
3. Select Import SCD File to open a dialog for choosing the file and importing.
98
SCL Tool
A090238
Fig. 6.1.4.-3 Select SCD File
4. Click Select SCD File to browse for the file.
A090240
Fig. 6.1.4.-4 SCD File dialog
5. Select the file and click Open to import the file.
99
SCL Tool
A090242
Fig. 6.1.4.-5 Progress bar navigation for the SCD File import
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.
A090244
Fig. 6.1.4.-6 Tree structure navigation
6. Right-click LD0 and select Expand. Fig 6.1.4.-7 displays all the LNs under
LD0.
100
SCL Tool
A090246
Fig. 6.1.4.-7 Expand tree node
A090248
Fig. 6.1.4.-8 Expanded tree node
7. Right-click LD1 to expand and display all the LNs under LD1.
101
SCL Tool
A090250
Fig. 6.1.4.-9 LN tree node navigation
8. Expand any of the LNs to view its DOIs.
102
SCL Tool
A090252
Fig. 6.1.4.-10 Expanded LN tree node navigation
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.
A090254
Fig. 6.1.4.-11 CID File export option navigation
103
SCL Tool
A090256
Fig. 6.1.4.-12 CID File export window navigation
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.
A090258
Fig. 6.1.4.-13 Save File dialog for exporting the SCL file
11.A popup is displayed once the file is exported successfully.
104
SCL Tool
A090260
Fig. 6.1.4.-14 Progress bar navigation for CID File export
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
SCL Tool
A070317
Fig. 6.1.5.-1 FTP Download or Upload tab
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
SCL Tool
A090262
Fig. 6.1.5.-2 IP textbox for the ECM file
5. Enter the IP address of the REF 542plus EB.

6. Enter the user name and password (abb for REF 542plus EB).
107
SCL Tool
A090264
Fig. 6.1.5.-3 Filling user ID and password for the FTP download
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 SCL Tool
is resetting the REF 542plus EB to recognize the newly loaded file.
A070319
Fig. 6.1.5.-4 Notification after the download
8. Click Upload.
108
SCL Tool
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.
A090266
Fig. 6.1.5.-5 File type to upload
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
SCL Tool
A070320
Fig. 6.1.5.-6 Notification after the upload
13.Click OK.
The REF542plus.cid file is in the destination folder.
A070321
Fig. 6.1.5.-7 Uploaded CID File navigation
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
SCL Tool
A090268
Fig. 6.1.6.-1 Firmware download
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
SCL Tool
A090270
Fig. 6.1.7.-1 Access to Graphical FTP
A090272
Fig. 6.1.7.-2 Graphical FTP
3. Enter the IP address of the IED, user name and password.
112
SCL Tool
4. Click List File Details to view the files in the IED.
A090274
Fig. 6.1.7.-3 Graphical FTP progress bar
5. See the tree view of the files available in the IED.
6.1.8. TELNET interface

1. On the Tools menu, click TELNET.
A090276
Fig. 6.1.8.-1 TELNET
The TELNET interface window appears. By default, the value of Port is 23.
113
SCL Tool
A090278
Fig. 6.1.8.-2 TELNET interface
2. Type the IP address for the host and click Connect.
A090280
Fig. 6.1.8.-3 TELNET interface connect
3. Type the user name in the Command text box and click Execute.
114
SCL Tool
A090282
Fig. 6.1.8.-4 TELNET interface user name
4. Type the password in the Command text box and click Execute.
A090284
Fig. 6.1.8.-5 TELNET interface password
5. Type in the TELNET command and click Execute.

Status/Result shows in the window.
115
SCL Tool
A090286
Fig. 6.1.8.-6 TELNET command execution
6.2. SCL core component
The SCL Tool 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 SCL Tool GUI are compared to the
final form of the SCL files.
116
SCL Tool
* 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 SCL Tool.
A070322
Fig. 6.2.-1 Header ID navigation
* Substation section (applicable to CID files only):

The Substation Relationship and Time Settings tab along with the relevant part
of the SCL file.
A070323
Fig. 6.2.-2 Substation relationship GUI information update
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
SCL Tool
A070324
Fig. 6.2.-3 SNTP server IP information update
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
* Time settings section
The time settings section along with the relevant part of the SCL file are shown
in Fig. 6.2.-4.
118
SCL Tool
A070325
Fig. 6.2.-4 Time settings information update
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
SCL Tool
* 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.
A090288
Fig. 6.2.-5 Measurement configuration information update
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
SCL Tool
A090290
Fig. 6.2.-6 Measurement configuration sAddr information update
* 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.
A070328
Fig. 6.2.-7 Primary switches information update
121
SCL Tool
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.
A070329
Fig. 6.2.-8 Channel number update for CILO
* 1 LN CSWI with the prefix CB, instance number 9 and description Switching
sAddr for Pos contains both the control and status part.
A070330
Fig. 6.2.-9 Channel number update for CSWI
* 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
SCL Tool
A070331
Fig. 6.2.-10 Channel number update for XCBR
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
A070332
Fig. 6.2.-11 LN creation for non-controllable primary switches
123
SCL Tool
The explanation for the primary switches part is as follows:

* 1 LN CSWI with the prefix CB, instance number 9 and description Switching
sAddr for Pos contains only the status part.
A070333
Fig. 6.2.-12 Channel number update for CSWI
* 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
SCL Tool
A070334
Fig. 6.2.-13 Channel number update for XCBR
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
SCL Tool
A090292
Fig. 6.2.-14 Coil supervision update for XCBR
* Protection section
The protection functions along with the relevant part of the SCL file are shown
in Fig. 6.2.-15.
126
SCL Tool
A070335
Fig. 6.2.-15 LN creation for the protection functions
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
SCL Tool
A070337
Fig. 6.2.-16 LN creation for GGIO
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
SCL Tool
First FUPLA Object Second FUPLA Object

DO Type
Reference 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:
A070338
Fig. 6.2.-17 DOI creation for GGIO LN
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
SCL Tool
A070339
Fig. 6.2.-18 Report control creation
130
SCL Tool
A070340
Fig. 6.2.-19 Properties update for RCB
A070341
Fig. 6.2.-20 Properties for RCB
131
SCL Tool
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
A070342
Fig. 6.2.-21 RCB client update
As shown above, the following information is updated under each client:

* IED Name
* IP Address
132
SCL Tool
* 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.
A070343
Fig. 6.2.-22 RCB client IP addresses update
* 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
SCL Tool
A070344
Fig. 6.2.-23 Device reference update
The revision information of the SCL Tool 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
SCL Tool
A070345
Fig. 6.2.-24 SCL Tool version information
* 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.
A070562
Fig. 6.2.-25 Symbol information in the SCL file
* 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
SCL Tool
A070563
Fig. 6.2.-26 Annotation information in the SCL file.
* ConnectivityNode Information: ConnectivityNode’s coordinates are

determined from the intersection points and then added to the SCL file as
A070564
Fig. 6.2.-27 ConnectivityNode information in the SCL file
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 SCL Tool 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.
A090294
Fig. 6.3.-1 Header information of the ECM file
* The Description section shows the substation information.
136
SCL Tool
A090296
Fig. 6.3.-2 Description field of the ECM file
* The General section indicates the active application protocols.
A090298
Fig. 6.3.-3 General section (Protocols) information of the ECM file
* The MODTCP section shows the MODBUS-TCP information.
A090300
Fig. 6.3.-4 MODBUS-TCP section of the ECM file
The following information is available under the MODTCP section:
137
SCL Tool
* 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.
A090302
Fig. 6.3.-5 SNTP section in the ECM file
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
SCL Tool
* 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.
A090304
Fig. 6.3.-6 HTTP section in the ECM file
* The SPA TCP section shows the SPATCP information.
A090306
Fig. 6.3.-7 SPA TCP section in the ECM file
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
SCL Tool
A090308
Fig. 6.3.-8 Security section in the ECM file
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
SCL Tool
7. SCL Tool error and exception handling

7.1. Missing files
SCL Tool 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 SCL Tool:
* 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 SCL Tool detects that
the folder is missing the Protection.xml file.
A070346
Fig. 7.1.-1 Missing file information in the 61850 file pool
* SCL schema file pool

If an SCL schema file pool file is missing, an exception message is shown by
SCL Tool. Fig. 7.1.-2 shows the error message displayed when the SCL Tool
detects that the folder is missing the CommonSA.xsd file.
A070347
Fig. 7.1.-2 Missing file information in the SCL schema file pool
141
SCL Tool
7.2. Configuration Tool RCA file
The following messages are displayed when the .rca file is not configured properly:
* The SCL Tool 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).
A070348
Fig. 7.2.-1 Communication board error in the RCA file
* The SCL Tool 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.
A070349
Fig. 7.2.-2 RCA file format error
* The SCL tool detects if the imported configuration file does not have protocol
information. The tool displays a message with the error type.
A090310
Fig. 7.2.-3 Protocol information missing
142
SCL Tool
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.
A090312
Fig. 7.3.1.-1 Device reference error
* 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.
A090314
Fig. 7.3.1.-2 Invalid SVG file import error
* 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.
A070351
Fig. 7.3.1.-3 Voltage level value error
* 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
SCL Tool
A090316
Fig. 7.3.1.-4 Substation name error
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.
A090318
Fig. 7.3.2.-1 Protocol type error
* 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.
A090320
Fig. 7.3.2.-2 Validation error
* 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
SCL Tool
A090322
Fig. 7.3.2.-3 IP address moving error
* 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.
A090324
Fig. 7.3.2.-4 IP address error
* 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.
A090326
Fig. 7.3.2.-5 Security information error
* If a form is submitted in the SNTP section without the SNTP IP being filled in,
an error message is displayed.
A090328
Fig. 7.3.2.-6 SNTP form validation error
* 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
SCL Tool
A090330
Fig. 7.3.2.-7 Parameter reading and writing validation error
* If in the Substation and Communication Settings tab SNTP is not configured and
an SCL file is generated, an error message is displayed.
A090332
Fig. 7.3.2.-8 SNTP server validation error
* 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.
A090334
Fig. 7.3.2.-9 Substation name error
* 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.
A090336
Fig. 7.3.2.-10 Primary switches designation error
146
SCL Tool
* 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.
A090338
Fig. 7.3.2.-11 Circuit breaker information message
* In the General I/Os tab, values can only be typed for LNGGIO Instance Number
or DOI Number, otherwise an error message is displayed.
A090340
Fig. 7.3.2.-12 Validation message for Instance Number and DOI Number
* In the General I/Os tab, the LNGGIO prefix can be started with alphabets only,
otherwise an error message is displayed.
A090342
Fig. 7.3.2.-13 Validation message for GGIO prefix
* 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
SCL Tool
A090344
Fig. 7.3.2.-14 Error message for LN Name
* 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.
A090346
Fig. 7.3.2.-15 Validation for the Enabled field
* 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
A090348
Fig. 7.3.2.-16 Validation for identical information for GGIO
* 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
SCL Tool
A090350
Fig. 7.3.2.-17 Validation for the DOI name
* If in the General I/Os tab the coil supervision is already configured but it is
reconfigured, an information message is displayed.
A090352
Fig. 7.3.2.-18 Validation for coil supervision DOIs
* 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.
A090354
Fig. 7.3.2.-19 Validation for the RCB properties
* If in the Report Control Blocks tab a wrong IP/IP Subnet/IP Gateway address is
typed, an error message is displayed.
A090356
Fig. 7.3.2.-20 Validation for the IP address
149
SCL Tool
* 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.
A090358
Fig. 7.3.2.-21 Error message for Buffer Time
* 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.
A090360
Fig. 7.3.2.-22 Dataset overflow notification
* 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.
A090362
Fig. 7.3.2.-23 SLD addition error message
* 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,
SCL Tool 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
SCL Tool
A090364
Fig. 7.3.2.-24 Configuration revision change information
* If in the RCB client the Client IED name is typed as "Dummy," an error message
is displayed.
A090366
Fig. 7.3.2.-25 Client IED name validation
* 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.
A090368
Fig. 7.3.2.-26 DOI number validation
* In the General I/Os tab only ISO646 string characters can be typed in the Signal
Designation field. Otherwise, an error message is displayed.
A090370
Fig. 7.3.2.-27 Signal Designation character validation
* Clicking "details" displays the table for the ISO646 string.
151
SCL Tool
A090372
Fig. 7.3.2.-28 ISO646 characters table
* 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.
A090374
Fig. 7.3.2.-29 DOI validation message
* 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
SCL Tool
A090376
Fig. 7.3.2.-30 Mandatory DOI validation
* 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.
A090378
Fig. 7.3.2.-31 LN generation validation
* In the General I/Os tab only alphanumeric characters can be typed in for the LN
prefix. Otherwise, an error message is displayed.
A090380
Fig. 7.3.2.-32 LN prefix character validation
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.
A070572
Fig. 7.3.3.-1 Validation for LNGGIO prefix
153
SCL Tool
* 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.
A070428
Fig. 7.3.3.-2 DataSet overflow notification
* 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.
A070429
Fig. 7.3.3.-3 Validation for IED properties
* 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.
A070430
Fig. 7.3.3.-4 Validation for IP address
* 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
SCL Tool
A070573
Fig. 7.3.3.-5 Validation for client IED name
* If another SCL file is imported over the previous file, a warning message is
displayed.
A090382
Fig. 7.3.3.-6 SCL file import notification
7.3.4. SCD import

* If another SCD file is imported over the previous file, a warning message is
displayed.
A090384
Fig. 7.3.4.-1 SCD file import warning
* If the same IED node is exported again, an information message is displayed.
A090386
Fig. 7.3.4.-2 SCD file export notification
155
SCL Tool
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.
A070431
Fig. 7.3.5.-1 FTP connection not established
* If the FTP connection is not able to connect in the FTP download or upload
section, an error message is shown.
A090388
Fig. 7.3.5.-2 FTP connection error
7.3.6. Graphical FTP

* If an FTP cpnnection cannot be formed in the Graphical FTP section, an error
A090390
Fig. 7.3.6.-1 Connection error
156
SCL Tool
8. Terminology
Term Description
Configuration Tool Software program to configure the REF 542plus. This
program runs on a PC.
Data Set The data set is the content basis for reporting and logging.
The data set contains references to the data and data
attribute values.
Ethernet Physical communication network to transfer Internet data of
the REF 542plus to the PC and back.
Firmware The base software programs stored inside the
REF 542plus. Among them, there are the FUPLA file
interpreter and the protection functions programs.
Report Control Block 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.
sAddr 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.
SPA Data communication protocol developed by ABB
Substation Configuration de- Also known as SCL. XML-based description language for
scription Language configurations of electrical substation IEDs. Defined in the
IEC 61850 standard.
157
158
SCL Tool
9. Abbreviations
Abbreviation Description
CB Circuit-breaker
CDC Common data class
CID Configured IED description
DO Data object
DOI Data object instance
DS Data set
FTP File transfer protocol
FUPLA Function block programming language; Functional pro-
gramming language; Function plan; Function chart
GUI Graphical user interface
HMI Human-machine interface
I/O Binary input and output
ICD IED capability description
IEC International Electrotechnical Commission
IEC 61850 International standard for substation communication and
modelling
IED Intelligent electronic device
IP Internet protocol
LD Logical device
LN Logical node
LN CSWI Type of LN; for Switch controller
LN CILO Type of LN; for Interlocking
LN GGIO Type of LN; for Generic process Inputs and Outputs
LN MMXU Type of LN; for Measurement
LN SIMG Type of LN; Insulation medium supervision (gas)
LN XCBR Type of LN; for Circuit Breaker
LN XSWI Type of LN; for Circuit Switch
MMS Manufacturing message specification
RAM Random access memory
RCB Report Control Block
sAddr 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.
SCADA Supervision, control and data acquisition
SCD System configuration descriptionSubstation Configuration
Description
SCL Substation configuration description language (defined by
IEC 61850)
SLD Single-line diagram
SNTP Simple Network Time Protocol
159
SCL Tool
SPA Data communication protocol developed by ABB

TCP Transmission Control Protocol
UTC Universal time clock; Universal Time Coordinated
XML Extensible markup language
160
1MRS756342 EN 10/2009
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

REF542plus CM 756342 ENb

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

REF542plus CM 756342 ENb

Transféré par

Droits d'auteur :

Formats disponibles

REF 542plus

7.3.4. SCD import................................................155

In no event shall ABB Oy be liable for direct, indirect, special, incidental or

The software or hardware described in this document is furnished under a license

© Copyright 2009 ABB Oy

All rights reserved.

In order to achieve this purpose, two major components are required:

1.2. Use of symbols

It should be understood that operation of damaged equipment could, under certain

1.3. Product documentation

1.4. Document revisions

Fig. 2.-1 Connection diagram

3. IEC 61850 standard

The IEDs support the following functions:

IEC 61850 provides:

Compared to other communication standards for Substation Automation, the

The system requirements for the SCL Tool are as follows:

The SCL Tool is compatible with the following versions:

4.2. REF 542plus SCL Tool installation

Follow these steps to install the SCL Tool:

Fig. 4.2.-1 SCL Tool installation package

3. Double-click on the Setup.exe file to start the SCL Tool installation.

Fig. 4.2.-2 SCL Tool setup wizard dialog

Fig. 4.2.-3 Installation folder selection dialog

Fig. 4.2.-4 Cancel confirmation dialog

6. In the cancel confirmation dialog, click Yes to exit the installation

Click No to continue the installation.

Fig. 4.2.-5 Browse for folder dialog

9. Select the folder to install the application in and click OK.

Fig. 4.2.-6 Disk Space dialog

11.Click OK to return to the previous dialog.

Fig. 4.2.-7 Confirm Installation dialog

13.Click Next to confirm the installation.

Fig. 4.2.-8 Installing SCL Tool

Fig. 4.2.-9 Installation complete dialog

14.Click Close to exit from the installation.

Fig. 4.2.-10 REF 542plus SCL Tool application icon

4.3. Uninstalling REF 542plus SCL Tool

Fig. 4.3.-1 Add or Remove Programs dialog

5. SCL files and folders

5.1. 61850 XML File Pool

Fig. 5.1.-1 61850 XML file pool

5.3. Missing Dataset FCDA Entries

Fig. 5.4.-1 UserData folder

5.5. Symbol Library

Fig. 5.5.-1 Symbol Library folder

5.6. SCL schema file pool

Fig. 5.6.-1 SCL schema file pool

The SCL schema file pool consists of the following files:

5.7. XML templates

Fig. 5.7.-1 XML templates

6. SCL Tool Components

6.1. SCL GUI

The GUI component of the SCL Tool contains:

By default the SCL Generation tab is selected, see Fig. 6.1.-1.

Fig. 6.1.-1 SCL Generation tab

6.1.1. Menu bar

The menu bar contains the following main menus:

The File menu has the following menu commands:

Fig. 6.1.1.-1 File menu

Fig. 6.1.1.-2 View menu

The default menu commands include:

If the selected tree node is