FactoryTalk View SE

FactoryTalk View SE: Hands-On Lab
Traiiniing Lab Manuall Tra n ng Lab Manua

.

TIME 15 MINUTES) ________________________________51 3/10/2008 Page 5 of 160 . TIME 20 MIN)______________________________42 ABOUT THIS SECTION ______________________________________________________42 GRAPHIC DISPLAYS ________________________________________________________42 ANIMATION 44 SECTION 3: TESTING DISPLAYS (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.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) __________________________ 98 ABOUT THIS SECTION ______________________________________________________ 98 RUNTIME EXPLORATION_____________________________________________________ 98 CONFIGURATION EXPLORATION ______________________________________________ 100 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 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 7 of 160 . 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.QUERYING LOGGED DATA __________________________________________________105 SECTION 8: FACTORYTALK DIAGNOSTICS SETUP AND THE VIEWER (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.

.

For this lab.00 (CPR 9). After executing the first few sections of the lab you will be provided several options. the development environment. The term “network” will be used instead of “distributed”.cli) It is recommended that novice users complete remaining lab procedures in the order they are presented. and supervisory control. Advanced users must complete all of Section 1 Creating your application Section 2 Graphic Displays . View SE is an integrated package for developing and running multi-user.00 (CPR 9). 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 9 of 160 . 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. product name changes have taken place to better reflect Rockwell Automation’s system-oriented software and integrated architecture. The remaining laboratory time is to be used for exploring the additional exercises. “RSView SE” was re-branded as “FactoryTalk View Site Edition” (or FactoryTalk View SE). What You Will Accomplish In This Lab As you complete the exercises in this hands-on session. Note: In v 5.Add Graphic Displays Section 3 Testing Displays . In this lab. Add Content to the Application. a data server. Configure and Run a Client. View Studio.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).Configure a FactoryTalk View Client File called AF07 or use the preconfigured client file (C:\LabFiles\Lab 15 FactoryTalk View SE\Client\AF07. time permitting. This lab uses FactoryTalk View SE 5. The term “local” will be used instead of stand-alone. these components could actually be on separate computers. This time estimate includes: Add Servers to the Application. you will be working with a local application containing an HMI Server. View SE is designed for automated process or machine monitoring. In the deployed system however. and a single HMI Client. The first 3 sections will take approximately 60 minutes for the novice user to complete. will also be on this computer. these servers and clients will all be located on the same computer. The additional exercises are optional and the approximate time to complete each exercise is indicated in the description. Terms used to describe a FactoryTalk View SE application and a FactoryTalk directory has changed. View SE scales easily from small to large systems. networked human-machine interface (HMI) applications. This lab procedure contains content and exercises for both novice and advanced users. and additional HMI clients could be used.

we have provided you with the following materials that will allow you to complete the labs in this workbook. redistributable version of Microsoft SQL Server.00.00.00.00 (Bld 42) Microsoft SQL Server 2005 Express Microsoft SQL Server Management Studio Express Microsoft SQL Server 2005 Express Edition is a free.00 SoftLogix 16. Hardware This hands-on lab does not require any hardware. or you can install Microsoft SQL Server 2005 Express. Lab Materials For this Hands-On lab.00.0117 FactoryTalk View SE v5.00.17 RSLogix5000 v16.55 RSLinx Enterprise v5. CompactLogix L3x and L4x.10.10. FactoryTalk Alarms and Events uses Microsoft SQL Server as the database engine for logging alarm and event information. A Logix5000 controller could be used in place of SoftLogix 5800. You can connect to an existing SQL Server database.00. 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. Service Pack 2. Note: FactoryTalk Alarms and Events Device Based Alarms requires firmware version 16.0117 (included with FactoryTalk View Site Edition and RSLinx Enterprise) RSLinx Classic (used for Logix programming) v2. which is included in the Redist folder on the FactoryTalk View SE and RSLinx Enterprise CDs.99 FactoryTalk Alarms and Events v2.00. and DriveLogix.03.03.52. Software This hands-on lab uses the following software: FactoryTalk Services Platform v2.20 or higher for ControlLogix.

Microsoft SQL Server Management Studio Express (SSMSE) is a free.key ClientStartup.Translated file for FactoryTalk Alarms and Events device-based alarm messages in RSLogix 5000 AF07_FTAETagServer_AlarmExport_translated.xls – Translated file for FactoryTalk View SE AF07_SE_Lab-Tags_translated. 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.ACD – copy of control program that is for the beginning of this lab prior to Tank 101 alarm messages being converted.sql Preconfigured FactoryTalk View SE files to be used in this lab: AlarmLogViewer.ACD – control program with Tank 101 alarms converted for language switching.cli 3/10/2008 Page 11 of 160 . Some alarm messages were preconfigured for language switching at the beginning of this lab AF07_SE_Lab_post_translation.gfx AlarmSummary.xls .mcr TankDataLogging.gfx TankAlarmSummary.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. It is included in the Redist folder on the FactoryTalk View SE and RSLinx Enterprise CDs. AF07_SE_Lab.gfx Footer.gfx AlarmStatusExplorer. easy-to-use graphical management tool for managing SQL Server 2005 Express.gfx Header.ACD – control program to be used in this lab AF07_SE_Lab_pre_translation.gfx – used in the Data Logging Section of this lab Tank101.TXT .gfx TankOverview.mdf – used in the Data Logging Section of this lab Client – contains a preconfigured FactoryTalk View SE Client file AF07. 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.gfx ClientKeys.

Note: When you type the text in the field.ACD to C:\RSLogix 5000\Projects\AF07_SE_Lab.. Most often.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.g. or a menu name from which you must choose an option or command. RSLogix 5000 or OK) Indicates: Any item or button that you must click on. Words shown in bold italics. authors use this “Tip Text” style for important information they want their students to see.g. Data Logging.ACD FactoryTalk View Studio – application shortcut Installed files for East Asian languages.. we have used the following conventions to help guide you through the lab materials.g. Document Conventions Throughout this workbook. Note that the files and setup steps for the optional sections (Language Switching. a variable).. enclosed in single quotes (e. directory. but not information that is required reading in order for you to complete the lab exercises.ACD – shortcut to C:\RSLogix 5000\Projects\AF07_SE_Lab. remember that you do not need to type the quotes. 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. This style or symbol: Words shown in bold italics (e. Controller1). The text that appears inside of this gray box is supplemental information regarding the lab materials. This will be an actual name of an item that you see on your screen or in an example.ACD Shortcuts for the following applications.. Note you only have to do this to demonstrate the Chinese language support. simply type the words that are contained within them (e.g. 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. 'Controller1') 3/10/2008 Page 12 of 160 . This is information that you must supply based on your application (e. The text that follows this symbol may provide you with helpful hints that can make it easier for you to use this product. An item that you must type in the specified field. and FactoryTalk Diagnostics) are not required unless you want to do those sections.

From there.The text that appears inside this gray box with the graphic will indicate that a feature is new in the V 5. Note: If the mouse button is not specified in the text. Though the lab can be done linearly. the user may select which exercises interest them most without having to be concerned with numerical order. the only required exercises are all of Section 1 Creating your application. where all exercises are cumulative.Add Graphic Displays. If Log On To Windows dialog is active type ‘administrator’ for Username and type ‘rockwell’ for password.00 (CPR 9) Release. Section 2 Graphic Displays .Configure a FactoryTalk View Client File called AF07. 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. 3/10/2008 Page 13 of 160 . The following steps must be completed before starting the lab exercise: 1. 2. and Section 3 Testing Displays . Use the same Login information if prompted to Log On to the FactoryTalk Directory or when creating a FactoryTalk Alarms and Events History Database.

distributed over a network. FactoryTalk Services Platform. FactoryTalk View comes with process faceplates and graphic libraries that can be used in your applications. Many of the graphic library objects are preconfigured with animation. and Windows 2000 operating systems. and includes client and server software for testing the applications you create. A member of the FactoryTalk family of products. FactoryTalk View Studio contains editors for creating complete applications.Overview About this lab This lab will outline the major components and fundamental ideas of FactoryTalk View Site Edition. FactoryTalk View Site Edition consists of several pieces of software you can use to build automation applications. You can use FactoryTalk View Studio to develop FactoryTalk View Site Edition and FactoryTalk View Machine Edition (ME) applications. FactoryTalk™ Directory. Process faceplates are preconfigured to work with various Logix5000 instructions (for example. FactoryTalk View SE Server. and FactoryTalk Activation. FactoryTalk View Site Edition (also called FactoryTalk View SE) provides all the tools you need to create powerful. Depending on the particular software packages installed. 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 humanmachine interface (HMI) applications that involve multiple users and servers. Windows XP. PIDE. 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. and the new ALMD and ALMA instructions). Use the editors to create applications that are as simple or as complex as you need. . FactoryTalk View SE Client. FactoryTalk View SE software is designed for use with Microsoft® Windows® Server 2003. It will specifically: Discuss the components of FactoryTalk View SE Discuss the differences between FactoryTalk View SE Local and Network Application Discuss HMI Servers. Use the objects as they are. use FactoryTalk View SE Client to view and interact with the application. you will have one or more of the following pieces of software: FactoryTalk View Studio. D2SD. dependable process monitoring and supervisory control applications. or change them to suit your needs. When you have finished developing an application. FactoryTalk Administrator Console. FactoryTalk Alarms and Events. data servers.

With the FactoryTalk View SE Client you can: Load. FactoryTalk View Administration Console allows you to: Change the properties of an HMI server. using the Alarm Log Setup editor (on the Tools menu). Add FactoryTalk users to an application. and manage log files. Change the location alarms are logged to. 3/10/2008 Page 15 of 160 . Run FactoryTalk View commands from the Command Line. The FactoryTalk View Administration Console has a two hour run-time limit. you need to create a configuration file using the FactoryTalk View SE Client wizard. using the Diagnostics Setup editor (on the Tools menu). The HMI Server does not have to be running when you configure a FactoryTalk View SE Client. To continue using it you simply shut it down and restart it. A warning message is displayed five minutes before the time is up. FactoryTalk View Administration Console contains a sub-set of the FactoryTalk View Studio editors. 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. view. using the Runtime Security editor. Change the properties of a data server. using the Alarm Setup editor. so you can make minor changes to an application without the need for installing FactoryTalk View Studio. Change how HMI tag alarms are logged and annunciated. using the Runtime Secured Commands editor.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. Change the path of data log models. Change which system activities are logged and how frequently. Set up security for commands and macros. Import and export HMI tags using the Tag Import and Export Wizard (on the Tools menu). To set up a FactoryTalk View SE Client.

also called the HMI server. FactoryTalk Administration Console Start > Programs > Rockwell Software > FactoryTalk Administration Console Part of the FactoryTalk Services Platform. which is routed through the system for display and logging. performs historical data logging. FactoryTalk View SE Servers. graphic displays. standalone tool for developing applications and managing a FactoryTalk system.00). tag-based alarm monitoring offers the equivalent of HMI Tag Alarm Monitoring. graphic displays. FactoryTalk Alarms and Events Before FactoryTalk® Alarms and Events (introduced in Version 5. However. or for third-party controllers communicating through OPC data servers. Only FactoryTalk View Studio can be used to create HMI servers and HMI projects. Tag-based alarm monitoring is supported for Logix5000 controllers. FactoryTalk View still supports this type of alarm monitoring. FactoryTalk Alarms and Events supports two types of alarm monitoring: Device-based alarm monitoring. and access to real-time data) to products and applications in a FactoryTalk system. data tags. for all of the FactoryTalk products and components participating in an automated control system. To maintain compatibility with existing applications. Tag-based alarm monitoring. Once installed. or if you do not want to use the pre-built alarm instructions available with RSLogix 5000. If you are not using Logix5000 controllers. health monitoring services. stores HMI project components (for example. The controller detects alarm conditions and publishes event information. are programmed in a logic project and then downloaded into a Logix5000 controller. consistent view of alarms and events throughout a FactoryTalk system.FactoryTalk View SE Server The FactoryTalk View SE Server. The server also contains a database of tags. FactoryTalk Alarms and Events can be used instead of FactoryTalk View SE HMI alarm monitoring. available in RSLogix 5000 v. Pre-built alarm instructions. or OPC servers) and names (for example. Software-based Tag Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish event information for display and logging. FactoryTalk Alarms and Events now allows multiple FactoryTalk products to participate together in a common. it runs as a set of ‘headless’ Windows services that supply information to clients as they request it. 16 or later. The FactoryTalk View SE Server has no user interface. FactoryTalk View SE supported only HMI tag alarm monitoring. To maintain compatibility with existing applications. 3/10/2008 Page 16 of 160 . and macros) and serves them to clients. global objects. but with an expanded feature set. FactoryTalk Administration Console is an optional. PLC-5. and HMI alarm monitoring. and log models). FactoryTalk Directory FactoryTalk Directory centralizes access to system resources (for example. and SLC 500 devices communicating through Rockwell Automation Device Servers (RSLinx Enterprise). FactoryTalk View still supports the traditional HMI alarm monitoring. You can use FactoryTalk Administration Console or FactoryTalk View Studio to develop applications and manage a FactoryTalk system. FactoryTalk Services Platform FactoryTalk Services Platform provides common services (such as diagnostic messages.

Floating concurrent activation requires a continuous network connection. and shared by client computers on the network. Create database definitions for logging historical alarm and event messages.Network and Local Network Applications A network application can contain several servers. Configure client computers to recognize the location of a Network Directory Server computer. Set up redundancy for OPC data servers and Tag Alarm and Event Servers. with multiple client users connecting to the application simultaneously. With FactoryTalk Activation. and one or more data servers. FactoryTalk View SE . FactoryTalk Activation provides these types of activations: Local node-locked activations are locked to a single computer. For example. and data log models. and viewing diagnostic messages. one HMI server per area. or system settings. an individual application. Create and configure alarm and event servers. you can use the FactoryTalk View Studio editors in the HMI server project to create application components such as graphics displays. Mobile node-locked activations are locked to a hardware dongle. Organize securable actions into groups.FactoryTalk Administration Console allows you to: Create and configure application. you may use separate servers for different functional areas or locations within your enterprise. logging. Configure options for routing. activation files are generated and distributed electronically. Secure a FactoryTalk system with security services. 3/10/2008 Page 17 of 160 . FactoryTalk Activation Start > Programs > Rockwell Software > FactoryTalk Activation > FactoryTalk Activation Tool FactoryTalk Activation provides a secure. there is no need for a physical “master disk” or any physical media. Once you have created the applications and an HMI server. and allow clients to interface to any of the servers. An area may contain another area within it. running on multiple computers on a network. Shared concurrent activations are locked to an activation server computer. while borrowed concurrent activation does not. Back up and restore an entire directory. There are two types of shared concurrent activation: floating and borrowed. Configure alarm conditions for tag-based alarm detection. and data server elements in a FactoryTalk Directory. from anywhere on the network. including both tag-based and device-based servers. Network applications have one or more areas (see Areas definition below). Configure system-wide policy settings. global objects. software-based system for activating Rockwell Software products and managing software activation files. area. instead.

an RSLinx Enterprise data server (configured as a FactoryTalk device based alarm server). 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*. The application root area can contain one HMI server. and a 3rd party OPC server (configured with the FactoryTalk tag based alarm server). and Packaging. However. This would allow you to add new. identical production lines to the application by copying HMI server projects into new areas. This is not necessary because FactoryTalk allows any client to see any data point within the application. regardless of which server the alarm comes from. You can think of areas as partitions of your hard drive. and one or more data servers. There is not a limit to the number of data servers that can co-exist in the same area. What you want to avoid is one physical installation of a data server to be referenced multiple times from different areas of the application. 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. An automotive plant could be divided into areas called Press and Fabrication. Body Shop. Best Practice Since an area is nothing more than a logical method of organizing the application. Alternatively. or a region within the process facility.0. Line 2. Root Area: All FactoryTalk View applications have one system-defined area called the root area. and not a physical entity. For example. which has the same name as the application. Engine.Areas: A key part of the network architecture system is the area. a single area may contain an HMI server for a physical location of a facility. regardless of which area it comes from. 3/10/2008 Page 18 of 160 . a plant with identical production lines could be divided into areas called Line 1. there is not a limit to the number of areas that can reside within an application. Paint Shop. Baking. Mixing. in this analogy). *Note: The initial release of FactoryTalk Alarms and Events have different limits than FactoryTalk View SE 5. For example. The partitions are all on the same main disk (or application. and Transmission. Please refer to the FactoryTalk Alarms and Events Quick Start Guide or Answer id 44177 within the Rockwell Automation Knowledgebase for more information. a bakery could be divided into areas called Ingredients. Line 3. However. an area might represent a portion of a process. and so on. 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. An area is a logical division within your application. This configuration allows for the alarm summary to filer alarms based on the area name.

3/10/2008 Page 19 of 160 . and Data Log are all different components you can configure under each HMI server – they are not areas within the area. Graphics. HMI Tags. Try looking at one of the areas – ie_packaging. and is_production. but are actually components of an HMI server. is_packaging. ie_production. There is a data server called RSLinx Enterprise located under the root area (Insta Corp). which is the application Insta Corp. Network Directory Root Area HMI Server Servers Areas Area Data server The Insta Corp application consists of four different defined areas: ie_packaging. Notice that the HMI server called IE_CasePack is located inside the area. the topmost area.This is an example of a FactoryTalk View SE network application. Alarms. The areas are marked by the folders that are right off the root. The folders under the ie_packaging HMI Server titled System. Logic and Control.

The diagram below shows an example system architecture using a Network application as part of a distributed FactoryTalk system. 3/10/2008 Page 20 of 160 .

all application components and the FactoryTalk View SE client are located on a single computer. 3/10/2008 Page 21 of 160 .Local Applications A local application is similar to an RSView32 project. 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 standalone FactoryTalk system. There is only one HMI server that is created for you in the root area when the application is created.

Add one or more of the following data servers a. 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 22 of 160 . one HMI server can be added per area (local creates one automatically). Rockwell Automation Device Server b. add one or more Areas 3) If it’s a network application. OPC Data server 5) Set up Tag Alarm and Event Server 6) Create graphic displays. Choose to add any of the faceplate displays into the HMI server. global objects.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. 4) Set up data server communications.

are programmed in a logic project and then downloaded into a Logix5000 controller. or with many clients. such as Siemens or Modicon®. Tag-based alarm monitoring. Third-party controller devices. An HMI server stores HMI project components such as graphic displays. Software-based Tag Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish event information for display and logging. OPC data servers (including RSLinx Classic) support any data server that conforms to the OPC-DA 2. An HMI server also manages a database of tags. Properly configuring a data server allows you to browse for a tag directly. Once a data server is configured. detects HMI tag alarms. and SLC 500 devices communicating through Rockwell Automation Device Servers (RSLinx Enterprise). but with an expanded feature set. 3/10/2008 Page 23 of 160 . Alarm and Event Servers FactoryTalk Alarms and Events allow multiple FactoryTalk products to participate together in a common. using third-party OPC servers. 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. The controller detects alarm conditions and publishes event information. OPC® tags (and their value or status information). PLC-5. and logs historical data. FactoryTalk Alarms and Events support two types of alarm monitoring: Device-based alarm monitoring. You can also use RSLinx Enterprise servers to subscribe to device-based alarms and events. Pre-built alarm instructions. a protocol that allows FactoryTalk View to retrieve tag values from: Rockwell Automation programmable controllers and devices. 16 or later. A data server can be a Rockwell Automation Device Server (RSLinx Enterprise) or a third-party OPC data server that serves up tag values.FactoryTalk View SE – Servers HMI Servers HMI servers are software programs that supply information to clients as they request it. Data Servers A data server provides a route to physical devices on the network. or named variables in a Logix5000 controller.0 standard. and serves these components to clients. tag-based alarm monitoring offers the equivalent of HMI Tag Alarm Monitoring. allowing applications to monitor and control the values in those devices. which is routed through the system for display and logging. you can set it up to point to a specific controller such as a ControlLogix processor. data servers can connect application clients to programmable controller values. The following types of data servers are supported: Rockwell Automation Device Servers (RSLinx Enterprise) provide best performance when communicating with Logix5000 controllers. Tag-based alarm monitoring is supported for Logix5000 controllers. consistent view of alarms and events throughout a FactoryTalk system. If you are not using Logix5000 controllers. OPC stands for OLE for Process Control. available in RSLogix 5000 v. using RSLinx Classic or RSLinx Gateway as an OPC server. For example. or if you do not want to use the pre-built alarm instructions available with RSLogix 5000.

Enhanced PID – PIDE. you will be prompted with the Add Process Faceplates dialog. Select New 5. Run FactoryTalk View Studio. Select the Start > FactoryTalk View Studio menu item. Discrete 2State Device – D2SD. You will be prompted with 4. Creating Local HMI Project in FactoryTalk View Studio To create a local application 1. After the AF07 HMI Server has been created.Section 1: Creating your application (est. Type ‘AF07’ 3. Select Site Edition (Local) 6. Select Create Wait for several seconds to allow FactoryTalk View Studio to create the application. 3/10/2008 Page 24 of 160 . Alarm Digital – ALMD. Select Continue 2. 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. 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.

2. Observe that a local application. Click the OK button. 3/10/2008 Page 25 of 160 .Add Process Faceplates into the HMI Server 1. The HMI Server called AF07 has been created in the root area (AF07). 4. 5. AF07. has been created. Maximize or resize your FactoryTalk View Studio window to the desired size for working with your application. Select the Clear All button. 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.

This is the Application Explorer window that will be used throughout this entire hands-on lab. some image files added for the Alarm faceplates under Images 6. Expand the Libraries folder created. They present views of automated plant activity or processes. 7. . These are the displays that the operator sees at run time. the changes are automatically applied to the copies. Global Object displays . Note: Only the image files starting with State_ were added with the process faceplates. There were also folder. displays.stored in the Displays folder. 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. The other image files are there when the HMI Server is created. The Explorer allows you to select different objects. Local Director HMI Server Application (Root Area) Displays for Process Faceplates added here Global Objects for Process Faceplates added here Types of Graphic Displays Standard Displays . Observe what has been added.stored in the Libraries 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. 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. When you make changes to the original object. All these library files are there when an HMI Server is 3/10/2008 Page 26 of 160 .stored in the Global Objects folder. A library display contains ready-made graphic objects that you can use in other displays. Library displays . and other components of the FactoryTalk View SE application. Click on the + next to the folders to expand them.

if it’s set to display when you create a new HMI server. click Cancel to close the dialog box. or when you create a new local application. Note: Adding faceplate displays to an application affects the license count. you have the option to add the process faceplate displays that are installed with FactoryTalk View SE. Each added faceplate display (. you can either replace the existing display or remove it from the list of displays.gfx file) counts as one display for activation purposes. 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. 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. without affecting HMI server creation.Add Process Faceplates Dialog When you add an HMI server to a network application. These faceplates along with the existing ones can be used as is or changed to suit your needs. 3/10/2008 Page 27 of 160 . uncheck the option to “Display this dialog when creating a new application”. The Add Process Faceplates Dialog box will open. If you don’t want to be prompted every time you create an HMI Server. If you added a display previously. If you don’t want to add faceplates.

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. 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. select the New Database… context menu item 3. 1. 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. 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. Expand the Connections folder. 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. 2. Alarming will be discussed in more detail later in the lab. Right-click on Databases folder. 3/10/2008 Page 28 of 160 . This component also defines and manages database definitions between alarm and event servers and logging destinations.

Click on OK.Your properties dialog should look like this: 4. the user will be assigned access to the database. The database user will also be created. 3/10/2008 Page 29 of 160 . Do you want to create the database?” click the Yes button 6. If the user already exists. When you are prompted with the Database does not exist message box: “The database will be created. After the database is created the dialog will close. 5. Expand the Databases folder to confirm that it was created.

The device server subscribes to alarms in the controller and then publishes the alarm information to FactoryTalk Alarms and Events services. Select the FTAEHistory database definition 7. You will add a Rockwell Automation Device Servers (RSLinx Enterprise). select the Add New Server > Rockwell Automation Device Server (RSLinx Enterprise)… context menu item. Alarm and event support must be enabled. Select the Alarms and Events tab 4. Click the OK button 3/10/2008 Page 30 of 160 . 1. Device-based alarms will be discussed in the Alarming and Language Switching sections of this lab.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. 2. To monitor alarms in a Logix5000 controller. Check the Enable history option 6. It provides the best performance when communicating with Logix5000 controllers. Check the Enable alarm and event support option 5. Right-click on the application node AF07. The RSLinx Enterprise Server Properties will appear. Leave defaults on the General tab. 3. a Rockwell Automation Device Server (RSLinx Enterprise) needs to be added to a FactoryTalk application.

without having to change all tag references to that processor. Expand the RSLinx Enterprise device server. A device shortcut is similar to a Windows shortcut on your computer’s desktop that provides easy access to an application. The Communication Setup editor has a new option for enabling alarm and event support at the device level.8. 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. If the change is made through a dialog box. 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. Double-click on Communication Setup The Communication Setup dialog will appear to the right of the Explorer tree. Open Communications Setup dialog 1. Warnings have been added to FactoryTalk to tell users if making an edit in the development environment will adversely affect the run-time system. 3/10/2008 Page 31 of 160 . In previous releases. 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). Communications Setup Editor Improvements Offline tag browsing no longer requires you to associate the device shortcut with a controller. 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. this warning icon appears next to the component where the edit can be made. which then propagates throughout the rest of the project. This enables the user to change the location of a processor or other such device in one place. Verify that the RSLinx Enterprise device server has been successfully added into your application.

Add Device Shortcut 1. Click the Add button 2. Type the text ‘SoftLogix’ Browse to the controller 1. Backplane. Select Start Browsing 3/10/2008 Page 32 of 160 . Right-click on the 1789-A17.

Select the AF07_SE_Lab. AF07_SE_Lab Note: 2 is the slot number of the SoftLogix module that is in the chassis. 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. Click the Browse… button next to the Offline Tag File entry field.2. In previous releases. This is where the control program for this lab is running. not on a networked location. Enable Alarms and Events support 1. Browse to C:\RSLogix 5000\Projects\ folder. Offline Tag Browsing Improvement Offline tag browsing no longer requires you to associate the device shortcut with a controller.ACD file. 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. Change the Enable Alarms & Events setting to Yes 3/10/2008 Page 33 of 160 . 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. Select 2. 1789-L60/A. Add Offline Tag File 1. Click the Open button.

Click the Yes button. Verify that the Device Shortcut named SoftLogix is highlighted and that slot 2 is highlighted and reads 2. 3/10/2008 Page 34 of 160 .Verify Configuration 1. Make sure your shortcut is SoftLogix we will be using pre-configured displays referencing that shortcut name. Your device shortcut has been created. AF07_SE_Lab for your Primary Device. Review your changes. 1789-L60/A. The Verify dialog will appear. The Communications Setup dialog should close. Click the OK button 2.

Or Select the Objects > Alarm and Event > Summary menu item. drag the cursor to the lower right corner of the display and release the mouse button. you will see the cursor change to show that the Alarm and Event Summary object has been selected. 3/10/2008 Page 35 of 160 . FactoryTalk Alarms and Events Verification 1. 2. 3. Single-click and hold down the mouse button. right-click on the Display folder. select the New context menu item An untitled display will be opened. Single-click to select the Alarm and Event Summary button from the tool menu. We will go into more details about these topics in the Tags and Alarms sections of this lab. Verify that you can access controller tags from the online SoftLogix Controller and the offline tags file by performing tag browses. In the Explorer. Mouse over the upper left corner of the empty display. As you are dragging the mouse you will see a rectangle to show the size of the object that will be created.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.

Release the mouse when you have the desired window size. Look at the Diagnostics List and the messages in it. It may take several seconds for the services to startup before you see alarms in the list. You can hide. 3/10/2008 Page 36 of 160 . 6. To change the size of the diagnostic window mouser the upper edge until you see the double lines. 4. 5. Mouse over the indicator to verify your connection.Ctrl-Z .Select the Edit – Undo menu item . move. It’s located above the status bar at the bottom of the FactoryTalk View Studio main window. 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. resize. 8. Single-click on the Test Display button from the tool menu. and clear messages from the Diagnostics List.After you release the mouse button the Alarm and Event Summary will appear. mouse down and drag up to change the size. Click the Edit Display button to get back to edit mode.Single-click on the Alarm and Event Summary object and select the delete key Diagnostics List The Diagnostics List shows information about system activities. Note: The alarm count of 32 may not be the same on your display.Select the CTRL and Z keys at the same time . To remove the object from the display perform one of the following actions: . Use the arrows to scroll through the messages or resized the window so you can see 3 or 5 lines at a time. 7. You should also start to see alarms appear in the summary (This may take a few moments).

A single controller status alarm is produced for each shortcut that is configured with alarms and events enabled.” This message is an informational message to help verify that your system is configured properly. 3/10/2008 Page 37 of 160 . 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. 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.You should see messages similar to the following. Notice the message “Successfully subscribed to 46 alarms from controller SoftLogix. 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. We have just verified that you have the RSLinx Enterprise Device Server and the SoftLogix Device Shortcut properly configured for FactoryTalk Alarms and Events.

3. 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. Single-click and hold down the mouse button drag the cursor to down and to the right and release the mouse button. Mouse over a blank area on the display. Single-click on the Numeric Input button from the tool menu. Or Select the Objects > Numeric and String > Numeric Input menu item. 2. 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. Click on the Connections tab. 1. As you are dragging the mouse you will see a rectangle to show the size of the object that will be created. you will see the cursor change to show that the Numeric Input object has been selected.

right-click on AF07.4. select the Refresh All Folders context menu item.Offline – Program:Tank101 . Your selected tag should look like this: 3/10/2008 Page 39 of 160 . Click on the Tags… button next to the Value field. It is an output value of the PIDE. CV is a member tag of the Enhanced PIDE. Expand the tree on the left and navigate to SoftLogix . The browser window and panes can be resized.JacketTempLoop JacketTempLoop is an Enhanced PIDE data structure. Click on CV in the right pane. If you don’t see a folder for SoftLogix. 5. 6. The Tag Browser will open.

13. 10. The tag will appear in the Tag/Expression field next to the Value. it would appear as what is called a wireframe. 8. Click the OK button.7 and select the ::[SoftLogix]Program:Tank101.CVEUMin tag for the Minimum Tag/Expression. 12.JacketTempLoop. 0 should appear on the display.7. It would look something like this instead. 3/10/2008 Page 40 of 160 . Repeat steps 4 .JacketTempLoop. 9.CVEUMax tag for the Maximum Tag/Expression. Click the OK button on the Numeric Input Properties dialog. If you were not online with the controller. Repeat steps 4 – 7 and select the ::[SoftLogix]Program:Tank101. 11. because the data is not available at this time. Single-click on the Test Display button from the tool menu. This actually verifies that you got the tag from the offline tag file and you are online with the controller.

Select the Esc key to cancel the changes and 0 will be displayed in the field again. try the numeric input object enhancement out. Click the Edit Display button to get back to edit mode. 18. 3/10/2008 Page 41 of 160 . Click the Edit Display button to get back to edit mode. 0 should appear on the display. 22. 19.14. Notice the field turns red and a message appears in the diagnostics list. 15. Before we close the display. Repeat Steps 1 – 14 but this time for Step 5 we will browse for the ONLINE tag. 16. 17. Close the display and when prompted to save your changes select No. Single-click on the Test Display button from the tool menu. Take a look at the online tags. You have the building blocks in place and are ready to start creating your graphic displays. Section 1 is complete. Type the number ‘-1’ in the field and select the enter key. 20. This time for step 5 collapse the Offline folder and expand the online folder. 21.

Copied to the clipboard from another Windows application and then pasted into the graphics display. rotating them. Copied and pasted from the Graphics Libraries. The elements that make up a graphic display are called graphic objects. 3/10/2008 Page 42 of 160 . flipping them horizontally or vertically. input and display fields. The Objects menu in the Graphic Displays editor (fig. The display can show system or process data. time 20 min) About This Section In this section of the lab you will learn about: Graphic Displays o o Libraries Adding existing HMI Components from the C:\LabFIles\ Lab 15 FactoryTalk View SE directory into your application Object Explorer Tag Placeholders Animation o o The Graphics Displays . and grouping them so they behave as a single object. 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. or another Windows application. Created by another Windows application and inserted into the graphic display using object linking and embedding. and alarm summaries. Graphic Displays A graphic display represents the operator’s view of plant activity. Graphic objects can be Created using the Graphic Display editor. rectangle and ellipse. aligning them with each other. Dragged and dropped from another graphic display or library. 1) provides simple drawing elements such as line. The graphics editor allows you to easily duplicate objects. reshape or resize objects. and arrange them in a variety of ways like stacking them.Adding existing HMI Components into your application must be completed prior to doing any other sections in this lab. as well as ready-made objects such as push buttons. spacing them horizontally or vertically. and provide operators with a way to write values to external devices such as programmable controllers.Section 2: Graphics and Animation (est.

3. Almost all the graphics used in this lab came from the graphics library.e. Open the C:\LabFiles\ Lab 15 FactoryTalk View SE folder. The folder will open. 3/10/2008 Page 43 of 160 . Move the folder so it is on top of FactoryTalk View Studio and you can still see the Explorer. Note: any animation that has been attached to an object will be included with it when it is copied into a display. 2. Displays and macros) that will be used in this lab.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. 1. Select the Start > Lab 15 FactoryTalk View SE menu item. Do the following to add them to the HMI Server. Adding existing HMI Components There are preconfigured HMI components (i.. Select all files but NOT the folders in the Lab 15 FactoryTalk View SE 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. In the example below. left. Files ending in MDF are Data Log Models and will be added in the Data Log Models folder under the Data Log folder. It can contain tag names. In Figure 2. logical and/or bitwise operators. Drag and drop over AF07 3. Files ending in MCR are macro files and will be added to the Macros folder located under the Logic and Control folder. an object can be made to fill (up. For example. There is a tab for each type of animation. relational. If there is a check mark in front of the animation type it means that the selected object is using that animation. constants and mathematical. 3/10/2008 Page 44 of 160 . down. Drag and drop all the files over the AF07 HMI Server. the animation dialog shows that expressions are used to animate objects. Move folder over top of FactoryTalk View Studio 4.4. The files will be added to the appropriate locations. or right) or change color in relation to a tag value. the fields on that animation tab will be grayed out. Expression: An expression is a mathematical or logical equation that returns a value. the Fill and Color animations are being used on the selected object. If an animation type is not available for a selected object. A single tag name is often used for simple expressions. Select all files but not the folders Files ending in GFX are display files and will be added to the Displays folder. You can verify that all the files were added by expanding those folders. 2. Selecting a new object while the Animation dialog is opened will update the Animation dialog for the object that was just selected. 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.

the object it corresponds to is selected. When you click an object in the display to select it. when you select it in the Object Explorer the handles outlining the selected object are visible.Figure 2: Animation Dialog The Object Explorer The Object Explorer provides a list of all the objects in the current graphic display. or is part of a group. If an object is hidden by another. its corresponding entry in the Object Explorer is highlighted in gray. You can expand or collapse the whole list using the Expand and Collapse buttons. Expand the Displays folder. When you click an item in the Object Explorer. 3/10/2008 Page 45 of 160 . A group of objects has a plus sign in front of its name. Open the TankOverview display. double-click on the TankOverview display. Let’s open up one of the displays and take a look at animation. To open the Object Explorer 1. including those that are hidden by other objects. Click this to expand the list of objects that make up the group.

Select the View > Object Explorer menu item Or Select the Show/Hide Object Explorer button from the menu bar to show or hide it. 3/10/2008 Page 46 of 160 . The Object Explorer can be resized and moved. The TankOverview display will be opened. Once selected (indicated by a check next to the menu item name). 3.2. and you will notice that the objects will be highlighted in the display. You can click on any of the objects listed. the Object Explorer appears.

3/10/2008 Page 47 of 160 . for example. Look at groups and animation by using the object explorer 1. animation behavior. Expand and Select the Agitator_Group in the Object Explorer. Grouping is useful when you have common objects that you want to move around or apply behaviors toward.Highlighted Agitator_Group The Object Explorer is truly useful when you group items together and want to reference individual elements within that group.

Right-click on the Agitator_Group and select the Animation > Touch context menu item. 3/10/2008 Page 48 of 160 . In the Object Explorer.2. The display will be positioned at the x and y coordinates specified. 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. 4. use the mouse or arrow keys to navigate down to item 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. 3. The Animation dialog will appear and open on the Touch tab. Position windows so you can see both the Object and Animation window. 5.

You will use the Command Wizard in the Global Objects section of this lab to build a Display command.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 can delete the Release action and recreate it with the Command Wizard. 3/10/2008 Page 49 of 160 .Agitator /x 275 /y150 If you want. Here is what the Command Wizard looked like when building this Display command for the Release action Display Logix_D2SD /T::[SoftLogix]Program:Tank101.

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. At run time you supply the tag names associated with the particular operation and these are used in place of the tag placeholders. To provide tag names at run time do one of these: . We are going to test run this display in View Studio.JacketTempLoop and parameter #2 will be replaced with ::[SoftLogix]Program:Tank101. You can also use the Tag Substitution menu option to replace tag placeholders.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. It has both Touch and Color animation. The first display command will open the Logix_PIDE display and anywhere that parameter #1 is used.Tag Placeholders can be used to mark where you want to insert a tag name at run time. Tag placeholders let you create one display that you can use to represent a number of similar operations. The /T parameter for the Display command allows for a list of tags (separated by commas) to be substituted into the display. 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.JacketTempAtune /X250 /Y20 We have configured touch animation to launch the faceplate display twice. Some objects may have multiple animations defined.JacketTempLoop.JacketTempAtune 7. 3/10/2008 Page 50 of 160 . Continue navigating through the Object explorer and look at various animations.ProductTempAtune /X10 /Y20.List the tag names in the command string for the Display command. it will be replaced with ::[SoftLogix]Program:Tank101. Display Logix_PIDE /T::[SoftLogix]Program:Tank101. but with the ability to show the same faceplate display with different data using parameter passing.ProductTempAtune The second display command will open the Logix_PIDE display and anywhere that parameter #1 is used. Let’s see the animation and parameter passing at work. it will be replaced with ::[SoftLogix]Program:Tank101. 6. . Click the tabs to look at those animation properties. Display Logix_PIDE /T::[SoftLogix]Program:Tank101. A tag placeholder is a cross-hatch character (#) followed by a number from 1 to 500. For example look at Tank101_AlarmIndicator_Polygon. There are actually 2 commands that will be executed by this expression. ::[SoftLogix]Program:Tank101.ProductTempLoop and parameter #2 will be replaced with ::[SoftLogix]Program:Tank101. ::[SoftLogix]Program:Tank101.ProductTempLoop. The faceplate displays will also be placed in different positions do they don’t overlay each other.

run the display in a FactoryTalk View SE Client. For example. screen navigation commands.Section 3: Testing Displays (est. Some FactoryTalk View commands are ignored when run in test display mode. edit. In Section 1. test run. the Test Display was used for both a FactoryTalk Alarm and Event and a native FactoryTalk View object. Behavior when test running a display might not always be identical to run-time behavior if changes made during development are not saved. by switching to test display mode in the Graphics editor. Verify Communications. Before you deploy an application. Let’s try this to animate the TankOverview display. 3/10/2008 Page 51 of 160 . 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. and using parameter values in a reference global object will not function in test display mode. using parameter placeholders in a display. The Microsoft VBA IDE (Visual Basic for Applications Integrated Design Environment) lets you write. and debug code. The FactoryTalk Alarms and Events Objects will work in test display mode. To test these features. Testing a graphic display in FactoryTalk View Studio is not the same as running the display in the FactoryTalk View SE Client. To make the behavior as close as possible you should save a display before testing it. to verify that everything works as intended. 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 o o Explore Docked Displays at Runtime Verify Client Keys work at Runtime 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. it is recommended that you test it in the FactoryTalk View SE Client. You can test the objects in a graphic display quickly. 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. Not everything can be done by test running your display.

look at a few of the components that were preconfigured for you to use with your client. Now you will need to configure a client file and run the client to finish testing the display. A macro can be specified on startup or shutdown of a client or display. From the FactoryTalk View Studio toolbar click on the Test Display button. 2. A macro is a list of commands or command symbols stored in a text file. 3/10/2008 Page 52 of 160 . 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.1. Click the Edit Display button to get back to edit mode. Look at the Diagnostics List. Configure Client File Before you configure the client file. Observe that the TankOverview graphic begins to animate. Click on the agitator and then click on the valve What happened? Nothing. 3. It can be called from a command line in FactoryTalk View Studio or from the Factory Talk View Administration Console for system administration. 4. The Display command for the touch animation on the agitator and the valve was issued but the command is ignored in FactoryTalk View Studio. The TankOverview display should be opened and have focus in FactoryTalk View Studio.

Some tag values will be set to 1. and set tag values in the controller. If prompted to save changes. Generally. The ClientStartup macro will be opened. with one command finishing before the next begins execution. In cases like that. double-click in the macro. Observe Pre-configured Macro These commands will dock displays at the top and bottom of the client window. select the No button. take longer. it does not finish until the message has been sent to the controller. Others. such as Set. To invoke the command wizard from the macro file.M). For example when you press F5 in Internet Explorer you will refresh the page. expand the Macros folder. FactoryTalk View SE has similar functionality. you can set up the macro so that the next command can be executed before the previous command is finished. 1. 3/10/2008 Page 53 of 160 . Double-click on the ClientStartup macro.FactoryTalk View has multi-tasking capabilities that you can take advantage of when you create macros. Sometimes it is useful to have a single key stroke perform a function or multiple functions in your application. or select Edit – Commands… (Ctrl. Use the ampersand character (&) to do this. Some commands (such as Print) finish quickly and the next command can start. the commands in a macro are executed in the order in which they are listed. In the case of Set. From the Explorer. 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. 3. Close the ClientStartup macro. 2.

expand the Client Keys folder. the object key action will be carried out and the client key action will not. display keys and client keys. when the object has focus at run time and the key is pressed. This means. The ClientKeys dialog will open. However. Object and display keys are defined in the Graphics editor. 1. The order of precedence for key animation is: object keys. 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. 2. There are also object and display keys. Observe Pre-Configured Client Keys These commands will perform a refresh of your client. that if a key has object and client key definitions.Client Keys allow the operator to interact with the system at run time to do things like change displays or set tag values. Double-click on ClientKeys. They are active only when their associated object or display is. From the Explorer. object and display keys take precedence over client keys. Client keys are defined for an application. for example. They are enabled whenever the application is running on a FactoryTalk View SE Client. 3/10/2008 Page 54 of 160 .

2. Configure Client File The FactoryTalk View Client can be launched from FactoryTalk View Studio. The FactoryTalk View SE Client Wizard will open. Select the SE Client button on the tool menu. Type ‘AF07’ 5. all displays including docked displays will be closed. Select Local and 3/10/2008 Page 55 of 160 . Close the ClientKeys. When the Launch FactoryTalk View SE Client dialog opens select the New… button. Type ‘AF07’ for the name of the configuration file and click the Next button. Select the Local radio button and click the Next button. 4.On the release action of function key 5. Click the New… button. If prompted to save changes. 1. 3. 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. select the No button. 3.

6. select the ClientStartup macro as the Startup macro. select the ClientKeys key file as the Initial client key file. the area would need to be specified for the initial display. If you use a network application. and click the Next button. Select the AF07 application. leave the defaults. and click the Next button. Select AF07 7. Select the TankOverview display as the initial display. Select TankOverview Select ClientKeys Select ClientStartup 3/10/2008 Page 56 of 160 . Note: If you used parameters in the initial display. they would be specified in the Display parameters field.

Type ’AF07’ Check this Maximize Option 9. and The FactoryTalk View Client will start with the specified configuration. and 10.8. 3/10/2008 Page 57 of 160 . Leave the default to save configuration and open FactoryTalk View SE Client now and click the Finish button. and click the Next button. check the maximize window option. Leave the defaults for auto logout and click the Next button. Type ‘AF07’ for the title bar text.

Observe that it will not overlay the docked areas. or information about alarms. 4. that allow the operator to move among displays in an application. Drag the Tank Overview display to the lower edge or lower right corner of the client. always remain visible to the operator. 5. or sending information to a maintenance team. Control panels. therefore. Explore Docked Displays 1. allowing an operator to gain access to certain displays at all times. such as changing users. that contain standard buttons for special purposes. Click the restore button on the Tank Overview display. Headers or banners. you might consider docking: Navigational menus. They will. The header display contains an alarm banner and is located at the top of the client window.Run Client The AF07 application is now running in a FactoryTalk View SE Client window. The startup macro docked displays in 2 areas. 2. such as the current user’s name and area. Minimize the Tank Overview display. 3/10/2008 Page 58 of 160 . Drag the minimized title bar around to the edges of the display client: Top edge: Bottom edge: 3. the footer display contains navigation buttons and is located at the bottom of the client window. that provide specific information to the operator. closing open windows. Docked displays cannot be accidentally closed by the operator and cannot have other graphics placed on top. For example. Docked Displays At run time. graphic displays can be docked to an edge of the FactoryTalk View SE Client window.

Close the footer display 6. Notice how it is sized to fit in the main viewable area of the docked displays. 7. Select the F5 key (defined to close all displays and re-display the header and footer). The header and footer display are re-docked and the footer display no longer has the button called Remove ME!. 4. Move the Tank Overview display so the close button is visible and close the display. Observe that it will not overlay the docked areas and scroll bars will appear so the display will still be visible. 3/10/2008 Page 59 of 160 .6. 8. Go back to FactoryTalk View Studio 2. 8. Verify Client Keys 1. Go back to AF07 client. Select the Remove Me! Button and then select the delete key. 3. Select the Tank Overview button on the footer display to open the Tank Overview display. 7. Save the footer display 5. Open the Footer display. Observe that all displays are closed (including Tank Overview).

Click the Close Displays button display. Click on the buttons in the faceplates. Click the temp Dec C text Logix_PIDE display was actually used with 3 different parameters. . 5. Navigation from the footer display worked using a button object. Notice that 2 displays are opened.Test Navigation at Runtime 1. 4. Select the Tank Overview button on the footer display to open the Tank Overview display. Click on the agitator and then click on the valve What happened? The faceplate for the 2 State Device and Enhanced PIDE opened. in the lower right corner of the footer Remember that these navigation commands did not function when test running the display in FactoryTalk View Studio. The 2. 3. Observe that the Tank Overview begins to animate. 3/10/2008 Page 60 of 160 . Navigation worked using touch animation.

or you can browse for tags from an offline file. for example.Section 4: Tags (est. Close the Tags Editor. 3/10/2008 Page 61 of 160 . 3. time 5 minutes) In this section. For example. You can browse while online and connected to a device. From the Explorer. security. Direct referencing of device tags is a defining feature of Rockwell Automation Integrated Architecture. eliminating tag duplication and tag management. a tag can represent a process variable in a network device. 2. 1. double-click on Tags located under the HMI Tags folder. maintain. Indirect Referencing or HMI Tags Tags defined within FactoryTalk View are referred to as HMI tags. in addition to the root folder. in addition to the tag’s value. they provide additional properties for alarms. The Tag Browser shows the root folder of the application and folders containing the tags for the application’s HMI and data servers. 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. eliminating tag management. 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. 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. a controller program file. An application can use a mix of HMI tags and device tags. the Tag Browser also shows a folder for each area. This is where you can create. and remove HMI Tags. For a network application. and data manipulation. Tags added to the controller are available immediately without adding the tag to the HMI database.

Verify Communications.Create multiple reference objects in a display. where OPC servers can only be browsed individually. organized by areas. or traditional HMI tags can all be browsed within the same tag browser. the FactoryTalk Tag Browser was used to verify access to offline and online tags when we added tags to a numeric input control. OPC.0 servers in the application will be available from the FactoryTalk directory. 3/10/2008 Page 62 of 160 . In Section 9 Global Objects . This structure tag can be assigned to a faceplate object to supply values to multiple objects. In Section 1. you will browse for a structured tag of type PIDE and PIDE_Autotune. An advantage of FactoryTalk is that it provides an aggregate view of all tags from any data server. You would choose the tag name you want to use right from the FactoryTalk tag browser. This includes traditional HMI tags that are available through the tag browser that browses the FactoryTalk directory. So. or where an HMI tag database shows a flat list (non hierarchical) of all the tags in the system. in this example you see the areas (Plant Area 1. FactoryTalk View tags. Plant Area 2…). The tags in the directory can return references to ControlLogix tags. So. you can see the topic names provided by the OPC servers. and the tags within them. PLC tags (5/500). and third-party OPC server tags without the need to download or import the tags with an intermediary step. the online/offline control program. All tag names from all OPC 2. Within those areas.Areas found in FactoryTalk Directory Tags within selected folders appear on right. any RSLinx. and view the display. Contrast this to a traditional system. 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 information is served in a hierarchical fashion.

3/10/2008 Page 63 of 160 . the write value is merely overwritten as soon as the defined expression is evaluated again. A derived tag file consists of a number of derived tags and a maximum update rate for them. From the Explorer. double-click on Derived Tags located under the Logic and Control folder. Writing directly to a derived tag is highly discouraged because the tag value is determined by a given expression. This is where you can create. or string tag whose value is determined through the evaluation of an expression. mathematical and logical operations. An expression can be simply a tag name or it can be an equation made up of tag names. digital. If a derived tag is written to. The current value of a derived tag is written to the tag’s data source. 1. At runtime you can have multiple derived tag files active at once (up to 20 derived tag files. and remove your Derived Tags. special functions and If-Then-Else logic. 3. each containing up to 1000 derived tags).Derived Tags A derived tag is an analog. Close the Derived Tag Editor. 2. maintain.

the types of devices used in the application. you will learn about: Types of Alarming Systems o o o o FactoryTalk View SE Alarming (HMI tag alarm system) FactoryTalk Alarms and Events (centralized alarm monitoring) HMI Tag Alarm System Configuration FactoryTalk Alarms and Events Configuration Alarm Banner – design and runtime behavior Alarm Summary – design and runtime behavior Alarm Log Viewer – design and runtime behavior Alarm Status Explorer – design and runtime behavior Expressions FactoryTalk Alarms and Events Objects o o o o o Device-Based Alarms Tag-Based Alarms Alarming Alarms are an important part of plant control applications because they alert operators when something goes wrong. 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. Often. HMI tag alarm detection does not include FactoryTalk alarms. 3/10/2008 Page 64 of 160 . you can set up a complete alarm system. it is also important to have a record of alarms and whether they were acknowledged. HMI tag alarm data is not managed by FactoryTalk Alarms and Events services. where operators can view and acknowledge the alarms. If alarms are detected – tag values outside the configured limits . and you want to monitor these tags for alarms. you must use the HMI tag alarm displays and logs available in FactoryTalk View SE. the processes you need to monitor for alarms.notification is sent to connected FactoryTalk View SE clients. and whether you want to build alarm detection into those devices.Section 5: Alarming (30 – 40 minutes) About This Section In this section. Traditional HMI Tag Alarm System In FactoryTalk View Studio. An HMI tag alarm system only detects alarms set up for tags in an HMI server’s tag database. alarm monitoring occurs at the HMI server. To monitor and respond to HMI tag alarms. Use a traditional HMI tag alarm system if your application uses HMI tags for other purposes. The choices you make will depend on factors such as the design of your application. This is a traditional HMI tag alarm system. At run time. FactoryTalk View SE supports the existing traditional HMI tag alarm system and the FactoryTalk Alarms and Events system.

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, systemrelated 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 65 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 66 of 160

FactoryTalk Administration Console FactoryTalk Alarms and Events 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. Import and export for tag-based alarms. Create database definitions for logging historical alarm and event messages. Organize securable actions into groups. 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. Create and configure displays with alarm objects (Banner, Summary, Log Viewer, Status Explorer). Test displays with alarm objects. 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). Configure the alarm log set up. Import and export for HMI alarm tags. Configure alarm tags and conditions for the alarms. Suppress, unsuppress, and view suppressed alarms. View alarm logs. Create and configure displays with Tag Alarm Summary object. Test displays with Tag Alarm Summary object (Note: this can only be done in FactoryTalk View Client). No Yes

FactoryTalk View Administration Console

FactoryTalk View Studio

Yes

Yes

Yes

Yes

Yes

Yes Yes Yes

Yes Yes Yes

Yes Yes Yes

Yes No

Yes No

Yes Yes

No

No

Yes

No

No

Yes

Yes

Yes

No No No No No No

Yes Yes No Yes Yes No

Yes Yes Yes Yes Yes Yes

No

No

No

3/10/2008

Page 67 of 160

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.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. or by selecting the HMI Tag Alarm Summary button on the tool menu Library objects are located in HMI Tag Alarm Information library display HMI Tag Alarm Log Setup. HMI Tag Alarm Log Viewer. and Tag Import and Export Wizard are located under the Tools menu: 3/10/2008 Page 68 of 160 .

Log Viewer. 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. 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 69 of 160 . This was done in Section 1 – Add a data server. Summary. and Status Explorer are located under Objects > Alarm and Event > Banner. Summary.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). Log Viewer. Banner. 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. 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.

double-click on the Header display to open it. Double-click on the Alarm and Event Banner Design View object in the display 3/10/2008 Page 70 of 160 . From the Explorer. 2. Select a row in the Banner and click on the run alarm command on a row in the Banner. you added a summary object on a display and performed a test display to verify that you were getting alarms. Run Time 1. Close the displays. A display should be launched for that alarm. Click on the Display the Alarm and Event Summary 6. Design Time button. embedded in a FactoryTalk View graphic display. 5. to monitor and respond to the most serious alarms requiring immediate attention. 4. 7.FactoryTalk Alarm and Event Objects Preconfigured displays have been added to your HMI project for all of the FactoryTalk Alarm and Event objects. Alarm and Event Banner (Header display) Use the Alarm and Event Banner object. observe the header display that contains the Banner object. button or double-click 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. From the AF07 client. 3. An Alarm Summary should be displayed. You should have FactoryTalk View Studio and Client opened. In Section 1 – Verify Communications. you will observe all of the FactoryTalk Alarm and Event objects in design and runtime. 8. In this section.

9.and the Alarm and Event Banner Properties will open. 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 71 of 160 . Click on each tab to look at all the properties.

Observe that the list and count are updated in the Summary. 4. 3/10/2008 Page 72 of 160 . Click the Tank101 Summary button in the footer display. Close the Header display in FactoryTalk View Studio when you are done. 8. click the Summary button in the footer display. 2.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. filter. 10. The Alarm Summary display is opened. and sort alarms during run time. to acknowledge. 5. suppress. 11. Select a row in the summary list to see details about the alarm. 3. embedded in a FactoryTalk View graphic display. Run Time 1. 7. disable. Alarm and Event Summary (AlarmSummary and TankAlarmSummary displays) Use the Alarm and Event Summary object. 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. Select a predefined filter called Pump or Tank101 from the drop down list 6. Notice that only alarms for Tank 101 are displayed and there is no way to modify the filter at runtime. From the AF07 client. Mouse over the toolbar on the Summary to see what the configured buttons do (read the tool tips).

10. You should now see alarms. Click the Tank Overview button in the footer display. These filters were preconfigured using the Alarm Class field that was configured for the alarm. From the Explorer. 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. Sort Configure sort order 3/10/2008 Page 73 of 160 . Click on each tab to look at all the properties. double-click on the AlarmSummary display to open it. If you don’t see any alarms in the Tank101 Summary. 12. 13.9. Double-click on the Alarm and Event Summary Design View object in the display and the Alarm and Event Summary Properties will open. Design Time 11. Enter ‘100’ in the input field next to the Manual Valve Opening Slider object. Click the Tank101 Summary button in the footer display.

3/10/2008 Page 74 of 160 . 21. 2. Even if the filters option is enabled at runtime only the alarms beginning with [SoftLogix]Program:Tank101 can be filtered. Select a predefined filter called Pump or Tank101 from the drop down list 6. Close the TankAlarmSummary display. Observe that the default filter is set so that Normal and Unacknowledged alarms do not appear in the TankAlarmSummary. Observe that this Summary object is only subscribing to alarms where the event source begins with [SoftLogix]Program:Tank101. Double-click on the Alarm and Event Summary Design View object in the display and the Alarm and Event Summary Properties will open. 18. to view and filter historical alarm information stored in Microsoft SQL Server databases. 16. Mouse over the toolbar on the Log Viewer to see what the configured buttons do. Close the property page. Close the property page. 15.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. 3. Run Time 1. 19. click the Log Viewer button in the footer display. 5. Go to the Filters property page. Click the Event Subscriptions tab. Close the AlarmSummary display in FactoryTalk View Studio when you are done. 4. Select a row in the list to see details about the alarm. The AlarmLogViewer display is opened. Open the TankAlarmSummary display 14. Alarm and Event Log Viewer (AlarmLogViewer) Use the Alarm and Event Log Viewer object. embedded in a FactoryTalk View graphic display. 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. 13. Observe that the list and count are updated in the Log Viewer. 17. From the AF07 client. 20.

3. Mouse over the toolbar on the Status Explorer to see what the configured buttons do. 2. click the Status Explorer button in the footer display. 2. 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. Select a row in the list and select the show details for selected alarm 3/10/2008 button from the toolbar. These filters were preconfigured using the Alarm Class field that was configured for the alarm. Click on each tab to look at all the properties. 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. The AlarmStatusExplorer display is opened. embedded in a FactoryTalk View graphic display. 5. Close the AlarmLogViewer display in FactoryTalk View Studio when you are done.Design Time 1. 4. Alarm Status Explorer (AlarmStatusExplorer) Use the Alarm Status Explorer object. to enable or disable alarms and suppress or unsuppress alarms. From the Explorer. double-click on the AlarmLogViewer display to open it. From the AF07 client. Page 75 of 160 . This is a historical view of what is in the log (database). Run Time 1. 3. 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. 4. Notice that there is not an Event Subscription tab.

3/10/2008 Page 76 of 160 . Observe the list is filtered to show only alarms that contain tank101. 10. From the Explorer. 6. 2. Type ‘*tank101*’ in the name field for the Alarm source filter and click the Apply Filter button.5. Nothing happens. Click on a column header to see the list sort by that column. 11. Click the suppress column until the suppressed alarms appear at the top of the list. You must rightclick on the object and then select the Properties… context menu item. Click the Cancel Filter button 12. 7. Double-click on the Alarm Status Explorer object in the display. Select a couple of rows and then click the suppress button. Observe the list shows all alarms. 8. double-click on the AlarmStatusExplorer display to open it. Select all the suppressed alarms and then click the unsuppress button. 9. Design Time 1.

Feel free to make configuration changes and perform a Test Display. FactoryTalk Alarm and Event Expressions There are new FactoryTalk View SE expressions that interact with the FactoryTalk Alarms and Events Services. the Alarm Status Explorer Properties will open.Now.number of Normal and Unacknowledged alarms Run Time 3/10/2008 Page 77 of 160 . 3.highest severity of unacknowledged alarms AE_InAlmAckedCount(AlarmName) .number of In Alarm and Acknowledged alarms AE_InAlmUnackedCount(AlarmName) .highest severity of acknowledged alarms AE_HighSeverityUnacked(AlarmName) .number of In Alarm and Unacknowledged alarms AE_NormalUnackedCount(AlarmName) . Close the AlarmStatusExplorer display in FactoryTalk View Studio when you are done. 4. This FactoryTalk Alarm and Event function returns this value: AE_HighSeverityAcked(AlarmName) .

click the TankOverview button in the footer display. The alarm indicators should be changing colors. This should trigger some alarms. double-click on the TankOverview display to open it. The alarm indicators should change colors. Observe the alarm indicators 4. If they are not. Open the Object Explorer by selecting the View – Object Explorer item from the menu. From the AF07 client. 2. Slide it back down to about 20 and then wait. slide the Manual Valve Opening up to about 90 and then wait a few seconds. 2. Design Time 1. 3.1. The TankOverview display is opened. 3. From the Explorer. Expand the Indicator_Group in the Object Explorer. 3/10/2008 Page 78 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 79 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 o The input value equal to one 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 o o o High High (HIHI) High (HI) Low (LO) 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 o Rate of Change Positive (ROC_POS) 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 80 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 to have 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 81 of 160

3/10/2008 Page 82 of 160 . 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. 4. close or hide it. 3. 2. Go online with the controller by selecting the Communications > Go Online menu item. If the Connected To Go Online dialog appears. It will take a few seconds for RSLogix 5000 to start and open to the routine. select the Upload button. Open RSLogix 5000 1. the FactoryTalk View command to open RSLogix 5000 will appear in the diagnostic list. do the following. If the Quick Start page appears.Observe Configured Alarms in Logix 5000 If you would like to take a look at the alarms that have been configured for this lab. Navigate to the Tank101 routine if you are not already there (double click to open).

Change to sheet 2 of 3.View Digital Alarm 1. 3/10/2008 Page 83 of 160 . Click on the … next to the ALMD to open the property pages. At the bottom of the Cascade Temperature Loop worksheet you should see the ALMD instructions. View Digital Alarm 1. Observe the Configuration properties for the ALMD instruction 3. 2. Close the dialog when you are done.

Click on the … next to the ALMA to open the property pages. At the bottom right of the Level Simulation worksheet you should see an ALMA instruction.2. Observe the Configuration and Messages property pages for the ALMA instruction 3/10/2008 Page 84 of 160 . 3.

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 85 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 o o Users and User Groups Commands 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 86 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 87 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 88 of 160

Operators will appear under User Groups in the Explorer. The New User dialog will open. check the user cannot change password. and type ‘password’ for the password. Type ‘Tank101Operator ‘ Select User cannot change password Select Password never expires Type ‘password’ Type ‘password’ Click the Create button Confirm the fields. You will be back at the Select User or Group dialog. Click the Create button. check the password never expires.7. 3/10/2008 Page 89 of 160 . 11. 8. You will be back at the New User Group dialog. Click the Create button. Type ‘Tank101Operator’ for the user name. Tank101Operator should be in the Members list: 10. Select the Tank101Operator and click the button. 9.

Check the Deny check box next to Alarming and check the Allow checkbox next to Acknowledge. The Select User or Group dialog appears. FactoryTalk Administration Console allows you to configure security for the System folder and its contents. In addition to a set of common actions that apply to most FactoryTalk products. applications. From the Explorer. and many other items. Select the Operators and click the OK button. 3/10/2008 Page 90 of 160 . and then configure security for the grouping in one step. Each FactoryTalk product defines its own set of resources. For example.Configuring Action Security When setting up security. actions can only be performed from the local computer — the FactoryTalk Local Directory does not contain any computer accounts. They can not perform the other actions. Security Settings for AF07 dialog appears. Let’s specify that our operators can not perform certain alarming actions. For information about those actions. expand the Alarming action. Action An organized activity performed on a resource in order to accomplish an objective. areas. 3. 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. While the Operators group is selected. Resources The objects in a FactoryTalk system for which actions can be secured. Click the Add… button. 4. Do not confuse resources with resource groupings: resource groupings allow you to group together control hardware represented in the Networks and Devices tree. Other products might allow you to configure security for logic controllers and other devices. each product can also include its own set of actions. 1. You are only allowing the operators to acknowledge FactoryTalk Alarm and Events Alarms. some products might allow you to configure security for resources such as servers in an area. Actions are grouped into categories. right-click on AF07 and select the Security… context menu item 2. see Help for the FactoryTalk product. In a FactoryTalk Local Directory.

select the Yes button. 5. Click the OK button. When prompted with this message.Your dialog should look like this. 6. 3/10/2008 Page 91 of 160 . The Security Settings for AF07 dialog closes.

3. While it is highlighted. or HMI tag. The Runtime Security dialog is opened. (Secured HMI components are those that have been assigned security codes. Assign Security Codes to Users and User Groups 1. The Select User and Group dialog is closed and the Operators group is added to the Users list. 6. button. graphic display. Select the Deny checkbox for A. Select the Add… button.Configuring Runtime Security After you have created users and user groups in FactoryTalk Security. The Select User and Group dialog is opened. Double-click on the Runtime Security icon in the Explorer Or Select the Settings > Runtime Security…. 3/10/2008 Page 92 of 160 . 8. 2. Click on the Security Accounts… 4. you add them to the security accounts list in the Runtime Security editor in FactoryTalk View SE. The Security Settings for AF07 dialog is opened. 7. 5.) These codes (A through P). menu item. along with those assigned to HMI project components. OLE object verb. determine which components a user has access to at run time. macro. and then assign that code only to the users who are supposed to have access to the component. To restrict access to a command. you assign a security code from A through P to it. you also assign the security codes that will give them access to secured HMI components. Select the Operators and click the OK button. When you add an account. expand the FactoryTalk View Security Codes actions.

3/10/2008 Page 93 of 160 . 9. When prompted with the message “Save changes to document?” Select the Yes button. When prompted Select the Yes button. 13. Click the OK button.Your settings should look like this. 11. The Runtime Security dialog closes. Select the Close button on the Runtime Security dialog 12. 10.

4. Open the AlarmStatusExplorer display from the Explorer. Click the … button next to the Command field. The Runtime Secured Commands dialog is opened. The Runtime Secured Commands dialog will close. The Command Wizard is opened. Click the Cancel button on the Command Wizard. 1. 5. Click the Close button on the Runtime Secured Commands dialog. 2. Observe all the commands that can be assigned security codes. When prompted with the message “Save changes to document?” select the No button. 8. Click in a cell in row 2 to select it. Assign Security Codes to Displays You will assign the A security code to the AlarmStatusExplorer display. 9. Select the Settings > Runtime Secured Commands… menu item. 3. 11.Assign Security Codes to Commands 1. Observe the Security Code drop down list that can be used to assign a security code to a command. 3/10/2008 Page 94 of 160 . 6. Expand the window to see all the fields. 10. 7.

Close the display.2. Select the Edit > Display Settings… 3. The information message “User tank101operator has been logged in. 6.” will appear in the diagnostics list. 7. Select the A from the Security Code drop down list. First you will try to suppress it from the Alarm Status Explorer display. menu item. You will login in as the tank101operator and then try to suppress an alarm. Let’s see what happens. 1. 3. Login as the new user ‘Tank101Operator’ using the password of ‘password’. 5. and then finally you will try to suppress it from the Summary display. Verifying Security Settings In this section you will verify your security settings with the client. The Display Settings dialog will open. 4. Note user name is not case sensitive. then from the Tank101 Summary display. Click the OK button. Go to the AF07 client 2. 4. Save the display. Click the button on the footer display. Your attempts should fail because of the security settings. 3/10/2008 Page 95 of 160 .

click the suppress button to confirm that you want to suppress the alarm. 14. The message will appear in the diagnostics list. 12. The operator can not suppress the alarms from here. But what do you see? There is a suppress and an Alarm Status Explorer button.5. Click in the button in the footer display.” will appear in the diagnostics list. Observe there isn’t an icon for the Alarm Status Explorer in the toolbar. button in the footer display. 9. Click on the button. 10. The display setting security worked! 7. 13. 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. Notice the suppress button is not displayed in the toolbar. This display didn’t hide the buttons from the operator or secure the display from the operator. The Tank101 Summary display was configured for operators and actions that should not be performed by operators were hidden from the toolbar. 11. 6. Click on the 8. What happened? Nothing! The message “Currently logged-in user does not have security access to AlarmStatusExplorer. If the message dialog appears. The actions security worked! 3/10/2008 Page 96 of 160 . click the OK button. The Tank101 Summary is displayed. Select a row (alarm) in the summary list and click on the suppress button. If the option to display errors from operator action in a dialog was checked when configuring the summary (which it was originally). When the Suppress Alarm dialog comes up. So far so good! It is looking pretty secure here. Note: If you don’t see these buttons you may have changed your configuration in the Alarming section. a dialog with the message will appear. So the operator can not get to the Alarm Status Explorer from here. The Alarm Summary is displayed.

15. This is because it is not the same as the display that we configured a security code on. The alarm will be acknowledged because the tank101operator has permission to perform that action. 22. Perform some of the steps above. he still could not perform actions that he didn’t have permissions for. 20. The actions are secured and the operator can not perform them. Right-click on an alarm in the summary and select one of the Ack context menu items. You should be able to open the Alarm Status Explorer from the footer display and perform all actions on the alarms. 17. 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. Click the button on the footer display. What happened? The Alarm Status Explorer dialog opened. 3/10/2008 Page 97 of 160 . unsuppress alarm) to try to perform these actions. Observe what happens. 16. Close the Alarm Status Explorer 19. 18. suppress alarm. Select an alarm in the list and then click on each of the first 4 buttons (enable alarm. 21. disable alarm. Login as administrator using the password of rockwell 23. Click on the Alarm Status Explorer button.

you create a data log model and specify the tags that are to be logged. flexible run-time control. and print chart data. time 20 min) About This Section In this section. toggle between isolated and nonisolated graphing.Section 7: Data Logging and Trending (est. or chart. Runtime Exploration Data Logging Data logging is a FactoryTalk View component that collects and stores tag values. To have a permanent record of tag values. An application can have up to 20 data log models running at a time. they’re not HMI (or memory) tags stored on the server itself. Remember: controller tags will keep their value when an HMI server is powered down because they’re located within the controller. When the HMI server is turned off. You specify which tag values to collect. and where to store them by defining a data log model.000. when to collect them. log them to the data log file on disk. You can add pens. Pens on the run-time chart represent data from the tags and expressions that you add to the trend object. plot one variable against another in XY plots. The values themselves are stored on a given HMI server. This is done in the Data Log Model editor. The HMI tag database does not store actual tag values. The values can also be logged to an ODBC-compliant database. the value table is cleared (excluding retentive tags). To log tag values to disk. The trend object provides extensive. 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. The maximum number of tags that can be logged by one data log model is 10. specify unique line settings. it only defines which values are to be collected. 3/10/2008 Page 98 of 160 . The trend object displays real-time data and historical data from the FactoryTalk View Site Edition data logs. of current or historical tag values. A trend provides operators with a way of tracking plant activity as it is happening. Trending A trend is a visual representation.

4. This will allow the user to browse through a timeline to look at the data over a given period of time. 7. Viewing a Trend 1. Look at the two error messages and an information message: There was an attempt to connect to an ODBC data source that failed. Click the Start button. Click the Data Logging 3. - Runtime trending o A Runtime trend displays data trends directly from the processor. 8. 5. Click the 3/10/2008 button in the footer display Page 99 of 160 . Go to the AF07 client 2. You will take a look at why this happened in the configuration section. Notice the messages that appear in the diagnostics list 6.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. Tank101 is logging to a secondary path that is a file. The Tank 101 Data Logging Trend will be displayed. button from the footer display. The trend will start trending its runtime data from the time it’s first loaded on the display. Notice the trend starts to update.

15. Wait about 20 seconds. 14. 2. From the Explorer. Wait about 20 seconds. 10. Slide the Manual Valve Opening Slider about half the way down. Note the HMI Time in the header. This means that the trend reads both Real-time data (occurring now) and Historical data (read from data log files). Observe the trend. Find the HMI Time that you noted if it is not visible by using the buttons under the trend. Click the Data Logging button from the footer display. Configuration Exploration Data Log Models 1. navigate to AF07 > Data Log > Data Log Models > Tank101. 13. Slide the Manual Valve Opening Slider to the bottom. Double-click on Tank101 3/10/2008 Page 100 of 160 . The trend displayed is configured to display historical data. Wait about 20 seconds or until the Level is OK.9. Slide the Manual Valve Opening Slider about half the way down. 12. Slide the Manual Valve Opening Slider to the top. 11.

select Administrative Tools. There is a System Data Source Name (DSN) called FactoryTalk that points to a SQL Server Express database called FactoryTalk. Select the Start > Settings > Control Panel menu item. If you want to see how the System DSN was configured. There is a database and a pointer to the database but the tables to store the data have not been created. Look at the System DSN tab and the DSN called FactoryTalk. Click the Create Tables button. 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.3. This was done to demonstrate what happens when the connection to the database fails and there is a backup path enabled. An ODBC System DSN stores information about how to connect to the indicated data pointer. The data log model can be configured to be stored as a file set or an ODBC database. From the Control Panel. 3/10/2008 Page 101 of 160 . 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. Notice that this data model is being stored in an ODBC database. Click the OK button. This is a pre-configured System DSN pointing to a database that is called FactoryTalk. and then select Data Sources (ODBC). 4.

you will want to store the logs to one common location instead of on each individual HMI server on the network. Notice Enable ODBC Backup Path is enabled. Notice that he Enable ODBC backup path was selected and a logging path was specified. The tables are created and the connection should be successful now. 6. This is why you were able to see the historical data in the trend display even though the connection to the ODBC failed. 3/10/2008 Page 102 of 160 . and notice the settings. 7. This configuration tab is used to set the file location of the data logs. Click the Log Triggers tab This configuration tab is used to decide how often and based upon what event the log should be updated.5. 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. SwitchBack is set to 10 minutes. At some point you will see messages like Click the Advanced button. Click on the Paths tab. This is useful if you have a distributed network set up.

3/10/2008 Page 103 of 160 . Trigger is On Change Heartbeat of 2 minutes 8. Click the Pens tab. From the Explorer. Double-click on the grid of the Trend object. Click the OK button to close the Tank101 Data Log Model dialog Configuring Trends Do not add a new trend or change this one. 10. 9. Click the Tags in Model tab This configuration tab is used to select what information is logged. The Trend Properties dialog will open. 4. You can add or remove different tags from this menu using the tag browser. 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 TankDataLogging display to open it.Notice that the trigger for logging is On Change. 1. You can do so at the end of this section. 3. Notice 6 tags have been added to the model.

Close the TankDataLogging display. Notice that the Model column has Tank101 which is the data model that was created. Then the OK was clicked to accept the changes. The Configure Tags dialog opened. 12. If prompted to save changes. Click the Cancel button to close the button properties. This command DataLogOff Tank101 stops the data logging for the model. 13. 9.5. Click the Cancel button on the Trend Properties dialog to close the dialog. Click the Action tab and look at the Release action. The Add All button was selected to add all the tags. select the No button. Click the Action tab and look at the Release action. 11. 6. These pens were added by selecting the Add Pen(s) from Model button. 10. Double-click on the Start button to open the button properties. 3/10/2008 Page 104 of 160 . 7. 8. Click the Cancel button to close the button properties. This command DataLogOn Tank101 starts the data logging for the model. Double-click on the Stop button to open the button properties.

3. Expand Options 3/10/2008 Page 105 of 160 . Click the Options >> button. Click Connections Properties Options 3. 4. 2. Microsoft SQL Server Management Studio Express will open and you will be prompted with a Connect to Database Engine dialog. Open the SQL folder. Type ‘FactoryTalk’ in the Connect to database field. Double-click on the ViewTank101DataLog. Click the Connect button 1.Querying Logged Data A view was created in the database to allow you to query the data log. Select the Start > Lab 15 FactoryTalk View SE menu item. Open the C:\LabFIles\ Lab 15 FactoryTalk View SE folder if it isn’t already opened. Click the Connection Properties tab. Click the Connect button. Type ‘FactoryTalk’ 4. 2.sql file. 1. Do the following to view the data log.

it should have. 16. 18. The Tank Overview will be displayed. button. 15. Slide the Manual Valve Opening Slider to the top. Wait about 20 seconds. Click the 12. Once you are connected. 8. Click the Execute button. 13. 20. 21. Did the row count change? Have we gotten any new rows? We are only logging on change. Note the HMI Time in the header. click the Execute 6. The Tank 101 Data Logging Trend will be displayed. Go back to the 19. Scroll to the bottom of the list and notice the number of rows. Go to the AF07 client 11.5. Scroll to the bottom of the list and notice the number of rows. 17. Query window. Click the Data Logging 23. Slide the Manual Valve Opening Slider to the bottom. Scroll to the bottom of the list and notice the number of rows and the Data and Time. Wait about 20 seconds. button from the footer display. Slide the Manual Valve Opening Slider about half the way down. Slide the Manual Valve Opening Slider about half the way down. 7. Wait about 20 seconds or until the Level is OK. 9. button in the footer display 14. Did the row count change? Are we getting new rows? Yes. Go to the AF07 client 22. Click the Execute button. 10. 3/10/2008 Page 106 of 160 . Results will appear in the window.

Wait about 20 seconds. Wait about 20 seconds. 30. 25. 31. Note the HMI Time in the header. Scroll to the bottom of the list and notice the number of rows. 36. Slide the Manual Valve Opening Slider about half the way down. Query window. Notice the messages that appear in the diagnostics list 26. Click the Stop button. Slide the Manual Valve Opening Slider about half the way down. Close the Microsoft SQL Server Management Studio Express. Click the 28. 33. Click the Execute button. Go back to the 34. Slide the Manual Valve Opening Slider to the top. Notice the trend is still being updated. 3/10/2008 Page 107 of 160 . Wait about 20 seconds or until the Level is OK. button in the footer display 29. If prompted to save changes. Slide the Manual Valve Opening Slider to the bottom.24. 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. 35. 27. 32. select the No button.

and also generate a series of communication messages classified as Operator-Warning. Engineer. You can view both local messages and messages retrieved and merged from logs on multiple computers. Warning. The FactoryTalk Diagnostics service includes a Diagnostics Setup editor. and Secure). "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. When you set options for a particular logging destination. FactoryTalk Alarms and Events. and a Local Log on each computer where the FactoryTalk Services Platform is installed. 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. time 20 min) About This Section In this section. The Diagnostics List is intended to show messages as they occur. and Developer-Error. Diagnostics information can be displayed in the Diagnostics List or in the FactoryTalk Diagnostics Viewer. Engineer-Warning. and Audit) together with Audience options (Operator. Messages displayed in the Diagnostics List are not time stamped. the FactoryTalk AssetCentre software product provides customized FactoryTalk Audit Logs. For example. a Diagnostics Viewer. the options you choose affect the log on this computer that any number of FactoryTalk products may be using.Section 8: FactoryTalk Diagnostics Setup and the Viewer (est. the filtering options you choose affect the types of messages routed from all FactoryTalk products that send messages. For example. Each FactoryTalk product and service categorizes the messages that it generates using a matrix of Severity options (Error. Information. FactoryTalk View SE. Developer. when you configure message routing options. and other FactoryTalk software products are all sending messages to one Local Log and to one FactoryTalk Audit Log on one computer. The Diagnostics Viewer provides a way to retrieve messages 3/10/2008 Page 108 of 160 . Other custom logging destinations are also available. Use the Diagnostics Viewer to review diagnostics messages. Likewise. a product might generate a series of security messages classified as Operator-Audit and Operator-Information. you will learn about these topics: FactoryTalk Diagnostics Diagnostics List Diagnostics Viewer Diagnostics Setup o o o Configuring the FactoryTalk View Diagnostics List Configuring the Local Log ODBC Database as a message source About FactoryTalk Diagnostics The idea behind FactoryTalk Diagnostics is to answer the question.

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. or View Administration Console) starts new messages begin to get logged to the list. When the Diagnostics Viewer window is open. 2. On the General tab of the Properties dialog. 3. Select the View > Options… menu item. From Explorer. Old messages will be removed from the list as new ones come in and the message limit has been reached.after they occurred. FactoryTalk View SE Client. Removing a message from the Diagnostics List does not delete the message from the Diagnostics log. select the Tools > Diagnostics Viewer… menu item Or select the Start > Diagnostics Viewer menu item. press the F5 key or click the Refresh button. You have used the FactoryTalk View Diagnostics List in earlier sections of this lab. new messages do not appear automatically. make sure message source is set to Local Log. New messages do not appear in the Diagnostics Viewer. and FactoryTalk View Administration Console window. Filter Diagnostics List 1. the list is cleared. removing a message from the View Studio window does not remove it from the View Client window. Removing a message from one Diagnostics List does not remove it from another Diagnostics List. When the application (View Studio. I. Open the Diagnostics Viewer 1.e. 3/10/2008 Page 109 of 160 . View Client. Diagnostics List The Diagnostics List can be displayed in a FactoryTalk View Studio window. Mouse over the toolbar and look at the menus to see the operations you can perform with the Diagnostics Viewer. To refresh the view and reload messages. 2. When the application is closed.. 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. 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. The FactoryTalk Diagnostics Viewer will open.

Observe the list was updated but no messages appear in the list. 6. Select the Audience = ‘Developer’ 2. Click on Apply from the Properties dialog. Move the Properties dialog so that you can see 3. Click on Apply from the Properties dialog. Select Equals 4. Select the Audience 5. Select Developer 2. Select Operator 5. Observer the list was updated to only show messages that were created with the audience set to operator. 8. 3/10/2008 Page 110 of 160 . 1. Select the OK button 7. 5. 1. Select Equals 4. Click the Add Where Condition…) button 4.tab on the Properties dialog. Click the the items in the Diagnostic Viewer. Select the OK button 3. Click the Modify… button 3.

Click the Add Where Condition…) button 11. From the Tools menu. The FactoryTalk Diagnostics Configuration dialog will open 3/10/2008 Page 111 of 160 . Diagnostics Setup Open the Diagnostics Setup 1. Run the Diagnostics Setup from within the FactoryTalk View Studio. Click on OK from the Properties dialog. Create a message filter. Take a look at the diagnostics setup to see why you didn’t see any developer messages. 1. 13. Select the Audience = ‘Operator’ select records where condition and click the Remove button. Select the OK button 2. 10. select the Diagnostics Setup… menu item 2. Select Contains 4. 12.9. Observe the list was updated to only show messages that contained the string tank101. Close the Diagnostics Viewer. Type ‘tank101’ 5. Select the Message 3.

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.3. 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. The destination is the Diagnostics List which is managed by FactoryTalk View. Warning. and Info appeared in the FactoryTalk View Diagnostics List. Look at the Destination Setup and the Message Routing configuration to see what messages got routed to the FactoryTalk View Diagnostics List. Expand the Destination Setup 4. Notice that there aren’t any configuration settings. Look at the configuration. Expand the Destination Setup. select the FT View Diagnostics List item. 2. 1. Configuring the Local Log You just used the Diagnostics Viewer to look at the local log. 3/10/2008 Page 112 of 160 . Click on each item and look at the settings.

1. and an option to clear the log. Select the Destination Setup > Local Log item The local log is a file that exists on this computer. 2. There are options for overwriting events. 3/10/2008 Page 113 of 160 . 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. log size.

Click the Apply button. FactoryTalk Diagnostics can also route these messages to other centralized logging destinations.3. Check all the options in the Developer row. ODBC Database as a Message Source Depending on the products you have installed and the configuration options you have set. Notice 2 messages in the diagnostics list got updated. 6. To send messages from multiple computers. click the clear all button in the Diagnostics List. 9. 10. such as an ODBC database or FactoryTalk Audit Log. Use the ODBC Database Destination Setup window to send messages to an ODBC data source. 8. 7. 4. Notice that they are developer messages one is of type audit and the other is of type information. Type ‘75’ in the Manual Valve Opening input field and select the enter key. Go to the AF07 client. 5. configure the destination on each computer where the FactoryTalk Diagnostics service is installed. Select the Start > Diagnostics Viewer menu item. Change the Message Routing for the Local Log to include all message types for the developer audience. 3/10/2008 Page 114 of 160 . Select the last 2 messages in the list to look at the details. Click on the Tank Overview button.

appear in the Local Log on the computer where the product is installed. Even if you create the additional fields manually. or the severity type set to Audit. You will use a System DSN called FactoryTalk that has been configured to point to a MS SQL Server Express database called FactoryTalk. Select the Destination Setup > ODBC Database item. Browse 3/10/2008 Page 115 of 160 . however. This includes: any additional database fields not included in the ODBC table format.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. nothing will be logged to them. The additional information logged by a FactoryTalk product will. 2. Configure the ODBC Database Setup 1. Secure messages can only be logged by the FactoryTalk AssetCentre software product to the FactoryTalk Audit Log. that a FactoryTalk product might use. Go to the Diagnostics Configuration You are going to configure the destination setup. any messages where the audience type is set to Secure.

Type ‘FTDiagnostics’ for the target table and click the Create Table button. Select the System Data Source tab Select the FactoryTalk Data Source Name 4.” 3/10/2008 Page 116 of 160 . Click the OK button. Click the OK button when you get the message that “The table FTDiagnostics was successfully created. Type ‘FTDiagnostics’ Click the Create table button 6.3. Click the FactoryTalk data source name. click the System Data Source tab. Click the … button next to the data source name. 5. When the Select Data Source dialog opens.

Click on the Tank Overview button. 14. 9. View the ODBC Log 10. 18. 12. 19. 13. Click the ODBC Database as the message source. 8. Notice a download message is logged in the Diagnostics List. Move the Properties window so you can view the list. Click the OK button. Type ‘85’ in the Manual Valve Opening input field and select the enter key. Notice the list is empty because nothing has happened since we created this destination. Go to the Diagnostics Viewer 11. Wait 30 seconds. Check all the options in the Developer row. 16. click the refresh button. Click the OK button.7. 17. 15. Select the View > Options menu item. Select the Message Routing setup and then select the ODBC Database. Change the Log message to database every setting to be 30 seconds. 3/10/2008 Page 117 of 160 . click the clear all button in the Diagnostics List. Go to the AF07 client. Notice that Audit messages can not be routed to the ODBC destination. Go to the Diagnostics Viewer 20.

22. If you queried the database. Notice that 2 messages got logged. Close the Diagnostics Viewer window. 3/10/2008 Page 118 of 160 .21. you would see it has been updated 23.

and still be able to be updated with changes to other aspects of the base global object. or refreshed by closing and reopening them. 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. This means each reference object can have a unique data source(s). 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. 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. 3/10/2008 Page 119 of 160 . you will learn about: Global Objects Create multiple reference objects in a display. meaning it happens at runtime on the client. you create global object displays in the Global Objects folder. Global objects are created on global object displays. you saw that the TankOverview display had one touch animation on the TankCoolingTemp_Group that opened two Logix_PIDE display for different loops. the same way you create standard graphic displays in the Displays folder. and view the display Using Global Object Parameters Reference Object Properties Modifying a global object. time 30 min) About This Section In this section. 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. Parameter passing is dynamic. The Logix_PIDE display contains reference objects to the Logix_PIDE base global object. You will use the parameter values to specify which PIDE loops you want to view and animate.Section 9: Global Objects (est. you will create a new display and use the base Logix_PIDE global object to create two reference objects on that display. In FactoryTalk View Studio. 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. In this section of the lab.

Minimize the Logix_PIDE global object. drag and drop it on the new display. Create a reference object on your new display – Single-click on the global object to select the faceplate. 7. select the New context menu item. 6. From the Explorer. Position the reference object in the upper left corner of the new display. Duplicate the 1st reference object – Right-click on the reference object and select the Duplicate context menu item OR perform a copy and paste. Open the Logix_PIDE global object . 4. Doubleclick on Logix_PIDE 3. 3/10/2008 Page 120 of 160 .Expand the Global Objects folder in the Explorer.Create New Display 1. Position the 2nd reference object next to the first one. create a new display – Right-click on Displays. 8. 2. Resize the display so window edges line up with faceplate edges. 5.

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. Notice that there is a description for the #1 and #2 parameters. The PIDE_Autotune is not required. The Global Object Parameter Values dialog is opened. 3/10/2008 Page 121 of 160 .9. You will be looking for structured tags of type PIDE and the PIDE_Autotune.

The #1 and #2 parameter values should be entered for the Tank101 . 12. Assign structured tags for #1 .Click on the … button under the Tag column for #1. This help you navigate more quickly.ProductTempAtune Notice that this time when the tag browser is opened you are positioned at the tag you previously selected (::[SoftLogix]Program:Tank101.ProductTempLoop).10. Repeat the above step for #2 using ::[SoftLogix]Program:Tank101.ProductTempLoop 13. 3/10/2008 Page 122 of 160 . When the Tab Browser opens navigate to ::[SoftLogix]Program:Tank101.ProductTempLoop Click the OK button 11. Click the OK button on the Global Object Parameter Values dialog.

14.JacketTempLoop #2 is assigned ::[SoftLogix]Program:Tank101. Assign these structure tags #1 is assigned ::[SoftLogix]Program:Tank101. 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.JacketTempAtune 15. 3/10/2008 Page 123 of 160 . Repeat the 5 previous steps. steps 9 – 13 for the 2nd reference object.

Remember there are 2 loops in your display. But first you need to launch the display. this global object uses parameter placeholders and even though we set the values they are ignored. literal numbers and strings in the embedded variable syntax. However. Remember. and display of right-most characters in embedded string variables. You can use the test display mode to test global objects. What happens? Lots of failed to resolve messages. Now you will have to test the display in the client. 16.Parameter Enhancements Added parameter enhancements that provide support for embedded variables in tooltips and title bars. Close the Tank101TempLoops display. Save the Display 17. Feeling adventurous? Try using this to show the loop names in the title bar like the Logix_PIDE display. Perform a Test Display. When prompted for a component name type ‘Tank101TempLoops ‘ 18. 3/10/2008 Page 124 of 160 . not all FactoryTalk View commands work in test display mode and parameter placeholders are ignored. 19.

5. Select the Display command. Find the TankCoolingTemp_Group object in the Object Explorer and Open the Touch Animation Properties. 3/10/2008 Page 125 of 160 . Open the TankOverview display 2. 1.Change Touch Animation Let’s change the touch animation on the Tank Overview display to open the new one you created. click the Next button. Open the Object Explorer 3. 4. Step 1 of Command Wizard. Remove the release action and click on the … button to open the Command Wizard.

Test New Display 1. check the /Y and type ‘20’ which is where the first display was opening. 4. Step 2 of Command Wizard.6. Let’s go to the client. Mouse over the temperature and click for the touch animation. 5. We can’t test the touch animation here. Verify the release action looks like this 8. 3/10/2008 Page 126 of 160 . Click the Close Displays button. 10. Save and Close the display. \ 7. Click the Apply button on the Animation dialog. What happens? Your new display should be opened and you should see values and animations for both loops. Select the Tank101TempLoops display. 3. 9. check the /X and type ‘10’. Click the Tank Overview button. Click the Finish button. Go to the AF07 Client 2. Click the Close button on the Animation dialog.

3. 1. 2. you can assign values to the global parameters in the resulting reference object. restore your Logix_PIDE Global Object if it is not opened then open it. When you copy a global object from a global object display onto a standard display from the Graphics folder. 3/10/2008 Page 127 of 160 . 4. From FactoryTalk View Studio. We just assigned the parameter values in reference objects in the previous section. Right-click on the PIDE_Global_Group Notice that Global Object Parameter Definitions is enabled in the context menu. Let’s look at how they get defined.Global Object Parameter Definitions Global object parameters are defined in base objects in global object displays. Right-click on the PIDE_Description_Group Notice that Global Object Parameter Definitions is not enabled on the context menu. Expand some of the groups in the Object Explorer.

3/10/2008 Page 128 of 160 . LinkAnimation The LinkAnimation property determines whether the reference object uses the animation set up for 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. you can not easily change the object name in the base object. the reference object will appear in red outline. with a red cross on a white background. 5. If you break the link the object will become a graphics object and will no longer reference the base object. Once you have a reference object. it can be restored. This means you can set up the expressions for the reference object separately. If you accidentally perform a name change or delete a base object. to use the animation. excluding expressions. Right-click on the PIDE_Global_Group and select the Global Object Parameter Definitions item in the context menu. You can choose to break the link to the base object after the reference object is created. Do not link. 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 will get a warning message when attempting to rename a base object. This is what you saw when assigning values in the reference global object. A reference object has properties that link it to its base object. If the specified global object display or base object does not exist.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. Observe the name and definitions. set up for the base object. to use the animation. or by the reference object itself. set up for the base object. Set up the LinkAnimation property of the reference object by selecting: Link with expressions. on the same global object display in order to allow the reference objects to work again. These properties can be modified after the object has been created. to set up animation and expressions for the reference object separately. Click the Cancel button to close the Global Object Parameter Definitions dialog. including expressions. You cannot modify the LinkBaseObject property. The Global Object Parameter Definitions dialog is opened. The values of the Link properties determine whether aspects of the reference object’s appearance and behaviors are defined by the base object. Link without expressions. 6. you must recreate the base global object with the same name. To restore the reference object.

or repeat actions set up for the base object. always uses the connections assigned to its base object. False. trend. select the Edit > Global Object Defaults menu item. the object will snap back to its original size. LinkConnections The LinkConnections property determines whether the reference object uses the connections set up for its base object. This is true when you select either Link with expressions or Link without expressions. or Button push button with an action other than Command. the LinkAnimation property determines whether the reference object uses the press. to use the connections assigned to the base object. False. From Explorer. You cannot set up connections for these reference objects separately. If you attempt to resize a reference object with its LinkSize property set to True. These are the default settings. In FactoryTalk View Site Edition. to set up connections for the reference object separately. 3/10/2008 Page 129 of 160 . to set up the height and width of the reference object separately. to use the height and width set up for the base object. Set up the LinkSize property of the reference object by selecting: True. Look at the Global Object Defaults 1. release. a reference object that is a tag label.For a Button push button object. LinkSize The LinkSize property determines whether the reference object uses the height and width set up for its base object. Set up the LinkConnections property of the reference object by selecting: True.

2. 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. or size of the base object will be reflected in the reference object.Global Object Default Settings The Global Object Defaults are now set to Link with expressions for the LinkAnimation properties and true for the LinkConnections. 5. From Explorer. 1. Global objects allow you to make the change in the base object and the reference objects will inherit that change. select the Property Panel item in the context menu or click the Show Property Panel button in the tool bar 4. If you mess up. Click the Cancel button to close the Global Object Defaults dialog. These have changed because Global Object Parameters allow you to use placeholders in the connections and expressions. You can change the text label in the base global object and the reference objects will reflect the change. Double-click on CVLabel_Text to open the Text Properties dialog. 3/10/2008 Page 130 of 160 . you can use the Add Process Faceplates dialog to add it back into the project and replace the one that you modified. Open the Tank101TempLoops display that you created. You will be modifying the Logix_PIDE Global Object. This means that any changes we make to the animation. connection. This means each reference object can have a unique data source(s). When you are done close the display. All the reference objects in this application have been created with these defaults. and still be able to be updated with changes to other aspects of the base global object. Open the Object Explorer 3. 2. From Explorer. This makes maintaining your application a lot easier. open the Logix_PIDE Global Object 2. Look at the Reference Properties 1. Right-click on an object in the Explorer. Modify CV Text The operator is not familiar with the label CV (Control Variable) and is use to seeing OUT (Output) instead. Click different objects in the Object Explorer and observe the properties. Find the CVLabel_Text object in the Object Explorer.

Select the text CV 4. Go to the AF07 Client 10.3. Click the Tank Overview button. 13. Click the Common tab 6. Click the OK button. 9. Click the Close Displays button. Type the text ‘OUT’ 5. 11. 7. Notice two reference objects have the change. Mouse over the temperature and click for the touch animation. 3/10/2008 Page 131 of 160 . Type the number ‘25’ for the width. 12. Save the global object. 8.

You want to add a text object for the EU next to the PV value. you want to use a parameter placeholder for the EU. From Explorer. the base object and the 3 reference objects now reflect the change. This next one is a little trickier. 3/10/2008 Page 132 of 160 . So.14. Let’s see how we would make this change. The Logix_PIDE Global Object already exists and is being referenced. The text label change would have been updated in all of the reference objects regardless of what the link properties were set to. open the Logix_PIDE Global Object 2. If you want to give it a try continue on or you can skip it and go to the next section. Find the PVValue_Group and then select the PV_NumericDisplay in the Object Explorer. Notice the reference object has the change. Click on the valve 15. Add engineering units as Parameter Definition Suppose you want to add engineering units to your faceplate. So we made a change in 1 place. 1. The engineering units (EU) could be different depending on the PIDE Loop you are looking at.

select the Literal string option. Single-click. Note: Literal string variables do not support spaces. The Text Properties opens. and release. and the show * option. 8. Move the mouse next to the PV_NumericDisplay object. 7. select the Fixed number of 6 characters. Click the Common tab. enter #3 for the literal. Click the Insert Variables…String option. 5. In the String Variables dialog. Click the OK button. Single-click on the Text object 4.3. 6. 3/10/2008 Page 133 of 160 . drag.

3/10/2008 Page 134 of 160 . Do you want to continue?” select the Yes button. When prompted “Changing the name will break the links to any reference objects. It is OK to rename the object here because we just created it and do not have any references to it yet. enter 16 for height. 43 for width. select the Global Object Parameter Definitions context menu item. 112 for left position. 292 for top. 10. Look in the Object Explorer and see if your new object was created under the group PV_ValueGroup. 13. 12.9. Type ‘EU_Text’ for the name. Click the OK button. Right-click on the PIDE_Global_Group in the Object Explorer. 11.

Verify engineering units are displayed (2nd try) 1. Notice two reference objects have the change but #3 is showing. 16. 3. select the Global Object Parameter Values context menu item. Right-click on the 1st reference object. Right-click on the 2nd reference object. Verify engineering units are displayed 1. 3/10/2008 Page 135 of 160 . From Explorer. Click the OK button. Click the Tank Overview button. Click the OK button. Pass the new #3 parameter value from reference object 1. Go to the AF07 Client 2. Enter ‘Deg-C’ for the #3 value. Enter #3 for the Name and PV engineering units (literal string with no spaces) for the description. 4. select the Global Object Parameter Values context menu item.14. Close all displays containing the Logix_PIDE reference objects or Click the Close Displays button. Click the Tank Overview button. 3. 15. 2. Save and close the display. 4. Save and Close the Global Object. The parameter has to be passed to the reference objects. Close all displays containing the Logix_PIDE reference objects or Click the Close Displays button. Enter ‘Deg-C’ for the #3 value. Mouse over the temperature and click for the touch animation. Go to the AF07 Client 2. Click the OK button. Mouse over the temperature and click for the touch animation. open the Tank101TempLoops. 3.

Use Tag Substitution to find and modify the references or you can skip to the next section.4. Notice two reference objects have 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. 3/10/2008 Page 136 of 160 .

It should look like this . Put the text immediately after the . select the Edit > Tag Substitution menu item. 10.EU’ Display Logix_PIDE /T::[SoftLogix]Program:Tank101.LevelAtune. 6. When you find it.::[SoftLogix]Program:Tank101. 9. 3. 8. scroll through the Search for list and look for occurrences of Display Logix_PIDE 5.LevelController. open the TankOverview display. and then copy it into the Replace with field.EU 7.Search and Replace References on TankOverview 1. When the TankOverview display is highlighted. 4. From the Explorer. select the Edit > Select All menu item. Click the Replace button. Edit the Replace with to add the EU for #3. Continue to look in the Search for list and make sure there are not anymore references. 2. Type a ‘.LevelController. click the replace button one at a time until complete. When prompted to confirm the replace.EU /x875 /y125 Remember no spaces for embedded variables being used as a literal string. Save and Close the display.::[SoftLogix]Program:Tank101. 3/10/2008 Page 137 of 160 . Display Logix_PIDE /T::[SoftLogix]Program:Tank101. While all items are selected. When the Tag Substitution dialog is opened. Make sure the confirm check box is checked.LevelAtune /x875 /y125 click to select it.

Organize global object displays in such a way that the majority of base global objects required by a specific standard display. At run time. set its Cache After Displaying property to Yes. avoid creating global objects that are too complex. avoid creating a large number of instances of this object on one standard display. Go to the AF07 Client 2. For example. loading a display with many global object instances can result in performance issues. Future product enhancements are planned to improve Global Object performance. design-time changes to the base object will not be picked up by the corresponding reference object until the FlushCache command is issued. If a complex global object is required.Verify engineering units are displayed on Tank Overview – Valve 1. If a standard display contains ten or more complex global objects and is being accessed frequently. Do not create a large number of base global objects on a single global object display. and combinations of these variables. Global Objects require extra time to resolve their required tag instances and start receiving them from the data server. 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. or an SE Client session is closed and restarted. the number of expressions and animations associated with a global object. This causes graphics using significant numbers of Global Objects to display more slowly. Here are some recommendations for working with global objects: Whenever possible. the number of global object connections. reside on the same global object display. Object complexity is measured by the number of graphic objects contained within a global object. This is done in the Properties tab of the Display Settings dialog box Important: While the Cache After Displaying property is in effect. Close all displays containing the Logix_PIDE reference objects or Click the Close Displays button. 3. Click the Tank Overview button. 3/10/2008 Page 138 of 160 . Click on the valve 4. a graphic with 20 relatively data intensive Global Objects takes 5-7 seconds to display. 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.

This includes FactoryTalk device-based alarm messages created in RSLogix 5000 and FactoryTalk tag-based alarm messages created in the Alarm Setup Editor. and then import translated strings for up to 40 languages into the same application. FactoryTalk historical alarm and event information is only logged in one language which is specified on the alarm server properties. With language switching you can: Develop an application in one language.Section 10: Language Switching (est. 3/10/2008 Page 139 of 160 . time 30 min) About This Section In this section. export the user-defined text strings for the application. 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. multiple FactoryTalk View SE clients can switch between any of the languages the application supports. At run time in a network application. Multiple clients can also run in different languages at the same time.

Previous to this release only 20 different languages were supported. the user-defined strings that support language switching are those that an operator sees in an application at run time. Support for 40 languages. Enable operators in multilingual countries to use the language of their choice. 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. You can also import text strings in one or multiple languages from an Excel spreadsheet to an application. These are translated when FactoryTalk View is localized text that can be displayed at run time but is used to operate the application. Language Switching Enhancements A default language for language switching can be specified. allowing operators in each location to view the application in their own language. such as menus.) text strings defined for FactoryTalk Alarm and Event summaries. banners. FactoryTalk View SE Language Switching In general. such as the names of graphic displays and command strings tag descriptions and string constants in expressions 3/10/2008 Page 140 of 160 . 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.Deploy a distributed application across different countries. Specifically. which are displayed in the same language as the operating system. 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. these are: text you specify for graphic objects and global objects including o o o o o captions tool tip text time and date embedded variables local messages 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.

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. select the Tools > Languages… menu item. in the Control Panel. The languages you will be selecting are installed. To find out which languages are installed on a computer. Be sure that these Windows languages are installed on the development and client computers before trying to switch languages. 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. 3/10/2008 Page 141 of 160 . 1. check the Regional Options (Windows 2000) or Regional and Language Options (Windows XP and Windows Server 2003). From FactoryTalk View Studio.text in the title bar of the FactoryTalk View SE Client window. which is part of the setup of the client.

