Abt-Ccv207-Tsm 2008-05

FactoryTalkr View
SE Programming
Student Manual
Important User Information
This documentation, whether, illustrative, printed, “online” or electronic (hereinafter “Documentation”) is intended for
use only as a learning aid when using Rockwell Automation approved demonstration hardware, software and firmware.
The Documentation should only be used as a learning tool by qualified professionals.
The variety of uses for the hardware, software and firmware (hereinafter “Products”) described in this Documentation,
mandates that those responsible for the application and use of those Products must satisfy themselves that all necessary
steps have been taken to ensure that each application and actual use meets all performance and safety requirements,
including any applicable laws, regulations, codes and standards in addition to any applicable technical documents.
In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter “Rockwell
Automation”) be responsible or liable for any indirect or consequential damages resulting from the use or application of
the Products described in this Documentation. Rockwell Automation does not assume responsibility or liability for
damages of any kind based on the alleged use of, or reliance on, this Documentation.
No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or
software described in the Documentation.
Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:
x properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell
Automation or third--party provided instructions, warnings, recommendations and documentation;
x ensuring that only properly trained personnel use, operate and maintain the Products at all times;
x staying informed of all Product updates and alerts and implementing all updates and fixes; and
x all other factors affecting the Products that are outside of the direct control of Rockwell Automation.
Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell
Automation is prohibited.
Throughout this manual we use the following notes to make you aware of safety considerations:
Identifies information about practices or circumstances

that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property
damage, or economic loss.
Identifies information that is critical for successful

application and understanding of the product.
Identifies information about practices or circumstances

that can lead to personal injury or death, property
damage, or economic loss. Attentions help you:
xidentify a hazard
xavoid a hazard
xrecognize the consequence
Important User Information
Labels may be located on or inside the drive to alert

people that dangerous voltage may be present.
Labels may be located on or inside the drive to alert

people that surfaces may be dangerous temperatures.
Comment Form
Email: ratps@ra.rockwell.com
or Fax: 440.646.4425
Page 1 of
Date:
Contact Information:
Name:
Company and Location:
Phone: Email:
Comments (include lesson title, if applicable):
Course or Product Name (Important):

Page 2
Table of Contents
Introduction
Course Overview
Course Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
Who Should Attend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II
Meeting Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
Student Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
Hands-On Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
Lessons
Introducing FactoryTalk View SE Software

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
FactoryTalk View SE (Site Edition) Software Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
Software Deployment Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--2
FactoryTalk View SE System Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--3
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--4
Exercise: Introducing FactoryTalk View SE Software

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--9
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--9
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--10
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--10
Configuring FactoryTalk Services For FactoryTalk View Applications

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
FactoryTalk Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--2
Setting Up the FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--2
FactoryTalk Local Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--2
FactoryTalk Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--4
Installing FactoryTalk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--5
Installing the Local Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--5
Installing the Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--5
Creating User and User Group Accounts in FactoryTalk Security . . . . . . . . . . . . . . . . . . . . . . . . 2--6
Windows-Linked User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--6
ii Table of Contents
Creating Applications and Adding Areas and Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--8

Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--8
Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--9
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--9
OPC Data Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--10
Rockwell Automation Device Servers (RSLinx Enterprise) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--10
Setting Up Communications with RSLinx Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--11
Monitoring Live Data Using the Rockwell Software Data Client . . . . . . . . . . . . . . . . . . . . . . . . . . 2--12
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--15
Exercise: Configuring FactoryTalk Services For FactoryTalk View Applications

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--17
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--18
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--20
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--20
Creating a FactoryTalk View SE Application and Configuring Communications

Using an RSLinx Enterprise Device Server
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1
Creating a FactoryTalk View SE Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1
FactoryTalk View Studio Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
Configuring Communications Using an RSLinx Enterprise Device Server . . . . . . . . . . . . . . . . . . 3--3
Adding an RSLinx Enterprise Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--3
Adding Device Shortcuts for RSLinx Enterprise Communications . . . . . . . . . . . . . . . . . . . . . . 3--4
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--5
Exercise: Creating a FactoryTalk View SE Application and Configuring Communications

Using an RSLinx Enterprise Device Server
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--8
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--10
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--10
Configuring OPC Communications in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1
Understanding RSLinx Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--2
Configuring Communications Using an RSLinx OPC Data Server . . . . . . . . . . . . . . . . . . . . . . . . 4--2
Configuring a Communications Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--2
Creating an OPC Topic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--3
Table of Contents iii
Locating HMI Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--4

Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--4
Exercise: Configuring OPC Communications in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--5
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--6
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--8
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--8
Creating an HMI Tag Database in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1
Creating an HMI Tag Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--2
Creating HMI Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--3
Tag Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--3
Importing and Exporting an HMI Tag Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--4
Creating and Modifying HMI Tags and Folders Using Microsoft Excel Software . . . . . . . . . . . . . . 5--5
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--6
Exercise: Creating an HMI Tag Database in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--9
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--10
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--10
Creating a Graphic Display in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1
Graphic Display Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1
Adding a Graphic Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
Graphic Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
Behavior Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--3
Grid Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--4
Creating and Manipulating Graphic Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--4
Creating Graphic Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--5
Objects Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--5
Objects Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--6
Manipulating Basic Graphic Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--6
iv Table of Contents
Adding Images to an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--8

Adding Images to a Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--8
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--9
Exercise: Creating a Graphic Display in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--11
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--13
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--14
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--14
Building an Interactive Graphic Display in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--1
Adding Objects From a Graphics Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--2
Available Graphics Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--2
Adding Interactive Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--2
Push Button Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--3
Button Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--4
Other Push Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--6
Gauge and Graph Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--9
Configuring Push Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--10
Using the Expression Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--11
Creating a Local Message File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--13
Trigger Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--13
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--13
Local Message Display Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--13
Testing a FactoryTalk View SE Graphic Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--14
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--14
Exercise: Building an Interactive Graphic Display in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--15
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--22
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--24
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--24
Animating a Graphic Display in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--1
Adding an Existing Graphic Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--1
Animating Graphic Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--1
Table of Contents v
Creating an Expression within an Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--4

Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--5
Exercise: Animating a Graphic Display in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--11
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--12
Using Tag Placeholders and Creating a FactoryTalk View SE Client

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--1
Adding Tag Placeholders to a Graphic Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--1
Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--2
Tag Substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--2
Displaying Placeholder Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--2
Creating a FactoryTalk View SE Client Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--3
Running a FactoryTalk View SE Client Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--4
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--4
Exercise: Using Tag Placeholders and Creating a FactoryTalk View SE Client

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--5
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--6
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--8
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--8
Configuring Global Objects in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--1
Global Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--1
Global Object Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--2
Global Object Display Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--2
Global Object Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--3
Global Object Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--3
Configuring Global Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--4
Updating Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--5
Broken Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--5
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--6
vi Table of Contents
Exercise: Configuring Global Objects in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--10
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--12
Switching Languages in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--1
Adding Languages to an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--1
Application Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--1
Adding Languages to an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--2
Switching the Current Application Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--2
Importing and Exporting Text Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--3
Importing Text Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--3
Exporting Text Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--4
Exporting a Single Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--4
Exporting Multiple Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--5
Modifying Application Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--5
Modifying Text Strings Exported to an Excel Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--5
Modifying Text Strings Exported to a Unicode Text File in Notepad . . . . . . . . . . . . . . . . . . . . . 11--6
Using Language Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--8
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--9
Exercise: Switching Languages in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--11
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--14
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--16
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--16
Configuring Alarms in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--1
Creating HMI Tags in a FactoryTalk View SE Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--2
Tag Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--2
Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--2
Configuring Alarms for HMI Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--3
Configuring the HMI Tag Alarm Setup Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--4
Creating or Modifying an HMI Tag Alarm Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--5
Acknowledging Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--6
FactoryTalk Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--7
FactoryTalk Alarms and Events Graphic Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--9
Table of Contents vii
Enabling FactoryTalk Alarms and Events on an RSLinx Enterprise Device Server . . . . . . . . . . . . 12--11
Creating or Modifying a FactoryTalk Alarms and Events Summary . . . . . . . . . . . . . . . . . . . . . . . 12--12
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--15
Exercise: Configuring Alarms in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--17
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--20
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--20
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--21
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--22
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--22
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--25
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--25
Creating and Viewing a Data Log Model in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--1
Creating or Modifying a Data Log Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--2
Selecting the ODBC Database Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--2
Selecting the File Set Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--4
Selecting Tags to Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--5
Viewing a Data Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--5
Naming Log File Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--5
Naming ODBC Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--6
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--7
Exercise: Creating and Viewing a Data Log Model in a FactoryTalk View SE Application
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--9
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--10
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--11
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--14
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--14
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--16
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--16
Creating and Configuring a Trend in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--1
Creating a Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--2
Configuring a Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--2
viii Table of Contents
Overlaying Data Snapshots on a Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--3

Creating a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--3
Creating an Overlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--4
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--5
Exercise: Creating and Configuring a Trend in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--8
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--10
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--10
Creating a Derived Tag File and an Event File in a FactoryTalk View SE Application
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--1
Creating a Derived Tag File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--2
Creating a Derived Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--2
Starting and Stopping a Derived Tag File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--3
Creating an Event File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--4
Creating an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--4
Starting and Stopping Event Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--5
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--6
Exercise: Creating a Derived Tag File and an Event File in a FactoryTalk View SE
Application
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--10
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--12
Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--1
Creating Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--1
Clearing a Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--2
Creating Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--2
Macro Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--2
Running Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--3
Creating Key Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--3
Object Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--4
Display Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--4
Table of Contents ix
Client Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--5

Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--5
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--6
Exercise: Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--10
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--12
Configuring Security in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--1
Creating a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--1
FactoryTalk User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--1
Adding a New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--2
Creating a User Group Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--2
FactoryTalk User Group Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--2
Creating a New Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--4
Specifying User Security Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--5
Assigning Security Codes to Graphic Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--5
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--6
Exercise: Configuring Security in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--10
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--12
Creating VBA Display Code in a FactoryTalk View SE Application

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--1
Adding VBA Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--1
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--3
Exercise: Creating VBA Display Code in a FactoryTalk View SE Application

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--5
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--10
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--12
x Table of Contents
Course Overview I
Course Overview
Course Purpose This course is a skill-building course that will aid you in developing
FactoryTalk View Supervisory Edition (SE) applications.
This course provides opportunities for you to work with local

FactoryTalk View SE applications. During class, you will have the
opportunity to practice the skills used to create an application and
build graphic displays. You will learn how to configure alarms and
security, trend data, and test your application using FactoryTalk View
SE Client.
You will also work with RSLinx Enterprise communications

software and the FactoryTalk Diagnostics system.
Who Should Attend Individuals who need to develop FactoryTalk View SE local or
network applications should attend this course.
Prerequisites To successfully complete this course, experience operating a

personal computer within a Microsoft Windows 2000 or
Windows XP environment is recommended.
Rev. May 2008 E 2008 Rockwell Automation, Inc. All rights reserved.
ovrsb9701SE
II Course Overview
Agenda This course consists of the following lessons:

Day 1
Course Overview
Introducing FactoryTalk View Supervisory Edition
Configuring FactoryTalk Servcies for FactoryTalk View
Applications
Creating a FactoryTalk View SE Application and Configuring
Communications Using an RSLinx Enterprise Device Server
Configuring OPC Communications
x Creating an HMI Tag Database
Day 2
Creating a Graphic Display
Building an Interactive Graphic Display
x Animating a Graphic Display
Day 3
Using Tag Placeholders and Creating a FactoryTalk View SE
Client
Configuring Global Objects
Switching Languages
x Configuring Alarms
Day 4
Creating and Viewing a Data Log Model
Creating and Configuring a Trend
Creating a Derived Tag File and an Event File
x Creating Symbols, Macros, and Keys
Day 5
Configuring Security
x Adding VBA Display Code
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. May 2008
ovrsb9701SE
Course Overview III
Meeting Course Objectives The following course structure is generally used to help you
understand the content and activities:
One lesson is devoted to each task.
Typical lesson includes most or all of these sections:
-- “What You Will Learn” -- lesson objectives
-- “Before You Begin” -- preparatory material
-- “Here’s How” -- demonstration of procedures
-- “Exercise” -- opportunity to perform new skills, often in a
hands-on lab environment
-- “How Did You Do?” -- where to go for feedback on
performance
-- “Answers” -- answers to exercises
x Integrated practices provide an opportunity to perform tasks using
the skills obtained during the training.
Student Materials To enhance and facilitate your learning experience, the following
materials are provided as part of the course package:
Student Manual, which contains the topical outlines and
exercises. Use this manual to follow presentations, take notes, and
work through your exercises.
x FactoryTalk View SE Procedures Guide, which provides all the
steps required to complete common FactoryTalk View SE
application development tasks, including the tasks in the
exercises. By following the procedures in this job aid, you can
immediately apply what is learned in the course to your own job.
Hands-On Exercises Throughout the course, you will have the opportunity to practice the
skills you have learned through a variety of hands-on exercises.
These exercises focus on the skills introduced in each lesson.
ovrsb9701SE
IV Course Overview
ovrsb9701SE
Lesson 1
Introducing FactoryTalk View SE
Software
What You Will Learn After completing this lesson, you should be able to understand
FactoryTalk View SE software capabilities.
Why These Skills Are Important
These skills are important for HMI (Human Machine Interface)

development.
Before You Begin FactoryTalk View SE (Site Edition) Software Capabilities
If students ask, mention that the version FactoryTalk View SE software is a part of the FactoryTalk View
of FactoryTalk View Studio that installs Enterprise Series family of products which provide a common HMI
with FactoryTalk View SE can create
both FactoryTalk View SE and solution for machine-level and supervisory-level applications:
FactoryTalk View ME applications. The
FactoryTalk View Studio that installs with
FactoryTalk View ME software can only
create FactoryTalk View ME
applications.
ISEsb9701SE
1--2 Introducing FactoryTalk View SE Software
Software Deployment Options

The software provides a flexible architecture for the following types
of applications:
Explain to students that this architecture x Local (Stand-alone) Applications: FactoryTalk View SE
is similar to RSView32 or similar software components are installed on one computer. If needed,
competitive HMI offerings.
additional data servers can send data to the computer hosting the
stand-alone application:
Optional Data
Server Local Application,
HMI Client, HMI Server,
and Data Server
ControlLogix PLC-5 Third-Party SLC 500

Controller Processor OPC Server Processor
Mention that the majority of the skills x Network (Distributed) Applications: FactoryTalk View SE
practiced in this class will be performed software components are spread out among multiple servers and
in a local environment. Students who are
working with network applications should client computers:
be encouraged to attend the FactoryTalk
View SE Architecture class (Course no. FactoryTalk View SE FactoryTalk View FactoryTalk View Studio
CCV205). Clients SE Servers Software
ControlLogix PLC-5 Third-Party SLC 500

Controller Processor OPC Server Processor
ISEsb9701SE
Introducing FactoryTalk View SE Software 1--3
Remind students that local applications Network applications include the following software components
can only have one HMI server. that do not apply to local applications:
x Additional HMI Servers: For improved application
performance, network applications can contain multiple HMI
servers. Each HMI server in the application requires a separate
software license.
x Areas: Areas are logical divisions of a FactoryTalk View SE
application created by a developer that help organize the HMI
projects. For example, a bakery might be divided into the
following areas:
-- Ingredients
-- Mixing
-- Baking
-- Packaging
FactoryTalk View SE System Limits

To set up a FactoryTalk View SE HMI system successfully, observe
these limits:
x The maximum number of FactoryTalk View Studio clients that
can have simultaneous access to a FactoryTalk View SE
application is 5.
x The maximum number of HMI servers supported in an
application is 10. Each of these can be redundant.
x The maximum number of FactoryTalk View SE Clients that can
have simultaneous access to a FactoryTalk View SE application is
50.
Mention that redundancy is not typically x In non-redundant scenarios, the maximum number of HMI
covered in a standard class. Refer servers that can be hosted on a single computer is 2.
students to the online Help system for
more information. x In redundant scenarios, the maximum number of HMI servers
that can be hosted on a single computer is 1.
ISEsb9701SE
Example FactoryTalk View SE Application
Open the InstaCorp.txt for setup InstaCorp produces soap dispensers and refills. This example will
instructions in order to demonstrate the show you some screens that have been developed for their
Ssoap_Local.apa application to
students. application.
Show students features of SE that relate
to their needs.
Note: This application was originally a
distributed (network) application and
may now have limited features and
functionality.
For your convenience and the students, InstaCorp home screen:
some screen shots have been provided.
ISEsb9701SE
InstaCorp production overview:
InstaCorp dispenser line, Filling:
ISEsb9701SE
InstaCorp dispenser line, Capping:
InstaCorp dispenser line, Labelling:
ISEsb9701SE
InstaCorp dispensing line, Packing:
InstaCorp Alarm Summary:
ISEsb9701SE
ISEsb9701SE
Exercise: Introducing FactoryTalk View SE Software 1--9
Exercise: Introducing FactoryTalk

View SE Software
Exercise A In this exercise, you will familiarize yourself with FactoryTalk View
SE software.
Context:
In order to begin development, you must understand the capabilities

of FactoryTalk View SE software.
Directions:
Answer the following questions:
1. What does the abbreviation HMI stand for?
2. What two applications does FactoryTalk View SE provide

architecture for?
3. What is an area?
4. True or False: A local application can have multiple HMI servers.
5. What is the maximum number of FactoryTalk View SE Clients

that can have simultaneous access to a FactoryTalk View SE
application?
How Did You Do? Turn to the Answers section.
ISEe9701SE
1--10 Exercise: Introducing FactoryTalk View SE Software
Answers Exercise A
1. HMI is an abbreviation for Human Machine Interface.

2. FactoryTalk View SE provides architecture for Local
(Stand-alone) and Network (Distributed) Applications.
3. Areas are logical divisions of a FactoryTalk View SE
application.
4. False. A local application can only have one HMI server.
5. The maximum number of FactoryTalk View SE Clients that
can have simultaneous access to a FactoryTalk View SE
application is 50.
ISEe9701SE
Lesson 2
Configuring FactoryTalk Services
For FactoryTalk View Applications
What You Will Learn After completing this lesson, you should be able to:
x Set up the FactoryTalk Directory
x Create user and user group accounts in FactoryTalk Security
x Create applications and add areas and servers
x Monitor FactoryTalk Live Data using the Rockwell Software
Data Client
These skills are important for the following reasons:

x Configuring the FactoryTalk Directory helps manage
applications.
x Setting up FactoryTalk Security will help limit access to users
that are assigned permissions in FactoryTalk.
x Creating applications and areas allow you to organize project
information and make it available to all computers participating
in the system.
x Monitoring FactoryTalk Live Data through the Rockwell
Software Data Client will allow you to remotely view tags from
different controllers.
Before You Begin Key Terms
Data Servers: Provide tags contained in OPC-DA (OLE for Process

Control Data Access) servers.
OLE: Object Linking and Embedding
Shortcut: A name that stands for the device you want to connect to
and the data that device contains.
Windows-linked accounts: FactoryTalk Security accounts that are

based on existing Windows users, or groups of Windows users.
COMsb9701SE
2--2 Configuring FactoryTalk Services For FactoryTalk View Applications
FactoryTalk Overview
A FactoryTalk system is comprised of software products, services,

and hardware devices participating together and sharing the same
FactoryTalk Directory and FactoryTalk services.
FactoryTalk View consists of several components:

x Hardware: Controllers
x Software: FactoryTalk View software
x Services: FactoryTalk Services
Setting Up the FactoryTalk Directory
For example, to access graphic displays FactoryTalk Directory is software that allows the parts of an
on an HMI server in the application, HMI application to find each other on a computer, or on the network.
clients use FactoryTalk Directory
software to find out which computer on
the network is hosting the HMI server. FactoryTalk Directory software also stores the information about
which users and computers are allowed access to the various parts of
a control system if you have used FactoryTalk Security, to secure
access to the resources that FactoryTalk Directory manages.
Tip " The FactoryTalk Directory server must not be installed on the same
computer as the domain controller for the network.
The FactoryTalk Services Platform installs and configures as many

as two completely separate and independent directories: local and
network directories.
FactoryTalk Local Directory

Create a FactoryTalk system that suits the needs of your facility.
COMsb9701SE
Configuring FactoryTalk Services For FactoryTalk View Applications 2--3
This course will use a similar For example, the following software could be communicating with a
configuration, except RSLogix 5 will be single programmable logic controller and participating in the same
replaced with RSLogix 5000.
Local Application held in a Local Directory:
x FactoryTalk Services Platform
x FactoryTalk View
x RSLinx Classic
x RSLogix 5
In a FactoryTalk Local Directory:

x Project information and security settings are located on a single
computer.
x The FactoryTalk system cannot be shared across a network or
from the Network Directory on the same computer.
x Products such as FactoryTalk View SE Local and FactoryTalk
View ME use the Local Directory.
COMsb9701SE
FactoryTalk Network Directory

This course does not discuss Network A FactoryTalk system may be much more complex, with software
applications. For more information products and hardware devices participating in multiple Network
regarding distributed applications, see
FactoryTalk View Site Edition Applications distributed across a network, all sharing the same
Architecture, course no. CCV205 Network Directory and FactoryTalk services.
In a FactoryTalk Network Directory:

x Project information and security settings from multiple
FactoryTalk products across multiple computers on a network can
be organized.
x Products such as FactoryTalk View SE and FactoryTalk
Transaction Manager use the Network Directory.
For example, the FactoryTalk View SE In a network system, if FactoryTalk Directory becomes unavailable
client will be able to read and write while an application is running, the application will continue to run
values, acknowledge alarms, and open
and close displays because a copy of correctly.
the information provided by FactoryTalk
Directory is stored locally on each However, while FactoryTalk Directory is unavailable, you cannot
computer that is connected to the
FactoryTalk Directory computer. modify an application’s structure; for example, you cannot add or
edit an area, a data server, or an HMI server.
Tip " All the computers participating in a distributed application share a

common FactoryTalk Directory located on a network computer.
COMsb9701SE
Installing FactoryTalk
During FactoryTalk installation, the first screen of the installation

process asks you to select the type of directory you want to install.
Select the Directory

you want to configure
FactoryTalk Security authenticates user identities and authorizes user

requests for access to a FactoryTalk-enabled system. These security
services are integrated into the FactoryTalk Directory and are
included as part of the FactoryTalk Services Platform.
Installing the Local Directory

If you are installing FactoryTalk Services Platform version 2.10
(CPR 9) and FactoryTalk View Site Edition on a computer for the
first time, all users will have full access to the directory and to
FactoryTalk View in the FactoryTalk Local Directory.
If you are upgrading an existing FactoryTalk system with

FactoryTalk Services Platform and FactoryTalk View Site Edition,
previously configured security will continue to be in effect.
Installing the Network Directory

If you are installing FactoryTalk Services Platform version 2.10
(CPR 9) and FactoryTalk View Site Edition on a computer for the
first time, all users that are members of the Windows Administrator
group on any local computer connected to the FactoryTalk Network
Directory, will have full access to the directory and to FactoryTalk
View in the FactoryTalk Directory Network.
COMsb9701SE
To restrict access to the FactoryTalk system for selected users and

computers, you need to remove the All Users account, create
FactoryTalk security accounts for the users and computers you want
to secure, and then give users the appropriate security permissions.
Creating User and User Group Accounts in FactoryTalk Security
If this is part of a standard course, more If you are using FactoryTalk Security to secure the FactoryTalk
information on how to create users and Directory, the application and its areas, users, computers, and
groups will be presented in another
lesson. devices, you should set up group accounts before creating individual
user accounts.
All users within a particular group inherit the security permissions

set up for the group. This makes it easier to assign and manage
permissions for multiple users with similar security needs. If you
change any of the permissions for the group, all members inherit the
changes.
Windows-Linked User Accounts

When a Windows-linked user attempts to log in, authentication of
the user name and password is performed by Windows via
FactoryTalk Security.
Select your
Windows-linked user
account
Double Click
Administrators
Click Add Select ’Show

Users Ony’
COMsb9701SE
With Windows-linked accounts, when the user logs into Windows,

they are automatically logged into the FactoryTalk Directory, as well.
For example, where the control system This type of security account can be useful when the security needs
is located on a dedicated domain. of the Windows network match those of the control system.
You can change the password for a Windows-linked account when

