Вы находитесь на странице: 1из 129

DATE : 19/07/2013

DOC. MSE10015 REV. 6.5.2

TDMS Test Data Management Software


USER MANUAL
DOC. MSE10015 REV. 6.5.2 Page 2/129

REVISION DESCRIPTION OF VISA


CHANGES
N PAG. DATE
1 All 30/01/2006 Issued release 1.0.0 Morandi

2 30/08/2007 Updated to version 5.0.0 Morandi


Introduction of Test Plans
5.0. 20/12/2007 Updated to version 5.0.3. Rossoni
3 Added Software Installation
paragraph
5.1. All 05/09/2008 Update to version 5.1.0. Morandi
0 Added Battery benches
software. Report selection
from Preferences
6.0 All 7/12/2009 Updated to revision 6.0 Lodi

6.2. 45,50 02/08/2010 Updated to revision 6.2.3 Morandi


3
6.2. All 10/11/2010 Updated to revision 6.2.7 Lodi
7
6.3. 109- 22/07/2011 Updated to revision 6.3.8 Lodi
8 119
6.5. 9 19/7/2013 Updated to revision 6.5.2 Lodi
2
DOC. MSE10015 REV. 6.5.2 Page 3/129

PREFACE ................................................................................... 7
1. TDMS OVERVIEW ...................................................... 8
1.1 HANDLING THE EXECUTION OF TEST PROGRAMS ................ 10
1.2 ORGANIZE AND PRINT TEST RESULTS .................................. 13
1.2.1 Create a Network Structure ................................. 14
1.2.2 The Toolbar ................................................................ 19
1.2.3 The Tables: Test Results, Test Plans,
Recordings .............................................................................. 21
1.2.4 Tables Menus ............................................................. 23
1.2.5 Menu of the Network Structure .......................... 24
2. PROGRAM MENUS ..................................................... 27
2.1 MENU FILE ....................................................................... 27
2.1.1 Open test results ................................................. 28
2.1.2 Import test results .............................................. 28
2.1.2.1 Drag & Drop ................................................................................ 29
2.1.2.2 Automatic Import list ............................................................... 32
2.1.3 Export database................................................... 32
2.1.4 Merge database ................................................... 33
2.1.5 Save ......................................................................... 35
2.1.6 Print network tree ............................................... 36
2.1.7 Print test report ................................................... 36
2.1.8 Exit ............................................................................ 37
2.2 MENU EDIT....................................................................... 37
2.3 MENU TEST ...................................................................... 40
2.4 MENU COMTRADE ............................................................ 42
2.5 MENU TEST PLAN ............................................................. 43
2.6 MENU OPTIONS ............................................................... 44
2.5.1 Preferences ............................................................ 44
2.5.2 Compact databases ............................................ 49
2.5.3 Languages .............................................................. 50
2.6 SECURITY ......................................................................... 50
2.6.1 Login......................................................................... 50
2.6.2 Privileges ................................................................ 51
DOC. MSE10015 REV. 6.5.2 Page 4/129

2.7 MENU ? ............................................................................. 54


3. PRINT REPORT............................................................ 55
3.1 SEARCH CRITERIA ........................................................... 59
3.1.1 Common Results ................................................. 59
3.1.1.1 Session dates .............................................................................. 60
3.1.1.2 Selections ..................................................................................... 60
3.1.1.3 Include report ............................................................................. 61
3.1.2 Test Plans ............................................................... 61
3.2 PRINTING OPTIONS ......................................................... 62
3.2.1 Relays ...................................................................... 62
3.2.1.1 Manual tests ...................................................................................... 63
3.2.1.2 Automatic Tests ............................................................................... 66
3.2.2 T1000/T3000 ........................................................ 67
3.2.3 Transformer........................................................... 68
3.2.4 Breaker.................................................................... 68
3.2.5 Comtrade ................................................................ 69
3.2.6 Energy meter ........................................................ 70
3.2.7 Transducers ........................................................... 70
3.2.8 PQ Meters ............................................................... 71
3.2.9 Line differential .................................................... 71
3.2.10 BTS ........................................................................ 72
4 TEST PLANS FOR MULTIFUNCTION RELAYS ... 73
4.1 WHAT ARE TEST PLANS? ...................................................... 73
4.2 EDITOR OF TEST PLANS........................................................ 75
4.2.1 Menu and Toolbar .................................................... 76
4.2.1.1 Menu Test Plan ................................................................................. 77
4.2.1.2 Menu Type of Protections ............................................................. 81
4.2.2 Test Plan Settings .................................................... 83
4.2.3 Modules ........................................................................ 84
4.2.4 Adding a Macro to the Test Plan ........................ 86
4.2.5 Test Plan list of Macros .......................................... 88
4.2.6 Saving and linking the Test Plan ....................... 89
4.2.7 Description of Generic Test Macros .................. 92
4.3 EXECUTION OF TEST PLANS ................................................. 103
DOC. MSE10015 REV. 6.5.2 Page 5/129

5. SYSTEM REQUIREMENTS ...................................... 110


5.1 HARDWARE REQUIREMENTS.................................................. 110
5.2 SOFTWARE REQUIREMENTS .................................................. 110
6. SOFTWARE INSTALLATION ................................. 111
6.1 INTRODUCTION ...................................................................... 111
6.2 USB SOFTWARE DRIVER INSTALLATION FOR DRTS OR
CBA1000 ..................................................................................... 121
6.3 TROUBLESHOOTING THE USB SOFTWARE DRIVER
INSTALLATION................................................................................ 123

7. WINDOWS VISTA/7 ................................................ 128


DOC. MSE10015 REV. 6.5.2 Page 6/129

Disclaimer
Every effort has been made to make this material complete, accurate, and up-to-date. In
addition, changes are periodically added to the information herein; these changes will be
incorporated into new editions of the publication. ISA S.R.L reserves the right to make
improvements and/or changes in the product(s) and/or the program(s) described in this
document without notice, and shall not be responsible for any damages, including but not
limited to consequential damages, caused by reliance on the material presented,
including but not limited to typographical errors.

Copies, reprints or other reproductions of the content or of parts of this publication shall
only be permitted with our prior written consent.
All trademarks are the property of their respective holders.

Copyright 2013 ISA S.R.L. Italy All rights reserved.


DOC. MSE10015 REV. 6.5.2 Page 7/129

Preface
We at ISA have been producing over the decades high quality
instruments for the testing of a wide range of protections for
electrical networks. We have customers worldwide that use daily
our instruments and carry out reliability tests, maintenance
checks, final test on production lines and so on by means of the
software that we provide with the instruments. Especially since
the inception of automatic test equipment, the software has
become increasingly important, making a lot easier to end-users
to set and repeat precisely series of tests. This has created an
enormous amount of test data.
Our customers also differ in needs and wants, and it could be
difficult to design and release an instrument or a software that
meets the demands of a variety of users. Test managers have
different needs and requests than field-operators, but most of our
customers realize the need of efficiently handle and organize the
test results.
We have therefore concentrated in designing a software that will
help organizing these results, both geographically and historically,
will allow test managers to collect results from various test teams
and to print professional reports.
This is the purpose of TDMS, Test & Data Management Software.
Please read this manual to acquaint with the features of this
powerful new software.
DOC. MSE10015 REV. 6.5.2 Page 8/129

1. TDMS OVERVIEW
TDMS stands for Test & Data Management Software. It is a
software designed to manage the execution of ISA test programs
and the results of tests performed.
These are the three main features of TDMS:
handle the execution of Test programs
organize the test results
print the test results
The software is password protected, with the possibility of
creating an unlimited number of users that fall into one out of
three built-in activity groups: administration, program editing and
normal usage. These features will be discussed in detail in the
paragraph Security.
In a typical session, a user will start TDMS to choose which ISA
software to launch for the testing of the particular device, be it a
relay of various ANSI IEC standards, an Energy meter,
Transducer, Power quality meter, Transformer and so on.
After executing the program and performing the necessary tests,
the user will store the results data in a file and return to TDMS. A
Test manager can build the network tree under his control,
setting out the device characteristics and geographical position in
the network and import the results. This will in time create a list
of historical test results for the device. It is possible to print out
the results, or to select more test results and print them in a
single report to compare previous results on the same device or
similar tests on different devices with same characteristics. The
report can also be exported in a Adobe Acrobat, Microsoft word,
or Microsoft excel format. It is also possible to select a set of
results previously performed and to repeat them directly from
TDMS: the appropriate software is run and loaded with the
chosen set of test results.

In the revision 6.2.7 we have improved graphically the


presentation page for test programs selection. Most important,
the automatic relay test set manual control module has been
replaced by a completely new module, much more performing
and friendly.

In the revision 6.3.8 we have added the possibility of operating


with the 64 bit version of WINDOWS.
DOC. MSE10015 REV. 6.5.2 Page 9/129

In the revision 6.5.2 we have added:


The Advanced Relay Test plan editor;
The control of the IEC61850-9 interface;
The control of the STS 5000 series of test sets.
DOC. MSE10015 REV. 6.5.2 Page 10/129

1.1 Handling the execution of Test programs


The first TDMS software feature is the capability to launch all the
software designed and maintained by ISA.

When the program is started, the following message appears:

Enter the password if you have defined it; else, press OK or RET
on the keyboard.

The use of this part of TDMS is simple: click on the program you
want to run, and it will be started.

Upon moving the mouse over the programs, a description of the


software appears by its side. For instance, moving on the Manual
program, the following is shown:
DOC. MSE10015 REV. 6.5.2 Page 11/129

Besides, the program name and version appear in the status bar
at the bottom of the page; in our instance:

Click on the menu item to launch the relative software. The only
exceptions to this are:
. Distance relay library. As you press it, the list of distance
relay manufacturers opens up. After you select a manufacturer,
you access the list of available distance relays of that
manufacturer.

For instance, the ABB submenu contains the links to the Special
Distance programs associated with the relays produced by ABB.
The same happens for all other manufacturers.
DOC. MSE10015 REV. 6.5.2 Page 12/129

. Differential 87. Pressing it, the following selection is


accessible.

. Relay test plan editor. Pressing it, the following selection is


accessible.

These programs allow to Edit, or Run, a program, which uses the


other test programs, in order to be able to test a multi-protection
relay.

. Advanced Relay Test Editor. Pressing it, the following


selection is accessible.

Even if the icons are the same as above, these programs allow to
Edit or Run a program which can perform any type of test on any
type of relay.

In the associated library are available some programs, which are


not in the test programs list, and which complete it. They are
found in the directory XTEST \ XTEST2000 \ PRG \ MV; they are:
REWTEST: it allows testing reverse power relays.
DOC. MSE10015 REV. 6.5.2 Page 13/129

DF_TEST: it allows testing frequency rate of change


relays.
V_TEST: it allows testing voltage relays.
F_TEST: it allows testing frequency relays.
LOF_TEST: it allows testing loss of field relays.

The manuals explaining the programs and how to operate them


are included in the collection of software manuals.

. Utilities. Pressing it, the following selection is accessible.

1.2 Organize and print test results


The features available to organize and print test results are
enclosed in the Network tree tab.
DOC. MSE10015 REV. 6.5.2 Page 14/129

