PULSE SCADA/HMI TRAINING GUIDE

PULSE SCADA/HMI TRAINING GUIDE

Copyright The information in this document is subject to change without prior notice and does not represent a commitment on the part of AFCON Control and Automation Ltd., AFCON Software and Electronics Division. No part of this document may be used or reproduced in any manner whatsoever without written permission from AFCON Control and Automation Ltd., AFCON Software and Electronics Division. The software described in this document is furnished under a license agreement or a nondisclosure agreement. The software may be used or copied only in accordance with the terms of the agreement. It is against the law to copy this software on any other medium for any purpose other than the purchaser's personal use. Copyright 2015 AFCON Control and Automation Ltd., AFCON Software and Electronics Division. All rights reserved. Pulse logos are registered trademarks of AFCON Control and Automation Ltd., AFCON Software and Electronics Division. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Pulse Training Guide i

Pulse Training Guide ii

Contents Lesson 1: About Pulse... 1 Lesson 2: Project Management... 23 Lesson 3: Pulse Communication... 43 Lesson 4: Pulse Workstation Management... 63 Lesson 5: Pulse Items... 85 Lesson 6: Graphics... 123 Lesson 7: Animations... 157 Lesson 8: Workflows... 201 Lesson 9: AutoActions... 213 Lesson 10: Cells... 225 Lesson 11: Resources... 237 Lesson 12: Templates... 249 Lesson 13: Instruments... 255 Lesson 14: Pulse Database... 271 Lesson 15: Alarms... 295 Lesson 16: Trends... 331 Lesson 17: Datasheet... 361 Lesson 18: Pulse Data Logger Report... 381 Lesson 19: Schedule Manager... 401 Lesson 20: Security... 415 Pulse Training Guide iii

Pulse Training Guide iv

Lesson 1 About Pulse Pulse Training Guide 1

Introduction to Pulse Pulse is an advanced SCADA/HMI environment for integrating, monitoring and controlling processes in the industrial, building, and security sectors. It incorporates technology such as.net Application Framework and Client/Server architecture to bring increased efficiency, superior visualization capabilities and a highly reliable platform for supervisory control to manufacturing environments and organizations. The Pulse model makes SCADA/HMI simpler, more scalable, and more cost-effective than ever before. Examples of project locations are an industrial factory, a civil defense infrastructure, an office building, a power station, an airport. Pulse employs Client/Server architecture to provide flexibility in deployment and maintenance. There is no need to install entire SCADA systems on every client workstation in the network. The core Pulse programs and project data reside on the Server and can run full time while the operator and developer client workstations log on and off according to their needs and work schedules. This provides important flexibility to companies and organizations deploying Pulse. For example, supervisors may monitor and control the operations over the Internet from almost anywhere and application engineers can work on project development and configuration changes from different facilities. Pulse Training Guide 2

Pulse Server The Pulse Server modules run as Windows services in the background with no need for user interaction. As a default setting, the modules start automatically when the Pulse Server computer starts up or restarts (administrators may change this setting). The services management (automatic start, manual start, stop, disable) is accessible from the remote Server Manager utility in the AFCON Pulse Program Group. The Pulse Server handles communication with the PLCs using P-CIM native drivers and/or OPC servers, and generates alarms according to alarm condition definitions defined in database blocks. It records the alarms into the database and the alarms queue from where the Server Publisher distributes them. The Pulse Kernel collects the database blocks real-time data and stores them in historical data files, according to block time frequency and value change resolution. The Pulse Server can be configured as a standalone server with single or dual communication channels. As a Redundant Hot standby system, the active server synchronizes the data with the passive server. Pulse Training Guide 3

A server can exchange data with other server(s). Servers can be configured as I/O servers with one common database, history, alarms, and displays. Pulse Training Guide 4

Disaster Recovery Control (DRC) The Pulse Disaster Recovery Control (DRC) Station (a feature and a system component), is a system level backup and restore capability. This capability gives the Pulse system an integrated, simplified backup and restore as well as disaster recovery operation (continuity). This feature is beyond the Hot Redundancy capability already available for Pulse servers. DRC adds another Pulse server station with a server and a client in one computer. This solution is designed to assure operation of critical systems at all times. The feature is simple to configure, runs transparently from normal operation and does not require any additional hardware (redundant switches, redundant networks, redundant storage), additional outside applications, or virtualization platforms. It is an economic solution alleviating a critical system availability challenge when disaster strikes. Pulse Training Guide 5

Pulse Client The Pulse client station is the user s (operator and/or developer) interface. The entire project's files remain stored on the Pulse server. The Remote client user logs into the project over an Internet or Intranet connection through a web browser. A client workstation can run from a local/remote computer web browser. A client workstation can also run from a Flash drive connected to one of the computer s USB ports. Multiple client workstations, each connected to a different Pulse server (Master Host), can run on the same computer. On the Pulse Client, the project may be accessed through both a Developer and Operator workstation modes. Pulse Training Guide 6

