notice 1 notice 2 - abb group · this manual should be read when you start working with microscada...

1MRS751852-MUMIssued: 15.03.2002Version: AProgram revision: 8.4.4

We reserve the right to change data without prior notice.

Introduction to MicroSCADA Technology

Product Guide

MicroSCADA

Notice 1

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

Notice 2

This document complies with the program revision 8.4.4.

Notice 3

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

Trademarks

Microsoft is a registered 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 Corporation.

MicroSCADA Technology Manuals

SYS 500 manuals

COM 500 manuals

Application Objects 1MRS751848-MEN

Introduction to MicroSCADA Technology 1MRS751852-MUM

JAVA-API for MicroSCADA 1MRS751851-MEN

Programming Language SCIL 1MRS751849-MEN

SCIL-API for MicroSCADA 1MRS752199-MEN

Status Codes 1MRS751850-MEN

System Configuration 1MRS751846-MEN

System Objects 1MRS751847-MEN

Configuring MicroSCADA for OPC DA Client 1MRS752246-MEN

Installation 1MRS751853-MEN

Picture Editing 1MRS751854-MEN

System Management 1MRS751857-MEN

Visual SCIL Objects 1MRS751856-MEN

Visual SCIL User Interface Design 1MRS751855-MEN

COM 500 Engineering 1MRS751858-MEN

Connecting LONWORKS Devices to MicroSCADA 1MRS751845-MEN

Communication Programming Interface (CPI) 1MRS751859-MEN

Configuring MicroSCADA for DNP V3.00 Master Protocol 1MRS751860-MEN

Configuring MicroSCADA for DNP V3.00 Slave Protocol 1MRS751861-MEN

Configuring MicroSCADA for IEC 60870-5-101 Master Protocol 1MRS751862-MEN

Configuring MicroSCADA for IEC 60870-5-101 Slave Protocol 1MRS751863-MEN



Configuring MicroSCADA for IEC 60870-5-104 Slave Protocol 1MRS751965-MEN

Configuring MicroSCADA for Modbus Master Protocol 1MRS752242-MEN

Configuring MicroSCADA for Modbus Slave Protocol 1MRS751864-MEN

MicroSCADAIntroduction to MicroSCADA Technology

Product Guide

1MRS751852-MUM

LIB 500 manuals

LIB 510 manuals

SMS 510 manuals

CAP 505 manuals

Common manual for LIB, CAP and SMS

LIB 500 Configuration Manual 1MRS751880-MEN

LIB 500 Operator’s Manual 1MRS751885-MUM

LIB 510 Configuration 1MRS751886-MEN

LIB 510 MV Process Configuration 1MRS751887-MEN

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

LIB 510 Operator’s Manual 1MRS751888-MUM

SMS 510 Installation and Commissioning 1MRS751897-MEN

SMS 510 Operator’s Manual 1MRS751898-MUM

CAP 505 Installation and Commissioning 1MRS751901-MEN

CAP 505 Operator’s Manual 1MRS751902-MUM

Relay Configuration Tool Tutorial 1MRS751903-MEN

Relay Mimic Editor Configuration 1MRS751904-MEN

Relay Configuration Tool Quick Start Reference 1MRS751905-MEN

SPTO Configuration Tool 1MRS751906-MEN

Protocol Editing Tool 1MRS751982-MUM

Tools for Relays and Terminals 1MRS752008-MUM

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADAProduct Guide

12345

1 Introduction

2 MicroSCADA technology

3 SYS 500 system server

4 Communication systems

5 LIB 5xx application libraries

MicroSCADAIntroduction to MicroSCADA Technology

Product Guide

1MRS751852-MUM

MicroSCADAContentsProduct Guide

Contents:

1MRS751852-MUM Introduction to MicroSCADA Technology

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

2. MicroSCADA technology ..........................................................32.1. General .........................................................................................32.2. MicroSCADA technology products ................................................32.3. MicroSCADA system description ..................................................5

2.3.1. Hierarchical and flat systems .............................................62.3.2. Single-user and multi-user systems ...................................62.3.3. Single and redundant systems ...........................................7

3. SYS 500 system server .............................................................93.1. General .........................................................................................93.2. Base system ................................................................................103.3. Applications .................................................................................113.4. Databases ...................................................................................11

3.4.1. Process database ............................................................113.4.2. History database ..............................................................133.4.3. Report database ..............................................................14

3.5. Programming with SCIL ..............................................................143.5.1. Objects .............................................................................15

3.5.1.1. User interface objects ........................................153.5.1.2. Application objects .............................................153.5.1.3. System objects ...................................................16

3.5.2. Attributes ..........................................................................173.5.3. Visual SCIL ......................................................................183.5.4. Visual SCIL objects ..........................................................18

3.6. Graphical user interface ..............................................................183.6.1. Pictures ............................................................................19

3.7. Base tools ...................................................................................203.7.1. System configuration tools ...............................................213.7.2. Application object tools ....................................................213.7.3. User interface tools ..........................................................223.7.4. Accessory tools ................................................................23

3.8. Peripheral equipment ..................................................................24

4. Communication systems ........................................................254.1. General .......................................................................................25

4.1.1. Upper level communication ..............................................264.1.2. Process communication ...................................................264.1.3. Network topologies ..........................................................27

4.2. COM 500 communication server .................................................284.3. Communication front-ends ..........................................................304.4. NET unit ......................................................................................32

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADAContents Product Guide

4.5. Communication system components .......................................... 334.5.1. Communication software ................................................. 334.5.2. Networks .......................................................................... 344.5.3. Communication hardware ................................................ 35

4.6. Process units .............................................................................. 36

5. LIB 5xx application libraries .................................................. 375.1. Application engineering .............................................................. 375.2. Application libraries ..................................................................... 38

1MRS751852-MUM MicroSCADA 1. Introduction


Product Guide

1

1MRS751852-MUM

1. Introduction

This manual belongs to the MicroSCADA technology 8.4.4 manuals.

This manual should be read when you start working with MicroSCADA for the first time. The content of the manual is the basis for the rest of the manuals, as it gives introduction to MicroSCADA technology.

In revision 8.4.4 MicroSCADA manuals are divided into the following three categories:

• MicroSCADA technology manuals. These manuals provide information common to all MicroSCADA products.

• SYS 500 manuals. These manuals provide information related to SYS 500 system server.

• COM 500 manuals. These manuals provide information related to COM 500 communication server.

Using this manual

This manual introduces MicroSCADA, its components and their functions. It contains general information related to the MicroSCADA system, technology, workstations, applications and graphical user interface.

Chapters

The manual contains the following chapters:

• Introduction gives information about the intended use of this manual.

• MicroSCADA Technology contains an overview of the MicroSCADA Technology products and system types.

• SYS 500 System Server describes the SYS 500 system server, its components and their features.

• Communication Systems describes the functionality of a NET unit. COM 500 and communication front-ends are also described.

• LIB 5XX Application Libraries contains an overview of the system engineering process.

1

1MRS751852-MUM MicroSCADA 2. MicroSCADA technol-

ogy


Product Guide

2

1MRS751852-MUM

2. MicroSCADA technology