Upon executing TDMS for the first time, the network tree is
empty, it must be created.

1.2.1 CREATE A NETWORK STRUCTURE


Only Administrator users can add, modify or delete parts from the
Network tree.
A network tree is a structured definition of the electrical network
managed by the user. A typical network comprises many
substations, each one handling a few lines.
To add a new network to the Network tree, press the Create new
Network icon from the icons list. It is also possible to select the
menu Edit New Network. The window that appears allows the
user to choose a name for the network and optionally a
description.

Press the Ok button to add the network node in the Network tree.

Select the network node Network 1. The Create new Substation


Icon in the icons list above the Network tree is enabled. Press the
button and fill in the similar information for the substation. It is
also possible to select the menu Edit New Substation.
DOC. MSE10015 REV. 6.5.2 Page 15/129

Press the Ok button to add the substation node to the node


Network 1 in the Network tree.

Select the Substation node Substation 1. The Create new Line


icon in the icons list above the Network tree is enabled. Press the
button and fill in the similar information for the line. It is also
possible to select the menu Edit New Line.
DOC. MSE10015 REV. 6.5.2 Page 16/129

There is a further option for the line: the list of devices that can
be displayed in the tree. Upon creating a line node, the sub-tree
of devices shown in the Devices tree is added to the node
automatically. Select only the nodes that you want to appear in
the network structure. For instance, if you do not control Meters,
Breakers and DFRs, uncheck the relative nodes and they will not
be displayed in the network tree.
Press the Ok button to add the Line node to the node Network 1-
Substation 1 in the Network tree.
DOC. MSE10015 REV. 6.5.2 Page 17/129

The structure here identified is a visual definition of how the


network is designed. After adding a line node, it is possible to add
a wide variety of devices, grouped by type.
Select a group type to add the relative device to the network. For
instance, select the Relays node, and press the Create new Relay
icon in the icons list. It is also possible to select the menu Edit
New Relay.
DOC. MSE10015 REV. 6.5.2 Page 18/129

In the window that appears, it is possible to set the Name of the


relay: this is the name that will be displayed on the tree when the
relay is added. It is possible to add an optional Description. Care
should be taken to fill in properly the Manufacturer, Model and
especially Serial Number fields. Compiling properly these fields
ease many statistical and practical procedures that the user will
appreciate while using TDMS. The Serial Number field is displayed
with the Name field in the network tree to easily identify the
device. Press the Ok button to add the relay to the node:
Network 1-Substation 1-Line 1- Relays
DOC. MSE10015 REV. 6.5.2 Page 19/129

As it can be seen, a new Relay node has been added. Select the
node to see the list of test results associated with this relay.

Since no test results have been imported at this time and no Test
Plan has been created yet, the grids Test results, Test Plans and
Recordings are empty.

1.2.2 THE TOOLBAR


At the top of the Network Tree page, there is a toolbar that
groups all the buttons for the creation of the various headers.

Creating a node by pressing the relative button of the toolbar is


the equivalent of choosing the relative menu item in the Edit

New menu. The toolbar also contains a special button for the
search of nodes in the Network Tree. By pressing this button the
following window is opened.
DOC. MSE10015 REV. 6.5.2 Page 20/129

By means of this window it is possible to search a node in the


structure by using key words of the Header Name, the Serial
Number, the Manufacturer or the Model. It is also possible to
decide whether the search should be Case sensitive and to
include the criteria in a AND clause or in OR clause with the top
menu.

Jolly characters can also be used. There are three jolly


characters: #, ?, *. Their features are:
. # replaces a single digit;
. ? replaces one digit or one character;
. * replaces a series of digits or characters.

For instance to search for all the nodes that have model type
P441 or P442, enter in the Model box the query P44#: after
pressing the Search button, the list will be filled with the nodes
that corresponds to the search criteria. You can use also P44?. If
the search id for P441AB or P441CD, use P441*.
DOC. MSE10015 REV. 6.5.2 Page 21/129

Double-click on the row to highlight the node in the network tree.

1.2.3 THE TABLES: TEST RESULTS, TEST PLANS, RECORDINGS


The Test results table represents a list of the test results that
have been carried out on the device with a specific ISA Software.
By Result we intend a group of tests that have been carried out
together on the device, not the single breakdown of the tests
performed on the device. This makes it possible to create an
historical list of test results performed. It eases the maintenance
of devices since it is possible to find out the time passed from the
previous test on the device very quickly.
Suppose that test results have been imported for the Relay1
(please see chapter 2, paragraph 2.1.2 for a detailed procedure
on how to import test results). When selecting the node from the
network tree, the Test results grid is filled with the relative test
results.

Test results are ordered by number depending on when they


have been imported. The ID column show the identifying number
that the TDMS software has given to the test result, a DATE
column is provided to let the user quickly see when the test result
DOC. MSE10015 REV. 6.5.2 Page 22/129

has been performed (not when it has been imported). The column
ORIGINAL FILENAME, although not used by TDMS, is a useful
indication since sometimes users give specific names to results
files in order to be identified quickly. The PROGRAM column
explains with which ISA test program the tests have been
performed. In this case, there have been tests made with the
Automatic Module for Ansi67 Relays and tests performed by
means of the Manual Module. The TESTSET column indicates
which ISA Instrument has been used to perform the tests.
By clicking on a column header it is possible to order the rows by
the data contained in the column, for instance clicking on the
date column will order by date the rows (in this case there will be
no effect since the rows have same date).

The Test Plans table represents a list of the Test plans that have
been linked to the device identified by the relay node. This table
is present only for Breaker and Relay devices. A Test Plan is a list
of Macro functions to be executed by the device.
Suppose that a Test Plan has been linked to the device Relay1
(please see chapter 1, section 1.3 for a detailed description of
Test Plans, how to create, link them to a device and execute
them). When selecting the node from the network tree, the Test
Plans grid is filled with the relative Test Plans.

Test Plans are identified by a progressive number ID, by a Name


and a Description that are given at the time of the creation of the
Test Plan. The Date field represent the date when the Test Plan
has been linked (or associated) to the device.

The Recordings table represents a list of the Comtrade Recordings


that have been linked to the device. This table is not available for
Breaker devices. In this case the list is empty because no
Comtrade recordings have been imported.
Suppose that the import of a Comtrade recording has been made,
the Recordings table will show also one line.
DOC. MSE10015 REV. 6.5.2 Page 23/129

The column ID shows the identifying number that the TDMS


software has given to the Recording, a DATE column is provided
to let the user quickly see when the recording has been executed
on the device (not when the recording has been recorded). The
column ORIGINAL FILENAME, although not used by TDMS, is a
useful indication since sometimes users give specific names to
results files in order to be identified quickly. Finally the NAME
column is provided to display the identifying name that the user
has given to the recording while importing it (see paragraph
2.1.2)

1.2.4 TABLES MENUS


By selecting one or more rows on each of the grid (just click on a
row from the grey column where the black arrow is) and then
performing a right-click, a popup menu is opened and various
operations can be performed on the selected row.
For instance, by opening the menu on the second row of the Test
results grid it is possible to Print the results, View / Modify the
header information of the session, Execute the test results or
Delete the row.

Similarly, by opening the menu on the Test Plans table it is


possible to Print the Test Plan, Edit the Test Plan Header Info
(that is change the Name or the Description given to the Test
Plan), Execute the Test Plan, Delete the Test plan or Edit the Test
Plan Settings (modify the nominal settings or the characteristic of
the device on which to run the Test Plan).
DOC. MSE10015 REV. 6.5.2 Page 24/129

Please notice the difference between the Edit Test Plan Header
Info and Edit Test Plan Settings: the first allows to change the
Name and Description of the Test Plan, the latter while not
changing the Test Plan itself, allows to modify the Relay nominal
settings and characteristic.

Similarly, by opening the menu on a row of the Recordings grid it


is possible to View / Modify the information of the recording,
Execute the recording with Comtrade or Delete the row.

The menus described have a corresponding menu that can be


selected from the menu bar at the top of the TDMS window.
Please refer to the menu items TEST and COMTRADE for a
detailed explanation of the actions of these popup menus.

1.2.5 MENU OF THE NETWORK STRUCTURE


By executing a right-click on a node of the Network structure a
menu appears to allow to select various functionalities of TDMS
for the node.
In details:
for a Network node :
DOC. MSE10015 REV. 6.5.2 Page 25/129

it is possible to display or modify the name given to the


network and its description

for a Substation node:

it is possible to:
1. display or modify the name given to the Substation
and its description
2. print the report of all tests of all devices that have
been inserted in the substation

for a Line node:

it is possible to:
1. display or modify the name given to the Line and
its description
2. print the report of all tests of all devices that have
been inserted in the line

for any Relay node:


DOC. MSE10015 REV. 6.5.2 Page 26/129

it is possible:
1. display or modify the name given to the relay and
its description, the manufacturer, the model or the
serial number.
2. print the report of all tests of all tests that have
been inserted in the report
3. Display, remove or print the Relay Settings
DOC. MSE10015 REV. 6.5.2 Page 27/129

2. PROGRAM MENUS
In this chapter we describe the menus that can be found at the
top of the TDMS window, when the Network Tree and a relay of
the net are selected.

File;
Edit;
Test;
Comtrade;
Test plan;
Options;
Security;
?

When you select a CB, the selection Comtrade is not available.


When you select a Transducer or a CT or a VT, the selection Test
Plan is not available.
When you select Resistance or Impedances, selections Test,
Comtrade, Test plan are not available.

When you select Programs control, you only find the selections:
File; Options; Security; ?, and the content is the same.

2.1 Menu File


DOC. MSE10015 REV. 6.5.2 Page 28/129

2.1.1 OPEN TEST RESULTS


By choosing this option it is possible to select a results file via a
standard windows dialog and preview the results. This option can
be selected even if no structure has been created. In this case
though, the network and the substation cannot be identified and
will appear in the report preview.

2.1.2 IMPORT TEST RESULTS


This menu option, opens the Import files window.

As it can be noticed, the tree on the left reproduces the same


network tree already created in TDMS. There is a list that can be
filled with files, the button Add files to the list and the button
Automatic Import list.
The import of test data to corresponding device is carried out in
two different steps:
a) By pressing the Add files to list button, the user loads the
list with a number of files (or just one) that should be
imported. The files integrity is checked and if it does not
match with the requirements of TDMS, an error message
appears indicating that the file is not valid and cannot be
imported.
This procedure also checks the data contained in the file
and in case there are tests relative to more devices (such
in the case of results performed with T3000 and saved
DOC. MSE10015 REV. 6.5.2 Page 29/129

with Xpro3000 into an .mdb file) a breakdown of the


devices is made. So for each file added to the list, there
may be more than one row added to the list. Another very
typical example is that of a device that has been tested in
X_pro both with the manual mode and with one of the
automatic modules. True the tests refer to the same
device, but the software allows the user to import these
groups of tests separately and possibly to different
devices. Two rows will be added to the list, one for the
manual mode tests, the other for the automatic test, like
in the following picture.

b) Once the list contains at least one row, it is possible to


