Reference Manual

SMP Gateway Protocol

Common Concepts
For use with SMP Gateway software version 6.3 or later.
Cooper Power Systems and Substation Modernization Platform are valuable trademarks of Cooper
Industries.
All brand and product names appearing in this document are the trademark or registered trademark
of their respective holders.

© 2013 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: PSMO-sales@cooperindustries.com
Web: http://www.cooperpower.com

Technical Support: eassupport@cooperindustries.com

S1120-11-1, Version 2
 Contents
1 Preface 1
1.1 Intended Audience .................................................................................................1
1.2 Overview ...............................................................................................................1
1.3 Additional Documentation ....................................................................................2
1.4 Getting Assistance .................................................................................................3

2 The SMP Gateway Software Architecture 5

2.1 The Master-and-Slave Protocol Model..................................................................5
2.1.1 Multiple Master Protocols for a Single Device .......................................6
2.1.2 Interconnections Protocol........................................................................6
2.2 The Real-Time Data eXchange (RTDX) ...............................................................6
2.3 System Components ..............................................................................................6
2.3.1 The SMP Gateway Automation Functions Component ..........................6
2.3.2 The SMP Gateway SoftPLC (CoDeSys) Component .............................7
2.3.3 The SMP Gateway Web Server ..............................................................7
2.4 Communication Components ................................................................................7
2.4.1 Serial Communication Components ........................................................7
2.4.2 IP Communication Components .............................................................8
2.4.3 Other Communication Components ........................................................8
2.5 SMP Gateway Configuration (PAR) Files ............................................................8
2.5.1 SMP Gateway Device Template (TPL) Files ..........................................8
2.5.2 Creating a Master Protocol Instance using a Template File ....................9
2.5.3 SMP Gateway CSV Files ........................................................................9
2.5.4 Comparing SMP Gateway Configuration Files ..................................... 10

3 RTDX Internals 11
3.1 Data Points .......................................................................................................... 11
3.1.1 Physical Data Points .............................................................................. 11
3.1.2 System Data Points ............................................................................... 11
3.1.3 Logic Data Points .................................................................................. 12
3.2 Data Point I/O Types ........................................................................................... 12
3.2.1 Analog Input Points............................................................................... 12

SMP Gateway Protocol Common Concepts Reference Manual ●i

 3.2.2 Binary Input Points ............................................................................... 12
3.2.2.1 Double-Bit Binary Input Points .............................................. 12
3.2.3 Analog Output Points ............................................................................ 12
3.2.4 Binary Output Points ............................................................................. 12
3.2.5 Protocol-Specific Data Point I/O Types ................................................ 12
3.3 Data Point Static Attributes ................................................................................. 13
3.3.1 Device Prefix and Naming Conventions for Data Points ...................... 13
3.4 Data Point Dynamic Attributes............................................................................ 14
3.4.1 Data Point Quality (RTDX Status) ........................................................ 14
3.4.2 RTDX Status (Quality) Flags ................................................................ 14
3.5 Control Operation Attributes and Messages ........................................................ 16

4 Connectivity 17
4.1 Link Initialization ................................................................................................ 17
4.1.1 Master Data Validity upon Link Initialization ...................................... 17
4.1.2 Preventing a Slave Protocol from Accepting Connections before
Master Data is Valid.............................................................................. 17
4.2 Link Availability and Activity ............................................................................. 18
4.3 Communication Failure ....................................................................................... 18
4.3.1 Link Reset ............................................................................................. 18
4.4 Link Redundancy ................................................................................................ 19
4.4.1 Setting up an Additional Link to an IED for Redundancy Purposes ..... 19
4.4.2 Setting up Additional Links to Master Stations for Redundancy
Purposes ................................................................................................ 20
4.5 IED Redundancy ................................................................................................. 21
4.5.1 Simplified IED Redundancy through Link Redundancy ....................... 22
4.5.2 Implementing IED Redundancy through Link Redundancy ................. 22
4.5.3 Implementing IED Redundancy using the Best-of Automation
Function ................................................................................................ 23
4.6 Passthrough Connections..................................................................................... 23
4.6.1 Data Acquisition Suspension for Passthrough Purposes ....................... 23
4.6.2 Setting up a Passthrough Connection to Suspend All Masters
during a Passthrough Session ................................................................ 24
4.6.3 Setting up a Passthrough Connection to Suspend Only One
Specific Master during a Passthrough Session ...................................... 24
4.7 Multidrop Connections ........................................................................................ 24
4.7.1 Multidrop Connection Scan Priority Levels .......................................... 24
4.8 Switched Connections ......................................................................................... 25
4.8.1 Switched Outgoing Connection Establishment Conditions ................... 25

ii ● Contents
 4.8.2 Switched Connection Termination Conditions ..................................... 26
4.8.3 Switched Connection Schedules ........................................................... 26
4.8.4 Switched Connection Activity Monitoring ........................................... 26

5 Device Data Retrieval 27

5.1 Data Acquisition .................................................................................................. 27
5.1.1 Data Retrieval by Polling ...................................................................... 27
5.1.2 General Interrogation ............................................................................ 27
5.1.3 Data Retrieval by Unsolicited Reporting .............................................. 28
5.1.4 Acquired Data Time-Tagging ............................................................... 28
5.1.5 Acquired Data Quality .......................................................................... 28
5.1.6 Out-of-Range and Over-Range Values ................................................. 28
5.2 Analog Data Processing ...................................................................................... 29
5.2.1 Retrieved Analog Data Conversion Using Scales and Offsets .............. 29
5.2.2 Analog Data Deadband ......................................................................... 29
5.3 Binary Data Processing ....................................................................................... 30
5.4 Data Reporting .................................................................................................... 30
5.4.1 Response to Polling ............................................................................... 30
5.4.2 Unsolicited Reporting ........................................................................... 30
5.4.3 Reported Analog Data Conversion Using Scales and Offsets ............... 30
5.4.4 Single-Bit Binary Inputs Reported as Double-Bit Binary Inputs .......... 31

6 Control Operations 33
6.1 Control Operation Types ..................................................................................... 33
6.1.1 Analog Control Operation Execution Types ......................................... 33
6.1.2 Binary Control Operation Execution Types .......................................... 33
6.2 Control Operation Processing .............................................................................. 34
6.2.1 Control Operation Confirmation and Validation ................................... 34
6.2.2 Control Operation Queuing ................................................................... 35
6.2.3 Control Operation Conversion .............................................................. 35
6.2.4 Control Operation Conversion using Paired Binary Output Points ....... 36
6.3 Local and Remote Control Operation Modes ...................................................... 37
6.3.1 Preventing Control Centers from Performing Remote Control
Operations ............................................................................................. 37
6.4 Control Operations over Multidrop Connections ................................................ 37
6.5 Control Operations Deactivation through System Data Points............................ 38
6.6 Binary Output Point Interlocking ........................................................................ 38
6.7 The SMP Gateway Control Log .......................................................................... 38

SMP Gateway Protocol Common Concepts Reference Manual ● iii

 7 IED File Retrieval 39
7.1 IED File Types .................................................................................................... 39
7.1.1 Other IED Files ..................................................................................... 39
7.2 System Folders .................................................................................................... 39
7.2.1 Defining Local System Folders ............................................................. 40
7.2.2 Defining Remote System Folders.......................................................... 40
7.3 Event File Retrieval Process ................................................................................ 41
7.3.1 Event File Retrieval Rules..................................................................... 41
7.3.2 Setting up Event File Retrieval ............................................................. 41
7.4 Configuration File Retrieval Process ................................................................... 42
7.4.1 Setting up Configuration File Retrieval ................................................ 42
7.5 IED File Headers ................................................................................................. 43
7.6 IED File Naming Convention .............................................................................. 43
7.7 IED File Time-Tagging ....................................................................................... 44

8 Advanced Features 45
8.1 Redundancy ......................................................................................................... 45
8.1.1 Hot-Standby Redundancy ..................................................................... 45
8.1.2 Allowing Hot-Standby Redundancy Support for a Slave Protocol ....... 46
8.2 Listen Mode ......................................................................................................... 46
8.3 Data Point Inhibition ........................................................................................... 46
8.3.1 Preventing an Output Point from Being Operated using the
Inhibition Automation Function ............................................................ 47
8.4 Data Point Value Forcing .................................................................................... 47
8.5 The SMP Gateway Integrated Firewall ............................................................... 48
8.5.1 SMP Gateway Firewall Access Rules ................................................... 48
8.5.2 Allowing Access to a Slave Protocol Only from Specific Master
Stations .................................................................................................. 48
8.6 Device Clock Synchronization ............................................................................ 48
8.7 SMP Gateway Clock Synchronization through Slave Protocols ......................... 49

9 Troubleshooting 51
9.1 Protocols Failed at Startup ................................................................................... 51
9.2 Acquired Values are Incoherent or Erroneous ..................................................... 52
9.3 Control Operation Fails ....................................................................................... 53
9.4 Protocol Communication Problems through a RS-232 Link ............................... 54
9.5 Protocol Communication Problems through an RS-485 Link ............................. 55
9.6 Protocol Communication Problems over an Ethernet Network ........................... 56

iv ● Contents
 9.7 Master Protocol Fails to Retrieve Event Files Available on Device.................... 56
9.8 Communication Link to an IED or Control Center Keeps Resetting .................. 57

10 Appendices 59

Appendix A - Master Protocol Common Settings Reference A-1

Master Protocol Common General Settings ................................................................................... A-1
Master Protocol Common Redundancy Settings ............................................................ A-3
Master Protocol Common Switched Connection Settings .............................................................. A-4
Master Protocol Common Switched Connection Schedule Settings ............................... A-5
Master Protocol Common File Settings .......................................................................................... A-6
Master Protocol Common Analog Input Settings ........................................................................... A-7
Master Protocol Common Binary Input Settings ............................................................................ A-9
Master Protocol Common Analog Output Settings ...................................................................... A-10
Master Protocol Common Binary Output Settings ....................................................................... A-12

Appendix B - Slave Protocol Common Settings Reference B-1

Slave Protocol Common General Settings...................................................................................... B-1
Slave Protocol Common Switched Connection Settings ................................................................ B-3
Slave Protocol Common Switched Connection Schedule Settings ................................. B-4
Slave Protocol Common Analog Input Settings ............................................................................. B-4
Slave Protocol Common Binary Input Settings .............................................................................. B-5
Slave Protocol Common Analog Output Settings .......................................................................... B-6
Slave Protocol Common Binary Output Settings ........................................................................... B-6

Appendix C - Additional Settings Reference C-1

System Folder Settings ................................................................................................................... C-1

Appendix D - System Data Point Reference D-1

Master Protocol System Data Points .............................................................................................. D-1
Slave Protocol System Data Points................................................................................................. D-3
Local/Remote Control Operation System Data Points ................................................................... D-4
System Folder System Data Points ................................................................................................. D-4

SMP Gateway Protocol Common Concepts Reference Manual ●v

 Figures
Figure 2-1 The master-and-slave protocol model........................................................................... 5
Figure 4-1 Typical IED link redundancy failover scenario .......................................................... 19
Figure 4-2 Typical IED redundancy failover scenario ................................................................. 21

SMP Gateway Protocol Common Concepts Reference Manual ● vii

 Tables
Table 2-1 Serial port interfaces ..................................................................................................... 7
Table 3-1 RTDX status flags ...................................................................................................... 15
Table 6-1 Control operation types .............................................................................................. 33
Table 6-2 Binary control operation execution types ................................................................... 34
Table 7-1 Event File Retrieval Rules .......................................................................................... 41
Table A-1 Master Protocol Common General Settings .............................................................A-3
Table A-2 Master Protocol Common Redundancy Settings ......................................................A-4
Table A-3 Master Protocol Common Switched Connection Settings ........................................A-5
Table A-4 Master Protocol Common Switched Connection Schedule Settings ........................A-6
Table A-5 Master Protocol Common File Settings ....................................................................A-7
Table A-6 Master Protocol Common Analog Input Settings .....................................................A-9
Table A-7 Master Protocol Common Binary Input Settings ....................................................A-10
Table A-8 Master Protocol Common Analog Output Settings ................................................A-12
Table A-9 Master Protocol Common Binary Output Settings .................................................A-13
Table B-1 Slave Protocol Common General Settings ................................................................ B-3
Table B-2 Slave Protocol Common Switched Connection Settings .......................................... B-4
Table B-3 Slave Protocol Common Switched Connection Schedule Settings........................... B-4
Table B-4 Slave Protocol Common Analog Input Settings ....................................................... B-5
Table B-5 Slave Protocol Common Binary Input Settings ........................................................ B-5
Table B-6 Slave Protocol Common Analog Output Settings .................................................... B-6
Table B-7 Slave Protocol Common Binary Output Settings ..................................................... B-7
Table C-1 System Folder Settings ............................................................................................. C-2
Table D-1 Master Protocol System Data Points ........................................................................D-3
Table D-2 Slave Protocol System Data Points ...........................................................................D-4
Table D-3 Local/Remote Control Operation System Data Points .............................................D-4
Table D-4 System Folder System Data Points ...........................................................................D-5

SMP Gateway Protocol Common Concepts Reference Manual ● ix

1 Preface

This reference manual provides detailed information on features and concepts that are common to
all master and slave protocol components available. It also describes all settings that are common
to these protocol components, and explains how to set up the less intuitive protocol features.
Protocol-specific features and settings are out of the scope of this document, and presented in
details in separate reference manuals.

1.1 Intended Audience

This document was designed as the definitive reference regarding the implementation and
configuration of protocol components within the SMP Gateway software architecture.
It is intended to users that need an exhaustive introduction to that aspect of the SMP Gateway
software, but also to more experienced users who want to learn about less known features and
advanced functionalities.

1.2 Overview
This manual is divided into the following chapters:
 Preface.
This is the current chapter, which present the purpose, scope and content of this manual, along
with a list of documents to consult for additional details, and technical assistance information.
 The SMP Gateway Software Architecture.
This chapter presents the various components of the SMP Gateway software, and their roles
per the protocol components.
 RDTX Internals.
This chapter focuses on the Real-Time Data eXchange (RTDX) database and the element at
the core of this component: data points.
 Connectivity.
This chapter regroups all concepts related to communication links and specialized
connections.
 Device Data Retrieval.
This chapter explains how the SMP Gateway software uses master protocol components to
retrieve real-time data from IEDs, and slave protocol components to report retrieved data to
control centers.
 Control Operations.
This chapter discusses how master and slave protocol instances handle control operations that
must be performed on output points.

SMP Gateway Protocol Common Concepts Reference Manual •1

  IED File Retrieval.
This chapter explains how the SMP Gateway retrieves event and configuration files from
IEDs.
 Advanced Features.
This chapter discusses additional protocol-related SMP Gateway features.
 Troubleshooting.
This chapter describes the most frequent problems encountered with the configuration or use
of SMP Gateway master and slave protocol components, and provides solutions or advices to
help users solving these issues.
 Appendices.
The appendices provide additional reference information about the protocol components, such
as lists of settings and system data points.

1.3 Additional Documentation

This document is part of the SMP Gateway documentation set, which is provided and installed as
part of the SMP Gateway Software & Tools package.
As a complement to this manual, separate reference manuals are available for each protocol
component, discussing additional features that are implemented for the corresponding protocol (or
that are implemented in a different manner), but also presenting each protocol-specific setting.
For additional information about the SMP Gateway software and the various SMP Gateway
models, refer to the following Cooper Power Systems manuals:
 SMP Gateway User Manual, S1120-10-1.
This manual describes all the steps required to configure any SMP Gateway model and to test
this configuration, explains how to connect the SMP Gateway to a control center and
substation devices, and describes the SMP Gateway’s advanced features.
 SMP 4 Installation Guide, S1120-12-1.
This guide gives you detailed instructions on installing and setting up the SMP 4.
 SMP 4/DP Installation Guide, S1120-14-1.
This guide gives you detailed instructions on installing and setting up the SMP 4/DP.
 SMP 16 Installation Guide, S1120-13-1.
This guide gives you detailed instructions on installing and setting up the SMP 16/CP or the
SMP 16/SG.
 SMP Gateway Automation Functions Reference Manual, S1120-16-1.
This manual provides all the information required to install and set up an instance of the
Automation Functions component in an SMP Gateway.
 SMP Gateway SoftPLC Reference Manual, S1120-17-1.
This manual explains how to install and set up the SMP Gateway SoftPLC runtime system,
along with its corresponding configuration tools and software libraries.
Also in the same documentation set, you will find technical notes that give additional information
about the most advanced features of the SMP Gateway, and application notes that will help you
use the SMP Gateway in your projects.

2● Chapter 1: Preface
1.4 Getting Assistance
If you have any question regarding the performance, application or testing of any component of
this SMP product, do not hesitate to contact us. Our staff will be pleased to assist you.
Technical Support
Cooper Power Systems
Energy Automation Solutions

Email: eassupport@cooperindustries.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.

SMP Gateway Protocol Common Concepts Reference Manual •3

2 The SMP Gateway Software
Architecture

This chapter presents the various components of the SMP Gateway software, and their roles per
the protocol components.

2.1 The Master-and-Slave Protocol Model

The SMP Gateway software architecture is based on the master-and-slave protocol model.
A typical automation system consists of a SCADA system (or control center), which is connected
to devices located in the substation. The SCADA regularly polls the devices in order to retrieve
device readings and statuses. The operator uses the SCADA system to perform control operations
on selected devices.
Since it is the control system that initiates data acquisition and control, it is considered to be the
master system. Since the substation devices respond to data acquisition and control requests, they
are considered slave systems. When inserting an SMP Gateway between the SCADA and the
devices, as a data concentrator, the gateway must play both roles: it becomes a slave system for
the SCADA, and a master system for the devices.

Figure 2-1 The master-and-slave protocol model

SMP Gateway Protocol Common Concepts Reference Manual •5

 The SMP Gateway internal architecture is based on a series of software components called
protocol components. These protocols are divided into two main categories:
 Slave protocol components.
Protocol components that implement all the functions necessary to process requests received
from a control center.
 Master protocol components.
Protocol components that implement the functions necessary to poll and operate devices.
A protocol component instance usually connects to a single device or control center (although
some of them support link redundancy), using a single standard or proprietary protocol.
Cooper Power Systems provides components for most standard protocols, such as DNP3,
MODBUS, IEC-60870-5-101/103/104 and IEC 61850, as well as a large number of proprietary
protocols for devices manufactured by SEL, GE, ABB, Schneider Electric and Alstom Grid, to
name only a few.

2.1.1 Multiple Master Protocols for a Single Device

