VIZ07 - FactoryTalk View SE Lab Manual

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


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


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


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


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 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 youll 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 Automations 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 of Section 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 exercises are 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 communicating through 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 using a 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 its a network application, add one or more Areas

3) If its 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 its set to display when you create a new HMI server. If you dont want to add faceplates, click Cancel to close the dialog box, without affecting HMI server creation. If you dont 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 computers 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/2008 Page 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

Lets 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. Its 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

Lets 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 dont 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 selected tag 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.


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


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.


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.


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

Lets open up one of the displays and take a look at animation.

To open the Object Explorer

1. Open the TankOverview display. Expand the Displays 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 dont 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.

Lets 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. Lets 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 TankOverview graphic 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.


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 dont 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 users

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 fit in 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 tags 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 applications 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 tags 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 servers 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

Documents

VIZ07 - FactoryTalk View SE Lab Manual