FactoryTalk View SE Basic Lab
FactoryTalk View SE Basic Lab
development
Expanding human possibility through
learning
Lab Book
Important User Information
This documentation, whether, illustrative, printed, “online” or electronic (hereinafter
“Documentation”) is intended for use only as a learning aid when using Rockwell Automation
approved demonstration hardware, software and firmware. The Documentation should only be used
as a learning tool by qualified professionals.
The variety of uses for the hardware, software and firmware (hereinafter “Products”) described in
this Documentation, mandates that those responsible for the application and use of those Products
must satisfy themselves that all necessary steps have been taken to ensure that each application and
actual use meets all performance and safety requirements, including any applicable laws,
regulations, codes and standards in addition to any applicable technical documents.
In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter
“Rockwell Automation”) be responsible or liable for any indirect or consequential damages resulting
from the use or application of the Products described in this Documentation. Rockwell Automation
does not assume responsibility or liability for damages of any kind based on the alleged use of, or
reliance on, this Documentation.
No patent liability is assumed by Rockwell Automation with respect to use of information, circuits,
equipment, or software described in the Documentation.
Except as specifically agreed in writing as part of a maintenance or support contract, equipment
users are responsible for:
• properly using, calibrating, operating, monitoring and maintaining all Products consistent
with all Rockwell Automation or third-party provided instructions, warnings,
recommendations and documentation;
• ensuring that only properly trained personnel use, operate and maintain the Products at all
times;
• staying informed of all Product updates and alerts and implementing all updates and fixes;
and
• all other factors affecting the Products that are outside of the direct control of Rockwell
Automation.
Reproduction of the contents of the Documentation, in whole or in part, without written permission
of Rockwell Automation is prohibited.
Throughout this manual we use the following notes to make you aware of safety considerations:
IMPORTANT
Identifies information that is critical for successful application and understanding of the product.
Labels may also be on or inside the equipment to provide specific precautions.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive
or motor, to alert people that dangerous voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or
motor, to alert people that surfaces may reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a
motor control center, to alert people to potential Arc Flash. Arc Flash will cause
severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective
Equipment (PPE).
Table of Contents
1. Introduction to Distributed HMI with FactoryTalk View Site Edition ..................................... 1-4
Before You Begin .................................................................................................................. 1-4
About this Training Lab ...................................................................................................... 1-4
Duration ............................................................................................................................ 1-4
Prerequisites ..................................................................................................................... 1-5
Materials ........................................................................................................................... 1-5
Exercise A: Explore FactoryTalk View SE Runtime .................................................................. 1-6
Objectives ......................................................................................................................... 1-6
Scenario ............................................................................................................................ 1-6
Practice............................................................................................................................. 1-6
Exercise B: Create an Application ......................................................................................... 1-14
Objectives ........................................................................................................................ 1-14
Scenario ........................................................................................................................... 1-14
Practice............................................................................................................................ 1-14
Exercise C: Create and Import HMI Displays.......................................................................... 1-22
Objectives ....................................................................................................................... 1-22
Scenario .......................................................................................................................... 1-22
Practice........................................................................................................................... 1-22
Exercise D: Create Display Objects....................................................................................... 1-40
Objectives ....................................................................................................................... 1-40
Scenario .......................................................................................................................... 1-40
Practice........................................................................................................................... 1-40
Exercise E: Animate Display Objects .................................................................................... 1-67
Objectives ....................................................................................................................... 1-67
Scenario .......................................................................................................................... 1-67
Practice........................................................................................................................... 1-67
Exercise F: Create a FactoryTalk View SE Client ................................................................... 1-72
Objectives ....................................................................................................................... 1-72
Scenario .......................................................................................................................... 1-72
Practice........................................................................................................................... 1-72
1. Introduction to Distributed
HMI with FactoryTalk View
Site Edition
Duration
This lab takes approximately 100 minutes to complete.
Prerequisites
There are no prerequisites for this hands-on lab.
Materials
This training lab requires the following items.
• Hardware: No hardware beyond a lab computer is required to complete this hands-on
lab. A Logix 5000 controller could be used in place of Studio 5000 Logix Emulate.
• Software:
• FactoryTalk View Site Edition 14.00.00 (CPR 9 SR 14)
• FactoryTalk ViewPoint SE 14.00.00 (CPR 9 SR 14)
• FactoryTalk Linx 6.40.00 (CPR 9 SR 14)
• FactoryTalk Logix Echo 2.01.00 (CPR 9 SR 13)
• Studio 5000 Logix Designer v35.00.00 (CPR 9 SR 13)
• FactoryTalk Services Platform 6.40.00 (CPR 9 SR 14)
• Files: Class Files Folder C:\Lab Files
• Folder FTView SE – contains a pre-configured View SE client file and a pre-
configured display that will be imported into the lab-created application
• Folder Images – contains images to be used as display backgrounds and company
logos
• Folder Studio 5000 Logix Emulate ACD File – contains the controller program pre-
downloaded to FactoryTalk Echo
Objectives
In this exercise, you will complete the following:
• Launch the FactoryTalk View SE Client
• Navigate between existing HMI displays
• View the FactoryTalk Alarms and Events (FTAE) Server
Scenario
As a potential application developer, it is important to understand how the end user will interact
with the developed application. Operators, engineers, administrators, and maintenance staff may
all use the same application to interact with a working system in unique ways. Interface design is
important for operational efficiency and effectiveness. Exploring an application will also give you a
better understanding of the end goal for this hands-on lab session.
Practice
The first exercise makes use of a pre-configured FactoryTalk View SE application. The application
contains a highlight on some of the new product features as well as a production site example. The
application is referred to as FTViewDemo.
1. Navigate to C:\Lab Files. (Also available as a shortcut on computer desktop)
2. Open the FTView SE folder and double click on the FactoryTalk View SE Client launcher
named FTViewCookieDemo
This will cause a small pop-up display with a double progress bar to appear. This progress bar
may take several moments to finish.
Once the Client is open, you will see the following screen.
NOTE
If you would like to adjust the Client window position on your monitor, click on the title bar and
drag the client window to the desired position. In most cases, the client window will have a
startup setting to maximize the client window to fill the entire monitor, but for the purposes of
this demonstration, we have chosen a smaller window size.
The Cookie Demo is comprised of two main screen areas. The first area is the banner. This
area at the top is always displayed and is being used as general system-wide information and
navigation. Typically, this area can be used in practice to display alarm information, time
display, navigation, and application identification.
The larger portion of the main screen is the production display itself. This area of the HMI
changes based on how the user navigates between displays. Clicking on a production section
name (such as Cooling or Case Packer) from the navigation banner will show a display with
information specific to the selected production area, replacing the previous production
display. The display shown below is a plant wide view.
4. Hover the cursor over the top of the four Silo level indicators in the top middle area of the
display
Notice the appearance of a black border around the Silo level indicator group of data.
NOTE
Objects that have been configured for touch animation will be indicated with a bold border that
appears when the mouse cursor is moved over the object. The action that occurs when the
object is then clicked depends on the definition in Touch Animation associated with that object.
You will experience more on animation in a later exercise.
5. Click on the Silo Group indicators. The resulting material storage display is shown
6. Click the Mixer text in the Navigation banner and the resulting mixer display is shown
7. Click on the Mixer mode select switch. The selector switch will change from AUTO to SEMI-
AUTO (or vice versa)
8. Click on the ALARMS button in the navigation banner and the associated alarm display will be
shown
From here, you can see the alarm summary display object in the main portion of the display.
Alarm functionality will be explored in greater depth in a later exercise.
NOTE
This concludes the guided tour of the pre-configured application. Please go ahead and spend a
few moments exploring the client on your own before proceeding to the final step.
9. Close the display client by clicking on the X in the top right corner of the window
Objectives
In this exercise, you will complete the following:
• Create a new FactoryTalk View SE Local Station Application
• Create a FactoryTalk Linx Data Server
• Define the device shortcut to a programmable controller
Scenario
The FactoryTalk application is a container for all necessary components and functions of a full HMI
control environment. Creating the application is the first step to building an HMI project.
A FactoryTalk application typically contains the following resources:
• Area containers ~ useful for larger, site-wide applications
• HMI server(s)
• Data provider(s)
• Alarm server(s)
Data servers provide the application with process information. Typically data servers are
connections to PLCs and PACs, but third party OPC data providers can connect to a multitude of
data sources.
Practice
In this exercise, you will use the FactoryTalk View SE Studio HMI development environment.
1. Launch FactoryTalk View Studio. This can be done from the Start menu or from the task bar
shortcut
b. Click Continue
3. When the ‘New / Open Site Edition (Local Station) Application’ pop-up is shown, select:
b. In the resulting tab from step a, enter “Cookie Demo” as the Application Name
At this point, you are able to observe the FactoryTalk View Studio main window. The window
contains an explorer pane on the left and the editor pane on the right. The content of the
editor pane depends on what is selected from the explorer pane.
Looking closer at the explorer pane, you can see the Application and the HMI project that has
been created.
NOTE
In a Local Station application, the HMI and Data servers must be hosted on the same computer.
The HMI server is named the same as the application name, and therefore automatically created.
In a Network application, the HMI project must be created manually and may be named
differently than the application.
b. In the displayed menu, select Add New Server -> Rockwell Automation Device Server
(FactoryTalk Linx)…
e. Click OK
6. In the Explorer pane, expand the newly created FactoryTalk Linx data server object and
double click on the Communication Setup option
a. Click Add
d. In the bottom area, in the Alarm and Events section, verify the dropdown for Subscribe
To is “All Alarms and Events Notifications Messages”
e. Click on the Apply button. In the resulting pop-up, click on the YES button (pop-up not
shown)
f. To finish creating the device shortcut, click the OK button at the bottom right
Objectives
In this exercise, you will:
• Create a header display
• Create an overview display
• Add a previously developed display for the cooling line
• Create an alarm display
Scenario
A graphic display represents the operator’s view of plant activity. This display can show system or
process data and provide operators with a way to read values from or write values to external
devices such as programmable controllers.
Practice
Create the Header Display
This display will be used for status and navigation information. Unlike the other displays, this
display is intended to always be open and will be configured to be parked at the top of the screen.
1. In the explorer pane of FactoryTalk View Studio, right click on Displays under the Graphics
folder. Select New to create a new display
A new ‘Untitled’ display will be opened in the editor pane. This new display will become the
header display. In the next steps, the properties of the display will be edited to allow the
header to show up at the correct position in the HMI client.
2. Edit the properties of the display by right clicking on an open area of the display. From the
right-click menu, select Display Settings
b. Select Specify Size in Pixels. Set the with and height as follows:
X: 0 Y:0
d. Choose Background Color by selecting the color swatch square and selecting a light
grey
You should see the display resize the background color change. In later exercises, you will
continue to develop this display.
After one or more displays have been created, the Displays object in the explorer pane will have a
plus “+” icon to the left of it, indicating that it contains items. Expand the container and observe the
newly created Header display. Displays can be launched two ways:
• Double click on the name of the display
• Right click on the name of the display and select Open
Other operations related to displays, such as delete, rename, etc. can also be executed from the
right-click menu.
7. Double click the Header display to launch the display editor
8. Now that you see how to open a display for editing, you can close the Header display
9. Right click on Displays in the explorer pane and select New to create a new display
10. Right click on the open display and choose Display Settings from the menu
a. Uncheck the Title Bar appearance checkbox. This will also grey out the checkboxes for
System Menu and Minimize Button just below
c. Select Specify Size in Pixels and set weight and height as follows:
X: 0 Y: 0
12. With the new display still open, right click on the Images container in the explorer pane.
14. Click the newly created display to bring it back to the focused object. From the FactoryTalk
View Studio menu, select Objects > Drawing > Image
MENU BAR
The top menu of FactoryTalk View Studio is called the Menu Bar and it changes based on the HMI
element you have open and in focus in the editor pane. If you don’t see the Objects menu option,
make sure you have a display object open and in focus for editing.
15. Move your mouse cursor over the open display. The mouse cursor has morphed to include an
image icon to the bottom right of the cursor. Click and hold the mouse, then drag to draw a
rectangle on the display
16. When the mouse button is released from the previous step, an Image Browser window
automatically opens:
a. Select the image that you imported in a previous step: back_01_1280x1024_ce cookie
line layout_rev1
b. Click OK
The image has been put on the display, but you notice that it needs to be sized and positioned
correctly. The properties of this image can be modified to put the object in an exact location.
17. Right click on the image in the display editor and select Properties.
c. Click OK
The image will now be show in the top left-hand corner of the display.
NOTE
Converting this image to wallpaper provides a couple of conveniences. All other objects added
to this display will automatically be placed on top of this image by default as well as avoiding
accidentally selecting and moving this image while doing the rest of the design work on this
screen.
There may be a time when displays will be used across multiple applications. In this case,
previously created displays can be easily reused by importing into the application. The Cooling
display will be imported into the CookieDemo application from an external file location. The
Cooling display contains information and objects relevant to this area of the Cookie Factory. In
future exercises, additional trends and animations will be added to this display.
21. Right click on Displays and select Add Component into Application…
22. In the resulting navigation window, go to C:\Lab Files\FTView SE and select Cooling.gfx
When the display opens, you will notice a large blue object with a white “X” pattern on it. This
indicates a missing reference to an image. The background image for this display will need to
be added to the library for this project.
24. Using the same approach as earlier, add the necessary image into the HMI project by clicking
on the Images container in the explorer pane and select Add Component Into Application…
27. Reopen the Cooling display. Confirm that the background image has now properly loaded
29. Create a new display. This display will be called Alarms. Right-click on the new screen and
select Display Settings. Make the following adjustments:
c. Select Specify Size in Pixels and set the width and height as:
X: 0 Y: 0
e. Type the name Alarms into the Navigation History Screen Name
Objectives
In this exercise, you will complete the following:
• Add images to the Header display
• Add navigation buttons to the Header display
• Add static text and dynamic string displays to the Cooling display
Scenario
Basic display objects create the visual structure of displays. Objects give context and purpose to
the actions or statuses they represent. Without them, an operator would not have the context to
know what an indicator is displaying or what it means. Text and shape display objects allow for
information to be visually organized.
Practice
Building the Header Display
The header will have two images and three navigation buttons added to it.
1. Add the Rockwell Automation and MightyQ’s Cookie Co logos to the application:
a. Right click on the Images container in the explorer pane and choose Add Component
Into Application… Navigate to C:\Lab Files\Images and select the following images:
ii. ra-logo-transparent-small.bmp
b. Click Open
2. In View Studio, open the Header display (if not already open). Add the images to the Header
display. The last time you added an image, it was done using the Menu Bar at the top of the
View Studio window. This time, find the Image icon in the toolbox on the right-hand side of
the View Studio window. Click on it to open.
3. With the image tool selected, draw a rectangle on the Header display by clicking and holding
down the left button on the mouse and dragging the mouse down and to the right. In the
Image Browser that automatically opens, select the Rockwell logo (ra-logo-transparent-
small) and click OK
4. Right click on the Rockwell logo image and select Properties. In the properties window,
select Common tab and change the size to the following:
c. Select OK
5. Repeating steps 2 & 3, add the MightyQ’s logo and move it to the far right and top side of the
display
6. Using the Button tool (as seen below), create a button on the Header display
Note: Don’t worry about the size or location of the button object for now. You will modify
this in a later step!
General tab:
a. Set the Style as No Border
Action tab:
c. Type in “Display Overview” as Release action
Up Appearance tab:
d. Change Fore Color to White and Back Style to Transparent
Common tab:
h. Set Height to 50 and Width to 200
When completed, the button properties should look like the images below:
The resulting button looks like the following image. At this point, the button position may be
different, but we will be adjusting when the remaining buttons are added. The button is indicated
by the 8 selection markers.
8. Make two copies of this button object by left-clicking on the button, then pressing keyboard
shortcut Ctrl+D twice. This is a shortcut command to duplicate the object on the display.
For the two buttons, right click on each button and select Properties. In the Properties menu of
each button, make these changes:
9. To position the buttons, all 3 need to be selected. Hold the Control (Ctrl) key and left-click to
select each button. You can also left-click and drag to ‘rubber band’ the three buttons
together. The Header display should have all 3 selected as shown below:
10. With all 3 buttons selected, use the Menu Bar to make the following selections:
Note: If your buttons are overlapping, try arranging them further apart individually, then
run through the arrangement steps again.
11. Use the Menu Bar or the Toolbox to select the rectangle tool. Drawing -> Rectangle
12. With the Rectangle tool, draw a rectangle object onto the display. This rectangle will be used
as a background for the navigation buttons. The exact size does not matter at this time, for
these properties will be defined in an upcoming step. The properties window for the
rectangle will appear one you draw the shape.
13. In the polygon properties window, make the following changes in the General tab:
g. Change Fill Direction from dark to light then click OK to close ‘Gradient Fill’ pop-up
Common tab:
h. Change Height to 50
Change Left to 0
Click OK
After you’ve made the changes to the properties, the Header display should appear similar to
this:
The rectangle has been drawn on top of the previously configured buttons.
Note: By default, the objects have a depth order based on when the object was created on
the screen. Most recently added objects are placed over previously created objects.
This depth order can be changed using the Bring to Front or Send to Back options
through the Arrangement menu.
14. Right-click on the recently created rectangle and select Arrange -> Send to Back from the
context menu
17. Using either the Menu Bar or the Toolbox, select the Text tool
a. Draw the text object over the top of the second cooling zone’s light grey label area and
make the following changes:
d. Change the Fore Color to dark grey and uncheck Size to Fit
g. Click OK
19. Use either Menu Bar or the Toolbox to select String Display
20. Use the teal-colored area of Zone 2 as a guide to draw the object
a. Draw the String Display object on the display. The properties window will automatically
open, make the following changes:
Common tab
General tab
h. Click OK
To change the Expression field, you can either type in the expression as seen above, or you
can build the expression using the editor. If you use the expression editor, perform the
following steps:
• In the Contents pane, select the Cooling_Zone2_InZone tag and confirm the tag
name in the Selected Tag text area
• Click OK
The tag browser will close with the selected tag in the Expression text area
b. Highlight Font and change it to Arial and Size 12 point bold by clicking the browse […]
button in the value field
c. Highlight ForeColor and change it to dark grey by clicking the browse […] button in the
value field
Note: The Property Panel window will display the properties of the currently selected
object. Try clicking on another object in the display and observe how the Property
Panel window changes to display the properties of the newly selected graphic
object.
22. Use either the Menu bar or the Toolbox to select the Numeric Display object
a. Draw a Numeric Display object where the Total Units indicator is desired
The ‘Numeric Display Properties’ window will appear, make the following adjustments:
Common tab:
General tab:
d. Use the tag browser, click on the Tags button and find the Total Parts tag
e. In the Folders pane, drill down to CookieDemo > Cookie Line > Online > Program:Cooling
(Click Refresh All Folders button if you don’t see the tag)
i. Click OK
24. While the new Numeric Display is still selected, in the Property Panel at the bottom right,
select Font and set to Arial, Bold, size 12. Then click on ForeColor and select Blue from the
color selector.
The full Cooling display should look like the following image:
25. To test your display, click on the Test Display button from the toolbox
Tag values should populate on the screen and the existing trends should begin to run.
Observe the screen changing. Once you’re complete with your observations, click the “Edit
Display” button that is next to the “Test Display” button to stop testing the display.
Objectives
In this exercise, you will configure the background of a status indicator to change its color based
on the state of the related Cooling Zone.
Scenario
Animation of display objects allows for changing some properties of display objects based on PLC
tag values. The following properties of objects can be modified through animation:
Visibility
Color
Fill
Position on screen (Horizontal and Vertical)
Size (Width and Height)
Rotation
Touch (Apply actions to objects)
And more!
Practice
It’s your turn to try it:
2. Open the Object Explorer in the bottom right of View Studio, switching away from the
Property Panel (shown in first image). In the Object Explorer, expand Zone2Group and expand
Zone2StatusGroup to reveal the Zone2AnimatedPolygon. Click on Zone2AnimatedPolygon
to select in both the Object Explorer and in the Cooling display as shown below:
IMPORTANT
Tip ~ The Object Explorer allows you to see the grouping and arrangement of objects on a
display. Selecting an object in the Object Explorer is effectively the same thing as picking it
directly on the display. The checkboxes can be unselected to hide the visibility of objects on the
display. This is very useful when interacting with complex grouped objects that are layered on a
display.
Tip ~ The names of objects are created by default as the object type with a number for the
number of objects of that type that are created on that display, such as StringDisplay3. These
names can be changed using the Property Panel (or in the Properties Window -> Common tab for
each item).
3. Right click on Zone2AnimatedPolygon and select Animation -> Color from the menu. The
‘Animation’ configuration window will be displayed
4. In the Animation tab, click on the Tag button. In the resulting ‘Tag Browser’ window, select the
tag by selecting the [+] to the left of the tag name
::[CookieLine]Cooling_Zone2_InZone
5. For this tag, you will edit animation states from their default values. In the ‘Animation’
window, underneath the expression area is the animation state area. Selecting a state on the
left list will cause the Value and Line/Fill objects to update with the state definitions. Edit the
following states to have the matching Value, Line, Fill, and Blink settings to the values below:
6. Click the Apply button on the animation window, then select Close.
With the display in test mode, you should be able to see the color indicator behind the status
text change from the default teal color to a white or green color, depending on the state the
cooling zone is in.
8. When you are finished monitoring, click the Edit Display button
Objectives
In this exercise, you will complete the following:
• Create a startup macro to prescribe screen starting positions
• Create a FactoryTalk View SE Client
Scenario
As an application developer, it is important to understand how the end user will interact with the
developed application. Operators, engineers, administrators, maintenance staff, and more may all
use the same application to interact with a working system in their own unique way. Interface
design is important for operational efficiency and effectiveness.
Practice
It’s your turn to try it:
1. In the explorer pane of FactoryTalk View Studio, right-click on the Macros object (within the
Logic and Control container) and select New from the menu
2. The Macro Editor will open. The Macro editor window looks very similar to other text editor
applications you may be used to. In the first open line, type in the following commands, one
per line:
Display Overview
Note: If you double click on the macro editor, the Command Wizard pop-up will be
displayed. The wizard allows users unfamiliar with FactoryTalk View SE command
syntax and options the ability to build their commands using an interface.
Note: Macros are essentially a list of commands to execute in sequence. This macro will
ensure the correct displays are called when a user launches the client. From the
commands entered above, the /DT parameter means the display will be docked at
the top of the screen.
4. In the FactoryTalk View SE Menu bar, select the SE Client Launcher: Tools -> Launch SE
Client
5. In the ‘FactoryTalk View SE Client Wizard’, click Create a FactoryTalk View SE configuration
file
6. In the Client file name field type “CookieDemoClient” as the name of the configuration file.
Click Continue
a. As the Application Type, select Local Station application by clicking the corresponding
button
c. From the Startup macro dropdown menu, select the recently configured macro
ClientStartup
d. Click on Advanced
10. The client should begin to launch. After the progress bar finishes, the client application
should be displayed as shown.
Note: If you would like to adjust the Client window position on your monitor, click on the
title bar and drag to the desired position. In most cases, the client window will have
the startup settings set to maximize the client window and fill the entire monitor.
11. In the Client application, you can navigate between the displays that have been created in the
HMI project. Navigate between the Overview, Cooling, and Alarm display.
Note: The Alarm display is currently blank and will be populated by you in a later exercise.
12. Close the Client window by clicking the ‘X’ in the top right corner
Objectives
In this exercise, you will complete the following:
• Create FactoryTalk Alarm and Event Server
• Create a server-based alarm
• Create an alarm banner object
• Create an alarm summary object
• Acknowledge an active alarm
Scenario
Alarms allow operators to identify and react to abnormal operation conditions. Annunciating alarm
conditions saves time, maintains safety, and increases efficiency in production. Operators interact
with FactoryTalk based alarms in several ways:
• Alarm Banner object
• Alarm Summary object
• Alarm-based animations of display objects
Practice
Creating a FactoryTalk Alarms and Event Server
The FactoryTalk Alarms and Events (FTAE) server is a component that constantly monitors
configured controller and HMI tags for alarm conditions. Adding an alarm server is a one-time
configuration. Once configured, individual alarm conditions can be added to the server while it is in
production.
1. In the FactoryTalk View Studio explorer pane, right-click on the CookieDemo application and
select Add New Server -> Tag Alarm and Event Server
2. In the ‘Tag Alarm and Event Server Properties’ window, type in “CookieAlarm” in the Name
property. Set Startup Type to “Load when operating system initializes”
3. On the Priorities and History tab, verify the Enable history box is unchecked, then click OK.
4. In the explorer pane, click to expand the newly created CookieAlarm alarm server. Double-
click on the Alarm and Event Setup. A small progress bar window will display, and after a few
seconds an Alarm and Event Setup window will be displayed.
Configuring Alarms
The Alarm and Event Setup editor is the primary tool for creating and modifying alarms. Depending
on the alarm type, different properties will be available in the editor. There are four primary alarm
types: digital (on / off), deviation, level, and event alarms. For this lab, we will stick with a digital
alarm and a level alarm. There are two types of alarm sources: server-based alarms and device-
based alarms. Device-based alarms are propriety types of alarms built in the ControlLogix
controller, using specific ALMA and ALMD instructions. There are two types of tag-based alarms:
Logix tag-based alarms and FTAE server-based alarms. Logix-based alarms are a newer type of
alarm that can originate from any controller value. FTAE server-based alarms originate from an
instance of FTAE server that needs to be created in the application, as we saw in previous steps.
5. In the Tag Alarm and Event Setup window, click on the New Alarm button in the top left
corner, then select Digital from the dropdown menu
6. In the ‘Digital Alarm Properties’ window, set the Name to “Cooling Zone Drive Alarm”. Set the
Severity to 500 and the Message to “Cooling Conveyor Drive has faulted. Check HMI
mounted at cabinet SC-107.”
7. Click on the ellipsis button for the Input Tag field. The ‘Select Tag’ browser window will
appear. Select ::[CookieLine]Program:Cooling.Alarm_Control[4] from the Tag Browser.
Click the OK button.
8. In the Input Tag field, the name of the tag selected should appear. Because you need to
reference a single bit from this tag, add .1 to the end of the tag name. It should look like the
following:
9. Click on the OK button at the bottom of the ‘Digital Alarm Properties’ window
12. Use the toolbox to select the Alarm Banner tool Objects -> Alarm and Event -> Alarm and
Event Banner
13. Create the Alarm Banner object in the display area between the two logo images. The ‘Alarm
and Event Banner Properties will be displayed
14. Click on the Sort tab and select Descending for the Event Time item
This setting will ensure that the most recent alarms show up at the top of the banner object.
16. The Alarm and Event Banner should be sized as shown on the header display:
19. Use the toolbox to add Objects -> Alarm and Event -> Alarm and Event Summary
20. Create an Alarm Summary object that covers the full Alarms display. The Alarm and Event
Summary Properties window will be shown. Click on the OK button on the window to accept
the default configuration
22. Launch the FactoryTalk View SE Client. This can be done from View Studio using the Tools ->
Launch View SE Client option from the menu bar. Click the option: Run an existing
FactoryTalk View SE Client configuration file
Note: When the client application is running (or when a display is in Test mode), the Alarm
Banner should have a green icon in the bottom left corner of the banner. This
indicates a healthy connection to the Alarm and Events system. In advanced
FactoryTalk configurations, the HMI may not be on the same computer as the Alarm
server.
Note: If there are no alarm events in the system, you will see the text “Waiting for Alarm
Events…” in the alarm summary and banner. There is simulation logic running in the
controller program that automatically generates alarms for the purpose of
demonstrating alarm functionality. After a few moments, new events should appear
in the Alarm and Event Summary.
25. Switch back to View Studio by selecting the icon from the taskbar
26. Bring up the ‘Command Line’ window by double-clicking on Command Line under the System
folder
Note: The Command Line window can be used to immediately execute commands or
macros. You can double-click inside the window to bring up the Command Wizard
editor or directly type into it. After creating the command and hitting enter, the
command will be immediately executed. Note that certain commands are not able to
run inside of View Studio such as the Display command. When attempting to issue
such a command that is not supported in View Studio, you will receive a diagnostic
message indicating the command could not be run. For example, the command
‘Display’ is ignored when issued from the development environment or an HMI
Server.
27. Either use the Command Wizard editor or directly type the following command:
Set ::[CookieLine]Program:Cooling.Alarm_Control[4].1 1
Hit the enter key when completed and the text will disappear. This will set an alarm condition
for the digital alarm that was configured in previous steps.
28. Switch back to the display client by selecting the icon from the taskbar
After 30-60 seconds, the alarm will return to a ‘Normal’ state removing it from the Alarm
Banner. The alarm banner will only show a few of the most recent and highest priority alarms
that are still in the ‘In Alarm’ state.
29. Navigate to the Alarms display. If the alarm does not clear within 60 seconds, you can
manually clear the alarm by switching back to View Studio and issuing the command:
Set ::[CookieLine]Program:Cooling.Alarm_Control[4].1 0
You can also use the up arrow in the command window to select the prior command to save
some typing.
The alarm condition has been returned to normal but still shows up in the Alarm Summary
because it has been configured to require operator or supervisor acknowledgement.
30. Select the alarm in the Alarm Summary object and click on the Acknowledge button (the
leftmost check icon)
With the alarm condition rectified and the alarm acknowledged, the Cooling Conveyor Drive
alarm will disappear from the Alarm Summary object. If historical logging was enabled, the
Alarm and Event Log Viewer could be used to review historical alarm information.
31. Leave the HMI Client window open
Objectives
In this exercise, you will complete the following:
• Create a trend on an existing display using a TrendPro object
• Configure trend pens based on PLC data values
Scenario
The TrendPro object displays real-time data and historical data. Pens on the runtime chart
represent data from the tags that you add to the trend object. The trend object provides an
extensive, flexible runtime control. You can add traces from Live Data, Data Logs, Historical Data,
and Alarm and Events historical log. You can also stack traces, specify unique line settings, create
templates, and customize many other TrendPro object settings. In this exercise, we will explore
just a few basic features of the TrendPro object.
Practice
The Cooling display has a trend already configured for Zone 1. A trend will be created for the
second cooling zone.
1. Open the Cooling display (if it is not already open from a previous exercise)
2. Use the menu bar or the toolbox to select the Trend object: Objects -> Trending -> TrendPro
3. Create a TrendPro object so that it fits the grey blank area of the Zone 2 parcel
Once the object is created, the TrendPro Properties window will open automatically.
Notice the TrendPro controls consume some of the area of the actual plot size. There are
several default Trend controls that cover the usable space for the trend. Using the Trend
properties, you can change the way the trend appears.
NOTE
The FactoryTalk View SE TrendPro object has many properties to customize the trend
appearance. If time permits, feel free to play around with the look and feel of the TrendPro
object.
6. Click on the Add Traces icon (+) at the bottom to select data points or items for trending
7. Expand Live Data -> CookieLine -> Online -> Program:Cooling -> mCoolUDT -> mCoolUDT[1]
NOTE
If you don’t see the correct folder structure in the Folder pane (top), or don’t see tags in the Tag
pane (bottom), click Refresh All Folders button.
8. Holding down the Ctrl key, select tags TempSetPtZone and TempZone to select both items
and click OK
10. Highlight the second trace in the list and make the same change: set the Precision to 0
11. While still in the Traces tab, select the first trace again and then select the Y-axis button
c. Click on Choose Line Style… icon and change the Y-axis color to black
In the line style window, click on the color icon, then in the color window select black
and click OK twice to close both windows.
d. Change the Scale to Minimum and set the values as per the Min / Max settings in the
screenshot
12. Using the Move Down arrow at the bottom, select the second trace in the list and complete
the same changes as specified in step 11.
Note: Most of the changes completed for the first trace will be inherited by the second
trace, you will likely only need to change the axis Style
13. While still in the ‘Properties’ window, click on the General tab and select Chart
Note: To get the degree symbol, hold down the Alt key, type 248 with the numeric
keypad and release the Alt key.
b. Click Font and change it to Microsoft Sans Serif, Regular, and Size 8 then click OK
Click on the square color swatch to the right of the color field. One of the ways to select
the color is to enter the color parameter 224 directly into the red, green, and blue fields.
The General tab should now have values like this snapshot:
c. Click on the Choose Line Style… icon and change the X-axis color to black
Confirm that the trends in Zone 1 and Zone 2 panels now look the same
19. Switch back to the View SE Client that was left open in the lats exercise (or open the Client
you created in Exercise F)
Objectives
In this exercise, you will complete the following:
• Configure the FactoryTalk ViewPoint desktop and mobile portal from a web browser
• Navigate a FactoryTalk ViewPoint application
Scenario
FactoryTalk ViewPoint provides a web-based portal for access to a FactoryTalk View application.
This can be useful for remote monitoring of production systems, or for uses that don’t necessarily
need to access all functions of the View SE Client.
Practice
1. Use the Windows Start to launch FactoryTalk ViewPoint Administration portal
FactoryTalk ViewPoint is an add-on to FactoryTalk View that extends visualization and real-time
decision capabilities to browser-based remote users, including plant managers, supervisors, or
mobile workers. With FactoryTalk ViewPoint, critical information of plant floor operations can now
be easily accessed and monitored from virtually any location and virtually any device.
FactoryTalk ViewPoint leverages HTML5 technology which opens up connectivity across common
types of mobile devices and modern browsers. Whether you are using an operator workstation,
iPad, or Samsung Galaxy Tab®, a web browser is all that is needed to gain access to a web-enabled
application.
A FactoryTalk ViewPoint web application consists of graphic displays selected from an existing
FactoryTalk View application converted for viewing in a web browser, and then published to a
FactoryTalk ViewPoint Server (also called the web server).
• For Site Edition applications, the FactoryTalk ViewPoint Server runs on a desktop or
server computer.
• For Machine Edition applications, a PanelView™ Plus, PanelView™ Plus 6 or PanelView™
Plus 7 operator terminal functions as the server.
After a moment, the ViewPoint Administration portal will appear.
3. In the resulting webpage, confirm Site Edition (Local) is selected for the FactoryTalk View
Application Type through the dropdown and CookieDemo is selected for Select the
application. Finally, click Select Graphic Displays
4. On Select displays step webpage, click the radio button to set the Header display as the
Initial Display and uncheck it for Mobile Enable. Select the ClientStartup macro from the
dropdown list and finally click the Publish Displays button
On the published display webpage, the progress bar will eventually complete, and the status
of each display should be show as done.
5. Click on the Open classic Web button. The web browser will open in a second browser tab and
the FactoryTalk View application will launch there
NOTE
The FactoryTalk ViewPoint Administration console allows you to publish displays to the web,
configure security, setup activations, view server settings, and also access online help.
This is the ‘Desktop View’ of ViewPoint in the web browser. The Header and Overview
displays are initially shown. This is the result of the startup macro selected during the
configuration of the FactoryTalk ViewPoint application.
6. Navigate to the Alarms display by clicking on the Alarms button from the navigation bar
7. Toggle the same alarm from Exercise H Step 27 by executing the command from the View
Studio Command window to observe the new alarm in the Alarm Summary.
Set ::[CookieLine]Program:Cooling.Alarm_Control[4].1 1
Remember, you can also use the up arrow in the command window to access previously
entered commands.
8. A list of alarms can be filtered by typing in a string in the Quick filter field as shown
9. Click on one of the alarms listed to open a new window that will contain more details about
that alarm
Also provided on this detailed alarm window is the ability to Acknowledge or Shelve the
alarm.
11. Tag writes from displays can be enabled and controlled by security settings. In the browser,
click the other tab to navigate back to the FactoryTalk ViewPoint Administration window
NOTE
By default, the screens available through ViewPoint are read-only. When a client is set to read-
only, the numeric inputs and action buttons that could change PLC values are disabled. The
functionality of some types of objects are not currently supported by ViewPoint in a browser.
Compatibility information can be found on Rockwell Automation’s Knowledgebase.
12. Using the FactoryTalk ViewPoint Administration tab that is still open in the browser:
The above actions will enable tag writes for all displays in the application.
13. In FactoryTalk ViewPoint, a Mobile Device interface is also offered for easier navigation on
devices which may have smaller and varied screen sizes
http://localhost/FTVP/m/
Note: Selecting “Allow” would enable FactoryTalk Alarms and Events notifications to
be displayed in the browser
Note: Notice that the Header display is not shown. This is because you were
instructed back in step for of this exercise to uncheck the display so that it was
not mobile enabled. Other displays that were published with the mobile enabled
option are the displays that appear in the list as expected.
c. Near the top, click on Alarms link that is sown next to the displays. You will see any
active alarms here
15. Review the details. Notice at the bottom that you are provided with options to Acknowledge
or Shelve the alarm
Note: If you are targeting mobile platforms with FactoryTalk View, you can use one of
Chrome’s built-in features to set the browser window’s size to a mobile device’s
known resolution. To view different layouts, you must enable the Chrome
developer tools.
17. In the top right corner of the browser, click on the menu icon and navigate from More tools to
select Developer tools
18. Use the toggle device toolbar button to enable the device toolbar above the web page image
(if not already visible)
19. Select the device to emulate from the Responsive dropdown list. Note that you can enable
other pre-built custom devices through developer tools options by selecting Edit… or set a
specific, custom resolution by directly changing the values. For this exercise, select iPhone
12 Pro
20. The browser will now show the application in the resolution of the selected device and can be
flipped from portrait to landscape mode using the icon highlighted in the screenshot
21. The browser content must be more compact when using smaller display sizes / devices.
Notice in the top left corner you can see an indication of the number of active alarms. Click on
the navigation icon in the top left as shown
23. You can explore by clicking on individual alarms here for more detail and choose to either
Acknowledge or Shelve alarms
You may try out other mobile display sizes and/or look at the other displays.
Click the navigation icon located in the top right or left for options.
NOTE
If you know you will have users looking at ViewPoint from mobile devices, you can modify
existing displays so that the content aligns to mobile friendly displays or create screens
specifically for those users.
This concludes all of the exercises for this lab. Thank you for your time and participation!
Trademarks not belonging to Rockwell Automation are property of their respective companies.