you log into FactoryTalk Directory in the same way that you would
change a FactoryTalk Security password.
Security permissions and policies for user and user group accounts
are set up in FactoryTalk Security and managed by FactoryTalk
Directory.
Tip " You can add individual Windows-linked user accounts to a user
group that was created in FactoryTalk Security.
Tip " You can also add a Windows-linked user group to a user group that
was created in FactoryTalk Security.
Tip " You cannot add a user account that was created in FactoryTalk
Security, to a Windows-linked user group.
COMsb9701SE
Creating Applications and Adding Areas and Servers
Applications
If this is part of a standard course, more A FactoryTalk application organizes elements such as data servers,
information on how to create alarm and event servers, HMI servers, and project information.
applications, areas, and servers will be
presented in another lesson.
It makes all of that information available to all software products and
computers participating in the same application:
Create a new application
FactoryTalk View Site Edition applications can be:

x Network (Distributed): The software programs that allow the
application to run can be distributed across a network on different
computers.
-- These programs include, for example, FactoryTalk
Directory, the FactoryTalk View SE Server software that
the HMI server requires, the FactoryTalk View SE Client,
OPC data servers, and so on.
x Local (Stand-Alone): All software programs are located on a
single computer, there can only be one HMI server, and there are
no areas.
COMsb9701SE
Areas
Areas organize and subdivide applications that use a Network
Directory into logical or physical divisions.
You can create an area

within your existing
application.
The root of an application can contain only one HMI server. To add
additional HMI servers to an application, create a separate area for
each server.
Each area can contain only one HMI server.
Areas are not available in a local directory.
Servers
For example, some of the values that A data server provides a route to the physical devices on a network
data servers provide access to are so you can access the values in those devices.
programmable controller values, OPC
tags and their value or status
information, and tags in a Logix5000
processor.
COMsb9701SE
In FactoryTalk View SE then you can create:

x An RSLinx Enterprise device server
x An OPC data server
x Tag Alarm and Event Server
Right-Click on
your Application
to add a sever.
OPC Data Servers

FactoryTalk Transaction Manager was Clients that need access to tags, such as FactoryTalk View SE and
formerly known as RSSql software. FactoryTalk Transaction Manager, use FactoryTalk Directory to
locate the computers that are hosting OPC-DA 2.0-compliant data
servers.
Data server information is stored as part of an application. Adding a

data server to an application or an area provides a link between a
hardware device containing tags (via the OPC server’s defined
topics) and the FactoryTalk Directory
Rockwell Automation Device Servers (RSLinx Enterprise)

RSLinx Enterprise is a FactoryTalk Live Data server and
device-based alarm and event server. It enables you to see values,
such as sensor readings and other controller data from plant floor
devices, from an application.
RSLinx Enterprise is a FactoryTalk Live Data

server, not an OPC server.
COMsb9701SE
Setting Up Communications with RSLinx Enterprise

Applications use a configuration file to communicate with devices on
the network. This file contains at least one shortcut and can be
configured in the Communication Setup editor:
Set up RSLinx Enterprise

communications
The shortcut is associated with a communication path to tell the

application where to find that data. Associate the device shortcut
with a processor:
Create your Shortcut
Point your shortcut to

the correct Processor
COMsb9701SE
For FactoryTalk View Site Edition (SE) applications, the primary

path originates from the workstation where the FactoryTalk View
runtime application is running and terminates at the control device.
The secondary path originates from the workstation where the

FactoryTalk View runtime application is running and terminates at
the secondary (redundant) control device.
Do not change the target device associated with a

device shortcut if RSLinx Enterprise is being used
by a runtime client. The shortcut will no longer
point to the device expected by the runtime client.
Inappropriate data and unexpected behavior may
result.
Tip " If you restore a FactoryTalk Directory, you must manually review
and verify the configuration to ensure that shortcuts contained in that
directory or application file point to the intended physical devices.
Monitoring Live Data Using the Rockwell Software Data Client
The Rockwell Software Data Client can be used as a tool to:

x Monitor data between FactoryTalk data servers or OPC data
servers.
x Group data items together in order to test the communications
network by enabling or disabling individual data items or groups
of data items.
The FactoryTalk Data Client is compatible for both network and
local directories:
COMsb9701SE
Select the appropriate initial connection:

If you want to . . . Then select . . .
Connect to RSLinx Classic Connect OPC Server
Connect to RSLinx Enterprise FactoryTalk
Load a configuration file containing data
Load Config File
items from an OPC server
Tip " When connecting to RSLinx Classic, select RSLinx Remote OPC
Server because this provides the most reliable connection.
After you open your application, create a group to which you can
then add data items:
Data items can be:

x Active: Use this to update data items in a group.
x Inactive: Use this to to prevent data items from being updated.
Explain to students that emulation mode Use HMI Emulation Mode to switch among groups of data items to
simulates the activity of an HMI simulate the activity of an HMI system that is switching among
application that is changing graphic
displays, by using groups to activate and graphic displays.
deactivate several data items at once.
COMsb9701SE
Monitor data points from your application by selecting them on the

Add Item dialog box:
Add Items
Data
Points
View the current quality and current value of the data point to ensure
good health:
COMsb9701SE
Here’s How To performing the following tasks:

1. Install FactoryTalk and set up the x Set up the FactoryTalk Directory
local and network FactoryTalk
Directories. x Create user and user group accounts in FactoryTalk Security
2. Create an application. x Create applications and add areas and servers
3. Add an RSLinx Enterprise device x Monitor FactoryTalk Live Data using the Rockwell Software
server. Data Client
4. Create a shortcut that points to your
controller.
5. Create a new group.
6. Add a new user to the group.
7. Open the Rockwell Software Data
Client and monitor diagnostic tags.
COMsb9701SE
COMsb9701SE
Exercise: Configuring FactoryTalk Services For FactoryTalk View Applications 2--17
Exercise: Configuring FactoryTalk

Services For FactoryTalk View
Applications
Exercise A In this exercise, you will practice configuring FactoryTalk Services

for FactoryTalk View Applications
Context:
Before you create a FactoryTalk View application, you need to

configure FactoryTalk Services for the network and local directory.
When you see underlined text, refer to the related procedure or

information in your job aid.
Directions:
1. Open the FactoryTalk Administration Console.
Tip " As part of the installation, Windows administrators will already be

added to the Administrators group of FactoryTalk. This allows you to
log in to FactoryTalk Administration Console.
2. Configure the FactoryTalk Network directory.

3. Click Tools and then FactoryTalk Directory Server Options.
4. Verify that the computer hosting the FactoryTalk directory server
says Localhost.
5. Create a new user in the network directory by assigning
administrator as the username and administrator as the
password.
6. Configure the password to so it will never expire.
7. Add the user, administrator, to the FactoryTalk Administrators
group.
8. Log out of the FactoryTalk Administration Console and log back
in to the network directory as administrator.
9. Create a new application named Data Testing.
10. Add a new area named Data Testing Area to Data Testing.
11. Add an RSLinx Enterprise Device Server to Data Testing Area.
12. Double-click the Communications Setup editor for RSLinx
Enterprise.
COMe9701SE
2--18 Exercise: Configuring FactoryTalk Services For FactoryTalk View Applications
13. Create a new shortcut named Shortcut that points to your

controller.
14. Click Verify.
15. Click OK.
16. Close and re-open the FactoryTalk Administration Console.
17. Configure the FactoryTalk Local directory.
18. Create a new user in the local directory by assigning
administrator as the username and administrator as the
password.
19. Configure the password to so it will never expire.
20. Add the user, administrator, to the FactoryTalk Administrators
group.
21. Open the Rockwell Software Data Client software.
22. Select the Network directory.
23. Select the FactoryTalk connection.
24. Select the shortcut you created and then Diagnostic Items.
25. Monitor FactoryTalk Live Data using the Data Testing
application.
26. Close the FactoryTalk Data Client software.
27. Delete the Data Testing application.
28. Close the FactoryTalk Administration Console.
COMe9701SE
COMe9701SE
Answers Exercise A
2. Go to Start>Programs>Rockwell Software> FactoryTalk

Administration Console and select Network for your
directory.
4. Your FactoryTalk Directory Server Location should appear

similar to the following:
COMe9701SE
5. Right-click Users>New and then select Users:
7. Add a member to the group by selecting the Group Membership

tab:
Select the Group
Add User to a Group
COMe9701SE
9. When you create a new application, you should see the

following graphic:
10. When you create your new area, you should see the following
graphic:
11. When you add your new data server, you should see the
following graphic:
Data Server
COMe9701SE
13. When you create your new device shortcut, you should see the
following graphic:
Shortcut
Path to
Controller
24. Add a diagnostic item:
Add items
Your shortcut
25. Monitor data:
COMe9701SE
COMe9701SE
Lesson 3
Creating a FactoryTalk View SE
Application and Configuring
Communications
Using an RSLinx Enterprise Device
Server
x Create a FactoryTalk View SE application
x Configure communications using an RSLinx Enterprise Device
Server by performing the following tasks:
-- Add an RSLinx Enterprise driver
-- Add device shortcuts for RSLinx Enterprise communications

x Creating a new local application is the first step in the application
development process.
x Creating and configuring a connection to a device server provides
a way to transfer data throughout the application.
Before You Begin Creating a FactoryTalk View SE Application
Tell students that the Product Type The FactoryTalk View Studio development environment is used to
Selection screen includes an option for create, open, build, and modify FactoryTalk View SE applications.
creating a machine-level application
using FactoryTalk View ME software. If
they are interested in learning more When you first open FactoryTalk View Studio, you are prompted to
about that particular software, refer them choose the type of application you are working with:
to the FactoryTalk View ME and
PanelView Plus Programming course
(Course No. CCV204) or the three-part
RSTrainer for FactoryTalk View ME
computer-based training course.
APPsb9701SE
3--2 Creating a FactoryTalk View SE Application and Configuring Communications
Tip " Once FactoryTalk View Studio software is open, you can switch
between product types (Network, Local, or FactoryTalk View ME)
from the File menu, by selecting Select Product Type...
FactoryTalk View Studio Software Components
After creating a new application or opening an existing application,

the main software screen is displayed:
Standard Graphics
Toolbar Toolbar
Object Toolbar
Application
Explorer
Window
Graphic
Display
Display
Window
Status Diagnostics
Bar List
Explain that the placement of the The main software screen can display the following components:
toolbars, the Application Explorer, and
other components can be configured by x Application Explorer Window: Provides access to the
the user. components of the open application.
x Diagnostics List: Displays information gathered by the
FactoryTalk Diagnostics module of the software.
x Display Window: Presents a work space for components selected
from the Application Explorer window.
x Graphic Display: Provides space for users to design application
screens.
x Status Bar: Displays information about selected items.
APPsb9701SE
Creating a FactoryTalk View SE Application and Configuring Communications 3--3
Configuring Communications Using an RSLinx Enterprise Device

Server
RSLinx Enterprise is a device server that links networks and devices

to Microsoft Windows 2000--, XP--, and CE--based applications. It
provides communication services between applications and devices
on the plant floor. Using a Windows computer, you can then see
values from your plant floor devices such as sensor readings and
other programmable logic controller (PLC) data.
Adding an RSLinx Enterprise Driver

1. In order to communicate to your controller, you must first add an
RSLinx Enterprise Device Server:
2. After your RSLinx Enterprise Server has been created, you can
configure your communication setup:
In the Communication Setup editor, you can:

Refer students to the RSLinx Enterprise x Add drivers
Getting Results Guide for more
information. x Add devices
x Create shortcuts
APPsb9701SE
Adding Device Shortcuts for RSLinx Enterprise

Communications
In RSLinx Enterprise, a device shortcut represents a specific path to
a processor (similar to DDE and OPC topics in RSLinx Classic). In
other words, they provide a mapping between a user-defined name
and a target device and have the following properties:
x Device shortcuts are stored on a per FactoryTalk application basis
versus being associated with the RSLinx Enterprise server itself.
x Each application can have its own set of device shortcuts for a
particular server. Therefore, even if you are using the same
computer to create multiple applications, each application must
have its own set of shortcuts defined.
x Shortcuts are not copied over from one application to another.
Device Shortcut
Target Device
APPsb9701SE
Creating a FactoryTalk View SE Application and Configuring Communications 3--5
Here’s How To perform the following tasks:

Demonstrate the following tasks: x Create a FactoryTalk View SE application
1. Open FactoryTalk View Studio x Configure communications using an RSLinx Enterprise Device
software.
Server by performing the following tasks:
2. Select a Local application.
-- Add an RSLinx Enterprise driver
3. Point out how you would create a -- Add device shortcuts for RSLinx Enterprise communications
new application.
As your instructor demonstrates these procedures, follow along in
4. Open the existing
CCV207_9701SE_DEM1.APA the associated job aid(s).
application file.
5. Point out some of the toolbars. If this
is a standard school, mention that
the use of these toolbars will be
covered in future lessons.
6. Add an RSLinx Enterprise device
server and rename it.
7. Create a shortcut and name it
LinxE_Shortcut..
8. Verify that your shortcut appears on
the left side of the window and that
its target points to your controller.
9. Close the application.
APPsb9701SE
APPsb9701SE
Exercise: Creating a FactoryTalk View SE Application and Configuring Communications 3--7
Exercise: Creating a FactoryTalk

View SE Application and
Configuring Communications
Using an RSLinx Enterprise Device
Server
Exercise A In this exercise, you will practice creating a local FactoryTalk View
SE (Site Edition) application and configuring communications using
RSLinx Enterprise.
Context:
Before you can create graphic objects that display data from a
processor or controller, you need to establish communications using
an RSLinx Enterprise data server.

Directions:
1. Open FactoryTalk View Studio.

2. If you want to view an application that is both stored and run on
the same computer, which type of FactoryTalk View Studio
application should you select?
3. Select the application type you identified in Question 2.

4. Create a new FactoryTalk View SE application named AppliSE.
5. Examine the Application Explorer and familiarize yourself with
the available application components. How many HMI servers
and areas does the application contain?
6. Add an RSLinx Enterprise device server to the application.

7. Double-click Communication Setup and expand the 1789-A17
backplane to view your processor.
8. Add a device shortcut named LinxE_Shortcut that points to the
controller running the CCV207_CLXProgram.acd or
CCV207_SoftProgram.acd file.
9. Minimize or close your FactoryTalk View SE application.
APPe9701SE
3--8 Exercise: Creating a FactoryTalk View SE Application and Configuring Communications
APPe9701SE
Exercise: Creating a FactoryTalk View SE Application and Configuring Communications 3--9
APPe9701SE
3--10 Exercise: Creating a FactoryTalk View SE Application and Configuring Communications
Answers Exercise A
2. You should select the Local product type to view an application

that is stored and run on the same computer.
4. Type AppliSE in the application name field:
5. The application contains one HMI server and zero areas.

(Recall that local applications do not use areas.)
Tip " If you have re-opened your application, the RSLinx Enterprise data
server may be located near the bottom of the Explorer window.
7. Your configuration should look similar to the following:
APPe9701SE
Lesson 4
Configuring OPC Communications
in a FactoryTalk View SE
Application
x Configure communications using an RSLinx OPC data server by
performing the following tasks:
-- Configure a communications driver
-- Create an OPC topic
x Locate HMI project files

x Failure to properly establish communications with the appropriate
controller or processor can result in the inability to transfer data
within an application.
x It is important to understand the structure and organization of
HMI project files to aid in development.
Driver: The software interface to the hardware device that allows

RSLinx Classic to communicate with your PLC.
OPC (Object Linking and Embedding for Process Control): A

communication standard designed to allow client applications access
to plant floor data in a consistent manner. It provides a common way
for applications to access data from any data source, such as a device
or database.
Topic: A topic represents a specific path to a processor.
OPCsb9701SE
4--2 Configuring OPC Communications in a FactoryTalk View SE Application
Understanding RSLinx Software
Explain to students that there are seven RSLinx software serves OPC data to the Rockwell Automation line
different versions of RSLinx Classic of programmable controllers. Unlike RSLinx Enterprise software, it
software to meet different cost and
functionality requirements. For more provides a download path for the various RSLogix software
information, students can refer to the packages to the matching controller.
RSLinx Classic Getting Results Guide.
Use RSLinx Classic software when:
x The information being served to FactoryTalk View SE Servers or
FactoryTalk View SE Clients is local.
x The RSLinx data server is installed on the same computer as the
FactoryTalk View SE Server.
You do not need to install an activation key to

make RSLinx Classic work, provided you run
RSLinx Classic software on the same computer as
the FactoryTalk View SE Server.
You must use an RSLinx activation key for RSLinx Gateway:

x If the information is being served to third-party OPC client, for
example, a FactoryTalk View SE Client.
x If the RSLinx data server is installed on a computer separate from
the FactoryTalk View SE Server. You might do this for
performance reasons, or to locate the OPC server physically close
to the process generating data.
Configuring Communications Using an RSLinx OPC Data Server
Configuring a Communications Driver

Open RSLinx Classic software and show Unlike RSLinx Enterprise, which lists drivers according to
students the Configure Drivers dialog communications protocol (DeviceNet, DF1, etc.), RSLinx drivers are
box. Point out drivers that are unique to
the software (i.e., the 1747--PIC/UIC listed according to the driver hardware installed on your computer.
driver).
RSLinx Classic software also includes additional drivers that are not
currently available in RSLinx Enterprise software.
OPCsb9701SE
Configuring OPC Communications in a FactoryTalk View SE Application 4--3
If students ask, remind them that driver Once the necessary drivers have been configured, the RSWho
configuration will be covered later in this window can be used to view configured drivers:
lesson.
Backplane Modules
Autobrowse Feature
Configured Networks
Selected Backplane
Creating an OPC Topic

Point out to students that RSLinx Classic After using the RSWho screen to verify a functioning connection to
topics can also be automatically created a processor or controller within your application, the next step is to
by downloading to a controller using the
software. This feature is enabled by create an OPC topic for the application. The DDE/OPC Topic
default, but can be disabled by the user. Configuration dialog box contains the following components:
OPC Topic List Associated

Controller
OPCsb9701SE
4--4 Configuring OPC Communications in a FactoryTalk View SE Application
The following components aid in OPC topic creation:

x OPC Topic List: Displays available communication paths.
x Associated Controller: Contains the application to which a
selected topic is associated.
RSLinx Classic topics typically point to an online

processor or controller. Offline topic support (i.e.
using RSLogix 5 or 500 offline files) can be
configured from the Data Collection tab in the
Topic Configuration window.
Locating HMI Project Files
New applications are saved on your computer using the following

path: C:\Documents and Settings\All Users
\Documents\FactoryTalk View Enterprise\SE\HMI Projects
Application components, useful for importing and exporting, can be

found in your project folder such as:
x Graphic displays
x Global Objects
x Images

Demonstrate the following tasks: x Configure communications using an RSLinx OPC data server by
1. Launch or open RSLinx Classic performing the following tasks:
software.
-- Configure a communications driver
2. Open the Configure Drivers dialog -- Create an OPC topic
box and add the driver that
corresponds to the network you are x Locate HMI project files
using.
3. Open the DDE/OPC Topic
Configuration dialog box. the associated job aid(s).
4. Create a new topic.
5. Open the
CCV207_9701SE_DEM1.APA
application.
6. Add a new OPC Data Server.
7. Name the server and then select
RSLinx OPC Server as the Prog ID.
8. Create a new graphic display.
9. Create a numeric display.
10. Show students how to browse
through the RSLinx OPC Server
and select a tag.
11. Show students how to browse to an
HMI project file.
OPCsb9701SE
Exercise: Configuring OPC Communications in a FactoryTalk View SE Application 4--5
Exercise: Configuring OPC

Communications in a FactoryTalk
View SE Application
Exercise A In this exercise, you will practice configuring OPC communications

in a FactoryTalk View SE (Site Edition) application using RSLinx
Classic software. You will also locate your HMI project files.
Context:
Before you can create graphic objects that display data from a
processor or controller, you need to establish communications using
an OPC data server.

Directions:
1. Open your FactoryTalk View SE application from the previous

exercise.
Tip " If you have not completed the previous FactoryTalk View SE
Programming exercises, open the OPC_9701SE_A1.APA file.
2. Add an OPC Data Server named RSLinxClassic with an OPC

Server name of RSLinx OPC Server.
3. If it is not already running, start RSLinx Classic software.
4. If it is not already configured, configure a communications driver
for the network that you are using.
5. Create an OPC Topic named RSLinxClassic_Topic in RSLinx
Classic software to communicate to your controller.
6. Click Start>Programs>Rockwell Software>FactoryTalk
Tools>Rockwell Software Data Client.
7. Select Local.
8. Select Connect OPC Server and then RSLinx Remote OPC
Server.
9. Leave the default settings for a new group and click OK.
10. Verify your OPC communications by performing the following:
A. Expand the RSLinxOPC_Topic that you created.
B. Expand Online and then Program:Filling.
OPCe9701SE
4--6 Exercise: Configuring OPC Communications in a FactoryTalk View SE Application
C. Add the Conveyor.ACC tag.

11. Click OK.
12. Verify that the current quality is Good.
13. Close Live Data Test Client.
14. Locate your HMI project files.
15. Verify that AppliSE.sed (or OPC_9701SE_A1) exists.
16. Minimize or close RSLinx Classic software.
17. Close your FactoryTalk View SE application.
OPCe9701SE
OPCe9701SE
Answers Exercise A
2. The OPC Data Server Properties window should look like the
following:
5. Your configuration should look similar to the following:
OPC Topic
Controller
OPCe9701SE
8. Select RSLinx OPC Server as shown below:
10. Add the Conveyor.ACC tag:
12. Verify the current quality:
14. Your application should be located in the following path:

C:\Documents and Settings\All Users
\Shared Documents\RSView Enterprise\SE\HMI Projects
Your project files will be in a folder named AppliSE or

OPC_9701SE_A1.
OPCe9701SE
OPCe9701SE
Lesson 5
Creating an HMI Tag Database in a
FactoryTalk View SE Application
x Create an HMI tag folder
x Create HMI tags
x Import and export an HMI tag database
x Create and modify HMI tags and folders using Microsoft Excel
software

x HMI tag folders provide a way to organize HMI tags.
x HMI tags provide additional properties for run-time security and
data manipulation.
Mention that the Tag Import and Export x You can import HMI tags from a third-party editor such as
Wizard must be run on the same Microsoft Excel software to create tags. You can also import PLC
computer as the HMI server.
or SLC databases to save programming time.
x Modifying HMI tags using Microsoft Excel software can be
useful when modifying many tags at once.
Direct Reference Tag: A data source that resides within a controller

or processor. Changes to a direct reference tag are immediately
Mention that using direct reference tags reflected in a FactoryTalk View SE application.
eliminates the need to create separate
HMI tags for the application.
Tip " The FactoryTalk Directory component built into FactoryTalk View
SE software lets users browse directly to a tag in a processor or
controller.
HMI Tag: A data source that resides within a FactoryTalk View SE

tag database. HMI tags can reference either a physical device or a
location in local memory (RAM).
Tag: A logical name that represents a variable in a network device or

in local memory (RAM).
CTDsb9701SE
5--2 Creating an HMI Tag Database in a FactoryTalk View SE Application
Creating an HMI Tag Folder

Emphasize that this lesson focuses on
the use of HMI tags. If this lesson is part HMI folders and tags are created and viewed using the Tags editor,
of a standard school, the use of which also is called the tag database. HMI folders can be used to
direct-reference tags will be covered in
later lessons. organize tags into logical groupings, such as for a machine or for a
packaging process.
Tip " If your application contains multiple machines that reference the
same tags, you can duplicate an existing HMI folder and rename the
tags within the folder.
The Tags editor is divided into the following sections:

x Form View: The section of the Tags editor reserved for entering
and modifying tag data.
x Spreadsheet View: The section of the Tags editor that provides a
listing of the existing HMI tags and folders.
Form View
Spreadsheet View
CTDsb9701SE
Creating an HMI Tag Database in a FactoryTalk View SE Application 5--3
Creating HMI Tags
HMI tags are classified based on the type of information received

from a data source. Users can choose from the following tag types:
Example: Analog tags can be used to x Analog Tags: Store a numeric value based on a range of values
record temperature, pressure, flow, or defined for the tag.
rotary control position.
x Digital Tags: Store a numeric value of either 0 or 1. They are
Example: Digital tags can be used to
represent devices such as switches, used to store a device’s on or off state.
contacts, or relays. x String Tags: Store ASCII characters, including whole words. The
Example: String tags can be used to maximum allowable string size is 82 characters.
store information such as alphanumeric
data collected from a bar code scanner.
If you are importing tags from an RSView32
project, string tags that contain more than 82
characters may be truncated.
Tag Data Sources

