Reference Manual

UCA 2.0 Slave Protocol

Documentation for part number P- SSPR-0801
© 2012 Cooper Power Systems, LLC – 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: [email protected]
Web: http://www.cooperpower.com

Technical Support: [email protected]

S1120-65-2, version 5
Contents
1. Introduction ............................................................................................................................. 1
2. Features.................................................................................................................................... 2
2.1 Communication ........................................................................................................................ 2
2.2 Supported MMS Services........................................................................................................... 2
2.2.1 Client Data Retrieval .................................................................................................. 2
2.2.2 Spontaneous Data ..................................................................................................... 2
2.2.3 Device Control ........................................................................................................... 3
2.2.4 Supported Data Types................................................................................................ 3
3. Configuration Settings ............................................................................................................. 5
4. Implementation Details ........................................................................................................... 6
4.1 Startup Sequence ..................................................................................................................... 6
4.2 Scan Cycle ............................................................................................................................... 6
5. Troubleshooting ....................................................................................................................... 7

UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL ●I

Tables
Table 2-1 Communication Features .................................................................................. 2
Table 2-2 Supported MMS Services .................................................................................. 2
Table 2-3 Control Request Processing .............................................................................. 3
Table 2-4 Supported Data Types ....................................................................................... 4
Table 5-1 Troubleshooting ................................................................................................ 7

UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL ● III

1. Introduction
This manual provides the information required to install and set up a UCA 2.0 slave protocol
component in an SMP Gateway.
This protocol component is used to provide data to any client compatible with the UCA 2.0
protocol definition.
You must be familiar with the SMP Gateway environment and the UCA 2.0 protocol specification
before proceeding with the document. This information can be acquired by reading the following
documents:
 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.
 61850 Config User Guide, S1120-19-5, Cooper Power Systems, LLC.
 SMP Gateway User Manual, S1120-10-1, Cooper Power Systems, LLC.

UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL ●1

2. Features
This chapter enumerates the features provided by the UCA 2.0 slave protocol component.

2.1 Communication
The following communication features are available when connecting clients to the SMP Gateway
hardware:

Feature Comment
TCP/IP The UCA 2.0 slave protocol component supports only TCP/IP.

Table 2-1 Communication Features

2.2 Supported MMS Services

UCA 2.0 services are mapped to MMS services. The following table enumerates the services
currently supported by the UCA 2.0 slave protocol component.

MMS Service UCA 2.0 Service

Initiate Initiate
Conclude Conclude
Abort Abort
GetNameList GetLogicalDeviceList
GetDataObjectsList
GetDataSetsList
GetCapabilityList GetCapabilities
Identify Identify
Read GetDataObjectValues
Write SetDataObjectValues
GetVariableAccessAttri GetDataObjectAttributes
butes
InformationReport SetDataObjectValues(Unconfirmed)

Table 2-2 Supported MMS Services

2.2.1 Client Data Retrieval

A Read indication is first received from the client. The data is then obtained from the
SMP Gateway and transformed to the UCA 2.0 protocol format.
All data is time-stamped by the system upon reception.
2.2.2 Spontaneous Data
The UCA 2.0 slave protocol component supports the Basic Report Control Block (BasRCB), as
defined in the Generic Object Models for Substation & Feeder Equipment (GOMSFE). The UCA 2.0
slave protocol component can provide these reports in order to send spontaneous data via the
InformationReport MMS service. The client must register with the slave component to receive the
information reports.

2● UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL

2.2.3 Device Control
Binary and analog outputs are used to control devices. The slave component receives Read and
Write requests. These requests are then translated to SMP Gateway format and published in the
system. The master component associated with the output point sends the request to the device.
The following table describes how system control requests are processed by the slave protocol
component.

System Request Processing

SBO Reads an SBO data object.
Open Writes 0 in a BO data object.
Close Writes 1 in a BO data object.
Pulse Writes in a BO data object. The OnDur setting related to the BO is
used to determine the length of the pulse.
Set Writes a value in an AO data object.

Table 2-3 Control Request Processing

