user’s manual hv/collect*2 - abb...[drive]:\sc\lib4\base\bbone\use\path4_s11.txt 14 1mrk 511...

$: User’s Manual HV/Collect*2 - ABB...[drive]:\sc\lib4\base\bbone\use\path4_s11.txt 14 1MRK 511 022-UEN*2.2-01 System setup Installation Instructions 2.3 Installation of Disturbance$
User’s ManualHV/Collect*2.2

Contents

Introduction 3

Instructions 9

Technical descriptions 25

References 39

Appendix 41

1

1

About this manual

This is a software manual for the Disturbance Collector software

Document number: 1MRK 511 022-UEN

Version: 2.2

Revision: 01

Issue date: May 1999

Data subject to change without notice

We reserve all rights to this document, even in the event that a patent is issued and a different commercial proprietary right is registered. Improper use, in particular repro-duction and dissemination to third parties, is not permitted.

This document has been carefully checked. If the user nevertheless detects any errors, he is asked to notify us as soon as possible.

The data contained in this manual is intended solely for the product description and is not to be deemed to be a statement of guaranteed properties. In the interests of our customers, we constantly seek to ensure that our products are developed to the latest technological standards.

As a result, it is possible that there may be some differences between the HW/SW product and this information product.

Author´s address:

ABB Automation Products ABSubstation Automation DivisionS-721 59 VästeråsTel: +46 21 34 20 00Fax: +46 21 14 69 18Internet: http://www.abb.se/net

© ABB Automation Products AB 1999

About this manual

IntroductionIntroduction

The chapter "Introduction"This chapter introduces you to the HV/Collect software

Preface .....................................................................................................................7

Abbreviations and definitions ...............................................................................7

Font conventions.............................................................................................8Product overview ............................................................................................8System overview.............................................................................................9

3

Introduction

4

Abbreviations and definitions

Preface

oft-

DA

s,

Introduction

Preface

Welcome to the Disturbance Collector User’s Guide. The Disturbance Collector sware is designed to provide a flexible tool for collection of disturbance files.

To be able to understand this document the user should be familiar with MicroSCAand MicroLIBRARY.

The function is designed and created by ABB Automation Products AB in VästeråSweden.

1 Abbreviations and definitions

Disturbance An anomaly in the data of the supervised equipment. Distur-bances are recorded by manual initiation or automatically if they meet pre-set triggering conditions.

Disturbance recorder The built in disturbance recorder in REx 5xxFTP File Transfer ProtocolLIB520 High Voltage MicroLIBRARYLAN Local Area NetworkLON Local Operating NetworkNFS The Network File System (NFS) allows a client node to per-

form transparent file access over the network. By using NFS, a client node operates on files residing on a variety of servers and server architectures, and across a variety of operating systems.

OS Operating System. Core software for a PC.PANORAMA The total, coordinated protection and control concept. Regis-

tered trademark of ABB Automation Products AB.RAS Remote Access ServerRECOM The RECOM software is used for collecting recordings from

disturbance recorders.Recording All the available information about a disturbance from one

disturbance recorder

RESDA An expert system for disturbance analysis. RESDA runs in Windows 3.1.RESDA version > 1.0 is assumed in this document.

RESDA log file The log file contain file references to uploaded recordings during an auto poll for a unit.

REVAL Disturbance Evaluation Program. REVAL runs in Windows OS.

REVAL-format The file format used by the REVAL evaluation program. The disturbance data is stored in two files, the header file and the data file.

51MRK 511 022-UEN*2.2-01


Preface

Introduction

s and

REVAL log file The log file contain file references to uploaded recordings during an auto poll for a unit.

SCS Substation Control System. A system for monitoring and controlling a complete substation, i.e. the MicroSCADA in this document.

SMS Substation Monitoring System. A collection of programs for monitoring protection units and handling of disturbance recordings.

TCP/IP Transmission Control Protocol/Internet Protocol.Unit Throughout this document the word “unit” refers to the

REx5xx terminal in which the disturbance recorder is located.

1.1 Font conventions

Normal text is written with this font and size.

SCIL CODE, SCIL PROGRAMS AND FILE NAMES ARE WRITTEN WITH THIS FONT AND SIZE.

1.2 Product overview

Disturbance recording is a very effective tool for the operating and design personnel to analyse the performance of the power system and related equipment during and after a major disturbance. By promptly detecting any problems and initiating the corrective measures, maximum operating reliability and availability of the power system is achieved. Disturbance recording also improves the understanding of the behaviour of the power system and the associated equipment, contributing to design improvements of future installations.

The complete disturbance recording and evaluation system consists of REVAL, RESDA and Disturbance Collector programs together with hardware for interconnect-ing the disturbance recorders and protection terminals in a local network, in either a ‘star’ or a ‘loop’ configuration.

This document describes only the functions of the Disturbance Collector programthe interface to REx5xx.

MicroSCADA software available for Disturbance Collector:

• HV/COLLECT - Software module for disturbance collector.

6 1MRK 511 022-UEN*2.2-01


Preface

Introduction

g-sers

1.3 System overview

The “Disturbance Collector” function is a part of LIB520 in the MicroSCADA. In Fiure 1 the “Disturbance Collector” function is shown as a part of a system. This Uguide covers only the functionality of the “Disturbance Collector” function.