Some devices make various data types available through different communication ports and
protocols; in this case, multiple different master protocol instances must be configured for a single
device.
For example, to retrieve events from an SEL relay in addition to real-time data, two master
protocol instances must be configured: the master protocol instance corresponding to the SEL
relay model (ex. SEL-551) and an SEL Events master protocol instance.

2.1.2 Interconnections Protocol

The Interconnections protocol was designed specifically for data exchanges between
interconnected SMP Gateways. It is also used by some other Cooper Power Systems products that
must interact with the SMP Gateway. It is available both as a master protocol component and a
slave protocol component.

2.2 The Real-Time Data eXchange (RTDX)

At the center of the SMP Gateway software architecture resides an internal database, called Real-
Time Data eXchange (RTDX).
RTDX is much more than a simple data store. Besides storing data point values, quality flags and
timestamps, it also provides the publishing and subscription mechanisms that allow efficient data
exchange between the internal data publishers (e.g. the master protocol components) and
subscribers (e.g. the slave protocol components).

2.3 System Components

In addition to master and slave protocols, the SMP Gateway software contains system components
that also interact with RTDX and the protocol components.

2.3.1 The SMP Gateway Automation Functions Component

The Automation Functions component extends the capabilities of existing devices by adding local
automation capabilities similar to what could be implemented using an external PLC. These
capabilities are usually not supported by the master protocol components.

6● Chapter 2: The SMP Gateway Software Architecture

 Automation Functions instances can use any physical, system or logic data point owned by a
master protocol; most functions also create their own logic data points, defined specifically for
these functions.

2.3.2 The SMP Gateway SoftPLC (CoDeSys) Component

The SoftPLC (CoDeSys) component makes the bridge between RTDX and an IEC 61131-3
SoftPLC application deployed on the SMP Gateway. It initializes and manages the logic data
points created specifically as outputs of the SoftPLC application logic; it also subscribes to
existing data points that are used as inputs by the same SoftPLC application logic.
SoftPLC applications are designed using the CoDeSys IDE, and provide more complex and
sophisticated automation capabilities than Automation Functions instances.

2.3.3 The SMP Gateway Web Server

The SMP Gateway web server provides full access to data points’ static and dynamic attributes,
through the browser-based eSMP application. This application also provides a commissioning tool
allowing users to force (simulate) data point values, and to perform control operations on master
output points.

2.4 Communication Components

Communication components implement the software portion of the communication links required
by protocol components to interact with devices and master stations.
Communication components are essentially of two types:
 Serial communication components
 IP communication components

2.4.1 Serial Communication Components

Serial communication components implement communication links through the SMP Gateway
serial ports.
The following serial port interfaces are available for protocol components:

Interface Description
Asynchronous Standard asynchronous communications, either via RS-232, RS-485 2-wire
(multidrop), or RS­485 4-wire.

Radio Serial radio communications through spread-spectrum radios, licensed-

frequency radios, and some custom radios.

K-BUS Multidrop communication link specific to the Courier protocol and mainly
(SMP 16 specific) used by MiCOM protection relays.
Specific hardware adaptors, called KITZ interface units, must be connected
between the SMP Gateway and relays that support this interface.
Note: Serial ports A02 and A10 of the SMP 16 supports K-BUS without a KITZ.

Table 2-1 Serial port interfaces

SMP Gateway Protocol Common Concepts Reference Manual •7

2.4.2 IP Communication Components
IP communication components implement communication links through the SMP Gateway
Ethernet ports.
Essentially, these communication components support the TCP/IP and UDP/IP protocols, and can
also be used for RAS (Remote Access Service) communications.

2.4.3 Other Communication Components

The SMP Gateway also supports some protocols that directly embed data into Ethernet data
packets, such as IEC 61850 GOOSE.

2.5 SMP Gateway Configuration (PAR) Files

SMP Gateway configuration (PAR) files contain the entire settings of the protocol, system, and
communication components of a given SMP Gateway, including data point and system folder
settings.
SMP Gateway configuration files are created and edited using the SMP Config application, which
is part of the SMP Tools suite.
IEC 61850-specific settings are also set in SMP Gateway configuration files, using the
61850 Config application that is also part of the SMP Tools suite.
Finally, when developing an IEC 61131-3 SoftPLC application for the SMP Gateway using the
CoDeSys IDE, it is possible to embed the corresponding boot application in the SMP Gateway
configuration file.

2.5.1 SMP Gateway Device Template (TPL) Files

Device template (TPL) files are essentially stripped down SMP Gateway configuration files that
contain only the settings and data point list of a single master protocol instance, for a given
protocol.
Device template files are created using SMP Config, and their use can greatly speed up the
configuration process of similar master protocol instances.
When creating a master protocol instance in SMP Config using a device template file, you only
have to specify the name and device prefix of the instance, select which points from the template
are required, and assign a connection to the instance.
Some device template files are provided with SMP Config. They are installed in the following
folder:

.\Users\Public\Documents\Cooper Power Systems\SMP Config\<version>\

Device Templates
(on Windows Vista, 7 or Server 2008)

OR

.\Documents and Settings\All Users\Documents\ Cooper Power

Systems\SMP Config\<version>\Device Templates
(on Windows XP or Server 2003)

where <version> is the version number of SMP Config used.

8● Chapter 2: The SMP Gateway Software Architecture

2.5.2 Creating a Master Protocol Instance using a Template File
Using a template to create a master protocol instance eases the task of configuring the master
protocol instance, by automatically entering most general settings and the point list for the
corresponding device.

To create a master protocol instance using a template file:

 In the left pane of SMP Config, expand the Master Protocols branch, and then select the
branch of the protocol for which you want to create an instance based on an available
protocol.
 From the Tools menu, choose New Instance from Template.
 Select the desired template, and then click Open.

 In the New Instance Name box, type the name of the master protocol instance to create.
 In the New Prefix box, type the device prefix that will be added to the name of this instance’s
data points.
 Click OK.

The new instance appears in the left pane.

 Adjust the instance’s settings, as required.
 Create and assign a new connection to the instance.

2.5.3 SMP Gateway CSV Files

The entire SMP Gateway configuration can be exported to a comma-separated values (CSV) file,
so it can be edited using a text editor or a spreadsheet application such as Microsoft Excel.
The edited CSV file can then be imported back in SMP Config, either for the same SMP Gateway
or a template for a new SMP Gateway configuration file.

Note: When exporting SMP Gateway configuration to a CSV file, pay attention to your
Windows regional settings. In some countries, the decimal point is written as a
comma instead of a period; as a result, if you try to open a CSV file in a
spreadsheet application such as Excel, the file content may not appear as
expected.

SMP Gateway Protocol Common Concepts Reference Manual •9

2.5.4 Comparing SMP Gateway Configuration Files
SMP Config does not allow the comparison of different versions of an SMP Gateway
configuration file. However, several comparison tools support the CSV format, making it possible
to compare two SMP Gateway configuration files that were exported to this format.

To compare two SMP Gateway configuration files:

 Open the first configuration file in SMP Config, using the appropriate version of the tool.
 From the File menu, choose Export.
 Select the folder where the CSV file should be saved.
 In the File name box, type the name of the file, and then click Save.
 Repeat these steps for the second configuration file.
 Compare both files together using the file comparison tool of your choice.

10 ● Chapter 2: The SMP Gateway Software Architecture

3 RTDX Internals

This chapter focuses on the Real-Time Data eXchange (RTDX) database and the element at the
core of this component: data points.

3.1 Data Points

At the core of RTDX lies the data point, which is the representation of a given element of data.
An RTDX data point has static and dynamic attributes. Static attributes are assigned at
configuration time and remains unchanged until the next configuration update. Dynamic attributes
are the properties that change through time.
Data points are usually classified according to their I/O type; however, they can also be classified
according to their use within the SMP Gateway system, which results in the following point types:
 Physical Data Points
 System Data Points
 Logic Data Points

3.1.1 Physical Data Points

A physical data point represents a measured value or state, which is provided by a device sensor or
actuator.
Physical data points are provided by master protocol instances, which retrieve their corresponding
values from the devices they are connected to.

3.1.2 System Data Points

A system data point represents a value that is specific to the SMP Gateway or one of its
components; it does not originate from an existing device.
System input points provide statistical data and current state information. System output points
provide an external control interface allowing operators to modify the current behavior of the
SMP Gateway.
For example, it is possible to temporarily deactivate control operations for all physical analog
inputs by operating a dedicated system binary output point; a corresponding system binary input
indicates if control operations are really deactivated for analog input points.

SMP Gateway Protocol Common Concepts Reference Manual • 11

3.1.3 Logic Data Points
Logic data points are system data points that are created in the SMP Gateway for automation logic
purposes, either for Automation Functions instance or for an IEC 61131-3 SoftPLC application.
They are used to store the result of a logic expression, either evaluated by an automation function
instance or by a SoftPLC application task; this result can then be reported to a master station
through a slave protocol.

3.2 Data Point I/O Types

Most of the times data points are categorized based on their input/output (I/O) type, which results
in the following data point types:
 Analog Input Points
 Binary Input Points
 Analog Output Points
 Binary Output Points
Additional point types, which are protocol-specific and based on the aforementioned types, are
also supported by RTDX.

3.2.1 Analog Input Points

Analog input points represent measured values and counters, as integer or floating-point values.

3.2.2 Binary Input Points

Binary input points represent state attributes, which takes the 0 (open) or 1 (close) value.

3.2.2.1 Double-Bit Binary Input Points

Double-bit binary input points are not much different from standard (single-bit) binary input
points, except that they are used to store two-state attributes (one in each bit).
Some protocols even use double-bit binary inputs for three-state attributes (e.g. 00, 01, and 10)
and four-state attributes (e.g. 00, 01, 10, and 11)
Double-bit binary input points are supported in RTDX, but not in every protocol; however, it is
possible to split a double-bit binary input into two single-bit binary inputs, for conversion
purposes.

3.2.3 Analog Output Points

Analog output points are also called setpoints; they represent integer or floating-point values that
can be set by a master station, through control operations.

3.2.4 Binary Output Points

Binary outputs are state attributes that can be set by a master station, through control operations.

3.2.5 Protocol-Specific Data Point I/O Types

Additional data point I/O types are also supported by RTDX, but only by a few protocols. Some of
them are specializations of the standard I/O types, while others are totally different.

12 ● Chapter 3: RTDX Internals

 The following list presents some of these protocol-specific data point I/O types:
 Counter Inputs (CIs) and Frozen Counter Inputs (FCIs).
Counter inputs are specialized analog inputs used mainly for statistic purposes; a frozen
counter input is usually mapped to each counter input, to store the current value of the counter
at a given moment, usually on user request. The DNP3 protocol, among others, supports these
I/O types.
 Accumulators.
Accumulators are similar to counter inputs, but are used to sum up analog values, rather than
reflecting an incrementing count. The VALMET (TEJAS) Series V protocol, among others,
supports this I/O type.
 Internal Indications (IINs).
Internal indications are bit fields used to regroup multiple state attributes; each bit they
contain is managed in RTDX as a separate binary input points. This I/O type is specific to the
DNP 3 protocol.
 Phasors.
Phasor measurements, per the IEEE standard C37.118 Synchrophasors for Power Systems,
are also supported by the SMP Gateway software; scalar components of each phasor can be
mapped to analog inputs in RTDX, so they can be made available through different slave
protocols or used as inputs to system components, such as automation functions or the
SoftPLC component.
 Arrays.
Arrays are simply groups of data points of a specific pre-configured size. All points belonging
to the same group must be of the same I/O type.

3.3 Data Point Static Attributes

Each data point has a set of static attributes, which are properties that do not change over time.
Most of these attributes, which includes the name and the description of the data point, are
specified as point settings.
Other examples of static attributes are scale factors and offset values, addresses and indexes, and
allowed control operations types.

3.3.1 Device Prefix and Naming Conventions for Data Points

A typical substation automation project requires the configuration of thousands of data points.
You can significantly reduce the effort by carefully planning how to name devices and data points.
Cooper Power Systems tools provide additional functionality if the names of data points are based
on some type of convention. For our engineering projects, we use a naming convention such as the
following:
 A data source name, such as the substation name (e.g. MAPLE, CEDAR).
 A voltage level (e.g. 220 or 25).
 A device name (e.g. L1 to indicate a line, T1 to indicate a transformer, F1 to indicate a feeder,
BUS for a bus bar).
 A signal name (e.g. V_phsA_mag to indicate the phase A voltage magnitude, A_phsA_mag to
indicate the phase A current magnitude, Pos_st to indicate the status of a breaker or a line
switch).
With such a convention, a data point called CEDAR_220_BUS_V_phsA_mag clearly indicates
the voltage magnitude of phase A on the 220 kV bus of the CEDAR substation. A data point

SMP Gateway Protocol Common Concepts Reference Manual • 13

 called MAPLE_025_F1_Pos_st indicates the status of the breaker switch of feeder 1 at the
Maple substation.

3.4 Data Point Dynamic Attributes

Data point dynamic attributes are data point properties that change over time. There are essentially
three dynamic attributes:
 State/Value.
The current state of a binary point, or the current value of an analog point; the value can be
expressed either as a raw value or in engineering units.
 Quality (RTDX Status).
This attribute gives additional information about the precision and quality of the state/value,
the status of the device (or sensor) that provided the value, and the quality of the timestamp.
 Timestamp.
The date and time at which the value or quality changed.
Dynamic attribute changes are called data point transitions.

3.4.1 Data Point Quality (RTDX Status)

Each data point value that is stored in the real-time database (RTDX) of an SMP Gateway is
tagged with a quality attribute called “RTDX status”. This attribute gives additional information
about the precision of the value, the state of the device (or sensor) that provided the value, or the
quality of the corresponding timestamp.
The RTDX status attribute consists in a 16-bit value divided into flags. The 12 less significant bits
are used to define the quality of the value, while the 4 most significant bits define the quality of
the corresponding timestamp. Each status bit (flag) is independent of the others (except for the
timestamp status flags), which means that a given value can be tagged with more than one status
flags at the time.

3.4.2 RTDX Status (Quality) Flags

The following table presents the RTDX status flags that are currently supported by the
SMP Gateway software and tools:

RTDX Status Flag Value Description

OK / Good 0x0000 Indicates that the value is valid.

Unknown 0x0001 Indicates that the corresponding data point exists within
RTDX, but that it was never updated by a master or system
component.

Restart 0x0002 Indicates that either the originating device or some other
(DNP3 specific) device along the reporting path is currently being restarted.
This implies that no valid status was retrieved for the
corresponding data point since the last SMP Gateway reset.

Communication 0x0004 Indicates that the connection with the originating device or
failure some other device along the reporting path is currently lost,
which implies that the value that is stored in RTDX for the
corresponding data point is the last reported value.

14 ● Chapter 3: RTDX Internals

 RTDX Status Flag Value Description
Forced 0x0008 Indicates that the reported value was not retrieved through
normal acquisition or by unsolicited reporting, but was
forced by a human operator or by some automated process
to provide “to the best of our knowledge” type information
with no other guarantee.

Bad hardware 0x0010 Indicates that the reported value is of a doubtful nature due
to known hardware problems. The value might be valid, but
cannot be guaranteed.

Over range 0x0020 Indicates that the reported value is outside its normal range.
(Analog specific) This is usually a direct indication that the value has reached
its maximum possible value (positive or negative), either
provided by a software component or a D/A converter
Another cause of the over range status is a possible loss of
precision resulting from a value conversion along the
reporting path (for example. by converting a 32-bit value to
a 16-bit value).

Bad reference 0x0040 Indicates that the reported value provides from an analog
(Analog specific) acquisition chain containing at least one invalid reference
channel. Best case is that the reported value is valid, but not
accurate.

Reserved 0x0080 Reserved for internal use.

Inhibited 0x0100 Indicates that the corresponding data point was logically
inhibited by a human operator or an automation process.

Out of range 0x0200 Indicates that the value is outside an expected range of
(Analog specific) values based on intrinsic hardware limitations.
An out-of-range value should be considered with caution,
since this is an abnormal condition that usually points to a
sensor defect or a physical installation issue.

Simulated 0x0400 Indicates that the reported value was not retrieved through
normal acquisition or by unsolicited reporting, but was
simulated by a human operator using the Commissioning
feature of the eSMP browser-based application.

Real-time clock (RTC) 0x2000 Indicates that the SMP Gateway provided the timestamp of
(Timestamp specific) the value.

Device time 0xC000 Indicates that the timestamp was reported by the device
(Timestamp specific) along with the value. It is assumed that the device clock is
properly synchronized with a reliable time source, and no
guarantee is provided in regards to the synchronization of
the device and SMP Gateway clocks.

Table 3-1 RTDX status flags

SMP Gateway Protocol Common Concepts Reference Manual • 15

3.5 Control Operation Attributes and Messages
In addition to data point attributes, RTDX manages the control operation attributes of the output
points and the various control operation messages that are exchanged by the slave and master
protocols when a control operation request is received by the SMP Gateway.

16 ● Chapter 3: RTDX Internals

4 Connectivity

This chapter regroups all concepts related to communication links and specialized connections.

4.1 Link Initialization

Link initialization consists in the successful establishment of the connection between a protocol
instance and the corresponding master station or device.
Following the initialization of the link, the first operation performed by most master protocols is a
general interrogation (GI) of the device, to retrieve the initial values and statuses of all data points.
Link availability and activity status data points are also updated at link initialization, along with
other protocol-specific system data points and statistics.

4.1.1 Master Data Validity upon Link Initialization

If a slave protocol instance accept master station connections as soon as the SMP Gateway
completes its startup, the master data points it is subscribed to may not be up-to-date per the actual
data points of the devices that provides them; this is the case if the corresponding master protocol
instances have yet to complete their first general interrogation (GI) scan. As a result, erroneous
data will be reported to the master station.
Master protocol instances can notify slave protocol instances that are subscribed to its data points
of the completion of the first GI operation, through the Notify When Ready general setting. Slave
protocol instances can then wait until all master data is valid before accepting connections from
control centers.

4.1.2 Preventing a Slave Protocol from Accepting Connections

before Master Data is Valid
You can configure each master protocol instance to notify the slave protocol instances when they
complete their first GI, and the slave protocol instances so they wait for these notifications before
accepting any master station connection.

To prevent a slave protocol from accepting connections before master data is

valid:
 In SMP Config, for each configured master protocol instance:
 Select the General settings branch.
 In the right pane, select Notify When Ready.
 For each slave protocol instance:

SMP Gateway Protocol Common Concepts Reference Manual • 17

  Select the General settings branch.
 In the right pane, click in the Wait for Init Timeout cell, and then type the maximum
amount of time, in milliseconds, the slave protocol instance must wait before accepting
master station connections, when first GI notifications from master protocol instances are
still pending.

