SYS 500 Installation 1MRS MEN. Notice 1. Notice 2. Notice 3. Trademarks

Transcription

1 1MRS MEN Issue date: Program revision: SYS 500 Documentation version: A Copyright 2000 ABB Substation Automation Oy. All rights reserved. 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 version complies with the program revision Notice 3 Additional information such as Release Notes and Last Minute Remarks can be found on the program distribution media. Trademarks Microsoft is a trademark of Microsoft Corporation. Windows NT is a trademark of Microsoft Corporation. LONWORKS is a registered trademark of Echelon Corporation. Other brand or product names are trademarks or registered trademarks of their respective holders. All Microsoft products referenced in this document are either trademarks or registered trademarks of Microsoft.

2 SYS 500 Manual 1MRS MEN Related SYS 500 and MicroSCADA Technology Manuals The following SYS 500 manuals are published with this software release. Picture Editing Visual SCIL User Interface Design Visual SCIL Objects System Management 1MRS MEN 1MRS MEN 1MRS MEN 1MRS MEN 1MRS MUM The following MicroSCADA technology manuals are published with this software release. Connecting LONWORKS Devices to MicroSCADA System Configuration System Objects Application Objects Programming Language SCIL Status Codes 1MRS MEN 1MRS MEN 1MRS MEN 1MRS MEN 1MRS MEN 1MRS MEN ABB Automation

3 1MRS MEN Manual SYS 500 Contents Page 1 Introduction About this Manual Reference Manuals Hardware and Software Requirements Base Systems Hardware Requirements Software Requirements Local Area Network (LAN) Process Communication System Communication Units, NETs...6 Communication Front-ends Process Connections MicroSCADA Workstations Peripherals Printers Alarm Devices Radio Clocks Separate Network Topology Server Installing Base Systems Overview Preparations Installing MicroSCADA Base Product Software Installing Optional Products Managing Applications Configuring the Base System Operator Workstation Managing Device Drivers Editing Configuration Files Base System Administration...43 ABB Automation

4 SYS 500 Manual 1MRS MEN 3.9.1Using MicroSCADA Control Panel and Administrator Start-up and Shutdown Management Supervising MicroSCADA Miscellaneuos Installing and Configuring LAN Installing Process Communication System Overview Installing PC-NET Software and PCLTA Cards Installing and Configuring PC-NET Software Installing Multiport Serialcard Installing PCLTA Cards Installing and Configuring Driver for PCLTA Card Starting and Configuring PC-NET Installing DCP-NET Units in Base Systems Installing Frontends Preparing the PC Installing DCP-NET Cards Installing Frontend Software Configuring Frontends Using Communicaton Frontends Installing NET Connections Installing Workstations Installing Workstations Connected to LAN Installing Workstations Connected via Telephone Line Compiling MicroSCADA Fonts Installing Peripherals Installing Printers Installing MicroSCADA Alarm Units Installing Radio Clocks Upgrading from Previous Revisions Upgrading Base Systems Upgrading DCP-NET ABB Automation

5 1MRS MEN Manual SYS Updating Device Drivers ABB Automation

6

7 1MRS MEN Manual SYS Introduction 1 Introduction This chapter summarises the contents of this manual and lists the most necessary reference manuals. 1.1 About this Manual This manual describes the software and hardware installation of MicroSCADA: base systems, LAN connections, process communication systems, workstations and peripherals. 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. 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 station types.) 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 MicroSCADA application 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 hand during the installation: MicroSCADA System Configuration, Configuration manual ABB Automation 1

8 SYS Introduction Manual 1MRS MEN MicroSCADA System Objects, Technical Reference manual Windows NT and exceed manuals from Microsoft. 2 ABB Automation

9 1MRS MEN Manual SYS Hardware and Software Requirements 2 Hardware and Software Requirements 2.1 Base Systems This chapter specifies the hardware and software required for the installation of MicroSCADA 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. This section describes the hardware and software requirements set by the MicroSCADA base systems Hardware Requirements PC The MicroSCADA base system sets the following requirements on the PC: Processor: Pentium or PentiumPro. Intel 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. ABB Automation 3

10 SYS Hardware and Software Requirements Manual 1MRS MEN Disk space: Minimum: 300 MB Recommended: 1 GB. 2 GB if Network Topology will run on the computer. Disk controller: All operating system supported. 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 Software Requirements Operating System MicroSCADA runs under the Windows NT TM operating system version 4.0 with 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 4 ABB Automation

11 1MRS MEN Manual SYS Hardware and Software Requirements 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. Additional Software The Hummingbird Exceed version is required whenever the base system monitor is used for displaying MicroSCADA X or VS remote monitors. 2.2 Local Area Network (LAN) Figure 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,TCP/IP Protocol Ethernet PC/Windows NT: DOS Computers (frontends): Software: Software: - Included in the operating system - PC/TCP Network Software for DOS, revision 2.05 or later Hardware: Hardware: - Any board supported by the - Ethernetinterface operating system compatible with PC/TCP Figure 1. An overview of the hardware and software requirements for local area networks (LAN) 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 network adapter cards can be used: SMC EtherEZ Ethernet adapter (recommended). 3Com509 (verified in tests). ReadyLINK, ENET Universal Series from COMPEX Inc., USA. ABB Automation 5