In the Tags editor, the form view of a tag changes based on the
selected data source. HMI tags can be classified as follows:
x Memory Tags: Reference a memory location within the
FactoryTalk View data table.
Remind students that access to device x Device Tags: Reference data stored in external controllers or
tags is provided through an OPC server processors.
such as RSLinx Enterprise.
When creating a memory tag, you can define a starting value for the
tag and whether the tag value is retained when an application is
closed and reopened:
Data Source
Starting Tag Value
Tag Value Retention
Open the Tags editor and show students System tags are specialized read-only memory tags that are created
the available system tags. automatically along with a new application.
Important: Don’t demo the tasks here;
they will be covered in the Here’s How These tags reference information such as recent alarm values, current
section. system time and date, communication status and errors, or other
system-level data.
CTDsb9701SE
You can select the data source for a device tag using the Tag
Browser:
Tag Address
Importing and Exporting an HMI Tag Database
If you are using HMI tags from a previously created application, use
the Tag Import and Export Wizard to manipulate tag database files:
Import and Export Options
Potential Learning Problem: The Use the Tag Import and Export wizard for the following tasks:
terms “HMI tag database” and
“FactoryTalk View tag database” are x Export the HMI tag database to a .csv file
interchangeable. x Import a .csv file to the HMI tag database
Explain that merging HMI tag database x Merge HMI tag databases
files combines the export of tags from
one file with the import of the tags to x Import A.I. Series or Logic 5 database (.csv) files
another file. x Import RSLogix 5 or RSLogix 500 address and symbol files
CTDsb9701SE
Creating an HMI Tag Database in a FactoryTalk View SE Application 5--5
When merging HMI tag databases, you must

open two instances of FactoryTalk View Studio
software. For additional help, see the
Procedures Guide or the online FactoryTalk
View SE Help system.
Mention to students that more tag Creating and Modifying HMI Tags and Folders Using Microsoft
database fields exist than what are Excel Software
shown in the following example. The
other fields can be accessed using the
scroll bar. Certain tag properties can be modified using the Tags editor;
however some properties (e.g., tag name) can be modified by
exporting the HMI tag file and opening the corresponding .csv file
using Microsoft Excel software:
Folders Section
Tag Section
Tip " If you need to change the name of a previously created tag, another
option is to duplicate the tag, change the tag name, and delete the
original tag.
Tip " Exported files are saved using the .csv extension. Therefore you
should browse for all files when opening the file using Microsoft
Excel software.
CTDsb9701SE
If this course is part of a standard When you import and export HMI tags, FactoryTalk View SE
school, mention that alarms will be software also provides an option to import and export alarm
covered in a later lesson.
information associated with the tags. This data is saved in a separate
.csv file:
Analog Alarms
Digital Alarms

1. Open the x Create an HMI tag folder
CCV2007_9701SE_DEM1.APA file
and demonstrate the following tasks: x Create HMI tags
2. Create an HMI tag folder. x Import and export an HMI tag database
3. Create an analog tag inside the HMI x Create and modify HMI tags and folders using Microsoft Excel
folder. software
4. Create digital and string tags
outside of HMI folder (at the root of As your instructor demonstrates these procedures, follow along in
the Tags editor). the associated job aid(s).
5. Export the HMI tags and alarm tags
to .csv files.
6. Open the tags .csv file using
Microsoft Excel software.
7. In the folders section, add a new
folder.
8. Change the path of the digital and
string tags so the tags are placed
inside an HMI folder.
9. Save the changes to the Microsoft
Excel file, making sure to preserve
the .csv file format.
10. Import the .csv file back into the
application.
11. Reopen the Tags editor and show
that the changes you made to the
database have been accepted.
CTDsb9701SE
Exercise: Creating an HMI Tag Database in a FactoryTalk View SE Application 5--7
Exercise: Creating an HMI Tag

Database in a FactoryTalk View SE
Application
Exercise A In this exercise, you will practice creating HMI tags and folders. You
will also practice importing and exporting the tag database and
modifying the database using Microsoft Excel software.
Context:
When you are working with data that needs to be manipulated or

creating alarmed tags, you should first create and/or modify the tags
using the tags database.

Directions:

exercise.
Programming exercises, open the CTD_9701SE_A1.APA file.
2. Create a new HMI tag folder called mem.

3. Create the following HMI tags using Memory as the data source:
A. Create a retentive analog tag called mem\analog.
B. Create a retentive digital tag called mem\digital.
C. Create a retentive string tag called mem\string.
4. Create a new HMI tag folder called Scaling.
5. Create an analog HMI tag called Timer using Device as the data
source.
A. Browse to the path [LinxE_Shortcut]ten_sec_timer.ACC in
the address bar.
B. Scale the timer tag so the end result will be in seconds. The
timer accumulator in the Logix 5000 program is in
milliseconds.
6. From the File menu, select Tools and then Tag Import and
Export Wizard. . .
CTDe9701SE
5--8 Exercise: Creating an HMI Tag Database in a FactoryTalk View SE Application
Tip " You may also go access the wizard from the Windows Start Menu by
selecting StartoProgramsoRockwell Softwareo
FactoryTalk ViewoToolsoTag Import and Export Wizard.
7. Export the FactoryTalk View tag database to a CSV file without

exporting the associated alarm information. Save the file as
C:\AppliSE-Tags.CSV.
8. Open Windows Explorer.
9. Browse to C:\ and then open the AppliSE-Tags.CSV file.
10. View the tag and folder information.
11. What information is located in the MSExcel W column?
12. Create and modify HMI tags and folders using Microsoft Excel
software by performing Steps 13. through 20.:
13. Copy Row 5.
14. Insert Copied Cells into Row 7.
15. Rename the folder in Row 7, Column B to Comments.
16. Copy Row 12.
17. Insert Copied Cells into Row 14.
18. Rename the tag in Row 14, Column B to Comments\Repair1.
19. Add the following tag descriptions to the appropriate column in
the CSV file:
20. Save your changes to the .CSV file.
Tip " Click Yes to any warnings about keeping the .CSV format.
21. Within FactoryTalk View SE, open the Tag Import and Export
Wizard.
22. Import the FactoryTalk View tags from the .CSV file you just
edited into the AppliSE application.
Tip " Make sure to select Update existing (slower) as you modified the
descriptions of several tags.
CTDe9701SE
23. Open the Tag Database editor and then confirm your edits are
correctly displayed.
Tip " If the Tag Database was open while the .CSV file was edited,
Refresh the Tag Database.
CTDe9701SE
Answers Exercise A
3. If you created your HMI tags correctly, it should look similar to

the following:
5. Your Scaling\Timer tag should have the following

configuration:
CTDe9701SE
7. Select Export FactoryTalk View tag database to CSV files as

shown below:
Select project type and file as shown below:
Configure your tag and alarm files as shown below:
11. The tag address of all the tags in the CSV file. In this file only
the Scaling\Timer tag has an address listed.
CTDe9701SE
14. Insert copied row as shown below:
22. Select Import FactoryTalk View tag CSV files as shown below:
Browse to your .CSV file as shown below:
CTDe9701SE
Lesson 6
Creating a Graphic Display in a
x Add a graphic display
x Create and manipulate graphic objects
x Add images to an application

x Creating a graphic display is one of the first steps in developing
an application and is imperative for a graphical interface.
x Manipulating objects in a graphic display ensures that an
application has a consistent look and feel.
x Adding images enables the developer to customize displays for an
application.
Before You Begin Graphic Display Editor
If this lesson is part of a standard From the Application Explorer, you can access the Graphics folder,
school, mention that several of these which contains a variety of editors used to create and build graphic
editors will be discussed in more detail
in the following lessons. displays:
Graphics Folder
CGDsb9701SE
6--2 Creating a Graphic Display in a FactoryTalk View SE Application
Adding a Graphic Display
There are three kinds of graphic displays:

x Standard Displays: These are the displays that the operator sees
at run time.
-- They present views of automated plant activity or processes.
-- They can show system or process data and provide operators
with a way to write values to a real-time database or network
devices such as a programmable logic controller.
x Global Object Displays: These let you link the appearance and
behavior of a graphic object on a global object display to multiple
copies of that object in standard displays.
-- When you make changes to the original object, these changes
are automatically applied to the copies.
x Library Displays: A library display contains ready-made graphic
objects that you can use in other displays.
Accessing the Displays folder from the Application Explorer
window allows users to create a new graphic display, add an existing
graphic display, or import and export a display.
New Display
Tip " Graphic displays are identified by a .gfx extension.
Graphic Display Settings
If students ask, tell them more details The Display Settings dialog box is used to configure individual
about the display settings features can graphic displays.
be found in the online FactoryTalk View
SE User’s Guide.
Properties Tab
The Display Settings dialog box opens by default to the Properties
tab, which is used to define the following graphic display
characteristics such as:
x Display types
x Update rates
x Security codes
CGDsb9701SE
Creating a Graphic Display in a FactoryTalk View SE Application 6--3
Display Type
Security Code
Tag Update
Rates
Behavior Tab
The Behavior tab provides additional display and object settings such
as:
x Commands that run with the graphic display is opened or closed
x On--screen keyboard visibility
x Input field colors when the field is selected or not selected
Startup and Shutdown

Commands
Input Field Colors
Keyboard Visibility
CGDsb9701SE
Grid Configuration
Tell students that decreasing the space Enabling a grid for FactoryTalk View SE graphic displays provides a
between horizontal and vertical lines reliable method for lining up graphic objects on the display:
provides better control of object
placement.
Grid Lines
Users can configure the following grid features:

x Visibility
x Color
x Vertical spacing between lines
x Horizontal spacing between lines
Explain that the snap-to-grid feature x Snap-to-grid
automatically moves graphic objects
from one grid line to another when
shifting on-screen objects.
Creating and Manipulating Graphic Objects
Drawing Objects: Lines and geometric shapes (e.g., ellipses,

polygons) that can be added to graphic displays.
Graphics Library: A collection of files that contain pre-designed

graphic objects that can be incorporated with existing graphic
displays.
CGDsb9701SE
An example of the motors graphic object library is shown below:
Tip " Users can modify items in the Graphics Library or create new library
files.
Creating Graphic Objects

Poll the students to determine if they Graphics objects are used to provide operators with an accurate
have previous experience working with representation of the machine or process they are controlling and
HMI development software (i.e.,
PanelBuilder, FactoryTalk View ME, or monitoring.
RSView32). Adjust your presentation
accordingly.
Objects Menu
The Objects menu provides a list of available tools. The drawing
objects submenu is used when creating text and graphic objects:
Drawing Objects
Submenu
CGDsb9701SE
Explain that the following list points out Objects Toolbar

the more commonly used objects. Refer
students to the online FactoryTalk View The Objects toolbar provides shortcuts to creating basic graphic
Machine Edition User’s Guide for more objects:
details on all the objects.
Basic Drawing Objects
The Properties dialog box for other drawing objects (the ellipse, in
the following graphic) provides graphics configuration tools:
Manipulating Basic Graphic Objects

One key component to manipulating graphic objects is the ability to
resize graphic objects. The following tools are available for resizing
graphic objects:
x The Common tab of a graphic object’s Properties dialog box lets
users change the object size using pixel measurements.
x Selected graphic objects are surrounded by handles, which can be
dragged to create the desired size.
CGDsb9701SE
If students ask, show them the The Graphics toolbar provides shortcuts to performing the following
drop-down menu selections that graphic manipulations:
correspond to the icons.
Flip
Duplicate Space Vertical
Cut Copy Paste Space Horizontal Flip
Vertical Horizontal
Send To Show/Hide
Group Back Zoom In Undo Redo Object Explorer
Ungroup Bring To Zoom Out Show/Hide
Front Property Panel
When working with complex graphic objects, the following

commands are commonly used:
x Space Vertical and Space Horizontal provide a uniform distance
between graphic objects.
You must have a minimum of three graphic

objects selected to use these commands.
x Bring to Front and Send to Back help organize graphic objects

that are stacked on top of one another.
x Flip Vertical and Flip Horizontal change the orientation of a
graphic object.
x Group and Ungroup help combine individual graphic objects
into a single unit (or break a previously grouped object into its
individual components).
Tip " It is not necessary to ungroup a grouped graphic object to modify the
properties of a single component of the group.
CGDsb9701SE
Adding Images to an Application
Images can be added to your application into the images folder:
Files types that may be added to the Images folder are:

x Bitmap files (.bmp)
x JPEG files (.jpg)
Tip " Best Practice: Use .bmp files whenever possible because the files
remain a static size at runtime. Using a compressed file (such as .jpg
file) can result in unexpected memory use at runtime.
Adding Images to a Display

Use the Objects menu to create an image.
Draw a space for an image.
CGDsb9701SE
The Image Browser window will appear with all images from the
Image folder available:

Open the CCV207_9701SE_DEM1.APA x Add a graphic display
file and demonstrate the following tasks:
x Create and manipulate graphic objects
1. Create a new graphic display and
name it Sample. x Add an image to an application
2. Create several drawing objects As your instructor demonstrates these procedures, follow along in
(circles, squares, etc.).
the associated job aid(s).
3. Group the objects and demonstrate
how individual objects within the
group can be selected and/or moved
without ungrouping objects.
4. Change an object’s pattern.
5. Ungroup the objects.
6. Select an object and convert it to
wallpaper. Show how the item can
no longer be selected.
7. Add the Plane.bmp file to the
images folder.
8. Insert Plane.bmp into your Sample
display.
CGDsb9701SE
CGDsb9701SE
Exercise: Creating a Graphic Display in a FactoryTalk View SE Application 6--11
Exercise: Creating a Graphic

Display in a FactoryTalk View SE
Application
Exercise A In this exercise, you will practice adding graphic displays, drawing
and arranging objects, and adding images in a FactoryTalk View SE
(Site Edition) application.
Context:
Before you can view data from a processor through an HMI (Human
Machine Interface), you must create a display.

Directions:

exercise.
Programming exercises, open the CGD_9701SE_A1.APA file.
2. Add a new graphic display to your FactoryTalk View SE

application.
3. Right-click on the display and then select Display Settings.
4. Configure your graphic display properties as follows:
Color of your choice
CGDe9701SE
6--12 Exercise: Creating a Graphic Display in a FactoryTalk View SE Application
5. Save the graphic display and name it Base Template.

6. Display the grid features by performing the following:
A. Show Grid.
B. Enable Snap On.
7. Create and configure basic drawing objects:
A. Add a red rectangle at the top of your display that will serve
as a title bar.
B. Add white text of font 16 that says Base Template:
C. Create a light grey panel object with a RaisedInset border

style of width 5.
D. Add three rounded rectangles and use the Arrange tools to
align them evenly within the grey panel object:
Tip " When creating graphic displays, save your work often.
8. Select all three rounded rectangles and access the Property Panel
to change their color to blue.
CGDe9701SE
9. Manipulate graphic objects by grouping the rounded rectangle

objects.
10. Convert the red rectangle graphic object at the top of the display
to wallpaper.
11. Add an image to your graphic display and use the RSView
Image.bmp file located in C:\SE Class Files\Images.
12. Try adding some of the following basic graphic elements to your
display that your are not familiar with:
x Line
x Polyline
x Polygon
x FreeHand
x Ellipse
x Arc
x Wedge
13. Save your display.
CGDe9701SE
Answers Exercise A
8. The Property Panel is accessed from the View menu, and

should have the foreground color set to blue:
11. The RSView Image object is imported as shown in the

following graphics:
CGDe9701SE
Your final graphic display should incorporate the

RSView Image.bmp file as shown below:
CGDe9701SE
CGDe9701SE
Lesson 7
Building an Interactive Graphic
Application
What You Will Learn After completing this lesson, you should be able to perform the
following tasks:
x Add objects from a Graphics Library
x Add interactive objects
x Create a local message file and display object
x Test a FactoryTalk View SE graphic display

x Pre-designed objects from the Graphics Library decrease the
amount of time needed to build graphic displays.
x Interactive objects allow for a customized application.
x Local message displays prompt or display information that can be
very helpful to operators or users.
x Graphic display testing is a useful tool because you can ensure a
display behaves accordingly as you develop your application.
Graphics Library: A collection of files that contain pre-designed

graphic objects that can be incorporated with existing graphic
displays.
Tip " Users can modify items in the Graphics Library or create new library
files.
Local Message Display: A display that provides ongoing

information on the status of devices and processes.
BGDsb9701SE
7--2 Building an Interactive Graphic Display in a FactoryTalk View SE Application
Adding Objects From a Graphics Library
Graphics Library files can be accessed from the Application

Explorer window:
Tip " Objects from an open library file can then be dragged (or copied and
pasted) to another graphic display.
Available Graphics Types

Mention that individual graphics files can Individual images in the Graphics Library can be created or imported
also be imported into a project using the from the following file types:
image graphic object.
x Bitmap files (.bmp)
x JPEG files (.jpg)
x AutoCAD files (.dxf)
x Windows metafiles (.wmf)
Example: Some compressed Tip " Best Practice: Use .bmp files whenever possible, because the files
.jpg images have expanded to remain a static size at runtime. Using a compressed file (such as a
as large as 5M at runtime.
.jpg file) can result in unexpected memory use at runtime.
Adding Interactive Objects
Many objects interact with the FactoryTalk View Tag Database. This
allows for control and display configuration.
BGDsb9701SE
Building an Interactive Graphic Display in a FactoryTalk View SE Application 7--3
Interactive objects include:

x Embedded Variables: Embedded variables allow you to display
values that change dynamically at runtime. At runtime, a
placeholder is updated with the real-time values of the variables.
x Push Buttons: Objects that are typically used to start or stop
processes or actions:
-- Numeric and String: Objects for entering or viewing
numbers or text in a graphic display.
x Indicator: Objects that allow an operator to make a selection
from a number of possible choices, all of which are visible at
once.
x Gauge and Graph: Objects that show the range of values and
relationships between variables.
x Key: Objects that represent keys on a keyboard and are for use
with touch screens.
x Advanced: Objects, such as trends and alarm summaries, which
allows you to view and analyze the data in your system.
x OLE Objects: Objects such as spreadsheets, charts, or text
produced by other Windows applications. The types of OLE
objects that are available depend on the software installed on your
system.
x Active-X Objects: Control objects such as gauges, sliders, and
buttons, and objects you create yourself using a tool like Visual
Basic. These objects allow an external action, such as a mouse
click, to initiate an action within FactoryTalk View software. The
Active-X objects that are available depend on the software
installed on your system.
Push Button Objects

There are seven different push buttons available:
BGDsb9701SE
Button Object
Tell students that a list of commands can The Button object provides a method of running a FactoryTalk View
be found in the FactoryTalk View SE command. Running a command allows you to:
User’s Guide.
x Navigate to other graphic screens
x Set the value of tags
x Control data logging
x Control login and logout
General Tab: Configure how the button will look. Choose a style
for the button’s appearance.
Styles
Common Tab: Some properties, such as size and position, are

common to all graphic objects. These properties are set up through
the Common tab in the Properties dialog box.
BGDsb9701SE
Up Appearance Tab: Specify what the button will look like when it
is not in its pressed position.
If you add an embedded variable to the caption, the embedded

variable syntax appears in the Caption box, but the text of the
variable appears on the face of the object.
Tell students that it is good practice to Down Appearance Tab: Specify what the button will look like
issue a single command from the when it is in its pressed position. By default, it will have the same
Release position rather than the Press
position. This allows an operator to properties as the Up Appearance.
move off a pressed button without
running the command if he had pressed
it by mistake.
BGDsb9701SE
Action Tab: Choose an action for this button:

Tip " Run Command is the default setting.
x Run Command
x Set tag to 1
x Set tag to 0
x Toggle tag value
x Set tag to 1 on press and to 0 on release
x Set tag to 0 on press and to 1 on release
Other Push Buttons

The rest of the push buttons perform a specific task and don’t use
FactoryTalk View commands. Their configurations are different
from the button object.
For example, a momentary push button Momentary:

may be used to control the states of a
valve. The valve can be opened, closed, x When the operator presses the button, it changes from State 0 to
or partially opened. State 1 and sends the State 1 value to the data source.
x When the operator releases the button, it changes from State 1
back to State 0 and sends the State 0 value to the data source.
For example, a maintained push button Maintained: This button works like a hard-wired switch.
may be used to control the type of label
to print for a bag filler machine. The x When the operator first presses the button, it changes from State 0
machine can print labels with metric or to State 1 and sends the State 1 value to the data source.
imperial weights.
x When the operator presses and releases the button a second time,
it changes from State 1 back to State 0 and sends the State 0 value
to the data source.
BGDsb9701SE
For example, a latched push button may Latched:

be used to control the filling process for
the bag filler machine. When the x When the operator first presses the button, it changes from State 0
operator presses the button, the to State 1 and sends the State 1 value to the data source.
application sets the button to State 1
and the caption changes to filling. x The button retains this value until unlatched by the Handshake
control.
For example, a multistate push button Multistate:
may be used to control mode of
operation for a bag filler machine. The x When the operator first presses the button, it changes from State 0
machine can operate manually, to State 1 and sends the State 1 value to the data source.
automatically, or it can be turned off.
x When the operator presses the button a second time, it changes
from State 1 to State 2 and sends the State 2 value to the data
source. Thus the state increments by one for each button press.
x When the button is in the last configured state and the operator
presses it, it changes to State 0 and sends the State 0 value to the
data source.
x Up to 256 states may be assigned to the button.
The action of the multistate push button depends on how the “Next
state based on” field is set:
x Current State: The application switches the button from the
current state to the next state and writes out the next state value.
x Value Control: The application reads the value of the Value
control and if the value matches one of the button’s state values,
changes the button to the next state and writes out the next state
value.
x Select this option if you want the button to base its state on
external changes to the Value control.
x If the value does not match one of the button’s state values,
the application changes the button to State 0 and writes out the
State 0 value.
x If you use the auto-repeat function for this button, the application
uses the last value written out to determine the next value to write
out, regardless of the “Next state based on” setting.
BGDsb9701SE
For example, an interlocked push button Interlocked: An interlocked push button is one of a group of buttons
may be used to control position of the that have the same control tag.
guide that directs the bottles from the
main conveyor to one of the three x The buttons function together in much the same way as Microsoft
secondary conveyors. Only one Windows option buttons: pressing one cancels the others and
secondary conveyor can be operational
at any moment. makes a new selection.
x Although interlocked push button function as a group, you can
add them to the screen one at a time.
x When the operator presses an interlocked push button, it changes
from State 0 to State 1 and sends the Button Value to the data
source.
x When the operator presses another interlocked push button, it
changes from State 0 to State 1, sends its button value to the data
source and the first button is set back to State 0.
For example, two ramp push buttons Ramp: A ramp changes a tag’s value by a given increment.
may be used to create a control to raise
or lower a value. x When the operator presses the ramp button, the application reads
the Value connection value, stores a local copy of the value, adds
or subtracts the ramp amount from the local value, and writes the
result to the Value control at the data source.
x Configure the auto repeat function under the Timing tab to allow
an operator to hold down the button and have it increment
continuously. Use ramp buttons in pairs to create a raise and
lower control.
BGDsb9701SE
Numeric and String Objects: These objects display information

from the Tag Database.
For example, you might use a numeric x Use the numeric display object to show the operator numeric
display to show the current temperature information from the data source.
of an oven in a bakery.
For example, you might set up strings x Use the string display object to show the operator messages from
displays that report on the state of a the data source.
process or operation, or that provide
instructions about what the operator
should do next. Gauge and Graph Objects
FactoryTalk View Studio contains objects to represent data in both
gauge and bar graph format.
Gauge: The gauge control will display tag or expression values with
as sweeping line. Options include the ability to set two thresholds
with unique fill colors:
For example, a bar graph push button Bar Graph and Scale: These objects are used to display data in a
may be used to monitor the speed of a bar chart format. Two thresholds with unique fill colors may be
conveyor.
configured. Typically a scale object is used in conjunction with a bar
graph to show tick marks.
Bar Scale
Object
Bar Graph
Text Objects
Object
BGDsb9701SE
Scale Setup
For example, a scale push button may The scale can be used as a ruler or measuring guide. The scale can be
be used to help visually determine the setup to have the tick marks configured in the up, down, left, or right
speed of a conveyor as depicted by the
bar graph. positions. You can also configure the number of major and minor
ticks:
You can place the scale next to a bar
graph, with text labels at the top and
bottom, to illustrate the range of the bar
graph.
Tick
Direction
Major Ticks Minor Ticks
Configuring Push Buttons