4.2 Link Availability and Activity

A communication link is considered available when the protocol instance is currently connected to
a device or a master station, regardless of the activity level on the link.
An available link is considered active when it is used by a protocol component instance to
communicate with a master station or a device.
The link availability concept is at the core of the link redundancy feature, which requires two
available links to work properly: if the active link becomes unavailable, the second link must be
available to take over communications and become the new active link, with minimal impact to
the data retrieval process.

4.3 Communication Failure

From a master protocol perspective, a communication failure is declared when the device fails to
answer to a request within a protocol-specific time interval configured for that matter. Some
master protocols can also be configured to retry the transmission of the failed request before
declaring a communication failure.
When communication failure is declared for a master connection, the corresponding device data
points becomes invalid and data stops to be reported for these points as long as they keep their
Communication Failure status flag; device output points cannot be operated during the same
period.

Note: When a communication link recovers from failure, the RTDX status of output
points is automatically set to OK before the master protocol instance even gets a
value or status update about these points.

Some protocol components, such as the DNP3 master, can be configured to wait
for such an update before setting the RTDX status of the output points to OK, ,
using the Group Comm Ok setting.

From a slave protocol perspective, a communication failure is declared when the master station
fails to answer to an unsolicited report, or when it remains inactive for a period of time exceeding
the value of the Inactivity Timeout setting; it will not be possible to perform control operations
through this slave protocol instance until the re-establishment of the connection.

4.3.1 Link Reset

When a communication failure is declared by a master protocol and according to protocol-specific
rules, the master protocol may perform a link reset, terminating the current communication session
before trying to establish a new one.
For example, this means that a master protocol instance may try to send a request to the device,
but without getting an appropriate response from the device; after retrying a pre-configured
number of times, it would reset the communication link.

18 ● Chapter 4: Connectivity
 Following a link reset, a master protocol instance will attempt to reconnect to the device at a pre-
configured protocol-specific frequency. A slave protocol instance will wait for the master station
to reconnect.

4.4 Link Redundancy

Link redundancy is a feature that, when supported, allows a master protocol instance to connect to
a given device through two different communication links. Only one link, the active link, is used
by the master protocol instance at a time; if the active link fails for any reason, the other (standby)
link is activated with minimal data loss (if any, depending on the protocol used).

Figure 4-1 Typical IED link redundancy failover scenario

To support link redundancy, an IED must be capable of accepting two different connections,
regardless of their connection type (for example, one may be a link serial and the other, a TCP/IP
connection).

Note: Link redundancy must not be confused with IED redundancy, which involves the
connection of the SMP Gateway to two separate devices.

Link redundancy is also supported for some slave protocols; however, it is implemented as
“additional instances” providing the same real-time data as the main slave protocol through
different communication links. As a result, slave link redundancy can be used both for redundant
links to a single master station, and for separate links to multiple master stations.

4.4.1 Setting up an Additional Link to an IED for Redundancy

Purposes
Redundant links to an IED can be configured if both the protocol used and the IED support this
feature.

SMP Gateway Protocol Common Concepts Reference Manual • 19

 Note: Refer to the corresponding master protocol reference manual to determine if it
supports link redundancy.

To set up an additional link to an IED for redundancy purposes:

 Configure the master protocol instance following the usual procedure, by specifying the
instance and data point settings; the provided general settings will be used by the first
connection.
 Select the Redundancy branch, and provide the following link redundancy settings:
 Select Enabled.
 If the first link must have precedence over the second one, when both links are available,
select Link 1 Preferred; this is the case if the first link is faster or more reliable.
 In the Link 1 Test Interval, type the delay, in milliseconds, between two complete link
test requests on the first link.
 In the Link 2 Test Interval, type the delay, in milliseconds, between two complete link
test requests on the second link.
 Specify the remaining settings of the Redundancy branch, which will be used by the
second connection and which are protocol-specific; refer to the corresponding master
protocol reference manual for the complete description of these settings.
 Define both communication links in the Connections branch, and assign these connections to
the master protocol instance in the Connection Usage branch; the usual master protocol
instance will now appear twice in the Connection Usage pane, to allow the assignment of
both connections.

4.4.2 Setting up Additional Links to Master Stations for

Redundancy Purposes
Slave link redundancy can be used both for redundant links to a single master station, and separate
links to multiple master stations; both scenarios are configured in a very similar manner.

To set up additional links to master stations for redundancy purposes:

 Configure the slave protocol instance following the usual procedure, by specifying the
instance and data point settings; the provided general settings will be used by the first
connection.
 For each additional link, define the corresponding general settings in the General (Additional
Instances) branch; use one row per additional link, and refer to the corresponding slave
protocol reference manual for a complete description of the protocol-specific settings.
 Define all communication links in the Connections branch, and assign these connections to
the slave protocol instance in the Connection Usage branch; the primary instance and the
additional ones all appears in the Connection Usage pane, to allow the assignment of all
connections.

20 ● Chapter 4: Connectivity
4.5 IED Redundancy
To improve reliability of their monitoring systems, utilities can use multiple protection IEDs to
monitor their breakers (also called “A-B protection”): this approach is called IED redundancy.
If an IED malfunction is caused by a specific hardware or software design problem, chances are
good that the second IED will display the same erratic behavior; for this reason, utilities normally
use IEDs from different manufacturers, for maximum reliability.

Figure 4-2 Typical IED redundancy failover scenario

The standard approach to implementing IED redundancy on the SMP Gateway is to configure it so
it polls both IEDs simultaneously with two different master protocol instances, and to use a Best-
of automation function instance to report the master data through single data points.
The rationale behind the use of the best-of automation function is to reduce the amount of data
points transmitted to the master station, and to keep the decisional logic as close as possible to the
redundant IEDs.
The best-of automation function implies the creation of one new logic data point per physical data
point provided by the master protocol instances; as a result, each device input/output is mapped to
three points: one physical data point per master protocol, each one provided by their respective
redundant IEDs, and a third (logic) data point called the “best-of” data point. The master station
should only be monitoring this best-of data point.
The value and quality of the best-of data point is determined as follow:
1. If the quality of the first data point evaluates to OK, then the value and quality of this point is
copied to the best-of data point.
2. Otherwise, if any bad quality flag is raised for the first point (communication failure, bad
hardware, etc.) and the quality of the second point evaluates to OK, then the value of the
second point is copied to the best-of data point.
3. If the quality of both data points is bad, the value and quality of the first point will be copied
to the best-of point.
This IED redundancy implementation presents the following characteristics:
 The best-of automation function can be used with any protocol. It requires the Automation
Function component to be a part of the SMP Gateway license.

SMP Gateway Protocol Common Concepts Reference Manual • 21

  The two IEDs of a redundant pair can use different protocols. For example, the first
protection IED can use DNP3, while the second one uses IEC 60870-5-101, even if there are
slight differences in the data map.
 It is a point-by-point redundancy. This means that it allows for any failure in the acquisition
path, as the logic used to determine the quality and value of the data point is not based on the
current state of the communication link or on the availability state of the IEDs: it is the
responsibility of the automation function component, and it is based on the quality of the
source data points.
 Binary or analog control operations can also be performed on the best-of points. When a
control operation is performed on a best-of output point, it is applied to the first point for
which the quality evaluates to OK, starting with the preferred one (if any).

Note: You can also use the Grouped Control automation function to perform the control
operation on both source points, instead of the best-of point.

4.5.1 Simplified IED Redundancy through Link Redundancy

When two redundant IEDs share the same data map and use the same protocol, the preferred
solution is to use a single master protocol instance with redundant communication links.
This solution requires less configuration effort, because only one set of data points is required
compared to the 3 sets of data points of the standard approach, which is implemented using two
master protocol instances and a Best-of automation function instance.

4.5.2 Implementing IED Redundancy through Link Redundancy

To implement IED redundancy through link redundancy:
 Configure a single master protocol instance following the usual procedure, by specifying the
instance and data point settings; the provided general settings will be used to communicate
with the first IED.
 Select the Redundancy branch, and provide the following link redundancy settings:
 Select Enabled.
 If the first IED must have precedence over the second one, when both IEDs are available,
select Link 1 Preferred; this is the case if the first link is faster or more reliable.
 In the Link 1 Test Interval, type the delay, in milliseconds, between two complete link
test requests on the link to the first IED.
 In the Link 2 Test Interval, type the delay, in milliseconds, between two complete link
test requests on the link to the second IED.
 Specify the remaining settings of the Redundancy branch, which will be used to
communicate with the second IED, and which are protocol-specific; refer to the
corresponding master protocol reference manual for the complete description of these
settings.
 Define both communication links in the Connections branch, and assign these connections to
the master protocol instance in the Connection Usage branch; the usual master protocol
instance will now appear twice in the Connection Usage pane, to allow the assignment of
both connections.
 In the slave protocol instances configuration, subscribe to the master data points, as usual.

22 ● Chapter 4: Connectivity
4.5.3 Implementing IED Redundancy using the Best-of
Automation Function
If two redundant IEDs use different protocols or do not share the same data mapping, you must
use two separate master protocol instances and a Best-of automation function instance to
implement IED redundancy on the SMP Gateway.

To implement IED redundancy using a Best-of automation function instance:

 Configure both master protocol instances following the usual procedure, by specifying the
instance and data point settings.
 Define both communication links in the Connections branch, and assign these connections to
their respective master protocol instances in the Connection Usage branch.
 Configure the Best-of automation function instance, as follow:

Note: The following procedure contains high level tasks, which are explained in details
in the SMP Gateway Automation Functions Reference Manual. Only settings that
are specific to this IED redundancy scenario are presented here.

 Define an Automation Functions instance and specify its general settings.

 Define one logic data points for each physical data point pair (one from each IED, which
represent the same input or output).
 Define one Best-of automation function for each physical data point pair:
 In the Result Point cell, type the name of the corresponding logic data point you just
defined for the pair.
 In the Point 1 and Point 2 cells, type the name of the corresponding physical data
points (one from each IED/master); these data points must be of the same type as the
logic data point.
 Specify the remaining settings as required.
 In the slave protocol instances configuration, subscribe only to the logic data points.

4.6 Passthrough Connections

Passthrough is the SMP Gateway feature that allows the establishment of transparent (virtual)
connections between desktop (or browser-based) applications and devices connected to the
SMP Gateway. It removes the need for a dedicated computer physically connected to the device,
thus allowing remote maintenance of these devices through the SMP Gateway.
For additional information about the Passthrough feature, refer to the SMP Gateway User Manual.

4.6.1 Data Acquisition Suspension for Passthrough Purposes

The passthrough feature can be used even if a master protocol instance is already connected to the
device. However, depending on the communication protocol used, it may be necessary to suspend
the master protocol instance or even all the master protocol instances sharing the same
communication links (for example, in a multidrop configuration), in order to establish the
passthrough connection.

SMP Gateway Protocol Common Concepts Reference Manual • 23

4.6.2 Setting up a Passthrough Connection to Suspend All
Masters during a Passthrough Session
If all master protocol instances sharing the same communication link as a passthrough connection
interfere with passthrough communications, the passthrough connection must be configured to
suspend data acquisition for all of these master protocol instances for the duration of the
passthrough session.

To set up a passthrough connection to suspend all masters during a passthrough

session:
 In the left pane of SMP Config, expand the Passthrough branch, and then select the
Connections branch.
 In the row of the passthrough connection to modify, select Suspend Link.

4.6.3 Setting up a Passthrough Connection to Suspend Only

One Specific Master during a Passthrough Session
If only one master protocol instance between those sharing the same communication link as a
passthrough connection interferes with passthrough communications, the passthrough connection
must be configured to suspend data acquisition for all of these master protocol instances for the
duration of the passthrough session.

To set up a passthrough connection to suspend only one specific master protocol

instance during a passthrough session:
 In the left pane of SMP Config, expand the Passthrough branch, and then select the
Connections branch.
 In the row of the passthrough connection to modify, select Suspend IED.
 In the IED Address cell, type the identifier of the device, per the protocol specifications. This
identifier can be found in the general settings of the master protocol instance.

4.7 Multidrop Connections

Multidrop connections allows multiple master protocol instances to share a single serial
communication port on the SMP Gateway so each of them can communicate with its own
corresponding device, over the same RS-485 communication link.
Protocols that identify devices using addresses or other numerical identifiers usually support the
feature; refer to the corresponding protocol reference manual to verify if it is the case.

4.7.1 Multidrop Connection Scan Priority Levels

Each master protocol instance is assigned a scan priority level, through the Scan Priority general
setting. This priority level determines the precedence of this instance over lower priority master
protocol instances in regards to the transmission of scan requests over the same shared multidrop
link. The highest priority level is 0.
For example, if two master protocol instances that share the same multidrop connection must poll
their respective device at the same time, the high priority instance will get access to the connection
before the other one, which will have to wait until the first instance complete its polling operation.

24 ● Chapter 4: Connectivity
4.8 Switched Connections
Switched connections allow the SMP Gateway to establish connection with devices and control
centers sporadically or periodically, rather than permanently, during short periods. A protocol
instance configured to use a switched connection is said to be in Switched Mode.
This feature is mostly designed to be used with modems, for the purpose of retrieving data from a
remote device, and is available only if supported by the protocol.
Up to two switched connections can be assigned to a protocol instance:
 An incoming connection, which is established when a slave protocol instance receives an
incoming call from a control center or when a master protocol instance receives an incoming
call from a device.
 An outgoing connection, which is used by a slave protocol instance to call a control center, or
by a master protocol instance to call a device.
For a master protocol instance configured in Switched Mode, the main connection is the outgoing
connection; it will accept incoming connections by default, although it is possible to configure it
to refuse them. From the master protocol perspective, incoming connections are used for device
data retrieval by unsolicited reporting.
For a slave protocol instance configured in Switched Mode, the main connection is the incoming
connection; it can be configured to accept outgoing connections, although it is not the default
behavior. From the slave protocol perspective, outgoing connections are used for unsolicited data
reporting to the control center.

4.8.1 Switched Outgoing Connection Establishment Conditions

A master protocol instance will establish an outgoing connection to a device if one of the
following conditions is met:
 The SMP Gateway completes its startup.
 It receives a control operation request from a slave protocol instance, which must be
performed on the device.
 It must perform a general scan, per the polling interval settings specified for this protocol
instance.
 It must establish a connection with the device, according to the Switched Connection
Schedule settings specified for this protocol instance.
 It is ready to perform a connection retry, following a connection establishment failure and
according to the Max Retries and Retry Delay settings.
 Any other protocol-specific condition; for example, the master protocol may be configured to
synchronize the device clock with the SMP Gateway clock on a regular basis.
A slave protocol instance will establish an outgoing connection to a control center if one of the
following conditions is met:
 The SMP Gateway completes its startup; the slave protocol instance may wait for the
subscribed master data to be valid before initiating the call, if configured to do so.
 The slave protocol instance is configured for unsolicited reporting and data changes are ready
to be reported to the control center.
 It must establish a connection with the control center, according to the Switched Connection
Schedule settings specified for this protocol instance.

SMP Gateway Protocol Common Concepts Reference Manual • 25

  The slave protocol is ready to retry to establish an outgoing connection with the control
center, following a connection failure and according to protocol-specific retry settings.
 Any other protocol-specific condition; for example, the slave protocol may be configured to
request time information from the control center on a regular basis, in order to synchronize
the SMP Gateway clock with the control center clock.

4.8.2 Switched Connection Termination Conditions

A switched connection is terminated when one of the following conditions is met:
 No significant information is exchanged for pre-configured period, which results in an
inactivity timeout.
 The maximum communication timer expires (defined by the Max Comm Timeout setting);
in this case, note that the communication session is terminated even if significant data is still
being exchanged between the master protocol instance and the device.

Note: No setting corresponding to the Max Comm Timeout setting exists for slave
protocol instances; however, the same mechanism may be implemented in a
control center.

 Communication errors are detected over the link, which is declared as failing.

4.8.3 Switched Connection Schedules

A switched connection schedule defines a period during which a protocol instance configured in
Switched Mode will perform outgoing calls to its corresponding control center or device, on a
regular basis.
For example, it is possible to configure a master protocol instance to call its corresponding device
every 30 minutes between noon and 6:00AM.

4.8.4 Switched Connection Activity Monitoring

For master protocol instance configured in Switched Mode, some data points can be configured to
serve as indicators of the connection activity, using the point-specific Monitor Activity setting.
When this setting is active for a given data point, a switched connection will be terminated if no
significant data change is detected on this point during the period defined by the Inactivity
Timeout switched connection setting. For analog points, the Comm Deadband setting is also
taken into account when determining if a data change is significant or not, in addition to the
standard deadband setting.

26 ● Chapter 4: Connectivity
5 Device Data Retrieval

This chapter explains how the SMP Gateway software uses master protocol components to
retrieve real-time data from IEDs, and slave protocol components to report retrieved data to
control centers.

5.1 Data Acquisition

Data acquisition is the operation by which master protocol instances retrieve real-time data from
devices, and store it into the SMP Gateway internal database (RTDX), as data point values. A
timestamp and quality attributes called RTDX status flags are assigned to these values, which may
also be processed according to master-specific settings before being injected into RTDX.

5.1.1 Data Retrieval by Polling

Most master protocols retrieve data from devices by polling them at a pre-configured frequency.
The implementation of this feature varies widely from one protocol component to another, and
also according to the device specifications. A master protocol may be configured to request the
latest values of all data points, even of those which did not change since the last scan: this
operation is called a general interrogation (GI). Some other protocols may request to receive all
state changes that occurred on binary points, to ensure that no transition is loss: this is called data
retrieval by exception, and it can also applies to analog data changes.
Refer to the corresponding protocol reference manual to determine its actual implementation of
data retrieval by polling, if this feature is supported by this protocol.

5.1.2 General Interrogation

General interrogation (GI) designates the operation performed by a master protocol instance to
retrieve the current values of all its data points from the device.
General interrogations are usually performed at link initialization, which occurs at startup or
following a communication link failure. They can also be performed at a given frequency.
Master protocol instances can notify slave protocol instances that are subscribed to its data points
of the completion of the first GI operation, through the Notify When Ready general setting, so
they can wait until all master data becomes valid before accepting connections from control
centers.

SMP Gateway Protocol Common Concepts Reference Manual • 27

5.1.3 Data Retrieval by Unsolicited Reporting
In an effort to reduce bandwidth usage, most recent protocols allow data retrieval by unsolicited
reporting, which means that devices report data to their respective control centers when they need
to, according to specific rules, instead of waiting for the control center to request it.
Unsolicited reporting rules vary according to the protocol specifications and the current
configuration of the device and the corresponding master protocol instance.
Refer to the corresponding protocol reference manual to determine its actual implementation of
unsolicited reporting, if this feature is supported by this protocol.

