L1 FT View SE Station Lab

L1 Basic Training
FT View Station
For Classroom Use Only!

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:
Identifies information about practices or circumstances

that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you:
• identify a hazard
• avoid a hazard
• recognize the consequence
Labels may be located on or inside the drive to alert people that dangerous voltage may be present.
Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures.
Introductory Lab for Distributed HMI with FactoryTalk® View Site Edition
Contents
Before you begin ........................................................................................................................................... 5
About this lab .................................................................................................................................................................................... 5
Who should complete this lab ........................................................................................................................................................... 5
What you will accomplish in this lab.................................................................................................................................................. 5
Tools & prerequisites ........................................................................................................................................................................ 5
Exercise 1: Explore FactoryTalk View Runtime – MightyQ’s Cookie Factory (10 min) ................................ 7
Objectives ......................................................................................................................................................................................... 7
Why it’s Important ............................................................................................................................................................................. 7
Lab Procedure .................................................................................................................................................................................. 7
Exercise 2: Create an Application from Studio 5000 Architect (10 min) ..................................................... 13
Objectives ....................................................................................................................................................................................... 13
Why it’s Important ........................................................................................................................................................................... 13
Lab Procedure ................................................................................................................................................................................ 13
Exercise 3: Create HMI displays, Import HMI displays (20 min)................................................................. 23

Objectives ....................................................................................................................................................................................... 23
Lab Procedure ................................................................................................................................................................................ 23
Exercise 4: Create display objects .............................................................................................................. 39

Objectives ....................................................................................................................................................................................... 39
Lab Procedure ................................................................................................................................................................................ 39
Exercise 5: Animate display objects (10 min) ............................................................................................. 64

Objectives ....................................................................................................................................................................................... 64
Lab Procedure ................................................................................................................................................................................ 64
3 of 144
Exercise 6: Create Trends (10 min) ............................................................................................................ 70
Objectives ....................................................................................................................................................................................... 70
Lab Procedure ................................................................................................................................................................................ 70
Exercise 7: Create a FactoryTalk View SE Client (10 min) ........................................................................ 79

Objectives ....................................................................................................................................................................................... 79
Lab Procedure ................................................................................................................................................................................ 79
Exercise 8: Configure Alarms (10 min) ....................................................................................................... 86

Objectives ....................................................................................................................................................................................... 86
Lab Procedure ................................................................................................................................................................................ 86
Exercise 9: Using FactoryTalk View SE TrendPro...................................................................................... 99

About this section............................................................................................................................................................................ 99
Read about TrendPro ..................................................................................................................................................................... 99
TrendPro design time configuration ................................................................................................................................................ 99
Using TrendPro at Runtime .......................................................................................................................................................... 107
Additional TrendPro runtime features ........................................................................................................................................... 113
Exercise 10: Using FactoryTalk ViewPoint with FactoryTalk View SE (15 min) (Optional) ...................... 122
Objectives ..................................................................................................................................................................................... 122
Why it’s Important ......................................................................................................................................................................... 122
Lab Procedure .............................................................................................................................................................................. 122
Exercise 11: Update the Studio 5000 Architect Project and add faceplate. ............................................. 139
Objectives ..................................................................................................................................................................................... 139
Why it’s Important ......................................................................................................................................................................... 139
Lab Procedure .............................................................................................................................................................................. 139
4 of 144
Before you begin
About this lab

This hands-on lab provides you with an opportunity to explore introductory features of FactoryTalk View Site Edition (FactoryTalk
View SE). If you are new to FactoryTalk View Site Edition and FactoryTalk ViewPoint, this hands-on lab allows you to learn about
the basic capabilities and features of a FactoryTalk View SE application for both desktop and mobile. You will build a simple
application from the beginning. Topics include creating an application, adding displays, working with tags and animations, basic
alarming, trending, and mobility. This lab will give you a solid understanding of how a FactoryTalk View SE HMI application
works, and how you can extend it mobile devices.
Now you have done The Logix Designer and the PVP 6, now it is time that you need to integrate to HMI
Workstation. And since this is a HMI project you need to integrate to the Existing Logix Designer Controller
that already running.
This lab takes approximately 90 minutes to complete.
Who should complete this lab

This hands-on lab is intended for all audiences. Basic computer operation is the only prerequisite knowledge needed for the lab.
What you will accomplish in this lab

As you complete the exercises in this hands-on lab, you will gain an understanding of the functionality and capability of
FactoryTalk View Site Edition by:
Exploring the MightyQ Cookies application’s runtime and design components
Creating a new application
Setting up PLC communication
Creating and importing HMI displays
Creating display objects
Animating display objects based on PLC values
Creating trends
Creating and configuring PLC based HMI alarms
Creating and viewing a client HMI session
Exploring the same application in FactoryTalk ViewPoint
Tools & prerequisites

There are no prerequisites for this hands-on lab.
5 of 144
Software
This hands-on lab uses the following software:
FactoryTalk View Site Edition 9.00.00 (CPR 9 SR 9)
FactoryTalk ViewPoint SE 9.00.00 (CPR 9 SR 9)
RSLinx Enterprise 5.90.00 (CPR 9 SR 9)
RSLinx Classic 3.80.00 (CPR 9 SR 8)
Studio 5000 Logix Designer v 300
Studio 5000 Logix Emulate v 30.02.00
Lab Files
This hands-on lab uses the following files located in the listed folders:
In the Class Files folder (C:\Lab Files\FTView SE Intro Lab)
Images (folder) – images to be used as display backgrounds and company logos
FullCookieDemo.cli – a View SE client configuration used for launching the finished Cookie demo application
Cooling.gfx – a FactoryTalk View SE display to be imported in to the lab created application
Preliminary.
1. Open the Studio 5000 Logix emulate
2. This is your existing controller .which already have a Studio 5000 Program (RACE-Cookie Line) inside. You can try to open
the Studio 5000, open the RA_CE Cookie Line or upload from the controller.
6 of 144
Exercise 1: Explore FactoryTalk View Runtime – MightyQ’s Cookie Factory (10 min)
Objectives
In this exercise, you will complete the following tasks:
Launch the FactoryTalk View SE Client
Navigate between existing HMI displays
View the FactoryTalk Alarm and Events alarm viewer
Why it’s Important

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.
Interface design is important for operational efficiency and effectiveness. Exploring the sample application will also give the lab
participant a better understanding of what the end goal of the overall hands on lab session.
Lab Procedure
This lab exercise makes use of a previously configured FactoryTalk View SE application. The application is a simulation of an
entire cookie production site. Production from batching to packaging is included in the sample application. The application is
referred to as ‘MightyQ Cookies’ or just ‘Cookies’.
1. Navigate to the class files in Windows Explorer. The class files folder is located at:
C:\Lab Files\FTView SE Intro Lab.
2. Double click on the FactoryTalk View SE Client launcher, named FullCookieDemo.cli.
7 of 144
This will cause a small pop up display with a double progress bar to appear. This progress bar will take a few seconds to
finish.
With the FactoryTalk View SE Client opened, you should be able to see the following screen.
The MightyQ Cookie HMI demo is comprised of two main screen areas. The first area is the top banner. This
screen area is always on display, and is for general system wide information and navigation. Typically, the
banner area is used for alarm information, time display, navigation, and application identification. The far left
icon, in the shape of three horizontal bars, will call a drop down list. This drop down list contains a historical
navigation menu.
8 of 144
The final bottom screen area is the production display. This area of the HMI changes based on how the user
navigates between displays. Clicking on a production section name (e.g. Cooling or Case Packer) on the
navigation banner will show a display with information specific to that area of production, replacing the previous
production display. The display shown below is for plant wide overview.
3. Move the mouse cursor over the top of the four Silo level indicators in the top right portion of the screen.
Notice the appearance of a black border around the entire Silo level indicator group.
Tip – Objects that have a click action will be indicated with a bold border that appears when the mouse
cursor is moved over that object. The action that occurs when an object is clicked depends on the Touch
Animation set for that display object. We’ll learn more about Animations in a later exercise.
9 of 144
4. Click on the Silo Group indicators. The resulting material storage display is shown.
5. Click on the Mixer text in the Navigation banner. The resulting mixer display is shown.
10 of 144
6. Click on the Mixer mode select switch. The selector switch will change from AUTO to SEMI-AUTO (or vice
versa).
7. Click on the Alarm text in the navigation banner. The alarm display will be shown.
11 of 144
From here, you can see the alarm summary display object in the bottom area of the display. Alarm functionality
will be discussed in greater detail in a later exercise.
8. Close the display client by clicking on the X icon in the top right corner of the window.
This concludes Exercise 1 [ Explore FactoryTalk View Runtime – MightyQ’s Cookie Factory ].
12 of 144
Exercise 2: Create an Application from Studio 5000 Architect (10 min)
Objectives
modify the computer and logical servers created by the Single Process Server template
extend the FactoryTalk View SE Distributed application to include additional logical servers
configure the new HMI Server with library objects
commit the work done in Architect to the actual FactoryTalk View SE Distributed project
Create a new FactoryTalk View SE Local Station application
Create an RSLinx Enterprise data server
Create a device shortcut to a programmable controller

