Config User Guide

User Guide
61850 Config
© 2010 Cooper Power Systems, hardware, software and manual. All rights reserved.
The information in this document is subject to change without notice.
Cooper Power Systems

Energy Automation Solutions
730 Commerciale Street
Suite 200
Saint-Jean-Chrysostome, Quebec
Canada G6Z 2C5
Phone: +1.418.834.0009
Fax: +1.514.227.5256
Email: sales@cybectec.com
Web: http://www.cooperpowereas.com
Technical Support: support@cybectec.com
GUI-00315-00001 T, version 9
Contents
1 Getting Started 1
1.1 Introduction ...........................................................................................................1
1.1.1 Welcome to 61850 Config ......................................................................1
1.1.2 Installing 61850 Config...........................................................................1
1.2 61850 Config .........................................................................................................2
1.2.1 Protocol Overview ..................................................................................2
1.2.2 Systems Overview ...................................................................................3
2 Using 61850 Config 5

2.1 Preliminary Requirements .....................................................................................5
2.2 Starting 61850 Config ...........................................................................................5
2.3 Creating a New Slave Connection .........................................................................6
2.4 Creating a New IEC 61850 Slave Configuration from Scratch .............................7
2.4.1 Creating a Slave Component ...................................................................7
2.4.2 Adding Clients to a Slave Component ....................................................9
2.4.3 Adding Files to a Slave Component ........................................................9
2.4.4 Adding a Logical Device to a Slave Component ..................................10
2.4.5 Adding a Logical Node to a Logical Device .........................................10
2.4.6 Adding a Common Data Class to a Logical Node ................................10
2.4.7 Adding a Control Block to a Logical Node ...........................................12
2.4.8 Adding a Dataset to a Logical Node .....................................................12
2.5 Modifying an IEC 61850 Slave Configuration ....................................................13
2.5.1 Editing the Client Rights .......................................................................13
2.5.2 Editing Common Data Class and Control Block Properties..................13
2.5.3 Deleting an Item ....................................................................................15
2.5.4 Renaming an Item .................................................................................15
2.5.5 Duplicating a Logical Device ................................................................15
2.6 Creating a New IEC 61850 Slave Configuration Template.................................15
2.6.1 Using Aliases ........................................................................................16
2.6.2 Creating the Template ...........................................................................16
2.7 Adding IEC 61850 Slave Configuration Template Data to an Existing IEC
61850 Slave .......................................................................................................................18
61850 Config User Guide •i

2.8 Creating a New UCA 2.0 Slave Configuration Using the Wizard.......................20
2.8.1 Creating a Slave Component .................................................................20
2.9 Creating a New UCA 2.0 Slave Configuration From Scratch .............................22
2.9.1 Creating a Slave Component .................................................................22
2.9.3 Adding a Folder under a DeviceModel .................................................23
2.9.4 Adding a Data Point under a DeviceModel...........................................23
2.9.5 Adding a Dataset to a Datasets Folder ..................................................23
2.9.6 Adding Basic Building Bricks under a DeviceModel ...........................24
2.9.7 Adding a Common Class under a DeviceModel ...................................25
2.10 Modifying a UCA 2.0 Slave Configuration .........................................................28
2.10.1 Editing Data Point Properties..................................................28
2.10.2 Copying a Folder or a Data Point............................................32
2.10.3 Cutting a Folder or a Data Point .............................................32
2.10.4 Pasting a Folder or a Data Point..............................................32
2.10.5 Deleting a Folder or a Data Point............................................32
2.10.6 Renaming a Folder or a Data Point .........................................32
2.10.7 Duplicating a Logical Device .................................................32
2.11 Creating a New Master Connection.....................................................................33
2.12 Creating a New IEC 61850 Master Configuration from Scratch .........................33
2.12.1 Creating a Master Component ................................................33
2.12.2 Configuring the Master Automatically ...................................36
2.13 Creating a New IEC 61850 Master Configuration Template ..............................36
2.14 Creating a New IEC 61850 Master Configuration from a Template ...................37
2.15 Modifying an IEC 61850 Master Configuration..................................................37
2.15.1 Refreshing the Configuration ..................................................37
2.15.2 Adding Common Data Classes or Control Blocks
Manually 38
2.15.3 Editing Common Data Class or Control Block Properties ......40
2.15.4 Adding Reports to Retrieve Data from the Device .................41
2.15.5 Adding Files to the Master Component ..................................42
2.15.6 Adding a Scan Cycle to Retrieve Data from the Device .........43
2.15.7 Editing the Logical Data Points of the Master ........................44
2.16 Creating a New UCA 2.0 Master Configuration from Scratch ............................44
2.16.1 Creating a Master Component ................................................44
2.16.2 Setting the Parameters of a Master Component ......................44
ii • 61850 Config User Guide

2.16.3 Downloading the Device Configuration .................................45
2.16.4 Adding a Data Point to a Master Component .........................45
2.16.5 Associating an Existing Data Point with a Device Point ........46
2.16.6 Adding a Scan Cycle to Retrieve Data from the Device .........47
2.16.7 Adding Device Report Support ...............................................48
2.16.8 Creating Brick Templates .......................................................48
2.16.9 Instantiating Brick Templates .................................................48
2.17 Creating a New UCA 2.0 Master Configuration Template .................................50
2.18 Creating a New UCA 2.0 Master Configuration from a Template ......................50
2.19 Modifying a UCA 2.0 Master Configuration ......................................................51
2.19.1 Editing Data Point Properties..................................................51
2.19.2 Deleting a Data Point ..............................................................54
2.19.3 Copying a Data Point ..............................................................55
2.19.4 Pasting a Data Point ................................................................55
2.19.5 Refreshing the Device Values Used as Data Point
Properties 55
2.20 Validating an IEC 61850 and UCA 2.0 Configuration ........................................55
61850 Config User Guide • iii

1 Getting Started
1.1 Introduction
1.1.1 Welcome to 61850 Config
61850 Config is designed to help you set up slaves and masters based on the IEC 61850 and UCA
2.0 protocols. With 61850 Config, you can easily:
Add a new IEC 61850 and UCA 2.0 slave configuration to an SMP configuration file created
by SMP Config.
Modify an existing IEC 61850 and UCA 2.0 slave configuration in an SMP configuration file.
Add a new IEC 61850 and UCA 2.0 master configuration to an SMP configuration file.
Modify an existing IEC 61850 and UCA 2.0 master configuration in an SMP configuration
file.
Validate the IEC 61850 and UCA 2.0 slave and master configuration.
Add new connections for the IEC 61850 and UCA 2.0 components.
Modify an existing connection used by IEC 61850 or UCA 2.0 components.
Create new templates for IEC 61850 and UCA 2.0 master configurations.
Create new templates for UCA 2.0 master bricks.
Create new templates for IEC 61850 slave configurations.
Modify existing IEC 61850 and UCA 2.0 templates.
Validate the IEC 61850 and UCA 2.0 slave and master templates.
1.1.2 Installing 61850 Config

61850 Config is automatically installed by the SMP Tools installation program.
61850 Config User Guide •1

1.2 61850 Config
1.2.1 Protocol Overview
1.2.1.1 IEC 61850 and UCA 2.0
UCA 2.0 (Utility Communications Architecture, version 2) and IEC 61850 are a standardized
communications protocol that allows electric utilities to use compatible devices originating from
various manufacturers. This interoperability is a significant factor in helping electric utilities
reduces their operating costs. What distinguishes UCA 2.0 and IEC 61850 from other protocols is
its object-oriented approach to modeling the devices in the electrical power industry (protection
relays, measures, etc.).
1.2.1.2 GOMSFE
GOMSFE (Generic Object Models for Substation and Feeder Equipment) is standardized model of
devices in the electrical power industry.
1.2.1.3 UCA 2.0 References

Utility Communications Architecture (UCATM) Version 2.0
IEEE-SA TR 1550-1999, Volume 1, November 1999.
Utility Communications Architecture (UCATM) Version 2.0
IEEE-SA TR 1550-1999, Volume 2, November 1999.
Utility Communications Architecture 2.0, Generic Object Models for Substation & Feeder
Equipment (GOMSFE)
KC Associates, Version 0.92, May 2001.
1.2.1.4 IEC 61850 References

IEC 61850-7-1 {Ed.1.0}, Communication networks and systems in substations - Part 7-1: Basic
communication structure for substation and feeder equipment - Principles and models.
communication structure for substation and feeder equipment - Abstract communication service
interface (ACSI).
communication structure for substation and feeder equipment - Common data classes.
communication structure for substation and feeder equipment - Compatible logical node classes
and data classes.
2• 61850 Config User Guide

1.2.2 Systems Overview
1.2.2.1 The IEC 61850 Slave Component
The slave component of protocol IEC 61850 allows you to group together all data points defined
in the SMP as IEC 61850 "logical devices", "logical nodes" and "common data classes".
61850 Config lets you configure the following IEC 61850 features:
Define URCBs and BRCBs for reporting by exception.
Set the deadband value of analog points.
Configure a Select command on a data point.
Configure an Operate command on a data point.
Retrieve information about the system.
Validate the architecture.
Create a slave template for the entire slave, "logical device" or "logical nodes".
Instantiate a slave template to speed up the configuration.
1.2.2.2 The UCA 2.0 Slave Component

The slave component of protocol UCA 2.0 allows you to group together every data point defined
in the SMP as a UCA 2.0 "logical device" of type "Basic RTU", as proposed in standard
GOMSFE 0.92.
61850 Config lets you configure the following UCA 2.0 features:
Define BasRCB for reporting by exception.
Set the deadband value of analog points.
Configure a Select command on a data point.
Configure an Operate command on a data point.
Retrieve information about the system.
Validate the architecture.
61850 Config helps you adhere to the GOMSFE models when you create a UCA 2.0 architecture
by:
giving you the opportunity to use a wizard that guides you during the creation of a new logical
device;
creating GOMSFE bricks and common classes such as GAIN, GIND, GSPT, GCTL, DI, AI,
and BasRCB.
You can also make your logical device from scratch and explore the capabilities of protocol UCA
2.0 in greater depth.
1.2.2.3 The IEC 61850 Master Component

The master component of protocol IEC 61850 allows you to access IEC 61850 compatible
devices. With 61850 Config, you can integrate IEC 61850 devices into your SMP configuration
by:
Downloading the device configuration and automatically configuring the resulting RTDX
points and available reports in a single operation.

Refreshing the device configuration to automatically adapt the master component to a change
in the device configuration.
Associating the common data classes from the device with the data points in the SMP.
Subscribing to the available reports in the device.
Creating new master templates, compatible with SMP Config, corresponding to device
configurations.
Instantiating a master template to quickly add an IEC 61850 device to your SMP
configuration file.
1.2.2.4 The UCA 2.0 Master Component

The master component of protocol UCA 2.0 allows you to access UCA 2.0 compatible devices.
With 61850 Config, you can integrate UCA 2.0 devices into your SMP configuration by:
Downloading device configurations.
Creating new data points in the SMP.
Associating data points in the SMP with device input/output points.
Subscribing to the available reports in the device.
Creating multiple scanning cycles to periodically retrieve the device data.
Creating new master templates, compatible with SMP Config, corresponding to device
configurations.
Instantiating a master template to quickly add a UCA 2.0 device to your SMP configuration
file.
Creating new brick templates, to take advantage of the common brick models in different
UCA 2.0 devices.
Instantiating brick templates to speed up the device configuration process.