12 SYS Hardware and Software Requirements Manual 1MRS MEN LAN Software, PC/DOS See Figure 1. The following LAN software have been verified in PC/DOS computers (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 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. Process connections: LONWORKS network connections, cables, modems, opto modems, etc 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 master and slave, IEC 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. A DCP- 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 base product software and in the front-end software. Internal NETs (DCP-NETs mounted within the base system computer) require the MiroSCADA driver package MS-CRAM, which is also included in the base product software. 6 ABB Automation

13 1MRS MEN Manual SYS Hardware and Software Requirements 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 Communication Front-ends The communication front-ends are PCs containing DCP-NET cards. General Requirements PC specifications: Processor: RAM Memory: Disk memory: Operating system: Free slots: I/O ports: Communication units: Front-end software: Minimum 80486, 66 MHz. Minimum 1 MB MB free disk space. MS-DOS, version 3.3 or later slots for communication boards If communication via LAN is used, 1 slot for the network adapter card. If serial communication is used, COM DCP-NET cards, see above. Included in the front-end software on the MicroSCADA CD. 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 is included in the tool software package delivered on the MicroSCADA installation CD. ABB Automation 7

14 SYS Hardware and Software Requirements Manual 1MRS MEN Fallback switches: The standard redundant front-end application software requires fallback switches, which are control input DTR edge sensitive. Verified in tests: FBS KU13.1 made by KUUMIC Oy, Finland Process Connections LONWORKS Network If MicroSCADA is connected to LONWORKS network, it requires a base system running 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 ABB Transmit Oy and have the product designation RER111. For more information, refer to the RER111 documentation. LONWORKS 1 network interface hardware in PC: 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 opto transceivers RER107 made by ABB Substation Automation Oy. At present, the PCLTA cards including the RER107 transceivers must be purchased from ABB Substation Automation Oy in a mounted and configured condition. If other transceivers are used, other requirements are set on the card configuration. The maximum number of devices (LON nodes) per transceiver is depending on the required communication rate (max 1.25 MB/s). MicroSCADA software: 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. 1 LONWORKS is a registered trademark of Echelon Corporation. 8 ABB Automation

15 1MRS MEN Manual SYS Hardware and Software Requirements NET Modems General requirements: Support for the transmission of 8 data bits, 1 parity bit, 1 start bit and stop bits. Modem verified for communication with stations (not on multidrop lines) and workstations (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: In the SPACOM end: PA-ZC 17 and cable SPA_ZP 19A2 from ABB Transmit Oy 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 V is required. 2.4 MicroSCADA Workstations General PC requirements: Processor: Minimum RAM memory: Disk storage: Operating system: Graphics adapter: Minimum 16 MB. 20 MB free disk space. Windows NT TM 4.0 with Service Pack 3 or Windows 95 with Service Pack 1. Support for 256 colours. X server software requirements: Using a PC as a MicroSCADA workstation requires the X-server software Exceed version from Hummingbird Communications Ltd. ABB Automation 9

16 SYS Hardware and Software Requirements Manual 1MRS MEN LAN requirements: See section 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 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 hardcopy printing via the X software if connected to a base system. Using the printer for semi-graphic MicroSCADA printing. Automatic printing is possible. The printer can be used for semi-graphic hardcopy printing via MicroSCADA and for hardcopy printing via the X server software if connected to 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 by all 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 the printers. This "transparent printing" requires printer type specific code definitions in the 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. LIB 500 uses full-graphic printout for the automatic event and alarm printouts. 10 ABB Automation

17 1MRS MEN Manual SYS Hardware and Software Requirements Semi-Graphic MicroSCADA Printers The semi-graphic MicroSCADA printout is composed of the semi-graphic portions of 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: Pixel-based colour printout: Any EPSON FX-80 compatible printer. Any EPSON JX-80 compatible printers, e.g. FACIT E620 or FACIT3550. 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 printout of the first type. Printers that are connected to a NET can produce any of the three qualities depending on the printer type and system configuration. Printer Servers Alarm Devices The following printer servers have been verified to work properly in MicroSCADA tests: HP JetDirect EX Plus with one parallel port. HP JetDirect EX Plus3 with three parallel ports. I/O and audio alarm cards: FPC-046 PC INDUSTRIAL I/O ISA card made by FLYTECH TECHNOLOGY. NuDAQ PCI-7250 PC audio alarm PCI card made by ADLink Technology Inc. PCI-1760 PC audio alarm PCI card made by Advantech. Cable connection card and alarm panels: Supplied by ABB Substation Automation 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 device may also be added to this system, for example alarm horn or robot telephone. Peripheral Component Interconnect (PCI) bus based audio alarm unit including audio alarm panel and either Adlink s PCI-7250 or Advantech s PCI-1760 audio alarm card. The Flytech based alarm unit occupies two or three ISA slots in the computer depending on whether an additional external alarm device is used or not. This system requires the installation of the MicroSCADA alarm device driver package MS-AA. ABB Automation 11

18 SYS Hardware and Software Requirements Manual 1MRS MEN The PCI based system requires the installation of the PCI-7250 or PCI-1760 audio alarm 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 Radio Clocks Internal Radio clock card can be mounted inside a base system computer or a communication front-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 receiver Meinberg Funkuhren, Germany Accuracy: About ms. The radio clock requires MicroSCADA radio clock driver MS-PC3x. External External radio clocks are connected to a serial port of a communication front-end or a NET: Types: - COMPUTIME with DCF77, MSF or GPS receiver - DIEM Electronic, Geneva, Switzerland - RCC8000 with MSF, DCF77, HBG or WWVB receiver Radiocode Clocks Ltd - Trimble, GPS Receiver. Additional hardware required for connecting to NET and communication front-end. Accuracy: About ms. Receiver features: DCF77: MSF: GPS: 77.5 khz, Mainflingen, Germany khz, Rugby. Satellite based. Global (Global Positioning System). 12 ABB Automation

19 1MRS MEN Manual SYS Hardware and Software Requirements 2.6 Separate Network Topology Server The Network Topology software sets the following requirements when running in a separate computer: Processor: Frequency: Bus architecture: Pentium or PentiumPro. 166 MHz or more. ISA or EISA. Audio alarm unit, NET cards, PCLTA and clock cards require ISA slots. RAM: Minimum: 64 MB Recommended: 96 MB Disk space: Minimum: MB depending on the size of the distribution network. Recommended: 1 GB Disk controller: Any SCSI or IDE controller supported by the Windows NT operating system. Display controller: Screen resolution: At least 1024x768 Colour support: At least 256 colours Display frequency: At least 70 Hz. Mouse: Any mouse supported by Windows NT TM. CD-ROM: Any device supported by Windows NT TM. Required for installation. I/O ports: A parallel port may be used for connecting a printer. Operating system: Microsoft Windows NT TM version 4.0 with Service Pack 3, Workstation or Server. Monitor: If the monitor will be used as a MicroSCADA monitor, it should have the screen resolution of at least 1024x768 pixels and the 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. ABB Automation 13

20

21 1MRS MEN Manual SYS Installing Base Systems 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 a proper and secure operation, before starting the installation, always check that the environmental requirements set by the equipment are fulfilled (power supply, temperature and relative humidity, for example). Check also that all computers are free from viruses. This chapter contains the following sections: 3.1 An overview of the installation procedures and the MicroSCADA base system 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, base system, tools, drivers and NETs. 3.4 Installing optional software products: Network Topology. The installation 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 operator workstation: 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 detailed in chapter 5. Upgrading from previous MicroSCADA revisions is discussed in chapter Overview Procedure The installation of a MicroSCADA base system comprises the following steps: If a local area network will be used, installing the network adapter card. ABB Automation 15

22 SYS Installing Base Systems Manual 1MRS MEN 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, PCLTA cards 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. 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 detailed in the following sections. MicroSCADA Software The MicroSCADA software is delivered on two CDs. The first one contains the MicroSCADA 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. 16 ABB Automation

23 1MRS MEN Manual SYS Installing Base Systems The MicroSCADA base product software comprises the following software packages: Workstation This package includes the MicroSCADA workstation programs. This software opens monitors to the MicroSCADA base system computer. System Base Software System Base Tools Drivers PC NET DCP NET This software package includes the MicroSCADA kernel, administration programs, a standard base system configuration file (SYS_BASCON.COM), standard start-up pictures and dialogs. The installation program creates a directory structured as shown in Figure 2, including an application directory named TUTOR and one named WD. This software package includes the application engineering and system management tools. These software packages include the device drivers used by some of the devices connected to the MicroSCADA system. The drivers are software modules, which handle the communication between the operating system and different devices; 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, a LON driver for PCLTA cards and a LON driver for the PAC 500 computer. Each driver package contains the actual driver, a configuration tool and associated files. This software package includes the PC-NET program, a standard initialisation file and a template for an on-line configuration file. This software package includes the DCP-NET program for the NET cards in the base system computer. ABB Automation 17

24 SYS Installing Base Systems Manual 1MRS MEN Figure 2. The organisation of the MicroSCADA base system files. The LIB 500 and Network Topology software are not included in the figure. 18 ABB Automation

25 1MRS MEN Manual SYS Installing Base Systems 3.2 Preparations Installing LAN Cards If a local area network will be used and the network adapter card is not built-in on the 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 NT operating system installation manual. Here are some notes of importance for MicroSCADA: The type of server must be set to standalone when installing the Windows NT 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). You can use the Express installation 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 64 MB (96 MB for large applications), smaller RAM size may result in degraded performance. For small applications with low functionality and low performance requirements, 32 MB RAM may be sufficient. On the other hand, big applications with 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 not changed at installation, this can be done in the Performance tab of System in the Control Panel. Use TCP/IP as LAN protocol As a LAN protocol, you must select TCP/IP if a LAN will be used for MicroSCADA communication or if Network Topology will be used. Use the NTFS file system Create at least one user belonging to the Users group MicroSCADA system administration - installation, manual start-up and shutdown, etc. - requires a Windows NT user belonging to the Administrators group. During the 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. Display Settings 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 the operating system installation or later. ABB Automation 19

26 SYS Installing Base Systems Manual 1MRS MEN Installing PC Cards Used by MicroSCADA A MicroSCADA base system computer may use a number of PC cards for various purposes: 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 corresponding MicroSCADA 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 the DCP-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 alarm cards and clock card and the configuration of the MicroSCADA device drivers for these devices are detailed in chapter 7. When installing the cards you should keep in mind that the I/O port addresses and the IRQ level used by the cards must not be used by any other device in the computer. 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: DCP386I card: PCLTA card: ISA alarm card: PCI alarm cards: Clock card: 3 I/O port addresses 7 I/O port addresses 8 I/O port addresses 16 I/O port addresses Cards select the necessary I/O port addresses automatically 8 I/O port addresses! An I/O port address used by a card may not be used by any other device in the computer. 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, the X server software (Exceed) has to be installed before the MicroSCADA base system software is installed. The installation of the MicroTOPOLOGY software also requires Exceed. 20 ABB Automation

27 1MRS MEN Manual SYS Installing Base Systems 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 CD contains an installation program, which creates the directory structure and copies the required files to your hard disk. The installation program also creates a new program folder by default named MicroSCADA 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 removed before a new installation. The old files will be overwritten, except for the following ones: In the \sc\prog directory: shutdown.cin 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.CF1 PC_NET.COM SYS_BASCON.COM SYS_CONFIG.PAR SYS_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: 1 Restart the computer to remove possible memory resident data. 2 Log on as a user with administrator rights. 3 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 the MS_base directory by double-clicking the program name. 4 The dialog box in Figure 3.appears on screen. ABB Automation 21

28 SYS Installing Base Systems Manual 1MRS MEN Figure 3. The installation of MicroSCADA begins with this dialog. 5 Click OK to continue the installation or Cancel to quit the installation. 6 A System Information dialog is shown. Click Next to continue. If you decided to continue the installation, the dialog shown in Figure 4. appears. The dialog box lists the software packages. The packages are named as follows: Workstation = System Base Software = System Base Tools = DCP driver = Flytech driver = PCLTA driver = MicroSCADA Workstation software. MicroSCADA Base System software. MicroSCADA Base System Tool software. The RAM driver package for the DCP-NET card located in the base system computer. The alarm driver package. The PCLTA driver package. LON driver for PAC 500 = The driver package for LON on the PAC 500 computer. PC31/PC32 driver = PC-NET = DCP-NET = The PC3x radio clock driver package. The PC-NET software. The DCP-NET software for the base system computer. 22 ABB Automation

29 1MRS MEN Manual SYS Installing Base Systems Figure 4. The dialog for selecting products to install A checkmark in the checkbox to the left of a package name indicates that it is selected 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 driver packages 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. 7 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 drive used in the previous installation is shown as default drive. Otherwise, the default drive will be C:. 8 To change the destination drive, click the Change Drive... button, see Figure 4 and select a new destination drive. ABB Automation 23

30 SYS Installing Base Systems Manual 1MRS MEN! 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. 9 Click Start to continue. Figure 5. Dialog that informs you that there is a package of the specified type already installed. 10 If a previous installation of the selected software package is detected, a dialog like the one in Figure 5 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 boxes are shown which contain information on the existing packages. You can choose to exit the installation procedure of the package or to continue with the new installation and overwrite the existing package. During the installation, a progress indicator and a text, see Figure 6, inform about the installation of the packages. 24 ABB Automation

31 1MRS MEN Manual SYS Installing Base Systems Figure 6. Progress bar indicating installation A message box will inform you when a package has been installed. 11 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. 12 Select the name of the folder in which you want to place the MicroSCADA icons. The default is MicroSCADA. This is asked during installation of the Workstation 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 its name. Click OK. Figure 7. This dialog allows you to change the folder in which the MicroSCADA icons are added 13 After the System Base Software has been installed you are asked to enter a password for a user named MicroSCADA, see Figure 8. The MicroSCADA user will be created during the installation. It will belong to the Administrator group. 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 should be given the same password on both computers. The password can be changed later from the MicroSCADA Control Panel. Note that this user name should not be for other purposes than administration tasks. ABB Automation 25

32 SYS Installing Base Systems Manual 1MRS MEN If the MicroSCADA user already exists due to a previous installation, its password is left unchanged. Figure 8. Entering password for the MicroSCADA user 14 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. 15 The installation is completed with two consecutive dialogs shown in Figure 9 and Figure 10. Click OK in both to complete the installation. Figure 9. The installation of the MicroSCADA base product software has been successfully installed 26 ABB Automation

33 1MRS MEN Manual SYS Installing Base Systems Figure 10. The last dialog of the MicroSCADA base product software installation. Clicking OK will reboot the computer immediately. During the installation, a log file of the installation procedure is written to \sc\prog\exec\sys500.log 3.4 Installing Optional Products Installing LIB 500 Refer to the LIB 500 documentation. Installing Network Topology To install the Network Topology software package: 1 Load the installation CD. 2 Open the Explorer and select the D: drive. 3 Start the MT_540.EXE program in the Topology directory by double-clicking the program name. 4 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 Managing Applications General During the installation of the MicroSCADA kernel software, two empty applications are created. The two applications are named TUTOR and WD. ABB Automation 27

34 SYS Installing Base Systems Manual 1MRS MEN Figure 11. The application directories created at installation You can add additional applications using the administration tools accessed from the MicroSCADA Control Panel. The MicroSCADA administration tools also provide means for listing and removing applications (see section 3.9). When you add an application, the application directories for the new application are created. The startup and initialisation pictures and dialogs are then copied to the application directory apl_. To view, add, prepare or delete applications: 1 Open the MicroSCADA Control Panel by double-clicking its icon: 2 Click Admin. 3 Click Applications. The dialog in Figure 12 appears. 28 ABB Automation

35 1MRS MEN Manual SYS Installing Base Systems Figure 12. The dialog for adding removing and preparing applications Adding Applications To add a new application: 1 Click Add in the Control MicroSCADA Applications dialog box. A dialog named Add new application appears. See Figure 13. Figure 13. Adding a new application 2 Type the name of the application to be created. 3 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. ABB Automation 29

36 SYS Installing Base Systems Manual 1MRS MEN Preparing Applications Preparing an application means copying necessary start-up and initialisation files to the application directory. When an application is added as described above, it is at the same time prepared and no further preparations are required. Likewise, the TUTOR and WD application created during the installation were prepared. However, if you are updating MicroSCADA and have applications, you need to prepare 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: 1 Open the dialog box Control MicroSCADA Applications. 2 Select the application to be prepared. 3 Click Base Tools. 4 Choose one of the following options: Full prepare Limited prepare to copy all initialisation files and pictures to the application directory. Possible existing files are overwritten. to copy initialisation files but not the APL_INIT and APL_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 use Limited prepare. To prepare an application for LIB 500: 1 Follow the steps 1 and 2 as in preparing an application. 2 Click LIB Refer to the LIB 500 documentation to complete the preparation. Removing Applications To remove an existing application: 1 Open the dialog box Control MicroSCADA Applications. 2 Select the application to be removed. 3 Click Remove. The selected application directory and its sub-directories will be deleted. 3.6 Configuring the Base System Operator Workstation General A MicroSCADA base system operator workstation is a computer running the MicroSCADA base system software. The display of the computer can be used for showing MicroSCADA monitors. 30 ABB Automation

37 1MRS MEN Manual SYS Installing Base Systems If the base system display is used as a MicroSCADA operator workstation, the colour palette of the display should hold at least 256 colours. You can check and modify 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 showing MicroSCADA 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 as follows: 1 Open the Control Panel (click Start, point Settings and click Control Panel). 2 Double-click the icon that represents the Display properties. 3 Select the Settings page, see Figure Select 256 Colors or more, in the Color Palette. 5 Test the setting by clicking Test. 6 If the test was OK, accept the change and exit the Display Properties by clicking OK. ABB Automation 31

38 SYS Installing Base Systems Manual 1MRS MEN Figure 14. MicroSCADA requires that the Color Palette holds at least 256 colors 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 the Exceed 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 the base system configuration. The MicroSCADA system requires one MON object per monitor. The delivered SYS_BASCON.COM configuration file contains the definition of 10 MON objects for the application TUTOR, 5 X type objects and 5 VS type objects. See the System Configuration manual, chapter ABB Automation

39 1MRS MEN Manual SYS Installing Base Systems 3.7 Managing Device Drivers General During the installation of the base system software, you had the possibility to install the MicroSCADA device driver packages. Even if the driver packages were selected for installation, the drivers are not yet ready for use, but must be configured 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 some other configuration data. When a driver has been installed and configured it should be tested and configured for automatic start-up. Hence, the entire procedure is as follows: Installing the driver packages. Configuring the drivers. The drivers cannot be configured until the corresponding hardware 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 corresponding hardware installation is described, i.e., in chapters 5 and 7. When updating a driver package to a new version, you need not configure the device driver again if you 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 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 the device driver management tools: 1 Open the MicroSCADA Control Panel by double-clicking its icon: ABB Automation 33

40 SYS Installing Base Systems Manual 1MRS MEN 2 Click Admin. 3 Click Drivers. The following dialog appears: Figure 15. The driver menu accessed from the MicroSCADA Control Panel Select the device driver you wish to view, configure or manage by clicking the corresponding 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 their manufacturers 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. MS-LONPAC = device driver for the LON interface on PAC ABB Automation

41 1MRS MEN Manual SYS Installing Base Systems Now the MicroSCADA Device Driver Configuration tool for the selected driver appears, see Figure 16. Figure 16. The MicroSCADA Device Driver Configuration tool menu 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 the installed package. This option is useful if you have installed a new device driver package and wish to compare it with a driver you have already configured. See Figure 17. Figure 17. This dialog informs you about the already installed driver version Update Driver Add Device Remove Device This selection replaces the configured device driver with the driver from the previous installed package installed driver. The configuration settings remain unchanged. Use this option when you have installed a new version of a driver package. Configuring a the device driver for a new device. The device driver configuration is detailed in the context where the hardware installation of the device is described, i.e., in chapters 5 and 7. Removing an existing device configuration. ABB Automation 35

42 SYS Installing Base Systems Manual 1MRS MEN Change Settings Re-configuring an already configured device. Testing the Drivers After configuring the drivers as described in chapter 5 and chapter 7, they should be tested. Reboot the system to make the settings take effect. If you are configuring the drivers for the first time, they are not started automatically after booting, but must be started manually. This is to avoid problems in case of problems with the configuration settings. To start a driver: 1 Open the Control Panel (click Start located in the taskbar, point Settings and click Control Panel). 2 Double-click the icon that represents the Devices. 3 Select the driver from the list of Devices (see Figure 18). 4 Click Start. Figure 18. The tool for starting device drivers If an error message appears, or if the device driver does not seem to work, the probable cause is conflicting settings. Settings may conflict due to the following two 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 the interrupt 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 be that 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. 36 ABB Automation

43 1MRS MEN Manual SYS Installing Base Systems To start the Event Viewer: 1 Click Start (located in the taskbar). 2 Point Programs. 3 Point Administrative Tools. 4 Click Event Viewer. To investigate in detail how your system is configured use the Windows NT Diagnostics 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: 1 Click Start (located in the taskbar). 2 Point Programs. 3 Point Administrative Tools. 4 Click Windows NT Diagnostics. If no error message appears, the device driver has started and the installation can be regarded as successful as far as the operating system is concerned. However, the operation 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 set automatic. This means that the device driver is started automatically together with the operating system: 1 Open the Control Panel (click Start located in the taskbar, point Settings and click Control Panel). 2 Double-click the icon that represents the Devices. 3 Select the driver from the list of Devices. 4 Click the Startup. 5 Change the startup type to Automatic (see Figure 19). 6 Click OK. Figure 19. Setting the startup type of a device driver to automatic ABB Automation 37

44 SYS Installing Base Systems Manual 1MRS MEN 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 two SYS_BASCON.COM template files, one for configuring a single base system and one for configuring a hotstand-by base system. The template file for a single base system, SYS_BASCON$COM, is during installation copied to SYS_BASCON.COM if the SYS_BASCON.COM does not previously exist. The template file for hot-stand-by systems is called SYS_BASCON.HSB. The SYS_BASCON$COM template file defines a system configuration as presented in Figure 20. 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 internal DCP-NET cards. One node is connected to the TCP/IP LAN link and one node, which is running the PC-NET communication software is connected over an integrated link to the base system. The configuration allows ten MicroSCADA monitors to be opened to the TUTORapplication. Figure 20. The system configuration defined by the delivered configuration software Also the other configuration files included in the delivery (NET_BASCON.COM, the DCP-NET preconfiguration, PC_NET.CF1 and PC_NET.COM) conform with the configuration in Figure ABB Automation

45 1MRS MEN Manual SYS Installing Base Systems The contents of the SYS_BASCON$COM file is listed below. Some configuration definitions have been excluded by commenting them. They can be taken into use by removing the comment sign in front of the #CREATE command that creates the base system object. To edit the current SYS_BASCON.COM: 1 Open the MicroSCADA Control Panel. 2 Click Admin. 3 Click Config. The SYS_BASCON.COM file is opened in the Notepad program for editing. 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 ; ; ;Base System = 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 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 t_version = "8.4.2")),- - ;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, 2=INFORMATION, 3=AUDIT_SUCCESS, 4=AUDIT_FAILURE) Bit_Mask(0,1,2,3,4)),- ;Security events (Bit 0=ERROR, 1=WARNING, 2=INFORMATION, 3=AUDIT_SUCCESS, 4=AUDIT_FAILURE) - FS = "NEVER") ;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 ABB Automation 39

46 SYS Installing Base Systems Manual 1MRS MEN LI = 1,- ;Link number SA = 201) ;Station address: ;#CREATE NOD1:B = %NOD #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 PRI2:B = %PRI #CREATE PRI:V = LIST(- TT = "LOCAL",- DT = "COLOR",- DC = "NET",- ND = 4,- ;NET node number: TN = 1,- ;Translated object number (printer nr in net) LP = 66) ;#CREATE PRI3:B = %PRI ;#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) ;#CREATE PRI15:B = %PRI ; ;Monitors #LOOP_WITH I = 1..5 #CREATE MON I :B = LIST(- TT = "LOCAL",- DT = = -1 #LOOP_END #LOOP_WITH I = #Create MON I :B = LIST(- TT = "LOCAL",- DT = = -1 #LOOP_END ;Translation type ;X monitor ;Translation type ;Visual SCIL monitor ; ;Applications ;The usage of OI & OX -attributes (required by LIB = 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,- 40 ABB Automation

