Prévia do material em texto

FactoryTalk View SE 
 
 
FFFaaaccctttooorrryyyTTTaaalllkkk VVViiieeewww SSSEEE::: 
HHHaaannndddsss---OOOnnn LLLaaabbb 
TTTrrraaaiiinnniiinnnggg LLLaaabbb MMMaaannnuuuaaalll 
 
 
3/10/2008 Page 5 of 160 
WELCOME TO FACTORYTALK VIEW SE HANDS-ON LAB_________________________________9 
ABOUT THIS HANDS-ON LAB __________________________________________________9 
LAB MATERIALS __________________________________________________________10 
DOCUMENT CONVENTIONS___________________________________________________12 
BEFORE YOU BEGIN _______________________________________________________13 
OVERVIEW 14 
ABOUT THIS LAB __________________________________________________________14 
FACTORYTALK VIEW SITE EDITION_____________________________________________14 
FACTORYTALK VIEW SE - NETWORK AND LOCAL__________________________________17 
FACTORYTALK VIEW SE – SERVERS ___________________________________________23 
SECTION 1: CREATING YOUR APPLICATION (EST. TIME 20 MIN) ___________________________24 
ABOUT THIS LAB __________________________________________________________24 
CREATING LOCAL HMI PROJECT IN FACTORYTALK VIEW STUDIO______________________24 
ADD PROCESS FACEPLATES INTO THE HMI SERVER________________________________25 
ADD DATABASE CONNECTION ________________________________________________28 
ADD A DATA SERVER _______________________________________________________30 
CONFIGURE COMMUNICATIONS _______________________________________________31 
VERIFY COMMUNICATIONS ___________________________________________________35 
SECTION 2: GRAPHICS AND ANIMATION (EST. TIME 20 MIN)______________________________42 
ABOUT THIS SECTION ______________________________________________________42 
GRAPHIC DISPLAYS ________________________________________________________42 
ANIMATION 44 
SECTION 3: TESTING DISPLAYS (EST. TIME 15 MINUTES)________________________________51 
 
3/10/2008 Page 6 of 160 
ABOUT THIS SECTION ______________________________________________________51 
TEST DISPLAY ____________________________________________________________51 
CONFIGURE CLIENT FILE ____________________________________________________52 
RUN CLIENT _____________________________________________________________58 
SECTION 4: TAGS (EST. TIME 5 MINUTES) ___________________________________________61 
TAGS 61 
SECTION 5: ALARMING (30 – 40 MINUTES) __________________________________________64 
ABOUT THIS SECTION ______________________________________________________64 
ALARMING 64 
FACTORYTALK ALARM AND EVENT OBJECTS_____________________________________70 
DEVICE-BASED ALARMS ____________________________________________________80 
OBSERVE CONFIGURED ALARMS IN LOGIX 5000 __________________________________82 
TAG-BASED ALARMS_______________________________________________________85 
SECTION 6: SECURITY (EST. TIME 20 – 30 MIN)_______________________________________86 
ABOUT THIS SECTION ______________________________________________________86 
ABOUT SECURITY _________________________________________________________86 
CREATING A USER AND USER GROUP __________________________________________87 
CONFIGURING ACTION SECURITY______________________________________________90 
CONFIGURING RUNTIME SECURITY_____________________________________________92 
VERIFYING SECURITY SETTINGS_______________________________________________95 
SECTION 7: DATA LOGGING AND TRENDING (EST. TIME 20 MIN) __________________________98 
ABOUT THIS SECTION ______________________________________________________98 
RUNTIME EXPLORATION_____________________________________________________98 
CONFIGURATION EXPLORATION ______________________________________________100 
 
3/10/2008 Page 7 of 160 
QUERYING LOGGED DATA __________________________________________________105 
SECTION 8: FACTORYTALK DIAGNOSTICS SETUP AND THE VIEWER (EST. TIME 20 MIN) ________108 
ABOUT THIS SECTION _____________________________________________________108 
ABOUT FACTORYTALK DIAGNOSTICS__________________________________________108 
DIAGNOSTICS LIST________________________________________________________109 
DIAGNOSTICS VIEWER _____________________________________________________109 
DIAGNOSTICS SETUP ______________________________________________________111 
ODBC DATABASE AS A MESSAGE SOURCE _____________________________________114 
SECTION 9: GLOBAL OBJECTS (EST. TIME 30 MIN) ___________________________________119 
ABOUT THIS SECTION _____________________________________________________119 
GLOBAL OBJECTS________________________________________________________119 
CREATE MULTIPLE REFERENCE OBJECTS ______________________________________119 
GLOBAL OBJECT PARAMETER DEFINITIONS _____________________________________127 
REFERENCE OBJECT PROPERTIES ____________________________________________128 
MODIFYING GLOBAL OBJECTS_______________________________________________130 
DESIGN RECOMMENDATIONS FOR WORKING WITH GLOBAL OBJECTS ___________________138 
SECTION 10: LANGUAGE SWITCHING (EST. TIME 30 MIN)_______________________________139 
ABOUT THIS SECTION _____________________________________________________139 
ABOUT LANGUAGE SWITCHING ______________________________________________139 
FACTORYTALK VIEW SE LANGUAGE SWITCHING _________________________________140 
DEVICE-BASED ALARM LANGUAGE SWITCHING ___________________________________149 
TAG-BASED ALARM LANGUAGE SWITCHING _____________________________________154 
VIEW TRANSLATED ALARM MESSAGES ________________________________________161 
 
3/10/2008 Page 9 of 160 
Welcome to FactoryTalk View SE Hands-On Lab 
About This Hands-On Lab 
Welcome to the Automation Fair Hands-On Lab series! This session provides you with an opportunity 
to explore the basics of FactoryTalk View Site Edition (FactoryTalk View SE). The following sections 
explain what you’ll be doing in this lab session and what you will need to do to complete the hands-on 
exercises. 
Note: In v 5.00 (CPR 9), product name changes have taken place to better reflect Rockwell 
Automation’s system-oriented software and integrated architecture. “RSView SE” was re-branded as 
“FactoryTalk View Site Edition” (or FactoryTalk View SE). Terms used to describe a FactoryTalk View 
SE application and a FactoryTalk directory has changed. The term “network” will be used instead of 
“distributed”. The term “local” will be used instead of stand-alone. This lab uses FactoryTalk View SE 
5.00 (CPR 9). View SE is an integrated package for developing and running multi-user, networked 
human-machine interface (HMI) applications. View SE is designed for automated process or machine 
monitoring, and supervisory control. 
In this lab, you will be working with a local application containing an HMI Server, a data server, and a 
single HMI Client. For this lab, these servers and clients will all be located on the same computer. View 
Studio, the development environment, will also be on this computer. In the deployed system however, 
these components could actually be on separate computers, and additional HMI clients could be used. 
View SE scales easily from small to large systems. This lab procedure contains content and exercises 
for both novice and advanced users. After executing the first few sections of the lab you will be 
provided several options. 
The first 3 sections will take approximately 60 minutes for the novice user to complete. This time 
estimate includes: Add Servers to the Application, Add Content to the Application, Configure and Run a 
Client. The remaining laboratory time is to be used for exploring the additional exercises. The additional 
exercises are optional and the approximate time to complete each exercise is indicated in the 
description. 
Advanced users must complete 
ƒ all ofSection 1 Creating your application 
ƒ Section 2 Graphic Displays - Add Graphic Displays 
ƒ Section 3 Testing Displays - Configure a FactoryTalk View Client File called AF07 or use the pre-
configured client file (C:\LabFiles\Lab 15 FactoryTalk View SE\Client\AF07.cli) 
It is recommended that novice users complete remaining lab procedures in the order they are 
presented, time permitting. 
What You Will Accomplish In This Lab 
As you complete the exercises in this hands-on session, you will gain an understanding of the 
functionality and capability of FactoryTalk View Site Edition by 
ƒ creating an application 
ƒ configuring an HMI server 
ƒ configuring an RSLinx Enterprise data server and enabling it for alarm and event support 
ƒ utilizing graphics and animation 
 
3/10/2008 Page 10 of 160 
ƒ test running displays 
ƒ configuring and running an HMI client file 
ƒ configuring and monitoring alarms (FactoryTalk device and tag based) 
ƒ implementing security 
ƒ working with data log models and trends 
ƒ using the FactoryTalk Diagnostics Viewer 
ƒ working with Global Objects 
ƒ configuring your application for language switching 
Who Should Complete This Lab 
This hands-on lab is intended for individuals who: 
ƒ Have a basic knowledge of HMI software and are involved in the design and implementation of 
supervisory-level HMI projects. 
Lab Materials 
For this Hands-On lab, we have provided you with the following materials that will allow you to complete 
the labs in this workbook. 
Hardware 
This hands-on lab does not require any hardware. A Logix5000 controller could be used in place of 
SoftLogix 5800. 
Note: FactoryTalk Alarms and Events Device Based Alarms requires firmware version 16.20 or higher 
for ControlLogix, CompactLogix L3x and L4x, and DriveLogix. 
Software 
This hands-on lab uses the following software: 
ƒ FactoryTalk Services Platform v2.10.00.0117 
ƒ FactoryTalk View SE v5.00.00.55 
ƒ RSLinx Enterprise v5.00.00.99 
ƒ FactoryTalk Alarms and Events v2.10.00.0117 (included with FactoryTalk View Site Edition and 
RSLinx Enterprise) 
ƒ RSLinx Classic (used for Logix programming) v2.52.00.17 
ƒ RSLogix5000 v16.03.00 
ƒ SoftLogix 16.03.00 (Bld 42) 
ƒ Microsoft SQL Server 2005 Express 
ƒ Microsoft SQL Server Management Studio Express 
 Microsoft SQL Server 2005 Express Edition is a free, redistributable version of Microsoft SQL Server. 
FactoryTalk Alarms and Events uses Microsoft SQL Server as the database engine for logging alarm 
and event information. You can connect to an existing SQL Server database, or you can install 
Microsoft SQL Server 2005 Express, Service Pack 2, which is included in the Redist folder on the 
FactoryTalk View SE and RSLinx Enterprise CDs. 
 
3/10/2008 Page 11 of 160 
Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical 
management tool for managing SQL Server 2005 Express. It is included in the Redist folder on the 
FactoryTalk View SE and RSLinx Enterprise CDs. 
Lab Files 
This hands-on lab uses the following files located in the C:\ LabFiles\Lab 15 FactoryTalk View SE\ 
subdirectory: 
ƒ LanguageSwitching – contains 3 files that will be used in the language switching section of the lab 
ƒ AF07_translated.xls 
– Translated file for FactoryTalk View SE 
ƒ AF07_SE_Lab-Tags_translated.TXT 
- Translated file for FactoryTalk Alarms and Events device-based alarm messages in RSLogix 
5000 
ƒ AF07_FTAETagServer_AlarmExport_translated.xls 
- Translated file for FactoryTalk Alarms and Events tag-based alarm messages in the 
FactoryTalk Tag Alarm and Event Server 
ƒ RSLogix 5000 – contains 3 files that can be used with RSLogix 5000. 
ƒ AF07_SE_Lab.ACD – control program to be used in this lab 
ƒ AF07_SE_Lab_pre_translation.ACD – copy of control program that is for the beginning of this 
lab prior to Tank 101 alarm messages being converted. Some alarm messages were 
preconfigured for language switching at the beginning of this lab 
ƒ AF07_SE_Lab_post_translation.ACD – control program with Tank 101 alarms converted for 
language switching. This is a backup copy of what the control program should look like after 
alarm messages have been translated 
ƒ SQL – contains 1 file for a SQL Query in Microsoft SQLExpress that will be used in the Data 
Logging section of this lab 
ƒ ViewTank101DataLog.sql 
ƒ Preconfigured FactoryTalk View SE files to be used in this lab: 
ƒ AlarmLogViewer.gfx 
ƒ AlarmStatusExplorer.gfx 
ƒ AlarmSummary.gfx 
ƒ Footer.gfx 
ƒ Header.gfx 
ƒ TankAlarmSummary.gfx 
ƒ TankOverview.gfx 
ƒ ClientKeys.key 
ƒ ClientStartup.mcr 
ƒ TankDataLogging.gfx – used in the Data Logging Section of this lab 
ƒ Tank101.mdf – used in the Data Logging Section of this lab 
ƒ Client – contains a preconfigured FactoryTalk View SE Client file 
ƒ AF07.cli 
 
3/10/2008 Page 12 of 160 
Lab Setup 
Copied lab files to C:\ LabFiles\Lab 15 FactoryTalk View SE\ 
Copied C:\LabFiles\ Lab 15 FactoryTalk View SE\ RSLogix 5000 \AF07_SE_Lab.ACD to C:\RSLogix 
5000\Projects\AF07_SE_Lab.ACD 
Shortcuts for the following applications, directory, and files were created in the Startup Menu: 
ƒ Lab 15 FactoryTalk View SE – shortcut to C:\ LabFiles\Lab 15 FactoryTalk View SE\ 
ƒ SQL Server Management Studio Express – application shortcut 
ƒ Diagnostics Viewer – application shortcut 
ƒ AF07_SE_Lab.ACD – shortcut to C:\RSLogix 5000\Projects\AF07_SE_Lab.ACD 
ƒ FactoryTalk View Studio – application shortcut 
Installed files for East Asian languages. 
Note you only have to do this to demonstrate the Chinese language support. 
SQL Server Express setup for the FactoryTalk Diagnostics and FactoryTalk View SE Data Logging 
sections 
ƒ Created a database called FactoryTalk using the administrator Workgroup account 
ƒ Created a System DSN called FactoryTalk using the FactoryTalk database as the default database. 
Note that the files and setup steps for the optional sections (Language Switching, Data Logging, and 
FactoryTalk Diagnostics) are not required unless you want to do those sections. 
Document Conventions 
Throughout this workbook, we have used the following conventions to help guide you through the lab 
materials. 
This style or symbol: Indicates: 
Words shown in bold italics 
(e.g., RSLogix 5000 or OK) 
Any item or button that you must click on, or a menu name 
from which you must choose an option or command. This will 
be an actual name of an item that you see on your screen or 
in an example. 
Words shown in bold italics, 
enclosed in single quotes 
(e.g., 'Controller1') 
An item that you must type in the specified field. This is 
information that you must supply based on your application 
(e.g., a variable). 
Note: When you type the text in the field, remember that you 
do not need to type the quotes; simply type the words that 
are contained within them (e.g., Controller1). 
 
The text that appears inside of this gray box is supplemental 
information regarding the lab materials, but not information 
that is required reading in order for you to complete the lab 
exercises. The text that follows this symbol may provide you 
with helpful hints that can make it easier for you to use this 
product. Most often, authors use this “Tip Text” style for 
important information they want their students to see. 
 
3/10/2008 Page 13 of 160 
 
The text that appears inside this gray box with the graphic will 
indicate that a feature is new in the V 5.00 (CPR 9) Release. 
Note: If the mouse button is not specified in the text, you should click on the left mouse button. 
Before You Begin 
This lab is intended to be a compilation of several smaller exercises designed to instruct the user on the 
basics of FactoryTalk View Site Edition. Though the lab can be done linearly, where all exercisesare 
cumulative, the only required exercises are all of Section 1 Creating your application, Section 2 Graphic 
Displays - Add Graphic Displays, and Section 3 Testing Displays - Configure a FactoryTalk View Client 
File called AF07. From there, the user may select which exercises interest them most without having to 
be concerned with numerical order. 
The following steps must be completed before starting the lab exercise: 
1. If Log On To Windows dialog is active type ‘administrator’ for Username and type ‘rockwell’ for 
password. 
2. Use the same Login information if prompted to Log On to the FactoryTalk Directory or when 
creating a FactoryTalk Alarms and Events History Database. 
 
 
Overview 
About this lab 
This lab will outline the major components and fundamental ideas of FactoryTalk View Site Edition. It 
will specifically: 
ƒ Discuss the components of FactoryTalk View SE 
ƒ Discuss the differences between FactoryTalk View SE Local and Network Application 
ƒ Discuss HMI Servers, data servers, and Tag Alarm and Event Server 
ƒ Discuss FactoryTalk Alarms and Events Services for Device Based and Tag Based Alarms 
FactoryTalk View Site Edition 
FactoryTalk® View Site Edition is an integrated software package for developing and running human-
machine interface (HMI) applications that involve multiple users and servers, distributed over a network. 
A member of the FactoryTalk family of products, FactoryTalk View Site Edition (also called FactoryTalk 
View SE) provides all the tools you need to create powerful, dependable process monitoring and 
supervisory control applications. 
FactoryTalk View SE software is designed for use with Microsoft® Windows® Server 2003, Windows 
XP, and Windows 2000 operating systems. 
FactoryTalk View Site Edition consists of several pieces of software you can use to build automation 
applications. Depending on the particular software packages installed, you will have one or more of the 
following pieces of software: FactoryTalk View Studio, FactoryTalk View SE Client, FactoryTalk View 
SE Server, FactoryTalk Alarms and Events, FactoryTalk Services Platform, FactoryTalk Administrator 
Console, FactoryTalk™ Directory, and FactoryTalk Activation. 
FactoryTalk View Studio 
 Start > Programs > Rockwell Software > FactoryTalk View > FactoryTalk View Studio 
FactoryTalk View Studio is configuration software for developing and testing FactoryTalk View SE 
applications. FactoryTalk View Studio contains editors for creating complete applications, and includes 
client and server software for testing the applications you create. Use the editors to create applications 
that are as simple or as complex as you need. You can use FactoryTalk View Studio to develop 
FactoryTalk View Site Edition and FactoryTalk View Machine Edition (ME) applications. 
FactoryTalk View comes with process faceplates and graphic libraries that can be used in your 
applications. Process faceplates are preconfigured to work with various Logix5000 instructions (for 
example, PIDE, D2SD, and the new ALMD and ALMA instructions). Many of the graphic library objects 
are preconfigured with animation. Use the objects as they are, or change them to suit your needs. 
When you have finished developing an application, use FactoryTalk View SE Client to view and interact 
with the application. 
 
3/10/2008 Page 15 of 160 
FactoryTalk View SE Client 
 Start > Programs > Rockwell Software > FactoryTalk View > FactoryTalk View Client 
FactoryTalk View SE Client is a complete runtime operating environment for viewing and interacting 
with FactoryTalk View SE local and network applications. To set up a FactoryTalk View SE Client, you 
need to create a configuration file using the FactoryTalk View SE Client wizard. The HMI Server does 
not have to be running when you configure a FactoryTalk View SE Client. With the FactoryTalk View 
SE Client you can: 
ƒ Load, view, and interact with multiple graphic displays at a time from multiple servers 
ƒ Perform alarm management 
ƒ View real-time and historical trends 
ƒ Adjust set points 
ƒ Start and stop components on any server 
ƒ Provide a secure operator environment 
ƒ And much more! 
FactoryTalk View Administration Console 
 Start > Programs > Rockwell Software > FactoryTalk View > Tools > SE Administration 
Console 
FactoryTalk View Administration Console is for administering FactoryTalk View applications after they 
have been deployed. FactoryTalk View Administration Console contains a sub-set of the FactoryTalk 
View Studio editors, so you can make minor changes to an application without the need for installing 
FactoryTalk View Studio. The FactoryTalk View Administration Console has a two hour run-time limit. A 
warning message is displayed five minutes before the time is up. To continue using it you simply shut it 
down and restart it. 
FactoryTalk View Administration Console allows you to: 
ƒ Change the properties of an HMI server. 
ƒ Change the properties of a data server. 
ƒ Add FactoryTalk users to an application, using the Runtime Security editor. 
ƒ Set up security for commands and macros, using the Runtime Secured Commands editor. 
ƒ Run FactoryTalk View commands from the Command Line. 
ƒ Change how HMI tag alarms are logged and annunciated, using the Alarm Setup editor. 
ƒ Change the path of data log models. 
ƒ Change which system activities are logged and how frequently, using the Diagnostics Setup editor 
(on the Tools menu). 
ƒ Change the location alarms are logged to, and manage log files, using the Alarm Log Setup editor 
(on the Tools menu). 
ƒ Import and export HMI tags using the Tag Import and Export Wizard (on the Tools menu). 
 
3/10/2008 Page 16 of 160 
FactoryTalk View SE Server 
The FactoryTalk View SE Server, also called the HMI server, stores HMI project components (for 
example, graphic displays, global objects, and macros) and serves them to clients. The server also 
contains a database of tags, performs historical data logging, and HMI alarm monitoring. FactoryTalk 
Alarms and Events can be used instead of FactoryTalk View SE HMI alarm monitoring. To maintain 
compatibility with existing applications, FactoryTalk View still supports the traditional HMI alarm 
monitoring. 
The FactoryTalk View SE Server has no user interface. Once installed, it runs as a set of ‘headless’ 
Windows services that supply information to clients as they request it. 
FactoryTalk Alarms and Events 
Before FactoryTalk® Alarms and Events (introduced in Version 5.00), FactoryTalk View SE supported 
only HMI tag alarm monitoring. To maintain compatibility with existing applications, FactoryTalk View 
still supports this type of alarm monitoring. 
However, FactoryTalk Alarms and Events now allows multiple FactoryTalk products to participate 
together in a common, consistent view of alarms and events throughout a FactoryTalk system. 
FactoryTalk Alarms and Events supports two types of alarm monitoring: 
ƒ Device-based alarm monitoring. Pre-built alarm instructions, available in RSLogix 5000 v. 16 or 
later, are programmed in a logic project and then downloaded into a Logix5000 controller. The 
controller detects alarm conditions and publishes event information, which is routed through the 
system for display and logging. 
ƒ Tag-based alarm monitoring. If you are not using Logix5000 controllers, or if you do not want to use 
the pre-built alarm instructions available with RSLogix 5000, tag-based alarm monitoring offers the 
equivalent of HMI Tag Alarm Monitoring, but with an expanded feature set. Software-based Tag 
Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish 
event information for display and logging. Tag-based alarm monitoring is supported for Logix5000 
controllers, PLC-5, and SLC 500 devices communicatingthrough Rockwell Automation Device 
Servers (RSLinx Enterprise), or for third-party controllers communicating through OPC data 
servers. 
FactoryTalk Services Platform 
FactoryTalk Services Platform provides common services (such as diagnostic messages, health 
monitoring services, and access to real-time data) to products and applications in a FactoryTalk 
system. 
FactoryTalk Directory 
FactoryTalk Directory centralizes access to system resources (for example, FactoryTalk View SE 
Servers, or OPC servers) and names (for example, data tags, graphic displays, and log models), for all 
of the FactoryTalk products and components participating in an automated control system. 
FactoryTalk Administration Console 
 Start > Programs > Rockwell Software > FactoryTalk Administration Console 
