APPLICATION NOTE

SMP Gateway and AREVA MiCOM Relays

This application note describes the different applications of the SMP Gateway with
AREVA MiCOM relays.

It briefly presents the different MiCOM relay series and their features, notably the
communication protocols they implement and how data is organized and transmitted
through the Courier protocol. The note then describes how the SMP Gateway can
retrieve this data using the AREVA (Courier) master protocol and how to remotely
access the relays using the SMP Gateway Passthrough. Finally, it explains how to
SMP Config can extract the data point settings from a MiCOM relay to automatically
configure an AREVA (Courier) master.

Note: In this application note, the term “MiCOM relay” refers to any MiCOM
protection relay that use the Courier protocol and that is supported by the
AREVA (Courier) master protocol.

Quebec City
730 Commerciale Street
Contents
Suite 200
Saint-Jean-Chrysos tome, Quebec
The MiCOM Protection Relay Series ..............................................................2 
Canada G6Z 2C5
Phone: +1.418.834-0009 Features ............................................................................................................... 2 
Fax: +1.514.227. 5256 The Courier Database Architecture ......................................................................... 2 
Montreal
1290 St. Denis Street Using the AREVA MiCOM (Courier) Master Protocol......................................3 
Suite 300 Retrieving Real-Time Data ..................................................................................... 3 
Montreal, Quebec Configuring an AREVA (Courier) Master using SMP Config ................................. 4 
Canada H2X 3J7
Phone: +1.514.845. 6195
Using SMP Config to Extract Data Points Settings from a MiCOM Relay .............. 5 
Fax: +1.514.227. 5256 Limitations and Restrictions............................................................................. 6 
Retrieving SOE and DDF Records ........................................................................... 7 
www.c ooperpower.c om
Extracting Binary Data from SOE Records......................................................... 7 
© 2012 Cooper Power Systems, LLC Retrieving Configuration Information from the Relay ............................................... 7 
All rights reserved.
S1120-26-2, version 4
Remotely Accessing MiCOM Relays using SMP Gateway Passthrough .........8 
2013/06/04 Using MiCOM S1 Studio over a K-BUS-Based Passthrough Connection ...................... 8 

Additional References....................................................................................8 

1
SMP GATEWAY AND AREVA MICOM RELAYS COOPER POWER SYSTEMS, LLC

The MiCOM Protection Relay Series

MiCOM protection relays are divided into three different series (families): the 20, 30
and 40 series, respectively numbered Px2x, Px3x and Px4x. For example, the P821 is
part of the 20 series. One of the features that are common to relays of a given series
is the main protocol they implement. They also support other protocols, but they
often only support a limited set of features/functions.

The following table presents the main characteristics of each series.

Series Main Protocol Others (Limited) Specification

Px2x MODBUS Courier, DNP3, … Transmission and distribution

systems

Px3x IEC 60870-5- Courier, MODBUS, Feeder and transformer

103 … protection and control

Px4x Courier MODBUS, DNP3, … Wide range of protection

functions

Features
Monitoring and protection IEDs produce a lot of data, and MiCOM relays make no
exception. The following types of data can be produced by a MiCOM relay, depending
on the series/models:

ƒ Real-time data.
These are the current values and measurements recorded by the relay, such
as breaker statuses, phase voltages and line currents.
ƒ Sequence of Events (SOE) records.
A SOE record contains transitions with timestamps accurate to the
millisecond. These records are used to monitor fast changes, such as
recloser operations or a sequence of related status changes.
ƒ Disturbance Data Fault (DDF) event files.
DDF files are generated when some fault condition is encountered. High-
resolution sampling of analog measurements and related binary input states
recorded just before and after the fault are saved in such files.

The SMP Gateway can gather all of this data, using the AREVA (Courier) master
protocol.

The Courier Database Architecture

All data stored in a MiCOM relay, including its configuration settings, are organized
following the Courier database architecture.

The courier database is a table of as much as 256 rows and 256 columns. It contains
settings and data regrouped into columns. In each column, each cell contains a
specific setting or data item and is referenced using a unique address corresponding
to its row and column indexes. Indexes are zero-based and are specified as
hexadecimal values. For example, cell 0B10 is located on the 12th row (0B
hexadecimal, 11 decimal) and the 17th column (10 hexadecimal, 16 decimal).