Fig. 1 Disturbance Collector system overview

A) The MicroSCADA file system is mounted, using NFS, in the PC, i.e. the MicroSCADA file system will be accessed as just another disk in the PC.

B) Remote communication, e.g. RAS. (not within the scope of this document to determine which technical solution to use).

C) The disturbances are collected using RECOM. If both communication ports of the terminal are used for disturbance transmission, a collision can occur. E.g. if the SMS user selects disturbance No 1, the SCS user selects disturbance No 3, then the SMS user reads first part of disturbance 1 and the whole disturbance No 3 with a corrupt disturbance file as a result.Consequence: Disturbance collection with RECOM can be used together with MicroSCADA, but with the risk of collisions.

N E T

MicroSCADAScreen

Mouse

Keyboard

(Console)

2)

Communication protocols1) LAN - TCP/IP, NFS2) SPA

Windows/REVAL

3) LON

Windows/RESDA

MM(Windows/REVAL)(Windows/RESDA)

C

A

(Windows/RECOM)(Dos/SMS-BASE)

1)M

M

Windows/REVALWindows/RESDA

B4)

DisturbanceCollector

PCLTA

3)

4) FTP, RAS or similar

71MRK 511 022-UEN*2.2-01


Preface

Introduction

8 1MRK 511 022-UEN*2.2-01

InstructionsInstructions

The chapter "Instructions"This chapter instructs you how to install the Disturbance Collector software and how to perform some typical tasks when to use the software.

Installation .............................................................................................................13

System requirements .........................................................................................13

Installation ..........................................................................................................14

Installation of MicroSCADA software ............................................................15Installation of the Disturbance Collector software.........................................15Installation of Disturbance Collector library function .....................................16

System setup .....................................................................................................16

Performing certain operations.............................................................................18

Start the automatic poll sequence......................................................................18

Show list of stored recordings.......................................................................20Identify new recordings .................................................................................21Start a manual uploading ..............................................................................23Clear all recordings in the recorder...............................................................24Change of password .....................................................................................24Diagnosing errors..........................................................................................25Communication problem ...............................................................................25Terminal busy ...............................................................................................26

9

Instructions

10

System requirements

Installation

r’

Instructions

Installation

Before using Disturbance Collector the software has to be installed on the hard disk of the MicroSCADA computer.

1 System requirements

In order to operate, the software module Disturbance Collector poses the following requirements on its environment.

At the protection terminal end:

Remote communication:

• The terminal with installed “remote communication’ and ‘disturbance recordeoptions.

The MicroSCADA PC:

• 64 MB RAM

• 1 GB disk

• Operating system Windows/NT 4.0 or later

• MicroSYS revision 8.4.2 or later

• MicroTOOL revision 8.4.2 or later

• MicroNET revision 8.2D or later

• PCNet revision 8.4.2 or later

• LIB500 revision 4.0.2 or later

• LIB510 revision 4.0.2 or later

• hv/rel501 version 2.2-00 One module/type of installed

Supported types

REL 501 version 1.2

REL 511 version 1.2

REL 521 version 1.2

REL 531 version 1.2

REL 551 version 1.2

REL 561 version 1.2

REB 551 version 1.1

REC 561 version 1.1

RET 521 version 2.0 or later

REx 5xx version 2.0

111MRK 511 022-UEN*2.2-01

Installation

Installation

Instructions

s

d e

terminal is required.

• hv/rel511 version 2.2-00 “





• hv/reb551 version 2.2-00 “

• hv/rec561 version 2.2-00 “

• hv/ret521 version 2.0-00 “

• hv/ret521 version 2.1-00 “

• hv/rex500 version 2.0-01 “

Note. All HV/rex5xx software are included in LIB 520 as separate packages.

The HV/collect package:

• 700 KB disk

2 Installation

Installation of the Disturbance Collector software has two meanings.

1; Installing the software:

• Installation of the Disturbance Collector software module means copying filefrom the CD to the hard disk.

2; Installing the library function:

• When installing the HV/REx5xx library function the command procedures antime channels needed by the Disturbance Collector function are created. Se“Installation of Disturbance Collector library function” on page 14.

!Important Note!In order to avoid problems, it is recommended not to have the MicroSCADA active during the installation.

12 1MRK 511 022-UEN*2.2-01

Installation

Installation

Instructions

2.1 Installation of MicroSCADA software

Before the installation of the Disturbance Collector can take place, the user must make sure that the MicroSCADA software is already installed on the PC.

2.2 Installation of the Disturbance Collector software

To install from the disk-drive to the hard disk, please follow the steps below:

1 Start up the File Manager (Explorer)

2 Run [drive]:\L520_402.EXE found on the CD.

3 Follow the instructions on the screen

The Disturbance Collector is now properly installed on the hard disk of the PC.

4 Start the MicroSCADA

The software is now installed in the following directories:

[drive]:\sc\lib4\smod\relays\rex5xx\collector\inst[drive]:\sc\lib4\smod\relays\rex5xx\collector\lang0[drive]:\sc\lib4\smod\relays\rex5xx\collector\use

The following files are updated by the installation:

[drive]:\sc\lib4\base\bbone\use\path4_s11.txt

131MRK 511 022-UEN*2.2-01