5.1.4 Acquired Data Time-Tagging

Acquired data is time-stamped. The timestamp is supplied by the device if it has time-stamping
capabilities and if the protocol allows the transmission of such information; otherwise, it is
automatically provided by the SMP Gateway based on current acquisition time.
Timestamps are stored in RTDX in the UTC format.
If the device provides timestamps adjusted to local time, the corresponding master protocol
instance must be configured so it can convert these timestamps to UTC time. Additionally, if the
device clock is automatically adjusted for daylight savings, the master protocol instance must also
be configured properly to handle this adjustment.

5.1.5 Acquired Data Quality

RTDX status flags are assigned to all acquired data, based on the information provided by the
device.

5.1.6 Out-of-Range and Over-Range Values

The Out-of-Range and Over-Range RTDX status flags are similar, but refer to two different (but
not mutually exclusive) situations.
A value is declared out-of-range when it is outside its normal range. This is usually a direct
indication that the value has reached its maximum possible value (positive or negative), either
provided by a software component or a D/A converter.
Another cause of the over range status is a possible loss of precision resulting from a value
conversion along the reporting path (for example. by converting a 32-bit value to a 16-bit value).
A value is declared over-range when it is outside an expected range of values based on intrinsic
hardware limitations.
For example, consider a sensor that produces a ±4 V signal, although the actual limitation of the
hardware is ±5 V. No status flag would be raised for a 3.9 V value; however, a 4.1 V value would
raise the Out-of-Range” flag, while a 5.0 V value would raise both the Out-of-Range and Over-
Range status flags.
An out-of-range value should be considered with caution, since this is an abnormal condition that
usually points to a sensor defect or a physical installation issue.

28 ● Chapter 5: Device Data Retrieval

 Note: These status flags should not be confused with alarm and warning thresholds
that may be defined by users and operators.

Based on the example above, the user may decide that any value larger than
3.0 V should trigger an alarm. That does not necessarily means that the value is
incorrect, but that the operators should have a closer look to the originating
device.

5.2 Analog Data Processing

Analog data consists of measured values. The system keeps two values for each analog measure
obtained: a raw value, which is essentially a sensor value, and a calculated value expressed in
engineering units, which is obtained by applying a scale factor and an offset value to the raw
value.
Depending on the protocol, the retrieved value of an analog data point may be the raw value or the
engineering value. The other value is then calculated using the Scale and Offset setting values that
are specified for the point in the master protocol settings.

5.2.1 Retrieved Analog Data Conversion Using Scales and

Offsets
The following formula is used to calculate the engineering value based on a retrieved raw value:
Engineering value = raw value X scaling factor + offset
The following formula is used to calculate the raw value based on a retrieved engineering value:
Raw value = (engineering value – offset) ÷ scaling factor
For some protocols, additional pre-processing scaling factor and offset settings, called Input Scale
and Input Offset, are also available for each point, and are applied directly to the retrieved value.
The resulting formulas are:
Engineering value = ((raw value X input scale + input offset) X
scaling factor) + offset
Raw value = ((eng. value X input scale + input offset) -
offset) ÷ scaling factor
When the Input Scale and Input Offset pre-processing settings are applied to retrieved values:
 The original value retrieved from the device is lost, as it will not be stored in RTDX.
 The calculation is always done using floating-point values, as this is the format of the pre-
processing settings.
 The intermediate result, resulting from the sole application of the Input Scale and Input
Offset pre-processing settings, is stored in RTDX in the same format as the original retrieved
value. If the original value was a raw value, the intermediate result is then formatted to a 32-
bit value.
 The final value is stored in RTDX in the remaining format.

5.2.2 Analog Data Deadband

Analog data can change often and sometimes very slightly. To filter engineering value changes
that are smaller than a certain amount, the SMP Deadband setting can be specified for each
analog data point. When such setting is specified, only engineering value changes larger than this

SMP Gateway Protocol Common Concepts Reference Manual • 29

 deadband value are considered by the master protocol instance and injected into RTDX; other
values are discarded.
When the value itself is smaller than the deadband, all value changes are considered by the master
protocol and injected into RTDX. This ensures that small variations around 0 are reported so that,
for example, reported values do not remain fixed at .01 when they are, in fact, 0.

5.3 Binary Data Processing

For obvious reasons, binary data requires less processing than analog data before it is injected into
RTDX.
Still, the state attribute of a single-bit binary input point can be inverted by the master protocol
instance.
The master protocol instance is also responsible for the processing of double-bit binary inputs,
when their values must be split into two single-bit binary inputs.

5.4 Data Reporting

Data reporting is the operation by which slave protocol instances report real-time data from the
RTDX database to control centers. This data is mostly retrieved from devices by master protocol
instances, but some is also generated by the SMP Gateway system components, either as system
information or as the result of logic operations on device data.

5.4.1 Response to Polling

Slave protocol instances mostly report data by responding to control center requests.
The implementation of this feature varies widely from one protocol component to another, and
also according to the device specifications.
As this type of data reporting is initiated by the control center, there is usually not much to
configure on the slave protocol side, except for some timeout settings.
Refer to the corresponding protocol reference manual to determine the actual implementation of
response-to-polling for the selected slave protocol, if this protocol supports this feature.

5.4.2 Unsolicited Reporting

A slave protocol that supports unsolicited reporting can be configured so it reports data value
changes without having to wait for a request from the control center. The main benefit of this
feature is that it requires less bandwidth compared to polling response, and it is recommenced to
use this reporting method on switched connections.
Refer to the corresponding protocol reference manual to determine the actual implementation of
unsolicited reporting for the selected slave protocol, if this protocol supports this feature.

5.4.3 Reported Analog Data Conversion Using Scales and

Offsets
Most of the time, the control center has no need for the raw data retrieved from the devices by the
master protocol instances. As a result, in most slave protocols, no additional processing is required
on the analog data to report: the slave protocol instance use the latest engineering value for each
data point and report them “as-is” to the control center.

30 ● Chapter 5: Device Data Retrieval

 Some slave protocol instances provide a scale factor and an offset value, which can be applied
using a formula that is similar to the one used by master instances, but reversed:
Reported value = (RTDX value – Offset) / Scale
Some variants exist, depending on the protocol. For example, some slave protocol instances allow
the use of the raw RTDX value, instead of the engineering value.
Refer to the corresponding protocol reference manual to learn how a specific slave protocol
processes analog data before reporting it.

5.4.4 Single-Bit Binary Inputs Reported as Double-Bit Binary

Inputs
It is possible to subscribe a slave protocol instance to a master single-bit binary input, but with the
intent to report it as a double-bit binary input.
In such scenario, the result depends on the selected slave protocol, as there is no single approach
to the implementation of this feature. Some protocols only use the least significant bit of the
double-bit binary input; some other s convert the 0 state to a 01 double-state (0 in the most
significant bit, 1 in the least), and the 1 state to a 10 double-state (1 in the most significant bit, and
0 in the least).
Refer to the corresponding protocol reference manual to learn how a specific slave protocol
processes double-bit binary inputs.

SMP Gateway Protocol Common Concepts Reference Manual • 31

6 Control Operations

This chapter discusses how master and slave protocol instances handle control operations that
must be performed on output points.

6.1 Control Operation Types

Control operation types define how control operation requests must be handled by the protocol
components.
The SMP Gateway supports the following control operation types:

Control Operation Type Description

Select Reserve and prepare an output point for an upcoming Execute
operation.

Execute/Operate Perform a control operation on an output point that was previously

selected for control operation.

Direct Execute Perform a control operation on an output point that does not require to
(or Direct Operate) be selected.

Recall Cancel the selection of an output point.

Table 6-1 Control operation types

The effect of the control operation is determined by its execution type.

6.1.1 Analog Control Operation Execution Types

Control operation execution types define the effect a control operation has on an output point.
The SMP Gateway currently only supports one execution type for analog output points: setpoint
operations.
Setpoint control operations are used to change the value of an analog output. The setpoint value
can be specified as a raw or floating-point value in the control request. Depending on master
protocol specifications, the setpoint value can be converted to another format, using the Scale and
Offset settings of the configured analog output point.

6.1.2 Binary Control Operation Execution Types

Control operation execution types define the effect a control operation has on an output point.

SMP Gateway Protocol Common Concepts Reference Manual • 33

 The SMP Gateway currently supports the following execution types for binary outputs:

Control Execution Type Description

Trip/Open Change the state of a binary output from 1 (ON, CLOSED, TRUE) to
0 (OFF, OPEN, FALSE).
If this output is connected to a contact relay, it will open it.

Close Change the state of a binary output from 0 (OFF, OPEN, FALSE) to 1
(ON, CLOSED, TRUE).
If this output is connected to a contact relay, it will close it.

Pulse Transmit a pulse command to the IED that owns the binary output,
with the value and activation period settings, if applicable.
The SMP Gateway does not change the value of the binary output
point; it waits for the IED to perform the control operation and to
provide the point value resulting from the control operation.

Table 6-2 Binary control operation execution types

6.2 Control Operation Processing

The control operation process is shared between the component instances involved, which
communicate with each other using RTDX messages.
Slave protocol instances receives control operation requests from the master station, performs
basic validation and forwards them to the corresponding master protocol instances that are
responsible for the essential part of the process: the final validation effort and the transmission of
the corresponding control operation request to the end device.
Master protocol instances must also ensure that Select-Before-Operate control operation sequences
are respected; for that matter, it preserve the current control state of the corresponding output
point, and make sure that a Select operation is received before an Execute operation, and that the
latter is received within the pre-configured selection period.
Additional control operation processing duties performed by the master protocol include control
operation confirmation (real or simulated) and control operation conversion.
Control operations initiated by system components work in a similar manner. When a system
component needs to change the value of a physical output, it communicates with the output point’s
owner (i.e. the master protocol instance) through RTDX, and the point’s owner transmits the
corresponding control operation request to the point owner.
In the case of system data output, the process is the same but simpler, as there is no end device to
contact: the corresponding output point value is changed and applicable actions are undertaken by
the component instance, if required (through system output points, users can suspend polling
activity, suspend control operations, or freeze counters).

6.2.1 Control Operation Confirmation and Validation

Master protocol instances are responsible for confirming each control request received from a
slave protocol instance, regardless of the result of the operation. This confirmation informs the
slave component whether the operation was completed, successfully or not, or simply refused.
Note that this confirmation message is sent for each control operation type (Select, Execute, Direct
Execute, and Recall).

34 ● Chapter 6: Control Operations

 When a control operation is performed on a physical data point, the confirmation process can be
performed in two different ways:
 Real confirmation.
The master protocol instance only sends its confirmation message to the slave when it
receives its own confirmation (response) from the device.
 Simulated confirmation.
The master protocol instance sends its confirmation message to the slave as soon as it
processes the control operation request, without waiting for a response from the device.
Real confirmation provides the true operation completion status to the control initiator. Since this
confirmation is sent once the control operation has been completed at the end device, the response
time is typically longer than that of a simulated confirmation.
The drawback of simulated confirmation is that control operation requests may succeed at the
basic validation level, but fail at the end-device level. In that case, the confirmation sent to the
initiator indicates that the operation was completed successfully when, in fact, it may have failed.
In both scenarios, standard validation is performed before any attempt is made to interact with the
end device. This validation prevents control operations requests from being forwarded to the end
device if:
 Output control operations are inhibited for this master protocol instance (through
configuration or via a system control operation).
 Output control operations are inhibited for this output point (through configuration or via a
system control operation).
 The control operation request is erroneous or contains unexpected parameters.
 The control operation applies to an unknown or non-configured (de-activated) output point.
 The corresponding output point is currently being operated by another slave protocol instance.
 The corresponding output point is not in a valid operational state; this is the case if the
communication link between the master protocol instance and the end device is currently
failing.

Note: Some master protocols provide the Ignore Quality for Control general setting,
which allows control operations to be performed on output points regardless of
the current quality of the points.

6.2.2 Control Operation Queuing

A single master protocol instance cannot perform control operations on multiple output points.
However, a queuing feature is provided, allowing the reception of multiple control operation
requests targeted at the same master protocol instance; queued control operations can then be
performed in sequence.
The maximum number of control operations that can be queued is specific to each master protocol
component.
On the slave protocol side, control operation timeouts may need to be adjusted to allow more time
for the confirmation of the concurrent control operations.

6.2.3 Control Operation Conversion

In some situations, the control operation process on the master station side is different than the one
on the device side. For example, the master station may only support Select-Before-Operate

SMP Gateway Protocol Common Concepts Reference Manual • 35

 (SBO) control operation sequences, while one of the devices to control only supports Direct
Execute operations.
RTDX allows most control operation conversion scenarios, as long as the required operation types
are supported by the corresponding slave and master protocols.
The following control operation conversion scenarios are possible:
 Select-Before-Operate to Direct-Operate.
In this scenario, a slave output point is configured to be operated using Select-Before-Operate
control operations, while the corresponding master output point can only be operated using
Direct Operate control operations.
 Direct-Operate to Select-Before-Operate.
In this scenario, a slave output point is configured to be operated using Direct Operate control
operations, while the corresponding master output point can only be operated using Select-
Before-Operate operations.
In the first scenario, the Select control operation is not performed for real: it is simulated by the
SMP Gateway and a confirmation is transmitted to the master station; the master station can then
proceed with the transmission of the Execute control operation, which is transmitted to the device.

Note: The simulation of the Select control operation must not be confused with
simulated confirmation, although from the master station standpoint, they both
result in the same effect: the slave protocol quickly informs the master station
that it can proceed with the transmission of the Execute control operation, even if
it did not validate with the device that the latter will accept the operation.

The second scenario requires additional work. When a master output point configured for SBO
receives a Direct Operate control operation, it must first transmit a Select operation to the device.
If the result is positive, the master can then transmit an Operate operation to the device. Failures
are communicated to the master station as soon as they occur; but if the entire process succeed, the
master station will only be notified at the completion of the Operate control operation (or when the
master protocol instance transmit the control operation request to the device, if simulated
confirmation is configured for this point).
Control operation conversion applies to both analog and binary output control operations.

6.2.4 Control Operation Conversion using Paired Binary Output

Points
Binary output points may be paired to perform complex control operations altogether; most of the
times, pairing is required when the protocol required by the master station and the one used by the
device are different, or when they do not support the same control operation execution types.
For example, a SCADA that only supports Pulse control operations over the VALMET TEJAS
Series V protocol would require binary output pairing to control an IED that supports only
Open/Close control operations.
Two scenarios are supported using paired binary outputs:
 Pulse to Open/Close conversion.
A pair of binary outputs in a slave protocol instance is mapped to a single binary output in a
master protocol instance.
 Open/Close to Pulse conversion.
A single binary output in a slave protocol instance is mapped to a pair of binary outputs in a
master protocol instance.

36 ● Chapter 6: Control Operations

 In the first scenario, the two slave protocol binary outputs can be operated by Pulse control
operations, each point being mapped to either an Open control operation or a Close control
operation on the master binary output.
In the second scenario, an Open control operation on the slave binary output is translated to a
Pulse operation on the first master binary output, while a Close operation is translated to a Pulse
operation on the second master binary output.
Binary output pairing implementation is a protocol-specific feature and is not supported by all
protocols. Refer to the corresponding protocol reference manual for additional information on how
to set up binary output pairs.

6.3 Local and Remote Control Operation Modes

By default, the SMP Gateway is in Remote Control Operation Mode, which means that control
operations to be performed remotely on physical output points through slave protocol instances.
The SMP Gateway can also be put into Local Control Operation Mode; in this mode, control
operations are refused at the slave protocol instance level: the only way to perform control
operation in this mode is via the SMP Gateway Local HMI or using Yukon Visual T&D.
The _smp___localControl system binary input indicates the current control operation mode. Use
the _smp___setLocalControl system binary output to switch from one mode to the other.

6.3.1 Preventing Control Centers from Performing Remote

Control Operations
It is possible to prevent control centers from performing remote control operations on physical
output points, via slave protocol instances, by putting the SMP Gateway into Local Control
Operation mode.

To prevent control centers from performing remote control operations:

 Make sure the current state of the _smp___localControl system binary input point is set to 0;
if it is set to 1, the SMP Gateway is already in Local Control Operation mode.
 If _smp___localControl is set to 0, perform a Direct-Execute Close control operation on the
_smp___setLocalControl system binary output point.
 Wait until the _smp___localControl point turns to 1, indicating that the SMP Gateway is now
in Local Control Operation mode.
 To revert to Remote Control Operation mode, perform a Direct-Execute Close control
operation again on the _smp___setLocalControl point, and wait until the
_smp___localControl point turns to 1.

6.4 Control Operations over Multidrop

Connections
On a multidrop link, control operation requests have precedence over any other type of requests.
During normal operation, all master protocol instances that share the same multidrop link have the
same priority level. In other words, each instance gets its turn on the link once every ‘X’ turns,
where ‘X’ is the number of instances.
When an instance is ready to send an output control request to its corresponding device, its priority
level is increased and it becomes the next in line to send a request, so it can send its control

SMP Gateway Protocol Common Concepts Reference Manual • 37

 operation request as fast as possible. If the operation is of the Select-Before-Operate type, both the
Select and the Execute control operation requests will be transmitted, one at a time.
When the instance has completed its control operation process, its communications link priority
level returns to normal and other instances can proceed with normal scanning operations.

6.5 Control Operations Deactivation through

System Data Points
It is possible to deactivate control operations of all physical analog or binary output points for a
given master protocol instance, by performing a control operation on either the ___AOCtrlDisable
or ___BOCtrlDisable system data point.
The ___AOCtrlEnable and ___BOCtrlEnable system data points are available to reactivate control
operations on these points.
The ___AOCtrlEnabled and ___AOCtrlEnabled system data points indicate whether control
operations are currently active, or not, for these data points. However, these data points only
reflect their activation state per the aforementioned system data points, as control operations can
also be suspended or deactivated through other means.

6.6 Binary Output Point Interlocking

The SMP Gateway supports binary output point interlocking, to prevent control operation
execution on a given binary output point under specific conditions.
For additional information about this feature and to learn how to configure it using SMP Config,
refer to the Interlocking Binary Output Points technical note (S1120-16-2).

Note: Binary output point interlocking uses SMP Gateway Automation Functions; to
successfully implement this feature on your SMP Gateway, its license must
include the SMP Gateway Automation Functions option.

6.7 The SMP Gateway Control Log

The Control log records all messages that are exchanged between the slave and master protocol
instances during a control operation process, including confirmation messages.
Its content can be viewed using the SMP Log application, via the eSMP browser-based
application, or the SMP Gateway HMI feature.
Refer to the Control log when control operations do not work as expected on the SMP Gateway,
to have a better understanding of the cause of the problem.