Part of the FactoryTalk Services Platform, FactoryTalk Administration Console is an optional, stand-
alone tool for developing applications and managing a FactoryTalk system. You can use FactoryTalk 
Administration Console or FactoryTalk View Studio to develop applications and manage a FactoryTalk 
system. Only FactoryTalk View Studio can be used to create HMI servers and HMI projects. 
 
3/10/2008 Page 17 of 160 
FactoryTalk Administration Console allows you to: 
ƒ Create and configure application, area, and data server elements in a FactoryTalk Directory. 
ƒ Create and configure alarm and event servers, including both tag-based and device-based 
servers. 
ƒ Configure alarm conditions for tag-based alarm detection. 
ƒ Organize securable actions into groups. 
ƒ Create database definitions for logging historical alarm and event messages. 
ƒ Configure options for routing, logging, and viewing diagnostic messages. 
ƒ Back up and restore an entire directory, an individual application, or system settings. 
ƒ Set up redundancy for OPC data servers and Tag Alarm and Event Servers. 
ƒ Configure client computers to recognize the location of a Network Directory Server computer. 
ƒ Configure system-wide policy settings. 
ƒ Secure a FactoryTalk system with security services. 
FactoryTalk Activation 
 Start > Programs > Rockwell Software > FactoryTalk Activation > FactoryTalk Activation Tool 
FactoryTalk Activation provides a secure, software-based system for activating Rockwell Software 
products and managing software activation files. With FactoryTalk Activation, there is no need for a 
physical “master disk” or any physical media; instead, activation files are generated and distributed 
electronically. 
FactoryTalk Activation provides these types of activations: 
ƒ Local node-locked activations are locked to a single computer. 
ƒ Mobile node-locked activations are locked to a hardware dongle. 
ƒ Shared concurrent activations are locked to an activation server computer, and shared by client 
computers on the network. 
There are two types of shared concurrent activation: floating and borrowed. Floating concurrent 
activation requires a continuous network connection, while borrowed concurrent activation does not. 
FactoryTalk View SE - Network and Local 
Network Applications 
A network application can contain several servers, running on multiple computers on a network, with 
multiple client users connecting to the application simultaneously, from anywhere on the network. For 
example, you may use separate servers for different functional areas or locations within your 
enterprise, and allow clients to interface to any of the servers. Network applications have one or more 
areas (see Areas definition below), one HMI server per area, and one or more data servers. An area 
may contain another area within it. 
Once you have created the applications and an HMI server, you can use the FactoryTalk View Studio 
editors in the HMI server project to create application components such as graphics displays, global 
objects, and data log models. 
 
3/10/2008 Page 18 of 160 
Areas: A key part of the network architecture system is the area. An area is a logical division within 
your application. You can think of areas as partitions of your hard drive. The partitions are all on the 
same main disk (or application, in this analogy), but they divide it logically and hold information 
independently of each other. An area can also be used to organize the application in a way that 
makes sense for the process it is controlling. 
For example, an area might represent a portion of a process, or a region within the process facility. 
An automotive plant could be divided into areas called Press and Fabrication, Body Shop, Paint 
Shop, Engine, and Transmission; a bakery could be divided into areas called Ingredients, Mixing, 
Baking, and Packaging. Alternatively, a plant with identical production lines could be divided into 
areas called Line 1, Line 2, Line 3, and so on. This would allow you to add new, identical production 
lines to the application by copying HMI server projects into new areas. 
 
Root Area: All FactoryTalk View applications have one system-defined area called the root area, 
which has the same name as the application. The application root area can contain one HMI server, 
and one or more data servers. 
Best Practice 
Since an area is nothing more than a logical method of organizing the application, and not a physical 
entity, there is not a limit to the number of areas that can reside within an application. However, there 
is a limit of 1 HMI server per area and 10 HMI servers per application*. 
The recommended limit of data servers within an application is 10*. There is not a limit to the number 
of data servers that can co-exist in the same area. However, it makes sense to logically organize the 
data servers that are serving alarms in order for the alarm summary to filter alarms appropriately at 
runtime. For example, a single area may contain an HMI server for a physical location of a facility, an 
RSLinx Enterprise data server (configured as a FactoryTalk device based alarm server), and a 3rd 
party OPC server (configured with the FactoryTalk tag based alarm server). This configuration allows 
for the alarm summary to filer alarms based on the area name, regardless of which server the alarm 
comes from. 
What you want to avoid is one physical installation of a data server to be referenced multiple times from 
different areas of the application. This is not necessary because FactoryTalk allows any client to see 
any data point within the application, regardless of which area it comes from. 
*Note: The initial release of FactoryTalk Alarms and Events have different limits than FactoryTalk View 
SE 5.0. Please refer to the FactoryTalk Alarms and Events Quick Start Guide or Answer id 44177 
within the Rockwell Automation Knowledgebase for more information.
 
3/10/2008 Page 19 of 160 
This is an example of a FactoryTalk View SE network application. 
 
The Insta Corp application consists of four different defined areas: ie_packaging, ie_production, 
is_packaging, and is_production. The areas are marked by the folders that are right off the root, 
which is the application Insta Corp. 
Try looking at one of the areas – ie_packaging, the topmost area. Notice that the HMI server called 
IE_CasePack is located inside the area. 
The folders under the ie_packaging HMI Server titled System, HMI Tags, Graphics, Alarms, Logic and 
Control, and Data Log are all different components you can configure under each HMI server – they are 
not areas within the area, but are actually components of an HMI server. 
There is a data server called RSLinx Enterprise located under the root area (Insta Corp). 
Root Area 
Network 
Directory 
Area 
Data server 
HMI Server 
Area Area Areas 
HMI Server HMI Server HMI Servers
 
3/10/2008 Page 20 of 160 
The diagram below shows an example system architecture usinga Network application as part of a 
distributed FactoryTalk system. 
 
 
3/10/2008 Page 21 of 160 
Local Applications 
A local application is similar to an RSView32 project; all application components and the FactoryTalk 
View SE client are located on a single computer. There is only one HMI server that is created for you in 
the root area when the application is created. You may use local applications for parts of the plant or 
process that are self-contained and are not related to other parts of the process. 
The diagram below shows an example system architecture using a Local application as part of a stand-
alone FactoryTalk system. 
 
 
 
3/10/2008 Page 22 of 160 
Creating a new FactoryTalk View SE application 
Here are the general steps for creating an application: 
1) Create a local or network application 
2) If it’s a network application, add one or more Areas 
3) If it’s a network application, one HMI server can be added per area (local creates one 
automatically). Choose to add any of the faceplate displays into the HMI server. 
4) Set up data server communications. Add one or more of the following data servers 
a. Rockwell Automation Device Server 
b. OPC Data server 
5) Set up Tag Alarm and Event Server 
6) Create graphic displays, global objects, and other components into your HMI server 
7) Set up historical FactoryTalk alarm and event logging 
8) Set up Security 
9) Set up a run-time FactoryTalk View SE Client 
 
3/10/2008 Page 23 of 160 
FactoryTalk View SE – Servers 
HMI Servers 
HMI servers are software programs that supply information to clients as they request it. An HMI server 
stores HMI project components such as graphic displays, and serves these components to clients. An 
HMI server also manages a database of tags, detects HMI tag alarms, and logs historical data. 
Data Servers 
A data server provides a route to physical devices on the network, allowing applications to monitor and 
control the values in those devices. For example, data servers can connect application clients to 
programmable controller values, OPC® tags (and their value or status information), or named variables 
in a Logix5000 controller. 
A data server can be a Rockwell Automation Device Server (RSLinx Enterprise) or a third-party OPC 
data server that serves up tag values. Once a data server is configured, you can set it up to point to a 
specific controller such as a ControlLogix processor. Properly configuring a data server allows you to 
browse for a tag directly. 
The following types of data servers are supported: 
ƒ Rockwell Automation Device Servers (RSLinx Enterprise) provide best performance when 
communicating with Logix5000 controllers, or with many clients. You can also use RSLinx 
Enterprise servers to subscribe to device-based alarms and events. 
ƒ OPC data servers (including RSLinx Classic) support any data server that conforms to the OPC-DA 
2.0 standard. OPC stands for OLE for Process Control, a protocol that allows FactoryTalk View to 
retrieve tag values from: 
ƒ Rockwell Automation programmable controllers and devices, using RSLinx Classic or RSLinx 
Gateway as an OPC server. 
ƒ Third-party controller devices, such as Siemens or Modicon®, using third-party OPC servers. 
Alarm and Event Servers 
FactoryTalk Alarms and Events allow multiple FactoryTalk products to participate together in a 
common, consistent view of alarms and events throughout a FactoryTalk system. FactoryTalk Alarms 
and Events support two types of alarm monitoring: 
ƒ Device-based alarm monitoring. Pre-built alarm instructions, available in RSLogix 5000 v. 16 or 
later, are programmed in a logic project and then downloaded into a Logix5000 controller. The 
controller detects alarm conditions and publishes event information, which is routed through the 
system for display and logging. 
ƒ Tag-based alarm monitoring. If you are not using Logix5000 controllers, or if you do not want to use 
the pre-built alarm instructions available with RSLogix 5000, tag-based alarm monitoring offers the 
equivalent of HMI Tag Alarm Monitoring, but with an expanded feature set. Software-based Tag 
Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish 
event information for display and logging. Tag-based alarm monitoring is supported for Logix5000 
controllers, PLC-5, and SLC 500 devices communicating through Rockwell Automation Device 
Servers (RSLinx Enterprise), or for third-party controllers communicating through OPC data 
servers. 
An Alarm and Event Server can be a Rockwell Automation Device Server (RSLinx Enterprise) that is 
enabled for monitoring device-based alarms or a FactoryTalk Alarm and Event Tag Server that has 
been configured for monitoring tag-based alarms. 
 
3/10/2008 Page 24 of 160 
Section 1: Creating your application (est. time 20 
min) 
About This Lab 
In this section of the lab you will: 
ƒ Create a Local Application called AF07 
ƒ Add Process Faceplate Displays (Alarm Analog – ALMA, Alarm Digital – ALMD, Discrete 2-
State Device – D2SD, Enhanced PID – PIDE, and Help – Help Browser) into your HMI Project 
ƒ Add Database Connection called FTAEHistory for FactoryTalk Alarms and Events Historical 
Logging 
ƒ Add a data server called RSLinx Enterprise 
ƒ Configure a Communications path called SoftLogix that will point to the SoftLogix controller 
ƒ Verify communications 
This entire section must be completed prior to doing any other sections in this lab. 
Creating Local HMI Project in FactoryTalk View Studio 
To create a local application 
1. Run FactoryTalk View Studio. Select the Start > FactoryTalk View Studio menu item. 
 
You will be prompted with 
 
 
 
Wait for several seconds to allow FactoryTalk View Studio to create the application. After the AF07 
HMI Server has been created, you will be prompted with the Add Process Faceplates dialog. 
2. Select 
Site Edition (Local) 
3. Select 
Continue
4. Select 
New
5. Type 
‘AF07’
6. Select 
Create
 
3/10/2008 Page 25 of 160 
Add Process Faceplates into the HMI Server 
1. Select the Clear All button. 
2. Check the boxes for these display types: 
• Alarm Analog – ALMA 
• Alarm Digital – ALMD 
• Discrete 2-State Device – D2SD 
• Enhanced PID – PIDE 
• Help – Help Browser 
Your dialog window should look like this: 
 
3. Click the OK button. 
4. Observe that a local application, AF07, has been created. The HMI Server called AF07 has been 
created in the root area (AF07). 
5. Maximize or resize your FactoryTalk View Studio window to the desired size for working with 
your application. 
 
3/10/2008 Page 26 of 160 
This is the Application Explorer window that will be used throughout this entire hands-on lab. The 
Explorer allows you to select different objects, displays, and other components of the FactoryTalk View 
SE application. 
 
 
Types of Graphic Displays 
Standard Displays - stored in the Displays folder. 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 controller. 
Global Object displays - stored in the Global Objects folder. Global object displays 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, the changes are automatically 
applied to the copies. 
Library displays - stored in the Libraries folder. A library display contains ready-made graphic objects 
that you can use in other displays.The faceplate displays and the global objects that were used to create them will be added to the HMI 
Server under the Displays and Global Objects folders. There were also 
some image files added for the Alarm faceplates under Images folder. 
6. Click on the + next to the folders to expand them. Observe what has been added. 
Note: Only the image files starting with State_ were added with the process faceplates. The other 
image files are there when the HMI Server is created. 
7. Expand the Libraries folder . All these library files are there when an HMI Server is 
created. 
 
Local 
Director
Application 
(Root Area) 
HMI 
Server 
Displays for 
Process Faceplates 
added here
Global Objects for 
Process Faceplates 
added here
 
3/10/2008 Page 27 of 160 
 
 Add Process Faceplates Dialog 
When you add an HMI server to a network application, or when you create a new local application, you 
have the option to add the process faceplate displays that are installed with FactoryTalk View SE. The 
Add Process Faceplates Dialog box will open, if it’s set to display when you create a new HMI server. If 
you don’t want to add faceplates, click Cancel to close the dialog box, without affecting HMI server 
creation. If you don’t want to be prompted every time you create an HMI Server, uncheck the option to 
“Display this dialog when creating a new application”. 
After you create the application or HMI server you can still add process faceplates by right-clicking on 
the HMI server and then selecting the Add Process Faceplates menu item. If you added a display 
previously, you can either replace the existing display or remove it from the list of displays. 
Note: Adding faceplate displays to an application affects the license count. Each added faceplate 
display (.gfx file) counts as one display for activation purposes. 
New Faceplates 
The Alarm Analog – ALMA and Alarm Digital – ALMD faceplates are preconfigured to work with the 
new RSLogix 5000 instructions that are available in V 16 or later. These faceplates along with the 
existing ones can be used as is or changed to suit your needs. 
 
3/10/2008 Page 28 of 160 
Add Database Connection 
In the next section you will be adding and configuring a Rockwell Automation Device Server (RSLinx 
Enterprise) and enabling it for alarm and event support and alarm and event history support. 
 FactoryTalk Alarm and Event Historian 
There is a FactoryTalk Alarm and Event Historian that performs historical logging of FactoryTalk alarm 
and event data (generated by one or more Rockwell Automation Device Servers (RSLinx Enterprise) or 
FactoryTalk Tag Alarm and Event Servers) to a database. This component also defines and manages 
database definitions between alarm and event servers and logging destinations. You can log historical 
alarms and events to a Microsoft SQL Server 2005 Express Edition (SP2) database (which can be 
optionally installed from the FactoryTalk View SE or RSLinx Enterprise CDs) or to your own existing 
Microsoft SQL Server databases. 
Before you add and configure the Rockwell Automation Device Server you are going to create a 
database so you can also enable FactoryTalk Alarm and Event History logging in the next section. 
Alarming will be discussed in more detail later in the lab. 
1. Expand the Connections folder. 
2. Right-click on Databases folder, select the New Database… context menu item 
 
3. When the Alarm and Event Historian Database Properties opens enter: 
Definition name: FTAEHistory 
Database user name: administrator 
Database password: rockwell 
Database name: FTAEHistory 
And leave the defaults for the other fields. 
 
3/10/2008 Page 29 of 160 
Your properties dialog should look like this: 
 
4. Click on OK. 
5. When you are prompted with the Database does not exist message box: “The database will be 
created. The database user will also be created. If the user already exists, the user will be assigned 
access to the database. Do you want to create the database?” click the Yes button 
 
6. After the database is created the dialog will close. Expand the Databases folder to confirm that it 
was created. 
 
 
 
3/10/2008 Page 30 of 160 
Add a data server 
To allow our application to monitor and control the values in the SoftLogix Controller that is running the 
control program for this lab you need to add a data server. You will add a Rockwell Automation Device 
Servers (RSLinx Enterprise). It provides the best performance when communicating with Logix5000 
controllers. 
To monitor alarms in a Logix5000 controller, a Rockwell Automation Device Server (RSLinx Enterprise) 
needs to be added to a FactoryTalk application. Alarm and event support must be enabled. The device 
server subscribes to alarms in the controller and then publishes the alarm information to FactoryTalk 
Alarms and Events services. Device-based alarms will be discussed in the Alarming and Language 
Switching sections of this lab. 
1. Right-click on the application node AF07, select the Add New Server > Rockwell Automation 
Device Server (RSLinx Enterprise)… context menu item. 
 
2. The RSLinx Enterprise Server Properties will appear. Leave defaults on the General tab. 
 
4. Check the Enable alarm and 
event support option
5. Check the Enable history option 
6. Select the FTAEHistory 
database definition 
3. Select the Alarms and Events tab 
7. Click the OK button 
 
3/10/2008 Page 31 of 160 
8. Verify that the RSLinx Enterprise device server has been successfully added into your application. 
 
 
Configure Communications 
We are going to configure a device shortcut. 
Device Shortcuts: A Device Shortcut allows you to create a ‘pointer’ to a device that you can refer to 
throughout the application while developing displays. This enables the user to change the location of a 
processor or other such device in one place, which then propagates throughout the rest of the project, 
without having to change all tag references to that processor. A device shortcut is similar to a Windows 
shortcut on your computer’s desktop that provides easy access to an application. 
 
 Communications Setup Editor Improvements 
Offline tag browsing no longer requires you to associate the device shortcut with a controller. In 
previous releases, you were required to associate a shortcut with both a controller and an offline tag file 
to be able to browse the tags in the offline tag file. You can now create a shortcut that is associated 
only with the offline tag file if all you want to do is browse tags in that file. 
The Communication Setup editor has been enhanced to prevent the creation of shortcuts that point to 
devices that do not provide data (such as communication modules and backplanes). 
The Communication Setup editor now provides status messages about shortcuts as you create them as 
well as a summary of all messages via a shortcut verification report. 
The Communication Setup editor has a new option for enabling alarm and event support at the device 
level. 
Warnings have been added to FactoryTalk to tell users if making an edit in the development 
environment will adversely affect the run-time system. If the change is made through a dialog box, this 
warning icon appears next to the component where the edit can be made. 
Open Communications Setup dialog 
1. Expand the RSLinx Enterprise device server. Double-click on Communication Setup 
 
The Communication Setup dialog will appear to the right of the Explorer tree. 
 
3/10/2008 Page 32 of 160 
Add Device Shortcut 
 
Browse to the controller 
1. Right-click on the 1789-A17, Backplane, Select Start Browsing 
 
 
1. Click the 
Add button 
2. Type the text 
‘SoftLogix’ 
 
3/10/2008Page 33 of 160 
 
2. Select 2, 1789-L60/A, AF07_SE_Lab 
Note: 2 is the slot number of the SoftLogix module that is in the chassis. This is where the 
control program for this lab is running. 
 
Add Offline Tag File 
1. Click the Browse… button next to the Offline Tag File entry field. Browse to C:\RSLogix 
5000\Projects\ folder. Select the AF07_SE_Lab.ACD file. Click the Open button. 
 
Offline Tag Browsing 
The offline tag file will enable you to browse a ControlLogix controller's tags when that controller is not 
online. The file must be located on the local PC, not on a networked location. 
 
 Offline Tag Browsing Improvement 
Offline tag browsing no longer requires you to associate the device shortcut with a controller. In 
previous releases, you were required to associate a shortcut with both a controller and an offline tag file 
to be able to browse the tags in the offline tag file. You can now create a shortcut that is associated 
only with the offline tag file if all you want to do is browse tags in that file. 
Enable Alarms and Events support 
1. Change the Enable Alarms & Events setting to Yes 
 
 
3/10/2008 Page 34 of 160 
Verify Configuration 
1. Verify that the Device Shortcut named SoftLogix is highlighted and that slot 2 is highlighted and 
reads 2, 1789-L60/A, AF07_SE_Lab for your Primary Device. Click the OK button 
2. The Verify dialog will appear. Review your changes. Make sure your shortcut is SoftLogix we 
will be using pre-configured displays referencing that shortcut name. Click the Yes button. 
 
The Communications Setup dialog should close. 
Your device shortcut has been created. 
 
3/10/2008 Page 35 of 160 
 
Verify Communications 
Let’s take a minute to verify that communications is setup correctly and that we are getting alarms. 
Verify that you are getting alarms by adding a FactoryTalk Alarms and Events Object to a display and 
then testing that display in FactoryTalk View Studio. Verify that you can access controller tags from the 
online SoftLogix Controller and the offline tags file by performing tag browses. We will go into more 
details about these topics in the Tags and Alarms sections of this lab. 
FactoryTalk Alarms and Events Verification 
1. In the Explorer, right-click on the Display folder, select the New context menu item 
 