Each push button varies in its setup parameters, but they all have
many items in common. Double-clicking on a push button brings up
the Properties dialog box:
Tell students that some buttons have General Tab: Assign general appearance settings (color, highlight,
touch margins which are useful when border, etc.) here. Each button type will have its own unique settings
buttons are positioned close together.
on this tab.
BGDsb9701SE
States Tab: Depending on the push button type, many states may be
assigned to it. Configure each state, including caption, colors and
images, if any. State settings may be copied and pasted onto other or
all states.
Common Tab: Some properties, such as size and position, are

common to all graphic objects. These properties are set up through
the Common tab in the Properties dialog box.
Explain to students that you can assign Connections Tab: Define the connections to the Tag Database on
controls to specific tags or to this tab. Each push button will have a Value field.
expressions.
Opens Tag
Browser
Using the Expression Editor

You may wish to display not just the value of a tag, but an expression
instead. An expression allows you to manipulate tag values using:
x Arithmetic operators (+, --, /, *, **, MOD)
x Bitwise operators (AND, OR, XOR, shift left, shift right,
complement)
x Relational operators (<, >, =, t, d, z)
x Logical comparisons (AND, OR, NOT)
x If-Then-Else statements
x Functions
BGDsb9701SE
The Expression Editor is available in many FactoryTalk View

objects:
x Graphics
x Derived Tags
x Events
x Data Log Setup
x Command Line
The following example of how an expression might be used to
control the value of a String Display object:
Tag names containing any of the following must be enclosed with

curly brackets:
x An underscore (Line_1_Start)
x A dash (Line-1-Start)
x Or if the names start with a number (1LineStart)
Selecting tags with the Tag Browser will automatically apply the
curly brackets.
BGDsb9701SE
Creating a Local Message File
Local message displays allow a message to be triggered based on a

value.
Trigger Value
Trigger values are used to signify when to prompt a message. They
have the following constraints:
x Must be positive or negative integers.
x Zero (0), is not an acceptable trigger value.
x Trigger values do not need to be consecutive, but they must be
unique for each message.
For example, you could use trigger x The trigger value cannot be blank.
values of 1, 2, and 3, or values of 10, 20,
and 30.
Messages
Messages will prompt the operator when signalled by the trigger and
have the following properties:
x Messages can be up to 256 characters long.
x The new line character, \n, may be used to specify that the
message continues onto the next line after the character.
x Strings may be added to the message by right-clicking the
Message column and then clicking Edit String to open the String
Edit dialog box.
Local Message Display Object

Local message display objects may be treated similar to drawing
objects. Their appearance, size, tag value, etc. may all be configured:
BGDsb9701SE
Testing a FactoryTalk View SE Graphic Display
Test communications by using the Test and Edit Display buttons:
Test and
Edit Display
Buttons

Open the CCV207_9701SE_DEM1.APA x Add objects from a Graphics Library
application and demonstrate the
following tasks: x Add interactive objects
1. Add a new graphic display. x Create a local message file and display object
2. Open the Buttons - Industrial file x Test a FactoryTalk View SE Graphic Display
from the Graphics Library and drag a
pushbutton onto the display. As your instructor demonstrates these procedures, follow along in
3. Configure the push button. the associated job aid(s).
4. Close the Graphics Library file.
5. Add and configure a push button
from the Objects toolbar.
6. Create a new local message display.
7. Add the message Making rootbeer
for triggers 1 and 3.
8. Add the message Making soda for
triggers 2 and 4.
9. Add a local message display object
to your graphic display.
10. Connect your local message display
to the tag:
{::[LinxE_Shortcut]Program:
Filling.Bottle_Counter.ACC}
11. Browse to and select your message
file.
12. Test the graphic display.
13. Point out to students how the
message changes according to the
trigger value (e.g., number of
bottles).
14. Show students what the local
message display looks like when a
value occurs that has no trigger or
message.
BGDsb9701SE
Exercise: Building an Interactive Graphic Display in a FactoryTalk View SE Application 7--15
Exercise: Building an Interactive

Graphic Display in a FactoryTalk
View SE Application
Exercise A In this exercise, you will practice adding objects from a Graphics
Library file, adding interactive objects, and creating a local message
file and display.
Context:
In order to create an interactive display, you should know how to

incorporate graphic objects using the FactoryTalk View SE Graphics
Library.
At the end of the exercise, your Tank Overview graphic display

should appear similar to the following example:
Motor
Mixing
Vat
Outflow
Pipe
Pump

Directions:

exercise.
Programming exercises, open the BGD_9701SE_A1.APA file.
BGDe9701SE
7--16 Exercise: Building an Interactive Graphic Display in a FactoryTalk View SE Application
2. Add a new graphic display and save it as Mixing Tank.

3. Near the center of the graphic display, add a mixing vat from the
Graphics Library files.
4. In which Graphics Library file did you find the mixing vat?
5. Above the mixing vent, add a motor from the Graphics Library.
6. Use the Graphics Library to add pipes (with and without liquid
visible) that empty into the top of the mixing vat.
Tip " You may have to use multiple library objects.
7. Add a short outflow pipe from the Graphics Library that will
drain the mixing vat from the bottom.
8. Add a pump graphic from the Graphics Library that connects an
outflow pipe to the top of the pump.
9. Add a pipe (with liquid visible) from the Graphics Library that
connects to the side of the pump.
Objects in the display have been labelled to aid you in this lab:
10. Objects “A” should be configured as follows:

A. Create a Text Object and insert the text Water Line.
-- Font: Arial, 16 pt, bold
BGDe9701SE
B. Duplicate the Water Line text object and replace the text
“Water Line” with Syrup Line.
C. Why is duplicating better than copying and pasting?
D. Duplicate the Syrup Line text object and replace the text
“Syrup Line” with Mixer Control.
E. Arrange the objects according to the example given at the
beginning of the exercise.
11. Objects “B” should be configured as follows:
A. Create a Panel (basic graphic object).
B. Create a Text Object and insert the text Start Water.
C. Create a momentary pushbutton with the following
configuration:
State 0:
-- Caption: OFF.
-- Font: Arial, 12 pt, bold.
State 1:
-- Caption: ON.
-- Font: Arial, 12 pt, bold.
Connections Tab:
-- Tag Value:
{::LinxE_Shortcut]Program:Mixing.H20_on_off}
-- Tag Indicator:
{::LinxE_Shortcut]Program:Mixing.H20_hold}
D. Arrange the objects according to the example given at the
12. Objects “C” should be configured as follows:
A. Duplicate the group created in Step 11.
B. Replace the “Start Water” text with Start Syrup.
C. Tag Value:
{::LinxE_Shortcut]Program:Mixing.Syrup_on_off}
D. Tag Indicator to:
{::LinxE_Shortcut]Program:Mixing.Syrup_hold}
BGDe9701SE
13. Objects “D” should be configured as follows:

A. Duplicate the group created in Step 11.
B. Replace the “Start Water” text with Start Pump.
C. Tag Value:
{::LinxE_Shortcut]Program:Mixing.Pump_on_off}
D. Tag Indicator:
{::LinxE_Shortcut]Program:Mixing.Pump_hold}
14. Objects “E” should be configured as follows:
A. Create a Panel (basic graphic object).
B. Create a Text Object and insert the text Tank Level.
C. Create a Numeric Display with a field length of at least 4
and the following expression:
{::LinxE_Shortcut]Program:Mixing.
MixerTank_Level}/10
D. Modify the Text Object font (object properties) to a font of
your choice.
E. Arrange the object according to the example given at the
15. Objects “F” should be configured as follows:
A. Create a Bar Graph.
Appearance:
-- Back color: gray
Bar Graph Settings:
-- Minimum value: 0
-- Maximum value: 1000
Threshold:
-- Threshold 1 value: 500
Connections:
-- Tag Value: {::LinxE_Shortcut]Program:
Mixing.Mixer_Tank_Level}
B. Arrange the object according to the example given at the
BGDe9701SE
16. Create a local message file named BatchProgress with the

following configuration:
17. Objects “G” should be configured as follows:

A. Create a local message display.
Appearance:
-- Back style: Transparent
-- Fore color: red
-- Message file: BatchProgress
Connections:
-- Tag Value to:
{::LinxE_Shortcut]Program:Mixing.Mixing_Message}
B. Arrange the objects according to the example given at the
18. Object “H” should be configured as follows:
A. Create a Button.
Action:
-- Action: Run Command
-- Press Action: Display “Main”
(The “Main” display will be created later).
Up Appearance:
-- Caption: Home
19. Object “I” should be configured as follows:
A. Create a Maintained Push Button.
State 0:
-- Caption: Mixer OFF
BGDe9701SE
State 1:
-- Caption: Mixer ON
Connections:
-- Tag Value:
{::LinxE_Shortcut]Program:Mixing.Mixer_on_off}
B. Arrange the objects according to the example given at the
20. Object “J” should be configured as follows:
A. Create a Text Object and insert the text Actual.
B. Insert a Numeric Variable referencing the tag:
{::LinxE_Shortcut]Program:Mixing.Mixer_rpm_actual}
C. Font: Arial, 14pt, bold
D. Arrange the object according to the example given at the

21. Object “K” should be configured as follows:
A. Create a Numeric Display with the following expression:
{::LinxE_Shortcut]Program:Mixing.
Mixer_rpm_setpoint}
B. Modify the Text Object font (use the Property Panel) to a
font of your choice.
C. Arrange the object according to the example given at the
22. Object “L” should be configured as follows:
A. Create a Ramp Button.
BGDe9701SE
Button Settings:
-- Select Ramp Down
-- Lower limit: 0
-- Ramp value: 10
Label:
-- Image: Arrow Down
Timing:
-- Auto Repeat Rate: 10
Connections:
-- Tag Value to: {::LinxE_Shortcut]Program:Mixing.
Mixer_rpm_setpoint}
beginning of the page.
23. Object “M” should be configured as follows:
A. Create a Ramp Button.
Button Settings:
-- Select Ramp Up
-- Upper limit: 1740
-- Ramp value: 10
Label:
-- Image to Arrow Up
Timing:
-- Auto Repeat Rate: 10
Connections:
-- Tag Value to: {::LinxE_Shortcut]Program:Mixing.
Mixer_rpm_setpoint}
beginning of the page.
24. Object “N” should be configured as follows:
A. Create a Text Object and insert the text Setpoint
B. Font: Arial, 14pt, bold.
C. Arrange the object according to the example given at the
25. Add a panel to the display and place it behind the mixer controls.
27. Test your FactoryTalk View SE graphic display.
Make sure to test all buttons.
BGDe9701SE
BGDe9701SE
BGDe9701SE
Answers Exercise A
4. You should have found the mixing vat in the Tanks file.
10.
C. Answers may vary slightly but should include at least one of
the following:
-- Duplicate works until you deselect the object.
-- If you duplicate an object, move it, and then select
Duplicate again, the object will be duplicated and moved in
one step. This is useful for creating a series of objects with
an equal distance between them.
-- Duplicating does not use the clipboard, so its contents are
not changed when you use this command.
BGDe9701SE
Lesson 8
Animating a Graphic Display in a
x Add an existing graphic display
x Animate graphic objects
x Creating an expression within an animation

x Adding existing graphic displays to an application can speed the
overall development process.
x Animating a graphic object allows the object to represent a tag’s
value graphically.
Before You Begin Adding an Existing Graphic Display
Accessing the Displays folder from the Application Explorer

window allows users to add an existing graphic display.
Add Existing
Display
Tip " Graphic displays are identified by a .gfx extension.
Animating Graphic Objects
Animated Object: A graphic object that is linked to a tag or

expression and has a type of animation attached to it, so the object’s
appearance changes to reflect changes in the tag’s value.
Drawing objects (i.e., rectangles, ellipses,

freehand drawings) can be configured with a
range of animation types. Interactive objects (i.e.,
pushbuttons, indicators) only support visibility
animation.
AGDsb9701SE
8--2 Animating a Graphic Display in a FactoryTalk View SE Application
To animate an object, right-click the object and then select

Animation:
Available Animations
There are several ways to animate an object at run time based on a

tag value:
x Visibility: An object can be visible or invisible.
x Color: The color of an object can change and may be configured
to blink.
-- For each change specify the value (or threshold) at which the
color is to change, the foreground and background colors, and
whether the colors are solid or blinking. If you choose a
blinking color you also specify a blink rate.
Foreground
Color/Blink
Background
Number of Color/Blink
Thresholds
Blink Rate
Threshold Value
AGDsb9701SE
Animating a Graphic Display in a FactoryTalk View SE Application 8--3
For example, you could have a tank that x Fill: Objects can appear to fill in different directions and to a
fills or empties. specified percent or range.
Fill Percentage
Minimum and
Maximum Values
Fill Direction
x Horizontal and Vertical Position: The position can change

based on the tag’s value or a range and can include an offset
value.
x Width and Height: The size of an object can change to a
specified percent or range.
Change
Percentage
Minimum and
Maximum Values Anchor Point
For example, you could have an x Rotation: The degrees of rotation and the center of rotation may
animated fan that spins when it is turned be configured.
on.
x Touch: Commands may be configured for press, repeat and
release actions.
x Horizontal and Vertical Slider: The tag value can change as the
position of the slider changes.
AGDsb9701SE
Creating an Expression within an Animation
In addition to controlling animation with tags, the Expression editor

can be used to add more precision to your animation control by
specifying conditions under which animation occurs:
Syntax Validation Available

Functions
Refer students to the FactoryTalk View Use the Expression editor to create:
ME online Help system for more
information about expressions. x “If-Then-Else” statements
x Logical statements (i.e., AND, OR, NOT)
x Relational statements (i.e., greater than, less, than, etc.)
If you are combining relational statements and

logical statements in an expression, be sure to
enclose the complete relational statements in
parentheses.
x Arithmetic statements (i.e., addition, subtraction, etc.)

x Bitwise statements (i.e., AND, OR, XOR, bit shift instructions,
etc.)
x Functional statements (i.e., advanced mathematical functions,
security codes)
Tip " You can also access the Tag Browser from the Expression editor.
AGDsb9701SE
Animating a Graphic Display in a FactoryTalk View SE Application 8--5
The following graphic shows a complete expression:
The syntax validation feature will check to see if the expression you
created is valid. If an expression is not valid, the software indicates
the location(s) of the invalid information.
Here’s How To perform the following:

Open the CCV207_9701SE_DEM1.APA x Add an existing graphic display
file and demonstrate the following tasks:
x Animate graphic objects
1. Add the existing Animation Display
to the application. x Creating an expression within an animation
2. Test run the display and show the As your instructor demonstrates these procedures, follow along in
students how the motor color
changes. the associated job aids(s).
3. Create another object and add
horizontal animation to it.
4. Show students how to create an
expression within an animation.
5. Show students how to copy
animation.
AGDsb9701SE
AGDsb9701SE
Exercise: Animating a Graphic Display in a FactoryTalk View SE Application 8--7
Exercise: Animating a Graphic

Application
Exercise A In this exercise, you will practice animating graphic objects.
Context:
You would like to create animation on your FactoryTalk View

display that reflects the real-time status of the executable code in the
plant floor controller.
There is a timer accumulator in the controller. The timer lasts for 8

seconds and has a time base of 0.001 seconds.

Directions:

exercise.
Programming exercises, open the AGD_9701SE_A1.APA file.
2. Add the following existing graphic displays to your graphics

display folder:
Follow the path C:\SE Class Files\Component to import for labs\
to add each display:
x aircoolers.gfx
x blankpage.gfx
x conveyor.gfx
x popup_motorssl.gfx
x popup_ss_ps_fs_ts.gfx
3. Add the following local message to your local message folder:
C:\SE Class Files\Components to import for labs\bottles.loc
4. Open the Conveyor display.
5. Test the display.
6. Where would you check for errors?
If you receive any errors, correct them before proceeding.

AGDe9701SE
8--8 Exercise: Animating a Graphic Display in a FactoryTalk View SE Application
7. Configure Bottle 1 (the left bottle) using the tag

{::LinxE_Shortcut]Program:FILLING.
CONVEYOR_TIMER and animate as follows:
A. Configure visibility animation:
-- Make visible when 0 d timer d 2000.
B. Configure fill animation:
-- Fill only to 90% and from bottom to top.
-- Fill from the inside only.
-- Use a constant range value minimum of 2500 and
maximum of 3000.
C. Configure horizontal position animation:
-- Move from the left side of the conveyor to underneath the
filling machine when 0 d timer d 2000.
-- Use a constant range value minimum of 0 and maximum
of 2000
-- Determine the horizontal offset by moving the bottle from
its minimum position at the left of the conveyor to its
maximum position underneath the filling machine (on top
of the middle bottle).
Tip " Disable the grid for a more precise path.
8. Copy the animation of Bottle 1 and paste it onto Bottle 2 (the

middle bottle):
A. Edit the visibility animation:
-- Make visible when 2000 d timer d 5750.
Tip " Check the syntax to make sure your expression is correct. Make sure
to use parenthesis before and after your expression.
B. Edit the horizontal position animation:

maximum of 5000.
-- Edit the horizontal offset by moving the bottle from its
minimum position underneath the filling machine to its
maximum position under the capper.
9. Copy the animation of Bottle 1:
A. Use the Object Explorer and browse to CappedBottle.
Expand CappedBottle to show the objects within the group.
B. Right-click Bottle and paste animation.
The animation must be applied to the cap and bottle
separately.
AGDe9701SE
C. Edit the visibility animation:

-- Make visible when the timer t 5750.
D. Edit the horizontal position animation:
maximum of 8000.
-- Edit the horizontal offset by moving the bottle from its
minimum position under the capper to its maximum
position at the right end of the conveyor.
10. Copy the animation of Bottle 3:
A. Use the Object Explorer and browse to CappedBottle.
Expand CappedBottle to show the objects within the group.
B. Right-click Cap and paste animation.
C. Delete the Fill animation.
11. Test your display:
Click the Start button and ensure an empty bottle moves along
the conveyor, fills, is capped, and then counted. Stop the test
when done.
12. Configure the fill animation on the filling machine so the stream
rectangle is visible when 2250 d timer d 3000.
13. Duplicate the gray rectangle below the capper machine:
AGDe9701SE
14. Animate one rectangle as follows:

A. Configure the visibility animation:
-- Make visible when the timer d 5750.
B. Configure the height animation:
-- Make the vertical percent change from a minimum of
38%to a maximum of 100%.
-- Anchor the animation to the Top of the rectangle.
-- Use a constant range value minimum of 5000 and a
maximum of 5500.
15. Animate the other rectangle as follows:
A. Configure the visibility animation:
-- Make visible when the timer t 5750.
B. Configure the height animation:
-- Make the vertical percent change from a minimum of
100%to a maximum of 38%.
-- Anchor the animation to the Top of the rectangle.
-- Use a constant range value minimum of 5750 and a
maximum of 6250.
16. Align the rectangles so they are on top of each other:

Verify that an empty bottle is filled and capped. Make sure that
the filler stream and the capper work properly.
19. Configure visibility animation on the stop button to only show
when the following tag is true:
{::LinxE_Shortcut]Program:FILLING.Conv_Running}.
20. Configure the visibility animation on the start button to show if a
non-zero number of bottles have been chosen to process (the
Ramp button prevents this from being negative):
Use the following tag:
{::LinxE_Shortcut]Program:FILLING.Bottle_Preset}
AGDe9701SE

Verify that the animations are functioning and that the Local
Message Display is reporting the status of the bottles.
AGDe9701SE
Answers Exercise A
3. If you added the bottles.loc file correctly, it will appear under

your Local Messages:
6. The Diagnostic list.

7. Bottle 1 should have the following configuration:
A. Your Visibility animation should look similar to the
following:
B. Your Fill animation should look similar to the following:
AGDe9701SE
C. Your Horizontal Position animation should look similar to

the following:
8.
following:
AGDe9701SE
9.
A. CappedBottle is found within the Object Explorer:
C. Your Visibility animation should look similar to the

following:
AGDe9701SE
D. Your Horizontal Position animation should look similar to

the following:
12. Your Visibility animation should look similar to the following:
AGDe9701SE
14.
following:
B. Your Height animation should look similar to the following:
AGDe9701SE
15.
following:
B. Your Height animation should look similar to the following:
AGDe9701SE
AGDe9701SE
Lesson 9
Using Tag Placeholders and
Creating a FactoryTalk View SE
Client
x Add tag placeholders to a graphic display
x Create a FactoryTalk View SE Client configuration file
x Run a FactoryTalk View SE Client Session

