Escolar Documentos
Profissional Documentos
Cultura Documentos
3/10/2008
Page 5 of 160
3/10/2008
Page 6 of 160
3/10/2008
Page 7 of 160
Section 3 Testing Displays - Configure a FactoryTalk View Client File called AF07 or use the preconfigured client file (C:\LabFiles\Lab 15 FactoryTalk View SE\Client\AF07.cli)
It is recommended that novice users complete remaining lab procedures in the order they are
presented, time permitting.
What You Will Accomplish In This Lab
As you complete the exercises in this hands-on session, you will gain an understanding of the
functionality and capability of FactoryTalk View Site Edition by
creating an application
configuring an RSLinx Enterprise data server and enabling it for alarm and event support
Page 9 of 160
implementing security
Have a basic knowledge of HMI software and are involved in the design and implementation of
supervisory-level HMI projects.
Lab Materials
For this Hands-On lab, we have provided you with the following materials that will allow you to complete
the labs in this workbook.
Hardware
This hands-on lab does not require any hardware. A Logix5000 controller could be used in place of
SoftLogix 5800.
Note: FactoryTalk Alarms and Events Device Based Alarms requires firmware version 16.20 or higher
for ControlLogix, CompactLogix L3x and L4x, and DriveLogix.
Software
This hands-on lab uses the following software:
FactoryTalk Alarms and Events v2.10.00.0117 (included with FactoryTalk View Site Edition and
RSLinx Enterprise)
RSLogix5000 v16.03.00
Microsoft SQL Server 2005 Express Edition is a free, redistributable version of Microsoft SQL Server.
FactoryTalk Alarms and Events uses Microsoft SQL Server as the database engine for logging alarm
and event information. You can connect to an existing SQL Server database, or you can install
Microsoft SQL Server 2005 Express, Service Pack 2, which is included in the Redist folder on the
FactoryTalk View SE and RSLinx Enterprise CDs.
3/10/2008
Page 10 of 160
Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical
management tool for managing SQL Server 2005 Express. It is included in the Redist folder on the
FactoryTalk View SE and RSLinx Enterprise CDs.
Lab Files
This hands-on lab uses the following files located in the C:\ LabFiles\Lab 15 FactoryTalk View SE\
subdirectory:
LanguageSwitching contains 3 files that will be used in the language switching section of the lab
AF07_translated.xls
Translated file for FactoryTalk View SE
AF07_SE_Lab-Tags_translated.TXT
- Translated file for FactoryTalk Alarms and Events device-based alarm messages in RSLogix
5000
AF07_FTAETagServer_AlarmExport_translated.xls
- Translated file for FactoryTalk Alarms and Events tag-based alarm messages in the
FactoryTalk Tag Alarm and Event Server
RSLogix 5000 contains 3 files that can be used with RSLogix 5000.
SQL contains 1 file for a SQL Query in Microsoft SQLExpress that will be used in the Data
Logging section of this lab
ViewTank101DataLog.sql
AlarmLogViewer.gfx
AlarmStatusExplorer.gfx
AlarmSummary.gfx
Footer.gfx
Header.gfx
TankAlarmSummary.gfx
TankOverview.gfx
ClientKeys.key
ClientStartup.mcr
AF07.cli
3/10/2008
Page 11 of 160
Lab Setup
Copied lab files to C:\ LabFiles\Lab 15 FactoryTalk View SE\
Copied C:\LabFiles\ Lab 15 FactoryTalk View SE\ RSLogix 5000 \AF07_SE_Lab.ACD to C:\RSLogix
5000\Projects\AF07_SE_Lab.ACD
Shortcuts for the following applications, directory, and files were created in the Startup Menu:
Created a System DSN called FactoryTalk using the FactoryTalk database as the default database.
Note that the files and setup steps for the optional sections (Language Switching, Data Logging, and
FactoryTalk Diagnostics) are not required unless you want to do those sections.
Document Conventions
Throughout this workbook, we have used the following conventions to help guide you through the lab
materials.
This style or symbol:
Indicates:
Any item or button that you must click on, or a menu name
from which you must choose an option or command. This will
be an actual name of an item that you see on your screen or
in an example.
3/10/2008
Page 12 of 160
The text that appears inside this gray box with the graphic will
indicate that a feature is new in the V 5.00 (CPR 9) Release.
Note: If the mouse button is not specified in the text, you should click on the left mouse button.
3/10/2008
Page 13 of 160
Overview
About this lab
This lab will outline the major components and fundamental ideas of FactoryTalk View Site Edition. It
will specifically:
Discuss the differences between FactoryTalk View SE Local and Network Application
Discuss HMI Servers, data servers, and Tag Alarm and Event Server
Discuss FactoryTalk Alarms and Events Services for Device Based and Tag Based Alarms
Start > Programs > Rockwell Software > FactoryTalk View > FactoryTalk View Studio
FactoryTalk View Studio is configuration software for developing and testing FactoryTalk View SE
applications. FactoryTalk View Studio contains editors for creating complete applications, and includes
client and server software for testing the applications you create. Use the editors to create applications
that are as simple or as complex as you need. You can use FactoryTalk View Studio to develop
FactoryTalk View Site Edition and FactoryTalk View Machine Edition (ME) applications.
FactoryTalk View comes with process faceplates and graphic libraries that can be used in your
applications. Process faceplates are preconfigured to work with various Logix5000 instructions (for
example, PIDE, D2SD, and the new ALMD and ALMA instructions). Many of the graphic library objects
are preconfigured with animation. Use the objects as they are, or change them to suit your needs.
When you have finished developing an application, use FactoryTalk View SE Client to view and interact
with the application.
Start > Programs > Rockwell Software > FactoryTalk View > FactoryTalk View Client
FactoryTalk View SE Client is a complete runtime operating environment for viewing and interacting
with FactoryTalk View SE local and network applications. To set up a FactoryTalk View SE Client, you
need to create a configuration file using the FactoryTalk View SE Client wizard. The HMI Server does
not have to be running when you configure a FactoryTalk View SE Client. With the FactoryTalk View
SE Client you can:
Load, view, and interact with multiple graphic displays at a time from multiple servers
Start > Programs > Rockwell Software > FactoryTalk View > Tools > SE Administration
Console
FactoryTalk View Administration Console is for administering FactoryTalk View applications after they
have been deployed. FactoryTalk View Administration Console contains a sub-set of the FactoryTalk
View Studio editors, so you can make minor changes to an application without the need for installing
FactoryTalk View Studio. The FactoryTalk View Administration Console has a two hour run-time limit. A
warning message is displayed five minutes before the time is up. To continue using it you simply shut it
down and restart it.
FactoryTalk View Administration Console allows you to:
Set up security for commands and macros, using the Runtime Secured Commands editor.
Change how HMI tag alarms are logged and annunciated, using the Alarm Setup editor.
Change which system activities are logged and how frequently, using the Diagnostics Setup editor
(on the Tools menu).
Change the location alarms are logged to, and manage log files, using the Alarm Log Setup editor
(on the Tools menu).
Import and export HMI tags using the Tag Import and Export Wizard (on the Tools menu).
3/10/2008
Page 15 of 160
Tag-based alarm monitoring. If you are not using Logix5000 controllers, or if you do not want to use
the pre-built alarm instructions available with RSLogix 5000, tag-based alarm monitoring offers the
equivalent of HMI Tag Alarm Monitoring, but with an expanded feature set. Software-based Tag
Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish
event information for display and logging. Tag-based alarm monitoring is supported for Logix5000
controllers, PLC-5, and SLC 500 devices communicating through Rockwell Automation Device
Servers (RSLinx Enterprise), or for third-party controllers communicating through OPC data
servers.
Start > Programs > Rockwell Software > FactoryTalk Administration Console
Part of the FactoryTalk Services Platform, FactoryTalk Administration Console is an optional, standalone tool for developing applications and managing a FactoryTalk system. You can use FactoryTalk
Administration Console or FactoryTalk View Studio to develop applications and manage a FactoryTalk
system. Only FactoryTalk View Studio can be used to create HMI servers and HMI projects.
3/10/2008
Page 16 of 160
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.
Create database definitions for logging historical alarm and event messages.
Set up redundancy for OPC data servers and Tag Alarm and Event Servers.
Configure client computers to recognize the location of a Network Directory Server computer.
FactoryTalk Activation
Start > Programs > Rockwell Software > FactoryTalk Activation > FactoryTalk Activation Tool
FactoryTalk Activation provides a secure, software-based system for activating Rockwell Software
products and managing software activation files. With FactoryTalk Activation, there is no need for a
physical master disk or any physical media; instead, activation files are generated and distributed
electronically.
FactoryTalk Activation provides these types of activations:
Shared concurrent activations are locked to an activation server computer, and shared by client
computers on the network.
There are two types of shared concurrent activation: floating and borrowed. Floating concurrent
activation requires a continuous network connection, while borrowed concurrent activation does not.
3/10/2008
Page 17 of 160
Areas: A key part of the network architecture system is the area. An area is a logical division within
your application. You can think of areas as partitions of your hard drive. The partitions are all on the
same main disk (or application, in this analogy), but they divide it logically and hold information
independently of each other. An area can also be used to organize the application in a way that
makes sense for the process it is controlling.
For example, an area might represent a portion of a process, or a region within the process facility.
An automotive plant could be divided into areas called Press and Fabrication, Body Shop, Paint
Shop, Engine, and Transmission; a bakery could be divided into areas called Ingredients, Mixing,
Baking, and Packaging. Alternatively, a plant with identical production lines could be divided into
areas called Line 1, Line 2, Line 3, and so on. This would allow you to add new, identical production
lines to the application by copying HMI server projects into new areas.
Root Area: All FactoryTalk View applications have one system-defined area called the root area,
which has the same name as the application. The application root area can contain one HMI server,
and one or more data servers.
Best Practice
Since an area is nothing more than a logical method of organizing the application, and not a physical
entity, there is not a limit to the number of areas that can reside within an application. However, there
is a limit of 1 HMI server per area and 10 HMI servers per application*.
The recommended limit of data servers within an application is 10*. There is not a limit to the number
of data servers that can co-exist in the same area. However, it makes sense to logically organize the
data servers that are serving alarms in order for the alarm summary to filter alarms appropriately at
runtime. For example, a single area may contain an HMI server for a physical location of a facility, an
RSLinx Enterprise data server (configured as a FactoryTalk device based alarm server), and a 3rd
party OPC server (configured with the FactoryTalk tag based alarm server). This configuration allows
for the alarm summary to filer alarms based on the area name, regardless of which server the alarm
comes from.
What you want to avoid is one physical installation of a data server to be referenced multiple times from
different areas of the application. This is not necessary because FactoryTalk allows any client to see
any data point within the application, regardless of which area it comes from.
*Note: The initial release of FactoryTalk Alarms and Events have different limits than FactoryTalk View
SE 5.0. Please refer to the FactoryTalk Alarms and Events Quick Start Guide or Answer id 44177
within the Rockwell Automation Knowledgebase for more information.
3/10/2008
Page 18 of 160
Network
Directory
Root Area
HMI Server
Servers
Areas
Area
Data server
The Insta Corp application consists of four different defined areas: ie_packaging, ie_production,
is_packaging, and is_production. The areas are marked by the folders that are right off the root,
which is the application Insta Corp.
Try looking at one of the areas ie_packaging, the topmost area. Notice that the HMI server called
IE_CasePack is located inside the area.
The folders under the ie_packaging HMI Server titled System, HMI Tags, Graphics, Alarms, Logic and
Control, and Data Log are all different components you can configure under each HMI server they are
not areas within the area, but are actually components of an HMI server.
There is a data server called RSLinx Enterprise located under the root area (Insta Corp).
3/10/2008
Page 19 of 160
The diagram below shows an example system architecture using a Network application as part of a
distributed FactoryTalk system.
3/10/2008
Page 20 of 160
Local Applications
A local application is similar to an RSView32 project; all application components and the FactoryTalk
View SE client are located on a single computer. There is only one HMI server that is created for you in
the root area when the application is created. You may use local applications for parts of the plant or
process that are self-contained and are not related to other parts of the process.
The diagram below shows an example system architecture using a Local application as part of a standalone FactoryTalk system.
3/10/2008
Page 21 of 160
3/10/2008
Page 22 of 160
Rockwell Automation Device Servers (RSLinx Enterprise) provide best performance when
communicating with Logix5000 controllers, or with many clients. You can also use RSLinx
Enterprise servers to subscribe to device-based alarms and events.
OPC data servers (including RSLinx Classic) support any data server that conforms to the OPC-DA
2.0 standard. OPC stands for OLE for Process Control, a protocol that allows FactoryTalk View to
retrieve tag values from:
Rockwell Automation programmable controllers and devices, using RSLinx Classic or RSLinx
Gateway as an OPC server.
Third-party controller devices, such as Siemens or Modicon, using third-party OPC servers.
Tag-based alarm monitoring. If you are not using Logix5000 controllers, or if you do not want to use
the pre-built alarm instructions available with RSLogix 5000, tag-based alarm monitoring offers the
equivalent of HMI Tag Alarm Monitoring, but with an expanded feature set. Software-based Tag
Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish
event information for display and logging. Tag-based alarm monitoring is supported for Logix5000
controllers, PLC-5, and SLC 500 devices communicating through Rockwell Automation Device
Servers (RSLinx Enterprise), or for third-party controllers communicating through OPC data
servers.
An Alarm and Event Server can be a Rockwell Automation Device Server (RSLinx Enterprise) that is
enabled for monitoring device-based alarms or a FactoryTalk Alarm and Event Tag Server that has
been configured for monitoring tag-based alarms.
3/10/2008
Page 23 of 160
Add Process Faceplate Displays (Alarm Analog ALMA, Alarm Digital ALMD, Discrete 2State Device D2SD, Enhanced PID PIDE, and Help Help Browser) into your HMI Project
Add Database Connection called FTAEHistory for FactoryTalk Alarms and Events Historical
Logging
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.
4. Select
New
3. Select
Continue
5. Type
AF07
2. Select
Site Edition (Local)
6. Select
Create
Wait for several seconds to allow FactoryTalk View Studio to create the application. After the AF07
HMI Server has been created, you will be prompted with the Add Process Faceplates dialog.
3/10/2008
Page 24 of 160
3/10/2008
Page 25 of 160
This is the Application Explorer window that will be used throughout this entire hands-on lab. The
Explorer allows you to select different objects, displays, and other components of the FactoryTalk View
SE application.
Local
Director
HMI
Server
Application
(Root Area)
Displays for
Process Faceplates
added here
3/10/2008
Page 26 of 160
3/10/2008
Page 27 of 160
3. When the Alarm and Event Historian Database Properties opens enter:
Definition name: FTAEHistory
Database user name: administrator
Database password: rockwell
Database name: FTAEHistory
And leave the defaults for the other fields.
3/10/2008
Page 28 of 160
4. Click on OK.
5. When you are prompted with the Database does not exist message box: The database will be
created. The database user will also be created. If the user already exists, the user will be assigned
access to the database. Do you want to create the database? click the Yes button
6. After the database is created the dialog will close. Expand the Databases folder to confirm that it
was created.
3/10/2008
Page 29 of 160
2. The RSLinx Enterprise Server Properties will appear. Leave defaults on the General tab.
3. Select the Alarms and Events tab
3/10/2008
Page 30 of 160
8. Verify that the RSLinx Enterprise device server has been successfully added into your application.
Configure Communications
We are going to configure a device shortcut.
Device Shortcuts: A Device Shortcut allows you to create a pointer to a device that you can refer to
throughout the application while developing displays. This enables the user to change the location of a
processor or other such device in one place, which then propagates throughout the rest of the project,
without having to change all tag references to that processor. A device shortcut is similar to a Windows
shortcut on your computers desktop that provides easy access to an application.
The Communication Setup dialog will appear to the right of the Explorer tree.
3/10/2008
Page 31 of 160
1. Click the
Add button
3/10/2008
Page 32 of 160
3/10/2008
Page 33 of 160
Verify Configuration
1. Verify that the Device Shortcut named SoftLogix is highlighted and that slot 2 is highlighted and
reads 2, 1789-L60/A, AF07_SE_Lab for your Primary Device. Click the OK button
2. The Verify dialog will appear. Review your changes. Make sure your shortcut is SoftLogix we
will be using pre-configured displays referencing that shortcut name. Click the Yes button.
3/10/2008
Page 34 of 160
Verify Communications
Lets take a minute to verify that communications is setup correctly and that we are getting alarms.
Verify that you are getting alarms by adding a FactoryTalk Alarms and Events Object to a display and
then testing that display in FactoryTalk View Studio. Verify that you can access controller tags from the
online SoftLogix Controller and the offline tags file by performing tag browses. We will go into more
details about these topics in the Tags and Alarms sections of this lab.
FactoryTalk Alarms and Events Verification
1. In the Explorer, right-click on the Display folder, select the New context menu item
Or
Select the Objects > Alarm and Event > Summary menu item.
3. Mouse over the upper left corner of the empty display, you will see the cursor change to show that
the Alarm and Event Summary object has been selected. Single-click and hold down the mouse
button, drag the cursor to the lower right corner of the display and release the mouse button. As
you are dragging the mouse you will see a rectangle to show the size of the object that will be
created.
3/10/2008
Page 35 of 160
After you release the mouse button the Alarm and Event Summary will appear.
4. Single-click on the Test Display button from the tool menu.
5. The indicator in the lower left corner of the Alarm and Event Summary display should be green to
indicate that you are connected to the RSLinx Enterprise Server. It may take several seconds for
the services to startup before you see alarms in the list. Mouse over the indicator to verify your
connection.
Note: The alarm count of 32 may not be the same on your display.
You should also start to see alarms appear in the summary (This may take a few moments).
6.
7. To remove the object from the display perform one of the following actions:
- Select the Edit Undo menu item
- Ctrl-Z - Select the CTRL and Z keys at the same time
- Single-click on the Alarm and Event Summary object and select the delete key
Diagnostics List
The Diagnostics List shows information about system activities. Its located above the status bar at the
bottom of the FactoryTalk View Studio main window. You can hide, move, resize, and clear messages
from the Diagnostics List.
8. Look at the Diagnostics List and the messages in it. Use the arrows to scroll through the messages
or resized the window so you can see 3 or 5 lines at a time.
To change the size of the diagnostic window mouser the upper edge until you see the double lines,
mouse down and drag up to change the size. Release the mouse when you have the desired
window size.
3/10/2008
Page 36 of 160
Notice the message Successfully subscribed to 46 alarms from controller SoftLogix. This
message is an informational message to help verify that your system is configured properly.
We have just verified that you have the RSLinx Enterprise Device Server and the SoftLogix Device
Shortcut properly configured for FactoryTalk Alarms and Events.
Controller Status Alarms
Rockwell Automation Device Servers (RSLinx Enterprise) generate diagnostic alarms relating to
Logix5000 controllers that are producing alarms in a FactoryTalk Alarms and Events system. These
alarms are referred to as controller status alarms and they indicate a problem with the connection to a
controller or the status of a controller. A single controller status alarm is produced for each shortcut that
is configured with alarms and events enabled.
The following conditions cause a controller status alarm to go In Alarm:
Unable to 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
Program download
Controller status alarms have the same name as the shortcut that references the controller. The alarm
message is not user configurable and the severity for all status alarms is configured in the system-wide
severity settings.
3/10/2008
Page 37 of 160
Or
Select the Objects > Numeric and String > Numeric Input menu item.
2. Mouse over a blank area on the display, you will see the cursor change to show that the Numeric
Input object has been selected. Single-click and hold down the mouse button drag the cursor to
down and to the right and release the mouse button. As you are dragging the mouse you will see a
rectangle to show the size of the object that will be created.
When you release the Numeric Input Properties dialog will appear.
3/10/2008
Page 38 of 160
5. The Tag Browser will open. If you dont see a folder for SoftLogix, right-click on AF07, select
the Refresh All Folders context menu item.
6. The browser window and panes can be resized. Expand the tree on the left and navigate to
SoftLogix - Offline Program:Tank101 - JacketTempLoop
JacketTempLoop is an Enhanced PIDE data structure.
Click on CV in the right pane. CV is a member tag of the Enhanced PIDE. It is an output value of
the PIDE. Your selected tag should look like this:
3/10/2008
Page 39 of 160
13.
0 should appear on the display. This actually verifies that you got the tag from the offline tag file
and you are online with the controller. If you were not online with the controller, it would appear
as what is called a wireframe, because the data is not available at this time. It would look
something like this instead.
3/10/2008
Page 40 of 160
14. Click the Edit Display button to get back to edit mode.
15. Take a look at the online tags. Repeat Steps 1 14 but this time for Step 5 we will browse for
the ONLINE tag. This time for step 5 collapse the Offline folder and expand the online folder.
16. Before we close the display, try the numeric input object enhancement out.
17. Single-click on the Test Display button from the tool menu.
18.
0 should appear on the display. Type the number -1 in the field and select the enter key.
19.
20.
Select the Esc key to cancel the changes and 0 will be displayed in the field again.
21. Click the Edit Display button to get back to edit mode.
22. Close the display and when prompted to save your changes select No.
Section 1 is complete. You have the building blocks in place and are ready to start creating your
graphic displays.
3/10/2008
Page 41 of 160
Graphic Displays
o
Libraries
Adding existing HMI Components from the C:\LabFIles\ Lab 15 FactoryTalk View SE
directory into your application
Animation
o
Object Explorer
Tag Placeholders
The Graphics Displays - Adding existing HMI Components into your application must be completed
prior to doing any other sections in this lab.
Graphic Displays
A graphic display represents the operators view of plant activity. The display can show system or
process data, and provide operators with a way to write values to external devices such as
programmable controllers. The elements that make up a graphic display are called graphic objects. The
Objects menu in the Graphic Displays editor (fig. 1) provides simple drawing elements such as line,
rectangle and ellipse, as well as ready-made objects such as push buttons, input and display fields, and
alarm summaries. Use these elements to create visual representations of processes and activities then
animate the display by linking objects to tags so that the appearance of the objects will change as the
values of the tags change.
The graphics editor allows you to easily duplicate objects, reshape or resize objects, and arrange them
in a variety of ways like stacking them, aligning them with each other, spacing them horizontally or
vertically, flipping them horizontally or vertically, rotating them, and grouping them so they behave as a
single object. Graphic objects can be
Copied to the clipboard from another Windows application and then pasted into the graphics
display.
Created by another Windows application and inserted into the graphic display using object
linking and embedding.
Dragged and dropped from another graphic display or library, or another Windows application.
3/10/2008
Page 42 of 160
Libraries
The Graphics Library comes with a number of ready-made graphic displays containing objects that you
can use in other displays
There are many different library objects that you can use within your applications.
Note: any animation that has been attached to an object will be included with it when it is copied into a
display.
Adding existing HMI Components
There are preconfigured HMI components (i.e., Displays and macros) that will be used in this lab. Do
the following to add them to the HMI Server. Almost all the graphics used in this lab came from the
graphics library.
1. Open the C:\LabFiles\ Lab 15 FactoryTalk View SE folder. Select the Start > Lab 15 FactoryTalk
View SE menu item.
2. The folder will open. Move the folder so it is on top of FactoryTalk View Studio and you can still
see the Explorer.
3. Select all files but NOT the folders in the Lab 15 FactoryTalk View SE folder.
3/10/2008
Page 43 of 160
4. Drag and drop all the files over the AF07 HMI Server. The files will be added to the appropriate
locations.
Files ending in GFX are display files and will be added to the Displays folder. Files ending in MCR are
macro files and will be added to the Macros folder located under the Logic and Control folder. Files
ending in KEY are client key files and will be added to the Client Keys folder located under the Logic
and Control folder. Files ending in MDF are Data Log Models and will be added in the Data Log Models
folder under the Data Log folder. You can verify that all the files were added by expanding those
folders.
Animation
Animation is the ability to add logic to a graphic object so that some characteristic of the object will
change when a tag value changes. For example, an object can be made to fill (up, down, left, or right)
or change color in relation to a tag value.
Expression: An expression is a mathematical or logical equation that returns a value. It can contain tag
names, constants and mathematical, relational, logical and/or bitwise operators. A single tag name is
often used for simple expressions.
In Figure 2, the animation dialog shows that expressions are used to animate objects. There is a tab for
each type of animation. If there is a check mark in front of the animation type it means that the selected
object is using that animation. If an animation type is not available for a selected object, the fields on
that animation tab will be grayed out. In the example below, the Fill and Color animations are being
used on the selected object. Selecting a new object while the Animation dialog is opened will update
the Animation dialog for the object that was just selected.
3/10/2008
Page 44 of 160
3/10/2008
Page 45 of 160
Once selected (indicated by a check next to the menu item name), the Object Explorer appears.
The Object Explorer can be resized and moved. You can click on any of the objects listed, and you
will notice that the objects will be highlighted in the display.
3/10/2008
Page 46 of 160
Highlighted
Agitator_Group
The Object Explorer is truly useful when you group items together and want to reference individual
elements within that group.
Grouping is useful when you have common objects that you want to move around or apply
behaviors toward, for example, animation behavior.
Look at groups and animation by using the object explorer
1. Expand and Select the Agitator_Group in the Object Explorer.
3/10/2008
Page 47 of 160
2. Right-click on the Agitator_Group and select the Animation > Touch context menu item.
3.
The Animation dialog will appear and open on the Touch tab.
4. Position windows so you can see both the Object and Animation window.
5. In the Object Explorer, use the mouse or arrow keys to navigate down to item
Agitator_Motor_Group, notice the Touch tab has a check next to it to indicate that Touch
animation is being used and there is an expression for the release action of the
Agitator_Motor_Group. This expression will open the Logix_D2SD faceplate that we added into
our project for the 2 state device called Tank101 Agitator. The display will be positioned at the x and
y coordinates specified.
3/10/2008
Page 48 of 160
The Display command was built using the Command Wizard. The Command Wizard is invoked
by clicking any of the buttons next to the actions. You will use the Command Wizard in the
Global Objects section of this lab to build a Display command. Here is what the Command
Wizard looked like when building this Display command for the Release action
Display Logix_D2SD /T::[SoftLogix]Program:Tank101.Agitator /x 275 /y150
If you want, you can delete the Release action and recreate it with the Command Wizard.
3/10/2008
Page 49 of 160
Tag Placeholders can be used to mark where you want to insert a tag name at run time. A tag
placeholder is a cross-hatch character (#) followed by a number from 1 to 500. Tag placeholders let
you create one display that you can use to represent a number of similar operations. At run time
you supply the tag names associated with the particular operation and these are used in place of
the tag placeholders. You can also use the Tag Substitution menu option to replace tag
placeholders.
To provide tag names at run time do one of these:
- List the tag names in a parameter file in the order they are to be used and reference that
parameter file in a command string for the Display command. The /P parameter for the Display
command allows a relative or absolute reference to a parameter file that contains tag names to be
substituted into the display.
- List the tag names in the command string for the Display command. The /T parameter for the
Display command allows for a list of tags (separated by commas) to be substituted into the display.
6. Use the mouse or arrow keys to navigate down to item TankCoolingTemp_Group, notice the
Touch tab has a check next to it to indicate that Touch animation is being used and there is an
expression for the release action of the TankCoolingTemp_Group. There are actually 2
commands that will be executed by this expression.
Display Logix_PIDE /T::[SoftLogix]Program:Tank101.ProductTempLoop,
::[SoftLogix]Program:Tank101.ProductTempAtune /X10 /Y20;
Display Logix_PIDE /T::[SoftLogix]Program:Tank101.JacketTempLoop,
::[SoftLogix]Program:Tank101.JacketTempAtune /X250 /Y20
We have configured touch animation to launch the faceplate display twice, but with the ability to
show the same faceplate display with different data using parameter passing. The faceplate
displays will also be placed in different positions do they dont overlay each other.
The first display command will open the Logix_PIDE display and anywhere that parameter #1 is
used, it will be replaced with ::[SoftLogix]Program:Tank101.ProductTempLoop and parameter
#2 will be replaced with ::[SoftLogix]Program:Tank101.ProductTempAtune
The second display command will open the Logix_PIDE display and anywhere that parameter #1
is used, it will be replaced with ::[SoftLogix]Program:Tank101.JacketTempLoop and parameter
#2 will be replaced with ::[SoftLogix]Program:Tank101.JacketTempAtune
7. Continue navigating through the Object explorer and look at various animations. Some objects may
have multiple animations defined. For example look at Tank101_AlarmIndicator_Polygon. It has
both Touch and Color animation. Click the tabs to look at those animation properties.
Lets see the animation and parameter passing at work. We are going to test run this display in View
Studio.
3/10/2008
Page 50 of 160
The Configure a FactoryTalk View Client File called AF07 and Run the FactoryTalk View Client File
must be completed prior to doing any other sections in this lab.
Test Display
Being able to test your display within View Studio without having to run it in a Client is a very powerful
feature of FactoryTalk View.
Behavior when test running a display might not always be identical to run-time behavior if changes
made during development are not saved. To make the behavior as close as possible you should save a
display before testing it.
The Microsoft VBA IDE (Visual Basic for Applications Integrated Design Environment) lets you write,
edit, test run, and debug code.
Not everything can be done by test running your display. Some FactoryTalk View commands are
ignored when run in test display mode. For example, screen navigation commands, using parameter
placeholders in a display, and using parameter values in a reference global object will not function in
test display mode. To test these features, run the display in a FactoryTalk View SE Client.
Testing a graphic display in FactoryTalk View Studio is not the same as running the display in the
FactoryTalk View SE Client. Before you deploy an application, it is recommended that you test it in the
FactoryTalk View SE Client, to verify that everything works as intended.
FactoryTalk Alarms and Events Objects
The existing (legacy) HMI Tag Alarm Summary object will not be animated when you run a display in
test display mode. The FactoryTalk Alarms and Events Objects will work in test display mode.
In Section 1, Verify Communications, the Test Display was used for both a FactoryTalk Alarm and
Event and a native FactoryTalk View object.
You can test the objects in a graphic display quickly, by switching to test display mode in the Graphics
editor. Lets try this to animate the TankOverview display.
3/10/2008
Page 51 of 160
1. The TankOverview display should be opened and have focus in FactoryTalk View Studio.
2. From the FactoryTalk View Studio toolbar click on the Test Display button.
3. Observe that the TankOverview graphic begins to animate. Click on the agitator
Now you will need to configure a client file and run the client to finish testing the display.
3/10/2008
Page 52 of 160
FactoryTalk View has multi-tasking capabilities that you can take advantage of when you create
macros. Generally, the commands in a macro are executed in the order in which they are listed, with
one command finishing before the next begins execution.
Some commands (such as Print) finish quickly and the next command can start. Others, such as Set,
take longer. In the case of Set, it does not finish until the message has been sent to the controller. In
cases like that, you can set up the macro so that the next command can be executed before the
previous command is finished. Use the ampersand character (&) to do this.
To invoke the command wizard from the macro file, double-click in the macro, or select Edit
Commands (Ctrl- M).
Observe Pre-configured Macro
These commands will dock displays at the top and bottom of the client window, and set tag values in
the controller.
1. From the Explorer, expand the Macros folder.
This macro will open a header display in a docked area on the top of the client. It will open a footer
display in a docked area on the bottom of the client. Some tag values will be set to 1.
3. Close the ClientStartup macro. If prompted to save changes, select the No button.
Sometimes it is useful to have a single key stroke perform a function or multiple functions in your
application. For example when you press F5 in Internet Explorer you will refresh the page. FactoryTalk
View SE has similar functionality.
3/10/2008
Page 53 of 160
Client Keys allow the operator to interact with the system at run time to do things like change displays
or set tag values. Client keys are defined for an application. They are enabled whenever the application
is running on a FactoryTalk View SE Client.
There are also object and display keys. Object and display keys are defined in the Graphics editor.
They are active only when their associated object or display is. However, object and display keys take
precedence over client keys.
The order of precedence for key animation is: object keys, display keys and client keys. This means, for
example, that if a key has object and client key definitions, when the object has focus at run time and
the key is pressed, the object key action will be carried out and the client key action will not.
Observe Pre-Configured Client Keys
These commands will perform a refresh of your client. This is useful for testing since you may need to
make changes to displays and you dont want to have to close and open the client each time you add or
change something on a display.
1. From the Explorer, expand the Client Keys folder.
3/10/2008
Page 54 of 160
On the release action of function key 5, all displays including docked displays will be closed. The
header display will then be re-opened and docked at the top and the footer display will be docked at
the bottom of the client.
3. Close the ClientKeys. If prompted to save changes, select the No button.
Configure Client File
The FactoryTalk View Client can be launched from FactoryTalk View Studio.
1. Select the SE Client button on the tool menu.
2. When the Launch FactoryTalk View SE Client dialog opens select the New button.
The FactoryTalk View SE Client Wizard will open.
3. Click the New button.
4. Type AF07 for the name of the configuration file and click the Next button.
Type AF07
5. Select the Local radio button and click the Next button.
Select Local
and
3/10/2008
Page 55 of 160
6. Select the AF07 application, leave the defaults, and click the Next button.
Select AF07
7. Select the TankOverview display as the initial display, select the ClientKeys key file as the
Initial client key file, select the ClientStartup macro as the Startup macro, and click the Next
button. Note: If you used parameters in the initial display, they would be specified in the Display
parameters field. If you use a network application, the area would need to be specified for the initial
display.
Select TankOverview
Select ClientKeys
Select ClientStartup
3/10/2008
Page 56 of 160
8. Type AF07 for the title bar text, check the maximize window option, and click the Next button.
Type AF07
Check this
Maximize Option
9. Leave the defaults for auto logout and click the Next button.
and
10. Leave the default to save configuration and open FactoryTalk View SE Client now and click the
Finish button.
and
The FactoryTalk View Client will start with the specified configuration.
3/10/2008
Page 57 of 160
Run Client
The AF07 application is now running in a FactoryTalk View SE Client window. The startup macro
docked displays in 2 areas. The header display contains an alarm banner and is located at the top of
the client window; the footer display contains navigation buttons and is located at the bottom of the
client window.
Docked Displays
At run time, graphic displays can be docked to an edge of the FactoryTalk View SE Client window,
allowing an operator to gain access to certain displays at all times. Docked displays cannot be
accidentally closed by the operator and cannot have other graphics placed on top. They will, therefore,
always remain visible to the operator.
For example, you might consider docking:
Navigational menus, that allow the operator to move among displays in an application.
Headers or banners, that provide specific information to the operator, such as the current users
name and area, or information about alarms.
Control panels, that contain standard buttons for special purposes, such as changing users, closing
open windows, or sending information to a maintenance team.
Top edge:
Bottom edge:
3/10/2008
Page 58 of 160
6. Observe that it will not overlay the docked areas and scroll bars will appear so the display will still
be visible.
7. Move the Tank Overview display so the close button is visible and close the display.
8. Select the Tank Overview button on the footer display to open the Tank Overview display. Notice
how it is sized to fit in the main viewable area of the docked displays.
Verify Client Keys
1. Go back to FactoryTalk View Studio
3/10/2008
Page 59 of 160
Remember that these navigation commands did not function when test running the display in
FactoryTalk View Studio.
3/10/2008
Page 60 of 160
Tags
Derived Tags
Tags
A tag is a logical name for a variable in a device or in local memory. For example, a tag can represent a
process variable in a network device.
Indirect Referencing or HMI Tags
Tags defined within FactoryTalk View are referred to as HMI tags; in addition to the tags value, they
provide additional properties for alarms, security, and data manipulation.
1. From the Explorer, double-click on Tags located under the HMI Tags folder.
2. This is where you can create, maintain, and remove HMI Tags.
3. Close the Tags Editor.
Direct Referencing
FactoryTalk View also supports direct referencing of values directly from a device such as a
ControlLogix controller without creating a corresponding entry in the HMI tag database, eliminating tag
duplication and tag management. Direct referencing of device tags is a defining feature of Rockwell
Automation Integrated Architecture. Tags added to the controller are available immediately without
adding the tag to the HMI database, eliminating tag management. An application can use a mix of HMI
tags and device tags.
FactoryTalk Tag Browser
FactoryTalk View has a FactoryTalk tag browser that allows you to access device tags while
configuring an application rather than typing the tag name. You can browse while online and connected
to a device, or you can browse for tags from an offline file, for example, a controller program file. The
Tag Browser shows the root folder of the application and folders containing the tags for the
applications HMI and data servers. For a network application, the Tag Browser also shows a folder for
each area, in addition to the root folder.
3/10/2008
Page 61 of 160
Areas found in
FactoryTalk Directory
All tag names from all OPC 2.0 servers in the application will be available from the FactoryTalk
directory. This information is served in a hierarchical fashion, organized by areas. So, in this example
you see the areas (Plant Area 1, Plant Area 2). Within those areas, you can see the topic names
provided by the OPC servers, the online/offline control program, and the tags within them. You would
choose the tag name you want to use right from the FactoryTalk tag browser.
An advantage of FactoryTalk is that it provides an aggregate view of all tags from any data server. This
includes traditional HMI tags that are available through the tag browser that browses the FactoryTalk
directory. So, any RSLinx, OPC, or traditional HMI tags can all be browsed within the same tag
browser. Contrast this to a traditional system, where OPC servers can only be browsed individually, or
where an HMI tag database shows a flat list (non hierarchical) of all the tags in the system. The tags in
the directory can return references to ControlLogix tags, PLC tags (5/500), FactoryTalk View tags, and
third-party OPC server tags without the need to download or import the tags with an intermediary step.
Structured Tag Support in FactoryTalk Tag Browser
The tag browser has been enhanced to let you select a structure tag in the left-hand pane of the object
browser and return a partial tag identifier to the editor that launched the browser. This structure tag can
be assigned to a faceplate object to supply values to multiple objects.
In Section 1, Verify Communications, the FactoryTalk Tag Browser was used to verify access to offline
and online tags when we added tags to a numeric input control. In Section 9 Global Objects - Create
multiple reference objects in a display, and view the display, you will browse for a structured tag of type
PIDE and PIDE_Autotune.
3/10/2008
Page 62 of 160
Derived Tags
A derived tag is an analog, digital, or string tag whose value is determined through the evaluation of an
expression. An expression can be simply a tag name or it can be an equation made up of tag names,
mathematical and logical operations, special functions and If-Then-Else logic. The current value of a
derived tag is written to the tags data source.
A derived tag file consists of a number of derived tags and a maximum update rate for them. At runtime
you can have multiple derived tag files active at once (up to 20 derived tag files, each containing up to
1000 derived tags).
Writing directly to a derived tag is highly discouraged because the tag value is determined by a given
expression. If a derived tag is written to, the write value is merely overwritten as soon as the defined
expression is evaluated again.
1. From the Explorer, double-click on Derived Tags located under the Logic and Control folder.
2. This is where you can create, maintain, and remove your Derived Tags.
3. Close the Derived Tag Editor.
3/10/2008
Page 63 of 160
Expressions
Device-Based Alarms
Tag-Based Alarms
Alarming
Alarms are an important part of plant control applications because they alert operators when something
goes wrong. Often, it is also important to have a record of alarms and whether they were
acknowledged.
FactoryTalk View SE supports the existing traditional HMI tag alarm system and the FactoryTalk
Alarms and Events system. The choices you make will depend on factors such as the design of your
application, the processes you need to monitor for alarms, the types of devices used in the application,
and whether you want to build alarm detection into those devices.
Traditional HMI Tag Alarm System
In FactoryTalk View Studio, you can set up a complete alarm system. At run time, alarm monitoring
occurs at the HMI server. If alarms are detected tag values outside the configured limits - notification
is sent to connected FactoryTalk View SE clients, where operators can view and acknowledge the
alarms. This is a traditional HMI tag alarm system.
An HMI tag alarm system only detects alarms set up for tags in an HMI servers tag database. HMI tag
alarm detection does not include FactoryTalk alarms. Use a traditional HMI tag alarm system if your
application uses HMI tags for other purposes, and you want to monitor these tags for alarms.
FactoryTalk View SE Clients receive HMI tag alarm information by way of the FactoryTalk View SE
Servers (also called HMI servers) that contain the HMI tags.
HMI tag alarm data is not managed by FactoryTalk Alarms and Events services. To monitor and
respond to HMI tag alarms, you must use the HMI tag alarm displays and logs available in FactoryTalk
View SE.
3/10/2008
Page 64 of 160
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
servers 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
View
Administration
Console
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
Yes
Yes
No
Yes
Yes
No
Yes
Yes
No
No
Yes
No
Yes
Yes
No
Yes
Yes
No
No
Yes
No
No
No
FactoryTalk
View
Studio
3/10/2008
Page 67 of 160
HMI Alarm Tags are created using the HMI Tag Editor or using the Tag Import Export Wizard. The
HMI Tag Editor is invoked from the Explorer by double-clicking on the Tags icon under the HMI
Tags Folder.
The HMI Tag Alarm Summary object can be added to a display by selecting the Objects >
Advanced > HMI Tag Alarm Summary menu item.
or by selecting the HMI Tag Alarm Summary button on the tool menu
Library objects are located in HMI Tag Alarm Information library display
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
Device-based alarms are configured in the control program and enabled in the Rockwell
Automation Device Server (RSLinx Enterprise). This was done in Section 1 Add a data server.
Tag Alarm and Event Server can be added to the application by right-clicking on the application
and selecting the Add New Server > Tag Alarm and Event Server context menu item.
Tag based alarms can be created and configured with the Alarm and Event Setup Editor by
double-clicking on the Alarm and Event Setup icon under the Alarm and Event Tag Server in
the Explorer.
or tag based alarms can be imported and exported by right-clicking on the Tag Alarm and Event
Server and selecting the Import and Export context menu item.
Banner, Summary, Log Viewer, and Status Explorer are located under Objects > Alarm and
Event > Banner, Summary, Log Viewer, and Status Explorer
Library objects are located in the Alarm and Event library display
3/10/2008
Page 69 of 160
2. Select a row in the Banner and click on the run alarm command
on a row in the Banner.
button or double-click
button.
3/10/2008
Page 70 of 160
9. Click on each tab to look at all the properties. A couple of things to point out here:
General
The Run Alarm Command will be invoked when the operator double-clicks on an alarm in the
Banner
Columns
3/10/2008
Page 71 of 160
Resize columns
Reorder columns
Status Bar
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
10. Feel free to make configuration changes and perform a Test Display or save your changes and
use the F5 key in the Client to refresh the header display.
11. Close the Header display in FactoryTalk View Studio when you are done.
Alarm and Event Summary (AlarmSummary and TankAlarmSummary displays)
Use the Alarm and Event Summary object, embedded in a FactoryTalk View graphic display, to
acknowledge, disable, suppress, filter, and sort alarms during run time.
Run Time
1. From the AF07 client, click the Summary button in the footer display.
2. The Alarm Summary display is opened.
3. Select a row in the summary list to see details about the alarm.
4. Mouse over the toolbar on the Summary to see what the configured buttons do (read the tool tips).
5. Select a predefined filter called Pump or Tank101 from the drop down list
6. Observe that the list and count are updated in the Summary.
7. Click the Tank101 Summary button in the footer display.
8. Notice that only alarms for Tank 101 are displayed and there is no way to modify the filter at
runtime.
3/10/2008
Page 72 of 160
9. If you dont see any alarms in the Tank101 Summary, Click the Tank Overview button in the footer
display. Enter 100 in the input field next to the Manual Valve Opening Slider object.
10. Click the Tank101 Summary button in the footer display. You should now see alarms.
Design Time
11. From the Explorer, double-click on the AlarmSummary display to open it.
12. Double-click on the Alarm and Event Summary Design View object in the display and the Alarm
and Event Summary Properties will open.
13. Click on each tab to look at all the properties. A couple of things to point out here:
Appearance
The Run Alarm Command will be invoked when the operator double-clicks on an alarm in the
Banner
Columns
Resize columns
Reorder columns
Reorder buttons/panes
Event Subscriptions
This Summary object will subscribe to all events with any priority
Display Filters
This Summary object has preconfigured filters. These filters were preconfigured using the Alarm
Class field that was configured for the alarm.
Sort
3/10/2008
Page 73 of 160
States
Configure text and background colors for the alarm states and priorities
Behavior
The Run Alarm Command will be invoked when the operator double-clicks on an alarm in the
Summary
3/10/2008
Page 74 of 160
Design Time
1. From the Explorer, double-click on the AlarmLogViewer display to open it.
2. Double-click on the Alarm and Event Log Viewer Design View object in the display
and the Alarm and Event Log Viewer Properties will open.
3. Click on each tab to look at all the properties. A couple of things to point out here:
General
Columns
Resize columns
Reorder columns
Toolbar
Reorder buttons
Display Filters
This Log Viewer object has preconfigured filters. These filters were preconfigured using the
Alarm Class field that was configured for the alarm.
Notice that there is not an Event Subscription tab. This is a historical view of what is in the log
(database).
4. Feel free to make configuration changes and perform a Test Display or save your changes and
use the button on the footer display to open the display again to see your changes.
5. Close the AlarmLogViewer display in FactoryTalk View Studio when you are done.
Alarm Status Explorer (AlarmStatusExplorer)
Use the Alarm Status Explorer object, embedded in a FactoryTalk View graphic display, to enable or
disable alarms and suppress or unsuppress alarms.
Run Time
1. From the AF07 client, click the Status Explorer button in the footer display.
2. The AlarmStatusExplorer display is opened.
3. Mouse over the toolbar on the Status Explorer to see what the configured buttons do.
4. Select a row in the list and select the show details for selected alarm
3/10/2008
button.
button.
9. Type *tank101* in the name field for the Alarm source filter and click the Apply Filter button.
10. Observe the list is filtered to show only alarms that contain tank101.
3/10/2008
Page 76 of 160
3/10/2008
Page 77 of 160
1. From the AF07 client, click the TankOverview button in the footer display.
2. The TankOverview display is opened.
3. Observe the alarm indicators
4. The alarm indicators should be changing colors. If they are not, slide the Manual Valve Opening
up to about 90 and then wait a few seconds. Slide it back down to about 20 and then wait. This
should trigger some alarms. The alarm indicators should change colors.
Design Time
1. From the Explorer, double-click on the TankOverview display to open it.
2. Open the Object Explorer by selecting the View Object Explorer item from the menu,
3. Expand the Indicator_Group in the Object Explorer.
3/10/2008
Page 78 of 160
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
When the alarm condition is true, the alarm enters the In Alarm state. When the alarm condition is
false, the alarm enters the Normal or Out of Alarm State.
Analog Alarm (ALMA)
An analog alarm can be configured to monitor for two types of alarm conditions: Level and Rate of
Change.
A Level alarm monitors an input for alarm conditions that go In Alarm when the input value goes above
or below predefined limits. When defining a level alarm, you can configure up to four alarm level
conditions each with limits (sometimes called thresholds), a severity and alarm message. The
supported alarm conditions are:
o
High (HI)
Low (LO)
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
Configuration Options
Lets 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
OR
Click the Logix 5000 Alarms button on the footer menu of the AF07 client
After clicking the button, the FactoryTalk View command to open RSLogix 5000 will appear in the
diagnostic list.
It will take a few seconds for RSLogix 5000 to start and open to the routine. If the Quick Start page
appears, close or hide it.
2. Go online with the controller by selecting the Communications > Go Online menu item.
button.
4. Navigate to the Tank101 routine if you are not already there (double click to open).
3/10/2008
Page 82 of 160
3/10/2008
Page 83 of 160
2. At the bottom right of the Level Simulation worksheet you should see an ALMA instruction. Click
on the next to the ALMA to open the property pages.
3. Observe the Configuration and Messages property pages for the ALMA instruction
3/10/2008
Page 84 of 160
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 servers
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
Security
Commands
Display 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 users identity, and whether a request for service actually
originated with that user.
User authorization verifies the users 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 users 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.
3/10/2008
Page 87 of 160
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
7. The New User dialog will open. Type Tank101Operator for the user name, check the user
cannot change password, check the password never expires, and type password for the
password.
Type Tank101Operator
Type password
Type password
button.
9. You will be back at the New User Group dialog. Tank101Operator should be in the Members list:
3/10/2008
Page 89 of 160
Resources
The objects in a FactoryTalk system for which actions can be secured. Each FactoryTalk product
defines its own set of resources. For example, some products might allow you to configure security for
resources such as servers in an area. Other products might allow you to configure security for logic
controllers and other devices. FactoryTalk Administration Console allows you to configure security for
the System folder and its contents, applications, areas, and many other items. Do not confuse
resources with resource groupings: resource groupings allow you to group together control hardware
represented in the Networks and Devices tree, and then configure security for the grouping in one step.
Lets specify that our operators can not perform certain alarming actions.
1. From the Explorer, right-click on AF07 and select the Security context menu item
2. Security Settings for AF07 dialog appears. Click the Add button.
3. The Select User or Group dialog appears. Select the Operators and click the OK button.
4. While the Operators group is selected, expand the Alarming action, Check the Deny check box
next to Alarming and check the Allow checkbox next to Acknowledge.
You are only allowing the operators to acknowledge FactoryTalk Alarm and Events Alarms. They
can not perform the other actions.
3/10/2008
Page 90 of 160
3/10/2008
Page 91 of 160
Or
Select the Settings > Runtime Security. menu item.
button.
button.
8. The Select User and Group dialog is closed and the Operators group is added to the Users list.
While it is highlighted, expand the FactoryTalk View Security Codes actions. Select the Deny
checkbox for A.
3/10/2008
Page 92 of 160
3/10/2008
Page 93 of 160
2. The Runtime Secured Commands dialog is opened. Expand the window to see all the fields.
3. Click in a cell in row 2 to select it.
3/10/2008
Page 94 of 160
menu item.
2. Click the
3. Login as the new user Tank101Operator using the password of password. Note user name is
not case sensitive.
4. The information message User tank101operator has been logged in. will appear in the
diagnostics list.
3/10/2008
Page 95 of 160
5. Click on the
button.
6. What happened? Nothing! The message Currently logged-in user does not have security
access to AlarmStatusExplorer. will appear in the diagnostics list. The display setting security
worked!
7. Click on the
11. The Alarm Summary is displayed. But what do you see? There is a suppress and an Alarm Status
Explorer button. This display didnt hide the buttons from the operator or secure the display from the
operator.
Note: If you dont see these buttons you may have changed your configuration in the Alarming
section.
12. Select a row (alarm) in the summary list and click on the suppress
button.
13. When the Suppress Alarm dialog comes up, click the suppress button to confirm that you want to
suppress the alarm.
14. What happened? There is a message right? The message should read something like Failed to
Suppress Alarm alarm [alarm name] Tank101Operator does not have Suppress/Unsuppress
permission. The message will appear in the diagnostics list. If the option to display errors from
operator action in a dialog was checked when configuring the summary (which it was originally), a
dialog with the message will appear. If the message dialog appears, click the OK button.
The actions security worked!
3/10/2008
Page 96 of 160
button.
16. What happened? The Alarm Status Explorer dialog opened. This is because it is not the same as
the display that we configured a security code on.
17. Select an alarm in the list and then click on each of the first 4 buttons (enable alarm, disable
alarm, suppress alarm, unsuppress alarm) to try to perform these actions. Observe what happens.
The actions are secured and the operator can not perform them. So even though the operator was
able to access the Alarm Status Explorer from the Summary display because maybe the HMI
Designer forgot to hide the button, he still could not perform actions that he didnt have permissions
for.
18. Close the Alarm Status Explorer
19. Right-click on an alarm in the summary and select one of the Ack context menu items.
20. The alarm will be acknowledged because the tank101operator has permission to perform that
action.
3/10/2008
Page 97 of 160
Runtime Exploration
Data Logging
Trending
Configuration Exploration
Historical Trending
Runtime Trending
You will be using the TankDataLogging display and Tank101 data log model that you added in Section
2 Adding existing HMI Components.
Runtime Exploration
Data Logging
Data logging is a FactoryTalk View component that collects and stores tag values. You specify which
tag values to collect, when to collect them, and where to store them by defining a data log model.
The HMI tag database does not store actual tag values; it only defines which values are to be collected.
The values themselves are stored on a given HMI server. When the HMI server is turned off, the value
table is cleared (excluding retentive tags). To have a permanent record of tag values, log them to the
data log file on disk. Remember: controller tags will keep their value when an HMI server is powered
down because theyre located within the controller; theyre not HMI (or memory) tags stored on the
server itself.
To log tag values to disk, you create a data log model and specify the tags that are to be logged. This is
done in the Data Log Model editor. The values can also be logged to an ODBC-compliant database.
An application can have up to 20 data log models running at a time. The maximum number of tags that
can be logged by one data log model is 10,000.
Trending
A trend is a visual representation, or chart, of current or historical tag values. A trend provides
operators with a way of tracking plant activity as it is happening. The trend object displays real-time
data and historical data from the FactoryTalk View Site Edition data logs. Pens on the run-time chart
represent data from the tags and expressions that you add to the trend object. The trend object
provides extensive, flexible run-time control. You can add pens, toggle between isolated and nonisolated graphing, specify unique line settings, plot one variable against another in XY plots, and print
chart data.
3/10/2008
Page 98 of 160
Historical Trending
o
Historical Trending is when a trend polls data from a data log that is previously
configured. This will allow the user to browse through a timeline to look at the data over
a given period of time.
Runtime trending
o
A Runtime trend displays data trends directly from the processor. The trend will start
trending its runtime data from the time its first loaded on the display.
Viewing a Trend
1. Go to the AF07 client
button.
There was an attempt to connect to an ODBC data source that failed, Tank101 is logging to a
secondary path that is a file. You will take a look at why this happened in the configuration section.
7. Notice the trend starts to update.
8. Click the
3/10/2008
15. Observe the trend. Find the HMI Time that you noted if it is not visible by using the buttons
under the trend.
The trend displayed is configured to display historical data. This means that the trend reads both
Real-time data (occurring now) and Historical data (read from data log files).
Configuration Exploration
Data Log Models
1. From the Explorer, navigate to AF07 > Data Log > Data Log Models > Tank101.
2. Double-click on Tank101
3/10/2008
3. The Tank101 Data Log Model dialog opens to the Setup tab.
This is a pre-configured
System DSN pointing to
a database that is called
FactoryTalk.
You can set up logging to log to a file set or to log to any database that you can connect to with
ODBC.
The data log model can be configured to be stored as a file set or an ODBC database. Notice that
this data model is being stored in an ODBC database. There is a System Data Source Name (DSN)
called FactoryTalk that points to a SQL Server Express database called FactoryTalk.
An ODBC System DSN stores information about how to connect to the indicated data pointer. If you
want to see how the System DSN was configured, Select the Start > Settings > Control Panel menu
item. From the Control Panel, select Administrative Tools, and then select Data Sources (ODBC).
Look at the System DSN tab and the DSN called FactoryTalk.
There is a database and a pointer to the database but the tables to store the data have not been
created. This was done to demonstrate what happens when the connection to the database fails
and there is a backup path enabled.
4. Click the Create Tables button if you havent already done so. You should get a FactoryTalk View
Datalog Editor message saying ODBC tables were successfully created. Click the OK button.
3/10/2008
This configuration tab is used to set the file location of the data logs. This is useful if you have a
distributed network set up; you will want to store the logs to one common location instead of on
each individual HMI server on the network.
Notice that he Enable ODBC backup path was selected and a logging path was specified. This is
why you were able to see the historical data in the trend display even though the connection to the
ODBC failed.
The tables are created and the connection should be successful now. At some point you will see
messages like
Click the Advanced button, and notice the settings. SwitchBack is set to 10 minutes.
6. Click the File Management tab
This configuration tab is used to configure how long you want to keep logging to individual files until
you either create a new file or delete older files.
7. Click the Log Triggers tab
This configuration tab is used to decide how often and based upon what event the log should be
updated.
3/10/2008
Trigger is On Change
Heartbeat of 2 minutes
3/10/2008
5. Notice that the Model column has Tank101 which is the data model that was created.
These pens were added by selecting the Add Pen(s) from Model button. The Configure Tags
dialog opened. The Add All button was selected to add all the tags. Then the OK was clicked to
accept the changes.
6. Click the Cancel button on the Trend Properties dialog to close the dialog.
8. Click the Action tab and look at the Release action. This command DataLogOn Tank101 starts
the data logging for the model.
11. Click the Action tab and look at the Release action. This command DataLogOff Tank101 stops
the data logging for the model.
3/10/2008
4. Microsoft SQL Server Management Studio Express will open and you will be prompted with a
Connect to Database Engine dialog.
Click the Options >> button.
Click the Connection Properties tab.
Type FactoryTalk in the Connect to database field.
Click the Connect button.
2. Click Connections
Properties Options
3. Type
FactoryTalk
4. Click the
Connect button
1. Expand Options
3/10/2008
button.
button.
9. Scroll to the bottom of the list and notice the number of rows and the Data and Time. Did the row
count change? Have we gotten any new rows? We are only logging on change.
10. Go to the AF07 client
Query window.
button.
20. Scroll to the bottom of the list and notice the number of rows. Did the row count change? Are we
getting new rows? Yes, it should have.
3/10/2008
button.
29. Slide the Manual Valve Opening Slider to the top. Wait about 20 seconds.
30. Slide the Manual Valve Opening Slider about half the way down. Wait about 20 seconds or
until the Level is OK.
31. Slide the Manual Valve Opening Slider to the bottom. Wait about 20 seconds.
32. Slide the Manual Valve Opening Slider about half the way down.
33. Go back to the
34. Click the Execute
Query window.
button.
35. Scroll to the bottom of the list and notice the number of rows. Did the row count change? What is
the date and time of the last row? You should have not received any new records after you stopped
the data logging.
36. Close the Microsoft SQL Server Management Studio Express. If prompted to save changes,
select the No button.
3/10/2008
FactoryTalk Diagnostics
Diagnostics List
Diagnostics Viewer
Diagnostics Setup
o
3/10/2008
after they occurred. New messages do not appear in the Diagnostics Viewer. A refresh can be done to
reload the messages. Messages that appear in the Diagnostic Viewer are time stamped so you know
when they occurred.
Diagnostics List
The Diagnostics List can be displayed in a FactoryTalk View Studio window, FactoryTalk View SE
Client, and FactoryTalk View Administration Console window. You have used the FactoryTalk View
Diagnostics List in earlier sections of this lab. You can clear messages from the Diagnostics List by
selecting a row or multiple rows and clicking the Clear button or by clicking the Clear All button.
Removing a message from the Diagnostics List does not delete the message from the Diagnostics log.
Removing a message from one Diagnostics List does not remove it from another Diagnostics List. I.e.,
removing a message from the View Studio window does not remove it from the View Client window.
When the application (View Studio, View Client, or View Administration Console) starts new messages
begin to get logged to the list. Old messages will be removed from the list as new ones come in and the
message limit has been reached. When the application is closed, the list is cleared.
Diagnostics Viewer
The FactoryTalk Diagnostics Viewer allows you to view both local messages and messages retrieved
and merged from multiple products running on multiple computers logging to multiple destinations.
Open the Diagnostics Viewer
1. From Explorer, select the Tools > Diagnostics Viewer menu item
Or
select the Start > Diagnostics Viewer menu item.
2. The FactoryTalk Diagnostics Viewer will open.
When the Diagnostics Viewer window is open, new messages do not appear automatically. To
refresh the view and reload messages, press the F5 key or click the Refresh button.
3. Mouse over the toolbar and look at the menus to see the operations you can perform with the
Diagnostics Viewer.
Filter Diagnostics List
1. Select the View > Options menu item.
2. On the General tab of the Properties dialog, make sure message source is set to Local Log.
3/10/2008
tab on the Properties dialog. Move the Properties dialog so that you can see
3. Click the
the items in the Diagnostic Viewer.
1. Select the Audience
3. Select Equals
5. Select the
OK button
4. Select Developer
2. Click the
Add Where Condition) button
3. Select Equals
4. Select Operator
5. Select the
OK button
3/10/2008
9. Select the Audience = Operator select records where condition and click the Remove button.
3. Select Contains
4. Type tank101
5. Select the
OK button
2. Click the
Add Where Condition) button
Diagnostics Setup
Open the Diagnostics Setup
1. Run the Diagnostics Setup from within the FactoryTalk View Studio. From the Tools menu, select
the Diagnostics Setup menu item
2. The FactoryTalk Diagnostics Configuration dialog will open
3/10/2008
2. Select the Message Routing setup and then select the FT View Diagnostics List
Messages that were intended for Operator and Engineer audience that were of type Error, Warning,
and Info appeared in the FactoryTalk View Diagnostics List.
Configuring the Local Log
You just used the Diagnostics Viewer to look at the local log. Look at the configuration.
3/10/2008
The local log is a file that exists on this computer. There are options for overwriting events, log size,
and an option to clear the log.
2. Select the Message Routing setup and then select the Local Log
Messages that were intended for Developer audience were not logged to the Local Log so that is why
we did not see any.
3/10/2008
3. Change the Message Routing for the Local Log to include all message types for the developer
audience. Check all the options in the Developer row.
3/10/2008
Microsoft Access
Oracle
Some types of information cannot be logged to an ODBC database destination. This includes:
any additional database fields not included in the ODBC table format, that a FactoryTalk product
might use. Even if you create the additional fields manually, nothing will be logged to them. The
additional information logged by a FactoryTalk product will, however, appear in the Local Log on
the computer where the product is installed.
any messages where the audience type is set to Secure, or the severity type set to Audit.
Secure messages can only be logged by the FactoryTalk AssetCentre software product to the
FactoryTalk Audit Log.
Browse
3/10/2008
3. Click the button next to the data source name. When the Select Data Source dialog opens,
click the System Data Source tab. Click the FactoryTalk data source name.
Select the System
Data Source tab
Select the
FactoryTalk Data
Source Name
Type
FTDiagnostics
6. Click the OK button when you get the message that The table FTDiagnostics was successfully
created.
3/10/2008
8. Select the Message Routing setup and then select the ODBC Database. Check all the options in
the Developer row.
Notice that Audit messages can not be routed to the ODBC destination.
9. Click the OK button.
View the ODBC Log
10. Go to the Diagnostics Viewer
11. Select the View > Options menu item. Move the Properties window so you can view the list.
12. Click the ODBC Database as the message source.
13. Click the OK button.
14. Notice the list is empty because nothing has happened since we created this destination.
15. Go to the AF07 client; click the clear all button in the Diagnostics List.
16. Click on the Tank Overview button.
17. Type 85 in the Manual Valve Opening input field and select the enter key.
18. Notice a download message is logged in the Diagnostics List.
3/10/2008
button.
22. If you queried the database, you would see it has been updated
3/10/2008
Global Objects
Global Objects
FactoryTalk View global objects allow you to link the appearance and behavior of one graphic object to
multiple references of that object in the same application.
Global objects are created on global object displays. In FactoryTalk View Studio, you create global
object displays in the Global Objects folder, the same way you create standard graphic displays in the
Displays folder.
Changes you make to the base object are reflected in all of the reference objects linked to it the next
time a display containing the reference objects are opened, or refreshed by closing and reopening
them.
Global Object Parameters
Global object parameters let you customize each reference global object instance with a specific tag(s)
for that instance without having to break the link to the base object's tags and expressions. This means
each reference object can have a unique data source(s), and still be able to be updated with changes
to other aspects of the base global object.
Parameter passing is dynamic, meaning it happens at runtime on the client. Global object parameters
give you an alternative way of using parameter passing at design time.
3/10/2008
9. Open the Global Object Parameters dialog on the 1st reference object - Right-click on the 1st
reference object and select the Global Object Parameter Values context menu item.
3/10/2008
10. Assign structured tags for #1 - Click on the button under the Tag column for #1.
When the Tab Browser opens navigate to ::[SoftLogix]Program:Tank101.ProductTempLoop
13. Click the OK button on the Global Object Parameter Values dialog.
3/10/2008
14. Repeat the 5 previous steps, steps 9 13 for the 2nd reference object. Assign these structure tags
#1 is assigned ::[SoftLogix]Program:Tank101.JacketTempLoop
#2 is assigned ::[SoftLogix]Program:Tank101.JacketTempAtune
15. Configure Display Settings with all the defaults except for these:
Display Type use On Top
type the text Temp Loops for Tank101 Product for the Title Bar
Notice the Insert Variable button under the title bar text.
3/10/2008
Parameter Enhancements
Added parameter enhancements that provide support for embedded variables in tooltips and title bars;
literal numbers and strings in the embedded variable syntax; and display of right-most characters in
embedded string variables.
Feeling adventurous? Try using this to show the loop names in the title bar like the Logix_PIDE
display. Remember there are 2 loops in your display.
16. Save the Display
17. When prompted for a component name type Tank101TempLoops
18. Perform a Test Display. What happens? Lots of failed to resolve messages.
You can use the test display mode to test global objects. However, this global object uses parameter
placeholders and even though we set the values they are ignored. Remember, not all FactoryTalk View
commands work in test display mode and parameter placeholders are ignored.
19. Close the Tank101TempLoops display.
Now you will have to test the display in the client. But first you need to launch the display.
3/10/2008
4. Remove the release action and click on the button to open the Command Wizard.
5. Step 1 of Command Wizard, Select the Display command, click the Next button.
3/10/2008
6. Step 2 of Command Wizard, Select the Tank101TempLoops display, check the /X and type 10,
check the /Y and type 20 which is where the first display was opening. Click the Finish button.
\
7. Verify the release action looks like this
4. Mouse over the temperature and click for the touch animation.
5. What happens? Your new display should be opened and you should see values and animations for
both loops.
3/10/2008
3/10/2008
The placeholder parameters can be used in any object contained on the global object display but the
Global Object Parameter Definitions are assigned at the top level group.
5. Right-click on the PIDE_Global_Group and select the Global Object Parameter Definitions
item in the context menu.
The Global Object Parameter Definitions dialog is opened. Observe the name and definitions. This is
what you saw when assigning values in the reference global object.
6. Click the Cancel button to close the Global Object Parameter Definitions dialog.
A reference object has properties that link it to its base object. When a reference object is created, the
global object defaults are used to set how the reference object will be linked to the base object. These
properties can be modified after the object has been created. You can choose to break the link to the
base object after the reference object is created. If you break the link the object will become a graphics
object and will no longer reference the base object.
The values of the Link properties determine whether aspects of the reference objects appearance and
behaviors are defined by the base object, or by the reference object itself.
LinkAnimation
The LinkAnimation property determines whether the reference object uses the animation set up for its
base object.
Set up the LinkAnimation property of the reference object by selecting:
Link with expressions, to use the animation, including expressions, set up for the base object.
Link without expressions, to use the animation, excluding expressions, set up for the base object.
This means you can set up the expressions for the reference object separately.
Do not link, to set up animation and expressions for the reference object separately.
3/10/2008
For a Button push button object, the LinkAnimation property determines whether the reference object
uses the press, release, or repeat actions set up for the base object. This is true when you select either
Link with expressions or Link without expressions.
LinkConnections
The LinkConnections property determines whether the reference object uses the connections set up for
its base object.
Set up the LinkConnections property of the reference object by selecting:
In FactoryTalk View Site Edition, a reference object that is a tag label, trend, or Button push button with
an action other than Command, always uses the connections assigned to its base object. You cannot
set up connections for these reference objects separately.
LinkSize
The LinkSize property determines whether the reference object uses the height and width set up for its
base object.
Set up the LinkSize property of the reference object by selecting:
True, to use the height and width set up for the base object.
False, to set up the height and width of the reference object separately.
If you attempt to resize a reference object with its LinkSize property set to True, the object will snap
back to its original size.
Look at the Global Object Defaults
1. From Explorer, select the Edit > Global Object Defaults menu item.
3/10/2008
4. Click different objects in the Object Explorer and observe the properties.
5. When you are done close the display.
3/10/2008
12. Mouse over the temperature and click for the touch animation.
13. Notice two reference objects have the change.
3/10/2008
3/10/2008
5.
6. In the String Variables dialog, select the Literal string option, enter #3 for the literal, select the
Fixed number of 6 characters, and the show * option.
3/10/2008
9. Type EU_Text for the name, enter 16 for height, 43 for width, 292 for top, 112 for left position.
13. Right-click on the PIDE_Global_Group in the Object Explorer, select the Global Object
Parameter Definitions context menu item.
3/10/2008
14. Enter #3 for the Name and PV engineering units (literal string with no spaces) for the
description.
3. Mouse over the temperature and click for the touch animation.
4. Notice two reference objects have the change but #3 is showing.
The parameter has to be passed to the reference objects.
Pass the new #3 parameter value from reference object
1. From Explorer, open the Tank101TempLoops.
2. Right-click on the 1st reference object, select the Global Object Parameter Values context menu
item. Enter Deg-C for the #3 value. Click the OK button.
3. Right-click on the 2nd reference object, select the Global Object Parameter Values context menu
item. Enter Deg-C for the #3 value. Click the OK button.
4. Save and close the display.
Verify engineering units are displayed (2nd try)
1. Go to the AF07 Client
2. Close all displays containing the Logix_PIDE reference objects
or
Click the Close Displays button. Click the Tank Overview button.
3. Mouse over the temperature and click for the touch animation.
3/10/2008
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. Use Tag Substitution to find and modify the references or you can skip to the
next section.
3/10/2008
3/10/2008
Whenever possible, avoid creating global objects that are too complex. Object complexity is
measured by the number of graphic objects contained within a global object, the number of
expressions and animations associated with a global object, the number of global object
connections, and combinations of these variables. If a complex global object is required, avoid
creating a large number of instances of this object on one standard display.
Do not create a large number of base global objects on a single global object display. Organize
global object displays in such a way that the majority of base global objects required by a
specific standard display, reside on the same global object display.
If a standard display contains ten or more complex global objects and is being accessed
frequently, set its Cache After Displaying property to Yes. This is done in the Properties tab of
the Display Settings dialog box
Important: While the Cache After Displaying property is in effect, design-time changes to the
base object will not be picked up by the corresponding reference object until the FlushCache
command is issued, or an SE Client session is closed and restarted.
3/10/2008
Language Switching
Translate strings
Develop an application in one language, export the user-defined text strings for the application, and
then import translated strings for up to 40 languages into the same application.
3/10/2008
Deploy a distributed application across different countries, allowing operators in each location to
view the application in their own language.
Support for 40 languages. Previous to this release only 20 different languages were supported.
text you specify for graphic objects and global objects including
o
captions
local messages
FactoryTalk View text objects (Note: A text object with its SizeToFit property set to True might
change in size when displayed in different languages.)
text strings defined for FactoryTalk Alarm and Event summaries, banners, and log viewers
graphic and global object display titles specified in the Display Settings dialog box
Among the text strings that do not support language switching are:
text strings that are part of the graphical user interface of FactoryTalk View Studio or View SE
Client software, such as menus, which are displayed in the same language as the operating
system. These are translated when FactoryTalk View is localized
text that can be displayed at run time but is used to operate the application, such as the names
of graphic displays and command strings
3/10/2008
text in the title bar of the FactoryTalk View SE Client window, which is part of the setup of the
client, not part of the application
Alarm Fault List messages displayed in FactoryTalk Alarm and Event Summary and Banner
objects
3/10/2008
3/10/2008
7. Notice that these languages have been added to the list and English is set as the default
language as indicated by the check mark next to English.
8. Check the Display undefined strings using the default language option.
3/10/2008
Your application has been configured to support 3 languages. Now you will need to perform an export
to get the strings that you will need for translation.
Export strings for translating
There are a number of ways to change the text strings in a graphic display besides editing them
individually by object. The best approach is to export the strings to Excel and use the Optimize
duplicate strings feature.
1. Click the Export button
2. Select the Export strings for all languages to an Excel spreadsheet radio button. Check the
Optimizing duplicate strings and Open exported file options
3/10/2008
Translate strings
Observe the open Excel file. Everywhere you see the text **REF: in the language columns (i.e., en-US,
de-DE, es-MX, and zh-CN) is referencing a duplicate string in the REF column before the language
column. That means you dont have to translate the text for that object. You only have to translate the
first occurrence of that text indicated by the text **UNDEFINED**. You will use a different file that has
already been translated to do the import.
Scroll down in Excel until you see row number 230. Column D Description will have
CloseNonPermissive_Text.Caption. Note, your Excel file may look different. If it isnt row 230 do a find
on the description. This is REF:36 and it is the first occurrence. Row 244 has a Column D description of
OpenNonPermissive_Text.Caption and is cross-referencing (**REF:36**) the first occurrence. Only
the first occurrence will need to be translated. Notice that the cross-reference to the first occurrence is
in the language columns. Notice that the REF Columns (E, G, I, and K) are left blank when the
occurrence is not cross-referenced.
Here is an example of first occurrence references of #36, 231, 232, and 233 along with the crossreverences.
3. Observe the file. Notice that not everything has been translated. Notice that this file was translated
from an export file that was not optimized.
4. Close the file.
3/10/2008
2. Select the option to Import strings from an Excel spreadsheet. from the String Import Export
Wizard dialog and click the Next button
3/10/2008
3. Select the Browse button and browse to this file C:\LabFiles\Lab 15 FactoryTalk View
SE\LanguageSwitching\AF07_translated.xls and click the Finish button.
4. String import in Progress will start. Once it is completed, you will see the message String import
completed successfully in the Diagnostics List.
5. Click the OK button on the Language Configuration dialog.
Language switching command
There is a FactoryTalk View language switch command that you use to perform language switching.
Buttons that use this command have been configured on the footer display. Lets look at them.
1. From the Explorer, open the footer display.
2. Double-click on the US flag button to open the Button Properties dialog.
3. On the Button Properties dialog, click on the Action tab.
Notice the Release action - Language en-US
The Language command was added to the Release action by clicking the button and then using the
Command Wizard. The command Language is located under the System Languages folder.
3/10/2008
Only the languages that have been added to your application will be displayed in the language id list.
3/10/2008
System\Time
System\Date
System\DateAndTimeString
System\MonthString
System\AlarmMostRecentDate
System\AlarmMostRecentTime
System\AlarmStatus
7. Notice that alarm messages for Tank101 are not translated. These will be translated in the next
section.
3/10/2008
You can export alarms from RSLogix 5000 to a comma-separated variable (*.csv) or text (*.txt) file. For
double-byte character sets (for example, Chinese), export alarms in .txt format because in RSLogix
5000, the .csv format does not support Unicode character sets.
Once you have exported the alarm messages, you can then manually add all the messages in the
languages you desire (limited to the languages supported by FactoryTalk View) and then import the file
when translation is complete. This simplifies sending the work out to translators.
Export alarm messages in RSLogix 5000
1. Go to RSLogix 5000
OR if it isnt 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
3/10/2008
3. Expand the width of columns A, B, C, and D. Notice that the last line of text in the file is the alarm
definition for the low alarm for the ProductTempLoop which we will be modifying. The first element
from the left is the instruction type (ALMMSG:) and the language string for the alarm message (enus for English in the United States). The alarm message text appears as the fourth column (D)
from the left (ProductTemp Low).
4. Copy the last ALMMSG line and then paste it at the end of the file.
5. Change the text en-us to de-DE (for German in Germany), and then change the alarm message
text to read, ProductTemp Tiefpunkt
6. Paste another copy of the ALMMSG line at the end of the file.
7. Change the text en-us to es-MX (for Spanish in Mexico), and then change the alarm message
text to read, ProductTemp Bajo.
Your file should look something like this.
3/10/2008
An export file C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitchingAF07_SE_LabTags_translated.TXT has been translated for you. The export file was created using the RSLogix
5000 Unicode Import/Export (*.TXT) format because it includes message strings that were translated in
Chinese. You will use that file when performing an import.
3/10/2008
5. Select the filename AF07_SE_Lab-Tags_translated.TXT, leave the default settings for the Tags
and Logic Comments.
button.
button.
9. When prompted with the message Done downloading. Change the controller mode back to
Remote Run? select the Yes button.
3/10/2008
3/10/2008
2. On the General tab of the Tag Alarm and Event Server Properties page type FTAETagServer
for the name.
3. Click on the Priorities and History tab, leave the settings at the defaults:
Notice the history is being logged in English and the tag alarms will be logged in the same
database as the device-based alarms.
4. Click the OK button
3/10/2008
5. Tag based alarms can be created and configured with the Alarm and Event Setup Editor.
Double-clicking on the Alarm and Event Setup icon under the Alarm and Event Tag Server in
the Explorer.
6. The Alarm and Event Setup Editor will open. Notice that there are no alarms. You will use the
import to create alarms.
7. Close the Alarm and Event Setup Editor
Normally, you would use the Alarm and Event Setup Editor to create your alarms, do an export,
translate the alarm messages, and then import them back into the Tag Alarm and Event Server. For
this lab you will be creating your alarms with a file that contains the alarms and the translated
messages strings. You will step through an export at the end of this section to see how it works.
Translate alarm messages
1. If you dont have C:\LabFiles\Lab 15 FactoryTalk View SE\LanguageSwitching folder open, do
so.
2. Double-click on the AF07_FTAETagServer_AlarmExport_translated.xls file to open it.
3. Notice there is a worksheet for each alarm type, one for the messages, and then one for tag update
rates.
4. Click on each of the tabs and take a look. There is one digital alarm and one level alarm. Notice
that one message can be used in multiple alarms.
5. Click on the Messages tab. There is a column for each language that has been translated.
6. Close the file.
Import alarm messages
1. From the Explorer, right-click on the FTAETagServer and select the Import and Export
context menu item.
3/10/2008
2. Select the Import alarm configuration from Excel File options and click the Next button.
7. A progress indicator will open. When complete, you should see this
3/10/2008
2. The Alarm and Event Setup Editor will open. Notice that there are two alarms.
3. Double-click on the first alarm, the Digital Alarm Properties dialog will open. Look at the Digital
Tab and notice that these properties are almost the same as the device-based digital alarm
instruction property sheet that you saw in RSLogix 5000. In fact, this tag alarm will be triggered from
the same condition as a device-based alarm that was created. This is just so you can compare
them.
3/10/2008
5. The next alarm will be displayed in the Level Alarm Properties dialog. Look at the Level and the
Messages tabs and notice that these properties are almost the same as the device-based analog
alarm instruction property sheet that you saw in RSLogix 5000. In fact, this tag alarm will be
triggered from the same condition as a device-based alarm that was created. This is just so you can
compare them. Notice on the Messages tab that the same message string is used for both the High
High and the High condition.
6. Click the Cancel button to close the Level Alarm Properties
7. Click the Messages tab.
Messages can be created when a new alarm is being created or they can be created from the message
tab and then they can be associated with an alarm.
You can create as many messages as you like for alarms, but each alarm can be associated with only
one message. For level alarms, you can configure one message per level condition.
Alarm messages can be shared between alarms to eliminate duplication. The Usage column on the
Message tab indicates how many alarms are referencing an alarm message.
8. To view the list of alarms that are referencing a particular alarm message, right-click the row
containing the message and then click the Usage Details context menu item. Click the OK button
to close the Message Usage Details dialog.
9. Close the Alarm and Event Setup Editor
Export alarm messages
You will step through an export to see how it is done.
1. From the Explorer, right-click on the FTAETagServer and select the Import and Export
context menu item.
3/10/2008
3. Leave the defaults with all the selected alarms and click the Next button
4. Select the Export messages for all alarms, check all the languages, and click the Next button.
5.
Change the file name to MY_ AF07_FTAETagServer_AlarmExport.xls and click the Finish
button.
3/10/2008
Notice that language switching works and alarm messages are also being updated to the
appropriate language.
4. Notice both the tag and device-based alarms appear and the message strings are language
switchable. Tag-based alarms will start with Tank101. Device-based alarms will have the shortcut
name at the beginning of the alarm name i.e., [SoftLogix].
Tag-based alarms will not appear in the Tank Summary because the event subscription is set to
[SoftLogix]Program:Tank101.*. The tag-based alarms start with Tank101. To get them to appear in the
Tank Summary, change the event subscription to *Tank101* or add another event source called
Tank101*
.
You have completed this lab!
3/10/2008