2 Using 61850 Config
2.1 Preliminary Requirements

61850 Config can be used to configure IEC 61850 and UCA 2.0 masters, slaves or connections.
You require an SMP configuration file created by SMP Config. Using SMP Config, you create
the file and add the masters and slaves that will be used by the SMP. You specify a connection to
all master protocol components created in SMP Config, in order to allow 61850 Config to
retrieve the published points. The points published by the masters are the source of the IEC 61850
and UCA 2.0 slave component points.
2.2 Starting 61850 Config

To start 61850 Config:
In the SMP Manager main screen, click on an SMP gateway.
In the Tools menu, click 61850 Config.
The 61850 Config’s main screen appears, showing two empty panes. As you work with the
application, the left pane will eventually display the architecture of the IEC 61850 and UCA 2.0
components configuration, while the right pane will display the properties (if any) of the item
selected in the left pane, as illustrated below.

Before you can do anything, you need to open an SMP configuration file created by SMP Config.
To do this:
In the File menu, click Open.
Note that you can open the same file in 2 different instances of 61850 Config. However, if you
make changes the second time you open the file, you will be asked to save the file under a new
name. This avoids collision in file editing and reduces the possibility of losing data and wasting
time.
2.3 Creating a New Slave Connection

To create a new slave connection:
In the left pane, under Connections, click Slave Connections.
In the Insert menu, point to Connection, and then click Slave.
To rename the slave connection:

In the left pane, click on the slave connection.
In the Edit menu, click Rename.
To configure the slave connection:

In the left pane, click on the slave connection.
In the right pane:

For an SMP 8-40, select the Board in the drop-down list.
For all other SMP models, the only choice is Board A.
Enter the Port number of the SMP or communication server.
2.4 Creating a New IEC 61850 Slave Configuration

from Scratch
2.4.1 Creating a Slave Component
To create a new IEC 61850 slave component:
In the left pane, click on IEC 61850 Slaves.
In the Insert menu, click Slave.
To rename the slave component:

In the left pane, click on the slave component.
To configure the slave component:

In the left pane, click on the slave component.
In the right pane:
Using the Connection drop-down list, choose the appropriate connection.
Note that only the available slave connections are shown.

The other settings can maintain their default values for a basic configuration. For an advanced
configuration, refer to the table below for a description of the settings.
Setting Description
Connection Indicates the connection that is associated with the slave.
Vendor Vendor name, for informative purposes. This setting is optional.
Model Component model, for informative purposes. This setting is optional.
Revision Component revision, for informative purposes. This setting is optional.

Setting Description
Client Time The time zone at which the client’s clock is set.
Zone
Some clients may expect to receive data changes or event files that are timestamped
using local time information, rather than UTC time. Therefore, if the client’s clock
is adjusted to the local time zone setting, the slave’s configuration must be set
accordingly so it can adjust the timestamps to the local time. If the slave is
configured to accept clock synchronization request, the same time zone setting will
be used to convert the client’s local time information to UTC time.
If the client’s clock is adjusted for daylight savings, the Auto Adjust DST setting
must also be enabled (see below).
By default, SMP Config assumes that the client’s clock is set to use UTC time,
which corresponds to the GMT time zone modifier setting.
Auto Adjust Indicates that the client’s clock is adjusted for daylight savings.
DST
This setting is used in conjunction with the Device Time Zone setting, to convert
timestamps to transmit from UTC to local time.
It is also used on the reception of clock synchronization request, to convert the

client’s local time information to UTC time.
Inactivity The number of seconds the component will wait after the last valid data link layer
Timeout frame is received, before resetting the communications link.
Control Enabled A checkmark enables control operations by the master on output points.
Integrity Report The number of milliseconds to wait before verifying whether an integrity report is
Scan Interval to be sent.
Max Connection Time to wait, in seconds, for a master component’s initial general interrogation
Delay scan completed notification.
This allows slave components to wait before allowing connections from a master,
until master components (those configured to do so) either complete their first
general interrogation scan, or time out if the communication cannot be established.
Thus, after an SMP restart, the master does not see any useless transitions resulting
from system initialization.
MMS Message The maximum number of bytes for the MMS message used to communicate with
Size the master. This setting is negotiated during the association, and whichever MMS
message size is smaller - slave or master - is used.
TPDU Size The size of the packet to be used in the transport layer.
Max In The maximum number of incoming requests. This setting is negotiated during the
Requests association, and whichever maximum number of incoming requests is smaller -
slave or master - is used.
Max Out The maximum number of outgoing requests. This setting is negotiated during the
Requests association, and whichever maximum number of outgoing requests is smaller -
Max Request The maximum number of variables included in a single request (read, write,
Variables report).

Setting Description
Request The number of milliseconds to wait for the master response to the previous request.
Timeout
2.4.2 Adding Clients to a Slave Component

To add a client to a slave component:
In the left pane:
Expand the slave component to which you want to add a client.
Click on Clients (TPAA).
In the Insert menu, click Slave Tpaa.
To configure the slave Tpaa:

In the left pane, click on the slave Tpaa you have just created.
The right pane displays the properties of the Tpaa.
In most cases, you can use the default value. For advanced configuration, refer to the table below
for a description of the settings.
Setting Description
AP Title Client application process title. A string consisting of at most 16 space-separated

entries. Used for validation in the ISO stack.
Range: first entry: 0 or 1
second entry: 0 to 39
remaining entries: 0 to 32,767
AE Qualifier Client application-entity qualifier of the application process. Used for validation in
the ISO stack.
Presentation Client presentation layer selector. A string consisting of at most 4 space-separated

Selector entries. An entry represents a byte. Used for validation in the ISO stack.
Range: all entries: 00 to FF
Session Selector Client session layer selector. Used for validation in the ISO stack.
Transport Client transport layer selector. Used for validation in the ISO stack.
Selector
2.4.3 Adding Files to a Slave Component

To add files to a slave component:
In the left pane:
Expand slave component to which you want to add files.

Click on Files.
In the Insert menu, click Slave File.
To configure the slave file:

In the left pane, click on the slave file you have just created.
In the right pane, enter the Directory information. If the path entered is a file, only this file
will be published by the slave; if it’s a directory, all the files in the directory will be published
by the slave.
2.4.4 Adding a Logical Device to a Slave Component

To add a logical device to a slave component:
In the left pane, click on the slave component under which you want to add a logical device.
In the Insert menu, click Slave Logical Device.
2.4.5 Adding a Logical Node to a Logical Device

To add a logical node to a logical device:
In the left pane, click on the logical device under which you want to add a logical node.
In the Insert menu, click Slave Logical Node.
2.4.6 Adding a Common Data Class to a Logical Node

To add a common data class to a logical node:
In the left pane, click on the logical node under which you want to add a common data class.
In the Insert menu, point to Slave Common Data Class, and then click the desired common
data class.
To configure the common data class:

In the left pane, click on the common data class you have just created.
In the right pane:
In the Attributes grid:
Click the Present checkbox to add or remove an attribute.
Select the source of the attribute, in the Source drop-down list.
Enter the Value of the attribute, if the source is set to "Local".
Click the Read-Only checkbox to set or remove the read-only attribute.
For additional information about the Attributes grid, see "Editing Common Data
Class and Control Block Properties", page 13.
In the I/O List grid, click on the browse button (…) of the first point.
The RTDX Point Selection dialog box appears, so that you can identify which RTDX data point
to use as reference to set the value of the point on which you clicked.
10 • 61850 Config User Guide

The dialog contains the following boxes and buttons:
Object Description
List of RTDX data points Displays the list of RTDX data points from which you can choose.
Group data points Specifies whether or not the data points are to be grouped together.
Unless you put a checkmark this checkbox, all dialog items below the
checkbox will be unavailable.
With a common beginning Specifies that the data points are to be grouped together by the starting
characters of their name, for display in the list of RTDX points.
With a common ending Specifies that the data points are to be grouped together by the trailing
characters of their name, for display in the list of RTDX points.
Are delimited by the States that each data point name has the specified delimiting character,
character ... in position ... and that you are interested in the nth occurrence of the delimiter. If your
data point names contain 3 separate underscores as delimiters, for
example, and you specify a position of 2, you are referring to the second
underscore. Thus, 61850 Config will group together data points that
have a common name preceding the second underscore or following the
second underscore, depending on whether you asked for grouping by
names with a common beginning or a common ending.
Have a fixed length of ... Specifies that 61850 Config is to look at the specified number of
characters characters. If you enter a value of 7, for example, 61850 Config will
group together data points that have names with the same 7 starting or
trailing characters, depending on whether you asked for grouping by
names with a common beginning or a common ending.
Select Selects the RTDX data point and closes the dialog.
Click on an RTDX point in the list.

Click the Select button of the dialog box.
The name of the RTDX point gets added to the Reference column.
61850 Config User Guide • 11

Repeat the process for each point in the I/O List.
2.4.7 Adding a Control Block to a Logical Node

To add a control block to a logical node:
In the left pane, click on the logical node under which you want to add a control block.
In the Insert menu, point to Slave Control Block, and then click the desired control block.
To configure the control block:

In the left pane, click on the control block you have just created.
In the right pane:
In the Attributes grid:
Enter the Value of the attribute, if the source is set to "Local".
Click the Read-Only checkbox to set or remove the read-only attribute.
For additional information about the Attributes grid, see "Editing Common Data Class and
Control Block Properties", page 13.
2.4.8 Adding a Dataset to a Logical Node

To add a dataset to a logical node:
In the left pane, click on Datasets under the logical node under which you want to add a
dataset.
In the Insert menu, click Slave Dataset.
To add a common data class to a dataset:

In the left pane, click on the dataset you have just created.
In the right pane:
Click Add to add an existing common data class to the dataset.
The Node Selection dialog box appears.

Click on the common data class you want to add.
Click the Select button to add the common data class to the list.
To remove a common data class from a dataset:

In the left pane, click on the dataset from which you want to remove a common data class.
In the right pane:
Click on the common data class you want to remove.
Click Remove to remove the common data class from the list.

2.5 Modifying an IEC 61850 Slave Configuration
2.5.1 Editing the Client Rights
Rights can be set for Files, for a logical device's GeneralLog, for logical nodes, common data
classes, and control blocks.
To edit the client rights:
In the left pane, click on the item you want to edit.
In the right pane, the Client Rights grid will be displayed at the top, showing the rights of the
clients you have defined for the slave component.
In the Rights drop-down list of a particular client, choose the rights your want to assign to the
client.
Right Description
None The item on which you clicked in the left pane is never shown or
reported, and any attempt to read the data causes an Access Denied
error.
Read Only The item on which you clicked in the left pane is shown to the client and
can be reported, but cannot be edited.
Read/Write The item on which you clicked in the left pane is shown to the client and
can be reported. A value can be written, but a control operation is not
permitted.
All (Read/Write/Delete) The item on which you clicked in the left pane is shown to the client and
can be reported. A value can be written, and the item on which you
clicked (GeneralLog or file) can be deleted.
All (Read/Write/Command) The item on which you clicked in the left pane is shown to the client and
can be reported. A value can be written, and a control operation is
permitted.
2.5.2 Editing Common Data Class and Control Block Properties