38 ● Chapter 6: Control Operations

7 IED File Retrieval

This chapter explains how the SMP Gateway retrieves event and configuration files from IEDs.

7.1 IED File Types

Although some master protocol components allow direct file retrieval from devices, most of the
files they retrieve do not exist in the same form and format on the device; such files regroup data
that can be mapped to data points, or not (such as text information), but which reveals to be more
significant when grouped altogether.
To keep things simple, no distinction is made between files that are retrieved “as-is” from IEDs,
and files that are assembled by the master protocol instances by regrouping IED data, traces and
data point values.
Master protocol essentially supports the following types of IED files:
 IED Event Files.
This type of files includes standard event files, disturbance data files, COMTRADE files,
oscillography files, and sequence-of-events (SOE) files.
 IED Configuration Files.
This type of files regroups hardware and firmware information, and configuration settings.

7.1.1 Other IED Files

Some master and slave protocol components support file transfer per design, which means that
they can retrieve an existing file from a device, and store it temporarily on the SMP Gateway
before retransmitting it to a master station.
These files are non-categorized in the SMP Gateway configuration, as their content is not analyzed
by the master protocol instance that retrieves them from the device.

7.2 System Folders

System folders are virtual folders, defined for a given SMP Gateway, which are used to store IED
files. Two types of system folders can be configured:
 Local System Folders.
This type of folder is located on the SMP Gateway itself. Be aware that disk space is limited
on an SMP Gateway, if you compare it to nowadays computer hard drives.
 Remote System Folders.
A remote system folder is a shared folder on a remote computer, which is identified using the
Unified Naming Convention (UNC). To use remote folders, the SMP Gateway must have

SMP Gateway Protocol Common Concepts Reference Manual • 39

 access to a WINS server in order to resolve computer names. See the corresponding
installation guide of your SMP Gateway for more information.
A system folder must be assigned to each IED file type configured for a specific master protocol
instance.

7.2.1 Defining Local System Folders

Define a local system folder if IED files must be retrieved and stored temporarily on the
SMP Gateway.

To define local system folders in a SMP Gateway configuration:

 In the left pane of the SMP Config window, click System Folders.
 In the Local System Folders pane, enter the following information for each new local system
folder:
 The numerical Folder ID, which is a number ranging from 1 to 99. On an SMP Gateway,
each system folder, remote or local, must have a unique ID.
 The folder Name. This name references the folder in master protocol instances’ file-
retrieval settings. It is also used in traces, logs and stats.
 The number of bytes that will trigger a transition on a specific system data point, thereby
advising you that space is running low. The maximum value you can type is
2,147,483,647, and the default is 0 (no notification at all).
 Select Compress to compress and archive event files to a ZIP file.
 Optionally, you can provide a description of the folder.

7.2.2 Defining Remote System Folders

Define a remote system folder if IED files must be retrieved and stored on a shared folder located
on a remote computer.

To define remote system folders in a SMP Gateway configuration:

 In the left pane of the SMP Config window, click System Folders.
 In the Remote System Folders pane, enter the following information for each new remote
system folder:
 The numerical Folder ID, which is a number ranging from 1 to 99. On an SMP Gateway,
each system folder, remote or local, must have a unique ID.
 The folder Name. This name references the folder in master protocol instances’ file-
retrieval settings. It is also used in traces, logs and stats.
 The Location of the shared folder, using the following syntax:

\\<Computer Name>\<Shared Folder Name>.

For example, the location \\cpu104\Events refers to a shared folder called Events
on a computer named cpu104.
 A Username and a Password, if access to the shared folder is secured. You must use the
computername\username or domainname\username format.

40 ● Chapter 7: IED File Retrieval

  The number of bytes that will trigger a transition on a specific system data point, thereby
advising you that space is running low. The maximum value you can type is
2,147,483,647, and the default is 0 (no notification at all).
 Clear the Compress check box.
 Optionally, you can provide a description of the folder.

7.3 Event File Retrieval Process

The event file retrieval process revolves around two concepts: the polling of the IED to detect
event files or a given type, and information about the last event file of this type that was retrieved.
First, the master protocol instance polls the IED at a pre-configured frequency, to detect the
presence of event files on the IED. Depending on the protocol, this frequency is either specified in
the settings of the event file type, or in the lists of requests that must be transmitted to the IED.
If event files are detected, the master protocol instance must determine which files it will retrieve,
according to the file retrieval rules defined for this type of event.
The master protocol instance then proceeds with the retrieval operation, and stores the files in the
system folder assigned to this type of event.

7.3.1 Event File Retrieval Rules

Event file retrieval rules define which files will be retrieved by the master protocol instance and in
which order; these rules are specific to each event file type.
These rules only apply when a master protocol does not have any information about the last event
file retrieved for the corresponding event type.
The following table describes the behavior of a master protocol instance according to each rule.

File Rule Behavior

New files only The newest event detected is marked as the last event retrieved, for
subsequent reference. Newer events will be downloaded, when
available.

Files from last X days All events that occurred during the last X day(s) will be downloaded,
starting with the oldest one.
Note: X is defined by the Max File Age setting.

All files All events will be downloaded, beginning with the oldest one.

Table 7-1 Event File Retrieval Rules

7.3.2 Setting up Event File Retrieval

The following procedure describes how to set up event file retrieval for most master protocol
components. If it does not seem applicable, refer to the reference manual of the corresponding
protocol to learn how to set up event file retrieval for this specific protocol.

Note: The system folder where the retrieved files will be stored by the master protocol
instance must be defined before setting up event file retrieval

SMP Gateway Protocol Common Concepts Reference Manual • 41

 To set up event file retrieval:
 In the left pane of the SMP Config, expand the master protocol instance branch.
 Select the Event Files branch.

The types of event files that can be retrieved using this protocol instance are listed in the right
pane.

A Name setting is automatically assigned to each event file type (ex. “Standard Event Report”),
based on the protocol. A Short Name setting (ex. “EVE”) is also automatically assigned to each
event file type, also based on the protocol. These settings are read-only.
 For each type of event file to retrieve:
 Clear the Disabled check box to activate the event file retrieval function for this specific
event type.
 In the Folder cell, select the previously-defined system folder where the master protocol
instance will store retrieved event files.
 In the File Rule cell, choose the event file retrieval rule that the master protocol instance
will follow to determine which files it will retrieve or not.
 In the Minimum Free Disk Space box, specify the amount of disk space that has to be
available in the system folder in order to store an event file.
 Optionally, you can type some meaningful information in the Extra Info cell. This
information will be appended to each event file name.
 Optionally, you can provide a description of the event file(s).
 Specify at which frequency the master protocol instance will poll the IED for event files of
these types; refer to the reference manual of the corresponding master protocol instance to
determine the settings to specify for that matter.

7.4 Configuration File Retrieval Process

The configuration file retrieval process is simple. The IED is polled by the corresponding master
protocol instance at a pre-configured frequency, to determine if a configuration file has changed.
Depending on the protocol, this polling frequency may be specified either in settings of the
configuration file type, or in the list of requests that must be transmitted to the IED.
If changes are detected, the master protocol instance retrieves the latest version of the
configuration file and stores it in the system folder specified for this configuration file type.

7.4.1 Setting up Configuration File Retrieval

The following procedure describes how to set up configuration file retrieval for most master
protocol components. If it does not seem applicable, refer to the reference manual of the
corresponding protocol to learn how to set up configuration file retrieval for this specific protocol.

42 ● Chapter 7: IED File Retrieval

 Note: The system folder where the retrieved files will be stored by the master protocol
instance must be defined before setting up configuration file retrieval

To set up configuration file retrieval:

 In the left pane of the SMP Config, expand the master protocol instance branch.
 Select the Configuration Files branch.

 Clear the Disabled check box to activate the configuration file retrieval function.
 In the Folder cell, select the previously-defined system folder where the master protocol
instance will store retrieved configuration files.
 In the Minimum Free Disk Space box, specify the amount of disk space that has to be
available in the system folder in order to store a configuration file.
 Optionally, you can type some meaningful information in the Extra Info cell. This
information will be appended to each configuration file name.
 Optionally, you can provide a description of the configuration file(s).
 Specify at which frequency the master protocol instance will poll the IED for configuration
files; refer to the reference manual of the corresponding master protocol instance to determine
the settings to specify for that matter.

Note: Most master protocol instances that support configuration file retrieval also
require the specification of additional protocol-specific settings, such as the type
of configuration information to retrieve, the memory address at which the
configuration information can be find, etc. The reference manual of the
corresponding protocol provides an exhaustive description of these settings.

7.5 IED File Headers

IED files are stored in various formats, which depend on the master protocol instance that retrieves
them. Moreover, some IED file types are comprised of multiple files. For example, an IED event
file can be stored in the COMTRADE format, which split the settings and the data into different
files.
Every time a master protocol retrieves an IED file (or set of files), it creates a header file that
contains processing information for other Cooper Power Systems applications that manage or
analyze the content of this file.
This header file has the same name as the IED files, but with a TXT extension.

7.6 IED File Naming Convention

The naming convention used by the SMP Gateway for IED files is based on the C37.232-2011 –
IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME), with
slight differences.
What follows is an example of an event file name, followed by a summary of the convention,
including some particularities that apply to the SMP Gateway.

SMP Gateway Protocol Common Concepts Reference Manual • 43

 20040129,044323484,UT,_smp,DEV_PREFIX_,CooperInc.,BOR,00002,Extra
Information.itd
 The filename contains several information fields, separated by commas.
 The Date and Time fields are provided by the master protocol instance. This time information
is usually retrieved by the device; if it is not available from the device, it is replaced by the
SMP Gateway current date and time.
 The Time Code field is fixed to “UT”, since the date and time specified by master protocol
instances must be provided as universal time (UT) or GMT (Greenwich Mean Time). Some
master protocols support a time zone setting, which is applied to the device-provided time.
This feature is required when the end-device clock is set in local time, to convert it to UT.
 The Station ID field is set to “_smp”, which is the prefix of general SMP Gateway system
data points.
 The Device ID field corresponds to the configured Device Prefix general setting of the master
protocol instance.
 The Company Name field corresponds to the same field provided in the SMP Gateway
configuration file.
 The Event Type field corresponds to the Short Name of the IED file type, as shown in the
corresponding master protocol file settings.
 The Option #1 field is provided by the master protocol, and is typically used as a sequential
number to differentiate events that occurred at the same moment; it is not used for
configuration files.
 The Option #2 field corresponds to the Extra Info field of the IED file type, as specified in
the master protocol instance settings.
 The file extension is provided by the master protocol instance, and is specific to each IED file
type and protocol.
 When more than one file is retrieved at once, they share the same file name, but with a
different file extension.

7.7 IED File Time-Tagging

IED files, along with their accompanying header files, are time-stamped using the time
information provided by IED, or the SMP Gateway current time if the IED does not provide it.
The timestamp is applied to both the file creation time and the file modification time.

44 ● Chapter 7: IED File Retrieval

8 Advanced Features

This chapter discusses additional protocol-related SMP Gateway features.

8.1 Redundancy
SMP Gateway redundancy implies the use of two SMP Gateways, called respectively the active
SMP Gateway and the standby SMP Gateway. Both SMP Gateways are connected to the same
control center and IEDs, and they share the same configuration.
The active gateway polls the devices and communicates with the control center as if it was a
standalone system. Meanwhile, the standby gateway is waiting, ready to take over the active role
when a specific failover condition is met, such as a critical malfunction of the active gateway.
For additional information about SMP Gateway redundancy and to how to set it up, refer to the
SMP Gateway User Manual.

Note: The redundancy function is not available on the SMP 4 and the SMP 4/DP.

8.1.1 Hot-Standby Redundancy

The SMP Gateway software has the possibility to maintain a complete up-to-date image of the
active SMP Gateway data on the standby SMP Gateway. This master protocol feature is called
hot-standby redundancy. It is available for the most common master protocols, and is activated by
the Hot-Standby Support general setting.
Whenever a transition occurs on a hot-standby data point, data point information is first updated in
the RTDX database of the active SMP Gateway; it is then transmitted to the standby
SMP Gateway, which updates its own RTDX database.
Using hot-standby redundancy, integrity scans are not always required during a failover, since the
hot-standby data points are already synchronized, reducing the failover time significantly.
Moreover, connected control centers do not see any bad transitory data.
The drawback is that all synchronized data must be transmitted to the standby SMP Gateway
before it can be made available to the control center. This can add a few dozen milliseconds to the
overall transmission time of a transition from the device to the control center.
To take full advantage of hot-standby redundancy, slave protocol instances should be configured
to accept incoming connections even while the SMP Gateway is on standby.

SMP Gateway Protocol Common Concepts Reference Manual • 45

8.1.2 Allowing Hot-Standby Redundancy Support for a Slave
Protocol
Although hot-standby redundancy is a master-protocol-specific feature, slave protocol instances
on redundant SMP Gateways must be configured to accept incoming connections even while the
SMP Gateway is on standby.

To allow hot-standby redundancy support for a slave protocol instance:

 In SMP Config, select the General settings branch of the slave protocol instance.
 In the Hot-Standby Support cell, select the behavior that is expected from the slave
component, between the following:
 Acquisition.
The slave protocol will receive data from the master protocol instances it is subscribed to,
without accepting control operation requests from the control center.
 Acquisition and control.
The slave protocol will receive data from the master protocol instances it is subscribed to,
and it will accept control operation requests from the control center. These control
operations will be forwarded to the active SMP Gateway, which will transmit the
corresponding control operation requests to the IEDs.

8.2 Listen Mode

A master protocol instance is said to be in Listen Mode when it cannot transmit over the serial link
it is using.
This mode is useful to verify that the SMP Gateway implementation of a particular protocol
reports the appropriate information about the device to which it is connected. This is done without
interrupting the communication that is taking place between the device and the master station.
Two different setups can be used for listen mode, depending on protocol specifications. If it is
possible to determine the request used to get a particular response, then a single serial port is
enough to go into listen mode. On the other hand, if it is impossible to establish which request
initiates a particular response, then a second serial port has to be used to spy on requests, in order
to parse the information within the response. A custom serial cable is also required in this case.
Listen mode is available only for some protocols.

8.3 Data Point Inhibition

Data point inhibition consists in putting a data point in a state where it temporarily appears
inactive from a control center standpoint.
Data changes occurring on an inhibited input point are no longer reported, as long as it remains in
this state, and its current value is the last one that was reported prior to the inhibition.
An inhibited output point cannot be operated as long as it remains inhibited.
Currently, there are only two ways to inhibit a data point: using the Inhibition automation
function, or through Visual T&D.

46 ● Chapter 8: Advanced Features

8.3.1 Preventing an Output Point from Being Operated using the
Inhibition Automation Function
The Inhibition automation function, when executed on a binary output, makes it non-operable as
long as it is inhibited.

Note: This procedure outlines the broad steps to perform to inhibit an output point. For
more specific details about the Automation Functions component and the
Inhibition function, refer to the SMP Gateway Automation Functions Reference
Manual.

To prevent an output point from being operated using the Automation Function:
 In the left pane of SMP Config, expand the System branch, and select the Automation
Functions branch.
 Define a new Automation Functions instance, and specify its general settings.
 Create a logic binary output point for the inhibition control point (i.e. the point to operate to
change the inhibition status of the point).
 Create a logic binary input point for the inhibition status point.
 Define an Inhibition automation function:
 In the Control Point cell, type the name of the logic binary output point created above.
 In the Status Point cell, type the name of the logic binary input point created above.
 In the Point 1 cell, type the name of the output point to inhibit.

Note: If you want to update more than one output point simultaneously, use the
additional provided settings (ex. Point 2, Point 3, etc.)

 Save the configuration file and upload it to the SMP Gateway.

 To inhibit the selected output point, perform a Direct-Execute Close operation on the
specified control point; the point will be inhibited when the state of the specified status point
will turn to 1.
 To remove the inhibition status, perform a Direct-Execute Open operation on the specified
control point, and wait for the specified status point to turn to 0.

8.4 Data Point Value Forcing

There are essentially two ways of overriding the value of a physical data point:
 Using the Force automation function;
 Using the commissioning tool of the eSMP browser-based application.
The Force automation function allows forcing an input data point (analog input or binary input) to
a given value, by performing a control operation on an output data point (analog output or binary
output). The input point is called the forced point; the output point, the force point. An additional
optional point - called the unforce point - can be used to revert the forced point to its former value
and quality. The forced point can be configured to be persisted, which means that it can retain its
forced value when the SMP Gateway restarts.

SMP Gateway Protocol Common Concepts Reference Manual • 47

 The Force feature of the eSMP browser-based application is used to force values for simulation
and commissioning purposes. In this case, the forced value is not persisted, and the RTDX status
of the forced value is set to Simulated, not Forced.

8.5 The SMP Gateway Integrated Firewall

The SMP Gateway is protected by an integrated firewall, which only allows communications with
specific users, computers and programs, including those with the SMP Tools, which goes through
a TLS-encrypted access port. This feature limits access to the SMP Gateway internal components
and services.

8.5.1 SMP Gateway Firewall Access Rules

Firewall access rules define which services or applications are allowed through the firewall; for a
given service or application, they can also allow access from specific computers or subnets.
Firewall access rules are specified using SMP Config, which provides a list of common services
that can be allowed through the firewall. Additional access rules can also be defined for custom
services and applications.

Note: Some access rules are also defined while configuring specific components, such
as slave connections, the SNTP server, or the Passthrough Direct Access Port.

8.5.2 Allowing Access to a Slave Protocol Only from Specific

Master Stations
The following procedure explains how to configure the SMP Gateway integrated firewall, using
SMP Config, so the connection to a slave protocol can be allowed only from specific master
stations, based on IP address and subnet information.

Note: The SMP Gateway integrated firewall is active by default, but can be deactivated;
make sure it is active before proceeding with this task.

To allow access to a slave protocol only from specific master stations:

 In the left pane of SMP Config, expand the Connections branch, and select either the TCP/IP
Slaves or UDP/IP Slaves branch, depending on the type of the connection used by the slave
protocol instance.
 In the row of the connection of the slave protocol instance:
 In the Accessible From cell, select Specific Computer or Subnet.
 In the Specific Computer or Subnet cell, type the IP address or subnet of the master
station to allow through the firewall; to allow access from multiple master stations, you
can also type multiple addresses and subnet, separated by commas.

8.6 Device Clock Synchronization

If it is supported by the device and the protocol it uses, the corresponding master protocol instance
can be configured to synchronize the device clock with the SMP Gateway clock.

