infilink hmi

345
Infilink-HMI Software for Windows™ Users Guide Kessler-Ellis Products Phone 800-631-2165 or 732-935-1320 extension 332 Website www.kep.com Licensing website http://infilock.kep.com Email [email protected] © 2004 KEP 99755REV22SEP04 All Rights Reserved

Upload: yaqui007

Post on 16-Apr-2015

206 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Infilink HMI

Infilink-HMI Software for Windows™

Users Guide

Kessler-Ellis ProductsPhone 800-631-2165 or 732-935-1320 extension 332Website www.kep.comLicensing website http://infilock.kep.comEmail [email protected]

© 2004 KEP99755REV22SEP04

All Rights Reserved

Page 2: Infilink HMI
Page 3: Infilink HMI

Infilink License and Warranty

The software accompanying this license agreement (the Software) is the property of KEP, Inc. and is protected bycopyright law. Your rights and obligations in its use are described as follows:

1. You may use and display the Software on a single computer.

2. You may make one copy of the Software for archival purposes.

3. You may copy the Software onto your hard disk and hold the original for archival purposes.

4. You may not make copies of materials that accompany the software, including instruction manuals,promotion materials, and labels.

5. You may not modify or attempt to reverse engineer the software, or make any attempt to change oreven examine the source code of the software.

6. The Software can be unlocked on only a single computer at one time.

7. You may not give or distribute copies of the Software or written materials associated with the Softwareto others.

8. You may not sub-license, sell, or lease the Software to any person or business.

Return PolicyThe original licensee of the Software can return it within thirty (30) days of purchase. Please call us for a ReturnGoods Authorization Number.

WarrantyKEP does not guarantee that the Software will satisfy your application needs, nor that the Software will be errorfree. Though the software is tested thoroughly there may be minor defects that may have been missed. As in allsoftware, not every useable application can be performed due to the complexity of the software itself.

Disclaimer of DamagesEven if the Software does not satisfy the customer’s needs, or is viewed as failing to perform, in no event will KEPbe liable to you for any direct or indirect damages, including lost profits or lost data. KEP’s liability shall neverexceed the purchase price for the Software.

TrademarksMicrosoft® and Microsoft Excel® are registered trademarks, Windows™ is a trademark of Microsoft Corporation.

Users GuideRevision 4.04

(c) 2004 Kessler-Ellis Products, Inc10 Industrial Way EastEatontown, NJ 077241-800-631-2165 (Voice)(732) 935-9344 (FAX)http://[email protected]

Copyright © 2004, KEP, Inc., All rights reserved.

Page 4: Infilink HMI
Page 5: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • i

Table of ContentsINFILINK-HMI SOFTWARE FOR WINDOWS™ ...................................................................................................I

Kessler-Ellis Products..............................................................................................................................i© 2004 KEP.............................................................................................................................................i

TABLE OF CONTENTS ....................................................................................................................................I

INTRODUCTION .......................................................................................................................................... 1

WELCOME .................................................................................................................................................. 1SYSTEM REQUIREMENTS ............................................................................................................................. 1SETTING UP ................................................................................................................................................ 2DIRECTORIES INSTALLED BY THE SETUP PROGRAM ...................................................................................... 2ICONS INSTALLED BY THE SETUP PROGRAM ................................................................................................. 3SETTING UP A SERVER ................................................................................................................................ 3INSTALLING DAO......................................................................................................................................... 4REGISTERING YOUR SOFTWARE .................................................................................................................. 5MOVING A LICENSE ..................................................................................................................................... 6UPGRADING A LICENSE................................................................................................................................ 7

INFILINK 4.06.01 NEW FEATURES............................................................................................................ 9

New Features Table of Contents........................................................................................................... 9UPGRADE COST ........................................................................................................................................ 10EDIT USERS IN RUN MODE ........................................................................................................................ 11IMPORTING WINDOWS FROM ANOTHER PROJECT ....................................................................................... 11RETENTIVE TAGS ...................................................................................................................................... 12ACTIVE UNACKNOWLEDGED ALARMS FLASHING.......................................................................................... 12TELEPHONY SCRIPTING COMMANDS........................................................................................................... 13TEXTTOSPEECH: SPEAKOUT SCRIPTING COMMAND .................................................................................. 15TREND PRINTING....................................................................................................................................... 16ANIMATED GIF OBJECT ............................................................................................................................. 17MAKING BITMAP OBJECTS FULLY / PARTIALLY TRANSPARENT ....................................................................... 18WINDOW PRINTING ................................................................................................................................... 19GRADIENT FILLS AND TRANSPARENCY ....................................................................................................... 20SENDKEYS SCRIPTING COMMAND.............................................................................................................. 22LANGUAGE SWITCHING.............................................................................................................................. 25BACKGROUND IMAGE TO HMI WINDOW....................................................................................................... 27SYSTEM TAGS: _FORMATTEDDATE, _FORMATTEDTIME .............................................................................. 28SCRIPT COMMANDS: _THISWIN.<TREND OBJECT NAME>.PENTAG .............................................................. 28SCRIPT COMMANDS: LOG2, LOG10 ............................................................................................................ 28SCRIPT COMMAND: DATATOFILE ............................................................................................................... 29TREND VIEW INCREASED: .......................................................................................................................... 29DDE SHARE NAME CHANGE...................................................................................................................... 29ROUND SCRIPTING COMMAND ................................................................................................................... 29ONSCREEN FRENCH KEYBOARD ................................................................................................................ 30BUG FIXES ................................................................................................................................................ 30

INFILINK OVERVIEW ................................................................................................................................ 31

DESIGN MODE........................................................................................................................................... 31SHORT CUT MENUS................................................................................................................................... 32THE INFILINK DOCKABLE TOOLBARS........................................................................................................... 34

Window Tools.......................................................................................................................................... 34DESIGN MODE KEYBOARD MAPPING .......................................................................................................... 36

Function Keys...................................................................................................................................... 36Alphanumeric Keys.............................................................................................................................. 36Numeric Keypad .................................................................................................................................. 36Arrow Keys .......................................................................................................................................... 36Other Keys........................................................................................................................................... 36

DESIGN MODE MOUSE FUNCTIONS ............................................................................................................ 36Buttons ................................................................................................................................................ 36

Page 6: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • ii

Combinations....................................................................................................................................... 37RUN MODE ............................................................................................................................................... 37

LESSON 1: LEARNING TO USE INFILINK .............................................................................................. 38

OVERVIEW ................................................................................................................................................ 38LESSON OBJECTIVES................................................................................................................................. 39CREATING A PROJECT ............................................................................................................................... 40THE IMPORTANCE OF OBJECT PROPERTIES................................................................................................ 43

About Object Properties ...................................................................................................................... 43The Object Name ................................................................................................................................ 43

A CHANCE TO PRACTICE ........................................................................................................................... 44Draw and Place a Rounded Rectangle. .............................................................................................. 44Draw and Place a Text Object............................................................................................................. 46Draw and Place a Triangle .................................................................................................................. 49Grouping the Objects........................................................................................................................... 51

SAVE THE PROJECT AND EXIT .................................................................................................................... 54

TAG GROUPS AND TAGS ........................................................................................................................ 56

OVERVIEW ................................................................................................................................................ 56ABOUT TAG GROUPS................................................................................................................................. 56ADDING/EDITING TAG GROUPS .................................................................................................................. 57

Creating Tag Groups ........................................................................................................................... 57Creating a Memory Tag Group............................................................................................................ 58Creating a DDE Tag Group ................................................................................................................. 58Creating an OPC Tag Group ............................................................................................................... 61Creating a Virtual Tag Group............................................................................................................... 62

ABOUT TAGS............................................................................................................................................. 63Predefined System Tags ..................................................................................................................... 63

ADDING/EDITING USER DEFINED TAGS....................................................................................................... 65Tag Edit Tools ..................................................................................................................................... 65Creating a Memory Tag....................................................................................................................... 65Creating a DDE Tag ............................................................................................................................ 67Creating an OPC Tag .......................................................................................................................... 68Creating a Virtual Tag.......................................................................................................................... 69Tag Edit Advanced Tab ....................................................................................................................... 70

Deadband........................................................................................................................................ 70Value clamps / Scaling.................................................................................................................... 70

Tag Edit Scripts Tab ............................................................................................................................ 71Scripts Tab ...................................................................................................................................... 71

Tag Edit Discrete, Level and Deviation Alarm Tabs ............................................................................ 71Alarm Tabs ...................................................................................................................................... 71

EXPORTING THE TAG DATABASE ................................................................................................................ 71Tag Database Field Definitions ........................................................................................................... 72

IMPORTING THE TAG DATABASE................................................................................................................. 75

ANIMATIONS: YOUR PROCESS IN ACTION .......................................................................................... 77

OVERVIEW ................................................................................................................................................ 77ABOUT ANIMATIONS .................................................................................................................................. 77ANIMATING AN OBJECT .............................................................................................................................. 78

Making an Object Blink ........................................................................................................................ 78Showing and Hiding Objects ............................................................................................................... 79Moving Objects Left and Right (Horizontally) or Up and Down (Vertically) ......................................... 80Stretching Objects Left and Right (Horizontally) or Up and Down (Vertically)..................................... 81Rotating a Line..................................................................................................................................... 82Enter Data Into a Tag .......................................................................................................................... 84Using Sliders to Input Data.................................................................................................................. 85Changing the Color of an Object ......................................................................................................... 86Showing the Value of a Tag................................................................................................................. 88Executing a Script With a Button Click ................................................................................................ 89

LIBRARIES: THE QUICK PATH TO GREAT LOOKING APPS ............................................................... 91

Page 7: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • iii

OVERVIEW ................................................................................................................................................ 91LIBRARY MANAGER TOOLS......................................................................................................................... 91

Create a New Library........................................................................................................................... 92Create a New Object Group ................................................................................................................ 92Open a library ...................................................................................................................................... 92Save a library....................................................................................................................................... 93The Library Manager Treebar.............................................................................................................. 93

SAVING OBJECTS TO A LIBRARY................................................................................................................. 94Placing an Object or Group from a Library .......................................................................................... 94Reassigning Tags................................................................................................................................ 95

SCRIPTS: THE FINAL WORD IN FLEXIBILITY ....................................................................................... 97

OVERVIEW ................................................................................................................................................ 97INTRODUCTION .......................................................................................................................................... 98PROJECT SCRIPT ...................................................................................................................................... 99WINDOW SCRIPTS................................................................................................................................... 100TAKE ACTION SCRIPTS ............................................................................................................................ 102TAG DATA CHANGE SCRIPTS ................................................................................................................... 103ALARM SCRIPTS ...................................................................................................................................... 104SCRIPT REFERENCE ................................................................................................................................ 106

General.............................................................................................................................................. 106Comments ......................................................................................................................................... 106Logical Constants .............................................................................................................................. 106Conditional Operators........................................................................................................................ 107Logical Operators .............................................................................................................................. 107Assignment Operator......................................................................................................................... 108

Virtual Tag assignment ......................................................................................................................... 108Arithmetic Operators.......................................................................................................................... 109Flow Control ...................................................................................................................................... 110Math Functions .................................................................................................................................. 111String Functions................................................................................................................................. 112File Functions .................................................................................................................................... 113Sound Functions................................................................................................................................ 118Window Functions ............................................................................................................................. 118System Functions .............................................................................................................................. 119Miscellaneous Functions ................................................................................................................... 120Color Constants................................................................................................................................. 121Object Properties............................................................................................................................... 122

General Object Properties............................................................................................................................. 122Arc, Pie and Chord Properties ...................................................................................................................... 123Rounded Rectangle Properties ..................................................................................................................... 123Alarm Viewer Properties................................................................................................................................ 123Alarm History Viewer Properties ................................................................................................................... 124Trend Properties ........................................................................................................................................... 124

LESSON 2: USING INFILINK TO MIMIC A PROCESS........................................................................... 127

OVERVIEW .............................................................................................................................................. 127LESSON OBJECTIVES............................................................................................................................... 128CREATING A PROJECT ............................................................................................................................. 129COPYING LIBRARY OBJECTS .................................................................................................................... 130

Place a Pump from the Library .......................................................................................................... 130EDIT/ARRANGE THE OBJECTS IN THE WINDOW ......................................................................................... 134

Rotate, Enlarge, and Place the Tank................................................................................................. 134Copy, Size, and Place a Section of Horizontal Pipe .......................................................................... 135Resize and Place the Pump .............................................................................................................. 136Place and Resize the Horizontal Pipe ............................................................................................... 137Copy, Place and Size a Section of Vertical Pipe ............................................................................... 138Place and Resize the Control Valve .................................................................................................. 139Place and Resize the Vertical Pipe.................................................................................................... 140Add a Fill Meter to the Tank............................................................................................................... 141

DEFINE A TAG TO ASSIGN TO THE FILL LEVEL ANIMATION.......................................................................... 144ANIMATE THE OBJECT T1_LEVEL ............................................................................................................. 145

Page 8: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • iv

CREATE A SCRIPT TO SIMULATE AN INCREASING FILL LEVEL ..................................................................... 147SAVE THE PROJECT................................................................................................................................. 149RUN THE PROJECT .................................................................................................................................. 149EXIT RUN MODE...................................................................................................................................... 149

LESSON 3: CONTROLLING A PROCESS ............................................................................................. 151

OVERVIEW .............................................................................................................................................. 151LESSON 3 OBJECTIVES............................................................................................................................ 152CONTINUING FROM LESSON 2 .................................................................................................................. 152

Opening Lesson 2 ............................................................................................................................. 152ADDING SOME NEW TAGS ....................................................................................................................... 153

Adding Tags ...................................................................................................................................... 153ADD AND ANIMATE THE NEW OBJECTS ..................................................................................................... 156

Add a Button to Turn the Pump On and Off ...................................................................................... 156Add a Text Object to Enter and Display the Pump Fill Rate.............................................................. 161Build a Slider to Control the Tank Drain Rate.................................................................................... 163Duplicate the Slider Text Object and Modify It to Display the Tank Level ......................................... 166Duplicate the Pump Control Button and Modify to use as a Valve Control ....................................... 167Modify the Existing Project Script ...................................................................................................... 168

SAVE AND RUN THE PROJECT .................................................................................................................. 170

LOGGING: DATA AND ALARMS ........................................................................................................... 173

OVERVIEW .............................................................................................................................................. 173THE ALARM LOGGER ............................................................................................................................... 174

Basic Settings.................................................................................................................................... 175Log File Timings ................................................................................................................................ 175Preferences ....................................................................................................................................... 176

DEFINING ALARMS................................................................................................................................... 177ALARM VIEWER PROPERTIES ................................................................................................................... 180ALARM HISTORY VIEWER PROPERTIES..................................................................................................... 183SETUP ALARM PRINTER ........................................................................................................................... 185

Send Output To ................................................................................................................................. 185Sample Format .................................................................................................................................. 185

THE DATA LOGGER ................................................................................................................................. 186Basic Settings.................................................................................................................................... 187Log File Timings ................................................................................................................................ 187Preferences ....................................................................................................................................... 188

LESSON 4: ALARMS AND ALARM LOGGING...................................................................................... 189

OVERVIEW .............................................................................................................................................. 189LESSON OBJECTIVES............................................................................................................................... 190CREATING A NEW PROJECT ..................................................................................................................... 191DRAWING THE ALARM VIEWER................................................................................................................. 191CREATING ALARM VIEWER CONTROL BUTTONS ........................................................................................ 192DRAWING THE ALARM HISTORY VIEWER................................................................................................... 193CREATING ALARM HISTORY VIEWER CONTROL BUTTONS.......................................................................... 194ENABLING THE ALARM LOGGER................................................................................................................ 195DEFINING TAGS WITH ALARMS ................................................................................................................. 196CREATING ANIMATIONS TO GENERATE ALARMS ........................................................................................ 200DISPLAYING THE ACTIVE ALARM COUNT ................................................................................................... 201SAVE AND RUN THE PROJECT .................................................................................................................. 202EXIT RUN MODE...................................................................................................................................... 204

LESSON 5: REAL-TIME AND HISTORICAL TRENDS........................................................................... 205

OVERVIEW .............................................................................................................................................. 205LESSON OBJECTIVES............................................................................................................................... 206CREATING A NEW PROJECT ..................................................................................................................... 207DEFINING TAGS....................................................................................................................................... 207DRAWING THE TREND AND EDITING TREND PROPERTIES .......................................................................... 208CREATING TREND CONTROL BUTTONS..................................................................................................... 210CREATE AND ANIMATE A HISTORICAL CURSOR ......................................................................................... 211

Page 9: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • v

ANIMATING TREND CONTROL BUTTONS.................................................................................................... 213Create an On button down Script for the Mode Button...................................................................... 213Create an On button down Script for the YRangeInc Button............................................................. 214Create an On button down Script for the YRangeDec Button ........................................................... 214Create an On button down Script for the Smooth Button .................................................................. 214Create an On button down Script for the Discrete Button ................................................................. 215Create an On button down Script for the Scatter Button ................................................................... 215Create an On button down Script for the SkipInc Button................................................................... 215Create an On button down Script for the SkipDec Button ................................................................. 215

CREATE A CURRENT VALUE DISPLAY ....................................................................................................... 216WRITING A PROJECT SCRIPT ................................................................................................................... 217SAVE AND RUN THE PROJECT .................................................................................................................. 218EXIT RUN MODE...................................................................................................................................... 220

ACTIVEX CONTROLS ............................................................................................................................. 221

OVERVIEW .............................................................................................................................................. 221INSERTING ACTIVEX CONTROLS INTO A PROJECT ..................................................................................... 222

SCHEDULER............................................................................................................................................ 223

OVERVIEW .............................................................................................................................................. 223INTRODUCTION ........................................................................................................................................ 224

Using the Calendar Tool........................................................................................................................ 224HOLIDAYS ............................................................................................................................................... 225ACTION GROUPS ..................................................................................................................................... 226

Creating an Action Group...................................................................................................................... 226EVENTS .................................................................................................................................................. 230

Creating a Single Event......................................................................................................................... 230Creating a Double Event ....................................................................................................................... 231Creating a Weekly Schedule................................................................................................................. 232

PREFERENCES ........................................................................................................................................ 234

USING OPC AND DDE ............................................................................................................................ 235

OVERVIEW .............................................................................................................................................. 235ABOUT OPC (OLE FOR PROCESS CONTROL) AND DDE (DYNAMIC DATA EXCHANGE)............................... 235

OPC Link Specifications .................................................................................................................... 235DDE Link Specifications .................................................................................................................... 235

INFILINK AS A DDE CLIENT ...................................................................................................................... 237Supported DDE Formats ................................................................................................................... 237Using Infilink as a Local Client.......................................................................................................... 237Using Infilink as a Remote Client....................................................................................................... 237

INFILINK AS A DDE SERVER..................................................................................................................... 238A Note About Discrete Tags .............................................................................................................. 238Using Infilink as a Local Server ......................................................................................................... 238

MS EXCEL AS A DDE SERVER................................................................................................................. 239Tag Group setup................................................................................................................................ 239Tag Addresses .................................................................................................................................. 239

SECURITY................................................................................................................................................ 240

OVERVIEW .............................................................................................................................................. 240DESIGN MODE SECURITY......................................................................................................................... 240RUN MODE SECURITY ............................................................................................................................. 242

Logging in to a Project....................................................................................................................... 242Logging Out as a User....................................................................................................................... 242Adding/Editing a User List ................................................................................................................. 243User List Tools................................................................................................................................... 244

Creating a New User ..................................................................................................................... 244

IVIEWER UTILITY.................................................................................................................................... 245

OVERVIEW .............................................................................................................................................. 245CONNECTING TO A REMOTE PC................................................................................................................ 246

Getting Started .................................................................................................................................. 246

Page 10: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • vi

Connecting ........................................................................................................................................ 246Disconnect......................................................................................................................................... 246iViewer Setup..................................................................................................................................... 248iViewer Setup Dialog ......................................................................................................................... 248Adding/Editing a Server ..................................................................................................................... 249Screen Shots ..................................................................................................................................... 249iViewer Tag Display........................................................................................................................... 250Modifying the Tag list display............................................................................................................. 251iViewer Status Bar ............................................................................................................................. 251

AUTOMATICALLY RUNNING A PROJECT............................................................................................ 252

OVERVIEW .............................................................................................................................................. 252WINDOWS 95/98..................................................................................................................................... 253

Making Infilink Auto Start in Win 95/98.............................................................................................. 253Making KEPServerEX Auto Start in Win 95/98 ................................................................................. 255

WINDOWS NT......................................................................................................................................... 257Making Infilink Auto Start in Win NT .................................................................................................. 257Making KEPServer Auto Start in Win NT .......................................................................................... 259

APPENDIX A: LIBRARY OBJECTS ............................................................................................................ 1

LIBRARY FILE: 2D_ISA_1 ............................................................................................................................ 1LIBRARY FILE: 2D_ISA_2 ............................................................................................................................ 2LIBRARY FILE: 2D_ISA_3 ............................................................................................................................ 3LIBRARY FILE: 3D_ISA_1 ............................................................................................................................ 4LIBRARY FILE: 3D_ISA_2 ............................................................................................................................ 5LIBRARY FILE: 3D_ISA_3 ............................................................................................................................ 6LIBRARY FILE: AIRCOND1.......................................................................................................................... 7LIBRARY FILE: AIRCOND2.......................................................................................................................... 8LIBRARY FILE: AIRCOND3.......................................................................................................................... 9LIBRARY FILE: ALARMHST ....................................................................................................................... 10LIBRARY FILE: ARROWS .......................................................................................................................... 11LIBRARY FILE: BITMAPS1......................................................................................................................... 12LIBRARY FILE: BITMAPS2......................................................................................................................... 13LIBRARY FILE: BITMAPS3......................................................................................................................... 14LIBRARY FILE: BUTTONS1 ....................................................................................................................... 15LIBRARY FILE: BUTTONS2 ....................................................................................................................... 16LIBRARY FILE: BUTTONS3 ....................................................................................................................... 17LIBRARY FILE: BUTTONS4 ....................................................................................................................... 18LIBRARY FILE: BUTTONS5 ....................................................................................................................... 19LIBRARY FILE: BUTTONS6 ....................................................................................................................... 20LIBRARY FILE: COMPUTER ...................................................................................................................... 21LIBRARY FILE: CONTROLR ...................................................................................................................... 22LIBRARY FILE: DATADISP......................................................................................................................... 23LIBRARY FILE: DIALS1 .............................................................................................................................. 24LIBRARY FILE: DIALS2 .............................................................................................................................. 25LIBRARY FILE: DUCTS .............................................................................................................................. 26LIBRARY FILE: ELECTRC1........................................................................................................................ 27LIBRARY FILE: ELECTRC2........................................................................................................................ 28LIBRARY FILE: FACILITY........................................................................................................................... 29LIBRARY FILE: FLEXTUBE ........................................................................................................................ 30LIBRARY FILE: FLOWMTRS...................................................................................................................... 31LIBRARY FILE: GENERMFG...................................................................................................................... 32LIBRARY FILE: HEATING1......................................................................................................................... 33LIBRARY FILE: HEATING2......................................................................................................................... 34LIBRARY FILE: INDICATR.......................................................................................................................... 35LIBRARY FILE: INTLSYMS......................................................................................................................... 36LIBRARY FILE: MAPSFLAG ....................................................................................................................... 37LIBRARY FILE: MATHANDL....................................................................................................................... 38LIBRARY FILE: METERS1.......................................................................................................................... 39LIBRARY FILE: METERS2.......................................................................................................................... 40LIBRARY FILE: METERS3.......................................................................................................................... 41LIBRARY FILE: METERS4.......................................................................................................................... 42LIBRARY FILE: MISCSYM1 ........................................................................................................................ 43LIBRARY FILE: MISCSYM2 ........................................................................................................................ 44LIBRARY FILE: MISCSYM3 ........................................................................................................................ 45LIBRARY FILE: MISCSYM4 ........................................................................................................................ 46

Page 11: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • vii

LIBRARY FILE: MIXERS............................................................................................................................. 47LIBRARY FILE: MOTORS........................................................................................................................... 48LIBRARY FILE: NATURE............................................................................................................................ 49LIBRARY FILE: OP_INTFC......................................................................................................................... 50LIBRARY FILE: PIPES1.............................................................................................................................. 51LIBRARY FILE: PIPES2.............................................................................................................................. 52LIBRARY FILE: PIPES3.............................................................................................................................. 53LIBRARY FILE: POWER............................................................................................................................. 54LIBRARY FILE: PROCESS......................................................................................................................... 55LIBRARY FILE: PUMPS.............................................................................................................................. 56LIBRARY FILE: SAFETY............................................................................................................................. 57LIBRARY FILE: SENSORS......................................................................................................................... 58LIBRARY FILE: SHAPES1.......................................................................................................................... 59LIBRARY FILE: SHAPES2.......................................................................................................................... 60LIBRARY FILE: SLIDERS1 ......................................................................................................................... 61LIBRARY FILE: SLIDERS2 ......................................................................................................................... 62LIBRARY FILE: SLIDERS3 ......................................................................................................................... 63LIBRARY FILE: SLIDERS4 ......................................................................................................................... 64LIBRARY FILE: SYSCMDS......................................................................................................................... 65LIBRARY FILE: TANKCUTS ....................................................................................................................... 66LIBRARY FILE: TANKS1............................................................................................................................. 67LIBRARY FILE: TANKS2............................................................................................................................. 68LIBRARY FILE: TIMEDATE......................................................................................................................... 69LIBRARY FILE: TRENDHST ....................................................................................................................... 70LIBRARY FILE: VALVES............................................................................................................................. 71LIBRARY FILE: VEHICLES......................................................................................................................... 72

TTEECCHHNNIICCAALL SSUUPPPPOORRTT ............................................................................................................................ 1

Kessler-Ellis Products............................................................................................................................ 1

Page 12: Infilink HMI
Page 13: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • 1

Introduction

WelcomeWelcome to Infilink HMI, an easy-to-use tool for any size HMI application. InfilinkHMI provides you with the tools to design and implement a custom interface forany process. Infilink offers interface solutions for PLCs, transmitters, sensors,remote I/O, and other process devices.Infilink HMI runs on Windows 98, NT 4.0, 2000, and XP.This chapter shows you how to set up Infilink HMI on your computer andintroduces the documentation set.

System RequirementsTo run Infilink HMI, you must have certain hardware and software installed on yourcomputer. The minimum system requirements include the following:• An IBM PC or compatible with a 233MHz Pentium microprocessor.• 32MB of RAM.• 30MB of free hard disk space.• At least one free serial port with a 16550 UART if you will be communicating

with serial devices.• VGA card and color monitor capable of at least 800x600-pixel resolution using

16 colors.

The recommended system configuration is the following:• An IBM PC or compatible with a 233 MHz Intel Pentium microprocessor.• 128MB of RAM• 100MB of free hard disk space• Accelerator enabled PCI Super VGA card and color monitor capable of at least

1024 x 768 pixel resolution using 256 colors.• Microsoft Windows XP.

Page 14: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • 2

Setting UpIf you have a previous version of Infilink installed on the target computer you shouldperform a backup of all project files created using that version in the event that youdecide to return to that version in the future.

The program SETUP.EXE on disk #1 (or CD) performs the installation, installing theInfilink HMI executable files, license file, help file, and other components. If you area Windows NT user you will need to ask your system administrator to perform theSetup.

1. Place the CD into the drive and the setup program should autorun. If not, thenbrowse the CD and run it by double-clicking it.

2. Choose the components you wish to install.

3. Click the Browse… button to choose a destination directory.

4. Choose a Program Folder/Program Group for the icons that invoke theexecutable files and help.

5. Verify your choices. If you want to make a change click on the < Back button.

6. At this point, the file copy process begins. You will be prompted for disks asneeded.

7. Upon completion of the file copy process, you will be given the opportunity toview the README.TXT file. This file contains release information specific to thisversion of Infilink HMI. You can find this file in the Infilink program directory ifyou want to read it later.

Directories Installed by the Setup ProgramYou specify the target directory for installation during the setup process. By default,this directory is called INFILINK. The Setup program creates additional directoriesfor the components that have been installed.

• \LESSONS contains one subdirectory for each lesson supplied with thesoftware. The lessons are covered later in this manual.

• \LIBRARY contains object library files for use with the Design Mode program.

• \IVIEWER contains the iViewer Internet utility

• \PROJECTS contains the INFILINKDEMO project designed to illustrate InfilinkHMI’s functionality.

• \UTILITIES contains utilites such as the data conversion utility, printscreen, andothers.

Page 15: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • 3

Icons Installed by the Setup ProgramInfilink Design ModeDesign tool for creating and editing an Infilink project.

Infilink Run ModeRuns a compiled Infilink project.

iViewer Internet UtilityApplet that allows the user to view Infilink data over the Internet

Help FolderOn-line information accessible from Design Mode by pressing the F1 key.

Event Log ViewerThe event log viewer captures and displays status output generated by run modecomponents.

ReadmeREADME.TXT includes the following major topics:

1) System Requirements2) New features for V4.03) INFILINK Demo Description

Setting up a ServerServers are used to get DDE data from applications or externally linked devicesthrough drivers. Infilink uses a Server to get data from external applications via OPCor DDE.

If you will be using a third party Server with Infilink, you can install it now or wait untilyou have developed your application and are ready to run it on the PC.KEPware’s OPC Server, KEPServerEX, comes with Infilink. You will be able tounlock one driver for use with Infilink.

Page 16: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • 4

Installing DAOIf you will be logging data in MDB format your PC will need DAO support. If you haveMicrosoft Access installed on your PC there is no need to install DAO support.

If you do not have Microsoft Access installed on your PC you will need to install thefiles needed to support Data Access Objects (DAO). You can select to install DAOsupport during Infilink installation by selecting the Full Installation option or selectingthe Custom Installation option and then selecting it as one of the components fromthe install list. There are 2 files included in the \DAO folder of the Infilink CD.

1. Run the Mdac_typ.exe utility to install support for OBDC and DAO on your PC.2. Additionally, run Dcom98.exe if your PC is running Windows95 or 98.

You can also download the latest versions of these files from the Universal DataAccess Web site at www.microsoft.com/data/. Select the proper downloadversions for your operating system.

Page 17: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • 5

Registering Your SoftwareUnlike other HMI products on the market, Infilink does not require a hardware lock.Furthermore, the design portion of the package can be run anywhere, anytime, withan unlimited tag count, for as long as you want, However, the run time portion of thepackage must be registered.

While a project is in the Run Mode use the Help menu, Purchase a license... menuto see this dialog...

Send an E-Mail that includes the KEP Sales Order number and a request to unlockthe software to [email protected]. Instructions will be included in the reply toreceive a Internet Unlock Password. Use it to access the Serial number and unlockcodes over the internet at www.kep.com’s unlock page. A serial number unlocks theRun Mode for 10 days. Once a Serial number is obtained the Help|Unlock menuitem is enabled.

Note: You have up to 10 days from the time you entered the serial number in whichto unlock the software. If the software is not unlocked within that time, it will ceaseto operate

Use your Internet Unlock Password to access the unlock webpage again and enterthe Computer ID. A Password that unlocks Infilink will be generated.

Note: The software unlock password is dependent on the number of user tags. 128,256, 512, 1024 and Unlimited tag unlock passwords are available.

