1MRS751253-MEN MicroSCADA Issue date: 29.02.00 · PDF fileThe information in this document is subject to change without ... Each application has its own directory branch on ... activation

1MRS751253-MENIssue date: 29.02.00

Program revision: 8.4.3

Documentation version: A

Copyright © 2000 ABB Substation Automation OyAll rights reserved.

MicroSCADAApplication Objects

Notice 1

The information in this document is subject to change without notice and should notbe construed as a commitment by ABB. ABB assumes no responsibility for any errorthat may occur in this document.

Notice 2

This document version complies with the program revision 8.4.3.

Notice 3

Additional information such as Release Notes and Last Minute Remarks can be foundon the program distribution media.

Trademarks

Microsoft is a trademark of Microsoft Corporation.

Windows NT is a trademark of Microsoft Corporation.

LONWORKS is a registered trademark of Echelon Corporation.

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

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

MicroSCADA Application ObjectsTechnical Reference Manual

1MRS751253-MEN

ABB Automation

Related SYS 500 and MicroSCADA Technology Manuals

The following SYS 500 manuals are published with this software release.

Installation 1MRS751254-MEN

Picture Editing 1MRS751255-MEN

Visual SCIL User Interface Design 1MRS751256-MEN

Visual SCIL Objects 1MRS751257-MEN

System Management 1MRS751258-MUM

The following MicroSCADA technology manuals are published with this softwarerelease.

Connecting LONWORKS Devices to MicroSCADA 1MRS751249-MEN

System Configuration 1MRS751248-MEN

System Objects 1MRS751252-MEN

Application Objects 1MRS751253-MEN

Programming Language SCIL 1MRS751250-MEN

Status Codes 1MRS751251-MEN

1MRS751253-MEN Application ObjectsTechnical Reference Manual

MicroSCADA

ABB Automation

Contents

Page

1 Introduction ....................................................................................1

2 Object Handling .............................................................................7

2.1 Defining Application Objects.............................................................. 7

2.2 Using Application Objects in SCIL ..................................................... 8

2.3 Some SCIL Commands................................................................... 12

3 Process Objects...........................................................................15

3.1 General ........................................................................................... 15

3.2 Configurable Process Object Attributes ........................................... 23

3.2.1 Basic Definition Attributes......................................................... 23

3.2.2 Identification Attributes ............................................................. 25

3.2.3 Addresses ................................................................................ 26

3.2.4 Operational State...................................................................... 29

3.2.5 Unit and Scale .......................................................................... 31

3.2.6 Limit Value Supervision ............................................................ 33

3.2.7 Alarm Handling ......................................................................... 36

3.2.8 Event Handling ......................................................................... 42

3.2.9 Saving the Event History .......................................................... 47

3.2.10 Printout Handling ...................................................................... 51

3.2.11 Miscellaneous Attributes........................................................... 54

3.3 Dynamic Process Object Attributes ................................................. 56

3.3.1 Object Value............................................................................. 57

3.3.2 Time and Validation Stamps..................................................... 61

3.3.3 Alarm and Warning States........................................................ 63

3.3.4 Blocking Attributes.................................................................... 66

3.3.5 Operation Counters Attributes .................................................. 68

3.3.6 Minimum and Maximum Values................................................ 69

3.3.7 Stamps Set by the Communication System.............................. 71

3.3.8 S.P.I.D.E.R. RTU Specific Attributes ........................................ 74


1MRS751253-MEN

ABB Automation

3.3.9 IEC Specific Attributes ..............................................................75

3.3.10 File Transfer Attributes..............................................................77

3.3.11 Event History Attributes.............................................................81

3.4 Defining Process Objects.................................................................84

3.5 Process Object Group Attributes......................................................85

4 Scales............................................................................................87

4.1 General ............................................................................................87

4.2 Scale Attributes................................................................................88

4.3 Defining SCALE Objects Using SCIL ...............................................90

5 Data Objects .................................................................................91

5.1 General ............................................................................................91

5.2 Data Object Attributes......................................................................95

5.2.1 Basic Definition .........................................................................95

5.2.2 Execution Definitions.................................................................98

5.2.3 Registered Data ......................................................................100

5.2.4 Execution Control....................................................................102

5.2.5 Storage ...................................................................................103

5.3 Defining Data Objects Using SCIL .................................................105

6 Command Procedures...............................................................107

6.1 General ..........................................................................................107

6.2 Command Procedure Attributes.....................................................109

6.2.1 Basic Attributes .......................................................................109

6.2.2 Program ..................................................................................111

6.2.3 Time and Validation Stamps ...................................................111

6.2.4 Execution Control....................................................................112

6.2.5 Storage Attributes ...................................................................114

6.3 Defining Command Procedures with SCIL .....................................115

7 Time Channels............................................................................117

7.1 General ..........................................................................................117

7.2 Time Channel Attributes.................................................................119

7.2.1 Basic Attributes .......................................................................120

7.2.2 Operational Status ..................................................................120


MicroSCADA

ABB Automation

7.2.3 Initialisation and Execution ..................................................... 121

7.2.4 Parallel Execution................................................................... 123

7.2.5 Time Tagging.......................................................................... 124

7.2.6 Comment................................................................................ 125

7.3 Defining Time Channels with SCIL ................................................ 126

8 Event Channels ..........................................................................127

8.1 General ......................................................................................... 127

8.2 Event Channel Attributes............................................................... 130

8.3 Predefined Event Channels ........................................................... 132

8.4 Defining Event Channels with SCIL ............................................... 136

9 Event Objects .............................................................................137

10 Variable Objects.........................................................................141

11 Free Type Objects (F) ................................................................143

11.1 General ......................................................................................... 143

11.2 Type Defining Attributes ................................................................ 145

11.3 Attributes for Defining Attributes .................................................... 146

11.4 Defining Free Type Objects ........................................................... 151

12 Using Object Definition Tools...................................................153

12.1 Object Navigator............................................................................ 153

12.2 Creating and Editing Objects ......................................................... 165

12.3 General Principles for Using Object Definition Tools ..................... 174

13 Process Object Definition Tool.................................................177

13.1 Overview ....................................................................................... 177

13.2 Common Area ............................................................................... 178

13.3 Configurable Attributes .................................................................. 179

13.4 Dynamic Attributes ........................................................................ 186

13.5 All Attributes .................................................................................. 190

14 Scale Object Definition Tool .....................................................191

15 Data Object Definition Tool .......................................................195


1MRS751253-MEN

ABB Automation

16 Command Procedure Definition Tool.......................................203

17 Time Channel Definition Tool....................................................209

18 Event Channel Definition Tool ..................................................217

19 Free Type Object Definition Tools ............................................221

19.1 Free Type Process Object Tool......................................................221

19.2 Free Type Object Tool ...................................................................223

1 Introduction2 Object Handling3 Process Object4 Scales5 Data Objects6 Command Procedures7 Time Channels8 Event Channels9 Event Objects

10 Variable Objects11 Free Type Objects (F)12 Using Object Definition Tools13 Process Object Definition Tool14 Scale Object Definition Tool15 Data Object Definition Tool16 Command Procedure Definition Tool17 Time Channel Definition Tool18 Event Channel Definition Tool19 Free Type Object Definition Tools

234

567

89

101112131415

161718

19

1


MicroSCADA1 Introduction

ABB Automation 1

1 Introduction

About this Chapter

This chapter introduces the MicroSCADA supervisory control system and describesthe role of application objects.

MicroSCADA

MicroSCADA is a microcomputer-based, programmable and distributed supervisorycontrol and data acquisition (SCADA) system. It is mainly used for remote and localsupervision and control of electricity and distribution on medium voltage level. It canalso be used for the supervision and control of heat and water distribution, industrialprocesses, water purification, traffic, etc.

The “control centers” of MicroSCADA are named base systems. These computers runthe supervisory control software. The MicroSCADA base system software is com-posed of the MicroSCADA kernel (main program), a number of facility programs, en-gineering and system handling tools, configuration software and application software.

The MicroSCADA kernel software is independent of the application area and extentof use. It is the same in all base systems. So are also most of the engineering and sys-tem handling tools. The configuration software is specified for the base system inquestion and adapted to the device configuration of the entire MicroSCADA distrib-uted system.

A base system contains one or more application software packages, called applica-tions. The application software specifies the functions of the MicroSCADA base sys-tem as a supervisory control system to suit for a certain process. The application soft-ware takes into account the user’s needs regarding the level of information, user inter-face, control operations, and so on.

Applications

Each application has a certain supervisory control task, for example, the control ofelectricity distribution or heat distribution. An application may control its own proc-ess and have its own connections to the process equipment, or it may share theequipment with other applications. Each application has its own directory branch onhard disk (see the System Management manual), and its own databases in the primarymemory and on hard disk. Different applications can communicate transparentlythrough SCIL statements, whether they are situated in the same base system or inseparate ones.

In simple terms, you could say that an application is composed of a set of objects thatcommunicate with each other, with the user and with the process equipment, seeFigure 1. The objects are of two categories:

• User interface objects (such as pictures, dialogs and dialog items) which form theuser interface of the application, the screen views. An application may contain


Application ObjectsTechnical Reference Manual

1MRS751253-MEN

ABB Automation2

several pictures. An hour glas cursor is shown while the picture is changed. Forsemigraphic pictures the hour glas is shown only when the monitor is of typeVS_LOCAL or VS_REMOTE.

• Application objects that specify control functions, calculations, data storage, pro-cess control, etc. The application objects are composed of process data (processobjects), report data (data objects), control programs (command procedures) andactivation mechanisms (event channels, time channels and event objects).

User interface objects as well as application objects are programmed and controlledusing SCIL language, which is an application language specifically developed for Mi-croSCADA.

User interface objects are described in the manuals Picture Editing, Visual SCIL UserInterface Design, and Visual SCIL Objects, while this manual describes the applica-tion objects.

Object inter-communication

Figure 1. A simplified scheme of a MicroSCADA application

Application Objects

Application objects are programmable units that perform various tasks, such as realtime process supervision, control procedures, data registration and storage, calcula-tions, automatic time and event activation, etc. There are nine types of applicationobjects, each performing a particular task:

1. Process objects (P). Process objects are images of connected process signals.These objects store and supervise the real time state of the process.

2. Scales (X). Scales are algorithms for scaling the data transferred from the stationsto the real values of the measured entity.

3. Data objects (D). Data objects register and store sampled or calculated data.



ABB Automation 3

4. Command procedures (C). These objects are SCIL programs, which can beexecuted automatically or manually.

5. Time channels (T). These objects control the automatic time based dataregistrations and program executions.

6. Event channels (A). These objects control automatic event based data registrationand program execution.

7. Event objects (E). These objects activate automatic event controlled programexecution (for example updating) in user interface objects.

8. Variable objects (V). Variable objects are temporary lists of attributes andattribute values.

9. Free Type objects (F). Free Type objects define user-defined process objecttypes.

The first seven types are illustrated in Figure 2.

The capital letter after each type in the list above is an identification mark for the ob-ject type when used in SCIL. All types of SCADA objects, except variable objects,are global and accessible using SCIL throughout the entire MicroSCADA network.



1MRS751253-MEN

ABB Automation4

Scales

ProcessObjects

CommandProcedures

#SET#EXEC#PRINT

TimeChannels

EventChannels

EventObjects

Data Objects

Basesystem

Application User interface objects

Applicationobjects

Figure 2. An illustration of the application objects and their interconnections



ABB Automation 5

Attributes

Information and data associated with objects - their values, functions, properties andactivities - are stored in attributes. An object normally has many different attributesand, thus, it can contain several types of data. Different object types have differentsets of attributes.

The attributes not only contain the dynamic data of the objects but also define theobjects and their functions. For example static (defining) attributes are the objectnames, addresses, activation criteria, activity states, connections to other objects,alarm handling specifications, SCIL programs and expressions. Examples of dynamicattributes are the object values, historical data, status codes and time tags. Figure 3shows an imaginary object (data object) and its static (defining) and dynamic attrib-utes.

Copied from:

Name:

Activated by:

Data:

Validation Stamp:

Time Stamp:

SAMPLE

TC_1H

ORIGIN

0.785

OK

12:00:00

Figure 3. An imaginary object (data object) and few of its static and dynamic at-tributes

Attribute values can be used in SCIL expressions and programs, for example in cal-culations, displays, conditional statements, etc. The values can be changed automati-cally by the process or system, or manually using SCIL. All dynamic and static attrib-utes can be accessed using SCIL, though all of them cannot be set using it.

As a rule, attributes are the only way to store, access, use and modify information inobjects and to operate through them. Attributes are therefore the most essential part ofobjects.

Defining Application Objects

Creation and definition of application objects is a part of application engineering, thatis the composition of an application software package. The object definitions mayalso be modified in a running application. Objects can be created and modified asfollows:

• Using type specific definition tools. In the object definition tools, objects are de-fined by filling in data and making appropriate choices.

• Using the standard application library LIB 500. Creation of objects using thestandard application library is mostly invisible to the user.



1MRS751253-MEN

ABB Automation6

• Using SCIL commands. This is the basic method and the other two methods areactually based on this one, because the tools are built with SCIL.

Event objects are event based activation signals that execute picture program parts.They are generated by process objects or by SCIL. These objects have no attributesand no other definitions beside activation criteria, and the object name when activatedby SCIL. The picture program parts activated by the event objects are stored withinthe pictures in the picture database and can be activated only when the picture is visi-ble on the screen.

Variable objects are always created with SCIL. The variable objects are used as vari-ables and as temporary storages for data.

Databases

Most application object types are stored in databases (a database is a set of relateddata stored in a structured form).

The process objects, scales and free type objects are stored in the Process Database.The data objects, command procedures, time channels and event channels are storedin a database named Report Database, and these objects are called report objectswith a common name.

Variable objects are stored in the same way as variables (The Programming LanguageSCIL manual, Chapter 5). Event objects are not stored.

Each application may only contain one process database and one report database. Theprocess and report database files are described in the System Management manual.


MicroSCADA2 Object Handling

ABB Automation 7

2 Object Handling

This chapter presents the principles on how to define application objects and how touse the objects in SCIL. It is divided into the following three sections:

2.1 Defining application objects: the possibilities for defining objects, theprinciples for using the object definition tools, the principles for definingobjects with SCIL.

2.2 Using application objects in SCIL: the object notation and how to useobject notations in SCIL, accessing attributes.

2.3 Some SCIL commands for application object handling.

2.1 Defining Application Objects

As mentioned in Chapter 1, application objects can be created (defined) and modifiedin three ways:

• Using application object definition tools.

• Using the standard application library LIB 500.

• By typing SCIL programs.

Using Definition Tools

By using application object definition tools, the engineer defines the objects’ one byone by entering attributes in fields or by making selections from various options.

The user interface of the application object definition tools depends on the type of theMicroSCADA monitor you are using. When you open a MicroSCADA monitor, youchoose a monitor type, either “X” type or “VS” type. In VS type monitors, the toolsare composed of SCIL dialogs. In X type monitors, the tools are composed of semi-graphic pictures.

Generally, there is no need to use X type monitors (only in special cases), and there-fore this manual will describe the tools based on dialogs. If you have a semi-graphicmonitor or a monitor configured as X type, see the MicroSCADA 8.2 Object De-scription manual to learn how to use them.

The application object definition tools are accessed from the Tool Manager by dou-ble-clicking the Object Navigator. In the Object Navigator the user can view objectlists, access the definition of selected objects, add new objects, copy objects withinthe same application or from one application to another, delete objects, etc.

The application object definition tools are described in Part II of this manual. TheObject Navigator and the principles for using the object definition tools are discussedin Chapter 12.



1MRS751253-MEN

ABB Automation8

Although objects have been created with SCIL or with the LIB 500 tools, you canview and edit them using the object definition tools.

Using LIB 500

LIB 500 is a set of standard application libraries for fast standardised application en-gineering. The LIB 500 libraries contain various types of application components.The application engineer uses these components to compose a complete application.The composition is done using the picture based library tools. The library tools createrequired application objects collectively. The programmer only gives some basic in-formation.

Defining Objects with SCIL

New application objects can be created with the SCIL command #CREATE, objectscan be modified with the #MODIFY command and objects can be deleted with the#DELETE command. See the brief description of SCIL commands in Chapter 2 or thecomplete description in the Programming Language SCIL manual.

In fact, application objects are always created, modified and deleted with SCIL, sinceboth the definition tools and the library tools are built with SCIL.

2.2 Using Application Objects in SCIL

General

In SCIL the application objects are used mainly through their attributes. Object datacan be included in SCIL programs and expressions via the attributes. Object data can,for instance, be shown in windows, it can form the basis for control operations or beused in the definition of other objects, etc. Objects and their attributes are identifiedby an object notation, see below.

All types of objects can be used in SCIL. However, the event objects cannot be in-cluded in expressions as they have no data and no attributes.

Object Notation

Object notations have the following format:

name:{application}type{attribute}{index}

where

’name’ Is the object name

’application’ Is the logical application number

’type’ Is the object type

’attribute’ Is an attribute name



ABB Automation 9

’index’ Is an index number

The information within brackets is not always obligatory. The parameters are ex-plained below. See the examples below under the headline Using Object Notation.

Name

The names of data objects, command procedures, time channels and event channelsmay contain max. 10 characters. The names of process, scale, event, variable and freetype objects may contain max. 63 characters.

Characters allowed are the letters A - Z, all digits, underscore (_) and points (.). Theobject name must begin with a letter, a digit or an underscore.

Object names can be freely chosen. Within an application, the object name must beunique for a specific object type, but objects of different types may have the samename.

Examples of correct object names:

RELA_123

1.RELA

BREAKER_92

Examples of incorrect object names:

RELÄ Contains an extended character (Scandinavian letter)

BREAKER 1 Contains a blank space

Process objects defined in LIB 500 must obey tighter rules: a maximum of nine char-acters is allowed for relay picture functions and ten characters for all the other typesof picture functions. The names must not start with a number.

Application

Application is the logical number of the application where the object is stored. It isthe application number as known to the present application (according to the applica-tion mapping, the APL:BAP attribute, see the System Objects manual). The numbercan be omitted when the object is in the current application (the normal case).

Including an application number (other than the current one) in an object notationbrings about a data transfer between two applications, within the same or differentbasesystems (provided that the basesystems are connected). A prerequisite is that theapplications recognise each other through the application mapping.

Type

The object type is indicated with a letter in accordance with the following:

P Process objects



1MRS751253-MEN

ABB Automation10

X Scale objects

D Data objects

C Command procedures

T Time channels

A Event channels

E Event objects

V Variable objects

F Free type objects

Attribute

An attribute represents the value or feature to be read or written with the object no-tation. It is generally named by a predefined attribute name, which is a combinationof two letters, A ... Z. Variable objects can have freely chosen attribute names of anylength up to 63 characters.

Reading an attribute means that the attribute value is used in an expression. Writingan attribute means that the attribute value is changed or updated with the #SET or#MODIFY commands. See the examples under the headline “Using Object Nota-tions” below.

The attribute of an object notation determines the value and the data type (see theProgramming Language SCIL manual, Chapter 3) of the entire notation. An objectnotation without an attribute may still refer to a special attribute, the default attribute(mentioned in the subsequent object descriptions, normally the object value).

Object notations can be used without an attribute together with some commands (sec-tion 2.3.). In these cases they refer to the entire object. Event objects can only be usedwithout an attribute.

Index

Indices are used to differentiate attribute values with equal object notations in allother respects. Such attribute values are handled as a vector, where the elements areaccessed using indices.

As a rule, indices refer to the elements of an attribute of vector type. The actual at-tribute determines the data type of the elements. Predefined process object types arean exception. For these objects, the indices refer to the individual objects in a group,not to attributes of vector type. However, for a certain attribute, the values are han-dled as elements in a vector.

In SCIL, an index or index range is marked in any of the following ways:

• With an integer number, either a positive integer value or an octal number. An in-dex of a variable object where the attribute is not composed of two letters must beembraced by brackets. In all other cases, no brackets are needed.

• With an integer type expression. The expression must be embraced by brackets.



ABB Automation 11

• With an interval (i..j), where ’i’ is the first index number and ’j’ the last. If the in-dex limits are given as expressions (for example an object notation or a variable)they should be embraced by brackets or spaces. Two points surrounded by brack-ets, (..), are interpreted as all the indices of the actual object notation. (i..) Indi-cates all indices larger than or equal to ’i’, and (..j) all indices less than or equal to’j’.

No space is allowed between the index and the rest of the object notation.

Using Object Notations

Object notations can be used in SCIL statements and expressions (event object nota-tions cannot be used in expressions). When used in expressions, the value of the at-tribute in the notation replaces the entire object notation. It can, for example, be partof a window definition expression, entailing that object data is shown in the window.It can also be included in data object definitions or in conditional expressions, etc.See the Programming Language SCIL manual, Chapter 6.

Examples:

!SHOW WINDOW OBJ:POV2

The value of the OV attribute of the process object OBJ with index 2 is read from theprocess database and displayed in the window WINDOW

@V = DATA:DRT + 60

A variable is assigned the value of the latest registration time added with 60 seconds

#SET BREAKER:PBO3 = 1

The process object BREAKER is closed. If the object represents a real physical ob-ject, the command is sent to the process station (RTU), which closes the real breaker.

!SHOW W DAT_OBJ:2DOV3

The third registered value of the data object DAT_OBJ situated in application 2 isshown in the window (Assumes that application 2 is known to the present applica-tion.)

Attribute Access Level

There are four main levels of access to the application object attributes:

• Read-only: Usually the attribute can be read using the object notation. It cannotbe written with the #SET or #MODIFY commands, nor can it be given valuewhen creating new object with #CREATE.

• Read-only, configurable: Usually the attribute can be read and it can be assigneda value when a new object is created with the #CREATE command or modifiedwith the #MODIFY command. It cannot be assigned values with the #SET com-mand.

• Read, conditional write: Usually the attribute can be read. It can be written pro-vided that certain conditions are fulfilled.



1MRS751253-MEN

ABB Automation12

• No limitations: These attributes can be both read and written freely, in somecases provided that the object is in use (IU=1).

These terms are used in the attribute descriptions in Chapters 3 ... 11.

2.3 Some SCIL Commands

General

A detailed description of SCIL is found in the Programming Language SCIL manual.This section briefly describes a few SCIL commands, which are important for appli-cation object handling. The commands are here given along with the arguments nec-essary for making a complete statement. The arguments are written in lowercase let-ters.

Setting Object Values

#SET object [= expression]

Assigns the value of ’expression’ to the attribute in ’object’, which must be a completeobject notation. The object can be any object type, except an event object. Concerningprocess objects, the command may entail control of the process.

Executing Objects

#EXEC object [(variable_list)]

Executes an object. The ’object’ can be a data object, a command procedure, an eventobject or an event channel. The command entails that a data object is registered, acommand procedure is executed, an event object is generated or an event channel isstarted. The variable list, which can be omitted, defines the variables to be used in thecommand procedure or in the data object expression.

Event Object Handling

#ON event_object [statement]

Defines a statement or a program sequence to be executed in the picture - main pic-ture, part picture, control board picture, or picture function - each time the namedevent object is generated (Chapter 9).



ABB Automation 13

Updating Process Database

#GET object

Gets process values from stations connected on ANSI lines (station type STA) andupdates them in the process data base. The ’object’ must be a process object or acommunication system object with the attribute ME (see the System Objects manual).

Process Query

#INIT_QUERY n [condition]

Initialises a process query. The process query is performed with the SCIL functionPROD_QUERY, which returns a list of process object attribute values. The commandstates the type of the following process query as well as which process objects are in-cluded in the query. The type of the process query can be: the whole process data-base, the alarm buffer (for alarms lists) or the history buffer (for event lists).

Creating Objects

#CREATE object [= expression]

Creates a new object and assigns it the attributes of the expression, which must be oflist type. Using this command all application object types can be created, except eventobjects. The expression, which must be of list type, assigns the object desired attrib-utes. It can be the LIST function or a variable object that has been assigned desiredattributes with FETCH, PHYS_FETCH, NEXT, PREV. The latter case means that thenew object is copied from an existing one (must be of the same type).

Modifying Objects

#MODIFY object = expression

Changes the object definition according to the attributes in the list type expression.The object can be of any application object type, except event objects. Most attributescan be modified with this command, except those that are generated by the system.Unlike the #SET command, the #MODIFY command allows several attributes to bewritten simultaneously. Some attributes that cannot be changed with #SET can bechanged with #MODIFY.



1MRS751253-MEN

ABB Automation14

Deleting Objects

#DELETE object

Deletes the object definition. The object can be of any application object type, exceptevent objects.

Searching through Objects

#SEARCH n appl type order [start [condition]]

Searches objects of a specified type and with specified features for browsing with theSCIL functions NEXT and PREV. Up to ten search sequences can be initialised si-multaneously in each picture or command procedure. Searching among variable ob-jects and event objects is not possible.


MicroSCADA3 Process Objects

ABB Automation 15

3 Process Objects

This chapter describes the process objects and their attributes. It is divided into fivesections with the following contents:

3.1 General: This section describes the basic features, use and functions ofprocess objects, process object types, user defined process object types,an overview of process object attributes, process objects, the storage ofprocess objects, etc.

3.2 Configurable process object attributes: This section lists and describes indetails process object attributes that define the functions of the objects.

3.3 Dynamic process object attributes: This section lists and describes indetails process object attributes that contain the dynamic, real time dataof the objects.

3.4 Defining process objects: required attributes, default values, principlesfor creating process objects using SCIL, examples.

3.5 Configurable process object group attributes: This section lists anddescribes in details process object group attributes that define thefunctions of the object groups.

3.1 General

Use

Process objects are typically data images of physical process devices, such as break-ers, disconnectors, switches, relays, detectors, sensors, regulators. These devices areconnected to MicroSCADA through Remote Terminal Units (RTUs), ProtectiveEquipment, Programmable Logics, Central Stations, etc., all of which will be referredto as process units or stations in the following text.

Process objects supervise the process signals registered in stations and control thesignals sent from the stations to the process equipment. Generally, each input andoutput connection in a station is represented by a process object in the MicroSCADAprocess database. Additionally, general supervision and status information stored in astation can be represented by process objects.

There are also process objects that have no physical correspondence, nor any data cor-respondence in the stations. These process objects are used for process simulations,for manually updated values, system message handling, etc.

Function

Process objects constitute the links between the control system and the controlledprocess. A process object contains the process data, various stamps related to the data(for example time and validation stamps or stamps set by the stations) and alarm state



1MRS751253-MEN

ABB Automation16

information. It also contains functional definitions, such as scale definition, automaticactivation, etc., see Figure 4. Both the dynamic data that reflect the real-time state ofthe process and the functional definitions are defined by attributes.

A process device is controlled by setting the object value of the corresponding outputobject with the #SET command. The order is passed out to the NET unit and to theprocess device via the station. Likewise, a spontaneous message from a station up-dates the corresponding input objects in the process database. Under certain condi-tions, the process objects of input type can also be updated using SCIL (with #SET,see the SS attribute). Process objects without process connection are always updatedusing SCIL.

Every update of a process object, whether it comes from the process or from SCIL,may cause the following effects, “post-processing”, (depending on the process objectdefinition and the value of the update):

• Alarm activation (input objects) including alarm signals, alarm printout and reg-istration in the alarm buffer (alarm list).

• Automatic printout.

• Event-based updating in pictures (through event objects).

• Activation of an event channel.

• Registration in the history buffer (event list).

Each update gets a validation stamp (the OS attribute) and a time stamp (the RT andRM attributes), and also other markings possibly.

If an object does not exist when an update comes, an event channel(UNDEF_PROC:A) is activated, see the Chapter 8.

Process Object Types

The type of a certain process object depends on the type of the corresponding in-put/output connection in the station. This connection corresponds to the main attributeof the process objects, the object value (the OV attribute). MicroSCADA supports tenpredefined process object types:

• Analog Input and Output.

• Binary Input and Output.

• Digital Input and Output.

• Double Indication (input).

• Pulse Counter (input).

• Bit Stream (output and input).

• File Transfer (output and input).

Table 1 shows the relationship between the MicroSCADA process object types andthe corresponding signal types in S.P.I.D.E.R. RTU and SPACOM stations.



ABB Automation 17

User Defined Types

In addition to the predefined process object types listed above, the MicroSCADA ap-plication engineer can define up to 155 different user-defined types. These processobject types are defined by free type objects described in the Chapter 11 of this man-ual.

Using free type objects the application engineer can define his own process objecttypes for which he can select the type of object value, other attributes and type of ac-tivation. Unlike the predefined object types, where the activations are always con-nected to the object value, any attribute of the user defined object types can be de-fined to cause post-processing.



1MRS751253-MEN

ABB Automation18

Process Displays Alarm Signals Alarm List Event ListEvent and Alarm Printout

Trends and Reports

Process Objects Report Database

Figure 4. The functions of the process database



ABB Automation 19

Table 1. The S.P.I.D.E.R. RTU and SPACOM specific data types and the corresponding process objecttypes. The bit stream and file transfer object types are not included as they have no correspon-dence within these types of stations.

Process Object Types S.P.I.D.E.R RTU Data Types SPACOM Data types

Binary Input, BI Indication single

Indication single event recording

Indications

Binary Signals

Alarms

Switches

Binary Output, BO Object command

Regulation command

Select open/close of secured control

Execute command

Cancel selection

Direct open/close commands

Lower/raise commands

Digital Input, DI Digital value

Digital Output, DO Digital setpoint

Analog Input, AI Analog value

Analog event recording

Measured data (current, voltage, inte-grated energy values, tap changer posi-tion, etc.).

Analog Output, AO Analog setpoint

General persistent output

Double Binary Indication, DB Indication double

Indication double event recording

Breaker and disconnector states

(open + close)

Pulse Counter, PC Pulse counter Pulse counters

Attributes

Table 2 lists the attributes of different process object types. This table lists both thedynamic attributes that reflect the real time state of the process and the definition at-tributes that specify the function of the process objects. In the attribute descriptions insections 3.2 and 3.3 these two main types of attributes are kept apart.

If no value is given to an attribute when an object is defined, the attribute is assigneda default value. The default values of the attributes are given in the attribute descrip-tions in section 3.2 and 3.3 They are also given within parenthesis in Table 2.

Objects of the user-defined types have all the common attributes. In addition, theyhave a number of user-defined attributes that can have any two-letter attribute nameexcept the common attribute names. The user-defined attributes are defined by thefree type objects described in the Chapter 11.



1MRS751253-MEN

ABB Automation20

Table 2. The process object attributes of different process object types. The default values are given withinparenthesis. R = the attribute is read only.

Predefined TypesObject Types

Attributes All Types BI BO AI AO DI DO DB PC BS FT

BasicAttributes

LN. PT, ZT IX IX IX IX IX IX IX IX IX IX

ObjectAddresses

UN, OT, IT OA,OB

OA,OB

OA, OB OA,OB

OA,OB

OA,OB

OA,OB

OA,OB

OA,OB

Object Value OV(0) BI(0) BO(0) AI(0) AO(0) DI(0) DO(0) DB(0) PC(0) BS(0) FT(0)

Time and Vali-dation Stamps

OS(R),RT(R),RM(R)

Alarm State AL(R),AS(R),AR(R),AT(R), YT,AM(R), YM

Operation State IU, SS, SU

Unit and Scale SN, ST,IR(0)

SN,ST,IR(0)

SC,BC(16)

Limit Values HI(0),LI(0),HW(HI),LW(LI),SZ(0),ZE(0),ZD(0)

HO(0),LO(0)

Alarm Handling AC(0),AD(0), PI,PD(0),RC(0)

AG(0) LA(0),NV(4)

Min / Max Val-ues

MM,MT, MV,XM, XT,XV

Stamps set bythe Stations

BL, CT, OR,RA, RB, SB

Event Handling AA(0),AE(0),AF(0), AH,AN, EE(0)

TH

Printout Han-dling

LD(0),PA(0), PF,PH, PU(0)

History Buff-ering

HE, HA, HF,HH, HL

Blocking At-tributes

AB, HB, PB,UB, XB

OperationCounting

CE,CL,CV,CO

CE,CL,CV,CO

CE,CL,CV,CO

S.P.I.D.E.R.RTU Attributes

SE(0),SP

OF,EP

IEC SpecificAttributes

OG, QL TY TY TY



ABB Automation 21

Predefined TypesObject Types

Attributes All Types BI BO AI AO DI DO DB PC BS FT

Event HistoryAttributes

CA, ED, EM,ET, EX, HD,HM, HT

MiscellaneousAttributes

CX, OX, DX,FI, FX

File TransferAttributes

FF, FN,ID, DC,FP, ST

Process Object Groups

Process objects of predefined types are regarded as parts of process object groups,where all objects have the same name and individual objects are identified by meansof indices. Up to 10 000 related process objects of the predefined types can be giventhe same name. Different I/O points of a motor control for example, can be given thesame object name. Process objects of several different predefined types can be in-cluded in the same group. Likewise, both real and process objects without processconnection (see below) can be contained in the same group. Objects of user definedtypes cannot be included in a group.

Every object in a group is defined separately and independently of the other objects inthe group. Individual attribute values are elements in a vector, formed by the corre-sponding attribute values of all objects in the group. Each attribute value is identifiedby the index of the object.

Storage

The process objects are stored in the process database, which is located on disk aswell as in RAM (primary memory). All the attributes are stored in RAM. Dependingon the switch state (see the attribute SS), the process object values (OV) are updatedalternatively both on disk and in RAM, only on disk, or only in RAM.

A full size process database is limited by the file size limit of 32 Mb. The maximumnumber of process objects varies between 4000 and 320 000 depending on the size ofthe attribute values. The lower limit is an extreme case where the database is filledwith bitstream objects each having an object value (bit string) of length 65000 andfully equipped text attributes. Also scales occupy space in the process database.

Note also that a process database including 320000 process objects occupies 80 Mb ofthe primary memory. The memory pool should hence be configured accordingly.

The name of the process database file is APL_PROCES.PRD.

At application start-up, the process database is copied from disk to RAM. As the val-ues stored on disk are probably out-dated, the process database should be updatedfrom the stations. This is managed differently for different types of stations:

• S.P.I.D.E.R. RTUs send all object values (input data) automatically to the processdatabase when the NET unit has been started (the NET unit has sent an SCI(Status Check Instruction)). When the NET unit is running, process database can



1MRS751253-MEN

ABB Automation22

be updated from the RTUs by setting the STAn:SSC attribute for all RTUs. Formore information on this attribute see the System Objects manual. For examplethe setting can be done in the initialisation programs, which are application de-pendent command procedures started by the event channels APL_INIT_1 andAPL_INIT_2. For more information on event channels see Chapter 8.

• The process data of stations on ANSI lines (Allen-Bradley, SRIO, etc.) is read andupdated in the process database by means of the #GET command (section 2.3.),for example, situated in the initialisation programs.

• Process data of SPACOM units are updated in the process database when theSTAn:SUP attribute of the stations (see the System Objects manual) is set. Forexample, the statement #SET STA2:SUP = 1 means that all process data of theSPACOM unit defined as STA2 is updated in the process database.

Process Object Notation

The process object attributes are accessed in SCIL with the following notation (seealso Chapter 2):

name: {a}P{at}{(i)}

or

name:[a]P[at][i]

where

’name’ Is the name of the process object group (predefined types) or proc-ess object (user-defined types)

’a’ Is the logical application number

’at’ Is the attribute name

