CAP505 Operators_Manual

ABB Automation

User’s Guide

CAP 5051MRS751902-MUMIssued: 15.12.2000Version: CProgram revision: 2.1.0

We reserve the right to change data without prior notice.

Operator’s Manual

Notice 1

The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any er-ror that may occur in this document.

Notice 2

This document complies with the CAP 505 version 2.1.0.

Notice 3

Additional information may be found in the Release Notes.

Trademarks

Microsoft and Windows NT are registered trademarks of Microsoft Corporation.

LON and LonTalk are registered trademarks of Echelon Corporation.

All Microsoft products referenced in this document are either trademarks or registered trademarks of Microsoft Corporation.

Other brand or product names are trademarks or registered trademarks of their respective holders.

ABB Automation

1MRS751902-MUMOperator’s ManualCAP 505User’s Guide

LIB 500 manuals

LIB 510 manuals

SMS 510 manuals

CAP 505 manuals

CAP 505/LIB 510/SMS 510 common manuals

CAP 505/SMS 510 common manuals

LIB 500 Configuration Manual 1MRS751880-MEN

LIB 500 Operator’s Manual 1MRS751885-MUM

LIB 510 Configuration 1MRS751886-MEN

LIB 510 MV Process Configuration 1MRS751887-MEN

LIB 510 MV Process Operator’s Manual 1MRS751891-MUM

LIB 510 Operator’s Manual 1MRS751888-MUM

SMS 510 Installation and Commisioning 1MRS751897-MEN

SMS 510 Operator’s Manual 1MRS751898-MUM

CAP 505 Installation and Commissioning 1MRS751901-MEN

CAP 505 Operator’s Manual 1MRS751902-MUM

Relay Configuration Tool Tutorial 1MRS751903-MEN

Relay Mimic Editor Configuration 1MRS751904-MEN

Relay Configuration Quick Start Reference 1MRS751905-MEN

SPTO Configuration Tool 1MRS751906-MEN

Protocol Editing Tool Operator’s Manual 1MRS751982-MUM

Tools for Relays and Terminals 1MRS752008-MUM

SM/Gateways Configuration 1MRS751870-MEN

1MRS751902-MUM CAP 505

ABB Automation

Operator’s Manual

User’s Guide

1 Introduction

2 Quick start example

3 Project Structure Navigator

4 Project Export/Import tool

5 Plant Structure Settings

6 Plant Structure object types

7 User Structure object types

8 Relay Download Tool

AB

CAP 505ContentsUser’s Guide

Contents:

Operator’s Manual1MRS751902-MUM

1. Introduction ...............................................................................11.1. General .........................................................................................11.2. Operational features ......................................................................11.3. User interface ................................................................................21.4. Base system ..................................................................................21.5. Applications ...................................................................................21.6. CAP 505 tools ...............................................................................3

2. Quick start example ..................................................................52.1. Projects .........................................................................................52.2. Views .............................................................................................52.3. Object types ..................................................................................52.4. Object type groups ........................................................................62.5. Starting CAP 505 ..........................................................................62.6. Instantiation of objects ..................................................................62.7. Moving objects in the project .......................................................112.8. Configuration of device objects ...................................................122.9. Using user views .........................................................................172.10.Launching object tools ................................................................19

3. Project Structure Navigator ...................................................203.1. General .......................................................................................203.2. Projects .......................................................................................20

3.2.1. Master Design View .........................................................203.2.2. User Views .......................................................................20

3.3. Object types ................................................................................213.4. Object type groups ......................................................................213.5. User interface ..............................................................................213.6. Entering the Project Structure Navigator .....................................223.7. File menu ....................................................................................23

3.7.1. File Open .........................................................................233.7.2. File Close .........................................................................243.7.3. Organize Projects ............................................................243.7.4. Exit ...................................................................................24

3.8. Edit menu ....................................................................................243.8.1. Insert Object .....................................................................253.8.2. Delete Object ...................................................................263.8.3. Object Properties .............................................................27

3.9. Views menu .................................................................................293.9.1. Create View .....................................................................293.9.2. Delete View ......................................................................303.9.3. View Properties ................................................................30

B Automation

1MRS751902-MUMOperator’s ManualCAP 505Contents User’s Guide

3.9.4. View List .......................................................................... 303.10.System Tools menu ................................................................... 30

3.10.1.Customize... ..................................................................... 313.11.Help menu .................................................................................. 31

3.11.1.About ............................................................................... 32

4. Project Export/Import tool ..................................................... 334.1. General ....................................................................................... 334.2. Features ...................................................................................... 34

4.2.1. Updating the project list ................................................... 344.2.2. Project storage ................................................................ 354.2.3. Copying projects between network computers ................ 354.2.4. Choosing storage location for temporary projects ........... 364.2.5. Exporting projects ............................................................ 364.2.6. Importing projects ............................................................ 374.2.7. Project properties ............................................................ 384.2.8. Deleting a project ............................................................. 384.2.9. Duplicating a project ........................................................ 384.2.10.Creating a new project ..................................................... 394.2.11.Errors accessing remote disk resources .......................... 39

5. Plant Structure Settings ........................................................ 415.1. General ....................................................................................... 415.2. Starting the Plant Structure Settings tool .................................... 415.3. Attributes of plant structures ....................................................... 41

5.3.1. Level Id ............................................................................ 425.3.2. Level Description ............................................................. 425.3.3. Field Length ..................................................................... 42

6. Plant Structure object types .................................................. 436.1. Overview ..................................................................................... 436.2. General ....................................................................................... 436.3. Field length ................................................................................. 436.4. Station ......................................................................................... 436.5. Bay .............................................................................................. 44

7. User Structure object types .................................................. 467.1. Overview ..................................................................................... 467.2. General ....................................................................................... 46

7.2.1. Instantiating Level objects ............................................... 46

8. Relay Download Tool ............................................................. 478.1. General ....................................................................................... 478.2. User interface ............................................................................. 478.3. Menu commands ........................................................................ 48

8.3.1. File menu ......................................................................... 488.3.2. Help menu ....................................................................... 48

ABB Automation

AB

1MRS751902-MUM CAP 505Contents

Operator’s Manual

User’s Guide

8.4. Relay communication functions ..................................................498.4.1. Send page ........................................................................498.4.2. Receive page ...................................................................498.4.3. The file transfer procedure ...............................................50

8.5. Relay command buttons .............................................................528.5.1. Store ................................................................................528.5.2. Reset ................................................................................528.5.3. Counter ............................................................................528.5.4. FB Code ...........................................................................528.5.5. FB List ..............................................................................53

B Automation


AB

Operator’s Manual

User’s Guide 1. Introduction

the

es.

rs

s

y

a local

r or

1. Introduction

$ERXW�WKLV�FKDSWHU

This chapter introduces CAP 505, its base system, operational features, user interface and functional description.

1.1. General