The FactoryTalk Application is a container for all of the necessary 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 project(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.
Lab Procedure
In this exercise, you will use the FactoryTalk View SE Studio HMI development environment.
13 of 144
1. Open Studio 5000 Architect.
2. Under the Toolbox search window, Type ‘Factory’, to quickly search for the Factory Talk View SE Server.
3. Drag and Drop the ‘FactoryTalk View SE’ Server from the Product Catalog to the Process Area layout
page. This is a quick way to create a computer with the logical server.
4. New Computer Graphic Dialog will appear for the computer being created. Type ‘CookieDemo’ for the
name, and select ‘DESKTOP-VJFSTD3’ (This is the computer that you’re using) for the Computer Name.
Click ‘OK’.
14 of 144
5. New FactoryTalk View SE Station Project Dialog appears, type ‘CookieDemo’ for HMI Server name, and
click ‘OK’
6. New Rslinx Enterprise Dialog appears, type ‘CookieLine’ for Rslinx Enterprise Server name, and click ‘OK’
15 of 144
7. Go to Alarm & event tab and Enable alarm & event Support. Then click OK
8. Give name Cookiealarm at Alarm and Evernt server Project
9. Link the New FT View Station to the L18ERM
16 of 144
10. Drag and Drop L18ERM to the New FT View Station
11. Click OK, (We will be using small part of the L18ERM-BB1B).
12. Commit the project, click OK, then right click and choose open in Designer.
17 of 144
Beside from Studio 5000 Architect you can create the FactoryTalk View Station from FT View Studio
program.
Choose What kind of application
18 of 144
13. At this point, you should be able to observe the FactoryTalk View Studio main window. The window contains
an Explorer pane (seen on the left) and the editor pane. The content of the editor pane depends on what is
selected from the ‘Explorer’ pane.
19 of 144
Looking closer at the Explorer pane, you can see the Application and the HMI project that have been created.
Tip – Local Station applications (versus Network applications) can only have HMI and DATA servers on the
same computer. The HMI server is named the same as our application name, and automatically created. In a
Network application, the HMI project must be created manually, and may be named differently than the
application.
14. In the Explorer pane, expand the newly created RSLinx Enterprise data server object and double click on
the Communication Setup option.
20 of 144
Creating RSLinx Enterprise can also be done from Right click on the Application CookieDemo.
‘RSLinx Enterprise Server Properties’ window will be able to be configure in the FT View Studio
21 of 144
8. In the Explorer pane, expand the newly created RSLinx Enterprise data server object and double click on the
Communication Setup option.
9. In the device shortcut editor pane, complete the following tasks:

(A) Click on the Add button.
(B) Type in the name “CookieLine” into the name field.
(C) In the device tree, browse the 1789-A17, Backplane object and select the RSLogix 5000 Emulator processor.
(D) In the bottom area, click on the Alarm and Events, Enable selection and pick ‘Yes’.
(E) Click on the Apply button. In the resulting pop up, click the YES button (the pop-up is not shown).
(F)To finish creating the device shortcut, click the OK button at the bottom right.
If you see above you have added the “emulator” controller and the “L18ERM “controller in you HMI. This is how you link to
many controller s in the Plant.
This concludes Exercise 2 [ Create an Application ].
22 of 144
Exercise 3: Create HMI displays, Import HMI displays (20 min)
Objectives
Create a header display
Create an overview display
Add a previously developed cooling line display
Create an alarm display

A graphic display represents the operator’s view of plant activity. The display can show system or process data, and provide
operators with a way to read values from or write values to external devices such as programmable controllers.
Lab Procedure
Create the Header display

This display will be used for status and navigation information. Unlike the other displays, this display is intended to be always on
display, and will be configured to be displayed at the top of the screen.
1. In the Explorer pane of FactoryTalk View Studio, right click on the Displays object in the Graphics folder within
the CookieDemo HMI project. 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 spot in the HMI client.
23 of 144
2. Edit the properties of this display by right clicking on an open area of the display. From the right click menu,
select Display Settings.
24 of 144
3. Make the following changes to the display’s settings:
(A) Uncheck the Title Bar appearance. This should also grey out the System Menu and Minimize Button checkboxes.
(B) Press the Specify Size in Pixels radio button. Set the width and height as follows:
Width: 1280 Height: 150
(C) Press the Specify Position in Pixels radio button. Set the X and Y positions as follows:
X: 0 Y: 0
(D) Choose a background color by clicking on the white square and selecting a light gray.
(E) Uncheck the box to Track Screen for Navigation.
(F) Click the OK button to finalize your screen changes.
You should see the display resize and change background color. In later exercises, we will add items to this display.
25 of 144
4. Close this display.
Tip – Make sure that you are closing the display editor, and NOT the entire Studio environment. This is the
‘inner’ close icon, not the outer close icon. Refer to the pictures below.
If the display editor was maximized, it may also look like this:
Make sure you close the inner / lower close icon.
26 of 144
5. Click on the Yes button when prompted to save the display.
6. In the Save prompt:

(A) Type the name “Header” in the Component Name text area.
(B) Click the OK button.
Opening an existing display

After one or more displays have been created, the Displays object in the Explorer pane will have a plus “+” icon to the left,
indicating that it has contained items. Expand the container and observe the newly created Header display. Displays can be
launched by double clicking on the name of the display, or by right clicking on each display name and selecting ‘Open’. Other
operations related to displays (like delete, rename, etc.) can be executed from the right click menu.
7. Double click on the Header display to launch the display editor.
8. Now that you see how to open a display for editing, you can now Close this Header display.
27 of 144
Create the Overview display
This display will be used for the starting display in the bottom part of the client interface. It contains a picture of the entire
production line. The overview display will be configured to be displayed at the lower part of the screen.
9. Right click on the Displays object in the Explorer pane and create a new display. Refer to step 1 of this
exercise if necessary.
10. Right click on the open display and choose Display Settings from the menu.
11. Make the following changes to the new display’s settings:

(A) Uncheck the Title Bar appearance checkbox. This will also grey out the System Menu and Minimize Button checkboxes.
(B) Check the Size to Main Window at Runtime checkbox.
(C) Press the Specify Size in Pixels radio button. Set the width and height as follows:
(D) Press the Specify Position in Pixels radio button. Set the X and Y positions as follows:
X: 0 Y: 0
(E) Choose a preferred background color by clicking on the white square.
(F) Check the box to Track Screen for Navigation. Type the name Overview into the Navigation History Screen Name.
(G) Click the OK button to finalize your screen changes.
28 of 144
12. With the new display still open, right click on the Images container in the Explorer pane. Select the Add
Component Into Application… menu option.
13. (A) Browse to C:\Lab Files\FTView SE Intro Lab\Images.

(B) Select the background_01_overview_1280x1024.BMP file.
(C) Click the Open button.
29 of 144
14. Return to the newly created display. From the top menu strip, select Objects > Drawing > Image.
Tip – The top menu of FactoryTalk View Studio is called the ‘Menu bar’; 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 it has the focus for editing.
15. Move your mouse cursor over the open display. The mouse cursor has changed to include the word ‘Image’ in
tiny letters to the bottom right of the cursor. Left click and drag a rectangle of any size on the display.
30 of 144
16. When the mouse button is released from the previous step, an Image Browser window appears.
(A) Select the background_01_overview_1280x1024 image we imported in the previous step.
The image has been put on the display, but it needs to be in the right spot to not have any blank space on the
display. The properties of this image can be modified to put the object in an exact spot.
17. Right click on the image object in the display editor and select Properties from the right click menu.
31 of 144
18. In the Image Properties window:
(A) Switch to the Common tab.
(B) In the Common Tab, set both the X and Y position to 0 (zero).
(C) Click the OK button.
The image should be displayed in the top left corner.
32 of 144
19. Right click on the image object and select Convert to Wallpaper. This function makes the image part of the
‘background’ of the display. When an object is in the background, all other objects are by default placed on top of
this object.
20. Close this display, and save the display as Overview.
Adding a previously created display

There may be times when displays will be used across multiple applications. In this case, being able to add existing displays
allows previously created displays to be easily reused. The Cooling display for this Cookie Factory application will be imported
from an external file location. The Cooling display contains information and objects with information relevant to that area of the
Cookie Factory. In future exercises additional trends and animations will be added to this display.
21. Right click on the Displays container within the Explorer pane and select Add Component Into Application…
33 of 144
22. In the Add Component Into Project window:
(A) Navigate to “C:\Lab Files\FTView SE Intro Lab\” folder.
(B) Select the Cooling.gfx file.
34 of 144
23. Open the newly added Cooling display. (You can double click on the name or right click and select open.)
When the display opens, there’s a large blue object with a white X pattern on it. This is a sign of a missing reference to an
image. The background for this display will have to be added to the HMI project.
35 of 144
24. Using the same approach as earlier, add the necessary image to the HMI project by right clicking on the Images
container in the Explorer pane.
25. In the Add Component Into Project window:

(A) Navigate to the following path: C:\Lab Files\FTView SE Intro Lab\Images\
(B) Select the background_05_cooling_1280x1024.BMP image
36 of 144
26. Close the Cooling display. If prompted to save this display, click Yes. Reopen the Cooling display and confirm
the background image was properly loaded.
27. Close the Cooling display.
37 of 144
28. Create a new display. This display will be called Alarms. Right click on the new screen and set the following
properties:
(A) Uncheck the Title Bar appearance checkbox. This should also grey out the System Menu and Minimize Button
checkboxes.
(B) Check the Size to Main Window at Runtime checkbox.
(C) Press the Specify Size in Pixels radio button. Set the width and height as follows:
(D) Press the Specify Position in Pixels radio button. Set the X and Y positions as follows:
X: 0 Y: 0
(E) Check the box to Track Screen for Navigation. Type the name Alarms into the Navigation History Screen Name.
(F) Click the OK button to finalize your screen changes.
29. Close this display and name it Alarms.
This concludes Exercise 3 [ Create HMI displays, Import HMI displays ].
38 of 144
Exercise 4: Create display objects
Objectives
Add images to the Header display
Add navigation buttons to the Header display
Add static text and dynamic string displays to the Cooling display

Basic display objects create the visual structure of displays. They indicate what purpose graphic objects serve. Without them, an
operator would have no idea what information an indicator is displaying. Text and shape display objects visually organize
information.
Lab Procedure
Building the Header display

The header display will have two images and three navigation buttons added to it. When this section of the exercise is done, the
Header display should look like the following:
39 of 144
1. Add the Rockwell Automation and MightyQ’s Cookie Co logos to the application:
• Right click on the Images container in the Explorer pane and choose Add Component Into Application...
and select the following files from C:\Lab Files\FTView SE Intro Lab\Images
o ra-logo-transparent-small.bmp
o mightyq cookie co 276_91.bmp
• Click the Open Button.
2. Add the images to the Header display. The last time we added an image, it was done using the Menu Bar at the
top of the Studio window. This time, find the Image icon in the toolbox and click on it.
40 of 144
3. With the Image tool selected (you can tell this from your cursor), click and drag a rectangle on the header
display.
(A) Select the Rockwell logo as the image source.
4. Right click on the resulting Rockwell logo image and select Properties. In the properties window, change the
Image Back Style to Transparent. Click the OK button.
41 of 144
5. Repeating steps 2 – 4, add the MightyQ logo in the same way, and move it to the far right side of the display.
6. Using the Button tool (as seen below), create a button on the Header display. Don’t worry about how big the
button object is for now; you can modify the size later. You can also use the Menu Bar menu by selecting
Objects > Push Buttons > Button.
When you click, drag and release the cursor, the properties window for the button object is displayed.
42 of 144
7. On the button properties window, make the following edits:
General tab
(A) Set the Style to No Border
(B) Uncheck the Highlight when object has focus checkbox
Action tab
(C) Type in the following for the Release action: Display Overview
In the Up Appearance tab
(D) Change the Fore Color to White and Back Style to Transparent
(E) Change the Caption to Overview
(F) Change the Font Size to 18
(G) Click the Bold style Font button (alternatively, use the … browse button to set the style)
In the Common Tab
(H) Set the Height to 50 and the Width to 200
Click OK when you are finished making the changes.
43 of 144
The resulting button looks like the following image. The button is indicated by the 8 selection markers.
8. Make two copies of this button object. This can be done by left clicking on the button object to select it, and then
pressing the keyboard shortcut Ctrl+C (hold Ctrl and press C), and then pressing the keyboard shortcut Ctrl+V
to paste a copy of the button on to the display.
For the two buttons, right click on each button and select Properties. In the Properties menu of each button, make the
following changes:
For the Cooling area button:
o On the action tab, change the Release Action to Display Cooling (refer to ‘C’ of the previous step)
o On the Up Appearance tab, change the Caption Text to Cooling (refer to ‘E’ of the previous step)
For the Alarms button:
o On the Action tab, change the Release Action to Display Alarms
o On the Up Appearance tab, change the Caption Text to Alarms
9. To align all of the buttons, hold the Control 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 each button selected, as
shown below.
44 of 144
10. With the three buttons selected, use the Menu Bar and make the following selections:
Arrange > Space Horizontal
Arrange > Align Bottom
Your Header display should look similar to the following image:
Verify that the buttons are aligned with the bottom of the screen by holding down the shift key and dragging them to the
bottom with your mouse or setting the Top property on the Common tab of the Properties dialog of each to 100.
45 of 144
11. Use the Menu Bar and select the rectangle tool.
Objects > Drawing > Rectangle
Alternatively, you can click on the Rectangle toolbox icon to select the Rectangle tool.
Tip – Hovering the mouse cursor over any of the toolbox icons will allow you to see the purpose of that icon
in the form of a yellow label. Try it out!
46 of 144
12. With the Rectangle tool, drag a rectangle object on to the display. This rectangle will be used as a background
for the navigation buttons. Don’t worry about the exact size; these properties will be changed later. The
properties window for the new rectangle object should pop up.
47 of 144
13. In the rectangle properties window, make the following changes:
In the General tab:
(A) Change the Line Style to None
(B) Change the Back Style to Gradient
(C) Click on the Back Color to launch the Gradient Fill window. In the Gradient Fill window:
(D) Change the Start Color to a dark grey
(E) Change the End Color to a lighter grey
(F) Change the Shading Direction to Vertical
(G) Change the Fill Direction from Dark to Light
48 of 144
(G) In the Common tab:
o Change the Height to 50
o Change the Width to 1280
o Change the Top to 100
o Change the Left to 0
(H) Click the OK button.
With those properties changed, the Header display should look similar to the following image:
The rectangle has been drawn on top of the previously created buttons.
Tip - By default, objects have a ‘depth’ order based on when the object was created on the screen; later
objects are placed over previously created objects. This depth order can be indirectly changed using the
‘Bring to Front’ and ‘Send to Back’ options on the Arrange context menu / Menu Bar.
49 of 144
14. Right click on the recently created rectangle and select Arrange > Send to Back from the right click context
menu.
The Rectangle should now be shown underneath the original navigation buttons.
15. Close and save the Header display.
50 of 144
Building the Cooling display
The Cooling display has some work already completed, but needs additional functionality added. The functionality for Cooling
Zone 1 has been finished, but the second and third cooling zones still have development work left to do. Trends on the Cooling
display will be completed in a later exercise. The following elements will be added in this exercise:
Zone 2 Text label
Zone 2 status String Display
Total Units Numeric Display
(optional) Zone 3 Text label
(optional) Zone 3 status String Display
16. Open the Cooling display from the Explorer pane.
17. Use either the Menu Bar or the toolbox to select the Text tool.
OR
51 of 144
18. Click and drag on the display to create a text object:
(A) Draw the text object over top of the second cooling Zone’s light gray label area. Then make the following
changes to the Text object’s Properties window:
(B) Change Text to ZONE 2
(C) Change the Font Size to 12 and set the Font as BOLD.
(D) Change the Fore Color (Font Color) to dark grey and uncheck the Size to Fit checkbox.
(E) On the Common tab change the Size to 31 Height and 108 Width.
(F) Change the Position to 117 Top and 629 Left.
(G) Click OK
52 of 144
Using tags in Display objects
The next object that will be created makes use of a live PLC value. These individual PLC values are referred to as ‘tags’. A tag is
essentially a reference to a process value, for example the pressure of a holding tank, the number of parts made in a shift, etc. In
FactoryTalk View Studio tags can be referenced by themselves, or used as part of a logical expression for more complex
relationships.
19. Use either the Menu bar or the toolbox to select the String Display tool.
OR
53 of 144
20. Using the teal area of Zone 2 as a guide:
(A) Draw a String Display object on the display. The properties window for the String Display object will appear.
In the Properties window, make the following changes:
(B) On the Common tab, Change to 20 Height and 108 Width.
(C) Change the Position to 120 Top and 766 Left.
54 of 144
On the General tab:
(C) Change the Expression to
If {::[CookieLine]Cooling_Zone2_InZone} == 1 then "Cooling" else "Idle"
You can either type this in directly, or refer to the next page for how to use the expression editor.
(D) Change the Dimensions width to 9 (if it is not already)
(E) Change the Justification to Center
(F) Click OK.
55 of 144
To change the Expression field, you can either type in the expression as it is seen above, or you can ‘build’ the expression
using the expression editor. If you use the expression editor, do as follows:
Click on the If button and select IF
Click on the Tags button and in the Tag Browser window, select the following path from the Folders pane (A):
CookieDemo > CookieLine > Online
In the Contents pane, select the (B) Cooling_Zone2_InZone tag and confirm the tag name in the (C) Selected Tag text
area.
Click OK and the tag browser will close with the selected tag displayed in the Expression text area.
Tip – If you don’t see the correct folder structure in the Folder pane (left side), or don’t see tags in the Tags
pane (right side), click the Refresh All Folders button.
There is no example image shown for the next steps while using the Expression Editor:
Click on the Relational button and select == EQ.
Type the value 1
Click the If button and select Then
Type in “Cooling” (include the double quotes)
Click the If button and select Else
Type in “Idle” (including the double quotes)
Click the Check Syntax button. The area to the right of the Check Syntax button should say ‘Valid’
As stated in the steps above, the resulting expression that you want to see is as follows:
If {::[CookieLine]Cooling_Zone2_InZone} == 1 then "Cooling" else "Idle"
56 of 144
To set the font properties, right click on the new string display and select Property Panel.
57 of 144
In the Property Panel window:
(A) Verify the selected object is StringDisplay1 (StringDisplay)
(B) Change the Font to be 12 point bold by clicking the browse … button in the value field
(C) Change the ForeColor to dark grey by clicking the browse … button in the value field
Tip – 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.
Close the Property Panel window by clicking on the X in the upper right-hand corner.
The two zones should look as follows:
58 of 144
22. Use either the Menu bar or the toolbox to select the Numeric Display tool.
OR
59 of 144
23. (A) Using the Numeric Display tool, draw a Numeric Display where the Total Units indicator should be.
The Numeric Display Properties window will appear. In the Properties Window, make the following changes:
On the Common tab:
(B) Change the Height to 20 and the Width to 60
(C) Change the Top to 535 and the Left to 719
On the General tab:
(D) Use the Tag browser (click on the Tags button) and find the Total Parts tag
60 of 144
(E) In the Folder pane: CookieDemo > Cookie Line > Online > Program:Cooling
(F) In the Contents pane: Select the mTotalParts tag
(G) Click OK
(H) Change the Field Length to 5
(I) Change the Justification to Center
(J) Click the OK button.
61 of 144
24. (A) Right click on the Numeric Display object that was just created.
(B) Select Property Panel from the right click menu.
(C) On the Property Panel, click on the ForeColor item and select Blue from the color Picker . Click on the Font
item and set the Font to Arial, Bold, size 12.
Close the Property Panel when done.
The full Cooling display should look like the following image:
62 of 144
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. Then
click the “Edit Display” button that is next to the “Test Display” button to stop testing the display.
26. Save and close the Cooling display.
This concludes Exercise 4 [ Create display objects ].
63 of 144
Exercise 5: Animate display objects (10 min)
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.

Animations of display objects allow for changing some properties of display objects based on PLC tag values. The following
properties of objects can be modified through animations:
Visibility
Color
Fill
Position on screen (Horizontal and Vertical
Size (Width and Height)
Rotation
Touch (apply actions to objects)
And more!
Lab Procedure
1. Open the Cooling Display from the Explorer pane.
64 of 144
2. Right click on an open space of the Cooling Display and select Object Explorer.
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 selecting it directly on the display. The check
boxes 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 the display. Objects can be grouped together by using the
Menu bar Arrange > Group option.
65 of 144
3. In the Object Explorer, expand the Zone2Group and expand the Zone2StatusGroup to reveal the
Zone2AnimationPolygon. Left click on Zone2AnimationPolygon to select it both in the Object Explorer and the
Cooling display, as seen below:
Tip – The names of objects are created by default as the object type with a number for the number of objects
of that type created on that display, for example, StringDisplay3. These names can be changed using the
Property Panel (or the Properties window, on the Common tab).
4. Right click on the Zone2AnimationPolygon and select Animation > Color from the menu. The animation
window will be displayed.
66 of 144
5. In the Animation tab, click on the Tag button and in the resulting Tag Browser window, select the tag
::[CookieLine]Cooling_Zone2_InZone. Click the OK button. This can be done as shown below:
67 of 144
6. 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 in the left list will cause the Value and Line / Fill
objects to update with the state. Edit the following states to have the correct Value, Line, Fill and Blink settings:
Step A)
Step B)
Step C)
Step D)
Step E)
7. Click the Apply button on the Animation window, and click the Close window.
68 of 144
8. Test the display using the Test Display button. When you are done testing, press the Stop Testing button.
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.
9. Save and close the Cooling display.