’i’ Is an index or index range

For predefined object types, the indices refer to the individual object(s) in a group. Anobject notation without an index normally refers to the process object with the lowestindex, but it refers to the whole group if the attribute is common to the group. Foruser-defined object types, the indices refer to elements in user-defined attributes ofvector type. The predefined common attributes cannot be indexed. In the followingattribute descriptions (sections 3.2 and 3.3), indexing is only explained for specialcases.

As a rule, a process object notation without attribute refers to the object value OV(BI, BO, AI, AO, DI, DO, DB, PC or BS). For user-defined objectd types, notationwithout attribute refers to the main attribute of the object. However, the commands#LIST, #CREATE, #DELETE and #MODIFY refer to the whole object or, if the no-tation contains no index, to the whole process object group.

The process data stored in stations using the ANSI X3.28 protocol can be directly ac-cessed with the system object attribute STAn:SME (see the System Objects manual).



ABB Automation 23

3.2 Configurable Process Object Attributes

This section describes the process object attributes that define the objects and theirfunctions. The attributes are grouped into the following sub-sections:

3.2.1 Basic Definition: IX, LN, PT, ZT

3.2.2 Identification: CX, OI, OX

3.2.3 Addresses: OA, OB, OT, TI, UN

3.2.4 Operational State: IU, SS, SU

3.2.5 Unit and Scale: BC, IR, SC, SN, ST

3.2.6 Limit Value Supervision: HI, HO, HW, LI, LO, LW, SZ, ZD, ZE

3.2.7 Alarm Handling: AG, LA, NV, AC, AD, PD, PI, RC

3.2.8 Event Handling: AA, AE, AF, AH, AN, EE, TH

3.2.9 Saving the Event History: HA, HE, HF, HH, HL

3.2.10 Printout Handling: LD, PA, PF, PH, PU

3.2.11 Miscellaneous Attributes: CE, CL, DX, FI, FX, RI, RX

3.2.1 Basic Definition Attributes

IX Index

The index of a process object of predefined type. The individual objects in a group (amaximum of 10 000 objects with the same name) are identified by indices.

In principle, the index for a new process object can be freely chosen. However, thefollowing convention is used: The index of an event recording object in S.P.I.D.E.R.RTUs should be assigned the index of the supervised object plus 100.

Data type: Integer

Value: 1...10 000

Access: Read-only, configurable

LN Logical Name

The logical name of the process object. The name is common to all objects in thegroup (predefined types). The individual process objects in the group (a maximum of10 000) are identified by indices (the IX attribute).



1MRS751253-MEN

ABB Automation24

Data type: Text

Value: Maximum length of the name is 63 characters. The name mustfollow the rules for object names given in section 2.2.

Indexing: When referring to an individual object of a predefined type, theobject index (the IX attribute) is used.When referring to a group, the attribute is not indexed.For user-defined objects the attribute is always used without an in-dex.


Example:

Modifying the LN attribute:@A = FETCH(0,"P","ABC",1)#SET A:VLN = "DEF"#MODIFY ABC:P1 = %A

PT Process Object Type

The type of the object. The system groups the process objects into nine predefinedprocess object types depending on the type of the object value. The object value canbe: binary input, binary output, analog input, analog output, digital input, digital out-put, pulse counter, double binary indication and bit stream. For more information seethe headline "Process Object Types" in section 3.1). In addition to predefined objecttypes, there may be up to 156 user defined types.

Data type: Integer

Value: 1 ... 255The type numbers 1 ... 99 are reserved for predefined types100 ... 255 can be used for user defined types.There are the following predefined types:

3 = Binary input (BI)

5 = Binary output (BO)

6 = Digital input (DI)

7 = Digital output (DO)

9 = Analog input (AI)

11 = Analog output (AO)

12 = Double Binary Indication (DB)

13 = Pulse Counter (PC)

14 = Bit Stream (BS)



ABB Automation 25

15 = File Transfer (FT)

Access: Read-only, configurable with #CREATE but not #MODIFY

ZT Modification Time

The time when the object was created or modified. This attribute is set by the mainprogram when the object is created and each time the object is updated by the#MODIFY command (for example, by the process object definition tool).

Data type: Time

Access: Read-only

3.2.2 Identification Attributes

CX Comment Text

A freely chosen text. This attribute is not included in the history buffer.

Data type: Text

Value: Text

Access: No limitations

OI Object Identifier

A freely chosen text that can be used as an identifier for the object, a descriptive textor a comment. The OI attribute is contained in the history buffer and event log (start-ing at column 231). Hence, it can be included in the event list. The attribute can bedivided in sub-strings according to application specific conventions.

Data type: Text

Value: Text of max. 63 characters


OX Object Text

A freely chosen text.

Data type: Text

Value: Text of maximum 63 characters




1MRS751253-MEN

ABB Automation26

3.2.3 Addresses

The attributes in this section specify the relationship between the process objects andthe corresponding input and output signals and data in the process units. For a certainprocess object, the UN attribute (Unit Number) specifies the unit where the corre-sponding process signal is registered. The OA and OB attributes (Object Address andBit Address) specify the address to the signal.

OA Object Address

The address to the process object. All real objects (the objects that are connected to aprocess) require an object address. A possible bit address is given separately with theattribute OB.

For process objects belonging to stations using the ANSI X3.28 protocol the objectaddress is the same as the word address defined in the station.

For process objects belonging to S.P.I.D.E.R. RTUs and SPA units, the object addressis a number coded according to the formula:

4096 * object type number + logical address

where

‘object type number' is 0 ... 11 according to the following:

0 = No object type (simple input, counter input, measurand input in P214)

1 = Object command (S.P.I.D.E.R. RTUs), binary output (SPA)

2 = Regulation command (S.P.I.D.E.R . RTUs), command output (P214)

3 = Digital setpoint

4 = Analog setpoint

5 = General persistent output (S.P.I.D.E.R. RTU), setpoint output (P214)

6 = Analog value

7 = Indication (single or double)

8 = Pulse counter

9 = Digital value

10 = Indication event recording

11 = Analog event recording



ABB Automation 27

’logical address’ Is the type specific logical address:For S.P.I.D.E.R. RTUs the block address.For SPA units: the SPA point address defined in NET.

The object address of process objects belonging to REX stations (REF, RED, REC,REL, etc., relays on a LON) is the address given in the process units.

The object address of process objects belonging to LMK stations (LSG device,Weidmuller, etc., on LON) is the address defined in NET by the correspondingLONWORKSi point definition (see the System Objects manual).

In the Process Object Definition Tool both the OA attribute and the logical addresscan be used.

Data type: Integer

Value: 0 ... 2 147 483 6470 = No object address. In the process object Definition Tool theOT attribute (Output Type) indicates whether the address isread/written in decimal or octal form. For FT type process objects0 is the only permissible value.

Default value: 0


OB Object Bit Address

The bit address of the object value in the station. All real binary and double indicationobjects require a bit address, except S.P.I.D.E.R. RTU objects of binary output type(object commands and regulation commands) which may not be given bit addresses.

Double binary indications are given even bit addresses. Using an even address for adouble binary input object is only possible if the subsequent odd bit address is free.

Giving a bit address requires that the word address (the attribute OA) has been speci-fied.

Data type: Integer

Value: 0 ... 15In the Process Object Definition Tool the OT attribute indicateswhether the address is displayed in decimal or octal form. On theother hand when using SCIl the address is always read/written inthe decimal form. For FT type process objects 16, no bit address,is the only permissible value.

Default value: 16 = No bit address

i LONWORKS is a registered trademark of Echelon Corporation.



1MRS751253-MEN

ABB Automation28


OT Output Type

The format - decimal, octal or hexadecimal form - used when displaying the addressesof the object (the attributes OA and OB).

Data type: Integer

Value: 0 = Decimal representation1 = Octal representation2 = Hexadecimal representation

Default value: 0


TI Table Index

Table index attribute supports configuring COM 500 object addressing. Reserved foruse by LIB 500.

Data type: Integer

Value: No range checking


UN Unit Number

The logical number of the station where the object is found. The logical number is thenumber as known to the application. The number is translated according to the stationmapping attribute APLn:BST, see the System Objects manual, Chapter 5. Objectswith a UN value of 1 … 2000 are connected to the process through the communica-tion system.

Data type: Integer

Value: 0 ... 65535

Default: 0




ABB Automation 29

3.2.4 Operational State

IU In Use

Status of use. This attribute determines whether the object can be operated or not.Taking an object out of use (IU = 0) means that all functions of the object, such asupdating and alarm and event handling, are switched off. No attributes (except IU)can be used or changed. However, the object definition is preserved and the objectcan be put back into use again at any time by setting the IU attribute to 1. If the switchstate is AUTO (SS = 2) or FICTITIOUS (SS = 3) when the object is put into use (IUset to 1), the OS attribute (Object Status) receives the value 10 (see the OS attribute).This applies all the other object types other than output objects (BO, DO or AO).

Data type: Integer

Value: 0 = Out of use1 = In use

Default value: 0


Example:

The process object ABC with index 3 is taken out of use:#SET ABC:PIU3 = 0

SS Switch State

This attribute describes how the object value (the attributes AI, AO, BI, BO, DI, DO,DB, PC and OV) is updated: manually, automatically or not at all.

Data type: Integer

Value: 0 … 3:0 = OFF, no updating, the object is disconnected. The

#SET and #GET commands cannot be used with the object.

1 = MAN, manual updating. The object is updated by SCIL (#SET). Updating from the process is inhibited and changes in output values (AO, BO, BS, DO) do not affect the process. The object value is updated both on disk and in RAM. #GET is not possible.

2 = AUTO, updating both from the process and from SCIL. The AI, BI, DI, PC and DB attributes can be updated from SCIL only if the object’s UN = 0 and SS = 2. The object values are updated only in RAM,



1MRS751253-MEN

ABB Automation30

except process objects with UN = 0 and SS =2, which are updated both on disk and in RAM.

3 = FICTIVE. The object is fictitious. Unit number (UN) and object addresses (OS, OB) are not required, but if given they have only an informative function. They are not used for data transfer between the process database and the station.

Default value: 0


Table 3. The table shows how different switch states affect the reading and writing of the OV attribute.When the value is changed with a definition tool, it is changed according to the principles in themodify column.

#SET obj:pov[ix] = value #MODIFY obj:p[ix] = LIST(ov = value) OV (RAM) OV (DISK)

SS=0 not possible, error 2013 (profobject switched off) is pro-duced

changes DISK value status 2013 defined

SS=1 changes RAM and DISKvalues

changes RAM and DISK values defined defined

SS=2 UN = 0:

changes RAM value

UN > 0:

input objects >> not possi-ble, error 2018 (prof updatecapability error) is produced

output objects >> changesRAM value

UN = 0:

changes RAM and DISK values

UN > 0:

input objects >> changes DISK value

output objects >> changes DISK value

UN = 0:

defined

UN > 0:

input objects >>status 10

output objects >>defined

defined

SS=3 changes RAM value changes RAM and DISK values defined defined

SU Substitution State

A common attribute to all predefined process object types. The value of SU attributeis stored on a disk. When SU is set to 1, the value of the OV attribute is stored on diskas well, even if the switch state of the object is AUTO.

The attribute may be set by a simple #SET command or a list type #SET commandmay be used to set the SU attribute and the corresponding OV attribute at the sametime, for example:#SET x:Py = LIST (SU = 1, BI = 1)

SU attribute is automatically reset from 1 to 0, when the value of the OV attribute isupdated. The OV attribute is updated by process if the switch state is in AUTO, or bySCIL in other switch states.

Setting the SU attribute generates an event if EE == 1 and activates an event channel,printout and/or history logging if enabled.



ABB Automation 31

The value of SU attribute is included in the snapshot variables.

Data type: Integer

Value: 0 = Not substituted1 = Substituted

Default value: 0


3.2.5 Unit and Scale

These attributes apply to AI, AO and/or PC type objects.

BC Bit Count

The number of bits in the maximum value of the pulse counter. This attribute appliesto Pulse Counter (PC) objects and is just informative. It entails no automatic functionsin the process database, but can be used in SCIL programs.

Data type: Integer

Value: 1 ... 32

Default value: 16 (31 in the definition tool)


IR Integer Representation

Configuration attribute for AI and AO type process objects for defining the represen-tation of the analog value.

When IR = 1, the following attributes are represented as integer values:

AI objects: AI, MV, XV, LI, HI, LW, HW, ZD

AO objects: AO, LO, HO

Furthermore, when IR = 1, the value is not scaled between the database and the ACPmessage. The scale name attribute SN must be empty, if given at all, when the objectis created.

Data type: Integer

Value: 0 = Floating point representation. Data type Real in SCIL1 = 32-bit signed integer representation. Data type Integer in SCIL

Default value: 0



1MRS751253-MEN

ABB Automation32

Access: Read-only, configurable. It can be created with the #CREATEcommand, but it cannot be modified with the #MODIFY com-mand.

SC Scaling

This attribute concerns only objects of type Pulse Counter (PC). It indicates the num-ber of units that one pulse corresponds to. The unit is determined by the ST (SortType) attribute.

The attribute has only an informative function. For S.P.I.D.E.R. RTUs the attribute isautomatically set in the RTUs.

Data type: Real

Value: Real


Example:@A = COUNTER:PSC3 * COUNTER:PPC3

SN Scale Name

The name of the scale used for the scaling of the object. The scale is an algorithm forthe transformation of analog process values to computer data scaled in accordancewith the unit of the object (the ST attribute). This attribute concerns only analog ob-jects (AI and AO). Every analog process object must have a scale (see Chapter 4).The scale must exist in the database before the process object can be created.

Scaling is executed in the process database before the object value is registered (AI)or sent to the process (AO).

Data type: Text

Value: Maximum 63 characters


ST Sort Type

The unit of the object value. This attribute concerns only analog and pulse counterobjects (AI, AO and PC).

Data type: Text





ABB Automation 33

3.2.6 Limit Value Supervision

These attributes apply to analog objects (AI and AO). The LI, HI, HW and LW attrib-utes (Low Input, High Input, High Warning and Low Warning), specify the alarm andwarning limits of analog objects. These attributes are also valid for user-defined ob-jects of data types real and integer.

For compatibility reasons, the following rule applies to the limit values: If the warn-ing and alarm limits have been set equal (HI = HW and LI = LW) and the alarm limitsare changed, the warning limits will always be changed accordingly.

HI Higher Input

Upper alarm limit for analog input values. Alarm is raised (AL = 1), when the AI at-tribute exceeds this value (provided that SZ = 1).

Data type: RealInteger, if IR=1

Value: >= LI and HWThe HI attribute cannot be set below the LI and HW attributesInteger, if IR=1

Default value: 0


HO Higher Output

Upper limit for analog output values (AO). If the attribute AO exceeds this value, anerror status is raised.


Value: >= LOInteger, if IR=1

Default value: 0


HW Higher Warning

The upper warning limit for analog input objects (if SZ = 1).




1MRS751253-MEN

ABB Automation34

Value: >= LW and <= HIThe HW attribute cannot be set higher than the HI attribute, norlower than the LW attribute.Integer, if IR=1

Default value: The HI attribute


LI Lower Input

Lower alarm limit for analog input values. Alarm arises (AL = 1) when the AI attrib-ute goes below this value (provided that SZ = 1).

Data type: Real

Value: <= HI and LWThe LI attribute cannot be set above the HI and LW attributes

Default value: 0


LO Lower Output

Lower limit for the analog output value (AO). If the AO attribute goes below thisvalue, an error message is produced.


Value: <= HOInteger, if IR=1

Default value: 0


LW Lower Warning

Lower warning limit for analog input objects (if SZ = 1).


Value: <= HW and >= LIThe LW attribute cannot be set smaller than LIInteger, if IR=1

Default value: The LI attribute



ABB Automation 35


SZ SCADA Zone Supervision

This attribute determines whether the warning and alarm supervision are managed bythe station or by MicroSCADA. If the supervision is handled in the station, the stationdetermines the alarm and warning state of the object, independent of the HI, LI, HWand LW attributes (see above). Warning and alarm supervision affect the alarm, eventand printout generation.

For S.P.I.D.E.R. RTU objects the SZ attribute should normally be 0 (supervision inthe RTU).

Data type: Integer

Value: 0 = Supervision in the station1 = Supervision in MicroSCADA

Default value: 0


ZE Zero deadband supervision Enabled

Analog input objects can be defined with zero deadband supervision. If supervision isenabled and the value of the object lies within the deadband, exact zero is stored asthe object value ( AI ). As long as the value lies within the deadband zone, the meas-ured entity (for example current, voltage) is regarded as switched off and the varia-tions are regarded as negligible disturbances.

When zero deadband is in use, the value 0 is not considered to be an alarming valueeven though a lower alarm limit LI >=0 is given. When the object gets the value 0, thealarm zone attribute AZ is set to 0. The Minimum Value attribute (MV) is not up-dated.

Data type: Integer

Value: 0 = No zero deadband supervision1 = Zero deadband supervision is enabled

Default: 0


ZD Zero Deadband

The width of the zero deadband, see Figure 5. The value of the object is regarded aszero when it lies within the shaded zone, that is, within the range -ZD ... +ZD. Seealso the ZE attribute above.



1MRS751253-MEN

ABB Automation36


Value: Width of the zero deadbandInteger, if IR=1

Default: 0.0


0ZD

ZD

+ZD

-ZD

Figure 5. An illustration of the ZD attribute

3.2.7 Alarm Handling

General

The following object types can be equipped with alarm handling:

• Analog input objects (AI).

• Binary input objects (BI).

• Double binary objects (DB).

• Objects of user-defined types.

Alarm handling is roughly illustrated in Figure 6. If an object has no alarm class(alarm class 0), it has no alarm function either. If there is an alarm class, and thealarm is not blocked (see section 3.3.4), an alarm is activated when the object valuereceives an alarming value.



ABB Automation 37

Alarm Handling

Process SCILUpdating of OV

AC ? = 0

AB?AL = 1(alarm on)

= 0

AL = 0 Change?

SetAT = RTAM = RM

= 1

Yes No

Yes

> 0

+Alarm Buffer.............................................

-

-

PI ?

+Alarm PictureQueue.............................................

- !INT_PIC

RC?

AR ?

= 0

= 1

= 1

PF ?Yes

LD

PF ?Yes

Alarm printout

LD>0?Yes

External Alarm Signals

ALARM LIST

PD

AZ = 1AZ = 2BI = AGDB = LA ?

Figure 6. A rough outline of the alarm handling attributes for analog input and binary input objects. OS issupposed to be 0. If the old OS = 10 the monitor alarm, alarm printout and external alarm signalsdepend on the PU attribute (Picture at First Update, see section 3.2.10).

“Alarm on” as well as ”alarm off” always cause a registration in the “alarm buffer”,which contains all active and unacknowledged alarms (if there is a demand for ac-



1MRS751253-MEN

ABB Automation38

knowledgment). The alarm buffer is sorted according to the alarm time (the AT andAM attributes, see section 3.3.3). If a new alarm occurs in an object that already is inthe buffer, the alarm time of the object is changed, and the buffer is resorted.

If an object has an alarm delay (the AD attribute), a short alarm state can pass withoutalarm activation (not included in Figure 6). However, the alarm time attributes (AT,AM, YT and YM) are updated.

Regarding automatic printout, see section 3.2.10.

Every time an alarm occurs an event channel named APL_ALARM is activated (if itexists), see Chapter 8.

Alarm Generation

For analog input (AI) objects, alarm generating values are specified by alarm limits,(the HI and LI attributes described in section 3.2.6), provided that SCADA supervi-sion is used (the SZ attribute). For binary and double binary objects, alarm generationis specified by the following attributes:

AG Alarm Generation

Alarm generation for binary input objects (BI). This attribute indicates which bitvalue, 0, 1 or both, will generate an alarm. When the BI attribute gets this value, analarm is generated. If both bit states generate an alarm, the alarm generation at thefirst update can be prevented by means of the Normal Value (the NV attribute, seebelow).

The attribute is also valid for user defined object types of data type Boolean.

Data type: Integer

Value: 0 = Bit value 0 generates an alarm1 = Bit value 1 generates an alarm2 = Both bit value 0 and bit value 1 generate an alarm3 = Both bit values 0 and 1 generate an alarm on each update, even

if the value hasn’t changed.

Default value: 0


LA Alarm Activation

The alarm generating states for double binary indications (DB), given as bit masks.Several states, even all four states can be alarm generating.

If one, two or three states are defined to be alarm generating, an alarm is generatedwhen the object value (the OV attribute) receives any of these states. The alarm dis-appears when a no-alarm state is received. If all four states are defined to generate an



ABB Automation 39

alarm (LA = 15), each new update causes a new alarm. In this case, the alarm disap-pears, that is, the AL attribute becomes = 0, when the alarm is acknowledged.

When an object with LA = 15 is updated for the first time (OS goes from 10 to 0) andthe object value is the normal value (NV), or the normal value is 4, no alarm is gener-ated. See the NV attribute.

Data type: Integer

Value: 0 ... 15. The alarm generating states given as bit masks0 = No alarm generation

Default value: 0


Example:

The OV values 0 and 2 will be alarm generating and the value of DB:PLA value willbe 5:#SET DB:PLA = BIT_MASK(0,2)

NV Normal Value

The normal value of a binary indication or double binary indication.

The NV attribute is important only at the first update and when all bit states are alarmgenerating. At the first update the former OS value is 10. All bit states ar alarm gener-ating when the AG = 2 for binary input objects and LA = 15 for DB objects. In thesecases, the object does not cause any alarm if its value is the same as the NV attributeor if NV = 4.

Data type: Integer

Value: 0, 1 or 2 for binary input (BI) objects and 0 ... 4 for double binaryindications (DB)

Default value: 2 for binary objects and 4 for double indications. These valuesmean that no alarm is generated at start-up for objects that are de-fined to be alarm generating in all states.


Example:

If a binary input object defined to generate alarm in all states (AG = 2) has NV = 1,no alarm is generated if BI = 1 at the first update. However, if BI = 0 at first update,an alarm is generated. If the NV attribute of the object = 2, no alarm is generated atfirst update independent of the value of BI.



1MRS751253-MEN

ABB Automation40

Alarm Handling Attributes

The following attributes specify the alarm functions of the object:

AC Alarm Class

There are seven equally significant alarm classes for grouping alarms. The applicationengineer chooses how to group the objects in alarm classes. They can, for example, begrouped based on the location of the process objects or alarm type. An object withalarm class 0 has no alarm function.

The alarm class is of significance when connecting the objects to audiovisual alarmsignals through additional circuit boards. All objects belonging to the same class havethe same type of audiovisual alarms. The audiovisual alarm signals to standard alarmdevises only work for objects with at least one printer, that is LD > 0.

Data type: Integer

Value: 0 ... 70 = no alarm function

Default value: 0


AD Alarm Delay

AD specifies the delay between the registration of an alarm value in the process data-base and the generation of that alarm. If there is a delay, the alarm value is updated inthe process object as normal, but the alarm messages and consequential activationsare not activated. There are several types of consequential activations: printout, audioand picture alarm, registration in alarm list and history buffer, event channel activa-tion. When the delay time expires, the AL attribute (Alarm, see section 3.3.3) is set to1 and the alarm signals are activated, provided that the alarming value remains. Oth-erwise, if the object value has been updated to a non-alarm value during the delay, noalarm is activated.

The alarm delay does not affect alarms generated by a FAULTY status of the object.Neither does the alarm delay apply when the alarm is cleared. In these cases, alarmmessages and activations are activated as usual.

Independent of the alarm delay, the alarm time stamps (AT, AM, YT and YM) are setto the time when the object was updated to the alarm value (that is the real alarmtime). When the alarm delay expires, the RT and RM attributes are updated if thealarm state remains.

For analog input objects, the warnings are delayed according to the AD attribute valuebecause of the alarm delay. If a situation occurs where the object value is updated toan alarm value during a warning delay, the delay is restarted. If the value returns to



ABB Automation 41

normal during the alarm delay, no alarm or warning is produced. However, if thevalue returns to a warning state, a warning is immediately produced.

Data type: Integer

Value: 0 ... 65535

Unit: Seconds

Default value: 0


PD Picture Devices

The logical monitor numbers of the alarm monitors, that is, the monitors where thepicture alarm message and the alarm picture will be shown. An object can have up to15 alarm monitors (the monitors with logical numbers 1 ... 15).

Data type: Integer

Value: 0 ... 65534, even numbers. The monitor numbers of the alarmmonitors given as a bit map. The alarm monitor numbers are thebit numbers of the ones in the bit representation of the integer. Themonitors are given with the logical numbers known to the applica-tion (according to the monitor mapping, the APLn:BMP attribute,see the System Objects manual).


Example:

Monitors with the logical numbers 2 and 4 will receive monitor alarms:#SET A:PPD = BIT_MASK(2,4)

PI Picture

The name of the alarm picture, that is the picture shown with the command !INT_PIC(section 2.2.).

When an alarm occurs, the alarm picture is placed as the last item in a monitor spe-cific alarm picture queue. At the same time a monitor alarm signal (a red flashingsquare in the upper right corner) is issued. The command !INT_PIC shows the alarmpicture that is first in the queue. When the picture is shown, it is removed from thequeue. The alarm picture can be shown when the monitor alarm signal has been is-sued. Even if the alarm disappears before the picture has been shown, the alarm pic-ture remains in the queue. When a semi-graphic monitor is closed (by the !CLOSEcommand), or when a picture is exited with the emergency exit key in the upper leftcorner, the remaining alarm pictures in the alarm picture queue of the monitor areshown one by one. If an alarm occurs while the monitor is closed, it is automaticallyproduced on screen immediately.



1MRS751253-MEN

ABB Automation42

Using the PU attribute (Printout at First Update, see section 3.2.10), alarm messages,including the monitor alarm and the alarm picture, can be inhibited when the object isupdated for the first time, for example when the previous OS value is 10.

Data type: Text

Value: Picture name


RC Receipt

Demand for acknowledgement. The attribute states whether acknowledgement isobligatory or not. If acknowledgement is required, the alarm is not removed from thealarm queue until it is acknowledged with the AR attribute.

Data type: Integer

Value: 0 = No acknowledgement demand1 = Demand for acknowledgement

Default value: 0


3.2.8 Event Handling

The attributes in this section determine event channels and event activated updating inpictures. The history buffering attributes that specify the registration in the historybuffer and in the event lists, are described in section 3.2.9, printout handling attributesin section 3.2.10. Event handling can be blocked. For more information on blocking,see the attributes in section 3.3.4.

AA Action Activation

This attribute determines the object value related situations, that cause an event chan-nel activation. It only applies for objects with event channel (AE = 1, see below). Re-garding objects of user-defined types, any user defined attribute can be defined to ac-tivate the event channel of the object.

Monitor alarm signal is shown only if the object has an alarm picture.



ABB Automation 43

Using the AF attribute it is possible to select whether event channel will be activatedwhen the object value is updated for the first time (OS = 10). It is always activatedwhen an object value already exists (OS < 10).

Data type: Integer

Values: 0 ... 5The activation criteria:

0 = ALARMActivation only when the AL attribute changes (that is an alarmcomes or goes).

1 = NEW VALUEActivation each time the OV attribute is changed, OS is changed to1 or 3, or SE or SP is set. Includes activation at alarm.

2 = UPDATEActivation each time the OV attribute is updated (even if it is notchanged), or SE or SP is set. If updating from the station is markedINTERROGATED, no event channel is activated, if the objectvalue has not changed and the AF attribute is = 0 (no activation atfirst update). For more information on INTERROGATED, see theCT attribute. Includes activation at alarm.

3 = WARNINGActivation when the warning or alarm state changes (the AL or AZattributes, see section 3.3.3), or SE or SP is set.

4 = UPActivation when a binary object is changed from 0 to 1, or thevalue of a double binary object is changed from 0 to 1, from 1 to 2,from 2 to 3, from 3 to 2 or 1 to 0. No meaning for other objecttypes. Includes activation at alarm.

5 = DOWNActivation when a binary object is changed from 1 to 0, or thevalue of a double binary object is changed from 0 to 1, from 2 to 3,from 3 to 2, from 2 to 1 or 1 to 0. No meaning for other objecttypes. Includes activation at alarm.

Default value: 0


AE Action Enabled

The connection of an event channel (Chapter 8) to the process object. The eventchannel transmits the process object events to another object, which can be a dataobject or a command procedure. The situations, which activate the connected eventchannel, are determined by the AA attribute. Besides, for user defined object types,



1MRS751253-MEN

ABB Automation44

each of the user-defined attributes can cause an event channel activation. All processobjects can be connected to an event channel.

When an event channel is activated, the values of the following process object attrib-utes are transmitted to variables with the same names as the attributes ("snapshotvariables"), see Chapter 8.

Data type: Integer

Value: 0 = No event channel1 = The process object is equipped with an event channel

Default value: 0


AF Action at First Update

This attribute determines whether the event channel (the AN attribute) is also acti-vated when the process object is updated for the first time. The process object is up-dated for the first time when the previous object value has the status 10 (OS = 10,NOT_SAMPLED_STATUS). The attribute only concerns those cases where the AAattribute would give cause for activation.

If updating from the station is marked SPONTANEOUS (see the CT attribute in sec-tion 3.3.7), event activation takes place at the first updating independent of the valueof AF.

The AF attribute only concerns objects with event channel (AE = 1).

Data type: Integer

Value: 0 = No activation at first update1 = Activation also at first update (OS = 10)

Default value: 0


AH Action on History

This attribute specifies whether or not updates marked HISTORY (see the CT attrib-ute in section 3.3.7), will cause an event channel activation.

Data type: Integer

Value: 0 = No event channel activation for HISTORY events1 = Event channel is activated for HISTORY events according to

the same activation criteria as for real time data



ABB Automation 45

Default: 0


AN Action Name

The name of the event channel connected to the process object. Several process ob-jects can have the same event channel. However, each process object can be con-nected to only one event channel.

Data type: Text



EE Event Enabled

This attribute states whether or not the process object is equipped with automaticevent activation of programs in user interface objects. If the object has this feature, anevent object with the same name and index as the process object is generated whencertain changes occur in the object. Changes in any of the following process objectattributes cause an event object generation:

SS, OS, AI, AO, BI, BO, DI, DO, DB, PC, BS, HI, HO, LI, LO, AC, RC, AR, AB, SE,SP, HW, LW, IU + blocking attributes + user defined attributes.

Regarding the attributes PC, RC, SE and SP, not only a change but also an update tothe attributes causes the generation of an event object. In addition, each user-definedattribute may cause an event object generation.

When an event object is generated, it starts event specific SCIL programs or programsequences in the user interface objects that are currently displayed on screen, seeChapter 9. Event object activation can be used for updating the display, for triggeringNetwork Topology functions, etc. Event objects do not transmit any information ofthe attribute that caused the event.

Data type: Integer

Value: 0 = No event object generation1 = Event object generation

Default value: 0


TH Threshold

Event channel activation with threshold means that the event channel connected to theprocess object is not activated immediately when the value is updated in the process



1MRS751253-MEN

ABB Automation46

database. Instead, some type of algorithm is used to calculate when the activation is tohappen.

The purpose of thresholding is to lower the load of frequent event channel activations,for example in cases where the event channel is used to send the value to anothercontrol station via a slow communication channel. Event channel activation withthreshold applies to analog input process objects. TH attribute implements the thresh-old.

The algorithm guarantees that if the value is changed once and then stays in that newvalue, the change is sooner or later reported. The attributes AE and XB are honoured.

AA should be set to UPDATE or NEW VALUE. AF should usually be set to 1 ( It isnormally not sensible to filter out the first activation ). If AF=1, the event channel isactivated immediately without threshold calculation, when the object is updated firsttime after the startup of the application.

If AI crosses a warning or alarm boundary, the event channel is activated immediately(or after the delay specified by AD) and the threshold calculation is stopped.

In an HSB system, the intermediate values of the integral are not shadowed due to ex-cessive load.

Consequently, the threshold calculation is started from the beginning after a switch-over. Assigning a new value to TH does not restart the possible on-going thresholdcalculation. The algorithm always uses the current value of TH.

Data type: Non-negative real value

Value: Non-negative real value

Default: 0 (no threshold used)


Example: The algorithm used is an integrating threshold algorithm thatworks like this:

1. A value of AI attribute is received and event channel is acti-vated. The value is named reported value.

2. When AI is updated and the new value differs from the reportedvalue, threshold calculation is started.

3. On each calculation cycle, 100 ms in current implementation,the time integral of the difference between AI and the reportedvalue is calculated. For example, if the reported value is 240.0 andAI is 243.0, value 0.3 is added to the integral.

4. If the absolute value of the integral reaches or exceeds the THattribute value, the associated event channel is activated and thethreshold calculation is stopped.



ABB Automation 47

-18

-17

-16

-15

-14

-13

-12

-11

-10

-9

-8

-7

-6

-5

-4

-3

-2

-1

0

1

2

3

4

5

6

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Time / (0,1 * s)

An

alo

g In

pu

t V

alu

e

-6

-5

-4

-3

-2

-1

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

0,1

* T

resh

old

Treshold exceed

Treshold exceed

Treshold exceed

Treshold exceed

Event channelactivation


Event channelactivation Event channel

activation

TH = 0,5

Last reported value

Last reported value

Last reported value

Last reported value


Figure 7. Event channel activation with treshold. Primary(left) y-axis represents the analog input value,here without unit. Secondary(right) y-axis is the time integral of the analog input value. The valueof the TH attribute in this example is 0,5. When the value of the treshold reaches or exceeds hevalue of 0,5, an event channel is activated and the treshold calculation is reset.

3.2.9 Saving the Event History

General

There is two ways to store the event history:

• Using history database.

• Using event log and history buffer.

The application engineer chooses one of them when he creates the application. At-tribute HP determines which one is in use. By default the event log is chosen, forcompatibility reasons. For more information about the HP attribute, refer to the Sys-tem Objects manual, Chapter 5 and for information on the functionHISTORY_DATABASE_MANAGER, refer to the Programming Language SCILmanual, Chapter 8. System Configuration manual, Chapter 13, also explains how toconfigure storing the event history. History database information related to each eventcontains some extra attributes, which are described later in this Chapter.

History Database

History database consists of history database files each containing events of one day.The files are named according to the date as APL_yymmdd.PHD. For example file



1MRS751253-MEN

ABB Automation48

APL_980115.PHD contains the events logged on 15-Jan-1998. For fast access in timestamp order, there is also an index file corresponding each data file. The name exten-sion of the index file is PHI. The history database is the basis for event lists made byLIB 500 version 4.0.2.

History Buffering

The event history for eligible process objects can also be stored in a history buffer lo-cated in the primary memory and in a history log on disk. All types of objects can beregistered in the history buffer and in the history log. The history buffer or the historylog is the basis for event lists made by LIB 500 version 4.0.1 or earlier versions of ap-plication libraries. The history buffer is read by process queries (the SCIL command#INIT_QUERY and the SCIL function PROD_QUERY). The history log is an ASCIIfile.

Most attributes stored in primary memory are transmitted to the history buffer, and tothe event log if such is used. Thus, event registrations have the same attributes as or-dinary objects. In addition they get another attribute: the CA attribute.

If a process object has history buffering (HE = 1), the data of the process object willbe copied to the history buffer when any of the following attributes is changed:

• Object value: OV. The OV attribute causes history registrations according to theHA attribute.

• Operational state: SS, IU.

• Limit values: HI, LI, LW, HW, HO, LO.

• Alarm definition: AC.

• Blocking attributes: AB, HB, PB, UB, XB.

• Alarm state: AL, AR.

• SE, SP. If HA is unlike 0, not only a change but also an updating of these attrib-utes causes registration in the history buffer. If HA = 0, these attributes cause noregistration in the history buffer.

In addition, each user-defined attribute can be defined to cause a registration in thehistory buffer.

The size of the buffer is application dependent and can be changed with theAPLn:BHB attribute. When the history buffer is full, the oldest registered value isomitted for each new registration.

History Configuration Attributes

HA History Activation

This attribute specifies the registration of history values caused by the OV attribute. Itapplies to process objects with registration in the history buffer (HE = 1).



ABB Automation 49

Data type: Integer

Value: 0 ... 5The history registration criteria:

0 = ALARMHistory registration only when the AL attribute changes (that is analarm comes or goes)

1 = NEW VALUEHistory registration each time the OV attribute is changed, OS ischanged to 1 or 3, or SE or SP is set. Includes activation at alarm.

2 = UPDATEHistory registration each time the OV attribute is updated (even ifit is not changed), or SE or SP is set. No history registration ismade if the update from the station is marked INTERROGATEDand the object value has not changed and the HF attribute is = 0.Includes activation at alarm.

3 = WARNINGHistory registration when the warning or alarm state changes (theAL or AZ attributes, see section 3.3.3), or SE or SP is set.

4 = UPHistory registration when a binary object is changed from 0 to 1,or the value of a double binary object is changed from 0 to 1, from1 to 2, from 2 to 3, from 3 to 2 or 1 to 0. No meaning for other ob-ject types. Includes activation at alarm.

5 = DOWNHistory registration when a binary object is changed from 1 to 0,or the value of a double binary object is changed from 0 to 1, from2 to 3, from 3 to 2, from 2 to 1 or 1 to 0. No meaning for other ob-ject types. Includes activation at alarm.

Default value: 0


HE History Enabled

This attribute states whether or not history registrations of the object will be copied tothe history buffer. All types of objects can be included in the history buffer.

Data type: Integer

Value: 0 = History registrations are not stored1 = History registrations are stored

Default value: 0



1MRS751253-MEN

ABB Automation50


HF History at First Update

This attribute determines whether the object is also registered in the history bufferwhen the process object is updated for the first time. The process object is updated forthe first time when the previous object value has the status 10(NOT_SAMPLED_STATUS, OS = 10) and the HA attribute would give cause for ana registration.

If the update from the station is marked SPONTANEOUS (see the CT attribute insection 3.3), history registration takes place at the first update independent of thevalue of HF.

The attribute concerns only objects with history registration (HE = 1).

Data type: Integer

Value: 0 = No registration at first update1 = Registration also at first update

Default value: 0


HH History on History

This attribute specifies whether or not updates marked HISTORY (see the CT attrib-ute in section 3.3) will be registered in the history buffer.

Data type: Integer

Value: 0 = Updates marked HISTORY are not logged in the history buffer

1 = HISTORY events are logged according to the same activation criteria as real time data

Default: 0


HL History Log Number

This attribute is only valid when the history log and history buffer are used for storingthe event history. It specifies the numbers of the printers used as event log printers.

All events registered in the history buffer are copied to the printer log files of theevent log printers. The printers should be configured as virtual printers (withoutphysical correspondence) with printer logging (see System Configuration, Chapter



ABB Automation 51

13). Each time the history buffer is updated, most attributes of the object are writtento the files as a long line text (374 characters).

The following attribute values are included in the history log:

GT (3), PT (3), LN (10), IX (3), CA (2), OV (12), OS (5), UN (3), OA (5), OB (2),OT (1), RM (3), RT (10), IU (1), SS (1), HA (1), AB (1), AC (1), AL (1), AR (1), AS(2), AD (3), RC (1), PF (10), OX (30), ST (10), AZ (1), HI (12), HO (12), HW (12),LI (12), LO (12), LW (12), SZ (1), LA (2), NV (1), AG (1), BC (2), CE (1), CL (10),CO (1), CV (10), OF (1), SE (1), SP (1), OI (30), BL (1), SB (1), OR (1), RA (11), RB(11), CT (1), RI (11), RX (10), PH (11), AH (1), HH (1), PB (1), XB (1), HB (1), UB(1), ZE(1), ZD (12), TH (12), OG (5), QL (5), TY (5).

The numbers within parenthesis indicate the field length in number of characters re-served for each attribute value. There is no space between the fields. The attributenames are not included in the log.

Data type: Integer

Value: The logical printer number, 1 ... 15, given as bit mask0 = No history log

Default value: 0


3.2.10 Printout Handling

The attributes in this section specify the printouts related to the process objects, theprinting devices and the automatic activation of printing procedures on the occurrenceof certain process events. The automatic printing described in this section can be tem-porarily blocked by means of the Blocking Attributes (see section 3.3).

LD Listing Devices

The printers to be used for automatic printing of the physical format picture (definedby the PF attribute, see below). The printers are selected with logical printer numberin the range 1 ... 15. The logical printer numbers are determined with the printer map-ping attribute (APLn:BPR, see the System Objects manual, Chapter 5).

Data type: Integer

Value: 0 ... 65534, even numbersPrinter numbers given as a bit mask. The bit numbers of the onesin the bit representation of the integer state which printers to use.The printers are given by logical printer numbers as defined to theapplication by the printer mapping (see the System Objects man-ual, Chapter 5).

Default value: 0



1MRS751253-MEN

ABB Automation52


Example:

The printer numbers 1, 3 and 5 are alarm and event printers (ABC:PLD2 == 42):#SET ABC:PLD2 = BIT_MASK(1,3,5)

PA Printout Activation

This attribute indicates which process events that will cause automatic printing: achange of alarm state, a change of warning state, a change of object value or updatingof object value. The attribute is valid for all process objects supplied with a physicalformat picture (the PF attribute) and at least one listing device (the LD attribute). ThePA attribute also affects the releasing of possible external alarm signals. The PU at-tribute (see below) states whether automatic printing is also activated at first update(when OS = 10). Independent of this attribute, each user-defined attribute can be de-fined to cause automatic printing.

Data type: Integer

Value: 0 … 5The printing criteria:

0 = ALARMAutomatic printing is activated when the alarm state changes (analarm comes or goes)

1 = NEW VALUEAutomatic printing is activated when the object value (the OV at-tribute) changes, the OS attribute changes to 1 or 3, or SE or SP isset. Includes activation at alarm.

2 = UPDATEAutomatic printing is activated when the object value (the OV at-tribute) is updated (even if it is not changed), or SE or SP is set. Ifthe object value is alarming, external alarm signals are producedfor each new update. Nothing is printed automatically, if the up-date from the station is marked INTERROGATED and the objectvalue has not changed and the PA attribute is = 0. Includes activa-tion at alarm.

3 = WARNINGAutomatic printing is activated when the warning state or alarm

The standard audio-visual alarm unit requires that at least one listing device is con-nected to the process object (LD > 0).



ABB Automation 53

state changes (the AZ attribute, see section 3.3.3), or SE or SP isset.

4 = UPAutomatic printing is activated when a binary object is changedfrom 0 to 1, or the value of a double binary object is changed from0 to 1, from 1 to 2, from 2 to 3, from 3 to 2 or 1 to 0. No meaningfor other object types. Includes activation at alarm.

5 = DOWNAutomatic printing is activated when a binary object is changedfrom 1 to 0, or the value of a double binary object is changed from0 to 1, from 2 to 3, from 3 to 2, from 2 to 1 or 1 to 0. No meaningfor other object types. Includes activation at alarm.

Default value: 0


PF Physical Format

The name of the automatically printed picture. The picture is printed out in accor-dance with the PA attribute, see above. It is also printed when a user-defined attributecauses a printout. In addition, the picture is printed with the command #LIST (seeChapter 2) if the object notation is given with an index (predefined object types).Each object can have its own physical format picture, or several objects can share thesame picture. Regarding the construction of format pictures, see the Picture Editingmanual.

When automatic printing is activated, a number of variables are defined which getboth their names and values from some attributes ("snapshot variables"). These attrib-utes are:

CA (Changed Attribute, see section 3.3.11)

LN, IX

OV, AI/AO/BI/BO/BS/DI/DO/DB/PC

AL, OS, RT, RM, AT, AM, AS, AZ (analog input objects), YT, YM

SE, SP and OF (S.P.I.D.E.R. RTU objects)

Blocking attributes, section 3.3.4.

Min. max attributes, section 3.3.6.

Stamps set by the station, section 3.3.7.

Corresponding variables (for example %AI) can be used in the format picture. In ad-dition, each of the user-defined attributes can be a "snapshot variable". Another auto-



1MRS751253-MEN

ABB Automation54

matically defined variable, %CHANGE, tells what kind of changes in the OV attrib-ute that caused the printout. The %CHANGE variable is described in Chapter 8.

Data type: Text

Value: Picture name


PH Printout on History

The attribute specifies whether or not updates marked HISTORY (see the CT attribute3.3.7) will activate automatic printing.

Data type: Integer

Value: 0 = No printout activation for updates marked HISTORY1 = HISTORY events are printed according to the same activation

criteria as real time data

Default: 0


PU Printout at First Update

This attribute determines whether automatic printing and alarm signals are also gener-ated when the process object is updated for the first time. The process objects are up-dated for the first time when the previous object value has status 10 (OS = 10,NOT_SAMPLED_STATUS). The attribute concerns automatic printing, alarm pic-ture and audio-visual alarm signals.

If an update is marked SPONTANEOUS in the station (see the CT attribute in section3.3.7), a printout is generated when the object is updated for the first time independ-ent of the value of PU.

Data type: Integer

Value: 0 = No activation at first update1 = Activation also at first update

Default value: 0


3.2.11 Miscellaneous Attributes

Counter Definition Attributes

These attributes apply for BI, BO and DB type process objects.



ABB Automation 55

CE Counter Enable

Operation counting is taken into use by setting this attribute to one.

Data type: Integer

Value: 0 = No counting1 = Counting in use

Default: 0


CL Counter Limit

The upper limit for the counter. When the counter value (the CV attribute) goes abovethis limit, counter overflow (the CO attribute) is set On.

Data type: Integer

Value: Integer

Default: 0


SCIL Attributes

These attributes are optional for all types of objects.

DX Directive Text

This attribute is reserved by ABB Substation Automation and should not be used inapplication programs.

FI Free Integer

An integer attribute that can be freely used for any application purpose.

Data type: Integer

Value: Integer (32 bit)


FX Free Text

A text attribute that can be freely used for any application purpose.



1MRS751253-MEN

ABB Automation56

Data type: Text

Value: Text of maximum 63 characters


RI Reserved Integer

An integer for use in standard application software LIB 500. The attribute may takeany integer value. It is of informative character and has no influence on the functionof the process object. The attribute is stored both on disk and in RAM.

Data type: Integer

Default value: 0

Access: No limitations. Reserved for use in engineering software, such asLIB 500

RX Reserved Text

A text attribute for use in standard application software LIB 500. The attribute maytake any text value. It has an informative character and does not influence the functionof the process object. The attribute is stored both on disk and in RAM.

Data type: Text


Default value: ""

Access: No limitations. Reserved for LIB 500

3.3 Dynamic Process Object Attributes

This section describes the process object attributes that reflect the real time state ofthe process. The attributes are grouped into the following subsections:

3.3.1 Object Value: AI, AO, BI, BO, BS, DB, DI, DO, OV,PC

3.3.2 Time and Validation Stamps: OS, RM, RT

3.3.3 Alarm and Warning States: AL, AR, AS, AM, AT, AZ, YM, YT

3.3.4 Blocking attributes: AB, HB, PB, XB, UB

3.3.5 Operation Counters: CO, CV

3.3.6 Minimum and Maximum Values: MM, MT, MV, XM, XT, XV



ABB Automation 57

3.3.7 Stamps Set by the Protocol: BL, CT, OR, RA, RB, SB

3.3.8 S.P.I.D.E.R. RTU Specific Attributes: OF, SE, SP, EP

3.3.9 IEC Specific Attributes: OG, QL, TY

3.3.10 File Transfer Attributes: DC, FF, FN, FP, FT, ID, ST

3.3.11 Event History Attributes: CA, ED, EM, ET, EX, HD, HM, HT

Within each sub-section, the attributes are in alphabetical order.

3.3.1 Object Value

The attributes described in this section represent the actual value of the object. Forreal objects (process objects connected to the process), the object values of input typeare automatically updated from the process stations (unless updating is blocked, seethe Blocking Attributes in section 3.2.10). The object values of output type are sentout to the process stations when set with the #SET command.

AI Analog Input

An analog input value - measured value - from the station via the communicationsystem to the base system. The value is scaled in the process database according to thescale defined by the SN attribute (see section 3.2.4 and Chapter 4).

Data type: Real.Integer, if IR=1When IR = 1, the value is not scaled between the database and theACP message

Value: Real or integer

Default value: 0

Access: Read, conditional write. The attribute can be written only if theswitch state is manual (SS = 1) or fictive (SS = 3), or if it’s UN = 0and SS = 2.

AO Analog Output

An analog output value (for example a set value, an analog setpoint, general output)from the base system to the station, via the communication system. The value is

The analog process objects are always stored as real data. Therefore, process data thatare logical integers may contain decimals after scaling. If this is a problem in calcula-tions, use the SCIL function ROUND to transform the object value to an integer.



1MRS751253-MEN

ABB Automation58

scaled according to the scale given by the SN attribute (see section 3.2.4.) before itleaves the process database.

Data type: RealInteger, if IR=1When IR = 1, the value is not scaled between the database and theACP message


Default value: 0

Access: Read, conditional write. The attribute cannot be written if the pro-cess object is OFF (SS = 0).

BI Binary Input

A binary input signal (indication) from the station to the base system via the commu-nication system.

Data type: Integer

Value: 0 or 1 (one bit)

Default value: 0

Access: Read, conditional write. The attribute can be written with SCIL ifthe switch state is manual (SS = 1) or fictive (SS = 3) or if it´s UN= 0 and SS = 2, but not otherwise.

BO Binary Output

A binary output signal (control signal, object command, regulation command) fromthe base system via the communication system to the station.

Data type: Integer

Value: 0 or 1 (one bit)

Default value: 0


BS Bit Stream

An output and input signal of bit string type.

Data type: Bit string



ABB Automation 59

Value: Length maximum 65535


DB Double Binary Indication

A double binary indication from the station. In some stations double binary indica-tions are handled as two single binary input values. In MicroSCADA the first bitmeans "closed", and the second bit "open".

Data type: Integer

Value: 0 = Intermediate position1 = Closed2 = Open3 = Faulty position

Default value: 0

Access: Read, conditional write. The attribute can be written only if theswitch state is manual (SS = 1) or fictive (SS = 3) or if it’s UN = 0or SS = 2.

DI Digital Input

A digital input value from the station via the communication system to the base sys-tem.

Data type: Integer

Value: 0 ... 65535 (16 bits)

Default value: 0

Access: Read, conditional write. The attribute can be written only if theswitch state is manual (SS = 1) or fictive (SS = 3) or if it’s UN = 0and SS = 2.

DO Digital Output

A digital output value (digital setpoint) from the base system via the communicationsystem to the station.

Data type: Integer

Value: 0 ... 65535 (16 bits)

Default value: 0



1MRS751253-MEN

ABB Automation60


OV Object Value

The OV attribute of output objects of IEC/REX type (BO, DO, AO, BS) is set withsyntax given in Table 4 on page 76 of this chapter. For an object of IEC/REX type inauto state only output objects (BO, DO, AO, BS) is set with syntax given in Table 4on page 76.

The intended use of the OV attribute is:

1 As a comprehensive name for one of the attributes AI, AO, BI, BO, BS, DI, DO,DB, PC and FT depending on the object type. For user-defined object types, theprogrammer selects, which attribute, if any, will be the OV attribute. Setting theOV attribute of an input object is meaningful only in case the object is in manualor fictive state.If the object type is unknown, the object is assumed to be of type IEC.

2 As default attribute when no attribute name is given at assigning a value of an ob-ject. For example, the #SET commands:

#SET A:PAI1 = 0#SET A:POV1 = 0#SET A:P1 = 0

of an analog input object are equivalent.

For input objects of any type and output objects of other type than IEC, the OV attrib-ute can be set manually together with the attributes listed in the example according tothe following model:#SET name:Pi = LIST(OV=exp1[,RT=exp2, RM=exp3, OS=exp4, OF= exp5, BL= exp6,-

SB= exp7, OR= exp8, RA= exp9, RB= exp10, CT= exp11,-TY= exp12, QL= exp13, OG= exp14])

