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

MicroSCADA Pro SYS 600 *9.1

System Configuration

Configuration Manual

MicroSCADA Pro SYS 600 *9.1 System Configuration Configuration Manual

1MRS751846-MEN

MicroSCADA Pro

SYS 600 *9.1

Issued:

26.03.2003

Version:

E/18.03.2005

System Configuration

Configuration Manual

1. About this manual

7

1.1. Copyrights

7

1.2. Trademarks

7

1.3. General

7

1.4. Document revisions

8

2. Introduction

9

2.1. System description

9

2.2. Configuration principles

14

3. Base system object definitions

17

3.1. Overview

17

3.2. Configuration files

18

4. Communication system object definitions

27

4.1. Overview

27

4.2. Defining communication system objects off-line

28

4.3. Defining communication system objects on-line

29

5. Configuration data files

35

5.1. General rules

35

5.2. Frontend configuration parameters

36

6. Base systems

41

6.1. Configuring a base system

41

6.2. Communicating applications

45

7. MicroSCADA networks

51

7.1. Global

definitions

51

7.2. Object

numbering

53

8. Local area networks (LANs)

55

9. Process communication system

57

9.1. Configuring a communication unit (NET)

57

9.2. Internal NETs (DCP-NETs)

61

9.3. Configuring base systems with PC-NET

63

9.4. Communication frontends

65

9.5. Networks of interconnected NETs

69

10.Operator workstations

77

11.Peripherals

79

11.1.Printers

79

11.2.Other peripherals

85

12.Configuring stations

12.1.General principles

87

87

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

12.2.Stations using ANSI X3.28 protocol

89

12.2.1.MicroSCADA configuration

89

12.2.2.SRIO configuration

96

12.3.S.P.I.D.E.R. and Collector RTUs

99

12.3.1.MicroSCADA configuration

99

12.3.2.RTU configuration

102

12.4.Stations in the LONWORKS network

102

13.Mirroring

105

13.1.Functional overview

105

13.2.Technical overview

105

13.3.Configuration

114

13.3.1.Example 1. One host, one image

115

13.3.2.Example 2. Two hosts, redundant image

117

13.3.3.Example 3. Station mapping in a mirroring system

119

13.3.4.Example 4. Local mirroring

121

13.3.5.Example 5. Hierarchical mirroring

122

14.Redundancy configurations

125

14.1.Hot stand-by base systems

125

14.1.1.Base system configuration procedure

127

14.1.2.Editing SYS_BASCON.HSB

127

14.1.3.NET configuration

135

14.1.4.Installing watchdog application

135

14.1.5.Starting the shadowing

136

14.1.6.Editing the command procedures

136

14.1.7.An example hot stand-by configuration

139

14.2.Redundant frontends

144

14.3.Communication loops

151

14.4.Hot stand-by with OPC client and servers

154

15.Miscellaneous

161

15.1.System message handling

161

15.2.Auto-dialling

164

15.3.Time synchronization

166

15.4.Storing the event history

168

15.4.1.History database

168

15.4.2.Event log

169

16.System Configuration Tool

171

16.1.Main functions

171

16.2.Starting the tool

172

16.3.How to handle the object and attribute trees

172

16.4.How to save a configuration from a former release

173

16.5.How to create a new configuration

173

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

16.5.1.Methods for adding new objects

174

16.5.2.Adding a redundant line

175

16.6.Default configuration

176

16.7.On-line configuration

177

16.8.How to change the attribute values

179

16.8.1.NET Node Station address

180

16.9.How to take a configuration in use or out of use

180

16.10.How to delete an object

182

16.10.1.How to delete a redundant line

182

16.11.Cut, copy and paste functions; reallocating stations

182

16.12.Preview function

184

16.13.User-defined programs

184

16.14.General object handling command

186

16.15.Environment

187

16.16.System Self Supervision with Monitor Classic

187

16.17.System Self Supervision with Monitor Pro

190

16.17.1.Supervision

Application Objects

191

16.17.2.Supervision

Monitoring

192

16.17.2.1.Proposed SA symbols

192

16.17.2.2.Dynamics

193

16.17.2.3.Base System Supervision

197

16.17.2.4.Monitor Classic Supervision

198

16.17.2.5.Communication

199

16.17.2.6.Communication Line

200

16.17.2.7.Station

201

16.17.2.8.LON Clock Master

202

16.18.Signal engineering

203

16.18.1.Signal engineering on station level

203

17.NETCONF Tool

187

17.1.Requirements

187

17.2.Installation

187

17.3.NETCONF tool basics

187

17.4.Using NETCONF Tool

190

18.NET Tool

197

18.1.NET Tool basics

197

18.2.Using the NET PRECONFIGURATION Tool

199

19.REx Configuration Tool

205

19.1.Using REx Configuration Tool

205

19.2.Defining the device

207

20.LMK Configuration Tool

211

20.1.Using LMK Configuration Tool

211

20.1.1.Defining the device

214

21.Index

217

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

1.

About this manual

1.1.

Copyrights

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

In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Oy be liable for incidental or consequential damages arising from use of any software or hardware described in this document.

This document and parts thereof must not be reproduced or copied without written permission from ABB Oy, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose.

The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license.

Copyright © 2005 ABB Oy All rights reserved.

1.2.

Trademarks

Registrations and trademarks used in this document include:

Windows: Registered trademark of Microsoft Corporation.

LonWorks: Registered trademark of Echelon Corporation Inc.

1.3.

General

This manual gives you information on the various configuration settings that you have to make in order to take your MicroSCADA system in use. It also describes how to use the configuration tools, which are available in the current release.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

1.4.

Document revisions

Version

Revision number

Date

History

A

8.4.4

15.03.2004

Document created

B

8.4.4

26.03.2004

SYS_CONFIG.PAR and SYS_BASCON.COM updated in Chapter 2

     

Chapter 12, Mirroring added

C

8.4.5

15.01.2004

Internal mirroring and hierarchical mirroring added in Chapter 12

     

Adding a redundant line added in Chapter 15

     

Windows NT changed to Windows

D

9.0

30.06.2004

Document updated

E

9.1

18.03.2005

Additions, System Self Supervision and HSB features

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

2.

Introduction

This chapter introduces the MicroSCADA system concepts and the system configuration principles:

2.1 The first section provides a summary of the MicroSCADA system with emphasis on the concepts which are central when configuring MicroSCADA: the base systems, the process data communication system, the connection of devices to a distributed network, etc.

2.2 The MicroSCADA configuration principles: the MicroSCADA configuration software modules and the configuration software management.

2.1.

System description

A MicroSCADA system is composed of one or more base systems, a process

communication system, workstations and peripherals. In addition, it may utilise local area networks (LANs). See Figure 2.1.-1.

Base systems

The MicroSCADA base systems are control centres that contain the supervisory control and monitoring functions of MicroSCADA. The tasks of a base system are

to collect all process-related data from the stations into the process database,

distribute the information and to send control commands via the NET communication units.

Each base system is composed of a base system computer including base system software. The base system computer is a standard PC running the Windows operating system. The MicroSCADA base system software comprises the MicroSCADA kernel, a number of facility programs, engineering and system handling tools, configuration software and application software.

The MicroSCADA kernel, as well as most of the engineering and system handling tools, is the same in all base systems independently of the application area and the extent of use.

The configuration software is specified for the base system in question and adapted

to the device configuration of the entire MicroSCADA system.

A base system may contain one or more applications. An application includes

application software and databases. The application software specifies the functions

of the MicroSCADA base system as a supervisory control system. The application

software is adapted for a certain process and for the user’s needs regarding the level

of information, user interface, control operations, and so on. A base system can run

several applications in parallel.

Process communication system

The process communication system connects the application software in the base systems with the process stations which gather process data, and performs the control commands. In addition, it may interconnect several base systems, as well as base systems and printers.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

The process communication is handled by a number of parallel or serially interconnected communication units, also called NETs. A NET is a communication program running on a special communication board (board based NETs or DCP NETs) or directly on the CPU of a PC (PC based NETs or PC NETs). The NETs may be situated within the base system computers and within PCs specially assigned for process communication. Such PCs are called frontends or communication frontends.

LANs