47 1MRS MEN Manual SYS Installing Base Systems 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 = list() ;Add LIB5xx global paths to list if LIB5xx = "/LIB4/Base/Bbone/Use/Bgu_Glpath.txt" #if File_Manager("EXISTS", Fm_Scil_File(%t_LIB_Path_Def_File)) #then #block #error = 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 = 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 ;#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) ; 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" ; ABB Automation 41

48 SYS Installing Base Systems Manual 1MRS MEN ;Node, Link for PC-NET & = do (read_text("sys_tool/create_c.scl"), "BASE_SYSTEM") ; ;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 By removing the semicolons from the file, you can make it load and start the internal communication 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-up before the execution of SYS_BASCON.COM. SYS_CONFIG.PAR can be edited with a text editor. SYS_CONFIG.PAR can contain the following parameters and set values: MEMORY_POOL_SIZE specifies the size of the global memory pool in megabytes (MB). Possible values are: 4, 8, 12, 16, 20, 24,..., that is a value divisible with 4. Default, if no value is given in SYS_CONFIG.PAR, is 20 MB. For example the line: MEMORY_POOL_SIZE = 24 sets the size of the global memory pool to 24 MB. ANALOG_SWITCH_STATE_CLOSED (default = 1) ANALOG_SWITCH_STATE_OPEN (default = 2) ANALOG_SWITCH_STATE_MIDDLE (default = 0) These parameters define the translation of the CLOSED, OPEN and MIDDLE states returned by the program interface function SCIL_Get_Switch_State. ASYNCHRONOUS_SHADOW_RECEIVER (default = 1) 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 base system A is shadowed to an application in base system B, and an application in base system B is shadowed to an application in base system A. 42 ABB Automation