2.2.4 Supported Data Types

The data type of a data object defines its format or structure. The following table enumerates the
UCA data types that are supported.

UCA Standard Description, Range of Values (if applicable)

DataType Name
BOOL Boolean — 1 bit, True (1) or False (0)
BSTR1 Bitstring — 1 bit
BSTR8 Bitstring — 8 bits
BSTR16 Bitstring — 16 bits
BSTR32 Bitstring — 32 bits
INT8U Unsigned integer — 8 bits, 0 to 255
INT16U Unsigned integer — 16 bits, 0 to 65,535
INT32U Unsigned integer — 32 bits, 0 to 4,294,967,295
INT8S Signed integer — 8 bits, -128 to +127
INT16S Signed integer — 16 bits, -32,768 to + 32,767
INT32S Signed integer — 32 bits, -2,147,483,648 to +2,147,483,647
FLT32 Floating point, IEEE format, single precision
FLT64 Floating point, IEEE format, double precision
VSTR8 Printable ASCII text string — 8 characters
VSTR16 Printable ASCII text string — 16 characters
VSTR32 Printable ASCII text string — 32 characters

UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL ●3

 UCA Standard Description, Range of Values (if applicable)
DataType Name
BTIME4 Number of ms since midnight — 4 bytes (GMT)
BTIME6 Number of ms since midnight, and days since January 1, 1984 — 6
bytes (GMT).
ENUM8 Enumerated value, 8 bits, signed — Well-known positive values,
0 always reserved and unused.
ENUM16 Enumerated value, 16 bits, signed — Well-known positive values,
0 always reserved and unused.
IDENT A printable ASCII text string representation of a DOReference —
identifies a DataObject or subcomponent of a DataObject in the server.

Table 2-4 Supported Data Types

4● UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL

3. Configuration Settings
Cooper Power Systems’ 61850 Config software program is used to define settings for the UCA 2.0
slave protocol component. The 61850 Config User Guide describe the configuration settings to be
specified for every UCA 2.0 slave protocol component instance.

UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL ●5

4. Implementation Details
4.1 Startup Sequence
The protocol component goes through the following steps on startup:
 Parses the configuration file.
 Initializes the various logs, traces and statistics.
 Refreshes all data objects with the values from the SMP Gateway.
 Initializes the communications link.
 Waits for incoming connections. On an incoming connection:
 Identifies the server.
 Starts the scan cycle.

4.2 Scan Cycle

Link initialization occurs under the following circumstances:

 The SMP Gateway is being restarted.
 A timeout has occurred.
 The communications link is being reset, due to 3 consecutive errors of any type.

Once the link has been initialized, and as long as it remains active, the protocol component uses
regular scanning cycles on a continuous basis. Note that the link is not considered active until the
device is identified.

The regular scanning cycle is as follows:

 If the RTDX data point has been changed, update the value in the slave component.
 If there is a report to be sent in this cycle that hasn’t been sent yet, send it.
 If there are no more reports to send, wait for the specified scan interval before beginning a
new cycle.

If the normal scanning cycle is abandoned to cause a link reset, all I/O points are tagged as
being defective due to a communications failure. Analog and binary input points become valid
again on an individual basis only when valid I/O data is received from the device. Analog and
binary output points become valid again as soon as the link is considered active.

6● UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL

5. Troubleshooting
The following table lists solutions to common problems experienced with the UCA 2.0 slave
protocol component.

Problem Solution
The SMP Gateway is This problem can be due to one of the following:
not communicating  There is a problem in the SMP Gateway configuration, which
with the control causes a startup failure.
center.
 The network path to the client is down.
 The remote client is down.
 The remote client is not trying to connect to the UCA 2.0 slave
component.
 The slave component is already connected to the maximum
number of clients.

The link to my device This problem can be due to one of the following:
keeps resetting.  The remote side has detected a change in the configuration.
 The remote client has reset the link.
 A timeout has occurred.

Table 5-1 Troubleshooting

UCA 2.0 SLAVE PROTOCOL REFERENCE MANUAL ●7