System setup

Installation

Instructions

te e

ng ,

2.3 Installation of Disturbance Collector library function

The Disturbance Collector is not a library function itself. It is an integrated part of the HV/REx 5xx library function.

When you install the HV/REx 5xx library function make sure that you select the DIS-TURBANCE RECORDER option, to be able to use the Disturbance Collector, see ref-erence. [4].

To be able to use the automatic uploading function, you have to create a button some-where in a menu or picture with the following SCIL code in the U_ACTIVATE named program.

@SDC_AUTHORIZATION_GROUP=”RELAY_ENGINEER”!WIN_NAME SRU_ADCOLA!WIN_POS SRU_ADCOLA (15,10)!WIN_PIC SRU_ADCOLA S_USE/SRU_ADCOLA!SHOW SRU_ADCOLA

3 System setup

REVAL/RESDA

The uploaded recordings can be analysed with a tool like REVAL or RESDA.

There are a number of ways to access the uploaded recordings from such a tool. One way is to have REVAL or RESDA running on a separate PC and then mount, using NFS, the disk, in the MicroSCADA PC, where the recording files are stored.

File -> Open... In the Open dialogue you just select the NFS mounted disk from the “Unit:” list (not to be confused with the definition of unit in this document). Navigathrough the directories to the terminal unit directory of your interest, then select thREVAL header file that you want to analyse.

In REVAL an automatic printout function is available. Before this is properly workitogether with HV/COLLECT the default path, where REVAL finds necessary filesmust be changed from [drive]:\SMS\..\RECOM to [drive]:\SC\LIB4\SMOD\RELAYS\REX5XX\COLLECTOR. This modifica-tion is made in [drive]:\REVAL\REVAL.INI tag RECOM_DIR.

14 1MRK 511 022-UEN*2.2-01

System setup

Installation

Instructions

!Note!Important notes concerning automatic printout from REVAL:

To get this function working properly it is of great importance that the necessary print-ers are defined for the MICROSCADA user. Otherwise REVAL is not able to detect default printer definitions which is a must.

If other location for REVAL than default [drive:]\sms\reval, is used, it is necessary to change the REVAL path definition within the HVCollect. This is made by edit two vari-ables @SDC_REVAL_LOC_PATH in file [drive:]\sc\lib4\smod\rex5xx\collec-tor\use\sru_dccom.txt to the correct path.

If the auto printout function is used the @SDC_REVAL_AUTO_PRINT should be set to TRUE.

151MRK 511 022-UEN*2.2-01

Start the automatic poll sequence

Performing certain operations

Instructions

in


On the following pages, a number of examples will be given on how to use the Distur-bance Collector. The main functions will be explained and exemplified.

For further information on the different commands and possibilities, See “Tutorial” on page 28.

In this chapter every used command is explained in text and figures.

4 Start the automatic poll sequence

1 Bring up the station picture

2 Press the Automatic Uploading button.

The one you have created according to the installation chapter, e.g. in the mamenu.

Fig. 1 Press Automatic uploading

Trends >Reports >Accessories >Network Map...Automatic Uploading......Previous picture

End session

Main

16 1MRK 511 022-UEN*2.2-01



Instructions

3 Activate the automatic polling

Fig. 2 Press “Activate auto poll”

4 Confirm the operation.

Fig. 3 Activate the Automatic polling by confirming (Yes).

171MRK 511 022-UEN*2.2-01



Instructions

4.1 Show list of stored recordings

1 Bring up the Automatic Uploading window

Fig. 4 Press the “More” and “Recordings list...” button

2 The list is displayed

Fig. 5 List of recordings in the station

18 1MRK 511 022-UEN*2.2-01



Instructions

4.2 Identify new recordings


2 Now press the button for the terminal with disturbance recorder for which you want to upload a recording.

This will bring up the “SPA Tool” window.

Fig. 6

Fig. 4.7 SPA Tool window

191MRK 511 022-UEN*2.2-01



Instructions

in

3 Press the Relay button (in this example, “REL 511 Z <”)

4 Press the “Upload recordings...” button in the “Transfers” menu.

5 The number of new recordings is shown in the “Manual Upload” window.

Bring up the “Unit recordings list” to get more information about the recordingsthe unit

Fig. 8 Press “Unit Recordings List...”

6 The list contains the fields like, “Date”, “Time”, “Sequence number” and “Trig reason”

Fig. 9 Unit recordings list

960529 001 NO 12:30:12.257 MANUAL960529 000 NO 11:37:56.128 I>>I0960528 003 YES 15:23:41.563 MANUAL

20 1MRK 511 022-UEN*2.2-01



Instructions

ill

4.3 Start a manual uploading


2 Now press the button at the disturbance recorder for which you want to upload a recording.

This will bring up the “SPA Tools” window.

3 Press the Relay button. This will update the menus.

4 Press the “Upload recordings...” button in the “Transfers” menu.

5 Wait until the “Number of new recordings” has been evaluated.

If there are any new recordings in the unit then the key “Upload Recordings” wturn from dimmed to normal.

6 Press the “Upload Recordings” button.

Fig. 10 Press “Upload recordings”

7 Confirm the operation.

Fig. 11 Start the manual uploading by confirming (Yes).

211MRK 511 022-UEN*2.2-01