Understanding this addressing scheme is important, as the configuration of the

AREVA (Courier) master protocol is based on it.

2
COOPER POWER SYSTEMS, LLC SMP GATEWAY AND AREVA MICOM RELAYS

Using the AREVA MiCOM (Courier) Master Protocol

This section describes how to use the AREVA (Courier) master protocol of the
SMP Gateway not only to read the actual values stored in MiCOM relays, but also
their SOE and DDF files.

The SMP Gateway supports MiCOM relays using the AREVA (Courier) master protocol
through an RS-232 or RS-485 interface. It only supports point-to-point with single
level addressing connections: multi-level addressing (where some relays are installed
as slaves to a master relay) is not supported.

MiCOM relays generally use the Courier protocol through a K-BUS interface,
consisting of a twisted pair of wires. This arrangement can support up to 32 devices
at a maximum distance of 1 KM. More recent relays directly support Courier through
an RS-485 serial link.

While similar to RS-485, K-BUS is not directly compatible and requires additional
processing by the SMP Gateway hardware. In consequence, AREVA (Courier) masters
can only be assigned to serial port A02 and A10 of an SMP 16. To assign an AREVA
(Courier) master to another port (including those available on SMP 16/SG serial
expansion modules), or to a serial port of an SMP 4, a KITZ 101 Courier Interface
Unit is required.

When planning the integration of an SMP Gateway with MiCOM relays, it is important
to validate the model and version of each relay to determine if converters will be
required.

Note: The front port of MiCOM relays directly supports the Courier protocol
through RS-232. However, the manufacturer does not recommend this port
for permanent connections.

Once connected to a MiCOM relay, the AREVA (courier) master can retrieve the
relay’s real-time data, but also SOE and DDF records.

Retrieving Real-Time Data

Data items are stored in the SMP Gateway as data points. It is assumed that the
value of a single data item is entirely contained into a cell. Therefore, to extract the
value of a data item from the content of a cell, the AREVA (Courier) master must be
aware of the cell’s address (row and column indexes), but also of the format of the
data.

Data stored in MiCOM relay data cells usually follow one of the following types:

ƒ Binary Flags.
Binary flags are a sequence of 1 to 4 bytes, where each bit has a distinct
meaning and takes either the 0 or 1 value, respectively meaning off (or false
or disabled) and on (or true or enabled).
In addition to the row and column indexes, the address of a binary flag also
includes a zero-based bit offset that designates the position of the flag in the
cell. For example, bit offset 8 designates the first bit of the second byte.
ƒ Unsigned /Signed Integer.
These are typical integer values, stored in up to four bytes. The size of the
value does not need to be specified at configuration time: this information is
reported with the value.
ƒ Courier Number.
This data type allows a dynamic range of numbers to be displayed with four

3
SMP GATEWAY AND AREVA MICOM RELAYS COOPER POWER SYSTEMS, LLC.

significant digits, a variable decimal point location and an inherent unit type
prefixed with a scalar multiplier.
ƒ IEEE Floating Point Number.
The format of values following this data type is based on the IEEE 754
(1985) standard for single-precision floating point numbers (4 bytes).
ƒ Indexed String.
This data type is used to translate values to strings and vice-versa. To use
this data type for a specific data point, a group of strings and their
respective values, called a “data group”, must be defined separately and
then assigned to the data point.
When configuring the data points of an AREVA (Courier) master, most of the effort
required is for the specification of the settings of each point, based on those data
types. The Areva (Courier) master supports the following data point types:

ƒ Analog inputs.
These data points are used to store the real-time values of all of the Courier
data types presented above, but are mostly used for integers, Courier
numbers and IEEE floating point numbers. These values are stored either as
floating point numbers (for the Courier Number and IEEE Floating Point
Number formats) or integers (for the Binary Flags, Signed/Unsigned Integer
and Indexed String formats); the Scale and Offset settings are then used
to calculate the other value, as follows:

floating point value = (integer value * scale) + offset