The needs for better information and control of electric utility power networks are increasing. To meet these needs, MicroSCADA Technology provides solutions that lead into greater efficiency, reliability and cost effectiveness.

2.1. General

MicroSCADA is a microcomputer-based, programmable and distributed supervisory control and data acquisition (SCADA) system. Microcomputer-based means that MicroSCADA runs on every commercially available PC-computer.

MicroSCADA is programmable because all application programs and most system configuration programs are built with SCIL (Supervisory Control Implementation Language). More information on SCIL is found in Section 3.5.1.

The system can be seen as a network where the control system can communicate with the widely distributed process through a communication system.

The common platform technology, which MicroSCADA is based on, is used for building applications and systems. SYS 500, COM 500 and LIB 510 are examples of MicroSCADA Technology products.

MicroSCADA-based electrical application areas are power transmission and distribution. It is also well suited for other process areas. District heating, water purification and distribution, waste water treatment, oil and gas distribution can be mentioned as non-electrical application areas.

The main MicroSCADA-based application systems are Substation Automation Systems for power transmission and distribution substations. There can also be Network Control and Distribution Management Systems for power distribution. Therefore, this manual focuses on that area.

2.2. MicroSCADA technology products

Product hierarchy

The MicroSCADA Technology product hierarchy is shown in Figure 2.2.-1

3

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADA2. MicroSCADA technology Product Guide

�� !�� "��

MicroSCADA Technology products are divided into two product families: system products and application libraries. System products are the core components of the system. Different LIB packages are application libraries (described in Chapter 5). Different product families can be used together. Some products require other MicroSCADA products, some can be used alone (e.g. COM 500 and SYS 500).

System products

A system product, consisting of SYS 500 System Server, communication system and operator workstation, contains the necessary hardware and software for running applications and handling communication between the components in the system. SYS 500 is described in Chapter 3 and communication systems are described in Chapter 4.

Operator workstation

An operator workstation is a computer that is used for controlling and supervising the process (it shows pictures and dialogs). It can be integrated into SYS 500 System Server, or reside in a separate computer that is connected to a base system computer. A laptop computer can also serve as a workstation. It is then connected to the control system over a dial-up line. The workstation computer can also be connected to a local area network (LAN) with a modem.

��

��

��

SYS 500[Systemserver]

CommunicationSystems

[Operator]Workstation

LIB 5xx[Application

libraries]

TechProd.CNV

COM 500[Communication

Server]


Frontend]


Frontend]

RemoteWorkstation

LocalWorkstation

LIB 500base

LIB 510

LIB 520

LIB 530

LIB 580

4


ogy


Product Guide

2
The computer that serves as an operator workstation can also be used for other purposes than as an operator workstation.
An operator workstation consists of a computer, an operating system, workstation programs, HSI (Human System Interface) and printers.The MicroSCADA HSI consists of a display, keyboard and mouse.

Workstation programs

Workstation programs are a set of programs that are used for process supervision and control. It enables the use of a MicroSCADA Notification Window, which shows system messages, and MicroSCADA Monitor Starter. The MicroSCADA Monitor Starter opens MicroSCADA monitors.

MicroSCADA monitors

A MicroSCADA monitor is used to supervise and control a MicroSCADA application on screen. It enables interaction between the operator and the base system computer. The monitor may be of Visual SCIL or X-monitor type. MicroSCADA monitors are always connected to SYS 500. The pictures and dialogs displayed on a screen of another computer are always stored in the SYS 500 System Server. The monitor may run remotely on an operator workstation and office computer via LAN, or remotely on a portable workstation via a dial-up modem or a GSM mobile phone connection.

Basic functionalities of SYS 500 System Server, e.g. process communication and reporting, do not require that MicroSCADA monitors are open. The application runs without them.

2.3. MicroSCADA system description

A MicroSCADA system is a system where MicroSCADA Technology products are used. It can contain one or more computers that are connected to each other in order to exchange data or pictures.

There are several ways to build a MicroSCADA system. It might contain one or several base systems, NET units, operator workstations, process units and peripheral equipment. Different commonly used system configurations are described here. An example system overview is shown in Figure 2.3.-1.

5

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADA2. MicroSCADA technology Product Guide

��#��

2.3.1. Hierarchical and flat systems

The difference between a hierarchical and a flat system is that a hierarchical system has several layers of system components, while a flat system has only one. The hierarchical system contains a multi-user system or a redundant system that is connected to one or more single-user systems through a serial line. A flat system could be, for example, a single-user system and a SYS 500 connected to the process units.

2.3.2. Single-user and multi-user systems

Both the single-user system and the multi-user system contains SYS 500. The single-user system has one local MicroSCADA monitor and NET unit. A modem may be used for communication with process units. In a multi-user system one or several operator workstations are connected to SYS 500 (usually through LAN). A communication front-end may also be connected to the system. The communication front-end increases the number of communication lines.

The NET unit that is connected to the single-user system increases the amount of available protocols and COM ports. It also eases the load of the base system computer.

More information on SYS 500 can be found in Chapter 3.

Operatorworkstations

SYS 500System servershot stand-by

COM 530

R

�

I

63$&�� &

SubstationAutomationSystem

COM 500

RedundantCommunicationServers(front ends)

Process unitsProtection relays

SubstationAutomationSystem

DistributionTerminal unit

Communicationgateway

LAN

COM 500

Remoteworkstation

Officenetwork

system.CNV

MicroSCADA System Overview

R

R

6


ogy


Product Guide

2

2.3.3. Integrated and distributed systems

Both the integrated and the distributed systems contain SYS 500 with all its components. The system components (a communication system and a workstation) can be optionally integrated to it in an integrated system. The distributed system contains, in addition to SYS 500, a communication frontend or an operator workstation.

2.3.4. Single and redundant systems

A single system is a MicroSCADA system that contains only one unit of each system component, while a redundant system can contain two base systems, and/or two NET units and/or two LAN connections dedicated for the same purpose. The idea with a redundant system is to make the system more safe when doubling some of its components. In most systems, the component availability is very important. This means that if one of the system components fails, the other one takes over the specific functions immediately after it has recognised a break-down in the other base system.

7

1MRS751852-MUM MicroSCADA 3. SYS 500 system

server

Introduction to MicroSCADA technology

Product Guide

3

1MRS751852-MUM

3. SYS 500 system server

About this chapter

This chapter gives an introduction to the SYS 500 system server and its components.

3.1. General

The SYS 500 system server is a PC based programmable automation system. The computer where SYS 500 runs is called the SYS 500 computer. This computer may be called the main computer. You may use SYS 500 with or without a HSI, which in this case could be a monitor (see Figure 3.1.-1).

��#�� $ �%&&��' (�

Task

The SYS 500 system server runs the operating system Windows NT and MicroSCADA software. SYS 500 contains the necessary hardware and software needed for communication between the different units. The computer that functions as the SYS 500 system server can be considered as the main computer. The system server contains data acquisition, supervising and controlling functions.

Features

Operational features of the system server:

• Control and supervision of the process (based on pictures, dialogs, windows and function keys, and event driven or cyclical application programs).

• Alarm and event handling.

• Flexible reporting system based on advanced calculations.