LANs may be used for connecting base systems with other base systems, base systems with frontends, and base systems with workstations.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

MicroSCADA System Overview PCs containing workstation programs Operator Workstations Local Area Network (LAN)
MicroSCADA System Overview
PCs containing workstation programs
Operator
Workstations
Local Area
Network (LAN)
Operator workstation
Printers
Alarm unit
Base System computer
Base System Software
Application Software
- Kernel (main program)
- Pictures, dialogs
- Engineering tools
- Report data
Base Systems
- Base System Configuration
- Process data
-
Application software
- Control programs, etc.
and
Peripherals
DCP-NET units:
-
Communication card
- NET program
-
Communication program
incl. conf parameters
- Configuration file
Process
Communication
System
Communication frontends
- Communication card
- Communication program
incl. conf parameters
System_overview.eps

Fig. 2.1.-1

The main system components of MicroSCADA

Workstations

A MicroSCADA workstation is a PC that runs the MicroSCADA HSI (Human System Interface). To be able to run the HSI, the workstation must run an X Server program.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

The workstations are connected via LAN or via remote connections, which use the operating system feature RAS.

Peripherals

The printers are connected to the base system computers, to a LAN via printer servers, or to the process communication system.

External alarm units can be connected to the base systems.

Radio clocks for external clock synchronization may be connected to the base systems, to NETs, and to the frontends.

MicroSCADA networks

Figure 2.1.-2 shows an example of a MicroSCADA system. The system can be regarded as a network where the communication units (NETs) and the base systems function as routing nodes, which can forward messages and data from one node or device to another. All base systems connected by the same process communication system or by a LAN belong to the same network.

There may be several communication units in a series between two communicating devices. However, for performance reasons, it is not recommended to have more than three communication units between communicating devices. In a large network, the routes between nodes can be doubled to obtain redundancy.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

Pro System Configuration Configuration Manual SYS 600 *9.1 Fig. 2.1.-2 An example of a MicroSCADA network.

Fig. 2.1.-2

An example of a MicroSCADA network. Most configuration possibilities are represented in this network, which will be used as an example throughout this manual.

Interoperability

An essential feature of MicroSCADA is the interoperability between separate base systems. Interoperability means that all the connected applications can communicate, if they are situated in the same base system or in separate base systems. In Figure 2.1.-2, for instance, all applications can intercommunicate. Communication between the base systems 2 and 3 requires some special arrangements in base system 1.

The connected devices - printers, workstations and process units - can be shared by several base systems in the network. The workstations connected to a LAN, for example, can be used by all base systems connected to the same LAN. Likewise, the

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

stations and printers connected to NETs can be used by all base systems connected to the same network of interconnected NETs. A frontend can recognise up to four base systems.

In the network of Figure 2.1.-2, for example, all the applications in base systems 1 and 3 can utilise the workstations on the LAN. The PCs running X software can be connected to several base systems and applications simultaneously. Application 5 can use both printers 1 and 2. A redirection of printout can be done during operation.

2.2.

Configuration principles

For a MicroSCADA system to operate properly, it must be configured for the special environment in which it is operating. MicroSCADA contains configuration software in the form of objects and data files. The configuration software defines:

• Nodes

• Applications

• Device connections

• Communication properties

• Memory capacities, destination addresses, etc.

The System Configuration Tool manages the configuration of the base system and the PC-NET. In the current version, the following base system and system objects can be created and configured:

• Integrated link to the PC-NET

• PC-NET

• LonTalk (LON), IEC, RP 570, RP 571, LCU500, DNP 3.0, Modbus and SPA protocol Lines

• REX, LMK, IEC, SPI, LCU500, DNP, PLC, and SPA Stations

• LON Clock Master and LON Star Coupler

Configuration software

The MicroSCADA configuration software is composed of objects and data that reside in the base systems, communication units (NETs) and communication frontends, see Figure 2.2.-1:

• Each base system contains a set of base system objects that specify the base system itself and its environment. During the operation, the base system objects reside in the primary memory of the base system computer. The base system objects are created with SCIL commands, when the MicroSCADA base system is started. They can be added and modified during the operation.

• Each communication unit contains a set of system objects that specify the unit itself and its environment. During the operation, the system objects reside in the memory of the communication boards (DCP-NETs) or PC (PC-NETs). The NET programs contain a preconfiguration, which gives the system objects default values. The system objects can be added and modified during the system operation.

• The communication frontends contain data files, which specify the frontend configuration and the parameters for the communication with the base system.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

The process units (stations) contain their own configuration definitions that must be regarded in the MicroSCADA configuration. For some station types, the configuration can be built in MicroSCADA and downloaded to the stations.

The MicroSCADA configuration software handling is detailed in Chapter 2 of this manual.

Building system configuration

As a rule, when a device is added to the MicroSCADA system, several configuration modules are affected. For example, when a process unit (station) is connected to a NET, additions and modifications are required in:

• The base system which will use it: base system objects

• The communication unit to which it is directly connected: system objects

Concerning PC-NET and LONWORKS network, the configuration work is done with the System Configuration Tool. It automatically gives default values which can be changed, if needed.

The MicroSCADA system configuration can be changed any time. However, in some cases a shut-down and restart is required for the changes to become valid.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

Pro System Configuration Configuration Manual 1MRS751846-MEN Fig. 2.2.-1 The communication server COM 500 is described in

Fig. 2.2.-1

The communication server COM 500 is described in the COM 500 Engineering Manual.

The configuration software modules in MicroSCADA

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

3.

Base system object definitions

This chapter describes the definition of the base system objects. It contains the following two sections:

3.1 An overview of the base system objects and the alternatives for defining base system objects.

3.2 A description of configuration files SYS_CONFIG.PAR, SYS_BASCON.COM and NET_BASCON.COM. These files define the initial configuration of the base system during the MicroSCADA start-up.

The base system objects and their attributes are detailed in the System Objects manual.

3.1.

Overview

Base system objects

Each base system has a set of base system objects which specify the base system and its environment, the hardware and software of the base system, the physical and logical connections of the base system and its applications. A base system is completely configured by the following base system objects:

• A SYS object for the base system itself.

• An APL object for each application residing in the base system ("local applications") and an APL object for each communicating application residing in connected base systems ("external applications").

• A MON object for each MicroSCADA monitor that will be opened to supervise an application in the base system.

• A LIN object for each connection link. A LIN object is neither needed for peripherals, nor for workstations.

• A NOD object for each directly or indirectly connected base system and NET unit (optionally also for each communication frontend).

• A PRI object for each printer, including both real printers and pseudo-printers for sending the printout to files, which will be used by the base system.

• A STA object for each connected station (connected through one or more NETs) (recommended in all cases, though not always required).

The base system object definitions and attributes, which are required for various installations, are detailed later in this manual.

Principles for defining base system objects

Generally, the base system objects are defined in the SYS_BASCON.COM file. The file is read and the commands in it are executed each time the base system is started. With a few limitations, the base system objects can also be created and modified during the MicroSCADA operation with SCIL and tool pictures.

Base system objects are created using the SCIL command #CREATE. The principles for creating a base system object with SCIL are as follows:

#CREATE object = LIST(attribute = value, attribute = value,

)

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

‘object’

The object to be created is specified using the base system object

‘attribute’

notation without attributes and index numbers Attribute name

‘value’

The value assigned to the attribute

Example:

Creating a SYS object:

#CREATE SYS:B = LIST(- SA = 209,- ND = 9,- DN = 1,- DS = "RTU",- FS = "NEVER")

After a base system object has been created, its attributes (provided that writing is enabled) can be changed with the #SET command. The objects cannot be modified with the #MODIFY command nor can they be deleted with the #DELETE command.

To learn more about the SCIL commands, refer to the Programming Language SCIL manual, Chapter 7. For more information on the base system object notation, refer to the System Objects manual, Chapter 2.

;STATION ADDRESS OF THE BASE SYSTEM ;NODE NUMBER OF THE BASE SYSTEM ;DEFAULT NET NODE NUMBER ;STA TYPES: E.G. STA,RTU,SPA,REX ;FILE SYNCH CRITERIA

On-line modifications

Most base system object attributes can be modified on-line with the Base System tool and with SCIL. These changes are not persistent and will be lost when the system is shut down. If the changes are to be persistent, they should be included in the SYS_BASCON.COM file.