Developer Workstation After a project is created, the process of designing project components (creating displays, inserting and defining graphic objects, instruments and controls), creating and configuring database blocks, alarms and more, is done in the Developer Workstation. This working mode is named design time (in contrast to run time mode, when the operators work in the Operator Workstation). NOTE Each client that runs the Developer Workstation uses one Development mode license. Pulse Training Guide 7

Operator Workstation The Operator Workstation is the Pulse Client s runtime operational interface. It is the environment in which operators view and interact with objects created in the Developer Workstation, in order to monitor and control actual real-time processes and/or equipment operation to which the objects correspond. Operators can interact by pressing on objects with the mouse pointer, or by typing on the keyboard. Real-time data can be displayed in text objects and counters, by graphic object animation, while Historical Trends can also be shown in graphs. The Operator Workstation ribbon contains the runtime programs and options intended to be used by the operators running the project. The Operator Workstation Personalization is applied to the Workstation environment. Furthermore, operator authorization is defined through the Menu Authorization Settings, which enables and disables menu options. Pulse Training Guide 8

System Requirements Hardware Requirements Pulse Standalone Configuration GHz Core i7 or faster Minimum 8 GB RAM (16 GB recommended) NOTE: The RAM size has to be increased as the database size increases to ensure optimal performance. 320 GB of free hard disk space NOTE: The size of the free hard disk space has to be increased as the size of the database increases to ensure optimal performance. Super VGA 3D display card with a minimum of 512 MB DDR3 memory Keyboard and mouse or compatible pointing device Network adaptor 100/1000 MB USB SEK (supplied with the Pulse package); without the SEK, Pulse runs in Demo mode. Pulse Server 2.4 GHz Xeon Quad Core processor 2.4 or faster Minimum 16 GB RAM (32 GB recommended) NOTE: The RAM size has to be increased as the database size increases to ensure optimal performance. Minimum 150 GB free SAS hard disk space NOTE: The size of the free SAS hard disk space has to be increased as the size of the database increases to ensure optimal performance. Keyboard and mouse or compatible pointing device Network adaptor 100/1000 MB USB (for Virtual Machine: USB over TCP adaptor) SEK (supplied with Pulse package); without the SEK, Pulse runs in Demo mode. Pulse Training Guide 9

Pulse Client 3 GHz i5 or faster (i7 recommended) Minimum 3 GB RAM (4 GB RAM recommended) 60 GB free hard disk space Super VGA 3D display card with a minimum of 512 MB DDR3 memory Keyboard and mouse or compatible pointing device Network adaptor 100/1000 MB Pulse Client Running from a USB Flash Drive 1 GB free disk space USB2 or faster port Pulse Training Guide 10

Software Requirements The table below details the operating systems that you can use to run both Pulse server and client components. * - Installing Pulse Server/Standalone successfully on a 32-Bit operating system depends on the application size. NOTE: Windows 2003 and Windows XP are not supported in Pulse 3.0. Pulse Training Guide 11

Pulse Installation *For details, refer to the Pulse Installation Guide. Pulse Server Group Modules Icon Module Name Description Main AFCON Pulse Group Launch Workstation Pulse Help Opens the Pulse web portal, from where users can access a workstation Opens the Pulse Help utility Restart This module restarts Pulse. Server Manager Shutdown Startup Uninstall Pulse Use this module to manage both local and remote Pulse servers, manage users' accounts, project configuration and more. This module stops Pulse and its running services. This module starts Pulse and the applicable services. Use this module to uninstall Pulse. Administrative Tools Deploy to Flash Drive HASP install HASP remove Registration and License A utility used to download the Pulse application to a USB Flash drive. A utility used to install the HASP protection key driver. A utility used to uninstall the HASP protection key driver. Use this utility to register your copy of Pulse. Pulse Training Guide 12

Development Security Manager Use this program to set and manage the Pulse security policy. Datasheet Manager Email Dispatcher INI File Editor Maintenance Manager Configurator OPC Browser OPC Gateway Editor Progate Editor Redundancy Editor Report Editor SER Editor Supreme Report Studio Use this program to add, edit or remove Datasheet tags from multiple data sources (XML, OLEDB, TEXT, etc.). Use this module to define the message format for automatically sending email messages containing information about alarms according to predefined definitions. Use this utility to edit Windows INI-type files, and to use and manage aliases. This module acts as a follow-up database for the plant s equipment. The OPC Browser is used for bidirectional communications between a Pulse project and an OPC server. It can also be used to check communications and to check an item s value. Use this utility to add, edit, and delete OPC Gateway tags. Use this utility to configure and set up the various Progate settings. This module defines the system s hot backup system, which runs during network and/or computer failures. Use this program to create and edit templates of plain text (TXT) reports and dbase (DBF) files. Use the SER (Sequence of Events Recorder) Editor to record events in Pulse. Run this program to generate Supreme Report on-demand reports. Pulse Training Guide 13