• Access to all process and system data according to the user rights.

• Support for multiple applications.

• Possibility to on-line documentation and data entry.

• Multi-user support.

• Printouts.

• Data exchange through common interfaces.

Components

The software in the SYS 500 system server is:

SYS 500 withintegrated HSI

SYS 500SYS500_HSI.CNV

9

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADA3. SYS 500 system server Product Guide

• Windows NTTM1 4.0 operating system (NT server or NT workstation)

• Base system software

• Base tools

• Application software

• Hummingbird eXceed version 5.1.3 when a distributed HSI is included in the system

The communication system and the operator workstation can be integrated in SYS 500 (see Figure 3.1.-2).

��#�� $ �%&&��

3.2. Base system

The base system collects all process related data, via the NET communication units, from the process units and stores the data in the process database. The collected information is then distributed for e.g. HSI-displays, archiving, calculations, printouts and for further processing and distribution in other systems. In a corresponding way, control commands are sent from the process database to the process units. The control commands can come from e.g. an operator through the HSI, an automatic function or some other system. The process database reflects the real time picture of the process.

The base system runs the application (See Figure 3.2.-1). The base system functionality is always the same, no matter how the application is used. The base system services are configured and accessed by SCIL. For more details on SCIL, please see Section 3.5.1.

1. Windows NT is a registered trademark of Microsoft Corporation.

SYS 500System Server

Base system Databases Base tools Application Operating system PC

SYS500_system_server.CNV

10


server


Product Guide

3

��#�� )�� $ �%&&�� *��"�� +

The base system also offers an application-programming interface for attaching functions as separate programs.

3.3. Applications

The customer needs and operational functions in the process define together what the application will be like. This means that the application software specifies the user interface and the SYS 500 system server functionality.

The application software consists of:

• pictures and dialogs

• process-, history- and report databases

• control programs

• configuration files etc.

Application engineering means adjusting MicroSCADA so that it suits a specific application. Application engineering can be performed by using a standard application library, LIB 500, or programming SCIL.

The application functions are all placed on an application software layer. This layer can be changed without affecting the base system, which executes the application. Several applications can be run at the same time, because each application has an own process to supervise and control. The application may either have own connections to process units or share the connections with other applications. Different applications may communicate with each other.

3.4. Databases

Each application contains a process database, a history database and a report database. The process database is used for process supervision, the report database for data storage, calculations, automatic activation and so on. The history database is used as a base for the event list. These three databases are described in detail in the following sections.

3.4.1. Process database

The process database contains application objects. It registers incoming and outgoing process data signals. It is a real-time database containing process objects,

11


scales and free type objects. Process communication from and to the base system passes through the process objects. The information flow is shown in Figure 3.4.1.-1.

��#�,�� (�� "�-��"��

Event

An event is an indication that something has happened in the system. Typical events are changes of object values, alarms or warnings, or alarm definitions. Events can cause printouts, automatic control operations, event lists and report database registrations.

The event list displays events that have occured in the system. It also informs about activities by other users, operations of objects, acknowledging alarms, editing of limit values and so on. With LIB 500 you can define own filters with the event list tool, depending on what kind of information you want in the event list. One or several criteria may be used to filter out unwanted information from the event list.

Alarm

Alarms are generated when something special has occured in the process. (An alarm is prioritised in the event list.) Alarms can cause audio-visual alarms, changes in the station picture, alarm pictures, alarm printouts and alarm lists. Information about alarming objects is stored in the alarm buffer. The information remains in the buffer until the reason for the alarm disappears or until the alarm is acknowledged.

The alarm list shows all the alarms that appear in the system alarm buffer. The alarm list is divided into two different lists: one with persisting (active) alarms and one

HistoryDB

ReportDB

Communication system

Process units

Process

Event listEvent andAlarm printout Alarm Alarm list Actions

ProcessDisplay

Trends andReports

Infoflow2.CNV

ProcessDB

12


server


Product Guide

3

with fleeting (inactive) alarms. An alarm is usually presented with a text that explains the reason of the alarm. The information flow is shown in Figure 3.4.1.-2.

Alarms and events can be generated in three different ways:

• Process events can generate alarms. The state of the process is evaluated in the base system, according to the limits that have been set. For example, if a measured value exceeds the predefined limits, an alarm will occur.

• The system itself can generate internal alarms from diagnostic programs, which supervise the MicroSCADA system components. An alarm will occur, if there are system communication errors, e.g. if a printer error occurs.

• System alarms are generated by an external module. This module can be considered as a system watch dog. System alarms of this type cannot be included in the alarm list.

Other devices in the MicroSCADA system can also generate alarms.

��#�,�� .� �� "��

3.4.2. History database

Events are stored in the history database as event history. The history database consists of the history database files which each contain events of one day. The history database is the base for event lists made by LIB 500 Base revision 4.0.2. or newer. Each event in the history database contains most of the process object attributes and some history database specific attributes.

Event EventEvent Event

Evaluation

Alarmif the event is critical

Alarm list

Actionsbased on alarm

Alarms2.CNV

13


3.4.3. Report database

The report database stores historical data and calculated values. It also contains SCIL programs that are executed based on time or events. The report database contains data objects, command procedures, time channels and event channels.

Report data in the report database needs to be handled mathematically or statistically. When data is collected from different sources, SCIL algorithms are used for data analysis and calculations. The data is then stored in the report database. The reports can be operational reports, alarm and event reports, trends etc.

Figure 3.4.3.-1 shows how data is put in the report database and how it is then analyzed.

��#�,�#��

3.5. Programming with SCIL

MicroSCADA programming is done with SCIL, which is a high-level application programming language. SCIL programs, which are created in the SCIL editor, contain statements that tell the system what to do. The programs can be in pictures, command procedures, Visual SCIL dialogs and in dialog items. Because MicroSCADA is built with SCIL, you can find SCIL in all MicroSCADA applications. Please note that SCIL is only used in MicroSCADA.

Like most other languages, SCIL includes features such as variable assignments, arithmetics, conditions, block structure, case statements, loops, etc. SCIL is an interpreted language but a SCIL compiler is also provided.

SCIL commands consist of:

14


server


Product Guide

3

