Reference Manual

SES-92 Slave Protocol

Documentation for part number P-SSPR-4001
© 2012 Cooper Power Systems, LLC – All rights reserved.
The information in this document is subject to change without notice.

Cooper Power Systems

Energy Automation Solutions
730 Commerciale Street
Suite 200
Saint-Jean-Chrysostome, Quebec
Canada G6Z 2C5
Phone: +1.418.834.0009
Fax: +1.514.227.5256
Email: PSMO-sales@cooperindustries.com
Web: http://www.cooperpower.com

Technical Support: PSSJ-support@cooperindustries.com

S1120-64-1, version 4
Contents
Contents ........................................................................................................................................... i
1. Introduction ............................................................................................................................. 1
2. Features.................................................................................................................................... 2
2.1 Communication ........................................................................................................................ 2
2.2 Supported Functions................................................................................................................. 2
2.2.1 Implementation Restrictions and Warnings .................................................................. 3
3. Configuration Settings ............................................................................................................. 4
3.1 General Settings....................................................................................................................... 4
3.2 Analog Inputs Settings ............................................................................................................. 5
3.2.1 Analog Inputs Settings ............................................................................................... 5
3.2.2 Analog References Settings ........................................................................................ 5
3.2.3 Accumulator Inputs Settings ....................................................................................... 5
3.2.4 Solid State Meter Inputs Settings ................................................................................ 6
3.3 Binary Inputs Settings .............................................................................................................. 6
3.3.1 Binary Inputs Settings ................................................................................................ 6
3.4 Analog Outputs Settings ........................................................................................................... 6
3.4.1 Analog Outputs Settings ............................................................................................. 6
3.5 Binary Outputs Settings ............................................................................................................ 7
3.5.1 Binary Outputs Settings .............................................................................................. 7
4. Implementation Details ........................................................................................................... 8
4.1 Diagnostic Flags ....................................................................................................................... 8
4.2 Time Synchronization ............................................................................................................... 8
4.3 Time Format ............................................................................................................................ 8
4.4 Digital Status Change ............................................................................................................... 8
4.5 Reset RTU Actions .................................................................................................................... 8
4.6 Accumulator and Solid State Meter Inputs ................................................................................. 9
5. Troubleshooting ..................................................................................................................... 10

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ●I

Tables
Table 2-1 Communication features ................................................................................... 2
Table 2-2 Supported requests ........................................................................................... 3
Table 3-1 General settings ................................................................................................ 5
Table 3-2 Analog inputs settings ...................................................................................... 5
Table 3-3 Analog references settings ............................................................................... 5
Table 3-4 Accumulator inputs settings ............................................................................. 6
Table 3-5 Solid state meter inputs settings ...................................................................... 6
Table 3-6 Binary inputs settings ....................................................................................... 6
Table 3-7 Analog outputs settings .................................................................................... 7
Table 3-8 Binary outputs settings ..................................................................................... 7
Table 5-1 Troubleshooting .............................................................................................. 11

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ● III

1. Introduction
This manual provides the information required to install and set up a SES-92 slave protocol
component in an SMP Gateway.
This protocol component is used to host data used by a remote control center, compatible with
the SES-92 protocol definition. It can also be used to send control requests to devices connected
to the SMP Gateway.
You must be familiar with the SMP Gateway environment, slave protocol concepts and the
SES-92 protocol specification before proceeding with this document. You can get this information
by reading the following documents:
 SES-92 RTU Protocol Manual – Release 2.0, Draft Release H.1, 08/01/98.
 Protocol Common Concepts Reference Manual, S1120-11-1, Cooper Power Systems, LLC.
 SMP Gateway User Manual, S1120-10-1, Cooper Power Systems, LLC.

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ●1

2. Features
This chapter enumerates the features provided by the SES-92 slave protocol component.

2.1 Communication
The following communication features are available when interconnecting devices to the
SMP Gateway hardware:

Feature Comment
Serial Port This protocol component supports RS-232 and RS-485 interfaces at
bit rates of up to 115,200 b/s.
Multidrop Multiple instances of this protocol component can share a single
serial port, as long as different addresses are used to identify the
devices and that the serial communication hardware supports such
a feature.
TCP/IP This protocol component supports TCP/IP communications.

Table 2-1 Communication features

2.2 Supported Functions

The following table enumerates the functions currently supported by the SES-92 Slave protocol
component:

Function Code Description

(hexadecimal)
00 Poll Exception Data
01 Repeat Last Message
02 Continue Message
03 Synchronize Protocol Version
10 Dump Status Data
11 Report Status Exception Data
12 Dump Extended Status Data
20 Dump Analog Data
21 Report Analog Exception Data
22 Dump Analog Group Data
23 Report Analog Group Exception Data
24 Assign Deadband and Group
25 Dump ADC Reference Data
30 Freeze Accumulator Data
31 Dump Accumulator Data
33 Dump Solid State Meter Data
50 Dump Digital Status Change Data

2● SES-92 SLAVE PROTOCOL REFERENCE MANUAL

 Function Code Description
(hexadecimal)
52 Synchronize Time
53 Read Time
54 Set Time Bias
60 SBO Trip/Close Select
61 SBO Trip/Close Execute
62 SBO Setpoint Select
63 SBO Setpoint Execute
64 DO Setpoint Execute
70 Reset RTU
73 Dump Diagnostics Request
79 RTU Configuration Complete

Table 2-2 Supported requests

2.2.1 Implementation Restrictions and Warnings

The following protocol and/or implementation restrictions must be understood:
 The data reported by the SES-92 slave protocol is updated internally as fast as it is injected
in the Real-Time Data Exchange component by the various master components.
Consequently, when a master station is exchanging information with a SES-92 slave, the
freshness of the data depends on the configuration (polling cycle/report by exception) of the
master station, as well as on the polling cycle of the masters that are providing the data.
 The protocol specification states that a slave must always increment its Julian Day from 365
to 366 in anticipation of a leap year. However, our implementation will check if the current
system year is a leap year before incrementing its Julian Day from 365 to 366. Hence,
masters are not required to reset the Julian Day back to day 1 on non-leap years.
 The non-volatile options for the Operating Parameter Block (NV-OPB) and for the
Configuration Data Block (NV-CDB) are not supported.
 Since there is no non-volatile Data Block NV-CDB, a RTU Configuration Complete request
with the CNV flag set will be refused by the slave protocol component. In that case, the
Success Code of the corresponding reply will be set to 00h (Unsupported Feature
Requested).
 The FRZ, COV and RAE flags of the Operating Parameter Block are not supported.
 Analog input points that are either disabled or not configured will not be included in any
group (including group 0).
 The slave protocol instance is limited on the quantity of simultaneous control operation that
can take place at the same time. Hence, the DO Setpoint Execute request (function codes 64
in hexadecimal) will operate each setpoint included in the request until it reaches that limit.
Any setpoints that are exceeding this limit will not be executed.
 The Reset RTU request will only reset the slave protocol instance, and not the entire
SMP Gateway.

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ●3

3. Configuration Settings
This chapter enumerates the configuration settings you have to specify for each SES-92 slave
protocol instance. The SMP Config software program is generally used to define these settings.
Only the settings specific to the SES-92 protocol are described here. The settings common to all
slave protocol components are described in the Protocol Common Concepts Reference Manual.

3.1 General Settings

Each instance of this slave protocol component contains general settings, which set the general
behavior of the component. The following table shows the general settings that are specific to
the SES-92 slave protocol.