CAP 505, the 5HOD\�3URGXFW�(QJLQHHULQJ�7RROV�software� is a &omputer $ided 3rogramming system for medium voltage relays in the RED 500 and SPACOM series.

CAP 505 provides you with the following tools:

• The Project Structure Navigator for handling relays and tools.

• The Relay Configuration Tool for configuration and programming of relays in RED 500 series.

• The Relay Mimic Editor for mimic configuration of relays in the RED 500 seri

• The RED Relay Tool for:

• Parametrization of RED 500 series of relays.

• SPA and LON1 communication.

• The SPA Relay Tool for:

• Parametrization of SPACOM series of relays.

• SPA-communication.

• The Project Export/Import Tool for project management.

• The Communication Configuration page for setting communication parameteof the device objects.

• The Relay Download Tool for configuration up/download of relays in the RED500 series.

• The Disturbance Recorder Collector Tool for uploading of disturbance recordfrom the RED 500 series of relays.

• The SPTO Configuration Tool for monitoring and configuring the SPTO 1D2,1D5, 1D6 and 6D3 control modules of the SPAC feeder terminal series.

• The Protocol Editing Tool (POD) for configuring the protocol object dictionartables of the REC52x relays.

• The System Configuration Tool for configuring the projects' system configurations.

CAP 505 runs on various types and sizes of computers. It can be used both as system near the relay and as a central system connected to several relays. Communication with the relays is done through the relay front panel connectothe rear connector.

1.2. Operational features

CAP 505 provides:

1. LON is a registered trademark of Echelon Corporation.

B Automation 1

1MRS751902-MUMOperator’s ManualCAP 5051. Introduction User’s Guide

ts:

and ring

• Product engineering (bay level).

• On-line and off-line engineering.

• Framework for relay tools.

• Project management.

• Object oriented project data management.

• Graphical programming for control and protection units.

• Graphical programming for mimic panel.

• Creation of documentation for the application program.

• Generation of application program code.

• Loading of program code, mimic configuration and parameters to the relay.

• Loading parameters from the relay.

• Loading of recorded values from the relay.

• Edit history of parameters.

• Comparison of present and saved values.

• Loading of disturbance records from the relay.

1.3. User interface

The user interface of the CAP 505 system consists of the following componen

• Project Structure Navigator for tool selection and object management.

• Project Export/Import for archiving and transfer of projects.

1.4. Base system

The CAP 505 system contains a base system and a communications system.

Supported communication protocols are:

• SPA, through COM-port and relay rear and front panel interfaces.

• LON® communication, through LonTalk®2 adapters to the relay rear panel interface.

• Supported LON communication cards are:

• RER 109 PCLTA Card.

• PCC-10 PC Card.

• PCLTA-20 Card.

1.5. Applications

A station control and protection system contains a wide variety of componentsfunctions. CAP 505 is a toolbox for handling data and tools during relay engineeprojects.

2. LonTalk is a registered trademark of Echelon Corporation.

2 ABB Automation


AB

Operator’s Manual

User’s Guide 1. Introduction

,

nes rated

rol,

n list

of rget

brary ed on ns

rt ted

ock

1.6. CAP 505 tools

6\VWHP�&RQILJXUDWLRQ�7RRO

The System Configuration Tool is used for configuring the projects’ system configuration to enable communication with the relays.

This tool is documented in the CAP 505 Installation and Commissioning manual.

3URMHFW�([SRUW�,PSRUW�7RRO

The Project Export/Import tool is used for project management purposes like deletion, duplication, and creation of projects. In addition to this, the tool is used when a project is to be transferred to another system or brought into the current collection of projects.

This tool is documented in chapter “Project Export/Import tool” on page 33.

5HOD\�&RQILJXUDWLRQ�7RRO

The Relay Configuration tool is used for configuring the functions of protectioncontrol, condition monitoring, measurement and logics.

The Relay Configuration tool is based on the IEC 1131-3 standard, which defithe programming language that is used for relay terminals. The programmablesystem of the RED 500 series of products allows the output contacts to be opein accordance with the state of the logic inputs, the outputs of protection, contmeasurement and condition monitoring functions. The control logic (e.g. interlocking and alarm logic) is programmed with Boolean functions, timers, counters, comparators and flip-flops. The programming languages are functioblock diagram language, state function chart diagram language or instruction language.

This tool is documented in the Relay Configuration Tool Tutorial and Relay Configuration Quick Start Reference.

3URWRFRO�(GLWLQJ�7RRO��32'�

The Protocol Editing tool is an engineering tool for protocol table configurationREC52X relay terminals. Protocol tables can be read from and written to the tadevice and also stored onto the hard disk. The tool allows to maintain a user liof protocol tables on a per-project basis. The engineering work can thus be basthe user library or standard templates, which comprises the protocol descriptiothat are shipped with the REC52X object type.

Signal-level protocol table modification is provided with functions such as Insesignal, Remove signal and Move signal. Attribute values of signals can be ediwithin the limits of the specified values. Protocol table signals can be listed in alphabetical order of the signal identification, address, data type or function blorder.

In addition, Protocol Editing tool produces the information necessary for eventhandling configuration in the MicroSCADAsystem.

This tool is documented in the Protocol Editing Tool Operator’s Manual.

B Automation 3

1MRS751902-MUMOperator’s ManualCAP 5051. Introduction User’s Guide

D5, es in

ries, fit

f the

500 DE.

5HOD\�0LPLF�(GLWRU

The Relay Mimic Editor is used for configuring the graphical display and the alarm channels of the feeder terminal. The MIMIC configuration may include circuit breakers, disconnectors, indicators, measurement data objects and user-defined texts and explanations.

Alarm function blocks can be configured in the same alarm view of the MIMIC editor. ON and OFF state texts and LED colours can be defined.

This tool is documented in the Relay Mimic Editor Configuration manual.

5HOD\�6HWWLQJ�7RRO

The Relay Setting tool is used for parameterisation of the relay units. The parameters can be set off-line in a PC, and downloaded to the relay or uploaded from the relay.

The Relay Setting Tool menu structure including views for parameterization are the same as the views on the technical level of the local MMI for the relays in the RED 500 series.

It is also possible to set parameters in relays in the SPACOM series.

This tool is documented in the Tools for Relays and Terminals manual.

5HOD\�'RZQORDG�7RRO

The Relay Download Tool is used for sending configurations and mimic pictures to the relay, and for storing configurations to non-volatile memory and for restarting the relay software.

This tool is documented in chapter “Relay Download Tool” on page 47.

6372�&RQILJXUDWLRQ�7RRO

The SPTO Configuration tool targets the control modules SPTO 1D2, SPTO 1SPTO 1D6 in SPAC 300 series and SPTO 6D3 in the SPAC 500 and 600 serithe SPACOM range of products.

The tool can be used to configure the SPTO 1D2, 1D5, 1D6 in the SPAC 300 sewhen the built-in factory default setting groups in the modules cannot be benefrom, or whenever it is desirable to make an own configuration.

This tool is documented in the SPTO Configuration Tool manual.

&RPPXQLFDWLRQ�SDJH

The Communication page is used for configuring the communication settings odevice objects.

The communication page is documented in the Tools for Relays and Terminals manual on a per-object type basis.

'LVWXUEDQFH�5HFRUG�&ROOHFWRU�7RRO

With the DR-Collector Tool, disturbance records can be uploaded from the REDand SPACOM series of relays. The supported recording file format is COMTRA

This tool is documented in the Tools for Relays and Terminals manual

4 ABB Automation


AB

Operator’s Manual

User’s Guide 2. Quick start example

ject.

f the

t as ts rt/

iated rge. u”

eir

For

s. In have n use her

efine .

2. Quick start example


This chapter discusses the basic steps for getting started with CAP 505 and is intended to serve as an introductory reading to users not familiar with CAP 505.

This example:

• Guides you through the process of constructing a representation of a simplestation with three bays with RED 500 and SPACOM relays, familiarizing youwith basic functions such as adding, configuring and moving objects in a pro

• Illustrates one solution to organize the project by means of user views.

1RWH��In this example it is assumed that you have completed commissioning oCAP 505 software, which is explained in the CAP 505 Installation and Commissioning manual.

2.1. Projects

CAP 505 supplies an initial empty project titled SOST. The SOST project is sethe default project initially, meaning that this project will contain the new objecunless another project is explicitly created and opened, using the Project ExpoImport Tool. For detailed information on working with CAP 505 projects, see chapter “Project Export/Import tool” on page 33.

2.2. Views

The Project Structure Navigator provides the possibility to define different viewcontexts. This feature makes it possible to do arbitrary grouping of the instantobjects, which is a useful feature when the number of instantiated objects is laFor detailed information on working with project views, see section “Views menon page 29.

2.3. Object types

There are three main categories of object types, level object types, device object types and compound object types.

The level object types are used for building the structure of the projects and thviews.

The device object types are used when a physical device shall be configured.example, REF54x is a device object type.

Compound object types combine behaviour of both level and device object typeessence, compound object types participate in project's structurization but alsoconfigurable properties, similar to the device object types. For instance, you caStation and Bay objects to build a representation of a station and its bays. Anotexample, are the communication gateway object types, e.g. LSG (LON/SPA Gateway). Device objects can be hosted by a gateway object, for which you dcorrect communication settings to enable communication through the gateway

B Automation 5

1MRS751902-MUMOperator’s ManualCAP 5052. Quick start example User’s Guide

2.4. Object type groups

Each object type belongs to one named object type group, which provides similar functionality.

Four object type groups are available:

User Structure Object types of this group serve the purpose of project structurization.

Plant Structure Object types of this group serve the purpose of project structurization.

Gateway Object types of this group serve the purpose of project structurization and representation of communication gateway devices.

Protection & Control Object types of this group serve the purpose of representing protection and control devices.

2.5. Starting CAP 505

To start CAP 505, select the Start CAP 505 icon from the program folder created by the CAP 505 installation program. The CAP 505 Login window appears. Click Login to open the Project Structure Navigator with the default project opened in the Master Design View mode.

2.6. Instantiation of objects

In this section, we begin by instantiating four RED 500 device objects and one SPACOM device object to the project. (The term instantiate�means that an instance of an object type is inserted into the project.) Then we add a simple representation of a station with three bays, illustrating how to move the device objects in the project structure.

'HYLFH�REMHFW�LQVWDQWLDWLRQ

At this point, your project contains only the abstract root node, which is titled Root. Click on the root node with the mouse, so the navigator knows where to insert the new object in the project structure. Next, choose Insert Object on the navigator’s Edit menu, this causes the Add Project Object dialog box to appear.

)LJ�� ,QVWDQWLDWLQJ�D�QHZ�REMHFW�WR�WKH�SURMHFW

This dialog box displays the object type groups and the object types present in the system. As you are now instantiating a device object, the interest group is Protection & Control, which groups the RED 500 series and SPACOM series object types.

6 ABB Automation


AB

Operator’s Manual


To instantiate a device object representing a REF54x relay terminal of the RED 500 relay series, click on the Protection & Control list item. As the result, you are viewing the list of Protection & Control object types. The first available object type is automatically selected, as shown in Figure 2.6.-2.

)LJ�� 6HOHFWLQJ�WKH�W\SH�RI�WKH�REMHFW

The appropriate object type (REF54X) is already selected, to instantiate it, click OK, which opens the New Object’s Properties dialog box for entering the object’s name and title.

)LJ�� (QWHULQJ�WKH�QDPH�DQG�WLWOH�IRU�WKH�REMHFW

Type in the name and title and click OK, so the dialog box closes and the object is inserted under the root node. The object’s title is displayed in the project views. Now your project should look like the one shown in Figure 2.6.-4.

B Automation 7


)LJ�� 7KH�LQVWDQWLDWHG�5()��[�GHYLFH�REMHFW�LQ�WKH�SURMHFWV�YLHZ

Repeat this instantiation procedure twice, specifying ’OUT1’ and ’OUT2’ as the names and ’Protection and control’ as the titles for both of the objects. These new REF54x objects will also be inserted under the project’s root node, since the project does not yet contain any compound objects being able to host the device objects. Your project should now look like the one shown in Figure 2.6.-5.

)LJ�� 7KUHH�5()��[�GHYLFH�REMHFWV�LQ�WKH�SURMHFW

Now you have three REF54x device objects in the project. As you may recall, the aim is to instantiate also a device object of the SPACOM type.

To accomplish that, repeat the instantiation procedure, with the exception, that you select the SPACOM object type from the Protection & Control group. For the object’s name and title, specify ’INCOMER2’, ’Differential protection’. When you are ready, the project should look like the one shown in Figure 2.6.-6.

)LJ�� )RXU�GHYLFH�REMHFWV�LQ�WKH�SURMHFWV�YLHZ

Notice that, in terms of usability, these newly instantiated device objects are somewhat abstract, since they lack essential information about the physical relay terminals they represent. In practice, these objects need to be configured before they can be used, the configuration procedure is explained later.

As you now have some device objects, you can advance to add compound objects to the project to organize the contents of the project.

8 ABB Automation


AB

Operator’s Manual


&RPSRXQG�REMHFW�LQVWDQWLDWLRQ��3ODQW�6WUXFWXUH

Next, you build a simple representation of a station with three bays.

Start by selecting the project’s root node that will be the insert-location for the Station object. In fact, the only location where you can insert a Station object, is the project’s root node.

On the Edit menu, choose Insert Object to bring up the Add Project Object dialog box. Since the Station object type belongs to the Plant Structure group, select the Plant Structure group as is done in Figure 2.6.-7.

)LJ�� 6HOHFWLQJ�WKH�6WDWLRQ�REMHFW�W\SH

To have the Station object instantiated, click OK. The dialog box that now appears for entering attributes for the object, is specific for instantiation of Plant Structure objects, as illustrated in Figure 2.6.-8. Enter ’Eastwick’ as the object’s title and ’STA1’ as its name.

)LJ�� ,QVWDQWLDWLQJ�D�3ODQW�6WUXFWXUH�REMHFW��6WDWLRQ

Click OK to instantiate the station object. Now your project should look like the one in Figure 2.6.-9.

B Automation 9


)LJ�� 7KH�QHZ�6WDWLRQ�REMHFW�LQ�WKH�SURMHFWV�YLHZ

Now you have a Station object capable of hosting the bays. Next, you will instantiate three Bay objects under the station. Eventually, the project’s device objects will be moved under these bays.

As the station will be the parent for the bays, select the Station object to set the correct insert-location.

Invoke the Add Project Object dialog box. The navigator is aware of the currently selected object’s type (Station) and displays the available object type groups and object types accordingly, see Figure 2.6.-10.

)LJ�� 6HOHFWLQJ�WKH�%D\�REMHFW�W\SH