An untitled display will be opened. 
2. Single-click to select the Alarm and Event Summary button from the tool menu. 
 
Or 
Select the Objects > Alarm and Event > Summary menu item. 
3. Mouse over the upper left corner of the empty display, you will see the cursor change to show that 
the Alarm and Event Summary object has been selected. Single-click and hold down the mouse 
button, drag the cursor to the lower right corner of the display and release the mouse button. As 
you are dragging the mouse you will see a rectangle to show the size of the object that will be 
created. 
 
 
3/10/2008 Page 36 of 160 
After you release the mouse button the Alarm and Event Summary will appear. 
4. Single-click on the Test Display button from the tool menu. 
 
 
5. The indicator in the lower left corner of the Alarm and Event Summary display should be green to 
indicate that you are connected to the RSLinx Enterprise Server. It may take several seconds for 
the services to startup before you see alarms in the list. Mouse over the indicator to verify your 
connection. 
 
 
Note: The alarm count of 32 may not be the same on your display. 
 
You should also start to see alarms appear in the summary (This may take a few moments). 
6. Click the Edit Display button to get back to edit mode. 
 
7. To remove the object from the display perform one of the following actions: 
- Select the Edit – Undo menu item 
- Ctrl-Z - Select the CTRL and Z keys at the same time 
- Single-click on the Alarm and Event Summary object and select the delete key 
 
Diagnostics List 
The Diagnostics List shows information about system activities. It’s located above the status bar at the 
bottom of the FactoryTalk View Studio main window. You can hide, move, resize, and clear messages 
from the Diagnostics List. 
8. Look at the Diagnostics List and the messages in it. Use the arrows to scroll through the messages 
or resized the window so you can see 3 or 5 lines at a time. 
 
To change the size of the diagnostic window mouser the upper edge until you see the double lines, 
mouse down and drag up to change the size. Release the mouse when you have the desired 
window size. 
 
3/10/2008 Page 37 of 160 
 
You should see messages similar to the following. 
 
 
 
Notice the message “Successfully subscribed to 46 alarms from controller SoftLogix.” This 
message is an informational message to help verify that your system is configured properly. 
We have just verified that you have the RSLinx Enterprise Device Server and the SoftLogix Device 
Shortcut properly configured for FactoryTalk Alarms and Events. 
 Controller Status Alarms 
Rockwell Automation Device Servers (RSLinx Enterprise) generate diagnostic alarms relating to 
Logix5000 controllers that are producing alarms in a FactoryTalk Alarms and Events system. These 
alarms are referred to as controller status alarms and they indicate a problem with the connection to a 
controller or the status of a controller. A single controller status alarm is produced for each shortcut that 
is configured with alarms and events enabled. 
The following conditions cause a controller status alarm to go In Alarm: 
• Unable to connect to the controller 
• Unable to get a list of list of alarms contained in the controller because there is no program or 
program download in progress 
• Unable to subscribe to one or more alarms in the controller because the controller has insufficient 
memory to create subscription 
• Connection to the controller is lost 
• Controller was switched to Program Mode 
• Program download 
• Non-recoverable program fault 
• Recoverable program fault 
Controller status alarms have the same name as the shortcut that references the controller. The alarm 
message is not user configurable and the severity for all status alarms is configured in the system-wide 
severity settings. 
 
 
3/10/2008 Page 38 of 160 
Verify access to Offline and Online Tags 
Let’s add two numeric input objects and perform a tag browse to an offline and online tag. 
1. Single-click on the Numeric Input button from the tool menu. 
 
 
Or 
 
Select the Objects > Numeric and String > Numeric Input menu item. 
2. Mouse over a blank area on the display, you will see the cursor change to show that the Numeric 
Input object has been selected. Single-click and hold down the mouse button drag the cursor to 
down and to the right and release the mouse button. As you are dragging the mouse you will see a 
rectangle to show the size of the object that will be created. 
 
When you release the Numeric Input Properties dialog will appear. 
 
 Numeric Input Enhancement 
Numeric input object allows for user-assigned minimum and maximum values that are validated prior to 
download. 
3. Click on the Connections tab. 
 
3/10/2008 Page 39 of 160 
4. Click on the Tags… button next to the Value field. 
 
5. The Tag Browser will open. If you don’t see a folder for SoftLogix, right-click on AF07, select 
the Refresh All Folders context menu item. 
 
6. The browser window and panes can be resized. Expand the tree on the left and navigate to 
SoftLogix - Offline – Program:Tank101 - JacketTempLoop 
JacketTempLoop is an Enhanced PIDE data structure. 
 
Click on CV in the right pane. CV is a member tag of the Enhanced PIDE. It is an output value of 
the PIDE. Your selectedtag should look like this: 
 
3/10/2008 Page 40 of 160 
 
7. Click the OK button. 
8. The tag will appear in the Tag/Expression field next to the Value. 
9. Repeat steps 4 - 7 and select the 
::[SoftLogix]Program:Tank101.JacketTempLoop.CVEUMin tag for the Minimum 
Tag/Expression. 
 
10. Repeat steps 4 – 7 and select the 
::[SoftLogix]Program:Tank101.JacketTempLoop.CVEUMax tag for the Maximum 
Tag/Expression. 
 
11. Click the OK button on the Numeric Input Properties dialog. 
12. Single-click on the Test Display button from the tool menu. 
 
 
13. 0 should appear on the display. This actually verifies that you got the tag from the offline tag file 
and you are online with the controller. If you were not online with the controller, it would appear 
as what is called a wireframe, because the data is not available at this time. It would look 
something like this instead. 
 
 
3/10/2008 Page 41 of 160 
14. Click the Edit Display button to get back to edit mode. 
 
15. Take a look at the online tags. Repeat Steps 1 – 14 but this time for Step 5 we will browse for 
the ONLINE tag. This time for step 5 collapse the Offline folder and expand the online folder. 
16. Before we close the display, try the numeric input object enhancement out. 
17. Single-click on the Test Display button from the tool menu. 
 
 
18. 0 should appear on the display. Type the number ‘-1’ in the field and select the enter key. 
19. Notice the field turns red 
and a message appears in the diagnostics list. 
 
20. Select the Esc key to cancel the changes and 0 will be displayed in the field again. 
21. Click the Edit Display button to get back to edit mode. 
 
22. Close the display and when prompted to save your changes select No. 
 
Section 1 is complete. You have the building blocks in place and are ready to start creating your 
graphic displays. 
 
3/10/2008 Page 42 of 160 
Section 2: Graphics and Animation (est. time 20 min) 
About This Section 
In this section of the lab you will learn about: 
ƒ Graphic Displays 
o Libraries 
o Adding existing HMI Components from the C:\LabFIles\ Lab 15 FactoryTalk View SE 
directory into your application 
ƒ Animation 
o Object Explorer 
o Tag Placeholders 
The Graphics Displays - Adding existing HMI Components into your application must be completed 
prior to doing any other sections in this lab. 
Graphic Displays 
A graphic display represents the operator’s view of plant activity. The display can show system or 
process data, and provide operators with a way to write values to external devices such as 
programmable controllers. The elements that make up a graphic display are called graphic objects. The 
Objects menu in the Graphic Displays editor (fig. 1) provides simple drawing elements such as line, 
rectangle and ellipse, as well as ready-made objects such as push buttons, input and display fields, and 
alarm summaries. Use these elements to create visual representations of processes and activities then 
animate the display by linking objects to tags so that the appearance of the objects will change as the 
values of the tags change. 
The graphics editor allows you to easily duplicate objects, reshape or resize objects, and arrange them 
in a variety of ways like stacking them, aligning them with each other, spacing them horizontally or 
vertically, flipping them horizontally or vertically, rotating them, and grouping them so they behave as a 
single object. Graphic objects can be 
ƒ Created using the Graphic Display editor. 
ƒ Copied and pasted from the Graphics Libraries. 
ƒ Copied to the clipboard from another Windows application and then pasted into the graphics 
display. 
ƒ Created by another Windows application and inserted into the graphic display using object 
linking and embedding. 
ƒ Dragged and dropped from another graphic display or library, or another Windows application. 
 
3/10/2008 Page 43 of 160 
Figure 1: Objects Menu 
Libraries 
The Graphics Library comes with a number of ready-made graphic displays containing objects that you 
can use in other displays 
 
There are many different library objects that you can use within your applications. 
Note: any animation that has been attached to an object will be included with it when it is copied into a 
display. 
Adding existing HMI Components 
There are preconfigured HMI components (i.e., Displays and macros) that will be used in this lab. Do 
the following to add them to the HMI Server. Almost all the graphics used in this lab came from the 
graphics library. 
1. Open the C:\LabFiles\ Lab 15 FactoryTalk View SE folder. Select the Start > Lab 15 FactoryTalk 
View SE menu item. 
 
2. The folder will open. Move the folder so it is on top of FactoryTalk View Studio and you can still 
see the Explorer. 
3. Select all files but NOT the folders in the Lab 15 FactoryTalk View SE folder. 
 
3/10/2008 Page 44 of 160 
4. Drag and drop all the files over the AF07 HMI Server. The files will be added to the appropriate 
locations. 
 
Files ending in GFX are display files and will be added to the Displays folder. Files ending in MCR are 
macro files and will be added to the Macros folder located under the Logic and Control folder. Files 
ending in KEY are client key files and will be added to the Client Keys folder located under the Logic 
and Control folder. Files ending in MDF are Data Log Models and will be added in the Data Log Models 
folder under the Data Log folder. You can verify that all the files were added by expanding those 
folders. 
Animation 
Animation is the ability to add logic to a graphic object so that some characteristic of the object will 
change when a tag value changes. For example, an object can be made to fill (up, down, left, or right) 
or change color in relation to a tag value. 
Expression: An expression is a mathematical or logical equation that returns a value. It can contain tag 
names, constants and mathematical, relational, logical and/or bitwise operators. A single tag name is 
often used for simple expressions. 
In Figure 2, the animation dialog shows that expressions are used to animate objects. There is a tab for 
each type of animation. If there is a check mark in front of the animation type it means that the selected 
object is using that animation. If an animation type is not available for a selected object, the fields on 
that animation tab will be grayed out. In the example below, the Fill and Color animations are being 
used on the selected object. Selecting a new object while the Animation dialog is opened will update 
the Animation dialog for the object that was just selected. 
2. Move folder over 
top of FactoryTalk 
View Studio
3. Select all files but 
not the folders 
4. Drag and drop 
over AF07 
 
3/10/2008 Page 45 of 160 
 
Figure 2: Animation Dialog 
 
The Object Explorer 
The Object Explorer provides a list of all the objects in the current graphic display, including those that 
are hidden by other objects. A group of objects has a plus sign in front of its name. Click this to expand 
the list of objects that make up the group. You can expand or collapse the whole list using the Expand 
and Collapse buttons. 
When you click an object in the display to select it, its corresponding entry in the Object Explorer is 
highlighted in gray. 
When you click an item in the Object Explorer, the object it corresponds to is selected. If an object is 
hidden by another, or is part of a group, when you select it in the Object Explorer the handles outlining 
the selected object are visible. 
Let’s open up one of the displays and take a look at animation. 
To open the Object Explorer 
1. Open the TankOverview display. Expand theDisplays folder, double-click on the TankOverview 
display. 
 
3/10/2008 Page 46 of 160 
2. The TankOverview display will be opened. 
 
3. Select the View > Object Explorer menu item 
Or 
Select the Show/Hide Object Explorer button from the menu bar to show or hide it. 
 
Once selected (indicated by a check next to the menu item name), the Object Explorer appears. 
The Object Explorer can be resized and moved. You can click on any of the objects listed, and you 
will notice that the objects will be highlighted in the display. 
 
3/10/2008 Page 47 of 160 
 
The Object Explorer is truly useful when you group items together and want to reference individual 
elements within that group. 
Grouping is useful when you have common objects that you want to move around or apply 
behaviors toward, for example, animation behavior. 
Look at groups and animation by using the object explorer 
1. Expand and Select the Agitator_Group in the Object Explorer. 
Highlighted 
Agitator_Group 
 
3/10/2008 Page 48 of 160 
2. Right-click on the Agitator_Group and select the Animation > Touch context menu item. 
 
3. The Animation dialog will appear and open on the Touch tab. 
4. Position windows so you can see both the Object and Animation window. 
5. In the Object Explorer, use the mouse or arrow keys to navigate down to item 
Agitator_Motor_Group, notice the Touch tab has a check next to it to indicate that Touch 
animation is being used and there is an expression for the release action of the 
Agitator_Motor_Group. This expression will open the Logix_D2SD faceplate that we added into 
our project for the 2 state device called Tank101 Agitator. The display will be positioned at the x and 
y coordinates specified. 
 
 
3/10/2008 Page 49 of 160 
 
The Display command was built using the Command Wizard. The Command Wizard is invoked 
by clicking any of the … buttons next to the actions. You will use the Command Wizard in the 
Global Objects section of this lab to build a Display command. Here is what the Command 
Wizard looked like when building this Display command for the Release action 
Display Logix_D2SD /T::[SoftLogix]Program:Tank101.Agitator /x 275 /y150 
 
 
If you want, you can delete the Release action and recreate it with the Command Wizard. 
 
3/10/2008 Page 50 of 160 
 