ƒ Binary inputs.
Binary input points are used to store binary flags and binary settings stored
as indexed string values. As binary flag cells are composed of up to 32 flags,
the Bit Offset setting must be specified to store the right flag in the
corresponding binary input point.
ƒ Analog outputs.
Analog output points are used to change setting values.
ƒ Binary outputs.
Binary output data points are used to change settings that are defined as
binary flags, and for breaker operations.

Configuring an AREVA (Courier) Master using SMP Config

There are three ways of creating an AREVA (Courier) master in SMP Config: using a
template, by extracting the data point settings directly from the relay or by starting
from scratch. Templates usually contain most of the general settings and data point
parameters that apply to all devices of a given manufacturer and model. For example,
Cooper Power Systems provides a template for the MiCOM P442.

When creating an AREVA (Courier) master using a device template, all master data
points are automatically created and configured, based on the default configuration
of the MICOM relay. The name of each data point can be modified to match private
naming convention; however, data points’ addresses and data types specified in
SMP Config must match the corresponding settings in the MiCOM Relay database.

Note: Templates are out of the scope of this document, as well as the creation of
new master protocols using SMP Config. For more details on these topics,
refer to the SMP Gateway User Manual, S1120-10-1.

During its initialization sequence, the AREVA (Courier) master can compare its
configuration with the one of the relay to make sure they match. This validation

4
COOPER POWER SYSTEMS, LLC SMP GATEWAY AND AREVA MICOM RELAYS

process is optional and can be configured using the Verify Configuration general
setting. It can also be performed each time the master resets its communication
sequence. At runtime, the master constantly makes sure that the format of the data
it receives still matches its own settings.

Using SMP Config to Extract Data Points Settings from a MiCOM Relay

SMP Config offers a configuration wizard to assist in the configuration of the AREVA
MiCOM (Courier) master protocol. To be able to use this wizard, there must be a
direct serial link between the PC that runs SMP Config and the MiCOM relay. This
feature is quite useful when a device template is not available for a specific relay
model.

Proceed as follows:

ƒ Using a direct serial RS-232 cable, connect the PC to the front port of the
MiCOM relay.
ƒ Start SMP Config.
ƒ In the left pane, under the Master Protocols branch, select AREVA
(Courier).
ƒ In the right pane, enter a name for the master and press ENTER.
ƒ In the left pane, expand the AREVA (Courier) branch, and then select the
master you just created.
ƒ Expand the master branch and select the General branch.

ƒ In the right pane, under Device Prefix, enter the character string that will
prefix the name of each data point of this master.
ƒ Under Device Address, enter the address of the relay, which is a number
ranging from 1 to 254. This address must match the one configured on the
relay.
ƒ Under Device Language, enter the language code specified in the relay
configuration. Refer to the relay’s documentation for a list of the languages
it supports and the corresponding codes.
ƒ From the Tools menu, select Import Points.

5
SMP GATEWAY AND AREVA MICOM RELAYS COOPER POWER SYSTEMS, LLC.

ƒ Under Communication Settings, enter the settings that correspond to the

ones configured on the relay for its front panel port.
ƒ Under Columns Selection, select the columns that contain the desired
data point settings, according to the relay’s documentation.
ƒ Click Connect to start interrogating the relay.

The Extraction in Progress dialog box appears. If it displays the

“Request: Empty frame” message without any other information, click
Cancel, and then verify the communication link and settings.
ƒ Once the extraction is complete, the Update Data Points dialog box
appears. Under Points to add, put a checkmark beside the data points to
add to the configuration or click All to add them all. Click Update to update
the configuration.

Note: The same procedure can be use to update an existing configuration, to add
or remove data points, or to update data point settings.

ƒ Back in SMP Config, adjust the data point settings if necessary. For example,
to change the Scale and Offset settings of an analog input, select and the
Analog Inputs branch, then the Physical branch: new values can be
specified for those settings in the right pane, for all physical analog inputs.

Limitations and Restrictions

No timestamps are provided with Courier data values (except for values extracted
from SOE, see below). In consequence, the AREVA (Courier) master uses the
SMP Gateway’s system time and applies it as the value timestamp on reception of a
new value.