To instantiate the object, click OK and specify the name and title as in Figure 2.6.-11.

10 ABB Automation


AB

Operator’s Manual


)LJ�� 6SHFLI\�QDPH�DQG�WLWOH�IRU�WKH�%D\�REMHFW

Next, add two bays similarly, specifying ’Bay2’, ’Bay3’ and ’Outgoing 1’, ’Outgoing 2’ as their names and titles. Now your project should look like the one shown in Figure 2.6.-12.

)LJ�� 7KH�VWDWLRQ�KRVWLQJ�WKUHH�ED\V

Now you are ready to organize the project further by moving the device objects to more appropriate locations in the project structure.

2.7. Moving objects in the project

In this section, the existing device objects are moved to new location in the project structure.

B Automation 11


Figure 2.7.-1 illustrates the intended final organization of the device objects in the Master Design View.

)LJ�� 2EMHFWV�LQ�WKHLU�ILQDO�ORFDWLRQV

The procedure for moving objects in the project’s views consists of the following steps:

1. Select the object you intend to move by clicking on it with the mouse.

2. On the Project Structure Navigator’s Edit menu, select Object Properties to bring up the General Object Attributes dialog box.

3. Click Move on the General Object Attributes dialog box to bring up the Move Object dialog box.

4. From the project structure, select the target compound object, which will host the moved object.

5. Click Move Here on the Move Object dialog box to move the object to the selected target location.

According to that procedure, move the objects one at a time to the locations shown in Figure 2.7.-1. Notice that, moving a device object under a bay object, causes the station node to collapse. A collapsed node is expanded by either double-clicking on it or by clicking on the plus sign (+) on the node’s left hand side.

Next, we will advance by configuring the project’s device objects.

2.8. Configuration of device objects

*HQHUDO

Prior to using an instantiated device object, the object must be configured before it is meaningful or even possible, to launch an object tool. Otherwise, such attempts result in notifications requesting you to configure the object.

For instance, configuring a REF54x device object means that the object is assigned:

1. The software configuration (SW), which is a set of hardware dependent files. The software configurations are supplied solely by ABB.

12 ABB Automation


AB

Operator’s Manual


ox,

utes

e pl

eral ts,

y n table

tion al ing ge

54x

2. The application (Apl) configuration, which is a set of application dependent files. An application configuration is either supplied by ABB or created within the CAP 505/501 environment, whereafter it has been saved into the application library of the object’s object type.

7KH�FRQILJXUDWLRQ�SURFHGXUH

A device object is configured in the Master Design View by means of a dialog bwhich is dependent on the device object's type. The configuration procedure comprises the following steps:

1. Select the device object in the project structure.

2. Select Object Properties on the Edit menu to open the General Object Attribdialog box for the object.

3. Click Attributes�to open the object’s configuration dialog box.4. From the SW library, select the SW configuration that matches the relay

terminal that shall be used.5. Select an application from the Apl library, or if the application is unknown,

some of the SM/RED object types allow uploading the configuration from threlay terminal. The uploaded configuration is available for selection in the Alibrary list.

Close the object's configuration dialog box by clicking OK to return to the GenObject Attributes dialog box. For more information on configuring device objecsee the Tools for Relays and Terminals manual.

&RQILJXULQJ�WKH�TXLFN�VWDUW�GHYLFH�REMHFWV

To proceed with the example, we configure the device objects in the order theappear in the project. Once we are done, the objects are configured as shown i“Example device configuration.” on page 17.

To proceed, select the device object INCOMER1 which is titled Incomer protecand control. On the Edit menu, select Object Properties to bring up the GenerObject Attributes dialog box. The tabbed page titled General is active, displaygeneral information on the object. Notice that, on this dialog box you can chansome of the object's attributes in the Master Design View. Which attributes arechangeable, depends on the object's type.

Now, to configure this REF54x device, click Attributes and you enter the REF Configuration dialog box, shown in Figure 2.8.-1.

B Automation 13


)LJ�� 7KH�FRQILJXUDWLRQ�GLDORJ�ER[�IRU�5()��[�GHYLFH�REMHFWV

$VVLJQLQJ�WKH�VRIWZDUH�FRQILJXUDWLRQ

As stated in Table 2.8.-1 on page 17, this object’s software configuration should be REF543-1MRS118501 rev. F, thus the software configuration suggested by default, has to be changed. On the dialog box’s upper area, the Select New check box is checked, allowing you to select the appropriate software configuration.

To change the configuration, select the configuration named REF543-1MRS118501 from the list titled SW library and select revision F from the list titled Rev.

$VVLJQLQJ�WKH�DSSOLFDWLRQ�FRQILJXUDWLRQ

To complete this object’s configuration, you need to assign the intended application configuration for the object, in this example it is 1MRS114502 revision A.

To assign it, select the application configuration 1MRS114502 from the list titled Apl library and the revision A from the list titled Rev. Next, click OK to apply the configuration, saving it to the project database. Now you returned to the General Object Attributes dialog box, close it by clicking OK.

14 ABB Automation


AB

Operator’s Manual


g d

. ect

es

he did the

8SORDGHG�DSSOLFDWLRQ�FRQILJXUDWLRQV�LQ�5()��[��5(0��[�DQG�5(&��[�REMHFW�W\SHV

The REF54x, REM54x and REC52x object types provide an alternative of using an application configuration, which you have uploaded from the relay terminal. Upon completion of the upload, you save the uploaded configuration into the object type’s user application library. These application configurations are stored without revision information and are available through the Apl library list, shown in Figure 2.8.-1. Use of uploaded application configurations is outlined below:

1. Insert the device object to the project.

2. Configure the object as explained above, assigning an empty application configuration, eventually you will replace it with the uploaded configuration. Apply the configuration normally and then return to the Project Structure Navigator.

3. Reopen the General Object Attributes dialog box selecting the Communication page to provide communication settings for the object. Select the communication protocol and configure the communication settings. Connect the communication cable, if not done yet.

4. Open the object type's configuration dialog box. Click Apl Utils… and you enter the dialog box for maintaining the user application library.

5. By clicking Receive, the upload starts bringing up a progress indicator dialobox. Upon completion of the upload, you provide the name for the uploadeconfiguration. This name will appear in the Apl library list.

6. Close the user application library management dialog box by clicking CloseNow, to assign the newly uploaded application configuration, check the SelNew check box and select the configuration from the Apl library list.

7. Close the object type's configuration dialog box by clicking OK. You are prompted to confirm the replacement of the application configuration, click Yto enforce the new configuration.

To proceed with the example, configure the other two REF54x device objects (OUT1 and OUT2) using Table 2.8.-1 on page 17 as reference.

At this point, you still have the SPACOM device object (INCOMER2) lacking tconfiguration. To configure it, enter the object's configuration dialog box as youwith the REF54x objects. The configuration dialog box that appears, differs fromone you used for the REF54x objects, see Figure 2.8.-2.

B Automation 15


)LJ�� 7KH�FRQILJXUDWLRQ�GLDORJ�ER[�IRU�63$&20�GHYLFH�REMHFWV

Now, locate the module named SPAD 346 from the Modules list and click Add −> when you have selected the module. The dialog box should look like the one shown in Figure 2.8.-3.

)LJ�� 7KH�VHOHFWHG�63$&20�FRQILJXUDWLRQ

16 ABB Automation


AB

Operator’s Manual


To apply the configuration, click OK and you return to the General Object Attributes dialog box.

Now you have almost completed this example. Next, you can familiarize yourself with use of user views in projects. Remember that regarding views, the example project contains only the Master Design View, which is the only view allowing you to instantiate device objects to the project and configure them.

2.9. Using user views

*HQHUDO

No specific rules for use of user views exist in regard to their logical contents or amount.

&UHDWLQJ�XVHU�YLHZV

In this example, we will create two rather self-explanatory user views, namely one named Outgoing and another named Incoming and populate these views with the previously instantiated device objects appropriately.

To proceed building the example project, select Create view on the Views menu of the Project Structure Navigator. This opens the Project View Properties dialog box shown in Figure 2.9.-1.

)LJ�� (QWHULQJ�LQIRUPDWLRQ�IRU�WKH�QHZ�XVHU�YLHZ

Specify the information for the view as shown in the above figure. You can later change these properties of views, by selecting the View Properties menu item on the Views menu. Click OK to create the view. The navigator opens the view immediately. Notice that the Views menu now contains this newly added view below the Master Design View menu item.

Next, add the other user view similarly and specify ’Outgoing’ for the view’s properties. Now your Views menu should contain the menu items shown in Figure 2.9.-2.

Table 2.8.-1 Example device configuration.

REF54x device SW Configuration Apl Configuration

INCOMER1 REF543-1MRS118501 rev. F 1MRS114502 rev. AOUT1 REF541-1MRS118500 rev. C 1MRS114501 rev. AOUT2 REF541-1MRS118500 rev. C 1MRS114501 rev. A

SPACOM device Relay Description

INCOMER2 SPAD 346

B Automation 17


)LJ�� 8VHU�YLHZ�PHQX�LWHPV�LQ�SODFH

$GGLQJ�REMHFWV�WR�D�XVHU�YLHZ

Final step of this example is to populate the user views with the device objects.

The procedure for adding objects to user views is simplified compared to Master Design View, since the objects are already assigned names and other basic information.

If the Outgoing view is not currently active, activate it by selecting the Outgoing menu item on the Views menu. Now, select Insert Object on the Edit menu to bring up the Add object from Master Design View dialog box, see Figure 2.9.-3. The dialog box lists all device objects that exist in the project, displaying both the titles and the names of the objects. Object names are displayed in parenthesis.

)LJ�� /LVW�RI�REMHFWV�LQ�0DVWHU�'HVLJQ�9LHZ

Notice the Add Level button on the dialog box. Through it you can add Level objects to the user view for organizing the view’s contents.

The intention is to add the objects OUT1 and OUT2 into this view. So, select the object named OUT1 from the list and click OK to add the object closing the dialog box. The contents of the view should now be as shown in Figure 2.9.-4.

18 ABB Automation


AB

Operator’s Manual


)LJ�� 2EMHFW�287��LQ�SODFH

Similarly, add the object named OUT2 to this view.

Next, switch the view by selecting the Incoming menu item on the Views menu. Add the remaining device objects INCOMER1 and INCOMER2 to this view.

2.10. Launching object tools

Object tools are launched as follows:

1. Select the target device object in the project. Object tools are available in all views of a project.

2. Double-click on the object tool on the Object Tools list or3. Select the tool from the Object Tools list and press <Enter> from the keyboard.

The Project Structure Navigator allows a single object tool to be used at a time. Documentation for each CAP 505 tool is supplied, the documentation is listed on page 1.

B Automation 19

1MRS751902-MUMOperator’s ManualCAP 5053. Project Structure Navi-

gatorUser’s Guide

sign can

ing ay

ure ews. d into

3. Project Structure Navigator


This chapter describes the elements and functionality of the Project Structure Navigator.

3.1. General

The Project Structure Navigator is your workspace for managing data and tools. It provides you with access to the CAP 505 tools and project-based object-oriented data-management.

3.2. Projects

In CAP 505, projects are the containers for object-oriented data management and storage. Projects allow you to build representations of power stations and their protection and control devices. The maximum number of projects in CAP 505 is limited only by the available disk space on your computer.

The navigator allows you to build projects and operate on them by means of a hierarchical tree structure. The structure is comprised of nodes where each node is an instance of an object type. Initially, all projects are empty, meaning that the project tree contains only one node (root level) that gives a starting point to build the project upon.

The Project Structure Navigator works in one of two modes, the Master Design View mode, or the user view mode.

3.2.1. Master Design View

The Master Design View allows instantiation of all available object types in CAP 505. It is the only view, in which you can:

• Instantiate objects to the project.

• Configure the objects.

• Configure the communication settings of the objects.

The device objects are also available for use in the user views. The Master DeView is a built-in view meaning that it is always available in every project and not be deleted.

3.2.2. User Views

User views are intended for designing browsable operator views, e.g. for showonly objects with importance to the user. The object hierarchy in a user view mdiffer from the one in the Master Design View. Object types of the User Structobject types group, provide you with means of arranging the hierarchy of user viThe device objects, that are available in the Master Design View, can be insertethe user views. (Notice the differentiation between the terms instantiate and insert here.)

20 ABB Automation


AB

Operator’s Manual

User’s Guide 3. Project Structure Navi-gator

nd its

3.3. Object types

The Project Structure Navigator handles objects of three types, namely:

Level object types Level object types serve as structurization items in a project. A level object type does not set restrictions on what object types it is possible to insert under it. In many respects, levels behave like directories in a file system since directories may contain files and subdirectories. An example of level object type is the Level type.

Device object types Device object types control physical devices. A device object stores parameters about physical hardware, e.g. a REF 541 terminal.

Compound object types Compound object types combine the behaviour of level and device object types. In a project, a compound object has both object properties and structurization properties. As the result, a compound object has private object settings and a view level, under which it is possible to insert objects of object types allowed by the object type. The main difference between views of a level object type and a compound object type is that compound object types set restrictions on what object types can be represented in its views. Examples of compound object types are plant structures and communication gateways.

3.4. Object type groups

Each object type belongs to one named object type group, whose member types provide common functionality.

Four object type groups are available:

User Structure Object types of this group serve the purpose of project structurization. Contains level object types only.

Plant Structure Object types of this group serve the purpose of MicroSCADA compatible project structurization. Contains compound object types only.

Gateway Object types of this group serve the purpose of project structurization and representation of communication gateway devices. Contains compound object types only.

Protection & Control Object types of this group represent protection and control devices. Contains device object types only.

3.5. User interface

Access to the various tools and functions, is provided by means of a tool bar, menus and keyboard shortcuts. Figure 3.5.-1 illustrates the navigator’s user interface aelements.

B Automation 21


gatorUser’s Guide

or

e t

ct

f the

ress e nel

)LJ�� 7KH�XVHU�LQWHUIDFH�RI�WKH�3URMHFW�6WUXFWXUH�1DYLJDWRU

8VHU�LQWHUIDFH�HOHPHQWV

Caption bar Displays the name of the current view. In Figure 3.5.-1, it is the Master Design View. Also contains the standard operating system’s window management commands fminimizing, maximizing and closing the window.

Menu bar File, Edit, Views, System Tools and Help menu.

Tool bar The tool bar contains shortcuts for fast access to the frequently used functions.

Object tools list An object selection sensitive list of object tools that aravailable for the object currently selected in the projecstructure.

Structure Displays the objects in the current project view for objeselection and navigation.

Status bar Displays the path of the current project and the type oobject, currently selected in the project structure.

3.6. Entering the Project Structure Navigator

To enter Project Structure Navigator:

1. From the CAP 505 program folder, select the shortcut Start CAP 505 and p<Enter> or double-click on the shortcut. This starts the MicroSCADA servicbringing up the CAP 505 Login window, Figure 3.6.-1 illustrates the login paof the window.

2. On the CAP 505 Login window, click Login to enter the Project Structure Navigator.

22 ABB Automation


AB

Operator’s Manual


)LJ�� 7KH�ORJLQ�SDQHO�RI�WKH�&$3��/RJLQ�ZLQGRZ

Notice that, if you attempt to start a second instance of CAP 505, which is not allowed, you are notified that CAP 505 is already running, see Figure 3.6.-2.

)LJ�� 1RWLILFDWLRQ�WKDW�&$3��LV�DOUHDG\�UXQQLQJ

