Config User Guide (UCA 2.0 Specific)

User Guide
MN912032EN, version 13
61850 Config
(UCA 2.0 Specific)
For use with SMP Gateway software version 7.0 or later.
All brand and product names appearing in this document are the trademark or registered trademark
of their respective holders.
© 2016 Eaton – All rights reserved.

The information in this document is subject to change without notice.
Eaton’s Energy Automation Solutions

1990 5th Street
Suite 220
Levis, Quebec
Canada G6W 5M6
Phone: +1.418.830-5800
Fax: +1.514.227.5256
Email: PSMO-sales@eaton.com
Web: http://www.cooperpower.com
Technical Support: eas-support@eaton.com
MN912032EN, version 13
EAS-SA QF-MKT-02 Rev.02
Contents
1 Getting Started 1
1.1 Introduction ...........................................................................................................1
1.1.1 Welcome to 61850 Config ......................................................................1
1.1.2 Document Scope .....................................................................................1
1.1.3 Installing 61850 Config...........................................................................1
1.2 Getting Assistance .................................................................................................2
1.3 61850 Config .........................................................................................................2
1.3.1 Protocol Overview ..................................................................................2
1.3.1.1 UCA 2.0 ...................................................................... 2
1.3.1.2 GOMSFE .................................................................... 2
1.3.1.3 UCA 2.0 References ................................................... 2
2 Using 61850 Config 3

2.1 Preliminary Requirements .....................................................................................3
2.2 Starting 61850 Config ...........................................................................................3
2.3 Creating a New Slave Connection .........................................................................4
2.4 Creating a New UCA 2.0 Slave Configuration Using the Wizard.........................5
2.4.1 Creating a Slave Component ...................................................................5
2.4.2 Adding a Logical Device to a Slave Component ....................................5
2.4.2.1 Adding Bricks Automatically ..................................... 5
2.4.2.2 Adding Bricks Manually ............................................ 6
2.5 Creating a New UCA 2.0 Slave Configuration From Scratch ...............................7
2.5.1 Creating a Slave Component ...................................................................7
2.5.2 Adding a Logical Device to a Slave Component ....................................7
2.5.3 Adding a Folder under a DeviceModel ...................................................8
2.5.4 Adding a Data Point under a DeviceModel .............................................8
2.5.5 Adding a Dataset to a Datasets Folder ....................................................8
2.5.6 Adding Basic Building Bricks under a DeviceModel .............................9
2.5.6.1 GAIN .......................................................................... 9
2.5.6.2 GIND .......................................................................... 9
2.5.6.3 GCTL.......................................................................... 9
2.5.6.4 GSPT ........................................................................ 10
61850 Config User Guide (UCA 2.0 Specific) ●i

2.5.7 Adding a Common Class under a DeviceModel ................................... 10