import the data. This is carried out in two possible ways
(please see the relative paragraph for a detailed
description of the procedure) :
o With a drag&drop: click on the row that should be
imported, keep the mouse button pressed, and
drag the row to the device on the network tree.
o By pressing the Automatic Import list. This
procedure automatically checks the network
structure and import the results to the correct
node.

2.1.2.1 Drag & Drop


When dragging an item from the list to the tree, the node is
highlighted and upon releasing the button, the corresponding
DOC. MSE10015 REV. 6.5.2 Page 30/129

data is imported to the main database. Please note that the


column Type of the list, identifies the type of device to which the
data refers to, so it is not possible to import results of tests
performed with an ISA software to a node that refers to a
different device type (for instance it is not possible to import a
Transducers results file into an Energy meter node). In such a
circumstance an error message will appear, indicating that the
selected data does not match the type of data of the device to
which the user tried to import.
There are only two exceptions to this rule, and apply when
importing results data performed with TDMS Manual mode and
with a T3000 in relay manual mode. In both cases, the test could
be performed on any device and therefore it is possible to import
these sessions to any of the device groups in the tree.
The import using the drag&drop feature may result in two
possible actions:
Creation of a new header on the network structure, and
immediate import of the data identified by the list item.
In order to create a new node (or header) while importing
data, select a list item, drag the item over the tree and
drop it on a group node instead of on a header node. For
example, when importing the second row of the above list,
which refers to a Ansi 67 Relay, drop the item on a Relays
node.

This will open the standard Relay Header window


discussed in paragraph 1.2 already filled with
Manufacturer, Model and Serial Number data coming from
the results.
DOC. MSE10015 REV. 6.5.2 Page 31/129

It is here possible to update this data and choose a name


for the relay node that will be created. Upon pressing the
Ok button, the node is created under the Relays group. By
pressing the Cancel button, the import procedure is
cancelled and no data is added to the database.
Please notice that this can be done ONLY WITH ONE ITEM
at a time. If more items are selected a warning will be
displayed to inform that it is not possible to add more than
one node.
Import of the data without the creation of a new node.
In order to import data to an already existing header
node, drop the drop the list item on a header node instead
of on a group node. For example, when importing the
second row of the above list, which refers to a Ansi 67
Relay, drop the item on the Relay 1 node.

Data is automatically imported with no other action to be


taken by the user.
More than one list items (if all referring to the same
device) can be selected, dragged and dropped on a node
to import all the relative data to the corresponding device.
DOC. MSE10015 REV. 6.5.2 Page 32/129

2.1.2.2 Automatic Import list


When pressing this button the software looks for devices in the
network structure that match the keys Substation Line Device
Serial Number of the items in the list.
Each results file contains these data. Care should be taken by the
user so that these fields are correctly filled in by means of the
appropriate ISA Test program.
All ISA test programs have a Header window where is possible to
identify Plant Name (this corresponds to Substation), Feeder (this
corresponds to Line) and Header Serial Number. Please notice
that the Instrument Serial Number field is different than the
Header Serial Number.
If values are correctly filled, the automatic procedure can easily
import all the test results into the database by selecting
automatically to which device they correspond. On the other
hand, if not match of the above described keys can be found, a
message appear to inform that the automatic procedure could not
be completed.

When using the automatic procedure it is not possible to create


new nodes. Data is imported in already existing header nodes if
the match is correct.

2.1.3 EXPORT DATABASE


This menu item opens a save dialog window by which the user
selects the name of a file that will contain the exported data. This
procedure can be carried out by an Administrator user and is very
useful both for backup, database replication or to allow to the
end-user to have a subset of the network structure on a local
machine. After selecting a node from the Network tree, (it could
be the entire network, a substation, a line or just a header node)
the software creates a subset of the database into a new
database file that can be used by another user on another
DOC. MSE10015 REV. 6.5.2 Page 33/129

machine.
For example a very common situation could be that of a Program
editor user that prepares test plans for his test operators. The
Program editor does not want the user to have the entire
network, but just the specific headers that he will test. By
exporting only these parts of the tree, he gives the user the
possibility to run only the tests prepared, by executing them from
the TDMS software installed on the test operator machine.

2.1.4 MERGE DATABASE


This menu item opens the Merge structures window with which it
is possible to load another database and merge parts or the
whole structure to import into the reference structure, which is
the one designed in TDMS.

As the window is open, the Reference structure appears in the left


tree. The name of the database that identifies the reference
structure is in the pink box on the left. The Show complete
structure option allow to display all the groups of the various lines
or only those that have been selected to be viewed as a line
option.
Press the button Browse on the right hand side to select the main
database of the Structure to import via a standard dialog window.
The extension of a main database is .isa.
Once the database is chosen, the relative tree is loaded in the
DOC. MSE10015 REV. 6.5.2 Page 34/129

network tree on the right. For example this is how it would


appear the window after opening another main database with
various devices already stored.

The merge procedure is purely manual:


Select the node from the Structure to import that you wish
to merge in the Reference structure
Press the mouse button as for a drag&drop operation
Drag the node on the reference structure, in a position
that corresponds to the type of data dragged. For instance
it is not possible to drag the CT named ct S/N 0214/473 in
a group node of the reference structure other than CT.
Release the button: an exact copy of the node selected in
the structure to import is now added to the reference
structure
DOC. MSE10015 REV. 6.5.2 Page 35/129

The merge can be done on the structure at all levels. It is


possible to import a header node, an entire line (select a line
node, drop on a substation node), an entire substation (select a
substation node, drop on a network node) or even the entire
network (select a network node drop in any position of the
reference structure). In case you import an entire network, a
message appears to explain that such network is added as a
whole to the reference structure, which will therefore be made of
two networks.

To close the merge structures window, press the X button at the


top right of the window.

2.1.5 SAVE
The software always updates the TDMS main database so that in
case of a system crash, all the changes to the database are not
lost. The Save menu item can be used to save a backup copy of
the database structure. A standard Windows dialog window
appears in order to select the name of the backup.
DOC. MSE10015 REV. 6.5.2 Page 36/129

2.1.6 PRINT NETWORK TREE


This option opens a print preview that enables to print or export a
simple report containing the key values of the network structure.
In this case the network is made of just a few nodes.

It is here possible to
navigate through the report pages by means
of the navigation buttons. In this case the buttons are
disabled since the report is made of just one page.
print the report by means of an installed printer that
can be chosen by the user
export the report into a format to be chosen at the
moment of export. A standard dialog window appears to
let the user choose the name of the exported file and the
type of file

select the zoom magnitude.

2.1.7 PRINT TEST REPORT


Printing the test report is one of the main features of TDMS and
therefore will be discussed in detail in a separate chapter. Please
DOC. MSE10015 REV. 6.5.2 Page 37/129

see chapter 3.

2.1.8 EXIT
This closes the software, and all modifications made to the
database are automatically confirmed.

2.2 Menu Edit

All the features in this menu can be executed only by an


Administrator user since they involve a change in the network
structure. Before selecting an item from this menu, a node must
be selected in the structure network, and the operations will refer
to the selected node.

New
It is possible to create a new node in the network structure by
choosing an item from the menu New. The item can be created
only if the selected node in the network tree corresponds to the
type of device that should be created. Each item in this menu has
an equivalent button in the toolbar at the top of the Network Tree
page.
DOC. MSE10015 REV. 6.5.2 Page 38/129

View/Modify
This item allows to change the identifying information of each
object. Depending on the object type, the relative window is
opened.
DOC. MSE10015 REV. 6.5.2 Page 39/129

It is possible to perform this identical operation by right-clicking


on the selected node and choosing the View/Modify item of the
popup menu.
Delete
It is possible to delete a selected node by selecting it and then
choosing Edit-Delete. Please notice that the delete procedure,
deletes all the data below the node selected. If a substation is
deleted, all the lines and all the header nodes of each lines will be
deleted from the database. Before deleting, a confirmation
window appears.

In case a network or a substation is about to be deleted a further


confirmation message box warns the operator of the implications
on the network structure of such a choice.
DOC. MSE10015 REV. 6.5.2 Page 40/129

2.3 Menu Test

The Test menu is equivalent to the menu that appears when


right-clicking on one test result.
View/Modify Test
This will open the Session information window for the selected
session. These information are imported together with the data
during the import procedure and have been set in the ISA test
program with which the test has been performed.

It is quite important to fill in correctly these fields since they will


appear on the report of the session. The Operator field can also
be used as a search criteria when printing reports. A Test
manager for instance may want to examine a report of the tests
carried out by a specific user in his test team.
If more than one session has been selected or if no session has
been selected, an error message appear, informing the user that
just one session must be selected in order to change header data.
DOC. MSE10015 REV. 6.5.2 Page 41/129

Execute test
This will execute the appropriate ISA test program to perform the
selected test result. If the software that is currently installed in
the PC is obsolete and cannot handle the data exported by TDMS,
a message will appear, inviting the user to update the specific
software to the latest available version.

The data is exported anyway and a file is created. The filename


although strange gives the indication of the exact date and time
in which the execution was attempted. The name is in the format:
tdms(year)(month)(day)(hour)(minute)(seconds). A message
appears to let the user know where the file has been created.

If more than one session has been selected or if no session has


been selected, an error message appear, informing the user that
just one session must be selected in order to execute the tests.
DOC. MSE10015 REV. 6.5.2 Page 42/129

Delete test
By selecting this menu, it is possible to delete from the database
the data corresponding to the session or sessions selected.

2.4 Menu Comtrade

The Comtrade menu is equivalent to the menu that appears when


right-clicking on one recording.
View/Modify Recording Header
This will open the Recording information window for the selected
recording.

These information is inserted by the user upon importing a


recording and appear when printing the recordings. The info in
the Name field is displayed in the column Name of the Recording
grid.
Execute recording
This will execute the ISA test program Comtrade to perform the
selected recording. If the Comtrade software that is currently
installed in the PC is obsolete and cannot handle the data
exported by TDMS, a message will appear, inviting the user to
update the specific software to the latest available version.
DOC. MSE10015 REV. 6.5.2 Page 43/129

The data is exported anyway and a file is created. The filename


although strange gives the indication of the exact date and time
in which the execution was attempted. The name is in the format:
tdms(year)(month)(day)(hour)(minute)(seconds). A message
appears to let the user know where the file has been created.

If more than one recording has been selected or if no recording


has been selected, an error message appear, informing the user
that just one session must be selected in order to change header
data.

Delete recording
By selecting this menu, it is possible to delete from the database
the data corresponding to the recording or recordings selected.

2.5 Menu Test plan


For this menu, please refer to the corresponding chapter.
DOC. MSE10015 REV. 6.5.2 Page 44/129

2.6 Menu Options

The options menu contains various items that allow to configure


both the appearance and behaviour of TDMS.

2.5.1 PREFERENCES
The TDMS Preferences window allow the user to identify a few
important settings for TDMS. The importance of these settings
makes it a feature available only to Administrator users.
The window has three main pages: the Directories tab, the Logo
tab and the Reports tab..
Directories Tab
DOC. MSE10015 REV. 6.5.2 Page 45/129

In the directories tab it is possible to define the directories in