which is analogous to#SET name:POVi = LIST(OV=exp1[,RT=exp2, RM=exp3, OS=exp4, OF= exp5,-

BL= exp6, SB= exp7, OR= exp8, RA= exp9, RB= exp10,-CT= exp11, TY= exp12, QL= exp13, OG= exp14])

where ’exp1’, ’exp2’, ’exp3’ etc. are expressions assigned to the attributes. The partwithin square brackets can be omitted, whereby the RM and OS attributes are set to 0.Attributes RT and RM are assigned values at registration time if not given in the list.Attributes TY, QL and OG apply to IEC/REX type objects only. For objects of typeIEC/REX also the OV attribute is optional.

Also the stamps set in the stations (see section 3.3.7) can be written in this way.

Data type: Integer, real or bit string

Value: Integer 0 or 1 for binary objectsReal for analog objectsInteger for DI, DO and PC objectsInteger 0 ... 3 for DB objectsBit string for BS objectsInteger for FT objects



ABB Automation 61

Default value: 0

Access: See the AI, AO, BI, BO, BS, DI, DO, DB, PC and FT attributes

Example:#SET A:P2 = LIST(OV=3.0,RT=B:PRT,RM=B:PRM)

or#SET A:POV2 = LIST(OV=3.0,RT=B:PRT,RM=B:PRM)

PC Pulse Counter

A pulse counter value from the station. The type of reading when the process objectbelongs to a S.P.I.D.E.R. RTU (“End of period” or “intermediate”), is given by the EPattribute of the objects, see section 3.3.8.

Data type: Integer

Value: Integer

Default value: 0

Access: Read, conditional write. The attribute can be written only if theswitch state is manual (SS = 1), or fictive (SS = 3) or if it’s UN = 0and SS = 2.

3.3.2 Time and Validation Stamps

These attributes are related to the object value. Each update of the object value in theprocess database gets a validation stamp (the OS attribute) and time stamps (the RTand RM attributes), independent of whether the object value changes or not.

OS Object Status

The status code of the process object. This attribute indicates the reliability of theobject value (the OV attribute).

Data type: Integer

Value: 0, 1, 2, 3 or 10:

0 = OK_STATUS

1 = FAULTY_VALUE_STATUSThe RTU has marked the process object value faulty (concernsS.P.I.D.E.R. RTUs only). An update with this status sets the objectto alarm state (AL = 1), provided that AC > 0 (section 3.2.). Thealarm state prevails until a new update comes with OS = 0.

2 = OBSOLETE_STATUSThe value is uncertain. The reason can be that the connection to



1MRS751253-MEN

ABB Automation62

the station is broken. The OS attribute automatically gets thisvalue when a system message with DATA_INVALIDATION flagis sent from the station. The obsolete status is also set for outputobjects at application startup.

3 = FAULTY_TIME_STATUSThe RTU has marked the registration time faulty (concernsS.P.I.D.E.R. RTUs only).

10 = NOT_SAMPLED_STATUSThe status when the value has not been read in the station or theobject has been out of use (IU = 0) or modified with the#MODIFY command, or the SS attribute has been changed. Forexample, the value in the station might not have been read aftersystem start-up.

Default value: 10 for most of the process objects.By default the OS attribute of BO, DO and AO objects is set to 2(OBSOLETE_STATUS) at application startup.

Access: Read-only. The OS attribute can be set manually along with theOV attribute, see the OV attribute, section 3.3.1.

RM Registration Milliseconds

The milliseconds of the registration time. The value of this attribute is set by the sta-tion. If the station does not give any milliseconds, or in case the update comes fromSCIL, the RM attribute is set by the base system. Otherwise, the RM attribute is up-dated in the same way as the RT attribute.

Data type: Integer

Value: 0 ... 999

Unit: Milliseconds

Access: Read-only. The RM attribute can be set manually along with theRT and OV attributes, see the OV attribute, section 3.3.1.

RT Registration Time

The time when the object was last updated. The time stamp may originate from thestation, NET or the base system. If the update from the station contains a time stamp,the time is copied to the RT attribute. If the time stamp does not contain a date, thedate is supplied by the base system. SPA input objects are time stamped in NET. Inother cases, the RT attribute is set by the base system time.