• commands (e.g. !SHOW.., #SET.., #ON.. etc.)

• objects (e.g. process objects)

• expressions (e.g. TIMES, SECOND, CLOCK)

• variables (e.g. @variable, %variable)

• names (e.g. picture- and dialog names)

There are three types of SCIL commands. Picture commands always begin with “!”, full graphic and motif commands begin with “.” and manoeuvre commands begin with “#”.

When you have written a new SCIL program you can check the syntax directly in the editor, instead of testing your program in the tool menu and recognising a syntax error there. Syntax errors are identified by specific error codes and their explanations can be found in the Status Codes manual (1MRS751850-MEN). An example of a SCIL program is shown below:

;show the trend basket dialog!WIN_NAME FORMAT/BASKET!WIN_BG_COLOR FORMAT/BASKET ("M",1)!WIN_POS FORMAT/BASKET (10,15)!WIN_PIC FORMAT/BASKET F_USE/FTU_BASKB!SHOW FORMAT/BASKET

Predefined functions

SCIL contains a large number of powerful predefined functions for various types of data processing. For example, the following important categories of functions are available in SCIL:

• Arithmetical functions

• Time functions

• Database functions

• File handling functions

3.5.1. Objects

MicroSCADA has an object-oriented environment. An object is a programmable entity that presents something. In MicroSCADA an object presents process units, system functions or SCIL programs. Objects are defined by their attributes. The following three objects types: user interface objects, application objects and system objects, are described in this section.

User interface objects

The user interface in a MicroSCADA system is the content of the MicroSCADA monitor. The user interface object is an object that forms an application user interface. Pictures, Visual SCIL dialogs and dialog items are user interface objects. They are programmed and controlled with SCIL. The user interface object types are organised in pictures and Visual SCIL Objects. The user interface is described in details in Section 3.6.

3.5.1.1. Application objects

Application objects are programmable units, which perform various tasks such as real time process supervision, control procedures, data registration and storage,

15


calculations, automatic time and event activation. Application objects are created, accessed, modified and deleted with SCIL and application object definition tools.

Application objects include, for example, the following types:

3.5.1.2. System objects

System objects are programmable units that define the configuration and communication in a MicroSCADA system. There are two kinds of system objects: base system objects and communication system objects. These two kinds of objects, define the MicroSCADA system configuration together with the PC-NET unit configuration data. With SCIL, system objects are accessed through their attributes.

• Scales Algorithms for changing values from the process units to values that are used in the base system. The algorithms may be one-to-one, linear or stepwise linear. Several process objects may use the same scale.

• Data objects These register and store sampled or calculated data. Every registered value has a time stamp and a status code which describes the value quality. Data objects are used for storing trends, energy value history, system configuration data, optimisation, calculation, estimations of energy values etc.

• Command procedures These are SCIL programs that can be executed automatically or manually. They can be used for all kinds of automatic operations like calculations, control operations, report printouts, configurations etc. They are used e.g. for automatic operations at system start-up.

• Time channels Time channels are used e.g. for starting programs or data registrations automatically. Actions are started based on time definitions (e.g. one hour). A time channel can start several actions. If the same channel starts several actions, they are started in priority order. A time channel is generally activated at predefined times, either at a certain time or at specified intervals.

• Event channels Event channels are used for automatically starting data registration and program execution or activating time channels. They are typically activated after process events, which appear as changes in the process object values. The event channels transmit information on process events from the process database to report database where they activate operations.

• Event objects Event objects start automatic updating in pictures, based on events. The event objects can be activated automatically or manually. They have no attributes.

• Variable objects Variable objects are temporary lists of attributes and attribute values, used in SCIL programs.

• Process objects Process objects are real-time images of process units, such as breakers, disconnectors, switches, relays, detectors, sensors or controllers. They store information related to the process.

Generally, each input and output connection in process units is represented by a process object in a process database. These are organised in groups. A group consists of a number of indexed process objects with the same logical name. The objects are typically related to the same process unit.

Most of the process database functionality is based on process objects. They supervise signals from process units and control signals that are sent to them. They contain process data, which is the object value, and various information related to the data. Attributes store the related information.

16


server


Product Guide

3

Base system objects handle the configuration of the base system. They also define the logical connections to NET units, other base systems and applications. With the base system objects you modify the base system configuration and the logical connections to other devices. Every base system has its own base system objects.

Communication system objects and their attributes specify the NET configurations. They also give the NET an image of communication lines and communication devices connected to them. Communication system objects handle the process communication.

3.5.2. Attributes

An attribute describe the properties of an object and information associated with it. Attributes describe object values, functions, properties and activities. An object normally has many different attributes. Each attribute can be defined with SCIL. Different object types have different sets of attributes.

Static and dynamic attributes

Attributes can be divided into configurable and dynamic attributes. See Figure 3.5.2.-1.

• Configurable attributes define the identification and properties of the object. Examples of configurable attributes of an object are the object name, object address, activation criteria, connections to other objects and alarm handling. Values of configurable attributes can be changed with SCIL or object definition tools.

• Dynamic attributes represent object values and some additional information related to the value, such as the status code and the time tag. Dynamic attributes usually change based on process events.

��#�%�� "/��"�� "��

Attributes of a process object

Changing the object value of a process object that represents an output controls a process unit.

The updated process object value is stored with additional information. For example, the occurence time is stored. Updating can be done with SCIL. Process events can also lead to an update. Updating may lead to the following actions:

• Alarm related activities

• Printouts

17


• Updating in pictures

• Event channel activation

• Event object activation

• Data registration

3.5.3. Visual SCIL

Visual SCIL is an object-oriented Windows look-and-feel graphical programming environment. Visual SCIL dialogs are programmed using methods. Methods, except some predefined and pre-programmed methods, are SCIL programs.

Methods define the dynamic operation of Visual SCIL dialogs and dialog items. Each dialog and dialog item has its own set of methods. Methods can be executed cyclically, after certain user operations or certain events. Some methods can be executed by a method called in SCIL.

Editable methods are programmed in the SCIL program editor, which is accessed from the Dialog Editor.

3.5.4. Visual SCIL objects

There are about 40 Visual SCIL objects that can be used for building graphical user interfaces.

Visual SCIL object types

Visual SCIL objects can be grouped into the following main types:

• Container Group Objects. This group contains dialogs and dialog items which can contain other dialog items. The objects are containers, picture containers, menus, notebooks and notebook pages.

• Other Dialog Items (for example a button).

• Images.

Buttons, texts, menus and images are called dialog items in a dialog.

Creating Visual SCIL objects

Dialogs are generally designed and programmed with the Dialog Editor, utilising the extensive set of included Visual SCIL objects, such as texts, buttons, lists, numeric spinners, combo boxes, check boxes, menu bars and notebooks. Visual SCIL objects can be loaded from files or be created by SCIL statements in pictures and dialogs.

Dialog boxes

Visual SCIL objects, for example, dialogs are mostly used when creating tools for application engineering purposes. The objects are shown in dialog boxes, which first show the main dialog or a picture container. The main dialog and all the dialogs opened within it, or from items included in the picture, belong to the same dialog system.

3.6. Graphical user interface

The graphical user interface of SYS 500 system server is composed of pictures and dialogs. Pictures are dynamic illustrations containing a static background, dynamic

18


server


Product Guide

3

windows and function keys. Pictures are suitable for process illustrations and controlling the process.

Dialogs made with Visual SCIL are mainly used for creating tools that are used in the application engineering. Dialogs and other VS objects are shown to the user on screen in dialog boxes.

3.6.1. Pictures

The operator uses pictures to supervise and control the process. A picture visualises a controlled process with different symbols and colors.

Picture components

A picture is composed of picture components, e.g. the picture background, picture windows, function keys, picture programs and picture functions. The picture background contains graphics, which are static, unchanging parts of the picture.

Picture windows are dynamic parts of the picture that can be shown, erased and replaced without any impact on other picture components. Windows may show complete pictures, text or data, figures or graphs. You can place them anywhere in the picture, even in a way that they overlap one another.

Function keys are rectangular programmed areas. When you click a function key, a program or a data entry is executed. Programs define the behaviour of the picture.

When a standard function is installed from a library, a copy of it is added into a picture as a picture function.

A picture function is a set of picture components, which may include all the components mentioned above. The picture components are shown in Figure 3.6.1.-1. A picture may contain picture windows which can contain pictures as well. It may also contain a number of picture functions, which are also constructed as pictures.

��#�0�� 1�� 2��.�� 2��

19


3.7. Base tools

Base tools make it easier to use a MicroSCADA system. For example, configurations can be made by using SCIL commands, but the system tools makes the configuration procedure easier.

Tools are used for building, modifying and viewing system and application components. They are used for the following tasks:

• Editing pictures and dialogs.

• SCIL programming.

• Managing application objects, for example viewing, modifying and creating them.

• Testing application functionality.

• Creating, modifying and viewing system objects.

• Searching text strings from SCIL programs, pictures and text files.

The tools can be divided into the following groups:

• User interface tools

• Application tools

• System tools

• Accessory tools

These groups are described with more details in the following sections. The tools can be opened from the Tool Manager (see Figure 3.7.1) where different tools are found on different tool pages.

The tool pages can easily be modified. You can change the names of the pages, add new tool pages (and delete them), move tools from one page to another, insert new tools etc.

20


server


Product Guide

3

��#�3�� "��

3.7.1. System configuration tools

System configuration tools are used to specify system objects and attributes, and functions that are related to the objects. Font Setting, Color Setting, Date/Time Settings, Base System Configuration and System Configuration tools are examples of the system tools.

3.7.2. Application object tools

Application tools are used to define objects, attributes and other features, which are closely related to an application and its functionality. On the Application Objects tools page, you find the Object Navigator and the Doc./Export tool. Application tools are a set of application object definition tools and an object navigator.

With the object navigator you can view object lists, access definitions for different objects, add, copy and delete objects. The Process Object Definition tool (Figure 3.7.2.-1) is, for example, found in the Object Navigator. It is used to define process objects of the predefined types.

21


��#�3�� 4"/��2�� 4"/��5��

User interface tools

User interface tools are mainly used to define the graphical user interface of an application or a tool. User interface tools are e.g. the dialog editor, the picture editors (full graphic and semi graphic), the text translation tool and the representation library editor (full graphic and semigraphic).

The picture editor is used to design and program pictures. It contains separate modes for designing picture background, picture functions, function keys and picture windows. When picture components are edited, different tools can be opened. For example, the Window Editor can only be opened when the window tool is chosen. Pictures can be created from the beginning, when the project engineer creates graphics and functionalities. Since the same kind of graphics and functionalities are needed for many applications, some pre-made picture functions can be taken from application libraries. The Picture Editor is shown in Figure 3.7.2.-2.

Please note that there is a difference between pictures and figures in MicroSCADA. A picture is dynamic and contains e.g. buttons, windows and programs, while a figure is a static picture that is included in the dynamic picture, e.g. the picture background.

The Representation Library Manager is used to copy or move a representation from one library to another one. The Representation Library Editor is used to edit the

22


server


Product Guide

3

features of the picture windows that cannot be edited in the Window Editor. You can also create new representations by simply copying the old ones.

��#�3�� 1��6��

The Dialog Editor is used to create Visual SCIL dialogs. A new dialog can be added into a file or an existing dialog can be edited. The Dialog Editor includes geometry management facilities and enables translation of texts.

The Text Translation Tool enables translating texts in all tools and dialogs (or the texts in LIB 5XX Application Libraries pictures) into local languages.

3.7.3. Accessory tools

Accessory tools, which are mainly used in the system engineering, are found on the Miscellaneous page in the Tool Manager. The SCIL Program Editor, Test Dialog, DB <--> Text Tool and Search Tool are examples of accessory tools.

The SCIL Program Editor is an accessory tool, which is a text editor that is especially developed for editing SCIL programs. It can be opened from several other tools when SCIL programs should be edited. You can, of course, open the editor from the Tool Manager when you want to create and edit a text file. The SCIL Program Editor includes a number of useful features. For example, it enables cutting, copying and pasting program lines as well as searching and replacing text. A program can be copied to and from an ASCII file.

The Test Dialog is used to execute SCIL command lines to find out values for variables of different data types. You can also save the Test Dialog outlook at exit, create some procedures and start them.

23


3.8. Peripheral equipment

Printers

Up to 20 printers can be connected to a base system, either directly or through LAN. The printers can be of various types, e.g. transparent printers, matrix printers and laser printers. In addition to these printers, the ones defined in the operating system can be accessed by MicroSCADA.

Each printer has a unique printer number, which can be associated with a certain task. For example, the task can be an alarm and event printout, hard copy, historical reports and so on. A printer can be programmed to take over the tasks of another printer automatically.

Printouts can be produced automatically or manually. The printout layout can be customised. The main printout types are logs, reports, hard copies and documents. Logs are automatic printouts based on process events. The logs can be directed to one or several printers.

Alarm devices

The MicroSCADA alarm unit is a normal computer card with a cable connection card. The cable connection card has two outputs. The first output is connected to a standard MicroSCADA alarm panel, which contains alarm class specific lights and push buttons for light and sound acknowledgement. The second output can be connected to 8 alarm devices.

24

1MRS751852-MUM MicroSCADA 4. Communication sys-

tems


Product Guide

4

1MRS751852-MUM

4. Communication systems

4.1. General

Information needs to be transmitted between the SYS 500 system server and process units. In some cases information from the process units needs to be transmitted to the network control centers as well. Commands sent from the network control centers to process units need to be transmitted in the same way. The data transmission is a task for the communication system. The process unit protocol is often different from the network control center protocol. This is why a protocol conversion is needed.

��,�� "��

The communication system also handles the communication between other devices in the MicroSCADA system, for example, between two system servers or two communication servers.

The communication can be divided into upper level communication and process communication. See Figure 4.1.-2. Some protocols used for communication are shown in the picture.

25

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADA4. Communication systems Product Guide

��,�� "��5��*5��-��+2� � �* �"�� +��"��

4.1.1. Upper level communication

Upper level communication means communication between the process units, the substation control system and the network control center. There can be a SYS 500 system server or a third-party system in the network control center.

The upper level communication is usually an asynchronous serial communication that uses telephone lines, radio links or power line carriers as the physical media.

4.1.2. Process communication

Process communication is the communication between the substation control system and the protection and control devices connected to the physical process. In case there is no substation control system, the protection and control devices are connected directly to the network control system, usually by data concentrators or remote terminal units (RTUs). The protection and control devices are usually connected to each other and the communication is thus called a process bus or field bus.

Because of electromagnetic disturbances caused by the primary electric process, optic fibres are mostly used as communication media in the process communication. The communication line is usually faster than the one used in the upper level communication due to the larger quantity of data.

26


tems


Product Guide

4

4.1.3. Network topologies

Most of the communication protocols implemented in MicroSCADA are so called master-slave protocols. The master is the primary station controlling the data requests and sending the command. The slave is the secondary station sending data to the master, either when requested or spontaneously, and executing commands sent by the master.

Some protocols, for example DNP V3.00, also support so called peer-to-peer communication, which means that slaves can communicate directly with each other. The number of masters and slaves connected to one communication line is limited by the protocol used. In practice the limitation is set by required performance and response. The more devices are connected to one line, the more bandwidth the communication requires.

There are several possibilities how to connect the master and the slave, or slaves. The direct topology (point-to-point) can be a direct physical cable from point-to-point or a two-node radio, or modem network. The serial bus topology (multi-drop) is commonly made up of many modems with their outputs/inputs tied together, or by using a star-coupler. Figure 4.1.3.-1 illustrates these network topologies.

��,��#�� 1��"��

A special type of a multi-drop communication is a communication loop, which is described in Figure 4.1.3.-2. A communication loop is a type of multi-drop communication where the line forms a loop. This means that there is always an alternative line leading to a node, even if a line is broken. Redundancy is achieved without duplicating the lines.

27


��,��#�� -�� 2��

4.2. COM 500 communication server

General

COM 500 is a communication server, which provides gateway services for routing the data flow between the process and network control systems. The data transfer usually involves protocol conversion. It also handles system co-ordination tasks, such as dynamic assignments of the control command authorities. See Figure 4.2.-1.

COM 500 supports a variety of protocols for connecting upper level systems, like some network control centers. It is typically connected to the network by some telecontrol protocol, for example RP 570. Different devices such as LONWORKS

1 devices, SPA devices and RTUs can be connected to it. COM 500 sends information to one of these devices for supervising and controlling the customer process.

COM 500 is based on MicroSCADA technology, like SYS 500. It can be integrated to SYS 500 for cost savings in compact system solutions. It also offers an interface for communication diagnostics of the control system.

1. LONWORKS is a trademark of Echelon Corporation registered in the United States and other countries.

28


tems


Product Guide

4

��,�� 4�%&&��"��-��

Functional environment

Figure 4.2.-2. describes the functional environment of a COM 500 application.

��,�� 4�%&&��

Example system

COM 500 is a communication server, which runs on the MicroSCADA base system. It can utilise both the DCP-NET and PC-NET units. Several COM 510 and COM

29


530 may be connected to a COM 500 in order to increase the system performance. An example of a COM 500 system is shown in Figure 4.2.-3.

��,��# 6.� ��4�%&&��

COM 500 sees each NCC and each local process unit as a station. (The local process unit is a system object type.) The communication mainly passes through the process database.

Communication from COM 500 to the Network Control Center (NCC) is based on command procedures. The command procedures send information to the NET unit for protocol conversion and transmission. Typically one command procedure is needed for each type of data to be transferred. At start-up and after communication disturbances all specified data is transferred. When the system is running, process events generally activate the command procedures via event channels.

Commands and setpoints from the NCC to the substation are brought into the COM 500 application via process objects. The process objects activate, via event channels, command procedures, which contain actual control commands to the process units. Safety is increased by using select-before-execute commands and a two-step authority check mechanism.

4.3. Communication front-ends

A communication front-end is a computer which is especially reserved for process communication. It is connected to a base system through LAN. The communication front-end is used for increasing the number of communication lines. It can also be used for distributing the communication lines over LAN and to decrease the load of the SYS 500 computer.

A communication front-end can contain either PC-NET or DCP-NET units. Usually a communication front-end is equipped with a display and other operator workstations facilities. An example of components in a communication front-end is shown in Figure 4.3.-2. Components that can be found in a communication front-end are DCP-NET software, a DCP card, COM ports and MFL.

MFL or base system software can be the supporting software in a communication front-end. MFL is message routing software used for loading DCP-NET software to

30


tems


Product Guide

4

DCP cards. It also serves as a communicator between the base systems and NET software.

COM 510 communication front-end

COM 510 is a DOS based computer, containing 1-4 DCP-NET units and MFL. Needed hardware is a DCP card from Emulex. COM 510 is connected to a base system through LAN. The base system is to be found in SYS 500 system server or in COM 500 communication server. See Figure 4.3.-1.

��,�#�� .� ��4�%�&��

COM 530 communication front-end

COM 530 is a Windows NT based computer containing 1-2 DCP-NET units and/or a PC-NET unit with the base system software dedicated to message routing. See Figure 4.3.-2.

��,�#�� .� ��4�%#&��

31


4.4. NET unit

The NET unit consists of NET software and communication hardware that is needed to run it. The NET unit can be placed in a base system computer or in a communication front-end. For example, PC-NET software with a PCLTA card is considered as a NET unit. The NET unit also includes configuration data of the unit itself, the lines and the connected devices. Event and alarm printers may also be connected to the NET unit.

The NET unit is used to increase the amount of available protocols and COM ports, and also to decrease memory consumption and processor load of the base system computer.

Task

The task of the NET unit is to convert external protocols to an internal protocol of MicroSCADA, which is used in the communication between the MicroSCADA nodes (base systems) and the NET units. The external protocol is used for communication with process units. This way devices and systems can be connected to MicroSCADA by using several communication protocols.

In addition, NET units handle the following tasks:

• Message routing between physical devices and applications in the base systems.

• Diagnostic supervision of connected devices and lines.

NET unit types

MicroSCADA has two types of communication units, DCP-NET and PC-NET. DCP-NET consists of a DCP-NET software running on a specific Emulex board, whereas PC-NET is a program running on the base system computer.

DCP-NET unit

The DCP-NET unit is a NET unit containing DCP-NET communication software and a DCP card. It can be either an external or an internal NET unit. The Internal NET unit is placed in the base system computer, which means that it is in the same computer as COM 500 or SYS 500. Two DCP cards can be placed into the base system computer.

The external NET unit is in a communication front-end. There can be four DCP cards in a communication front-end. The DCP card has 8 NET lines that can be connected to process units or other devices.

PC-NET unit

PC-NET communication software is similar to the communication software of the DCP-NET unit. It runs on the main processor of a Windows NT computer in parallel with the MicroSCADA Kernel. The PC-NET unit can be placed in the base system computer or in a communication front-end.

For communication with the LonTalk®2 protocol the PC-NET unit uses a PCLTA card. (PC LonTalk Adapter). For communication it also uses COM ports. The COM

2. LonTalk is a trademark of Echelon Corporation registered in the United States and other countries.

32


tems


Product Guide

4

ports of the base system may be used, but they are often needed for other communication purposes. An additional multi-port serial card may be used.

4.5. Communication system components

The communication system contains communication software, communication hardware and networks.

4.5.1. Communication software

Communication software includes protocols, protocol environment software, supporting software, operating system and devices.

Protocols

Every-day transmission involves, besides the communication hardware, also logical agreements, i.e. protocols. Protocols are a set of "traffic rules" and conventions for sending information in the network. They govern the content, format, timing, sequencing and error control of messages.

Transmitted data is coded according to the protocol rules. Protocols are very important when it comes to the communication in a system.

SPA, RP 570 and LonTalk are examples of master protocols that can be used for process communication in a MicroSCADA system. Communication between the base system and communication front-ends is based on the internal protocol of MicroSCADA. Slave protocols are used for communication between the NET units and network control centers.

Protocol development software

CPI (Communication Programming Interface) is a protocol development software that is used for implemented protocols in MicroSCADA environment. It is a collection of functions that help to convert between the internal protocol of MicroSCADA and some other protocols. An application program, which exchanges data between MicroSCADA and a foreign system, can be made by using CPI. The communication between a CPI application program and MicroSCADA base system is based on TCP/IP network.

Supporting software

Supporting software is needed for running communication software. It can be either a MFL or a base system. The base system is used as the supporting software when PC-NET is used in a COM 530 communication front-end. (MFL is described in Section 4.3.)

Operating system and device software

An operating system can be either Windows NT or DOS. In COM 500 or SYS 500 the operating system is always Windows NT. Device software contains e.g. different programs that are used to handle communication with a LMK device, SPA device or printer. The software uses point definitions in the NET unit, for example, for LONWORKS or SPA points.

33


4.5.2. Networks

LAN, LONWORKS network and serial lines can be used for communication in a MicroSCADA system.

LAN

LAN (Local Area Network) is a network used in a geographically small area, for example, inside a company. In a MicroSCADA system, LAN is usually used for communication between the base system, front-ends and workstations, and for upper level communication. It has a large capacity for data transmission. Usually TCP/IP (Transmission Control Protocol/Internet Protocol) is used for data transmission in LAN networks. TCP/IP provides communication across the connected networks of computers, with several protocols.

LONWORKS network

LONWORKS network is a network where LonTalk is used for communication in distributed networks. With the LONWORKS communication technology it is possible to build a protection and control system including more than one network control center, NCC. The NCCs receive status values, measurements and time-tagged events from process units. LONWORKS network is built around a star-coupler, which connects other devices into a star form.

��,�%�� .� ��)21725.6��-