which the software searches for the described elements:
Report models: this is the directory that must contain the
reports (.rpt files) that will execute the print preview of
export to .pdf, .doc or .xls format. After installing the
software, this directory is set to be c:\xtest\tdms\reports.
In case a user asks ISA to tailor the reports to his specific
need, it is possible to identify which directory contains the
modified reports, so that the original reports shipped with
the installation are not to be overwritten.
If the selected directory does not contain report files, upon
pressing the Ok button an error message appears.

Database Models: this is the directory that contains the


database model. The files in this directory MUST NOT BE
DOC. MSE10015 REV. 6.5.2 Page 46/129

MOVED OR REPLACED. Please do not try to OPEN these


files, especially during the program execution. These are
models that the program uses continuously as a database
reference.
If the selected directory does not contain the model files,
upon pressing the Ok button an error message appears.

Database: this directory identifies the position of the


reference structure. Normally it coincides with the
Database models directory. Again the files in this directory
should not be MOVED OR REPLACED. Please do not try to
OPEN the files in this directory, especially during the
program execution.
If the selected directory does not contain a database file,
upon pressing the Ok button an error message appears.

Reference structure: this is the main database (with


extension .isa) that the TDMS software currently displays.
It is possible to open a different structure by selecting the
appropriate database directory (see previous point) and
the relative structure name.
This will prompt the user to login to the other database
upon pressing the Ok button.
The user may not have the same privileges on a different
database and may not even be a user on the new selected
database. If the user does not know the login and press
the cancel button, the following message appears.
DOC. MSE10015 REV. 6.5.2 Page 47/129

If the Ok button is pressed, then it is possible to try a new


password, otherwise the TDMS software is shut down for
security reasons.
Please consider that even if the software could allow the
user to access the newly selected reference structure, the
next time TDMS is run, the same problem occurs, and the
user would not know how to enter the TDMS software,
blocking therefore the execution of the program to such
user. This potential problem is prevented by shutting down
the software when the new login procedure fails.
It is also possible to create a new reference structure
database by pressing the button Create New. By pressing
the button, the user is asked to insert a name for the
structure. Please indicate a name without any special
character (|!$%&/()=?^\-[] {}#@.:;,<>). Press Ok to
create the file.

Logo Tab
DOC. MSE10015 REV. 6.5.2 Page 48/129

In the logo tab it is possible to select which logo will appear in the
report or when exporting to .pdf, .doc or .xls.

Reports Tab

This page is provided in order to set the report template. For each
type of result, we make available a default report to print the test
results. But it is possible to add further templates in order to print
reports in a different way. For instance we also provide a compact
DOC. MSE10015 REV. 6.5.2 Page 49/129

report for the printing of a breaker test result.


In this page it is possible to select the report template that will be
used when printing the report. It is possible to open this page at
any time during the TDMS execution so to change the report
style.
In order to select the desired report template from the list, select
the report, and press the mouse right button: the following menu
will appear:

After selecting the menu item, the report selected will become
the default for the following print actions on the selected type of
result.

>>>

2.5.2 COMPACT DATABASES


After working with TDMS many times, managing the nodes on the
network tree, such as importing, deleting, merging structures,
the database may grow in size and slow down the speed with
which actions are performed.
The Compact databases procedure allows an Administrator user
to optimize the size and performance of the databases. A
message appears to prompt the user for the compacting
procedure.
DOC. MSE10015 REV. 6.5.2 Page 50/129

If the user presses Cancel, no action is taken on the databases. If


the user press Ok, the compacting procedure is carried out.
Depending on the size of the databases and the amount of data
to optimize, this may take a few minutes. During the optimization
DO NOT TRY TO OPEN, COPY OR MOVE FILES FROM THE
DIRECTORIES IDENTIFIED IN THE TDMS PREFERENCES. Please
let the procedure finish. The user is informed of the status of the
compacting procedure and when the procedure is finished.

2.5.3 LANGUAGES
It is possible to set the display language for TDMS. By clicking on
a specific language menu item, the appearance of TDMS main
window and all the others will change accordingly, the messages
will be given in the new language and the reports will also be
translated.

2.6 Security

The security menu contains the Login and the Privileges


submenus. At any time during the execution of the software, it is
possible to perform a new Login to change the user.

2.6.1 LOGIN
As soon as the user executes the software TDMS, a login page
appears. This identifies the user and sets the privileges to him
entrusted.
DOC. MSE10015 REV. 6.5.2 Page 51/129

As the software is run the first time, no users have been set and
therefore there is no password. Just press the Ok button to start
using the software. By pressing the Cancel button, the software is
closed. The user should also select his main activity by choosing
the correct option: Power Generation or Transmission &
Distribution. This will tailor some descriptions and messages in
order to be more understandable by the user.

2.6.2 PRIVILEGES
The operator that enters the TDMS software for the first time has
the privileges of an Administrator user, being able to create users
and set their privileges.
In order to do so, choose the menu Security - Privileges. This
opens a new window where it is possible to Add, Edit or Remove
users.
DOC. MSE10015 REV. 6.5.2 Page 52/129

Press the Add user button to add a new user. In the following
window it is possible to set User name and Password for the user.
Also the Privileges associated with this user, to be chosen from
one of the options on the right.

The four main areas of user privileges are:


a) full control of the network structure. The user manages
the various elements on the network, adds, edits or
deletes nodes, imports or exports data.
b) full control over the execution of all ISA test programs.
The user is able to choose which program to execute and
can design new tests procedures.
c) limited control over the execution of ISA test programs.
The user is able to choose a previously imported test, and
runs the specific program with these tests.
d) Print preview or export in .pdf, .doc or .xls of the test
results and settings
The three groups identified to handle the above user privileges
are:
Administrator: is a special user that has the privileges to
perform every functionality in TDMS. An administrator has
full control of the network structure (a), full control over
the execution of all ISA test programs (b) and can execute
the printing (d). There can be more than one administrator
user. We suggest that only one administrator user should
manage the network structure.
Program editor: this user does not control the network.
Still, he has full control over the execution of all ISA test
programs (b) and can execute the printing (d). This makes
him a true Program Editor. He will usually design and
implement a series of test with a particular software, and
DOC. MSE10015 REV. 6.5.2 Page 53/129

import the results. This allows him to prepare well defined


test procedures that cannot be modified.
User: this user has privileges only to execute previously
set (by administrators or program editors) test procedures
by running the appropriate software, so he has limited
control over the execution of ISA test programs (c) and
can execute the printing (d).
The following table summarizes the differences among user
privileges:

Network Full control Limited Report


control of ISA test control of Preview
programs ISA test
programs
Administrator X X X X
Program X X X
editor
User X X
Table 1. User privileges differences

Select the user type, name and password and press ok, the user
will be added to the list of users. Repeat this procedure for all the
users.

Press the Edit User button to change a users Password or


Privileges. It is not possible to change a Username. Please create
DOC. MSE10015 REV. 6.5.2 Page 54/129

a new username for this purpose.


Select one or more users from the list and press the Remove user
button to delete the selected users from the list of users.
By pressing the Ok button, the list of users is saved into the
database. It is mandatory to set at least one administrator user.
A warning message appears if no administrators have been added
and it is not possible to leave the Privileges window until this user
is added. By pressing the Cancel button, all changes made to the
users list are discarded and the programs returns to the main
window of TDMS.

2.7 Menu ?

The menu About TDMS opens a window that describes the version
of the software, the currently connected user and ISA contact
details.
DOC. MSE10015 REV. 6.5.2 Page 55/129

3. PRINT REPORT
This section refers to the menu selection File-Print Test Report.
Printing and exporting reports is such a big feature of TDMS that
the printing procedure is described in this separate chapter.
The print report menu is available only if a node from the network
tree is selected. If no node has been selected yet, the following
message appears:

It is also not possible to print an entire network, the printing can


be performed starting from a substation node. If a network node
is selected, the following message appears.

When the user selects this menu item, the Print Report window
appears:
DOC. MSE10015 REV. 6.5.2 Page 56/129

The caption of the window identifies the portion of the Network


Tree that has been selected for printing. Furthermore this window
configures itself depending on the data that is associated to the
selected node (or results if one or more rows from the Test
results grid are selected).
TDMS looks for the test results that have been imported in all the
objects under the selected node, and gives a configuration page
for each report that will handle such data.
The window is divided in two main pages:
a) the Search criteria page allows the user to further set
general rules as to which data should be previewed and
then printed or exported.
This page is further divided in two main pages mutually
exclusive: the printing will be done according to the
selection

Common Results are the results obtained by running ISA


Software as standalone, Test Plans are results obtained by
executing Test Plans and are therefore a collection of all
the results of the macros.
DOC. MSE10015 REV. 6.5.2 Page 57/129

If the Common Result page is selected, it is possible to set


search criteria as described in section 3.1.
If the Test Plans page is selected, it is possible to select
ONLY ONE Test Plan from the list provided as in the
following example.

b) the Printing Options page allows to configure the printing


for each of the reports involved in the printing. This page
is further divided in pages corresponding to the Type of
Device that carried out the tests:
Relays
Comtrade
Breaker
Energy Meter
Transducer
PQ Meter
Relays T1000/T3000
Line Differential
Transformer
BTS
The Relays page is also divided into two main pages
Manual Test
Automatic, which groups the settings for the
Distance Relay 21, Overcurrent Relay 50-51,
Differential Relay 87, Directional Relay 67,
Synchrocheck Relay 25
When pressing the Change Report Logo button, the TDMS
DOC. MSE10015 REV. 6.5.2 Page 58/129

Preferences window is opened and by means of the Browse


button it is possible to select the Logo to show in the reports.
When pressing the Print Preview button, the data is searched
according to selections and the preview window appears. There
are as many preview tabs in the preview window as the number
of reports that have been selected in the Include report frame of
the Search Criteria page.

The user can navigate through the pages of each report, by


selecting the page pressing on the relative tab at the top of the
page:

On each page there is a list of icons that allows to:


navigate through the report pages by
means of the navigation buttons
print the report by means of an installed printer that
can be chosen by the user
DOC. MSE10015 REV. 6.5.2 Page 59/129

export the report into a format to be chosen at the


moment of export. A standard dialog window appears to
let the user choose the name of the exported file and the
type of file

select the zoom magnitude.


It is possible to print all the reports automatically by pressing the
button at the top of the window.

3.1 Search Criteria


The Print Report window always opens in the Search criteria
page. This page is configured depending on the type of the
results. If among the results identified by the selected node some
have not been executed by means of Test Plans, the Common
Results selection will be available. Similarly if among the results
identified by the selected node some have been executed by
means of Test Plans, the Test Plans selection will be enabled.

3.1.1 COMMON RESULTS


If among the results identified by the selected node some have
not been executed by means of Test Plans, this page will be
enabled. The user can perform a series of selections that extract
only the information needed.
DOC. MSE10015 REV. 6.5.2 Page 60/129

3.1.1.1 Session dates

The session dates option allows to refine the search to those test
results that have been performed within a certain period. By
selecting the option As per selection, it is possible to define the
From and To date via a drop down menu.

3.1.1.2 Selections

These further selections allow the user to set specific queries on


the data.
DOC. MSE10015 REV. 6.5.2 Page 61/129

For instance, by opening the Operator drop down menu, it is