Tag Placeholders can be used to mark where you want to insert a tag name at run time. A tag 
placeholder is a cross-hatch character (#) followed by a number from 1 to 500. Tag placeholders let 
you create one display that you can use to represent a number of similar operations. At run time 
you supply the tag names associated with the particular operation and these are used in place of 
the tag placeholders. You can also use the Tag Substitution menu option to replace tag 
placeholders. 
 
To provide tag names at run time do one of these: 
 
- List the tag names in a parameter file in the order they are to be used and reference that 
parameter file in a command string for the Display command. The /P parameter for the Display 
command allows a relative or absolute reference to a parameter file that contains tag names to be 
substituted into the display. 
 
- List the tag names in the command string for the Display command. The /T parameter for the 
Display command allows for a list of tags (separated by commas) to be substituted into the display. 
 
6. Use the mouse or arrow keys to navigate down to item TankCoolingTemp_Group, notice the 
Touch tab has a check next to it to indicate that Touch animation is being used and there is an 
expression for the release action of the TankCoolingTemp_Group. There are actually 2 
commands that will be executed by this expression. 
Display Logix_PIDE /T::[SoftLogix]Program:Tank101.ProductTempLoop, 
::[SoftLogix]Program:Tank101.ProductTempAtune /X10 /Y20; 
 
Display Logix_PIDE /T::[SoftLogix]Program:Tank101.JacketTempLoop, 
::[SoftLogix]Program:Tank101.JacketTempAtune /X250 /Y20 
We have configured touch animation to launch the faceplate display twice, but with the ability to 
show the same faceplate display with different data using parameter passing. The faceplate 
displays will also be placed in different positions do they don’t overlay each other. 
The first display command will open the Logix_PIDE display and anywhere that parameter #1 is 
used, it will be replaced with ::[SoftLogix]Program:Tank101.ProductTempLoop and parameter 
#2 will be replaced with ::[SoftLogix]Program:Tank101.ProductTempAtune 
The second display command will open the Logix_PIDE display and anywhere that parameter #1 
is used, it will be replaced with ::[SoftLogix]Program:Tank101.JacketTempLoop and parameter 
#2 will be replaced with ::[SoftLogix]Program:Tank101.JacketTempAtune 
7. Continue navigating through the Object explorer and look at various animations. Some objects may 
have multiple animations defined. For example look at Tank101_AlarmIndicator_Polygon. It has 
both Touch and Color animation. Click the tabs to look at those animation properties. 
Let’s see the animation and parameter passing at work. We are going to test run this display in View 
Studio. 
 
3/10/2008 Page 51 of 160 
Section 3: Testing Displays (est. time 15 minutes) 
About This Section 
In this section of the lab you will: 
ƒ Test Run Displays in the FactoryTalk View Studio Graphics Editor 
ƒ Configure a FactoryTalk View Client File called AF07 
ƒ Observe Startup Macro 
ƒ Observe Client Keys 
ƒ Run the FactoryTalk View Client File called AF07 
o Explore Docked Displays at Runtime 
o Verify Client Keys work at Runtime 
o Test navigation at runtime 
The Configure a FactoryTalk View Client File called AF07 and Run the FactoryTalk View Client File 
must be completed prior to doing any other sections in this lab. 
Test Display 
Being able to test your display within View Studio without having to run it in a Client is a very powerful 
feature of FactoryTalk View. 
Behavior when test running a display might not always be identical to run-time behavior if changes 
made during development are not saved. To make the behavior as close as possible you should save a 
display before testing it. 
The Microsoft VBA IDE (Visual Basic for Applications Integrated Design Environment) lets you write, 
edit, test run, and debug code. 
Not everything can be done by test running your display. Some FactoryTalk View commands are 
ignored when run in test display mode. For example, screen navigation commands, using parameter 
placeholders in a display, and using parameter values in a reference global object will not function in 
test display mode. To test these features, run the display in a FactoryTalk View SE Client. 
Testing a graphic display in FactoryTalk View Studio is not the same as running the display in the 
FactoryTalk View SE Client. Before you deploy an application, it is recommended that you test it in the 
FactoryTalk View SE Client, to verify that everything works as intended. 
 FactoryTalk Alarms and Events Objects 
The existing (legacy) HMI Tag Alarm Summary object will not be animated when you run a display in 
test display mode. The FactoryTalk Alarms and Events Objects will work in test display mode. 
In Section 1, Verify Communications, the Test Display was used for both a FactoryTalk Alarm and 
Event and a native FactoryTalk View object. 
You can test the objects in a graphic display quickly, by switching to test display mode in the Graphics 
editor. Let’s try this to animate the TankOverview display. 
 
3/10/2008 Page 52 of 160 
1. The TankOverview display should be opened and have focus in FactoryTalk View Studio. 
2. From the FactoryTalk View Studio toolbar click on the Test Display button. 
 
3. Observe that the TankOverviewgraphic begins to animate. Click on the agitator 
 and then click on the valve 
 
What happened? Nothing. Look at the Diagnostics List. The Display command for the touch 
animation on the agitator and the valve was issued but the command is ignored in FactoryTalk View 
Studio. 
 
 
 
4. Click the Edit Display button to get back to edit mode. 
 
 
Now you will need to configure a client file and run the client to finish testing the display. 
Configure Client File 
Before you configure the client file, look at a few of the components that were preconfigured for you to 
use with your client. 
A macro is a list of commands or command symbols stored in a text file. To run a macro you use its 
name just as you would a command. The commands in the macro will be executed in the order in which 
they are listed. 
A macro can be specified on startup or shutdown of a client or display. It can be called from a 
command line in FactoryTalk View Studio or from the Factory Talk View Administration Console for 
system administration. 
 
3/10/2008 Page 53 of 160 
 
FactoryTalk View has multi-tasking capabilities that you can take advantage of when you create 
macros. Generally, the commands in a macro are executed in the order in which they are listed, with 
one command finishing before the next begins execution. 
Some commands (such as Print) finish quickly and the next command can start. Others, such as Set, 
take longer. In the case of Set, it does not finish until the message has been sent to the controller. In 
cases like that, you can set up the macro so that the next command can be executed before the 
previous command is finished. Use the ampersand character (&) to do this. 
To invoke the command wizard from the macro file, double-click in the macro, or select Edit – 
Commands… (Ctrl- M). 
Observe Pre-configured Macro 
These commands will dock displays at the top and bottom of the client window, and set tag values in 
the controller. 
1. From the Explorer, expand the Macros folder. 
 
2. Double-click on the ClientStartup macro. The ClientStartup macro will be opened. 
 
 
This macro will open a header display in a docked area on the top of the client. It will open a footer 
display in a docked area on the bottom of the client. Some tag values will be set to 1. 
3. Close the ClientStartup macro. If prompted to save changes, select the No button. 
Sometimes it is useful to have a single key stroke perform a function or multiple functions in your 
application. For example when you press F5 in Internet Explorer you will refresh the page. FactoryTalk 
View SE has similar functionality. 
 
3/10/2008 Page 54 of 160 
Client Keys allow the operator to interact with the system at run time to do things like change displays 
or set tag values. Client keys are defined for an application. They are enabled whenever the application 
is running on a FactoryTalk View SE Client. 
There are also object and display keys. Object and display keys are defined in the Graphics editor. 
They are active only when their associated object or display is. However, object and display keys take 
precedence over client keys. 
The order of precedence for key animation is: object keys, display keys and client keys. This means, for 
example, that if a key has 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. 
Observe Pre-Configured Client Keys 
These commands will perform a refresh of your client. This is useful for testing since you may need to 
make changes to displays and you don’t want to have to close and open the client each time you add or 
change something on a display. 
1. From the Explorer, expand the Client Keys folder. 
 
2. Double-click on ClientKeys. The ClientKeys dialog will open. 
 
 
 
3/10/2008 Page 55 of 160 
On the release action of function key 5, all displays including docked displays will be closed. The 
header display will then be re-opened and docked at the top and the footer display will be docked at 
the bottom of the client. 
3. Close the ClientKeys. If prompted to save changes, select the No button. 
Configure Client File 
The FactoryTalk View Client can be launched from FactoryTalk View Studio. 
1. Select the SE Client button on the tool menu. 
 
2. When the Launch FactoryTalk View SE Client dialog opens select the New… button. 
The FactoryTalk View SE Client Wizard will open. 
3. Click the New… button. 
4. Type ‘AF07’ for the name of the configuration file and click the Next button. 
 
5. Select the Local radio button and click the Next button. 
 and 
Type ‘AF07’ 
Select Local 
 
3/10/2008 Page 56 of 160 
6. Select the AF07 application, leave the defaults, and click the Next button. 
 
7. Select the TankOverview display as the initial display, select the ClientKeys key file as the 
Initial client key file, select the ClientStartup macro as the Startup macro, and click the Next 
button. Note: If you used parameters in the initial display, they would be specified in the Display 
parameters field. If you use a network application, the area would need to be specified for the initial 
display. 
 
Select TankOverview 
Select ClientKeys 
Select ClientStartup 
Select AF07 
 
3/10/2008 Page 57 of 160 
8. Type ‘AF07’ for the title bar text, check the maximize window option, and click the Next button. 
 
9. Leave the defaults for auto logout and click the Next button. 
and 
10. Leave the default to save configuration and open FactoryTalk View SE Client now and click the 
Finish button. 
 and 
The FactoryTalk View Client will start with the specified configuration. 
Check this 
Maximize Option 
Type ’AF07’ 
 
3/10/2008 Page 58 of 160 
Run Client 
The AF07 application is now running in a FactoryTalk View SE Client window. The startup macro 
docked displays in 2 areas. The header display contains an alarm banner and is located at the top of 
the client window; the footer display contains navigation buttons and is located at the bottom of the 
client window. 
 Docked Displays 
At run time, graphic displays can be docked to an edge of the FactoryTalk View SE Client window, 
allowing an operator to gain access to certain displays at all times. Docked displays cannot be 
accidentally closed by the operator and cannot have other graphics placed on top. They will, therefore, 
always remain visible to the operator. 
For example, you might consider docking: 
ƒ Navigational menus, that allow the operator to move among displays in an application. 
ƒ Headers or banners, that provide specific information to the operator, such as the current user’s 
name and area, or information about alarms. 
ƒ Control panels, that contain standard buttons for special purposes, such as changing users, closing 
open windows, or sending information to a maintenance team. 
Explore Docked Displays 
1. Minimize the Tank Overview display. 
2. Drag the minimized title bar around to the edges of the display client: 
Top edge: Bottom edge: 
3. Click the restore button on the Tank Overview display. 
4. Observe that it will not overlay the docked areas. 
5. Drag the Tank Overview display to the lower edge or lower right corner of the client. 
 
 
3/10/2008 Page 59 of 160 
6. Observe that it will not overlay the docked areas and scroll bars will appear so the display will still 
be visible. 
7. Move the Tank Overview display so the close button is visible and close the display. 
 
8. Select the Tank Overview button on the footer display to open the Tank Overview display. Notice 
how it is sized to fitin the main viewable area of the docked displays. 
Verify Client Keys 
1. Go back to FactoryTalk View Studio 
 
2. Open the Footer display. 
3. Select the Remove Me! Button and then select the delete key. 
4. Save the footer display 
5. Close the footer display 
6. Go back to AF07 client. 
7. Select the F5 key (defined to close all displays and re-display the header and footer). 
8. Observe that all displays are closed (including Tank Overview). The header and footer display are 
re-docked and the footer display no longer has the button called Remove ME!. 
 
3/10/2008 Page 60 of 160 
Test Navigation at Runtime 
1. Select the Tank Overview button on the footer display to open the Tank Overview display. 
 
 
Navigation from the footer display worked using a button object. 
2. Click the temp Dec C text . Notice that 2 displays are opened. The 
Logix_PIDE display was actually used with 3 different parameters. 
3. Observe that the Tank Overview begins to animate. Click on the agitator 
 and then click on the valve 
What happened? The faceplate for the 2 State Device and Enhanced PIDE opened. Navigation 
worked using touch animation. 
4. Click on the buttons in the faceplates. 
5. Click the Close Displays button in the lower right corner of the footer 
display. 
Remember that these navigation commands did not function when test running the display in 
FactoryTalk View Studio. 
 
3/10/2008 Page 61 of 160 
Section 4: Tags (est. time 5 minutes) 
In this section, you will learn about: 
ƒ Tags 
ƒ Direct referencing of device tags 
ƒ Indirect referencing and HMI Tags 
ƒ FactoryTalk Tag Browser 
ƒ Derived Tags 
Tags 
A tag is a logical name for a variable in a device or in local memory. For example, a tag can represent a 
process variable in a network device. 
Indirect Referencing or HMI Tags 
Tags defined within FactoryTalk View are referred to as HMI tags; in addition to the tag’s value, they 
provide additional properties for alarms, security, and data manipulation. 
1. From the Explorer, double-click on Tags located under the HMI Tags folder. 
 
2. This is where you can create, maintain, and remove HMI Tags. 
3. Close the Tags Editor. 
Direct Referencing 
FactoryTalk View also supports direct referencing of values directly from a device such as a 
ControlLogix controller without creating a corresponding entry in the HMI tag database, eliminating tag 
duplication and tag management. Direct referencing of device tags is a defining feature of Rockwell 
Automation Integrated Architecture. Tags added to the controller are available immediately without 
adding the tag to the HMI database, eliminating tag management. An application can use a mix of HMI 
tags and device tags. 
FactoryTalk Tag Browser 
FactoryTalk View has a FactoryTalk tag browser that allows you to access device tags while 
configuring an application rather than typing the tag name. You can browse while online and connected 
to a device, or you can browse for tags from an offline file, for example, a controller program file. The 
Tag Browser shows the root folder of the application and folders containing the tags for the 
application’s HMI and data servers. For a network application, the Tag Browser also shows a folder for 
each area, in addition to the root folder. 
 
3/10/2008 Page 62 of 160 
 
All tag names from all OPC 2.0 servers in the application will be available from the FactoryTalk 
directory. This information is served in a hierarchical fashion, organized by areas. So, in this example 
you see the areas (Plant Area 1, Plant Area 2…). Within those areas, you can see the topic names 
provided by the OPC servers, the online/offline control program, and the tags within them. You would 
choose the tag name you want to use right from the FactoryTalk tag browser. 
An advantage of FactoryTalk is that it provides an aggregate view of all tags from any data server. This 
includes traditional HMI tags that are available through the tag browser that browses the FactoryTalk 
directory. So, any RSLinx, OPC, or traditional HMI tags can all be browsed within the same tag 
browser. Contrast this to a traditional system, where OPC servers can only be browsed individually, or 
where an HMI tag database shows a flat list (non hierarchical) of all the tags in the system. The tags in 
the directory can return references to ControlLogix tags, PLC tags (5/500), FactoryTalk View tags, and 
third-party OPC server tags without the need to download or import the tags with an intermediary step. 
 Structured Tag Support in FactoryTalk Tag Browser 
The tag browser has been enhanced to let you select a structure tag in the left-hand pane of the object 
browser and return a partial tag identifier to the editor that launched the browser. This structure tag can 
be assigned to a faceplate object to supply values to multiple objects. 
In Section 1, Verify Communications, the FactoryTalk Tag Browser was used to verify access to offline 
and online tags when we added tags to a numeric input control. In Section 9 Global Objects - Create 
multiple reference objects in a display, and view the display, you will browse for a structured tag of type 
PIDE and PIDE_Autotune. 
 
Tags within selected 
folders appear on right.
Areas found in 
FactoryTalk Directory
 
3/10/2008 Page 63 of 160 
Derived Tags 
A derived tag is an analog, digital, or string tag whose value is determined through the evaluation of an 
expression. An expression can be simply a tag name or it can be an equation made up of tag names, 
mathematical and logical operations, special functions and If-Then-Else logic. The current value of a 
derived tag is written to the tag’s data source. 
A derived tag file consists of a number of derived tags and a maximum update rate for them. At runtime 
you can have multiple derived tag files active at once (up to 20 derived tag files, each containing up to 
1000 derived tags). 
Writing directly to a derived tag is highly discouraged because the tag value is determined by a given 
expression. If a derived tag is written to, the write value is merely overwritten as soon as the defined 
expression is evaluated again. 
1. From the Explorer, double-click on Derived Tags located under the Logic and Control folder. 
 
2. This is where you can create, maintain, and remove your Derived Tags. 
3. Close the Derived Tag Editor. 
 
 
 
3/10/2008 Page 64 of 160 
Section 5: Alarming (30 – 40 minutes) 
About This Section 
In this section, you will learn about: 
ƒ Types of Alarming Systems 
o FactoryTalk View SE Alarming (HMI tag alarm system) 
o FactoryTalk Alarms and Events (centralized alarm monitoring) 
o HMI Tag Alarm System Configuration 
o FactoryTalk Alarms and Events Configuration 
ƒ FactoryTalk Alarms and Events Objects 
o Alarm Banner – design and runtime behavior 
o Alarm Summary – design and runtime behavior 
o Alarm Log Viewer – design and runtime behavior 
o Alarm Status Explorer – design and runtime behavior 
o Expressions 
ƒ Device-Based Alarms 
ƒ Tag-Based Alarms 
Alarming 
Alarms are an important part of plant control applications because they alert operators when something 
goes wrong. Often, it is also important to have a record of alarms and whether they were 
acknowledged. 
FactoryTalk View SE supports the existing traditional HMI tag alarm system and the FactoryTalk 
Alarms and Events system. The choices you make will depend on factors such as the design of your 
application, the processes you need to monitor for alarms, the types of devices used in the application, 
and whether you want to build alarm detection into those devices. 
Traditional HMI Tag Alarm System 
In FactoryTalk View Studio, you can set up a complete alarm system.At run time, alarm monitoring 
occurs at the HMI server. If alarms are detected – tag values outside the configured limits - notification 
is sent to connected FactoryTalk View SE clients, where operators can view and acknowledge the 
alarms. This is a traditional HMI tag alarm system. 
An HMI tag alarm system only detects alarms set up for tags in an HMI server’s tag database. HMI tag 
alarm detection does not include FactoryTalk alarms. Use a traditional HMI tag alarm system if your 
application uses HMI tags for other purposes, and you want to monitor these tags for alarms. 
FactoryTalk View SE Clients receive HMI tag alarm information by way of the FactoryTalk View SE 
Servers (also called HMI servers) that contain the HMI tags. 
HMI tag alarm data is not managed by FactoryTalk Alarms and Events services. To monitor and 
respond to HMI tag alarms, you must use the HMI tag alarm displays and logs available in FactoryTalk 
View SE. 
 
3/10/2008 Page 65 of 160 
FactoryTalk Alarms and Events System 
The FactoryTalk Alarms and Events Services centralize the distribution of device-based and tag-based 
alarm data to run-time clients, through FactoryTalk alarm servers that you add to a FactoryTalk View 
SE application. 
ƒ device-based alarms, set up by programming alarm detection instructions directly into Logix5000 
controllers. FactoryTalk View SE Clients receive device-based alarms by way of Rockwell 
Automation Device Servers (RSLinx Enterprise) that you add to a FactoryTalk View SE application. 
ƒ tag-based alarms, set up to specify alarm conditions for tags in older programmable controllers 
(PLC-5 or SLC 500), in third-party devices communicating through OPC data servers, or in an HMI 
server’s tag database (HMI tags). FactoryTalk View SE Clients receive tag-based alarms by way of 
FactoryTalk Tag Alarm and Event Servers that you add to a FactoryTalk View SE application. 
 FactoryTalk Alarms and Events 
ƒ Provides a single, integrated set of alarm information. All participating FactoryTalk products work 
together to provide a consistent way to define, manage, log, and view alarm and event information 
across a FactoryTalk application. 
ƒ Streamlines alarm programming and eliminates polling with device-based alarm monitoring. If your 
automation system includes Logix5000 controllers, you can use pre-built alarm instructions, 
available in RSLogix 5000 v. 16 or later, to simplify coding, and then download to the controller. 
Device-based alarm monitoring eliminates the need for duplicating alarm tags in an HMI server and 
requires fewer controller communication resources by eliminating polling. 
ƒ Allows other controllers to participate in the integrated system with tag-based alarm monitoring. If 
your automation system includes older controllers, such as PLC-5s or SLC 500s, or if you prefer not 
to use the new alarm instructions with Logix5000 controllers, software-based tag servers monitor 
controllers for alarm conditions and publish event information. 
ƒ Allows monitoring alarms and events from third-party controllers. Tag-based alarm monitoring also 
makes it possible to monitor alarm conditions from third-party controllers, which communicate 
through OPC-DA servers. 
ƒ Provides accurate time stamps on alarm conditions that are generated from Logix5000 controllers 
using device-based alarm monitoring. With device-based alarm monitoring, time stamps are applied 
immediately in the controller and are not delayed until alarms reach an HMI server. To ensure 
accurate time stamps on device-based alarms, synchronize the clocks of all controllers that produce 
alarms. The event time is propagated throughout the FactoryTalk Alarms and Events system, so 
inaccurate time stamps can affect where alarms are displayed in the Alarm and Event Summary or 
the Alarm and Event Banner as well as reports about the alarm and event history. The Logix5000 
Clock Update Tool which is included with RSLogix 5000 can be used to accomplish this 
synchronization. 
ƒ Sends process data with events and messages. You can associate up to four tags with each alarm 
to include process data with event information and alarm messages. 
ƒ Secures access to alarm and event operations through integration with FactoryTalk Security. 
ƒ Generates messages for logging, including audit messages that track operator actions, system-
related diagnostic messages, and historical alarm and event messages. 
ƒ Displays alarm messages and status information during run time, from FactoryTalk View graphic 
displays. 
 
3/10/2008 Page 66 of 160 
Configuration 
FactoryTalk Administration Console, FactoryTalk View Administration Console, and FactoryTalk View 
Studio support configuration of the alarming systems. Both the FactoryTalk Administration Console and 
FactoryTalk View Administration console have limitations on what can be configured. Neither of these 
consoles will allow you to create, configure, and test HMI Displays. 
FactoryTalk View SE supports the existing HMI tag alarm system and the FactoryTalk Alarms and 
Events system. Configuration for both of these alarming systems is fully supported from within 
FactoryTalk View Studio. 
 
The comparison chart on the next page shows which alarming tasks can be performed from within each 
user interface. 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3/10/2008 Page 67 of 160 
 
FactoryTalk 
Administration 
Console 
FactoryTalk 
View 
Administration 
Console 
FactoryTalk 
View 
Studio 
FactoryTalk Alarms and Events 
Create and configure application, area, and data server 
elements in a FactoryTalk Directory. 
Yes Yes Yes 
Create and configure alarm and event servers, including 
both tag-based and device-based servers. 
Yes Yes Yes 
Configure alarm conditions for tag-based alarm detection. Yes Yes Yes 
Import and export for tag-based alarms. Yes Yes Yes 
Create database definitions for logging historical alarm 
and event messages. 
Yes Yes Yes 
Organize securable actions into groups. Yes Yes Yes 
View and manage alarm states (e.g., suppress, 
unsuppress, disable, and enable). Note: This is done by 
running the Alarm Status Explorer in Test Display mode. 
No No Yes 
Create and configure displays with alarm objects 
(Banner, Summary, Log Viewer, Status Explorer). 
No No Yes 
Test displays with alarm objects. No No Yes 
HMI Tag Alarm System 
Configure the alarm setup (e.g., maximum update rate, 
whether an alarm will be generated when tag value is 
approaching normal range, and how printing and logging 
are handled with redundancy enabled). 
No Yes Yes 
Configure the alarm log set up. No Yes Yes 
Import and export for HMI alarm tags. No Yes Yes 
Configure alarm tags and conditions for the alarms. No No Yes 
Suppress, unsuppress, and view suppressed alarms. No Yes Yes 
View alarm logs. No Yes Yes 
Create and configure displays with Tag Alarm Summary 
object. 
No No Yes 
Test displays with Tag Alarm Summary object (Note: this 
can only be done in FactoryTalk View Client). 
No No No 
 
3/10/2008 Page 68 of 160 
HMI Tag Alarm System Configuration 
The FactoryTalk View Studio objects for the HMI Tag Alarm System are located here: 
ƒ HMI Alarm Tags are created using the HMI Tag Editor or using the Tag Import Export Wizard. The 
HMI Tag Editor is invoked from the Explorer by double-clicking on the Tags icon under the HMI 
Tags Folder. 
 
 
ƒ The HMI Tag Alarm Summary object can be added to a display by selecting the Objects > 
Advanced > HMI Tag Alarm Summary menu item. 
 
or by selecting the HMI Tag Alarm Summary button on the tool menu 
 
 
ƒ Library objects are located in HMI Tag Alarm Information library display 
 
ƒ HMITag Alarm Log Setup, HMI Tag Alarm Log Viewer, and Tag Import and Export Wizard are 
located under the Tools menu: 
 
 
3/10/2008 Page 69 of 160 
FactoryTalk Alarms and Events Configuration 
The FactoryTalk View Studio objects for the FactoryTalk Alarms and Events System are located here: 
ƒ Device-based alarms are configured in the control program and enabled in the Rockwell 
Automation Device Server (RSLinx Enterprise). This was done in Section 1 – Add a data server. 
ƒ Tag Alarm and Event Server can be added to the application by right-clicking on the application 
and selecting the Add New Server > Tag Alarm and Event Server… context menu item. 
 
 
Tag based alarms can be created and configured with the Alarm and Event Setup Editor by 
double-clicking on the Alarm and Event Setup icon under the Alarm and Event Tag Server in 
the Explorer. 
 
 
 or tag based alarms can be imported and exported by right-clicking on the Tag Alarm and Event 
Server and selecting the Import and Export context menu item. 
 
ƒ Banner, Summary, Log Viewer, and Status Explorer are located under Objects > Alarm and 
Event > Banner, Summary, Log Viewer, and Status Explorer 
 
 
or by selecting the button for the object on the Tool menu 
 
ƒ Library objects are located in the Alarm and Event library display 
 
3/10/2008 Page 70 of 160 
FactoryTalk Alarm and Event Objects 
Preconfigured displays have been added to your HMI project for all of the FactoryTalk Alarm and Event 
objects. In Section 1 – Verify Communications, you added a summary object on a display and 
performed a test display to verify that you were getting alarms. In this section, you will observe all of the 
FactoryTalk Alarm and Event objects in design and runtime. You should have FactoryTalk View Studio 
and Client opened. 
Alarm and Event Banner (Header display) 
Use the Alarm and Event Banner object, embedded in a FactoryTalk View graphic display, to monitor 
and respond to the most serious alarms requiring immediate attention. 
Run Time 
1. From the AF07 client, observe the header display that contains the Banner object. 
2. Select a row in the Banner and click on the run alarm command button or double-click 
on a row in the Banner. 
Note: If the button is gray there is not a FactoryTalk View command associated with that 
alarm or the row is not selected. Select a row and try it again. 
3. A display should be launched for that alarm. 
4. Close the displays. 
5. Click on the Display the Alarm and Event Summary button. 
6. An Alarm Summary should be displayed. 
Design Time 
7. From the Explorer, double-click on the Header display to open it. 
8. Double-click on the Alarm and Event Banner Design View object in the display 
 
 
3/10/2008 Page 71 of 160 
and the Alarm and Event Banner Properties will open. 
 
 
9. Click on each tab to look at all the properties. A couple of things to point out here: 
General 
ƒ The Run Alarm Command will be invoked when the operator double-clicks on an alarm in the 
Banner 
ƒ The Alarm Summary button is configured to open the AlarmSummary display 
ƒ Button sizes and text fonts can be configured 
Columns 
ƒ Hide and show columns 
 
3/10/2008 Page 72 of 160 
ƒ Resize columns 
ƒ Reorder columns 
Status Bar 
ƒ Hide and show panes 
ƒ Reorder panes 
Event Subscriptions 
ƒ This Banner object will subscribe to all events with any priority 
States 
ƒ Configure text and background colors for the alarm states and priorities 
ƒ Normal and unacknowledged alarms will not appear in the banner. 
10. Feel free to make configuration changes and perform a Test Display or save your changes and 
use the F5 key in the Client to refresh the header display. 
11. Close the Header display in FactoryTalk View Studio when you are done. 
Alarm and Event Summary (AlarmSummary and TankAlarmSummary displays) 
Use the Alarm and Event Summary object, embedded in a FactoryTalk View graphic display, to 
acknowledge, disable, suppress, filter, and sort alarms during run time. 
Run Time 
1. From the AF07 client, click the Summary button in the footer display. 
2. The Alarm Summary display is opened. 
3. Select a row in the summary list to see details about the alarm. 
4. Mouse over the toolbar on the Summary to see what the configured buttons do (read the tool tips). 
5. Select a predefined filter called Pump or Tank101 from the drop down list 
 
6. Observe that the list and count are updated in the Summary. 
7. Click the Tank101 Summary button in the footer display. 
8. Notice that only alarms for Tank 101 are displayed and there is no way to modify the filter at 
runtime. 
 
3/10/2008 Page 73 of 160 
9. If you don’t see any alarms in the Tank101 Summary, Click the Tank Overview button in the footer 
display. Enter ‘100’ in the input field next to the Manual Valve Opening Slider object. 
 
10. Click the Tank101 Summary button in the footer display. You should now see alarms. 
Design Time 
11. From the Explorer, double-click on the AlarmSummary display to open it. 
12. Double-click on the Alarm and Event Summary Design View object in the display and the Alarm 
and Event Summary Properties will open. 
13. Click on each tab to look at all the properties. A couple of things to point out here: 
Appearance 
ƒ The Run Alarm Command will be invoked when the operator double-clicks on an alarm in the 
Banner 
ƒ The Alarm Summary button is configured to open the AlarmSummary display 
ƒ Button sizes and text fonts can be configured 
Columns 
ƒ Hide and show columns 
ƒ Resize columns 
ƒ Reorder columns 
Toolbar and Status Bar 
ƒ Hide and show buttons/panes 
ƒ Reorder buttons/panes 
Event Subscriptions 
ƒ This Summary object will subscribe to all events with any priority 
Display Filters 
ƒ This Summary object has preconfigured filters. These filters were preconfigured using the Alarm 
Class field that was configured for the alarm. 
Sort 
ƒ Configure sort order 
 
3/10/2008 Page 74 of 160 
States 
ƒ Configure text and background colors for the alarm states and priorities 
Behavior 
ƒ The Run Alarm Command will be invoked when the operator double-clicks on an alarm in the 
Summary 
12. Close the property page. 
13. Open the TankAlarmSummary display 
14. Double-click on the Alarm and Event Summary Design View object in the display and the Alarm 
and Event Summary Properties will open. 
15. Click the Event Subscriptions tab. 
16. Observe that this Summary object is only subscribing to alarms where the event source begins with 
[SoftLogix]Program:Tank101. Even if the filters option is enabled at runtime only the alarms 
beginning with [SoftLogix]Program:Tank101 can be filtered. 
17. Go to the Filters property page. Observe that the default filter is set so that Normal and 
Unacknowledged alarms do not appear in the TankAlarmSummary. 
18. Close the property page. 
19. Close the TankAlarmSummary display. 
20. Feel free to make configuration changes to the AlarmSummary display and perform a Test 
Display or save your changes and use the button on the footer display to open the display again to 
see your changes. 
21. Close the AlarmSummary display in FactoryTalk View Studio when you are done. 
Alarm and Event Log Viewer (AlarmLogViewer) 
Use the Alarm and Event Log Viewer object, embedded in a FactoryTalk View graphic display, to view 
and filter historical alarm information stored in Microsoft SQL Server databases. 
Run Time 
1. From the AF07 client, click the Log Viewer button in the footer display. 
2. The AlarmLogViewer display is opened. 
3. Select a row in the list to see details about the alarm. 
4. Mouseover the toolbar on the Log Viewer to see what the configured buttons do. 
5. Select a predefined filter called Pump or Tank101 from the drop down list 
6. Observe that the list and count are updated in the Log Viewer. 
 
3/10/2008 Page 75 of 160 
Design Time 
1. From the Explorer, double-click on the AlarmLogViewer display to open it. 
2. Double-click on the Alarm and Event Log Viewer Design View object in the display 
and the Alarm and Event Log Viewer Properties will open. 
3. Click on each tab to look at all the properties. A couple of things to point out here: 
General 
ƒ The log must be selected 
ƒ Text fonts can be configured 
Columns 
ƒ Hide and show columns 
ƒ Resize columns 
ƒ Reorder columns 
Toolbar 
ƒ Hide and show buttons 
ƒ Reorder buttons 
Display Filters 
ƒ This Log Viewer object has preconfigured filters. These filters were preconfigured using the 
Alarm Class field that was configured for the alarm. 
Notice that there is not an Event Subscription tab. This is a historical view of what is in the log 
(database). 
4. Feel free to make configuration changes and perform a Test Display or save your changes and 
use the button on the footer display to open the display again to see your changes. 
5. Close the AlarmLogViewer display in FactoryTalk View Studio when you are done. 
Alarm Status Explorer (AlarmStatusExplorer) 
Use the Alarm Status Explorer object, embedded in a FactoryTalk View graphic display, to enable or 
disable alarms and suppress or unsuppress alarms. 
Run Time 
1. From the AF07 client, click the Status Explorer button in the footer display. 
2. The AlarmStatusExplorer display is opened. 
3. Mouse over the toolbar on the Status Explorer to see what the configured buttons do. 
4. Select a row in the list and select the show details for selected alarm button from the toolbar. 
 
3/10/2008 Page 76 of 160 
5. Select a couple of rows and then click the suppress button. 
6. Click on a column header to see the list sort by that column. 
7. Click the suppress column until the suppressed alarms appear at the top of the list. 
8. Select all the suppressed alarms and then click the unsuppress button. 
9. Type ‘*tank101*’ in the name field for the Alarm source filter and click the Apply Filter button. 
 
10. Observe the list is filtered to show only alarms that contain tank101. 
11. Click the Cancel Filter button 
12. Observe the list shows all alarms. 
Design Time 
1. From the Explorer, double-click on the AlarmStatusExplorer display to open it. 
2. Double-click on the Alarm Status Explorer object in the display. Nothing happens. You must right-
click on the object and then select the Properties… context menu item. 
 
3/10/2008 Page 77 of 160 
Now, the Alarm Status Explorer Properties will open. 
 
3. Feel free to make configuration changes and perform a Test Display. 
4. Close the AlarmStatusExplorer display in FactoryTalk View Studio when you are done. 
FactoryTalk Alarm and Event Expressions 
There are new FactoryTalk View SE expressions that interact with the FactoryTalk Alarms and Events 
Services. 
This FactoryTalk Alarm and Event function returns this value: 
AE_HighSeverityAcked(AlarmName) - highest severity of acknowledged alarms 
AE_HighSeverityUnacked(AlarmName) - highest severity of unacknowledged alarms 
AE_InAlmAckedCount(AlarmName) - number of In Alarm and Acknowledged alarms 
AE_InAlmUnackedCount(AlarmName) - number of In Alarm and Unacknowledged alarms 
AE_NormalUnackedCount(AlarmName) - number of Normal and Unacknowledged alarms 
Run Time 
 
3/10/2008 Page 78 of 160 
1. From the AF07 client, click the TankOverview button in the footer display. 
2. The TankOverview display is opened. 
3. Observe the alarm indicators 
 
4. The alarm indicators should be changing colors. If they are not, slide the Manual Valve Opening 
up to about 90 and then wait a few seconds. Slide it back down to about 20 and then wait. This 
should trigger some alarms. The alarm indicators should change colors. 
Design Time 
1. From the Explorer, double-click on the TankOverview display to open it. 
2. Open the Object Explorer by selecting the View – Object Explorer item from the menu, 
3. Expand the Indicator_Group in the Object Explorer. 
 
3/10/2008 Page 79 of 160 
4. Right-click on the Tank101AlarmIndicator_Polygon from the Object Explorer, select the 
Animation – Color context menu item. 
 
5. Observe the expression in the color animation 
 
This expression will change the color of the polygon to red if there are any active alarms where the 
alarm names starting with SoftLogix]Program:Tank101 (i.e., all my tank101 alarms.) It does not 
matter whether alarms are acknowledge or unacknowledged. 
 