34


tems


Product Guide

4

Serial lines

Serial transmission of data can be used for upper level and process communication. Usually it is used when communication cannot be realized in a LAN network. The serial transmission passes through the COM ports of the computer.

4.5.3. Communication hardware

Communication hardware includes protocol hardware, connection cards and supporting hardware.

Protocol hardware

Protocol hardware is needed to run the protocols. It can be either a PC or a DCP card.

Connection cards

Connection cards are used to handle communication between base system and external nodes. They are communication hardware that can be placed in the base system computer. For example PCLTA card or Multiport serial card are connection cards. PC-NET software uses PCLTA card (PC LonTalk Adapter) or Multiport Serial card to communicate.

PCLTA card is an ISA bus card. Two NET lines can be connected to it and to the LONWORKS network. Multiport serial card is a connection card inside the computer. Its purpose is to extend the amount of COM ports that can be used for communication.The COM ports of the computer can be used for other tasks.

Supporting hardware

Supporting hardware is communication hardware outside the NET unit. It can be e.g. a modem, a network card, a fallback switch or a time synchronisation device.

A modem is a device that converts the computer’s digital signals to analog signals before transmission. Thus, one data transmission needs two modems, one at each end of the line.

Network cards are used for connecting a computer to a network, for example to a LAN network. For redundant LAN, a special type of network card is needed.