Instructions

4.4 Clear all recordings in the recorder


2 Now press the button at the disturbance recorder for which you want to upload a recording. This will bring up the “SPA Tools” window.

3 Press the Relay button. This will update the menus.

4 Press the “Recorder Tool...” button in the “Tools” menu.

5 Wait until the “Recorder data” has been evaluated.

If there are any recordings in the unit then the key “Clear Recordings” will turnfrom dimmed to normal.

6 Clear the recordings in the unit.

Fig. 12 Press the “Clear Recordings” button

7 Confirm the operation

Fig. 13 Clear all recordings by confirming (Yes)

4.5 Change of password

The Disturbance Collector has no password handling of its own. Instead, activities are depending on the users authority level in the MicroSCADA. All users with authority level 1 or higher have access to the Disturbance Collector activities.

New MicroSCADA users can only be added by the MicroSCADA system manager.

22 1MRK 511 022-UEN*2.2-01



Instructions

r-

CIL

nty hese

4.6 Diagnosing errors

When errors occur, the system produces error messages which are shown in the status bar at the bottom of the windows. The error messages are composed of one or two sta-tus codes, and possibly a SCIL statement or expression.

The meaning of these codes are described in S.P.I.D.E.R MicroSCADA The program-ming language SCIL and the S.P.I.D.E.R MicroSCADA User’s Manual. See “Refeence publications” on page 39.

The error messages in the example below have the following meaning:

883 16303 TXRX_STRN=STA8:SME(%TXRX_SAR..%TXRX_EAR)

SCIL statement in command procedure

RMTP_NET_NOT_RUNNING

PICO_SCIL_ERROR_IN _CALLBACK_SEQUENCE

In other words:

You have tried to read settings from a terminal but the NET is not running. The Sstatement shown comes from the command procedure that handles the reading. Start the NET and try again.

A probable cause for these errors can be:

• The NET-program is not running.

• The terminal is not defined in the base system (SPANET, LON).

• The terminal is not defined in the DATA list (SRIO).

• The terminal has an other SPA address than defined in the MicroSCADA (SPANET, LON and SRIO).

• The fibre optic bus is broken.

• The terminal is faulty.

4.7 Communication problem

Errors have, in most cases, something to do with the communication. When the program does not get an answer from the unit within the time limit it does tweattempts to re-send the message. If the terminal still does not respond to any of tattempts there is a communication problem in the system.

A probable cause for these communication problems can be:

231MRK 511 022-UEN*2.2-01



Instructions

ets ndle me age. If tion

• The NET is running but the line that is used for this purpose is not in use.

• The terminal (slave) does not respond (SPANET, LON and SRIO)

4.8 Terminal busy

During communication with the terminal it sometimes happens that the terminal gbusy. This is a normal behaviour and it occur when the terminal has to much to hae.g. when SMS and the MicroSCADA is reading from the same terminal at the satime. In these situations the program makes twenty attempts to re-send the messthe terminal still does not respond to any of these attempts there is a communicaerror in the system.

A probable cause for terminal busy can be:

• Change of actual setting

• Change setting group

• Change configuration

• Clear Disturbance Report

• Select Disturbance Report

• If SMS and MicroSCADA are reading at the same time.

24 1MRK 511 022-UEN*2.2-01

Technical descriptionsTechnical descriptions

The chapter "Technical instructions"This chapter describes the Disturbance Collector software and its functionality.

Overview ............................................................................................................29

Functions............................................................................................................29

Tutorial ...............................................................................................................30

Manual Uploading .........................................................................................30Unit recordings list ........................................................................................32Automatic polling...........................................................................................33Set time between auto polls ..........................................................................35Station wide uploaded list .............................................................................36RESDA/REVAL Log Files .............................................................................37Recorder tool ................................................................................................38Auto poll in progress .....................................................................................40

25

Technical descriptions

26

Overview

ated

Technical descriptions

1 Overview

The purpose of the Disturbance Collector is to collect disturbances from disturbance recorders and save them as files on a hard drive for long time storage and evaluation.

Two files for each uploaded recording will be created, one header file yymmddss.reh and one data file yymmddss.rev where yymmddss = year, month, day and sequence number of the recording.

Both upload processes (manual and automatic) stores disturbances under the MicroSCADA directory structure in \apl\’application_name’\recorder\sdc, which isthe main storage directory for recording files. Subdirectories for each unit are creat run time and are named according to the unit name. E.g. \apl\apl_1\recorder\sdc\unit_2\95113001.reh and 95113001.rev.

2 Functions

• Recordings saved in REVAL format

• Generation of information files for RESDA

• Manual or Automatic uploading of recorder

• Automatic polling of recorder is time driven

• Station wide list of uploaded recordings

• Unit recordings list

Tools to operate recorder:

• Manual trig

• Clear indication LEDs

• Clear recordings

271MRK 511 022-UEN*2.2-01

Tutorial Technical descriptions

3 Tutorial

3.1 Manual Uploading

Fig. 1 Manual uploading dialogue

In this dialogue manual uploading of disturbance recordings can be made.

If there are no new recordings in the unit, then the Upload recordings button will be dimmed.

If there are no recordings at all in the unit, then the Unit recordings list button will be dimmed as well.