possible to view a list of all operators that have performed tests
imported under the selected network node.
The same apply for the Manufacturer (list of all devices
manufacturers), Model (list of all devices models) or Serial
Number (list of all devices Serial numbers).
It is possible to write in these drop-down menus as a mean to
identify more quickly the desired item in the menu.

3.1.1.3 Include report

The Include Report frame allows the user to define which reports
he wants effectively to preview. The reports that are not available
for the selected network node are greyed and cannot be
previewed. If there are Comtrade recordings associated with the
selected data, the Comtrade report is also available. The
Multifunction Relay check, is a report that previews in a single
report the 4 individual reports, Ansi 50-51, 87, 67 and 25. Since
this report may take some time to display, it is commonly not
checked, and the reports for the different ANSI standards are run
separately.

3.1.2 TEST PLANS


If among the results identified by the selected node some been
executed by means of Test Plans, this page will be enabled. The
user can select ONLY ONE Test Plan from the list that is shown.
DOC. MSE10015 REV. 6.5.2 Page 62/129

Clicking on any row will automatically select the relative Test


Plan. ONLY THE SELECTED TEST PLAN will be printed.

3.2 Printing Options


The Printing Options page is further divided in pages describing
the reports of each of the type of devices involved in the current
printing session.
The Include Notes Page option lets the user to add the Notes that
may have been written at the time the tests were performed and
that were saved with the data.

3.2.1 RELAYS
The Relays page includes the Test performed with the Manual
Test module and those performed with automatic modules.
DOC. MSE10015 REV. 6.5.2 Page 63/129

3.2.1.1 Manual tests

When the selected network node contains tests sessions


performed with Manual mode, the Manual test page is available.
The Graph Settings frame allows to choose whether to Show
graphs in the report and to join the points of the graphs with a
line. It also allow to make a sub-selection of the test types that
should be included in the preview by selecting separately the
Shot, Ramp, Delta Ramp and Sequence test types. Also the
Columns Selection allows the user to choose one by one which
columns will be displayed in the preview.
When more Test results are to be printed in the same report, it is
possible to select, for each test result, the columns that will be
printed. Select the option Choose columns for each session and a
series of lists will appear to let the user select the appropriate
columns.
DOC. MSE10015 REV. 6.5.2 Page 64/129

Upon pressing the Print Preview button, the selections are saved
into the substation database, so that the next time the same test
result is printed, the same columns are automatically displayed.
A maximum of 9 columns can fit in the standard report for Manual
mode. If more columns are selected the following message
appears:

Once a certain combination of selection for this report is made, it


is possible to save the list of selections in a Layout Template.
Press the Save Current Layout button to identify a name for the
layout.
DOC. MSE10015 REV. 6.5.2 Page 65/129

Upon pressing Ok, the template is saved and appears in the


Layout templates Menu

The selected template can be deleted by pressing the Delete


Current Layout button. When more Layouts are available, just
select the one appropriate for the current printing preview needs
and the objects in the page will be selected accordingly.
DOC. MSE10015 REV. 6.5.2 Page 66/129

3.2.1.2 Automatic Tests


Distance Relay 21

When the selected network node contains tests sessions that


have been performed with ISA Distance 21 test program, the
Distance Relay 21 frame is available.
The Graphs settings box allows to decide whether to include the
graphs in the report. It is possible to define also whether to
Show tolerances and which zones to view.

Overcurrent Relay 50-51


When the selected network node contains tests sessions that
have been performed with the Overcurrent ANSI 50-51 automatic
module, the Overcurrent Relay 50-51 test page is available. It is
possible to define whether to include the graphs in the report.

Differential Relay 87
When the selected network node contains tests sessions that
have been performed with the ISA ANSI 87 automatic module,
the Differential Relay 87 test page is available.

It is possible to define whether to show graphs in the report. For


the graphs ID-IR it is also possible to set the same scale on both
axes or to leave the scale adjustment automatic.

Directional Relay 67
DOC. MSE10015 REV. 6.5.2 Page 67/129

When the selected network node contains tests sessions that


have been performed with the ISA ANSI 67 automatic module,
the Directional Relay 67 test page is available. It is possible to
define whether to include the graphs in the report.

Synchrocheck Relay 25
When the selected network node contains tests sessions that
have been performed with the ISA ANSI 25 automatic module,
the Synchrocheck Relay 25 test page is available. It is possible to
define whether to include the graphs in the report.

3.2.2 T1000/T3000

When the selected network node contains tests sessions


performed with T1000 or T3000 relay mode, the T1000/T3000
test page is available.
Please refer to paragraph 3.2.1 since the selections have exactly
the same meaning.
DOC. MSE10015 REV. 6.5.2 Page 68/129

3.2.3 TRANSFORMER

When the selected network node contains tests results performed


on transformers, the Transformers test page is available.
There are two possible reports to print:
Normal Report is a list of all the tests performed on the
Transformer. Some test types include a graph, and the
style of the graph can be selected in the Graph Style drop
down menu. The Include Notes Page option lets the user
to add the Notes that may have been written at the time
the tests were performed and that were saved with the
data.
Special Report contains the Compare Excitation Curves
report. This report allows to compare the excitation curves
of a CT. It is not possible to select the comparison criteria
in TDMS, but if the comparison is set in XPro3000 prior to
the data being imported, then TDMS opens a list of
comparison groups already set and the user may choose
which comparison criteria to use.

3.2.4 BREAKER
When the selected network node contains tests sessions
performed with a Circuit Breaker, the Breaker test page is
available.
DOC. MSE10015 REV. 6.5.2 Page 69/129

It is possible to define a few Report options on the left frame,


while in the Channels Selection frame it is possible to define for
each of the results which channels should be included in the
resulting graph. Each of the result is also identified by the Type of
the test: CLOSE, OPEN, OC (open-close), CO (close-open) or OCO
(open-close-open)

3.2.5 COMTRADE
When the selected network node contains tests sessions that
have associated Comtrade recordings, , the Comtrade test page is
available.
No selections are available for this report. The report is a list of
all the recordings that have been associated to the physical
outputs of the ISA Instrument used to reproduce the recording,
both analogue and digital.
DOC. MSE10015 REV. 6.5.2 Page 70/129

3.2.6 ENERGY METER

When the selected network node contains tests sessions


performed with ISA Energy Meter test program, the Energy Meter
test page is available.
Please refer to paragraph 3.2.1 since the selections have exactly
the same meaning. The only difference is that it is possible to set
the title of the graph (should it be displayed) by means of the box
Graphs Title. Since the Type, Title and Phase columns are used by
the report to group the results, it is not possible to uncheck them.
Therefore the number of column that can be viewed
simultaneously in the report is 12. If too many columns are
selected the following message appears.

3.2.7 TRANSDUCERS
When the selected network node contains tests sessions that
have been performed with ISA Transducers test program, the
Transducers test page is available.
DOC. MSE10015 REV. 6.5.2 Page 71/129

Since all the saved data of a tests performed with the ISA
Transducers Test program can be displayed at the same time in
the report, there is no need to perform particular selections, just
the Include Notes Page option is specified to let the user add the
Notes that may have been written at the time the tests were
performed and that were saved with the data.

3.2.8 PQ METERS
When the selected network node contains tests sessions that
have been performed with ISA PQMeters test program, the
PQMeters test page is available.
The report is a list of all the tests performed on the PQMeter and
the selection of data is made automatically depending on the type
of test, so there is no needs to perform particular selections, just
the Include Notes Page option is specified to let the user add the
Notes that may have been written at the time the tests were
performed and that were saved with the data.

3.2.9 LINE DIFFERENTIAL

When the selected network node contains tests sessions that


have been performed with ISA Line Differential test program, the
Line Differential test page is available.
The selections are very similar to those described in par 3.2.1,
please refer to this paragraph.
DOC. MSE10015 REV. 6.5.2 Page 72/129

3.2.10 BTS

When the selected network node contains tests sessions that


have been performed with ISA Battery Benches test program, the
BTS test page is available.
In addition it is possible to select the measures to include in the
final report by means of the option Show Sample Every xx
minutes.
DOC. MSE10015 REV. 6.5.2 Page 73/129

4 TEST PLANS FOR MULTIFUNCTION RELAYS


Modern relays host a number of test capabilities that make them
more and more Multifunctional. In order to test all the functions
of such a Relay, the user can create and run a Test Plan, which is
a list of macro functions to be run on the same device. To create
a Test Plan, go to the Program Control Tab: one button is
dedicated to the Test Plan functionalities.

By choosing the Editor menu item, it is possible to create, edit,


modify, delete, save a Test Plan. By choosing the Run menu item
it is possible to select and run the tests of a Test Plan.

4.1 What are Test plans?


This paragraph offers an introductory view to Test Plans.
A Test Plan is a list of macro functions that can be run on a relay.
Such a list is by definition independent from the characteristic of
a relay, and this makes it possible for a Test Plan to be run on
any relay having the test capabilities defined by the Test Plan.
This also implies that the macros are not defined to details that
refer to a particular relay. For instance, one of the macros
available is Overcurrent 5051 Search definite time thresholds.
This macro does not define which thresholds to search: since
each relay has a different nominal characteristic it will
automatically look for all such thresholds. But this macro asks for
the Type of Fault to be defined. So the test plan that runs this
macro executes a search of the Time Thresholds whatever the
relay characteristic, but only for the selected Types of Fault.
There are three main actions related to the use of a Test Plan.
1. Creation of the Test Plan
This step is performed by using the Test Plan Editor
function of TDMS. You can run this function by choosing
Relay Test Plan Editor Editor from the Program control
DOC. MSE10015 REV. 6.5.2 Page 74/129

This function is described in more details in the coming


paragraphs.
A Test Plan that has been created and saved, at this
stage does not include any setting related to a specific
relay. Lets say it is a list that potentially can be run on
any relay and for this reason is kept void of any relay-
related setting. So the next necessary step is that of
setting the relay characteristic by Associating the Test
Plan to a Relay.
2. Association of the Test Plan to a Relay.
This step is also performed by using the Relay Test Plan
Editor Editor function of TDMS. Once the Test Plan is
saved, it can be applied to any relay in the Network
tree. This step is essential in order to tailor the Test
Plan to the characteristic of a specific relay. Associating
a Test Plan to an Overcurrent relay means for instance
to define its Nominal Characteristic, the Trip Contact
and its Status, the maximum time and so on. This must
be done in order for the Test Plan to take effect on the
specific settings of the relay
3. Execution of the Test Plan
Once the original Test Plan has been applied to the
specific relay with step 2, you have in effect created a
new Test Plan tailored to the settings for the relay and
that can be applied only to this relay. In order to run
this Test Plan, you have two options:
Use the function Relay Test Plan Editor Run from
the Program Control: this gives a list of the Test
Plans that have been associated and therefore can
be run on the relays of the Network Tree.
Select the Relay node from the Network Tree: the
grid Test Plans contains a list of the Test Plans that
have been applied to the relay. From this grid it is
possible to Run the chosen Test Plan.
These methods will be described in the following
DOC. MSE10015 REV. 6.5.2 Page 75/129

paragraphs of this chapter.