49 1MRS MEN Manual SYS Installing Base Systems Configuration of Local Memory Pool There are three configuration parameters in SYS_CONFIG.PAR concerning local memory pools to consider: PICO_MEMORY_POOL_SIZE REPR_MEMORY_POOL_SIZE PRIN_MEMORY_POOL_SIZE Determines the size (as megabytes) of the local memory pool of all the monitor processes in the system. The default value is 8 MB. Determines the size of the local memory pool of all repr processes. The default value is 4 MB. Determines the size of the local memory pool of all prin processes. The default value is 2 MB. Setting a pool size to 0 demands the processes of the category to always use the global memory pool. If a process requires more memory than the specified memory pool size allows the dialog "SCIL Application Error/Memory Pool Exhausted" is shown. The dialog shows a critical error with information about which pool caused the error. The information is either "Local memory pool exhausted" or "Global memory pool exhausted". If the SYS_CONFIG.PAR file does not exist the default values are used. A template, SYS_CONFIG$PAR is copied to \sc\sys\active\sys_ during the installation of the System Base Software package. The contents of the SYS_CONFIG$PAR is: ; File: Sys_config.par ; Description: Configuration for static base system parameters ; leading ; indicates commented line ; Version ; ; ;MEMORY_POOL_SIZE = 20 ;Must be 4,8,12,16,20,24,28,... (MB) ;PICO_MEMORY_POOL_SIZE = 8 ;Memory Pool for Monitor processes ;REPR_MEMORY_POOL_SIZE = 4 ;Memory Pool for Report processes ;PRIN_MEMORY_POOL_SIZE = 2 ;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 Panel or in the MicroSCADA Administrator. These tools can only be run on the MicroSCADA base system computer. ABB Automation 43

50 SYS Installing Base Systems Manual 1MRS MEN Using MicroSCADA Control Panel and Administrator MicroSCADA Control Panel To open the MicroSCADA Control Panel: 1 Double-click the MicroSCADA Control Panel icon. The Figure 21 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. Figure 21. The MicroSCADA Control Panel 2 To exit the MicroSCADA Control Panel dialog without choosing any of the options, click Quit. MicroSCADA Administrator To open the MicroSCADA Administrator: 1 Click Admin in the MicroSCADA Control Panel. 44 ABB Automation

51 1MRS MEN Manual SYS Installing Base Systems The MicroSCADA Administrator is shown in Figure 22. Figure 22. The MicroSCADA Administrator dialog box Options of the MicroSCADA Administrator dialog: Applications Service Password Autologon Config View Drivers Opens a dialog used for managing applications. Opens a dialog for setting start-up type for MicroSCADA service. Opens a dialog for changing the password for the MicroSCADA user. Opens the dialog Windows NT Automatic Logon. (See also System Management manual.) Opens the Notepad editor for editing SYS_BASCON.COM. Opens a dialog showing MicroSCADA processes. Starts the driver configuration programs. ABB Automation 45

52 SYS Installing Base Systems Manual 1MRS MEN Start-up and Shutdown Management Starting MicroSCADA Manually To be able to start MicroSCADA manually, you must be a user belonging to the Administrator group. To start MicroSCADA manually: 1 Click the Start in the MicroSCADA Control Panel. 2 Click OK in the message which appears, see Figure 23. Figure 23. This message tells that MicroSCADA has started 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 MicroSCADA program 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 kernel continues 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: 1 Click Stop in the MicroSCADA Control Panel. When MicroSCADA has stopped, the following dialog box appears. Figure 24. This dialog appears when the MicroSCADA service has been stopped 2 Click OK in the message box. 46 ABB Automation

53 1MRS MEN Manual SYS Installing Base Systems! Do not shut down or restart the computer while MicroSCADA is running. In exceptional situations, for example if MicroSCADA does not start properly due to an error in the SYS_BASCON.COM file, you may wish to stop MicroSCADA without 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 Management below. Start-up Management MicroSCADA can be started manually or automatically. When using automatic startup of MicroSCADA, MicroSCADA is started directly after the computer has been switched on or restarted and the operating system has started. To select automatic or manual start-up: 1 Click Service in the MicroSCADA Administrator. The following dialog box appears. Figure 25. The dialog box for startup management 2 Select Automatic startup, Manual startup or Disabled. Disabled means that MicroSCADA cannot be started. 3 Click OK. Automatic Logon Automatic Logon means that a user is automatically logged on when the computer is started. To enable automatic logon: 1 Select the AutoLogon button in the MicroSCADA Administrator. The dialog box in Figure 26 appears. ABB Automation 47

54 SYS Installing Base Systems Manual 1MRS MEN Figure 26. The dialog box for selecting automatic logon 2 Enter the name and password of the user. 3 Select Automatic Logon Enabled. 4 Click OK. To remove the automatic logon select Automatic Logon Disabled. This action also requires 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\exec directory. 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 editing the program file with text editor, the MicroSCADA system administrator can add other functions. However, the program must not require more time than 2 minutes to execute. When Forced Stop has been selected, MicroSCADA is stopped immediately without executing the SCIL program stored in the shutdown.cin file 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 CPU time 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 48 ABB Automation

55 1MRS MEN Manual SYS Installing Base Systems displayed as a checked option under priority in the dialog. To update values click Refresh. Figure 27. Viewing running MicroSCADA processes MicroSCADA Error Supervision The MicroSCADA workstation error messages are stored in an error log file named SYS_ERROR.LOG and located in the SYS_ directory. The messages are also displayed in the MicroSCADA Notification window as they are produced. You can open up to 8 MicroSCADA Notification windows per base system. Each window can display the last 1000 messages produced. To open a Notification window on the base system: 1 Double-click the MicroSCADA Notify icon. How to open MicroSCADA Notification windows on workstations is described in chapter 6. ABB Automation 49

56 SYS Installing Base Systems Manual 1MRS MEN 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: 1 Add a user named MicroSCADA in the other computer and assign it the same password as the password of the MicroSCADA user defined in the base system computer. The user should belong to the User or Administrator group. 2 Add the MicroSCADA user to the list of users for the specified shared resources. MicroSCADA accesses the shared resources in the other computer by using UNC references. Changing Password The password of the MicroSCADA user entered during installation can be changed. To change it: 1 Click Password in the Administrator menu. The same dialog appears as during the MicroSCADA software installation. 2 Enter the new password and confirm it. 3 Click OK. Performance Notes To 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 the operating system (click Start located in the taskbar, point Settings and click Control Panel, double-click System, select the Performance page). 50 ABB Automation

57 1MRS MEN Manual SYS Installing and Configuring LAN 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 LAN nodes on a TCP/IP network. Network Adapter Card Each computer on the LAN contains a network adapter card and software for handling 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 adapter card. 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 software is installed during the installation of the operating system. In the PC/DOS computers used by communication frontends, you can insert the network adapter card before or after you have installed the operating system. Refer to 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. aaa.bbb.ccc.ddd The address is requested during the configuration of the LAN software, i.e., during the installation of the Windows NT operating system in the base system and workstation computers, and during the installation of the PC/TCP software in frontends. The IP addresses of the MicroSCADA base system, workstation and frontend computers must comply with the addresses of other nodes on the network. Consult your local area network administrator for valid IP addresses and other LAN configuration issues. Host Names During the installation of the Windows NT operating system, you will give the computer a name. This is the computer name for the NETBIOS protocol under which the computer will be recognised on the LAN. Note that this name is not the same name as the host name used by TCP/IP. The host name is given when configuring the TCP/IP protocol. ABB Automation 51

58 SYS Installing and Configuring LAN Manual 1MRS MEN You can read the host name and IP address of computer by entering: ipconfig /all in a Command Prompt window on a computer with Windows NT or at the DOS prompt 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 names to be recognised 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 lowercase letters and one in uppercase letters. The items in a host table are separated by spaces or tabs mscada MSCADA unix UNIX pcx PCX mw MW mfl1 MFL 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 for information 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 is available and functional. The syntax is: ping host 52 ABB Automation

59 1MRS MEN Manual SYS Installing and Configuring LAN 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. Example: ping Reply from : bytes=32 time < 10ms TTL 255 For more information on ping and how to use it, see the on-line help of the utility. ABB Automation 53

60

61 1MRS MEN Manual SYS Installing Process Communication System 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 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 28. 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 a specific ISA bus based card family called DCP. The DCP card is manufactured by Emulex. PC-NET. The PC-NET runs on the base system computer. PC-NET supports: ACP (the MicroSCADA internal protocol), LonTalk, SPA, IEC master and slave, IEC master, IEC 1107, RP570 master and slave, RP571 master, 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 a communication 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 unit specific preconfiguration. The program is stored on disk in the host computer and loaded to the RAM memory of the unit at startup. ABB Automation 55