Dismiss the notification by clicking OK.

3.7. File menu

The File menu contains the project handling functions and exit.

)LJ�� 7KH�)LOH�PHQX

3.7.1. File Open

.H\ERDUG�HQWU\��&WUO!��2!

7RRO�EDU�HQWU\�

By selecting this menu alternative the currently open project is closed and the Open Project dialog box is opened.

B Automation 23


gatorUser’s Guide

AP

ing

)LJ�� 7KH�2SHQ�3URMHFW�GLDORJ�ER[

To open a project into the navigator view, first select the project and then click Open. This enforces also the project’s system configuration, which you can view and modify by means of the System Configuration Tool.

3.7.2. File Close

This alternative closes the currently open project.

3.7.3. Organize Projects

When selecting this alternative, the Project Export/Import Tool is started, for more information on the tool, see chapter “Project Export/Import tool” on page 33.

3.7.4. Exit

.H\ERDUG�HQWU\��$OW!�)�!

By selecting this alternative, the tool session is terminated and you enter the C505 Login window.

1RWH��To close CAP 505, click Exit on the CAP 505 Login window, this will stopthe MicroSCADA service.

3.8. Edit menu

The edit menu contains functions for adding and deleting objects and for invokthe General Object Attributes dialog box for the currently selected object.

Accessibility of the menu items depends on the currently selected object. For instance, the Delete Object item in Figure 3.8.-1 is disabled, indicating that thecurrently selected object cannot be deleted.

)LJ�� 7KH�(GLW�PHQX

24 ABB Automation


AB

Operator’s Manual


3.8.1. Insert Object

.H\ERDUG�HQWU\��,QVHUW!

7RRO�EDU�HQWU\��

Through this menu alternative you initiate instantiation/insertion of objects in the project.

,QVHUW�2EMHFW�LQ�WKH�0DVWHU�'HVLJQ�9LHZ

When you select the Insert Object function in the Master Design View, the Add Project Object dialog box, shown in Figure 3.8.1.-1, appears allowing you to specify the type of the object to be added to the currently selected location.

)LJ�� ,QVWDQWLDWLRQ�RI�DQ�REMHFW

The Project Structure Navigator displays all object type groups currently available in the CAP 505 environment. However, the object types of these groups are filtered according to the currently selected object, which will host the new object.

To instantiate the object, choose the appropriate object type group, then select the type for the new object and click OK to enter the dialog box, on which you provide the basic properties for the new object, see Figure 3.8.1.-2. Notice that this dialog box varies according to the type of the new object.

)LJ�� 3URYLGH�SURSHUWLHV�IRU�WKH�QHZ�REMHFW

Type in the title and the name for the object and click OK to complete its instantation.

1RWH��If you omit the name, the Project Structure Navigator uses a generated name. You can change both of these properties later by means of the General Object

B Automation 25


gatorUser’s Guide

Attributes dialog box. The title is a property by which you will identify the object in the project views.

,QVHUW�2EMHFW�LQ�WKH�XVHU�YLHZV

When you select the Insert Object function in a user view, the Add object from Master Design View dialog box appears, allowing you to select the object to be added to the currently selected location.

)LJ�� ,QVHUWLQJ�D�GHYLFH�REMHFW�WR�D�XVHU�YLHZ

To insert a device object, choose it from the object list and click OK to close the dialog box.

1RWH��All device objects that you have instantiated in the Master Design View are available for selection, however, you can insert a device object only once to a given user view.

This dialog box also allows you to instantiate Level objects, which you can use for organizing the contents of the user view. This is accomplished through the Add Level button, see Figure 3.8.1.-3.

To instantiate a Level object, either select the root node of the view or another Level object and click Add Level to enter the dialog box for providing the title of the object, see Figure 3.8.1.-4.

)LJ�� ,QVWDQWLDWLQJ�D�/HYHO�REMHFW�WR�D�XVHU�YLHZ

Provide a unique title in the view’s scope and click OK to close the dialog box.

3.8.2. Delete Object

.H\ERDUG�HQWU\��'HOHWH!

7RROEDU�HQWU\�

26 ABB Automation


AB

Operator’s Manual


m the to be

or s of

ation ects sign ject

tion s

To delete the currently selected object, use this function. You can delete only objects, which do not contain any subordinate objects.

If you are working in a user view, the deleted object remains in the project database and thus it can be re-added to any user view in the project. However, deleting an object from the Master Design View permanently removes the object from the project database, which in essence means erasing the object’s file storage frohard disk. Regarding device objects, deletion automatically causes the object silently removed from any user views.

3.8.3. Object Properties

.H\ERDUG�HQWU\��$OW!��5HWXUQ!

7RRO�EDU�HQWU\�

To bring up the General Object Attributes dialog box for the currently selectedobject, use this menu item.

Notice that, if you select the root node, this function brings up the dialog box fchanging/viewing properties of the project (in Master Design View) or propertiea user view (in a user view).

3.8.3.1. General Object Attributes dialog box

The General Object Attributes dialog box is a central tool for project object management. The dialog box contains two tabbed pages; General, Communicfor setting/viewing object's attributes. The General page is available for all objin all views, whereas the Communication page is displayed only in Master DeView for objects that require communication settings. Through the dialog box'sbuttons, you invoke the object's configuration dialog box, if supported by the obtype, and the dialog box for moving the object in the project hierarchy.

1RWH��The Communication page is not documented here. For detailed informaon configuring the communication settings, refer to the respective object type'configuration guide�

B Automation 27