Pulse Setup Communication Network Project Use this program to install, configure and uninstall Pulse communication drivers Use this module to set up and modify network stations. Use the Project Configuration to setup and configure the Pulse projects settings. Runtime Alarm Handler Email Dispatcher Maintenance Manager OPC Gateway This module displays system and alarm messages. It has two windows: Current Alarm and Alarm Summary. Use this module to define the message format for automatically sending email messages containing information about alarms according to predefined definitions. This module acts as a follow-up database for the plant s equipment. This module is an OPC server that receives information about the workplace, and then using OPC protocol, translates it and sends it to the OPC client that sends it to an external device. Tools Audit Trail Backup or Restore Wizard Email Sender This utility displays changes that were made to various modules, as well as actions done by Pulse users. Run this wizard to back up and restore Pulse projects. Use this module to send text messages. Pulse Training Guide 14

the following menus: AFCON Pulse (main menu) Administrative Tools Development Pulse Setup Runtime Tools FTP Utility History Viewer Log Window OPC Browser Project Migration Wizard Supreme Report Generator Use this utility to transfer files between the Pulse web client to Pulse web server. This module displays history files in list format. The History Viewer can also convert history files into.csv format. These files can be opened and modified in Microsoft Excel. Use this utility to view the Pulse log files in the Pulse Logger window. The OPC Browser is used for bidirectional communications between a Pulse project and an OPC server. It can also be used to check communications and to check an item s value. Run this wizard to convert an existing P-CIM 7.70 project into a Pulse project. Run this program to generate Supreme Report on-demand reports. Ser ver side inte racti ve mod ules are acce ssibl e fro m the Win dow s des ktop Sta rt men u via Pulse Training Guide 15

Licensing Pulse system licensing policy is based on the following considerations: 1. Number of concurrent PC Pulse workstations logged in at a single time, distributed according to the following working modes: Maximum number of Development workstations logged in at one time from different computers Maximum number of Monitor & Control Operator workstations logged in at one time from different computers Maximum number of Monitor Operator workstations logged in at one time from different computers Maximum number of Event Management workstations(*) logged in at one time from different computers NOTE (*) A Monitor Operator workstation and a Monitor and Control Operator workstations are considered 'Event Management workstations' when the Event Center window is open. Note that the user cannot open the Event Center window in Development mode. The number of EM licenses can be less or equal to the total number of the Monitor Operator workstation and the Monitor and Control Operator workstations together. For each computer logging into Pulse, a single license is used for each different working mode. Up to three licenses (1 Development, 1 Monitor & Control, and 1 Monitor) may be used at a time on a single computer (counted by a Pulse server). NOTE If a developer user and a monitor user both log in from the same computer, Pulse records 2 licenses used. 2. The I/O count is cumulative and counted by the Pulse kernel. Unadvised items are not subtracted under the license. NOTE An I/O item is an item whose source is a communication driver or an OPC server. I/O items are counted for licensing purposes with the following exceptions: A database block is not an I/O item, but the address it refers to is. Two blocks pointing to the same address are counted as only one I/O item. Same I/O items with different Engineering Units (EGU) Conversion are counted as only one I/O item. Pulse Training Guide 16

Same I/O items with different output formats are counted as only one I/O item. Direct driver addresses and their bit values are counted as only one I/O item. As an exception, if a bit on a register is accessed through an alarm Bit block, it is counted as one separate I/O item. OPC DA Publisher items. NOTE Dollar Variables, configuration items, alarms and other data items not originating in a communication driver or OPC driver, are not counted. Pulse Training Guide 17

Pulse Registration and License Utility The Registration and License Utility is used as follows: To view the current SEK (Security Enabled Key) or Sentinel parameters To save license details to a file To update license parameters To run the Sentinel HASP Remote Update System (RUS) utility The Registration and License Utility supports two types of Security Enabled Keys (SEK): HASP4 and Sentinel. HASP4 - supports Dart, P-CIM, Pulse versions 1.10, 1.20, 1.50, 2.0 and 2.1. The HASP4 can be connected to an LPT or USB port. Sentinel - supports Pulse 1.50 and higher. The Sentinel key can be connected to a USB port only. Pulse Training Guide 18

Pulse supports the Sentinel which has the following license types: Time limited key (has a built-in time counter) Network SEK Software key support Software key support, time limited Software key support, time limited, network key Hardware key support Hardware key support, time limited Hardware key support, time limited, network key *For additional information, refer to the "Pulse Registration & License Guide". Pulse Training Guide 19