48 ● Chapter 8: Advanced Features

 If the device clock is set to use local time, instead of UTC time, the master protocol instance must
be configured to adjust the SMP Gateway time according to the same time zone and daylight
savings setting, before it transmits the time information to the device.

8.7 SMP Gateway Clock Synchronization through

Slave Protocols
When no external time source is available to the SMP Gateway, a master station or control center
can itself serves as a time source, if the protocol it uses to communicate with the gateway supports
time adjustment (synchronization).
If the master station is set to use local time, instead of UTC time, the slave protocol instance must
be configured to adjust the master station time to UTC time, based on the time zone and daylight
savings settings of the master station, when the master station attempts to synchronize the
SMP Gateway clock with its own.

SMP Gateway Protocol Common Concepts Reference Manual • 49

9 Troubleshooting

This chapter describes the most frequent problems encountered with the configuration or use of
SMP Gateway master and slave protocol components, and provides solutions or advices to help
users solving these issues.

9.1 Protocols Failed at Startup

When you power on or restart the SMP Gateway, the Status of the SMP Gateway displayed in
SMP Manager is set to Protocols Failed,

Possible Causes:
 Some of the protocol components, for whose you provided configuration settings in the
SMP Gateway configuration (PAR) file, are missing.
 The SMP Gateway configuration (PAR) file contains errors or is not up-to-date with the
current version of the SMP Gateway software installed.

SMP Gateway Behavior:

 No master or slave protocol components are started.
 The SMP Gateway application is idle, but its operating system is running.
 Non-protocol related system components are started and available; as a result, SMP Trace,
SMP Stats and SMP Log can connect to the SMP Gateway.

Solution:
 Make sure the latest SMP Gateway license that was provided by your sales representative is
installed on the SMP Gateway. If this is not the case:
 Update the SMP Gateway license, using SMP Manager.
 Update the SMP Gateway application, to ensure that the licensed components are
properly installed.
 Start SMP Log and examine the Startup log:
 Make sure that you are using the correct configuration file, which should be listed in the
first entries of the log. If this is not the correct file, use SMP Manager to upload to the
correct one to the SMP Gateway.
 If the Startup log reveals configuration errors, fix them in the SMP Gateway
configuration (PAR) file, using SMP Config, before uploading the corrected version of
the file to the SMP Gateway using SMP Manager.

SMP Gateway Protocol Common Concepts Reference Manual • 51

  If the Startup log reveals configuration version errors, the SMP Gateway configuration
(PAR) file may be obsolete. Try opening it with the version of SMP Config that matches
the SMP Gateway software version; if the file is obsolete, SMP Config will offer to
update it: accept and save the file to the correct version, before uploading the up-to-date
version of the file to the SMP Gateway using SMP Manager.
 Configuration version errors can also be due to obsolete software. Make sure that the
correct version of the SMP Gateway application is installed on the SMP Gateway, and if
this is not the case, update it using SMP Manager.
 Make sure the Hardware settings specified in the SMP Gateway configuration (PAR)
file are valid and correspond to the actual SMP Gateway hardware configuration. A
mismatch at this level, which occurs mostly when a configuration file is reused for a
different SMP Gateway model, may also result in the Protocols Failed SMP Gateway
status. If there is a mismatch, fix the configuration file in SMP Config before uploading
the corrected version of the file to the SMP Gateway using SMP Manager.
 If the problem persists, try using a simpler version of the configuration file, in an attempt to
isolate the problem. For example, use an SMP Gateway configuration file that only contains
one master protocol instance; if it works, try adding back each instance until you stumble unto
the problem and get a better comprehension of it.

9.2 Acquired Values are Incoherent or Erroneous

All data exchanges are taking place correctly over the communication link and no protocol error is
reported; however, some of the acquired values are incoherent or erroneous.

Possible Causes:
 The settings provided for the data points are incorrect, either in the master or slave protocol
instance, or in both instances.
 The protocol implementation on the SMP Gateway may differ slightly from the device’s or
control center’s own implementation, which causes the protocol instance to process the
acquired or reported data in an unexpected manner.

Solution:
 If you are unsure whether the problem occurs at the slave or master protocol level, you can
use the eSMP browser-based application to view the current values as stored in RTDX:
 In SMP Manager, from the Tools menu, choose Internet Explorer to start the eSMP
application.
 If the values displayed in eSMP are valid a coherent, as opposed to those reported to the
control center, the problem lies in the slave protocol configuration.
 If the values displayed in eSMP are as erroneous and incoherent as those reported to the
control center, the problem probably lies in the master protocol configuration.
 Start SMP Trace and examine the RTDX and protocol traces. If a problem appears in the
protocol traces, this may be due to a protocol incompatibility; otherwise, this may be due to a
configuration problem.
 Start SMP Config and examine the protocol instance configuration. Pay attention to the
following:
 Data addressing.
Is the address of the corresponding physical data point correct? Some devices have

52 ● Chapter 9: Troubleshooting
 flexible configuration options, so you have to compare the SMP Config values with the
values set by the device manufacturer’s software.
 Conversion factors.
For physical analog data points, are the Scale and Offset settings set properly?
 Polarity.
For binary input points, is the Inverted Pol setting set properly?
 Warning messages.
Are there any pending warning messages in SMP Config, regarding the data points that
have erroneous values?

9.3 Control Operation Fails

Control operations performed on a physical output point fail systematically.

Possible Causes:
 Control operations are deactivated for the entire SMP Gateway, for either analog or binary
output points, for a specific slave or master protocol instance, or for a specific output point.
 The output point is not in a controllable state.
 In the case of Select-Before-Operate control operations, the sequence of operation may not be
respected.

SMP Gateway Behavior:

 The SMP Gateway refuses the control operations, but the corresponding output point is not
impacted.
 If the control operation is initiated by a control center, via a slave protocol instance, the
SMP Gateway responds negatively to its control operation requests.

Solution:
 Open the SMP Gateway configuration (PAR) file in SMP Config and verify the following
settings:
 Make sure that control operations are allowed for both the slave and the master protocol
components involved in the control operation, using the Control Enabled general
setting.
 Make sure the controlled output point is not deactivated, using the Disabled point setting,
in the corresponding master protocol instance configuration.
 Verify the state of the _smp___LocalControl system binary input point: if it is set to 1, the
SMP Gateway is in Local Control Operation mode, which means that control operations
cannot be performed through slave protocols.
 Verify the state of the ___AOCtrlEnabled or ___BOCtrlEnabled system binary input point
specific to the corresponding master protocol instance: if it is set to 0, control operations are
currently deactivated for this type of output point. Perform a Direct-Execute Close control
operation on the ___AOCtrlEnable or ___BOCtrlEnable system output point to reactivate
them.
 Verify the RTDX status of the controlled output point:
 If it is set to Communication Failure, this means that there is currently a communication
problem between the master protocol instance and the device that provides this physical

SMP Gateway Protocol Common Concepts Reference Manual • 53

 output point. Solve the communication problem and the point will become operable again
(i.e. its RTDX status will be set to OK).
 If it is set to Inhibited, the point was inhibited by Visual T&D or the Inhibition
automation function; TODO
 Start SMP Log and examine the Control log:
 Make sure the proper sequence of operations was transmitted by the control center. For
example, some protocols or points are configured for Select-Before-Operate control
operations. In such scenario, if an Execute control operation is sent to a non-selected
output point, it may be refused by the SMP Gateway.
 Similarly, some protocols or points are configured for a specific control operation
execution type (ex. Open/Close, Pulse, etc.). Make sure that the control center is not
trying to perform a Pulse control operation on an Open/Close point, for example.
 Pay attention to any other error or warning message found in the log, for any other
protocol-specific issue.
 Additional troubleshooting details can also be provided through the SMP Trace tool; however,
you must establish an SMP Trace session with the SMP Gateway and select the proper
protocol traces to display before you perform the control operation, as SMP Gateway traces
are not stored in non-volatile memory (as opposed to log entries).

9.4 Protocol Communication Problems through a

RS-232 Link
A master or slave protocol instance cannot communicate with an IED or a control center through
an RS-232 link.

Possible Causes:
 The cables used are faulty.
 The SMP Gateway serial port was not set for RS-232 communications in the SMP Gateway
configuration, or other related settings were not specified properly.

Solution:
 Make sure the cables used are appropriate and work properly. Also remember that
SMP Gateway ports are configured in DTE mode, which means that in most scenarios, a
straight cable will work to connect to a modem or to most IED maintenance ports. If the
SMP Gateway must connect to a PC, use a null modem cable.
 Start SMP Config, and examine the settings of the corresponding serial port and connection:
 The Interface setting of the serial port must be set to Asynchronous.
 The Link Type setting of the serial port connection must be set to RS-232.
 Verify the values of the Baud Rate, Parity, Byte Size and Stop Bits settings, and make
sure they match to the corresponding setting values in the IED or control center
configuration.
 Finally, if the IED or control center supports software flow control (XON/XOFF), adjust
the corresponding settings accordingly. Proceed in a similar manner for the device
hardware handshaking mode (RTS, DTR-DSR, DCD-RI, and CTS).

54 ● Chapter 9: Troubleshooting
 Note: The serial ports of the SMP 16 do not use the DSR and DTR signals by default.
You must change the position of certain jumpers on the SMP 16 main board to
use these signals.

For additional details, refer to the SMP 16 Installation Guide, S1120-13-1.

9.5 Protocol Communication Problems through

an RS-485 Link
A master or slave protocol instance cannot communicate with an IED or a control center over an
RS-485 multidrop link.

Possible Causes:
 The cables used are faulty.
 Termination resistors may be required.
 Other devices on the link cause interference.
 The SMP Gateway serial port was not set for RS-485 communications in the SMP Gateway
configuration, or other related settings were not specified properly.

Solution:
 Make sure the cables used are appropriate and work properly.
 Although SMP Gateway serial ports are designed to operate in RS-485 mode without the need
for termination resistors, such resistors may be required if the propagation delay is 15% above
of one bit width.

Note: Termination resistors are out of the scope of this document. For additional
details, refer to the “Using Termination Resistors for RS-485 Communications
with the SMP Gateway”, S1120-18-1.

 Start SMP Config, and examine the settings of the corresponding serial port and connection:
 The Interface setting of the serial port must be set to Asynchronous.
 The Link Type setting of the serial port connection must be set to RS-485 (4 wires) or
RS-485 (2 wires).
 Still in the serial port connection settings, pay attention to the RTS setting: it should be
set to Always On for 4-wire RS-485 or to TX request for 2-wire RS-485; other settings
can keep their default values, unless specified otherwise by the documentation of the
corresponding IED or control center.
 Finally, verify the values of the Baud Rate, Parity, Byte Size and Stop Bits settings, and
make sure they match to the corresponding setting values in the IED or control center
configuration.
 If other devices on the multidrop link seem to interfere with the protocol instance, try using a
point-to-point link to make sure that other settings were properly specified; then, proceed with
the multidrop reconfiguration.

SMP Gateway Protocol Common Concepts Reference Manual • 55

9.6 Protocol Communication Problems over an
Ethernet Network
A master or slave protocol instance cannot establish a TCP/IP or UDP/IP connection with its
corresponding IED or control center.

Possible Causes:
 The network cable used may not be working properly.
 The connections may not be configured properly.

Solution:
 Make sure you are using the right cables and that they are working properly.
 Start SMP Config and examine the settings of the corresponding connection. Make sure the
TCP/UDP port and IP address are correct.
 Start SMP Trace and examine the connection traces, which may provide connection failure
reasons and details.
 In the case of a slave protocol instance, try to perform a Ping request from the control center,
to verify if the SMP Gateway can be reached.

Note: Before proceeding with this Ping verification, make sure the ICMP PING service
is allowed through the SMP Gateway integrated firewall, in the SMP Gateway
configuration file.

 In the case of a master protocol instance, you can also perform a Ping request, but from the
SMP Gateway, to verify if the IED can be reached. To perform a Ping request from the
SMP Gateway:
 In SMP Manager, from the Tools menu, choose SMP Console.
 Type the ping request at the SMP Console command prompt.

9.7 Master Protocol Fails to Retrieve Event Files

Available on Device
A master protocol instance fails to retrieve event files from a device, although it appears that there
are some event files available on this device that have not been retrieved yet.

Possible Causes:
 The specified system folder is not available.
 There is not enough space available on the specified system folder.
 The File Rule setting specified for this type of event file in the master protocol instance
configuration lead to a behavior not as expected.

Solution:
 Verify the state of the _smp___Folder<ID><Name>_Available system binary input, where
<ID> is the value of the Folder ID system folder setting, and Name is the value of system

56 ● Chapter 9: Troubleshooting
 folder setting of the same name. If it is set to 0, the folder is not available; verify if the
computer that hosts the folder is still available to the SMP Gateway.
 Verify the state of the _smp___Folder<ID><Name>_LowDiskSpace system binary input. If it
is set to 1, this means that there is not enough space available in the system folder. Free up
space or specify another system folder in the SMP Gateway configuration for this event file
type.
 Start SMP Log and examine the content of the File log. The latest entries will provide
information about the last event of this type that was retrieved and the connection status of the
system folder.
 Start SMP Config and verify the settings of the event file type, especially the File Rule
setting, to make sure that the master protocol instance is configured to retrieve files of this
type as expected.

9.8 Communication Link to an IED or Control

Center Keeps Resetting
The communication link is established successfully with an IED or control center, but keeps
resetting.

Possible Causes:
 The communication link quality is pretty bad, which causes checksum errors and reception
timeout expirations resulting in communication link resets.
 Timeout settings configured for this protocol instances are too short and aggressive.
 A protocol incompatibility causes an unexpected error, which results in an immediate link
reset.

SMP Gateway Behavior:

 The protocol instance will keep establishing and resetting connections, unless it provides a
feature that limits the number of link resets within a given time frame.

Solution:
 Start SMP Stats, and examine the statistics page for the corresponding protocol:
 Verify if errors occur following a given pattern: do they occur for the same requests? Are
they always of the same type (timeout, checksum, etc.)?
 Start SMP Trace, activate the corresponding protocol and connection traces, and wait for the
problem to occur; then pause the trace feature, and examine the trace contents:
 Based on the SMP Stats observations, search for corresponding traces and messages:
these traces should provide more details about the errors and their cause (configuration,
protocol incompatibility, etc.).
 Search for the link reset trace message, to get additional detail about the cause of reset.
 Based on the SMP Stats and SMP Trace information, you should now have a good idea of the
cause of the problem:
 If errors do not follow a predictable pattern, the cause of the problem is probably bad link
quality. Take corrective actions as necessary.

SMP Gateway Protocol Common Concepts Reference Manual • 57

  If errors follow a predictable pattern that looks like a configuration issue, open the
SMP Gateway configuration (PAR) file and adjust the protocol settings accordingly,
especially inactivity and communication timeout settings.
 If errors follow a predictable pattern which seems to lead to a protocol incompatibility,
refer to the corresponding protocol reference manual to make sure that you properly
understand the SMP Gateway implementation and settings of this protocol. If you do not
manage to solve the problem at this point, contact Cooper Power Systems’ Technical
Assistance team.

58 ● Chapter 9: Troubleshooting
10 Appendices

SMP Gateway Protocol Common Concepts Reference Manual • 59

 Appendix A - Master Protocol Common Settings
Reference

This appendix presents the settings that are common to all master protocol components, when
applicable.

Note: Protocol-specific settings are presented and described in the reference manuals
of the corresponding protocols.

Master Protocol Common General Settings

General settings specify the general behavior of a master protocol component instance.