A fallback switch is a card that is used to switch a serial line to another one (e.g. with redundant front-ends). This means that it changes, for example, the secondary DCP-NET unit to a primary DCP-NET unit.

Time synchronisation means that the time in the internal clocks of the MicroSCADA system are synchronised. The time can also be changed so that it is the same as an external time source. An external time source can be for example:

• GPS (Global Positioning System), which is normally used for satellite based navigation

• Radio clock

• Device in upper level system, e.g. a network control system

Clocks in a base system and in a communication front-end are often synchronised.

35


4.6. Process units

Process units are devices in the process. They collect data from the process and execute orders from the base system. Process units can, be for example, REx, SPA, or LMK device or RTU. The process units are handled as stations inside the MicroSCADA system. The concept RTU was also previously used for the process unit.

Process units can be divided into primary devices and secondary devices. Process devices are called primary devices. The devices needed for automation are called secondary devices. For example, breakers and disconnectors are primary devices and relays are secondary devices. See Figure 4.6.-1.

��,�0�� .� ��8�� 8�� "�� "��

36

1MRS751852-MUM MicroSCADA 5. LIB 5xx application

libraries


Product Guide

5

1MRS751852-MUM

5. LIB 5xx application libraries

5.1. Application engineering

Application engineering means the process of customising MicroSCADA for a user by creating an application which contains supervisory control functions. The application can also contain pictures, dialogs, SCIL programs and necessary object definitions. See Figure 5.1.-1.