3/10/2008 Page 80 of 160 
 
Device-Based Alarms 
Logix controllers will serve alarm information to FactoryTalk Alarms and Events Services with 
FactoryTalk View SE 5.0. Two new alarm instructions have been added to the Logix Controllers. These 
new instructions are available in the ladder logic, function block, and structured text programming 
languages. 
Digital Alarm (ALMD) 
A digital alarm is configured to monitor its input for one of the following alarm conditions: 
o The input value equal to one 
o The input value equal to zero 
When the alarm condition is true, the alarm enters the In Alarm state. When the alarm condition is 
false, the alarm enters the Normal or Out of Alarm State. 
Analog Alarm (ALMA) 
An analog alarm can be configured to monitor for two types of alarm conditions: Level and Rate of 
Change. 
A Level alarm monitors an input for alarm conditions that go In Alarm when the input value goes above 
or below predefined limits. When defining a level alarm, you can configure up to four alarm level 
conditions each with limits (sometimes called thresholds), a severity and alarm message. The 
supported alarm conditions are: 
o High High (HIHI) 
o High (HI) 
o Low (LO) 
o Low Low (LOLO) 
A Rate of Change alarm monitors an input for alarm conditions that go In Alarm when the input value 
changes faster or slower than predefined limits. When defining a level alarm, you can configure up to 
two rate of change conditions each with limits, a severity, and an alarm message. The supported alarm 
conditions are: 
o Rate of Change Positive (ROC_POS) 
o Rate of Change Negative (ROC_NEG) 
Configuration Options 
Let’s look at some of the configuration options and how they are related to the HMI. You can make any 
change to an alarm instruction while the controller is running. The changes take effect immediately and 
are displayed in the FactoryTalk Alarms and Events objects the next time the alarm changes state. 
 
3/10/2008 Page 81 of 160 
Severity 
The severity value can range from 1 to 1000, to indicate different levels of importance. Alarm severities 
are integer values, where 1 is the least severe, and 1000 is the most severe. For example, a level 
alarm may be configured with the HI level condition using a severity of 750 to warn that a vat is 80 
percent full of liquid while the HIHI level condition could use a severity of 900 to indicate that the vat is 
about to overflow. 
Because 1000 different alarm severities can be cumbersome to work with, ranges of alarm severities 
are mapped to one of four (Low, Medium, High, Urgent) alarm priorities by the FactoryTalk Alarms and 
Events system. 
Minimum Duration 
The Minimum Duration specifies the minimum amount of time that the alarm condition must be true (the 
Input=1 in this case) before the alarm condition goes In Alarm. This setting is used to minimize false 
alarms. 
Associated Tags 
In many cases it is useful tohave additional process information associated with an alarm. When an 
alarm is defined, you can associate up to four tags with the alarm. At run time, the tag values are 
recorded in the Alarm and Event History Log and can also be displayed in the Alarm and Event 
Summary or Alarm and Event Log Viewer, and embedded in alarm messages. The contents of the 
Alarm and Event Log Viewer can be filtered based on the value of an associated tag. 
Alarm Class 
To help group alarms, you might want to classify alarms that relate to each other in ways that do not 
include severity or priority. For example, you might want to group together alarms by function, such as 
those that monitor for valves that fail to open or close, pressure, temperature, equipment running, or 
tank levels. The alarm class is a text string of up to 40 characters that you enter when configuring an 
alarm. 
At run time, the value of the alarm class is recorded in the Alarm and Event History Log and can also 
be displayed in the Alarm and Event Summary or Alarm and Event Log Viewer. The contents of the 
Alarm and Event Summary or Alarm and Event Log Viewer can also be filtered based on the value of 
the alarm class. 
FactoryTalk View Command 
You can associate a FactoryTalk View command of up to 1000 characters with any alarm. The 
command is executed from the Alarm and Event Summary or Alarm and Event Banner when the 
operator selects an alarm and then clicks a button. The Summary and Banner can also be configured to 
execute the command when the operator double-clicks the alarm in the list. A common use for the 
FactoryTalk View command is to display a screen that shows an overview of the equipment related to 
the alarm. 
 
3/10/2008 Page 82 of 160 
Observe Configured Alarms in Logix 5000 
If you would like to take a look at the alarms that have been configured for this lab, do the following. 
Open RSLogix 5000 
1. Select the AF07_SE_Lab shortcut from the Start menu 
 
OR 
Click the Logix 5000 Alarms button on the footer menu of the AF07 client 
 
After clicking the button, the FactoryTalk View command to open RSLogix 5000 will appear in the 
diagnostic list. 
It will take a few seconds for RSLogix 5000 to start and open to the routine. If the Quick Start page 
appears, close or hide it. 
2. Go online with the controller by selecting the Communications > Go Online menu item. 
 
3. If the Connected To Go Online dialog appears, select the Upload button. 
4. Navigate to the Tank101 routine if you are not already there (double click to open). 
 
 
 
3/10/2008 Page 83 of 160 
View Digital Alarm 
1. At the bottom of the Cascade Temperature Loop worksheet you should see the ALMD 
instructions. Click on the … next to the ALMD to open the property pages. 
 
2. Observe the Configuration properties for the ALMD instruction 
 
3. Close the dialog when you are done. 
View Digital Alarm 
1. Change to sheet 2 of 3. 
 
 
3/10/2008 Page 84 of 160 
2. At the bottom right of the Level Simulation worksheet you should see an ALMA instruction. Click 
on the … next to the ALMA to open the property pages. 
 
3. Observe the Configuration and Messages property pages for the ALMA instruction 
 
3/10/2008 Page 85 of 160 
 
 
4. Close the dialog when you are done. 
Tag-Based Alarms 
FactoryTalk tag-based alarms are set up by specifying alarm conditions for tags in devices that do not 
have built-in alarm detection. Use tag-based alarms to include these devices in an integrated 
FactoryTalk Alarms and Events system. 
You can set up tag-based alarms for tags in older programmable controllers (PLC-5 or SLC 500), for 
tags in third-party devices communicating through OPC data servers, or for HMI tags in an HMI server’s 
tag database. 
You can also set up tag-based alarms for Logix5000 controllers that do support device-based alarms, if 
you prefer not to set up built-in alarm detection. FactoryTalk View SE Clients receive tag-based alarm 
data by way of Tag Alarm and Event Servers that you add to a FactoryTalk View SE application. 
You will create tag-based alarms in Section 10 - tag-based alarm language switching. 
 
 
3/10/2008 Page 86 of 160 
Section 6: Security (est. time 20 – 30 min) 
About This Section 
In this section, you will learn about: 
ƒ Security 
ƒ Creating a User and User Group 
ƒ Configuring Action Security 
ƒ Configuring Runtime Security - Assigning security codes (A - P) 
o Users and User Groups 
o Commands 
o Display Settings 
ƒ Verifying Security Settings 
About Security 
For FactoryTalk products like FactoryTalk View SE, the FactoryTalk Directory stores information about 
which users are allowed access to the parts of a control system. 
FactoryTalk Security uses this information to provide two basic services: 
ƒ User authentication verifies the user’s identity, and whether a request for service actually 
originated with that user. 
ƒ User authorization verifies the user’s request to access a software resource, based on the 
access rights and privileges defined for that user. 
For example, when a FactoryTalk View SE network application user logs on to FactoryTalk View 
Studio, FactoryTalk Security services verify the user’s identity first. 
If authentication succeeds, security services check permissions assigned to the user, to authorize 
actions performed on secured parts of the application. 
In a network application, security services also check whether the user is allowed to perform authorized 
actions on the current computer. 
In addition, FactoryTalk Security services manage system-wide policies, such as how often users must 
change their passwords, or whether users can back up and restore applications. 
The security system is extremely powerful. Some particular considerations: 
ƒ You can enforce “line-of-sight” security by restricting operators to specific computers that are 
within visual range of the machine or process. 
ƒ Inheritance allows you to define basic levels of access for a broad set of users, across a 
FactoryTalk-enabled system. You can then refine security settings for selected users as 
necessary, by overriding inherited permissions on lower-level resources. 
 
3/10/2008 Page 87 of 160 
ƒ In a FactoryTalk View Site Edition application, an HMI server always inherits the permissions 
assigned to the area in which it resides. You cannot set up access to an HMI server separately. 
ƒ You can explicitly deny rights to certain users from all computers or from specific computers. 
Selecting the Deny check box for an action denies permission explicitly. This always takes 
precedence over allowing permission. 
ƒ If a user belongs to two different groups, and one group is allowed to delete applications but the 
other group is denied that permission explicitly, then the user will not be allowed to delete 
applications. 
 Security 
Following installation of the FactoryTalk View SE software, the All Users account is automatically added 
to the Runtime Security list and allowed all run-time security codes. This gives any FactoryTalk View 
SE Client user permission to run a client, open displays, write to tags, and execute commands and 
macros. 
In a secured FactoryTalk system, you must remove the All Users account, add users to the Runtime 
Security list, and then give the users the security permissions needed to run an application. 
After the FactoryTalk View SE software is installed, all users have full initial access to network and local 
applications on the computer. 
There is no need to log on, to run FactoryTalk View Studio, the FactoryTalk View SE Administration 
Console, or a FactoryTalk View SE Client. The current Windows user is automatically logged on to 
FactoryTalk View SE. 
However,you do need to log on and off to change users, or to gain access to secured parts of the 
FactoryTalk system. 
FactoryTalk View Runtime Security 
FactoryTalk View Runtime Security manages run-time security for HMI project components, including 
FactoryTalk View commands and macros, graphic displays, OLE objects, and HMI tags. In FactoryTalk 
View Studio, you can secure access to HMI project components by assigning security codes (A - P) to 
users and user groups (in the Runtime Security editor); to commands and macros (in the Runtime 
Secured Commands editor), to graphic displays and OLE object animation (in the Graphics editor), and 
to HMI tags (in the Tags editor). 
Before you can assign FactoryTalk View security codes to users and user groups, you have to create 
the user and user group accounts in FactoryTalk Security, and then add them to the Runtime Security 
editor. 
Creating a User and User Group 
When setting up security for a FactoryTalk View 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 similar security needs. Rather than assigning 
permissions to each user in the system, you can create accounts for new users, and then add the users 
the appropriate groups. 
You are going to create a new user and user group. You will assign the user to a user group. You will 
do this from FactoryTalk view Studio. 
 
3/10/2008 Page 88 of 160 
1. From the Explorer, expand the Users and Groups folder. 
2. Right-click on the User Group folder, select the New > User Group… context menu item. 
 
3. The New User Group dialog will be opened. 
4. Type ‘Operators’ in the Name field 
 
5. Click the button 
6. The Select User or Group dialog will open, Click the Show users only radio button and click 
Create New > User… menu item. 
 
 
3/10/2008 Page 89 of 160 
7. The New User dialog will open. Type ‘Tank101Operator’ for the user name, check the user 
cannot change password, check the password never expires, and type ‘password’ for the 
password. 
 
Confirm the fields. Click the Create button. 
8. You will be back at the Select User or Group dialog. 
Select the Tank101Operator and click the button. 
9. You will be back at the New User Group dialog. Tank101Operator should be in the Members list: 
 
10. Click the Create button. 
11. Operators will appear under User Groups in the Explorer. 
 
Type ‘Tank101Operator ‘ 
Select User cannot 
change password
Select Password never expires 
Type ‘password’ 
Type ‘password’ 
Click the Create button 
 
3/10/2008 Page 90 of 160 
 
Configuring Action Security 
When setting up security, you can specify which actions a user or group can perform on the resources 
in your system while working from a particular computer or group of computers. In a FactoryTalk Local 
Directory, actions can only be performed from the local computer — the FactoryTalk Local Directory 
does not contain any computer accounts. 
Action 
An organized activity performed on a resource in order to accomplish an objective. Actions are grouped 
into categories. In addition to a set of common actions that apply to most FactoryTalk products, each 
product can also include its own set of actions. For information about those actions, see Help for the 
FactoryTalk product. 
 
Resources 
The objects in a FactoryTalk system for which actions can be secured. Each FactoryTalk product 
defines its own set of resources. For example, some products might allow you to configure security for 
resources such as servers in an area. Other products might allow you to configure security for logic 
controllers and other devices. FactoryTalk Administration Console allows you to configure security for 
the System folder and its contents, applications, areas, and many other items. Do not confuse 
resources with resource groupings: resource groupings allow you to group together control hardware 
represented in the Networks and Devices tree, and then configure security for the grouping in one step. 
Let’s specify that our operators can not perform certain alarming actions. 
1. From the Explorer, right-click on AF07 and select the Security… context menu item 
 
2. Security Settings for AF07 dialog appears. Click the Add… button. 
3. The Select User or Group dialog appears. Select the Operators and click the OK button. 
4. While the Operators group is selected, expand the Alarming action, Check the Deny check box 
next to Alarming and check the Allow checkbox next to Acknowledge. 
 
You are only allowing the operators to acknowledge FactoryTalk Alarm and Events Alarms. They 
can not perform the other actions. 
 
3/10/2008 Page 91 of 160 
Your dialog should look like this. 
 
5. Click the OK button. When prompted with this message, 
 
select the Yes button. 
6. The Security Settings for AF07 dialog closes. 
 
3/10/2008 Page 92 of 160 
Configuring Runtime Security 
After you have created users and user groups in FactoryTalk Security, you add them to the security 
accounts list in the Runtime Security editor in FactoryTalk View SE. When you add an account, you 
also assign the security codes that will give them access to secured HMI components. (Secured HMI 
components are those that have been assigned security codes.) 
These codes (A through P), along with those assigned to HMI project components, determine which 
components a user has access to at run time. 
To restrict access to a command, macro, graphic display, OLE object verb, or HMI tag, you assign a 
security code from A through P to it, and then assign that code only to the users who are supposed to 
have access to the component. 
Assign Security Codes to Users and User Groups 
1. Double-click on the Runtime Security icon in the Explorer 
 
 
Or 
 
Select the Settings > Runtime Security…. menu item. 
 
2. The Runtime Security dialog is opened. 
3. Click on the Security Accounts… button. 
4. The Security Settings for AF07 dialog is opened. 
5. Select the Add… button. 
6. The Select User and Group dialog is opened. 
7. Select the Operators and click the OK button. 
8. The Select User and Group dialog is closed and the Operators group is added to the Users list. 
While it is highlighted, expand the FactoryTalk View Security Codes actions. Select the Deny 
checkbox for A. 
 
3/10/2008 Page 93 of 160 
Your settings should look like this. 
 
9. Click the OK button. 
10. When prompted 
Select the Yes button. 
11. Select the Close button on the Runtime Security dialog 
12. When prompted with the message “Save changes to document?” Select the Yes button. 
13. The Runtime Security dialog closes. 
 
 
3/10/2008 Page 94 of 160 
Assign Security Codes to Commands 
1. Select the Settings > Runtime Secured Commands… menu item. 
 
2. The Runtime Secured Commands dialog is opened. Expand the window to see all the fields. 
3. Click in a cell in row 2 to select it. 
 
4. Click the … button next to the Command field. 
 
5. The Command Wizard is opened. 
 
6. Observe all the commands that can be assigned security codes. 
7. Click the Cancel button on the Command Wizard. 
8. Observe the Security Code drop down list that can be used to assign a security code to a 
command. 
9. Click the Close button on the Runtime Secured Commands dialog. 
10. When prompted with the message “Save changes to document?” select the No button. 
11. The Runtime Secured Commands dialog will close. 
Assign Security Codes to Displays 
You will assign the A security code to the AlarmStatusExplorer display. 
1. Open the AlarmStatusExplorerdisplay from the Explorer. 
 
3/10/2008 Page 95 of 160 
2. Select the Edit > Display Settings… menu item. 
3. The Display Settings dialog will open. 
4. Select the A from the Security Code drop down list. 
 
5. Click the OK button. 
6. Save the display. 
 
7. Close the display. 
Verifying Security Settings 
In this section you will verify your security settings with the client. You will login in as the 
tank101operator and then try to suppress an alarm. First you will try to suppress it from the Alarm 
Status Explorer display, then from the Tank101 Summary display, and then finally you will try to 
suppress it from the Summary display. Your attempts should fail because of the security settings. Let’s 
see what happens. 
1. Go to the AF07 client 
 
2. Click the button on the footer display. 
3. Login as the new user ‘Tank101Operator’ using the password of ‘password’. Note user name is 
not case sensitive. 
 
4. The information message “User tank101operator has been logged in.” will appear in the 
diagnostics list. 
 
3/10/2008 Page 96 of 160 
5. Click on the button. 
6. What happened? Nothing! The message “Currently logged-in user does not have security 
access to AlarmStatusExplorer.” will appear in the diagnostics list. The display setting security 
worked! 
7. Click on the button in the footer display. 
8. The Tank101 Summary is displayed. 
9. Observe there isn’t an icon for the Alarm Status Explorer 
in the toolbar. The Tank101 Summary display was configured for operators and actions that should 
not be performed by operators were hidden from the toolbar. So the operator can not get to the 
Alarm Status Explorer from here. 
Notice the suppress button 
is not displayed in the toolbar. The operator can not suppress the alarms from here. 
 
So far so good! It is looking pretty secure here. 
10. Click in the button in the footer display. 
11. The Alarm Summary is displayed. But what do you see? There is a suppress and an Alarm Status 
Explorer button. This display didn’t hide the buttons from the operator or secure the display from the 
operator. 
Note: If you don’t see these buttons you may have changed your configuration in the Alarming 
section. 
12. Select a row (alarm) in the summary list and click on the suppress button. 
13. When the Suppress Alarm dialog comes up, click the suppress button to confirm that you want to 
suppress the alarm. 
14. What happened? There is a message right? The message should read something like “Failed to 
Suppress Alarm alarm [alarm name] Tank101Operator does not have Suppress/Unsuppress 
permission. The message will appear in the diagnostics list. If the option to display errors from 
operator action in a dialog was checked when configuring the summary (which it was originally), a 
dialog with the message will appear. If the message dialog appears, click the OK button. 
 
The actions security worked! 
 
3/10/2008 Page 97 of 160 
15. Click on the Alarm Status Explorer button. 
16. What happened? The Alarm Status Explorer dialog opened. This is because it is not the same as 
the display that we configured a security code on. 
17. Select an alarm in the list and then click on each of the first 4 buttons (enable alarm, disable 
alarm, suppress alarm, unsuppress alarm) to try to perform these actions. Observe what happens. 
The actions are secured and the operator can not perform them. So even though the operator was 
able to access the Alarm Status Explorer from the Summary display because maybe the HMI 
Designer forgot to hide the button, he still could not perform actions that he didn’t have permissions 
for. 
18. Close the Alarm Status Explorer 
19. Right-click on an alarm in the summary and select one of the Ack context menu items. 
 
20. The alarm will be acknowledged because the tank101operator has permission to perform that 
action. 
21. Click the button on the footer display. 
22. Login as administrator using the password of rockwell 
23. Perform some of the steps above. You should be able to open the Alarm Status Explorer from the 
footer display and perform all actions on the alarms. 
 
3/10/2008 Page 98 of 160 
Section 7: Data Logging and Trending (est. time 20 
min) 
About This Section 
In this section, you will learn about: 
ƒ Runtime Exploration 
ƒ Data Logging 
ƒ Trending 
ƒ Configuration Exploration 
ƒ Historical Trending 
ƒ Runtime Trending 
ƒ Data Log Models 
ƒ Querying logged data 
ƒ Create your own trend 
You will be using the TankDataLogging display and Tank101 data log model that you added in Section 
2 – Adding existing HMI Components. 
Runtime Exploration 
Data Logging 
Data logging is a FactoryTalk View component that collects and stores tag values. You specify which 
tag values to collect, when to collect them, and where to store them by defining a data log model. 
The HMI tag database does not store actual tag values; it only defines which values are to be collected. 
The values themselves are stored on a given HMI server. When the HMI server is turned off, the value 
table is cleared (excluding retentive tags). To have a permanent record of tag values, log them to the 
data log file on disk. Remember: controller tags will keep their value when an HMI server is powered 
down because they’re located within the controller; they’re not HMI (or memory) tags stored on the 
server itself. 
To log tag values to disk, you create a data log model and specify the tags that are to be logged. This is 
done in the Data Log Model editor. The values can also be logged to an ODBC-compliant database. 
An application can have up to 20 data log models running at a time. The maximum number of tags that 
can be logged by one data log model is 10,000. 
Trending 
A trend is a visual representation, or chart, of current or historical tag values. A trend provides 
operators with a way of tracking plant activity as it is happening. The trend object displays real-time 
data and historical data from the FactoryTalk View Site Edition data logs. Pens on the run-time chart 
represent data from the tags and expressions that you add to the trend object. The trend object 
provides extensive, flexible run-time control. You can add pens, toggle between isolated and non-
isolated graphing, specify unique line settings, plot one variable against another in XY plots, and print 
chart data. 
 
3/10/2008 Page 99 of 160 
There are two different types of Trending 
- Historical Trending 
o Historical Trending is when a trend polls data from a data log that is previously 
configured. This will allow the user to browse through a timeline to look at the data over 
a given period of time. 
- Runtime trending 
o A Runtime trend displays data trends directly from the processor. The trend will start 
trending its runtime data from the time it’s first loaded on the display. 
Viewing a Trend 
1. Go to the AF07 client 
 
2. Click the Data Logging button from the footer display. 
3. The Tank 101 Data Logging Trend will be displayed. 
4. Click the Start button. 
5. Notice the messages that appear in the diagnostics list 
 
6. Look at the two error messages and an information message: 
 
There was an attempt to connect to an ODBC data source that failed, Tank101 is logging to a 
secondary path that is a file. You will take a look at why this happened in the configuration section. 
7. Notice the trend starts to update. 
8. Click the button in the footer display 
 
3/10/2008 Page 100 of 160 
9. Note the HMI Time in the header. 
10. Slide the Manual Valve Opening Slider to the top. Wait about 20 seconds. 
11. Slide the Manual Valve Opening Slider about half the way down. Wait about 20 seconds oruntil the Level is OK. 
12. Slide the Manual Valve Opening Slider to the bottom. Wait about 20 seconds. 
13. Slide the Manual Valve Opening Slider about half the way down. 
14. Click the Data Logging button from the footer display. 
15. Observe the trend. Find the HMI Time that you noted if it is not visible by using the buttons 
under the trend. 
The trend displayed is configured to display historical data. This means that the trend reads both 
Real-time data (occurring now) and Historical data (read from data log files). 
Configuration Exploration 
Data Log Models 
1. From the Explorer, navigate to AF07 > Data Log > Data Log Models > Tank101. 
 
2. Double-click on Tank101 
 
3/10/2008 Page 101 of 160 
3. The Tank101 Data Log Model dialog opens to the Setup tab. 
 
You can set up logging to log to a file set or to log to any database that you can connect to with 
ODBC. 
The data log model can be configured to be stored as a file set or an ODBC database. Notice that 
this data model is being stored in an ODBC database. There is a System Data Source Name (DSN) 
called FactoryTalk that points to a SQL Server Express database called FactoryTalk. 
An ODBC System DSN stores information about how to connect to the indicated data pointer. If you 
want to see how the System DSN was configured, Select the Start > Settings > Control Panel menu 
item. From the Control Panel, select Administrative Tools, and then select Data Sources (ODBC). 
Look at the System DSN tab and the DSN called FactoryTalk. 
There is a database and a pointer to the database but the tables to store the data have not been 
created. This was done to demonstrate what happens when the connection to the database fails 
and there is a backup path enabled. 
4. Click the Create Tables button if you haven’t already done so. You should get a FactoryTalk View 
Datalog Editor message saying ODBC tables were successfully created. Click the OK button. 
This is a pre-configured 
System DSN pointing to 
a database that is called 
FactoryTalk. 
Click the Create Tables 
button. 
 
3/10/2008 Page 102 of 160 
5. Click on the Paths tab. 
 
This configuration tab is used to set the file location of the data logs. This is useful if you have a 
distributed network set up; you will want to store the logs to one common location instead of on 
each individual HMI server on the network. 
Notice that he Enable ODBC backup path was selected and a logging path was specified. This is 
why you were able to see the historical data in the trend display even though the connection to the 
ODBC failed. 
The tables are created and the connection should be successful now. At some point you will see 
messages like 
 
Click the Advanced button, and notice the settings. SwitchBack is set to 10 minutes. 
6. Click the File Management tab 
This configuration tab is used to configure how long you want to keep logging to individual files until 
you either create a new file or delete older files. 
7. Click the Log Triggers tab 
This configuration tab is used to decide how often and based upon what event the log should be 
updated. 
Notice Enable ODBC 
Backup Path is enabled. 
 
3/10/2008 Page 103 of 160 
Notice that the trigger for logging is On Change. 
 
8. Click the Tags in Model tab 
This configuration tab is used to select what information is logged. You can add or remove different 
tags from this menu using the tag browser. 
9. Notice 6 tags have been added to the model. 
10. Click the OK button to close the Tank101 Data Log Model dialog 
Configuring Trends 
Do not add a new trend or change this one. You can do so at the end of this section. 
1. From the Explorer, double-click on the TankDataLogging display to open it. 
The Trend object can be created by selecting the Objects > Advanced > Trend menu item 
 
or by selecting the Trend button on the menu bar 
 
2. Double-click on the grid of the Trend object. 
3. The Trend Properties dialog will open. 
4. Click the Pens tab. 
Trigger is On Change 
Heartbeat of 2 minutes 
 
3/10/2008 Page 104 of 160 
5. Notice that the Model column has Tank101 which is the data model that was created. 
 
These pens were added by selecting the Add Pen(s) from Model button. The Configure Tags 
dialog opened. The Add All button was selected to add all the tags. Then the OK was clicked to 
accept the changes. 
6. Click the Cancel button on the Trend Properties dialog to close the dialog. 
7. Double-click on the Start button to open the button properties. 
8. Click the Action tab and look at the Release action. This command DataLogOn Tank101 starts 
the data logging for the model. 
 
9. Click the Cancel button to close the button properties. 
10. Double-click on the Stop button to open the button properties. 
11. Click the Action tab and look at the Release action. This command DataLogOff Tank101 stops 
the data logging for the model. 
 
12. Click the Cancel button to close the button properties. 
13. Close the TankDataLogging display. If prompted to save changes, select the No button. 
 
3/10/2008 Page 105 of 160 
Querying Logged Data 
A view was created in the database to allow you to query the data log. Do the following to view the data 
log. 
1. Open the C:\LabFIles\ Lab 15 FactoryTalk View SE folder if it isn’t already opened. Select the Start 
> Lab 15 FactoryTalk View SE menu item. 
 
2. Open the SQL folder. 
3. Double-click on the ViewTank101DataLog.sql file. 
 
4. Microsoft SQL Server Management Studio Express will open and you will be prompted with a 
Connect to Database Engine dialog. 
Click the Options >> button. 
Click the Connection Properties tab. 
Type ‘FactoryTalk’ in the Connect to database field. 
Click the Connect button. 
 
3. Type 
‘FactoryTalk’
4. Click the 
Connect button 
1. Expand Options 
2. Click Connections 
Properties Options 
 
3/10/2008 Page 106 of 160 
5. Once you are connected, click the Execute button. 
6. Results will appear in the window. 
7. Scroll to the bottom of the list and notice the number of rows. 
8. Click the Execute button. 
9. Scroll to the bottom of the list and notice the number of rows and the Data and Time. Did the row 
count change? Have we gotten any new rows? We are only logging on change. 
10. Go to the AF07 client 
 
11. Click the button in the footer display 
12. The Tank Overview will be displayed. 
13. Note the HMI Time in the header. 
14. Slide the Manual Valve Opening Slider to the top. Wait about 20 seconds. 
15. Slide the Manual Valve Opening Slider about half the way down. Wait about 20 seconds or 
until the Level is OK. 
16. Slide the Manual Valve Opening Slider to the bottom. Wait about 20 seconds. 
17. Slide the Manual Valve Opening Slider about half the way down. 
18. Go back to the Query window. 
19. Click the Execute button. 
20. Scroll to the bottom of the list and notice the number of rows. Did the row count change? Are we 
getting new rows? Yes, it should have. 
21. Go to the AF07 client 
22. Click the Data Logging button from the footer display. 
23. The Tank 101 Data Logging Trend will be displayed. 
 
3/10/2008 Page 107 of 160 
24. Click the Stop button. 
25. Notice the messages that appear in the diagnostics list 
 
26. Notice the trend is still being updated. 
27. Click the button in the footer display 
28. Note the HMI Time in the header. 
29. Slide the Manual Valve Opening Slider to the top. Wait about 20 seconds. 
30. Slide the Manual Valve Opening Slider about half the way down. Wait about 20 seconds or 
until the Level is OK. 
31. Slide the Manual Valve OpeningSlider to the bottom. Wait about 20 seconds. 
32. Slide the Manual Valve Opening Slider about half the way down. 
33. Go back to the Query window. 
34. Click the Execute button. 
35. Scroll to the bottom of the list and notice the number of rows. Did the row count change? What is 
the date and time of the last row? You should have not received any new records after you stopped 
the data logging. 
36. Close the Microsoft SQL Server Management Studio Express. If prompted to save changes, 
select the No button. 
 
 
 
3/10/2008 Page 108 of 160 
 Section 8: FactoryTalk Diagnostics Setup and the 
Viewer (est. time 20 min) 
About This Section 
In this section, you will learn about these topics: 
ƒ FactoryTalk Diagnostics 
ƒ Diagnostics List 
ƒ Diagnostics Viewer 
ƒ Diagnostics Setup 
o Configuring the FactoryTalk View Diagnostics List 
o Configuring the Local Log 
o ODBC Database as a message source 
About FactoryTalk Diagnostics 
The idea behind FactoryTalk Diagnostics is to answer the question, "Why did that happen?" 
FactoryTalk Diagnostics collects and provides access to a global store of time-and-date stamped 
messages that can help answer that question. 
The FactoryTalk Diagnostics service includes a Diagnostics Setup editor, a Diagnostics Viewer, and a 
Local Log on each computer where the FactoryTalk Services Platform is installed. Other custom 
logging destinations are also available. For example, the FactoryTalk AssetCentre software product 
provides customized FactoryTalk Audit Logs. 
Use the Diagnostics Setup editor to set up options for logging destinations and to filter the types of 
messages you want to log on the local computer. 
Use the Diagnostics Viewer to review diagnostics messages. You can view both local messages and 
messages retrieved and merged from logs on multiple computers. 
FactoryTalk View SE, FactoryTalk Alarms and Events, and other FactoryTalk software products are all 
sending messages to one Local Log and to one FactoryTalk Audit Log on one computer. When you set 
options for a particular logging destination, the options you choose affect the log on this computer that 
any number of FactoryTalk products may be using. Likewise, when you configure message routing 
options, the filtering options you choose affect the types of messages routed from all FactoryTalk 
products that send messages. 
Each FactoryTalk product and service categorizes the messages that it generates using a matrix of 
Severity options (Error, Warning, Information, and Audit) together with Audience options (Operator, 
Engineer, Developer, and Secure). For example, a product might generate a series of security 
messages classified as Operator-Audit and Operator-Information, and also generate a series of 
communication messages classified as Operator-Warning, Engineer-Warning, and Developer-Error. 
Diagnostics information can be displayed in the Diagnostics List or in the FactoryTalk Diagnostics 
Viewer. The Diagnostics List is intended to show messages as they occur. Messages displayed in the 
Diagnostics List are not time stamped. The Diagnostics Viewer provides a way to retrieve messages 
 
3/10/2008 Page 109 of 160 
after they occurred. New messages do not appear in the Diagnostics Viewer. A refresh can be done to 
reload the messages. Messages that appear in the Diagnostic Viewer are time stamped so you know 
when they occurred. 
Diagnostics List 
The Diagnostics List can be displayed in a FactoryTalk View Studio window, FactoryTalk View SE 
Client, and FactoryTalk View Administration Console window. You have used the FactoryTalk View 
Diagnostics List in earlier sections of this lab. You can clear messages from the Diagnostics List by 
selecting a row or multiple rows and clicking the Clear button or by clicking the Clear All button. 
Removing a message from the Diagnostics List does not delete the message from the Diagnostics log. 
Removing a message from one Diagnostics List does not remove it from another Diagnostics List. I.e., 
removing a message from the View Studio window does not remove it from the View Client window. 
When the application (View Studio, View Client, or View Administration Console) starts new messages 
begin to get logged to the list. Old messages will be removed from the list as new ones come in and the 
message limit has been reached. When the application is closed, the list is cleared. 
Diagnostics Viewer 
The FactoryTalk Diagnostics Viewer allows you to view both local messages and messages retrieved 
and merged from multiple products running on multiple computers logging to multiple destinations. 
Open the Diagnostics Viewer 
1. From Explorer, select the Tools > Diagnostics Viewer… menu item 
 
Or 
 
select the Start > Diagnostics Viewer menu item. 
2. The FactoryTalk Diagnostics Viewer will open. 
When the Diagnostics Viewer window is open, new messages do not appear automatically. To 
refresh the view and reload messages, press the F5 key or click the Refresh button. 
3. Mouse over the toolbar and look at the menus to see the operations you can perform with the 
Diagnostics Viewer. 
Filter Diagnostics List 
1. Select the View > Options… menu item. 
 
2. On the General tab of the Properties dialog, make sure message source is set to Local Log. 
 
 
 
3/10/2008 Page 110 of 160 
 
3. Click the tab on the Properties dialog. Move the Properties dialog so that you can see 
the items in the Diagnostic Viewer. 
 
 
4. Click on Apply from the Properties dialog. 
5. Observe the list was updated but no messages appear in the list. 
6. 
 
 
7. Click on Apply from the Properties dialog. 
8. Observer the list was updated to only show messages that were created with the audience set to 
operator. 
2. Click the Modify… button 
3. Select Equals 
4. Select Operator 
5. Select the 
OK button
1. Select the Audience = 
‘Developer’ 
2. Click the 
Add Where Condition…) button 
3. Select Equals 
4. Select Developer 
5. Select the 
OK button
1. Select the Audience 
 
3/10/2008 Page 111 of 160 
9. Select the Audience = ‘Operator’ select records where condition and click the Remove button. 
 
 
10. Create a message filter. 
 
11. Click on OK from the Properties dialog. 
12. Observe the list was updated to only show messages that contained the string tank101. 
13. Close the Diagnostics Viewer. 
Take a look at the diagnostics setup to see why you didn’t see any developer messages. 
 
Diagnostics Setup 
Open the Diagnostics Setup 
1. Run the Diagnostics Setup from within the FactoryTalk View Studio. From the Tools menu, select 
the Diagnostics Setup… menu item 
2. The FactoryTalk Diagnostics Configuration dialog will open 
2. Click the 
Add Where Condition…) button 
3. Select Contains 
4. Type ‘tank101’ 5. Select the 
OK button
1. Select the Message 
 
3/10/2008 Page 112 of 160 
3. Expand the Destination Setup 
 
4. Click on each item and look at the settings. 
Configuring the FactoryTalk View Diagnostics List 
Earlier in the lab you used the Diagnostics List in FactoryTalk View Studio and Client to look at 
diagnostic messages. Look at the Destination Setup and the Message Routing configuration to see 
what messages got routed to the FactoryTalk View Diagnostics List. 
1. Expand the Destination Setup, select the FT View Diagnostics List item. Notice that there aren’t 
any configuration settings. The destination is the Diagnostics List which is managed by 
FactoryTalk View. 
 
2. Select the Message Routing setup and then select the FT View Diagnostics List 
 
Messages that were intended for Operator and Engineer audience that were of type Error, Warning, 
and Info appeared in the FactoryTalk ViewDiagnostics List. 
Configuring the Local Log 
You just used the Diagnostics Viewer to look at the local log. Look at the configuration. 
 
 
3/10/2008 Page 113 of 160 
1. Select the Destination Setup > Local Log item 
 
The local log is a file that exists on this computer. There are options for overwriting events, log size, 
and an option to clear the log. 
2. Select the Message Routing setup and then select the Local Log 
 
Messages that were intended for Developer audience were not logged to the Local Log so that is why 
we did not see any. 
 
3/10/2008 Page 114 of 160 
3. Change the Message Routing for the Local Log to include all message types for the developer 
audience. Check all the options in the Developer row. 
 
4. Click the Apply button. 
5. Go to the AF07 client; click the clear all button in the Diagnostics List. 
6. Click on the Tank Overview button. 
7. Type ‘75’ in the Manual Valve Opening input field and select the enter key. 
8. Notice 2 messages in the diagnostics list got updated. 
 
9. Select the Start > Diagnostics Viewer menu item. 
10. Select the last 2 messages in the list to look at the details. Notice that they are developer 
messages one is of type audit and the other is of type information. 
 
ODBC Database as a Message Source 
Depending on the products you have installed and the configuration options you have set, FactoryTalk 
Diagnostics can also route these messages to other centralized logging destinations, such as an ODBC 
database or FactoryTalk Audit Log. 
Use the ODBC Database Destination Setup window to send messages to an ODBC data source. To 
send messages from multiple computers, configure the destination on each computer where the 
FactoryTalk Diagnostics service is installed. 
 
3/10/2008 Page 115 of 160 
The ODBC Database destination supports these ODBC-compliant databases: 
ƒ Microsoft SQL Server 
ƒ Microsoft Access 
ƒ Oracle 
ƒ Sybase SQL Server 
Some types of information cannot be logged to an ODBC database destination. This includes: 
ƒ any additional database fields not included in the ODBC table format, that a FactoryTalk product 
might use. Even if you create the additional fields manually, nothing will be logged to them. The 
additional information logged by a FactoryTalk product will, however, appear in the Local Log on 
the computer where the product is installed. 
ƒ any messages where the audience type is set to Secure, or the severity type set to Audit. 
Secure messages can only be logged by the FactoryTalk AssetCentre software product to the 
FactoryTalk Audit Log. 
Configure the ODBC Database Setup 
1. Go to the Diagnostics Configuration 
You are going to configure the destination setup. You will use a System DSN called FactoryTalk that 
has been configured to point to a MS SQL Server Express database called FactoryTalk. 
2. Select the Destination Setup > ODBC Database item. 
 
Browse 
 
3/10/2008 Page 116 of 160 
3. Click the … button next to the data source name. When the Select Data Source dialog opens, 
click the System Data Source tab. Click the FactoryTalk data source name. 
 
4. Click the OK button. 
5. Type ‘FTDiagnostics’ for the target table and click the Create Table button. 
 
6. Click the OK button when you get the message that “The table FTDiagnostics was successfully 
created.” 
Select the System 
Data Source tab
Select the 
FactoryTalk Data 
Source Name 
Type 
‘FTDiagnostics’ 
Click the Create 
table button 
 
3/10/2008 Page 117 of 160 
7. Change the Log message to database every setting to be 30 seconds. 
 
8. Select the Message Routing setup and then select the ODBC Database. Check all the options in 
the Developer row. 
 
Notice that Audit messages can not be routed to the ODBC destination. 
9. Click the OK button. 
View the ODBC Log 
10. Go to the Diagnostics Viewer 
11. Select the View > Options menu item. Move the Properties window so you can view the list. 
12. Click the ODBC Database as the message source. 
13. Click the OK button. 
14. Notice the list is empty because nothing has happened since we created this destination. 
15. Go to the AF07 client; click the clear all button in the Diagnostics List. 
16. Click on the Tank Overview button. 
17. Type ‘85’ in the Manual Valve Opening input field and select the enter key. 
18. Notice a download message is logged in the Diagnostics List. 
19. Go to the Diagnostics Viewer 
20. Wait 30 seconds, click the refresh button. 
 
3/10/2008 Page 118 of 160 
21. Notice that 2 messages got logged. 
 
22. If you queried the database, you would see it has been updated 
 
23. Close the Diagnostics Viewer window. 
 
 
3/10/2008 Page 119 of 160 
Section 9: Global Objects (est. time 30 min) 
About This Section 
In this section, you will learn about: 
ƒ Global Objects 
ƒ Create multiple reference objects in a display, and view the display 
ƒ Using Global Object Parameters 
ƒ Reference Object Properties 
ƒ Modifying a global object, and view the changes in a display 
ƒ Design recommendations for working with global objects 
Global Objects 
FactoryTalk View global objects allow you to link the appearance and behavior of one graphic object to 
multiple references of that object in the same application. 
Global objects are created on global object displays. In FactoryTalk View Studio, you create global 
object displays in the Global Objects folder, the same way you create standard graphic displays in the 
Displays folder. 
Changes you make to the base object are reflected in all of the reference objects linked to it the next 
time a display containing the reference objects are opened, or refreshed by closing and reopening 
them. 
 Global Object Parameters 
Global object parameters let you customize each reference global object instance with a specific tag(s) 
for that instance without having to break the link to the base object's tags and expressions. This means 
each reference object can have a unique data source(s), and still be able to be updated with changes 
to other aspects of the base global object. 
Parameter passing is dynamic, meaning it happens at runtime on the client. Global object parameters 
give you an alternative way of using parameter passing at design time. 
Create Multiple Reference Objects 
In Section 2 – Animation – Object Explorer of this lab, you saw that the TankOverview display had one 
touch animation on the TankCoolingTemp_Group that opened two Logix_PIDE display for different 
loops. The Logix_PIDE display contains reference objects to the Logix_PIDE base global object. 
In this section of the lab, you will create a new display and use the base Logix_PIDE global object to 
create two reference objects on that display. You will use the parameter values to specify which PIDE 
loops you want to view and animate. You will then change the touch animation in the Tank Overview 
display to call the new display and then run the client to test your work. 
 
3/10/2008 Page 120 of 160 
Create New Display 
1. From the Explorer, create a new display – Right-click on Displays, select the New context menu 
item. 
2. Open the Logix_PIDE global object - Expand the Global Objects folder in the Explorer, Double-
click on Logix_PIDE 
3. Create a reference object on your new display – Single-click on the global object to select the 
faceplate, drag and drop it on the new display. 
 
4. Minimize the Logix_PIDE global object. 
5. Position the reference object in the upper left corner of the new display. 
6. Duplicate the 1st reference object – Right-click on the reference object and select the Duplicate 
context menuitem OR perform a copy and paste. 
7. Position the 2nd reference object next to the first one. 
8. Resize the display so window edges line up with faceplate edges. 
 
3/10/2008 Page 121 of 160 
9. Open the Global Object Parameters dialog on the 1st reference object - Right-click on the 1st 
reference object and select the Global Object Parameter Values context menu item. 
 
 
The Global Object Parameter Values dialog is opened. 
 
Notice that there is a description for the #1 and #2 parameters. You will be looking for structured 
tags of type PIDE and the PIDE_Autotune. The PIDE_Autotune is not required. 
 
 
 
3/10/2008 Page 122 of 160 
10. Assign structured tags for #1 - Click on the … button under the Tag column for #1. 
When the Tab Browser opens navigate to ::[SoftLogix]Program:Tank101.ProductTempLoop 
 
Click the OK button 
11. Repeat the above step for #2 using ::[SoftLogix]Program:Tank101.ProductTempAtune 
 
Notice that this time when the tag browser is opened you are positioned at the tag you previously 
selected (::[SoftLogix]Program:Tank101.ProductTempLoop). This help you navigate more quickly. 
12. The #1 and #2 parameter values should be entered for the Tank101 - ProductTempLoop 
 
13. Click the OK button on the Global Object Parameter Values dialog. 
 
3/10/2008 Page 123 of 160 
14. Repeat the 5 previous steps, steps 9 – 13 for the 2nd reference object. Assign these structure tags 
#1 is assigned ::[SoftLogix]Program:Tank101.JacketTempLoop 
 
 
#2 is assigned ::[SoftLogix]Program:Tank101.JacketTempAtune 
 
15. Configure Display Settings with all the defaults except for these: 
Display Type use On Top 
type the text ‘Temp Loops for Tank101 Product’ for the Title Bar 
 
 
Notice the Insert Variable… button under the title bar text. 
 
3/10/2008 Page 124 of 160 
 
 Parameter Enhancements 
Added parameter enhancements that provide support for embedded variables in tooltips and title bars; 
literal numbers and strings in the embedded variable syntax; and display of right-most characters in 
embedded string variables. 
Feeling adventurous? Try using this to show the loop names in the title bar like the Logix_PIDE 
display. Remember there are 2 loops in your display. 
16. Save the Display 
17. When prompted for a component name type ‘Tank101TempLoops ‘ 
18. Perform a Test Display. What happens? Lots of failed to resolve messages. 
You can use the test display mode to test global objects. However, this global object uses parameter 
placeholders and even though we set the values they are ignored. Remember, not all FactoryTalk View 
commands work in test display mode and parameter placeholders are ignored. 
19. Close the Tank101TempLoops display. 
Now you will have to test the display in the client. But first you need to launch the display. 
 
3/10/2008 Page 125 of 160 
Change Touch Animation 
Let’s change the touch animation on the Tank Overview display to open the new one you created. 
1. Open the TankOverview display 
2. Open the Object Explorer 
3. Find the TankCoolingTemp_Group object in the Object Explorer and Open the Touch Animation 
Properties. 
 
4. Remove the release action and click on the … button to open the Command Wizard. 
 
5. Step 1 of Command Wizard, Select the Display command, click the Next button. 
 
3/10/2008 Page 126 of 160 
6. Step 2 of Command Wizard, Select the Tank101TempLoops display, check the /X and type ‘10’, 
check the /Y and type ‘20’ which is where the first display was opening. Click the Finish button. 
\ 
7. Verify the release action looks like this 
 
8. Click the Apply button on the Animation dialog. 
9. Click the Close button on the Animation dialog. 
10. Save and Close the display. 
We can’t test the touch animation here. Let’s go to the client. 
Test New Display 
1. Go to the AF07 Client 
2. Click the Close Displays button. 
3. Click the Tank Overview button. 
4. Mouse over the temperature and click for the touch animation. 
5. What happens? Your new display should be opened and you should see values and animations for 
both loops. 
 
3/10/2008 Page 127 of 160 
Global Object Parameter Definitions 
Global object parameters are defined in base objects in global object displays. When you copy a global 
object from a global object display onto a standard display from the Graphics folder, you can assign 
values to the global parameters in the resulting reference object. 
We just assigned the parameter values in reference objects in the previous section. Let’s look at how 
they get defined. 
1. From FactoryTalk View Studio, restore your Logix_PIDE Global Object if it is not opened then 
open it. 
2. Expand some of the groups in the Object Explorer. 
 
3. Right-click on the PIDE_Global_Group Notice that Global Object Parameter Definitions is 
enabled in the context menu. 
4. Right-click on the PIDE_Description_Group Notice that Global Object Parameter Definitions is 
not enabled on the context menu. 
 
3/10/2008 Page 128 of 160 
The placeholder parameters can be used in any object contained on the global object display but the 
Global Object Parameter Definitions are assigned at the top level group. 
5. Right-click on the PIDE_Global_Group and select the Global Object Parameter Definitions 
item in the context menu. 
The Global Object Parameter Definitions dialog is opened. Observe the name and definitions. This is 
what you saw when assigning values in the reference global object. 
 
6. Click the Cancel button to close the Global Object Parameter Definitions dialog. 
Reference Object Properties 
The reference object has a LinkBaseObject property that specifies the name and location of the base 
object the reference object is linked to. You cannot modify the LinkBaseObject property. If the specified 
global object display or base object does not exist, the reference object will appear in red outline, with a 
red cross on a white background. 
Once you have a reference object, you can not easily change the object name in the base object. You 
will get a warning message when attempting to rename a base object. If you accidentally perform a 
name change or delete a base object, it can be restored. To restore the reference object, you must 
recreate the base global object with the same name, on the same global object display in order to allow 
the reference objects to work again. 
 
A reference object has properties that link it to its base object. When a reference object is created, the 
global object defaults are used to set how the reference object will be linked to the base object. These 
properties can be modified after the object has been created. You can choose to break the link to the 
base object after the reference object is created. If you break the link the object will become a graphics 
object and will no longer reference the base object. 
The values of the Link properties determine whether aspects of the reference object’s appearance and 
behaviors are defined by the base object, or by the reference object itself. 
LinkAnimation 
The LinkAnimation property determines whether the reference object uses the animation set up for its 
base object. 
Set up the LinkAnimation property of the reference object by selecting: 
ƒ Link with expressions, to use the animation, including expressions, set up for the base object. 
ƒ Link without expressions, to use the animation, excluding expressions, set up for the base object. 
This means you can set up the expressions for the reference object separately. 
ƒ Do not link, to set up animation and expressions for the reference object separately. 
 
3/10/2008 Page 129 of 160 
For a Button push button object, theLinkAnimation property determines whether the reference object 
uses the press, release, or repeat actions set up for the base object. This is true when you select either 
Link with expressions or Link without expressions. 
 
LinkConnections 
The LinkConnections property determines whether the reference object uses the connections set up for 
its base object. 
Set up the LinkConnections property of the reference object by selecting: 
ƒ True, to use the connections assigned to the base object. 
ƒ False, to set up connections for the reference object separately. 
In FactoryTalk View Site Edition, a reference object that is a tag label, trend, or Button push button with 
an action other than Command, always uses the connections assigned to its base object. You cannot 
set up connections for these reference objects separately. 
 
LinkSize 
The LinkSize property determines whether the reference object uses the height and width set up for its 
base object. 
Set up the LinkSize property of the reference object by selecting: 
ƒ True, to use the height and width set up for the base object. 
ƒ False, to set up the height and width of the reference object separately. 
If you attempt to resize a reference object with its LinkSize property set to True, the object will snap 
back to its original size. 
 Look at the Global Object Defaults 
1. From Explorer, select the Edit > Global Object Defaults menu item. 
 
These are the default settings. 
 
3/10/2008 Page 130 of 160 
 Global Object Default Settings 
The Global Object Defaults are now set to Link with expressions for the LinkAnimation properties and 
true for the LinkConnections. These have changed because Global Object Parameters allow you to use 
placeholders in the connections and expressions. This means each reference object can have a unique 
data source(s), and still be able to be updated with changes to other aspects of the base global object. 
All the reference objects in this application have been created with these defaults. This means that any 
changes we make to the animation, connection, or size of the base object will be reflected in the 
reference object. 
2. Click the Cancel button to close the Global Object Defaults dialog. 
Look at the Reference Properties 
1. From Explorer, Open the Tank101TempLoops display that you created. 
2. Open the Object Explorer 
3. Right-click on an object in the Explorer, select the Property Panel item in the context menu 
or 
click the Show Property Panel button in the tool bar 
 
4. Click different objects in the Object Explorer and observe the properties. 
5. When you are done close the display. 
Modifying Global Objects 
What happens when you think you have your application all done and then you get a change request? 
The change could be adding a new item to a display or changing colors on an animation. Global objects 
allow you to make the change in the base object and the reference objects will inherit that change. This 
makes maintaining your application a lot easier. 
You will be modifying the Logix_PIDE Global Object. If you mess up, you can use the Add Process 
Faceplates dialog to add it back into the project and replace the one that you modified. 
Modify CV Text 
The operator is not familiar with the label CV (Control Variable) and is use to seeing OUT (Output) 
instead. You can change the text label in the base global object and the reference objects will reflect 
the change. 
1. From Explorer, open the Logix_PIDE Global Object 
2. Find the CVLabel_Text object in the Object Explorer. Double-click on CVLabel_Text to open 
the Text Properties dialog. 
 
3/10/2008 Page 131 of 160 
3. Select the text CV 
 
4. Type the text ‘OUT’ 
5. Click the Common tab 
6. Type the number ‘25’ for the width. 
7. Click the OK button. 
8. Save the global object. 
9. Go to the AF07 Client 
10. Click the Close Displays button. 
11. Click the Tank Overview button. 
12. Mouse over the temperature and click for the touch animation. 
13. Notice two reference objects have the change. 
 
3/10/2008 Page 132 of 160 
14. Click on the valve 
15. Notice the reference object has the change. 
So we made a change in 1 place, the base object and the 3 reference objects now reflect the change. 
The text label change would have been updated in all of the reference objects regardless of what the 
link properties were set to. 
This next one is a little trickier. If you want to give it a try continue on or you can skip it and go to the 
next section. 
Add engineering units as Parameter Definition 
Suppose you want to add engineering units to your faceplate. The engineering units (EU) could be 
different depending on the PIDE Loop you are looking at. So, you want to use a parameter placeholder 
for the EU. The Logix_PIDE Global Object already exists and is being referenced. Let’s see how we 
would make this change. 
1. From Explorer, open the Logix_PIDE Global Object 
2. You want to add a text object for the EU next to the PV value. Find the PVValue_Group and then 
select the PV_NumericDisplay in the Object Explorer. 
 
 
3/10/2008 Page 133 of 160 
3. Single-click on the Text object 
4. Move the mouse next to the PV_NumericDisplay object. Single-click, drag, and release. 
 
5. The Text Properties opens. Click the Insert Variables…String option. 
 
6. In the String Variables dialog, select the Literal string option, enter #3 for the literal, select the 
Fixed number of 6 characters, and the show * option. 
 
Note: Literal string variables do not support spaces. 
7. Click the OK button. 
8. Click the Common tab. 
 
3/10/2008 Page 134 of 160 
9. Type ‘EU_Text’ for the name, enter 16 for height, 43 for width, 292 for top, 112 for left position. 
 
10. Click the OK button. 
11. When prompted “Changing the name will break the links to any reference objects. Do you want to 
continue?” select the Yes button. 
It is OK to rename the object here because we just created it and do not have any references to it yet. 
12. Look in the Object Explorer and see if your new object was created under the group 
PV_ValueGroup. 
 
13. Right-click on the PIDE_Global_Group in the Object Explorer, select the Global Object 
Parameter Definitions context menu item. 
 
3/10/2008 Page 135 of 160 
14. Enter #3 for the Name and PV engineering units (literal string with no spaces) for the 
description. 
 
15. Click the OK button. 
16. Save and Close the Global Object. 
Verify engineering units are displayed 
1. Go to the AF07 Client 
2. Close all displays containing the Logix_PIDE reference objects 
or 
Click the Close Displays button. Click the Tank Overview button. 
3. Mouse over the temperature and click for the touch animation. 
4. Notice two reference objects have the change but #3 is showing. 
The parameter has to be passed to the reference objects. 
Pass the new #3 parameter value from reference object 
1. From Explorer, open the Tank101TempLoops. 
2. Right-click on the 1st reference object, select the Global Object Parameter Values context menu 
item. Enter ‘Deg-C’ for the #3 value. Click the OK button. 
3. Right-click on the 2nd reference object, select the Global Object Parameter Values context menu 
item. Enter ‘Deg-C’ for the #3 value. Click the OK button. 
4. Save and close the display. 
Verify engineering units are displayed (2nd try) 
1. Go to the AF07 Client 
2. Close all displays containing the Logix_PIDE reference objects 
or 
Click the Close Displays button. Click the Tank Overview button. 
3. Mouse over the temperature and click for the touch animation. 
 
3/10/2008 Page 136 of 160 
4. Notice two reference objectshave the parameter values being displayed. 
 
That takes care of one of the faceplates we know about but there are still references on the 
TankOverview display. Use Tag Substitution to find and modify the references or you can skip to the 
next section. 
 
3/10/2008 Page 137 of 160 
Search and Replace References on TankOverview 
1. From the Explorer, open the TankOverview display. 
2. When the TankOverview display is highlighted, select the Edit > Select All menu item. 
3. While all items are selected, select the Edit > Tag Substitution menu item. 
4. When the Tag Substitution dialog is opened, scroll through the Search for list and look for 
occurrences of Display Logix_PIDE 
 
5. When you find it, 
Display Logix_PIDE 
/T::[SoftLogix]Program:Tank101.LevelController,::[SoftLogix]Program:Tank101.LevelAtune /x875 
/y125 
click to select it, and then copy it into the Replace with field. 
6. Edit the Replace with to add the EU for #3. Type a ‘,EU’ 
Display Logix_PIDE 
/T::[SoftLogix]Program:Tank101.LevelController,::[SoftLogix]Program:Tank101.LevelAtune,EU 
/x875 /y125 
 
Remember no spaces for embedded variables being used as a literal string. Put the text 
immediately after the , It should look like this ,EU 
7. Make sure the confirm check box is checked. Click the Replace button. 
8. When prompted to confirm the replace, click the replace button one at a time until complete. 
9. Continue to look in the Search for list and make sure there are not anymore references. 
10. Save and Close the display. 
 
3/10/2008 Page 138 of 160 
Verify engineering units are displayed on Tank Overview – Valve 
1. Go to the AF07 Client 
2. Close all displays containing the Logix_PIDE reference objects 
or 
Click the Close Displays button. Click the Tank Overview button. 
3. Click on the valve 
4. Do you see your engineering units? 
Design recommendations for working with global objects 
Depending on global object complexity and the number of data items associated with it, loading a 
display with many global object instances can result in performance issues. For example, a graphic with 
20 relatively data intensive Global Objects takes 5-7 seconds to display. 
At run time, Global Objects require extra time to resolve their required tag instances and start receiving 
them from the data server. This causes graphics using significant numbers of Global Objects to display 
more slowly. The reason for this is that global objects instances and the data items associated with 
them are not cached to the local memory cache at run time. 
Here are some recommendations for working with global objects: 
ƒ Whenever possible, avoid creating global objects that are too complex. Object complexity is 
measured by the number of graphic objects contained within a global object, the number of 
expressions and animations associated with a global object, the number of global object 
connections, and combinations of these variables. If a complex global object is required, avoid 
creating a large number of instances of this object on one standard display. 
ƒ Do not create a large number of base global objects on a single global object display. Organize 
global object displays in such a way that the majority of base global objects required by a 
specific standard display, reside on the same global object display. 
ƒ If a standard display contains ten or more complex global objects and is being accessed 
frequently, set its Cache After Displaying property to Yes. This is done in the Properties tab of 
the Display Settings dialog box 
 
Important: While the Cache After Displaying property is in effect, design-time changes to the 
base object will not be picked up by the corresponding reference object until the FlushCache 
command is issued, or an SE Client session is closed and restarted. 
Future product enhancements are planned to improve Global Object performance. 
 
3/10/2008 Page 139 of 160 
Section 10: Language Switching (est. time 30 min) 
About This Section 
In this section, you will learn about: 
ƒ Language Switching 
ƒ FactoryTalk View SE Language Switching 
ƒ Configuration of supported languages 
ƒ Export strings for translating 
ƒ Translate strings 
ƒ Import strings that have been translated 
ƒ Language switching command 
ƒ View language switching 
ƒ Language switching in alarm messages (FactoryTalk Alarms and Events) 
ƒ Device-based alarm language switching 
ƒ Export alarm messages 
ƒ Translate alarm messages 
ƒ Import alarm messages 
ƒ Tag-based alarm language switching 
ƒ Create a Tag Alarm and Event Server 
ƒ Translate alarm messages 
ƒ Import alarm messages 
ƒ Verify alarm import 
ƒ Export alarm messages 
ƒ View language switching of alarm messages 
About Language Switching 
Language switching allows operators to view user-defined text strings in FactoryTalk View SE Client 
applications in multiple languages at run time. This includes FactoryTalk device-based alarm messages 
created in RSLogix 5000 and FactoryTalk tag-based alarm messages created in the Alarm Setup 
Editor. FactoryTalk historical alarm and event information is only logged in one language which is 
specified on the alarm server properties. 
At run time in a network application, multiple FactoryTalk View SE clients can switch between any of 
the languages the application supports. Multiple clients can also run in different languages at the same 
time. 
With language switching you can: 
ƒ Develop an application in one language, export the user-defined text strings for the application, and 
then import translated strings for up to 40 languages into the same application. 
 
3/10/2008 Page 140 of 160 
ƒ Deploy a distributed application across different countries, allowing operators in each location to 
view the application in their own language. 
ƒ Enable operators in multilingual countries to use the language of their choice. 
 
 Language Switching Enhancements 
ƒ A default language for language switching can be specified. 
ƒ Support for 40 languages. Previous to this release only 20 different languages were supported. 
ƒ Local message displays support language switching 
String Spreadsheet Editing 
String spreadsheet editing lets you export text strings for all languages supported by an application to 
an Excel spreadsheet in one easy operation. You can also import text strings in one or multiple 
languages from an Excel spreadsheet to an application. 
The Optimize Duplicate Strings feature allows you to translate only 1 occurrence of each string to 
reduce errors and translation costs. 
FactoryTalk Alarms and Events 
Language switching is supported in FactoryTalk Alarms and Events. 
FactoryTalk View SE Language Switching 
In general, the user-defined strings that support language switching are those that an operator sees in 
an application at run time. Specifically, these are: 
ƒ text you specify for graphic objects and global objects including 
o captions 
o tool tip text 
o time and date embedded variables 
o local messages 
o numeric embedded variables 
ƒ FactoryTalk View text objects (Note: A text object with its SizeToFit property set to True might 
change in size when displayed in different languages.) 
ƒ text strings defined for FactoryTalk Alarm and Event summaries, banners, and log viewers 
ƒ graphic and global object display titles specified in the Display Settings dialog box 
Among the text strings that do not support language switching are: 
ƒ text strings that are part of the graphical user interface of FactoryTalk View Studio or View SE 
Client software, such as menus, which are displayed in the same language as the operating 
system. These are translated when FactoryTalk View is localized 
ƒ text that can be displayed at run timebut is used to operate the application, such as the names 
of graphic displays and command strings 
ƒ tag descriptions and string constants in expressions 
 
3/10/2008 Page 141 of 160 
ƒ text in the title bar of the FactoryTalk View SE Client window, which is part of the setup of the 
client, not part of the application 
ƒ text associated with HMI tag alarms 
ƒ Alarm Fault List messages displayed in FactoryTalk Alarm and Event Summary and Banner 
objects 
Configuration of supported languages 
You will need to add the desired languages to the application. 
1. From FactoryTalk View Studio, select the Tools > Languages… menu item. 
 
2. Click the Add… button on the Language Configuration dialog. 
The languages in the list are supported for language switching by the application at run time. Be sure 
that these Windows languages are installed on the development and client computers before trying to 
switch languages. 
To find out which languages are installed on a computer, check the Regional Options (Windows 2000) 
or Regional and Language Options (Windows XP and Windows Server 2003), in the Control Panel. 
The languages you will be selecting are installed. 
 
3/10/2008 Page 142 of 160 
3. Select the German (Germany) language and click the OK button. 
 
4. Click the Add… button on the Language Configuration dialog. 
5. Select the Spanish (Mexico) language and click the OK button. 
 
 
3/10/2008 Page 143 of 160 
6. Select the Chinese (PRC) language and click the OK button. 
 
7. Notice that these languages have been added to the list and English is set as the default 
language as indicated by the check mark next to English. 
8. Check the Display undefined strings using the default language option. 
 
9. Click the Apply button. 
 
3/10/2008 Page 144 of 160 
Your application has been configured to support 3 languages. Now you will need to perform an export 
to get the strings that you will need for translation. 
Export strings for translating 
There are a number of ways to change the text strings in a graphic display besides editing them 
individually by object. The best approach is to export the strings to Excel and use the Optimize 
duplicate strings feature. 
1. Click the Export button 
 
2. Select the Export strings for all languages to an Excel spreadsheet radio button. Check the 
Optimizing duplicate strings and Open exported file options 
 
3. Click the Next button 
If you have a network application with multiple HMI Servers you would be prompted to select one HMI 
Server at this point. Since you are using a local application there is only one HMI Server and you will 
not see the Select Servers dialog. 
4. Leave the default location and click the Finish button. 
5. The String Export in Progress will start and then complete. 
6. The Excel document will be created and opened. 
 
3/10/2008 Page 145 of 160 
Translate strings 
Observe the open Excel file. Everywhere you see the text **REF: in the language columns (i.e., en-US, 
de-DE, es-MX, and zh-CN) is referencing a duplicate string in the REF column before the language 
column. That means you don’t have to translate the text for that object. You only have to translate the 
first occurrence of that text indicated by the text **UNDEFINED**. You will use a different file that has 
already been translated to do the import. 
Scroll down in Excel until you see row number 230. Column D “Description” will have 
‘CloseNonPermissive_Text.Caption”. Note, your Excel file may look different. If it isn’t row 230 do a find 
on the description. This is REF:36 and it is the first occurrence. Row 244 has a Column D description of 
“OpenNonPermissive_Text.Caption” and is cross-referencing (**REF:36**) the first occurrence. Only 
the first occurrence will need to be translated. Notice that the cross-reference to the first occurrence is 
in the language columns. Notice that the “REF” Columns (E, G, I, and K) are left blank when the 
occurrence is not cross-referenced. 
Here is an example of first occurrence references of #36, 231, 232, and 233 along with the cross-
reverences. 
 
Let’s look at a file that has been translated for you. 
1. From the Start menu, select the Lab 15 FactoryTalk View SE shortcut 
. Open the LanguageSwitching folder. 
2. Double-click on the AF07_translated.xls file 
 
3. Observe the file. Notice that not everything has been translated. Notice that this file was translated 
from an export file that was not optimized. 
4. Close the file. 
 
 
3/10/2008 Page 146 of 160 
Import strings that have been translated 
Now that you have a file with translated strings, let’s import them. 
1. Select the Import button from the Language Configuration dialog. 
2. Select the option to Import strings from an Excel spreadsheet…. from the String Import Export 
Wizard dialog and click the Next button 
 
 
3/10/2008 Page 147 of 160 
3. Select the Browse … button and browse to this file C:\LabFiles\Lab 15 FactoryTalk View 
SE\LanguageSwitching\AF07_translated.xls and click the Finish button. 
 
4. String import in Progress will start. Once it is completed, you will see the message String import 
completed successfully in the Diagnostics List. 
5. Click the OK button on the Language Configuration dialog. 
Language switching command 
There is a FactoryTalk View language switch command that you use to perform language switching. 
Buttons that use this command have been configured on the footer display. Let’s look at them. 
1. From the Explorer, open the footer display. 
2. Double-click on the US flag button to open the Button Properties dialog. 
3. On the Button Properties dialog, click on the Action tab. 
Notice the Release action - Language en-US 
The Language command was added to the Release action by clicking the … button and then using the 
Command Wizard. The command Language is located under the System – Languages folder. 
 
3/10/2008 Page 148 of 160 
 
Only the languages that have been added to your application will be displayed in the language id list. 
 
 
4. Click the Cancel button. 
5. Repeat steps 2 – 4 for the other flags to observe the release action. 
6. Close the footer display. 
View language switching 
Language switch commands are ignored in Test Display mode. Since the client was up and running 
before we added the new languages, we need to close the client and open it again for the additional 
languages to appear. 
 
3/10/2008 Page 149 of 160 
1. Go to the AF07 Client. 
2. Close the AF07 client. 
3. Go back to View Studio an Launch the client. 
4. Click the different flag buttons in the footer display and navigate through different displays. 
5. Notice that language switching works but not everything was translated. 
6. Notice that the date and time are still displayed in English. 
You can use FactoryTalk View SE system tags in an application to display text in graphic displays. For 
example, the tag, system\dateandtimestring, displays the current date and time. Text in the following 
system tags is always displayed in the format prescribed by the language of the Windows operating 
system: 
ƒ System\Time 
ƒ System\Date 
ƒ System\DateAndTimeString 
ƒ System\MonthString 
ƒ System\AlarmMostRecentDate 
ƒ System\AlarmMostRecentTime 
ƒ System\AlarmStatus 
7. Notice that alarm messages for Tank101 are not translated. These will be translated in the next 
section. 
 
Device-based alarm language switching 
In RSLogix 5000, use the Alarm Properties dialog box to translate device-based alarm messages 
individually. RSLogix 5000 configures alarm messages in the language of RSLogix 5000 software. For 
example, theGerman version of RSLogix 5000 configures alarm messages in the German language. If 
you add another language, then when RSLinx Enterprise connects to the controller, both languages are 
uploaded and available to FactoryTalk Alarms and Events clients. 
 
3/10/2008 Page 150 of 160 
You can export alarms from RSLogix 5000 to a comma-separated variable (*.csv) or text (*.txt) file. For 
double-byte character sets (for example, Chinese), export alarms in .txt format because in RSLogix 
5000, the .csv format does not support Unicode character sets. 
Once you have exported the alarm messages, you can then manually add all the messages in the 
languages you desire (limited to the languages supported by FactoryTalk View) and then import the file 
when translation is complete. This simplifies sending the work out to translators. 
Export alarm messages in RSLogix 5000 
1. Go to RSLogix 5000 
OR if it isn’t already opened 
 
select the AF07_SE_Lab shortcut from the Start menu 
 
 
OR 
 
Click the Logix 5000 Alarms button on the footer menu of the FactoryTalk View Client 
 
 
 
2. Select the Tools > Export menu item. 
3. When the Export dialog opens navigate to C:\LabFiles\Lab 15 FactoryTalk View 
SE\LanguageSwitching and keep the default filename. 
4. Notice the Save as type options for the export file. 
 
 
 
This lab will demonstrate how to use both formats. 
5. Keep the default of RSLogix 5000 Import/Export File (*.CSV) selected. 
6. Click the Export button. 
If your RSLogix 5000 project includes a large number of programs, and you want to translate alarm 
messages from only one of them, you can make selections in the Export dialog box to limit the data that 
is exported. 
 
3/10/2008 Page 151 of 160 
Translate alarm messages 
1. From the Start menu, select the Lab 15 FactoryTalk View SE 
shortcut . Open the LanguageSwitching folder. 
2. Double-click on the AF07_SE_Lab-Tags.CSV file to open it in Microsoft Excel. 
 
3. Expand the width of columns A, B, C, and D. Notice that the last line of text in the file is the alarm 
definition for the low alarm for the ProductTempLoop which we will be modifying. The first element 
from the left is the instruction type (ALMMSG:) and the language string for the alarm message (en-
us for English in the United States). The alarm message text appears as the fourth column (D) 
from the left (“ProductTemp Low”). 
4. Copy the last ALMMSG line and then paste it at the end of the file. 
 
5. Change the text en-us to ‘de-DE’ (for German in Germany), and then change the alarm message 
text to read, ‘ProductTemp Tiefpunkt’ 
6. Paste another copy of the ALMMSG line at the end of the file. 
7. Change the text en-us to ‘es-MX’ (for Spanish in Mexico), and then change the alarm message 
text to read, ‘ProductTemp Bajo’. 
Your file should look something like this. 
 
8. Save your changes. 
 
3/10/2008 Page 152 of 160 
An export file C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitchingAF07_SE_Lab-
Tags_translated.TXT has been translated for you. The export file was created using the RSLogix 
5000 Unicode Import/Export (*.TXT) format because it includes message strings that were translated in 
Chinese. You will use that file when performing an import. 
 
 
 
3/10/2008 Page 153 of 160 
Import alarm messages 
1. From RSLogix 5000, if you are online with the controller then go offline by selecting the 
Communications > Go Offline menu item. 
 
2. Select the Tools > Import menu item. 
 
3. When the Import dialog opens navigate to C:\LabFiles\Lab 15 FactoryTalk View 
SE\LanguageSwitching 
 
4. Select the RSLogix 5000 Unicode Import/Export Files (*.TXT) file type. 
 
5. Select the filename AF07_SE_Lab-Tags_translated.TXT, leave the default settings for the Tags 
and Logic Comments. 
 
6. Click the Import button. 
 
7. Select the Communications > Download menu item 
8. When the Download Dialog appears, select the Download button. 
9. When prompted with the message “Done downloading. Change the controller mode back to 
Remote Run?” select the Yes button. 
 
3/10/2008 Page 154 of 160 
10. Make sure the controller is in Remote Run mode. 
 
If it is not, select the Communications > Run Mode menu item 
11. Tank 101 alarms should now be language translating in View Client. You will verify this at the end of 
this section. 
 
Tag-based alarm language switching 
When the Alarm and Event Setup editor launches in FactoryTalk Administration Console, alarm 
messages display in the default language defined for the application. If a message string does not exist 
in the default language a question mark character (?) is displayed. 
When the Tag Alarm and Event Editor opens in FactoryTalk View Studio, alarm messages display in 
the language selected during start up of the FactoryTalk View SE application. If alarm messages are 
not defined in the specified language, alarm messages display in the default language defined for the 
application. If a message string does not exist in the default language a question mark character (?) is 
displayed. 
When editing alarm messages in multiple languages, the Microsoft Excel method offers the advantage 
that you don’t have to close and then re-open the application in the appropriate language each time—
you can edit the text in any language in one step and then import the translated text for all languages 
into the application at once. 
 
3/10/2008 Page 155 of 160 
Create a Tag Alarm and Event Server 
1. From the Explorer, right-click on the AF07 and select the Add New Server > Tag Alarm and 
Event Server… context menu item. 
 
2. On the General tab of the Tag Alarm and Event Server Properties page type ‘FTAETagServer’ 
for the name. 
3. Click on the Priorities and History tab, leave the settings at the defaults: 
 
Notice the history is being logged in English and the tag alarms will be logged in the same 
database as the device-based alarms. 
4. Click the OK button 
 
3/10/2008 Page 156 of 160 
5. Tag based alarms can be created and configured with the Alarm and Event Setup Editor. 
Double-clicking on the Alarm and Event Setup icon under the Alarm and Event Tag Server in 
the Explorer. 
 
6. The Alarm and Event Setup Editor will open. Notice that there are no alarms. You will use the 
import to create alarms. 
7. Close the Alarm and Event Setup Editor 
Normally, you would use the Alarm and Event Setup Editor to create your alarms, do an export, 
translate the alarm messages, and then import them back into the Tag Alarm and Event Server. For 
this lab you will be creating your alarms with a file that contains the alarms and the translated 
messages strings. You will step through an export at the end of this section to see how it works. 
Translate alarm messages 
1. If you don’t have C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching folder open, do 
so. 
2. Double-click on the AF07_FTAETagServer_AlarmExport_translated.xls file to open it. 
 
3. Notice there is a worksheet for each alarm type, one for the messages, and then one for tag update 
rates. 
 
4. Click on each of the tabs and take a look. There is one digital alarm and one level alarm. Notice 
that one message can be used in multiple alarms. 
5. Click on the Messages tab. There is a column for each language that has been translated. 
6. Close the file. 
Import alarm messages 
1. From the Explorer, right-click on the FTAETagServer and select the Import and Export… 
context menu item. 
 
The Alarm Import Export Wizard will open. 
 
3/10/2008 Page 157 of 160 
2. Select the Import alarm configuration from Excel File options and click the Next button. 
 
3. Click the browse … button.4. The Select Alarm Import File dialog will open. 
Navigate to C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching. 
Select the AF07_FTAETagServer_AlarmExport_translated.xls file and click the Open button. 
5. Click the Next button on the Alarm Import Export Wizard 
6. Select the Update existing alarm definitions and create new alarm definitions from the import 
file option and click the Finish button. 
 
7. A progress indicator will open. When complete, you should see this 
 
8. Click the OK button. 
Verify alarm import 
1. Double-clicking on the Alarm and Event Setup icon under the Alarm and Event Tag Server in 
the Explorer. 
 
 
3/10/2008 Page 158 of 160 
2. The Alarm and Event Setup Editor will open. Notice that there are two alarms. 
 
3. Double-click on the first alarm, the Digital Alarm Properties dialog will open. Look at the Digital 
Tab and notice that these properties are almost the same as the device-based digital alarm 
instruction property sheet that you saw in RSLogix 5000. In fact, this tag alarm will be triggered from 
the same condition as a device-based alarm that was created. This is just so you can compare 
them. 
 
 
3/10/2008 Page 159 of 160 
4. Click the forward arrow button to navigate to the next alarm 
 
5. The next alarm will be displayed in the Level Alarm Properties dialog. Look at the Level and the 
Messages tabs and notice that these properties are almost the same as the device-based analog 
alarm instruction property sheet that you saw in RSLogix 5000. In fact, this tag alarm will be 
triggered from the same condition as a device-based alarm that was created. This is just so you can 
compare them. Notice on the Messages tab that the same message string is used for both the High 
High and the High condition. 
6. Click the Cancel button to close the Level Alarm Properties 
7. Click the Messages tab. 
Messages can be created when a new alarm is being created or they can be created from the message 
tab and then they can be associated with an alarm. 
You can create as many messages as you like for alarms, but each alarm can be associated with only 
one message. For level alarms, you can configure one message per level condition. 
Alarm messages can be shared between alarms to eliminate duplication. The Usage column on the 
Message tab indicates how many alarms are referencing an alarm message. 
8. To view the list of alarms that are referencing a particular alarm message, right-click the row 
containing the message and then click the Usage Details context menu item. Click the OK button 
to close the Message Usage Details dialog. 
9. Close the Alarm and Event Setup Editor 
Export alarm messages 
You will step through an export to see how it is done. 
1. From the Explorer, right-click on the FTAETagServer and select the Import and Export… 
context menu item. 
 
The Alarm Import Export Wizard will open. 
2. Select the Export alarm configuration to Excel file and click the Next button 
 
 
3/10/2008 Page 160 of 160 
3. Leave the defaults with all the selected alarms and click the Next button 
 
4. Select the Export messages for all alarms, check all the languages, and click the Next button. 
 
5. Change the file name to MY_ AF07_FTAETagServer_AlarmExport.xls and click the Finish 
button. 
 
6. A progress indicator will open. When complete, Click the OK button. 
 
3/10/2008 Page 161 of 160 
View translated Alarm Messages 
When RSLinx Enterprise makes the connection to the controller, all alarm messages and their 
languages are uploaded from the controller. When a FactoryTalk View SE Client runs, the FactoryTalk 
Alarm and Event objects (Alarm and Event Summary, for example) connect to the Alarm and Event 
system and request alarm messages in the current language. You can then switch among languages 
with the click of a button on the client computer, and the alarm monitoring system and all of the client 
screens switch to the appropriate language on that specific client. 
Switching languages at run time does not switch time and date formats. The Alarm and Event objects in 
FactoryTalk View always show the date/time format of the operating system. 
Alarm Fault List messages that can be displayed from the Alarm and Event Banner and Summary do 
not currently switch languages. 
FactoryTalk historical alarm and event information is only logged in one language which is specified on 
the alarm server properties. The contents of the Alarm and Event Log Viewer event list, which consists 
of historical alarm and event information, is not translated. This data continues to appear in the same 
language used when the alarm and event information was written to the alarm history database. For 
example, a message logged in English will be displayed only in English, even if the language is 
switched to German. 
1. Go to the AF07 Client. 
2. Click the different flag buttons in the footer display and navigate through different displays. 
3. Notice that language switching works and alarm messages are also being updated to the 
appropriate language. 
4. Notice both the tag and device-based alarms appear and the message strings are language 
switchable. Tag-based alarms will start with Tank101. Device-based alarms will have the shortcut 
name at the beginning of the alarm name i.e., [SoftLogix]. 
 
Tag-based alarms will not appear in the Tank Summary because the event subscription is set to 
[SoftLogix]Program:Tank101.*. The tag-based alarms start with Tank101. To get them to appear in the 
Tank Summary, change the event subscription to *Tank101* or add another event source called 
Tank101* 
. 
You have completed this lab!