3.2.

Configuration files

When the MicroSCADA program starts up, it reads the following four configuration files to set up its initial configuration:

• SYS_CONFIG.PAR contains parameter values that configure the program itself. These parameters may not be set by SCIL.

• SYS_TIME.PAR contains the history of the time zone and daylight saving time rules of the site. This file should not be modified by the user. See the Programming Language SCIL manual for details (function TIME_ZONE_RULES).

• SYS_BASCON.COM contains a SCIL program that creates the base system objects.

• SYS_NETCON.COM contains a SCIL program that loads the DCP-NET program(s) used by the system. Because DCP-NETs are seldom used any more, this file is normally not required, or it may be empty.

All these files are located in the directory \msroot\sys\active\sys_, where msroot stands for the root directory of the MicroSCADA installation, normally ‘sc’.

of the Mi croSCADA installation, normally ‘sc’. If the System Configuration tool is used, the station

If the System Configuration tool is used, the station (STA) objects are not defined in SYS_BASCON.COM. Their configuration is managed by the tool, see Chapter 15 .

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

SYS_CONFIG.PAR

The configuration file SYS_CONFIG.PAR is a text file containing settings of system parameters that cannot be set with SCIL. The file is read at system start-up before the execution of SYS_BASCON.COM. SYS_CONFIG.PAR can be edited with a text editor.

SYS_CONFIG.PAR can contain the following parameters and set values:

MEMORY_POOL_SIZE

specifies the size of the global memory pool in megabytes (MB). Possible values

, given in SYS_CONFIG.PAR, is 64 MB. For example the line:

are: 4, 8, 12, 16, 20, 24,

that is a value divisible with 4. Default, if no value is

MEMORY_POOL_SIZE = 100

sets the size of the global memory pool to 100 MB.

MEMORY_POOL_ADDRESS

specifies the start virtual address of the global memory pool. The start address (default value 30000000) should be changed (by trial and error or examining the DrWatson log) to a new value if the start of a monitor or an external program (Application Extension Program or Integrated Program) fails and the message “? Map_Global_Memory (MapViewOfFileEx): 487” is shown in the Notification Window. The address is given as an 8-digit hexadecimal number with 6 trailing zeroes. Any value between 20000000 and 6F000000 may be tried. A good value will be found quickly, if sequence 20000000, 28000000, 30000000 etc. is used. When a valid value is found, it may be used in all MicroSCADA installations running the same external programs and the same operating system configuration. The value does not depend on MicroSCADA configuration, such as number of monitors or network connections etc.

The parameter MEMORY_POOL_HOLE offers an alternative (and recommended) way of finding a valid memory pool address. It is easier to use, because the MicroSCADA program does the trial-and-error procedure.

MEMORY_POOL_HOLE

This parameter advises the MicroSCADA start-up code not to use the specified virtual memory area for the global memory pool. The parameter should be written into the parameter file only if a monitor process or an external program fails to initialize and displays an error message of the following format in the Notification Window (and SYS_ERROR.LOG):

Add the following line to sys_config.par and restart MicroSCADA MEMORY_POOL_HOLE = 30000000 - 301FFFFF

The line should be copied to sys_config.par exactly as shown in the error message. The parameter MEMORY_POOL_ADDRESS should not be touched. After the restart the program should initialize without errors. The configuration file may contain several MEMORY_POOL_HOLE lines, because there is a slight possibility that even the second start-up fails now suggesting another hole in the pool address space.

PICO_MEMORY_POOL_SIZE

REPR_MEMORY_POOL_SIZE

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

PRIN_MEMORY_POOL_SIZE

These three parameters define the sizes of the local memory pools of MicroSCADA processes:

PICO_MEMORY_POOL_SIZEDetermines the size (as megabytes) of the local memory pool of all the monitor processes in the system. The default value is 16 MB. REPR_MEMORY_POOL_SIZEDetermines the size of the local memory pool of all repr processes. The default value is 8 MB. PRIN_MEMORY_POOL_SIZEDetermines the size of the local memory pool of all prin processes. The default value is 4 MB.

Setting a pool size to 0 demands the processes of the category to always use the global memory pool.

If a process requires more memory than the specified memory pool size allows the

dialog "SCIL Application Error/Memory Pool Exhausted" is shown. The dialog shows a critical error with information about which pool caused the error. The information is either "Local memory pool exhausted" or "Global memory pool exhausted".

ANALOG_SWITCH_STATE_CLOSED (default = 1)

ANALOG_SWITCH_STATE_OPEN (default = 2)

ANALOG_SWITCH_STATE_MIDDLE (default = 0)

These parameters define the translation of the CLOSED, OPEN and MIDDLE states returned by the program interface function SCIL_Get_Switch_State.

If the SYS_CONFIG.PAR file does not exist the default values are used.

A template, SYS_CONFIG$PAR is copied to \sc\sys\active\sys_ during the

installation of the System Base Software package. The contents of the

SYS_CONFIG$PAR is:

; File: Sys_config.par

; Description: Configuration for ’static’ base system parameters

; leading ’;’ indicates commented line

; Version 9.0

;---------------------------------------------------------------

;

;MEMORY_POOL_ADDRESS

;MEMORY_POOL_SIZE

;PICO_MEMORY_POOL_SIZE

;REPR_MEMORY_POOL_SIZE

;PRIN_MEMORY_POOL_SIZE

;

;ANALOG_SWITCH_STATE_OPEN

;ANALOG_SWITCH_STATE_CLOSED

;ANALOG_SWITCH_STATE_MIDDLE

= 30000000 ;Memory pool start address = 64 ;Must be 4,8,12,16,20,24,28,

= 16 ;Memory Pool for Monitor processes

= 8 ;Memory Pool for Report processes = 4 ;Memory pool for Printer processes

(MB)

= 2 ;The semantics for MicroTOPOLOGY of AI

= 1 ;process objects used for indicating the

= 0

;state of a switching device

SYS_BASCON.COM

The system configuration of the MicroSCADA base system is defined in the SYS_BASCON.COM configuration file.The file is a text file containing SCIL statements for creating the base system (B) objects. The System Base software package contains two SYS_BASCON.COM template files, one for configuring a single base system and one for configuring a hot-stand-by base system. The template

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

file for a single base system, SYS_BASCON$COM, is during installation copied to SYS_BASCON.COM if the SYS_BASCON.COM does not previously exist. The template file for hot-stand-by systems is called SYS_BASCON.HSB.

The SYS_BASCON$COM template file defines a system configuration as presented in Figure 3.2.-1. The configuration consists of an application called “TUTOR”. Two PRI objects, one “normal” and one “transparent”, are connected to the Windows printer manager. Both objects correspond to one physical printer. A third PRI object is connected to a NET node. The fourth PRI object, PRI15, is defined as a log printer printing to a specified log file. The base system has four communication links to NET nodes. Two of the NET nodes are running on internal DCP-NET cards. One node is connected to the TCP/IP LAN link and one node, which is running the PC-NET communication software is connected over an integrated link to the base system. The configuration allows ten MicroSCADA monitors to be opened to the TUTOR-application.

MicroSCADA monitors to be opened to the TUTOR-application. Fig. 3.2.-1 The system configuration define d by

Fig. 3.2.-1

The system configuration defined by the delivered configuration software

Also the other configuration files included in the delivery (NET_BASCON.COM, the DCP-NET preconfiguration, PC_NET.CF1 and PC_NET.COM) conform with the configuration in Figure 3.2.-1.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

The contents of the SYS_BASCON$COM file is listed below. Some configuration definitions have been excluded by commenting them. They can be taken into use by removing the comment sign in front of the #CREATE command that creates the base system object.

To edit the current SYS_BASCON.COM:

1. Open the MicroSCADA Control Panel.

2. Click Admin.

3. Click Config.

The SYS_BASCON.COM file is opened in the Notepad program for editing.

;File: Sys_bascon.com ;Desription: Standard Base system configuration file

; Version 9.0

;----------------------------------------------------

;----------------------------------------------------

;Base System Object

@l_Standard_Paths = do(read_text("/STool/Def/Path_Def.txt"))