When an object is updated with SCIL (with #SET), the time stamp is always given bythe base system. Output objects are time stamped before the command is sent to NET.



ABB Automation 63

The RT attribute of BO type objects is also updated when SE or SP is set (section3.3.8).

If an object has an alarm delay (the AD attribute, section 3.2.), the RT attribute is up-dated when the alarm delay expires provided that the alarm state is prevailing.

Data type: Time

Value: Time

Initial value: At system start-up, the attribute gets the value of the time when theprocess object was established in the RAM memory of the processdatabase.

Access: Read-only. The RT attribute can be set manually along with theOV attribute, see section 3.3.1.

3.3.3 Alarm and Warning States

The attributes in this section show the alarm and warning states of the process objects.Alarm and warning handling is defined by the alarm handling attributes in section3.2.7 and the limit values in section 3.2.6.

AL Alarm

This attribute indicates whether alarm is prevailing or not. The attribute is generatedautomatically by the system. If AC >0, and the AB attribute does not prevent analarm, this attribute is set to 1 (= alarm is generated) in the following cases:

• The value of an analogue input object (or an object of an integer or real user-defined type) comes into the low alarm or high alarm zone (see the AZ attribute insection 3.2.5). If the alarm supervision is handled by MicroSCADA, and the ob-ject value exceeds the alarm limits (the HI and LI attributes) or the limits arechanged so that the object value falls outside the limits.

• A binary input object (or a Boolean object of a user-defined type) gets the alarmgenerating value (the AG attribute).

• A binary double indication gets any of the alarm states (the LA attribute). At thefirst update, the alarm can be prevented by the NV attribute.

• The OS attribute gets the value 1.

When an alarm is generated (AL=1), an alarm signal is a red blinking sign in the up-per right corner of the screen (supposing the object is equipped with an alarm pic-ture). At the same time the alarm picture of the object is placed in a monitor specificalarm picture queue, and the object is placed in the alarm buffer. The alarm buffercontains most of the object attributes. It can be read with process queries (the functionPROD_QUERY). In addition, a printout (see section 3.2.10) and external alarm canbe produced.

Data type: Integer



1MRS751253-MEN

ABB Automation64

Value: 0 = No alarm (normal state)1 = Alarm is prevailing

Initial value: 0

Access: Read-only

AR Alarm Receipt

Status of acknowledgement. This attribute indicates whether or not the alarm has beenacknowledged in the cases where acknowledgement is required.

Data type: Integer

Value: 0 = The alarm is not acknowledged1 = The alarm is acknowledged or there is no demand for

acknowledgement

Default value: 0


AS Alarm State

The alarm state is a number calculated from the alarm class (AC), the alarm (AL) andthe state of acknowledgement (AR).

Data type: Integer

Value: 0 ... 14When an alarm arises, the attribute gets the value of AC (1 ... 7), ifRC = 1, and AC + 7, if RC = 0. When the alarm is acknowledged,7 is added to the attribute value. When the alarm disappears, theattribute gets the value 0, supposing that it has been acknowl-edged, or there is no demand for acknowledgement.

Initial value: 0

Access: Read-only

AM Alarm Milliseconds

The milliseconds of the alarm time (see the AT attribute below), that is, the time whenan alarm last arose or was cleared. Generally, the alarm milliseconds are the same asthe RM attribute of the update that caused the change of alarm state. However, in casethe object has an alarm delay there may be a difference, see the AT attribute.

Data type: Integer

Value: 0 ... 999



ABB Automation 65

Unit: Milliseconds

Access: Read-only

AT Alarm Time

The alarm time in seconds when an alarm last arose or was cleared. Generally, thealarm time is the same as the RT attribute of the update that caused the change ofalarm state. If the object has an alarm delay, the AT and AM attributes are updatedwhen an alarm occurs. The RT and RM attributes are updated when the alarm delayexpires, provided that the alarm state prevails.

Data type: Time

Value: Time

Unit: Seconds

Initial value: At system start-up, the attribute gets the value of the time when theprocess object was established in the RAM memory of the processdatabase.

Access: Read-only

Example:!SHOW AL_TIME TIMES(OBJ:PAT2)

AZ Alarm Zone

The alarm and warning state of the object, see Figure 8. This attribute is only valid forAI objects. Depending on the SZ attribute, the value of the AZ is set either by Micro-SCADA according to the limit values or by the RTU, see section 3.2.6.

Data type: Integer

Value: 0 ... 4:0 = Normal state1 = Low alarm2 = High alarm3 = Low warning4 = High warning

Default value: 0

Access: Read-only



1MRS751253-MEN

ABB Automation66

Higher Input, HI

Higher Warning, HW

Lower Warning, LW

Lower Input, LI

OVAZ = 2

AZ = 4

AZ = 0

AZ = 3

AZ = 1

Figure 8. An illustration of the AZ attribute (SZ = 1)

YM Alarm on time Milliseconds

The milliseconds of the time when an alarm last occurred in the object. This attributeis identical to AM while the object alarm is active, but unlike the AM attribute, theYM attribute is not updated when the alarm is cleared.

Data type: Integer

Value: Integer

Unit: Milliseconds

Access: Read-only

YT Alarm on Time

The time when an alarm last occurred in the object. This attribute is identical to theAT attribute while the object alarm is active. Unlike the AT attribute, the YT attributedoes not change when the alarm is cleared.

Data type: Time

Value: Time

Access: Read-only

3.3.4 Blocking Attributes

The following attributes are used to temporarily block the updating of a process ob-ject or to block the post-processing (printouts, event channel activation and eventlists) normally caused by process object update. If the value is changed, the new valueof the blocking attribute is stored on disk. Like the dynamic attributes, they are in-



ABB Automation 67

cluded in the “snapshot variable” list. The setting of any of the attributes is logged inthe history buffer and in the history log if there is any. Also, an event is generated.

AB Alarm Blocking

This attribute indicates whether the alarm function is on or off (blocked). See also theNV attribute in section 3.2.7 and the PU attribute in section 3.2.10.

Data type: Integer

Value: 0 = No blocking, the alarm function works1 = Blocking, the alarm is off. Those situations that normally

would have caused an alarm do not cause any alarm when AB = 1.

Default value: 0


HB History Blocking

Blocks and unblocks the registration in the history buffer. When history registration isblocked, no events are registered in the history buffer (nor in the event log on disk),not even in situations that would have caused a registration according to the HA at-tribute.

Data type: Integer

Value: 0 or 11 = The history buffer (event list) is blocked

Default: 0


PB Printout Blocking

Blocks and unblocks printout generation. When printout is blocked, no printout isgenerated even though the situation according to the PA attribute would generate aprintout.

Data type: Integer

Value: 0 or 11 = The printout is blocked

Default: 0




1MRS751253-MEN

ABB Automation68

UB Update Blocking

This attribute blocks and unblocks the updating of the process object. When the ob-ject is blocked (UB = 1), it is not updated the process, nor from SCIL. An error statusis generated if the OV value is set by SCIL. Consequently, both input and output viathe OV attribute is blocked. The OV attribute may, however, be read by SCIL.

When UB is set to 1, the OS attribute of the object is set to INVALID ( 2 ) to indicatethat the value may be outdated.

Data type: Integer

Value: 0 = Updating is not blocked1 = Updating is blocked

Default: 0


XB Activation Blocking

Blocks and unblocks event channel activation. When event channel activation isblocked, nothing is activated, even though the situation would imply so.

Data type: Integer

Value: 0 or 11 = The event channel activation is blocked

Default: 0


3.3.5 Operation Counters Attributes

These attributes are used for counting the operation of an object. They can be used,for example, for monitoring the need for service. The attributes are valid for BI, BOand DB objects.

CO Counter Overflow

This attribute is set to 1 when the CL attribute (Counter Limit) is exceeded. The at-tribute is automatically reset when the CV attribute is reset.

Data type: Integer

Value: 0 or 11 = Overflow on

Access: Read-only



ABB Automation 69

CV Counter Value

This attribute counts how many times the object is set to one (1). The CV attribute isincremented each time the object is changed to one (1), independent of whether theset order comes from the process or from SCIL.

The attribute can be reset with SCIL (no automatic reset).

Data type: Integer

Value: Integer

Initial value: 0

Access: No limitations. Cannot be fetch with FETCH (SCIL section 8.7),nor modified with #MODIFY.

3.3.6 Minimum and Maximum Values

The attributes in this section apply to analog input (AI) objects. All the minimum andmaximum attributes are stored on RAM only, not on disk. They are passed as snap-shot variables to format pictures and event channels.

MM Minimum time Milliseconds

The milliseconds of the time when the minimum value (the MV attribute) occurred.

Data type: Integer

Value: 0 ... 999

Unit: Milliseconds

Access: Read-only

MT Minimum Time

The time in seconds when the minimum value (the MV attribute) occurred.

Data type: Time

Value: Time

Unit: Seconds

Access: Read-only



1MRS751253-MEN

ABB Automation70

MV Minimum Value

Records the lowest value of the AI attribute since last reset. At the first update of theobject after application startup, the MV attribute is reset to the current value. It mayalso be reset by SCIL by writing any value into the MV attribute (normally it is resetto the current value of AI).



Default: The value of the object at application start-up


XM Maximum time Milliseconds

The milliseconds of the time when the maximum value (the XV attribute) occurred.

Data type: Integer

Value: 0 ... 999

Access: Read-only

XT Maximum Time

The time in seconds when the maximum value (the XV attribute) occurred.

Data type: Time

Value: Time

Unit: Seconds

Access: Read-only

XV Maximum Value

Records the highest value of the AI attribute since last reset. At the first update of theobject after application startup, the MV attribute is reset to the current value. It mayalso be reset by SCIL by writing any value to the MV attribute (normally it is reset tothe current value of AI).





ABB Automation 71

Default: The value of the object at application start-up


3.3.7 Stamps Set by the Communication System

The attributes in this section contain information set in NET on the basis of stamps setby the process units (in the relays or RTUs) in accordance with the IEC 870 - 5 - 103standard. If the communication protocol supports these attributes, they are updated inthe process database along with the object value. The following rules apply for theBL, SB, OR and OF attributes:

• A change of a quality attribute generates an event if EE = 1.

• A change of a quality attribute activates an event channel, a printout and/or his-tory logging if the activation is enabled (AE == 1, LD <> 0 or HE == 1) and theactivation criterion (AA, PA or HA) is "NEW VALUE" or "UPDATE".

• In such activation, the changed attribute is reported as the value of CA pseudo-attribute. If more than one attribute is changed at the same time, each change willbe reported separately in any order. For example, if OV changes from 0 to 1 andSB from 1 to 0, two activations occur, one with CA == "BI", BI == 1 and SB ==0, the other with CA == "SB", BI == 1 and SB == 0.

• When the switch state (SS) or the substitution state (SU) of the object ischanged, the quality attributes are set to 0.

RA and RB attributes are of informative character and do not affect the function ofthe process object. The CT attribute affects the activation of the post-processing.

The attributes are supported by protocols based on the IEC 870 - 5 - 103 standard,also possibly by other protocols (CT). If a protocol does not support the attributes,they can still be used but must be set with SCIL. However, the attributes cannot be setone by one using the #SET command. They may only be set along with the OV attrib-ute using list value in the #SET command, see the OV attribute in section 3.3.1.

All attributes in this section are stored only in RAM.

BL Blocked

The updating of the value has been blocked in the relay.

Data type: Integer

Data type: 0 or 1

Access: Read-only. Can be written together with the OV attribute, see sec-tion 3.3.1.



1MRS751253-MEN

ABB Automation72

CT Cause of Transmission

The type of the data transmission from the station to the process database. The func-tion of the CT attribute can be determined by setting a base system STY object attrib-ute, see the System Objects manual, Chapter 9.

There are the following types of data transmission:

UNKNOWN Updating is not marked regarding the type of transmissionbecause the protocol does not support the attribute

SPONTANEOUS Spontaneous updating caused by a change in the station

INTERROGATED The transmission started on an interrogation from Micro-SCADA

HISTORY The transmission contains history data from the historybuffer of the station

If CT = UNKNOWN, the process object is updated in the process database and theconsequential actions (post-processing) takes place according to the activation attrib-utes, that is, the update is regarded as spontaneous.

If CT = SPONTANEOUS, there is a slight difference in the case of the first update ofthe process object (when OS is 10 before the event). Post-processing (printout, eventchannel activation and history logging) is done regardless of the value of the corre-sponding control attribute (PU, AF or HF, section 3.2).

If CT = INTERROGATED and the object value has not changed, there is a slight dif-ference in the post-processing when the activation criteria is UPDATE, see the AA,HA and PA attributes in section 3.2.

If CT = HISTORY, the process database is not updated at all. Only post-processing(printout, event channel activation and/or history logging) is done. The snapshot vari-able list and the history buffer (and history log) entry contains the received OV valueand the received communication protocol attribute values. The rest of attributes arecopied from the process object. The pseudo-attribute CA is set to "CT".

Data type: Integer

Value: 0 ... 255 as defined by the CT attribute of the station type (theSTYn:BCT attribute, see the System Objects manual, Chapter 9).The following values apply to stations of type REX:

0 = UNKNOWN (applies to all station types)1 = SPONTANEOUS2 = INTERROGATED3 = HISTORY

Value 0 may mean that the attribute is not supported by the proto-col.

Default value: 0



ABB Automation 73

Access: Read-only. The attribute can be written along with the OV attrib-ute, see section 3.3.1.

OR Out of Range

The station cannot handle the signal read from the process. An example could be thatthe signal value is larger or smaller than the range supported by an analog/digital con-verter.

Data type: Integer

Value: 0 or 1

Access: Read only. The attribute can be written along with the OV attrib-ute, see section 3.3.1.

RA Reserved A

RB Reserved B

These attributes are used for protocol dependent data. At present they are used by theRP571 protocol as follows:

RA Relative time

RB Event number

Data type: Integer

Data type: Integer

Access: Read only. The attribute can be written along with the OV attrib-ute, see section 3.3.1.

SB Substituted

The value read from the process has been substituted by another value in the station.For example, the value has been changed manually on the relay front panel.

Data type: Integer

Access: Read-only. The attribute can be written along with the OV attrib-ute, see section 3.3.1.



1MRS751253-MEN

ABB Automation74

3.3.8 S.P.I.D.E.R. RTU Specific Attributes

EP End of Period

This attribute concerns only PC (Pulse Counter) type objects and tells the type ofpulse counter reading. Each pulse counter update has this attribute.

Data type: Integer

Value: 0 = Intermediate reading1 = End of period reading (including intermediate reading)

Initial value: 0

Access: Read-only

OF Overflow

This attribute indicates is there an overflow in the event recording buffer or pulsecounter history buffer of the RTU.

The attribute is only valid for pulse counters and event recording objects (see section3.3). Each update of these objects, originating from the RTU, contains the OF attrib-ute.

Data type: Integer

Values: 0 = No overflow1 = Overflow

Access: Read-only

SE Selection

Selecting the object means that MicroSCADA performs a check-back before execut-ing the operation.

Selection of a IEC or REX type object in manual or fictive state is done with the pre-defined semantics given in Table 4 on page 76 of this chapter. For an object ofIEC/REX type in auto state only output objects (BO, DO, AO, BS) is set with #SETLIST command, see Table 4 on page 76.

Data type: Integer

Value: 0 = Cancelling the selection (IHC)1 = Selection (CBXC)

Default value: 0



ABB Automation 75

Access: Read, conditional write. It can be written with #SET, provided thatthe object is in use (IU = 1). Not configurable. Not included inFETCH.

Selection of a RTU command object (BO).

Example:#ERROR CONTINUE#IF CMD:PSE1 == 0 #THEN #BLOCK

#SET CMD:PSE1 = 1#IF STATUS == 0 #THEN #BLOCK

#SET CMD:PBO = 0#IF STATUS <> 0 #THEN !SHOW ERROR "FAILED"#BLOCK_END

#ELSE !SHOW ERROR "SELECTION FAILED"#BLOCK_END

#ELSE !SHOW ERROR "ALREADY SELECTED"

If not already selected, the command object CMD1 is selected, otherwise an errormessage "ALREADY SELECTED" is displayed. If the selection succeeded, thecommand object is set to 0, otherwise an error message "SELECTION FAILED" isdisplayed. If the set operation did not succeed, an error message "FAILED" is dis-played.

SP Stop Execution

Writing to this attribute interrupts the RTU200 object command under execution.

Data type: Integer

Value: 1

Access: Read, conditional write. It can be written with #SET, provided thatthe object is in use (IU = 1). Not configurable. Not included inFETCH.

Example:#SET CMD:PSP5

3.3.9 IEC Specific Attributes

Following attributes are needed for store and/or forward all the needed informationwhen IEC protocol is used for communication.

They have a predefined semantics only for REX and IEC stations: For output objectsthey are configuration attributes that are sent within ACP messages (see below). Forinput objects they are dynamic attributes received in ACP messages. The attributes

SE = 1 may mean that the object is already selected by another operator. The objectcan not be selected again until SE is set to 0.



1MRS751253-MEN

ABB Automation76

are included in the snapshot variable lists. To fully support selection and its cancella-tion in the IEC protocols, the schema presented in Table 4 is to be used.

CT, OG and TY are always sent in the ACP message if corresponding attribute isspecified in the "#SET" list. If not in the list, the values in the corresponding databaseattributes are sent unless they are zero.

New OP_SUBITEM = 17, Codes for OP_SUBITEM are:

0 = Activate, execute

1 = Activate, select

2 = Deactivate, execute

3 = Deactivate, select

Table 4. Schema concerning SCIL interface, process database and ACP messages. SOV stands for SelectedOV, a value stored in the database (without a SCIL attribute name).

Action SCIL ACP (* Process data-base

Select Open #SET n:PSEi=

list(OV="open"[,CT=a][,OG=b][,TY=c])

OV="open", OP=1 [,TY=c]

[,CT=a][,OG=b]

SE=1, SOV=OV

Select Close #SET n:PSEi=list(OV="close"[,CT=a][,OG=b][,TY=c]) OV="close", OP=1, [,TY=c]

[,CT=a][,OG=b]

SE=1,SOV=OV

Select Deactivate #SET n:PSEi=0 |

#SET n:PSEi=list(SE=0[,CT=a][,OG=b][,TY=c])

OV=SOV, OP=3, [,TY=c]

[,CT=a][,OG=b]

SE=0

Execute Open #SET n:POV="open" |

#SET n:POVi=


OV="open" [,TY=c]

[,CT=a][,OG=b]

OV="open", SE=0

Execute Close #SET n:POVi="open" |

#SET n:POVi=


OV="close"[,TY=c]

[,CT=a][,OG=b]

OV="close", SE=0

Execute Deactivate #SET n:PSEi=0 |

#SET n:PSEi=list(SE=0[,CT=a][,OG=b][,TY=c])

OV=OV,

if SE==0 OP=2 else OP=3,[,TY=c] [,CT=a][,OG=b]

SE=0

OG OriGinator identification

Defines the source system of the data, for both input and output objects. For inputobjects this is dynamic information, for output respectively a configuration attribute.OG is sent along the ACP message in control messages if its value differs from 0. Seealso table above.

Data type: Integer

Value: 0 … 65535




ABB Automation 77

QL command QuaLifier

Extra qualifier for commands, various purposes, for both input and output objects. Forinput objects this is dynamic information, for output a configuration attribute. QL issent along the ACP message in control messages if its value differs from 0. See alsotable above.

Data type: Integer

Value: 0 … 65535


TY TYpe identification

Defines how the command should be interpreted by the communication unit, (e.g. sin-gle/double bit command, regulating step command). For input objects this is dynamicinformation, for output objects a configuration attribute. TY is sent along the ACPmessage in control messages if its value differs from 0. See also table above. ASDUtype or number of received command or indication is written to the TY attribute of theinput process object. The ASDU types vary according to the used protocol. For exam-ple ASDU type 45 for IEC870-5-101 protocol is IEC single command.

Data type: Integer

Value: 0 ... 65535

Access: Unlimited Access

3.3.10 File Transfer Attributes

The term File Transfer is used to mean any bulk data transfer between MicroSCADAand a station. A file is a sequence of bytes, of any length, with no interpretation of itscontents. The implementation of file transfer in MicroSCADA is protocol independ-ent.

In MicroSCADA, a file is represented by a disk file and identified by its disk filename. In a station a file is typically, but not necessarily, a memory segment in RAMand the identification or naming is protocol dependent. The ID is handled in Micro-SCADA as a byte string with no interpretation.

File transfer is always initiated by MicroSCADA, spontaneous file transfer from sta-tion to MicroSCADA is not supported. File transfer is done asynchronously. It is ini-tiated by SCIL, but the SCIL command does not wait for the completion of the trans-fer. File transfer is implemented via the process database.

FT (File Transfer) process object type implements the file transfer functionality. Thefollowing functions are supported by this implementation:

• Receiving (uploading) a file from a station.

• Sending (downloading) a file to a station.



1MRS751253-MEN

ABB Automation78

• Browsing the file hierarchy of a station.

• Reading file attributes from a station.

• Deleting a file or directory in a station.

The process objects of this type have all the same common attributes as “real” processobjects. Especially, the post-processing attributes, such as EE and AE, may be used toreport the completion of the transfer to the application. The completion of the transferis indicated by a change of the value of FT attribute. The address attributes OA andOB have no meaning in conjunction with FT objects, OA should be set to 0, if set atall. There may be any number of FT objects connected to one station, for exampleeach configured to a specific download/upload.

DC Directory Contents

This attribute contains the contents of a transferred folder.

Data Type: Vector list

Value: TYPE Text value “FILE” or “DIRECTORY”

ID Byte string, the file’s ID in the station

NAME Text value, the name of the file in the station

CREATION TIME Time value

LENGTH Integer value, length of the file as bytes

AUXILIARY Byte string value, station specific auxiliary in-formation

Attributes NAME, CREATION TIME, LENGTH andAUXILIARY are returned only if supported by the station.

Access: Read-only

Example:@UPLOAD = FT:PDC10@FILE_1 = %UPLOAD(1)@TYPE_1 = FILE_1:VTYPE

FF File Function

The functions to be performed on a file.

Data type: Integer

Value: 0 … 4:0 = None1 = Send a file2 = Receive a file



ABB Automation 79

3 = Read Directory4 = Delete a file or directorySetting FF to 0 cancels the ongoing transfer

Default value: 0

Access: Read, conditional write. May be written only when switch state isAUTO

FN File Name

The tag of the disk file to be sent or received.

Data type: Byte string

Value: Byte string


Example:#SET FT:PFN10 = FM_FILE(“C:\sc\conf.txt”)

FP File Transfer Progress

Displays the number of bytes transferred between NET and the station during currenttransfer (FT==1) or last transfer (FT==4). Valid only when FF==1 or FF==2, other-wise 0.

Data type: Integer

Value: 0 … 2 GB

Unit: Bytes

Access: Read-only

FT File Transfer

Displays the state of transfer.

Data type: Integer

Value: 0 … 4:0 = Idle1 = Transfer in progress2 = Cancelled, by the user3 = Aborted,by the station or a communication error4 = Ready

Default value: 0



1MRS751253-MEN

ABB Automation80

Access: Read-only

ID Identification

The file’s ID in the station. May be a fixed value known by the SCIL programmer inadvance, or may be retrieved by reading the directory structure of the station. ID isgiven protocol specifically in little-endian or big-endian way depending on whetherthe LSB or the MSB is read first.


Value: Byte string


Example:#SET FT:PID10 = PACK_STR(VECTOR(97,234),”byte_string”,1,”big_endian”)

ST Status

A SCIL status code giving more information when the transfer is aborted (FT = 3).

Data type: Integer

Value: A SCIL status code

Default value: 10

Access: Read-only

Examples of Using File Transfer

The following sequence may be used in a SCIL program to receive a file from a sta-tion or send a file to a station:

1 Set attributes FN and ID (in any order) to identify the file both in MicroSCADAand in the station. Setting one of these attributes automatically sets FT to 0 (idlestate).

2 Set FF to 1 or 2 to initiate the transfer. This step generates a SCIL error if thestation cannot accept the request (invalid ID, not enough memory to receive thefile, etc.).

3 Wait (in a way or another) for the completion of the transfer or cancel it by settingFF to 0.

The following sequence may be used to browse the directory structure in a station:

1 Set ID to zero length byte string (indicating the root directory of the station).

2 Set FF to 3 to initiate the transfer.

3 Wait for the completion (or cancel by setting FF to 0).

4 Read the result from the DC attribute.



ABB Automation 81

5 Pick up the ID of the desired file and start a file transfer, or pick up the ID of asubdirectory, set it to the ID attribute and repeat steps 2 to 5.

The following sequence may be used to read attributes of a file:

1 Set attribute ID to identify the file in a station.

2 Set FF to 3 to initiate the query.

3 Wait for the completion.

4 Read the result from the DC attribute (DC contains the attributes of the file as one-element long vectors).

The following sequence may be used to delete a file in a station:

1 Set ID attribute to identify the file in the station.

2 Set FF to 4.

3 Wait for the completion.

3.3.11 Event History Attributes

Each event in the history database contains the snapshot of all the attributes of theprocess object, except CX attribute. So all the attribute values are saved at the mo-ment of the event. Additionally, information related to each event contains some extraattributes described below. These attributes are not “real attributes”, rather “virtualattributes”. They may be used in process database queries in addition to the other pro-cess object attributes. For more information about the commands used for queries, seeChapter 8 in the manual Programming Language SCIL and for information on how toconfigure the even history see System Configuration manual, Chapter 13. Historyconfiguration attributes are described earlier in this Chapter.

If the event log and history buffer are used instead of history database, the only valuein the following list that is stored is the value of CA attribute. In addition to the valueof CA attribute, also the values of the attributes listed in the description of HL attrib-utes are stored.

CA Changed Attribute

This attribute is the name of the process object attribute that changed and caused theevent activation.

In addition to the fact that it is used in the history database, the attribute is included inthe history buffer. From the buffer it is transmitted as a "snapshot variable" (%CA) tothe physical format picture (PF) and the event channel (AN). Unlike ordinary attrib-utes, it cannot be included in an object notation.

Data type: Text

Value: A text of two characters, the name of the attribute, for example"AI"

Access: Read only. The attribute can only be read using the SCIL functionPROD_QUERY and as %CA in the physical format picture (see



1MRS751253-MEN

ABB Automation82

the PF attribute, section 3.2.10) and in objects started by the eventchannel (see the AE attribute in this chapter). It cannot be readwith an object notation and it cannot be written.

ED Event Daylight saving

Indicates is the daylight saving time in use when the value of ET attribute is calcu-lated.

Data type: Integer

Value: 0 = Not known1 = Daylight saving time not in use2 = Daylight saving time in use

Access: Read-only

EM Event time Milliseconds

The milliseconds of the time the event appears. So when this attribute is used with theET attribute, you are able to know the time in accuracy of a millisecond. EM attributeof an event is usually equal to RM, but not always. For example, if XB is changed bySCIL, EM tells the time of change and RM reflects the latest update of OV attribute.

Data type: Integer

Value: 0 ... 999

Unit: Milliseconds

Access: Read-only

ET Event Time

The time the event appears, in accuracy of a second. ET attribute of an event is usu-ally equal to RT, but not always. For example, if XB is changed by SCIL, ET tells thetime of change and RT reflects the latest update of OV attribute.

Data type: Time

Value: Time

Unit: Seconds

Access: Read-only

EX Event comment teXt

Data type: Text



ABB Automation 83


Default Value: Empty


HD History logging Daylight saving

Indicates is the daylight saving time in use when the value of HT attribute is calcu-lated.

Data type: Integer

Value: 0 = Not known1 = Daylight saving time not in use2 = Daylight saving time in use

Access: Read-only

HM History logging time Milliseconds

Records the milliseconds of the time when the event was written to the history data-base. So when this attribute is used with the HT attribute, you are able to know thetime in accuracy of a millisecond.

Data type: Integer

Value: 0 ... 999

Unit: Milliseconds

Access: Read-only

HT History logging Time

Records the time when the event was written to the history database.

Data type: Time

Value: Time

Access: Read-only



1MRS751253-MEN

ABB Automation84

3.4 Defining Process Objects

Attributes

When a new process object of predefined type is defined, some definition attributesare obligatory, others are optional and some attributes are not valid depending on theobject type, see Table 2. The following attributes are the minimum requirements:

LN Logical name (common to a group)

IX Index (not for user-defined object types)

PT or any of the attributes AI, AO, BI, BO, BS, DI, DO, DB, PC.

In addition to the three attributes mentioned above, real objects with process commu-nication require the following attributes:

UN and OA plus the OB attribute for binary objects (except S.P.I.D.E.R. RTU objectsof BO type).

All analogue objects require:

SN Scale Name

For example, the following optional features can be defined as follows:

• Alarm generating objects: the alarm handling attribute AC (Alarm Class), alarmlimits or AG, LA, the SZ attribute for SCADA supervision.

• Monitor alarm: the PI and PD attributes.

• Automatic printing: the PF and LD attributes.

• External alarm: the LD attribute.

• Event channel: at least the AN and AE attributes.

• Event object (event controlled updating in pictures): the EE attribute.

• History buffering (including the object in the event list): the HE attribute.

• Switch state AUTO: the SS attribute.

• Taking the object into use: the IU attribute.

Creating Process Objects with SCIL

To create a process object with SCIL, create it with the #CREATE command and as-sign it attributes using LIST. The LN and IX attributes need not be given.

To copy an existing process object to a new one:

1 Create a variable object with #CREATE and assign it attributes with some SCILdatabase function (FETCH, PHYS_FETCH, NEXT or PREV).

2 If desired, change the attributes with #SET or #MODIFY.



ABB Automation 85

3 Create the process object with #CREATE and assign it the value of the variableobject as a variable.

Examples

Example 1:#CREATE PROC:P 1= LIST(AI = 0, SN = "S")

An analogue input object is created with the name PROC, index 1, analogue inputvalue 0 and scale name "S".

Example 2:@V = FETCH(0,"P","OLD",1)#SET V:VLN = “NEW”#CREATE NEW:P1 = %V

A process object called "NEW" is created with the same attributes as the process ob-ject "OLD" with index 1 in the same application.

3.5 Process Object Group Attributes

This section describes the process object group attributes that define the object groupsand their functions. The attributes of a process object group are common for all theprocess objects under that certain group, except for ZT which is separately defined forthe process object groups and the process objects. The configurable process objectattributes have been introduced already in an earlier section of this chapter.

GC Group Comment


Data type: Text

Value: Text


GT Group Type

An arbitrary type number defined by the programmer.

Data type: Integer

Value: 0 ... 255

Default value: 0




1MRS751253-MEN

ABB Automation86

LF Logical Format

The name of the "logical" format picture. The picture is printed with the command#LIST, see Chapter 2. When printing the picture with #LIST, the object notationshould be given without an index, otherwise the physical format (the PF attribute) isused. Objects of user-defined types do not have this attribute.

When printing the picture with the #LIST command, a variable with the name LN isautomatically formed and assigned the name of the object group (the attribute LN).The variable %LN can be used as the process object name in the format picture. Inthis way, several different objects can use the same logical format picture.

Data type: Text

Value: Picture name

Indexing: No index, the attribute is common for all objects in the group



The time when the object group was created or modified. This attribute is set by themain program when the object group is created and each time the object group is up-dated by the #MODIFY command (for example, by the process object group defini-tion tool).

Data type: Time

Data type: Time

Access: Read-only


MicroSCADA4 Scales

ABB Automation 87

4 Scales

About this Chapter

This chapter describes scale objects and their attributes:

4.1 General: The basic properties of scale objects, their use and function, etc.

4.2 Scale attributes: The Scale attributes listed and described in alphabeticalorder.

4.3 Defining scales using SCIL: Required attributes and an example.

4.1 General

Use

Scales define algorithms for the transformation of data transferred from the processstations to the values stored in the process database. The values stored in the processdatabase should be the same as the measured quantities.

Every definition for analog process object includes a scale name (the process objectattribute SN), which is the name of the scale to be used in the transformation. Thesame scale can be used by several analog process objects, independent of their type(analog input or output). With regard to fictitious process objects, scales have nomeaning, yet they are required in the process object definition.

Function

The stations (RTUs, protective equipment, PLCs and other process control units) re-ceive analog signals from the process instrumentation as electrical currents (mA) orvoltages (V). In the stations, these values are transformed to digital values. In the pro-cess database the digital values are scaled to the analog unit of the process object us-ing the scaling algorithm given by the scale name of the process object. The analogoutput values are scaled correspondingly in the process database before they are sentout to the stations.

As an example, scaling can mean that the digital number 0 is translated to 20 oC andthe digital number 1000 to 100 oC (see Figure 9).

Scale Object Notation

Scale attributes can be accessed from SCIL with the notation:

name:[appl]X[at]

MicroSCADA4 Scales


1MRS751253-MEN

ABB Automation88

where

‘name’ Is the object name

'appl' Is the logical application number

'at' Is the attribute name

See also Chapter 2.

All scale attributes can be both read and written from SCIL without limitations.

Storage

Scales are stored in the process database on disk and in RAM.

4.2 Scale Attributes

LN Logical Name

The name of the scale.

Data type: Text

Value: The name must follow the rules for object names given in section2.2


SA Scaling Algorithm

The algorithm by which scaling is performed: one-to-one, linear or stepwise linearscaling, see Figure 9.

Data type: Integer

Value: 0 = 1:1 scaling.1 = Linear scaling2 = Stepwise linear scaling. The scale is linear in a number of

intervals, but the scale as a whole is non-linear.

Default: 0



MicroSCADA4 Scales

ABB Automation 89

SC Scaling Constants

The constants that determine the inclination of the linear scaling and the inclination ofthe linear intervals of the stepwise linear scaling. The inclination is given as pairs ofcorresponding MicroSCADA process database values and RTU values.

Data type: Vector

Value: If SA = 1: Vector with four real elements

If SA = 2: Vector of maximum 100 real elements representing the

coordinates of 50 points on the scaling curve

Indexing: If SA = 1:Index 1 = The lower station valueIndex 2 = The upper station valueIndex 3 = The lower process database valueIndex 4 = The upper process database value

If SA = 2:An odd index refers to a station value and thefollowing even index to corresponding processdatabase value. The values of odd indices must beascending.

Default value: No


Linear Scaling Stepwise Linear Scaling

ProcessDatabase

SA = 1SC = (0,1000,20,100)

SA = 2SC = (0,20,200,10,500,40,750,50,1000,100)

100

50

0

Stations

0 500 1000

ProcessDatabase

100

50

0

Stations

0 500 1000

Figure 9. An illustration of linear and stepwise linear scaling

MicroSCADA4 Scales


1MRS751253-MEN

ABB Automation90


The time at which the object was created or modified. This attribute is set by the mainprogram when the object is created and each time it is updated in the application ob-ject definition tool or using SCIL (the #CREATE and #MODIFY commands).

Data type: Time

Access: Read-only

4.3 Defining SCALE Objects Using SCIL

Required Attributes

When defining a new scale object, the LN attribute is required. If no other attribute isdefined, the scale will be a 1 to 1 scale (SA = 0). If the SA attribute is set to 1 or 2, theSC attribute must be defined as well.

Example:

Creating a linear scale named LINEAR:#CREATE LINEAR:X = LIST( SA = 1, SC = (1,100,10,500))


MicroSCADA5 Data Objects

ABB Automation 91

5 Data Objects

This chapter describes the data objects, their attributes and how to define data objectswith SCIL. It is divided into the following sections:

5.1 The use of data objects, the activation and function of the data objects,etc.

5.2 Data object attributes: The data object attributes are listed and described.The attributes are grouped in sub-sections according to their functions.

5.3 The principles for defining data objects using SCIL and examples.

5.1 General

Use

Data objects (datalog objects) are used to sample and calculate, register and storedata. A data object can contain one or more, up to 500 000, registered values. Eachregistered value has a validity stamp (status code) and a time stamp.

Data objects can be used for storing trend data, historical data, running plan data, datafor system configuration, optimisation, calculation, etc. Data objects can also be usedas global variables when there is a need for using the same data in several differentSCIL contexts (pictures, command procedures, Visual SCIL contexts).

Each data registration is done according to a SCIL expression and a logging function.The execution of data registration can be started manually or automatically.

Function

The data of a data object is sampled or calculated in accordance with a SCIL expres-sion, that can contain constants and variables as well as data from other objects. (Seethe Programming Language SCIL manual.) The variables used in an expression mustbe defined to the data object. The final data registration is performed via a loggingfunction, that enables, for example, an automatic calculation of mean values, sums,integral values, etc. The logging function is carried out using each new calculated orsampled value and the latest internal object value. Every internal and registered objectvalue gets a status code and a time stamp.



1MRS751253-MEN

ABB Automation92

Figure 10. The execution of data objects

The registered values can be accessed as vector elements by means of indices. Theoldest registered value has the index 1. The maximum number of registered values tobe stored can be chosen freely. When the number of registrations exceeds the maxi-mum number, the oldest registered value will be omitted.

The execution of a data object, i.e. a new data registration, can be started in the fol-lowing ways:

• From a SCIL program - a picture program, a command procedure or a method -with the command #EXEC (section 2.3.).

• From a time channel, which implies an automatic time dependent execution. Exe-cution through a time channel is performed in accordance with the priority of thedata object. For more information see the EP attribute in Chapter 5). Time activa-tion is used, e.g., when trend data is sampled from a process object.

• From an event channel, which implies an automatic event dependent executioncaused by a change in a process object. A data object can, for example, store theevent history of a certain process object. The registration time of a process objectcan be copied to the data object. For more information see the TS attribute,Chapter 5.



ABB Automation 93

All three kinds of activations can be applied to the same data object.

Variables

Variables that are to be used in the expression must be known by the data object. Ifthe object is executed with #EXEC, variables can be transmitted with the variable list(see Chapter 2). When execution starts from an event channel, certain attribute valuesof the process object are transmitted as variables with the same name. See Chapter 8.When the data object is executed through a time channel, the data object expressioncan include variables that were defined in command procedures, which were executedearlier by the same time channel.

Executing Tasks

There are a number of different tasks, at least 2 and at most 17, which execute dataobjects, command procedures and time channels. If a task is busy when an executionorder comes, the order is put into a queue. The order is executed when the task be-comes free.

A task always executes an object completely before it starts to execute the next ob-ject. Depending on the PE attribute (see Chapter 5), the execution is handled by a par-allel or non-parallel task. The maximum number of parallel queues in use for a par-ticular application is defined by attribute PQ. The executing task can be determined inaccordance with Figure 11.

Figure 11. The tasks that execute the data objects, command procedures and timechannels



1MRS751253-MEN

ABB Automation94

Storage

Data objects are stored in the report database, which is on disk, or in files specified bythe HN attribute. In addition, the most frequently used data objects may be stored inthe primary memory (report cache memory), where they share the memory space withother report objects (command procedures, time channels, event channels). The mem-ory space reserved for this purpose is application dependent and set with the attributeSYS:BRC or with a tool.

To get faster reporting, the dynamic data of a data object can be stored exclusively inprimary memory. This is determined by an attribute (the MO attribute, section 5.2.5).

Data Object Notation

Data object attributes - the registered data as well as the static attributes - are accessedfrom SCIL with the following object notation:

name:[a]D[at][i]

where

’name’ Is the name of the object


’at’ Is an attribute name

‘i' Is an index or index range that refers to the registered object values(the OV, OS and RT attributes). The oldest registered value hasthe index 1.

For example, the notation DATA:DOV32 is the 32:nd registered data in the data ob-ject named DATA.

A data object notation without an attribute refers to the object value (the OV attrib-ute), except with the command #EXEC, which refers to the whole object. The OV, OSand RT attributes without an index refer to the "internal object value".

Editing Data Objects

Registered values can be changed with the SCIL command #SET (section 2.3) and thedata object notation. The #SET command is, for example, used in the definitions tool(section 5.3.1.). An object value changed with #SET always gets an OK status (OS =0). The registration time (the RT attribute) is updated. Changing a registered objectvalue with #SET does not affect subsequent registrations. However, changing the ob-ject value (the OV attribute) without an index means that the "internal object value" ischanged, which will affect subsequent registrations.



ABB Automation 95

Clearing Data Object Registrations

The following situations clear all registered object values, which means that the ob-ject values get "Not sampled" status (OS = 10) and the next registration starts fromindex number 1:

• The time channel, that executes the data object, is initialised (see Chapter 7).

• The logging function (the LF attribute) is changed.

• The LR attribute (last registration) is set to 0.

In the last case, when the LR attribute is set to 0, the registered data object values arecertainly cleared. However the "internal object value" (see Figure 10) is preserved andwill affect the new registrations.

If the chosen number of maximum registrations (the HR attribute) is changed to alower number, the oldest registered values are cleared.

5.2 Data Object Attributes

Here the data object attributes are grouped into the following sub-sections:

5.2.1 Basic Definitions: CM, FI, FX, IU, LN, VL, VT, ZT

5.2.2 Execution Definitions: IN, LF, PS, SR

5.2.3 Registered Data: OS, OV, RT

5.2.4 Execution Control: EP, PE, PQ, SE, TC, TS

5.2.5 Storage: HN, HR, LR, MO

The data attributes in section 5.2.3. represent the registered data, the validationstamps and time stamps. All other attributes describe the definition of the object.

5.2.1 Basic Definition

CM Comment

The comment text of the object.

Data type: Text

Value: Text




1MRS751253-MEN

ABB Automation96

FI Free Integer

This attribute is reserved for the SCIL application, it has not any semantics known tothe base system.

Data type: Integer

Default value: 0

Access: Full access by SCIL

FX Free Text


Data type: Text


Default value: ""


IU In Use

The IU attribute specifies whether the object is in use or not. When the object is not inuse (IU = 0), it cannot be executed. However, its definition is preserved and the at-tributes can both be read and written as usual.

Data type: Integer


Default: 0


LN Logical Name

The logical name of the data object. The name must follow the rules for object namesgiven in section 2.2.

Data type: Text





ABB Automation 97

VL Value Length

Maximum string length. This attribute is used to define the length of the VT attribute.

Data type: Integer

Value: 1 … 255, if VT="TEXT", otherwise 0

Access: Read only, configurable

The allowed LF (Logging Function) values for this data type:

INTEGER: DIRECT, SUM, DIFFERENCE, PULSE DIFFERENCE,MAXIMUM. MINIMUM, COPY

TIME: DIRECT, MAXIMUM, MINIMUM, COPY

TEXT: DIRECT, COPY

VT Value Type

VT attribute supports REAL, INTEGER, TIME and TEXT values for data objects.

Data type: Text

Value: "REAL", "INTEGER", "TIME" or "TEXT"

Default: "REAL"

Access: Read only, configurable with #CREATE but not with #MODIFY.

The allowed LF (Logging Function) values for this data type:

INTEGER: DIRECT, SUM, DIFFERENCE, PULSE DIFFERENCE,MAXIMUM. MINIMUM, COPY

TIME: DIRECT, MAXIMUM, MINIMUM, COPY

TEXT: DIRECT, COPY

The evaluation of the IN attribute must result to the data type defined by the VT at-tribute. However, if VT is INTEGER, the following data conversions are done auto-matically: real values are rounded to nearest integer value and boolean values areconverted to 0 (= FALSE) or 1 (= TRUE).


The time when the object was created or modified. This attribute is set by the mainprogram when the object is created and each time it is updated by the application ob-ject definition tool or by SCIL (the #CREATE and #MODIFY commands).



1MRS751253-MEN

ABB Automation98

Data type: Time

Access: Read-only

5.2.2 Execution Definitions

IN Instruction

The SCIL expression of the data object. This expression must follow the rules forSCIL, see the Programming Language SCIL manual, Chapter 6. Data registrationstarts with the calculation of this expression, see Figure 10.

Data type: Text

Value: Text


The evaluation of this attribute must result to the data type defined by the VT attrib-ute. However, if VT is INTEGER, the following data conversions are done automati-cally: real values are rounded to nearest integer value and boolean values are con-verted to 0 (= FALSE) or 1 (= TRUE).

LF Logging Function

The operation to be performed on the calculated/sampled value before registration.The logging functions use the calculated/sampled values and the internal object value(see Figure 10).

Data type: Integer

Values: 0 ... 10:

0 = DIRECTNo calculation is performed. The value calculated/sampled withthe SCIL expression is directly registered.

1 = SUMThe sum of all calculated/sampled values

2 = MEAN VALUEThe mean value of all calculated/sampled values. (The time inter-val between samplings is not regarded.) The mean value is calcu-lated as the mean value of the last sampled/calculated value andthe last stored mean value (= the internal object value).

3 = INTEGRALThe time integral of all calculated/sampled values. The values areconsidered to be constant between executions. The time is calcu-lated in seconds, and it starts from 0 with the first execution of the



ABB Automation 99

data object. The value is calculated as the integral value of the lastsampled/calculated value and the last stored value.

4 = DIFFERENCEThe difference between two consequently calculated/sampled val-ues. The value is calculated as the difference value of the last sam-pled/calculated value and the last stored value.

5 = PULSE DIFFERENCEThe same as above, but the expression is regarded to be a pulsecounter, which is set to zero, when a certain value (the attributePS) is obtained.

6 = TIME DERIVATIVE The time derivative of two consequent calculated/sampled values.The time unit is seconds. The value is calculated as the time de-rivate value of the last sampled/calculated value and the last storedvalue.

7 = PULSE DERIVATIVE The same as above, but the expression is regarded to be a pulsecounter, which is set to zero, when a fixed value (the attribute PS)is obtained.

8 = MAXIMUMThe last registered value is the largest calculated/sampled valuesince the initiation of the data object. Smaller values entail noregistration.

9 = MINIMUMThe last registered value is the smallest calculated/sampled valuesince the initiation of the data object. Only smaller values are reg-istered, values larger than this entail no registration.

10 = COPYCopies the registered values into another data object. The statuscodes and the time stamps are also copied.

Default: 0


PS Pulse Scale

If the logging function is PULSE DIFFERENCE (LF = 5) or PULSE DERIVATIVE(LF = 7), the expression (the IN attribute) is regarded as a pulse counter. The PS at-tribute indicates at which value the physical pulse counter is set to zero and countingrestarts. Set the PS attribute to the maximum value of the pulse counter +1 (to regardthe zero value).

Data type: Integer or real



1MRS751253-MEN

ABB Automation100

Value: Integer or real


SR Source

The name of the data object to be copied when the logging function is COPY (LF =10).

Data type: Text

Value: Text, maximum 63 characters


TS Time Stamp

The TS attribute determines whether the RT attribute is updated by the operatingsystem time or from the variable %RT.

When the data object is started by an event channel, the %RT variable is the registra-tion time of the activating process object. Using the %RT variable as the registrationtime is useful when there is a time delay between the data object execution and theprocess event causing the execution.

Data type: Integer

Value: 0 = The RT attribute is set according to the operating system time when the object is executed

1 = The RT attribute is copied from the variable %RT if such a variable has been defined to the data object (see 5.1Variables)

Default: 0


5.2.3 Registered Data

OS Object Status

This attribute is generated automatically at each data registration. It describes the reli-ability of the registered value.

Data type: Integer or vector

Value: Integer or vector of integers. A status code, see the manual StatusCodes. The object status can be any status code corresponding toerrors that can occur in expressions. Examples:0 = The value is OK



ABB Automation 101

1 = The value is uncertain. The data object gets this status code if calculation of the expression failed and the logging function isanything else than DIRECT.

10 =The data object has not been calculated, for example, because it is new or since the MicroSCADA system has been out of use.

Indexing: History registration number. The attribute without an index refersto the internal object value (see Figure 10).


OV Object Value

The object value, i.e., the value obtained when the expression has been calculated andthe logging function performed.

Data type: Real, integer, text or time. Defined by the VT attribute.

Value: Real, integer, text or timeIf text, maximum 255 characters

Indexing: History registration number. The attribute without an index refersto the "internal" object value which is the same as the last regis-tered object value, unless some of the values have been changedwith #SET.



The registration time of the object value with an accuracy of one second. The timestamp is either set by the operating system or copied from a variable named %RT (seethe TS attribute in this chapter.). If the registered value is altered with #SET, the RTattribute also changes, so that it gets the value of the update time (set according to theoperating system time).

Data type: Time or time vector

Value: Time or time vector

Indexing: History registration number. The attribute without an index refersto the "internal" object value (Figure 10).

Setting a registered object value with the #SET command (with an index or indexrange) does not affect the subsequent registrations. However, setting the object valuewithout an index means setting the internal object value and, hence, affects subse-quent registrations, unless the logging function is DIRECT or COPY.



1MRS751253-MEN

ABB Automation102

Access: Read, conditional write. It can be written with the #SET command.

5.2.4 Execution Control

EP Execution Priority

The priority of the data object in relation to other data objects and command proce-dures executed by the same time channel. When the time channel is activated, the ob-jects are executed in the order determined by their priority. Objects with the same pri-ority can be executed in any order.

Data type: Integer

Value: 0 ... 2550 means the highest priority

Default value: 255


PE Parallel Execution

This attribute indicates whether the object is executed by a parallel task or not, seeFigure 11.

Data type: Integer

Value: 0 = Non-parallel execution1 = Parallel execution. The object is executed by the task

determined by the PQ attribute.

Default value: 0


PQ Parallel Queue

The number of the parallel queue, if there is a parallel execution (PE = 1). See Figure11.

Data type: Integer

Value: 0 ... APL:BPQ. PQ = 0 means that the system places the executionorder in the parallel queue that is emptied first (on the conditionthat PE = 1). PQ <> 0 is recommended for especially time criticalor time consuming objects.

Default: 0



ABB Automation 103


SE Start-up Execution

During application start-up, all time channels, which would have started during sys-tem break, are activated to make the reporting catch up real time. With this attributeyou can select to execute the data object or not during application start-up. Those dataobjects that are not executed are marked with NOT_SAMPLED_STATUS (OS = 10).

The SE attribute concerns data objects, which are in use, and connected to a timechannel, which is in use.

Data type: Integer

Value: 0 = The data object is not executed during application start-up1 = The data object is executed during application start-up as

started by the time channel

Default value: 0


TC Time Channel

The name of the time channel that starts the execution of the data object.

Data type: Text

Value: Maximum length 63 characters


5.2.5 Storage

HN History File Number

Data objects (the definitions as well as history registrations), command procedures,time channels and event channels are stored in files named APL_REPORT.nnn, where’nnn’ is a sequence number specified by the HN attribute. Each file can contain up to32 Mb data. The file number can be freely chosen from the range 0 ... 399.

Data type: Integer

Value: 0 ... 399, file number

Default value: 0




1MRS751253-MEN

ABB Automation104

HR History Registrations

The maximum number of registrations. When the number of registrations has reachedthis value, the oldest registered value will be omitted with every new registration.

When a new data object is created, required memory space is reserved for the maxi-mum number of registered data.

Data type: Integer

Value: 0 ... 500 000HR = 0 means that the data object contains only the "stored"

object value (see Figure 10), which is accessed with outindex.

Default value: 0


LR Latest Registration

The index for the latest registered value. Higher indices than this cannot be used inSCIL. The next registration gets the index LR + 1 as long as this number is less thanor equal to the HR attribute. If LR is set with #SET to a lower value, all data registra-tions above the new LR gets NOT SAMPLED status. Setting the LR attribute doesnot affect the internal object value.

Data type: Integer

Value: Less or equal to the attribute HR

Access: No limitations. Not included in FETCH, section 8.7.

MO Memory Only

This attribute determines the way of storing the attributes OV, LR, OS and RT. Theseattributes can either be stored both on disk and in RAM (primary memory) or only inRAM. All other attributes are stored both on disk and in RAM or only on disk. In theprimary memory, the data objects use the report cache memory.

Use memory only (MO = 1) for frequently executed and less critical data objects.

Data type: Integer

Value: 0 = All attributes are stored both on disk and in primary memory1 = The attributes OV, LR, OS and RT are stored only in primary

memory.

Default value: 0



ABB Automation 105


5.3 Defining Data Objects Using SCIL

General

A new data object is created by giving it a name (= the LN attribute). Other attributesget the default values mentioned in the attribute descriptions, for example:

Expression, IN = No expressionLogging function, LF = DIRECTNumber of history registrations, HR = 0Execution priority, EP = 255In use, IU = 0

When a new data object is created, all registered values get the status code 10 (OS =10).

Examples:

In the example below, a data object named "data" is created with the following attrib-utes:

Expression = %ALogging function = SUMMaximum history registrations = 2000State of use = In use

SCIL program:#CREATE DATA:D = LIST( IN = “%A", LF = 1, HR = 2000, IU = 1)

In the following example, an existing data object is copied using the FETCH function:@V = FETCH(0,”D”,”DATA1”)#SET V:VLN = “DATA2”#CREATE DATA2:D = %V

In the latter example, the new data object DATA2 will get all the registered values ofthe copied data object DATA1.


MicroSCADA6 Command Procedures

ABB Automation 107

6 Command Procedures

This chapter describes the command procedures and their attributes. The chapter isdivided into the following sections:

6.1 General: The use of command procedures, the activation and function ofcommand procedures, the use of variables in command procedures, etc.

6.2 Command procedure attributes: The attributes listed and described. Theattributes are grouped into sub-sections according to their functions.

6.3 Defining command procedures: The principles for defining commandprocedures using SCIL and an example.

6.1 General

Use

Command procedures contain SCIL programs of up to 10 000 program lines (SCILstatements) which can be started automatically or manually. They can be used for allkinds of automatic operations, for example, calculations, control operations, reportprintouts, automatic system and communication configuration, etc. Command proce-dures are, for example, used for the execution of automatic operations at system start-up. Generally, the user interface related operations can not be handled by commandprocedures, see "Program" below.

Function

A command procedure can be started in the following three ways:

• From a SCIL program (a picture program, a command procedure or a method)with the command #EXEC (see Chapter 2), for example, #EXEC PROG:C.

• From time channels (Chapter 7), giving an automatic time controlled execution.Execution through a time channel is performed in accordance with the priority ofthe command procedure For more information, see the EP attribute, Chapter 6.

• From event channels (Chapter 8), giving an automatic event controlled executionfrom a process object.

It is possible to use all the above three ways for starting the same command proce-dure. In addition, the program of the command procedure can be handled as a textvector, which can be executed completely or partly with the #DO command.

When an execution order comes from an #EXEC command, a time channel or anevent channel, the order is executed at once provided that the executing task is free,see below. If the executing task is occupied at that moment, the execution order is putin a queue. When started, the command procedure is executed completely to the endwithout interruptions (unless interrupted by an error).



1MRS751253-MEN

ABB Automation108

Program

A command procedure may contain any SCIL statements, except commands for han-dling user interface objects (picture commands, graphics commands, Visual SCILcommands). However, a command procedure program run with the #DO commandmay also contain user interface related commands, provided that the #DO command isexecuted in a user interface object (picture, dialog).

Rules for program construction can be found in the manual "MicroSCADA, Pro-gramming Language SCIL".

Variables

Besides the variables defined in the command procedure in question, the commandprocedure can use the following variables:

• If execution is started with #EXEC, the command procedure can use the variablesin the variable list of the command (see Chapter 2).

• If the command procedure is started by an event channel, it can use some auto-matically defined variables ("snapshot variables") which get both their names andvalues from certain process object attributes (see Chapter 8).

• When the command procedure is started from a time channel, the command pro-cedure can use variables defined in other command procedures started earlier bythe same time channel. These command procedures have a higher priority.

If the program of the command procedure is executed with #DO, all variables in theexecuting picture or command procedure can be used.

Executing Tasks

There are a number of tasks, at least 2 and at most 17, which execute data objects,command procedures and time channels. If a task is busy when an execution ordercomes, the order is put in a queue, and the object is executed when the task becomesfree. A task always executes an object completely before it starts to execute the nextobject. Depending on the PE attribute (see Chapter 6), execution is handled by a par-allel or non-parallel task. The executing task can be determined in accordance withChapter 5, Executing Tasks.

Storage

Command procedures are stored on disk in the report database, in the files specifiedby the HN attribute. In addition, the most frequently used command procedures can bestored in the primary memory in a memory space (report cache) which they share withother report objects (data objects, time channels, event channels). The size of thismemory space can be changed with the attribute SYS:BRC or with a tool.

To get faster execution, the dynamic data of a command procedure (the RT and OSattributes) can be stored only in primary memory. This is determined by an attribute:the MO attribute (section 6.2.6).



ABB Automation 109

Object Notation

The command procedure attributes are accessed from SCIL with the following objectnotation (see also Chapter 2):

name:[a]C[at][i]

where


’a’ Is logical application number

’at’ Is attribute name

’i’ Is an index

An object notation without an attribute refers to the program, i.e., the IN attribute.This is how the object notation is used with the #EXEC command. For example, exe-cuting the command procedure named COMPROC1:#EXEC COMPROC1:C

Indexing is only used along with the IN attribute and then the indices to the line num-bers.

6.2 Command Procedure Attributes

In this description the command procedure attributes are grouped in the followingsub-sections:

6.2.1 Basic Attributes: CM, FI, FX, IU, LN, ZT

6.2.2 Program: IN, CP

6.2.3 Time and Validation Stamps: OS, RT, TS

6.2.4 Execution Control: EP, SE, TC, PE, PQ

6.2.5 Storage: HN, MO

6.2.1 Basic Attributes

CM Comment

A freely chosen comment text. The maximum length of the text is 255 characters.

Data type: Text

Value: Text




1MRS751253-MEN

ABB Automation110

FI Free Integer


Data type: Integer

Default value: 0


FX Free Text


Data type: Text


Default value: ""


IU In Use

The attribute states whether the object is in use or not. When the object is out of use(IU = 0), it cannot be executed. However, the attributes can both be read and writtenas usual.

Data type: Integer


Default value: 0


LN Logical Name

The logical name of the command procedure. The name must follow the rules for ob-ject names given in section 2.2.

Data type: Text





ABB Automation 111


The time when the object was created or modified. This attribute is set by the mainprogram when the object is created and each time it is updated by the object definitiontool or by SCIL (the #CREATE and #MODIFY commands).

Data type: Time

Access: Read-only

6.2.2 Program

CP Compiled Program

The byte code compiled from the source program (attribute IN) of a command proce-dure object is stored as this attribute. When the IN attribute is modified alone (withoutCP attribute), the CP attribute is cleared.


Value: Byte string value containing the byte code (zero length byte stringif none exists)


IN Instruction

The program of the command procedure as a text vector.

Data type: Vector

Value: Text vector

Indexing: Program line number, 0 ... 10 000. The attribute without an indexmeans the whole program.


6.2.3 Time and Validation Stamps

OS Object Status

This attribute indicates how the last program execution succeeded.

Data type: Integer

Value: All status codes that can be produced during a program execution.Examples:



1MRS751253-MEN

ABB Automation112

0 = The program was correctly executed10 = The program execution failed

Access: Read, conditional write. It can be written with #SET.


The registration time with an accuracy of one second. Time stamping is performed bythe operating system when program execution is completed (TS = 0), or it is copiedfrom the variable %RT (TS = 1), see the TS attribute below.

Data type: Time

Value: Time

Access: Read, conditional write. It can be written with #SET.

TS Time Stamp

The TS attribute determines whether the RT attribute is updated by the operatingsystem time or from the variable %RT.

When the data object is started by an event channel, the %RT variable is the registra-tion time of the activating process object. Using the %RT variable as the registrationtime is useful when there is a time delay between the command procedure executionand the process event causing the execution.

Data type: Integer

Values: 0 = The RT attribute is set according to the operating system time when the command procedure has been executed

1 = The RT attribute is copied from the variable %RT if such a variable has been defined to the data object (see 6.1)

Default value: 0


6.2.4 Execution Control

EP Execution Priority

The priority order of the program in relation to other command procedures and dataobjects started by the same time channel. The attribute states the order in which ob-jects started by the same time channel will be executed. Objects with the same priorityorder may be executed in any order.

Data type: Integer



ABB Automation 113

Value: 0 ... 2550 is the highest and 255 the lowest priority order

Default value: 255



This attribute indicates whether the object is executed by a parallel task or not, seeChapter 5.

Data type: Integer

Value: 0 = Non-parallel execution1 = Parallel execution

Default value: 0


PQ Parallel Queue

The number of the parallel queue, if there is parallel execution (PE = 1). See Chapter5.

Data type: Integer

Value: 0 ... APLn:BPQ. PQ = 0 means that the system places the execu-tion order in the parallel queue that first becomes empty (on thecondition that PE = 1). PQ <> 0 is recommended for time criticalor time consuming objects.

Default value: 0


SE Start-up Execution

This attribute indicates whether the command procedure is executed during applica-tion start-up while reporting is catching up real time, i.e. all time channels, whichwould have started during system break, are activated.

The SE attribute concerns command procedures that are in use (IU = 1) and connectedto a time channel that is in use.

Data type: Integer

Value: 0 = The command procedure is not executed during applicationstart-up



1MRS751253-MEN

ABB Automation114

1 = the command procedure is executed during application start-upas started by the time channel

Default value: 0


TC Time Channel

The name of the time channel (Chapter 7) which starts the command procedure.

Data type: Text

Value: Maximum length 63 characters


6.2.5 Storage Attributes

HN History File Number

Command procedures, together with data objects, time channels and event channels,are stored in files named APL_REPORT.Fnn, where ’nn’ is a sequence number. Forcommand procedures and data objects the file number is specified by the HN attrib-ute. The file numbers can be freely chosen from the range 0 ... 99. Time channels andevent channels are always stored in APL_REPORT.F00. Each file can contain up to32 MB.

Data type: Integer

Value: 0 ... 399, file number

Default value: 0


MO Memory Only

This attribute determines the storage area of the attributes OS and RT. These attrib-utes can either be stored both on disk and in RAM (primary memory) or only inRAM. All other attributes are stored both on disk and in RAM or only on disk. Stor-ing the OS and RT attributes only in RAM reduces the memory access time when theOS and RT attributes are written.

In the primary memory the command procedures use the report cache.

Data type: Integer



ABB Automation 115

Value: 0 = All attributes are stored both on disk and in primary memory1 = The attributes OS and RT are stored only on primary memory

Default value: 0


6.3 Defining Command Procedures with SCIL

Attributes

The minimum to be defined when creating a new command procedure is the logicalname, the LN attribute.

Other attributes get the default values mentioned in the attribute descriptions above,for example:

Program, IN No programExecution priority, EP 255In use, IU 0

Example:

The following SCIL program example creates a command procedure called LIST forthe printout of a process object:#CREATE LIST:C = LIST(IN = VECTOR(“#LIST 2 ‘LN’:P”), IU = 1)


MicroSCADA7 Time Channels

ABB Automation 117

7 Time Channels

This chapter describes the time channels, the time channel attributes and the defini-tion of time channels. It contains the following sub-sections:

7.1 General: The use and function of time channels, the object notation andthe storage of time channels.

7.2 Attributes: The time channel attributes listed and described. Theattributes are grouped according to the their function.

7.3 The principles for defining time channels with SCIL.

7.1 General

Use

Time channels provide schedules for automatic time activated start-up of operationsin the report database: the registration of data objects and the execution of commandprocedures. One time channel can start one or more objects. If a time channel startsseveral objects, they are started in priority order. See Figure 12. Each data object orcommand procedure can be connected to only one time channel at a time.

A time channel is activated at chosen times, either at an absolute point of time or cy-clically at fixed intervals. Discontinuous time activation is handled by means of con-ditions.

Time channels are used for cyclic program execution or data registration, time de-pendent reports, trends, regular checks, time control, etc.

Function

A time channel has two functions: execution and initialisation, see Figure 12. Exe-cution of a time channel means that the objects connected to the time channel are exe-cuted, i.e. the data objects are registered and the command procedure programs areexecuted. The objects are executed according to their priority (the EP attribute). Ini-tialisation implies that data objects attached to the time channel are emptied of allregistered data, unless the logging function is COPY. For command procedures theinitialisation has no meaning.

Both initialisation and execution can occur cyclically at a fixed cycle time.

Periodic initialisation and execution are synchronised at chosen synchronisationtimes. At synchronisation time the periodic initialisation/execution is restarted, inde-pendent of the phase of the cycle in progress. This means that initialisation/executionalways takes place at the synchronisation times. If no cycle is given, initialisa-tion/execution occurs only at synchronisation times. Synchronisation can occur onceat a selected time or periodically once a year, once a month, once a week, once a dayor once an hour. See Figure 12.



1MRS751253-MEN

ABB Automation118

Discontinuous initialisation and execution are obtained by means of conditions. Theconditions, which often contain some time functions, regulate the activities, so thatinitialisation/execution is performed only when the conditions are fulfilled.

When execution and initialisation coincide, execution precedes initialisation. This isvalid whether the initialisation and execution occur in the same or in separate timechannels. If the execution of two time channels coincides, the one with the shorter cy-cle time is executed fully before the other one starts.

The objects areemptied of allregistered data.

NewRegistration

ProgramExecution

Time

#EXECEvent Channel

Time ChannelX

Initialization- Period- Synchronization- Condition

Execution- Period- Synchronisation- Condition

Data Object

Time Channel: XPriority: 1

CommandProcedure

Time Channel: XPriority: 2

Figure 12. The function of time channels. Data objects and command procedures are started in accordancewith their priority (the EP attribute).

The time channelis created

Initialization cycle

TimeExecution synchronization

Execution Execution Execution

Initialization cycleInitialization cycle

Initialization Initialization

Initialization synchronization

Initialization

Execution cycle

Execution Execution Execution Execution

Execution cycleExecution cycle

Initialization

Execution

Execution cycle Execution cycle Execution cycle Execution cycle

Figure 13. The time activation of a time channel with periodic execution and initialisation

Time channels can also be executed by event channels (Chapter 8) and by the #EXECcommand (section 2.3.). In these cases, execution occurs immediately and independ-ent of the condition. Execution in this way does not affect the subsequent function ofthe time channel.



ABB Automation 119

When an application is restarted after a break, all time channels that would have beenstarted during the break are executed. All connected data objects and certain selectedcommand procedures are executed.

Executing Tasks

There are a number of different tasks, at least 2 and at most 17, which execute dataobjects, command procedures and time channels. If a task is busy when an executionorder comes, the order is put in a queue, and the object is executed when the task be-comes free. A task always executes an object completely before it starts to execute thenext object. Depending on the PE attribute the execution is handled by a parallel ornon-parallel task. The executing task can be determined in accordance with Chapter 5.

Object Notation

The time channel attributes are accessed from SCIL with the following object nota-tion (see also Chapter 2):

name:[a]T[at][i]

where


’a’ Is logical application number


’i’ Is an index

A time channel object notation can be used without an attribute only with the com-mand #EXEC. Indices are used to distinguish initialisation and execution.

Storage

Time channels are stored in the report database on disk, in the file namedAPL_REPORT.F00. In addition, the most frequently used time channels can be storedin the primary memory, where they share the memory space with other report objects(command procedures, data objects, event channels). The memory space reserved forthis purpose is application dependent and can be set with the attribute SYS:BRC orwith a tool.

Each application can contain up to 255 time channels.

7.2 Time Channel Attributes

The time channel attributes are grouped into the following subsections:

7.2.1 Basic Attributes: LN, ZT



1MRS751253-MEN

ABB Automation120

7.2.2 Operational Status: IU

7.2.3 Initialisation and Execution: CD, CY, SU, SY

7.2.4 Parallel Execution: PE, PQ, SX

7.2.5 Time Tagging: RB, RE, RT, RS

7.2.6 Comment: CM

7.2.1 Basic Attributes

LN Logical Name

The name of the time channel.

Data type: Text

Value: Maximum length 63 characters. The name must follow the rulesfor object names given in section 2.2.



The time when the object was created or modified. This attribute is set by the mainprogram when the object is created and each time it is updated by the object definitiontool or by SCIL (the #CREATE and #MODIFY commands).

Data type: Time

Access: Read-only

7.2.2 Operational Status

IU In Use

This attribute indicates whether the time channel is activated or not. When the timechannel is not in use (IU = 0), it cannot be activated. However, the attributes can bothbe read and written as usual. Taking the time channel out of use and into use againdoes not affect the subsequent function of the time channel (neither the initialisa-tion/execution period nor the synchronisation).

Data type: Integer


Default value: 0



ABB Automation 121


7.2.3 Initialisation and Execution

CD Condition

Initialisation/execution can take place only if this condition is fulfilled. The conditionis a Boolean type SCIL expression.

Data type: Vector

Value: Vector of two text elements consisting of Boolean expressions

Indexing: Index 1 = The condition for initialisationIndex 2 = The condition for execution

Default value: No condition


CY Cycle

The time interval between periodic initialisations/executions. The cycle starts at thesynchronisation times.

Data type: Vector

Value: Vector of two integers, >=0

Unit: Seconds

Indexing: Index 1 = The initialisation cycleIndex 2 = The execution cycle


SU Synchronisation Unit

Defines how often periodic synchronisation takes place. The exact point of time ofsynchronisation is defined by the SY attribute.

Data type: Vector

Time functions included in the condition always refer to the current system time, alsowhen the time channel is activated during application start-up.



1MRS751253-MEN

ABB Automation122

Value: Vector of two integer elements, 0 ... 6:0 = No synchronisation or once at the time determined by the SY

attribute1 = Once a year at the time determined by the SY attribute2 = Once a month at the time determined by SY3 = Last day of month at the time determined by the SY attribute4 = Once a week on the weekday and time fixed by the SY

attribute5 = Once a day at the hour and minute determined by the SY

attribute6 = Once an hour at the minute determined by the SY attribute

Indexing: Index 1 = InitialisationIndex 2 = Execution

Default value: Both elements = 0


Example: The synchronisation time has been set to 1991-02-14 13:40:38. IfSU = 2 (synchronisation once a month), synchronisation occurs at13:40:38 o’clock on the 14th of every month.

SY Synchronisation Time

The time of synchronisation. At the synchronisation time, initialisation/execution oc-curs, and the periodic initialisation/execution is restarted. See the SU attribute.

Data type: Vector

Value: Vector of two time elements

Indexing: Index 1 = InitialisationIndex 2 = Execution

Default value: Present time (the time when the object is created) for executionand 1978-01-01 00:00 (zero time) for initialisation.


Example:

The time channel X is executed after an hour. If the time channel has periodic execu-tion, the period is restarted:#SET X:TSY2 = CLOCK + 3600



ABB Automation 123

7.2.4 Parallel Execution


This attribute indicates whether the object is executed by a parallel task or not, seeChapter 5.

Data type: Integer

Value: 0 = Non-parallel execution1 = Parallel execution. The object is executed by the task

determined by the PQ attribute.

Default value: 0


PQ Parallel Queue

The number of the parallel queue, if there is parallel execution (PE = 1). See Chapter5.

Data type: Integer

Value: 0 ... APLn:BPQ. PQ = 0 means that the system places the execu-tion order in the parallel queue that is emptied first (on the condi-tion that PE = 1)

Default: 0


SX Synchronised Execution

Determines if the parallel objects of the time channel are executed to the end beforethe next non-parallel object is started, see Figure 14.

Data type: Integer

Values: 0 = No1 = Yes

Default value: 0




1MRS751253-MEN

ABB Automation124

1 2 4 6

5

3

1 2 4 6

5

3

Figure 14. An illustration of the SX attribute. The numbered boxes represent dataobjects and command procedures that are activated by the same timecannel. Objects 3, 4 and 5 are parallel, the others are nonparallel. SX =1 should be chosen if object number 6 is dependent on the results fromobjects 3, 4 and 5.

7.2.5 Time Tagging

RB Registered Begin Time

RB attribute registers the real time of the last execution (or initialisation) of the timechannel. It is updated after the time channel has finished. It includes the time taken bycommand procedures and catalogues executed by the command procedures that aredirectly run by the time channel, but it excludes any executions in parallel queues.This attribute is not updated if the time channel is executed by the SCIL command#EXEC.

Data type: Vector

Value: 2 time type values

Access: Read only

RE Registered End Time

RE attribute registers the real time of the last execution (or initialisation) of the timechannel. It is updated after the time channel has finished. It includes the time taken bycommand procedures and catalogues executed by the command procedures that aredirectly run by the time channel, but it excludes any executions in parallel queues.This attribute is not updated if the time channel is executed by the SCIL command#EXEC.



ABB Automation 125

Data type: Vector

Value: 2 time type values

Access: Read only


The latest scheduled initialisation/execution time. The RT attribute is updated eachtime the time channel is initialised or executed, except when the time channel is exe-cuted by the #EXEC command or by an event channel. Though the RT attribute of atime channel is always updated when a channel is executed, the objects connected tothe time channel are not executed if the condition is not fulfilled.

Data type: Vector


Indexing: Index 1 refers to the initialisation time and index 2 to the execu-tion time

Access: Read-only

RS Registered Synchronisation

The last synchronisation time.

Data type: Vector


Indexing: Index 1 refers to the initialisation time and index 2 to the execu-tion time

Access: Read-only

7.2.6 Comment

CM Comment


Data type: Text

Value: Text




1MRS751253-MEN

ABB Automation126

7.3 Defining Time Channels with SCIL

General

When defining a new time channel, the logical name (LN) is obligatory. The rest ofthe attributes get the default values mentioned above.

Example:@V = FETCH(2,"T","TC_1")#MODIFY V:V = LIST(CD=(0,"DOW7"))#CREATE TC_2:T = %V---

A new time channel is created by copying an existing one and adding a condition forexecution.


MicroSCADA8 Event Channels

ABB Automation 127

8 Event Channels

This chapter describes event channels and their attributes, as well as how to define theevent channels. It is divided in the following four sections:

8.1 The use of event channels and their function, the variables transferred tothe event channels.

8.2 Event channel attributes in alphabetical order.

8.3 Predefined event channels. The event channels with predefined namesand functions.

8.4 Defining event channels with SCIL.

8.1 General

Use

Event channels are facilities for automatic event-activated start-up of operations in thereport database. An event channel can start the registration of data objects, the execu-tion of command procedures and the activation of time channels. Event channels areactivated using process events (changes in the process object values). In other words,event channels transmit the process events from the process database to the reportdatabase where they activate consequential operations. Event channels can also beactivated by SCIL.

The event channels are, for example, used for:

• Storing the process events in the report database.

• Event activated program execution, for example process control, calculation,printout, etc.

• Forwarding process data to other objects.

• Automatic dial-up of stations or remote workstations.

• Event-activated system configuration.

Function

An event channel can be activated in two ways (besides predefined event channelsthat are activated by special events, section 8.4):

1. From a process object defined with an event channel (the AN attribute). Certainchanges in the process objects (in the process database) activate the event channel(see below).

2. Using the SCIL command #EXEC.



1MRS751253-MEN

ABB Automation128

The activation of an event channel from a process object (predefined types) dependson the AA attribute of the process object (see Chapter 3). There are the following fourlevels of event channel activation:

• Activation when the alarm state (the AL attribute) changes, that are, at “alarm on”and “alarm off” events.

• Activation when the alarm and warning state changes (concerns analog input ob-jects). Activation depends on the AI, HI, LW, HW and SZ attributes.

• Activation each time the object value (OV) is changed, the object gets status code(OS) 1 or 3, or the SE or SP attributes are set.

• Activation each time the object value (OV) is updated (even if it does not change),or the SE or SP attributes are set.

For a process object of a user-defined type, any of the user-defined attribute can bedefined to cause an event channel activation.

Process objects of all types can be connected to an event channel. A process objectcan have one event channel or none at all (the AN attribute in Chapter 3), but severalprocess objects can activate the same event channel. An event channel, in turn, canactivate up to 11 report objects, see Figure 15. One of the activated objects is the pri-mary object that is activated first at the moment of activation. The other ten are sec-ondary objects are activated in the same order in which they are defined in the ST at-tribute.

Event channels are always executed by the event channel task, see Chapter 5.

Event Channel Activation

Process Database Report Database

Eventchannel

Process objects

...................

...................

..................

..................

...................

...................

# EXEC

Timechannels

Dataobjects

Commandprocedures

Figure 15. The activation of an event channel

Variables

When an event channel is activated, the values of the following process object attrib-utes are transmitted to equally named variables, "snapshot variables", in the objectsstarted by the event channel:

Basic attributes: LN, IX



ABB Automation 129

Object value: OV and one of the attributes BI, BO, AO,AI, DI, DO, DB, PC or BS

Alarm handling attributes: AL, AS, AF, AZ (analog input objects)

Time and validation stamps: AT, AM, RT, RM, YT, YM, OS

Event handling attributes: CA

Blocking attributes: AB, HB, PB, UB, XV

Minimum and maximum values: MM, MT, MV, XM, XT, XV

Stamps set by the stations: BL, CT, OR, RA, RB, SB

S.P.I.D.E.R. RTU specific attributes: OF, EP

The snapshot variables, for example, %AI, can be used in the expressions of the dataobjects and in the programs of the command procedures, which the event channel ac-tivate. If the event channel activates time channels, the variables can also be used inthe data objects and command procedures started by the time channels. As one eventchannel normally serves several process objects, snapshot variables should be usedinstead of the complete object notations in the activated objects. This is the only wayto guarantee that the right process object values are used.

Depending on the data object definition, the RT attribute of the data object can becopied directly from %RT (see the TS attribute, Chapter 5).

Besides the snapshot variables, a variable CHANGE is generated automatically whenan event channel is activated from a process object. The CHANGE variable tells whatkind of change in the OV attribute caused the event channel activation. The variablecan have the following four values:

"NONE" OV not changed

"VALUE" Value of OV has changed

"ZONE" Alarm zone of an AI object has changed

"ALARM" Alarm state of the object has changed

When an event channel is activated with the #EXEC command, variable values can betransferred with the variable list of the #EXEC statement.

Predefined Event Channels

Each application can contain some event channels with predefined names and acti-vating events. Examples of these are event channels activated at alarm, at applicationstart-up and various system events. These event channels are described in section 8.4.



1MRS751253-MEN

ABB Automation130

Object Notation

Event channel attributes can be accessed from SCIL with the following object nota-tion (see also Chapter 2):

name:[a]A[at]

where

’name’ Is object name



The notation can be used without attributes only with the #EXEC command.

Storage

Event channels are stored in the report database, in the APL_REPORT.F00 file,which is on disk. In addition, the most frequently used event channels can be stored inthe primary memory (report cache memory), where they share the memory space withother report objects (data objects, time channels, command procedures). The memoryspace reserved for this purpose is application dependent and set with the attributeSYS:BRC or with the Base System Configuration Tool.

8.2 Event Channel Attributes

CM Comment

A freely formed comment text.

Data type: Text

Value: Text


LN Logical Name

The name of the event channel.

Data type: Text

Value: Maximum length 63 characters. The name must follow the rulesgiven in section 2.2.




ABB Automation 131

ON Object Name

The name of the primary object activated by the event channel.

Data type: Text

Value: Object name. Maximum length 63 characters.


OT Object Type

The type of the primary object activated by the event channel.

Data type: Text

Value: "D", "C" or "T"


SN Secondary object Names

The names of the secondary objects, up to ten, that are activated by the event channel.The corresponding object types must be given with the ST attribute.

Data type: Vector

Value: A text vector of up to 10 object names

Indexing: Secondary object number. The same indexing must be used in theST attribute.


ST Secondary object Types

The types of secondary objects activated by the event channel.

Data type: Vector

Value: A text vector of the same length as SN containing the types of ob-jects:"D" Data object"C" Command procedure object"T" Time channel object

Indexing: Secondary object number. The same indexing as in the SN attrib-ute.




1MRS751253-MEN

ABB Automation132


The time when the object was created or modified. This attribute is set by the mainprogram when the object is created and each time it is updated by an object definitiontool or by SCIL (the #CREATE and #MODIFY commands).

Data type: Time

Access: Read only

8.3 Predefined Event Channels

General

Each application can contain a number of event channels that are activated by certainprocess or system events. These event channels have predefined names, but they donot exist until they are defined by the application engineer as described above.

Initiating Event Channels

Two event channels under the names APL_INIT_1 and APL_INIT_2 are activated ateach application start-up (unless the application has been the receiving part in a hotstand-by relation, see below). APL_INIT_1 is activated when the application has beenset to "HOT" (section 12.3.2) and the process database has been copied from the diskstorage to the primary memory. APL_INIT_2 is activated when the reporting hascaught real time, that is when all active time channels, which would have been startedduring the break, have been executed.

When an application, which has been the receiving part in a hot stand-by (shadowing)relation, is set to Hot, an event channel named APL_INIT_H is executed. The eventchannels mentioned above (APL_INIT_1 and APL_INIT_2) are not executed.

Event Channel Activated at Alarm

The event channel named APL_ALARM is activated for each alarm on or alarm offevent in the process database. The following six variables are passed from the processobject to the event channel:

AC Alarm class of the alarm object

AL AL attribute of the object (0 or 1)

AT Alarm Time

AM Alarm Milliseconds

LN Logical name of the object

IX Index of the object



ABB Automation 133

Monitor Events

When a login, logout or communication fault occurs in a monitor object (a monitor orapplication window) an event channel named MON_EVENT is executed. The fol-lowing variables are transferred to the event channel and can be used in the commandprocedure or data object that it starts:

%VIDEO_NR = Logical monitor number (as known to the application)

%MO = MONn:B object number of the monitor

%EVENT = The event that caused the activation:1 = Login2 = Logout3 = Monitor error (a semi-graphic workstation does not respond to

diagnostic commands, or an application window has been closed using the window manager facilities).

Unknown Process Object

When an effort is made to update a process object that does not exist, an event chan-nel called UNDEF_PROC is executed. The attributes UN and OA are transferred tothe event channel and can be used as variables, that is %UN and %OA, in the com-mand procedure or data object that the event channel starts.

System Events

Depending on a base system definition, the APLn:BEE attribute (see the System Ob-jects manual, Chapter 5), certain system events activate an event channel namedSYS_EVENT. The event causing the activation as well as the event source and eventtime are transferred to the event channel as variables. The SYS_EVENT channel isactivated by the events described in this section.

The following variables are transferred to the event channel and can be used in thecommand procedure or data object, which it starts:

%SOURCE The source of the event identified by text

%SOURCE_NR The source number

%EVENT The event that caused the activation, given as a text

%RT Event time as time data

%RM Milliseconds of the event time, integer

The following system events are generated whenever one of the printer, node or ex-ternal clock objects changes its state:

%SOURCE "PRI" = Printer"NOD" = Node"CLOCK" = External clock

%SOURCE_NR Integer:If source is "PRI": PRI object number



1MRS751253-MEN

ABB Automation134

If source is "NOD": NOD object numberOther sources: 0

%EVENT If source ="PRI": "OUTPUT LOST" = Printerconnection lost(printer queue overflow)

Source ="NOD": "LOST" = Connection to node lost"FOUND" = Connectionre-established

Source ="CLOCK": "LOST" = Clock data is invalid"FREE" = Clock has lost thesynchronising connection"FOUND" = Clock is synchronised again after a disturbance “SUMMER/WINTER TIMECHANGE WARNING” =The PC31/32 clock has issued anannouncement of coming shift of time season. When the time season change announcement bit (bit D3) of the clockhas changed to 1, the SYS_EVENT event channel is activated the next time the base system time is updated from the clock.

The following system event is generated whenever an application changes its state(APL:BAS) to enable application supervision:

%SOURCE “APL_AS”

%SOURCE_NR Application number

%EVENT “COLD”“WARM”“HOT”

The following system event is generated whenever an application changes its shad-owing phase (APL:BSP) to enable application supervision:

%SOURCE “APL_AS”


%EVENT “NONE”“TO_WARM_SEND”“WARM_SEND”“TO_HOT_SEND”“HOT_SEND”“TO_WARM_RECEIVE”“WARM_RECEIVE”“TO_HOT_RECEIVE”“HOT_RECEIVE”



ABB Automation 135

The following system event is generated to enable global memory pool supervision:

%SOURCE “GLOBAL_POOL”

%SOURCE_NR 0

%EVENT “CACHE BORROW” event is generated when the globalmemory pool manager reduces the size of picture or reportcache.“OVERFLOW” event is generated when a memory alloca-tion request fails due to insufficient global memory.

These two events are generated only once per systemstartup. However, they may be re-enabled by setting SYSattribute ME.

The system may fail to generate the "OVERFLOW" eventbecause generation of an event requires itself some globalmemory.

The following system events are generated to enable local memory pool supervision:

%SOURCE “PICO_POOLi” i = Monitor number (1 … 50)“REPR_POOLi” i = Queue number (1 … 17)“PRIN_POOLi” i = 1 (process printouts) or

i = 2 (report printouts)


%EVENT “OVERFLOW”

These events are generated only once per applicationstartup. However, they may be re-enabled by setting APLattribute ME.

The following system events are generated to supervise various queues of an applica-tion:

%SOURCE "APL_EM" APL:BEU > APL:BEM"APL_QMi" APL:BQU(i) > APL:BQM(i):

i = 1 (time channel queue)i = 2 (event queue, process + SCIL)i = 3 (parallel queues)i = 4 (delayed execution queue)

"APL_PMi" APL:BPU(i) > APL:BPM(i):i = 1 (process printouts)i = 2 (SCIL printouts)


%EVENT “EXCEEDED”

Each of these events is generated only once per applicationstartup. However, they may be re-enabled by setting APLattribute QE.



1MRS751253-MEN

ABB Automation136

Events in Stations

Certain events related to stations activate an event channel named APL_EVENT. Theevent causing the activation as well as the event source are transferred to the eventchannel as variables. The APL_EVENT channel is activated when the connection to astation is lost or re-established.

The following variables are transferred to the event channel and can be used in thecommand procedure or data object that it starts:

%SOURCE The source of the event identified by a text:"UN" = station

%SOURCE_NR IntegerIf source is "UN": Unit number (station number as

known to the application)

%EVENT The event that caused the activation given as a text as fol-lows:

If source = "UN": "SUSPENDED" = Connection to the station is lost. This event is generated when the OSattribute of the process objects of the stations set to 2.

“RUNNING” = Connection to the stationreestablished

%RT Event time as time data

%RM Milliseconds of the event time, integer

8.4 Defining Event Channels with SCIL

Example:

Creating an event channel connected to the command procedure PRINT:#CREATE EVCH:A = LIST(ON = "PRINT", OT = "C")


MicroSCADA9 Event Objects

ABB Automation 137

9 Event Objects

Use

Event objects facilitate for automatic event-activated start-up of various operations,normally updating, in user interface objects (pictures and Visual SCIL objects). Theoperations to be started are defined as program sequences in the pictures (with the#ON command, section 2.3) and as event activated methods in the Visual SCIL ob-jects.

The event objects are useful, for example, for the following purposes:

• To get an automatic and immediate update of pictures when a change occurs inthe process database. The process objects are defined with event object activation,that is the process object attribute EE is set to 1. The appropriate SCIL commandsare defined in the pictures as #ON sequences, designated to event objects with thesame name and index as the activating process object. See Figure 16 and the nextexample. This makes regular updating with update programs unnecessary.

• To execute SCIL sequences or event activated methods in user interface objectswhen an event in a process object or in another object occurs. An #EXEC com-mand in a command procedure can activate an event object to execute a SCIL(=#ON) sequence or a method in a user interface object.

Function

Event objects are activated by process events or by SCIL (see below). The activationof an event object is noted in all monitors belonging to the application. In picturesdisplayed at that moment it causes the execution of the SCIL sequences defined forthe actual event object by means of the #ON command. In dialogs and dialog items(Visual SCIL objects) displayed at the moment, it causes the execution of the eventmethods specified to be started by the event in question.

When a picture is brought to screen and an #ON command is detected in a pictureprogram, the statement or block of the command will not be executed at once. Thestatement will be stored. Always when the event object of an #ON command is acti-vated, the command will be executed provided that the picture is still on screen. SeeFigure 16. The #ON blocks are stored as long as the picture is displayed on screen orstored as fast picture. An event object activation causes no reaction if there are novalid #ON blocks for the actual event object at the event moment. Regarding fastpictures, the event object activations are noted and the #ON blocks are executed whenthe pictures are displayed on screen.

The #ON commands are only valid for the picture in which they are situated (mainpicture, window picture or picture function). Hence, although a picture can containonly one valid #ON block at a time for a certain event object, one display can containseveral different #ON blocks, which are started by the same event object. Event acti-vated methods in Visual SCIL objects obey same rules as #ON commands in pictures.



1MRS751253-MEN

ABB Automation138

Displays

ProcessDatabase

Process

#EXEC BREAKER3:E2

#ON BREAKER3:E2 #BLOCK !SHOW BREAKER3 BREAKER3:PBI2 #BLOCK_END

BREAKER3:PBI2(EE = 1)

BREAKER3:E2

Figure 16. An example that illustrates the use of event objects in pictures

Event Object Execution

As was mentioned above, an event object can be executed (generated) in two ways:

• From the process database. A change in a process object defined with eventobject activation (EE = 1, see Chapter 3) automatically activates an event objectwith the same name and index as the process object. Event object activation oc-curs when any of the following attributes is changed:

• AI, AO, BI, BO, DI, DO, DB, PC, BS, HI, HO, LI, LO, HW, LW, SS,OS, AC, RC, AR, AB, SE, SP.

• For user-defined process object types other attributes may also cause anevent object execution.

• Activation takes place independently of the cause of the change - achange of state in a station or an assignment in a SCIL program (by thecommand #SET, section 2.3). The value of the changed attribute is nottransmitted to the event object, nor any information about which attrib-ute has changed.

• From a SCIL program (in a picture or a command procedure). The event objectsare activated with the command #EXEC (section 2.3). In this case, the name of theevent object can be chosen freely. However, bear in mind that event objects areglobal, and one event object can cause different reactions in different pictures ifthe same name is used.

Storage

Event objects are not stored.



ABB Automation 139

Event Object Notation

The event objects are utilised in SCIL with the following object notation:

name:[a]E[i]

where

’name’ Is the event object name


’i’ Is an index

An event object notation does not contain any attribute. Event objects have no values,hence they cannot be parts of expressions. They can only be used with the #EXECand #ON commands.

Example

If the process object

BREAKER3:P2

is equipped with event object execution (BREAKER3:PEE2 = 1), the event object

BREAKER2:E2

is executed each time a change in the process object (for instance the attribute BI) oc-curs in the process database, see figure 16.

The process picture containing the object could contain the SCIL statement:#ON BREAKER3:E2 !SHOW BREAKER3 BREAKER3:PBI2

which implies that the process object value BREAKER3:PBI2 is shown in the win-dow BREAKER3 each time the event object is generated. It is shown provided thatthe picture is displayed for the moment and the #ON statement has been executed.


MicroSCADA10 Variable Objects

ABB Automation 141

10 Variable Objects

Use

Variable objects serve as temporary storage places for attributes (attributes gatheredfrom other objects or arbitrary attributes). They are used to form lists, for example,alarm and event lists, to browse through the object properties, to copy objects, to cre-ate and change objects, etc.

The variable objects have no attributes of their own, but they may be assigned attrib-utes belonging to other object types or arbitrary attributes. The objects as a whole, in-cluding all attributes, can be handled as variables of the data type list.

Definition

Variable objects can be created and assigned values in two ways:

• By creating the variable object with the #CREATE command and assigning it at-tribute values with the #SET or #MODIFY commands (section 2.3). The attributenames may be freely selected and composed of up to 63 characters.

• By assigning a variable the value of a list type expression: a list type function, alist type variable or a list aggregate (see the manual "The Programming LanguageSCIL", Chapter 3). At the same time a variable object with the same name isformed. The variable object gets all the attributes of the list expression.

When a variable object is created in one of these ways, the new definition automati-cally replaces a possible existing one. Variable objects can be modified with#MODIFY and deleted, even individual attributes, with #DELETE.

Function

A variable object is at the same time both an object and a variable of list type. The listas a whole is handled as a variable, for example %V, while the attributes in the list areaccessed with a variable object notation, e.g. V:VOV. When handled as a variable, itcan be copied to another variable or assigned to an object with the #CREATE and#MODIFY commands, see "Examples" below.

Like variables, the variable objects belong to the picture or command procedure inwhich they are assigned values. The same name may be used for different variableobjects, provided that they occur in different circumstances. Handled as variables, thevariable objects can be transferred to printout pictures and command procedures, seethe Programming Language SCIL manual Chapter 5.

Attributes

As mentioned above, the variable objects may be assigned arbitrary attribute names.Unlike the other object types, the variable objects can have attribute names containing

MicroSCADA10 Variable Objects


1MRS751253-MEN

ABB Automation142

up to 63 characters. All alphanumerical characters as well as underscores are allowedin the attribute names, but the first character may not be an underscore or a digit.

The variable object attributes are used in the same way as other application object at-tributes. In addition, they can be used in variable expansions (the Programming Lan-guage SCIL manual Chapter 5).

Variable Object Notation

The variable object attributes are accessed with the following object notation:

name:[a]V[at][i]

where



’at’ Is an attribute name, 1 ... 63 characters long

’i’ Is an index referring to the elements of a vector type attribute. Ifthe attribute name is longer than two characters, the index must besurrounded by parentheses. In NAME:VAA1, for example, thedigit is regarded as an index. In NAME:VAAA1 the digit is re-garded as a part of the attribute name. In NAME:VAAA(1) thedigit is an index.

A variable object notation must always contain an attribute. If the attribute is of vec-tor type, the vector elements are named by means of indices. An object notation with-out an index refers to the entire vector. All variable object attributes can be accessedwithout limitations.

Storage

The variable objects are stored like variables, see the Programming Language SCILmanual, Chapter 5.

Examples

Creating a simple alarm list:#INIT_QUERY "L"@LIST = PROD_QUERY(20)!SHOW AT LIST:VAT!SHOW AM LIST:VAM!SHOW LN LIST:VLN!SHOW OX LIST:VOX!SHOW OV LIST:VOV!SHOW AR LIST:VAR

Creating a data object by copying an existing one:@V = FETCH(0,”D”,”DATA1”)#SET V:VLN = “DATA2”#CREATE DATA2:D = %V


MicroSCADA11 Free Type Objects (F)

ABB Automation 143

11 Free Type Objects (F)

About this Chapter

This chapter describes free type objects, their attributes and how to define them. It isdivided into the following sections:

11.1 General: The use of the free type objects and an overview of theattributes.

11.2 Type Defining Attributes.

11.3 Attributes for Defining Attributes.

11.4 Defining Free Type Objects in SCIL, examples.

11.1 General

Use

Free type objects are used for defining new process object types, the user-definedprocess object types (see Chapter 3), and their user-defined attributes. Using free typeobjects the programmer can define up to 156 process object types. Each new processobject type gets the common process object attributes (see Table 2). In addition, theprogrammer can design new type specific attributes with desired features. Each user-defined object type has a type number that is used as type definition when creatingprocess objects of the type in question.

Free type objects are mainly used for designing process object types to be used by in-tegrated programs.

Attributes

Free type objects have two types of attributes:

• Elementary attributes that are related to the process object type: name, type num-ber, main attribute (object value attribute), type comment text and the total num-ber of user-defined attributes.

• Attributes that define the user-defined attributes: attribute name, data type, auto-matic activation functions, etc. Each user-defined attribute is defined by a numberof free type attributes, which give the user-defined attribute its properties. Theuser-defined attributes are identified by sequential numbers given as indices.

Object Definition

Free type objects are defined with the #CREATE command and deleted with the#DELETE command. A free type object can not be deleted until all process objects ofthe corresponding type have been deleted. Individual attributes cannot be deleted.



1MRS751253-MEN

ABB Automation144

After a free type object has been created, its attributes can be changed with#MODIFY, though with some restrictions:

• The attribute name (AN) is used to identify the attribute. Therefore the attributename itself may not be changed. A new attribute name is regarded as a new user-defined attribute.

• Due to memory reservation, the new attributes given with #MODIFY do not be-come valid for the process objects until the application is restarted.

.........1 2 3 4 5Attribute

Properties

Attribute Name (AN)Datatype (AT)Printout Activation (AP)etc.

Free type object Process Object Type

Name (LN)Type Number (PT)Object Value (OV)Comment (CX)Number of Attributes (NA)

Figure 17. The attributes of free type objects. The type number, that is the PT at-tribute, is the same as the PT attribute for the process objects. The OVattribute specifies which attribute will be regarded as the OV attribute ofthe process objects. The other attributes have nothing to do with the pro-cess object attributes.

The free type objects can also created using an object definition tool. It can be ac-cessed in the Tool Manager by double-clicking the Free Types icon in the ApplicationObjects page.

Storage

Free type objects are stored in the process database in RAM where they are read eachtime a user-defined process object is handled.

Object Notation

Free type objects are handled using the following object notation:

name:[a]F[at][i]



ABB Automation 145

where

’name’ Object name

’a’ Application number

’at’ Attribute name

’I’ Index that identifies the user-defined process object attribute of theactual type, used with attribute defining attributes only.

11.2 Type Defining Attributes

An application can contain up to 156 user-defined process object types. The free typeobjects have the following five elementary attributes for defining a user-defined proc-ess object type:

LN Logical Name

The name of the free type object (and the name of the process object type).

Data type: Text

Value: The name must follow the rules given in section 2.2

Access: Read-only, configurable. Cannot be modified with #MODIFY.

PT Process Object Type

The type number of the process object type.

Data type: Integer

Value: 100 ... 255

Access: Read-only, configurable. Cannot be modified with #MODIFY.

OV Attribute Name

The name of the attribute that represents the main attribute (the object value). Allautomatic functions connected to the OV attribute (for example alarm handling, his-tory buffering, automatic printout) will be related to this attribute. The attribute mustbe of some simple data type.

The attribute OV attribute is not obligatory. If omitted, the automatic OV attributefunctions are not performed.

Data type: Text



1MRS751253-MEN

ABB Automation146

Value: Text of two letters (attribute name), or an empty text string (if noOV attribute).


Example:#MODIFY TYPE_1:F=list(OV="BB")

CX Comment Text

A comment text related to the free type object (the user-defined process object type).

Data type: Text

Value: Text


NA Number of Attributes

The number of user-defined attributes defined for the type. This attribute is informa-tive only.

Data type: Integer

Value: Integer

Access: Read-only


The time when the object was created or modified. This attribute is set by the mainprogram when the object is created and each time it is updated by Free Type defini-tion tool or by SCIL (the #CREATE and #MODIFY commands).

Data type: Time

Data type: Time

Access: Read-only

11.3 Attributes for Defining Attributes

Each user-defined process object type can have a number of type specific user-definedattributes (up to 255). Each user-defined attribute is defined by a name, a data type,and desired activation functions. All features are defined by the F object attributes de-scribed below. The attributes are indexed with a sequential number, which identifiesthe user-defined attributes of the actual type. For example, AN (3) refers to the nameof the third attribute of the actual type (defined by the actual F object).



ABB Automation 147

AN Attribute Name

The name of the attribute. The name can be any two-letter combination not used as acommon predefined process attribute name. However, some attribute names includespecial functions:

• If the OV value of the object type is integer or real, the LW, HW, LI and HI at-tributes will have the same function as the same attributes for analogue input pro-cess objects.

• If the OV value of the object type is a Boolean value, the AG attribute will havethe same function as the AG attribute for binary process objects (predefinedtypes).

Data type: Text

Value: Text

Access: Read-only, configurable. Cannot be modified with #MODIFY,only new user-defined attributes can be appended.

AI Attribute Indexing

The maximum index of the attribute (maximum number of elements) if it is a vector.All elements in the vector must be of the same data type, which is given with the ATattribute.

Data type: Integer

Value: 0 ... 10000. 0 or 1 means that the attribute is not indexed. It is asimple data type.

Default: 0


AT Attribute Value Type

The data type of the attribute, or of the elements of an indexed attribute.

Data type: Text

Value: "INTEGER""REAL""TIME""BOOLEAN""TEXT""BIT_STRING"



1MRS751253-MEN

ABB Automation148


AL Attribute Length

The length of the attribute value or the elements of an indexed attribute.

Data type: Integer

Value: The value depends on the AT value (that is the data type of the at-tribute) in the following way:

"INTEGER": 0 = Default = the same as 4 (see below)4 = Signed 32 bit value2 = Signed 16 bit value-2 = Unsigned 16 bit value1 = Signed 8 bit value-1 = Unsigned 8 bit value

"TEXT": (+)n = Fixed size of n characters-n = Variable size, max. n characterswhere 1 <= ’n’ <= 255

"BIT_STRING": (+)n = Fixed size of n bits-n = Variable size of max. n bitswhere 1 <= ’n’ <= 65535

For REAL, TIME and BOOLEAN values the attribute is ignored.The length is fixed to 4, 4 and 1 bytes respectively.


AP Attribute Printout

The selection of printout generation at attribute changes. If printout generation is se-lected, the format picture of the process object (the PF attribute) is printed each timethe attribute changes.

Data type: Integer

Values: 0 = No printout generation1 = Printout generation

Default: 0




ABB Automation 149

AA Attribute Action

The selection of event channel activation caused by changes of the attribute value. Ifevent channel activation is selected, the event channel of the process object (the ANattribute) is activated each time the attribute is changed.

Data type: Integer

Value: 0 = No event channel activation1 = Event channel activation

Default value: 0


AH Attribute History

Selection of history buffer registration when the attribute is changed.

Data type: Integer

Value: 0 = No history buffer registration1 = History buffer registration

Default: 0


AE Attribute Event

Selection of event object generation. If event object generation is selected, an eventobject is generated each time the attribute is changed.

Data type: Integer

Value: 0 = No event object generation1 = Event object generation

Default: 0


AD Attribute on Disk

Updating of the attribute in the process database on disk when the attribute changes.

Data type: Integer

Value: 0 = No updating1 = Updating



1MRS751253-MEN

ABB Automation150

Default: 0


AS Attribute Snapshot

Defining the attribute as a predefined variable ("snapshot variable") transferred to theevent channel and format picture of the process object.

Data type: Integer

Value: 0 = No (the attribute will not be snapshot variable)1 = Yes (the attribute will be a snapshot variable)

Default: 0


AX Attribute Comment Text

A freely formed comment text relating to the attribute.

Data type: Text

Value: Text


AO Attribute Offset

An informative attribute that tells the starting memory byte number of the user-defined process object attributes stored in consecutive bytes.

Data type: Integer

Value: Integer

Access: Read-only

Example:

A process object has four user-defined attributes of the following byte length:

1 1 byte AO(1) = 0

2 2 bytes AO(2) = 1

3 4 bytes AO(3) = 3

4 ....….. AO(4) = 7



ABB Automation 151

11.4 Defining Free Type Objects

Examples

T1:FLN = = "T1"

T1:FPT = = 101

T1:FOV = = "BB"

The free type object T1 represents a user-defined process object type with type num-ber 101. The object value (main attribute) of this type is called BB.

Suppose that the BB attribute is the first user-defined attribute of the type (index 1),and that it has the following properties:

T1:FAN(1) == "BB"

T1:FAT(1) == "INTEGER"

T1:FAL(1) == 4

T1:FAP(1) == 1

This means that the BB attribute is a signed integer of 32 bits. A change in the attrib-ute generates an automatic printout.


MicroSCADA12 Using Object Definition Tools

ABB Automation 153

12 Using Object Definition Tools

This chapter describes how to access object definition tools through the Object Navi-gator and how to use the Navigator for application object management (listing, copy-ing, moving, deleting, etc.). It gives also some general principles for using the objectdefinition tools.

12.1 Object Navigator

The Object Navigator provides the following object handling functions:

• Listing objects of selected types.

• Accessing the object definition forms for viewing and editing.

• Adding new objects.

• Moving an object from one application to another.

• Copying objects within the same application or from one application to another.

• Deleting objects.

• Renaming objects.

• Application data export.

All application objects, pictures and vso files are accessible in the Object Navigator.In addition, contents of representation files can be viewed.

Entering and Exiting Object Navigator

To enter the Object Navigator, double-click the Object Navigator icon in the Applica-tion Object page of the MicroSCADA Tool Manager. To exit the Object Navigator,choose Exit from the Object menu.

Object Navigator Composition

The Object Navigator is composed of four main areas, see Figure 18. First is the menubar, where the functions are generally selected. Secondly, there is the application andobject type tree, where the handled application and object types are selected. Thirdly,there is an area for listing object names and indices. Status bar in the bottom of thepage shows information on the selected object.

If Process Objets is selected from the object tree, the view options are Objects byGroup and Objects in Table. The view option is selected from the Options menu.



1MRS751253-MEN

ABB Automation154

Figure 18. Object Navigator outlook, when process objects are viewed in groups.Status bar shows information on the selected index.

The title of the Object Navigator can be for example as follows: TUTOR[1] /510_402_1:B_MONITOR(1) - Process Object. The beginning of the title, TUTOR,identifies the name of the current application of the MicroSCADA monitor. The [1]stands for the number of monitors open to the TUTOR application. The 510_402_1illustrates the object source application name. In the end of the example title there isthe B_MONITOR part, which is the name of the process object that is displayed. If anobject shown in the application object form is from other than the current application,the application name is shown before the object name in the object form title.

The + or - sign to the left of an application name works as collapse/expand commandkey. Clicking the + sign makes the object type names visible and accessible, clickingthe - sign makes the type names disappear. This makes the list easier to view.

When selecting an object type in an application, the object names of the type in ques-tion appear in the list to the right of the object type list. If process objects were se-lected, the Navigator shows a third list box furthest to the right. This list contains theindices of the selected process object group. By default, all object names, up to onethousand names that meet the filtering criteria of the selected type, are listed.

The button with the number 1000 and a downwards arrow, , is enabled if there aremore than one thousand names. Clicking this button results in displaying the nextthousand items, or as many as there are left. In general, the buttons having the number1000 and the downward or the upward arrow is enabled if there are more objectnames in either direction.

The scroll bars allow you to browse up and down in the lists.

The Object Navigator functions for handling pictures, vso files and representationsare not included in the current version of this manual.



ABB Automation 155

Status Bar

The status bar shows information depending on the selected object. See Table 5 andTable 6 below.

Table 5. If the object is selected from object tree, status bar shows this informa-tion.

Selected object Information

Application - The type of application (LOCAL or EXTERNAL)- State of application (HOT, WARM, COLD or ERROR)- The error text, if the state is error- Computer name, if the type is EXTERNAL- Base system version, if the type is EXTERNAL

Object type - How many objects are shown in the table

Table 6. If the object is selected from object table, status bar shows this informa-tion.

Selected object Information

Process ObjectIndex

- In Use or not- Switch State- Object type- Object value- Registration time

Scale Object - Scaling algorithm (Linear 1:1, Linear or Stepwise Linear)- Modification time

Data Object - In Use or not- Value Type (REAL, INTEGER, TEXT, TIME)- Comment Text- Numbers of history registration- Registration Time

Command Proce-dure

- In Use or not- Comment Text- Connected Time Cannel- Registration Time

Time Channel - In Use or not- Comment Text- Registration Time

Event Channel - Comment Text- Primary Object- The two first Secondary Object(s)

Free Type ProcessObject

- In Use or not- Switch State- Comment Text- Output Type- Registration Time

Free Type Object - Comment Text- Process Object Type

In Figure 19, the status bar shows that the Process Object AA1FT with index 2 is Inuse, Switch State is automatic, the object type is File Transfer LAG 1.4, the value is 0and registration time was 99-11-01 14:50:32.949.



1MRS751253-MEN

ABB Automation156

Figure 19. The status bar gives information about the selected Process Object AA1FT

If an object is selected from object tree, but no attribute is selected from the table, thestatus bar shows the number of objects in view. For example, when Command Proce-dures is selected from the Object tree as shown in Figure 20.

Figure 20. Object Navigator. The status bar shows that the Command Proceduresfrom number one to number 42 are shown in the list.



ABB Automation 157

Accessible Applications

When the Object Navigator is entered, the application and object type tree shows theaccessible applications and object types available for the current application. Thesymbols for the accessible applications are:

Local application. Green symbol for HOT state and cyan symbol for WARMstate applications.

External application. Only HOT state applications, green symbol, areaccessible.

Possible application node types:

• LOCAL HOT Green symbol.

• LOCAL WARM Cyan symbol.

• LOCAL COLD Magenta symbol.

• EXTERNAL HOT Green symbol.

• EXTERNAL ERROR Grey symbol.

It is possible to handle objects in the following application types and states only:

• LOCAL HOT.

• LOCAL WARM.

• LOCAL ERROR.

• EXTERNAL HOT.



1MRS751253-MEN

ABB Automation158

Figure 21. The status bar and the application symbol show that TUTOR applicationis local and hot

External Applications

It is possible to handle objects in external applications in the same way as in local ap-plications, if the mapped applications have SYS 500 version 8.4.3 or later. With olderversions of MicroSCADA, it is only possible to paste objects to external applications.

If there are external applications mapped to the current application, the Show ExternalApplication check box is enabled as shown in Figure 22. The mapped external appli-cations are shown only when the check box is selected.



ABB Automation 159

Figure 22. External applications are shown by checking the Show External Appli-cations checkbox. Local application ELGARO and external applicationSR_TEST1 are hot.

When an object type is selected from an external application, field for the name (andpossible index) of the external object is displayed in the right side of the Object Navi-gator window. The object to be handled can be defined by inputting its name (and in-dex) directly to these fields. Below the field(s) is Recent Objects list. See Figure 23.These are objects that the Object Navigator can assume to exist in the external appli-cation, for example after a copy operation. The Recent Objects list is cleared everytime Object Navigator is re-started. When an object is selected from the Recent Ob-jects list, the name (and index) field is updated respectively. If a name is typed di-rectly to name-field, selection in the Recent Objects list is cleared. Each external ap-plication displayed has its own set of Recent Objects.



1MRS751253-MEN

ABB Automation160

Figure 23. Object Navigator showing the Recent Objects list for the SR_TEST2mapped external application

Representation Options for Process Objects

Process Objects has two representation possibilities: the list format that includesLogical Name (LN) and Index (IX) and the table format. List format is the traditionaloption. To view the list format, choose Options > View Process Objects by Groups.To view the table format, choose Options > View Process Objects in Table. SeeFigure 24.

Figure 24. The Options menu shows that the representation format at the moment isTable

For table format, the default attributes are LN, IX, UN (Unit Number), OA (ObjectAddress), OB (Object Bit Address), OI (Object Identifier) and OX (Object Text). Thevalues of OA and OB are encoded depending on object type, but in the list, they aredisplayed in decimal format. For this reason, they are shown between brackets([OA]).



ABB Automation 161

If some column header is double-clicked in the table, the table becomes sorted by thevalues of that column.

It is also possible to show one additional attribute in the table. The attribute can beselected from the User-defined drop-down list. See Figure 25. The list includes all theattributes that are not shown as default in the table. The empty line (the last item inthe drop-down list) removes the user-defined attribute from the table.

Figure 25. An additional attribute can be selected from the User-defined drop-downlist, if the attributes are shown in table format.

Page Length

It is possible to change the page length for the table view by selecting Process ObjectTable Page Length from the Options menu. The Table Page Length dialog opens andthe number of objects can be selected. See Figure 26.

Figure 26. Page length can be defined for process object attributes, if table formatis selected.

Refresh Functionality

This functionality is needed for updating the view of dynamic attributes, when theobjects are presented in list format. Refresh function can be carried out by selectingView > Refresh from the menu bar or pressing the F5 key on keyboard.

Filtering

To restrict the listed object names, enter a Filter. As the filter, you can use an asteriskto denote one or more characters at the end of the name. For example POT* lists ob-jects beginning with a string "POT" and "*" lists all objects, *P is not a valid filter.All object names that match the filter are listed in the object name list. A single aster-isk in the filter box means that all objects are listed.



1MRS751253-MEN

ABB Automation162

Filtering Process Objects

When viewing the Process Objects, an empty filter is used by default. The filters arestored into a parameter file when the Object Navigator is closed, and restored whenthe tool is opened next time. The last 20 filters can be selected from the drop-downlist. A filter can be activated by selecting it from the list. In Figure 27 the ProcessObjects are viewed in a table form.

Figure 27. Process Objects are viewed in a table form. In this picture there is nofilter activated.

Defining a Filter

A new filter can be defined, if View > Set Filter ... is selected from the menu bar. Thiscommand opens a filter dialog. See Figure 28.

Figure 28. Filter dialog for defining and editing filters. There are two conditionsspecified in this dialog: LN == A_* AND IX >= 10. The quotation marksare automatically added, if the attribute type is text.

Only the value should be typed into a value field. If a quotation mark is needed, it isautomatically added to the filter.

If there is no filter selected in Object Navigator when the filter dialog is opened, onlythe first drop-down list is enabled. It is possible to choose any attribute from the At-tribute drop-down list. After the attribute is selected, the next drop-down list becomes



ABB Automation 163

enabled. From this list, it is possible to choose the comparison signs < (smaller than),<= (smaller than or equal to), == (equal to), >= (bigger than or equal to), > (biggerthan) or <> (unequal). In the text box, it is possible to type any text. AND or OR hasto be chosen from the last drop-down list, to be able to enter the next filter condition.

After filling the dialog, the new filter is appended to the drop-down list in the ObjectNavigator, when OK or Apply is clicked, if no SCIL errors were found. If the numberof items reaches 20, the last item in the drop-down list is erased.

A validation check is done, when OK or Apply is clicked, or if OR or AND functionis chosen. The following message is shown, if in the first filter condition, for exampletext is entered as an attribute value that should be integer.

Figure 29. Filter Status info dialog tells that the given attribute value is invalid

OK button updates the contents of process object list in Object Navigator and closesthe Filter dialog. Apply button refreshes the contents of process object list in ObjectNavigator, according to defined filter. Clear button clears all fields and combo boxesand Cancel button closes the dialog without any changes to the Object Navigator.

It is also possible to type the filter condition directly in the Filter field. Another checkis performed when OK or Apply is clicked. If there is any SCIL error in the filterfield, an error message is shown.

Figure 30. This error message is caused by a missing attribute name in the filterfield

Editing a filter

If a filter is selected from the drop-down list when the filter dialog is opened, it can beedited in the dialog. The selected filter is shown in the Filter field. It is also possibleto edit the filter directly in that field.



1MRS751253-MEN

ABB Automation164

Editing Attribute Values of Process Objects

In the Edit dialog, it is possible to change the attribute value(s) of one or several Proc-ess Objects at a time.

1 From the menu bar, choose Options > View Process Objects in Table.

2 From the table, select the attribute (or attributes) that you want to change.

3 Click right mouse button on the table and select Edit from the pop-up menu.

Figure 31. Several attributes have been selected from the table and right mouse button has been clicked. Toedit the attributes, select Edit from the pop-up menu.

The Edit dialog opens and it contains the values of the object that was first selectedfrom the table.

Figure 32. Edit dialog contains the values of the attribute that was selected first. Ifseveral attributes are selected from the table, the fields for UN, OA andOB attribute values are disabled.

The text fields for UN, OA and OB are disabled, if more than one object is selectedfrom the object table. These fields are also disabled if the attributes of the selectedobject type are not editable.



ABB Automation 165

The last text field gets the value of the user-defined attribute, if it exists in the table.The IU check box becomes unavailable, if the IU (In Use) attributes of the selectedobjects are unequal.

The OK and Apply buttons become enabled after something has been modified.Clicking Apply will update the selected object(s) both in the database and in the table.Clicking OK will do the same as Apply and close the edit dialog as well.

Error messages are displayed, if something goes wrong during the save operation.

Viewing or Editing Objects

To view or edit the definition of an existing object:

1 Click the object type name below the name of the application where the object isstored.

All objects of the selected type appear in the list box to the right. In the case of Proc-ess Objects of predefined type, the list shows the names of the process object groups.The object names are listed in alphabetical order.

2 Double-click the name of the object and possibly the index (if the object is aprocess object of a predefined type), or click and choose Properties from theObject menu.

The object definition tool of the selected object appears and you can edit it. Refer tothe following chapters to learn how to use the object definition tools. See also Chapter11 where some common functions are described.

12.2 Creating and Editing Objects

Creating New Application Objects

To create and define a new object:

1 Click the object type in the application where the object will be stored.

2 Choose New from the Object menu, or use the shortcut key Ctrl+N.

3 Type the name in the dialog that appears.

The object (object group for process objects) is created with the given name and thename appears in the object list. The name is the LN attribute of the object.

The following step 4 is required only for process object groups.

4 If you are creating a new process object, index and object type is requested:

1. Select the process object group where the index is created to.

2. Choose Object/New and input an index that doesn’t exist under the selectedgroup.

3. Define the process object type and the station type in the dialog that appears.See Figure 33. It is possible to change the focus between the two list boxes,



1MRS751253-MEN

ABB Automation166

possible check boxes and the command buttons with the Tabulator key. ForAnalog Input and Analog Output object types, there is a possibility to choosethe object representation to be real or 32-bit integer. Default data type is realand the 32-bit integer representation can be chosen by selecting a check boxshown in Figure 34. Also when creating Analog Input and Binary Input DNP,RTU 200 and RTU 200 (EDU) base objects, an option for automatic creation ofsecondary object is given, see Figure 34. The automatic creation of thesecondary object is done during the creation of the base object.

The given index will be the IX attribute of the object and the selected object type willbe the PT attribute. The 32-bit integer representation for the Analog Input and Outputtypes will be the IR attribute.

The object has been created with the default values given in Chapters 3 ... 11. Forsome object types, obligatory attributes are assigned values.

Figure 33. The dialog, box where you can choose the object type (PT attribute) of anew process object. Here a binary object will be created.



ABB Automation 167

Figure 34. For the Analog Input and Output object types, there is a check box forselecting a 32-bit integer representation. Also for the Analog and BinaryInput DNP, RTU 200 and RTU 200 (EDU) objects there is check box forautomatic creation of secondary object.

Creating New Data Objects

To create a new Data Object:

1 From the menu bar, choose Object > New.

2 Give name for the new data object and click OK.

3 Give the VT and VL values (VL only if VT is TEXT) in the dialog that opens. SeeFigure 35.

Figure 35. The selected value type is real. In this case, it is not possible to give theVL attribute value.

4 Click OK.

Event Recording Objects

Event recording objects are process objects created for RTU 200 and RTU 200 (EDU)objects. Their index (IX) should be the index of the supervised object plus 100. Theevent recording object can be of type BI, AI or DB.

When a new RTU-200 event recording object is created, it gets the Block Address,OB, UN and OI of the supervised object. If the supervised object does not exist, the



1MRS751253-MEN

ABB Automation168

OA, OB, UN and OI get default values given by the base system. For this reason thesupervised object should be created first.

Defining an Application Object

To define the application object:

1 Enter the Object Navigator.

2 Select an object type from the application and object tree.

3 Double-click the object name in the list.

4 The object definition tool for the selected object type appears. The attributes havethe default values. Define the application object. See the following sections andchapters for more information on how to use the tools.

Defining a Process Object Group

To define the process object group:

1 Enter the Object Navigator.

2 Select the Process Objects group type from the application and object tree.

3 Double-click a process object group name in the list.

4 The definition tool for the selected object group appears. The tool is shown inFigure 36. Enter the definitions in it. The name of the logical format picture canalso be browsed.

Figure 36. The definition tool for process object group

For process object groups the group indices have to be defined separately by double-clicking on the index that is to be defined.

Renaming Application Objects

To change the name of an object:

1 In the left list box, click the application object type you want to rename.

2 Click the name of the object in the second list box. In the case of process objects,click the process object groups and then the index.



ABB Automation 169

3 Choose Rename from the Object menu.

4 Type the name of the object in the white text box of the dialog that appears. ClickOK.

Copying Application Objects

To quicken application engineering, application objects and their definitions can becopied to create several objects with same configurations. A maximum of 10 000 ob-jects may be copied per one copy operation, and the same concerns the paste opera-tion as well. Note that the cut operation allows a maximum of 50 objects to be cut atone time. To copy application objects from one application to another:

1 Click the object type under the name of the application from which you wish tocopy objects.

2 Select an object for copying by clicking the name of the object. Several objects canbe selected by holding the Ctrl key down while you click the objects or pressingthe mouse button down and dragging the pointer over the objects.

3 Choose Copy from the Edit menu.

4 Click the object type below the application to which you wish to copy the objects.

5 Choose Paste from the Edit menu.

When a Process Object that has reference to a Scale Object, is copied from one appli-cation and pasted to another, the referenced Scale Object is automatically copied andpasted at the same time. If the Scale Object did not exist before the paste operation inthe application where it was pasted to, it will be created there. Figure 37 shows an ex-ample of the informative dialog box that appears when referenced Scale Objects arecreated into an application while pasting.

Figure 37. The Paste dialog informs that two Scale Objects were created in the ap-plication

The copying of objects from a local application to an external application is done inthe same way as copying between two local applications. Objects that are successfullypasted to an external application are displayed in the Recent Objects list for the objecttype under the application. Objects in an external application can not be copied.

To copy application objects within an application:

1 Click the object type under the name of the application where you want to copyobjects.



1MRS751253-MEN

ABB Automation170

2 Select an object for copying by clicking the name of the object. Several objects canbe selected by holding the Ctrl key down while you click the objects or pressingthe mouse button down and dragging the pointer over the objects.

3 Choose Copy from the Edit menu.


In both cases, the user is reminded of a duplication of object names with the followingdialog. The dialog contains four buttons:

Retry Retries to paste, use if fields have been edited.

Overwrite Overwrites existing object.

Skip Continues to paste but skips the currently overlapping ob-ject.

Stop Stops pasting, pasted objects are not cancelled.

Figure 38. Duplicate Object names are not allowed

Copying Process Objects Index

To copy the definition of a process object and to paste the definition to another objectindex:

1 Select application.

2 Select process object group.

3 Select an index or several indices.

4 Click Copy on the Edit menu.

5 Select target application.

6 Select target in one of the following manners:

Case 1 Select a process object group whereas the indexes arepasted under that group

Case 2 No group is selected, the indices are pasted under theobject group name stored at copy

Case 3 If several object groups are selected, indices are pastedunder the first group in the selection.

7 Click Paste on the Edit menu.



ABB Automation 171

If Address Overlap error occurs when pasting the process object index, the dialog inFigure 39 is shown.

Figure 39. Address Overlap dialog

The user may fill in a new unit number, a new object address or check the "RemoveOverlapping Addresses…" check box. If the check box is selected, all the overlappingaddresses of objects that remain to be pasted are cleared after a retry. The addressesthat were cleared during pasting are shown in a dialog alongside the correspondingindexes, see Figure 40. Changing the unit number is useful when copying a wholeprocess object group to another station where the object addresses should be the same.

Figure 40. Dialog presenting the addresses that were cleared during operation,alongside the corresponding indexes.

Attempt to overwrite a process object index with an index of a different processtype (PT) is not allowed. The message “Object can’t be overwritten, PT’s don’tmatch” is shown.



1MRS751253-MEN

ABB Automation172

Moving Objects

To move an application object:

1 Choose the application from where to move, the object type and the object. Youcan also move several objects by selecting them at the same time with the help ofthe Ctrl key.

2 Choose Cut from the Edit menu.

3 Choose another application where you want to insert the object or the objects.


Deleting Application Objects

A maximum of 10000 objects can be deleted at a time.

To delete an application object:

1 Choose the application from which you want to delete objects.

2 Choose the object type and the objects to be deleted. Several objects can be se-lected by holding the Ctrl key down while you click the objects or pressing themouse button down and dragging the pointer over the objects. In the case of a pro-cess object, choose the object group and then the indexes to be deleted. Note, thatif only a process object group and no indexes is selected, the whole group and allindexes under it will be deleted. External application objects can be selected fromthe Recent Objects list.

3 Choose Delete from the Edit menu. The delete prompt appears.

4 Click OK to delete or Cancel to cancel the deletion.

Process object groups in external applications can not be deleted. If copied applica-tion objects are going to be deleted the dialog box shown in Figure 41 appears. In thedialog box, the user has to confirm whether the delete operation is continued or not. Inthis case continuing the operation will cause the copied application object to disap-pear also from the Clipboard.

It is possible to cut a maximum of 50 objects at one time.

If only a process object group and no indices is selected, the whole group and ALLINDICES under it will be deleted.

You cannot undo delete operation!



ABB Automation 173

Figure 41. The dialog box, that appears when a copied application object is beingdeleted.

Application Data Export

To enter the Data Export Tool:

1 Click Export... on the Data menu.

2 The Data Export Tool dialog opens. For further instructions, see the SYS 500System Management manual.

File Transfer

File transfer is implemented via process database. It is possible to create File TransferLAG 1.4 Process Objects in the same way as other Process Objects.

Figure 42. File transfer objects are created in the same way as other Process Ob-jects

It is not possible to set the address for File Transfer LAG 1.4, only the station UN canbe modified. There is an own page for File Transfer objects under the Dynamic tab.See Figure 43.

The following functions are supported in current release:

• Receiving (uploading) a file from a station.

• Sending (downloading) a file to a station.



1MRS751253-MEN

ABB Automation174

• Browsing the file hierarchy of a station.

• Reading file attributes from a station.

• Deleting a file or directory in a station.

Figure 43. There is an own page for File Transfer objects under the Dynamic tab

The process objects of this type have all the same common attributes as other processobjects. Especially, the post-processing attributes, such as EE, AE etc., may be usedto report the completion of the transfer to the application.

The address attributes OA and OB have no meaning in conjunction with FT objects.OA should be set to zero (if set at all).

There may be any number of FT objects connected to one station, e.g. each config-ured to a specific download / upload.

12.3 General Principles for Using Object Definition Tools

Definition Tool Title

The title of an object definition tool shows the name of the object and the object type.It also shows the name and number of the application where from the tool is started.In the case of process objects, the object name is followed by the index.



ABB Automation 175

Pages

Most of the object definition tools are composed of pages, which can be accessed byclicking the tabs. In some cases, the tool contains so many pages that not all of themcan be shown on screen at the same time. In these cases, you make the tabs visible bymoving to the left and right with the arrow keys.

Figure 44 shows an example of an object definition tool, the data object definitiontool. It has five visible tabs. The black right arrow indicates that the whole row of tabsis not shown. In this case, the rightmost tab, All attributes, is not completely visible.

User Interaction

The user interface of the object definition tools follows Windows standard interface.To those who are not familiar with this standard a few explanations are given.

Data that you cannot change for the object in question, for example because of someprevious selections, is made unavailable. In Figure 44, the Source and Pulse Scaletexts are disabled, which indicates that these features cannot be changed.

Text boxes that provide a drop-down list of options are equipped with a down arrow.You make a choice by clicking the arrow and then selecting an option in the list (or bypressing the mouse button on the arrow and keeping it down while dragging thepointer to the option where you release the button). In Figure 44, the Logging functionhas a drop-down list of options. A button with three dots opens a dialog where youcan make a choice by clicking in a selection box. In Figure 44 the button is besidesthe Source text box.

Check boxes are used when an attribute or feature can be either active or inactive. Across in the box means that the attribute or feature is selected. You change the selec-tion by clicking the check box.

In the tool descriptions in the next chapters, the attributes are described in brief. Toget a detailed description of the attributes, refer to the corresponding descriptions inChapters 3 ... 11.

Storing the Object and Exiting the Tool

When object definition is complete, you can choose to save the object and exit thetool, cancel the definitions and exit the tool, or save the definition without exiting thetool. These options are at the bottom of the dialog:

OK Saves the object definition (updates the object if it was changed)and closes the tool.

Cancel Cancels the definition and closes the tool.

Apply Saves the definition but does not close the tool.



1MRS751253-MEN

ABB Automation176

Figure 44. An example page of a definition tool


MicroSCADA13 Process Object Definition Tool

ABB Automation 177

13 Process Object Definition Tool

About this Chapter

This chapter describes the definition tool for defining process objects of predefinedtypes. It is divided into five sections as follows:

13.1 Overview: a summary of the definition tool.

13.2 Common Area: the attributes and options in the common area of the tool.

13.3 Configurable Attributes: the Configurable page and its sub-pages.

13.4 Dynamic Attributes: the Dynamic page and its sub-pages.

13.5 All Attributes: the All attributes page.

To get a detailed description of the attributes mentioned in this chapter, refer toChapter 3 of this manual.

13.1 Overview

General

The tool for defining process objects of predefined types is accessed from the ObjectNavigator by double-clicking a process object. Process objects are created in the Ob-ject Navigator. The procedure is described in the Chapter 12. The Process ObjectDefinition Tool can also be accessed from the Event Channel Definition Tool.

The Process Object Definition Tool contains a common area and three main tabs:

• Configurable. Below this tab there are a number of sub-tabs each of which repre-sent a page with configurable attributes.

• Dynamic. This tab presents several pages that show the values of the dynamic at-tributes at the moment the tool is opened. The content of the tool can also be up-dated.

• All attributes. This page lists all attributes in alphabetical order.

The page All attributes has no sub-page. It is the same page no matter which processobject type was chosen. The other two pages, Dynamic Attributes and ConfigurableAttributes, have sub-pages, which vary depending on the process object type. Thenames of the sub-pages, as well as their contents, differ.



1MRS751253-MEN

ABB Automation178

13.2 Common Area

General

The common area above and below the pages, see Figure 45, contains basic defini-tions that are common to all object types.

Figure 45. The Process Object Definition Tool. This picture shows the part of thetool that is common for all process objects. It also shows notebookpages, which differ according to the process object type.

Identification

This section of the tool specifies the identification attributes of the objects, seeChapter 3. The GC attribute is common to all objects of the same group.

Operation State

Take the object into use and out of use with the In Use check box. The selection isapplied to the process object when OK or Apply is clicked. The selection specifies theIU attribute. The Switch State is the SS attribute. See Chapter 3.



ABB Automation 179

Process Object Type

Here you select the type of station, which reads or controls the object, and the objecttype as it is defined in the station. This is not an attribute.

Other Information

The Modification Time text box below the pages shows the time when the object waslast modified, no matter was it modified in the tool or with SCIL commands(CREATE, MODIFY).

The Next and Previous Process Object Index (IX) and Group (LN) command buttonsbelow the pages make it easier to move from one Process Object Index or Group toanother. When any of the four command buttons is active it means that there is one ormore object(s) or index(es) in the respective direction of the button.

Values shown in the tool are the values at the moment the tool was opened. If youwant to update the values of the tool, click the Fetch button.

13.3 Configurable Attributes

Overview

The configurable attributes are grouped into the following sub-pages, which may beshown or hidden depending on the object type:

• Addresses.

• Unit and Scale (analog objects and pulse counters).

• Limit values (analog objects).

• Alarm Generation (binary input objects and double binary indications).

• Alarm Handling (AI, BI and DB type objects).

• Events.

• History.

• Printouts.

• Miscellaneous.

If the object is not in use, changes to some dynamic attributes will not be updated.



1MRS751253-MEN

ABB Automation180

Addresses

In the Addresses page (see Figure 46) you define the addressing attributes.

Figure 46. Example of the attributes that are defined in the Address page

Station Unit Number, UN Click the buttons with three dots and select a stationnumber in the list that appears, or type the stationnumber directly into the field.

Addressing Type the object address (the OA attribute) and the bitaddress (OB attribute). With some station types (forexample RTU) the addresses are encoded. This meansthat the addresses shown on the page are not directlyOA or OB -values, but they are encoded from thesewith some encoding method. Similarly when encodingis typed, it is converted to OA or OB using the samemethod. If address encoding is needed, the appearanceof the page changes. Instead of OA and OB, the nameof the encoded value is shown to the left of the textbox, which displays the encoded value.

Output Type, OT Select output type by choosing an option from thedrop-down list box. The item is available when thereis no address encoding.

For process object types SPA and RTU200, the block address value “” is interpretedas 0 (zero). The Object Bit Address (OB) is set to value 16 whenever the block ad-dress is 0 (zero).

Limit Values

The Limit Values page (see Figure 47) is present when defining an analog object. Thepages for analog input and analog output objects are different. In the following list arethe attributes that are defined on the pages.

Limit Values The alarm and warning limits of analog objects. TheHI, HW, HO, LW, LO and LI attributes.

SCADA Zone Supervision Choose one of the options in the drop-down list: Mi-croSCADA or station. If “station” is chosen, the



ABB Automation 181

alarm and warning state is supervised by the stationand the alarm and warning limits have no meaning.(See the SZ attribute in Chapter 3).

Zero Deadband Superv. Enable zero deadband by selecting the check box (theZE attribute). If zero deadband is enabled, enter thesize of the deadband in the text box (the ZD attribute).

Figure 47. The Limit Values page for a process object of type analog input

Alarm Generation

Figure 48. The Alarm Generation page of a binary input objet

For binary input objects and double binary indications, there is an Alarm Generationpage (see Figure 48) which contains the following attributes:

Alarm Generation, AG The alarm generating value(s) of a binary input ob-ject.

Alarm Activation, LA The alarm generating value(s) of double binary indi-cations.

Normal Value, NV The normal value of a binary input object or doubleindication.

These attributes are all described in Chapter 3.



1MRS751253-MEN

ABB Automation182

Figure 49. Alarm Generation drop-down list includes four options

Alarm Handling

The Alarm Handling page (see Figure 50) is shown for all objects types. You can de-fine the following alarm handling functions:

Alarm Class, AC Choose the alarm class group you want to use bychoosing a class in the drop-down list box.

Alarm Blocking, AB Click the check box to block and unblock the alarmfunction. The alarm function is blocked when a crossis shown in the box.

Alarm Delay, AD Define the delay between alarm registration in thedatabase and the alarm generation. You can enter avalue or browse up and down by clicking the arrows.

Alarm Monitors, PD Choose the monitors where you want to show thealarm messages and pictures by checking the corre-sponding check boxes. The monitor numbers are thelogical monitor numbers chosen when opening themonitors (application session).

Picture, PI Enter an alarm picture name either by typing it in thebox or by choosing it in the picture list dialog pro-duced by clicking the button with three small dots.

Receipt Required, RC Click the check box to insert and remove demand foralarm acknowledgement.



ABB Automation 183

Figure 50. The Alarm Handling page

Unit and Scale

The Unit and Scale page is shown only for analog objects and pulse counters. A ScaleName (SN) is obligatory for all analog objects. The page for analog objects containsalso the ST attribute and Show button, which opens the Scale Object Definition Tool.The attributes BC, ST and SC are also defined for pulse counter in the Unit and Scalepage.

Events

In the Events page (see Figure 51) you define the following:

Event Channel To connect the process object to an event channel,select the check box Action Enabled (the AE attrib-ute) and enter the name of the event channel in theAction Name (AN) text box. You can choose an eventchannel from the event channel list obtained byclicking the button with three dots. You access thedefinition tool of the event channel by clicking theShow... button to the right. Choose activation criteriain the Action Activation (AA) drop-down list, and byselecting the check boxes Action at First Update (AF)and Action on History Values (AH).

Event Object Enabled, EE A check in the check box means that an event objectwith the same name as the process object will be gen-erated at each change in the process object.



1MRS751253-MEN

ABB Automation184

Figure 51. The Events page

History

In the History page (see Figure 52) you define the History buffering attributes:

History Enabled, HE Select the check box if you wish to include the proc-ess object in the history buffer (in the event list).

History Activation, HA Choose the activation criteria for history registrationby clicking an option in the drop-down list.

History at First Update, HF Select the check box if you wish history registrationat first update of the process object.

History on History, HH Select the check box if you wish history registrationof updates marked as HISTORY.

History Log Printers, HL Select a logical printer number for registration inevent log on disk. If event logging on disk will beused, a PRI object must defined in the base system forprinter logging, see the System Configuration manual.

Figure 52. The History Page



ABB Automation 185

Printouts

In the Printouts page (see Figure 53) you can define the following printing functions:

Printout Activation, PA Choose activation criteria by clicking and option inthe drop-down list.

Printout at First Upd., PU Select the check box if you wish printout at the firstupdate.

Printout on History, PH Select the check box if you wish printout at updatesmarked as HISTORY.

Format Picture, PF The name of the printed picture. Enter a picture nameor choose one from the drop-down list.

Printers, LD Select the printers that will be used for automaticprintout. The printer numbers are logical numbers.The printer number 15 is greyed out because it cannotbe selected. It is used by microlibrary.

Figure 53. The Printouts page

Miscellaneous

In the Miscellaneous page you can define the use of operational counters and someattributes used in SCIL. The Miscellaneous attributes are detailed in Chapter 3 of thismanual.



1MRS751253-MEN

ABB Automation186

Figure 54. The Miscellaneous page for Pulse Counters

13.4 Dynamic Attributes

Object State

The Object State page (see Figure 55) shows the following object information:

Object Value The present object value (OV), the time stamps (RTand RM), and the validation stamp (OS). The upperrow shows the values stored in RAM. The lower rowshows the object value stored on disk. This value canbe edited.

Communication These attribute shows markings set in the stations orin NET.

The attributes are detailed in section 3.3 of this manual.

Figure 55. The Object State page



ABB Automation 187

File Transfer

The file transfer page is visible only for the file transfer objects. The following attrib-utes are shown:

File Transfer, FT Displays the state of transfer.

File Function, FF Displays the function to be performed on the file.

File transfer Progress, FP Displays the number of bytes transferred between NETand the station during current transfer or last transfer.

Identification, ID The file’s identification in the station.

File Name, FN The tag of the disk file to be sent or received.

Status, ST A SCIL status code giving more information when thetransfer is aborted.

Directory Contents, DC Gives information about the contents of the file or di-rectory in the form of type, ID, name, creation time,length and auxiliary elements.

Figure 56. The File Transfer page

Value History

The value history attributes are analog input (AI) specific.

Minimum Value, MV The lowest value of the AI attribute sincethe last reset.

Maximum Value, XV The highest value of the AI attribute sincelast reset.

Minimum Time, MT The time in seconds when the minimumvalue (the MV attribute) occurred.

Minimum time Milliseconds, MM The milliseconds of the time when theminimum value, MV, occurred.



1MRS751253-MEN

ABB Automation188

Maximum Time, XT The time in seconds when the maximumvalue (the XV attribute) occurred.

Maximum time Milliseconds, XM The milliseconds of the time when themaximum value (the XV attribute) oc-curred.

Figure 57. The Value History Page

Alarm

The Alarm page (see Figure 58) shows the present alarm state of the object. The fol-lowing attributes are shown:

Alarm, AL The alarm ON/OFF state.

Alarm State, AS A value that indicate the alarm state andthe state of acknowledgement.

Alarm Receipt, AR Acknowledged or not acknowledged. Yesmay also mean that the object has no de-mand for acknowledgement.

Alarm Activated at, YT, YM The time when the latest alarm was acti-vated.

Alarm Activated/Deactivated at The time when an active alarm was acti-vated (turned ON) or when the latestalarm was deactivated (turned OFF) if it isno longer active.

Alarm Zone, AZ The attribute is defined for Analog Outputobjects.



ABB Automation 189

Figure 58. The Alarm page

Blocking

In the Blocking page (see Figure 59) you can temporarily block printout, history buff-ering, event activation and updating. Block the functions by selecting the corre-sponding check boxes.

Figure 59. The Blocking page

Counters

The Counters page (see Figure 60) shows the values of the operational counters.

Figure 60. The Counters page



1MRS751253-MEN

ABB Automation190

13.5 All Attributes

The All Attributes page (see Figure 61) lists all process object attributes. The attributevalues shown in a white text box can be edited. The attribute values shown on a graybackground cannot be edited. When the attribute name is dimmed, the attribute is notvalid for the process object type in question.

Figure 61. The All Attributes page


MicroSCADA14 Scale Object Definition Tool

ABB Automation 191

14 Scale Object Definition Tool

About this Chapter

This chapter presents the definition tool for defining scales and provides a point-by-point description of the data and text boxes in the tool.

General

The definition tool for defining scales is accessed from the Object Navigator by dou-ble-clicking a scale object. A new object is created in the Object Navigator. The pro-cedure is described in the Chapter 12. The tool is also obtained from the Process Ob-ject Definition Tool by selecting to view the scale of a process object.

The definition tool contains a common area and one or two pages. The alternativepages are All Attributes, Linear Scaling and Stepwise Linear Scaling. The Scaling Al-gorithm determines which pages are shown. See Figure 62. The page All Attributescontains all attributes in alphabetical order. Here you can check and edit the attrib-utes.

Figure 62. The tool for defining scales. Here the scaling algorithm is one-to-onescaling.

Common Area

The common area above and below the pages, contain the following definitions andinformation:

Scaling, SA Here you select the scaling algorithm of the scale: one-to-one, linear or stepwise linear scaling. Click the desired algo-rithm in the list of options. You must make this selection be-fore you can continue the definition, because it determineswhich pages will be shown in the tool. Linear and stepwise



1MRS751253-MEN

ABB Automation192

linear scaling requires further definitions in the Linear andStepwise linear pages respectively. One-to-one scaling re-quires no further definitions. For process objects withoutprocess connection, always use one-to-one scaling. Defaultvalue is one-to-one scaling.

Last Modified Below the pages is the point of time when the scale was cre-ated or last modified.

Linear Scaling

Figure 63 shows the Linear Scaling page of the Scale definition tool.

Figure 63. The Linear Scaling page

To define a linear scale, enter scaling constants as follows:

Low Process Enter a low value used in the stations.

Low Database Enter the corresponding value used in the MicroSCADAprocess database.

High Process Enter a higher value used in the stations.

High Database Enter the corresponding value used in the MicroSCADAprocess database.

The low value does not need to be the lowest possible value and the high value doesnot need to be the highest possible value.

These boxes define the SC attribute when the scaling algorithm is linear.



ABB Automation 193

Stepwise Linear Scaling

Figure 64 shows the page for defining stepwise linear scaling.

Figure 64. The Stepwise linear page of the scale definition tool

The page shows 50 pairs of text boxes, each of which corresponding to a coordinateon the scaling algorithm curve, Chapter 4. The text boxes to the left show the valuesin the stations (the process) and the text boxes to the right show the values in the Mi-croSCADA process database. You can browse upward and downward in the list usingthe scroll bar to the right.

Each point in the scaling algorithm curve that means a turn in the line direction mustbe specified, and the points must be given in ascending order. For each number, enterthe process values in the text boxes to the left and the corresponding MicroSCADAprocess database values in the text boxes to the right.

The Insert button allows you to enter scaling points in-between two points. The De-lete button deletes the selected point. The insertion and deletion place is determinedby clicking one of the text boxes in the correct row. Inserting moves the selected rowand all rows below it one row downwards. Deleting removes the selected row andmoves all the rows below it one row upwards.

Entering superfluous data points makes no harm, provided that they represent correctrelations between process values and values stored in the MicroSCADA process data-base.


MicroSCADA15 Data Object Definition Tool

ABB Automation 195

15 Data Object Definition Tool

About this Chapter

This chapter describes how to define data objects using the definition tool.

Overview

You access the Data Object Definition Tool from the Object Navigator by double-clicking a data object. A new object is created in the Object Navigator. The procedureis described in the Chapter 12. The tool is also accessed from the definition tools fortime channel and event channel.

The Data Object Definition Tool, see Figure 65, is composed of a common area andfive pages. The pages contain the following definitions and information:

• The Data Registration page defines the calculation of the object.

• The Data page lists the registered data and provides means for editing the objectvalue, the status code and registration time of certain indices.

• The Execution Control page defines the automatic time activation of the data ob-ject and the executing tasks.

• The Storage page defines the file where the object is saved. It also defines thingsconcerning the registration and storage of data.

• The All Attribute page lists all attributes with their values in alphabetical order.

To define a new data object or edit an existing one, double-click the object name inthe Object Navigator and modify the desired attribute values on the data object form.You can check all attributes in the All Attributes page, and view registered data in theData page.



1MRS751253-MEN

ABB Automation196

Figure 65. The Data Object Definition Tool includes five pages. In the first one,Data Registration, you can define the calculation of the object.

Common Area

The tool has a common area above and below the pages.

Enter the following in the common area above the pages:

Comment, CM Enter a freely chosen text comment text of maximum 255characters. The comment text, which is optional but recom-mended, should describe the object briefly.

In use, IU Take the object into use and out of use with the In Usecheck box. The selection is applied to the data object whenOK or Apply is clicked. The selection specifies the IU at-tribute.

The Value Type (VT) is shown in the upper right hand corner.



ABB Automation 197

The Last Modified date in the bottom of the tool page shows the time when the objectwas created or last edited, the ZT attribute.

Data Registration

The Data Registration page specifies the calculations to be performed at data objectexecution. The list of SR (Source) shows only Data Objects of the same type (VT).

The list can be opened by clicking the button. See Figure 65. This button is en-abled only when the "Copy Data from Another Data Object" is marked.

Enter the following data in this page:

Instruction, IN The SCIL expression to be used in calculating or samplingthe data object.

Logging function, LF Choose logging function by browsing in the list. The chosenfunction determines the value of the attribute LF as follows:

DIRECT = 0

SUM = 1

MEAN VALUE = 2

INTEGRAL = 3

DIFFERENCE = 4

PULSE DIFFERENCE = 5

DERIVATIVE = 6

PULSE DERIVATIVE = 7

MAXIMUM = 8

MINIMUM = 9

Copy Data from ... Select this check box to choose logging function COPY (theobject is copied from another object). If chosen a possibleselection in the Logging function list is disregarded. Whenyou select this check box, the LF attribute is set to COPY.See Figure 66.

Source, SR The name of the data object to be copied if the loggingfunction is COPY. This text box is shaded and disabled ifthe logging function is another than COPY.

Pulse Scale, PS This text box is enabled when PULSE DIFFERENCE orPULSE DERIVATIVE is chosen as logging function. Enterthe value, at which the pulse counter is set to zero.

A data object that is out of use cannot be executed.



1MRS751253-MEN

ABB Automation198

Figure 66. Copy Data from Another Data Object check box is checked to enablelogging function COPY

Data

The second page of the Data Object Definition Tool is shown in Figure 67. This pageshows the dynamic values of the data objects - value (OV), status (OS) and registra-tion time (RT).

In the area showing the registered values, the indices are shown to the left. You canbrowse through the indices using the scroll bars. Above the registered values is theinternal object value (stored value) with status codes and registration time.

The tool reads the values from the report database. The shown values can be updatedby clicking the Fetch button in the Data page. There are also possibilities for listingthe registered values. The listing order and the listed indices can be defined using thecontrols to the right from the Registered Values list. You can change the dynamic at-tributes in the tool.



ABB Automation 199

Figure 67. The second page of the Data Object Definition Tool contains dynamicdata of the Data Objects. You can view or change the data.

To change the registered attributes or the internal value:

1 Click the data post you wish to edit.

2 Click the Edit... button.

3 The dialog in Figure 68 is shown on screen. The upper row shows the old values ofthe attributes. Type the new values in the lower text box row.

4 Click OK to exit the dialog and confirm the changes or Cancel to exit withoutsaving the changes.

The value is updated directly to the database immediately as you click OK. Thismeans that you cannot cancel the changes by clicking Cancel in the definition tool.



1MRS751253-MEN

ABB Automation200

Figure 68. Using this dialog you can change the values of OV, OS and RT attrib-utes.

Execution Control

Figure 69 shows the Execution control page of the Data Object Definition Tool. Inthis page you can specify the time activation and the executing tasks.

Figure 69. The Execution Control page of the Data Object Definition Tool

Time Channel, TC The name of the time channel that will execute thedata object. You can choose time channel by typingthe name in the text box, or by selecting it in the list(produced by clicking the button with three dots).You access the definition of the chosen time channelby clicking the Show TC button to the right.

Execution Priority EP The execution priority of the data object (1...255)in relation to other data objects and command proce-dures started by the same time channel. The defaultvalue is 255, which is the lowest priority. This can bechanged by scrolling to the right number with the helpof the black arrows.

Start-up Execution, SE A cross in the box means that the data object is exe-cuted during application start-up. Click the box tochange the selection.



ABB Automation 201

Parallel Execution, PE A cross in the box means that parallel execution isallowed. Click the box to change the selection.

Queue (PQ) If parallel execution is allowed, enter the queue num-ber in the text box to the right.

Storage

Figure 70 shows the Storage page of the Data Object Definition Tool.

Figure 70. The storage page of the Data Object Definition Tool

Enter the following definitions in the page:

Data in, HN If desired, enter the file number, 0 ... 99, which willbe used in the extension of the name of the file wherethe object will be saved. The HN attribute.

Attributes in RAM, MO Here you can choose to save the dynamic attributes(OV, OS, LR and RT) in RAM only.

Time stamp, TS Choose whether the time stamp of the data registra-tion will be taken from the operating system time orcopied from the variable %RT. When started by anevent channel the %RT variable has the value of thetime stamp (the RT attribute) of the process objectthat activated the event channel.

History Registrations, HR Enter the maximum number of registrations that willbe saved. When this value is exceeded, the oldestregistered values will drop out of the object.

At the bottom of the page is the number of the latest registration in the data object, theLR attribute. The value can be edited.



1MRS751253-MEN

ABB Automation202

All Attributes

The page named All Attributes is shown in Figure 71. The page lists all attributes inalphabetical order. The attribute values in white text boxes can be edited. The attrib-ute values with grey background cannot be edited. The attributes whose names aregreyed out are not valid for the data object. Browse through the attribute list by mov-ing the scroll bar.

Figure 71. The All Attributes page of the Data Object Definition Tool


MicroSCADA16 Command Procedure Definition

Tool

ABB Automation 203

16 Command Procedure Definition Tool

This chapter describes how to define command procedures using the definition tools.

Overview

The definition tool for command procedures is accessed from the Object Navigator bydouble-clicking a command procedure. A new object is created in the Object Naviga-tor. The procedure is described in the Chapter 12. It can also be accessed from timechannel and event channel tools.

The Command Procedure Definition Tool comprises a common area and four pages.The pages contain the following definitions and information:

• The Procedure page contains the program of the command procedure.

• The page Execution control defines the automatic time activation of the commandprocedure and the executing tasks.

• The Storage page defines the file where the object is saved and the origin of thetime stamp.

• The All Attributes page finally lists all attributes in alphabetical order.

Common Area

Enter the following in the common area:

Comment Enter a comment text. The comment text, which is optionalbut recommended, is a freely chosen text of maximum 255characters. The text should describe the object briefly. TheCM attribute.

In Use Take the object into use and out of use with the In Usecheck box. The selection is applied to the object when OKor Apply is clicked. The selection specifies the IU attribute.

Procedure Page

Figure 72 shows the Procedure page of the Command Procedure Definition Tool. TheInstruction (IN): list contains the program. You can browse up and down, to the leftand to the right in the program by using the scrollbars.

If the object is not taken into use, it cannot be executed.

MicroSCADA16 Command Procedure DefinitionTool


1MRS751253-MEN

ABB Automation204

To type a new program or edit an existing one:

1 Click the Edit button or doubleclick the Instruction (IN): list.

2 The SCIL editor appears as a separate dialog. The general functions of the SCILEditor are described in the Programming Language SCIL manual. It is alsopossible to import and export text from the SCIL Program Editor. To importchoose Import and to export choose Export from the File menu. The importfunction opens a file chooser, where the name of the file to be imported isspecified. If you click OK or Apply, the contents of the file is loaded to the SCILProgram Editor. It is placed starting from the row where the cursor is, if the row isempty. It there is text in the row, the contents is placed starting from the next row.The Export function opens also a file chooser where the name of the file isspecified. If no text is selected, everything in the SCIL Program Editor istransferred to the specified file. Note that if existing file is specified, exportoverwrites previous contents of the file.

Compile IN when Edited If check box is checked, the compilation is done al-ways when user edits and updates the IN-attribute. Asuccessful compilation updates the IN and CP-attributes.

Compiling a Command Procedure:

1 Click Edit. The SCIL editor is opened. Enter the Command Procedure or edit anold one. If the Compile IN when Edited procedure mentioned above has beendone, the following step 2. can be skipped, otherwise proceed to step 2.

2 In the SCIL editor, check the Compilation in Use option on the Options menu.

3 Choose Update on the File menu.

4 Choose Exit on the File menu.

‘Compile IN when Edited’ is checked because compilation was taken into use in theSCIL editor. A successful compilation updates the IN and CP-attributes and ‘Com-piled’ is shown in the ‘Compile Status:’ field.

If compilation is cancelled in the SCIL editor (IN could not be compiled or user can-celled the compilation), the IN attribute is updated and the CP attribute is emptied.

If compiled program exists 'Uncompile'-button can be used to clear the CP-attribute.

If the command procedure is compiled (CP not empty), the Command Procedure toolautomatically checks the 'Compile IN when edited' check box on 'Procedure'-tab. Oth-erwise (not compiled) the check box is not checked as default.



Tool

ABB Automation 205

Figure 72. The Procedure page of the Command Procedure Definition Tool

Execution Control Page

Figure 73 shows the Execution Control page.

Figure 73. The Execution Control page of the Command Procedure Definition Tool

The upper section of the page specifies the time activation of the command procedure:

Time channel If time activation will be used, enter the name of the acti-vating time channel, either by typing it in the box or bybrowsing in the list for the desired time channel. The visible

MicroSCADA16 Command Procedure DefinitionTool


1MRS751253-MEN

ABB Automation206

time channel name is the activating time channel. By click-ing the Show button to the right you get access to the defi-nition tool of the selected time channel and can edit it if de-sired.

Execution Priority The execution priority of the command procedure within thetime channel. Value 255 is the lowest priority.

Start-up Execution A cross in the box means that start-up execution is set. Clickthe box to set or clear start-up execution. If start-up execu-tion is set, the object will be executed at application start-up,in case the time channel would have started while the appli-cation was not running.

The lower section of the page defines the executing tasks.

Storage Page

Figure 74 shows the Storage page of the definition tool.

Figure 74. The Storage page of the Command Procedure Definition Tool

The upper section of the page specifies the file where the command procedure will besaved and the storage of the OS and RT attributes in RAM only. Generally, use RAMonly (a cross in the box) for all command procedures, unless the OS and RT attributesare of special importance.

The lower section of the tool defines the origin of the time stamp, that is, the RT at-tribute.

All Attributes

Figure 75 shows the page All Attributes. This page lists all command procedure at-tributes in alphabetical order.



Tool

ABB Automation 207

Figure 75. All Attributes page of the Command Procedure Definition Tool


MicroSCADA17 Time Channel Definition Tool

ABB Automation 209

17 Time Channel Definition Tool

About this Chapter

This chapter provides a point-by-point description of the input fields and functionbuttons in the Time Channel Definition Tool.

Overview

The Time Channel Definition Tool, see Figure 76, comprises a common area and fivepages containing the following definitions and information:

• The Execution page specifies the Execution of the time channel.

• The Initialisation page specifies the Initialisation of the time channel.

• The Execution Control page defines the executing tasks.

• The Objects page shows the objects connected to the time channel.

• The All Attribute page finally lists all attributes in alphabetical order.

Common Area

The common area of the Time Channel Definition Tool contains the following defini-tions:

Comment Enter a freely chosen text of maximum 255 characters. Thecomment text, which is optional but recommended, shoulddescribe the object briefly. The text will be the CM attrib-ute.

In Use Take the object into use and out of use with the In Usecheck box. The selection is applied to the object when OKor Apply is clicked. The selection specifies the IU attribute.

Execution Page

The Execution page specifies the execution time of the time channel. See Chapter 7 toget an explanation of the execution of time channels.

If the object is not taken into use, it cannot be executed.



1MRS751253-MEN

ABB Automation210

Figure 76. The Execution page of the Time Channel Definition Tool

Execution cycle The time interval for periodically recurrent executions ifsuch is desired. The fields can be left empty. The CY attrib-ute, index 2.

Condition for ... A conditional expression according to the rules of SCIL.Enter a condition if you wish to limit the execution. Initiali-sation/execution occurs only when the condition is fulfilled.The CD attribute.

Synchronisation The synchronisation times. The selections are a combinationof SU and SY attributes.

The synchronisation time is determined as follows:

• No synchronisation.

• Synchronisation once.

• Synchronisation once a year.

• Synchronisation once a month.

• Last day of month.

• Once a week.



ABB Automation 211

• Specific day of week.

• Last day of month.

• Once a day.

• Once an hour.

The time stamps of the time channel farthest down on the page show the last execu-tion time and the last synchronisation time.

Initialisation Page

Figure 77 shows the initialisation page. This page specifies the initialisation times ofthe time channel. See Chapter 7 to get an explanation of what initialisation means.

Execution cycle The time interval for periodically recurrent executions ifsuch is desired. The fields can be left empty. The CY attrib-ute, index 2.

Condition for ... A conditional expression according to the rules of SCIL.Enter a condition if you wish to limit the occurrences ofexecutions. Initialisation/execution occurs only when thecondition is fulfilled. The CD attribute.

Synchronisation The synchronisation times. The selections are a combinationof SU and SY attributes. The synchronisation alternativesare the same as for execution.

The time settings farthest down on the page show the latest initialisation and synchro-nisation times.



1MRS751253-MEN

ABB Automation212

Figure 77. The Initialisation page of the Time Channel Definition Tool

Execution Control Page

Figure 78 shows the Execution Control page.

Parallel Execution A cross in the box means that parallel execution is allowed.Click the box to change the selection. If parallel execution isallowed, enter the queue number in the field to the right.The PE and PQ attributes.

Synchronised Exe... The SX attribute.



ABB Automation 213

Figure 78. The Execution Control page of the Time Channel Definition Tool

Objects Page

The Objects page provides an overview of all data objects and command proceduresconnected to the time channel. See Figure 5. To get the list of the connected objectsand command procedures, click the Fetch button. Only the first 10 000 objects areshown in the list. If there are more than 10 000 connections, the user is informed witha Time Channel dialog. See Figure 79.



1MRS751253-MEN

ABB Automation214

Figure 79. This Time Channel dialog informs that there are more than 10 000 con-nected objects, but only the first 10 000 are shown.

Each row in the list contains the name of an object, the priority within the time chan-nel and the object type The page is of informative character and the list of connectedobjects cannot be edited here. Objects are added to the list when they are defined intheir respective tools to be activated by the time channel in question. However, theobject definitions are accessed from the list.

To view or edit any of the objects in the list, click the object and then the Show Ob-ject button.

The definition of the selected object appears in a new window.

Figure 80. The Objects page of the Time Channel Definition Tool



ABB Automation 215

All Attributes

Figure 81 shows the page All Attributes. The page lists all time channel attributes inalphabetical order. All attributes, except the read-only attributes, can be changed. Thedata fields of the read-only attributes are grey.

Figure 81. The All Attributes page of the Time Channel Definition Tool


MicroSCADA18 Event Channel Definition Tool

ABB Automation 217

18 Event Channel Definition Tool

About this Chapter

This chapter describes how to define event channels using the object definition tools.

Overview

The definition tool for defining event channels is accessed from the Object Navigatorby double-clicking an event channel. A new object is created in the Object Navigator.The procedure is described in the Chapter 12. The tool is also obtained from the Proc-ess Object Definition Tool by selecting to view the event channel of a process object.

The Event Channel Definition Tool, see Figure 82, comprises a common area andthree pages containing the following definitions and information:

• The page Activated Objects specifies the primary and secondary objects activatedby the event channel.

• The page Process Objects lists all process objects connected to the event channel.The list cannot be edited, but the process object definitions are accessible in thepage.

• The page All Attributes lists all attributes in alphabetical order.

Common Area

Comment The comment text is optional but recommended, a freely chosen text ofmaximum 255 characters, the CM attribute. The comment text shoulddescribe the event channel briefly.

Activated Objects

Figure 82 shows the page Activated Objects. This page specifies the data objects andcommand procedures activated by the event channel.



1MRS751253-MEN

ABB Automation218

Figure 82. Activated Objects page of an Event Channel

Primary Object The name and the type of the primary object (data object,command procedure or time channel) started by the eventchannel. The OT and ON attributes.

Secondary Objects The names and types of the secondary objects (data objects,command procedures and time channels) started by theevent channel. The ST and SN attributes.

To view the object definitions of the activated objects, click the object name in the listand then click the Show... button.

To add a new secondary object, click the Add... button.

To edit an object name or type in the list, click the object name and then the Set...button.

To remove a secondary object from the list, click the object name and then Remove.

Process Objects

The Process Objects page (see Figure 83) lists all process objects that activate theevent channel.



ABB Automation 219

Figure 83. The Process Objects page

The connection of process objects to the event channel is done in the process objectdefinition. Hence, the list cannot be edited. To view or edit the process object defini-tions, click the object in the list and then click the Show... button. The Show... buttonopens the Process Object Definition Tool where the selected objects can be edited asdescribed in Chapter 3. The Fetch button updates the contents of the list. The list isnot automatically updated when the tool is opened, so Fetch must always be clicked toview the connected process objects.

Attribute List

This page, see Figure 84, lists all event channel attributes in alphabetical order. Theattributes can be edited.



1MRS751253-MEN

ABB Automation220

Figure 84. All event channel attributes are listed in alphabetical order


MicroSCADA19 Free Type Object Definition

Tools

ABB Automation 221

19 Free Type Object Definition Tools

General

This chapter introduces the Free Type Object Tool and the Free Type Process ObjectTool. These tools are Application Object handling tools and are launched from theApplication Object Navigator.

The tool for handling application objects, Application Object Navigator, is accessedthrough Tool Manager. The Application Object Navigator presents objects classifiedby type in a tree where application names form the nodes and object types form theleafs. The Free Type Object tools are accessed by choosing object type and name ofthe object of interest.

19.1 Free Type Process Object Tool

Accessing the Tool

Clicking the Free Type Process Object type in the tree of Application Object Naviga-tor shows the object names in the listbox to right. To access the Free Type ProcessObject tool, double-click an object name. The dialog box shown in Figure 85 isopened.

MicroSCADA19 Free Type Object DefinitionTools


1MRS751253-MEN

ABB Automation222

Figure 85. The Free Type Process Object tool as it appears after double clicking anobject named Á_SPA_ANSW´ in the Object Navigator and expandingthe Ídentification´ node with the default view ´Standard´.

Fields

Logical Name (LN) Value (text) of the LN-attribute. The logical name ofthe process object (OBJ_NAME:PLN).

Process Object Type (PT) Value (integer) of the PT-attribute(OBJ_NAME:PPT).

Comment Text (CX) Value (text) of the CX-attribute. The value of this at-tribute is supposed to serve as a description of theobject (OBJ_NAME:PCX).

View This drop-down combo box offers two alternativeviews to the attribute tree. The alternative views areStandard and User Attributes.

Attribute tree The attributes are displayed in a tree structure ac-cording to category.

Attribute box Contains facilities for editing the attribute values dis-played in the ’Attribute Tree’.



Tools

ABB Automation 223

Attribute information A description of the attribute or its function.

Using the Tool

The Free Type Process Object tool is used for displaying and setting the values of at-tributes of free type process objects. For object identification the tool presents essen-tial identification attributes (LN, PT and CX).

Storing Settings and Exiting the Tool

The value of some attributes shown in the attribute box may be edited, others onlyviewed.

OK Save settings and close dialog. In case of an error the dialogstays open and the status code of the error is shown.

Cancel Close the tool without saving. If settings have been changedduring the session the user is asked to confirm the action.

Apply Save settings and leave dialog open. Use for intermediatesave.

19.2 Free Type Object Tool

Accessing the Tool

The Free Type Object tool is accessed from Application Object Navigator by double-clicking the ´Free Type Objects´ leaf in the tree.

Using the Tool

The Free Type Object tool is used for displaying and setting the values of attributes offree type objects. For object identification the tool presents essential identification at-tributes (LN and PT). The dialog consists of two main components; the ÁttributeDefinition´ tab and the Áttribute Tree´ tab.

Attribute Definition

User attribute names are presented in a listbox. The order in which they are presentedis determined by the elements in the textvector that is the value of the AN-attribute.This can be checked using the Éxamine´ tab of Test Dialog and enteringOBJ_NAME:FAN in the inspection field.

The properties of a single User Attribute are shown in the right side of the User At-tribute list. The properties displayed belong to the User Attribute currently selected inthe User Attribute list. The values of AN, AI, AT and AL indexes can not be config-ured on existing User Attributes.

MicroSCADA19 Free Type Object DefinitionTools


1MRS751253-MEN

ABB Automation224

Figure 86. Áttribute Definition´ tab of the Free Type Object definition tool

New User Attributes are defined by clicking the Ńew Attribute´ button, see Figure86. This action adds a ´+´ sign to the attribute list, focuses the Name(AN) field andassigns default values to the rest of the attribute indices. As the User Attribute name isdefined, the name is shown in the User Attributes list preceded by a ´+´ sign. The ´+´sign disappears as the definition is saved. The attribute indices AN, AI, AT and ALare modifiable until the User Attribute definition is saved. Removal of User Attributescan be done prior to saving. Saved User Attributes can not be removed. After savingthe User Attributes, the attributes appear on the View User Attributes tree of the sametype of process object in the Free Type Process Object Tool, see section 19.1.

Attribute Tree

The Áttribute Tree´ tab is used for grouping, displaying and modifying Free TypeObject attributes. The groups and attributes displayed in the tree are predefined (infile attrib_f.scl). When an attribute in the tree is selected an attribute data type spe-cific edit field is displayed in the edit box.



Tools

ABB Automation 225

Figure 87. The Áttribute Tree´ tab of Free Type Object definition tool

Storing Settings and Exiting the Tool

The value of attribute indices only for viewing are dimmed.

OK Save settings and close dialog. In case of an error the dialog stays openand the status code of the error is shown.

Cancel Close the tool without saving. If settings have been changed during thesession the user is asked to confirm the action.

Apply Save settings and leave dialog open. Use for intermediate save.


MicroSCADA

ABB Automation

INDEX

Page

A

AA ............................................................................................................................... 42, 153AB........................................................................................................................................ 67AC........................................................................................................................................ 40Accessible applications...................................................................................................... 161acknowledgement................................................................................................................. 42action activation................................................................................................................... 42action enabled ...................................................................................................................... 43action name.......................................................................................................................... 45Action on History................................................................................................................. 44activation as first update ...................................................................................................... 44Activation Blocking ............................................................................................................. 68AD ............................................................................................................................... 40, 153Addressing attributes ......................................................................................................... 184AE................................................................................................................................ 43, 153AF ........................................................................................................................................ 44AG ....................................................................................................................................... 38AH ............................................................................................................................... 44, 153AI ..................................................................................................................... 22, 24, 57, 151AL................................................................................................................................ 64, 152alarm .............................................................................................................................. 16, 64alarm activation.................................................................................................................... 38alarm blocking ..................................................................................................................... 67alarm buffer.......................................................................................................................... 16alarm class ........................................................................................................................... 40alarm delay........................................................................................................................... 40alarm generation .................................................................................................................. 38alarm handling ..................................................................................................................... 37alarm list .................................................................................................................... 143, 144alarm milliseconds ............................................................................................................... 65alarm monitor....................................................................................................................... 41Alarm on Time..................................................................................................................... 67Alarm on time Milliseconds................................................................................................. 66alarm picture ........................................................................................................................ 41alarm picture queue.............................................................................................................. 41alarm receipt ........................................................................................................................ 64alarm state ............................................................................................................................ 65alarm time ............................................................................................................................ 65alarm zone............................................................................................................................ 66AM....................................................................................................................................... 65AN ............................................................................................................................... 45, 151Analog Input ................................................................................................................ 57, 170Analog Output.............................................................................................................. 58, 170AND................................................................................................................................... 167AO ................................................................................................................... 22, 24, 58, 154AP ...................................................................................................................................... 152APL_ALARM.................................................................................................................... 134


1MRS751253-MEN

ABB Automation

APL_EVENT. ................................................................................................................... 137APL_INIT_1 ............................................................................................................... 22, 134APL_INIT_2 ............................................................................................................... 22, 134APL_INIT_H .................................................................................................................... 134APL_REPORT .......................................................................................................... 116, 132application ......................................................................................................................... 1, 9application objects................................................................................................................. 4AR ....................................................................................................................................... 64AS................................................................................................................................ 65, 154AT ............................................................................................................................... 65, 151attribute............................................................................................................................ 5, 19Attribute .............................................................................................................................. 23Attribute Access .................................................................................................................. 11Attribute access level........................................................................................................... 11Attribute Action................................................................................................................. 153Attribute Event .................................................................................................................. 153Attribute History................................................................................................................ 153Attribute Indexing ............................................................................................................. 151Attribute Length ................................................................................................................ 152attribute name .................................................................................................................. 8, 10Attribute Name .................................................................................................................. 151Attribute Offset.................................................................................................................. 154Attribute on Disk ............................................................................................................... 153Attribute Printout............................................................................................................... 152Attribute Snapshot ............................................................................................................. 154Attribute Value Type......................................................................................................... 151Attribute Values

Editing ......................................................................................................................... 168automatic dial-up ............................................................................................................... 129automatic printout.......................................................................................................... 16, 53AX ..................................................................................................................................... 154AZ........................................................................................................................................ 66

B

basesystem............................................................................................................................. 1BC ....................................................................................................................................... 31BI ............................................................................................................................ 22, 24, 58Binary Input................................................................................................................... 16, 58Binary Output ...................................................................................................................... 59bit count............................................................................................................................... 31Bit Stream................................................................................................................ 16, 24, 59BL........................................................................................................................................ 72BLocked .............................................................................................................................. 72BO ........................................................................................................................... 22, 24, 59BS............................................................................................................................ 22, 24, 59

C

CA ....................................................................................................................................... 82Cause of Transmission......................................................................................................... 72CD ..................................................................................................................... 123, 214, 215CE........................................................................................................................................ 55CHANGE .......................................................................................................................... 131changed attribute ................................................................................................................. 82CL........................................................................................................................................ 55CM............................................................................... 97, 111, 127, 132, 200, 207, 213, 221CO ....................................................................................................................................... 69command procedure ...................................................................................................... 3, 120


MicroSCADA

ABB Automation

command procedures ................................................................................................. 109, 207Command Procedures ........................................................................................................ 160command QuaLifier ............................................................................................................. 77Comment...................................................................................................... 97, 111, 127, 132comment text........................................................................................................................ 25Comment Text ........................................................................................................... 150, 154communication system........................................................................................................... 1Compiled Program............................................................................................................. 113condition .................................................................................................................... 119, 120Condition ........................................................................................................................... 123COPY................................................................................................................................. 101Copying.............................................................................................................................. 173Copying objects ................................................................................................................. 173counter enable...................................................................................................................... 55counter limit......................................................................................................................... 55counter overflow.................................................................................................................. 69counter value........................................................................................................................ 69CP ...................................................................................................................................... 113CREATE.............................................................................................................................. 13Creating Application Objects............................................................................................. 169creating objects .................................................................................................................... 13CT ........................................................................................................................................ 72CV........................................................................................................................................ 69CX................................................................................................................................ 25, 150CY...................................................................................................................... 123, 214, 215Cyan symbol ...................................................................................................................... 161Cycle .................................................................................................................................. 123cycle time........................................................................................................................... 119

D

data .......................................................................................................................... 93, 95, 98data object.................................................................................................. 2, 93, 94, 120, 199data type............................................................................................................................... 10database ................................................................................................................................. 6datalog object....................................................................................................................... 93DB............................................................................................................................ 22, 24, 59DC........................................................................................................................................ 79Defining a filter.................................................................................................................. 166Defining Application Objects ............................................................................................ 172defining objects...................................................................................................................... 5Defining Process Object Group ......................................................................................... 172DELETE .............................................................................................................................. 14Deleting.............................................................................................................................. 176deleting objects .................................................................................................................... 14DI............................................................................................................................. 22, 24, 60DIFFERENCE ................................................................................................................... 101Digital Input................................................................................................................... 16, 60Digital Output ...................................................................................................................... 60DIRECT............................................................................................................................. 100directive text ........................................................................................................................ 56Directory Contents ............................................................................................................... 79DO ................................................................................................................... 22, 24, 60, 109Double Binary Indication............................................................................................... 24, 59DX ....................................................................................................................................... 56

E

ED........................................................................................................................................ 82


1MRS751253-MEN

ABB Automation

EE........................................................................................................................................ 45EM....................................................................................................................................... 83end of period........................................................................................................................ 74EP ........................................................................................................ 74, 104, 109, 114, 204ET........................................................................................................................................ 83event activated screen control.............................................................................................. 45event channel ........................................................................... 3, 16, 44, 45, 94, 95, 129, 132event channel activation .............................................................................................. 42, 130event channel task.............................................................................................................. 130event channels ................................................................................................................... 221Event comment teXt ............................................................................................................ 83Event Daylight saving.......................................................................................................... 82event enabled....................................................................................................................... 45event handling ..................................................................................................................... 42event list ............................................................................................................................ 143event methods.................................................................................................................... 139event object ....................................................................................................... 3, 12, 16, 139Event object....................................................................................................................... 139event object handling........................................................................................................... 12event recording object ......................................................................................................... 23event recording objects........................................................................................................ 15Event recording objects ..................................................................................................... 171Event Time .......................................................................................................................... 83Event time Milliseconds ...................................................................................................... 83EX ....................................................................................................................................... 83EXEC ...................................................................... 12, 94, 95, 109, 110, 129, 131, 140, 141executing objects ................................................................................................................. 12executing task ...................................................................................................... 95, 110, 121execution ........................................................................................................... 119, 120, 121Execution................................................................................................................... 109, 113Execution Priority...................................................................................................... 104, 114expression.............................................................................................................. 93, 95, 201External application........................................................................................................... 161External Applications ........................................................................................................ 162

F

Fetch.................................................................................................................................. 183FF ........................................................................................................................................ 79FI .................................................................................................................................. 56, 98File Function........................................................................................................................ 79File Name ............................................................................................................................ 79File Transfer .................................................................................................... 16, 24, 80, 177File transfer Progress........................................................................................................... 80Filter .................................................................................................................................. 166

Editing ......................................................................................................................... 167Quotation mark............................................................................................................ 166

Filtering ............................................................................................................................. 165Process Objects ........................................................................................................... 166

FN........................................................................................................................................ 79FP ........................................................................................................................................ 80free integer........................................................................................................................... 56Free Integer ................................................................................................................. 98, 112free text................................................................................................................................ 56Free Text ..................................................................................................................... 98, 112free type object ...................................................................................................................... 3free type objects................................................................................................................. 147FT .................................................................................................................................. 24, 80


MicroSCADA

ABB Automation

FX .................................................................................................................................. 56, 98

G

GC........................................................................................................................................ 86GET ..................................................................................................................................... 13global variables.................................................................................................................... 93Green symbol..................................................................................................................... 161Grey symbol....................................................................................................................... 161group.............................................................................................................................. 22, 23Group ................................................................................................................................. 172group comment .................................................................................................................... 86group type ............................................................................................................................ 86GT........................................................................................................................................ 86

H

HA ....................................................................................................................................... 49HB........................................................................................................................................ 67HD ....................................................................................................................................... 83HE........................................................................................................................................ 50HF ........................................................................................................................................ 50HH ....................................................................................................................................... 50HI......................................................................................................................................... 33higher input .......................................................................................................................... 33higher warning ..................................................................................................................... 33historical data....................................................................................................................... 93history activation.................................................................................................................. 49history at first update ........................................................................................................... 50History Blocking.................................................................................................................. 67history buffer.................................................................................................................. 16, 50history buffering................................................................................................................... 48History Database.................................................................................................................. 48history enabled..................................................................................................................... 50History File Number .................................................................................................. 105, 116history log number ............................................................................................................... 51History logging Daylight saving .......................................................................................... 83History logging Time........................................................................................................... 84History logging time Milliseconds....................................................................................... 84History on History................................................................................................................ 50History Registrations ......................................................................................................... 106HL........................................................................................................................................ 51HM....................................................................................................................................... 84HN ............................................................................................................... 96, 105, 110, 116HO ....................................................................................................................................... 33HOT state........................................................................................................................... 161HR...................................................................................................................................... 106HT........................................................................................................................................ 84HW ...................................................................................................................................... 33

I

ID......................................................................................................................................... 80Identification........................................................................................................................ 80IEC....................................................................................................................................... 76IN............................................................................................................... 100, 111, 113, 201In Use............................................................................................................. 29, 98, 112, 122index .................................................................................................................. 10, 21, 22, 23Index .................................................................................................................................... 23INIT_QUERY ..................................................................................................................... 13


1MRS751253-MEN

ABB Automation

initialisation ....................................................................................................... 119, 120, 121Instruction.................................................................................................................. 100, 113Integer Representation......................................................................................................... 31INTEGRAL....................................................................................................................... 100IR ........................................................................................................................................ 31IR attribute......................................................................................................................... 170IU .................................................................................................................. 29, 98, 112, 122IU check box ..................................................................................................................... 169IX ........................................................................................................................................ 23IX attribute ........................................................................................................................ 170

L

LA........................................................................................................................................ 38LAG 1.4............................................................................................................................. 177Latest Registration............................................................................................................. 106LD ....................................................................................................................................... 52LF ........................................................................................................................ 86, 100, 201LI ........................................................................................................................................ 34LIB500 .................................................................................................................................. 8linear scaling.................................................................................................................. 90, 91list ...................................................................................................................................... 143LIST .................................................................................................................................... 86listing device........................................................................................................................ 52LN ........................................................................................... 23, 90, 98, 112, 122, 132, 149LO ....................................................................................................................................... 34Local application ............................................................................................................... 161logging function................................................................................................................... 93Logging Function .............................................................................................................. 100logical format ...................................................................................................................... 86Logical Name .......................................................................... 23, 90, 98, 112, 122, 132, 149lower input........................................................................................................................... 34lower output......................................................................................................................... 34lower warning...................................................................................................................... 34LR...................................................................................................................................... 106LW....................................................................................................................................... 34

M

Magenta symbol ................................................................................................................ 161MAXIMUM ...................................................................................................................... 101MaXimum Time .................................................................................................................. 71MaXimum time Milliseconds .............................................................................................. 70MaXimum Value ................................................................................................................. 71MEAN VALUE................................................................................................................. 100Memory Only ............................................................................................................ 106, 116MINIMUM........................................................................................................................ 101Minimum Time.................................................................................................................... 70Minimum time Milliseconds................................................................................................ 70Minimum Value................................................................................................................... 70MM...................................................................................................................................... 70MO .................................................................................................................... 106, 110, 116Modification Time............................................................. 25, 87, 92, 99, 113, 122, 134, 150MODIFY ............................................................................................................................. 13MON_EVENT .................................................................................................................. 135Moving .............................................................................................................................. 176MT....................................................................................................................................... 70MV ...................................................................................................................................... 70


MicroSCADA

ABB Automation

N

NA ..................................................................................................................................... 150New.................................................................................................................................... 169NEXT .................................................................................................................................. 14Next Group ........................................................................................................................ 183Next Index ......................................................................................................................... 183Normal Value....................................................................................................................... 39Not sampled ......................................................................................................................... 97Number of Attributes ......................................................................................................... 150NV ....................................................................................................................................... 39

O

OA ............................................................................................................................... 26, 168OB.......................................................................................................................... 26, 27, 168Object Bit Address............................................................................................................... 27Object Identifier................................................................................................................... 25object name............................................................................................................................ 9Object Name ...................................................................................................................... 133Object Navigator................................................................................................................ 157object notation ................................................................................................................. 8, 11Object Status........................................................................................................ 62, 102, 113object text ............................................................................................................................ 25Object Type ....................................................................................................................... 133Object Value .......................................................................................................... 57, 60, 103Objects by Group............................................................................................................... 157Objects in Table................................................................................................................. 157OF ........................................................................................................................................ 75OG ....................................................................................................................................... 77OI......................................................................................................................................... 25ON ............................................................................................................... 12, 133, 139, 141Options............................................................................................................................... 164Options menu............................................................................................................. 157, 165OR................................................................................................................................ 73, 167OriGinator identification......................................................................................................77OS .............................................................................................. 16, 62, 64, 96, 102, 110, 113OT.................................................................................................................. 27, 28, 133, 222Out of Range........................................................................................................................ 73Output Type ......................................................................................................................... 28OV ..................................................................................................... 16, 22, 60, 96, 103, 149OV Attribute Name............................................................................................................ 149overflow............................................................................................................................... 75OX ....................................................................................................................................... 25

P

PA........................................................................................................................................ 52Page Length ....................................................................................................................... 165Parallel Execution.............................................................................................. 104, 115, 125Parallel Queue............................................................................................................ 104, 125Parallel Queue.................................................................................................................... 115PB ........................................................................................................................................ 68PC ............................................................................................................................ 22, 24, 61PD........................................................................................................................................ 41PE ........................................................................................................ 95, 104, 110, 115, 125PF......................................................................................................................................... 53PH........................................................................................................................................ 54physical format..................................................................................................................... 53


1MRS751253-MEN

ABB Automation

PI ........................................................................................................................................ 41picture.................................................................................................................................. 41picture at first update ........................................................................................................... 54picture devices..................................................................................................................... 41PQ...................................................................................................................... 104, 115, 125predefined event channel ................................................................................................... 134PREV................................................................................................................................... 14Previous Group.................................................................................................................. 183Previous Index................................................................................................................... 183printer .................................................................................................................................. 52printout ................................................................................................................................ 51printout activation................................................................................................................ 52Printout Blocking ................................................................................................................ 68Printout on History .............................................................................................................. 54priority....................................................................................................................... 119, 120process database ............................................................................................ 6, 16, 18, 21, 65Process database limits ........................................................................................................ 21process object ................................................................................................................ 2, 140process object group............................................................................................................ 21Process object groups ........................................................................................................ 176process object notation ........................................................................................................ 22Process Object Type.................................................................................................... 24, 149process objects......................................................................................................... 15, 16, 23Process Objets ................................................................................................................... 157process query....................................................................................................................... 13PROD_QUERY............................................................................................................. 13, 48PS .............................................................................................................................. 101, 201PT ................................................................................................................................ 24, 149PT attribute........................................................................................................................ 170PU........................................................................................................................................ 54Pulse Counter .......................................................................................................... 16, 24, 61PULSE DERIVATIVE...................................................................................................... 101PULSE DIFFERENCE...................................................................................................... 101Pulse Scale......................................................................................................................... 101

Q

QL ....................................................................................................................................... 77

R

RA ....................................................................................................................................... 74RAM.............................................................................................................................. 21, 65RB ............................................................................................................................... 74, 126RC ....................................................................................................................................... 42RE...................................................................................................................................... 126reading an attribute .............................................................................................................. 10receipt .................................................................................................................................. 42Recent Objects list............................................................................................. 163, 173, 176Registered Begin Time ...................................................................................................... 126Registered End Time ......................................................................................................... 126Registered Synchronisation ............................................................................................... 127Registration Milliseconds .................................................................................................... 63Registration Time ........................................................................................ 63, 103, 114, 127Renaming........................................................................................................................... 172report cache ....................................................................................................................... 132report database....................................................................................................... 6, 129, 132report object .......................................................................................................................... 6Reserved A .......................................................................................................................... 74


MicroSCADA

ABB Automation

Reserved B........................................................................................................................... 74Reserved Integer .................................................................................................................. 56Reserved Text ...................................................................................................................... 56RI ......................................................................................................................................... 56RM................................................................................................................................. 16, 63RS ...................................................................................................................................... 127RT .................................................................................................. 63, 96, 103, 110, 114, 127RTU ............................................................................................................................... 16, 26RX........................................................................................................................................ 56

S

SA .................................................................................................................................. 90, 91SB ........................................................................................................................................ 74SC .................................................................................................................................. 32, 91SCADA.................................................................................................................................. 1SCADA zone supervision .................................................................................................... 35scale ....................................................................................................................................... 2scale name............................................................................................................................ 32scales.................................................................................................................................. 195SCALES .............................................................................................................................. 89scaling.................................................................................................................................. 32scaling algorithm.................................................................................................................. 89Scaling Algorithm................................................................................................................ 90Scaling Constants................................................................................................................. 91SCIL................................................................................................................... 6, 7, 8, 11, 12SCIL commands................................................................................................................... 12SCIL expression................................................................................................................... 93SCIL program .................................................................................................................... 109SE ........................................................................................................................ 75, 105, 115SEARCH.............................................................................................................................. 14searching through objects .................................................................................................... 14Secondary object............................................................................................................... . 170Secondary object Names.................................................................................................... 133Secondary object Types ..................................................................................................... 133selection ............................................................................................................................... 75SET .................................................................................................................... 10, 11, 12, 96SN .......................................................................................................................... 32, 89, 133snapshot variable................................................................................................................ 130sort type ............................................................................................................................... 32Source ................................................................................................................................ 102SP......................................................................................................................................... 76SR ...................................................................................................................................... 102SS................................................................................................................................... 16, 29ST .......................................................................................................................... 32, 81, 133Start-up Execution ..................................................................................................... 105, 115station................................................................................................................................... 15Status ................................................................................................................................... 81Status bar ........................................................................................................................... 159stepwise linear scaling ................................................................................................... 90, 91stop execution ...................................................................................................................... 76Storage ................................................................................................................................. 21Storing ............................................................................................................................... 179SU ................................................................................................................................ 30, 123SuBstituted........................................................................................................................... 74SUM................................................................................................................................... 100Switch State ......................................................................................................................... 29SX .............................................................................................................................. 125, 126


1MRS751253-MEN

ABB Automation

SY.............................................................................................................................. 123, 124synchronisation.................................................................................. 119, 123, 124, 127, 214Synchronisation Time........................................................................................................ 124Synchronisation Unit ......................................................................................................... 123Synchronized Execution .................................................................................................... 125SYS_EVENT .................................................................................................................... 135SZ ........................................................................................................................................ 35

T

Table Index.......................................................................................................................... 28Table Page Length............................................................................................................. 165task ...................................................................................................................................... 95TC...................................................................................................................... 105, 116, 204TH ....................................................................................................................................... 46Threshold............................................................................................................................. 46TI ........................................................................................................................................ 28time activation ................................................................................................................... 105time channel....................................................................................... 3, 94, 95, 119, 120, 213Time Channel ............................................................................................................ 105, 116TIME DERIVATIVE........................................................................................................ 101time stamp ..................................................................................................................... 16, 63Time Stamp ............................................................................................................... 102, 114trend data ............................................................................................................................. 93TS .............................................................................................................................. 102, 114TY ....................................................................................................................................... 78type ........................................................................................................................................ 9TYpe identification.............................................................................................................. 78

U

UB ....................................................................................................................................... 68UN............................................................................................................................... 28, 168UNDEF_PROC ................................................................................................................. 135Unit Number........................................................................................................................ 28Update Blocking.................................................................................................................. 68updating process database ................................................................................................... 13user-defined attribute................................................................................................. 147, 150User-defined attribute................................................................................................ 165, 169Using Object Definition Tools .......................................................................................... 178

V

validation stamp................................................................................................................... 16Value field ......................................................................................................................... 166Value Lenght ....................................................................................................................... 99Value Type .......................................................................................................................... 99variable .............................................................................................................. 130, 135, 143Variable ............................................................................................................................... 95variable object ............................................................................................................... 3, 143variables ............................................................................................................................ 110View options...................................................................................................................... 157VL ....................................................................................................................................... 99VT ....................................................................................................................................... 99

W

WARM state...................................................................................................................... 161workstation ............................................................................................................................ 1writing an attribute............................................................................................................... 10


MicroSCADA

ABB Automation

X

XB........................................................................................................................................ 68XM....................................................................................................................................... 70XT........................................................................................................................................ 71XV ....................................................................................................................................... 71

Y

YM....................................................................................................................................... 66YT........................................................................................................................................ 67

Z

ZD.................................................................................................................................. 35, 36ZE ........................................................................................................................................ 35Zero Deadband..................................................................................................................... 35Zero deadband supervision Enabled .................................................................................... 35ZT ...................................................................................... 25, 87, 92, 99, 113, 122, 134, 150


MicroSCADA

ABB Automation

Customer Feedback

About This Chapter

This chapter contains information on how to send customer feedback and how to gettechnical support from the SA Help Desk.

Customer Feedback Database

Customer Feedback is a Lotus Notes database, using which ABB companies can re-port errors, make improvement proposals and queries related to products manufac-tured by ABB Substation Automation Oy. Customer Feedback database is connectedto the change management system of ABB Substation Automation Oy, which handlesall error corrections and improvements made to the products.

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

Writing A Customer Feedback Report

When writing a Customer Feedback report, the following general instructions shouldbe taken in consideration:

• Write the report in English.

• Write only one error report, query or improvement proposal in a Customer Feed-back report.

• If you are reporting an error, try to isolate the error as well as possible. Describethe sequence of events and actions that lead to the error. If any error messages orother debug information is provided by the system, please write it down. Includealso information of the system, e.g. a system diagram, revision information andconfiguration data.

• If you are making an improvement proposal, try to describe how the improvedfunction should work and avoid providing solutions. Information about the im-portance of the improvement, e.g. number of projects that require the improve-ment, helps us to make the decision whether and when the improvement should beimplemented.

To make a Customer Feedback report, select Feedback Report from the Create menu.This opens an empty Customer Feedback document. Fill out the fields listed below. Aquestion mark next to a field provides help for filling out the field.

1 Subject. This should contain a short description of the issue. A more detailed de-scription can be given in the Description of Feedback field below.

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

3 Customer Information.


1MRS751253-MEN

ABB Automation

4 Reporting Information. This should contain detailed information of the product thereport is about.

5 The person who you want to send the feedback to and whether you want to get areply from that person.

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

7 Category.

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

Actions

When ABB Substation Automation Oy receives a Customer Feedback report, it isanalysed by a sales person or a representative of the technical support. The analysermay ask for additional information in order to completed the analysis. After the reporthas been analysed, one of the following actions is taken:

• In case of a clear error, the report is moved to the change management system ofABB Substation Automation Oy. In this system, the error is analysed in detail andcorrected in a future patch release or major release depending on the severity andimpact of the error.

• In case of an improvement proposal, the report is also moved to the change man-agement system, where it is taken as a requirement to future releases.

• In case of a query, an answer is provided.

When Customer Feedback reports are handled in the change management system, theoutcome can be one of the following:

No Actions It is decided that the report re-quires no further action. If, for ex-ample, the problem is caused by aconfiguration error, it belongs tothis category.

Will be implemented in patch/current release This result means that the correc-tion or new feature will be avail-able in the next official programrelease.

Moved to future release This result means that the newfeature will be available in somenew program release in the nearfuture.

SA Help Desk

ABB Substation Automation Oy provides a technical support service called SA HelpDesk to support local engineering centres in their system projects. The purpose of SAHelp Desk is to provide support for urgent issues such as:

• Year 2000 issues.

• High-priority issues concerning systems at customers’ sites.


MicroSCADA

ABB Automation

For other kind of technical support, please use the Customer Feedback database. SAHelp Desk is available every day from 06:00 to 21:00 Central European Time.

SA Help Desk can be contacted by telephone. The number is:

+358 50 334 1900

Documents

1MRS751253-MEN MicroSCADA Issue date: 29.02.00 · PDF fileThe information in this document is subject to change without ... Each application has its own directory branch on ... activation