This concludes Exercise 5 [ Animate display objects ].
69 of 144
Exercise 6: Create Trends (10 min)
Objectives
Create trend objects on existing displays
Configure trend pens based on PLC data values

The trend object displays real-time data and historical data. Pens on the run-time chart represent data from the tags and
expressions that you add to the trend object. The trend object provides extensive, flexible run-time control. You can add pens,
toggle between isolated and non-isolated graphing, specify unique line settings, plot one variable against another in XY plots,
and print chart data.
Lab Procedure
The Cooling display has two trends already configured for Zone1. These trends will be created for the second cooling zone (and
if time permits, the third zone).
1. Open the Cooling display if it is not already open from the previous exercise.
2. Use the menu bar to select the Trend object. Objects > Trending > Trend
70 of 144
3. Create a trend object that is the full width and about half the height of the Zone 2 panel area.
Notice the Trend 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, we can change the way the trend appears.
Tip – The FactoryTalk View SE trend object has many properties to configure. Play around with the look and
feel of the trend object!
4. In the Trend Properties window, make the following changes:

On the General tab:
(A) Change the Display Chart Title to Temp (°C)
To get the degree symbol, hold down the Alt key, type 248 with the numeric keypad and release the Alt key
71 of 144
On the Display tab
(B) Uncheck the Display value bar checkbox
(C) Change the background color to a light grey
(D) Uncheck the Display Line Legend checkbox
(E) Check the Allow Scrolling checkbox
(F) Uncheck the Display Scrolling Mechanism checkbox
G) Uncheck the Display pen icons checkbox
On the X-Axis tab

