VIEWSE-UM005E-EN-E–July 2007 4/24/07 11:37 AM Page 1

View Site Edition

USER’S GUIDE VOLUME 2

PUBLICATION VIEWSE-UM005E-EN-E–August 2007
Supersedes Publication VIEWSE-UM005D-EN-E
 Contacting Rockwell Customer Support Telephone — 1-440-646-3434
Online support — http://support.rockwellautomation.com

Copyright Notice © 2007 Rockwell Automation Technologies Inc. All rights reserved. Printed in USA.
This document and any accompanying Rockwell Software products are copyrighted by Rockwell
Automation Technologies Inc. Any reproduction and/or distribution without prior written consent
from Rockwell Automation Technologies Inc. is strictly prohibited. Please refer to the license
agreement for details.

Trademark Notices Allen-Bradley, ControlLogix, FactoryTalk, PLC-2, PLC-3, PLC-5, Rockwell Automation, Rockwell
Software, RSLinx, RSView, the Rockwell Software logo, and VersaView are registered trademarks of
Rockwell Automation, Inc.
The following logos and products are trademarks of Rockwell Automation, Inc.:

RSMACC, RSLogix, Data Highway Plus, DH+, RSView, FactoryTalk View, RSView Studio,
FactoryTalk View Studio, PanelBuilder, PanelView, RSView Machine Edition, RSView ME Station,
and WINtelligent.
FactoryTalk Activation, FactoryTalk Administration Console, FactoryTalk Alarms and Events,
FactoryTalk Automation Platform, FactoryTalk Services Platform, FactoryTalk Diagnostics,
FactoryTalk Directory, FactoryTalk Live Data, RSAssetSecurity, and FactoryTalk Security.
PanelView, RSLinx Classic, RSLinx Enterprise, SLC 5, and SLC 500

Other Trademarks ActiveX, Microsoft, Microsoft Access, SQL Server, Visual Basic, Visual C++, Visual SourceSafe,
Windows, Windows ME, Windows NT, Windows 2000, Windows Server 2003, and Windows XP are
either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
ControlNet is a registered trademark of ControlNet International.
DeviceNet is a trademark of the Open DeviceNet Vendor Association Inc. (ODVA)
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
OLE for Process Control is a registered trademark of the OPC Foundation.
Oracle, SQL*Net, and SQL*Plus are registered trademarks of Oracle Corporation.
All other trademarks are the property of their respective holders and are hereby acknowledged.

Warranty This product is warranted in accord with the product license. The product’s performance may be
affected by system configuration, the application being performed, operator control, maintenance,
and other related factors. Rockwell Automation is not responsible for these intervening factors. The
instructions in this document do not cover all the details or variations in the equipment, procedure, or
process described, nor do they provide directions for meeting every possible contingency during
installation, operation, or maintenance. This product’s implementation may vary among users.
This document is current as of the time of release of the product; however, the accompanying
software may have changed since the release. Rockwell Automation, Inc. reserves the right to change
any information contained in this document or the software at anytime without prior notice. It is your
responsibility to obtain the most current information available from Rockwell when installing or
using this product.

Doc ID VIEWSE-UM005E-EN-E
August 2007

2
Contents

Preface
About RSView Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
About the FactoryTalk View SE documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
What’s in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
Finding information about FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Try the User’s Guide and Help first . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Finding information on the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Contacting Rockwell Automation Technical Support . . . . . . . . . . . . . . . . . . . . P-4

1 • Getting started with FactoryTalk View SE

Welcome to FactoryTalk View Site Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
About RSView Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
About FactoryTalk systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
FactoryTalk Services Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Finding more information about FactoryTalk services . . . . . . . . . . . . . . . . . . . . 1-3
FactoryTalk View Site Edition software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
FactoryTalk View tools and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
FactoryTalk View SE features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Quick start: setting up the software you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Step 1: Plan the layout of the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Step 2: Install the FactoryTalk Services Platform . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Step 3: Install FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Step 4: Install the communications software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Step 5: Install the necessary activation keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Step 6: Set up the FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Running FactoryTalk View SE without activation . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Exploring the Samples Water application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Creating a new FactoryTalk View SE application . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Step 1: Create the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Step 2: Create a graphic display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Step 3: Test run the application in FactoryTalk View SE Client . . . . . . . . . . . . 1-15

2 • Exploring FactoryTalk View Studio

About FactoryTalk View Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Opening an application in FactoryTalk View Studio. . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Gaining access to the HMI Projects folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

i
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Opening the Samples Water application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Parts of the FactoryTalk View Studio main window . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Menu bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Application tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Communications tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Diagnostics List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Workbook mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Showing and hiding items in the main window . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Working in the Explorer window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Moving the Explorer window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Opening and closing folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Opening component editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Creating and modifying components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Adding components to an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
About component names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Deleting, removing, and renaming components . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Techniques for working in editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Gaining quick access to common actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Browsing lists and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Supplying tag names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Selecting and building commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Building expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Printing from FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Selecting a printer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Printing at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

3 • Planning an application
Understanding the process you are automating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Planning the layout of the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Choose a Windows domain or workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Determine which computers you’ll need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Planning communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Determine how to access data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Planning how to monitor and control alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Planning an alarm monitoring and control system . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Advantages of using Alarms and Events services . . . . . . . . . . . . . . . . . . . . . . . . 3-6
About traditional HMI tag alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

ii
 • • • • •
CONTENTS

Deciding when to use HMI tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Design the HMI tag database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Designing a dependable control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Plan how to secure the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Plan to use built-in system availability features . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Setting up the run-time application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Develop a hierarchy of graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Create templates to ensure consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Apply visual design principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Plan how to use trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Plan run-time language switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Designing a system that is easy to deploy and maintain . . . . . . . . . . . . . . . . . . . . . . 3-13
Allow for multiple users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Integrating with other applications and customizing the system . . . . . . . . . . . . . . . . 3-14

4 • Setting up FactoryTalk Directory

About FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
FactoryTalk Directory in a networked system . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
FactoryTalk Directory in a FactoryTalk View SE application. . . . . . . . . . . . . . . 4-3
About local applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Running network applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Specifying the location of the FactoryTalk Directory server. . . . . . . . . . . . . . . . . . . . 4-4
Setting up FactoryTalk Directory for a local application . . . . . . . . . . . . . . . . . . . 4-7
Restoring FactoryTalk Directory when deploying an application . . . . . . . . . . . . . . . . 4-7
What happens if the Network Directory server is unavailable. . . . . . . . . . . . . . . . . . . 4-8
Monitoring Network Directory status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

5 • Setting up security
About FactoryTalk Security services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
About the FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Finding more information about FactoryTalk Security . . . . . . . . . . . . . . . . . . . . 5-2
Gaining initial access to a FactoryTalk system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Logging users on to and off from FactoryTalk View SE. . . . . . . . . . . . . . . . . . . . . . . 5-4
Logging on to the FactoryTalk Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Logging on to FactoryTalk View Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Logging on to a FactoryTalk View SE Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Deciding how to secure a FactoryTalk View SE application . . . . . . . . . . . . . . . . . . . 5-8
Securing FactoryTalk View SE applications at run time . . . . . . . . . . . . . . . . . . . 5-9
Securing FactoryTalk system resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Setting up FactoryTalk accounts in FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . 5-11
Setting up accounts in the Runtime Security editor . . . . . . . . . . . . . . . . . . . . . . 5-11

iii
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Removing All Users from the Runtime Security list . . . . . . . . . . . . . . . . . . . . . 5-14

Specifying login and logout macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Removing Runtime Security accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Setting up run-time security for HMI project components . . . . . . . . . . . . . . . . . . . . 5-16
Assigning security codes to commands and macros . . . . . . . . . . . . . . . . . . . . . 5-17
Assigning security codes to graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Assigning security codes to OLE objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Assigning security codes to HMI tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Other ways to control run-time access to an application . . . . . . . . . . . . . . . . . . . . . . 5-20
Lock operators into the run-time environment . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Use the signature button to control user actions. . . . . . . . . . . . . . . . . . . . . . . . . 5-21
About FactoryTalk Security accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
About the All Users account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Specifying which users can set up security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Choosing the types of accounts to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Organizing users in groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Setting up user and computer accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Creating computer accounts for a network application . . . . . . . . . . . . . . . . . . . 5-26
Setting up system-wide policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Setting up security for FactoryTalk system resources . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Modifying FactoryTalk Security settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Specifying which actions users can perform . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Organizing actions into groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Understanding inherited permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Breaking the chain of inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Using explicit permissions to override inheritance . . . . . . . . . . . . . . . . . . . . . . 5-34
Performing secured tasks in FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

6 • Working with network applications

About FactoryTalk View Site Edition network applications . . . . . . . . . . . . . . . . . . . . 6-1
Parts of a network application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
About FactoryTalk systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Finding more information about FactoryTalk services . . . . . . . . . . . . . . . . . . . . 6-3
Key network application concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
FactoryTalk Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
FactoryTalk Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
HMI servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
HMI projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
HMI clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Absolute and relative references. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

iv
 • • • • •
CONTENTS

System availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Language switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Creating network applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Adding areas and servers to a network application . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Adding and deleting areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Adding an HMI server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Adding a data server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Adding a Tag Alarm and Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Deciding when to use multiple servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Running multiple HMI servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Setting up HMI server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Changing the name of the host computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Specifying how the server starts up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Setting up HMI server redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Selecting startup and shutdown components . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Starting and stopping an HMI server’s components . . . . . . . . . . . . . . . . . . . . . 6-18
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Monitoring the status of an HMI server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Deleting HMI servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Deleting HMI server project files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Renaming, deleting, and backing up network applications . . . . . . . . . . . . . . . . . . . . 6-21
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Backing up and restoring network applications . . . . . . . . . . . . . . . . . . . . . . . . . 6-22

7 • Working with local applications

About FactoryTalk View SE local applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Parts of a local application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
About FactoryTalk systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Finding more information about FactoryTalk services . . . . . . . . . . . . . . . . . . . . 7-3
Key local application concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
FactoryTalk Local Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
FactoryTalk Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
HMI servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
HMI projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
HMI clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Relative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Language switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Creating local applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

v
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Importing a project into a new application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Adding servers to a local application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Adding a Tag Alarm and Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Setting up HMI server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Selecting startup and shutdown components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Monitoring the status of an HMI server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Renaming, deleting, copying, and backing up local applications . . . . . . . . . . . . . . . 7-10
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Copying, backing up, and restoring local applications. . . . . . . . . . . . . . . . . . . . 7-11

8 • Setting up communications
About data servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Overview of data server communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Using multiple data servers in an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Setting up communications in FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Adding RSLinx Enterprise data servers to an application . . . . . . . . . . . . . . . . . . . . . . 8-5
Setting up general properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Setting up RSLinx Enterprise data server redundancy . . . . . . . . . . . . . . . . . . . . . 8-7
Setting up support for alarms and events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Deleting an RSLinx Enterprise data server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Setting up communications for RSLinx Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
About the Primary and Secondary tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Adding OPC data servers to an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Setting up general properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Setting up OPC data server redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Setting up advanced properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Deleting an OPC data server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

9 • Working with tags

About data server tags and HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Using direct referencing to eliminate duplication . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Using the extended capabilities of HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Using tag data in a FactoryTalk View SE application . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Setting up data server tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Setting up HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Specifying tag names where tag data is needed . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Logging tag values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

vi
 • • • • •
CONTENTS

Observing tag-related limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

About tag references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Absolute references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Relative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
The home area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Parts of the Tag Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Viewing tags in folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Showing server names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Finding tags in the home area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Searching for and selecting tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Selecting folders instead of individual tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Displaying a tag’s properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Filtering tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Creating, modifying, and importing HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Browsing for offline tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Browsing for offline tags from RSLinx Enterprise . . . . . . . . . . . . . . . . . . . . . . 9-13
Browsing for offline tags from RSLinx Classic . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Browsing for offline tags from other OPC servers . . . . . . . . . . . . . . . . . . . . . . 9-13

10 • Creating HMI tags

About HMI tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
HMI tag types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Data sources for HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Organizing HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Naming HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Grouping HMI tags in folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Viewing tag statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Parts of the Tags editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Accept and Discard buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Form and spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Query box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Folder hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Creating, modifying, and deleting tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Selecting a data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Getting HMI tag data from a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Getting HMI tag data from memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Creating HMI tags without using the Tags editor. . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Creating tags in a third-party application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Creating tags in other FactoryTalk View editors . . . . . . . . . . . . . . . . . . . . . . . 10-10
Importing and exporting tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Importing tags from a PLC database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10

vii
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Defining alarm conditions for HMI tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11

Modifying HMI tag and alarm properties at run time. . . . . . . . . . . . . . . . . . . . . . . 10-12

11 • Setting up HMI tag alarms

About HMI tag alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
HMI tag alarm features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
About FactoryTalk Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Key HMI tag alarms concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Alarm thresholds for analog tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Alarm states for digital tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Alarm severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Alarm messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Alarm log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
HMI tag alarm displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Alarm acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Alarm suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Alarm functions in expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Acknowledge bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Handshake bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Summary of steps for setting up HMI tag alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Setting up general HMI tag alarm behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
Setting up alarm monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Setting up alarm severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
Setting up alarm messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
Setting up alarm conditions for HMI tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Setting up alarms for HMI analog tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Setting up alarms for HMI digital tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Modifying HMI tag and alarm properties at run time . . . . . . . . . . . . . . . . . . . 11-20
About FactoryTalk View SE alarm events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
Setting up HMI tag alarm logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23
Specifying where log files are stored or printed. . . . . . . . . . . . . . . . . . . . . . . . 11-24
Specifying when log files are created and deleted . . . . . . . . . . . . . . . . . . . . . . 11-24
Setting up periodic logging to a central ODBC database . . . . . . . . . . . . . . . . . 11-25
Exporting alarm log files manually to ODBC format . . . . . . . . . . . . . . . . . . 11-25
Adding remarks to the alarm log file at run time . . . . . . . . . . . . . . . . . . . . . . . 11-26
Viewing HMI tag alarm log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
Alarm log file names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
Suppressing alarm logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-29
Suppressing alarm printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-29
Creating an HMI tag alarm summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
The parts of an HMI tag alarm summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31

viii
 • • • • •
CONTENTS

Inserting headings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31

Choosing fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Choosing colors and blink styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Selecting buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-33
Choosing the data to display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-34
Sorting and filtering at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
Using tag placeholders to specify alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
Replacing tag placeholders at run time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-36
Running commands or custom programs for selected alarms . . . . . . . . . . . . . . . . . 11-37
Using the Execute button to run commands or programs . . . . . . . . . . . . . . . . 11-37
Using the Identify button to run commands or programs. . . . . . . . . . . . . . . . . 11-39
Starting and stopping HMI tag alarm monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 11-39
Ways to start HMI tag alarm monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-39
Ways to stop HMI tag alarm monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-40

12 • Setting up FactoryTalk alarms

About FactoryTalk Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Advantages in using Alarms and Events services . . . . . . . . . . . . . . . . . . . . . . . 12-2
About traditional HMI tag alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Finding more information about Alarms and Events . . . . . . . . . . . . . . . . . . . . . 12-4
Key FactoryTalk Alarms and Events concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Alarms and events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Alarm servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Level alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Deviation alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Digital alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
FactoryTalk alarm and event displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Alarm priority and severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Alarm class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Alarm states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
Alarm tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
Alarm status tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Alarm messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Alarm audit, diagnostic, and history logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Summary of basic steps for setting up FactoryTalk alarms . . . . . . . . . . . . . . . . . . . 12-15
Setting up system-wide alarm and event policies . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Securing access to FactoryTalk alarm information . . . . . . . . . . . . . . . . . . . . . 12-17
Working with Rockwell Automation Device Servers . . . . . . . . . . . . . . . . . . . . . . . 12-18
Setting up support for Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Specifying a device-based alarm source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20
Viewing device-based alarm information at run time . . . . . . . . . . . . . . . . . . . 12-20

ix
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Working with Tag Alarm and Event Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21

Setting up alarm priorities and history logging . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Viewing tag-based alarm information at run time . . . . . . . . . . . . . . . . . . . . . . 12-23
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23
Setting up FactoryTalk tag-based alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Creating tag-based digital alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Creating tag-based level alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
Creating tag-based deviation alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
Viewing all tag-based alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
Setting up status tags for tag-based alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
Setting up tag-based alarm messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
Adding variables to alarm messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
Specifying tag update rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Setting up alarm and event history logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32
Defining an alarm and event log database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32
Enabling alarm and event history logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
Setting up alarm and event displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34
About the Alarm and Event graphic library . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34
Setting up an alarm and event summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34
Setting up an alarm and event banner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
About the alarm and event banner at run time . . . . . . . . . . . . . . . . . . . . . . . . . 12-38
Using an alarm summary to monitor and respond to alarms . . . . . . . . . . . . . . . . . . 12-39
The parts of an alarm and event summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-40
Acknowledging alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-41
Resetting latched digital alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43
Suppressing and disabling alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43
Unsuppressing and enabling alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-44
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-44
Working with alarm sources in the Alarm Status Explorer . . . . . . . . . . . . . . . . . . . 12-45
The parts of an alarm status explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-46
Viewing alarm details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
Unsuppressing and suppressing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
Disabling and enabling alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-49
Viewing alarm and event history logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-50
The parts of an alarm and event log viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-50
Using tags to interact with alarms or obtain their status . . . . . . . . . . . . . . . . . . . . . 12-52
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-54
Using FactoryTalk alarm functions in expressions . . . . . . . . . . . . . . . . . . . . . . . . . 12-54
Retrieving information about the severity of alarms . . . . . . . . . . . . . . . . . . . . 12-54
Retrieving information about the number of alarms . . . . . . . . . . . . . . . . . . . . 12-55
Specifying the FactoryTalk alarm source in an expression . . . . . . . . . . . . . . . 12-56

x
 • • • • •
CONTENTS

What happens if the alarm source becomes unavailable . . . . . . . . . . . . . . . . . 12-58

Importing and exporting alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-59
About import and export formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-60
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-60

13 • Setting up language switching

About language switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Text strings that allow language switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Text strings that do not allow language switching . . . . . . . . . . . . . . . . . . . . . . . 13-2
Summary of steps for setting up language switching. . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Setting up font support for Windows languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Installing additional Windows languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Selecting a language for a new FactoryTalk View application . . . . . . . . . . . . . . . . . 13-6
About the current application language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Adding languages to an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Setting up a default application language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Displaying undefined text strings in the default language . . . . . . . . . . . . . . . . . 13-9
Exporting application text strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Troubleshooting export problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
Export file formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
Working with text strings exported to an Excel spreadsheet . . . . . . . . . . . . . . . . . . 13-13
Spreadsheet format and content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
Maintaining the format of the spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
Modifying or translating text strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Working with duplicate text strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Working with strings exported to a Unicode text file . . . . . . . . . . . . . . . . . . . . . . . 13-16
File name and format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Opening a Unicode text file in Microsoft Excel. . . . . . . . . . . . . . . . . . . . . . . . 13-17
Saving a Unicode text file in Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
Differences in format for Unicode files saved in Excel . . . . . . . . . . . . . . . . . . 13-18
Saving a Unicode text file in Notepad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
File schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Working with pairs of double quotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Working with backslashes and new-line characters . . . . . . . . . . . . . . . . . . . . . 13-19
Importing translated or modified text strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
Troubleshooting import problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
Setting up run-time language switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Using the Language command to switch languages. . . . . . . . . . . . . . . . . . . . . 13-26
Support for multiple languages in the graphic libraries . . . . . . . . . . . . . . . . . . . . . . 13-26

xi
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Language support in new graphic libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26

Using the graphic libraries in a multi-language application. . . . . . . . . . . . . . . 13-27

14 • Setting up FactoryTalk system availability

FactoryTalk features that maximize system availability . . . . . . . . . . . . . . . . . . . . . . 14-1
Finding more information about system availability . . . . . . . . . . . . . . . . . . . . . 14-2
Monitoring the status of application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
States for non-redundant and redundant servers. . . . . . . . . . . . . . . . . . . . . . . . . 14-4
States for redundant servers only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
What happens if a non-redundant HMI server fails . . . . . . . . . . . . . . . . . . . . . . 14-6
Monitoring the status of the Network Directory server . . . . . . . . . . . . . . . . . . . . . . . 14-7
What happens if the Network Directory server is unavailable . . . . . . . . . . . . . . 14-8
Redundancy as part of a system availability strategy . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Planning the layout of a redundant system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
About FactoryTalk View SE system limits . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
Activating FactoryTalk View SE in a redundant system . . . . . . . . . . . . . . . . . 14-11
Setting up redundant servers in FactoryTalk View SE. . . . . . . . . . . . . . . . . . . 14-12
Setting up a redundant HMI server pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Specify the Network Directory on the secondary computer. . . . . . . . . . . . . . . 14-13
Copy HMI project files to the secondary computer . . . . . . . . . . . . . . . . . . . . . 14-14
Set up HMI server redundancy options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Replicate changes to the secondary HMI server . . . . . . . . . . . . . . . . . . . . . . . 14-16
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
Determining the Active HMI server in a redundant pair . . . . . . . . . . . . . . . . . . . . . 14-17
When an HMI server is ready to be active or standby . . . . . . . . . . . . . . . . . . . 14-17
Specifying On Active and On Standby macros . . . . . . . . . . . . . . . . . . . . . . . . 14-18
What happens if both servers become active . . . . . . . . . . . . . . . . . . . . . . . . . . 14-19
Switching the Active and Standby servers manually . . . . . . . . . . . . . . . . . . . . . . . . 14-20
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
What happens when the primary HMI server fails . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Failing over to the Standby secondary server. . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Switching back to primary, or staying with the Active server . . . . . . . . . . . . . 14-22
Notifying clients when switching back to the primary. . . . . . . . . . . . . . . . . . . 14-22
Modifying HMI tag and alarm properties at run time . . . . . . . . . . . . . . . . . . . . . . . 14-23
Modifying HMI tag properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23
Modifying HMI tag alarm properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-26
Managing HMI data in an online redundant system . . . . . . . . . . . . . . . . . . . . . . . . 14-29
Synchronize time clocks on redundant computers . . . . . . . . . . . . . . . . . . . . . . 14-29
Centralize storage of diagnostic and alarm log data. . . . . . . . . . . . . . . . . . . . . 14-30
Determine which server will run events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-30
Synchronize derived tags and data log files . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-31

xii
 • • • • •
CONTENTS

Monitoring network client and server connections . . . . . . . . . . . . . . . . . . . . . . . . . 14-31

About network glitches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-32

15 • Logging system activity

About FactoryTalk Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Summary of steps for setting up Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Finding more information about FactoryTalk Diagnostics . . . . . . . . . . . . . . . . 15-2
Key FactoryTalk Diagnostics concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Message routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Message categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Setting up FactoryTalk Diagnostics in FactoryTalk View. . . . . . . . . . . . . . . . . . . . . 15-4
Setting up message routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Logging to a central database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Tracking system events in the Diagnostics List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Working with the Diagnostics List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Viewing messages in the Diagnostics List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Viewing FactoryTalk Diagnostics logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9

16 • Using the FactoryTalk View SE Client object model

and display code
Customizing applications using VBA with FactoryTalk View . . . . . . . . . . . . . . . . . 16-1
Summary of basic steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
About procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
How VBA code runs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Parts of the VBA integrated development environment. . . . . . . . . . . . . . . . . . . . . 16-3
FactoryTalk View SE Client object model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Viewing the objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Finding information about FactoryTalk View SE Client objects. . . . . . . . . . . . . . . . 16-8
Finding information about VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8

17 • Deploying network applications

About deploying network applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Summary of steps to deploy a network application . . . . . . . . . . . . . . . . . . . . . . 17-2
Backing up a network application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Backing up FactoryTalk System information. . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Setting up the FactoryTalk Network Directory server . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Specifying the location of FactoryTalk Network Directory . . . . . . . . . . . . . . . . . . . 17-6
Moving HMI project files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

xiii
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Copying an HMI server that is not running . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7

Copying an HMI server while it is running . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Restoring a network application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Restoring FactoryTalk System information . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Changing HMI server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Updating the name of the HMI server’s host computer . . . . . . . . . . . . . . . . . . 17-11
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
How HMI server components start and stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Starting and stopping HMI server components manually . . . . . . . . . . . . . . . . 17-12
Stopping and starting HMI services manually . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Synchronizing redundant HMI servers and projects . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Moving data server files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Moving RSLinx Enterprise files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Moving RSLinx Classic files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Changing data server properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Setting up the FactoryTalk View SE Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Creating a new client configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Copying client setup files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Running the FactoryTalk View SE Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Running multiple FactoryTalk View SE Clients . . . . . . . . . . . . . . . . . . . . . . . 17-18
Logging users on to the FactoryTalk View SE Client . . . . . . . . . . . . . . . . . . . 17-19
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Locking operators into the run-time environment . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Administering deployed applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Monitoring disk space on HMI servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21

18 • Deploying local applications

About deploying local applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Summary of steps to deploy a local application . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Moving a local application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Backing up and restoring FactoryTalk System information. . . . . . . . . . . . . . . . 18-4
Changing HMI server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
How HMI server components start and stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Starting and stopping HMI server components manually . . . . . . . . . . . . . . . . . 18-5
Moving data server files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Changing data server properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Setting up the FactoryTalk View SE Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7

xiv
 • • • • •
CONTENTS

Creating a new client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7

Running the FactoryTalk View SE Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Logging users on to the FactoryTalk View SE Client . . . . . . . . . . . . . . . . . . . . 18-8
About FactoryTalk Security permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Locking operators into the run-time environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Administering deployed applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9

19 • Creating graphic displays

About graphic displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Importing and exporting graphic display XML files . . . . . . . . . . . . . . . . . . . . . 19-2
About global object displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Parts of the Graphics editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Viewing display contents in the Object Explorer . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Viewing object properties in the Property Panel . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Techniques for working in graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Zooming in and out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Setting up a display grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Using the toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Selecting objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Using shortcut menus to perform actions quickly . . . . . . . . . . . . . . . . . . . . . . . 19-8
Techniques for working with graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Duplicating objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Resizing and reshaping objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Arranging objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
Flipping objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
Rotating objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Grouping objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Ungrouping objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16
Modifying grouped objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
Applying colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
Applying pattern styles and colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18
Changing line properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19
Naming graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19
Assigning tags and expressions to objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20
Adding tooltips to graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21
Using tag substitution to replace text strings . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21
Creating a background for a display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-22
Testing graphic displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-23
Testing the appearance of objects in different states . . . . . . . . . . . . . . . . . . . . 19-23
Creating and working with global object displays . . . . . . . . . . . . . . . . . . . . . . . . . . 19-24
Creating global object displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-24

xv
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Adding standard displays that contain reference objects . . . . . . . . . . . . . . . . . 19-25

About global object displays at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25
Adding process faceplates to an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Working with faceplates in the Graphics editor . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Using objects from the graphic libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Location of library files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Importing graphic files from third-party applications . . . . . . . . . . . . . . . . . . . . . . . 19-27
Using bitmaps in a FactoryTalk View application . . . . . . . . . . . . . . . . . . . . . . 19-28
When to use a bitmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Using placeholders to specify tag values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Creating a tag placeholder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-30
Replacing tag placeholders using parameter files . . . . . . . . . . . . . . . . . . . . . . 19-30
Replacing tag placeholders using the Display command . . . . . . . . . . . . . . . . . 19-31
Setting up tag placeholders for global objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32
Defining tag placeholders for use in reference objects. . . . . . . . . . . . . . . . . . . 19-32
Modifying global objects that use tag placeholders . . . . . . . . . . . . . . . . . . . . . 19-35
Setting up the appearance and behavior of a graphic display . . . . . . . . . . . . . . . . . 19-35
Setting up the properties of a graphic display . . . . . . . . . . . . . . . . . . . . . . . . . 19-35
Setting up the run-time behavior of a graphic display . . . . . . . . . . . . . . . . . . . 19-40
Setting up displays to open more quickly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-43
Changing the default display settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-44
Docking displays to the FactoryTalk View SE Client window . . . . . . . . . . . . . . . . 19-45
Display command parameters for docking displays. . . . . . . . . . . . . . . . . . . . . 19-45
About the appearance and behavior of docked displays. . . . . . . . . . . . . . . . . . 19-46
Closing docked displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-47
Printing displays at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-48

20 • Creating graphic objects

Types of graphic objects in FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
About global objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Setting up the properties of graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Setting up properties common to all objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Creating the different types of drawing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Drawing a rectangle or square . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Drawing a rounded rectangle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Drawing a polyline or polygon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Drawing an ellipse or circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Drawing an arc or wedge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Changing the properties of drawing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Creating text objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
Creating a panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8

xvi
 • • • • •
CONTENTS

Adding images into graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8

Placing images in graphic displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
Adding images to an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
Importing images into graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Pasting images into graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Techniques for working with objects that use data . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Specifying tag names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Determining which objects have input focus . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
Using the keyboard to select objects that can take focus . . . . . . . . . . . . . . . . . 20-10
Removing objects from the tab sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-11
Creating the different types of push buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-11
Creating button push buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-12
Creating momentary push buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
Creating maintained push buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-14
Creating latched push buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
Creating multistate push buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
About the run-time error state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
Creating interlocked push buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
Creating ramp push buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
Creating the different types of data display and input objects . . . . . . . . . . . . . . . . . 20-19
Using input objects to retrieve and send data . . . . . . . . . . . . . . . . . . . . . . . . . . 20-20
Shortcut keys for retrieving and sending data . . . . . . . . . . . . . . . . . . . . . . . . . 20-22
FactoryTalk View commands for retrieving and sending data. . . . . . . . . . . . . 20-23
Parts of the on-screen keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Creating numeric and string display objects. . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
Creating numeric and string input objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Creating the different types of indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Setting up states for indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Setting up connections for indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
Creating multistate indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
Creating symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
Creating list indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Creating the different types of gauges and graphs . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Using gauges to show limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Using graphs to compare values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-28
Creating gauges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Creating bar graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Creating scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Using key objects to simulate keyboard functions. . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Creating the different types of key objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-30
Using the same set of keys with different graphic objects . . . . . . . . . . . . . . . . 20-31
Creating the different types of advanced objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-31

xvii
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Creating arrows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32

Creating tag labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32
Creating time and date displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-33
Creating display list selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-33
Providing operator instructions in local message displays . . . . . . . . . . . . . . . . . . . 20-34
Setting up local messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-34
Creating local message displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-35
Creating and restoring recipes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-36
Creating a recipe object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-36
Restoring and saving recipe values at run time . . . . . . . . . . . . . . . . . . . . . . . . 20-36
Creating control list selectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-39
Selecting states in a control list selector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-39
Using keys to scroll the list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-39
Setting the Value tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-40
Creating control list selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-40
Creating piloted control list selectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-41
Selecting states in a piloted control list selector. . . . . . . . . . . . . . . . . . . . . . . . 20-41
Using keys to scroll the list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-42
Setting the Value tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-43
Creating piloted control selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-44
Specifying the text and value for each state . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-44
Setting up connections for a piloted control list selector . . . . . . . . . . . . . . . . . 20-45
Creating the Alarm and Event objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-46
Creating global objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-46
Creating reference objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-47
Using placeholders to specify values for global objects. . . . . . . . . . . . . . . . . . 20-48
Adding global objects into the graphic libraries. . . . . . . . . . . . . . . . . . . . . . . . 20-48
Setting up the link properties of reference objects. . . . . . . . . . . . . . . . . . . . . . . . . . 20-48
LinkAnimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-49
LinkConnections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-50
LinkSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-50
LinkBaseObject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-50
Link properties of grouped reference objects . . . . . . . . . . . . . . . . . . . . . . . . . . 20-51
Breaking links between reference and base objects . . . . . . . . . . . . . . . . . . . . . 20-51
Working with OLE objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-51
Creating OLE objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-52
Converting OLE objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-52
Working with ActiveX objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-53
Attributes of ActiveX objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-53
Creating ActiveX objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-54
Setting up ActiveX objects to interact with FactoryTalk View . . . . . . . . . . . . 20-54
Setting up tools in the ActiveX toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-54

xviii
 • • • • •
CONTENTS

Deploying ActiveX components automatically at run time . . . . . . . . . . . . . . . 20-55

Using electronic signatures to authorize run-time changes . . . . . . . . . . . . . . . . . . . 20-55
Securing tag writes, commands, and downloads . . . . . . . . . . . . . . . . . . . . . . . 20-56
Creating signature buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-57
Securing objects in graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-57
Tracking changes using FactoryTalk Diagnostics . . . . . . . . . . . . . . . . . . . . . . 20-58

21 • Animating graphic objects

About animation in FactoryTalk View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Setting up animation for FactoryTalk View graphic objects . . . . . . . . . . . . . . . . . . . 21-2
Linking animation to tag values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Linking animation to expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Linking animation to actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4
Determining start and end points for a range of motion. . . . . . . . . . . . . . . . . . . 21-4
Defining the range of motion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4
Applying animation to object groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Testing animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
Viewing the animation applied to objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
Copying or duplicating objects with animation . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
About global objects and animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
Creating effects using the different types of animation . . . . . . . . . . . . . . . . . . . . . . . 21-7
Showing and hiding objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
Changing an object’s color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
Changing the level of fill in an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-11
Moving an object horizontally in a display . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-11
Moving an object vertically in a display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-11
Rotating objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-11
Changing the width of an object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
Changing the height of an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
Setting up touch zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
Creating a horizontal slider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
Creating a vertical slider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-14
Animating OLE verbs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-14
Using index numbers to navigate to objects in a display . . . . . . . . . . . . . . . . . . . . . 21-14
Checking an object’s index number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-15
How tab index numbers work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-16
Creating a tab sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-16
Changing index numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-17
Associating objects and displays with keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-17
Setting up object keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-17
Setting up display keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19

xix
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Viewing the key list at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19

Setting up object-specific commands using keys . . . . . . . . . . . . . . . . . . . . . . . 21-20
Animating ActiveX objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-22
Connecting tags to an ActiveX object’s properties . . . . . . . . . . . . . . . . . . . . . 21-23
Connecting tags to an object’s methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-25
Connecting tags to an ActiveX object’s events . . . . . . . . . . . . . . . . . . . . . . . . 21-25

22 • Setting up navigation
Designing a display hierarchy for an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Setting up ways to move among displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Using commands to open, close, and switch displays . . . . . . . . . . . . . . . . . . . . 22-2
Choosing display types with navigation in mind . . . . . . . . . . . . . . . . . . . . . . . . 22-5
Reducing display call-up time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6
Setting up keys to run FactoryTalk View commands . . . . . . . . . . . . . . . . . . . . . . . . 22-6
General rules governing precedence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
Precedence and the F1 key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
Precedence and embedded ActiveX objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
Precedence and embedded OLE objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
Keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
Creating client keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
Running client key components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-11

23 • Creating expressions
About expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1
Where you can use expressions in FactoryTalk View SE . . . . . . . . . . . . . . . . . 23-1
Working in the Expression editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Expression components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3
Checking the syntax of an expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4
Cutting, copying, and pasting expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4
Formatting expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4
Using tag names and tag placeholders in expressions . . . . . . . . . . . . . . . . . . . . . . . . 23-5
Specifying the area with a tag name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-5
Using placeholders to specify tag values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-5
Using constants in expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
Using operators to modify values in expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
Arithmetic operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
Relational operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-7
Logical operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-7
Bitwise operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-8
Evaluation order of operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9
Using built-in functions in expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11

xx
 • • • • •
CONTENTS

Math functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11

File functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-12
Time functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-13
Tag functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-15
Security functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-17
Language function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-18
FactoryTalk alarm functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-18
Using if-then-else logic in expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-19
Nested if-then-else. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-20

24 • Creating embedded variables

About embedded variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1
Inserting embedded variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1
Creating numeric embedded variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3
Creating string embedded variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-5
Creating time and date embedded variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7
How embedded variables are displayed at run time. . . . . . . . . . . . . . . . . . . . . . . . . . 24-8
Numeric embedded variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-9
String embedded variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-9
Time and date embedded variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-9
How embedded variables are updated at run time . . . . . . . . . . . . . . . . . . . . . . . . . . 24-10

25 • Setting up data logging

About data logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1
Gathering tag data in data log models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1
Data log storage formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2
ODBC database storage format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-3
Creating data log models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4
Specifying the storage format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5
Setting up log paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5
Setting up and managing data log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-6
Specifying when to log data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-6
Choosing the data to be logged. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-7
Logging data to ODBC data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-7
Logging data to an existing ODBC data source . . . . . . . . . . . . . . . . . . . . . . . . 25-7
Creating a new ODBC data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8
Setting up security to log data to a remote computer . . . . . . . . . . . . . . . . . . . . . 25-8
Creating new files at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8
Using the DataLogNewFile command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-9
Switching log paths at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-9
Setting up switching options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-10

xxi
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Switching back manually to the primary path . . . . . . . . . . . . . . . . . . . . . . . . . 25-10

Moving data from the secondary path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-11
Logging on demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12
Using the DataLogSnapshot command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12
Combining logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12
Modifying existing data log models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-13
Changing log paths in the SE Administration Console . . . . . . . . . . . . . . . . . . 25-13
Making run-time changes without modifying the model . . . . . . . . . . . . . . . . . 25-13
Starting and stopping data logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-14
Ways to start data logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-14
Ways to stop data logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-15

26 • Setting up trends
About trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
Charting current versus historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
Creating trend objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2
Providing a name for the trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-3
Setting up trend properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-3
Testing a trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-4
The parts of a trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5
Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5
Chart title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5
X-axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-6
X-axis legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-6
Y-axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-6
Y-axis legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-6
Pens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7
Legends. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7
Pen icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7
Pen markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-8
Value Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-9
Trend chart styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-9
The Standard chart style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-10
The XY Plot chart style. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-10
Isolated graphing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-11
Plotting a value across the full width of the chart . . . . . . . . . . . . . . . . . . . . . . 26-12
Choosing trend colors, fonts, lines, and legends . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-13
Changing the trend highlight color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-13
Changing the trend object background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-13
Displaying a current value legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-14
Displaying a line legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-15

xxii
 • • • • •
CONTENTS

Using shading to compare pens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-15

Using overlays to compare real-time and historical data . . . . . . . . . . . . . . . . . . . . . 26-18
Setting up snapshots and overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-18
Using trend templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-20
Applying a consistent appearance to trend charts . . . . . . . . . . . . . . . . . . . . . . 26-20
Creating a set of different views for the same data . . . . . . . . . . . . . . . . . . . . . 26-20
Returning to a standard display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-20
Saving pen attribute data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-20
Loading trend templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-21
About the Trend graphic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-21
Working with trends at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-22
Collecting data in the background at run time . . . . . . . . . . . . . . . . . . . . . . . . . 26-22
Selecting pens at run time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-23
Modifying trend properties at run time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-23
Scrolling the trend chart at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-24
Displaying the value of pens at various positions . . . . . . . . . . . . . . . . . . . . . . 26-25
Displaying the difference in pen values for two points . . . . . . . . . . . . . . . . . . 26-26
Zooming the trend chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-27
Panning the trend chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-27
Using the arrow keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-28
Printing the trend chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-28
Using overlays at run time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-28
Fixing run-time errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-29

27 • Creating macros
About macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1
Macro syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1
Specifying parameters in a macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-3
Typing macro names that contain spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-3
Nesting macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-4
Running macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-4
Specifying a macro to run when an HMI server starts . . . . . . . . . . . . . . . . . . . 27-5
Specifying user login and logout macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-5

28 • Using derived tags

About derived tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-1
How to use derived tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-1
Parts of the Derived Tags editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-2
Accept and Discard buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-3
Form and spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-3
Checking the syntax of an expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-3

xxiii
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Creating a derived tags component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-3

About the maximum update rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-4
Using multiple derived tag components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-4
Modifying existing derived tag components . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-5
Starting and stopping derived tags processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-5
Ways to start derived tags processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-5
Ways to stop derived tags processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-6

29 • Using events
About events in FactoryTalk View Site Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-1
Parts of the Events editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-1
Accept and Discard buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-2
Form and spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-2
Checking the syntax of an expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3
Creating an events component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3
About the maximum update rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Using multiple events components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Modifying existing event components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Starting and stopping events processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Ways to start events processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-5
Ways to stop events processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-5

APPENDICES

A • FactoryTalk View commands

Using commands in a FactoryTalk View SE application . . . . . . . . . . . . . . . . . . . . . A-1
How to use commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Using placeholders in commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Where commands run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Using absolute and relative references. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
How relative references are resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Creating symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Important guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Running and building commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

B • Setting up DDE communications for HMI tags

Overview of DDE communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Setting up an HMI server as a DDE client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Creating an HMI tag that uses DDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

xxiv
 • • • • •
CONTENTS

Specifying Device as the data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Syntax for DDE addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Scanning for new tag values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

C • ODBC database schemas

About the FactoryTalk Diagnostics log table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
HMI tag alarm log table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Data log tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

D • Importing and exporting XML files

About XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Exporting graphics data to an XML file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Modifying exported XML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Saving XML files in Notepad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Testing XML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Importing XML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Error log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Importing graphic display XML files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Graphic display XML file structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Index

xxv
Preface
FactoryTalk® View Site Edition is an integrated software package for developing and
running human-machine interface (HMI) applications that involve multiple users and
servers, distributed over a network.
A member of the FactoryTalk family of products, FactoryTalk View Site Edition (also
called FactoryTalk View SE) provides all the tools you need to create powerful,
dependable process monitoring and supervisory control applications.
FactoryTalk View SE software is designed for use with Microsoft® Windows® Server
2003, Windows XP, and Windows 2000 operating systems.

About RSView Enterprise

RSView® Enterprise is the former name of the FactoryTalk View family of software
products.
As of version 5.00 (CPR 9), Rockwell Software products that depend on and can share
FactoryTalk services in an integrated control system have been renamed to represent the
FactoryTalk brand.
The following table shows the new names for members of the product family formerly
known as RSView Enterprise:

RSView name (CPR 7 and earlier) FactoryTalk View name (CPR 9 and later)
RSView Enterprise FactoryTalk View
RSView Supervisory Edition (SE) FactoryTalk View Site Edition (SE)
RSView SE Distributed FactoryTalk View SE (Network)
RSView SE Stand-alone FactoryTalk View SE (Local)
RSView Studio FactoryTalk View Studio

RSView SE Client™ FactoryTalk View SE Client

RSView SE Server™ FactoryTalk View SE Server

RSView SE Administration Console™ FactoryTalk View SE Administration Console

RSView Machine Edition™ (ME) FactoryTalk View Machine Edition (ME)

RSView ME Station™ FactoryTalk View Machine Edition Station

P1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

About the FactoryTalk View SE documentation

The FactoryTalk View SE documentation set includes:
„ Release Notes. Read this information before you begin installing or working with the
software. The Release Notes are available from the FactoryTalk View Site Edition CD
and from the Help menu in FactoryTalk View Studio.
„ FactoryTalk View Site Edition Installation Guide. This manual contains information
about installing and activating the various FactoryTalk View SE software components.
In addition to the printed copy that comes with the software, the Installation Guide is
available in PDF format, from the FactoryTalk View Site Edition CD and from the
Help menu in FactoryTalk View Studio.
„ FactoryTalk View Site Edition User’s Guide. This manual contains comprehensive
information about designing, developing, and deploying FactoryTalk View SE
applications, as well as reference information.
For ease of printing, the User’s Guide is divided into two volumes. Both volumes are
available in PDF format, from the Help menu in FactoryTalk View Studio. For more
information about the contents of each volume, see “What’s in this manual,” next.
„ Help. Online procedures and reference information are available from the Help menu
in FactoryTalk View Studio, and from editors and dialog boxes used to develop
FactoryTalk View SE applications.

What’s in this manual

The FactoryTalk View Site Edition User’s Guide contains comprehensive information
about designing, developing, and deploying FactoryTalk View SE network and local
applications.
This includes information about how FactoryTalk View SE applications use FactoryTalk
services, and other FactoryTalk products.
The User’s Guide is organized in two volumes, available in PDF format from the Help
menu in FactoryTalk View Studio.
Volume 1 – Designing and Deploying Applications contains information about:
„ working in the FactoryTalk View SE development environment.
„ the key features of FactoryTalk View SE network and local applications.
„ setting up communications for an application, and working with tags.
„ setting up alarm monitoring and control, using HMI tags and FactoryTalk Alarms and
Events.

P2
 • • • • •
• PREFACE

„ features that support system availability at run time.

„ deploying applications in a production environment.
Volume 2 – Creating Application Components contains information about:
„ creating graphic displays and objects for operators to interact with at run time.
„ animating graphic objects.
„ gaining access to data using FactoryTalk View expressions and embedded variables.
„ monitoring historical data using data log models and trends.
„ using macros and FactoryTalk View commands in an application.
„ processing data using derived tags and event detection.

To open the User’s Guide

1. In FactoryTalk View Studio, on the Help menu, click Online Books.
2. Click the Volume you want to open.

If you are having trouble opening the User’s Guide, you might need to install Adobe Reader.
You can do this from the FactoryTalk View Site Edition installation CD. For details, see the
FactoryTalk View Site Edition Installation Guide.

Finding information about FactoryTalk View SE

There are several ways to find information about using FactoryTalk View SE.

Try the User’s Guide and Help first

The FactoryTalk View Site Edition User’s Guide and Help provide comprehensive
information about typical uses of FactoryTalk View SE. If you have a question, the
documentation probably contains the answer.
To find the information you need in either the User’s Guide or the Help, start with the
table of contents and the index, or perform a full-text search.
For more information, see Chapter 7, “Getting the information you need” in the
FactoryTalk View Site Edition Installation Guide.

Finding information on the Internet

If you can’t find the answer to your question in the User’s Guide or Help, try the Web sites
you can connect to from within FactoryTalk View Studio.

P3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ The Rockwell Automation Home Page offers general information about

Rockwell Software products and services.
„ The Rockwell Automation Downloads page provides access to various resources,
including information, drivers, and software extensions that you might need to
develop your FactoryTalk View SE applications.
„ The Rockwell Automation KnowledgeBase offers a comprehensive, searchable
database of support information for all Rockwell Automation products, including
FactoryTalk View SE.
„ The FactoryTalk View Series Home Page offers specific information about the
FactoryTalk View family of software products, including FactoryTalk View SE and
FactoryTalk View Machine Edition (ME).

To connect to Web sites from within FactoryTalk View Studio

„ On the Help menu, click Rockwell Automation on the Web, and then click the name of
the Web site you want to visit.

To connect to any Web site, you must have a web browser installed on the computer, and you
must have an active Internet connection.

Contacting Rockwell Automation Technical Support

If you can’t find the answer to your question in the documentation or on the Internet,
contact Rockwell Automation Technical Support, using one of these methods:
„ Telephone: 1-440-646-3434
„ Online: http://support.rockwellautomation.com
Support staff are available Monday to Friday from 8 a.m. to 5 p.m. local time (North
America only), except on statutory holidays.

When you call

When you call, be at your computer and ready to provide the following information:
„ the product’s Serial Number and Product Key. If you are using:
„ FactoryTalk Activation, the Serial Number and Product Key are printed on the
Activation Certificate enclosed with the product software CD.
„ EvRSI activation, the Serial Number is printed on the Activation disk label.
„ the product version number
„ the Coordinated Product Release (CPR) number

P4
 • • • • •
• PREFACE

„ the type of hardware you are using

„ the names of other Rockwell Automation products installed on the computer
„ the exact wording of any messages displayed on the computer
„ a description of what happened and what you were doing when the problem occurred
„ a description of how you tried to solve the problem
If you are running a FactoryTalk View SE network application, also note:
„ how many computers are participating in the network application.
„ whether computers on the network are connected using a Windows domain controller,
or a workgroup.
„ which FactoryTalk View SE components are installed on participating computers.
„ which computers are running servers (the FactoryTalk Network Directory server,
FactoryTalk View SE Servers, data servers, or FactoryTalk Tag Alarm and Event
Servers), and whether servers are set up with redundancy.
„ which computers are running clients (FactoryTalk View SE Client or FactoryTalk
View Studio, or some other FactoryTalk client).
You might also be required to provide information about any FactoryTalk View add-ons
and updates that are installed on the computer.

To view the list of installed add-ons and updates

1. In FactoryTalk View Studio, on the Help menu, click About FactoryTalk View
Studio.
2. To view the list of installed updates, click Updates.
3. To view the list of installed add-ons, click Add-Ons.

P5
19 Creating graphic displays

19 • Placeholder
This chapter describes:
„ what graphic displays are.
„ parts of the Graphics editor.
„ techniques for working in graphic displays.
„ techniques for working with graphic objects.
„ testing graphic displays.
„ creating and working with global object displays.
„ adding process faceplates to an application.
„ using objects from the graphic libraries.
„ importing graphic files from third-party applications.
„ using placeholders to specify tag values.
„ setting up tag placeholders for global objects.
„ setting up the appearance and behavior of graphic displays.
„ docking displays to the FactoryTalk® View SE Client window.
„ printing graphic displays at run time.

About graphic displays

A graphic display represents a run-time operator’s view of plant activity.
A graphic display can show system or process data, and provide an operator with ways to
write values to external devices such as programmable controllers. To create a visual
record of tag values, the operator can print the display at run time.
Each graphic display can contain up to 3000 references to expressions or tags (HMI tags
and data server tags). This limit includes the tags contained in embedded variables.
The limit also includes duplicate references. For example, one display can contain only
3000 numeric inputs that refer to tags, even if all 3000 objects refer to the same tag.
Graphic displays are made up of graphic objects, which can be:
„ created in the Graphics editor.
„ dragged and dropped from a graphic library.

19-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ ActiveX® objects embedded in the graphic display.

„ created by another Windows® application, then copied and pasted into a display, or
inserted using Object Linking and Embedding (OLE).

Importing and exporting graphic display XML files

The information a graphic display contains is stored in a file called displayname.gfx
(where displayname is the name you give to the graphic display).
In FactoryTalk View Studio, you can use the Graphics Import Export Wizard to export
graphic display information to an XML file, or to import a graphic display XML file into
an application.
You can edit the XML files before importing them back into an application, to modify
existing graphic objects, or to add new objects to a display.
For more information about importing and exporting graphic display files, see
Appendix D, Importing and exporting XML files.

About global object displays

FactoryTalk View global objects allow you to link the appearance and behavior of one
graphic object to multiple copies of the object in the same application.
Global objects are created on global object displays. In FactoryTalk View Studio, you
create global object displays in the Global Objects folder, the same way you create
standard graphic displays in the Displays folder.
All of the objects and groups of objects on a global object display are global objects. Any
graphic object you can create in FactoryTalk View can be a global object, except for
ActiveX controls, OLE objects, and HMI tag alarm summaries.

Working with global objects

When you copy a global object onto a standard display in the Displays folder, the copy is
called a reference object. The original global object in the Global Objects folder becomes
its base object.
Reference objects have special properties that allow them to link to their base objects.
At run time, when a standard display that contains reference objects is run, the global
object display (or displays) that contains the base objects is loaded in the background.
Changes you make to the base object are reflected in all of the reference objects linked to
it, the next time displays containing the reference objects are opened, or refreshed by
closing and reopening them.
For information about creating global object displays, see page 19-24.

19-2
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Parts of the Graphics editor

19 • Placeholder
Use the Graphics editor to create and modify standard graphic displays, global object
displays, and graphic libraries. Where you open the Graphics editor determines the type of
display you create.

To open the Graphics editor

1. In FactoryTalk View Studio, in the Explorer window, open the Graphics folder.
2. Right-click one of the Displays, Global Objects, or Libraries icons, and then click
New. Or, double-click an existing standard display, global object display, or graphic
library.
When the new or existing display opens, you are working in the Graphics editor.

Menu bar
Docked
toolbar

Display area

Floating
toolbar

Diagnostics
List
Status bar

The Graphics editor consists of these parts:

The toolbars contain buttons for commonly used menu items. The previous illustration
shows three toolbars, but the Graphics editor has others, including toolbars for foreground
and background colors, pattern styles, and aligning objects.
You can hide or show toolbars using the View menu, and move the toolbars around on the
screen. For more information about toolbars, see page 19-7.

19-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

The display area is the graphic display itself.

To set up the run-time appearance and behavior of a display, right-click the display, and
then click Display Settings.
In the Display Settings dialog box, you can set up a title bar for the display, specify its
size, position, and background color, and determine whether it has a border at run time.
The appearance of a display in the Graphics editor is similar to its run-time appearance
(except for the content of the title bar, and the position of the display).
Some changes made at design time, such as resetting the zoom feature, do not affect the
appearance of the display at run time.
For more information about display settings, see “Setting up the appearance and behavior
of a graphic display” on page 19-35.
The Diagnostics List displays information about system activity, such as command
and macro usage, tag reads and writes, communication errors, and system warnings for
the computer where FactoryTalk View is installed.
The status bar describes the action associated with the selected menu item or button.
The status bar also shows the x- and y-coordinates, width, and height of the selected
graphic object.

Viewing display contents in the Object Explorer

The Object Explorer displays a tree-list of all the objects in a graphic display. Objects are
listed in front-to-back order, with the most recently created objects at the front. Grouped
objects are listed as expandable items in the tree, with a + icon.
When you click an object in the Object Explorer, it is selected in the display, and selection
handles appear around it automatically. This means you can use the Object Explorer to
select an object hidden by others in a display, instead of bringing the object to the front.

The Object Explorer does not show wallpaper objects, or the objects within ActiveX composite
objects.

You can keep the Object Explorer open while you work on different objects, and in
different displays.
You can also use the Object Explorer to highlight specific types of objects, and objects
that have animation, or a tag or expression assigned to them.

To open the Object Explorer

„ In FactoryTalk View Studio, open the Graphics editor, right-click the graphic display,
and then click Object Explorer.

19-4
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

19 • Placeholder
Click the + icon to view
the objects and grouped
When you right-click an
objects within a group.
object in the Object
Explorer, the object’s
shortcut menu opens,
as it does when you right-
click the object in the
graphic display.

To highlight different types of objects in a display

1. In the Object Explorer, click Settings.
2. In the Highlight Settings dialog box, select boxes beside the items that you want
highlighted, and then click OK.
3. In the Object Explorer, select the check box, Highlighting on.
The objects are highlighted in red in the Object Explorer and in the graphic display.

Viewing object properties in the Property Panel

The Property Panel displays the properties of graphic objects and the values assigned to
the properties. It also shows the tags or expressions assigned to an object’s connections.
Use the Property Panel to modify the properties of graphic objects, and to assign tags and
expressions. You can select multiple objects, and then make changes to the common
properties of all of the objects at the same time.

19-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

You can keep the Property Panel open as you work in the Graphics editor, and you can
drag the panel’s borders to make it larger or smaller.

To open the Property Panel

„ Right-click a graphic object in a display, and then click Property Panel.
Show/Hide
Property Panel You can also click the Property Panel tool on the tool bar, to show or hide the panel.
tool

Click this button for help

with the selected property.

Scroll to see more

properties …

… or drag this bar up

This box describes or down to see more
the selected property properties, or more of
and the type of data the description.
the property uses.

For details about options in the Property Panel, click Help.

Techniques for working in graphic displays

When working with graphic displays, you will use certain actions and techniques
frequently. Knowing how to perform these actions can save time.

Zooming in and out

Zoom in To magnify or reduce the view of a graphic display, use the Zoom In or Zoom Out option
on the View menu. Zoom In magnifies objects, while Zoom Out reduces magnification.
In the Properties tab of the Display Settings dialog box, if the Size property for a display is
set to Specify Size in Pixels, you can use Zoom to Fit to resize the display to fit the
Zoom out workspace window.

19-6
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

If the Size property is set to Use Current Size, Zoom to Fit behaves in the same way as
Cancel Zoom; it returns a display to its original size.

19 • Placeholder
Setting up a display grid
To size and position objects precisely, use the grid items on the View menu. You can
change the grid settings any time during the drawing process.

Select this check box to

make the grid visible.
Select this check box to
make the grid active. Set the spacing
Select a color for the of the grid points
grid points. in pixels.

Use the grid to simplify aligning and sizing objects. When the grid is on, all objects you
draw or place are aligned to the grid automatically.
If you select Snap to Grid, the grid is activated, and the next object you draw or position
will be pulled to the closest grid point. Turning on the grid does not affect the placement
of existing objects.
If you clear Snap to Grid, the grid is passive, and does not affect the position of objects.
Turn off the grid to draw or position an element between the grid lines.

Using the toolbars

The toolbars are a convenient way to perform an action. You can:
„ hide or show the toolbars using the items on the View menu. If there is a check mark
beside the toolbar name, the toolbar is visible.
„ drag the toolbars anywhere on the screen.
„ dock the toolbars to an edge of the FactoryTalk View Studio workspace (except the
ActiveX Toolbox).

Selecting a drawing tool

The Objects toolbar contains tools for creating, selecting, and rotating objects. The tools
are also available on the Objects menu.
To draw an object, click a tool in the toolbox or on the Objects menu. When you do this,
Select tool
the pointer changes to show which tool is active.
To stop using a drawing tool, click the Select tool, or click another drawing tool.

19-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Selecting objects
To work with an object in a graphic display, first you must select it.
To select a single object in a display, click on the object using the left mouse button.
Handles appear along the edges of a selected object.
To select several objects, click in the graphic display at one corner of the group, and then
drag the mouse diagonally, to draw a bounding box around the objects. When you release
the mouse button, all the objects within the bounding box are selected.
You can also select a group of objects by holding down the Ctrl key while you click each
individual object.
To cancel selection of an object or a group of objects, click in a part of the graphic display
that does not contain any objects.

Using shortcut menus to perform actions quickly

When you right-click in a graphic display, or on a graphic object, a shortcut menu opens,
as shown in the following illustration.

When you
right-click an
object …

… the shortcut
menu opens.

The shortcut
menu contains
items for working
with the selected
object.

The items on the shortcut menu depend where you click: when you right-click an object,
the menu contains items relevant to the object; when you right-click a display, the menu
contains items relevant to the display.

Techniques for working with graphic objects

When creating and modifying graphic objects in a display, you use certain actions and
techniques frequently. Knowing how to perform these actions can save time.
For specific information about different objects, see Chapter 20, Creating graphic objects.

19-8
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Duplicating objects

19 • Placeholder
When you duplicate graphic objects in a display, you also duplicate actions.
For example, if you duplicate an object, move it, and then duplicate it again, the second
duplicate action copies and moves the object, in one step. This is useful for creating a
series of objects with an equal distance between them.
When an object is duplicated, any animation attached to the object is also duplicated.
If an object group is duplicated, the new copy of the group can be ungrouped into
individual objects. For more information about grouping objects, see page 19-15.

To duplicate an object
„ Right-click the object in a display, and then click Duplicate.
Duplicate works until the object is no longer selected.

Select object Duplicate object Move object Duplicate again

Resizing and reshaping objects

When you select an object, handles appear around it.
When you position the pointer over a handle, the pointer changes to a double-headed
arrow. You can then click on and drag the handle, to resize and reshape the object.
You can also press Shift and the arrow keys on the keyboard, to resize and reshape objects
in small increments.

19-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Drag a side handle to

change either the width or
height.

Drag a corner handle to

change both the width and
height.

You can reshape some objects using the object’s editing tool. To do this, right click the
object, and then click Edit. The tool varies depending on the object that has been selected.

To maintain an object’s proportions while resizing

„ Click on a corner handle, press Shift, and then drag the mouse.

If you attempt to resize a global reference object with its LinkSize property set to True, the object
will snap back to its original size. For more information about the LinkSize property, see “Setting
up the link properties of reference objects” on page 20-48.

Arranging objects
You can arrange objects in a graphic display in a number of ways, using the Arrange menu
or buttons on the toolbar. You can:
„ stack objects by moving them in front of or behind other objects.
„ align objects with each other.
„ space objects horizontally or vertically.
„ flip objects horizontally or vertically.
„ rotate objects around an anchor point.
„ combine several objects into a group that behaves as a single object.
„ separate a grouped object into its component objects.

Stacking objects
Objects in a graphic display are stacked in the order they are created, with the most
recently created object on top.

19-10
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

To change the order, move objects to the front or back of the stack.

19 • Placeholder
Use Send to Back to move the selected object to the bottom of the stack:

Select the object. Send the object to back.

.
Use Bring to Front to move the selected object to the top of the stack:

Select the object from behind. Bring the object to front.

.

To select the object at the back

„ Click the top object once, pause, and then click again. Do not double-click and do not
move the mouse.

Aligning objects
To line up the tops, bottoms, or sides of objects in a display, align the objects with each
other, or with the display grid.
To do this Click this button or menu item
Align the selected object (or objects) with the left-
Align Left
most selected object.
Align the selected object (or objects) with the Align Center
horizontal center of the largest selected object.
Align the selected object (or objects) with the Align Right
right-most selected object.
Align the selected object (or objects) with the top- Align Top
most selected object.
Align the selected object (or objects) with the Align Middle
vertical center of the largest selected object.

19-11
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To do this Click this button or menu item

Align the selected object (or objects) with the Align Bottom
bottom-most selected object.
Align the selected object (or objects) with the Align Center Points
center of all selected objects.
Align the selected object (or objects) with the grid. Align to Grid

Aligning objects top, middle, and bottom

Align top

Align middle

Align bottom

Aligning objects left, right, and center

Select objects Align left

19-12
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

19 • Placeholder
Select objects Align center

Select objects Align right

Spacing objects
To create an equal amount of space between the center points of objects in a graphic
display, space the objects vertically or horizontally.

To do this Click this button or menu item

Place the centers of the selected objects an equal
Space Horizontal
distance apart horizontally.
Place the centers of the selected objects an equal
Space Vertical
distance apart vertically.

Spacing objects vertically and horizontally

Centers are
separated by an
equal vertical
distance.

Select objects Space vertically

19-13
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Centers are
separated by an
equal horizontal
distance.

Select objects Space horizontally

Flipping objects
To move an object in a graphic display to a position that is a mirror image of its original
position, flip the object vertically or horizontally.

To do this Click this button or menu item

Flip the selected object (or objects) top to bottom
Flip Vertical
(upside-down).

Flip the selected object (or objects) left to right Flip Horizontal

Flipping objects vertically

Select object Flip vertical

Flipping objects horizontally

Select object Flip horizontal

19-14
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Rotating objects

19 • Placeholder
To rotate an object or group of objects around an anchor point, use the Rotate tool. The
anchor point is represented by a crosshair, as shown in the following illustrations:

You can place the crosshair inside an object.

You can place the crosshair outside an object.

You can also use the Rotate tool when attaching rotation animation to a graphic object.
For details, see “Rotating objects” on page 21-11.

You cannot rotate OLE objects, ActiveX objects, bitmaps, text, or panel objects.

Grouping objects
Grouping combines several objects into one so you can manipulate them as a single
object. Grouping is useful for keeping objects in the same position relative to each other.
You can cut, copy, and paste groups, arrange the group as a single object relative to other
objects, and apply the same properties to all the members of the group at once.

19-15
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Drag the mouse to select the objects. Group them.

You can attach animation to a group and preserve any animation attached to the objects
that make up the group.
Group animation generally takes precedence over the animation attached to individual
objects. For more information, see “Applying animation to object groups” on page 21-5.
Deleting a group deletes all individual objects in the group. Changing the color or pattern
style of the group changes the color or pattern style of all individual objects in the group.

Ungrouping objects
When you disconnect a group of objects, the individual objects in the group are selected in
the graphic display.
Ungrouping deletes animation attached to the group, because the group no longer exists.
However, any animation attached to the individual objects remains active.

Select the group. Ungroup it.

19-16
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Modifying grouped objects

19 • Placeholder
You can modify a group of objects without breaking up the group. This is particularly
useful when animation is attached to the group, because ungrouping deletes the animation.
Modify grouped objects using:
„ the Property Panel, to apply shared properties to all members of the group at the same
time. For example, change the line width of all objects in the group to 2 pixels.
„ toolbars, to apply the same pattern style, background style, foreground colors, and
background colors to all members of the group.
„ the States toolbar, to cycle through the states and apply the same properties to them,
for all members of the group at the same time.

When you select a group containing objects with states, only the states shared by all objects
in the group are displayed in the toolbar. For information about using the States toolbar, see
“Testing the appearance of objects in different states” on page 19-23.

To modify the objects within a group, double-click the group. A rope-like border indicates
that the group is in edit mode.

Double-click on a group Click inside the box to

to place it in edit mode. select objects within the
group.

Click inside the box to select individual objects or other groups within the group. You can
also add new objects to the group.
To see which objects are selected, look in the Object Explorer or the FactoryTalk View
Studio status bar. For information about using the Object Explorer, see page 19-4.
To cancel group edit mode, click outside the group border.

Applying colors
The color palettes contain a range of colors that you can apply to graphic objects. You can
select colors before you draw an object, or you can apply them to an existing object.
To show and hide the color palettes, click their names on the View menu.

19-17
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

You can use the:

„ Foreground Color palette to select a color for the outline of an object, for text, or
for hollow objects.
„ 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.

Applying pattern styles and colors

Use the Pattern Styles toolbar to apply patterns to graphic objects. You can select a pattern
before you draw an object, or you can apply a pattern to an existing object.
An object’s pattern is visible only if the object’s background style is Solid. Objects with a
transparent background have no pattern.

Hollow polyline object Filled polyline object

Pattern styles apply to the interior of objects. Closed objects such as rectangles, circles,
polygons, text objects, and wedges are completely filled.
Open or partially open objects, such as polylines or freehand objects, can also take a
pattern style. The Graphics editor draws an imaginary line from the start and end points,
and then fills the object as a closed object.
The pattern color is not determined by the foreground or background color selected for an
object. Instead, you must apply pattern colors separately.

19-18
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

To open the Pattern Styles toolbar

On the View menu, click Toolbars, and then click Pattern Styles.

19 • Placeholder
„

To apply a pattern color

1. Right-click the graphic object, and then click Properties.
2. In the Properties dialog box, click the Pattern color box, and then click a pattern color.

Changing line properties

You can select a line object and change its width and style in the General tab of its
Properties dialog box, or in the Property Panel. The line styles are:
Solid

Dash

Dot

Dash-Dot

Dash-Dot-Dot

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 customize line width and color in the Pens tab of the Trend
Properties dialog box. For more information, see Chapter 26, Setting up trends.

Naming graphic objects

When you create a graphic object, it is assigned a name automatically.
In the Common tab of the object’s Properties dialog box, or in the Property Panel, you can
give the object a new name.

19-19
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

An object’s name is used when logging events for the object. It 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 is also displayed in the Object Explorer. For more information, see
page 19-4.

Assigning tags and expressions to objects

To assign tags or expressions to an individual object, use the Connections tab in the
object’s Properties dialog box, or in the Property Panel.
The following illustration is of the Property Panel for a maintained push button. In the
Connections tab, you can set up a Value tag and an Indicator tag or expression.

Type a tag name or

expression in this column.

Click this button to open

The arrows show the the Tag Browser.
direction in which data
flows between the Click this button to open
object and the tag or the Expression editor.
expression.

This box describes the

selected connection,
and the type of data it
uses.

The Connections tab is blank, if multiple objects are selected. You can only assign a tag or
expression to one object at a time.

The arrows beside the connection names indicate the direction data flows between the tag
or expression and the object:
„ A right arrow indicates that data flows from the object to the tag or expression only. In
other words, the object can write to the tag or expression.
„ A left arrow indicates that data flows from the tag or expression to the object only. In
other words, the object can read from the tag or expression.

19-20
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

„ A double arrow indicates that data flows in both directions. In other words, the object
can write to, or read from, the tag or expression.

19 • Placeholder
Adding tooltips to graphic objects
To provide information about a graphic object to an operator, add a tooltip to the object.
By default, an object has no tooltip. If you add a tooltip, it shows at run time, when the
operator positions the pointer over the object for a few seconds.

When you type

a name here …
… the object’s
name changes
here.

When you type

text here …

… a tooltip for the object

is displayed at run time.

You can create a tooltip for an object in the Property Panel, or in the Common tab of the
object’s Properties dialog box.
Tooltips can consist of a single line or multiple lines of text.

Using tag substitution to replace text strings

Use tag substitution to replace the text strings in graphic objects or embedded variables in
a graphic display.

19-21
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

You can find and replace text strings in tag names, expressions, and FactoryTalk View
commands.
You cannot use tag substitution to replace text created using the Text tool.

To search for and replace text strings

1. Select the graphic object (or objects) that contain text strings you want to replace.

To select all the graphic objects in a display, press Ctrl+A.

2. On the Edit menu, click Tag Substitution.

3. In the Tag Substitution dialog box, type the text you search for and replace, and then
click Replace.
For details about options in the Tag Substitution dialog box, click Help.

Creating a background for a display

You can create a background for a graphic display by converting objects to wallpaper.
For example, you can import photographs of a machine or process, convert the images to
wallpaper, and then overlay the wallpaper with animated objects.
When graphic objects are converted to wallpaper, they are locked into position and
become a static background for other objects in the display. You cannot select or modify
wallpaper objects, and any animation attached to them is not in effect.
Converting bitmaps that do not need to be selected or animated can improve the
performance of a graphic display significantly.

To convert objects to wallpaper

1. Select one or more objects.
2. On the Edit menu, select Wallpaper, and then click Convert to Wallpaper.
To reactivate converted objects, and to restore any animation attached to the objects,
unlock the wallpaper.

Objects in a global object display cannot be converted to wallpaper.

19-22
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Testing graphic displays

19 • Placeholder
You can test the objects in a graphic display quickly, by switching to test display mode in
the Graphics editor.
Test Display
tool
When you are finished testing, to continue working on the display, switch back to edit
display mode. To switch between test and edit modes, use the buttons on the toolbar or the
items on the View menu.
Edit Display Testing a graphic display in FactoryTalk View Studio is not the same as running the
tool display in the FactoryTalk View 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 between open displays.
In addition, some FactoryTalk View commands are ignored when run in test display
mode. For a complete list of these commands, see Appendix A in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

If objects in a graphic display are connected to tags in devices, to fully test the display you must
set up communication with the devices or data servers.
Before you deploy an application, it is recommended that you test it in the FactoryTalk View
SE Client, to verify that everything works as intended.

Testing the appearance of objects in different states

Some objects have multiple states. You can set up each state differently, so the object’s
appearance changes whenever the state changes.
To make sure the different states for an object are set up correctly, view each state using
the Sates toolbar or the Property Panel.

To view an object’s states using the States toolbar

1. On the View menu, click Toolbars, and then click States.
2. Select one or more objects.
3. In the States toolbar, click the state you want to view. If you selected multiple objects,
the toolbar shows the states common to all the objects.
4. To view the next state in the list, click on it, or press the Down Arrow key. To view:
„ the previous state, press the Up Arrow key.
„ the first state, press the Home key.
„ the last state, press the End key.

19-23
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To view an object’s states using the Property Panel

1. Select one or more objects.
2. In the Property Panel, click the State property, and then click the state to view.
3. To view the next state quickly, double-click the row, or press Enter on the keyboard.

Creating and working with global object displays

Use the Graphics editor to create global object displays in the Global Objects folder, the
same way you create standard displays in the Displays folder.
All of the objects and groups of objects created in a global object display are global
objects. Any graphic object you can create in FactoryTalk View can be a global object,
except for ActiveX controls, OLE objects, and HMI tag alarm summaries.
When you copy a global object into a standard graphic display (in the Displays folder), the
copy is called a reference object. The original global object (in the Global Objects folder)
becomes the copy’s base object.
Reference objects have special properties that allow them to link to the original, base
objects. When you modify properties of a base object, the changes are copied to all
reference objects linked to the base object.
For information about setting up the properties that link base and reference objects, see
“Setting up the link properties of reference objects” on page 20-48.
You can produce an unlimited number of reference objects from a single base object.
However, reference objects can only link to a base object within the same application or,
in a network application, within the same HMI server.

Creating global object displays

To create a global object display, create a new display in the Global Objects folder, or add
a standard display or graphic library into the Global Objects folder.
When you add a standard display into the Global Objects folder, graphic objects in the
display convert to global objects, except for ActiveX controls, OLE objects, HMI tag
alarm summaries, and reference objects with broken links. These objects are deleted.

About global object display files

Global object display files are saved with the extension .ggfx, to the following location on
the development computer:
\Documents and Settings\All Users\Documents\RSView Enterprise\SE\HMI
Projects\<HMI Project Name>\Global Objects

19-24
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

where <HMI Project Name> is the name of the HMI server in the Explorer window.

19 • Placeholder
The number of global object displays you create in an application does not count toward the
maximum allowed by the activation licenses you have purchased and installed.

To create a new global object display

„ In FactoryTalk View Studio, in the Explorer window, right-click the Global Objects
icon, and then click New.
The new global object display opens in the Graphics editor. Use tools in the editor to
create global objects, just as you would create graphic objects in a standard display.

To create a global object display from an standard display

1. In FactoryTalk View Studio, in the Explorer window, right-click the Global Objects
icon, and then click Add Component into Application.
2. Browse to and select the standard display or library to add, and then click Open.

Adding standard displays that contain reference objects

In a network application, if you add a standard display or graphic library containing linked
reference objects into the Global Objects folder, the linked reference objects:
„ convert to global objects, if added within the same HMI server:
„ are deleted, if added to a different HMI server.

Existing reference objects with broken links are always deleted, whether you add them within the
same HMI server, or to a different one.

About global object displays at run time

When a graphic display containing global reference objects is run, the global object
display (or displays) containing the linked base objects also runs, in the background.
When you modify the base object in a global object display, all linked reference objects
are updated with the changes, the next time their host displays are opened or refreshed.
Since global object displays run in the background, you cannot select or specify one:
„ as a parameter for the Display command.
„ from the Component Browser, when creating a display list selector object.
„ as the initial display, when creating a client file in the FactoryTalk View SE Client
Wizard.

19-25
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

However, you can run a global object display in test display mode, when developing an
application in FactoryTalk View Studio.

To improve performance, minimize the number of global object displays that must be loaded in
the background at run time, by storing the base objects used in an application on as few global
object displays as possible.

Adding process faceplates to an application

When you add an HMI server to a network application, or when you create a new local
application, you have the option to add the process faceplate displays that are installed
with FactoryTalk View SE.
In the Add Process Faceplates dialog box, you can select to add some or all of the
faceplate displays. For details about options in the dialog box, click Help.

You can also add the process faceplates later, after you create the application or HMI
server. To do this, right-click the HMI server, and then click Add Process Faceplates.
If you added a display previously, you can either replace the existing display or remove it
from the list of displays.

Adding faceplate displays to an application affects the license count. Each added faceplate
display (.gfx file) counts as one display for activation purposes. The corresponding global object
display (.ggfx file) is not included in the count.

19-26
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Working with faceplates in the Graphics editor

19 • Placeholder
The faceplate displays you selected are added to the Graphics folder, under the Displays
and Global Objects icons.
Like the graphics libraries installed with FactoryTalk View SE, you can use the process
faceplates displays in an application as they are, or you can copy and then paste the
faceplates into existing standard and global objects displays.
For more information about faceplates, see the FactoryTalk View Site Edition Help.

Using objects from the graphic libraries

FactoryTalk View comes with a set of libraries that contain graphic objects and displays.
Many of the objects are preconfigured with animation. Use the objects as they are, or
change them to suit your needs. You can:
„ look at the objects and displays to get ideas for the application you are creating.
„ drag and drop objects from the libraries into displays.

Location of library files

For Windows 2000, library files are stored in the folder:
\Documents and Settings\All Users\Documents\RSView Enterprise\
SE\Libraries

For Windows XP or Windows Server 2003, library files are stored in the folder:
\Documents and Settings\All Users\Shared Documents\RSView Enterprise\
SE\Libraries

You can change the folder where library files are located. For details, see the FactoryTalk
View Site Edition Help.

Importing graphic files from third-party applications

FactoryTalk View can import the following types of files:

File extension Type of file

.wmf Windows metafiles
.bmp, .gif, .tif, .pcx Bitmap files
.jpg JPEG files
.dxf AutoCAD ® files*

19-27
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

*FactoryTalk View does not import AutoCAD 13 or later .dxf files. To import a graphic file
created in AutoCAD 13 or later, export the graphic file as a .wmf file in AutoCAD, and
then open the.wmf file in FactoryTalk View.

Before importing files, set up the computer’s display properties to display more than 256
colors. This will ensure that imported objects are the same colors as the original objects.
When you import objects, you can convert them to FactoryTalk View objects. This offers
the following advantages:
„ Graphic display files are smaller.
„ Objects are groups of objects rather than a single object. This means you can modify
the individual parts of the object, including attaching animation to individual parts.

Using bitmaps in a FactoryTalk View application

Bitmaps consume Windows resources. When using bitmaps, consider the following
guidelines.

Use device-dependent bitmaps

Device-dependent bitmaps (.bmp files) display faster than device-independent bitmaps
(.dib files) because the FactoryTalk View Graphics editor is optimized for device-
dependent bitmaps.
Also, you can modify device-dependent bitmaps in place using the Microsoft® Paint
program.

Avoid unnecessary color depth

Create bitmaps in the lowest color depth possible. The more colors you use, the more
memory that is consumed:
„ 16-color bitmaps consume 4 bits per pixel (½ byte per pixel)
„ 256-color bitmaps consume 8 bits per pixel (1 byte per pixel)
„ 24-bit bitmaps consume 24 bits per pixel (3 bytes per pixel)
If possible, use 16-color bitmaps. To change a higher-resolution bitmap to 16 colors, open
the bitmap in the Microsoft Paint program and save the bitmap as a 16-color bitmap.

Match palettes in 256-color systems

In a 256-color system, if bitmaps use two different color palettes, Windows must
recalculate and redraw all bitmaps when window focus changes.
Redrawing bitmaps causes delays and can make a scanned image or photograph `sparkle’
or appear as a negative.

19-28
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

To match palettes, use a bitmap-oriented graphical tool that lets you match palettes.

19 • Placeholder
Palette matching is an issue only for 256-color video adapters. 24-bit color systems do not
match palettes and 16-color systems dither colors (that is, alternate pixels of different
colors to approximate another color).

Do not use the Scale option

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.
Bitmaps take longer to draw when they are scaled to a size different from their original
size.
An OLE object can be a bitmap or a bitmap wrapped in a metafile. These types of OLE
objects will also draw more slowly when scaled.

Avoid large bitmaps

Graphic displays that contain large bitmaps consume memory and can be very slow to
display because of the delay in loading the bitmaps from disk.

Avoid many bitmaps

Whenever possible, create graphic objects using the FactoryTalk View drawing objects.
You can also change a bitmap to an FactoryTalk View object by converting the bitmap to
wallpaper, tracing over the bitmap with FactoryTalk View drawing objects, and then
deleting the bitmap.

When to use a bitmap

Bitmaps generally make graphic displays slower. However, objects with large amounts of
detail, such as subtle shading, might draw more quickly if converted to a bitmap because
bitmaps take the same amount of time to draw regardless of their complexity.

Using placeholders to specify tag values

Tag placeholders can save time by providing a way to use a single graphic display for
several similar operations.
For example, imagine you are creating displays for a plant that cans corn and beans, and
the machinery used in both processes is identical.
Instead of creating two displays and then specifying corn-related tags in one display and
bean-related tags in another, you can create one display and use tag placeholders where
tag names are required.

19-29
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

When the display runs, the placeholders must be replaced with actual tag names.
You can do this using a parameter file, or by specifying the tag names as parameters of the
Display command.

Creating a tag placeholder

A tag placeholder is the cross-hatch character (#) followed by a number from 1 to 500.
You can use a tag placeholder to specify a value for a graphic object, instead of (or as part
of) specifying a tag name, expression, command, or embedded variable.
In the following illustration, the tag placeholder #1 is specified in the Connections tab of
the Numeric Input Properties dialog box, instead of a tag name:

You can refine the tag placeholder, by specifying portions of the complete tag name.
For example, if you are specifying an HMI tag, you can add a folder name (or names) to
the placeholder, as in the following entry:
#1\PV
To specify the full tag name at run time, you would only have to provide the folder name.

Only HMI tag alarm summaries support tag placeholders that use wildcard characters. For
example, is #1\PV* a valid placeholder for an alarm summary, but not for other graphic objects.

Replacing tag placeholders using parameter files

To replace the tag placeholders in a graphic display, load a parameter file when you run
the display. A parameter file contains one entry for each unique placeholder in a display.
For example, to replace the tag placeholder #1 with a tag named corn/weight, load a
parameter file containing this entry:
#1 = corn\weight

19-30
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

When the display opens, #1 will be replaced with the tag named corn/weight.

19 • Placeholder
Only HMI tag alarm summaries support parameter file entries that use wildcard characters. For
example, a parameter file containing the entry #1 = bean_* would display alarms associated with
all tags beginning with bean_, only if the file is loaded with an alarm summary display.

Assigning a parameter file to the initial client display

You can specify a parameter file to load with the graphic display that opens initially, when
a FactoryTalk View SE Client starts up.
To do this, in the FactoryTalk View SE Client Wizard, select the display in the Initial
display list. Then, in the Display parameters box, type /P followed by the name of the
parameter file to load with the display (for example, /PBeans).

Example: Replacing tag placeholders using a parameter file

To load a parameter file named Beans, to replace tag placeholders in a graphic display
named Canning, type:
Display Canning /PBeans

Replacing tag placeholders using the Display command

When you run a graphic display, instead of using a parameter file to replace tag
placeholders, you can use the /T parameter with the Display command.

Example 1: Replacing tag placeholders by listing tag names

To run a graphic display named Canning, with the tags Pea_Weight, Pea_Level, and
Pea_Temp, type:
Display Canning /TPea_Weight,Pea_Level,Pea_Temp

Example 2: Replacing a tag placeholder with a folder name

The tag database contains these tags:

Corn\Weight Bean\Weight
Corn\Level Bean\Level
Corn\Temp Bean\Temp

19-31
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Wherever the tags are needed, the placeholder #1 is used for the folder name, as follows:
#1\Weight, #1\Level, or #1\Temp.
To run the display named Canning with the tags in the Corn folder, you would type:
Display Canning /TCorn
To run the display named Canning with the tags in the Bean folder, you would type:
Display Canning /TBean

Setting up tag placeholders for global objects

Using tag placeholders in a global object lets you assign unique values to the different
reference objects linked to the global base object.
To set this up, first you define the tag placeholder for the global base object, and then you
assign run-time values to the linked reference objects.
When displays containing the reference objects are run, the tag placeholder is replaced
with the value specified for each reference object.
For grouped reference objects, the value specified for the top-level object is applied to
every object comprising the group, that uses the same tag placeholder.
If you do not assign a value to a tag placeholder at design time, you can provide the value
at run time using either a parameter file, or the /T parameter with the Display command.
For information about using these methods, see page 19-30 and page 19-31.

Defining tag placeholders for use in reference objects

You can use tag placeholders instead of (or as part of) a tag name, expression, command,
or embedded variable associated with a global object or group of objects.
These are the steps involved in setting up tag placeholders for global objects:
1. Define one or more tag placeholders at the global base object.
2. Create one or more reference objects linked to the base object.
For information about creating reference objects, see “Creating global objects” on
page 20-46.
3. For each reference object, assign a value to the tag placeholder (or placeholders)
defined at the base object.

19-32
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

You can assign a unique value to the same tag placeholder, for each different reference
object. For an example, see page 19-34.

19 • Placeholder
To define tag placeholders for the global base object
1. Right-click the global base object (or group), and then click Global Object Parameter
Definitions.
2. In the Global Object Parameter Definitions dialog box, specify a tag placeholder name
(#1, for example) and optional description, as shown in this illustration:

You can define multiple tag placeholders for a single global object or group.
For grouped objects, the placeholder defined for the top-level object applies to all
objects in the group.
For details about options in the Global Object Parameter Definitions dialog box, click
Help.

To assign a value to a tag placeholder in a reference object

1. Right-click the global reference object (or group), and then click Global Object
Parameter Values.

If there are no tag placeholders defined for the linked base object, the Global Object
Parameter Values dialog box is not available.

The Global Object Parameter Values dialog box displays the Name and Description of
all tag placeholders defined for the global base object. as shown in the following
illustration.

2. In the Value column, specify a value for each tag placeholder, either by typing in the
box or by clicking Tag to browse for and select a tag.
For details about options in the Global Object Parameter Values dialog box, click Help.

19-33
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Example: Assigning different values to the same placeholder in

two global reference objects
To assign different values to two global reference objects that are linked to the same base
object, follow these steps:
1. In the global object display, right-click the global base object (or group), and then
click Global Object Parameter Definitions.

If you select any of the individual objects in a group object, the Global Object Parameter
Definitions dialog box is not available.

2. In the Global Object Parameter Definitions dialog box, provide a tag placeholder
name. For this example, use #1.
3. Type a description for the tag placeholder, that indicates what type of value to assign
to the placeholder.
4. Right-click the global base object, and then click Global Object Defaults.
5. In the Global Object Defaults dialog box, ensure that these options are selected:
„ For the LinkAnimation default, select Link with expressions.
„ For the LinkConnections default, select True.
Click OK.
6. Create a global reference object, by copying the base object and then pasting it into a
standard graphic display (in the Displays folder).
7. Duplicate the reference object.
8. Right-click the first reference object, and then click Global Object Parameter Values.
The Global Object Parameter Values dialog box displays the tag placeholder name and
description you set up for the global base object.
9. In the Value column beside tag placeholder #1, type a tag name, or click the Tag
button (. ..) to browse for and select a tag. Click OK.
10. Repeat steps 8 and 9 for the second reference object. To assign a unique value, select a
different tag.

19-34
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Modifying global objects that use tag placeholders

19 • Placeholder
Modifying a global object that uses tag placeholders has various effects, depending on the
type of modification.

Modifying grouped base objects

Tag placeholders defined for a grouped base object are deleted, if the grouped object is:
„ ungrouped.
„ regrouped with another object or group, to form a new grouped object.
„ copied and then pasted into another grouped object.

Modifying tag placeholders defined for the base object

Changes made to tag placeholder definitions at the global base object are copied to linked
reference objects, the next time the displays containing the reference objects are opened or
refreshed.
For example, when you add, delete, or change the description of a tag placeholder for a
base global object, the same change will take effect for any linked reference objects, the
next time the reference objects are updated.

Setting up the appearance and behavior of a graphic display

Use the Display Settings dialog box to set up the appearance and behavior of a graphic
display. You can modify display settings at any time, while you are setting up the contents
of the display.

To open the Display Settings dialog box

„ On the Edit menu, click Display Settings.
You can also right-click in an empty area of the display, and then click Display
Settings.

Setting up the properties of a graphic display

In the Properties tab of the Display Settings dialog box, you can specify:
„ how the display interacts with other displays at run time.
„ whether multiple copies of the display can run simultaneously on the same client.
„ how displays are cached.
„ what buttons and text show in the display’s title bar.
„ how often the display is updated.

19-35
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ the display’s size and position, and whether it can be resized at run time.
„ run-time security for the display.
„ the display’s background color.

In the Properties
tab, secure the
display and set
up how it looks
and performs at
run time.

Specifying the display type

You can set up the following display types in a FactoryTalk View application:
Replace is the default display type. Use this option if you want the graphic display to
replace other open displays when it opens. A display of Replace type closes any open
display that it overlaps. You don’t need to run separate commands to close the other
displays.
Overlay graphic displays will layer with other displays, overlapping some and being
overlapped by others as the focus changes between open displays. Use this option if the
display doesn’t need to replace other displays or appear on top at all times.

19-36
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

For overlay displays, you can select the check box, Keep at Back, if you want the display
always at the back. However, it is recommended that you use the On Top display type to

19 • Placeholder
control the layering of displays.
Overlay displays always appear behind On Top displays, and are replaced by Replace
displays. Use Overlay with care, because keeping multiple displays open can affect
system performance adversely.
On Top graphic displays will stay on top at all times, even if another display has focus.
Use this option if you want the display to always appear on top.
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 the one that had focus most recently.
You can use the PullForward, PushBack, and SetFocus commands to cycle through
multiple On Top and Overlay displays at run time. For more information about these
commands, see the FactoryTalk View Site Edition Help.

Allowing multiple running copies

Use this option with graphic displays of type Overlay or On Top, to allow multiple copies
of the display to run simultaneously.
For example, you can open two copies of the same display in different parts of a
FactoryTalk View SE Client window, by issuing the following commands:
Display PID /Q1
Display PID /Q2
PID is the name of a graphic display: the /Q1 parameter positions the first copy of the
display at the top-right corner of the window; the /Q2 parameter positions the second copy
at the top-left corner of the window.
If the Display command specifies a display that does not allow multiple copies, and the
display is already running, it is brought to the foreground only.
If multiple copies of a display (or several separate displays) are running, use the SetFocus
command to bring any hidden displays to the foreground. A display of type On Top is
always at the front, regardless of which display has focus.
For more information about commands that allow you navigate between displays at run
time, see the FactoryTalk View Site Edition Help.

To run multiple copies of displays without using the Allow Multiple Running Copies option, use
the Display command with different parameter files, for each copy of the display you want to run.
For more information, see “Replacing tag placeholders using parameter files” on page 19-30.

19-37
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Caching displays
Placing a graphic display in the cache makes the display appear more quickly at run time,
every subsequent time it is opened, because it does not have to be read from disk.
You can have up to 40 graphic displays in the cache. Place large or complex displays in
the cache, to minimize the use of system resources.
The Always Updating option allows a cached display to keep up to date, even when it is
not visible. Use this option to update trend data continuously, or to run VBA code in the
background.
The Always Updating option affects the behavior of the display’s startup and shutdown
commands. For more information, see “Specifying startup and shutdown commands” on
page 19-41.

Cached displays consume memory.

Once Windows consumes all physical memory, it is forced to swap to disk, which slows all
system activities. Always updating a cached display can add to communications overhead,
because data is retrieved for tags whose values might not be needed.

Setting up the title bar and other display attributes

You can set up a graphic display to have a title bar, so the operator can grab and move the
display at run time.
If you type a title for the display, it will appear in the title bar in place of the component
name. The title can be anything you want and can include spaces.
You can also insert variables into title bar text. For more information, see Chapter 24,
Creating embedded variables.
The following illustration shows the window style options that are available when you
select the Title Bar check box. To add or remove an item from the title bar, select or clear
the appropriate check box.
Maximize button

Title Minimize button

Title bar

System menu box Close button (comes

with System menu)

19-38
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Scaling the graphic display

You can set up a graphic display to resize automatically when it starts running, so it fits

19 • Placeholder
the size of the FactoryTalk View SE Client main window. When resized, the display is
panned or scaled, depending on which option you selected.
FactoryTalk View graphics are resolution independent. This means that no matter what
resolution you use to create graphic displays, they are resized automatically to suit the
monitor on which they are displayed at run time.

Showing the last known values of HMI tags

You can set up a graphic display to show 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 to display graphics more quickly.
At run time, if a display is not set up to show the last known value of HMI tags, objects
with values that have not yet been updated appear in outline form. The outline indicates
that data is not current, or is in error.
Graphic objects might appear in outline form the first time a display starts, if the HMI
tags used in the display are not initialized.
Once the tags are initialized and values arrive, the objects appear in their normal form.
However, if data is unavailable or in error, the objects will remain in outline form.

The last acquired value can be displayed for HMI tags only. For other kinds of tags, the last value
cannot be retained.

Setting the update rate for tags

The maximum tag update rate is the fastest rate at which data servers can send tag value
changes to the graphic display.
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.
The default update rate is 1 second. This means that data servers will not send tag value
updates faster than once every second.

Preventing scroll bars on the main window

If a graphic display is larger than the FactoryTalk View SE Client main window, scroll
bars will appear on the window when the display is started.
The scroll bars will remain on the window, even if subsequent displays are small enough
that scroll bars are not needed.

19-39
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To minimize the need for scroll bars, the FactoryTalk View SE Client tries to position all
graphic displays within its main window, unless this placement is explicitly overridden by
the /X and /Y parameters of the Display command.
To prevent scroll bars, create all graphic displays smaller than the working area in the
FactoryTalk View SE Client main window.
Keep in mind that the size of the working area depends on several factors: the monitor’s
display resolution, whether the display has a title bar, the size of the client window, and
whether the client shows the Diagnostics List.
To ensure that the FactoryTalk View SE Client main window never has scroll bars, for
large displays, select the option, Size to Main Window at Runtime.

For smaller graphic displays not meant to fill the client window, do not use Size to Main Window
at Runtime, to avoid scroll bars. Instead, position smaller displays so that they are completely
visible within the client window.

Specifying the display’s position

Instead of setting up a graphic display to use its current size and position, you can specify
an exact size and position for the display at run time.
If you do this, you can override the display settings by using size and position parameters
with the Display command. For details, see the FactoryTalk View Site Edition Help.

Securing the graphic display

To restrict access to a graphic display, select a security code. For more information about
securing graphic displays, see Chapter 5, “Setting up security,” in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

Setting up the run-time behavior of a graphic display

In the Behavior tab of the Display Settings dialog box, you can specify:
„ startup and shutdown commands.
„ colors for input fields.
„ the behavior of interactive objects, such as push buttons.
„ the behavior of objects with input focus.
„ whether an on-screen keyboard is available, for systems that do not have a hardware
keyboard attached to them at run time.

19-40
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

19 • Placeholder
In the Behavior
tab, set up how
objects in the
display behave
at run time, and
specify startup
and shutdown
commands.

Specifying startup and shutdown commands

To run commands when the graphic display starts or stops running, specify display startup
and shutdown commands, or macros.
If you use the Always Updating option with the Cache After Displaying option, the
startup command is run when the display is loaded into the cache.
The shutdown command is run only when the cache is flushed. This happens when:
„ the FlushCache command is run.
„ a user logs off the FactoryTalk View SE Client.
„ the FactoryTalk View SE Client is closed.

19-41
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

For details about the FlushCache command, see the FactoryTalk View Site Edition Help.

The startup command runs before the display opens, so commands such as UploadAll or
RecipeRestore will not work as startup commands or in a startup macro.
The shutdown command runs after the display closes, so commands such as DownloadAll or
RecipeSave will not work as shutdown commands or in a shutdown macro.

Specifying colors for input objects

At run time, an operator can use input objects to read values from or write values to
programmable controllers and other devices.
You can select the color an input object will have when selected, when not selected, and
when there is an operator input error.
Text color is the color of the text in the input object. Fill color is the background color of
the input object. To select a color, click the colored box to open a palette, and then click a
color to apply.
Choose colors for input objects that will stand out from the background color of the
display. Also choose different colors for selected objects, so that an operator can tell when
an object is selected, and when it is highlighted (see the next sections).

Specifying the behavior of interactive objects

Interactive objects are objects an operator can interact with at run time, using a mouse,
keyboard, or touch screen. A button with a press action is an example of an interactive
object.
You can specify whether interactive objects in a graphic display beep when pressed,
whether they have a highlight box when the mouse passes over them, and what color the
highlight will be.

Specifying the behavior of objects with input focus

Objects with input focus are ready to accept keyboard or mouse input.
You can specify whether objects with input focus in a graphic display have a highlight
box, and what color the highlight will be.

Using both types of highlight in the same display

You can choose to highlight only interactive objects, only objects with input focus, or both
types of object.
An interactive object is highlighted when the mouse passes over it. An object that can take
input focus is highlighted when it has focus. It is possible for one object to show both
types of highlight at the same time.

19-42
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

The following illustration shows what the two types of highlight might look like in a
graphic display.

19 • Placeholder
This interactive
object is highlighted
because the pointer
is resting on it.

This input object is

highlighted because
it has focus, as the
cursor indicates.

When selecting highlight colors, be sure to pick colors that stand out from the background
of the display.

Displaying the on-screen keyboard

To display a keyboard at run time, to interact with numeric input, string input, and recipe
objects in the graphic display, select the check box, Display On-screen Keyboard.
The on-screen keyboard is typically used with systems that do not have a hardware
keyboard, such as systems that only use touch screens.
When the operator clicks or touches the selected object, or presses Enter on a hardware
keyboard, the on-screen keyboard is presented.
The keyboard for string input and recipe fields allows alphanumeric entry. The keypad for
numeric input fields allows numeric entry only. For more information, see page 20-23.

Setting up displays to open more quickly

Graphic displays open more quickly if they are stored in the display cache. You can place
up to 40 graphic displays in the cache.
To cache a display, use one of these methods:
„ Use the Cache After Displaying option in the Display Settings dialog box. For details,
click Help in the dialog box.
„ Use the [cache] parameter with the Display command.
The [cache] parameter loads a graphic display into the cache without displaying it.
The parameter has two options:

19-43
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ /Z loads the graphic display into the cache without opening it. When the display is
called up subsequently, it opens quickly.
„ /ZA loads the display into the cache and continually updates the values in the
display, even when the display is not visible.
For details about the Display command, see the FactoryTalk View Site Edition Help.

Removing displays from the cache

To remove all graphic displays from the display cache, run the FlushCache command, or
close the FactoryTalk View SE Client.
To remove a specific graphic display from the cache, run FlushCache <file>, where <file>
is the name of the display you want to remove. For details, see the FactoryTalk View Site
Edition Help.
If a graphic display uses the Always Updating option with the Cache After Displaying
option, the display’s shutdown command is run when the FlushCache command is run, or
when you close the application.

Changing the default display settings

When you begin using the Graphics editor to create graphic displays for an application,
the values already specified in the Display Settings dialog box are used as default values.
For example, the Display Type property is set to Replace, the Title Bar property is
selected (meaning the display will have a title bar), and the Background Color property is
set to white.
All the new displays you create will have these initial default settings.

To change the default settings for new graphic displays

1. Create a new display, and change its display settings to the desired default values.

When you make certain changes, the Set as Default button changes to Apply. This lets you
apply the changes to the current display without closing the Display Settings dialog box.
It does not affect the default display settings.

2. Click OK to save the changes and to close the Display Settings dialog box.
3. Open the Display Settings dialog box again, and then click Set as Default at the
bottom of the dialog box.
The values selected for the previous display become default settings for new displays.

19-44
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

Docking displays to the FactoryTalk View SE Client window

19 • Placeholder
At run time, graphic displays can be docked to an edge of the FactoryTalk View SE Client
window, allowing an operator to gain access to certain displays at all times.
For example, you might consider docking:
„ navigational menus, that allow the operator to move among displays in an application.
„ headers or banners, that provide specific information to the operator, such as the
current user’s name and area, or information about alarms.
„ control panels, that contain standard buttons for special purposes, such as changing
users, closing open windows, or sending information to a maintenance team.

Display command parameters for docking displays

To dock graphic displays, run the Display command with any of the following parameters:

To dock a display in this position Use this parameter

Top edge of the client window /DT
Bottom edge of the client window /DB
Left edge of the client window /DL
Right edge of the client window /DR

To let an operator dock a graphic display, provide a button object in another display, that
uses the Display command with one of the docking parameters as its press action.
In the FactoryTalk View SE Client Wizard, you can also specify a docking parameter for
the initial display that runs when the client starts up.

The Display command parameters /B, /Min., /Max, /X, and /Y are ignored, if specified with one of
the docking parameters. For more information, see the FactoryTalk View Site Edition Help.

Example: Using the Display command to dock a display after the

FactoryTalk View SE Client starts up
To dock a display named Menu to the top edge of the SE Client window, after the client
starts up, create a button in the initial display that uses this command as its press action:
Display Menu /DT

When the operator presses the button, the display will attach to the top edge of the client
window.

19-45
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

About the appearance and behavior of docked displays

When you open a graphic display using one of the docking parameters, certain display
settings are ignored. For example, whatever is specified in the Displays Settings dialog
box, a docked display:
„ has no borders or scroll bars.
„ has no title bar (and therefore no minimize, maximize, or close buttons).
„ cannot be undocked or moved.
„ cannot be resized, independent of the FactoryTalk View SE Client window.

Changing the width of the client window changes the width of displays docked at the top or
bottom of the window. Changing the height of the window changes the height of displays
docked at the left or right.

If a graphic display is set up to pan or scale, to allow multiple running copies, or to cache
after displaying, these settings will still apply when the display is docked.

Docking multiple displays in the same position

You can also run more than one docked display in the same position, if the additional
displays are the Overlay or On Top type.
For example, if you use /DT to dock a menu to the top of the client window, and then use
/DT to open another display, as long as the second display is of the type Overlay or On
Top type, it will run directly beneath the first.
If you dock a Replace type of display, it will close any other displays running in the same
position. For more about display type, see page 19-36.

Running other displays in the available client area

The size and position of docked graphic displays in the FactoryTalk View SE Client
window determines where in the window other graphic displays can run.
For example, if you dock a display named Menu at the top of the SE Client window, and
then run a display named Line1, it will run in the area not occupied by the docked display.
If Line1 is larger than the available client area, scroll bars will be provided for gaining
access to the hidden portion of the display.
If you opened Line1 first, and then ran the Menu display with a docking parameter, Line1
would be repositioned in the client window, to accommodate the Menu display.
In the following illustration, the FactoryTalk View SE Client window contains three
docked menus (top, left, and bottom), and a graphic display named Primary Treatment is
running in the available client area.

19-46
 • • • • •
19 • CREATING GRAPHIC DISPLAYS

19 • Placeholder
The menu at the top
was docked initially,
when the FactoryTalk
View SE Client started.

The languages (left)

and navigation (bottom)
menus were docked in
that order, by clicking
buttons on the initial
display.

The Primary Treatment

display was opened
from the navigation
menu.

Closing docked displays

Use the Abort command to close docked displays individually, or to close all docked
displays, and any other displays running in the FactoryTalk View SE Client window.

Docked displays, along with any other running displays, will also close when the Logout
command is run, or when the FactoryTalk View SE Client logs off automatically.

Example: Closing an individual docked display

To provide the operator with a way to close a docked display named Menu, create a button
in the display that uses this command as its press action:
Abort Overview

When the operator presses the button, the Menu display will close.

19-47
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Example: Closing all docked displays

To provide the operator with a way to close all docked displays, along with any other
displays running in the FactoryTalk View SE Client window, create a client key that uses
this command as its press action:
Abort * /D

When the operator presses the key, all running displays will close.

The Abort command’s /D parameter, which closes any docked displays, is valid only when used
with Abort *.

Printing displays at run time

To let an operator print graphic displays at run time, when you create the displays, provide
a way for the operator to run the PrintDisplay command.
For example, create a button object, display key, or client key with the PrintDisplay
command as the press action.
When you use the PrintDisplay command, FactoryTalk View prints the entire display,
even if parts are covered by other displays. You can use the ScreenPrint command to print
an image of whatever shows on the monitor.
For more information about the PrintDisplay and ScreenPrint commands, see the
FactoryTalk View Site Edition Help.

19-48
20 Creating graphic objects

20 • Placeholder
This chapter describes how to use, create, and set up the graphic objects available in
FactoryTalk® View Site Edition (also called FactoryTalk View SE).
For information about using the Graphics editor, and creating and setting up graphic
displays, see Chapter 19, Creating graphic displays.

Types of graphic objects in FactoryTalk View SE

In FactoryTalk View Studio, in the Graphics editor, you can create the following types of
graphic objects:
Drawing objects are geometric and freehand objects, images, panels, and text. Drawing
objects are the only FactoryTalk View graphic objects that do not use data connections.
For more information, see “Creating the different types of drawing objects” on page 20-4.
Push button objects are typically used to start or stop processes or actions. For more
information, see “Creating the different types of push buttons” on page 20-11.
Numeric and string objects are used for entering or displaying numbers or text. For
more information, see “Creating the different types of data display and input objects” on
page 20-19.
Indicator objects display the status of a process or operation by showing colors,
captions, images, or options to indicate different states. For more information, see
“Creating the different types of indicators” on page 20-25.
Gauge and graph objects show a range of values, and relationships between variables.
For more information, see “Creating the different types of gauges and graphs” on
page 20-27.
Key objects represent keys on a keyboard, and are for use with touch screens. For more
information, see “Using key objects to simulate keyboard functions” on page 20-29.
Advanced objects, such as trends and HMI tag alarm summaries, allow an operator to
monitor, analyze, and interact with application data. For more information, see “Creating
the different types of advanced objects” on page 20-31.
Some of the advanced objects are described in detail in other parts of this manual. For
information about creating:
„ HMI tag alarm summaries, see page 11-30 in Volume 1 of the FactoryTalk View Site
Edition User’s Guide.
„ trend objects, see Chapter 26, Setting up trends.

20-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Alarm and Event objects such as the alarm and event summary and the alarm status
explorer, allow FactoryTalk View SE users to monitor and control FactoryTalk Alarms
and Events.
For information about the Alarm and Event objects, see Chapter 12, “Setting up
FactoryTalk alarms,” in Volume 1 of the FactoryTalk View Site Edition User’s Guide.
OLE objects such as spreadsheets, charts, or text, are produced by other Windows®
applications. The OLE objects that are available depend on the software installed on the
system. For information, see “Working with OLE objects” on page 20-51.
ActiveX® objects such as gauges, or sliders, can be created using a tool like Visual
Basic®, or purchased from a third-party vendor. They allow an external action, such as a
mouse click, to initiate an action in FactoryTalk View.
For more information, see “Working with ActiveX objects” on page 20-53, and
“Animating ActiveX objects” on page 21-22.

About global objects

FactoryTalk View global objects allow you to link the appearance and behavior of one
graphic object to multiple copies of that object in the same application.
Any graphic object you can create in FactoryTalk View can be a global object, except for
ActiveX controls, OLE objects, and HMI tag alarm summaries. For details, see:
„ “Creating global objects” on page 20-46.
„ “Setting up the link properties of reference objects” on page 20-48.
For more information about global object displays, see Chapter 19, Creating graphic
displays.

Setting up the properties of graphic objects

After creating a graphic object, you can use the Properties dialog box to set up its
appearance and behavior.

Opening the Properties dialog box

To open the Properties dialog box for an object, use one of these methods:
„ For some objects, the Properties dialog box opens directly, when you create the object.
„ For other objects, you open the Properties dialog box by double-clicking the object
after you create it.
„ You can also right-click the object, and then click Properties.

20-2
 • • • • •
20 • CREATING GRAPHIC OBJECTS

The following illustration shows the Properties dialog box for a polygon object.

20 • Placeholder
In the Properties dialog box, the features of the object are organized in tabs. The number
of tabs and their contents depend on the type of object. For details about options in any
Properties dialog box, click Help.

Setting up properties common to all objects

There is a Common tab in the Properties dialog box for every FactoryTalk View graphic
object. Use the Common tab to set up these properties for the object:
„ height and width
„ top and left position
„ name
„ tooltip
„ visibility
For ActiveX objects, trends, and Alarm and Event objects, you can also set up these
properties:
„ focus highlight
„ pointer highlight
„ key navigation
„ tab index

20-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Creating the different types of drawing objects

To draw simple objects such as lines, rectangles, and ellipses, in the Graphics editor,
select drawing tools from the Objects menu or toolbar.
The drawing tool for an object has the name of the object. To draw a rectangle or square,
for example, select the Rectangle tool.
After selecting a drawing tool, draw the object by dragging the tool, or by clicking end
points. You can draw rectangles, ellipses, and arcs only by dragging; you can draw
polylines and polygons only by clicking end points.

Drawing a rectangle or square

Use the Rectangle tool to draw a rectangle or square.

Rectangle tool To draw a rectangle

„ Drag the Rectangle tool diagonally, until the rectangle is the desired size.

To draw a square
„ Press Ctrl while you drag the Rectangle tool.

Drawing a rounded rectangle

Use the Rounded Rectangle tool to draw a rectangle with rounded corners.

Rounded To draw a rounded rectangle

rectangle tool
„ Drag the Rounded Rectangle tool diagonally, until the rounded rectangle is the desired
size.

To change a rounded rectangle into a right-angle rectangle

1. Position the pointer on the small box displayed inside the rounded rectangle.
If the box is not visible, right-click the rounded rectangle, and then click Edit.
2. Drag the drawing tool until the rectangle is the desired shape.

20-4
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Drawing a polyline or polygon

20 • Placeholder
A polyline is a series of connected line segments. A polygon is a closed polyline shape.

Polyline tool

Polygon tool
Polyline Polygon Filled

To draw a polyline or polygon

1. Drag the Polyline or Polygon tool to create the first segment of the object.
To draw horizontal or vertical lines (not diagonal lines), press Ctrl while you drag.
2. Release the mouse button.
3. Move the Polygon or Polyline tool to where the angle of the object is to be, and then
click the left mouse button.

Repeat this step until the object is completed.

4. To finish drawing, click the Select tool.

Drawing an ellipse or circle

Use the Ellipse tool to draw an ellipse or circle.

Ellipse tool To draw an ellipse

„ Drag the Ellipse tool diagonally, until the ellipse is the desired size.

To draw a circle
„ Press Ctrl while you drag the Ellipse tool.

20-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Drawing an arc or wedge

Arcs and wedges are drawn in two steps: first you create an ellipse or circle, and then you
reshape the ellipse or circle.
Arc tool

Arc Hollow wedge Filled wedge

Wedge tool
You can also use the Arc and Wedge tools to reshape existing arcs, ellipses, or wedges.

To draw the arc or wedge

1. Drag the Arc or Wedge tool to draw a circle.
2. Release the mouse button.
3. Click a handle, and drag the Arc or Wedge tool to ‘cut out’ part of the circle.

.
To draw the arc or wedge in 45-degree increments, press Ctrl while you draw.

Changing the properties of drawing objects

You can change the properties of drawing objects:
„ in the object’s Properties dialog box.
„ in the Property Panel. For details, see page 19-5.
„ using the Foreground Color and Background Color palettes, and the Pattern Style
toolbar. For details, see page 19-17.
All drawing objects, except for text, image, and panel objects, have the same properties.
Line objects do not take patterns.
For details about setting up a drawing object, click Help in its Properties dialog box.

To open the Properties dialog box

„ Double-click the object.
You can also right-click the object, and then click Properties.

20-6
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Creating text objects

20 • Placeholder
Use the Text tool to draw a text object. You can then create the text and set up its
appearance in the Text Properties dialog box.
Text tool
Choosing text fonts
You can choose a font before or after you create text, and change the font of any object,
including objects that display data or have captions.
When choosing a font, style, size, and color for text, keep the following design principles
in mind:
„ Choose a font that was designed for on-screen viewing. Examples include Arial, Arial
Narrow, Trebuchet MS, and Verdana. You can download these and other fonts free of
charge, from the Microsoft® Typography web site.
„ TrueType™ and OpenType® fonts are recommended because they can be resized
easily, without losing text quality.
„ Choose only one or two fonts, and use them for all the graphic displays in an
application.
„ Choose a font size that can be read easily. Test the font size, and adapt it to the screen
resolution the operator will see at run time.
„ To save screen space, use a condensed font such as Arial Narrow, that fits more
characters per line, rather than reducing the font size.
„ Sans-serif typefaces are easier to read at small sizes and lower resolutions on the
screen than serif typefaces. For example, for normal text use Arial rather than Times
New Roman.
„ Use high-contrast color combinations, such as yellow on blue, rather than low-
contrast combinations like black on green.
„ Use colors with recognizable meanings. For example, in some countries the colors red
and green mean stop and start.
Keep color meanings consistent by assigning red only to Stop buttons, and green only
to Start buttons.
„ Ensure that the fonts used in graphic displays are installed on all computers where the
displays will run.
If a font is not installed, Windows substitutes one that is installed, possibly with
unsatisfactory results.

20-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Creating a panel
Use the Panel tool to draw rectangles and squares that have borders.
The panel object supports visibility animation. You can also set up panel objects to blink
Panel tool
at run time. For details, click Help in the Panel Properties dialog box.

Adding images into graphic displays

To add an image into a graphic display, you can:
„ place an image to be used in several displays.
„ import an image that is not in the Windows bitmap format (.bmp).
„ paste an image copied from another application.

Placing images in graphic displays

Use the Image tool to place a bitmap or jpeg image in a graphic display.
If the image is not a bitmap or jpeg file, you must use image editing software to convert it
Image tool
to one of those formats before you can place it in a graphic display.
If the image is monochrome (1 bit per pixel, 2 colors), you can change its color,
background color, and transparency, and you can make it blink at run time.
For monochrome images, the background color becomes transparent when you change the
Image back style to Transparent.
For color images, any area of the image that is black becomes transparent when you
change the Image back style to Transparent.

Adding images to an application

Images you add to an application can be inserted in graphic displays over and over again.
If you modify the original image, all displays that use the image are updated
automatically.
To add an image you want to use in several displays, add it to the application using the
Image tool, or add the image to the Images folder in FactoryTalk View Studio, in the
Explorer window.
When you add an image using the Image Browser, the image appears automatically in the
Explorer window, and vice versa.
You can add an image to an application when you place it in a graphic display or before
you place it in the display. For more information, click Help in the Image Browser.

20-8
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Importing images into graphic displays

20 • Placeholder
FactoryTalk View can read .bmp and JPEG (.jpg, .jpeg, .jpe, .jif, .jfif) files in their
original format, without requiring conversion.
When you import an image, FactoryTalk View converts .gif, .tif, .pcx, and .jpg images to
the Windows .bmp format. Vector images in .dxf and .wmf formats are converted to
FactoryTalk View graphic objects.
For details, see “Importing graphic files from third-party applications” on page 19-27.
For information about bitmap files, and about choosing graphic file formats for best
performance, see page 19-28.

Pasting images into graphic displays

You can also add an image to a graphic display by copying the image to the Windows
clipboard from another application, and then pasting it into the display.
To paste an image from the clipboard, open the display in the Graphics editor, and then, on
the Edit menu, click Paste Special.

Techniques for working with objects that use data

Graphic objects that an operator can interact with at run time, using a mouse, keyboard, or
touch screen, are called interactive objects.
Examples of interactive objects are a numeric input object, a button that has a press
action, and a rectangle object with touch animation.

Specifying tag names

At run time, interactive objects obtain data from tags. When creating interactive objects,
you specify the name of the tag (or a tag placeholder) that will supply the object with data.

Supplying a tag name

To supply a tag name for an object that uses data, when creating the object you can:
„ type the name of the 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.
„ click the Browse or Tags button (whichever is available) to open the Tag Browser and
select or create the tag.
For more information about working with tags and the Tag Browser, see Chapter 9,
“Working with tags,” in Volume 1 of the FactoryTalk View Site Edition User’s Guide.

20-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Determining which objects have input focus

At run time, the object with focus in a graphic display is surrounded by a highlight box,
unless the check box, Disable Highlight When Object has Focus, is selected in the Display
Settings dialog box for the display.
In the Display Settings dialog box, you can also specify the highlight color. For more
information, see “Specifying the behavior of objects with input focus” on page 19-42.
Highlight box
Focus highlight for ActiveX and trend objects
For ActiveX and trend objects, use the Common tab in the object’s Properties dialog box
to specify whether to display a highlight.
If the check box, Disable Highlight When Object has Focus, is selected for the graphic
display, that setting overrides what is specified for the ActiveX or trend object, in its
Properties dialog box.

Using the keyboard to select objects that can take focus

If a mouse or touch screen is not connected to the computer at run time, the operator can
use the keys on a keyboard or keypad to select (give focus to) these objects:
„ push button objects
„ numeric and string input objects
„ control list selectors, piloted control list selectors, and display list selectors
„ trends and HMI tag alarm summaries
„ FactoryTalk Alarm and Event objects, including alarm and event summaries, banners,
status explorers, and the log viewer.
„ third-party ActiveX input objects
Use the following keys to move to and select a different object:

To do this Press
Move from the upper left to the lower right Tab
Move from the lower right to the upper left Shift+Tab
Move left, right, up, or down Ctrl+arrow key

When a graphic display opens, of the objects that can have input focus, the object that has
a tab index of 1 is selected initially.

If all of the objects in a display are continuously updating input objects, none of the objects will
receive initial focus. Instead, the operator must select an input object to give it focus. For more
information, see “Updating tag values continuously” on page 20-21.

20-10
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Removing objects from the tab sequence

20 • Placeholder
By default, you can use the Tab and arrow keys to navigate to objects that can have input
focus in a graphic display.
You can also turn off key navigation for objects that take input focus, except for push
buttons, recipe objects, input objects, and HMI tag alarm summaries.
When an object’s key navigation is turned off, an operator can still select the object using
a mouse or touch screen, if one is available.

Turning off key navigation

To turn off key navigation, use one of these methods:
„ For display list and control list selectors, open the object’s Properties dialog box, click
the General tab, and then clear the check box, Key navigation.
„ For ActiveX objects, trends, and Alarm and Event objects, open the object’s
Properties dialog box, click the Common tab, and then clear the check box, Key
navigation.
„ In the Property Panel for the object, click the Properties tab, and then set the
KeyNavigation property to False.

Creating the different types of push buttons

Push buttons start or stop processes or actions and change tag values. You can create the
following types of push buttons, depending on the needs of the application:
Button objects can change tag values, or run FactoryTalk View commands.
Momentary push buttons change a tag to one value when the button is pressed, and
another value when the button is released.
Momentary push buttons work like the Pulse button on a food processor, but with an
indicator light to signal whether the motor is running or stopped. The machine is on only
while the button is held down. When the button is released, the machine turns off.
Momentary push buttons are useful for jogging a motor, and they can be set up to start and
stop a machine or process.
Maintained push buttons switch between two values.
This type of button is useful for changing a setting within a machine or process, but not
for starting the machine or process. For example, use the maintained push button for
changing modes, such as Auto to Manual, or Metric to Imperial.

20-11
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Latched push buttons lock in the on position, and must be unlocked by another button or
process to return to the off position. This type of button is useful for starting a machine or
process.
Multistate push buttons allow an operator to cycle through multiple options
consecutively, using a single button that displays the current state of a process or
operation. Each state can be represented by a different color, caption, or image.
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.
Ramp push buttons increase or decrease the value of a tag by either an integer or floating
point value. You can use two ramp buttons together to create an increase/decrease control,
for example for the speed of a motor.
For details about setting up a push button, click Help in the object’s Properties dialog box.

Never use push buttons for emergency stops. Always hard-wire emergency stop buttons.

Creating button push buttons

Use the Button tool to create push buttons that work like standard Windows buttons.
You can assign FactoryTalk View commands to buttons, so they trigger actions when
Button tool
pressed and released.
You can also attach different types of animation to a button, except for fill, rotation and
touch animation. For more information, see Chapter 21, Animating graphic objects.

Setting up button properties

In the Button Properties dialog box:
„ in the General tab, specify general characteristics of the button including style, index
number, runtime focus highlight, and whether the cursor is captured when the button
is pressed.
„ in the Action tab, set up how the button will behave when the user presses, holds, and
releases it at run time.
„ in the Up Appearance tab, specify what the button looks like when it is not pressed.
„ in the Down Appearance tab, specify what the button looks like when it is pressed.

20-12
 • • • • •
20 • CREATING GRAPHIC OBJECTS

20 • Placeholder
Creating momentary push buttons
Use the Momentary Push Button tool to create a button that starts a process or action.
A momentary push button changes a tag to one value when pressed, and to another value
Momentary
Push Button
when released. You can specify values for the press and release actions, or the momentary
tool push button can have these states:
„ Normally open means the released state of the button is off: when the button is
pressed, the tag’s value is set to 1; when the button is released, the tag’s value is set to
zero. Pressing the button completes the circuit.
„ Normally closed means the released state of the button is on: when the button is
pressed, the tag’s value is set to 0; when the button is released, the tag’s value is set
to 1. Pressing the button breaks the circuit.

Setting up momentary push button properties

In the Momentary Push Button Properties dialog box:
„ in the General tab, specify the general appearance for all states of the momentary
push button at run time, and what type of action the button performs.

20-13
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ in the States tab, specify the appearance and behavior of the button for each state,
when it is pressed and released.
„ in the Connections tab, specify the tags or the expression the button will use for
transferring data.

Creating maintained push buttons

Use the Maintained Push Button tool to create a button that changes a setting in a machine
or process.
Maintained
Push Button When first pressed, the maintained push button changes a tag to one value. When pressed
tool and released a second time, the button changes the tag to another value.
Maintained push buttons are not useful for starting or stopping a machine or process.

20-14
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Setting up maintained push button properties

In the Maintained Push Button Properties dialog box:

20 • Placeholder
„ in the General tab, specify the general appearance and touch margins of the button,
how it changes states, and whether an audio signal is produced when it is pressed.
„ in the States tab, specify the appearance and behavior of the button for each state,
when it is pressed and released.
„ in the Connections tab, specify the tags or the expression the button will use for
transferring data.

Creating latched push buttons

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 return to the off position. This type of
Latched button is useful for starting a machine or process.
Push Button
tool The Handshake tag must be set back to zero before the operator can press the latched push
button again.

20-15
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Setting up latched push button properties

In the Latched Push Button Properties dialog box:
„ in the General tab, specify the general appearance and touch margins of the button,
its latch reset type, and whether an audio signal is produced when it is pressed.
„ in the States tab, specify what the button does when it is latched and unlatched.
„ in the Connections tab, specify the tags or the expression the button will use for
transferring data.

Creating multistate push buttons

Use the Multistate Push Button tool to create a button that allows an operator to view and
cycle through multiple options consecutively.
Multistate
Push Button
The multistate push button displays the current state of a process or operation, by showing
tool 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. If
the button is in its last state when the operator presses it, the button returns to its first state.

20-16
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Setting up multistate push button properties

In the Multistate Push Button Properties dialog box:

20 • Placeholder
„ in the General tab, specify the general appearance and touch margins of the button,
how it changes states, and whether an audio signal is produced when it is pressed.
„ in the States tab, specify what the button does when it is pressed and released.
„ in the Timing tab, set up whether the button is to repeat automatically when the
operator presses and holds it down. You can also set up repeat rate for the button.
„ in the Connections tab, specify the tags or the expression the button will use for
transferring data.

About the run-time error state

Momentary, maintained, latched, and multistate push buttons display an error state when:
„ the Value tag is unassigned.
„ the display opens, if the Value tag does not match one of the specified state values.
„ the Indicator tag or expression does not match one of the specified state values.
For details about push button states, click Help in the Properties dialog boxes.

Creating interlocked push buttons

Use the Interlocked Push Button tool to create multiple buttons, one at a time, that work
together in a group and share the same tag.
Interlocked
Push Button The buttons work together like the preset station selector buttons on a car radio: pressing
tool one button cancels another. When the operator presses one of the interlocked push
buttons, the button’s 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.

Setting up interlocked push button properties

In the Interlocked Push Button Properties dialog box:
„ in the General tab, specify the general appearance and touch margins of the button,
its value, and whether an audio signal is produced when it is pressed.
„ in the States tab, specify what the button does when it is pressed and released.
„ in the Connections tab, specify the tags or the expression the button will use for
transferring data.

20-17
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Creating ramp push buttons

Use the Ramp Button tool to create a button that an operator can use to increase or
decrease the value of a tag.
Ramp
Push Button Ramp push buttons can change a tag by either an integer or floating point value. You can
tool 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.
Some data servers do not impose a minimum or maximum limit on the value of a tag. Set
the upper and lower limits of the ramp push button to limit the range of values the
operator can send to the data server

Setting up ramp push button properties

In the Ramp Push Button Properties dialog box:
„ in the General tab, specify the general appearance of the button, the action the button
performs, and whether an audio signal is produced when it is pressed.
„ in the Label tab, create a caption and select an image for the button.

20-18
 • • • • •
20 • CREATING GRAPHIC OBJECTS

„ in the Timing tab, set up whether the button action will repeat automatically, when
the operator holds the button down. You can also set up the repeat rate.

20 • Placeholder
„ in the Connections tab, specify the tags or the expression the button will use for
transferring data.

Creating the different types of data display and input objects

Data display and input objects allow an operator to view or change tag data. You can
create the following types of data display or input objects:
Numeric and string display objects allow an operator to view tag or expression
values in a graphic display at run time. Use display objects to show numeric values or text
that the operator does not need to modify.
Numeric and string input objects allow an operator to read or write tag values at run
time.

20-19
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

An input object can also be set up to display a tag’s current value, when the object is not
being used to download or upload data.
This eliminates the need to create separate input and display objects for a single tag. For
more information, see “Updating tag values continuously” on page 20-21.
For details about setting up a data display or input object, click Help in the object’s
Properties dialog box.

Using input objects to retrieve and send data

An operator can use numeric and string input objects to retrieve data from and send data
to the value table, so it can be used by programmable controllers, external OPC ® servers
or DDE devices, or FactoryTalk View memory.

12345

To download data, the operator types Programmable

a number into the input object, and controller
then presses PgDn or Enter.

12345

To upload data to the input object, Programmable

the operator presses PgUp. controller

If a graphic display contains several input objects, the operator can select a single object
and then read or write a value, or read or write values for all objects in the display at once.

20-20
 • • • • •
20 • CREATING GRAPHIC OBJECTS

The operator can also retrieve a series of values from a recipe file, change them, write the
changed values back to the programmable controller, and then save them to a recipe file.

20 • Placeholder
For more information about recipes, see “Creating and restoring recipes” on page 20-36.

Tag-related limits
Each graphic display in an application can contain up to 3000 references to expressions
or tags (HMI tags and data server tags). This limit includes the tags contained in
embedded variables.
The limit also includes duplicate references. For example, one display can contain only
3000 numeric inputs that refer to tags, even if all 3000 objects refer to the same tag.

Updating tag values continuously

You can set up a numeric or string input object to display a tag’s value and update the
value continuously. At run time, the appearance of a continuously updating input object
changes to reflect which mode it is in.
When the input object is displaying a value from the programmable controller or server, it
has a dotted border:

This is called display mode.

When a value is entered in the input object, but the value is yet to be downloaded, it has a
solid border:

This is called pending write mode.

When the input object is ready to receive input, it has a solid border surrounded by a
highlight box:

This is called input mode (or input focus).

At run time, when a graphic display containing input objects is opened, the first non-
updating object in the index sequence receives focus.

20-21
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

If all the input objects in the display are set to update continuously, none of the objects
will receive initial focus. Instead, the operator must select an object to give it focus.
After selecting an input object, the operator can upload a value or restore a recipe into the
object. If an upload fails because of a communication error, the input object appears in
outline form.
To return to the input object to display mode, press ESC.

Validating operator input

To validate operator input, you can specify minimum and maximum values for numeric
input objects.
At run time, if the operator attempts to download a value outside the valid range, the input
object changes color, an error message is logged to the Diagnostics List, and the download
is canceled.
To define the minimum and maximum, in the Connections tab of the Numeric Input
Properties dialog box, specify a tag, expression, or number for each value.

In the Displays Settings dialog box, you can select the colors input objects will become
when operator input errors occur. For more information, see “Setting up the run-time
behavior of a graphic display” on page 19-40.
Alternatively, you can use the graphic Display object’s event BeforeInputFieldDownload,
to validate input objects before downloads occur. For information about VBA and the
Display object, see the FactoryTalk View Site Edition Help.

Shortcut keys for retrieving and sending data

An operator 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 objects that are in pending write mode (in
the active graphic display) to the value table.
„ Ctrl+PgDn downloads the contents of the selected input object to the value table.

20-22
 • • • • •
20 • CREATING GRAPHIC OBJECTS

„ Enter downloads the contents of the selected input object to the value table

20 • Placeholder
If the graphic display is set up to use the on-screen keyboard, pressing Enter brings up
the on-screen keyboard.

To prevent an operator from using Enter to download values, or to open the on-screen
keyboard, use the /E parameter with the Display command to open the graphic display.
This turns off the Enter key.

„ PgUp uploads all values from the value table and then displays them in the input
objects in the graphic display.
„ Ctrl+PgUp uploads a value from the value table for the selected input object.
„ Tab moves among input objects.

FactoryTalk View commands for retrieving and sending data

An operator can use the following commands to retrieve data from and send data to the
value table:
„ Download downloads the contents of the selected input object to the value table.
„ DownloadAll downloads the contents of all input objects that are in pending write
mode to the value table.
„ Upload uploads a value from the value table and displays it in the selected input
object.
„ UploadAll uploads all the values from the value table and displays them in the input
objects.
To let an operator use these commands, assign them to FactoryTalk View button objects in
the graphic display. For more information, see the FactoryTalk View Site Edition Help.

Parts of the on-screen keyboard

You can set up graphic displays so that the operator can use an on-screen keyboard for
input entry in recipe, string, or numeric input objects.
The keyboard that opens for string input and recipe objects (shown in the following
illustration) allows alphanumeric entry.
The keypad that opens for numeric input objects allows numeric entry only.

20-23
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Characters typed in the on-screen keyboard are transferred to the selected input object
when the operator presses Update Field or Download in the on-screen keyboard, or
presses Enter on a hardware keyboard.

To do this Press
Close the on-screen keyboard and store the new value in the Update Field
input object for a subsequent download.
For numeric and string input objects, close the on-screen Download
keyboard and download the value or text the operator typed.
For recipe objects, close the on-screen keyboard, open the
Recipe dialog box, and insert the text the operator typed, into the
Recipe File box.
Close the on-screen keyboard and discard the operator’s Cancel
changes.

For more information about the on-screen keyboard, see “Setting up the run-time behavior
of a graphic display” on page 19-40.

Creating numeric and string display objects

Use the Numeric Display and String Display tools to create objects that allow an operator
to view tag or expression data at run time.
Numeric and
String Display
In the Numeric Display or String Display Properties dialog box, specify the tag or
tools expression to display, and the appearance of the display object. For details about options
in the Properties dialog box, click Help.

20-24
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Creating numeric and string input objects

20 • Placeholder
Use the Numeric Input and String Input tools to create objects that allow an operator to
enter data for tags that accept numeric values, or text.
Numeric and
String Input In the Numeric Input or String Input Properties dialog box, specify the tag that the
tools operator is to interact with at run time, the appearance of the input object, and whether the
object will continuously update the tag’s value.
For details about options in the Properties dialog box, click Help.

Creating the different types of indicators

Indicators display the status of processes or operations by showing different colors,
captions, images, or options to reflect different states.
You can create the following types of indicators, depending on the needs of the
application:
Multistate indicators display the current state of a process or operation by showing a
different color, caption, or image to reflect different states.
Symbol indicators display a symbol that changes to match the state of a process or
operation. This allows the operator to see the status of a process or operation at a glance.
List indicators display a list of states for a process or operation, and highlight the current
state. Each state is represented by a caption in the list.
This allows the operator to view the current state and also see the other possible states. For
sequential processes, the list can inform the operator about what happens next.
For details about setting up an indicator object, click Help in the object’s Properties dialog
box.

Setting up states for indicators

Indicators change their appearance based on their states. In the States tab of the Properties
dialog box, you can specify how the indicator will look in each of its different states.
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 an available
state, none of the states is highlighted.

Set up states for an indicator object in the Connections tab of the Properties dialog box.

20-25
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Using the Least Significant bit to trigger states

The Least Significant Bit (LSB) trigger type changes the indicator’s state based on the
position of the lowest bit in the tag’s value. Any higher bit positions are ignored.
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).
You can use a programmable controller to set these bits individually.

Setting up connections for indicators

To connect with a device such as a programmable controller, indicators use a tag or
expression called the Indicator tag or expression.
The Indicator tag is similar to a pilot light on a hard-wired panel. The tag or expression
changes the indicator’s appearance for each of its states, providing visual feedback to the
operator. For example, the Indicator tag can show that a process is running or stopped.
Set up the Indicator tag or expression in the Connections tab of the Properties dialog box.

Creating multistate indicators

Use the Multistate Indicator tool to create an indicator that displays the current state of a
process or operation by showing a different color, caption, or image for each state.
Multistate
Indicator tool
In the Multistate Indicator Properties dialog box, specify state values for the multistate
indicator. For details about options in the Properties dialog box, click Help.
At run time, the multistate indicator displays the state whose value matches the Indicator
tag or expression’s value.

Creating symbols
Use the Symbol tool to create an indicator that displays a monochrome image that
changes color to match the state of a process or operation. This allows the operator to see
Symbol the status of a process or operation at a glance.
Indicator tool
In the Symbol Properties dialog box, specify state values for the symbol indicator, and the
image to be displayed for each state. For details about options in the Properties dialog
box, click Help.
At run time, the symbol indicator displays the state whose value matches the Indicator tag
or expression’s value.

20-26
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Creating list indicators

20 • Placeholder
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 to let an
operator view the current state and also see the other possible states. For sequential
processes, the list can inform the operator about what happens next.
In the List Indicator Properties dialog box, specify state values for the list indicator. For
details about options in the Properties dialog box, click Help.
At run time, the list indicator highlights the state whose value matches the Indicator tag or
expression’s value.

Creating the different types of gauges and graphs

Gauges and graphs provide graphical representations of numeric values.

Using gauges to show limits

Gauges display numeric values in dial format. Gauges are useful for displaying a value in
relation to its lower and upper limits.
For example, a temperature gauge shows the current temperature in relation to its
minimum and maximum extremes. By looking at the position of the needle on the gauge
(pointing left, up, or right), the operator can tell at a glance whether the temperature is
nearer its lower or upper limit, or nearer the middle.
Gauges are used instead of numeric displays when it’s important for the operator to
recognize an abnormal condition immediately, either from far away (when the scale on the
gauge isn’t visible), or before it is possible to make an exact reading on the gauge.

Changing a gauge’s fill color at different thresholds

As the needle sweeps higher on a gauge, the area below it can fill with a color. To help the
operator recognize abnormal conditions, you can set up a gauge to change its fill color
when the tag value crosses a threshold. For example:
„ if the temperature of an oven is lower than required for a recipe, the gauge can show
the temperature in blue.
„ 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.

20-27
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

If you use colored fills on a gauge, make sure enough of the fill is visible when an
abnormal condition occurs, to allow the operator to recognize the condition.

Some people are color blind to red and green, so don’t rely on color alone to establish meaning.

Using graphs to compare values

Graphs display numeric values in bar graph format.
Graphs are useful for comparing multiple values, or for representing the fill levels of tanks
that suit readings on a vertical scale.
Use graphs instead of numeric displays when it’s important for an 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 graph’s fill is green and the other’s is red, than it is to subtract one numeric value from
another.
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.

Changing a bar graph’s fill color at different thresholds

To help the operator recognize abnormal conditions, you can set up a graph to change its
fill color when the tag value crosses a threshold. For example:
„ if the level of the tank of ingredients is lower than the recipe requires, the graph can
show the tank’s level in red.
„ if the level of the tank is in the current range for the recipe, the graph can show the
level in yellow.
„ if the level is higher than the level the recipe requires, the graph can show the level in
green.

Showing limits using scales with bar graphs

Unlike gauges, bar graphs do not have integrated scales.
Instead, 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.

20-28
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Creating gauges

20 • Placeholder
Use the Gauge tool to represent a numeric value using a needle on a dial.
In the Gauge Properties dialog box, specify the maximum and minimum values of the
Gauge tool
gauge, and the tag or expression the gauge is connected to. For details about options in the
Properties dialog box, click Help.
At run time, the gauge indicates the value of the tag or expression in relation to the
gauge’s minimum and maximum values.

Creating bar graphs

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 In the Bar Graph Properties dialog box, specify the maximum and minimum values of the
bar graph, and the tag or expression the graph is connected to. For details about options in
the Properties dialog box, click Help.
At run time, the graph shows the value of the tag or expression in relation to the graph’s
minimum and maximum values.

Creating scales
Use the Scale tool to create a scale for a bar graph.
In the Scale Properties dialog box, specify the appearance of the scale. For details about
Scale tool
options in the Properties dialog box, click Help.
To place values on the scale as a legend, use text objects. Because the scale doesn’t
change at run time, you don’t need to connect it to a tag.

Using key objects to simulate keyboard functions

In the FactoryTalk View Graphics editor, the term ‘key’ can mean any of the following:
„ Key animation links a graphic object or display to a keyboard key or mouse button,
so that an operator can perform an action by pressing the key or mouse button. For
more information, see “Associating objects and displays with keys” on page 21-17.
„ The on-screen keyboard allows touch screen users to type numbers or text in input
objects without the need for a hardware keyboard.
To allow an operator to use the on-screen keyboard, select the check box Display on-
screen keyboard, in the Behavior tab of the Display Settings dialog box. For details,
see “Setting up the run-time behavior of a graphic display” on page 19-40.

20-29
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ Keys are graphic objects you place on a display to simulate the functions of keyboard
keys. This type of key can only be used with control list selectors, piloted control list
selectors, display list selectors, and trends.

Creating the different types of key objects

For control list selectors, display list selectors, piloted control list selectors, or trends, you
can create the following types of keys, depending on the needs of the application:
Backspace moves the cursor back to the highlighted item.
End moves to the bottom item of the page that is currently displayed. For trends, pressing
End resumes trend scaling and moves to the current or latest data in the trend.
Enter selects the item that is currently highlighted.
Home moves to the top item of the page that is currently displayed. For trends, pressing
Home pauses the trend and moves to the earliest data in the trend.
Move left pauses the trend and scrolls to the left.
Move right pauses the trend and scrolls to the right.
Move down moves down one item in the list. For trends, pressing Move down scrolls
down to display lower values on the vertical scale.
Move up moves up one item in the list. For trends, pressing Move up scrolls up to
display higher values on the vertical scale.
Page down moves down one page in the list.
Page up moves up one page in the list.
To create the different key objects, use the tools shown in this illustration:
Home Move up

End Move right Page up

Backspace Move left Page down

Enter Move down

In the Properties dialog box, the various features of the object are organized in tabs. For
details about options in each tab, click Help.

20-30
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Setting up the auto-repeat function for selected keys

All of the key objects have similar features, except that the move left, move right, move

20 • Placeholder
up, move down, page up and page down keys can be set up to auto-repeat.
In the Timing tab, set up whether the key press repeats automatically when the operator
presses and holds down the key. You can also set up the rate at which the key repeats. For
details, click Help.

Using the same set of keys with different graphic objects

If a graphic display contains more than one control list selector, piloted control list
selector, display list selector, or trend, you can use one set of keys to control all the
objects. You don’t have to set up a separate set of keys for each object.
To allow all the objects to use the same set of keys, create the key objects, and then, in the
General tab of each key’s Properties dialog box, select Object with Focus for the “Send
press to” option. For more information, click Help in the Properties dialog box.

Creating the different types of advanced objects

The FactoryTalk View advanced objects have various functions. You can create the
following types of advanced objects, depending on the needs of the application:
HMI tag alarm summary objects allow an operator to monitor and respond to HMI tag
alarm data.
Arrow objects track tag or expression values in a vertical or horizontal path.
Control list selectors allow an operator to select from a list of states, and write values
associated with those states.
Piloted control list selectors have the same function as control list selectors.
However, they can be controlled directly by an operator, or remotely by a device such as a
programmable controller.
Tag labels display information about a tag’s properties, such as the description,
engineering units, and minimum and maximum values.
Display list selectors allow an operator to select from a list of graphic displays.
Local message displays provide an operator with information, or prompts about what
to do next.
Recipe objects allow an operator to restore data from a recipe file, to input objects in a
graphic display.
Time and date displays show the current time and date.

20-31
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Trends provide visual representations, or charts, of real-time or historical data.

For information about creating:
„ an HMI tag alarm summary object, see Chapter 11, “Setting up HMI tag alarms,” in
Volume 1 of the FactoryTalk View Site Edition User’s Guide.
„ a trend object, see Chapter 26, Setting up trends.
For details about setting up any of the advanced objects, click Help in the object’s
Properties dialog box.

Creating arrows
Use the Arrow tool to create arrows that move based on a tag value or the result of an
expression. Arrows can move vertically or horizontally.
Arrow tool
Vertical arrows move up or down, and horizontal arrows move left or right, in relation to a
tag’s Low or High EU (Engineering Units).
For HMI tags, arrows can move in relation to the tag’s minimum and maximum values,
or values specified in the General tab of the Arrow Properties dialog box. For data server
tags, values must be specified in the General tab.
For vertical arrows, if the value is less than or equal to the minimum value, the arrow is at
the bottom of its range. 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 of its range. If the value is equal to or greater than the maximum value, the
arrow is at the right.

Creating tag labels

Use the Tag Label tool to display different types of tag information at run time.
In the Tag Label Properties dialog box, specify the tag associated with the label, and the
Tag Label
tool
property to display. For details about options in the Properties dialog box, click Help.
Some HMI tag properties have different names when displayed using a tag label. The
following table describes which properties correspond with the types of tag labels.

Corresponds For this

with the HMI type of
This tag label tag property HMI tag And displays
Low EU Minimum Analog A tag’s minimum value
High EU Maximum Analog A tag’s maximum value

20-32
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Corresponds For this

with the HMI type of

20 • Placeholder
This tag label tag property HMI tag And displays
Contact Value Status Digital The current status of a tag. When the tag value is 1,
‘On Label’ is displayed. When the tag value is 0, ‘Off
Label’ is displayed.
Engineering Units (EU) Units Analog A tag’s Units label
Tag Name Name All types A tag’s name
Tag Description Description All types A tag’s description
Contact Open Label Off Label Digital A tag’s Off label
Contact Close Label On Label Digital A tag’s On label

Creating time and date displays

A time and date display shows the current time and date. Use the Time and Date Display
tool to create a box that shows the time and date in a graphic display.
Time and
Date Display
In the Time Date Display Properties dialog box, specify the appearance of the object, and
tool the format in which the time and date appear. For details about options in the Properties
dialog box, click Help.

Creating display list selectors

Use the Display List Selector tool to create list of graphic displays in the application.
In the Display List Selector Properties dialog box, associate a different display with each
Display List
Selector tool
state. For details about options in the Properties dialog box, click Help.
At run time, to open a display, the operator selects the corresponding state, and then
presses Enter.

For network applications, display list selectors work with graphic displays located in the home
area only. For more information about the home area, see Chapter 6, “Working with network
applications,” in Volume 1 of the FactoryTalk View Site Edition User’s Guide.

Setting up states for a display list selector

To set up the states for a display list selector, decide how many graphic displays are to be
in the list, and then, in the States tab, add that number of states to the display list selector.
For each state, specify a display and a caption that identifies the display. This is what the
operator will see in the list at run time.

20-33
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Providing operator instructions in local message displays

Use local message displays to provide an operator with information about a process, or
about what to do next, at run time.
For example, you might provide messages that describe the status of a device whose
condition cannot be represented graphically with accuracy, or to tell the operator how to
deal with a specific situation when it arises.

Setting up local messages

These are the tasks involved in setting up local messages:
1. In the Local Messages editor, create a local message file that contains the messages to
display, and the trigger values for these message.
2. In a graphic display, create a local message display that presents a message when its
Value tag or expression matches a trigger value in the specified local message file.
You can use multiple local message display objects in a display, and link each object to a
different local message file. You can also use the same local message file for multiple
local message displays.
For more information about local messages, see the FactoryTalk View Site Edition Help.

Trigger values cannot be zero

The trigger value for a local message can be any non-zero integer value (positive or
negative). Trigger values do not need to be contiguous, but they must be unique for each
message. For example, you could use trigger values of 1, 2, and 3, or of 10, 20, and 30.
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.

What is displayed at run time

In the local message file, each message is associated with a trigger value. When the local
message display’s Value tag or expression matches the trigger value, the message
associated with the trigger is displayed.
At run time, a local message display shows one message at a time.
Special cases are handled in the following ways:
„ If the Value tag or expression is unassigned, the local message display is filled with
question marks (?).

20-34
 • • • • •
20 • CREATING GRAPHIC OBJECTS

„ The Value tag or expression is rounded to the nearest integer. If the value does not
match any of the trigger values in the message file, the local message display is filled

20 • Placeholder
with question marks (?).
„ If the message is too long to fit in the list, the last displayed character is replaced with
an asterisk (*).
„ When the Value tag or expression’s value is 0, the local message display is cleared.

Creating local message displays

Use the Local Message Display tool to create an object that displays predefined messages
at run time.
Local Message
Display tool
In the Local Message Display Properties dialog box, specify the message display’s Value
tag, and the related message file. For details about options in the Properties dialog box,
click Help.

Example: Setting up local messages

This example shows how to use local messages to notify the operator about the status of a
hoist.
1. Create an analog tag called Hoist_Status.
This tag points to an address in a programmable controller that is linked to a sensor on
the hoist. The tag has five possible values:

When the hoist is The tag’s value is

At bottom 1
Raising 2
Stopped between the top and bottom 3
Lowering 4
At top 5

2. In the Local Messages editor, create the following messages with 5 trigger values, to
match the values of the Hoist_Status tag:

Trigger value Message

1 The hoist is ready to rise.
2 The hoist is raising the pallet.
3 The hoist has stopped.
4 The hoist is lowering the pallet.
5 The hoist is finished rising.

20-35
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

3. Save the message file with the name Hoist status.

4. In the Graphics editor, create a local message display object.
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 Tag/Expression column.
At run time, when the operator views the graphic display containing the local message
display object, the status of the hoist is displayed.

Creating and restoring recipes

A recipe file supplies tag values for all the numeric and string input objects in a graphic
display. To determine which input objects receive which tag values, the recipe file uses the
index numbers assigned to the objects.
FactoryTalk View assigns index numbers to input objects and buttons as you create them.
To check the index number for an object, open its Properties dialog box, and then check
the number in the Tab index box.
For more information about index numbers, see “Using index numbers to navigate to
objects in a display” on page 21-14.
You can create a recipe file in the Recipes editor or, at run time, by specifying a file name
in the recipe object, and then saving values to that file.

Creating a recipe object

Use the Recipe tool to create a recipe object in a graphic display, so that an operator can
restore or save recipe files at run time.
Recipe tool
Rather than entering values one by one into input objects in the display, the operator can
use the recipe object to load recipes that provide values for all the objects at once. The
operator can also use the recipe object to write the values to network devices.

Each graphic display can contain only one recipe object.

Restoring and saving recipe values at run time

At run time, an operator can restore values from a recipe file into input objects and send
those values to a network device or server.

20-36
 • • • • •
20 • CREATING GRAPHIC OBJECTS

The operator can also upload values from a network device or server into input objects,
and then save those values to a recipe file. If an upload fails because of a communication

20 • Placeholder
error, the input object appears in outline form.
To use a recipe object in a graphic display, do one of the following:
„ Double-click the recipe object to open the Recipe dialog box, and then save or restore
the recipe file.
„ Press Ctrl+R to move to the object, and then press Enter to restore the contents of the
recipe file.
„ Press Ctrl+W to move to the object, and then press Enter to save the recipe file.
If the display is set up to use the on-screen keyboard, selecting the recipe object and
pressing Enter opens the keyboard. To open the Recipe dialog box, press Download in the
on-screen keyboard.

To restore the values from a recipe file

1. In the recipe object, type the name of the recipe file you want to restore, and then press
Enter.

If you don’t know the name of the recipe file, just click in the recipe object, and then press
Enter.

2. In the Recipe dialog box, click Restore.

If you didn’t specify a recipe file name, select a recipe file first, and then click
Restore.
You can also use the RecipeRestore command to restore values from a recipe file. For
details, see the FactoryTalk View Site Edition Help.

To download recipe values to a network device or server

„ After restoring values from a recipe file to input objects in a display, to download the
values, press PgDn, or use the DownLoad or DownLoadAll command.

20-37
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Example: Creating a recipe file at run time

Values typed in input boxes in the following graphic display, are used to create a recipe
file for chocolate-chip cookies.

Numeric input
boxes
Recipe object

String input box

This is the new recipe file:

Index number Tag name

(in comment)
Value

To save recipe values from a network device or server

1. To upload values you want to save to a recipe file, press PgUp, or run the Upload or
UploadAll command.

20-38
 • • • • •
20 • CREATING GRAPHIC OBJECTS

2. In the recipe object, type the name of the recipe file, and then press Enter.

20 • Placeholder
If you don’t know the name of the recipe file, just click in the recipe object, and then press
Enter.

3. In the Recipe dialog box, click Save.

If you didn’t specify a recipe file name, select a recipe file first, and then click Save.
You can also use the RecipeSave command to save values to a recipe file. For details, see
the FactoryTalk View Site Edition Help.

Creating control list selectors

Control list selectors allow an operator to scroll through a list of states for a process and
select one of the states. A highlight in the list shows the current state.

Selecting states in a control list selector

A control list selector can show several states at the same time, but only one state can be
selected at a time. As the operator scrolls through the list, each state is selected
automatically.
To let the operator confirm the selection of a particular state before the state’s value is
written to the network device, include an Enter key with the control list selector.

Using keys to scroll the list

Control list selectors work with:
„ key objects. These are graphic objects that duplicate the functions of keyboard keys.
Use them with touch-screen terminals.
„ the arrow keys and Enter key on a terminal’s keypad.
„ the arrow keys and Enter key on a keyboard.

20-39
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

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 more information about keys, see “Using key objects to simulate keyboard functions”
on page 20-29.

Setting the Value tag

At run time, the Value tag changes:
„ when the operator selects the next item in the list.
„ when the operator presses the Enter key, if the control list selector requires that a
selection be confirmed using the Enter key.
„ when another process changes the tag’s value in the network device.
For example, a control list selector is used to change a tag’s value. If the tag’s value is
zero, when the operator selects the next state, the tag’s value changes to the value for
the next state, for example 1.
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.
Using Enter key handshaking to ensure the current value is read
When the operator presses the control list selector’s Enter key, the highlighted state’s
value is written to the network device.
Use Enter key handshaking to hold the current value of the tag at the network device for a
specified period, to ensure it is read before the control list selector overwrites it with a
new value.
Before Enter key handshaking completes for an object, the operator can provide input to
other objects in the graphic display. However, if the operator presses the Enter key for an
object before its handshake is completed, an error is sent to the Diagnostics log file.
If the graphic display is closed, the Enter tag is reset to 0, and any handshake timing is
also reset.

Creating control list selectors

Use the Control List Selector tool to create a list that displays multiple options and allows
an operator to cycle through them consecutively. The control list selector displays the
Control List current state of a process or operation by highlighting the state.
Selector tool
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.

20-40
 • • • • •
20 • CREATING GRAPHIC OBJECTS

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.

20 • Placeholder
Creating piloted control list selectors
Piloted control list selectors allow an operator or remote device to scroll through and
select from a list of states for a process. A highlight in the list indicates the current state.

Piloted control list features

Piloted control list selectors have features that control list selectors do not:
„ States can be selected by an operator, by a remote network device, or by both an
operator and a network device.
Control list selectors can be controlled by the operator or a network device, but not
both.
„ Individual states can be turned off, to prevent them from being selected.
Control list selectors do not allow states to be turned off.
„ The state values of all 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.
Control list selectors have no Visible States 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.
Control list selectors have no Top Position tag.

Selecting states in a piloted control list selector

A piloted control list selector can show several states at the same time, but only one state
can be selected at a time.
You can set up a piloted control list selector to be operator controlled or remote controlled,
by assigning tags or expressions in the Connections tab.
You can also set up individual states to be operator controlled, remote controlled, operator
and remote controlled, or none of those. If none is selected, the state is turned off and
cannot be selected.
If the piloted control list selector is set up to be operator controlled, and the operator
selects a remote controlled state, or one that is turned off, a hollow cursor is displayed, as
shown on the right in the following illustration.

20-41
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

The filled cursor means the The hollow cursor means the
operator can select this state. operator cannot select this state.

Using keys to scroll the list

When a piloted control list selector is operator controlled, it works with:
„ key objects. These are graphic objects that duplicate the functions of keyboard keys.
Use them with touch-screen terminals.
„ the arrow keys and Enter key on a terminal’s keypad.
„ the arrow keys and Enter key on a keyboard.
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 more information about keys, see “Using key objects to simulate keyboard functions”
on page 20-29.

Controlling the list view

If the piloted control list selector contains more states than the list can display
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.

Selecting items directly or remotely

Each state can be selected directly by an operator, or remotely by a device such as a
programmable controller. The operator or the controller scrolls through the list to select a
different state or a different group of visible states.

20-42
 • • • • •
20 • CREATING GRAPHIC OBJECTS

When an operator or remote device selects a state, the value assigned to the selected state
is written to the piloted control list selector’s Value tag. If the state is turned off, the state’s

20 • Placeholder
value is not written to the Value tag.
If the operator attempts to select a state that is remote controlled, the state’s value is not
written to the Value tag.

Setting the Value tag

At run time, the Value tag changes:
„ when the operator selects an item in the list, if the check box, Write on enter, is cleared
in the General tab.
„ when the operator selects an item in the list, and then presses the Enter key, if the
check box, Write on enter, is selected in the General tab.
„ when a remote device selects an item in the list.
For more information about the Write on enter option, see the FactoryTalk View Site
Edition Help.

Using Enter key handshaking to ensure the current value is read

When the operator presses the piloted control list selector’s Enter key, the highlighted
state’s value is written to the network device.
Use Enter key handshaking to hold the current value of the tag at the network device for a
specified period, to ensure it is read before the piloted control list selector overwrites it
with a new value.

Enter key handshaking can be used only if the piloted control list selector is operator controlled
and if the check box, Write on enter, is selected.

How the handshaking tags and settings interact

If the Enter tag is not assigned, no handshaking will take place.
If the Enter tag is assigned, when the operator presses the Enter key associated with the
piloted control list selector, the following will occur:
1. The timer for the Enter key control delay option begins timing. When the time has
expired, the Enter tag is set to 1.
If the Handshake reset type is set to Non-zero value, the Enter Handshake tag must
be 0 when the Enter key control delay expires in order to set the Enter tag to 1.
2. The timers start for the Enter key handshake time, and Enter key hold time.

20-43
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

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.
4. The Enter tag is reset to 0.

How the Handshake reset type option works

The Enter Handshake tag resets the Enter tag as follows:
„ 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.
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 is logged to the Diagnostics log.
If the graphic display is closed, the Enter tag is reset to 0, and any handshake timing is
also reset.

Creating piloted control selectors

Use the Piloted Control List Selector tool to create a list that displays multiple options and
allows an operator to cycle through them consecutively. The piloted control list selector
Piloted Control displays the current state of a process or operation by highlighting the state.
List Selector
tool A piloted control list selector can be operator controlled, remote controlled, operator and
remote controlled, or neither.

Specifying the text and value for each state

Piloted control list selectors change their appearance and the Value tag, based on their
states.
In the States tab of the Properties dialog box, for each state, you specify the text that
appears in the list and the value for the Value tag.
You can also set up whether each state can be operator controlled, remote controlled,
operator and remote controlled, or neither. If None is selected, the state is turned off and
cannot be selected.

20-44
 • • • • •
20 • CREATING GRAPHIC OBJECTS

You can set up 255 states for a piloted control list selector. This provides the operator with
up to 255 selections in the list.

20 • Placeholder
Setting up connections for a piloted control list selector
To connect with a network device such as a programmable controller, piloted control list
selectors use tags or expressions. You set up these tags or expressions in the Connections
tab of the Properties dialog box.
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 trigger an action, for example, to set 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 network device.
„ The Remote Access tag or expression determines whether the piloted control list
selector can be operated by the operator or remotely, for example, by a network
device.
If the remote access tag has a value of zero, or is not assigned, the operator can select
states in the list. If the remote access tag has a non-zero value, the selected state is
determined by the value of the Indicator tag or expression.
„ The Top Position tag receives the value of the state that is the first item in the list
whenever the list scrolls.
„ The Visible States tag receives the values of all the states visible in the list
whenever the list scrolls. The tag must support arrays, and the arrays must have as
many elements as the number of items visible in the piloted control list selector.
For example, if the piloted control list selector has 5 visible states, and the state values
are written to network device addresses N7:0 through N7:4 using RSLinx Enterprise,
the Visible States tag should be an array tag with the following address:
::[RSLinx Device Shortcut]N7:0,L5

where L5 indicates that the tag writes values to five addresses in the array.
„ The Enter tag allows a network device to confirm a selection after the Value tag is
written. The Enter tag is set for as long as is specified in the Timing tab.
„ The Enter handshake tag or expression resets the Enter tag, using the Handshake
reset type option specified in the Timing tab.

20-45
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Creating the Alarm and Event objects

The FactoryTalk Alarm and Event objects provide run-time displays of FactoryTalk
device-based and tag-based alarm data, sources, and activity.
You can create the following Alarm and Event objects:
The Alarm and event summary displays detailed alarm information from selected
Rockwell Automation Device Servers (RSLinx Enterprise) and Tag Alarm and Event
Servers in a FactoryTalk View SE application.
You can use the alarm and event summary to view, acknowledge, suppress, and disable
the alarms on display.
The Alarm and event banner displays up to 5 of the highest priority, most severe, and
most recent alarms in the system.
You can use the alarm and event banner to monitor and acknowledge the most serious
FactoryTalk alarms in the system.
The Alarm status explorer shows the areas in an application that contain alarm
sources, and the tags being monitored for alarms.
You can use the alarm status explorer to view alarm sources, suppress or unsuppress, and
enable or disable alarms.
The Alarm and event log viewer displays information stored in the logs generated by
the FactoryTalk Alarms and Events Historian.
You can use the alarm and event log viewer to view, sort, filter, and export historical alarm
information.
For information about creating the FactoryTalk Alarm and Event objects, and using them
to monitor and interact with alarms at run time, see Chapter 12, “Setting up FactoryTalk
alarms,” in Volume 1 of the FactoryTalk View Site Edition User’s Guide.

Creating global objects

FactoryTalk View global objects allow you to link the appearance and behavior of one
graphic object to multiple copies of that object in the same application.
You create global objects in displays in the Global Objects folder, in the same way you
create graphic objects in displays in the Displays folder.
All of the objects and groups of objects created in a global object display are global
objects. Any graphic object you can create in FactoryTalk View can be a global object,
except for ActiveX controls, OLE objects, and HMI tag alarm summaries.

20-46
 • • • • •
20 • CREATING GRAPHIC OBJECTS

For more information about creating global object displays, see Chapter 19, Creating
graphic displays.

20 • Placeholder
Creating reference objects
After creating a global object (or group of objects), you can copy it for use in standard
displays throughout an application.
When you copy a global object into a standard graphic display (in the Displays folder), the
copy is called a reference object. The original global object (in the Global Objects folder)
becomes the copy’s base object.
Reference objects have special properties that allow them to link to the original, base
objects. When you modify properties of a base object, the changes are copied to all
reference objects linked to the base object.
You can produce an unlimited number of reference objects from a single base object.
However, reference objects can only link to a base object within the same application or,
in a network application, within the same HMI server.

To create a reference object

To create a reference object, use one of these methods:
„ Copy a global object from a global object display into a graphic display in the same
application or, in a network application, within the same HMI server.
„ Copy an existing reference object from one graphic display to another in the same
application or, in a network application, within the same HMI server.
„ Add a global object display into the Displays folder in the same application or, in a
network application, within the same HMI server. In this case, all objects saved in the
display are converted to reference objects.

If you add a global object display into the Displays folder in a different HMI server, the global
objects are converted to standard graphic objects, rather than reference objects.

To add a global object display into the Displays folder

1. In FactoryTalk View Studio, in the Explorer window, right-click the Displays icon,
and then click Add Component Into Application.
2. Browse to and select the global object display to be added, and then click Open.

20-47
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Using placeholders to specify values for global objects

A tag placeholder is the cross-hatch character (# ) followed by a number from 1 to 500.
You can use tag placeholders to specify a value for a graphic object, instead of (or as part
of) a tag name, expression command, or embedded variable.
Using tag placeholders in standard graphic objects allows you to use a single graphic
display for different purposes, by substituting tag values for the placeholders at run time.
For more information, see “Using placeholders to specify tag values” on page 19-29.
You can also set up tag placeholders for global objects.
This allows you to assign different run-time values to the reference objects linked to a
global base object. First you define the tag placeholder at the global base object, and then
you assign the run-time values to the linked reference objects.
For more information, see “Setting up tag placeholders for global objects” on page 19-32.

Adding global objects into the graphic libraries

Displays in the in the Libraries folder cannot contain reference objects. If you add:
„ a global object display into the Libraries folder, the global objects are converted into
standard graphic objects.
„ a standard graphic display containing reference objects into the Libraries folder, the
reference objects are deleted, when the new library is saved.

Setting up the link properties of reference objects

A reference object has properties that link it to its base object. You can set these properties
when you copy (or drag and drop) a global object into a standard graphic display, or you
can modify them later.
The Link properties have default values when the reference object is created. You can
modify these properties in the Property Panel for the object, or in the Global Object
Defaults dialog box.
The values of the Link properties determine whether aspects of the reference object’s
appearance and behavior are defined by the base object, or by the reference object itself.
For details, see the property descriptions that follow.

To open the Global Object Defaults dialog box

„ Right-click the reference object you want to modify, and then click Global Object
Defaults.

20-48
 • • • • •
20 • CREATING GRAPHIC OBJECTS

20 • Placeholder
For details about options in the Global Object Defaults dialog box, click Help.

If you change the properties of a linked reference object, you might lose the original settings.
For example, if you change a reference object’s LinkConnections property from False to True,
any connections previously assigned for the reference object are deleted. To restore the original
connections, click Undo on the Edit menu.

LinkAnimation
The LinkAnimation property determines whether the reference object uses the animation
set up for its base object.
Set up the LinkAnimation property of the reference object by selecting:
„ Link with expressions, to use the animation, including expressions, set up for the
base object.
„ Link without expressions, to use the animation, excluding expressions, set up for
the base object. This means you can set up the expressions for the reference object
separately.
„ Do not link, to set up animation and expressions for the reference object separately.
For a Button push button object, the LinkAnimation property determines whether the
reference object uses the press, release, or repeat actions set up for the base object. This is
true when you select either Link with expressions or Link without expressions.

20-49
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

LinkConnections
The LinkConnections property determines whether the reference object uses the
connections set up for its base object.
Set up the LinkConnections property of the reference object by selecting:
„ True, to use the connections assigned to the base object.
„ False, to set up connections for the reference object separately.

In FactoryTalk View Site Edition, a reference object that is a tag label, trend, or Button push
button with an action other than Command, always uses the connections assigned to its base
object. You cannot set up connections for these reference objects separately.

LinkSize
The LinkSize property determines whether the reference object uses the height and width
set up for its base object.
Set up the LinkSize property of the reference object by selecting:
„ True, to use the height and width set up for the base object.
„ False, to set up the height and width of the reference object separately.

If you attempt to resize a reference object with its LinkSize property set to True, the object will
snap back to its original size.

LinkBaseObject
The LinkBaseObject property specifies the name and location of the base object the
reference object is linked to.
You cannot modify the LinkBaseObject property. If the specified global object display or
base object does not exist, the reference object will appear in red outline, with a red cross
on a white background.
To restore the reference object, you must recreate the global object with the same name,
on the same global object display.

To find the base object linked to a reference object

„ Right click the reference object (or group), and then click Edit Base Object.
This opens the global object display containing the base object, and selects the base
object on the display.

20-50
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Link properties of grouped reference objects

20 • Placeholder
Grouped reference objects use the same properties as individual reference objects, to link
to their grouped base objects. For grouped reference objects, you can set up:
„ LinkBaseObject only for the group, not for individual objects within the group.
„ LinkConnections only for individual objects within the group.
„ LinkAnimation for the group and for individual objects within the group.
„ LinkSize only for the group, not for individual objects within the group.
When the Link properties apply to grouped reference objects, the word Group is added to
the property name in the Property Panel.

Breaking links between reference and base objects

To break the link between a reference object (or group) and its base object, use one of
these methods:
„ Right-click the reference object, and then click Break Link.
„ Delete, remove, or rename the global object display containing the base object.
„ Delete or rename the base object itself.

If you delete an object that is part of a grouped based object, the corresponding object in the
grouped reference object is also deleted, instead of being treated as a broken link.

Working with OLE objects

OLE is an acronym for Object Linking and Embedding. OLE objects are objects created
in other Windows applications and linked to, or embedded in, a FactoryTalk View graphic
display.
The main difference between linking and embedding is where data is stored.
Linked objects are stored in the source file. The graphic display stores only the location of
the source file and displays a representation of the linked data. Embedded objects become
part of a graphic display.
This difference means that:
„ linking pastes the object into the graphic display and retains links to the source file in
addition to allowing it to be modified. If the source file is changed, the object in the
display is changed.
When you double-click a linked OLE object to modify it, its application opens in
another window. The object’s source file is active.

20-51
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

If you move an application, remember to move, copy, or update the link for the source
file to the new location.
„ embedding pastes the object into the graphic display and allows it to be modified. If
the source file is changed, the object in the display is not affected.
When you double-click an embedded OLE object to modify it, the Graphics editor’s
toolbar is replaced by the application’s toolbar. A border appears around the object to
indicate that it can be modified. This is called in-place editing.
If you move an HMI project, embedded OLE objects are moved automatically, with
the HMI project files.

FactoryTalk View is an OLE client application. This means FactoryTalk View cannot be
embedded in other Windows applications.

Creating OLE objects

When you create an OLE Object in a graphic display, you are actually inserting an object
made by another application.

To create an OLE object in a graphic display

1. On the Objects menu, click OLE Object, and then drag the tool to create a box the size
needed to contain the OLE object.
2. In the Insert Object dialog box, select Create New to open the application within the
graphics display and create an object, or choose Create from File to select and insert
an existing object.
For details about inserting and modifying OLE objects, see the FactoryTalk View Site
Edition Help.

Converting OLE objects

Convert an OLE object to an FactoryTalk View graphic object, if you want to:
„ change an embedded, vector-based object into a polygon, to make it easier to
manipulate.
„ reduce the size of a graphic display file.
Embedding an object in a graphic display increases the size of the graphic file,
because the embedded object includes information about its source application. This
lets you double-click the object and modify it using the source application.
If you convert the object, you can no longer modify it using its source application.
However, you can use the editing tools in the Graphics editor to work with the object.

20-52
 • • • • •
20 • CREATING GRAPHIC OBJECTS

Working with ActiveX objects

20 • Placeholder
ActiveX objects are software components supplied by products independent from
FactoryTalk View, such as Microsoft® Office 2003, Visual Basic®, and many other third-
party applications.
For example, you can embed the Microsoft Forms ActiveX objects in an FactoryTalk
View graphic display.
By embedding an ActiveX object in a FactoryTalk View display, and then assigning
properties or specifying handlers for the object’s events, the object can interact with
FactoryTalk View.
Data is passed between an ActiveX object and FactoryTalk View using tags.
If you attach a tag to an ActiveX object’s Value property, the object’s behavior changes as
the tag’s value changes.

FactoryTalk View supports the use of windowed ActiveX controls only. You cannot use
windowless ActiveX controls in an FactoryTalk View graphic display.

Exchanging data with tags

To pass data between an ActiveX object and FactoryTalk View, the ActiveX object must
supply information in the same format as the tags with which the data is exchanged.
For example, if the ActiveX object is connected to an HMI tag, the ActiveX object must
provide information that is compatible with the analog, digital, or string format of the tag.
FactoryTalk View does not support pointer parameters in an ActiveX object.

Attributes of ActiveX objects

An ActiveX object has three types of attributes that allow access to its features:
„ Properties are named characteristics and values of an object, such as shape, color,
position, or number.
„ Events are actions triggered by the ActiveX object in response to an external action
on the object, such as a mouse click.
In FactoryTalk View you can use events to change the value of a tag, or to run a
FactoryTalk View 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.
„ Methods are functions implemented in the ActiveX object that allow external actions
to change the object’s appearance, behavior, or properties.

20-53
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

A call to a method might be made in response to events from other controls and could
trigger other events.
You can use the FactoryTalk View Invoke command as the external event that calls a
method. For more information about the Invoke command, see the FactoryTalk View
Site Edition Help.

Creating ActiveX objects

When you create an ActiveX object in a graphic display, you are actually inserting an
object made by another application.

To create an ActiveX object in a graphic display

1. On the Objects menu, click ActiveX Control, and then drag the tool to create a box the
size needed to contain the object.
2. In the Insert an ActiveX Control dialog box, select an object from the list that is
presented.
For details about inserting and registering ActiveX objects, see the FactoryTalk View Site
Edition Help.

Setting up ActiveX objects to interact with FactoryTalk View

To set up an ActiveX object to interact with FactoryTalk View you can:
„ connect the object’s properties to tags. For details, see “Assigning tags and
expressions to objects” on page 19-20.
„ connect the object’s methods to tags. For details, see “Connecting tags to an object’s
methods” on page 21-25.
„ connect the object’s events to tags. For details, see “Connecting tags to an ActiveX
object’s events” on page 21-25.
„ use VBA code. For more information, see Chapter 16 in Volume 1 of the FactoryTalk
View Site Edition User’s Guide.

Setting up tools in the ActiveX toolbox

Use the ActiveX toolbox to set up tools for the ActiveX objects you use frequently.
By default, the ActiveX toolbox contains some of the Microsoft Forms 2.0 ActiveX
controls that are installed with VBA, and the FactoryTalk View SE Signature Button.

20-54
 • • • • •
20 • CREATING GRAPHIC OBJECTS

For information about adding objects to the toolbox, see the FactoryTalk View Site
Edition Help.

20 • Placeholder
The ActiveX toolbox cannot be docked to the FactoryTalk View Studio workspace.

Deploying ActiveX components automatically at run time

FactoryTalk View SE clients can automatically install the correct versions of ActiveX
controls used in graphic displays.
To deploy ActiveX controls automatically, you need to create .cab files for the ActiveX
controls, and then put the .cab files in the same folder where you installed FactoryTalk
View SE.
To do this, run the program CABARC.exe, on the computer hosting the HMI server.
CABARC.exe is located in:
\Documents and Settings\All Users\Shared Documents\RSView Enterprise\
ActiveX Control Setup*
*The path given is for Windows XP or Windows Server 2003. In Windows 2000,
the third folder is named Documents.
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.

Using electronic signatures to authorize run-time changes

To secure run-time operations in FactoryTalk View SE, use the electronic signature
feature to prevent operators from performing actions they aren’t authorized to perform.
The signature button can be used together with other features of FactoryTalk View SE, to
meet the security standards required for regulated manufacturing applications, for
example, those required for US Government 21 CFR Part 11 compliance.
The signature button verifies the operator’s identity, and allows an action to be performed
only if the operator provides the appropriate user name and password.
The following illustration shows a signature button for authorizing downloads from a
graphic display, and the FactoryTalk View Electronic Signature dialog box that opens
when the signature button is pressed.

20-55
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

When the operator clicks

Authorize download...

...the FactoryTalk View

Electronic Signature dialog
box opens.

Values are downloaded to

the network device only if the
operator’s name and password
are accepted.

If the operator is a Windows-linked user that does not belong to the current Windows domain,
include the domain name with the user name, using the syntax domain\user name. For more
information about Windows-linked users, see Chapter 5, “Setting up security,” in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

Securing tag writes, commands, and downloads

You can use the signature button to secure the following operations:
„ setting a tag value
„ running a FactoryTalk View command
„ downloading all input object values to a network device
At run time, these operations can be prevented and an error message displayed if a user
name or password is incorrect, or if other information, such as an operator’s comment, is
required but not provided.

20-56
 • • • • •
20 • CREATING GRAPHIC OBJECTS

In addition, the signature button can be set up to require authorization by another person,
such as a supervisor, before the operation can be carried out.

20 • Placeholder
For added security, in the Connections tab of the signature button’s Properties dialog box,
use the security function CurrentUserHasCode in an expression assigned to the button’s
Enabled property.
This checks whether the current user has the security code assigned to the graphic display.
For more information about securing graphic displays, see page 5-18 in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

Creating signature buttons

The electronic signature button is an ActiveX object. The tool to create an electronic
signature button is in the ActiveX toolbox.

To create an electronic signature button

1. On the View menu, click ActiveX Toolbox. This opens the ActiveX toolbox.
2. Click the Electronic Signature button in the ActiveX toolbox.
3. Drag the tool to create a box on the display that is the size the button is to be.
4. Right-click the signature button, and then click Properties. This opens the FactoryTalk
View SE Signature Button Properties dialog box.

Securing objects in graphic displays

The signature button does not change the way graphic objects in a display work.
For example, numeric input objects in a display will download their values to a network
device when the operator presses Page Down, even if there is a signature button on the
display.
To ensure that values are downloaded only if the electronic signature is verified, you must
secure the graphic objects separately. To do this, use one of these methods:
„ Turn off the Enter key, by using the /E parameter with the Display command. For
details about the Display command, see the FactoryTalk View Site Edition Help.
„ Use display keys to set the Page Up, Ctrl+Page Up, Page Down, and Ctrl+Page Down
keys to do nothing. For details about setting up display keys, see page 21-19.

20-57
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Tracking changes using FactoryTalk Diagnostics

The operations initiated by the signature button are logged to FactoryTalk Diagnostics,
and can be viewed in the Diagnostics List or Diagnostics Viewer.
The logged information includes user name, old value, new value, operator’s comments,
and name of the person approving the change.
For information about logging system activity, see Chapter 15 in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

20-58
21 Animating graphic objects

21 • Placeholder
This chapter describes:
„ what FactoryTalk® View animation is.
„ setting up animation for FactoryTalk View graphic objects.
„ creating effects using the different types of animation.
„ using index numbers to navigate to objects in a display.
„ associating objects and displays with keys.
„ animating ActiveX objects.

About animation in FactoryTalk View

In FactoryTalk View Site Edition (also called FactoryTalk View SE), you can animate
objects in graphic displays, to enhance how you visualize automation controls and
processes in an application.
Following are some of the ways you can animate objects in FactoryTalk View:
„ Link a FactoryTalk View graphic object to a tag or an expression, so that the object’s
appearance changes when the value of the tag or expression changes.
For more information, see “Setting up animation for FactoryTalk View graphic
objects” on page 21-2.
„ Link a graphic object or display to a key or mouse button, to let an operator perform
an action by pressing the key or mouse button.
For more information, see “Associating objects and displays with keys” on
page 21-17.
„ Animate an ActiveX object:
„ by assigning tags to the ActiveX object’s properties, so that the tags’ values
change when the properties change or, in some cases, the properties change when
tag values change.
„ by running commands based on the ActiveX object’s events.
„ mapping tags to the ActiveX object’s event parameters.
„ interacting with the ActiveX object using VBA code.
For more information about animating ActiveX objects, see page 21-22.

21-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Setting up animation for FactoryTalk View graphic objects

To animate FactoryTalk View objects in a graphic display, create the objects first, and then
apply animation to them.
In the Graphics editor, use the Animation dialog box to apply animation to the selected
object or group of objects.

Check marks
indicate which
types of animation
are applied to the
selected object.

Animation tabs

Expression area

Range of values
through which
the object is
animated

Expression range
options

For details about options in each Animation tab, click Help.

To set up key animation, open the Object Key or the Display Key dialog box, from the Graphics
editor’s Edit menu. For more information about key animation, see “Associating objects and
displays with keys” on page 21-17.

While working in a graphic display, you can leave the Animation dialog box open and
move it around. This means you only have to open the dialog box once, to apply
animation to different objects in the display.
It also means you can use Object Smart Path to set the range of motion for an object,
rather than needing to know and then to type the number of pixels you want the object to
move. For more information, see “Defining the range of motion” on page 21-4.

21-2
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

To open the Animation dialog box

1. Select the object or object group you want to apply animation to.

21 • Placeholder
2. On the View menu, click Animation, and then click the type of animation you want to
apply.
If the selected object doesn’t allow certain types of animation, the types will not be
available on the Animation menu.

Linking animation to tag values

Most types of animation can be linked to the value of a tag. To link animation to a tag
value, you have to specify a tag name or a tag placeholder.

To set up animation using a tag name

„ In the Animation dialog box, in the Expression box, type a tag name, or click Tag to
open the Tag Browser, to search for and select a tag.
You can use a tag that already exists in a device or in the HMI server’s tag database, or
you can use the name of a new tag that you plan to create later.

Using tag placeholders

A tag placeholder is a cross-hatch character (#) followed by a number between 1 and 500.
Tag placeholders used in graphic displays are replaced with tag names when the display is
run. For details, see “Using placeholders to specify tag values” on page 19-29.
To apply animation using a placeholder instead of a tag name, type the placeholder in the
Expression box.

Linking animation to expressions

Many types of animation require an expression. You can build expressions using tag
values, constants, mathematical equations, security functions, and if–then–else logic.
A tag name or tag placeholder can be included as part of an expression, or stand alone as
the entire expression.
For more information about expressions, see Chapter 23, Creating expressions.

To set up animation using an expression

„ In the Animation dialog box, in the Expression box, type the expression, or click
Expression to open the Expression editor, to build an expression.

21-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Linking animation to actions

Some types of animation, such as touch animation, require you to specify an action.
The action can be a FactoryTalk View command or macro. For example, to use touch
animation to open a graphic display, specify the Display command as the press or release
action.
For a complete list of FactoryTalk View commands and their syntax, see the FactoryTalk
View Site Edition Help. For more information about macros, see Chapter 27, Creating
macros.

Determining start and end points for a range of motion

Many types of animation require an expression range, using minimum and maximum
values to determine start and end points for the object’s range of motion.
When setting up animation, to calculate minimum and maximum values, select one of the
following options in the Animation dialog box:
„ Use tag’s min and max property values uses values taken from the minimum
and maximum range defined for the first HMI tag used in the expression. This is the
default option.
„ Use constant uses numeric constants. Type the minimum and maximum values in
the boxes.
„ Read from tags uses the values of the tags you specify. Use this option if you expect
the minimum and maximum values to change.

With the Read from tags option, the minimum and maximum values are read only the first
time animation is started for the object. For example, the values are read when the display
containing the object is run.

Defining the range of motion

To define a range of motion when setting up animation for an object, you can:
„ move the object in the Graphics editor. This feature is called Object Smart Path. For
an example, see “About Object Smart Path,” next.
„ type values in the At minimum and At maximum boxes.
Motion is defined in pixels, degrees, or percent, depending on the type of animation.

Visibility, color, and touch animation do not use a range of motion, because these types of
animation represent a change of state, not a range of values.

21-4
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

About Object Smart Path

With Object Smart Path, you can easily set the range of motion for an object, by moving

21 • Placeholder
the object on the graphic display. The following example shows how this feature works.

Example: Using Object Smart Path to define a range of motion

for a horizontal slider
1. In the Graphics editor, create a slider using a line and a rectangle, or copy a slider
object from the Sliders library in the Graphics Libraries.
2. Right-click the slider, select Animation, and then click Horizontal Slider.
3. In the Tag box, type a tag name. To find and select a tag, click the Browse button.
4. In the display, drag the slider to the position indicating the lowest number in the range.
5. In the Animation dialog box, set this position by clicking the At minimum check box.
6. In the display, drag the slider to the position indicating the highest number in the
range.
7. In the Animation dialog box, set this position by clicking the At maximum check box.
8. To save the settings, click Apply.
When you finish setting up the animation, the slider returns to its starting position.

Applying animation to object groups

You can apply animation to a FactoryTalk View graphic object, to a group of objects, and
to the individual objects that comprise a group.
To animate a group of objects in a graphic display, group the objects first, and then apply
animation to the group.
At run time, animation set up for object groups generally takes precedence over animation
set up for objects within the group, except for visibility, fill, and color animation.
Visibility and color animation applied to individual objects takes precedence over any
group animation. Fill animation applied to a group is added to any animation applied to
individual objects.

21-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To apply animation to individual objects in a group, use the group edit feature. For details
about this feature, see “Modifying grouped objects” on page 19-17.

Combining different types of animation can produce unexpected results. Be sure to test group
animation, to ensure that the animation achieves the effect you want.

Testing animation
To test the animation applied to objects in a graphic display quickly, switch to test display
mode in the Graphics editor.
Test Display
tool When you are finished testing, switch back to edit display mode to continue working on
the display. To switch between test and edit modes, use the buttons on the toolbar or the
items on the View menu.
Edit Display Testing a display in FactoryTalk View Studio is not the same as running the display in the
tool
FactoryTalk View 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 between open displays.
In addition, some FactoryTalk View commands are ignored when run in test display
mode. For a complete list of these commands, see Appendix A in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

If the animation applied to objects in a graphic display uses device tags, to test the animation,
you must set up communications with the devices or data servers. Before deploying an
application, test it in a FactoryTalk View SE Client, to verify that everything works as intended.

Viewing the animation applied to objects

To view the types of animation applied to an object or object group, use one of these
methods:
„ Right-click the object, and then click Animation. On the shortcut menu, a check mark
appears beside each type of animation the object has.
„ Select the object, and then open the Animation dialog box. In the dialog box tabs, a
check mark appears beside each type of animation the object has.
„ In the Object Explorer, click Settings, select the animation types you want to find, and
then click OK. You can also use the Object Explorer to check which objects have
animation linked to a particular tag. For details, see page 19-4.
„ To view animation applied to individual objects within a group, use the group edit
feature. For details about this feature, see “Modifying grouped objects” on
page 19-17.

21-6
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

Copying or duplicating objects with animation

21 • Placeholder
When you copy or duplicate objects that have animation, the animation is copied or
duplicated with the object.
If you copy or duplicate an object group, the copy can be ungrouped, just like the original
object.
You can also copy animation without copying the original object, and then paste the
animation onto another object. If the original object has more than one type of animation,
all the types will be copied and pasted.

To copy and paste only the animation

1. Right-click the object that has the animation you want to copy.
2. On the shortcut menu, click Copy animation.
3. Right-click the object you want to paste the animation onto.
4. Click Paste animation

About global objects and animation

FactoryTalk View global objects allow you to link the appearance and behavior of one
graphic object to multiple copies of the object in the same application.
When you copy a global object into a standard graphic display in the Displays folder, the
copy is called a reference object. The reference object has special properties that allow it
to link to its base object, which is the original object in the global object display.
For example, the value of the LinkAnimation property determines whether the reference
object will use the animation set up for itself, or the animation set up for the base object.
For more information about the LinkAnimation property, see “Setting up the link
properties of reference objects” on page 20-48.

Creating effects using the different types of animation

FactoryTalk View SE provides a range of animation types, to let you create different
effects for the objects you use in graphic displays.
You can apply one type of animation to an object or group of objects, or you can combine
animation types to achieve a particular effect.
For example, applying both width and height animation to a drawing object, such as a
rectangle, gives it the appearance of moving into or out of the display, as it shrinks and
expands.

21-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

The following sections provide an overview of the animation types available in the
Animation dialog box. For details about each type, click Help in the dialog box.
For information about how to apply animation, see “Setting up animation for FactoryTalk
View graphic objects” on page 21-2.

Showing and hiding objects

Use visibility animation to make an object visible or invisible, based on a tag value or the
result of a logical expression. If an object is invisible, no other animation applied to the
object is evaluated, to prevent unnecessary processing.
All FactoryTalk View graphic objects allow visibility animation. If there is a conflict,
visibility animation overrides an object’s visibility property.
The following types of objects only allow visibility animation:
„ images and panels
„ push buttons (except the button type)
„ indicators
„ gauges and graphs
„ key objects
„ advanced objects (except arrows and labels)
For details about Visibility options in the Animation dialog box, click Help.

Changing an object’s color

Use color animation to change an object’s color, based on a tag value or the result of an
expression. You can specify up to 16 color changes (A to P) for any object.
Colors can be solid or blinking. For each color change, specify the value or threshold at
which the color changes, and specify the colors you want the object to change to. At run
time, when the value reaches or crosses the threshold, the color of the object changes.

Color animation does not affect string input, numeric input, or recipe objects. Color for these
objects is defined in the Display Settings dialog box.

For details about Color options in the Animation dialog box, click Help.

21-8
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

Example 1: Creating text that blinks

21 • Placeholder
This example describes how to create text that blinks between two colors. In this example,
the expression is simply a constant value that matches the value for the selected threshold.
1. Using the Text tool, create a text object. For details, page 20-7.
2. In the Text Properties dialog box, type some text, and then click OK.
3. Select the text object, open the Animation dialog box, and then click the Color tab.
4. In the Expression box, type 0. (Zero is the default value for threshold A.)
5. In the list, click threshold A. Leave the value in the Value box as 0.
6. For the foreground color, click Blink. (Only foreground color affects text.)
7. For each blink color, open the color palette, and then click a color.
8. Click Apply, and then close the Animation dialog box.
Use the Test Display tool to test the animation in this example. The text will blink
between the colors you selected.

Example 2: Creating an object that changes color as the fill level

changes
This example describes how to create a rectangle object that changes color as the object’s
fill level increases. This example uses a tag called Hopper\FlourLevel, which has a range
of 1 to 100. To test the animation, you must create the tag.

To create the object

1. Using the Rectangle tool, create a rectangle.
2. Right-click the rectangle, and then click Properties. In the Back Style list, click Solid.
3. Using the Foreground Color and Background Color palettes, make the rectangle gray.
4. With the rectangle selected, open the Animation dialog box, and then click the Fill tab.

To apply fill animation to the object

1. In the Expression box, type Hopper\FlourLevel (the tag that monitors the fill level).
2. For Fill Direction, click Up.

21-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To apply color animation to the object

1. Click the Color tab.
2. In the Expression box, type Hopper\FlourLevel (the same tag used in the Fill tab).
3. Set up foreground and background colors for the normal state, and for the first and
second warnings (see next tasks).
4. Click Apply, and then close the Animation dialog box.
To set up the color for the normal state
1. In the thresholds and colors list, click A, and leave the value in the Value box as 0.
2. For foreground and background colors, click Solid.
3. For each of the colors, open the color palettes, and then click gray (the same gray used
for the rectangle).
To set up the color for the first warning
1. In the thresholds and colors list, click B.
2. In the Value box, type 80.
3. For foreground and background colors, click Blink.
4. For the first foreground color, select gray. For the second color, select yellow.
5. Repeat step 4 for the background colors.
To set up the color for the second warning
1. In the thresholds and colors list, click C.
2. In the Value box, type 95.
3. For foreground and background colors, click Blink.
4. For the first foreground color, select gray. For the second color, select red.
5. Repeat step 4 for the background colors.
Use the Test Display tool to test the animation in this example.
When the flour level reaches 80, the rectangle will blink between gray and yellow,
warning the operator that the hopper is nearly full. When the flour level reaches 95, the
rectangle will blink between gray and red.

21-10
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

Changing the level of fill in an object

21 • Placeholder
Use fill animation to change the level of fill in an object, based on the result of an
expression or a tag value, in relation to the specified 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 objects, or push button
objects. It also does not affect transparent objects or line objects, even if those objects are
grouped into a single object.
For details about Fill options in the Animation dialog box, click Help.

Moving an object horizontally in a display

Use horizontal position animation to move an object horizontally in a display, based on
the result of an expression or a tag value, in relation to the specified minimum and
maximum values.
The object’s horizontal position is proportional to the value of the expression. For
example, if the value of the expression is halfway between its minimum and maximum
values, the object will be halfway between its minimum and maximum pixel offset.
For details about Horizontal Position options in the Animation dialog box, click Help.

Moving an object vertically in a display

Use vertical position animation to move an object vertically in a display, based on the
result of an expression or a tag value, in relation to the specified minimum and maximum
values.
The object’s vertical position is proportional to the value of the expression. For example,
if the value of the expression is halfway between its minimum and maximum values, the
object will be halfway between its minimum and maximum pixel offset.
For details about Vertical Position options in the Animation dialog box, click Help.

Rotating objects
Use rotation animation to rotate an object around an anchor point, based on the result of
an expression or a tag value, in relation to the specified minimum and maximum values.
The degree of rotation is proportional to the value of the expression. For example, if the
value of the expression is halfway between its minimum and maximum values, the object
will rotate half the specified rotation range.

21-11
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Panel and image drawing objects, the button object, advanced objects (except arrows),
OLE objects, ActiveX objects, and bitmaps cannot be rotated.
For details about Rotation options in the Animation dialog box, click Help.

Setting up rotation animation

To set up rotation animation, you must specify:
„ 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.)
„ the degree of rotation for the object.
„ the center, or axis, of rotation (for example, to rotate the object around its center point,
or around its top left corner). The center of rotation can be inside or outside the object.
If the center is outside the object, the object moves in an arc.
The following illustrations show how the rotation range and the center of rotation work.

The object rotates when

tag values fall within this
range.

The object stops rotating

when tag values fall
within this range.

Tag values 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

With the center of rotation

inside the object, at the
top-left corner, this object
rotates from zero to 180
degrees as its tag value
changes. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

With the center of rotation

outside the object, at the
top-left corner, this object
rotates in an arc from zero
to 180 degrees as its tag
value changes. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

21-12
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

Changing the width of an object

21 • Placeholder
Use width animation to change an object’s width, based on a tag value or the result of an
expression or a tag value, in relation to the specified minimum and maximum values.
The object’s width is proportional to the value of the expression. For example, if the value
of the expression is halfway between its minimum and maximum values, the object will
be half its full width.
For details about Width options in the Animation dialog box, click Help.

Changing the height of an object

Use height animation to change an object’s height, based on the result of an expression or
a tag value, in relation to the specified minimum and maximum values.
The object’s height is proportional to the value of the expression. For example, if the
value of the expression is halfway between its minimum and maximum values, the object
will be half its full height.
For details about Height options in the Animation dialog box, click Help.

Setting up touch zones

Use touch animation to specify press, repeat, and release actions for an object, that are
triggered when an operator touches the object using a mouse or a touch screen.
To highlight touch objects, use the options in the Display Settings dialog box. You can set
up a highlight box for a touch object, when the cursor passes over it at run time. You can
also make the computer beep when a touch object is selected.

Do not create momentary push buttons using drawing objects with touch animation. Instead,
create a momentary push button object, or a button object with a momentary action. For more
information about creating buttons, see page 20-11.

For details about Touch options in the Animation dialog box, click Help.

Creating a horizontal slider

Use horizontal slider animation to 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. If the
tag value is changed externally, the position of the slider also changes. An object can have
both vertical and horizontal slider animation.
For details about Horizontal Slider options in the Animation dialog box, click Help.

21-13
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Creating a vertical slider

Use vertical slider animation to 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 vertically.
The pixel position of the object is translated into values that are written to the tag. If the
tag value is changed externally, the position of the slider also changes. An object can have
both vertical and horizontal slider animation.
For details about Vertical Slider options in the Animation dialog box, click Help.

Animating OLE verbs

Use OLE (Object Linking and Embedding) verb animation to set up OLE objects to
perform certain actions.
When the expression evaluates to true—that is, when the expression does not equal 0—
the specified OLE verb is activated. The verbs available depend on the OLE object.
Typical verbs include open and edit.
For details about OLE Verb options in the Animation dialog box, click Help.

Applying other types of animation to OLE objects

You can apply visibility, touch, and OLE verb animation to OLE objects. Like other
objects, the type of animation you can apply depends on the object.
For example, you could apply visibility animation to a spreadsheet and then create a
button that, when pressed, would display or hide the spreadsheet.
Do this to show or hide various shift reports or management summaries contained in
embedded spreadsheets or database forms.

Using index numbers to navigate to objects in a display

As you create certain FactoryTalk View graphic objects, they receive a tab index number
automatically.
FactoryTalk View gives index numbers to the following types of objects:
„ numeric and string input objects
„ button objects
„ objects with object key animation
„ ActiveX objects

21-14
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

The index number increases, each time you create another of these objects in the display.
For example, if you create a numeric input object, followed by a button object and a string

21 • Placeholder
input object, the objects will have index numbers 1, 2, and 3.
FactoryTalk View also gives index numbers to objects that support key navigation, such
as display list selectors. To allow an operator to navigate to these objects using the
keyboard, the object’s KeyNavigation property must be set to True.

Checking an object’s index number

To check an object’s index number, double-click the object to open its Properties dialog
box, and then check the number in the Tab index box, as shown in this illustration:

The Properties
dialog box for the
selected input
object shows the
object has tab
index number 1.

You can also check the tab index number using one of these methods:
„ Right-click the object, click Property Panel, and then check the value of the TabIndex
property.
„ For objects with object key animation, right-click the object, click Object Keys, and
then check the number in the Tab index box.

21-15
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

How tab index numbers work

Tab index numbers are used to:
„ determine a tab sequence for objects that an operator can navigate to in a display.
„ move among objects using the Position, NextPosition, and PrevPosition commands at
run time. For details about these commands, see the FactoryTalk View Site Edition
Help.
„ specify which tag values in a recipe file go into which numeric or string input objects.
For more information, see “Creating and restoring recipes” on page 20-36.

Creating a tab sequence

You can use index numbers to create a tab sequence. The tab sequence is the order in
which users can move through a series of objects in a graphic display, using the Tab key.
In the following illustration, the tab order is from left to right:

The circled
numbers above
the objects show
each object’s
index number.

The boxes are

numeric input
objects.

The grouped
drawing objects
have object key
animation.

The buttons are

button objects.

Moving through a tab sequence

To move through the tab sequence in a display, use one of these methods:
„ Press the Tab key to move through the objects from the lowest index number (1) to the
highest index number.

21-16
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

„ Press the Shift-Tab keys to move through the objects from the highest index number to
the lowest index number.

21 • Placeholder
Changing index numbers
Once you have created two or more objects that have index numbers, you can change the
index numbers.
For example, if you have created four input objects, you can modify the fourth object to
have index number 1. However, you cannot change the fourth object to have index
number 5, because there are only four input objects in the display.
When you change an index number, other index numbers are adjusted automatically, so
that no two objects in the display have the same index number, and so that there are no
gaps in the numbering.
If you type an index number that is too high, FactoryTalk View changes it to the highest
available number. If you type a number that is in use, FactoryTalk View renumbers other
objects in the display, changing the tab sequence.

Associating objects and displays with keys

You can associate FactoryTalk View commands with graphic objects in a display, or with
the display itself, using object keys and display keys.
A key can be either a key on a keyboard or keypad, or a button on a touch screen
connected to the computer or monitor an operator is using to interact with an application
at run time.
An operator can use keys to perform actions such as moving from one display to another,
setting tag values, and so on.
Some keys are reserved for use by Windows® and FactoryTalk View SE. For more
information about reserved keys, see “Keyboard shortcuts” on page 22-8.

About client keys

Client keys are different from object and display keys. Client keys are always active at run
time. Object and display keys are only active while a specific object or display has focus.
For more information about client keys, see page 22-10. For information about
precedence amongst object, display, and client keys, see page 22-7.

Setting up object keys

Use object keys to connect a graphic object with one or more keys.

21-17
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

For example, if you connect a rectangle to the F4 key, at run time, when the rectangle has
input focus, the operator can press F4 to perform the key’s press, repeat, or release action.
Use the Object Keys dialog box to set up keys, assign an index number to the object, and
specify whether the object has a highlight box when it is selected at run time.

To open the Object Keys dialog box

„ Right-click the object you want to set up keys for, and then click Object Keys.

For details about options in the Object Keys dialog box, click Help.

Example: Using object keys to open and close valves

A graphic display shows a tank with two valves, named Valve 1 and Valve 2.
The valves control the flow in and out of the tank. Both valves are set up with the same
object key animation:
F2 = Open
F3 = Close
At run time, the operator can select either Valve 1 or Valve 2, and press F2 to open the
valve or F3 to close it.

21-18
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

Setting up display keys

21 • Placeholder
Use display keys to connect a graphic display with one or more keys.
Display keys are similar to object keys, except you don’t have to select an object in the
display, for a display key to respond.
For example, you could connect a display to the F6 key. At run time, when the display is
open, the operator can press F6 to perform the key’s press, repeat, or release action.

To open the Display Keys dialog box

„ Right-click the display, and then click Display Keys.
For information about options in the Display Keys dialog box, click Help.

Example: Using a display key to open a menu

Suppose you want to use the Home key to open a main menu display.
To do this, create a display key that redefines the Home key, by following these steps:
1. Right-click the display, and then click Display Keys.
2. In the Display Keys dialog box, assign a display key.
3. Type the following in the Press Action box:
Display “Main Menu”

Whenever the operator presses Home, the active graphic display closes and the Main
Menu display opens.

If the Main Menu display is of the Overlay 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 19-42.

Viewing the key list at run time

An operator can open a key list at run time, to see which keys are associated with an
object and with the graphic display, and to see what actions the keys will perform.

To display the key list

„ Click an object that is associated with object keys.

21-19
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Label

Modifiers

Key

The key list shows all the object keys set up for the selected object first, followed by all
display keys. Key labels are as specified in the Object Keys or Display Keys dialog box.

The key list does not separate the two types of keys because this distinction does not matter to
an operator. The operator only needs to know what will happen a key is pressed.

To disable the key list

„ Use the /O parameter with the Display command. For details, see Help about the
Display command.

Setting up object-specific commands using keys

You can set up object and display keys, using the [tag] parameter, so that selecting
different objects in a display runs different FactoryTalk View commands.
To do this, you would create a display key first, using the [tag] parameter in the command
specified for its press, repeat or release action, for example:
Set [tag] 1

Then, you would set up object keys for the different graphic objects in the display, using
the Current [Tag] parameter as a placeholder for a tag name (or any character string).
At run time, when an object is selected and the display key is pressed, the contents of the
Current [tag] box replace [tag] in the FactoryTalk View command.
The following three examples show how you can use the Current [tag] parameter.

21-20
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

Example 1: Creating display-wide keys to open and close valves

21 • Placeholder
Imagine you have a graphic display containing 20 valves and you want the operator to be
able to open and close all the valves with the same two keys, F2 and F3, respectively.
Instead of specifying the tag name for each valve, use the [tag] parameter with display
keys. Set this up as follows:
1. In the Display Keys dialog box, assign the F2 and F3 keys.
2. For the F2 key’s press action, type Set [tag] 1.
3. For the F3 key’s press action, type Set [tag] 0.
4. For each valve object, open the Object Keys dialog box, and type the tag name in the
Current [tag] box.
At run time, the operator can select any valve object and press F2 to open the valve, or
press F3 to close the valve.

Example 2: Opening object-specific Help

Imagine you have a graphic display containing various graphic objects that represent
plant-floor equipment.
If something goes wrong with a piece of equipment, you want the operator to be able to
select the corresponding object in the display, and then open a Help file that suggests steps
for correcting the situation.
1. In the Display Keys dialog box, create a display key. For details, click Help. In the
Press Action box, type Help [tag].
2. In the Object Keys dialog box, type the appropriate Help file name in the Current [tag]
box for each equipment object.
At run time, when the operator selects any equipment object and presses the appropriate
Display key, the help file for that piece of equipment is displayed.

21-21
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Example 3: Opening an object-specific HMI tag alarm summary

Imagine you want to have HMI tag alarm information available for a specific machine. If
something goes wrong and causes an alarm, you want the operator to be able to display an
alarm summary for that machine.
To display the HMI tag 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.
1. Create an HMI tag alarm summary that uses a filter containing only the alarms for the
machine. The filter must contain a tag placeholder (for example, #1).
For information about creating an HMI tag alarm summary, see Chapter 11 in
Volume 1 of the FactoryTalk View Site Edition User’s Guide.
2. In the Display Keys dialog box, assign a display key. In the Press Action box, type
Display AlmSumm /t[tag].
3. In the Object Keys dialog box, type the name of the machine you want to specify in
the alarm summary filter.
At run time, the value of [tag] in the Display Keys, replaces #1 in the alarm summary
filter, and then displays HMI tag alarms for the selected machine only.

Animating ActiveX objects

To animate an ActiveX object in FactoryTalk View SE, connect the object’s properties,
methods, or events to tags, so it can receive or modify data at run time. To use tag data to
animate an ActiveX object, use one of these methods:
„ In FactoryTalk View Studio, use the Property Panel, the Invoke command, or the
Events and Methods editors. These methods are simpler, but less flexible.
„ In the Visual Basic® Integrated Development Environment (IDE), use VBA code.
This method is more complex, but more flexible.
A graphic display is like a Visual Basic form. When you insert an ActiveX control in a
graphic display, you can gain access to the ActiveX control’s methods, properties, and
events using VBA code.
For an overview of how VBA code works in FactoryTalk View SE, see Chapter 16 in
Volume 1 of the FactoryTalk View Site Edition User’s Guide. For detailed information
and code examples, see the FactoryTalk View Site Edition Help.

21-22
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

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.

21 • Placeholder
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
“Viewing object properties in the Property Panel” on page 19-5.

The run-time behavior of ActiveX objects depends on the vendor’s implementation. Before
making your application available to users, test ActiveX objects thoroughly to ensure they behave
as desired.

Connecting tags to an ActiveX object’s properties

ActiveX objects have sets of different properties. To view an object’s properties, right-
click the object, and then click Property Panel.
The content of the Property Panel is determined by the application that created the
ActiveX object, not by FactoryTalk View.
In the following illustration, the Property Panel is for an ActiveX check box named
CheckBox1. Clearing this check box changes an oven’s temperature control from
Automatic mode to Manual mode.

CheckBox1 is the
default name of this
object.

The object’s Value

property is assigned
to the Auto tag in the
Oven folder.

This connects the

check box to an
oven’s temperature
control.

For information about a property, select the property, and then click Help.

21-23
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

About ActiveX object names

As shown in previous illustration, ActiveX objects have a default name. The name is
used:
„ to identify the object when logging its events.
For information about ActiveX events, see “Connecting tags to an ActiveX object’s
events” on page 21-25.
„ 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. For more information, see
“Connecting tags to an object’s methods” on page 21-25.
You can change the default name for any object. For more information about object
naming, see page 19-19.

Viewing an object’s methods

The Object Methods dialog box shows the methods implemented for the selected object.
To view the object’s methods, right-click the object, and then click Methods.

For more information

about the object and
its methods, click this
button.

For details about options in the Object Methods dialog box, click Help.

21-24
 • • • • •
21 • ANIMATING GRAPHIC OBJECTS

Connecting tags to an object’s methods

21 • Placeholder
A method is an action the ActiveX object can perform.
Methods are part of the object. You can:
„ view a list of the object’s methods.
„ find documentation for the object’s methods.
„ use the Invoke command to call the object’s methods.

Using the Invoke command to call a method

Use the FactoryTalk View Invoke command to call a method for the named ActiveX
object. With the Invoke command you can:
„ assign the value returned by a method to a tag.
„ set an object’s property to a tag value or a constant.
„ set a tag to the value of an object property.
To specify parameters for the Invoke command, use the Command Wizard. For details
about using the Invoke command, see the FactoryTalk View Site Edition Help.

To use the Invoke command to interact with an ActiveX object, the object must have a name.

Connecting tags to an ActiveX object’s events

The ActiveX Control Events dialog box shows the events associated with the selected
ActiveX object, and allows you to specify FactoryTalk View commands or macros that
will run when an event occurs at run time.
You can also use VBA code to make an ActiveX object’s properties, methods, and events
interact with FactoryTalk View SE. For VBA code examples, see the FactoryTalk View
Site Edition Help.

To view an ActiveX object’s events

„ Right-click the object, and then click ActiveX Events.

21-25
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Click here
to open the
Command
Wizard.

Click here for

information from
the vendor, about
the object and its
events.

For details about options in the ActiveX Control Events dialog box, click Help.

21-26
22 Setting up navigation

22 • Placeholder
This chapter describes:
„ what a display hierarchy is.
„ setting up ways to move among displays in an application.
„ setting up keys to run FactoryTalk® View commands.
„ creating and running client key components.

Designing a display hierarchy for an application

An important part of designing a complete operator interface is determining how
operators will navigate through and interact with graphic displays in an application.
To direct an operator through the main parts of an application, set up a hierarchy (or
series) of graphic displays, that provides progressively more detail as the operator moves
through different levels of information and data.
The display hierarchy can represent parts of a plant or process, as well as different types
of data displays. For example, the top level might represent an area in the plant, and the
bottom level might contain trends and alarm displays specific to each area.
Operators or supervisors with the necessary security permissions, might also be able to
navigate between areas in the application, or gain access to displays that provide specific
information, such as management summaries.
When designing a display hierarchy, consider the needs of the various application users,
including managers, supervisors, and operators. A hierarchy might include:
„ an initial graphic display that serves as a menu.
„ an overview of the plant, including links to displays located on FactoryTalk View
SE Servers in areas around the plant.
„ a comprehensive display of each process being monitored.
„ process-specific displays.
„ management summary displays.
„ trend displays of historical and real-time data.
„ alarm displays, for monitoring and responding to alarms.
The following illustration shows a simple display hierarchy design for a network
application that contains two areas:

22-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Main Menu
Graphic Display

Process-Wide Area 1 Area 2 Management

Alarm Summary Process Process Summary
Overview Overview

Process 1 Process 2 Process 3 Process 4

Monitoring Monitoring Monitoring Monitoring

Process 1 Process 2 Process 3 Process 4

Trend Display Trend Display Trend Display Trend Display

For a live example of a display hierarchy that involves different navigation methods, run the
FactoryTalk View SE Samples application. To do this, on the Windows Start menu, select
Programs, Rockwell Software, FactoryTalk View, and then click Samples Water.

Setting up ways to move among displays

FactoryTalk View gives you the tools for linking graphic displays and creating an overall
application structure that is easy for an operator to use.
You can create an application that is keyboard-based, touch screen-based, or combines
both navigation methods.
Although the methods look different to operators, they work similarly; that is, both
involve the use of FactoryTalk View commands.

Using commands to open, close, and switch displays

You can use the following FactoryTalk View commands to open, close, and switch
between open displays at run time.

22-2
 • • • • •
22 • SETTING UP NAVIGATION

Use the commands in macros, or as actions specified for touch zones, buttons, display
keys, or object keys in a graphic display.

22 • Placeholder
To do this Run this command
Open the specified graphic display. Display
If the specified display is already open and it allows
multiple running copies (set up in the Display Settings
dialog box), the Display command opens another copy
of the display and makes it active.
If the specified display is already open and it does not
allow multiple running copies, the Display command
makes the display active.
A display of type:
„ Replace opens on top of other open displays,
and closes the ones it overlaps.
„ Overlay opens on top of any open displays, but
does not close them.
„ On Top opens on top of any open displays and
remains in the foreground.
Close the active or specified graphic display. Abort
Use the Abort command when you cannot use a display
of type Replace to close other running displays.
Pull the specified graphic display in front of other open PullForward
displays.
If the specified display is of type Replace or Overlay, the
PullForward command gives the display focus, and
positions it behind any On Top display that is open.
Push the specified graphic display behind other open PushBack
displays.
If the specified display is of type On Top, the PushBack
command positions the display behind any other open
On Top displays, but in front of any open Replace or
Overlay displays.

The PullForward and PushBack commands provide quick display changes because displays are
already open. However, the more displays you have open, and the more complex the displays
are, the more memory and CPU are used.

Commands for opening, closing, and switching displays run only at the FactoryTalk View
SE Client. Attempting to run these commands at a FactoryTalk View SE Server (for
example, in a server startup macro) or in FactoryTalk View Studio, will result in errors.

22-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

For more information about where commands run, see Appendix A in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

Example: Setting up navigation using keyboard operation

The graphic display in this example is designed to act as a menu, by providing keys that
an operator can press to open graphic displays representing different processes.

To create this display, the designer assigned various FactoryTalk View commands to keys
using the three types of key definitions: object, display, and client. In all cases, keys (not
mouse buttons) were defined to run commands.
Object keys and display keys are set up in the Graphics editor. For more information, see
Chapter 21, Animating graphic objects.
Client keys are created in the Client Keys editor. For more information, see “Creating
client keys” on page 22-10.

22-4
 • • • • •
22 • SETTING UP NAVIGATION

Example 2: Setting up navigation using mouse and touch screen

22 • Placeholder
operation
The graphic display in this example contains buttons that an operator can click using a
mouse, or press on a touch screen, to open detail displays. This display acts as a menu and
presents information.

To create the buttons, the designer used the Button drawing tool in the Graphics editor.
The buttons can be selected with a mouse or by pressing a touch screen. For information
about creating buttons, see “Creating the different types of push buttons” on page 20-11.

Choosing display types with navigation in mind

When designing an application, the display types you choose give you additional control
over how an operator can navigate from one display to another.
For example, use the On Top option to keep a display on top at all times, even when
another display has focus.

22-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Or use the Replace option if you want a display to replace any open displays that it covers
or touches, when it opens.
You select a type for a graphic display in the Display Settings dialog box. For more
information, see “Specifying the display type” on page 19-36.

Displays that you want to run in a fixed position, for example, menus or banners, can be docked
to the inside of the FactoryTalk View SE Client window. For more information, see “Docking
displays to the FactoryTalk View SE Client window” on page 19-45.

Reducing display call-up time

To reduce the time required to open a graphic display, load it into the display cache. You
can load the display:
„ before it is displayed, by using the Display command with the /Z or /ZA parameter.
For details, see the FactoryTalk View Site Edition Help.
„ when it is displayed for the first time, by using the Cache After Displaying option in
the Display Settings dialog box. For details, see “Caching displays” on page 19-38.

Setting up keys to run FactoryTalk View commands

You can associate FactoryTalk View commands with objects in a display, or with the
entire display, using object or display key animation.
You can also associate commands with keys that are independent of objects or displays,
and are available at all times throughout the system, by creating client keys.
Operators can use keys to interact with the system, for example, to change displays or set
tag values. When deciding what type of key to create, use the following table as a guide:

To do this Set up For details, see

Associate a key with a Object key animation in the page 21-17
specific graphic object Graphics editor
(object key)
Associate a key with a Display key animation in the page 21-19
specific graphic display Graphics editor
(display key)
Create a key that works A key definition component page 22-10
everywhere on an in the Client Keys editor
FactoryTalk View client
(client key)

22-6
 • • • • •
22 • SETTING UP NAVIGATION

General rules governing precedence

22 • Placeholder
You can assign a single key to one or more of the three types of key definitions—object,
display, or client.
For example, you could assign the F2 key to open a valve when the valve object has input
focus, close a popup display that has focus, and, as a client key, to open a graphic display
containing a process overview.
When a single key has more than one definition, the following rules of precedence apply:
„ When a graphic display is active and an object has input focus, object keys have
precedence over display keys and client keys.
„ When a graphic display is active, display keys have precedence over client keys.
For example, if you assign the F2 key as a display key in some graphic displays in an
application, and you assign F2 as a client key in the same application, F2 will only
work as a client key if the active display does not also use F2 as a display key.
When designing an application, pay particular attention to the keys used by embedded
objects.
Object keys and display keys generally have precedence over keys used by embedded
objects (for example, ActiveX®, or OLE objects).
However, keys used by OLE objects that are not part of FactoryTalk View (for example,
an Excel worksheet), have precedence over object or display keys. For details, see the
pages that follow.

Precedence and the F1 key

When you are developing an application in FactoryTalk View Studio, the F1 key is
reserved for opening context-sensitive Help.
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 opening Help.

Precedence and embedded ActiveX objects

When a graphic display is active and an embedded ActiveX object has input focus, a key
that triggers an action in the embedded object will not trigger that action, if the same key
is also defined as an object or display key.
Instead, when you press the key, the action associated with the object key or display key
will be triggered.
Say, for example, that an ActiveX slider object controls the speed of a motor by using the
F2 key to increase the speed and the F3 key to decrease the speed. If F2 is also defined as

22-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

an object key to jog the motor’s position, pressing F2 when the slider has input focus will
always jog the motor’s position, instead of increasing the motor’s speed.
However, if a key that triggers an action in an embedded ActiveX object is also defined as
a client key, pressing that key will trigger both the action defined for the embedded object
and the action defined for the client key.
For example, if the F2 key for an ActiveX gauge object increases a motor’s speed, and F2
is also defined as a client key to print the current graphic display, each time the operator
presses F2, the motor’s speed will be increased, and the graphic display will be printed.

Precedence and embedded OLE objects

For embedded OLE objects, a key that triggers an action in the embedded object will
trigger only that action, even if the key is also defined as an object or display key. In this
case, the action defined for the object or display key will not be triggered at all.
However, if a key that triggers an action in an embedded OLE object is also defined as a
client key, pressing that key will trigger both the action defined for the embedded object
and the action defined for the client key.

Keyboard shortcuts
The following keyboard shortcuts are normally reserved for use by Windows® and
FactoryTalk View SE.

To do this Press this key

Move focus to the object with the next highest index Tab
number.
Move focus to the object with the next lowest index Shift+Tab
number.
Move focus to the next object, in the direction the Ctrl+Up Arrow,
arrow key points. Ctrl+Left Arrow,
Ctrl+Down Arrow,
Ctrl+Right Arrow
Move focus to the next window. Ctrl+F6
Move focus to the previous window. Ctrl+Shift+F6
Close the active window. Ctrl+F4 or
Ctrl+Shift+F4

22-8
 • • • • •
22 • SETTING UP NAVIGATION

To do this Press this key

22 • Placeholder
Perform the press and release actions for the button Enter
object that has focus.
Download the value in the input object that has
focus.
Open the Recipe dialog box when a recipe object
has focus. If Ctrl+W was pressed previously, the
recipe is saved. If Ctrl+R was pressed previously,
the recipe is restored.
Open the on-screen keyboard, if the input or recipe
object with focus is set up to display the keyboard.
Upload data into all input objects in the display. PgUp
Upload data into the input object that has focus. Ctrl+PgUp
Download data from all input objects in the display. PgDn
Download data from the input object that has focus. Ctrl+PgDn
Delete the contents of the input object. Home+Shift+End+Del
Move input focus to the recipe object, and prepare Ctrl+R
for a recipe restore.
Move input focus to the recipe object, and prepare Ctrl+W
for a recipe save.
Open the Recipe dialog box. + on the numeric keypad
If Ctrl+W was pressed previously, the recipe is
saved. If Ctrl+R was pressed previously, the recipe
is restored.
Move the selection bar on the Object Key menu. Up Arrow,
Down Arrow
Close the Object Key menu, or exit input mode for Esc
the updating input object that has focus.
Move the cursor one position left or right. Left Arrow,
Right Arrow
Delete the character to the left of the cursor. Backspace
Delete the character to the right of the cursor. Del
Delete all characters from the cursor position to the Shift+End+Del
end of the line.
Copy the selected items to the clipboard. Ctrl+C or Ctrl+Ins

22-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To do this Press this key

Cut the selected items and place them in the Ctrl+X or Shift+Del
clipboard.
Paste the contents of the clipboard at the current Ctrl+V or Shift+Ins
cursor position.
Position the cursor at the beginning of the data entry Home
object.

The arrow keys perform different actions when a trend graphic object has focus. For details, see
page 26-28.

Precedence and reserved keys

If you assign a reserved key to an object or display key, the object or display key function
takes precedence, and the default, reserved function of that key is disabled.
However, if you use a reserved key or key combination as a client key, the key will
perform both the actions of the client key and the action of the reserved key.

Defining client key actions for reserved keys is not recommended, as the results can be
unpredictable.

Creating client keys

A client key is associated with commands or macros that run when the key is pressed.
To create a client key, you create a client key component in the Client Keys editor. A
single component can contain more than one client key definition.
Client keys are similar to object keys and display keys, except client keys are not
dependent on a particular graphic object or display. Client keys are active at all times.

To open the Client Keys editor

„ In FactoryTalk View Studio, in the Explorer window, open the Logic and Control
folder, right-click Client Keys, and then click New.

22-10
 • • • • •
22 • SETTING UP NAVIGATION

22 • Placeholder
For details about the options in the editor, click the Help button.

Running client key components

To run a client key component, use one of these methods:
„ Use the FactoryTalk View Key command in a macro or anywhere else you can use
FactoryTalk View commands. For details, see the FactoryTalk View Site Edition Help.
„ Run the client key component when the FactoryTalk View SE Client runs. For details,
see Help for the FactoryTalk View SE Client Wizard.

You cannot run more than one client key component at a time. If you try to do this, the
components are not merged. Instead, the second component overrides the first component.

22-11
23 Creating expressions

23 • Placeholder
This chapter describes:
„ what expressions are, and where you can use them.
„ working in the Expression editor.
„ using tag names and tag placeholders in expressions.
„ using constants in expressions.
„ using operators to modify values.
„ using built-in functions.
„ using if-then-else logic.

About expressions
Sometimes the data you gather from devices is only meaningful when you:
„ compare it to other values.
„ combine it with other values.
„ create a cause-effect relationship with other values.
Expressions allow you to create mathematical or logical combinations of data that return
more meaningful values.

Where you can use expressions in FactoryTalk View SE

In FactoryTalk® View Studio, you can set up expressions for different purposes, in the
following editors:
„ In the Graphics editor, use an expression to control the appearance of a graphic
object, or to display the value of an expression in a numeric or a string display object.
„ In the Derived Tags editor, specify the name of a tag that will store the result of an
expression.
„ In the Events editor, associate an expression with an action (a command or macro).
When the expression changes from false to true (from 0 to any non-zero value), the
action runs.

23-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ In the Data Log Models editor, when setting up file management for a data log
model, use an expression to determine when log files are created.

You can also use expressions to set the value of a tag, using the If or Set command. For details,
see the FactoryTalk View Site Edition Help.

Working in the Expression editor

Editors that can use expressions contain an Expression box. The editors might also
contain expression buttons, and an Expression column.
For example, the following illustration shows the Expression box, buttons, and column in
the Events editor.

Type the expression

in the Expression box.

Select from lists of

components, to help
build the expression.

Check the syntax of

the expression.

View the expression

in the Expression
column.

Dialog boxes or tabs in which you can type expressions contain an Expression button for
opening the Expression editor.

23-2
 • • • • •
23 • CREATING EXPRESSIONS

For example, the following illustration shows the Expression button in the Connections
tab of the Numeric Input Properties dialog box.

23 • Placeholder
Click *** to open the
Expression editor.

If the button has no

caption, the property
does not allow an
expression.

Expression components
You can build an expression using any of the following components:
„ tag values
„ tag placeholders
„ constants
„ mathematical, relational, logical, and bitwise operators
„ built-in functions
„ if-then-else logic
To select the components to use in an expression, click the following buttons in the
Expression box or editor.

To open this list Click

If-then-else operators

Logical operators

Relational operators

Arithmetic operators

Bitwise operators

Built-in functions

23-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To open this list Click

Tags (in the Tag Browser)

FactoryTalk alarms (in the Alarm

Source Browser)

Checking the syntax of an expression

Use the Check Syntax button to verify that the expression you typed uses correct syntax.
If the syntax is invalid, an error is displayed in the Check Syntax box.
You can check the syntax at any time while the Expression editor is open. In editors with
an Expression box, the syntax is checked automatically, when you click Accept or OK.

Cutting, copying, and pasting expressions

You can cut, copy, or paste an expression or parts of an expression. How you perform
these actions depends on whether the expression is in a window or in a dialog box.
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 only use the keyboard because there is no
access to the menu bar or toolbar.
When you cut or copy an expression to the clipboard, you can paste it into any other
Expression box. You can also paste it into a command line.

Formatting expressions
You can format expressions using tabs, line returns, and multiple spaces so they are easier
to read.
However, do not let tag names, key words, function names, or function arguments span
more than one line.

Example: Formatting an expression

To format this if-then-else statement, you can align the Else with the appropriate If, so the
logic is easy to understand:
If (tag1>tag2) Then 0
Else If (tag1>tag3) Then 2
Else 4

23-4
 • • • • •
23 • CREATING EXPRESSIONS

Or you can condense the statement as follows:

23 • Placeholder
If (tag1>tag2) Then 0 Else If (tag1>tag3) Then 2 Else 4

Using tag names and tag placeholders in expressions

You can use a tag name as part of an expression, or the tag can stand alone as the entire
expression.
To supply a tag name, type it in the Expressions box, or click Tags to browse for and select
a tag in the Tag Browser. Enclose tag names that contain dashes or start with a number in
brackets {} when you use them in an expression.
Also use brackets when using wildcard characters (* or ?) to represent multiple tags in an
expression. You can use wildcards, for example, when using HMI tag alarm functions. For
more information about these built-in functions, see page 23-15.

This wildcard character Does this

? Matches any single character.
* Matches any number of characters, including the
backslash (\) character.

For more information about working with tags, see Chapter 9 in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

Specifying the area with a tag name

In a FactoryTalk View SE network application, when referring to a tag in a different area,
you can use an absolute or relative reference to the tag.
For more information about using references with tag names, see “About tag references”
on page 9-6, in Volume 1 of the FactoryTalk View Site Edition User’s Guide.

Using placeholders to specify tag values

In the Graphics editor, you can use tag placeholders instead of tag names, to specify tag
values in expressions.
A tag placeholder is the cross-hatch character (#) followed by a number from 1 to 500.
Placeholders let you reuse graphic displays, by substituting different tag values into the
displays at run time.
For more information, see “Using placeholders to specify tag values” on page 19-29.

23-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Using constants in expressions

To provide a constant value for an expression, use any of the following formats:
„ integer (123)
„ floating point (123.45)
„ scientific notation (1.2345E ² )
„ string constant (“character string”)
„ ‘pi’ string (to represent the symbol π)
FactoryTalk View replaces the string with its numeric value.

Using operators to modify values in expressions

To modify the values returned to an expression, use arithmetic, relational, logical, or
bitwise operators.

Arithmetic operators
Arithmetic operators calculate values based on two or more numeric values.
The following table describes the arithmetic operators, with examples. (In the examples,
tag1 = 5 and tag2 = 7.)

Symbol Operator Example

+ 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
The modulus operator is the remainder of one
number divided by another. For example, the
remainder of 13 divided by 5 is 3; so 13%5=3
Important: This operator is for integers only, not
floating point numbers.
** exponent tag1**tag2
returns a value of 78125

23-6
 • • • • •
23 • CREATING EXPRESSIONS

Be sure that any tag value you use as a divisor cannot at some point have a value of 0.
Expressions that attempt to divide a number by 0 produce an error at run time.

23 • Placeholder
String operands
The + operator can be used to join string operands. For example, the expression “hello” +
“world” returns: helloworld.

Relational operators
Relational operators compare two numeric or string values, to provide a true or false
result. If the statement is true, the expression returns a value of 1. If the statement is false,
the expression returns a value of 0.
The following table describes the relational operators, with examples. (For the numeric
examples, tag1 = 5 and tag2 = 7. For the string examples, serial_no = ST009.)

Symbol Operator Numeric examples String examples

EQ, == equal tag1==tag2 serial_no==“ST011”
false false
NE, <> not equal tag1<>tag2 serial_no<>“ST011”
true true
LT, < less than tag1<tag2 serial_no<“ST011”
true true
GT, > greater than tag1>tag2 serial_no>“ST011”
false false
LE, <= less than or equal to tag1<=tag2 serial_no<=“ST011”
true true
GE, >= greater than or equal to tag1>=tag2 serial_no>=“ST011”
false false

How string operands are evaluated

String operands are evaluated by case and by alphabetical order. Lower case letters are
greater than upper case letters. For example, h is greater than H. Letters later in the
alphabet are greater than those earlier in the alphabet. For example, B is greater than A.

Logical operators
Logical operators determine the validity of one or more statements. There are three logical
operators: AND, OR, and NOT. The operators return a non-zero value if the expression is
true, or 0 if the expression is false.

23-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

The following table describes the logical operators, with examples. (In the examples,
tag1 = 5 and tag2 = 7.)

Symbols Operator Action Example

AND, && and Returns a 1 if the statements to the right (tag1<tag2) AND (tag1==5)
and to the left of the operator are both true. Both statements are true; returns a 1.
OR, || or Returns a 1 if either or both statements are (tag1>tag2) OR (tag1==5)
true. tag1==5 is true; returns a 1.
NOT negation Reverses the logical value of the statement NOT (tag1<tag2)
it operates on. Although tag1<tag2 is true, NOT reverses
the logical value; returns a 0.

The parentheses are essential in the these expressions. For more information, see “Evaluation
order of operators” on page 23-9.

Bitwise operators
Bitwise operators examine and manipulate individual bits within a value.
The following table describes the bitwise operators.

Bitwise operators are for integers only, not for floating-point numbers.

Symbol Operator Action

& AND Compares two integers or integer tags on a bit-by-bit basis.
Returns an integer with a bit set to 1 if both the corresponding bits in the
original numbers are 1. Otherwise, the resulting bit is 0.
| inclusive OR Compares two integers or tags on a bit-by-bit basis.
Returns an integer with a bit set to 1 if either or both of the corresponding
bits in the original numbers are 1. If both bits are 0, the resulting bit is 0.
^ exclusive OR (XOR) Compares two integers or tags on a bit-by-bit basis.
Returns an integer with a bit set to 1 if the corresponding bits in the original
numbers differ. If both bits are 1 or both are 0, the resulting bit is 0.
>> right shift Shifts the bits within an integer or tag to the right.
Shifts the bits within the left operand by the amount specified in the right
operand. The bit on the right disappears.
Either a 0 or a 1 is shifted in on the left, depending on whether the left-most
bit is a 0 or a 1. If the left-most bit is 0, a 0 is shifted in. If the left-most bit
is 1, a 1 is shifted in. In other words, the sign of the number is preserved.

23-8
 • • • • •
23 • CREATING EXPRESSIONS

Symbol Operator Action

23 • Placeholder
<< left shift Shifts the bits within an integer or tag to the left.
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.
Reverses every bit within the number so every 1 bit becomes a 0 and vice
versa.

Example: Bitwise operators

For these examples tag1=5 (binary 0000 0000 0000 0101) and tag2=2 (binary 0000 0000
0000 0010)
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)

Evaluation order of operators

In expressions with more than one operator, evaluation order is determined as follows:
„ Operators in parentheses are evaluated first. Use parentheses to change the order.
„ Two operators of the same precedence are evaluated from left to right.

23-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ Operators not enclosed in parentheses are evaluated as follows:

Evaluation order Symbols

1 (highest) ()
2 NOT
~
3 *
/
MOD, %
**
AND, &&
&
>>
<<
4 +
–
OR, ||
|
^
5 EQ, =
NE, <>
LT, <
GT, >
LE, <=
GE, >=

Examples: Evaluation order

In the following examples, tag1 = 5, tag2 = 7, and tag3 = 10.
_____________________________
(tag1>tag2) AND (tag1<tag3)
is evaluated in this sequence:
1. tag1>tag2=0
2. tag1<tag3=1
3. 0 AND 1=0
The expression evaluates to 0 (false).
_____________________________
tag1>tag2 AND tag3

23-10
 • • • • •
23 • CREATING EXPRESSIONS

is evaluated in this sequence:

23 • Placeholder
1. tag2 AND tag3=1
2. tag1>1=1
The expression evaluates to 1 (true).
_____________________________
NOT tag1 AND tag2>tag3 ** 2
is evaluated in this sequence:
1. NOT tag1=0
2. 0 AND tag2=0
3. tag3 ** 2=100
4. 0>100=0
The expression evaluates to 0 (false).

Using built-in functions in expressions

The following sections describe the built-in functions you can use in FactoryTalk
View SE expressions.
Many of the built-in functions check for specific true and false conditions. If the condition
is true, the expression returns a value of 1. If the condition is false, the expression returns
a value of 0.

Math functions
Use the built-in math functions to calculate the square root, log (natural or base 10), or
trigonometry ratios (in radians or degrees) of a tag or expression.

This function Returns this value

SQRT (expression) The square root of the expression
LOG (expression) The natural log of the expression
LOG10 (expression) The base ten log of the expression
SIN (expression) The sine of the expression in radians
COS (expression) The cosine of the expression in radians
TAN (expression) The tangent of the expression in radians

23-11
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

This function Returns this value

ARCSIN (expression) The arc sine of the expression in radians
ARCCOS (expression) The arc cosine of the expression in radians
ARCTAN (expression) The arc tangent of the expression in radians
SIND (expression) The sine of the expression in degrees
COSD (expression) The cosine of the expression in degrees
TAND (expression) The tangent of the expression in degrees
ARCSIND (expression) The arc sine of the expression in degrees
ARCCOSD (expression) The arc cosine of the expression in degrees
ARCTAND (expression) The arc tangent of the expression in degrees

File functions
Use the built-in file functions to check whether a file exists, or to check the amount of free
disk space.
The file parameter is the path name, surrounded by quotes. The drive parameter is the
drive letter.

This function Returns this value Example

FILE_EXISTS(“file”) 1 (true) if the specified FILE_EXISTS(“C:\Documents and
file exists Settings\All Users\Shared Documents\
RSView Enterprise\SE\ActivityLog\
Activity.exp”)
Returns 1 (true) if the file exists or 0 (false) if
the file does not exist.
Use this function to set a tag when a specified
file has been created or deleted.
FREE_BYTES(drive) The number of bytes FREE_BYTES(c)
free on the specified Returns the number of bytes available on
drive drive C, up to a maximum of 2.1 GB.
Use this function to display a message or
trigger an alarm when disk space is getting
low.

To have an expression containing these functions evaluated more than once, assign the
expression to an event rather than to an object in a graphic display.

23-12
 • • • • •
23 • CREATING EXPRESSIONS

Time functions

23 • Placeholder
Use the built-in time functions to examine system time. These functions use the time or
interval parameters.

This function Returns

TIME(“time”) 1 (true) if the time specified is the current time.
BEFORE_TIME(“time”) 1 (true) if the expression is evaluated before the
specified time.
AFTER_TIME(“time”) 1 (true) if the expression is evaluated after the
specified time.
INTERVAL(“interval”) 1 (true) if the specified time interval has elapsed—
the interval timer starts running when an event file
starts running.

The time and interval parameters must be enclosed in quotes.

The time parameter can include the following options:

„ day of week[Sun, Mon, Tue, Wed, Thu, Fri, or Sat]
„ month[Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, or Dec]
„ date[1 to 31]
„ year[1997 to 2100]
„ hour of day[00: to 23:]
„ minute[:00 to :59]
„ second[:00 to :59]
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.

Example 1: Specific time parameters

The following all represent the same date and time, and are valid time parameters:
„ "mon aug 22 2005 17:00"
„ "mon aug 22 2005 17: :00"

23-13
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ ":00 aug 22 mon 2005 17:"

The validity of the date is not checked. For example, if Aug 22 2005 is not a Monday, this error
is not detected.

Example 2: Less specific time parameters

Following are valid examples of time parameters:
„ “17:00” means any day at 5:00 a.m.
„ “ :30 ” means any hour, on the half hour
„ “ mon 17:” means 5:00 p.m. each Monday
The interval parameter has the format
<number> <units>
where <units> is one of:
„ mil (millisecond)
„ sec (second)
„ min (minute)
„ hou (hour)
„ day (day)
„ wee (week)
„ mon (month)
„ yea (year)

Example 3: Time and interval functions

TIME(“sun aug 21 2005 14:30”)
Returns 1 (true) if it is exactly 2:30 p.m. and 0 seconds, on Sunday, August 21, 2005;
otherwise returns 0 (false).
AFTER_TIME(“sun aug 21 2005 14:30”)

23-14
 • • • • •
23 • CREATING EXPRESSIONS

Returns 1 the first time the expression is evaluated after 2:30 p.m. on Sunday, August 21,
2005.

23 • Placeholder
BEFORE_TIME(“aug 21 2005”)
Returns 1 (true) the first time the expression is evaluated before August 21, 2005.
INTERVAL(“1 min”)
Returns 1 (true) if a minute has elapsed since the expression last returned a 1.
(tag1>500) and INTERVAL (“30 sec”)
Returns 1 (true) when tag1>500 on some 30-second interval since the event file started
running. (It does not mean 30 seconds after tag1>500.)

Tag functions
Use the built-in tag functions to examine the status of a tag, HMI tag alarm, or HMI alarm
event (or multiple tags or alarm events).
For information about setting up HMI tag alarms, see Chapter 11 in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

If a graphic display requires more than 20 HMI tag alarm functions, for performance reasons
it is better to use the alarm functions in derived tags. For details, see Help for alarm functions.

This function Returns this value

alm_ack(tag or alarm event) 1 (true) if the tag’s alarm or the alarm event has
or been acknowledged.
alm_ack(tag*) If examining multiple tags, 1 (true) if one or more
alarms have been acknowledged.
alm_allacked(tag or alarm event) 1 (true) if the tag’s alarm or the alarm event has
or been acknowledged.
alm_allacked(tag*) If examining multiple tags, 1 (true) if all tags
matching the pattern have been acknowledged. If
any of the tags has not been acknowledged, the
expression returns 0.
alm_fault(tag or alarm event) 1 (true) if there has been an alarm fault for the
or specified tag or alarm event.
alm_fault(tag*) If examining multiple tags, 1 (true) if there has
been an alarm fault for one or more of the tags.

23-15
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

This function Returns this value

alm_in_alarm(tag or alarm event) 1 (true) if the tag or alarm event is in alarm.
or If examining multiple tags, 1 (true) if one or more
alm_in_alarm(tag*) of the tags or alarm events are in alarm.
alm_level(tag or alarm event) The alarm level or threshold for an analog tag or
or alarm event. This can be value between 1 and 8,
or 0 if the tag is not in alarm.
alm_level(tag*) If examining multiple tags, the highest level of the
tags in alarm. For example, if the current alarms
are levels 2, 6, and 8, this function returns the
value 8.
alm_severity(tag or alarm event) The severity of the alarm or alarm event. This can
or be a value between 1 and 8, or 0 if the tag or alarm
event is not in alarm.
alm_severity(tag*) If examining multiple tags, the highest severity of
the tags or alarm events that are in alarm. For
example, if the current alarms have severities
of 1, 3, and 6, this function returns the value 1.
alm_suppress(tag or alarm event) 1 (true) if the tag’s alarms are suppressed.
or For multiple tags, 1 (true) if one or more of the
alm_suppress(tag*) tags’ alarms are suppressed.
alm_tags_inalm(tag or alarm event) 1 (true) if the tag or alarm event is in alarm.
or If examining multiple tags, the number of tags or
alm_tags_inalm(tag*) events in the query that are in alarm, or 0 if none
are in alarm.
alm_tags_inalm_unack(tag or alarm 1 (true) if the tag or event is in alarm and
event) unacknowledged.
or If examining multiple tags, the number of tags or
alm_tags_inalm_unack(tag*) events in the query that are both in alarm and
unacknowledged, or 0 if none are in alarm and
unacknowledged.
alm_tags_unack(tag or alarm event) 1 (true) if the tag or alarm event is
or unacknowledged; 0 if the tag or event is
alm_tags_unack(tag*) acknowledged.
If examining multiple tags, the number of tags or
alarm events in the query that are unacknowledged,
or 0 if all are acknowledged.
comm_err(tag) 1 (true) if the last read or write operation for the
specified tag indicated a communication failure.
You can examine the status of only one tag with
this function.

23-16
 • • • • •
23 • CREATING EXPRESSIONS

In a network application, you can specify an absolute or a relative reference to a tag. For
more information, see page 9-6 in Volume 1 of the FactoryTalk View Site Edition User’s

23 • Placeholder
Guide.
To examine multiple tags at once, use a wildcard character in the expression argument.

This wildcard character Does this

? Matches any single character.
* Matches any number of characters, including the
backslash (\) character.

Example: HMI tag alarm functions

ALM_IN_ALARM(/Ingredients::vessel3\TIC3\pv*)
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.
In this example, the tags are in the area called Ingredients.

Security functions
Use the built-in security functions to control access to an application, based on a user’s
identity or security permissions.

This function Returns this value Example

CurrentUserHasCode 1 (true) if the user CurrentUserHasCode(ABP)
possesses any of the Returns 1 if the current user has been
specified security codes. assigned one or more of the specified codes.
If checking multiple If not, returns 0.
security codes, do not
type a space between the
security code letters.
CurrentUserName The name of the current CurrentUserName()
user. The user’s domain Returns the name of the current user.
is not included.

23-17
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Language function
Use the built-in language function to return the name of the current run-time language. An
expression containing this function is evaluated whenever a language switch occurs.

This function Returns this value Example

CurrentLanguage The RFC1766 name of CurrentLanguage()
the current run-time Returns en-US, if the current run-time
language. language is English (United States).

FactoryTalk alarm functions

Use the built-in FactoryTalk alarm functions to examine the status of one or more
FactoryTalk alarms.

This function Returns

AE_HighSeverityAcked (AlarmName) The highest severity value, from 1 to 1000, of
or specified alarms that have the state In Alarm and
AE_HighSeverityAcked (Alarm*) Acknowledged.
0 if none of the specified alarms is In Alarm and
Acknowledged.
AE_HighSeverityUnacked The highest severity value, from 1 to 1000, of
(AlarmName) specified alarms that have the state In Alarm and
or Unacknowledged.
AE_HighSeverityUnacked (Alarm*) 0 if none of the specified alarms is In Alarm and
Unacknowledged.
AE_InAlarmAckedCount (AlarmName) The number of specified alarms that have the state
or In Alarm and Acknowledged.
AE_InAlarmAckedCount (Alarm*) 0 if none of the specified alarms is In Alarm and
Acknowledged.
AE_InAlarmUnackedCount The number of specified alarms that have the state
(AlarmName) In Alarm and Unacknowledged.
or 0 if none of the specified alarms is In Alarm and
AE_InAlarmUnackedCount (Alarm*) Unacknowledged.
AE_NormalUnackedCount The number of specified alarms that have the state
(AlarmName) Normal and Unacknowledged.
or 0 if none of the specified alarms is Normal and
AE_NormalUnackedCount (Alarm*) Unacknowledged..

You can specify an absolute or a relative reference to an alarm source.

23-18
 • • • • •
23 • CREATING EXPRESSIONS

To examine multiple alarms at once (a set of alarms for a machine in a particular area, for
example) use a wildcard character in the expression argument.

23 • Placeholder
This wildcard character Does this
? Matches any single character.
* Matches any number of characters, including the
backslash (\) character.

For more information about using FactoryTalk alarm functions in expressions, and for
examples, see Chapter 12, “Setting up FactoryTalk alarms,” in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

About using FactoryTalk alarm names in expressions

To supply a FactoryTalk alarm name for an expression, type it in the Expressions box, or
click the Alarms button to browse for and select one or more tags in the Alarm Source
browser.
You must specify an alarm source when you use the built-in FactoryTalk alarm functions
in an expression. An alarm source might be a single alarm, or an area containing several
alarms.
When referring to an alarm source, you can use an absolute or relative reference.
Enclose alarm names that contain dashes or start with a number in brackets {} when you
use them in an expression. Also use brackets when using wildcard characters (* or ?) to
represent multiple alarms.
You can also use placeholders in alarm names, to substitue values for the placeholders at
run time. For more information about placeholders, see “Using placeholders to specify tag
values” on page 19-29.
For more information about the FactoryTalk alarm functions, see Chapter 12, “Setting up
FactoryTalk alarms,” in Volume 1 of the FactoryTalk View Site Edition User’s Guide.

Using if-then-else logic in expressions

Use if-then-else logic in an expression to carry out an action conditionally, or to branch
actions depending on the statements in the expression.
The if-then-else statements allow the expression to perform different actions in different
situations, and to repeat activities until a condition changes.

Do not confuse the if-then-else expression with the If command. For details about the If
command, see the FactoryTalk View Site Edition Help.

23-19
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To build conditional expressions, use the relational operators and the logical operators for
the statement, and values.
The if-then-else structure is:
If statement Then value1 Else value2
If the statement is true then the expression returns value1; if the statement is false then the
expression returns value2. Keep in mind that the statement is a mathematical equation and
true means a non-zero value, and false means 0.
Following is an illustration of the if–then–else structure:

enter

true
statement

false

value2 value1

exit

Nested if-then-else
It is common to nest an if-then-else structure inside the then or else part of an if-then-
else structure.

Example 1: Nested if-then-else

This expression:
If statement1 Then value1
Else if statement2 Then value2
Else value3

23-20
 • • • • •
23 • CREATING EXPRESSIONS

is interpreted in this way:

23 • Placeholder
enter

true
statement1

false

true
statement2

false

value3 value2 value1

exit

Example 2: Nested if–then–else

This expression:
If statement1 Then
If statement2 Then value1
Else value2
Else value3
is interpreted in this way:

23-21
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

enter

true statement2 true value1

statement1

false false

value3 value2

exit

23-22
24 Creating embedded variables

24 • Placeholder
This chapter describes:
„ what embedded variables are.
„ where you can insert embedded variables.
„ how to create numeric embedded variables.
„ how to create string embedded variables.
„ how to create time and date embedded variables.
„ how embedded variables are displayed at run time.
„ how embedded variables are updated at run time.

About embedded variables

Embedded variables allow you to display values that change dynamically at run time.
You can insert embedded variables into the text captions on graphic objects, tooltip text,
local message text, and the title bar text of graphic displays.
Embedded variables can contain the following elements:
„ tags
„ tag placeholders
„ literal numbers or strings
„ the time and date
For information about how embedded variables are updated at run time, see page 24-10.

Inserting embedded variables

You can insert embedded variables:
„ in the captions you create for graphic objects.
For graphic objects with multiple states, you can insert different embedded variables
in each state’s caption. For information about specific graphic objects, see Chapter 20,
Creating graphic objects.
„ in local messages you create in the Local Messages editor. For information about
creating local messages, see page 20-34.

24-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ in the tooltips you create for graphic objects. For information about creating tooltips,
see page 19-21 or see Help.
„ in the title bar text you create for graphic displays. For information about setting up
display titles, see page 19-35.
You can insert more than one embedded variable in the same caption, message, tooltip, or
display title.
For example, you might embed a tag value and a time variable in a local message. At run
time, when the local message is displayed, it will show the tag’s current value and the
current time. As the tag’s value and the time change, the embedded variable is updated.
You can also insert variables in the alarm messages you create for FactoryTalk alarm
definitions. For more information, see Chapter 12, “Setting up FactoryTalk alarms,” in
Volume 1 of the FactoryTalk View Site Edition User’s Guide.

Embedded variables are case sensitive and must use specific syntax to work. Otherwise, the
entire embedded variable is treated as a string of text.
To avoid this when inserting embedded variables, use the Numeric Variable, String Variable, and
Time and Date Variable dialog boxes, instead of typing the variables manually. For more
information about embedded variable syntax, see subsequent sections in this chapter.

To insert an embedded variable in the caption of a graphic object

1. Open the graphic object’s Properties dialog box.
2. Click the tab containing the Caption box (the General, Up Appearance, Label, or
States tab, depending on the type of object).
3. Click the Insert Variable button beneath the Caption box, or right-click the Caption
box, and then click Insert Variable.
4. Click the type of variable you want to insert (Numeric, String, or Time/Date).
5. Fill in the options in the dialog box that opens. For details, click Help.

To insert an embedded variable in a local message

1. Open the Local Messages editor
2. Right-click the Message column, and then click Edit String.
3. Click the Insert Variable button beneath the String Edit box, or right-click the String
Edit box, and then click Insert Variable.
4. Click the type of variable you want to insert (Numeric, String, or Time/Date).
5. Fill in the options in the dialog box that opens. For details, click Help.

24-2
 • • • • •
24 • CREATING EMBEDDED VARIABLES

To insert an embedded variable in the tooltip of a graphic object

1. Open the graphic object’s Properties dialog box.

24 • Placeholder
2. In the Common tab, click the Insert Variable button beneath the ToolTip text box, or
right-click the ToolTip text box, and then click Insert Variable.
3. Click the type of variable you want to insert (Numeric, String, or Time/Date).
4. Fill in the options in the dialog box that opens. For details, click Help.

Tooltips can consist of a single line of text, or multiple lines.

To insert an embedded variable in the title bar of a display

1. Open the Display Settings dialog box.
2. In the Properties tab, click the Insert Variable button beneath the Title Bar box, or
right-click the Title Bar box, and then click Insert Variable.
3. Click the type of variable you want to insert (Numeric, String, or Time/Date).
4. Fill in the options in the dialog box that opens. For details, click Help.

To modify an embedded variable

1. Right-click the embedded variable string in the Caption, String Edit, ToolTip text, or
Title Bar box, and then click Edit Variable.
2. Make the necessary changes in the Numeric, String or Time and Date Variable dialog
box, and then click OK.

Creating numeric embedded variables

Insert numeric embedded variables to display analog or digital tag values or literal
numbers in local message text, in a graphic object’s caption or tooltip, or in a graphic
display’s title bar.

24-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

In the Numeric Variable dialog box, select the Tag option to display the value of the
specified tag (or tag placeholder) in the embedded variable at run time.
Select the Literal number option, to display the number you type in the dialog box, or the
parameter value that replaces the tag placeholder.
Formatting options (Number of digits, Decimal places, Fill left with) apply to either a tag
value or a literal number. For example, if you type the literal number 9999, and select 2
decimal places, at run time the number will display as 99.99
For details about options in the Numeric Variable dialog box, click Help.
For information about how embedded variables are updated at run time, see page 24-10.

Syntax for numeric embedded variables that use a tag value

Numeric embedded variables that use a tag value use this syntax:
/*N:# Tag_name Fill_character DP:#*/
where
„ N indicates that it is a numeric embedded variable.
„ # indicates the number of digits.
„ Tag_name specifies which numeric tag’s value to display.
You can specify a tag placeholder instead of a tag name.
„ Fill_character is the fill character: NOFILL, ZEROFILL, or SPACEFILL.
„ # indicates the number of decimal places.

Example: Numeric embedded variable using a tag

At run time, the numeric embedded variable
/*N:3 Oven_temp NOFILL DP:0*/
would display the current value of an analog tag called Oven_temp, with 3 digits, no
decimal places, and no fill characters.

Syntax for numeric embedded variables that use a literal number

Numeric embedded variables that use literal numbers use this syntax:
/*LN:# ### Fill_character DP:#*/

24-4
 • • • • •
24 • CREATING EMBEDDED VARIABLES

where

24 • Placeholder
„ L indicates that the embedded variable will contain a literal number.
„ N indicates that it is a numeric embedded variable.
„ # indicates the number of digits.
„ ### is the literal number (or tag placeholder).
„ Fill_character is the fill character: NOFILL, ZEROFILL, or SPACEFILL.
„ # indicates the number of decimal places.

Example: Numeric embedded variable using a literal number

At run time, the numeric embedded variable
/*LN:3 9999 NOFILL DP:0*/
would display the number
9999
with no decimal places, and no fill characters.

Creating string embedded variables

Insert string embedded variables to display string tag values or literal text strings in local
message text, in a graphic object’s caption or tooltip, or in a graphic display’s title bar.

In the String Variable dialog box, select the Tag option to display the value of the
specified tag (or tag placeholder) in the embedded variable at run time.

24-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Select the Literal string option, to display the text string you type in the dialog box, or the
parameter value that replaces the tag placeholder.

The literal string you type (or specify in a parameter file) cannot contain spaces.

Formatting options for fixed number of characters apply to either a tag value or a literal
string. For example, if you type the literal string September, and select 3 for Fixed number
of characters (but no other options), at run time the string will display as Sep.
For details about options in the String Variable dialog box, click Help. For information
about how embedded variables are updated at run time, see page 24-10.

Syntax for string embedded variables that use a tag value

String embedded variables that use a tag value use this syntax:
/*S:# Tag_name*/
where
„ S indicates that it is a string embedded variable.
„ # indicates the fixed number of characters to display.
In the String Variable dialog box, clear the check box, Fixed number of characters, if
you don’t want to use a fixed number.
„ Tag_name specifies which string tag’s value to display. You can specify a tag
placeholder instead of a tag name.

Example: String embedded variable using a tag

At run time, the string embedded variable
/*S:20 Blower_status*/
would display the current value of the string tag named Blower_status, with a fixed length
of 20 characters.

Syntax for string embedded variables that use a literal string

String embedded variables that use a text string use this syntax:
/*LS:# SSS*/

24-6
 • • • • •
24 • CREATING EMBEDDED VARIABLES

where

24 • Placeholder
„ L indicates that the embedded variable will contain a literal string.
„ S indicates that it is a string embedded variable.
„ # indicates the fixed number of characters to display.
In the String Variable dialog box, clear the check box, Fixed number of characters, if
you don’t want to use a fixed number.
„ SSS is the literal string (or tag placeholder).

Example: String embedded variable using a literal string

At run time, the string embedded variable
/*LS:0 September28*/
would display the text string
September28
with no fixed number of characters.

A literal string embedded variable can contain numbers. However, if you want to format the
number (with decimal places, for example), insert a literal number instead. For details, see
“Creating numeric embedded variables” on page 24-3.

Creating time and date embedded variables

Insert time and date embedded variables to display the current time and date in local
message text, in a graphic object’s caption or tooltip, or in a graphic display’s title bar.

24-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

In the Time and Date Variable dialog box, select the format in which you want the current
time and date displayed at run time.
For details about options in the Time and Date Variable dialog box, click Help.
For information about how embedded variables are updated at run time, see page 24-10.

Syntax for time and date embedded variables

Time and date embedded variables use this syntax:
/*Time_date_format*/

where
Time_date_format uses one of these character sequences:

These characters Specify this format

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

Example: Time and date embedded variable

At run time, the time and date embedded variable
/*SDT*/
would display the short date followed the time, for example:
9/28/2006 1:12:25 PM
A space is inserted between the time and date at run time.

How embedded variables are displayed at run time

If there is no valid data available for an embedded variable, the caption, local message,
tooltip, or title bar that contains it will display question marks (?).
This might occur when a display first opens and the data has not arrived yet, or when there
is a problem that prevents communication with the data source.

24-8
 • • • • •
24 • CREATING EMBEDDED VARIABLES

Numeric embedded variables

24 • Placeholder
For numeric embedded variables that use tag values, how the value is displayed depends
on whether the data type is integer or floating-point: integer values are displayed as they
are; floating-point values are rounded to fit the number of digits specified for the variable.
For example, if 6 is the number or digits specified, the floating point value 1234.56 is
rounded to 1234.6, and the value 1234.44 is rounded to 1234.4. The decimal point
counts as one of the digits. If the value is negative, the minus sign also counts as a digit.
If the floating-point value, including a decimal point and a minus sign, contains more
digits than specified for the variable, the numeric variable is replaced with asterisks (*).

Number formats
Numeric embedded variables use 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 will also use a comma for the decimal symbol.

String embedded variables

For string embedded variables that do not use a fixed number of characters, the entire tag
value or literal string is displayed, unless a null character (? ) is read. Nothing after a null
character is displayed.
For string embedded variables that do use a fixed number of characters, the entire tag
value or literal string is displayed up to the number of characters specified, unless a null
character ( ? ) is read. Nothing after a null character is displayed.
If necessary, spaces are used to make up the specified number of characters.

Null characters have a hex value of 0, and indicate the end of a string. A null character does not
add to the actual length of the string.

By default, string variables that use a fixed number of characters display the characters
from left to right. To display characters from right to left, in the String Variable dialog
box, select the check box, Right-most characters in string are displayed.
You can also specify whether asterisks (* ) are displayed at run time, if the string is longer
than the width of the field it is embedded in.

Time and date embedded variables

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.

24-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Time and date formats

Time and date embedded variables use the time and date formats you set up on the run-
time computer. For example, if the time and date variable displays the short date, at run
time the variable will use the short date format set up for the run-time computer.

How embedded variables are updated at run time

How an embedded variable is updated at run time depends on the type of variable and
where it is embedded:
„ In caption text, title bar text, and local messages, numeric or string embedded
variables that use tag values are updated whenever a new tag value is read from the
data source.
Embedded variables that use tags are also updated when the graphic display is loaded
into the cache, using the Always Updating option. For information about setting up
display caching, see “Setting up displays to open more quickly” on page 19-43.
„ In tooltips on graphic objects, numeric or string embedded variables that use tag
values are updated only when the graphic display containing the object is opened.
Embedded variables that use tags in tooltips will not update dynamically, while the
display is running.
„ Time and date embedded variables are updated as the system time and date change.

24-10
25 Setting up data logging

25 • Placeholder
This chapter describes:
„ what data logging is.
„ data log storage formats.
„ creating a data log model.
„ working with ODBC data sources.
„ creating new files at run time.
„ switching log paths at run time.
„ logging on demand.
„ modifying existing data log models.
„ starting and stopping data logging.

About data logging

Data log is a FactoryTalk® View component that collects and stores tag values.
Logged data can be stored in an internal file set, or an ODBC-compliant (Open Database
Connectivity) database, and can be:
„ displayed in trends. To display historical data in a trend, assign a tag from a data log
model to a pen. For more information, see Chapter 26, Setting up trends.
„ archived for future use.
„ analyzed using any ODBC-compatible reporting software, such as Microsoft® Excel,
or Business Objects Crystal Reports®.

Gathering tag data in data log models

A data log model defines which tags to log data for, when to log the data, and where to log
the data.
In the Data Log Models editor, you also specify the format of the log files (file set, or
ODBC), and when to create and delete the files (also called records).
A single data log model can log data for up to 10,000 tags.

25-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Using multiple data log models

At run time, up to 20 data log models can run simultaneously on each FactoryTalk View
SE Server.
Use multiple data log models to:
„ store related information in separate file sets.
„ log groups of tags at different rates.
„ log groups of tags based on events.

Data log storage formats

Logged data is stored either in an internal file set or in an ODBC-compliant database.
Each data log file set includes files for storing numeric values (either integers or floating
point values), text, and tag names.
Internal file sets store tag values in proprietary-format files. You cannot view the contents
of the file sets, except in trends. File sets provide faster performance for historical trends
than an ODBC database.
If you log tag values to an ODBC database, you can view the data in trends, or use third-
party, ODBC-compliant tools to analyze and create reports from the data.
If the ODBC database becomes unavailable, FactoryTalk View logs the data to backup
files in proprietary format.
To use data in multiple formats, define multiple data log models for the same set of tags.

How log file sets are named

When you create a log file set, the set is given a name automatically. The name is based on
the date the file was created, and the type of data it contains. The maximum length of a log
file set’s name, including its path, is 200 characters.
File sets use the following file name format:
YYYY MM DD NNNN <Log File Identifier String> <(type)>.dat

where
„ YYYY is the year.
„ MM is the month.
„ DD is the day.
„ NNNN is the sequential file identifier.

25-2
 • • • • •
25 • SETTING UP DATA LOGGING

This number indicates the sequence files were created in. You can have up to 9999
file sets per day. At midnight, the sequence starts again at 0000.

25 • Placeholder
„ <Log File Identifier String> is a text string you can specify to help identify the log
file. The maximum string length is 20 characters.
„ <(type)> is the file type.
The type is enclosed in parentheses. There are three file types: Tagname, Float (for
analog and digital tag values), and String.

Example: Parts of a data log long file name

The data log file named
2006 10 30 0004 Oven Temperatures (Float).dat
was created October 30 2006:
„ 0004 indicates that this is the fourth file set created that day.
„ Oven Temperatures is the log file identifier string, which the user defined to help
identify the data.
„ (Float) indicates that this file contains analog or digital tag values.

ODBC database storage format

Use the ODBC database storage format to store data using an ODBC data source such as
Oracle or Microsoft SQL Server.
The ODBC format stores data in up to three tables:
„ Tag table (optional) stores tag names in an index so they can be referenced using a 2-
or 4-byte numeric field (rather than a 40-byte character field) in the float and string
tables.
„ Float table stores analog and digital tag values.
„ String table (optional) stores string tag values.
For details about the contents of the tables, see Appendix C in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

ODBC backup files are stored as binary files with the extension .obf. You cannot view the
contents of .obf files.

25-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

How ODBC tables are named

The ODBC tables are created with the default names TagTable, FloatTable, and
StringTable. In the Data Log Models editor, you can modify these names before creating
the tables, or you can specify the names of different tables.
If you specify a backup path for an ODBC model, FactoryTalk View names the backup
log files as described on page 25-2.

Creating data log models

In the Data Log Models editor, you create data log models that specify:
„ which log file format to use.
„ where to store data log file sets (primary or secondary paths).
„ when to create and delete log files.
„ which actions will trigger logging.
„ which tag values will be logged.

Set up general data

log model properties.

Specify paths the data

will be logged to.

Specify when log files

will be created
and deleted.

Specify how and when

logging should occur.

Select the tags you

want to log data for.

For details about options in the Data Log Models editor, click Help.

25-4
 • • • • •
25 • SETTING UP DATA LOGGING

To open the Data Log Models editor

1. In FactoryTalk View Studio, in the Explorer window, open the Data Log folder

25 • Placeholder
2. Right-click the Data Log Models icon, and then click New.
You can also open the Data Log Models editor by dragging its icon into the
FactoryTalk View Studio workspace, or by double-clicking an existing Data Log
Models component.

Specifying the storage format

In the Data Log Models editor, use the Setup tab to specify a log file identifier string,
storage format, and description for the data log model.
The log file identifier string becomes part of the file name. The description is for
information only.
If you select File Set as the storage format and you plan to log string tags, you can also
specify the number of characters to be logged.
For details about options in the Setup tab, click Help.

Selecting the ODBC database format

When you select ODBC database as the storage format, type the path and file name of the
ODBC data source, and specify the ODBC tables that will be used, or create new tables.
To create tables for a new data source, click Create Tables. If FactoryTalk View cannot
create the tables automatically, you will have to open the database using its editing tool,
and create the tables manually.
To select an existing table from the specified database, click the Browse button, and then
select a table in the Select ODBC Table dialog box. To view the order, type, length, and
precision of the fields in the table, click the table to select it and then click Details.
For more information, see “Logging data to an existing ODBC data source” on page 25-7.

Setting up log paths

In the Data Log Models editor, use the Paths tab to set up logging paths.
If the storage format is file sets, specify the primary path, and an optional secondary file
path in case the primary path becomes unavailable. If the storage format is ODBC, you
can specify a backup file path for the ODBC database.
Setting up a secondary or backup logging path prevents loss of data. For example, if the
disk space for the primary path becomes full, data logging will switch to the secondary

25-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

path, if available, until space becomes available on the primary path. For more
information, see “Switching log paths at run time” on page 25-9.
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.
For details about options in the Paths tab, click Help.

Setting up and managing data log files

In the Data Log Models editor, use the File Management tab to specify when to start new
files and when to delete old files.

Creating new file sets

If the data log model uses file sets, you can set up data logging to create new file sets:
„ periodically.
„ at specified times.
„ when a particular event occurs.
„ never. This means that all data will be logged to one file set.
Log files are saved in the folder you specify in the Paths tab.

If the data log model uses the ODBC format, data is added continually to the same database, so
this section does not apply.

Deleting file sets and ODBC database records

If a data log model uses file sets, you can set up file management to delete file sets after a
specified period or once a specified number of file sets has been created. To never delete
file sets, clear the check boxes under Delete Oldest Files.
Data log file sets are deleted only when a new file set is created. If the application creates
a new file set each day and deletes the oldest file set every third day, there will be file sets
for the three previous days’ data, as well as a file set for the current day.
If a data log model uses the ODBC database format, you can purge old records from the
database using standard relational database tools or SQL queries. You can also set up
FactoryTalk View to delete (purge) records in the ODBC database after a specified time.
For details about options in the File Management tab, click Help.

Specifying when to log data

In the Data Log Models editor, use the Log Triggers tab to specify what will trigger the
data to be logged, and when or how frequently this will occur.

25-6
 • • • • •
25 • SETTING UP DATA LOGGING

You can set up data logging to log tag values:

25 • Placeholder
„ periodically. This is called periodic logging.
„ only when a tag’s value changes. This is called on-change logging.
„ when a particular event occurs and triggers the DataLogSnapshot command. This is
called on-demand logging. For more information, see page 25-12.
You can also combine types of logging. For more information, see page 25-12.
For details about options in the Log Triggers tab, click Help.

Choosing the data to be logged

In the Data Log Models editor, use the Tags in Model tab to specify which tags will be
scanned for data. A data log model can contain up to 10,000 tags.
For details about options in the Tags in Model tab, click Help.

Logging data to ODBC data sources

You can store logged data in an existing ODBC data source, or you can create a new
ODBC data source.

Logging data to an existing ODBC data source

You can log data to an existing ODBC data source, but its tables must contain fields that
are formatted for the FactoryTalk View data log.
There are two ways to prepare tables for data logging to an existing database:
„ Set up the FactoryTalk View data log fields in the existing ODBC tables before
setting up a data log model.
„ Create new tables in the existing database automatically or manually, from within the
Data Log Models editor.

To use the tables in an existing ODBC data source

1. Add fields for the data log data to the tables in the ODBC database.
For information about:
„ the order and type of fields needed to log data to an ODBC database, see
Appendix C in Volume 1 of the FactoryTalk View Site Edition User’s Guide.
„ modifying the ODBC database tables, see the documentation for the ODBC
database you are using.

25-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

2. Set up a data log model, as described in Help. Specify the existing ODBC database as
the ODBC Data Source, and then specify the tables you edited.

To create new tables in an existing ODBC data source

1. Specify the name of the existing ODBC data source in the ODBC Data Source field
of the Data Log Models editor.
2. Click Create Tables. FactoryTalk View automatically creates new data log tables in
the existing database. You can also create tables manually.
3. Set up the rest of the data log model, as described in Help.

Creating a new ODBC data source

To create a new ODBC data source, use the ODBC Data Source Administrator in the
Windows® Control Panel. For details about using the tool, click Help in the ODBC Data
Source Administrator window.
You can create the tables for a new data source using either of the methods described in
“Logging data to an existing ODBC data source” on page 25-7.

Setting up security to log data to a remote computer

If you are logging data to an ODBC database that is not located on the computer where
the data is being generated, you must change certain DCOM security settings. For
details, see the FactoryTalk View Site Edition Help.

Creating new files at run time

To create new file sets or ODBC backup files at run time, use the FactoryTalk View
command DataLogNewFile.
If a data log model uses the ODBC format, and if FactoryTalk View is logging to the
backup path, running the DataLogNewFile command creates a new set of backup files.
If FactoryTalk View is logging to the ODBC database, an End Snapshot and then a Begin
Snapshot are logged when this command is run.
If a data log model uses file sets, DataLogNewFile creates a new file set regardless of how
the data log model is set up to start new files. The new file set is created in the same
location that FactoryTalk View is currently logging to.
DataLogNewFile records two snapshots of data: an End Record in the old file, and a
Begin Record in the new file. It is not necessary to use the DataLogSnapshot command in
this case.

25-8
 • • • • •
25 • SETTING UP DATA LOGGING

Using the DataLogNewFile command

25 • Placeholder
You can use the DataLogNewFile command with either of these parameters:
„ DataLogNewFile <component> (where <component> is a data log model name)
creates a new file set for the specified data log model.
„ DataLogNewFile * creates a new file set for all data log models that are currently
running.
You can use the DataLogNewFile command anywhere you can type a FactoryTalk View
command or macro.
To provide operators with a way to create new files at run time, create a button object in a
graphic display, or a display key or client key, that uses DataLogNewFile as the press
action.

Switching log paths at run time

FactoryTalk View lets you specify a secondary or backup path to be used in the event the
primary path for file sets, or the ODBC database, becomes unavailable. This could
happen due to a network failure, or lack of disk space on the computer where the data is
being logged.
If the primary data log location becomes unavailable, FactoryTalk View begins to store
the data in a buffer.
The buffer can hold up to 64 Kb of data. If the primary location is still unavailable when
the buffer fills, or when the maximum amount of time to buffer data has elapsed,
FactoryTalk View switches to the secondary path.
FactoryTalk View checks periodically to determine whether the primary file path has
become available again. Once it is available, FactoryTalk View switches back
automatically.
FactoryTalk View also checks the status of the primary path if the secondary path
becomes unavailable, and will switch back if possible. If both paths are unavailable,
FactoryTalk View buffers the data.
If the buffer fills and both paths are still unavailable, FactoryTalk View empties the buffer
(the data in the buffer is lost) and begins storing new data in the buffer. FactoryTalk View
continues checking both paths until one becomes available.

For data log models that use the file set format, FactoryTalk View creates a new file set each time
the logging path changes.

25-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Setting up switching options

In the Advance Configuration dialog box, you can specify the length of time data will be
buffered before switching to the secondary path, and when data logging will switch back
to the primary path.
For example, if the data log file is locked, data is buffered for the maximum time (in
minutes) you specify to buffer data before attempting a switchover. When the buffer time
elapses, a new set of files is created on the primary path.
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 set is created when the specified time
period has elapsed.
To open the Advance Configuration dialog box, in the Data Log Models editor, select the
Paths tab, and then click Advanced. For details about options in the Paths dialog box,
click Help.

If a 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 set is started immediately.

Switching back manually to the primary path

To switch back to the primary path or ODBC database manually, use the FactoryTalk
View command DataLogSwitchBack.
You can only use the command to switch back to the primary path or database. You cannot
use it to switch from the primary path or ODBC database to the secondary or backup path.
The switchback is performed only if the specified data log model is running, FactoryTalk
View is logging data to the secondary or backup path, and the primary path or ODBC
database is available.
For data log models that use file sets, FactoryTalk View creates a new set of files when it
switches back to the primary path.

To avoid affecting performance, FactoryTalk View does not move data from the secondary or
backup path automatically, when a switchback to the primary occurs. You must move the backup
data manually, using the DataLogMergeToPrimary command. For details, see “Moving data from
the secondary path” on page 25-11.

Using the DataLogSwitchBack command

You can use the DataLogSwitchBack command with either of these parameters:
„ DataLogSwitchBack <component> (where <component> is a data log model name)
switches logging for the specified data log model.

25-10
 • • • • •
25 • SETTING UP DATA LOGGING

„ DataLogSwitchBack * switches logging for all data log models that are currently
running.

25 • Placeholder
You can use the DataLogSwitchBack command anywhere you can type a FactoryTalk
View command or macro.
To provide operators with a way to switch manually to the primary path or ODBC
database at run time, create a button object in a graphic display, or a display key or client
key, that uses DataLogSwitchBack as the press action.

Moving data from the secondary path

When you begin writing to or reading from a data log model, FactoryTalk View sends a
message to the FactoryTalk Diagnostics log if there are files in the secondary (or backup)
path.
You must move these files manually to the primary path or ODBC database. To do this,
use the FactoryTalk View command DataLogMergeToPrimary.
If a data log model is running when the command is run, FactoryTalk View performs a
switchback to the primary path or ODBC database for the specified model, or all running
models.
If the model uses file sets, FactoryTalk View moves all files on the secondary path
(including the current file set) to the primary path, begins a new file set on the primary
path, and then continues logging to the new file set.
If the model uses the ODBC format, FactoryTalk View merges the data in the ODBC
backup files into the ODBC database, and then continues logging to the ODBC database.

Using the DataLogMergeToPrimary command

You can use the DataLogMergeToPrimary command with either of these parameters:
„ DataLogMergeToPrimary <component> (where <component> is a data log model
name) moves data for the specified data log model, whether or not the model is
running.
„ DataLogMergeToPrimary * moves data for all data log models whether or not they are
running.
You can use the DataLogMergetoPrimary command anywhere you can type a FactoryTalk
View command or macro.
To provide operators with a way to restore backup data to the primary path or ODBC
database at run time, create a button object in a graphic display, or a display key or client
key, that uses DataLogMergetoPrimary as the press action.

25-11
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Logging on demand
To record the values of tags in a data log model on demand, use the FactoryTalk View
command DataLogSnapshot. If you specified the On Demand trigger for the data log
model, logging will occur only when the DataLogsnapshot command is run.

Using the DataLogSnapshot command

You can use the DataLogSnapshot command with either of these parameters:
„ DataLogSnapshot <component> (where <component> is a data log model name)
records tag values for all tags in the specified model at the instant the command is run.
„ DataLogSnapshot * records tag values for all tags in all running models at the instant
the command is run.
You can use the DataLogSnapshot command anywhere you can type a FactoryTalk View
command or macro. For example, you can use the command as the action for an event (an
example of how to do this follows).
To provide operators with a way to log on demand at run time, create a button object in a
graphic display, or a display key or client key, that uses DataLogSnapshot as the press
action.

Example: Creating an event for on-demand logging

To create an event that will trigger logging when an alarm occurs:
1. In the Data Log Models editor, in the Log Triggers tab, select the option On Demand.
2. Open the Event editor. Create an expression such as:
If alm_in_alarm(motor_fault) and new_batch_started then 1 else 0
3. In the Event editor’s Action field, type DataLogSnapshot <component> where
‘component’ is the name of the data log model.
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).

Combining logging
You can combine periodic or on-change logging with on-demand logging. This allows
data to be captured at particular times, as well as when a particular event occurs.

25-12
 • • • • •
25 • SETTING UP DATA LOGGING

To combine logging
1. In the Data Log Models editor, in the Log Triggers tab, select the Periodic or On

25 • Placeholder
Change option.
2. Type the DataLogSnapshot command with the <component> or * (asterisk) parameter,
anywhere you can use a macro or command.

Modifying existing data log models

You can modify a data log model during development or at run time, using either
FactoryTalk View Studio or the FactoryTalk View SE Administration Console.
If you change a model at run time, the changes will not take effect until you stop and then
restart data logging. For information about starting and stopping data logging, see
page 25-14.

If a tag that you delete from a data log model is used in a trend object, be sure to remove all
references to the deleted tag from the trend.

Changing log paths in the SE Administration Console

To change the log paths for a data log model after deploying a FactoryTalk View SE
application, you can use the FactoryTalk View SE Administration Console (you don’t
need to use FactoryTalk View Studio).
You can change the primary and secondary paths for file sets, and the backup path for
ODBC data log models. You cannot use the Administration Console to change the
ODBC database.

Making run-time changes without modifying the model

At run time, you can also change the following data log parameters, without modifying
the data log model:
„ the log rate for periodic logging (use the DataLogChangeRate command)
„ the log file identifier string (use the DataLogRenameFile command)
Use these commands anywhere you can enter a FactoryTalk View command or macro.
For example, in FactoryTalk View Studio, or the FactoryTalk View SE Administration
Console, type the command directly at the command line.
These changes take effect immediately, but only apply to the current logging session.
When you stop and restart logging, FactoryTalk View uses the logging rate and log file
identifier specified for the data log model.

25-13
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

For details about the DataLogChangeRate and DataLogRenameFile commands, see the
FactoryTalk View Site Edition Help.

Starting and stopping data logging

There are many ways to start and stop data logging. Choose the way that works best for
the application.
To provide operators with a way to start and stop data logging, use FactoryTalk View
commands and macros in conjunction with graphic objects. For details about FactoryTalk
View command syntax, see the FactoryTalk View Site Edition Help.
In the following methods, <component> represents the name of a data log model.

Ways to start data logging

To start data logging, use one of these methods:
„ In the HMI Server Properties dialog box, click the Components tab, select the Data
Logging check box, and then specify a data log model.
The data log model will run the next time the HMI server runs, or when the HMI
server’s components are started manually.
„ In the Macros editor, create a macro that contains the command, DataLogOn
<component>. In the HMI Server Properties dialog box, click the Components tab,
select the Macro check box, and then specify the macro.
The specified data log model will run when the HMI server runs. To start more than
one data log model, specify multiple DataLogOn <component> commands in the
macro.
„ In the Graphics editor, open the Display Settings dialog box, and then click the
Behavior tab. In the Startup box, type DataLogOn <component>.
„ In the Graphics editor, create a button object and then specify DataLogOn
<component> as the button’s press action. When the button is pressed, the command
runs.
„ In the Graphics editor, create a graphic object and attach touch animation to it, using
DataLogOn <component> in the Action box. When the object is touched, data logging
starts for the specified model.
„ In the Events editor, type the DataLogOn <component> command in the Action box
for an event.
„ At the command line in FactoryTalk View Studio, or the FactoryTalk View SE
Administration Console, type DataLogOn <component> and then press Enter.

25-14
 • • • • •
25 • SETTING UP DATA LOGGING

Ways to stop data logging

25 • Placeholder
You can manually stop all the components that are running on the HMI server, including
data log models, event components, derived tag components, and alarm monitoring.
For details about stopping running components:
„ in network applications, see page 17-12, in Volume 1 of the FactoryTalk View Site
Edition User’s Guide.
„ in local applications, see page 18-5, in Volume 1 of the FactoryTalk View Site Edition
User’s Guide.
To stop data logging, use one of these methods:
„ Use the DataLogOff <component> command (where <component> is the name of the
data log model) to stop a single model. To stop all data log models, use the
DataLogOff * command.
„ In the Graphics editor, create a button object, and then specify DataLogOff
<component> or DataLogOff * as the button’s press action. When the button is
pressed, the command runs.
„ In the Graphics editor, create a graphic object and attach touch animation to it, using
DataLogOff <component> or DataLogOff * in the Action box. When the object is
touched, data logging is stopped for the specified model.
„ In the Events editor, specify DataLogOff <component> or DataLogOff * as the action
for an event.
„ At the command line in FactoryTalk View Studio, or the FactoryTalk View SE
Administration Console, type DataLogOff <component> or type DataLogOff * and
then press Enter.

25-15
26 Setting up trends

26 • Placeholder
This chapter describes:
„ what trends are.
„ how to create trends.
„ the parts of a trend.
„ trend chart styles.
„ choosing colors, fonts, lines, and legends for a trend.
„ using shading to compare pens.
„ using overlays to compare real-time and historical data.
„ using trend templates.
„ working with trends at run time.

About trends
A trend is a visual representation, or chart, of current or historical tag values. A trend
provides an operator with a way to track plant activity as it is happening.
In a trend, you can:
„ plot data for as many as 100 tags or expressions.
„ plot data over time, in a standard trend chart.
„ plot one tag against another, in an XY Plot chart.
„ use shading to emphasize a comparison between two pens.
„ display isolated or non-isolated graphs.
In an isolated graph, each pen is placed in a separate band of the chart. In a non-
isolated graph, pen values can overlap.

Charting current versus historical data

A trend can display:
„ real-time data from a data server.
„ historical data from a data log model’s set of files.

26-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

In a network application, you can plot historical data from data log models in local or
remote areas of the application. For more information about data log models, see
Chapter 25, Setting up data logging.

Creating trend objects

You can create a trend using the Trend drawing tool, or you can use the ready-made trend
chart in the Trend graphic library. For more information, see page 26-21.
The following illustration is of a FactoryTalk® View graphic display that contains two
different trend displays.

To create a trend object

1. In the Graphics editor, create a new graphic display, or open an existing one.

26-2
 • • • • •
26 • SETTING UP TRENDS

2. On the Objects menu, point to Advanced Objects, and then click Trend.

26 • Placeholder
You can also click the Trend tool on the Objects toolbar.
Trend tool
3. On the graphic display, drag the mouse to create a box approximately the size you
want the trend to be.

Providing a name for the trend

When you create a trend object, it is given a name by default. To change the name, right-
click the trend object, and then click Property Panel.
In the Properties tab, in the (Name) row, type the trend’s new name.
The name can contain letters, numbers, and the underscore character ( _) ; however, the
first character must be a letter, and the name cannot contain spaces.

Setting up trend properties

The Trend Properties dialog box contains several tabs in which you can set up the trend’s
data, appearance, and behavior:
„ In the General tab, set up the trend’s data server (real-time or historical polling),
chart title, chart style, and update mode.
„ In the Display tab, set up the appearance of the trend display.
„ In the Pens tab, set up pen tags and expressions, and the appearance of pens in the
trend.
„ In the X-Axis tab, set up the trend’s horizontal axis.
„ In the Y-Axis tab, set up the trend’s vertical axis.
„ In the Overlays tab, add or remove snapshots of historical data.
„ In the Template tab, set up properties for trend templates.
„ In the Runtime tab, set up ways to interact with the trend at run time.
„ In the Common tab, set up the trend’s size and position in the graphic display.
Once you have set up the trend, you can modify it as you would any other graphic object.
You can move it, resize it, attach animation to it, and so on.
You can also copy a trend object by dragging it from one graphic display to another.
For more information about working with graphic displays and objects, see Chapter 19,
Creating graphic displays, and Chapter 20, Creating graphic objects.

26-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To open the Trend Properties dialog box

„ Double-click the trend object.
You can also right-click the object, and then click Properties.

For details about options in the Trend Properties dialog box, click Help.

Testing a trend
In FactoryTalk View Studio, in the Graphics editor, you can use Test Display mode to test
a trend while you are setting it up.
If you have set up communications and there is data for the tags, the pens will plot values.
When you are finished testing, switch back to Edit Display mode to continue setting up
trend properties.

To switch between Test and Edit Display modes

„ In the Graphics editor, on the View menu, click Test Display or Edit Display.
You can also click the Test Display or Edit Display buttons on the toolbar.

26-4
 • • • • •
26 • SETTING UP TRENDS

The parts of a trend

26 • Placeholder
There are two trend chart styles—the standard chart, and the XY Plot chart.
The following illustration shows the parts of a standard trend chart with two pens and a
three-minute time span.

Chart title
Trend border

Pen with a
square symbol
Chart
pen marker

Pen icon
Y-axis

Y-axis legend
Pen without a
pen marker

X-axis

X-axis legend
Scrolling
mechanism
Line legend

Current value legend is displayed

as a column in the line legend.

Chart
The chart contains the plotted trend data. The chart is bounded by the y-axis on the left,
and the x-axis at the bottom.
Plotted data is shown using pen lines, pen markers, and grid lines.

Chart title
The chart title is the name you give to the trend chart. Naming the trend is optional.

26-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

X-axis
The x-axis is the bottom edge of the chart. It is also known as the horizontal axis, or the
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 associated with
the selected pen.
The number of timestamps or values shown depends on the size of the trend object and the
number of vertical grid lines.
At run time, you can double-click the x-axis legend, to open the X-Axis tab of the Trend
Properties dialog box. You can set up a trend to exclude the x-axis legend.

Y-axis
The y-axis is the left 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. The minimum and
maximum values for the scale can be:
„ determined automatically (using the best fit for the current data).
„ derived from a pen’s minimum and maximum values.
„ constant values.
„ controlled by tags.
All pens in the trend can use the same scale, or each pen can have 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.
For example, if Pen 1 has a minimum value of 10 and a maximum value of 100, the scale
on the vertical axis is 10 to 100 when the pen is selected.
If Pen 2 has a minimum of -10 and a maximum of 50, the scale on the vertical axis
changes to -10 to 50 when the operator selects the next pen in the line legend.
At run time, you can double-click the y-axis legend, to open the Y-Axis tab of the Trend
Properties dialog box. The legend can also be used to pan data. For more information, see
“Panning the trend chart” on page 26-27.
You can set up a trend to exclude the y-axis legend.

26-6
 • • • • •
26 • SETTING UP TRENDS

Pens

26 • Placeholder
Pens are the lines or symbols used to represent values on a trend chart. The values can be
tags you are monitoring, expressions that manipulate tag values, or constant values.
To make it easier for an operator to distinguish one pen from another, use different colors,
widths, and symbols (also called markers) for each pen.
For an example of how pen markers are used, see page 26-8.

Legends
There are four kinds of trend legends:
„ x-axis legend (described on page 26-6)
„ y-axis legend (described on page 26-6)
„ line legend
„ current value legend
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 is displayed on
the chart. When the position of the line legend is set to:
„ Left, the line legend is on the left side of the chart, and the current value legend is on
the right side.
„ Bottom, the current value legend is a column in the line legend.
For more information about the current value legend and the line legend, see page 26-14
and page 26-15.

Pen icons
Pen icons, if specified, are displayed at the right edge of the trend chart.
At run time, if a pen’s current value is within the scale shown on the vertical axis, the
pen’s icon is displayed.
The position of the icon 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.

26-7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Pen markers
Pen markers are symbols that indicate data points. A data point is the exact position of a
value plotted on a trend chart.
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.
„ to read pen values at run time.
The following illustration shows pen markers in a trend.

A ‘boxed’ pen
marker

An ‘Up triangle’ pen

marker

If data is plotted frequently, the markers might not display as distinct, separate symbols on the
trend chart.

26-8
 • • • • •
26 • SETTING UP TRENDS

Value Bar

26 • Placeholder
The value bar marks the value of each pen in a trend, at the selected position on the trend
chart, as shown in the following illustration.

The value of each pen

plotted on the trend
chart at this position

The value bar

You can position the value bar by clicking anywhere on the trend chart at run time.
If you position the value bar on a pen marker, it shows the value of the data point
represented by the pen marker.

Trend chart styles

There are two trend chart styles—the standard chart, and the XY Plot chart.
You can set up the chart styles for a trend object in the General tab of the Trend Properties
dialog box. For details about options in the General tab, click Help.

26-9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

The Standard chart style

A standard chart plots tag values against time, as shown in the following illustration.

In a standard chart,
the y-axis shows
pen values …

… and the y-axis

legend shows time
values.

The XY Plot chart style

An XY Plot chart plots the values of one or more tags against another tag.
Use the XY Plot chart to plot one (or more) 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.
In the following illustration, the y-axis pen’s data is plotted as a diagonal line on the trend
chart. The x-axis legend displays the scale for the x-axis pen. The time period covered by
the chart is at the upper left.

26-10
 • • • • •
26 • SETTING UP TRENDS

26 • Placeholder
In an XY Plot, the
y-axis shows pen
values …

… and the x-axis

legend shows pen
values.

Isolated graphing
For charts with multiple pens, you can allow the pen values to overlap, or you can isolate
each pen in its own horizontal band on the chart.
Use isolated graphing to view each pen individually on the trend chart.
The band is the area of the trend chart used by an isolated pen. Use the isolated graphing
percentage to specify the space between each pen band.
With isolated graphing, a grid line is placed automatically above each pen’s band.
The following illustration shows isolated graphing, with 0% isolation between each pen’s
band.

In the illustration, each pen has its own scale. Another option is to use the same scale for all
pens in the trend.

26-11
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Plotting a value across the full width of the chart

Use horizontal lines on a trend chart to provide an orientation for your tag data.
For example, you can define upper and lower limits for a tag’s value, and then show the
limits as horizontal lines in the trend. When the value crosses one of the limits, the tag’s
condition is obvious on the trend.
The vertical position the pen in the trend depends on value of the tag, expression, or
constant used to define the pen. If the value changes, the position of the horizontal line
also changes.

To plot a constant value across the chart’s full width

1. In the Trend Properties dialog box, click the Pens tab.
2. Add a pen with a constant value.
When values for the pen are plotted across the full width of the chart, the pen shows as a
solid horizontal line.

To plot a tag or expression across the chart’s full width

1. In the Trend Properties dialog box, click the Pens tab.
2. Add a pen with a tag or expression that will determine the position of the pen line.

26-12
 • • • • •
26 • SETTING UP TRENDS

3. In the Pen Attributes spreadsheet, in the Type column, select Full Width.

26 • Placeholder
When the trend runs, the pen shows as a solid horizontal line across the full width of the
chart.

Choosing trend colors, fonts, lines, and legends

In the Trend Properties dialog box, you can set up colors, fonts, lines, and markers for a
trend chart and pens.

To set up this attribute In this tab Click this box, button, or list
Chart background color Display Background color
Text color for the x-axis legend Display Text color
Text font, style, and size Display Font
Pen line, pen marker, pen icon, and Pens Color
text color for the y-axis legend
Pen line width Pens Width
Pen line style Pens Style
Pen marker Pens Marker
Color of vertical lines in the grid X-Axis Grid color
Color of horizontal lines in the grid Y-Axis Grid color

You can also set up these attributes in the Property Panel. To open the Property Panel,
right-click the trend object, and then click Property Panel.

Changing the trend highlight color

The chart title, y-axis legend, x-axis legend, and line legend can have a highlight box at
run time.
Whether these parts of the trend are highlighted, and in what color, is determined by
settings for the graphic display that contains the trend. For more information about display
settings, see “Setting up the appearance and behavior of a graphic display” on page 19-35.

Changing the trend object background

The space behind and around the trend chart and legends is the background of the trend
object (shown in the following illustration).

26-13
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

The shaded area is

the background of
the trend object.

You can change the color and style settings for the background using the WindowStyle
and WindowColor options in the Property Panel. For details about using the Property
Panel, see page 19-5.

Displaying a current value legend

The current value legend can be displayed by itself or as part of the line legend, depending
on the position of the line legend.
When the line legend is displayed to the left of the trend chart, the current value legend is
displayed to the right of the trend, as shown in the following illustration.

Current time
Current pen value
Pen icon
Pen line color

26-14
 • • • • •
26 • SETTING UP TRENDS

When the line legend is displayed at the bottom of the trend chart, the current value legend
is displayed as a column in the line legend, as shown in the following illustration.

26 • Placeholder
Pen caption Current value Min/max values Engineering
legend units

Displaying a line legend

The line legend shows the details of a pen line, including the line color, pen name, the
minimum and maximum values, and the engineering units.
The line legend’s appearance differs depending on where it is located relative to the trend
chart. The previous illustration shows the line legend as it appears at the bottom of the
trend.
The following illustration shows the line legend as it appears to the left of the trend:

Pen caption

Engineering units Min/max values

Using shading to compare pens

To compare the values of two or more pens in a trend, use shading in the trend.
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.
If Pen 2 is the upper boundary for Pen 1, the shading will indicate when the tag’s value
exceeds the threshold, by filling in the area between the two pens with the line color for
Pen 1.
At least two pens must be set up for a trend, before you can use shading.
Set up shading in the Pens tab in the Trend Properties dialog box. For details about
options in the Pens tab, click Help.

Shading is determined by the position of lines on the trend chart—not by the actual tag values.

26-15
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

The trend in the following illustration uses shading to indicate tag values in alarm. The
difference between the tag’s value and the tag’s alarm level is shaded.

Shading between pen

values

Upper-bound pen

Lower-bound pen

Example 1: Shading with three pens

The upper pen, Pen 2, has a constant value of 75 and the lower pen, Pen 3, has a constant
value of 25.
Pen 1 represents the tag called VIN_LEVEL. The trend is shaded whenever Pen 1 goes
above Pen 2 or below Pen 3. A plot for this trend looks like this:

Pen 1

Pen 2

Pen 3

26-16
 • • • • •
26 • SETTING UP TRENDS

To produce the shading shown in the illustration, use the following settings:

26 • Placeholder
Shading
Tag name or
Pen constant value Upper Bound Lower Bound
Pen 1 VIN_LEVEL Pen 2 Pen 3
Pen 2 75
Pen 3 25

Example 2: Shading with two pens

Whenever Pen 1 goes above Pen 2, the trend is shaded like this:

Pen 1

Color 1

Pen 2

To produce the shading shown in the illustration, use the following settings:

Shading
Tag name or
Pen constant value Upper Bound Lower Bound
Pen 1 VIN_LEVEL Pen 2
Pen 2 OIL_LEVEL

26-17
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Example 3: Shading between two pens

Whenever Pen 1 goes above or below Pen 2, the trend is shaded like this:

Pen 1

Color 1

Pen 2

To produce the shading shown in the illustration, use the following settings:

Shading
Tag name or Constant
Pen value Upper Bound Lower Bound
Pen 1 VIN_LEVEL Pen 2 Pen 2
Pen 2 OIL_LEVEL

Using overlays to compare real-time and historical data

You can layer a trend with a snapshot of previously charted data. This is called an overlay.
Use overlays to compare current charted data to a historical snapshot. For example, you
might set up overlays to compare data for a particular shift or batch process.

Setting up snapshots and overlays

To create an overlay, create the data snapshot first, and then add the snapshot as an
overlay, to the trend charting current data.
When you add a snapshot to a trend as an overlay, the pens from the snapshot are added
automatically to the Pens tab in the Trend Properties dialog box. You can change the
attributes of pens used in overlays, just as you can change the attributes of regular pens.
An operator can show or hide overlays on the trend chart at run time, using the trend’s
shortcut menu. For more information, see page 26-28.

26-18
 • • • • •
26 • SETTING UP TRENDS

For information about setting up the trend’s run-time options, click Help in the Runtime
tab of the Trend Properties dialog box.

26 • Placeholder
To create a snapshot
1. Right-click the trend you want to get a data snapshot from, and then click Create
Snapshot.
2. In the Component Name dialog box, type a name for the snapshot, and then click OK.

To add a snapshot to the trend as an overlay

1. In FactoryTalk View Studio, open the graphic display containing the trend that will
chart current data.
2. Double-click the trend. The Trend Properties dialog box opens.
3. In the Overlays tab, click Add.
4. In the Component browser, find and select the snapshot you want to add, and then
click OK.
The following illustration is of a trend overlay.

Overlay time

Overlay pen

Currently plotting pen

Currently plotting pen

Overlay pen

26-19
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Using trend templates

You can use a trend template to:
„ apply a consistent appearance to trend charts.
„ create a set of different views for the same data.
„ return to a standard display after experimenting with display options.
„ save pen attribute data.
Use the Trend Properties dialog box to create a trend template. For details about options in
the dialog box, click Help.

Applying a consistent appearance to trend charts

Create a trend template to standardize a trend chart for all your applications.
Use a standard template when you have several different applications, and you need the
trend chart to work the same way in each application.
When you have created and saved the template, load the template into each application’s
trend chart.

Creating a set of different views for the same data

To assess the same data in different ways, create trend templates that provide different
views of the data.
Load the trend templates at run time, to change the appearance of the trend

Returning to a standard display

Create a trend template to use as a standard trend display.
Load the standard display template after an operator changes the trend chart settings, and
you want to return to the standard trend chart.

Saving pen attribute data

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. The next time you run the trend, if you want the same pen
attribute data, you can load the template.

26-20
 • • • • •
26 • SETTING UP TRENDS

Loading trend templates

26 • Placeholder
Load a template to return to the original trend settings, or to apply a consistent trend
appearance across applications.

To load a template
1. In the Trend Properties dialog box, click the Template tab, and then click Load
template.
2. In the Component browser, find and select the template you want to load, and then
click OK.

Saving, loading, or deleting a template takes effect immediately, and cannot be undone. If you
load a template at run time, any existing pens in the trend are deleted and replaced with the pens
in the template.

Example: Using the Invoke command to load trend templates at

run time
A trend template named Isolated uses isolated graphing, and a template named Non-
isolated uses non-isolated graphing.
To provide an operator with a way to switch between the two templates at run time, do the
following in the trend’s graphic display:
1. For the isolated graphing template, create a button that runs the following command as
its press action:
Invoke Me.Trend1.LoadTemplate (“Isolated”)

2. For the non-isolated graphing template, create a button that runs the following
command as its press action:
Invoke Me.Trend1.LoadTemplate (“Non-Isolated”)

To load the templates at run time, the operator can press either button.

In the Invoke commands in this example, Trend1 is the default name of the trend object. Be sure
to use the correct name of the trend in the Invoke command.

About the Trend graphic library

The Trend graphic library contains a real-time trend, and objects for controlling the trend.
You can use the trend and objects as they are, or you can modify them to suit your needs.
To use the objects, drag and drop them into a graphic display.
26-21
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To open the Trend graphic library

1. In FactoryTalk View Studio, in the Explorer window, open the Graphics folder.
2. In the Libraries folder, right-click Trend, and then click Open.

Working with trends at run time

How you can interact with a trend at run time depends on the options you set up in the
Runtime tab of the Trend Properties dialog box.
You might be able to do some or all of the following:
„ View and modify trend properties.
„ Modify legend properties.
„ Pan or zoom on the trend chart.
„ Use the trend chart’s shortcut menu.
For details about options in the Runtime tab, click Help.

Collecting data in the background at run time

Real-time trends collect data only while the trend is displayed. This means that a real-time
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 entire time the application is
running, or if other graphic displays are opened before the trend display.
If you want a trend to contain data when the graphic display opens, you can use a data log
model, or you can run startup macro, to load and update the display in the background.
This loads data into the data buffer for the trend.

You can run a startup macro when the HMI server runs. For information about setting up startup
components for an HMI server in a network and a local application, see Chapters 6 and 7
respectively, in Volume 1 of the FactoryTalk View Site Edition User’s Guide.

Example: Using a startup macro to load and update a trend in the

background
1. Create a startup macro that includes this command:
Display Trend1 /ZA

where Trend1 is the name of the graphic display containing the real-time trend, and
/ZA is the parameter for loading the trend data into the data buffer.

26-22
 • • • • •
26 • SETTING UP TRENDS

Trend data will remain in the cache, and continue to update, until you run the
FlushCache command, or until you stop running the application.

26 • Placeholder
2. When you want the real-time trend to become visible, run the following command:
Display Trend1

When the graphic display opens, the trend will contain data.

Selecting pens at run time

To display details about a pen, select the pen by clicking it in the line legend. When a pen
is selected, the vertical scale changes to reflect the scale of values for the pen.

The y-axis legend shows

the minimum and
maximum scale for a pen
…

… when you click the pen

line in the line legend.

Modifying trend properties at run time

Changes made to trend properties at run time are not saved.
The changes affect the trend that is running, but as soon as the graphic display is changed
or closed, the changes to the trend are lost.
To make permanent changes to a trend, open and modify it in FactoryTalk View Studio.

26-23
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To open the Trend Properties dialog box at run time

„ Right-click the trend chart, and then click Chart properties.

At run time, the Trend Properties dialog box shows only the tabs specified in the Runtime tab,
when you set up the trend. You can make changes only in the available tabs. The Runtime tab
itself, is not available at run time.

To change the trend chart title

1. Double-click the trend chart title.
2. In the Graph title dialog box, type a name for the trend chart, and then click OK.

To open the Y-Axis tab

1. Double-click the y-axis legend.
2. In the Y-Axis tab, make the desired changes, and then click OK.

To open the X-Axis tab

1. Double-click the x-axis legend.
2. In the X-Axis tab, make the desired changes, and then click OK.

To open the Pens tab

1. Double-click the line legend.
2. In the Pens tab, make the desired changes, and then click OK.

Scrolling the trend chart at run time

To view different areas of charted data, an operator can use the set of VCR-style buttons
included with a trend. The following illustration describes the function of each button.

Oldest Backward Backward Pause Forward Forward Most

data 1 time ½ time ½ time 1 time recent
span span span span data

26-24
 • • • • •
26 • SETTING UP TRENDS

To make the VCR-style buttons available at run time, in the Display tab of the Trend
Properties dialog box, select the check box, Display scrolling mechanism.

26 • Placeholder
You can also use the buttons in the Trend graphic library. For information about the
library, see page 26-21.

Displaying the value of pens at various positions

The value bar displays the value of each pen in the trend, at the position you select on the
trend chart.

Pen values

The value bar

The color of the value bar changes automatically, so it is visible for all background colors.
For example, if the trend background color is black, the value bar color will be white. If
the trend background color is white, the value bar will be black.
A tilde ( ~) indicates an approximate value. An approximate values is displayed when
there is no value for the pen at the exact time stamp of the value bar. The approximate
value is based on the nearest available reading.

To show the value bar

„ Click the trend where you want the value bar to appear.

To hide the value bar

„ Click the trend’s vertical axis.

26-25
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

You can also right-click the trend, and then click Show value bar. A check mark
indicates the value bar is visible. No check mark indicates the value bar is hidden.

Displaying the difference in pen values for two points

The delta value bar works with the value bar to show the difference in value between two
x-axis points for standard and XY Plot chart types.

The value bar

The value of the

data point at the
value bar’s
position

The delta value

bar

The difference
between the
value bar’s data
point and the
delta value bar’s
data point

To show the delta value bar

1. Right-click the trend chart, select Active value bar, and then click Value.
2. Click the trend where you want the value bar to appear.
3. On the shortcut menu, click Active value bar, and then click Delta.
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.

To move the delta value bar

1. Right-click the trend, select Active value bar, and then click Delta.
2. Click the trend chart at the position where you want to know the difference between
the value indicated by the value bar, and the value indicated by the delta value bar.

26-26
 • • • • •
26 • SETTING UP TRENDS

To remove the delta value bar

Right-click the trend, and then click Show value bar.

26 • Placeholder
„

This removes both the value bar and the delta value bar from the trend. However, if
you click Show value bar again, only the value bar will reappear.

Zooming the trend chart

Use zoom to view a selected area of the trend chart in more detail.
To zoom, use one of these methods:
„ Right-click and drag the y-axis to zoom vertically.
„ Right-click and drag the x-axis to zoom horizontally.
„ Left-click and drag the chart to zoom into the selected area.

To restore the original trend chart view

„ Right-click the trend chart, and then click Undo Zoom/Pan.

Panning the trend chart

Use pan to view areas of the trend chart that are outside the area of the chart you are
viewing. You must pause the trend before you can pan to an area.

To pause the trend

„ Click the VCR-style pause button at the bottom of the trend.
To pause the trend, you can also right-click the trend chart, and then click Scroll.

To pan vertically
„ Click and then drag the y-axis legend.

To pan horizontally
„ Click and then drag the x-axis legend.

To restore the original trend chart view

„ Right-click the trend chart, and then click Undo Zoom/Pan.

26-27
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Using the arrow keys

You can use the arrow keys on the keyboard to perform some of the same functions as the
mouse and VCR-style buttons.

Press and hold And then press

To do this this key this arrow key
Move back half a time span. (none) Left
Move forward half a time span. (none) Right
Pan up 10%. (none) Up
Pan down 10%. (none) Down
Move back a full time span. Shift Left
Move forward a full time span. Shift Right
Switch to the next pen’s y-axis. Shift Up or Down
Move the value bar to the next data Ctrl Left or Right
point.
Pan up or down 10%. Ctrl Up or Down
Pause. Shift and Ctrl Left or Right
Switch to the next pen’s y-axis. Shift and Ctrl Up or Down

Printing the trend chart

To print the trend chart
1. Right-click the trend, and then click Print Trend.

Using overlays at run time

Before you can use overlays at run time, a snapshot must be created and the overlay must
be set up in the Overlays tab. For more information about snapshots and overlays, see
“Setting up snapshots and overlays” on page 26-18.

To align an overlay to the left of the trend chart

„ Right-click the trend chart, select Overlays, Align Left, and then click the name of the
overlay to align to the left of the trend chart.

To relocate an overlay
„ Right-click the trend chart, select Overlays, Relocate, and then click the name of the
overlay to relocate.

26-28
 • • • • •
26 • SETTING UP TRENDS

To show or hide an overlay

1. Right-click the trend chart, select Overlays, click Show/Hide, and then click the name

26 • Placeholder
of the overlay you want to show or hide.
A check mark beside the overlay name indicates it is visible on the trend chart. No
check mark beside the overlay name indicates it is hidden.

To open the Overlays tab

1. Right-click the trend chart, select Overlays, and then click Properties.

Fixing run-time errors

If data for the trend is not available at run time due to communication errors, messages are
sent to the Diagnostics List.
For information about setting up FactoryTalk Diagnostics, see Chapter 15 in Volume 1 of
the FactoryTalk View Site Edition User’s Guide.
For information about troubleshooting common trend problems, see Help.

To view information in the Diagnostics List

„ In FactoryTalk View Studio, on the Tools menu, click Diagnostics Viewer.
You can also open the Diagnostics Viewer from the Windows® Start menu: select
Programs, Rockwell Software, FactoryTalk Tools, and then click Diagnostics Viewer.

26-29
27 Creating macros

27 • Placeholder
This chapter describes:
„ what macros are.
„ macro syntax.
„ running macros.

About macros
A macro is a series of commands stored in a macro component.
You can use a macro component like a command, anywhere a command can be used.
When the component name is issued, the macro runs, carrying out all the commands in the
component.
You can create macros to perform almost any action, or series of actions. For example, a
macro can:
„ open a group of graphic displays, and define their initial positions.
„ define temporary key definitions.
„ close any open graphic displays.
„ set tag values.

To create a new macro

„ In FactoryTalk® View Studio, open the Logic and Control folder, right-click the
Macros icon, and then click New.
For details about using the Macros editor, see the FactoryTalk View Site Edition Help.

Macro syntax
When typing commands in macros, follow these guidelines:
„ Separate each identifier, specification, or string with a space or a tab.
„ Start each command on a new line, or separate commands on the same line with a
semicolon (;).
„ To insert a comment, type an exclamation mark (!) at the beginning of a new line or
immediately after a semicolon (;).

27-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Everything between the exclamation mark and the end of the line, or the next
semicolon, is treated as a comment.
„ To replace a tag name with its current value when a command is evaluated, enclose the
tag name in dollar signs ($) to create a placeholder in the command.
When a macro containing $tag$ runs, current tag values are substituted for the
placeholders, when the macro first opens for execution.
„ To indicate percent in a macro, use two percent signs (%%). A single percent sign
indicates a parameter. For more information, see “Specifying parameters in a macro”
on page 27-3.

Do not use dollar signs or percent signs in comments inserted in macros. This causes errors
at run time.

For assistance while typing commands in macros, double-click anywhere in the Macros
editor to open the Command Wizard.
For information about command syntax and how to use the wizard, see Appendix A in
Volume 1 of the FactoryTalk View Site Edition User’s Guide.

Example 1: A macro called Factory

A macro called Factory contains the following commands:
Display /Ingredients::Overview
Display /Ingredients::Detail
/Ingredients::Valve23=Open

When the macro runs, the graphic display called Overview opens, then the display called
Detail opens, and then the tag Valve23 is set to its open state. The displays and the tag all
are located in the area called Ingredients.

Example 2: A macro using placeholders in commands

The first two entries in this macro are Display commands that use placeholders:
Display /$Tag1$::Process1
Display /$Tag1$::TrendDisplay$Tag2$
Valve23=Open

27-2
 • • • • •
27 • CREATING MACROS

When the macro runs, FactoryTalk View replaces the placeholders ($Tag1$, $Tag2$) with
the current values of the specified tags.

27 • Placeholder
For example, if Tag1 (a string tag) = Mixing and Tag2 (an analog tag) = 2, then the graphic
display Process1 from the Mixing area opens, followed by the display TrendDisplay2,
also from the Mixing area.
Finally, the tag Valve23 from the home area is set to its open state. In this example, the
home area is also the area in which the macro is run.
You don’t need to put brackets around tag names when using placeholders in commands.

Specifying parameters in a macro

Macros can accept parameters. To specify a parameter in a macro, type a percent (%) sign
followed by a number. Up to nine parameters are allowed.
To run the macro and parameters, specify the macro name followed by the parameters.
Separate multiple parameters with spaces.

Example 3: Factory macro with two parameters

Re-create the Factory macro described in Example 1, as follows:
Display Overview
Display %1
Valve23=%2

To run the macro, type the macro name with the parameters to substitute for the
placeholders %1 and %2:
Factory Detail Open

When the macro runs, it substitutes “Detail” wherever %1 occurs in the macro, and
substitutes “Open” wherever %2 occurs in the macro.
The actions performed are the same as in Example 1. However, in this example the macro
runs in the home area instead of the Ingredients area.

Typing macro names that contain spaces

If the name of a macro contains spaces, enclose the name in quotation marks when typing
the macro name.

27-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

If the macro contains parameters, place the parameters outside the quotation marks.

Example 4: Macro name with spaces and parameters

The name of the macro in Example 3 is Factory Display, instead of Factory. To run the
macro, type the following at the command line:
“Factory Display” Detail Open

Nesting macros
You can insert a macro within another macro—this is called nesting. A macro can have up
to eight nesting levels.

The single quotation mark ( ‘ ) is a special character in FactoryTalk View and cannot be used in
nested macros. Instead, use the double quotation mark ( “ ) .

Example 5: Nesting macros

A macro called Draw contains:
Display Overview
Display Detail

and a macro called Factory contains:

Draw
Valve23=Open

With the Draw macro nested in the Factory macro, running the Factory macro performs
the same actions as in Example 3.

Running macros
At run time, an operator can run a macro anywhere they can run a FactoryTalk View
command. Ensure you include a way for the operator to run commands or macros, for
example, by specifying them as press actions for buttons.
For more information about running macros, see Help.

27-4
 • • • • •
27 • CREATING MACROS

Specifying a macro to run when an HMI server starts

27 • Placeholder
If you have created an HMI server with components that must start in a particular order,
create a Startup macro. To make this macro run when the HMI server starts, select it as
the startup macro in the Components tab of the HMI Server Properties dialog box.
For details about specifying the startup macro:
„ in network applications, see page 6-17, in Volume 1 of the FactoryTalk View Site
Edition User’s Guide.
„ in local applications, see page 7-8, in Volume 1 of the FactoryTalk View Site Edition
User’s Guide.

Specifying user login and logout macros

You can assign login and logout macros to any user or group of users listed in the Runtime
Security editor, in FactoryTalk View Studio. Any macro component, containing any
FactoryTalk View command, can be a login or logout macro.
For example, a login macro might contain a command to bring up a specific graphic
display in an area of the plant. A logout macro might contain commands to redefine
sensitive keys.
A user’s login macro runs when the user logs on to the FactoryTalk View SE Client.
If the client is already running when the user logs on, the current user is logged off. If the
current user is assigned a logout macro, the logout macro runs once the new user’s name
and password are accepted.
In a network application, a login or logout macro will only run in the area where it’s
located.
For example, if you specify a login macro located in the Bottling area, when the user logs
on to the a FactoryTalk View SE Client, the macro will run only if the Bottling area is the
client’s home area.

You specify the client’s home area when you select components for the client configuration file.
For more information, click Help in the FactoryTalk View SE Client wizard.

For more information about logging on and off at run time, and about assigning login and
logout macros to users, see Chapter 5, “Setting up security,” in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

27-5
28 Using derived tags

28 • Placeholder
This chapter describes:
„ what derived tags are and how to use them.
„ setting up derived tags.
„ creating a derived tags component.
„ starting and stopping derived tags processing.

About derived tags

A derived tag is a tag whose value is the result of an expression. An expression can be
simply a tag name, or it can be an equation made up of tag names, mathematical and
logical operations, special functions, and If-Then-Else logic.
Derived tag calculations are carried out at the FactoryTalk View SE Server (also called the
HMI server).
A derived tags component is a file that contains the definitions of one or more derived
tags. A derived tags component can be run when an HMI server starts, or it can be run
using the DerivedOn command, after the HMI server has started.

How to use derived tags

Here’s an example of how a derived tag can be used. Suppose there are five weight
sensors on a conveyor belt. The tag database contains one tag for each sensor, so the
weight at each point on the conveyor belt is monitored.
If the weight at any point is excessive, FactoryTalk® View triggers an alarm. However, if
no individual sensor detects an excessive weight, but the total of all five sensors is too
high, an alarm might be triggered.
To handle this case, you could set up a derived tag to sum the weights of all five sensors.
Then, if this total, which would be the value of the derived tag, is too high, FactoryTalk
View can trigger an alarm.

Writing to a tag whose value is the result of a derived tag expression is not recommended,
because a derived tag is re-evaluated whenever tags in the expression change.
For example, if a derived tag named Tag3 is defined by the expression Tag1 + Tag2, you can set
Tag3 to 0; however, the value of Tag3 will change again, when either Tag1 or Tag2 changes.

28-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Parts of the Derived Tags editor

Use the Derived Tags editor to create derived tag components for an application.

To open the Derived Tags editor

1. In FactoryTalk View Studio, in the Explorer window, open the Logic and Control
folder.
2. Right-click the Derived Tags icon, and then click New.
You can also open the Derived Tags editor by dragging its icon into the FactoryTalk
View Studio workspace, or by double-clicking an existing Derived Tags component.

Form

Spreadsheet

28-2
 • • • • •
28 • USING DERIVED TAGS

Accept and Discard buttons

28 • Placeholder
When you enter information in the Derived Tags editor, the Prev and Next buttons change
to Accept and Discard buttons.
Click Accept to save derived tags information. Click Discard to cancel changes to the
derived tags file.

Form and spreadsheet

In the upper part of the form, provide a name and description for the derived tag.
In the Expression box, create the expression that will determine the derived tag’s value.
You can use the buttons beneath the box to build expressions. For more information, see
Chapter 23, Creating expressions.

Checking the syntax of an expression

In the Derived Tags editor, to verify that the expression you typed uses correct syntax,
click Check Syntax. If the syntax is invalid, an error is displayed in the Check Syntax box.
You can check the syntax of an expression at any time while the Derived Tags editor is
open. The syntax is also checked automatically, when you click Accept or OK in the
editor.

Creating a derived tags component

You can use any tag to store the result of a derived tag calculation. The tag must already
exist, for example, as an HMI tag (memory or device) or in a data server, before you can
use it as a derived tag.

Do not create derived tags that depend on the results of other derived tags.
Derived tags processing is not sequential. This means the results of an expression that includes
other derived tags might not occur in the desired scan or order of evaluation. To avoid this, it is
best to put all the required logic in the expression.

These are the tasks involved in setting up derived tags for an application:
1. Create the derived tags in the Derived Tags editor in FactoryTalk View Studio.
2. Set the maximum update rate in the Derived Tag Setup dialog box.
3. Save the derived tags component and give it a name.

28-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

To create a derived tags component

1. In the Derived Tags editor, specify the tag that will hold the derived value and type a
description of the tag.
2. In the Expression box, create an expression that will determine the derived tag’s value.
For information about expressions, see Chapter 23, Creating expressions.
3. Click Accept.
4. Click Next to create another derived tag if the derived tags component is to contain
more than one derived tag.
5. Repeat steps 1 through 4 until all derived tags for the particular component are
defined.
6. On the Setup menu, click Derived Tag Setup.
7. In the Derived Tag Setup dialog box type a description of the component and specify a
maximum update rate, and then click OK.
8. In the Derived Tags editor, click Close.
9. Specify the name of the derived tags component and then click OK.
For details about options in the Derived Tags editor and in the Setup dialog box, click
Help.

About the maximum update rate

The maximum update rate is the fastest rate at which the value of any derived tag in a
derived tag component can be updated.
The maximum update rate also determines the fastest rate at which data servers can send
changes in tag values.
Set a maximum update rate separately, for each derived tag component you create.
Set the update rate as fast as, or faster than, the rate at which the values of tags used in the
derived tags component change, unless it is desirable to miss changes in tag values.

Expressions containing derived tags are evaluated only when the value of a tag or function in the
expression changes.

Using multiple derived tag components

You can create multiple derived tag components, for example, to group derived tags that
need to be evaluated at different rates.

28-4
 • • • • •
28 • USING DERIVED TAGS

Each HMI server in an network application can run up to 20 derived tag components, with
up to 1,000 tags in each component.

28 • Placeholder
Modifying existing derived tag components
You can modify derived tags during development or when you run the application.
If you change an derived tags component at run time, the changes will not take effect until
you stop and then restart derived tags processing. For information about starting and
stopping derived tags, see page 28-5.

Starting and stopping derived tags processing

There are many ways to start and stop derived tags processing. Choose the way that works
best for the application.
To provide an operator with a way start and stop derived tags processing, use FactoryTalk
View commands and macros in conjunction with graphic objects. For details about
FactoryTalk View command syntax, see the FactoryTalk View Site Edition Help.
In the following methods, <component> represents the name of a derived tags file.

Using clients to start and stop derived tags processing is not recommended, as one client might
stop processing a derived tags component that another client is using.

Ways to start derived tags processing

For network applications, it is best to start derived tags processing using a server
component such as the startup macro, or using event processing.

Network and local applications

„ In HMI Server Properties dialog box, click the Components tab, select the check box,
Derived tags, and then select a derived tag component.
The derived tag component will start the next time the HMI server runs, or when the
HMI server’s components are started manually.
„ In the Macros editor, create a macro that contains the command, DerivedOn
<component>. In the HMI Server Properties dialog box, click the Components tab,
select the Macro check box, and then specify the macro. Derived tags processing will
start when the HMI server runs.
„ In the Events editor, specify the DerivedOn <component> command as the action for
an event.
„ At the command line in FactoryTalk View Studio, or the FactoryTalk View SE
Administration Console, type DerivedOn <component> and then press Enter.

28-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Local applications only

The following methods are not recommended for network applications, as they use clients
rather than servers to start derived tags processing:
„ In the Graphics editor, create a button and then specify the DerivedOn <component>
command as the button’s press action. When the button is pressed, derived tags
processing starts.
„ In the Graphics editor, create a graphic object and then attach touch animation with
the DerivedOn <component> command as the object’s action. When the object is
touched, derived tags processing starts.
„ For the Login Macro in the FactoryTalk View SE User Accounts editor, specify the
DerivedOn <component> command, or a macro that contains the command.
„ For the Startup command in the Display Settings Behavior tab, specify the DerivedOn
<component> command, or a macro that contains the command.

Ways to stop derived tags processing

Having multiple clients stop derived tags processing is not recommended. Do this in
special cases only, for example, for application maintenance.

Network and local applications

„ To shut down all the components that are running on the HMI server, including all
derived tag components, stop the components running on the HMI server manually.
For details about stopping an HMI server’s components manually in network
applications, see page 17-12, and in local applications, see page 18-5, in Volume 1 of
the FactoryTalk View Site Edition User’s Guide.
„ To stop a single derived tag component, use one of these methods:
„ In the Macros editor, create a macro that contains the command, DerivedOff
<component>. In the HMI Server Properties dialog box, click the Components tab,
select the check box, On shutdown macro, and then specify the macro.
Derived tags processing will stop when the HMI server shuts down.
„ In the Events editor, specify the DerivedOff <component> command as the action
for an event.
„ At the command line in FactoryTalk View Studio, or the FactoryTalk View SE
Administration Console, type DerivedOff <component> and then press Enter.

28-6
 • • • • •
28 • USING DERIVED TAGS

Local applications only (single components)

The following methods are not recommended for network applications, as they use clients

28 • Placeholder
rather than servers to stop derived tags processing:
„ In the Graphics editor, create a button and then specify the DerivedOff <component>
command as the button’s press action. When the button is pressed, derived tags
processing stops.
„ In the Graphics editor, create a graphic object and then attach touch animation with
the DerivedOff <component> command as the object’s action. When the object is
touched, derived tags processing stops.
„ For the Logout Macro in the FactoryTalk View SE User Accounts editor, specify the
DerivedOff <component> command, or a macro that contains the command.
„ For the Shutdown command in the Display Settings Behavior tab, specify the
DerivedOff <component> command, or a macro that contains the command.

28-7
29 Using events

29 • Placeholder
This chapter describes:
„ what FactoryTalk® View Site Edition events are.
„ setting up events.
„ creating an events component.
„ starting and stopping events processing.

About events in FactoryTalk View Site Edition

Events are expressions that trigger actions.
Expressions are equations containing tag values, mathematical operations, if–then–else
logic, and other built-in FactoryTalk View functions. For information about using
expressions, see Chapter 23, Creating expressions.
Actions are FactoryTalk View commands, symbols, or macros. For example, an action
could initiate a snapshot of tag values using the DataLogSnapshot command, or change a
tag value using the Set command.

Events are detected at the FactoryTalk View SE Server (also called the HMI server).
Commands that run only at the FactoryTalk View SE Client are ignored when issued by an event
expression. For details about where commands run, see Appendix A in Volume 1 of the
FactoryTalk View Site Edition User’s Guide.

An events component is a file that contains the definitions of one or more events. An
events component can be run when an HMI server starts, or it can be run using the
EventOn command after the HMI server has started.

Parts of the Events editor

Use the Events editor to set up events processing for an application.

To open the Events editor

1. In FactoryTalk View Studio, in the Explorer window, open the Logic and Control
folder.
2. Right-click the Events icon, and then click New.

29-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

You can also open the Events editor by dragging its icon into the FactoryTalk View
Studio workspace, or by double-clicking an existing Events component.

Form

Spreadsheet

Accept and Discard buttons

When you enter information in the Events editor, the Prev and Next buttons change to
Accept and Discard buttons. Click Accept to save information. Click Discard to cancel
changes to the event component.

Form and spreadsheet

In the upper part of the form, specify the action and provide a description for the event
component.
In the Expression box, create the expression that will determine when the action is
performed. You can use the buttons beneath the box to build expressions. For more
information, see Chapter 23, Creating expressions.

29-2
 • • • • •
29 • USING EVENTS

Checking the syntax of an expression

29 • Placeholder
In the Events editor, to verify that the expression you typed uses correct syntax, click
Check Syntax. If the syntax is invalid, an error is displayed in the Check Syntax box.
You can check the syntax of an expression at any time while the Events editor is open. The
syntax is also checked automatically, when you click Accept or OK in the editor.

Creating an events component

An event consists of two parts: an expression and an action.
When a component in the expression changes, the expression is evaluated. If the
expression’s true state changes from false on the previous evaluation, to true on the
current evaluation, the action is triggered.
These are the tasks involved in setting up events for an application:
1. Create the events in the Events editor.
2. Set the maximum update rate for the events component in the Events Setup dialog
box.
3. Save the events component and give it a name. The file extension .eds is added by the
system.

To create an events component

1. In the Events editor, in the Action box, specify the command, macro or symbol that
will run when the event expression evaluates to true.
2. In the Expression box, create an expression that will determine the conditions for
triggering the action.
For information about expressions, see Chapter 23, Creating expressions.
3. Click Accept.
4. Click Next to create another event, if the events component is to contain more than
one event.
5. Repeat steps 1 through 4 until all events for the particular component are defined.
6. On the Setup menu, click Event Setup.
7. In the Event Setup dialog box type a description of the component, specify a
maximum update rate, and then click OK.
8. Click Close.
9. Provide a name for the events component, and then click OK.

29-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

For details about options in the Events editor and in the Setup dialog box, click Help.

About the maximum update rate

The maximum update rate is the fastest rate at which any event expression in an events
component can be updated.
The maximum update rate also determines the fastest rate at which data servers can send
changes in tag values.
Set a maximum update rate separately, for each events component you create.
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

Using multiple events components

You can create multiple events components, for example, to group events that need to be
evaluated at different rates.
Each HMI server in an network application can run up to 20 event components, with up to
1,000 tags in each component.

Do not create events that depend on other events. Events are not processed sequentially.

Modifying existing event components

You can modify events during development or when you run the application.
If you change an event component at run time, the changes will not take effect until you
stop and then restart events processing.

Starting and stopping events processing

There are many ways to start and stop events processing. Choose the way that works best
for the application.
To provide an operator with a way start and stop events processing, use FactoryTalk View
commands and macros in conjunction with graphic objects. For details about FactoryTalk
View command syntax, see the FactoryTalk View Site Edition Help.
In the following methods, <component> represents the name of an events file.

29-4
 • • • • •
29 • USING EVENTS

Ways to start events processing

29 • Placeholder
To start events processing, use any of these methods:
„ In the HMI Server Properties dialog box, click the Components tab, select the Events
check box, and then select an event component.
The event component will start the next time the HMI server runs, or when the HMI
server’s components are started manually.
„ In the Macros editor, create a macro that contains the command, EventOn
<component>. In the HMI Server Properties dialog box, click the Components tab,
select the Macro check box, and then specify the macro.
Event detection will start when the HMI server runs.
„ In the Graphics editor, create a button object and then specify the EventOn
<component> command as the button’s press action. When the button is pressed,
event detection starts.
„ In the Graphics editor, create a graphic object and attach touch animation to it, using
EventOn <component> in the Action box. When the object is touched, event detection
starts.
„ At the command line in FactoryTalk View Studio, or in the FactoryTalk View SE
Administration Console, type EventOn <component>, and then press Enter.
„ For the Login Macro in the FactoryTalk View SE User Accounts editor, specify the
EventOn <component> command, or a macro that contains the command.
„ For the Startup command in the Display Settings Behavior tab, specify the EventOn
<component> command, or a macro that contains the command.

Ways to stop events processing

To stop all the components that are running on the HMI server, including event
components, stop the components running on the HMI server manually.
For details about stopping an HMI server’s components manually in network applications,
see page 17-12 and in local applications, see page 18-5.
To stop a single event component, use any of these methods:
„ In the Macros editor, create a macro that contains the command, EventOff
<component>. In the HMI Server Properties dialog box, click the Components tab,
select the check box, On shutdown macro, and then specify the macro.
Events processing will stop when the HMI server shuts down.

29-5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

„ In the Graphics editor, create a button object and then specify the EventOff
<component> command as the button’s press action. When the button is pressed,
event detection stops.
„ In the Graphics editor, create a graphic object and attach touch animation to it, using
EventOff <component> in the Action box. When the object is touched, event detection
stops.
„ At the command line in FactoryTalk View Studio, or the FactoryTalk View SE
Administration Console, type EventOff <component>, and then press Enter.
„ For the Logout Macro in the FactoryTalk View SE User Accounts editor, specify the
EventOff <component> command, or a macro that contains the command.
„ For the Shutdown command in the Display Settings Behavior tab, specify the
EventOff <component> command, or a macro that contains the command.

29-6
APPENDIX D

Importing and exporting XML files

This appendix describes:
„ what XML is.
„ exporting FactoryTalk® View graphics data to XML files.
„ modifying exported XML files.
„ importing graphic display XML files.
„ the XML file structure for graphic displays.

About XML
XML is the Extensible Markup Language used to create documents with structured
information.
XML has a standardized format and structure. You can modify the elements and attributes
of a graphic display by changing them, or by adding new ones, in the XML file.
For more, general information about XML, see the World Wide Web Consortium’s web
page about XML at:
http://www.w3.org/XML.

For specific information about importing and exporting XML files in FactoryTalk
View SE. see the FactoryTalk View Site Edition Help.

Exporting graphics data to an XML file

The quickest way to create XML files for FactoryTalk View graphic displays is to export
the data from FactoryTalk View.
After exporting, you can open the XML file in Notepad, modify it, and then import the
modified file back into FactoryTalk View.

To export graphic display information to an XML file

1. In FactoryTalk View Studio, in the Explorer window, right-click the Displays editor.
2. Click Import and Export to open the Graphics Import Export Wizard.
3. In the Operation Type dialog box, select Export graphic information from displays,
and then click Next.

D-1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

4. Follow the instructions in the wizard. For details, click Help.

FactoryTalk View creates XML files for the selected graphic displays, in the location
you specify. In the same location.

FactoryTalk View also creates a file called BatchImport_Application name.xml. Use this file to
import several displays at once. To import a different set of displays than you exported,
modify the list of displays names in the BatchImport_Application name.xml file.

Modifying exported XML files

When you modify an XML graphic display file, you can make changes to objects that
already exist in the display or you can add additional objects.
When you import the file back into FactoryTalk View, the revised file overwrites the
previous XML file, so the changes you have made are visible when you open the display
in FactoryTalk View.
When you import the file you specify whether you are importing changes or new objects.
You can’t do both actions in a single import operation.
It is recommended that you use Notepad to edit XML files.

If you include attributes for an object whose name does not match one of those in the graphic
display, those attributes are not imported. Attributes for all other objects in the file whose names
do match the ones in the graphic display are imported.

Saving XML files in Notepad

Save XML files created or modified in Notepad using either the UTF-8 or UTF-16 file
format. Notepad’s Unicode file type corresponds to UTF-16 file format.
For files containing strings in English or other Latin-based languages, UTF-8 is
recommended, to reduce the size of the XML file. For other languages such as Chinese,
Japanese, or Korean, UTF-16 is recommended.
The first line of every XML file contains XML version and encoding attributes. Make
sure the encoding attribute matches the format that you are going to use when you save
the file.
For example, if the original file was saved in UTF-8 format and you plan to save it in
UTF-16 format, make sure the first line specifies
encoding=”UTF-16”

D-2
 • • • • •
D • IMPORTING AND EXPORTING XML FILES

Testing XML files

An XML file must be well-formed to be imported. To find out whether your XML file is
well-formed, test it.

To test an XML file

„ Open the XML file in Internet Explorer.
If you can see the XML code, your file is well-formed. If the XML code is not well-
formed, Internet Explorer displays an error message.

Importing XML files

You can import graphic display information in an XML file that has been created using an
external editor, or you can import an XML file that you originally exported from
FactoryTalk View and then modified.

When you import modified graphic displays, the existing displays are overwritten. To save a copy
of existing displays, select Yes when the Graphics Import Export Wizard displays the prompt “Do
you want to back up the displays that will be modified by the import?”
Alternatively, you can create backup copies by exporting the existing displays, before importing
the modified ones.

Error log file

If errors occur during importing, the errors are logged to a text file. The file opens
automatically when importing is finished. The last paragraph of the file lists the location
of the file.

Importing graphic display XML files

You can import a single graphic display XML file at a time, or import multiple graphic
displays. You can also choose whether to import new objects or update existing objects.
To import multiple graphic displays, specify the names of the graphic displays in the file
BatchImport_Application name.xml. FactoryTalk View creates this file when you export
multiple graphic displays.

To import graphic display information from an XML file

1. In the Explorer window, right-click the Displays editor.
2. Click Import and Export to open the Graphics Import Export Wizard.
3. In the Operation Type dialog box, select Import graphic information into displays, and
then click Next.

D-3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

4. Follow the instructions in the wizard.

For details about using the Graphics Import Export Wizard, see Help.

Graphic display XML file structure

The graphic display XML file is an FactoryTalk View XML document that describes the
objects and settings for a graphic display. The root element of the XML document is
called gfx. It represents the graphic display.
An XML document can contain only one root element. All other elements must be
contained within the beginning and end markers of the root element.
In an XML document, the start of an element is marked this way:
<element name>
The end is marked this way:
</element name>
The syntax for specifying an attribute for an element is:
attribute=“value”
The attribute value must be enclosed in single or double quotes. You can specify multiple
attributes for an element. For example, the caption element contains 13 possible attributes.
Elements for group objects begin with:
<group name>
and end with:
</group name>
The <group> element contains all the elements and attributes for each object in the group.
Here is a sample structure for a graphic display XML document containing two graphic
objects. Animations, Connections, and States are all group objects.
For more information about graphic object elements and their attributes, see Help.

Element Description
<gfx> Root element.
<displaySettings> Contains attributes from the Display Settings dialog box
in the Graphic Displays editor.
<object1> Contains attributes from the General and Common tabs in
the object’s Properties dialog box, as well as elements for
the object’s caption, image, animation, and connections.

D-4
 • • • • •
D • IMPORTING AND EXPORTING XML FILES

Element Description
<caption> Contains attributes for the object’s caption.
<imageSettings> Contains attributes for the object’s image.
<animations> Is a group object that contains an animation element for
each type of animation set up for the object.
<animateVisibility> Contains attributes for Visibility animation.
<animateColor> Contains attributes for Color animation.
</animations> Indicates the end of the animations object.
<connections> Is a group object that contains a connection element for
each connection assigned to the object.
<connection name= “Value”> Contains attributes for the Value connection.
<connection name= “Indicator”> Contains attributes for the Indicator connection.
</connections> Indicates the end of the connections object.
</object1> Indicates the end of the object1 element.

<object2> Contains attributes from the General and Common tabs in

the object’s Properties dialog box, as well as elements for
the object’s states and connections.
<states> Is a group object that contains state elements for each of
the object’s states.
<state stateid=“0”> Contains attributes for the object’s first state, as well as
elements for the state’s caption and image.
<caption> Contains attributes for the state’s caption.
<imageSettings> Contains attributes for the state’s image.
</state> Indicates the end of the state element.
<state stateid=“1”> Contains attributes for the object’s second state, as well as
elements for the state’s caption and image.
<caption> Contains attributes for the state’s caption.
<imageSettings> Contains attributes for the state’s image.
</state> Indicates the end of the state element.
</states> Indicates the end of the states object.
<connections> Contains a connection element for each connection
assigned to the object.
<connection name= “Value”> Contains attributes for the Value connection.
<connection name= “Indicator”> Contains attributes for the Indicator connection.
</connections> Indicates the end of the connections element.
</object2> Indicates the end of the object2 element.
</gfx> Indicates the end of the gfx element.

D-5
 • • • • •
INDEX

Index

Index
Symbols and Invoke command „ 21-25
modifying properties „ 21-23
.bmp files „ 19-27, 19-28
selecting using keyboard „ 20-10
.cab files „ 20-55
using names „ 21-24
.cli files „ 17-17, 18-7, 18-8
using with VBA code „ 21-25
.dat files „ 25-1, 25-2
ActiveX toolbox „ 20-54
.dxf files „ 19-27
activity logging
.ggfx files „ 19-24
See FactoryTalk Diagnostics
.gif files „ 19-27
adding components into an application „ 2-11
.jpg files „ 19-27
advanced objects „ 20-1, 20-31
.pcx files „ 19-27
ActiveX objects
.tif files „ 19-27
See ActiveX objects
.wmf files „ 19-27
arrow „ 20-31
.xml files „ 19-2, D-1
control list selector „ 20-31
[tag] parameter „ 21-20
creating „ 20-39, 20-40
Enter key handshaking „ 20-40
A scrolling key list „ 20-39
absolute references „ 6-6 states for „ 20-39
in commands „ A-5 value tag „ 20-40
syntax „ 6-6 display list selector „ 20-31
to tags „ 9-6 creating „ 20-33
acknowledge bit „ 11-12 states for „ 20-33
Acknowledge command „ 11-10 HMI tag alarm summary „ 20-31
AcknowledgeAll command „ 11-10 local message display „ 20-31
acknowledging alarms creating „ 20-34
FactoryTalk alarms „ 12-41 OLE objects „ 20-51
HMI tag alarms „ 11-10 converting „ 20-52
activation creating „ 20-52
demo mode „ 1-10 piloted control list selector „ 20-31
grace period „ 1-10 controlling remotely „ 20-42
in a redundant system „ 14-11 creating „ 20-41
running without „ 1-10 Enter key handshaking „ 20-43
Active (Can’t reach partner) „ 14-6 indicator tag for „ 20-45
Active macro remote access tag for „ 20-45
See On Active macro resetting Enter tag „ 20-44
Active state „ 14-4 scrolling key list „ 20-42
ActiveX objects „ 19-2, 20-2, 20-53 states for „ 20-41, 20-44
applying animation to „ 21-22 top position tag „ 20-45
deploying automatically „ 20-55 value tag „ 20-43, 20-45
events „ 21-25 visible states tag „ 20-45
highlighting in a display „ 20-10 recipe object „ 20-31
methods „ 21-25 selecting using keyboard „ 20-10

I–1
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

tag label „ 20-31 testing „ 21-6, 26-4

creating „ 20-32 using VBA code „ 21-22
time and date display „ 20-31 viewing animation „ 21-6
creating „ 20-33 Animation dialog box „ 21-2
trends opening „ 21-3
See trends animation types „ 21-7
Alarm and Event Historian „ 12-32 color „ 21-8
alarm and event history logging „ 12-31 in grouped objects „ 21-5
alarm and event objects „ 20-2 fill „ 21-11
alarm banner „ 12-11 in grouped objects „ 21-5
alarm status explorer „ 12-11 horizontal position „ 21-11
alarm summary „ 12-10 horizontal slider „ 21-13
log viewer „ 12-11 OLE verbs „ 21-14
selecting using keyboard „ 20-10 rotation „ 21-11
See also FactoryTalk Alarms and Events touch „ 21-13
Alarm and Event Setup editor „ 12-24 vertical position „ 21-11
alarm class „ 12-12 vertical slider „ 21-14
Alarm Import Export Wizard „ D-1 visibility „ 21-8
alarm logging width „ 21-13
FactoryTalk alarms „ 12-32 Application Manager „ 6-21, 7-10
HMI tag alarms „ 11-23 backing up applications in „ 18-3
alarm monitoring restoring applications in „ 18-3
planning „ 3-5 application server states „ 14-4
See FactoryTalk Alarms and Events for redundant servers „ 14-5
See HMI tag alarms applications „ 2-1, 6-1, 7-1
Alarm Setup editor „ 11-14 adding process faceplates to „ 19-26
Alarm Status Explorer „ 12-45 deploying „ 17-1, 18-1
alarm tags „ 12-13, 12-52 navigating displays in „ 22-1
AlarmLogRemark command „ 11-38 opening „ 2-2
aligning graphic objects „ 19-11 planning „ 3-1
animation „ 21-1 a redundant system „ 14-9
and global objects „ 21-7 alarm monitoring „ 3-5
applying to object groups „ 19-16, 21-5 communications „ 3-4
precedence „ 21-5 customizing the system „ 3-14
copying „ 21-7 for multiple users „ 3-13
defining range of motion „ 21-4 network layout „ 3-2
display keys „ 21-19 security „ 3-8
duplicating objects with „ 21-7 trends „ 3-12
for ActiveX objects „ 21-1, 21-22 redundant servers in „ 14-2, 14-8
linking to actions „ 21-4 referencing components in „ 6-6
linking to expressions „ 21-1, 21-3 restoring „ 17-9
linking to keys „ 21-1 Sample Water „ 1-10
linking to tags „ 21-1, 21-3 setting up run time „ 3-10
object keys „ 21-17 switching languages in
Object Smart Path „ 21-5 See language switching
tag placeholders in „ 21-3 arc graphic object „ 20-6

I–2
 • • • • •
INDEX

areas „ 6-5 See FactoryTalk View Studio

adding to an application „ 6-10 client keys „ 22-4
application root „ 7-1 creating „ 22-10
deleting „ 6-10 precedence „ 22-7

Index
home area „ 6-5, 9-6 running a key file „ 22-11
in Execute command parameters „ 11-37 color „ 19-17
in network applications „ 6-2 in graphic objects „ 21-8
maximum number of HMI servers „ 6-13 in HMI tag alarm summaries „ 11-32
showing in HMI tag alarm summaries in trends „ 26-13
„ 11-34 color animation „ 21-8
arithmetic operators „ 23-6 Command Wizard „ 2-15
arranging graphic objects „ 19-10 building commands in „ 2-14
arrow graphic objects „ 20-31 commands „ A-1
audit messages „ 15-3 See also individual command entries
auto-repeat for keys „ 20-31 absolute references to „ A-5
availability building in Command Wizard „ 2-14
See system availability connecting to ActiveX events „ 21-25
display caching „ 26-22
B execution of „ A-3
for moving among displays „ 22-2
Background Color palette „ 19-18
in macros „ 2-15
bar graph objects „ 20-29
placeholders in „ A-2
base objects „ 19-2
relative references in „ A-5
tag placeholders in „ 19-33
setting up security for „ 5-17
See also global objects
startup and shutdown „ 19-41
bitwise operators „ 23-8
using placeholders in „ 27-2
Browse button „ 2-14
using touch animation to run „ 21-13
buffer zone
Common actions
See HMI tag alarms, deadband
buffering messages „ 15-6
See security permissions, Common actions
communications „ 8-1, 8-2
built-in alarm detection „ 12-2
DDE
Business Objects Crystal Reports „ 25-1
and FactoryTalk Diagnostics „ 15-1
See DDE communications
error function „ 23-16
button objects „ 20-11, 20-12
planning „ 3-4
opening displays with „ 22-5
computer accounts „ 5-26
condition-related events „ 12-6
C Connections tab „ 19-20
CABARC.exe „ 20-55 constants „ 23-6
caching graphic displays „ 19-38 contacting
calling methods „ 21-25 Rockwell Automation „ P-4
captions „ 20-7 technical support „ P-4
changing passwords „ 5-7 control
Check Syntax button „ 23-4 See animation
circle graphic object „ 20-5 control list selectors „ 20-31, 20-39, 20-44
client copying HMI servers „ 17-7
See FactoryTalk View SE Client creating display templates „ 3-11

I–3
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Crystal Reports server cache file „ 8-12

See Business Objects Crystal Reports setting up properties „ 8-10
current application language „ 13-7 redundancy
See system availability
D RSLinx Classic
Backup Restore Utility „ 17-15
data display objects „ 20-19
RSLinx Enterprise „ 8-1
data log files „ 25-6
adding „ 6-12, 7-6, 8-5
and third-party software „ 25-1
deleting „ 8-8
deleting „ 25-6
moving files „ 17-15
managing files „ 25-6
setting up Alarms and Events „ 8-8
naming „ 25-2
setting up properties „ 8-6
run-time limits „ 25-2
tags in „ 9-1
storage format „ 25-2
using multiple servers „ 6-12, 8-3
ODBC „ 25-1, 25-3
data sources for HMI tags „ 10-2
data log models „ 25-1
device „ 10-8
modifying „ 25-13
memory „ 10-9
Data Log Models editor „ 25-5, 25-8
date and time displays „ 20-33
data logging „ 9-5, 25-1
DDE communications
and events „ 25-12
HMI server as client „ B-2, B-3
choosing data to log „ 25-7
poll rate „ B-3
commands
syntax „ B-3
DataLogMergeToPrimary „ 25-11
default application language „ 13-6
DataLogNewFile „ 25-9
setting up „ 13-8
DataLogOff „ 25-15
Define command „ A-6
DataLogOn „ 25-14
deploying local applications „ 18-1
DataLogSnapshot „ 25-12
backing up „ 18-3
DataLogSwitchBack „ 25-10
the Local Directory „ 18-4
log triggers „ 25-6
changing HMI server properties „ 18-5
ODBC data source „ 25-7
creating the run-time client „ 18-7
creating new „ 25-7, 25-8
restoring „ 18-3
ODBC database tables „ 25-7, C-3
the Local Directory „ 18-4
on demand „ 25-12
starting and stopping components „ 18-5
paths „ 25-5
steps involved in „ 18-1
moving data between „ 25-11
updating data server names „ 18-6
switching at run time „ 25-10, 25-13
deploying network applications „ 17-1
starting „ 25-14
backing up „ 17-3
stopping „ 25-15
the Network Directory „ 17-5
when to log data „ 25-6
changing data server properties
data servers „ 6-2, 8-1
updating computer name „ 17-16
adding to a local application „ 7-6
changing HMI server properties „ 17-10
adding to a network application „ 6-12
starting and stopping the server „ 17-12
deleting „ 8-8
starting services „ 17-14
OPC data servers „ 8-1
stopping services „ 17-13
adding „ 6-12, 7-7, 8-9
updating computer name „ 17-11
deleting „ 8-13
copying client files „ 17-17

I–4
 • • • • •
INDEX

copying HMI servers „ 17-7 display list selectors „ 20-31, 20-33

using the HMIBackup utility to „ 17-8 Display Settings dialog box „ 19-35
creating new client files „ 17-17 Set as Default „ 19-44
moving files displays

Index
HMI projects „ 17-6 See graphic displays
RSLinx Classic „ 17-15 Displays editor
RSLinx Enterprise „ 17-15 See Graphics editor
restoring „ 17-9 distributed applications
the Network Directory „ 17-10 See network applications
setting up the Network Directory „ 17-5 docking graphic displays „ 12-39, 19-45
specifying the location of „ 17-6 Download command „ 20-23
steps involved in „ 17-2 DownloadAll command „ 20-23
synchronizing HMI servers with projects drawing objects „ 20-1
„ 17-14 arc „ 20-6
derived tags „ 28-1 circle „ 20-5
commands ellipse „ 20-5
DerivedOff „ 28-6 images „ 20-8
DerivedOn „ 28-5, 28-6 adding into displays „ 20-8, 20-9
creating „ 28-4 adding to an application „ 20-8
limits „ 28-5 modifying properties „ 20-6
maximum update rate for „ 28-4 panel „ 20-8
modifying „ 28-5 polygon „ 20-5
starting and stopping processing „ 28-5 polyline „ 20-5
deviation alarms „ 12-9 rectangle „ 20-4
device-based alarms „ 11-2, 12-2, 12-3 rounded rectangle „ 20-4
Diagnostics List „ 2-5, 15-7 square „ 20-4
clearing messages „ 2-5, 15-8 text „ 20-7
hiding and showing „ 2-6 choosing fonts „ 20-7
Diagnostics Viewer „ 15-9 wedge „ 20-6
opening at run time „ 15-9 duplicating graphic objects „ 19-9
disabling alarms „ 12-48
display cache „ 19-38, 22-6 E
adding displays „ 19-43
Edit Display mode „ 19-23, 26-4
removing displays „ 19-44
electronic signatures „ 20-55
Display command
ellipse graphic object „ 20-5
and key lists „ 21-20
embedded variables „ 24-1
caching parameters for „ 19-43
displaying at run time „ 24-8
docking parameters for „ 19-45
inserting „ 24-1
position parameters for „ 19-40
in captions „ 24-2
display grid „ 19-7
in local messages „ 24-2
display hierarchy „ 3-10
in title bar text „ 24-3
display keys „ 21-17
in tooltips „ 24-3
creating „ 21-19
modifying „ 24-3
key list „ 21-19
numeric variables „ 24-3
precedence „ 22-7
syntax with numbers „ 24-4
running commands with „ 21-20

I–5
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

syntax with tags „ 24-4 built-in functions „ 23-11

string variables „ 24-5 file functions „ 23-12
syntax with strings „ 24-6 for FactoryTalk alarms „ 12-54
syntax with tags „ 24-6 alarm source „ 12-56, 12-58
time and date variables „ 24-7 for HMI tag alarms „ 23-15
syntax „ 24-8 acknowledged „ 11-11
types of values in „ 24-1 in alarm „ 11-11
updating at run time „ 24-10 wildcards in „ 11-12
enabling alarms „ 12-44, 12-48 language function „ 23-18
Enter key „ 20-40 math functions „ 23-11
handshaking „ 20-40, 20-43, 20-45 security functions „ 23-17
resetting the Enter tag „ 20-44 tag functions „ 23-15
turning off „ 20-57 time functions „ 23-13
error messages „ 15-3 checking syntax „ 23-4
event-based alarms „ 11-21 constants in „ 23-6
events „ 29-1 copying „ 23-4
commands evaluating operators „ 23-9
EventOff „ 29-5 for reporting communication errors „ 23-15
EventOn „ 29-5 formatting „ 23-4
creating „ 29-3 HMI tag alarm events in „ 11-23
evaluation interval for „ 29-4 if–then–else logic „ 23-19
for ActiveX objects „ 21-25 logical operators in „ 23-7
for on-demand logging „ 25-12 placeholders in „ 23-5
limits „ 29-4 relational operators in „ 23-7
maximum update rate for „ 29-4 tags in „ 23-5
modifying „ 29-4
starting and stopping processing „ 29-4 F
using multiple components „ 29-4
Execute button „ 11-37 F1 key and precedence „ 22-7
Execute command „ 11-37 FactoryTalk Activation „ 1-5, 1-10
Explorer See also activation
in FactoryTalk View Studio „ 2-7 FactoryTalk Alarms and Events „ 1-5, 12-1
opening editors in „ 2-8 acknowledging alarms „ 12-41
opening folders in „ 2-8 all alarms „ 12-42
exporting security permissions for „ 12-44
graphic displays „ D-1 selected alarms „ 12-42
text strings using alarm tags „ 12-53
See language switching advantages „ 12-2
expressions „ 2-15, 23-1 alarm and event banner „ 12-11, 12-34
and data logging „ 25-12 at run time „ 12-38
and derived tags „ 23-1 docking to client window „ 12-39
and events „ 23-1 alarm and event log viewer „ 12-11
and object animation „ 21-3 creating „ 12-50
arithmetic operators in „ 23-6 parts „ 12-50
assigning to graphic objects „ 19-20 alarm and event policies „ 12-16
building „ 23-3 alarm and event summary „ 12-10, 12-34

I–6
 • • • • •
INDEX

alarm monitoring in „ 12-39 suppressing alarms „ 12-43

filtering and sorting data „ 12-41 security permissions for „ 12-44
parts „ 12-40 tag-based alarms „ 12-24
alarm class „ 12-12 alarm messages for „ 12-29

Index
alarm displays „ 12-10, 12-34 alarm tags for „ 12-53
alarm faults „ 12-8 deviation alarms „ 12-27
alarm history logging „ 12-22 digital alarms „ 12-24
alarm logs „ 12-14 in Alarm and Event Setup editor „ 12-28
alarm messages „ 12-14 level alarms „ 12-25
alarm monitoring status tags for „ 12-28
security for „ 12-17 update rates for „ 12-31
setting up „ 12-15 FactoryTalk Diagnostics „ 15-1
alarm priority „ 12-11 See also Diagnostics List
modifying „ 12-12 audiences „ 15-4
setting up „ 12-22 categorizing tag writes „ 15-4
alarm servers destinations „ 15-2
RSLinx Enterprise „ 12-18 getting Help for „ 15-2
Tag Alarm and Event Servers „ 12-21 logging to ODBC „ 15-5
alarm severity „ 12-11 buffering messages „ 15-6
alarm states „ 12-13 messages „ 15-3
alarm status explorer „ 12-11, 12-45 audiences „ 15-4
disabling alarms in „ 12-48 categories „ 15-3
parts „ 12-46 routing „ 15-2, 15-5
suppressing alarms in „ 12-48 Setup tool „ 15-4
viewing details in „ 12-47 viewing log files „ 15-9
alarm status tags „ 12-14 FactoryTalk Diagnostics Viewer
alarm tags „ 12-13, 12-52 See Diagnostics Viewer
built-in alarm functions „ 12-54 FactoryTalk Directory „ 4-1
number of alarms „ 12-55 local cache „ 14-6
severity „ 12-54 Local Directory „ 1-10, 4-1
specifying alarm source „ 12-56 setting up „ 4-7
deadband „ 12-8 Network Directory „ 1-10, 4-1
deviation alarms „ 12-9 backing up „ 17-5
digital alarms „ 12-10 managing multiple applications „ 4-4
disabling alarms „ 12-43 monitoring server status „ 14-7
enabling alarms restoring „ 17-10
security permissions for „ 12-44 specifying localhost „ 4-5
history logging „ 12-31 specifying location of „ 17-6
defining databases „ 12-33 restoring „ 4-7
enabling „ 12-33 service disruptions „ 4-8
importing and exporting alarms „ 12-59 single sign-on to „ 5-5
formats „ 12-60 FactoryTalk Security
latched digital alarms „ 12-10, 12-43 assigning permissions „ 5-31
resetting „ 12-43, 12-44 authorizing users „ 5-1
level alarms „ 12-7 changing passwords „ 5-7
limits „ 12-7 computer accounts „ 5-25

I–7
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

finding information about „ 5-3 See HMI servers

for local applications „ 7-4 FactoryTalk View Site Edition
single sign-on „ 5-5 See FactoryTalk View SE
system policies „ 5-27 FactoryTalk View Studio „ 1-4
system resources „ 5-28 Communications tab „ 2-4
user accounts „ 5-25 editors „ 2-9
FactoryTalk system „ 14-1 Alarm Setup „ 11-14
FactoryTalk View „ P-1 Client Keys „ 22-10
formerly RSView Enterprise „ P-1 Data Log Models „ 25-5, 25-8
Secured Commands editor „ 5-17 Derived Tags „ 28-2
tools „ 1-5 Events „ 29-1
Application Manager „ 6-21, 18-3 Expressions „ 23-2
Diagnostics Viewer „ 15-9 Graphics „ 19-3
FactoryTalk Diagnostics Setup „ 15-4 hints for working in „ 2-13
HMI Tag Alarm Log Viewer „ 11-27 printing from „ 2-15
HMIBackup utility „ 17-8 Runtime Security „ 5-11
Specify FactoryTalk Directory Location Secured Commands „ 5-17
„ 4-5, 14-7 Suppressed List „ 11-10, 11-29
Tag Import and Export Wizard „ 10-10 Tags „ 10-4, 11-19
FactoryTalk View SE Explorer window in „ 2-4
activity messages in „ 15-3 exploring „ 2-3
documentation set „ P-2 opening editors „ 2-8
graphic objects in „ 20-1 running „ 2-1
logging on and off „ 5-4 status bar in „ 2-6
software components „ 1-4 toolbars in „ 2-3
system limits „ 14-10 workspace in „ 2-4
FactoryTalk View SE Administration Console Failed state „ 14-4
„ 17-20, 18-9, 25-13 file formats
FactoryTalk View SE Client „ 1-4 for alarm log „ 11-28
changing passwords „ 5-7 for data logs „ 25-2
copying client files „ 17-17 for exported text strings „ 13-11
creating a new client file „ 17-17, 18-7 in Microsoft Excel „ 13-12
docking displays in „ 12-39, 19-45 Unicode text files „ 13-12
logging off „ 5-7, 17-19, 18-8 file functions „ 23-12
logging on to „ 17-19, 18-8 file types
object model „ 16-1, 16-4 graphics
Help for „ 16-8 importing „ 19-27
preventing scroll bars in „ 19-39 using bitmaps „ 19-28
setting up security for „ 5-20, 17-19, 18-9 log files „ 25-2
starting „ 17-18 ODBC alarm log „ 11-25
from Tools menu „ 17-18, 18-8 ODBC data log „ 25-3
multiple clients „ 17-18 fill animation „ 21-11
using .cli file „ 17-18 filtering alarms
when Windows starts „ 17-18, 18-8 in HMI tag alarm summaries „ 11-34
system limits „ 14-11 filtering tags „ 9-11
FactoryTalk View SE Server removing a filter „ 9-12

I–8
 • • • • •
INDEX

finding information linking grouped objects „ 20-51

about FactoryTalk Alarms and Events updating at run time „ 19-2
„ 12-4 tag placeholders in „ 19-32, 19-33
about FactoryTalk Security „ 5-2 modifying „ 19-35

Index
about FactoryTalk View SE „ P-2 graphic displays „ 19-1
in this manual „ P-2 aligning objects in „ 19-11
on the Internet „ P-3 appearance of „ 19-35
flipping graphic objects „ 19-14 arranging objects in „ 19-10
FlushCache command „ 19-41, 19-44 assigning parameter files to „ 19-31
running on shutdown „ 19-41 behavior of „ 19-35
fonts „ 20-7 caching „ 19-38, 22-6
for Windows languages „ 13-5 using the Display command „ 19-43
in HMI tag alarm summaries „ 11-32 color for input objects in „ 19-42
substituting at run time „ 20-7 commands
Foreground Color palette „ 19-18 display caching parameters „ 19-43
functions Download „ 20-23
See expressions, built-in functions DownloadAll „ 20-23
FlushCache „ 19-41, 19-44
G PrintDisplay „ 19-48
PullForward „ 19-37
gauge and graph objects „ 20-1
PushBack „ 19-37
bar graph „ 20-29
RecipeRestore „ 20-37
using to compare values „ 20-28
RecipeSave „ 20-38, 20-39
gauge „ 20-29
ScreenPrint „ 19-48
using to show limits „ 20-27
SetFocus „ 19-37
scale „ 20-29
shutdown „ 19-41
global object displays „ 19-24
startup „ 19-41
at run time „ 19-25
Upload „ 20-23, 20-38
base objects in „ 19-2
UploadAll „ 20-23, 20-38
creating „ 19-24, 19-25
creating Help for „ 21-21
from standard display „ 19-25
creating templates for „ 3-11, 19-44
creating global objects in „ 19-2, 20-46
default settings for „ 19-44
file type „ 19-24
defining display keys „ 21-19
location of „ 19-24
designing „ 3-10
global objects „ 19-24, 20-2, 20-46
docking „ 12-39, 19-45
animating „ 21-7
closing docked displays „ 19-47
base objects „ 19-2
duplicating objects in „ 19-9
breaking links „ 20-51
exporting to XML „ D-1
in global object displays „ 19-24
flipping objects in „ 19-14
parameter values for „ 19-33
global object displays „ 19-24
reference objects „ 19-2
grouping objects in „ 19-15
and the graphic libraries „ 20-48
HMI tag alarm information in „ 11-9
breaking links „ 20-51
importing XML „ D-3
creating „ 20-47
improving performance „ 19-43
link to base object „ 20-47
interactive objects in „ 19-42
linked properties „ 20-48
line properties for objects in „ 19-19

I–9
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

modifying object groups in „ 19-17 See drawing objects

naming objects in „ 19-19 gauges and graphs
navigating „ 22-1 See gauge and graph objects
using a hierarchy „ 3-10, 22-1 indicators
using buttons „ 22-5 See indicator objects
using keys „ 22-4 keys
On Top type „ 19-37 See key objects
Overlay type „ 19-36 numeric and string
patterns for objects in „ 19-18 See numeric and string objects
positioning displays „ 19-40 OLE
positioning objects „ 19-7 See OLE objects
printing „ 2-15, 19-48 push buttons
at run time „ 2-16 See push button objects
Replace type „ 19-36 trend
replacing text strings in „ 19-21 See trends
resizing displays „ 19-39 graphic objects „ 20-1
resizing objects in „ 19-9 aligning „ 19-11
rotating objects in „ 19-15 applying animation to „ 21-2
running multiple copies „ 19-37 See also animation
securing „ 5-18, 19-40 arranging „ 19-10
selecting objects in „ 19-8 assigning expressions to „ 19-20
spacing objects in „ 19-13 assigning tags to „ 19-20
stacking objects in „ 19-10 captions „ 20-7
startup and shutdown commands „ 19-41 embedded variables in „ 24-2
tag limits „ 9-5, 20-21 checking index numbers „ 21-15
testing „ 19-23 choosing text fonts „ 20-7
animation in „ 21-6 common properties of „ 20-3
object states in „ 19-23 converting „ 19-28
trends in „ 26-4 defining object keys „ 21-17
title bar „ 19-38 duplicating „ 19-9
embedded variables in „ 24-3 exporting to XML „ D-1
tooltips for objects in „ 19-21 flipping „ 19-14
ungrouping objects in „ 19-16 for displaying data „ 20-19
wallpaper „ 19-22 for inputting data „ 20-19
xml import and export „ 19-2 importing „ 19-27
zooming in and out „ 19-6 importing XML „ D-3
graphic libraries line properties „ 19-19
See libraries modifying groups „ 19-17
graphic object types „ 20-1 modifying properties „ 20-6
ActiveX names for „ 19-19
See ActiveX objects patterns for „ 19-18
advanced positioning in display grid „ 19-7
See advanced objects replacing text in „ 19-21
alarm and event resizing „ 19-9
See alarm and event objects rotating „ 19-15
drawing selecting „ 19-8

I–10
 • • • • •
INDEX

using keyboard „ 20-10 adding to an application „ 2-11

spacing „ 19-13 as command parameters „ A-6
stacking „ 19-10 creating „ 2-10
supplying tags for „ 20-9 file names „ 2-12

Index
testing states „ 19-23 maximum length „ 2-12
tooltips „ 19-21 spaces in „ 2-12
embedded variables in „ 24-3 in Explorer window „ 2-10
using data in „ 20-9 in HMI servers „ 6-5
using index numbers to navigate „ 21-14 opening „ 2-11
viewing states „ 19-23 relative references to „ 6-6
in Property Panel „ 19-24 viewing „ 2-10
in States toolbar „ 19-23 HMI projects „ 6-5, 7-4
Graphics editor „ 19-3 deleting project files „ 6-20
display area „ 19-4 gaining access to folder „ 2-2
shortcut menus „ 19-8 moving project files „ 17-6
status bar „ 19-4 HMI servers „ 6-4
toolbars „ 19-3, 19-7 about redundancy for „ 6-8
ActiveX toolbox „ 20-54 See also system availability
group edit mode „ 19-17 adding to an application „ 6-11
grouped objects „ 19-15 as DDE client „ B-2
animating „ 21-5 copying „ 17-7
ungrouping „ 19-16 deleting „ 6-19
HMI services
H starting manually „ 17-14
stopping manually „ 17-13
HandshakeOn command „ 11-13
in local applications „ 7-2, 7-4
handshaking
in network applications „ 6-2
for Enter key „ 20-43, 20-45
installing the HMIBackup utility „ 17-8
handshake bit „ 11-13
limits in redundant system „ 14-11
Health Monitoring Policy „ 14-31
monitoring disk space „ 17-21
highlight
monitoring status „ 7-9
enabling or disabling „ 19-42
On active macro „ 6-18
for ActiveX objects „ 20-10
On standby macro „ 6-18
for trend objects „ 20-10, 26-13
properties „ 6-14, 7-7, 17-10, 18-5
historical alarms and events „ 12-14
running multiple servers „ 6-13
HMI analog tags „ 10-1
showing in Tag Browser „ 9-9
setting up alarms for „ 11-20
starting and stopping „ 17-12, 18-5
HMI clients „ 6-5, 7-4
startup components „ 6-17
HMI device tags
synchronizing with projects „ 17-14
data sources for „ 10-8
using multiple servers „ 6-12
DDE communications „ B-2
HMI string tags „ 10-1
HMI digital tags „ 10-1
HMI system tags „ 10-1
setting up alarms for „ 11-20
HMI Tag Alarm Log Viewer „ 11-27
HMI memory tags „ 10-9
HMI tag alarms „ 9-3, 11-1, 12-4
HMI project components
acknowledging „ 11-10, 11-12
absolute references to „ 6-6
acknowledge bit „ 11-12

I–11
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

alarm banner „ 11-6 charting in trends „ 26-15

alarm displays „ 11-7 commands
alarm events „ 11-21 Acknowledge „ 11-10
logging „ 11-23 AcknowledgeAll „ 11-10
alarm faults „ 11-4 AlarmLogRemark „ 11-26, 11-38
alarm log files „ 11-7 AlarmOff „ 11-8, 11-40
adding remarks to „ 11-26 AlarmOn „ 11-13, 11-40, 25-14
creating „ 11-24, 11-25 HandshakeOn „ 11-13
limits „ 11-28 Identify „ 11-39
location „ 11-24 SuppressOn „ 11-10
names „ 11-28 deadband „ 11-5
viewing „ 11-27 defining alarm conditions „ 11-19
alarm logging „ 11-23 for analog tags „ 11-20
exporting to ODBC „ 11-25 for digital tags „ 11-20
on redundant servers „ 11-16 in Tags editor „ 11-14, 11-19
to ODBC „ 11-25 Execute command „ 11-37
alarm messages „ 11-17 for analog tags „ 11-20
Acknowledged „ 11-17 for digital tags „ 11-20
custom messages „ 11-19 handshake bit „ 11-13
In Alarm „ 11-17 handshaking
Out of alarm „ 11-17 switching on „ 11-13
placeholders in „ 11-18 Identify button „ 11-39
system defaults „ 11-18 ODBC alarm log tables „ C-1
types „ 11-7 Suppressed List „ 11-29
user default „ 11-19 suppressing „ 11-10
alarm monitoring system tags „ 11-9
on redundant servers „ 11-16 tag placeholders in „ 11-35
setting up „ 11-15 HMI tags „ 9-1, 9-4
starting and stopping „ 11-39 analog tags „ 10-1
alarm severity „ 11-6 browsing „ 9-9
setting up „ 11-16 creating „ 10-6, 10-9, 28-3, 29-2
alarm summary „ 11-8, 20-31, 21-22 in Tag Browser „ 9-12
buttons „ 11-33 data sources for „ 10-2
colors „ 11-32 DDE „ B-2
creating „ 11-30 deleting „ 10-7
filtering data „ 11-34 designing a database „ 3-7
fonts „ 11-32 device tags „ 10-2
inserting headings „ 11-31 digital tags „ 10-1
showing areas „ 11-34 duplicating „ 10-7
sorting data „ 11-34 importing „ 10-10
alarm thresholds „ 11-3 in Tag Browser „ 9-12
variable thresholds „ 11-4 memory data source „ 10-9
and FactoryTalk alarms „ 12-2 memory tags „ 9-3
built-in functions „ 11-11, 23-15 minimum and maximum values „ 9-2
acknowledged „ 11-11 modifying „ 10-7
in alarm „ 11-11 naming „ 10-3

I–12
 • • • • •
INDEX

offsetting values „ 9-2 breaking inheritance „ 5-33

organizing in folders „ 10-3 overriding inheritance „ 5-34
scaling values „ 9-2 input focus
setting up alarms for „ 11-20 giving to graphic objects „ 20-10

Index
setting up security for „ 5-19, 9-2 specifying behavior „ 19-42
string tags „ 10-1 input objects „ 20-19
syntax for OPC addresses „ 10-8 commands
system tags „ 10-1 Download „ 20-23
Tags editor „ 10-4 DownloadAll „ 20-23
using in expressions „ 10-3 NextPosition „ 21-16
HMIBackup utility „ 17-8 Position „ 21-16
home area „ 6-5, 9-6 PrevPosition „ 21-16
finding tags in „ 9-9 Upload „ 20-23, 20-38
horizontal position animation „ 21-11 UploadAll „ 20-23, 20-38
horizontal slider animation „ 21-13 highlight for
Host unreachable „ 14-4 enabling or disabling „ 19-42
question marks in „ 20-37
I retrieving data using „ 20-20
sending data using „ 20-20
Identify command „ 11-39
shortcut keys for „ 20-22
if-then-else expressions „ 23-19
specifying behavior for „ 19-42
images „ 20-8
specifying color for „ 19-42
importing „ 20-9
updating values continuously „ 20-21
pasting into displays „ 20-9
validating operator input „ 20-22
placing in displays „ 20-8
interactive objects
importing
specifying behavior of „ 19-42
graphic displays „ D-1
translated text files
See also advanced objects
interlocked push buttons „ 20-12, 20-17
See language switching
Invoke command „ 21-25
index numbers „ 21-14
checking „ 21-15
modifying „ 21-17 K
removing „ 20-11 key list „ 21-19
indicator objects „ 20-1 disabling „ 21-20
connecting to tags „ 20-26 key navigation „ 20-10
indicator tag „ 20-26, 20-45 turning off „ 20-11
list indicator „ 20-25 key objects „ 20-1, 20-30
creating „ 20-27 auto-repeat for „ 20-31
multistate indicator „ 20-25 backspace „ 20-30
creating „ 20-26 End „ 20-30
states for „ 20-25 Enter „ 20-30
least significant bit „ 20-26 Home „ 20-30
symbol indicator „ 20-25 Move down „ 20-30
creating „ 20-26 Move left „ 20-30
information messages „ 15-3 Move right „ 20-30
inheriting security permissions „ 5-33 Move up „ 20-30

I–13
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

Page down „ 20-30 support in graphic libraries „ 13-26

Page up „ 20-30 text files
Send press to „ 20-31 importing „ 13-20
keyboard shortcuts „ 22-8 troubleshooting imports „ 13-21
keypad for numeric input „ 19-43 text strings
keys „ 20-29, 22-6 exporting „ 13-9
See also key list optimizing duplicate strings „ 13-15
See also special keys that do not allow switching „ 13-2
animation „ 20-29 troubleshooting exports „ 13-11
arrow keys in trends „ 26-28 undefined „ 13-9
client keys „ 21-17 latched push buttons „ 20-12, 20-15
display keys „ 21-19 level alarms „ 12-7
Enter key handshaking „ 20-40 libraries „ 19-27
object keys „ 21-17 global objects in „ 20-48
on-screen keyboard „ 19-43, 20-23, 20-29 location of files „ 19-27
opening displays with „ 22-4 support for languages in „ 13-26
precedence among key types „ 22-7 using for trends „ 26-21
running commands with „ 21-20 line properties „ 19-19
shortcut keys „ 22-8 list indicators „ 20-25, 20-27
using to scroll lists „ 20-39 Loading state „ 14-4
viewing at run time „ 21-19 local applications „ 2-1, 7-1
administering at run time „ 18-10
L creating „ 7-5
importing projects „ 7-5
Language command „ 13-26
data servers in „ 7-2
Language Configuration dialog box „ 13-9,
deleting „ 7-10
13-20
deploying
language function „ 23-18
language switching „ 13-1
See deploying local applications
HMI server in „ 7-2
application languages „ 13-6
properties „ 7-7
adding „ 13-8
parts of „ 7-1
current language „ 13-7
renaming „ 7-10
default language „ 13-6
run-time client for „ 18-7
maximum number „ 13-1
security for „ 7-4
selecting „ 13-6
setting up the Local Directory „ 4-7
exported text files
structure of „ 7-1
Microsoft Excel files „ 13-13, 13-17
local message displays „ 20-31, 20-34
duplicate strings „ 13-15
local messages „ 20-34
format „ 13-12
embedded variables in „ 24-2
translating strings „ 13-15
logging off
Unicode files „ 13-12 at run time „ 5-7, 17-19, 18-8
format „ 13-16 from FactoryTalk View SE „ 5-4
schema „ 13-18 logging on
in local messages „ 13-2 at run time „ 17-19, 18-8
installing Windows languages „ 13-6 single sign-on „ 5-5
regional settings and „ 13-2 to FactoryTalk View SE „ 5-4

I–14
 • • • • •
INDEX

logging paths for HMI projects „ 17-6

See data logging, paths moving graphic objects „ 21-11
logging system activity multistate indicators „ 20-25, 20-26
See FactoryTalk Diagnostics multistate push buttons „ 20-12, 20-16

Index
logical operators „ 23-7
login and logout macros „ 27-5 N
Logix5000 devices „ 9-5
network
alarm instructions in „ 12-2
planning layout of „ 3-2
network applications „ 2-1, 6-1
M adding Tag Alarm and Event Servers
macros „ 27-1 „ 6-12, 7-7

assigning to FactoryTalk View users „ 5-16 administering at run time „ 17-21

creating „ 27-1 areas in „ 6-2
identifying HMI tag alarms with „ 11-39 adding „ 6-10
login and logout „ 5-15, 27-5 deleting „ 6-10
nesting „ 27-4 home area „ 6-5
On active macro „ 6-18 computer accounts for „ 5-25, 5-26
On standby macro „ 6-18 creating „ 6-9
setting up security for „ 5-17 data servers in „ 6-2
startup and shutdown „ 19-41, 27-5 adding data servers „ 6-12
using parameters in „ 27-3 deleting „ 6-21
using with trends „ 26-22 deploying
maintained push buttons „ 20-11, 20-14 See deploying network applications
math functions „ 23-11 HMI servers in „ 6-2
methods „ 21-25 adding HMI servers „ 6-10
and Invoke command „ 21-25 properties „ 6-14
Microsoft Access „ 25-3 managing multiple „ 4-4
Microsoft Excel parts of „ 6-2
and data logging „ 25-1 referring to components in „ 6-6
and FactoryTalk Diagnostics „ 15-1 renaming „ 6-21
creating HMI tags in „ 10-9 run-time clients for „ 17-16
saving exported text files in „ 13-17 setting up security for „ 5-38
viewing HMI tag alarm logs in „ 11-7 specifying the Network Directory location
working with text strings in „ 13-13 „ 4-4, 4-5

Microsoft SQL Server „ 25-3 structure of „ 6-1

Microsoft Visual Basic network glitch „ 14-32
and DDE communications „ B-2 NextPosition command „ 21-16
viewing HMI tag alarm logs in „ 11-7 Non-Allen-Bradley devices „ 1-9, 8-1, B-2
Modicon devices „ 1-9, 8-1, B-2 Not configured state „ 14-6
modifying grouped objects „ 19-17 Not loaded state „ 14-5
module called ThisDisplay „ 16-4 numeric and string objects „ 20-1
momentary push buttons „ 20-11, 20-13 and electronic signatures „ 20-57
monitoring HMI server status „ 7-9 display objects „ 20-19
moving files numeric displays „ 20-24
for data servers „ 17-15, 18-6 string displays „ 20-24

I–15
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

input objects „ 20-19 OPC-DA data items

and on-screen keyboard „ 20-23 See tags, data server tags
numeric inputs „ 20-25 optimizing duplicate text strings „ 13-15
string inputs „ 20-25 Overlay type graphic displays „ 19-36
selecting using keyboard „ 20-10
numeric embedded variables „ 24-3 P
at run time „ 24-9
panel graphic object „ 20-8
parameter files
O assigning to graphic displays „ 19-31
Object Browser in VBA „ 16-7 pattern colors „ 19-19
object keys „ 21-17 pattern styles „ 19-18
creating „ 21-17 piloted control list selectors „ 20-31, 20-41
key list „ 21-19 placeholders
precedence „ 22-7 See also tag placeholders
running commands with „ 21-20 in commands „ 27-2
object model using in animation „ 21-3
See FactoryTalk View SE Client using in expressions „ 23-5
Object Smart Path „ 21-5 polygon graphic object „ 20-5
objects polyline graphic object „ 20-5
See graphic objects Position command „ 21-16
ODBC data logging precedence
See data logging among key types „ 22-7
ODBC databases and embedded ActiveX objects „ 22-7
for FactoryTalk Diagnostics „ 15-5 and embedded OLE objects „ 22-8
ODBC log tables and the F1 key „ 22-7
data logging „ C-3 general rules „ 22-7
HMI tag alarms „ C-1 shortcut keys „ 22-10
ODBC schemas PrevPosition command „ 21-16
See ODBC storage format PrintDisplay command „ 19-48
ODBC storage format printing „ 2-15
data log files „ 25-1, 25-3 at run time „ 2-16
offline tags „ 9-12, 9-13 selecting a printer „ 2-16
offsetting tag values „ 9-2 Procedure window in VBA „ 16-4
OLE for Process Control procedures in VBA code „ 16-2
See data servers, OPC process faceplates
OLE objects „ 20-2, 20-51 adding to an application „ 19-26
animating verbs „ 21-14 Programmatic ID „ 8-10
setting up security for „ 5-18 Project Explorer in VBA „ 16-4
On active macro „ 14-30 Properties window in VBA „ 16-4
On standby macro „ 6-18, 14-30 Property Panel „ 19-17
On Top type graphic displays „ 19-37 assigning expressions in „ 19-20
online changes „ 14-2 assigning tags in „ 19-20
for HMI tag alarms „ 14-26 using with ActiveX objects „ 21-23
for HMI tags „ 14-23 protecting against system failure
on-screen keyboard „ 19-43, 20-23 See system availability

I–16
 • • • • •
INDEX

push button objects „ 20-1, 20-11 replicating changes „ 17-14

button „ 20-11, 20-12 reserved keys
interlocked „ 20-12, 20-17 See shortcut keys
latched „ 20-12, 20-15 resizing graphic objects „ 19-9

Index
maintained „ 20-11, 20-14 restoring network applications „ 17-9
momentary „ 20-11, 20-13 Rockwell Automation
multistate „ 20-12, 20-16 contacting „ P-4
ramp „ 20-12, 20-18 technical support „ P-4
run-time error state for „ 20-17 web sites „ P-3
selecting using keyboard „ 20-10 Rockwell Automation Device Servers „ 12-6,
12-18
Q See also data servers, RSLinx Enterprise
rotating graphic objects „ 19-15, 21-11
Quick Start
rotation animation „ 21-11
VBA code „ 16-2
rounded rectangle graphic object „ 20-4
RSAssetSecurity
R See FactoryTalk Security
ramp push buttons „ 20-12, 20-18 RSLinx Enterprise
Ready to provide service „ 14-4 See data servers
recipe objects „ 20-31 RSLogix 5000 „ 9-5
recipes „ 20-36 run time
and on-screen keyboard „ 19-43, 20-23 authorizing operations „ 20-55
commands docking displays to client window „ 12-39,
Download „ 20-23 19-45
DownloadAll „ 20-23 font substitution „ 20-7
RecipeRestore „ 20-37 global object displays „ 19-25
RecipeSave „ 20-39 preventing scroll bars „ 19-39
Upload „ 20-23, 20-38 restoring recipes „ 20-36
UploadAll „ 20-23, 20-38 setting up FactoryTalk View SE Clients
index numbers in „ 21-16 for local applications „ 18-7
rectangle graphic object „ 20-4 for network applications „ 17-16
reference objects „ 19-2, 19-24, 20-47 troubleshooting trends „ 26-29
See also global objects updating reference objects „ 19-2
creating „ 20-47 running
linking to base object „ 19-24 FactoryTalk View Studio „ 2-1
linked properties „ 20-48, 21-7 Samples Water client „ 1-12
parameter values for „ 19-33 Runtime Secured Commands editor „ 5-17
updating at run time „ 19-2 Runtime Security
referencing tags „ 9-6 See security codes
relational operators „ 23-7 Runtime Security editor „ 5-11
relative references „ 6-6
in commands „ A-5 S
syntax „ 6-6
Samples Water „ 1-10
to tags „ 9-6
in FactoryTalk View Studio „ 1-11, 2-2
remote access tag „ 20-45
running „ 1-12
Replace type graphic displays „ 19-36

I–17
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

testing „ 1-12 for backing up applications „ 17-4, 18-3

scale graphic object „ 20-29 for creating applications „ 6-9, 7-6
scaling tag values „ 9-2 for deleting applications „ 6-22, 7-10,
ScreenPrint command „ 19-48 8-5
scroll bars for deleting areas „ 6-14
preventing in client window „ 19-39 for deleting HMI servers „ 6-20
SE HMI Tag Alarm Log Viewer „ 11-7 for enabling FactoryTalk alarms „ 12-44
security „ 5-1 for exporting FactoryTalk alarms
See also FactoryTalk Security „ 12-60

built-in functions „ 23-17 for exporting text strings „ 13-10

electronic signatures „ 20-55 for modifying applications „ 6-9, 7-6
for commands „ 20-56 for modifying servers „ 6-19, 7-9, 17-11,
for downloads „ 20-56 17-16
for HMI project components „ 5-9 for renaming applications „ 6-22, 7-10
for system resources „ 5-28, 5-31 for resetting latched alarms „ 12-44
for tag writes „ 20-56 for restoring applications „ 17-9, 18-3
locking users into FactoryTalk View for running FactoryTalk View SE Client
„ 5-20, 17-19, 18-9 „ 17-19, 18-8

logging on at run time „ 17-19, 18-8 for suppressing FactoryTalk alarms

planning „ 3-8 „ 12-44

security codes for writing to tags „ 17-19

for commands and macros „ 5-17 denying an action „ 5-31
for FactoryTalk View commands „ 5-17 explicit permissions „ 5-34
for FactoryTalk View users „ 5-12 for backup and restore operations „ 17-5,
for graphic displays „ 5-18, 19-40 17-10, 18-4
for HMI tags „ 5-20 for switching servers „ 14-20
for macros „ 5-17 inherited permissions „ 5-33
for OLE object verbs „ 5-18 overriding „ 5-34
Unspecified_Command „ 5-17 precedence „ 5-35
security permissions selecting objects „ 19-8
Alarming actions Server Status dialog box „ 6-19, 7-9, 14-3
for acknowledging FactoryTalk alarms SetFocus command „ 19-37
„ 12-44 short file names
for enabling FactoryTalk alarms „ 12-44 for alarm logs „ 11-28
for resetting latched alarms „ 12-44 shortcut menus „ 2-13, 19-8
for suppressing FactoryTalk alarms showing and hiding objects „ 21-8
„ 12-44 Siemens devices „ 1-9, 8-1, B-2
assigning by action „ 5-30 signature button „ 20-55
assigning by user „ 5-30 creating „ 20-57
Common actions „ 5-38 single sign-on „ 5-5
for acknowledging FactoryTalk alarms spacing graphic objects „ 19-13
„ 12-44 special keys
for adding areas „ 6-14 Ctrl „ 20-4, 20-5
for adding device servers „ 12-21 drawing objects with „ 20-6
for adding servers „ 6-14, 7-7, 8-5, PgDn „ 20-37
12-23 PgUp „ 20-38

I–18
 • • • • •
INDEX

precedence „ 22-10 string variables with tags „ 24-6

Shift-Tab „ 21-17 time and date variables „ 24-8
shortcut keys „ 22-8 system availability „ 6-8
Ctrl-PgDn „ 20-22 and non-redundant HMI servers „ 14-6

Index
Ctrl-PgUp „ 20-23 and the Network Directory „ 4-8, 14-8
Enter „ 20-23 application server redundancy „ 6-13, 14-2,
PgDn „ 20-22 14-8, 14-12
PgUp „ 20-23 client and server connections „ 14-31
Tab „ 20-23 features in FactoryTalk View SE „ 3-8,
Tab „ 21-16 14-1
square graphic object „ 20-4 Health Monitoring Policy „ 14-31
stacking graphic objects „ 19-10 HMI server redundancy „ 6-8, 6-16, 14-13,
stand-alone applications 14-14
See local applications copying project files „ 14-14
Standby macro failover to secondary „ 14-21
See On standby macro limits „ 14-11
Standby state „ 14-6 On standby macro „ 6-18
Starting state „ 14-4 replicating changes „ 6-17, 14-16, 17-14
Startup macro „ 27-5 server failure conditions „ 14-21
using with trends „ 26-22 specifying the Network Directory
States toolbar „ 19-17, 19-23 „ 14-13

status tags „ 12-14 specifying the secondary server „ 6-17

string display objects „ 20-24 switchback options „ 14-22
string embedded variables „ 24-5 notifying clients „ 14-22
at run time „ 24-9 synchronizing servers and projects
string input objects „ 20-25 „ 17-14

and electronic signatures „ 20-57 managing data „ 14-29

Suppressed List „ 11-29 for derived tags „ 14-31
suppressing alarms for HMI tag alarms „ 14-29
FactoryTalk alarms „ 12-43 for logging „ 14-30
HMI tag alarms „ 11-10 for running events „ 14-30
symbol indicators „ 20-25, 20-26 monitoring server status „ 6-19, 14-2
symbols „ A-6 for Network Directory server „ 14-7
Define command „ A-6, A-7 network glitches „ 14-32
Undefine command „ A-7 On active macro „ 14-30
Synchronized - ready to be Active „ 14-5 On standby macro „ 14-30
Synchronized - ready to be Standby „ 14-5 online changes „ 14-2, 14-23
Synchronizing with active „ 14-5 to HMI tag alarms „ 14-26
Synchronizing with standby „ 14-5 to HMI tags „ 14-23
syntax OPC server redundancy „ 8-10
checking in expressions „ 23-4 specifying the secondary server „ 8-11
for DDE communications „ B-3 switchback options „ 8-11
for embedded variables planning „ 3-8
numeric variables with numbers „ 24-4 for availability „ 3-8
numeric variables with tags „ 24-4 for redundancy „ 14-9
string variables with strings „ 24-6 RSLinx Enterprise redundancy „ 8-7

I–19
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

specifying the secondary server „ 8-7 as command parameters „ A-6

switchback options „ 8-8 assigning to graphic objects „ 19-20, 20-9
switching Active and Standby „ 14-20 browsing for „ 9-7
system tags „ 10-1, 10-2 offline browsing „ 9-13
for HMI tag alarms „ 11-9 data server tags „ 9-1
setting up „ 9-3
T HMI tags
tab index „ 21-14
See HMI tags
home area „ 9-9
removing „ 20-11
in expressions „ 23-5
tab sequence „ 21-14
with built-in functions „ 23-15
checking index numbers „ 21-15
in graphic objects
creating „ 21-16
updating values continuously „ 20-21
modifying index numbers „ 21-17
limits in graphic displays „ 9-5, 19-1, 20-21
removing objects from „ 20-11
logging values „ 9-5, 25-7
Tag Alarm and Event Servers „ 12-6, 12-21
write values „ 15-4
Tag Browser „ 9-7
properties in tag labels „ 20-32
browsing offline tags „ 9-12
relative references „ 9-6
RSLinx Enterprise „ 9-13
updating values „ 20-22
creating HMI tags in „ 9-12, 10-10
using in editors „ 2-14
displaying tag properties „ 9-10
using in trends „ 26-12
filtering tags „ 9-11
with placeholders in commands „ 27-2, A-2
finding home area „ 9-9
Tags editor „ 11-14
importing PLC tags in „ 9-12
Test Display mode „ 19-23, 21-6, 26-4
modifying HMI tags in „ 9-12
testing graphic displays „ 1-12
removing a filter „ 9-12
text graphic object „ 20-7
showing server names „ 9-9
ThisDisplay module „ 16-4
using wildcards in „ 9-12
time and date
tag functions „ 23-15
displays „ 20-31, 20-33
Tag Import and Export Wizard „ 10-10
embedded variables „ 24-7, 24-9
tag labels „ 20-31, 20-32
time functions „ 23-13
tag placeholders „ 19-29
title bar „ 19-38
assigning to global objects „ 19-32
toolbars „ 2-3, 19-3
creating „ 19-30
hiding and showing „ 2-6
in FactoryTalk View commands „ A-2
States toolbar „ 19-23
in HMI tag alarm summaries „ 11-35
tooltips „ 19-21
replacing at run time „ 11-36
top position tag „ 20-45
using parameter files „ 19-30
touch animation „ 21-13
tag substitution „ 19-21
tracking-related events „ 12-6
tag-based alarms „ 11-2, 12-4
trends „ 26-1
tags „ 9-1
and the Display command „ 26-22
absolute references „ 9-6
as graphic objects „ 20-32
addressing syntax
background color „ 26-13
DDE „ B-3
chart scale „ 26-6
OPC „ 10-8
charts „ 26-5
and object animation „ 21-3
plotting an XY chart „ 26-10

I–20
 • • • • •
INDEX

standard plotting „ 26-10 U

comparing data „ 26-18
Undefine command „ A-7
comparing pens „ 26-15
undefined text strings „ 13-9
creating „ 26-2

Index
ungrouping graphic objects „ 19-16
displaying tag values „ 26-12
Upload command „ 20-23, 20-38
highlighting in a display „ 20-10
UploadAll command „ 20-23, 20-38
in graphic libraries „ 26-21
user accounts „ 5-25
isolated graphing „ 26-11
legends „ 26-7
See also FactoryTalk Security
Administrators group „ 5-23
current value legend „ 26-7, 26-14
authorizing „ 5-1
line legend „ 26-7, 26-15
in FactoryTalk View
x-axis and y-axis „ 26-6
adding „ 5-11
modifying properties „ 26-13
removing „ 5-16
at run time „ 26-23
login and logout macros for „ 5-15, 27-5
overlays „ 26-18
Windows-linked users „ 5-24
adding „ 26-19
at runtime „ 26-28
panning in „ 26-27 V
parts of „ 26-5 value tag „ 20-45
pens „ 26-7 VBA
icons „ 26-7 Help for „ 16-8
markers „ 26-8 VBA code
selecting at run time „ 26-23 planning how to use „ 3-14
shading in „ 26-15 using to animate ActiveX objects „ 21-22
planning „ 3-12 using with ActiveX objects „ 21-25
printing „ 26-28 VBA documentation „ 16-8
running in the background „ 26-22 VBA IDE „ 16-1, 16-3
scrolling „ 26-24 about procedures „ 16-2
shading „ 26-15 Object Browser „ 16-7
snapshots „ 26-18 Procedure window „ 16-4
adding as an overlay „ 26-19 Project Explorer „ 16-4
creating „ 26-19 Properties window „ 16-4
templates „ 26-20 ThisDisplay module „ 16-4
loading „ 26-21 VBA Integrated Development Environment
testing „ 26-4 See VBA IDE
troubleshooting „ 26-29 vertical position animation „ 21-11
using at run time „ 26-22 vertical slider animation „ 21-14
using multiple pens „ 26-11 viewing objects „ 16-7
value bar „ 26-9 visibility animation „ 21-8
delta value bar „ 26-26 visible states tag „ 20-45
x-axis „ 26-6
y-axis „ 26-6 W
zooming „ 26-27
wallpaper „ 19-22
warning messages „ 15-3
wedge graphic object „ 20-6

I–21
• • • • •

FACTORYTALK VIEW SITE EDITION USER’S GUIDE

width animation „ 21-13 creating „ D-1

wildcards exporting „ D-1
filtering tags using „ 9-12 importing „ D-3
in FactoryTalk View commands „ A-2 modifying „ D-2
in HMI tag alarm functions „ 11-12 structure „ D-4
Windows testing „ D-3
regional settings „ 13-2
workgroups „ 4-4 Z
zoom
X in graphic displays „ 19-6
XML files „ D-1 in trends „ 26-27

I–22