You can edit the properties of common data classes and control blocks.
To edit these properties:
In the left pane, click on the common data class or control block you want to edit.
The right pane displays the properties of the item on which you clicked.
Use the Attributes grid to edit the properties of the item on which you clicked in the left
pane.
2.5.2.1 Present
The Present property indicates whether or not this attribute will exist. You cannot change this
setting for a mandatory attribute or for a non-61850 attribute.
Select or clear the checkbox, depending on whether or not you want the attribute to exist.

2.5.2.2 Source
This Source property indicates the source data for the attribute. For a common data class, the
source can be edited only for the attribute that represents the key value (stVal, mag, etc.). Any
change to the source of the attribute will automatically change the source of related attributes. For
example, if you change the source for the stVal attribute, the source for the q, t and d attributes
will automatically change to the same source. For a control block, the source cannot be edited and
is always local because a control block is not related to RTDX data points.
Click on the source in the drop-down list.
Source Description
Local The value of the point is local to the slave.
StVal, Mag, The value of the point is related to the value of an RTDX data point. See I/O List,
etc. below.
2.5.2.3 Value
If the source is local, you can normally set the static value of the attribute. However, for some
attributes, the value cannot be edited because it would not be logical to do so or because the value
is derived from that of another attribute. For example, for the MV common data class, the
instMag.f value cannot be edited because it automatically derives its value from mag.f, which can
be edited. Some of these values are only informative, while others influence the behavior of the
common data class or control block. db, for example, is the deadband and will be applied in the
slave, to the corresponding input points of the common data class. Other values consist of the
presence or absence of a checkmark used to specify, for example, whether or not a particular
option is to be used in a report. If no value appears in the grid and the field cannot be edited, and
then there is no default value applicable to the attribute.
2.5.2.4 Specific Attribute Information
Attribute Description
Simulated Control This is a non-61850 attribute. For Select, Operate and Direct Operate
Confirmation commands, you can ask the master to simulate the confirmation without
actually waiting for confirmation from the real device. This attribute exists only
with control common data classes.
d This is the description of the common data class. If the source is not local, you
can choose one of the following values in the Value drop-down list:
Description or Name. This will indicate whether the description or name of the
RTDX data point will be used to describe the common data class.
DatSet This attribute represents the dataset associated with the control block. The
Value column contains a drop-down list of all the datasets in the logical node to
which the control block belongs. "Empty" means that there is no dataset
associated with the control block; if you set the value to "Empty", you will
generate a validation error when you save the file.

