ABB micro SCADA installation note

7/23/2019 ABB micro SCADA installation note

http://slidepdf.com/reader/full/abb-micro-scada-installation-note 1/132

1MRS751853-MENIssued: 15.03.2002

Version: A

Program revision: 8.4.4

We reserve the right to change data without prior notice.

Installation

Installation Guide

SYS 500

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-MUMJAVA-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-MENConfiguring MicroSCADA for Modbus Master Protocol 1MRS752242-MEN

Configuring MicroSCADA for Modbus Slave Protocol 1MRS751864-MEN

SYS 500Installation

Installation Guide

1MRS751853-MEN



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

1MRS751853-MENInstallationSYS 500

Installation Guide



1

2

34

5

6

7

8

1 Introduction

2 Hardware and software requirements

3 Installing base systems

4 Installing and configuring LAN

5 Installing process communication system

6 Installing workstations

7 Installing peripherals

8 Upgrading from previous revisions

SYS 500Installation

Installation Guide

1MRS751853-MEN



SYS 500

ContentsInstallation Guide

Contents:

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

1.1. About this manual .........................................................................1

1.2. Reference manuals .......................................................................1

2. Hardware and software requirements .....................................3

2.1. Base systems ................................................................................3

2.1.1. Hardware requirements .....................................................3

2.1.2. Software requirements .......................................................4

2.2. Local Area Network (LAN) ............................................................5

2.3. Process communication system ....................................................5

2.3.1. Communication units, NETs ..............................................6

2.3.2. Communication front-ends .................................................6

2.3.3. Process connections ..........................................................72.4. MicroSCADA workstations ............................................................8

2.5. Peripherals ....................................................................................9

2.5.1. Printers ...............................................................................9

2.5.2. Alarm devices ..................................................................10

2.5.3. Radio clocks .....................................................................11

2.6. Separate network topology server ..............................................11

3. Installing base systems ..........................................................13

3.1. Overview .....................................................................................13

3.2. Preparations ................................................................................17

3.3. Installing MicroSCADA base product software ...........................183.4. Installing optional products ..........................................................25

3.5. Managing applications ................................................................26

3.6. Configuring the base system operator workstation .....................29

3.7. Managing device drivers .............................................................31

3.8. Editing configuration files ............................................................36

3.9. Base system administration ........................................................43

3.9.1. Using MicroSCADA control panel and administrator .......44

3.9.2. Start-up and shutdown management ...............................45

3.9.3. Supervising MicroSCADA ................................................48

3.9.4. Miscellaneuos ..................................................................50

4. Installing and configuring LAN ..............................................51

5. Installing process communication system ...........................53

5.1. Overview .....................................................................................53

5.2. Installing PC-NET software and PCLTA cards ............................56

5.2.1. Installing and configuring PC-NET software ....................56

5.2.2. Installing multiport serialcard ...........................................57

5.2.3. Installing PCLTA cards ....................................................57

5.2.4. Installing and configuring driver for PCLTA card .............60

1MRS751853-MEN Installation




Contents Installation Guide

5.2.5. Installing PCLTA-20 adapter in Windows 2000 Professionalor Windows 2000 Server 60

5.2.6. PCLTA-20 Card installation ............................................. 63

5.2.7. Configuration settings for the PCLTA-20 adapter ............63

5.2.8. Starting and configuring PC-NET .................................... 65

5.3. Installing DCP-NET units in base systems .................................67

5.4. Installing frontends ......................................................................72

5.4.1. Preparing the PC .............................................................72

5.4.2. Installing DCP-NET Cards ............................................... 73

5.4.3. Installing frontend software ..............................................74

5.4.4. Configuring frontends ......................................................76

5.4.5. Using communicaton frontends .......................................78

5.5. Installing NET connections .........................................................79

6. Installing workstations .......................................................... 81

6.1. Installing workstations connected to LAN ...................................816.2. Installing workstations connected via telephone line ..................86

6.3. Compiling MicroSCADA fonts .....................................................98

7. Installing peripherals ........................................................... 101

7.1. Installing printers .......................................................................101

7.2. Installing MicroSCADA alarm units ...........................................104

7.3. Installing radio clocks ................................................................110

8. Upgrading from previous revisions .................................... 113

8.1. Upgrading base systems .......................................................... 113

8.2. Upgrading DCP-NET ................................................................1178.3. Updating device drivers ............................................................ 118



1MRS751853-MEN SYS 500

1

1. Introduction

Installation

Installation Guide

11. Introduction

This chapter summarises the contents of this manual and lists the most necessaryreference manuals.

1.1. About this manual

This manual describes the software and hardware installation of MicroSCADA:base systems, LAN connections, process communication systems, workstations andperipherals. The manual is divided into 8 chapters with the following contents:

Chapter 2. REQUIREMENTS

The hardware and software requirements for the entire

MicroSCADA system.

Chapter 3. INSTALLING BASE SYSTEMS

The installation of the MicroSCADA base systems and

the Windows NT operating system.

Chapter 4. INSTALLING LAN CONNECTIONS

The installation of local area network (LAN) hardware

and software. Installing connections to LAN.

Configuration of TCP/IP networks.

Chapter 5. INSTALLING PROCESS COMMUNICATION

SYSTEM

The installation of PC-NETs, DCP-NETs and

communication front-ends. Installation of communication

equipment. Connecting stations. (See also the station

specific manuals for connecting stations to MicroSCADA

as well as the product manuals of the respective stationtypes.)

Chapter 6. INSTALLING WORKSTATIONS

The installation of workstations. The installation and

compilation of fonts. Display management. (The

installation of semi-graphic workstations is described in a

separate manual of our former releases.)

Chapter 7. INSTALLING PERIPHERALS

The installation of printers, alarm units and radio clocks.

Chapter 8. UPGRADING FROM PREVIOUS REVISIONS

The upgrading of an existing 8.2 MicroSCADAapplication to 8.4. The upgrading of the NET.

1.2. Reference manuals

The following manuals are referred to in this document and should be at handduring the installation:

MicroSCADA System Configuration, Configuration manual

• MicroSCADA System Objects, Technical Reference manual

• Windows NT and eXceed manuals from Microsoft

1MRS751853-MEN




3

2. Hardware and soft-ware requirements

Installation

Installation Guide

2

2. Hardware and software requirements

This chapter specifies the hardware and software required for the installation ofMicroSCADA revision 8.4.3:

2.1 Hardware and software requirements set by the base systems:computer, graphics card, monitor, mouse, operating system,

MicroSCADA software and other additional software.

2.2 Requirements on network adapter cards and LAN software.

2.3 Requirements set by the process communication system: PC-NET

program, DCP-NET cards, front-ends, gateways, LONWORKS

networks, cables, modems and optomodems, line switches, etc.

2.4 Requirements on MicroSCADA workstations.

2.5 Requirements on peripheral equipment: printers, alarm units and radio

clocks.

2.6 Miscellaneous: requirements on a separate Network Topology

computer.

The requirements set by the semi-graphic workstations are detailed in the

MicroWORKSTATION manual that was issued in our former releases.

2.1. Base systems

This section describes the hardware and software requirements set by the

MicroSCADA base systems.

2.1.1. Hardware requirements

PCThe MicroSCADA base system sets the following requirements on the PC:

Processor: Pentium or Pentium Pro. Intel 80486 can be used but is not

recommended.

Frequency: 120 MHz or more, 200 MHz recommended. Minimum

166 MHz, if Network Topology will run on the computer.

Bus architecture: PCI, ISA or EISA.

Emulex NET cards, PCLTA Dual Port and clock cards

(PC32) require ISA slots. Alarm unit requires either ISA

(Flytech) slots or a PCI (ADLink PCI-7250 or Advantech

PCI-1760) slot.

RAM: Minimum: 128 MB.

Recommended: 256 MB or more. 256 MB, if

Network Topology will run on the

computer.

Disk space: Minimum: 300 MB

Recommended: 1 GB. 2 GB if Network Topology

will run on the computer.

Disk controller: All operating system supported.

1MRS751853-MEN



4


2. Hardware and softwarerequirements

Installation Guide

Display controller: Screen resolution: at least 1024x768

Colour support: at least 256 colours

Display frequency: at least 70 Hz

Mouse: Any mouse supported by the operating system.

CD-ROM: Any device supported the operating system. Required for

MicroSCADA installation.

Free slots: Depending on the configuration:

- One for the network adapter card used for LAN, unless

it is included on the motherboard.

- One ISA slot for each DCP-NET card.

- One ISA slot for each PCLTA (LON) card.

- One PCI slot for each PCLTA-20 (LON) card.

- At least two ISA slots for a standard MicroSCADA

alarm unit. The alarm unit occupies a third slot if

additional external alarm devices are used.

- One PCI slot for a PCI audio alarm card.

- One ISA slot for a radio clock card.

Tape driver: Not required by MicroSCADA. For taking backup any

operating system supported device can be used.

I/O ports: Optional. Serial ports (COM ports) can be used for

process connections provided that the base system

contains the PC-NET software. Serial and parallel ports

can be used for printer connections and for connecting

remote workstations.

Monitor

If the monitor will be used for displaying MicroSCADA monitors, it should have a

screen resolution of at least 1024x768 pixels and a screen refresh rate of at least

70Hz.

Network adapter card

Any network adapter card supported by the operating system can be used. See

section 2.2.

2.1.2. Software requirements

Operating system

MicroSCADA 8.4.3 runs under the Windows NTTM operating system version 4.0with Service Pack 3, from Microsoft. Both the Windows NT Workstation and the

Windows NT Server may be used. The limitation of the Workstation version is in

the number of simultaneous users of the shared resources. If the MicroSCADA base

system will communicate with more than one remote MicroSCADA Workstation at

a time using RAS (Remote Access Services), the Server version is required.

For the MicroSCADA support to work smoothly in case of problems, we

recommend that you use the English version of the operating system.




5


Installation

Installation Guide

2

Additional software

The Hummingbird Exceed version 5.1.3 is required whenever the base system

monitor is used for displaying MicroSCADA X or VS remote monitors.

2.2. Local Area Network (LAN)Figure 2.2.-1 shows an overview of the LAN hardware and software requirements.

In all LAN communication, MicroSCADA uses the LAN communication protocol

TCP/IP (Transport Control Protocol/Internet Protocol) and Ethernet interface.

LAN in PC/Windows NT computers

MicroSCADA supports all network adapter cards supported by the Windows NT™

operating system. The device drivers are included in the Windows NT operating

system package.

LAN card, PC/DOS

In PC/DOS computers (workstations and front-ends), e.g., the following networkadapter cards can be used:

• SMC EtherEZ Ethernet adapter (recommended).

• 3Com509 (verified in tests).

• ReadyLINK, ENET Universal Series from COMPEX Inc., USA.

LAN software, PC/DOS

See Figure 2.2.-1. The following LAN software have been verified in PC/DOScomputers (workstations and front-ends) on TCT/IP networks:

• PC/TCP from ftp Software Inc., USA, versions 2.05, 2.1, 2.3, 3.1 and 4.1.

2.3. Process communication system

This section describes the requirements set by the process communication system:

• NETs (PC-NETs and DCP- NETs)

• Front-ends and gateways, redundant front-ends.



6



Installation Guide

• Process connections: LONWORKS network connections, cables, modems, optomodems, etc.

2.3.1. Communication units, NETs

PC-NETs

The PC-NET is a communication program that runs in the base system computers.It uses the COM ports of the computer or the COM ports of a multiport serial card

and the channels of (a) possible PCLTA card/cards as communication lines. The PC-NET program is required for communication with LONWORKS network.

PC-NET supports the following protocols: ACP (MicroSCADA internal protocol),

LonTalk, SPA, IEC 870-5-101 master and slave, IEC 870-5-103 master, IEC 1107,ADLP 80 slave, LCU 500, RP570 master and slave and RP571 master.

The PC-NET program is included in the MicroSCADA base product software.

DCP- NETs

The DPC-NETs are composed of NET programs running on special PC card. ADCP-NET requires:

Communication card: -DCP286i with daughter board RS-232C, 8-port, or

- DCP386i with daughter board RS-232, 8-port.

Both these cards have a RAM memory of 1024 kB.The DCP386i card is faster than DCP286i.

Manufacturer: Emulex Corp., California.

Communication software: DCP-NET. Included in the MicroSCADA baseproduct software and in the front-end software.Internal NETs (DCP-NETs mounted within the

base system computer) require the MicroSCADAdriver package MS-CRAM, which is also includedin the base product software.

The DCP-NET program includes all communication protocols supported by

MicroSCADA, except LonTalk, which is supported only in PC-NET.

Each NET unit occupies one full-size slot in the host computer.

If the base system computer contains two communication boards, effective cooling

is required.

2.3.2. Communication front-ends

The communication front-ends are PCs containing 1... 4 DCP-NET cards.

General requirements

Processor: Minimum 80486, 66 MHz.

RAM Memory: Minimum 1 MB.




7


Installation

Installation Guide

2

Disk memory: 1... 3 MB free disk space.

Operating system: MS-DOS, version 3.3 or later.

Free slots: 1... 4 slots for communication boards

If communication via LAN is used, 1 slot for the networkadapter card.

I/O ports: If serial communication is used, COM1

Communication units: 1... 4 DCP-NET cards, see above.

Front-end software: Included in the front-end software on the MicroSCADACD.

Network adapter cards and LAN software: See section 2.2.

If the front-end contains more than one communication card, effective cooling is

required.

Redundant front-ends

Software: Special application software is required in the base

systems that use redundant front-ends. The software isincluded in the tool software package delivered on the

MicroSCADA installation CD.

Fallback switches: The standard redundant front-end application software

requires fallback switches, which are control input DTRedge sensitive. Verified in tests: FBS KU13.1 made by

KUUMIC Oy, Finland.

2.3.3. Process connections

LONWORKS network

If MicroSCADA is connected to LONWORKS network, it requires a base systemrunning PC-NET and a LONWORKS network interface hardware.

When a LONWORKS network is connected to MicroSCADA, it is built in star

formations around interconnected star couplers. The star couplers are made by ABBTransmit Oy and have the product designation RER111. For more information, refer

to the RER111 documentation.

• Single or dual channel PCLTA card(s) made by Echelon Corporation. The PC-

NET can utilise up to 4 channels.

• A transceiver for each output channel that will be used, preferably the optotransceivers RER107 made by ABB Substation Automation Oy.

At present, the PCLTA cards including the RER107 transceivers must be purchasedfrom ABB Substation Automation Oy in a mounted and configured condition. If

other transceivers are used, other requirements are set on the card configuration.

1. LONWORKS is a registered trademark of Echelon Corporation.



8



Installation Guide

The maximum number of devices (LON nodes) per transceiver is 30 - 50 dependingon the required communication rate (max 1.25 MB/s).

• PC-NET software.

• MS-PCLTA driver package.

Twisted NET cables

The cable wiring for connecting devices to NET is illustrated in chapter 5 and

chapter 8 (printers). The NET serial ports are 25 pin male plugs.

Together with the PC-NET, the COM ports can be used for process communication.

The COM ports are 9 pin male connectors.

NET modems

General requirements: Support for the transmission of 8 data bits, 1 parity bit, 1

start bit and 1... 2 stop bits.

Modem verified for communication with stations (not on multidrop lines) andworkstations (including autodialling):

• Semaphor (2314C, 2324C and 2396C) made by Ericsson, Sweden.

Optomodems

Consider the following guidelines when selecting optomodems:

• Demand for external power supply.

• Power supply provided by the RTUs.

Tested and recommended optomodems for use in NET - SPACOM communication:

In the NET end: PA-ZC 17 and cable SPA_ZP 19A2 from ABB TransmitOy

In the SPACOM end: See the SPACOM documentation.

Tested optomodem in communication NET - S.P.I.D.E.R. RTU or SRIO:

Trademark: FOM 6A, from RAD, Israel.

Additional power supply: Power Supply Adapter PSA

from RAD (required when used with RTU200).

When used with RTU210 or SRIO, no additional power supply is required, if the

power is taken from pin 20. RTU210 and SRIO give about 8V on pin 20, while

RTU200 gives about 3V, which is not enough as 6...15V is required.

2.4. MicroSCADA workstations

Processor: Minimum 80486.

RAM memory: Minimum 16 MB.

Disk storage: 20 MB free disk space.




9


Installation

Installation Guide

2

Operating system: Windows NTTM 4.0 with Service Pack 3 or Windows 95with Service Pack 1.

Graphics adapter: Support for 256 colours.

• Using a PC as a MicroSCADA workstation requires the X-server software

Exceed version 5.1.3 from Hummingbird Communications Ltd.

See section 2.2.

2.5. Peripherals

In this section there are detailed requirements, which are set by the following

peripheral equipment:

• Printers. There are different requirements depending on how the printers will be

used.• Alarm devices

• Radio clocks

2.5.1. Printers

There are the following alternatives for using a printer in MicroSCADA:

• Using the printer exclusively for hardcopy printing via the X server software.

• Using the printer for full-graphic MicroSCADA printout. Automatic printing

from MicroSCADA is possible and the printer can also be used for hardcopyprinting via the X software if connected to a base system.

• Using the printer for semi-graphic MicroSCADA printing. Automatic printing ispossible. The printer can be used for semi-graphic hardcopy printing viaMicroSCADA and for hardcopy printing via the X server software if connectedto a base system.

Printers can be connected to a base system, a NET or to LAN (via printer servers).Printers connected to a base system and printers connected to LAN can be used byall base systems on the LAN, and printers connected to a NET can be used by all

base systems connected to the process communication system.

Hardcopy devices used via X server

Any printer or hardcopy device supported by the operating system can be used. The

printer can be connected directly to the base system or workstation, or to the LAN.

Full-graphic MicroSCADA printers

The full-graphic MicroSCADA printing is realised by direct print data transfer to theprinters. This "transparent printing" requires printer type specific code definitions inthe base system.

Printer type: Any printer type supported by the operating system.

To simplify the printer coding the MicroSCADA delivery contains a printer code

definition file, which applies to the following printer types: IBM Proprinter, Epson,

Epson FX and Fujitsu DPL24C.



10



Installation Guide