Setting Description
RTU Group The RTU Group is the second byte of the RTU address. It identifies
in which group the slave component reside. For the slave to
recognize a master request, both the RTU Group and the RTU
Identifier of the request must match the slave configuration.
The SES-92 slave also supports the Group Global Address used
to address all RTUs assigned to a common group. Note that
requests using the Group Global Address will not be replied by the
slave protocol component.
Range: 0 to 254
Default value: 0
RTU Identifier The RTU Identifier is the first byte of the RTU address. It uniquely
identifies a RTU within a specified RTU group. For the slave to
recognize a master request, both the RTU Group and the RTU
Identifier of the request must match the slave configuration.
The SES-92 slave also supports the System Global Address used
to address all RTUs assigned to all groups. Note that requests using
the System Global Address will not be replied by the slave protocol
component.
Range: 0 to 254
Default value: 0
SOE Queue Length The maximum number of Digital Status Change Events that can be
held in the Sequence Of Event (SOE) Digital Status Change queue.
The content of this queue is retrieved using the Dump Digital Status
Change Data request. A value of 0 means that the Digital Status
Change queue is disabled. If the queue is full and another Digital
Status Change occurs, the oldest change will be removed from the
queue to make room for the new change.
Note however that this ‘oldest’ change is based on the time the
change was added to the queue and not on the timestamp of the
change itself.
Range: 0 to 65,535
Default value: 500

4● SES-92 SLAVE PROTOCOL REFERENCE MANUAL

 Setting Description
Time-Sync Enabled A checkmark allows the Synchronize Time request to modify the
SMP Gateway internal clock. If no checkmark is set for this setting,
the slave protocol will still respond to the Synchronize Time request,
but it will have no effect.
Range: Checkmark / no checkmark
Default value: No checkmark

Table 3-1 General settings

3.2 Analog Inputs Settings

3.2.1 Analog Inputs Settings
Each instance of the slave protocol component may contain several analog input points to be
reported to the master station. Analog input settings tell the component how to map analog
inputs from the RTDX to protocol addresses. The following table shows the analog input settings
that are specific to the SES-92 slave protocol.

Setting Description
Identifier The analog input identifier assigned to the point. This number
uniquely identifies a point within all analog inputs.
Range: 0 to 4095
Default value: 0

Table 3-2 Analog inputs settings

3.2.2 Analog References Settings

Each instance of the slave protocol component may contain several analog references (also called
“ADC Reference Points” or “A/D Converter Points”) to be reported to the master station. Analog
references settings tell the component how to map analog inputs from the RTDX to protocol
addresses. The following table shows the analog references settings that are specific to the SES-
92 slave protocol.

Setting Description
Identifier The analog reference identifier assigned to the point. This number
uniquely identifies a point within all analog references.
Range: 0 to 4095
Default value: 0

Table 3-3 Analog references settings

3.2.3 Accumulator Inputs Settings

Each instance of the slave protocol component may contain several accumulator inputs to be
reported to the master station. Accumulator input settings tell the component how to map analog
inputs from the RTDX to protocol addresses. The following table shows the accumulator input
settings that are specific to the SES-92 slave protocol.

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ●5

 Setting Description
Identifier The accumulator input identifier assigned to the point. This number
uniquely identifies a point within all accumulator inputs.
Range: 0 to 255
Default value: 0

Table 3-4 Accumulator inputs settings

3.2.4 Solid State Meter Inputs Settings

Each instance of the slave protocol component may contain several solid state meter inputs to be
reported to the master station. Solid state meter input settings tell the component how to map
analog inputs from the RTDX to protocol addresses. The following table shows the solid state
meter input settings that are specific to the SES-92 slave protocol.

Setting Description
Identifier The solid state meter input identifier assigned to the point. This
number uniquely identifies a point within all solid state meter
inputs.
Range: 0 to 255
Default value: 0

Table 3-5 Solid state meter inputs settings

3.3 Binary Inputs Settings

3.3.1 Binary Inputs Settings
Each instance of the slave protocol component may contain several binary input points (also
called “Digital Input Points” or “Status”) to be reported to the master station. Binary inputs
settings tell the component how to map binary inputs from the RTDX to protocol addresses. The
following table shows the binary inputs settings that are specific to the SES-92 slave protocol.

Setting Description
Identifier The binary input identifier assigned to the point. This number
uniquely identifies a point within all binary inputs.
Range: 0 to 4095
Default value: 0
Use SOE Indicates if this point will generate Sequence Of Events (SOE) on
point changes. If this parameter is checked, each state transition on
this point will add a Digital Status Change Event to the SOE queue.
Range: checkmark/no checkmark
Default value: no checkmark

Table 3-6 Binary inputs settings

3.4 Analog Outputs Settings

3.4.1 Analog Outputs Settings
Each instance of the slave protocol component may contain several analog output points (also
called “Setpoint Controls” or “Setpoints”) to be controlled by a master station. Analog outputs
settings tell the component how to map analog outputs from the RTDX to protocol addresses.

6● SES-92 SLAVE PROTOCOL REFERENCE MANUAL

 The following table shows the analog outputs settings that are specific to the SES-92 slave
protocol.

Setting Description
Identifier The analog output identifier assigned to the point. This number
uniquely identifies a point within all analog outputs.
Range: 0 to 255
Default value: 0
Format The format of the analog output value. This indicates the slave how
to interpret the “Setpoint Value” field of the SBO Setpoint Select
and DO Setpoint Execute requests. If “Signed” is selected, the
setpoint value ranges from -2048 to 2047. If “Unsigned” is selected,
the value ranges from 0 to 4095.
Allowed values: Signed
Unsigned
Default value: Signed

Table 3-7 Analog outputs settings

3.5 Binary Outputs Settings

3.5.1 Binary Outputs Settings
Each instance of the slave protocol component may contain several binary output points (also
called “Digital Output Points”) to be controlled by a master station. Binary outputs settings tell
the component how to map binary outputs from the RTDX to protocol addresses. The following
table shows the binary output settings that are specific to the SES-92 slave protocol.

Setting Description
Identifier The binary output identifier assigned to the point. This number
uniquely identifies a point within all binary outputs.
Range: 0 to 255
Default value: 0

Table 3-8 Binary outputs settings

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ●7

4. Implementation Details
4.1 Diagnostic Flags
The master station can retrieve the internal state of the slave protocol component via the Dump
Diagnostic Data request. However, the slave protocol component only supports the following
Diagnostic Flags:
 RST (Reset)
 LOP (Loss of Operating Parameters)
 LCD (Loss of Configuration Data)
 Other flags will always be reported as 0 (cleared state).
 The slave protocol component will clear the LCD flag upon receiving the RTU Configuration
Complete request.
 The slave protocol component will clear the LOP flag upon receiving the Reset RTU request
with a valid Operating Parameter Block.

4.2 Time Synchronization

Since the Synchronize Time request contains only the time and the day of the year and not the
year itself, the slave protocol component will try to adjust the current year based on the current
system date. To do this adjustment, the protocol component will calculate the absolute difference
between the current system date and the new Julian Day set on the previous year, on the
current year and on the following year. The smaller difference will determine the new system
year that will be set with the Julian Day. For example, if the current system date is November
20th, 2007, a Synchronize Time request with a Day of Year field of 1 will set the current system
date to January 1st, 2008.

4.3 Time Format

Every request that sends or receives time values will use the Coordinated Universal Time (UTC)
standard (that is, without any time zone offset). For example, a Synchronize Time or Dump
Digital Status Change Data request containing Day of Year 1, 13:14:00, will represent a time
based on the UTC time standard that is equivalent to January 1st, 8:14:00 in the Eastern
Standard Time (EST) time zone.

4.4 Digital Status Change

Digital Status Change events are generated on a binary input state change, no matter what the
point quality is. In addition, the timestamp of a Digital Status Change event will be the timestamp
associated with the binary input state change that generated the event.
The quantity of Digital Status Change events that can be retained before the master status
retrieve them is limited by the “SOE Queue Length” parameter (see “General Settings” in this
document). If the queue is full and another Digital Status Change occurs, the oldest change will
be removed from the queue to make room for the new change. Note however that this ‘oldest’
change is based on the order the change were added to the queue and not on the timestamp of
the change itself.