(H) Change the time span to 6 minutes
(I) Change the Major grid lines to 3, Change the Minor grid lines to 1
72 of 144
On the Y Axis tab
(J) Change the Min / Max value option to Preset
(K) Change the Major grid lines to 1, Change the Minor grid lines to 1
5. On the trend Properties window, go to the Pens tab. On the Pens tab, PLC tags are configured as traces on the
trend. This trend will have two pens configured. Click on the Add Pens button to launch the Expression Editor.
73 of 144
6. In the Expression Editor window, click on the Tags button to launch the Tag Browser.
7. Select the tag {::[CookieLine]Program:Cooling.mCoolUDT[1].TempSetPtZone} from the Tag Browser and

click the OK button.
74 of 144
8. At the Expression Editor, confirm the expression shown below and click the OK button.
9. For the newly created pen, make the following changes:

Set the Pen color to Blue
Set the Minimum Value to 0
Set the Maximum Value to 80
Use the scrollbar to get to the Min and Max value settings for the pen.
75 of 144
10. Use the previous steps 5 – 9 to add the second pen with the tag
{::[CookieLine]Program:Cooling.mCoolUDT[1].TempZone}. Set the Pen to use the color Green, with the
same Min / Max values (0, 80).
76 of 144
11. Confirm the pen settings for the created Trend. Click OK to finish configuring the Trend.
12. If you want to change the Trend window color, this can be done by accessing the Trend’s Property Panel. Right
click on the Trend object and select Property Panel. Within the Property Panel:
Change the WindowColor property to the same light grey color used for the chart area background color
Change the WindowStyle property to Opaque.
77 of 144
13. Confirm your trend looks like the following image:
14. Test the display using the Test Display button. When you are done testing, press the Stop Testing button.
15. Save and close the Display.
This concludes Exercise 6: Create Trends.
78 of 144
Exercise 7: Create a FactoryTalk View SE Client (10 min)
Objectives
Create a startup macro to manipulate screen starting positions
Create a FactoryTalk View SE client launcher

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.
Interface design is important for operational efficiency and effectiveness.
Lab Procedure
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 context menu.
79 of 144
2. The Macro Editor will pop up. The Macro editor window looks very similar to other text editor applications. In the
first open line, type in the following commands, one per line:
Display Header /DT
Display Overview
Tip – If you double click in the Macro editor, the Command Wizard pop up will be displayed. This wizard
allows users unfamiliar with command functionality of View SE the ability to ‘build’ commands using an
interface.
Tip – 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. For those curious, the /DT switch means the display will
be docked at the top of the screen. If you double click on an open area of the Macro editor, it will bring up a
command selector. Using the command selector, you can see all of the different commands that can be
issued in a macro.
3. Close the Macro editor and save the Macro as ClientStartup.
4. In the FactoryTalk View Studio Menu bar, select the SE Client Launcher: Tools > Launch SE Client
80 of 144
5. In the FactoryTalk View SE Client Wizard, click the New button.
6. In the FactoryTalk View Client Configuration Name window, type “CookieDemoClient” as the name of the
configuration file. Click the Next button.
81 of 144
7. In the Application Type window, click the radio button for Local Station application. Click the Next button.
8. In the Application Name window, select CookieDemo from the drop down list, and click the Next button.
82 of 144
9. In the Client Components window, select the ClientStartup macro that was created earlier from the Startup
Macro drop down. Click the Next button.
10. In the Client Window Properties window:

(A) Select Maximize window.
(B) Uncheck Allow client to be resized at runtime.
(C) Click the Next button.
83 of 144
11. On the Auto Logout Window, click the Next button. (No example image is shown.)
12. On the Completion Options window, click the Finish button. (No example image is shown.)
13. The client should begin to launch. After the progress bar finishes, the client application will be displayed:
84 of 144
14. 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.
15. Close the Client window by clicking on the “X” in the top right-hand corner.
This concludes Exercise 7 [ Create a FactoryTalk View SE Client ].
85 of 144
Exercise 8: Configure Alarms (10 min)
Objectives
Reviewing how to FactoryTalk Alarm and Event server
Create a tag based alarm
Create an alarm banner object on an existing display
Create an alarm summary object on an existing display
Acknowledge a currently active alarm from the PLC

Alarms provide the operator to identify and react to abnormal operation conditions. Annunciating alarm conditions saves time,
maintains safety and increases production run-time. Operators interact with FactoryTalk based alarms in several ways:
• The Alarm Banner object
• The Alarm Summary object
• Alarm based animations of display objects
Lab Procedure
Creating a FactoryTalk Alarm and Event Server

The FTAE (FactoryTalk Alarms and Events) server is a program that runs on the HMI computer, constantly
monitoring PLC tags for alarm conditions. Adding an alarm server is a one-time configuration, after which
individual alarm conditions can be added to the server while it is in production.
86 of 144
In the Properties window for the Tag Alarm and Event Server, type in “CookieAlarm” in the Name property.
On the Priorities and History tab, verify the Enable history box is unchecked and click the OK button.
n the Explorer Pane, click to expand the newly created CookieAlarms 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 Set Up window will be displayed.
87 of 144
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 three primary alarm types: digital (on / off) alarms, deviation alarms, and level
alarms. For this lab, we will stick with a digital alarm and a level alarm. There are also two types of alarm sources: HMI / tag
based alarms, and device based alarms. Device based alarms are built in the ControlLogix controller, using specific ALMA and
ALMD instructions. Tag based alarms can originate from any PLC tag value.
1. In the Tag Alarm and Event Set Up window, click on the New Alarm button in the top left corner, and select
Digital from the drop down menu.
2. In the Digital Alarm Properties Window, set the Name to “Cooling Zone Drive Alarm”. Set the Message to
“Cooling Conveyor Drive has faulted. Check HIM mounted at cabinet SC-107.” Set the Severity to 500.
88 of 144
89 of 144
7. Click on the ellipsis button for the Input Tag field. The Tag Browser object will appear. Select the
::[CookieLine]Program:Cooling.Alarm_Control[4] tag from the Tag Browser. Click the OK button.
8. In the Input Tag field, the name of the tag selected should appear. Because we need to reference a single bit
from the tag, add .1 to the end of the tag name. It should look like the following:
90 of 144
9. Click on the OK button at the bottom of the Digital Alarm Properties window.
10. Click the Save button on the Alarm and Event Setup Window. Close the window. If prompted, save your
changes.
Alarm Display Objects