The Stop button will be dimmed as long as no uploading is in progress.

Fields

Unit The selected unit.

Number of new recordingsShows how many recordings that has been uploaded during this uploading session and the amount of new recordings in the unit mem-ory prior to this uploading session.

23c:\sc\apl\apl1\recorder\sdc\test_rec96053100.rev

28 1MRK 511 022-UEN*2.2-01


at

-at sys-

ill

m of al

ind ,

et

Number of data transfersUsed as an indication that the uploading is in progress by showing the number of data transfers that has been made.

Path Directory path for the disturbance files for this unit.

File Name of the file header for the disturbance that is currently being uploaded.

Buttons

Upload recordingsThe upload function has to be confirmed, so when pressing this button a confirmation box like the one shown in Figure 3.1 is displayed. An authority level >= 1 (operator) is required to upload recordings.

Stop The “Stop” button Stops the current uploading operation.

CloseClose this dialogue.

Unit recordings listThe “Unit recordings list” button brings up a list of all recordings thare stored in the unit.

Help Brings up the help information for this dialogue.

Confirm Dialogue Buttons

Yes Start the uploading. The Stop button will turn from dimmed to “normal”. The manual uploading function will upload all disturbances thhas been recorded. The uploaded recordings are stored in the filetem and the format is REVAL file-format. The maintenance of the files, i.e. deletion of old recording files, that are no longer needed, wbe done through the Windows NT file manager.

No Close the confirmation box, no uploading is activated.

Status texts

Below is a description of the texts that can show up on the status bar at the bottothe dialogue. Error or warning messages are displayed in yellow and informationmessages in black colour.

Checking number of new recordingsInformational text. Sending SPA messages to the terminal unit to fout how many new, not yet uploaded and stored in the file systemrecordings that are stored in the terminal unit.

Uploading recording dataInformational text. Sending SPA messages to the terminal unit to gall data for a disturbance recording to store in a REVAL data file.

291MRK 511 022-UEN*2.2-01


s hat

s/No.

Uploading recording headerInformational text. Sending SPA messages to the terminal unit to get all parameters that are needed to assembly the REVAL header file.

Communication errorError text. Communication with the terminal unit failed.

Recorder option not installedError text. Disturbance recorder option is not installed in the terminal unit.

Recorder not supported (“model”)Error text. Disturbance recorder option model in the terminal unit inot supported by this function, where “model” is the model name thas been fetched from the terminal unit.

3.2 Unit recordings list

Fig. 2 Unit recordings list dialogue

This is a list of all disturbance recordings within a specific unit.

Fields

Date The disturbance recording date, in format YYMMDD.

Seq. no The disturbance recording sequence number, 0..255.

Uploaded Indication whether the disturbance has been uploaded or not, Ye

Time The disturbance recording time, in format hh:mm:ss.sss.

Trig Trig reason.

960529 001 NO 12:30:12.257 MANUAL960529 000 NO 11:37:56.128 I>>I0960528 003 YES 15:23:41.563 MANUAL

30 1MRK 511 022-UEN*2.2-01


Buttons

Close Close this dialogue.


Status texts

Below is a description of the texts that can show up on the status bar at the bottom of the dialogue. Error or warning messages are displayed in yellow and informational messages in black colour.

Retrieving information about all disturbances in the unitInformational text. Sending SPA messages to the terminal unit to retrieve information, for presentation in the list, about all the distur-bance recordings that are stored in the terminal unit.


3.3 Automatic polling

Fig. 3 Automatic Uploading dialogue

311MRK 511 022-UEN*2.2-01


e.

.

ss).

-

d-i-

ity

til ing or-

The automatic polling is scheduled by a Time Channel object in the MicroSCADA.

The “Activate auto poll” button will be dimmed if automatic polling is already activ

The “Deactivate auto poll” button will be dimmed if automatic polling is not active

Fields

Current unit If automatic uploading is activated, then this field will show the name of the unit or if no unit is currently being polled then “<None>” will be shown.

