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.
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
ii ● Contents
EAS-SA QF-MKT-02 Rev.02
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.
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.1.2 GOMSFE
GOMSFE (Generic Object Models for Substation and Feeder Equipment) is standardized model of
devices in the electrical power industry.
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.
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.
The new logical device now appears in the left pane, and contains all the bricks you added using
the above process.
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
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.
To remove a reference:
Click the Remove button, in the right pane.
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.
Click the Select button of the dialog box.
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:
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 (GIND) Generic
Indicator.
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 binary input points, and you can associate a maximum
of 32 points with the brick.
Click the Select button of the dialog box.
This operation automatically creates the corresponding dataset for the report and adds it to the
Datasets folder.
2.5.6.3 GCTL
To add a GCTL:
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 (GCTL) Generic
Control.
2.5.6.4 GSPT
To add a GSPT:
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 (GSPT) Generic
Set Point.
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 output points, and you can associate a maximum
of 32 points with the brick.
Click the Select button of the dialog box.
This operation automatically creates the corresponding dataset for the report and adds it to the
Datasets folder.
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.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.
System The value of the point is related to specific information about the system.
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.
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.
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).
The Node Selection dialog box appears.
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.
Click the Select button of the dialog box.
Note that you can only refer to a data point on the same logical device.
OnDur Source = RTDX The amount of time the pulse stays ON.
I/O Type = BO
Value = State
UCA 2.0 type of the reference =
INT32U
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.
Put a checkmark in the Validate configuration on connection reset checkbox, if you want
the configuration to be validated whenever the connection is reset.
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.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.
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.
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.
The Node Selection dialog box appears.
In the dialog, click on the device point you want to associate with the data point.
Click the Select button of the dialog box.
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.
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.
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.
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.
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 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.
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.
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.
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).
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.
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.
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
identify the device point.
None.
If the checkbox does not contain a
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.
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.
If 61850 Config finds any errors, the Error Report dialog box appears, displaying the list of
errors found.
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.
The name is too long The data point has too long a name.
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.)
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 reference is invalid The item in the Datasets folder has an invalid reference in its Dataset
List.
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.
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.