2.5.2.5 I/O List
The bottom grid contains the information about the RTDX data points that are used as source
values for the common data class or control block.
To set a reference to the RTDX point:
Click on the browse (…) button.
The RTDX Point Selection dialog box appears (refer to "Adding a Common Data Class to a
Logical Node", page 10).
Click on the RTDX data point you want to associate with this attribute.
2.5.3 Deleting an Item

You can delete a client, file, logical device, logical node, common data class or control block.
To delete an item:
In the left pane, click on the item you want to delete.
In the Edit menu, click Delete.
2.5.4 Renaming an Item

You can rename a client, file, logical device, logical node, common data class or control block.
Note that this operation is subject to certain validation rules.
To rename an item:
In the left pane, click on the item you want to rename.
2.5.5 Duplicating a Logical Device

You can save time by duplicating a logical device within a particular slave component.
To do this:
Click on the logical device you want to duplicate.
In the Edit menu, click Copy.
Click on the slave component to which the logical device belongs.
In the Edit menu, click Paste.
2.6 Creating a New IEC 61850 Slave Configuration

Template
With 61850 Config, you can create template files to quickly configure logical devices and logical
nodes of the same model.

2.6.1 Using Aliases
When you create a template, you will assign aliases to the data point names of your devices so that
the template will contain generic data point names. When you subsequently instantiate logical
devices from the template, you will resolve the aliases in order to assign the required names to the
data points. This mechanism, which saves a lot of time and effort, can best be understood by an
example.
Suppose that the slave subscribes to the following data points:
Maple_SEL387_025_F1_IA
Maple_SEL387_025_F1_IB
Maple_SEL387_025_F1_IC
This nomenclature makes it easy to recognize that the points belong to the Schweitzer SEL387
relay located on feeder 1, in the 25 KV area of a substation called Maple, and that they represent
the 3 phases of the current.
If you assigned aliases to "Maple", "SEL387", "025" and "F1", the data points would now have
names such as:
%substation%_%device%_%voltage%_%feeder%_IA
%substation%_%device%_%voltage%_%feeder%_IB
%substation%_%device%_%voltage%_%feeder%_IC
These names would be saved to the template.
Suppose you now used the template to instantiate the data points to 2 other SEL387 devices
located on feeders 2 and 3 respectively. For the device located on feeder 2, you would resolve the
aliases to "Maple", "SEL387", "025" and "F2". For the device located on feeder 3, you would
resolve the aliases to "Maple", "SEL387", "025" and "F3".
The following data points would be added to the current configuration:
2.6.2 Creating the Template

To create a slave configuration template:
Open a configuration file that has a slave containing one or more devices for which you want
to create a template.
In the left pane, click on the slave whose configuration you want to save as a template.
In the File menu, click Save As Template.
The Define Aliases dialog box appears.

Object Description
Alias Delimiter Use this text box to enter the character that will serve as a delimiter for
the aliases.
Do not enter a character that can be found in the RTDX data point
names of the file that is currently open.
Replace Click this button in order to replace some text in the data point names
shown in the I/O Name list with other text that will serve as an alias.
Save Click this button to save the template on disk.
Click the Replace button to define an alias.

The Replace dialog box appears.
Object Description
Find what Enter the text you want to replace in the names of the data points that
appear in the I/O Name list of the Define Aliases dialog.
Replace with Type the replacement text between the delimiter characters.

Object Description
Replace All Click this button to change the names of all the RTDX data points in the
slave template. The change is not applied to the names in the original
file.
In the Find what text box, enter the text to be replaced.

In the Replace with text box, enter the replacement text (alias).
Click Replace All.
The dialog closes and the Define Aliases dialog reappears.
Click the Replace button and repeat the above steps for each alias you want to add.
To finish, click the Save button of the Define Aliases dialog.
A standard Windows Save dialog box appears.
Enter the new template file name, and click Save.
The saved file contains a template of the slave on which you clicked.
2.7 Adding IEC 61850 Slave Configuration

Template Data to an Existing IEC 61850 Slave
The fastest and easiest way to create a complete IEC 61850 slave component is to instantiate the
slave, or a part of it, from a template. The template, which typically resides in your SMP
configuration file, has been created with 61850 Config (see "Creating a New IEC 61850 Slave
Configuration Template", above).
To instantiate slave component data from a template:
In the left pane, click on the slave to which you want to add data.
In the Tools menu, click New Instance from Template.
A standard Windows Open dialog box appears.
Click on the template file you want to instantiate, and click Open.
The Resolve Aliases dialog box appears.

Object Description
Alias List Use this list to resolve the aliases by typing the text that is to replace the
alias in the data point names listed in the I/O List portion of the dialog.
Logical Device List This list shows the logical devices that exist in the template. You can
assign a new name to each logical device in the list by choosing a
replacement name in its New Name drop-down list. The drop-down list
includes not only a new name for the logical device, but also the list of
all the logical devices in the template. If you choose a new name in the
drop-down list, the data from the currently selected logical device will
be instantiated to a logical device with the new name you just assigned.
If you choose another logical device in the drop-down list, the data from
the currently selected logical device will be instantiated to the logical
device that you chose in the drop-down list.
I/O List The I/O Name column shows all the RTDX data point names that are
used, while the Object Ref column shows the objects that use the data
points. If the RTDX data point name is displayed in red, its aliases have
not yet been resolved.
OK Click this button to have the template data instantiated in the current file,
with the options chosen in the alias and logical device lists.
In the Alias List, click in the Text column of each alias, and enter the text to resolve the alias.
In the Logical Device List, click in the New Name column of each logical device to choose
the logical device to which the data will be instantiated.
Click OK.
Each logical node from a logical device in the template file will be added, in the current
configuration, to the logical device you chose in the dialog. If a logical node already exists in the
current configuration, a number will be added to its name to distinguish it from the existing node.

For example, the logical device in the current configuration would now include logical nodes
NODE and NODE1. Note, however, that logical nodes LLN0 and LPHD will not be instantiated
from the template to the current configuration.
2.8 Creating a New UCA 2.0 Slave Configuration

Using the Wizard
You can create a new UCA 2.0 slave configuration in one of two ways:
using the wizard (below);
from scratch (see "Creating a New UCA 2.0 Slave Configuration From Scratch", page 22).

To create a new UCA 2.0 slave component:
Click on UCA 2.0 Slaves.

In the left pane, click on the slave component you have just created.
In the right pane:
Enter the Vendor, Model and Revision information.
Using the Connection combo box, choose the appropriate connection.
Note that only the available connections are shown.

The New Logical Device dialog box appears.
Enter the name of the new logical device.
Click either the Manual or the Automatic button of the dialog box, depending on whether
you want to create bricks manually or automatically.
2.8.2.1 Adding Bricks Automatically

If you click the Automatic button of the New Logical Device dialog box, the wizard takes the
RTDX points published by all the protocol masters in the SMP configuration file, and creates a
logical device based on a basic RTU defined by GOMSFE. It splits the RTDX points into four
categories: analog inputs are placed in GAIN (Generic Analog Input), binary inputs are placed in
GIND (Generic Indicator), analog outputs are placed in GSPT (Generic Set Point), and binary
outputs are placed in GCTL (Generic Control). Note that a brick can have a maximum of 32
points.
The new logical device now appears in the left pane, under the slave component on which you
clicked.

2.8.2.2 Adding Bricks Manually
If you click the Manual button of the New Logical Device dialog box, the New Logical Device -
Add Bricks dialog box appears. Initially, the list of currently added bricks is empty. As you add
bricks, they are displayed in the list, as shown below.
Object Description
GAIN... If you click one of these buttons, the RTDX Point Selection dialog box
GIND... appears, so that you can choose which RTDX data points you want to
GSPT... add to the brick.
GCTL...
Bricks currently added Each time you select a group of RTDX points using the RTDX Point
Selection dialog, the points appear in this list, under the type of brick
you specified.
Remove This button is used to remove bricks or RTDX points from the list.
To add a brick and choose the RTDX points you want to include in the brick:
Click the GAIN, GIND, GSPT or GCTL button.
The RTDX Point Selection dialog box appears (see "Adding a Common Data Class to a Logical
Node", page 10).
Once you select the RTDX Point, the New Logical Device - Add Bricks dialog box is displayed
once again, and the newly added brick is listed in the dialog box.

Repeat the process as many times as required, until you have added all the bricks you want to
add.
To remove a brick:
Click on the brick in the New Logical Device - Add Bricks dialog box.
Click the Remove button.
When you have finished creating bricks:

Click the Finish button of the New Logical Device - Add Bricks dialog box.
The new logical device now appears in the left pane, and contains all the bricks you added using
the above process.
2.9 Creating a New UCA 2.0 Slave Configuration

From Scratch
You can create a new UCA 2.0 slave configuration in one of two ways:
from scratch (below);
using the wizard (see "Creating a New UCA 2.0 Slave Configuration Using the Wizard", page
20).

To create a new UCA 2.0 slave component:
Click on UCA 2.0 slaves.

In the left pane, click on the slave you have just created.
In the right pane:
Enter the Vendor, Model and Revision information.
Using the Connection combo box, choose the appropriate connection.

The New Logical Device dialog box appears (see "Creating a New UCA 2.0 Slave Configuration
Using the Wizard", page 20).
Enter a name for the logical device.
Click on the Manual button of the dialog box.

The New Logical Device - Add Bricks dialog box appears (for a screenshot of the dialog, see
"Adding Bricks Manually", page 21).
If you choose to add bricks immediately, turn to "Adding Basic Building Bricks under a
DeviceModel", page 24).
Otherwise, click on the Finish button of the dialog box.
This creates a logical device with two empty folders: DeviceModel and Datasets.
At this point, you can create a UCA 2.0 architecture by using the procedures for:
Adding a Folder under a DeviceModel
Adding a Data Point under a DeviceModel
Adding a Dataset to a Datasets Folder
Adding Basic Building Bricks under a DeviceModel
Adding a Common Class under a DeviceModel
2.9.3 Adding a Folder under a DeviceModel

You can add a folder at any level, under the DeviceModel of a slave component.
To add a folder under an existing folder:
Click on the folder under which you want to add a folder.
In the Insert menu, click Slave Node.
2.9.4 Adding a Data Point under a DeviceModel

You can add a data point at any level, under the DeviceModel of a slave component.
A data point can have one of the following sources: a local value such as deadband, a system value
such as time, or an RTDX point attribute.
To add a data point to an existing folder:
Click on the folder to which you want to add a data point.
In the Insert menu, click Slave Point.
2.9.5 Adding a Dataset to a Datasets Folder

A dataset is a list of references to data points or folders under the DeviceModel of the logical
device. Typically, you reference a data point or a group of data points within a folder, because
they have properties that you want to apply to some other data points.
To add a dataset to a Datasets folder:
Click on the Datasets folder.
In the Insert menu, click Slave Dataset.
The right pane of the main screen displays a list of dataset references. Initially, the list is empty.
To add a reference:
Click on the Add button, in the right pane.
The Node Selection dialog box appears, showing all the folders and data points under the device
model.

Click on the data point or folder you want to add as reference.
In the right pane, the item you just added will appear in the list of dataset references.
Note that you can add a maximum of 32 references.
To remove a reference:
Click the Remove button, in the right pane.
2.9.6 Adding Basic Building Bricks under a DeviceModel

You can easily add a brick under a DeviceModel.
2.9.6.1 GAIN
To add a GAIN:
Click on the DeviceModel under which you want to add the brick.
In the Insert menu, point to Slave Basic Building Bricks, and then click (GAIN) Generic
Analog Input.
Node", page 10).
Click on the RTDX points you want to include in the brick.
Note that you will only have the choice of analog input points, and you can associate a maximum
of 32 points with the brick.
This operation automatically creates the corresponding dataset for the report and adds it to the
Datasets folder.
2.9.6.2 GIND
To add a GIND:
In the Insert menu, point to Slave Basic Building Bricks, and then click (GIND) Generic
Indicator.
Node", page 10).
Note that you will only have the choice of binary input points, and you can associate a maximum
Datasets folder.
2.9.6.3 GCTL
To add a GCTL:

In the Insert menu, point to Slave Basic Building Bricks, and then click (GCTL) Generic
Control.
Node", page 10).
Note that you will only have the choice of binary output points, and you can associate a maximum
Datasets folder.
2.9.6.4 GSPT
To add a GSPT:
In the Insert menu, point to Slave Basic Building Bricks, and then click (GSPT) Generic
Set Point.
Node", page 10).
Note that you will only have the choice of analog output points, and you can associate a maximum
Datasets folder.
2.9.7 Adding a Common Class under a DeviceModel

61850 Config allows you to add some useful common GOMSFE classes quickly and easily. You
can add a common class to any folder under a DeviceModel.
2.9.7.1 (DI) Device Identity

To add a DI folder:
Click on the parent folder.
In the Insert menu, point to Slave Common Class, and then click (DI) Device Identity.
2.9.7.2 (AI) Analog Input

To add an AI folder:
In the Insert menu, point to Slave Common Class, and then click (AI) Analog Input.
Node", page 10).
Click on the RTDX point you want to associate with this AI.
The raw and float values, the quality and the timestamp of the selected RTDX point, will be
attributed to certain points in this AI.

Click on a reference point, to indicate the value of the deadband.
Note that you will only be able to select points with a UCA type equal to INT16U. If you don’t
choose a reference point, there will be no deadband attributed to this AI.
2.9.7.3 (SI) Status Input Single Bit

To add an SI folder:
In the Insert menu, point to Slave Common Class, and then click (SI) Status Input Single
Bit.
Node", page 10).
Click on the RTDX point you want to associate with this SI.
The state, the quality and the timestamp of the selected RTDX point will be attributed to the points
in this SI.
2.9.7.4 (AO) Analog Output

To add an AO folder:
In the Insert menu, point to Slave Common Class, and then click (AO) Analog Output.
Node", page 10).
Click on the RTDX point you want to associate with this AO.
The raw and float values, and the timestamp of the selected RTDX point, will be attributed to the
points in this AO.
Click on a reference point, to indicate the state of the selected point.
Note that you will only be able to select points with a UCA type equal to BOOL. If you don’t
choose a reference point, there will be no state attributed to this AO.
2.9.7.5 (BO) Binary Output

To add a BO folder:
In the Insert menu, point to Slave Common Class, and then click (BO) Binary Output.
Node", page 10).
Click on the RTDX point you want to associate with this BO.
The state and timestamp of the selected RTDX point will be attributed to the points in this BO.

Click on a reference point, to indicate how long the pulse will stay ON.
Note that you will only be able to select points with a UCA type equal to INT32U. If you don’t
choose a reference point, there will be no On duration attributed to this BO.
The Node Selection dialog box appears once again.
Click on a reference point, to indicate the state of the selected point.
Note that you will only be able to select points with a UCA type equal to BOOL. If you don’t
choose a reference point, there will be no state attributed to this BO.
2.9.7.6 (ACF) Analog Configuration

To add an ACF folder:
In the Insert menu, point to Slave Common Class, and then click (ACF) Analog
Configuration.
Node", page 10).
Click on the RTDX point you want to associate with this ACF.
The scale, offset and unit of the selected RTDX point will be attributed to the points in this ACF,
and another point will contain the deadband value.
2.9.7.7 (CCF) Control Configuration

To add a CCF folder:
In the Insert menu, point to Slave Common Class, and then click (CCF) Control
Configuration.
2.9.7.8 (SBOCF) SBO Configuration

To add an SBOCF folder:
In the Insert menu, point to Slave Common Class, and then click (SBOCF) SBO
Configuration.
2.9.7.9 (d) Description

To add a d folder:
In the Insert menu, point to Slave Common Class, and then click (d) Description.
Node", page 10).
Click on the RTDX point you want to associate with this d.

The description of the selected RTDX point will be attributed to the points in this d.
2.9.7.10 (basRCB) Basic Report Control Block

To add a basRCB folder:
In the Insert menu, point to Slave Common Class, and then click (basRCB) Basic Report
Control Block.
Click on dataset, as reference.
2.10 Modifying a UCA 2.0 Slave Configuration

You can modify a UCA 2.0 slave configuration.
The modifications you can make are discussed in the following sections:
"Editing Data Point Properties"
"Copying a Folder or a Data Point"
"Cutting a Folder or a Data Point"
"Pasting a Folder or a Data Point"
"Deleting a Folder or a Data Point"
"Renaming a Folder or a Data Point"
2.10.1 Editing Data Point Properties

You can edit the properties of UCA 2.0 data points.
To edit a data point:
In the left pane, click on the data point you want to edit.
The right pane displays the properties of the data point.
2.10.1.1 Source
The source indicates the type of information you want to associate with the data point.
Click on the source in the drop-down list.
Source Description
RTDX The value of the point is related to the value of an RTDX point.
Local The value of the point is local to the slave.
System The value of the point is related to specific information about the system.

2.10.1.2 RTDX Name
If the source is RTDX, you must select an RTDX point.
To do this, proceed as follows:
Click the browse (…) button.
Node", page 10).
Click on the RTDX point you want to associate with this data point.
2.10.1.3 Function
If the source is RTDX, you can associate a function with the data point.
Click on the function in the drop-down list.
Function Constraints Description
None There is no function associated with the point.
Select Source = RTDX Perform a Select when the point is read.

I/O Type = AO or BO
Operate Source = RTDX Perform an Operate when the point is written.

I/O Type = AO or BO
Direct Source = RTDX When the point is written, perform an Operate

Operate without a Select, even if the Select is necessary.
I/O Type = AO or BO
2.10.1.4 Value
If the source is RTDX, you must indicate which attribute of the RTDX point you want to associate
with the data point. If the source is System, you must choose which information you want to
retrieve from the system. If the source is Local, you can assign a default value to the data point.
Click on the function in the drop-down list.
Value Constraints Description
None Source = RTDX No attribute.

Function = SELECT
Description Source = RTDX The description attribute of the RTDX point.
Float Source = RTDX The float attribute of the RTDX point.

I/O Type = AI or AO
Offset Source = RTDX The offset attribute of the RTDX point.

I/O Type = AI or AO
Quality Source = RTDX The quality attribute of the RTDX point.

Value Constraints Description
Raw Source = RTDX The raw attribute of the RTDX point.

I/O Type = AI or AO
Scale Source = RTDX The scale attribute of the RTDX point.

I/O Type = AI or AO
Time Source = RTDX The time attribute of the RTDX point.
Unit Source = RTDX The unit attribute of the RTDX point.

I/O Type = AI or AO
State Source = RTDX The state attribute of the RTDX point.

I/O Type = BI or BO
Time Source = System The system time.
Default value Source = Local A default value that you specify.
2.10.1.5 UCA 2.0 Type

You must attribute a UCA 2.0 type to your data point.
Click on the UCA 2.0 type in the drop-down list.
The UCA 2.0 Slave supports the following types:
UCA 2.0 Types Supported
BOOL ENUM8 INT16S
BSTR1 ENUM16 INT16U
BSTR8 FLT32 INT32S
BSTR16 FLT64 INT32U
BSTR32 IDENT VSTR8
BTIME4 INT8S VSTR16
BTIME6 INT8U VSTR32
2.10.1.6 Reference
Some points may reference other points in the UCA 2.0 architecture.
To select a reference point, proceed as follows:
Click the browse (…) button of the appropriate property (State, for example).

Click on the data point you want to use as reference for the selected property.
For example, if you are looking for a State reference, you must click on a Boolean data point.
Note that you can only refer to a data point on the same logical device.
Reference Constraints Description

Type
Deadband Source = RTDX The deadband value.

I/O Type = AI or AO
Value = Raw
UCA 2.0 type of the reference =
INT16U
State Source = RTDX The state of the selection.

I/O Type = AO or BO
Function = SELECT
BOOL
OnDur Source = RTDX The amount of time the pulse stays ON.
I/O Type = BO
Value = State
INT32U
Dataset For the dataset within a basRCB The reference to a dataset.
2.10.1.7 Write
Indicates whether you have write access to the data point.
Select or clear the checkbox, depending on whether or not you have write access to the data
point.
2.10.1.8 Simulated Control Confirmation

For Select, Operate and Direct Operate commands, you can ask the master to simulate the
confirmation without actually waiting for confirmation from the real device.
Select or clear the checkbox, depending on whether or not you want the master to simulate a
confirmation.
2.10.1.9 RTDX Quality to UCA 2.0 Quality

You can convert the RTDX quality to UCA 2.0 quality.
Select or clear the checkbox, depending on whether or not you want the RTDX quality to be
converted to UCA 2.0 quality.

2.10.2 Copying a Folder or a Data Point
You can copy a folder or a data point. All references outside the copied item are set to zero. If a
report is associated with a dataset, the dataset is not copied and the reference is set to zero. It is
your responsibility to create the corresponding dataset and associate the dataset with the report.
To copy a folder or a data point:
In the left pane, click on the item you want to copy.
2.10.3 Cutting a Folder or a Data Point

You can cut a folder or a data point, and move it to another location. All references are kept.
To cut a folder or a data point:
In the left pane, click on the item you want to cut.
In the Edit menu, click Cut.
2.10.4 Pasting a Folder or a Data Point

To paste a folder or a data point that you cut or copied:
In the left pane, click on the folder in which you want to paste the folder or data point.
2.10.5 Deleting a Folder or a Data Point

You can delete a folder or a data point. Note that this operation may take a while because all
references to the deleted item must be removed.
To delete a folder or a data point:
In the left pane, click on the item you want to delete.
2.10.6 Renaming a Folder or a Data Point

You can rename a folder or a data point. Note that this operation is subject to certain validation
rules.
To rename a folder or a data point:
In the left pane, click on the item you want to rename.
2.10.7 Duplicating a Logical Device

You can save time by duplicating a logical device within a particular slave component.
To do this:
Click on the logical device you want to duplicate.
Click on the slave component.
This must be the same slave component as for the logical device you copied.

2.11 Creating a New Master Connection

To create a new master connection:
In the left pane, under Connections, click Master Connections.
In the Insert menu, point to Connection, and then click Master.
To rename the master connection:

In the left pane, click on the master connection.
To configure the master connection:

In the left pane, click on the master connection.
In the right pane:
For an SMP 8-40, select the Board in the drop-down list.
For all other SMP models, the only choice is Board A.
Enter the Port number of the device.
Enter the IP address of the device.
2.12 Creating a New IEC 61850 Master

Configuration from Scratch
2.12.1 Creating a Master Component
To create a new master component:
In the left pane, click on IEC 61850 Masters.
In the Insert menu, click Master.
61850 Config adds a virgin master component under IEC 61850 Masters and assigns it a default
name.
To rename the master component:

In the left pane, click on the master component.
To configure the master component:

In the right pane:

Using the Connection drop-down list, choose the appropriate connection.
Enter the Device prefix.
The others settings can maintain their default values for a basic configuration. For an
advanced configuration, refer to the table below for a description of the settings.
Setting Description
Connection Indicates the connection that is associated with the master.
Vendor Vendor name, for informative purposes. This represents the information about the
client, not the device. The setting is optional.
Model Component model, for informative purposes. This represents the information about
the client, not the device. The setting is optional.
Revision Component revision, for informative purposes. This represents the information
about the client, not the device. The setting is optional.
Device prefix A string used as a prefix for all the I/O point names supported by a particular
device. This prefix ensures that every I/O point name in a system is unique.
Device Time The time zone at which the device clock is set.
Zone
The device may use its internal clock to timestamp the data it transmits to the
master. Therefore, if the device’s clock is adjusted to the local time zone setting,
the master’s configuration must be set accordingly so it can adjust the timestamps
back to the UTC time. If the master is configured to synchronize the device’s clock
with its own clock, the same time zone setting will be used to convert the
SMP Gateway’s UTC time to the device’s local time.
If the device’s clock is adjusted for daylight savings, the Auto Adjust DST setting
must also be enabled (see below).
By default, SMP Config assumes that the device’s clock is set to use UTC time,
which corresponds to the GMT time zone modifier setting.
Auto Adjust Indicates that the device’s clock is adjusted for daylight savings.
DST
This setting is used in conjunction with the Device Time Zone setting, to convert
the device-reported timestamps from local time to UTC time.
It is also used for device clock’s synchronization by the master, to convert the
SMP Gateway’s current UTC time to local time.
Selection The number of milliseconds during which an execution control request can be
timeout issued after an output point has been successfully selected. If the timeout period
expires, the execution control request is refused. A value of 0 disables selection
timeout.
Request timeout The timeout value, in milliseconds, for a request to be considered unanswered.
Command The timeout value, in milliseconds, for a command to be considered unanswered.

timeout

Setting Description
Keep alive The interval, in milliseconds, at which a status request is sent by the master to keep
the connection alive.
Control enabled A checkmark indicates that the master can receive commands.
Validate A checkmark indicates that the master is to validate the configuration whenever the
configuration on connection is reset.
connection reset
Notify when Put a checkmark to activate the initial general interrogation completed notification
ready mechanism.
This mechanism allows slave components (those configured to do so) to wait
before allowing connections from a master station, until either the master
components complete their first general interrogation or until there is a timeout, if
the communication cannot be established. Thus, aster an SMP restart, the master
station does not see any useless transitions resulting from system initialization.
MMS Message The maximum number of bytes for the MMS message used to communicate with
Size the master. This setting is negotiated during the association, and whichever MMS
message size is smaller - slave or master - is used.
TPDU Size The size of the packet to be used in the transport layer.
Max In The maximum number of incoming requests. This setting is negotiated during the
Requests association, and whichever maximum number of incoming requests is smaller -
Max Out The maximum number of outgoing requests. This setting is negotiated during the
Requests association, and whichever maximum number of outgoing requests is smaller -
Max Request The maximum number of variables included in a single request (read, write,
Variables report).
Command Indicate the originator category (parameter orCat in Iec61850 standard) that will be
Originator sent with each command.
Category
Command Indicate the originator identifier (parameter orIdent in Iec61850 standard) that will
Originator be sent with each command.
Identifier
Command Check to force the device to execute a synchrocheck before any command.
Synchrocheck
Command Check to force the device to execute an interlock check before any command.
Interlock-check
Hot-Stanby Set this parameter to Standard to enable the Hot Standby SMP redundancy
Support feature. If it is set to With Link Test, the master will connect and validate the
configuration while on standby mode to accelerate the fail-over process. This
setting applies only when 2 SMPs are grouped together in a redundant
configuration.

2.12.2 Configuring the Master Automatically
The master protocol component can also be automatically configured in 2 ways: the configuration
can be downloaded directly from the device, or read from a SCL file.
To download the device configuration:
In the right pane, use the Connection drop-down list to specify the connection through which
the device can be accessed.
In the Tools menu, click Get Config.
The download operation may take a while.
To configure the master with the SCL file:

In the Tools menu, click Get Config From File.
In this case, the connection is also configured automatically, if the information is present in the
file.
Once automatic configuration is completed, the DeviceConfig (IEC 61850) folder is selected and
contains the device configuration. 61850 Config has detected the standard common data classes
and created the equivalent RTDX data points. If there were URCBs, 61850 Config has set up the
configuration such that the IEC 61850 master component will activate the URCBs once
connected. Only one URCB per dataset is automatically activated in this way.

Configuration Template
With 61850 Config, you can create template files to quickly configure devices of the same model.
To create a new master template file:
Open a configuration file that has a master containing one or more devices for which you
want to create a template.
In the left pane, click on the master whose configuration you want to save as a template.
The saved file contains a template of the master on which you clicked. The template is compatible
with SMP Config, so you can also use SMP Config to instantiate IEC 61850 master templates in
your SMP configuration file.

Configuration from a Template
The fastest and easiest way to create a complete IEC 61850 master component is to instantiate one
from a template. The template, which typically resides in your SMP configuration file, has been
created by 61850 Config (see "Creating a New IEC 61850 Master Configuration from a
Template", above).
To instantiate a master component from a template:
In the left pane, click on IEC 61850 Masters.
Click on the template file you want to instantiate, and click Open.
The Enter New Instance Information dialog box appears.
Enter the new instance name and prefix in the appropriate text boxes, and click OK.
A new master corresponding to the instantiated template is now added to the left pane, under IEC
61850 Masters.
Notes:
You can also use SMP Config to instantiate a template.
You can modify a template by opening it with 61850 Config. The configuration process
is the same as for a normal master.
2.15 Modifying an IEC 61850 Master Configuration

2.15.1 Refreshing the Configuration
In some cases, the configuration of the device may change. With 61850 Config, you can refresh
the configuration without losing current settings. Since the configuration of an IEC 61850 master
component is simple, it may be easier to delete the master, create a new one, and download the
configuration from the device. The Refresh Config option is there for advanced configurations in
the event, for example, that you rename all the RTDX data points and don’t want to lose the
settings.
To refresh the master configuration:
In the Tools menu, click Refresh Config or Refresh Config From File.
The configuration of the device will be downloaded or read again. New items will be added, and
deleted items will be deleted. Only logical nodes and logical devices will be deleted if they no
longer exist on the device. Common data classes and control blocks will remain, but without any
association with MMS points.
From this point on, you can delete unused common data classes and control blocks, and add new
ones.
To add common data classes and control blocks automatically:

In the Tools menu, click Configure Master.
This will create all the new common data classes and control blocks automatically. Already
configured items will not be modified.
To add common data classes and control blocks manually, see "Adding Common Data Classes or
Control Blocks Manually", below.
2.15.2 Adding Common Data Classes or Control Blocks Manually
Note: A good understanding of the IEC 61850 standard is required to understand this
section. This is usually reserved for advanced users.
61850 Config allows you to add common data classes and control blocks manually. The IEC
61850 standard use the MMS protocol to transmit data and define normalized structure classes for
the common data classes and control blocks. This is why we have to map the DeviceConfig (IEC
61850) tree, which contains the common data classes and control blocks, to the DeviceConfig
(MMS) tree, which contains the MMS data. This process is done automatically with the Get
Config or Configure Master command of the Tools menu, but is limited to the common data
classes and control blocks known to 61850 Config. If a device uses a new data class or a user-
defined data class, the only way to acquire this data is to map an existing common data class or
control block to the MMS structure of this new data.
For example, you can create an SAV in the DeviceConfig (IEC 61850) tree and map it to the
MMS points of an MV. Attributes instMag, q, t and d will work perfectly, but the SAV will never
receive the mag attribute with the deadband applied to it.
Before adding common data classes or control blocks manually, we recommend that you execute
the Refresh Data command. Since the values of the MMS points are not saved, this will ensure
that those MMS points have the right values for the configuration. If the Get Config or Refresh
Config command was executed during the same session, you do not have to refresh the data of the
MMS tree.
To refresh the MMS tree values:
In the Tools menu, click Refresh Data.
2.15.2.1 Adding Common Data Classes or Control Blocks from The

DeviceConfig (IEC 61850) Tree
To add a common data class or control block from the DeviceConfig (IEC 61850) tree:
In the left pane:
Expand the DeviceConfig (IEC 61850) folder.
Expand the logical device to which you want to add the item.
Click on the logical node to which you want to add the item.
In the Insert menu, click Master Common Data Class or Master Control Block and click
on the specific item you want to add.
The common data class or control block settings appear in the right pane.
To map an attribute to an MMS point:
In the right pane, click on the browse (…) button of the attribute you want to map.

The Node Selection dialog box appears, showing that portion of the DeviceConfig (MMS) tree
that is equivalent to the current logical node.
Click on the MMS node you want to map to the attribute.
Click Select.
Note: You can map attributes in a totally illogical way; the only rule is that the MMS
point must originate from the right MMS type.
If the attribute you just mapped was the main value of a common data class (stVal, setVal, mag.i
or mag.f), 61850 Config will try to map the other attributes for you. This will happen only when
the MMS points have exactly the same name as the attribute of the common data class.
For more information on the common data class and control block settings, see "Adding Common
Data Classes or Control Blocks from the DeviceConfig (MMS) Tree", below.
2.15.2.2 Adding Common Data Classes or Control Blocks from the

DeviceConfig (MMS) Tree
To add a common data class or control block from the DeviceConfig (MMS) tree:
In the left pane:
Expand the DeviceConfig (MMS) folder.
Expand the logical device to which you want to add the item.
Expand the MMS structure and click on the specific MMS point you want to map.
The MMS point settings appear in the right pane.

In the right pane, click the New button.
The Create CDC dialog box appears.
Select the CDC Type in the drop-down list.
Select the Attribute in the drop-down list.
In the CDC box, enter the name of the new common data class.
Click Create.
The dialog closes and the new common data class reference now appears in the right-pane grid.
To configure the new common data class:
Click on the common data class reference in the grid.
Click Go To.
This selects the common data class in the DeviceConfig (IEC 61850) tree and the settings appear
in the right pane.
If the attribute you just mapped was the main value of a common data class (stVal, setVal, mag.i
or mag.f), 61850 Config tries to map the other attributes for you. This occurs only when the MMS
points have exactly the same name as the attribute of the common data class.
For more information on the common data class and control block settings, see "Editing Common
Data Class or Control Block Properties", below.

2.15.3 Editing Common Data Class or Control Block Properties
To edit common data class or control block properties, proceed as follows:
In the left pane, open the appropriate logical device and logical node under the DeviceConfig
(IEC 61850) node.
Click on the common data class or control block you want to edit.
In the right pane, apply your modifications to the appropriate settings, as described in the
tables below.
2.15.3.1 Disable
The Disable property indicates whether this common data class or control block is disabled.
Mark or clear the checkbox, depending on whether or not you want this common data class or
control block to be disabled.
Notes:
If you put a checkmark, you will automatically disable all RTDX data points in the I/O
List.
If you then remove the checkmark, you will not automatically enable all RTDX points in
the I/O List.
2.15.3.2 Attributes
This list contains all the attributes of the common data class or control block. The attributes
include the following columns:
Column Description
Name The name of the attribute.
Source The source of the value for this attribute. If it can be edited, this is a drop-down list.
See the table below for a description of the values that can appear in the drop-down
list.
Value The value of the attribute. If the source is Local, you can specify a value.
MMS point This is a reference to the MMS point associated with this attribute. You can edit the
reference by clicking on the browse (…) button next to it and selecting a new data
point in the Node Selection dialog.
This function is for advanced users only. In most cases, the standard automatic
configuration will be used and there will be no need to manually change the
references.
The source of the value for the attribute is described in the table below.
Source Description
None The attribute has no impact on the master. It can be an informative attribute or a
specific IEC 61850 feature not supported by the RTDX and therefore ignored.
Local The attribute value can be edited, and the value you enter, or the default value, will
be used for this attribute.

Source Description
MMS Static The value used for this attribute will be the value as it was read from the device
with the last Get Config or Refresh Data command. The description and scale
information use this type of source, but you can set them to Local if you so
choose.
MMS Dynamic The value used for this attribute is the dynamic value read in the device when the
master component executes. The value, quality and timestamp attribute use this
type of source.
2.15.3.3 I/O List

This list contains the specific RTDX information of the data points produced by the common data
class. For each RTDX data point, the list shows the data point on one line with an indication of its
type (analog output, binary input, etc.), followed by a first attribute indented on the next line,
followed by a second attribute indented on the next line, and so on for all the attributes related to
the RTDX data point.
Name The RTDX name of the data point. This name must adhere to the naming convention
for RTDX data points.
Disable Put a checkmark if you want to disable the data point.
Invert Polarity For a binary point, put a checkmark if you want the value to be inverted.
Control Type Use the drop-down list to choose one of the five control types: Open Close, Pulse,
Pulse Close, Pulse Open, Open Close Pulse.
BO Pairing If you chose Pulse Open as the Control Type, you must specify a Pulse Close binary
output point, and vice versa.
Use this when the device only supports pulse.
Input Scale Scaling factor applied on the input read by the protocol, regardless of their type (raw
or floating point) to generate a reported value. The calculation is done in floating
point, but the reported value will remain of the same type read by the protocol
component. The following equation is used:
Reported value = (protocol value * input scale) + input
offset
Input Offset Offset value applied on the input read by the protocol. See Input Scale setting.
2.15.4 Adding Reports to Retrieve Data from the Device

You can add a report to the master component. This report will use the URCB or BRCB on the
device to retrieve data.
To add a report:
In the left pane, select the Reports folder of the appropriate logical device and logical node
under the DeviceConfig (IEC 61850) node.

In the Insert menu, click Master Report Brcb or Master Report Urcb, depending on the
type of report control block you want to use.
A new item is added to the Reports folder, and the report settings appear in the right pane. These
settings are described in the table below.
Disable Check if you want the file to be disabled.
Write Dataset Check if the dataset is not already set in the DatSet attribute of the report control
block. Some devices do not support to write in this attribute and all the DatSet
attributes are already associated with a dataset.
Attributes This list contains all the attributes of the reports. All the values of the attributes that
are not read-only on the device that can be edited. Note that if the Write Dataset
checkbox is unchecked, the DatSet attribute is not editable.
Report Control This list contains all the report control blocks on the device that can be used to
Block produce the reports. You can add or remove a report control block by using the Add
and Remove button on the top right of the list. Note that the report control blocks
must be of the same type as the report when it was created. The type of report control
block is written in the top of the right pane.
2.15.5 Adding Files to the Master Component

You can add a file from the device to the master component. The file will be downloaded from the
device by a command request on a logical point. The state of the download process is shown in
another logical point associated with the file.
To add a file:
In the left pane, click on the Files folder of the master component.
In the Insert menu, click Master File.
A new item is added to the Files folder, and the file settings appear in the right pane. These
settings are described in the table below.
Disable Put a checkmark if you want the file to be disabled.
Device File Indicates the name of the file in the device.

Name
Local File Indicates the name that will be used when the file is downloaded to the local folder.
Name
Command Indicates the name of the logical binary output point to activate in order to download
Point the file.

Status Point Indicates the name of the logical analog input point that will show the status of the
file download.
The possible statuses are the following:
0 Idle: The component is waiting for the command to download the file.
1 Ready: The component is ready to download and is waiting for the remote
folder.
2 Starting download: The component is starting the download.
3 Downloading: The component is in the process of downloading the file.
4 Download Completed: The data point shows the result of the last download,
and the component is waiting for a new file download command.
5 Download Aborted: The data point indicates that the last download was
aborted, and the component is waiting for a new file download command.
6 Download Failed: The data point indicates that the last download failed, and
the component is waiting for a new file download command.
In the right pane, enter the Device File Name and Local File Name.
2.15.6 Adding a Scan Cycle to Retrieve Data from the Device

You can add a scan cycle to retrieve data from the device.
Note that this is not the method designed to retrieve data with IEC 61850 devices. With this
method, transitions may be lost. The right way is to use a report control block (URCB or BRCB).
However, if for some reason you don’t want to use a report control block, this method is available.
To add a scan cycle:
In the left pane, click on the ScanList folder of the master component.
In the Insert menu, click Master Scan.
An item called NewScan is added to the ScanList folder, and the scan settings appear in the right
pane.
In the right pane, click the Logical device browse (…) button.
In the Node Selection dialog, click on the logical device to be scanned, and click Select.
In the right pane, select the type of scan cycle: a dataset (Scan dataset) or a list of device
points (Scan list).
If you selected Scan dataset, which is the recommended setting:
Click the Scan dataset browse (…) button.
In the Node Selection dialog, click on the dataset you want to associate with the scan,
and click Select.
If you selected Scan list:
Click the Add button.
In the Node Selection dialog, click on the device point to be scanned, and click Select.
Repeat the operation until you have identified all the device points to be included in the
scan cycle, up to a maximum of 32 points.

To remove a device point from the list:
Click on the device point, in the Scan list.
2.15.7 Editing the Logical Data Points of the Master

You can enable or disable the various logical points of the master component.
To enable or disable a logical point:
In the left pane:
Expand the IO Logic folder.
Expand the Analog Inputs, Binary Inputs or Binary Outputs folder.
Click on the logical point you want to edit.
The logical I/O data point settings appear in the right pane.
Mark or clear the Disable checkbox, depending on whether or not you want this point to be
disabled.
If you are editing the settings of a logical input point and you want to apply a deadband to its
value, enter the SMP deadband value.
2.16 Creating a New UCA 2.0 Master Configuration

from Scratch
2.16.1 Creating a Master Component
To create a new master component:
In the left pane, click on UCA 2.0 Masters.
In the Insert menu, click Master.
61850 Config adds a virgin master component under UCA 2.0 Masters and assigns it a default
name.
To rename the master component:

Click on the master component.
The master component you just created contains all the base folders and data points required in a
configuration. The base folders and data points cannot be cut, copied, renamed or deleted.
2.16.2 Setting the Parameters of a Master Component

To set the parameters of a master component, proceed as follows:
In the right pane, click on the appropriate connection in the Connection combo box.

Enter the Device prefix, Selection timeout, Request timeout and Keep alive parameters.
Put a checkmark in the Control enabled checkbox, if you want to allow the master to accept
commands and transmit them to the device.
Put a checkmark in the Validate configuration on connection reset checkbox, if you want
the configuration to be validated whenever the connection is reset.
2.16.3 Downloading the Device Configuration

To download the device configuration:
In the right pane, use the Connection drop-down list to specify the connection through which
the device can be accessed.
In the Tools menu, click Get Config.
The download operation may take a while.
Once the download is complete, the DeviceConfig folder is selected and contains the device
configuration.
Note: Some devices may give you information that is not related to UCA 2.0. If this
happens, you can delete unwanted logical devices from the DeviceConfig folder.
You are now ready to start configuring the master component. You will be able to create a UCA
2.0 master component architecture by using the procedures for:
Adding a Data Point to a Master Component
Associating an Existing Data Point with a Device Point
Adding a Scan Cycle to Retrieve Data from the Device
Adding Device Report Support
Creating Brick Templates
Instantiating Brick Templates
2.16.4 Adding a Data Point to a Master Component

You can add a data point to a master component. Note that this operation is subject to certain
validation rules. You can add an analog input, analog output, binary input, or binary output point.
The procedure is identical in all cases and is explained below, using an analog input point for the
purpose of demonstration.
2.16.4.1 Adding a Data Point Directly to the IO List

To add an analog input data point directly to the IO List:
In the left pane, click on the IO List/Analog Inputs/Physical Inputs folder under the master
component.
In the Insert menu, point to Master IO point, and then click (AI) Analog Input.
The new data point now appears in the IO List/Analog Inputs/Physical Inputs folder of the
master component.

2.16.4.2 Adding a Data Point to the IO List, from a Master Device Point
To add a data point to the IO List, from a master device point:
In the left pane, in the DeviceConfig folder of the master component, click on the device
point you want to associate with a new data point.
In the right pane, click the New button.
The Create RTDX Point dialog box appears.
Use the IO Type drop-down list to specify the data point type.
Use the Attribute drop-down list to specify the attribute to be associated with the device
point.
In the RTDX point text box, enter the name of the new data point.
Click the Create button of the dialog box.
The new data point now appears in the appropriate folder, in the IO List of the master component.
Furthermore, checkmarks are appended to the device point and to all the folders above it, within
the DeviceModel. This provides an easy way for you to identify which device points are
associated with the data points in the master component's IO list.
To jump directly to the new data point in the IO List:

Click on the new data point in the right pane.
Click the Go To button.
2.16.5 Associating an Existing Data Point with a Device Point

You can associate an existing data point in the IOList of the master component, with a device
point in its DeviceConfig folder. Note that this operation is subject to certain validation rules.
There are two procedures available.
2.16.5.1 Making the Association from the Device Point to the IO List
In the left pane, in the DeviceConfig folder of the master component, click on the device
point.
In the right pane, click the Add button.
The Select RTDX Point dialog box appears.
Use the IO type drop-down list to specify the data point type.
Use the Attribute drop-down list to specify the attribute to be assigned to the data point.
Use the RTDX point drop-down list to specify the name of the existing data point.
Click the Select button.
The attributes of the device point are assigned to the associated data point.
Checkmarks are appended to the device point and to all the folders above it, within the
DeviceModel. This provides an easy way for you to identify which device points have been
associated with data points in the IO list.
To jump directly to the associated data point in the IO List:

Click on the data point in the right pane.

Click the Go To button.
2.16.5.2 Making the Association from the IO List to the Device Point
In the left pane, in the IO List of the master component, click on the data point you want to
associate with a device point.
In the right pane, click the browse (…) button of the Value or State field.
In the dialog, click on the device point you want to associate with the data point.
In the right pane, you can see that all the settings for the data point are automatically updated with
the information from the brick that contains the device point.
2.16.6 Adding a Scan Cycle to Retrieve Data from the Device

You can add a scan cycle to retrieve data from the device.
To add a scan cycle:
In the left pane, click on the ScanList folder of the master component.
In the Insert menu, click Master Scan.
An item called NewScan is added to the ScanList folder, and the scan settings appear in the
right pane.
In the right pane, click on the Logical device browse (…) button.

In the dialog, click on the logical device to be scanned.
In the right pane, select the type of scan cycle: a dataset (Scan dataset) or a list of device
points (Scan list).
If you have selected Scan dataset, which is the recommended setting,
Click the Scan dataset browse (…) button.
The Node Selection dialog box appears once again.

In the dialog, click on the dataset you want to associate with the scan.
If you have selected Scan list,
Click the Add button.

In the dialog, click on the device point to be scanned.
Repeat the operation until you have identified all the device points to be included in the
scan cycle. You can include a maximum of 32 points.
To remove a device point from the list:

In the right pane, click on the device point, in the Scan list.
2.16.7 Adding Device Report Support

You can receive report data from a device. In order to receive the report, you must add a report
item to your configuration.
To add a report item:
In the left pane, select the Reports folder of the master component.
In the Insert menu, click Master Report.
An item called NewReport is added to the Reports folder, and the report settings appear in the
right pane.
In the right pane, click the Report Node browse (…) button.
In the dialog, under the appropriate DeviceModel, click on a folder for which you want a
report.
If you clicked on a folder that contains standard folders, the settings in the right pane will
automatically be updated.
If you want to correct the associations or add missing information:
Click on the corresponding browse (…) button.
When the device sends a report, you will be able to receive the data it contains.
2.16.8 Creating Brick Templates

You can create brick templates to speed up the process of creating a master from scratch. Once a
brick model is defined, you can use it to automatically create the required data points and make all
the associations.
To create a brick template:
In the left pane, under DeviceModel, click on the brick you want to use as a model.
In the dialog, specify the template file name, and click Save.
The template is now available to be instantiated, for bricks of the same type.
Note:
You can modify a template by opening it with 61850 Config.
The configuration process is the same as for a normal master.
2.16.9 Instantiating Brick Templates

To instantiate a brick template:
In the left pane, click on the type of brick you want to instantiate.

In the dialog, click on the template file to be instantiated, and click Open.
The Enter New Brick Prefix dialog box appears.
Enter the brick prefix, and click OK.
The Create from Template dialog box appears, displaying the list of available data points.
In the dialog, choose the data points you want to create.
Click the OK button of the dialog box.
For each data point in the template brick, a new data point will be added to the IO List. This new
data point will have the brick prefix you entered above. The data points you selected will be added
to the appropriate data point lists. For example, if the template brick was associated with a binary
input point called BI_2 and you entered a new brick prefix of NEW, and then a new data point will
be created and will be called NEWBI_2. You will be able to see the new data point in the IO List.
Furthermore, if you click on any device point that had BI_2 as an associated data point, you will
see, in the right pane, that it now has NEWBI_2 as an associated data point as well.
Once you have completed a brick instantiation, the command New Instance from Last Template
becomes available in the Tools menu. This command allows you to instantiate a brick, using the
template file you used for the last instantiation.
To instantiate a brick from the template you used for the last instantiation:
In the left pane, click on the type of brick you want to instantiate.
In the Tools menu, click New Instance from Last Template.
The Enter New Brick Prefix dialog box appears.

Enter the brick prefix, and click OK.
The Create from Template dialog box appears, displaying the list of available data points.
In the dialog, choose the data points you want to create.
Click the OK button of the dialog box.
When you try to instantiate a brick from a template, you may get a message informing you that the
template you chose cannot be used for the instantiation. Here is a list of possible causes for this
problem.
The template file is corrupted.
You clicked on one type of brick and chose a template of another type of brick.
The last template used was for a master.
The brick you clicked on and the brick in the template match, but there is a difference in the
names of the points within the bricks.

Template
With 61850 Config, you can create template files to quickly configure devices of the same model.
To create a new master template file:
Open a configuration file that has a master containing one or more devices for which you
want to create a template.
In the left pane, click on the master that corresponds to the future template.

The saved file contains a template of the master on which you clicked. The template is compatible
with SMP Config, so you can also use SMP Config to instantiate UCA 2.0 master templates in
your SMP configuration file.

from a Template
The fastest and easiest way to create a complete UCA 2.0 Master component is to instantiate one
from a template. The template, which typically resides in your SMP configuration file, has been
created by 61850 Config (see "Creating a New UCA 2.0 Master Configuration Template", above).
To instantiate a master component from a template:

In the left pane, click on UCA 2.0 Masters.
Click on the template file you want to instantiate.
The Enter New Instance Information dialog box appears.
Enter the new instance name and prefix in the appropriate text boxes.
Click the OK button.
A new master corresponding to the instantiated template, is now added to the left pane, under
UCA 2.0 Masters.
Notes:
You can also use SMP Config to instantiate a template.
You can modify a template by opening it with 61850 Config. The configuration process
is the same as a normal master.

2.19 Modifying a UCA 2.0 Master Configuration
You can modify the UCA 2.0 master configuration. In the left pane, checkmarks are appended to
each brick in which device points have been mapped to data point attributes.
The modifications you can make are discussed in the following sections:
"Editing Data Point Properties"
"Deleting a Data Point"
"Copying a Data Point"
"Pasting a Data Point"
"Refreshing the Device Values Used as Data Point Properties"
2.19.1 Editing Data Point Properties

You can edit the properties of physical data points.
To modify the properties of a physical data point, proceed as follows:
In the left pane, open the appropriate folder in the IO List of the master component for which
you want to modify the properties of a physical data point.
Click on the physical data point you want to edit.
In the right pane, apply your modifications to the appropriate settings, as described in the
tables below.
When a property has a value text box or combo box, you can specify the value to be used. Some
properties are mandatory; if left empty, they will generate a validation error.
The four layouts for the physical data points are presented in this section. These layouts are
displayed in the right pane whenever you click on a data point in the left pane.
Note that you cannot edit the properties of logical data points. The only action you can take with a
logical data point is to mark the Disable checkbox in the right pane.
Note: Device values are not dynamically updated. To retrieve up-to-date values, use
the Refresh command (see "Refreshing the Device Values Used as Data Point
Properties", page 55).
2.19.1.1 Physical Analog Input Points (AI)
Box Constraints Description
Disable None. If this checkbox contains a checkmark, the

data point is disabled.
Value Must point to a float or int point. Specifies the device value used as the data
source for the data point. Use the browse
button to identify the device point. If
available, use the combo box drop-down list
to specify the format of the value.

SMP Must be a positive integer. Specifies the value used by the SMP to filter
deadband the transient states. Enter the value manually.
Quality Must point to a quality point. If the checkbox contains a checkmark,

specifies the device quality point used for the
data point quality. Use the browse button to
identify the device point.
Timestamp Must point to a timestamp point. If the checkbox contains a checkmark,

specifies the device timestamp point used for
the data point timestamp. Use the browse
button to identify the device point.
Description Must point to a string point. If the checkbox contains a checkmark,

specifies the device description point used
for the data point. Use the browse button to
None. If the checkbox does not contain a

checkmark, use the text box to manually
enter the data point description.
Units Must point to a unit point. If the checkbox contains a checkmark,

specifies the device unit point used for the
data point unit. Use the browse button to

checkmark, use the combo box drop-down
list to specify the unit type.
Scale Must point to a scale point. If the checkbox contains a checkmark,

specifies the device scale point used for the
data point scale. Use the browse button to
Must be a number. If the checkbox does not contain a

checkmark, use the combo box drop-down
list to specify the data point scale.
Offset Must point to an offset point. If the checkbox contains a checkmark,

specifies the device offset point used for the
data point offset. Use the browse button to
Must be a number. If the checkbox does not contain a

enter the data point offset.
2.19.1.2 Physical Binary Input Points (BI)

Disable None. If the checkbox contains a checkmark, the

data point is disabled.
State Must point to a binary point. Specifies the device value used as the data
source for the data point. Use the browse
button to identify the device point. If
available, use the combo box to specify the
format of the value.
Inverted None. If the checkbox contains a checkmark, the

polarity data point polarity is inverted.
Quality Must point to a quality point. If the checkbox contains a checkmark,

specifies the device quality point used for the
data point quality. Use the browse button to
Timestamp Must point to a timestamp point. If the checkbox contains a checkmark,

specifies the device timestamp point used for
the data point timestamp. Use the browse
Description Must point to a string point. If the checkbox contains a checkmark,

specifies the device description point used
for the data point. Use the browse button to
None.
If the checkbox does not contain a
enter the data point description.
2.19.1.3 Physical Analog Output Points (AO)

The Analog Outputs folder contains all the properties of the Analog Inputs/Physical Inputs
folder, plus the Operate parameters. For the common properties, see "Physical Analog Input
Points (AI)" (above).
Operate value Must point to a device int or float Specifies the device point used for the
output point. command Operate value. Use the browse
SBO Must point to a device SBO point. If the checkbox contains a checkmark,
specifies the device SBO point used for the
data point SBO. Use the browse button to
None.
If the checkbox does not contain a
checkmark, the point does not support Select
Before Operate mode.

2.19.1.4 Physical Binary Output Points (BO)
The Binary Outputs/Physical Outputs folder contains all the properties of the Analog
Inputs/Physical Inputs folder, plus the Operate parameters. For the common properties, see
"Physical Binary Input Points" (above).
Operate status Must point to a device binary output Specifies the device point used for the
point. command Operate status. Use the browse
SBO Must point to a device SBO point. If the checkbox contains a checkmark,
specifies the device SBO point used for the
data point SBO. Use the browse button to

checkmark, the point does not support Select
Before Operate mode.
Control type None. Use the combo box to choose one of the four
control types: Open/Close, Pulse,
Pulse/Close, Pulse/Open.
OnDur Must point to a positive integer If the checkbox contains a checkmark, the
device point that specifies the On master will write to this device point, to
duration of a pulse. control the On duration. The device point
must not be read-only. Use the browse button
to search for the device point. Also, make
A positive integer value. sure to enter a value in Activation time.
Activation Must be a positive integer. This value is used for the pulse duration if no
time duration is specified by RTDX. Enter a value
in this box if you put a checkmark in
OnDur.
Master None. If you put a checkmark in this box, the

duration master station that sends the command will
allowed specify its own pulse duration. If you do not
put a checkmark, the Activation time you
have specified will be used, regardless of
whether or not the master station specifies a
pulse duration.
BO pairing Must point to another BO data If you chose Pulse, Open as the Control
point. type, you must specify a Pulse, Close binary
output point, and vice versa.
Use this when the device only supports
pulse.
2.19.2 Deleting a Data Point

To delete a data point:
In the left pane, click on the data point you want to delete.

2.19.3 Copying a Data Point

To copy a data point:
In the left pane, click on the data point you want to copy.
2.19.4 Pasting a Data Point

To paste a data point that you previously cut or copied:
In the left pane, click on the folder in which you want to paste the data point.
2.19.5 Refreshing the Device Values Used as Data Point

Properties
When you set a reference to a device point, the associated value is not dynamically updated. This
enables you to create your configuration without having to be connected to the device. You can
retrieve the device values when you want them to appear in 61850 Config.
To refresh the device values used in the master configuration:
In the left pane, click on the master component to be refreshed.
In the Tools menu, click Refresh Data.
This operation may take a while.
2.20 Validating an IEC 61850 and UCA 2.0

Configuration
It is important to validate an IEC 61850 or UCA 2.0 configuration, to ensure that it is usable. In
fact, 61850 Config automatically performs the validation when you attempt to save a
configuration.
To validate an IEC 61850 or UCA 2.0 slave or master configuration, or both:
In the Tools menu, click Validate.
If 61850 Config finds any errors, the Error Report dialog box appears, displaying the list of
errors found.

To locate a faulty item:
Select an error message in the dialog box.
Click the Go To button of the dialog box.
The item containing the error is selected, in the left pane.
To correct the problem:
Make a modification in the left pane, such as changing the data point name
OR
Modify the appropriate parameter in the right pane.
Once you have corrected a few errors, you may want to refresh the error list in the dialog box.
To do this:
Click the Refresh button of the dialog box.
Note: 61850 Config does not save your configuration if your architecture contains
errors, so if you have just corrected some errors, we strongly suggest that you
save your configuration.
The errors you may encounter are listed in the tables below.
General Validation Description

Errors
Unknown error An unidentified error has occurred.
The name is too long The data point has too long a name.
In UCA 2.0, the name must contain less than 32 characters.
Note that the name includes the names of all the folders above the data
point. Thus, a data point called AO_123, which is in folder GIND1 /
ST / ST15 is considered to have a name of GIND1/ST/ST15/AO_123.
Enter a name The data point has not been assigned a name.

General Validation Description
Errors
The folder contains too A folder can’t contain more than 65,534 items, including folders and
many items data points.
(We strongly recommend that you limit the number of items to 32.)
Slave Validation Description

Errors
The RTDX reference is The data point specified in the RTDX name box does not exist.
invalid
This occurs when the source is RTDX, but the data point specified in
the RTDX name box has been removed by SMP Config.
The referenced deadband Either the type of the referenced deadband data point is not INT16U or
type is invalid the referenced data point is invalid.
The referenced state type is Either the type of the referenced state data point is not BOOL or the
invalid referenced data point is invalid.
The referenced OnDur type Either the type of the referenced OnDur data point is not INT32U or
is invalid the referenced data point is invalid.
The folder is empty The folder contains no data points. Insert at least one data point or
delete the folder.
The Dataset List must The item in the Datasets folder has an empty Dataset list.
contain at least one dataset
The reference is invalid The item in the Datasets folder has an invalid reference in its Dataset
List.
Master Validation Description

Errors
The RTDX reference is A data point in the Associated RTDX points list is non-existent.
invalid
Either the data point has been removed by SMP Config or you
removed the point from the IO List. The latter case is exceptional,
since 61850 Config normally manages the removal of data points in
the IO List. The situation might arise after your computer went down,
for example.
The prefix/data point name The prefix, when combined with the data point name, results in a string
combination is too long that is too long. Diminishing the prefix length is the recommended
solution, in most cases.
Enter the device prefix The Device prefix box of the master component is empty.

Errors
Specify which datasets are to The item in the ScanList folder must specify a dataset or a list of
be scanned dataset points to be scanned. Either use the browse (...) button of the
Scan dataset box to identify a dataset, or click Scan list and use the
Add button to create a list of datasets.
Set the Dataset pointer The item in the Reports folder must specify a dataset in its Dataset
box. Use the browse button to locate the appropriate dataset.
The referenced dataset type The Dataset box of the item in the Reports folder points to an invalid
is invalid dataset.
Set the Report Folder pointer The Report folder box of the item in the Reports folder must specify
a report folder. Use the browse button to locate the appropriate report
folder.
Set the Operate Value The Operate value box of the analog output point does not specify a
pointer for the command value point for the command. Use the browse button to locate the
appropriate value point.
Set the Operate Status The Operate status box of the binary output point must specify a
pointer for the command status point for the command. Use the browse button to locate the
appropriate status point.
Set the Value pointer The Value box of the analog input point must specify a value point.
Use the browse button to locate the appropriate value point.
Set the Description pointer The Use Device Value checkbox contains a checkmark for the
Description, but the Description box does not specify a description
point. Use the browse button to locate the appropriate description point.
Set the Units pointer The Use Device Value checkbox contains a checkmark for the Units,
but the Units box does not specify a unit point. Use the browse button
to locate the appropriate unit point.
Set the Scale pointer The Use Device Value checkbox contains a checkmark for the Scale,
but the Scale box does not specify a scale point. Use the browse button
to locate the appropriate scale point.
Set the Offset pointer The Use Device Value checkbox contains a checkmark for the Offset,
but the Offset box does not specify an offset point. Use the browse
button to locate the appropriate offset point.
Set the Quality pointer The Use Device Value checkbox contains a checkmark for the
Quality, but the Quality box does not specify a quality point. Use the
browse button to locate the appropriate quality point.
Set the Timestamp pointer The Use Device Value checkbox contains a checkmark for the
Timestamp, but the Timestamp box does not specify a timestamp
point. Use the browse button to locate the appropriate timestamp point.
Set the SBO pointer The SBO checkbox contains a checkmark, but the SBO box does not
specify an SBO point for the command. Use the browse button to
locate the appropriate SBO point.

Errors
Set the State pointer The State box for a binary data point must specify a state point. Use
the browse button to locate the appropriate state point.
Set the OnDur pointer The OnDur checkbox contains a checkmark, but the OnDur box does
not specify a device point for the pulse duration. Use the browse button
to locate the appropriate OnDur point.
Set the BO Pairing pointer The BO Pairing checkbox of the binary output point contains a
checkmark, but the BO Pairing box does not specify a valid binary
output point. Use the browse button to locate the appropriate device
point.
Invalid Open/Close pair for The pointer in the BO Pairing box does not produce a valid BO
BO pairing Pairing pair with the binary output point selected in the left pane. If
you specified Pulse, Open as the Control type, you must specify a
Pulse, Close binary output point in the BO Pairing box, and vice
versa. Use the browse button to locate the appropriate device point.
The Dataset List must The item in the Datasets folder has an empty Dataset list in the right
contain at least one dataset pane.

Config User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Config User Guide

Uploaded by

Copyright:

Available Formats

User Guide

Cooper Power Systems

Technical Support: support@cybectec.com

2 Using 61850 Config 5

61850 Config User Guide •i

ii • 61850 Config User Guide

61850 Config User Guide • iii

1.1.2 Installing 61850 Config

61850 Config User Guide •1

1.2.1.3 UCA 2.0 References

1.2.1.4 IEC 61850 References

2• 61850 Config User Guide

1.2.2.2 The UCA 2.0 Slave Component

1.2.2.3 The IEC 61850 Master Component

61850 Config User Guide •3

1.2.2.4 The UCA 2.0 Master Component

4• 61850 Config User Guide

2.1 Preliminary Requirements

2.2 Starting 61850 Config

61850 Config User Guide •5

2.3 Creating a New Slave Connection

To rename the slave connection:

To configure the slave connection:

6• 61850 Config User Guide

2.4 Creating a New IEC 61850 Slave Configuration

To rename the slave component:

To configure the slave component:

Note that only the available slave connections are shown.

Connection Indicates the connection that is associated with the slave.

Vendor Vendor name, for informative purposes. This setting is optional.

Model Component model, for informative purposes. This setting is optional.

Revision Component revision, for informative purposes. This setting is optional.

61850 Config User Guide •7

It is also used on the reception of clock synchronization request, to convert the

8• 61850 Config User Guide

2.4.2 Adding Clients to a Slave Component

To configure the slave Tpaa:

AP Title Client application process title. A string consisting of at most 16 space-separated

Presentation Client presentation layer selector. A string consisting of at most 4 space-separated

2.4.3 Adding Files to a Slave Component

61850 Config User Guide •9

To configure the slave file:

2.4.4 Adding a Logical Device to a Slave Component

2.4.5 Adding a Logical Node to a Logical Device

2.4.6 Adding a Common Data Class to a Logical Node

To configure the common data class:

10 • 61850 Config User Guide

 Click on an RTDX point in the list.

61850 Config User Guide • 11

2.4.7 Adding a Control Block to a Logical Node

To configure the control block:

2.4.8 Adding a Dataset to a Logical Node

To add a common data class to a dataset:

The Node Selection dialog box appears.

To remove a common data class from a dataset:

12 • 61850 Config User Guide

2.5.2 Editing Common Data Class and Control Block Properties

61850 Config User Guide • 13

Local The value of the point is local to the slave.

2.5.2.4 Specific Attribute Information

14 • 61850 Config User Guide

2.5.3 Deleting an Item

2.5.4 Renaming an Item

Click on an RTDX point in the list.

Click the Replace button to define an alias.

In the Find what text box, enter the text to be replaced.