2.5.7.1 (DI) Device Identity.................................................. 10
2.5.7.2 (AI) Analog Input ..................................................... 10
2.5.7.3 (SI) Status Input Single Bit ....................................... 11
2.5.7.4 (AO) Analog Output ................................................. 11
2.5.7.5 (BO) Binary Output .................................................. 11
2.5.7.6 (ACF) Analog Configuration .................................... 12
2.5.7.7 (CCF) Control Configuration ................................... 12
2.5.7.8 (SBOCF) SBO Configuration ................................... 12
2.5.7.9 (d) Description .......................................................... 12
2.5.7.10 (basRCB) Basic Report Control Block ..................... 12
2.6 Modifying a UCA 2.0 Slave Configuration ......................................................... 13
2.6.1 Editing Data Point Properties ................................................................ 13
2.6.1.1 Source ....................................................................... 13
2.6.1.2 RTDX Name ............................................................. 13
2.6.1.3 Function .................................................................... 14
2.6.1.4 Value ........................................................................ 14
2.6.1.5 UCA 2.0 Type .......................................................... 15
2.6.1.6 Reference .................................................................. 15
2.6.1.7 Write ......................................................................... 16
2.6.1.8 Simulated Control Confirmation .............................. 16
2.6.1.9 RTDX Quality to UCA 2.0 Quality .......................... 16
2.6.2 Copying a Folder or a Data Point .......................................................... 16
2.6.3 Cutting a Folder or a Data Point............................................................ 17
2.6.4 Pasting a Folder or a Data Point ............................................................ 17
2.6.5 Deleting a Folder or a Data Point .......................................................... 17
2.6.6 Renaming a Folder or a Data Point ....................................................... 17
2.6.7 Duplicating a Logical Device ................................................................ 17
2.7 Creating a New Master Connection..................................................................... 17
2.8 Creating a New UCA 2.0 Master Configuration from Scratch ............................ 18
2.8.1 Creating a Master Component............................................................... 18
2.8.2 Setting the Parameters of a Master Component .................................... 18
2.8.3 Downloading the Device Configuration................................................ 19
2.8.4 Adding a Data Point to a Master Component ........................................ 19
2.8.4.1 Adding a Data Point Directly to the IO List ............. 19
2.8.4.2 Adding a Data Point to the IO List, from a
Master Device Point .............................................................................. 19
ii ● Contents
2.8.5 Associating an Existing Data Point with a Device Point....................... 20

2.8.5.1 Making the Association from the Device Point
to the IO List 20
2.8.5.2 Making the Association from the IO List to the
Device Point 20
2.8.6 Adding a Scan Cycle to Retrieve Data from the Device ....................... 21
2.8.7 Adding Device Report Support ............................................................. 22
2.8.8 Creating Brick Templates...................................................................... 22
2.8.9 Instantiating Brick Templates ............................................................... 22
2.9 Creating a New UCA 2.0 Master Configuration Template ................................. 23
2.10 Creating a New UCA 2.0 Master Configuration from a Template ...................... 24
2.11 Modifying a UCA 2.0 Master Configuration ...................................................... 24
2.11.1 Editing Data Point Properties ................................................................ 25
2.11.1.1 Physical Analog Input Points (AI) ............................ 25
2.11.1.2 Physical Binary Input Points (BI) ............................. 26
2.11.1.3 Physical Analog Output Points (AO)........................ 27
2.11.1.4 Physical Binary Output Points (BO)......................... 27
2.11.2 Deleting a Data Point ............................................................................ 28
2.11.3 Copying a Data Point ............................................................................ 28
2.11.4 Pasting a Data Point .............................................................................. 29
2.11.5 Refreshing the Device Values Used as Data Point Properties............... 29
2.12 Validating an UCA 2.0 Configuration ................................................................. 29
61850 Config User Guide (UCA 2.0 Specific) ● 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 Document Scope

This document only covers the configuration and setup of UCA 2.0 master and slave
protocols.
IEC 61850 master and slave protocol configuration is now presented and explained in the
IEC 61850 Master and Slave Protocols Reference Manual, MN912028EN.
1.1.3 Installing 61850 Config

61850 Config is automatically installed by the SMP Tools installation program.
61850 Config User Guide (UCA 2.0 Specific) •1

1.2 Getting Assistance

If you have any question regarding the performance, application or testing of any component of
this Eaton’s Cooper Power series product, do not hesitate to contact us. Our staff will be pleased to
assist you.
Technical Support
Eaton’s Energy Automation Solutions
Email: eas-support@eaton.com
Phone: +1.763.595.7775
Toll Free: +1.800.815.2258
Business hours are from 8 a.m. and 5 p.m. CST, Monday to Friday.
1.3 61850 Config

1.3.1 Protocol Overview
1.3.1.1 UCA 2.0
UCA 2.0 (Utility Communications Architecture, version 2) is 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.3.1.2 GOMSFE
GOMSFE (Generic Object Models for Substation and Feeder Equipment) is standardized model of
devices in the electrical power industry.
1.3.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.
2● Chapter 1: Getting Started