#CREATE SYS:B = List(- SA = 209,- ND = 9,- TM = "SYS",- TR = "LOCAL",- DN = 1,- DS = "STA",- DE = 0,- OP = 1,- PC = 6000,- RC = 1000,-

;Station address of base system ;Node number of base system ;Time Master, SYS or APL ;Time Reference, LOCAL or UTC ;Default NET node number ;Default STA type: E.G. STA,RTU,SPA,REX ;DDE server 0=disabled, 1=enabled ;OPC server 0=disabled, 1=enabled ;Picture Cache (kB) ;Report Cache (kB)

-

-

;MS-STOOL Settings PH = %l_Standard_Paths,- SV = (0,-

;System Variables

list(t_System_Configuration_File = "sys_/SysConf.ini",- ;System

Configuration information b_Conf_Mech_In_Use = TRUE,- ;enables/disables start-up

configuration

b_SSS_Mech_In_Use = TRUE,- ;enables/disables system self supervision routing t_Version = "8.4.3")),-

- ;Operating System events

OE = 0,-

OT = (Bit_Mask(0,1,2,3,4),- ;Application events (Bit 0=ERROR, 1=WARNING,

;1=Enabled, 0=Disabled

2=INFORMATION, 3=AUDIT_SUCCESS, 4=AUDIT_FAILURE) Bit_Mask(0,1,2,3,4),- ;System events (Bit 0=ERROR, 1=WARNING,

2=INFORMATION, 3=AUDIT_SUCCESS, 4=AUDIT_FAILURE) Bit_Mask(0,1,2,3,4)),- ;Security events (Bit 0=ERROR, 1=WARNING, 2=INFORMATION, 3=AUDIT_SUCCESS, 4=AUDIT_FAILURE)

-

FS = "NEVER") NEVER,MAINT,SET,CHECKPOINT,ALWAYS

;File sync. criteria:

;----------------------------------------------------

;Communication Links ;NOTE! Use the system configuration tool to create a link for the PC-NET!

#CREATE LIN:V = LIST(- LT = "RAM",-

;Link to DCP-NET (requires DCP driver)

;Link type

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

SD

= "RM00",-

;DCP card (first:RM00, second RM01)

RE

= "BCC",-

;Redundancy

TI

= 2,-

;Timeout length (s)

NA

= 3,-

;NAK limit

EN

= 3)

;ENQ limit

;#CREATE LIN1:B = %LIN

#CREATE LIN:V = LIST(- TCP/IP)

;Link to other SYS or LAN frontend (requires

LT

= "LAN")

;Link type

;#CREATE LIN2:B = %LIN

;----------------------------------------------------

;Node objects (NET’s and SYS’s) ;NOTE! Use the system configuration tool to create nodes for the PC-NET!

#CREATE NOD:V = LIST(-

;Node for DCP-NET

LI

= 1,-

;Link number

SA

= 201)

;Station address: 0 255

;#CREATE NOD1:B = %NOD

#CREATE NOD:V = LIST(-

LI

SA

= 2,-

= 202)

;#CREATE NOD2:B = %NOD

;Node for LAN frontend or SYS

;----------------------------------------------------

;Printers

;#do Read_Text("sys_/pr_default.dat") transparent printer below ;#CREATE PRI:V = LIST(-

; TT = "LOCAL",-

; DT = "TRANSPARENT",- ;Device type

; OJ = 1,-

; DC = "LINE",-

; CS = %CS,-

; SD = "\\My_NT\My_Printer",-

;

;#CREATE PRI1:B = %PRI

;This line is needed for the

;Transparent type printer

;Translation type

;Printer opened on job basis

;Device connection: CONSOLE, LINE OR NET

;Control sequences

;System device name

;Lines per page

LP = 66)

#CREATE PRI:V = LIST(-

TT

= "LOCAL",-

DT

= "NORMAL",-

DC

= "LINE",-

SD

= "\\My_NT\My_Printer",-

LP

= 66)

;#CREATE PRI2:B = %PRI

#CREATE PRI:V = LIST(-

TT

= "LOCAL",-

DT

= "COLOR",-

DC

= "NET",-

ND

= 4,-

;NET node number: 1

99

TN

= 1,-

;Translated object number (printer nr in net)

LP

= 66)

;#CREATE PRI3:B = %PRI

;#CREATE PRI:V = LIST(-

"EVENT_LOG" (History logging Policy)

; TT = "LOCAL",-

; OD = "LOG",-

; LL = "DAY",-

; LD = "/APL/TUTOR/PICT",- ;Log directory

; LP = 0)

;Required if HP of application is

;Output destination (LOG, PRINTER)

;Log Length (DAY, WEEK, MONTH)

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

;#CREATE PRI15:B = %PRI

;----------------------------------------------------

;Monitors

#LOOP_WITH I = 1

5

#Create MON’I’:B = LIST(-

TT = "LOCAL",- DT = "VS") @MON_MAP(%I) = -1 #LOOP_END

#LOOP_WITH I = 6

10

;Translation type ;Visual SCIL monitor

#CREATE MON’I’:B = LIST(-

TT = "LOCAL",-

;Translation type

DT = "X") @MON_MAP(%I) = -1 #LOOP_END

;X monitor

;----------------------------------------------------

;Applications

;The usage of OI & OX -attributes (required by LIB 500) @SV(15) = LIST(-

Process_Objects=LIST(-

OI=LIST(-

Title1=VECTOR("Substation"),-

Title2=VECTOR("Bay"),-

Title3=VECTOR("Device"),-

Title4=VECTOR(""),-

Title5=VECTOR(""),-

Length1=10,-

Length2=15,-

Length3=5,-

Length4=0,-

Length5=0,-

Field1=VECTOR("STA"),-

Field2=VECTOR("BAY"),-

Field3=VECTOR("DEV"),-

Field4=VECTOR(""),-

Field5=VECTOR("")),-

OX=LIST(-

Title1=VECTOR("Object text"),-

Length1=30)))

;Create Application specific global paths @l_Global_Paths = list()

;Add LIB5xx global paths to list if LIB5xx installed @t_LIB_Path_Def_File = "/LIB4/Base/Bbone/Use/Bgu_Glpath.txt" #if File_Manager("EXISTS", Fm_Scil_File(%t_LIB_Path_Def_File)) #then #block #error continue @v_File_Contents = read_text(%t_LIB_Path_Def_File) #if substr(%v_File_Contents(1),5,16) == "LIB 500 revision" and substr(%v_File_Contents(1),22,5) >= "4.0.2" #then #block #modify l_Global_Paths:v = do(read_text(%t_LIB_Path_Def_File)) #block_end #error stop #block_end

#if substr(SYS:BPR, 1, 7) == "SYS_600" #then #block ; PP

;Add SA_LIB global paths to list @t_SALIB_Path_Def_File = "/SA_LIB/Base/Bbone/Use/Bgu_Glpath.txt" #if File_Manager("EXISTS", Fm_Scil_File(%t_SALIB_Path_Def_File)) #then #block

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

#error continue @v_File_Contents = read_text(%t_SALIB_Path_Def_File) #if substr(%v_File_Contents(1),5,14) == "SA LIB version" and substr(%v_File_Contents(1),20,5) >= "1.0.0" #then #block #modify l_Global_Paths:v = do(read_text(%t_sALIB_Path_Def_File)) #block_end #error stop #block_end

#block_end

#CREATE APL:V = LIST(- TT = "LOCAL",- NA = "TUTOR",- AS = "HOT",-

;Translation Type ;Name of application directory ;Application state (COLD,WARM,HOT)

PH = %l_Global_Paths,- PQ = 15,-

-;

in COM500 Applications

-;

Needed in COM500 Applications

;Number of parallel queues/ Needed

QD = (1,1,0,0,0,0,1,1,1,1,1,1,1,1,1),- ;Parallel queue dedication/

SV = %SV,- CP = "SHARED",-

;System variable (RESERVED) ;Color Allocation Policy

RC = VECTOR("FILE_FUNCTIONS_CREATE_DIRECTORIES"),- ;Revision

compatibility HP = "DATABASE",- ;History Logging Policy ("DATABASE", "EVENT_LOG", "NONE")

-;

EE = 1,-

0=Disabled)

