RSView SE Users PDF
RSView SE Users PDF
RSView SE Users PDF
User’s Guide
Doc ID VIEWSE-UM003C-EN-E
Contacting Technical Support Telephone—440-646-5800
Rockwell Software Technical Support Fax—440-646-5801
World Wide Web Support—www.software.rockwell.com or
www.support.rockwellautomation.com
Copyright Notice © 2003 Rockwell Software Inc., a Rockwell Automation company. All rights reserved.
Printed in the United States of America.
Portions copyrighted by the Allen-Bradley Company, LLC, a Rockwell Automation Company.
This manual and any accompanying Rockwell Software products are copyrighted by Rockwell
Software Inc. Any reproduction and/or distribution without prior written consent from
Rockwell Software Inc. is strictly prohibited. Please refer to the license agreement for details.
VBA and DCOM, Copyright 1996, 1997 Microsoft Corporation. All rights reserved.
Trademark Notices WINtelligent Series is a registered trademark. The Rockwell Software logo, RSAssistant,
RSBatch, RSData, RSEmulate 5, RSEmulate 500, RSGuardian, RSHarmony, RSKeys, RSLinx,
RSLogix 5, RSLogix 500, RSPower, RSPowerCFG, RSPowerRUN, RSServer32, RSServer,
RSServer Toolkit, RSSql, RSToolbox, RSTrainer, RSTrend, RSTune, RSView32, RSView32
Resource Kit, RSView, RSWire, A.I. Series, Advanced Interface (A.I.) Series, AdvanceDDE,
ControlGuardian, ControlView, INTERCHANGE, Object Smart Path, Packed DDE,
PLC-500, WINtelligent, WINtelligent EMULATE 5, WINtelligent EMULATE 500,
WINtelligent LOGIC 5, WINtelligent VIEW, WINtelligent RECIPE, WINtelligent VISION,
and WINtelligent VISION2 are trademarks of Rockwell Software Inc.
PLC, PLC-2, PLC-3, and PLC-5 are registered trademarks, and Data Highway Plus, DH+, DHII,
DTL, Network DTL, Pyramid Integrator, PanelBuilder, PanelView, PLC-5/250, PLC-5/20E,
PLC-5/40E, PLC-5/80E, SLC, SLC 5/01, SLC 5/02, SLC 5/03, SLC 5/04, SLC 5/05, SLC 500,
ControlLogix 5550, and SoftLogix are trademarks of the Allen-Bradley Company, Inc.
Microsoft, MS-DOS, Windows, FoxPro, and Visual Basic are registered trademarks, and
Windows NT, ActiveX, and Microsoft Access are trademarks of the Microsoft Corporation.
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox
Corporation. IBM is a registered trademark of International Business Machines Corporation.
AIX, PowerPC, Power Series, and RISC System/6000 are trademarks of International Business
Machines Corporation. Adobe and Photoshop are registered trademarks of Adobe Systems
Incorporated. AutoCAD is a registered trademark of Autodesk, Inc. CorelDRAW is a trademark
of Corel Corporation. Seagate Crystal Reports is a trademark of Seagate Technology, Inc. or one
of its subsidiaries. Intel and Pentium are registered trademarks of Intel Corporation. OPC is a
trademark of the OPC Foundation. UNIX is a registered trademark in the United States and
other countries, licensed exclusively through X/Open Company Limited.
All other trademarks are the property of their respective holders and are hereby acknowledged.
Warranty This Rockwell Software product is warranted in accord with the product license. The product’s
performance will be affected by system configuration, the application being performed, operator
control, and other related factors.
The product’s implementation may vary among users.
This manual is as up-to-date as possible at the time of printing; however, the accompanying
software may have changed since that time. Rockwell Software reserves the right to change any
information contained in this manual or the software at any time without prior notice.
The instructions in this manual do not claim to cover all the details or variations in the
equipment, procedure, or process described, nor to provide directions for meeting every possible
contingency during installation, operation, or maintenance.
Doc ID VIEWSE-UM003C-EN-E
September 2003
Contents
Preface ................................................................................................................................................... P-1
About the documentation ............................................................................ P-1
Finding the information you need .......................................................... P-2
Try the user’s guides and Help first .......................................................................... P-2
Information on the Internet....................................................................................... P-2
Contacting Rockwell Software Technical Support ................................................. P-3
Chapter 1
Getting started ...............................................................................................................................1-1
The main parts of RSView Supervisory Edition ........................... 1-1
Features in brief ................................................................................................. 1-3
The RSView Enterprise tools .................................................................... 1-4
The Rockwell Software utilities ............................................................. 1-5
Quick Start steps ............................................................................................... 1-6
Start with a plan ........................................................................................................... 1-6
Chapter 2
Exploring RSView Studio ...................................................................................................2-1
Starting RSView Studio ................................................................................. 2-1
Opening an application ................................................................................. 2-2
Running the samples application............................................................................... 2-4
Exploring the RSView Studio main window ................................... 2-4
The menu bar ............................................................................................................... 2-5
The toolbar ................................................................................................................... 2-5
The Application Explorer........................................................................................... 2-5
The workspace ............................................................................................................. 2-5
Contents Q
i
The Application tab......................................................................................................2-5
The Communications tab............................................................................................2-6
The Diagnostics List ....................................................................................................2-6
The status bar ................................................................................................................2-7
Showing and hiding items in the main window .......................................................2-8
Working in the Application Explorer .....................................................2-8
Undocking the Application Explorer ........................................................................2-9
Folders......................................................................................................................... 2-10
Editors......................................................................................................................... 2-10
Components ............................................................................................................... 2-13
Adding components to an application ............................................. 2-14
ii Q
RSView Supervisory Edition User’s Guide
Chapter 3
Planning an application .......................................................................................................3-1
Understanding the process ........................................................................ 3-1
Contents Q
iii
Chapter 4
Setting up FactoryTalk Directory .............................................................................4-1
Chapter 5
Working with distributed applications ...............................................................5-1
iv Q
RSView Supervisory Edition User’s Guide
Basic steps for developing an application .................................... 5-12
Contents Q
v
Chapter 6
Working with stand-alone applications .............................................................6-1
Key concepts.........................................................................................................6-1
Understanding terminology.........................................................................................6-1
About stand-alone applications ..................................................................................6-1
About data-server redundancy....................................................................................6-2
Using references in stand-alone applications ...........................................................6-2
Basic steps for developing an application .......................................6-3
Activities when deploying an application.........................................6-3
Creating an application..................................................................................6-4
Importing a project into a new application .....................................6-5
Renaming an application ..............................................................................6-6
Deleting an application ..................................................................................6-7
Using data servers in stand-alone applications ...........................6-7
Setting up HMI server properties ...........................................................6-8
Setting up the HMI server’s general properties.......................................................6-9
Specifying the HMI server’s startup and shutdown components ..................... 6-10
Starting and stopping an HMI server’s components
manually ................................................................................................................. 6-12
Chapter 7
Setting up communications ............................................................................................7-1
vi Q
RSView Supervisory Edition User’s Guide
Adding OPC data servers ............................................................................ 7-7
Setting up general properties...................................................................................... 7-8
Setting up data server redundancy ............................................................................ 7-9
Setting up advanced properties................................................................................ 7-10
Adding RSLinx Enterprise data servers........................................... 7-12
Setting up general properties.................................................................................... 7-13
Setting up data server redundancy .......................................................................... 7-14
Setting up communications in RSLinx Enterprise ................... 7-15
Primary and Secondary tabs ..................................................................................... 7-15
Removing data servers ................................................................................ 7-17
Chapter 8
Working with tags.......................................................................................................................8-1
Tags and the HMI tag database ............................................................. 8-1
Data server tags, HMI tags, and their attributes..................................................... 8-1
Basic steps for using tags ............................................................................................ 8-3
When to use data server tags ................................................................... 8-4
Eliminate duplication .................................................................................................. 8-4
Access to complex data............................................................................................... 8-4
Steps for using data server tags ............................................................ 8-4
When to use HMI tags .................................................................................... 8-5
Alarms............................................................................................................................ 8-5
Security .......................................................................................................................... 8-5
Data manipulation ....................................................................................................... 8-6
Storing values in RSView’s memory ......................................................................... 8-7
Steps for using HMI tags ............................................................................. 8-7
Browsing for tags .............................................................................................. 8-8
Browsing for off-line tags from RSLinx ............................................ 8-10
Browsing for off-line tags from other OPC servers ................. 8-10
Using the tag browser .................................................................................. 8-11
Contents Q
vii
Working with folders in the tag browser ........................................ 8-12
Showing server names............................................................................................... 8-12
Adding folders............................................................................................................ 8-12
Finding the home area .............................................................................................. 8-13
Refreshing the list of folders and tags .................................................................... 8-14
Working with tags in the tag browser .............................................. 8-14
Displaying tags ........................................................................................................... 8-14
Showing or hiding tag descriptions......................................................................... 8-14
Selecting tags .............................................................................................................. 8-15
Using the selected tags list........................................................................................ 8-15
Displaying tag properties.......................................................................................... 8-17
Filtering tags ............................................................................................................... 8-17
Creating, editing, and importing HMI tags ........................................................... 8-18
Using tag references .................................................................................... 8-19
Absolute references ................................................................................................... 8-19
Relative references..................................................................................................... 8-19
The home area............................................................................................................ 8-20
Logging tag values ......................................................................................... 8-21
Chapter 9
Creating HMI tags ......................................................................................................................9-1
HMI tag types .......................................................................................................9-1
Data sources for HMI tags .........................................................................9-2
Device.............................................................................................................................9-2
Memory ..........................................................................................................................9-2
Retentive memory tags ................................................................................................9-2
Organizing HMI tags ........................................................................................9-3
Naming HMI tags ........................................................................................................9-3
Using folders to group HMI tags ..............................................................................9-4
The Tags editor ....................................................................................................9-4
viii Q
RSView Supervisory Edition User’s Guide
Using the Accept and Discard buttons .............................................. 9-5
Contents Q
ix
Importing tags from a PLC database...................................................................... 9-22
Using the Tag Import and Export Wizard ............................................................ 9-24
Adding alarms to HMI tags ...................................................................... 9-25
Chapter 10
Creating derived tags...........................................................................................................10-1
How to use derived tags ........................................................................................... 10-1
How to use multiple derived tag components ...................................................... 10-2
Summary of steps ........................................................................................... 10-2
The Derived Tags editor ............................................................................. 10-2
Using the Check Syntax button............................................................................... 10-3
Using the Accept and Discard buttons .................................................................. 10-4
Setting the maximum update rate ...................................................... 10-4
Creating derived tags ................................................................................... 10-5
Editing derived tags....................................................................................... 10-6
Starting and stopping derived tag processing ........................... 10-7
Ways to start derived tag processing....................................................................... 10-7
Ways to stop derived tag processing....................................................................... 10-8
Chapter 11
Setting up alarms......................................................................................................................11-1
Summary of features ..................................................................................... 11-1
Key concepts...................................................................................................... 11-2
Alarms for analog HMI tags.................................................................................... 11-2
Alarms for digital HMI tags .................................................................................... 11-7
Alarm severity............................................................................................................. 11-7
Alarm messages.......................................................................................................... 11-8
Alarm log file.............................................................................................................. 11-8
Alarm displays ............................................................................................................ 11-9
Alarm acknowledgment .......................................................................................... 11-12
x Q
RSView Supervisory Edition User’s Guide
Alarm suppression ................................................................................................... 11-12
Alarm functions in expressions ............................................................................. 11-13
Acknowledge bit ...................................................................................................... 11-15
Handshake bit........................................................................................................... 11-16
Switching handshaking on...................................................................................... 11-17
Alarm events............................................................................................................. 11-17
Summary of steps.......................................................................................... 11-20
The Alarm Setup editor ............................................................................. 11-21
Specifying how the monitoring system behaves .................... 11-22
Setting up alarm trigger thesholds......................................................................... 11-22
Specifying how often the system checks for alarms........................................... 11-23
Specifying how alarm monitoring behaves on redundant servers.................... 11-23
Setting up alarm severity ........................................................................ 11-24
Setting up alarm messages.................................................................... 11-26
Types of messages ................................................................................................... 11-27
Defining the content of the message.................................................................... 11-27
Adding remarks to the alarm log file at run time ................... 11-30
Specifying alarm conditions for analog and digital tags .. 11-31
When to set up alarms for tags .............................................................................. 11-32
Setting up alarms for analog tags ..................................................... 11-32
Setting up alarm thresholds.................................................................................... 11-32
Setting up alarm messages ...................................................................................... 11-34
Setting up advanced features.................................................................................. 11-35
Setting up alarms for digital tags ...................................................... 11-37
Setting up alarm states............................................................................................. 11-37
Setting up alarm messages ...................................................................................... 11-39
Setting up advanced features.................................................................................. 11-40
Setting up alarm logging .......................................................................... 11-42
Specifying where to store alarm log files .................................... 11-44
Contents Q
xi
Creating log files............................................................................................ 11-45
Monitoring disk space............................................................................................. 11-45
Managing log files ......................................................................................... 11-46
Creating files periodically........................................................................................ 11-46
Creating files on demand........................................................................................ 11-47
Never creating new files ......................................................................................... 11-47
Deleting log files ............................................................................................ 11-48
Logging to a central database ............................................................. 11-49
Exporting alarm log files manually to ODBC format....................................... 11-51
Editing alarm log setup ............................................................................. 11-52
Setting up security to allow alarm logging to a
remote computer ........................................................................................... 11-53
About alarm log files ................................................................................... 11-55
How log files are named ......................................................................................... 11-55
Viewing alarm log files .............................................................................. 11-56
Using the alarm log viewer at run time ................................................................ 11-57
Creating an alarm summary .................................................................. 11-57
Creating an alarm summary object........................................................................ 11-58
The parts of an alarm summary............................................................................. 11-58
Inserting headings.................................................................................................... 11-59
Choosing fonts......................................................................................................... 11-61
Choosing colors and blink styles........................................................................... 11-61
Formatting buttons.................................................................................................. 11-63
Choosing data........................................................................................................... 11-67
Filtering data............................................................................................................. 11-67
Sorting data............................................................................................................... 11-73
Running commands, macros, or custom programs in response to alarms..... 11-74
Using alarm data with commands ......................................................................... 11-77
Viewing the area name in tag names..................................................................... 11-80
xii Q
RSView Supervisory Edition User’s Guide
Suppressing alarm printing .................................................................... 11-81
Using AlarmOn and AlarmPrintOff in the correct order ................................. 11-81
Suppressing alarm monitoring ............................................................. 11-81
Suppressing alarm monitoring for tags................................................................. 11-82
Viewing suppressed tags ......................................................................................... 11-82
Using the Suppressed List ...................................................................................... 11-83
More RSView commands....................................................................................... 11-83
Starting and stopping alarm monitoring ....................................... 11-83
Ways to start alarm monitoring at the HMI server............................................ 11-84
Ways to stop alarm monitoring ............................................................................. 11-85
Chapter 12
Logging system activity ................................................................................................... 12-1
Contents Q
xiii
Using the Diagnostics List...................................................................... 12-17
Hiding, showing, and moving the Diagnostics List ........................................... 12-18
Messages in the Diagnostics List........................................................................... 12-19
Viewing FactoryTalk Diagnostics log files ................................. 12-19
Using the Diagnostics Viewer at run time ........................................................... 12-20
Chapter 13
Setting up data logging ......................................................................................................13-1
xiv Q
RSView Supervisory Edition User’s Guide
Creating file sets ........................................................................................... 13-21
Changing log paths using the RSView Administration Console ...................... 13-36
Contents Q
xv
Chapter 14
Chapter 15
Setting up security ..................................................................................................................15-1
xvi Q
RSView Supervisory Edition User’s Guide
Securing commands and macros ....................................................... 15-11
Security codes ........................................................................................................... 15-12
The Unspecified_Command .................................................................................. 15-12
Setting up security by inclusion ............................................................................. 15-13
Setting up security by exclusion............................................................................. 15-13
Assigning security to a graphic display ........................................ 15-14
Assigning security to an OLE object ............................................... 15-16
Assigning security to an HMI tag ...................................................... 15-17
Preventing users from modifying an application .................... 15-19
Locking users into the RSView SE Client environment ..... 15-20
Logging in at run time ................................................................................ 15-21
Logging out at run time ............................................................................. 15-21
Changing passwords at run time ....................................................... 15-22
Chapter 16
Creating graphic displays .............................................................................................. 16-1
About graphic displays and graphic objects ............................... 16-1
The Graphic Displays editor .................................................................... 16-2
The parts of the editor .............................................................................................. 16-3
Mastering basic techniques ..................................................................... 16-5
Correcting mistakes ................................................................................................... 16-5
Zooming in and out................................................................................................... 16-5
Using the grid ............................................................................................................. 16-6
Using the toolbars...................................................................................................... 16-7
Selecting a drawing tool ............................................................................................ 16-8
Testing graphic displays ............................................................................................ 16-9
Working with objects ................................................................................................ 16-9
Selecting and deselecting objects........................................................................... 16-10
Using the Object Explorer ..................................................................................... 16-11
Highlighting objects in the Object Explorer ....................................................... 16-13
Contents Q
xvii
Using the context menu.......................................................................................... 16-15
Moving objects......................................................................................................... 16-15
Copying objects........................................................................................................ 16-16
Duplicating objects.................................................................................................. 16-18
Resizing objects........................................................................................................ 16-19
Arranging objects..................................................................................................... 16-20
Stacking objects........................................................................................................ 16-21
Aligning objects ....................................................................................................... 16-22
Spacing objects......................................................................................................... 16-24
Flipping objects........................................................................................................ 16-25
Rotating objects ....................................................................................................... 16-26
Grouping and ungrouping objects........................................................................ 16-28
Editing grouped objects.......................................................................................... 16-29
Applying colors ........................................................................................................ 16-31
Applying pattern styles............................................................................................ 16-32
Changing line properties......................................................................................... 16-33
Using the Property Panel........................................................................................ 16-34
Setting up properties ............................................................................................... 16-35
Assigning tags and expressions to objects ........................................................... 16-38
Using tag substitution to replace text associated with objects.......................... 16-39
Testing the appearance of objects in different states......................................... 16-42
Naming graphic objects .......................................................................................... 16-43
Adding tooltips to objects ...................................................................................... 16-43
Creating a background for your display ............................................................... 16-45
Importing graphic files from third-party applications ......... 16-46
Converting imported objects to RSView native objects.................................... 16-47
Using bitmaps .................................................................................................. 16-47
When a bitmap could help ..................................................................................... 16-49
Using graphic libraries .............................................................................. 16-49
Location of library files........................................................................................... 16-49
xviii Q
RSView Supervisory Edition User’s Guide
Using tag placeholders ............................................................................. 16-51
Replacing tag placeholders using a parameter file .............................................. 16-52
Assigning parameter files to graphic displays...................................................... 16-54
Replacing tag placeholders using parameters to the Display command ......... 16-55
Contents Q
xix
Chapter 17
xx Q
RSView Supervisory Edition User’s Guide
Using the keyboard to navigate to, and select objects ..... 17-27
What input focus looks like.................................................................................... 17-27
Using the keys on the keyboard or keypad .......................................................... 17-28
Removing objects from the tab sequence............................................................ 17-28
How to use push buttons ......................................................................... 17-29
Setting up push buttons .......................................................................................... 17-31
How to use the States tab for push buttons ........................................................ 17-33
How to use the Connections tab for push buttons............................................ 17-34
How the Value tag works ....................................................................................... 17-35
How the Indicator tag works ................................................................................. 17-36
Creating push buttons ................................................................................ 17-37
Contents Q
xxi
Creating latched push buttons ............................................................ 17-65
Setting up the appearance of the latched push button,
and how to unlatch it .............................................................................................. 17-67
Setting up what the latched push button does
when it is latched and unlatched ........................................................................... 17-69
Connecting the latched push button to data ....................................................... 17-73
Creating multistate push buttons ...................................................... 17-74
Setting up the appearance of the multistate push button,
and how it changes state......................................................................................... 17-76
Setting up what the multistate push button does
when it is pressed and released.............................................................................. 17-79
Setting up whether the multistate push button repeats when held down....... 17-83
Connecting the multistate push button to data................................................... 17-84
Creating interlocked push buttons ................................................... 17-85
Setting up the appearance and value of the interlocked push button ............. 17-87
Setting up what the interlocked push button looks like
when it is pressed and released.............................................................................. 17-89
Connecting the interlocked push button to data ................................................ 17-93
Creating ramp push buttons .................................................................. 17-94
Setting up the appearance of the ramp push button, and how it works ......... 17-96
Setting up the text that appears on the ramp push button................................ 17-99
Setting up whether the ramp push button repeats when held down............. 17-102
Connecting the ramp push button to data......................................................... 17-103
Creating numeric or string fields ..................................................... 17-103
Creating numeric display fields............................................................................ 17-103
Creating string display fields ................................................................................ 17-105
Creating numeric or string input fields............................................................... 17-107
Using input fields at run time ............................................................. 17-113
Updating tag values continuously ....................................................................... 17-113
Keys ......................................................................................................................... 17-114
xxii Q
RSView Supervisory Edition User’s Guide
RSView commands................................................................................................ 17-115
Using the on-screen keyboard ............................................................................. 17-115
How to use indicators .............................................................................. 17-117
How to use the States tab for indicators ............................................................ 17-118
How to use Least Significant Bits to trigger states ........................................... 17-119
How to use the Connections tab for indicators................................................ 17-119
Creating multistate indicators ........................................................... 17-120
Setting up the appearance of the multistate indicator,
and its number of states........................................................................................ 17-122
Setting up how the multistate indicator’s appearance changes
to match its value ................................................................................................... 17-123
Connecting the multistate indicator to data....................................................... 17-128
Creating symbol indicators .................................................................. 17-128
Setting up the appearance of the symbol indicator,
and its number of states........................................................................................ 17-130
Setting up how the symbol indicator changes appearance
when its value changes .......................................................................................... 17-131
Connecting the symbol indicator to data ........................................................... 17-133
Creating list indicators ............................................................................ 17-134
Setting up the appearance of the list indicator,
and its number of states........................................................................................ 17-136
Setting up how the list indicator’s appearance changes
when its value changes .......................................................................................... 17-138
Connecting the list indicator to data................................................................... 17-140
How to use gauges and graphs ......................................................... 17-141
Gauges make it easy to see limits ........................................................................ 17-141
Graphs make it easy to compare values ............................................................. 17-142
How to use the Connections tab for gauges and graphs................................. 17-143
Creating gauges ........................................................................................... 17-144
Setting up the appearance of the gauge.............................................................. 17-146
Setting up how the gauge works.......................................................................... 17-148
Connecting the gauge to data............................................................................... 17-150
Contents Q
xxiii
Creating bar graphs ................................................................................... 17-150
Setting up the appearance of the bar graph....................................................... 17-152
Connecting the bar graph to data........................................................................ 17-154
Creating scales ............................................................................................. 17-154
Setting up the appearance of the scale ............................................................... 17-156
How to use keys ........................................................................................... 17-158
Using the Key objects ........................................................................................... 17-159
Keys can work with the object that has focus................................................... 17-160
Creating keys ................................................................................................. 17-160
Setting up the appearance of the key.................................................................. 17-162
Adding text or an image to the key..................................................................... 17-165
Setting up whether the key repeats when held down....................................... 17-168
Creating advanced objects .................................................................. 17-169
Objects described in other chapters ................................................................... 17-169
Creating arrows ............................................................................................ 17-170
How to use control list selectors .................................................... 17-172
Choosing between control list selectors
and piloted control list selectors.......................................................................... 17-172
How control list selectors work at run time ...................................................... 17-172
How to use the States tab for control list selectors.......................................... 17-173
How to use the Connections tab for control list selectors.............................. 17-174
Creating control list selectors ........................................................... 17-177
Setting up the appearance of the control list selector ...................................... 17-179
Setting up the control list selector’s value and appearance ............................. 17-182
Setting up the control list selector to work with an Enter key ....................... 17-184
Connecting the control list selector to data....................................................... 17-185
How to use piloted control list selectors................................... 17-186
Choosing between piloted control list selectors
and control list selectors ....................................................................................... 17-186
How piloted control list selectors work at run time......................................... 17-187
xxiv Q
RSView Supervisory Edition User’s Guide
How to use the States tab for piloted control list selectors ............................ 17-189
How to use the Connections tab for piloted control list selectors ................ 17-191
Creating piloted control list selectors ......................................... 17-194
Setting up the appearance of the piloted control list selector......................... 17-196
Setting up the piloted control list selector's state values and captions .......... 17-198
Setting up the piloted control list selector to work with an Enter key.......... 17-201
Connecting the piloted control list selector to data.......................................... 17-202
Creating tag labels ..................................................................................... 17-204
Contents Q
xxv
Creating and editing OLE objects ................................................... 17-238
Other methods for inserting OLE objects ....................................................... 17-240
Converting OLE objects...................................................................................... 17-240
Creating and editing ActiveX objects ........................................... 17-242
When exchanging data with tags, use the same data type ............................... 17-242
ActiveX properties, methods, and events .......................................................... 17-243
Making ActiveX objects interact with RSView ................................................. 17-244
Using VBA code to make ActiveX objects interact with RSView................. 17-245
Using the ActiveX Toolbox ................................................................................. 17-245
Deploying ActiveX components automatically
at run time ........................................................................................................ 17-247
Recording and authorizing run-time changes
using electronic signatures ................................................................. 17-248
Securing tag writes, commands, and downloads .............................................. 17-249
Securing objects in displays.................................................................................. 17-249
Tracking changes with FactoryTalk Diagnostics .............................................. 17-250
Using the Signature button for compliance with
regulated manufacturing applications ................................................................. 17-250
Creating Signature buttons .................................................................. 17-250
Specifying a caption for the Signature button................................................... 17-252
Setting up the run-time behavior of the Signature button .............................. 17-252
Specifying colors for the Signature button ........................................................ 17-255
Specifying a tag for the Signature button........................................................... 17-256
Changing the style and color of the font ........................................................... 17-256
Chapter 18
Animating graphic objects .............................................................................................18-1
Types of animation ......................................................................................... 18-1
Using the Animation dialog box ............................................................ 18-3
Using the Animation dialog box ............................................................................. 18-4
Using Object Smart Path to set animation visually .............................................. 18-6
xxvi Q
RSView Supervisory Edition User’s Guide
Testing animation ........................................................................................... 18-6
Using tag names and tag placeholders ........................................... 18-7
Tag names ................................................................................................................... 18-7
Tag placeholders ........................................................................................................ 18-7
Using commands and macros ................................................................ 18-8
Using expressions........................................................................................... 18-8
Setting the range of tag values
for animating the object ............................................................................. 18-9
Limiting the range of values used for animation ................................................ 18-10
Defining a range of motion for the object .................................... 18-11
Objects that do not have a range of motion........................................................ 18-11
Using OSP (Object Smart Path) ........................................................................... 18-11
Setting up visibility animation ............................................................. 18-13
Setting up color animation ..................................................................... 18-14
Using the colors and thresholds list...................................................................... 18-15
Setting up fill animation ........................................................................... 18-20
Setting up horizontal position animation ..................................... 18-22
Setting up vertical position animation ........................................... 18-23
Setting up width animation .................................................................... 18-25
Setting up height animation .................................................................. 18-27
Setting up rotation animation............................................................... 18-29
How rotation animation works.............................................................................. 18-29
Setting up touch animation .................................................................... 18-33
Setting up horizontal slider animation ........................................... 18-34
Setting up vertical slider animation................................................. 18-36
Setting up OLE verb animation ........................................................... 18-37
Attaching other types of animation to OLE objects ......................................... 18-38
Animating ActiveX controls ................................................................... 18-39
Naming an ActiveX object..................................................................................... 18-40
Contents Q
xxvii
Connecting tags to an ActiveX object’s properties.............. 18-40
Connecting tags to an object’s methods ..................................... 18-42
Viewing an object’s methods ................................................................................. 18-42
Using the Invoke command to call a method ..................................................... 18-43
Connecting tags to an ActiveX object’s events ...................... 18-44
Using VBA code to make ActiveX objects interact with RSView .................. 18-45
Associating objects and displays with keys ............................. 18-45
Creating object keys ................................................................................... 18-46
Using index numbers .................................................................................. 18-49
How tab index numbers work ............................................................................... 18-49
Checking an object’s index number...................................................................... 18-50
Changing index numbers........................................................................................ 18-51
Creating a tab sequence .......................................................................................... 18-52
Using the Current [Tag] parameter .................................................. 18-54
Summary of steps .................................................................................................... 18-54
Three examples ........................................................................................................ 18-55
Creating display keys ................................................................................. 18-60
Editing display and object keys .......................................................... 18-62
Modifying a key........................................................................................................ 18-63
Removing a key........................................................................................................ 18-63
Removing all keys .................................................................................................... 18-63
Viewing the key list at run time.......................................................... 18-64
Disabling the key list ............................................................................................... 18-65
Applying animation to groups............................................................... 18-65
Checking the animation on objects ................................................. 18-65
Checking animation using the menu, or the Animation dialog box ................ 18-66
Changing the animation on objects ................................................. 18-67
Copying or duplicating objects with animation ....................... 18-67
Copying animation without copying objects ............................. 18-68
xxviii Q
RSView Supervisory Edition User’s Guide
Chapter 19
Setting up trends ...................................................................................................................... 19-1
Contents Q
xxix
Saving trend data to the data buffer ..................................................................... 19-20
Overlaying a snapshot of previously-charted data.............................................. 19-21
Setting up the trend display settings ............................................. 19-22
Displaying a current value legend ......................................................................... 19-24
Displaying a line legend .......................................................................................... 19-25
Determining how the trend chart is filled with data .......................................... 19-27
Adding pens to the trend ......................................................................... 19-29
Adding a pen from a data log model .................................................................... 19-30
Deleting a pen from the trend ............................................................................... 19-32
Setting up pen attributes......................................................................................... 19-32
Editing multiple pens simultaneously................................................................... 19-37
Plotting tag limits..................................................................................................... 19-38
Using shading to compare pens ............................................................................ 19-38
Setting up the horizontal axis (x-axis) ........................................... 19-43
Setting up the x-axis display options .................................................................... 19-44
Setting up the vertical axis (y-axis) ................................................. 19-45
Defining the minimum and maximum values on the vertical axis................... 19-46
Setting up the Y-Axis display options .................................................................. 19-48
Setting up the vertical scale for multiple pens..................................................... 19-49
Comparing real-time and historical data ...................................... 19-50
Setting up snapshots and overlays .................................................. 19-51
Deleting snapshots .................................................................................................. 19-53
Changing the attributes of a snapshot pen .......................................................... 19-53
Setting up overlays................................................................................................... 19-53
Creating a trend template ....................................................................... 19-56
Applying a consistent appearance to trend charts .............................................. 19-56
Creating a set of different views for the same data ............................................ 19-56
Returning to a standard display ............................................................................. 19-56
Saving pen attribute data ........................................................................................ 19-57
Creating and saving a new template...................................................................... 19-57
xxx Q
RSView Supervisory Edition User’s Guide
Loading a template .................................................................................................. 19-59
Deleting a template.................................................................................................. 19-59
Loading a template at run time.............................................................................. 19-59
Setting up the trend’s run-time options......................................... 19-60
Displaying property pages at run time.................................................................. 19-61
Setting up chart behavior........................................................................................ 19-61
Setting up context menu options .......................................................................... 19-62
Setting up the Common properties ................................................... 19-63
Using the Trend graphic library .......................................................... 19-63
Testing the trend ........................................................................................... 19-63
Using the trend at run time .................................................................... 19-64
Collecting data in the background at run time .................................................... 19-64
Selecting pens ........................................................................................................... 19-65
Changing the trend properties ............................................................................... 19-66
Using scrolling options at run time....................................................................... 19-67
Using the value bar at run time.............................................................................. 19-68
Using the delta value bar at run time .................................................................... 19-69
Using zoom at run time .......................................................................................... 19-70
Using pan at run time.............................................................................................. 19-71
Using the arrow keys at run time........................................................................... 19-71
Printing the trend chart at run time ...................................................................... 19-72
Using overlays at run time ...................................................................................... 19-72
Fixing run-time errors ............................................................................................. 19-73
Chapter 20
Creating expressions........................................................................................................... 20-1
Contents Q
xxxi
Creating expressions .................................................................................... 20-2
Expression buttons.................................................................................................... 20-3
Using the Check Syntax button............................................................................... 20-4
Cutting, copying, and pasting expressions .................................. 20-4
Formatting expressions .............................................................................. 20-5
Using tag names and tag placeholders ........................................... 20-6
Using area names with tag names ........................................................................... 20-7
Using tag placeholders instead of tag names......................................................... 20-7
Constants .............................................................................................................. 20-7
Arithmetic operators ..................................................................................... 20-8
String operands .......................................................................................................... 20-9
Relational operators...................................................................................... 20-9
How string operands are evaluated......................................................................... 20-9
Logical operators .......................................................................................... 20-10
Bitwise operators .......................................................................................... 20-10
Built-in functions............................................................................................ 20-12
Tag functions............................................................................................................ 20-13
Time functions ......................................................................................................... 20-15
File functions............................................................................................................ 20-19
Math functions ......................................................................................................... 20-19
Security functions .................................................................................................... 20-20
Evaluation order of operators............................................................... 20-21
If–then–else ...................................................................................................... 20-23
Nested if–then–else structure............................................................................... 20-25
Chapter 21
Creating embedded variables.....................................................................................21-1
xxxii Q
RSView Supervisory Edition User’s Guide
Creating embedded variables ................................................................. 21-2
Creating numeric embedded variables.................................................................... 21-4
Creating string embedded variables ........................................................................ 21-5
Creating time and date embedded variables .......................................................... 21-7
Cutting, copying, and pasting embedded variables ............... 21-9
Editing embedded variables .................................................................... 21-9
Deleting embedded variables ................................................................. 21-9
How embedded variables are updated at run time ............... 21-10
How embedded variables are displayed at run time............ 21-10
Numeric embedded variables................................................................................. 21-10
String embedded variables...................................................................................... 21-11
Time and date embedded variables....................................................................... 21-11
Chapter 22
Creating macros ........................................................................................................................ 22-1
Creating macros ............................................................................................... 22-1
Running macros ................................................................................................ 22-3
Using parameters ....................................................................................................... 22-4
Typing macro names that contain spaces .............................................................. 22-5
Nesting macros........................................................................................................... 22-5
Creating a macro that runs when an HMI server starts...................................... 22-6
Chapter 23
Setting up navigation .......................................................................................................... 23-1
Developing a hierarchy of displays ..................................................... 23-1
Ways of moving among displays ........................................................... 23-2
Commands for moving among displays................................................................. 23-3
Reducing display call-up time .................................................................................. 23-4
Where to use RSView commands ........................................................................... 23-4
Examples of navigation methods ......................................................... 23-5
Contents Q
xxxiii
Using keys ............................................................................................................ 23-7
General rules about precedence .............................................................................. 23-7
Precedence and the F1 key ...................................................................................... 23-8
Precedence and embedded ActiveX objects ......................................................... 23-8
Precedence and embedded OLE objects .............................................................. 23-9
Reserved keys ........................................................................................................... 23-10
Creating client keys .................................................................................... 23-12
Running client key components ......................................................... 23-14
Chapter 24
Using the SE Client object model and display code ........................24-1
The VBA integrated development environment........................ 24-2
Opening the IDE window....................................................................................... 24-2
Parts of the IDE window ........................................................................................ 24-3
Quick Start steps............................................................................................. 24-5
How VBA code runs ................................................................................................ 24-5
About procedures ............................................................................................ 24-5
The RSView SE Client Object Model ................................................. 24-6
Viewing the objects ................................................................................................. 24-10
Getting Help with RSView SE Client objects..................................................... 24-10
Opening Help from the Object Browser............................................................. 24-11
Opening Help from the Code Window ............................................................... 24-11
Opening Help from the RSView Help Contents window ................................ 24-12
Using VBA Help .............................................................................................. 24-13
VBA documentation............................................................................................... 24-13
Chapter 25
Setting up redundancy ........................................................................................................25-1
HMI redundancy as part of a complete strategy ..................... 25-2
Protecting against software failures ................................................ 25-3
xxxiv Q
RSView Supervisory Edition User’s Guide
Considering redundancy options .......................................................... 25-5
Redundant FactoryTalk Directory computers ...................................................... 25-5
Redundant RSView SE Servers ............................................................................... 25-6
Redundant data servers ............................................................................................. 25-9
Planning the layout of a redundant system ................................ 25-10
An application with a single HMI server............................................................. 25-10
An application with two HMI servers ................................................................. 25-12
An application with up to five HMI servers ....................................................... 25-12
A distributed application that can run
as a set of stand-alone applications ....................................................................... 25-13
Scenarios that explain how redundancy works ...................... 25-15
FactoryTalk Directory is down, and redundancy is not set up for it............... 25-15
Primary FactoryTalk Directory goes down, secondary becomes active.......... 25-16
One primary FactoryTalk Directory, multiple secondary
FactoryTalk Directory computers: primary goes down ..................................... 25-17
Setting up a redundant RSView SE system ................................ 25-18
Licensing in a redundant system ....................................................... 25-19
FactoryTalk Directory computers ......................................................................... 25-19
RSView SE Servers.................................................................................................. 25-19
OPC Servers............................................................................................................. 25-19
RSView SE Clients .................................................................................................. 25-20
Chapter 26
Deploying distributed applications...................................................................... 26-1
Overview of deploying your distributed application............... 26-1
Copying FactoryTalk Directory files .................................................. 26-4
Specifying the location of FactoryTalk Directory .................... 26-4
Copying HMI server files ............................................................................ 26-4
Copying an HMI server that is not running .......................................................... 26-5
Copying an HMI server while it is running ........................................................... 26-6
Setting up HMI server properties ........................................................ 26-8
Contents Q
xxxv
Starting and stopping an HMI server’s components
manually ................................................................................................................. 26-9
Chapter 27
xxxvi Q
RSView Supervisory Edition User’s Guide
Opening the RSView SE Client............................................................... 27-6
Opening the RSView SE Client automatically when Windows starts ............... 27-7
Opening multiple clients........................................................................................... 27-7
How server components start and stop ................................................................. 27-8
Chapter 28
Administering applications........................................................................................... 28-1
Specifying time, date, and number formats ................................. 28-1
Backing up or restoring a stand-alone application ................. 28-2
Administering your application ............................................................. 28-2
Monitoring disk space on the HMI server...................................... 28-4
Appendix A
RSView commands ..................................................................................................................A-1
Using RSView commands ........................................................................... A-1
Where to use commands ........................................................................................... A-1
How to use commands .............................................................................................. A-1
Using placeholders in commands............................................................................. A-2
Precedence ................................................................................................................... A-4
Where commands run................................................................................................ A-4
Commands that do not run in test display mode .................................................. A-6
Absolute and relative references............................................................................... A-6
How relative references are resolved ....................................................................... A-7
Creating symbols......................................................................................................... A-8
Important guidelines .................................................................................................. A-9
Contents Q
xxxvii
Appendix B
System tags ...................................................................................................................................... B-1
Alarms .......................................................................................................................B-1
Time ............................................................................................................................B-2
Appendix C
Setting up DDE communications for HMI tags ........................................ C-1
About DDE communications .....................................................................C-1
Overview of DDE communications .......................................................C-2
Summary of steps .............................................................................................C-3
Creating an HMI tag using DDE ..............................................................C-3
Specifying device as the data source .........................................................................C-3
Syntax for DDE addresses.........................................................................................C-4
Scanning for new tag values .....................................................................C-4
Appendix D
The ODBC database schemas.................................................................................... D-1
FactoryTalk Diagnostics log table ....................................................... D-1
Alarm log table ................................................................................................... D-2
Data log tables ................................................................................................... D-5
Appendix E
Exporting text in your application for translation ...............................E-1
Text that you cannot export .....................................................................E-2
Text that is part of the software ................................................................................E-2
Text that is displayed at run time, but cannot be exported...................................E-3
Text that is not displayed at run time, and cannot be exported ...........................E-4
Exporting text ......................................................................................................E-5
Importing text ......................................................................................................E-8
xxxviii Q
RSView Supervisory Edition User’s Guide
Troubleshooting importing....................................................................... E-10
Common errors and their causes............................................................................ E-10
Information for translators ...................................................................... E-12
File name and format ............................................................................................... E-12
Opening the text file in Microsoft Excel .............................................................. E-13
Saving the text file in Microsoft Excel .................................................................. E-15
Differences in file format for files saved in Excel.............................................. E-16
Editing the Unicode text file in Notepad.............................................................. E-16
File schema ................................................................................................................ E-16
Working with pairs of double quotes .................................................................... E-18
Working with backslashes and new-line characters............................................. E-18
Appendix F
Importing and exporting XML files ........................................................................ F-1
About XML .............................................................................................................. F-1
Creating an XML file .................................................................................................. F-1
Saving XML files in Notepad.................................................................................... F-2
Testing an XML file.................................................................................................... F-2
Importing a Multistate Indicator XML file ........................................ F-3
Error log file .................................................................................................................F-3
Multistate Indicator XML file structure ............................................. F-4
Syntax, attributes, and elements................................................................................. F-4
Specifying attributes in the correct order................................................................. F-5
Version and encoding ................................................................................................. F-5
The gfx element ........................................................................................................... F-6
The msi element........................................................................................................... F-6
The defs element.......................................................................................................... F-6
Multiple multistate indicators in the same file......................................................... F-7
Multistate Indicator element ...................................................................................... F-8
States element............................................................................................................... F-9
Font Element..............................................................................................................F-10
Contents Q
xxxix
Connection Element ................................................................................................. F-11
Animation Element ................................................................................................... F-11
Image Element ........................................................................................................... F-12
Caption element......................................................................................................... F-13
xl Q
RSView Supervisory Edition User’s Guide
P Preface
Thank you for choosing RSView Supervisory Edition™. RSView
Supervisory Edition is a member of the RSView Enterprise Series
family of products. It is an integrated package for developing and
running multi-user, distributed-server human-machine interface
applications. RSView Supervisory Edition is designed for automated
process or machine monitoring, and supervisory control.
Designed for use with Microsoft® Windows® 2000 and Windows XP,
RSView Supervisory Edition gives you all the tools you need to create
effective monitoring and supervisory control applications.
Preface ■ P–1
Finding the information you need
You have many options for finding information about how to use
RSView, or how to solve problems with RSView.
To find the answer, use the table of contents and the index in the user’s
guides and Help.
You can also perform a full-text search on both the Help and the PDF
versions of the user’s guides. For information about using Help and the
user’s guides, see Chapter 3, “Getting the information you need” in the
RSView Supervisory Edition Installation Guide.
On the Help menu, select Rockwell Software on the Web, and then
click the name of the web page you want to view.
The Rockwell Software Discussion Forums are web pages for users of
Rockwell Software products. The forums offer discussion groups, for
exchanging tips and questions with other RSView users.
If you can’t find the answer to your question using any of the resources
suggested above, contact Rockwell Software Technical Support at:
Telephone: 440-646-5800
Fax: 440-646-5801
http://www.software.rockwell.com, or
http://support.rockwellautomation.com
Preface ■ P–3
When you call
When you call, you should be at your computer and ready to give the
following information:
You’ll find this number on the Activation disk label and in the
About RSView Studio dialog box available from the Help menu in
RSView Studio.
a description of what happened and what you were doing when the
problem occurred
Getting started
This chapter introduces RSView Supervisory Edition, and describes:
Features in brief
With RSView Supervisory Edition, you can:
use graphics from the graphic libraries, or import files from other
drawing packages such as CorelDRAW! ™, and Adobe®
Photoshop®.
use the RSView SE Client Object Model and VBA to share data
with other Windows programs such as Microsoft Access and
Microsoft SQL Server, interoperate with other Windows programs
such as Microsoft Excel, and customize and extend RSView to fit
your unique needs.
The following steps explain how to get up and running with RSView.
If you are creating a stand-alone application, skip step 3. You
must complete step 2 at a minimum before you can complete steps 5
or 6. The other steps can be completed in any order.
If you are creating a distributed application, you must complete
steps 2 and 3 at a minimum before you can complete steps 5 or 6. The
other steps can be completed in any order.
Use the utility called Specify FactoryTalk Directory Location to set the
name of the computer on which the FactoryTalk Directory is installed.
Use the Specify FactoryTalk Directory Location utility on every
computer on the network you want to have access to your applications.
For details about how the FactoryTalk Directory software works, see
page 5-2.
Stand-alone applications include one HMI server. You can add one or
more data servers to a stand-alone application. You cannot add areas or
HMI servers to stand-alone applications.
once communications have been set up, how your application will
access values in the programmable controllers or devices.
RSView conforms to the OPC Data Access (DA) 2.0 specification for
information exchange among automation or control applications, field
systems or devices, and business or office applications.
You access these tags by specifying the tag’s address for any object
you want to connect to data, in RSView Studio. For example, in a
graphic display, you can type the tag’s address as part of an object’s
expression.
Either complete this step, or step 6. You need not necessarily complete
both.
When you browse for tags in devices, the OPC topics appear in the tag
browser, each representing a device.
Either complete this step, or complete step 5. You need not necessarily
complete both.
Set up communications for use with OPC data servers if you want to
communicate with non-Allen-Bradley devices. You can have multiple
When you browse for tags in devices, the OPC topics appear in the tag
browser, each representing a device.
Import an existing HMI tag database using the Tag Import and
Export Wizard.
For details, see Chapter 8, Working with tags, and Chapter 9, Creating HMI
tags.
Create graphic displays that represent your process. Build your graphic
displays in a variety of ways:
Use the RSView drawing tools to create graphic objects and text.
You can create simple objects such as ellipses and rectangles, or
create more complex objects such as trends and alarm summaries.
You can also embed ActiveX objects.
Drag and drop ready-made objects from the RSView libraries into
a display.
user level so you lock users into the RSView SE Client. To set up
user-level security, use the DeskLock Tool, included in the Tools
folder.
For details, see Chapter 24, Using the SE Client object model
and display code.
When you start RSView Studio you need to specify the type of
application you want to create. This is called the product type.
Click the Start button, select Programs, and then click RSView
Studio.
Click the Start button, select Programs, Rockwell Software,
RSView Enterprise, and then click RSView Studio.
When you start RSView Studio, the Product Type Selection dialog
box appears automatically.
Opening an application
To familiarize yourself with the RSView Studio development
environment, you can open the sample application. You’ll find it in the
Existing tab of the New/Open SE Distributed Application dialog box.
X On the File menu, select Recent Files, and then click the name of
the application you want to open.
Menu bar
Toolbar
Application Explorer
Workspace
Browse devices on
the network
Diagnostics List
Status bar
The toolbar
The toolbar contains buttons for commonly-used menu items so you
can quickly access the items without opening the menus. When you
point to a button on the toolbar, the name of the button is displayed in
a tooltip.
Standard toolbar
Graphics toolbar
Objects toolbar
All of the editors use the Standard toolbar. The Graphic Displays and
Graphic Libraries editors have additional toolbars.
The workspace
The workspace is the blank area of the RSView Studio window, to
which you can drag and drop icons from the Application Explorer to
launch editors. For details, see “Working in the Application Explorer”
on page 2-8.
Use the Diagnostics Setup tool to select the activity categories you want
to log to the Diagnostics List. For details, see “Routing messages” on
page 12-14.
You can detach (undock) the Diagnostics List from the main window,
and then move the bar anywhere on the screen.
To undock the Diagnostics List, drag the grab bars at the bottom left
of the Diagnostics List. If you can’t see the grab bars, drag the top edge
of the Diagnostics List to make it a bit larger.
To detach the
Diagnostics List, drag
the grab bars.
When the Diagnostics List is undocked, you can make it any size you
want, for example to view more than one message at a time. To resize
the bar, drag an edge or corner until the bar is the size you want.
For information about specifying the types of activities you can display
in the Diagnostics List, see “Message routing” on page 12-3.
For example, if you position the pointer over the Open button, the
following message appears in the status bar:
Application name
Workspace
Click the title bar and then drag the window. To prevent the
Application Explorer from docking automatically while you move
it across the screen, hold down the Ctrl key on the keyboard while
you move the Application Explorer.
Double-click the title bar to float the explorer in the middle of the
main window, and then drag it to a new position.
Right-click the title bar, and then click a new docking location:
floating, or MDI (Multiple Document Interface) Child.
If you click MDI Child, the explorer becomes a window. You can
move, minimize, maximize, or restore the explorer window, but
only within the main window. You cannot move the explorer
outside the main window.
The parts of the Application Explorer are described on the pages that
follow.
Click the folder, and then press Enter to either open or close the
folder depending on its current state.
Editors
Editors are for creating or setting up application components. To open
an editor, do one of the following:
Right-click the editor’s icon to open the context menu, and then
click New or Open.
Right-click to view the
context menu.
If you can use the editor to create multiple components, the context
menu contains New. If the editor can open only a single component,
the context menu contains Open.
Diagnostics Setup Specify the type of system activity you want to log
(Tools menu) and where, when, and how you want it logged.
Alarm Log Setup Specify the type of alarm activity you want to log,
(Tools menu) and where, when, and how you want it logged.
Displaying components
Any components created with the editor appear below the editor in the
tree.
When you add a component in the Application Explorer using the Add
Component into Application option, you are creating a copy of the file
in the application.
X Using the Windows Explorer, locate the file of the component you
want to add to your application, and then drag the file to the
Application Explorer.
1. Right-click the editor that was used to create the component you
want to copy. For example, to add a graphic display component,
right-click the Graphic Displays editor.
3. In the dialog box, find the component you want to add or update,
and then click it.
Use the items on the context menu to rename, remove, and delete
components. The Remove item removes a component from the
Application Explorer. The Delete item removes a component and
deletes its associated file from disk.
Renaming a component
To rename a component
3. Click OK.
3. Select the file that the component represents, and then click Open.
Removing a component
If you no longer want to use a particular component in an application,
you can remove the component (file reference) from the application
using the Remove item on the context menu.
To remove a component
RSView supports long file names. File names, including the path, can
be up to 200 characters long.
For example, the following path and file name contains 111 characters.
The component name (the name of the graphic display) is only 15
characters long, but can be as long as 111 characters:
The Application Explorer and the Graphic Displays editor use context
menus. To open a context menu, right-click the mouse.
The Browse button appears beside data-entry fields. You can type
information into the fields, or you can click the Browse button to open
Browse button a list containing valid entries for the field.
Many editors require a tag name. Tags are stored in devices, data
servers, and in the HMI tag database. Their names are used in other
parts of RSView. You do not have to create tags before you work in
other editors.
Type the name of a tag. You do not have to create the tag to use
the tag name, but be sure to create the tag later or errors will be
reported at run time.
For detailed information about tags, see Chapter 8, Working with tags.
Using expressions
Many editors use expressions to compute values based on tags and
functions. Expressions can be complex logical expressions, or they can
be tag names.
Printing
Each RSView editor has a Print item on its File menu.
To print selections
1. Select the item you want to print. The item can be a record in an
editor’s spreadsheet or it can be an object in a graphic display.
4. Click OK.
3. Click OK.
To select a printer
2. If you don’t want to use the default printer, specify another printer.
4. Click OK.
When you use the PrintDisplay command RSView prints the entire
display, even if parts are covered by other displays. You can also use the
ScreenPrint command to print an image of whatever shows on the
monitor. For more information about these commands see
Appendix A, RSView commands.
Planning an application
A well-designed application requires planning. To help you plan, this
chapter provides guidelines for:
planning communications.
planning alarms.
collecting data.
using trends.
talk to operators and other experts who are going to use the system.
Find out what information they need to optimize plant operations.
You can add as many data servers to your application as you need.
If your application includes a large number of tags and you are not
using RSLinx for RSView or RSLinx Enterprise for communications,
you should place your OPC data server in a different area than the one
in which your HMI server is located. This provides best performance
when accessing data in a large number of tags. RSLinx for RSView and
RSLinx Enterprise are optimized to provide best performance, even if
located in the same area as the HMI server.
For details, see the topics in this manual. For details about developing
RSView Machine Edition applications, see the RSView Machine Edition
User’s Guide.
Using the schema outlined above, you can scale your network to any
size you need, by adding as many computers as you need, running each
of the pieces of software described above, subject to the limits
described above.
Planning redundancy
In theory, the ideal redundant solution involves having at least one copy
of everything—hardware, software, networks, and so on. In practice,
this is seldom feasible, or even necessary.
your network layout, and calculate the processing load you expect
for each computer. This information can help you plan what parts
of your application can share hardware. For example, you might
decide to have four secondary HMI servers run on a single
computer. Or, you might decide to structure your distributed
application so that if the HMI network fails, the application
continues running on the computer as a set of stand-alone
applications.
FactoryTalk Directory
HMI servers
data servers
You can set up RSView Supervisory Edition to send alarm and data log
information automatically to an ODBC-compliant database. You can
set up an HMI server to buffer data locally if the database becomes
unavailable.
Planning communications
When planning communications, gather information about the types
of controllers or devices in your plant, and the software you have
available for communicating with them. This will help you set up one
or more OPC servers.
Also plan how you will access data in the controllers or devices. For
most purposes you can access the values in controllers or devices
directly, using tags provided by a data server in your application.
For certain special purposes, however, you will need to set up an HMI
tag database. HMI tags provide extended capabilities, such as:
Collect information
Before you begin creating the HMI tag database, collect the following
information:
Group HMI tags in the way that makes most sense for your
application. For example, group all similar devices or group related
areas of the plant floor.
When creating HMI tags, place related tags into folders. For greater
organization, create nested folders.
Planning alarms
which alarms will require additional actions that you can supply
using a macro.
Collecting data
When planning displays, determine the best way for users to navigate
through your displays and develop a template to establish a common
look and feel for your displays.
a title.
navigational buttons.
Consistency
When you design several displays, place the same kinds of buttons
in the same positions. For example, if you have a Start button in a
certain position in one display, don’t put a Stop button in the same
position in the next display.
Clarity
Use symbols that are easily recognizable. For example, use the
conventional ISA symbols for tanks and valves.
Some people are color blind to red and green so don’t rely on color
alone to establish meaning.
Using trends
When planning trends, consider how they will be used. For example,
will the trend be used to:
Add custom alarm events You can write your own alarm detection
algorithms using PLC logic, and then create events in RSView to
respond to the algorithms.
Secure the system The RSView Object Model allows you to obtain
security information about who is using the system, and to use the
security information and events to control access to the system. For
example, you can restrict a user’s access to a graphic display on a
secured computer by creating code that displays the graphic display on
a workstation with a specific computer name, only when the user is
logged in with a particular user name.
Setting up FactoryTalk
Directory
This chapter describes:
You can set up your network so that multiple applications share a single
FactoryTalk Directory, or so that there are multiple FactoryTalk
Directory computers for multiple applications.
Your network can also contain more than one computer running the
FactoryTalk Directory software. This is useful if you want to:
To change the
location of the
primary server,
click the Browse
button.
To change the
location of the
primary server,
click the Browse
button.
Summary of steps
To set up redundancy, complete these steps:
To change the
location of the
primary server,
click the Browse
button.
To specify the
location of the
secondary
server, click the
Browse button.
To change the
location of the
primary server,
click the Browse
button.
To specify the
location of the
secondary
server, click the
Browse button.
To change the
location of the
primary server,
click the Browse
button.
To specify the
location of the
secondary
server, click the
Browse button.
Working with
distributed applications
This chapter describes:
HMI projects contain displays, log models, alarms, HMI tags and
other services. HMI projects are loaded by HMI servers.
FactoryTalk Directory
FactoryTalk Directory is software that allows the parts of an
application to find each other on a computer, or on the network.
Your network can also contain more than one computer running the
FactoryTalk Directory software. This is useful if you want to
An application includes:
a list of Windows users and their access codes (called privileges) for
accessing the application and its contents.
HMI servers.
You can see the operational status of primary and secondary HMI
servers by clicking the General tab in the HMI Server Properties dialog
box of either the primary or the secondary server.
Active means that the server is running, and able to serve data to
clients that connect to it.
Standby means that the server is running, and will replace the
active server if the active server fails.
Out of service means that the server has been created, but cannot
be contacted.
For details about loading the server manually, see “Starting and
stopping an HMI server’s components manually” on page 26-9.
Each area can contain one or more sub-areas, and one or more data
servers. Each area or sub-area can contain only one HMI server.
You can use the application root area like any other area, for example
to contain an HMI server, or one or more data servers.
For example, if two graphic displays are located in different areas, each
has a different home area.
Use absolute references when you want to ensure that the same
component is used, regardless of where it is referenced from.
Relative references are useful if your component names are all the
same, but they are in different areas. This might be the case if you
expect to clone identical areas, for example to represent identical
production lines in your plant. For details about how to use areas in
structuring an application, see page 5-16.
Syntax
Precede area names with a forward slash (/). Also separate area names
from other area names, with a forward slash.
Separate area names from component names with two colons (::).
For information about using absolute and relative references with tags,
see “Using tag references” on page 8-19.
For details about how the FactoryTalk Directory software works, see
page 5-2.
Creating an application
To begin working in RSView, create an application.
When you start RSView Studio, the Product Type Selection dialog
box appears automatically.
If the Product Type Selection dialog box is not open, do one of the
following:
Renaming an application
You cannot rename a distributed application that is in use. Ensure that
all users disconnect from the application first.
To rename an application
For details about using the Application Manager tool, click Help.
The HMI projects and data servers you have set up in your application
are not automatically deleted when you delete an application. For
details about deleting an HMI server’s files, see page 5-30. For details
about removing a data server, to delete its cache files, see page 7-17.
To delete an application
For details about using the Application Manager tool, click Help.
Structuring an application
To determine a structure for your application, review your application
plan. For tips about planning applications, see Chapter 3, Planning an
application.
A review of your application plan will help you decide how to use areas
in your application. For example, you can:
Each area in your application cannot contain more than one HMI
server. Each area can contain more than one data server.
If this happens, you should add another HMI server or data server,
installed on a different computer, and then move some of the
components in the HMI project to the new HMI server, or some of
the OPC server tags to the new data server. This distributes the
You can set up redundant HMI servers or data servers to enable your
application to use a secondary server in the event that the primary
server goes out of service.
You must set up redundancy separately for each HMI server or data
server in your application.
3. Click OK
To remove an area
X Right-click the area you want to remove, and then click Remove.
HMI servers and data servers located in the area are not deleted
from disk.
Naming restrictions
The names of HMI servers are stored by FactoryTalk Directory, and
are not deleted, even if you remove an HMI server from all
applications in which it is used and then delete the HMI server’s
project files.
The name of every HMI server must be unique. This means that:
You cannot re-use a name for an HMI server, even after you have
deleted the HMI server.
3. Click Next.
When you are finished adding your HMI server, you can set up the
HMI server’s properties. For details, see page 5-22.
If you want to create a new HMI server that is not based on an existing
HMI server, HMI project, or RSView32 application, click Create a
new HMI server.
When you create an HMI server, the server’s HMI project is created
automatically.
After you have copied an HMI server, changes made to the original do
not affect the copy, or vice versa.
After you have copied a project into the new HMI server, changes
made to the original project do not affect the copy, or vice versa.
2. Copy the HMI project files from the primary HMI server to the
secondary HMI server. For details, see “Copying HMI server
files” on page 26-4.
3. Set up the properties of the secondary HMI server. For details, see
the next section.
view the HMI server’s name, project file path, number of existing
graphic displays, and the maximum number of graphic displays
allowed on the HMI server.
2. In the HMI Server Properties dialog box, fill in the fields in each
tab, as described in the sections that follow. When you are finished,
click OK.
Name The name of the HMI server. This name is set when you create
the HMI server. You cannot change it.
You cannot type the name of a computer on which the HMI project
does not exist. Before you can change the computer name in this box,
you must copy the HMI project to the target computer.
Project file (relative to server computer) The file path to the HMI
server’s files. The path is set when you create an HMI server. You
cannot change it.
Startup type Specify when you want the HMI server to be loaded:
When the HMI server is loaded, you can edit the server’s HMI
project using RSView Studio, and you can connect clients to the
HMI server. A client can be RSView Studio, the RSView
Administration Console, or the RSView SE Client.
This option allows clients to connect quickly, and ensures that the
HMI server can be brought back to normal operation automatically
if the computer on which it is running is restarted.
The HMI server can only be unloaded by changing the Startup type
to On demand, and then closing all clients.
Because the HMI server runs as a service, users do not have to log
in to make the HMI server run.
In the Redundancy tab, specify the name of the computer hosting the
secondary HMI server.
When the primary HMI server becomes available again, the system
automatically switches back to the primary server.
This option is available only if the HMI server startup type is set to
Load and run startup components when operating system initializes.
For details about the HMI server’s startup type, see page 5-24.
which macros will run when the HMI server shuts down.
Data logging Starts running the specified data log model. This is the
same as using the DataLogOn <component> command. Up to 20 data
log model files can run simultaneously, but only one can be specified in
the Components tab. To run more files, list them in a startup macro.
Derived tags Runs the specified derived tags file. This is the same as
using the DerivedOn <component> command. Up to 20 derived tag files
can run simultaneously, but only one can be specified in the
Components tab. To run more files, list them in a startup macro.
Events Runs the specified event component. This is the same as using
the EventOn <component> command. Up to 20 event components can
If you have not set up a secondary server in the Redundancy tab, this
option is not available.
On standby macro Runs the specified macro when the HMI server
switches from being active to being on standby. This most frequently
happens when the system switches back from the secondary HMI
server to the primary HMI server after the primary server has been
restored to operation. This macro will not run if the active HMI server
fails and is unable to run the macro, for example if the power to the
computer fails. Any macro can be used as the On standby macro.
If you have not set up a secondary server in the Redundancy tab, this
option is not available.
When you stop the HMI services manually, clients are disconnected, all
HMI servers running on the computer are shut down, and the
activation keys used by the HMI servers are released.
When you start the HMI services manually, clients are allowed to
connect to HMI servers on the computer.
If you have set up a redundant HMI server, you can also start or stop
the redundant server’s components manually.
You can remove an HMI server from your application without deleting
its project files. This allows you to add the HMI server to an
application at a later time. You can also add the HMI server to an
application temporarily, while you copy components to other HMI
servers in the application.
1. Disconnect all clients from the HMI server. A client is any of the
following: RSView Studio, RSView Administration Console, or
RSView SE Client.
2. Start RSView Studio, and then open the application from which
you want to remove the HMI server.
3. Right-click the HMI server you want to remove, and then click
Remove.
1. Disconnect all clients from the HMI server. A client is any of the
following: RSView Studio, the RSView Administration Console, or
the RSView SE Client.
3. Delete the folder that has the same name as the HMI server whose
project files you want to delete.
Working with
stand-alone applications
This chapter describes:
Key concepts
Understanding terminology
For definitions of terms such as FactoryTalk Directory, HMI server,
and so on, see Chapter 5, Working with distributed applications.
You do not have to set up FactoryTalk Directory for use with stand-
alone applications. This is done automatically.
Because stand-alone applications contain only one root area and one
HMI server, you cannot use absolute references.
To create an application
When you start RSView Studio, the Product Type Selection dialog
box appears automatically.
If the Product Type Selection dialog box is not open, do one of the
following:
To import a
project, type an
application
name, and then
click Import.
To import a project
2. Click Import.
4. Type the path and file name of the project you want to import, or
click the Browse button to browse for the project file, and then
click Finish.
After you have copied a project into the new application, changes made
to the original project do not affect the copy, or vice versa.
Renaming an application
You cannot rename a stand-alone application that is in use. Close all
RSView SE Clients first.
To rename an application
For details about using the Application Manager tool, click Help.
By default, the HMI project and data servers you have set up in your
application are not automatically deleted when you delete an
application. For details about deleting an HMI project, see page 6-12.
For details about removing a data server, to delete its cache files, see
page 7-17.
To delete an application
1. Write down the the name of the HMI server in the application.
You will need this list if you want to delete the HMI server’s files
(step 3, below).
If you want to provide redundant operation for data servers at run time,
you must install each data server on a separate computer.
You can set up redundant data servers to enable your application to use
a secondary server in the event that the primary server goes out of
service.
You must set up redundancy separately for each data server in your
application.
For details about adding data servers to your application, see page 7-7.
2. In the HMI Server Properties dialog box, fill in the fields on each
tab, as described in the sections that follow. When you are finished,
click OK.
Name The name of the HMI server. This name is set when you create
the HMI server. You cannot change it.
Project file (relative to server computer) The file path to the HMI
server’s files. The path is set when you create an HMI server. You
cannot change it.
which macros will run when the HMI server shuts down.
Data logging Starts running the specified data log model. This is the
same as using the DataLogOn command. Up to 20 data log model files
can run simultaneously, but only one can be specified in the
Components tab. To run more files, list them in a startup macro.
Derived tags Runs the specified derived tags file. This is the same as
using the DerivedOn <component> command. Up to 20 derived tag files
can run simultaneously, but only one can be specified in the
Components tab. To run more files, list them in a startup macro.
Events Runs the specified event component. This is the same as using
the EventOn <component> command. Up to 20 event components can
On shutdown macro Runs the specified macro when you click the
Stop All Running Components button in the HMI Server Properties
dialog box. Any macro can be used as a shutdown macro. Closing any
RSView SE Client will not run the On shutdown macro.
Setting up
communications
This chapter describes:
OPC servers provide a way for RSView to retrieve tag values from:
RSView SE Server’s
HMI tags
Third-party Third-party
RSLinx OPC server
application
with OPC
server support
Allen-Bradley Non-
programmable Allen-Bradley
controller device
1. Gather information about your network, and the devices that are
connected to it. You will need this information to set up RSLinx,
or another OPC server.
3. If you want to use RSLinx for RSView as the OPC server that
enables communications on your network, set up RSLinx for
RSView. For details, see Getting Results with RSLinx, or see Help for
RSLinx.
6. In RSView Studio, add a data server that points at the OPC server
you set up in step 3, step 4, or step 5.
7. If you want to use HMI tags in your application, open the Tags
editor, and then create device tags that point at addresses in
devices. For details about creating HMI tags, see Chapter 9,
Creating HMI tags.
If you do not want to use HMI tags, but instead want to access
addresses in devices directly, skip this step. For details about using
tags, see Chapter 8, Working with tags.
An OPC data server provides support for any data server that
conforms to the OPC-DA 2.0 standard, or an OPC server for use
with the version of RSLinx called RSLinx for RSView.
An OPC data server for use with RSLinx for RSView provides
enhanced support for Rockwell Automation programmable controllers
and devices.
If you are using RSLinx for RSView or another OPC data server for
communications, create an OPC data server. If you are using RSLinx
Enterprise for communications, create an RSLinx data server.
If your application includes a large number of tags and you are not
using RSLinx for RSView or RSLinx Enterprise for communications,
you should place your OPC data server in a different area than the one
in which your HMI server is located. This provides best performance
when accessing data in a large number of tags. RSLinx for RSView and
RSLinx Enterprise are optimized to provide best performance, even if
located in the same area as the HMI server.
For details about adding RSLinx Enterprise data servers, see “Adding
RSLinx Enterprise data servers” on page 7-12.
2. In the Data Server Properties dialog box, fill in the fields in each
tab, as described in the sections that follow. When you are finished,
click OK.
Name Type a name for the data server. The name cannot include
dashes or hyphens (–).
Description Type a description for the data server. For example, use
this box to describe a component’s location, to identify a contact
person or number in the event of failure, or to keep track of changes or
version information.
Computer that will run the OPC server Type the name of the
computer on which the data server will run. To browse for the name of
the computer, click the Browse button.
If you want to use RSLinx as the OPC server, click the Browse button,
and then click RSLinx Remote OPC Server.
In the Redundancy tab, specify the name of the secondary data server,
and specify whether RSView should switch back to the primary data
server if it becomes available again.
To make RSView switch back to the primary data server when the
primary server becomes available again, click Switchback to the
primary server when it becomes available.
In the Advanced tab, set up a cache for tags on the data server. A cache
allows you to view tag names when you are not connected to the data
server.
5. Click OK.
If tags are added, modified, or deleted on the data server, you must
synchronize the cache manually.
You can synchronize a data server’s cache only after you have created
one.
4. Click OK.
For details about adding OPC data servers for use with RSLinx for
RSView or other OPC servers, see “Adding OPC data servers” on
page 7-7.
2. In the Data Server Properties dialog box, fill in the fields in each
tab, as described in the sections that follow. When you are finished,
click OK.
Name Type a name for the data server. The name cannot include
dashes or hyphens (–).
Description Type a description for the data server. For example, use
this box to describe a component’s location, to identify a contact
person or number in the event of failure, or to keep track of changes or
version information.
In the Redundancy tab, specify the name of the secondary data server,
and specify whether RSView should switch back to the primary data
server if it becomes available again.
X Right-click the data server you want to remove, and then click
Remove.
When you remove a data server, its cache files are also deleted.
RSView conforms to the OPC Data Access (DA) 2.0 specification for
information exchange among automation or control applications, field
systems or devices, and business or office applications.
The tags that you create in the Tags editor in RSView are called HMI
tags, but your application can also use other kinds of tags, such as those
found in ControlLogix processors, or tags from other OPC-compliant
devices.
Tag-related limits
Each HMI server in your application can have up to 40,000 HMI tags
that have alarms. Of these alarm tags, 10,000 can be analog HMI tags.
To animate graphic displays, monitor alarms, log data, and for several
other uses, you need to obtain values from, or provide values to devices
or other software programs.
If your application includes a large number of tags and you are not
using RSLinx for RSView or RSLinx Enterprise for communications,
To use a data server tag, you must first create it in the OPC
server or processor. For example, in a ControlLogix processor,
create the tag using your RSLogix 5000 programming software.
To use an HMI tag, you must first create it in the HMI Tags
editor. For details, see Chapter 9, Creating HMI tags.
2. Browse for, or type, the name of the tag anywhere you want to
connect an object to ‘live’ data at run time.
If you don’t know the names of tags, you can browse for them. You can
browse while online and connected to a device, or you can browse for
tags from an offline file, for example a PLC program file.
To browse for tags, use the tag browser. For details, see page 8-8.
You can type the name of a tag that doesn’t yet exist. If you do this,
ensure that you spell every instance of the tag name consistently. When
Eliminate duplication
Using data server tags allows you to add, modify, or delete tags in a
device without having to duplicate the changes in the RSView HMI tag
database.
additional HMI tags every time you create a new instance of a data
structure in your controller.
You must use HMI tags (that is, you cannot use data server tags) for
any of the following things you might need to do in your application.
Alarms
In RSView, HMI tags provide the only method for triggering an alarm
when a tag has a certain value.
For more information about alarms, see Chapter 11, Setting up alarms.
Security
For information about assigning security codes to tags, see Chapter 15,
Setting up security.
You must use HMI tags if the data server you are using does not
provide for:
The scale and offset modify the ‘raw data’ that comes from and goes to
the programmable controller before it is saved in the computer’s
memory (called the value table). The scale and offset also modify the
value specified in RSView before it is written to the programmable
controller.
The offset is a fixed value—after the value from the PLC is multiplied
by the scale, the offset amount is added.
HMI tags allow you to set a minimum and maximum values that can
be written to the programmable controller or server.
For information about minimum and maximum, and scale and offset,
see “Setting up an analog tag” on page 9-13.
and so on. For information about creating memory HMI tags, see
Chapter 9, Creating HMI tags.
2. In the tag database, create memory tags, or, for device tags, map
each tag name to an OPC, or DDE address.
The tag browser has two modes: one for selecting a single tag, and one
for selecting multiple tags. Depending on whether a single tag or
multiple tags are expected, when you click the Browse or Tag button
the single-selection tag browser appears, as shown above, or the
multiple-selection tag browser appears, as shown on page 8-15.
The tag browser for multiple selections lets you add tags to a list, and
then edit the list before you click OK.
edit an HMI tag by right-clicking it, and then clicking Edit HMI
Tag. The Tag Editor dialog box opens so you can edit the tag’s
definition.
import tags from a PLC or SLC database and copy them into the
RSView tag database if the selected folder contains an HMI server.
To do this, right-click a blank area of the browser’s right pane, and
then click Import PLC Tags. The PLC Database Browser opens so
you can specify the tags you want to import.
You can use the Offline folder to browse tags in a PLC program stored
on disk. If the OPC/DDE topic in RSLinx has access to symbols, you
can browse for them in the Offline folder, in the tag browser. For
details about adding symbols to the OPC/DDE topic in RSLinx, see
RSLinx Help.
For details about setting up and managing a data server’s cache files, see
“Setting up advanced properties” on page 7-10.
Browse button
Root folder
Area folder
Folders pane
Tags pane
The tag browser window is divided into two panes. The left pane shows
the folder hierarchy for the tags in the application. The right pane
displays the tags in the folder you select in the left pane.
The parts of the tag browser are described on the pages that follow.
By default, the folder pane shows folders, but not the servers they
belong to. You can show the names of servers in the application. To
display server names, right-click a blank area of the folders pane and
then click Show Server Names.
Adding folders
You can add folders to HMI servers only. When you click the icon of
a folder that does not contain an HMI server, you cannot add folders.
1. To make it easy to see where you can add folders, right-click the
Folders pane and then click Show Server Names.
4. Click OK.
If you have the tag browser open, and you or another user on the
network add a tag, the new tag does not appear in the tag browser
automatically.
X Right-click a folder in the Folders list, and then click Refresh folder.
X Right-click a folder in the Folders list, and then click Refresh all
folders.
Displaying tags
To display tags, select a folder. Any tags in the folder appear in the right
pane of the tag browser.
By default, the tag browser does not show tag descriptions. To show or
hide tag descriptions, right-click a blank area of the right pane, and then
click Show Description.
To select consecutive tags, click the first item, press and hold down
the Shift key, click the last tag, and then click OK.
To select tags that are not consecutive, click the first item, press and
hold down the Ctrl key, and then click each item. When you are
finished selecting items, click OK.
To select all the tags in the list, right-click the tags pane, and then click
Add Item(s) to List.
1. Click the folder that contains the tags you want to add to the list.
You can remove items from the list before you click OK.
X Highlight the item or items you want to remove, and then do one
of the following:
To clear the list, you do not have to highlight tag names first.
The Tag Properties dialog box shows information about the tag. The
properties are a snapshot, and do not update in real time. You cannot
display the properties of multiple tags at the same time.
Filtering tags
To display only tags whose names match a pattern, type the pattern in
the Tag Filter box, and then press Enter.
The context menu in the tag browser’s right pane includes three menu
items for manipulating HMI tags:
Import PLC Tags allows you to import a tag from another database.
For information about creating and editing HMI tags, see Chapter 9,
Creating HMI tags. For information about importing tags from a PLC
database, see page 9-22.
When you type a tag name, you are creating a reference to the tag. For
example, you might refer to a tag called FanRunning to obtain its value
for animating a graphical representation of a fan in a graphic display.
In distributed applications, there are two ways to refer to a tag. You can
create an absolute reference, or a relative reference.
Absolute references
Use absolute references when you want to ensure that you are referring
to a specific tag in a specific location.
Relative references
Relative references are useful if your tag names are all the same, but
they are in different areas. This might be the case if you expect to clone
identical areas, for example to represent identical production lines in
your plant. For details about how to use areas, see page 5-16.
For example, if you are creating a graphic display in the Cooling area,
and add a relative reference to a tag (for example, FanStart), RSView
looks for the tag in the home area of the graphic display (Cooling). If
the tag does not belong to a data server or HMI server in the home
area, an error will occur when the display runs.
If the tags you are selecting are in the home area, the tag browser
automatically uses relative references. If the tags are not in the home
area, the tag browser uses absolute references.
how to create analog, digital, and string tags using the Tags editor.
These tags can represent devices that use text, such as a bar
code scanner that uses an alphanumeric product code.
When defining an analog, digital, or string HMI tag, you must specify
a data source. The data source determines whether the HMI tag
receives its values externally or internally.
Device
An HMI tag with Device as its data source receives its data from a
source external to RSView. The data can come from a programmable
controller or other device via RSLinx, or from another OPC or DDE
server.
Memory
An HMI tag with Memory as its data source receives its data from
RSView internally. A memory tag can be used to store values internally.
For memory tags, optionally you can specify that the tag’s value be
retained when RSView Studio, or the RSView SE Client shuts down.
Tag names can be up to 255 characters long. If you create a folder, the
folder name becomes part of the tag name.
A to Z
0 to 9
The tag name can be mixed case. Tag names preserve upper and lower
case for readability but are not case sensitive. For example, the tag name
MixerValve1 is the same as mixervalve1.
When a tag name starts with a number or contains a dash, enclose the
name in braces { } when you use it in an expression, for example,
{N33-0}. Also use braces when using wildcards to represent multiple
tags in an expression, for example, {alarm*}. For more information
about using tags in expressions see Chapter 20, Creating expressions.
For greater organization, you can nest folders. For example, if your
plant is divided into zones, you can organize the tag database first by
zone, then by machines in the zone, and finally by devices in each
machine. The result might be Area1\Machine1\Pump.
Form
Query box
Folder hierarchy
Spreadsheet
In the upper part of the form, define the basic characteristics of the tag,
such as tag name, type, security, and specifics related to the tag type.
Select the Alarm check box to define alarm conditions for an analog or
digital tag. To edit alarms once they have been defined, click the Alarm
button.
When you search for tags, remember that the backslash in a folder
name counts as one character in the tag name.
You can nest folders. If a folder icon has a plus ( + ) sign on it, the
folder contains one or more folders. If the folder’s icon is blank, it does
not contain any other folders.
This folder contains one or more folders.
Creating a folder
1. On the Edit menu, click New Folder, or on the toolbar, click the
Create Folder button.
Create Folder
2. In the New HMI Tag Folder dialog box, type the folder name.
3. Click OK.
To open a folder
2. On the Edit menu, click New Folder, or on the toolbar, click the
Create Folder button.
Create Folder
3. In the New HMI Tag Folder dialog box, type a backslash (\)
followed by the new folder name.
4. Click OK.
When you nest folders, remember that the backslash in a folder name
counts as one character in the tag name.
To view a series of nested folders, resize the hierarchy box. To resize it,
place the cursor over the right border of the box until it changes to a
double arrow. Drag the border to the required size.
4. Click OK.
Deleting a folder
1. Select one or more folders in the hierarchy.
2. On the Edit menu, click Delete Folder, or on the toolbar, click the
Delete Folder button.
Delete folder
Use the spreadsheet to view tags. Use the query box or folder hierarchy
to select the tags you want to view.
To select a row, click anywhere in the row or click the row number.
1. Place the cursor over the division between the column or row, in
the top or side border. When positioned correctly, the cursor
changes to a double arrow.
Adding a tag
Click the New button in the forms area. This inserts a new row
above the highlighted row.
On the Edit menu, click Insert Row, or on the toolbar, click the
Insert Row Insert Row button. This inserts a new row above the highlighted
row.
3. In the Tag Name box, type the name for the new tag.
4. Click Accept.
Editing a tag
You can edit all parts of a tag except the tag name and tag type.
Deleting a tag
Delete tags carefully. Once you click the Delete button, the tag is
deleted. There is no confirmation message, and you cannot undo the
deletion.
2. On the Edit menu, click Delete, or on the toolbar, click the Delete
button.
Delete
1. If the tag is part of a folder, select the folder in the folder hierarchy.
The folder name appears in the Name field and is the first part of
the tag name.
2. Type a tag name. If the tag is part of a folder, type the name after
the backslash (\).
Scale and Offset Type a number. For the scale, do not use 0.
To disable the scale, type 1. To disable the offset, type 0.
The scale and offset modify the ‘raw data’ that comes from and
goes to the programmable controller before it is saved in the value
table. The scale and offset also modify the value specified in
RSView before it is written to the programmable controller.
This formula shows the relationship between the PLC value and
the amount stored in the RSView value table:
For tags with Device as the data source, select the data type that
matches the format of the data stored in the programmable
controller or Windows application.
For tags with Memory as the data source, select the data type that
matches the format of the data you will store in the tag.
2. Type a tag name. If the tag is part of a folder, type the name after
the backslash (\).
2. Type a tag name. If the tag is part of a folder, type the name after
the backslash (\).
The following topics describe how to complete the Data Source fields.
For details about setting up analog, digital, and string tag types, see
“Setting up tag type” on page 9-12.
An HMI tag with device as its data source receives its data from a
source external to RSView. The data can come from:
For details about creating HMI tags for use with DDE
communications, see Appendix C, Setting up DDE communications for
HMI tags.
1. Click Device.
2. In the Address box, specify the name of the tag in the OPC server,
or specify the DDE item.
You can click the Browse button to select the address of the OPC
Browse button
tag.
[AccessPath]Address or
::[AccessPath]Address
where :: indicates that the address resides in a data server in the home
area.
IMPORTANT The square brackets are part of the syntax. They do not
indicate optional parameters.
For communications with other OPC servers, the access path may
be optional. For information about the syntax for the access path,
see your OPC server documentation.
1. Click Memory.
When you first load an HMI project, a memory tag has the value
defined in the Initial Value box.
The value of a memory tag can also be set using derived tags, events,
or graphic objects.
If you want the memory tag to revert to its inital value the next time
RSView Studio or an RSView SE Client starts, clear the Retentive
check box.
When you import tags, they can be merged with tags already in the tag
database, in which case any tags with the same name are updated with
the new information.
For more information about the Wizard, see “Using the Tag Import
and Export Wizard” on page 9-24.
Browse button 1. Click the Browse button or the Tags button, whichever is available,
to open the tag browser.
2. In the tag browser, open the folder in which you want to create the
tag, right-click a blank area of the Contents pane, and then click
Tag button
New HMI Tag.
The Tag Editor dialog box opens so you can set up the tag.
To import tags from a PLC database, use the Import PLC Tags dialog
box.
DB Browser button in
In the tag browser, right-click a blank area of the Contents
the Tags editor pane, and then click Import PLC Tags.
Use the Import PLC Tags dialog box to import tags selectively from
an Allen-Bradley PLC database into the RSView HMI tag database.
Tags imported in this way are copied into the database—they are not
shared with the source database. This means changes to tags in RSView
do not affect the database from which they have been imported and
vice versa.
For PLC and SLC addresses, the Import PLC Tags dialog box shows
only addresses that are used in the symbol or address list of the PLC
programming software.
1. In the Import tags into Folder box, type the name of the folder in
the tag database into which you want to import the tags.
2. In the RSLinx Topic box, type the name of the RSLinx topic to
which the tags belong.
3. In the PLC Database box, type the name and path for the database
you want to import tags from, or click the Browse button to locate
Browse button and select the database you want to import tags from.
The addresses and symbols from the selected database are displayed
in the box below the Filter data entry field.
4. To filter the tag list so that only certain addresses or symbols are
displayed, type a character string, then click Search. If you want to
search on names only, click Symbols so that only symbol names are
displayed. If an address does not have a symbol name it will not be
displayed.
Use the filter if the address or symbol list is too big to display
entirely.
6. Click OK.
The selected symbols are added to the tag database for the current
application, and are displayed in the tag list. If you have already
imported a particular symbol, you are prompted to change its name
if you want to import it again.
In RSView Studio, click the Tools menu, and then click Tag
Import and Export Wizard.
Click the Windows Start button, select Programs, Rockwell
Software, RSView Enterprise, Tools, and then click Tag Import
and Export Wizard.
If you need help while using the wizard, click the Help button.
When a tag has an alarm set up for it, an X appears in the Alm column
of the Tags editor’s spreadsheet, and the Alarm button in the editor’s
form is highlighted (enabled).
You should not write to derived tags, because the derived tag is only
evaluated when the expression changes. For example, if the derived tag
called Tag3 has the expression of Tag1+Tag2, and if you set Tag3=0,
the value of Tag3 becomes zero, and will only be updated when the
value of Tag1 or Tag2 changes.
Use multiple derived tag components to group derived tags that need
to be evaluated at different rates.
Summary of steps
The main steps for setting up derived tags are:
1. Set the maximum update rate for the the derived tag component in
the Derived Tag Setup dialog box.
You must set the maximum update rate separately for each derived tag
component.
The maximum update rate also determines the fastest rate at which
data servers send changes in tag values.
Set the update rate as fast as, or faster than, the rate at which the values
of tags used in the expressions change, unless it is desirable to miss
changes in tag values.
1. On the menu bar, click Setup and then click Derived Tag Setup.
2. In the Derived Tag Setup dialog box, type a brief description of the
derived tag component. This description is for your information
only—it does not appear anywhere else.
4. Click OK.
1. In the Tag Name box, type the name of the tag that will hold the
derived value. You can also browse for the tag name using the
Browse button Browse button.
You can use any tag as a derived tag. The tag must already exist, for
example in a programmable controller or data server, before you
can use it as a derived tag.
3. In the Expression box, type the expression that will determine the
derived tag’s value. For information about expressions, see
Chapter 20, Creating expressions.
4. Click Accept.
2. Use the Prev and Next buttons to move among derived tags. Make
the required changes.
In the Graphic Displays editor, create a button and then specify the
DerivedOn <component> command as the button’s press action.
When the button is pressed, derived tag processing starts.
To stop a single derived tag component, use any of the methods below:
In the Graphic Displays editor, create a button and then specify the
DerivedOff <component> command as the button’s press action.
When the button is pressed, derived tag processing stops.
Setting up alarms
In RSView Studio, you can set up a complete alarm system. Alarms are
an important part of most plant control applications because an
operator must know the instant something goes wrong. It is often
equally important to have a record of the alarm and whether the alarm
was acknowledged.
IMPORTANT You can monitor only HMI tags for alarms. You cannot
monitor data server tags for alarms.
Summary of features
monitor any analog and digital HMI tag for alarms (to a maximum
of 40,000 tags per HMI server).
display the last 2,000 alarm transactions from each HMI server, in
an alarm summary.
Key concepts
An alarm occurs when something goes wrong. It can signal that a
device or process has ceased operating within acceptable, predefined
limits or it can indicate breakdown, wear, or a process malfunction.
Thresholds
Alarm
Threshold security
values Thresholds levels
5,000 6 * 1
4,000 5 * 4
Increasing
3,000 4 8
1,000 2 6
Decreasing
1 1 4
Time
Thresholds must be set up
in ascending order * These alarms are triggered only if the check
box ‘Generate alarms when approaching
normal operating range’ is selected in the
Alarm Setup dialog box.
You can specify whether or not to generate alarms when an analog tag
value is moving back to normal operating range and recrosses the alarm
trigger threshold. If you choose to generate alarms when the motor is
moving back towards normal operating range, an alarm would be
triggered when the motor speed falls below 5,000 rpm and 4,000 rpm,
and when it rises above 1 rpm and 1,000 rpm. If you don’t want to
generate these alarms, make sure the check box ‘Generate alarms when
approaching normal operating range’ is deselected in the Setup tab of
the Alarm Setup editor.
Variable thresholds
Alarm faults
A variable threshold must not become higher than the threshold above
it or lower than the threshold below it. If this happens, an alarm fault
is generated for the monitored tag. To correct an alarm fault, you must
change the variable threshold so it does not overlap either of its
neighbors. This can become complex when the neighboring thresholds
are themselves variable, because these boundaries are determined
dynamically at run time.
The tag’s alarm status stays where it was before the alarm fault was
generated.
The alarm fault status bit for the tag is set in the value table. This
notifies other applications that an alarm fault has been generated.
The Alarm Type column in the alarm summary states that the tag is
in `Alarm Fault ’.
When the faulty thresholds return to their normal operating range, the
alarm fault condition is cleared, the out-of-alarm-fault status is
generated and logged, and alarms for the tag resume normal operation.
Deadband
With certain kinds of measured values, such as line pressure, tag values
can fluctuate rapidly above and below a critical threshold. Where such
conditions exist, you can create a deadband as a buffer to prevent the
fluctuations from triggering and retriggering unnecessary alarms.
rpm In alarm
In alarm again
5,000
4,000
Deadband
3,500
3,000
Threshold
2,000 Out of alarm
1,000
0 n
Time
Digital tags are either on or off. Therefore, alarms for digital tags do
not have thresholds. They have alarm states.
Alarm severity
Alarm messages
For each message, you can use the default message or create your own
message, and you can selectively route alarm messages to a log file and/
or printer.
The alarm log file records alarm incidents that occur. You can set up
how often, if ever, you want log files created and deleted.
In RSView, you can view the alarm log file using the Alarm Log Viewer.
an alarm summary.
When alarms are generated, they are recorded in two places: the alarm
log file, and the computer’s memory. The alarm log viewer displays the
records in the alarm log file. The alarm summary displays the records
in the computer’s memory.
The alarm log viewer displays the contents of the alarm log file. The
contents of this file depend on how you set up severities in the Alarm
Setup editor. By default, the log file will have a record for each of the
following alarm incidents:
Alarm summary
When the list of alarms at the HMI server is full and a new alarm is
generated, the alarm at the bottom of the list (the oldest alarm) is
acknowledged automatically by the system, and then dropped from the
the list. Alarms that are acknowledged automatically by the system
appear in the alarm log file with SysAk (system-acknowledged) in the
TransType (transaction type) field.
Alarms are also dropped when they are out of alarm, or acknowledged
manually. When alarms are dropped, they are removed from memory.
When the AlarmOff command is issued, the contents of the alarm
summary are erased.
AlarmOff is just one of the RSView commands used with alarms. For
details about this command and others, see Appendix A, RSView
commands, or see Help.
System tags are created and updated by RSView. You can use these tags
anywhere a tag name is required.
One acknowledgment is all that is required for all previous and current
alarms for a tag, so alarm log files often show fewer acknowledgments
than alarms.
Alarm suppression
You can suppress alarm monitoring for tags. This is useful for testing
or for performing repairs or maintenance on a piece of equipment.
ALM_IN_ALARM (tag)
where tag is the name of the tag you want to check for alarms. When a
tag is in alarm, the expression result is 1. When a tag is out of alarm,
the expression result is 0.
ALM_ACK (tag)
When alarm monitoring starts and a tag has never been in alarm, the
ALM_ACK expression returns 1 by default. To reverse this default
behavior, create the registry key Alarm Initially Acked on the computer
HKEY_LOCAL_MACHINE\Software\Rockwell Software\
RSView Enterprise\Alarm Server
To create or change the key, use the Windows Regedit32 utility. For
details about using Regedit32, click Help in the Registry Editor window.
ALM_ALLACKED (tag*)
Other functions are also used with expressions to monitor alarms. For
more information, see Chapter 20, Creating expressions.
For built-in alarm functions, you can use wildcards in the expression to
retrieve information about multiple tags at once.
This wildcard Does this
ALM_IN_ALARM (alarm*)
where alarm* represents all tags whose names begin with ‘alarm.’ If one
or more of these tags are in alarm, the expression result is 1. If all of
the tags are out of alarm, the expression result is 0.
An acknowledge bit is a digital tag that can be used for two things:
to acknowledge an alarm, or
When you set up an acknowledge bit for a tag, the HMI server
monitors the value of the acknowledge bit, and automatically
acknowledges the alarm when the value of the acknowledge bit changes
from 0 to 1. This is called a remote acknowledge, and a RmAck
(Remote Acknowledge) transaction is logged to the alarm log file.
1. In the Tags editor, click an analog or digital tag for which you have
set up an alarm.
4. In the Acknowledge Bit box, type the name of a tag or click the
Browse button to browse for the tag you want to use as the
Browse button acknowledge bit.
Handshake bit
A handshake bit is a digital tag that can be used to monitor the status
of an alarm.
When you set up a handshake bit for a tag, the HMI server sets the
handshake bit to 1 when the tag goes into alarm. If the Auto Reset
feature is enabled, the HMI server sets the handshake bit to 0 when the
tag goes out of alarm.
1. In the Tags editor, click an analog or digital tag for which you have
set up an alarm.
4. In the Handshake Bit box, type the name of a tag or click the
Browse button to browse for the tag you want to use as the
Browse button handshake bit.
Alarm events
You can customize and extend the RSView alarm monitoring system
by writing your own alarm-detection algorithms using PLC ladder
logic, custom programs, or any other appropriate tools. You can then
add alarm events to the RSView alarm subsystem, to respond to your
alarm-detection algorithms for annunciation, logging, printing, and for
display in alarm summaries.
By using a tag name for an alarm event, you can customize the alarm
features of the tag. For example, you can use alarm events to specify an
alarm’s time stamp. Because alarms are scanned in the background,
alarms that are generated rapidly might appear out of sequence in
RSView, because they might all be scanned at the same time, and
therefore given the same time stamp. If the sequence in which alarms
are generated is important, you might want to record accurate time
stamps for the alarms by buffering the alarms in the PLC, and then
using alarm events to record them with accurate time stamps in
RSView.
You can also use alarm events to provide a tag with more than eight
thresholds.
Alarm events let you create alarms, even without setting up tags in the
tag database. Event-based alarms work just like tag-based alarms. They
appear in alarm summaries, they can be used with alarm system tags,
and they can be logged to disk or printer.
You can filter event-based alarms the same way you filter tag-based
alarms in alarm summaries. You can acknowledge event-based alarms,
either individually, or with wildcards, using the Acknowledge
command. You cannot suppress event-based alarms.
As with tag-based alarms, you can use alarm events with alarm
functions in expressions.
Alarm events are not processed until the AlarmOn command is issued,
and alarm events are no longer processed after the AlarmOff
command is issued.
You cannot specify thresholds for analog alarm events. All analog
alarm events have a value of zero.
You cannot specify alarm labels for event-based alarms. That is, you
cannot use the IntoAlarm and OutOfAlarm labels for digital tag-
based alarms, or the threshold labels for analog tag-based alarms.
A name must be associated with each alarm event. The event name can,
but need not be, a tag defined in the tag database. An alarm event name
cannot be an alarm tag in the database.
Alarm event names can be up to 255 characters long. The alarm event
name can contain the following characters:
A to Z
0 to 9
The alarm event name can be mixed case. Alarm event names preserve
upper and lower case for readability but are not case sensitive. For
example, the alarm event name HopperOverflow is the same as
hopperoverflow.
Event-based alarms appear in the alarm log file in the order in which
the alarm transactions were logged. If you specify a time stamp for
Summary of steps
The main steps involved in setting up alarms are described below. You
do not have to complete the steps in this order.
1. Set up the general features of all alarms in the Alarm Setup editor.
a. Set up alarm severities. For each severity, you can specify the
destination of alarm messages. You can also specify how to
annunciate the alarm.
Using the Alarm Setup editor, you can also specify whether to
generate alarms when an analog tag value is moving back to normal
operating range and recrosses the alarm trigger threshold. If you
don’t want to generate these alarms, ensure that the check box for
the option is deselected in the Setup tab.
The alarm log file is a record of alarm incidents. Using the Alarm
Log Setup editor, you can specify where you want the alarm log file
stored, and when - if ever - you want log files created and deleted.
3. For each HMI tag you want to monitor, specify the alarm
conditions in the Tags editor. You can define alarms for analog and
digital tags, but not for string tags.
For more information about how this feature works, see “Thresholds”
on page 11-2.
This option applies to all analog alarm tags in the HMI project.
When this check box is selected, RSView generates alarms when the
value of an analog tag moves back towards the normal operating
range, and recrosses the alarm trigger threshold. For an example,
see page 11-3.
You should match the maximum update rate to the rate at which you
expect tag values to change. For example, if you are monitoring
temperatures that fluctuate slowly, you can check for alarms less
frequently than if you are monitoring rapidly-changing manufacturing
processes.
2. To log and print alarms on the active HMI server only, click Only
log and print alarm messages on the active server.
Alarm severities
Alarm incidents
3. Select a check box for the destination at which you want to log the
alarms. You can log to the alarm log file, to a printer, or to both.
Alarm severities and incidents are logged as follows:
Alarm What is logged
4. For each alarm severity, specify how you want the alarm to be
annunciated.
The sound for the internal bell can come from your computer’s
speaker or from a sound card.
You can choose from the sounds that come with Windows, or you
can install additional sound files. For information about installing
drivers and assigning sounds, see your Windows documentation.
5. Click OK.
Alarm messages appear in the description field of the alarm log file
only. You cannot display them in alarm summaries.
To use the default messages for all alarms and alarm events, do not
change anything. The default messages are used automatically. Alarm
events use system messages if you don’t specify a log message string
using the /L parameter with the AlarmEvent command.
Do not give placeholders too much space, or your messages might not
fit in the alarm log file. In the example above, the tag name has
10 spaces (\10N).
The user default messages are messages you create to replace the
system default messages.
Your message can say whatever you want, and can use both words
and placeholders. For a list of placeholders, see “System default
messages” on page 11-27.
To create a user-default
message, type a message in
the appropriate box.
To select the user message as the default message, click the User
Defaults button when you are setting up analog and digital alarms.
Custom messages
To create a custom message, type any message you want. For more
information see:
Alarm log remarks can also be printed. You cannot display alarm log
remarks in alarm summaries.
The AlarmLogRemark command has parameters that let you add a text
comment, the alarm severity, and the tag name to the alarm log file.
Other parameters let you prompt the operator for the text part of the
remark at run time, and log the remark to a printer as well as to the
alarm log file.
At run time, only one Alarm Log Remark dialog box is displayed at a
time, and the operator must respond to the dialog box before the next
one is displayed.
by importing tags into the tag database using the Tag Import and
Export Wizard. For information about using the Tag Import and
Export Wizard, see page 9-24.
To set up an alarm for an existing tag, click the tag in the Tag Database
spreadsheet, and then click the Alarm check box. Click the Alarm
button to open the Analog Alarm or Digital Alarm dialog box.
1. Set up the alarm threshold, and then choose the message that will
appear if the threshold is crossed.
2. Set up the messages that are sent when a tag goes out of alarm and
when an operator acknowledges an alarm.
2. Click a threshold.
You do not have to set up all eight thresholds, but the ones you do
use, you must set up in ascending order. For example, you can set
up thresholds 1, 2, 5, and 8, as long as you set them up in that order.
If you click Custom Message, type the message in the File and/or
Printer boxes. You can use both words and placeholders.
When you click another threshold, the information you set up for
the previous threshold is saved.
2. Select the file and printer messages for when a tag goes out of
alarm, and for when an operator acknowledges an alarm.
When the HMI server detects the acknowledge bit changing from
0 to 1, the HMI server acknowedges all alarms for tags associated
with this acknowledge bit, and logs a remote acknowledgement
message to the alarm log file. The bit is set only once per
acknowledgement.
Set up the messages that are sent when a tag goes out of alarm and
when an operator acknowledges an alarm.
Severities are set up in the Alarm Setup editor. For details, see
“Setting up alarm severity” on page 11-24.
If you click Custom Message, type the message in the File and/or
Printer boxes. You can use both words and placeholders.
2. Select the file and printer messages for when a tag goes out of
alarm and when an operator acknowledges an alarm.
If you click Custom Message, type the message into the File and/or
Printer boxes. You can use both words and placeholders.
When the HMI server detects the acknowledge bit changing from
0 to 1, the HMI server acknowedges all alarms for tags associated
with this acknowledge bit, and logs a remote acknowledgement
message to the alarm log file. The bit is set only once per
acknowledgement.
IMPORTANT You must run the Alarm Log Setup program on the
same computer as the HMI server that is monitoring
tags for alarms. If you run the Alarm Log Setup program
on a computer that does not contain an HMI server set
up to monitor tags for alarms, the settings will have no
effect.
2. If you want to change where the log files are stored, specify a new
path.
When log files are created, they are stored in the folder you specify
here.
3. Click OK.
4. If the log path is not located on the same computer as the HMI
server, you must change the security account under which the
alarm log program files run. For details, see “Setting up security to
allow alarm logging to a remote computer” on page 11-53.
Log files are saved in the directory you specify on the Logging tab.
the schema for the ODBC alarm log table on page D-2.
2. Under Start New Files, click an option to specify when you want to
have new files created. For details, see the topics on the pages that
follow.
When the operator presses the button at run time, a new alarm log
file is created at the HMI server, and all subsequent messages are
logged to the new file.
To manage disk space if a log file grows too large, stop alarm
monitoring, delete the alarm log file, and then restart alarm monitoring.
For details about how to monitor disk space on computers running
HMI servers, see page 28-4.
You cannot delete an alarm log file while RSView is monitoring alarms.
Alarm log files are deleted only when a new file is created. If your
application creates a new file each day and deletes the oldest file every
third day, your project will have files for the three previous days’ data,
as well as a file for the current day.
2. Under Delete Oldest Files, select one or both check boxes and
then type a number to specify when to delete the log files.
If you do not want files deleted, leave the check boxes under Delete
Oldest Files blank.
After Maximum Time Files are deleted after the maximum time
has expired. For example, if two days is the specified time, files are
deleted at midnight of the third day, so you always have data for the
current day and the two previous days.
After Maximum Files The oldest log file is deleted after the
specified maximum has been reached. The files currently being
logged to are not included in this number. For example, if you
type 10, you will have a maximum of 11 alarm log files at any
time—10 old ones and the current one. When a new set is started,
the oldest file is deleted.
If you have set up File Management to delete the oldest files when a
new one is started, and you are exporting data to an ODBC database,
make sure you export the data before the oldest file is deleted.
If you have set up file management to delete the oldest files when a new
set is started, and you are exporting data to an ODBC database, make
sure you export the data before the oldest files are deleted.
For information about the contents of the alarm log ODBC tables, see
page D-2.
1. In the Alarm Log Setup editor, click the Central Logging tab.
4. Specify the name of the ODBC data source. To browse for the
data source name, click the Browse button.
If the target table does not exist, and if you have a connection to the
database, you can create the target table. Type the target table name
and then click Create Table.
6. If the ODBC database and HMI server are not located on the
same computer, you must enter a User ID and password to
7. Click OK.
For information about the contents of the alarm log ODBC tables, see
page D-2.
If the table in the database to which you are attempting to export data
is not ODBC compliant, the export will fail. If an ODBC- compliant
table does not exist, RSView will try to create it.
When you export data to an ODBC table, RSView keeps track of the
data that was exported in a control file called Alarm.exp. This file is
located in the log path where the .dat files are stored. The next time you
export data, only the newest data is exported. If the control file is
deleted, all the alarm log data in the .dat files are exported when you
issue the export command.
If you have set up file management to delete the oldest files when a new
set is started, and you are exporting data to an ODBC-compliant
When the operator presses the button, the contents of the alarm log file
are exported to the ODBC database.
For information about the contents of the alarm log ODBC tables, see
page D-2.
If you change the alarm log setup at run time, the changes take effect
immediately.
1. Open the Alarm Log Setup editor by doing one of the following:
6. Click This user, and then type the name and password of a user
that has access to the network share or database.
7. Click OK.
10. Click This user, and then type the name and password of a user
that has access to the network share or database.
8. Click OK.
11. Click This user, and then type the name and password of a user
that has access to the network share or database.
MM is the month.
DD is the day.
n is the sequence letter (‘a’, ‘b’, ‘c’, and so on). This letter indicates
the sequence in which the files were created. You can have up to
26 files (‘a’ to ‘z’) per day. At midnight, the sequence starts at ‘a’
again.
The contents of the alarm log files depend on how you set up alarm
severities in the Alarm Setup editor.
For information about the contents of the alarm log ODBC tables, see
page D-2.
You can choose to display the contents of alarm log files stored either
on the local computer, or on a remote computer, and you can select the
number of log files to be displayed in the alarm log viewer. Each alarm
log file is displayed in a separate tab in the alarm log viewer.
You must include the quotation marks, because there are spaces in
the parameter.
At run time, the viewer may appear behind the RSView SE Client
window. This is the result of operating system rules. You can either
bring the viewer to the front manually, or you can work around this
problem programmatically. For details about a programmatic work-
around, see technical note P9029 in the Rockwell Software Support
Library.
At run time, operators can use the alarm summary to view and interact
with the alarms.
3. Drag the mouse to create a box approximately the size you want
for the alarm summary.
You can edit the alarm summary object as you would any other
graphic object. You can move it, resize it, and so on. You can also
use this object in other graphic displays by dragging it from one
display and dropping it in another.
Inserting headings
The Insert menu contains the items that can appear in the summary. To
add a heading for an item, click the item on the Insert menu. You can
add as many items as you want and place them in any order you want.
To resize an item, click the item and then drag a handle with the
mouse.
When you move or resize the box above the line, or the one below
the line, you move or resize its twin as well.
To edit the the text in a box, double-click the box. The Modify Text
dialog box appears. Type the new text in the To box, and then
click OK.
Choose the font, style, and size you want. When you are finished,
click OK.
To increase the size of the header area so a large font is more easily
displayed, drag the divider down.
To set up colors
3. Click a color box to open the color palette, and then click a color in
the palette.
4. To set up the blink style for an item’s state, click Blink and then
select the blink colors.
Text and Background are the colors the message initially appears in.
If you click Blink, the default blink colors are the text and
background colors reversed.
Formatting buttons
You can specify which buttons you want on the button bar and where
you want the bar located.
2. In the Buttons dialog box, select or clear the check boxes that
correspond to the buttons you want to add to, or remove from, the
alarm summary.
The table on the pages that follow describes what the buttons do.
If you select the Execute check box, the Execute Command dialog
box appears. For information about using the Execute button, see
“Using alarm data with commands” on page 11-77.
In addition to providing Filter and Sort buttons that the operator can
use at run time, you can filter or sort alarms permanently at design time.
The result of the design-time filter or sort operation is retained each
time the summary is activated at run time. For more information see
“Choosing data” on page 11-67.
To specify the location of the button bar, click Button Bar Position on
the Format menu, and then click a location. In the following
illustration, the button bar is on the left.
Using Filter
Using Sort
Alarm information can also be filtered and sorted at run time, but
changes are not saved.
To display tag names with the names of the areas they belong to, click
Display full tag name.
Filtering data
2. In the Filter dialog box, select the check boxes that correspond to
the items you want to exclude from the alarm summary.
Type or select the tag names you want to appear in the alarm summary.
To include tags from a specific area only, type the area name.
By default, the Area and Tag Names box contains * which means all
tags are displayed from the home area (the area in which the graphic
display is located). For details about the home area, see page 5-9.
Enter each area or tag name on a separate line. You can use wildcards
to select tags.
/Powertrain::*
or
/Powertrain
To collect alarm transactions from the current area for the tag name
Coolant_East, type:
Coolant_East
To collect alarm transactions from the current area for all tags whose
names begin with Coolant, type:
Coolant*
/Powertrain::Coolant*
/Press::FlowValve*
To collect alarms from more than one HMI server, you can type:
/Powertrain::*
/Press::*
You can also use the Areas and Tags buttons to browse for area or tag
names rather than typing them.
Tag placeholders
You can also use tag placeholders to specify the area or tag names you
want to appear in the alarm summary.
/#1::*
or
/Area1/#1/Area3::*
To display alarm transactions from a specific area for a tag whose name
you want to specify at run time, type:
Area::#1
Area::Folder/#1/*
If you use tag placeholders, at run time you must specify the tag or
folder name each placeholder represents, either by using a parameter
file or by specifying the tag or folder names as parameters to the
Display command. If you use a parameter file, it can contain wildcards.
#1 = bean_weight
#2 = bean_level
#3 = bean_temp
To run the display called Canning with the Beans parameter file, type:
Only the tag types that are checked, appear in the alarm summary. To
include all alarms, leave both Analog and Digital checked.
Alarm States
If you leave the Out of Alarm state unchecked, the alarm summary item
changes color when the tag goes out of alarm. Tags that are out of
alarm remain in the alarm summary until they are acknowledged.
If you want to see only the tags that are in alarm in the summary, click
Only show tags currently In Alarm. Digital change of state alarms and
InAndOutOfAlarm events are not displayed in the alarm summary
when you select this check box.
Alarm Severities
Out of alarm messages do not have severities, so if you select the Out
of Alarm option all out of alarm messages will be shown whether or
not you show the InAlarm message for a given severity.
With the Execute button, you can specify a command or macro that
operators can run with reference to the highlighted alarm in an alarm
summary. The Execute command can be appended with tag
information derived from the highlighted alarm - for example, the area
name, tag name, alarm type, severity, value, date and time, and the tag
type.
For details about using alarm data with commands, see page 11-77.
X At run time, with data populating the alarm summary, do one of the
following:
With the Identify button, you can specify a command or macro that
operators can run when a tag is in alarm. Use this button to provide
information about an alarm. For example, use the Display command to
open a display that contains instructions about how to handle a motor
that is running too fast.
1. In the Tags editor, click an analog or digital tag for which you have
set up an alarm.
When you use the Identify command, the command or macro runs
whether or not the tag is in alarm.
Using parameters
Severity and value are shown only for alarms of type IntoAlarm. For
alarm types OutOfAlarm and IntoFault, the severity is 0.
To include the area name in the parameters passed to the command for
the Execute button, select the Insert Area name check box.
If you select the Insert Area name check box, the Area name appears
automatically between the first and second word you type in the
Execute Command Text box. Because you cannot change the position
of the area name, be sure the command shown at the bottom of the
dialog box is syntactically correct before you click OK.
If you select the Tag name check box, to pass tag names as arguments
to the Execute command text, the tag names always include the area
name, whether or not areas are displayed in the alarm summary.
At run time, the area name is the area of the alarm that is highlighted
in the alarm summary.
If you set up the Execute button to run a custom program, and you
copy the alarm summary from one application to another application,
you must ensure that the custom program is available in the new
application, otherwise the Execute button will not run the program.
To do this, click the Data menu, and then click Display full tag name.
You can suppress alarm monitoring for tags. This is useful for testing
or performing repairs or maintenance on equipment.
To suppress more than one tag, use a wildcard. The wildcards are:
The Suppressed List shows which tags are suppressed—that is, which
tags are not being monitored for alarms.
operator comments.
Key concepts
Destinations
If you also set up local log files, you can use them to buffer information
while communications with the database are lost.
For example:
Category
Severity
Audience
RSView does not make use of the Engineer category. Selecting this
option has no effect for messages generated by RSView.
The Secure audience allows auditing tools, such as those required for
US Government 21 CFR Part 11 compliance, to track system activity.
For details about the schema for the ODBC database, see Appendix D,
The ODBC database schemas.
2. Fill in the fields as described in the sections that follow. To save the
changes, click Apply. When you are finished, click OK.
Browse button
2. In the Browse for Folder dialog box, click the folder in which you
want to create the log file.
3. Click OK.
Maximum log size Type or select the maximum size of the log file in
kilobytes.
Do not overwrite events Select this option if you don’t want the
system to overwrite any events in the log file. To prevent the log file
from becoming full, clear the log file manually, as described below. If
the log file becomes full, new events are discarded.
3. Browse for the folder in which you want to save the file.
You can also specify that messages remain in the local log file for a
period of time after they have been exported to the ODBC-compliant
database. This is useful in the event of a network failure, or any other
reason that causes the database to be unavailable. In this case, the
messages remain in the local log file until the buffer time expires. If the
ODBC-compliant database becomes available during that time, the
buffered messages are then exported to the database.
Buffer message locally for up to: Type a number, and then select a
time interval to specify how long messages should remain in the local
log file before they are deleted.
Data source name Type the name of the ODBC data source. To
browse for the data source name, click the Browse button.
Browse button
Target table Type the name of the target table in the ODBC-
compliant database. To browse for the target table, click the Browse
button.
If the target table does not exist, and if you have a connection to the
database, you can create the target table. Type the target table name and
then click Create Table.
Login required If the ODBC database and HMI server are not
located on the same computer, you must enter a Database user ID and
password to connect to the database. Select the Login Required check
box, and then type the user ID and password.
To route messages
2. Select or clear check boxes for the messages types you want to log,
and the audiences you want to receive them.
IMPORTANT RSView does not log any messages for the audience
called Developer. Selecting check boxes for the
audience Developer has no effect.
If you are using a network share or UNC path, click This user,
and then type the name and password of a user that has access
to the network path or database.
If you are using a mapped network drive, click Interactive user.
8. Click OK.
If you are using a network share or UNC path, click This user,
and then type the name and password of a user that has access
to the network path or database.
If you are using a mapped network drive, click Interactive user.
9. Click OK.
Diagnostics List
Status bar
You can detach (undock) the Diagnostics List from the main window,
and then move the Diagnostics List anywhere on the screen.
To undock the Diagnostics List, drag the grab bars at the bottom left
of the Diagnostics List. If you can’t see the grab bars, drag the top edge
of the Diagnostics List to make it a bit larger.
To detach the
Diagnostics List, drag
the grab bars.
When the Diagnostics List is undocked, you can make it any size you
want, for example to view more than one message at a time. To resize
the bar, drag an edge or corner until the bar is the size you want.
To clear messages, click the Clear or Clear All button. Clear removes
the top message. Clear All removes all the messages. Clearing a message
in the Diagnostics List does not delete the message from the
Diagnostics log file.
You must include the quotation marks, because there are spaces in
the parameter.
At run time, the viewer may appear behind the RSView SE Client
window. This is the result of operating system rules. You can either
bring the viewer to the front manually, or you can work around this
problem programmatically. For details about a programmatic work-
around, see technical note P9029 in the Rockwell Software Support
Library.
displayed in trends.
A data log model defines which tags to log data for, when to log the
data, and where to log the data. In the model you also specify the
format of the log files (file set, or ODBC) and when to create and
delete the files, or records when using an ODBC-compliant database.
If you use a file set, tag values are stored in proprietary-format files.
You cannot view the contents of these file sets, except in trends.
If you need to use data in multiple formats, define multiple data log
models for the same tags.
RSView names the log file sets using long file names. The maximum
length of a log file set’s name, including its path, is 200 characters. File
sets are named using the following format for the file name:
MM is the month.
DD is the day.
<Log File Identifier String> is a text string you can specify to help
identify the log file. The maximum string length is 20 characters.
For a details about the contents of the tables, see page D-5.
ODBC backup files are stored as binary files with the extension .obf.
You cannot view the contents of the .obf files.
If you specify a backup path for an ODBC model, RSView names the
backup log files as described on page 13-3.
There are two ways to prepare tables for data logging to an existing
database:
Set up the RSView data log fields in the existing ODBC tables
before setting up your data log model.
1. Add fields for the data log data to the tables in the ODBC
database. See the example on page 13-10 for information about the
steps you need to complete to add fields to an existing table.
The section “Data log tables” on page D-5 describes the order and
type of fields needed to log data to an ODBC database. Edit the
tables as described in the documentation for the ODBC database
you are using.
1. Specify the name of the existing ODBC data source in the ODBC
Data Source field of the Data Log Models editor. For more
information, see “Setting up a model” on page 13-7.
2. Open the Data Log Models editor by doing one of the following:
Right-click the Data Log Models icon and then click New.
Drag the Data Log Models icon to the workspace.
This text string forms part of the file name for the data log files.
Data log files are named using long file names. For more
information about how log file sets are named, see page 13-3.
If you choose the ODBC storage format in step 4, long file names
apply to the backup files only.
You can change the log file identifier string at run time, as described
on page 13-37. However, the run-time change affects the current
data log session only. When you stop and restart the model RSView
uses the string you set up here.
The file set stores tag values in a proprietary format for fast
performance.
5. If you choose file set and are logging string tags, you must specify
the number of characters used to log the string.
Type the path and file name of an existing ODBC data source. If
the data source does not yet exist, use the ODBC Data Source
Administrator to create it.
If you are creating a new database, you can create the tables
automatically at the data source you specified. To do this, type
the table names in the table boxes, and then click Create Tables.
When you save the data log model, RSView informs you if the
fields in a selected table are not in the order or of the type
required to log data. In this case you must edit the table as
described in the documentation for the ODBC database you
are using. For information about the order and type of fields
needed to log data to an ODBC database, see page D-5.
8. If the ODBC database and HMI server are not located on the
same computer, you must enter a User ID and password to
connect to the database. Click the Login Required checkbox and
then type your user ID and password.
To log in and create the tables, you must have access to the SQL Server.
3. In the Select Data Source dialog box, specify the data source you
created, and then click OK. If required, enter your login ID and
password.
6. Click Add.
In the Type field, click the type that most closely matches the SQL
Data Type for the field you are adding, as listed in the tables starting
on page D-5.
If you want to edit a table that already exists, log in, click the table name,
and then click View. The order of the data log fields must match the
order listed in the tables starting on page D-5. If you add the data log
fields to an existing table, the data log fields must appear first in the
table. However, you can use different names for the data log fields.
1. In the Select Table dialog box, select FloatTable, and then click
Index.
3. In the Index Fields field select DateAndTime (or the name you
assigned to the first field in the FloatTable).
RSView also checks the status of the primary path or ODBC database
if the secondary or backup path becomes unavailable, and will switch
back if possible. If both paths are unavailable, RSView buffers the data.
If the buffer fills and both paths are still unavailable, RSView empties
the buffer (the data in the buffer is lost) and begins storing new data in
the buffer. RSView continues checking both paths until one becomes
available.
If the data log file is locked, data is buffered for the time specified for
Maximum Time To Buffer in the Advanced Configuration dialog box,
and then a new set of files is created on the primary path. If the
secondary path is not set up, the data is buffered for 10 minutes (the
default value for maximum time). If the maximum time is set to 0, a
new file is started immediately.
If the model is logging to the secondary path and the file is locked, the
behavior is the same: the data is buffered, and then a new file is created
when the specified time period has elapsed.
You can also switch back to the primary path or ODBC database
manually, using the DataLogSwitchBack command (see page 13-19) or
the DataLogMergeToPrimary command (see page 13-20).
For models that use the file set format, RSView creates a new file set
each time the logging path changes.
You can specify the primary and secondary file paths for a file set, and
the ODBC backup file path by editing the data log model in the
RSView Studio Application Explorer, as described next.
You can also change the log paths at run time using the RSView
Administration Console, as described on page 13-36.
1. In the Data Log Models editor, click the Paths tab. If you are using
the ODBC storage format, go to step 3.
2. If you are using file sets, specify the primary path where you want
to store the data log files.
For file sets, if you used this default path as your primary path,
specify a different path for the secondary path.
The amount of time RSView buffers the data may vary slightly from
the time you specify, depending on the log rate for periodic models
or the frequency with which tag values change for on-event models.
In all other cases, RSView checks whether the primary path has
become available after the specified time has elapsed.
Minimum free disk space required for auto switchback
(MB) For data log models that use file sets, specify a high enough
value to prevent RSView from switching between paths frequently
because of low disk space on the primary path.
RSView does not use this value to trigger a switch to the secondary
path. The value is used only to determine whether to switch back to
the primary path automatically after the time to retry has elapsed.
1. On the computer on which you want to run a data log model, click
the Windows Start button, and then click Run.
1. On the computer on which you want to run a data log model, click
the Windows Start button, and then click Run.
4. Click This user, and then type the name and password of a user
that has access to the network share or database.
5. Click OK.
You can switch back to the primary path manually using the
DataLogSwitchBack <component> command or the
DataLogSwitchBack * command.
You can make it possible for operators to issue these commands at run
time. For example, you can create a button object and use the
DataLogSwitchBack <component> command as the press action.
If your data log model uses the ODBC format, data is added
continually to the same database, and this section does not apply. If
your data log model uses file sets, RSView logs the data to sets of files.
You can set up your application to create new file sets, over these time
intervals:
periodically
at specified times
never
Log files are saved in the folder you specify on the Paths tab.
If the hard disk space for the primary path is full, data logging switches
to the secondary path, if enabled, until space becomes available on the
primary path. If you do not set up a secondary path, when the primary
path runs out of disk space data logging stops and no more log files are
created.
1. In the Data Log Models editor, click the File Management tab.
2. Under Start New Files, click an option to specify when you want
new files created. For information about the different options, see
the topics that follow.
To manage disk space if a log file grows too large, stop data logging,
move or delete the data log file, and then restart data logging. For
details about monitoring disk space on computers running HMI
servers, see page 28-4.
If your data log model uses the ODBC format, these commands create
a new set of backup files if RSView is logging to the backup path when
the command is issued. If RSView is logging to the ODBC database,
RSView logs an End Snapshot and then a Begin Snapshot when you
issue these commands.
If your data log model uses file sets, these commands start a new file
set regardless of when new files have been set up to start in the Data
Log Models editor. The new file set is created in the same path that
RSView is currently logging to.
If your data log model uses file sets, you can delete file sets after a
specified period or once a specified number of file sets has been
created. If you never want file sets deleted, leave the check boxes under
Delete Oldest Files blank.
Data log file sets are deleted only when a new file set is created. So, if
your project creates a new file set each day and deletes the oldest file
set every third day, your project will have file sets for the three previous
days’ data, as well as a file set for the current day.
1. In the Data Log Models editor, click the File Management tab. If
you are using the ODBC storage format, go to step 3.
2. If you are using file sets, under Delete Oldest Files, select one or
both check boxes, and then type a number to specify when to
delete the file sets. If you select both check boxes, files sets are
deleted after the maximum time or after the maximum number of
files is reached, whichever happens first. If you do not want files
deleted, leave the check boxes blank under Delete Oldest Files.
After Maximum Time File sets are deleted after the maximum
time has expired. For example, if two days is the specified time, file
sets are deleted at midnight of the third day, so you always have data
for the previous two days and the current day.
After Maximum Files The oldest log file set is deleted when the
specified maximum is reached. The files currently being logged to
are not included in this number. For example, if you specify 10, you
will have a maximum of 11 data log file sets at any time - 10 old ones
and the current set. When a new set is started, the oldest file set is
deleted.
When you have finished specifying options for deleting file sets, go
to “Specifying when to log data” on page 13-29.
3. If you are using the ODBC storage format, select the check box,
After Maximum Time. Type a number to specify when to delete
the records, and then select whether the number is measured in
days, weeks, or months.
If you do not want records deleted, leave the check box blank. This
option purges records from the ODBC database only, not from the
backup files. RSView deletes ODBC backup files only when the
DataLogMergeToPrimary command is issued.
1. In the Data Log Models editor, click the Log Triggers tab.
To log periodically
1. Click Periodic.
2. In the Interval field, type a time, and then click a time unit to
specify how often tag values will be logged. All tags in the model
will be logged each time this interval expires.
Do not set the interval faster than the OPC update rate or OPC
topic poll rate, or you will log redundant data.
You can change the periodic log rate at run time, as described on
page 13-37. However, the run-time change affects the current data
log session only. When you stop and restart the model, RSView uses
the log rate you set up here.
Logging on change
On-change logging is used to log only tags whose values have changed,
when the change occurs.
To log on change
1. Click On Change.
2. In the Maximum Update Rate list, click the fastest rate at which
data servers should send changes in tag values. Use a larger value to
prevent rapid tag changes from overloading the HMI server.
4. In the Heartbeat field, type a time, and then click a time unit to
specify how often tag values will be logged even if no change has
occurred. If you do not want to use the heartbeat, type 0.
The heartbeat ensures that the data in the log file is current. The
heartbeat is also a good way to ensure that data logging is working
and acquiring valid data.
Logging on demand
Logging on demand means that data is logged for a model only when
the DataLogSnapshot command is issued. When the
DataLogSnapshot command is executed, values for all tags in the
specified model or models are logged.
To log on demand
1. Click On Demand.
2. Run the model or models for which data will be logged. To run a
model, select the model in the Startup editor or issue the
DataLogOn <component> command where component is the name
of the data log model.
The DataLogSnapshot * command records tag values for all tags in all
running models at the instant the command is executed.
You can use these commands anywhere you can enter an RSView
command or macro. For example, enter the command as the action for
an event.
Operators can also use these commands at run time. For details, see
“Providing operators with a way to log on demand” on page 13-33.
When the tag called motor_fault goes into alarm, and the tag called
new_batch_started is 1, the DataLogSnapshot <component>
command runs. All tags in the model will then be logged (not just the
tag in alarm).
To combine logging
creating a display key or client key and using the command as the
press action—operators can then press a key to take a data log
snapshot.
To specify tags
1. In the Data Log Models editor, click the Tags in Model tab.
2. In the Tag(s) to Add box, specify the tags that will be logged. To
do this, do one of the following:
To remove a tag from the Tags in Model box, click a tag, and then
click Remove. To remove multiple tags, Shift-click the tags and then
click Remove. To remove all the tags, click Remove All. Tags that
you remove appear in the Tag(s) to Add box. Delete the tags you
want to remove from the Tag(s) to Add box before you click OK.
1. In the Application Explorer, open the data log model you want to
change.
IMPORTANT If you delete a tag from a data log model, and the tag is
also used in a trend object, be sure to remove all
references to the deleted tag from the trend object.
2. Open the Data Log Model in which you want to change the log
path.
You can change the following data log parameters at run time without
editing the data log model:
These run-time changes take effect immediately, but are lost if you shut
down the application and then restart it (the changes are not retentive).
You can change the rate at which periodic logging occurs at run time
using the command:
where
<value> is the numeric portion of the time interval for the log rate.
For example, if you want to log data every 20 seconds, the value is
20.
[unit] is the time unit of the log rate: hundredths, tenths, seconds,
minutes, hours, or days. If you omit the unit parameter, the default
is seconds.
The change to the logging rate applies during the current logging
session only. When you stop and restart logging, RSView uses the
logging rate you specified in the the data log model.
You can change the identifier string that forms part of the file name in
log file sets. The log file identifier string is also used in the names of
ODBC backup files. To change the string, use the command
DataLogRenameFile <component> <LogFileIDString>, where
The change to the log file identifier string applies during the current
logging session only. When you stop and restart logging, RSView uses
the log file identifier string you specified in the the data log model.
You can display historical data in a trend by assigning a tag from a data
log model to a pen.
There are many ways to start and stop data logging. Choose the way
that works best for your project.
To stop all the components that are running on the HMI server,
including data log models, event components, derived tag components,
and alarm monitoring, stop the components running on the HMI
server manually.
To stop data logging, you can also use any of the methods described
below:
Setting up events
Events are expressions that trigger actions. Expressions are equations
containing tag values, mathematical operations, if–then–else logic, and
other built-in RSView functions. Actions are RSView commands,
symbols, or macros. An action could, for example:
This chapter describes how to use the Events editor to create events. It
does not describe the expressions used to produce the event’s actual
function. If you do not know how to use expressions, see Chapter 20,
Creating expressions.
Set the maximum update rate for the event component in the
Events editor’s Event Setup dialog box.
You must set the maximum update rate separately for each event
component.
The maximum update rate also determines the fastest rate at which
data servers send changes in tag values.
Set the update rate as fast as, or faster than, the rate at which the values
of tags used in the expressions change, unless it is desirable to miss
changes in tag values.
1. On the menu bar, click Setup and then click Event Setup.
4. Click OK.
Creating events
An event consists of two parts: an expression and an action. When the
expression changes from false on the previous evaluation to true on the
current evaluation, the action is triggered.
To create an event
For information about macros and symbols, see Chapter 23, Setting
up navigation.
2. To disable the event, click to clear the Enabled check box. When
the event component runs, this disabled event is not evaluated.
5. Click Accept.
Editing events
You can edit events during development or when you run the
application.
To edit an event
2. Use the Prev and Next buttons to move among events. Make the
required changes.
If you change the event component while running the application, the
changes don’t take effect until you stop running the component and
then restart it.
Setting up security
Set up security in your application to prevent users from accessing
certain parts of the system.
This chapter describes the RSView security system, and outlines how
to:
Only users with the specified security code can run the secured
commands, open a graphic display, or write to secured HMI tags.
In this way, the security code determines the user or group’s level of
access to the system.
Only users with the specified security code can open the application
in RSView Studio, or the RSView Administration Console.
In the User Account editor, the following security codes are assigned:
users who belong to the Operators group can access the Boiler
graphic display and the DataLogOn command. This group can also
access any graphic displays that have no security assigned to them.
Gail has full access to the system at run time, and can open the
application in RSView Studio, or the RSView Administration
Console.
users who log on to the system as Guest can access the Boiler
graphic display only.
graphic displays, OLE objects with verb animation, and tags you
want to secure.
If you want to create new users, create the accounts in Windows. For
details about creating users and groups in Windows, see Windows
Help.
Any users you don’t select for the RSView user list will not have access
to the parts of the application you have secured.
This is the RSView
User Accounts editor.
Using this editor, you
can add Windows
users or groups to the
list of users in
RSView.
You can modify a user account’s security codes after you have added
the user to the RSView user list.
2. In the Security Codes area, select the check box for each security
code you want users to have access to by default.
3. Click OK.
To add users from a Windows domain, your network must have at least
one Windows server acting as a domain controller.
You can use local workstation domains provided that all computers
participating in the application have identical sets of user accounts and
passwords, are in the same Windows workgroup, and all users
participating in the workgroup must have administrative rights.
2. In the Windows Domain list, click the name of the domain from
which you want to add users.
5. Click OK.
The name of the user or group is deleted from the RSView User
Accounts list. The user or group is not deleted from the Windows
domain.
The security codes of the user or group are deleted from the User
Accounts editor.
If you remove users from the Windows domain, they are not removed
automatically from the RSView user list. You must remove the users
from the RSView user list manually.
2. In the RSView User Accounts list, click the user name or group
name you want to delete.
2. In the Security Codes area, select the check box for each security
code you want this user to have access to.
3. Click Accept.
Any macro component can be a login or logout macro and can contain
any RSView command. For example, a login macro could contain a
command to bring up a graphic display for an area of the plant. A
logout macro could contain commands to redefine sensitive keys.
For the login and logout macros to be executed, they must be in the
area from which the Login or Logout command was executed.
1. In the User Accounts editor, click the name of the user or group
whose account you want to change.
2. Type the name of a macro in the Login Macro box and Logout
Macro box.
These macros run each time this user logs in and out. For more
information about macros see “Login and logout macros” on
page 15-10.
4. Repeat steps 1 through 3 for each user to whom you want to assign
a login or logout macro.
You can also secure commands using the Signature button in a graphic
display, to control the actions an operator can perform at run time, for
example:
issuing a command.
For details about using the Signature button, see “Recording and
authorizing run-time changes using electronic signatures” on
page 17-248.
Security codes
RSView has 17 security codes: an asterisk (*) and the letters A
through P. The asterisk is for unlimited access, and the letters are for
limited access.
The letters are not hierarchical—all letters provide the same level of
security. You do not have to use all of the security codes, nor do you
have to assign the codes in a particular order. For example, you can
choose to use only the codes D and P, and you can assign P before you
assign D.
The Unspecified_Command
The first record in the spreadsheet is called Unspecified_Command.
Any commands or macros that are not listed in the spreadsheet use the
security code selected for the Unspecified_Command.
If you change the default to a letter, you have to list only those
commands you want users who are assigned this code to have access
to. This is referred to as security by exclusion.
3. In the Security Code list, select a code for the command or macro.
Ensure you include the Login and Logout commands and assign
them the * security code.
3. In the Security Code list, select a code for the command or macro.
You can also secure objects in a graphic display using the Signature
button, to control the actions an operator can perform at run time, for
example:
issuing a command.
3. Click OK.
7. Click Apply.
Assign security to an HMI tag to restrict write access to the tag. This
prevents users who do not have the tag’s security code from changing
the tag’s value. You can assign security to HMI tags only. You cannot
assign security to data server tags.
You can also secure tags using the Signature button in a graphic display,
to control the actions an operator can perform at run time, for
example:
issuing a command.
For details about using the Signature button, see “Recording and
authorizing run-time changes using electronic signatures” on
page 17-248.
4. Click Accept.
To secure an application
3. Click OK.
To allow users to log out at run time, include a way for them to issue
the Logout command. For example, create a button and use the Logout
command as the press action.
You can also set up an RSView SE Client to log out automatically after
a specified period of inactivity. For details, see Help for the SE Client
wizard.
2. The current user’s logout macro is executed and the user is logged
out.
how to re-use the same graphic display with different sets of tags.
For details about creating and editing specific graphic objects, see
Chapter 17, Setting up graphic objects.
Docked toolbar
Drawing area
Floating toolbar
Diagnostics list
Status bar
You can hide or show toolbars using the View menu, and you can move
the toolbars anywhere on the screen.
The Object Explorer lists all the objects and groups of objects in your
display. The Object Explorer does not list objects that have been
converted to wallpaper.
You can click an object in the list to select it in your display. You can
also right-click the object to open the context menu for the object.
You can keep the Object Explorer open while you work on different
objects, and in different displays. For more information about using the
Object Explorer, see page 16-11.
The Property Panel displays the properties of the selected objects, and
shows what values are assigned to the properties. For example, the
Property Panel shows whether an object’s background style (BackStyle)
is solid or transparent. The Property Panel also lists the object’s
connections, and shows which tags or expressions have been assigned
to them.
You can keep the Property Panel open while you work on different
objects, and in different displays. For details about using the Property
Panel, see page 16-34.
The status bar describes the action performed by the selected menu
item or button. The status bar also displays the x- and y-coordinates,
and width and height, of the selected object.
Correcting mistakes
If you change your mind about something you did, undo the action. If
Undo you change your mind again, redo the action.
To undo an action
Redo
X On the Edit menu, click Undo, or on the toolbar, click the Undo
button.
To redo an action
X On the Edit menu, click Redo, or on the toolbar, click the Redo
button.
You can also zoom the graphic display to fit the size of the window.
Zoom out
To zoom in on objects
When the graphic display is resized, the relative sizes of each of the
objects in the display (also called the aspect ratio), is not maintained.
The grid can be active or passive. If you turn on Snap to Grid, the grid
is active, and all the objects you draw or position are pulled to the
closest grid point. This makes it easy to align and size objects. If you
Turn off the grid either to draw or position an element between the
grid lines. Turn on the grid and the next object you draw or place will
automatically be aligned with the grid. Turning on the grid does not
affect the placement of existing objects.
You can click Show Grid and Snap On on the View menu.
hide or show them using the items on the View menu. If there is a
check mark beside the toolbar name, the toolbar is visible. If there
is no check mark, the toolbar is hidden.
A toolbar that is
docked
Before you can draw an object, you must select the appropriate tool.
To select a drawing tool, click the tool in the toolbox or on the Objects
menu. When you click a tool, the pointer changes to show which tool
is active.
IMPORTANT Test mode is not the same as running the display. Test
mode does not change the appearance or position of the
display, as set up in the Display Settings dialog box.
Once you have drawn an object, you can select the object, and then edit
it. You can:
move objects.
copy objects.
duplicate objects.
For information about using the Object Explorer, see page 16-11.
Selecting objects
To select Do this
To deselect Do this
Use the Object Explorer to select an object that is hidden behind other
objects in the display, without bringing the object to the front. Objects
are listed in front-to-back order. The object you created most recently
is at the front, unless you move it back using the Send to Back option.
For details about stacking objects, see page 16-21.
You can also use the Object Explorer to highlight objects that have
animation attached, and to highlight objects with specific tag or
expression assignments. For more information, see page 16-13.
The Object Explorer does not show wallpaper objects, nor the objects
within ActiveX composite objects.
The objects are highlighted in red in the Object Explorer and in the
graphic display. If your graphic display uses a red background, the
highlighting is not visible in the graphic display.
Each object that has one or more of the specified animation types
assigned will be highlighted.
The list displays all the tags and expressions that have been assigned
to objects in the graphic display, except tags contained in embedded
variables.
5. Click OK.
Moving objects
You can move objects using the mouse or the keyboard. The keys give
you fine positioning, allowing you to move objects in small increments.
To drag objects
You can move several objects at once by selecting them all and then
dragging one of the selected objects.
2. Hold down Shift while you press an arrow key. Holding Shift is the
same as pressing the left mouse button.
Use the plus (+) and minus (–) keys to increase or decrease, per
press, the distance moved by the arrow keys.
Copying objects
To copy objects, you can:
You can drag and drop objects between displays. This is particularly
useful for copying objects from a graphic library.
3. When the object is where you want it, release the mouse button.
You can cut, copy, or paste objects using the menu items on the Edit
menu or the buttons on the toolbar.
Once you copy an object, you can paste it anywhere in the drawing area
of:
To paste objects
X Select one or more objects and then click Delete on the Edit menu,
or press Delete on the keyboard.
Duplicating objects
Unlike Cut and Copy, Duplicate does not use the clipboard.
Duplicate
1. Select one or more objects.
When you select an object, handles appear around it. Use these handles
to resize the object.
3. Drag the handle until the object is the desired size or shape.
For perfect circles and squares, hold down Ctrl while you drag a corner
handle.
When advanced objects, such as input fields, are resized, the font is
resized to fit the new boundary.
3. Hold down Shift and press an arrow key until the object is the
desired size or shape.
Arranging objects
You can arrange objects in a number of ways using the items on the
Arrange menu or the buttons on the toolbar. You can:
Send to Back moves the selected object to the bottom of the stack.
Bring to Front moves the selected object to the top of the stack.
1. Select an object.
1. Select an object.
Aligning objects
Objects can easily be aligned with each other and with the grid. Align
objects with each other when you want the tops, bottoms, or sides to
line up.
Align top
Align middle
Align bottom
Spacing objects
With Space Vertical and Space Horizontal, objects are moved vertically
or horizontally to have the same amount of space from the center point
of each object.
Centers are
separated by an equal
vertical distance.
Centers are
separated by an equal
horizontal distance.
Flipping objects
Flipping an object creates a mirror image of that object. You can flip
most objects.
1. Select an object.
Rotating objects
Use the Rotate tool to rotate an object or group of objects around an
Rotate tool anchor point.
You can also use the Rotate tool when attaching rotation animation to
a graphic object. For details about rotation animation, see “Setting up
rotation animation” on page 18-29.
You cannot rotate OLE objects, ActiveX objects, bitmaps, and text.
3. Place the pointer on an edge of the object, and then drag the object
to rotate it.
To group objects
To ungroup objects
The handles around the group are replaced with handles around
each object.
use the Property Panel to apply the same properties to all the
members of the group at once. For example, change the line width
of all objects in the group to 2 pixels.
use the toolbars to apply the same pattern style, background style,
foreground colors, and background colors to all the members of the
group.
for objects that have states, use the States toolbar to cycle through
the states and apply the same properties to the states for each object
in the group at once. When you select a group containing objects
with states, only the states that are common to all objects in the
group appear in the toolbar. For information about using the States
toolbar, see “Testing the appearance of objects in different states”
on page 16-42.
When you double-click, you are in group edit mode. In this mode, you
can select individual objects in the group and modify them. You can
also add new objects to the group.
To see what objects are selected, either look at the status bar, or use the
Object Explorer. For details about using the Object Explorer, see
page 16-11.
Use the Foreground Color palette to select a color for the outline of an
object, for text, or for hollow objects.
Use the Background Color palette to select a color for the inside of an
object or for solid objects.
For objects with patterns, you can set the color of the pattern
separately. To do this, open the object’s Properties dialog box, click the
Pattern color box, and then click a pattern color.
You can apply pattern styles to objects before or after you draw them.
Line style Click a style for the line. Line styles are available only
when the line width is 1.
Dash
Dot
Dash-Dot
Dash-Dot-Dot
Back color Click the color box to open the palette, and then click
a color for the object’s background.
Line style uses both the foreground color and background color
attributes. Foreground color applies to the line, and background color
applies to the spaces in the line. For example, to obtain the dash-dot
line, choose black as the foreground color, and choose white as the
background color. Black is applied to the dots and dashes and white is
applied to the spaces between the dots and dashes.
For trend objects, you can also customize line width and color using the
Pens tab of the Trend Properties dialog box.
You can keep the Property Panel open as you work in the Graphic
Displays editor. You can drag the panel’s borders to make the Property
Panel larger or smaller.
Setting up properties
Use the Properties tab in the Property Panel to set up the properties of
the selected object or objects.
If the property has a list of values associated with it, press Enter or
double-click the property’s row to change the property’s value to the
next available value. To select a particular value, click a value in the
list.
If the property has a dialog box (such as the Font dialog box)
associated with it, double-click the row, or click the Browse button
Browse button to open the dialog box.
Some objects that can be set up using a Properties dialog box, have
a property called (Custom) appears in the first or second row of the
grid. Double-click the row, or click the Browse button to open the
object’s Properties dialog box.
5. Press Enter or click another cell in the grid to save the change. The
selected object is updated with the new property value and its
appearance in the display changes, if appropriate.
If multiple objects are selected, you can specify which properties you
want to display in the Property Panel:
To view all the properties of all the selected objects, click All
Properties.
If a group of objects is
selected, this box shows
Multiple Selection. If only To view only properties that
one object is selected, this are shared among all
box shows the object’s selected objects, click
name and type. Shared Properties.
If a group of objects is
selected, click the Include
Grouped Objects button to
edit the properties of the
objects within the group.
The arrows indicate the direction in which the data flows between the
tag or expression and the object:
A right arrow indicates that the object sends values to the tag or
expression. The object can write to the tag or expression.
A left arrow indicates that the tag or expression sends values to the
object. The object can read from the tag or expression.
A double arrow indicates that the data flows in both directions. The
object can write to, or read from, the tag or expression.
X Click the row that contains the tag you want to delete, and then
press Delete.
Tag substitution does not work for text objects you create using the
Text tool.
To replace text
The lists under the Search for, and Replace with, boxes show the
text strings used by the objects you selected in the graphic display.
The text you type in the Search for, or Replace with boxes can be
part or all of:
an RSView command.
Browse button
The Browse button opens the Tag Browser.
In the list under the Search for box, select the text string you
want to search for.
Click the Browse button to open the Tag Browser, and then
select the tag you want to search for.
Browse button
In the Search for box, type the text you want to search for.
4. In the Replace with box, do one of the following:
In the list under the Replace with box, select the text string you
want to replace with.
Click the Browse button to open the Tag Browser, and then
select the tag you want to replace with.
In the Replace with box, type the text you want to replace with.
5. Click Replace.
If you selected multiple objects, the toolbar shows the states that are
common to all the objects.
3. To view the next state, click it in the list in the States toolbar, or
press the Down Arrow key on your keyboard.
You can also use these keys to select the next state:
2. In the Property Panel, click the State property and then click the
state you want to view.
3. To view the next state quickly, double-click the row, or press the
Enter key on your keyboard.
All objects have a default name. Once you have drawn a graphic object,
you can change its name.
The object’s name is used when logging events for the object. The
object’s name is also used with commands (for example, when using
the Invoke command to call a method, you must specify the name of
the object in which the method is implemented).
The object’s name also appears in the Object Explorer. For details
about using the Object Explorer, see page 16-11.
Tooltips appear at run time when you bring the cursor to rest over an
object for a few seconds, if the object is not disabled.
… the object’s
name changes
here.
To unlock wallpaper
To import files
1. In the Graphic Displays editor, click the Objects menu and then
click Import.
3. In the Open dialog box, click the Files of type list, and then click
the type of file you want to import.
5. Click Open.
6. If the Convert Object dialog box appears, click Yes to convert the
object to a native RSView object or click No to leave the object in
its original format.
Using bitmaps
Create bitmaps in the lowest color depth possible. The more colors you
use, the more memory that is consumed:
The Scale option in the Display Settings dialog box causes the contents
of a graphic display to change size to suit the size of the graphic
display’s window. To speed up the display of a graphic containing
bitmaps, choose Pan rather than Scale because bitmaps take longer to
draw when they are scaled to a size different from their original size.
Graphic displays that contain large bitmaps consume memory and can
be very slow to display because of the delay in loading them from disk.
look at the objects and displays to get ideas for your own
application.
drag and drop objects from the libraries into your own displays.
Use the objects as they are or change them to suit your needs.
1. In RSView Studio, click the Tools menu, and then click Options.
2. In the Options dialog box, click the Browse button, and then select
the folder that contains the library files you want to use.
Browse button
2. Right-click the Libraries icon and then click Add Component into
Application.
4. Click Open.
For example, imagine you are creating displays for a plant that cans
corn and beans. The machinery used in both processes is identical.
Instead of drawing two displays and then specifying corn-related tags
in one display and bean-related tags in another, you can create one
display and not specify any tag names. Where a tag name is required,
type a tag placeholder instead.
When the display runs, the placeholders must be replaced with tag
names. This can be done in two ways: with a parameter file, or by
specifying the tag names as parameters to the Display command.
If you are using an HMI tag, you can also add a folder name to the
placeholder. For example, #1\PV is a valid placeholder and requires
only one parameter (the folder name).
For tag placeholders in alarm summary objects, you can use wildcards
in the placeholder. For example, #1\PV* is a valid placeholder.
2. Type one entry for each unique placeholder in the graphic display,
associating the placeholder with a tag name. For example:
#1 = bean_weight
#2 = bean_level
#3 = bean_temp
For tag placeholders in alarm summary objects only, you can use
wildcards in the parameter file. For example, #1 = bean_* is a valid
parameter entry. The alarm summary would display any alarms
associated with tags beginning with bean_.
You cannot use wildcards in placeholders for any objects other than
alarm summaries.
where:
graphic displays that are opened using display list selectors. For
details about setting up display list selectors, see page 17-206.
the graphic display that opens when the RSView SE Client connects
to the application.
where:
For tag placeholders in alarm summary objects only, you can use
wildcards when you specify tag names at the command line.
Corn\Weight Bean\Weight
Corn\Level Bean\Level
Corn\Temp Bean\Temp
To run the display called Canning with the folder containing corn tags,
type:
To run the display called Canning with the folder containing bean tags,
type:
You can save the settings for the current graphic display, or you can
save the settings as the default for all new graphic displays.
Set as Default does not save the settings for the current display. To save
the settings for the current display, you must also click OK.
display type
caching
security
background color
on-screen keyboard
specify what buttons and text appear in the title bar, how often the
display is updated, and other display attributes.
specify the display’s size and position, and whether it can be resized
at run time.
Replace is the default display type. Use this option if you want the
graphic display to replace other open graphic displays when it opens.
The RSView SE Client closes any graphic display that the newly-
opened display overlaps. This way you don’t need to issue separate
commands to close the other displays.
Overlay Use this option if the graphic display doesn’t need to replace
others or appear on top. The display will layer with other displays,
overlapping some and being overlapped by others as the focus changes
between multiple displays.
Keep at Back Select this check box if you always want this graphic
display at the back. However, we recommend that you use the On Top
display type to control the layering of displays. To use Keep at Back,
you must click the Overlay option.
On Top Use this option to keep the graphic display on top at all times.
It remains on top even if another display has focus. However, if more
than one graphic display of the On Top type is open at once, the display
that appears on top is the one that has focus, or that had the most
recent focus.
PID is the name of a graphic display. /Q1 positions the first display at
the top-right corner of the screen. /Q2 positions the second display at
the top-left corner of the screen.
You can also run multiple copies without selecting this option, by using
the Display command with different parameter files for each copy of
the display.
For details about parameter files, see “Replacing tag placeholders using
a parameter file” on page 16-52.
Cache After Displaying Click Yes to load the graphic display into the
display cache when it is displayed for the first time. Placing the graphic
display in the cache makes the graphic display appear more quickly
every subsequent time, because it does not have to be read from disk.
You can have up to 40 graphic displays in the cache. Use this option for
large or complex displays only, to minimize the use of system resources.
Click No if you don’t want the RSView SE Client to load the display
into the display cache.
Always Updating Select this check box to keep the cached display up
to date. For example, select this check box to update trend data
continuously for the display, even when the display is not visible. You
can also use this option to execute VBA code in the background.
Title Bar To have a title bar appear on the graphic display at run time,
select the Title Bar check box.
If the Title Bar check box is not selected, the check boxes for the
System Menu, Minimize button, and Maximize button are not available
(because these items all appear in the title bar).
You can also type a title for the graphic display, which will appear in the
title bar at run time in place of the component name. The title can be
anything you want and can include spaces. You cannot type a title if the
Title Bar check box is not selected.
Title bar
Show Last Acquired Value Select this check box to show a graphic
display with the last known value for each HMI tag in the display until
current values arrive from the programmable controller. In many
applications, selecting this option will help display graphics more
quickly.
IMPORTANT The last acquired value can be displayed for HMI tags
only. For other kinds of tags, the last value cannot be
retained.
If you do not select this option, objects with values that have not yet
been updated will appear in outline form. The outline indicates that
data is not current, or is in error.
Selecting Show Last Acquired Value might not affect a graphic display
the first time the display starts because the HMI tags used in the display
might not be initialized and so might not have any values. To indicate
that there are no tag values, the objects appear in outline form. Once
the HMI tags have been initialized and tag values arrive, the objects
appear in their normal form.
This option does not affect objects with HMI tags that are in error. If
an object has a tag that is in error, the object will appear in outline form.
Maximum tag update rate This is the fastest rate at which data
servers send changes in tag values to the graphic display.
The default update rate is 0.5 seconds. This means that data servers will
not send updates to tag values faster than twice every second.
To minimize the need for scroll bars, the RSView SE Client tries to
position all graphic displays within the working area of the RSView SE
Client main window, unless explicitly overridden by the /X and /Y
parameters of the Display command.
To ensure the RSView SE Client main window never has scroll bars,
select the Size to Main Window at Runtime option for large displays.
Do not select this option for smaller graphic displays that are not
meant to fill the screen. However, be sure to position the smaller
displays so they are completely visible, otherwise scroll bars might
appear.
Click Use Current Size. When you save the graphic display, the size
of the window at that time becomes the default size.
Click Specify Size in Pixels, and then type a value in the Width box
and the Height box.
The window size and position you specify here can be overridden by
the RSView Display command. The Display command accepts size and
position parameters, which override the Display Settings options. For
more information about the Display command, see Appendix A,
RSView commands, or see Help.
If you do not select the check box, the graphic display cannot be resized
at run time.
When Resized Click Pan to resize the display so objects retain their
original size when the display size changes. For example, if the display
was resized to four times its original size, only one quarter of the display
Click Scale to resize the display so objects in the display are magnified
or reduced, to maintain their size in relation to the display size. For
example, if the display was resized to one quarter its original size, the
entire display would be visible - but it would all be one quarter its
original size.
Click Use Current Position. When you save the graphic display, the
position of the window at that time becomes the default position.
Click Specify Position in Pixels and then type values in the X and Y
boxes. These boxes specify the position of the window in relation
to the top-left corner of the RSView main window. The x-value
positions the window from the left edge of the main window and
the y-value positions the window from the top of the main window.
The window size and position you specify here can be overridden by
the RSView Display command. The Display command accepts size and
position parameters, which override the Display Settings options. For
more information about the Display command, see Appendix A,
RSView commands, or see Help.
If you use the Always Updating option with the Cache After Displaying
option, the startup command is executed when the display is loaded
into the cache. The shutdown command is executed only when the
cache is flushed. The cache is flushed when:
If you do not use the Always Updating option, the startup and
shutdown commands work normally, as described above.
Input fields are created with the Numeric Input, String Input, and
Recipe drawing tools. At run time, operators can use these fields to read
values from or write values to the programmable controller.
Text color is the color of the text in the input field. Fill color is the
background color of the input field. To open the color palette click a
colored box, and then click a color.
When choosing colors for the input fields, be sure to choose colors that
will stand out from the background color of the display. Choose
different colors for when the field is selected, so the operator can tell
that the field is highlighted.
You can create a tab sequence for interactive objects that use index
numbers. For details, see “Creating a tab sequence” on page 18-52.
When an object has input focus - that is, the object is ready to accept
keyboard or mouse input - the object will have a highlight box. You can
enable or disable this highlight box, and select the color of the box.
When the operator clicks or touches the selected field, or presses Enter
on a hardware keyboard, the on-screen keyboard appears.
The keypad for numeric input fields allows numeric entry only.
To cache displays:
use the [cache] parameter with the Display command. The [cache]
parameter loads a graphic display into the cache without displaying
it. The [cache] parameter has two options: /Z and /ZA. For
example, the command Display Bakery /Z loads the graphic display
called Bakery into the cache but does not display it. When the
graphic is called up, it is displayed quickly. The command Display
Bakery /ZA loads the display into the cache and continually
updates the values in the display. For details about the Display
command, see Appendix A, RSView commands, or see Help.
If a display uses the Always Updating option with the Cache After
Displaying option, the display’s shutdown command is executed when
you issue a FlushCache command, or when you close the application.
For details about the FlushCache command, see Appendix A, RSView
commands, or see Help.
When you use the PrintDisplay command RSView prints the entire
display, even if parts are covered by other displays. You can also use the
ScreenPrint command to print an image of whatever shows on the
monitor. For more information about these commands see
Appendix A, RSView commands, or see Help.
For details about the basic techniques for using the Graphic Displays
editor, and for details about setting up graphic displays, see Chapter 16,
Creating graphic displays.
Push buttons Objects that are typically used to start or stop processes
or actions.
Gauge and graph Objects that show the range of values, and
relationships between variables.
Key Objects that represent keys on a keyboard, and are for use with
touch screens.
Once you have selected a drawing tool, there are two ways to draw
objects: dragging, or clicking end points. Some objects, such as
rectangles, ellipses, and arcs, can be drawn only by dragging. Others,
such as polylines and polygons, can be drawn only by clicking end
points.
Creating text
Choosing a font
You can choose a font before or after you create text. You can change
the font of any object, including display and input objects.
When choosing a font, style, size, and color for text on the screen, keep
the following design principles in mind:
You can select any font you have installed, but TrueType™ and
OpenType® fonts are recommended. These fonts can be resized
easily, without losing text quality.
Choose only one or two fonts, and use them for all the graphic
displays in your application.
Choose a font size that most operators can read easily. Test the font
size, and adapt it to the screen resolution you expect operators to
be viewing at run time.
If you are short of screen space, rather than reducing the font size,
keep the size the same, but use a condensed font that fits more
characters per line, for example, Arial Narrow.
Some people are color blind to red and green so don’t rely on color
alone to establish meaning.
Ensure that the fonts you choose for your graphic displays are
installed on all the computers on which you intend to run the
graphic displays. If a font is not installed, Windows substitutes one
that is installed, possibly with unsatisfactory results.
When you release the left mouse button, the Text Properties dialog
box opens.
After you’ve set up one text object to look the way you want, copy
and paste it to create additional text objects with the same
formatting. Then edit the text of the new objects.
Font, size, and style Click a font for the text in the Font list. Type or
click a size for the font in the Size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
Or, click the Browse button to open the Font dialog box and set up
font attributes.
Browse button
Back color Click the color box, and then click a color for the text’s
background.
Fore color Click the color box, and then click a color for the text.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the text object. Clear this check box to
wrap on characters instead.
Alignment Click a position in the grid, relative to the text box. In the
default alignment position, the text is centered vertically and
horizontally within the text box.
Back style Click Solid to cover the display behind the text object with
a solid rectangle in the shape of the text’s box. Click Transparent to
allow the display’s background to show through between the letters.
2. In the Text box, click where you want to make the change. To
delete characters, use the Backspace and Delete keys.
RSView can read .bmp and JPEG (.jpg, .jpeg, .jpe, .jif, .jfif) files in their
native format, without requiring their conversion. For information
about importing graphic files in formats other than .bmp or JPEG, see
“Importing graphic files from third-party applications” on page 16-46.
There are three ways to add an image to a graphic display. You can:
You can paste an image you copy only for as long as the image remains
on the Windows clipboard—that is, until you next cut or copy
something.
2. Click the graphic display into which you want to paste the image.
5. Click OK.
If the image is monochrome (1 bit per pixel, 2 colors), you can change
its color, background color, transparency, and you can make it blink at
run time.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
When you release the mouse button, the image browser appears.
3. Click an image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image color Click the colored square to open the color palette,
and then click a color for a monochrome image. You cannot change
the color of grayscale or color images.
Image back color Click the colored square to open the color
palette, and then click a color for the background of a monochrome
image. You cannot change the background color of grayscale or
color images.
When you add an image using the Image Browser, the image also
appears in the Application Explorer automatically, and vice versa.
2. In the Open dialog box, select the folder in which the image you
want is located.
2. In the Open dialog box, select the folder in which the image you
want is located.
You can set up panel objects to blink at run time. The panel object does
not support animation, so you cannot make it blink or move in
response to a tag’s change in value.
To create a panel
To draw a square panel, press Ctrl while you drag the mouse.
Border uses back color Select the check box if you want the
panel’s border to have the same color as the panel’s background.
Clear the check box if you want the panel’s border to have a
different color than the background, and then choose a Border
color. For details, see page 17-14.
Back color Click the color box to open the palette, and then click
a color for the panel’s background.
Border color Click the color box to open the palette, and then
click a color for the panel’s border.
You can only change the border color if you clear the Border uses
back color check box.
Blink Select the check box to make the panel blink at run time.
Clear the check box to prevent the panel from blinking at run time.
2. Drag the drawing tool diagonally until the object is the size you
want.
2. To draw an ellipse, drag the drawing tool diagonally until the object
is the size you want.
You can also use the Snap to Grid option to draw straight lines.
You can change the style and width of lines using the object’s
Properties dialog box. For details, see “Changing the properties of
drawing objects” on page 17-20.
Polygon tool
2. Drag the drawing tool to create the first segment of the object.
Release the mouse button.
Wedge tool
Arc Hollow wedge Filled wedge
When you release the mouse button, a set of handles appears so you
can reshape the circle.
3. Click a handle, and drag the mouse to `cut out’ part of the circle.
You can also use the Arc and Wedge tools to reshape any arc, ellipse,
or wedge.
1. Place the pointer on the object you want to reshape, right-click the
object, and then click Edit.
1. Place the pointer on the object you want to reshape, and then do
one of the following:
in the object’s Properties dialog box. For details, see the topics in
this section.
in the Property Panel. For details about using the Property Panel,
see page 16-34.
1. Select the object. For details about the ways you can select objects,
see page 16-10.
Dash
Dot
Dash-Dot
Dash-Dot-Dot
Fore color Click the color box to open the palette, and then click
a color for the object’s foreground.
Line width Type a number between 1 and 32767 to change the
thickness of the line. Line width is measured in pixels.
Back color Click the color box to open the palette, and then click
a color for the object’s background.
Pattern color Click the color box to open the palette, and then
click a color for the pattern.
Every graphic object has a Common tab in its Properties dialog box.
Use the Common tab to set up these properties for the object:
name
tooltip
visibility
For ActiveX and trend objects, you can also set up these properties:
focus highlight
pointer highlight
key navigation
tab index
1. Select the object. For details about the ways you can select objects,
see page 16-10.
Height Type the number of pixels for the height of the object. The
height includes the object’s borders.
Width Type the number of pixels for the width of the object. The
width includes the object’s borders.
Top Type the number of pixels from the top of the display to
position the object. You can type a positive or negative number. If
you use a negative number, part or all of the object is off the display.
Name Type a name for the object. The name must start with a
letter, and cannot contain spaces. You can use numbers and the
underscore character ( _ ) in the name.
If you don’t specify a name for the object, the default name is used
in the status bar, activity bar, Property Panel, and Object Explorer
in RSView Studio, and in activity log messages at run time.
Tooltip text Type a tooltip for the object. Tooltips are descriptive
text that appear at run time when you bring the cursor to rest over
an object for a few seconds, if the object is not disabled. An object
that has been disabled cannot be selected.
Visible Click this box to make the object visible. Clear the check
box if you don’t want the object to appear at run time.
Clear the check box if you don’t want the object to display a
highlight box at run time.
For more information about focus highlight, see “What input focus
looks like” on page 17-27.
Clear the check box if you don’t want the object to display a
highlight box at run time.
Clear the check box if you don’t want the operator to navigate to the
object using the keyboard.
Tab index Either leave the default as it is, or type a number. Index
numbers determine the Tab sequence for interactive objects such as
input objects and buttons, and are also used in recipe files. For
details, see “Using index numbers” on page 18-49.
2. For some objects you will need to double-click the object to set it
up. For other objects, a properties dialog box appears
automatically.
At run time, interactive objects obtain data from tags. When creating
interactive objects, you must specify the name of the tag that supplies
the object with data.
Browse button Type a tag name in a Tag Name box or in an Expression box.
Click the Browse button and then click a tag name in the list.
trends
For ActiveX and trend objects, you can specify whether or not to
display a highlight box in the object’s Properties dialog box, on the
Common tab. For details, see “Setting up properties common to all
graphic objects” on page 17-22.
If the Disable Highlight When Object has Focus box is selected in the
Display Settings dialog box, that setting overrides the setting you
specify in the ActiveX object’s Properties dialog box.
When an object’s key navigation is disabled, the operator can still select
the object using a mouse or touch screen, if available.
In the Property Panel, click the Properties tab, and then set the
KeyNavigation property to False.
For display list selectors, open the object’s Properties dialog box,
click the General tab, and then clear the Key navigation check box.
For ActiveX and trend objects, open the object’s Properties dialog
box, click the Common tab, and then clear the Key navigation check
box.
Buttons can run RSView commands, or they can work like momentary
push buttons.
Momentary push buttons change a tag to one value when the button
is pressed, and another value when the button is released. Momentary
Interlocked push buttons work in groups, and share the same tag. The
buttons work together like the preset station selector buttons on a car
radio: pressing one button cancels another. Although interlocked push
buttons work as a group, you add them to the display one at a time.
In the Properties dialog box, the various features of push buttons are
organized in tabs. Most push buttons have at least four tabs: a General
tab, a States tab, a Common tab, and a Connections tab.
The States tab contains settings for what the button does, and how its
appearance changes, for example when the button is pressed or
released.
The Common tab is common to all graphic objects. Use the Common
tab to change the object’s spatial properties, its name, tooltip, and
visibility. For details, see “Setting up properties common to all graphic
objects” on page 17-22.
The button object has no Connections tab; instead it has an Action tab.
Set up the tags to which the button is connected on the Action tab.
Button push buttons have no states. They have Press and Release
actions, an Up Appearance and a Down Appearance. For details
about setting up a Button push button, see “Creating buttons” on
page 17-37.
Ramp push buttons have no states; they can only ramp a value up
or down.
Multistate push buttons have two states by default, but you can add
more states, to add up to 255 functions to the button.
Most push buttons have two ways of sending and receiving data:
The Value tag triggers the button’s action, for example starts a
machine or process. The Value tag is similar to the contact on a
hard-wired push button.
Exceptions
For most push buttons, the Value tag is a read-write tag. There are two
exceptions:
If you assign the same tag name to the Value tag and to the Indicator
tag, the button’s appearance will change when the operator presses the
button. If you assign different tag names to the Value and Indicator
tags, the button’s appearance will change only when the value of the
Indicator tag changes.
For those buttons that have an Indicator tag, the tag is always a read tag.
Creating buttons
Use the Button tool to create push buttons that work like standard
Windows buttons. You can attach RSView commands to the buttons
Button tool
so they trigger actions when pressed and released.
You can apply visibility, color, horizontal and vertical slider, horizontal
and vertical position, width, and height animation to the button.
2. Drag the mouse to draw a button the size you want, and then
release the mouse button.
3. Fill in the fields in each tab to set up the button’s appearance and
what it does, as described in the sections that follow.
3D, Recessed, and Raised styles can be used only for rectangular-
shaped buttons. The Beveled style supports rectangular and
polygonal shapes. If you change a 3D, recessed, or raised button to
another shape, or if you rotate it, the button automatically changes
to beveled.
The highlight and shadow colors on the beveled button use the
current system settings.
2. To prevent the cursor from moving off the button until the
button’s release action is carried out, select the Capture cursor
check box. Use this feature when you need to ensure that a
button’s release action is carried out.
If the Capture cursor check box is not selected, the button will
behave like a standard Windows button, allowing the user to
`cancel’ the button’s release action by holding the mouse button
down while moving the cursor off the button.
4. In the Tab index box, either leave the default value or type a new
value. Index numbers determine the tab sequence for interactive
objects such as buttons and input fields and are also used in recipe
components. For details, see “Using index numbers” on
page 18-49.
In the action tab, click an action in the list, and then specify what
happens when the action occurs.:
Set tag to 1Sets the specified tag to 1 when the button is released
(mouse down = no action, mouse up = Set <tag name> 1).
Set tag to 0 Sets the specified tag to 0 when the button is released
(mouse down = no action, mouse up = Set <tag name> 0).
You must specify either a press or release action; both are not required.
If you specify a repeat action, the action is repeated at the rate specified
in the Repeat rate box, for as long as the mouse button is held down.
Pressing the Enter key does not cause a repeat action to be executed
because Windows interprets this as a series of press actions, so the
repeat action is not carried out. The Enter key works for the press and
release actions only.
In the Up Appearance tab, specify what the button looks like when it
is not pressed.
Pattern style Click a pattern style for the button. If the Back style is
Transparent, the pattern is not visible.
Fore, Back, and Pattern color Click the corresponding color box to
open the palette, and then click a color in the palette.
Caption Type a caption for the button. To change the caption’s font
or size, click a font or size in the corresponding list.
An image you reference is not saved with the graphic display. You should
reference images that are large in size, but stored on the same computer
as the graphic display.
An image you import is saved with the graphic display. You should
import small images, or images on other computers on the network. If
you import images that reside on other computers on the network, they
don’t have to be sent across the network every time the graphic display
is opened. This helps reduce network traffic.
To scale the image to fit the surface of the button, select the Scale image
check box. To keep the image at its original size, leave the Scale image
check box cleared.
If the button is a polygon, the caption and imported bitmap image are
clipped at the rectangular extents of the button.
If you want the button to appear the same when it is pressed as when
it is not pressed, click Same as Up Appearance. If you want a different
appearance for the button, clear the check box, and then choose
different options. For details about the options, see “Setting up what
the button looks like when it is not pressed” on page 17-42.
For details about the button’s properties, see the topics starting on
page 17-39.
Reshaping a button
If you reshape or rotate a button, the button type always changes to
beveled. Only beveled buttons can be a polygon (or non-rectangular)
shape.
To reshape a button, click the button to select it, and then click the
Polygon tool. Move or add vertices as you would with any polygon. For
details about reshaping polygons, see “Reshaping drawing objects” on
page 17-18.
Use the Momentary Push Button tool to create a button that starts a
process or action. When pressed, momentary push buttons change a
Momentary Push Button
tag to one value, and when released, they change a tag to another value.
tool
The momentary push button’s states can perform one of three kinds of
actions:
change the Value tag to 1 when the button is pressed, and to zero
when the button is released. This kind of button is called normally
open, because its released state is off. Pressing the button completes
the circuit.
change the Value tag to zero when the button is pressed, and to 1
when the button is released. This kind of button is called normally
change the Value tag to a value you specify. You assign these values
to the button’s press and release actions. For example, 50 when
released, and 100 when pressed.
Momentary Push Button 2. Drag the mouse to draw a button the size you want.
tool
3. Double-click the button to set it up.
In the General tab, specify what the momentary push button looks like
at run time, and what type of action the button performs.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the button’s
border to have the same color as the button’s background.
Clear the check box if you want the button’s border to have a different
color than the button’s background, and then choose a Border color in
the States tab. For details, see “Border color” on page 17-51.
Highlight color Click the color box to open the palette, and then click
a color for the border that appears around the button when it is
selected. If the button does not have a border, the highlight color is not
visible when the button is pressed.
Click Normally closed to change the button’s tag to zero when the
button is pressed, and 1 when the button is released.
Click Value to specify values for each of the button’s states. Type values
in the States tab, described on page 17-51.
Hold time The amount of time the button remains pressed before the
Release action takes effect, even if the operator releases the button
sooner.
The hold time should reflect network traffic. Increasing the hold time
prevents a very quick object press from being missed by the
programmable controller. If you are using a memory HMI tag, click the
shortest hold time.
The operator cannot press the button again until the hold time has
expired. If a display change occurs before the hold time has expired, the
value for the released state is sent immediately to the tag.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Vertical margin The number of pixels for the vertical touch margin.
The vertical margin is a touch-insensitive margin inside the object’s top
and bottom edges. If the operator presses the touch-insensitive margin,
the button press is not registered.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Audio Select this check box to beep the computer’s internal speaker
when the operator presses the button.
If the computer running the display does not have an internal speaker,
pressing the button does not trigger a beep.
the Value tag does not match one of the state values you set up.
the Indicator tag does not match one of the state values you set up.
Select state Click a state, and then set up the state on the right-hand
side.
Value The value to which the button changes the Value tag when the
selected state is in effect. When the Indicator tag changes to this value,
the button’s appearance changes to the settings you specify for the
state.
If you clicked Value for the button action in the General tab, you can
type a value for the state in this box. You cannot type a value for the
button’s error state.
If you clicked Normally open for the button action in the General tab,
state 0 has a value of 0, and state 1 has a value of 1. You cannot change
these values.
If you clicked Normally closed for the button action in the General tab,
state 0 has a value of 1, and state 1 has a value of 0. You cannot change
these values.
Back color Click the color box to open the palette, and then click a
color for the button’s background.
Border color Click the color box to open the palette, and then click a
color for the button’s border.
Blink Select the check box to make the button blink at run time. Clear
the check box to prevent the button from blinking at run time.
Caption Type the text you want to appear on the button. If you don’t
want any text on the button, leave the Caption box blank.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the caption. Clear this check box to
truncate words that are too long for the width of the caption.
Image Type the name of the image file you want to display on the
button, or click the Browse button to browse for the image.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image back color Click the colored square to open the color palette,
and then click a color for the background of a monochrome image. You
cannot change the background color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the button. Clear this check box to crop the image to the area of the
button.
If you assign this tag, the button does not display the pressed state until
it receives a response from the Indicator tag. Set up the controller to
change the Indicator tag’s value when it has read the Value tag’s value.
When pressed and released the first time, the maintained push button
changes a tag to one value. When pressed and released a second time,
the button changes the tag to another value.
In the General tab, specify what the button looks like at run time, and
how the button changes state.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the button’s
border to have the same color as the button’s background.
Clear the check box if you want the button’s border to have a different
color than the button’s background, and then choose a Border color in
the States tab. For details, see “Border color” on page 17-61.
Highlight color Click the color box to open the palette, and then click
a color for the border that appears around the button when it is
selected. If the button does not have a border, the highlight color is not
visible when the button is pressed.
Click Value control to toggle the button’s state relative to the Value tag.
If the operator presses the button, changing its state to 1, and then the
Value tag changes the button’s state to zero, the next time the operator
presses the button, the button’s state will be 1.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Audio Select this check box to beep the computer’s internal speaker
when the operator presses the button. If the computer running the
display does not have an internal speaker, pressing the button does not
trigger a beep.
In the States tab, specify what the button does when it is pressed and
released.
the Value tag does not match one of the state values you set up
when the display that contains the maintained push button opens.
the Indicator tag does not match one of the state values you set up.
Select state Click a state, and then set up the state on the right-hand
side.
Value The value to which the button changes the Value tag when the
selected state is in effect. When the Indicator tag changes to this value,
the button’s appearance changes to the settings you specify for the
state.
Back color Click the color box to open the palette, and then click a
color for the button’s background.
Border color Click the color box to open the palette, and then click a
color for the button’s border.
Blink Select the check box to make the button blink at run time. Clear
the check box to prevent the button from blinking at run time.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Caption blink Select the check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
Image Type the name of the image file you want to display on the
button, or click the Browse button to browse for the image.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image color Click the colored square to open the color palette, and
then click a color for a monochrome image. You cannot change the
color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the button. Clear this check box to crop the image to the area of the
button.
Value Type a tag name, or click the Browse button to browse for a tag.
The Value tag triggers the button’s action. For example, the tag that,
when set to 1, changes to Auto mode.
If you assign this tag, the button does not display the pressed state until
it receives a response from the Indicator tag. Set up the controller to
change the Indicator tag’s value when it has read the Value tag’s value.
Use the Latched Push Button tool to create a button that latches in the
on position, and must be unlatched by another button or process to
Latched Push Button tool
return to the off position.
Latched push buttons work like momentary buttons, except that the tag
doesn’t change to the button’s release value until the button is
unlatched by another button or process. This type of button is useful
for starting a machine or process.
In the General tab, specify what the button looks like at run time, and
how to unlatch it.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the button’s
border to have the same color as the button’s background.
Clear the check box if you want the button’s border to have a different
color than the button’s background, and then choose a Border color in
the States tab. For details, see “Border color” on page 17-70.
Highlight color Click the color box to open the palette, and then click
a color for the border that appears around the button when it is
selected. If the button does not have a border, the highlight color is not
visible when the button is pressed.
To unlatch the push button when the Handshake tag changes from a
zero to a non-zero value, click Zero to non-zero transition.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Vertical margin The number of pixels for the vertical touch margin.
The vertical margin is a touch-insensitive margin inside the object’s top
and bottom edges. If the operator presses the touch-insensitive margin,
the button press is not registered.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Audio Select this check box to beep the computer’s internal speaker
when the operator presses the button.
If the computer running the display does not have an internal speaker,
pressing the button does not trigger a beep.
the Value tag does not match one of the state values you set up
when the display containing the latched push button first opens.
the Indicator tag does not match one of the state values you set up.
Select state Click a state, and then set up the state on the right-hand
side.
Value The value to which the button changes the Value tag when the
selected state is in effect. When the Indicator tag changes to this value,
the button’s appearance changes to the settings you specify for the
state.
Back color Click the color box to open the palette, and then click a
color for the button’s background.
Border color Click the color box to open the palette, and then click a
color for the button’s border.
Blink Select the check box to make the button blink at run time. Clear
the check box to prevent the button from blinking at run time.
Caption Type the text you want to appear on the button. If you don’t
want any text on the button, leave the Caption box blank.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the caption. Clear this check box to
truncate words that are too long for the width of the caption.
Image Type the name of the image file you want to display on the
button, or click the Browse button to browse for the image.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image back color Click the colored square to open the color palette,
and then click a color for the background of a monochrome image. You
cannot change the background color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the button. Clear this check box to crop the image to the area of the
button.
If you assign this tag, the button does not display the pressed state until
it receives a response from the Indicator tag. Set up the controller to
change the Indicator tag’s value when it has read the Value tag’s value.
To unlatch the button, the Handshake tag works with the Latched
Reset Type setting (in the General tab, see page 17-68).
Depending on which item you clicked in the Latched Reset Type list,
the Handshake tag unlatches the button either when the Handshake tag
has a non-zero value, or when the Handshake tag changes from a zero
to a non-zero value.
Use the Multistate Push Button tool to create a button that displays and
allows an operator to cycle through multiple options consecutively. The
Multistate Push Button tool
multistate push button displays the current state of a process or
operation by showing a different color, caption, or image to reflect
different states.
Each time the operator presses the button, the tag changes to the value
for the next state. When the button is in its last state and the operator
presses the button, the button returns to its first state.
Multistate Push Button tool 2. Drag the mouse to draw a button the size you want.
In the General tab, specify what the button looks like, and how the
button changes state.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the button’s
border to have the same color as the button’s background.
Clear the check box if you want the button’s border to have a different
color than the button’s background, and then choose a Border color in
the States tab. For details, see “Border color” on page 17-80.
Highlight color Click the color box to open the palette, and then click
a color for the border that appears around the button when it is
selected. If the button does not have a border, the highlight color is not
visible when the button is pressed.
Assign only as many states as you want to set up. If you don’t assign
values to all the states the button has, the operator must press the
button repeatedly through all the empty states before the first state
becomes available again.
Next state based on When the operator presses the button, the next
state that is displayed can be based on the current state, or on the value
of the Value tag.
Click Current state to use the current state as the basis for deciding
what the next state will be. Click Current state if you want the button
itself to determine what its next state will be.
Click Value control to use the Value tag as the basis for deciding what
the next state will be. Click Value control if you want other devices to
change the Value tag, and determine what the button’s next state will
be.
If the Value tag does not match one of the button’s state values, the
button changes to State 0, and changes the Value tag to the value of
State 0.
Vertical margin The number of pixels for the vertical touch margin.
The vertical margin is a touch-insensitive margin inside the object’s top
and bottom edges. If the operator presses the touch-insensitive margin,
the button press is not registered.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Audio Select this check box to beep the computer’s internal speaker
when the operator presses the button.
If the computer running the display does not have an internal speaker,
pressing the button does not trigger a beep.
In the States tab, specify what the button does when it is pressed and
released.
the Indicator tag does not match one of the state values you set up.
Select state Click a state, and then set up the state on the right-hand
side.
Insert state Click a state, and then click Insert state. The new state
always appears above the selected state.
Value The value to which the button changes the Value tag when the
selected state is in effect. When the Indicator tag changes to this value,
the button’s appearance changes to the settings you specify for the
state.
Back color Click the color box to open the palette, and then click a
color for the button’s background.
Border color Click the color box to open the palette, and then click a
color for the button’s border.
Blink Select the check box to make the button blink at run time. Clear
the check box to prevent the button from blinking at run time.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Caption blink Select the check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
Image Type the name of the image file you want to display on the
button, or click the Browse button to browse for the image.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image color Click the colored square to open the color palette, and
then click a color for a monochrome image. You cannot change the
color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the button. Clear this check box to crop the image to the area of the
button.
Auto repeat rate Select the number of times per second a button
press is registered when the button goes into auto repeat mode. If you
don’t want the button to repeat automatically, click 0.
Value Type a tag name, or click the Browse button to browse for a tag.
The Value tag triggers the button’s action. For example, the tag that
switches among recipes.
If you assign this tag, the button does not display the pressed state until
it receives a response from the Indicator tag. Set up the controller to
change the Indicator tag’s value when it has read the Value tag’s value.
Use the Interlocked Push Button tool to create multiple buttons that
work together in groups, and share the same tag.
Interlocked Push Button
tool The buttons work together like the preset station selector buttons on a
car radio: pressing one button cancels another. Although interlocked
push buttons work as a group, you add them to the display one at a
time.
When the operator presses one of the interlocked push buttons, the
buttons’ Value tag changes to one value. When the operator presses a
different interlocked button, the buttons’ Value tag changes to another
value. All the buttons share the same Value tag.
In the General tab, specify the button’s appearance, and the value to
which it changes the tag it is connected to.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the button’s
border to have the same color as the button’s background.
Clear the check box if you want the button’s border to have a different
color than the button’s background, and then choose a Border color in
the States tab. For details, see “Border color” on page 17-90.
Highlight color Click the color box to open the palette, and then click
a color for the border that appears around the button when it is
selected. If the button does not have a border, the highlight color is not
visible when the button is pressed.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Vertical margin The number of pixels for the vertical touch margin.
The vertical margin is a touch-insensitive margin inside the object’s top
and bottom edges. If the operator presses the touch-insensitive margin,
the button press is not registered.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
If the computer running the display does not have an internal speaker,
pressing the button does not trigger a beep.
Back color Click the color box to open the palette, and then click a
color for the button’s background.
Border color Click the color box to open the palette, and then click a
color for the button’s border.
Blink Select the check box to make the button blink at run time. Clear
the check box to prevent the button from blinking at run time.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see “Choosing a
font” on page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the caption. Clear this check box to
truncate words that are too long for the width of the caption.
Image Type the name of the image file you want to display on the
button, or click the Browse button to browse for the image.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image back color Click the colored square to open the color palette,
and then click a color for the background of a monochrome image. You
cannot change the background color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the button. Clear this check box to crop the image to the area of the
button.
Value Type a tag name, or click the Browse button to browse for a tag.
The Value tag triggers the button’s action. For example, the tag that,
when set to 1, changes to Auto mode.
Use the Ramp Push Button tool to create a button that the operator can
use to increase or decrease the value of a tag.
Ramp Push Button tool
Ramp push buttons can change a tag by either an integer or floating
point value. You can use two ramp buttons together to create an
increase/decrease control.
Each time the operator presses the button, the tag changes to the next
highest or next lowest value, depending on how you set up the button.
In the General tab, specify what the button looks like, and whether the
button ramps a value up or down.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the button’s
border to have the same color as the button’s background.
Clear the check box if you want the button’s border to have a different
color than the button’s background, and then choose a Border color.
For details, see “Border color” on page 17-96.
Back color Click the color box to open the palette, and then click a
color for the button’s background.
Border color Click the color box to open the palette, and then click a
color for the button’s border.
Highlight color Click the color box to open the palette, and then click
a color for the border that appears around the button when it is
selected. If the button does not have a border, the highlight color is not
visible when the button is pressed.
Blink Select the check box to make the button blink at run time. Clear
the check box to prevent the button from blinking at run time.
Upper limit This box appears only if you click Ramp up. Type the
upper limit for the tag’s value.
Ramp down Click Ramp down to decrease the value of the tag.
Lower limit This box appears only if you click Ramp down. Type the
lower limit for the tag’s value.
Ramp value Type the positive value by which the button increases or
decreases the tag’s value.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Vertical margin The number of pixels for the vertical touch margin.
The vertical margin is a touch-insensitive margin inside the object’s top
and bottom edges. If the operator presses the touch-insensitive margin,
the button press is not registered.
This is useful for buttons that are positioned close together. A touch-
insensitive border on each button helps ensure that an adjacent button
is not pressed by mistake.
Audio Select this check box to beep the computer’s internal speaker
when the operator presses the button.
If the computer running the display does not have an internal speaker,
pressing the button does not trigger a beep.
Caption Type the text you want to appear on the button. If you don’t
want any text on the button, leave the Caption box blank.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Caption blink Select the check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the caption. Clear this check box to
truncate words that are too long for the width of the caption.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image color Click the colored square to open the color palette, and
then click a color for a monochrome image. You cannot change the
color of grayscale or color images.
Image back color Click the colored square to open the color palette,
and then click a color for the background of a monochrome image. You
cannot change the background color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the button. Clear this check box to crop the image to the area of the
button.
Auto repeat rate Select the number of times per second a button
press is registered when the button goes into auto repeat mode. If you
don’t want the button to repeat automatically, click 0.
Auto repeat delay Click the number of milliseconds the button must
remain pressed before auto repeat starts.
In the Connections tab, specify the tag with which the button
exchanges data. Ramp push buttons have no Indicator tag.
Value Type a tag name, or click the Browse button to browse for a tag.
The Value tag triggers the button’s action. For example, the tag that
changes a motor’s speed.
You can create different kinds of numeric and string fields, depending
on your needs:
Display fields show values in a graphic display. Use them when you
need to show a value that an operator does not need to modify.
Decimal places Type the number of places you want after the
decimal point. This number must be at least one less than the field
width.
6. Click OK.
For example, assume you have a string 12 characters long. The first
eight characters contain the tag address. The last four characters
contain the tag status. To display only the status, specify a character
6. Click OK.
12345
12345
To upload data and display it in the input field, the Programmable controller
operator presses PgUp.
Operators can select any one of the input fields in the display and read
or write the values associated with that field, or they can read or write
all the values at once. You also have the option of setting input fields
so that tag values update continuously when the operator is not using
the field to input data.
Colors for input fields are set in the Display Settings dialog box. For
details, see “Specifying colors for input fields” on page 16-70.
Tab index Either leave the default as it is, or type a number. Index
numbers determine the Tab sequence for interactive objects such as
input objects and buttons, and are also used in recipe files. For
details, see “Using index numbers” on page 18-49.
Default data Type a value that will appear in the numeric input
field when the graphic is initially displayed.
Decimal places Type the number of places you want after the
decimal point. This number must be at least one less than the field
width.
Overflow You can make selections from this list only if you clicked
Floating Point in the Format list. Specify how you want the floating
point value displayed if it is too long for the field. The value can be
shown as an exponent, rounded up to fit in the field, or replaced
completely by asterisks.
Select this check box to discard whatever the operator types in the
field, if the operator selects another object before pressing PgDn,
Ctrl-PgDn, or Enter to download the value to the programmable
controller. The numeric input field then resumes updating itself
with values from the programmable controller.
Clear this check box if you want to force the operator to complete
his or her entry in this field before selecting or using another object
in the graphic display.
6. Click OK.
Tag Type a tag name, or a placeholder for a string tag. For details
about placeholders, see “Using tag placeholders” on page 16-51.
Tab index Either leave the default as it is, or type a number. Index
numbers determine the Tab sequence for interactive objects such as
input objects and buttons, and are also used in recipe files. For
details, see “Using index numbers” on page 18-49.
Select this check box to discard whatever the operator types in the
field, if the operator selects another object before pressing PgDn to
download the value to the programmable controller. The string
input field then resumes updating itself with values from the
programmable controller.
Clear this check box if you want to force the operator to complete
his or her entry in this field before selecting or using another object
in the graphic display.
6. Click OK.
At run time, operators can use input fields to retrieve data from and
send data to the value table so it can be accessed by the programmable
controller, external OPC server or DDE device, or by RSView
memory.
When a value has been entered in the field but not downloaded yet
(pending write mode), the border around the field is solid.
This field is in
display mode
This field is in
pending write
mode
This field is in
input mode
The operator can put the field into input mode by selecting the field,
uploading to the field, or restoring a recipe to the field. The operator
can set the field back to display mode by pressing the Escape key.
Keys
Operators can use the following keys to retrieve data from and send
data to the value table. You can re-assign these actions to other keys or
assign them to button objects.
PgDn downloads the contents of all input fields that are in pending
write mode in the active graphic display to the value table.
If the display has been set up to use the on-screen keyboard, pressing
Enter brings up the on-screen keyboard.
PgUp uploads all values from the value table and then displays them in
the input fields.
Ctrl-PgUp uploads a value from the value table for the selected input
field.
Upload uploads a value from the value table and displays it in the
selected input field.
UploadAll uploads all the values from the value table and displays them
in the input fields.
Update Field Closes the on-screen keyboard, and stores the new value
on screen for later download.
Download For numeric and string input fields, closes the on-screen
keyboard, and downloads the value or text the operator
typed.
Most indicators have several states, and an error state. The error state
occurs when the indicator is receiving invalid data.
The List indicator has no error state. If the value of the Indicator tag
does not match any of the available states, none of the states is
highlighted.
Each bit position in the tag’s value corresponds to one of the indicator’s
states: for example, position 1 triggers state 1.
The number of states a tag’s value can trigger depends on the tag’s data
type. For example, a tag of type long integer can be used to change up
to 33 of an indicator’s states (32 bit positions plus zero).
Use the Multistate Indicator tool to create an indicator that displays the
current state of a process or operation by showing a different color,
Multistate Indicator tool
caption, or image for each state.
You specify the state values of the multistate indicator. At run time, the
indicator displays the state whose value matches the Indicator tag’s
value.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the
indicator’s border to have the same color as the indicator’s background.
Clear the check box if you want the indicator’s border to have a
different color than the indicator’s background, and then choose a
Border color in the States tab. For details, see “Border color” on
page 17-124.
Click LSB to trigger a state based on the least significant bit’s position
of the Value tag.
the value of the Indicator tag does not match one of the state values
you set up.
Select state Click a state, and then set up the state on the right-hand
side.
Insert state Click a state, and then click Insert state. The new state
always appears above the selected state.
Delete state Click the state you want to delete, and then click Delete
state.
Value Type the integer value for each state. When the Indicator tag
changes to this value, the indicator’s appearance changes to the settings
you specify for the state.
Back color Click the color box to open the palette, and then click a
color for the indicator’s background.
Border color Click the color box to open the palette, and then click a
color for the indicator’s border.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Caption Type the text you want to appear on the indicator. If you
don’t want any text on the indicator, leave the Caption box blank.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
Caption blink Select the check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the caption. Clear this check box to
truncate words that are too long for the width of the caption.
Alignment Click a position in the grid for the text, relative to the
indicator. In the default alignment position, the text is centered
vertically and horizontally on the indicator.
Image Type the name of the image file you want to display on the
indicator, or click the Browse button to browse for the image.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
Image color Click the colored square to open the color palette, and
then click a color for a monochrome image. You cannot change the
color of grayscale or color images.
Image back color Click the colored square to open the color palette,
and then click a color for the background of a monochrome image. You
cannot change the background color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the button. Clear the check box to crop the image to the area of the
button.
Alignment Click a position in the grid for the image, relative to the
indicator. In the default alignment position, the image is centered
vertically and horizontally on the indicator.
You specify the state values, and the image you want displayed for each
state. At run time, the indicator displays the state that matches the
Indicator tag or expression’s value.
2. Drag the mouse to draw an indicator the size you want. When you
release the left mouse button, the Image Browser appears
automatically.
For details about adding images to graphic displays, see page 17-6.
Border style Click a border style in the list, or click None to remove
the border.
Number of states Click the number of states you want the indicator
to have.
Trigger type Click Value to trigger a state based on the value of the
Value tag.
Click LSB to trigger a state based on the least significant bit’s position
of the Value tag.
Image Type the name of the monochrome image file you want to
display on the indicator, or click the Browse button to browse for the
image.
the value of the Indicator tag does not match one of the state values
you set up.
Select state Click a state, and then set up the state on the right-hand
side.
Insert state Click a state, and then click Insert state. The new state
always appears above the selected state.
Value Type the integer value for each state. When the Indicator tag
changes to this value, the indicator’s appearance changes to the settings
you specify for the state.
Border color Click the color box to open the palette, and then click a
color for the indicator’s border.
Image color Click the colored square to open the color palette, and
then click a color for a monochrome image. You cannot change the
color of grayscale or color images.
Image back color Click the colored square to open the color palette,
and then click a color for the background of a monochrome image. You
cannot change the background color of grayscale or color images.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Use the List Indicator tool to create an indicator that displays a list of
states for a process or operation, and highlights the current state.
List Indicator tool
Each state is represented by a caption in the list. This type of indicator
is useful if you want operators to view the current state, but also see the
other possible states.
For sequential processes, the list can inform the operator about what
happens next.
You specify the state values of the list indicator. At run time, the
indicator highlights the state whose value matches the Indicator tag’s
value.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the
indicator’s border to have the same color as the indicator’s background.
Clear the check box if you want the indicator’s border to have a
different color than the indicator’s background, and then choose a
Border color. For details, see “Border color” on page 17-136.
Back color Click the color box to open the palette, and then click a
color for the indicator’s background.
Border color Click the color box to open the palette, and then click a
color for the indicator’s border.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Selection fore color Click the color box to open the palette, and then
click a color for the foreground of a selected item in the list.
Blink Select the check box to make the indicator blink at run time.
Clear the check box to prevent the indicator from blinking at run time.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption truncate Click Word to cut off captions that exceed the
maximum length at the beginning of the word. Click Character to cut
off captions that exceed the maximum length, even in the middle of a
word.
Number of states Click the number of states you want the indicator
to have.
Trigger type Click Value to trigger a state based on the value of the
Value tag. Click LSB to trigger a state based on the least significant bit’s
position of the Value tag.
Select state Click a state, and then set up the state on the right-hand
side.
Insert state Click a state, and then click Insert state. The new state
always appears above the selected state.
Delete state Click the state you want to delete, and then click Delete
state.
Value Type the integer value for each state. When the Indicator tag
changes to this value, the indicator’s appearance changes to match the
settings you specify for the state.
Caption Type the text you want to appear on the indicator. If you
don’t want any text on the indicator, leave the Caption box blank.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Caption blink Select the check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
Alignment Click a position in the grid for the text, relative to the
indicator. In the default alignment position, the text is centered
horizontally on the indicator.
Gauges are used instead of numeric displays when it’s important for the
operator to recognize an abnormal condition instantly, either from far
away when the scale on the gauge isn’t visible, or before the operator
has had the opportunity to determine the exact reading on the gauge.
This characteristic of gauges is one of the reasons why they are used in
automobile instrumentation.
As the needle sweeps higher on a gauge, the gauge can fill the area
below it with a color. The gauge can change its fill color to help an
operator recognize abnormal conditions. The change in color happens
when the tag value crosses a threshold you set up for the gauge. For
example:
if the temperature is in the correct range for the recipe, the gauge
can show the temperature in green.
if the temperature is higher than the recipe will allow, the gauge can
show the temperature in red.
IMPORTANT Some people are color blind to red and green, so don’t
rely on color alone to establish meaning.
For example, one bar graph can show the required level of a tank of
ingredients for a recipe, and a second bar graph can show the actual
level of the tank. The first graph changes to represent the required level
for each recipe, and the second graph changes as the actual level in the
tank rises or drops.
Graphs are used instead of numeric displays when it’s important for the
operator to analyze the relationships between numeric values. It’s easier
for the operator to see that one graph is at a lower level than the other,
or that one’s fill is green and the other’s red, than it is to subtract one
numeric value from another.
As it fills, a graph can change its fill color to help an operator recognize
abnormal conditions. The change in color happens when the tag value
crosses a threshold you set up for the graph. For example
if the recipe will empty the tank, the graph can show the level in
yellow.
IMPORTANT Some people are color blind to red and green, so don’t
rely on color alone to establish meaning.
Unlike gauges, bar graphs do not have integrated scales. You can show
values on a bar graph using a scale and text.
Scales consist of major ticks, represented by long lines, and minor ticks,
represented by short lines. To indicate the values of major or minor
ticks, use text objects.
Creating gauges
For some important definitions, and to understand how gauges work,
see “How to use gauges and graphs” on page 17-141.
To create a gauge
Back color Click the color box to open the palette, and then click a
color for the gauge’s background.
Fill color Click the color box to open the palette, and then click a color
for the filled part of the gauge. The filled part represents a numeric
value, and is displayed against the gauge’s background. If you use
thresholds, this color is used until the graph’s value reaches the first
threshold.
Line style Click a line style for the gauge’s scale. If you want a line
style other than solid, the line width must be 1 pixel.
Line width Type a number between 1 and 32767 to change the line
thickness of the gauge’s scale. Line width is measured in pixels.
Needle color Click the color box to open the palette, and then click a
color for the gauge’s needle.
Sweep style Click Point to point the needle at the scale as the needle
sweeps over the gauge. Click Fill to fill the area below the needle with
color as the needle sweeps over the gauge.
Major ticks Click the number of major ticks you want on the gauge’s
scale.
Minor ticks Click the number of minor ticks you want on the gauge’s
scale. Minor ticks are spaced evenly between the major ticks.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Minimum value Type the minimum value you want displayed on the
gauge. If the Value tag is at or below this value, the needle is at the left
end of the dial.
Maximum value Type the maximum value you want displayed on the
gauge. If the Value tag is at or above this value, needle is at the right end
of the dial.
Digits after decimal Click the number of digits you want displayed
after the decimal point, in numeric labels on the gauge’s scale.
Legend color Click the color box to open the palette, and then click
a color for the numbers on the gauge’s scale.
Fill color Click the color box to open the palette, and then click a color
for the filled part of the gauge. The filled part represents a numeric
value, and is displayed against the gauge’s background.
Value Type a tag name, or click a Browse button to browse for a tag.
The Value tag changes the position of the needle on the gauge.
Use the Bar Graph tool to create a graph that represents a numeric
value by filling and emptying as the value rises and falls.
Bar Graph tool
You specify the maximum and minimum values of the bar graph, and
the tag to which the graph is connected. At run time, the graph shows
the value of the tag in relation to the graph’s minimum and maximum
values.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the bar
graph’s border to have the same color as the bar graph’s background.
Clear the check box if you want the bar graph’s border to have a
different color than the bar graph’s background, and then choose a
Border color in the States tab. For details, see “Border color” on
page 17-152.
Back color Click the color box to open the palette, and then click a
color for the bar graph’s background.
Border color Click the color box to open the palette, and then click a
color for the bar graph’s border.
Fill color Click the color box to open the palette, and then click a color
for the filled part of the graph. The filled part represents a numeric
value, and is displayed against the graph’s background. If you use
thresholds, this color is used until the graph’s value reaches the first
threshold.
Maximum value Type the maximum value you want displayed on the
graph. If the Value tag is at or above this value, the graph is filled.
Fill direction Click the direction in which you want the graph to fill.
Fill color Click the color box to open the palette, and then click a color
for the filled part of the graph. The filled part represents a numeric
value, and is displayed against the graph’s background.
In the Connections tab, specify the tag from which the bar graph
receives data.
Value Type a tag name, or click a Browse button to browse for a tag.
The Value tag changes the fill level on the bar graph. For example, the
Value tag can show the temperature in an oven.
Creating scales
Scale tool You specify the appearance of the scale. To place values on the scale as
a legend, use text objects. Because the scale doesn’t change at run time,
you cannot connect it to any tags.
To create a scale
In the General tab, specify what the scale looks like at run time.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the scale’s
border to have the same color as the scale’s background.
Clear the check box if you want the scale’s border to have a different
color than the scale’s background, and then choose a Border color. For
details, see “Border color” on page 17-156.
Back color Click the color box to open the palette, and then click a
color for the scale’s background.
Border color Click the color box to open the palette, and then click a
color for the scale’s border.
Line style Click a line style for the scale. If you want a line style other
than solid, the line width must be 1 pixel.
Line width Type a number between 1 and 32767 to change the line
thickness of the scale. Line width is measured in pixels.
Fore color Click the color box to open the palette, and then click a
color for the scale.
Tick direction Click the direction in which you want the ticks to face.
For example, if you are positioning the scale to the right of a vertical
bar graph, click right.
Major ticks Click the number of major ticks you want on the scale.
Minor ticks Click the number of minor ticks you want on the gauge’s
scale. Minor ticks are spaced evenly between the major ticks.
For control list selectors, display list selectors, or trends, you can create
different keys, depending on your needs:
To link one set of keys to several objects, create the keys, and then set
up the keys to send their press action to the object with focus. For
details, see “Send press to” on page 17-164.
Creating keys
You create and set up all of the keys in the same way, except that the
Move Up, Move Down, Page Up, and Page Down buttons can be set
up to auto repeat. The other keys have no auto repeat function.
For some basic definitions, and to understand how keys work, see
“How to use keys” on page 17-158.
To create a key
1. Click the tool for the kind of key you want to create.
Home Move Up
4. In the key’s Properties dialog box, fill in the fields on each tab, as
described in the sections that follow.
In the General tab, specify what the key looks like at run time.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the key’s
border to have the same color as the key’s background.
Clear the check box if you want the key’s border to have a different
color than the key’s background, and then choose a Border color. For
details, see “Border color” on page 17-162.
Back color Click the color box to open the palette, and then click a
color for the key’s background.
Border color Click the color box to open the palette, and then click a
color for the key’s border.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Blink Select the check box to make the key blink at run time. Clear the
check box to prevent the key from blinking at run time.
This is useful for keys that are positioned close together. A touch-
insensitive border on each key helps ensure that an adjacent key is not
pressed by mistake.
Vertical margin The number of pixels for the vertical touch margin.
The vertical margin is a touch-insensitive margin inside the object’s top
and bottom edges. If the operator presses the touch-insensitive margin,
the key press is not registered.
This is useful for keys that are positioned close together. A touch-
insensitive border on each key helps ensure that an adjacent key is not
pressed by mistake.
If the computer running the display does not have an internal speaker,
pressing the key does not trigger a beep.
Send press to Click Object With Focus to send the key’s press action
to the object that is selected on the display. For example, if a rectangle
object is selected, pressing the Move Up key sends the Move Up
command to the rectangle.
Click Linked Object to send the button’s press action to the object to
which the key is linked. For example, if the key is linked to a control list
selector, pressing the Move Up key sends the Move Up command to
the control list selector.
Linked object Click the Browse button, and then click the object you
want to link the key to.
Caption Type the text you want to appear on the key. If you don’t want
any text on the key, leave the Caption box blank.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Caption blink Select the check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the caption. Clear this check box to
truncate words that are too long for the width of the caption.
Caption back style Click Solid to cover the key’s background (such
as a graphic image) with the text. Click Transparent to allow the key’s
background to show through.
If you click the Browse button, the Image Browser appears. Click an
image in the list on the left, and then click OK.
Image back style Click Solid to cover the key’s background behind
the image. Click Transparent to allow the key’s background to show
through the image.
For monochrome images, any area of the image that is not black
becomes transparent when you change the Image back style to
Transparent.
For color images, any area of the image that is black will become
transparent when you change the Image back style to Transparent.
Image color Click the colored square to open the color palette, and
then click a color for a monochrome image. You cannot change the
color of grayscale or color images.
Image back color Click the colored square to open the color palette,
and then click a color for the background of a monochrome image. You
cannot change the background color of grayscale or color images.
Image blink Select the check box to make a monochrome image blink
at run time. Clear the check box to prevent the image from blinking at
run time. You cannot make grayscale or color images blink.
Image scaled Select the check box to scale the image to fit the area
of the key. Clear this check box to crop the image to the area of the key.
In the Timing tab, set up whether or not you want the key to repeat
automatically when the operator presses and holds the key down. You
can also set up the rate at which the key repeats.
Auto repeat rate Select the number of times per second a key press
is registered when the key goes into auto repeat mode. If you don’t want
the key to repeat automatically, click 0.
Auto repeat delay Click the number of milliseconds the key must
remain pressed before auto repeat starts.
For vertical arrows, if the value is less than or equal to the minimum
value, the arrow is at the bottom. If the value is equal to or greater than
the maximum value, the arrow is at the top.
For horizontal arrows, if the value is less than or equal to the minimum
value, the arrow is at the left. If the value is equal to or greater than the
maximum value, the arrow is at the right.
To create an arrow
Range To use the minimum and maximum values for the first
HMI tag in the expression, clear the Specify check box. To specify
minimum and maximum values, select the Specify box, and then
type values in the Min and Max boxes.
6. Click OK.
key objects. These are graphic objects that duplicate the functions
of keyboard keys. Use them with touch-screen terminals. For
details, see “Creating keys” on page 17-160.
The operator presses the keys to scroll up or down the list, or to make
selections from the list. The keys can be set up to work with the control
list selector that has focus, or with a specific control list selector. For
details about how keys work, see “How to use keys” on page 17-158.
Set up the states in the States tab of the control list selector’s Properties
dialog box.
You can set up 255 states for a control list selector. This provides the
operator with up to 255 selections in the list.
Control list selectors have three tags for sending and receiving data:
The Value tag triggers the control list selector’s action, for example
setting a motor’s speed to low, medium, or high.
The Enter handshake tag or expression resets the Enter tag, using
the Handshake reset type option specified in the Timing tab.
If another process changes the tag’s value to 2, the next time the
operator selects the next state, the tag’s value changes to 3.
When the operator presses the control list selector’s Enter key, the
highlighted state’s value is written to the programmable controller or
device.
When the operator presses the control list selector’s Enter key, the
following happens:
1. The timer for the Enter key control delay option begins timing.
When the time has expired, the Enter tag is set to 1.
2. The timers start for the Enter key handshake time, and Enter key
hold time.
If the Enter Handshake tag is not assigned, the Enter tag remains
set until the Enter key hold time expires.
The Enter Handshake tag resets the Enter tag like this:
Non-zero value resets the Enter tag when the Enter Handshake tag
is a non-zero value.
In either case, if the Enter key handshake time expires before the Enter
Handshake tag resets the Enter tag, an error appears in the diagnostics
log file.
Before the Enter tag is reset to 0 the operator can provide input to
other objects in the graphic display.
If the operator presses the Enter key for an object whose Enter tag has
not yet been reset (using a key, or external keyboard or keypad), an
error appears in the diagnostics log file.
If the graphic display is closed, the Enter tag is reset to 0, and any
handshake timing is also reset.
Use the Control List Selector tool to create a list that displays and
allows an operator to cycle through multiple options consecutively. The
Control List Selector tool
control list selector displays the current state of a process or operation
by highlighting the state.
Each time the operator presses a key, the control list selector’s highlight
changes position, and the Value tag changes to the value for the next
state. When the control list selector is in its last state and the operator
presses the key, the control list selector returns to its first state.
2. Drag the mouse to draw a control list selector the size you want.
In the General tab, specify what the control list selector looks like at
run time.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the control
list selector’s border to have the same color as the control list selector’s
background.
Clear the check box if you want the control list selector’s border to have
a different color than the control list selector’s background, and then
choose a Border color. For details, see “Border color” on page 17-179.
Back color Click the color box to open the palette, and then click a
color for the control list selector’s background.
Border color Click the color box to open the palette, and then click a
color for the control list selector’s border.
Pattern style Click a pattern style for the control list selector.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Selection back color Click the color box to open the palette, and
then click a color for the background of a selected item in the list.
Blink Select the check box to make the control list selector blink at run
time. Clear the check box to prevent the control list selector from
blinking at run time.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption truncate Click Word to cut off captions that exceed the
maximum length at the beginning of the word. Click Character to cut
off captions that exceed the maximum length, even in the middle of a
word.
The maximum caption length depends on the width of the control list
selector and the font size.
Number of states Click the number of states you want the control list
selector to have.
Clear this check box to send the state value as soon as the operator
selects a new state.
Key navigation Select this check box to allow the operator to navigate
to the control list selector and give it focus using the keyboard.
Tab index Either leave the default value or type a new value. Index
numbers determine the tab sequence among objects in a graphic
display. For details about tab sequences, see “Using index numbers” on
page 18-49.
Wrap around Select this check box to allow the list to wrap
automatically from the last item back to the first item when scrolling
down, and from the first item back to the last item when scrolling up.
Select state Click a state, and then set up the state on the right-hand
side.
Insert state Click a state, and then click Insert state. The new state
always appears above the selected state.
Delete state Click the state you want to delete, and then click Delete
state.
Value Type the integer value for each state. The Value tag changes to
this value when the selected state is in effect.
Caption Type the text you want to appear in the list for this state.
Caption back style Click Solid to cover the control list selector’s
background color with the caption’s background color. Click
Transparent to hide the caption’s background color.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
The caption’s background color is only visible on items in the list that
are not highlighed, and if the Caption back style is Solid.
Caption blink Select the check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
In the Timing tab, set up the timing and handshake settings for the
Enter key.
Enter key control delay Select the delay between the time the Enter
key is pressed and the Enter tag is set to 1. To set up the Enter tag, click
the Connections tab. For details, see page 17-185.
Enter key hold time Select the amount of time the Enter tag remains
set at a value of 1. This setting only applies if the Enter tag is set up,
and the Enter handshake tag is not set up in the Connections tab.
Handshake reset type Click Non-zero value to reset the Enter tag
when the Enter handshake tag is a non-zero value. Click Zero to non-
zero transition to reset the Enter tag when the Enter handshake tag
changes from zero to a non-zero value.
In the Connections tab, specify the tags or expression with which the
control list selector exchanges data.
Value Type a tag name, or click the Browse button to browse for a tag.
The Value tag triggers the state’s action. For example, the tag that
switches among recipes.
Enter Type a tag name, or click the Browse button to browse for a tag.
The Enter tag accepts values of 0 or 1 only. The tag determines how
long the Enter key press is registered. No further values can be entered
at the selector while the Enter tag is set to 1. For details about how the
Enter tag works, see “How to use control list selectors” on
page 17-172.
Use this tag or expression for Enter key handshaking if you want to
reset the Enter tag when a value in the programmable controller
changes.
The state values of all of the items that are visible in the list can be
written to the Visible States tag when the list scrolls. The Visible
States tag must be a data-server tag that supports arrays. You cannot
use an HMI tag.
The state value of the item at the top of the list can be written to the
Top Position tag when the list scrolls.
You can set up the piloted control list selector to be operator controlled
or remote controlled by assigning tags or expressions on the
Connections tab.
The value of the Remote Access tag determines who can select the
piloted control list selector’s states. When the piloted control list
selector is set up to be:
The operator can select this state. The operator cannot select
this state.
key objects. These are graphic objects that duplicate the functions
of keyboard keys. Use them with touch-screen terminals. For
details, see “Creating keys” on page 17-160.
The operator presses the keys to scroll up or down the list, or to make
selections from the list. The keys can be set up to work with the piloted
control list selector that has focus, or with a specific piloted control list
selector. For details about how keys work, see “How to use keys” on
page 17-158.
If the piloted control list selector contains more states than can be
displayed in the list simultaneously, the value of the Top Position tag (if
assigned) changes whenever the item at the top of the list changes.
If the visible states tag is assigned, the values assigned to all visible
states are written to the Visible States tag whenever the list scrolls. If all
the visible states are written, the tag must support arrays, and the array
must be the same length as the number of visible states in the piloted
control list selector.
You can also set up whether each state can be selected by the operator,
or remotely, for example by a programmable controller or other device,
or by both the operator and a remote device, or by neither. If you set
access to None, the state cannot be selected.
You can set up 255 states for a piloted control list selector. This
provides the operator with up to 255 selections in the list.
Piloted control list selectors have seven tags for sending and receiving
data:
The Value tag receives the value of the currently-selected state. You
can use this value to triggers an action, for example setting a motor’s
speed to low, medium, or high.
The Indicator tag selects an item in the list if the piloted control list
selector is being controlled remotely, for example by a
programmable controller.
The Top Position tag receives the value of the state that is the first
item in the list whenever the list scrolls.
For example, if the piloted control list selector has 5 visible states,
and the state values are written to programmable controller
addresses N7:0 through N7:4 using RSLinx Enterprise, the Visible
States tag should be an array tag with the following address:
where L5 indicates that the tag writes values to five addresses in the
array.
The Enter handshake tag or expression resets the Enter tag, using
the Handshake reset type option specified in the Timing tab.
if the Write on enter check box in the General tab is cleared, and the
operator selects an item in the list.
For details about the Write on enter check box, see page 17-197
if the Write on enter check box in the General tab is selected, and
the operator selects an item in the list, and then presses the Enter
key.
When the operator presses the Enter key associated with the piloted
control list selector, the highlighted state’s value is written to the
programmable controller or device.
If the Enter tag is assigned, when the operator presses the Enter key
associated with the piloted control list selector, the following happens:
1. The timer for the Enter key control delay option begins timing.
When the time has expired, the Enter tag is set to 1.
2. The timers start for the Enter key handshake time, and Enter key
hold time.
3. If the Enter Handshake tag is assigned, the Enter tag remains set
until the Enter key handshake time expires or until it is reset by the
Enter Handshake control, whichever happens first.
If the Enter Handshake tag is not assigned, the Enter tag remains
set until the Enter key hold time expires.
The Enter Handshake tag resets the Enter tag like this:
Non-zero value resets the Enter tag when the Enter Handshake tag
is a non-zero value.
Zero to non-zero transition resets the Enter tag when the Enter
Handshake tag changes from zero to a non-zero value.
In either case, if the Enter key handshake time expires before the Enter
Handshake tag resets the Enter tag, an error appears in the diagnostics
log file.
Before the Enter tag is reset to 0 the operator can provide input to
other objects in the graphic display.
If the operator presses the Enter key for an object whose Enter tag has
not yet been reset (using a key, or external keyboard or keypad), an
error appears in the diagnostics log file.
If the graphic display is closed, the Enter tag is reset to 0, and any
handshake timing is also reset.
Use the Piloted Control List Selector tool to create a list that displays
and allows an operator to cycle through multiple options consecutively.
Piloted Control List
The piloted control list selector displays the current state of a process
Selector tool
or operation by highlighting the state.
2. Drag the mouse to draw a piloted control list selector the size you
want.
In the General tab, specify what the piloted control list selector looks
like at run time.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select this check box if you want the piloted
control list selector’s border to have the same color as the selector’s
background.
Clear the check box if you want the piloted control list selector’s border
to have a different color than the selector's background, and then
choose a Border color.
Back color Click the color box, and then click a color for the piloted
control list selector’s background.
Border color Click the color box, and then click a color for the
piloted control list selector’s border.
Pattern style Click a pattern style for the piloted control list selector.
Pattern color Click the color box, and then click a color for the
pattern.
Selection back color Click the color box, and then click a color for
the background of a highlighted item in the list.
Selection fore color Click the color box, and then click a color for
the text of a highlighted item in the list.
Blink Select this check box to make the selector blink at run time.
Clear the check box to prevent the selector from blinking at run time.
The maximum caption length depends on the width of the selector and
the font size.
Number of states Click the number of states you want the selector to
have.
Write on enter Select this check box to send the piloted control list
selector’s state value to the programmable controller when the operator
presses Enter.
Clear this check box to send the state value as soon as the operator
scrolls to a new state.
Select state Click a state, and then set up the state on the right-hand
side.
Delete state Click the state you want to delete, and then click Delete
state.
5. Click Current State to paste the settings to the selected state only.
Click All States to paste the settings to all of the object’s states.
6. Click OK.
Value Type the integer value for each state. The Value tag changes to
this value when the state is selected.
Caption Type the text you want to appear in the list for this state.
The caption’s background color is visible only on items in the list that
are not highlighted, and if the Caption back style is Solid.
Caption blink Select this check box to make the caption blink at run
time. Clear the check box to prevent the caption from blinking at run
time.
Caption back style Click Solid to cover the piloted control list
selector’s background color with the caption’s background color. Click
Transparent to hide the caption’s background color.
Alignment Click a position in the grid, relative to the piloted control
list selector. In the default alignment position, the text is positioned at
the left of the piloted control list selector, inside the border (if a border
is used).
Access Click Operator and Remote to allow both the operator and a
remote device to select this state.
Click Remote to allow only the remote device to select the state.
Enter key control delay Select the delay between the time the Enter
key is pressed and the Enter tag is set to 1. To set up the Enter tag, click
the Connections tab. For details, see page 17-185.
Enter key hold time Select the amount of time the Enter tag remains
set at a value of 1. This setting only applies if the Enter tag is set up,
and the Enter handshake tag is not set up in the Connections tab.
Enter key handshake time Select the maximum amount of time the
Enter tag remains set at a value of 1. This setting only applies if the
Enter tag and Enter handshake tag are both set up in the Connections
tab.
Handshake reset type Click Non-zero value to reset the Enter tag
when the Enter handshake tag is a non-zero value. Click Zero to non-
zero transition to reset the Enter tag when the Enter handshake tag
changes from zero to a non-zero value.
Value Type a tag name, or click the Browse button to browse for a tag.
You can use the Value tag to trigger an action when the operator selects
the state. For example, you can use the tag to change a motor’s speed
to a new setting.
Indicator Type a tag name or expression, or click a Browse button to
browse for a tag, or compose an expression. The Indicator tag or
expression shows which state is selected when the piloted control list
selector is controlled remotely. For example, the Indicator tag or
expression can be used to show which recipe is selected.
Remote Access Type a tag name or expression, or click a Browse
button to browse for a tag, or compose an expression. The Remote
Access tag determines whether the piloted control list selector is
controlled by the operator, or controlled remotely, for example by a
programmable controller. If the Remote Access tag is not assigned, or
when its value is zero, the operator controls the piloted control list
selector. When the Remote Access tag has a non-zero value, the
selected state is set remotely using the Indicator tag.
For an example of the syntax for arrays in OPC tags using RSLinx as a
data server, see “How to use the Connections tab for piloted
control list selectors” on page 17-191.
Enter Type a tag name, or click the Browse button to browse for a tag.
The Enter tag accepts values of 0 or 1 only. The tag determines how
long the Enter key press is registered. The piloted control list selector
cannot be operated while the Enter tag is set to 1. For details about how
the Enter tag works, see “How Enter-key handshaking works” on
page 17-193.
The Enter handshake tag or expression resets the Enter tag, using the
Handshake reset type option specified in the Timing tab.
Use this tag or expression for Enter key handshaking if you want to
reset the Enter tag when a value in the programmable controller
changes.
2. Drag the mouse to draw the tag label field. When the tag label is
the size you want, release the mouse button.
To select a tag
name, click the
Browse button.
5. Click OK.
Display list selectors work with graphic displays located in the home
area only. For details about the home area, see page 5-9.
You can decide how many, and which displays are shown in the list. You
can assign each state in the display list selector to a different graphic
display. You can label each state using either the name of the graphic
display, or any caption you type for the state.
Use the Display List Selector tool to create list of displays in the
application. Each graphic display is represented by a different state in
Display List Selector tool
the display list selector.
You specify the graphic displays associated with each state. At run time,
the operator selects a graphic display by highlighting the state in the list,
and then pressing a key to select the state.
Display List Selector tool 2. Drag the mouse to draw an display list selector the size you want.
In the General tab, specify what the display list selector looks like at run
time.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the display
list selector’s border to have the same color as the display list selector’s
background.
Clear the check box if you want the display list selector’s border to have
a different color than the display list selector’s background, and then
choose a Border color. For details, see “Border color” on page 17-209.
Back color Click the color box to open the palette, and then click a
color for the display list selector’s background.
Border color Click the color box to open the palette, and then click a
color for the display list selector’s border.
Pattern style Click a pattern style for the display list selector.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Selection fore color Click the color box to open the palette, and then
click a color for the foreground of a selected item in the list.
Blink Select the check box to make the display list selector blink at run
time. Clear the check box to prevent the display list selector from
blinking at run time.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Caption truncate Click Word to cut off captions that exceed the
maximum length at the beginning of the word. Click Character to cut
off captions that exceed the maximum length, even in the middle of a
word.
The maximum caption length depends on the width of the display list
selector and the font size.
Number of states Click the number of states you want the display list
selector to have.
Tab index Either leave the default value or type a new value. Index
numbers determine the tab sequence among objects in a graphic
display. For details about tab sequences, see “Using index numbers” on
page 18-49.
Wrap around Select this check box to allow the list to wrap
automatically from the last item back to the first item when scrolling
down, and from the first item back to the last item when scrolling up.
Select state Click a state, and then set up the state on the right-hand
side.
Insert state Click a state, and then click Insert state. The new state
always appears above the selected state.
Delete state Click the state you want to delete, and then click Delete
state.
Display Type the name of the graphic display that opens when the
operator highlights this state and presses Enter. To browse for a
graphic display, click the Browse button.
Parameter file Type the name of the parameter file you want to run
when the operator highlights this state and presses Enter. To browse
for a parameter file, click the Browse button.
A parameter file assigns tags to tag placeholders in the display when the
display opens.
Display position Select this check box to specify the Top position and
Left position for the display. These properties apply only to displays of
type On Top or Overlay. These properties do not apply to displays of
type Replace.
Top position Type the number of pixels from the top of the screen at
which you want the display positioned.
Left position Type the number of pixels from the left edge of the
screen at which you want the display positioned.
Caption Type the text you want to appear as the name of the graphic
display in the display list selector.
Caption back style Click Solid to cover the display list selector’s
background with the text. Click Transparent to allow the display list
selector’s background to show through.
Caption color Click the color box to open the palette, and then click
a color for the caption’s text.
Caption back color Click the color box to open the palette, and then
click a color for the caption’s background.
The caption’s background color is only visible if the Caption back style
is Solid.
Alignment Click a position in the grid for the text, relative to the
display list selector. In the default alignment position, the text is aligned
at the left edge of the display list selector.
For information about how local messages work, see “Using local
messages” on page 17-231.
In the local message file, type a message, and then assign a trigger value
to the message. At run time, when the local message display’s Value tag
matches the trigger value in the local message file, the corresponding
message is displayed.
The Value tag is rounded to the nearest integer. If the value does not
match any of the trigger values in the specified message file, the
display is filled with question marks (?).
If the message is too long to fit in the list, the last displayed
character is replaced with an asterisk (*).
You specify the messages in a local message file, and then set up the
local message display to show the messages when the local message
display’s Value tag matches a trigger value in the local message file.
1. Create a local message file. For details, see “Using local messages”
on page 17-231.
3. Drag the mouse to draw a local message display the size you want.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the local
message display’s border to have the same color as the local message
display’s background.
Clear the check box if you want the local message display’s border to
have a different color than the local message display’s background, and
then choose a Border color. For details, see “Border color” on
page 17-218.
Back color Click the color box to open the palette, and then click a
color for the local message display’s background.
Border color Click the color box to open the palette, and then click a
color for the local message display’s border.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Fore color Click the color box to open the palette, and then click a
color for the foreground of the local message display.
Blink Select the check box to make the local message display blink at
run time. Clear the check box to prevent the local message display from
blinking at run time.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the local message display. Clear this check
box to truncate words that are too long for the width of the local
message display.
If no message exists for the trigger value, the local message display is
filled with question marks (?).
With a recipe field, operators can load all the values from a recipe file
into the numeric and string input fields in one keystroke rather than
having to enter values one by one. Operators can then write all these
values to the programmable controller with another keystroke.
IMPORTANT Each graphic display can have only one recipe field.
4. In the Default recipe name box, type the name of the recipe file to
and from which values will be saved and restored. Do not include a
file extension.
6. Click Left, Center, or Right to specify how the recipe file name will
be aligned within the field.
8. Click OK.
2. Type one entry per line. Type one entry for each input field in the
display. You can have up to 500 entries.
5. Type a file name in the recipe field and press Enter. The recipe
dialog box opens with the name in the recipe file field.
6. To save the values in the input fields and at the same time create a
recipe file, click Save.
Recipe field
Index number
Value
Tag name
Use the mouse. Double-click the recipe field to open the Recipe
dialog box and save or restore the recipe file.
Press Ctrl-R to move to the field and then press Enter to restore the
contents of the recipe file.
Press Ctrl-W to move to the field and then press Enter to save the
recipe file.
a. In the recipe field, type the name of a recipe file and press
Enter, or click in the recipe field and press Enter. The Recipe
dialog box opens.
c. Click Restore.
You can also restore the values from a recipe file using the RSView
RecipeRestore command. For details, see Appendix A, RSView
commands, or see Help.
a. In the recipe field, type the name of a recipe file and press
Enter, or click in the recipe field and press Enter. The Recipe
dialog box opens.
c. Click Save.
You can also save the values from a recipe file using the RSView
RecipeSave command. For details, see Appendix A, RSView commands,
or see Help.
A time and date display shows the current time and date in a graphic
display. Use the Time and Date Display tool to create a box that shows
Time and Date Display
the time and date in a graphic display. You specify the appearance of
tool
the time and date display, and the format in which the time and date
appear.
2. Drag the mouse to draw a box size you want for the time and date
display.
4. In the Time and Date Display Properties dialog box, fill in the
fields on each tab, as described in the sections that follow.
Border style Click a border style in the list, or click None to remove
the border.
Border uses back color Select the check box if you want the time and
date display’s border to have the same color as the time and date
display’s background.
Clear the check box if you want the time and date display’s border to
have a different color than the time and date display’s background, and
then choose a Border color. For details, see “Border color” on
page 17-230.
Back color Click the color box to open the palette, and then click a
color for the time and date display’s background.
Pattern style Click a pattern style for the time and date display.
Pattern color Click the color box to open the palette, and then click
a color for the pattern.
Fore color Click the color box to open the palette, and then click a
color for the foreground of the time and date display.
Blink Select the check box to make the time and date display blink at
run time. Clear the check box to prevent the time and date display from
blinking at run time.
Font, size, and style Click a font for the caption in the font list. Type
or click a size for the font in the size box. Click B to make the font bold,
click I to make the font italic, click U to underline the text.
For design guidelines and ideas about choosing fonts, see page 17-2.
Word wrap Select this check box to wrap words to the next line if they
are too long for the width of the time and date display. Clear this check
box to truncate words that are too long for the width of the time and
date display.
Time and date format Click the format in which you want the time
and date displayed.
You create messages in the Local Messages editor, and then display
them in local message displays, which you create in the graphic display
editor.
You can use multiple local message displays in your application, and
you can link each local message display to a different local message file.
Or, you can use the same local message file for multiple local message
displays.
For information about local message displays, see “How to use local
message displays” on page 17-215.
For example, the tag that shows whether the valve is open or closed,
or the tag that shows the temperature in the boiler.
2. Determine what values for those tags you want to use to trigger
local messages.
For example, trigger a ‘Valve open’ message when the valve’s tag is 1
(to represent ‘open’), or trigger a ‘Low Temperature’ message when
the value of the boiler’s temperature tag is 120 (to represent 120°F
or 49°C).
At bottom 1
Raising 2
Stopped between the top and bottom 3
Lowering 4
At top 5
5. In the object’s Properties dialog box, click the General tab, and
then select the Hoist status message file.
6. Click the Connections tab, and then type Hoist_Status in the Value
tag box.
Because trigger values cannot be 0, if you use a digital HMI tag, you
can only use the value 1 to trigger a message. If you use an analog tag
or an expression, you can use any non-zero integer or floating point
value to trigger a message. Floating point values are rounded to the
nearest integer.
When the Value tag’s value is 0, the local message display is cleared.
Trigger value Type a non-zero integer value. When the Value tag
or expression changes to this value, the corresponding message
appears in the local message display. This column cannot be blank.
3. To save the message file, on the File menu click Save. In the Enter
Component Name box, type a name for the file, and then click
OK.
4. Click Close.
1. Right-click the Message cell in the spreadsheet, and then click Edit
String.
2. In the String Edit dialog box, click Insert Variable, and then click
the type of variable you want to insert.
To delete a message
X Click any cell in the row you want to delete, and then press Delete.
To delete multiple messages, shift-click the cells.
Type the messages in the order you want them to appear in the
Local Messages editor.
1. In the spreadsheet application, select the cells for the trigger values
and messages to copy, and then press Ctrl-C (or right-click the
selected cells and then click Copy).
2. In the Local Messages editor, click in the Trigger value column for
the first message and then press Ctrl-V (or right-click in the
column and then click Paste).
The cell contents from the spreadsheet application are pasted into
the local messages editor.
linking pastes the object into the graphic display and retains links to
the source file in addition to allowing it to be edited. If the source
file is changed, the object in the display is changed.
6. Click OK.
To convert an object
2. On the Edit menu, click Paste Special. The Paste Special dialog box
opens.
Paste copies the contents of the clipboard into the active graphic
but does not link to the source application. This is an embedded
object.
Paste Link copies the contents of the clipboard into the active
graphic and links it to the source application. This is a linked object.
This option is not available if the object comes from an application
that does not support OLE linking.
4. Click the file format in which you want to paste the object into
RSView.
5. Click OK.
For example, you can embed the Microsoft Forms ActiveX objects in
RSView graphic displays. If you attach an RSView tag to an ActiveX
object’s Value property, the object’s behavior changes as the tag’s value
changes.
In RSView you can use events to change the value of a tag, or to run an
RSView command or macro. When the event occurs, the command or
macro runs. To use the ActiveX object to change a tag’s value, associate
the tag with one of the object’s event parameters.
ActiveX Control tool On the Objects toolbar, click the ActiveX Control tool.
On the Objects menu, click ActiveX Control.
If you have set up tools in the ActiveX Toolbox, as described on
page 17-245, click the tool in the toolbox, draw a box the size you
want for the object, and then skip the rest of these steps.
If some objects you have installed do not appear in the list, the
objects might not be registered. To register them, click Register, and
then locate the objects you want to add.
To remove an object from the list, click the object and then click
Unregister.
4. Click OK.
2. Right-click the lower part of the tab you want to add tools to, and
then click Additional Controls.
3. In the list of installed controls, select the check boxes of the tools
you want to add, and then click OK.
You can use up to 10 tabs in the toolbox, to group related tools. The
number of tabs you can view simultaneously depends on the length of
the tab names.
3. If you are renaming the page, type a name in the Caption box.
You can also type descriptive text in the Control Tip Text box. This
text becomes a ToolTip, and appears when the operator positions
the cursor over the tab at run time.
When you click Delete Page, the tab that has focus is deleted. When a
tab has focus (is selected) a dotted line appears around the label’s text.
1. In the ActiveX Toolbox, click the icon for the object you want to
add.
When you release the mouse button, the object appears in the
graphic display.
To deploy ActiveX controls automatically, you must create .cab files for
the ActiveX controls, and then put the .cab files in the same folder
where you installed RSView. To do this, use the program
CABARC.exe located on the computer that is running the HMI
server, in the folder \Documents and Settings\All Users\Documents\
RSView Enterprise\ActiveX Control Setup.
For information about creating .cab files, see the text file,
CreatingCabFiles.txt in the ActiveX Control Setup folder. The text file
contains examples for creating .cab files, and information about the
naming conventions that must be used.
If you open a graphic display containing ActiveX objects that are not
installed, the graphic display runs, but a shaded rectangle appears in
place of the ActiveX object.
For added security, the Signature button can also be set up so that
authorization by another person, such as a supervisor, is required
before the operation can be carried out.
At run time, the action can be prevented from being carried out and an
error message can be displayed if a user name or password is incorrect,
or if other information, such as an operator’s comment, is required but
not provided.
The Signature button does not change the way RSView graphic objects
work. For example, any numeric input fields in a graphic display will
download their values to a programmable controller when the user
presses Enter or Page Down, even if the Signature button appears on
the display.
Set the Page Up, Ctrl-Page Up, Page Down, and Ctrl-Page Down
keys to do nothing using display keys. For details about display key
animation, see page 18-60.
issuing a command.
2. If the ActiveX toolbox is not visible, click the View menu, and
then click ActiveX Toolbox to make it visible.
When you release the mouse button, the Signature button appears
in the graphic display.
Set Value If the button’s operation is Set Value, specify the maximum,
minimum, and number of decimal places that is set for the tag. If
maximum and minimum are the same value, they are ignored.
Minimum Specify the minimum allowable value that the tag can be
set to.
Maximum Specify the maximum allowable value that the tag can be
set to.
Domain Type the name of the domain the operator and approver are
members of, or click the Browse button, and then select a domain.
Browse button
Enable Performer Authentication Select the check box to enable the
User name and Password boxes for the operator in the Authentication
dialog box at run time. This means that the person who is currently
logged in to the client must verify their login identity before they can
perform the operation.
Performer Group Specify the name of the group that the performer
must be a member of. If the Performer group box is blank, the
performer does not need to belong to any group.
Enable Approver Authentication Select the check box to enable the
User name and Password boxes for the approver in the Authentication
Properties Select the property for which you want to specify a color.
Color Set Click the color set you want to use. You can use either a
standard set of colors, or you can select the Windows System Colors.
Color Palette Click the color you want to use for the property. You
can also create custom colors.
In the Connections tab, specify the tag whose value is set by the
Signature button. The tag must be associated with the Value property
of the button.
Value Type the name of a tag or click the Browse button to open the
Tag browser, and then select a tag.
The double-headed arrow indicates that the Signature button can read
from, or write to the tag.
To change the style of the button’s font, use the Font property in the
Properties tab of the Property Panel. To change the font’s color, change
the ForeColor property.
You can also use the Property Panel to change other properties for the
button, such BackColor, Height, and Width.
For details about using the Property Panel, see page 16-34.
Animating
graphic objects
This chapter describes the various types of animation you can attach to
graphic objects, and outlines how to:
Types of animation
To animate objects in a graphic display, you must create the objects, and
then you can attach different kinds of animation to them. Once you
have created graphic objects, you can:
Some graphic objects, such as the Multistate Indicator, can have only
Visibility animation. Others can have as many types of animation as you
like. For example, you can apply both width and height animation to the
drawing objects to give them the appearance of moving into or out of
the display as they shrinks and expand.
To attach key animation, use the Object Key and Display Key dialog
boxes. For information about key animation, see “Associating objects
and displays with keys” on page 18-45.
The Animation dialog box is a floating dialog box, which means you
can have it open all the time and can move it around the screen, select
other objects, and open other dialog boxes.
Animation tabs
Expression area
Expression range.
Animation tabs
Click the tab for the type of animation you want to set up.
Expression area
To supply a tag name for an expression, click the Tag button and then
click a name, or type the name. If you do not specify the minimum and
maximum values, and if you use multiple tags in an expression, the first
HMI tag is used for the minimum and maximum values.
Specify how the object’s appearance should change based on the result
of the expression.
For some types of animation, you have to specify a change of state. For
example, an object with visibility animation will switch between visible
and invisible.
If you do not want to use the values set for the tag or are using data
server tags, specify minimum and maximum values. The range of
motion for the object is related to the minimum and maximum values
for the expression. The object moves from the At Minimum position
to the At Maximum position as the expression value changes to the
maximum value.
If you do not specify minimum and maximum values, RSView uses the
minimum and maximum values for the first tag in the expression. For
Apply Validates and then applies the animation set up for the selected
object or group of objects. Clicking another tab is the same as clicking
Apply—the animation you have set up is validated, and then applied to
the object.
Close Prompts you to apply your changes and then closes the dialog
box.
Because the Animation dialog box stays open, you can go back and
forth between the dialog box and the graphic display. This makes it easy
to set the range of motion for an object because you do not have to
know how many pixels you want an object to move. Instead, use the
RSView Object Smart Path (OSP) feature.
Testing animation
You can test the animation you have set up in a graphic display quickly
Test Display mode by switching to Test Display mode. When you are finished testing,
switch back to Edit Display mode to continue editing. To switch
between test and edit modes, use the buttons on the toolbar or the
Edit Display mode items on the View menu.
IMPORTANT Test Display mode is not the same as running the display
in the RSView SE Client. Test Display mode does not
change the appearance or position of the display as set
up in the Display Settings dialog box, and you cannot
switch among displays while in Test Display mode.
Tag names
You can use tag names that already exist in a device or that you have
already added to the tag database, or you can use a new tag name that
you will add to a device or to the tag database later.
Tag placeholders
Tag placeholders allow you to create displays that can be used with
different tags. A placeholder is a cross-hatch character (#) followed by
a number between 1 and 500. Tag names are substituted for
placeholders when the display is run. If you are using HMI tags, you
can also substitute folder names for part of the tag name. For example,
When setting up object keys, you can specify the [Tag] parameter as a
placeholder for a tag name or any character string. The [Tag] parameter
is used for object keys only. For more information about this
parameter, see “Using the Current [Tag] parameter” on page 18-54.
Using expressions
Many types of animation require an expression. You can use
expressions involving tag values, constants, mathematical equations,
and if – then – else program logic for animation. A tag name or tag
placeholder can be included as part of an expression, or it can stand
alone as the entire expression.
You can limit the range of values by specifying constants. For example,
if you specify a minimum of 0 and a maximum of 100, the object will
not react to values outside of this range. So, even if the expression
results in 200, the object does not change from its At Maximum
position.
If you do not specify the minimum and maximum values, and if you use
multiple tags in an expression, the first HMI tag is used for the
minimum and maximum values.
Move the objects in the Graphic Displays editor. This is called OSP
(Object Smart Path). For details, see below.
2. Open the Animation dialog box and then click the Horizontal
Slider tab.
5. In the Graphic Displays editor, drag the slider to the position that
indicates the lowest number in the range.
6. In the Graphic Displays editor, drag the slider to the position that
indicates the highest number in the range.
If you want the object to be visible when the tag or expression value
is true—that is, when it does not equal zero—click Visible.
5. Click Apply.
Color animation does not affect string input, numeric input, or recipe
fields. Color for these fields is defined in the Display Settings dialog
box.
To return to the
default colors and
thresholds, click
this button.
4. In the list box, select a threshold (A through P) for which you will
set up a value and colors. You can change the default values and
colors for thresholds A and B.
5. In the Value box, type the threshold value. When the expression
value reaches this threshold, the object’s color changes.
Solid colors have only one foreground and one background color.
8. In the Blink Rate box, specify how many seconds each blink cycle
will be. For example, if you specify four seconds, the object will be
one color for two seconds and the other color for two seconds.
9. Click Apply.
For details about creating text and other graphic objects, see page 17-2.
3. Open the Animation dialog box, and then click the Color tab.
Attach color animation as follows:
f. Click each color box to open the color palette and then click a
color.
4. Click Apply.
c. Click Apply.
6. Click Apply.
With fill animation, the level of fill in an object changes based on a tag’s
value in relation to its minimum and maximum values. The object’s fill
level is proportional to the value of the expression. For example, if the
value of the expression is halfway between the minimum and maximum
values, the object will be half full.
Fill animation does not affect string input, numeric input, or recipe
fields, nor does it affect push buttons of type Button. It also does not
affect transparent objects or line objects, even if those objects are
grouped into a single object.
8. Click Apply.
5. Set the starting point for the object by dragging the object or by
typing a value, and then click the At minimum check box.
6. Set the ending point for the object by dragging the object or by
typing a value, and then click the At maximum check box.
7. Click Apply.
5. Set the starting point for the object by dragging the object or by
typing a value, and then click the At minimum check box.
6. Set the ending point for the object by dragging the object or by
typing a value, and then click the At maximum check box.
7. Click Apply.
When you first click the object, its width is 100 percent.
5. Set the minimum width for the object by doing one of the
following:
Click a handle on the left or right side of the object and drag it
to resize the object.
Type the width you want the object to be when the expression
evaluates to its minimum value.
Select the At minimum check box.
6. Set the maximum width for the object by doing one of the
following:
Click a handle on the left or right side of the object and drag it
to resize the object.
Type the width you want the object to be when the expression
evaluates to its maximum value.
Select the At maximum check box.
This is the part of the object that does not move. For example, click
Left if you do not want the left side of the object to move. As the
value of the expression changes, the object will grow to or shrink
from the right.
8. Click Apply.
When you first click the object, its height is 100 percent.
5. Set the minimum height for the object by doing one of the
following:
Type the height you want the object to be when the expression
evaluates to its minimum value.
6. Set the maximum height for the object by doing one of the
following:
Type the height you want the object to be when the expression
evaluates to its maximum value.
7. Click an anchor point. This is the part of the object that does not
move. For example, click Top if you do not want the top of the
object to move. As the value of the expression changes, the object
will grow to, or shrink from, the bottom.
8. Click Apply.
the tag or expression that will provide values to rotate the object
the range of values for the tag or expression (values outside the
range will not be used to rotate the object)
Tag values 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Tag values 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Tag values 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
To use the HMI tag’s range of values to rotate the object, click
Use tag’s min and max property values.
To specify a range of values within which the object rotates,
click Use constant, and then type a minimum and maximum
value. When the tag’s value falls within these values, the object
rotates.
To obtain minimum and maximum values from tags, click Read
from tags, and then specify a tag for the minimum value, and a
tag for the maximum value. When animation starts, the tags are
read once to determine their values. The values are not updated
until animation is stopped and started again.
5. Set the center of rotation using one of the methods described
below. The center of rotation is the point around which the object
will rotate. This point can be inside or outside the object. If it is
outside, the object will appear as if it is moving in an arc.
If you use the preset center points to define the center of rotation,
the object will rotate around the same point even if the object is
resized. For example, the top-left corner will always be the center of
rotation no matter what size the object is.
Specifying coordinates
The default coordinates 0,0 are the center of the object; all
coordinate values are relative to the center. To specify coordinates,
do one of the following:
Using the mouse, drag the circle and crosshair to the desired
The circle and crosshair
center of rotation, and then click the option button next to the
indicate the object’s
center of rotation.
box in which the coordinates are displayed.
Type values in the coordinates box.
6. Set the range of motion for the object.
To set the minimum
Click the Rotate tool, and then drag the object to the desired
Rotate tool degree of rotation using the mouse.
Type the desired degree of rotation (this value is relative to the
object’s current position). For clockwise rotation, use a positive
number. For counterclockwise rotation, use a negative number.
When you are finished, select the At minimum check box.
Click the Rotate tool, and then drag the object to the desired
degree of rotation using the mouse.
Type the desired degree of rotation (this value is relative to the
object’s current position). For clockwise rotation, use a positive
number. For counterclockwise rotation, use a negative number.
When you are finished, select the At maximum check box.
7. Click Apply.
5. Click Apply.
With horizontal slider animation, you can create a graphic object that
sets the value of a tag. To do this, define a path for the object and then
use the mouse to move the object horizontally. The pixel position of
the object is translated into values that are written to the tag. An object
can have both vertical and horizontal slider animation.
3. Type the name of the tag whose value will be determined by the
slider.
5. Set the starting point for the slider object by dragging the object or
by typing a value, and then select the At minimum check box.
7. Click Apply.
3. Type the name of the tag whose value will be determined by the
slider.
5. Set the starting point for the slider object by dragging the object or
by typing a value, and then select the At minimum check box.
6. Set the ending point for the slider object by dragging the object or
by typing a value, and then select the At maximum check box.
7. Click Apply.
With OLE (Object Linking and Embedding) verb animation, you can
set up OLE objects to perform certain actions. When the expression
evaluates to true—that is, when the expression does not equal zero—
the specified OLE verb is activated. The verbs available depend on the
OLE object. Typical verbs include open, and edit.
4. Click the OLE Verb list to display the OLE verbs available for the
selected OLE object. Click a verb in the list.
6. Click Apply.
There are two ways you can animate an ActiveX object’s properties,
methods, and events with data from RSView:
In the Visual Basic Editor, using VBA code. This is the more
complex way, but more flexible.
You can also change an ActiveX object’s properties without using tags.
If you choose this method, the object’s properties do not change
dynamically at run time. You make static changes to an ActiveX object’s
properties just as you do for any other graphic object—in the
Properties tab in the Property Panel. For more information, see “Using
the Property Panel” on page 16-34.
All objects have a default name. You can change the default name of all
objects, including ActiveX objects.
The middle column indicates whether the property updates the tag,
or the tag updates the property:
You can:
To call an object’s method, the object must have a name. For details
about naming ActiveX objects, see page 18-40.
Use the RSView Invoke command to call the method for the named
object.
parameter The tag name or constant that the method will use.
display_name.object.method(parameter1, parameter2, …)
2. Click the event you want to attach the command or macro to.
To open the
Command Wizard,
click this button.
5. Type the tag name or click the Browse button to open the Tag
Browser, and then select a tag. The tag’s value is determined when
the ActiveX event occurs.
6. To log the event, select the check box Log event to Diagnostics
Log, and then if necessary, set up logging in the Diagnostics Setup
editor.
Object keys and display keys are different from client keys. Object keys
and display keys are active only while a particular object or display has
input focus. Client keys are active at all times. Object and display keys
are discussed on the following pages. For details about client keys, see
page 23-12.
For details about the order of precedence among object, display, and
client keys, see page 23-7.
Object keys associate graphic objects with keys. When an object has
input focus, an operator can use keys to interact with the object.
For detailed information about how keys work at run time, see
“Specifying the behavior of interactive objects” on page 16-70.
Imagine you have a graphic display showing a tank with two valves. The
two valves control the flow in and out of the tank. Both valves have
been set up with object key animation as follows:
Valve 1 F2 = Open
F3 = Close
Valve 2 F2 = Open
F3 = Close
At run time, operators can select either valve, and then press F2 to
open it and press F3 to close it.
1. Click an object.
3. Click Add.
4. In the Key list, click a key. If desired, select one or both modifiers.
Some keys are normally reserved for use by Windows and RSView.
For details about assigning reserved keys as object, display, or client
keys, see “Reserved keys” on page 23-10.
5. Click OK.
The key you added appears in the Select key list. If you selected a
modifier, the first letter of that modifier is also displayed. If you
The information in the Select key list appears in the key list at run
time, so operators know which keys are associated with an object
and a display. For details about the key list, see “Viewing the key list
at run time” on page 18-64.
7. In the Press Action box and, if desired, in the Release Action box,
type an RSView command or a macro. Separate multiple
commands or macros with a semi-colon (;) or place them on
separate lines.
The command or macro is the action that will occur when the key
is pressed or released.
8. If you want an action to repeat while the key is held down, type the
RSView command or macro name in the Repeat Action box.
9. If, at run time, you want a highlight box to appear around the
object when it has input focus, select the check box, Highlight
when object has focus. For details, see “Specifying the behavior of
interactive objects” on page 16-70.
For details about the Tab index box, see “Using index numbers” on
page 18-49. For details about the Current [Tag] box, see “Using the
Current [Tag] parameter” on page 18-54.
button objects
ActiveX objects
For example, if you create a numeric input object, then a button object,
and then a string input object, the objects will have the index numbers
1, 2, and 3.
specify which tag value goes into which numeric or string input field
in a recipe file. For details about recipe files, see “Creating a recipe
file” on page 17-222.
Double-click the object and then check the number in the Tab
index box.
Right-click the object, click Property Panel, and then scroll down to
find the number in the TabIndex box.
For objects with object key animation, right-click the object, click
Object Keys, and then check the number in the Tab index box.
For example, if you have created four input fields, you can change the
order of their index numbers. You can change input field 4 to index
number 1. However, you cannot change input field 4 to index
number 5, because you have not created five input fields.
When you change an index number, other numbers are adjusted so two
objects do not have the same number and there are no gaps in the
numbering.
3. Click OK.
3. Click OK.
3. Click OK.
A tab sequence is the order in which users can move through a series
of objects using the Tab key.
To create a tab sequence, use index numbers. For details about using
index numbers, see page 18-49.
For example, if you want F2 to set the value of a selected object’s tag to
0, you would set up a display key for F2, using the [tag] parameter, and
then set up object keys for each object on the screen, specifying which
tag to use for each object.
Summary of steps
1. Create a graphic object.
At run time, when the object is selected and the display key is pressed,
the contents of the Current [Tag] field replace [tag] in the RSView
command.
1. In the Display Keys dialog box, assign two display keys. For the
press action, type Set [tag].
2. In the Object Keys dialog box, type the tag name in the Current
At run time, the operator can select any valve object, and then press F2
to open the valve and F3 to close it.
1. In the Display Keys dialog box, create a display key. For details, see
page 18-61. In the Press Action box, type Help [tag].
To display the alarm summary for the machine, the operator can
position the cursor over any object related to that machine in a graphic
display, and then press a Display Key.
2. In the Display Keys dialog box, assign a display key. In the Press
Action box, type Display AlmSumm /t[tag].
Using the keys, operators can interact with the graphic displays at run
time.
If the Main Menu display is of the Overlay display type, you must use
the Abort command to close the active display.
For details about how keys and other interactive objects work at run
time, see “Specifying the behavior of interactive objects” on
page 16-70.
2. Click Add.
Some keys are reserved for use by Windows and RSView. Reserved
keys do not appear in the Key list.
4. Click OK.
The key you added appears in the Select key list. If you selected a
modifier, the first letter of that modifier is also displayed. If you
create a label in the next step, it also appears in the Select key list the
next time you open the Display Keys dialog box.
The information in the Select key list appears in the key list at run
time, so operators know which keys are associated with an object
and a display. For details about the key list, see “Viewing the key list
at run time” on page 18-64.
6. In the Press Action box and, if desired, in the Release Action and
Repeat Action boxes, type an RSView command or a macro, or
Browse button click the Browse button to open the Command Wizard.
The command or macro is the action that will occur when the key
is pressed, pressed and held, or released. Separate multiple
commands or macros with a semi-colon ( ; ), or place them on
separate lines.
7. Click OK.
2. In the Select key list, click the key you want to modify.
Removing a key
2. In the Select key list, click the key you want to remove.
Label
Modifiers
Key
The key list displays the keys listed in the Select key list in the Object
Keys and Display Keys dialog boxes. All object keys are displayed first
in the list, and then all display keys. The key list does not separate the
two types of keys because this distinction does not matter to
operators—they only need to know what action will occur when they
press a key.
The key list is displayed. It lists keys associated with this object and
all keys associated with this display.
This rule does not apply to visibility, fill or color animation: for objects
with these kinds of animation, animation of the individual objects takes
precedence over animation of the group.
To apply animation to objects within groups, use the group edit feature.
For details about editing grouped objects, see page 16-29.
1. Click an object.
1. Click an object.
When the Animation dialog box opens, see which items have a
check mark.
4. Click Apply.
In the same display, drag the object and then press Ctrl and
drop the object.
1. Click the object that has the animation you want to copy.
3. Select the object(s) that you want to copy the animation to.
Setting up trends
This chapter describes trends, and outlines how to:
You can:
plot data over time, or plot one tag against another in an x-y plot
chart to show the relationship between the two tags.
y-axis legend
Pen without a
pen marker
x-axis
x-axis legend
Scrolling
mechanism
Chart
The chart is bounded by the y-axis on the left and the x-axis on the
bottom. The chart contains the plotted trend data, shown using pen
lines and pen markers, as well as grid lines.
The chart title is the name you give to the trend chart. Naming the
trend is optional.
x-axis
The x-axis is the bottom horizontal edge of the chart. It is also known
as the horizontal axis or time axis.
x-axis legend
For standard charts, the x-axis legend indicates the time span covered
by the trend. For XY Plot charts, the x-axis legend shows the scale, or
range, of values from a pen you select.
You can set up the trend to omit the x-axis legend. The number of
timestamps or values shown depends on the size of the trend object
and the number of vertical grid lines.
The x-axis legend can also be used at run time to open the X-Axis tab.
For details about setting this up, see “To open the X-Axis tab” on
page 19-66.
y-axis
The y-axis is the left vertical edge of the chart. It is also known as the
vertical axis.
y-axis legend
The y-axis legend shows the scale, or range, of values for the pens. You
can set up the trend to omit the y-axis legend.
determined automatically (using the best fit for the current data).
constant values.
controlled by tags.
You can set up the trend so that all pens use the same scale, or so that
each pen has its own scale on the y-axis. When the operator clicks a pen
in the line legend, the vertical axis shows the selected pen’s scale.
The y-axis legend can also be used at run time to open the Y-Axis tab
or to pan data. For details about setting this up, see “To open the Y-
Axis tab” on page 19-66 For more information about panning data at
run time, see “Using pan at run time” on page 19-71.
Pens
Pens are the lines or symbols used to represent values. Pens can be
different colors, widths, and symbols—called markers—so operators
can distinguish one pen from another easily.
For an example of how pen markers are used, see page 19-7. For a list
of pen markers, see page 19-34.
The pen values can be tags you are monitoring, expressions that
manipulate tag values, or constants.
x-axis legend
y-axis legend
line legend
The x-axis and y-axis legends are described earlier in this chapter.
The line legend shows the color, name, description, minimum value
and maximum values for each pen line shown on the trend chart.
The current value legend shows the pen icon, current pen value, and
current time for each pen line shown on the trend chart.
The position of the line legend determines where the current value
legend appears on the chart. When the position of the line legend is set
to Left, the line legend appears on the left side of the trend chart and
the current value legend appears on the right side. When the position
of the line legend is set to Bottom, the current value legend appears as
a column in the line legend. For more information about positioning
the line legend, see page 19-26.
Pen icons
Pen icons appear at the right edge of the chart. You can specify whether
or not pen icons are displayed on the trend chart. For more
information about showing or hiding pen icons, see page 19-25.
At run time, if a pen’s current value is within the scale shown on the
vertical axis, the icon is displayed. The icon’s position indicates the
pen’s most recently-recorded value, even if the trend is paused, or if the
most recent value has not yet been plotted.
You can use pen markers to show when data is sampled. For example,
when the trend is updated as the value changes, the pen marker
indicates when the trend is updated.
You can use pen markers as a means to reading pen values at run time.
Place the value bar on a pen marker, and the value bar shows the value
of the chart point indicated by the pen marker.
For information about setting up the trend using the Trend Properties
dialog box, see the topics starting on page 19-17.
You can position the value bar by clicking anywhere on the trend chart
at run time.
Standard Chart
A standard chart plots tag values against time.
Use the XY Plot chart to plot one tag’s values against another tag’s
values instead of plotting one tag’s values against time. For example,
you could plot the temperature of a tank against the pressure of the
tank.
The x-axis legend displays the scale for the x-axis pen. The time period
covered by the chart is at the upper left.
In this illustration each pen uses its own scale. You can use the same
scale for all pens. For information about setting up the pen scale, see
“Setting up the vertical scale for multiple pens” on page 19-49.
You can also specify these settings in the Properties tab of the Property
Panel. For details about using the Property Panel, see page 16-34.
You can change the color and style settings for the background using
the WindowStyle and WindowColor options in the Property Panel.
For information about using the Property Panel, see page 16-34.
2. Drag the mouse to create a box approximately the size you want
for the trend.
Once you have set up the trend, you can edit it as you would any other
graphic object. You can move it, resize it, attach animation to it, and so
on. You can also use this object in other graphic displays by dragging it
from one display and dropping it into another.
Display chart title Click the Display chart title check box, and then
type the title text (up to 80 characters). The chart title also displays the
current date at the top of the trend chart.
Data Server The data server determines where the data for the trend
is acquired. Select the type of data server to provide data to the trend:
Poll for Historical Data acquires the newest historical data from the
data server. Use this option to poll the data log at the rate specified
by the chart update mode. When you use this option, the trend
charts only historical data. For information about the chart update
mode, see page 19-19.
If you use Poll for Historical Data, the current value legend does not
display pen icons or pen values.
Standard Click Standard to plot each pen against time, with time on
the x-axis. Use a Standard plot type to measure a pen’s values against
time.
XY Plot This option is available only when one or more pens have
been set up in the Pens tab.
Click XY Plot to create a trend with a pen that serves as the x-axis. Use
an XY Plot chart to plot one pen’s values against another pen’s values.
X-Axis pen Select the pen for the x-axis in an xy plot. The y-axis pen
on the trend chart charts against the x-axis pen’s values.
The Manual option is reserved for use with the NewData method in
the TrendX object model, and is only available when the data server is
set to None.
The NewData method allows you to provide data to the trend chart
from sources other than RSView real-time and historical data
providers. For more information about the NewData method in the
TrendX object model, see Help.
Refresh Rate Type a number, and then click a time unit to determine
how often the trend updates data. The refresh rate range is 50
milliseconds to 596 hours.
While using Historical poll mode, the refresh rate controls how often
the data server is polled for data, and the refresh rate cannot be set to
a value lower than 1 second.
You can plot historical data from a data log model in the HMI server
you are running, or you can plot data from a different HMI server,
either on the same computer, or on another computer in the
application. For information about data log models, see Chapter 13,
Setting up data logging.
You can use the buffer to collect data for the trend when trend is not
visible on the graphic display. For information about charting data
Overlay pen
Currently-plotting pen
Currently-plotting pen
Overlay pen
24-hour format.
AM/PM format.
Data point connection Specify how data points on the trend are
connected:
Show only markers displays a marker for each data point. Lines do
not connect the data points.
Display milliseconds If you select the Standard chart style, select this
check box to display milliseconds in the time labels on the x-axis
legend. Click the Display scale check box on the X-Axis tab to display
time labels.
Display value bar To view details about a specific point in the trend,
use the value bar. At its position on the trend chart, the value bar
displays each pen’s value, date and time. For more information about
using the value bar at run time, see “Using the value bar at run time”
on page 19-68.
The chart border is always black. For information about setting the
background color for the other areas in the trend, see “Choosing trend
colors, fonts, lines, and markers” on page 19-13.
Text color Click the text color box, and then click a color in the
palette.
The labels on the vertical axis use the color of the selected pen. To
select a pen, click a pen in the line legend.
Font Click this button to change the type style of all text in the trend
chart.
The following illustration shows the current value legend to the right
of the trend:
Current time
Current pen value
Pen icon
Pen line color
The following illustration shows the current value legend as part of the
line legend, at the bottom of the trend:
Display time Select this check box to display the time when data was
last collected.
Display pen icons Select this check box to display the pen icons in the
current value legend. The pen icons show the current value of the pen.
When the chart is paused, the pen icon continues to chart the current
value of the pen, and therefore could be in a different position than the
end of the pen line in the chart.
Click Bottom to make the line legend and the current value legend
appear at the bottom of the chart.
Click Left to make the line legend appear to the left of the chart.
If there are more pens specified than you have specified to appear in
the line legend, the trend chart will plot all the pens, but the line legend
will only show the number of pens you have specified. To view the pens
that are not shown on the chart, use the scroll bar.
Long tag name displays the full path and tag name for each pen.
Allow scrolling Select this check box to allow the trend data to plot
on the trend chart.
If you clear this option, the trend chart is paused, and the data buffer
stores trend data until the buffer limit is reached. When the limit is
reached, the oldest data is discarded and replaced with the newest data.
While the trend is paused, the pen icons to the right of the trend chart
indicate pen values by pointing to the position of the pen value. For
information about displaying pen icons, see page 19-25.
The operator can turn off pause by clicking the pause button at run
time. When pause is turned off, the trend data that was held in the
buffer plots on the trend chart. For more information about the
scrolling mechanism, see page 19-67.
Continuous Scroll scrolls the chart from right to left as the trend
data is plotted.
Half Screen Scroll scrolls the chart half a screen at a time. The chart
scrolls from left to right. When the pens reach the right side of the
chart, the chart scrolls half a screen and the pens continue plotting
values starting in the center of the chart.
Full Screen Scroll scrolls the chart a full screen at a time. The chart
scrolls from left to right. When the pens reach the right side of the
chart, the entire chart scrolls and the pens continue plotting values,
starting at the left side of the chart.
Buffer for extra data The data buffer stores pen values that are not
within the time period or the value range of the trend chart at run time.
The operator can view these pen values by using the VCR-style
buttons to scroll through the data manually.
You can use the data buffer to collect data in the background when the
trend chart is not displayed in the graphic display. For more
information about collecting trend data in the background, see
page 19-64.
Type the number of data points to store for each pen. You can store a
maximum of 32,767 data points, or records, per pen.
To plot a tag value, click Tags, and then specify a tag name in
the Tag Browser.
To plot a constant value-such as a tag’s alarm level-type a value
in the Expression box.
To define an expression, use the buttons in the Expression
Editor.
1. In the Pens tab, click Add Pen(s) from Model to open the
Configure Tags dialog box.
If there is no area to select, you have not set up a data log model for
this application. Click Cancel to return to the Pens tab.
3. In the model list, specify a data log model. The data log model tags
are listed in the box.
4. Click the tag you want to add to the trend as a pen, and then click
Add. To add all of the tags in the model, click Add all.
Click the first tag you want to select, press and hold down the
Shift key, and then click the last tag you want to select.
Click, and then drag the mouse across the tags you want to
select.
To select tags that are not consecutive, click the first tag you
want to select, press and hold down the Ctrl key, and then click
each tag you want to select.
5. The tags that will be added to the trend are listed in the Tags to
monitor box.
6. If you made a mistake and do not want to add one of the tags listed
in the tags to monitor box, click the tag, and then click Remove.
7. To remove all of the tags from the Tags to Monitor box, click
Remove All.
8. When the Tags to monitor box lists the tags you want to add to the
trend, click OK.
Click the first pen you want to select, press and hold down the
Shift key, and then click the last pen you want to select.
Click, and then drag the mouse across the pens you want to
select.
To select pens that are not consecutive, click the first pen you
want to select, press and hold down the Ctrl key, and then click
each pen you want to select.
Pen Number This column identifies the number of the pen. Up to 100
pens can be added to a trend. To select a pen, click the pen number.
Model Click the browse button to select a data log model for a pen.
Tags and expressions must be set up in the data log model you select.
For information about data log models, see Chapter 13, Setting up data
logging.
Color Select a color to identify this pen on the trend chart. Click the
color column, and then click a color in the palette. Do not choose the
same color as the background of the trend object.
Visible By default, all pens in a trend are visible. However, too many
pens on one display can be difficult to read.
Click the cell to switch the Visible setting to On or Off. When Visible
is set to Off, the pen is not displayed in the chart.
Width The pen width affects the thickness of the pen line and the
markers.
Click the cell, and then specify a pen width from the drop-down list
box. If you specify a width other than 1 pixel, you cannot change the
line style setting.
Type Click the cell, and then specify how the trend line is plotted on
the chart:
This item Does this
Digital Draws a line along the time axis as the first value, then, when
the value changes, draws a vertical line to the second value.
For example:
Full Width Draws a tag’s most recent value horizontally across the
width of the trend.
For example, if the most recent value for a tag is 75, draws
a horizontal line across the trend at 75. When the value
changes, redraws the line at the new value.
You can use full width to display values that act as high and
low set points.
Style Click this cell, and then specify a line style. You can select from
one of five styles, shown below.
Dash
Dot
Dash-Dot
Dash-Dot-Dot
Marker Select a marker from the symbols in the list. If you use the
Show only markers option, specified in the Display tab, only pens for
which you specify a marker are displayed in the trend.
The marker appears at each data point. You can select from none,
boxed, up triangle, down triangle, letters, characters, or the line number
of the pen.
Name Marker
Boxed
Up triangle
Down triangle
If a pen displays new data frequently, for example every few seconds,
the markers might appear to form a solid line.
Min/Max The Min and Max tag values are specified in the HMI
server’s tag editor and are automatically entered in these columns.
The tag’s minimum and maximum values are used to determine a pen’s
scale. When an operator clicks a pen in the line legend, the y-axis legend
re-scales to fit the selected pen’s minimum and maximum values. Tag
values outside the minimum and maximum scale do not appear on the
trend chart.
You can also specify a pen scale on the Y-Axis tab. For more
information about setting minimum and maximum value options on
the Y-Axis tab, see page 19-46.
Eng. Units Select this check box, and then type the name of the
engineering unit that the pen represents. For example, rpm, gallons, fps,
or degrees. The engineering units are displayed as part of the line
legend.
Description If the tag you have added to the trend already has a
description, the description appears in this cell. To remove the
description, click the cell, and then press the Backspace key.
Lower Bound The lower bound setting determines when shading will
occur between the pen for which you are setting up the pen attributes,
and the pen you select as the lower bound pen.
Click this cell and specify the lower bound pen in the list. At run time,
the area between the two pens is shaded when the pen you have set up
on the Pens tab crosses the lower bound pen on the trend chart. For
information about using shading to compare pen values, see
page 19-38.
Upper Bound The upper bound setting determines when shading will
occur between the pen for which you are setting up the pen attributes,
and the pen you select as the upper bound pen.
Click this cell and specify the upper bound pen in the list. At run time,
the area between the two pens is shaded when the pen you have set up
on the Pens tab crosses the upper bound pen on the trend chart. For
information about using shading to compare pen values, see
page 19-38.
Link Data Select this check box to update the tag’s minimum,
maximum, description, and engineering units properties at run time.
This allows you to make changes to the trend properties at any time and
have them updated at run time. Link data also updates the tag
properties if the properties were changed in the HMI server’s tag
editor.
If the tag’s minimum and maximum values are not available, three
question marks (???) appear in the columns.
For digital tags, 0 is used for the minimum, and 1 is used for the
maximum. For analog tags, specify the minimum and maximum values
in the HMI server’s tag editor.
Click the first pen you want to select, press and hold down the
Shift key, and then click the last pen you want to select.
Click, and then drag the mouse across the numbers of the pens
you want to select.
To select pens that are not consecutive, click the first pen you
want to select, press and hold down the Ctrl key, and then click
each pen you want to select.
2. In the Multiple Pen Edits spreadsheet, specify the new attributes
for the pens.
If you make a mistake and want to correct the changes you have
made, click Clear Selections to empty the Multiple Pen Edits
spreadsheet.
3. When you are satisfied with your changes, click Apply to Selected
Pens.
Use horizontal lines to provide an orientation for your tag data. For
example, if you define values that are the limits within which a tag
should operate, and display horizontal lines in your trend to indicate the
limits, when a tag crosses one of these limits the tag’s alarm condition
is obvious on the trend. Both pens must use the same minimum and
maximum values.
There are two ways to plot a value so that it appears as a horizontal line
across the full width of the chart:
When values for the pen have been plotted across the full width of
the chart, the pen appears as a solid horizontal line.
In the Pens tab, add a pen with a tag or expression that will
determine the position of the pen line. In the Type column of the
Pen Attributes spreadsheet , choose Full Width.
For example, you can set up Pen 1 to show a tag’s value and Pen 2 to
show a constant value that is an alarm threshold. When Pen 2 is the
upper boundary for Pen 1, the shading will highlight where the tag’s
Set up shading in the Pens tab in the Trend Properties Dialog box.
The trend below calls attention to tag values in alarm. The difference
between the tag’s value and the tag’s alarm level is shaded.
Upper-bound pen
Lower-bound pen
Pen 1
Pen 2
Pen 3
To produce the shading shown above, the following settings were used:
Shading
Tag name or
Pen Constant value Upper Bound Lower Bound
Pen 1
Color 1
Pen 2
To produce the shading shown above, the following settings were used:
Shading
Tag name or
Pen Constant value Upper Bound Lower Bound
Pen 1
Color 1
Pen 2
To produce the shading shown above, the following settings were used:
Shading
Tag name or
Pen Constant value Upper Bound Lower Bound
Start date and Start time When Allow scrolling is selected in the
Display tab, the start date and time are disabled. To change the start
date or time, clear the Allow scrolling check box.
Specify the starting date and time for the trend. To select a date, click
the Start date list, and then click a date on the calendar.
The Start date and Start time settings determine when the trend begins
to collect and chart data. The start time is shown on the left side of the
x-axis. As the chart scrolls with new data, the time is updated on the
horizontal axis label.
If the trend is plotting current values only and it is first displayed after
the specified time, the current time is used as the starting point.
Time span Type a number, and then select a time unit, to determine
the time span of data the trend displays at run time.
For a Standard chart, the time span defines the horizontal scale. For an
XY Plot chart, the minimum and maximum values of the selected pen
(specified in the Pens tab) define the horizontal scale, and the time span
defines the number of data points plotted.
Display scale Select this check box to display the x-axis legend at the
bottom of the trend.
For a standard chart, the legend shows the start and end times of the
pen values currently charted in the trend. If there is room, intermediate
times are shown below each vertical grid line.
For an xy plot chart, the legend shows the minimum and maximum
values of the pen selected for the x-axis. If there is room, intermediate
values are shown as well.
Display date on scale Select this check box to display the date of
each time stamp.
Major grid lines/Minor grid lines Type the number of major and
minor lines that will appear on the trend chart. You can display up to
30 major lines, and up to 10 minor lines between each major line. The
major lines are solid, and the minor lines are dashed.
Grid color If grid lines are displayed on the chart, you can change their
color. Click the grid color box, and then click a color in the palette. The
grid line color will change to the color you have selected.
Use the Y-Axis tab to specify which scale of pen values you use for the
trend chart. The scale of values can be the same for all pens, different
for all pens, or a percentage of the pen values.
To use the same scale for all pens, use the All pens on same scale or
Scale using pen options. For details, see “Setting up the vertical scale
for multiple pens” on page 19-49.
To use a different scale for each pen, use the option, Each pen on
independent scale. For details, see “Setting up the vertical scale for
multiple pens” on page 19-49. When you use a different scale for each
pen, the minimum and maximum values on the y-axis legend change to
reflect the scale of the selected pen.
Click Preset to make the minimum and maximum pen values you
set up in the Pens tab serve as the y-axis scale. The scale does not
change.
The Scale options on the Y-Axis tab specify which pen’s minimum
and maximum values are used as the Preset values. For more
4. Click Apply.
5. Click Apply.
If you select isolated graphing, you cannot display horizontal grid lines.
Instead, a horizontal line appears above each band. For more
information about isolated graphing, see page 19-12.
Type a number between 0 and 10 for the percentage of the chart height
that separates each pen in the trend. A 0% isolation will display the pen
bands closely together, and a 10% isolation will display the pen bands
farther apart.
Display scale Select this check box to display the y-axis legend to the
left of the trend.
Major grid lines/Minor grid lines Type the number of major and
minor lines that will appear on the trend chart. You can display up to
30 major lines, and up to 10 minor lines between each major line. The
major lines are solid, and the minor lines are dashed.
Grid color If grid lines are displayed on the chart, you can change their
color. Click the Grid color box, and then click a color in the palette.
If you select isolated graphing, the grid color is used for the horizontal
lines between bands.
All pens on same scale Click All pens on same scale to use one scale
for all pens. The lowest minimum value from all the pens and the
highest maximum value from all the pens makes up the pen scale.
Scale using pen You must add at least one pen to the trend to use this
option.
Click Scale using pen to use the same scale for all pens and then select
a pen from the list. The pen scale is based on the minimum and
maximum values for the specified pen.
Scale as percentage Select this check box to display the y-axis values
as a percentage of the minimum and maximum scale. The y-axis legend
displays the percentage scale, from 0 to 100%. For example, you could
have a tank with a minimum value of 0 gallons and a maximum value
of 5237.50 gallons. By using Scale as percentage, the trend chart would
show the tank as 50% full instead of a value of 2618.75 gallons.
delete snapshots.
The Overlay options can be changed at run time. The run-time options
allow the operator to align, relocate, show, hide, and set up overlays. For
Before you can add a snapshot to a trend and set it up as an overlay, you
must first create a snapshot.
To create a snapshot
3. Right-click the trend to open the context menu, and then click
Create Snapshot.
Operators can show or hide overlays on the trend chart using the
context menu at run time. You can set up run-time options in the
Runtime tab. For information about setting up the trend’s run-time
options, see page 19-60.
To remove an overlay
To delete a snapshot
You can change the attributes of pens used in overlays in the same way
as the attributes of regular pens. For details about setting up pen
attributes, see page 19-32.
Setting up overlays
For information about changing the overlay at run time, see
page 19-72.
Click Position to align the earliest data in the snapshot with the run-
time chart, based on a percentage you set in the Offset (%) column.
Click Time to start the snapshot at the time you specify in the Start
column.
The overlay data in the snapshot scrolls with the data in the run-
time chart, based on the chart’s refresh rate. For information about
setting up the refresh rate, see page 19-19.
If you pan or zoom the data in the chart, the overlay data held in the
snapshot also pans or zooms.
Start This cell is available when you anchor the overlay by time. It is
not available if you anchor the overlay by position.
The default start time is the time at the left-most side of the chart.
Double-click this cell to open the Start Time dialog box. Use the Start
Time dialog box to set up a start time. For information about the
options on the Start Time dialog box, see Help.
Offset (%) This cell is available when you anchor the overlay by
position. It is not available if you anchor the overlay by time.
Type a percentage to define how far from the left edge of a run-time
chart an overlay is anchored. The percentage is in terms of the total
width of the chart.
To anchor the overlay at the left edge of the run-time chart, set the
offset to 0.
Click the cell to switch the Visible setting to On or Off. To display the
overlay when the chart opens at run time, set Visible to On. When
Visible is set to Off, the Overlay does not appear on the trend chart.
To show or hide a pen in the overlay, use the Visible option in the Pens
tab. For details, see page 19-33.
At run time, operators can show or hide each overlay using the context
menu. You can set run-time settings to allow an operator to show or
hide overlays at run time. For information about setting up run-time
settings, see page 19-60.
First Pen/Last Pen Use the First Pen/Last Pen option to determine
which pens in the Pens tab correspond with the pens in the snapshot.
When you add a snapshot to a trend, all of the pens in the snapshot are
added to the Pen Attributes spreadsheet in the Pens tab. The numbers
in the first pen and last pen columns identify the first and last pens in
the snapshot and correspond with the pen numbers in the Pens tab.
You can change pen attributes for snapshot pens in the Pens tab. For
information about using the Pen Attributes spreadsheet, see
page 19-32.
When you have created and saved your template, load the template into
each RSView Studio application’s trend chart.
Create a trend template to save pen attribute data. You can add a
number of new pens at run time, create a template, and then save pen
attribute data with the template. You can then close the trend graphic
display, reopen it later, and instead of having to add each pen again, you
can load the template. When you load the template, the pen attribute
data will also be loaded.
1. Use the General, Display, Pens, X-Axis, and Y-Axis tabs to set up
the display options and pen attributes you want to capture in a
template.
To set up options in this tab See page
2. In the template tab, click the display options you want to apply to a
trend chart when the template is loaded.
On the left side of the options box, the trend tabs are listed. Click a
tab to select it.
On the right side of the options box, the tab options that can be
included in a trend template are listed. Click the option to check or
1. In the Trend Properties dialog box, click the Template tab, and
then click Load template.
Deleting a template
1. In the Trend Properties dialog box, click the Template tab, and
then click Delete template.
For example, to prevent operators from adding pens to the chart at run
time, clear the Pens tab check box.
The Display Property option for at least one of the above tabs must be
checked to allow editing legend properties.
Allow Show/Hide value bar Select this check box to allow operators
to use the context menu to show and hide the value bar. This option
will allow operators to show the value bar even if you have cleared the
value bar check box in the Display tab. For information about setting
up options on the Display tab, see page 19-22.
Allow print Select this check box to allow operators to print the trend
chart.
Allow Delta value bar Select this check box to allow operators to use
the Delta value bar. For information about using the Delta value bar at
run time, see page 19-69.
The graphic library files are displayed below the Libraries Folder.
4. Drag and drop one or more trend buttons, or the trend chart into
your display.
X On the View menu, click Test Display or Edit Display, or click the
Test Display or Edit Display buttons on the toolbar.
Real-time trends collect data only while the trend is displayed. This
means that a trend will not contain any data when the graphic display
opens. This can be a problem if the trend chart is not open for the
whole time the application is running, or if other graphic displays are
opened before the trend display.
If you want the trend to contain data when the graphic display is
opened, you can either use a data log model, or you can create a startup
macro that loads and updates the display in the background. This loads
data into the data buffer for the trend.
2. When you want the real-time trend to become visible, issue the
following command:
Display Trend1
Trend1 will appear in the graphic display and will contain data.
Selecting pens
To display details about a pen, select the pen by clicking it in the line
legend. When the pen is selected, the vertical scale changes to reflect
the scale of values for the pen.
The Trend Properties dialog box opens. The dialog box shows only
the tabs for which check boxes are selected in the Runtime tab. The
Runtime tab is not accessible at run time.
The graph title window allows you to change the name of the trend
chart at run time.
1. In the trend chart display at run time, double-click the trend title.
The Graph title dialog box opens.
2. Type a name for the trend chart, and then click OK.
2. Change the settings for the Y-Axis tab, and then click OK.
For information about the options on the Y-Axis tab, see “Setting up
the vertical axis (y-axis)” on page 19-45.
2. Change the settings for the X-Axis tab, and then click OK.
For information about the options on the X-Axis tab, see “Setting up
the horizontal axis (x-axis)” on page 19-43.
1. In the trend chart display at run time, double-click the line legend.
The Pens tab opens.
2. Change the settings for the Pens tab, and then click OK.
For information about the options on the Pens tab, see “Adding pens
to the trend” on page 19-29.
A set of VCR-style buttons are included with the trend. These buttons
allow the operator to view different areas of charted data. To show the
VCR-style buttons at run time, in the Display tab, click Display
scrolling mechanism.
To show the value bar, click the trend where you want the value bar to
appear.
1. At run time, right-click the trend chart to open the context menu,
point to Active value bar, and then click Value.
2. Click the trend where you want the value bar to appear.
4. Click the trend where you want to see the difference between the
value at the Value bar’s data point and the value at the Delta Value
bar’s data point.
2. Click the trend chart at the position on the trend where you want
to know the difference between the value indicated by the Value
bar and the value indicated by the Delta value bar.
1. Right-click the trend to open the context menu, and then click
Show value bar.
2. Both the value bar and the delta value bar are removed from the
trend.
3. Open the context menu, and then click Show value bar again. The
value bar reappears but the delta value bar does not.
Left-click and drag the chart to zoom into the selected area.
X At run time, right-click the chart, and then select Undo Zoom/Pan.
X At run time, right-click the trend chart, point to Overlays, and then
click Properties.
If data for the trend is not available at run time due to communication
errors, a message is sent to the Diagnostics List. For information about
setting up FactoryTalk Diagnostics, see Chapter 12, Logging system
activity.
X In RSView Studio, click the Tools menu, and then click Diagnostics
Viewer.
Creating expressions
This chapter includes
About expressions
Sometimes the data you gather from devices is only meaningful when
you:
Expression components
Expressions can be built from:
tag values.
tag placeholders.
constants.
built-in functions.
if–then–else logic.
Derived Tags: You can define an expression and then specify the
name of a tag that will store the result of the expression.
Data Log Setup: When setting up file management, you can choose
to have a log file created when a particular event occurs. One way
of doing this is to create an expression.
Creating expressions
All editors that can use expressions include an Expression box. In some
editors, you will also find:
expression buttons.
an expression column.
Expression box
Expression buttons
Expression column
Expression buttons
These are the expression buttons:
This button Displays a list of This button Displays a list of
Arithmetic operators
When you are working in a window, you can use the commands on the
Edit menu, the toolbar, or the keyboard. When you are working in a
dialog box, you can use only the keyboard because you cannot access
the menu bar or toolbar.
You can paste into the Expression box in the form or into the
Expression column in the spreadsheet.
2. Press Ctrl-V.
Formatting expressions
You can format expressions so they are easier to read. However, do not
let tag names, key words, function names, or function arguments span
more than one line.
When formatting expressions, you can use tabs, line returns, and
multiple spaces.
If (tag1>tag2) Then 0
Else If (tag1>tag3) Then 2
Else 4
Click the Tags button and then select a tag from the Tag Browser.
Enclose tag names that contain dashes or start with a number in braces
{} when you use them in an expression. This distinguishes the
characters in the tag name from the characters in the expression. Also
use braces when using wildcards (* or ?) to represent multiple tags in
an expression.
For detailed information about tags, see Chapter 8, Working with tags.
You can use tag placeholders in the same way you use tag names. A tag
placeholder is the cross-hatch character (#) followed by a number from
1 to 500. For detailed information about placeholders, see Chapter 16,
Creating graphic displays.
Constants
A constant can have any of the following formats:
integer (123).
the string ‘pi’ (to represent the symbol π). RSView replaces the
string with its numeric value.
+ addition tag1+tag2
returns a value of 12
– subtraction tag1–tag2
returns a value of –2
* multiplication tag1*tag2
returns a value of 35
/ division tag1/tag2
returns a value of 0.7142857
MOD, % modulus tag2 MOD tag1
(remainder) returns a value of 2
IMPORTANT Be sure that any tag value you use as a divisor cannot at
some point have a value of zero. Expressions that
attempt to divide a number by zero produce an error at
run time.
Relational operators
Relational operators compare two numeric or string values to provide
a true or false result. If the statement is true, a value of 1 is returned. If
false, 0 is returned.
Example
(For these examples,
Symbols Operator Action tag1=5 and tag2=7)
AND, && and Returns a 1 if the statements to the (tag1<tag2) AND (tag1==5)
right and to the left of the operator both statements are true; returns a 1
are both true.
OR, || or Returns a 1 if either or both (tag1>tag2) OR (tag1==5)
statements are true. tag1==5 is true; returns a 1
NOT negation Reverses the logical value of the NOT (tag1<tag2)
statement it operates on. although tag1<tag2 is true, NOT
reverses the logical value; returns a 0
Bitwise operators
Bitwise operators examine and manipulate individual bits within a
value.
IMPORTANT These operators are for integers only, not floating point
numbers.
Shifts the bits within the left operand by the amount specified in
the right operand. The bit on the right disappears.
Shifts the bits within the left operand by the amount specified in
the right operand. The bit on the left disappears and 0 always
shifts in on the right.
~ complement Returns one’s complement; that is, toggles the bits within an
integer or tag.
tag1&tag2
Returns 0 (binary 0000 0000 0000 0000)
tag1|tag2
Returns 7 (binary 0000 0000 0000 0111)
tag1^tag2
Returns 7 (binary 0000 0000 0000 0111)
tag1>>1
Returns 2 (binary 0000 0000 0000 0010)
tag1<<1
Returns 10 (binary 0000 0000 0000 1010)
~tag1
Returns –6 (binary 1111 1111 1111 1010)
Built-in functions
tag
time
file
math
user
Many functions check for specific true and false conditions. They
return 1 if the condition is true, and 0 if the condition is false.
Returns 1 (true) if one or more tags in the specified folder have a name
beginning with the letters “pv” and are in alarm. Returns 0 (false) if
none of the specified tags are in alarm.
Time functions
The following built-in functions examine system time. These functions
use the time or interval parameters.
month [Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep,
Oct, Nov, or Dec]
date [1 to 31]
It does not matter in what order options are listed. You can include any
or all of these options; the more you include, the more specific the time
becomes.
The following all represent the same date and time, and are valid time
parameters:
“17:00”
means any day at 5:00 PM
“ :30 ”
means any hour, on the half hour
“ mon 17:”
means 5:00 PM each Monday
<number> <units>
mil (millisecond)
sec (second)
min (minute)
hou (hour)
day (day)
wee (week)
mon (month)
yea (year)
_____________________________
_____________________________
BEFORE_TIME(“aug 20 2000”)
_____________________________
INTERVAL(“1 min”)
_____________________________
The file parameter is the path name, surrounded by quotes. The drive
parameter is the drive letter.
Math functions
These functions perform math on an expression:
This function Returns this value
Security functions
These functions return information about users.
This function Returns this value Example
when two operators have equal precedence, they are evaluated from
left to right
1 (highest) ()
2 NOT
~
3 *
/
MOD, %
**
AND, &&
&
>>
<<
4 +
–
OR, ||
|
^
5 (lowest) EQ, =
NE, <>
LT, <
GT, >
LE, <=
GE, >=
_____________________________
1. tag1>tag2=0
2. tag1<tag3=1
3. 0 AND 1=0
_____________________________
2. tag1>1=1
_____________________________
1. NOT tag1=0
2. 0 AND tag2=0
3. tag3 ** 2=100
4. 0>100=0
If–then–else
enter
true
statement
false
value2 value1
exit
enter
true
statement1
false
true
statement2
false
exit
if (statement1) then
if (statement2) then (value1)
else (value2)
else (value3)
enter
false false
value3 value2
exit
Creating
embedded variables
This chapter describes:
For example, you could embed a tag value and the time variable in a
local message. At run time when the local message is displayed, it is
updated to reflect the tag’s current value as the value changes. The time
is also updated as the time changes.
string tags.
the time.
the date.
Embedded variables are case sensitive, and must use the proper syntax
to work. Otherwise, the embedded variable is treated as a piece of text.
Therefore, we do not recommend creating and editing embedded
2. Click the tab containing the Caption box (the General tab or the
States tab, depending on the type of object).
5. Fill in the options in the dialog box that opens, as described in the
following sections.
1. In the Local Messages editor, right click the Message column, and
then click Edit String.
4. Fill in the options in the dialog box that opens, as described in the
following sections.
To open the Tag Browser and select a tag, click the Browse button.
Fill left with Select a character to fill the left of the display with if
the value at the data source contains fewer than the maximum
number of digits. If you don’t want to use a fill character, select
None.
3. Click OK.
where
Tag_name is the tag to display; you can also type a tag placeholder
here.
To open the Tag Browser and select a tag, click the Browse button.
Browse button Fixed number of characters Select this check box if you want the
variable always to display the same number of characters, and then
select the number of characters to be displayed, up to 255.
3. Click OK.
/*S:# Tag_name*/
where
Tag_name is the tag to display; you can also type a tag placeholder
here.
/*S:20 Blower_status*/
3. Click OK.
/*Time_date_format*/
where
SD Short date
LD Long date
SDT Short date and time
LDT Long date and time
T Time
TSD Time and short date
TLD Time and long date
To display the time followed by the short date, you would type this:
/*TSD*/
A space is placed between the time and date when the embedded
variable is displayed at run time.
3. Click OK.
If the tag value, including the decimal point and minus sign, contains
more digits than specified for the variable, the numeric variable is
replaced with asterisks (*).
The numeric variable uses the number format you set up on the run-
time computer. For example, if the run-time computer is set up to use
a comma for the decimal symbol, the numeric variable uses a comma
for the decimal symbol.
Null characters have a hex value of 0. The null character indicates the
end of string input. It does not add to the actual string length.
For embedded variables that show both the time and the date, a space
is placed between the time and date when the embedded variable is
displayed at run time.
Time and date embedded variables use the time and date formats you
set up on the run-time computer. For example, if you specify the short
date format, at run time the display uses the short date format that the
run-time computer uses.
Creating macros
A macro is a series of commands stored in a macro component. The
name of the macro component is then used like a command, and can
be used anywhere a command can be used. When the component name
is entered, the macro runs, executing all the commands in the
component.
You can create macros to perform almost any action. For example, a
macro can:
Creating macros
To create a macro
To replace a tag name with its current value when the macro or
command is evaluated, enclose the tag name in dollar signs ($)
to create a placeholder in the command. When a macro
containing $tag$ runs, the tag values are substituted first.
To indicate a percent in a macro, use two percent signs (%%)
because a single percent sign indicates a parameter.
For information about parameters, see “Using parameters” on
page 22-4. For information about command syntax, see “How to
use commands” on page A-1.
At run time, operators can run a macro anywhere they can run an
RSView command. Ensure you include a way for operators to run
commands or macros, for example by specifying them as press actions
for buttons.
Display /Ingredients::Overview
Display /Ingredients::Detail
/Ingredients::Valve23=Open
When the macro called Factory runs, the graphic display called
Overview appears, then the graphic display Detail appears, then the tag
Valve23 is set to its open state. All are in the area called Ingredients.
Display /$Tag1$::Process1
Display /$Tag1$::TrendDisplay$Tag2$
Valve23=Open
The graphic display Process1 in the Mixing area appears, then the
graphic display TrendDisplay2 appears, also from the area called
Mixing, and finally, the tag Valve23 in the home area is set to its open
You don’t need to put braces around tag names when using
placeholders in commands.
Using parameters
To run the macro and parameters, specify the macro name followed by
the parameters. Separate multiple parameters with spaces.
For example, here is the same Factory macro with two parameters:
Display Overview
Display %1
Valve23=%2
“Factory Display” %1
Nesting macros
You can insert a macro within another macro—this is called nesting.
You can have eight nesting levels in macros.
Display Overview
Display Detail
Draw
Valve23=Open
Setting up navigation
An important part of the complete operator interface is the way
operators navigate through, and interact with, your application.
RSView gives you the tools for linking displays and creating an overall
application structure that is easy for operators to use.
process-specific displays.
Main Menu
Graphic Display
The display type you choose gives you additional control over how the
operator navigates between displays. For example, use the On Top
option to keep a display on top at all times, even when another display
has focus. Or use the Replace option if you want a display to replace all
other open displays when it opens. For details about assigning display
type see “Specifying the display type” on page 16-60.
You can reduce the time required to display a graphic by loading the
graphic into the display cache. You can
load the graphic when it is displayed for the first time by using the
Cache After Displaying option in the Display Settings dialog box of
the Graphic displays editor. For details, see “Specifying caching” on
page 16-62.
a macro.
Object key and display key animation are set up in the Graphic displays
editor. For details, see Chapter 18, Animating graphic objects. Client keys
To create the buttons, the designer used the Button drawing tool in the
Graphic displays editor. The buttons can be selected with a mouse or
with a touch screen. For details about how to create buttons, see
page 17-37.
Keys with repeat actions are ideal for such tasks as `ramping’ a tag’s
value.
When deciding what type of key to create, use the following table as a
guide:
You can assign a single key to one or more of the three types of key
definitions—object, display, or client. For example, the F2 key can
open a valve when the valve object has input focus, or it can close a
popup display that has focus, or the F2 key can be a client key that
opens a graphic display containing an overview of your process.
When a graphic display is active and an object has input focus, object
keys have precedence over display keys and client keys.
When you design your system, pay particular attention to the keys used
by embedded objects. Object keys and display keys have precedence
over keys used by embedded objects (for example, ActiveX, or OLE
objects), except for OLE objects that are not part of RSView (for
example, an Excel worksheet), whose keys have precedence over object
or display keys. For details, see the pages that follow.
At run time, if a graphic display has focus and a press, release, or repeat
action has been defined for the F1 key, F1 acts as a display, object, or
client key instead of launching Help.
For example, you might have an ActiveX slider object to control the
speed of a motor, with the F2 key defined to increase the motor’s
speed, and the F3 key defined to decrease the motor’s speed. If you
have defined F2 as an object key to jog the motor’s position, pressing
F2 will never increase the motor’s speed—every time an operator
presses F2, the motor’s position will be jogged instead.
+ on the numeric keypad Displays the Recipe dialog box, or saves the
recipe if Ctrl-W was pressed previously, or
restores the Recipe if Ctrl-R was pressed
previously.
Enter If Enter is pressed when a button has focus,
the button’s press and release actions are
executed.
If you define a press, release, or repeat action for a reserved key, to use
the key as an object or display key, the object or display key function
takes precedence, and the default, reserved function of that key is
disabled.
If you use a reserved key or key combination as a client key, the key will
perform both the actions of the client key you defined, as well as the
action of the reserved key. Because the results can be unpredictable,
defining client key actions for reserved keys is not recommended.
3. Click Add.
Some keys are reserved for use by Windows and RSView. Reserved
keys do not appear in the Key field in the Add Key dialog box.
5. Click OK.
The key you add is displayed in the Key field. If you specified a
modifier, the first letter of that modifier is also displayed. If you
create a label in the next step, it will also be listed in this field. As
you continue to add keys, they will be listed here.
6. In the Label field, if you want, type a label for the key.
The command or macro is the action that will occur when the key
is pressed or released. You can type multiple commands or macros.
If you do, separate them with a semi-colon (;) or type them on
separate lines.
8. If you want an action to repeat while the key is held down, type the
RSView command or macro name in the Repeat Action field.
Key /R
Using the
SE Client object model
and display code
Use the RSView SE Client object model with Visual Basic for
Applications (VBA) code in graphic displays to customize and extend
the capabilities of the RSView SE Client. Some ways you might do this
include:
Creating custom forms for operators You can use VBA to create
custom forms, for example as pop-up dialog boxes that operators can
interact with at run time. You can also use VBA logic to validate the
operator’s input, for example to ensure that the value an operator
enters in a numeric input field falls within 10% of the value of another
numeric input field.
This chapter provides a brief description of the IDE but does not
include detailed information about VBA —it is assumed that you are
familiar with the VBA environment and Visual Basic programming
language. This chapter highlights aspects of VBA that are unique to
RSView Studio, and describes how to use VBA from within RSView
graphic displays.
1. Open the graphic display for which you want to write VBA code.
In the Graphic Displays editor, click the View menu, and then
click Visual Basic Editor.
Project Explorer
window
Properties
window
Procedure or
Code window
You can create additional VBA modules and user forms. To use the
procedures in these modules and to use the user forms, you must call
them from procedures that exist in the module called ThisDisplay.
Properties Window
This window lists the property settings for the code modules, class
modules, and the VBA user forms and the objects on those forms. You
cannot call forms directly from RSView. To use a form, call the form
from a procedure in the code module called ThisDisplay.
This window is where you write and edit your VBA procedures. In
ThisDisplay, any RSView SE Client objects that raise events are listed
in the drop-down list on the left-hand side of the window. When an
object is selected in the left-hand list, the object’s events are listed in the
right-hand drop-down list.
For details about creating graphic displays, see Chapter 16, Creating
graphic displays.
About procedures
A procedure is a named block of code that executes as a unit. Examples
of procedures are Visual Basic subroutines and functions. The module
called ThisDisplay contains any number of procedures that are
executed in response to a display’s events.
The procedures you create in the module called ThisDisplay can call
procedures in other user forms or modules.
VBA can interact with the following objects in the RSView SE Client
Object Model:
Scale Represents the RSView scale object. Use this object with bar
graphs.
Tag Represents the FactoryTalk tag object. Use the Tag object to
provide runtime information for a tag, or to set the value of a tag.
press F2
To view the global object variables, click DisplayClient in the first list.
Help topics for VBA code and the RSView SE Client Object Model
open in a separate window, on top of the RSView Help window.
To return to the RSView Help window, close the SE Client Object
Model Help window.
Click the Help menu, and then click Microsoft Visual Basic Help.
VBA documentation
If you’re new to Visual Basic, you might want to look at the following
Microsoft publications:
Setting up redundancy
A redundant system is a back-up system that duplicates the function of
a device. This means that redundant components are alternate
components that can be used when primary components fail. For HMI
systems, redundancy provides a means of ensuring system availability.
When the primary server becomes available again, the system can
automatically switch back to it.
This backup mode that runs on the secondary server does not detect
alarms; it only keeps alarm states synchronized.
When the system fails over to the secondary server, alarm monitoring
starts automatically on the secondary server if it was running on the
primary server. When the system fails back to the primary server, alarm
monitoring automatically starts on the primary server and stops on the
secondary server, if it was running on the secondary server.
For alarm states to synchronize properly, the clocks on the primary and
secondary RSView SE Servers must be kept synchronized to a time
server. If the clocks on the computers are not synchronized, multiple
alarms or inconsistent information could be displayed in an alarm
summary when failover occurs.
When the primary server is active, the secondary server is loaded and
the project is loaded. However, components such as event detection,
alarm monitoring, and data logging do not have to be running unless
the secondary computer becomes active. This is user configurable. (See
“Startup type” on page 5-24.)
Synchronizing memory tag values, derived tags, and
data log files To keep these elements synchronized, runthe same
derived tag components and data log models on both primary and
secondary computers. Memory tags can be kept synchronized if their
values are the result of derived tags.
Managing events While events, triggered by an event detector, are
not specifically synchronized between primary and secondary RSView
SE Servers, it is possible to manage which server is responsible for
detecting and executing events, so that only one server is active at a
time. To handle the situation where an event is executing when a
primary RSView SE Server fails, issue the EventOn command (to start
event detection) only on an active HMI server, and always issue the
EventOff command (to stop event detection) on a standby server. To
do this automatically, you can issue these commands in the HMI
server’s On Active or On Standby macros.
Executing commands and macros If a primary HMI server fails
when a command or macro is executing, the execution stops during
failover to a secondary HMI server. To continue, re-issue the
This is advisable only if the secondary computer does not also perform
processor- or disk-intensive tasks like data logging, processing derived
tags, or detecting and triggering events. Because the HMI projects are
loaded into memory on a secondary computer as soon as it is set up to
be a secondary RSView SE Server, ensure that the secondary computer
In this case, you cannot provide redundancy for HMI servers or data
servers because the redundant server would remain inaccessible if the
HMI network failed.
When the primary FactoryTalk Directory computer goes down and the
secondary FactoryTalk Directory becomes active, all RSView SE
Clients, RSView Studio, and the RSView Administration Console can
continue to access the system normally. Graphic displays, tags, and
other components that are added to the system are immediately
accessible to all clients.
When the HMI network fails, every client computer continues running
as a stand-alone application on the network. Clients can continue to
open graphic displays and tags located on the same computer, but
cannot open graphic displays or tags located on other computers on the
network.
RSView SE Servers
RSView SE Servers require licenses for the both primary servers and
the secondary servers. Floating licenses are not supported for RSView
SE Servers.
OPC Servers
Deploying
distributed applications
Once you have finished developing and testing your application, you
are ready to move it to the set of computers that will run your
application in a ‘live’ setting, for example, the plant floor. This process
is called deploying an application.
Your own checklist might include activities that are not listed here, for
example, setting up database software, or OPC servers. Ensure that
you add these activities to your own checklist.
Copy HMI server files If you are copying HMI servers from one
set of computers to another, you must copy the HMI servers’ files
as well. To copy the files, use Windows Explorer.
Specify the startup settings for each HMI server The startup
settings allow you to specify which parts of your application start
automatically when the HMI server starts.
If you have already set up an RSView SE Client, you can copy the
client’s configuration file (.cli) from one computer to another. You
do not have to modify the client configuration file after you have
copied it.
By default, the Application Data folder is hidden. To see it, from the
Windows Explorer, click the Tools menu, select Folder Options,
and then click Show hidden files and folders.
1. Copy the files from the following folder on the source computer to
the same folder on the target computer:
The HMI project folder has the same name as the HMI server in
the application, and contains the RSView SE Server's configuration
files.
IMPORTANT The HMI server will fail to load if you deleted the
HMI project files. Even if this happens, you can still
access the HMI server’s properties.
3. Right-click the HMI server, and then click Properties to open the
HMI Server Properties dialog box.
5. Click OK.
To do this, use the HMIBackup utility to copy the files from the source
computer to a temporary folder, and then copy the files from the
temporary folder to the target computer.
Update the HMI server properties with the name of the new
computer on which the HMI server is running.
For details, see “Finding the information you need” on page P-2 in
the preface to this manual.
2. Extract utility to the local drive of the computer where the HMI
server is located.
4. For each HMI server located on the local computer that you want
to back up, run the following command from the Command
Prompt:
where:
[backup path name] is the optional path where the backup files will be
stored
For each HMI project you back up, a folder is created, with the same
name as the HMI project, inside the HMIBackup folder. The HMI
server’s backup files are copied to this folder.
X Copy the backup HMI project folders to the following folder on the
target computer:
IMPORTANT The HMI server will fail to load if you deleted the
HMI project files. Even if this happens, you can still
access the HMI server’s properties.
2. Right-click the HMI server, and then click Properties to open the
HMI Server Properties dialog box.
3. In the box, Computer hosting the server, type the name of the new
computer, or click the Browse button to select the name of the
Browse button new computer.
4. Click OK.
You can also use the HMI Server Properties dialog box to view the
HMI server’s name, project file path, number of existing graphic
displays or the maximum number of graphic displays allowed.
Use the RSView SE Service Manager tool to start or stop the HMI
services running on a computer.
IMPORTANT When you stop the HMI services manually, clients are
disconnected, all HMI servers running on the
computer are shut down, and the activation keys used
by the HMI servers are released.
When you start the HMI services manually, clients are allowed to
connect to HMI servers on the computer.
4. Copy the HMI project that was changed to the server on which
the project is out of date. For details, see “Copying HMI server
files” on page 26-4.
For details about copying third-party OPC data servers, see the
documentation supplied with your OPC server.
3. Select a folder for the backup file, type a name for the file, and then
click Save.
4. Copy the backup file from the source computer to the target
computer.
If you copy a data server from one computer to another, you must
change the name of the computer on which the data server is running.
3. In the box, Computer that will run the OPC server, type the name
of the computer that is hosting the RSLinx or OPC-DA 2.0 data
Browse button server, or click the Browse button to select the computer name.
4. If you are setting up redundancy for the data server, specifiy the
properties of the secondary data server in the Redundancy tab. For
details, see “Setting up data server redundancy” on page 7-9.
5. Click OK.
load, view, and interact with multiple graphic displays at a time, that
reside on any HMI server.
Set up the RSView SE Client using the RSView SE Client wizard. The
HMI server does not have to be running when you set up an RSView
SE Client, however, the HMI server must be loaded before you can
open an RSView SE Client.
The wizard creates a configuration file with the extension .cli. The
information in the file includes the name of the RSView application to
which the client can connect, the components that are started when the
connection is made, and the run-time behavior of the client.
With the RSView SE Client wizard you can create a new client
configuration, or edit an existing one. You can also run a configuration
file from the first screen of the RSView SE Client wizard, or you can
remove a configuration file from the list of available configurations.
X Copy the .cli file from the following folder at the source computer
to the same folder at the target computer.
1. Make sure all HMI servers used by the application are loaded. For
information about loading HMI servers, see “Setting up HMI
server properties” on page 5-22.
If the current Windows user is not in the RSView User Accounts list,
the validation fails. A message is displayed, and you can then either
cancel the attempt to run the RSView SE Client, or you can log in
manually as another user. If you click Retry to log in manually, the
RSView Login dialog box appears.
You can have more than one client window open on a single computer.
Multiple client windows allow you to connect to more than one
application from a single client computer.
3. Make sure the HMI servers used by each application are loaded.
DisplayClientOpen <file>
where <file> is the name of the .cli file you want to open.
You can stop all HMI server components manually using RSView
Studio, or the RSView Administration Console. For details, see
page 26-9.
Deploying
stand-alone applications
About deploying stand-alone applications
Once you have finished developing and testing your application, you
are ready to run your stand-alone application. If necessary, you can
move your application to a new location in a ‘live’ setting, for example,
the plant floor. This process is called deploying an application.
There are several activities you must perform to deploy your stand-
alone application.
Use this list of activities as the basis for your own checklist, to help you
deploy your application.
Your own checklist might include activities that are not listed here, for
example, setting up database software, or OPC servers. Ensure that
you add these activities to your own checklist.
If you have already set up an RSView SE Client, you can copy the
client’s configuration file (.cli) from one computer to another. You
do not have to modify the client configuration file after you have
copied it.
For details about using the Application Manager tool, click Help.
The HMI Server Properties dialog box also shows the HMI server’s
name, project file path, number of existing graphic displays or the
maximum number of graphic displays allowed.
3. In the HMI Server Properties dialog box, click Stop All Running
Components. All components stop running, including alarms, data
log models, derived tag components, and event components.
If you are using RSLinx, on the RSLinx primary computer, run the
RSLinx Backup Restore Utility to back up configuration files. Then on
the second computer, run the utility to restore the configuration. Click
the Windows Start menu, select Rockwell Software, RSLinx, and then
click Backup Restore Utility.
2. In the box, Computer that will run the OPC server, type the name
of the computer on which the data server is installed, or click the
Browse button Browse button to select the computer name.
3. Click OK.
load, view, and interact with multiple graphic displays at a time, that
reside on any HMI server.
view trends.
Set up the RSView SE Client using the RSView SE Client wizard. The
HMI server does not have to be running when you set up an RSView
SE Client, however, the HMI server will be loaded when you open the
RSView SE Client.
The wizard creates a configuration file with the extension .cli. The
information in the file includes the name of the RSView application to
With the RSView SE Client wizard you can create a new client
configuration, or edit an existing one. You can also run a configuration
file from the first screen of the RSView SE Client wizard, or you can
remove a configuration file from the list of available configurations.
If the current Windows user is not in the RSView User Accounts list,
the validation fails. A message is displayed, and you can then either
cancel the attempt to run the RSView SE Client, or you can log in
manually as another user. If you click Retry to log in manually, the
RSView Login dialog box appears.
3. Make sure the HMI servers used by each application are loaded.
DisplayClientOpen <file>
where <file> is the name of the .cli file you want to open.
Server components start after the HMI server loads. Opening RSView
SE Client will run the Startup components. You can start HMI server
components manually using RSView Studio, or the RSView
Administration Console. For details, see page 27-3.
You can also stop all HMI server components manually using RSView
Studio, or the RSView Administration Console. For details, see
page 27-3.
Administering
applications
After your application has been deployed, you might need to make
small changes to the application while it is in use. This process is called
administration.
You can make changes to your application using either RSView Studio,
or the RSView Administration Console.
set the time, date, and number formats correctly for your computer.
1. Click the Start button, select Settings, and then click Control Panel.
5. Click OK.
For information about using the Control Panel to set time, date, and
number formats, see your Windows documentation.
For details about using the Application Manager tool, click Help.
RSView Studio, or
add users to, or remove users from the system, using the User
Accounts editor.
change which commands are secured, and which users can access
the commands, using the Secured Commands editor.
change how alarms are logged and annunciated, using the Alarm
Setup editor.
change what system activities are logged, and how frequently, using
the Diagnostics Setup editor on the Tools menu.
change the location to which alarms are logged, and manage log
files, using the Alarm Log Setup editor on the Tools menu.
import and export HMI tags using the Tag Import and Export
Wizard on the Tools menu.
To find information about using these editors, see the chapters in this
manual.
After you have deployed an RSView application, be sure that the disk
space on the computers running HMI servers does not fall below
20 MB.
1. In the HMI server’s Events editor, create an event that uses the
free_bytes function to return number of free bytes available on the
HMI server’s hard disk.
2. Create a tag. If you want alarms when disk space drops below
preset levels above 20 MB, create an analog tag. If you want an
alarm only when disk space drops below 20 MB, create a digital tag.
RSView commands
This appendix describes:
in a macro or symbol.
in a command line.
Enclose long file names containing spaces with double quotes when
the file names are used as parameters. For example,
Display Screen$Tag1$
Display $Tag3$$Tag2$
Valve23=Open
When the macro runs, Tag1=1, Tag2=2, and Tag3=Screen. These are
all string tags.
You don’t need to put braces around tag names when using
placeholders in commands.
In this example, the initial value of Tag1 is zero. The value 4 is assigned
to Tag1, and the tag is then used in a macro. Type the following text in
a button’s press action:
RSView replaces the placeholder in the command with the tag’s current
string value. The graphic display Screen4 appears.
Tag placeholders are evaluated before commands run. You can ensure
Tag1 evaluates to 4 by embedding the tag placeholder in a macro, not
in the button. If you include the tag placeholder in the button, the tag
placeholder evaluates before the value of the tag is set to 4. $Tag1$ will
therefore evaluate to zero (the tag’s initial value), not 4.
You don’t need to put braces around tag names when using
placeholders in commands.
Precedence
Commands take precedence over macros. For example, if you have a
macro called Display the Display command will run whenever you try
to run the Display macro.
The following commands run wherever they are issued. For example,
if one of these commands is issued at the client, it runs at the client.
When the command runs from a graphic display, the area that
contains the graphic display is used to resolve the relative reference.
When the command runs from a graphic display, the area that contains
the graphic display is used to resolve the relative reference.
Some commands are run by a part of the system that runs in the
background. This background activity is managed by the HMI server.
For example, an Events component runs commands when events
occur. These systems resolve relative references using the area in which
the HMI server is located, because the HMI server manages the
background activity.
Creating symbols
The symbol
The string
Important guidelines
A symbol and a macro should not have the same name. If they do,
the symbol runs instead of the macro.
Right-click the Command Line icon and then click Show on the
context menu.
Click the Browse button beside an action field or any field requiring
an RSView command.
To see the commands and macros you last used, click this folder:
To see the commands that can be used for a particular part of the
system, click one of these folders:
= (Equal) [&]<tag_name>=<expression>
<tag_name> The name of the tag that will store the result of the
expression. The tag name can be an absolute or relative reference. The
tag name can include an area name.
Enclose strings in quotes. The string can contain any character, and can
include spaces.
Do not use braces for the tag name before the equal sign.
You can attach security to the = (Equal) command just as you can for
any RSView command. For information about security, see Chapter 15,
Setting up security.
&Tag1=Tag1+1
Evaluates the command asynchronously. Increases the value of Tag1
by 1.
Tag1=Tag2
Sets the value of Tag1 to be the same as Tag2.
Tag1=Tag2+Tag3
Adds the values of Tag2 and Tag3 and stores the result in Tag1.
1Pump={Industry-2}+{2Pump}
Adds the values of Industry-2 and 2Pump and stores the result in
1Pump. Braces surround Industry-2 because of the dash in the name.
Braces surround 2Pump because the name starts with a number. No
braces are used for 1Pump because this name is on the left side of the
equal sign.
Acknowledge Hopper1\Flow
Acknowledges all outstanding alarms for the tag Hopper1\Flow.
Acknowledge Hopper1\*
Acknowledges all outstanding alarms for all tags in the folder called
Hopper1.
Acknowledge *
Acknowledges all outstanding alarms.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
OutOfAlarm or Out Indicates that the tag has gone out of alarm.
/A Analog
/D Digital
If the name of an alarm event is the name of a tag in the tag database,
the value specified by this parameter will not update the tag’s value in
the value table.
<HH:MM:SS> The 24-hour military format for time. You must use
this format for indicating the time.
If you specify a time stamp for an alarm, the alarm may not appear as
the most recent alarm in the \system\AlarmBanner tag, even if it was
logged after an alarm with a more recent time stamp.
This command lets you start a new alarm log file on demand. All
subsequent alarm messages are logged to the new file.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains the
graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
[“Text”] A text string, up to 132 characters long. The text can contain
the following placeholders:
\N The tag name. If the tag is in a local tag database, you can also
use the placeholders [\S] tag description and [\U] tag units.
If both the Text parameter and the /P parameter are specified, the
contents of the Text parameter will appear in the text field at run time,
and the operator can modify or add to the contents of the Text
parameter before it is logged to the alarm log file. If the tag name (/T
If both the /P parameter and the /Sn parameter are specified, the
prompt dialog box will display the alarm severity at run time, but the
operator cannot change the severity.
[/R] Logs the remark to a printer as well as to the alarm log file. If the
alarm severity is not specified (/Sn parameter), the printer for Severity
1 is used. If no printer is assigned to the specified severity, the alarm log
remark is not printed.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
To have alarm monitoring start when an HMI server starts, open the
HMI Server Properties dialog box, click the Components tab, and then
select the Alarming check box.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If Notepad is open and contains an untitled file, the Notepad title bar
reads Untitled–Notepad. To close Notepad you must type exactly
what’s in the Notepad title bar:
AppAbort Untitled–Notepad
You can also work around this problem programmatically. For details,
see technical note P9029 in the Rockwell Software Support Library.
Beep Beep
Runs a wave file to produce a sound from the computer speaker. The
sound is a wave file assigned to the Default Beep in the Windows
Control Panel.
<component> The name of a data log model. The data log model can
be an absolute or relative reference. The data log model can include an
area name.
<value> The numeric portion of the time interval for the log rate. For
example, if you want to log data every 20 seconds, the value is 20. The
value must be an integer from 1 to 64,000.
<component> The name of a data log model. The data log model
can be an absolute or relative reference. The data log model can
include an area name.
<component> The name of a data log model. The data log model
can be an absolute or relative reference. The data log model can
include an area name.
/area::* Creates new files for all models that are currently running.
DataLogNewFile Daily
Creates a new set of data log files for the data log model called Daily.
DataLogNewFile /Mixing::*
Creates a new set of data log files for all the data log models in the area
called Mixing. You cannot specify this parameter as /Mixing*.
Stops data logging for a specified model or stops data logging for all
models.
<component> The name of a data log model. The data log model
can be an absolute or relative reference. The data log model can
include an area name.
<component> The name of a data log model. The data log model can
be an absolute or relative reference. The data log model can include an
area name.
To have a data log model start automatically when a project starts, open
the HMI Server Properties dialog box, click the Components tab, click
the Data Logging check box, and then specify a component.
<component> The name of a data log model. The data log model can
be an absolute or relative reference. The data log model can include an
area name.
<component> The name of a data log model. The data log model
can be an absolute or relative reference. The data log model can
include an area name.
/area::* Logs a snapshot of data for all models that are running.
<component> The name of a data log model. The data log model
can be an absolute or relative reference. The data log model can
include an area name.
/area::* Switches data logging for all models that meet the
conditions outlined above.
Symbol definitions are valid only during the current session; they must
be re-defined each time RSView is restarted. Symbols are typically
defined in a startup or login macro.
Define Di
Deletes the symbol Di.
If you are using the Cache After Displaying option in the Display
Settings dialog to cache displays, use the position parameters with the
Display command to ensure that displays open in the correct position
after caching. Otherwise, if a user moves a display at run time, the new
position is remembered by the cache option.
Do not cache more than 40 displays using the [cache] parameter and/
or the Cache After Displaying option.
[/E] Disables the Enter key so it does not download values in numeric
input fields to the programmable controller or server, unless the
Display On-Screen Keyboard option is selected (in the Behavior tab of
the Display Settings dialog box).
[/U] Updates tag values in all input fields when the display first opens.
[cache] Specifies how to load the specified graphic display into the
display cache, as follows:
/Z Loads the specified graphic display into the cache (but does not
make it visible), so the display appears quickly when it is first used.
To remove all displays from the cache, use the FlushCache command.
To remove a particular display from the cache, use the
FlushCache [display] command.
Display Sample
The graphic display called Sample is opened. It is positioned and sized
as specified in its Display Settings dialog box.
If a graphic display called Canning uses three tag placeholders, and you
want to substitute tags for canning corn, you would type:
<file> is the name of the RSView SE Client configuration file (.cli) you
want to close. The name can include the path to the file.
<title> Closes the RSView SE Client with the specified text in its title
bar.
<file> is the name of the RSView SEClient configuration file (.cli) you
want to open. The name can include the path to the file.
Download Download
Writes the value in the selected input field of the active graphic display
to the programmable controller or server.
The Enter key also downloads the value in the selected input field.
However, if the /E parameter is used with the Display command, the
Enter key is disabled, unless the Display On-Screen Keyboard option
is selected (in the Behavior tab of the Display Settings dialog box). If
the selected input field is a recipe field, pressing the Enter key opens
the Recipe dialog box.
Writes the values in all input fields of the active graphic display to the
programmable controller or server.
Without the parameter, unloads all graphic displays from the display
cache. With the parameter, unloads the specified graphic display from
the display cache.
[display] The name of a graphic display. You can specify the graphic
display name using either an absolute or relative reference. The graphic
display name can include an area name.
If a display uses the Always Updating option with the Cache After
Displaying option, the display’s shutdown command runs when you
issue the FlushCache command.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
IMPORTANT This command will not set the handshake bit for any tag
already in alarm when the command runs.
[word] A word you want to search for in the Help file. When you
specify a search word, the command will either:
open the Help file at a topic if the word uniquely identifies that
topic.
The name of a Windows Help file. The default Help file is for
[/Ffile]
RSView.
Runs the command or macro associated with the named tag, whether
or not the tag is in alarm. The command or macro runs at the same
location as the one from which the Identify command was issued.
[tag] Specifying the word “tag” inside square brackets runs the
Identify command for the tag associated with the highlighted object in
the active graphic display.
IMPORTANT When many alarms are occurring rapidly, do not use the
Identify command without a tag name. A new alarm
could become the current alarm before the Identify
command runs, and then command or macro that runs
might not be the one expected.
Identify Hopper1\Divider
Runs the Identify command or macro for the tag Hopper1\Divider,
whether or not the tag is in alarm.
Identify [tag]
Runs the Identify command or macro for the selected tag in the active
graphic display.
You cannot nest If commands. Commands that you use for the
THEN or ELSE actions cannot be If commands.
The keywords IF, THEN, ELSE, and ENDIF are not case sensitive.
Example:
You can use the Invoke command to change the properties listed in the
Property Panel for a graphic object.
The easiest way to specify the <parameter> string for the Invoke
command is to use the Command Wizard.
parameter The tag name or constant that the method will use.
You must specify all of the parameters, even those that are optional.
tag_name The name of the tag to which the value returned by the
method is written.
tag_name=display_name.object.property(tag_name or
constant) Sets an object’s property to the specified tag’s value or to a
constant value.
Logs users into the system. To log in, users must have an account in the
User Accounts editor.
Logout Logout
NextPosition NextPosition
Moves focus to the object with the next highest tab index number.
Tab also moves focus to the object with the next highest index number.
NextWindow NextWindow
Ctrl-Tab and Ctrl-F6 also move focus to another open graphic display.
Opens the RSLogix 5000 program, and then displays the specified
routine. This command can only be issued from RSView Studio, the
RSView Administration Console, or the RSView SE Client, and
requires that RSLogix 5000, version 12 or later, be installed on the
computer on which the command is issued.
<project> The full path to an RSLogix 5000 project file (*.acd). If
there are spaces in the path name, enclose the path in quotation marks
(“ ”).
<program> The name of the program in the RSLogix 5000 project.
<routine> The name of the routine in the program.
[/RNrung_number] Optionally, the number of a rung in a ladder
diagram routine.
[/RIrung_identifier] Optionally, the identifier of a rung in a ladder
diagram routine.
Examples:
OpenRSLogix5000 "c:\My Projects\Pumphouse.acd"
MainProgram Ladder1 /RN34
This command opens the project called Pumphouse.acd, locates the
program called MainProgram, opens the routine called Ladder1, and
navigates to rung number 34.
OpenRSLogix5000 c:\Pumphouse\Pumphouse.acd
MainProgram Ladder1 /RI4967157
This command opens the project called Pumphouse.acd, locates the
All commands or macros that follow the Pause command must not be
asynchronous (preceded by the & sign), otherwise the Pause command
has no effect.
<file> The complete path to the wave file, including the .wav
extension.
Moves focus to the object with the specified tab index number.
buttons
PrevPosition PrevPosition
Moves focus to the object with the previous tab index number.
Shift-Tab also moves focus to the object with the previous number.
PrevWindow PrevWindow
[/U] Initiates an update of tag values in all input fields before starting
to print. This parameter is not necessary with input fields that are
updated continuously.
PrintDisplay prints the entire run-time display, even if parts are covered
by other displays. However, PrintDisplay does not necessarily print
ActiveX or OLE objects in their run-time state.
Moves the specified graphic display in front of all other windows. If the
specified graphic display is of the Replace or Overlay type, and a display
of the On Top type is open, PullForward positions the specified display
behind the back-most On Top display and gives the specified display
focus.
Moves the specified graphic display behind all other windows. If the
specified graphic display is of the On Top type, PushBack positions the
display behind any other open On Top displays, and in front of any
open displays of the Replace or Overlay type.
[/V] Performs a read immediately after the write to verify that the value
was altered in the programmable controller or server.
IMPORTANT If you use the Ramp command in a macro, you must use
two percent signs (%%) instead of one. A single percent
sign is used in a macro to indicate a parameter. For
example, to create a macro that increases the value of
tag1 by 75%, you would type: Ramp tag1+75%%
Reads the values from a recipe component into all input fields in the
active graphic display. This command is used with the Recipe field.
Saves the values in all input fields of the active graphic display to a
recipe component. This command works with the Recipe field.
You can specify whether comments are logged. To do this, select the
Message Routing item in the Diagnostics Setup tool, and then select
one or more of the Info check boxes.
ScreenPrint ScreenPrint
[/V] Performs a read immediately after the write to verify that the value
was altered in the programmable controller or server.
A numeric value of 0 or 1.
If the alarm for the specified tag is set up to use the internal bell, this
command silences the computer’s sound.
If the alarm for the specified tag is set up to use the external bell, this
command resets the tag associated with the external bell and silences
the associated audio device.
Silences the internal and external bells for all tags in alarm.
Using this command is faster than using the Silence command with the
asterisk (*) wildcard.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
If the command runs from a graphic display, the area that contains
the graphic display is used to resolve the reference.
<tag_name> The name of a tag, or a wildcard. You can specify the tag
name using either an absolute or relative reference. The tag name can
include an area name.
[/V] Performs a read immediately after the write to verify that the value
was altered in the programmable controller or server.
Upload Upload
System tags
System tags are preconfigured HMI tags that are created and updated
by an HMI server.
Alarms
The following tags are updated with information about the alarms in
the HMI server:
Tag name Type Contains information about
Time
The following tags contain time and date information in various
formats:
Tag name Type Provides this data Read or write
Monday,
December 16 2002
10:47:50 AM
system\DayOfMonth Analog Day of the month Read only
(1 to 31).
system\DayOfWeek Analog Day of the week Read only
(1 to 7); Sunday=1.
Setting up DDE
communications for
HMI tags
DDE servers provide a way to connect an HMI server’s HMI tags (the
DDE client) to:
RSView SE Server’s
HMI tags
CF_Text or CF_Text or
XLTable AdvanceDDE TM
AdvanceDDE*
Third-party Third-party
RSServer DDE server
application,
such as
Microsoft Excel
Network or
PLC network comunication
link
5. In the Tags editor, create tags. Select Device as the data source. In
the Address box, type the required DDE address.
For details about the syntax of DDE addresses, see page C-4.
For details about creating tags, see “Working with tags” on page 8-1.
The following topics describe how to complete the Data Source fields
in the Tags editor for tags that use DDE communications.
For details about creating HMI tags, see “Creating HMI tags” on
page 9-1.
1. Click Device.
Type the DDE address for the tag. The DDE item name and
format depend on the DDE server, and are not validated by
RSView.
DDE : Application|Topic!Item
between the Application name, the vertical bar, and the Topic name.
between the Topic name, the exclamation mark, and the Item name.
For applications using DDE, values are updated by the server at the
rate specified in the server product. When the server detects a change,
it provides the changed value to RSView. For more details about setting
the poll rate, see your server documentation.
The ODBC
database schemas
RSView produces three kinds of log files—activity, alarm, and data log
files—that can be stored in ODBC-compliant databases. This chapter
specifies the schemas for these databases.
TimeStmp The time and date data was logged, in SQL_TIMESTAMP Driver
coordinated universal time (UTC) format. dependent
MessageText The text of the message. SQL_VARCHAR, or 254
SQL_CHAR
Audience A number representing the audience for SQL_SMALLINT, or 1
the message: SQL_INTEGER
2 for Developer
3 for Secure
4 for Engineer
8 for Operator
1 for Error
2 for Warning
4 for Information
8 for Audi
Area The area in which the activity occurred. SQL_VARCHAR, or 80
SQL_CHAR
Location The name of the computer that initiated SQL_VARCHAR, or 15
the command or action that caused the SQL_CHAR
activity.
UserID The name of the user that initiated the SQL_VARCHAR, or 38
command or action that caused the activity. SQL_CHAR
UserFullName The name of the user (including domain SQL_VARCHAR, or 255
name, if there is one) that initiated the SQL_CHAR
command or action that caused the activity.
Provider The name of the product the activity SQL_VARCHAR, or 20
belongs to. SQL_CHAR
TimeStmp The time and date data was logged, in SQL_TIMESTAMP Driver
coordinated universal time (UTC) format. dependent
MilliTime Millisecond time when data was logged. SQL_INTEGER 3
Log tables for floating-point and string data are the same except one
contains analog and digital tag data and the other contains string tag
data.
This column Contains SQL data type Length
DateAndTime The date and time the tag values were SQL_TIMESTAMP Driver
logged. dependent
Millitm The millisecond time the tag values were SQL_SMALLINT, or 4
logged. SQL_INTEGER
TagIndex, or The index number for the tag. The tag SQL_SMALLINT, or 2 or
name that corresponds to this number is SQL_INTEGER 4
listed in the tag name table.
TagName If the tag table isn’t used, the tag name SQL_VARCHAR, or 255
appears in this column SQL_CHAR
Val The analog or digital value of the tag. SQL_DOUBLE, or 8, or
SQL_INTEGER, or 4, or
SQL_SMALLINT 2
The string value of the tag. SQL_VARCHAR, or 82
SQL_CHAR
D if a node is disabled.
0 for Long
1 for Float
2 for String
When the translators send the translated files back to you, you can
import them into your application, substituting the original language of
your application for the one contained in the translated text files.
the file format of the text file, including information about what
parts of the file should not be translated. You should share this
information with the translator to ensure that the file can be
imported after translation.
text that can be displayed at run time, but is used to operate your
application, for example the names of graphic displays, and
command strings.
text that you add to your application, but is not displayed at run
time.
text in the login dialog box that appears to operators at run time.
text in the Recipe dialog box that appears to operators at run time.
and so on.
the text that appears in the title bar of the RSView SE Client
window. This text is part of the setup for your display client. The
text is not part of your application.
System Tags
You might have used system tags in your application to display text in
graphic displays. System tags are always shown in the format prescribed
by the language of the Windows operating system—if you are running
the English language version of the Windows operating system, the
text in system tags is displayed in English, and dates and numbers are
formatted for U.S. English. These system tags include:
Time
Date
DateAndTimeString
AlarmResetDateAndTimeString
The following text strings are not exported. The properties listed below
apply to all graphic objects in your application that support the
properties mentioned, unless the names of specific objects are
mentioned.
In this product This graphic object Includes text that cannot be exported
for this property (where applicable)
Exporting text
Text in your application is exported to tab-delimited text files in
Unicode format.
1. Ensure that the HMI project containing the text you want to
export is not being modified or edited. If components are being
edited remotely and have not been saved, the exported file will not
contain the unsaved changes.
To select all of the check boxes, click Select All. To deselect all of
the check boxes, click Clear All.
If you cancel the export before it is complete, any files that were created
are not deleted, but their contents might not be complete.
Importing text
To import text from a file into your application, the file must be saved
in Unicode Text format.
For details about saving the file in Microsoft Excel, see “Saving the text
file in Microsoft Excel” on page E-15.
Text strings that exist in your application, but do not appear in the text
file are not deleted. This allows you to import only those strings that
have been modified.
1. Ensure that the HMI project into which you want to import text is
not being modified or edited. If components are being edited
remotely and are saved after you have imported text for them, the
imported text will be overwritten.
5. In the Select Files window, click the Browse button, and then select
the text files that contain the text you want to import into your
Browse button application.
Troubleshooting importing
Each time errors occur while importing text into an application, the
ImportErrors.txt file is overwritten.
If some, but not all, of the text in an HMI server appears to have been
modified, the import might have been canceled. If you cancel the
import before it is complete, any text strings that were changed are not
restored to their original values. To restore the text originally in the
application, import the text from the backup text file you created in
step 2 on page E-9.
ServerName defined in FileName.txt does not exist. None of the
strings in this file were imported. This error is logged if the name
of the HMI server is invalid. If the HMI server was renamed, open the
file, and then correct the name of the HMI server.
the string reference number has been modified in the text file, and
the new string reference number is not used in the application.
Open the backup text file, and then copy the correct the string
reference number into the translated text file.
the object was deleted from the application after the text was
exported. If this is correct, ignore the error.
4. Click Next.
1. Select the Tab check box. If any other check boxes are selected,
clear them.
3. Click Next.
5. Click Finish.
2. When closing the file, you are prompted to save changes. Click Yes.
3. You can save the file using its original name, or you can type a new
name.
If you use Notepad to open a Unicode text file that was saved in Excel,
you will notice some differences from a file edited and saved in
Notepad.
IMPORTANT You do not have to change the format of the file before
you import it into RSView Studio.
When saving the file, save it using the Unicode encoding option in the
Save As dialog box.
File schema
Comments
The text file uses the # symbol as a comment delimiter if it is the first
character on a line.
The first seven lines of the text file contain header information that
should not be translated or modified.
Body
The body of the text file starts on line eight, and includes the following
fields:
In the translated text file, the only text that should be modified is the
text inside the quotation marks in the string definition column. For
example, translated into German, the file would contain these changes:
Do not change the entries in the component name column, unless the
component was renamed in the application after the text was exported.
If a text string contains double quotes, the whole string definition must
also be enclosed in double quotes. For example:
To force text to begin on a new line, precede the text with the escape
character \ and the new line character n. For example:
Motor\nabschalten
Motor
abschalten
To make the characters \n appear as part of the text, type \\n. To make
a backslash appear in the application, type two backslashes (\\).
Seven\Eight
About XML
XML is the Extensible Markup Language used to create documents
with structured information. In RSView Supervisory Edition, you can
use XML to edit the elements and attributes of multistate indicators.
For information about using the XML language, see the World Wide
Web Consortium’s web page about XML at:
http://www.w3.org/XML/
The settings for the multistate indicator objects defined in the file
are imported into the corresponding multistate indicator objects in
the Graphic Display.
A sample XML file is provided in Help. Use this sample file for
information about the layout and hierarchy of elements in the XML
file.
You can copy the text in Help into another application, and then save
the file in Unicode format, with a .xml extension.
For example, if a multistate indicator has a border style set to line, and
a shape set to circle, and then you import an XML file to change the
border style to raised and the shape to rectangle, the object could be
displayed as a rectangle with the border style set to line.
This happens if the border style is specified before the shape in the
XML file. Because border style is specified first, it is applied to the
object when the object is still a circle. Since a circle cannot have a raised
border style, the change is not made. After that, the shape is changed
to a rectangle.
The first line of every XML file contains the xml version, and encoding
attributes.
Make sure the encoding attribute matches the format that you use
when you save the file. For example, if the original file was saved as
UTF-8 and you plant to save it with UTF-16 encoding, make sure the
first line specifies:
attribute="UTF-16"
<gfx>
.
.
.
</gfx>
<gfx>
<defs>
<font id="New Font" font family="Verdana"/>
</defs>
<msi id="Indicator1" >
.
</msi>
<msi id="Indicator2" >
.
</msi>
.
</gfx>
You can specify multiple attributes for an element, and have multiple
elements. For a more detailed XML example, see the sample multistate
indicator XML document in Help.
If you include settings for an object whose name does not match one
of those in the graphic display, the settings for that object are not
imported. Settings for all other objects in the file whose names do
match those in the graphic display are imported.
borderwidth = <int>
description = <string>
height = <int>
id= <string> – Must be the name of the object you are modifying.
Each multistate indicator object must have a unique ID.
numstates = <int>
width = <int>
x = <int>
y = <int>
value = <int>
id = <string> – Type a short name that you can use when referring to
the font element later in the XML file. For example, you can use a font
ID called BigFont to refer collectively to the values of the font-size and
font-weight attributes. See also “Caption element” on page F-13.
font-family = <string>
font-size = <int>
text-decoration = none|underline|line-though|
underline; linethrough – To specify multiple values for the text-
decoration attribute, separate the values with semi-colons. This is the
only attribute for which you can specify multiple values.
name = <string>
expr = <string>
Animation Element
This element is called animation in the XML file. The animation
element must be contained within an animations element.
expr = <string>
type = visibility
text = <string>
Index ■
I–1
AlarmLogOn A-20 system default 11-27
AlarmLogRemark 11-79, A-21 user default 11-28
AlarmLogSendToODBC A-23 Alarm messages 11-29
AlarmOff 11-10, 11-85, A-23 setting up 11-26, 11-34, 11-39
AlarmOn 11-17, 11-81, 11-84, A-24 Alarm monitoring 11-1, 11-42
I–2 ■
RSView Supervisory Edition User’s Guide
AlarmPrintOn command 11-81, A-25 copying without copying objects 18-68
Alarms Current [Tag] parameter 18-54
acknowledging 11-12, 11-15 defining range of motion 18-11
adding to tags 9-25, 11-2
display keys 18-60
ALM_ACK expression
finding 18-65
changing default behavior 11-14
finding objects animated by tags 16-14
assigning sounds to 11-25
finding tags 18-65
bells 11-25
for grouped objects 16-28
charting in trends 19-29, 19-38
grouped objects 18-65
crossing thresholds 11-22
min. and max. values 18-9
expressions in 11-13
object keys 18-46, 18-49
identifying 11-35, 11-40, 11-75
logging 11-42 Object Smart Path 18-6, 18-11
locally 11-44 precedence in grouped objects 18-65
tags and placeholders 18-7
to ODBC 11-49
testing 18-6, 19-63
max. update rate 11-23
using commands for actions 18-8
messages 11-26, 11-34, 11-39
planning 3-8 using VBA code 18-39
running custom programs 11-80 viewing in Object Explorer 16-13
Animation dialog box 18-3
setting up 11-4, 11-20
Animation types 18-1
for analog tags 11-32 color 11-10, 18-14
for digital tags 11-37 in grouped objects 18-65
using Tags editor 11-2, 11-20, 11-31 fill 18-20
severity 11-24 in grouped objects 18-65
starting 11-84
height 18-27
stopping
horizontal position 18-22
starting 11-85
horizontal slider 18-34
summary of steps 11-20
OLE verb 15-16, 18-37
suppressing 11-12, 11-81, 11-82
rotation 18-29
viewing suppressed alarms 11-82
touch 18-33
suppressing printing 11-81
vertical position 18-23
system tags B-1
vertical slider 18-36
using tags for 8-5
ALM_ (alarm) functions 11-13, 11-14, 20-13
visibility 11-10, 18-13
Analog HMI tags width 18-25
alarms 11-32 Application commands
alarms for 9-25, 11-2, 11-31 AppAbort A-25
alarms when crossing thresholds 11-22 AppStart A-25
and trends 19-37 Application Explorer 2-5, 2-8, 5-14, 6-5
Index ■
I–3
Application files home area 5-9, 8-20
deleting 2-17 how to use 5-16
Application Manager 5-14, 5-15, 6-6, 6-7, max. number of HMI servers 5-18
27-3, 28-2
Applications
removing 5-18
administering at run time 28-2 showing in alarm summaries 11-67, 11-78,
11-80
distributed 5-1, 5-4
tag references 8-19
creating 5-13
Arithmetic operators 20-8
deploying 26-1 Arrow graphic object 17-170
FactoryTalk Directory location 4-6 Asynchronous execution
home area 5-9 = (Equal) command A-13
max. number of HMI servers 5-17 Set command A-54
Auto-repeat
number of displays 5-22
for keys 17-168
redundancy 25-13
renaming 5-14
root area 5-9
B
running as stand-alone 25-13 Backspace key 17-160
Bar graphs 17-150
localizing
indicator tag 17-143
see Localizing applications
Beep command A-26
opening 2-2 Bells for alarms 11-25
recently used 2-3 Bitwise operators
planning 3-1, 3-13 AND, & 20-10
running Samples 2-4 inclusive OR, | 20-10
securing 15-19 Browse button 2-19
Built-in functions
stand-alone 6-1
file 20-19
backing up 28-2
math 20-19
copying 27-3
security 20-20
creating 6-4 tag 20-13
deleting 6-7 time 20-15
deploying 27-1 Buttons 17-37
FactoryTalk Directory location 4-5 editing 17-45
importing projects 6-5 highlight
in redundancy 25-13 enabling or disabling 17-39
number of displays in 6-8
renaming 6-6 C
restoring 28-2 CABARC.exe 17-247
stand-alone vs. distributed 5-8 Cache
Windows A-25 creating for OPC data servers 7-10
Arc graphic object 17-17 synchronizing for OPC data servers 7-11
Areas 5-4, 5-8 Calling methods 18-43
adding 5-18 Check syntax
application root 5-9 derived tags 10-3
application root area 5-9 expressions 20-4
I–4 ■
RSView Supervisory Edition User’s Guide
Circle graphic object 17-15 Communications
Client commands See also DDE communications
DisplayClientOpen 26-18, 27-8 See also OPC communications
Client key commands errors 20-13
Key 23-15
planning 3-6
Client keys 23-5, 23-12 setting up 7-1
creating 23-12 Component names
precedence among key types 23-7 and /P parameter 2-18
running a key file 23-14 and spaces 2-18
Client Keys editor 23-12 long 2-18
Clients maximum length of 2-18
See RSView SE Client Components
Code window absolute references 5-10
getting help 24-11 adding 2-14
Color copying 2-14
in graphic displays 16-31, 16-68 deleting 2-17
animating 11-10, 18-14 in Application Explorer 2-13
in trends 19-13, 19-14, 19-15 naming 2-18
Color animation 18-14 opening 2-14
COMM_ERR function 20-13 relative references 5-10, 6-2
Command execution A-4 removing 2-17
Command line renaming 2-16
using A-10 starting manually 26-9, 27-3
Command Wizard 2-20, A-10 startup 5-26, 6-10
Commands A-1
stopping manually 26-9, 27-4
See also individual command entries Constants
absolute and relative references A-6 in expressions 20-7
adding alarm data 11-77 Context menus 2-19
assigning security to 15-13 using in graphics 16-15
attaching to ActiveX events 18-44 using in trends 19-62
executed at client A-5 Control
executed at server A-4 See Animation
Control list selectors 17-172, 17-177
in buttons 17-41 differences from piloted control list selectors
in editors 2-20 17-186
in events 14-1 Enter-key handshaking 17-175
in macros 2-20 indicator tag 17-174
placeholders in 22-2, A-2 navigating to 17-27
precedence over macros A-4 value tag 17-174
redundancy wrap around 17-181
See Redundancy Control network redundancy
securing 15-13 See Redundancy
ControlLogix processor 8-3
startup and shutdown 16-69 Crystal Reports
using in graphic displays 18-8 See Seagate Crystal Reports
using with alarms 11-74 Current [Tag] parameter 18-54, 18-62
Index ■
I–5
D starting and stopping 5-27, 6-11, A-28,
A-29
Data log files stopping 13-39
and third-party software 13-1
when to log data 13-29
creating 13-21 Data logging commands
deleting 13-26 DataLogChangeRate A-26
max. at run time 13-1
DataLogMergeToPrimary 13-20, A-27
naming 13-3
DataLogNewFile 13-25, A-28
redundancy
DataLogOff 13-39, A-28
See Redundancy
DataLogOn 13-38, A-29
storage format 13-2
DataLogRenameFile A-29
ODBC 13-1, 13-4
Data log models 13-1
DataLogSnapshot 13-32, 14-1, A-30
editing 13-35 DataLogSwitchBack 13-19, A-31
setting up 13-7 Data server tags
using in trends 19-30 Tags 8-1, 9-1
Data Log Models editor 13-5, 13-6 Data servers 5-4, 7-4
I–6 ■
RSView Supervisory Edition User’s Guide
DDE communications C-2 and trends 19-37
and RSServer C-1 setting up 9-16
poll rate C-4 Disk space
RSView as client monitoring 11-47, 13-21, 28-4
assigning server to RSView tags C-4 Display cache 16-62, 23-4
Display command A-33
setting up C-3
and graphic displays 16-66, 16-67, 16-74
setting up C-1
and key lists 18-65
syntax C-4
and parameter files 16-52, 16-55
Deadband for alarms 11-3, 11-5, 11-36
Define command A-9, A-31 and trends 19-64
Deploying applications Display keys 23-5
See Applications, distributed creating 18-60
See Applications, stand-alone editing 18-62
Derived tag commands precedence among key types 23-7
DerivedOff A-32 Display list selectors 17-206
DerivedOn 10-7, A-32 navigating to 17-27
Derived tags 10-1 Display Settings dialog box 16-57
DisplayClientOpen command 26-18, 27-8
checking syntax 10-3
Displays
creating 10-5
See Graphic displays
creating expressions 20-2 Displays editor
editing 10-6 See Graphic Displays editor
evaluation interval for 10-4 Distributed applications
max. components at run time 10-2 See Applications
max. in a component 10-2 Documentation for RSView SE P-1
max. update rate 10-4 Download command 17-115, 17-226, A-36
DownloadAll command 17-115, 17-226, A-37
redundancy
Drawing objects
See Redundancy
See Graphic object types
starting and stopping processing 5-27, 6-11,
10-7
Derived Tags editor 10-2 E
DeskLock 15-20
Edit Display mode 16-9, 19-63
Device HMI tags 9-2
Editors 2-10
DDE communications C-3 Alarm Log Viewer 11-9
OPC communications 9-18 Alarm Setup 11-20, 11-21
Diagnostics List 2-6, 12-17
Client Keys 23-12
clearing messages 2-7, 12-19
Data Log Models 13-5, 13-6
hiding 2-8
Derived Tags 10-2
moving 2-6
Displays 16-2
resizing 2-6
Events 14-2
showing 2-8
Diagnostics Setup 12-7
Graphic Libraries 16-50
Diagnostics Viewer 12-20 hints for working in 2-19
Digital HMI tags Libraries 16-50
alarms 11-37 Local Messages 17-235
alarms for 9-25, 11-7 Macros 22-1
Index ■
I–7
Parameters 16-53 creating expressions 20-2
Recipes 17-222 creating expressions for 14-6
Secured Commands 15-12 editing 14-6
Suppressed List 11-12, 11-82, 11-83 evaluation interval for 14-3
Tags 9-4, 11-20, 11-31 for on-demand logging 13-32
tags 11-31 max. components at run time 14-1
User Accounts 15-6 max. in a component 14-1
Electronic signatures 17-248 max. update rate 14-3
Ellipse graphic object 17-15
Embedded variables 21-1 overview 14-2
copying 21-9 redundancy
creating 21-2 See Redundancy
date and time starting and stopping processing 5-27, 6-11,
creating 21-7 14-7
Events editor 14-2
displaying at run time 21-11
Execute button
syntax 21-8 in alarm summaries 11-74, 11-77
deleting 21-9 Execute command 11-74
displaying at run time 21-10 Expressions 2-21, 20-1
editing 21-9 alarm events in 11-19
numeric and animation 18-8
creating 21-4 assigning to graphic objects
displaying at run time 21-10 using the Property Panel 16-38
syntax 21-5 built-in functions in 20-12
string checking syntax 20-4
creating 21-5 constants in 20-7
displaying at run time 21-11 copying 20-4
syntax 21-6 creating 20-2
time and date evaluation order 20-21
creating 21-7 formatting 20-5
displaying at run time 21-11 if–then–else logic 20-23
syntax 21-8 in alarms 11-13
types of values 21-2 in data logging 13-32
updating at run time 21-10 in derived tags 10-6
End key 17-160 in events 14-6
Enter key 17-160 in the = (Equal) command A-13
handshaking 17-174, 17-175, 17-176, in trends 19-29
17-192, 17-193, 17-194 operators in 20-8
Event commands
evaluation order of 20-21
EventOff 14-8, 25-8, A-37
I–8 ■
RSView Supervisory Edition User’s Guide
F Failure
See Redundancy
F1 key File locations
precedence 23-8 graphic libraries 16-49
FactoryTalk Diagnostics 12-1 File names
See also Diagnostics List See also Component names
access permissions for services 12-15, long
12-16 for data logs 13-3
audiences 12-4 short
buffering messages 12-12 for alarm logs 11-56
categories 12-3 File types
clearing the log file manually 12-10 graphics
destinations 12-2 importing 16-46
local log file 12-8 using bitmaps 16-47
logging path 12-8 log 13-2
logging to ODBC database 12-10 .dat 13-3
message audiences 12-4 data log 13-1
message buffering 12-12 .obf 13-4
message categories 12-3 ODBC
message routing 12-3 alarms 11-51
message severities 12-4 data log 13-4
ODBC data source 12-13 FactoryTalk Diagnostics 12-10
overview of steps 12-6 sound
routing 12-3 .wav 11-26, A-26, A-47
routing messages 12-14 Fill animation 18-20
setting up 12-6, 12-7 Filter
severities 12-4 alarm summaries 11-67
size of log file 12-9 removing from tags 8-18
tag writes 12-5 tags 8-17
viewing log files 12-19 FlushCache command 16-74, A-37
Index ■
I–9
Freehand graphic object 17-17 color 16-31
Functions creating 16-1, 17-1
See Built-in functions creating a background 16-45
creating a template 16-58
G creating templates 3-9
Gauges 17-141, 17-144
displaying alarm information in 11-10
indicator tag 17-143 displaying in background A-33
Global key commands downloading values from 17-107, 17-114
Key A-44 grid 16-6
Graphic display commands improving performance 16-74
Abort A-15 max. update rate of tags 16-64
Display A-33 moving among 23-1, 23-3, A-50
and key lists 18-65 planning 3-9
and parameter files 16-52, 16-55 positioning 16-67, A-34
caching 16-74, 19-64 preventing scroll bars 16-65
positioning 16-67 printing 2-21, 16-75, A-49
sizing 16-66 quantity in application 5-22, 6-8
reducing call-up time 16-62, 16-74, A-34
Download 17-115, 17-226, A-36
replacing text 16-39
DownloadAll 17-115, 17-226, A-37
running multiple copies 16-61
FlushCache 16-74, A-37
securing 15-14, 16-67
and trends 19-65
sizing 16-64, 16-66, A-34
executing shutdown command with
specifying run-time appearance 16-63
16-69
startup and shutdown commands for 16-69
NextPosition 18-49, A-45 testing 16-9
NextWindow A-45 animation 18-6, 19-63
Position 18-49, A-48
types 16-60
PrevPosition 18-49, A-48
uploading recipes to 17-221, 17-225
PrevWindow A-48
uploading values to 17-107, 17-114
PrintDisplay 16-75, A-49
using parameter files 16-54
PullForward A-50
using parameter files in A-34
PushBack A-50 Graphic Displays editor 16-2
RecipeRestore 17-226, A-52 Graphic libraries
RecipeSave 17-227, A-52 See Libraries
ScreenPrint 16-75, A-53 Graphic Libraries editor 16-50
SendKeys A-53 Graphic object types 17-1
SetFocus 16-61, A-56 ActiveX 17-242, 18-39
Upload 17-115, 17-227, A-59 common properties 17-25
UploadAll 17-115, 17-227, A-60 advanced objects 17-1, 17-26, 17-169
Graphic displays 16-1 alarm summary 11-10, 11-58
background color 16-68 arc 17-17
caching 16-62, 23-4 arrow 17-170
with the Display command 16-74, bar graph 17-150
A-33 circle 17-15
I–10 ■
RSView Supervisory Edition User’s Guide
control list selector 17-172, 17-177 recipe field 17-221
display list selector 17-206 rectangle 17-15
drawing objects 17-2 rounded rectangle 17-14
changing properties 17-20 scale 17-154
reshaping 17-18 square 17-15
text 17-2 string display field 17-105
ellipse 17-15 string display fields 11-10
freehand 17-17 string input field 17-107
gauge 17-141, 17-144 electronic signatures 17-249
graph 17-141, 17-150 tag label 17-204
image 17-6 time and date display 17-228
indicators 17-117 trend 19-1, 19-16
list 17-134 common properties 17-25
multistate 17-120 wedge 17-17
Graphic objects 17-1
importing XML F-3
aligning 16-22
troubleshooting XML F-5
XML file structure F-4 animating
See Animation
symbol 17-128
arranging 16-20, 16-24
key
keys 17-160 assigning tags
using the Property Panel 16-38
line 17-16
changing properties 17-20
local message display 17-215
color 16-31
local messages 17-231
common properties
numeric and string 17-103
changing properties 17-22
electronic signatures 17-249
converting 16-47
numeric display field 17-103
to wallpaper 16-45
numeric display fields 11-10
numeric input field 17-107 copying from other Windows applications
16-2
electronic signatures 17-249
creating expressions 20-2
OLE objects 15-16, 17-238
cutting and pasting 16-16
panel 17-12
deselecting 16-10
piloted control list selector 17-186, 17-194
duplicating 16-18
polygon 17-16
editing 16-9, 16-29
polyline 17-16
editing properties 16-34
push buttons 17-29
embedded variables in 21-2
buttons 17-37
flipping 16-25
interlocked 17-85
formatting 16-31
latched 17-65 grid 16-6
maintained 17-55 grouping and ungrouping 16-28
momentary 17-45 importing 16-46
multistate 17-74 line properties 16-33
ramp 17-94 methods 18-42
Index ■
I–11
moving 16-15 Help
naming 16-43, 17-24, 18-40 activation 1-5
navigating among 17-27 alarm log viewer 1-5, 11-57
pattern styles 16-32 Code window 24-11
positioning 16-21, 16-22, 16-24 RSView SE Client object model 24-10
with grid 16-6 technical support 1-6
replacing text 16-39 VBA 24-13
reshaping 17-18, 17-45 VBA Object Browser 24-11
Help command A-39
resizing 16-19
Help files
rotating 16-26 creating for displays 18-57
selecting 16-10 Highlight
setting up ActiveX objects 17-28
using the Property Panel 16-35 enabling or disabling 16-71
spatial properties for buttons 17-39
setting up 17-22 trends 17-28, 19-13
stacking 16-21 HMI clients 5-2
testing states 16-42 HMI projects 5-2
HMI servers 5-2
using keys to work with
adding 5-19
See Special keys
alarm monitoring 5-27, 6-11, 11-84, 11-85
using tags and placeholders 17-27
allowing clients to connect 26-11
using with object keys 18-46
attaching to existing 5-21
visibility 17-22
components stop automatically 27-8
Graphs
See Bar graphs computer name 5-24
Grid copying 5-20
in graphic displays 16-7 creating 5-20
in trends 19-45, 19-49 data logging 5-27, 6-11
Grouped objects deleting 5-30
animation 18-65 derived tag processing 5-27, 6-11
Group objects description 5-23, 6-9
setting up in the Property Panel 16-37 event processing 5-27, 6-11
how to use 5-16
H importing projects 5-21
load balancing 5-16
Handshake bit 11-16, 11-36, 11-41 load on demand 26-19
HandshakeOff command A-38 max. number in application 5-17
HandshakeOn command 11-17, A-39
max. number of displays 5-24, 6-10
Handshaking
for Enter key 17-174, 17-175, 17-192, max. number of servers 5-18
17-193 moving files 26-4
resetting 17-176, 17-194 name 5-23, 6-9
switching on 11-17 naming 5-19
Hardware failure number of displays used 5-24, 6-9
See Redundancy On Active macro 5-28
Height animation 18-27 On Shutdown macro 5-28, 6-12
I–12 ■
RSView Supervisory Edition User’s Guide
On Standby macro 5-28 placing in graphic displays 17-8
primary 5-25 settings 17-10
project file 5-24, 6-9 Index numbers 17-25, 18-49
redundancy 5-5, 5-17, 5-21, 5-25 and recipe files 17-222
removing 5-29 changing 18-51
secondary 5-25 checking 18-50
setting up 5-22, 6-8 removing 17-28
showing in Tag Browser 8-12 using for tab sequences 18-49
starting and stopping components 26-19, Indicator tag
27-8 control list selectors 17-174
starting components manually 26-9, 27-3 gauges and graphs 17-143
starting manually 1-5 indicators 17-119
starting when necessary 5-24 piloted control list selectors 17-191
starting with startup components 5-24 push buttons 17-36
startup macro 5-28, 6-12 Indicators 17-117
startup settings 5-24 indicator tag 17-119
status 5-6 list 17-134
stopping components manually 26-9, 27-4 multistate 17-120
stopping manually 1-5, 26-10 importing XML F-3
stopping when not needed 5-24 troubleshooting XML F-5
synchronizing 5-7, 26-12 XML file structure F-4
tags 8-1 symbol 17-128
HMI services Input field commands
starting manually 26-11 Display
stopping manually 26-10 /U parameter A-33
HMI tags Download 17-115, 17-226, A-36
See Tags DownloadAll 17-115, 17-226, A-37
Home area 5-9, 8-20
NextPosition 18-49, A-45
finding tags in 8-13 Position 18-49, A-48
Home key 17-160
Horizontal position animation 18-22
PrevPosition 18-49, A-48
Horizontal slider animation 18-34 SendKeys A-53
Upload 17-115, 17-227, A-59
I UploadAll 17-115, 17-227, A-60
Input fields
Identify command 11-75, A-40 creating
setting up alarms with 11-35, 11-40 numeric 17-107
If command A-41 recipe 17-221
If-then-else expressions 20-23
string 17-107
nesting 20-25
Image graphic object 17-6 downloading values from 17-107, 17-114
Images highlight
adding to Application Explorer 17-11 enabling or disabling 16-71
adding to Image Browser 17-11 question marks in 17-108, 17-114, 17-225
importing 17-11 specifying behavior for 16-71
pasting into graphic displays 17-7 specifying color for 16-70
Index ■
I–13
updating tag values in A-33 location of files 16-49
uploading values to 17-107, 17-114 using for alarm displays 11-10
using at run time 17-113, 17-225 using for trends 19-16, 19-63
using keys with Libraries editor 16-50
Shift-Tab A-48 Limits
special keys 17-113 number of HMI servers 5-16
Tab A-45 tags in graphic displays 8-2
Input focus tags with alarms 8-2
giving to graphic objects 17-27 Line graphic object 17-16
List indicators 17-134
specifying behavior 16-71
Load balancing
Integrated Development Environment
See IDE data servers 5-16, 6-7
Interactive objects HMI servers 5-16
See also Advanced objects Local message displays 17-215
I–14 ■
RSView Supervisory Edition User’s Guide
M Microsoft Visual Basic 11-8
Index ■
I–15
Object Explorer 16-11 OPC-DA data items
opening 16-11 See Tags
using to highlight objects 16-13 OpenRSLogix5000 command 3-14, A-46
Overview of RSView 1-6
using to select objects 16-12
Object keys 23-5
features in brief 1-3
creating 18-46 software programs 1-1
editing 18-62
key list 18-48, 18-62, 18-64 P
precedence among key types 23-7 Page Down key 17-160
Object model Page Up key 17-160
See RSView SE Client object model Pan
Object properties in trends 19-71
editing 16-34 Panel graphic object 17-12
Object Smart Path 18-6, 18-11 Parameter files 16-53, A-34
Objects assigning to graphic displays 16-54
viewing 24-10 running 16-53
Objects that use data 17-26 Parameters editor 16-53
ODBC data logging Passwords 15-22
See Data logging Pattern styles 16-32
ODBC schemas invisible 16-32
See ODBC storage format Pause command A-47
Piloted control list selectors 17-186, 17-194
ODBC storage format
data log files 13-1, 13-4 controlling remotely 17-188
Offsetting differences from control list selectors
Offsetting tag values 8-6 17-186
OLE objects 17-2, 17-238
Enter-key handshaking 17-193
attaching verb animation 18-37 indicator tag 17-191
converting 17-240 value tag 17-191
Placeholders 11-27
securing 15-16
See also Tag placeholders
OLE verb animation 18-37
On Active macro 5-28 in alarm summaries 11-70
On Shutdown macro 5-28, 6-12 in commands 22-2, A-2
On Standby macro 5-28 Planning applications 3-1
On startup macro PlayWave command A-47
PLC network redundancy
See Startup macro
Online help P-1 See Redundancy
On-screen keyboard 16-72, 17-115, A-33 PLC redundancy
OPC See Redundancy
RSView as client Poll rate for DDE C-4
Polygon graphic object 17-16
assigning server to RSView tags 9-18 Polyline graphic object 17-16
OPC communications 7-2 Position command 18-49, A-48
and RSLinx 7-1 Precedence
setting up 7-1 among client, object, and display keys 23-7
syntax 9-19 and the F1 key 23-8
OPC data servers embedded ActiveX objects 23-8
See Data servers embedded OLE objects 23-9
I–16 ■
RSView Supervisory Edition User’s Guide
in macros 20-21 Quick Start 1-6
reserved keys 23-12 VBA code 24-5
PrevPosition command 18-49, A-48
PrevWindow command
PrintDisplay command
A-48
2-23, 16-75, A-49
R
Printers Ramp command A-50
selecting 2-22 Ramp push buttons 17-94
Procedure window Read tag 16-38
See VBA Procedure window ReadMe file P-1
Read-write tag 16-38
Procedures
Recipe commands
defined 24-5
Download 17-115, 17-226, A-36
Programmatic ID
for RSLinx for RSView 7-9 DownloadAll 17-115, 17-226, A-37
Project Explorer RecipeRestore 17-226, A-52
See VBA Project Explorer RecipeSave 17-227, A-52
Project file path Upload 17-115, 17-227, A-59
viewing 5-22, 6-8 UploadAll 17-115, 17-227, A-60
Properties Recipes 17-221
ActiveX 18-40, A-43 and on-screen keyboard 16-72, 17-115
Properties window recipe field 17-221
See VBA Properties window recipe file 17-222
Property Panel 16-34 using at run time 17-223, 17-225
assigning tags to graphic objects 16-38 using index numbers 17-222, 18-49
opening 16-34 Recipes editor 17-222
setting up grouped objects 16-37 Rectangle graphic object 17-15
Redundancy 25-1, 25-15, 25-18
setting up multiple objects 16-37
activation
using to set up graphic objects 16-35
See Redundancy, licensing
using with ActiveX objects 18-40
PullForward command A-50
alarms 11-23, 25-6, 25-7
Push buttons 17-29 commands 25-8
buttons 17-37 computer for secondary server 5-26
indicator tag 17-36 control network 25-2
interlocked 17-85 data log files 25-8
latched 17-65 data servers 5-7, 5-17, 6-2, 6-8, 25-9
maintained 17-55 OPC 7-9
momentary 17-45 RSLinx 7-14
multistate 17-74 derived tags 25-8
ramp 17-94 effect on clients 25-4
value tag 17-35 events 25-8
PushBack command A-50 FactoryTalk Directory 4-3, 4-8, 5-5, 25-5,
25-15, 25-16, 25-17
Q fail-over time for servers 25-4
hardware 25-2
Question marks HMI server status 5-6
in input fields 17-108, 17-114, 17-225 HMI servers 5-5, 5-17, 5-21, 5-25, 25-6,
in trends 19-36 25-10, 25-12
Index ■
I–17
information network 25-2 RSLogix 5000 8-3
I–18 ■
RSView Supervisory Edition User’s Guide
time, date, and number formats 28-1 removing groups 15-8
trends 19-66 removing users 15-8
delta value bar 19-69 securing commands 15-11
loading a template 19-59 securing macros 15-11
overlays 19-72 setting up default access 15-6
printing 19-72 Signature button 17-248
scrolling 19-67 super user account 15-7
setting up 19-60 system administrator 15-7
troubleshooting 19-73 tags 15-17
value bar 19-68 Unspecified_Command 15-12
zoom 19-70 Windows user list 15-2, 15-5
Security codes 15-12
Index ■
I–19
Ctrl String HMI tags
copying objects with 16-16 setting up 9-17
drawing objects with 17-15, 17-16, String input graphic object 17-107, 17-114
17-17 and on-screen keyboard 16-72, 17-115
resizing objects with 16-19 Strings
I–20 ■
RSView Supervisory Edition User’s Guide
T using the [tag] parameter 18-54
using with tag folders 16-52
Tab index 17-25, 18-49 Tag substitution 16-39
removing 17-28 Tag values
Tab key changing 9-20
creating a tab sequence 18-52 displaying in a tag label object 17-204
Tab sequence
downloading 17-107, 17-114
changing index numbers 18-51
logging 8-21, 12-5, 13-34
checking index numbers 18-50
updating 17-114, C-4
creating 18-49, 18-52
continuously in graphic displays
removing objects from 17-28
Tag Browser
17-113
adding folders 8-12 uploading 17-107, 17-114
displaying tag properties 8-17 Tags 8-1, 9-1
Index ■
I–21
basic steps for using 8-7, 8-8 storing values in memory 8-7
creating 8-18, 9-5, 9-20 syntax
data sources 9-18 DDE communications C-4
data types 9-15 OPC communications 9-19
deleting 9-12 using for alarms 8-5
device 9-2 using in editors 2-19
digital 9-16 using in expressions 2-21, 9-3, 18-5, 20-6
duplicating 9-12 with built-in functions 20-13
editing 9-12 using in trends 19-29, 19-38
using with object keys 18-48, 18-62
folders 9-4, 9-6
using with placeholders in commands 22-2,
grouping 9-4 A-2
importing 8-18, 9-21, 9-22, 9-24 Tags editor 9-4, 11-20, 11-31
memory 9-2, 9-20 Technical support P-3, 1-6
Test Display mode 16-9, 18-6, 19-63
naming 9-3
Text
organizing 9-3 importing and exporting
retentive tags 9-2 see Localizing applications
string 9-17 Text graphic object 17-2
Tags editor 9-4 editing 17-6
when to use 8-5 ThisDisplay module 24-4
Thresholds for alarms 11-2, 11-4, 11-32
home area 8-13
Time and date 28-1, B-2
in graphic objects in trends 19-17, 19-23, 19-43, 19-44
updating continuously 17-113 Time and date displays 17-228
limits Toggle command A-58
alarms 8-2 Toolbars 2-5, 16-3, 16-7
in graphic displays 8-2, 16-1 ActiveX toolbox 17-245
logging values 8-21, 12-5 hiding 2-8
max. update rate in displays 16-64 showing 2-8
min. and max. values 8-6 States toolbar 16-42
Toolbox
offline 8-10
ActiveX 17-245
offsetting values 8-6 Tools 1-4
planning database 3-7 Alarm Log Setup 1-5, 11-43
redundancy Alarm Log Viewer 1-5, 11-56
See Redundancy Application Manager 1-4, 5-14, 5-15, 6-6,
references 8-19 6-7, 27-3, 28-2
refreshing list in Tag Browser 8-14 DeskLock 1-4, 15-20
relative references 8-19 Diagnostics Setup 1-5, 12-7
removing a filter 8-18 Diagnostics Viewer 1-5, 12-19, 12-20
scaling values 8-6 RSView SE Service Manager 1-5
securing 8-5, 15-17 Specify FactoryTalk Directory Location
selecting 8-15 1-5, 4-6, 4-7, 4-13
showing descriptions 8-14 Tag Import and Export Wizard 1-5, 9-21,
showing server names 8-12 9-24
I–22 ■
RSView Supervisory Edition User’s Guide
Tooltips pens 19-5, 19-29
adding to ActiveX toolbox 17-246 adding 19-29, 19-30
adding to graphic objects 16-43, 17-24 adding from a data log model 19-30,
Touch animation 18-33
Translating applications
19-33
see Localizing applications attributes 19-32, 19-53
Trends 19-1 deleting 19-32
appearance 19-8, 19-15 editing 19-32
background color 19-15 editing multiple 19-37
changing at run time 19-66 icons 19-6, 19-25
chart background color 19-14
line number 19-32
chart radix 19-22
chart scale 19-4, 19-35, 19-44, 19-46 line style 19-34
chart title 19-17 line type 19-33
charts 19-3, 19-10, 19-11, 19-18 line width 19-33
common properties 17-25 markers 19-7, 19-34
comparing data 19-38, 19-50 masking 19-33
connecting data points 19-23 selecting at run time 19-65
creating planning 3-11
setting up 19-16 plotting a horizontal line 19-38
data buffer 19-20, 19-28 plotting an XY chart 19-11
data source 19-20 plotting historical data 19-20
delta value bar plotting real-time data 19-20
using at run time 19-69 printing 19-72
displaying milliseconds 19-23 radix 19-22
displaying tag values 19-38 running in the background 19-64
editing at run time 19-66 scrolling 19-27, 19-67
filling with data 19-27
at run time 19-67
graphic library 19-63
selecting a data server 19-17
isolated graphing 19-12, 19-48
shading 19-36, 19-38
legends 19-6
current value legend 19-6, 19-24 snapshots 19-21, 19-51
adding as an overlay 19-52
line legend 19-6, 19-25
x-axis legend 19-4 creating 19-51
y-axis legend 19-4 deleting 19-53
multiple pens 19-12 removing as an overlay 19-52
navigating to 17-27 templates 19-56
overlays 19-21, 19-50, 19-51 creating 19-57
adding 19-52 deleting 19-59
at runtime 19-72 loading 19-59
removing 19-52 testing 19-63
pan 19-71 time format 19-22
parts of time span 19-44
Heading 3 19-3 troubleshooting 19-73
Index ■
I–23
updating pen values 19-19 piloted control list selectors 17-191
deadband 19-20 push buttons 17-35
heartbeat 19-20 VBA code 18-39
using at run time 19-9, 19-60, 19-64 planning 3-12
pan 19-71 quick start 24-5
using with ActiveX objects 17-245, 18-45
value bar 19-9, 19-23, 19-68
validating operator input 17-108
using at run time 19-68
VBA documentation 24-13
x-axis 19-4, 19-43 VBA IDE 24-1, 24-2
y-axis 19-4, 19-45 Procedure window 24-4
zoom 19-70 Procedures defined 24-5
Project Explorer 24-4
U Properties Window 24-4
ThisDisplay module 24-4
Undefine command A-10, A-59
Unicode format
using 24-2
for XML files F-2 using the IDE 24-2
Upload command 17-115, 17-227, A-59 VBA Integrated Development Environment
UploadAll command 17-115, 17-227, A-60 See VBA IDE
User account commands Vertical position animation 18-23
Login 15-13, 15-21, A-44 Vertical slider animation 18-36
Viewing objects 24-10
Logout 15-13, 15-21, A-45
Visibility animation 11-10, 18-13
User accounts 15-5
Visual Basic
adding 15-7 See Microsoft Visual Basic
administrator 15-7
assigning security codes 15-10
login and logout macros 15-10 W
maintaining in Windows 15-2, 15-5 Wallpaper
removing 15-8 converting graphic objects to 16-45
tracking system usage by 12-19 Wedge graphic object 17-17
User Accounts editor 15-6 Width animation 18-25
UTF-16 format Wildcards 9-3, 9-6
for XML files F-2 and commands A-2
UTF-8 format using to select tags 8-17, 11-69
for XML files F-2 using to suppress alarm monitoring 11-82
Utilities 1-5 Windows
See also Tools security 15-2, 15-5, 15-22
Windows applications A-25
Windows CE
V messages for FactoryTalk Diagnostics
Value table 8-6
12-15
updating C-4 Windows workgroups 3-2, 4-2, 5-3, 15-7,
Value tag 26-16
Workgroups in Windows 3-2, 4-2, 5-3, 15-7,
control list selectors 17-174 26-16
local message displays 17-215 Workspace 2-5
local messages 17-232, 17-234 Write tag 16-38
I–24 ■
RSView Supervisory Edition User’s Guide
X
XML F-1
importing into graphic displays F-1
saving F-2
testing for well-formed F-2
well-formed F-2
Z
Zoom 16-5
in trends 19-70
Index ■
I–25