Click the Add… button on the Language Configuration dialog. Select the Spanish (Mexico) language and click the OK button. 5. 3/10/2008 Page 142 of 160 . 4. Select the German (Germany) language and click the OK button.3.

6. 7. 3/10/2008 Page 143 of 160 . Check the Display undefined strings using the default language option. Click the Apply button. 9. Select the Chinese (PRC) language and click the OK button. 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.

The String Export in Progress will start and then complete. The best approach is to export the strings to Excel and use the Optimize duplicate strings feature. Leave the default location and click the Finish button. 1. Since you are using a local application there is only one HMI Server and you will not see the Select Servers dialog. 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. Select the Export strings for all languages to an Excel spreadsheet radio button. Click the Export button 2. Now you will need to perform an export to get the strings that you will need for translation. 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. 5. The Excel document will be created and opened. 4. 6.Your application has been configured to support 3 languages. 3/10/2008 Page 144 of 160 . Check the Optimizing duplicate strings and Open exported file options 3.

Translate strings Observe the open Excel file.xls file 3. G. Open the LanguageSwitching folder. Everywhere you see the text **REF: in the language columns (i. select the Lab 15 FactoryTalk View SE shortcut . Double-click on the AF07_translated. de-DE. Observe the file. and 233 along with the crossreverences. You will use a different file that has already been translated to do the import. en-US. Close the file. Notice that the cross-reference to the first occurrence is in the language columns.. Note. es-MX. and K) are left blank when the occurrence is not cross-referenced. You only have to translate the first occurrence of that text indicated by the text **UNDEFINED**. your Excel file may look different. and zh-CN) is referencing a duplicate string in the REF column before the language column. Let’s look at a file that has been translated for you. Here is an example of first occurrence references of #36. This is REF:36 and it is the first occurrence. 4. If it isn’t row 230 do a find on the description.e. Scroll down in Excel until you see row number 230. From the Start menu. Only the first occurrence will need to be translated. 3/10/2008 Page 145 of 160 . I.Caption” and is cross-referencing (**REF:36**) the first occurrence. Notice that the “REF” Columns (E. Notice that this file was translated from an export file that was not optimized. 232. Notice that not everything has been translated. Row 244 has a Column D description of “OpenNonPermissive_Text. Column D “Description” will have ‘CloseNonPermissive_Text. 2. That means you don’t have to translate the text for that object. 231.Caption”. 1.

let’s import them. 1. from the String Import Export Wizard dialog and click the Next button 3/10/2008 Page 146 of 160 . Select the option to Import strings from an Excel spreadsheet…. 2. Select the Import button from the Language Configuration dialog.Import strings that have been translated Now that you have a file with translated strings.

Once it is completed. 4. 3/10/2008 Page 147 of 160 . 1. open the footer display. Notice the Release action . 3. Language switching command There is a FactoryTalk View language switch command that you use to perform language switching. From the Explorer. Click the OK button on the Language Configuration dialog. Buttons that use this command have been configured on the footer display. Let’s look at them. Double-click on the US flag button to open the Button Properties dialog. 2. Select the Browse … button and browse to this file C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching\AF07_translated. On the Button Properties dialog. click on the Action tab.Language en-US The Language command was added to the Release action by clicking the … button and then using the Command Wizard. you will see the message String import completed successfully in the Diagnostics List. 5.xls and click the Finish button. String import in Progress will start. The command Language is located under the System – Languages folder.3.

3/10/2008 Page 148 of 160 . Repeat steps 2 – 4 for the other flags to observe the release action. 5. 4. 6. Click the Cancel button.Only the languages that have been added to your application will be displayed in the language id list. 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. Go back to View Studio an Launch the client. 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. 2. displays the current date and time. 3/10/2008 Page 149 of 160 . RSLogix 5000 configures alarm messages in the language of RSLogix 5000 software. These will be translated in the next section. For example. then when RSLinx Enterprise connects to the controller. the German version of RSLogix 5000 configures alarm messages in the German language. Go to the AF07 Client. both languages are uploaded and available to FactoryTalk Alarms and Events clients. system\dateandtimestring. use the Alarm Properties dialog box to translate device-based alarm messages individually. Close the AF07 client. Click the different flag buttons in the footer display and navigate through different displays. Notice that alarm messages for Tank101 are not translated. the tag. 4. Notice that the date and time are still displayed in English. If you add another language. Notice that language switching works but not everything was translated. Device-based alarm language switching In RSLogix 5000. 6. You can use FactoryTalk View SE system tags in an application to display text in graphic displays. For example. 5.1.

Select the Tools > Export menu item. Notice the Save as type options for the export file. 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. 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.CSV) selected. Export alarm messages in RSLogix 5000 1. For double-byte character sets (for example.txt format because in RSLogix 5000.txt) file. and you want to translate alarm messages from only one of them. export alarms in .csv) or text (*. 3. 4. Keep the default of RSLogix 5000 Import/Export File (*. 3/10/2008 Page 150 of 160 . If your RSLogix 5000 project includes a large number of programs.You can export alarms from RSLogix 5000 to a comma-separated variable (*.csv format does not support Unicode character sets. Click the Export button. 5. the . Once you have exported the alarm messages. 6. When the Export dialog opens navigate to C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching and keep the default filename. you can make selections in the Export dialog box to limit the data that is exported. This lab will demonstrate how to use both formats. Chinese).

Open the LanguageSwitching folder. Change the text en-us to ‘es-MX’ (for Spanish in Mexico).Translate alarm messages 1. 7. From the Start shortcut menu. Double-click on the AF07_SE_Lab-Tags. B. 8. Your file should look something like this. 3. Copy the last ALMMSG line and then paste it at the end of the file. C. 4. The alarm message text appears as the fourth column (D) from the left (“ProductTemp Low”). Save your changes. Change the text en-us to ‘de-DE’ (for German in Germany). 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. select the Lab 15 FactoryTalk View SE . The first element from the left is the instruction type (ALMMSG:) and the language string for the alarm message (enus for English in the United States). and D. ‘ProductTemp Tiefpunkt’ 6. and then change the alarm message text to read. ‘ProductTemp Bajo’. Paste another copy of the ALMMSG line at the end of the file. Expand the width of columns A. 2.CSV file to open it in Microsoft Excel. and then change the alarm message text to read. 5. 3/10/2008 Page 151 of 160 .

TXT has been translated for you. You will use that file when performing an import. The export file was created using the RSLogix 5000 Unicode Import/Export (*.TXT) format because it includes message strings that were translated in Chinese. 3/10/2008 Page 152 of 160 .An export file C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitchingAF07_SE_LabTags_translated.

7.Import alarm messages 1. When the Download Dialog appears. When prompted with the message “Done downloading.TXT. Select the RSLogix 5000 Unicode Import/Export Files (*. 6. 5. if you are online with the controller then go offline by selecting the Communications > Go Offline menu item. From RSLogix 5000. When the Import dialog opens navigate to C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching 4. 3/10/2008 Page 153 of 160 . Select the filename AF07_SE_Lab-Tags_translated. Select the Communications > Download menu item 8. 2. 3. 9. Select the Tools > Import menu item. Change the controller mode back to Remote Run?” select the Yes button. leave the default settings for the Tags and Logic Comments.TXT) file type. Click the Import button. select the Download button.

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. Make sure the controller is in Remote Run mode. alarm messages display in the language selected during start up of the FactoryTalk View SE application. Tank 101 alarms should now be language translating in View Client. 3/10/2008 Page 154 of 160 . When the Tag Alarm and Event Editor opens in FactoryTalk View Studio. alarm messages display in the default language defined for the application. select the Communications > Run Mode menu item 11. If alarm messages are not defined in the specified language. Tag-based alarm language switching When the Alarm and Event Setup editor launches in FactoryTalk Administration Console. If a message string does not exist in the default language a question mark character (?) is displayed. When editing alarm messages in multiple languages.10. If it is not. alarm messages display in the default language defined for the application. You will verify this at the end of this section. If a message string does not exist in the default language a question mark character (?) is displayed.

3. 2. From the Explorer. right-click on the AF07 and select the Add New Server > Tag Alarm and Event Server… context menu item. 4.Create a Tag Alarm and Event Server 1. On the General tab of the Tag Alarm and Event Server Properties page type ‘FTAETagServer’ for the name. 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. Click the OK button 3/10/2008 Page 155 of 160 . Click on the Priorities and History tab.

one for the messages. Double-click on the AF07_FTAETagServer_AlarmExport_translated. Close the Alarm and Event Setup Editor Normally. You will step through an export at the end of this section to see how it works. translate the alarm messages. 4. Close the file. 6. 5. you would use the Alarm and Event Setup Editor to create your alarms. If you don’t have C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching folder open. 2. For this lab you will be creating your alarms with a file that contains the alarms and the translated messages strings. There is one digital alarm and one level alarm. There is a column for each language that has been translated. do an export. The Alarm Import Export Wizard will open. Import alarm messages 1. Notice there is a worksheet for each alarm type. and then import them back into the Tag Alarm and Event Server. 3.xls file to open it. 3/10/2008 Page 156 of 160 . Notice that one message can be used in multiple alarms. Double-clicking on the Alarm and Event Setup icon under the Alarm and Event Tag Server in the Explorer. Notice that there are no alarms. 7. The Alarm and Event Setup Editor will open. right-click on the FTAETagServer and select the Import and Export… context menu item. Translate alarm messages 1. and then one for tag update rates. You will use the import to create alarms. Click on each of the tabs and take a look. 6. From the Explorer. Tag based alarms can be created and configured with the Alarm and Event Setup Editor. Click on the Messages tab. do so.5.

Click the Next button on the Alarm Import Export Wizard 6. 3. you should see this 8. Click the OK button. Select the Import alarm configuration from Excel File options and click the Next button. A progress indicator will open. Navigate to C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching.2. 5. 7. The Select Alarm Import File dialog will open.xls file and click the Open button. Select the Update existing alarm definitions and create new alarm definitions from the import file option and click the Finish button. Double-clicking on the Alarm and Event Setup icon under the Alarm and Event Tag Server in the Explorer. Click the browse … button. When complete. Verify alarm import 1. 4. Select the AF07_FTAETagServer_AlarmExport_translated. 3/10/2008 Page 157 of 160 .

In fact. Double-click on the first alarm. 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. This is just so you can compare them. this tag alarm will be triggered from the same condition as a device-based alarm that was created. 3/10/2008 Page 158 of 160 . The Alarm and Event Setup Editor will open. Notice that there are two alarms.2. 3. the Digital Alarm Properties dialog will open.

To view the list of alarms that are referencing a particular alarm message. 9. The next alarm will be displayed in the Level Alarm Properties dialog. Click the Messages tab. Notice on the Messages tab that the same message string is used for both the High High and the High condition. 8. Click the OK button to close the Message Usage Details dialog.4. In fact. you can configure one message per level condition. right-click on the FTAETagServer and select the Import and Export… context menu item. 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. 2. Click the forward arrow button to navigate to the next alarm 5. right-click the row containing the message and then click the Usage Details context menu item. From the Explorer. The Usage column on the Message tab indicates how many alarms are referencing an alarm message. this tag alarm will be triggered from the same condition as a device-based alarm that was created. You can create as many messages as you like for alarms. 1. 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. Alarm messages can be shared between alarms to eliminate duplication. The Alarm Import Export Wizard will open. Close the Alarm and Event Setup Editor Export alarm messages You will step through an export to see how it is done. Select the Export alarm configuration to Excel file and click the Next button 3/10/2008 Page 159 of 160 . This is just so you can compare them. 6. but each alarm can be associated with only one message. Click the Cancel button to close the Level Alarm Properties 7. For level alarms.

5. Change the file name to MY_ AF07_FTAETagServer_AlarmExport. 6. Leave the defaults with all the selected alarms and click the Next button 4. Click the OK button. 3/10/2008 Page 160 of 160 . A progress indicator will open. When complete. Select the Export messages for all alarms.xls and click the Finish button.3. check all the languages. and click the Next button.

. Notice both the tag and device-based alarms appear and the message strings are language switchable. and the alarm monitoring system and all of the client screens switch to the appropriate language on that specific client. The Alarm and Event objects in FactoryTalk View always show the date/time format of the operating system. change the event subscription to *Tank101* or add another event source called Tank101* . Tag-based alarms will not appear in the Tank Summary because the event subscription is set to [SoftLogix]Program:Tank101. FactoryTalk historical alarm and event information is only logged in one language which is specified on the alarm server properties. When a FactoryTalk View SE Client runs. You have completed this lab! 3/10/2008 Page 161 of 160 . the FactoryTalk Alarm and Event objects (Alarm and Event Summary. 3. This data continues to appear in the same language used when the alarm and event information was written to the alarm history database.e. 1.View translated Alarm Messages When RSLinx Enterprise makes the connection to the controller. The tag-based alarms start with Tank101. 4. Device-based alarms will have the shortcut name at the beginning of the alarm name i. Switching languages at run time does not switch time and date formats. For example. even if the language is switched to German. for example) connect to the Alarm and Event system and request alarm messages in the current language. Tag-based alarms will start with Tank101. is not translated. Go to the AF07 Client.*. Alarm Fault List messages that can be displayed from the Alarm and Event Banner and Summary do not currently switch languages. which consists of historical alarm and event information. You can then switch among languages with the click of a button on the client computer. [SoftLogix]. all alarm messages and their languages are uploaded from the controller. 2. Notice that language switching works and alarm messages are also being updated to the appropriate language. Click the different flag buttons in the footer display and navigate through different displays. a message logged in English will be displayed only in English. The contents of the Alarm and Event Log Viewer event list. To get them to appear in the Tank Summary.

Sign up to vote on this title
UsefulNot useful