gatorUser’s Guide

)LJ�� 7KH�*HQHUDO�2EMHFW�$WWULEXWHV�GLDORJ�ER[

3.8.3.2. Moving objects

Objects can be moved only within the current view. The procedure involves using the Move Object dialog box, see Figure 3.8.3.2.-1. The dialog box is invoked

Table 3.8.3.1-1 General Object Attributes dialog box items.

General page

Object Title field A read/write attribute in the Master Design View, read-only in user views.

Object Name field A read/write attribute in the Master Design View, read-only in user views.

Object Type field The type of the object, read-only in all views.Version field The version of the object’s type, read-only in all views.

Group field The group of the object’s type, read-only in all views.Remarks field Remarks on the object. A read/write attribute in the Master Design

View, read-only in user views. Note! Data is automatically truncated to 253 characters without notice.

Buttons

OK Closes the dialog box saving the changes to the object’s general attributes.

Cancel Closes the dialog box discarding the changes to the object’s general attributes.Note! This button does not have any impact on changes to the object’s configuration.

Move If the object’s type supports moving objects, invokes the dialog box for moving the object within the current view, otherwise this button is disabled. For details on moving objects, see section “Moving objects” on page 28

Attributes Invokes the dialog box for configuring the object. Enabled in Master Design View only, on condition that the object's type supports object configuration, otherwise this button is disabled.

28 ABB Automation


AB

Operator’s Manual


through the General Object Attributes dialog box (button Move). You can access this function only if the currently selected object’s type supports moving objects.

)LJ�� 7KH�0RYH�2EMHFW�GLDORJ�ER[

To move an object:

1. Select the object you intend to move.

2. From the Edit menu select Object Properties to open the General Object Attributes dialog box.

3. Click Move to open the Move Object dialog box.4. In the project structure, select the node, which will host the moved object.

Notice that you can work with the project tree in a normal manner, i.e. expand and collapse nodes.

5. On the Move Object dialog box, click Move Here to move the object. The Move Object dialog box closes causing the project structure to collapse. Notice that, if the Project Structure Navigator detects that the currently selected target node can not host the object you are about to move, you are not allowed to perform the move operation. In practice, clicking Move Here has no effect.

To cancel moving the object, click Cancel in the Move Object dialog box.

3.9. Views menu

The Views menu contains view manipulation functions and the list of user views, if such have been created in the current project. For example, in Figure 3.9.-1 below, the project contains one user view, titled User view 1.

)LJ�� 7KH�9LHZV�PHQX

3.9.1. Create View

Through this menu option it is possible to create new user views.

B Automation 29


gatorUser’s Guide

ject f the

ays

P 505

)LJ�� &UHDWLQJ�D�QHZ�YLHZ

New user views are created by defining the view name, that is the instance name, and the view description that is a logical name for the view. The root name is the name of the root node in the new view.

3.9.2. Delete View

This option deletes the current view, only user views can be deleted i.e. you cannot delete the Master Design View.

3.9.3. View Properties

By selecting this option can the current view’s properties be changed.

)LJ�� 7KH�3URMHFW�3URSHUWLHV�GLDORJ�ER[

Project properties are the project name, that is the instance name, and the prodescription that is a logical name for the project. The root name is the name oroot node in the project view.

3.9.4. View List

The view list is a list of all views defined for the project. By selecting one of theviews the navigator changes the active view. Only the Master Design View is alwavailable, user views are optional.

3.10. System Tools menu

The System Tools menu contains the tools that are available for use at the CAsystem level.

30 ABB Automation


AB

Operator’s Manual


tool

er

to/

ded

ct

)LJ�� 7KH�6\VWHP�7RROV�PHQX

This menu is customizable. You can modify the contents of this menu by selecting the Customize… option, see section “Customize...” on page 31. By default, menuitems for invoking the System Configuration Tool, the Plant Structure Settings and the DR-Collector tool are available.

For detailed information on the System Configuration tool, refer to the CAP 505 Installation and Commissioning manual.

For detailed information on the Plant Structure Settings tool, refer to the chapt“Plant Structure Settings” on page 41.

For detailed information on the DR Collector tool, refer to the Tools for Relays and Terminals manual.

3.10.1. Customize...

The Customize… menu alternative makes it possible to add and remove toolsfrom the System Tools menu.

)LJ�� 7KH�FXVWRPL]DWLRQ�GLDORJ�ER[

By selecting a system tool from the right hand list and clicking <<, the tool is adto the System Tools menu. And by selecting a tool from the left hand list and clicking Remove, the tool is removed from the System Tools menu.

3.11. Help menu

This menu contains the function for invoking the about dialog box of the ProjeStructure Navigator.

)LJ�� 7KH�+HOS�PHQX

B Automation 31


gatorUser’s Guide

3.11.1. About

.H\ERDUG�HQWU\��)�!

The mandatory About dialog box.

)LJ�� 7KH�$ERXW�GLDORJ�ER[�IRU�WKH�3URMHFW�6WUXFWXUH�1DYLJDWRU

1RWH��The information presented in this dialog box should be available when contacting ABB in a problem solving situation.

32 ABB Automation


AB

Operator’s Manual

User’s Guide 4. Project Export/Importtool

ject

take t s

4. Project Export/Import tool


This chapter describes the Project Export/Import Tool.

4.1. General

The Project Export/Import Tool is used when a project is to be transferred to another system or brought into your CAP 505 project collection, which comprises all projects stored under the directory \CAP505\PRJ.

)LJ�� 7KH�XVHU�LQWHUIDFH�RI�WKH�3URMHFW�([SRUW�,PSRUW�7RRO

The Project Export/Import Tool provides you with the following project-management functionality:

• Copying projects.

• Exporting projects from the CAP 505 project collection to an arbitrary user-defined location.

• Importing projects from an arbitrary user-defined location to the CAP 505 procollection.

• Deleting projects from the CAP 505 project collection.

• Duplicating projects in the CAP 505 project collection.

• Creating projects in the CAP 505 project collection.

!Regarding a project’s system configuration, you have to re-create it, when youinto use a project, which you have imported or copied to your CAP 505 projeccollection. Remember to verify that the device objects’ communication settingcomply with the newly created system configuration in such projects.

B Automation 33

1MRS751902-MUMOperator’s ManualCAP 5054. Project Export/Import

toolUser’s Guide

rk

PL ther

cal

y

ry

4.2. Features

4.2.1. Updating the project list

The operating principle of the Project Export/Import Tool is to first select a project collection to the list view. The project list is updated by choosing the Source... button. The project list can be one of the following:

• Your CAP 505 project collection. By default, the project list displays this selection.

• MicroSCADA application projects on a logical drive, either a local or a netwodrive.

• Projects stored in an arbitrary user-specified directory.

The project list displays project names in the format APL/ProjectName. When Ais CAP 505, it means that the project is in the CAP 505 project collection. Any oAPL indicates the MicroSCADA application and project name.

The Source... button invokes the following dialog box for choosing one of the alternatives above:

)LJ�� 7KH�3URMHFW�6RXUFH�'LUHFWRU\�GLDORJ�ER[

The MicroSCADA Apl On Drive and the Path entries allow you to access both loand network computers.

To use the MicroSCADA Apl On Drive option, specify the drive letter followed ba colon (:), for example 'R:'. The Path entry allows using the Universal NamingConvention (UNC) format in addition to the standard format: <drive:>\<directopath>. Sample UNC entries are provided below:

8VLQJ�D�VKDUH�QDPH

??:25.67$?%DFNXS?&$3��?3URMHFWV

where;

WORKSTA is the name of target computer.

BACKUP is a share name on the target computer.

CAP505\PROJECTS is a directory path under the share name.

8VLQJ�D�:LQGRZV�17�DGPLQLVWUDWLYH�VKDUH�QDPH

??:25.67$?&�?%DFNXS?&$3��?3URMHFWV

where;

WORKSTA is the name of target computer.

34 ABB Automation


AB

Operator’s Manual


and t unter cted

pes.

hut

PKS

For

ss.

lace ich

C$ is a Windows NT administrative share name on the target computer, the root directory of the drive ’C’.

BACKUP\CAP505\PROJECTS

is a directory path under the share name.

4.2.2. Project storage

Projects are stored in the PRJS directory in earlier CAP 505/501 releases, for example:

�'5,9(�!?6&?&$3��?35-6

In later CAP 505/501 releases they are stored in the PRJ directory, for example:

�'5,9(�!?&$3��?35-

The MicroSCADA application projects are stored under the following directory:

�'5,9(�!?6&?$3/?$3/1$0(?3527(&7,21?35-

where;

APLNAME is the name of the MicroSCADA application.

4.2.3. Copying projects between network computers

In network environments, projects can be copied from the local computer to/from other computers in the network. Other computers are referred to by using their computer name, which is a feature of the operating system. You should be granted full access to the share name if the intention is to copy projects to the network computer’s project database collection.

The destination can be one of the following alternatives:

• The CAP 505 project collection on the local computer.

• A MicroSCADA library application on a drive letter.

• A network directory.

• A MicroSCADA library application on a network computer.

Notice that, it is up to you to verify before the project is copied that, object typestools in the project are compatible or equal on the remote system. If the projeccontains objects of greater or foreign object types, the remote system may encoproblems if the project contains object types of other versions than what is expeby the object types and tools. Copying a project does not include the object ty

1RWH��In Hot Stand-by Basesystems (HSB) it is important that MicroSCADA is sdown while the project is being copied.

When a project is copied to a MicroSCADA application, it is copied to the application’s PROTECTION\PRJ directory, e.g. when the application is named the destination would be \SC\APL\PKS\PROTECTION\PRJ. Since a MicroSCADA library application can process one project only, it is named PRJ.example,�when a project is copied from a CAP 505 project collection to a MicroSCADA library application it is renamed to PRJ during the copying proce

If a project already exists in the destination directory, you are prompted to repthe project or abort the operation. Also, if you enter a destination directory wh

B Automation 35


toolUser’s Guide

e

'. In he

’.

o the

ported ecial-

e.

n be as a time

actually is the same as the source directory, you will be notified that the copying cannot continue.

The Copy To button brings up the dialog box shown in Figure 4.2.3.-1, for choosing a destination for the selected project in the project list view.

)LJ�� 7KH�&RS\�3URMHFW�GLDORJ�ER[

Enter the drive designation for the option MicroSCADA APL on Drive in format <drive letter><colon>, for example ‘C:’. Use the letter of the drive on which thMicroSCADA has been installed.

Enter a network computer name in UNC format, for example '\\L40017\MYPRJthis example, the computer name is L40017 and MYPRJ is the share name. Toption MicroSCADA APL on Network \\Computer\Share refers to the APL directory on the MicroSCADA computer, for example '\\L40017\D_root\SC\APLPress <Enter> when your option is either MicroSCADA APL on Drive or MicroSCADA APL on Network \\Computer\Share to update the MicroSCADA APL list with the desired MicroSCADA applications.

When you have selected the desired destination, click OK to copy the project tselected destination.

4.2.4. Choosing storage location for temporary projects

!With temporary projects are meant the compressed projects that have been exfrom CAP 505 or other product. It is recommended to save such projects in a sppurpose directory outside the directory structure of CAP 505, for example C:\EXPORTS. Especially, avoid using the directory \CAP505\TEMP for such purpose, since the CAP 505 kernel may choose to erase its contents at any tim

4.2.5. Exporting projects

Exporting a project means that all associated object entries in a project are duplicated to some other location specified by you. The destination location caon the local system or on a network drive: the destination location is specifieddirectory path, for example C:\EXPORTS. The directory path must exist at the you issue the export command.

36 ABB Automation


AB

Operator’s Manual


ry our ter h to t S.

.

t first rive

ple,

The output result, in the specified directory, is a compressed archive file with the file extension .AR. For example, if the project filename (which is also the actual directory name for the project) is KRISTIINANKAUPUNKI then the compressed archive file name is truncated to KRISTIIN.AR.

1RWH� When the project is later imported, the full project name must be used, although its compressed project filename is only eight (8) characters in length.

The object types used in the project are not exported along with the project hence the functionality in this sense is the same as with copying the projects, as described in section “Copying projects between network computers” on page 35.

)LJ�� 7KH�([SRUW�3URMHFW�GLDORJ�ER[

4.2.6. Importing projects

Importing a project is done in a similar way to exporting, except for the directoentry: the source directory is the location from where the project is copied to yproject collection. The source directory can be a directory on your local compusystem or on a network drive. The directory entry must be the full directory patthe project, for example C:\EXPORTS\KRISTIINANKAUPUNKI would mean thaa compressed project archive file 'KRISTIIN.AR' is in the directory C:\EXPORT

Notice that the project must be specified using its complete project filename although its compressed archive filename is only eight (8) characters in length

If the compressed archive was distributed to you on several diskettes, you muscopy the contents of all of the diskettes to a common directory on a hard disk dand import the project from there (see the note in the following figure).

)LJ�� 7KH�,PSRUW�3URMHFW�GLDORJ�ER[

The source directory is the path to the project in the export directory. For examif a project DEMO was exported to X:\EXPORTS then the source archive path

B Automation 37


toolUser’s Guide

he

would be X:\EXPORTS\DEMO (if the drive letter X: is mounted to the same location on both systems).

4.2.7. Project properties

The following dialog box shows the filename of the selected project:

)LJ�� 7KH�*HQHUDO�3URMHFW�3URSHUWLHV�GLDORJ�ER[

4.2.8. Deleting a project

Deleting a project is an irreversible operation that cannot be undone.

)LJ�� 2QFH�\RX�GHOHWH�D�SURMHFW��\RX�FDQQRW�UHFDOO�LW

4.2.9. Duplicating a project

Duplicating a project means that an exact copy of the selected project is copied to your CAP 505 project collection. During the process of duplication, you can specify a different project name and description. The project filename is actually a folder name (directory name) which then will become the project’s home directory. Tproject filename must not already exist.

1RWH��The Project Filename must be a single-word name without spaces or characters other than:

• A through Z and

• 0 through 9

38 ABB Automation


AB

Operator’s Manual


does ted

)LJ�� 7KH�'XSOLFDWH�3URMHFW�GLDORJ�ER[

4.2.10. Creating a new project

Creating a new project is done in a dialog box similar to duplicating a project. The newly created project is assigned an empty system configuration meaning that you have to setup its system configuration by means of the System Configuration tool. Regarding project creation, the same restrictions that apply to the project duplication apply also here, see section “Duplicating a project” on page 38.

4.2.11. Errors accessing remote disk resources

If you attempt read/write access to a disk resource on a remote computer, whichnot contain matching MicroSCADA user account, you will receive errors illustrain Figure 4.2.11.-1 and in Figure 4.2.11.-2.

)LJ�� 1RWLILFDWLRQ�DERXW�D�IDLOHG�H[SRUW�RSHUDWLRQ

)LJ�� 1RWLILFDWLRQ�DERXW�D�IDLOHG�LPSRUW�RSHUDWLRQ