2 Using 61850 Config
2.1 Preliminary Requirements

61850 Config can be used to configure 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 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 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:
4● Chapter 2: Using 61850 Config

 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 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 7).
2.4.1 Creating a Slave Component

To create a new UCA 2.0 slave component:
 Click on UCA 2.0 Slaves.
 In the Insert menu, click Slave.
To configure the slave component:

 In the left pane, click on the slave component you have just created.
 Enter the Vendor, Model and Revision information.
 Using the Connection combo box, choose the appropriate connection.
Note that only the available connections are shown.
2.4.2 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.
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.4.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.4.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.
The dialog contains the following boxes and buttons:
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.
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.5 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 5).
2.5.1 Creating a Slave Component

To create a new UCA 2.0 slave component:
 Click on UCA 2.0 slaves.
 In the Insert menu, click Slave.
To configure the slave component:

 In the left pane, click on the slave you have just created.
 Enter the Vendor, Model and Revision information.
 Using the Connection combo box, choose the appropriate connection.
2.5.2 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.
The New Logical Device dialog box appears (see "Creating a New UCA 2.0 Slave Configuration
Using the Wizard", page 5).
 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 6).
 If you choose to add bricks immediately, turn to "Adding Basic Building Bricks under a
DeviceModel", page 9).
 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.5.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.5.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.5.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.

 Click the Select button of the dialog box.
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.5.6 Adding Basic Building Bricks under a DeviceModel

You can easily add a brick under a DeviceModel.
2.5.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.
The RTDX Point Selection dialog box appears
 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.5.6.2 GIND
To add a GIND:
 In the Insert menu, point to Slave Basic Building Bricks, and then click (GIND) Generic
Indicator.
The RTDX Point Selection dialog box appears.
Note that you will only have the choice of binary input points, and you can associate a maximum
Datasets folder.
2.5.6.3 GCTL
To add a GCTL:
 In the Insert menu, point to Slave Basic Building Bricks, and then click (GCTL) Generic
Control.


Note that you will only have the choice of binary output points, and you can associate a maximum
Datasets folder.
2.5.6.4 GSPT
To add a GSPT:
 In the Insert menu, point to Slave Basic Building Bricks, and then click (GSPT) Generic
Set Point.
Note that you will only have the choice of analog output points, and you can associate a maximum
Datasets folder.
2.5.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.5.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.5.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.
 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.
The Node Selection dialog box appears.
 Click on a reference point, to indicate the value of the deadband.
10 ● Chapter 2: Using 61850 Config

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.5.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.
 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.5.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.
 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.5.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.
 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.
61850 Config User Guide (UCA 2.0 Specific) • 11

 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.5.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.
 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.5.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.5.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.5.7.9 (d) Description

To add a d folder:
 In the Insert menu, point to Slave Common Class, and then click (d) Description.
 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.5.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.6 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.6.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.6.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.6.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.
Click on the RTDX point you want to associate with this data point.

2.6.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.6.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.
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

Value Constraints Description

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.6.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.6.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.6.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.6.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.6.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.6.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.

 In the Edit menu, click Copy.
2.6.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.6.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.
 In the Edit menu, click Paste.
2.6.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.
 In the Edit menu, click Delete.
2.6.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.6.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.7 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.
 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.8 Creating a New UCA 2.0 Master Configuration

from Scratch
2.8.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.8.2 Setting the Parameters of a Master Component

To set the parameters of a master component, proceed as follows:
 In the left pane, click on the master component.
 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.8.3 Downloading the Device Configuration

To download the device configuration:
 In the left pane, click on the master component.
 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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.
 Click the Remove button.

2.8.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.8.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 File menu, click Save As Template.
A standard Windows Save dialog box appears.
 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.8.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 Tools menu, click New Instance from Template.