4.2 Editor of Test Plans


By choosing the Relay Test Plan Editor Editor menu item, the
following window is opened.

The Test Plan Editor window can be set to 4 different statuses


that modify the appearance and the functionalities that can be
used:
a) Test plan Closed : the window does not show any Test
Plan, only menus and toolbar are available.
b) New Test Plan : a new Test Plan ready for editing is
created and displayed.
c) Editing Test Plan : either a new Test Plan or a Test Plan
that has been loaded is undergoing modifications by the
user
d) Linking Test Plan : a Test Plan that have been saved is
linked to a Relay of the Network Tree
The window opens in New Test Plan mode by default.

At the top there are a menu and a toolbar, that allow to create
DOC. MSE10015 REV. 6.5.2 Page 76/129

and to edit the Test Plan. A few Test Plan settings are also found
at the top of the window. Then the window is divided in two
sections:
Modules
In this frame there are all the macro functions that can be
used in a Test Plan
Test plan
In this frame there is a grid that shows all the macros
included in the test plan. There is also a little toolbar to
edit the Test Plan.

4.2.1 MENU AND TOOLBAR


At the top of the page there are two main Menu Items
Test Plan

These menu items have an identical corresponding


item in the toolbar.

Type of Protections
DOC. MSE10015 REV. 6.5.2 Page 77/129

First, lets have a look to the Test Plan Menu.

4.2.1.1 Menu Test Plan


This is the main menu of the Test Plan Editor window. Here are
summarized the main functions that can be performed on a Test
Plan:
New: Creates a new Test Plan. Sets the window to the
New Test Plan status. If the user has made some
changes to the Test Plan, when choosing this function the
following message of confirmation appears.

The Test Plan Editor window is then loaded with a new


Test Plan.

Open: Opens a window (List of Test Plans) to choose the Test


Plan.

Here it is possible to choose from the Test Plans that have


DOC. MSE10015 REV. 6.5.2 Page 78/129

been already created and stored into the TDMS database.


These Test Plans do not contain any specific relay setting.
Double-click on the row or select it and press the Ok
button. The Test Plan will be loaded in the Test Plan Editor
window which is also set to the Editing Test Plan status.
It is also possible to select a Test Plan and delete it from
the list by pressing the Delete Test Plan button at the top
of the window.

Close: Closes the Test Plan and sets the Test Plan Editor
window to the Test Plan Closed Status. The window
appears empty and in this status it is only possible to
Open a Test Plan or to Create a new one.

Delete: deletes the Test Plan that is currently opened. The


other option to delete a Test Plan is by using the List of
Test Plans window that can be opened by choosing the
menu Open. If the user has made changes to the Test Plan
the following message of confirmation appears.
DOC. MSE10015 REV. 6.5.2 Page 79/129

Once the Delete function is complete, the window is set to


the Test Plan Closed Status. In this status it is only
possible to Open a Test Plan or to Create a new one.

Save: saves a Test Plan with the name written in the


Name box. Once the save is complete a confirmation
message appears

Save as: same as the Save option, but it allows to define a


new name for the Test Plan, without changing the Test
Plan that is being edited. A Window appears to allow to
define a Name and Description of the New Test Plan.

It can be used to duplicate Test Plans in order to edit a


copy of the Test Plan instead of editing the original one.

Link: associates a Test Plan to an existing Relay. The


DOC. MSE10015 REV. 6.5.2 Page 80/129

window is set to Link Test Plan status

In this status, the window changes completely


appearance, allowing the user to select a relay node from
the Network Tree in order to complete the Link. If a
Network tree has not been created yet, it is possible to
create it now by using the toolbar ( ) at
the top of the frame Select Relay Header to Link Test Plan.
The buttons in this toolbar replicate those in the Network
Tree toolbar; see the paragraphs relative to the TDMS
menus for details on how to use them. By pressing the
Link button, the process of associating the Test Plan to the
relay starts. By pressing the Cancel button the window
returns to the Edit Test Plan Status.

When the Link is complete, by choosing the node of the


Relay in the Network Tree page, the table Test Plans will
show that one Test Plan is available for the Relay.
DOC. MSE10015 REV. 6.5.2 Page 81/129

Exit: Closes the Test Plan Editor window

4.2.1.2 Menu Type of Protections


By choosing the Edit menu item, a new window is opened to allow
the user to create customized families of test.

The picture shows that no Type has been added yet. If Types
have already been defined, the window shows the relative list.
A Type of Protection can be described as the name given to a
DOC. MSE10015 REV. 6.5.2 Page 82/129

family of protections that can run only a subset of all the Macros
available for the creation of a Test Plan. The creation of a Type of
Protections is optional; by default a Test Plan can contain any of
the Macros. That of creating a Type of Protection serves only as a
guideline for the operator to choose only the appropriate Macros.
The Macros that can be defined are grouped in main Modules:
Generic Tests
ANSI 25
ANSI 5051
ANSI 67
ANSI 87
ANSI 21
Wait
Shell
As it can be seen from the list, a Test Plan can also contain
special Macros that do not represent specific tests but that are
important for the correct execution and flow of the Test. These
are the Wait Pause macro, which inserts a pause in the Test
Plan, and the Shell macro, which runs an external application.
A Type of Protection can be Added, Edited if existing or Deleted
by choosing the relative button at the top of the window. By
pressing the Add Type button at the top, a new window appears.
It allows to define one by one which Macros can be selected for
the Type of Protection. As an example, the window shows a
selection of Generic Tests and other functions, saved with the
name Selected Macros.
DOC. MSE10015 REV. 6.5.2 Page 83/129

Once the user presses the Ok button, the Type of Protection is


added to the list and when going back to the Test Plan Editor
window, this is inserted in the menu Type of Protections and can
be selected as a parameter for the Test Plan.
If a Test Plan is created by choosing as Type of Protection the
above type, it will not be possible to add a few Macros of the
Generic Test module, none of the ANSI 25 module and none of
the ANSI 67 module.

4.2.2 TEST PLAN SETTINGS


At the top of the window there are a few Test Plan Settings

The grey box on top contains the name of a Test Plan if a


Test Plan has been opened from the list of previously
DOC. MSE10015 REV. 6.5.2 Page 84/129

saved test plans. It is empty if the window shows a new


Test Plan, because a name has not yet been chosen.
The Type of Protection box is a menu that contains a list of
users customized selection of viable tests for the Test
Plan. By means of the Type of Protections menu at the top
of the Editor Window, the user can create customized
views of the Macro functions as a guideline of the Macros
that can be applied to a family of Relays, enabling or
disabling some Macros.
The Instrument box is a menu that contains a list of ISA
Test Instruments.

One of the Test Plan Settings is the instrument that will be


used to run the Test Plan. If a different ISA Instrument will
be used than the one that have been selected, a message
of warning may appear during the Test Plan execution,
especially when an Instrument with lower capabilities is
running a Test Plan that has been created for a more
powerful Instrument.
The Name box allows the user to choose a Name for the
Test Plan. This name will be used to identify the Test Plan
at all times.
The Description box allows the user to choose a
Description for the Test Plan

4.2.3 MODULES
By pressing any of the buttons in the Modules frame, a menu with
the Macros available for the specific module appears.
DOC. MSE10015 REV. 6.5.2 Page 85/129

Generic Tests

Synchrocheck ANSI 25

Overcurrent ANSI 5051


DOC. MSE10015 REV. 6.5.2 Page 86/129

Directional ANSI 67

Differential ANSI 87

Distance ANSI 21

Pause

External Program

The icons on the buttons and the menus describe the relative
Test.
By selecting one item from the menu it is possible to add the
Macro to the Test Plan.

4.2.4 ADDING A MACRO TO THE TEST PLAN

Suppose the user wants to add to the Test Plan the Search /
Verify the R-X characteristic macro for a Distance relay. When
DOC. MSE10015 REV. 6.5.2 Page 87/129

choosing this menu item form the menu that appears by pressing
the button Distance ANSI 21 the following window is displayed.

It is possible to define the characteristics of the search, start,


stop and step angles and for which zones the test should be
done. As a further selection, the Fault types and the Test
sequence need also to be defined.
This top part of the window is customized for each of the Macros.
For instance when choosing the Verify curve Macro of a
Differential ANSI 87 the window will appear like this.
DOC. MSE10015 REV. 6.5.2 Page 88/129

The bottom part of the window on the other hand remains exactly
the same for all the macros.
It has a Show message to the operator box and the Remarks box.
For each of the Macros it is in fact possible to add a message to
be displayed to the operator when the test is actually performed.
If the Show message to the operator box is selected, this
message will appear and stop the execution. The user will need to
press the Ok button on the window that will display the message
in order to continue the execution. The Remarks are on the other
hand comments that the creator of the Test Plan adds to the
Macro. Both boxes can contain text and pictures.
By pressing the Add Test button, the Macro is automatically
added to the Test Plan as the last test to be performed. By
pressing the Cancel button, the Macro is not added to the Test
Plan.

4.2.5 TEST PLAN LIST OF MACROS


Suppose that the two Macros mentioned in the Adding a Macro to
the Test Plan paragraph are actually added to the Test Plan, the
frame Test Plan of the Editor Window will contain two rows.

It is possible to Edit each of the Macro by double-clicking on the


row or by selecting the row and then pressing the button in
the toolbar. This will open again the Add Macro to the Test Plan
window with the settings previously performed. It is possible to
change the order of the Macros by selecting the row and then
pressing the Up or Down buttons. It is also possible to
delete one Macro from the Test Plan by selecting the item and by
DOC. MSE10015 REV. 6.5.2 Page 89/129

pressing the relative button . When a Test Plan is edited, the


Test Plan Editor window status is set to Edit Test Plan.

4.2.6 SAVING AND LINKING THE TEST PLAN


Now that the Test Plan has been created, the user can save the
Test Plan by writing a name in the Name box and press the Save
button of the toolbar or, alternatively choose the Test Plan Save
item in the menu.
Once the Test Plan is saved, it is possible to Link (or associate)
the Test Plan to a Relay in order to tailor it to the specific settings
and characteristic of the Relay.
Select the Link button of the toolbar or, alternatively choose the
Test Plan Link item in the menu. The Test Plan Editor window
changes appearance to execute the association.

After selecting the relay node to which the Test Plan should be
linked, press the Link button at the bottom of the window.
DOC. MSE10015 REV. 6.5.2 Page 90/129

During the linking process the window changes appearance to


inform the user of the progress. A Stop button appears and can
be used to Stop the linking of the Test Plan in any moment, while
all the other controls are disabled. The box below the Stop button
describes the current status of the linking process: the Step of
the Test Plan currently being linked and a description of the
software module that is handling the link. Please note that the
number of steps of the Test Plan DOES NOT correspond to the
number of Macros in the Test Plan. One Step groups all the
consecutive Macros specified by the same module. For example, if
the Test Plan is made up of more macros all of the Distance 21
Module only one step will be linked, in fact all the macros of such
a Test Plan work on the same Relay characteristic and settings.
If for some reasons the user chooses to Stop the linking before it
automatically concludes, a confirmation message will appear.

In the meantime, as described in the box, a module is taking care


