0% found this document useful (0 votes)
443 views19 pages

VALMET (TEJAS Series V) Slave Protocol

Uploaded by

JOSE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
443 views19 pages

VALMET (TEJAS Series V) Slave Protocol

Uploaded by

JOSE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

Reference Manual

VALMET (TEJAS Series V)


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

Cooper Power Systems


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

Technical Support: [email protected]

S1120-29-1, version 6
Contents
1. Introduction ............................................................................................................................. 1
2. Features.................................................................................................................................... 2
2.1 Communications....................................................................................................................... 2
2.2 Interoperability ........................................................................................................................ 2
2.2.1 Implementation Restrictions and Warnings .................................................................. 2
2.2.2 Supported Opcodes.................................................................................................... 2
3. Configuration Settings ............................................................................................................. 4
3.1 General Settings....................................................................................................................... 4
3.2 Analog Input Settings ............................................................................................................... 5
3.3 Binary Input Settings ................................................................................................................ 6
3.4 Counter Input Settings ............................................................................................................. 7
3.5 Analog Output Settings ............................................................................................................. 8
3.6 Binary Output Settings ............................................................................................................. 9
4. Implementation Details ......................................................................................................... 11
4.1 Startup Sequence ................................................................................................................... 11
4.2 Scan Cycle ............................................................................................................................. 11
4.3 Special Features ..................................................................................................................... 11
4.3.1 Generated Binary Inputs .......................................................................................... 11
5. Troubleshooting ..................................................................................................................... 12

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ●i


Tables
Table 2-1 Communication Features .................................................................................. 2
Table 2-2 Supported Opcodes ........................................................................................... 3
Table 3-1 General Settings ............................................................................................... 5
Table 3-2 Analog Input Settings ....................................................................................... 6
Table 3-3 Binary Input Settings ........................................................................................ 7
Table 3-4 Counter Input Settings ..................................................................................... 7
Table 3-5 Analog Output Settings ..................................................................................... 9
Table 3-6 Binary Output Settings ................................................................................... 10
Table 4-1 Generated Binary Inputs ................................................................................ 11
Table 5-1 Troubleshooting .............................................................................................. 13

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ● iii


1. Introduction
This manual provides the information required to install and set up a VALMET TEJAS - Series V
slave protocol component in an SMP Gateway.
The VALMET TEJAS - Series V slave protocol is used to report information on I/O points of
different RTUs to a TEJAS master station. This is done on standard asynchronous serial links in
point-to-point configurations
You must be familiar with the SMP Gateway environment and the TEJAS protocol specification
before proceeding with this document. You can get this information by reading the following
documents:
 Series V Communication Protocol, B8300-AAA-00005, VALMET Automation Inc., Jan. 1992.
 Energy Control System Remote Terminal Unit Communication Protocol, ECS-00004-02,
Oglethorpe Power Corporation, December 1992.

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ●1


2. Features
This chapter enumerates the features provided by the VALMET TEJAS - Series V slave protocol
component.

2.1 Communications
The following communications features are available when interconnecting devices to the
SMP Gateway:

Feature Comment
Serial Port This protocol component supports the RS-232, RS-422 and RS-485
interfaces at bit rates up to 115200 bps.
TCP/IP This protocol component supports TCP/IP communications.
Multidrop This protocol component can be used over a multidrop link, if its
device address is different than the one of other devices sharing the
link.
Serial Radios The VALMET TEJAS - Series V protocol component supports
asynchronous communications using serial radios.

Table 2-1 Communication Features

2.2 Interoperability
This section, in conjunction with chapter 3, provides complete information on how to
communicate with the VALMET TEJAS - Series V slave via the TEJAS protocol.
2.2.1 Implementation Restrictions and Warnings
The following protocol and/or implementation restrictions must be understood:
 The data reported by the VALMET TEJAS - Series V slave protocol is updated internally as
fast as it is injected in the Real-Time Data Exchange component by the various master
components. Obviously, when a master station is exchanging information with a VALMET
TEJAS - Series V 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 following RTU types are supported:
 Micro/1
 Micro/1C
 Micro/1E
 Micro/1L
 Camdac
 Landac
 Wesdac D20
2.2.2 Supported Opcodes
The following request codes are supported by the VALMET TEJAS - Series V slave protocol
component:

2● VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL


Opcode Name
01 Analog Scan
02 Accumulator Scan
03 Status Scan
04 Control Select
05 Control Execute
06 Control Direct Execute
07 Accumulator Freeze
10 Status Change (COS) Dump
11 RTU Status Clear
12 RTU Configuration
13 Analog Deadband Download
14 Analog Change Count
15 Analog Change (ABE) Dump
16-19 Setpoint Select
20-23 Setpoint Execute
24-27 Setpoint Direct Execute
28 Setpoint Scan
36 Sangamo BCD counter

Table 2-2 Supported Opcodes

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ●3


3. Configuration Settings
This chapter enumerates the configuration settings you have to specify for each instance of the
VALMET TEJAS - Series V slave protocol. The SMP Config software program is generally used to
define these settings.

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 for the VALMET
TEJAS - Series V slave protocol.

Setting Description

Device Prefix A string used as a prefix for all the I/O point names supported by a
particular device. This prefix ensures that every I/O point name in
the system is unique. Each device monitored by the system must
have its own, unique device prefix.
A device prefix is not required for a VALMET TEJAS - Series V slave,
but defining one adds two system (logical) data points to the
component: ___LinkActive and ___LinkAvailable (see section 4.3.1
for details).
Range: 1 to 19 ASCII characters
Default value: none
RTU Address The RTU address that identifies the slave component in requests
and responses.
The VALMET TEJAS - Series V slave supports and processes
requests with a ‘0’ address (global address), but does not respond
to these requests.
Range: Wesdac D20: 1 to 32,767
Others: 1 to 127
Default value: 1
RTU Type The type of RTU emulated by the slave component. This setting is
used to determine the appropriate interpretation of the detailed
RTU status flags. The Wesdac D20 RTU type also specifies 2-byte
address support. You choose the type in a drop-down list.
Allowed values: Micro 1
Micro 1C
Micro 1E
Micro 1L
LANDAC
CAMDAC
WESDAC D20
Default value: LANDAC

4● VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL


Setting Description
Inactivity Timeout The number of seconds that the component will wait after the last
valid request is received, before resetting the communications link.
If set to 0, the inactivity timeout is disabled.
If a device prefix has been defined, the link activity state is
published using the ___LinkActive system (logical) data point (see
section 4.3.1 for details).
Range: 0 to 2,147,483,647 seconds
Default value: 0
Unavailability Timeout The number of seconds that the slave component will wait after the
last valid data request is received or the last connection request
from the master station, before declaring the link unavailable.
If set to 0, the unavailability timeout is disabled.
If a device prefix has been defined, the link availability state is
published using the ___LinkAvailaible system (logical) data point
(see section 4.3.1 for details).
Range: 0 to 1,000,000 seconds
Default value: 60 seconds
Control Enabled A checkmark indicates that the slave can receive control and
setpoint command requests.
Range: checkmark / no checkmark
Default value: checkmark
CRC A checkmark indicates that the CRC-16 algorithm is used to
calculate the checksum on received and transmitted data. If there is
no checkmark, the LRC technique is used.
Range: checkmark / no checkmark
Default value: checkmark
Max Connection Delay Maximum number of seconds to wait before accepting a connection
from a TEJAS master station. A value of 0 means that there will be
no delay.
Range: 0 to 86,400 seconds
Default value: 0

Table 3-1 General Settings

3.2 Analog Input 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
for the VALMET TEJAS - Series V slave protocol.

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ●5


Setting Description
Name The name of the point for which you want to retrieve information
from the RTDX.
Range: 1 to 39 ASCII characters
Default value: none
Address The analog address assigned to the point.
Range: 0 to 255
Default value: 0
Disabled When this setting is selected, the point is ignored by the protocol
component.
Range: checkmark / no checkmark
Default value: no checkmark
Unipolar Defines how the RTDX analog value will be encoded as a VALMET
TEJAS analog value. A checkmark indicates a 12-bit absolute
positive value (unipolar). If there is no checkmark, the value is
handled as a 12-bit 2’s complement value (bipolar).
Range: checkmark / no checkmark
Default value: no checkmark
Scale The processing performed to convert the analog information
obtained from the RTDX to the VALMET TEJAS 12-bit format is:
Raw value = (floating-point value - offset) / scale
If the Unipolar setting is selected, the resulting value is converted
to a 12-bit unsigned value.
Range: –3.4E38 to 3.4E38, not 0.0
Default value: 1.0
Offset The processing performed to convert the analog information
obtained from the RTDX to the VALMET TEJAS 12-bit format is:
Raw value = (floating-point value - offset) / scale.
If the Unipolar setting is selected, the resulting value is converted
to a 12-bit unsigned value.
Range: –3.4E38 to 3.4E38
Default value: 0.0
RTU Deadband Specifies the initial analog-by-exception deadband for this analog
input. Only changes greater than the deadband will be reported to
the master station. A value of 0 implies that all transitions, no
matter how small, will be reported. This value may be changed by
the master by a Download Analog Deadband request.
Range: 0 to 255
Default value: 0