B Automation 39


toolUser’s Guide

1RWH��The notification in Figure 4.2.11.-2 appears also if the specified project does not exist.

In order to recover from such situation, ensure that the target computer’s MicroSCADA user account is assigned the same password as on your local computer, see also Release Notes.

40 ABB Automation


AB

Operator’s Manual

User’s Guide 5. Plant Structure Settings

CAP

u in

oject

5. Plant Structure Settings


This chapter describes the functionality of the Plant Structure Settings tool.

5.1. General

In order to be able to define the attributes for the plant structure object types, that are global to the project, this system level tool is available. This tool provides the possibility to modify the pre-defined attributes and define the properties of the undefined levels in the object type. For more information on the plant structure object types, see chapter “Plant Structure object types” on page 43.

The lowest three levels are disabled because there are no use for them in the505/501 environment.

5.2. Starting the Plant Structure Settings tool

Start the tool by selecting Plant Structure Settings from the System Tools menthe Project Structure Navigator, see Figure 5.2.-1.

)LJ�� 6WDUWLQJ�WKH�3ODQW�6WUXFWXUH�6HWWLQJV�WRRO

5.3. Attributes of plant structures

The attributes of the plant structure are global to the project, i.e. in the same prthere cannot be several definitions of the plant structure’s attributes.

)LJ�� 3ODQW�6WUXFWXUH�6HWWLQJV�GLDORJ�ER[

The attributes that can be modified through this tool are:

• Level Id

• Level Description

B Automation 41

1MRS751902-MUMOperator’s ManualCAP 5055. Plant Structure Settings User’s Guide

nality

e it is

l in

dd

es’

• Field Length

These attributes are described in more detail in the following chapters.

The default values have been chosen on the basis of the corresponding functioin the MicroSCADA Network Control system.

1RWH� It is not recommended to change the default values, because in such casprobable that compatibility problems can occur when e.g. exporting projects toMicroSCADA.

5.3.1. Level Id

The Level Id attribute defines what the identifier is for recognizing a certain levea plant structure.

The defaults are:

• STA, that is used for recognizing station level objects.

• BAY, that is used for recognizing bay level objects.

• DEV, that is used for recognizing device level objects.

5.3.2. Level Description

The Level Description attribute is used for describing the different levels in the AObject dialog box when an object is instantiated.

The defaults are:

• Station

• Bay

• Device

5.3.3. Field Length

The Field Length attribute defines the maximum possible length of the instancnames when adding an object of the plant structure type to the project.

The defaults are:

• 10

• 15

• 5

42 ABB Automation


AB

Operator’s Manual

User’s Guide 6. Plant Structure objecttypes

mple, gal

to the

ng to cated

level. open

6. Plant Structure object types


This chapter describes the object types included in the plant structure object group.

6.1. Overview

The plant structure object types are intended to be used, when building MicroSCADA compatible project structures. It is possible to define five structure levels, although three of them are pre-defined. For more information on structure level definition, see chapter “Plant Structure object types” on page 43.

6.2. General

The plant structure object types are level sensitive. This means that, it is only possible to insert pre-defined objects under each level of the structure. For exait is not possible to insert a bay object under the root level, while it is perfectly leunder the station level.

6.3. Field length

The length of the instance name in the plant structure object type is restricted value defined for the level in the Plant Structure Settings, see chapter “Plant Structure object types” on page 43 for more information.

)LJ�� 1RWLILFDWLRQ�DERXW�WKH�LQVWDQFH�QDPH�OHQJWK

If the instance name is longer than defined in the Plant Structure Settings, thenotification shown in Figure 6.3.-1 appears. When this happens, the correct thido is to shorten the instance name to the maximum number of characters indiby the notification.

6.4. Station

The station level is intended to be used in conjunction with a subsequent bay Highlight the project's root node and select Insert Object from the Edit menu to the Add Project Object dialog box, see Figure 6.4.-1.

B Automation 43

1MRS751902-MUMOperator’s ManualCAP 5056. Plant Structure object

typesUser’s Guide

)LJ�� $GGLQJ�D�VWDWLRQ�OHYHO�REMHFW

Instantiate the station object by selecting the Plant Structure object group and then the Station object type and click OK to open the station level object dialog box, see Figure 6.4.-2. (Notice that, in the Project Structure Navigator’s status bar, the displayed object type is OI for objects of type Station).

)LJ�� $GGLQJ�D�6WDWLRQ�OHYHO�REMHFW

Type in an appropriate name and title for the object and click OK to have the station level object inserted.

The name of the object identifies the unique instance as the structure is built up. The instance name length is restricted to the number of characters defined in the Plant Structure Settings. The maximum length of the name is also displayed on the dialog box.

The title of the object is a symbolic description and it is visible in the Project Structure Navigator.

6.5. Bay

Highlight a station level object of a plant structure and select Insert Object from the Edit menu to open the Add Project Object dialog box, see Figure 6.5.-1.

44 ABB Automation


AB

Operator’s Manual

User’s Guide 6. Plant Structure objecttypes

)LJ�� $GGLQJ�D�%D\�OHYHO�REMHFW

Instantiate the bay object by selecting the Plant Structure object group and then the Bay object type and click OK to open the bay level object dialog box, see Figure 6.5.-2. (Notice that, in the Project Structure Navigator’s status bar, the displayed object type is OI for objects of type Bay).

)LJ�� $GGLQJ�D�%D\�OHYHO�REMHFW

Type in an appropriate name and title for the object and click OK to have the bay level object inserted.

The name of the object identifies the unique instance as the structure is built up. The instance name length is restricted to the number of characters defined in the Plant Structure Settings. The maximum length of the name is also displayed on the dialog box.

The title of the object is a symbolic description and it is visible in the Project Structure Navigator.

B Automation 45

1MRS751902-MUMOperator’s ManualCAP 5057. User Structure object

typesUser’s Guide

7. User Structure object types


This chapter describes the object types included in the User Structure object group.

7.1. Overview

User Structure object types are intended to serve as structurisation objects for structures that have some other structurisation requirements than MicroSCADA compatibility. The level structure can be built as deep as is required for the purpose intended.

7.2. General

The user structure object types can be used in both the Master Design View and in the user views.

The main difference between User Structure object types and Plant Structure object types is that the User Structure does not have the guided instantiation order which means that the levels and their purposes are defined by the user.

7.2.1. Instantiating Level objects

Highlight a level object and select Insert Object from the Edit menu to open the Add Project Object dialog box, see Figure 7.2.1.-1. Notice that in every view, the root node is also a Level object.

)LJ�� $GGLQJ�D�8VHU�6WUXFWXUH�REMHFW

To instantiate the level object, select the User Structure object group and then the Level object type. Click OK to open Add Level dialog box shown in Figure 7.2.1.-2.

)LJ�� $GGLQJ�D�/HYHO�REMHFW

Enter a title for the object and click OK to insert it into the tree structure. The title is visible in the Project Structure Navigator and it must be unique in the scope of its view i.e. in a single view you cannot have two Level objects having the same title.