Enter the password in the Password field and click OK.

Once a PC is unlocked no further codes are needed for unlimited and continuousoperation time. The password you receive is only valid for a single PC. If you want tomove the software to another PC you will have to obtain another password for thatPC.

Page 18: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • 6

Moving a License

Accept a License.../Move a License...This menu item is used to move the license from on PC to another. Once the Movea License procedure is finished, the PC where the license originated will be locked inDemo Mode and the PC that received the license will be unlocked for unlimited timeuse. A blank floppy diskette is needed for this process. Infilink must also be installedon the PC that will accept the license (target computer).

@ Use a formatted floppy disk. The disk must not have any files on it when startingstep 1.

1. Insert blank floppy disk into target computer. Initiate license activation fromtarget computer by clicking on Help|Accept a License, select a floppy drive, clickStep 1, this prepares the floppy disk. Remove the floppy disk. @ Do NOT turn off the target computer or exit Infilink 2. Insert the floppy disk from Step 1 into the licensed computer. Continue byselecting Help|Move a License menu and selecting the floppy drive. Click Step 2,this causes the Infilink to exit Run Mode. Remove the floppy disk. 3. Insert the floppy disk into the target computer. Click Step 3, this takes the licensefrom the floppy disk and puts it into the target computer. Notes: DO NOT EXIT TARGET PCs INFILINK OR LICENSE MENU AFTER THISPROCESS IS STARTED, OR THE LICENSE WILL BE LOST. Set the User Access Level required to perform license transfers by going toProject|Properties, Users tab and making the appropriate entries. If you want tomove the software to another PC, you can use the transfer a license procedure. Thisprocedure will erase the license from the source PC and install it on the target PC.

Page 19: Infilink HMI

Copyright © 2004 KEP, Inc. Introduction • 7

Upgrading a LicenseThe Upgrade License feature is provided for users that wish to upgrade a License toa higher tag count or add Internet access with the iViewer utility.

Send your request via e-mail with the Serial Number and Computer ID [email protected]. A new Serial Number and Password that will unlock the RunMode for the higher tag count will be e-mailed back to you. Alternately, you can Faxthe information to KEP. Enter the serial number and password in the appropriatefields and click OK.

@ Use the Copy numbers to clipboard button then paste it into your e-mail requestto insure accurate data.

Page 20: Infilink HMI
Page 21: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 9

Infilink 4.06.01 New Features

This document is to provide a description of features new to version 4.06.01; these are all thefeatures added since version 4.02.02.

Document updated 16-September-2004

New Features Table of Contents

Upgrade Cost 10Edit Users in Run Mode 11Importing Windows from Another Project 11Retentive Tags 12Active Unacknowledged Alarms Flashing 12Telephony Scripting Commands 13TextToSpeech: SpeakOut Scripting Command 15Trend Printing 16Animated GIF Object 17Making bitmap objects fully / partially transparent 18Window Printing 19Gradient Fills and Transparency 20SendKeys Scripting Command 22Language Switching 25Background image to HMI window 27System tags: _FormattedDate, _FormattedTime 28Script commands: _ThisWin.<Trend object name>.PenTag 28Script commands: Log2, Log10 28Script Command: DataToFile 29Trend View Increased: 29DDE Share Name Change 29Round Scripting Command 29OnScreen French Keyboard 30Bug Fixes 30

Page 22: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 10

Upgrade Cost

KEP is not increasing prices for these new features, and it is a free upgrade from Infilinkversion 4.00.20 and later to version 4.06.01.

Some of the new features require KEPRUN-0000 (unlimited tag version). Current users, andnew purchasers, of KEPRUN-0000 have these features at no additional cost.

Text-To-SpeechTelephonyIviewer (5 license)

If you have one of the lower tag versions now, and want to upgrade, the upgrade price isreasonable. Basically, it is the price difference plus $50. Contact KEP, your manufacturer’srepresentative, or your distributor for details.

The other new features are available in all tag counts of Infilink.

Page 23: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 11

Edit Users in Run Mode

In the "user properties" dialog a check box was added, "Allow runmode editing of user table".

Editing of user table in runmode can be done in two ways:1. Menu item "Users - Edit users".2. Script command _Syscmd.EditUsers.

Menu item "Users - Edit users" will be enabled only when there is a logged in user has thepermission to edit user table at runmode.

User table edited at runtime is saved as file “ProjectUsers.dat” in the project directory. This fileis encrypted.

Runmode uses the table from “ProjectUsers.dat” and overrides the DesignMode table.

Runmode on exit creates the file “ProjectUsers.dat”. Runmode edited user table can beimported into design mode by importing the file “ProjectUsers.dat” by clicking the button“Import run mode user table” on “User list” tab of “Project properties”.

“ProjectUsers.dat” file is project specific. The file generated for one project will not beaccessible to another project. This is done to prevent somebody from copying the file,creating another project and then getting user names and passwords.

In some cases it is possible that the Infilink design mode work is done in some office and runmode runs at different location. User table edited in runmode can be “Imported” by copyingthe file “ProjectUsers.dat” to computer running design mode. The file should be copied in theproject directory. The file can be imported by clicking button “Import run mode user table” on“User list” tab of “Project properties”. As “ProjectUsers.dat” is tied to a specific project,importing it can be done only for that project.

Importing Windows from Another Project

Using design mode menu item “Window – Import” it is now possible to import HMI windowmade in another project. All the contents of source window (shapes along with theiranimations, trend / alarm objects, Window background picture if defined, animated GIF files ifpresent, window scripts) are imported. Any tag names present in the imported window if notfound in the project tag table will generate errors while compiling project.

Import window functionality is upward compatible for different Infilink versions.

Page 24: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 12

Retentive Tags

While defining memory tags, check the check box “Retentive” to make it retentive.

Value of that memory tag at project close will be stored and will be assigned to that memorytag on next execution of the project, overriding its initial value setting.

Values of retentive tags are stored in file “ProjectRetentiveTags.dat” in project directory. Thisfile is encrypted and is tied to a particular project.

While getting the tag values from the file “ProjectRetentiveTags.dat” Infilink uses “Groupname”, “Tag name” and its data type to identify a particular tag.

Changing the data type of Tag1 (from Word to Long for example) causes the retentive value tobe lost.

Error messages are posted to Eventlogger in the following cases:• Retentive tags are defined in a project but “ProjectRetentiveTags.dat” is not found.• “ProjectRetentiveTags.dat” is copied into project directory from different project.• “ProjectRetentiveTags.dat” is corrupt.• Runmode is unable to save file “ProjectRetentiveTags.dat” on project exit.

Active Unacknowledged Alarms Flashing

There is now a setting in the Alarm Viewer properties. Active Unacknowledged Alarms can bemade to flash between two different colors, and the colors are selectable.

This provides more prominent notification of alarms.

Page 25: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 13

Telephony Scripting Commands

Script command DescriptionPh_MakeCall Make outgoing call.Ph_DropCall Drop current callPh_EnableIncoming Enable incoming callsPh_DisableIncoming Disable incoming callsPh_TTSString Say a string over phone using text to speechPh_TTSFile Say contents of file over phone using text to

speechPh_PlayWaveFile Play a wave file over phonePh_StopVoiceOut Stop playing of wave file or text to speechPh_EnableDTMF Enable sensing of digits pressed over remote

phonePh_DisableDTMF Disable sensing of digits pressed over remote

phone

Syntax of all of above script commands is like: Ph_MakeCall(“G1”);Each command expects a string expression / string constant in the parenthesis. This string isused to identify the memory tag group which is to be associated with that command.

Using a tag group name as a parameter to a command allows the user to work with multiplephone lines.

Tags used with above telephony commands.

Tag name Datatype

Usage

LineName string Specifying line / phone device namePhoneNumber string Specifying phone number to callCallStatus long Call status codeCallStatusString string Call status stringIncomingRings long Number rings after which incoming call should

be answeredVoiceOut string String to use for Ph_TTSString / Ph_TTSFile or

file name to use for Ph_PlayWaveFileVoiceOutStatus long Code which gives the status of text to speech

output or playing of wave fileLastDTMFReceived long Last digit received from remote touch tone

phoneErrorCode long Error code indicating last error.ErrorString string String informing about ErrorCodeCallerID string Caller ID received for incoming callTimer1, Timer2,Timer3

long Generic timers, automatically incremented byInfilink at every second. Setting –1 to these tagsstops incrementing operation.

Page 26: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 14

IncomingEnabled Discrete

Whether incoming calls are enabled or not.

Call status codes.Code Description1 Call state Idle2 Call state Offering (Incoming call)4 Call state Accepted (Incoming call)8 Call state Dialtone16 Call state Dialing32 Call state Ringback64 Call state Busy128 Call state Special Info256 Call state Connected512 Call state Proceeding1024 Call state On Hold2048 Call state Conferenced4096 Call state On Hold Pending Conference8192 Call state On Hold Pending Transfer16384 Call state Disconnected32768 Call state Unknown

Voice out status codes.-1 Voice status undefined100 Wave file playing in progress101 Wave file playing completed.102 Text to speech in progress103 Text to speech completed

Defaults : For each telephone device Infilink assumes the following defaults: Incoming callsdisabled, DTMF input enabled.

Page 27: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 15

TextToSpeech: SpeakOut Scripting CommandSpeakOut (TextToSpeech, Repetition);

TextToSpeech: This is a string enclosed in quotation marks, or a string tag.Repetition: This is the number of times that TextToSpeech is repeated. This is a number, ora numeric tag.

Example:SpeakOut (MemGrp\SayIt,1);This takes the text in the tag “SayIt”, and sends it one time out the PC’s speakers.

Script command syntax:SpeakOut (string expression, nRepeatCount);SpeakOut (string tag, nRepeatCount);SpeakOut (string literal, nRepeatCount);

The string is spoken using the installed TTS engine. TTS engine is configured through controlpanel for settings like speed, voice type etc.

NRepeatCount has a valid range between 1 and 10 (inclusive). Attempt to program numberoutside this range results in clamping it to valid range.

Attempt to issue more SpeakOut commands before finishing the previous one results inqueuing of the SpeakOut commands.

StopSpeaking;

Stop speaking / TTS. This command terminates any speaking going on and also empties allthe queue if built.

SpeakOut and StopSpeaking commands operate independent of telephony commands. It ispossible to have two different text to speech sessions, both over telephone line and overcomputer speakers.

Page 28: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 16

Trend Printing

Brief notes about trend printing.• Trend printing is done by using script command "_ThisWin.Trend.TrendPrint".• Default printer is used for printing.• This command prints real time and historical trends, whatever is seen on the screen as

a "Trend Object" is printed on the printer.• Any drawing objects appearing above or below the trend objects are not included in

print.• Works for both "Portrait" and "Landscape" modes.• For historical trends, the inactive period black rectangles shown on the screen are

printed with black cross-hatched brush. This improves appearance and reduces ink ortoner usage.

• While printing the trend object, proper scaling is automatically done to fit the trend onthe paper in both "Portrait" and "Landscape" modes.