Auto poll statusIf automatic uploading is activated, then this field shows the current status of the automatic uploading process (idle or in progre

Auto poll modeThis field shows the current mode of the automatic uploading (activated or deactivated).

Auto poll time periodThis field shows the time set for interval between polls, in format hh:mm.

Buttons

Activate auto pollIf auto poll is already active then this button will be dimmed. Whenyou have confirmed this function it will activate the automatic uploaing function. Subsequent polls will be executed at the interval specfied by the parameter “Auto poll time period”. All disturbance recorders that are defined in the MicroSCADA system for a stationand that are defined on the SPA/LON bus will be polled. An authorlevel >= 1 (operator) is required to activate auto polling.

Deactivate auto pollIf auto poll is already deactivated then this button will be dimmed. When you have confirmed this function it will deactivate the auto-matic uploading function, no subsequent polls will be executed unthe automatic uploading is activated again. If any automatic uploadwas “in progress” then it will be aborted by this command. An authity level >= 1 (operator) is required to deactivate auto polling.

More Brings up a list of more commands.



32 1MRK 511 022-UEN*2.2-01


-

Confirmation Dialogue Buttons

Yes This button will execute the selected operation (Activate/Deactivate auto poll).

No Cancels the confirmation.

More Buttons

Set poll timeThis button will bring up a small query box, inquiring the operator for a new time between auto polls.

Recordings listThe “Recordings List” button brings up a list of all uploaded recordings that are stored in the file system for the units in the station.

Log filesThe “Log Files” button brings up the “RESDA/REVAL Log files” dialogue with settings for log files.

3.4 Set time between auto polls

Fig. 4 Set time between auto polls dialogue

The default value for the time between auto polls is 30 minutes.

The formula below can be used as a guide to evaluating the time between auto polls for your specific system:

Auto poll time >= 15 + terminal units * 15 (minutes)

Fields

Hour Input field for hours between auto polls.

Minute Input field for minutes between auto polls.

331MRK 511 022-UEN*2.2-01


Buttons

Execute Close this dialogue and sets the new time between auto polls. An authority level >= 1 (operator) is required to set a new time between auto polls.

Cancel Close this dialogue and ignores the setting.


Status texts

Below is a description of the texts that can show up on the status bar at the bottom of the dialogue. Error or warning messages are displayed in yellow and informational messages in black colour.

A minimum of 30 minutes is requiredError text. The time between auto polls has to be set to at least 30 min-utes.

3.5 Station wide uploaded list

Fig. 5 Uploaded recordings in the station dialogue

This dialogue shows a list of all recordings that has been uploaded for this station.

Fields

Unit Unit name.

Date The disturbance recording date, in format YYMMDD.

Time The disturbance recording time, in format hh:mm:ss.sss.

34 1MRK 511 022-UEN*2.2-01


Buttons



3.6 RESDA/REVAL Log Files

Fig. 6 RESDA/REVAL Log Files dialogue

In this dialogue you can control the creation of log files for RESDA and REVAL. The log files, if they are to be created, will be stored in the same directory as the distur-bance files. The name of the log files will be RCM-RSD.nnn for RESDA log files and RCM-REV.nnn for REVAL log files, where nnn is an index number. The default value is to create both RESDA and REVAL log files.

Toggle Buttons

Yes (RESDA) If set, indicating that log files should be created for RESDA.

No (RESDA) If set, indicating that no log files should be created for RESDA.

Yes (REVAL) If set, indicating that log files should be created for REVAL.

No (REVAL) If set, indicating that no log files should be created for REVAL.

Buttons

Execute Close this dialogue and stores the new settings for REVAL and RESDA log files. An authority level >= 1 (operator) is required to change the settings.

Cancel Close this dialogue and ignores the setting.


351MRK 511 022-UEN*2.2-01


e

o- An lly.

3.7 Recorder tool

Fig. 7 Recorder tool dialogue

Fields


Date/time (unit)Shows the current date and time in the unit.

Number of new recordingsShows the number of new recordings in the unit, i.e. “not yet uploaded” as a part of all recordings that are stored in the unit.

Free recording memoryIndication of the amount of free recording memory in percent of thtotal recording memory.

Buttons

Manual trig Function for manually trigging. The triggering will be ignored if a prgressing disturbance recording exists in fault-time recording state.authority level >= 1 (operator) is required to trig a recording manua

36 1MRK 511 022-UEN*2.2-01


er-

m of al

ind ,

et

al

s hat

Clear RecordingsClear all recorded disturbances in the unit. An authority level >= 1 (operator) is required to clear recordings.

Clear indication LED’sClears the indication LED’s on the unit. An authority level >= 1 (opator) is required to clear indication LED’s.



Confirm Dialogue Buttons

Yes The “Recorder tool” functions follows the “select before execute” principle, i.e. this button will execute the selected function.

No Cancels the confirmation.

Status texts

Below is a description of the texts that can show up on the status bar at the bottothe dialogue. Error or warning messages are displayed in yellow and informationmessages in black colour.

Checking number of new recordingsInformational text. Sending SPA messages to the terminal unit to fout how many new, not yet uploaded and stored in the file systemrecordings that are stored in the terminal unit.

Reading recorder dataInformational text. Sending SPA messages to the terminal unit to gthe parameters that are shown in the dialogue.


Recorder option not installedError text. Disturbance recorder option is not installed in the terminunit.

Recorder not supported (“model”)Error text. Disturbance recorder option model in the terminal unit inot supported by this function, where “model” is the model name thas been fetched from the terminal unit.

371MRK 511 022-UEN*2.2-01


ng

ue.

is

em-

the

3.8 Auto poll in progress

Fig. 8 Auto poll in progress information dialogue

This information dialogue is shown when either:

• Automatic polling is in progress and you tried to activate the manual uploadidialogue.

• Automatic polling is in progress and you tried to start the recorder tool dialog

Fields


From Current unit where uploading is in progress or “<None>” if no unit currently being polled.

Number of new recordingsShows how many recordings that has been uploaded during this uploading session and the amount of new recordings in the unit mory prior to this uploading session.

Number of data transfersUsed as an indication that the uploading is in progress by showingnumber of data transfers that has been made.

Path Directory path for the disturbance files for this unit.

File Name of the file header for the disturbance that is currently being uploaded.

Buttons



38 1MRK 511 022-UEN*2.2-01

Reference publications

The following documents are related to this manual and the operation of the Distur-bance Collector function.

1 S.P.I.D.E.R MicroSCADA User’s Manual rev 8.4.1 or later

2 S.P.I.D.E.R MicroSCADA Programming Language SCIL rev. 8.4.1 or later

3 S.P.I.D.E.R MicroSCADA Object Description rev 8.4.1 or later

4 HV/REx5xx User’s Manual rev. 2.1

5 HV/REX500 User’s Manual rev. 2.0

6 HV/RET521 User’s Manual rev. 2.1

1MRK 511 022-UEN*2.2-00

References

39

40

Appendix

The chapter "Appendix"

Appendix................................................................................................................43

Application engineering information ...................................................................43

Text files........................................................................................................43Help files .......................................................................................................43

41

Appendix

42

Application engineering information

Appendix

Appendix

1 Application engineering information

1.1 Text files

File location: SMOD/RELAYS/REX5XX/COLLECTOR/LANG’L’

1.2 Help files

File location: SMOD/RELAYS/REX5XX/COLLECTOR/LANG’L’

Filename Description

SRU_ADCOL.TXT Automatic Uploading dialogue and status texts

SRU_IDCOL.TXT Automatic Uploading In Progress dialogue and status texts

SRU_MDCOL.TXT Manual Upload dialogue and status texts

SRU_TDCOL.TXT Recorder Tool dialogue and status texts

Filename Description

SRU_ADCOLA.HLP Automatic Uploading help texts

SRU_ADCOLB.HLP Uploaded Recordings In The Station dialogue help texts

SRU_ADCOLC.HLP Time Between Auto Polls dialogue help texts

SRU_ADCOLD.HLP RESDA/REVAL Log Files dialogue help texts

SRU_IDCOLA.HLP Automatic Uploading In Progress dialogue help texts

SRU_MDCOLA.HLP Manual Upload dialogue help texts

SRU_MDCOLB.HLP Unit Recordings List help texts

SRU_TDCOLA.HLP Recorder Tool dialogue help texts

43

Application engineering information

Appendix

44

Index

451MRK 511 022-UEN*2.2-01

Symbols.REH 27.REV 27

AAuthority level 29Automatic uploading 14, 27

CChecking number of new recordings 29Clear indication LEDs 27Clear recordings 27Close 29, 31Communication error 30, 31Confirm dialogue 29Confirmation dialogue 29

DDate 30Disturbance 5, 27, 29Disturbance Collection 7Disturbance Collector 6, 7, 11, 12, 13, 14, 27Disturbance recorder 5, 11, 27Disturbance recorder option 14Disturbance recording 5, 6, 28, 30, 31Disturbance recording time 30

EError text 30

FFile 29FTP 5

HHelp 29, 31HV/COLLECT 6

IInformational text 29Installing the library function 12Installing the software 12

LLAN 5LIB520 5, 7LON 5

MManual trig 27Manual uploading 21, 27, 28, 29MicroLIBRARY 11MicroNET 11MicroSCADA 6, 7, 12, 27MicroSCADA PC 14MicroSYS 11MicroTOOL 11

NNFS 5, 7, 14Number of data transfers 29Number of new recordings 28

OOperating system 11, 12

PPath 29PCNet 11PYRAMID 5

RRAM 11RECOM 5, 7Recording 5, 28, 29RESDA 5, 6, 14, 27RESDA log file 5Retrieving information 31REVAL 5, 6, 14, 27, 29, 30REVAL log file 6REVAL-format 5REx5xx 6, 12, 14

SSCS 6Seq. no 30Sequence number 27, 30SMS 6, 7SPA messages 29, 30, 31SPA-bus communication 11Station wide list 27Status bar 29Status texts 29, 31Stop 29Storage 27

TTCP/IP 6Time 30Trig 30Trig reason 30

UUnit 6, 28, 29Unit name 27Unit recordings list 27, 28, 29, 30Upload recordings 28, 29Uploaded 30Uploaded recording 27, 29Uploading recording data 29Uploading recording header 30

WWindows NT file manager 29

46

Customer feedback report

Product:

ABB Automation Products AB would appreciate your comments on this product. Please grade the following questions by selecting one alternative per category. Your answer will enables us to improve our products.

How do you grade the quality of the product?

Excellent Poor

Total impression

Useability

Functionality

Human-man interface

Comments: __________________________________________________________

____________________________________________________________________

____________________________________________________________________

How do you grade the quality of the documentation?

Excellent Poor

Total impression

Layout

Illustrations

Readability

Easy to find

Content structure

Comments: __________________________________________________________

____________________________________________________________________

____________________________________________________________________

Rem

ove

from

bin

der

Rem

ove

from

bin

der

Suggestions for improvments:

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

Please send this report to:

ABB Automation Products ABSubstation Automation DivisionDept. TMD4S-721 59 VästeråsSweden

By facsimile:

Send to + 46 21 321633

Rem

ove

from

bin

der

Program:

This card registers your program and makes you eligible to receive information about future updates.

Name:

_____________________________________________________________________________________Title:

____________________________________________________________________________________Company: Dept.

____________________________________________________________________________________Address:

____________________________________________________________________________________

____________________________________________________________________________________City: State: Zip:

____________________________________________________________________________________Phone:

____________________________________________________________________________________Fax:

____________________________________________________________________________________

Program supplied by:

____________________________________________________________________________________Adress:

____________________________________________________________________________________

____________________________________________________________________

Software Registration Form

________________City: State: Zip:

____________________________________________________________________________________Phone:

____________________________________________________________________________________Date of receival of the program:

____________________________________________________________________________________Program serial Nr:

____________________________________________________________________________________

Fascimile:

Please send this registration card to ABB Automation Products AB, Sweden depart-ment TPS(+46 21 32 17 36)

Place PostageStamp Here

ABB Automation Products ABSubstation Automation DivisionDepartment: TPSS-721 59 VästeråsSweden

To be folded

Tape here

Rem

ove

from

bin

der

SOFTWARE LICENSE

• This ABB Automation Products AB License Agreement (”License”) grants you the nonexclusive right to use one copy of the enclosed software program (”SOFTWARE”) on a single computer (i.e., with a single CPU) at asingle location at any time. If you have multiple Licenses for the SOFTWARE you may have as many copiesof the SOFTWARE in use as you have Licenses.

• The software is owned by ABB AB or its suppliers and is protected by Swedish copyright laws, international treaty provisions, and all other applicable national laws. Therefore you must treat theSOFTWARE as any other copyrighted material (e.g., a book or musical recording) except that if the softwareis not copy protected you may either (a) make a copy of the SOFTWARE solely for backup or archivalpurposes, or (b) transfer the SOFTWARE to a single hard disk provided you keep the original solely forbackup or archival purposes. You may not copy the Documentation accompanying the SOFTWARE.

• The License is effective until terminated. This License will terminate automatically without notice fromABB AB if you fail to comply with any provision of this License. Upon termination youshall return the diskettes containing the SOFTWARE and all Documentation to ABB AB and destroy any copies of the SOFTWARE or any portions of it which has not been returned to ABB

AB, including copies resident in computer memory.

• You may not rent, lease, lend, sell or give away the SOFTWARE, but you may transfer your rights underthis ABB AB License Agreement on a permanent basis provided you transfer all copies of the SOF TWARE and all written materials, and the recipient agrees to the terms of this Agreement. Youmay not modify, adapt, translate, reverse engineer, decompile, disassemble, or create derivative works basedon the SOFTWARE. You may not modify, adapt, translate or create derivative works based on the writtenmaterials.

LIMITED WARRANTY

• ABB AB’s entire liability and your exclusive remedy shall be, at ABB AB’s option, either (a) return of the price paid or (b) repair or replacement of the SOFTWARE that

does notmeet ABB AB’s Limited Warranty and which is returned to ABB AB with a copy of your receipt. This Limited Warranty is void if failure of the SOFTWARE has

resulted fromaccident, abuse, or misapplication. Any replacement SOFTWARE will be warranted for the remainder of theoriginal warranty period or 30 days, whichever is longer.

• ABB AB disclaims all other warranties, either express or implied, including but not limited to implied warranties of merchantability and fitness for a particular purpose, with respect to the WARE,accompanying Product Manual(s) and written materials. This warranty gives you specific legal rights.

• Neither ABB AB nor anyone else who has been involved in the creation, production ordelivery of this product shall be liable for any direct, indirect, consequential or incidental damages (includingdamages for loss of business profits, business interruption, loss of business information, and the like) arisingout of the use or inability to use such product even if ABB AB has been advised of thepossibility of such damages. In any case, ABB AB's entire liability under any provision of this agreement shall be limited to the amount actually paid by you for the software.

ACKNOWLEDGEMENT

By opening the diskette package you acknowledge that you have read this agreement, understand it, and agreeto be bound by its terms and conditions. You also agree that it is the complete and exclusive statement of theagreement between the parties and supersedes all proposals or prior agreement, oral or written, and any othercommunications between the parties relating to the subject matter of the licence or limited warranty.

This Agreement is governed in all aspects by Swedish law. If any provisions of this Agreement are invalid orunenforceable, all others will remain in effect.

IMPORTANT - READ CAREFULLY BEFORE OPENING

ABB Automation Products AB

1. Grant of License

2. Copyright

3. Term

4. Other Restrictions

Limited Warranty

Customer Remedies

No Other Warranties

No Liability forConsequential Damages

This legal document is an agreement between You, the user, and ABB Automation Products AB, Västerås, SWEDEN. By openingthe diskette package You indicate your acceptance of the terms and conditions of this agreement. If You do not agree to theterms of this agreement, promptly return the unopened diskette package and other items which are part of the product for a fullrefund. Your product is a single user version unless you have a written agreement with ABB Network Partner AB.

License Agreement

• ABB Automation Products AB warrants that the software will perform substantially in accordance with the accompanying Product Manual(s) for a period of 1 year from the date of delivery from ABB Automation Products AB, Västerås. ABB Automation Products AB does not warrant that the SOFTWARE is free from coding errors.

Automation Products

Automation Products Automation Products

Automation Products

Automation Products



Automation Products


Automation Products SOFT-

ABB Automation Products ABSubstation Automation DivisionS-721 59 VästeråsSwedenTel: +46 21 342000Fax: +46 21 146918

1MR

K 5

11 0

22-U

EN

*2.2

-01

Printed on recycled and ecolabelled paper

user’s manual hv/collect*2 - abb...[drive]:\sc\lib4\base\bbone\use\path4_s11.txt 14 1mrk 511...

Documents