46 ABB Automation


AB

Operator’s Manual

User’s Guide 8. Relay Download Tool

lay

.

the elay

8. Relay Download Tool


This chapter describes the functionality of the Relay Download Tool.

8.1. General

The Relay Download Tool performs bi-directional communication with relay units, allowing you to:

• Send Relay Configuration Tool configurations (Relay configuration) to the reterminal.

• Send Relay Mimic Editor pictures (Mimic configuration) to the relay terminal

• Send Relay Configuration Tool projects (RCT project) to the relay terminal.

• Receive Relay Mimic Editor pictures (Mimic configuration) from the relay terminal.

• Receive Relay Configuration Tool projects (RCT project) from the relay terminal.

• Send function block (FB) codes to the relay terminal.

• Read function block lists from the relay terminal.

• Read configuration counter values from the relay terminal.

• Reset the relay terminal.

• Store the current settings and data in the non-volatile memory of the relay terminal.

8.2. User interface

The Relay Download Tool window contains two pages. The Send page, whichcontains the functions for sending (downloading) data to the relay terminal andReceive page, containing the functions for receiving (uploading) data from the rterminal. To switch between the pages, click on the page title.

B Automation 47

1MRS751902-MUMOperator’s ManualCAP 5058. Relay Download Tool User’s Guide

)LJ�� 7KH�5HOD\�'RZQORDG�7RRO�ZLQGRZ

8.3. Menu commands

This section describes commands that are available from the menu bar, (1).

8.3.1. File menu

The File menu is used for terminating the Relay Download Tool session.

)LJ�� 7KH�)LOH�PHQX�RI�5HOD\�'RZQORDG�7RRO

8.3.1.1. Exit

By selecting this menu item the Relay Donwload Tool session terminates and you return to the Project Structure Navigator.

8.3.2. Help menu

The Help menu is used for invoking the Relay Download Tool’s About dialog box, which displays version information.

)LJ�� 7KH�+HOS�PHQX�RI�WKH�5HOD\�'RZQORDG�7RRO

8.3.2.1. About

By selecting this menu item you can view the Relay Download Tool’s version information.

48 ABB Automation


AB

Operator’s Manual


8.4. Relay communication functions

This section describes the relay communication functions, (2).

8.4.1. Send page

The Send page contains check boxes for selecting what to download to the relay terminal. Relay Configuration Tool configurations and projects and Relay Mimic Editor configurations are available. The download is executed by clicking the Send button.

)LJ�� 7KH�6HQG�SDJH

8.4.2. Receive page

The Receive page contains check boxes for selecting what to upload from the relay terminal. Relay Configuration Tool projects and Relay Mimic Editor configurations can be selected. The upload is executed by clicking the Receive button.

B Automation 49


)LJ�� 7KH�5HFHLYH�SDJH

8.4.3. The file transfer procedure

8.4.3.1. The progress indicator dialog box

The dialog box shown in Figure 8.4.3.1.-1, is shown during a file transfer procedure. The progress bar displays the percentage of the file’s size having been sent to/received from the relay terminal, also the actual filename is shown.

)LJ�� 7KH�SURJUHVV�LQGLFDWRU�GLDORJ�ER[

8.4.3.2. Error dialog boxes

The following error messages may appear during the file transfer:

,QFRUUHFW�FRPPXQLFDWLRQ�VHWWLQJV

The following error message appears when incorrect communication settings are applied.

50 ABB Automation


AB

Operator’s Manual


)LJ�� (UURU�PHVVDJH�IRU�LQFRUUHFW�FRPPXQLFDWLRQ�VHWWLQJV

5HOD\�QRW�UHVSRQGLQJ

The following error message appears when the relay is not responding.

)LJ�� (UURU�PHVVDJH�LQGLFDWLQJ�WKDW�WKH�UHOD\�GRHV�QRW�UHVSRQG

2WKHU�PHVVDJHV

Various other error messages not mentioned here, may appear when attempting to download erroneous configuration(s). Such configurations contain either, features that are unsupported by the targeted relay, or erroneous settings.

For instance, the following message is shown when the relay returns an error status, indicating that an unsupported feature has been applied in the configuration.

)LJ�� $Q�XQVXSSRUWHG�328�LV�LQFOXGHG�LQ�WKH�WUDQVPLWWHG�FRQILJXUDWLRQ

B Automation 51


5HOD\�V\VWHP�HUURUV

If the error message contains only an error code without description, a system error has occurred in the relay.

8.5. Relay command buttons

This section describes the relay command buttons, (3).

8.5.1. Store

The Store command saves current settings and data into relay’s non-volatile memory.

8.5.2. Reset

The Reset command resets the relay.

8.5.3. Counter

The Counter command displays the amount of configurations successfully sent to and stored in the relay, see Figure 8.5.3.-1.

)LJ�� 1XPEHU�RI�GRZQORDGHG�DQG�VXFFHVVIXOO\�VWRUHG�FRQILJXUDWLRQV�LQ�WKH�UHOD\

8.5.4. FB Code

The FB Code command allows you to activate function blocks in the relay. Enter the function block code into the text field and send it to the relay by clicking OK. The activated function blocks can be fetched using the FB List command, see section “FB List” on page 53.

)LJ�� )XQFWLRQ�EORFN�FRGH�GLDORJ�ER[

52 ABB Automation


AB

Operator’s Manual


8.5.5. FB List

The FB List button invokes the dialog box for viewing the activated function blocks in the relay. The function blocks are listed in ascending alphabetic order.

)LJ�� $FWLYDWHG�IXQFWLRQ�EORFNV�LQ�WKH�UHOD\

Notice, that you can copy the function block list onto the clipboard, using the Copy to Clipboard button.

To close the dialog, click Close.

B Automation 53

AB

CAP 505IndexUser’s Guide

Index

Operator’s Manual1MRS751902-MUM

Page&

CAP 505$SSOLFDWLRQV ................................................................................................................. 2%DVH�V\VWHP .................................................................................................................. 2,QWURGXFWLRQ .................................................................................................................. 1/RJLQ�ZLQGRZ ............................................................................................................. 220XOWLSOH�LQVWDQFHV�QRW�DOORZHG .................................................................................. 232SHUDWLRQDO�IHDWXUHV .................................................................................................... 14XLFN�VWDUW�H[DPSOH ..................................................................................................... 55HTXHVWHG�SURGXFW�LQIRUPDWLRQ�ZKHQ�FRQWDFWLQJ�$%% .............................................. 326WDUWLQJ ....................................................................................................................... 226WDUWLQJ�WKH�0LFUR6&$'$�VHUYLFH ................................................................................ 66WRSSLQJ�WKH�0LFUR6&$'$�VHUYLFH ............................................................................ 246XSSRUWHG�FRPPXQLFDWLRQ�SURWRFROV ............................................................................ 27RROV ............................................................................................................................. 19LHZLQJ�SURGXFW�YHUVLRQ�LQIRUPDWLRQ ......................................................................... 31

(Edit Menu'HOHWH�2EMHFW .............................................................................................................. 27,QVHUW�2EMHFW ............................................................................................................... 252EMHFW�3URSHUWLHV ....................................................................................................... 27

)Floppy disks,PSRUWLQJ�SURMHFWV�IURP�PXOWLSOH�IORSS\�GLVNV ........................................................... 37

Function blocks$FWLYDWLQJ�IXQFWLRQ�EORFNV�LQ�UHOD\V ........................................................................... 52)HWFKLQJ�DFWLYH�IXQFWLRQ�EORFNV�IURP�UHOD\V .............................................................. 53

.Kernel6WDUWLQJ�WKH�0LFUR6&$'$�VHUYLFH ..........................................................................6, 226WRSSLQJ�WKH�0LFUR6&$'$�VHUYLFH ............................................................................ 24

0Master Design View,QVWDQWLDWLRQ�RI�REMHFWV ............................................................................................... 25

Menus(GLW�0HQX ................................................................................................................... 24)LOH�PHQX .................................................................................................................... 23)LOH�PHQX��5HOD\�'RZQORDG�7RRO ............................................................................... 48+HOS�PHQX .................................................................................................................. 31+HOS�PHQX��5HOD\�'RZQORDG�7RRO ............................................................................. 486\VWHP�7RROV�PHQX ...............................................................................................30, 319LHZV�0HQX ................................................................................................................ 29

MicroSCADA Network Control system3ODQW�VWUXFWXUH�FRPSDWLELOLW\ ...................................................................................... 42

MicroSCADA service6WDUWLQJ�WKH�0LFUR6&$'$�VHUYLFH ..........................................................................6, 226WRSSLQJ�WKH�0LFUR6&$'$�VHUYLFH ............................................................................ 24

B Automation

1MRS751902-MUMOperator’s ManualCAP 505Index User’s Guide

2Object type groups&$3��REMHFW�W\SH�JURXSV ...................................................................................... 21*DWHZD\ ..................................................................................................................... 213ODQW�6WUXFWXUH ........................................................................................................... 213URWHFWLRQ��&RQWURO ................................................................................................. 218VHU�6WUXFWXUH ............................................................................................................ 21

Object types&$3��REMHFW�W\SHV ................................................................................................. 218VHU�6WUXFWXUH�REMHFW�W\SH ......................................................................................... 46

Objects%DVLF�REMHFW�SURSHUWLHV .............................................................................................. 25&RQILJXUH�REMHFWV ....................................................................................................... 28'HOHWLQJ�REMHFWV ......................................................................................................... 27*HQHUDO�REMHFW�DWWULEXWHV ........................................................................................... 27,QVHUWLRQ�RI�REMHFWV�LQ�WKH�XVHU�YLHZV ......................................................................... 26,QVWDQWLDWLQJ�REMHFWV ................................................................................................... 25,QVWDQWLDWLRQ�RI�/HYHO�REMHFWV�LQ�WKH�XVHU�YLHZV ......................................................... 26,QVWDQWLDWLRQ�RI�REMHFWV�LQ�WKH�0DVWHU�'HVLJQ�9LHZ ................................................... 250RYH�REMHFWV .............................................................................................................. 283URFHGXUH�IRU�PRYLQJ�REMHFWV .................................................................................... 296DYH�FKDQJHV�WR�REMHFWV�JHQHUDO�DWWULEXWHV ............................................................... 289LHZ�FKDQJH�REMHFWV�QDPH ........................................................................................ 289LHZ�FKDQJH�REMHFWV�WLWOH ........................................................................................... 289LHZLQJ�REMHFW�SURSHUWLHV .......................................................................................... 27

3Plant structure object attributes)LHOG�/HQJWK ............................................................................................................... 42/HYHO�'HVFULSWLRQ ....................................................................................................... 42/HYHO�,G ...................................................................................................................... 42