A standard Windows Open dialog box appears.
 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.
 In the File menu, click Save As Template.
A standard Windows Save dialog box appears.

 Enter the new template file name, and click Save.
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.
 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.
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.11 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.11.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 29).
2.11.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.11.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.11.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.11.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 (BI)" (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.11.2 Deleting a Data Point

To delete a data point:
 In the left pane, click on the data point you want to delete.
 In the Edit menu, click Delete.
2.11.3 Copying a Data Point

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

2.11.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.11.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.12 Validating an UCA 2.0 Configuration

It is important to validate an 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 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 a maximum of 64 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.
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.

Slave Validation Description

Errors
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.
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.

Master Validation Description

Errors
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.
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 (UCA 2.0 Specific)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Config User Guide (UCA 2.0 Specific)

Încărcat de

Drepturi de autor:

Formate disponibile

User Guide

© 2016 Eaton – All rights reserved.

Eaton’s Energy Automation Solutions

Technical Support: eas-support@eaton.com

2 Using 61850 Config 3

61850 Config User Guide (UCA 2.0 Specific) ●i

2.5.7 Adding a Common Class under a DeviceModel ................................... 10

2.8.5 Associating an Existing Data Point with a Device Point....................... 20

61850 Config User Guide (UCA 2.0 Specific) ● iii

1.1.2 Document Scope

1.1.3 Installing 61850 Config

61850 Config User Guide (UCA 2.0 Specific) •1

1.2 Getting Assistance

1.3 61850 Config

1.3.1.3 UCA 2.0 References

2● Chapter 1: Getting Started

2 Using 61850 Config

2.1 Preliminary Requirements

2.2 Starting 61850 Config

61850 Config User Guide (UCA 2.0 Specific) •3

2.3 Creating a New Slave Connection

To rename the slave connection:

To configure the slave connection:

4● Chapter 2: Using 61850 Config

 For an SMP 8-40, select the Board in the drop-down list.

2.4 Creating a New UCA 2.0 Slave Configuration

2.4.1 Creating a Slave Component

To configure the slave component:

2.4.2 Adding a Logical Device to a Slave Component

2.4.2.1 Adding Bricks Automatically

61850 Config User Guide (UCA 2.0 Specific) •5

2.4.2.2 Adding Bricks Manually

The dialog contains the following boxes and buttons:

6● Chapter 2: Using 61850 Config

When you have finished creating bricks:

2.5 Creating a New UCA 2.0 Slave Configuration

2.5.1 Creating a Slave Component

To configure the slave component:

2.5.2 Adding a Logical Device to a Slave Component

61850 Config User Guide (UCA 2.0 Specific) •7

2.5.3 Adding a Folder under a DeviceModel

2.5.4 Adding a Data Point under a DeviceModel

2.5.5 Adding a Dataset to a Datasets Folder

8● Chapter 2: Using 61850 Config

 Click on the data point or folder you want to add as reference.

2.5.6 Adding Basic Building Bricks under a DeviceModel

61850 Config User Guide (UCA 2.0 Specific) •9

The RTDX Point Selection dialog box appears.

2.5.7 Adding a Common Class under a DeviceModel

2.5.7.1 (DI) Device Identity

2.5.7.2 (AI) Analog Input

10 ● Chapter 2: Using 61850 Config

2.5.7.3 (SI) Status Input Single Bit

2.5.7.4 (AO) Analog Output

2.5.7.5 (BO) Binary Output

61850 Config User Guide (UCA 2.0 Specific) • 11

 Click on a reference point, to indicate the state of the selected point.

2.5.7.6 (ACF) Analog Configuration

2.5.7.7 (CCF) Control Configuration

2.5.7.8 (SBOCF) SBO Configuration

2.5.7.9 (d) Description

2.5.7.10 (basRCB) Basic Report Control Block

12 ● Chapter 2: Using 61850 Config