AA = 1,- MO = %MON_MAP,- PR = (1,2,3)) #CREATE APL1:B = %APL

;System Events & Operating System Events (1=Enabled,

;Number of APL-APL servers ;Monitor mapping ;Printer mapping

;#CREATE APL:V = LIST(- ;LIB5xx Demo Application

; TT = "LOCAL",-

; NA = "510_403_1",- ;Name of application directory

; AS = "HOT",-

; PH = %l_Global_Paths,-

; SV = %SV,-

; CP = "SHARED",-

; RC = VECTOR("FILE_FUNCTIONS_CREATE_DIRECTORIES"),- ;Revision

compatibility

; HP = "DATABASE",- ;History Logging Policy ("DATABASE", "EVENT_LOG", "NONE")

; EE = 0,-

0=Disabled)

;Translation Type

;Application state (COLD,WARM,HOT)

;System variable (RESERVED)

;Color Allocation Policy

;System Events & Operating System Events (1=Enabled,

; MO = %MON_MAP,-

;Monitor mapping

; PR = (1,2,3))

;Printer mapping

;#CREATE APL1:B = %APL

;----------------------------------------------------

;Station Types

#SET STY3:BCX = "ANSI X3-28" #SET STY4:BCX = "SPIDER RTUs" #SET STY5:BCX = "SINDAC (ADLP80 S)" #SET STY6:BCX = "P214" #SET STY7:BCX = "SINDAC (ADLP180)" #SET STY8:BCX = "PAC-5" #SET STY9:BCX = "SATTCON/COMLI" #SET STY17:BCX = "LON" #SET STY20:BCX = "LCU 500" #SET STY21:BCX = "SPACOM" #CREATE STY22:B = LIST(NA = "SPI", DB = "STA", CX = "S.P.I.D.E.R/RP570") #CREATE STY23:B = LIST(NA = "LMK", DB = "REX", CX = "LonMark") #CREATE STY24:B = LIST(NA = "ADE", DB = "STA", CX = "Ademco")

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

#CREATE STY25:B = LIST(NA = "PCO", DB = "STA", CX = "Procontic / RCOM") #CREATE STY26:B = LIST(NA = "WES", DB = "STA", CX = "Westinghouse") #CREATE STY27:B = LIST(NA = "ATR", DB = "STA", CX = "Alpha Meter") #CREATE STY28:B = LIST(NA = "PLC", DB = "RTU", CX = "PLC") #SET STY29:BCX = "IEC" #SET STY30:BCX = "DNP"

;----------------------------------------------------

;Node, Link for PC-NET & Stations

@i_Status = do (read_text("Sys_Tool/Create_C.scl"), "BASE_SYSTEM")

;----------------------------------------------------

;LAN node name of the computer @t_lan_node_name = "Basesystem1"

@i_system_node

#set nod’i_system_node’:bnn = %t_lan_node_name

= SYS:BND

;----------------------------------------------------

;Other Stations ;NOTE! Use the system configuration tool to create stations for the PC-NET!

;NET 1 (DCP-NET) stations ;#CREATE STA:V = LIST(-

; TT = "EXTERNAL",-

; ST = "RTU",-

; ND = 1,-

; TN = 1)

;#CREATE STA1:B = %STA

"RTU",- ; ND = 1,- ; TN = 1) ;#CREATE STA1:B = %STA If the MicroSCADA

If the MicroSCADA base system revision 8.4.2 or later is used together with applications that were created with earlier revisions of the base system, for example by using LIB 4.0.1, the revision compatibility switch NO_ALIAS_CHECKING should be turned on. This is done by adding "NO_ALIAS_CHECKING" to the RC attribute of the application in SYS_BASCON.COM.

SYS_BASCON.COM:

#CREATE APL:V = LIST(-

RC = VECTOR("FILE_FUNCTIONS_CREATE_DIRECTORIES" ,"NO_ALIAS_CHECKING") ,-

SYS_NETCON.COM

The default SYS_NETCON.COM file has the following contents:

;#PAUSE 10 ;@A=LOAD_DCP("SYS_NET.1MB",1,1);LOAD NET1 ON LINK 1 ;@A=LOAD_DCP("My_NET_FILE",2,1);LOAD NET2 ON LINK 2

By removing the semicolons from the file, you can make it load and start the internal communication units next time it is executed.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

4.

Communication system object definitions

This chapter describes the definition of the communication system objects. It contains the following three sections:

4.1 An overview of the communication system objects and the alternatives for defining communication system objects.

4.2 Configuring NETs off-line: the preconfiguration of the DCP-NETs and the initialization file of the PC-NETs.

4.3 Configuring NETs on-line: the principles for defining and modifying communication system objects with SCIL, defining communication system objects in the SYS_NETCON.COM configuration file and configuring NET start-up.

The communication system objects and their attributes are detailed in the System Objects manual.

4.1.

Overview

Communication system objects

Each communication unit contains a set of system objects which specify the unit itself, the line properties and connected devices etc. A NET unit is completely configured by the following system objects:

• A NET object for the definition of the NET unit itself

• A NET object for each directly or indirectly connected base system and NET unit

• NET line definitions such as line protocol, data transmission rates, etc

• An APL object for each application in the connected base systems

• A PRI object for each directly connected printer

• A STA object for each directly and indirectly connected station

Defining communication system objects

The communication system objects can be defined both off-line (the NET is out of operation) and on-line (NET in operation).

The off-line configuration comprises:

• The DCP-NET’s preconfiguration written off-line by a configuration tool, see Section 4.2.

• The PC-NET configuration with the System Configuration Tool and automatic updating of the initialization file.

• When started, the PC-NETs read an initialization file which contain the most fundamental definitions.

The on-line configuration can be done with SCIL or tool pictures as follows:

• The SYS_NETCON.COM executed at each base system start-up may contain SCIL statements for defining communication system objects.

• The communication system objects can be changed with SCIL programs started automatically or manually.

• The objects can also be changed with tool pictures.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

The on-line configuration can be read into the System Configuration Tool by selecting Configuration - Open On-line. Reading the on-line configuration sets the tool into On-line mode.

4.2.

Defining communication system objects off-line

Preconfiguration with the system configuration tool

The System Configuration Tool configures the LIN and NOD base system objects needed for the PC-NET. All configurable attributes of the LIN:B object and NOD:B object can be changed from the tool. The initialization file pc_net.cf1 is updated automatically.

Preconfiguration in DCP-NETs

The DCP-NET communication program which runs in the board based communication units contains what is called a "preconfiguration". The preconfiguration is a set-up of system objects and attributes which functions as a default configuration. Each time the NET unit is loaded and started the preconfiguration becomes valid.

The preconfiguration can be viewed, edited and documented off-line with a program called NETCONF which runs in the DOS environment or during operation from the base system by means of a preconfiguration tool picture.

Changes made in the preconfiguration come into force, when the communication program is loaded into the communication unit the next time.

The preconfiguration has the following limitations:

• A maximum of 20 stations per unit can be preconfigured

• Some attributes cannot be preconfigured

The required configuration blocks are described in this manual and the attributes are found in the System Objects manual.

PC-NET configuration with the System Configuration Tool

When a PC-NET configuration is created with the System Configuration Tool, the tool produces two data files: sysconf.ini and signals.ini. When the system is started, it reads the mentioned files and creates a pc_net.cf1 file automatically.

To create system objects, the System Configuration Tool automatically creates the file sys_base.scl, which is executed at system start-up.

After the PC-NET has started, the system executes the file sys_net.scl to configure the PC-NET. The file is automatically created by the System Configuration Tool.

Initialization file of the PC-NET

When the PC-NET program is started, it reads the initial configuration file PC_NET.CF1, which is a text file located in the SYS_ directory. It defines the basic communication nodes and addresses to enable the communication to an application

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

that will download the total configuration. The initial configuration file is composed of a number of lines, each of which specify an attribute (see below). The attributes are referred to with the notation:

object.attribute

The possible objects are:

local_node

The PC-NET itself

ext_node

An external node (the base system where the NET

ext_apl

is situated) An application in the base system where the NET is situated

In case the PC_NET.CF1 file is missing when the PC-NET is started, a default configuration becomes valid.

The following PC_NET.CF1 file is included in the MicroSCADA delivery:

local_node.sa=203 ; the station address of the PC NET

local_node.nn=3

ext_node(1).sa=209 ; the station address of the base system ext_node(1).nn=9 ; the node number of the base system

; the node number of the PC NET

ext_apl(1).nn=9

; the node number of the base system

ext_apl(1).an=1

; an application in the base system

All line and station configuration of the PC NET, as well as the definition of other nodes and applications can be done with the System Configuration Tool (with User- Defined Programs, if not supported by the tool yet). The usage of the tool is described in the Connecting LONWORKS Devices to MicroSCADA manual.

4.3.

Defining communication system objects on-line

The on-line changes take effect immediately. However, if the NET unit is stopped and restarted, the on-line changes will be lost and the preconfiguration will be restored. On-line changes which need to be permanent, and are not made in the preconfiguration, should therefore be included in a command procedure which is executed each time the NET unit has been restarted.

Principles

The procedure for creating communication system objects is as follows:

• Define the NET line to be used by assigning it the desired protocol (the PO attribute, see Chapter 12).

• Give the line its communication properties by means of the line attributes (Chapter 12).

• Create the object by giving it an object number and assigning it the line number.

• Set the attributes of the created object.

• Take the line and the device into use.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

In SCIL, communication system objects are created and deleted using NET attributes, see the System Objects manual, Sections 12.3.1 - 12.3.5. When adding a device, the NET line must first be defined. NET lines are defined by the NET line attribute PO. See examples 4 and 5 in Section “Modifying communication system objects with SCIL” on page 30.

Most attributes can be both read and written on-line with SCIL commands. The attributes are accessed with the object notation according to the format:

OBJnn:Sati

'nn'

Object number (device number)

'at'

Attribute name

'i'

The possible index

The object notation is detailed in the System Objects manual.

The attributes are written with the #SET command according to the format:

#SET OBJnn:SATi = value

See Example 1 in Section “Modifying communication system objects with SCIL” on page 30.

The line attributes can be changed with the SCIL command #SET:

#SET NETnn:Sati = value

'i'

When a new line or device is created on-line, its attributes get the default values given in the System Objects manual.

Line number

Modifying communication system objects with SCIL

By changing attributes, it is possible to define new devices (create new system objects), switch over a device from one line to another, and even redefine a line for another protocol.

Changing the line protocol on-line requires that the line is first removed and then added again with the new protocol. First the line must be taken out of use as described below. In addition, all devices on the concerned line must be removed by setting the attributes which create them to "D". A line is removed from the configuration by setting its PO attribute to 0. A new line is created by setting the PO attribute of the line to the line protocol value (System objects, Section 13.2.). See examples 3 and 4 below.

Changing the line attributes on-line generally requires that the actual line is taken out of use, i.e. setting IU = 0, while the change is performed. After the modification, the line is restarted by setting the IU attribute to 1. See Example 2 below.

Example 1

Changing the printer type of PRI2:

#SET PRI2:SIU = 0 #SET PRI2:SPT = 7 #SET PRI2:SIU = 1

;The printer is taken out of use. ;The printer is changed to a pixel-based colorprinter. ;The printer is taken into use.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

Example 2

Changing the transmission rate on line 1 of NET1:

#SET NET:SIU1 = 0 #SET NET:SBR1 = 1200 #SET NET:SIU1 = 1

;The line is taken out of use. ;The baud rate is changed. ;The line is taken into use.

Example 3

Removing line 2 of NET1, when two stations (STA1 and STA2) are connected to the line:

#SET STA1:SIU = 0 #SET SAT2:SIU = 0 #SET NET1:SIU2 = 0 #SET NET1:SST1 = “D” #SET NET1:SST2 = “D” #SET NET1:SPO2 = 0

Example 4

Adding a printer on line 2 of NET1:

;The stations are deleted. ;The lines are deleted.

;The station is taken out of use. ;The line is taken out of use.

#SET NET1:SPO2 = 4 #SET NET1:SIU2 = 1 #SET NET1:SPR4 = 2

Example 5

Adding three stations of type S.P.I.D.E.R. (STA1, STA2 and STA3) on line 4 of

NET1:

#LOOP WITH NR = 1

;Line number 2 is created as a printer line. ;The line is taken into use. ;Printer number 4 is connected to line 2.

3

#SET NET1:SRT’NR’ = 4 #SET STA’NR’:SSA = %NR #SET STA’NR’:SAL = 1 #SET STA’NR’:SIU = 1

;Station number ‘NR’ is connected to line 4. ;The station address of the station.

#LOOP_END

SYS_NETCON.COM

The base system recognises and executes a file called SYS_NETCON.COM which is a text file containing SCIL commands. The file is executed each time the base system is started. Normally, the file contains only commands for starting possible internal frontends by means of the SCIL function LOAD_DCP (see the Programming Language SCIL manual, Section 8.10.). However, it can also contain statements for reconfiguration of NET objects provided that there is a time delay of at least 5 seconds (achieved with the #PAUSE command) between the start-up of an internal frontend and the subsequent configuration statements.

frontend and the subsequent configuration statements. Only NET objects can be conf igured in SYS_NETCON.COM.

Only NET objects can be configured in SYS_NETCON.COM. Configuring STA and PRI system objects is not possible.

The SYS_NETCON.COM file can be edited with a text editor in Windows environment, e.g. Notepad, or with the MicroSCADA SCIL Program Editor (see Programming Language SCIL, Chapter 12). The SYS_NETCON.COM file must be stored in ASCII format.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

NET start-up configuration with SCIL

A command procedure for on-line reconfiguration of NET could be started as follows:

• When a NET unit is restarted, it sends the system message 10001 to all the defined applications (by default to process object address 6000 + NET no.). Provided that the application is running, the system message may be used for updating a process object which activates an event channel, which in turn starts a command procedure with reconfiguration commands. See “System message handling” on page 161.

• When the connection between NET and an application recovers after a break, NET sends the system message 1000 + APL no. to the application (by default to address 6050 + NET no.). This message can be used for conditional start of reconfiguration procedures, i.e., reconfiguration takes place if NET has been restarted, not if the application has been out of use. This can be checked, e.g. by reading a system object attribute configured on-line. If on-line configuration changes are valid, NET has not been out of operation.

Reconfiguration commands could also, for example, be included in the command procedures started by the event channels APL_INIT_1 and APL_INIT_2, (APL_INIT_H in Hot Stand-by systems, see the Application Objects manual, Section 8.3.). However, a NET unit can be restarted even though the application is not.

NET start-up configuration with the System Configuration Tool

The System Configuration Tool creates procedures for automatic start-up and configuration of the PC-NET. The automatic starting/configuration can be switched on or off. Manual starting/stopping of the PC-NET can be done in the on-line mode.

The automatic starting and configuration of the PC-NET works in the following way:

• A command procedure SYS_INIT_1:C is connected to the event channel APL_INIT_1:A as the first secondary object. If the list of the secondary objects is full, the last one will be removed and a warning will be generated (notify window, log file).

• The command procedure SYS_INIT_1:C calls a text file (StartPCNET.scl) which starts the PC-NET. The program in the text file first updates the sys_/pc_net.cf1 file and then starts the PC-NET by setting the corresponding base system link object type to "INTEGRATED". The pc_net.cf1 file is updated in the following way:

local_node.sa

Taken from the stored configuration

local_node.nn

Taken from the stored configuration

ext_node(1).sa

Own base system station address (SYS:BSA)

ext_node(1).nn

Own base system node number (SYS:BND)

ext_apl(1).nn

Own base system node number (SYS:BND)

ext_apl(1).an

Own application number (APL:BAN)

• The PC-NET sends a system message to the own application when it is started. This message is received by a process object to which an event channel, SYS_NET'net_number'D:A, is connected. This event channel calls a command

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

procedure SYS_NET'net_number'D:C. If the process object exists (e.g. created by LIB5xx) and has an event channel connected to it, all the objects connected to that event channel will be moved to the SYS_NET'net_number'D:A event channel as secondary objects. In other cases, the tool automatically creates a process object SYS_NETD:P('net_number'), to which the event channel SYS_NET'net_number'D:A is connected.

• The command procedure SYS_NET'net_number'D:C checks the message coming from the PC-NET. If this is the start message (10001), the PC-NET will be configured according to the information entered in the tool.

All the possible error messages that occur during the start-up or configuration of the PC-NET are shown in the notify window. They are logged into the SYS_ERROR.LOG and SYS_ERROR.OLD log files, which can be viewed in the tool.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

5.

Configuration data files

This chapter describes:

5.1 The general rules for the configuration data files of the communication frontends. The data files are illustrated by an example.

5.2 The configuration parameters of the communication frontend.

5.1.

General rules

Contained parameters

As mentioned above, the configuration parameters of the workstations are listed and described in the workstation manuals. The parameters of the communication frontend are described in Section 5.2. All the listed parameters need not to be included in the configuration data files. Some parameters are mandatory only for certain configurations and some represent optional features. Many configuration parameters have default values (see the parameter lists), which are valid if no other values are given for the parameters in the configuration data file. If the default values are correct, the parameters need not to be included in the data files. The values given in the data files replace the default values.

File format

The parameter definition lines of the data files can be arranged in any order. Each line in the files has the following structure, see Figure 5.1.-1:

• The first six character positions of a line are reserved for the parameter name.

• The seventh position contains a blank space.

• The parameter value is written starting from position 8.

• After the parameter a comment may follow, indicated with a starting semicolon (;).

ent may follow, indicated with a starting semicolon (;). Fig. 5.1.-1 The format of a line

Fig. 5.1.-1

The format of a line in the data files MFLCONF.DAT and MWCONF.DAT

Editing the data files

The data files can be changed with a text editor (DOS format). They cannot be changed while the workstation or frontend is in operation, because a modification requires that the actual workstation or frontend (including the communication units) is restarted.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

5.2.

Frontend configuration parameters

Frontend parameters

SRC Station Address of Frontend

The station address of the communication frontend must be unique among all nodes (base systems, communication units and front-ends) in the entire MicroSCADA network.

SRCNOD Node number of Frontend

Value:

1

32

Default value:

Station address - 200

Base system parameters

The communication frontends can be connected to up to four base systems, each of

which is identified by a sequence number 1

a certain base system by the DST parameter, see below. The base system communication parameters must always be included in the frontend configuration data file MFLCONF.DAT, unless the given default values are accepted.

4. The sequence number is related to

DI Diagnostic Command Interval

MFL sends cyclically diagnostic commands to the base systems when there is no other communication. This parameter specifies the time interval between the commands.

Type:

Integer

 

Value:

0

65535

The time interval in seconds 0 = no diagnostics

 

Default value:

15

Indexing:

Base system sequence number, 1

4

If index is omitted, the value is valid for all the base systems

DST Station Addresses of Connected Base Systems

The station addresses of the base systems to which the frontend is connected. This parameter is the value of SYS:BSA in the connected base system, see the System Objects manual, Chapter 4.

Indexing:

Base system sequence number, 1 If omitted, index = 1

4

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

NOD

Node number of base system

Value:

1

32

Indexing:

Base system sequence number, 1 If omitted, index = 1

4

PROT

Protocol

The link layer protocol used in the communication with the base system.

0

=

ANSI X3.28 (using a COM port)

2

=

TCP/IP (possible if the base system computer is PC /Windows)

Default value:

0

Indexing:

Base system sequence number, 1 If omitted, index = 1

4

NET Parameters

Each communication frontend can contain up to four communication units (NETs) connected to the RAM interface. In the MFLCONF.DAT file the individual units

are identified by a board index (interface number), 1

the I/O base addresses, IRQ levels and RAM window locations of the DCP/MUXi

boards as follows:

4. The indexes are related to

Index

I/O address

IRQ

RAM address

 

1 33CH

5

D0000H

D3FFFH

 

2 2BCH

12

D4000H

D7FFFH

 

3 23CH

15

D8000H

DBFFFH

 

4 1FCH

3

DC000H

DFFFFH

CMOD

Initial mode of NET

0 =

single mode of NET

1 =

redundant hot

2 =

redundant stand-by

Default value:

0

Indexing:

Board index 0 = single (no redundancy) see above If omitted, index 1

CSRC

NET Station addresses

The station address, the AS attribute, of the NET (see System Objects, Chapter 12). This parameter is only needed when a NET unit or base system is connected to a serial line of the NET unit in question (specified by the index). The parameter name may occur several times in the configuration file, with different values, if several base systems or communication units are connected to the same unit.

Indexing:

Board index, see above If omitted, index 1

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

CPNOD

Peer node number of NET

The node number of the partner NET in a redundant relationship. The parameter has no meaning, if there is no redundancy.

Indexing:

Board index, see above If omitted, index 1

TCP/IP interface parameter

The following parameter is mandatory, if TCP/IP communication is used:

HOST

TCP/IP Host Name

The internet address or host name of the base system computer given either as host name/alias name or with dot notations. The parameter is valid only for TCP/IP communication, i.e. PROT = 2.

Indexing:

Base system sequence number, 1 Communication Parameters above) No index = index 1