4.5 Reset RTU Actions

The Reset RTU request does not restart the entire SMP Gateway. Instead, it reset the state of the
slave protocol instance. On reception of a Reset RTU request, the slave will do the following
steps:
 Reset the communication link (including disconnection on a connection-oriented
communication link like TCP/IP)

8● SES-92 SLAVE PROTOCOL REFERENCE MANUAL

  Copy the Operating Parameter Block data in the Reset RTU request to the V-OPB.
 Set the LCD Diagnostic Flag to indicate loss of configuration data.
 Place all analog inputs in group 0 and set all the analog deadbands to 255 (no report).
 Clear all exception and Digital Status Change events.
 Wait for a Dump Diagnostic or a Synchronize Protocol Version request and reply to all
other requests with a Null Message.

4.6 Accumulator and Solid State Meter Inputs

The behavior of accumulator and solid state meter inputs is simulated locally by the
SMP Gateway and is not forwarded to the end devices. Upon reception of a “Freeze Accumulator
Data” request from the master, the SES-92 slave component takes a snapshot of the current
running values of the analog inputs related to the accumulator and solid state meter inputs.
This behavior is transparent to the master. When a freeze occurs, the ACC flag is set according to
the standard and is cleared only when all existing accumulator and solid state meter input points
have been read by the master.

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ●9

5. Troubleshooting
The following table enumerates solutions to common problems experienced with the SES-92
slave protocol component:

Problem Solution
The SMP Gateway is This problem can be due to one of the following:
not communicating  There is a problem in the SMP Gateway settings, which results
with the master in a failed startup.
station.
 RTU addressing problem: The configured RTU Group and
RTU Identifier general settings do not match the ones
configured in the master station.
 Cable problems: Make sure you are using the right cables and
that they are working properly. If possible, swap cables with
one that is known to work.
 Serial interface configuration problem: Serial interfaces on an
SMP Gateway can be configured in RS-232, RS-422 and
RS­485. The interface configuration may not be compatible
with the interface configuration of your IED.
 DTE-DCE problems: SMP Gateway serial ports are configured in
DTE mode. Use a straight cable to connect to a modem or to
most IED maintenance ports. You should, however, use a NULL
modem when connecting directly to a PC. Use a breakout box
to diagnose the problem.
 Baud rate, parity, data bit and stop bit problems: These
settings must be configured identically at both ends of the
configuration (serial links only). For the SMP Gateway, this
information is available via the connection statistics or via
the configuration file itself.

The link to my device This problem could be due to a number of things:

keeps resetting.  Bad link quality: The link quality is bad and too many
exchanges are corrupted as they travel from one end of the
connection to the other. Consult the link connection and scan
statistics to determine whether the link’s checksum error ratio
is acceptable. Take corrective action if necessary.
 The link times out on a regular basis: You should consult the
link statistics to determine if that is what is happening. This
may be due to bad link quality, if it is accompanied by
checksum errors. However, it may also be caused by defective
IED behavior or incorrect configuration of the Inactivity
Timeout setting. Increase the duration allowed for link
timeouts if you have doubts.

10 ● SES-92 SLAVE PROTOCOL REFERENCE MANUAL

 Problem Solution
 The link systematically resets following a specific exchange:
Consult the link traces to verify if this is happening. This
behavior is usually due to protocol incompatibility. If you have
some knowledge of the application-level protocol, you should
be able to identify what it is that the client side is asking that
the other side cannot handle or, alternatively, what it is that
the other side is responding that the client side cannot handle.
In some cases, you may be able to modify your configuration
to avoid the problem-causing exchange.

Table 5-1 Troubleshooting

SES-92 SLAVE PROTOCOL REFERENCE MANUAL ● 11