Setting Description
Device Prefix A prefix for the name of each I/O data point provided by this master’s
corresponding device.
This prefix must be unique in the entire SMP Gateway configuration to
ensure that every I/O point name is also unique.
The following reserved words and characters cannot be used as part of a
device prefix: the word _smp (which is the device prefix of system data
points), the comma (,), the double quotes ("), the semicolon (;) and the
grave accent (`).
Range: 1 to 19 ASCII characters.
Default value: none

Listen Mode Indicates if Listen Mode is active.

Range: checkmark / no checkmark
Default value: no checkmark (Listen Mode is not active)

Scan Priority The default priority level of this master protocol instance on the multidrop
(Multidrop specific) link it shares with additional master protocol instances.
An instance with a higher priority level has precedence over lower priority
instances when it needs to transmit a scan request on the link.
Note: This setting is only effective if a multidrop connection is assigned to this
master protocol instance.
Range: 0 (highest) to 100 (lowest)
Default value: 1 (normal)

SMP Gateway Protocol Common Concepts Reference Manual • A-1

 Setting Description
Control Enabled Indicates if control operations are allowed for this master protocol instance.
Range: checkmark / no checkmark
Default value: checkmark (control operations are allowed)

Ignore Quality for Indicates if control operations will be performed by this master protocol
Control instance on output points even when their quality is bad.
Range: checkmark / no checkmark
Default value: no checkmark (output point quality must be good)

Device Time Zone The time zone at which the device clock is set.
This setting is used in conjunction with the Auto Adjust DST setting to
convert device-reported timestamps from local time to UTC time.
It is also used for device clock synchronization by the master, to convert the
SMP Gateway current time from UTC to local time.
By default, SMP Config assumes that the device clock is set to use UTC
time, which corresponds to the GMT time zone modifier setting.

Auto Adjust DST Indicates if the device clock is adjusted for daylight savings.
This setting is used in conjunction with the Device Time Zone setting to
convert device-reported timestamps from local time to UTC time.
It is also used for device clock synchronization by the master, to convert the
SMP Gateway current time from UTC to local time.
Range: checkmark / no checkmark
Default value: no checkmark (device clock is not adjusted for DST)

Selection Timeout The maximum amount of time the master will wait, following the successful
selection of an output point, for the reception of an execution control request
on this point.
If set to 0, the selection timer is deactivated.
Range: 0 to 3,600,000 milliseconds (1 hour)
Default value: 10,000 milliseconds

Test Mode Point The name of a binary input point used for the Test Mode function.
(Test Mode specific)
Range: The name of any binary input, without the device prefix
Default value: no text (Test Mode is inactive)

Test Mode Type Indicates which data points will be considered by the Test Mode function.
(Test Mode specific)
Range: Analog Inputs
Binary Inputs
Inputs
Analog Outputs
Binary Outputs
Outputs
All
None
Default value: None

A-2 ● Appendix A - Master Protocol Common Settings Reference

 Setting Description
Block Control in Test Indicates that control operations will be blocked on the corresponding output
Mode points while in Test Mode.
(Test Mode specific)
Note: This setting is only effective if the Test Mode Type setting is set to Analog
Outputs, Binary Outputs, Outputs, or All.
Range: checkmark / no checkmark
Default value: no checkmark (control operations are allowed)

Notify When Ready Indicates if this master protocol instance will notify slave protocol instances
of the completion of its first general interrogation, or of a timeout if
communication cannot be established with the device.
Range: checkmark / no checkmark
Default value: no checkmark (master will not notify slaves)

Hot-Standby Support Indicates that hot standby redundancy is activated for this master protocol
(Redundancy specific) instance.
Note: This setting is only effective when the SMP Gateway is part of a redundancy
group.
Range: checkmark / no checkmark
Default value: no checkmark (hot standby is inactive)

Delay Between Tx Indicates the minimum delay, in milliseconds, between two successive
transmissions.
Range: 0 to 60,000 milliseconds
Default value: 0 millisecond

Table A-1 Master Protocol Common General Settings

Master Protocol Common Redundancy Settings

Redundancy settings specify the general behavior of a second link to an IED, when link
redundancy is required.

Setting Description
Enabled Indicates that link redundancy is activated for this master protocol instance.
Range: checkmark / no checkmark
Default value: no checkmark (link redundancy is inactive)

Link 1 Preferred Indicates that the first link should always be used when it is available.
Range: checkmark / no checkmark
Default value: no checkmark (first link has no precedence over the
second)

Link 1 Test Interval The delay, in milliseconds, between two complete link test requests on the
first link.
Range: 0 to 300,000 milliseconds
Default value: 3000 milliseconds

SMP Gateway Protocol Common Concepts Reference Manual • A-3

 Setting Description
Link 2 Test Interval The delay, in milliseconds, between two complete link test requests on the
second link.
Range: 0 to 300,000 milliseconds
Default value: 3000 milliseconds

Scan Priority The default priority level of this master protocol instance’s second link on
(Multidrop specific) the multidrop link it shares with additional master protocol instances.
An instance with a higher priority level has precedence over lower priority
instances when it needs to transmit a scan request on the link.
Note: This setting is only effective if this redundant link is a multidrop connection.
Range: 0 (highest) to 100 (lowest)
Default value: 1 (normal)

Selection Timeout The maximum amount of time the master will wait on the second link,
following the successful selection of an output point, for the reception of an
execution control request on this point.
If set to 0, the selection timer is deactivated.
Range: 0 to 3,600,000 milliseconds (1 hour)
Default value: 10,000 milliseconds

Delay Between Tx Indicates the minimum delay, in milliseconds, between 2 successive

transmissions over the second link.
Range: 0 to 60,000 milliseconds
Default value: 0 millisecond

Table A-2 Master Protocol Common Redundancy Settings

Master Protocol Common Switched Connection Settings

Switched connection settings specify how a master protocol instance behaves when connected to
an IED through a switched connection.

Setting Description
Enabled Indicates that Switched Mode is activated for this master protocol instance.
Range: checkmark / no checkmark
Default value: no checkmark (Switched Mode is inactive)

Accept Incoming Indicates that the master protocol instance will accept incoming connections.
Connections
Two connection instances must be assigned to this master protocol instance:
a master (client) connection instance for outgoing connections, and a slave
(server) connection instance for incoming connections.
Range: checkmark / no checkmark
Default value: checkmark (master will accept incoming connections)

A-4 ● Appendix A - Master Protocol Common Settings Reference

 Setting Description
Force Init Indicates if a general interrogation is to be performed each time connection
is established with the device; otherwise, general interrogations are
performed only at startup or if the device resets.
Range: checkmark / no checkmark
Default value: no checkmark (GI performed at startup and device resets)

Max Retries Maximum number of times the master protocol instance retries to establish a
connection with the device before reporting a communication failure.
Range: 0 to 14
Default value: 3

Retry Delay The amount of time to wait before retrying to establish a connection with the
device.
Range: 0 to 2,147,483,647 milliseconds
Default value: 300,000 milliseconds (5 minutes)

Urgent Connections The amount of time during which the master protocol instance can try to
Timeout establish a connection with the device, when an urgent situation arises,
before aborting the connection establishment operation and reporting a
communication failure.
Note: This setting has precedence over the Max Retries setting when an urgent
situation arises.
Range: 0 to 2,147,483,647 milliseconds
Default value: 120,000 milliseconds (2 minutes)

Inactivity Timeout The amount of time during which the master protocol instance can keep the
connection to the device alive when there is no significant data exchanged
with the device, before terminating the communication session.
Range: 0 to 2,147,483,647 milliseconds
Default value: 120,000 milliseconds (2 minutes)

Control Inactivity The amount of time during which the master protocol instance can keep the
Timeout connection to the device alive when there is no significant data exchanged
with the device and if the connection was initiated to perform a control
operation, before terminating the communication session.
Range: 0 to 2,147,483,647 milliseconds
Default value: 120,000 milliseconds (2 minutes)

Max Comm Timeout The maximum amount of time allowed for a communication session. When
this timer expires, the communication session is terminated, even if valuable
data is still being exchanged.
Range: 0 to 2,147,483,647 milliseconds
Default value: 600,000 milliseconds (10 minutes)

Table A-3 Master Protocol Common Switched Connection Settings

Master Protocol Common Switched Connection Schedule Settings

Switched connection schedule settings define when a master protocol instance will establish a
connection with the device on a regular basis.

SMP Gateway Protocol Common Concepts Reference Manual • A-5

 Setting Description
Start Time The number of minutes after midnight that designates the start of the call
period.
Range: 0 to 1,439 minutes

Stop Time The number of minutes after midnight that designates the end of the call
period.
If the Stop Time setting has the same value as the Start Time setting, its
reference is not midnight but noon.
Range: 0 to 1,439 minutes

Comm Cycle The amount of time between two calls to the device, during the call period.
Range: 1 to 1,440 minutes

Table A-4 Master Protocol Common Switched Connection Schedule Settings

Master Protocol Common File Settings

File settings specify how IED files will be processed by a master protocol instance.

Setting Description
Name The long name associated with this type of event file. This setting is
(Event file specific) available for information purposes and is read-only.

Short Name The short name associated with this type of event file, used to build file
(Event file specific) names. This setting is available for information purposes and is read-only.

Disabled Indicates that the master protocol instance will not attempt to retrieve IED
files of this type.
Range: checkmark / no checkmark
Default value: no checkmark (files if this type will be retrieved)

Folder The system folder where IED files of this type will be stored.
Allowed values: As shown in the drop-down list.
Default value: No folder

File Rule The file retrieval rule that applies to this type of event file; this rule defines
(Event file specific) which file should be retrieved and in which order, if applicable.
Allowed values: New files only
Files from last X days (where X = Max File Age setting)
All files
Default value: New files only

Max File Age Maximum file age, in days, of the files to be downloaded, that is, from file
(Event file specific) creation to event list retrieval.
Range: 1 to 32,767 days, if File Rule is Files from last X days
0, otherwise
Default value: 0 days

A-6 ● Appendix A - Master Protocol Common Settings Reference

 Setting Description
Min Free Disk Space Minimum free disk space, in megabytes, that must be available in the
specified system folder to allow an IED file of this type to be retrieved.
System folder space will not be checked if Min Free Disk Space if set to 0.
Range: 0 to 2,147,483,647 megabytes
Default value: 0 megabytes

Extra Info Optional, free-form text providing extra information about this type of IED
file. This extra information is used as part of the corresponding files names.
Note: Special characters \ / : * ? “ < > | and control characters cannot be used.
Range: 1 to 19 ASCII characters.
Default value: none

Description An optional description for event or configuration files of this type.

Range: 1 to 63 ASCII characters.
Default value: none

Table A-5 Master Protocol Common File Settings

Master Protocol Common Analog Input Settings

Analog input settings define the main characteristics of each analog input data point of the device,
and how its corresponding data will be processed by a master protocol instance.

Setting Description
Name The tag name associated with this data point; this tag name must be unique
in this master protocol instance configuration, but also in the SMP Gateway
configuration.
To ensure that this point name is unique in the entire system, it is preceded
by the Device Prefix, as specified in the general settings.
The following characters cannot be used as part of a data point name: the
comma (,), the quotation mark ("), the semicolon (;) and the grave accent (`).
Range: 1 to 39 ASCII characters
Default value: none

Disabled Indicates that this data point will be ignored by the master protocol instance.
This setting can be used, for example, to temporarily remove from
configuration data points that are in problem due to hardware failures.
Range: checkmark / no checkmark
Default value: no checkmark (the point is active)

Persistent Indicates if the value, quality and timestamp of the data point will be
(Switched mode specific) retained if the SMP Gateway is restarted.
Range: checkmark / no checkmark
Default value: no checkmark (value, quality and timestamp not persisted)

SMP Gateway Protocol Common Concepts Reference Manual • A-7

 Setting Description
Monitor Activity Indicates that this point will be monitored to determine whether the current
(Switched mode specific) communication session should be kept alive or terminated.
Range: checkmark / no checkmark
Default value: no checkmark (data point activity is not monitored)

Input Scale Scaling factor applied on the input read by the protocol, regardless of its
type (raw or floating point), to generate a reported value.
The calculation is done in floating point, but the reported value will remain
of the same type as read by the protocol component.
The following equation is used:

Reported value = (protocol value * input scale) +

input offset
Range: –3.4E38 to 3.4E38, excluding 0.0
Default value: 1.0

Input Offset Offset value applied on the input read by the protocol, regardless of its type
(raw or floating point), to generate a reported value.
The calculation is done in floating point, but the reported value will remain
of the same type as read by the protocol component.
The following equation is used:

Reported value = (protocol value * input scale) +

input offset
Range: –3.4E38 to 3.4E38
Default value: 0.0

Scale Scaling factor used to convert raw (32-bit) values to significant engineering
units (floating point), and vice versa. The conversion depends on the format
of the reported value.
The following equation is used:

E.U. value = (raw value * scale) + offset

Range: –3.4E38 to 3.4E38, excluding 0.0
Default value: 1.0

Offset Offset value used to convert raw (32-bit) values to significant engineering
units (floating point), and vice versa. The conversion depends on the format
of the reported value.
The following equation is used:

E.U. value = (raw value * scale) + offset

Range: –3.4E38 to 3.4E38
Default value: 0.0

A-8 ● Appendix A - Master Protocol Common Settings Reference

 Setting Description
SMP Deadband The minimum engineering value variation that must be detected for this data
point for the new value to be reported.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes are reported)

Comm Deadband If the Monitor Activity setting is selected, engineering value variations
(Switched mode specific) larger than this Comm Deadband setting value are considered as significant
data changes.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes are considered as significant)

Units Engineering units, which accompany this data point’s values in the various
SMP Tools.
Allowed values: As shown in the drop-down list
Default value: Undefined

Description An optional point description, which accompanies this point in the various
SMP Tools.
Range: 1 to 63 ASCII characters
Default value: none

Table A-6 Master Protocol Common Analog Input Settings

Master Protocol Common Binary Input Settings

Binary input settings define the main characteristics of each binary input data point of the device,
and how its corresponding data will be processed by a master protocol instance.

Setting Description
Name The tag name associated with this data point; this tag name must be unique
in this master protocol instance configuration, but also in the SMP Gateway
configuration.
To ensure that this point name is unique in the entire system, it is preceded
by the Device Prefix, as specified in the general settings.
The following characters cannot be used as part of a data point name: the
comma (,), the quotation mark ("), the semicolon (;) and the grave accent (`).
Range: 1 to 39 ASCII characters
Default value: none

Disabled Indicates that this data point will be ignored by the master protocol instance.
This setting can be used, for example, to temporarily remove from
configuration data points that are in problem due to hardware failures.
Range: checkmark / no checkmark
Default value: no checkmark (the point is active)

SMP Gateway Protocol Common Concepts Reference Manual • A-9

 Setting Description
Persistent Indicates if the state, quality and timestamp of the data point will be retained
(Switched mode specific) if the SMP Gateway is restarted.
Range: checkmark / no checkmark
Default value: no checkmark (state, quality and timestamp not persisted)

Inverted Pol Indicates that this point value (state) will be inverted before it is reported.
Range: checkmark / no checkmark
Default value: no checkmark (point state is not inverted)

Monitor Activity Indicates that this point will be monitored to determine whether the current
(Switched mode specific) communication session should be kept alive or terminated.
Range: checkmark / no checkmark
Default value: no checkmark (data point activity is not monitored)

Description An optional point description, which accompanies this point in the various
SMP Tools.
Range: 1 to 63 ASCII characters
Default value: none

Table A-7 Master Protocol Common Binary Input Settings

Master Protocol Common Analog Output Settings

Analog output settings define the main characteristics of each analog output data point of the
device, and how its corresponding data will be processed by a master protocol instance.

Setting Description
Name The tag name associated with this data point; this tag name must be unique
in this master protocol instance configuration, but also in the SMP Gateway
configuration.
To ensure that this point name is unique in the entire system, it is preceded
by the Device Prefix, as specified in the general settings.
The following characters cannot be used as part of a data point name: the
comma (,), the quotation mark ("), the semicolon (;) and the grave accent (`).
Range: 1 to 39 ASCII characters
Default value: none

Disabled Indicates that this data point will be ignored by the master protocol instance.
This setting can be used, for example, to temporarily remove from
configuration data points that are in problem due to hardware failures.
Range: checkmark / no checkmark
Default value: no checkmark (the point is active)

A-10 ● Appendix A - Master Protocol Common Settings Reference

 Setting Description
Monitor Activity Indicates this point will be monitored to determine whether the current
(Switched mode specific) communication session should be kept alive or terminated.
Range: checkmark / no checkmark
Default value: no checkmark (data point activity is not monitored)

Input Scale Scaling factor applied on the input read by the protocol, regardless of its
type (raw or floating point), to generate a reported value.
The calculation is done in floating point, but the reported value will remain
of the same type as read by the protocol component.
The following equation is used:

Reported value = (protocol value * input scale) +

input offset
Range: –3.4E38 to 3.4E38, excluding 0.0
Default value: 1.0

Input Offset Offset value applied on the input read by the protocol, regardless of its type
(raw or floating point), to generate a reported value.
The calculation is done in floating point, but the reported value will remain
of the same type as read by the protocol component.
The following equation is used:

Reported value = (protocol value * input scale) +

input offset
Range: –3.4E38 to 3.4E38
Default value: 0.0

Scale Scaling factor used to convert raw (32-bit) values to significant engineering
units (floating point), and vice versa. The conversion depends on the format
of the reported value.
The following equation is used:

E.U. value = (raw value * scale) + offset

Range: –3.4E38 to 3.4E38, excluding 0.0
Default value: 1.0

Offset Offset value used to convert 32-bit values (raw) to significant engineering
units (floating point), and vice versa. The conversion depends on the format
of the reported value.
The following equation is used:

E.U. value = (raw value * scale) + offset

Range: –3.4E38 to 3.4E38
Default value: 0.0

SMP Gateway Protocol Common Concepts Reference Manual • A-11

 Setting Description
SMP Deadband The minimum engineering value variation that must be detected for this data
point for the new value to be reported.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes are reported)

Comm Deadband If the Monitor Activity setting is selected, engineering value variations
(Switched mode specific) larger than this Comm Deadband setting value are considered as significant
data changes.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes are considered as significant)

Units Engineering units, which accompany this data point’s values in the various
SMP Tools.
Allowed values: As shown in the drop-down list
Default value: Undefined

Group Comm Ok Indicates that this point’s quality will be reported as OK as soon as the
communication link recovers from failure.
Range: checkmark / no checkmark
Default value: checkmark (point quality reported as OK on link up)

Description An optional point description, which accompanies this point in the various
SMP Tools.
Range: 1 to 63 ASCII characters
Default value: none

Table A-8 Master Protocol Common Analog Output Settings

Master Protocol Common Binary Output Settings

Binary output settings define the main characteristics of each binary output data point of the
device, and how its corresponding data will be processed by a master protocol instance.