LIB 500 uses full-graphic printout for the automatic event and alarm printouts.

Semi-graphic MicroSCADA printers

The semi-graphic MicroSCADA printout is composed of the semi-graphic portionsof the pictures. Depending on the printout quality, the following printers are

supported:Black-and-white character-based printout: Any type.

Pixel-based black-and-white printout: Any EPSON FX-80 compatible

printer.

Pixel-based colour printout: Any EPSON JX-80 compatible

printers, e.g. FACIT E620 orFACIT3550.

None of the three printout types supports the printing of full graphics or pixel based

curves. Printers that are directly connected to a base system always produce printoutof the first type. Printers that are connected to a NET can produce any of the threequalities depending on the printer type and system configuration.

Printer servers

The following printer servers have been verified to work properly in MicroSCADAtests:

• HP JetDirect EX Plus with one parallel port.

• HP JetDirect EX Plus3 with three parallel ports.

2.5.2. Alarm devices

I/O and audio alarm cards: FPC-046 PC INDUSTRIAL I/O ISAcard made by FLYTECH

TECHNOLOGY.NuDAQ PCI-7250 PC audio alarmPCI card made by ADLink

Technology Inc.

PCI-1760 PC audio alarm PCI cardmade by Advantech.

Cable connection card and alarm panels: Supplied by ABB SubstationAutomation Oy, Finland.

There are two kinds of solutions for the alarm unit:

• Industry Standard Architecture (ISA) bus based unit including standard alarm

panel, FPC-046 I/O card and cable connection card. An additional alarm devicemay also be added to this system, for example alarm horn or robot telephone.

• Peripheral Component Interconnect (PCI) bus based audio alarm unit includingaudio alarm panel and either Adlink ’s PCI-7250 or Advantech’s PCI-1760 audioalarm card.

The Flytech based alarm unit occupies two or three ISA slots in the computerdepending on whether an additional external alarm device is used or not. Thissystem requires the installation of the MicroSCADA alarm device driver package

MS-AA.




11


Installation

Installation Guide

2

The PCI based system requires the installation of the PCI-7250 or PCI-1760 audioalarm card driver package, depending on which card is used for the unit.MicroSCADA supports version 2.0 of the ADLink ’s PCI-7250 card driver for

Windows NT 4.0 and version 1.10 of the Advantech’s PCI-1760 card driver for

Windows NT 4.0. The PCI card drivers and installation instructions are provided by

their manufacturers.

2.5.3. Radio clocks

Radio clock card can be mounted inside a base system computer or a communicationfront-end. The card occupies one full-size ISA slot in the computer.

Alternative Types:

- PC31 or PC32 with DCF77 receiver

- PC32 with additional minute pulse output and

possibility for connecting to external GPS166 receiverMeinberg Funkuhren, Germany

Accuracy: About 10... 20 ms.

The radio clock requires MicroSCADA radio clock driver MS-PC3x.

External radio clocks are connected to a serial port of a communication front-end ora NET:

Types:

- COMPUTIME with DCF77, MSF or GPS receiver- DIEM Electronic, Geneva, Switzerland

- RCC8000 with MSF, DCF77, HBG or WWVB receiverRadiocode Clocks Ltd

- Trimble, GPS Receiver. Additional hardware requiredfor connecting to NET and communication front-end.

Accuracy: About 10... 20 ms.

Receiver features:

DCF77: 77.5 kHz, Mainflingen, Germany.

MSF: 60... 80 kHz, Rugby.

GPS: Satellite based. Global (Global Positioning System).

2.6. Separate network topology server

The Network Topology software sets the following requirements when running in aseparate computer:

Processor: Pentium or Pentium Pro.



12



Installation Guide

Frequency: 166 MHz or more.

Bus architecture: ISA or EISA.Audio alarm unit, NET cards, PCLTA-10 and clock cards

require ISA slots.

RAM: Minimum: 64 MB

Recommended: 96 MB

Disk space: Minimum: 100... 500 MB depending on thesize of the distribution network.

Recommended: 1 GB

Disk controller: Any SCSI or IDE controller supported by the WindowsNT operating system.

Display controller: Screen resolution: at least 1024x768

Colour support: at least 256 coloursDisplay frequency: at least 70 Hz.

Mouse: Any mouse supported by Windows NTTM.

CD-ROM: Any device supported by Windows NTTM. Required forinstallation.

I/O ports: A parallel port may be used for connecting a printer.

Operating system: Microsoft Windows NTTM version 4.0 with Service Pack3, Workstation or Server.

Monitor: If the monitor will be used as a MicroSCADA monitor, it

should have a screen resolution of at least 1024x768

pixels and a screen refresh rate of at least 70Hz.

Network adapter card: Any network adapter card supported by Windows NT can

be used. See section 2.2.




13

3. Installing base sys-tems

Installation

Installation Guide

3

3. Installing base systems

This chapter describes how to install the MicroSCADA base system software on a

PC running the Windows NT operating system.

To ensure proper and secure operation, before starting the installation, always checkthat the environmental requirements set by the equipment are fulfilled (for example

power supply, temperature and relative humidity). Check also that all computers arefree from viruses.

This chapter contains the following sections:

3.1 An overview of the installation procedures and the MicroSCADA basesystem software.

3.2 Preparations: installing the hardware, the Windows NT operating

system and the X-server software (if needed).

3.3 Installing the MicroSCADA software packages: workstation, basesystem, tools, drivers and NETs.

3.4 Installing optional software products: Network Topology. Theinstallation of LIB 500 is described in the LIB 500 documentation.

3.5 Managing applications: adding, preparing and removing applications.

3.6 Installing the base system monitor as a MicroSCADA operatorworkstation: modifying the monitor settings and compiling fonts.

3.7 Managing MicroSCADA device drivers.

3.8 Editing the base system configuration files.

3.9 Administering the base system installation:

-Using the MicroSCADA Control Panel and Administrator-Start-up and shutdown management-Supervising MicroSCADA processes and errors

-Changing password, sharing resources, performance notes.

The installation of NETs (PC-NETs and DCP-NETs) in the base system is detailedin chapter 5. Upgrading from previous MicroSCADA revisions is discussed in

chapter 8.

3.1. Overview

Installation procedureThe installation of a MicroSCADA base system comprises the following steps:

• If a local area network will be used, installing the network adapter card.

• Installing the operating system.

• For the local area network, installing corresponding device drivers and protocols.

• Installing the PC cards used by MicroSCADA: NET cards, alarm units, PCLTAcards and radio clock cards.

• Installing the X-server software, Exceed, if MicroSCADA X-monitors or VS

remote monitors are shown on the base system computer display.

1MRS751853-MEN



14


3. Installing base systems Installation Guide

• Installing the MicroSCADA base product software.

• Installing optional products if such are used: LIB 500 and Network Topology.

• Adding and preparing of applications.

• Taking the PC monitor into use as a MicroSCADA operator workstation.

• Configuring, testing and starting the MicroSCADA drivers.• Modifying the base system configuration files to match the actual configuration.

• Administrative tasks: defining start-up type, changing password, sharing

resources, etc.

These installation steps are explained in detail in the following sections.

MicroSCADA software

The MicroSCADA software is delivered on two CDs. The first one contains theMicroSCADA base product software, the frontend software, the workstation

software, the LIB 500 standard application engineering software and the Network

Topology software. The other one contains the documentation of the products.




15


Installation

Installation Guide

3

The MicroSCADA base product software comprises the following softwarepackages:

Table 1:

Workstation This package includes the MicroSCADA workstation

programs. This software opens monitors to the MicroSCADAbase system computer.

System Base Software This software package includes the MicroSCADA kernel,

administration programs, a standard base systemconfiguration file (SYS_BASCON.COM), standard start-up

pictures and dialogs. The installation program creates a

directory structured as shown in Figure 3.1.-1, including an

application directory named TUTOR and one named WD.

System Base Tools This software package includes the application engineeringand system management tools.

Drivers These software packages include the device drivers used bysome of the devices connected to the MicroSCADA system.

The drivers are software modules, which handle the

communication between the operating system and differentdevices; in this case, PC cards. There are five MicroSCADA

drivers: a RAM driver for communication with DCP-NET cards

residing in the base system computer, an audio alarm driver, a

radio clock driver and a LON driver for PCLTA cards. Each

driver package contains the actual driver, a configuration tool

and associated files.

PC NET This software package includes the PC-NET program, a

standard initialisation file and a template for an on-line

configuration file.

DCP NET This software package includes the DCP-NET program for the

NET cards in the base system computer.



16






17


Installation

Installation Guide

3

3.2. Preparations

Installing LAN cards

If a local area network will be used and the network adapter card is not built-in onthe mother board of the base system computer, install the network adapter card as

described in the product manual of the network adapter card.

Installing operating system

Install the Windows NT operating system as described in the Windows NToperating system installation manual. Here are some notes of importance for

MicroSCADA:

The current version of MicroSCADA can not be installed on a server acting as a

primary domain controller (PDC) or a backup domain controller (BDC).

In the Express installation, the parameters are given default values. The size of the

virtual memory should be changed. The minimum recommended RAM size is 64MB (96 MB for large applications), smaller RAM size may result in degradedperformance. For small applications with low functionality and low performance

requirements, 32 MB RAM may be sufficient. On the other hand, big applicationswith high functionality and performance requirements may require more than 96

MB RAM. The virtual memory initial size setting in Windows NT should be at least

three times the size of the RAM memory. If the virtual memory initial size is notchanged at installation, this can be done in the Performance tab of System in theControl Panel.

As a LAN protocol, you must select TCP/IP if a LAN will be used for MicroSCADAcommunication or if Network Topology will be used.

MicroSCADA system administration - installation, manual start-up and shutdown,

etc. - requires a Windows NT user belonging to the Administrators group. Duringthe MicroSCADA installation, a user named MicroSCADA will be created

automatically. This user belongs to the Administrators group, and can be used for

system administration but should not be used for MicroSCADA operation.Therefore, for ordinary operators you should add one or more users belonging to the

Users group.

If the base system computer screen will be used for MicroSCADA monitors, the

display settings should be set as described in section 3.6. You can do it during theoperating system installation or later.



18



Installing PC cards used by MicroSCADA

A MicroSCADA base system computer may use a number of PC cards for variouspurposes:

• One or two DCP-NET cards for running the DCP-NET program.

• One or two PCLTA cards for communication with LON buses.• Alarm cards for audio-visual alarms.

• A clock card for time synchronisation.

The use of these cards requires the installation and configuration of a correspondingMicroSCADA device driver. The cards can be installed before or after installing the

MicroSCADA base system software, but you should install them before you

configure the corresponding MicroSCADA device driver. The installation of theDCP-NET cards and LON cards as well as the configuration of the corresponding

MicroSCADA device drivers is detailed in chapter 5. The installation of the alarmcards and clock card and the configuration of the MicroSCADA device drivers forthese devices are described in detail in chapter 7.

When installing the cards you should keep in mind that the I/O port addresses andthe IRQ level used by the cards must not be used by any other device in thecomputer. Each of the PC cards uses a block of I/O port addresses. The cards use I/ O port address blocks as follows:

DCP286I card: 3 I/O port addresses.

DCP386I card: 7 I/O port addresses.

PCLTA-10 card: 8 I/O port addresses.

ISA alarm card: 16 I/O port addresses.

PCI alarm cards: Cards select the necessary I/O port addresses automatically.

Clock card: 8 I/O port addresses.

An I/O port address used by a card may not be used by any other device in thecomputer. If two devices are allocated overlapping I/O port address ranges, RAM

addresses or IRQ levels, none of the devices will work properly.

Installing exceed

If VS remote monitors or X-monitors will be opened on the base system screen, theX server software (Exceed) has to be installed before the MicroSCADA base system

software is installed. The installation of the MicroTOPOLOGY software also

requires Exceed.

Install Exceed as described in the Exceed manual. You can also follow the

installation instructions described in chapter 6 of this manual.

3.3. Installing MicroSCADA base product software

General

The MicroSCADA Installation CD contains an installation program, which creates

the directory structure and copies the required files to your hard disk. The




19


Installation

Installation Guide

3

installation program also creates a new program folder by default namedMicroSCADA and three icons:

• The MicroSCADA Control Panel (see section 3.9).

• A MicroSCADA Monitor icon for opening MicroSCADA monitors.

• A MicroSCADA Notify icon for opening a notification window.Any previously installed MicroSCADA software does not need to be removedbefore a new installation. The old files will be overwritten, except for the followingones:

In the \sc\prog directory:

shutdown.cin

Installation preserves the old version of shutdown.cin.The new version is copied into same directory and named

shutdown$cin.

and in the \sc\sys\active_\sys_:PC_NET.CF1PC_NET.COMSYS_BASCON.COM

SYS_CONFIG.PARSYS_NETCON.COM

The applications located under the \sc\apl directory are not touched. The application

TUTOR and WD can be overwritten. The installation program asks whether to do

that or not.

Step-by-step description

To install the MicroSCADA base product software from CD:

Restart the computer to remove possible memory resident data.

Log on as a user with administrator rights.

Put the installation CD in the CD unit. Open the Windows NT Explorer, select

the drive with the installation CD and start the MS_842.EXE program in theMS_base directory by double-clicking the program name.

The dialog box in Figure 3.3.-1 appears on screen.



20



Click OK to continue the installation or Cancel to quit the installation.

A System Information dialog is shown. Click Next to continue.

If you decided to continue the installation, the dialog shown in Figure 3.3.-2.

appears.

The dialog box lists the software packages. The packages are named as follows:

Workstation = MicroSCADA Workstation software

System Base Software = MicroSCADA Base System software

System Base Tools = MicroSCADA Base System Tool software

DCP driver = The RAM driver package for the DCP-NET cardlocated in the base system computer

Flytech driver = The alarm driver package

PCLTA driver = The PCLTA driver package

PC31/PC32 driver = The PC3x radio clock driver package

PC-NET = The PC-NET software

DCP-NET = The DCP-NET software for the base system

computer




21


Installation

Installation Guide

3

A checkmark in the checkbox to the left of a package name indicates that it isselected for installation. By default only the MicroSCADA Workstation,MicroSCADA base system package and the engineering and application tools

package are selected.

If you are updating MicroSCADA to a newer revision, install also the driver

packages as they might have been changed. A new installation of driverpackages does not overwrite the existing driver configuration. Note however,that to take new drivers into use, the corresponding device driver configuration

program must be run. This is done from the MicroSCADA Control Panel.

Select the packages to be installed.

The installation program suggests a destination drive for the MicroSCADA

installation. If MicroSCADA has been installed before, the destination driveused in the previous installation is shown as default drive. Otherwise, the default

drive will be C:.

To change the destination drive, click the Change Drive... button (see Figure

3.3.-2), and select a new destination drive.



22



MicroSCADA must be installed on a disk drive physically located in the base system

computer. It can not be installed on a logical disk drive, e.g. a network drive.

Click Start to continue.

If a previous installation of the selected software package is detected, a dialoglike the one in Figure 3.3.-3 is shown. Click Continue to proceed with the

installation.

The installation program starts the installation of the selected software

packages. If you already have the packages installed on the disk, dialog boxesare shown which contain information on the existing packages. You can choose

to exit the installation procedure of the package or to continue with the newinstallation and overwrite the existing package.




23


Installation

Installation Guide

3

During the installation, a progress indicator and a text, see Figure 3.3.-4, informabout the installation of the packages.

A message box will inform you when a package has been installed.

After the installation of the selected packages a dialog box appears with a

question whether you want to add a folder and icons for the installed package.Click Yes to add the MicroSCADA icons.

Select the name of the folder in which you want to place the MicroSCADAicons. The default is MicroSCADA. This is asked during installation of theWorkstation package and System Base software. You can select an existing

folder or create a new one. Click the one you want to use in the list or type itsname. Click OK.

After the System Base Software has been installed you are asked to enter a

password for a user named MicroSCADA, see Figure 3.3.-6. The MicroSCADA



24



user will be created during the installation. It will belong to the Administratorgroup. It is the user that owns the MicroSCADA processes.

The MicroSCADA user will perform all references made by the processes. If

two base system computers will share resources, the MicroSCADA user shouldbe given the same password on both computers. The password can be changed

later from the MicroSCADA Control Panel. Note that this user name should notbe for other purposes than administration tasks.

If the MicroSCADA user already exists due to a previous installation, the

password is left unchanged.

Enter and confirm the password.

The other packages that were selected earlier are installed.

The procedure is following:

• A dialog with information of previous installation.

• Progress bar indicating installation proceeding.

• Message box with information of successful installation of the

package.

The installation is completed with two consecutive dialogs shown in Figure

3.3.-7 and Figure 3.3.-8. Click OK in both to complete the installation.




25


Installation

Installation Guide

3

During the installation, a log file of the installation procedure is written to

3.4. Installing optional products

Installing LIB 500

Refer to the LIB 500 documentation

Installing network topology

To install the Network Topology software package:

Load the installation CD.

Open the Explorer and select the D: drive.

Start the MT_540.EXE program in the Topology directory by double-clickingthe program name.

Follow the instructions on screen.

The installation of the Network Topology software follows the same procedure as

the installation of the base product software described in section 3.3.



26



3.5. Managing applications

General

During the installation of the MicroSCADA kernel software, two emptyapplications are created. The two applications are named TUTOR and WD.

You can add additional applications using the administration tools accessed from theMicroSCADA Control Panel. The MicroSCADA administration tools also provide

means for listing and removing applications (see section 3.9). When you add anapplication, the application directories for the new application are created. The start-up and initialisation pictures and dialogs are then copied to the application directory

apl_.

To view, ad, prepare or delete applications:

Open the MicroSCADA Control Panel by double-clicking its icon:

Click Admin.

Click Applications. The dialog in Figure 3.5.-2 appears.




27


Installation

Installation Guide

3

Adding applications

To add a new application:

Click Add in the Control MicroSCADA Applications dialog box.

A dialog named “Add new application” appears. See Figure 3.5.-3.

Type the name of the application to be created.

Click OK.

The new application directory and its sub-directories are created under the \sc\apl

directory. The initialisation and start-up pictures and dialogs are copied into the pict

sub-directory of the new application.



28



Preparing applications

Preparing an application means copying necessary start-up and initialisation files tothe application directory. When an application is added as described above, it is at

the same time prepared and no further preparations are required. Likewise, theTUTOR and WD application created during the installation were prepared.

However, if you are updating MicroSCADA and have applications, you need toprepare them again to be able to properly access to the tools.

If LIB 500 will be used, the applications must also be prepared for LIB 500.

To prepare an application:

Open the dialog box Control MicroSCADA Applications.

Select the application to be prepared.

Click Base Tools.

Choose one of the following options:

Full prepare to copy all initialisation files and pictures to the applicationdirectory. Possible existing files are overwritten.

Limited prepare to copy initialisation files but not the APL_INIT andAPL_START pictures. Use this option if you wish to keep the

existing APL_INIT and APL_START files. For instance, if you

have prepared the application for LIB 500, you should useLimited prepare.

To prepare an application for LIB 500:

Follow the steps 1 and 2 as in preparing an application.

Click LIB 500.

Refer to the LIB 500 documentation to complete the preparation.

Removing applications

To remove an existing application:

Open the dialog box Control MicroSCADA Applications.

Select the application to be removed.

Click Remove.

The selected application directory and its sub-directories will be deleted.




29


Installation

Installation Guide

3

3.6. Configuring the base system operator workstation

General

A MicroSCADA base system operator workstation is a computer running theMicroSCADA base system software. The display of the computer can be used for

showing MicroSCADA monitors.

If the base system display is used as a MicroSCADA operator workstation, thecolour palette of the display should hold at least 256 colours. You can check andmodify the display settings during the installation of the operating system or later

using the Display Settings dialog.

In addition, if the MicroSCADA operator workstation is used for showingMicroSCADA monitors of the type X or VS remote, X-software must be installed

and MicroSCADA fonts must be compiled for the X software.

If the display will not be used for MicroSCADA monitors the following operations

are not needed.

Display settings

If the colour palette is not set for at least 256 colours, modify the display settings asfollows:

Open the Control Panel (click Start, point Settings and click Control Panel).

Double-click the icon that represents the Display properties.

Select the Settings page, see Figure 3.6.-1.

Select 256 Colors or more, in the Color Palette.

Test the setting by clicking Test.

If the test was OK, accept the change and exit the Display Properties by clicking

OK.



30



Compiling fonts

Font compilation is required if the MicroSCADA operator workstation will be used

for showing MicroSCADA monitors of type X or VS remote.

During the base software installation, the MicroSCADA fonts were installed as files

in bdf format in the directory \sc\fonts\scada_font\x. Compilation is done from theExceed software. Compile the fonts as described in the Exceed manuals and in the

description in section 6.3.

Configuring MicroSCADA

To be able to open a MicroSCADA monitor a MON object has to be defined in thebase system configuration. The MicroSCADA system requires one MON object permonitor. The delivered SYS_BASCON.COM configuration file contains thedefinition of 10 MON objects for the application TUTOR, 5 “X” type objects and 5

“VS” type objects. See the System Configuration manual, chapter 9.




31


Installation

Installation Guide

3

3.7. Managing device drivers

General

During the installation of the base system software, you had the possibility toinstall the MicroSCADA device driver packages. Even if the driver packages were

selected for installation, the drivers are not yet ready for use, but must beconfigured first. Configuring drivers means that they are given information of the I/ O addresses and interrupt levels used by the hardware devices, as well as someother configuration data. When a driver has been installed and configured it shouldbe tested and configured for automatic start-up. Hence, the entire procedure is asfollows:

• Installing the driver packages.

• Configuring the drivers. The drivers cannot be configured until the correspondinghardware has been installed. The installation of the hardware is described

elsewhere in this manual - the installation of the DCP cards and PCLTA cards in

chapter 5, and the installation of the alarm cards and radio clock cards in chapter

7. The configuration of the device drivers is detailed where the correspondinghardware installation is described, i.e., in chapters 5 and 7. When updating adriver package to a new version, you need not configure the device driver again ifyou will use the same configuration as before. Instead, use the Update option in

the device driver configuration tool.

• Testing the drivers.

• Defining automatic start-up.

The MicroSCADA Device Driver Configuration tool allows you to:

• View the version of the installed device driver package.

• Install a new device driver package.

• Remove an installed device driver package.

• Configure a device driver for the first time.

• Reconfigure a device driver.

The MicroSCADA Device Driver Configuration tool is started from the

MicroSCADA Administrator tool

Using driver installation setup tools

The driver management tools are accessed from the MicroSCADA Administrator

tool which in turn is accessed from the MicroSCADA Control Panel. To enter thedevice driver management tools:

Open the MicroSCADA Control Panel by double-clicking its icon:

Click Admin.

Click Drivers.



32



The following dialog appears:

Select the device driver you wish to view, configure or manage by clicking thecorresponding button.

MS-CRAM = device driver for the DCP-NET card

MS-AA = device driver for the Flytech FPC-046 alarm card.The device drivers, and installation instructions, for the

two PCI audio alarm cards are provided by theirmanufacturers and are not included in the MicroSCADA

device driver package.MS-PC3x = device driver for radio clock card

MS-PCLTA = device driver for the PCLTA card




33


Installation

Installation Guide

3

Now the MicroSCADA Device Driver Configuration tool for the selected driverappears, see Figure 3.7.-2.

The tool provides the following options:

Driver Version This selection provides information about the version of the

present driver configuration program, the version of the

configured driver if any, and the version of the driver in theinstalled package. This option is useful if you have installed anew device driver package and wish to compare it with a driver

you have already configured. See Figure 3.7.-3.

Update Driver This selection replaces the configured device driver with the

driver from the previous installed package installed driver. Theconfiguration settings remain unchanged. Use this option when

you have installed a new version of a driver package.

Add Device Configuring a device driver for a new device. The device driverconfiguration is detailed in the context where the hardware

installation of the device is described, i.e., in chapters 5 and 7.

Remove Device Removing an existing device configuration.

Change Settings Re-configuring an already configured device.



34



Testing the drivers

After configuring the drivers as described in chapter 5 and chapter 7, they should betested.

Reboot the system to make the settings take effect.

If you are configuring the drivers for the first time, they are not started automati-

cally after booting, but must be started manually. This is to avoid problems in case

of problems with the configuration settings.

To start a driver:

Open the Control Panel (click Start located in the taskbar, point Settings and

click Control Panel).

Double-click the icon that represents the Devices.

Select the driver from the list of Devices (see Figure 3.7.-4).

Click Start.

If an error message appears, or if the device driver does not seem to work, theprobable cause is conflicting settings. Settings may conflict due to the followingtwo reasons:

• The hardware settings do not match the values given during the device driver

configuration. An example of this could be that the card has been set to use theinterrupt level 5 but the device driver has been given the value 7 for the interrupt

level.

• The settings conflict with other settings in the computer. An example could bethat the device uses the same interrupt level as another device in the computer.

When such problem occurs, first check the event log of the operating system for

more information. The Event Viewer is used for browsing the event log.

To start the Event Viewer:

Click Start (located in the taskbar).




35


Installation

Installation Guide

3

Point Programs.

Point Administrative Tools.

Click Event Viewer.

To investigate in detail how your system is configured use the Windows NTDiagnostics program. To avoid problems in the first place it is recommended to have

this program run before the installation and configuration of the devices.

To start the Windows NT Diagnostics:

Click Start (located in the taskbar).

Point Programs.

Point Administrative Tools.

Click Windows NT Diagnostics.

If no error message appears, the device driver has started and the installation can beregarded as successful as far as the operating system is concerned. However, theoperation of the driver should still be tested by running MicroSCADA.

Configuring automatic start-up

If the device responds properly, the device driver start-up type should be setautomatic. This means that the device driver is started automatically together withthe operating system:

Open the Control Panel (click Start located in the taskbar, point Settings and

click Control Panel).

Double-click the icon that represents the Devices.

Select the driver from the list of Devices.

Click the Startup.

Change the startup type to Automatic (see Figure 3.7.-5).

Click OK.



36



3.8. Editing configuration files

SYS_BASCON.COM

The system configuration of the MicroSCADA base system is defined in the

SYS_BASCON.COM configuration file residing in the \sc\sys\active\sys_directory. The file is a text file containing SCIL statements for creating the base

system (B) objects. The System Base software package contains twoSYS_BASCON.COM template files, one for configuring a single base system andone for configuring a hot-stand-by base system. The template file for a single base

system, SYS_BASCON$COM, is during installation copied toSYS_BASCON.COM if the SYS_BASCON.COM does not previously exist. Thetemplate file for hot-stand-by systems is called SYS_BASCON.HSB.

The SYS_BASCON$COM template file defines a system configuration aspresented in Figure 3.8.-1. The configuration consists of an application called“TUTOR”. Two PRI objects, one “normal” and one “transparent”, are connected to

the Windows NT 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 internalDCP-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.




37


Installation

Installation Guide

3

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.8.-1.

The contents of the SYS_BASCON$COM file is listed below. Some configurationdefinitions 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 basesystem object.

To edit the current SYS_BASCON.COM:

Open the MicroSCADA Control Panel.

Click Admin.

Click Config.

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

to the System Configuration manual to learn more about how to configure

MicroSCADA.

;File: Sys_bascon.com

;Description: Standard Base system configuration file

;Version 8.4.4

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



38



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

;Base System Object

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

#CREATE SYS:B = List(-

SA = 209,- ;Station address of base system ND = 9,- ;Node number of base system

TM = "SYS",- ;Time Master, SYS or APL

TR = "LOCAL",- ;Time Reference, LOCAL or UTC

DN = 1,- ;Default NET node number

DS = "STA",- ;Default STA type: E.G. STA,RTU,SPA,REX

DE = 0,- ;DDE server 0=disabled, 1=enabled

PC = 6000,- ;Picture Cache (kB)

RC = 1000,- ;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,- ;1=Enabled, 0=Disabled

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

2=INFORMATION, 3=AUDIT_SUCCESS, 4=AUDIT_FAILURE)

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


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


-

FS = "NEVER") ;File sync. criteria:

NEVER,MAINT,SET,CHECKPOINT,ALWAYS

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

;Communication Links

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

#CREATE LIN:V = LIST(- ;Link to DCP-NET (requires DCP driver)

LT = "RAM",- ;Link type

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(- ;Link to other SYS or LAN frontend (requires TCP/IP)

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




39


Installation

Installation Guide

3

#CREATE NOD:V = LIST(- ;Node for LAN frontend or SYS

LI = 2,-

SA = 202)

;#CREATE NOD2:B = %NOD

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

;Printers

;#do Read_Text("sys_/pr_default.dat") ;This line is needed for the

transparent printer below

;#CREATE PRI:V = LIST(- ;Transparent type printer

; TT = "LOCAL",- ;Translation type

; DT = "TRANSPARENT",- ;Device type

; OJ = 1,- ;Printer opened on job basis

; DC = "LINE",- ;Device connection: WORKSTATION, LINE OR NET

; CS = %CS,- ;Control sequences

; SD = "\\My_NT\My_Printer",- ;System device name

; LP = 66) ;Lines per page

;#CREATE PRI1:B = %PRI

#CREATE PRI:V = LIST(-

TT = "LOCAL",-

DT = "NORMAL",-

DC = "LINE",-

SD = "\\My_NT\My_Printer",-

LP = 66)


#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 PRI:V = LIST(- ;Required if HP of application is "EVENT_LOG"

(History logging Policy)

; TT = "LOCAL",-

; OD = "LOG",- ;Output destination (LOG, PRINTER)

; LL = "DAY",- ;Log Length (DAY, WEEK, MONTH)

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

; LP = 0)


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

;Monitors

#LOOP_WITH I = 1..5

#CREATE MON’I’:B = LIST(- TT = "LOCAL",- ;Translation type

DT = "X") ;X monitor

@MON_MAP(%I) = -1

#LOOP_END

#LOOP_WITH I = 6..10

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

TT = "LOCAL",- ;Translation type

DT = "VS") ;Visual SCIL monitor

@MON_MAP(%I) = -1

#LOOP_END

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

;Applications



40



;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

#CREATE APL:V = LIST(-

TT = "LOCAL",- ;Translation Type

NA = "TUTOR",- ;Name of application directory

AS = "HOT",- ;Application state (COLD,WARM,HOT)

PH = %l_Global_Paths,-

-; PQ = 15,- ;Number of parallel queues/ Needed in COM500 Applications

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

Needed in COM500 Applications

HB = 0,- ;History buffer size

SV = %SV,- ;System variable (RESERVED)

CP = "SHARED",- ;Color Allocation Policy

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

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

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

0=Disabled)

MO = %MON_MAP,- ;Monitor mapping

PR = (1,2,3)) ;Printer mapping

#CREATE APL1:B = %APL

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

; TT = "LOCAL",- ;Translation Type

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

; AS = "HOT",- ;Application state (COLD,WARM,HOT)

; PH = %l_Global_Paths,-

; HB = 0,- ;History buffer size

; SV = %SV,- ;System variable (RESERVED)




41


Installation

Installation Guide

3

; CP = "SHARED",- ;Color Allocation Policy

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

compatibility

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

"NONE")

; EE = 0,- ;System Events & Operating System Events (1=Enabled,

0=Disabled)

; 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")

#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"

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

;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 = SYS:BND

#set nod’i_system_node’:bnn = %t_lan_node_name

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

;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

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



42



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

Refer to the System Configuration manual to learn more about how to configure

MicroSCADA.

Setting parameters in 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-upbefore the execution of SYS_BASCON.COM. SYS_CONFIG.PAR can be editedwith a text editor.

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

specifies the size of the global memory pool in megabytes (MB). Possible valuesare: 4, 8, 12, 16, 20, 24,...., that is a value divisible with 4. Default, if no value isgiven in SYS_CONFIG.PAR, is 64 MB. For example the line:

MEMORY_POOL_SIZE = 100

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

specifies the start address of the memory pool. The start address (default value30000000) should be changed (by trial and error or examining the DrWatson log) to

a new value if the start of an external program (Application Extension Program orIntegrated 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 leading zeroes. Any value between20000000 and 6F000000 may be tried. A good value will be found quickly, ifsequence 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 onMicroSCADA configuration, such as number of monitors or network connections

etc.

These parameters define the translation of the CLOSED, OPEN and MIDDLE states

returned by the program interface function SCIL_Get_Switch_State.

Setting the parameter = 1 enables the option "asynchronous shadow receiver" in

HSB files for avoiding degradation of throughput in some HSB configurations. The

feature should be enabled if "cross-shadowing" is used, i.e., an application in basesystem A is shadowed to an application in base system B, and an application in basesystem B is shadowed to an application in base system A.




43


Installation

Installation Guide

3

Configuration of local memory pool

There are three configuration parameters in SYS_CONFIG.PAR concerning localmemory pools to consider:

PICO_MEMORY_POOL_SIZE Determines the size (as megabytes) of

the local memory pool of all themonitor processes in the system. Thedefault value is 16 MB.

REPR_MEMORY_POOL_SIZE Determines the size of the local

memory pool of all repr processes.The default value is 8 MB.

PRIN_MEMORY_POOL_SIZE Determines 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 thedialog "SCIL Application Error/Memory Pool Exhausted" is shown. The dialog

shows a critical error with information about which pool caused the error. Theinformation is either "Local memory pool exhausted" or "Global memory pool

exhausted".

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 theinstallation of the System Base Software package. The contents of theSYS_CONFIG$PAR is:

; File: Sys_config.par

; Description: Configuration for ’static’ base system parameters; leading ’;’ indicates commented line

; Version 8.4.4

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

;

;MEMORY_POOL_SIZE = 64 ;Must be a multiple of 4 (MB)

;MEMORY_POOL_ADDRESS = 30000000 ;Memory pool start address

;PICO_MEMORY_POOL_SIZE = 16 ;Memory Pool for Monitor processes

;REPR_MEMORY_POOL_SIZE = 8 ;Memory Pool for Report processes

;PRIN_MEMORY_POOL_SIZE = 4 ;Memory pool for Printer processes

;

;

;ASYNCHRONOUS_SHADOW_RECEIVER = 1 ;Should be used in cross-shadowing systems

;

;ANALOG_SWITCH_STATE_OPEN = 2 ;The semantics for MicroTOPOLOGY of AI

;ANALOG_SWITCH_STATE_CLOSED = 1 ;process objects used for indicating the;ANALOG_SWITCH_STATE_MIDDLE = 0 ;state of a switching device

3.9. Base system administration

General

Most of the operations described below are done in the MicroSCADA Control Panelor in the MicroSCADA Administrator. These tools can only be run on theMicroSCADA base system computer.



44



3.9.1. Using MicroSCADA control panel and administrator

MicroSCADA control panel

To open the MicroSCADA Control Panel:

Double-click the MicroSCADA Control Panel icon.

Figure 3.9.1.-1 shows the dialog box presented for the user.

The MicroSCADA Control Panel provides buttons for starting MicroSCADA

manually and for stopping MicroSCADA, and for accessing the MicroSCADA

Administrator tool.

To exit the MicroSCADA Control Panel dialog without choosing any of theoptions, click Quit.

MicroSCADA administrator

To open the MicroSCADA Administrator:

Click Admin in the MicroSCADA Control Panel.




45


Installation

Installation Guide

3

The MicroSCADA Administrator is shown in Figure 3.9.1.-2.

Options of the MicroSCADA Administrator dialog:

Applications Opens a dialog used for managing applications

Service Opens a dialog for setting start-up type for MicroSCADA

service

Password Opens a dialog for changing the password for the MicroSCADAuser

Autologon Opens the dialog ‘Windows NT Automatic Logon’. (See alsoSystem Management manual.)

Config Opens the Notepad editor for editing SYS_BASCON.COM

View Opens a dialog showing MicroSCADA processesDrivers Starts the driver configuration programs

3.9.2. Start-up and shutdown management

Starting MicroSCADA manually

To be able to start MicroSCADA manually, you must be a user belonging to theAdministrator group.



46



To start MicroSCADA manually:

Click Start in the MicroSCADA Control Panel.

Click OK in the message which appears, see Figure 3.9.2.-1.

MicroSCADA can also be started with the operating system tool for starting and

stopping services.

MicroSCADA runs as a Windows NT service which means that the MicroSCADAprogram runs in the “background”. No application icon is shown in the task bar. You

can check that MicroSCADA is running by viewing the running programs in the

Task Manager tool of operating system. To view explicit MicroSCADA processes,use the View option in the MicroSCADA Administrator. The events related to the

service function can be viewed in the Event Viewer. The MicroSCADA kernelcontinues to run in the background even if a user logs out.

Stopping MicroSCADA

To be able to stop MicroSCADA, you must be a user belonging to the

Administrators group.To stop MicroSCADA:

Click Stop in the MicroSCADA Control Panel.

When MicroSCADA has stopped, the following dialog box appears.

Click OK in the message box.

Do not shut down or restart the computer while MicroSCADA is running.




47


Installation

Installation Guide

3

In exceptional situations, for example if MicroSCADA does not start properly dueto an error in the SYS_BASCON.COM file, you may wish to stop MicroSCADAwithout running the normal shutdown procedure. To do this, click the Forced Stop

button in the MicroSCADA Control Panel.

When MicroSCADA is stopped, open monitors are closed. This may cause error

messages in the error log.

For more information on the shutdown procedure, see Shutdown Managementbelow.

Start-up management

MicroSCADA can be started manually or automatically. When using automaticstart-up of MicroSCADA, MicroSCADA is started directly after the computer hasbeen switched on or restarted and the operating system has started.

To select automatic or manual start-up:

Click Service in the MicroSCADA Administrator.

The following dialog box appears:

Select Automatic startup, Manual startup or Disabled. Disabled means that

MicroSCADA cannot be started.

Click OK.

Automatic logon

Automatic Logon means that a user is automatically logged on when the computeris started. To enable automatic logon:

Select the AutoLogon button in the MicroSCADA Administrator.

The dialog box in Figure 3.9.2.-4 appears.



48



Enter the name and password of the user.

Select Automatic Logon Enabled.

Click OK.

To remove the automatic logon select Automatic Logon Disabled. This action alsorequires the password of the user for which automatic logon is defined.

Shutdown management

When Stop has been selected in the Control Panel, the shutdown procedure starts the

SCIL program stored in the file shutdown.cin. The file is located in the \sc\prog\execdirectory. When this program has been executed to the end, or when 2 minutes have

elapsed since the shutdown command was given, MicroSCADA is stopped.

The shutdown.cin file included in the MicroSCADA base product software package

contains a SCIL program which closes all running applications and links. By editingthe program file with text editor, the MicroSCADA system administrator can addother functions. However, the program must not require more time than 2 minutes

to execute.

When Forced Stop has been selected, MicroSCADA is stopped immediately withoutexecuting the SCIL program stored in the shutdown.cin file.

3.9.3. Supervising MicroSCADA

Viewing processes

To view the currently running MicroSCADA processes, click the View button in the

MicroSCADA Administrator.

The MicroSCADA Administrator views process name, memory address and CPUtime used by the processes during the session. The execution priority of a specific

process can be inspected by selecting the process from the list. The execution

priority is displayed as a checked option under priority in the dialog. To updatevalues click Refresh.




49


Installation

Installation Guide

3

MicroSCADA error supervision

The MicroSCADA workstation error messages are stored in an error log file namedSYS_ERROR.LOG and located in the SYS_ directory. The messages are alsodisplayed in the MicroSCADA Notification window as they are produced. You can

open up to 8 MicroSCADA Notification windows per base system. Each windowcan display the last 1000 messages produced. To open a Notification window on the

base system:

Double-click the “MicroSCADA Notify” icon.

How to open MicroSCADA Notification windows on workstations is described inchapter 6.



50



3.9.4. Miscellaneuos

Enabling shared resources

The MicroSCADA base system can use shared resources - files, printers - with other

computers on the LAN. To enable a MicroSCADA base system to use a shared

resource on another computer:

Add a user named MicroSCADA in the other computer and assign it the samepassword as the password of the MicroSCADA user defined in the base systemcomputer. The user should belong to the User or Administrator group.

Add the MicroSCADA user to the list of users for the specified sharedresources.

MicroSCADA accesses the shared resources in the other computer by using UNCreferences.

Changing passwordThe password of the MicroSCADA user entered during installation can be changed.To change it:

Click Password in the Administrator menu.

The same dialog appears as during the MicroSCADA software installation.

Enter the new password and confirm it.

Click OK.

Performance notesTo ensure maximum performance when running MicroSCADA:

• Use a blank screen saver. Other screen savers may cause a significant CPU load

• Set Priority Boost to None in the System tool of Windows NT 4 (click located in the taskbar, point Settings and click Control Panel, double-clickSystem, select the Performance page).




51

4. Installing and config-uring LAN

Installation

Installation Guide

4

4. Installing and configuring LAN

About this chapter

This chapter describes the general principles for installing the network adapter card

and the software needed. It also briefly describes the configuration of the LANnodes on a TCP/IP network.

Network adapter card

Each computer on the LAN contains a network adapter card and software forhandling the card and the protocols used.

In the NT computers you should insert the network adapter card before you install

the operating system. Some computers are equipped with a built-in network adaptercard. Refer to the product manuals of the used card. The LAN software is installed

and configured during the installation of the operating system.

In the PAC 500 computers, the network adapter card is built-in. The LAN softwareis installed during the installation of the operating system.

In the PC/DOS computers used by communication frontends, you can insert thenetwork adapter card before or after you have installed the operating system. Referto the product manuals of the used network adapter card. The used LAN software

should be PC/TCP. Install this software as described in the PC/TCP manual.

IP address

Each node or host in a TCP/IP network has a unique identifier, an IP address. The

IP address is composed of four numbers in the range from 0 to 255. The numbers are

separated with dots.

The address is requested during the configuration of the LAN software, i.e., duringthe installation of the Windows NT operating system in the base system andworkstation computers, and during the installation of the PC/TCP software in

frontends.

The IP addresses of the MicroSCADA base system, workstation and frontendcomputers must comply with the addresses of other nodes on the network. Consult

your local area network administrator for valid IP addresses and other LANconfiguration issues.

Host namesDuring the installation of the Windows NT operating system, you will give thecomputer a name. This is the computer name for the NETBIOS protocol under

which the computer will be recognized on the LAN. Note that this name is not thesame name as the host name used by TCP/IP. The host name is given whenconfiguring the TCP/IP protocol.

1MRS751853-MEN



52


4. Installing and configuringLAN

Installation Guide

You can read the host name and IP address of computer by entering:

in a Command Prompt window on a computer with Windows NT or at the DOSprompt on a computer with DOS. In Windows NT you can also check the settings

from the Network Tool in the Control Panel.To be able to use host names in the communication frontend computers the namesto be recognized have to be defined in a host table on the computer. The host table

maps the host name to an IP address. The name and location of the hosts files are

defined during the installation of the PC/TCP software.

Below is an example of a host table. Here each node has two names, one in lower

case letters and one in upper case letters. The items in a host table are separated byspaces or tabs.

128.231.159.20 mscada MSCADA

128.231.159.21 unix UNIX

128.231.159.22 pcx PCX128.231.159.23 mw MW

128.231.159.25 mfl1 MFL1

128.231.159.26 mfl2 MFL2

The same mechanism can also be used in Windows NT. There are however, other

mechanisms such as DNS that can be used. Consult your network administrator forinformation on solutions applied to your network.

In a communication frontend, the host table should contain names of all base

systems that will use the frontend.

Configuring MicroSCADA for LAN

In the base systems connected to LAN, define a LIN object of type LAN. One object

is enough for all LAN connections. Refer to the System Configuration manual,chapter 7.

In the frontends, define the IP addresses or host names of the connected base systems

in the MFL.DAT file of the frontend.

Testing the LAN communication

Use the ping utility to test the connectivity on the LAN and determine if a host isavailable and functional. The syntax is:

where ’host’ is the IP address or node name of a computer on the network. If the

computer responds, a message is produced with some diagnostic information.

Ping 192.10.0.210

Reply from 192.10.0.210: bytes=32 time < 10ms TTL 255

For more information on ping and how to use it, see the on-line help of the utility.




53

5. Installing processcommunication system

Installation

Installation Guide

5

5. Installing process communication system

This chapter describes:

5.1 The process communication system: the communication units (NETs),

the communication lines and the NET configuration.5.2 The installation of PC based NETs and PCLTA cards.

5.3 The hardware and software installation of internal NETs.

5.4 The hardware and software installation of communication frontends.

5.5 The installation of NET connections: cables, modems, etc.

The upgrading from a previous NET program version - 7.3, 8.1 or 8.2 - using the

existing preconfiguration is described in chapter 8.

If you are using System Configuration tool, please refer to MicroSCADA System

Configuration manual.

5.1. Overview

NET unit types

The process communication in MicroSCADA is handled by the NET

communication units. See Figure 5.1.-1. MicroSCADA has two types of NET

communication units software:

• DCP-NET. DCP-NET runs on a separate communication card with its own

processor. The communication card, here called DCP-NET card, belongs to aspecific ISA bus based card family called DCP. The DCP card is manufactured byEmulex.

• PC-NET. The PC-NET runs on the base system computer. PC-NET supports:

ACP (the MicroSCADA internal protocol), LonTalk, SPA, IEC 870-5-101 master

and slave, IEC 870-5-103 master, IEC 1107, RP570 master and slave, RP571master, ADLP80 slave and LCU 500.

DCP-NET units may be situated within the base system computer, or within the

communication frontends. There can be up to four DCP-NET units in acommunication frontend. A base system computer can contain up to two DCP-NET

units.

Each DCP-NET unit has its own communication program, which contains a unitspecific preconfiguration. The program is stored on disk in the host computer and

loaded to the RAM memory of the unit at startup.

1MRS751853-MEN



54


5. Installing process com-munication system

Installation Guide

Figure 5.1.-1 illustrates the NET types and their connections. The NETcommunication lines are described below.

Note that the last setup of hardware in the picture allows the use of all eight NETlines of the PC-NET. The third setup of hardware restricts the number of PC-NET

lines due to lack of IRQs. The channels of the PCLTA card occupy one IRQ each, just like the COM ports of the computer.

Communication lines of DCP-NET units

The DCP-NET cards have 8 serial ports, numbered 1... 8. Each of the serial lines canbe connected to the process, to another communication unit, a frontend, a base

system or a printer. The device, which can be connected to a line, depends on theprotocol assigned to the line in the NET configuration.




55


Installation

Installation Guide

5

Besides the eight serial lines, the DCP-NET program uses logical line forcommunication within the computer where the card is loaded. This line is used for:

• Communication between the NET and the host computer (base system or

communication frontend).

• Communication between the NETs within the same host computer (base systemcomputer or frontend).

The serial lines have the following priority order (from highest to lowest priority):3, 4, 1, 2, 5, 6, 7, 8. Lines with a high priority are recommended for base system andNET connections.

Communication lines of PC-NET units

The PC-NET use the serial ports (COM ports) of the PC or COM ports of a multiportserial card and the channels of possible PCLTA card(s) as communication lines. A

base system computer can use up to 4 channels. Hence, a PC-NET may have in all

up to 8 NET lines. The PC-NETs communicate with the host base system through

line 13, which is a logical link.

The COM ports of the PC, if used, have NET line numbers 1...4. By default, line

number 1 corresponds to COM1, line number 2 to COM2, and so on. These lines canbe connected to the process (SPACOM and S.P.I.D.E.R. RTUs), other NETs,

frontends and base systems. The COM ports are taken into use as NET lines byassigning them protocols in the PC-NET configuration.

Additional COM ports for use with PC-NET is obtained by installing a multiport

serial card. A suitable serial card for this purpose expands one PCI slot to 8 serialports. The numbering of the added COM ports is done as the driver of the card is

installed. A realistic case would be two physical COM ports numbered 1 and 2. The

numbering of COM ports of the serial card would then be 3... 10. Assigningappropriate lines of the PC-NET to COM ports is done by means of the SD attribute,see the System Objects manual (Chapter 13: NET LINES.).

The NET line numbers of the channels can be freely chosen among the free linenumbers. If no COM ports are used, the numbers 1 to 8 can be chosen. If four COMports are used, the numbers 5 to 8 are available. The NET lines are taken into use as

LONWORKS channels by assigning them the LonTalk protocol. During the PCLTA

card driver configuration, the channels are given a device number and a devicename. See section 5.2. By default, the NET line numbers of the channels are the

device number + 1, but this relation can be changed in the PC-NET configuration. Ifthe PCLTA card driver is configured as recommended in this manual, the channelswill correspond to line numbers 1... 4, but this line numbering can be changed in the

NET configuration.

NET program configuration

By configuring the NETs, the NET programs get information about themselves and

the environment. The configuration of a NET unit specifies the node number and thestation address of the unit itself, the protocols used on the lines, the devices

connected to them and the communication properties.

Concerning the DCP-NET units, a NET specific configuration is included in theprograms. This configuration is called preconfiguration and it specifies, among

other things, the node number of the unit (default = 1). The preconfiguration serves



56



Installation Guide

as a default configuration. It can be edited using the NET PRECONFIGURATIONtool or with a DOS program named NETCONF.

The PC-NET program contains no preconfiguration, but at startup the PC-NET

program reads an initial configuration from a text file. The initial configuration filecontains only the most elementary definitions.

Generally, it is necessary to make changes on-line using SCIL, after the NET unit

has started. This applies especially to the PC-NETs, which are almost completelyconfigured with SCIL. The SCIL configuration is done using SCIL commands andthe communication system objects. The SCIL configuration is not stored, but has to

be repeated after each restart of the NET. For more information on this subject seeSystem Configuration Chapters 3 and 8.

5.2. Installing PC-NET software and PCLTA cards

Overview

The installation and configuration of a PC-NET in a base system comprises thefollowing steps:

• Installing and configuring the PC-NET software.

• Installing multiport serial card if such is to be used.

• Installing PCLTA cards if LonTalk protocol will be used.

• Starting and configuring the NET.

The installation of the PCLTA cards is described in this section since the use ofPCLTA cards is closely related to the PC-NETs

5.2.1. Installing and configuring PC-NET software

Installing PC-NET software from disk

The PC-NET software is installed during the installation of the MicroSCADA

software package. See Chapter 3. To install it, it has to be selected in the base system

installation program. If it was deselected during the first installation, it can beinstalled later by re-starting the installation procedure and de-selecting all other

packages except the PC-NET software. The program is installed into the PC-NETdirectory with the name PC_NETS.EXE.

Editing initial configuration file

When the PC-NET program is started, it reads an initial configuration file, the file

PC_NET.CF1, which is stored in the SYS_ directory. The PC_NET.CF1 filedefines the basic communication nodes and addresses to enable the communication




57


Installation

Installation Guide

5

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

The possible objects are:

Edit the PC_NET.CF1 file in a text editor and insert the following definitions:

• The node number (local_node.nn) and station address (local_node.sa) of the PC-

NET. Default: NET number = 1, station address = 201

• The node number (ext_node(1).nn) and station address (ext_node(1).sa) of the

base system where the NET will be running. Default: node number = 9, stationaddress = 209

• The node number (ext_apl(1).nn) and application number (ext_apl(1).an) of the

application that the NET will initially communicate with (an application withinthe same base system). Default: node number = 9, application number = 1.

In case the PC_NET.CF1 file is missing when the PC-NET unit is started, the default

configuration mentioned above 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 ; the node number of the PC-NET

ext_node(1).sa=209 ; the station address of the base system

ext_node(1).nn=9 ; the node number of the base systemext_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 othernodes and applications, must be done with SCIL after the NET has been started.

5.2.2. Installing multiport serialcard

As PC-NET supports 8 communication lines, additional COM ports are required ifcommunication is to be established over more than 4 serial lines. The multiport

serialcard is installed in a PCI slot of the PC. The 8 COM ports obtained occupy oneIRQ. The numbering of the COM ports is handled during installation of the card-

driver. As to the installation procedure, refer to the installation manual of the

multiport serialcard. The serialcard model that has been tested and verified is namedRocketPort®, made by Comtrol Corporation.

5.2.3. Installing PCLTA cards

General

A PC-NET utilises an ISA bus card called PCLTA-10 (PC LonTalk Adapter) or a

32-bit PCI card called PCLTA-20. A PCLTA card may have one or two channels,thus allowing the connection of one or two transceiver cards, see Figure 5.2.3.-1.

• local_node The PC-NET program itself

• ext_node An external node (the base system where the NET is situated)

• ext_apl The application in the base system where the NET is situated



58



Installation Guide

Each of the channels will be a NET line connected to a star coupler of a LONWORKS network.

The PCLTA-20 adapter includes either an integral twisted pair transceiver or an

SMX transceiver (Model 74405) interface. For models with an integral twisted pairtransceiver, the network connection is made via a removable screw terminal block.

The use of the PCLTA card(s) requires the installation and configuration of aMicroSCADA or an Echelon device driver. During the device driver configuration,each channel is given a device number. By default, the NET line numbers of thechannels will be the device number plus 1.

During the driver installation, you are requested the I/O base addresses of the cards.

These addresses must coincide with the addresses set physically on the cards.

Installing and configuring the PCLTA-20 adapter

There are different versions of the PCLTA-20 installation software, one for

Windows 95/98, one for Windows NT and one for Windows 2000 Professional/ Server. (Information on how to install the adapter in Windows 2000 is described insection 5.2.5.)

Each version installs the files required by the associated Windows operating systemto recognise the PCLTA-20 adapter, as well as the downloadable NSI (network

services interface) and MIP (Microprocessor Interface Program) images.

Installation of the software must occur before insertion of the PCLTA-20 adapter

into a PC’s slot.




59


Installation

Installation Guide

5

Installation software is provided in the Connectivity Starter Kit Model 58030-01(which must be purchased separately from Echelon Corporation), and provides asoftware-based control panel and a software driver for Microsoft Windows 95/98 or

NT operating systems. Installation software is also available on Echelon’s web site

at www.echelon.com/support.

Further software and hardware installation and PCLTA-20 device driverconfiguration instructions are available in the manual LONWORKS

® PCLTA-20 PCI

LonTalk Adapter User’s Guide, which is available on Echelon’s web site.

The MicroSCADA Technology manual Connecting LONWORKS®

Devices to

MicroSCADA describes how to use the LNT (LON Network Tool) program toinitialise the PCLTA card and it offers more information on LONWORKS

® networkas well.

Additional configuration advises:

• If you use the SMX card (model 74405) and RER 107 transceiver card, use thecustom setting for the transceiver.

• Set the Automatic Flush Cancel on.

• From the NT Diagnostics, you should check that the device (pnplon) hasappeared to the resources.

Installing PCLTA-10 card

To install a PCLTA card:

Select an I/O base address for the PCLTA card and set it on the card as describedin the PCLTA manual. See also Figure 5.2.3.-1. You can select any free I/Oaddress where also next 7 addresses are also free. The driver installation tool

suggests 340 as default value, which is also the setting on the card at delivery.

The setting is shown in Figure 5.2.3.-1. Other possible values are 300, 308, 310,318... 370 and 378 hex. Write down the selected I/O address. An example is

shown in table 5.2.3-1. This information will be needed during the driverconfiguration.

If you use other channels than RER107, you will probably have to configure the card

for the channels. Refer to the PCLTA and channel documentation.

http://www.echelon.com/support

http://www.echelon.com/support



60



Installation Guide

Table 5.2.3-1 The PCLTA card information needed during system configuration. The device names areneeded only if you wishto redefine the NET line numbering.

5.2.4. Installing and configuring driver for PCLTA card

Opening installation and configuration tool

To open the installation and configuration tool for PCLTA card drivers:

If the MiSCLONP is not already installed, install the driver package asdescribed in section 3.7.

Start the MiSCLONP Configuration tool. See section 3.7.

Click Add Device to configure the driver for the first time, or select ChangeSettings to reconfigure it.

Configuring PCLTA driver

For more information on how to configure the PCLTA driver, see the manual“Connecting LONWorks Devices to MicroScada”, section 3.3.2 MicroSCADAdevice driver configuration.

5.2.5. Installing PCLTA-20 adapter in Windows 2000 Professional orWindows 2000 Server

Software installation

When drivers are installed to a Windows 2000 Server where Terminal Services are

running, the installation should be done using the Add/Remove Programs functionfound in the Control Panel (see Fig. 5.2.5.-1).

Browse to the folder where the driver installation file exists. If you are runningWindows 2000 Professional on your computer, you can run the installation exe-

file directly (see Fig. 5.2.5.-2).

Card no.I/O

addressChannel Device no. = n Dev. name = LONPn NET line = n +1

1 A

B

2 A

B




61


Installation

Installation Guide

5

Launch the PCLTA-20 software installation program. Choose .

Follow the instructions that appear on the screen.



62



Installation Guide

Click

The installation directory is by default C:\Lonworks. The path can be changed by

clicking the button and defining a new directory.

Click




63


Installation

Installation Guide

5

Select the restart option at the end of the installation.

5.2.6. PCLTA-20 Card installation

Turn the PC off and remove the power cord.

Open the PC case and locate an empty 32-bit slot.

Check that the RER107 LON communication adapter is attached to the PCLTA-20 adapter.

Insert the PCLTA-20 adapter into the slot.

Reinsert the power cord and restart the PC. A “New Hardware Found” windowwill be displayed briefly when the operating system recognizes the PCLTA-20

adapter.

You can check if the installation has been successful by using the Device managerfound in Control Panel/Administrative Tool/Computer Management (see

Fig. 5.2.6.-1).

5.2.7. Configuration settings for the PCLTA-20 adapter

Open the control panel by selecting the “LonWorks Plug 'n Play" icon in the ControlPanel.



64



Installation Guide

In the dialog that appears (see Fig. 5.2.7.-1), you will find the followingconfiguration properties that need to be set:

• Device Selected

Controls which PCLTA-20 adapter is selected for configuration.

• NI Application

Controls the type of image or application to be used. The image should be set toPCC10L7.

• Automatic Flush CancelShould be checked.

• TransceiverOpens the PCLTA-20 Transceiver dialog box. Do the settings according to what

is shown in Figure 5.2.7.-2.

• System Image Path

Specifies the full directory path for the PCLTA-20 system images. This path is setby the PCLTA-20 Installation software but may be modified by the user.




65


Installation

Installation Guide

5

5.2.8. Starting and configuring PC-NET

Starting PC-NET

To start the PC-NET:

Define a link, a LINn:B object, in the base system of type “INTEGRATED” and

set the SC attribute to the name of the PC-NET program including path. The

standard base system configuration file, SYS_BASCON.COM, contains such a

link definition, in the section that defines communication links. By removing thecomment sign (;) in front of the #CREATE LIN3:B command, you get an

integrated link with link number 3.

To enable communication between the base system and the PC-NET:

Define the PC-NET as a node, a NODn:B object on the integrated link. Thestandard base system configuration file, SYS_BASCON.COM, defines a PC-

NET as node 3 on link 3. Take the definition into use by removing the commentsign (;) front of the #CREATE NOD3:B command.

Configuring PC-NET on-line

After the PC-NET has been started, it must be configured on-line with SCIL withregard to the NET lines, connected stations, and possibly other NET and base systemconnections.

The delivered PC-NET software comprises a template for on-line configurations,the file PC_NET.COM, which is in the \sc\sys\active\sys_ folder. The file contains

a template for configuring station objects of REX-type in the PC-NET. Using this

file assumes that the REX stations have been defined in the base system. Thestandard base system configuration file, SYS_BASCON.COM contains the stationdefinitions utilised by PC_NET.COM. Hence, the NET line used is line number 1,

which corresponds to device number 0. The channel A of the first card is configured

as recommended above.



66



Installation Guide

The contents of the default PC_NET.COM is listed below:

;*********************************************************************

;

; PC_NET.COM

; PC-NET CONFIGURATION TEMPLATE

;;*********************************************************************

@PC_NET = 3

@LON_LINK = 1

@REX_STATIONS = VECTOR(5,6)

@LON_NODES = VECTOR(5,6)

@LON_SUBNET = 1

;CREATE A LON LINK (FIRST LON CHANNEL ON PCLTA CARD) IF ONE DOES NOT EXIST

ALREADY

#IF NET’PC_NET’:SPO’LON_LINK’==0 #THEN #BLOCK

#SET NET’PC_NET’:SPO’LON_LINK’ = 27

#BLOCK_END

;KILL ALL STATIONS THAT MAY EXIST TO HAVE AN EMPTY CONFIGURATION AS BASE;REQUIRES THAT THE STATION HAS A CORRESPONDING BASESYSTEM OBJECT STAx:B

#ERROR IGNORE

#SET NET’PC_NET’:SIU’LON_LINK’ = 0 ; STOP THE NET LINE BEFORE CONFIG STARTS

#ERROR STOP

#LOOP_WITH I = 1..LENGTH(%REX_STATIONS)

@REX=%REX_STATIONS(%I)

#IF (STA’REX’:BST=="REX") AND -

(STA’REX’:BND==%PC_NET) AND -

(STA’REX’:BTT=="EXTERNAL") #THEN #BLOCK

#ERROR IGNORE

#SET STA’REX’:SIU = 0

@REX_NR = STA’REX’:BTN

#SET NET’PC_NET’:SRX’REX_NR’ = "D"

#ERROR STOP

#BLOCK_END

#LOOP_END


@REX=%REX_STATIONS(%I)

@REX_NR = STA’REX’:BTN

#SET NET’PC_NET’:SRX’REX_NR’= %LON_LINK

#SET STA’REX’:SAL = 1

#SET STA’REX’:SLI = %LON_LINK

#SET STA’REX’:SNN = %LON_NODES(%I) ;NODE NUMBER

#SET STA’REX’:SSN = %LON_SUBNET ;SUBNET NUMBER

#SET STA’REX’:SUN = 1 ;UNIT NUMBER

#SET STA’REX’:SRM = 7 ;RUNNING MODE = 7 -> EVENTS SESSION,

;2 -> ONLY TRANSPARENT SPA FOR SETTINGS

#SET STA’REX’:SUT = 1 ;UNIT TYPE 1 -> REC

#SET STA’REX’:SMI = 1000 + %REX

#LOOP_END

;CREATE COMMAND CROSSREFERENCE TABLE, MICROSCADA -> SPA

#SET STA5:SSP1=(10,120,120,"V",6,6,4,1) ;E1Q0

#SET STA5:SSP2=(10,120,120,"V",7,7,4,2) ;E1Q0

#SET STA5:SSP3=(10,120,120,"V",11,11,4,3) ;E1Q0

#SET STA5:SSP4=(10,120,120,"V",10,10,4,4) ;E1Q0

#SET STA6:SSP1=(10,120,120,"V",6,6,4,1) ;E2Q0

#SET STA6:SSP2=(10,120,120,"V",7,7,4,2) ;E2Q0




67


Installation

Installation Guide

5

#SET STA6:SSP3=(10,120,120,"V",11,11,4,3) ;E2Q0

#SET STA6:SSP4=(10,120,120,"V",10,10,4,4) ;E2Q0

;ENABLE TIME SYNC. MESSAGES. BOTH LSG AND MINUTE SYNC

#SET NET’PC_NET’:SLK’LON_LINK’ = 3


@REX=%REX_STATIONS(%I) #SET STA’REX’:SIU = 1

#LOOP_END

#SET NET’PC_NET’:SIU’LON_LINK’ = 1

5.3. Installing DCP-NET units in base systems

Overview

This section describes the installation of DCP-NET units into base system

computers (internal NETs). The installation includes the following steps:

• Marking the cards. This is not required but recommended for clarity.• Jumper and switch settings of the cards.

• Mounting the cards in the computer.

• Installing and configuring the RAM driver.

• Installing and configuring the communication programs.

• Configuring the base system.

• Programming automatic startup of the units.

Marking the cards

The DCP-NET cards are differentiated by the jumper and switch settings and by the

DCP-NET program loaded to the cards at start-up. Each communication programcontains the node number of the NET unit (= NET system object number).

Select a unique node number, 1... 32, for each card and mark it at the rear of the

card. The same number must be configured in the program, which is loaded ontothe card, see "Software Installation" below. In the deliveredSYS_BASCON.COM file, the internal NETs are given node numbers 1 and 2.

The node number must be unique among all connected communication units, basesystems, remote semi-graphic workstations and communication frontends within the

MicroSCADA distributed network. For more information on this subject see the

System Configuration manual, Chapter 5. It is necessary to know the node number

of the NET unit when connecting devices to it.

Setting jumpers and switches

At this stage you need to know the free interrupt levels and I/O addresses in the basesystem computer where you are going to install the NET cards. You can check them

in the Windows NT Diagnostics tool. The interrupt level must be unique within thecomputer. The I/O addresses must not be used by any other device in the computer.

A DCP286 card occupies 3 addresses (the base address and the next two addresses),

and a DCP386 card 7 addresses (the base address and the next six addresses).



68



Installation Guide

To set jumper and switches:

Set the interrupt level of the card to a unique value, and set the I/O base address.Figure 5.2.3.-1 shows some alternatives for the I/O base address. If these

addresses and the next two or six addresses are free, you can use them. You can

check which addresses and IRQ levels are free in the Windows NT Diagnosticstool, Resources. Write down the interrupt level and I/O base address you select.

For this you can use the table 5.4.2-1. You will need them during the driverinstallation. Select one of the cards for device 0 and the other one for device 1.

If you have a DCP-286i card, remove the jumper on AB and place it on BC.This is needed for revision information handling.

Mounting the cards

To mount the DCP-NET cards:

Fasten each card to a full-size 16 bit slot in the base system computer. Any freeslot can be used. For more information see the installation guide of the card.

Connect the 80 pin connectors to the rear of the cards and mark them with the

same node number as the card.




69


Installation

Installation Guide

5

Table 5.3.-1 The information needed for the installation and startup of internal NET units. The shadedfields are needed for startup with the SCIL function LOAD_DCP. The link number is definedby a LINn:B base system object. For more information see System Configuration, section8.2.

Configuring RAM device driver for DCP cards

The use of internal NETs requires the installation and configuration of the RAM

driver. During the driver configuration, you give each card a device number, 0 or 1,and enter the interrupt levels and I/O base addresses set on the cards. See Figure 5.3.-1. In addition, each device requires a shared memory base address.

Device no. Device name Node No.Interrupt

Level

I/O Base

AddressLink No. File Name

0 RM00

1 RM01



70



Installation Guide

If the MS-CRAM package is not already installed, install the driver package asdescribed in section 3.7.

Start the driver configuration program. For more information see section 3.7.

Click Add Device to configure the driver for the first time. To reconfigure it,click Change Settings.

Figure 5.3.-2 shows the dialog box shown for the user when configuring the devicedriver for the DCP-NET cards. Each card is configured separately as a device with

a device number, 0 or 1. When configuring the devices you need to know thehardware settings on the cards.

Enter the following configuration data most of which you find in table 5.3.-1:

Device Number The device number of the DCP-NET card, 0 or 1. It is

recommended that you set the first card as device 0 and

the second card as device 1.

Type of Card The type of the card. The following card types are

supported: DCP/MUXi, DCP-286i, DCP-386i.

IRQ level The interrupt level used by the card. The interrupt levelmust be the same as the level set on the card.

I/O Port Address The I/O base address used by the card. This must be the

same as the address set on the card.

Shared Memory Base Address. The start address of the shared memory.The DCP-NET cards use by default 16 kB of sharedmemory (see below). Check the free memory addresses in

the Windows NT Diagnostics tool, Resources, and select

a memory address where the following 16 kB are free.

On-card Memory Size The size of the memory on the card. Both DCP286i and

DCP386i have 1024 KB.

Window Size The window size used when gaining access to the card’smemory. The default 16 KB should not be changed.




71


Installation

Installation Guide

5

Each of the cards gets a device name, which is RM00 for device number 0 and RM01for device number 1. The device name is needed in the link (LINn:B object)definition in the base system, see System Configuration, section 8.2. The link

number together with the node number and the file name of the communication

program are needed for the start-up of the NET. See table 5.3.-1.

Test the driver and configure automatic start-up as described in section 3.7.

Installing and configuring the NET program

The NET programs must be stored in the folder SYS/ACTIVE/SYS_ from where

they are sought when the NET is loaded, and possibly started, with the SCILfunction LOAD_DCP (see the SCIL manual, chapter 8). During the installation ofthe MicroSCADA base system package, a NET program for internal NET is

installed in the SYS_ folder, unless deselected.

The delivered DCP-NET program is named sys_NET.1mb. The program contains a

standard preconfiguration, which normally needs to be modified to match the actual

configuration. The preconfiguration can be done on-line with the NETPRECONFIGURATION tool, which is accessed from the Tool Manager. Theconfiguration requirements and the configuration tool are described in the System

Configuration manual.

For safety, copy the delivered NET program to another name in the same SYS_

folder.

Open the NET PRECONFIGURATION tool (see System Configuration).

Load the NET program and modify the preconfiguration. The minimum to be

set is the node number and station address of the NET communication unit.Check also the memory size in the preconfiguration: For DCP-286i and DCP-386i, the memory size should be 1024 KB.

Save the program with a name starting with SYS_ and including the nodenumber. For example you can use SYS_NETnn, where ’nn’ is the node number(system object number) of the NET communication unit. Write down the name.

In case the program is given a name, which does not begin with SYS_, it will besearched for in the PICT folder. Then a logical path referring to the SYS_ foldermust be included in SYS_BASCON.COM, for example #PATH PICT +/SYS/ ACTIVE/SYS_.

Configuring base system

To configure the base system for using internal NETs:

Define a link object, LINn:B for each of the NETs.

Define each of the NETs as a node, a NODn:B object.

The standard base system configuration file contains two links for internal

NETs, link1 and link2 and two nodes, node 1 and 2. Take them into use by

removing the comments.



72



Installation Guide

Automatic start-up

To configure automatic start-up of DCP-NETs situated in the base system:

Insert the LOAD_DCP function into a SCIL program, for example, into the inSYS_NETCON.COM or into a command procedure started by the event channel

APL_INIT_1. The NET program name and the LINn:B object number of the useddriver as arguments are given as arguments. For more information see theProgramming Language SCIL manual, Chapter 8.

5.4. Installing frontends

Overview

The frontends are computers especially reserved for process communication. Theycan communicate with one or more base systems via a LAN, or they can beconnected to a NET via a COM port of the frontend computer. A frontend cancontain 1... 4 DCP-NET cards.

The installation of communication frontends comprises the following steps, whichare detailed below:

Preparing the computer.

Installing the DCP-NET cards.

Installing the DCP-NET programs.

Configuring the frontend.

5.4.1. Preparing the PC

Configuring PC

To configure the computer, do the following in the SETUP utility of the PC:

Remove shadow RAM and video ROM shadow.

Remove unnecessary RAM resident programs.

Installing LAN

If LAN will be used for communication with base systems, install the network

adapter card and the LAN software. The LAN requirements are described in section2.4. The installation of LAN is briefly described in Chapter 4.

When installing the network adapter card do not use the RAM addresses, I/Oaddresses and interrupt levels used on the communication cards, see table 5.4.2-1.




73


Installation

Installation Guide

5

Miscellaneous notes

If a mouse driver is used, do not use the interrupt levels 3,5 12 or 15 on the mousedriver.

If using any of the interrupt levels on the mouse driver cannot be avoided, only threeDCP-NET cards can be installed. In some computers, for instance, IRQ12 is

reserved for the mouse driver and cannot be used for the DCP-NET card.

5.4.2. Installing DCP-NET Cards

Overview

The hardware installation of DCP-NET cards in the frontend includes the followingsteps:

Mark the communication cards. This is not required but recommended forclarity.

Define jumper and switch settings of the cards.

Mount the cards in the computer.

Marking the cards

The cards are differentiated by the jumper and switch settings and by the

communication program loaded to the cards at start-up. Each communication

program contains the node number of the NET unit (= NET system object number).

Choose a unique node number, 1... 32, for each card and mark it at the rear of the

card. The same number must be configured in the program, which is loaded onto the

card, see "Software Installation" below. The node number must be unique among allconnected communication units, base systems, remote semi-graphic workstations

and communication frontends within the MicroSCADA distributed Network. Formore information see the System Configuration manual, Chapter 5. It is necessaryto know the node number of the NET unit when connecting devices to it.

Jumpering and switch setting

To set jumpers and switches:

Set the I/O base address and the interrupt level to the values given in table 5.4.2-

1.

See also Figure 5.3.-1 which shows the possible I/O base addresses.

If you have a DCP-286i card, remove the jumper on AB and place it on BC.

This is needed for revision information handling.

Write down the node numbers of the DCP-NET cards together with their

respective I/O addresses, for example, in table 5.4.2-1.



74



Installation Guide

This is necessary for the subsequent software installation and start-up.

The frontend reserves automatically the RAM addresses given in table 5.4.2-1 forthe common RAM of the NET communication units.

Do not use the selected interrupt levels, the I/O addresses and RAM addresses on

any other card in the computer, nor for the mouse.

Table 5.4.2-1 The information needed for the installation and startup of thecommunication units within a communication frontend

5.4.3. Installing frontend software

General

The communication frontend software comprises (see Figure 5.4.3.-1):

• One DCP-NET communication program for one DCP-NET card.

• A loading and routing program named MFL, which runs on the PC under DOS.

At start-up, the MFL program starts the loading of the communication programsto the communication cards. During operation it forwards ACP messages

between the separate communication units and the base systems.

• A load program, MFLOAD_E, which loads the DCP-NET communicationprograms to the DCP-NET cards. At start-up, the program is called by MFL.

Files

The following files included in the frontend software package are used by the

communication frontend. See Figure 5.4.3.-1:MFL.EXE Executable program file. During operation, MFL.EXE

handles the communication between the NET units andthe LAN or COM interface.

MFLCONF.DAT Text file, which specifies the configuration of MFL. See

the System Configuration manual, Chapter 4.

MFLOAD_E.EXE Executable file for setting up NET unit information and

loading the communication programs to thecommunication units.

Card no. Node no.I/O Base

address

Interrupt

level

RAM

addresses

File

name

1 33C 5 D000 ...

D3FFF

2 2BC 12 D4000 ...D7FFF

3 23C 15 D8000 ...

DBFFF

4 1FC 3 DC000 ...

DFFF




75


Installation

Installation Guide

5

MFLOAD_E.SET Setup file, which contains information needed to load thecommunication programs to the communication units.The file is created by running MFLOAD_E.EXE.

MFLCONV.EXE Converts old MFLOAD_E.SET files.

NETCONF.EXE Executable file for building the preconfigurations of the

communication programs.

NET....84 Delivered NET program. During the installation of a NETunit, the delivered NET program is copied to a new name

and configured for the NET in question. At start-up, the

NET programs are loaded on the communication units.

Installing software on disk

The frontend software is included in the MicroSCADA installation CD. If yourfrontend computer cannot install from a CD, you can copy the frontend softwarefrom the CD to two diskettes as follows:

Load the CD into a Windows NT computer.

Open the Explorer and the D: disk.



76



Installation Guide

Double-click the file NET84_1.bat in the Frontend folder to copy the frontendsoftware to the first diskette.

Double-click the file NET84_2 to copy the software to the second diskette.

Install the software on the disk of the frontend computer as follows:

Make a folder for the frontend software. For example, to make a MFL folder,

type:

MD \MFL

Copy the files from the NET, NETCONF and MFL folders on the CD or fromthe diskettes into the MFL folder on disk. To copy, type:

COPY A:\NET\*.* \MFL

COPY A:\NETCONF\*.* \MFL

COPY A:\MFL\*.* \MFL

5.4.4. Configuring frontends

Configuring NET programs

To configure DCP-NET programs:

Copy the communication program to another programs. For example you can

name the program NETnn.84, where ’nn’ represents the node number of theNET communication unit.

Write down the names. An example of this is shown in table 5.4.2-1.

The delivered communication program contains a standard configuration parameter

setup, which normally must be changed. The configuration requirements as well as

the configuration program NETCONF are described in the System Configurationmanual.

Configure each file for a NET unit using the NETCONF program. Each file

must be configured with a unique node number and station address. Check alsothe memory size in the preconfiguration: for DCP-286i and DCP-386i, the

memory size should be 1024 KB.

Editing MFLCONF.DAT

The frontend itself is configured in the file MFLCONF.DAT, which can be editedwith a text editor. The parameters included in the file are listed and described in theSystem Configuration manual, section 4.2. The necessary configuration parametersettings are described in Chapter 8 of the System Configuration manual. Generally,at least the following parameters must be checked and possibly modified:

SRC The station address of the frontend

SRCNOD The node number of the frontend

PROT The LAN protocol used on the frontend - base systemcommunication: DECNET or TCP/IP




77


Installation

Installation Guide

5

DST1... DST4 Station addresses of the base systems connected to thefrontend via LAN or the COM port.

NOD1... NOD4 Base system node numbers

Also check the following parameter if TCP/IP is used:

HOST1... HOST4 TCP/IP host names or internet addresses of the basesystems

If a COM port is used for connecting the frontend to a NET line, check that

COM Serial communication port number

Serial communication attributes (BR, RE, PY, etc.)

In addition if base systems are connected via a NET line of the communication

frontend, set the CSRC parameter.

Configuring Loading of the cards

Starting the frontend requires a MFLOAD_E.SET file, which contains informationnecessary for the loading of the communication programs to the cards. To configurethe loading of the communication cards and create the MFLOAD_E.SET file asfollows:

Start the program MFLOAD_E by entering:MFLOAD_E.

Open the "Configuration" sub-menu.

Select "Input files" and enter the file names to be loaded for each DCP-NET

card. See table 5.4.2-1.

Select the "Special" sub-menu and confirm the selection by clicking OK.

Select the "Auto-opt" sub-menu.

Select LOAD & START as automatic function by pressing Enter.

Exit the "Auto-opt" sub-menu by pressing the Esc key.

Select the "Settings" sub-menu and "Store" function to store the auto-option

settings.

Return to the main menu by pressing Esc. Now the settings are stored in the file

MFLOAD_E.SET.

Exit the MFLOAD_E program.

Creating automatic start-up

To create automatic start-up of the frontend each time the computer is switched on:

Configure the loading of the cards as described above.



Add the following two commands to the end of the .BAT file, which starts the

LAN software package:

CD \MFL (if the folder name is MFL)

MFL or make a .BAT file (for example STARTMFL.BAT) for the commands

if LAN is not used.

Insert the name of the .BAT file into the AUTOEXEC.BAT file to execute it.

5.4.5. Using communicaton frontends

Start-up and shutdown

If automatic start-up was created, the frontend is started automatically as the poweris switched on. To start the LAN frontend manually:

Move to the MFL folder.

Enter the command:

MFL

MFL calls MFLOAD_E, which reads the necessary load information from the fileMFLOAD_E.SET.

To shut down the communication frontend, press Ctrl - C.

Base system communication

If the communication frontend is started before the connected base systems, thefrontend displays error messages for command transmission tries until the basesystem starts. This happens because the communication units send diagnosticcommands cyclically to all known applications at least until a connection isestablished. An error message is also displayed at later disturbances in the basesystem communication.

The station addresses of the connected base systems are configured in the MFLconfiguration file. The MFL program reads the source address of each arrivingmessage. In this way it learns the addresses of the NET communication units in the

frontend, and all other nodes connected to the units. The base system learns the link

number of each node address from arriving messages.

Testing

The MFL program cyclically displays the time of the computer and the diagnosticcounter values for all its interfaces. The base system connection status is shown on

a dedicated line. Another line is reserved for other system information. See Figure

5.4.5.-1. Some additional display functions can be executed with the followingcommands:

M Msg routingStarts and stops display of information about all message routing

actions of MFL. Source and destination addresses are displayed,

as also reply status code and destination interface.

R RestoreRestores the initial display and selects time as cyclic update

mode.

0 Resets all MFL diagnostic counters.




79


Installation

Installation Guide

5

5.5. Installing NET connections

Overview

Below are some suggestions for the installation of connections to the process and toother devices:

• Twisted cables.

• Dial-up modem settings.

Twisted cables

Figure 5.5.-1 shows the cable wiring of the NET cables.

Dial-up modem settings

The dial-up modems may be of various types, and each type has its own settings.

Some general rules for dial-up modems used in the NET - RTU communication arepresented.

The modem in the NET end should have the following settings:

• The modem must not answer to coming calls (ATS0 = 0).

• No error correction.

• XON/XOFF = 0

Regarding the modem settings in the RTU end, refer to the RTU manual.



80



Installation Guide

The diagram above, applies to most NET connections, except for one type of printerconnections. See Chapter 7 for more information.




81

6. Installing workstations

Installation

Installation Guide

6


About this chapter

This chapter describes how to install a MicroSCADA workstations connected to a

local area network and MicroSCADA workstations connected via a telephone line.6.1 Installing workstations connected to a local area network: PCs running

Exceed.

6.2 Installing workstations connected via a telephone line.: Exceed and

RAS.

6.3 Compiling fonts.

The installation of the semi-graphic workstations is described in a separate manual.

6.1. Installing workstations connected to LAN

GeneralThis description applies to MicroSCADA workstation connected to a local areanetwork. The installation involves the following steps which are detailed below:

• Preparing the computer by installing and configuring the operating system andthe software needed for the local area network communication.

• Installing Exceed in the computer.

• Installing the MicroSCADA Workstation software package.

• Compiling fonts.

• Configuring the MicroSCADA base system.

Preparing the computer

Install and configure the operating system and the LAN, see chapter 3 and 4. Wheninstalling the operating system, note the following:

• Define a user belonging to the User group. For the user to be able to open aMicroSCADA monitor on the workstation without explicitly identifying himself

for the base system computer the user must be defined on the base system

computer with the same password as on the workstation.

• Set the color palette to at least 256 colors for the display. The display setting tool

can be found in the Control Panel. For more information see section 3.6.

Installing ExceedThe installation procedure below can be regarded as a sample installation. Thesample assumes that the Exceed software version is 5.1.3 delivered on a CD. Formore information about the installation of Exceed, refer to the Exceed manuals.

To install the Exceed software:

Log on as a user having administrator rights.

Close all applications. Start the setup.exe installation program located in the \winnt\exceed directory by double-clicking the name in Explorer.

1MRS751853-MEN



82


6. Installing workstations Installation Guide

A dialog with the title “Exceed for Window NT V5.1.3 - Setup” appears onscreen. Read the message. Click OK. In the next dialog, see Figure 6.1.-1, selectthe Shared setup type and the Custom method. Click OK.

In the next dialog you are asked for the home directory of Exceed. Accept thesuggested home directories by clicking OK.

You are then asked to choose the components and fonts that you want to install(Figure 6.1.-2). Select components to install by clicking.

Select the components you want to install. A standard set to choose is:

Default

File Transfer Protocol

In this file you can edit IP-addresses

and Aliases

Controls which network services your

PC responds to when an incomingrequest is made

Allows you to send ICMP-echo

request packages to the network

Remote copy, Windows-basedversion of UNIX1 rcp command

Remote copy, Windows-basedversion of UNIX rexec command

Windows-based version of UNIX

rexec command Windows-based version of UNIX rsh

command

Enables you to make Telnetconnections to remote host

Displays the route a packet take to a

host

1. UNIX is a registered trademark of X/Open Company Limited.




83


Installation

Installation Guide

6

Files needed when you want to createfiles that can be run from client, orstarted to a client

Click OK.

Click Fonts.

Select the fonts needed (Figure 6.1.-3). These are:

Miscellaneous fonts

75dpi fonts100dpi fonts

Click OK.



84



The selection you have made is presented (Figure 6.1.-4). Click Start to beginthe installation.

The program is installed. The last step is to create a user profile.

If Exceed was installed in the default directory run the setup.exe program

located in the \program files\exceed.nt\userins directory.

The installation asks if you want to do an installation that enables all users to useExceed. Click Yes.

A dialog box for choosing the keyboard file is displayed. Select the keyboardfile you want to use, for example “us.kbf ” or “swedish.kbf ” and click OK. See

Figure 6.1.-5.

In the next dialog box you can type and confirm a password. A password is

needed only in case you want to prevent others from changing your settings.

Click Skip, unless you wish to use a password.




85


Installation

Installation Guide

6

“Would you like to create the program group ‘Exceed’ ?”

Click Yes.

“Would you like to tune the X server for optimal graphics performance now?”

Click Yes. Wait until graphics are tuned and a message box with a text“Installation for Exceed for Windows NT V5.3.1 is now complete” appears.

Click OK.

Installing MicroSCADA workstation package

The MicroSCADA workstation software package contains the fonts used byMicroSCADA and a program for opening MicroSCADA monitors on the screen.To install the workstation package:

Log in as a user with administrator rights.

Load the MicroSCADA CD. Start the Explorer and search for the CD drive. Theinstallation program MS_WS.EXE is in the Workstation directory. on the CD.Start the program by double-clicking the name.

The installation program asks for the names of the base systems to which theNotification window (see section 3.9.) will be connected.

Enter the name of one or two base systems. If no Notification window is needed,you can leave the fields empty.

The MS_WS.EXE program creates a directory structure similar to the one in thebase system, see chapter 3. It copies the programs notify.exe and mons.exe to the

EXEC directory and creates icons for opening MicroSCADA monitors and

Notification window.

Compiling fonts

Compile the MicroSCADA fonts as described in section 6.3.

Configuring MicroSCADA

Configure the base systems by defining a number of "X" or “VS” type MONn:B

objects in SYS_BASCON.COM. See the System Configuration manual, section

9.1., "Monitor".

MiscellaneousTo get the correct function of the Alt keyboard key in the Exceed workstations:

Open the Exceed X input settings tool by selecting Start, Program, Exceed,Xconfig and Input.

Select the value “To X” for the Alt key field.



86



In order to allow copying from Windows to X and vice versa, do the following:

Open the Exceed X Selection settings window by selecting Start, Programs,Exceed, Xconfig and X Selection.

Check ’Auto Copy X Selection’ and ’Auto Paste to X Selection’.After this Exceed has to be restarted if it was running.

If there are problems with screen update when using X monitor, the screen updateperformance can be increased by following settings.

Open the Exceed performance settings window by selecting Start, Programs,Exceed, Xconfig and Performance.

Make the following selections:

• Check 'Save Unders'.

• Select 'Maximum Backing Store:' 'Always'.• Select 'Default Backing Store:' 'When Mapped'.

After this Exceed has to be restarted if it was running.

In order to correctly position opening X windows, do the following:

Open the Exceed Window Mode settings window by selecting Start, Programs,Exceed, Xconfig and Window Mode.

Clear the check mark from 'Cascade Windows'.

After this Exceed has to be restarted if it was running.

6.2. Installing workstations connected via telephone line

Overview

Instead of a local area network the MicroSCADA workstation can use a telephoneline to connect to a base system.

This configuration of the workstation requires that the workstation is running the X

emulator software (Exceed) and using the Remote Access Service (RAS) providedby the Windows NT operating system. The workstations are connected via

telephone lines to a Windows NT computer on the LAN - a MicroSCADA base

system computer or another Windows NT computer on the LAN (see Figure 6.2.-1).This computer will act as the server of the connection while the workstationcomputer will be the client. When connection is established, the client workstation

will be regarded as a computer on the LAN and it can communicate with all

MicroSCADA base system on the LAN. The contact is taken from the workstationacting as a client to the base system acting as a server.

RAS service is not installed automatically in the express installation of Windows

NT. It must be installed afterwards, both in the server and in the client computer. Theserver is configured to accept incoming calls, while the client is configured to make

outgoing calls.




87


Installation

Installation Guide

6

The installation procedure comprises the following steps which will be detailedbelow:

• Installing and configuring the workstation computer.

• Installing modems to both computers.

• Installing RAS in both the workstation and server computers.• Configuring start-up of RAS in the server computer.

• Preparing for dial-up from the workstation computer.

Installing and configuring workstation

Install and configure the workstation computer as described in section 6.1.,excluding the LAN which is not required.

Installing modems

To install the modems:

Install modems to both computers.

During the RAS installation, the installation program will search for the modem type

in the file modem.inf in the directory \WINNT\system32\ras.

Check that the modem types you are using are mentioned in the modem.inf file.If not, add the required code to the file. The code might be provided on a

diskette delivered with the modem.

Installing RAS

RAS must be installed both in the client and server computers. Below follows a step-

by-step description of a RAS installation. Refer also to the Windows NT operatingsystem manuals.

Double-click the icon My Computer and Control Panel. From Control paneldouble-click the Network icon.



88



The Network tool appears.

Select the page Services and click Add.

Select Remote Access Service and click OK.

Select the installation media, e.g. A:\i386 if diskette.




89


Installation

Installation Guide

6

File copying starts. When ready, you are asked the following question:

Make sure that the modem is connected to the desired COM port, and click Yes.

Follow the instructions on the screen, see Figure 6.2.-5.

You can either use automatic modem detection or enter the RAS communicationmedia manually.

• If you use automatic modem detection, select Next and follow the

instructions on the screen.• In case you do not wish to use automatic modem detection, the

windows in Figure 6.2.-6 and Figure 6.2.-7 will be shown. Select

type of modem and communication port.



90



The installation program searches for the type of connected modem in the file

modem.inf in the directory \WINNT\system32\ras. An error message is produced ifthe modem type is not found.

Enter the dialing information, see Figure 6.2.-8, and click Next.




91


Installation

Installation Guide

6

Click Install Modem.



92



Click Configure.

Select the option “Receive calls only” in the server computer and “Dial out

only” in the client computer. Click OK.

Click Network (see Figure 6.2.-10).




93


Installation

Installation Guide

6

Select the TCP/IP protocol and click Configure.



94



Enter the address range of all remote workstations connected to the server. If theserver runs under Windows NT Workstation, only one remote workstation isallowed. However, although only one workstation will be used, the address must

be given as an address range. In the case in Figure 6.2.-13, the remote

workstation is assigned the IP address 138.221.80.231.

Configuring start-up of RAS in server computer

To configure automatic start-up of Remote Access Service in the server computer:

Double-click the icon My Computer and Control Panel. From Control paneldouble-click the Services icon.

Select Remote Access Server and click Startup.




95


Installation

Installation Guide

6

Select Automatic startup.

Click OK.

Checking RAS

The RAS Service functions can be controlled from the tool Remote Access Admin,which can be found under Administrative Tool, see Figure 6.2.-16. This tool

contains useful functions for connection diagnostics and help for RAS questions.

Preparing for dial-up from workstation computer

To prepare a dial-up from the workstation computer to the base system, insert thephone number of the server computer in a phone book as follows:

Double-click the icon My Computer. Double-click the icon Dial-UpNetworking.

Follow the instructions in the windows which appear, see Figure 6.2.-17 and

Figure 6.2.-18.



96






97


Installation

Installation Guide

6

By clicking Alternates (Figure 6.2.-19) you will find features which can be set in theRAS client.

MicroSCADA has been tested using the TCP/IP and PPP protocols.

Dialing-up

During the RAS installation, an icon named Dial-up Network was created on theworkstation computer. To establish connection with the server computer, and with



98



the network, double-click this icon and click the key Call. To finish the connection,click the icon and the key Hang-up.

6.3. Compiling MicroSCADA fonts

The semi-graphic fonts exist in three different sizes for three different picture sizes.When opening a MicroSCADA monitor, the font size is selected, and with that the

size of the MicroSCADA pictures. Although no semi-graphics are used in thepictures, the size of the semi-graphic font determines the size, or actually the

maximum size, of the pictures.

Besides the semi-graphic fonts, the tool pictures use a Helvetica font (upper andlower case) which likewise exists in three different sizes. LIB 500 uses a third set of

fonts of three different sizes. The fonts are delivered as *.bdf files in theMicroSCADA base system package. During the installation, the font files areinstalled on the base system disk as *.bdf files in the sc\fonts\scada_font\x directory.

The font files and the corresponding picture sizes are listed in Table 6.3.-1. The

semi-graphic fonts and the scalo*.bdf fonts are always required. The abb*.bdf fontsare needed for LIB 500.

Table 6.3.-1 The MicroSCADA font files and the sizes of the resultingpictures

If a Visual SCIL remote monitor or an X monitor is to be opened on the computer

these files must be compiled. This applies to both MicroSCADA base systemcomputers and MicroSCADA workstation computers.

Compiling fonts

This information concerns the Exceed Xconfig program version 5.1.0.3.

Compile the fonts as follows:

Start the Xconfig program.

Choose Font by double-clicking the icon.

Click Compile Fonts in the Font Settings dialog box, see Figure 6.3.-1.

Table 2:

Font files Picture size

Semi-graphic fonts Tool fonts LIB fonts (pixels)

scada1620.bdf

scada1215.bdf

scada810.bdf

scalo1620.bdf

scalo1215.bdf

scalo810.bdf

abb18.bdf

abb14.bdf

abb10.bdf

1280 x 960

960 x 720

640 x 480




99


Installation

Installation Guide

6

Select the directory where the fonts are stored, in this case

\sc\fonts\scada_fonts\x see Figure 6.3.-2.

Click Select all.

Click Compile.

The Font Compiling Progress dialog box appears on the screen. Wait until all

the fonts are compiled and then click Done to exit the dialog box.

In the next step you are asked if you want to add the output font directory to thefont database. Click Yes.



100



A dialog box with title “Add Font Directory” appears. Type the name of the fontdatabase file, e.g. scada, in the File Name row. Click OK.

You are told that the font directory has been added to the font database. Click

OK.

Click Close in the Compile Fonts dialog and Close in the Font Settings dialog(Figure 6.3.-2).

Exit the Xconfig program by selecting Exit in the Settings menu.




101

7. Installing peripherals

Installation

Installation Guide

7


About this chapter

This chapter describes how to install the following peripheral equipment:

7.1 Printers: printers connected directly to base system computers, to theLAN and to NET units.

7.2 MicroSCADA alarm equipment.

7.3 Radio Clocks: radio clock cards mounted in the base system computers,clocks connected to communication frontends, and clocks connected to

communication units.

7.1. Installing printers

Introduction

Printers are used for automatic event and alarm printout, and for operator initiatedhardcopy. For hard copy, the hard copy functions of eXceed or Windows NT can beused without any configuration measures in MicroSCADA. The automatic eventand alarm printout on the other hand requires that the printers are known to

MicroSCADA. These printers can also be used for MicroSCADA initiated hardcopy. The installation descriptions below apply to the printers used byMicroSCADA. Regarding the installation of Windows NT hard copy devices, refer

to the Windows NT and the printer manuals.

A MicroSCADA printer can be connected in the following ways:

Directly to a base system computer, through the parallel port or a serial port.

To a LAN via a printer server.

To a DCP-NET.

Printers connected to a NET unit can be made accessible to all base systems in theentire distributed MicroSCADA system. A printer connected directly to a base

system can also be used by other base systems on the LAN, provided that the printeris defined as “shared” in the operating system configuration of the computer towhich it is directly connected, see Sharing Resources in section 3.9. Printers

connected to a LAN can be made accessible to all base systems on the LAN.

On the application level, the printing can be accomplished according to twodifferent principles which determines the appearance of the printout:

Semi-graphic picture based printing.

Full graphic SCIL defined printing (“transparent” printing).

The picture based printing gives a copy of the semi-graphic parts of the printed

picture. There are three different types of picture based printout: Character-basedblack-and-white printout, pixel-based black-and-white printout, and pixel-based

colour printout. See the requirements in chapter 2. The picture-based printoutproduced by printers directly connected to the base system or to LAN are always

1MRS751853-MEN



102


7. Installing peripherals Installation Guide

character based and black-and-white. Pixel-based or colour printout is obtainedexclusively on printers connected to the NET lines (provided that the printersupports this type of printout).

The SCIL defined may contain any characters, graphics, formatting and colourssupported by the printer interface. This type or printout may be obtained on any

printer, independent of the type of connection.

Connecting printers to the base system

To connect a printer directly to a base system computer:

Connect the printer to a parallel or serial port. Printers connected to the parallel

port of a base system computer can be placed at a maximum distance of 3metres from the base system computer. Serial lines allow the connection lines tobe up to 15 metres without modem.

Configure the printer to the operating system as described in the Windows NT

manuals. Define the printer as “shared” if it will be used by several base systemsor other Windows NT computers on the LAN.

Select the connection mode on the printer: parallel mode if the printer was

connected to the parallel port and serial mode if it was connected to a serial port.

Configure the printer in the base system as a PRIn:B object, see the System

Configuration manual, section 10.1. If the printer will be used by several basesystems, or by programs other than MicroSCADA on the same or othercomputers, set the OJ attribute of the printer to 1. See the example in the

SYS_BASCON.COM file in section 3.8.

Printers that will be used by several base systems must be defined in all basesystems, both regarding the operating system configuration and the MicroSCADA

configuration.

Connecting printers to LAN

To connect a printer to a LAN via a HP JetDirect printer server:

Install the printer server on the LAN and install the printers as described in theprinter server manual.

If only one printer will be connected to the server, use the DLC protocol. In other

cases you must use the TCP/IP protocol. Refer to information provided by HewlettPackard on Internet on how to configure the printer server for the TCP/IP protocol.

Perform the following in all base systems that will use the printer server:

Configure the DLC protocol in Windows NT. For this operation the compactdisc containing the Windows NT is needed.

Configure the printer in Windows NT. Define one base system as printer

manager and share the printer with other base systems. In case you have hotstand-by systems, both base systems should be defined as printer managers. The

printer port must be configured as “Job Based”.




103


Installation

Installation Guide

7

Define the printer or printers as PRI base system objects inSYS_BASCON.COM. Define the PRI objects as if the printers were directlyconnected to the computer, see the System Configuration manual Chapter 10.

Connecting printers to NET units

In order to connect a printer to a NET unit:

Connect the printer to a free NET line. Generally, the lines with the lowest

priority should by used for printer connections (see Chapter 5, "Communication

Lines"). Figure 7.1.-1 shows the possible cable wiring for printer connectionswith different output synchronisation (see the OS attribute for printer lines in the

System Objects manual).

Select the connection mode on the printer: set the printer in serial mode.

Define the printer line and a PRI object in DCP-NET of the NET unit to which it

is directly connected, see the System Configuration manual, Chapter 10.

Define the printer as a PRI object in all the base systems which will use it. See

the System Configuration manual, Chapter 10. See also the

SYS_BASCON.COM example in Chapter 3 of this manual.



104



Printers cannot be connected to the PC-NET.

7.2. Installing MicroSCADA alarm units

Introduction

The MicroSCADA alarm unit is either a standard ISA card upon which an additional

cable connection card has been added, see Figure 7.2.-1, or a standard PCI cardconnected to an audio alarm panel, see Figure 7.2.-2.

The cable connection card provides two outputs from the PC ISA card, one of which

is connected to a standard MicroSCADA alarm panel. The wires of the other cable

can be connected to eight arbitrary alarm devices, issuing alarm signals originatingfrom different alarm classes, or from the watchdog facility.

The alarm cards used are the FPC-046 PC INDUSTRIAL I/O ISA card by Flytech

Technology, PCI-7250 PC audio alarm PCI card by ADLink and PCI-1760 PC audioalarm PCI card by Advantech. The cable connection card for the FPC-046 is

constructed by ABB Substation Automation Oy.

The standard MicroSCADA alarm panel for the FPC-046 PC card contains:

• Seven alarm class -specific lamps and one for the watchdog indication.

• Seven alarm class -specific push buttons, and one button for the watchdog, for

light and sound acknowledgement.

• One push button for acknowledging all alarms, the button includes also a lamp.

The MicroSCADA audio alarm panel for the PCI-7250 and PCI-1760 cardscontains:

• Seven alarm class -specific lamps and one lamp for the watchdog indication.

• A speaker for audio alarm.• A switch for enabling and disabling the speaker.

• A lamp for indicating the speaker on/off state.

• A single button for light and sound acknowledgement.

• Transparent pockets for placing text identifications for the alarm classes.

Major differences between the two alarm panels are, that the audio alarm panel uses

PCI based PC cards, has an independent power source and has the watchdogcircuitry in the alarm panel. In the ISA card based solution the watchdog circuitry isin the cable connection card making it dependent on the power source of the PC.

Also the alarm panel with the ISA card uses the power source of the PC.




105


Installation

Installation Guide

7



106



The installation of the alarm devices comprises the following steps:

Mounting and connecting the alarm cards.

Installing and configuring the alarm device drivers.




107


Installation

Installation Guide

7

Connecting the alarm panels and devices.

Configuring MicroSCADA.

Installing the alarm cards

Installing the FPC-046 I/O card and the cable connection card:

Mount the alarm card, including the cable connection card, into a free ISA

expansion slot in the base system computer. The factory setting of the I/O port

address, 170H, does not need to be changed, provided that this address and thenext 15 addresses are not used by any other device. You can check this for

example with Windows NT Diagnostics tool.

Fasten the two 25 pin connectors of the flat cables to two output racks at the rear

of the PC. This arrangement enables connection of alarm devices withoutopening the computer case.

Installing the PCI-1760 and PCI-7250 audio alarm cards:

Mount the alarm card used into a free PCI expansion slot in the base systemcomputer. A PCI card selects the necessary I/O port addresses automatically.

A cable that comes with the audio alarm unit has a D15 connector in one endand D37 in the other. Connect the D37 connector to the output of the PCI audio

alarm card in the back of the PC. For compatibility reasons the jumper JP0 on

the Advantech PCI-1760 must be set to wet (W) contact position, the default isdry (D).

Configuring alarm driversTo be able to successfully configure the alarm driver you must belong to the usergroup Administrators.

To configure the standard alarm unit (using FPC-046 I/O card) drivers:

If the MS-AA package is not already installed, install the package as describedin Chapter 3.

Start MicroSCADA Control Panel.

Click Admin and then Drivers.

Click MS-AA to configure the MiSCAlrm driver.

Click Add Device to configure the device for the first time, or click ChangeSettings to reconfigure it. Figure 7.2.-3 shows the configuration dialog box for

the alarm driver.



108



Enter the following configuration data:Device Number: The device number. Only one card is supported. It

will be device 0.

Type of Card: The type of the card. Only one card is supported:

FPC-046 PC Industrial I/O Card.

I/O Port Address: The I/O port used by the card. This must be thesame as the I/O port address set on the card, seeabove.

Alarm State when MicroSCADA Not Running:

The selection of whether to have all the lamps on

the alarm panel turned on or off whenMicroSCADA service is stopped.

Audio_set will be used: This check box must be selected when using the

audio_set executable, described in Chapter 10 ofthe System Configuration manual.

Test the driver and configure automatic start-up as described in Chapter 3.

For Advantech PCI-1760 and ADLink PCI-7250 audio alarm cards’ driverinstallation and configuration see the equivalent card manufacturer documentation.The Windows NT 4.0 drivers for both PCI cards are delivered with the cards. Thedriver versions supported by MicroSCADA are:

• Version 2.0 of the ADLink ’s PCI-7250 I/O card driver for Windows NT 4.0.

• Version 1.10 of the Advantech’s PCI-1760 I/O card driver for Windows NT 4.0.

If there are problems with the compatibility of the drivers with MicroSCADA, thesupported versions of the drivers can be downloaded from the manufacturerWWW-sites:

• ADLink site: http://www.adlink.com.tw/home.htm

• Advantech site: http://www.advantech.com/

If this does not solve your problem, please contact the ABB Substation Automation

Oy customer support.




109


Installation

Installation Guide

7

Connecting alarm panels and devices

Connecting the alarm panel and devices to the standard ISA based alarm unit:

Connect the standard MicroSCADA alarm panel as illustrated in Figure 7.2.-1.

Connect possible additional alarm devices to the 25-pin connector. The table inFigure 7.2.-1 specifies the output pins and corresponding alarm output (alarm

class and watchdog).

Connecting the alarm panel and devices to the PCI based audio alarm unit:

Connect the D15 connector of the cable coming from the audio alarm card to

either of the audio alarm panel’s controller connectors.

Connect possible additional alarm devices to the 25-pin relay (Fujitsu RA-5W-

K) output connector on the alarm panel. The table in Figure 7.2.-2 specifies theoutput pins and corresponding alarm output (alarm class and watchdog).

To place texts in the transparent pockets of the free text windows on the audioalarm panel:

Open all four screws on the bottom of the box.

Open two bolts on the inside of the cover, which holds the electric circuit board.

Print or write alarm explanation texts on paper and put them to the pocketbetween the iron plate and plastic cover as demonstrated in Figure 7.2.-4.

MicroSCADA configuration

Set the SYS:BAA attribute to 1 in sys_bascon.com as shown in Figure 7.2.-5. See

also the System Configuration manual, chapter 10. If MicroSCADA is to beconfigured for either of the PCI cards, then also the SYS:BAD attribute needs to be

set as shown in Figure 7.2.-5. The AA and AD attributes are described in the System

Objects manual Chapter 4.



110



7.3. Installing radio clocks

Installing clock cards in base systems

In order to install a radio clock card in a base system computer:

Set the I/O port address of the clock card. The I/O port address and the next 7

addresses must not be used by any other device in the computer. You can checkthis for example with Windows NT Diagnostics tool.

Mount the card into a free expansion slot in the computer.

Install and configure the radio clock driver as described below.

Configure MicroSCADA according to the System Configuration manual,section 9.3., "External Clocks".

Configuring radio clock driver

To be able to successfully configure the radio clock driver you must belong to theuser group Administrators.

If the MS-PC3X package is not already installed, install the package as

described in section 3.7.




111


Installation

Installation Guide

7

Start MicroSCADA Control Panel.

Click Admin and then Drivers.

Click MS-PC3X to configure the MiSCPC3x driver.

Click Add Device to configure the device for the first time, or click ChangeSettings to reconfigure it.

Enter the following configuration data in the radio clock driver configurationdialog, see Figure 7.3.-1.

Device Number The device number. Only one card is supported. It will be

device 0.

Type of Card The type of the card. The following card types are

supported: PC31, PC32.

I/O Port Address The I/O port used by the card. This must be the same asthe I/O port address set on the card, see above.

Test the driver and configure automatic start-up as described in section 3.7.

Installing clocks connected to communication frontends

In order to install a radio clock connected directly to a communication frontend:

Configure the clock as described in the clock manual. If a clock of type

RCC8000 is used, the format must be of type number 1, i.e., 25 ASCII

characters.

Connect the clock to the COM1 port.

Configure the MFLCONF.DAT configuration file as described in the SystemConfiguration manual, chapter 10.

Installing clocks connected to NET units

In order to install a radio clock connected to a NET unit:

Configure the clock as described in the clock manual. If a clock of type

RCC8000 is used, the format must be of type number 1, i.e., 25 ASCIIcharacters.



112



Connect the clock to a free NET line.

Configure the DCP-NET of the NET unit as described in the System Configurationmanual, chapter 10.




113

8. Upgrading from previ-ous revisions

Installation

Installation Guide

8

8. Upgrading from previous revisions

About this chapter

This chapter describes:

8.1 How to use a base system configuration made for MicroSCADA 8.1 or8.2 and how to copy the MicroSCADA application software used inMicroSCADA 8.1 or 8.2. It also contains information on issues when

upgrading to MicroSCADA 8.4.2. For example memory handling and

monitor diagnostics are handled.

8.2 How to use an existing NET preconfiguration when upgrading the NET

program to DCP-NET 8.4.

8.1. Upgrading base systems

Using the SYS_BASCON.COM file

A SYS_BASCON.COM file made for MicroSCADA 8.1 or 8.2 can be used in a

8.4.1 base system. However, operating system specific attributes must be edited.

To reuse a SYS_BASCON.COM file:

Connect the UNIX system and the system that runs the Windows NT1 operatingsystem through a local area network.

Copy the SYSBASCON.COM file located in the /usr/sc/sys/active/sys_

directory on the UNIX system to the \sc\sys\active\sys_ directory of the

computer that runs the Windows NT operating system. This can for example be

done by using FTP.If FTP is used:

Start the FTP server on the Unix system if it is not started.

Log in as an administrator, to the computer that runs the Windows NT operating

system.

Start the program Command Prompt.

Change directory to \usr\sc\sys\active\sys_ by giving the command:

Start FTP by giving the following command:

’destination’: The host name of the computer

running the Windows NToperating system.

Use a MicroSCADA user defined on the Unix system to log on.

1. Windows NT is a trademark of Microsoft

1MRS751853-MEN



114



Installation Guide

Give the command:

The file should now be copied to the computer that runs the Windows NT operatingsystem.

When the file has been copied close the connection to the Unix system by givingthe command:

Change the operating system specific attributes, e.g. the System Device (SD)attribute.

Copy the SYS_BASCON.COM after you have installed the MicroSCADA base

system software.

Compatibility issues

The behaviour of some SCIL language elements have been changed from previousversions. The compatibility with the old revision is defined by compatibility issues.

To force SCIL programs executed within a MicroSCADA application to behave asbefore regarding one or more compatibility issues, the Revision Compatibility (RC)

attribute of the application must be set. For more information regarding

compatibility issues, see the System Objects manual.

Memory handling

It is possible that shortage of memory errors in some SCIL program (SCIL error:

MEMORY_POOL_EXHAUSTED) occur after upgrading to revision 8.4.2. Thisproblem can be solved by tuning the memory pool parameters in theSYS_CONFIG.PAR file.

In previous revisions of MicroSCADA all SCIL programs used the same memorypool independently of where the SCIL program was located (command procedure,picture, form picture, etc.). In this revision all processes executing SCIL programs

have their own local memory pool, mainly of performance and reliability reasons.

This means however that the total amount of memory available for a process e.g. aMicroSCADA Monitor will change due to upgrading to revision 8.4.2. This can lead

to shortage of memory errors in some SCIL programs (SCIL error:MEMORY_POOL_EXHAUSTED). The size of the local memory pools can be

tuned by means of parameters in the SYS_CONFIG.PAR file. The behaviour is

identical to previous revisions if the local memory pools are set to 0. This is howevernot recommended as it decreases the performance. For more information on thissubject, see the section 3.8.

SCIL

If the MicroSCADA base system revision 8.4.2 will be used together withapplications created with earlier revisions of the base system, e.g. 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




115


Installation

Installation Guide

8

application in SYS_BASCON.COM. If the switch is not turned on, it is possible thata SCIL error message (580, SCIL_VARIABLE_ALIASING_ERROR) occurs insome SCIL program.

Sys_Bascon.com:

#CREATE APL:V = LIST(-

...

RC =

VECTOR("FILE_FUNCTIONS_CREATE_DIRECTORIES" ),-

...

For system performance, the arguments of predefined SCIL functions as well as

arguments of method/named program calls are passed by reference to the calledsubprogram, if they are of structured type (text, bit string, byte string, vector or list).

In previous revisions there were some cases where the reference became invalid

unnoticed. These cases produce a SCIL error in 8.4.2. By means of the revisioncompatibility switch these programs can be made to work also in 8.4.2. Turning onthe compatibility switch forces copies of arguments to be passed to subprograms,

instead of references, with degraded performance as a result.Note that the compatibility switch can be turned on either for the whole applicationor by means of the SCIL function REVISION_COMPATIBILITY locally in a

program. Note also that it is not possible to use the compatibility switch for compiledSCIL programs.

The cases are:

(X contains a text or vector value)

APPEND ( %X , .METHOD )

or.METHOD1 ( %X, .METHOD )

If METHOD modifies the variable X, the first argument becomes invalid. (The

APPEND functions is just an example. Other functions that take structured datatypes as arguments are also concerned).

This program case is erroneous, as the arguments of the subprogram/function call

may be evaluated in any order and a particular order must not be assumed.

@Y = %X + .METHOD

If METHOD modifies the variable X, the reference becomes invalid before theaddition is done.

This program case is erroneous, as the addition (and multiplication) may beevaluated in any order and a particular order must not be assumed.

.METHOD ( %X )

The method contains the following lines:

@X = "New Text"



116



Installation Guide

The assignment invalidates the argument of the method call. For more informationsee the Programming Language SCIL manual, section Function:REVISION_COMPATIBILITY, System Objects manual, RC attribute and the

Programming Language SCIL manual, section The SCIL Compiler.

Monitor diagnosticsDiagnostics for VS-REMOTE and X monitor types is included in revision 8.4.2 in

order to detect errors in the communication with the X-server. The default value for

the diagnostics interval is 10 seconds. This should be taken into account e.g. if theX-server is connected to the system through a modem because a connection to the

X-server is established at a rate defined by the diagnostics interval. The diagnosticsinterval is defined by means of the base system attribute MON:BDI.

Copying MicroSCADA application software from UNIX

If you have a MicroSCADA application built for MicroSCADA 8.1 or 8.2 you cancopy it to MicroSCADA 8.4.1 using the apptra tool. The tool is composed of two

files, apptra and tf, which are delivered with the MicroSCADA 8.4.1 base systempackage.

To copy the MicroSCADA application software from a UNIX base system to acomputer running the Windows NT operating system:

Connect the UNIX base system and the computer that runs the Windows NT

operating system through a local area network.

Log in to the UNIX system as a MicroSCADA user.

Log in as an administrator.to the computer that runs the Windows NT operating

system.

Start the FTP server on both computers if they are not already started.

Copy the files apptra and tf from the \sc\prog\exec directory of the computerthat runs the Windows NT operating system to the /usr/sc/prog/exec directory ofthe UNIX computer.

On the UNIX computer the file attributes for the files should be change to

enable a execution of the files. This is done by entering the following command:

Run the apptra program on the UNIX computer by entering the following

command:

apptra ’application’ ’destination’ ’usr’ ’passwd’

where

’application’ Is the MicroSCADA application name on the UNIX computer

’destination’ The host name of the computer that runs the Windows NToperating system




117


Installation

Installation Guide

8

’usr’ User name used by the FTP program, to log on to the computerthat runs the Windows NT operating system.

’passwd’ The password used by the ’usr’

The MicroSCADA application is copied to the login directory of the FTP-server onthe computer that runs the Windows NT operating system.

If the host name of the computer running the Windows NT operating system is’mynt’ and the application name is ’myapl’ and there is a user with the name ’guest’ and with the password ’secret’ defined on the computer, the command is:

If the FTP-server default directory on ’mynt’ is d:\tmp, the MicroSCADA applicationsoftware is copied to the directory: d:\tmp\myapl.

Move the application directory and all its sub-directories to a sub-directory

under the \sc\apl directory on the computer running the Windows NT operatingsystem.

Prepare the application as described in section 3.5.

Log off the UNIX system and computer that runs the Windows NT operatingsystem.

MicroSCADA application using operating system specific features, such asprograms started with the SCIL function OPS_CALL, must be changed to work in

the new environment.

8.2. Upgrading DCP-NET

Introduction

When upgrading the DCP-NET from an older revision, the existing preconfigurationcan be used. However, some modifications might be necessary.

Base System Revision

The PC-NET revision 8.4.2 must be used together with MicroSCADA base systemrevision 8.4.2.

Upgrading from 7.3

An existing preconfiguration of MicroNET 7.3 cannot be combined as such withDCP-NET 8.4. In order to use the preconfiguration of MicroNET 7.3:

Load the MicroNET 7.3 program to the NETCONF program or to the NETPRECONFIGURATION tool.

Make the following changes:

• Define all base systems and workstations as nodes.



118



Installation Guide

• Define all applications by means of base system node number.

• Allocate all stations to an appropriate application (the AL and AS attributes).

If the NETCONF program is used:

Save the new 7.3 configuration as a journal file.

Load the DCP-NET 8.4 program to the base buffer and the 7.3 preconfiguration

journal file to the extra buffer.

Copy the 7.3 configuration to the base buffer and save the program.

If the NET PRECONFIGURATION tool is used:

Load the DCP-NET 8.4 program and copy the 7.3 configuration to it.

Select "EVERYTHING CLEAR DEST. BUFFER FIRST".

Upgrading from 8.1 or 8.2

The preconfiguration of a NET communication program of revisions 8.1 and 8.2can be directly used in 8.4 without modifications. The upgrading from 8.1 or 8.2 to8.4 can be accomplished with the NETCONF program as follows. Enter thecommand:

NETCONF -C’oldfile’ -O’newfile’ NET.82

where 'oldfile' is the name of the old NET program (8.1, or 8.2) and 'newfile' is thename of the new NET program (8.4) including the preconfiguration.

Creating a new NET program file NET1.84 based on the delivered NET programsys_net.1mb and including the preconfiguration of NET1.82:

NETCONF -CNET1.82 -ONET1.84 sys_net.1mb

8.3. Updating device drivers

In general the device drivers are backwards compatible within a major revisionnumber, i.e. drivers in 8.4.2 revision may be used with Base System Software ofrevisions 8.4.1 and 8.4.0. When updating MicroSCADA, the installation should

include the updated drivers.

Driver packages can be installed from the MicroSCADA software CD. Start the

installation as described in Chapter 3 of this manual and select the desired driverpackages in the “MicroSCADA Product Installation” dialog. To use the same driver

configuration with the updated driver, use the option in theMicroSCADA Device Driver Configuration tool menu. This procedure is described

in the “Managing Device Drivers” section of this manual.



SYS 500

IndexInstallation Guide

IndexPage

ACP ...............................................................................................................................74

Additional applications ..................................................................................................26Alarm ........................................................................................................................... 104

Alarm device ............................................................................................................... 109

Alt keyboard key ........................................................................................................... 85

APL_INIT .....................................................................................................................28

APL_START .................................................................................................................28

Application ....................................................................................................................19

Application preparing ....................................................................................................28

Audio alarm unit .............................................................................................................. 3Automatic Flush Cancel ................................................................................................ 64

Automatic Logon ........................................................................................................... 47

Automatic start-up .........................................................................................................77

Automatic startup ..........................................................................................................47

Backup domain controller .............................................................................................17

Cable wiring .................................................................................................................... 8

Clock cards (PC32) ......................................................................................................... 3

Compatibility ............................................................................................................... 114

COMPUTIME ............................................................................................................... 11

Configuration settings ...................................................................................................63

DCF77 ........................................................................................................................... 11

DCP286 card .................................................................................................................67

DCP386 card .................................................................................................................67

DCP-NET .................................................................15, 18, 36, 53, 67, 73, 74, 76, 117

........ .................................................................................................... 55

Device driver .................................................................................................... 15, 18, 31

Device Selected .............................................................................................................64

Dial-up ...........................................................................................................................95

Dial-up modem ..............................................................................................................79

DPC-NET ........................................................................................................................ 6

Driver startup .................................................................................................................35

Emulex NET cards .......................................................................................................... 3

EPSON FX-80 ...............................................................................................................10

EPSON JX-80 ................................................................................................................10

Exceed ...........................................................................................................................81

Exceed X .......................................................................................................................85

Exceed Xconfig .............................................................................................................98

Express installation ........................................................................................................17

FACIT E620 ..................................................................................................................10

1MRS751853-MEN Installation




Index Installation Guide

FACIT3550 ................................................................................................................... 10

File system .................................................................................................................... 17

FOM 6A .......................................................................................................................... 8

Font compilation ........................................................................................................... 30

Forced Stop ................................................................................................................... 47

FPC-046 PC ................................................................................................................ 104

FPC-046 PC INDUSTRIAL I/O ISA card .................................................................... 10

Front-end ...............................................................................................................5, 6, 52

Full-graphic printing ....................................................................................................... 9

GPS ............................................................................................................................... 11

GPS166 ......................................................................................................................... 11

Host name ..................................................................................................................... 51

Host table ...................................................................................................................... 52

HP JetDirect EX Plus .................................................................................................... 10HP JetDirect EX Plus3 .................................................................................................. 10

Installation CD .............................................................................................................. 18

IP address ...................................................................................................................... 51

LAN .........................................................................................................5, 9, 51, 72, 81

LIB500 ..............................................................................................................13, 25, 28

LIN object ..................................................................................................................... 52

LOAD_DCP ............................................................................................................69, 72

LON ..........................................................................................................................6, 53LON cards ..................................................................................................................... 18

LonTalk ........................................................................................................................... 6

Manual startup ............................................................................................................... 47

MFL .............................................................................................................................. 74

MFL.DAT ...................................................................................................................... 52

MFLCONF.DAT ................................................................................................... 76, 111

MFLOAD_E.SET ......................................................................................................... 77

MicroNET 7.3 ............................................................................................................. 117

MicroSCADA fonts ...................................................................................................... 85

MicroSCADA monitor .................................................................................................. 85MicroSCADA monitors ............................................................................................4, 29

MicroSCADA Notification window ............................................................................. 49

MicroSCADA processes ............................................................................................... 48

MicroSCADA user ........................................................................................................ 24

MicroSCADA workstation .......................................................................................9, 85

........ .................................................................................................... 86

MicroSCADA workstation error messages ................................................................... 49

MicroWORKSTATION .................................................................................................. 3

MiSCLONP ................................................................................................................... 60

MiSCPC3x driver .........................................................................................................111

Modem .......................................................................................................................... 87




Index

Installation

Installation Guide

MON object ...................................................................................................................30

MS_WS.EXE ................................................................................................................85

MS-AA ............................................................................................................. 10, 20, 32

MS-CRAM ......................................................................................................... 6, 20, 32

MS-DCP-NET ...............................................................................................................20

MS-PC3X ............................................................................................................ 110, 111

MS-PC3x .................................................................................................................11, 32

MS-PCLTA ......................................................................................................... 8, 20, 32

NET .................................................................................................................................9

NET cables ....................................................................................................................79

NET cards ........................................................................................................................ 3NET_BASCON.COM ...................................................................................................37

NETBIOS ...................................................................................................................... 51

NETCONF ...................................................................................................... 56, 76, 117

Network adapter card ..............................................................................................17, 51

Network tool ..................................................................................................................88

Network Topology .............................................................................................. 3, 17, 25

Network Topology software .......................................................................................... 11

NI Application ...............................................................................................................64

NuDAQ PCI-7250 .........................................................................................................10

Operating system ............................................................................................................. 4

Operator workstation ..................................................................................................... 29

PAC 500 ...................................................................................................................32, 51

Password ..................................................................................................................23, 50

PA-ZC 17 .........................................................................................................................8PC_NET.CF1 ...........................................................................................................37, 56

PC_NET.COM .........................................................................................................37, 65

PC31 .............................................................................................................................. 11

PC32 .............................................................................................................................. 11

PCI-1760 ..................................................................................................................... 104

PCI-1760 PC audio alarm PCI card ..............................................................................10

PCI-7250 ..................................................................................................................... 104

PCI-7250 PC audio alarm PCI card ..............................................................................10

PCLTA .................................................................................................................. 6, 7, 57

PCLTA card ...................................................................................................................55

PCLTA Dual Port ............................................................................................................. 3

PCLTA-20 adapter .........................................................................................................60PCLTA-20 Card installation .......................................................................................... 63

PC-NET .......................................................................................6, 7, 15, 36, 53, 56, 65

Peripheral equipment ................................................................................................... 101

Ping ................................................................................................................................52

PPP protocols ................................................................................................................97

Preconfiguration ............................................................................................................55

PRECONFIGURATION tool ..................................................................................56, 71

Previously installed MicroSCADA ............................................................................... 19

Primary domain controller .............................................................................................17

Printer ......................................................................................................................9, 102

Printers ......................................................................................................................... 101




Index Installation Guide

Priority Boost ................................................................................................................ 50

PSA ................................................................................................................................. 8

Radio clock ................................................................................................................. 110

RAS ............................................................................................................................... 86RCC8000 ............................................................................................................... 11, 111

Remote Access Service ................................................................................................. 86

RER107 ........................................................................................................................... 7

RER111 ........................................................................................................................... 7

REX station ................................................................................................................... 65

RP570 ........................................................................................................................6, 53

RP571 ........................................................................................................................6, 53

RTU210 ........................................................................................................................... 8

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

Screen saver .................................................................................................................. 50Semaphor ........................................................................................................................ 8

Semi-graphic font .......................................................................................................... 98

Semi-graphic printout ................................................................................................... 10

Server ............................................................................................................................ 17

Server computer ............................................................................................................ 94

Service ........................................................................................................................... 46

Shared resources ........................................................................................................... 50

Shutdown.cin ................................................................................................................. 48

Software installation ..................................................................................................... 60

SPA ............................................................................................................................6, 53

SPA_ZP 19A2 ................................................................................................................. 8

SPACOM ....................................................................................................................... 55

SRIO ................................................................................................................................ 8Stand-alone front-end .................................................................................................... 74

Star coupler ..................................................................................................................... 7

Station suspension .................................................................................................98, 103

Stop MicroSCADA ....................................................................................................... 47

SYS_BASCON$COM .................................................................................................. 36

SYS_BASCON.COM ................................................................. 36, 45, 47, 65, 67, 113

SYS_BASCON.HSB .................................................................................................... 36

SYS_CONFIG.PAR ....................................................................................................... 42

SYS_ERROR.LOG ....................................................................................................... 49

SYS_NETCON.COM ................................................................................................... 41

System Image Path ........................................................................................................ 64

TCP/IP .....................................................................................................................51, 97

TCP/IP protocol ............................................................................................................ 93

The display settings ....................................................................................................... 17

The MicroSCADA Administrator ................................................................................. 43

The MicroSCADA Control Panel ................................................................................. 43

The NET communication units ..................................................................................... 53

Tools .............................................................................................................................. 15

Transceiver ................................................................................................................7, 64

Trimble .......................................................................................................................... 11




Index

Installation

Installation Guide

Updating MicroSCADA ................................................................................................ 21

Upgrading .................................................................................................................... 118

User group .....................................................................................................................81

Visual SCIL remote monitor .........................................................................................98

VS remote monitor ....................................................................................................5, 29

Workstation ...................................................................................................................... 5

X monitor ..................................................................................................................5, 98

X server software ........................................................................................................... 18

Xconfig ..........................................................................................................................85

X-monitor ................................................................................................................18, 29

X-server software ............................................................................................................ 9

ABB micro SCADA installation note

Documents

Transcript of ABB micro SCADA installation note