Professional Documents
Culture Documents
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 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.
Page 2 of 132
Lab VZ01 - FactoryTalk Machine Edition and
PanelView Plus Introductory Lab
Contents
Before you begin ........................................................................................................................................... 5
About this lab .................................................................................................................................................................................... 5
Tools & prerequisites ........................................................................................................................................................................ 5
Document conventions ..................................................................................................................................................................... 7
FactoryTalk View Machine Edition ................................................................................................................................................. 7
PanelView Plus 6 .......................................................................................................................................................................... 8
Using Global Objects to Make Application Design Convenient and Quick ................................................. 82
Cross Reference and Search & Replace ........................................................................................................................................ 95
Global Object and Parameters Test Application ............................................................................................................................. 98
Page 3 of 132
Language Switching .................................................................................................................................. 101
Page 4 of 132
Before you begin
Page 5 of 132
Ethernet connection between computer and PanelView Plus terminal
FactoryTalk View Machine Edition Studio V7.00.00 (CPR9 SR6)
FactoryTalk Services Platform 2.60.00 (CPR9 SR6)
RSLinx Enterprise V5.60.00 (CPR9 SR6)
RSLinx Classic V3.60.00 (CPR9 SR6)
Studio 5000 Logix Designer V21 (CPR9 SR5.1)
SoftLogix 5800 v21 (CPR 9 SR5.1)
Microsoft Excel 2010
Page 6 of 132
Document conventions
Throughout this workbook, we have used the following conventions to help guide you through the lab materials.
Words shown in bold italics Any item or button that you must select, click on, or a menu name from
(e.g., RSLogix 5000 or OK) which you must choose an option or command. This will be an actual
name of an item that you see on your screen or in an example.
Words shown in bold This is the name of an item that you see on your screen or in an
(e.g., Communication Setup) example.
Words shown underlined and enclosed in An entry that you must type in the specified field. This is information that
single quotes you must supply based on your application (e.g., a variable).
(e.g., Controller1') Note: When you type the text in the field, remember that you do not
need to type the quotes; simply type the words that are contained within
them (e.g., Controller1).
Note: If the mouse button is not specified in the text, you should click on the left mouse button.
Page 7 of 132
PanelView Plus 6
The PanelView Plus are operator interface terminals designed to optimize system development, performance, and efficiency.
The PanelView Plus 6 line is the latest addition to Rockwell Automations versatile family of Allen-Bradley PanelView
operator interface displays for machine level operator terminal applications in industrial environments.
Enhancements to the hardware platform, embedded operating system and development environment enable users to:
Take time and costs out of application development - PanelView Plus 6 dramatically reduces development, setup time
and troubleshooting time through features like tag re-use, complete Symbol Factory graphic library and pre-built face
plates.
Run their processes more effectively - Improved hardware performance delivers up to 30% faster screen response,
enabling operators to navigate through screens more quickly, and can help avoid maintenance calls resulting from
mistakenly pressing inputs multiple times. In addition, new capabilities wring more value from your process.
Reduce maintenance costs - New features like on-board pdf capability and remote user access enable context-sensitive
help and can avoid on-site visits to get processes back up and running faster when things go wrong.
Page 8 of 132
Creating a Hello World Application
1. Using the Start menu select All Programs>Rockwell Software>FactoryTalk View> FactoryTalk View Studio
item
Page 9 of 132
After the FactoryTalk View Studio for Machine Edition application opens, you will see a screen similar to the screenshot shown
below:
Page 10 of 132
5. Next, click the Create button .
After creating the application, the FactoryTalk View Studio for Machine Edition opens the application:
If you are unfamiliar with FactoryTalk View Studio for Machine Edition, please review the information in the next few pages.
Page 11 of 132
Exploring FactoryTalk View Studio for Machine Edition Interface
The FactoryTalk View Studio for Machine Edition Application Windows is divided in to several key elements
Page 12 of 132
contains computer-scoped components,
FactoryTalk View Data Server and FactoryTalk Services
Platform objects.
Page 13 of 132
By default, new projects in FactoryTalk View Studio for Machine Edition are configured for a PanelView Plus 700 terminal with a
640x480 resolution. In this lab, you are using a PanelView Plus 1250; this terminal has a larger display and resolution, so you
next need to change the project window size to match for your project.
6. Maximize FactoryTalk View Studio by clicking the maximize button in the upper right-hand corner.
7. Double-click the Project Settings item located in the top System container to open its dialog.
8. Select the PVPlus 1250 (800x600) item from the Project window size setting using the dropdown list
.
10. Click the OK button to proceed. There is no need to change any setting on this dialog.
Page 14 of 132
While changing the projects display size a progress dialog is shown.
Upon creation of a new project, FactoryTalk View ME 7.0 will automatically create a default display called MAIN which is also
defined as the initial startup display. We will use this display for the following steps in our lab. If you require more displays, you
can always add a new display to the project you are working on. We will see an example of this in the section on Global Objects.
11. To open existing displays, open the Displays container by clicking the expander from the Explorer Pane
window.
Common Configure the objects size (Height and Width) and display position. Display top-left
corner is {0,0} coordinate.
In addition, most objects that display static text (e.g. Text, Shutdown button) have a Label tab.
1. Select the Text tool , and add a text box to the display.
When you release the mouse button, the Text Properties dialog will immediately open.
Page 15 of 132
2. Click the Text field and enter Hello World! This is my Intro application.
Page 16 of 132
4. Close the display using the File > Close menu item.
When prompted to save MAIN click the YES button.
Now that you have created objects on the Main display, verify that it is configured as the applications Startup graphic.
5. To open the Startup dialog, double-click on the Startup item in the System container.
Page 17 of 132
2. Save the runtime project using the suggested name Intro.mer by clicking the Save button .
After creating the runtime MER file, the FactoryTalk View Studio for Machine Edition displays the open application.
Page 18 of 132
Downloading a runtime MER to a PanelView Plus terminal
1. To download the runtime MER to the PanelView Plus 1250 terminal at your workstation, first select the Tools>
Transfer Utility menu item:
Page 19 of 132
2. Click the Source File Browse button to select the runtime MER file to download.
Page 20 of 132
3. Click on the Intro.mer file to select the project. The File Name box should update to reflect the selection.
6. Select the 192.168.1.20, PanelView Plus_6 1250, PanelView Plus_6 1250 item by clicking on it once. The
screen that you will see may look slightly different from the example shown below:
Page 21 of 132
Running an Application on a PanelView Plus Terminal
In this lab section, you will work with a PanelView Plus terminal. Execute the following steps to run the FactoryTalk Machine
Edition application you just completed.
1. Tap on the PanelView Plus screen on your lab station if the screensaver is active.
You will now see the PanelView Plus 6.0 desktop.
2. Locate the FTView ME Station icon on the desktop and double-tap it to launch FTView ME Station.
4. Select the Intro.MER file from those available from the terminals Internal Storage.
6. When prompted, press Yes [F7] to overwrite the terminals current communication configuration with the
configuration contained within the Intro.MER file.
7. Once successfully loaded, press the Run Application [F2] to start executing the runtime file.
Page 22 of 132
After the start-up processing completes, you should see your applications startup display:
Page 23 of 132
Animating a Display with Control System Data
Configuring Communications
1. Return to the hmi project in FatoryTalk View Studio and double-click the RSLinx Enterprise item to expand it.
2. Right-click on the Communication Setup item and select Open to launch the RSLinx Enterprise
Configuration Wizard.
Communication Configuration
Create a new configuration
Generates an empty communication
configuration scheme for the application.
Copy an existing configuration from a
previously created projects
Reuse a communication configuration
from a different application file.
Copy the configuration that is currently
running on this workstation
Infrequently used; copies the
communication configuration from an
application currently being hosted using
FactoryTalk Machine Edition Station on
the same workstation
Page 24 of 132
4. Click the Finish button . The Communication Setup dialog opens.
You can resize the dialog by using the size handles, or click the maximize button
Page 25 of 132
Exploring the Communication Setup Dialog
The Communication Setup dialog has three main areas.
Network Path
Displays the
network topology
Device Shortcuts path to the device
A list of shortcuts associated with the
defined on the selected shortcut.
workstation in RSLinx Also used to create
Enterprise. a new shortcut to
the select network
device.
You will notice that the Network Path dialog area has two tabs, Design (Local), and Runtime (Target). The definitions below should help you
to understand how to use these tabs, and why there provide powerful flexibility when designing an application. These tabs allow you to
develop and debug an application while at your desk, working on the shop floor, or some other location that is not co-located with the control
system.
The tabs can be used as described below
Design (Local) Configure the network and device path(s) for the development environment in
which the application will be designed and debugged. This network topology
and device path(s) may be different than the production environment where the
application will ultimately run.
If the development and production environments are identical, you can copy
the Design (Local) configuration to the Runtime (Target) configuration using
the Copy from Design to Runtime button .
Runtime (Target) Configure the network and device path(s) for the production environment in
which the application will run (e.g. customer facility). The network topology
and path(s) may be completely different than those defined using the Design
(Local) tab.
Page 26 of 132
5. To create a new shortcut, click the Add button in the Device Shortcuts area.
6. Name the shortcut Intro by typing Intro and then pressing the [Enter] key on the keyboard.
If you have successfully completed these steps, the Communication Setup dialog will look like this:
Page 27 of 132
7. Expand the EtherNet, Ethernet driver by clicking the expander once.
8. Click the expander once to open the 192.168.1.1, SoftLogix 5800 EtherNet/IP, SoftLogix 5800
EtherNet/IP item.
9. Click the expander to open the 1789-A17/A, 1789-A17/A Virtual Chassis item.
10. Select 2, 1789-L60/A, BlockMachine by clicking on it once. The dialog should now look like this:
11. Click the Apply button in the Device Shortcuts pane to associate the selected device (e.g. SoftLogix 5800
Controller) with the selected communication shortcut (e.g. Intro).
Page 28 of 132
13. Click the Verify button to confirm the association.
14. Close the Shortcut Verifier dialog by clicking the Close button .
In this lab, the design and production environments are identical. To proceed you have two options:
A. Use the Copy from Design to Runtime button to copy the design environment
topology and device paths to the production environment (e.g. Runtime (Target) tab).
It is estimated this option will require less than 5 minutes to complete.
B. Manually configure the production environment so that you understand how this functionality works. It is estimated
manual configuration will require 5 to 10 minutes to complete.
Page 29 of 132
Option A
a) Click the Copy from Design to Runtime button to copy the communication
configuration from the Design (Local) tab to the Runtime (Target) tab.
Page 30 of 132
Option B
b) Right-click on EtherNet, Ethernet item to open the context menu, and select Add Device.
c) Click Add Device which opens the Add Device Selection dialog.
g) Click the OK button to accept the selection. This action opens the Device Properties dialog.
Page 31 of 132
h) Enter 192.168.1.1 in the Address field to set the devices TCP/IP address.
k) Click the OK button to add the device to the Runtime (Target) configuration.
l) Use the expander to open the 192.168.1.1, SoftLogix5800 EtherNet/IP, SoftLogix 5800 EtherNet/IP device.
m) Right-click the 1789-A17, 1789-A17 Virtual Chassis item and select Add Device.
Page 32 of 132
n) Expand the 1789-L60/A, 1789-L60/A SoftLogix 5860 Controller item by clicking.
Page 33 of 132
p) Click the OK button to accept the selection.
r) Click the OK button to add the device to the Runtime (Target) configuration.
t) Click the Yes button to apply the changes to the Intro shortcut.
Page 34 of 132
15. Click the Verify button to confirm the Design and Runtime associations.
Confirm both the Design and Runtime devices are assigned for shortcut Intro.
16. Close the Shortcut Verifier dialog by clicking the Close button .
17. Click the OK button to complete the communication setup and close the Communication Setup dialog.
Be sure to use the OK button! If you close the dialog with the Close button, the communication setup will not
be saved to the application.
Page 35 of 132
1. Double-click the MAIN display in the Explorer to open the display.
2. Select the Maintained Pushbutton tool from the Objects toolbar or select Objects->Push Button-
>Maintained.
3. When you move the cursor over the MAIN display frame, the mouse cursor will change to
4. Move the mouse cursor in the middle of the MAIN display frame; click and hold the left mouse button, and then
drag down and to the right to create a Maintained Pushbutton object.
6. Change the Height and Width fields to size the Maintained Pushbutton exactly.
Height 120
Width 150
Page 36 of 132
7. Click the Apply button to commit these changes. The button should move and resize on the display
to match these settings. If you accidently clicked OK button, simply reopen the buttons property dialog by
double-clicking the button.
Page 37 of 132
Adding Images from Symbol Factory
FactoryTalk Studio for Machine Edition v6.0 includes Software Toolboxs Symbol Factory library. This library
contains over 5,000 images. Most of these images are vector graphics and can be used as you might any other
image on a FactoryTalk Machine Edition display. The vector graphics can be animated using FactoryTalk Studio
for Machine Edition standard animation options (e.g. Fill, Color, Visibility). Approx. 1,000 images are bitmaps
that you can use with buttons, multi-state indicators, etc. to create more visually appealing applications.
The Symbol Factory Viewer looks like this. There are three main areas to the viewer.
Preview
A larger view of the
selected image.
Categories
Collections of related
images
Symbols
Displays the images
available within the
selected Category.
Page 38 of 132
14. Click the Launch Library button to bring up the Symbol Factory library.
Page 39 of 132
16. Select the Illuminated rectangular pushbutton (Green Up Off) button image.
17. Click Copy to copy the image to the project image library.
18. Click Paste from Library to add the image to the project library.
Page 40 of 132
19. Leave the default name and click OK.
21. The State0 button properties should now look like this.
Page 41 of 132
22. Select State1 in the Select State: field.
Page 42 of 132
27. Click the Image browser button
28. Click the Launch Library button to bring up the Symbol Factory library.
Page 43 of 132
30. Select the Illuminated rectangular pushbutton (Green Down On) button image.
31. Click Copy to copy the image to the project image library.
32. Click Paste from Library to add the image to the project library.
Page 44 of 132
33. Leave the default name and click OK.
35. The State1 button properties should now look like this.
Page 45 of 132
36. Click the Apply button to commit these changes.
39. In the Value row, click on the Browse button in the Tag column
The Tag Browser is used to view and select tags from the applications configured data sources. When you configured
RSLinx Enterprise earlier in this lab, you were configuring a data source. Other data sources might be a PLC5 or SLC500
processor, or a device accessed using available KEPware drivers.
Tag Area
Used to select a specific
tag from the selected
Folder List folder
Used to browse a
shortcuts Controller
and Program tags
and UDTs Tag Filter
Shows only those tags that start with
the user-entered filter. Press [Enter] to
apply a filter to the Tag Area.
Page 46 of 132
The following further defines and highlights the uses and functionality provided in the Tag Browser.
Folder List
HMI Server (e.g. )
Contains tags defined in the HMI Server,
referred to as memory tags. The
FactoryTalk Machine Edition runtime
manages and updates these tags.
System
Contains default HMI tags for system
information, such as, time of day, date,
etc.
<Communication Shortcut> (e.g. VZ01)
Contains tags that exist in the memory of
the device the shortcut represents.
Diagnostic Items
Predefined diagnostic and troubleshooting
tags useful for monitoring communication
and controller status.
Online
Tags contained in a Logix Controllers
memory; the tags are directly referenced
by the FactoryTalk Machine Edition
runtime.
Tag Area
Name
Column containing the tags name. Use
the Tag filter function to quickly find tags
that start with the user-entered filter.
Access Rights
New! In V18 firmware, Logix Controllers
implements Access Rights for tags. This
column displays a tags Access Rights
property. Tags are either ReadOnly or
ReadWrite.
40. Right-click on the Intro item in the Folders list; select the Refresh All Folders item.
Page 47 of 132
41. Double-click the Intro folder to expand.
Double-click here in
step 42.
42. Double-click the Online item to expand.
Page 48 of 132
44. In the Tag Area, locate and select the tag Pelleter_Running.
Note that the Selected Tag text box reflects your selection.
Page 49 of 132
45. Click the OK button
to complete the
connection configuration.
47. Select the Numeric Display tool from the Objects toolbar or select Objects-> Numeric and String ->
Numeric Display
48. Move the mouse above the maintained pushbutton; click and hold the left mouse button, then drag down and to
the right to create a Numeric Display box.
Page 50 of 132
49. Change the following Numeric Display
Properties.
Text Bold
51. Change the Height and Width fields to size the Numeric Display exactly.
Height 50
Width 100
53. In the Value row, click the Browse button in the Tag column to open the Tag Browser.
Page 51 of 132
54. In the Folder List, expand the path Intro> Online> Program:Extruder_Control .
Page 52 of 132
58. Save the MAIN display using the File> Save menu item.
59. Close the MAIN display using the File> Close menu item
Page 53 of 132
Testing an Application on the Desktop
There are two methods available to test an entire application. One is to download the application to a PanelView Plus terminal.
The other is to use the terminal emulation capability that is included with FactoryTalk Studio for Machine Edition. You will be
testing the application on the desktop using the terminal emulation functionality.
When the runtime MER file is built, the system loads the runtime MER in to an emulation mode. The application will appear in
the upper left-hand corner of the computer display.
2. To evaluate the application click on the Start Pelleter button, . The button color and caption
change.
The color is now an illuminated green and the caption reads Stop Pelleter. The numeric display is showing a value other than 0.
Page 54 of 132
3. Click the Stop Pelleter button to end the simulated process.
Page 55 of 132
Adding Alarms to an Application
Use the default Alarm display to announce and exercise the alarming function.
When you have completed this section the application will appear as it did at the end of the last section. However, as the
application executes, simulated alarms will occur.
Page 56 of 132
A display has already been created that you will use to generate several alarms. First, lets add additional images to the HMI
projects Image library. These images are used by the displays that will be added to the project. Then well add the Alarm
Generator display to the project.
1. In the Explorer pane, under Graphics, right click on Images and select Add Component Into Application
3. Select all the images by pressing the CTRL & A keys and then click Open.
Page 57 of 132
4. Right click on Displays and select Add Component Into Application.
Next, lets create some HMI tags that we will use to generate some alarms. Normally, you will use tags from your controller but
for demonstration purposes we will use HMI tags.
Page 58 of 132
7. Right click on Tags and select Open to open the HMI tag database.
9. Click Next and enter the following to create tag Alarm_Analog2. Click Accept.
Page 59 of 132
10. Click Next and enter the following to create tag Alarm_Digital1. Click Accept.
11. Click Next and enter the following to create tag Trip_Point. Click Accept. Note the Initial Value of 65.
Page 60 of 132
Configuring Alarms
Triggers tab
Used to define and manage the events
that will trigger an alarm to occur.
The control system designer can also
configure the system for alarm
coordination with the control system.
Messages tab
For each defined alarm event, the
system designer can configure the
message that corresponds with the
alarm.
Advanced tab
Allows the configuration of the system
display on which to show alarms, the
alarm history, and additional remote
connections for control system
coordination.
Page 61 of 132
Next, we will configure the alarms.
15. Click the Exprn button to open the Expression editor. We will create a short expression for the first trigger.
Page 62 of 132
17. Click on the Intro HMI Server. Select Alarm_Analog1. Click OK.
Page 63 of 132
19. Type 200 after the > symbol and click OK.
20. Click OK again to assign the expression to the Alarm Triggers list. Leave the default Trigger type as Value.
22. Click the Exprn button to launch the expression editor again.
23. Copy and Paste the following expression into the expression editor.
24. Click OK twice to assign the expression to the Alarm Triggers list. Leave the default Trigger type as Value.
Page 64 of 132
27. Click on the Intro HIM Server. Select Alarm_Digital1. Click OK.
28. Click OK again to assign the tag to the Alarm Triggers. Leave the default Trigger type as Value.
The Alarm Triggers list should look like the following:
Page 65 of 132
29. Click the Messages tab to assign trigger values and messages to the alarm triggers you just created.
30. Assign the Alarm_Analog1 trigger by selecting it from the list using the Trigger drop down menu.
32. Type Tank Level > High Alarm in the Message field.
Page 66 of 132
33. Leave the rest of the settings at the default.
34. Assign the Alarm_Analog2 trigger by selecting it from the list using the Trigger drop down menu
Page 67 of 132
37. Leave the rest of the settings at the default.
38. Assign the Alarm_Digital1 trigger by selecting it from the list using the Trigger drop down menu.
Page 68 of 132
41. Leave the rest of the settings at the default.
42. Click the Advanced tab. Here one can specify which display will show the alarms. We will use the default,
[Alarm] display.
Page 69 of 132
46. Select the Alarm Generator button and copy it.
47. Minimize the Preconfigured_Buttons display and paste the button onto the MAIN display.
The Preconfigured_Buttons display contains several buttons that have already been configured for you. The buttons, when
they are pasted into other displays, will paste to the same location as they appear on the Preconfigured_Buttons display since
their size and location properties are retained.
Your MAIN display should now appear as shown
The button is a Goto Display Button that is configured to open the ALARM_GENERATOR display and has a bitmap image
(Icon-Alarm) assigned to it instead of a label.
Page 70 of 132
48. Close the MAIN display and save the changes when prompted.
Page 71 of 132
Alarm Test Application
1. Test the application on the Desktop by selecting the Running Man icon in the toolbar.
When the application opens you will see the MAIN screen.
2. Click the Alarm Generator button to bring up the Alarm Generator display.
Page 72 of 132
Lets simulate our first alarm. This example uses a digital alarm trigger, so a value of 1 will cause the alarm to trigger. A
maintained pushbutton is used to simulate the alarm.
3. Click the Red pushbutton to simulate a digital alarm. Notice, after a few seconds, that the Alarm Banner pops
up.
4. Click the button to close the Alarm Banner and click the Red pushbutton to reset the alarm.
Lets simulate another alarm. This example uses an expression for the alarm trigger. When the tag we are evaluating reaches a
value greater than 200, the expression is true or a 1. So, a value of 1 will cause the alarm to trigger. Ramp pushbuttons are
used to simulate the alarm.
5. Click the UP arrow repeatedly until a value greater than 200 is displayed each press of the Ramp button
increments the value by 25.
Notice, that once a value greater than 200 is reached, the Alarm Banner pops up again.
6. Click the button to close the Alarm Banner and click the Down arrow repeatedly until a value below 200
is reached.
Page 73 of 132
Now, lets simulate our last alarm trigger. This example also uses an expression. This time we are forcing the result of the
expression to be 65 when the tag we are evaluating reaches a value greater than 65. So, a value of 65 will cause the alarm to
trigger.
6. Click your mouse onto the slider and leave it clicked while you move the slider up past the Alarm Trip Point -
indicates a value of 65.
Notice, that once a value greater than 65 is reached, the Alarm Banner pops up again.
7. Click the button to close the Alarm Banner and move the slider down past the Alarm Trip Point.
Page 74 of 132
Alarm History Display
We just saw how the popup display, Alarm Banner, can alert you when alarms occur. What if you want to maintain a history of
alarms and display them? Well, we can do this by using an Alarm List object. FactoryTalk View Machine Edition Studio already
has a finished Alarm History graphic display that one can add to their HMI project. It can be found under the Libraries container
in the Project Explorer pane. However, well create a new display and place an Alarm List object on it.
2. Select , , , and .
3. Using your mouses left click button, draw a rectangle on the new display, starting in the upper left corner and
going about three-quarters of the way down. The Alarm List Properties configuration dialog pops up.
5. Uncheck Display column for the following items by selecting each one and then clicking the Display column
box: Acknowledged symbol, Active symbol, and Acknowledge time. We only want to display Alarm time
and Message on the Alarm List.
Page 75 of 132
6. Click OK to apply the changes.
8. Enter Alarm History for the display name and click OK.
Page 76 of 132
Next, well add some buttons to the display.
7. Select , , , and .
8. Using your mouses left click button, draw a rectangle in the lower left corner of the display. The Clear Alarm
History Button Properties configuration dialog pops up.
10. Enter the caption shown below and click OK. The button should look similar to what is shown.
12. Using your mouses left click button, draw a small square next to the Clear History button. The Move Up
Button Properties configuration dialog pops up.
13. On the General tab, select to send the key press to Linked Object.
14. Click the browser button for Linked object to bring up a list of objects to assign the button to.
Page 77 of 132
16. Click OK again to apply the changes to the Move Up button.
17. Perform steps 11-16 to add a Move Down button to the display.
18. Right click on the Preconfigured Buttons display and select Open.
20. Minimize the Preconfigured Buttons display and paste the button onto the Alarm History display. The button
will paste to the desired location.
Your display should look similar to what is shown.
21. When finished, close the Alarm History display and save your changes when prompted.
Next, well add a Goto Display button onto the MAIN display.
Page 78 of 132
22. Right click on the MAIN display and select Open.
23. Maximize the Preconfigured Buttons display and copy the Alarm History button.
24. Close the Preconfigured Buttons display and paste the Alarm History button onto the MAIN display. The
button will paste to the desired location.
The MAIN display should now look similar to what is shown.
Page 79 of 132
The Goto Display button we just added is assigned to the Alarm History display.
25. Close the MAIN display and save the changes when prompted.
Page 80 of 132
Alarm History Test Application
1. Test the application on the Desktop by selecting the Running Man icon in the toolbar.
2. Generate some alarms and then navigate to the Alarm History screen by clicking the Alarm History Goto Display
button, . Refer to page 72 for instructions on testing the application and how to generate the alarms.
Notice how the alarms appear in the list. You may have to close the Alarm Generator display in order to view the Alarm
History display. Associated with the alarms, is an alarm log the alarm history. This log can store up to 10,000 alarms. The
alarm history size is defined in Alarm Setup under the Advanced tab. The default log size is 128.
Finally, pressing the Clear History button will clear all alarms stored in the alarm log file.
3. Shut down the test application by pressing the letter X on your keyboard.
Congratulations!!
You have successfully created a FactoryTalk View Studio for Machine Edition application that uses alarms, created a runtime
file, and, exercised the application on your desktop.
Page 81 of 132
Using Global Objects to Make Application Design Convenient and Quick
FactoryTalk View global objects allow you to link the appearance and behavior of a graphic object to multiple copies of that
object. When you update the original object, changes are automatically applied to all the copies of the object used in the
application. The original object that was created is called the base object. The base objects can be copied over to other displays
and reused. These objects that were copied over are called reference objects. You can do the following with Global Objects:
82 of 132
Creating Base Global Objects
We will use an already developed base object to demonstrate the capability of Global Objects. We will define the parameters for
the base object. Then, we will copy the base object onto another display and further define the parameters for each reference
object. Finally, we will change a property of the base object and see how the other reference objects are affected.
1. Right-click the Global Objects folder in the Project Explorer and select Add Component Into Application.
4. Open the Screen Objects display that you just added under Global Ojects.
83 of 132
A global object has already been created. This global object is a group consisting of several individual components. We will
want to assign some parameters to the global object. The #1, #2, etc. are known as parameters. The parameter can represent
any part of a tag or the entire tag. This allows us to reuse the global object in multiple places. Also, if we want to change an
attribute for the global object, we would just change the attribute of the base object on the Global Object display and the change
will propagate to all the instances of that global object known as reference objects. You can break the link back to the base
object, if desired. Then the reference object becomes an ordinary object with independent attributes.
Lets assign some parameters to the base object.
5. Right click on the global object and select Global Object Parameter Definitions.
84 of 132
6. Enter #1 and Silo Number as shown below and click OK.
We will only use 1 parameter in this lab. Next, well see how this parameter can be used.
7. Click View in the toolbar and then select Object Explorer. This will provide an easy way to select the individual
components that make up the entire global object.
85 of 132
8. Expand Group7 and then Group 13 by clicking the +.
Notice the #1 in the tag. This is the parameter we assigned to the global object and represents the actual Silo number. The tag
will provide the fill animation for the polygon for that specific Silo. There are 2 polygons, one for the Lower Hopper Level and one
for the Upper Hopper Level. The same fill animation is applied to the Upper Hopper Level.
86 of 132
10. Close the Animation configuration dialog.
12. Click the Connections tab. Notice that #1 is used in place of the actual Silo number. The numeric display will
show the actual value of the Lower Hopper Level. There is another numeric display for the Upper Hopper Level.
15. Click the Connections tab and then click the Expression browser button.
87 of 132
Notice the #1 being used in place of the Silo number. This expression sets the state value of the multistate indicator. There are
3 states to indicate the present state of the Silo Filling, Filled, and Emptying.
16. Close the Expression Editor and the Multistate Indicator Properties configuration dialog.
Notice the #1 in the Literal String Embedded Variable. This again represents the actual Silo number.
18. Close the Text Properties configuration dialog and the Object Explorer.
19. Close the Screen Objects display and save the changes when prompted.
88 of 132
Weve explored how to assign parameters to the global object and how we used the parameter #1 for our specific global object.
Now, lets use the global object in our application. First, well add a display that has been already created to our project.
20. Right click on Displays and select Add Component Into Application.
22. Select the Vacuum Silo Group.gfx and Vacuum Silo.gfx files and click Open.
23. Open the Screen Objects Global Display and copy the Silo global object.
89 of 132
24. Open the Vacuum Silo Group display and paste the Silo global object into the lower left corner of the display.
Once its pasted onto the display, click and drag the object to the desired location.
25. Paste 3 more instances of the Silo global object onto the Vacuum Silo Group display, place each one next to
the previous one. Your display should look similar to the following.
Now lets assign the actual value for the parameter, #1.
26. Right click on the first global object that you pasted and select Global Object Parameter Values.
90 of 132
27. Enter a 1 for the Value property and click OK. Remember that this parameter corresponds to the Silo number.
In our application, we have a total of 4 Silos.
28. Repeat steps 26 & 27 for the remaining global objects entering 2, 3, and 4 respectively.
Lets examine another use of parameters. Well look at how a parameter can be passed to another display.
91 of 132
This single display is reused to present data for each of the 4 Silos. The #1 parameter is used on this display to represent the
actual Silo number. But the value for the parameter is provided via a parameter list.
30. Click View in the toolbar and then select Object Explorer.
92 of 132
31. Using Object Explorer, open MultistateIndicator1.
32. Click on the Connections tab. Notice the #1 in place of the Silo number just like how it was used for the global
object.
33. Close the Multistate Indicator Properties configuration dialog and the Object Explorer.
34. Close the Vacuum Silo display. Do not save any changes if prompted.
35. On the Vacuum Silo Group display, double click one of the Silos in the middle of the tank image for example.
The picture below shows the outline of a goto display button and the area to double click.
93 of 132
The first Silo was chosen. Notice the display that will be opened is called Vacuum Silo, the display we just finished examining.
Also, notice a Parameter list is used and the value being passed for the #1 parameter is 1. If more than one parameter is being
used, the order in which the actual values, separated by a comma, are listed is the order in which they are passed. For example,
if the parameter list consisted of {X}, {Y}, {Z} X is the value for #1; Y is the value for #2; and Z is the value for #3.
36. Close the Vacuum Silo Group display and save the changes when prompted.
37. Close the Screen Objects Global Display. Do not save any changes if prompted.
94 of 132
Cross Reference and Search & Replace
Before we test the application, we need to change the shortcut name that is called out in the controller tags. The reason for this
is that we used some pre-configured displays from another application. The shortcut name from the original application is
BlockComms. The shortcut name used in this lab is Intro. So, we need to change wherever BlockComms is called out to be
Intro instead.
There are 10 components that contain the BlockComms shortcut name. Double clicking one of items takes you to the specific
component. We can now access the specific tag and manually change the tag name. However, some of the components use
expressions and the BlockComms name is used multiple times in the expression, so it will take quite a bit of time to manually
update them all.
95 of 132
So, lets use a Search and Replace function instead to make the changes much easier.
5. Enter BlockComms into the Find what: box and Intro into the Replace with: box. Click the Replace All
button.
96 of 132
When the process is complete, a list of successful or failed attempts will be shown.
4. Close the Preconfigured Buttons display and paste the Vacuum Silo button onto the MAIN display.
Remember it will paste into the desired location.
5. Close the MAIN display and save the changes when prompted.
97 of 132
Global Object and Parameters Test Application
So, now we are ready to test the application.
1. Test the application on the Desktop by selecting the Running Man icon in the toolbar.
3. Click on the center of all 4 Silo tanks to navigate to the Vacuum Silo display. Click the
Return button to navigate back to the Vacuum Silo Group display. Notice how the Vacuum Silo display
changes depending on which Silo tank is selected.
4. Click the letter X on your keyboard to shut down the test application.
98 of 132
Now, lets change the background color of the multistate indicator for all 4 Silo data objects. Remember that these are reference
objects.
99 of 132
4. Click the States tab and select State1.
5. Click the square to the left of Back color to bring up the color palette.
6. Select a shade of light green and click OK to apply the color change.
7. Close the Screen Objects display and save the changes when prompted.
8. Test the application on the Desktop by selecting the Running Man icon in the toolbar.
10. Click the letter X on your keyboard to shut down the test application.
You have now learned how using global objects and parameters can simplify your application. The number of objects used and
the number of displays used are reduced. If any future edits are required, the time it takes to perform the edits is also reduced.
100 of 132
Language Switching
Now, lets further explore how to simplify an application by using language switching. We will create a single application that
supports multiple languages.
First, lets add the languages that we need to support into the application.
3. Add the following languages to the application. Each language needs to be added one at a time. Select the
desired language and then click OK. Repeat the process until they are all added.
101 of 132
Your Language Configuration should appear as shown.
5. Ensure English is checked and that Display undefined strings using the default language is checked. Click
the Export button.
6. Ensure the settings are selected as shown below and click Next.
102 of 132
7. Click Finish to begin the export process.
Since we checked to open the file once it has been exported, Microsoft Excel will be opened.
8. Navigate to the Windows taskbar and click on the Microsoft Excel icon.
.
Notice the column headings and how the languages are shown. The text that is not translated is shown as UNDEFINED**.
You can manually translate the new strings for each language or use the FactoryTalk View Translation Utility. The translation
utility uses Microsofts Bing Translator. In this lab, we will manually translate strings for a couple of objects on the MAIN display.
You can learn more about the translation utility in the VZ02 Advanced Lab.
103 of 132
9. Browse to C:\Lab Files\View ME Introductory\Strings. Select Translated Strings.docx and click Open.
10. Copy the text for each language from the Word document into the appropriate cell of the exported Microsoft
Excel file, replacing the text **UNDEFINED**.
Note: de-DE is the German language heading and es-ES is the Spanish language heading.
104 of 132
11. When finished, close and save the Microsoft Excel file. Close the Microsoft Word document.
13. Select Import strings from an Excel spreadsheet into all application languages defined in the
spreadsheet and click Next.
105 of 132
15. The default path is C:\Users\Public\Documents\RSView Enterprise\Strings. Select Intro_1.xls and click
Open.
17. Once the import has completed, click OK to exit the Language Configuration dialog.
106 of 132
Next, well add some language switch buttons to the application.
107 of 132
20. Add the button to the lower left corner of the MAIN display by holding down the mouses left button and drawing
a square.
2. Border width to 1
108 of 132
23. Click the Label tab and click the Image browser button.
26. Click the Common tab and enter the values shown below for Size and Position.
109 of 132
The MAIN display should look similar to this
Lets add the other language switch buttons. These have already been created for you.
110 of 132
29. Close the Preconfigured Buttons display and paste the buttons onto the MAIN display. Remember, the
buttons will paste to the desired location.
30. Close the MAIN display and save the changes when prompted.
Now lets test the application but this time well test it on the PanelView Plus 6 terminal.
111 of 132
Testing the Language Switch Application on the Terminal
Remember, to test the application on a PanelView Plus 6, you need to create a runtime file, MER, and download it to a
PanelView Plus 6 terminal.
4. If prompted click the Yes button to replace the existing runtime application (Intro.mer).
112 of 132
5. Select all the languages to include in the runtime file and click Finish.
After a few moments, a progress dialog, Creating runtime file, will appear; this dialog lets you monitor the creation process.
When the runtime application is completed, the dialog will close automatically.
6. To download the runtime MER to the PanelView Plus 1250 terminal at your workstation, first, select the
Tools>Transfer Utility menu item:
113 of 132
7. Click the Source File browse button to select the runtime MER file to download.
114 of 132
8. Double-click the Intro.mer file to select the runtime application and close the dialog.
115 of 132
9. Select the 192.168.1.20, PanelView Plus_6 1250, PanelView Plus_6 1250 item by clicking on it once. The
screen that you will see may look slightly different from the example shown below:
10. To initiate the download process, click the Download button . If you are asked if you wish to overwrite
the existing file, click Yes.
During the download, a progress dialog will update.
116 of 132
When the download process completes a confirmation dialog is shown.
117 of 132
14. Select the Intro.MER file from those available from the terminals Internal Storage.
118 of 132
15. Press Load [F2] to load the runtime file in to memory.
16. When prompted, press Yes [F7] to overwrite the terminals current communication configuration with the
configuration contained within the VZ01.MER file.
17. Once successfully loaded, press the Run Application [F2] to start executing the runtime file.
After the start-up processing completes you should see your applications startup display.
119 of 132
18. Click the Language Switch buttons and notice how the text changes for the 2 objects that were translated on the
MAIN display.
120 of 132
Now lets take a look at one last feature that is new in FactoryTalk View Machine Edition version 7.0. A PNG image file is now
supported. A PNG file is lossless and can produce very high quality and high resolution images. A PNG is the best overall
image format for computer-generated graphics and files containing text and images having sharp transitions. It also supports
transparency.
1. In the Explorer pane, under Graphics, right click on Images and select Add Component Into Application
3. Change the file type using the drop down arrow from Bitmap Images (*.bmp) to PNG Images (*.png).
121 of 132
4. Select the Spanish flag and click Open to bring that image into the Project library.
5. Double click on the Spanish flag on the MAIN display to bring up its properties.
122 of 132
6. Click the Label tab and click the Image browser button.
123 of 132
124 of 132
Lab Configuration and Setup
Lab Information
125 of 132
Application/Programming
Computer/Host Settings
Location Files
Computer Name Varies by machine
IP Address (NIC 1) DHCP connected to Event classroom network
IP Address (NIC 2) Host computer TCP/IP setting: DHCP
VMware image TCP/IP setting:
IP Addr: 192.168.1.1
Subnet: 255.255.255.0
Operating System Windows 7 Professional
126 of 132
Location Files
C:\Lab Files\ViewME View ME -
Introductory \PVP None required.
C:\Lab Files\ViewME View ME -
Introductory \SoftLogix Block_Machine.acd (Slot 2)
C:\Lab Files\ViewME View ME - Translated Word doc for languages & prebuilt
Introductory \ViewME displays and graphics
Intro Ethernet, Ethernet > 192.168.1.1 > Backplane > 2, 1789-L60 v21
127 of 132
Application Versions
Vendor Software Version Service Pack
FactoryTalk
Activation 3.60.00 CPR9 SR6
Rockwell Manager
FactoryTalk
2.60.00 CPR9 SR6
Rockwell Diagnostics
FactoryTalk
2.60.00 CPR9 SR6
Rockwell Service Platform
FactoryTalk View
7.00.00 CPR9 SR6
Rockwell Machine Edition
Rockwell RSLinx Enterprise 5.60.00000 CPR9 SR6
Rockwell RSLinx Classic 3.60.00 CPR9 SR6
Rockwell Studio 5000 21.00.00 CPR9 SR5.1
Rockwell SoftLogix 5800 21.00.00 CPR9 SR5.1
Rockwell .NET Framework 4
Microsoft Internet Explorer 10
Rockwell PanelView Plus 6 7.00.xx
128 of 132
Configure the Virtual Network
1. Select Virtual Network Editor from the Edit menu to open the Virtual Network Editor dialog.
129 of 132
2. Select the Host Virtual Network Mapping tab
3. For VMnet0 select the physical ethernet adapter that will be connected to the PanelView Plus terminal.
4. Click the OK button to commit the changes that have been made.
130 of 132
Notes
131 of 132
Publication CE-DM255A-EN-E April 2013 132 of 132 Copyright 2011 Rockwell Automation, Inc. All rights reserved.
Supersedes Publication CE-DM232A-EN-E April 2012