x Tag placeholders allow for faster development by using one
display to represent a number of similar operations.
x Creating and testing an application is useful for troubleshooting
and allows the user to view and interact at run time with site-level
applications.
Before You Begin Adding Tag Placeholders to a Graphic Display
Use tag placeholders to mark where you want to insert a tag name at
runtime.
Tag Placeholders: A cross-hatch character (#) followed by a number

1 to 500.
At runtime you supply the tag names associated with the particular
operation and these are used in place of the tag placeholders.
Tip " Use the Tag Substitution menu option to replace tag placeholders.
CLIsb9701SE
9--2 Using Tag Placeholders and Creating a FactoryTalk View SE Client
Parameter Files
When you create a graphic display that uses tag placeholders, you
can specify a parameter file that will supply tag names for the tag
placeholders.
This allows you to use different sets of tags with a single graphic
display:
Tag Substitution
Instead of creating parameter files to replace a tag name, you can
replace only what is unique about each tag.
Suppose you have the following tags:

x {::[Enterprise_Shortcut]Fruit_Program:Apples_Count}
x {::[Enterprise_Shortcut]Fruit_Program:Oranges_Count}
x {::[Enterprise_Shortcut]Fruit_Program:Bananas_Count}
You can use tag substitution to replace Apples using the tag
placeholder #1, Oranges using #5 and Bananas using #10.
Displaying Placeholder Parameters

Display parameters run the specified graphic display file:
CLIsb9701SE
Using Tag Placeholders and Creating a FactoryTalk View SE Client 9--3
Parameters specified here override the settings in the Display

Settings dialog box (in the Graphic Display editor):
Display
Parameter
Tags
Use the Display /T<tag> command to list tags that are to be

substituted into the display.
For example, John Hancock would If the file name has a space in it, enclose the name in double quotes.
become “John Hancock”.
Creating a FactoryTalk View SE Client Configuration File
The configuration file defines the run time client. The information in
it includes:
x The name of the FactoryTalk View SE application file that it
connects to at run time
x Run time properties and behavior of the client
x The components that will be started when the connection is made:
Initial Display
Display Parameters
Initial Client Key File
Startup Macro
Shutdown Macro
Tip " The file extension for a client file is .CLI
CLIsb9701SE
9--4 Using Tag Placeholders and Creating a FactoryTalk View SE Client
Running a FactoryTalk View SE Client Session
When you run an application using FactoryTalk View SE Client you

will be able to test the full functionality of your application, such as
animations, tag data, and security.
The FactoryTalk View SE Client can be launched from the toolbar:
Launch SE Client
It can also be launched from the Windows Start Menu and then going
to ProgramsoRockwell SoftwareoFactoryTalk ViewoFactoryTalk
View Site Edition Client.

Open the CCV207_9701SE_DEM1.APA x Add tag placeholders to a graphic display
following tasks: x Create a FactoryTalk View SE Client configuration file
1. Open the Tag Placeholders display. x Run a FactoryTalk View SE Client Session
2. Substitute the tag placeholder #1 for As your instructor demonstrates these procedures, follow along in
Tank_1 on all three tags.
3. On the Tank 1 button, enter Display
“Tag Placeholders” /T Tank_1 as
the release action.
4. Create a FactoryTalk View SE Client
configuration file using Tag
Placeholders as the initial display.
5. Test the display to ensure the tag
placeholders are correct.
6. Point out to students that you have
to press the Tank 1 button in order
to substitute the information at run
time.
CLIsb9701SE
Exercise: Using Tag Placeholders and Creating a FactoryTalk View SE Client 9--5
Exercise: Using Tag Placeholders

and Creating a FactoryTalk View SE
Client
Exercise A In this exercise, you will practice substituting reference tags with tag
placeholders in a FactoryTalk View SE application. You will then
create a FactoryTalk View SE Client to run and test your application.
Context:
You need to add 3 new tanks to your FactoryTalk View SE graphic

display. You will reduce your workload by taking advantage of tag
placeholders.

Directions:

exercise.
Programming exercises, open the CLI_9701SE_A1.APA file.
2. Add the existing graphic display to your graphic displays folder:

C:\SE Class Files\Components to import for labs
\Tankdata.gfx
3. Open the Tankdata graphic display.
4. Add tag placeholders to the graphic display by substituting all
instances of Tank_1 with #1.
5. How many instances of tags were replaced?
6. Open the numeric display to confirm the substitution has

occurred.
7. Type or browse for Display Tankdata /T Tank_1 into
the release action for the Tank 1 button.
8. Repeat for the Tank 2 and Tank 3 buttons, substituting the text
Tank_2 and Tank_3 where needed.
CLIe9701SE
9--6 Exercise: Using Tag Placeholders and Creating a FactoryTalk View SE Client
9. Save and close the Tankdata graphic display.
Tip " Display commands are ignored when issued from FactoryTalk View
Studio design environment.
10. Create and configure a FactoryTalk View SE Client with the

following properties:
x Configuration name: Tank Data
x Type of SE application: Local
x Application connected to: AppliSE (or CLI_9701SE_A1)
x Initial display: Tankdata
x Display parameters: /T Tank_1
11. Run the FactoryTalk SE Client Session you just configured and
test your application.
Tip " If you are prompted to log in, use the user name administrator
and a password administrator.
12. Click the buttons at the top of the display and verify that you see
the different tanks’ data.
13. Review the Diagnostic Bar to see if any errors were generated.
CLIe9701SE
CLIe9701SE
Answers Exercise A
4. Your Tag Substitution dialog box should look similar to the

following:
5. Five instances were replaced.

6. Tank_1 was replaced with #1:
CLIe9701SE
7. The configuration for the Tank 1 button should look similar to

the following:
10. Your FactoryTalk View SE Client Components dialog box

should look similar to the following:
CLIe9701SE
12. You should see the the corresponding tank data for the tank
button you press at the top of the screen:
CLIe9701SE
Lesson 10
Configuring Global Objects in a
What You Will Learn After completing this lesson, you should be able to configure global
objects in a FactoryTalk View SE Application.
These skills are important because using global objects reduces

development time by linking the appearance and behavior of a
graphic object to multiple copies of that object.
Global Objects also promotes consistency between applications by

allowing you to add in your previously created Global Objects when
a new application is created.
Base Objects: The original global object on the global object

display.
Global Objects: Allow you to link the appearance and behavior of a

graphic object to multiple copies of that object in the same
application.
Global Object Displays: Global objects are created on global object

displays.
Reference Objects: Created when a global object is copied onto a

standard display from the Displays folder.
Global Objects
Global objects can be created or added from other displays’ libraries.
When an object is added to a Global Objects graphic display it

becomes a base object that can be referenced from a standard graphic
display.
A global object can be copied onto any number of displays, or

multiple times onto a single display.
CGOsb9701SE
10--2 Configuring Global Objects in a FactoryTalk View SE Application
Global Object Displays
At runtime, when a standard display that contains reference objects is

run, the global object display (or displays) that contains the
corresponding base objects, is loaded in the background.
Global object displays are created similar to a standard display:
You can distinguish between a global object display and a standard

display by the title bar:
Global Object
Display
Standard
Display
Global object displays added to an application do

not count toward the maximum displays allowed
by the activation.
Tip " Global object displays have the file extension .ggfx while standard
graphic displays have the file extension .gfx
Global Object Display Limitations

Global object displays have the following limitations:
Remind students that this is the same x Global object displays have a limit of 3000 tags.
tag limit for the standard displays.
x A global object display cannot be displayed in the FactoryTalk
View SE Client.
x Objects on a global object display cannot be converted to
wallpaper.
Tip " Global Object displays will support Test Display mode, but they
cannot be displayed at runtime.
CGOsb9701SE
Configuring Global Objects in a FactoryTalk View SE Application 10--3
Global Object Organization

Use groups as a way to organize the global objects.
Ungrouping and regrouping objects will cause the

group name to change. Using the same group
name is important to ensure all the linked objects
stay linked. If you ungroup and regroup a base
global object use the same name so the reference
objects will not be broken (i.e., lose the
connection to the base object).
The Object Explorer can be used to select a group and perform an

edit. The Object Explorer makes it easy to navigate to a group or
object when there are a lot of objects or nested objects on a display
or in a global object:
Global Object Limitations

Global objects have the following limitations:
If students ask about RSLogix 5000 x All FactoryTalk View graphic objects can be global objects
faceplates, refer them to the FactoryTalk
View SE User’s Guide. except:
-- ActiveX controls
-- OLE objects
-- HMI tag alarm summary objects
-- Picture objects that have been imported into a display but
not converted to the native FactoryTalk View graphic
format
CGOsb9701SE
x Reference objects can only be linked to base objects within the

same HMI server in a network application, or within the same
application, for a local application.
Configuring Global Objects
When you copy or drag a global object onto a standard graphic

display, the resulting reference object has several new properties
called Link properties.
The Link properties are given default values when the reference
object is created. You can change the default values that are assigned
to a new reference object by setting the global object defaults:
The global object link properties are defined as follows:

x LinkAnimation Default: The LinkAnimation property
determines whether or not the animation assigned to a base object
will be used by the reference object, and if the animation is used,
whether or not the expressions assigned to the base object are
used. The initial default value of this property is Link with
expressions.
x LinkConnections default: The LinkConnections property
determines whether or not the connections assigned to the base
object will be used by the reference object. The initial default
value of this property is True.
CGOsb9701SE
Configuring Global Objects in a FactoryTalk View SE Application 10--5
x LinkSize default: The LinkSize property determines whether or

not the values assigned to the Height and Width properties of the
base object will be used by the reference object. The initial
default value of this property is True.
The number of tags used by the base object’s

connections will count toward the 3000 tag limit
for the display that the reference object is on.
Updating Information
Changes made to the base object will be reflected in the reference
objects linked to it the next time the displays containing the
reference objects are opened, or refreshed by closing and reopening.
A reference object will also be refreshed with information from its

base object when a change is made to the reference object that
requires it to retrieve information from the base object.
Broken Links
When a reference object has a LinkBaseObject property referring to
a base object that no longer exists or is the wrong type of object, it
becomes a broken link object.
A broken link object can be moved and A broken link object is displayed as a rectangle with a red cross and
deleted but no other editing is allowed. a white background:
Broken Link Object
Tip " If a broken link object refers to a base object that has been restored,
it will become a reference object.
CGOsb9701SE
Here’s How To configure global objects.

1. Open the As your instructor demonstrates these procedures, follow along in
application. the associated job aid(s).
2. Open the My Global Objects
display from the Global Objects
folder.
3. In the Bottles folder of Libraries add
the clear bottle to the Global Objects
Test display.
4. Select a new color for the back and
fore colors of the bottle polygon.
5. Change the polygon back style to
solid.
6. Copy the animation from the brown
bottle to your new bottle.
7. Open the standard display Global
Objects Test.
8. Copy your new bottle to Global
Objects Test.
9. Show how you cannot alter the
animations on the reference object.
10. View the Global Object Defaults.
11. Test the display.
CGOsb9701SE
Exercise: Configuring Global Objects in a FactoryTalk View SE Application 10--7
Exercise: Configuring Global

Objects in a FactoryTalk View SE
Application
Exercise A In this exercise, you will practice configuring global objects.
Context:
You should be able to quickly create several objects with similar

appearance and behavior.

Directions:

exercise.
Programming exercises, open the CGO_9701SE_A1.APA file.
2. Add the existing graphic display to the global objects folder:

C:\SE Class Files
\Component to import for labs\mymotors.ggfx
3. Configure a new FactoryTalk View SE Client Session using the
information below:
-- Configuration name: AirCoolers
-- Type of SE Application: AppliSE.APA (or
CGO_9701SE_A1.APA) application.
-- Initial display: aircoolers.
-- Save configuration and open FactoryTalk View SE Client
now.
4. Test the graphic display by performing the following:
A. Click on a cooling blower.
The Motor Popup window will open.
CGOe9701SE
10--8 Exercise: Configuring Global Objects in a FactoryTalk View SE Application
B. Click the ON button.

The motor should become blue, indicating run mode:
Tip " If the cooling blower is yellow or has a fault, turn the SSL off and
stop the feedback. Next, reset faults on the SSL and the cooling
blower.
C. While the motor is running, click the SSL ON button for

Cooling Blower 1.
After a few seconds, the motor should become yellow,
indicating alarm mode.
D. Click on the motor or SSL object to reset the faults.
E. Turn Cooling Blower 1 off and reset the faults to clear the
alarms.
5. Leave the client open and return to your FactoryTalk View SE
application.
6. Open the Aircoolers display.
7. Double-click Cooling Blower 3
8. Right-click the SSL object and then select Global Object
Defaults.
9. What is the default value for LinkAnimation?
10. Close the Global Object Defaults window.

CGOe9701SE
11. Open the Property Panel of the SSL object.

12. Are you able to change the height or width? Why/Why not?
13. Close the Property Panel.

14. Right-click on the ellipse of the SSL object and view the color
animation.
15. Are you able to change the colors? Why/Why not?
16. Are you able to change the expression? Why/Why not?
17. Close the Animation window.

18. In the Global Objects folder, double-click the mymotors display.
19. Configure the global object by accessing the color animation
properties on the ellipse of the SSL object and modifying the
following:
x Change the color of line A (value 0) from blue to white.
x Access the Color animation properties on the largest ellipse of
the motor.
x Change the color of line A (value 0) from gray to white.
x Change the color of line C (value 2) from blue to green.
20. Save the Global Objects display and then close it.
21. Return to the FactoryTalk View SE Client.
22. Observe the colors of the display.
23. Click the BlankPage button.
CGOe9701SE
24. Click the Air Coolers button. Describe what happened:
25. Close the FactoryTalk View SE Client.

CGOe9701SE
CGOe9701SE
Answers Exercise A
9. Link with expressions.

12. No, they are read-only. The LinkSize default is set to true,
therefore the properties of the base object will be used by the
reference object.
15. No, the animation is linked to the base object.
16. Yes, the animation is linked except for expressions.
24. The colors changed after returning to a refreshed screen.
CGOe9701SE
Lesson 11
Switching Languages in a
x Add languages to an applicaiton
x Import and export text strings
x Modify application languages
x Use language commands

x To make an application universal it is important to understand
how to add and change languages.
x In order to modify application language text, you should know
how to export the text, modify it using Microsoft Excel software,
and import the text back into the application.
x In order to change languages during run time, language
commands must be created and used in the application.
Before You Begin Adding Languages to an Application
Application Languages
When you create a new FactoryTalk View application, you must
select a language for the application. The language you select
becomes the default application language:
Windows-supported
languages
SLAsb9701SE
11--2 Switching Languages in a FactoryTalk View SE Application
Adding Languages to an Application

Use the Language Configuration dialog box to add the languages you
want the application to support.
You can add up to 40 languages to an application:
Default language for the

application is English.
Export and Import

text strings
Current language for this
application is English.
Add languages to the
application.
Switching the Current Application Language

When opening an existing application, you select a language from
the list of languages the application supports. The language you
select becomes the current application language:
Text strings in the application that are unavailable in a language will

be treated as undefined.
SLAsb9701SE
Switching Languages in a FactoryTalk View SE Application 11--3
Refer students to FactoryTalk View SE Undefined text strings in an application display as question
User’s Manual for more information marks (?), unless the application is set up to display undefined
about modifying Unicode text files in
Microsoft Excel and in Notepad. strings in the default language.
Importing and Exporting Text Strings
Use the Language Configuration dialog box to export text strings in

an application in order to translate or modify them.
If the application contains multiple languages, you can export text

strings for the selected language only, or for all languages in the
application.
Importing Text Strings
Use the Language Configuration dialog box to import text strings

into an application, after translating or modifying them.
If you are importing text into a network application, you can import
text for multiple HMI servers at the same time.
Select the appropriate option for your application:
If you are importing strings from a Before importing translated or modified text strings, it
Unicode text file, before you click Import, Guideline is recommended to export the current text strings in
in the list of application languages,
select the language of the strings you order to create a backup.
are about to import.
SLAsb9701SE
Text strings that exist in an application, but do not exist in the import
file, are not deleted or modified during the import operation. This
allows you to import only text strings that have been modified.
Before importing text into an application, ensure

that the HMI project components involved are not
in use. If components are being modified
remotely, and the changes are saved after you
import text, the imported text will be overwritten.
Exporting Text Strings
Exporting a Single Language

If you are exporting strings for a single To export strings only for the currently selected language and save
language only, be fore you click Export, them to a text file in Unicode format, select the option: Export
in the list of application languages,
select the languages of the strings you strings for <aa--BB> to one or more Unicode text files (where aa--BB
want to export. is the RFC1766 code for the selected language):
SLAsb9701SE
Exporting Multiple Languages

To export strings for all languages in the application and save them
to a Microsoft Excel spreadsheet, select the option: Export strings for
all languages to an Excel spreadsheet. This option allows you to
translate or modify multiple languages at the same time:
Refer students to FactoryTalk View SE Optimizing duplicate strings allows any string that occurs multiple
User’s Manual for more information on time in the application to be displayed only once in the Excel
working with duplicate text strings.
spreadsheet.
Before exporting text in an application, ensure

that all the HMI project components containing
text to be exported are not in use. If project
components are being modified remotely, and they
have not been saved, the exported file might not
contain the unsaved changes.
Modifying Application Languages
Modifying Text Strings Exported to an Excel Spreadsheet

Text strings exported for all languages in an application are saved in
an Excel spreadsheet. This allows you to translate or modify multiple
languages at the same time.
SLAsb9701SE
The spreadsheet provides the following information for each

exported text string:
x Server identifies the name of the HMI server that contains the
exported text string.
x Component Type identifies the type of component that contains
the text string. The component type can be either a standard
graphic display or a global object display.
x Component Name indicates the name of the standard display,
global object display, or local message file that contains the text
string.
x Description identifies where the text string is used in the
standard display or global object display.
x REF displays a unique reference number beside the first instance
of each text string with duplicates in the HMI server.
x The <RFC1766 name> column contains the exported text strings.
The number of columns depends on the number of languages in
the application when the strings were exported.
FactoryTalk View SE software requires that parts of the Excel
spreadsheet file remain as they were when exported:
x Do not change the default order of the Server, Component Type,
Component Name and Description columns.
x Do not insert any blank rows or columns in the spreadsheet. The
import operation will stop at a blank row or column. Anything
after that will not be imported.
x You can change the order of the columns containing the text
strings for each language. However, if you move one of the
columns, remember to move the associated REF column with it if
one exists.
The REF column must always be to the left of the strings column.
x Do not delete a REF column, or any of the unique duplicate string
identifiers in a REF column.
x Do no delete a row that contains a unique duplicate string
identifier in the REF column.
Modifying Text Strings Exported to a Unicode Text File in

Notepad
Text strings exported for the selected application language are saved
in a text file in Unicode format.
SLAsb9701SE
The file is sorted alphabetically by component name and then

numerically by string reference number. Each string reference
number refers to a different object in the component. In the
following example, string reference 1 might refer to a push button in
the graphic display called Pump station:
In the translated text file, the only text that needs to be modified is
the text inside the quotation marks in the string definition column:
Tip " The string reference number is unique to FactoryTalk View.
Modifying the component type or string FactoryTalk View SE software requires that parts of the Unicode text
reference number prevents FactoryTalk file remain as they were when exported:
View SE software from identifying the
object correctly when you import the x Do not change the entries in the component name column, unless
text. the component was renamed in the application after the text was
exported.
x Do not modify the component type or string reference number.
SLAsb9701SE
Using Language Commands
Refer students to FactoryTalk View SE Use the Language command to switch languages at run time.
User’s Manual for more information
about supporting multiple languages by The Language command uses the following syntax:
setting up individual libraries.
Language <RFC1766 name>
Where <RFC1766 name> is a code name for the language you
want to switch to.
To allow language switching at run time, provide the operator with a
way to run the Language command for each language the application
supports.
Tip " If you create buttons to allow language switching at run time, be
If students ask, explain that the flag aware that button captions will be translated when a language switch
graphics were imported into the occurs. To avoid confusion, use graphics instead of text to represent
application.
the different languages.
SLAsb9701SE

1. Open the x Add languages to an application
application. x Import and export text strings
2. Add the Spanish es- MX language x Modify application languages
to your application. x Use language commands
3. Export the English en- US language
into a Unicode text file. As your instructor demonstrates these procedures, follow along in
4. Open the file in the Notepad the associated jobs aid(s).
software.
5. Modify some of the English text
strings on a graphic display with
Spanish text such as Hola or
Buenos Dias.
6. Save the new text file.
7. Import the new text file.
8 Open the display which contains the
modified text from Notepad.
9. Create a button configured to use
the Language command to change
the current language to English.
10. Create another button configured to
use the Language command to
change the current language to
Spanish.
11. Test your display.
SLAsb9701SE
SLAsb9701SE
Exercise: Switching Languages in a FactoryTalk View SE Application 11--11
Exercise: Switching Languages in

a FactoryTalk View SE Application
Exercise A In this exercise, you will practice switching languages.
Context:
You must be able to change an application’s language in order to

make your application universal.

Directions:

exercise.
Programming exercises, open the SLA_9701SE_A1.APA file.
2. Export text strings into a Unicode text file located in the root
directory of C:\.
3. Open the C:\AppliSE_AppliSE_en--US.txt file that was just
created.
Tip " Your file may have been exported as

C:\SLA_9701SE_A1_SLA_9701_A1_en--US.txt.
SLAe9701SE
11--12 Exercise: Switching Languages in a FactoryTalk View SE Application
4. Modify the application language by scrolling down to the Graphic

Display aircoolers tags and find and replace the following text:
5. Save the text file as AppliSE_AppliSE_fr--FR.txt.

6. Add the French (France) language to your FactoryTalk View SE
application.
7. Import the AppliSE_AppliSE_fr--FR.txt file.
8. Return to your FactoryTalk View SE application and open the
aircoolers display.
9. Add a button near the “BlankPage” button.
SLAe9701SE
10. Use the language command and configure the button to have a
release action of English (United States), en--US.
11. Type EN in the Caption field of the Up Appearance tab and select
any color.
12. Duplicate the EN button and move it above the first EN button.
13. Use the language command and configure the button to have a
release action of French (France), fr--FR.
14. Change the Up Appearance caption to FR and select any color.
15. Save your changes to the display.
16. Launch your FactoryTalk View SE Client named AirCoolers.
17. Click the FR button.
18. What do you show on the language buttons? Why?
19. Export French text strings into a Unicode text file located in the
root directory of C:\.
Tip " Select the French language in the Language Configuration dialog
box.
20. Open the C:\AppliSE_AppliSE_fr--FR.txt file.
Tip " Your file may have been exported as

C:\SLA_9701SE_A1_SLA_9701SE_A1_fr--FR.txt.
21. Save the file as C:\New French Text.txt

22. Find the two buttons in the air coolers display.
Depending on when you exported, your .txt file may display the
button captions as “EN” and “FR”, or “?” and “?”.
23. If your button captions display a ?, change them to EN and FR.
24. Delete all rows in the file except the header and the two button
rows:
SLAe9701SE
25. Save the .txt file.

26. Import the New French Text.txt file.
Tip " Select the French language in the Language Configuration dialog
box.
27. Return to your FactoryTalk SE Client.

28. Click BlankPage.
29. Click Air Coolers.
The two language buttons should have a caption for the French
language.
30. Close your FactoryTalk View SE Client.
SLAe9701SE
SLAe9701SE
Answers Exercise A
7. The import export wizard should look like the following

graphic:
10. In the Release action field of the Button Properties dialog box,
click the ellipsisoAll Commands and
MacrosoLanguageoNextoEnglish (United States), en--US.
18. A question mark appears on the buttons. The French language
was not recorded for the button caption. The buttons were
created after the import of the French language.
SLAe9701SE
29. Your final display should appear similar to the following:
SLAe9701SE
SLAe9701SE
Lesson 12
Configuring Alarms in a
x Create HMI tags in a FactoryTalk View SE application
x Configuring Alarms for HMI tags
x Configure the HMI tag alarm setup editor
x Create or modify an HMI tag alarm summary
x Enable FactoryTalk Alarms and Events on an RSLinx Enterprise
Device Server
x Create or modify a FactoryTalk Alarms and Events summary

x HMI tags can be used to define alarms within the HMI
application.
x Using the HMI tag alarm setup editor to specify the maximum
update rate, whether or not an alarm will be generated when an
HMI tag value is approaching normal range, and how alarm
message printing and logging are handled when redundancy is
enabled.
x Developing an alarm summary interface is important for the user
to be able to view, acknowledge, and silence alarms.
x FactoryTalk Alarms and Events allows multiple FactoryTalk
products to share a common view of alarms and events.
x The FactoryTalk Alarms and Events Summary lets an operator
acknowledge, disable, enable, suppress, filter, and sort alarms
during run time with enhanced setup features compared to the
HMI Tag Alarm summary
Data Source: Specifies where the data for a tag will come from.
Tag Type: Specifies how FactoryTalk View SE software interprets

data from a programmable controller or a data server, and how it is
represented in FactoryTalk View SE software.
AMSsb9701SE
12--2 Configuring Alarms in a FactoryTalk View SE Application
Creating HMI Tags in a FactoryTalk View SE Application
In addition to the tags you create, When you create an HMI tag you assign it a type and data source.
FactoryTalk View SE software provides a
set of system tags. There are analog,
digital, and string system tags.
HMI Tag Type
Data Source
Tag Type
The three types of tags that you can create are:
Analog:
Analog tags store a numeric value from a range of values defined for
the tag. Use them to represent devices that can have a range of values
such as temperature, pressure, flow, or the position of a rotary
control.
Digital:
Digital tags will accept any numeric value. Zero will be written as
False (0) and any non-zero number will be written as true (1). Use
them to represent devices that have two states, on or off, such as
switches, contacts and relays.
String:
String tags store ASCII strings that can be a string of characters or
whole words. The maximum size allowed for a string is 82
characters.
Data Source
The data source specifies where an HMI tag’s data comes from. The
data source for analog, digital, or string HMI tags can be device or
memory.
AMSsb9701SE
Configuring Alarms in a FactoryTalk View SE Application 12--3
Device:
An HMI tag with device as its data source receives data from a
source external to FactoryTalk View SE software. The data can come
from a programmable controller or other device via RSLinx, or from
another OPC server.
Memory:
You can specify that a memory tag’s An HMI tag with memory as its data source receives data from
value be retained even if the HMI server FactoryTalk View SE software internally. A memory tag can be used
is shut down.
to store values internally. Its value at start up is defined by the Initial
Value setting.
System:
For system tags, which can be analog, digital, or string types, the
data source is a special type called System.
Configuring Alarms for HMI Tags
Alarm set up for HMI analog and digital Alarms are an important part of most plant control applications
tags are detected at the HMI server. because they alert operators when something goes wrong.
An alarm can signal that a device or process has ceased operating

within acceptable, predefined limits, or it can indicate breakdown,
wear, or a process malfunction. Often, it is also important to have a
record of alarms and whether they were acknowledged.
In FactoryTalk View Site Edition software, you can specify alarm

conditions for tags you want to monitor in an HMI server’s tag
database.
Tag Editor
Alarm Editor
AMSsb9701SE
Using HMI tag alarms, you can:

x Monitor any analog or digital HMI tag for alarms, up to a
maximum of 40,000 tags per HMI server (10,000 of these can be
analog tags)
x Display the most recent 2,000 alarm transactions in an HMI tag
alarm summary
x Define up to eight different severity levels to distinguish alarms
visually
x Use system default messages or custom messages to describe
HMI tag alarms
x Log alarm messages to a file, to a printer, or to both
x Suppress HMI tag alarms for maintenance and tuning purposes
x Associate a command or macro with an alarm to provide custom
handling of the alarm
x Share alarm information with other FactoryTalk View SE
components
x Use the Acknowledge bit to synchronize alarm acknowledgement
on redundant HMI server pairs
x Use the AlarmEvent command to respond to alarm detection
algorithms you create for notification, logging, printing, and for
displaying in HMI tag alarm summaries
Configuring the HMI Tag Alarm Setup Editor
Point out to students that configurations In the Alarm Setup editor you specify the general features of all
in the Alarm Setup editor will effect all alarms for the HMI server where your application is running.
alarms. If students want to configure an
individual alarm they will do that in the
HMI tags editor. Alarm Setup Editor
AMSsb9701SE
This editor has three tabs in which you specify the following:
x Setup: Whether or not an alarm will be generated when a tag
value is approaching normal range.
x Severities: Logging destinations and annunciation for alarm
severities and events.
x User Messages: User default messages for the alarm log file and
printer.
Creating or Modifying an HMI Tag Alarm Summary
When an alarm is detected, notification is sent to connected

FactoryTalk View SE clients, where operators can view HMI tag
alarm information recorded in the HMI server computer’s memory:
Alarm Summary Display
A single HMI tag alarm summary can display alarms from multiple
HMI servers located on different computers. Each HMI server
maintains a list of up to 2,000 alarms.
As new alarms occur, they are displayed at the top of the list in the
alarm summary. When the list is full and a new alarm is generated,
the alarm at the bottom of the list (the oldest alarm) is acknowledged
automatically by the system, and then dropped from the list.
In the alarm log file, alarms acknowledged automatically by the

system are identified by SysAk (system0acknowledged) in the
TransType (transaction type) field.
Refer students to the FactoryTalk View Alarms are also dropped from the alarm summary when they are out
SE User’s Guide for more information of alarm, and acknowledged manually. When alarms are dropped,
regarding alarm commands.
they are removed from memory. When the AlarmOff command is
run, the entire contents of the alarm summary are erased.
AMSsb9701SE
For a more advanced alarm summary, When setting up an HMI tag alarm summary, you can specify which
FactoryTalk Alarms and Events alarm information to display, and how the information will appear in
summary will be discussed later in this
lesson. the alarm summary:
Alarm information
objects
Acknowledging Alarms
An operator can acknowledge HMI tag alarms displayed in an alarm
summary or some other HMI tag alarm display. Acknowledging an
alarm does not correct the condition causing the alarm, but indicates
that the operator is aware of the alarm.
For example, a tag representing A tag, not an alarm, is acknowledged: a single tag might cause
temperature might trigger Warm, Hot, several alarms.
and Overheat alarms by the time it is
acknowledged.
One acknowledgement is all that is required for all previous and
The tag could also go in and out of current alarms for a tag, so alarm log files often show fewer
alarm several times before being
acknowledged. acknowledgements than alarms.
Acknowledge and
Silence Buttons
AMSsb9701SE
To acknowledge HMI tag alarms, you can use any of these methods:
x Click Acknowledge or Acknowledge All in the HMI tag alarm
summary
x Use the FactoryTalk View command Acknowledge by itself, or
with parameters to name a tag or group of tags
x Use the FactoryTalk View command AcknowledgeAll
Unacknowledged alarms remain outstanding until

the HMI tag alarm summary is full, alarm
monitoring is turned off, or the system is shut
down.
FactoryTalk Alarms and Events
FactoryTalk Alarms and Events allows multiple FactoryTalk

products to participate together in a common, consistent view of
alarms and events throughout a FactoryTalk system.
The diagram below shows a high-level view of the components of

the FactoryTalk Alarms and Events system:
The Factory alarms and events feature supports device-based and

tag-based alarm monitoring and allows multiple FactoryTalk
products to use the same alarm and event information.
AMSsb9701SE
1. Device-based alarm monitoring: With device-based alarm

monitoring, alarm instructions, available with RSLogix 5000
version 16 or later, are programmed and then downloaded into
Logix5000 controllers. The controller detects alarm conditions
and notifies RSLinx Enterprise of alarm states. A Rockwell
Automation Device Server (RSLinx Enterprise) extracts the alarm
information and publishes it to FactoryTalk Alarms and Events
services.
Use device-based alarm monitoring with: Logix5000 controllers,
programmed with RSLogix 5000 software version 16 or later, and
when communicating through Rockwell Automation Device
Servers (RSLinx Enterprise).
2. Tag-based alarm monitoring: A Tag Alarm and Event Server
uses tags to monitor programmable controllers for alarm
conditions. When an alarm condition is detected, the server
publishes the information to FactoryTalk Alarms and Events
services.
Use tag-based alarm monitoring with:
x PLC-5 or SLC 500 devices, communicating through Rockwell
Automation Device Servers (RSLinx Enterprise)
x RSLinx Classic or RSLinx Gateway
x Third-party controllers, communicating through OPC-DA
servers
x Logix5000 controllers that have not been programmed with
pre-built alarm instructions available in RSLogix 5000
software version 16 or later
3. FactoryTalk Alarms and Events services: Both device-based
and tag-based alarms and events are published to FactoryTalk
Alarms and Events services, which then routes the information to
FactoryTalk Alarms and Events objects hosted in FactoryTalk
View, the alarm and event history log, and to diagnostic logs and
audit logs.
To use alarm and event logging, install 4. Alarm and Event Historian and Log: The Alarm and Event
Microsoft SQL Server 2005 Express Historian is a logging component that installs silently as part of
SP2 separately, or use an existing
Microsoft SQL Server 2000 SP4 or the alarms and events software. It manages connections between
Microsoft SQL Server 2005 database. alarm servers and databases and logs data from each alarm server
to an alarm history database. An Alarm and Event Log Viewer
allows viewing and printing data from alarm history databases.
Third-party database tools can also retrieve, view, analyze, and
print alarm history information.
AMSsb9701SE
5. Diagnostic and Audit Logs: FactoryTalk Diagnostics routes

messages generated by FactoryTalk Alarms and Events to local
logs on the computers hosting FactoryTalk components, and
optionally to a centralized database log. Audit messages are also
routed to the local log and to the FactoryTalk Audit Log if
FactoryTalk AssetCenter is installed.
6. Alarm and Event Setup and Monitoring: FactoryTalk Alarms
and Events includes a number of software components that allow
engineers and operators to define alarm conditions, set up alarm
servers, view and interact with alarm conditions, and view and
run reports on historical alarm information.
FactoryTalk Alarms and Events Graphic Objects

Information from tag-based or device-based alarm monitoring can be
displayed and interacted with, in graphic displays at run time using
the alarm and event graphic objects.
FactoryTalk Alarms and

Events Summary Object
Alarm and Event

Banner Object
Alarm and Event

Log Viewer Object
AMSsb9701SE
These objects are available in the FactoryTalk View Graphics editor

on the Objects/Alarm and Event menu, and include:
x Alarm and Event Summary: Lets an operator acknowledge,
disable, enable, suppress, filter, and sort alarms during run time.
x Alarm and Event Banner: Lets an operator monitor and respond
to the most serious alarms requiring immediate attention.
x Alarm Status Explorer: Lets an operator enable or disable
alarms, suppress or unsuppress alarms, and view operator
comments.
x Alarm and Event Log Viewer: Lets an operator view, sort, filter,
and print historical alarm information stored in Microsoft SQL
Server databases.
Alarm and Event Log Viewer
For example, the number of alarms that You can also use FactoryTalk alarm and event expression functions
are in alarm and unacknowledged. to animate objects and display alarm count information.
AMSsb9701SE
Enabling FactoryTalk Alarms and Events on an RSLinx

Enterprise Device Server
By default, Enable alarm and event Check Enable alarm and event support to enable alarm and event
support is always unchecked (disabled). support and to activate the options on the properties dialog.
Enable Alarm and

Event Support
Enable History
Tip " Uncheck Enable history if you are not logging historical data.
Support for FactoryTalk Alarms and Events and

support for a redundant (secondary) RSLinx
Enterprise server cannot be enabled at the same
time.
To enable support for FactoryTalk Alarms and
Events, you must first disable support for a
redundant server on the Redundancy tab, then
enable support for FactoryTalk Alarms and
Events.
AMSsb9701SE
You must also enable FactoryTalk Alarms and Events for each
shortcut you want supported:
Shortcut
Enable Alarms
and Events
Enable: Select Yes from the dropdown list to enable FactoryTalk

Alarms and Events support for the selected shortcut.
For more information on buffering, refer Buffer Timeout (min.): Enter the length of time you want RSLinx
to the FactoryTalk View Site Edition Enterprise to buffer alarms in the event it becomes disconnected
Help.
from the selected Logix5000 controller. To disable the buffer, enter 0
(zero).
Creating or Modifying a FactoryTalk Alarms and Events

Summary
The FactoryTalk Alarm and Event Summary object subscribes to

alarms and events from one or more areas in the FactoryTalk system
and allows an operator to monitor and interact with those alarms and
events.
AMSsb9701SE
For information on adding an object to a The Alarm and Event Summary is hosted on a FactoryTalk View SE
graphic display in FactoryTalk View display as an object:
Studio, refer to the FactoryTalk View Site
Edition Help.
Toolbar
Event List
Details Pane
Status Bar
The Alarm and Event Summary consists of four parts:

x Toolbar: The toolbar is displayed at the top of the Alarm and
Event Summary and allows the operator to perform operations
such as acknowledge alarms, filter the events displayed or show
alarm faults.
x Event List: The top part of the Alarm and Event Summary
displays a list of events, divided into columns. The columns
across the top of the event list represent data fields in the Alarm
and Event Summary display.
x Details Pane: The bottom part of the Alarm and Event Summary
displays information about the event that is selected in the event
list. If multiple events are selected the following text is displayed
in the details pane, “Multiple messages are selected”. Select one
message to view the message details.
x Status Bar: The status bar at the bottom of the Alarm and Event
Summary shows the status of the connections to alarm and event
servers, the number of alarms in various states, and what filter
and sort order if any is applied to the event list.
AMSsb9701SE
Use the Appearance tab in the FactoryTalk Alarm and Event

Summary Properties dialog box to change how information is
displayed in the Alarm and Event Summary, and how users interact
with the information at run time.
Show Details
Pane
Toolbar
Column
Headings
Row
Text
Status
Grid Bar
AMSsb9701SE
Here’s How To perform the following tasks::

1. Open the x Create HMI tags in a FactoryTalk View SE application
application. x Configuring Alarms for HMI tags
2. Open the Tag Database editor. x Configure the HMI tag alarm setup editor
3. Create a digital alarm named horn x Create or modify an HMI tag alarm summary
in the Alarms folder (Alarms\horn).
Use memory as the data source. As your instructor demonstrates these procedures, follow along in
4. Configure the Alarm Setup editor for the associated job aid(s).
the following:
S Severity 1 Annunciation: External
Bell (Alarms\horn)
S Severity 2 Annunciation: External
Bell (Alarms\horn)
S User Msgs In Alarm File and
Printer Messages:
\11d \8t InAlm Tag \40n \15v \10u
\10l
5. Open the Alarms.gfx display.
6. Add an HMI Tag Alarm Summary
object to the display.
7. Insert the Tag Name and Alarm
Label objects into the HMI Tag
Alarm Summary object.
8. Save and test your display.
9. Show students how to perform the
following:
S Enable alarms
S Generate alarms
S Acknowledge alarms
AMSsb9701SE
Here’s How To perform the following tasks for FactoryTalk Alarms and Events:
Demonstrate the following tasks: x Enable FactoryTalk Alarms and Events on an RSLinx Enterprise
1. Enable RSLinx Enterprise to support Device Server
FactoryTalk Alarms and Events.
x Create or modify a FactoryTalk Alarms and Events summary
2. Modify the LinxE_Shortcut data
server to enable alarm and event As your instructor demonstrates these procedures, follow along in
support. the associated job aid(s).
3. Open the Alarm and Event
Summary display.
4. Add an Alarm and Events
Summary object to the display.
5. Show students some of the object
features they can configure.
6. Save and test your display using the
Test Display button.
7. Enter a value of 100 in the numeric
input at the bottom of the display.
8. Show students how to view alarm
details and acknowledge the alarm.
AMSsb9701SE
Exercise: Configuring Alarms in a FactoryTalk View SE Application 12--17
Exercise: Configuring Alarms in a

Exercise A In this exercise, you will practice the following:

x Create HMI tags in a FactoryTalk View SE application
x Configuring alarms for HMI tags
x Configure the HMI tag alarm setup editor
x Create or modify an HMI tag alarm summary
Context:
You must be able to configure alarms so that the operator is aware of

dangerous and abnormal operation of the control system. Configure a
screen that will be used to display and acknowledge HMI tag alarms
for your FactoryTalk View SE application.
Directions:

exercise.
Programming exercises, open the AMS_9701SE_A1.APA file.
2. Open the Tag Database editor.

3. Create a new HMI tag folder named Alarms.
4. Create the following 5 HMI tags. Accept all the defaults, and use
memory as the data source:
AMSe9701SE
12--18 Exercise: Configuring Alarms in a FactoryTalk View SE Application
5. Configure an alarm for the digital HMI tag, Alarms\digital1,

with the following properties:
x Alarm Type: On
x Alarm Label: Pressure Switch
x Severity: 2
x In Alarm Messages: User Defaults
x Alarm Identification: Appstart C:\SE Class
Files\Alarm\alarminfo.htm
Tip " You must type the Appstart path C:\SE Class
Files\Alarm\alarminfo.htm into the Program field of the Command
Wizard dialog box.
x Acknowledge Bit: Alarms\ack (Auto Reset)

x Handshake Bit: Alarms\Handshake (Auto Reset)
6. Configure an alarm for the analog HMI tag, Alarms\analog1,
with the following properties:
Threshold 2 Threshold 4 Threshold 6 Threshold 8

Threshold: 10 Threshold: 20 Threshold: 80 Threshold: 95
Decreasing Decreasing Increasing Increasing
Label: way too cold Label: too cold Label: too hot Label: way too hot
Severity: 1 Severity: 3 Severity: 3 Severity: 1
In Alarm Messages: In Alarm Messages: In Alarm Messages: In Alarm Messages:
System Defaults System Defaults System Defaults \11d \8t This temp is
HOT HOT HOT \40n
7. Configure the HMI tag alarm setup editor with the following
properties:
x Severity 1 Annunciation: External Bell (Alarms\horn)
x Severity 2 Annunciation: External Bell (Alarms\horn)
x User Msgs In Alarm File and Printer Messages:
My User message on \11d \8t InAlm Tag \40n \15v \10u \10l
8. Add an existing graphic display to your FactoryTalk View SE
application using the following path:
C:\SE Class Files\Components to import for labs\Alarms.gfx
9. Open the Alarms graphic display.
10. Create an HMI tag alarm summary object on your display.
AMSe9701SE
11. Modify the HMI tag alarm summary by inserting the following
items into your HMI tag alarm summary object:
x Alarm Time
x Tag Name
x Tag Value
x Alarm Label
x Alarm Severity
x Operator Name
12. Modify the HMI tag alarm summary by showing only the
following buttons in the HMI tag alarm summary:
x Ack Current
x Ack All
x Silence Current
x Identify
x Filter
x Sort
13. Save the changes to your display.
14. From the Tools menu, select Launch SE Client.
15. Configure a FactoryTalk View SE Client to have the following
properties:
x Name: Alarms
x Type of Application: Local
x Application to connect to: AppliSE (or
AMS_9701SE_A1.APA)
x Initial display: Alarms
16. Test the Alarm System by performing the following;
A. Click the Enable Alarms button to activate the alarm
system.
B. Generate alarms by changing the values of the digital and
analog tags at the bottom of the screen.
C. Acknowledge and Silence the alarms.
D. What happens to the entries in the HMI tag alarm summary
object when you press the acknowledge button?
AMSe9701SE
E. How are the handshaking, acknowledgment and horn bits

changed?
F. Select the Alarms\digital1 tag when it is in alarm. Click the

Identify button. What happens? Why?
G. Click the Alarm Log Viewer button to open a historical log

of all alarms.
H. Configure the Alarm Log Viewer.
17. Close the FactoryTalk View SE Client.
18. Minimize or close your Factory Talk View SE application.
Exercise B In this exercise, you will practice configuring a FactoryTalk Alarms

and Events monitoring system.
Context:
You must be able to configure alarms so that the operator is aware of

dangerous and abnormal operation of the control system. You are
required to configure a FactoryTalk Alarms and Events summary and
enable FactoryTalk Alarms and Events on an RSLinx Enterprise
device server.
Tip " The alarms have been configured in your RSLogix 5000 application.
The steps in this lab will show you how to display these alarms in
your FactoryTalk View SE application.
Directions:

exercise.
Programming exercises, open the AMS_9701SE_B1.APA file.
AMSe9701SE
2. Modify the LinxE_Shortcut device server to enable alarm and

event support. Clear the Enable history checkbox.
3. Access the Communications Setup editor and enable Alarms &
Events.
4. Add the C:\SE Class Files\Components to import for
labs\Alarm and Event Summary.gfx display to your HMI
graphic displays.
5. Open the Alarm and Event Summary display.
6. Add an Alarm and Events Summary object to the display.
7. Modify the Alarm and Event Summary object toolbar to
display the following buttons:
x Acknowledge
x Acknowledge with Comments
x Acknowledge All
x Suppress Alarm
x Reset Alarm
x Run Alarm Command
x Alarm Details
x Alarm Faults
x Filter List
x Details Pane
x Refresh
8. Modify the Alarm and Event Summary object to include a
column that displays the Current Value.
9. Save the changes you made to the display.
10. Test your display by performing the following:
A. Click the Test Display button.
B. Enter a value of 95 in the Numeric Input at the bottom of the
display.
C. Right-click the alarm and select View Alarm Details.
D. View the alarm details and then close the View Alarm Details
dialog box.
E. Right-click the alarm and select acknowledge.
11. Stop the test of the display.
AMSe9701SE
Answers Exercise A
5. The Alarm States configuration for the Alarms\digital1 tag

The Advanced alarm configuration for the Alarms\digital1 tag

AMSe9701SE
6. The Alarms Thresholds configuration for the Alarms\analog1

tag should look similar to the following:
7. The Severity configuration for the Alarms Setup editor should

look similar to the following:
AMSe9701SE
The User Msgs configuration for the Alarms Setup editor

11. Your HMI tag alarm summary object should now look similar
to the following:
12. The following buttons should now be visible at the bottom of

your HMI tag alarm summary object:
16.
D. When you acknowledge the alarms, the alarm is no longer
flashing and changes text color. The Alarms\ack bit goes
high and the Alarms\horn bit changes to 0.
AMSe9701SE
E. The Alarms\ack bit is changed by clicking the Ack Current

or Ack All buttons. The Alarms\handshaking bit is changed
by disabling the alarm condition for the Alarms\digital1 tag.
The Alarms\horn bit is changed by clicking the Silence or
Ack buttons.
F. The Identify button launches the Alarms Identification that
you programmed, a website explaining how the operator
should handle the scenario.
Answers Exercise B
2. Your RSLinx Enterprise Server Properties dialog box should

look similar to the following:
AMSe9701SE
3. Your Communications Setup editor should look similar to the

following:
7. Your Alarm and Event Summary Properties Toolbar tab

AMSe9701SE
8. Your Alarm and Event Summary Columns tab should look

similar to the following:
AMSe9701SE
AMSe9701SE
Lesson 13
Creating and Viewing a Data Log
Model in a FactoryTalk View SE
Application
x Create or modify a data log model
x View a data log
These skills are important because correctly configuring a data log

model ensures that data can be viewed on a trend. Data logs provide
a historical record of data from an application.
Data Log: A FactoryTalk View component that collects and stores

tag values. A single data log model can log data for up to 10,000
tags.
Data Log Model: Defines which tags to log data for, when to log the
data, and where to log the data.
At run time, up to 20 data log models can run simultaneously on

each FactoryTalk View SE Server.
File Set: A type of storage format used to log data to proprietary file
sets with the extension .DAT.
If you choose the ODBC storage format, Log File Identifier String: A user-defined string, up to 20
long file names apply only to the backup characters long, which becomes part of the log file’s name if long
files.
file names are supported.
ODBC backup files are stored as binary ODBC Database: A type of storage format used to log data to tables
files which you cannot view. in an ODBC database using an ODBC data source such as Microsoft
SQL Server or Oracle.
DLMsb9701SE
13--2 Creating and Viewing a Data Log Model in a FactoryTalk View SE Application
Creating or Modifying a Data Log Model
A data log model can be created similarly to that of a new graphics

display:
Use the Data Log Models editor to configure the Setup tab to:
x Specify a log file identifier string
x Specify a storage format
x Create a description for the data log model
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.
Selecting the ODBC Database Format

The path and filename are required even When you select ODBC database as the storage format, type the path
if you are using the default ODBC and file name of the ODBC data source, and specify the ODBC
location.
tables that will be used, or create new tables.
Tip " If FactoryTalk View cannot create the tables automatically, you will
have to open the database using its editing tool, and create the tables
manually.
DLMsb9701SE
Creating and Viewing a Data Log Model in a FactoryTalk View SE Application 13--3
Storage Format
Create Tables
ODBC backup files are stored as binary ODBC storage format will log data to tables in an ODBC data source
files which you cannot view. such as Microsoft SQL Server or Oracle. If you log to an
ODBC-compliant database, you can view the data in trends and use
third-party, ODBC-compliant tools to analyze and create reports
from the data.
Delete old records from the ODBC database using standard relational
database tools or SQL queries:
Purge ODBC
Database
You can also set up FactoryTalk View to delete (purge) records in the
ODBC database after a specified time.
DLMsb9701SE
Selecting the File Set Format

File set storage format will log data to a If the data log model uses file sets, you can set up data logging to
proprietary file sets with the extension create new file sets:
.DAT.
x Periodically
You cannot view these files except with
trends. x At specified times
x When a particular event occurs
x 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.
You can also set up the file management to delete file sets after a
specified period or once a specified number of file sets has been
created. Clear the check boxes under Delete Oldest Files to never
delete file sets:
Start New Files

Frequency Settings
Delete Oldest Files

Frequency Settings
DLMsb9701SE
Selecting Tags to Log

In the Tags in Model tab you identify which tags the model will log
data for:
Browse for Tags
Add or Remove
Tags in Model
The total number of characters and spaces allowed for the path and
name of a tag in a data log model is 255.
Viewing a Data Log
Naming Log File Sets

Tell students the default location of the When you create a log file set, the set is given a name automatically.
files is in the Trending Data folder of The name is based on the date the file was created, and the type of
their HMI project folder.
data it contains. The maximum length of a log file set’s name,
including its path, is 200 characters.
DLMsb9701SE
File sets use the following file name format:

YYYY MM DD NNNN <Log File Identifier String> <(type)>.dat
where:
x YYYY is the year
x MM is the month
x DD is the day
x NNNN is the sequential file identifier
This number indicates the sequence files were created in. You can
have up to 9999 files per day. At midnight, the sequence starts
again at 0000.
x <Log File Identifier String> is a text string you can specify to
help identify the log file. The maximum string length is 20
characters.
x <(type)> is the file type. The type is enclosed in parentheses.
There are three file types:
-- Tagname
-- Float (for analog and digital tag values)
-- String
An example of the string file type is shown below in MicrosoftR
Excel software:
Default Naming
Convention
Date and Time

Logging Started
Date and Time

Logging Stopped
Naming ODBC Tables

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.
DLMsb9701SE

Open the CCV207_9701SE_DEM1.APA x Create or modify a data log model
following tasks:. x View a data log
1. Create a data log model with a log As your instructor demonstrates these procedures, follow along in
file identifier string named Model.
2. Show students the different tabs and
what they can configure.
3. Add tags into your model to log.
4. Open the DataLog display. Show
students the DataLogOn and
DataLogOff commands.
5. Test your display and log data for
several seconds.
6. Show students the log files that were
created.
DLMsb9701SE
DLMsb9701SE
Exercise: Creating and Viewing a Data Log Model in a FactoryTalk View SE Application 13--9
Exercise: Creating and Viewing a

Data Log Model in a FactoryTalk
View SE Application
Exercise A In this exercise, you will be creating a flat file data log model.
Context:
You must be able to configure a data log to store changes in tag

values to a file. Before you can create a historical trend, you need to
collect the data in a file set.

Directions:

exercise.
Programming exercises, open the DLM_9701SE_A1.APA file.
2. Create a new data log model with the following properties:

x Description: Trending Data Log
x Log File Identifier String: Historical Trending
x Log Periodically Interval: 1 second
x Add the following tags to the Tags in Model:
3. Save the data log model as Trending Data.

4. Test the data log model by performing the following:
A. Issue the DataLogOn command for the data log model
Trending Data.
Tip " Use the Command Wizard to automatically build the command.
DLMe9701SE
13--10 Exercise: Creating and Viewing a Data Log Model in a FactoryTalk View SE Application
B. After several seconds issue the DataLogOff command for

the data log model Trending Data.
C. In explorer, navigate to the following folder: C:\Documents
and Settings\All Users\Documents\RSView
Enterprise\SE\HMI
Projects\AppliSE\DLGLOG\Trending Data
Tip " Your navigation may be C:\Documents and Settings\All

Users\Documents\RSView Enterprise\SE\HMI
Projects\DLM_9701SE_A1\DLGLOG\Trending Data
D. Verify that the following files were created:

*.DAT Files: 3 (Float, String, Tagname)
*.DLG File: 1
*.DNS Files: 1
If you use the File Set storage format, tag

values are stored in proprietary-format files.
You cannot view the contents of these file sets
except with trends.
DLMe9701SE
Exercise B In this exercise, you will practice creating and viewing an ODBC
data log model.
Context:
You need to create an ODBC data log model in order to view logged
data using an ODBC compliant data source.
Directions:
1. Open the ODBC Data Source Administrator by performing the

following actions:
If Using Windows XP . . . Then . . .

Click Start>Settings>Control Panel>
Classic Mode Administrative Tools>Data Source
(ODBC)
Click Start>Settings>Control Panel>
Performance and Maintenance>
XP Mode (Category View)
Administrative Tools> Data Source
(ODBC)
2. Click the System DSN tab.

3. Click Add and then select Microsoft Access Driver (*.mdb).
4. Click Finish.
5. In the Data Source Name field of the ODBC Microsoft Access
Setup dialog box, type My Data Source.
6. Click Create.
7. Browse to C:\SE Class Files\ and type My Data Source.mdb
as the database name.
8. Click OK.
A window appears verifying that your database was successfully
created.
9. Click OK until all of the ODBC Data Source Administrator
windows have closed.
exercise.
Programming exercises, open the DLM_9701SE_B1.APA file.
DLMe9701SE
11. Duplicate the Trending Data data log model and name it My
Data Log.
12. Modify the data log settings by opening the My Data Log data
log and performing the following:
x Change the Description to ODBC Data Log.
x Change the Storage Format to ODBC database.
x In the ODBC Data Source field, type My Data Source.
13. Click Create Tables.
A window appears verifying ODBC tables were created
successfully.
14. Click OK.
15. Using Microsoft Explorer, browse to C:\SE Class Files and then
open the My Data Source.mdb Microsoft Access file.
16. Verify that the following tables have been created:
x FloatTable
x StringTable
x TagTable
17. Open a table and view the rows and columns that were
automatically generated.
18. Return to FactoryTalk View SE software and test the data log
model by performing the following:
A. Issue the DataLogOn command for the data log model My
Data Log.
Tip " Use the Command Wizard to automatically build the command.
B. Return to the My Data Source.mdb file and open the

StringTable.
C. Verify that data is being logged.
D. In FactoryTalk View SE software, issue the DataLogOff
command for the data log model My Data Log.
19. Close the Microsoft Access file.
DLMe9701SE
DLMe9701SE
Answers Exercise A
2. Your Data Log Model Setup tab should look similar to the
following:
Your Data Log Model Log Triggers tab should look similar to
the following:
4.
B. If you correctly configured the DataLogOn and DataLogOff
commands, your Diagnostic List should look similar to the
following:
DLMe9701SE
C. You should see the following files in your Trending Data

folder:
DLMe9701SE
Answers Exercise B
3. Select the Microsoft Access Drivers (*.mdb) as shown below:
5. Type the Data Source Name:
Data Source
Name (DSN)
DLMe9701SE
7. Type the Database Name:
Database Name
11. Duplicate the Trending Data data log model and save as My
Data Log:
DLMe9701SE
12. Your data log should appear similar to the following:
Data Log
Description
ODBC database
DSN
Default Tables
Created
16. Three tables have been created:
Tables
18.
C. Data has been logged:
DLMe9701SE
Lesson 14
Creating and Configuring a Trend
in a FactoryTalk View SE
Application
x Create a trend
x Configure a trend
x Overlay data snapshots on a trend by performing the following:
-- Create a snapshot
-- Create an overlay

x Trends provide a way for users to track plant activity and history.
x Comparing trends allows users to analyze production, present and
past.
Trend: 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.
Overlay: A layered trend with a snapshot of previously charted data.
The values can be tags you are Pens: The lines or symbols used to represent values on a trend chart.
monitoring, expressions that manipulate
tag values, or constant values. X-axis: The bottom edge of the chart. It is also known as the
horizontal axis, or the time axis.
Y-axis: The left edge of the chart. It is also known as the vertical
axis.
TNDsb9701SE
14--2 Creating and Configuring a Trend in a FactoryTalk View SE Application
Creating a Trend
Trends are created from the Advanced Object menu:
Advanced
Object
Create a Trend
As with other objects, draw a trend object box on a display to the

size of the trend you want to create.
Configuring a Trend
In the Trend Properties dialog box, you can set up the trend’s data,
appearance, and behavior:
x General Tab: Set up the trend’s data server (real-time or
historical polling), chart title, chart style, and update mode.
x Display Tab: Set up the appearance of the trend display.
x Pens Tab: Set up pen tags and expressions, and the appearance of
pens in the trend.
x X-Axis Tab: Set up the trend’s horizontal axis.
x Y-Axis Tab: Set up the trend’s vertical axis.
x Overlays Tab: Add or remove snapshots of historical data.
x Template Tab: Set up properties for trend templates.
x Runtime Tab: Set up ways to interact with the trend at run time.
x Common Tab: Set up the trend’s size and position in the graphic
display.
TNDsb9701SE
Creating and Configuring a Trend in a FactoryTalk View SE Application 14--3
The General tab of the Trend Properties is shown below as an

example:
Chart Title Data

Server
Chart Style
Update
Mode
Overlaying Data Snapshots on a Trend
Explain to students that in order to Use overlays to compare current charted data to a historical snapshot.
create an overlay, they need to create For example, you might set up overlays to compare data for a
the data snapshot first, and then add the
snapshot as an overlay to the trend particular shift or batch process.
charting the current data.
Creating a Snapshot
Create a snapshot when you want to capture or record real-time data:
Create Snapshot
TNDsb9701SE
Creating an Overlay
An operator can show or hide overlays When you add a snapshot to a trend as an overlay, the pens from the
on the trend chart at runtime, using the snapshot are added automatically to the Pens tab in the Trend
trend’s shortcut menu.
Properties dialog box. You can change the attributes of pens used in
overlays, just as you can change the attributes of regular pens.
Use the Overlays tab of the Trend Properties dialog box to configure
overlay attributes:
Overlay
Attributes
Add a Snapshot
The following is an illustration of a trend overlay:
Overlay time
Overlay pen
Currently
plotting pen
Currently
plotting pen
Overlay pen
TNDsb9701SE
Creating and Configuring a Trend in a FactoryTalk View SE Application 14--5

Open the CCV207_9701SE_DEM1.APA x Create a trend
following tasks: x Configure a trend
1. Open the Trend display. x Overlay data snapshots on a trend by performing the following:
2. Add a trend to the display. -- Create a snapshot
3. Show students the different -- Create an overlay
configuration options for the trend.
4. Add pens to the trend. the associated job aid(s).
5. Test your display and view the data.
6. Create a snapshot.
7. Create an overlay using the
snapshot you just created.
TNDsb9701SE
TNDsb9701SE
Exercise: Creating and Configuring a Trend in a FactoryTalk View SE Application 14--7
Exercise: Creating and Configuring

a Trend in a FactoryTalk View SE
Application
Exercise A In this exercise, you will practice creating, configuring, and

overlaying trend objects.
Context:
You are responsible for creating and configuring trends to

graphically display the real-time and historical data of the three tank
levels in your application.

Directions:

exercise.
Programming exercises, open the TND_9701SE_A1.APA file.
2. Add a new graphic display to your application.

3. Create a trend and add it to the graphic display.
4. Save your display as Trend.
5. Configure the trend to include the following pens from the
trending data model:
6. Configure all three pens to have the following attributes:

x Width: 3
x Max fields: 2000
TNDe9701SE
14--8 Exercise: Creating and Configuring a Trend in a FactoryTalk View SE Application
7. Test the FactoryTalk View SE graphic display and verify that data
is trending.
8. Stop the graphic display test.
9. Create and configure a maintained pushbutton on the Trend
display to control the pump from Tank 1.
x State 0 Caption: Tank 1 Pump OFF
x State 1 Caption: Tank 1 Pump ON
x Use the same tag for the value and indicator connection:
10. Repeat Step 9. for the pumps from Tank 2 and Tank 3.
11. Create a button to clear the chart using the invoke command and
the following command wizard fields:
x Display: Trend
x Object: Trend1
x Property or Method: ClearChart
x Method parameters: “ “ (Empty)
Tip " Make sure the name of the object is correct in your command. The
trend object will be Trend1 if it is the first trend created for this
application. To see the name of the object, right-click the object and
select Property Panel.
12. Test the FactoryTalk View SE graphic display.

13. Overlay data snapshots on a trend by performing the following:
x Right-click on the trend after it has been running for a few
moments and select Create Snapshot.
x Enter the component name as Levels.
x Right-click on the chart again and select Chart Properties.
x Add the Levels snapshot to the Overlays tab.
14. Stop the graphic display test.
TNDe9701SE
TNDe9701SE
Answers Exercise A
6. You should set the width of the pens to 3:
You should set the Max value of the pens to 2000:
11. The Press Action for the button should be configured similar to
the following:
TNDe9701SE
The Press Action for the button should have the following
syntax:
13. Your Overlays tab should look similar to the following:
TNDe9701SE
TNDe9701SE
Lesson 15
Creating a Derived Tag File and an
Event File in a FactoryTalk View SE
Application
x Create a derived tag file
x Create an event file

Example: Suppose you have 5 weights x Correctly creating a derived tag file allows you to obtain tag
on a conveyor belt. A derived tag could values as a result of an expression. With a properly configured
trigger an alarm to sound if any one of
the weights is too heavy OR if the sum derived tag file, alarms can be triggered when the sum of certain
of all the weights is too heavy. values reaches too high of a level.
x Events are useful when action needs to be taken based on an
expression.
x If an event file is not properly stopped and re-started after
modifications have been made, then the changes will not take
effect and you will not be able to view the results of those
modifications.
Actions could initiate a snapshot of tag Actions: FactoryTalk view commands, symbols, or macros.
values using the DataLogSnapshot
command, or change a tag value using Derived Tag: An analog, digital, or string tag whose value is
the Set command.
determined through the evaluation of an expression.
Derived Tag (Component) File: Contains the definitions of one or

more derived tags.
Event: Expressions that trigger actions.
Event (Component) File: Consists of a number of events and a

maximum update rate for them.
Expressions: Equations containing tag values, mathematical

operations, if-then-else logic, and other built-in FactoryTalk View
functions.
Maximum Update Rate: The fastest rate at which the value of any
derived tag in a derived tag component can be updated.
EVTsb9701SE
15--2 Creating a Derived Tag File and an Event File in a FactoryTalk View SE Application
Creating a Derived Tag File
Explain to students that you could create You can create multiple derived tag components.
multiple derived tag components to
group derived tags that have different Each HMI server in a network application can run up to 20 derived
evaluation rates.
tag components, with up to 1,000 tags in each component.
You can modify derived tags during development or when you run
the application.
If you change a derived tags component at run time, the changes will
not take effect until you stop and then restart derived tags processing.
Creating a Derived Tag

When setting up derived tags for an application, you must perform
the following tasks:
x Create the derived tags in the Derived Tags editor in FactoryTalk
View Studio.
x Set the maximum update rate in the Derived Tag Setup dialog
box.
x Save the derived tags component and give it a name.
The Derived Tags editor is comprised of the following parts:
x Form Area: Used to provide a name and description for the
derived tag.
x Spreadsheet Area: Displays a list of tags.
Tip " Once information is entered in the Derived tags editor, the Prev and
Next buttons change to Accept and Discard.
EVTsb9701SE
Creating a Derived Tag File and an Event File in a FactoryTalk View SE Application 15--3
Accepted derived tags appear below in the spreadsheet:
Derived
Tags Editor
Tag Name
Description
Form Expression
Spreadsheet Accepted
derived tags
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.
Derived tag calculations are carried out at the FactoryTalk View SE

Server (also called the HMI server).
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.
Starting and Stopping a Derived Tag File

A derived tags component file can be run when an HMI server starts,
or it can be run using the DerivedOn command, after the HMI server
has started.
EVTsb9701SE
Commands that run only at the FactoryTalk View SE Client are

ignored when issued by an event expression.
Using clients to start and stop derived tags

processing is not recommended, as one client
might stop processing a derived tag component
that another client is using.
Creating an Event File
Explain to students that you could create You can create multiple events components.
multiple events components to group
events that have different evaluation Each HMI server in a network application can run up to 20 event
rates.
files, each containing up to 1,000 events.
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.
Creating an Event
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:

x Create the events in the Events editor.
x Set the maximum update rate for the events component in the
Events Setup dialog box.
x Save the events component and give it a name. The file extension
.eds is added by the system.
The Events editor is comprised of the following components:
x Form Area: Used to provide a name and description for the
event component.
x Spreadsheet Area: Displays a list of tags.
Tip " Once information is entered in the Events editor, the Prev and Next
buttons change to Accept and Discard.
EVTsb9701SE
Creating a Derived Tag File and an Event File in a FactoryTalk View SE Application 15--5
Accepted event actions appear below in the spreadsheet:
Event Editor
Action
Description
Form Expression
Accepted
Spreadsheet
event actions
Events are detected at the FactoryTalk View SE Server (also called

the HMI server).
Do not create events that depend on other events.

Events are not processed sequentially.
Starting and Stopping Event Processing

An events component file can be run when an HMI server starts, or it
can be run using the EventOn command, after the HMI server has
started.
Commands that run only at the FactoryTalk View SE Client are

ignored when issued by an event expression.
Using clients to start and stop event processing is

not recommended, as one client might stop
processing an event component that another client
is using.
EVTsb9701SE
Here’s How To perform the following:

Open the CCV207_9701SE_DEM1.APA x Create a derived tag file
following tasks: x Create an event file
1. Create a new derived tag file and As your instructor demonstrates these procedures, follow along in
add a couple of derived tags.
the associated job aids(s).
2. Create an expression for at least
one of the derived tags.
3. Open a new display.
4. Create a numeric display object or
another appropriate object to confirm
your derived tag expression value.
5. Use the command line to start and
stop derived tag processing.
6. Verify that good data is being read in
and that it is true to your expression.
7. Create a new event file and add a
couple of events.
8. Create an expression for at least
one event.
9. Open your display.
10. Add startup and shutdown
commands to your event file.
11. Save and test the display.
12. View the Diagnostics List to verify
that the commands are executing.
EVTsb9701SE
Exercise: Creating a Derived Tag File and an Event File in a FactoryTalk View SE Application 15--7
Exercise: Creating a Derived Tag

File and an Event File in a
Exercise A In this exercise, you will practice creating a derived tag file and an
event file.
Context:
You must be able to populate the Diagnostic List with custom event
information. You must be also able to configure the HMI to do basic
arithmetic to display the total level of all three tanks in your
application by configuring derived and event files.

Directions:

exercise.
Programming exercises, open the EVT_9701SE_A1.APA file.
2. Create a new derived tag file.

3. From within the derived tag file, launch the tag browser.
4. Select the mem folder.
5. Right-click on the right window pane and then click New HMI
Tag.
6. Configure the HMI tag as follows:
x Name: TotalTankLevel
x Type: Analog
x Maximum: 3000
x Data Source Type: Memory
7. Add the tag TotalTankLevel to the derived tag file and create an
expression that will sum the individual tank levels for the new
derived tag (Tank_1_Level + Tank_2_Level + Tank_3_Level).
8. Accept your edits and select another derived tag entry within the
file.
EVTe9701SE
15--8 Exercise: Creating a Derived Tag File and an Event File in a FactoryTalk View SE Application
9. Launch the Tag Browser and and create a new HMI tag in the
mem folder named PumpsString with the following properties:
x Type: String
x Data Source Type: Memory
10. Add the tag PumpsString to the derived tag file and create the
following expression:
11. Accept your edits to the tag.

12. Save the derived tag file as Tanks.
13. Open the Trend graphic display.
14. Add the pen mem\TotalTankLevel to the trend.
Tip " If you need to create space, remove the overlay Levels.
15. Create a text object to show Tank Total in the Trend graphic
display.
16. Create numeric display object mem\TotalTankLevel close to the
text object.
17. Create a string display to show the value of the
mem\PumpsString tag in the Trand graphic display.
18. Test the display by performing the following:
A. Open the Command Line and enter DerivedOn Tanks.
EVTe9701SE
B. Press the Test Display button for the Trend display.

C. Confirm that the two derived tags are working correctly.
D. Stop the display test.
E. Open the Command Line and enter DerivedOff Tanks.
19. Create a new event file.
20. Create a new event with the following properties:
x Action: Remark Total Tank Level over 1000
x Description: Automatically create an entry in the
Diagnostic Log
x Expression: mem\TotalTankLevel > 1000
21. Create a new event with the following properties:
x Action: Toggle
::[LinxE_Shortcut]Program:Tanks.Tank_1_Pump
x Description: Automatically toggle pump 1 on and off
x Expression: interval (“5 sec”)
22. Save the event file as TankEvents.
23. Test the event files by performing the following:
A. Open the Trend display Behavior tab.
B. Add commands to start the Tanks derived tag file and the
TankEvents event file to the Startup field.
C. Add commands to stop the Tanks derived tag file and the
TankEvents event file to the Shutdown field:
D. Save your changes to the Trend display.

E. Test the Trend display.
EVTe9701SE
F. Check the Diagnostics List on your computer to verify the

commands are executing:
G. Close the display.

EVTe9701SE
EVTe9701SE
Answers Exercise A
6. Your TotalTankLevel HMI tag should be configured similar to

the following:
7. The syntax for the expression associated with the

TotalTankLevel tag should look similar to the following:
EVTe9701SE
9. Your PumpsString HMI tag should be configured similar to the

following:
18. Your Trend display should now look similar to the following:
EVTe9701SE
20. Your event file should be configured similar to the following:
21. Your event file should be configured similar to the following:
EVTe9701SE
Lesson 16
Creating Symbols, Macros, and
Keys in a FactoryTalk View SE
Application
x Create symbols
x Create macros
x Create keys assignments
Having the skills to properly create a macro allows for a series of

commands to execute at runtime, rather than a single command.
Using symbols, macros, and key assignments provide shortcuts and
reduce development time for users.
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.
Keys: 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.
Macros: A series of commands stored in a macro component.
Symbols: A single word used to replace long commands or

commands with parameters that are hard to remember or easy to mix
up.
Creating Symbols
Symbols can be used anywhere a command can be used:

x In a box that requires an action
x In a macro
x At the command line.
SMKsb9701SE
16--2 Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application
To define a symbol, at the command line or in a macro or box, type:

Define <symbol> <string>
Where: <symbol> is the abbreviated command, without spaces
and <string> is an existing command with or without parameters.
It can contain spaces and other symbols.
Symbol Word Command String
Clearing a Symbol
To clear a symbol, at the command line or in a macros or box, type:
Undefine <symbol>
Where: <symbol> is the name of the symbol you want to delete.
To clear all defined symbols, at the command line or in a macros or

box, type:
Undefine *
Creating Macros
Tell students they can use macros to You can use a macro component like a command, anywhere a
close and open graphic displays, set tag command can be used. When the component name is issued, the
values, and define temporary key
definitions. macro runs, carrying out all the commands in the component.
Macro Syntax
When typing commands in macros, follow these guidelines:
x Separate each identifier, specification, or string with a space or a
tab.
x Start each command on a new line, or separate commands on the
same line with a semicolon (;).
x To insert a comment, type an exclamation mark (!) at the
beginning of a new line or immediately after a semicolon (;).
Tip " Everything between the exclamation mark and the end of the line, or
the next semicolon, is treated as a comment.
SMKsb9701SE
Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application 16--3
x 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.
x To indicate percent in a macro, use two percent signs (%%). A
single percent sign indicates a parameter.
Do not use dollar signs ($) or percent signs (%) in

comments inserted in macros. This causes errors
at run time.
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.
Tell students that in order to make a If you have created an HMI server with components that must start
macro run when the HMI server starts, in a particular order, create a Startup macro.
select it as the startup macro in the
Components tab of the HMI Server
Properties dialog box.
Creating Key Assignments
Keys allow you to define a FactoryTalk View command to a

keyboard key sequence. For example, you could create a key
association so an operator could press F3 and be presented with the
main graphic display.
To set up key animation you redefine the operation of a particular

key, or key combination, by assigning a command or macro to a key
action (press, hold, or release). At run time, when the key action
occurs the command or macro is carried out.
You can set up keys for the following:

x Objects
x Displays
x HMI project (client keys)
You can use these alone or in The types of keys that can be redefined are:
combination with Control and/or Shift.
x The alphabetic keys
x Function keys
x Keys on the numeric keypad
x Mouse buttons
SMKsb9701SE
Object Keys
You may assign a key to be active only when a particular graphical
object has focus. This type of key will not be in effect otherwise.
Add a key and associate a command with the key:
Display Keys
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.
SMKsb9701SE
Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application 16--5
For example, you could connect a display to the F5 key. At run time,
when the display is open, the operator can press F5 to perform the
key’s press, repeat, or release action:
Assigned Keys
Release Action
Client Keys
Tell students that is it a best practice to Client keys allow the operator to interact with the system at run time
have a client key that will open the main to do things like change displays or set tag values. Client keys are
display. This way, if display navigation is
not completely set up and the defined for an application using the Client Keys editor. They are
FactoryTalk View SE Client is empty, you enabled whenever the application is running on an SE Client, unlike
can use the client key to open the main object and display keys which are active only when their associated
display instead of restarting the SE
Client. object or display is.
Precedence
The order of precedence for key animation is:
x Non-native embedded OLE object
x Object Keys
x Display Keys
x Client Keys
This means that if a key has both object and client key definitions,
when the object has focus at run time and the key is pressed, the
object key action will be carried out and the client key action will
not.
SMKsb9701SE
Client Key files are saved in the Logic and Control section of the
HMI project:
Logic and Control
Client Key

Open the CCV207_9701SE_DEM1.APA x Create symbols
following tasks: x Create macros
1. Open the command line and create x Create keys assignments
a symbol.
2. Create a new display that uses your
symbol command. the associated job aid(s).
3. Add a key assignment to the
display.
4. Create a macro that opens your
new display on startup.
5. Save and test your display and verify
the following:
A. Your new display opened on
startup.
B. Verify your symbol.
C. Verify your key assignment.
SMKsb9701SE
Exercise: Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application 16--7
Exercise: Creating Symbols,

Macros, and Keys in a FactoryTalk
View SE Application
Exercise A In this exercise, you will practice creating symbols, macros and keys
assignments.
Context:
You must configure symbols, macros and key assignments before

your display will function properly. You are required to comply with
the following specs:
x Configure the keyboard hot keys to modify the number of bottles
to fill for the Conveyor line
x Configure hot keys to shutdown the SE Client, launch a Help file,
and launch an executable file.
Directions:

exercise.
Programming exercises, open the SMK_9701SE_A1.APA file.

application.
3. Create a numeric display that connects to the mem\analog tag.
4. Create a mem\analog text object.
5. Create a symbol for the command UP by performing the
following:
A. Open the Command Line.
B. Enter Define UP ramp mem\analog +5.
6. Create a symbol for the command DOWN by performing the
following:
A. Open the Command Line.
B. Enter Define DOWN ramp mem\analog -5.
SMKe9701SE
16--8 Exercise: Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application
7. Test the FactoryTalk View SE graphic display by performing the

following:
x Click the Test Display button.
x Open the Command Line.
x Enter UP.
x Verify that after a moment the value of the mem\analog tag
updates.
x Enter DOWN.
x Verify that after a moment the value of the mem\analog tag
updates.
x Close the display when you are done. You do not need to save
the display.
8. Create a macro named StartupServer that will execute the
following commands:
x Alarmon
x DataLogOn “Trending Data”
x ::[LinxE_Shortcut]Program:Filling.Bottle_Preset = 0
Tip " You can use the Command Wizard to help you build the commands
by selecting it from the Edit menu.
9. Create a macro named ShutdownServer that will execute the

following commands:
x DataLogOff *
x AlarmOff
10. Create a macro named StartClient that will start the Conveyor
display when the client starts:
11. Create a macro named ShutdownClient that will make a beep

sound when the client is stopped:
SMKe9701SE
12. Open the Conveyor graphic display.

13. Create an object key for the Filler object with the following
properties:
x Key: Ctrl + C
x Label: Calculator
x Release action: AppStart calc.exe
14. Create a display key with the following properties:
x Key: F3
x Label: Five Bottles
x Release action:
::[LinxE_Shortcut]Program:Filling.Bottle_Preset = 5
15. Create a display key with the following properties:
x Key: F4
x Label: Eight Bottles
x Release action:
::[LinxE_Shortcut]Program:Filling.Bottle_Preset = 8
16. Save the Conveyor display.
17. Create a new client key file and configure the following
parameters:
x Key: Ctrl + Z
x Label: Quit
x Press Action: DisplayClientClose
18. Configure the following key in the client key file:
x Key: Ctrl + H
x Label: Help
x Press Action: Help /f”C:\Program Files\Common
Files\Rockwell\Help\SLDisplayClient.chm”
19. Save the client key file as Project Keys.
20. Configure your applications HMI server properties as follows:
x Startup Macro: StartupServer
x On shutdown macro: ShutdownServer
21. Within your HMI server properties, click Run Startup
Components.
22. Verify you see your startup macro execute in the Diagnostics List.
23. Within your HMI server properties, click Stop All Running
Components.
24. Verify you see your shutdown macro execute in the Diagnostics
List.
25. Click Launch SE Client from the Tools menu.
SMKe9701SE
26. Configure a new FactoryTalk View SE client with the following

properties:
x Name of configuration: Macro Key Test
x Type of application: Local
x Application to connect to: AppliSE.APA (or
SMK_9701SE_A1.APA)
x Initial client key file: Project Keys
x Startup macro: Start Client
x Shutdown macro: ShutDownClient
27. Test the running client by performing the following:
A. Open the Macro Key Test SE Client configuration.
B. Look at the Diagnostics List on the SE Client and confirm
that the Startup Macro has executed.
C. Click the Filling machine and confirm the Key List is shown
with all the Object and Display keys listed.
D. Use the F3 and F4 keys on the keyboard to change the bottle
preset number.
E. Use the Ctrl-C key when the Filler machine has focus to start
the calculator.
F. Use the Ctrl-H key (client key) to bring up the Help system.
G. Use the Ctrl-Z key to close the client.
H. Look at the Diagnostics List in FactoryTalk View Studio and
confirm the shutdown macro executed.
SMKe9701SE
SMKe9701SE
Answers Exercise A
4. Your new graphic display should now look similar to the

following:
8. Your StartupServer macro should be configured similar to the

following:
9. Your ShutdownServer macro should be configured similar to

the following:
SMKe9701SE
13. Your Object Key should be configured similar to the following:
15. You should now have two Display Keys configured similar to
the following:
SMKe9701SE
18. Your client key file should look similar to the following:
20. Your HMI server properties should look similar to the

following:
SMKe9701SE
Lesson 17
Configuring Security in a
x Create a user account
x Create a user group account
x Specify user security codes
x Assigning security codes to graphic displays
These skills are important to prevent unauthorized users from

accessing an application. Security can also be configured so that
operators can only view screens relevant to their job function.
Before You Begin Creating a User Account
FactoryTalk User Account

During FactoryTalk Services Platform installation, an account named
All Users is created automatically, at the Local Directory and the
Network Directory.
The All Users account is visible in the When you create a local or a network application, an All Users
Runtime Security editor, but not in the account is also added automatically to the Runtime Security list for
user Groups folder that contains other
FactoryTalk group accounts. the application. By default, the account is allowed all run-time
security codes:
Add, view, or modify security

codes for the selected account.
All Users Account
SCYsb9701SE
17--2 Configuring Security in a FactoryTalk View SE Application
All of this means that initially, after the FactoryTalk View SE

software is installed, any FactoryTalk system user you create will be
able to open, create, or modify an application in FactoryTalk View
Studio, or run an application in the FactoryTalk View SE Client.
To retain full access for all users, nothing further is required.
Security permissions is discussed in To restrict access to FactoryTalk system resources for selected users
more detail later. and computers, you need to remove the All Users account, create
accounts for the users and computers you want to secure, and then
give the accounts the appropriate security permissions.
Adding a New User Account

In FactoryTalk View Studio, you can create user accounts that:
x Originate at the FactoryTalk Directory
x Refer to Windows users. These are called Windows-linked user
accounts.
Add User to
a Group
User Name
Password
Configuration
Create
Password
Creating a User Group Account
FactoryTalk User Group Account

As part of directory configuration, these FactoryTalk user groups are
created:
x Windows Administrators is a group linked to Windows users
with administrative privileges on the computer.
x Administrators is a group for FactoryTalk users with
administrative privileges.
SCYsb9701SE
Configuring Security in a FactoryTalk View SE Application 17--3
The following illustration shows where to find these groups in

FactoryTalk View Studio:
The Windows Administrators group belongs

to the FactoryTalk Administrators group.
Both groups are created during FactoryTalk
Directory installation.
By default, the Windows Administrators group belongs to the

FactoryTalk system Administrators group.
Tell students they cannot convert an This means that Windows users with administrative privileges on the
original FactoryTalk account to a local computer have full access to local and network applications,
Windows-linked account, nor can you
add a FactoryTalk account to a including the ability to set up security for the FactoryTalk system.
Windows-linked user group.
Whichever type of FactoryTalk Security account you decide to use,
when setting up security for a FactoryTalk View SE application, it is
recommended that you create group accounts and set up access
permissions for them first.
Using group accounts makes it easier to assign and manage

permissions for multiple users with the same security needs. Rather
than assigning permissions to each user separately, you can create
accounts for new users, and then add these users to the appropriate
groups.
Tell students they are able to add Later, if you want to change an individual user’s permissions, you
Windows-linked groups to FactoryTalk can move the user’s account to a different group. You can also
groups.
change permissions for several individual users at once, by
modifying the group that the users belong to.
SCYsb9701SE
Creating a New Group

In FactoryTalk View Studio, you can create user group accounts that:
x Originate at the FactoryTalk Directory
x Refer to Windows groups. These are called Windows-linked user
accounts.
Group Name
Add Members
to the Group
SCYsb9701SE
Configuring Security in a FactoryTalk View SE Application 17--5
Specifying User Security Codes
Use the Security Settings dialog box to add the users or groups of
users that are to have access to the resource, and then allow or deny
permission to perform the actions that define levels of access:
Set up security codes

by user or action.
List of user groups with

level of access to securable
HMI project components.
To add FactoryTalk users

or groups, click Add.
To assign security codes to

the selected user or group,
select the Allow check
boxes.
Explain to students that this means you When setting up permissions for a network application, you can
can determine not only who has access associate users and groups of users with specific computers or
to system resources, but from which
computers. groups of computers.
Assigning Security Codes to Graphic Displays
In the Graphics editor, you can set up security for graphic displays.
You can assign a security code while you are creating a graphic
display, or you can assign it later.
Only users or groups assigned the graphic display’s security code

will be able to open the display at run time. Users must have at least
one security code assigned to them, to open graphic displays
assigned an asterisk (*).
SCYsb9701SE
Security codes can be located in the display settings of a graphic

display:
Security Codes

Open the CCV207_9701SE_DEM1.APA x Create a user account
following tasks: x Create a user group account
1. Create a new user group. x Specify user security codes
2. Add a new user to your group. x Assigning security codes to graphic displays
3. Open the Runtime Security and As your instructor demonstrates these procedures, follow along in
deny your group to have access to
Security Code A. the associated job aid(s).
4. Open the Security display.
5. Configure the display to have a
security level of A.
6. Configure a macro to login the user
you created OR create a test client
to have the initial display Login.
7. Test your display security.
SCYsb9701SE
Exercise: Configuring Security in a FactoryTalk View SE Application 17--7
Exercise: Configuring Security in a

Exercise A In this exercise, you will practice performing the following:

x Create a FactoryTalk user and user group account
x Specify user security codes
x Assign security codes to a graphic display
Context:
You must configure security for your FactoryTalk View SE

application so that specific users only have access to screens relevant
to their job function. You will need to create the user accounts and
groups, as well as configure security for the application.

Directions:

exercise.
Programming exercises, open the SCY_9701SE_A1.APA file.
2. Create the following new user group accounts:

x Admin
x Operators
x Maintenance
3. Create the following new user accounts and configure the
passwords to never expire:
User Name Password Group

Student student Admin
Tim tim Operators
John john Operators
Bill bill Maintenance
Susan susan Maintenance
4. Open the Runtime Security editor from the Settings menu.
SCYe9701SE
17--8 Exercise: Configuring Security in a FactoryTalk View SE Application
5. Specify the user security codes as follows:
User Group or User Security Codes Allowed

Admin Allow All
Operators A, F, and H
Maintenance A, B, C, D, and F
Tim B
6. Save and close the Runtime Security editor.

application.
8. Add the following elements to the display:
x Text objects: Login Screen, Currently Logged In:
x String Display: Expression CurrentUserName()
x Button: Login command
x Button: Logout command
x Button: Display TankData /Ttank_1 command
x Security Code: P
x Display List Selector object: Assign Conveyor, TankData,
Trend, and Alarms display to the object.
x Move Up, Move Down, and Enter buttons
9. Save your display as Main.
SCYe9701SE
10. Create a button on the Trend graphic display, that displays the
Main display when pressed.
11. Assign a security code to the TankData graphic display so that
Operators may not access it, but all others, including Tim can.
12. Assign security code A to the Conveyor graphic display.
13. Open the Runtime Secured Commands editor form the Settings
menu.
14. Configure the ALLUSERS runtime security account to only
allow security code P.
15. Specify a user security code that prevents Maintenance from
accessing the AppStart and Invoke commands.
16. Select Launch SE Client from the Tools menu.
17. Configure a FactoryTalk View SE Client with the following
properties:
x Name: Final Client
x Type of application: Local
x Application to connect to: AppliSE.APA (or
SCY_9701SE_A1.APA)
x Initial Display: Main
18. Launch the Final Client client configuration.
19. Test your security configurations by performing the following:
A. Login as John.
B. Test your access to the TankData display.
C. Logout and login as Tim.
D. Test your access to the TankData display.
E. Return to the Main display.
F. Login as Susan.
G. Open the Conveyor display.
H. What happens when you attempt to open the calculator by
pressing Ctrl-C while the Filler object is in focus?
I. Open the Trend display.

J. Test your permissions to use the Clear Trend Chart button.
K. Return to the Main display.
L. Click the Logout button.
SCYe9701SE
M. What happens when you attempt to logout?
N. Close the client when you are done troubleshooting.
Tip " Login to close the client.
SCYe9701SE
SCYe9701SE
Answers Exercise A
3. For example, your Student user account should appear similar

to the following:
5. Your Runtime Security settings should look similar to the

following:
SCYe9701SE
8. The Display List Selector should be configured similar to the

following:
Display
Caption
11. Your TankData display settings should be configured similar to

the following:
Security Code B
SCYe9701SE
14. The ALLUSERS runtime security account should appear like

the following:
15. Your runtime security should appear similar to the following:
Security Code
E or H
SCYe9701SE
19. The security settings should produce the following results:

B. John should not have access to the TankData display.
D. Tim should have access to the TankData display.
G. Susan will have access to the Conveyor display.
H. Susan is denied access and the diagnostic list displays the
following:
Improper security access for command ‘AppStart calc.exe’.
M. When you attempt to Logout you are automatically prompted
to login as another user.
J. Susan does not have access to the Clear Trend Chart button
because she does not have access to the invoke command.
SCYe9701SE
SCYe9701SE
Lesson 18
Adding VBA Display Code in a
What You Will Learn After completing this lesson, you should be able to add VBA code.

x You can use VBA logic to perform many actions such as:
-- Validate an operator’s input
-- Dynamically adjust graphic displays based on the size of the
FactoryTalk View SE Client window
-- Integrate data from additional programs such as Microsoft
Excel or Microsoft SQL
Procedures: A named block of code that runs as a unit.
VBA IDE: Visual Basic for Applications (VBA) Integrated

Development Environment (IDE) enhances the development
capabilities of the FactoryTalk View SE Client.
Adding VBA Code
Use the FactoryTalk View SE Client object model with Microsoft

Visual Basic for Applications (VBA) code in graphic displays to
customize and extend the capabilities of the FactoryTalk View SE
Client.
For example, you can use the object model and display code to do
the following:
x Use data with other applications
x Create custom forms for operators
x Design intuitive graphic displays
x Manipulate the FactoryTalk View SE Client window
x Send custom messages to the Diagnostics log
x Secure the system
VBAsb9701SE
18--2 Adding VBA Display Code in a FactoryTalk View SE Application
There are two basic tasks involved in working with the FactoryTalk
View SE Client object model and VBA:
Display code is saved with a graphic x Create the graphic display and the graphic objects that require
display. Before you can write VBA code VBA code written to them.
that manipulates graphic objects, you
must create the graphic display and the x In the VBA Integrated Development Environment (VBA IDE),
graphic objects in FactoryTalk View using the Visual Basic programming language, write procedures
Studio.
in the code window for the module called ThisDisplay.
The integrated development environment for VBA IDE is available
from the FactoryTalk View Graphics editor.
Use the VBA IDE to create, test, and debug VBA procedures. VBA
procedures can be designed to run in response to events that occur in
FactoryTalk View graphic displays at run time.
The VBA IDE has the following components:
Project Explorer
Window
Properties
Window
Procedure or
Code Window
VBAsb9701SE
Adding VBA Display Code in a FactoryTalk View SE Application 18--3
Here’s How To add VBA code.

Open the CCV207_9701SE_DEM1.APA As your instructor demonstrates these procedures, follow along in
following tasks: the associated job aid(s).
1. Open the VBA display.
2. Expose the Numeric Input object to
VBA through the Property Panel.
3. Open the VBA IDE editor from the
VBA display.
4. Change the drop-down menus,
select Display and
BeforeInputFieldDownloaded
5. Add VBA code of your own or enter
the following code:
IF NumericInput1.Value < 0 Or
NumericInput1.Value > 1000 Then
MsgBox “The value must be
between 0 and 1000”
Cancel = True
End If
6. Save and test the VBA display by
entering values and confirming you
are unable to enter a value that is
not between 0 and 1000.
VBAsb9701SE
18--4 Adding VBA Display Code in a FactoryTalk View SE Application
VBAsb9701SE
Exercise: Creating VBA Display Code in a FactoryTalk View SE Application 18--5
Exercise: Creating VBA Display

Code in a FactoryTalk View SE
Application
Exercise A In this exercise, you will practice creating VBA code.
Context:
You must limit the valid entries for a Numeric Input object and
disable certain buttons based on which user is logged in to your
application using VBA code.

Directions:

exercise.
Programming exercises, open the VBA_9701SE_A1.APA file.

application and create the following objects:
x Text object: Mixer RPM Setpoint
x Numeric Input object: Connected to
::[LinxE_Shortcut]Program:Mixing.Mixer_rpm_setpoint
x Numeric Display object: Connected to
::[LinxE_Shortcut]Program:Mixing.Mixer_rpm_setpoint
3. Save the display as VBA.
4. Expose the Numeric Input object to VBA through the Property
Panel.
5. From the open space in the VBA display, access the main window
of the Microsoft VBA editor.
6. From the editor, confirm Display is selected from the left
drop-down menu, and then select BeforeInputFieldDownload
from the right.
VBAe9701SE
18--6 Exercise: Creating VBA Display Code in a FactoryTalk View SE Application
7. Add the following code within the VBA editor:
8. Save your changes

9. Test the graphic display by performing the following:
A. Click the Test Display button.
B. Enter values in the numeric input.
C. Confirm you are unable to enter a value beyond
0 through 1740.
10. Open the ActiveX Toolbox from the View menu.
11. Add a ComboBox control to the VBA display.
12. Close the ActiveX Toolbox.
13. Create four buttons on the VBA display.
14. Select the ComboBox and the four buttons and then open the
Property Panel.
15. Enable all objects to be exposed to VBA control.
16. Return to the main window of the Microsoft VBA editor.
VBAe9701SE
17. Enter the following code when display animation starts:
18. Right-click on the ComboBox and select VBA Code.

19. Add more code to enable one of the four buttons only when it has
been selected from the ComboBox:
Tip " CBool is a VBA function that returns a 0 or 1 based on the

expression in the parentheses. For more help in VBA, select the item
you want help with and use the F1 key on the keyboard.
20. Save the VBA code and the VBA display.
VBAe9701SE
21. Test the display and confirm the ComboBox enables the
appropriate buttons.
22. Open the Main display.
23. Create a button and apply a caption as shown:
24. Open the Property Panel for the OPERATOR may NOT press
this button and configure the following:
x Name: btnNoOp
x ExposeToVBA: VBA Control
25. Add VBA code to create a variable, oDCApp, to represent the
Display Client Application:
A. Press F7 to open the VBA editor.
B. Select General from the objects drop-down list.
C. Enter the following code:
VBAe9701SE
26. Add VBA code to assign the oDCApp variable to your

application and to enable or disable the buttons based on which
user is logged in by entering the following code:
Tip " The code you entered above will only check the security codes when
the display first starts up.
27. Add VBA code that will check the security codes whenever
someone logs in by performing the following:
A. Select oDCApp from the Object drop-down list within the
VBA editor.
B. Select Login from the Event drop-down list.
C. Copy and paste the line of code from the earlier subroutine:
Tip " It is a good practice to destroy an object that has been created in
code.
VBAe9701SE
28. Destroy the oDCApp code by performing the following;

A. Select Display from the Object drop-down list within the
VBA editor.
B. Select AfterAnimationStop from the Event drop-down list.
C. Enter the following line of code within the subroutine:
29. Select Launch SE Client from the Tools menu.

30. Test the application using the Final Client configuration made in
the previous lab.
Tip " If you have not completed the previous labs, create a new client
configuration that displays Main as the initial graphic.
31. Log in as John and Tim and verify that the appropriate buttons
are available. John will not have access, Tim will have access.
Tip " John password is john. Tim password is tim.
32. Close the Client.

VBAe9701SE
VBAe9701SE
Answers Exercise A
4. Your Numeric Input should be configured to be exposed to

VBA code within the Property Panel:
21. Your VBA display should now look similar to the following:
24. The Panel Panel for the OPERATOR may NOT press this
button should look similar to the following:
VBAe9701SE
28. Your completed code should look similar to the following:
31. John will not have access to the OPERATOR may NOT press
this button or the Tank Data display.
Tim will have access to the OPERATOR may NOT press this
button and the Tank Data display.
VBAe9701SE
VBAe9701SE
The following are trademarks of Rockwell Automation, Inc.:
1336 FORCE 1336 IMPACT
1336 PLUS CompactLogix
ControlBus ControlLogix
Data Highway Plus DH+
DriveTools FactoryTalk
Flex FlexLogix
Logix5000 Logix5550
PanelBuilder PanelView
PLC-5 PHOTOSWITCH
PowerFlex RediSTATION
RSLinx RSLogix
RSView RSNetWorx
SCANPort SLC
SoftLogix Ultra
EtherNet/IP and ControlNet are trademarks of ControlNet International Ltd.
DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA).
The following are registered trademarks of Microsoft Corporation:

MS-DOS PowerPoint
Windows Windows NT
IBM is a registered trademark of International Business Machines Corporation.
Pentium is a registered trademark of Intel Corporation.
All other trademarks are the property of their respective holders and are hereby acknowledged.
Catalog Number ABT-CCV207-TSM -- May 2008 E 2008 Rockwell Automation, Inc. All rights reserved.
Supersedes Catalog Number ABT--CCV207--TSM -- October 2007 Printed in USA

Abt-Ccv207-Tsm 2008-05

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Abt-Ccv207-Tsm 2008-05

Încărcat de

Drepturi de autor:

Formate disponibile

FactoryTalkr View

Identifies information about practices or circumstances

Identifies information that is critical for successful

Identifies information about practices or circumstances

Labels may be located on or inside the drive to alert

Labels may be located on or inside the drive to alert

Comments (include lesson title, if applicable):

Course or Product Name (Important):

Introducing FactoryTalk View SE Software

Exercise: Introducing FactoryTalk View SE Software

Configuring FactoryTalk Services For FactoryTalk View Applications

Creating Applications and Adding Areas and Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--8

Exercise: Configuring FactoryTalk Services For FactoryTalk View Applications

Creating a FactoryTalk View SE Application and Configuring Communications

Exercise: Creating a FactoryTalk View SE Application and Configuring Communications