Alarms can be monitored using two main display objects: the Alarm Summary object, and the Alarm Banner. These objects
provide a viewer that can show alarms sorted by severity, time of alarm, etc. They are powerful tools for managing alarm
conditions.
11. Open the Header display using the Explorer pane.
12. Use the Menu bar to select the Alarm Banner tool.
91 of 144
13. Create an Alarm Banner object in the display area between the two image objects (the logos). The Alarm and
Event Banner Properties will be displayed. Click the OK button on this window.
14. The Alarm Banner should be shown on the Header display:
15. Save and close the Header display.
92 of 144
16. Use the Explorer pane to open the Alarms display.
17. Use the Menu Bar to select the Alarm Summary tool.
18. 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 at the bottom of the window to accept the default configuration.
19. Save and close the Alarms display.
93 of 144
20. Launch the FactoryTalk View SE Client. This can be done from View Studio using the Tools > Launch SE
Client option from the Menu bar. Select the CookieDemoClient configuration and click the Run button.
After some time, the client window will be displayed.
You may see some alarms in the banner! These alarms are Device based alarms configured directly in the PLC. The Alarm
server listens to these alarms because the PLC was configured in the Data Server configuration from Exercise 2.
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 Server. In advanced FactoryTalk
configurations, the HMI may not be on the same computer as the Alarm server.
94 of 144
21. Navigate to the Alarms display in the View SE Client.
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 purpose of demonstrating alarm functionality but there may be times where no alarms
are active and you may get that message during this lab.
22. Switch back to View Studio by selecting the icon from the task bar.
95 of 144
23. Bring up the Command Line window by double clicking on Command Line under the System folder.
Tip: The Command Line window can be used to immediate 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
applicable to running 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 to the effect of: “The
command ‘Display’ is ignored when issued from the development environment or an HMI Server.”
24. Either use the Command Wizard editor or directly type the following command:
Set ::[CookieLine]Program:Cooling.Alarm_Control[3].1 1
Hit the enter key when completed and the text will disappear.
25. Switch back to the Display Client by selecting the icon from the task bar.
96 of 144
26. After 30-60 seconds, the alarm will be automatically rectified. Notice how it will eventually disappear from the
Alarm Banner. This happens because even though the alarm condition has been rectified, it still needs to be
acknowledged by an operator or supervisor. 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:
You can also use the up arrow in the command window to select the prior command to save some typing.
27. The alarm condition has been rectified, but note that the alarm still shows up in the Alarm Summary.
97 of 144
28. Select the alarm in the Alarm Summary object, and click on the Acknowledge button (the leftmost check icon).
29. With the alarm condition rectified and the alarm acknowledged, the Cooling Conveyor Drive alarm disappears
from the Alarm Summary object. If historical logging was enabled, the alarm history viewer could be used to
review alarms over a period of time.
30. Leave the HMI Client window open.
This concludes Exercise 8 [ Configure Alarms ].
98 of 144
Exercise 9: Using FactoryTalk View SE TrendPro
About this section

In this section, you will learn about:
TrendPro Design time Configuration:
Creating a TrendPro object.
Exploring TrendPro Properties.
Adding traces and exploring trace settings.
Exploring the General tab.
TrendPro Runtime Configuration:
Adding a trace during runtime.
Zoom and Change Time span.
Print trend and save image.
Trend Properties changes.
Axis menu settings.
Trace data export.
Read about TrendPro

The TrendPro object provides modern trending capabilities with easy run-time configuration, easy drag and drop ad-hoc trending,
and statistical and sampling calculations. You can plot data from live data, FactoryTalk View SE data logs, and FactoryTalk
Historian.
By using traces, you can display and compare multiple tags concurrently independent of the data source of the tags, and
manipulate the data in a graph in a variety of ways such as panning, zooming, and scaling. You can also easily capture the
historical data to reference or analyze later.
TrendPro design time configuration
1. In FactoryTalk View Studio duplicate the Alarm Display by right click on the Alarm Display and name the
display 02_MixerTrend.
2. Open the display.delete the Alarm summary and from the Objects > Trending menu item, select TrendPro.
99 of 144
3. Place the TrendPro object within the framed border in the display 02_MixerTrend.
4. The TrendPro Properties dialog should appear.
100 of 144
5. Explore the settings on this dialog:
Chart
Specify which trend panes are displayed and whether the context menus are available to operators at runtime.
The panes include Tag explorer, Toolbar, Timebar, and Tag list. You can also specify whether to collapse the trace tag
list when the trend first runs.
Properties dialog
Specify which trend property tabs are available to operators at run time.
By default, the runtime properties dialog box includes the General and Traces tabs. The General tab includes Time
Period, Application, Chart, Retrieval, and Shape.
Trend Setup
Click this button to open the Properties dialog box and configure the detailed trend appearances and behaviors at run
time. The Properties dialog box is also available at run time if the Context menu option is enabled.
101 of 144
6. Click the Trend Setup button.
7. Click on the plus sign to add traces.
102 of 144
8. Under Live Data expand the folders to the following location:
Line1_Data\CookieLine\Online\Program:Mixer\MixerVFD_REQ and then double click on
Motor_In_Speed.
103 of 144
104 of 144
9. You should now see the trace added into the Traces tab.
Explore the setting for this trace:
Trace
The options for the trace. Select from the following:
Clear the Visible check box if you do not want trace data to appear on the chart.
In the Tag box, click Browse to navigate to another tag.
In the Historical model box, click Browse to navigate to another historical model.
Select the Caption check box and type a name for the trace that will display in the y-axis of the trend and in the Tag
field of the Legend.
Note: You must select Tag caption under Legend for the caption to display in the y-axis and Legend.
Select the Engineering units check box and type an engineering unit for the trace that will display in the y-axis of the
trend and in the Unit field of the Legend.
105 of 144
Style
The options that define the style of the trace, such as line color. Select from the following:
Click Style to modify the line color, style, and width of the trace line.
Under Legend, select whether to display the Tag name or Tag caption on the y-axis of the trend and in the Legend.
Display
The options that display on the plot. Select from the following:
Select the Statistics check box to determine whether statistics should be calculated on the trace data. The display of
statistical data is controlled on the Chart tab in the General section.
Select the Trace line check box to draw a line to connect points.
Select the Point markers check box to display measured data points.
Note: If the Trace line and the Point markers check boxes are not selected, point markers will display on the chart by
default.
Select the Direction arrows check box to display arrows to indicate the direction of a trace. This option is only applied
when a trace line exists.
Point markers
The shape, color, and size of points on the trace.
Numeric tags
The options that apply to numeric tags. Select from the following options:
In the Format box, click the down arrow to select a scientific or decimal number format for the measured data point
display.
In the Precision box, type the decimal precision for the measured data point display.
Plotting algorithm
The type of interpolation that is applied to the plot. Select one of the following options:
Select Sample and hold to draw flat lines between time periods and make adjustments along the y-axis when a change
occurs, much like a stairwell, rather than a classic line graph.
Select Linear interpolation to use an algorithm that connects data points in a progressive line fashion.
Discrete and time tags