62 SYS Installing Process Communication System Manual 1MRS MEN Figure 28 illustrates the NET types and their connections. The NET communication lines are described below. A DCP-card A base system with two DCP-cards EightNET lines PC rearpanel 16 serialnet lines connected to process stations, NETs,front-ends,base systems A base system with a PC-NET Two PCLTA cards,each with two channels PC-NET program Stand-alone front-end containing fourdcp-cards COM ports PC rearpanel A base system with a PC-NET Two PCLTA cards,each with two channels PC-NET program Multiport COM ports serialcard 8 COM ports PC rearpanel 4 NET lines (Serial) 4 NET lines (LonTalkprotocol) PC rearpanel 32 serialnet lines connected to processstations, NETs,front-ends,basesystems 4 NET lines (LonTalk protocol) The totalnumberofpc-net lines is max.8 8 NET lines NET lines are apportioned among serialand LonTalk (Serial) Figure 28. The different NET types, their locations and possible connections. Note that the last setup of hardware in the picture allows the use of all eight NET lines 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 Each of the serial lines can be 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 the protocol assigned to the line in the NET configuration. Besides the eight serial lines, the DCP-NET program uses logical line for communication 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 system computer 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 and NET connections. 56 ABB Automation

63 1MRS MEN Manual SYS Installing Process Communication System Communication Lines of PC-NET Units The PC-NET use the serial ports (COM ports) of the PC or COM ports of a multiport serial 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 By default, line number 1 corresponds to COM1, line number 2 to COM2, and so on. These lines can be 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 by assigning 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 serial ports. 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 Assigning appropriate 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 line numbers. If no COM ports are used, the numbers 1 to 8 can be chosen. If four COM ports 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 device name. 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. If the PCLTA card driver is configured as recommended in this manual, the channels will correspond to line numbers , 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 the station 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 the programs. This configuration is called preconfiguration and it specifies, among other things, the node number of the unit (default = 1). The preconfiguration serves as a default configuration. It can be edited using the NET PRECONFIGURATION tool 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 file contains 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 completely ABB Automation 57

64 SYS Installing Process Communication System Manual 1MRS MEN configured with SCIL. The SCIL configuration is done using SCIL commands and the 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 see System Configuration Chapters 3 and Installing PC-NET Software and PCLTA Cards Overview The installation and configuration of a PC-NET in a base system comprises the following 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 of PCLTA cards is closely related to the PC-NETs 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 be installed 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-NET directory 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 file defines the basic communication nodes and addresses to enable the communication with the application that will download the total configuration. The initial configuration file is a text file composed of a number of lines, each of which specifies an attribute (see below). The attributes are referred to with the notation: object.attribute The possible objects are: local_node ext_node The PC-NET program itself An external node (the base system where the NET is situated) 58 ABB Automation

65 1MRS MEN Manual SYS Installing Process Communication System ext_apl The application in the base system where the NET is situated 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, station address = 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 within the 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 local_node.nn=3 ext_node(1).sa=209 ext_node(1).nn=9 ext_apl(1).nn=9 ext_apl(1).an=1 ; the station address of the PC-NET ; the node number of the PC-NET ; the station address of the base system ; the node number of the base system ; the node number of the base system ; an application in the base system All line and station configuration of the PC-NET, as well as the definition of other nodes and applications, must be done with SCIL after the NET has been started Installing Multiport Serialcard As PC-NET supports 8 communication lines, additional COM ports are required if communication 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 one IRQ. The numbering of the COM ports is handled during installation of the carddriver. As to the installation procedure, refer to the installation manual of the multiport serialcard. The serialcard model that has been tested and verified is named RocketPort, made by Comtrol Corporation 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 29. Each of the channels will be a NET line connected to a star coupler of a LONWORKS network. ABB Automation 59

66 SYS Installing Process Communication System Manual 1MRS MEN X X X X I/O address Tranceiver ChannelA Tranceiver ChannelB Figure 29. A PCLTA-10 card The PCLTA-20 adapter includes either an integral twisted pair transceiver or an SMX transceiver (Model 74405) interface. For models with an integral twisted pair transceiver, the network connection is made via a removable screw terminal block. The use of the PCLTA card(s) requires the installation and configuration of a MicroSCADA or an Echelon device driver. During the device driver configuration, each channel is given a device number. By default, the NET line numbers of the channels 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 two versions of the PCLTA-20 installation software, one for Windows 95/98 and one for Windows NT. Each version installs the files required by the associated Windows operating system to recognise the PCLTA-20 adapter, as well as the downloadable NSI (network services interface) and MIP (Microprocessor Interface Program) images. of the software must occur before insertion of the PCLTA-20 adapter into a PC s PCI slot. software is provided in the Connectivity Starter Kit Model (which must be purchased separately from Echelon Corporation), and provides a software-based control panel and a software driver for Microsoft Windows 95/98 or NT operating systems. software is also available on Echelon s web site at 60 ABB Automation

67 1MRS MEN Manual SYS Installing Process Communication System Further software and hardware installation and PCLTA-20 device driver configuration 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 to initialise the PCLTA card and it offers more information on LONWORKS network as well. Additional configuration advises: If you use the SMX card (model 74405) and RER 107 transceiver card, use the custom setting for the transceiver. Set the Automatic Flush Cancel off. From the NT Diagnostics, you should check that the device (pnplon) has appeared 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 described in the PCLTA manual. See also Figure 29. You can select any free I/O address 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 29. Other possible values are 300, 308, 310, and 378 hex. Write down the selected I/O address. An example is shown in Table 1. This information will be needed during the driver configuration. 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. ABB Automation 61

68 SYS Installing Process Communication System Manual 1MRS MEN Table 1. The PCLTA card information needed during system configuration. The device names are needed only if you wish to redefine the NET line numbering. Card no. I/O address Channel Device no. = n Dev. name = LONPn NET line = n +1 1 A B 2 A B Installing and Configuring Driver for PCLTA Card Opening and Configuration Tool To open the installation and configuration tool for PCLTA card drivers: 1 If the MiSCLONP is not already installed, install the driver package as described in section Start the MiSCLONP Configuration tool. See section Click Add Device to configure the driver for the first time, or select Change Settings to reconfigure it. Configuring PCLTA Driver Figure 30 shows the dialog box that appears when you click Add Device. Figure 30. Starting the driver configuration To configure the MiSCLONP driver: 1 Enter the following data: Card Number Type of Card The number of the card. It is recommended that you set the first card as card number 0, the second card as card number 1 and so on. The type of the card. The PCLTA Single Channel and PCLTA Dual Channel card types are supported. 62 ABB Automation

69 1MRS MEN Manual SYS Installing Process Communication System 2 Click OK. A dialog box shown in Figure 31 appears. In this dialog you specify each of the channels of the card. Figure 31. The configuration of the channels 3 Enter the following data for each of the channels on the card: Device Number The device number. Each channel is seen as a device with a device number. It is recommended that you set channel A on card 0 as device 0 and channel B as device 1. Then use numbers 2 and 3 for the two channels on card 1. In this way, channel A on card 0 will be NET line number 1 by default, and the others will be NET line numbers 2, 3 and 4. I/O Port Address IRQ Level Clock Select Uplink Buffers Downlink Buffers DL Priority Buffers Flush cancel at init The I/O base address of the card. This must be the same as the address set physically on the card. If a card has two channels, channel B is automatically given an I/O base address, which is 4 + the address of channel A. The interrupt level used by the channel. This must be unique among all devices in the computer. Allowed values are 5, 9, 10, 11, 12, and 15. You can check which one is free in the Windows NT Diagnostics tool, Resources. The Neuron clock rate for the channel. You can use the default value, 10 MHz. The number of uplink buffers used by the channel. You can use the default value, 20. The number of downlink buffers used by the channel. You can use the default value, 20. The number of downlink priority buffers used by the channel. You can use the default value, 20. If this option is checked (default), the device driver will issue the niflush_cancel command to the network interface after reset. This means that the Network interface is ABB Automation 63

70 SYS Installing Process Communication System Manual 1MRS MEN reset into NORMAL state and can participate in Network transactions. If no niflush_cancel command is issued, the Network interface remains in a FLUSH state where it ignores all incoming messages and prevents all outgoing messages. 4 Click OK and define the next channel on the card in the same way, and then the next card. 5 When all cards and channels have been configured, test the driver and configure automatic start-up of the driver as described in section 3.7. Configure the LON-PAC Driver The LON-PAC driver is exclusively used with the PAC 500 computer that has the LONWORKS network adapter on the motherboard. 1 To install and configure the driver, click MS-LONPAC in the MicroSCADA Driver Configuration dialog. This will open the MiSCLOND Configuration for MicroSCADA dialog. 2 From the MiSCLOND Configuration for MicroSCADA dialog click Add Device if you are installing the driver or Change Settings if you are reconfiguring the driver. 3 In the appearing MiSCLOND Add Device dialog, the first 6 fields are grayed and can not be edited. The next 6 fields have predefined alternatives in dropdown boxes. Use of the default values is recommended. 4 As default the Flush cancel at init option is checked. For further inf., see configuring PCLTA Driver above. 5 Click OK. A message is displayed if operation is successful. 6 Click Close. A message about rebooting the computer before changes take place is displayed 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 the comment 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. The standard 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 comment sign (;) front of the #CREATE NOD3:B command. 64 ABB Automation

71 1MRS MEN Manual SYS Installing Process Communication System Configuring PC-NET On-line After the PC-NET has been started, it must be configured on-line with SCIL with regard to the NET lines, connected stations, and possibly other NET and base system connections. 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. The standard base system configuration file, SYS_BASCON.COM contains the station definitions 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. The contents of the default PC_NET.COM is listed below: ;********************************************************************* ; ; PC_NET.COM ; PC-NET CONFIGURATION TEMPLATE ; = = = = = 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 = #IF (STA REX :BST=="REX") AND - (STA REX :BND==%PC_NET) AND - (STA REX :BTT=="EXTERNAL") #THEN #BLOCK #ERROR IGNORE #SET STA REX :SIU = = STA REX :BTN #SET NET PC_NET :SRX REX_NR = "D" #ERROR STOP #BLOCK_END #LOOP_END #LOOP_WITH I = 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 = %REX #LOOP_END ABB Automation 65

72 SYS Installing Process Communication System Manual 1MRS MEN ;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 #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 #LOOP_WITH I = #SET STA REX :SIU = 1 #LOOP_END #SET NET PC_NET :SIU LON_LINK = 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 program contains the node number of the NET unit (= NET system object number). Select a unique node number, , 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 " below. In the delivered SYS_BASCON.COM file, the internal NETs are given node numbers 1 and 2. The node number must be unique among all connected communication units, base systems, 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. 66 ABB Automation