Plant structure object types%D\�REMHFWV ................................................................................................................. 442YHUYLHZ .................................................................................................................... 436WDWLRQ�REMHFWV ............................................................................................................ 43

Plant structure objects,QVHUWLRQ�FRQVWUDLQWV .................................................................................................. 430RGLILDEOH�DWWULEXWHV ................................................................................................. 42

Plant Structure Settings tool2YHUYLHZ .................................................................................................................... 416WDUWLQJ�WKH�WRRO ......................................................................................................... 41

Project Export/Import Tool$FFHVVLQJ�QHWZRUN�SURMHFWV ........................................................................................ 34&RS\LQJ�SURMHFWV�EHWZHHQ�QHWZRUN�FRPSXWHUV .......................................................... 35&UHDWLQJ�SURMHFWV ....................................................................................................... 39'HOHWLQJ�SURMHFWV ........................................................................................................ 38'XSOLFDWLQJ�SURMHFWV .................................................................................................. 38([SRUWLQJ�SURMHFWV ...................................................................................................... 36*HQHUDO�SURMHFW�SURSHUWLHV ......................................................................................... 38,PSRUWLQJ�SURMHFWV ...................................................................................................... 372YHUYLHZ .................................................................................................................... 336HOHFWLQJ�SURMHFWV ....................................................................................................... 346WRUDJH�ORFDWLRQ�IRU�WHPSRUDU\�SURMHFWV .................................................................... 368VHU�LQWHUIDFH ............................................................................................................ 33

Project Structure Navigator

ABB Automation


AB

Index

Operator’s Manual

User’s Guide

&KDQJLQJ�9LHZLQJ�3URMHFW�SURSHUWLHV ........................................................................ 30&ORVLQJ�WKH�FXUUHQW�SURMHFW ........................................................................................ 24&UHDWLQJ�XVHU�YLHZV .................................................................................................... 29&XVWRPL]DEOH�6\VWHP�7RROV�PHQX ............................................................................... 31'HOHWLQJ�REMHFWV�IURP�SURMHFW ..................................................................................... 27'HOHWLQJ�XVHU�YLHZV .................................................................................................... 30(GLW�PHQX ................................................................................................................... 24(QWHULQJ ...................................................................................................................... 22([LWLQJ�WKH�VHVVLRQ ...................................................................................................... 24)LOH�PHQX .................................................................................................................... 23+HOS�PHQX .................................................................................................................. 31,QVWDQWLDWLQJ�REMHFWV�WR�SURMHFW ................................................................................... 25/LVW�RI�YLHZV ................................................................................................................ 300HQX�EDU .................................................................................................................... 222EMHFW�WRROV�OLVW .......................................................................................................... 222SHQLQJ�SURMHFWV ........................................................................................................ 232YHUYLHZ .................................................................................................................... 203URMHFWV ...................................................................................................................... 206WDWXV�EDU ................................................................................................................... 226WUXFWXUH ..................................................................................................................... 227RRO�EDU ...................................................................................................................... 228VHU�LQWHUIDFH ............................................................................................................. 229LHZLQJ�REMHFW�SURSHUWLHV ........................................................................................... 279LHZV�PHQX ................................................................................................................. 29

Projects$FFHVVLQJ�QHWZRUN�SURMHFWV ........................................................................................ 34%XLOW�LQ�0DVWHU�'HVLJQ�9LHZ ...................................................................................... 20&KDQJLQJ�9LHZLQJ�SURMHFW�SURSHUWLHV ........................................................................ 30&ORVLQJ�WKH�FXUUHQW�SURMHFW ........................................................................................ 24&RS\LQJ�SURMHFWV�EHWZHHQ�QHWZRUN�FRPSXWHUV ........................................................... 35&UHDWLQJ�SURMHFWV ........................................................................................................ 39'HOHWLQJ�REMHFWV�IURP�SURMHFW ..................................................................................... 27'HOHWLQJ�SURMHFWV ........................................................................................................ 38'XSOLFDWLQJ�SURMHFWV ................................................................................................... 38([SRUWLQJ�SURMHFWV ...................................................................................................... 36*HQHUDO�SURMHFW�SURSHUWLHV ......................................................................................... 38,PSRUWLQJ�SURMHFWV ...................................................................................................... 37,PSRUWLQJ�SURMHFWV�IURP�PXOWLSOH�IORSS\�GLVNV ........................................................... 37,QVWDQWLDWLQJ�REMHFWV�WR�SURMHFW ................................................................................... 250D[LPXP�QXPEHU�RI�SURMHFWV ..................................................................................... 202SHQLQJ�SURMHFWV ........................................................................................................ 232YHUYLHZ .................................................................................................................... 202YHUYLHZ�RI�SURMHFW�YLHZV .......................................................................................... 203ODQW�VWUXFWXUH�DWWULEXWHV ........................................................................................... 413URFHGXUH�IRU�PRYLQJ�REMHFWV .................................................................................... 293URMHFW�OLVW .................................................................................................................. 346HOHFWLQJ�SURMHFWV�LQ�WKH�3URMHFW�([SRUW�,PSRUW�7RRO ................................................. 346SHFLI\LQJ�SDWKV�LQ�8QLYHUVDO�1DPLQJ�&RQYHQWLRQ�81&�IRUPDW .............................. 346WRUDJH�ORFDWLRQ�IRU�WHPSRUDU\�SURMHFWV .................................................................... 366WRUDJH�ORFDWLRQ�LQ�&$3�� .............................................................................. 357RRO�IRU�SURMHFW�PDQDJHPHQW ..................................................................................... 339LHZLQJ�FKDQJLQJ�REMHFW�DWWULEXWHV ............................................................................ 27

B Automation

1MRS751902-MUMOperator’s ManualCAP 505Index User’s Guide

5Relay Download Tool&RXQWHU�FRPPDQG ...................................................................................................... 52'LVSOD\LQJ�YHUVLRQ�LQIRUPDWLRQ ................................................................................. 48(UURU�PHVVDJHV .......................................................................................................... 50)%�FRGH�FRPPDQG ..................................................................................................... 52)%�OLVW�FRPPDQG ........................................................................................................ 53)LOH�PHQX ................................................................................................................... 48+HOS�PHQX .................................................................................................................. 482YHUYLHZ .................................................................................................................... 475HFHLYH�SDJH .............................................................................................................. 495HOD\�FRPPXQLFDWLRQ�IXQFWLRQV ................................................................................. 495HVHW�FRPPDQG .......................................................................................................... 526HQG�SDJH ................................................................................................................... 496WRUH�FRPPDQG ........................................................................................................... 527HUPLQDWLQJ�WKH�VHVVLRQ ............................................................................................. 48

6Session([LWLQJ�WKH�VHVVLRQ ..................................................................................................... 24

System Tools&XVWRPL]LQJ ............................................................................................................... 31

8Universal Naming Code6SHFLI\LQJ�SDWKV�LQ�81&�IRUPDW ................................................................................ 34

User Structure object types2YHUYLHZ .................................................................................................................... 468VDELOLW\�LQ�SURMHFW�YLHZV .......................................................................................... 46

User views,QVHUWLRQ�RI�REMHFWV .................................................................................................... 26,QVWDQWLDWLRQ�RI�/HYHO�REMHFWV ..................................................................................... 26

9Views&UHDWLQJ�XVHU�YLHZV ................................................................................................... 29'HOHWLQJ�XVHU�YLHZV .................................................................................................... 30/LVW�RI�YLHZV ............................................................................................................... 300DVWHU�'HVLJQ�9LHZ ................................................................................................... 202YHUYLHZ .................................................................................................................... 208VHU�YLHZV .................................................................................................................. 20

ABB Automation


AB

Customer Feedback

Operator’s Manual

User’s Guide

cribe or ude nd

d

ment

ate isted

d

get a

1MRS751902-MUM

Customer Feedback

About This Chapter

This chapter contains information on how to send customer feedback.

Customer Feedback Database

Customer Feedback is a Lotus Notes database which ABB companies can use to report errors, make improvement proposals and queries related to products manufactured by ABB Substation Automation Oy. The Customer Feedback database is connected to the change management system of ABB Substation Automation Oy, which handles all error corrections and improvements, made to the products.

Please note that the Customer Feedback database is primarily intended for writing reports about released products. If you are using for example a beta release in a pilot project, this should be clearly stated.

Writing A Customer Feedback Report

When writing a Customer Feedback report the following general instructions should be taken into consideration:

• Write the report in English.

• Write only one error report, query or improvement proposal in a Customer Feedback Report.

• If you are reporting an error, try to isolate the error as good as possible. Desthe sequence of events and actions causing the error. If any error messagesother debug information is provided by the system, please write it down. Inclalso information of the system, e.g. a system diagram, revision information aconfiguration data.

• If you are making an improvement proposal, try to describe how the improvefunction should work. Avoid providing solutions. Information about the importance of the improvement, e.g. number of projects that require the improvement, helps us to make the decision whether and when the improveshould be implemented.

To make a Customer Feedback Report, select Feedback Report from the Cremenu. This opens an empty Customer Feedback document. Fill out the fields lbelow. A question mark next to a field provides help for filling out the field.

� Subject. This should contain a short description of the issue. A more detailedescription can be given in the Description of Feedback field below.

� Type of Feedback: Comment/Improvement, Query or Complaint/Error.

� Customer Information.

� Reporting Information. This should contain detailed information about the product that is handled in the report.

� The person who you want to send the feedback to and whether you want toreply from that person or not.

B Automation

1MRS751902-MUMOperator’s ManualCAP 505Customer Feedback User’s Guide

t is alyser

m of and y and

ses.

stem,

new

ill e

� Information related to internal handling of the report (not obligatory).

� Category.

You can issue the report by clicking the Issue Feedback button. This will send the report to the selected person and change its status to “in progress”.

Actions

When ABB Substation Automation Oy receives a Customer Feedback report ianalysed by a sales person or a representative of the technical support. The anmay ask for additional information in order to complete the analysis. After the report has been analysed, the following actions are taken:

• In case of a clear error the report is moved to the change management systeABB Substation Automation Oy. In this system the error is analysed in detail corrected in a future patch release or major release depending on the severitimpact of the error.

• In case of an improvement proposal the report is also moved to the change management system where it is considered as a requirement for future relea

• In case of a query an answer is provided.

When Customer Feedback reports are handled in the change management sythe outcome can be one of the following:

No Actions This means that it is decided that thereport requires no further action. If forexample the problem is caused by a configuration error, it belongs to this category.

Will be implemented in patch/current releaseThis means that the correction orfeature will be available in the next official program release.

Moved to future release This means that the new feature wbe available in a new program releasin the near future.

ABB Automation

Documents

CAP505 Operators_Manual