Configuring OPC Communications in a FactoryTalk View SE Application

Locating HMI Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--4

Exercise: Configuring OPC Communications in a FactoryTalk View SE Application

Creating an HMI Tag Database in a FactoryTalk View SE Application

Exercise: Creating an HMI Tag Database in a FactoryTalk View SE Application

Creating a Graphic Display in a FactoryTalk View SE Application

Adding Images to an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--8

Exercise: Creating a Graphic Display in a FactoryTalk View SE Application

Building an Interactive Graphic Display in a FactoryTalk View SE Application

Exercise: Building an Interactive Graphic Display in a FactoryTalk View SE Application

Animating a Graphic Display in a FactoryTalk View SE Application

Creating an Expression within an Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--4

Exercise: Animating a Graphic Display in a FactoryTalk View SE Application

Using Tag Placeholders and Creating a FactoryTalk View SE Client

Exercise: Using Tag Placeholders and Creating a FactoryTalk View SE Client

Configuring Global Objects in a FactoryTalk View SE Application

Exercise: Configuring Global Objects in a FactoryTalk View SE Application

Switching Languages in a FactoryTalk View SE Application

Exercise: Switching Languages in a FactoryTalk View SE Application

Configuring Alarms in a FactoryTalk View SE Application

Exercise: Configuring Alarms in a FactoryTalk View SE Application