73 1MRS MEN Manual SYS Installing Process Communication System Setting Jumpers and Switches At this stage you need to know the free interrupt levels and I/O addresses in the base system 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 the computer. 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). To set jumper and switches: 1 Set the interrupt level of the card to a unique value, and set the I/O base address. Figure 29 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 Diagnostics tool, Resources. Write down the interrupt level and I/O base address you select. For this you can use the Table 3. You will need them during the driver installation. Select one of the cards for device 0 and the other one for device 1. 2 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: 1 Fasten each card to a full-size 16 bit slot in the base system computer. Any free slot can be used. For more information see the installation guide of the card. 2 Connect the 80 pin connectors to the rear of the cards and mark them with the same node number as the card. DCP board Interrupt Level Turn board around I/Obase addresses) ON ON I/O base address: 2BC ON I/O base address: 23C ON I/O base address: 33C I/O base address: 1FC Figure 32. I/O addresses to be used on the DCPNET cards in communication frontends. The same I/O addresses can be used in internal NETs. ABB Automation 67

74 SYS Installing Process Communication System Manual 1MRS MEN Table 2. The information needed for the installation and startup of internal NET units. The shaded fields are needed for startup with the SCIL function LOAD_DCP. The link number is defined by a LINn:B base system object. For more information see System Configuration, section 8.2 Device no. Device name Node No. Interrupt Level I/O Base Address Link No. File Name 0 RM00 1 RM01 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 Table 2. In addition, each device requires a shared memory base address. 1 If the MS-CRAM package is not already installed, install the driver package as described in section Start the driver configuration program. For more information see section Click Add Device to configure the driver for the first time. To reconfigure it, click Change Settings. Figure 33 shows the dialog box shown for the user when configuring the device driver 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 the hardware settings on the cards. Figure 33. The configuration of the RAM driver 4 Enter the following configuration data most of which you find in Table 2: 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 ABB Automation

75 1MRS MEN Manual SYS Installing Process Communication System Type of Card IRQ level I/O Port Address Shared Memory On-card Memory Size Window Size The type of the card. The following card types are supported: DCP/MUXi, DCP-286i, DCP-386i. The interrupt level used by the card. The interrupt level must be the same as the level set on the card. The I/O base address used by the card. This must be the same as the address set on the card. Base AddressThe start address of the shared memory. The DCP-NET cards use by default 16 kb of shared memory (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. The size of the memory on the card. Both DCP286i and DCP386i have 1024 KB. The window size used when gaining access to the card s memory. The default 16 KB should not be changed. Each of the cards gets a device name, which is RM00 for device number 0 and RM01 for 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 2. 5 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 SCIL function LOAD_DCP (see the SCIL manual, chapter 8). During the installation of the 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 NET PRECONFIGURATION tool, which is accessed from the Tool Manager. The configuration requirements and the configuration tool are described in the System Configuration manual. 1 For safety, copy the delivered NET program to another name in the same SYS_ folder. 2 Open the NET PRECONFIGURATION tool (see System Configuration). 3 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. 4 Save the program with a name starting with SYS_ and including the node number. 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. ABB Automation 69

76 SYS Installing Process Communication System Manual 1MRS MEN In case the program is given a name, which does not begin with SYS_, it will be searched for in the PICT folder. Then a logical path referring to the SYS_ folder must 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: 1 Define a link object, LINn:B for each of the NETs. 2 Define each of the NETs as a node, a NODn:B object. 3 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. 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 in SYS_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 used driver as arguments are given as arguments. For more information see the Programming Language SCIL manual, Chapter Installing Frontends Overview The frontends are computers especially reserved for process communication. They can communicate with one or more base systems via a LAN, or they can be connected to a NET via a COM port of the frontend computer. A frontend can contain DCP- NET cards. The installation of communication frontends comprises the following steps, which are detailed below: 1 Preparing the computer. 2 Installing the DCP-NET cards. 3 Installing the DCP-NET programs. 4 Configuring the frontend Preparing the PC Configuring PC To configure the computer, do the following in the SETUP utility of the PC: 1 Remove shadow RAM and video ROM shadow. 70 ABB Automation

77 1MRS MEN Manual SYS Installing Process Communication System 2 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 section 2.4. The installation of LAN is briefly described in Chapter 4.! When installing the network adapter card do not use the RAM addresses, I/O addresses and interrupt levels used on the communication cards, see Table 3. Miscellaneous Notes! If a mouse driver is used, do not use the interrupt levels 3, 5, 12 or 15 on the mouse driver. If using any of the interrupt levels on the mouse driver cannot be avoided, only three DCP-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 Installing DCP-NET Cards Overview The hardware installation of DCP-NET cards in the frontend includes the following steps: 1 Mark the communication cards. This is not required but recommended for clarity. 2 Define jumper and switch settings of the cards. 3 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, , 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 " below. The node number must be unique among all connected communication units, base systems, remote semi-graphic workstations and communication frontends within the MicroSCADA distributed Network. For more ABB Automation 71

78 SYS Installing Process Communication System Manual 1MRS MEN information see the System Configuration manual, Chapter 5. It is necessary to know the node number of the NET unit when connecting devices to it. Jumpering and Switch Setting To set jumpers and switches: 1 Set the I/O base address and the interrupt level to the values given in Table 3. 2 See also Figure 32 which shows the possible I/O base addresses. 3 If you have a DCP-286i card, remove the jumper on AB and place it on BC. This is needed for revision information handling. 4 Write down the node numbers of the DCP-NET cards together with their respective I/O addresses, for example, in Table 3. 5 This is necessary for the subsequent software installation and start-up. The frontend reserves automatically the RAM addresses given in Table 3 for the 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, or for the mouse. Table 3. The information needed for the installation and startup of the communication units within a communication frontend. Card no. Node no. I/O Base address Interrupt level RAM addresses 1 33C 5 D D3FFF 2 2BC 12 D D7FFF 3 23C 15 D DBFFF 4 1FC 3 DC DFFF File name Installing Frontend Software General The communication frontend software comprises (see Figure 34): 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 programs to the communication cards. During operation it forwards ACP messages between the separate communication units and the base systems. 72 ABB Automation

79 1MRS MEN Manual SYS Installing Process Communication System A load program, MFLOAD_E, which loads the DCP-NET communication programs 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 Figure 34: MFL.EXE MFLCONF.DAT MFLOAD_E.EXE MFLOAD_E.SET MFLCONV.EXE NETCONF.EXE NET...84 Executable program file. During operation, MFL.EXE handles the communication between the NET units and the LAN or COM interface. Text file, which specifies the configuration of MFL. See the System Configuration manual, Chapter 4. Executable file for setting up NET unit information and loading the communication programs to the communication units. Setup file, which contains information needed to load the communication programs to the communication units. The file is created by running MFLOAD_E.EXE. Converts old MFLOAD_E.SET files. Executable file for building the preconfigurations of the communication programs. Delivered NET program. During the installation of a NET unit, 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. Figure 34. An illustration of the software of communication frontends ABB Automation 73

80 SYS Installing Process Communication System Manual 1MRS MEN Installing Software on Disk The frontend software is included in the MicroSCADA installation CD. If your frontend computer cannot install from a CD, you can copy the frontend software from the CD to two diskettes as follows: 1 Load the CD into a Windows NT computer. 2 Open the Explorer and the D: disk. 3 Double-click the file NET84_1.bat in the Frontend folder to copy the frontend software to the first diskette. 4 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: 1 Make a folder for the frontend software. For example to make a MFL folder, type: MD \MFL 2 Copy the files from the NET, NETCONF and MFL folders on the CD or from the diskettes into the MFL folder on disk. To copy, type COPY A:\NET\*.* \MFL COPY A:\NETCONF\*.* \MFL COPY A:\MFL\*.* \MFL Configuring Frontends Configuring NET Programs To configure DCP-NET programs: 1 Copy the communication program to another programs. For example you can name the program NETnn.84, where nn represents the node number of the NET communication unit. 2 Write down the names. An example of this is shown in Table 3. 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 Configuration manual. 3 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 also the 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 edited with a text editor. The parameters included in the file are listed and described in the System Configuration manual, section 4.2. The necessary configuration parameter 74 ABB Automation

81 1MRS MEN Manual SYS Installing Process Communication System settings are described in Chapter 8 of the System Configuration manual. Generally, at least the following parameters must be checked and possibly modified: SRC SRCNOD PROT DST1...DST4 NOD1... NOD4 The station address of the frontend The node number of the frontend The LAN protocol used on the frontend - base system communication: DECNET or TCP/IP Station addresses of the base systems connected to the frontend via LAN or the COM port. 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 base systems 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 information necessary for the loading of the communication programs to the cards. To configure the loading of the communication cards and create the MFLOAD_E.SET file as follows: 1 Start the program MFLOAD_E by entering: MFLOAD_E 2 Open the "Configuration" sub-menu. 3 Select "Input files" and enter the file names to be loaded for each DCP-NET card. See Table 3. 4 Select the "Special" sub-menu and confirm the selection by clicking OK. 5 Select the "Auto-opt" sub-menu. 6 Select LOAD & START as automatic function by pressing Enter. 7 Exit the "Auto-opt" sub-menu by pressing the Esc key. 8 Select the "Settings" sub-menu and "Store" function to store the auto-option settings. 9 Return to the main menu by pressing Esc. Now the settings are stored in the file MFLOAD_E.SET. 10 Exit the MFLOAD_E program. ABB Automation 75

82 SYS Installing Process Communication System Manual 1MRS MEN Creating Automatic Start-up To create automatic start-up of the frontend each time the computer is switched on: 1 Configure the loading of the cards as described above. 2 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. 3 Insert the name of the.bat file into the AUTOEXEC.BAT file to execute it Using Communicaton Frontends Start-up and Shutdown If automatic start-up was created, the frontend is started automatically as the power is switched on. To start the LAN frontend manually: 1 Move to the MFL folder. 2 Enter the command: MFL MFL calls MFLOAD_E, which reads the necessary load information from the file MFLOAD_E.SET. 3 To shut down the communication frontend, press Ctrl - C. Base System Communication If the communication frontend is started before the connected base systems, the frontend displays error messages for command transmission tries until the base system starts. This happens because the communication units send diagnostic commands cyclically to all known applications at least until a connection is established. An error message is also displayed at later disturbances in the base system communication. The station addresses of the connected base systems are configured in the MFL configuration file. The MFL program reads the source address of each arriving message. 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 diagnostic counter 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 35. Some additional display functions can be executed with the following commands: 76 ABB Automation

83 1MRS MEN Manual SYS Installing Process Communication System M R Msg routing Starts 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. Restore Restores the initial display and selects time as cyclic update mode. 0 Resets all MFL diagnostic counters. Figure 35. The screen display of the MFL program. If all base systems cannot be shown simultaneously, they can be scrolled with the F1 key. 5.5 Installing NET Connections Overview Below are some suggestions for the installation of connections to the process and to other devices: Twisted cables. Dial-up modem settings. Twisted Cables Figure 36 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 are presented. The modem in the NET end should have the following settings: The modem must not answer to coming calls (ATS0 = 0). ABB Automation 77

84 SYS Installing Process Communication System Manual 1MRS MEN No error correction. XON/XOFF = 0. Regarding the modem settings in the RTU end, refer to the RTU manual. Figure 36. The wiring connection for cables of 9 and 25 wires respectively. The diagram applies to most NET connections, except for one type of printer connections. See Chapter ABB Automation

85 1MRS MEN Manual SYS Installing Workstations 6 Installing Workstations 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 General This description applies to MicroSCADA workstation connected to a local area network. The installation involves the following steps which are detailed below: Preparing the computer by installing and configuring the operating system and the 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. When installing the operating system, note the following: Define a user belonging to the User group. For the user to be able to open a MicroSCADA 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 Exceed The installation procedure below can be regarded as a sample installation. The sample assumes that the Exceed software version is delivered on a CD. For more information about the installation of Exceed, refer to the Exceed manuals. ABB Automation 79

86 SYS Installing Workstations Manual 1MRS MEN To install the Exceed software: 1 Log on as a user having administrator rights. 2 Close all applications. Start the setup.exe installation program located in the \winnt\exceed directory by double-clicking the name in Explorer. 3 A dialog with the title Exceed for Window NT V Setup appears on screen. Read the message. Click OK. In the next dialog, see Figure 37, select the Shared setup type and the Custom method. Click OK. Figure 37. Exceed setup types and methods are chosen in this dialog 4 In the next dialog you are asked for the home directory of Exceed. Accept the suggested home directories by clicking OK. 5 You are then asked to choose the components and fonts to you want to install (Figure 38). Select components to install by clicking. Select the components you want to install. A standard set to choose is: All X-server related Components FTP Host File Editor Inetd, Talk, Gopher Menu Editor Ping RSH REXEC Default File Transfer Protocol In this file you can edit IP-addresses and Aliases Controls which network services your PC responds to when an incoming request is made Allows you to send ICMP-echo request packages to the network Remote copy, Windows-based version of UNIX2 rcp command. Remote copy, Windows-based version of UNIX rexec command. 2 UNIX is a registered trademark of X/Open Company Limited. 80 ABB Automation

87 1MRS MEN Manual SYS Installing Workstations Remote Exec Remote Shell Telnet Traceroute Xsession, Xstart, Wstart 6 Click OK. Windows-based version of UNIX rexec command Windows-based version of UNIX rsh command Eenables you to make Telnet connections to remote host Displays the route a packet take to a host Files needed when you want to create files that can be run from client, or started to a client. Figure 38. This dialog box present the components that you can install 7 Click Fonts. 8 Select the fonts needed (Figure 39). These are: Miscellaneous fonts 75dpi fonts 100dpi fonts ABB Automation 81

88 SYS Installing Workstations Manual 1MRS MEN Figure 39. This dialog box presents the fonts that you can install 9 Click OK. 10 The selection you have made is presented (Figure 40). Click Start to begin the installation. The program is installed. The last step is to create a user profile. 11 If Exceed was installed in the default directory run the setup.exe program located in the \program files\exceed.nt\userins directory. 12 The installation asks if you want to do an installation that enables all users to use Exceed. Click Yes. Figure 40. This dialog box presents the choices you have made 13 A dialog box for choosing the keyboard file is displayed. Select the keyboard file you want to use, for example us.kbf or swedish.kbf and click OK. See Figure ABB Automation

89 1MRS MEN Manual SYS Installing Workstations Figure 41. In this dialog you can choose the keyboard language file 14 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. Would you like to create a the program group Exceed? 15 Click Yes. Would you like to tune the X server for optimal graphics performance now? 16 Click Yes. Wait until graphics are tuned and a message box with a text 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 by MicroSCADA and a program for opening MicroSCADA monitors on the screen. To install the workstation package: 1 Log in as a user with administrator rights. 2 Load the MicroSCADA CD. Start the Explorer and search for the CD drive. The installation 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 the Notification window (see section 3.9) will be connected. 3 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 the base 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. ABB Automation 83

90 SYS Installing Workstations Manual 1MRS MEN 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". Miscellaneous To get the correct function of the Alt keyboard key in the Exceed workstations: 1 Open the Exceed X input settings tool by selecting Start, Program, Exceed, Xconfig and Input. 2 Select the value To X for the Alt key field. In order to allow copying from Windows to X and vice versa, do the following: 1 Open the Exceed X Selection settings window by selecting Start, Programs, Exceed, Xconfig and X Selection. 2 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 update performance can be increased by following settings. 1 Open the Exceed performance settings window by selecting Start, Programs, Exceed, Xconfig and Performance. 2 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: 1 Open the Exceed Window Mode settings window by selecting Start, Programs, Exceed, Xconfig and Window Mode. 2 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 telephone line to connect to a base system. 84 ABB Automation

91 1MRS MEN Manual SYS Installing Workstations This configuration of the workstation requires that the workstation is running the X emulator software (Exceed) and using the Remote Access Service (RAS) provided by 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 42. This computer will act as the server of the connection while the workstation computer will 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 workstation acting 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. The server is configured to accept incoming calls, while the client is configured to make outgoing calls. The installation procedure comprises the following steps, which will be detailed below: 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. (e.g.a basesystem) R e m o t e workstation) Figure 42. Connecting a workstation via a telephone line to MicroSCADA Installing and Configuring Workstation Install and configure the workstation computer as described in section 6.1, excluding the LAN, which is not required. ABB Automation 85

92 SYS Installing Workstations Manual 1MRS MEN Installing Modems To install the modems: 1 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. 2 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 stepby-step description of a RAS installation. Refer also to the Windows NT operating system manuals. 1 Double-click the icon My Computer and Control Panel. From Control panel double-click the Network icon. The Network tool appears. 2 Select the page Services and click the Add. Figure 43. The list of Network services 3 Select Remote Access Service and click OK. 4 Select the installation media, e.g. A:\i386 if diskette. 86 ABB Automation

93 1MRS MEN Manual SYS Installing Workstations Figure 44. Selecting installation media. Here, RAS is installed from a CD connected to the network. File copying starts. When ready, you are asked the following question dialog box shown in Figure 45. Figure 45. Question related to RAS setup 5 Make sure that the modem is connected to the desired COM port, and click Yes. 6 Follow the instructions on the screen, see Figure 46. Figure 46. Installing New Modem ABB Automation 87

94 SYS Installing Workstations Manual 1MRS MEN 7 You can either use automatic modem detection or enter the RAS communication media 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 47 and Figure 48 will be shown. Select type of modem and communication port. Figure 47. Selecting modem manually Figure 48. Selecting communication port manually 88 ABB Automation

95 1MRS MEN Manual SYS Installing Workstations 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 if the modem type is not found. 8 Enter the dialing information, see Figure 49, and click Next. Figure 49. Dialing information Figure 50. Adding RAS devices 9 Click Install Modem. ABB Automation 89

96 SYS Installing Workstations Manual 1MRS MEN Figure 51. Remote Access Setup dialog box 10 Click Configure. Figure 52. Configuring Port Usage 11 Select the option Receive calls only in the server computer and Dial out only in the client computer. Click OK. 12 Click Network (see Figure 51). 90 ABB Automation

97 1MRS MEN Manual SYS Installing Workstations Figure 53. Network Configuration dialog box 13 Select the TCP/IP protocol and click Configure. Figure 54. Entering TCP/IP addresses in the server computer ABB Automation 91

98 SYS Installing Workstations Manual 1MRS MEN 14 Enter the address range of all remote workstations connected to the server. If the server runs under Windows NT Workstation, only one remote workstation is allowed. However, although only one workstation will be used, the address must be given as an address range. In the case in Figure 54, the remote workstation is assigned the IP address Configuring Start-up of RAS in Server Computer To configure automatic start-up of Remote Access Service in the server computer: 1 Double-click the icon My Computer and Control Panel. From Control panel double-click the Services icon. Figure 55. The Windows NT window for managing services 2 Select Remote Access Server and click Startup. Figure 56. Selecting automatic startup 92 ABB Automation

99 1MRS MEN Manual SYS Installing Workstations 3 Select Automatic startup. 4 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 57. This tool contains useful functions for connection diagnostics and help for RAS questions. Figure 57. Remote Access Administration Preparing for Dial-Up from Workstation Computer To prepare a dial-up from the workstation computer to the base system, insert the phone number of the server computer in a phone book as follows: 1 Double-click the icon My Computer. Double-click the icon Dial-Up Networking. 2 Follow the instructions in the windows which appear, see Figure 58 and Figure 59. Figure 58. New phonebook entry wizard dialog box ABB Automation 93

100 SYS Installing Workstations Manual 1MRS MEN Figure 59. Alternatives related to server Figure 60. Adding the phone number By clicking Alternates (Figure 60) you will find features which can be set in the RAS client. MicroSCADA has been tested using the TCP/IP and PPP protocols. 94 ABB Automation

101 1MRS MEN Manual SYS Installing Workstations Figure 61. Editing phonebook entry Dialing-Up During the RAS installation, an icon named Dial-up Network was created on the workstation computer. To establish connection with the server computer, and with 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 the pictures, 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 and lower 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 the MicroSCADA base system package. During the installation, the font files are installed 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 4. The semigraphic fonts and the scalo*.bdf fonts are always required. The abb*.bdf fonts are needed for LIB 500. ABB Automation 95

102 SYS Installing Workstations Manual 1MRS MEN Table 4. The MicroSCADA font files and the sizes of the resulting pictures 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 x x 480 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 system computers and MicroSCADA workstation computers. Compiling Fonts This information concerns the Exceed Xconfig program version Compile the fonts as follows: 1 Start the Xconfig program. 2 Choose Font by double-clicking the icon. 3 Click Compile Fonts in the Font Settings dialog box, see Figure 62. Figure 62. The font settings dialog box 4 Select the directory where the fonts are stored, in this case \sc\fonts\scada_fonts\x see Figure Click Select all. 6 Click Compile. 96 ABB Automation

103 1MRS MEN Manual SYS Installing Workstations Figure 63. The dialog box for compiling fonts 7 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. 8 Next you are asked if you want to add the output font directory to the font database. Click Yes. 9 A dialog box with title Add Font Directory appears. Type the name of the font database file, e.g. scada, in the File Name row. Click OK. 10 You are told that the font directory has been added to the font database. Click OK. 11 Click Close in the Compile Fonts dialog and Close in the Font Settings dialog (Figure 63). 12 Exit the Xconfig program by selecting Exit in the Settings menu. ABB Automation 97

104

105 1MRS MEN Manual SYS Installing Peripherals 7 Installing Peripherals About this Chapter This chapter describes how to install the following peripheral equipment: 7.1 Printers: printers connected directly to base system computers, to the LAN 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 initiated hardcopy. For hard copy, the hard copy functions of exceed or Windows NT can be used without any configuration measures in MicroSCADA. The automatic event and alarm printout on the other hand requires that the printers are known to MicroSCADA. These printers can also be used for MicroSCADA initiated hard copy. The installation descriptions below apply to the printers used by MicroSCADA. Regarding the installation of Windows NT hard copy devices, refer to the Windows NT and the printer manuals. A MicroSCADA printer can be connected as follows: 1 Directly to a base system computer, through the parallel port or a serial port. 2 To a LAN via a printer server. 3 To a DCP-NET. Printers connected to a NET unit can be made accessible to all base systems in the entire 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 printer is defined as shared in the operating system configuration of the computer to which 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 two different principles which determines the appearance of the printout: 1 Semi-graphic picture based printing. 2 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-based ABB Automation 99

106 SYS Installing Peripherals Manual 1MRS MEN black-and-white printout, pixel-based black-and-white printout, and pixel-based colour printout. See the requirements in chapter 2. The picture-based printout produced by printers directly connected to the base system or to LAN are always character based and black-and-white. Pixel-based or colour printout is obtained exclusively on printers connected to the NET lines (provided that the printer supports this type of printout). The SCIL defined may contain any characters, graphics, formatting and colours supported 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: 1 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 3 metres from the base system computer. Serial lines allow the connection lines to be up to 15 metres without modem. 2 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 systems or other Windows NT computers on the LAN. 3 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. 4 Configure the printer in the base system as a PRIn:B object, see the System Configuration manual, section If the printer will be used by several base systems, or by programs other than MicroSCADA on the same or other computers, 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 base systems, 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: 1 Install the printer server on the LAN and install the printers as described in the printer 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 Hewlett Packard 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: 1 Configure the DLC protocol in Windows NT. For this operation the compact disc containing the Windows NT is needed. 2 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 hot stand-by 100 ABB Automation

107 1MRS MEN Manual SYS Installing Peripherals systems, both base systems should be defined as printer managers. The printer port must be configured as Job Based. 3 Define the printer or printers as PRI base system objects in SYS_BASCON.COM. Define the PRI objects as if the printers were directly connected 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: 1 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 64 shows the possible cable wiring for printer connections with different output synchronisation (see the OS attribute for printer lines in the System Objects manual). Figure 64. The cable wiring required for frontend printer connections with the different alternatives for flow control (the OS, Output Synchronisation, attribute). The cable wiring, shown in a figure in Dial-up Modem Settings section of chapter 5, can be used in cases 1 and 3. 2 Select the connection mode on the printer: set the printer in serial mode. 3 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 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. Printers cannot be connected to the PC-NET. ABB Automation 101

108 SYS Installing Peripherals Manual 1MRS MEN 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 65, or a standard PCI card connected to an audio alarm panel, see Figure 66. 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 originating from 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 audio alarm 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 cards contains: 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 watchdog circuitry in the alarm panel. In the ISA card based solution the watchdog circuitry is in 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. 102 ABB Automation

109 1MRS MEN Manual SYS Installing Peripherals Figure 65. The installation of the standard alarm unit for the FPC-046 PC card ABB Automation 103

110 SYS Installing Peripherals Manual 1MRS MEN Figure 66. The installation of the alarm unit for the PCI-7250 and PCI-1760 cards. In the figure there are two standard PCI cards connected to the audio alarm panel, this kind of audio alarm unit installation is used in hot stand-by systems. The installation of the alarm devices comprises the following steps: 1 Mounting and connecting the alarm cards. 2 Installing and configuring the alarm device drivers. 3 Connecting the alarm panels and devices. 104 ABB Automation

111 1MRS MEN Manual SYS Installing Peripherals 4 Configuring MicroSCADA. Installing the Alarm Cards Installing the FPC-046 I/O card and the cable connection card: 1 Mount the alarm card, including the cable connection card, into free ISA expansion slot in the base system computer. The factory setting of the I/O port address, 170H, need not be changed, provided that this address and the next 15 addresses are not used by any other device. You can check this for example with Windows NT Diagnostics tool. 2 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 without opening the computer case. Installing the PCI-1760 and PCI-7250 audio alarm cards: 1 Mount the alarm card used into a free PCI expansion slot in the base system computer. A PCI card selects the necessary I/O port addresses automatically. 2 A cable that comes with the audio alarm unit has a D15 connector in one end and 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 is dry (D). Configuring Alarm Drivers To be able to successfully configure the alarm driver you must belong to the user group Administrators. To configure the standard alarm unit (using FPC-046 I/O card) drivers: 1 If the MS-AA package is not already installed, install the package as described in Chapter 3. 2 Start MicroSCADA Control Panel. 3 Click Admin and then Drivers. 4 Click MS-AA to configure the MiSCAlrm driver. 5 Click Add Device to configure the device for the first time, or click Change Settings to reconfigure it. Figure 67 shows the configuration dialog box for the alarm driver. ABB Automation 105

112 SYS Installing Peripherals Manual 1MRS MEN Figure 67. The configuration of the alarm driver Enter the following configuration data: Device Number: Type of Card: I/O Port Address: The device number. Only one card is supported. It will be device 0. The type of the card. Only one card is supported: FPC-046 PC Industrial I/O Card. The I/O port used by the card. This must be the same as the I/O port address set on the card, see above. Alarm State when MicroSCADA Not Running: The selection of whether to have all the lamps on the alarm panel turned on or off when MicroSCADA service is stopped. Audio_set will be used: This check box must be selected when using the audio_set executable, described in Chapter 10 of the 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 driver installation and configuration see the equivalent card manufacturer documentation. The Windows NT 4.0 drivers for both PCI cards are delivered with the cards. The driver 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, the supported versions of the drivers can be downloaded from the manufacturer WWWsites: ADLink site: Advantech site: If this does not solve your problem, please contact the ABB Substation Automation Oy customer support. 106 ABB Automation

113 1MRS MEN Manual SYS Installing Peripherals Connecting Alarm Panels and Devices Connecting the alarm panel and devices to the standard ISA based alarm unit: 1 Connect the standard MicroSCADA alarm panel as illustrated in Figure Connect possible additional alarm devices to the 25-pin connector. The table in Figure 65 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: 1 Connect the D15 connector of the cable coming from the audio alarm card to either of the audio alarm panel s controller connectors. 2 Connect possible additional alarm devices to the 25-pin relay (Fujitsu RA-5W-K) output connector on the alarm panel. The table in Figure 66 specifies the output pins and corresponding alarm output (alarm class and watchdog). To place texts in the transparent pockets of the free text windows on the audio alarm panel: 1 Open all four screws on the bottom of the box. 2 Open two bolts on the inside of the cover, which hold the electric circuit board. 3 Print or write alarm explanation texts on paper and put them to the pocket between the iron plate and plastic cover as demonstrated in Figure 68. Figure 68. Audio alarm panel s cover plate seen from inside the box MicroSCADA Configuration Set the SYS:BAA attribute to 1 in sys_bascon.com as shown in Figure 69. See also the System Configuration manual, chapter 10. If MicroSCADA is to be configured for either of the PCI cards, then also the SYS:BAD attribute needs to be set as shown in Figure 69. The AA and AD attributes are described in the System Objects manual Chapter 4. ABB Automation 107

114 SYS Installing Peripherals Manual 1MRS MEN Figure 69. The sys_bascon.com file with the different SYS:BAx attribute settings. All that comes on a row after a semicolon ( ; ) is comment text, so the AD attribute setting for the PCI-1760 has been written in the file just as an example. 7.3 Installing Radio Clocks Installing Clock Cards in Base Systems In order to install a radio clock card in a base system computer: 1 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 check this for example with Windows NT Diagnostics tool. 2 Mount the card into a free expansion slot in the computer. 3 Install and configure the radio clock driver as described below. 4 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 the user group Administrators. 1 If the MS-PC3X package is not already installed, install the package as described in section Start MicroSCADA Control Panel. 108 ABB Automation

115 1MRS MEN Manual SYS Installing Peripherals 3 Click Admin and then Drivers. 4 Click MS-PC3X to configure the MiSCPC3x driver. 5 Click Add Device to configure the device for the first time, or click Change Settings to reconfigure it. 6 Enter the following configuration data in the the radio clock driver configuration dialog, see Figure 70. Figure 70. The dialog box for configuring the radio clock driver Device Number Type of Card I/O Port Address The device number. Only one card is supported. It will be device 0. The type of the card. The following card types are supported: PC31, PC32. The I/O port used by the card. This must be the same as the I/O port address set on the card, see above. 7 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: 1 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. 2 Connect the clock to the COM1 port. 3 Configure the MFLCONF.DAT configuration file as described in the System Configuration manual, chapter 10. Installing Clocks Connected to NET Units In order to install a radio clock connected to a NET unit: 1 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. 2 Connect the clock to a free NET line. Configure the DCP-NET of the NET unit as described in the System Configuration manual, Chapter 10. ABB Automation 109