FactoryTalk View Site Edition V15 - Basic Lab
FactoryTalk View Site Edition V15 - 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
Before You Begin ............................................................................................................................ 6
About this Training Lab ......................................................................................................... 6
Duration ............................................................................................................................... 6
Prerequisites ........................................................................................................................ 6
Materials .............................................................................................................................. 6
Exercise A: Explore FactoryTalk View SE Runtime ........................................................................ 8
Objectives ............................................................................................................................8
Scenario ...............................................................................................................................8
Practice................................................................................................................................8
Exercise B: Create an Application ................................................................................................. 14
Objectives .......................................................................................................................... 14
Scenario ............................................................................................................................. 14
Practice.............................................................................................................................. 14
Exercise C: Create and Import HMI Displays ................................................................................. 20
Objectives ..........................................................................................................................20
Scenario .............................................................................................................................20
Practice..............................................................................................................................20
Exercise D: Runtime Navigation Configuration ............................................................................ 33
Objectives .......................................................................................................................... 33
Scenario ............................................................................................................................. 33
Practice.............................................................................................................................. 33
Exercise E: Create Display Objects............................................................................................... 40
Objectives ..........................................................................................................................40
Scenario .............................................................................................................................40
Practice..............................................................................................................................40
Exercise F: Animate Display Objects ............................................................................................ 70
Objectives .......................................................................................................................... 70
Scenario ............................................................................................................................. 70
Practice.............................................................................................................................. 70
Exercise G: Create a FactoryTalk View SE Client ..........................................................................76
Objectives .......................................................................................................................... 76
Scenario ............................................................................................................................. 76
Practice.............................................................................................................................. 76
Exercise H: Configure Alarms ....................................................................................................... 83
Objectives .......................................................................................................................... 83
Scenario ............................................................................................................................. 83
Practice.............................................................................................................................. 83
Exercise I: Create Trends ............................................................................................................. 98
Objectives .......................................................................................................................... 98
Scenario ............................................................................................................................. 98
Practice.............................................................................................................................. 98
Exercise J: Create Global Objects ............................................................................................... 107
Objectives .........................................................................................................................107
Scenario ............................................................................................................................107
Practice.............................................................................................................................107
Appendix 1: Using FactoryTalk ViewPoint with FactoryTalk View SE (Optional) ......................... 119
Objectives ......................................................................................................................... 119
Scenario ............................................................................................................................ 119
Practice............................................................................................................................. 119
Appendix 2: DataLogPro and TrendPro ....................................................................................... 133
Objectives .........................................................................................................................133
Scenario ............................................................................................................................133
Practice.............................................................................................................................133
Appendix 3: Runtime Security ..................................................................................................... 142
Objectives ........................................................................................................................ 142
Scenario ........................................................................................................................... 142
Practice............................................................................................................................ 142
Appendix 4: Language switching ................................................................................................. 151
Objectives ......................................................................................................................... 151
Scenario ............................................................................................................................ 151
Practice............................................................................................................................. 151
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 15.00.00 (CPR 9 SR 15)
☐ FactoryTalk ViewPoint SE 15.00.00 (CPR 9 SR 15)
☐ FactoryTalk Linx 6.50.00 (CPR 9 SR 15)
☐ FactoryTalk Logix Echo 3.00.00 (CPR 9 SR 14)
☐ Studio 5000 Logix Designer v36.00.00 (CPR 9 SR 14)
☐ FactoryTalk Services Platform 6.50.00 (CPR 9 SR 15)
Objectives
In this exercise, you will complete the following:
• Launch the FactoryTalk View SE Client
• Navigate a completed HMI application
• 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 named Demo_Overview.
The most exciting part of this exercise is that in the upcoming exercises, you'll have the
opportunity to build an identical application yourself!
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.
Header: The first area is the header, located at the top of the screen. This area is always
visible and serves as a place to display general system-wide information. Typically, it can be
used to show alarm notifications, the current time, and application identification.
Navigation Menu: The second area is the Navigation Menu, which is also always displayed and
is docked just below the Header display. The Runtime Navigation Menu display is predefined
and can be customized. It allows users to navigate between different displays, including the
History, Back, and Forward functions. Please keep in mind that this lab presents only the
basic functions of this display. To learn more, please check out our "What’s New in
FactoryTalk View SE" Lab, where this topic is explored in greater detail.
Production Display: The larger portion of the main screen is dedicated to the production
display. This area of the HMI changes based on the user's navigation. Clicking on a production
section name (such as "Overview" or "Cooling") in the navigation menu, will bring up a display
with information specific to the selected production area, replacing the previous display. For
example, the display shown below represents the Cooling area.
Footer: Finally, at the bottom of the screen, there is a Footer area, which is always visible. In
this application, it is used primarily as a visual closure for the application view.
3. Click the Cooling text in the Navigation Menu area and the corresponding cooling display will
appear.
5. You may notice that the Dashboard display cannot be opened, and special privileges are
required. To access this display, click the Login button in the Header area and log in with the
following credentials:
user: Operator
password: rockwell
Once logged in, you should be able to open the Dashboard display. You’ll also see that
information about the currently logged-in user is displayed just below the FactoryTalk View
Studio logo in the Header area.
6. Click on the Alarms text in the Navigation Menu and the associated alarm display will be
shown. Here, you can view the alarm summary display object in the main section of the
screen. While alarm functionality will be explored in more detail in a later exercise, you can
generate a new alarm by using the alarm icon. This new alarm will appear both in the summary
section and in the alarm banner object within the Header area of the application.
7. Use the navigation buttons to explore the ability to navigate between displays based on your
navigation history. Click the Backward button to view the previously opened display, then
click the Forward button to return to the most recent display.
8. Use the History button to check your navigation history. From the list that appears, select any
display you want to revisit
9. Go to the Overview display and click on the Cooling Status indicator. You will be taken to the
Cooling display. This demonstrates another way to navigate between displays in the
application
Notice the appearance of a blue border around the Cooling Status objects group.
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.
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.
10. 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 virtual 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 taskbar
shortcut
b. Click Continue
3. When the ‘New / Open Site Edition (Local Station) Application’ pop-up is shown:
Factory Talk View Studio will now prepare a new application and working environment for you.
Once it is created and loaded, you will 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
have 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 is therefore automatically
created. In a Network application, the HMI project must be created manually and may be named
differently than the application.
e. In the displayed menu, select Add New Server -> Rockwell Automation Device Server
(FactoryTalk Linx)…
d. 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 that the dropdown for
Subscribe To is “All Alarms and Events Notifications Messages”
e. Click the Apply button. In the resulting pop-up, click YES (pop-up not shown)
f. To finish creating the device shortcut, click the OK button at the bottom right.
In Factory Talk Linx pop-up window click Yes, to confirm the changes
Objectives
In this exercise, you will:
• Create an overview, alarm, and footer display
• Add a previously developed header, cooling, and dashboard 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. In this exercise, we will build the framework of our
application. The application will consist of four main components: three fixed elements—Header,
Footer, and Navigation Menu—and a section of the screen for the main content. By properly
configuring the displays and later invoking them through a macro (in one of the upcoming
exercises), we will achieve the desired effect. This is the design of your application:
You don't need to create all the components from scratch. Instead of building some objects, you
will import ones that have already been prepared. This is intended to make your work easier and to
avoid repeating similar tasks that you need to perform.
Practice
Create the Footer Display
In this application, the Footer display is used primarily as a visual closure for the application view.
This display is intended to always be open and will be configured to be parked at the bottom 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
footer display. In the next steps, the properties of the display will be edited to allow the footer
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 the Background Color by selecting the color swatch square and selecting a dark
gray color:
You should see the display resize and the background color change. In later exercises, you will
continue to develop this display.
8. 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
the System Menu and Minimize Button just below
c. Select Specify Size in Pixels and set weight and height as follows:
X: 0 , Y: 0
10. With the new display still open, right-click on the Images container in the Explorer Pane.
12. 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.
13. 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
14. When the mouse button is released from the previous step, an Image Browser window
automatically opens:
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.
15. Right-click on the image in the display editor and select Properties.
c. Click OK
The image will now be shown 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.
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
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 Alarms display. Displays can be launched in 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.
Adding Previously Created Displays
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 them into the application.
Three added displays, for now, do not require any changes. You can open those displays and check
how they look. Do not save any changes when closing. In future exercises, those displays will be
used and modified to familiarize you with the Factory Talk View Site Edition features.
NOTE
Importing displays with integrated images is not possible, and images need to be imported
separately. In this Lab, we handled this task for you, as you already learned how to do that in one
of the previous tasks
This is how your Displays folder in the application should look after this exercise:
Objectives
In this exercise, you will complete the following:
• Configure the Runtime Navigation Menu
• Add displays to the menu
• Add icons to the menu
Scenario
Runtime Navigation Menu was introduced in version 14 and makes it much easier to create an
advanced navigation menu with a search function. In this exercise, we will create a new navigation
that will allow you to navigate through the application.
Practice
Configuring the navigation menu
1. Open Navigation Menu Configurator (double-click the icon)
4. Select Navigation Menu, and click the “+” Icon to add new Menu Items.
5. Check Alarms, Cooling, Dashboard, and Overview displays checkboxes. Click OK to finalize
menu changes.
6. Click and drag the Overview display just below the Alarm display.
9. In the following display click Add icons, as we do not have an Alarm icon added by default.
10. In the File Browser select Alarm.svg image, and click Open.
11. Now Alarm.svg is available on the list. Select the icon, and then click Ok.
12. Confirm the changes in the Alarms navigation field, by clicking Ok.
The Navigation Menu is now created. This display can be tested only on running Factory Talk View
SE Client. In one of the next Exercises, you will learn how to add a Navigation Menu to your running
application and will have a chance to see how it works.
Objectives
In this exercise, you will complete the following:
• Add image object to the Footer displays
• Add static text and dynamic string displays to the Cooling display
• Add a navigation button to the Overview 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 out the Footer Display
1. Add the Rockwell Automation logo to the application:
Right-click on the Images container in the Explorer pane and choose Add Component Into
Application… Navigate to C:\Lab Files\BasicLab\Images, select the RA_Logo.png image
file and Click Open
2. In View Studio, open the Footer display (if not already open). Add the image to the Footer
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 Footer 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 RA_Logo image and click OK.
4. Right-click on the RA logo image and select Properties. In the properties window, select the
Common tab, and in the position section change the following: Top: 5 and Left: 475. Click OK
to finalize screen changes.
7. Using either the Menu Bar or the Toolbox, select the Drawing/Text tool
8. Click and drag on the display to create a Text Object. Draw the Text Object over the top of the
second cooling zone’s light grey label area
9. The properties window will automatically open, make the following changes:
c. Change the Fore Color to dark grey (Hex: 3F, 3F, 3F) and uncheck Size to Fit
Hex designations appear as you cover your mouse over the color swatch.
c. Click OK
10. Use either the Menu Bar or the Toolbox to select Numeric and String/String Display
11. Click and drag on the display to create a string display. Use the teal-colored area of Zone 2 as
a guide to draw the object
12. The properties window will automatically open, make the following changes:
TIP
If you are having any issue with syntax, open Alarm Syntax Help.txt from
C:\LabFiles\BasicLab to compare or copy and paste.
e. Click OK
[OPTIONAL] 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:
• Click on the If… button and select If
• Click on Tags… button and in the ‘Tag Browser’ window, select the following path
from the Folders page: CookieDemo > CookieLine > Online
- 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 button
• 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
• Click on the Relational button and select == EQ
• Type the value 1
• Click the If button and select Then
• Type in “Cooling”
• Click the If button and select Else
• Type in “Idle”
• Click the Check Syntax button. The area to the right of the Check Syntax button
should say “Valid”
13. To set the font properties, click on the string display and open the Property Panel at the
bottom right corner of View Studio.
b. Highlight the Font and change it to Arial, Size 16, bold by clicking the browse […] button
in the value field
c. Highlight ForeColor and change it to dark grey (Hex: 3F, 3F, 3F) 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.
15. Use either the Menu bar or the Toolbox to select the Numeric Display object
16. Using the Numeric Display tool draw a Numeric Display object where the Total Units indicator
is desired
17. The Numeric Display Properties window will appear, make the following adjustments:
On the Common tab:
a. Change Width to 75 and Height to 25
b. In the Folders pane, drill down to Cookie Demo > FactoryTalk Linx > CookieLine > Online
> Program:Cooling (Click Refresh All Folders button if you don’t see the tag)
d. click OK
f. Click OK
18. While the new Numeric Display is still selected, in the Property Panel at the bottom right,
select Font and set it to Arial, Bold, size 16. Then click on ForeColor and select Blue (Hex: 39,
43, F0) from the color selector.
19. To test your display, click on the Test Display button from the toolbox
20. Tag values should populate on the display 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.
23. . Using the Drawing/Panel tool, create a new Panel on the Overview display
Note: Don’t worry about the size or location of the button object for now. You will modify
this in a later step!
c. Click OK.
c. Click OK.
27. Using the Drawing/Text tool, create a new Text on the Overview display
c. Change the Fore Color to dark grey (Hex: 3F, 3F, 3F) and uncheck Size to Fit
c. Click OK.
29. Using the Drawing/Rectangle tool, create a new Rectangle on the Overview display
General tab
d. Click OK.
31. Use either Menu Bar or the Toolbox to select Numeric and String/String Display
33. The properties window will automatically open. Make the following changes:
e. Click OK
b. Highlight the Font and change it to Arial, Size 12, Bold by clicking the browse […] button
in the value field
c. Highlight ForeColor and change it to dark grey (Hex: 3F, 3F, 3F) by clicking the browse
[…] button in the value field
35. Using the Push Button/Button tool, create a new Button on the Overview display
c. Click OK
The button with a transparent background used here ensures that clicking within the group you
created will take you to the Cooling display
37. Click and hold the mouse, then drag to select created objects
Note: Organizing objects into groups allows for easy management, such as changing their
position on the display, and also enables animating entire groups of objects. You will
learn more about animations in the next task.
38. With the objects still selected, select Arrange/Group from the menu bar
This exercise has demonstrated how to easily add and configure new objects in FactoryTalk View
SE. The objects used today are fundamental components of any SCADA application. In the
upcoming tasks, you will learn more about animating objects, and find information on how to
create Global Objects, which can significantly speed up the process of developing a new
application.
This concludes Exercise E: Create Display Objects
Objectives
In this exercise, you will configure the background of status indicators to change color based on
the state of the related objects.
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
Co.lor
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:
1. Open the Cooling display from the Explorer pane
2. Open the Object Explorer in the bottom right of View Studio, switching away from the
Property Panel.
3. 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).
4. Right-click on Zone2AnimatedPolygon and select Animation -> Color from the menu. The
‘Animation’ configuration window will be displayed
5. In the Expression area, click on the Tag button. In the resulting ‘Tag Browser’ window, select
the following path from the Folders page: CookieDemo > FactoryTalk Linx > CookieLine >
Online. Select the tag: Cooling_Zone2_InZone by selecting the [+] to the left of the tag name
The tag definition will be added to the Expression field as shown below
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 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:
(use the default green color (Hex: 10, EB, 10)
7. 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 changing from white to green every few seconds.
9. When you are finished monitoring, click the Edit Display button
12. Open the Object Explorer (if not already opened) in the bottom right of View Studio, expand
created earlier in this lab Group_CoolingState and reveal the Polygon_CoolingStatus.
13. Right-click on Polygon_CoolingStatus and select Animation -> Color from the menu
14. In the Animation Color tab, click on the Tag button. In the resulting ‘Tag Browser’ window,
select the following path from the Folders page: CookieDemo > FactoryTalk Linx >
CookieLine > Online. Select the tag: tag Cooling_MachineActive by selecting the [+] to the
left of the tag name
15. For this tag, you will again 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, and Fill, settings to the values below:
16. 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 changing from red to green every few seconds.
18. When you are finished monitoring, click the Edit Display button
Object animations are a great way to make your application more accurately reflect the current
state of your machine or process presented on the display. The color change animation
demonstrated in this exercise is just one of the many possibilities offered by the FactoryTalk View
SE environment. In addition to colors, you can also animate fill levels, position, size, or rotation, as
well as create actions related to clicking on or moving the object
Objectives
In this exercise, you will complete the following:
• Create a startup macro to prescribe runtime 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:
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 executed 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, and the /DB parameter means that the display will be docked
at the bottom of the screen. The DisplayNavigationMenu command is used to display
the Navigation Menu that you created before. It will be docked below the Header
display.
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
b. From the Connect to the application dropdown menu, select CookieDemo as the
application to establish connection
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. Try navigating between the Overview, Cooling, and Alarm displays. Use the
predefined navigation display for this, and also try using the navigation button created on the
Overview display.
Note: The Alarm display is currently blank and will be populated by you in a later exercise.
12. To close the client window, right-click on its icon in the taskbar and select the Close Window
option from the menu.
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
b. Set Startup Type to “When firs client connects (Redundancy will be disabled)”
b. click OK.
3. In the Explorer pane, click to expand the newly created CookieDemoAEServer 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. 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.
4. 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
c. set the Message to “Cooling Conveyor Drive has faulted. Check HMI mounted at
cabinet SC-107.”
d. Click on the ellipsis button for the Input Tag field. The ‘Select Tag’ browser window will
appear.
6. Click on the OK button at the bottom of the Digital Alarm Properties window
7. Click Save and Close the Alarm and Event Setup window
9. Using the Alarm and Event/Alarm and Event Summary tool, create a new Alarm and Event
Summary on the Header display
10. On the Alarm and Event Summary properties window, make the following changes:
a. For Alarm Name change the Width to 320 and Align to Left
This setting will ensure that the most recent alarms show up at the top of the banner object.
c. Click OK
13. Using the Alarm and Event/Alarm and Event Banner tool, create a new Alarm and Event
Banner on the Alarms display
14. On the Alarm and Event Banner properties window, make the following changes:
a. Make sure that only Alarm State, Alarm Name and Message are selected in Show
Column
b. For Alarm Name change the Width to 320 and Align to Left
c. Click OK
To simplify process of testing how the Alarms in Factory Talk Studio works, you will use the
preconfigured button already added to Header Display. Using the button you will manually change
the alarm tag state value in the PLC. Button require some small changes
15. In the Header display find button with Alarm icon on it, right-click on and select Properties
a. Click on the ellipsis button for the Value field. The ‘Select Tag’ browser window will
appear.
17. Repeat steps a,b and c for the second parameter: Indicator. Select the same tag as for the
Value
20. 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.
23. Click modified previously “Alarm” button, on the header part of the application. This will set
an alarm condition for the digital alarm that was configured in previous steps. The alarm will
show up in the banner object.
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.
24. Navigate to the Alarms display. If the alarm does not clear within 60 seconds, you can
manually clear the alarm by clicking created earlier button one more time
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.
25. 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.
26. 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 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 logs. 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. Using the Trending/TrendPro tool, create a new Trend Pro on the Cooling display
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 that can be used to customize
the trend appearance. If time permits, feel free to play around with the look and feel of the
TrendPro object.
5. Click on the Add Traces icon (+) at the bottom to select data points or items for trending
6. In the Select Item dialog 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 the Refresh All Folders button.
7. Holding down the Ctrl key, select tags TempSetPtZone and TempZone, and click OK
a. Highlight the first trace in the list, and change the Precision (in the Numeric Tag
section) to 0
8. Highlight the second trace in the list and make the same change: set the Precision to 0
9. While still in the Traces tab, select the first trace again and then select the Y-axis button
c. Click on the 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
10. Now select the second trace in the list and complete the same changes as specified in step 9.
11. 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
c. Change the Margins to: Left 25, Top 18, Right 5, Bottom 15
e. In the Background section, change Window Color to grey (R: 192, G: 192, B: 192) and
Canvas Color to a light grey (R: 224, G: 224, B:224)
c. Click the Choose Line Style… icon and change the X-axis color to black
13. While still in the General tab, select Retrieval, and uncheck the Show retrieval information
on the trend checkbox
Confirm that the trends in Zone 1 and Zone 2 panels now look the same
17. Switch back to the View SE Client that was left open in the last exercise (or open the Client
you created in Exercise F)
Objectives
In this exercise, you will complete the following:
Import and finish the creation of Global Object
Add Global Object instances to the Dashboard display
Scenario
Global objects are one of the key features of FactoryTalk View SE when it comes to creating large
and complex visualization applications. Global objects allow for standardization and increased
efficiency during the application development process. A global object is created and defined in a
single location. Then, in standard visualization displays, copies of this object (instances) are added
and parameterized. Thanks to the continuous connection between the global object and its
instances, it is possible to make changes to the base object and automatically propagate those
changes throughout the entire application. In this exercise, we will do exactly that using a
previously prepared global object.
Practice
1. Right-click on Global Objects and select Add Component into Application…
The Global Object is not ready yet and requires further configuration, which you will complete
in the next steps. The first task is to add a missing Numeric Display by duplicating an existing
one and then making the necessary adjustments.
5. From Object Explorer right-click on the newly created object and select Properties. (Object
will be placed on the top of the list, just below the Display object. It should be called
NumerDisplayGoodParts1)
b. Click OK
IMPORTANT
The expression above uses the parameter (#1). Parameters enable you to customize global
objects, allowing you to easily and quickly adapt an instance of a global object to specific needs
by simply modifying a parameter.
Later in the exercise, you will learn how to assign values to this parameter. For example, in the
expression ::[CookieLine]Program:#1.mTotalParts, if the value "Cooling" is assigned to
parameter #1, the resulting link would be ::[CookieLine]Program:Cooling.mTotalParts, which
correctly points to the variable in the PLC controller
8. To create the Global Object, you need to group the objects. Click and hold the mouse, then
drag to select all the objects on the AreaFaceplate display.
9. With the objects still selected, go to the menu bar and choose Arrange, then select Group or
use the keyboard to type Ctrl + G.
10. Global Object is now created. The next step is to define the parameters. Right-click on the
global object and select Global Object Parameter Definitions
11. In the Global Object Parameter Definitions window add a new parameter definition. In the
first row, enter the following:
Name: “#1”,
Description: “Equipment Name”
13. Right-click on the newly created global object and select Copy
14. Close the AreaFaceplate GlobalObject window. From the Explorer pane open the Dashboard
display
15. Right-click on an empty area of the display and select Paste. A new object will be added to
the Dashboard display. Repeat this step until you have added a total of four objects. Using
the screenshot below as a reference, arrange the newly created objects similarly. Do not
worry about the exact positioning, as this will be addressed later.
16. Now, you need to adjust the positions of the objects on the display. Select the first object you
just added on the left, along with the top object that was originally on the display. Hold down
the Ctrl key and left-click on both objects to select them.
17. While both objects are selected, From the top menu select Arrange/Align Left. You will see
that the newly added object moved left to align with the top one,
18. Select the newly added object on the far right and the top object that was originally on the
display. Left-click on both while holding the Ctrl key.
19. From the Top Menu select Arrange/Align Right. The picture below shows how it should look
now:
20. Now, select all four newly added objects by clicking and holding the left mouse button, then
dragging the cursor over them.
21. From the Top Menu select Arrange/Align Middle and then Arrange/Space Horizontal. The
final effect should look like this:
22. Now, right-click on the first object from the left and select Global Object Parameter Values.
23. In the Global Object Parameter Values window set the value of parameter #1 to “Oven” and
click OK
24. Repeat steps 17 and 18 for the second, third, and fourth newly added objects setting
parameter #1 to “Cooling”, “Loader”, and “Palletizer”, respectively
26. You can now observe that each of the newly added global objects represents a different part
of the process and displays distinct data. Global objects not only enhance efficiency during
application development but also contribute to standardizing the application.
Note: It's important to mention that these copies of the global object are instances. This
means that any changes made to the global object will automatically propagate to all
its instances.
28. From the Explorer pane open the AreaFaceplate global object.
29. Using the Object Explorer find the PanelColorChange object. It will be part of the previously
created Group1. Right-click on it and select Properties.
30. From the General tab change the Back color to white and click OK
31. Save the changes and close the AreaFaceplate global object
32. From the Explorer pane open the Dashboard display again. Note, that all instances of your
global object were updated with your recent color change
33. Launch the FactoryTalk View SE Client created before (if not already launched) and navigate
to the Dashboard display. Check if the created global objects behave as expected
As you have seen, global objects are a powerful tool, and when combined with parameterization,
they become highly flexible. Properly planning your application allows you to maximize the use of
global objects, significantly simplifying the designer's work when making later changes, updates,
or expanding the application.
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
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, uncheck the Footer and Header for Mobile Enable. Select the ClientStartup
macro from the dropdown list, check Publish navigation menu, 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.
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 Compatibility and Download
Center.
The above actions will enable tag writes for all displays in the application.
8. 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.
AThis is the ‘Desktop View’ of ViewPoint in the web browser. The Header, Footer, and
Overview displays are initially shown as a result of the startup macro selected during the
configuration of the FactoryTalk ViewPoint application. You can also see the Navigation
Menu at the top of the screen, which was added using the checkbox during the configuration.
9. Navigate to the Alarms display by clicking on the Alarms button from the navigation bar
10. Toggle the same alarm from Exercise H using the previously modified button in the Header
section of your application.
11. A list of alarms can be filtered by typing in a string in the Quick filter field as shown
12. 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.
14. 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.
15. Near the top, click on Alarms link that is shown next to the displays. You will see any active
alarms here
17. 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.
19. In the top right corner of the browser, click on the menu icon and navigate from More tools to
select Developer tools
20. Use the toggle device toolbar button to enable the device toolbar above the web page image
(if not already visible)
21. 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
22. 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
23. 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
24. 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.
Objectives
In this exercise, you will complete the following:
Add new tags to DataLog Pro
Add new TrendPro Object to present DataLogPro data.
Scenario
DataLogPro allows real-time data logging to an InfluxDB database. The configuration process is
straightforward and does not require the user to have prior knowledge of the database storage
itself. The logged data is then accessible from tools such as TrendPro, which you have already
explored earlier. In this exercise, after configuring DataLogPro, we will duplicate an existing
TrendPro object and modify it on the Overview display.
Practice
1. From the Explorer pane navigate to Data Log catalog, expand it, right-click on DataLogPro,
and click Open
2. The DataLogPro window will open. In the Tag Browser (on the right side of the window)
navigate to: FactoryTalkLinx > CookieLine > Online > Program:Cooling > mCoolUDT >
mCoolUDT[1]. Use the [+] sign to add TempZone and TempSetPtZone tags to DataLogModel:
3. You will see both tags added to the list on the main part of the window. We will keep the
default settings. Close the window and Save the changes.
That’s it! Your data is now being logged into the InfluxDB database. Now let’s create an interface to
see your data.
4. Open the Cooling display and Copy the TrendPro object created in one of the previous
exercises
5. Close the Cooling display and open the Overview display. Right-click on an empty area of the
display and select Paste. A new Trend Pro object will be added to the Overview display.
Repeat this step to add a second Trend Pro Object
Note: You will add two Trend Pro objects to make comparing both data presentation
methods easier. The first chart will display data identical to the Cooling display—live
data only, while the second Trend Pro object will present data archived using
DataLog Pro.
6. Ensure that you now have two TrendPro objects on the Overview display. You can verify this
visually or by checking in the Object Explorer. You should see two TrendPro objects listed just
below the main Display object at the top of the list.
7. Right-click on the first newly added Trend Pro object and select Properties (You can select
the object directly on the display, or from the Object Explorer)
8. In the Common tab change the Top to: 20 and Left to: 590, and then click OK
9. Now select the second Trend Pro object, go to Properties, and in the Common tab change
the Top to: 20 and Left to: 935, and then click OK.
This is how your two trends objects should now be placed on the Overview display
10. Using the Drawing/Panel tool, create a new Panel on the Overview display
Note: Don’t worry about the size or location of the panel object for now. You will modify
this in a later step!
11. On the Panel properties window which will appear after creating the object, make the
following changes:
a. In the General tab change the Border Style to RaisedInset and the Border width to 7
b. In the Common tab change Width to 700, Height to 300, Top to 5, Left to 570, and click
OK.
12. The newly created Panel will hover over the previously pasted Trend Pro objects. Right-click
on the Panel, and select Arrange/Sent to back
The Panel will be now placed below the two Trend Pro objects
13. Now right-click on the right TrendPro object and select Properties. From the general tab
click Trend Setup
14. While in the Traces tab, select the first trace (if it’s not already selected by default) and click
on the ellipsis button next to the Tag field. The Select Item window will appear.
15. In the Select Item window expand the DataLogPro, and select Ungrouped tags. From the
item list below select the first tag:
::CookieLine]Program:Cooling.mCoolUDT[1].TempSetPtZone and click Ok
16. Now select the second trace and repeat steps 14 and 15. In the Select Item window, this time
select the second tag from the list:
::[CookieLine]Program:Cooling.mCoolUDT[1].TempZone
17. Click Close to close the Properties window and then OK to close the TrendPro properties
window.
Note: DataLogPro began logging data immediately after you completed the configuration.
As a result, when you start the display in test mode, you should already see that the
traces cover the entire period (5 minutes) defined in the TrendPro object
19. If you wish, you can also check the functionality using the FactoryTalkView SE Client created
earlier. The TrendPro objects should behave the same as when tested using the Test Display
functionality.
Note: You should notice that both charts are not identical. The TempZone signal on the
right chart appears to be shifted compared to the same signal presented on the left
chart. What do you think is the cause of this? You will find the answer to this
question on the next page.
Note: Answer: The signal shift is due to the data logging settings in DataLog Pro. The data
presented on the left chart, which is live data, is sampled with the default frequency
settings of the display. In contrast, the data on the right chart is sampled at the
default frequency set in DataLog Pro, which is 10 seconds. The difference in
sampling rates, along with the characteristics of this signal, causes the signal to be
displayed differently depending on the chart. This is why it is crucial to properly
configure data logging parameters when using DataLog Pro. You can learn more
about this in our second lab: "What's New in FactoryTalk View SE V15.
Objectives
In this exercise, you will complete the following:
Create a new User
Configure security by editing the Security Codes
Modify a label to display the current user's name
Modify the login button
Create security access rights for the display
Scenario
Security settings are one of the fundamental functionalities of any SCADA system. In this exercise,
you will go through the process step by step, from creating a user to assigning the appropriate
permissions for displays. This solution allows you to manage access to displays or various
functions of your system, ensuring that only authorized individuals have access. In this exercise,
you will create a user in FactoryTalk View SE, but remember that you can also add your local or
domain users and groups to the Factory Talk View SE Application.
Practice
Creating a new user
c. click OK
6. Select the newly created user in the Select User or Group window and click OK
Setting Up Permissions
b. In the Permission for All Users field expend the Factory Talk View Security Codes and
uncheck the Code A
[Optional] Select newly created user Student and make sure that the Code A is checked
c. Click OK
Action tab
b. Click OK
12. Right-click on the String Display object located just below the Factory Talk View SE Logo and
go to Properties
Common tab
b. Click OK
14. Click Test Display to check if the newly added component works as expected. You should see
that the Currently logged user is the Windows user ONCOURSEWINSVR2\LABUSER
17. Right-click on an empty area of the display and select Display Settings
18. In the Settings window, change the Security Code to Code A, and click OK to accept the
changes
20. Start the FactoryTalk View SE Client. If the client is already open, close it and then reopen it
21. When the client starts, try to navigate to the Dashboard display. You will notice that the
display is not opening.
22. Click the Login button from the Header part of the application and log in using the newly
created user
Username: Student
Password: rockwell
Note: The currently logged-in user information in the Header section of the display
should update to show Student as the logged-in user.
23. Navigate one more time to the Dashboard display. This time display will open.
Objectives
In this exercise, you will complete the following:
Add a second language to your application
Add translation for the second language
Modify the predefined button to be able to change the language
Scenario
The option to change the language is often a required functionality for end users. Having multiple
language versions of the same application allows operators to easily operate the machine in their
native language, as well as aids in machine maintenance and communication with the service
team. In this exercise, you will learn how to add a new language to your application and upload
additional translations. You will also modify a button that will allow for changing the application’s
language. In this exercise, we will focus on changing the language for the navigation menu
Practice
1. In the first step, you will add a new language. In this exercise, we have chosen Polish as the
language, as the author of this manual is from that country. Go to the menu bar and select
Tools and then Languages…
2. English Language (en-US) is already added (this language was chosen when you were creating
a new application). In the Language Configuration window check Display undefined strings
using the default language and then click Add to add a new language
3. In the Add Language window select Polish (Poland) pl-PL and click Ok
4. In the Language Configuration window, confirm adding new language by clicking the Apply
button
5. Adding a new language does not automatically translate the application's text strings. There
are two approaches to handle the translation. You can either switch the application language
in Studio to the new one and manually translate all the strings, or you can export the existing
language strings to a text or Excel file and perform the translations there. To save you time,
we've already prepared a translated language file for you, which now just needs to be
imported. In the Language Configuration window select the Polish language and then click
Import
6. The String Import Export Wizard will appear. In the Import Operation section click Next
10. You will see that the string import is in progress, and after a few seconds, it should be
completed. Based on what you did during the lab, an Export Log text file may appear,
informing you that not everything was imported into the application. Don’t worry about that
and close the log file. You can also close the Language Configuration window by clicking OK
a. Type “If CurrentLanguage() = "en-US" Then Language pl-PL Else Language en-US
Endif” in Release action field
b. Click OK
15. Start the FactoryTalk View SE Client. If the client is already open, close it and then reopen it
16. When the client will start, click on the Language Switch button, which you modified before,
and note how text strings on the Navigation menu change
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.