Table 3-2 Analog Input Settings

3.3 Binary Input Settings


Each instance of the slave protocol component may contain several binary input points to be
reported to the master station. Binary input settings tell the component how to map binary inputs

6● VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL


from the RTDX to protocol addresses. The following table shows the binary input settings for the
VALMET TEJAS - Series V slave protocol.

Setting Description
Name The name of the point for which you want to retrieve information
from the RTDX.
Range: 1 to 39 ASCII characters
Default value: none
Address The status point address assigned to the point.
Range: 0 to 255
Default value: 0
Disabled When this setting is selected, the point is ignored by the protocol
component.
Range: checkmark / no checkmark
Default value: no checkmark
Inverted Pol. A checkmark indicates that the state received from the RTDX for
this point should be inverted before being reported to the master
station.
Range: checkmark / no checkmark
Default value: no checkmark

Table 3-3 Binary Input Settings

3.4 Counter Input Settings


Each instance of the slave protocol component may contain several counter input points to be
reported to the master station. Counter input settings tell the component how to map data
retrieved from the RTDX into accumulator addresses. The following table shows the counter input
settings for the VALMET TEJAS - Series V slave protocol.

Setting Description
Name The name of the point for which you want to retrieve information from the
RTDX.
Range: 1 to 39 ASCII characters
Default value: none
Address The accumulator address assigned to the point.
In the range specified below for Wesdac D20, 200 represents the first Sangamo
counter.
Range: Wesdac D20: 0 to 199 (counter input)
200 to 255 (Sangamo BCD counter)
Others: 0 to 255
Default value: 0
Disabled When this setting is selected, the point is ignored by the protocol component.
Range: checkmark / no checkmark
Default value: no checkmark

Table 3-4 Counter Input Settings

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ●7


3.5 Analog Output Settings
Each instance of the slave protocol component may contain several analog output points to be
reported to or controlled by a master station. Analog output settings tell the component how to
map analog outputs from the RTDX to protocol addresses. The following table shows the analog
output settings for the VALMET TEJAS - Series V slave protocol.

Setting Description
Name The name of the point for which you want to retrieve information
from the RTDX.
Range: 1 to 39 ASCII characters
Default value: none
Address The setpoint address assigned to the point.
Range: 0 to 63
Default value: 0
Disabled When this setting is selected, the point is ignored by the protocol
component.
Range: checkmark / no checkmark
Default value: no checkmark
Unipolar Defines how an RTDX analog value will be encoded as a TEJAS
setpoint value. A checkmark indicates a 12-bit unipolar value
(absolute positive value). Otherwise, the value will be treated as a
12-bit 2’s complement value.
Range: checkmark / no checkmark
Default value: no checkmark
Simulated Control Indicates for which command type sent to the master protocol
Confirmation component that owns the point, simulated confirmations are
required.
Simulated confirmation differs from real confirmation in that it is
sent by the master protocol component before the operation is
performed, and confirmed by the remote device. A real
confirmation is sent back only after the specified operation is
performed and confirmed by the remote device.
DIRECT EXECUTE commands are processed as EXECUTE
commands.
Allowed values: Never
SELECT only
EXECUTE only
SELECT and EXECUTE
Default value: SELECT and EXECUTE
Scale The processing performed to convert the analog information
obtained from the RTDX to the VALMET TEJAS 12-bit format is:
Raw value = (floating-point value - offset) / scale
If the Unipolar setting is selected, the resulting value is converted
to a 12-bit unsigned value.
Range: –3.4E38 to 3.4E38, not 0.0
Default value: 1.0

8● VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL


Setting Description
Offset The processing performed to convert the analog information
obtained from the RTDX to the VALMET TEJAS 12-bit format is:
Raw value = (floating-point value - offset) / scale
If the Unipolar setting is selected, the resulting value is converted
to a 12-bit unsigned value.
Range: –3.4E38 to 3.4E38
Default value: 0.0

Table 3-5 Analog Output Settings

3.6 Binary Output Settings


Each instance of the slave protocol component may contain several binary output points to be
reported to or controlled by a master station. Binary output settings tell the component how to
map binary outputs from the RTDX to protocol addresses. The following table shows the binary
output settings for the VALMET TEJAS - Series V slave protocol.

Setting Description
Name The name of the point for which you want to retrieve information
from the RTDX.
Range: 1 to 39 ASCII characters
Default value: none
Address The control point address assigned to the point.
Range: 0 to 255
Default value: 0
Disabled When this setting is selected, the point is ignored by the protocol
component.
Range: checkmark / no checkmark
Default value: no checkmark
Simulated Control Indicates for which command type sent to the master protocol
Confirmation component that owns the point, simulated confirmations are
required.
Simulated confirmation differs from real confirmation in that it is
sent by the master protocol component before the operation is
performed, and confirmed by the remote device. A real
confirmation is sent back only after the specified operation is
performed and confirmed by the remote device.
DIRECT EXECUTE commands are processed as EXECUTE
commands.
Allowed values: Never
SELECT only
EXECUTE only
SELECT and EXECUTE
Default value: SELECT and EXECUTE

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ●9


Setting Description
Points Pairing Indicates how OPEN/CLOSE operations using two PULSE points are
supported for the RTDX point, when such operations are supported.
Another point should be used to define the second point of the pair,
which will handle the complementary operation.
The two points of an open/close pair are linked together using the
Open/Close Pair setting, so they don’t have to be consecutive.
However, they must have the same point name.
Allowed values: None
Open
Close
Default value: None
Open/Close Pair Indicates the number of the open/close pair, if supported. This
setting is used to combine two pulse points to allow open/close
operations on a single RTDX point.
Only two points can use the same OPEN/CLOSE pair number.
Allowed values: 0 not assigned
1 to 65,535 pair number
Default value: 0

Table 3-6 Binary Output Settings

10 ● VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL


4. Implementation Details
4.1 Startup Sequence
The protocol component goes through the following steps on startup:
 Parses the configuration file.
 Initializes the various logs, traces and statistics.
 Subscribes to all the configured I/O points, and reads the current value and state of all the
I/O points.
 Waits for a connection request from the VALMET TEJAS master station.
 Starts the scan cycle.

4.2 Scan Cycle

Link initialization occurs under the following circumstances:


 The SMP Gateway is being restarted.
 The communications link is being reset, due to errors of any type.

Once the link has been initialized, and as long as it remains active, a regular scanning cycle is
performed on a continuous basis. Note that the link is not considered active until a valid
association is made.

The regular scanning cycle is as follows:


 Wait for an appropriate request from the link.
 Validate the request.
 Process the request.
 Complete the response and send it.
 Decide whether the reception status is OK and/or the link needs to be reset.

4.3 Special Features


4.3.1 Generated Binary Inputs
If a device prefix is defined in its general settings, the VALMET TEJAS - Series V slave component
produces two logical binary inputs:

Name Description

___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.

Table 4-1 Generated Binary Inputs

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ● 11


5. Troubleshooting
The following table enumerates solutions to common problems experienced with the VALMET
TEJAS - Series V slave protocol component:

Problem Solution
The SMP Gateway is not This problem can be due to one of the following:
communicating with the  There is a problem in the SMP Gateway settings, which
master station. results in a failed startup.
 RTU addressing problem: The configured RTU Address
general setting does not match the one configured in the
master station.
 Cable problems: Make sure you are using the right cables
and that they are working properly. If possible, replace the
cable you think is defective with one that is known to work.
 Serial interface configuration problem: Serial interfaces on
an SMP Gateway can be configured in RS232, RS422 and
RS485. The interface configuration may not be compatible
with the interface configuration of your IED.
 DTE-DCE problems: SMP Gateway ports are configured in
DTE mode. You should therefore 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: The baud
rate, parity, data bit and stop bit 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.

12 ● VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL


Problem Solution
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’s 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.
 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

VALMET (TEJAS SERIES V) SLAVE PROTOCOL REFERENCE MANUAL ● 13

You might also like