4 (see the Base system

Examples:

HOST

SPIDER

HOST

130.0.9.130

system Examples: HOST SPIDER HOST 130.0.9.130 Comments are not allowed on this parameter line. Serial

Comments are not allowed on this parameter line.

Serial communication parameters

The following parameters are meaningful only when the frontend is connected to a base system through serial lines and a COM port. If a base system is connected on a COM port, an external clock cannot be connected, see below. Likewise, if an external clock is connected to a COM port, it is not possible to connect a base system this way.

BR

Baud Rate

The transmission rate used on the line.

Recomm.:

BR = 9600

COM

Communication Port

The communication port used for serial communication with the base system.

Value:

1 = COM1 2 = COM2

Default value:

1

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

EN

ENQ Limit

See the EN attribute in the System Objects manual, Chapter 13.

Type:

Integer

Value:

1

255

ER

Embedded Response

For more information, refer to the System Objects manual, Chapter 13.

Value:

0 = No

1 = Yes

NA

NAK Limit (1

255)

See the NA attribute in the System Objects manual, Chapter 13.

PY

Parity

See the System Objects manual, Chapter 13.

Value:

0 = no parity

1 = odd parity

2 = even parity

Recomm.:

Even parity (PY=2)

RE

Redundancy

See the System Objects manual, Chapter 13.

Value:

0 = No redundancy

(1 = CRC, not supported)

2

= BCC

Recomm.:

RE = 2

TI

Timeout Length

See the TI attribute in the System Objects manual, Chapter 13.

Type:

Integer

Value:

1

255

External clock parameters

The following parameters apply, when an external clock is connected to a COM port of the PC:

COMAG

COM Port for ASCII General

The number of the COM port (1 or 2) reserved for time synchronization using the General ASCII protocol. Only one COM port at a time is available for serial communication (software limitation). Hence, if a COM port is used for time

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

synchronization, no base system can be connected through a serial line, or, if a base system is connected via a COM port, time synchronization of the frontend is not possible.

Values:

0 = no external clock (default)

1 = COM1

2 = COM2

CLOCK

Clock Type

The type of clock used on the COM port specified by the COMAG parameter.

Values:

1 = COMPUTIME

2

= RCC8000

5

= GPS166

6

= TRIMBLE

MODE

Synchronization Mode

Currently needed only if CLOCK = 6. In that case MODE should be given value 6.

Internal clock parameters

The following parameters are required, when the Meinberg radio clock boards PC31 and PC32 are used for clock synchronization:

TZ_MIN

Time zone (minutes)

Time zone dependent correction added to the time received from the radio clock.

Value:

-720 … 720

CF

Clock read frequency

Clock read frequency (cycle) in seconds. The parameter determines how often the time will be read from the PC31/PC32 clock and written to the NET boards. The value should be an adjusting between the demands for accuracy and the increased load caused by the readings.

Default value:

0 = no reading

CA

Clock address

The I/O address of the radio clock.

Default value:

768 ( = 300H)

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

6.

Base systems

This chapter describes:

6.1 The fundamental configuration of a base system and its applications.

6.2 How to configure intercommunication between two applications in the same base system or in separate ones. The base system configuration additions and modifications required by various installations are

14. Chapter 3 describes the structure

described in detail in Chapters 7

of the SCIL program blocks for base system object definition.

6.1.

Configuring a base system

Fundamental definition (SYS)

Create a SYS:B object with at least the following attributes (see the example in Figure 6.1.-1):

ND

The node number of the base system. The node number must be

SA

unique within the entire MicroSCADA network, see Chapter 7. The MicroPROTOCOL station address of the base system. Like the node number, the station address must be unique within the network, see Chapter 7.

The following attributes are optional:

ER

The use of the base system as a routing node. It means that if

DN, DS

routing is enabled in a specific base system, it can route messages addressed to other nodes. See Section 4.2.4. in System Objects. The default node number and default station type. These

SH

attributes should not be used! Shadowing attribute. This attribute is used for the configuration

TI

of hot stand-by, see Chapter 14. Timeout length for node communication. The attribute can be

PC, RC

locally and temporarily sidestepped by a SCIL function (TIMEOUT). Memory cache space attributes, see ‘Tuning memory

FS

parameters’ in this section. File Sync. The flushing of buffered data onto disk.

DE

Allowing applications in the base system to be accessed by other

AA CA, CF, CL, TZ

software using DDE. The use of standard audio-visual alarm unit. Attributes related to an external clock, see Chapter 10 or Section

SD, SP

4.3.2. in System Objects. SPACOM devices connected directly to the base system.

DM, TF

Debug mode and time format.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

The following attribute is read-only and is therefore not set:

DU

The attribute states whether the DDE server is usable or not. Its value is 0, if the DDE server has not been started. If the DDE server has been started, its value is 1 if a user has logged on to the base system computer, otherwise 0.

has logged on to the base system computer, otherwise 0. The SYS:B object definition must come

The SYS:B object definition must come first in the base system configuration file SYS_BASCON.COM, otherwise the system will not start.

Links (LIN)

A link is a data transmission line to another base system, a NET unit or a device.

Each link is defined by a LINn:B object (n = 1 following links:

• One link for the LAN. The definition of LAN links is described in Chapter 8.

• Two RAM links for internal DCP NETs. The RAM links are described in Section

20). A base system can have the

9.2.

• One Integrated link for a PC NET. (Created by the System Configuration Tool.)

Nodes (NOD)

Nodes are directly or indirectly connected base systems, communication units, and communication frontends. The nodes are defined by NODn:B objects

(n = 1

• Communication with another base system. This is described in Section 6.2.

• Communication through the communication units. Each NET unit - DCP NETs as well as PC-NETs - which will be recognized by the base system must be defined as a node. These node definitions are described in Chapter 9.

• Reading and writing the attributes of communication frontends. A node is primarily specified by the used connection link and the station address of the node. If a node is only indirectly connected to the base system, the link to the node is the link to the nearest intermediate node. The link object must have been defined before the node can be defined.

250). A node definition is needed for:

Devices (MON, PRI, STA)

The monitors, printers and stations are defined as MONn:B (n = 1

(n = 1

The required MON definitions are described in Chapter 10, PRI objects in Chapter 11 and STA objects in Chapter 12.

100), PRIn:B

20) and STAn:B (n = 1

5000) objects respectively.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

Local applications (APL)

A local application is situated in the base system in question, which means that all the application software is stored in the computer as a directory branch under the application directory apl. For example, the application software of the local application "sample" is stored in the directory \sc\apl\sample.

"sample" is stored in the directory \sc\apl\sample. The application directory branch with its subdirectories

The application directory branch with its subdirectories must exist before a local application can be defined in the base system configuration (see the Installation manual).

Base system 1

Node Number: 9 Station Address: 209

APL1

APL2

Base System Configuration

Base system

#CREATE SYS:B = LIST(-

- = 209, -

PC = 1000,-

RC = 500 )

ND = 9,

SA

Concerning the definition of links, nodes, monitors, printers and stations, see the examples in the subsequent chapters.

Application 1:

#CREATE APL:V = LIST(- NA = SAMPLE , - AS = HOT , - MO = (-1, -1, -1, -1, -1)- TT = LOCAL ) #CREATE APL1:V = %APL

Application 2:

#CREATE APL:V = LIST (- NA = TUTOR ,- AS = HOT ,- MO2 = 2, - TT = LOCAL ) #CREATE APL2:V = %APL

Example_defin.eps

Fig. 6.1.-1

An example of the fundamental definition of a base system and the definition of two local applications.

To configure a local application in the base system:

Create an APLn:B object ('n' = 1

the System Objects manual, Chapter 5):

250) and assign it the following attributes (see

NA

Application Name. The application name is the name of the

MO

application directory branch containing the application software (e.g. "SAMPLE" according to the example above). Monitor mapping, see the headline "Device Mapping" below.

AS

"HOT" if the application will be running.

AP

Application mapping if the application will communicate with

ST, PR

other applications within the same or in different base systems (see Section 7.2). Printer and station mapping. These attributes are generally not needed, see the headline "Device Mapping" below.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

TT EM, HB, PM

"LOCAL" History buffer and queue lengths, see the headline "Tuning

PQ

Memory Parameters”. Number of parallel queues.

QL

Maximum length of process queries.

See the examples in Figure 6.1.-1.

of process queries. See the examples in Figure 6.1.-1. At least one local application must be

At least one local application must be created in SYS_BASCON.COM, given a name (NA), set to "LOCAL" (TT) and to "HOT" (AS) and mapped for at least one monitor (MO).

The application that is created first in SYS_BASCON.COM will be the default application. If no application number is given when opening a MicroSCADA monitor, the default application is chosen. Likewise, if no application number given when using the program interface, the default application is addressed.

Device mapping

Monitors, printers and stations can be mapped for an application, which means that the application recognises the devices under logical numbers.

The station mapping, for instance, specifies the station numbers under which the application will know the stations. The station mapping has the following format:

APLn:BSTi = j

i

The logical station numbers as known to the application and the

j

values The STA object numbers of the stations

The printer mapping works in a similar way and also the mapping of semi-graphic workstations. Printers and stations can be mapped for several applications simultaneously, while the semi-graphic workstations are reserved for the application when mapped.

The printers and stations have a default mapping, which means that each logical application recognises them under the real object numbers. Therefore, the printer and station mapping is needed only if the application for some reason needs to know the devices under logical numbers. If there are no obstacles, let the logical numbers be the same as the object numbers (i.e. i = j), i.e. do not change the default values of printer and station mapping.

The monitor mapping is described in Chapter 10.

Tuning memory parameters

The allocation and use of the available RAM memory is affected by the following base system attributes:

• The SYS:B attributes PC (= Picture Cache Size) and RC (= Report Cache Size), see the System Objects manual, Chapter 4.

• The APLn:B attribute HB (= History Buffer), see the System Objects manual, Chapter 5.

1MRS751846-MEN

MicroSCADA Pro

System Configuration

Configuration Manual

SYS 600 *9.1

• The picture cache and report cache memory space is common to all the applications in the base system. The cache memories contain only objects and pictures that have been in use, but are not currently running. The maximum cache space is specified by the PC and RC attributes. When these limits are reached, the least used objects are removed.

During operation, there should be at least 500 kB free memory. The MF, MS and MU attributes can be used for reading the occupied and the free memory space (see the System Objects manual, Section 4.2.5). If there is not enough free memory, memory is taken from the picture and report caches.

6.2.

Communicating applications

Communication between applications means that the object data in one application can be read and written from another one by means of the object notations. Communication between applications in the same base system, i.e. between two local applications, is achieved simply by application mapping (the APLn:BAP attribute).

Communication between applications in separate base systems requires that the base systems are physically connected to each other, either through direct serial lines, through LAN or through frontends, see Figure 6.2.-1. The configuration and communication principles are the same, independently of the route between the base systems. The communicating base systems are identified to each other by node numbers and station addresses and the link to the nearest node. The route through the network need not to be defined. It is recommended not to have more than three communication units between two communicating base systems.

SYS 600 *9.1

MicroSCADA Pro

System Configuration

Configuration Manual

1MRS751846-MEN

Base system 1

Node Number: 9 Station Address: 209

APL1

APL2

Base System Configuration

Base system

#CREATE SYS:B = LIST(-

- = 209, -

PC = 1000,- RC = 500 )

ND = 9,