The picture editor, the application object definition tools, the application libraries and SCIL programming are used for application engineering. Application libraries provide a fast application engineering of standard solutions, while SCIL programming allows a variety of applications, even extreme specialisation.

Application engineering can be some of the tasks mentioned below.

• Creating the user interface by using the picture editor, application libraries and dialog editor. Installation and configuration of standard functions is done in the picture editor.

• Creating and defining application objects. Application objects are defined in the picture editor or in the application object definition tools.

• Programming additional and other picture functionalities. This is mainly done by using the SCIL editor.

• Programming other functionalities, for example, supervisory control and calculation functions.

These tasks are generally done in parallel. Simultaneous display of several MicroSCADA pictures in separate MicroSCADA monitors can be done on the same screen. This means that system control, application engineering, maintenance and operation can be done at the same time.

��%�� 6��"��

37

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADA5. LIB 5xx application

librariesProduct Guide

5.2. Application libraries

Application libraries are MicroSCADA Technology products that contain a set of standardised application functions. The libraries can be used for fast application engineering of standard solutions. They include standard functions, which are installed to the picture. Objects connected to various functions are created automatically when standard functions are installed into the picture. Process object attributes are also given default values.

Standardised application functions can be, for example, alarm and event lists, single line diagram components or specific tools and process unit specific tools and functions. SCIL programming can be used, if standardised application functions cannot solve specific customer requirements.

Customer applications can be built by installing and configuring functions from application libraries, for example, from LIB 510.

LIB 5xx application libraries

LIB 5XX is a set of application libraries, which contain the following products:

• LIB 500 Base, which is a platform for other support packages (LIB 5xx), containing several backbone functions. It also provides event and alarm lists, busbar coloring and system self-supervision.

• LIB 510, which provides application functions for monitoring and controlling medium voltage process.

• LIB 520, which is mainly intended for high voltage applications.

• LIB 530, which is intended for medium and high voltage applications.

• LIB 580, which is also a high voltage library.

Which application library to select, depends on what process devices are used in the system. Each product center provides an application library for its own protection and control products.

Standard functions can be tools dedicated to certain protection terminals for parameterisation or disturbance collecting. They can also be used in station pictures, e.g. like the Medium Voltage components in LIB 510. The LIB 510 support package is mainly intended for products like SPACOM, RED 500 etc.

Standard functions are copied from the application libraries. The copy is installed to a station picture and configured to fit a specific process. A lot of time is saved when working this way, since the standard functions are already tested and their reliability is high. Another benefit with the standard functions is that they are continuously developed and kept up-to-date.

38

MicroSCADAIndexProduct Guide

Index

1MRS751852-MUM Introduction to MicroSCADA Technology

Page�

Accessory Tools ............................................................................................................. 23Alarm ............................................................................................................................. 12�� ....................................................................................................................... 241�� .......................................................................................................................... 249�� ............................................................................................................................. 24