of the Linking. In particular, the Distance module handles this
DOC. MSE10015 REV. 6.5.2 Page 91/129

first step of the Test Plan. Although the following pictures show
the behaviour of the Distance 21 module, it should be noted that
the sequence of events and the description is valid for all the
Steps of the Test Plan, regardless of the module that handles
them, with the only exception of the General Tests macro; see
the following paragraph for a more detailed description of these
tests.

a) The module appears with a message reminding of the


actions to be taken in order for the link to be successful.

b) It is possible to specify all the nominal parameters and to


load a nominal characteristic for the relay if known. The
window shows only the parameters that can be modified.

c) A box describes the status of the linking process


DOC. MSE10015 REV. 6.5.2 Page 92/129

When all the settings have been defined, press the


Continue button to go to the next step of the Test Plan or
to conclude the linking if this step is the last step in the
Test Plan. A confirmation message appears.

Press Abort in any moment to Abort the linking process. A


confirmation message appears.

When all Steps have been completed, a new row appears in the
Test Plans table of the Network Tree page corresponding to the
relay node to which the Test Plan has been linked.

4.2.7 DESCRIPTION OF GENERIC TEST MACROS


As described in previous paragraphs, at the time of the definition
of the Test Plan, only a few settings related to the macro are
defined. Then at the time of linking, other settings specific to the
relay are added. This is particularly true for the Generic Tests
Macros and they include some general Relay Settings such as the
DOC. MSE10015 REV. 6.5.2 Page 93/129

Nominal Values (current, voltage, frequency, vdc and so on), the


CT Side and specific settings for each of the Macro (Trip Contact
and relative Status and other specific parameters). The Vnom
parameter can be given in 3-phase values or 1-phase values. For
instance if the relays nominal voltage is 110V (ph-ph), setting
110V (with the selection 3-phase) or 63,51V (with selection 1-
phase) will be equivalent.
When linking a Test Plan that is made by one or more Macro of
the Generic Test module the following window appears.

At the top there is a General Relay Settings frame that contains


settings for the Relay. Then the list Generic Tests shows the
Macros that have been included in the Test Plan. For each of
these Macros the user must define the relative settings.

In this paragraph we describe these parameters in order to


understand how to set these macros. For each Macro there is a
description of the parameters to be set at the definition of the
Macro and at the linking of the Macro.
DOC. MSE10015 REV. 6.5.2 Page 94/129

Macro Name Prefault


Settings at
definition

When a Macro of the Generic Test module is


added to a Test Plan, a Prefault Macro must be
added first. This is to ensure that the instrument
will receive Prefault conditions for the correct
execution of tests. These initial conditions are the
Voltages, Currents, the frequency and the
Duration of the Prefalt.
Settings at When linking, apart from the Nominal Settings of
Linking the relay, the Prefault Macro does not add any
specific setting.

Macro Name Shot

A Shot defines the Voltages, Currents, the


frequency, the Time of the Prefault Tpre and the
Holt time THold.
The output menu allows to select to which
outputs the shot frequency should be applied.
DOC. MSE10015 REV. 6.5.2 Page 95/129

The Shot Type menu allows to choose the


Prefault, Fault, PostFault conditions.

At linking a Shot Macro, the user needs to define


the I/O Setup contact settings, optionally giving
also a Name to the contacts used. At least one
contact must be defined for the Macro; more
contacts can be used to set the Stop condition of
the Macro. Other parameters are: the Maximum
Time duration of the Shot and whether it is
necessary to use the Point on Wave (if so on
which phase and at which Angle) or the Absolute
Angles features.

Macro Name Ramp


DOC. MSE10015 REV. 6.5.2 Page 96/129

A Ramp is defined by initial conditions and the


actual ramp values. Initial Voltages and Currents
allows to set the start conditions while the Ramp
Type selector allows to choose which parameter
(V, phV, I, phI or Frequency) will ramp. As it can
be seen a ramp Macro can be executed only on
one parameter, to be chosen from the selector.

Then depending on the instrument it will be


possible to ramp one or more outputs, by
enabling the relative selector.

In this example only V1 and V3 will ramp with


the values defined in the relative columns.
Frequency, Output and Shot type have the same
meaning as for the Shot Macro.

At linking a Ramp Macro, the user needs to


define the I/O Setup contact settings, optionally
DOC. MSE10015 REV. 6.5.2 Page 97/129

giving also a Name to the contacts used. At least


one contact must be defined for the Macro; more
contacts can be used to set the Stop condition of
the Macro. Other parameters are: the Maximum
Time duration of the Ramp and the Nominal
Time, that represents the Operating Time of the
Relay and is used for correct timing calculations.

Macro Name Undervoltage and OverVoltage

Undervoltage and Overvoltage Macros have the


same initial settings: a Test Name to identify the
Test, the Search Algorithm of the voltage
threshold and the Fault on which to execute the
search.
The Search Algorithm defines the method used to
find the threshold and can be:
Delta Ramp: the threshold will be determined by
consecutive shots increasing the voltage (or
decreasing depending on the Macro) until it is
found.
Ramp: the threshold will be determined by
ramping the voltage until the threshold is found.
Go / No go: the threshold is determined by
executing a shot over the nominal threshold level
and one shot under the nominal threshold level
to verify the Trip /No trip condition.

At linking a UnderVoltage or OverVoltage Macro,


the user needs to define the I/O Setup contact
settings, optionally giving also a Name to the
DOC. MSE10015 REV. 6.5.2 Page 98/129

contacts used. At least one contact must be


defined for the Macro; more contacts can be used
to set the Stop condition of the Macro. Other
parameters are: the Nominal Threshold (always
in phase-neutral values) the Operating Time of
the Relay and the Maximum Error accepted: it
will be used to determine the Pass/Fail result of
the Macro.
If the Search Algorithm set for the Macro is the
Go /No go, the two shots will be executed at
Nominal Threshold Maximum Error and the
Pass/Fail will be determined by a Trip/no Trip at
these values.

Macro Name Underfrequency and Overfrequency

Underfrequency and Overfrequency Macros have


the same initial settings: a Test Name to identify
the Test and the Search Algorithm of the
frequency threshold. The Search Algorithm
defines the method used to find the threshold
and can be:
Delta Ramp: the threshold will be determined by
consecutive shots increasing the frequency (or
decreasing depending on the Macro) until it is
found.
Ramp: the threshold will be determined by
ramping the frequency until the threshold is
found.
Go / No go: the threshold is determined by
executing a shot at frequency higher than the
nominal and one shot at frequency lower than
nominal threshold to verify the Trip /No trip
condition.
DOC. MSE10015 REV. 6.5.2 Page 99/129

At linking a UnderFrequency or OverFrequency


Macro, the user needs to define the I/O Setup
contact settings, optionally giving also a Name to
the contacts used. At least one contact must be
defined for the Macro; more contacts can be used
to set the Stop condition of the Macro. Other
parameters are: the Nominal Threshold F< (or
F>), the Operating Time of the Relay and the
Maximum Error accepted: it will be used to
determine the Pass/Fail result of the Macro.
If the Search Algorithm set for the Macro is the
Go /No go, the two shots will be executed at
Nominal Threshold Maximum Error and the
Pass/Fail will be determined by a Trip/no Trip at
these values.

Macro Name Delta / Delta t

The Delta F / delta T Macro has only an optional


Test Name parameter to identify the Test. The
search algorithm is automatically defined as a
consecutive list of frequency ramps at delta
frequency values close to the nominal threshold.
DOC. MSE10015 REV. 6.5.2 Page 100/129

At linking a Delta F / Delta t Macro, the user


needs to define the I/O Setup contact settings,
optionally giving also a Name to the contacts
used. At least one contact must be defined for
the Macro; more contacts can be used to set the
Stop condition of the Macro. Other parameters
are: the start Frequency F Start, the nominal
threshold df/dt, the Operating Time of the Relay
and the Test Range () which is a measure of
the precision of the search. Optionally it is
possible to include a limit on the minimum
frequency achieved F< so that the test does not
go beyond this condition.

Macro Name Reverse Power

The Reverse Power Macro has only an optional


Test Name parameter to identify the Test. The
search algorithm is automatically defined as a Go
/ No Go test at values close to the Nominal
reverse Power threshold.
DOC. MSE10015 REV. 6.5.2 Page 101/129

At linking a Reverse Power Macro, the user needs


to define the I/O Setup contact settings,
optionally giving also a Name to the contacts
used. At least one contact must be defined for
the Macro; more contacts can be used to set the
Stop condition of the Macro. Other parameters
are: the nominal Reverse Power P< express in
%, the Operating Time of the Relay and the
Maximum Error. The search will be performed by
executing two shots at P< Maximum Error and
the Pass/Fail will be determined by a Trip/no Trip
at these values.

Macro Name Reverse Current

The Reverse Current Macro has only an optional


Test Name parameter to identify the Test.

At linking a Reverse Current Macro, the user


needs to define the I/O Setup contact settings,
optionally giving also a Name to the contacts
used. At least one contact must be defined for
the Macro; more contacts can be used to set the
DOC. MSE10015 REV. 6.5.2 Page 102/129

Stop condition of the Macro. Other parameters


are: the nominal Reverse current ratio Ratio = I-
/I+ express in %, the Operating Time of the
Relay and the Maximum Error. The search will be
performed by executing two shots at Ratio
Maximum Error and the Pass/Fail will be
determined by a Trip/no Trip at these values.

Macro Name Reverse Voltage

The Reverse Voltage Macro has only an optional


Test Name parameter to identify the Test.

At linking a Reverse Voltage Macro, the user


needs to define the I/O Setup contact settings,
optionally giving also a Name to the contacts
used. At least one contact must be defined for
the Macro; more contacts can be used to set the
Stop condition of the Macro. Other parameters
are: the nominal Reverse current ratio Ratio = V-
/V+ express in %, the Operating Time of the
Relay and the Maximum Error. The search will be
performed by executing two shots at Ratio
Maximum Error and the Pass/Fail will be
determined by a Trip/no Trip at these values.
DOC. MSE10015 REV. 6.5.2 Page 103/129

4.3 Execution of Test Plans


A Test Plan that has been previously saved and associated to a
relay can be executed in two ways, producing the same result:
a) By choosing the menu item Relay Test Plan Editor Run in
the Program Control page of TDMS

A new window is opened.

As it can be seen, it is organized in two main pages: List


and Test Plan. The List page contains a list of all the Test
Plans that are ready to be executed. The Test Plan page
shows the Test Plan structure when a Test Plan is chosen
from the list.
Since we have created only one Test Plan, only one row is
shown in the above picture.
In time, the user will create and run more and more Test
Plans, therefore this window organizes the Test Plans
ready for execution depending on their position in the
Network Tree. It also shows the Date when the Test Plan
was linked to the Relay.
To run a Test Plan, double-click on the relative row; the
DOC. MSE10015 REV. 6.5.2 Page 104/129

Test Plan is loaded in the List page.


It is always possible to return to the List of Test Plans and
select a different Test Plan by clicking on the List page.

b) By Selecting the appropriate row in the table Test Plans of


the relay node in the Network Tree page of TDMS.

By right-clicking on a row of the Test plans table, a menu


appears.