The options that apply to discrete and time tags. Select from the following options:
106 of 144
Click the Enable shading check box to apply shading to discrete or time-period tags. These tags will usually display in
an on-off format.
Click the Use trace color check box to shade the trace using the same color as the trace line.
Click the color swatch beside the Color box and select an alternate color for the shaded area.
10. Click the Close button when done exploring the settings.
11. Click OK.
12. Save the display and close it.
13. Edit the Header and add Mixer Trend in the Header which link to the Mixer Trend Display
Using TrendPro at Runtime
1. Open the FT View Client
2. Click the Mixer Trend menu button to go to the 02_Mixer Trend display.
107 of 144
3. The Trend display should look something like the following image, with the trace being plotted in blue. (You
may need to wait for the trend to be plotted)
108 of 144
4. Right-click on the trend and from the menu select Properties.
109 of 144
5. On the Properties window, go to the Traces tab and then click the plus sign to add a new trace.
110 of 144
6. In the items list select the tag
Line1_Data\CookieLine\Online\Program:Mixer\MixerVFD_REQ.Motor_Out_Ramped.
Note that this window can be resized from the bottom right corner, and the items column size can be
expanded so that the entire tag can be read.
7. Click OK.
8. Then click Close on the Properties window.
9. The newly added trace can be seen on the trend in red.
10. Another way to add a trace is to drag and drop from the item window..
111 of 144
11. In the items list select Line1_Data\CookieLine\Online\Program:Mixer\MixerVFD_REQ.Energy and drag
and drop it onto the trend area.
112 of 144
12. This trace is plotted in the trend in green.
Additional TrendPro runtime features
1. At the bottom right of the trend area are buttons that allow zooming in and out:
2. Clicking the plus button zooms in. The minus button zooms out and the last button is the reset button, which
resets back to the default view. Explore using these three buttons.
113 of 144
3. The time span can be changed by clicking in the x-axis area and dragging the mouse to the right or left.
4. You can also right-click in the trend area and use the Time Period menu item to create a new time period
and scroll to the next one.
114 of 144
5. You can also print the trend by clicking the printer icon. In this lab, you can select printer PDFCreator.
6. You can also right-click in the trend area and select the Capture Image menu item to create an image file
of the trend area. Try printing the image and then use windows explorer to view the saved image.
7. You can also bring up the Trend Properties window by right-clicking in the trend area and selecting the
Properties menu item.
115 of 144
8. In the Properties window click on the X-axis and uncheck the checkbox for the Visible property.
116 of 144
9. Click on Close. Note that the X-axis is no longer visible. Property changes made to the trend persist while
the client is running and are reset when the client is restarted. Make the X-axis visible again.
10. Now right click in the trend area and select Axes > Stack > Y-axes.
117 of 144
11. The Y-Axis will now appear stacked for the current traces.
12. Turn stacking off by doing a right-click in the trend area and selecting Axes > Stack > Y-axes.
13. Now right click in the trend area and select Axes > Layer > Y-axes.
118 of 144
14. The Y-Axis will now appear layered for the current traces.
15. Turn layering off by doing a right-click in the trend area and selecting Axes > Trace > Y-axes.
16. Now right-click in the Trend area and select Trace Data….
119 of 144
17. The Trace Data window will appear and show all the data currently being displayed on the trend. Scroll
through the data and note that it is for all three tags. It is being displayed in the Narrow format, therefore
data for each individual tag displays in separate groups, in the order in which it was retrieved.
18. Click the Wide button and note that now data for all tags displays in one group, sorted by timestamp.
Interpolation is used to fill data gaps, and bad quality values are displayed as '<null>'.
120 of 144
19. Click the Sparse Wide button and note that data for all tags displays in one group, sorted by timestamp. No
interpolation is done to fill gaps, and bad quality values are displayed as '<null>'. This is useful when
working with date, time and string tags since it removes duplicate entries.
20. If there are additional time periods configured, they can be selected from the Time Period setting.
21. There is also the option to Print Preview the data and Print the data. Click these to see how they function,
then close the Trace Data window.
22. Click the Exit button to close the 02_MixerTrend display.
You just finished Exercise 9 TrendPro !
121 of 144
Exercise 10: Using FactoryTalk ViewPoint with FactoryTalk View SE (15 min) (Optional)
Objectives
Configure the FactoryTalk ViewPoint portal from a web browser
Navigate a FactoryTalk ViewPoint application

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 users that don’t necessarily need access to all functions of the View SE client.
Lab Procedure
1. Use the Start Screen to Launch the FactoryTalk ViewPoint Adiministration Portal. The first time this loads, it may
take a minute.
122 of 144
While waiting, here’s some important information about ViewPoint:
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’re using Internet Explorer on an operator workstation, Safari on an iPad or Google
Chrome on a 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 Standard
operator terminal functions as the server.
You will eventually see a Web Browser open with the ViewPoint Administration Portal.
123 of 144
2. Click on the Publish Displays to Web button.
3. In the resulting webpage, select Site Edition (Local) from the Application type drop down, and select
CookieDemo from the Application drop down. Finally, click the Select Graphic Displays button.
124 of 144
Available FactoryTalk ViewPoint publishing options:
Web Enable
Select whether each display should be published for viewing in a browser.
o Checked - the display will be published.
o Cleared - the display will not be published.
Initial Display
Select which display will be shown when a user first connects to FactoryTalk ViewPoint.
Mobile Enable
Select for users looking at ViewPoint from mobile devices. A URL interface is also provided for easier
navigation between displays on devices that have smaller screens. You may wish to create displays
specifically tailored to mobile users. Mobile URL: http://localhost/FTVP/m/
o Checked - the display will be published to the mobile URL.
o Cleared - the display will not be published to the mobile URL.
Re-publish all selected displays (optional)

Overwrite the existing published displays even if their content has not changed.
Select a Startup Macro (optional)

If the FactoryTalk View application selected includes a macro, from the Select a startup macro list, select a
macro that runs when a client connects to the published application.
4. On the Select Displays webpage, click the radio button to set the Header as the initial display and uncheck
it for Mobile Enable. Select the ClientStartup from the startup macro dropdown list, and then click the Publish
Displays button.
125 of 144
5. On the Publish display webpage, the progress bar will eventually complete, and the status of each display
should be shown as Done. Click on the Open Web application button. The web browser will spawn a second
browser tab, and the FactoryTalk View application will launch in this second window.
Tip: The FactoryTalk ViewPoint Administration console allows you to publish displays to the web, configure
security, set up activations, view server settings and access the on-line help.
126 of 144
6. This view is the ‘Desktop View’ of ViewPoint in the browser. The Header and Overview displays are initially
shown. Prior to publishing this was the selected initial display used in combination with the startup macro.
127 of 144
7. Navigate to the Alarms display by clicking on “Alarms” on the header. If in previous the lab steps, all the alarms
were acknowledged and turned off, then no alarms will be shown.
8. Toggle the same alarm from Exercise 8 Step 24 by executing the below command from the View Studio
Command Window and observe the new alarm appear in the Alarm Summary.
Remember, you can also use the up arrow in the command window to select the prior command.
128 of 144
9. A list of alarms can be filtered by typing in the “Quick filter” window as shown.
10. Click on one of the alarms listed to open a new window that will contain more details about the alarm.
Also provided on this detailed alarm window is the ability to “Acknowledge” or “Shelve” the alarm.
129 of 144
11. Navigate to the Cooling display by clicking on “Cooling” on the header and observe the trends.
12. Writes from displays can be enabled and controlled by security settings. In the browser click on the tab for the
FactoryTalk ViewPoint Administration.
Tip: By default, the screens available on ViewPoint are ‘read only’. When a client is set to read-only, the
numeric inputs and action buttons that could change PLC values are prohibited. 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.
130 of 144
13. Using the FactoryTalk ViewPoint Adminstration tab that is still open in the browser:
(A) Click on “Security Settings”.
(B) Click on “Secured Displays”.
(C) Click on “CookieDemo” to select the cooling display.
(D) Click the box next to “Enable Write” to place a check mark in it.
(E) Click on “Save” to save the settings.
131 of 144
18. In FactoryTalk View a Mobile Device interface is also offered for easier navigation on devices which
may have smaller and varied screen sizes.
(A) Navigate to the following URL in the Chrome browser: http://localhost/FTVP/m/
(B) Notice that the “Header” display is not shown. This because you were instructed back at step 4 to
un-check this display so that it was not to be Mobile Enabled.
(C) Near the top click on Alarms that is shown next to Displays (do not click on the display named
Alarms).
19. You will see any active alarms here.