Another limitation of the Courier protocol is the lack of queuing support for fast
changes; this means that if multiple changes occur between requests, only the latest
change is reported. Instead, MiCOM relays can record such transitions with
timestamps in Sequence of Events (SOE) records. SOE recording is a feature that
requires specific configuration on the relay, including the selection of the cells for
which changes will be recorded.

6
COOPER POWER SYSTEMS, LLC SMP GATEWAY AND AREVA MICOM RELAYS

Retrieving SOE and DDF Records

MiCOM relays can generate Sequence of Events (SOE) and Disturbance Data Fault
(DDF) records. Both types of records can be retrieved by the AREVA (Courier) master
and stored as event files either on a local folder of the SMP Gateway or to a shared
folder on a remote computer.

Event file retrieving is out of the scope of this document, but it is explained in details
in the SMP Gateway User Manual, S1120-10-1.

Extracting Binary Data from SOE Records

As discussed earlier, data values retrieved from MiCOM relay data cells are not time-
stamped: the AREVA (Courier) master uses the SMP Gateway’s system time to assign
a timestamp to each value it retrieves.

However, the MiCOM relay can store the same binary data values in SOE records, and
in this case, timestamps are provided by the relay for each value. When the
SMP Gateway’s AREVA (Courier) master retrieves a SOE record file, it can extract
those values and their corresponding timestamps, and then store them in the
gateway’s real-time database, in separate binary input points.

To configure binary input event points:

ƒ First, modify the relay’s configuration so the changes to the corresponding

data cell are recorded in an SOE. To learn how to modify the relay’s
configuration, refer to the relay’s documentation.
ƒ Start SMP Config.
ƒ In the left pane, under the Master Protocols branch, expand the AREVA
(Courier) branch.
ƒ Expand the master branch and the Binary Inputs branch.
ƒ Select the Events branch.

ƒ In the right pane, for each binary input event point, enter the settings as if it
was a standard physical binary input point. Pay attention to the addressing
settings and make sure these settings point to cells that are configured on
the relay to be reported in SOE records.

Retrieving Configuration Information from the Relay

The AREVA (Courier) master can also retrieve configuration information and relay
settings from the relay, through the Courier protocol, and store these settings to files.

7
SMP GATEWAY AND AREVA MICOM RELAYS COOPER POWER SYSTEMS, LLC.

For additional information, refer to the AREVA (Courier) Master Protocol Reference
Manual, S1120-26-1.

Remotely Accessing MiCOM Relays using SMP Gateway

Passthrough
The SMP Gateway Passthrough function allows a user to remotely access a MiCOM
relay for maintenance, using the relay’s own configuration and maintenance tool,
without interrupting the real-time data acquisition process performed by the AREVA
(Courier) master.

The following restrictions and limitations apply to the ARERA (Courier) master when
using passthrough connections with MiCOM relays:

ƒ For some MiCOM relays, once a SER record has been retrieved through a
passthrough connection, the AREVA (Courier) master might no longer be able to
detect and retrieve the record during its next event polling sequence.
ƒ While doing remote maintenance of MiCOM relay through a passthrough
connection, real-time data acquisition and event extraction by the AREVA
(Courier) master are slowed down.
ƒ If the passthrough connection is defined over a K-BUS communication link,
specific timeout values must be specified in MiCOM S1 Studio; otherwise, MiCOM
S1 Studio may not be able to properly communicate with the MiCOM relay over
the passthrough connection.

Using MiCOM S1 Studio over a K-BUS-Based Passthrough Connection

As stated above, if the passthrough connection is defined over a K-BUS
communication link, specific timeout values must be specified in MiCOM S1 Studio
Explorer.

These timeout settings are accessible in MiCOM S1 Studio, by double-clicking the

corresponding Connection branch in the Studio Explorer pane.

In the Edit Connection window, specify the following setting values:

ƒ Reset response time (ms): 2000

ƒ Response time (ms): 2000
ƒ Global transmit time (ms): 500

Additional References
For more information on the features and settings presented in this application note,
refer to the following documents:

ƒ SMP Gateway User Manual, S1120-10-1

ƒ AREVA (Courier) Master Protocol Reference Manual, S1120-26-1
ƒ Protocol Common Concepts Reference Manual, S1120-11-1