Setting Description
Name The tag name associated with this data point; this tag name must be unique
in this master protocol instance configuration, but also in the SMP Gateway
configuration.
To ensure that this point name is unique in the entire system, it is preceded
by the Device Prefix, as specified in the general settings.
The following characters cannot be used as part of a data point name: the
comma (,), the quotation mark ("), the semicolon (;) and the grave accent (`).
Range: 1 to 39 ASCII characters
Default value: none

A-12 ● Appendix A - Master Protocol Common Settings Reference

 Setting Description
Disabled Indicates that this data point will be ignored by the master protocol instance.
This setting can be used, for example, to temporarily remove from
configuration data points that are in problem due to hardware failures.
Range: checkmark / no checkmark
Default value: no checkmark (the point is active)

Monitor Activity Indicates this point will be monitored to determine whether the current
(Switched mode specific) communication session should be kept alive or terminated.
Range: checkmark / no checkmark
Default value: no checkmark (data point activity is not monitored)

Master Duration Indicates that the activation time specified by the master station should be
Allowed used, if available, instead of the Activation Time setting value specified for
pulse control operations performed on this point.
Range: checkmark / no checkmark
Default value: checkmark (use activation time provided by master)

Activation Time The activation time, in milliseconds, to use for pulse control operations
performed on this point, when the activation time is not specified by the
operator (master station).
Range: 0 to 30,000 milliseconds
Default value: 500 milliseconds

Group Comm Ok Indicates that this point’s quality will be reported as OK as soon as the
communication link recovers from failure.
Range: checkmark / no checkmark
Default value: checkmark (point quality reported as OK on link up)

Open/Close Pair The index of the open/close pair this data point belongs to, when combining
two pulse points from a slave protocol instance to operate a single
open/close point of a master protocol instance.
Note: Only two points can share the same Open/Close Pair setting value.
Range: 0 to 65,535
Default value: 0

Description An optional point description, which accompanies this point in the various
SMP Tools.
Range: 1 to 63 ASCII characters
Default value: none

Table A-9 Master Protocol Common Binary Output Settings

SMP Gateway Protocol Common Concepts Reference Manual • A-13

 Appendix B - Slave Protocol Common Settings
Reference

This appendix presents the settings that are common to all slave protocol components, when
applicable.

Note: Protocol-specific settings are presented and described in the reference manuals
of the corresponding protocols.

Slave Protocol Common General Settings

General settings specify the general behavior of a slave protocol component instance.

Setting Description
Device Prefix A prefix for the name of each system data point provided by this slave
protocol instance.
Note: This setting is optional for a slave protocol instance; when specified, it makes
the slave-specific system data points available.
This prefix must be unique in the entire SMP Gateway configuration to
ensure that every data point name is also unique.
The following reserved words and characters cannot be used as part of a
device prefix: the word _smp (which is the device prefix of system data
points), the comma (,), the double quotes ("), the semicolon (;) and the
grave accent (`).
Range: 1 to 19 ASCII characters.
Default value: none

Inactivity Timeout The time to wait, in milliseconds, after the reception of the last valid request,
before reporting a communication failure and resetting the communication
link.
If set to 0, the inactivity timer is deactivated.
Range: 0 to 2,147,483,647 milliseconds
Default value: 300,000 milliseconds

SMP Gateway Protocol Common Concepts Reference Manual • B-1

 Setting Description
Unavailability Timeout The time to wait, in milliseconds, after the last valid request received from
the master station, or the last valid connection request received from the
master station, before declaring the communication link unavailable.
If set to 0, the unavailability timer is deactivated.
Range: 0 to 2,147,483,647 milliseconds
Default value: 60,000 milliseconds

Control Enabled Indicates if control operations are allowed for this slave protocol instance.
Range: checkmark / no checkmark
Default value: checkmark (control operations are allowed)

Control Rx Timeout The time to wait, in milliseconds, for a response to a control request from
the master protocol that owns the corresponding output point, before
responding to the master station that sent the original control request.
Range: 0 to 2,147,483,647 milliseconds
Default value: 3,600,000 milliseconds (1 hour)

Selection Timeout The maximum amount of time the slave will wait, following the successful
selection of an output point, for the reception of an execution control request
on this point.
If set to 0, the selection timer is deactivated.
Range: 0 to 3,600,000 milliseconds (1 hour)
Default value: 10,000 milliseconds

Wait for Init Timeout, The time to wait, in milliseconds, following the slave protocol instance
Max Connection Delay initialization sequence, for the master protocol instances to provide the
initial values of each subscribed data point, before the slave starts to process
master station requests.
If set to 0, the slave will accept and process requests as soon as it completes
its link initialization sequence.
Range: 0 to 2,147,483,647 milliseconds
Default value: 0

Client Time Zone The time zone at which the master station clock is set.
This setting is used in conjunction with the Auto Adjust DST setting, to
convert timestamps to transmit from UTC to local time.
It is also used on the reception of clock synchronization request, to convert
the master station local time information to UTC time.
By default, SMP Config assumes that the master station clock is set to use
UTC time, which corresponds to the GMT time zone modifier setting.

B-2 ● Appendix B - Slave Protocol Common Settings Reference

 Setting Description
Auto Adjust DST Indicates that the master station clock is adjusted for daylight savings.
This setting is used in conjunction with the Client Time Zone setting, to
convert timestamps to transmit from UTC to local time.
It is also used on the reception of clock synchronization request, to convert
the master station local time information to UTC time.
Range: checkmark / no checkmark
Default value: no checkmark (master clock is not adjusted for DST)

Time-Sync Enabled, Indicates of the slave protocol will accept clock synchronization requests
Allow Set Time, received from the master station and use them to adjust the SMP Gateway
Time Sync clock.
Range: checkmark / no checkmark
Default value: checkmark (slave will use clock synchronization requests)

Hot-Standby Support Indicates the startup status of the slave protocol instance on the standby
SMP Gateway of a SMP Gateway redundancy group.
Allowed values:
 Disabled.
Slave is not started on a standby SMP Gateway.
 Acquisition.
Slave is started while on standby, but no control operation is allowed.
 Acquisition and Control.
Slave is started while on standby, and control operations are allowed.
Default value: Disabled

Table B-1 Slave Protocol Common General Settings

Slave Protocol Common Switched Connection Settings

Switched connection settings specify how a slave protocol instance behaves when connected to a
master station through a switched connection.

Setting Description
Enabled Indicates that Switched Mode is activated for this slave protocol instance.
Range: checkmark / no checkmark
Default value: no checkmark (Switched Mode is inactive)

Allow Outgoing A checkmark indicates that the slave protocol instance can initiate outgoing
Connections connections.
Two connection instances must be assigned to this slave protocol instance: a
master (client) connection instance for outgoing connections, and a slave
(server) connection instance for incoming connections.
Allowed values: checkmark / no checkmark
Default values: no checkmark (slave cannot initiate outgoing connections)

SMP Gateway Protocol Common Concepts Reference Manual • B-3

 Setting Description
Max Retries The maximum number of connection retries the slave protocol can attempt
with the master station before declaring a communication failure.
Range: 0 to 14
Default values: 3

Retry Delay The amount of time to wait before retrying to establish a connection with the
master station.
Range: 0 to 2,147,483,647 milliseconds
Default values: 300,000 milliseconds

Table B-2 Slave Protocol Common Switched Connection Settings

Slave Protocol Common Switched Connection Schedule Settings

Switched connection schedule settings define when the slave protocol instance will establish a
connection with the master station on a regular basis.

Setting Description
Start Time The number of minutes after midnight that designates the start of the call
period.
Range: 0 to 1,439 minutes

Stop Time The number of minutes after midnight that designates the end of the call
period.
If the Stop Time setting has the same value as the Start Time setting, its
reference is not midnight but noon.
Range: 0 to 1,439 minutes

Comm Cycle The amount of time between two calls to the master station, during the call
period.
Range: 1 to 1,440 minutes

Table B-3 Slave Protocol Common Switched Connection Schedule Settings

Slave Protocol Common Analog Input Settings

Analog input settings define the analog input points to be reported to the master station.

Setting Description
Name The name that identifies the data point.
This name must be unique and should refer to an existing data point, either
produced by a master protocol instance or a system component.

Immediate Report Indicates that events occurring for this data point will be immediately
(Switched mode specific) reported to the master station, through an outgoing connection, even if such
a connection is not currently established with the master station.
Range: checkmark / no checkmark
Default value: no checkmark (events will not be reported immediately)

B-4 ● Appendix B - Slave Protocol Common Settings Reference

 Setting Description
Deadband Floating-point deadband value; only changes larger than the deadband will
be reported to the master station.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes reported to master station)

Report Deadband Floating-point deadband value used in switched mode; the slave protocol
(Switched mode specific) initiates a connection with the master station when it needs to report a value
change larger than this Report Deadband setting value.
This setting is applicable only between communication sessions, and if the
Allow Outgoing Connections setting is selected.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes trigger a call to the master station)

Disabled Indicates that the point will not be available to the master station, but will
remain in the list of configured analog inputs for possible future use.
Range: checkmark / no checkmark
Default value: no checkmark (the point will not be available)

Table B-4 Slave Protocol Common Analog Input Settings

Slave Protocol Common Binary Input Settings

Binary input settings define the binary input points to be reported to the master station.

Setting Description
Name The name that identifies the data point.
This name must be unique and should refer to an existing data point, either
produced by a master protocol instance or a system component.

Immediate Report Indicates that events occurring for this data point will be immediately
(Switched mode specific) reported to the master station, through an outgoing connection, even if such
a connection is not currently established with the master station.
Range: checkmark / no checkmark
Default value: no checkmark (events will not be reported immediately)

Disabled Indicates that the point will not be available to the master station, but will
remain in the list of configured binary inputs for possible future use.
Range: checkmark / no checkmark
Default value: no checkmark (the point will not be available)

Inverted Pol. Indicates that the point’s current state will be inverted before being reported
through the slave protocol instance.
Range: checkmark / no checkmark
Default: no checkmark (point state not inverted)

Table B-5 Slave Protocol Common Binary Input Settings

SMP Gateway Protocol Common Concepts Reference Manual • B-5

 Slave Protocol Common Analog Output Settings
Analog output settings define the analog output points to be reported to the master station.

Setting Description
Name The name that identifies the data point.
This name must be unique and should refer to an existing data point, either
produced by a master protocol instance or a system component.

Deadband Floating-point deadband value; only changes larger than the deadband will
be reported to the master station.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes reported to master station)

Report Deadband Floating-point deadband value used in Switched Mode; the slave protocol
(Switched mode specific) initiates a connection with the master station when it needs to report a value
change larger than this Report Deadband setting value.
This setting is applicable only between communication sessions, and if the
Allow Outgoing Connections setting is selected.
Range: 0.0 to 3.4E38
Default value: 0.0 (all value changes trigger a call to the master station)

Simulated Control Enables simulated control operation confirmation, and indicates for which
Confirmation control operation simulated confirmations are required from the master
protocol instance that owns the point.
Allowed values:
 None
 SELECT only
 EXECUTE only
 SELECT and EXECUTE
Default value: None (simulated confirmation not activated for this point)

Disabled Indicates that the point will not be available to the master station, but will
remain in the list of configured analog outputs for possible future use.
Range: checkmark / no checkmark
Default value: no checkmark (the point will not be available)

Table B-6 Slave Protocol Common Analog Output Settings

Slave Protocol Common Binary Output Settings

Binary output settings define the binary output points to be reported to the master station.

Setting Description
Name The name that identifies the data point.
This name must be unique and should refer to an existing data point, either
produced by a master protocol instance or a system component.

B-6 ● Appendix B - Slave Protocol Common Settings Reference

 Setting Description
Immediate Report Indicates that events occurring for this data point will be immediately
(Switched mode specific) reported to the master station, through an outgoing connection, even if such
a connection is not currently established with the master station.
Range: checkmark / no checkmark
Default value: no checkmark (events will not be reported immediately)

Simulated Control Enables simulated control operation confirmation, and indicates for which
Confirmation control operation simulated confirmations are required from the master
protocol instance that owns the point.
Allowed values:
 None
 SELECT only
 EXECUTE only
 SELECT and EXECUTE
Default value: None (simulated confirmation not activated for this point)

Disabled Indicates that the point will not be available to the master station, but will
remain in the list of configured binary outputs for possible future use.
Range: checkmark / no checkmark
Default value: no checkmark (the point will not be available)

Inverted Pol. Indicates that the point’s current state will be inverted before being reported
through the slave protocol instance.
Range: checkmark / no checkmark
Default: no checkmark (point state not inverted)

Table B-7 Slave Protocol Common Binary Output Settings

SMP Gateway Protocol Common Concepts Reference Manual • B-7

 Appendix C - Additional Settings Reference

This appendix presents additional settings that may be required during the configuration process of
master or slave protocol instances.

System Folder Settings

System folder settings define the virtual folders that are used by master protocol instances to store
event and configuration files.

Setting Description
Folder ID The numerical identifier of the folder, which must be unique in a given
SMP Gateway configuration.
The numerical Folder ID, which is a number ranging from 1 to 99. On an
SMP Gateway, each system folder, remote or local, must have a unique ID.
Range: 1 to 99

Name The name of the folder; this name references the folder in the file settings of
the master protocol instances that will use it. It also appears in the various
SMP Tools.

Location The location of the shared folder, using the Unified Naming Convention.
(Remote folder specific)
For example, the location \\cpu104\Events refers to a shared folder
called Events on a computer named cpu104.

Username The username and password of the account that the SMP Gateway will use
Password to connect to this remote system folder, including the name of the
(Remote folder specific) domain/workgroup the account belongs to.

Low Disk Space Alarm The minimum number of bytes that must be available in the system folder; if
available disk space goes below this minimum, the SMP Gateway will
advise that space is running low on this system folder, through a dedicated
system data point.
Range: 0 to 2,147,483,647 bytes
Default value: 0 byte (no notification)

SMP Gateway Protocol Common Concepts Reference Manual • C-1

 Setting Description
Compress Indicates that the IED files downloaded to this folder will be compressed
and archived in a ZIP file. If multiple files are retrieved at once, all files will
be compressed and archived together in the same ZIP file.
Note: If the retrieved files are native COMTRADE files, you must compress them.
Range: checkmark / no checkmark
Default value: checkmark, for local system folders
no checkmark, for remote system folders

Description An optional description field.

Table C-1 System Folder Settings

C-2 ● Appendix C - Additional Settings Reference

 Appendix D - System Data Point Reference

This appendix presents the various system data points that available for most master and slave
protocols.

Master Protocol System Data Points

Name Description
System Analog Inputs

___AOCtrlFailCount Total number of non-completed or failed control operations on analog

outputs.

___AOCtrlOKCount Total number of successfully completed control operations on analog

outputs.

___BOCtrlFailCount Total number of non-completed or failed control operations on binary

outputs.

___BOCtrlOKCount Total number of successfully completed control operations on binary

outputs.

___ChksumErrorCount Total number of checksum errors that were detected by the protocol
component.

___CommErrorCount Total number of unsuccessful exchanges with the device.

___CommOKCount Total number of successful exchanges with the device.

___CommTimeoutCount Total number of communication timeouts.

___CommLinkRstCount Total number of device link resets.

System Binary Inputs

___AOCtrlEnabled If set to 1, control operations on analog outputs are allowed.

If set to 0, such operations that are requested by slave or system
components are refused by the master protocol instance.

___BOCtrlEnabled If set to 1, control operations on binary outputs are allowed.

If set to 0, such operations that are requested by slave or system
components are refused by the master protocol instance.

___CommStatus If set to 1, indicates that communication is established and active with the
(Switch mode specific) device.

SMP Gateway Protocol Common Concepts Reference Manual • D-1

 Name Description
___CommFail If set to 1, indicates that the master protocol instance no longer
communicates with the device.

___GICompleted If set to 1, indicates that last general interrogation was completed

successfully.
If set to 0, indicates that the last general interrogation failed, or that no
general interrogation was performed since last system reset.

___LinkActive_(n) If set to 1, indicates that link ’n’ is active; it means that this is the
(Link redundancy specific) communication link that is currently used by the master protocol instance.
If set to 0, indicates that link ‘n’ is not active; however, it may be available
(see ___LinkAvailable_(n) below).

___LinkAvailable_(n) If set to 1, indicates that link ’n’ is available; it means that the
(Link redundancy specific) communication link is established, although it may not currently be used
by the protocol component (see ___LinkActive_(n) above).
If set to 0, indicates that the communication link is not established.

___LinkOkSinceFO_(n) If set to 1, indicates that successful exchanges occurred over the

(Link redundancy specific) communication link since the last failover.
If set to 0, indicates that no successful exchange occurred over the
communication link since the last failover.

___ListenModeEnabled If set to 1, indicates that Listen Mode is enabled.

Otherwise, is set to 0.

___NotifyReady If set to 1, indicates that the active link has completed its general
interrogation and has notified slave protocol instances.
Otherwise, is set to 0, and reset to 0 each time a failover occurs.

___ScanEnabled If set to 1, indicates that general scan (polling) is activated for the master
protocol instance.
If set to 0, indicates that general scan (polling) was suspended, using the
___ScanDisable analog output system point, for this master protocol
instance.

System Binary Outputs

___AOCtrlDisable Deactivate analog control operation processing until further notice or

system reset.

___AOCtrlEnable Reactivate analog control operation processing (if currently deactivated).

___BOCtrlDisable Deactivate binary control operation processing until further notice or

system reset.

___BOCtrlEnable Reactivate binary control operation processing.

___CountersFrzScan Force immediate reporting of device counters.

___ForceClockSync Force device clock synchronization with the SMP Gateway clock.

___ForceGI Force the transmission of a general interrogation request to the device.

D-2 ● Appendix D - System Data Point Reference

 Name Description
___ForceResetRTU Force the transmission of a device reset request to the device.

___ListenModeDisable Deactivate Listen Mode until further notice.

___ListenModeEnable Reactivate Listen Mode (if currently deactivated).

___LogCountersFrz Force immediate report of all system analog inputs.

___LogCountersFrzRst Report and then reset all system analog inputs.

___LogCountersRst Reset and then report all system analog inputs.

___ScanDisable Deactivate general scan (polling) until further notice or system reset.

___ScanEnable Reactivate general scan (polling) (if currently deactivated).

___ScanFast Set the general scan (polling) operation to the highest priority level.

___ScanNormal Set the general scan (polling) operation at its pre-configured priority level.

___ScanReset Reset the communication link with the device, and the general scan
(polling) process by the same occasion.

___ScanSlow Set the general scan (polling) operation to the lowest priority level.

Table D-1 Master Protocol System Data Points

Slave Protocol System Data Points

Note: Slave protocol system data points are not visible in SMP Config. Moreover, to
activate them in the configuration of a given slave protocol instance, you must
define the slave protocol Device Prefix general setting.

Name Description
System Binary Inputs

___LinkActive Indicates whether or not the link configured for this protocol instance
shows signs of activity.

___LinkAvailable Indicates whether or not the link configured for this protocol instance is
operational.

___ScanEnabled If set to 1, indicates that communications between this slave protocol

instance and a master station are currently allowed; use the
___ScanDisable system binary output point to deactivate communications.
If set to 0, indicates that communications are deactivated for this protocol
instance; use the ___ScanEnable system binary output point to re-activate
communications.

SMP Gateway Protocol Common Concepts Reference Manual • D-3

 Name Description
System Binary Outputs

___ScanDisable Terminate the communication link between this slave protocol instance
and the corresponding master station, and prevent the slave protocol
instance from establishing any new connection.
As a result, it sets the ___ScanEnabled system binary input to 0.

___ScanEnable Allow a slave protocol instance for which communications were

deactivated (using the ___ScanDisable system binary output) to start
accepting new connections from a master station again.
As a result, it sets the ___ScanEnabled system binary input to 1.

Table D-2 Slave Protocol System Data Points

Local/Remote Control Operation System Data Points

The following system data points are available to manage the control operation mode of the entire
SMP Gateway:

Name Description
System Binary Inputs

_smp___localControl If set to 1, indicates that the SMP Gateway is in Local Control Operation
mode, which means that it only allows control operations from a local
HMI.
If set to 0, indicates that the SMP Gateway is Remote Control Operation
mode, which means that it allows control operations from the SCADA
(i.e. via slave protocol instances).
When the SMP Gateway starts up for the first time, this point is set to 0.
The value of this point is persisted, i.e. its value is stored in non-volatile
memory and is not reset to 0 when the SMP Gateway restarts.

System Binary Outputs

_smp___setLocalControl Allow the user to switch from Remote Control Operation mode to Local
Control Operation mode.
Current control operation mode is indicated by the _smp___localControl
system binary input.

Table D-3 Local/Remote Control Operation System Data Points

System Folder System Data Points

The following system data points are available to monitor the current status of each system folder:

Note: Each set of point is identified using the corresponding system folder Folder ID
and Name settings.

D-4 ● Appendix D - System Data Point Reference

 Name Description
System Analog Inputs

_smp___Folder<ID><Name>_FreeDiskSpace Indicates the amount of disk space that is available on the

host of the system folder.

System Binary Inputs

_smp___Folder<ID><Name>_Available If set to 1, indicates that the system folder is available to the

SMP Gateway.

_smp___Folder<ID><Name>_LowDiskSpace If set to 1, indicates that the system folder host is running low
on disk space.

Table D-4 System Folder System Data Points

SMP Gateway Protocol Common Concepts Reference Manual • D-5