Application�� ............................................................................................................................ 36�� ..........................................................................................................11, 37)�"�� .......................................................................................................... 4, 37, 384"/�� ....................................................................................................................... 15 �� ...................................................................................................................... 11�� ........................................................................................................................... 21

Attributes ....................................................................................................................... 17

�

Background ................................................................................................................... 19Base System .................................................................................................................. 10Base Tools ..................................................................................................................... 20

�

COM 500 ....................................................................................................................... 28COM 510 ....................................................................................................................... 31COM 530 ....................................................................................................................... 31COM Ports ..................................................................................................................... 32Common platform technology ......................................................................................... 3Communication�� ................................................................................................................6, 30'�� .............................................................................................................32, 35)�� ........................................................................................................................... 271�� (�� .............................................................................................. 33 �� ......................................................................................................................... 28 �� ...................................................................................................................... 33

Configurable Attributes ................................................................................................. 17Connection Cards .......................................................................................................... 35Container Group Objects ............................................................................................... 18CPI ................................................................................................................................. 33

�

Data Transmission ......................................................................................................... 25Database ........................................................................................................................ 11DCP-NET Unit .............................................................................................................. 32DCP-NET unit .................................................................................................. 29, 30, 32Device Software ............................................................................................................ 33Diagnostic programs ...................................................................................................... 13Dialog6�� ......................................................................................................................... 18(�� ........................................................................................................................... 18

Direct topology .............................................................................................................. 27Distributed System .......................................................................................................... 7Dynamic Attributes ....................................................................................................... 17

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADAIndex Product Guide

�

Event ............................................................................................................................. 12External Time Source .................................................................................................... 35

�

Fallback Switch ............................................................................................................. 35Flat system ...................................................................................................................... 6Full graphic command .................................................................................................. 15Function Keys ............................................................................................................... 19

�

Gateway ........................................................................................................................ 28GPS ............................................................................................................................... 35Graphical User Interface ............................................................................................... 18

�

Hierarchical system ......................................................................................................... 6History Database ..................................................................................................... 11, 13HSI (Human System Interface) .............................................................................5, 9, 10

Information Flow .......................................................................................................... 12Integrated system ............................................................................................................ 7Internal NET unit .......................................................................................................... 32

LAN ........................................................................................................................30, 34Laptop computer ............................................................................................................. 4LIB 500 Base ................................................................................................................ 38LIB 510 ......................................................................................................................... 38LIB 520 ......................................................................................................................... 38LIB 530 ......................................................................................................................... 38LIB 580 ......................................................................................................................... 38LIB 5XX ....................................................................................................................... 38Local Area Network (LAN) ...................................................................................... 4, 34LONWORKS Network ................................................................................................. 34

�

Main computer ................................................................................................................ 9Methods ......................................................................................................................... 18MFL .............................................................................................................................. 30Microcomputer-based ..................................................................................................... 3MicroSCADA�� 1�� ............................................................................................................... 24�� 9�� ................................................................................................................. 24��"�� .................................................................................................................... 11�� ........................................................................................................................ 5�� ............................................................................................................ 51�� ....................................................................................................................... 4 �� .......................................................................................................................... 5�� ................................................................................................................... 3��1�� .................................................................................................... 3

Modem .......................................................................................................................... 35

1MRS751852-MUM MicroSCADAIndex


Product Guide

Motif command ............................................................................................................. 15Multi-drop network topology ........................................................................................ 27Multiport Serial Card ..................................................................................................... 35Multi-user system ............................................................................................................ 6

�

NCC ............................................................................................................................... 26NET �� ...................................................................................................................... 329�� ............................................................................................................................. 329�� .................................................................................................................. 32

Network�� .......................................................................................................................... 35�� .................................................................................................................. 27

Networks ....................................................................................................................... 34

Object ............................................................................................................................ 15Object Navigator ........................................................................................................... 21Operating System .......................................................................................................... 33Operator Workstation ...................................................................................................... 4Optic fibres .................................................................................................................... 26

�

PCLTA card .............................................................................................................32, 35PC-NET unit ..................................................................................................... 29, 30, 32Peer-to-peer communication ......................................................................................... 27Picture:�-�� ................................................................................................................ 19�� ................................................................................................................... 15�� ................................................................................................................ 196�� ......................................................................................................................... 22�� ..................................................................................................................... 197�� ..................................................................................................................... 19

Pictures .......................................................................................................................... 18Point-to-point network topology ................................................................................... 27Predefined Functions ..................................................................................................... 15Primary Devices ............................................................................................................ 36Printers ........................................................................................................................... 24Process�� ............................................................................................................................ 3�� .......................................................................................................... 25��"�� ..............................................................................................................10, 114"/�� ....................................................................................................................... 309�� ........................................................................................................................... 36

Product�� ........................................................................................................................ 4'�� ..................................................................................................................... 3

Program Editor .............................................................................................................. 23Protocol ......................................................................................................................... 33�� ...........................................................................................................25, 32'�� ................................................................................................................... 35

1MRS751852-MUMIntroduction to MicroSCADA TechnologyMicroSCADAIndex Product Guide

�

Redundant system ........................................................................................................... 7Remote Terminal Unit (RTU) .................................................................................26, 28Report�� ........................................................................................................................... 14��"�� .............................................................................................................. 11, 14

�

SCIL ..........................................................................................................................3, 14SCIL Program Editor .................................................................................................... 23SCS ................................................................................................................................ 26Secondary Devices ........................................................................................................ 36Serial:�� .............................................................................................................. 27)�� ........................................................................................................................... 35�� .............................................................................................................. 35

Single System .................................................................................................................. 7Single-user system .......................................................................................................... 6Standard Functions ........................................................................................................ 38Standardised application functions ............................................................................... 38Station ........................................................................................................................... 30Supporting'�� ................................................................................................................... 35 �� ...............................................................................................................30, 33

Syntax error ................................................................................................................... 15SYS 500 Components ................................................................................................... 10SYS 500 Computer ......................................................................................................... 9SYS 500 System Server .................................................................................................. 9System4"/�� ......................................................................................................................... 161�� ....................................................................................................................... 4 �� ........................................................................................................................... 9�� ........................................................................................................................... 21

�

TCP/IP ........................................................................................................................... 34TCP/IP network ............................................................................................................. 33Telecontrol Protocol ...................................................................................................... 28Test Dialog .................................................................................................................... 23Text Translation Tool .................................................................................................... 23Time Synchronisation ................................................................................................... 35Tool Manager ................................................................................................................ 20Transmission Control Protocol/Internet Protocol ......................................................... 34Two-node network ........................................................................................................ 27

�

Upper Level Communication ........................................................................................ 25User(��4"/�� ......................................................................................................... 15(�� ........................................................................................................... 22

�

Visual SCIL ................................................................................................................... 18Visual SCIL Objects ................................................................................................15, 18

1MRS751852-MUM MicroSCADAIndex


Product Guide

�

Workstation ...................................................................................................................... 4Workstation Programs ..................................................................................................... 5

�

X-monitor type ................................................................................................................ 5

notice 1 notice 2 - abb group · this manual should be read when you start working with microscada...

Documents