This menu is described in more details in the relative


paragraph. Select the Execute Test Plan item to run the
Test Plan. The Test Plan will be loaded in the Test Plan
page of the Test Plan Execution window.

Once the Test Plan is loaded in the Test Plan page, press the Run
button to start the Test Plan Execution.
DOC. MSE10015 REV. 6.5.2 Page 105/129

Prior to the Execution, the user can also define which tests should
or should not be performed by selecting/unselecting the relative
rows in the grid.

This allows to run the complete Test Plan or only a subset of it as


required.
During the execution the window changes appearance to inform
the user of the test progress. A Stop button appears and can be
used to Stop the execution of the Test Plan in any moment, while
all the other controls are disabled. The box below the Run and
Stop buttons describe the current status of the execution: the
Step currently being executed and a description of the software
module that is handling the execution.
DOC. MSE10015 REV. 6.5.2 Page 106/129

If for some reasons the user chooses to Stop the execution before
it automatically concludes, a confirmation message will appear.

In the meantime, as described in the box, a module is taking care


of the Test Execution. In particular, the Distance module handles
this first Step of the Test Plan. Although the following pictures
show the behaviour of the Distance 21 module, it should be noted
that the sequence of events and the description is valid for all the
Steps of the Test Plan, regardless of the module that handles
them.

a) The window shows only the parameters that can be


modified.
DOC. MSE10015 REV. 6.5.2 Page 107/129

It is not possible to add other tests, to open other results


or to save the results in a different file. The saving of the
results is performed automatically by TDMS once the user
continues to the next step of the Test Plan. The test table
is filled with the tests that correspond to the Macro
functions added to this Test Plan. At this stage is also
possible to define the Hardware Status of the trip contacts.
The Start, Stop and Reset buttons handle the execution of
the tests. Press the Start button to execute the tests.
Tests can be repeated by choosing the Repeat selected
tests menu item of the test table.

b) A box describes the status of the execution.

When all the tests have been performed, the box flashes
to highlight the next action to be taken: press the
Continue button to go to the next step of the Test Plan or
to conclude the execution if this step is the last step in the
Test Plan. A confirmation message appears.
DOC. MSE10015 REV. 6.5.2 Page 108/129

All tests in this step of the Test Plan must be executed. A


message appears if the tests have not been completed.

Press Abort in any moment to Abort the execution. A


confirmation message appears.

When all Steps have been completed, a new row appears in the
Test Results table of the Network Tree page corresponding to the
relay node to which the Test Plan has been executed.
DOC. MSE10015 REV. 6.5.2 Page 109/129

As it can be seen in the above picture, there is a difference


between a test imported in TDMS and a Test Plan executed by
TDMS: the Original Filename column shows the name of the Test
Plan instead of the name of the database file that has been
imported, and the Program column shows the type Test Plan. It
should be noted that this row summarizes all the results obtained
by running all steps of the Test Plan.
DOC. MSE10015 REV. 6.5.2 Page 110/129

5. SYSTEM REQUIREMENTS
Hardware and software requirements of the PC where TDMS is
installed are the followings.

5.1 Hardware requirements


1) Micro: PENTIUM III or more.
2) RAM: minimum 256 Mbytes.
3) Hard disk.
4) Mouse or trackball.
5) VGA 1025 x 768, 256 Colors display.
6) Interface: USB or RS232.

5.2 Software requirements


The program runs with any one of the following software.
1) WINDOWS 98 SE.
2) WINDOWS NT.
3) WINDOWS ME.
4) WINDOWS 2000.
5) WINDOWS XP.
6) WINDOWS VISTA (32bit).
A mandatory requirement to allow TDMS to work is that the
Microsoft .NET Framework version 1.1 should be installed already
on the PC and updated to the latest release.
A redistributable version of the framework is included in the
software package. In case the .NET Framework is not present on
the PC, the installation of TDMS cannot be completed. In case of
such an event, install the .NET Framework, prior to the
installation of TDMS.
DOC. MSE10015 REV. 6.5.2 Page 111/129

6. SOFTWARE INSTALLATION

6.1 Introduction

Before proceed with installation, you must uninstall the


previous version of TDMS.

If the Operating system is WINDOWS 7, please refer to


APPENDIX 1 before continuing.

If you have installed the Avira Avir antivirus program,


please disable it before the installation, and enable it at
the end: it would inhibit the installation because of a false
virus problem.

Insert the disk in the CD-Rom drive and open it: you will see the
following content.

If this is the first time you install TDMS, and you dont have
installed Microsoft.net Framework, double click on dotnet.fx to
install it: the following confirmation window is opened.

Press yes: the Framework program is installed.

NOTE: If the program was actually already installed, the following


warning message is displayed.
DOC. MSE10015 REV. 6.5.2 Page 112/129

In this instance, press OK and proceed.

Once Framework is installed, select the 32 bits or the 64 bits


directory, as per your WINDOWS operating system. As you do,
the following files are accessible.

Double click on SETUP.EXE: the following dialogue window is


opened.
DOC. MSE10015 REV. 6.5.2 Page 113/129

A few seconds after, the program opens the following two


windows:

If you press Next>, the following window appears:


DOC. MSE10015 REV. 6.5.2 Page 114/129

If you uninstalled the previous version of TDMS, or if this is the


first installation, press Next> to continue. The following window
appears:

Accept, and then press Next> to continue; the following window


is displayed.
DOC. MSE10015 REV. 6.5.2 Page 115/129

After reading, press Next: the following window is opened.

You can load company name and owners name. It is also


DOC. MSE10015 REV. 6.5.2 Page 116/129

possible to determine which user will be able to use the software


on the target computer. From this moment the installation starts.

Next window is the following.

During installation, if you have the Window XP operating system,


this message appears twice. Press Continue in order to
complete the installation.
DOC. MSE10015 REV. 6.5.2 Page 117/129

On the Windows Vista operating system this message appears


twice. Select Install this driver software anyway in order to
complete the installation.

Files are copied, the C:\XTEST directory is created with all related
subdirectories. The Windows operating system is modified to
allow the software to run.

If the C:\XTEST directory already exists, the program over-writes


files with the same name, but does not delete other files in the
directory.

This process requires a few moments; at the end of it, the


following window is opened.
DOC. MSE10015 REV. 6.5.2 Page 118/129

There are three tabs, one for each range of products. You can
select the type of product that you have: if you have more types,
select the default one for each type of product.

For many test sets there are more than one connection available:
select the preferred one. If you choose RS232, set also the serial
port to be used to control the test set. Be careful not to conflict
with other programs.

If the user has only one type of test set, we suggest selecting it
and leaving unchecked the Ask model to user option. For the
automatic relay test sets, the choice is among the following
devices.
. UTB (MICR-4 control card);
. UTS 8 bit (MICR-4 control card);
. UTS 32 bit (MICR-H control card);
. ART/3: it is to be used also for UTB with the 32-bit (MICR-H)
control card;
. DRTS: it includes also BER3;
. ART/100 (single phase);
. DRTS.3;
. DRTS.6;
DOC. MSE10015 REV. 6.5.2 Page 119/129

. RTS3 or DRTS3 PLUS;


. DRTS66: it includes also DRTS64 and DRTS34.

The second tab, Secondary injection and transformers test sets,


has two selections.

The third tab, Circuit Breaker Analyzers, has the same selection
for two test sets.
DOC. MSE10015 REV. 6.5.2 Page 120/129

The Choose Model at startup option is for the case that the user
has more than one model: the program allows selecting the type
of instrument as the program is started, otherwise it connects
directly to the instrument.

It is always possible to run the SetComm program and modify


these selections if needed.
If the RS232 port is selected, the program also asks on which
serial port the communication with the instrument will take place.
If the USB port is selected, the question is not applicable.

NOTE: if the RS232 interface is not available on your PC, it is


possible to use an USB to RS232 converter (such as the model
UC232A of the manufacturer MAXXTRO). Note that these
converters are supported by WINDOWS 98 REV. D up.

After choosing the communication port, the following window is


displayed for a very short time
DOC. MSE10015 REV. 6.5.2 Page 121/129

And then, the installation ends with the following window.

NOTE: If you have installed TDMS on a new computer, it is


appropriate to install and identify at least one printer, otherwise it
will not be possible to preview the reports in any program.

NOTE: the TDMS page can be cut: this depends upon the display
settings. To fix the problem, go to the Control panel, and select
the screen. Next, select Modify resolution, and select the
resolution of 1366x760 pixel, or more. In the Screen general
properties, the dot density must be set as 96 DpI.

6.2 USB software driver installation for DRTS or CBA1000

After the program has been installed, if you want to use the USB
interface, first of all you have to be the Administrator of the PC,
DOC. MSE10015 REV. 6.5.2 Page 122/129

otherwise the USB driver will not be installed. Then, connect your
PC to the test set: as the USB interface is sensed, a different
behavior appears depending on your operating system:
1) Windows 2000/Windows Vista: the software driver may be
automatically installed.
2) Windows XP: the following new hardware wizard starts

Choose No, not now option and press Next>. The following
window is displayed.

Press Continue button: the installation is completed; the test


DOC. MSE10015 REV. 6.5.2 Page 123/129

set can be controlled by the USB interface.


During the installation of the driver, a message like "driver not
Microsoft certified" or something similar may appear; if you
refuse to install the driver, also our USB driver will not be
installed

6.3 Troubleshooting the USB software driver installation


NOTE: following images refer to Windows Vista operating system.
For others operating system screenshots are similar.
The fact that the installation of driver software successfully
ended, is confirmed by the following window (you can open
Computer Management program right-clicking My Computer icon
an selecting Manage voice)

Otherwise, if there is an installation problem, the following error


window is displayed.
DOC. MSE10015 REV. 6.5.2 Page 124/129

The wrong installation process is confirmed by the alert !sign in


Computer Management window.

To troubleshoot this problem, right click Unknown device icon and


select Update Driver Software option
DOC. MSE10015 REV. 6.5.2 Page 125/129

The following window appears. Select Browse my computer for


driver software option.

The following window will appear. For DRTS family instruments


DOC. MSE10015 REV. 6.5.2 Page 126/129

select C:\xtest\Isa_usb_drivers folder. For CBA family


instruments select C:\xtest\CBA_usb_drivers folder. Press
Next button.

The following window will appear. Select Install this driver


software anyway option
DOC. MSE10015 REV. 6.5.2 Page 127/129

If Windows successfully installs driver software, this message


finally appears.
DOC. MSE10015 REV. 6.5.2 Page 128/129

7. WINDOWS VISTA/7

WINDOWS VISTA/7 has introduced some different file handling,


that impose a simple additional operation.

BEFORE the program installation, on the CD-ROM


installation disk, reach with the mouse the file SETUP.EXE,
and right click on it: the following window is opened.

Select the option Execute as administrator, then start


the installation program, and execute the installation as
explained in the manual.

AFTER the program installation, reach the TDMS icon with


the mouse, and right click on it: the following window is
opened.
DOC. MSE10015 REV. 6.5.2 Page 129/129

Select Advanced properties: the following window is


opened.

Last, select Execute as administrator: the selection will be


memorized, and used as you start the program.

Вам также может понравиться