(A) Click on the one of the alarms to view the alarm details.
132 of 144
20. Review the alarm details. Notice at the bottom that you are provided with options to Acknowledge or Shelve the
alarm.
133 of 144
21. (A) Near the top of the browser window, click on Displays.
(B) Then click on the Overview display.
22. 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
developer tools. Navigate from the Menu to More tools and select Developer tools.
134 of 144
23. Use the Toggle device toolbar button to enable the device toolbar above the web page image if not already
visible.
24. Select the device to emulate from the drop down 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.
135 of 144
23. The browser content has to be more compact when using smaller display sizes / devices. Notice in the right top
corner you can see an indication of the alarms there. Click on the navigation icon on the top right as shown.
136 of 144
24. Click on Alarms.
137 of 144
25. You can click on individual alarms here for more detail and can choose to Acknowledge or Shelve alarms at the
bottom.
You may try out other mobile display sizes and/or look at other different displays.
Click the navigation icon located in the top right or left for options.
Tip – If you know you will have users looking at ViewPoint from mobile devices, you can create screens
specifically for those users, or change the default resize behavior of displays.
138 of 144
Exercise 11: Update the Studio 5000 Architect Project and add faceplate.
Objectives
Updating the Changes that you have made in the Studio 5000 Architect
Add standard faceplate from Studio 5000 Architect
Test the faceplate from Studio 5000 Architect

This will make your whole Project centralize and it will be easier to manage all the faceplate and library.
Lab Procedure
1. Navigate back to Architect, right-click on ‘CookieDemo’ and select ‘Update Project Changes’. Updating a
Project saves changes that were made in Logix Designer or FactoryTalk View to the Architect program.
2. Update Summary dialog appears. To see the list of changes that will occur when selecting Update, expand
the Ice_Cream_Plant project. Click ‘Update’
139 of 144
3. Ethernet Configuration Dialog appears. Leave devices and port configuration as is. Click ‘OK’
Let’s make an observation

Edits made in FactoryTalk View Studio have been updated back into Architect. To see that CookieDemo has been updated
in Architect.
Expand the ‘Displays’ in the Ice_Cream_HMI server and notice the new display Overview, Alarm and Cooling are displayed.
.
As you have created the Faceplate on the PVP 6 we will do the same here with the L18ERM
controller.
140 of 144
Add Library Objects to the HMI Server
1. Drag and Drop the ‘FactoryTalk View SE’ folder located under 01 – Common > FactoryTalk View SE over
the CookieDemo.
2. Drag and Drop the ‘FactoryTalk View SE’ folder located under 02 – Process Objects > IO Processing >
Basic Analog Input (P_AIn) over the Ice_Cream_HMI Server.
3. Commit the Project and right click and select open in designer.
4. Open the ‘(RA-BAS) P_AIn Graphics Library’ under the Global Objects folder
Open the Cooling Display
141 of 144
Move the ‘(RA-BAS) P_AIn Graphics Library’ to the right to see the ‘Cooling’ display.
Drag and drop the ‘Analog Inputs: Standard (P_Ain)’ Global Object to the new display.
5. Close the ‘(RA-BAS) P_AIn Graphics Library’ Global Object file.
6. When prompted, select ‘No’ to not save the changes.
7. Right-Click and select the ‘Global Object Parameter Values’
142 of 144
8. Select the ‘browse button’ next to the #102 parameter value
9. Find and select the ‘L18ERM-BB1B > Online > Program:Area > TT001’
Notice the path was automatically copied into the Selected Tag below. Click ‘OK’ button
10. Save the Display and run FT View Client
11. You’ll see the Picture below:
143 of 144
12. Click the Analog input that you just created to display the faceplate.
This concludes all of the exercises for the lab. Thank you for your time and participation!
144 of 144

L1 FT View SE Station Lab

Uploaded by

Copyright:

Available Formats

L1 FT View SE Station Lab

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

L1 FT View SE Station Lab

Uploaded by

Copyright:

Available Formats

L1 Basic Training

For Classroom Use Only!

Identifies information about practices or circumstances

Exercise 3: Create HMI displays, Import HMI displays (20 min)................................................................. 23

Exercise 4: Create display objects .............................................................................................................. 39

Exercise 5: Animate display objects (10 min) ............................................................................................. 64

Exercise 7: Create a FactoryTalk View SE Client (10 min) ........................................................................ 79

Exercise 8: Configure Alarms (10 min) ....................................................................................................... 86

Exercise 9: Using FactoryTalk View SE TrendPro...................................................................................... 99

About this lab

This lab takes approximately 90 minutes to complete.

Who should complete this lab

What you will accomplish in this lab

Tools & prerequisites

Why it’s Important

2. Double click on the FactoryTalk View SE Client launcher, named FullCookieDemo.cli.

Why it’s Important

8. Give name Cookiealarm at Alarm and Evernt server Project

9. Link the New FT View Station to the L18ERM

Choose What kind of application

9. In the device shortcut editor pane, complete the following tasks:

This concludes Exercise 2 [ Create an Application ].

Why it’s Important

Create the Header display

Make sure you close the inner / lower close icon.

6. In the Save prompt:

Opening an existing display

7. Double click on the Header display to launch the display editor.

11. Make the following changes to the new display’s settings:

13. (A) Browse to C:\Lab Files\FTView SE Intro Lab\Images.

The image should be displayed in the top left corner.

20. Close this display, and save the display as Overview.

Adding a previously created display

25. In the Add Component Into Project window:

27. Close the Cooling display.

29. Close this display and name it Alarms.

This concludes Exercise 3 [ Create HMI displays, Import HMI displays ].

Why it’s Important

Building the Header display

Your Header display should look similar to the following image:

15. Close and save the Header display.

16. Open the Cooling display from the Explorer pane.

26. Save and close the Cooling display.

This concludes Exercise 4 [ Create display objects ].

Why it’s Important

1. Open the Cooling Display from the Explorer pane.

9. Save and close the Cooling display.

Why it’s Important

4. In the Trend Properties window, make the following changes:

On the X-Axis tab

7. Select the tag {::[CookieLine]Program:Cooling.mCoolUDT[1].TempSetPtZone} from the Tag Browser and

9. For the newly created pen, make the following changes:

15. Save and close the Display.

This concludes Exercise 6: Create Trends.

Why it’s Important

3. Close the Macro editor and save the Macro as ClientStartup.

10. In the Client Window Properties window:

This concludes Exercise 7 [ Create a FactoryTalk View SE Client ].

Why it’s Important

Creating a FactoryTalk Alarm and Event Server