• A printer typically offers more resolution (total # of horizontal and vertical dots) than aPC screen. It is likely that more detailed plot is obtained on the printed trend than isseen on the screen. Infilink plots the trend utilizing the higher resolution available onthe printer. In the unlikely event that the printer resolution is less than the height andwidth of the trend, Infilink will not print the trend and it will post an error message in theevent logger stating this.

• Using print spooling (instead of choosing "Print directly to printer") is best; otherwiseInfilink program execution will slow while printing.

Page 29: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 17

Animated GIF Object

• Select “Animated GIF” drawing tool, or select menu item “Draw-Animated GIF”.• Draw a rectangle on the window.• Animated GIF properties dialog appears.• Select the Animated GIF file for this object.• Check the check box “Animate in design mode” if you want to see the animation in design

mode. Run mode will always animate the object, design mode gives you the choice.• Click OK, you should see the animated picture.• This object can be resized, moved, duplicated (etc.) just like other Infilink objects.• If the object is being animated and if a zoom level other than 100 % is chosen, animation

stops. Coming back to 100 % zoom should restore animation if it was on.

If the selected file does not contain valid Animated GIF (or mis-typing of file name) then youshould see following bitmap indicating the failure to load the file.

Following animations are allowed for this object.1. Show / Hide2. Take Action3. Enter Data

Animated GIF objects when being animated is always displayed on top of all other objects(irrespective of their Z level).

Page 30: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 18

Making bitmap objects fully / partially transparent

• Create the bitmap object as usual.• Go to “Bitmap properties” dialog, “Bitmap mask” tab.• Select the bitmap file to be used as mask. This file has to be of type bmp (bitmap), it can

not be in other image formats like JPEG, TIFF etc. (As opposed to basic bitmap objectwhich allows most of the image formats to be used)

• Clicking OK shows the bitmap with transparent portions as defined in Mask bitmap.• Mask bitmap is automatically stretched / shrunk in memory to the size of base bitmap

before applying the mask.• For all the “White” pixels (RGB values 255, 255, 255) found in mask bitmap, corresponding

pixels in base bitmap are made transparent.

Used “Animated GIF” and “Mask bitmap” files are copied into project sub-directories“AnimatedGIFs” and “BitmapMasks”.

“Ragged Tank Cut-Out” has been a typical request which could not be done until this featurewas added to Infilink:

Page 31: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 19

Window Printing

In design mode user can print the HMI window by using menu item “Window – Print…” or byright clicking on empty portion of HMI window and selecting “Print…”.

The window is printed to the default printer.

User is able to print three lines of footer information. Infilink before printing presents defaultprint lines and allows the user to edit them.

In run mode user prints the HMI window by using script command“Print Window <Window Name>”

The <Window Name> must be a string literal. Only the visible window is printed to the defaultprinter.

Page 32: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 20

Gradient Fills and Transparency

This applies to following shapes:Polygon, Rectangle, Rounded Rectangle, Ellipse, Pie, Chord, Button, Live and History AlarmViewers, Trend.

Gradient filling of these objects is done by selecting the Shape Properties dialog and choosingthe Interior tab. Previous method of filling objects is retained as “Normal fills”. New “Gradientfills” style is introduced. Checking this radio control results in gradient fill. Colors / gradientpattern / transparency / gamma correction is configured by clicking “Configure Gradient fills…”button.

Focus X and Focus Y edit boxes accept numbers between 0 – 99, both inclusive. Thesenumbers specify percentage of center color portion in X and Y directions.

Using Gamma Correction option has also some specific effect on gradient.

Alpha level (transparency) of 0 – 255 (both inclusive) can be assigned to each color. 255being least transparent, 0 means most transparent.

All the objects except Trends show proper transparency. Trends ignore alpha values.

Line styles like dashed, dash dot for objects filled with “Normal fills” and having line thicknessgreater than single pixel were resulting in a solid line. This is unchanged. But now with fillstyle “Gradient fills” selected, proper line style is available for all line thickness values.

Blink and Color fill animations do not work if object is Gradient filled.

Page 33: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 21

Here is an example of a bitmap with a rectangle on top of it. The rectangle has gradient fillsand alpha (transparency) properties:

This is the setup:

Page 34: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 22

SendKeys Scripting Command

SendKeys(strWinCaption, strKeyStrokes, nFlags);Send keystrokes to other top level windows.

Parameter Data Format MeaningstrWinCaption Tag with datatype string,

String expression,String Literal

SendKeys command sends thekey strokes to the window(s)having this caption on the samecomputer as Infilink

strKeyStrokes Tag with datatype string,String expression,String literal

String holding characters /keystrokes to be sent to targetwindow(s).

nFlags Tag with datatype otherthan string or discrete.Relational expressionresulting in number,Number literal.

Indicates how strWinCaptionshould be used to find targetwindow.

Examples:SendKeys (“Notepad”, “helloworld<enter>”, 0);SendKeys (strTag1, strTag2, longTag3);SendKeys (strTag1 + strTag2, strTag3 + strTag4, lTag5 – lTag6);

Page 35: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 23

Which keystrokes can be sent:Generally all characters found on US English keyboard are sent as keystrokes to targetwindow. To send the keystrokes like: “Enter” use syntax <enter>. Following table lists thekeystrokes which can be sent in this way.Keystroke Required string to be

entered, non casesensitive

Numpad 0 <Numpad0>Numpad 1 <Numpad1>Numpad 2 <Numpad2>….. …..Numpad 9 <Numpad9>“Shift” press <Shift_Down>“Shift” release <Shift_Up>“Control” press <Ctrl_Down>“Control” release <Ctrl_Up>“Alt” press <Alt_Down>“Alt” release <Alt_Up>Back space <Back>Tab <Tab>Escape <Escape>Home <Home>End <End>Left Arrow <Left>Right Arrow <Right>Up Arrow <Up>Down Arrow <Down>Enter <Enter>Insert <Insert>Delete <Delete>F1 <F1>F2 <F2>……….F24 <F24>

Examples:1. String “John <home>F <home>Kennedy ” results in the following string when sent to

Notepad application, “Kennedy F John”2. String “ABC <left><left> DEFGHI ” results in the following string when sent to Notepad

application, “A DEFGHI BC “

Page 36: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 24

Explanation of nFlags:Two attributes of window caption matching can be controlled:1 Attempt matching given caption string exactly or non exactly with the target windowcaption.2 Attempt matching given caption string to target window caption with case sensitivity of not.Value of nFlag Attempt Exact

matchCase sensitivematching

0 No No1 Yes No2 No Yes3 Yes Yes4 or any other value No No

Keystrokes are sent to all the top level windows with matching caption. It is possible to sendthe keystrokes to single or multiple windows simultaneously.Examples of nFlags usage.Sending keystrokes to notepad window with caption “Untitled – Notepad”Value of strCaption Value of nFlags Will keystrokes be sent

to notepad ?“notepad” 0 Yes“Notepad” 2 No“untitled – notepad” 1 Yes“Untitled – Notepad” 1 Yes“ntitled – Notepad” 1 No“Untitled – Notepad” 3 Yes“ntitled – Notepad” 3 No

Page 37: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 25

Language Switching

General Concept:

Assume that the user is looking for creating runtime displays in "English" and "Spanish". (more thantwo languages are supported).

Infilink design mode allows the user to create a string table. It is basically a table with "n" rows andtwo columns since we are assuming two languages in this example. Row1 contains two strings, 1."High Temp in English", 2. "High Temp in Spanish". Similarly other rows contains two stringseach with same meaning.

Currently "Text object" contains a string. With this feature, user is able to assign a row number fromstring table to the text object. Script command "SelectLanguage (<Language Name>)" is available tothe user.

Let us assume that user creates 10 text objects on a HMI window. At start of run mode these 10 textobjects displays text from string table column 1. User executes script command "SelectLanguage(Spanish)" on a button press. After executing this script command Infilink replaces text of all 10 textobjects by picking up strings from the Spanish column.

The display which was in English is now in Spanish.

Following Infilink objects will assume similar behaviour as of "Text object" because of languageswitching feature.

1. Button (text displayed on button), 2. Alarm comments. 3. HMI Window caption..

Design mode offers a string table editor. User is able to set required number of columns (Languages)and go on adding / editing rows.

Details:

User can create user interfaces (HMI windows) in such a way that in run mode the userinterface is shown in any one of the configured languages.

User creates a string table in design mode using menu item “Tools – String table…”, a dialogbox similar to following will appear.

Multilanguage strings can be import/exported to/from a CSV file. This allows most of theediting to be done within a spreadsheet.

Page 38: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 26

User can create many strings in multiple languages. Each string has a string identifier (StringID). Duplicate String IDs are trapped by Infilink.

Text object, button object, Window Caption and Alarm comment can be assigned a string IDinstead of a string. While assigning string ID, character ‘#’ should be put as initial characterbefore actual string ID.To assign a string ID of IDS_GREETING to a text object, #IDS_GREETING should be enteredas text.Infilink upon seeing first character as “#” will treat that string as string ID. At run time stringassociated with that string ID for currently selected language are assigned to the text object.

The script command “SelectLanguage <Language Name>” should be used to select currentlanguage. <Language Name> is expected to be a string expression. Passing an empty stringto SelectLanguage command causes “Default Language” to be selected.The other languages are selected by passing the actual language name, which is the same asthe column heading for that language. The string IDs and language names are not case-sensitive.

Page 39: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 27

Background image to HMI window

An image in standard image format (BMP, JPEG, GIF, PNG) can be assigned as abackground to HMI window.While setting window properties in following dialog box, background image is selected.

The image can be used in semi transparent form by assigning “Image alpha value” less than255. For semi transparent images the background color of the window is seen through theimage. Assigning value of 255 to “Image alpha value” will make the image completely opaqueand at that setting background color will not be seen.

Page 40: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 28

System tags: _FormattedDate, _FormattedTime

These string tags will contain formatted “System Date” and “System Time”. The format is setin the windows control panel. These tags are typically used with show value animation for textobject, to show nicely formatted time and date.

Script commands: _ThisWin.<Trend object name>.PenTag

_ThisWin.<Trend object name>.PenTag = <string expression> is used to assign a tag to atrend pen. <String expression> is used to get the tag name to be used with pen.

The pen with index set by _ThisWin.Trend.CurrentPen is affected by this command.

Example:_ThisWin.Trend.CurrentPen = 3 ;_ThisWin.Trend.PenTag = “LiquidTemp” ;

PenTag command does nothing in the following cases.1. CurrentPen index is greater than the number of pens used for the trend.2. Attempt to assign a tag name which is already used for any pen for that trend.3. Invalid or non existing tag name.4. Tag name expressed without group name and tag name not unique across tag groups.

Event logger will show error messages to inform about these error conditions.

Assigning a tag to real time trend will cause that pen to start plotting from beginning. Datalogging is enabled for the tag if required when executing PenTag command.

History data for any tag which was not being logged before executing PenTag command willnot be available for the time before executing PenTag command. Hence that data can not beseen in history plot. However data for time after logging enabled is available and is seen onhistory plot.

Assignment of a tag name to a trend pen is retained only while the parent window is open.

Script commands: Log2, Log10

Log2(<Numerical expression>) will cause log to the base of 2 to be calculated.Log10(<Numerical expression>) will cause log to the base of 10 to be calculated.

Result 0 is assumed for input numbers of 0 and less than 0.

Page 41: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 29

Script Command: DataToFile

_ThisWin.<Trend object name>.DataFileName_ThisWin.<Trend object name>.DataToFile

User can save the data plotted on History or Real time trend by using script command_ThisWin.<Trend object name>.DataToFile.

Data for time period trend start to trend end (time corresponding to trend left edge to rightedge) for all the trend pen tags is stored onto disk file.

The file name set by _ThisWin.<Trend object name>.DataFileName is used to store the data.If the file name is not set (i.e. DataFileName property of trend is an empty string) beforeexecuting DataToFile command then Infilink will generate a file name using system time andstore the file in “Project directory\DataLog”.

Example:_ThisWin.Trend.DataFileName = “c:\InfilinkTrendData\May13.dat” ;_ThisWin.Trend.DataToFile ;

The name set by DataFileName command is retained while the window is open. The samefile name is used in subsequent executions of the DataToFile command. User is expected tochange the file name before executing DataToFile command if overwriting of previous file isnot expected.

Trend View Increased:Now max time span 1440 hrs, Max pens 12.

DDE Share Name ChangeInfilink while acting as NetDDE server was registering “INFILINK HMI” as DDE share name, itis now registering “INFILINK” as DDE share name.

Round Scripting CommandTag1 = Round (Expression resulting in number);Tag1 = Round (Tag1);Tag1 = Round (Number literal);

Tag5 = Round (5.45) + Round (Tag1);

Page 42: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink 4.06.01 New Features • 30

OnScreen French Keyboard

Onscreen French keyboard added. English or French keyboard can be invoked for data entryanimation. Setting is made through project properties dialog in design mode.

Bug FixesFlat lines were being displayed on trends if System Time changed; this is now fixed.

If HMI windows were created with width and height equal to screen resolution then scrolling torightmost and bottommost portions of those windows was not possible; fixed.

Infilink is now able to respond to iViewer information requests from computers runningWindowsXP.

Page 43: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink Overview • 31

Infilink Overview

Design ModeInfilink Design Mode is used to create a project that will execute in Infilink RunMode. A project is a collection of objects that graphically depicts a process oroperation. A valid project contains at least one window to display the output forthe project. Output is generated by drawing one or more objects in the windowand then assigning animations to those objects. Animations are driven by datathat is stored in internal memory locations called tags.

In addition to object animations, Infilink provides a scripting language tomanipulate project components and tag data. Scripts may be assigned at theproject level, window level and object level. A script may also be assigned toexecute when the value of a tag changes or reaches an Alarm condition.

Tags can reference data from external devices such as PLCs, user definedmemory variables, or other Windows applications through DDE. Tags areassigned to external devices using a node identifier or alias for each device. Thisalias identifies the device driver and protocol used to communicate with the deviceand its network ID.

The steps involved in creating a Infilink project are as follows:

1. Identify the hardware that will be accessed and draw up a map to identifyeach device. This step will help you determine which DDE or OPC serverapplication you need to provide device data. It will also simplify theprocess of identifying these devices to Infilink.

2. Launch Infilink Design Mode and click cancel on the Open Project dialogthat automatically pops up. Use the New... item on the File menu tocreate an empty Infilink project. A default window will be displayed beforemoving on.

3. Open the Window Properties dialog box to choose the options that youwish to apply to the window at run time.

4. Use the Tag Groups item on the Project menu to setup OPC and DDE taggroups referring to the device map created in step 1. (If you don't havethe appropriate device driver yet you may skip this step for now andassign the tags you will define in the next step to a memory group.)

5. Use the Tag Groups item on the Project menu to assign tags to thegroups entered in step 4. This step maps device locations that will bemonitored with assigned tags in Infilink that will be referred to whendefining scripts and animations.

Page 44: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink Overview • 32

6. Use the drawing tools to create objects on the project window.

7. Use the Animations... item on the Edit menu to assign animations to thecreated objects.

8. Use the Scheduler Utility to program timing for events to occur on a realtime basis.

9. Save the project.

Short Cut MenusWhen using the Design Mode application to create a project you will find thatInfilink makes it easy to select the most common commands that may be appliedto an object or window. When you select an object or window with the right mousebutton, you will be presented with a small pop-up menu called a Short Cut Menu.The menu's content changes based on the object or area clicked. Here are someof the functions that are available from the Short Cut menus:

Short Cuts on Objects

For objects, short cut menu functions provide quick access to common activitiessuch as Cut, Copy, Duplicate, and Delete. The short cut menus also provide theeasiest means of accessing an object's properties and animations. Depending onthe object selected additional functions such as Reshape, Font, and Reassigntags may be available.

Page 45: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink Overview • 33

Short Cuts on Windows

The short cut menu functions for a window allow you to quickly turn the Gridfeature on and off. You can also quickly Save the selected window or Close italtogether. The Last Drawing Tool selection allows you to easily draw multipleobjects of the same type without having to reselect the drawing tool from thetoolbox.

Short Cuts on Tag Groups and Tags

All of the tag management tools are included in the shortcut menus. The only wayaccess Tag Import and Export commands is through the short cut menu.

Page 46: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink Overview • 34

The Infilink Dockable ToolbarsThe Infilink Toolbars provide convenient access to the most commonly useddesign tools. Each of the buttons on the Toolbars has a pop-up identifier called atool tip to tell you what function it performs. Pausing the mouse cursor over aToolbar button causes the tool tip to appear. The Toolbars can be dragged to anyscreen location or “docked” along the edge of the design mode window.

Project Tools

- Save project

- Open project

- Run Project

- Tag Groups

- Project Properties

- Library Manager

- Event Viewer

Window Tools

- New - Duplicate

- Open - Properties

- Close - Color

- Save - Grid On/Off

- Delete

Drawing Tools

- Select objects - Draw chord

- Draw line - Draw text

- Draw polyline - Draw button

- Draw polygon - Import bitmap

- Draw rectangle - Import metafile

- Draw rounded rectangle - Draw alarm viewer

- Draw ellipse/circle - Draw alarm history viewer

- Draw arc - Draw trend view

- Draw pie

Line Tools Fill Tools

Page 47: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink Overview • 35

- Line Color - Solid

- Select single line - Dash

- Select double line - Dot

- Select triple line - Dash dot

- Select thick line - Dash dot dot

- None

- Fill Color

- Unfilled - Solid Fill

- Horizontal Hatch

- Vertical Hatch

- Cross Hatch

- Downward Diagonal Hatch

- Upward Diagonal Hatch

- Diagonal Cross Hatch

Text Tools

- Bold text

- Italic text

- Underline text

- Select font

- Increment font size

- Decrement font size

- Text Color

Layout Tools

- Move Forward one level

- Move Back one level

- Rotate Clockwise

- Rotate Counter Clockwise

- Flip Horizontal

- Flip Vertical

Editing Tools

- Undo - Make Group

- Cut - Break Group

- Copy - Remove from Group

- Paste - Shape Properties

- Duplicate - Reassign Tag

- Delete - Reshape

*To create a group, use the selector tool, , to lassothe objects you wish to group.

Alignment Tools

- Align Left - Align Right

- Align Top - Align Bottom

- Center Vertical

- Center Horizontal

- Space Equally Horizontal

- Space Equally Vertical

- Make same Width

- Make same Height

Page 48: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink Overview • 36

Design Mode Keyboard MappingFunction Keys

F4 Displays the Properties dialog box for the selected object.F5 Displays the Animations dialog box for the selected object.F6 Displays the Tag Database dialog box.F7 Saves the current project.F8 Closes the current project.F9 Runs the current project.

Alphanumeric KeysCTL-X Cuts the selected object to the clipboard.CTL-V Pastes an object from the clipboard into the active window.CTL-C Copies the selected object to the clipboard.CTL-D Duplicates the selected object.CTL-Z Undoes the most recent edit. Up to 32 operations can be undone.

Numeric Keypad+ Brings the selected object forward in the z-order.- Sends the selected object backward in the z-order.

Arrow KeysLeft Moves the selected object to the left by one grid line (or one pixel if the

grid is not enabled).Right Moves the selected object to the right by one grid line (or one pixel if

the grid is not enabled).Up Moves the selected object up by one grid line (or one pixel if the grid is

not enabled).Down Moves the selected object down by one grid line (or one pixel if the

grid is not enabled).

Other KeysTab Moves the selection to the next object on the window as determined

by the z-order.Shift-Tab Moves the selection to the previous object on the window as

determined by the z-order.Esc Ends reshape mode or interactive animation definition.Del Deletes the selected object.

Design Mode Mouse FunctionsButtonsLeft Click Object/window selection.Right Click Context sensitive short cut menu.Double Click Ends reshape mode or interactive animation definition.

Page 49: Infilink HMI

Copyright © 2004 KEP, Inc. Infilink Overview • 37

CombinationsShift-Drag Defines a square boundary rectangle when drawing an object.

Defines a diagonal line when drawing a line.

Ctrl-Drag Defines a vertical or horizontal line when drawing a line.

Ctrl-Click Adds/Deletes a node when reshaping a polyline or polygon.

Ctrl-Shift-Double Click Opens grouped objects for editing without breakingapart the group.

Run ModeThe Run Mode application executes an Infilink project created in Design Mode.Run mode consists of six basic components: run time animator, database server,data logger, alarm logger, OPC/DDE server and event logger.

Run Time AnimatorThis is the main window that you see when you start Run Mode. The run timeanimator handles any operator interaction with a running Infilink project.

Database ServerThis is the data management component of Infilink Run Mode. You may see itreferred to as the "Data Manager". It handles the exchange of data between therun time animator and the device drivers. It is also responsible for managing activeOPC and DDE links, updating the scheduler, animator and data logger when apiece of data changes, and notifying the animator of alarm conditions.

Data LoggerThe data logger processes data changes and records information about the changeto a log file.

Alarm LoggerThe alarm logger processes alarm notifications from the database server andrecords the alarms to a log file.

OPC/DDE ServerA server provides the interface between Infilink and a specific piece of hardware.Each server knows only how to communicate with a specific device or set ofdevices. You will need to choose the appropriate server for your application andinstall this component separately.

If Infilink does not provide a native driver for the device that you will be using, youcan use any third party OPC or Advanced DDE server in place of the device driver.KEPware's OPC Server application, KEPServerEX, has been provided for you onthe Infilink CD. Please refer to the documentation provided with KEPServerEX todetermine if an appropriate device driver is available for your application.

Event Log ViewerThe event log viewer captures and displays status output generated by the otherrun mode components. Each status message is time stamped and displayed in theEvent Logger window. The contents of this window may then be printed or saved toa text file for later review.

Page 50: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 38

Lesson 1: Learning to Use Infilink

OverviewIf you need help, thecompleted lessons maybe found in the Infilink\lessons directory.

These lessons areprovided to give you areference of what aproject should look likewhen completed.

Thank you for making Infilink your choice in HMI Software. Infilink has beendesigned to allow you, the user, to get maximum performance with a minimalamount of effort.

This lesson and the lessons that follow are designed to guide you through theprocess of creating an Infilink project. The lessons will get more complex as theyprogress. Some lessons, like this one, are designed to teach you about the partsof Infilink. At any time you may jump forward to another lesson or skip lessonsentirely.

Page 51: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 39

Lesson ObjectivesThis lesson is designed to give you a basic understanding of how to navigatewithin Infilink. When completed you should be able to:

• Create a new project.• Add/Draw objects in a project window using the Toolbars or Main

Menu.• Edit objects using the Main Menu, Short Cut Menus, or Toolbars.• Save a Project

If you feel that you know how to navigate in Infilink, please feel free to go toLesson 2.

This is what your projectwill look like at the end ofthe lesson.

Page 52: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 40

Creating a Project1. Open the Infilink Design Mode application.

2. Click Cancel in the Open Project dialog box

Show at startup, whenthis box is checked theOpen Project window willautomatically come upwhen Infilink Design isstarted.

3. Click the File menu and select New ...

Page 53: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 41

4. The New Project dialog box will open. Type a name in the Create Directoryfield as a project name, we suggest using “Lesson1”. Click Create to acceptthe settings and create the project.

5. When the system asks you to verify the name and path of your project, clickYes if it is correct. If not, click No and repeat 3.

6. The design Mode will start with a default window created. Open the WindowProperties dialog box by clicking on Properties… in the Window menu. Leave“Win001” for a window Name and type “Drawing and Editing” for a Title.

Page 54: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 42

Win001 is thesystem generatedobject Name forthe first window ina project. You canchange this nameat any time.Generally we willgive a name to awindow thatindicates its usei.e." Main" or"Pump_room1".

The Title text willappear in the titlebar of the projectwindow.

Show when projectstarts in run mode,when checked,makes the windowopen wheneverthe project isopened in runmode.

7. Click on Show when project starts in run mode, then click OK to create the window.

8. A grid is available to assist in the layout and alignment of objects in thewindow. If it is not activated, click on the Layout menu and select Enable grid or

click the button on the Window Toolbar. When objects are drawn orresized, they will “snap” to the points on the grid.

9. To make document images clearer we have chosen the color of our window to

be white. If you wish to change your window color, click the button on theWindow Toolbar and select the desired color from the displayed palette.

Page 55: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 43

The Importance of Object Properties

Unnamed objects will bereferred to as "unnamed"on the status bar, and incompile error messages.

An Infilink project will notrun if it contains errors.

About Object Properties

Every object has properties that can be modified both at design and run time. Thedifferences in dialog boxes for each object are too numerous to explain in onelesson. You can investigate these differences on your own when you havelearned how to create each of the objects and modify their properties.

Properties common to every object are name, size and position. Generally you willuse the mouse to change an object’s size or position. You must however use anobject’s property dialog to change its name.

The Object Name

When creating objects it is very important that you consider giving a unique nameto any object that will be animated. You might have ten to twenty objects groupedtogether to simulate a panel and have one object that is animated. Naming thatobject will allow you to immediately know when you have selected that object byseeing its name appear in the status bar.

To reference the properties of an object at run time using a script, you must beable to specify that object by name.

When you save a project if there are errors in scripts or animations, messages willappear in the event logger. These messages will indicate objects by name andindicate what kind of error has occurred.

Page 56: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 44

A Chance to PracticeYou will now take the opportunity to add some objects to our project and learn howto manipulate them. Feel free to deviate from the lesson, its goal is to help youfeel comfortable using Infilink

If you make a mistakewhen drawing an object,you can choose Undofrom the Edit menu orselect the object andpress the DEL key toremove it.

Draw and Place a Rounded Rectangle.First, you will place a Rounded Rectangle in the upper left corner of our projectwindow.

1. Click the button on the Toolbar.

2. Place the pencil cursor in the upper left corner of the project window.

3. Holding the left mouse button down, drag the cursor down and to the rightcreating a box. Release the mouse button when done.

4. While the object is still selected press the right mouse button and click

Properties... from the popup.

Page 57: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 45

5. Type “Round_rect” in the Name field of the Properties dialog box.

Notice the name of theobject changed from“Unnamed” to“Round_rect” on thestatus bar.

6. The Geometry tab allows you to change the shape of the corners. Changingboth numbers to 0 will make the rounded rectangle a perfect square.Changing those numbers to 100 will make it a perfect circle. As you will see,these attributes can also be changed visually by invoking a special modecalled Reshape.

7. Click OK to exit the dialog.

Page 58: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 46

8. While the object is still selected, press the right mouse button and clickReshape from the short cut menu.

9. Move the cursor over the reshape dot until it becomes a hand.

10. Holding down the left mouse button, move the dot around and see how itsdifferent locations effect the corners of the rectangle.

11. When you are through, drag the reshape dot to the center of the bottom line

and release the left mouse button as shown below

Draw and Place a Text ObjectYou are now going to draw a text object in the approximate center of the projectwindow.

1. Click the button on the Edit Toolbar.

2. Place the pencil cursor below the rectangle in the center of the projectwindow.

3. Holding the left mouse button down, drag the cursor down and to the rightcreating a box. Release the mouse button when done.

Page 59: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 47

4. While the object is still selected press the right mouse button and select the

Properties... item from the short cut menu.

5. Select the Text tab and type the following text in the Text field: “Text can beuseful”.

Page 60: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 48

6. Click on the General Tab and type “My_text” in the Name field.

Notice the name of theobject changed from“none” to “My_text”onthe status bar.

7. Click OK to accept the changes and exit the dialog.

8. If the text is too close to the rectangle or is not close enough to the center,

place the cursor over the text until it becomes a hand.

9. Holding the left mouse button down, drag the text object so that it is centeredin the project window.

Page 61: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 49

Draw and Place a TriangleYou are now going to draw a polygon in the shape of a triangle in the lower rightcorner of the project window.

1. Click the button on the Toolbar.

2. Place the pencil cursor below the text object in the lower right portion of theproject window.

3. Click the left mouse button to set the first corner of your triangle. Drag thecursor to the next point and release. Move the cursor to the last position anddouble click to finish creating the triangle.

4. While the object is still selected, use the short cut menu as you did above todisplay the properties dialog or press F4 to do the same thing.

Page 62: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 50

5. Assign the name “Triangle” to the object and click OK.

See the help file forinformation on how toreshape a polygon.

6. Change the fill color of the triangle to bright green by clicking the , solid fill

and the , fill color tools on the Fill Toolbar.

Page 63: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 51

Grouping the ObjectsYou are now going to group all three objects and manipulate them together.

1. Click the button in the Edit Toolbar to set the Selection Tool.

2. Click somewhere on a blank area of the window to deselect any selectedobjects.

3. Position the cursor above and to the left of the Rounded rectangle.

4. Holding the left mouse button down, drag the cursor down and to the rightcreating a bounding box or “lasso” large enough to enclose all of the objectsin the project window and release the mouse button.

5. Click the button on the Toolbar to align all of the grouped objects totheir horizontal centers.

Notice how the objectsaligned to the right.Alignment always keysoff of the object with theblack handles.

Page 64: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 52

6. Click the button on the Toolbar to space all of the grouped objects equallyfrom the top of the group to the bottom.

7. Click on the Group tool in the Edit Toolbar to group the objects.

8. Use one of the methods described earlier in the lesson to display theproperties of the group and name it “grpLesson1”.

Page 65: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 53

9. Drag the left side of the group to the left to resize the group and the objectscontained within it.

10. Double Click while holding the Shift and Ctrl keys down on one of the groupedobjects. This selects the group and allows you to edit individual objects in thegroup.

Note: Variable size is automatically assigned to text objects in a group when thegroup is resized by dragging a handle.

Page 66: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 54

11. Click on the button in the Alignment Toolbar to align all of the groupedobjects to their Horizontal center points.

12. Click the button to undo the last changes until your window returns to theimage below.

Save the Project and Exit1. Select the Save item from the Project menu2. Select the Exit item from the Project menu to exit the program.

Page 67: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 1: Learning to Use Infilink • 55

Page 68: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 56

Tag Groups and Tags

OverviewThis section describes the Tag Database Editor. You will use this editor to definegroups that represent PLC devices and tags that represent locations on thesedevices.

About Tag GroupsA Tag Group is used by Infilink to identify a source of data. A Tag Group can referto a piece of physical hardware, an OPC or DDE link or internal memory locationswithin Infilink. What follows is a description of each of the possible Tag Grouptypes.

SystemThese are internal memory locations maintained by Infilink that contain systeminformation. Such as the current date and time, the name of the current user, etc.Tags cannot be defined for this Tag Group and are read only.

MemoryUser defined memory locations within the context of the running project. A tagthat is used to hold the intermediate results of a calculation would be assigned tothis node.

DDE (User Defined)A type of PLC hardware device, program or DDE server application that willprovide data to Infilink. For DDE servers, the Server Name will identify a serverapplication and topic a node in that server.

OPC (User Defined)An OPC server application that will provide data to Infilink. For OPC servers, theProg ID will identify an OPC application.

VirtualA Virtual Tag serves as a pointer to another tag's information. These tags can thenbe dynamically reassigned to another tag's values during Run mode with a script.Virtual tags can hold data of any type.

Page 69: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 57

Adding/Editing Tag GroupsThe Tag Editor is called up by selecting Tag Groups… from the Project menu orby pressing F6.

Creating Tag GroupsThe Tag Groups dialog box is used to add user defined Tag Groups to a project.Click on Tag Groups… in the Infilink Project menu or press F6.

Clicking on Tag Group icon allows you to add a new Tag Group of that type,double clicking on a defined and highlighted tag group allows you to edit thegroup’s properties.

Edit Tag Group Properties ToolUse this tool to bring up the properties window of a Tag Group.

Delete Tag Group ToolUse this tool to delete a Tag Group. A Tag Group can only be deleted if it is empty.

Page 70: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 58

Creating a Memory Tag Group

1. Click on the tool.

2. Name: Enter a name that will identify this Tag Group. The name you enterhere will appear in scripts that use Tags from this group.

3. Click OK to add the group.

Creating a DDE Tag Group

1. Click on the tool.

2. Name: Enter a name that will identify this Tag Group as a link to a DDEserver. The name you enter here will appear in scripts that use Tags from thisgroup.

Page 71: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 59

See Using DDEAlthough KEPware's OPCserver is referred to asKEPServerEX, its applicationname is still KEPDDE.

3. Server name: Enter the name of the program or DDE server application thatthis Tag Group will use to get to a DDE information source.

4. For a DDE Tag Group, you would enter the name of the server application thatwill be providing data to your project. If you will be using KEPware's OPCserver, you would enter KEPDDE if the server and Infilink will reside on thesame PC. Otherwise, you would enter a string of the form \\<computername>\ndde$ to specify a NETDDE connection to KEPServerEX on the PCidentified by <computer name>.

5. Server topic: Enter the name of the server device or program handle that is aDDE information source.

6. If the Tag Group you are defining uses an Infilink device driver then this fieldidentifies the device on the device network. You must enter a number hereeven if only one device will be used.

7. For a DDE Tag Group you would enter the name of the server topic that theTag Group will represent. Note: If you will be using KEPware's OPC serverthen the topic would be "_ddedata" or an Alias name created in the server.When specifying a topic for a remote server you will need to append a $ toidentify the topic as a registered NETDDE share.

8. Data format: You may specify the format of a DDE connection for a givennode by assigning a format to that node. Available formats are Advanced andCF_TEXT. If you know that a specific server supports both Advanced andCF_TEXT connections (such as KEPServerEX), you can force Infilink to onlyconnect using the format that you choose by assigning the desired connectiontype. When the format is set to Advanced, Infilink will alternately try Advancedfollowed by CF_TEXT when attempting to connect with a server.

Advanced Tab

9. Initially disabled at run mode start: Allows you to manually start looking forDDE information when you need it. In some cases, the DDE information is notavailable until the Server Application is started (sometimes this is after Infilinkis already running).

Page 72: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 60

10. Wait: Puts a delay in before attempting to reconnect to a broken DDE link.This gives the Server a chance to reestablish a link with its Topic.

11. CF_TEXT DDEThese settings apply only when CF_TEXT is the data format.

Enable Block data start requestsOn startup, DDE tag information must be sent to the server so that theserver knows what information to give Infilink. When checked, DDE taginformation is sent in a high efficiency fashion to the server. Otherwise,each DDE tag's information is sent normally. Check this box toaccommodate servers without high efficiency request capabilities.

Initialization delay in milliseconds (0-2000)This value causes a communication delay to the DDE server shortly afterInfilink starts. This allows servers with a long response after startup torespond properly to Infilink initialization commands. This delay occurs onlyonce when Infilink is started.

Data start request delay in milliseconds (0-1000)Use this value to put an additional delay after DDE communications areinitialized. Once this delay is over requests for DDE data begin. Thisallows servers with a long response after initialization to respond properlyto Infilink data requests. This delay occurs only once when Infilink isstarted.

Notes:1. The above two delays can add up to 3 seconds to the startup time ofan Infilink project. Making the delay times shorter reduces this additionaldelay. The delay can be fine-tuned by a trial and error process. Thedelay is dependent on the server you are using.2. KEPServerEX will accept high efficiency data requests and requiresno delays on startup.

12. Click OK to add the group.

Page 73: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 61

Creating an OPC Tag Group

1. Click on the tool.

2. Name: Enter a name that will identify this Tag Group as a link to an OPCserver. The name you enter here will appear in scripts that use Tags from thisgroup.

3. Description: Enter a brief description. This will help you to identify the purposeof the tags in this group later on.

4. Prog ID: Enter the name of the OPC server or source. Use the tool tobrowse for OPC applications that are running at design time. If you will beusing KEPware's OPC server, you would enter KEPware.KEPServerEX.V4 ifthe server and Infilink will reside on the same PC. Otherwise, you enter aremote machine name to specify a remote connection toKEPware.KEPServerEX.V4.

5. Remote machine: Enter a remote machine name <computer name> tospecify a remote connection to the server, named in the Prog ID field.

6. Update Rate: The update rate specifies how often the Tag Group shouldrequest data from the Server.

7. Click OK to add the group.

Page 74: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 62

Creating a Virtual Tag Group

1. Click on the tool.

2. Name: Enter a name that will identify this as a Virtual Tag Group. The nameyou enter here will appear in scripts that use Tags from this group.

3. Description: Enter a brief but meaningful description. This will help you toidentify the purpose of the tags in this group later.

4. Click OK to add the group.

Page 75: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 63

About TagsA tag is a named object that is used to reference a piece of data. The Tag Groupto which the tag is assigned determines the source of the data.

The Tag Groups dialog box is used to define new tags and edit the properties ofexisting tags. You can access this dialog box by pressing F6 or selecting the TagGroups… item from the Project menu while in Design Mode. Any changes thatyou make to the tags are not saved until you save your project.

Predefined System TagsThere are sixteen predefined, read-only memory tags called System tags thatInfilink Run Mode automatically assigns and updates. You cannot delete thesetags or change their properties. System tags are not included in the tag count ofyour application.

_AccessLevel ShortIdentifies the access level of the current user (0-255).

_ActiveAlarmCnt LongIdentifies the number of currently active alarms in the running project.

_AlarmLogStatus ShortIdentifies the state of the Alarm Logger where: 0 = Off, 1 = On and -1 = Disabled.

_DataLogStatus ShortIdentifies the state of the Data Logger where: 0 = Off, 1 = On and -1 = Disabled.

_Date ShortIdentifies the day of the month.

_Day ShortIdentifies the day of the week where: 0 = Sunday, 1 = Monday,..., 6 = Saturday.

See File Functions inScripting.

_FileOpStatus ShortHolds the result of the most recent file operation. Result codes are defined asfollows:

0 Function success-1 File not found-2 Maximum open file count of 8 has been exceeded-3 Unable to create the target file-4 An error occurred during a file read operation-5 An error occurred during a file write operation-6 A memory allocation failure occurred during a read operation-7 The maximum CSV field length of 256 characters has been exceeded.-8 A specified read offset was past the end of the file.-9 An invalid length parameter was specified.

_Hour ShortIdentifies the current hour in 24 hour format where 0 = 12:00 am, 13 = 1:00 pm,etc.

Page 76: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 64

See System Functions inScripting

_MenusVisible DiscreteIdentifies the visible state of the main program menus at run time where 0 = Off, 1= On.

_Minute ShortIdentifies the current minute from 0 to 59.

_Month ShortIdentifies the current month from 1 to 12.

_Msecond ShortIdentifies the current millisecond from 0 to 999.

_ProjectPath StringIdentifies the current project path formatted with a trailing backslash character (\)as in C:\Infilink\Projects\test\

_Second ShortIdentifies the current second from 0 to 59.

_User StringIdentifies currently logged in user. If no user is logged in, this tag will assume thevalue NOUSER

_Year ShortIdentifies the current year in 4 digit format.

Page 77: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 65

Adding/Editing User Defined Tags

Tag Edit Tools

Create new Tag ToolUse this tool to create a new Tag in the active group. Right clicking in the Tagwindow will bring up a shortcut menu to do the same thing.

Edit Tag Properties ToolUse this tool to bring up the Tag Properties window.

Delete Tag ToolUse this tool to delete a Tag. Make sure the tag is not used in any animation orerrors will occur when trying to save the project.

Creating a Memory Tag

Click on a Memory Tag Group in the Tag Group list. Then click on the toolabove the Tag list or right click in the tag list box and select New Tag…

Tag names are not casesensitive and as such"Tag1" is the same as"tag1". You should try touse as descriptive andunique a name aspossible for each tag thatyou define. Doing so willavoid confusion. The tagname can be up to 32characters in length andmust start with a letter.

Tag Name FieldDisplays the name of the currently selected tag. When defining a new tag you willenter the name for that tag in this field.

DescriptionEnter a brief but meaningful description. This will help you to identify the purposeof the tag later.

Initial value (Memory Tags only)Enter the value that you would like this tag to assume when the project is firststarted.

Page 78: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 66

Data Type applies to allTag group types exceptVirtual.

Data TypeUse this list to select a data type for the value that will be assigned to the tag.

Discrete: Boolean value, False = 0, True = 1

Char: An 8 bit signed value with a range from -128 to 127 that represents onecharacter.

Byte: An 8 bit value with a range from 0 to 255.

Short: A 16 bit signed value with range -32768 to 32767

Word: A 16 bit unsigned value with range 0 to 65535

Long: A 32 bit signed value with range -2,147,483,648 to 2,147,483,647

DWord: A 32 bit unsigned value with range 0 to 4,294,967,295

Real: Single precision (4 byte) floating point value with range -3.37 E38 to +3.37E38

Double: Double precision (8 byte) floating point value with range –1.7976931 E308to +1.7976931 E308

String: A character array of varying length from 1 to 256 bytes

SecuritySecurity is used to restrict the user from changing a tag's value. A tag's value maybe changed by a variety of ways. Conditional access can also be implemented byusing Access Levels.

Internal AccessSelect Read Only to prevent the value of this tag from being altered. If a tagvalue is to be modified under project control from either a script or enter dataanimation then it must be given Read/Write privileges.

DDE client accessSelect No Access to prevent OPC/DDE client applications from viewing thevalue of this tag.Select Read Only to allow OPC/DDE client applications to read it's value butprevent the value from being altered.Select Read/Write to allow any OPC/DDE client application to modify thevalue of the tag.

Internet client accessSelect No Access to prevent Internet client applications from viewing thevalue of this tag.Select Read Only to allow Internet client applications to read it's value butprevent the value from being altered.Select Read/Write to allow any Internet client application to modify the valueof the tag.

See Lesson 5 for moreinformation on loggingdata.

Log on data changeUse the Log on data change check box to have value changes for this tagrecorded in a log file.

Click OK to add the group.

Page 79: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 67

Creating a DDE Tag

Click on a DDE Tag Group in the Tag Group list. Then click on the tool abovethe Tag list. Alternatively, right click in the tag list area and select New Tag... fromthe shortcut window.

The Data type shouldmatch the value you areretrieving.

Most Settings are the same as a Memory tag. Additional settings are listed below.

Server itemThe address* of the information in the device or tag name in the server. For acontroller this might be a register number (ie. R0012) or in a spreadsheet program acell location (c3).

*AddressThe address of a Server item is a string of 1 to 30 characters that specifies an itemname supported by the topic identified in the DDE Tag group properties.Note: If you will be using KEPServerEX without an Alias as the topic, you mustspecify the Channel and Device as well as the address for the item name.<Channel Name>.<Device Name>.<Address>

You can specify an optional scan rate and/or data type for the item using theformat:

<item name>@<scan rate>

Where:<item name> is the path to the device address or just an address if an alias isused.<scan rate> is the scan rate of the address in milliseconds. Infilink will request theinformation from the DDE server at this interval. The scan rate specifies howoften the device driver should request this piece of data from the device.

Page 80: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 68

Creating an OPC Tag

Click on an OPC Tag Group in the Tag Group list. Then click on the toolabove the Tag list. Or right click in the tag list area and select New Tag... from theshortcut window.

The Data type should matchthe value you are retrieving.

Most Settings are the same as a DDE tag. Additional setting listed below.

Design Tip

When more than oneaddress in the server isselected, Infilink willmake tags for all of theselected addresses. Thispowerful feature easesthe task of creating tagsseparately in Infilink afterthey have already beencreated in the server.

Server itemThe address* of the information in the device or tag name in the server.

*AddressThe address of a Server item is a string of 1 to 32 characters that specifies an itemname supported by the Prog ID identified in the OPC Tag group properties. Ifyou will be using KEPServerEX, specify the item using the format:

<channel name>.<device name>.<item name>

Where:<channel name> is the name of the Channel in the OPC server<device name> is the name of the device in the OPC server<item name> is the device address in the controller or a tag name that wascreated in the OPC server

Use the tool to browse for OPC Server items. This will generate the addressfor you automatically and put it in the Server item text box.

Note: Once a tag name is entered, the browse button will prompt you ifyou want to change the tag name. Select NO to continue with thebrowsing.

Page 81: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 69

Access path (optional)If the Server accesses two tags or addresses with the same name, a specific path isnecessary to determine which value will be returned to Infilink. If you will beusing KEPServerEX, specify the item using the format:

<channel name>.<device name>

Where:<channel name> is the name of the Channel in the OPC server<device name> is the name of the device in the OPC server

Engineering TypeThe Tag will hold the value as scaled by the OPC server.

Raw TypeThe Tag will hold the device’s un-scaled value from the OPC server.

Creating a Virtual Tag

Click on an OPC Tag Group in the Tag Group list. Then click on the toolabove the Tag list. Or right click in the tag list area and select New Tag... from theshortcut window.

Only a Name is needed.

Page 82: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 70

Tag Edit Advanced Tab

DeadbandSelect the Enable check box to set the minimum raw value change the tag canundergo before Infilink will see the value as changed.

Example: If a deadband of 10 is entered, the tag’s raw value must change by ±10units from that last recorded value before a new value for the tag will berecognized and logged.

If the initial value of thetag is set to a lesservalue than the Minimumclamp, an error messagewill be reported to theEvent Logger.

Value clamps / ScalingClampingSelect the Minimum check box to set the minimum raw value the tag can accept. Ifthe value goes below this value the minimum value is returned.

Select the Maximum check box to set the maximum raw value the tag can accept.If the value goes above this value, the maximum value is returned.

For example, if the clamp values are set to 10 minimum and 40 maximum Infilinkwill never allow the tag to assume a value less than 10 or greater than 40.

ScalingDDE and OPC tags can be scaled. Scaling is a simple linear interpolation betweenthe raw values and the engineering values entered. Engineering Minimum andMaximum are the scaled value range that Infilink will use for scripts andanimations. Raw Minimum and Maximum are the data range received from theserver. When Infilink writes data back to the server the scaling is “backed out” orreversed so that the server gets relevant data.

For example: The value of a word from the server is a 10-bit A/D converter valuewith the range of 0 to 1024. You would like to see it displayed as values rangingfrom 4 to 20. Set the Raw minimum as 0 and the maximum as 1024. Set theEngineering minimum as 4 and the maximum as 20. (Shown above).

Page 83: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 71

Tag Edit Scripts Tab

Scripts TabDisplays a Script Editor dialog box to view or edit the data change script for theselected tag.

Tag Edit Discrete, Level and Deviation Alarm TabsSee Lesson 4 for moreinformation on alarmsand alarm logging.

Alarm TabsDisplays the alarm definitions. If you have added a tag that has an assigned datatype other than string, you may use these tabs to assign alarms to it.

Exporting the Tag DatabaseRight click in the Tag Groups list. You can use the Export Tags to CSV File… itemon the Tag Group shortcut menu to generate a .CSV (comma separated variable)text file containing the selected group’s tag data for the current project. The file iscomposed of a Field Identification Record that identifies the order and content ofthe fields (columns) in each record (row) and the tag information that correspondsto those fields.

Page 84: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 72

Special Note: This is thebest way to create aCSV file. Let Infilinkcreate a template usingthe Export Tag Databasefunction. Then add tothe template and read itback with the Import TagDatabase function..

Quick TipIf you intend to use the CSV function to create your tag database in another product suchas Microsoft Excel, create a couple of tags using Infilink's normal group and tag editors.Once you have a small tag database established, use the export tag database function togenerate a template CSV file. You can then import this file into Excel and add to it asneeded.

Tag Database Field Definitions

Tag NameThe name of the tag.

DescriptionThe user supplied description of this tag.

Eng. Data TypeThe data type to use from within Infilink. Discrete, Short, Word, Long, etc.

Raw Data Type (OPC tags only)The data type to expect from the server. Discrete, Byte, Char, Short, Word, Long,DWord, Real, Double, String.

Server Item (OPC and DDE tags only)The device location/DDE item the tag references.

Access Path (OPC tags only)The path to the device location of the OPC item the tag references.

Initial value (Memory tags only)Initial value assigned if a memory tag.

Local AccessR/W if the tag may be written to, RO otherwise.

Client Access“None” if the tag cannot be accessed from DDE client application, RO if read onlyaccess is provided, R/W if full read/write access is provided.

Internet Access"None" if the tag cannot be accessed from Infilink Viewer application, RO if readonly access is provided, R/W if full read/write access is provided.

Log On Change“Y” if the data for the tag is to be logged, “N” if not.

DeadbandThe deadband value for the tag if defined.

Min. Value ClampThe minimum engineering value if clamping or scaling is enabled.

Max. Value ClampThe maximum engineering value if clamping or scaling is enabled.

Min. Value Clamp_RawThe minimum raw input value if scaling is enabled.

Page 85: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 73

Max. Value Clamp_RawThe maximum raw input value if scaling is enabled.

DeadbandThe deadband value for the tag if defined.

Discrete Alarm TriggerIf a discrete alarm is defined, the state that triggers that alarm. 0 = False, 1 = True.

Discrete Alarm CommentIf a discrete alarm is defined, the text that is assigned to that alarm. 0 to 64characters.

Discrete Alarm SeverityIf a discrete alarm is defined, the severity that is assigned to that alarm. 0 to 16.

Discrete Alarm Access LevelIf a discrete alarm is defined, the Access level that is assigned to that alarm. 0 to255.

Discrete Alarm ActionIf a discrete alarm is defined, the actions that are assigned to the alarm. “L” = Log,“P” = Print, “D” = Display "E" = E Mail.

Deviation Alarm TargetIf a deviation alarm is defined, the target value that is assigned to that alarm.

Deviation Alarm Min. %%The minor deviation percentage if a deviation alarm is defined.

Deviation Alarm Min. CommentIf a deviation alarm is defined, the text that is assigned to that alarm.

Deviation Alarm Max. %%The major deviation percentage if a deviation alarm is defined.

Deviation Alarm Max. CommentIf a deviation alarm is defined, the text that is assigned to that alarm.

Deviation Alarm SeverityIf a deviation alarm is defined, the severity that is assigned to that alarm. 0 to 16.

Deviation Alarm Access LevelIf a deviation alarm is defined, the Access level that is assigned to that alarm. 0 to255.

Deviation Alarm ActionIf a deviation alarm is defined, the actions that are assigned to the alarm. “L” =Log, “P” = Print, “D” = Display "E" = E Mail.

High High Alarm TriggerHigh high alarm activation value if high/low alarm is defined.

High High Alarm CommentIf a High High alarm is defined, the text that is assigned to that alarm.

Page 86: Infilink HMI

Copyright © 2004 KEP, Inc. Tag Groups and Tags • 74

High Alarm TriggerHigh alarm activation value if high/low alarm is defined.

High Alarm CommentIf a High alarm is defined, the text that is assigned to that alarm.

Low Alarm TriggerLow alarm activation value if high/low alarm is defined.

Low Alarm CommentIf a Low alarm is defined, the text that is assigned to that alarm.

Low Low Alarm TriggerLow Low alarm activation value if high/low alarm is defined.

Low Low Alarm CommentIf a Low alarm is defined, the text that is assigned to that alarm.

Level Alarm SeverityIf a Level alarm is defined, the severity that is assigned to that alarm. 0 to 16.

Level Alarm Access LevelIf a Level alarm is defined, the Access level that is assigned to that alarm. 0 to255.

Level Alarm ActionIf a Level alarm is defined, the actions that are assigned to the alarm. “L” = Log,“P” = Print, “D” = Display "E" = E Mail.

TargetThe target value if a deviation alarm is defined.

Major DevThe major deviation percentage if a deviation alarm is defined.

Minor DevThe minor deviation percentage if a deviation alarm is defined.

Notes

1. System tags are not included in the CSV output.

2. Data change and Alarm scripts are not included in the CSV output

3. If a tag database that contains scripts is exported, modified and then importedback into the same project, the scripts will remain intact.

4. When importing a tag database, the fields of an identification record are notrequired to be in any specific order.

5. When importing a tag database, only required fields need be included buteach included field must have a matching field in the identification record.

Page 87: Infilink HMI

Copyright © 2004 KEP, Inc. • 75

Importing the Tag DatabaseYou can use the Import Tag Database… item on the Tools menu to merge thecontents of a .CSV (comma separated variable) text file consisting of node and tagdata with the existing node and tag data for the current project. You can use theExport Tag Database function to create a template that can then be expanded in aspreadsheet application that supports CSV files. The result can then be saved todisk and imported back into Infilink using this tool.

Page 88: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 76

Page 89: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 77

Animations: Your Process in Action

OverviewNow that you have learned a little about Infilink, we will take the opportunity todiscuss animations. In Infilink, every object can be animated in some fashion torespond either to mouse clicks or changes in the data of an associated control tag.This section discusses all of the Animations available from the Animations DialogBox.

About AnimationsThe following types of animation are defined in Infilink:

1. Show/Hide2. Blink3. Stretch Horizontally4. Stretch Vertically5. Move Horizontally6. Move Vertically

7. Change Color8. Rotate9. Enter Data10. Show Value11. Slider12. Take Action

Not all forms of animation are available for all objects. For example, a Text objectcan have a Show Value animation whereas a Rectangle object cannot, yet bothobjects can have a Take Action animation. Objects can have several animationsdefined at once.Animations are defined using the Animations dialog box accessed from theAnimations… menu item on the Edit menu, by selecting Animations… from theshort cut menu or by pressing the F5 key. An object or group must be selectedbefore you can use the Animations dialog box. Once you are in the Animationsdialog box, only those animations that are appropriate to the object or group aremade available.

You will not be able to assign conflicting animations to the same objects or to thegroups that contain those objects. For example, you cannot place an Enter Dataand Slider animation on the same object.

Page 90: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 78

Animating an Object

The Blink animationcannot be assigned to agroup

Making an Object BlinkThe Blink Animation is used for Blinking an object; either alternately making itvisible, then invisible, or alternately making it one color, then another color. Threeblinking speeds are provided.

. 1. Press the tool or press the Blink button in the Animations dialog box.

2. Press the Tags... button in order to view the Tag List. An Analogtag must be attached to this animation. Select a tag to create a tag name orexpression.

3. Check the Substitute zero for input value if tag data is not valid if desired.Checked: Whenever the Tag value is outside of the specified range the moveanimation puts the object in the zero position.Unchecked: Whenever the Tag value is outside of the specified range themove animation leaves the object in the last valid position.

Page 91: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 79

4. If a Discrete tag is selected, then choose whether to blink the object when thevalue of the tag is Logical TRUE (ON) or Logical FALSE (OFF).

5. If an Analog tag is selected then choose whether to blink when the value iseither Within the Range (Inclusive) or Outside the Range of assigned valuesyou enter under Input value range. If Within the Range is selected, the objectwill blink when the tag value falls within the given Low to High range.

6. Select a Blink type. Show/hide will alternately show and hide the object whenthe blink condition is TRUE. Change colors will alternately change the color ofthe border, interior or text of an object when the blink condition is TRUE. Youset the colors by clicking on the colored rectangles and choosing the desiredcolor in the Color Selection Dialog.

7. Select the desired Blink rate Slow, Medium or Fast. The Fast cycle time isapproximately 400 ms, Medium is approximately 800 ms and Slow isapproximately 1.2 seconds.

8. Choose OK to accept the animation definition.

Showing and Hiding ObjectsThe Show/Hide Animation is used to provide conditional visibility or invisibility of anobject. It can be used with overlapping images to show multiple states of anobject.

The Show/Hideanimation may beassigned to any object.

1. Press the button in the Animations Toolbar. Or, right click on the objectand select animations. Then select the Show/Hide animation button.

2. Press the Tags... button in order to view the Tag List. An Analogtag must be attached to this animation. Select a tag to create a tag name orexpression.

3. Check the Substitute zero for input value if tag data is not valid if desired.Checked: Whenever the Tag value is outside of the specified range the moveanimation puts the object in the zero position.Unchecked: Whenever the Tag value is outside of the specified range themove animation leaves the object in the last valid position.

Page 92: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 80

The Show/HideAnimation can be usedwith overlapping imagesto show multiple statesof an object.

4. If a Discrete tag is selected then choose whether to make the object visiblewhen the value of the tag is Logical TRUE (ON) or Logical FALSE (OFF).

5. If an Analog tag is selected, use the Show when input value is dropdown tochoose Within the Range or Outside the Range. Enter the desired valuerange under Input value range. If the value of the tag is chosen Within theRange, then the object will only be shown when the tag value falls within thatLow - High range.

6. Choose OK to accept the animation definition.

Moving Objects Left and Right (Horizontally) or Up and Down(Vertically)

The Move animationmay be assigned to anyobject except Alarmviewers and Trends.

Move Left/Right incombination with MoveUp/Down, using equalsteps, displays adiagonal path ofmovement.

1. The Move Left/Right Animation is used to move an object in the x-direction.The Move Up/Down Animation is used to move an object in the y-direction.

2. Press the Move Horizontal or Move Vertical button in the Animationsdialog box

3. Press the Tags... button in order to view the Tag List. An Analogtag must be attached to this animation. Select a tag to create a tag name orexpression.

4. Check the Substitute zero for input value if tag data is not valid if desired.Checked: Whenever the Tag value is outside of the specified range the moveanimation puts the object in the zero position.Unchecked: Whenever the Tag value is outside of the specified range themove animation leaves the object in the last valid position.

Page 93: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 81

5. Enter the Input Value Range for Low and High that corresponds to the analogranges. High limit should always be greater than the low limit.

6. The related position of the object for each tag value can be set either by the

keyboard or by clicking the Low or High Related position button . Clickingone of these buttons takes you to the object where you can graphically set thedesired initial and final object positions using the mouse.

7. Choose OK to accept the animation definition.

The Stretch animationcannot be assigned toobjects of type line ortext.

Stretching Objects Left and Right (Horizontally) or Upand Down (Vertically)

The Stretch Left/Right Animation is used for re-sizing an object by changing itswidth.The Stretch Up/Down Animation is used for re-sizing an object by changing itsheight.

Left/Right stretch andUp/Down stretch usedtogether gives an objecta zoom in/out effect.

The Stretch animation isused to create Bargraphobjects.

1. Press the or buttons in the Animations Toolbar. Alternatively, rightclick on the object and select animations. Then select the Slider animationbutton.

2. Press the Tags... button in order to view the Tag List. An Analogtag must be attached to this animation. Select a tag to create a tag name orexpression.

3. An Analog tag must be attached to this animation. Enter the value that the taghas at the end points of motion in the Input value range Low and High editfields. The high limit should always be greater than the low limit.

Page 94: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 82

4. Choose the Direction in which to stretch the object.Left/top edge - Vertical Stretch from the top down; Horizontal Stretch from leftto right.Center - Vertical Stretch from the center up and down; Horizontal Stretchfrom the center left and right.Right/bottom edge - Vertical Stretch from the bottom up; Horizontal Stretchfrom right to left.User Defined - allows the user to set and anchor graphically using the relatedposition button in the Stretch from frame and the mouse. The top and bottomlimits of stretch are set graphically using the other related position buttons.

5. The related position of the object can be set for each tag value either by the

keyboard or by clicking the Low or High Related position button . Clickingone of these buttons takes you to the object where you can graphically set thedesired initial and final size using the mouse.

6. Choose OK to accept the animation definition.

The Rotate animationcan only be assigned toline objects.

Rotating a LineThe Rotate Animation can be attached to a line object. The center of rotation canbe defined anywhere within the window. Typical use is as an indicator needle of ameter or to show the rotation of a wheel.

1. Press the tool or Rotate button in the Animations dialog box

2. Press the Tags... button in order to view the Tag List. An Analogtag must be attached to this animation. Select a tag to create a tag name orexpression.

3. Check the Substitute zero for input value if tag data is not valid if desired.Checked: Whenever the Tag value is outside of the specified range the moveanimation puts the object in the zero position.Unchecked: Whenever the Tag value is outside of the specified range themove animation leaves the object in the last valid position.

Page 95: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 83

4. Enter the Input Value Range for Low and High values that correspond to thetag ranges. High should always be greater than the low value.

5. The Angle of rotation in degrees of the object for each tag value can be set

either by the keyboard or by clicking the relative position buttons. Clickingone of these buttons takes you to the object where you can graphically set thedesired initial and final object rotations using the mouse. Angles of rotationare measured in degrees as shown in the following diagram:

6. Select the Center of rotation (the pivot point). This can be:

Start point - The beginning of where the object was drawn.Center point - The center of the object.End point - The end of where the object was drawn.

User defined - If selected, the relative position button is used tographically set the center of rotation using the mouse.

7. Choose OK to accept the animation definition.

Page 96: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 84

Enter Data Into a TagThe Enter Data Animation allows the operator to assign a value to a tag in RunMode.

The Enter Dataanimation cannot beassigned to objects oftype line, arc, pie orchord.

The Enter Dataanimation can beassigned to a groupeven if one or more ofthe objects in the groupcannot accept the EnterData animation.

1. Press the tool or press the Enter Data button in the Animations dialogbox.

2. Press the Tags... button in order to view the Tag List. Select atag.

3. Once the tag is selected, then select the Entry Method you want to use. Thereare 6 different methods to choose from:

Popup - Displays a popup dialog box that allows the operator to make anon/off selection or keypad if the tag is numerical or keyboard if the tag is astring. A plain data entry field is shown if the Keyboard attached option isselected in Project Properties. All data entry is done in signed decimal format.Toggle TRUE/FALSE - The value of the assigned tag will be toggled fromTRUE to FALSE or from FALSE to TRUE when the mouse button or assignedkey is depressed.Force SET/TRUE (1) - A one will be written to the tag whenever the animationis invoked.Force RESET/FALSE (0) - A zero will be written to the tag whenever theanimation is invoked.Momentary - NO - The value of the assigned tag will change to TRUE whenthe mouse button or assigned key is depressed and back to FALSE whenreleased.Momentary - NC - The value of the assigned tag will change to FALSE whenthe mouse button or assigned key is depressed and back to TRUE whenreleased.

4. If the tag is a numerical value, select the Significant figures to display (1-12).

Page 97: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 85

5. Check Invoke using a keyboard shortcut if you want to supply a keyboardshortcut to activate the animation. Fill out the shortcut controls as desired.

6. If a Numeric tag is selected, Select to limit the range of entry in one of twoways.Default for data type: Limits entry to the range for that Data type.User defined: Limits the range to the settings entered in the High and Low textfields.

7. If your project supports multi-user security, enter the Access level that theoperator must have to activate the animation.

8. Choose OK to accept the animation definition.

Using Sliders to Input DataSlider Animation is used to vary an analog tag value within a given range. Thenew value depends on the position of the Slider. It acts like a “volume control”.

The Slider animationcannot be assigned toobjects of type line, arc,pie or chord.

Slider animations maybe assigned to anygroup.

1. Press the button in the Animations Toolbar. Alternatively, right click on theobject and select animations. Then select the Show/Hide animation button.

2. Press the Tags... button in order to view the Tag List. An Analogtag must be attached to this animation. Select a tag.

3. Enter the value that the tag should assume at the end points of motion in theOutput value range Low and High edit fields.

Page 98: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 86

4. Choose the Direction in which to slide the object, Horizontal (Left/Right) orVertical (Up/Down).

5. The related position of the object can be set for each tag value either by thekeyboard or by clicking the @low value or @high value Related position

buttons . Clicking one of these buttons takes you to the object where youcan graphically set the desired initial and final location using the mouse.

6. Select While sliding to update the value of the tag while the slider is in motionor On release to update the value of the tag following release of the mousebutton.

7. If your project supports multi-user security, enter the Access level that theoperator must have to activate the animation.

8. Choose OK to accept the animation definition.

The Change Coloranimation cannot beassigned to objects oftype bitmap, metafile orgroup.

Changing the Color of an ObjectThe Change Color Animation is used for changing the color of an object based onthe value of a tag. With a Discrete tag, two colors may be chosen - one for eachpossible state. With an Analog tag, up to seven colors may be chosen.

1. Press the tool or press the Change color button in the Animations dialogbox.

2. Press the Tags... button in order to view the Tag List. An Analogtag must be attached to this animation. Select a tag to create a tag name orexpression.

3. Check the Substitute zero for input value if tag data is not valid if desired.Checked: Whenever the Tag value is outside of the specified range the moveanimation puts the object in the zero position.Unchecked: Whenever the Tag value is outside of the specified range themove animation leaves the object in the last valid position.

4. If the object to which you are assigning the animation has a border then youmay choose whether to change the border color by selecting the appropriatechoice in the Border Ranges dropdown selection list.

5. If the object to which you are assigning the animation has an interior then youmay choose whether to change the fill color by selecting the appropriatechoice in the Interior Ranges dropdown selection list.

6. Selecting None disables the color change for the corresponding feature,Border or Interior.

7. If a Discrete tag is selected, choose a color for each of the two states, Off andOn using the Color Selection Dialog.

Page 99: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 87

If an Analog tag is selected, choose the Range number 2 - 7 and the Color foreach range. The first color is assigned when the tag value is below the first valuein the range, the next when the tag value is between the first and second values,etc. The last color is assigned when the tag value is greater than the last valuegiven.

Page 100: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 88

8. Choose OK to accept the animation definition.

Showing the Value of a TagThe Show Value Animation shows the dynamic value of a Tag. It works with bothDiscrete tags and Analog tags. It can be used to monitor a value while a processis running.

The Show Valueanimation can only beassigned to button andtext objects.

1. Press the button on the Toolbar. Or, right click on the object and selectanimations. Select the Show Value button in the Animations dialog box.

2. Press the Tags... button in order to view the Tag List. Select atag to create a tag name or expression.

3. Select the Data type that matches the Tag in the Treat value as frame and fillin its format settings.

String - Char, String tags. If a String tag is selected then no formatting isrequired. The string will be displayed as it appears in the tag. Char isdisplayed as the ASCII character designated by its numeric value.

Discrete - Discrete tags. If a Discrete tag is selected then enter the text toshow when the tag value is ON and when the tag value is OFF.

Integer – Byte, Short, Word, Long, DWord. Choose the desired Integer Formatfrom the list. Available formats are Decimal (Signed), Decimal (Unsigned),Hexadecimal, Octal and Binary. Specify the field width and if you want to showleading zeros.

Real - Real, Double. Set the Real Format fields. Select to display the valuewith a given number of significant numbers (a fixed field width with floating DP(decimal point)). Or, select to display the value in a fixed format with aspecified number of digits to the Left of the DP and a specified number ofdigits to the Right of the DP.

4. Choose OK to accept the animation definition.

Page 101: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 89

Formatting examplesValue Format Tag Value Displayed TextString "Running" RunningDiscrete (On, Off) 0 - False OffShort, Decimal (Signed) -54 -54Word, Decimal (Unsigned) with leading zeros 54 00054Real, 3 significant figures 12.34 12.3 Real, Fixed field, 3 Left, 3 Right 12.34 12.340

The Take Actionanimation cannot beassigned to objects oftype line, arc, pie orchord.

Executing a Script With a Button ClickIn Run Mode, positioning the mouse cursor over an object with a Take Actionanimation causes the cursor to change to a pointing finger. Clicking with the leftmouse button executes the associated At Key Down Take Action script.

Take Action Scripts are for those functions and operations that should occur as adirect result of pressing/clicking on a button or other object. Typically, thesescripts would be used for reading and writing files, opening windows, settingpresets, or acknowledging an event.

There are three types of window scripts: On button down, While button pressed,and On button up. One Script may be written for each type. While the left buttonremains down the assigned While Key Pressed script will execute at the specifiedinterval. After the mouse button is released, the assigned After Key Up script willexecute.

You may assign these scripts in any combination using the following steps.

Page 102: Infilink HMI

Copyright © 2004 KEP, Inc. Animations: Your Process in Action • 90

1. Press the Take Action button on the Animations toolbar.

2. Select when the script will occur.

3. If your project will support multi-user security, enter the Access level that theoperator must have to activate the animation.

See Scripting for moreinformation.

4. If desired, check Invoke using keyboard shortcut and choose an optional ShortCut Key equivalent to the mouse button.

5. Enter the script and Verify that the syntax is correct.

6. Choose OK to accept the animation definition.

Page 103: Infilink HMI

Copyright © 2004 KEP, Inc. Libraries: The Quick Path to Great Looking Apps • 91

Libraries: The Quick Path to Great Looking Apps

OverviewLibraries are files containing previously drawn objects and groups. Infilink has aLibrary Manager to help you organize objects used in a project. The LibraryManager has some tools to help you accomplish this.

Library Manager tools

Create a New Library

Create a New Object Group

Open a library

Save a library

Cut an object

Copy an object

Paste an object

Delete an object or object group

Rename an object or object group

Library Manager Treebar

Page 104: Infilink HMI

Copyright © 2004 KEP, Inc. Libraries: The Quick Path to Great Looking Apps • 92

Create a New Library

1. To create your own libraries, select the New Library item from the File menu or

click on the tool. Enter a logical name for the library, e.g.., "PumpProject","CanningMachine", etc. then click OK. A new empty Library will be created withan empty object group called Untitled.

2. Click on the Rename tool to give the new untitled group an appropriatename. Object group names should reflect the type of objects that are in them.

You are now ready to begin saving objects to the Object group.

Create a New Object Group

All objects must be placed in a group.

To create a new group simply click on the tool.

Then, rename the group using the tool.

The new group is ready to accept objects.

Open a library

Click on . All Infilink libraries have an extension of *.kol or *.lib. System Libraryis the default library that comes with Infilink.

Scroll to the library you want to open, click on it, and then press Open.

Page 105: Infilink HMI

Copyright © 2004 KEP, Inc. Libraries: The Quick Path to Great Looking Apps • 93

Save a library

Click on to save an existing library or enter a filename in the popup dialog ifthis is a new file and click Save to save the current library.

The Library Manager Treebar

A Treebar is a tool that displays the Object Groups and their Objects in ahierarchical fashion. It is located to the left of the object field as shown.

The selected object has its name highlighted in the Treebar. To Rename an object

or object group, click on its name then click on the Rename tool. An Objectname may be up to 64 characters long.

Page 106: Infilink HMI

Copyright © 2004 KEP, Inc. Libraries: The Quick Path to Great Looking Apps • 94

Saving Objects to a Library

Any drawn object placedor drawn on a windowincluding groups ofobjects can be saved toa library. All of theanimations and scriptswill be saved along withthe object or group. Thismakes objects andgroups in libraries auseful resource for futureprojects. Entire windowscan be lassoed, groupedand then saved to alibrary if desired.

1. Click on the object or group to save. Right click to the shortcut menu andselect Copy.

2. Open the library and object group where you want to save the selectedobject or group.

3. Right click in the object field of the library and select Paste from the shortcutmenu. A new Untitled object will be added to the treebar to the left of theobject field. Use Rename to assign an appropriate name, up to 64 characterslong, to the object or group.

Be sure to save the library so that the new object or group is not lost!

Design TipNote: The object to be saved must be copied from an Infilink window. Objectscopied from other programs such as Word or Paint cannot be pasted directly to alibrary. Paste them to an Infilink window first then copy them from the window andpaste them to the library.

Placing an Object or Group from a LibrarySee Appendix A for alist of Infilink libraries.

Using predefined libraryobjects speedsdevelopment of aproject. Objects from alibrary can be placed inany Infilink window.

1. To place an object or group from a library in a project window, simply click onand drag it on to the project window. Once an object has been placed, it maybe moved, edited, or animated.

2. Resize and adjust the object as desired. Objects that have been animated andcopied to a library retain these animations and the tags associated with them.

If these objects are copied from the library into a project window you will have tosupply valid tag names to support the animations. Infilink allows you to reassignthe tags in your library objects when you paste them onto your project window. Ifthe object has an animation assigned to it the Reassign Tag dialog pops up.

Page 107: Infilink HMI

Copyright © 2004 KEP, Inc. Libraries: The Quick Path to Great Looking Apps • 95

Reassigning TagsThe Reassign Tagfunction can be invokedat any time on anywindow by simply rightclicking on an object. Ifthe object contains tags,the Reassign Tagsselection will beavailable from theshortcut menu.

Design TipIf you duplicate objectswhich contain taginformation such as adisplay, you can quicklychange the tags in thenewly duplicated objectsusing the reassign tagsfunction. Thecombination of these twofunctions allows you tocreate an object oncethen quickly populateyour window withduplicates each attachedto their proper tags bythe reassign tagsfunction.

The Reassign Tag dialog is used to replace one or more tag names assigned tothe selected object. Each animation and script assigned to the object will bescanned for tag usage. You will be shown a dialog box for each different tag thatis assigned to the object.

The dialog appears as follows:

The text to the right of Old name: indicates the name of a tag found in the scan.This tag may be assigned to more than one animation or script. To reassign this

tag you can either type in a valid tag name or press the New name: buttonand select a tag from the Tag List dialog. When you press the OK button alloccurrences of Old name will be replaced with the tag name shown in the editcontrol.

You can skip reassignment of a tag by pressing OK without making any changesto the name.

Press Cancel at any time to stop the reassignment process.

Page 108: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 96

Page 109: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 97

Scripts: The Final Word in Flexibility

OverviewScripts provide the additional functionality your application may need. Infilinkscripts allow you to perform tasks such as complex scaling operations, filemanipulation, string handling, and user interactions with your process. Thissection is provided as a reference for the script functions.

Page 110: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 98

IntroductionScripts are automated sequences of commands that are executed by Infilink atrun-time. There are five types of scripts:

1. Project Scripts - Assigned at the project level.2. Window Scripts - Assigned at the window level.3. Take Action Scripts - Assigned as an animation at the object level.4. Tag Scripts - Assigned to individual tags.5. Alarm Scripts - Assigned to individual Alarms

This editor is used to editeach type of script.

The following buttons are common to all the editors:

Opens the Tag Group dialog box. You can select a tag from the taglist and its name will automatically be inserted into the script at the cursor location.

Searches the script for errors. If an error is found, a description ofthe error will appear in the status bar at the bottom of the dialog and the cursor willbe placed at the approximate location of the error.

Launches help for the type of script you are editing.

Quits the current edit.

Validates and assigns the script.

Page 111: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 99

Project ScriptAccess to the project script editor is granted by selecting the Scripts tab in theProject Options dialog box. There are three types of project scripts: On projectopen, While project running, and On project close. One Script may be written foreach type.

Project Scripts willcontain those functionsand operations that youneed to have performindependently to whatthe operator is doingsomewhere else in theproject.

You should not attemptto access tags assignedto user defined nodesfrom an On project openor On project close scriptbecause external datamay not be availablewhen the script isexecuted.

On project openInitialization steps that you want to perform when your project starts could betaken care of with a On project open script. This type of script executes oncewhen the project is initially loaded. You might use an On project open script to setthe state of some internal memory tags or launch an external application.

While project runningPeriodic operations at the project level can be performed in a While projectrunning script. While project running scripts execute on a user defined Intervalanywhere between 100 and 99999 ms. While project running scripts are executedbefore any On window open scripts if such scripts are defined.

On project closeAny project level cleanup that you need to perform can be done in an On projectclose script.

Entering a Project Script1. Press the Scripts tab and select when the script will occur.

2. Enter the script and Verify that the syntax is correct.

3. Choose OK to accept the script definition.

Page 112: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 100

Example: While running script @ 5000 MS scan rate# If the acknowledge bit for the chlorine alarm# is on. Show the Hazard window and beep the speaker# 5 times.If (chlorine_ack == ON) then Show "Hazard"; Beep(5); Chlorine_ack = OFF;Endif;

Window ScriptsAccess to the window script editor is granted from the Window Properties dialog.You can display the Window Properties dialog for the selected window by selectingproperties from the window's shortcut menu. There are three types of windowscripts: On project open, While project running, and On project close. One Scriptmay be written for each type. The types of script that you may define for a windoware defined below.

Window Scripts are usedfor those functions andoperations that are onlyimportant while thewindow is opened. Forexample you may wantto show or hide certainobjects, or you may wishto perform somecalculation that onlydisplays on the window.

On window showInitialization steps that you want to perform prior to showing a window could betaken care of with an On window show. You might use an On window show scriptto initialize the properties of one or more objects on the window.

While window showingPeriodic operations at the window level can be performed in a While windowshowing script. While window showing scripts execute on a user defined Intervalanywhere between 100 and 99999 ms. You might use this type of script to cyclethe value of a memory tag that is used on the window.

Page 113: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 101

On window hideAny window level cleanup that you need to perform when a window is removedfrom view can be done with an On window hide script. You might use this type ofscript to show a different window.Entering a Window Script1. Press the Scripts tab and select when the script will occur.

2. Enter the script and Verify that the syntax is correct.

3. Choose OK to accept the script definition.

Example: While showing script# Calculate the percentage of capacity used in the brewing vat.# The vat is 27 feet deep. Each foot equals 4800 gallons or 400# GPI. Capacity is initialized at 129,600. Level is recorded in# inches and GPI is initialized at 400.

percap = (level * GPI) / capacity;

Page 114: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 102

Take Action ScriptsAccess to the Take Action script editor is granted from the Animations dialog box.You can display the Animations dialog for the selected object or group by pressingF5. There are three types of window scripts: On button down, While buttonpressed, and On button up. One Script may be written for each type.

Take Action Scripts arefor those functions andoperations that shouldoccur as a direct resultof pressing/clicking on abutton or other object.Typically, these scriptswould be used forreading and writing files,opening windows, settingpresets, oracknowledging an event.

On button downThe script assigned to this phase of the button or key press will execute as soonas the mouse button or assigned short cut key is pressed.

While button pressedThis script executes at the specified Interval from 100 to 99999 ms while themouse button or assigned short cut key remains pressed. You might use this typeof script to change the value of a memory tag at a slightly faster rate than could beattained from repeatedly pressing the key.

On button upThis script executes when the mouse button or assigned short cut key is released.To emulate a Windows style button that initiates a single action you would use thistype of script.

Page 115: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 103

Executing a Script With a Button ClickYou may assign these scripts in any combination using the following steps.

1. Press the Take Action button on the Animations toolbar. Select when thescript will occur.

2. If your project will support multi-user security, enter the Access Level that theoperator must have to activate the animation.

3. If desired, check Invoke using keyboard shortcut and choose an optional ShortCut Key equivalent to the mouse button.

4. Enter the script and Verify that the syntax is correct.

5. Choose OK to accept the animation definition.

Example: On button up script

# When the button is pressed and released,# the Chlorine Gas Alarm is acknowledged.

Chlorine_ack = TRUE;PostMsg ("Acknowledge Chlorine Gas Alarm by operator" +_User);

Tag Data Change ScriptsData Change Scripts arefor those functions andoperations that you wantto perform when datachanges. You might usea Data Change Script tomodify a process when atag exceeds a certainvalue.

Access to the data change script editor is granted by selecting the Scripts tab in aTag's Properties dialog box. You can display the Tag Groups dialog box bypressing F6.

Page 116: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 104

When defining numericaltags, you can assign aDeadband. TheDeadband specifies theminimum amount bywhich the tag value mustchange before a changeevent will be triggered.

On data changeAn On data change script assigned to a tag in the tag database will executewhenever the tag value changes. If the tag has an assigned deadband, the valuemust change by at least that value before the script will execute.

Entering a Tag Script1. Select a tag by clicking the Tag Group tool button to display the defined tags

and then choose one by double-clicking it with the mouse or use the shortcutmenu and select Properties. From the Tag’s Properties dialog box, click onthe Scripts Tab.

2. Enter the script and Verify that the syntax is correct.

3. Choose OK to accept the script definition.

Example:# If the chlorine sensor detects chlorine the chlorine# acknowledge bit is set on.

If (chlorine_detect == 1) then Chlorine_act = 1;Endif;

Alarm ScriptsAccess to the alarm script editor is through a Tag’s properties dialog when youassign an alarm to a tag.

Alarm Scripts are forthose functions andoperations that you wantto perform when analarm condition is active.You might use an AlarmScript to sound an alarmwhen a tag exceeds acertain value. The scriptmay take place at any toall of the possible times.

Page 117: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 105

On active transitionActions that you want to perform when the alarm occurs could be taken care ofwith a On active transition script. This type of script executes once when thealarm initially occurs. You might use a On active transition script to trigger anannunciator or show a diagnostic window.

While activePeriodic operations while an alarm condition exists can be performed with a Whileactive script. While active scripts execute on a user defined Interval anywherebetween 100 and 99999 ms.

On acknowledgePeriodic operations after an alarm is acknowledged can be performed with an Onacknowledge script. On acknowledge scripts execute once when the alarm isacknowledged. Acknowledging an alarm does not stop any While active scriptsfrom executing.

On inactive transitionAny alarm housekeeping that you need to perform can be done in an On inactivetransition script.

Entering an Alarm Script1. Select a tag by clicking the Tag Group tool button to display the defined tags

and then choose one by double-clicking it with the mouse or use the shortcutmenu and select Properties. From the Tag’s Properties dialog box, click onthe appropriate Alarm Tab then click on the Script button.

2. Enter the script and Verify that the syntax is correct.

3. Choose OK to accept the script definition.

Page 118: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 106

Script ReferenceGeneralThe remainder of this chapter deals with the commands and constructs that maybe used when writing a script. Here are some basics:

• A valid script contains at least one statement.• Each statement must end with a semicolon (;)• Keywords such as IF, THEN, While and _SysCmd are not case sensitive.• Window names, tag names and object names are not case sensitive.

Comments In order to continue acomment on the next lineyou must place a # at thebeginning.

You will find it helpful to include comments in your scripts so that when othersreview your work (or even you at a later date) the intended operation of the scriptwill be clear. A comment is defined by preceding the comment text with a pound sign (#) as in:

# This is a sample comment # # Show the value of a numeric expression by assigning it # to a text object. #

Logical Constants The following constants are provided for use in expressions involving the discrete

data type. They can be used anywhere a logical TRUE or FALSE is required.

ON or TRUE may be used to indicate a logical TRUE (1) OFF or FALSE may be used to indicate a logical FALSE (0)

Example: # Sound a beep from the PC speaker if the value of # DiscreteTag1 is TRUE If DiscreteTag1 == ON Then Beep; EndIf;

Page 119: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 107

Conditional Operators Conditional operators are used when creating relational expressions for use in IF-THEN-ELSE or WHILE statements. The following operators are available:

> Greater than < Less than >= Greater than or equal to <= Less than or equal to = or == Equal to <> Not Equal to

Parentheses may beused to set the desiredorder of execution oflogical operations.Operations written inparentheses areevaluated first from theinside out.

Example:

If (tag1 > tag2) then tag3 = 1; elseif (tag1 == tag2) then tag3 = 0; else tag3 = -1; endif;

Logical Operators Logical operators are used when combining conditional expressions.

AND Logical AND Logical expressions involving AND evaluate to TRUE if both sides of theexpression are TRUE. OR Logical OR Logical expressions involving OR evaluate to TRUE if either side of the expressionis TRUE. NOT Logical Inversion Inverts the result of a logical expression.

Infilink assumes that anynon-zero value is TRUE.

Examples: If (tag1 > tag2) OR (tag1 > tag3) then tag4 = tag1; endif; DiscreteTag1 = DiscreteTag2 AND DiscreteTag3; DiscreteTag1 = NOT (DiscreteTag2 AND DiscreteTag3);

Page 120: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 108

Assignment Operator To make an assignment to a tag or object property you would use the equals sign(=) as in: <tag name> = <expression> <window name>.<object name>.<object property> = <expression> When working with the assignment operator, <expression> can be a literal value,tag name, object property, or any combination of these that have compatible datatypes. Compatible simply means that all components of the expression must beeither string or numeric. The target of the assignment determines the appropriatetype. Virtual Tag assignmentVirtual tags can be used to hold other tag's values. No matter what type of valuethat may be. This is done by using the assignment operator. The virtual tag'sname property is assigned to a string that is actually another tag's name. Thesyntax for this assignment operation is:

<virtual tag name>.name="<tag name>";

Examples:

# Assign the result of a numeric expression to a tag tag1 = tag2 + tag3; # Assign a numeric constant to a tag tag1 = 5; # Assign a logical constant to a discrete tag DiscreteTag1 = ON; # Assign a string literal to a string tag StringTag1 = “This is a string”;

# Assign another tag’s value to a virtual tag virTags\virTag1.name="memTags\boolTag";

Page 121: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 109

Arithmetic Operators Arithmetic operators are used when constructing numeric expressions. Thefollowing operators are available:

The addition operatormay also be used toconcatenate strings.

Division by zeroevaluates to zero.

% may be used withinteger data types only.

+ Addition - Subtraction * Multiplication / Division % Modulo division. Returns the remainder from the division of two numbers.

Operators that act on tags or object properties: Toggle <discrete tag/object property>

Toggles the value of a discrete tag or object property from 1 to 0 or 0 to 1. Decr <numeric tag/object property> Decrements the value of a numeric tag or object property by one. Incr <numeric tag/object property> Increments the value of a numeric tag or object property by one.

Examples: # Modulo counter nAngleTag = (nAngleTag + 1) % 360; # Toggle the visibility of an object Toggle _ThisWin.Rect1.Show; # Increment the value of a tag Incr tag1;

Page 122: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 110

Flow Control IF-THEN-ELSE conditional construct.

Syntax: If <relational expression> Then Statement 1; Statement 2; . Statement n; ElseIf <relational expression> Then Statement 1; Statement 2; . Statement n; Else Statement 1; Statement 2; . Statement n; EndIf;

If a <relational expression> resolves to a logical TRUE the statements followingthe Then keyword are executed followed by a jump to the first statement followingthe EndIf keyword. If a <relational expression> resolves to a logical FALSE eachsuccessive ElseIf condition will be evaluated until a logical TRUE <relationalexpression> is found. If all ElseIf conditions are found to be FALSE, the Elsesection will execute if present otherwise execution will jump to the first statementfollowing the EndIf keyword. You may include as many or as few ElseIf sections as are necessary to qualifythe set of conditions you are scripting. You may omit the Else section if no default processing is required.

While Loop

Syntax: While <relational expression> Statement 1; Statement 2; . Statement n; EndWhile;

A While Loop can only be used in a While Showing Window Script, While RunningProject Script, or While Key Pressed Take Action Script. If the <relational expression> resolves to a logical FALSE, execution jumps to thefirst statement following the EndWhile keyword. If the <relational expression>resolves to a logical TRUE, the body of the loop will execute up to the EndWhilekeyword and the script will be suspended until the next interval as specified in theInterval setting. When execution resumes, the <relational expression> isevaluated again and the process repeated.

Page 123: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 111

Math Functions Each of the following functions returns and expects arguments of the real datatype.

Sin (<angle in degrees>) Returns the trigonometric sine of <angle in degrees>

Cos (<angle in degrees>) Returns the trigonometric cosine of <angle in degrees>

Tan (<angle in degrees>) Returns the trigonometric tangent of <angle in degrees>

Asin (<real>) Returns the inverse sine of <real>

Acos (<real>) Returns the inverse cosine of <real>

Atan (<real>) Returns the inverse tangent of <real>

Sqrt (<real>) Returns the square root of <real> (returns zero if <real> is negative)

Pow (<number>, <exponent>) Returns <number> raised to the power <exponent>

Abs (<real>) Returns the absolute value of <real>

Examples:

# Calc the hypotenuse of a right triangle from the lengths# of its other two sides. Hyp = sqrt ((s1 * s1) + (s2 * s2)); # Calc the angle between Hyp and S2 Angle = atan (s1 / s2);

Page 124: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 112

String Functions String functions operate on string expressions. You can specify a stringexpression by using a string literal or string tag or by concatenating string literalsand string tags in any combination using the + operator.

A string literal can be upto 127 characters inlength.

You create a string literal by enclosing the characters you wish to use in doublequotation marks as in "This is a string." If you need to include thedouble quotation character (“) in the string you can precede it with a backslashcharacter (\). If the literal must end with the backslash character because thestring will represent a path name then you should add one additional backslash toprevent the closing quote from being included as part of the string.

LTrim (<string expression>) Returns <string expression> with leading spaces removed.

RTrim (<string expression>) Returns <string expression> with trailing spaces removed.

Trim (<string expression>) Returns <string expression> with leading and trailing spaces removed.

Str (<numeric expression>) Returns the string representation of <numeric expression>

Val (<string expression>) Returns the numeric value of <string expression>.

UCase (<string expression>) Returns <string expression> with all characters converted to upper case.

LCase (<string expression>) Returns <string expression> with all characters converted to lower case.

Chr (<numeric expression>) Returns a single character string consisting of the ASCII character indicated by<numeric expression>.

Len (<string expression>) Returns the number of characters in <string expression>.

Equal (<string expression1>, <string expression2>) Returns 1 if <string expression1> is equal to <string expression2>, 0 if not.

Left (<string expression>, <num chars>) Returns the leftmost <num chars> characters from <string expression>.

Right (<string expression>, <num chars>) Returns the rightmost <num chars> characters from <string expression>.

Mid (<string expression>, <first char>, <num chars>) Returns the middle <num chars> characters from <string expression> starting at<first char>.

Page 125: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 113

StrPathName (<string expression>) Returns the path portion of a file specification identified by <string expression>. If <string expression> were given as c:\path\file.ext the return would bec:\path\

StrFileName (<string expression>) Returns the file name portion of a file specification identified by <stringexpression>. If <string expression> were given as c:\path\file.ext the return would befile.ext

Examples: # Simple string assignment StringTag = "My String"; # Assignment of a string containing embedded quotes QuotedStringTag = "This string needs \"quotes\""; # Assignment of a path to string tag (note the extra # backslash) PathStringTag = "c:\dir1\dir2\\"; # Convert a string to a number NumTag = Val (StringTag);

File Functions The <tag name> passed to the following two functions may be used as <filename> when calling the file read/write functions described below. The tag namesupplied must be a string type.

FileGetWriteName (<tag name>)

Displays a dialog box that allows the operator to select/enter a file specificationand assign it to the string tag identified by <tag name>. The string tag will containa complete file specification including drive, path and filename.

When a selection ismade from this dialog,the path is “remembered”between uses.

Page 126: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 114

FileGetReadName (<tag name>)

Displays a dialog box that allows the operator to select/enter a file specificationand assign it to the string tag identified by <tag name>. The string tag will containa complete file specification including drive, path and filename. The difference between this function and FileGetWriteName() is that for thisfunction the operator must choose an existing file.

When a selection ismade from this dialog,the path is “remembered”between uses.

Notes:1. The file name functions should only be called from a Take Action script (On

button down or On button up).2. The dialog box that is displayed by calling either of these functions will not be

displayed until after the function returns. You should not include anystatements following FileGetReadName() or FileGetWriteName() thatdepend on the file name that is to be selected.

3. You should only call these functions from an On button down or On button upTake Action script.

Page 127: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 115

Each of the following functions returns a Large Integer value indicating the byteoffset into the file where the operation completed. This return value may be usedas the <offset> argument in subsequent calls to the file functions. If an erroroccurs, the function will return -1 and the system tag _FileOpStatus will contain avalue indicating the type of error.

FileWriteText (<file name>, <offset>, <string expression>, <length>)

• Writes <length> characters from <string expression> to the file specified by<file name> starting at byte offset <offset>.e.g. FileWriteText(PathTag, 5, StringTag, LengthTag); Writes StringTag dataover existing file data beginning after character 5.

• If <offset> is given as -1, the characters will be appended to the file.e.g. FileWriteText(PathTag, -1, StringTag, LengthTag); Writes StringTag datato end of existing file data.

• If <offset> is given as -2, the specified file is completely erased prior toperforming the write operation.e.g. FileWriteText(PathTag, -2, StringTag, LengthTag); File will contain onlycharacters from StringTag

• If an <offset> is given that is past the end of the file, the space between thecurrent file endpoint and the new characters will be padded with spaces.

• If <length> is given as -1, all characters in <string expression> will be written.• No carriage return line feed is appended to the output text. If the text should

be terminated with a CR-LF pair you can append +Chr(13)+Chr(10) to <stringexpression>.

Example:# The string parameters used within the FileWriteText# function can also be entered as literals such as: # FileWriteText #("C:\testfile.txt", -1, "String", Len("String”)); PathTag = "C:\temp\testfile.txt"; StringTag = "New Message: " + plc_string + Chr(13) + Chr(10); LengthTag = Len (StringTag); FileWriteText (PathTag, -1, StringTag, LengthTag); if _FileOpStatus <> 0 Then Show "MyErrorWindow"; endif;

Page 128: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 116

FileReadText (<file name>, <offset>, <string tag/object property>, <length>)

• Reads <length> characters from the file specified by <file name> starting atbyte offset <offset> into <string tag/object property>

• If a read past end of file is attempted, the function will read as much data as itcan and return -1. _FileOpStatus will be set to -4.

• If an <offset> is given that is negative or past the end of the file no action willoccur.

• The tag or object property specified must have write permission and be a stringtype.

Example:# The string parameters used within the FileReadText# function can also be entered as literals such as:# FileReadText("C:\temp\testfile.txt", 0, StringTag, 100);

PathTag = "C:\temp\testfile.txt"; FileReadText(PathTag, 0, StringTag, 2000); if _FileOpStatus <> 0 And _FileOpStatus <> -4 Then Show "MyErrorWindow"; endif;

FileWriteCSV (<file name>, <offset>, <tag name>, <number of tags>)

• Generates a record which consists of comma separated data fields from<number of tags> tags starting with <tag name>.

• <tag name> must be of the form "base name+numeric suffix" i.e. Tag43,DataVal20.

• <tag name> and <number of tags> must be literals.• CSV data fields are limited to 250 characters each.• The <offset> is the starting record where new data fields are written to the

specified file.• If <offset> is given as -1, output is appended to the specified file.• If <offset> is given as -2, the specified file is erased prior to performing the

write operation.

Example:# The file name parameter used within the FileWriteCSV# function can also be entered as a literal such as: # FileWriteCSV ("C:\temp\testrec.csv", -1, UserTag1, 10); # In order for this script to compile properly, your tag# database would need to contain tags UserTag1,# UserTag2,...,UserTag10.# The values of these ten tags would then be written to# the CSV output file. PathTag = "C:\temp\testrec.csv"; FileWriteCSV(PathTag, -1, UserTag1, 10); if _FileOpStatus <> 0 Then Show "MyErrorWindow"; endif;

Page 129: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 117

FileReadCSV (<file name>, <offset>, <tag name>, <number of tags>)

• Reads comma separated data from <file name> starting at <offset> record.• The data is read into tags starting with <tag name> and progressing until

<number of tags> fields are read.• <tag name> must be of the form "base name+numeric suffix" i.e. Tag43,

DataVal20.• <tag name> and <number of tags> must be literals.• The <offset> is the number of records into the file, each record may any

number of data fields.

Example:# The file name parameter used within the FileReadCSV# function can also be entered a literal such as:# FileReadCSV ("C:\temp\testrec.csv", 0, UserTag1, 10); # In order for this script to compile properly, your tag# database would need to contain tags UserTag1,# UserTag2,...,UserTag10.# These ten tags would then be loaded with the data read# from the CSV input file. PathTag = "C:\temp\testrec.csv"; FileReadCSV(PathTag, 0, UserTag1, 10); if _FileOpStatus <> 0 Then Show "MyErrorWindow"; endif;

Page 130: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 118

Sound Functions The function that you will use to generate sound from a Infilink project depends onwhether or not the target PC will have an installed sound card and speakers.

Beep (<numeric expression>) Issues one or more beep to the PC speaker. If <numeric expression> is given then the result of that expression will determinethe beep count, otherwise a single beep will be issued. No special audio hardware is required to use this function.

PlaySound (<string expression>) Plays the sound specified by <string expression>. <string expression> can be a .WAV file specification or the name of a systemsound as defined in WIN.INI. The size of a .WAV file specified to this function should be < 100 KB in length. This function requires a sound card.

Example:# Sound an alarm when the fluid level exceeds our limitif (TankLevel > TankLimit) then TankInlet = OFF; PlaySound (WaveFilePath + "tanklim.wav");endif;

Window FunctionsThe argument to each of the following functions is the name of a window (not thewindow title). In all cases <window name> must be quoted as in "Win001".

Hide <window name>Makes a window invisible, but does not unload it from memory.

Load <window name>Loads a window into memory, but does not make it visible.

Move <window name> To <new left>, <new top>Changes the location of a window. Coordinates are relative to the upper leftcorner of the main application window.

Move <window name> By <horizontal change>, <vertical change>Changes location of a window relative to its current location.

Resize <window name> To <new width>, <new height>Changes the size of a window.

Resize <window name> By <change in width>, <change in height>Changes size of a window relative to its current size.

Show <window name>Makes a window visible. If the window is not already in memory, it will be loaded.

Page 131: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 119

Unload <window name>Removes a window from memory.

Examples:# Move this window to the right by 10 pixels (Because we# are operating from Take Action script assigned to a# button on the window we want to move we can use _ThisWin.)# Move _ThisWin by 10, 0;

# Hide a window and show a different oneHide “MainMenu”;Show “TrendView”;

System FunctionsAll system functions have the following syntax: _SysCmd.<identifier>Supported identifiers are described below. If a command corresponds to a menuitem, the item is given as <Menu>/<Item>.

AboutBox Help/About...Displays the Run Mode About Box.

AlarmLogStart Logger/Start alarm loggerTurns on the Alarm Logger.

AlarmLogStop Logger/Stop alarm loggerTurns off the Alarm Logger.

CloseWin File/Close windows...Displays a list of open windows that may be selectively closed.

DataLogStart Logger/Start data loggerTurns on the Data Logger.

DataLogStop Logger/Stop data loggerTurns off the Data Logger.

DataLogPulse Logger/Pulse data loggerPulses the Data Logger, causing it to take a “snap-shot” of all tags that have theLog Data attribute set.

DesignMode Project/Design modeReturns the project to Design Mode for editing.

EventLog Windows/Show eventsBrings the Event Logger to the foreground.

Exit Project/ExitExits Infilink Run Mode.

HideMenusCauses the menu bar at the top of the main window to be hidden, restrictingaccess to the menu commands.

Page 132: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 120

LogIn Users/Login...Displays the login dialog box.

LogOut Users/Log outLogs the current user out of the system. A user must be logged in for thiscommand to succeed.

OpenWin Project/Open windows...Displays a list of unopened windows that may be selectively opened.

ShowMenusCauses the menu bar at the top of the main window to be shown, allowing accessto the menu commands.

GroupConnect (<"group name">) Causes the specified OPC tag group to attempt to establish a connection with

the server.

GroupDisconnect (<"group name">) Causes the specified OPC tag group to break a connection with the server.

GroupDisable (<"group name">) Causes the specified DDE tag group to stop communicating with the server.

GroupEnable (<"group name">) Causes the specified DDE tag group to resume communications with the

server.

GroupReset (<"group name">)Causes the specified DDE tag group to break then re-establish a link with theserver.

Examples:# Initialize the display on start_SysCmd.HideMenus;_SysCmd.Login;

Miscellaneous Functions

Run (<string expression>)Evaluates <string expression> and attempts to launch a Windows application ofthat name. The return value will be TRUE if the application is launched andFALSE if not.

PostMsg (<string expression>)Posts the result of string expression to the Event Logger window. This functioncan be used when debugging a script or to post messages about the result of anoperation.

ExitStops executing the current script.

Exit Application andPulseDataLogger areprovided for compatibilitywith previous versions ofInfilink.

Exit Application (same as _SysCommand.Exit () )Closes the project and exits Infilink Run Mode.

PulseDataLogger (same as _SysCommand.DataLogPulse () )Causes the data logger to take a snapshot of all tags that are being logged.

Page 133: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 121

Examples:# This example loads Microsoft Excel with a specific# spreadsheet and if successful, sends the values of tags# PlcTagPressure and PlcTagTemp to the spreadsheet by# assigning those values to tags that reference cells R1C1# and R1C2if Run ("excel.exe calc.xls") then ExcelTagR1C1 = PlcTagPressure; ExcelTagR1C2 = PlcTagTemp;endif;

# Post a message to the event loggerPostMsg (“Tank filled by operator ” + _User);

Color ConstantsAll color constants have the following syntax : _SysColor.<identifier>

Color Identifier Red Value Green Value Blue Value

Aqua 0 255 255Black 0 0 0Blue 0 0 255Fuchsia 255 0 255Green 0 128 0Gray or Grey 128 128 128Lime 0 255 0Maroon 128 0 0Navy 0 0 128Olive 128 128 0Purple 128 0 128Red 255 0 0Silver 192 192 192Teal 0 128 128White 255 255 255Yellow 255 255 0

Example# Change fill color;_ThisWin.MyRectangle.FillColor = _SysColor.Maroon;

Page 134: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 122

Object PropertiesAccess to the properties of an object requires the following syntax:

<window name>.<object name>.<property name>

When accessing an object from within a Window Script or Take Action Script andthat object is on the same window that the script is being assigned to, <windowname> may be substituted with the keyword _ThisWin.

Example:# Change the fill color of an object to RED_ThisWin.Rect1.FillColor = _SysColor.RED;

General Object PropertiesShow DiscreteSets/returns the visible state of the object. TRUE = Visible, FALSE = Hidden.

Name StringReturns the name of the object assigned in Design Mode.

LineColor LongSets/returns the color used to draw the object border.

LineStyle IntegerSets/returns the style of lines used to draw the object border. Values are asfollows: 0 = solid, 1 = dashed, 2 = dotted, 3 = dash dot, 4 = dash dot dot. Non-solid line styles are only applied if the LineWidth property is set to 0 or 1.

LineWidth IntegerSets/returns the thickness of lines used to draw the object border. Values rangefrom 0 to 7 where 7 is the thickest.

FillColor LongSets/returns the color used to draw the interior of filled objects.

FillStyle WordSets/returns the pattern style used to fill the interior of filled objects.

Text StringSets/returns the text assigned to the object

TextColor LongSets/returns the color used to draw text.

Page 135: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 123

The following table shows the accessible properties of each objectObject

LineRectangleRounded RectangleEllipseGroupButtonPolylinePolygonArcPieChordBitmapTextTrendAlarm History ViewerAlarm

Name

RORORORORORORORORORORORORORORORO

Show

R/WR/WR/WR/WR/WR/WR/WR/WR/WR/WR/WR/WR/WR/WR/WR/W

LineStyleR/WR/WR/WR/WN/AN/AR/WR/WR/WR/WR/WN/AN/AN/AN/AN/A

LineWidthR/WR/WR/WR/WN/AN/AR/WR/WR/WR/WR/WN/AN/AN/AN/AN/A

LineColor*R/WR/WR/WR/WN/AN/AR/WR/WR/WR/WR/WN/AN/AN/AN/AN/A

FillColor*N/AR/WR/WR/WN/AR/WN/AR/WN/AR/WR/WN/AR/WN/AN/AN/A

Text

N/AN/AN/AN/AN/AR/WN/AN/AN/AN/AN/AN/AR/WN/AN/AN/A

TextColorN/AN/AN/AN/AN/AR/WN/AN/AN/AN/AN/AN/AR/WN/AN/AN/A

RO = Read Only, R/W = Read/Write, N/A = Not available* Note: Colors are formed by combining 8 bit Red, Green and Blue intensity values into a 24 bit integer of theform: (Blue * 65536) + (Green * 256) + Red. You can also use one of the predefined color constants whenassigning colors at run time.

Arc, Pie and Chord PropertiesStartAngle IntegerSets/returns the angle in degrees between the horizontal centerline of the objectand a line drawn from the center point to the point on the border at which drawingbegins.

EndAngle IntegerSets/returns the angle in degrees between the horizontal centerline of the objectand a line drawn from the center point to the point on the border at which drawingends.

Clockwise DiscreteSets/returns the direction in which the object is drawn. TRUE = Clockwise fromStartAngle, FALSE = Counterclockwise from StartAngle.

Rounded Rectangle PropertiesCornerWidth IntegerSets/returns the width of the ellipse used to create the rounded corners.

CornerHeight IntegerSets/returns the height of the ellipse used to create the rounded corners.

Alarm Viewer PropertiesSeverity IntegerSets/returns the severity of alarms that can be displayed in the alarm window. Thisproperty has a valid range of 0 to 9. Alarms of severity greater than or equal to thisvalue will be displayed.

AckAll ServiceAcknowledges all current alarms.

ScrollUp, ScrollDown Service Scrolls the alarm display up/down by one line.

Page 136: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 124

ScrollLeft, ScrollRight ServiceScrolls the alarm display left/right by one column.

AlarmCount IntegerRead only property that identifies the number of alarms displayed in the viewer.

Alarm History Viewer PropertiesFilter ServiceDisplays a dialog box that allows the operator to select filter settings for the viewer.

ScrollLeft, ScrollRight ServiceScrolls the alarm display left/right by one column.

ScrollUp, ScrollDown ServiceScrolls the alarm display up/down by one line.

PageUp, PageDown ServiceScrolls the alarm display up/down by the number of lines that may be viewed atone time.

Home ServicePositions the first available alarm at the top of the view.

End ServicePositions the last available alarm at the bottom of the view.

AlarmCount Large IntegerRead only property that identifies the number of alarms displayed in the window.

StartDate, StartTime StringSets/returns the date/time used to determine the first alarm that will be shown bythe viewer. The format used when reading input or generating output will be thatdefined under the [intl] section of the WIN.INI file. Refer to your Windowsoperating documentation for more information on how to change the format ofthese items.

Print ServiceSends the alarm history to the default Windows printer.

Trend PropertiesMode DiscreteSets/returns the operating mode of the trend where 0 = Real-time and 1 =Historical.

TimeSpan LongSets/returns the time span of a historical trend in seconds. The valid range of thisproperty is from 0 to 2147483.

DrawMode IntegerSets/returns the drawing mode for historical data where 0 = Scatter, 1 = Discreteand 2 = Smooth.

Scatter plots data points only along the line of the graph.

Discrete joins data points assuming the value is constant until the next datapoint (i.e. a stair step pattern).

Smooth joins data points directly, this is the default mode used for trends. Evenwith this mode set, the graph can appear to be squared if data changes areabrupt.

Page 137: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 125

Redraw ServiceRefreshes the historical trend using the current trend properties.

StartDate, StartTime StringSets/returns the start date/time used when displaying historical data. The formatused when reading input or generating output will be that defined under the [intl]section of the WIN.INI file. Refer to your Windows operating documentation tochange the format if these items.

See also: Logging Data Path StringSets/returns the DOS path name used when obtaining historical data. It isinitialized to the default data logger path when the object is created.

MinRange, MaxRange RealSets/returns the vertical range of data values displayed on a historical trend.

Skip Long (Write only)Scrolls a historical trend forward or backward by the specified number ofmilliseconds. Assigning a positive value scrolls the trend forward in time, anegative value scrolls it backward. Typically you would use this property in a TakeAction script assigned to a button. One button would use a script to assign anegative value when pressed and another would assign a positive value.

The following four properties work together:CurrentPen IntegerSets/returns the current history pen used with the next three properties. Validvalues range from 1 to 10.

PenTag StringSets/returns the name of the tag assigned to the current pen. Changing thisproperty changes the source of data for the pen.

Cursor LongSets/returns the current cursor position in milliseconds relative to the start time ofthe trend. The cursor value is subtracted from the StartTime and used withCurrentPen to determine PenValue. The cursor value cannot exceed the timespan of the trend.

PenValue RealReturns the value of the CurrentPen at the current Cursor position. If the cursor isbetween samples, the value returned is for the previous sample.

Page 138: Infilink HMI

Copyright © 2004 KEP, Inc. Scripts: The Final Word in Flexibility • 126

Page 139: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 127

Lesson 2: Using Infilink to Mimic A Process

OverviewIf you need help, thecompleted lessons maybe found in the Infilinklessons directory.

These lessons areprovided to give you areference of what aproject should look likewhen completed.

In the last lesson, you learned some of the capabilities of Infilink as a graphicaltool. You should now be familiar with:

• How to draw objects in a window.• How to access and edit object properties.• How to use the Short Cuts and Toolbars.• How to create groups.• How to reshape objects.

In this lesson, you will create a simple process and animate it. As the previouslesson acquainted you with how to navigate in Infilink this lesson will provide anadditional foundation for the lessons that follow.

Page 140: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 128

Lesson Objectives All lesson projects,although written to workwith memory tags, willwork with PLC's withminimal modification.

This lesson is designed to provide you with the basics needed to create a simpleInfilink project that can be applied to a real-world situation. In this project you willlearn:

• How to copy objects from the supplied Libraries.• How to enter tags.• How to create a Project Script.• How to animate an object by associating a tag with it.• You will reinforce editing skills learned in Lesson 1.

When this lesson iscompleted, it willsimulate the filling of atank.

Page 141: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 129

Creating a ProjectYou will start by creating a new project as you did in Lesson 1. For this lesson youwill need to create a project called “Lesson2”.Assign properties to the default window as shown. (Name, Title, Type,Background Color)

Although in this lessonyou are going to resizethe window by the Clickand Drag method, youcan position and size awindow using thedimension settings in theWindow PropertiesDialog.

Page 142: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 130

Copying Library Objects

Place a Pump from the LibraryTo help reduce the development time of your project, Infilink provides an extensiveobject library. All you need to do is find the objects that you want and drag theminto your project windows. A complete preview of all library objects can be foundin Appendix A. For more information on libraries see Libraries: A Quick Path toGreat Looking Apps., later in this document.

If you make a mistakewhen drawing an object,you can choose Undofrom the Edit menu orpress CTRL-Z to backup a step.

1. From the Infilink Main Menu, select the Library Manager item from the View

menu or click on the Project tools toolbar. In the Library Manager SelectOpen from the File menu.

Find and open the “System Library.kol” Infilink library file.

2. Scroll down through the list of library groups until you find the library groupnamed Pumps. Click on “Pumps” to display the pump objects.

Page 143: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 131

You can use the Library ManagerTreebar to expand Library Grouptrees and find objects as well.

3. Move the mouse over each of the objects on the library window. You willnotice that momentarily holding the mouse cursor over an object will display adescription of that object. Use this method to find and select the objectidentified as Horizontal Pump - left shown below.

4. Once your have selected the object, drag and drop the pump to the upper halfof the window and about one third of the way.

If the Library Manager is on topof the Window, you may have tomove Library Manager out of theway.

Unchecking Always On Top inthe Library Manager’s Viewmenu will send the LibraryManager to the background oncethe mouse leaves the LibraryManger window during drag anddrop.

Page 144: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 132

5. Use the procedure from above to drag and drop object Tank 28 from librarygroup Tanks1 into the project window as shown below.

6. Drag and drop object Control Valve - vertical from library group Valves intothe project window.

Page 145: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 133

7. Drag and drop object Long horizontal pipe from library group Pipes1 into theproject window.

8. Drag and drop object Long vertical pipe from library group Pipes1 into theproject window.

9. Close the Library Manager.

Page 146: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 134

Edit/Arrange the Objects in the WindowNow that you have all of the objects you need it’s time to start placing themtogether on the window. Our goal is to have a tank that will be filled using a pump.The inlet to the pump comes from an off screen source via a pipe. A control valvewill be employed to empty the tank to an off screen location. You will place a levelindicator on the tank to display its fill level. The tank fill level will be the onlyanimation assigned in this lesson.

Turn off the grid if it is on byunchecking the Grid item in theView menu.

Rotate, Enlarge, and Place the TankBecause the focal point of the lesson is the tank you will place and size it first.

1. Select the Tank by placing the cursor over it and pressing the left mousebutton.

2. Once selected, click the Rotate Counterclockwise button on the Toolbar torotate the tank 90 Degrees in the counterclockwise direction.

3. You will now resize the tank vertically by placing the cursor over the objecthandle at top center of the object until it becomes a double arrow. Click andhold the left mouse button, and slowly drag the top edge of the tank up. Ourgoal is to stretch the flange on the inlet so that it is slightly larger then thehorizontal pipe. You can check this by dragging the pipe over next to theflange and comparing the ends.

Page 147: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 135

4. You will now resize the tank horizontally. Our goal is to stretch the flange onthe outlet so that it is slightly larger than the vertical pipe. You can check thisby dragging the pipe over next to the flange and comparing the ends. First,resize the Window larger so that it can hold the resized objects.

5. Next place the tank in the upper right corner of the window.

As an alternative to duplicatingthe section of pipe, you couldmake a copy of it and paste thecopy into the project window.

Copy, Size, and Place a Section of Horizontal PipeNow you are going to place a section of pipe at the inlet flange of the tank so thatyou can connect the pump to the tank.

1. Select the Horizontal Pipe.

2. Click the Duplicate Button on the toolbar. A second section of horizontalpipe should appear below and to the right of the original. (Ctrl-D does the samething.)

Page 148: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 136

3. Drag the duplicated pipe to the tank and place it as close to the flange as youcan. If the pipe is not aligned properly use the arrow keys on the keyboard tomove the object while it is still selected. When the grid is disabled the objectwill move one pixel width for each key click, otherwise it will move one gridwidth.

Resize and Place the PumpYou will now place the pump so that it is connected to the inlet pipe.

1. Select the Pump.

2. Drag the pump so that its flange is aligned as close to the pipe as you can getit.

Page 149: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 137

3. Resize the pump until its flanges and pipes are the proper size for thehorizontal pipe.

4. Use the keyboard arrow keys to position the pump flanges against thehorizontal pipe.

Place and Resize the Horizontal PipeNow you are going to place the remaining section of horizontal pipe. Resize it togive the appearance that it is coming from an off screen source connected to thepump.

1. Select the Horizontal Pipe.

2. Drag the pipe and place it as close as you can to the inlet flange on the pump.

3. Use the cursor keys to align the pipe properly with the pump inlet flange.

Page 150: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 138

4. Resize the pipe by dragging its left side to the edge of the screen.

Copy, Place and Size a Section of Vertical PipeYou are now going to create and place a section of vertical pipe at the outlet to thetank.

1. Select the Vertical Pipe and duplicate it.

Page 151: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 139

2. Drag the duplicated pipe to the tank and place it as close to the outlet flangeas you can.

3. Use the keyboard arrow keys to align the pipe to the outlet flange and pipe.

Place and Resize the Control ValveNow you will place the outlet control valve for the tank. You’ll assume that there isa gravity drain on the tank.

1. Select the Control Valve and place it as close as you can to the bottom end ofthe vertical pipe.

Page 152: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 140

3. Resize the valve until the pipe ends are close to the same size.

4. Use the keyboard cursor keys to align the valve to the bottom of the verticalpipe.

Place and Resize the Vertical PipeYou are now going to place the last section of vertical pipe. This will simulate thetank draining to a location somewhere off screen.

1. Select the Vertical Pipe. Align it as close to the outlet flange of the valve asyou can.

Page 153: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 141

2. Use the keyboard arrow keys to align the pipe with the outlet flange of thevalve.

3. Resize the pipe so that it goes to the bottom edge of the window.

You will be writing a script tosimulate a level sensor in thetank. If this were a live projectyou would simply assign a PLCtag to the animation.

Add a Fill Meter to the TankFinally you are going to place two rectangles on the tank to show the level of fill.The first will be a black rectangle that will act as the background for the second,which will be animated to indicate the fluid level inside the tank.

1. Click the Draw Rectangle button on the Toolbar.

2. Draw a black filled rectangle above the outlet flange of the tank as shownbelow.

3. If the Rectangle is not black then click the Fill Color button on the Toolbarand choose black from the color palette.

4. Click the Duplicate button on the Toolbar. A second rectangle shouldappear below and to the right of the first.

5. Click the Fill Color button on the Toolbar and choose a light blue from thecolor palette.

Page 154: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 142

6. Resize the rectangle until it is half the size of the black one.

Page 155: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 143

7. Use the keyboard arrow keys to align the rectangle so that it covers thebottom half of the black rectangle.

8. While you have the rectangle selected, you are going to identify it as animportant object. Press F4 to display the Rectangle Properties dialog box.

9. Enter "T1_level" in the Name field and click OK to close the dialog box.

It is a good idea to assign aname to an object that will beanimated. The name will helpyou locate the object if you mustedit the animation at a later time.

Page 156: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 144

Define a Tag to Assign to the Fill Level AnimationTag names are not casesensitive.

You are now going to create a tag that will be used to drive the animation for thefill level on the tank. You will only go over the steps necessary to build this tag.For details on creating tags see the chapter on Groups and Tags.In a live application that accesses data from a PLC, the tag that you create wouldbe associated with a PLC register connected to a level sensor in the tank. As thetank level increases or decreases, the value in the PLC register would change andthe indicator in Infilink would change in proportion.

1. Select the Tag Groups… item from the Project menu or click the tool todisplay the Tag Groups dialog box.

2. Click the tool to create a new Memory tag group. Name the tag group“Memory”.

3. In the Tag Name field right click and select New Tag… enter"Tank_level" for the tag name.

4. Choose a Data Type of Word and Security for Internal as Read/write.

5. Click the OK button to add the tag to the database.

6. Click the Olose button to exit.

Page 157: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 145

Animate the Object T1_levelNow you are going to create the animation, with the aid of the tag you just added,which will give the rectangle named T1-level the appearance that it is indicatingthe exact level of fluid in the tank.

1. Make sure that you still have the rectangle T1_level selected. You can verifythis by checking the object name in the status bar at the bottom of the Infilinkwindow.

2. With the cursor positioned over the light blue rectangle, press the right mousebutton to activate the short cut menu and select Animations….

3. From the Animations dialog, click the Stretch Vertically button .

Page 158: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 146

4. Click on the button and select the "Tank_level" tag you createdearlier.

5. Click the Stretch from dropdown and select Right/bottom edge.

6. Click the Offset from initial size, Low position button and align the cursorline with the bottom edge of the rectangles.

7. Click the Offset from initial size, High position button and align the cursorline with the top of the black rectangle.

8. Change the Input value range High value to 1000.9. Click OK to accept the animation and exit the Stretch Vertically dialog box.10. Click Close to exit the Animations dialog box.

Page 159: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 147

Create a Script to Simulate an Increasing Fill LevelBecause you are only using a memory tag, you need to write a script to allow us tosimulate a rising fluid level in the tank. Normally you would be using a sensorattached to a PLC or smart device to measure the exact fluid level in the tank.

1. Select Properties… from the Project menu.

For a completeunderstanding of scriptsand how to use them,See Scripting.

2. Select the Scripts tab.3. There are 3 possible types of scripts at the project level: On project open, While

project running and On project close. If the Script Editor did not open by defaultto While project running then select it now.

Page 160: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 148

4. Type in the following Script:

If Tank_Level < 1001 then Tank_Level = Tank_Level + 1;Endif;

5. In the Scan rate field change the number to 100 msec.

6. Click the button to verify that the script is correct. If it is, themessage No errors. will appear at the bottom of the window.

This script will executeevery 100 milliseconds.If the value of"Tank_level" is less than1001 then it will beincremented by 1. If it isgreater than or equal to1001, the script will donothing.

7. Click OK to close the Project Properties dialog box and accept the changes.

Page 161: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 149

Save the ProjectIf a project is modifiedyou will be prompted tosave changes when youchoose Exit or Run.

Now you need to save the project.

1. Select the Save item from the Project menu.

Run the Project1. Select the Run item from the Project menu or click on the tool.2. When the Run Mode starts, you should start to see the blue fill indicator

moving slowly toward the top of the tank.

Exit Run ModeIf you want to keep theRun Mode open for thenext lesson then clickDesign Mode in theProject menu.

1. Click on the Project menu and select Exit.2. The Run Mode is now closed.

Page 162: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 2: Using Infilink to Mimic A Process • 150

Page 163: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 151

Lesson 3: Controlling a Process

OverviewIf you need help, thecompleted lessons maybe found in the Infilinklessons directory.

You have now learned:• How to create a simple animation to monitor a process.• How to copy objects from the object libraries.• How to add a tag.• How to write a simple script.

In later lessons you will select and use some library objects that have animationsalready assigned to them. In this lesson, you will learn:• How to create and animate buttons and text.• How to create scripts that are more complex.• How to control a process from Infilink.

You will see that controlling a process is as easy as monitoring it was in the lastlesson.

Page 164: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 152

Lesson 3 ObjectivesAll lesson projects,although written to workwith memory tags, willwork with PLC's withminimal modification.

Lesson 3 is designed to advance your basic knowledge of creating Infilinkapplications by building upon Lesson 2. You will build upon the previous lesson byadding button controls for the valve and pump, text objects to display the fill rate,drain rate and tank level, and a slider control to vary the drain rate of the tank.

In this lesson you will learn:

• How to draw and animate buttons for use in a control environment.• How to draw and animate text for use as data output and input.• How to create your own slider controls.• How to write a script that controls a process and performs some error

checking..

Continuing from Lesson 2

Opening Lesson 2If you did not close Lesson 2 then skip to the "Adding Some New Tags" section ofthis lesson.

1. Start Infilink Design Mode.2. The Open Project dialog box will be displayed with lesson2 highlighted by

default. If lesson2 is not highlighted you can browse the directory tree until youfind it.

3. Click OK to open the project.

Page 165: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 153

Adding Some New TagsAdding TagsYou will start by adding tags for the new animations. Adding tags first will allowyou to immediately animate an object when you create it. You will be adding 4new tags named Pump_on, Valve_on, Fill_rate, and Drain_rate.

1. Select the Tag Groups… item from the Project menu or click the tool todisplay the Tag Groups dialog box. (or press F6).

2. Click on the Memory tag group. Click on to create a new tag.

3. Type “Pump_on” in the tag name field located to the left of the button.4. Select Discrete from the Data type drop-down list.5. Select Read/Write from the Security Internal drop-down list.6. Click the OK button to add the tag to the database.

Page 166: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 154

7. Click on to create a new tag.8. Type “Valve_on” in the tag name field.9. Select Discrete from the Data type drop-down list.10. Click the OK button to add the tag to the database.

As long as you click Addafter making a changeyou can add new tags bymodifying the previousone.

11. Click on to create a new tag.12. Type “Fill_rate” in the tag name field.13. Select Word from the Data type drop-down list.14. Click the OK button.

Page 167: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 155

15. Click on to create a new tag.16. Type “Drain_rate” in the tag name field.17. Select Word from the Data type drop-down list.18. Click the OK button.

19. Click the Close button.

Page 168: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 156

Add and Animate the New Objects

Object names are limitedto 32 characters.

Add a Button to Turn the Pump On and OffYou are now going to add a button to the project that will turn the pump on and off.You are going to assign three animations to it. The first will be an Enter Dataanimation that will allow us to turn the control bit on and off. The second will be aShow Value animation that will indicate the status of the control bit using thebutton text. The third and final animation will be a change color animation which,will allow us to visually verify the status of the control bit by turning the button redwhen it is off and green when it is on. First you will draw the button.

1. Click the button on the Toolbar and draw a button in the project windownext to the pump.

2. Display the properties dialog for the button and name it “ctrlPump”.3. Click OK.

Text will be added to thebutton using a ShowValue animation.

4. Press F5 to display the Animations dialog box for the button you just created.

Page 169: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 157

You may double click atag name to highlightand select itimmediately.

5. Click the Enter Data button in the Animations dialog box.

6. In the Enter Data animation dialog box, click the button to openthe tag list.

7. Click on the tag Pump_on to highlight it then click the Select button.

You may have noticed the drop down box for Entry Method. Discrete tags offeryou 6 ways to enter or change their data.

• Popup - Displays a popup dialog box that allows the operator to make anon/off selection.

• Toggle TRUE/FALSE- The value of the assigned tag will be toggled fromTRUE to FALSE or from FALSE to TRUE when the mouse button orassigned key is depressed.

• Force SET/TRUE - A one will be written to the tag whenever the animationis invoked.

• Force RESET/FALSE - A zero will be written to the tag whenever theanimation is invoked.

• Momentary-NO - The value of the assigned tag will change to TRUE whenthe mouse button or assigned key is depressed and back to FALSE whenreleased.

• Momentary-NC - The value of the assigned tag will change to FALSE whenthe mouse button or assigned key is depressed and back to TRUE whenreleased.

Page 170: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 158

10. Select Toggle from the Entry Method drop-down list.11. Click OK to accept the animation.

Notice that you canassign short cut keys tothis animation. Anyanimation that requiresthe operator to performan action can beassigned a shortcut.

Access level can beused to control whichoperators have access tothis animation.

12. Click the Show Value button on the Animations dialog box.

Page 171: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 159

13. In the Show Value animation dialog box, click the Tags… button and selectPump_on.

14. Click on the Discrete radio button.15. Notice that the Discrete format fields become active: one field to enter the text

that should be displayed when the tag’s value is ON, and one for when thevalue is OFF.

16. Type "Pump On" in the ON text field and type “Pump Off” in the OFF text field.17. Click OK to accept the animation.

18. Click the Change Color button on the Animations dialog box.

Page 172: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 160

19. Select or type in the name of the Pump_on tag.20. You will notice that there are two Ranges fields and color selection arrays,

Border and Interior. Each has two dropdown lists boxes that allow you toselect the number of colors for the object. Change both dropdowns toDiscrete.

21. You will notice that the labels for the color selection boxes change to Off andOn. These color selections will represent the objects color when the tag is ONor OFF.

22. Click on the Interior rectangle labeled ON and select a bright green.23. Click on the Interior rectangle labeled OFF and select a bright red.24. Click OK to accept the animation.

25. Click Close at the main Animations dialog to accept all the animations and exit.

Page 173: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 161

Add a Text Object to Enter and Display the Pump Fill RateNext, you are going to add a text object that you will interface with the Fill_rate tagto show its value and provide a click point for data entry.

1. Click the button on the Toolbar and draw a text object immediatelybeneath the pump.

2. Display the properties dialog for the object and name it “dspFillrt”. The contentof the Text field is not important because you will be assigning a Show Valueanimation to the object.

3. Click OK.

Page 174: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 162

4. Click the Enter Data button in the Animations toolbar or use the Short Cutmenu to display the Animations dialog for dspFillrt and click the Enter Databutton there.

5. Assign the tag Fill_rate by selecting it from the tag list or typing in the namemanually.

6. Click on the Output value range dropdown and select User defined.7. Type "0" in the Low field and “10” in the High field. These values limit the

range of numbers the operator can enter into the assigned tag.8. Click OK to accept the animation.

9. Click the Show Value button in the Animation toolbar.10. Assign the tag Fill_rate by either selecting it from the tag list or typing the name

manually.11. Check Field width and type "2" in the Field width text field. This format

specifies that the output will have a maximum of two digits. Leaving Leadingzeroes unchecked indicates that leading zeroes will not be displayed.

12. Click OK to accept the animation.

Page 175: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 163

13. Click OK to accept all the animations and exit the Animations dialog box.

14. If the text object is no longer centered under the pump then either drag theobject with the mouse or align it with the cursor keys until it is.

Many sliders areavailable for your use inthe Libraries. This lessonis designed to show youhow easy it is to createyour own object andanimate it.

You may want to enablethe grid so you canmeasure distances usinggrid lines.

Build a Slider to Control the Tank Drain RateYou are now going to build a slider that you will use to control the drain rate of thetank through the drain valve. You will create a Slider animation to set the value oftag Drain_rate. You will also create a Show Value animation to display the settingassigned to Drain_rate.

1. Click the button on the Toolbar and draw a rectangle in the lower leftcorner of the project window.

2. Use the button on the Fill Tools Toolbar to set the fill color to light gray.

3. Click the button on the Toolbar and draw a line on top of the rectangleabout a third of the height from the top. Place the line ends so that they areapproximately a cursor width from either end of the rectangle.

4. Use the button on the Line Tolls Toolbar to set the line color to black.

5. Click the button to select a triple thick line.

Page 176: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 164

6. Click the button on the Toolbar and draw a button centered over the leftend point of the line.

7. Display the properties dialog for the button and name it “sldDrain”.

8. With the button still selected click the Slider button on the AnimationsToolbar.

9. Assign the tag Drain_rate by either selecting it from the tag list or typing thename manually.

10. Set the slide direction to Horizontal (This should be the default setting.)

11. Type "0" in the Low Tag value field and “10” in the High Tag value field.

12. Click the Related position selector buttons to graphically position the end pointsof the slider. You will want the low end to be at the left end of the line, and thehigh end to be at the right end of the line.

13. Click While sliding to allow the Slider to update the tag as you move it.

14. Click OK to accept the animation.

Page 177: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 165

15. Click the button and draw a text object on the rectangle centered belowthe line. This object will be used to display the setting Drain_rate assigned bythe slider.

16. Display the properties dialog for the button and name it “dspDrain”.

17. Assign a Show Value animation to the object that will display the Integer valueof tag Drain_rate using Field width, 2.

18. If the text object is no longer centered below the line then drag it so that it is.

Page 178: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 166

Duplicate the Slider Text Object and Modify It to Display theTank LevelYou are now going to make a duplicate of the text object on the slider and modifyit so that you can display the value of tag Tank_level.1. Select text object dspDrain and right click to Duplicate on the shortcut menu to

make a copy of it.2. Place the duplicated text object just above the tank over the fill indicator.3. Click on the object with right mouse button to display the Short Cut menu and

select Reassign Tags….

Reassign tags allowsyou to selectivelyreplace one tag name foranother in eachanimation and scriptassigned to an object.

4. When the Replace Tag dialog appears, change Drain_rate to Tank_level.5. Click OK to complete the replacement.

6. Display the properties dialog for the object and change the name fromdpsDrain1 to dspTnklvl.

7. Click the Show Value button in the Animation toolbar to edit the ShowValue animation.

8. Type "4" in the Field width to replace the old width of "2".9. If the text object is out of position, drag it so that it is in position.10. Click OK to accept the animation.

Page 179: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 167

Duplicate the Pump Control Button and Modify to use as aValve ControlYou are now going to perform the same process on the button that controls thepump to make a button to control the drain valve.

1. Select the pump control button, ctrlPump and duplicate it.2. Display the Reassign Tag dialog and change the tag name from Pump_on to

Valve_on.

3. Use the properties dialog to change the name of the object from ctrlPump1 toctrlValve.

4. Edit the Show Value animation assigned to ctrlValve to display “Unlocked”when Valve_on is ON and “Locked” when Valve_on is OFF.

5. Your completed project window should appear as shown below.

Page 180: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 168

The pound sign (#) isused in Infilink scriptingto allow you to commentyour scripts.

Modify the Existing Project ScriptYou are now going to modify your existing project script so that it will work with thenew objects in simulating a tank control. If you were using an actual PLC, youwould have flow sensors monitoring the rate of flow at the inlet and outlet, as wellas the tank level. The pump control button would then turn on an actual pump.The slider would then control the butterfly in the valve.

1. Display the Project Options dialog by selecting Properties… from the Projectmenu.

2. Click the Scripts tab to display the Script Editor.3. Replace the existing While project running script with the following:

# If the pump is turned on and the tank is not# full then fill the tank at the specified rate.If Pump_on AND (Tank_Level < 1001) Then Tank_Level = Tank_Level + Fill_rate;Endif;

# If the tank is full then turn the pump off.If Tank_Level = 1000 Then Pump_on = OFF;Endif;

# If the valve is unlocked and the tank is not# empty the tank at the specified rate.If Valve_on AND (Tank_Level > 0) Then Tank_Level = Tank_Level - Drain_rate;Endif;

# If the pump is on then the valve cannot be# unlocked.If Pump_on Then Valve_on = OFF;endif;

# If the Valve is Unlocked then the Pump cannot be#turned on.If Valve_on Then Pump_on = OFF;endif;

Page 181: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 169

1. Click the Check button to verify that there were no typing errors. Fix any errorsthat may be indicated.

2. Click General tab and click the Use popup keypad for data entry startup optionand the Create a project summary compile option.

3. Click OK to accept the script and new project options.

The popup keypadallows you to enter datausing the mouse if theproject will be run on asystem that doesn’tsupport a standardkeyboard.

Create project summarycauses Infilink togenerate a reportwhenever you save theproject. This reportcontains a detailed listingof every tag, window,and object. The report isstored in a file calledCOMPILE.TXT locatedin the project directory.You can use Notepad toview the contents of thisfile.

Page 182: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 170

Save and Run the Project1. Click the Project menu and select Run or press F9.2. You will be prompted to save changes. You should select Yes.

3. Once the project window has opened in run mode, click on the Fill Rate textbeneath the pump.

4. On the popup keypad, click or type "5".5. Click OK to accept the new value for Fill_rate.

Page 183: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 171

6. The text object will now display “5”.7. Click on the pump control button above the pump. The button should turn

green and the text should change from “Pump Off” to “Pump On”.

8. Once the tank level reaches 1000, the color of the pump control button shouldchange to red.

9. Click on the slider button and drag it to the right until the text beneath itdisplays “8”.

10. Click on the valve control button to unlock the valve.11. The valve should drain the tank in increments of “8”. Move the slider and

watch this value change.12. When you are done, select Exit from the Project menu. If you want to make

changes select Design Mode.

Page 184: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 3: Controlling a Process • 172

Page 185: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 173

Logging: Data and Alarms

OverviewThis section covers alarm and data logger setup, assigning alarm information to atag, alarm viewer properties and setup of the alarm printer.

Page 186: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 174

The Alarm LoggerInfilink logs alarm data to disk using a proprietary binary format. Infilink Run Modeuses data in this form when working with an alarm history viewer. To alsogenerate data files that may be viewed in other applications such as MicrosoftExcel you must check the Generate DBF output files option. This option causes aDBF (Data Base Format) file to be created and updated in parallel with each ofInfilink's proprietary data files. Because DBF files are about twice the size ofstandard Infilink alarm log files you should only check this option if you truly needto generate portable alarm data.

An alarm log entry is generated when one of the following events is detected:• A tag is entering an alarm state.• A tag is leaving an alarm state.• The operator acknowledges an alarm.

Each entry contains the following information:• A time stamp indicating when the event occurred.• The name of the operator who was logged in at the time of the event.• The event type.• The value of the tag at the time the event was detected.• The user defined comment associated with the alarm.

The Project Properties Alarm Logger tab allows you to specify the destination andcontrol the scheduling of alarm log file activity.

Page 187: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 175

Basic Settings

See Lesson4 LoggingOnly alarms with the Log attribute enabled will be recorded. You can controlwhether or not the alarm logger should start automatically when the project startsby using the Start logger when project starts option.

DirectoryThe Default option saves alarm log files to a directory called ALARMLOG that isappended to the project directory. For example, if your project directory isc:\Infilink\projects\process1 then Infilink will store the alarm log files toc:\Infilink\projects\process1\alarmlog. Infilink will create this directory if it does notalready exist.

The User specified option allows you to control where logged data will be recorded.You must enter a fully qualified DOS path name consisting of 256 characters orless. Whatever you type here will then have the name ALARMLOG appended toit. If the directory you specify doesn't exist Infilink will create it. To specify anetwork directory, you must first map the network resource to a logical drive.

The naming convention of each log file stored in the chosen directory isYYMMDDHH.ALF. Where YY is the year, MM is the month, DD is the day and HHis the hour when the data in the file begins. If you choose to also generate DBFfiles you will see files of the same base name but with a .LOG extension.

Log File Timings

Change files every n hoursThis value specifies how long after the start time to record alarms before creatinga new log file.

Start at hour nThis value specifies the hour of the day that will be used to determine the start ofthe first log file for that day.

Keep log files for n daysThis value specifies how long after completion of the last update a log file shouldbe preserved before being deleted.

Example:Assume the following:1. Alarm logging is enabled and at least one alarm in the project will be

logged.2. Start logging immediately is enabled for the project.3. Start at Hour = 9:00 am.4. Change Files After = 3 hours.

These settings would yield a cycle of log files created at 9:00 AM, 12:00 PM, 3:00PM, 6:00 PM, 9:00 PM, 12:00 AM, 3:00 AM and finally 6:00 AM before repeating.

If you start your project running at 7:00 AM with these settings, your first log file willbe named in accordance with the 6:00 AM interval in the cycle. Data will belogged to this file until the next scheduled log file change at 9:00 AM.

Page 188: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 176

Preferences

Generate DBF output filesCheck this option to generate a copy of your logged alarms in DBF format. ManyWindows applications recognize this portable format.

Generate MDB output filesCheck this option to generate a copy of your logged alarm data in MDB format.This is the Data Object format used by Microsoft Access and similar programs.Note: Support for Data Objects must be installed on the PC to use the MDBoption. See: Installing DAO

Buffer sizeThe number you specify here will determine how many records the alarm loggerwill buffer before performing a disk write.

Max holding periodThe number you specify here will determine how long the alarm logger should holdon to unwritten data waiting for the buffer size number of records to be available.

Req. disk spaceThe number you specify here will determine how much disk space must beavailable for the alarm logger to run. If the amount of free disk space falls belowthis value while the alarm logger is running, it will stop and post a message to theEvent Logger. If the disk space is below this value when Infilink Run Mode islaunched, the alarm logger simply will not start.

Each alarm log record consumes approximately 100 bytes of disk space. If youare also generating DBF output then this number increases to approximately 300bytes.

Page 189: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 177

Defining AlarmsOne or more alarms can be assigned to a tag from the Tag Group Propertiesdialog. Select the desired tag and click on one of the Alarm tabs to display thealarm parameters.

Level AlarmsLevel alarms are used to trigger an event when the value of a tag exceeds or goesbelow an assigned limit.

Comment TextEnter text to describe the alarm. This text will be displayed in the commentcolumn when the alarm is shown in an alarm viewer or an Alarm History Viewerwindow object.

High/Low AlarmsLo, LoLoAn alarm is triggered for this tag when the value falls below these values. Aseparate alarm is issued for each case.

Hi, HiHiAn alarm is triggered for this tag when the value rises above these values. Aseparate alarm is issued for each case.

Page 190: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 178

Deviation AlarmsAllows two alarms, minor and major to be defined using percentages of thespecified target value to trigger the alarms.

Discrete AlarmsFor tags defined with the discrete (Boolean) data type, you can specify whetheryou want an alarm condition to occur when the value is TRUE (1) or FALSE (0) bychecking the appropriate box.

SeverityAll Alarms can be assigned a severity level in the range 0 to 15. The severity levelof an alarm determines which alarm window(s) in your project will display thealarm. The default severity is 5.

Page 191: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 179

Access LevelAssign an Access level 0 to 255. Only users who are logged in with access levelsgreater than or equal to the alarm access level can acknowledge the alarm in RunMode. The default Access level is 0.

ActionsDisplayAlarm events will be displayed in any active alarm viewer that has a severity levelset equal to the severity of this alarm. Events that will cause the display to updateare transition from inactive to active, change in value while active, and transitionfrom active to inactive. Acknowledged alarms are deleted from all views upontransition from active to inactive.

LogAlarm events will be logged to disk and accessible to any active alarm historyviewer. Events that will be logged are transition from inactive to active, useracknowledge, and transition from active to inactive.

PrintAlarm events will be sent to the local alarms printer on each transition frominactive to active, user acknowledge and transition from active to inactive. SeeSetup Alarm Printer later in this section for more information.

E MailWhen Internet access is enabled, alarm notification is sent via E Mail to theaddress specified in the Project Properties Internet Tab.

ScriptsAlarm Scripts are for those functions and operations that you want to performwhen an alarm condition is active. You might use an Alarm Script to sound analarm when a tag exceeds a certain value. The script may take place at any to allof the possible times.

On active transitionActions that you want to perform when the alarm occurs could be taken care ofwith a On active transition script. This type of script executes once when thealarm initially occurs. You might use a On active transition script to trigger anannunciator or show a diagnostic window.

While activePeriodic operations while an alarm condition exists can be performed with a Whileactive script. While active scripts execute on a user defined Interval anywherebetween 100 and 99999 ms.

On acknowledgePeriodic operations after an alarm is acknowledged can be performed with an Onacknowledge script. On acknowledge scripts execute once when the alarm isacknowledged. Acknowledging an alarm does not stop any While active scriptsfrom executing.

On inactive transitionAny alarm housekeeping that you need to perform can be done in an On inactivetransition script.

Page 192: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 180

Alarm Viewer PropertiesGeneral Tab

See Lesson4 fordirections on how to usethe Alarm Viewer.

NameThe name that you will use to refer to this viewer when using script commands.

X, Y PosSets the location of the upper left corner of the object to the specified coordinates.These coordinates are relative to the upper left corner of the window where theobject resides.

WidthAdjusts the horizontal size of the bounding rectangle.

HeightAdjusts the vertical size of the bounding rectangle.

Page 193: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 181

Text TabAlarm Text ColorsText colors may be used to select the color of the column headings and to indicateindividual alarm status. When an alarm is triggered, it will appear in the alarmviewer with the text color chosen as Active alarm. Double-clicking the alarm willcause it to change to the Active and acknowledged color. If it is not acknowledgedand the tag state that caused the alarm no longer exists, the alarm will change tothe Inactive alarm color. Acknowledged alarms disappear when no longer active.

Severities TabMinimum Severity LevelA number between 0 and 15. The viewer will display alarms with severity greaterthan or equal to the value specified here. The default is 0.

Page 194: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 182

Other TabSort on:Select from the dropdown: Date/Time, Tag Name, Event type, Alarm type, orSeverity heading to sort the listed alarms based on that column. Additionally selectto sort in Ascending or Descending order.

Allow acknowledge on double clickCheck this item to allow alarms to be acknowledged at run time by double clickingon the displayed alarm text.

See Scripting for moreinformation.

Minimum Access Level for AcknowledgmentA number between 0 and 255. Users with access level greater than or equal tothis number may acknowledge alarms displayed by this window. Alarms may beacknowledged by either clicking, as described above, or invoking the AckAll viewerproperty from a script.

Page 195: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 183

Alarm History Viewer PropertiesGeneral Tab

See Lesson4 fordirections on how to usethe Alarm HistoryViewer.

NameThe name that you will use to refer to this viewer when using script commands.

X, Y PosSets the location of the upper left corner of the object to the specified coordinates.These coordinates are relative to the upper left corner of the window where theobject resides.

WidthAdjusts the horizontal size of the bounding rectangle.

HeightAdjusts the vertical size of the bounding rectangle.

Page 196: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 184

Text TabAlarm Text ColorsText colors may be used to select the color of the column headings and to indicateindividual alarm status. When an alarm is triggered, it will appear in the alarmviewer with the text color chosen as Active alarm. Double-clicking the alarm willcause it to change to the Active and acknowledged color. If it is not acknowledgedand the tag state that caused the alarm no longer exists, the alarm will change tothe Inactive alarm color. Acknowledged alarms disappear when no longer active.

Page 197: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 185

Setup Alarm PrinterThe Project Properties Alarm Printer tab is used to choose a target device and/orfile for the alarm printer as well as the format that will be applied to the output.

Send Output To

Local PrinterCheck this box to direct alarm output to a local printer specified by the drop-downlist. Valid selections are LPT1 through LPT3.

Lines per pageSpecify the number of alarms you would like printed on each page. Once thenumber of lines is reached, a form feed is sent to the printer.

Text fileCheck this box to direct alarm output to a text file. You specify the file by typingthe name into the supplied edit control. When this option is selected, the contentsof the file will be reset at project start up.

Event LoggerCheck this box to direct alarm output to the Event Logger window.

See Lesson4 fordirections on using thereshape method. Sample Format

Configure the output format using the reshape method described for an alarmviewer. Available columns are:Date, Time, User, Type, Severity, Event, Tag Name, Value at Event, Comment.

Page 198: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 186

The Data LoggerInfilink logs tag data to disk using a proprietary binary format. Infilink Run Modeuses data in this form when working with a historical trend object. To alsogenerate data files that may by viewed in other applications such as MicrosoftExcel you must check the Generate DBF output files option. This option causes aDBF (Data Base Format) file to be created and updated in parallel with each ofInfilink's proprietary data files. Because DBF files are about 50% larger thanstandard Infilink log files you should only check this option if you truly need togenerate portable log data.

Tag values are logged once when the initial value of the tag is determined andthen once every time the value of the tag changes. Each entry in a log file isstamped with the date and time the data was determined to have changed so anaccurate history of its activity can be presented.

Infilink also provides a script command called _SysCmd.DataLogPulse that you canuse to generate log entries on demand or at timed intervals instead of or inaddition to the standard log on data change method described above.

The Setup Data Logger dialog box allows you to specify the destination andcontrol the scheduling of data log file activity.

Page 199: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 187

Basic Settings

DefaultThis option saves log files to a directory called DATALOG that is appended to theproject directory. For example, if your project directory isc:\Infilink\projects\process1 then Infilink will store the database files toc:\Infilink\projects\process1\datalog. Infilink will create this directory if it does notalready exist.

See Nodes and Tags.

See Lesson5 fordirection on viewinglogged data in ahistorical trend.

User specifiedThis option allows you to control where logged data will be recorded. You mustenter a fully qualified path name consisting of 256 characters or less. Whateveryou type here will then have the name DATALOG appended to it. If the directoryyou specify doesn't exist, Infilink will create it. To specify a network directory, youmust first map the network resource to a logical drive.

The naming convention of each log file stored in the chosen directory isYYMMDDHH.DLF. Where YY is the year, MM is the month, DD is the day and HHis the hour when the data in the file begins. If you choose to also generate DBFfiles you will see files of the same base name but with a .LOG extension.

Log File Timings

Start logger when project startsChecking this item enables the recording of tag data and automatically starts thedata logger when the project is executed in Run mode. Only tags with the LogData attribute enabled will be recorded. Data logging can still be invoked later onusing the _SysCmd.DataLogStart script command.

#Start the Data Logger ;_SysCmd.DataLogStart ;

Change files every n hoursThis value specifies how long after the start time to record data before creating anew log file. The range is 1 to 24 hours.

Start at hour nThis value specifies the hour of the day that will be used to determine the start ofthe first log file for that day. The range is 0 to 23.

Keep log files for n daysThis value specifies how long after completion of the last data update a log fileshould be preserved before being deleted.

Example:Assume the following:

Data logging is enabled and at least one tag in the project will be logged. Start logging immediately is enabled for the project. (See Project Options.) Start at Hour = 9:00 am. Change Files After = 3 hours.

These settings would yield a cycle of log files created at 9:00 AM, 12:00 PM, 3:00PM, 6:00 PM, 9:00 PM, 12:00 AM, 3:00 AM and finally 6:00 AM before repeating.

If you start your project running at 7:00 AM with these settings, your first log file willbe named in accordance with the 6:00 AM interval in the cycle. Data will belogged to this file until the next scheduled log file change at 9:00 AM.

Page 200: Infilink HMI

Copyright © 2004 KEP, Inc. Logging: Data and Alarms • 188

Preferences

Generate DBF output filesCheck this option to generate a copy of your logged data in DBF format. ManyWindows applications recognize this portable format.

Generate MDB output filesCheck this option to generate a copy of your logged data in MDB format. This isthe Data Object format used by Microsoft Access and similar programs.Note: Support for Data Objects must be installed on the PC to use the MDBoption. See: Installing DAO

Buffer sizeThe number you specify here will determine how many records the data logger willbuffer before performing a disk write.

Max holding periodThe number you specify here will determine how long the data logger should holdon to unwritten data waiting for the Buffer size number of records to be available.

Req. disk spaceThe number you specify here will determine how much disk space must beavailable for the data logger to run. If the amount of free disk space falls belowthis value while the data logger is running, it will stop and post a message to theEvent Logger. If the disk space is below this value when Infilink Run Mode islaunched, the data logger simply will not start.

Each log record consumes approximately 40 bytes of disk space. If you are alsogenerating DBF output then this number increases to approximately 130 bytes.

Page 201: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 189

Lesson 4: Alarms and Alarm Logging

OverviewIf you need help, thecompleted Infilink lesson4 may be found in theInfilink lessons directory.

These lessons aredesigned to run withoutthe use of a PLC.

Alarms are used to inform the operator that something important has happened ina process that Infilink is monitoring. You can define High/Low and Deviation typealarms for analog values and On/Off alarms for discrete values. When an alarmevent is detected for a particular tag, the details of the event can be displayed in analarm viewer, sent to a local printer, and logged to disk. In this Lesson you will seehow to define and view alarm events using Infilink.In Lesson 4, you will learn how to:1. Draw an Alarm Viewer and add control buttons.2. Draw an Alarm History Viewer, add control buttons, and enable alarm logging.3. Define alarms for analog and discrete tags.4. Create sliders and a button to generate alarms.5. Display the active alarm count using a Show Value animation.6. Run a project and manipulate real time and historical alarms.

Page 202: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 190

Lesson ObjectivesThis lesson will guide you through the utilization of Alarms and Alarm Logging in aInfilink project. In this lesson you will learn:1. How to design Alarm and Alarm History Displays.

2. How to add control buttons to interface with Alarm and Alarm History Displays.

3. How to enable alarm logging.

4. How to define High/Low, Deviation, and Discrete alarms.

5. How to add previously drawn objects from Infilink libraries to your project.

6. How to manipulate alarms at Runtime.

This lesson is intended for intermediate users of Infilink.

Page 203: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 191

Creating a New Project1. Open Infilink's Design Mode.

2. Click Cancel in the Open Project dialog box.

3. Click the File menu, then click on New…

4. Type in a name for your project, such as lesson4, and click Create.

5. Click Yes to verify the name and path of your project.

6. Right click and open the Windows Properties dialog box. Type“Alarm_Lesson” for a window Name and type “Alarm Lesson Panel” for aTitle. Click Show at Startup, then click OK. Size the window so that it fills thescreen.

Drawing the Alarm ViewerAn alarm viewer displays alarm events as they occur in real time.

1. From the Infilink Main Menu, select Draw, then select Alarm viewer or click the

button on the Toolbar.

2. Move the Pencil cursor to the window and draw an alarm viewer, leaving roomto the left and above for text and buttons.

3. If all of the alarm viewer column titles are not visible, resize the object suchthat it appears like the figure below.

4. To modify column widths select Reshape from the Short Cut Menu. Reshapemode can also be invoked from the Infilink Main Menu by selecting Edit then

Reshape, or from the Toolbox by selecting the Reshape tool .5.

6. When in Reshape mode the alarm viewer will appear in a black and whiteformat as seen above. To make changes to column widths, use the mouse todrag the appropriate column divider lines to the left or right. Other columnediting options are available from the Short Cut Menu. To view these optionsplace the cursor in the column that you would like to edit, right click, thenchoose the appropriate option from the menu as shown below.

7. To return from Reshape mode you can double click the mouse or press theEsc key.

Page 204: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 192

Creating Alarm Viewer Control ButtonsIn order to scroll the contents on an alarm view you need to utilize the Service typeproperties of the Alarm view object. For simplicity, you will use library objects thathave been predefined for this purpose.

1. From the Infilink View Menu, select Library Manager, then Open SystemLibrary.kol

2. Select and expand the library group named ALARMCTR.

3. Drag and drop the buttons shown below from the ALARMCTR library groupand place them into the Main Window above the Alarm Viewer. Leave spaceabove the Alarm Viewer and Control Buttons because later you will add twoSliders and a Button to generate alarms.

4. After you have finished placing in all of the control buttons, minimize theLibrary Manager window.

Page 205: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 193

Drawing the Alarm History ViewerAn Alarm History Viewer displays alarms that have been logged to disk.1. From the Infilink Main Menu, select Draw, then select Alarm History Viewer or

click the button on the Toolbar.

2. Draw an alarm history viewer leaving room to the left and above for buttons.Make the alarm history viewer object the same width as the alarm viewerobject.

The colors used by theAlarm Viewer object canbe set by right clickingon the object andselecting Properties...from the Short CutMenu. Border color andfont can be set using theToolbars.

3. Next use the Reshape mode to adjust the column format of the Alarm HistoryViewer. Delete the User and Severity columns and move other columns suchthat the Alarm History Viewer is formatted as shown below.

4. Exit from Reshape mode.

Page 206: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 194

Creating Alarm History Viewer Control ButtonsAgain you will use library objects to provide control functions.1. Restore the Library Manager.

2. Select and expand the library group named ALARMHST.

3. Drag and drop the buttons shown below from the ALARMHST library groupand place them into the Main Window to the left and above the Alarm HistoryViewer. Resize the window and the buttons as necessary.

4. After you have finished placing in all of the control buttons, minimize theLibrary Manager.

Page 207: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 195

Enabling the Alarm LoggerNow that you have an Alarm history viewer, you need to enable alarm logging.1. From the Infilink Project Menu, select Properties, then select Alarm Logger tab.

2. In the Buffer size: text field enter 5, and in the Max holding period: text field enter1. Accept the defaults for the remaining alarm logger setup properties andclick OK.

Page 208: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 196

Defining Tags with AlarmsIn this section you will add three tags and for each tag you will define an alarm.

1. Click on the from the Toolbar.

2. In the Tag Groups dialog box click on to create a memory tag group

named “Memory”.

3. Click to enter a new tag. Set the tag properties of the first tag as shown

below.

4. Click the Level Alarm tab. Set the alarm properties as shown below.

7. Click OK

Page 209: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 197

8. The HighLowTag Attributes column now includes an “A” indicating that analarm is assigned to the tag.

9. Now add a second tag with the properties shown below.

Page 210: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 198

11. Click the Deviation Alarms tab.

12. Set the alarm properties of the second tag as shown below.

13. Click OK

14. Add the third tag with the properties shown below.

Page 211: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 199

15. Click the Discrete Alarm tab.

16. Set the alarm properties of the third tag as shown below.

17. Click OK then click Close to close the Tag Groups dialog.

Page 212: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 200

Creating Animations to Generate AlarmsIn this section, you will add two sliders and a button from Infilink libraries. Whenyou run the project, you will use these objects to change the values of our threetags, and generate alarms. The alarm data will appear in the views that you haveconfigured.

1. Drag Slider19(Range 0-100)Horizontal from the SLIDERS3 library group anddrop it into the Main Window above the Alarm Viewer. When you place in thisSlider, you will be prompted to “Replace assigned tag names?”. Click Yes andreplace the old name with a new name of "HighLowTag". Resize the slider tofit in the window as shown below.

2. Duplicate the slider that you just pasted into the Main Window, and use theReassign tags… option from the Short Cut Menu to assign the tag"DeviationTag" to the new slider.

3. Drag Button Style 3 from the BUTTONS4 library group and drop it into theMain Window above the Alarm Viewer. When you place in this Toggle Buttonyou will be prompted to “Replace assigned tag names?”. Click Yes andreplace the old name with a new name of "DiscreteTag".

4. Close the Library Manager.

Page 213: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 201

Displaying the Active Alarm CountYou will use a Show Value animation on a Text object, to show the Active AlarmCount.

1. Draw a couple of Text objects over to the left of the Alarm Viewer.

2. For the upper Text object edit its properties and in the text field type “ActiveAlarms”.

3. For the lower Text object, edit its animations and add a Show Value animationwith the System Tag "_ActiveAlarmCnt" assigned to it.

Page 214: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 202

Save and Run the Project1. Click the Project menu, then click Save.

2. Click the Project menu, then click Run.

3. At startup the Sliders will display initial values of 50, and the Button will beRed(OFF). Both the Alarm Viewer and Alarm History Viewer should be blank.

4. Move the first Slider to its outer limits, this will trigger the Low and High alarmsdefined for tag "HighLowTag".

5. Move the second Slider to its outer limits, this will trigger the Major Deviationalarm defined for tag "DeviationTag".

6. Click on the Button between the Sliders to trigger the alarm defined for tag"DiscreteTag".

7. Alarms displayed in the Alarm Viewer can be sorted according to Date, Time,Alarm Type, and Tag Name. To sort alarms, position the cursor on one ofthese Column Headings and click the left mouse once. To reverse the sortorder, click again.

Page 215: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 203

8. Alarms displayed in the Alarm Viewer can be Acknowledged one at a time byusing the left mouse to double click on individual alarm rows. Or, they can beAcknowledged all at once using the Alarm Viewer object's AckAll service thatcan be attached to a button or used in a script.

9. Alarms will be logged to disk and viewable in the Alarm History Viewer,according to the Buffer Size and Max Holding Period that were assigned whenyou enabled the Alarm Logger in the design portion of this lesson. In ourexample, the alarm log is updated after every five alarm events, or after oneminute has elapsed, whichever comes first. For more information on settingup the alarm logger, consult the Infilink help file.

10. The Scrolling, Paging, Home, and End buttons use At Key Down and WhileKey Pressed animations to invoke Service type object properties of theassociated Alarm Viewer or Alarm History Viewer object. See ObjectProperties in the Infilink help file.

11. The History Filter button allows you to filter out logged alarms that you do notwish to see in the Alarm History Viewer window. Only alarms that meetcriteria checked in the Alarm Log Filtering dialog box will be shown.

Page 216: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 4: Alarms and Alarm Logging • 204

Exit Run Mode. 1. Click on the Project menu, then click Exit.

2. The project is now closed. The Event Logger window is still open.3. To close the Event Logger, select the Event Logger’s File menu and click Exit.

Page 217: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 205

Lesson 5: Real-Time and Historical Trends

OverviewIf you need help, thecompleted Infilink lesson5 may be found in theInfilink lessons directory.

These lessons areprovided to give you areference of what aproject should look likewhen completed.

When monitoring process values it is often important to log a history of thosevalues over a period as well as display a portion of the logged data on the screen.Infilink allows you to store the logged data to a file contained in the projectdirectory as well as display real-time and historical data on the screen.In this lesson, you will:

• Draw a trend object and edit its properties.• Toggle a trend between real-time and historical mode.• View historical data in scatter, discrete and smooth modes.• Scroll through historical data.• Increase or decrease the range of the value scale.• Create a sliding cursor that will display values chosen graphically from a

trend.

Page 218: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 206

Lesson Objectives Lesson 5 will guide you through the design and utilization of Real Time and

Historical trends. In this lesson you will learn:• Some basic properties of trends.• How to toggle between Real Time and Historical trend data.• How to scroll historical data.• How to change between historical data modes.• How to modify trend value scales.• How to determine a pen value at any point on a historical trend.

This lesson is intended for intermediate users of Infilink.

Page 219: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 207

Creating a New Project1. Open Infilink's Design Mode.2. Click Cancel in the Open Project dialog box.3. Click the File menu, then click on New…4. Type in a name for your project, such as “lesson5”, and click OK.5. Click Yes to verify the name and path of your project.6. Right click and open the Windows Properties dialog box. Type

“Trend_Lesson” for a window Name and type “Trend Lesson Panel” for aTitle. Click Show at Startup, then click OK.

Defining TagsYou will need to define four tags for this lesson. These tags will allow you toproduce data for a real-time and a historical trend. They will also allow you todisplay data values as the historical trend is scrolled.

1. Click on the from the Toolbar.

2. In the Tag Groups dialog box click on the Memory Group tool to create amemory tag group named “Memory”.

3. Click to enter a new tag. In the Name field enter “PenData” for a tagname. Using the provided drop down list, choose a Data type of “Real” andan Internal Security of “Read/Write”. Since you will want to view historicaldata on this tag, click on the Log on data change selection for this tag. Acceptthe default values for the other fields.

4. Click OK to add the tag to the Memory tag group.

5. Click . Enter “Cursor” for a tag name, “Long” for the Data Type and“Read/write” for the Internal Security. Click OK.

6. Click . Enter “Increment” for a tag name, “Discrete” for the Data Typeand “Read/write” for the Internal Security. Click OK.

7. Click . Enter “Value” for a tag name, “Real” for the Data Type and“Read/write” for the Internal Security. Click OK.

8. Press Close to exit the Tag Groups dialog.

Page 220: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 208

Drawing the Trend and Editing Trend PropertiesThe first thing you need to do is create a trend object and edit its properties.

1. From the Infilink Main Menu, select Draw, then select Trends or click the button on the Toolbar.

2. Draw a trend window leaving room to the left and below for buttons. Resizethe window if necessary.

3. Right click on the trend and select properties, the Trend Viewer Propertiesdialog box will appear.

4. In the Trend Name editbox type “Trend1”,this is the name usedto refer to this object.

While in Design Modeyou can return to the“Trend Property” dialogat any time by rightclicking your mouse onthe trend object andselecting Properties.

5. Click on the Time Axistab. Change the Timespan to 8 Seconds.

6. Change the RefreshRate to 250Milliseconds.

7. Change the Major gridlines to 3.

Page 221: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 209

If the Enable HistoricalDisplay box is notchecked, you will not beable to switch toHistorical Mode whenrunning the project.

8. Click on the Value Axistab. Change theMinimum and Maximumvalue to range from -25to 25.

9. Change the Major gridlines to 3.

10. Click on the Pens tab.

Click , the new

pen tool. Click and select "PenData".

11. Click the OK button toexit the Pen Propertiesdialog box.

12. Click OK to exit theTrend ViewerProperties dialog box.

Page 222: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 210

Creating Trend Control ButtonsThere are library objectsprovided that will performmost of the functions youare about to create. Youmay use them ratherthan create all of theseanimations. The libraryobjects found in theTRENDHST libraryassume a Trend objectname of "Trend". Thetrend in this lesson usesa name of "Trend1".

Following this lesson willgive you a betterunderstanding of howobject properties can beused.

Here you will create buttons to toggle between Real Time and Historical TrendModes, increment and decrement the Trend Value Scale, change the HistoricalDraw Mode, and Scroll through historical data.

1. From the Infilink Main Menu, select Draw, then select Button or click the button on the Toolbar.

2. Draw a Button.3. Right click on the button and select Properties….4. In the Button Properties dialog type “Mode” for the Name and “Historical” for

the button Text. The button text may not be displayed if the button is tonarrow. If this occurs, simply widen the button.

5. Either repeat the above steps for the remaining buttons or use the duplicate

function to make copies of this button. Change the names and text of thecopies to match those below.

A description of the useof these buttons will beexplained in theanimation process.

Name: “YRangeInc”Name: “YRangeDec”Name: “Smooth”Name: “Scatter”Name: “Discrete”Name: “SkipInc”Name: “SkipDec”

Text “+Y Range”Text: “-Y Range”Text: “Smooth”Text: “Scatter”Text: “Discrete”Text: “+10 Sec”Text: “-10 Sec.”

6. Arrange the buttons by dragging each one to a new location. Place thebuttons as shown below.

Page 223: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 211

Create and Animate a Historical Cursor

You can also click on the“Fill” button on the Filltools toolbar.

You will now build a historical cursor animation to graphically determine historicaldata values at runtime. The value at which the cursor intersects the data will bedisplayed.

1. From the Infilink Main Menu, select Draw, then select Polygon or click the button on the Toolbar.

2. Draw a polygon as shown below just above the trend object. This will be ourCursor. Place the polygon as shown.

3. Right click on the polygon and select Properties…. Enter “Marker” for thepolygon object’s name and press OK.

4. From the Interior tab, then select Color. A Fill Color Palette will appear. Selecta color for the Marker.

5. Click OK to close the Polygon Properties dialog.

Page 224: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 212

The Cursor positionrepresents the time inmilliseconds relative tothe start time of thetrend.

The starting position fora trend is the right handside. It scrolls from theright to the left.

1. Select the “Marker” and click . The Slider animation dialog box willappear.

2. Click . For the Tag select “Memory\Cursor”.3. Set the Low value to 0. Set the High value to 7999. This is the range in

milliseconds that will be available on the trend at all times. Recall that you setthe Trend Time Span to 8 seconds (8000 msec.).

4. Now you need to set the Related positions. Click the Low Related Position cursor

. A cursor will appear on the screen. Center this cursor over the rightedge of the trend window and click the mouse button.

5. Now click the High Related Position cursor and center the cursor over theleft edge of the trend. Again click the mouse button to return to the animationsdialog box.

6. Click OK to accept the slider animation.

Page 225: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 213

Animating Trend Control ButtonsNow you will add some functionality to the buttons that have been created. Youaccomplish this by adding animations to each button.

The Mode Button is theone we assigned a textof “Historical” to earlier.

In place of the windowname you can use“_ThisWin” to refer to anobject on the currentwindow.

If you are viewing thisdocument online, simplycut this script out andpaste it into the scriptwindow.

This script also showshow the text on a buttoncan be changed on thefly.

Create an On button down Script for the Mode ButtonThe Mode button will allow us to toggle between real-time and historical mode atruntime.1. Click on the “Mode” button.

2. From the Animation toolbar, select . The Take Action animation dialog willappear.

3. Select the On button down option, if it does not open there by default.4. Enter the following script:

If (_ThisWin.Trend1.Mode = 0) Then _ThisWin.Trend1.Mode = 1; # Change to Historical _ThisWin.Mode.Text = "Real Time"; # Update Button _ThisWin.Marker.Show = 1; # Show Marker Else _ThisWin.Trend1.Mode = 0; # Change to Real Time _ThisWin.Mode.Text = "Historical"; # Update Button _ThisWin.Marker.Show = 0; # Hide Marker Endif;

5. Click the Verify button to make sure there are no errors in the script.6. Click OK to accept the animation.

Page 226: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 214

The YRangeInc Button isthe one we assigned thetext “+Y Range” toearlier.

Create an On button down Script for the YRangeInc ButtonThe "YRangeInc" button will allow us to increment the value span of the trend1. Click on the “YRangeInc” button and create an On button down, Take Action

Animation for "YRangeInc".2. Enter the following script for the action. The # symbol is used to indicate

comments within the script.

# ALLOW THE TRENDS VALUE RANGE TO # SPAN TO A MAXIMUM OF –50 TO 50. If (_ThisWin.Trend1.MaxRange - _ThisWin.Trend1.MinRange < 100) Then _ThisWin.Trend1.MaxRange = _ThisWin.Trend1.MaxRange + 5; _ThisWin.Trend1.MinRange = _ThisWin.Trend1.MinRange - 5; Endif;

3. Click the Verify button to make sure there are no errors in the script.4. Click OK to accept the animation.

The YRangeDec Buttonis the one we assignedthe text “-Y Range” toearlier.

Create an On button down Script for the YRangeDecButtonThe "YRangeDec" button will allow us to decrement the value span of the trend.1. Click on the “YRangeDec” button and create an On button down, Take Action

Animation for "YRangeDec".2. Enter the following script for the action. The # symbol is used to indicate

comments within the script.

# ALLOW THE TRENDS VALUE RANGE TO # SPAN TO A MINIMUM OF –10 TO 10. If (_ThisWin.Trend1.MaxRange - _ThisWin.Trend1.MinRange > 20) Then _ThisWin.Trend1.MaxRange = _ThisWin.Trend1.MaxRange - 5; _ThisWin.Trend1.MinRange = _ThisWin.Trend1.MinRange + 5; Endif;

3. Click the Verify button to make sure there are no errors in the script.4. Click OK to accept the animation.

Create an On button down Script for the Smooth ButtonThe "Smooth" button will redraw the trend by joining data points as lines.1. Click on the “Smooth” button and create an On button down, Take Action

Animation for "Smooth".2. Enter the following script for the action. The # symbol is used to indicate

comments within the script.

# SET THE TREND DRAWMODE TO SMOOTH # HISTORICAL MODE _ThisWin.Trend1.DrawMode = 2;

3. Click the Verify button to make sure there are no errors in the script.4. Click OK to accept the animation.

Page 227: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 215

Create an On button down Script for the Discrete ButtonThe "Discrete" button will redraw the trend by assuming data is constant until thenext data change. The result is a square wave.1. Click on the “Discrete” button and create an On button down, Take Action

Animation for "Discrete".2. Enter the following script for the action. The # symbol is used to indicate

comments within the script.

# SET THE TREND DRAWMODE TO DISCRETE # HISTORICAL MODE (SQUARE LINES) _ThisWin.Trend1.DrawMode = 1;

3. Click the Verify button to make sure there are no errors in the script.4. Click OK to accept the animation.

Create an On button down Script for the Scatter ButtonThe "Scatter" button will redraw the trend as data points.1. Click on the “Scatter” button and create an On button down, Take Action

Animation for "Scatter".2. Enter the following script for the action. The # symbol is used to indicate

comments within the script.

# SET THE TREND DRAWMODE TO SCATTER # HISTORICAL MODE (POINTS ONLY, NO LINES) _ThisWin.Trend1.DrawMode = 0;

3. Click the Verify button to make sure there are no errors in the script.4. Click OK to accept the animation.

Create an On button down Script for the SkipInc ButtonThe "SkipInc" button will allow us to scroll forward in time while in historical mode.1. Click on the “SkipInc” button and create an On button down, Take Action

Animation for "SkipInc".2. Enter the following script for the action. The # symbol is used to indicate

comments within the script.

# SKIP THE TREND WINDOW FORWARD BY # 10000 MSEC. OR 10 SECONDS _ThisWin.Trend1.Skip = 10000;

3. Click the Verify button to make sure there are no errors in the script.4. Click OK to accept the animation.

Create an On button down Script for the SkipDec ButtonThe "SkipDec" button will allow us to scroll backward in time while in historicalmode.1. Click on the “SkipDec” button and create an On button down, Take Action

Animation for "SkipDec".2. Enter the following script for the action. The # symbol is used to indicate

comments within the script.

# SKIP THE TREND WINDOW BACKWARD BY # 10000 MSEC. OR 10 SECONDS _ThisWin.Trend1.Skip = -10000;

3. Click the Verify button to make sure there are no errors in the script.4. Click OK to accept the animation.

Page 228: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 216

Create a Current Value DisplayIn order to view the value associated with the Marker position, you need to createa display. This can be accomplished with a text object and the “show value”animation.

1. From the Infilink Main Menu, select Draw, then select Text or click the button on the Toolbar.

2. Move the pencil cursor and Draw a Text object below the lower right edge ofthe trend.

3. Right click on the Text object and select Properties…. The Properties dialogwill appear.

4. Type "dspValue" in the object name field.5. Click OK to exit the dialog box.

6. Press the Show Value button . For the Tag name Enter “Memory\Value”.7. Because “Value” represents a Real number, select Treat value as Real.

Change the Real format to Fixed field with Left of DP set to 6 and Right of DPset to 2.

8. Click OK to accept the Show Value animation.9. Draw a second text object above the "dspValue". This will be used as a label.10. Right click on the Text object and select Properties…. The Properties dialog

will appear.11. Type "Marker Value" in the text field.

12. From the Infilink Toolbar, click the Bold button to make the text field bold.Select the dspValue bold as well.

Page 229: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 217

Writing a Project ScriptBecause you are only using memory tags you need to write a script to simulate achange in data. Normally you would be collecting data from an external deviceand displaying it in a real-time trend.1. From the Infilink Main Menu, select Project, then select Properties. The Project

Properties dialog will appear.2. Press the Scripts tab.3. Select While project running because you want the script to execute

continuously when in run mode.4. Set the Interval to 250 msec.5. Type in the following script:

This script will beevaluated every 250milliseconds. The “Pen”value will always stay inthe range of ±30 and willincrement or decrementby 2.5 units.

If (PenData >= 30) Then Increment = 0; ElseIf (PenData <= -30) Then Increment = 1; Endif; If (Increment) Then PenData = PenData + 2.5; Else PenData = PenData – 2.5; Endif; # When in Historical mode, load the historical trend's # cursor position with the position of the marker and # retrieve the value of the data at that position. If (Trend_Lesson.Trend1.Mode) Then Trend_Lesson.Trend1.Cursor = Cursor; Value = Trend_Lesson.Trend1.PenValue; Endif;

6. Click the Verify button to make sure there are no errors in the script. If it is,“No errors” will appear at the bottom of the window.

7. Press OK to exit the Project Properties dialog box.

Page 230: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 218

Save and Run the Project1. Click the Project menu, then Click Save.2. Click the Project menu, then click Run.3. The Trend will appear on the screen. Data from “PenData” will be displayed on

the trend.

4. Because the default value span was set to –25 to 25, some data will be out ofrange and will not displayed on the trend. You can correct this by pressing the“+Y Range” button that you created. Click the “+Y Range” button and noticethe value span increases to –35 to 35. The “PenData” waveform should nowbe in complete view on the trend.

Changing the Y valuerange in the Real Timetrend does not change itin the Historical Mode.When you switch toHistorical Mode you willhave to increase therange again to be able tosee all of the data.

Page 231: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 219

5. Wait for a minute to pass, then click the "Historical" button. The historical datawill load to the trend window.

6. Click the “+10 Sec.” Button to scroll 10 seconds forward. The historical datawill now come in to view. You can continue to scroll forward in time. At anytime you wish to return click “-10 Sec.” to scroll backward in time.

Trend is in Discrete drawmode. Notice thatdspValue is displayingthe value of the databeneath the marker.

The draw modefunctions (Scatter,Discrete, and Smooth)are only available while atrend object is inhistorical mode.

7. You can click on the "Scatter", "Discrete", or "Smooth" buttons to change thedraw mode of the trend. Scatter will plot individual points only. Discrete plotsthe points in a squared line, assuming that data is constant until the next datachange. Smooth moves the pen in a straight line between points. The figureabove and the two that follow show identical data in scatter, discrete, andsmooth draw modes.

8. Drag the “Marker Cursor” that you created. Notice that the value displaychanges as the marker intersects a data change.

9. You can return to real-time mode by pressing the "Real Time" button.

Trend in smooth drawmode.

Page 232: Infilink HMI

Copyright © 2004 KEP, Inc. Lesson 5: Real-Time and Historical Trends • 220

Trend in scatter drawmode.

Exit Run Mode1. Click on the Project menu, then click Exit.2. The project is now closed. The Event Log Viewer window is still open.3. To close the Event Log Viewer, select the Event Log Viewer’s Project menu

and click Exit.

Page 233: Infilink HMI

Copyright © 2004 KEP, Inc. ActiveX Controls • 221

ActiveX Controls

OverviewMost ActiveX controls arenot compatible with

Infilink.

Infilink is an ActiveX container. ActiveX controls are independent objects that canbe placed into an Infilink Project. These controls come in many varieties. Infilinkis designed to handle ActiveX controls with OPC connectivity. In particular, wehave tested for compatibility ioCompTM ActiveX controls. These controls areincluded in the Infilink setup software. ActiveX controls from other vendors havenot been verified for operation.

Page 234: Infilink HMI

Copyright © 2004 KEP, Inc. ActiveX Controls • 222

Inserting ActiveX Controls into a ProjectUse the Tools|Load ActiveX controls… menu command to call up the ActiveXSelect controls dialog. A list of the Active X controls installed on the PC isdisplayed.

Select the controls to include in yourproject by checking the box in front of thecontrol’s name.

Note: Up to 24 ActiveX components maybe assigned to a project.

Once all the desired controls are selectedclick OK. The selected controls appear onthe tool bar as an icon.

Place a control by clicking on its icon anddragging a rectangle in the projectwindow.

Access the control’s properties by rightclicking on the shaded border andselecting Properties from the pop-upshortcut menu.

Refer to the help provided with theActiveX control for further informationabout the control’s properties.

Page 235: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 223

Scheduler

OverviewThis section describes how to use the Scheduler to manage tag operations bytime and date.

The Scheduler allows you to specify a particular time and date a tag is to bemodified. There are also features to set tags to be changed on a weekly basis atspecified times. Such events are useful for daily or weekly startup and shutdownof equipment, building controls and regularly scheduled maintenance.

Page 236: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 224

IntroductionUse the Scheduler to program in actions to occur at desired datesand times or on a regular basis. Use Action groups to make severalactions occur at the same time. As actions and times areprogrammed, they are displayed in list boxes throughout Scheduler.

• Use Single and Double events to make actions occur on a givendate and time.

• Use Weekly Schedule to make actions occur on a daily basisevery week.

• Use the Holiday settings to override the weekly schedule.

Using the Calendar Tool

Use the and buttons to scroll through months.Click on a day to select that day.Days that have events assigned to them are shown in Bold.Week numbers are shown in the leftmost column.

Page 237: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 225

HolidaysUse the Holidays dialog box to specify holidays. Holidays cause the WeeklySchedule events to be ignored.

Yearly AddUse this to add a holiday that occurs every year to the list of holidays.For example: January 1st is always a holiday.

Holiday Others AddUse this command to enter Holidays that may vary from year to year.For example: Thanksgiving (USA) changes with each passing year.

How to define a Holiday1. Use the calendar scrolling features to get to the dates you need to specify as

holidays.

2. As you click on dates, a popup dialog prompts you for a label for the holiday.

3. Enter the label and click OK. The holiday will automatically be listed in theappropriate holiday list box.

4. Continue clicking on dates and assigning labels.

5. Click Done after all desired dates are selected.

Page 238: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 226

Action GroupsUse the Action groups dialog box to create groups of actions. This way, instead ofspecifying a tag to be changed at a particular time and date you can specify thegroup of actions to occur at that time. The dates and times that these actionsoccur are specified in the Single Event, Double Event and Weekly Schedule dialogboxes.

Creating an Action Group

1. Select the type of action to occur.New Single Action A single action is a command that occurs when the actionis called.New Double ActionA Double Action is a command that changes state at a start time and thenchanges the state back to its previous condition at an end time.

Page 239: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 227

2. When the Action Group Dialog pops up enter a name for the group. Groupnames may be up to 20 characters long.

3. Click on to enter a new Single or Double Action. See followingpages entering these actions.

4. Continue to click on New to add more actions, Edit to modify actionshighlighted in the list box or Delete to remove the highlighted action from thelist box.

5. Click OK when you are done creating the group.

Page 240: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 228

Entering a New Single Action

1. Enter the Tag to modify. If you do not know the tag name, click on the

button to browse for the Tag to modify.2. Select the type of action to perform on this tag.

• On/Off forces a 1 or 0 into a tag.• Force Value forces a constant into a tag.• Modify Value to changes the tag’s value by a percentage. The

percentage is always a positive whole number.3. Click OK when done

Page 241: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 229

Entering a New Double ActionThis dialog box is used to define what an action does. Because a doubleaction is a duration, two actions need to be specified, a start action andan end action

1. Enter the Tag to modify. If you do not know the tag name, click on the

button to browse for the Tag to modify.2. Select the type of action to perform on this tag when the action is called.

• On/Off forces a 1 or 0 into a tag.• Force Value forces a constant into a tag.• Modify Value to changes the tag’s value by a percentage. Thepercentage is always a positive whole number.

3. Select the type of action to perform on this tag when the action period isended.• Check the Restore value box to put the tag’s previous value (before

the start action) back into the tag.• On/Off forces a 1 or 0 into the tag.• Force Value forces another constant into the tag.• Modify Value to changes the tag’s value by another percentage.

4. Click OK when done

Page 242: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 230

EventsUse Events to specify when a tag or action group is to be changed. The dates andtimes that these actions occur are specified in the Single Event, Double Event andWeekly Schedule dialog boxes.

Creating a Single EventA Single Event is used to execute a data change, once, when it is called. Use thisto change values at some designated time and date.

1. Click on to begin programming this type of Event.

2. When the Single Event Dialog box pops up enter a name for the Event. Eventnames may be up to 20 characters long

3. Check the Disable execution if you want to suspend this event fromhappening. Typically this is used in Run Mode to stop an event fromhappening because it could cause a problem or is no longer necessary.

Page 243: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 231

4. Specify the Date and Time that the action is to take place.

5. Select the Action to perform.• New Single Tag A single action is defined to occur at the Date and Time

specified.• New Action Group An Action group is selected. This means that all

actions specified in the group will happen at the Date and Time.

6. Use the Edit and Delete buttons to modify the list.

7. Click OK when done creating the single event.

Creating a Double EventA Double Event is used to execute an action at a given time and anothercomplimentary action at an end time.

3. Click on to begin programming this type of Event.

4. When the Double Event Dialog box pops up enter a name for the Event. Eventnames may be up to 20 characters long

5. Check the Disable execution if you want to suspend this event fromhappening. Typically, this is used in Run Mode to stop an event fromhappening because it could cause a problem or is no longer necessary.

Page 244: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 232

4. Specify the Date and Time that the action is to take place (Start) and when theaction is to cease (End).

5. Select the Action to perform.• New Single Tag A double action is defined to occur for the duration

specified.• New Action Group An Action group is selected. This means that all single

actions specified in the group will happen at the Start time and doubleactions in the group will continue to the End time.Use the Edit and Deletebuttons to modify the list.

6. Click OK when done creating the single event.

Creating a Weekly ScheduleUse this command to set up a series of events to occur on a weekly basis. Eachday can have various events assigned to it. Events assigned to a day are ignoredif that day is specified as a holiday.

1. Click on to begin programming thistype of Event.

2. When the Weekly Schedule Dialog box pops up enter a name for the Event.Event names may be up to 20 characters long.

3. Check the Disable execution if you want to suspend this event fromhappening. Typically, this is used in Run Mode to stop an event fromhappening because it could cause a problem or is no longer necessary.

Page 245: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 233

4. Specify the Dates that this weekly schedule is to be in effect. Check theForever box to always have this weekly schedule active.

5. Click the Add button to bring up the Schedule dialog box. Select the days ofthe week and times for actions to occur. Repeat this action until all days andtimes are entered.

6. Select the Actions to perform during the times in the Schedule list.• New Single Tag A single action is defined to occur at the scheduled Days

and Times specified.• New Action Group An Action group is selected. This means that all actions

in the group will happen on the Days and Times of the weekly schedule.Use the Edit and Delete buttons to modify the list.

7. Click OK when done creating the single event.

Page 246: Infilink HMI

Copyright © 2004 KEP, Inc. Scheduler • 234

PreferencesUse preferences to change overall operation of the Scheduler.

Because the scheduler is available at run time for review Access can be restrictedto prevent unauthorized access and changes.

Minimum user level to access scheduler at run timeEnter the user level required to access Scheduler once in the Run Mode.

Allow run mode editing.Select to allow editing of Scheduler settings.

Execute events and schedules on defined second.Scheduler tracks events accurately up to the minute. The scheduler can be madeto operate on a per second track if desired.

Minimum and Maximum DatesDisplays the minimum and maximum dates allowed for use with Scheduler. Thesedates are fixed and cannot be changed.

Page 247: Infilink HMI

Copyright © 2003 KEP, Inc. Using OPC and DDE • 235

Using OPC and DDE

OverviewThis section describes how to use Infilink in a client/server configuration with DDE.

About OPC (OLE for Process Control) and DDE (DynamicData Exchange)

Object Linking and Embedding (OLE) for Process Control (OPC)and Dynamic Data Exchange (DDE) allows Infilink to operate in aclient/server relationship with other Windows applications. Anyapplication that supports OPC or DDE can be a client to Infilink, inthat it can access data from Infilink's tag database, and a server thatprovides data to Infilink through a link that has been defined by anOPC or DDE tag group.

OPC Link Specifications

The general format of a local OPC link specification is:<Application>|<Channel Name>.<Device Name>!<Item>

<Application> is the name used to identify the server application.<Channel Name>.<Device Name> is the path to the data set that will bereferenced.<Item> is the individual piece of data that is requested.

Access to Networked machine data is similar to DDE Link Specifications givenbelow.

DDE Link Specifications

The general format of a local DDE link specification is:<Application>|<Topic>!<Item>

<Application> is the name used to identify the server application.<Topic> is the data set that will be referenced.<Item> is the individual piece of data that is requested.

This format is used when the client and the server reside on the same PC.

Page 248: Infilink HMI

Copyright © 2003 KEP, Inc. Using OPC and DDE • 236

A Network DDE link specification takes the form:\\<Computer Name>\ndde$|<Share Name>!<Item>

<Computer Name> is the name of the network PC where the DDE serverapplication is located.<Share Name> is a registered DDE share name identifying the application andtopic.

<Item> is the individual piece of data that is requested.

This format is used when the client and the server reside on different PCsconnected to the same network.

Page 249: Infilink HMI

Copyright © 2003 KEP, Inc. Using OPC and DDE • 237

Infilink as a DDE ClientThe client in a DDE conversation is the recipient of data from another application.

Supported DDE FormatsInfilink supports two DDE formats when used as a client: AdvancedDDE andCF_TEXT. By default Infilink will try to connect using the AdvancedDDE formatand upon failure, fall back to CF_TEXT. You can override the default behavior byspecifying a format for each DDE tag group in your project by modifying the Dataformat section of the DDE Tag group's properties.

See Tag Groups.

Using Infilink as a Local ClientTo use Infilink as a client to a local server (one on the same PC) you will first needto:

1. Create a DDE Tag Group2. Identify the server3. Specify the topic4. Define one or more tags that will be assigned to that tag group.

Each tag will identify the item portion of the DDE link in its address field. The itemrefers to the data that the server should provide.

Although KEPware'sDDE server is now calledKEPServerEX, theapplication name is stillKEPDDE.EXE andshould be used as theapplication name in DDElinks.

Although any DDE enabled Windows application can be a server to Infilink, let'suse KEPServerEX as an example (formerly KEPDDE). Assume you need to getthe data from address 40001 of a Modbus device and assign it to a tag called"RegData". You would first create a project in KEPServerEX that identifies thechannel as COM1 and device as something like "Modbus1". (Refer to theKEPServerEX online documentation for details.) Next you will define a InfilinkDDE Tag Group with KEPDDE as the Server name and_ddedata.COM1.Modbus1 as the topic. Finally, create a tag called RegData withaddress 40001.

Now when you place the server on line and run your Infilink project, the value of"RegData" will be updated every time register 40001 of the Modbus devicechanges.

Using Infilink as a Remote ClientTo use Infilink as a client to a remote server you will perform the same steps as ifyou were using a local server except the application name that you assign to thenode will be of the form \\<computer name>\ndde$ and the topic will have a $appended to it.

The Network DDE services must be started on the PC that Infilink is running onbefore a connection attempt can be made. Under Windows 95/98 you would dothis by running the application NETDDE.EXE. Once you start the Network DDEservices they remain active until you restart the computer.

The server PC that you specify may require you to log in before a connection canbe established. If this is the case, you will be presented with a log in dialog fromthe NETDDE agent on the client PC. You will need to specify an appropriate username and password when this dialog is displayed in order to complete the DDElink.

If a connection attempt fails, Infilink will only attempt to connect one more timebefore assuming the server is unavailable. You can tell Infilink to retry by usingthe Reinitialize Links item on the Run Mode DDE menu. You can also performthis function using the script command _SysCommand.DDEReset.

Page 250: Infilink HMI

Copyright © 2003 KEP, Inc. Using OPC and DDE • 238

Using the same example from above let's assume that the KEPServerEX will berunning on a computer named NETPC. You will define an Infilink node with\\NETPC\ndde$ as the application and _ddedata.COM1.Modbus1$ as the topic.Finally, create a tag called RegData with address 40001 and assign it to this node.

Notes1. KEPServerEX is a 32-bit application. It must be run on either Windows 95/98,

Windows NT or Windows 2000.2. A link to a DDE server item will be started and remain active only as long as some

demand is made on the data provided by that link. See The PROJECT.INI File[tuning] section in the Infilink help file for further information.

Infilink as a DDE ServerThe server in a DDE conversation is the application that is providing data.

A Note About Discrete TagsWhen using Infilink as a DDE server it is important to understand how the clientwill write Boolean values to discrete tags. By default Infilink assumes that if aclient writes a non-zero value to a discrete tag then that tag will be assigned avalue of TRUE. Some clients do not observe this convention but rather onlyconsider the least significant bit of the value they are writing to be what should beassigned.

Using Infilink as a Local ServerTo use Infilink as a server to a local client, you need to tell the client applicationhow to reference the data in Infilink's tag database. To do this, you will need tofind the DDE link setup area of the application that you intend to use as a client,specify Infilink as the application, the name of a Tag Group as the topic and thename of a tag in the Tag group as the item.

Let's use Microsoft Excel as an example. Assume you want to get the data for aTag group called "FlowInfo" and a tag called "FlowRate" and store it in cell locationA5. You would place the cursor in cell A5 and enter the formula: =Infilink|FlowInfo!FlowRateNow whenever the value of FlowRate changes, the text in cell A5 will be updated.

If FlowRate is defined as a Read/Write tag, you could write an Excel macro to"Poke" a new value to FlowRate. This macro might appear as follows:

Sub PokeFlowRate()Dim rangetopokeDim channelchannel = Application.DDEInitiate("Infilink", "FlowInfo")Set rangetopoke = Worksheets("Sheet1").Cells(1, 5)Application.DDEPoke channel, "FlowRate", rangetopokeApplication.DDETerminate channel

End Sub

Page 251: Infilink HMI

Copyright © 2003 KEP, Inc. Using OPC and DDE • 239

MS Excel as a DDE Server

Tag Group setupTo identify Microsoft Excel as a local DDE server you will define a DDE Tag Groupthat identifies Excel as the Server name and sheet1 as the Server topic.

If the copy of Excel that you want to use is on another PC connected to yournetwork the application would be \\<computer name>\ndde$ and the topicsheet1$. You will need to create a DDE share for sheet1$ so that it will berecognized by the NETDDE agent.

Tag AddressesTo address spreadsheet locations on sheet1 assign addresses of the form r#c#where the #'s would be replaced by the row and column of the cell you areinterested in. Be sure to enter your addresses using only lower case characters.

Page 252: Infilink HMI

Copyright © 2003 KEP, Inc. Security • 240

Security

OverviewThe purpose of this section is to explain Design and Run Mode Security optionsavailable with Infilink HMI.

Design Mode SecurityInfilink projects can be protected from unauthorized editing by assigning apassword. By default a project is not password protected.

To assign a password to a project that is not protected, the Current Password fieldshould be left blank. Otherwise, you will need to enter the password that iscurrently assigned prior to making any changes.

Note: There is no wayto access a passwordprotected project withoutthe password. If youforget your password,you will not be able toopen the project.

1. From the Project menu, select Properties... then click on the Password tab.

When entering a password for a project that is currently protected,

enter the Current Password then click OK.

2. When entering a new password for a project that is not currently protected,simply leave the Current Password empty. Enter up to six characters in the NewPassword field.

Page 253: Infilink HMI

Copyright © 2003 KEP, Inc. Security • 241

If you are a systemsintegrator and areresponsible forinstallation of Infilink anda completed Infilinkproject at a customer siteyou should passwordprotect the project toprevent unauthorizedediting. You will not beable to prevent designtime access to theproject any other waybecause Infilink DesignMode is available free ofcharge to anyone whovisits our web site.

3. Enter the same characters in the Confirm field.

4. Click OK. The new password will be assigned when the project is saved.

To remove the password from a project leave the New Password and Confirmfields blank. Click OK for both selections and the password will be removed whenthe project is saved.

Page 254: Infilink HMI

Copyright © 2003 KEP, Inc. Security • 242

Run Mode SecurityInfilink provides 256 user access levels. When Run Mode is initially started, theuser is set to NOUSER. This default name has an access level of 0. This defaultuser can only access windows and user triggered animations that have beenassigned an access level of 0.

To define a user with a higher access level you must log in with an access level atleast one level higher than the level you wish to assign.

When a user logs in, the system tags _User and _AccessLevel are updated toidentify the user name and assigned access level respectively.

If no users exist, thelogin menu is disabled. Logging in to a Project

Access to windows and user triggered animations is based on theaccess level of the logged in user. The system administratorassigns login names and access levels for an Infilink project. Thelogin dialog allows the operator to enter one of these names thusgaining access to the features of the current project. When theUser, Log In menu is selected the Log In dialog appears.

User NameType the name of a user that has been defined for the current project.

PasswordEnter the password that is assigned for the user name.

Click Ok to perform the login or Cancel to return with no further action.

Note:

- These buttons are used to call up a popup touchscreen or mouseaccessible keyboard when a physical keyboard is not attached to the unit.

Logging Out as a UserThe user can log out of the project by selecting Log Out from the User menu. Thisremoves the current user from the system access list and sets the access level to0.

Page 255: Infilink HMI

Copyright © 2003 KEP, Inc. Security • 243

Adding/Editing a User ListA project programmer may create or modify the list of users. User names andpasswords are not case sensitive and limited to sixteen characters.

The Project Properties dialog User List tab allows you to create and edit a list ofusers for your project.

Page 256: Infilink HMI

Copyright © 2003 KEP, Inc. Security • 244

User List Tools

Add a new User to the list. This tool calls up the User Properties dialog foryou to enter user information.

Creating a New User1. Type the Name of a user that has been defined for the current project.

2. Enter a brief but meaningful Description of this user.

3. Enter the Password (up to 16 characters) that is assigned for the user name.

4. Confirm the password by entering it again.

5. Set the Access level. This is the maximum level that this user will be allowedto access.

6. Check if you want the user to have access to this project's run-time tag datavia the Internet using the iViewer utility.

Note: Infilink software must be licensed for iViewer access before this feature canbe used. If this box is checked without the software being licensed, a windowdisplaying an error message will appear when entering Run mode.

Edit an existing user's properties using the User Properties dialog.

Delete a User from the list.

Minimum user level to allow move licenseAssigns an Access level that will allow the user to transfer the Infilink license fromone computer to another. We recommend setting this level high.

Page 257: Infilink HMI

Copyright © 2003 KEP, Inc. iViewer Utility • 245

iViewer Utility

OverviewThe iViewer utility is available through KEP's website. (www.kep.com). It is used todisplay screen captures and tag data at a remote location via the Internet. Tagsassigned Internet Read/Write permission can be changed; provided the user hasan appropriate Access level.

Note: The Infilink package must be licensed to allow Internet access. Use theUpgrade License procedure to add Internet capability.

Page 258: Infilink HMI

Copyright © 2003 KEP, Inc. iViewer Utility • 246

Connecting to a remote PC

Getting Started

Before using iViewer there are some things that need to be done:• Make sure the copy of Infilink on the remote PC is licensed for remote iViewer

access.

• Make sure the Project Properties Internet tab has "Enable tag value accessover internet" enabled.

• Make sure the Project Properties, User List tab, has a user defined and thatthe user has "Allow access using iViewer" enabled.

• Make sure that both computers have internet connections.

• Find out the URL (or IP) address of the remote PC that you are trying toaccess.

@ Design Tip: The IP address of a PC can be determined by running "ipconfig"from the command line or DOS prompt.

ConnectingStart up iViewer and select Connect from the Action Menu.• Enter the Remote PC's URL (or IP) address.

• Enter A valid User Name and password.

• Click on the "Connect to server button"

iViewer should connect to the Remote PC and display all of the tags designatedfor internet viewing.

DisconnectSelect Disconnect from the Action menu to end the communications link to theremote Server.

Page 259: Infilink HMI

Copyright © 2003 KEP, Inc. iViewer Utility • 247

ServerThe Server is the remote PC that is running Infilink. Enter the URL (or IP) addressof the remote PC in this field.

PortThe port address of the PC that is running iViewer. 9000 is the default for mostPC's. if your PC has more than one Port address put the appropriate number ofthe port in this field.

User name and PasswordEnter the name of a User from the project User List that has Internet accessenabled. Enter the corresponding password for that user in the Password field.

Enable the check box to remember this User and Password the next time youattempt to connect to the Server.

Page 260: Infilink HMI

Copyright © 2003 KEP, Inc. iViewer Utility • 248

iViewer SetupUse the Setup menu to modify how iViewer displays screen shots and taginformation. You can also set up a list of frequently accessed URL's.

iViewer Setup Dialog

Page 261: Infilink HMI

Copyright © 2003 KEP, Inc. iViewer Utility • 249

Adding/Editing a Server

Server nameEnter a familiar name for the remote PC acting as a Server.

DescriptionEnter a brief and meaningful description of the Server.

URLEnter the URL (or IP) address of the Server. The URL is typically given as<Computer name>.<company name> com.

PortThe port address of the PC that is running iViewer. 9000 is the default for mostPC's. if your PC has more than one Port address put the appropriate number ofthe port in this field.

Screen ShotsiViewer can get a screen shot of the remote PC’s display. Use the Action menuGet Screen shot menu item to get a one-time screen shot. Infilink must not beminimized on the remote PC. Sheen shots can be done automatically by makingthe proper settings in the iViewer Setup Dialog.

Check the box to enable automatic retrieval of screen shots from the Server.If the box is not checked, screen shots can still be done manually using theGet Screen shot menu item from the Action Menu.

Set the interval at which screen shots are to be taken. Internet connectionspeed should be taken into consideration when making this selection. Thetime to the next screen shot is displayed in the Status Bar.

@ Design Tip: Do a screen shot manually first and time how long it takesthe screen shot to arrive. Make sure that the minutes setting is longerthan the time it takes to actually get a screen shot.

Page 262: Infilink HMI

Copyright © 2003 KEP, Inc. iViewer Utility • 250

iViewer Tag DisplayThe tags in the project that have Internet read or write capabilities are available forviewing with iViewer. From this list the user can select the tags to be displayed inthe Tag values dialog by using the Setup|Tag List menu item.

Tags that are in an alarm condition are highlighted with the alarm type displayed inthe Alarm column.

To hide or show the Tag list, make select the Tags menu item from the Viewmenu.

If write ability has been assigned to the tag and the user access level for the tag isless than the user level of the iViewer user, the tag's value can be changed.Double click on the tag name in the Tag values dialog. The dialog shown below

pops up. Enter the new value for the tag and click the button. If the value entered is valid, the new value will be displayed in the Tagvalues dialog.

Page 263: Infilink HMI

Copyright © 2003 KEP, Inc. iViewer Utility • 251

Modifying the Tag list displaySelect the Setup|Tag List menu item to call up the Select tags to view dialog.Check the boxes of the Tag groups and Tags you would like to be displayed in the

Tag Values window. Click when you are done.

iViewer Status BarThe status bar can be enabled (View menu item is checked) or disabled byselection.

The status bar shows the state of iViewer (Ready), the time until the next ScreenShot (NSS) and the URL (or IP) address of the Server (Connected to:).

Page 264: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 252

Automatically Running a Project

OverviewThe KEPServerEX is a32 bit product andcannot run on Windows3.x.

In this section we will show you how to setup Infilink and the KEPServerEX to startrunning a project automatically when your PC is started, or when selecting ashortcut or program item.

Page 265: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 253

Windows 95/98Making Infilink Auto Start in Win 95/98

1. Locate the Startup folder and create a new shortcut. The Startup folder isaccessed by right clicking the Windows Start button and selecting Open fromthe popup menu. You then double click the Programs folder icon from thedisplayed Start Menu folder to display the Programs folder. You then doubleclick the Startup folder icon to display the Startup folder contents. You thenselect the File menu and choose New and Shortcut to start the Shortcutwizard.

2. Use the Browse button on the displayed Create Shortcut dialog to findRunMode.exe. Your command line should look something like“c:\Infilink\RunMode.exe”.

3. Click Next and give your new Shortcut a name.

4. Right click on the new Shortcut and select properties from the popup shortcutmenu.

5. Now append a space, quotation marks, the path to the project you wish toload, the words 'project.hmi', and close the quotes. (ie."c:\Infilink\proj1\project.hmi"). All together it should look something like:

"c:\Infilink\RunMode.exe" "c:\Infilink\proj1\project.hmi".

Page 266: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 254

Infilink requires you toprovide the full path tothe directory where theproject is located. It alsorequires the Working orStart in directory wherethe Infilink executablesare located.

6. Click OK to complete the shortcut. The Infilink Runtime icon should appear inthe StartUp folder with the name that you chose in step 4.

7. Restart Windows to test your shortcut.

Page 267: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 255

Making KEPServerEX Auto Start in Win 95/98Now we'll setup the KEPServerEX to start automatically.1. Use Windows Explorer to find the ServerMain.exe application in the

KEPServerEX folder.2. Open the startup folder as described above. Drag ServerMain.exe to the

Startup folder. This creates a new shortcut in the startup folder toServerMain.exe. You can rename the shortcut as you would any otherwindows file.

3. Right click on the new Shortcut and select Properties… from the shortcutmenu.

4. Select the Shortcut tab.

Quotes (") are neededbecause of the spacebetween Program andFiles in the path.

5. The Target will be as follows:"C:\Program Files\KEPServerEX\ServerMain.exe” /run myproject.kdp

6. The Start in directory will be the directory in which the server project is saved:"C:\Program Files\KEPServerEX\Projects "

7. In the Run list box select Minimized.

Page 268: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 256

8. Click Apply to accept the shortcut and click OK to exit the dialog.

Page 269: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 257

Windows NTMaking Infilink Auto Start in Win NTThe only difference between setting up shortcuts in Windows NT and Windows95/98 is that Windows NT has an extra tab for share permissions. The default isfor everyone to have access.

1. Drag the Infilink RunMode from the Infilink Products folder to the Startup folder.This creates a shortcut to RunMode.exe.

2. Right mouse click on the new shortcut and select Properties… from theshortcut menu.

3. By default, the dialog will default to general properties. Select the Shortcuttab.

4. In shortcuts, the Target will be the same the Command Line we used in theWindows 95/98 example. You will have the full path to the Infilink executablefollowed by a space and the full path to the project directory. For example:D:\INFILINK\RunMode.EXE c:\project1\.

5. The Start in directory will be the path to the folder where RunMode.exe islocated. For example: D:\Infilink.

Page 270: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 258

6. Click Apply to accept the shortcut and click OK to exit the dialog.

Page 271: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 259

Making KEPServer Auto Start in Win NTNow we'll setup the KEPServerEX to start automatically.7. Drag ServerMain.exe from the KEPware Product folder to the Startup folder.

This creates a shortcut to ServerMain.exe.

8. Select Properties… from the shortcut menu.

9. Select the Shortcut tab.

Quotes (") are neededbecause of the spacebetween Program andFiles in the path.

10. For example the Target will be as follows: "D:\Program Files\KEPware\ServerMain.exe" /run myproject.kdp

11. The Start in directory will be the directory in which the server project is saved:"D:\Program Files\KEPware\Projects"

12. In the Run list box select Minimized.

Page 272: Infilink HMI

Copyright © 2003 KEP, Inc. Automatically Running a Project • 260

13. Click Apply to accept the shortcut and click OK to exit the dialog.

Page 273: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-1

Appendix A: Library Objects

LIBRARY FILE: 2D_ISA_1

Page 274: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-2

LIBRARY FILE: 2D_ISA_2

Page 275: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-3

LIBRARY FILE: 2D_ISA_3

Page 276: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-4

LIBRARY FILE: 3D_ISA_1

Page 277: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-5

LIBRARY FILE: 3D_ISA_2

Page 278: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-6

LIBRARY FILE: 3D_ISA_3

Page 279: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-7

LIBRARY FILE: AIRCOND1

Page 280: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-8

LIBRARY FILE: AIRCOND2

Page 281: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-9

LIBRARY FILE: AIRCOND3

Page 282: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-10

LIBRARY FILE: ALARMHST

Page 283: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-11

LIBRARY FILE: ARROWS

Page 284: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-12

LIBRARY FILE: BITMAPS1

Page 285: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-13

LIBRARY FILE: BITMAPS2

Page 286: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-14

LIBRARY FILE: BITMAPS3

Page 287: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-15

LIBRARY FILE: BUTTONS1

Page 288: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-16

LIBRARY FILE: BUTTONS2

Page 289: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-17

LIBRARY FILE: BUTTONS3

Page 290: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-18

LIBRARY FILE: BUTTONS4

Page 291: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-19

LIBRARY FILE: BUTTONS5

Page 292: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-20

LIBRARY FILE: BUTTONS6

Page 293: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-21

LIBRARY FILE: COMPUTER

Page 294: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-22

LIBRARY FILE: CONTROLR

Page 295: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-23

LIBRARY FILE: DATADISP

Page 296: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-24

LIBRARY FILE: DIALS1

Page 297: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-25

LIBRARY FILE: DIALS2

Page 298: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-26

LIBRARY FILE: DUCTS

Page 299: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-27

LIBRARY FILE: ELECTRC1

Page 300: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-28

LIBRARY FILE: ELECTRC2

Page 301: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-29

LIBRARY FILE: FACILITY

Page 302: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-30

LIBRARY FILE: FLEXTUBE

Page 303: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-31

LIBRARY FILE: FLOWMTRS

Page 304: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-32

LIBRARY FILE: GENERMFG

Page 305: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-33

LIBRARY FILE: HEATING1

Page 306: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-34

LIBRARY FILE: HEATING2

Page 307: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-35

LIBRARY FILE: INDICATR

Page 308: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-36

LIBRARY FILE: INTLSYMS

Page 309: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-37

LIBRARY FILE: MAPSFLAG

Page 310: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-38

LIBRARY FILE: MATHANDL

Page 311: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-39

LIBRARY FILE: METERS1

Page 312: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-40

LIBRARY FILE: METERS2

Page 313: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-41

LIBRARY FILE: METERS3

Page 314: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-42

LIBRARY FILE: METERS4

Page 315: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-43

LIBRARY FILE: MISCSYM1

Page 316: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-44

LIBRARY FILE: MISCSYM2

Page 317: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-45

LIBRARY FILE: MISCSYM3

Page 318: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-46

LIBRARY FILE: MISCSYM4

Page 319: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-47

LIBRARY FILE: MIXERS

Page 320: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-48

LIBRARY FILE: MOTORS

Page 321: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-49

LIBRARY FILE: NATURE

Page 322: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-50

LIBRARY FILE: OP_INTFC

Page 323: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-51

LIBRARY FILE: PIPES1

Page 324: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-52

LIBRARY FILE: PIPES2

Page 325: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-53

LIBRARY FILE: PIPES3

Page 326: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-54

LIBRARY FILE: POWER

Page 327: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-55

LIBRARY FILE: PROCESS

Page 328: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-56

LIBRARY FILE: PUMPS

Page 329: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-57

LIBRARY FILE: SAFETY

Page 330: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-58

LIBRARY FILE: SENSORS

Page 331: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-59

LIBRARY FILE: SHAPES1

Page 332: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-60

LIBRARY FILE: SHAPES2

Page 333: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-61

LIBRARY FILE: SLIDERS1

Page 334: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-62

LIBRARY FILE: SLIDERS2

Page 335: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-63

LIBRARY FILE: SLIDERS3

Page 336: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-64

LIBRARY FILE: SLIDERS4

Page 337: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-65

LIBRARY FILE: SYSCMDS

Page 338: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-66

LIBRARY FILE: TANKCUTS

Page 339: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-67

LIBRARY FILE: TANKS1

Page 340: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-68

LIBRARY FILE: TANKS2

Page 341: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-69

LIBRARY FILE: TIMEDATE

Page 342: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-70

LIBRARY FILE: TRENDHST

Page 343: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-71

LIBRARY FILE: VALVES

Page 344: Infilink HMI

Copyright © 2004 KEP, Inc. Appendix A: Library Objects • A-72

LIBRARY FILE: VEHICLES

Page 345: Infilink HMI

Copyright © 2004 KEP, Inc. Technical Support • B-1

TTeecchhnniiccaall SSuuppppoorrttKessler-Ellis ProductsPhone 800-621-2165 or 732-935-1320 extension 332Website www.kep.comLicensing website http://infilock.kep.comEmail [email protected]

KEP technical support by telephone or email is free.

Information KEP will generally need to provide the best possible technical support includes:• Version of Infilink (Help / About)• If the problem is related to licensing, we will need serial number, website login code, or at least the

approximate date of purchase and the name of the distributor.• Company name and phone number.• Your email address.• A description of the problem.

New Features:KEP values user input on what features should be added to the product. Please contact us with any ideas youhave which can make our product more useful to you.

Updates:Would you like to know when Infilink-HMI updates are available? I suggest that you signup for KEP’s e-newsletter. You can signup on www.kep.com, or by emailing [email protected].

Thank you for your support of Infilink-HMI.

--The Infilink-HMI Team.