Creating and Viewing a Data Log Model in a FactoryTalk View SE Application

Creating and Configuring a Trend in a FactoryTalk View SE Application

Overlaying Data Snapshots on a Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--3

Exercise: Creating and Configuring a Trend in a FactoryTalk View SE Application

Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application

Client Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--5

Exercise: Creating Symbols, Macros, and Keys in a FactoryTalk View SE Application

Configuring Security in a FactoryTalk View SE Application

Exercise: Configuring Security in a FactoryTalk View SE Application

Creating VBA Display Code in a FactoryTalk View SE Application

Exercise: Creating VBA Display Code in a FactoryTalk View SE Application

This course provides opportunities for you to work with local

You will also work with RSLinx Enterprise communications

Prerequisites To successfully complete this course, experience operating a

Agenda This course consists of the following lessons:

Why These Skills Are Important

These skills are important for HMI (Human Machine Interface)

Before You Begin FactoryTalk View SE (Site Edition) Software Capabilities

Software Deployment Options

ControlLogix PLC-5 Third-Party SLC 500

ControlLogix PLC-5 Third-Party SLC 500

FactoryTalk View SE System Limits

Example FactoryTalk View SE Application

InstaCorp production overview:

InstaCorp dispenser line, Filling:

InstaCorp dispenser line, Capping:

InstaCorp dispenser line, Labelling: