reproduction and/or distribution without prior written consent from Rockwell Automation, Inc. is strictly prohibited.
Please refer to the license agreement for details.
Allen-Bradley, DH+, FactoryTalk, Logix5000, PanelView, PLC-5, Rockwell, Rockwell Automation, Rockwell
Software, RSLinx, RSLogix, RSSql, RSView, SLC, SoftLogix, and WINtelligent are trademarks of Rockwell
Automation, Inc.
Any Rockwell Automation software or hardware not mentioned here is also a trademark, registered or otherwise, of
Rockwell Automation, Inc.
ActiveX, Microsoft, Microsoft Access, SQL Server, Visual Basic, Visual C++, Visual SourceSafe,, Windows ME,
Windows NT, Windows 2000, Windows Server, Windows XP, Windows 7, Windows 8.1, Windows 8, and Windows
Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
Oracle is a registered trademarks of Oracle Corporation.
ControlNet is a registered trademark of ControlNet International.
DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA)
All other trademarks are the property of their respective holders and are hereby acknowledged.
This product is warranted in accordance with the product license. The product’s performance may be affected by system
configuration, the application being performed, operator control, maintenance, and other related factors. Rockwell
Automation is not responsible for these intervening factors. The instructions in this document do not cover all the
details or variations in the equipment, procedure, or process described, nor do they provide directions for meeti ng every
possible contingency during installation, operation, or maintenance. This product’s implementation may vary among
users.
This document is current as of the time of release of the product; however, the accompanying software may have
changed since the release. Rockwell Automation, Inc. reserves the right to change any information contained in this
document or the software at anytime without prior notice. It is your responsibility to obtain the most current information
available from Rockwell when installing or using this product.
Version:8.00.00 CPR 9 Service Release 7
August 2014
FactoryTalk View Machine Edition is a member of the FactoryTalk View family of
products. It is an integrated package for developing and running automation applications.
Review operating system requirements
FactoryTalk View ME software is supported on these Microsoft Windows operating
systems:
Operating System32 bit64 bit
Windows Server 2012 R2 Standard Edition
Windows Server 2012 Standard Edition
Windows 8.1 Enterprise Edition
Windows 8.1 Professional
Windows 8 Professional
Windows 8 Enterprise Edition
Windows 7 Ultimate with Service Pack 1
Windows 7 Enterprise Edition with Service
Pack 1
Windows 7 Professional with Service Pack 1
Windows 7 Professional
Windows Server 2008 R2 Standard Edition
Windows Server 2008 Standard Edition with
Service Pack 2
Windows Server 2008 R2 Standard Edition
with Service Pack 1
Windows Server 2008 R2 Enterprise Edition
with Service Pack 1
X
X
XX
XX
XX
XX
X
X
XX
XX
X
XX
X
X
Windows V ista Business with Service Pack 2
X
P-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Operating System32 bit64 bit
Windows XP Professional with Service
Pack 3
Windows Server 2003 R2 Standard Edition
with Service Pack 2
For the latest information regarding software platform support, refer to
PanelView Plus and PanelView Plus CE terminals running Microsoft Windows CE
4.1
PanelView Plus 6 terminals running Microsoft Windows CE 6.0
PanelView Plus 7 terminals running Microsoft Windows CE 6.0
FactoryTalk View Studio is tested and supported on operating systems installed from
original Microsoft media only. For operating systems installed by the computer vendor,
please see Knowledgebase article 26842.
FactoryTalk View Machine Edition gives you all the tools you need to create effective
machine-level monitoring and control applications.
About the documentation
The FactoryTalk View Machine Edition documentation set includes:
Release Notes: Information to read before you begin installing or working with the
software.
X
XX
P-2
The Release Notes are available on the FactoryTalk View installation DVD, as well as
from the Help menu in FactoryTalk View Studio.
FactoryTalk View Machine Edition Installation Guide: A guide to installing and
activating the various components of FactoryTalk View Machine Edition.
The Installation Guide is available on the FactoryTalk View installation DVD, as well
as from the Help menu in FactoryTalk View Studio.
FactoryTalk View Machine Edition User’s Guide: Comprehensive information about
FactoryTalk View Machine Edition, procedures for creating and running an
automation application, and reference information.
The User’s Guide is also available on the FactoryT alk View installation DVD, as well
as from the Help menu in FactoryTalk View Studio.
Help: Online procedures and reference information.
Help is available from the Help menu in FactoryTalk View Studio.
Find the information you need
You have many options for finding information about how to use FactoryTalk View, or
how to solve problems with FactoryTalk View.
Try the User's Guide and Help first
The User’s Guide and Help provide comprehensive information about typical uses of
FactoryTalk View . Chances are, your question is answered in the documentation.
T o find the answer, use the table of contents and the index in the User’s Guide and Help.
You can also perform a full-text search on both the Help and the User’s Guide. For
information about using Help, see Chapter 5, “Getting the information you need,” in the
FactoryTalk View Machine Edition Installation Guide.
For information about performing searches on the User’s Guide, see Adobe Reader Help.
Information on the Internet
If you can’t find the answer to your question or problem in the User’s Guide or Help, you
can find information on the web.
• • • • •
PREFACE
You can connect to the Rockwell Automation web site from within FactoryTalk View
Studio. To do so, you must have a web browser installed on your computer, and you must
have an active Internet connection.
To connect to web sites from FactoryT alk View Studio
From the Help menu, select Rockwell Automation on the Web, and then select the
name of the web page you want to view.
The Rockwell Automation Knowledgebase
The Knowledgebase web page leads to a comprehensive, searchable database of support
information for all Rockwell Automation products.
Contact Rockwell Automation Technical Support
If you can’t find the answer to your question using any of the resources suggested above,
contact Rockwell Automation Technical Support at:
Support staff are available Monday to Friday from 8:00 A.M. to 7:00 P.M. Eastern
Standard Time (North America only), except on statutory holidays.
When you call
When you call, be at your computer and be ready to give:
The product serial number.
You’ll find this number on the Activation disk label and in the About FactoryTalk
View Studio dialog box available from the Help menu in FactoryTalk View Studio.
The product version number.
The type of hardware you are using.
The exact wording of any messages that appeared on your screen.
A description of what happened and what you were doing when the problem occurred.
A description of how you tried to solve the problem.
You may also be required to provide information about the FactoryTalk View add-ons and
updates that are installed on your computer.
To view the list of installed add-ons and updates
1. In FactoryTalk View Studio, select Help> About FactoryTalk View Studio.
P-4
2. To view the list of installed add-ons, click Add-Ons.
1
Getting Started
FactoryTalk View Machine Edition is software for developing and running humanmachine interface applications. FactoryTalk View Machine Edition is designed for
monitoring and controlling automated processes and machines.
For information about installing FactoryTalk View Machine Edition, see the FactoryTalk V iew Machine Edition Installation Guide.
The parts of FactoryTalk View Machine Edition
FactoryTalk View Machine Edition includes two products:
FactoryTalk View Studio
applications. This software runs on operating systems such as Windows Server 2012,
Windows 8.1, Windows 8, Windows 7, Windows Server 2008, Windows Vista, Windows
Server 2003, and Windows XP operating systems.
FactoryTalk View ME Station
level applications. Use FactoryTalk View ME Station to run the applications you develop
in FactoryTalk View Studio.
RSLinx Enterprise
assist in developing and running your FactoryTalk View ME applications.
You can run machine-level applications on the Windows CE 6.0 PanelView Plus 7,
Windows CE 6.0 PanelView Plus 6, Windows CE 4.1 PanelView Plus, and PanelView
Plus CE terminals, aswell as on personal computers.
is configuration software for developing machine-level
is a stand-alone run-time environment for machine-
is a communication server built around FactoryTalk technology to
Additional software
The FactoryTalk View installation DVD also includes two additional software products:
RSLinx Classic
communication drivers. RSLinx Classic is an OPC-compliant data server.
Classic is available for personal computers only
Adobe Reader 11.0.03
Edition User’s Guide. If desired, you can also use the software to print the User’s
Guide.
is software that provides communications to a wide range of
.
is software for reading the online FactoryTalk View Machine
The FactoryTalk View Machine Edition tools
RSLinx
FactoryTalk View Studio tools
These tools are installed with FactoryTalk View Studio:
1-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Application Documenter
FactoryTalk applications.
Application Manager
restoring applications.
DeskLock
is the software that prevents Windows Server 2012, Windows 8.1,
Windows 8, Windows 7, Windows Server 2008, Windows V ista, Windows Server
2003, and Windows XP users from exiting the FactoryTalk View application at run
time. You can use this tool to set up a customized desktop and to prevent access to
Windows functions. You cannot use DeskLock if you are running your application on
a PanelView Plus 7, PanelView Plus 6, PanelView Plus, or PanelView Plus CE
terminal.
FTVIEWUSER Account Reset
account back to its default.
Graphic Strings Search and Replace
operations on STRINGS that are contained within graphic displays. STRINGS
include: tags, expressions, commands or text assigned to objects.
Legacy Tag Database Conversion
database to a new format to work with Microsoft SQL database.
ME Firmware Upgrade Wizard
on PanelView Plus 7, PanelView Plus 6, PanelView Plus, or PanelView Plus CE
terminals.
is software that provides detailed information about
is software for renaming, copying, deleting, backing up, and
is software for resetting the FTVIEWUSER
is software for performing search and replace
is software for converting your legacy tag
is software for installing new firmware releases
1-2
ME Transfer Utility
is software for moving a run-time machine-level application
(.mer file) from the development computer to PanelView Plus 7, PanelView Plus 6,
PanelView Plus, or PanelView Plus CE terminals.
Tag Import and Export Wizard
is software for importing or exporting the
FactoryTalk View tag database.
To start the tools
From the Windows Start menu, select Programs > Rockwell Software >
FactoryTalk View > Tools, and then select the tool to start.
Diagnostics Viewer
Diagnostics Viewer
allows you to view FactoryTalk Diagnostics messages using the
FactoryTalk Diagnostics Viewer.
From the Windows Start menu, select Programs > Rockwell Software >
FactoryTalk Tools > Diagnostics Viewer.
These tools are also available fr om the Tools menu in FactoryTalk View S tudio.
1 • Getting Started
FactoryTalk tools
FactoryTalk tools are installed when you install FactoryTalk Services Platform. They are
available from the Windows Start menu.
To start FactoryTalk tools
From the Windows Start menu, select Programs > Rockwell Software >
FactoryTalk Tools, and then select the tool to start.
FactoryTalk Activation Manager
FactoryTalk Activation Manager is automatically installed when you install FactoryTa lk
View. It is available from the W indows Start menu.
To start FactoryTalk Activation Manager
From the Windows Start menu, select Programs > Rockwell Software >
Start and exit FactoryTalk View Studio.
Open sample applications.
Explore the FactoryTalk View Studio main window.
Use the Explorer window.
Work with editors.
Enter information in spreadsheets.
Print information in editors.
For information about working with editors’ components, see Chapter 18 in the
FactoryTalk View Machine Edition User’s Guide.
Start and exit FactoryTalk View Studio
FactoryTalk View Studio is configuration software for developing machine-level
applications. This software runs on the Microsoft Windows Server 2012, Windows 8.1,
Windows 8, W indows 7, Windows Server 2008, Windows V ista, Windows Server 2003,
and Windows XP operating systems.
Start FactoryTalk View Studio
To start FactoryTalk View S tudio
From the Windows Start menu, select Programs, and then click FactoryTalk View
Studio.
FactoryTalk View comes with several sample applications. We suggest you open the
InstantFizz_ME sample application now to use while you try out the instructions in the
remainder of this chapter. See the instructions on page 2-2.
Exit FactoryTalk View Studio
To exit FactoryTalk ViewStudio
From the File menu, select Exit.
If there are any unsaved changes in open editors, FactoryTalk View Studio asks you
whether to save the changes before exiting the program.
2-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Open sample applications
The sample application is designed for screen resolution 800 x 600.
When you first install FactoryTalk View, sample applications are accessible to all users.
For information about setting up users and granting them access to applications, see
Chapter 11.
To open the InstantFizz_ME sample application
1. Start FactoryTalk View Studio.
2-2
2. In the Existing tab, select InstantFizz_ME.
3. Specify a language for the application, and then click Open.
FactoryTalk View Studio shows the sample application in the Explorer window.
Problems opening applications
If you have trouble opening an application in FactoryTalk View Studio, the problem could
be a Microsoft Windows security setting. You must have read and write access to the
folder that contains the HMI projects. For example, if you belong to the Windows user
group called Power Users, and the group does not have write access to the HMI projects
folder, you won’t be able to open applications in FactoryTalk View.
2 • Explore FactoryTalk View Studi o
The default location for the HMI projects folder is:
C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\ME
(Windows XP, and Windows Server 2003)
or
Users\Public\Public Documents\RSViewEnterprise\ME
(Windows Server 2012, Windows 8.1, Windows 8, Windows 7, Windows Server
2008, and Windows Vista)
For more information about security, see Chapter 11.
To set up write access for any Windows Security Group
1. Right-click the HMI projects folder, and then click Properties.
2. In the Security tab of the Properties dialog box, select a Windows Security Group (for
example, Power Users) from the list of groups and user names.
3. In the Permissions box below the list, select Full Control, and then select Allow.
• • • • •
2-3
Title bar
Menu bar
Toolbar
Explorer
window
Diagnostics List
Status bar
Workspace
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Explore the FactoryTalk View Studio main window
The menu bar
The menu bar contains the menu items for the active window. Each editor has its own set
of menus.
2-4
2 • Explore FactoryTalk View Studi o
Tooltip
The toolbar
The toolbar contains buttons for commonly used menu items so you can have quick
access to the items without opening the menu. When you point to a button on the toolbar,
the button name is shown in a tooltip and in the status bar.
All editors use the Standard toolbar. The Graphic Displays, Graphic Libraries, Runtime
Security, and Tags editors have additional to olbars.
The Explorer window
The Explorer window has two tabs: the Application tab, and the Communications tab.
The Application tab contains the editors for creating and editing your application. It also
contains the System folder for setting up FactoryTalk Security.
• • • • •
The Communications tab contains the communications tree for the development
computer. For more information about using the communications tree, see Help for
RSLinx Enterprise.
For more information about the Explorer window, see page 2-8. For information about
setting up security, see Chapter 11.
The workspace
The workspace is the blank area of the FactoryTalk View Studio window. You can drag
icons from the Explorer window to the workspace to open editors and components. For
more information, see page 2-8.
The Diagnostics List
The Diagnostics List shows messages about system activities. You can specify the types
of messages to show in the Diagnostics List, move the list, resize it, and clear the
messages in it.
For information about testing graphic displays, see page 19-10.
Move the Diagnostics List
You can detach (undock) the Diagnostics List from the main window, and then move the
list anywhere on the screen.
2-5
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
To detach the
Diagnostics List, drag
the grab bars.
• • • • •
T o undock the Diagnostics List, drag the grab bars at the bottom left of the Diagnostics
List. If you can’t see the grab bars, drag the top edge of the Diagnostics List to make it a
bit larger.
T o prevent the Diagnostics List from docking automatically while you move it across the
screen, hold down the Ctrl key on the keyboard while you move the Diagnostics List.
When the Diagnostics List is undocked, you can make it any size you want, for example
to view more than one message at a time. To resize the bar, drag an edge or corner until
the bar is the size you want.
To re-attach the Diagnostics List, double-click its title bar.
To clear the selected message in the Diagnostics List, click Clear. To clear all the
messages in the Diagnostics List, click Clear All.
Messages in the Diagnostics List
The types of messages that appear in the Diagnostics List depend on how you set up
FactoryTalk Diagnostics on the development system. For information about specifying
the types of messages to show, see page 10-3.
2-6
The status bar
The status bar shows information about the active window or about the selected tool or
menu item. The information that is shown depends on where the mouse pointer is. For
example, when you select a graphic object in the Graphics editor, the status bar shows
information about the selected object.
2 • Explore FactoryTalk View Studi o
Workbook tabs
Workbook tabs
If you select Workbook Mode from the View menu, the workspace shows tabs at the
bottom for each open editor or component. Workbook Mode allows you to bring forward
an open item more quickly than by using the Window menu.
• • • • •
2-7
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
The status bar, Explorer
window, Diagnostics List,
and Standard toolbar are
visible. Workbook Mode is
turned on.
• • • • •
Show and hide items in the main window
You can show or hide all the items in the main window (except the menu bar) by clicking
the items on the View menu.
To hide or show the Explorer window
On the View menu, click Explorer Window, or click the Explorer Window tool on the
toolbar.
Use the Explorer window
The Explorer window is the main tool for working with FactoryTalk View Studio. It lists
the editors you use to develop your application, as well as the components, such as
graphic displays, you’ve created.
2-8
Use the Explorer window to set up security for your application. You can use the window
®
to set up users and user groups, and to assign security access to FactoryTalk
Directory to
the application, and to networks and devices. For information about setting up security,
see Chapter 11.
An application consists of one or more data servers and an HMI project (also known as an
HMI server). The data servers provide communications for the project. The project
consists of graphic displays, alarm information, user information, and other settings.
This manual generally uses the term application to refer to both application-level and
project-level procedures.
The top icon is FactoryTalk Directory.
This application contains two servers.
1. The application’s HMI server contains
editors for setting up your application
and the components you create.
Click the - symbol to close a folder
Components are listed below the
editor’s icon when you open the folder.
Click the + symbol to see the list of
components for an editor.
This folder contains FactoryTalk
Security policies and users
2. RSLinx Enterprise data server
• • • • •
2 • Explore FactoryTalk View Studi o
2-9
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
View the Explorer window
You can view the Explorer window in a number of ways:
As a docked window. When docked, the explorer is always on top of other windows
that it overlaps. You can dock the explorer to any edge of the main window.
As a floating window. When floating, the explorer is always on top of other windows
that it overlaps, but you can move it to different locations in the main window.
As a “child” window. When the explorer is in child mode, you can minimize the
explorer or position other windows in front of it. This mode is particularly useful
when you are working in multiple editors or working with the Help open.
T o put the explorer in child mode, right-click the Explorer window title bar , and then click
MDI Child.
Move and resize the Explorer window
You can move the Explorer window in a number of ways:
Click the title bar and drag.
Right-click the title bar, then select a new docking location, floating, or child mode.
2-10
You can resize the Explorer window by dragging its edges.
Work with editors
When developing an application, you will use many different editors, but they have many
similar features and often require similar information. Knowing how to use these features
saves time.
For information on working with particular editors, see the chapters later in this guide.
Locate editors
The editors are grouped in folders in the Explorer window (see the illustration on
page 2-9). Each editor is shown with an icon to the left of the editor name.
To open a folder in the Explorer window
Click the + symbol to the left of the folder icon, or double-click the folder name.
2 • Explore FactoryTalk View Studi o
View an editor's components
With some editors you enter information in a single window or a tabbed dialog box. Other
editors allow you to create multiple components, such as graphic displays or message
files. Each component is stored in a separate file, with its own name.
You can create components in these editors:
Graphics (components include graphic displays, global object displays, and graphic
libraries, each in their own folder)
Alarms
Parameters
Local Messages
Information Messages
Data Log Models
Macros
RecipePlus
• • • • •
The Explorer window lists the components you create under the icon for the editor you
used to create the component.
Use the Images editor to copy bitmap images into your application (but not to create new
images). Each image you copy is listed as a component under the editor.
To view a list of components for an editor
Click the + symbol to the left of the editor icon, or double-click the editor name.
For information about working with components, see Chapter 18 in the FactoryTalk View
Machine Edition User’s Guide.
Open editors
To open an editor
Use the editors in FactoryTalk View Studio to create or modify application components.
Editors are represented by icons in the Explorer window, or by items in menus.
T o open an editor, use one of these methods:
Double-click on one of the components in an application (for example, a display).
Drag the editor’s icon from the Explorer to the workspace.
2-11
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
This column is for display
purposes only.
Enter information in this
column.
• • • • •
Right-click the editor’s icon, and then click New or Open.
If the editor can create multiple components, the shortcut menu contains New. If the editor
can only open a single component, the menu contains Open.
From the Tools menu, select the editor you want to open.
Close editors
To close an editor
Click the close button on the editor’s title bar, or From the File menu, select Close.
Some editors have an OK, Cancel, or Close button that you can click to close the
editor.
Enter information in spreadsheets
Some editors contain spreadsheets for entering information. You can enter information in
the white columns. Gray columns show information; you cannot enter information in
them.
2-12
2 • Explore FactoryTalk View Studi o
These editors contain spreadsheets:
Tags
Runtime Security (formerly User Accounts)
Global Connections
Local Messages
Alarm Setup
Information Setup
Information Messages
Macros
RecipePlus Editor
In the Graphics editor, many of the Properties dialog boxes for setting up graphic objects
contain spreadsheets for assigning tags or expressions to the objects.
To enter information in a cell in a spreadsheet
Click the cell, and then type the information. If the cell already contains text, the new
information is added after the current text.
In the Property Panel, double-click the cell and then type the information. If the cell
already contains text, double-clicking highlights the text and typing replaces the
highlighted text.
• • • • •
Print
To move to the next cell in the row
Press Tab or Enter.
The method to use depends on which editor you’re working in.
To move to the first cell in the next row
Press Enter or Down Arrow.
The method to use depends on which editor you’re working in.
To delete a cell’s contents
Click the cell, and then press Delete or Backspace. Pressing Backspace removes the
characters one by one.
The method to use depends on which editor you’re working in.
To delete rows
Select one or more rows, right-click the selection, and then click Delete Rows.
Each editor has a Print item on its File menu.
2-13
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
To print an editor’s contents
1. Open the editor.
2. From the File menu, select Print.
3. Click OK.
Select a printer
You must install a printer before you can select it. For information about installing a
printer, see your W indows documentation.
The Print Setup menu item in FactoryTalk View Studio applies to your development computer
only.
To print at run time, set up a printer on the computer or PanelView Plus terminal you’ll be using to
run your application. For more information about printing at run time, see page 2-15.
To select a printer
1. From the File menu in any editor or component, select Print Setup.
2-14
2. If you don’t want to use the default printer, specify another printer.
3. Choose the appropriate paper and orientation options.
4. Click OK.
2 • Explore FactoryTalk View Studi o
Select printer setup options
For detailed information about printer options, refer to your Windows documentation.
Select a network printer
FactoryTalk View Studio can print to a network printer. For detailed information about
setting up network printers, refer to your Windows documentation.
Print at run time
Print graphic displays at run time using the display print button or using a remote display
print. You can also send diagnostics and alarm messages to a printer at run time.
For information aboutSee
Display print buttonspage 19-31
Print graphic displayspage 19-30
Print displays remotelypage 8-5
Print alarm messagespage 9-10
Print diagnostics messagespage 10-8
Specify the printers to use at run time for
Windows Server 2012, Windows 8.1, Windows
8, Windows 7, W indows Server 2008, and
Windows Vista applications
The type of printer to use with a PanelView Plus
7, PanelView Plus
PanelView Plus CE terminal
6, PanelView Plus, or
page 15-10
page 16-1
• • • • •
2-15
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
2-16
3
Plan applications
A well-designed application requires planning. To help you plan, this chapter describes:
Understand the machines and processes you’re automating.
Collect data.
Design an HMI tag database.
Plan graphic displays and navigating between them.
Plan languages.
Plan alarms.
Provide information for the operator.
Plan trends.
Plan recipes.
Design a secure system.
FactoryTalk View comes with several sample applications that can give you guidance
when planning your application. For instructions on opening the sample applications, see
page 2-2.
Understand the process
Gather information from a variety of sources so you have a complete and detailed
understanding of the machines and processes you’re automating.
T o gather information:
T alk to machine operators and other experts who are going to use the system. Find out
what information they need to optimize machine operations and processes.
Talk to management and management information systems staff to find out what
information they need to support planning decisions.
Break up each section of the process into its constituent parts.
Determine what type of communications you’ll be using—which network types, data
servers, and devices.
Determine which process variables you need to have access to and identify their
locations in the programmable controllers.
3-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Collect data
When planning data collection, design your system so only essential data is collected.
Limiting data collection is important because collection activities require substantial
processing power and generate a lot of traffic on the network.
Keep data collection requirements in mind when designing the layout of the
programmable controller data tables and the HMI tag database. Ideally, tag addresses
reference contiguous blocks of programmable controller data tables to reduce highway
traffic and optimize system response. If you’re going to use data from an OPC server, read
the server documentation to find out how to optimize traffic.
Design an HMI tag database
Take the time to plan your HMI tag database. A good design helps reduce the time
required for maintenance and can improve programmable controller-to-FactoryTalk View
response time.
For information about creating HMI tags, see Chapter 7.
If you are going to use direct referencing for all your tags, you don’t need to create HMI
tags in FactoryTalk View.
Data Server tags usually update faster than HMI tags. T o obtain the best system performance for
your application, use Data Server tags where possible.
3-2
For information about creating Data Servers to data server tags, see Chapter 6.
Collect informatio n
Before you begin creating the tag database, collect:
Flowcharts of your processes (or process and instrument diagrams).
A list of programmable controller data table or register addresses your application will
have access to.
Machinery systems documentation.
Alarm requirements (for more information, see page 3-6).
Organize tags
Before creating tags:
Develop naming conventions for tags, choosing names that are familiar and logical to
everyone. This makes troubleshooting easier.
Group related tags.
Group tags in the way that makes the most sense for your application. For example,
group all similar devices or group related areas of the plant floor.
When creating tags, place related tags into folders. For greater organization, nest
folders.
Plan graphic displays
When planning displays, determine the best way for users to navigate through your
displays and develop a template to establish a common look and feel for your displays.
Also consider factors about the run-time terminal that affect how the application is shown
and used, such as:
Screen size.
The maximum number of displays supported at run time.
If the applications runs on a personal computer, the maximum number of displays
is based on the type of activation used.
If the application runs on PanelView Plus, the maximum number of displays is
based on the amount of memory used by the application. Applications run on a
PanelView Plus can contain as many displays as can fit in the memory of the
PanelView Plus terminal.
• • • • •
3 • Plan applications
If the application runs on PanelView Plus Compact, for the maximum number of
displays available when the application is running on a PanelView Plus Compact
terminal, see page 4-5.
Whether the operator will be using a keyboard, touch screen, mouse, or combination
of navigation and data entry methods.
For information about creating graphic displays, see Chapter 19.
Develope a hierarchy of displays
A hierarchy of displays is a series of graphic displays that provide progressively more
detail as users move through them. Design your display hierarchy to meet the needs of the
various users, including managers, supervisors, and operators.
Well-organized graphic displays present information clearly and consistently and guide
users through the system. Before designing individual graphic displays, plan an overall
display hierarchy and plan how users will navigate through the hierarchy.
For information about navigation methods and developing a hierarchy of displays, see
Chapter 8.
3-3
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Create a template to ensure consistency
It is possible to keep a consistent appearance among all the displays in an application by
presenting the same pieces of information in the same place on each graphic display. To
ensure uniformity, develop a display with common elements that acts as a template. Each
time you develop a new display, start with a duplicate of the template.
For example, the template could contain:
Your company logo.
A title.
The date and time.
Navigational buttons.
Use global object displays to create template objects. You can copy the objects into your
graphic displays, and update all the objects at once by updating the original object in the
global object display. For information about creating global object displays, see
page 25-11.
Design displays
When designing displays, applying good visual design principles helps users and
increases their efficiency. Remember these important design principles:
3-4
Consistency
Be consistent with your use of symbols and color.
Be consistent with button labels and button placement.
When you design several displays, place the same kinds of buttons in the same
positions. For example, if you have a Start button in a certain position in one display,
don’t put a Stop button in the same position in the next display.
Clarity
Use symbols that are easily recognizable. For example, use the conventional ISA
symbols for tanks and valves.
Don’t overload the screen with information.
Use standard, clear terminology, and avoid abbreviations or acronyms that the user
might not understand.
Use colors with recognizable meanings. For example, in North America the colors red
and green usually mean stop and start. Keep color meanings consistent by assigning
red only to Stop buttons, and green only to Start buttons.
3 • Plan applications
Some people are color blind to red and green so don’t rely on color alone to establish
meaning.
Use high contrast color combinations, such as yellow on blue.
Display Types
On Top display type is used to position the display in front of any other display that is
already open at run-time.
Replace display type is used to have the display close any open displays on the screen
at run-time. Replace displays do not close displays of the type On Top that have the
Cannot Be Replaced option selected. Only one Replace display can be open at a time.
Usability
If you’re designing for a touch screen, don’t place important buttons where they’ll be
blocked by an On Top display. The user can’t press a covered button. Also, ensure the
button is large enough for users to touch easily.
Ensure there is always a clear way to move between displays.
Keep the intended user in mind and design displays so they are easy to understand and
use. Ask the users to test the displays.
• • • • •
Plan languages
Before setting up languages, plan:
Which languages you need to use.
Which Windows fonts support these languages.
For applications running on a personal computer which Windows fonts support
these languages.
For applications running on a PanelView Plus terminal which languages the fonts
resident on the terminal support.
How different languages will affect design elements in your graphic displays, such as
object size and message length.
Whether operators need to switch languages at run time, and if so, under what
conditions. This will help you determine where to locate Language Switch buttons in
your application.
How to show operators which button to press to switch to their languages. For
example, by using a text label in French, or a French flag, to alert a French operator.
For information about setting up language switching, see Chapter 12.
3-5
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Plan alarms
Before setting up alarms, plan:
What conditions will trigger alarms.
How operators will be notified of alarms.
What information you want alarm messages to contain.
How operators will respond to alarms.
The maximum number of alarm messages supported at run time. See page 4-5 for
alarm restrictions on PanelView Plus Compact terminals as well as Windows,
PanelView Plus and PanelViewPlus 6.
For information about setting up alarms, see Chapter 9.
Provide information for the operator
In addition to notifying the operator of alarm conditions, you can provide information and
instructions about plant processes, and inform the operator about system activities.
Before setting up information notification, plan:
What system activity the operator needs to be informed about.
What conditions will trigger information messages.
3-6
What information you want the messages to contain.
Local and information messages
Use local messages to give the operator information in a specific graphic display while the
display is open. Use information messages to give the operator information no matter
which display is open.
For information about setting up local messages, see page 19-26. For information about
setting up information messages, see Chapter 27.
Diagnostics messages
Set up diagnostics messages to notify the operator of system activity such as tag reads and
writes, running macros, communication problems, or problems opening displays.
For information about setting up diagnostics messages, see Chapter 10.
Plan trends
When planning trends, consider how they will be used. For example, will the trend be
used to:
Analyze process trends?
Monitor production efficiency?
Archive process variables to ensure compliance with government regulations?
Based on such considerations, you can determine:
Which tags need to be plotted on the same trend.
Which tags need to be logged by using a data log model.
For information about setting up data logging, see Chapter 26. For information about
creating trend graphic objects, see Chapter 28.
Plan recipes
When planning recipes, consider how they will be used. For example, will recipes be used
to:
Compare tag values to pre-set data values?
Upload tag values to existing or new data sets?
Download values from data sets to tags?
• • • • •
3 • Plan applications
Archive tag values to ensure compliance with government regulations?
Based on such considerations, you can determine:
Which tag sets and data sets to pair together in a recipe file.
Which RecipePlus button actions to use with the RecipePlus selector and RecipePlus
table.
For information about using recipes and creating RecipePlus graphic objects, see
Chapter 29.
Design a secure system
When deciding on your security requirements, consider whether to:
Restrict access to every graphic display to prevent accidental changes.
Restrict access to certain graphic displays.
Have everyone log on.
Use passwords, and if so, whether to have a minimum length, and whether to require
that the passwords are changed periodically.
Allow only authorized users to shut down the application.
3-7
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Use the DeskLock tool on Windows platforms to prevent users from switching to
another application at run time (for applications that will run on personal computers).
You can use this tool to set up a customized desktop and to prevent access to
Windows
®
functions.
Based on these considerations, you can set up security for individual users or groups of
users. For example, you might want to set up groups of users such as a manager group and
an operator group.
For more information about setting up security, see Chapter 11.
3-8
4
Work with applications
This chapter describes:
Application files.
Create, import, open, and close applications.
Rename, copy, delete, back up, and restore applications.
Specify project settings.
View application properties.
View HMI server properties.
What is an application?
An application is the software application you create in FactoryTalk V iew Studio to
monitor and control your plant processes. An application consists of one or more data
servers and an HMI project (also known as an HMI server). The data servers provide
communications for the project. The project or HMI server consists of graphic displays,
alarm information, user information, and other settings.
For information about viewing the application properties, see page 4-18. For information
about viewing the HMI server properties, see page 4-18.
Application versus project
This manual generally uses the term application to refer to both application-level and
project-level procedures. An exception is the section on using the Project Settings editor,
which begins on page 4-11. In that section, the term project is used.
When you create an application, FactoryTalk View creates folders and files in various
locations on the development computer. Some of the folders are empty until you start
setting up your application. When you finish developing the application, FactoryTalk
View uses the information in the various folders and files to create the run-time
application.
HMI project file
The HMI project file has the extension .med. The HMI project file is located in this
directory:
C:\Documents and Settings\All Users\Shared Documents\RSView
Enterprise\ME\HMI projects (Windows XP, and Windows Server 2003 R2)
or
4-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
C:\Users\Public\Public Documents\RSView Enterprise\ME\HMI projects
(Windows Server 2012, Windows 8.1, Windows 8, Windows 7, Windows Server
2008, and Windows Vista)
Run-time application file
The run-time application consists of a file with the extension .mer. For information about
creating the run-time application, see Chapter 14.
Component files
Component files are located in folders in the HMI project folder, as described in the
following table. For example, graphic display component files (with the extension .gfx)
are stored in the Gfx folder. You might need to navigate to the location of these files, for
example if you are adding a component from one application into another application.
This folderContainsFile extensions
Application nameHMI project file and the folders described below .med
DLGData log models (component files).mdf
GfxGraphic display component files.gfx
Global ObjectsGlobal object display component files.ggfx
ImagesImage files.bmp, .png, or .jpg
InformationInformation message component files.ifm
LocalLocal message component files.loc
MacrosMacro component files.mcr
PARParameter component files.par
RecipePlusRecipePlus component files.rpp
4-2
External folders
The following table lists some FactoryTalk View folders that are external to the HMI
project folder, and the types of files they contain.
The folders are located in this directory:
C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise
(Windows XP, and Windows Server 2003 R2)
or
4 • Work with applications
C:\Users\Public\PublicDocuments\RSView Enterprise
(Windows Server 2012, Windows 8.1, Windows 8, Windows 7, Windows Server
2008, and Windows Vista)
This folderContainsFile extensions
ImagesImage files for use on graphic objects.bmp
ME\ArchivesME archive application files.apa
ME\LibrariesGraphic library component files and image files
used in the library displays
ME\Logs\Runtime Application Name\
Dlglog\Data Log Model
Name
ME\Logs\Runtime
Application Name\
M_Alarms
ME\RuntimeRun-time application files.mer
ME\HMI projectsSample application folders, including all files
ME\FaceplatesGraphic displays and global object displays for
Data log files for applications that have run on
the development computer
Alarm log file for applications that have run on
the development computer
and folders needed for the sample
Logix5000 faceplates
.gfx
.bmp
.log
.tag
.alm
.gfx
.ggfx
.bmp
• • • • •
If desired, you can specify a different directory in which to store graphic library
component files. For more information, see page 19-19.
Default log file locations for Pane lV iew Plus 7, PanelView Plus
6, PanelView Plus, or PanelView Plus CE applications
On the PanelView Plus 7 or PanelView Plus 6 terminal, alarm and data log folders are
located by default in this directory:
\Windows\Logs
On the PanelView Plus or PanelView Plus CE terminal, the
located by default in this directory
\Storage Card\Rockwell Software\RSViewME\Logs
alarm and data log folders are
4-3
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Data log file locations
You can also store data log files in a different location on the run-time computer, on a
networked computer, or on a PC card. For more information, see Chapter 26.
Naming files
File names, including the path, can be up to 200 characters long (file names can contain
spaces). For example, the following path and file name contains 119 characters:
C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\HMI
projects\Malthouse Clgx 640x480\Gfx\Steeping.gfx
Creat, import, open, and close applications
Creat applications
You can create a new application when you start FactoryTalk View Studio, or once
FactoryTalk View Studio is already open.
To create a new application when you start FactoryT alk View
Studio
1. Start FactoryTalk View Studio.
4-4
4 • Work with applications
New Application
2. In the New tab, in the Application name box, type a name for your application, up to
32 characters long.
3. If desired, type a description of the application. If you don’t type a description now,
you can add one later, as described on page 4-18 .
4. Specify a language for the application. For information about using different
languages, see Chapter 12.
5. Click Create.
FactoryTalk View Studio creates the application’s folders and files, and then shows
the new application in the Explorer window.
The application is created in the ME\HMI projects directory, in a folder with the same
name as the application name.
This is the path to the ME\HMI projects directory:
C:\Documents and Settings\All Users\Shared Documents\RSView
Enterprise\ME\HMI projects
(Windows XP, and Windows Server 2003 R2)
or
• • • • •
C:\Users\Public\Public Documents\RSView Enterprise\ME\HMI projects
(Windows Server 2012, Windows 8.1, Windows 8, Windows 7, Windows Server
2008, and Windows Vista)
Once you create the application the system automatically creates a display called “MAIN” and
sets the Projects Settings, startup Graphic to “Main”.. These settings determine the general
appearance of your run-time application, and affect how your graphic displays look. For more
information, see page 4-17.
To create a new application when FactoryTalk View Studio is
already open
1. From the File menu, select New Application, or click the New Application tool.
If an application is already open, FactoryTalk View Studio asks you whether to close
the application that is currently open. Click Yes.
2. Follow steps 2 through 5 in the previous procedure.
Import applications
You can import PanelBuilder, PanelBuilder32, PanelBuilder 1400e, and FactoryTalk
View Machine Edition applications into FactoryTalk View Studio.
4-5
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
PanelBuilder and PanelBuilder32 files can be in either development format (*.pba) or runtime terminal format (*.pva). PanelBuilder 1400e files have the file extension *.pvc.
When you import older application files, FactoryTalk View creates a copy of the
application for the current version of FactoryTalk View. The older version is not altered.
You can use current version application files to create previous version run-time files. For
more information, see page 4-9.
If the application you are importing contains any direct driver nodes, the import wizard
will create one RSLinx topic for each direct driver node it finds. All topics are then
converted into device shortcuts, to run with RSLinx Enterprise. You must have both
RSLinx Classic and RSLinx Enterprise installed to make this two-step conversion.
To create RSLinx topics after import, follow these steps in RSLinx before importing the
application.
To validate direct driver nodes in RSLinx
1. Create the appropriate RSLinx Classic drivers if not already created (for example,
AB_ETH-1).
For more information about creating RSLinx Classic drivers, see the RSLinx Classic
Help.
2. If it is an Ethernet driver (AB_ETH-1), add the IP address of each direct driver node to
the Ethernet driver setup.
4-6
3. Start RSWho and select each device associated with each direct driver node (for
example, 131.200.13.128).
If these steps are not followed in this order, the topics generated by the import code
will be invalid and will need to be fixed using the Topic Editor in RSLinx.
To import an application
1. Start FactoryTalk View Studio
2. In the New tab, in the Application name box, type a name for the imported
application, up to 32 characters long.
3. If desired, type a description of the application. If you don’t type a description now,
you can add one later, as described on page 4-18 .
4. Specify a language for the application. For information about using multiple
languages, see Chapter 12.
5. Click Import. The Machine Edition Import Wizard opens.
6. Follow the directions in the Machine Edition Import Wizard.
4 • Work with applications
For more information about importing PanelBuilder 1400e applications, see
Appendix A. For more information about importing PanelBuilder and PanelBuilder32
applications, see Appendix B.
Open applications
You can open an application when you start FactoryTalk View Studio, or once
FactoryTalk View Studio is already open.
Older RSView Machine Edition application files are converted to the current version of
FactoryTalk View when you open them. However, you can still use the current version of
FactoryTalk View Studio to create older version run-time files. For information about the
features supported in different versions of FactoryTalk View, see Appendix G.
For information about opening a sample application, see page 2-2.
To open an existing application when you start FactoryTalk View
Studio
1. Start FactoryTalk View Studio.
• • • • •
4-7
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
Open Application
• • • • •
2. In the Existing tab, select the application to open.
When you select an application from the Existing tab, the resolution and version that was last
used to open the application is shown.
3. Specify a language for the application, and then click Open. For information about
using different languages, see Chapter 12.
4. If this is the first time you are opening an application that was created in an earlier
version of the software, you may be prompted to select a default language. Select a
language, and then click OK. For information about the default language, see
page 12-2.
FactoryTalk View Studio shows the application in the Explorer window.
To open an existing application when FactoryTalk V iew S tudio is
already open
1. From the File menu, select Open Application, or click the Open Application tool.
If an application is already open, FactoryTalk View Studio asks you whether to close
the application that is currently open. Click Yes.
2. Follow steps 2 through 4 in the previous procedure.
To open an application you used recently
1. From the File menu, select Recent Applications, and then click the name of the
application to open.
2. If an application is already open, FactoryTalk View Studio asks you whether to close
the application that is currently open. Click Yes.
The application opens. For applications with multiple languages, the language you
used most recently opens. For information about using different languages, see
Chapter 12.
Problems opening applications
If you have trouble opening an application in FactoryTalk View Studio, the problem could
be a Microsoft Windows security setting. You must have read and write access to the
folder that contains the HMI projects. For example, if you belong to the Windows user
group called Power Users, and the group does not have write access to the HMI projects
folder, you won’t be able to open applications in FactoryTalk View.
The default location for the HMI projects folder is:
C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\ME
(Windows XP and Windows Server 2003)
4-8
4 • Work with applications
or
C:\Users\Public\Public Documents\RSView Enterprise\ME
(Windows Server 2012, Windows 8.1, Windows 8, Windows 7, Windows Server
2008, and Windows Vista)
For more information about security, see Chapter 11.
To set up write access for any Windows Security Group
1. Right-click the HMI projects folder, and then select Properties.
2. In the Security tab of the Properties dialog box, select a Windows Security Group
(for example, Power Users) from the list of groups and user names.
3. In the Permissions box below the list, select Full Control, and then select Allow.
Open multip l e applications
To open two applications at the same time, for example to copy images and graphic
objects between applications, start two instances of FactoryTalk View Studio.
To view a graphic display in different languages at the same time, open the application multiple
times, selecting a different language each time you open it.
• • • • •
Open and edit applications from earlier versions of RSView or
FactoryTalk View ME
You can open and edit applications from RSView 3.10, 3.20, and FactoryTalk View 4.0,
5.0, 6.0, 6.10, and 7.0. When you are finished editing, you can create runtime application
files for ME Station version 3.10, 3.20, 4.0,5.0, 5.10, 6.0, 6.10, and 7.0. This allows you to
continue running your applications on existing terminals, without upgrading all your
software.
The application is converted to the current version of FactoryTalk View when you import
it, but when you create the run-time application file you can save it back to the earlier
version.
If the application uses a feature that is not supported by the run-time version, you will not
be able to create the run-time application file. The exceptions are multiple languages, and
global objects. When you create the run-time application file, it uses the application’s
current language. You can create as many different run-time application files, in as many
different languages, as you want. However, the language switch feature is not available at
run time for version 3.10, and 3.20 applications. Global objects are converted to regular
objects in the run-time application file for versions 3.10, and 3.20.
For information about importing applications, see page 4-5. For information about the
features supported in different versions of FactoryTalk View and RSView, see
4-9
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
Close button
• • • • •
Appendix G. For information about using multiple languages, see Chapter 12. For
information about using global objects, see Chapter 19.
Close applications
To close an application
From the File menu, select Close Application.
If there are any unsaved changes in open editors, FactoryTalk View Studio asks you
whether to save the changes before closing the application.
To close an application and exit FactoryTalk View S tudio at the
same time
Click the Close button at the right end of the FactoryTalk View Studio title bar.
If there are any unsaved changes in open editors, FactoryTalk View Studio asks you
whether to save the changes before closing.
Rename, copy, delete, back up, and restore applications
Use the Application Manager tool to:
Rename applications.
Copy applications.
Delete applications.
Create a compressed backup copy of an application, with the file extension .apa.
Restore an application from the backup file, with the file extension .apa.
Restore a legacy project backup file (with the file extension .mea) from an earlier
release of FactoryTalk View Studio, and convert it to the current version.
Restore a run-time application file, with the file extension .mer, to a development
application, with the file extension .med. For more information, see page 14-6.
T o start the Application Manager tool, do one of the following
In FactoryTalk View Studio, from the Tools menu, select Application Manager.
From the Windows Start menu, select Programs > Rockwell Software >
FactoryTalk View > Tools > Application Manager.
For details about using the tool, see the Application Manager’s Help.
4-10
About project settings
Project window size
(640 x 480 pixels)
Screen resolution
(1024 x 728 pixels)
Project settings determine the general appearance of your run-time application, such as
the size and position of the project window and whether a title bar appears in the project
window. You can also change the setting for running Compact Machine Edition
applications, and enable automatic logout of the current user.
Since project settings affect how your graphic displays look, specify the settings before
creating graphic displays.
Project window size and run-time screen resolution
This section describes the difference between project window size and run-time screen
resolution, and describes how these two settings can affect the behavior of your
application at run time.
The project window size is the amount of room your application occupies on the run-time
terminal or computer screen, in pixels. The run-time screen resolution is the actual size of
the run-time terminal or computer screen, in pixels. Therefore, the project window size
must be less than or equal to the run-time screen resolution.
• • • • •
4 • Work with applications
Usually, an application is designed to completely fill the run-time terminal or computer
screen. If you want your application to do this, set the project window size to the
4-11
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
resolution of the screen in pixels. For information on setting the project window size, see
page 4-17.
Screen resolution for PanelView Plus 7, PanelView Plus 6,
PanelView Plus, and PanelView Plus CE terminals
If you are going to run your application on a PanelView Plus 7, PanelView Plus 6,
PanelView Plus, or PanelView Plus CE terminal, select one of these project window sizes:
For this terminal or monitorSelect this project window size
PanelView Plus - 400 or 600
PanelView Plus Compact - 400 or 600
PanelView Plus 6 - 400 or 600
PanelView Plus Compact 6 - 400 or 600
PanelView Plus 7 4” Wide480x272
PanelView Plus - 700 or 1000
PanelView Plus CE - 700H or 1000H
PanelView Plus 6 -700 or 1000
PanelView Plus Compact - 1000
PanelView Plus 7 6” or 7”
PanelView Plus 7 9” Wide800x480
PanelView Plus - 1250
PanelView Plus CE - 1250H
PanelView Plus CE - 1200P, 1200M, or 1200W
PanelView Plus 6 - 1250
PanelView Plus 7 10”
PanelView Plus - 1500
PanelView Plus CE - 1500H
PanelView Plus CE - 1500P, 1500M, or 1500W
PanelView Plus 6 - 1500
PanelView Plus 7 15”
PanelView Plus 7 12” Wide1280x800
PanelView Plus CE - 1700M
PanelView Plus 7 19”
320x240
640x480
800x600
1024x768
1280x1024
4-12
4 • Work with applications
For this terminal or monitorSelect this project window size
PanelView Plus CE - 2000M1600x1200 (Custom size)
If you are creating an application for a PanelView Plus 7, PanelV iew Plus 6, or PanelView
Plus 400 or 600 terminal:
Resize the default message displays so that the entire message is visible.
Reposition the [ALARM] display from the default position (0, 0), as this position is
below the viewing area of the terminals.
Change the project window size after creating graphic displays
The project window size is used for all graphic displays of the Replace type. If you change
the window size after you have already created graphic displays, you have the option of
scaling graphic displays.
If you choose to scale graphic displays, all Replace and On Top displays are resized and
the objects in them are scaled to fit the new size. You can also specify whether to scale the
font size and border size of the graphic objects, and the size of graphic images in the
Images folder.
• • • • •
If you choose not to scale displays when you change the project window size, Replace
displays are resized, but any objects in the displays remain the same size and in the same
position as before. On Top displays are not resized.
For more information about Replace and On Top displays, see page 19-12. For more
information about scaling displays, see Help.
4-13
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
FactoryTalk View sizes
the pop-up window to
occupy the center of the
screen.
• • • • •
How the run-time screen resolution affects the pop-up windows
FactoryTalk View comes with a pop-up Login window, as well as numeric and string popup windows for run-time data entry, and a Change Password window for changing user
passwords at run time.
4-14
How the project window size affects the default message displays
Your application comes with preconfigured, default graphic displays for diagnostics,
alarm, and information messages. If the project window size is smaller than the default
displays, the edges of the displays are cut off at run time.
If your project window size is smaller than the default message display sizes, you can
resize the default displays, or use your own displays instead.
4 • Work with applications
Control box
Title
Graphic display name
Minimize button
Close button
Compact Machine Edition application
Applications intended for PanelView Plus Compact terminals have certain restrictions,
such as the number of displays and alarm messages supported.
Whether an application will be developed as a Compact Machine Edition application is
specified when the application is first created. You can change that choice here at any
time.
Title bar
If you select this option, a title bar is used for all Replace graphic displays. For
information about graphic display types, see page 19-12.
If desired, you can also use a Control box, Minimize button, and Close button on the title
bar. The Close button appears only if you select the Control box in the Project Settings
editor.
• • • • •
If you plan to set up security for your application and want to prevent unauthorized users
from stopping the application, do not use a title bar.
For information about setting up security, see Chapter 11.
Change the Title bar or Border setting
If you change the Title bar or Border setting, you have the option of scaling graphic
displays to accommodate the new display size. For details, see Help.
4-15
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
The title you specify in the
Project Settings editor
applies to all replace
displays.
You can specify a different
title for each On Top display
(using the Display Settings
dialog box in the Graphics
editor).
• • • • •
Title bar for On Top displays
For On Top displays, you can specify a different name to use in the title bar. Use the
Display Settings dialog box to specify the name (for details, see Help).
4-16
Enable auto logout
Use the Project Settings Runtime tab to log the current user out automatically if the
terminal is inactive for a specified period of time. You can set up the terminal to open a
particular graphic display after the automatic logout, and you can apply a parameter file or
parameter list to the display you select.
If no display is selected, whatever display was open at logout will remain open.
Note that this auto-logout feature that returns to a specific display applies to ALL user accounts
including the DEFAULT user account.
Specify project settings
T o specify project settings, use the Project Settings editor. For details about selecting
options in the editor, see Help.
• • • • •
4 • Work with applications
You can change an application to PanelViewPlus Compact by selecting it in the Project window
size list.
4-17
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
View application properties
You can view this information about your application:
Application name
Application description, if any
T o view application properties
From the Application menu, select Application Properties.
4-18
View HMI server properties
You can use the Explorer window to view this information about your project or HMI
server:
Application name
Application description, if any
Location of the project file
Number of graphic displays in the application
Maximum number of displays you’re licensed to use
4 • Work with applications
To view HMI server properties
In the Explorer window, right-click the HMI server name, and then select Properties.
• • • • •
4-19
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
4-20
5
Set up communications
This chapter describes:
Data servers.
OPC (Open, Productive, Collaborative) communications.
Creating data servers and setting up communications.
About data servers
Data servers provide access to devices, on the network, making it possible to browse,
read, and write values fromFactoryTalk View applications.
FactoryTalk View ME supports the following types of data servers:
Rockwell Automation Device Servers
RSLinx Enterprise is the recommended data server for all Rockwell Automation
devices and networks. RSLinx Enterprise does not require activation or licensing and
can be installed as often as needed in any application.
OPC Data Servers
v2.05a.
The OPC Foundation is a non-profit organization that provides standards and
technology that enables software from different vendors to work together. The
following OPC Data Access v2.05a servers are available with FactoryTalk View ME.
KepServer Enterprise is used to communicate with non-Rockwell Automation
devices like Siemens or Modicon controllers.
KepServer Enterprise does not require activation or licensing for FactoryTalk
View ME.
are any data server that supports the OPC-DataAccess Standard
RSLinx Classic can only be used with FactoryTalk View ME Station and should
only be considered in the following situations:
CIP to non-CIP routing is required to reach the device.
Unsolicited messages are used to send data from controllers.
Alias topics (multiple paths to the same device) are required.
About OPC communications
FactoryTalk View ME supports OPC communication on the PanelView Plus family of
terminals for use with only KEPServer Enterprise. Any OPC Data Access v2.05a
compliant server is supported by FactoryTalk View ME Station running on personal
5-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
computers. RSLinx Classic and KEPServer Enterprise are OPC DA V2.05a compliant
OPC servers.
Create data servers
An RSLinx Enterprise data server is created automatically with a new application. It is
located under the application’s HMI server in the Explorer window, just above the
FactoryTalk System folder.
You can create additional OPC data servers for your application. For example, you might
want to use an RSLinx Enterprise data server and a KEPServer Enterprise data server to
communicate with a third party device.
Set up RSLinx Enterprise data servers
You can use the Communication Setup editor to add drivers, add devices, set up driver
and device properties, and set up device shortcuts.
To set up communications in RSLinx Enterprise
1. In the Explorer window, open the RSLinx Enterprise data server.
5-2
2. Double-click the Communication Setup editor.
3. In a new application, the RSLinx Enterprise Configuration Wizard opens. Follow the
instructions to create a new configuration or use an existing device configuration.
Once you make a choice and click Finish, the Communication Setup editor opens.
In an existing application, double-clicking Communication Setup opens the
Communication Setup editor, with its two tabs.
The Design (Local) tab is for establishing the location of the tags/addresses for editing.
The tags/addresses can be online with a controller or other data server, or an offline
controller file. This will enable the Tag Browser to find the tags/addresses.
5 • Set up communications
The Runtime (Target) tab is for identifying the connection from the run-time computer
or terminal to the controller or other data server. If the paths are the same, use the Copy
button to copy the Design configuration to the Runtime tab.
For more information, see Help for RSLinx Enterprise.
Set up an OPC data server
Use a KEPServer Enterprise data server if you need to connect third party devices.
Use RSLinx Classic data server if you have one of the situations described above and you
are using a personal computer in your application.
If you need to view or use tag names when you are not connected to a device, you can
setup a cache that will read in tag names from the device and enable them to be used when
the device is offline.
To create an OPC data server
In the Explorer window, right-click the application, select Add New Server, and then
click OPC Data Server.
• • • • •
5-3
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
5-4
For details about selecting options in the OPC Data Server Properties dialog box,
see FactoryTalk View Machine Edition Help.
Update data server caches
If tags are added, modified, or deleted on the data server, you must update (synchronize)
the cache manually.
For information about updating the data server cache periodically after you create it, see
FactoryTalk View Machine Edition Help.
For information about editing and removing data servers, see FactoryTalk View Machine
Edition Help.
Summary of steps
T o set up communications, follow these steps:
5 • Set up communications
1. Gather information about your network, and the devices that are connected to it. You
will need this information to set up RSLinx Enterprise, KEPServer Enterprise,
RSLinx Classic, or another OPC server. Do one of the following:
If you want to use KEPServer Enterprise as the OPC server that enables
communications on your network, set up KEPServer Enterprise on the
development computer. For details, see KEPServer Enterprise Help.
If you want to use RSLinx Classic as the OPC server that enables communications
on your network, set up RSLinx Classic on the development computer. RSLinx
Classic is included on the FactoryTalk View installation DVD. For details, see
Getting Results with RSLinx, or see Help for RSLinx.
Note: RSLinx Classic is available for FactoryTalk View ME Station on personal
computers only.
If you want to use an OPC server other than RSLinx Classic for communications
on your network, set up the OPC server on the development computer. For details,
see the documentation supplied with your OPC server.
2. In FactoryTalk View Studio, create a data server that points to the OPC server you
have installed .
For details, see page 5
• • • • •
KEPServer Enterprise is the only OPC Server supported on PanelView Plus terminals.
If you are using RSLinx Enterprise for communications, you don’t need to create a
data server because it is created automatically when you create your FactoryTalk
Machine Edition application.
3. If you want to use HMI tags in your application, open the Tags editor , and then create
device tags that point to addresses in devices. For details about creating HMI tags, see
Chapter 7.
If you do not want to use HMI tags, but instead want to reference addresses in devices
directly, skip this step.
Best practice is to use direct reference tags.
4. In objects in graphic displays, or anywhere else you want access to values in tags, type
the tag name using the syntax for your OPC server, or use the Tag Browser to select
tags. For details about using tags, see Chapter 6.
5. Create the run-time application file. For details, see Chapter 14.
All the necessary tag information is compiled with the run-time application file.
6. If you are using an OPC server other than RSLinx Enterprise or RSLinx Classic,
install the OPC server software on the run-time computer.
5-5
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
For applications that will run on a personal computer, the OPC server can be on a
different (remote) computer than the run-time computer, but the remote computer
must be on the same network as the run-time computer.
5-6
6
Work with tags
This chapter provides general information about working with all kinds of tags. This
chapter describes:
Types of tags.
When to use data server tags.
Steps for using data server tags.
When to use HMI tags.
Steps for using HMI tags.
Browse for tags and offline tags.
Use the Tag Browser.
Use tags and expressions in your application.
Log tag values.
Use macros to assign values to tags.
For information about creating HMI tags, see Chapter 7.
Types of tags
A tag is a logical name for a variable in a device or in local memory (RAM). For example,
a tag can represent a process variable in a programmable controller.
Data server tags
FactoryTalk View conforms to the OPC DA (Data Access) 2.05a specification for
information exchange among automation or control applications, field systems or devices,
and business or office applications.
In FactoryTalk View, data servers such as RSLinx Enterprise, RSLinx Classic, and
KEPServer Enterprise provide access to OPC-DA-compliant tags. In the FactoryTalk
View documentation, the tags you use through a data server are called data server tags.
For more information about data servers, see Chapter 5.
Data server tags include tags found in Logix5000 processors and tags from other OPCcompliant devices. You use data server tags by providing a direct reference to the tag’s
location, wherever you want your application to use the data.
6-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
HMI tags
In addition to direct referencing tags from data servers, FactoryTalk View allows you to
create tags with additional properties such as minimum and maximum values, scale, and
offset. These tags can reference values at an external data source, or store values in the
run-time computer’s memory. Tags you create in FactoryTalk View are called HMI tags.
The data source
The FactoryTalk View documentation uses the term data source as a generic term that
includes all possible sources of tag data, for both data server tags and HMI tags. The data
source can be memory or a device such as a programmable controller or an OPC server.
FactoryTalk View writes values to and reads values from the data source. The data source
is set up to exchange information (in the form of numeric or string values) between the
FactoryTalk View value table and the machine that your application is controlling.
Basic steps for using tags
T o use tags, follow these basic steps:
1. If the tag does not already exist, create the tag.
T o use a data server tag, you can use an existing tag in the processor (for example, a
programmable controller), or you can create a new one in the processor or OPC server.
For example, in a Logix5000 processor, you could create the tag using your RSLogix
5000, or Logix Designer programming software.
6-2
T o use an HMI tag, you must first create it in the Tags editor. For details, see
Chapter 7.
2. Browse for, or type, the name of the tag anywhere you want to connect an object to
data at run time.
For example, to make a push button change a tag value when it is pressed, connect the
push button to a tag by typing the tag name in the Connections tab of the push button’s
Properties dialog box.
Browse for tags
If you don’t know the names of tags, you can browse for them. You can browse while
online and connected to a device, or you can browse for tags from an offline file, for
example a Logix5000 program file.
T o browse for tags, use the Tag Browser. For details, see page 6-5.
Use tag names that don’t exist
You can type the name of a tag that doesn’t yet exist. If you do this, ensure that you spell
every instance of the tag name consistently, and that when you do create the tag, you spell
it the same way you did when you referred to it.
When to use data server tags
For some of the things you want to do in your application, you might not need to create
HMI tags. Use direct references to tags located in devices instead, for example, tags
located in an OPC server’s database.
Eliminate du plication
Using data server tags allows you to add, modify, or delete tags in a device without having
to duplicate the changes in the FactoryTalk View HMI tag database.
Use complex data
Some devices, for example Logix5000 processors, support complex data types such as
arrays and structures. Your controller might have structures that contain hundreds of
member elements.
• • • • •
6 • Work with tags
Referencing tag values directly eliminates the need for creating an HMI tag for each
member.
Direct reference tags usually update faster than HMI tags. To obtain the best system
performance for your application, use direct reference tags where possible.
Steps for using data server tags
To use data server tags, complete three basic steps:
1. Create the tag in the OPC server or processor, or use an existing tag in the processor.
The server must understand the syntax of the device it is connected to. You need only
create a tag if you want to browse the server.
Examples of OPC servers include RSLinx Enterprise, RSLinx Classic, and
KEPServer Enterprise. For information about creating tags in OPC servers that have
their own tag database, see the documentation provided with the server.
For information about creating tags in a Logix5000 processor, see the documentation
for your device programming software.
2. Create a data server in FactoryTalk V iew, if your application doesn’t already have one.
Every new FactoryTalk View Machine application includes a RSLinx Enterprise data
server automatically.
6-3
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
For more information, see Chapter 5.
3. In graphic displays, data log models, or anywhere else you want to use a tag’s value,
create a direct reference to the tag. At run time, the tag’ s value is passed to the graphic
display or data log model.
When to use HMI tags
Use HMI tags to manipulate tag data and to store tag values in the run-time computer’s
memory.
Scale, offset, or provide a range for data
Use HMI tags if the data server you are using does not provide for:
Scale or offset a value.
Set minimum or maximum limits on a value (that is, providing a range of values).
Scale and offset
The scale and offset modify the raw data that comes from and goes to the programmable
controller before the data is saved in the computer’s memory (called the value table). The
scale and offset also modify the value specified in FactoryTalk View before it is written to
the programmable controller.
6-4
The scale is a multiplication factor—the value from the programmable controller is
multiplied by the scale.
The offset is a fixed value—after the value from the programmable controller is
multiplied by the scale, the offset amount is added.
Minimum and maximum
HMI tags allow you to set a minimum and maximum value that can be written to the
programmable controller or server.
These values do not affect what is read from the programmable controller or server.
For example, if you specify a minimum of 0 and a maximum of 100, FactoryTalk View
would be able to read a value of 200 from a programmable controller and store it in the
value table, but would not be able to write this value to the programmable controller.
For more information about minimum and maximum, and scale and offset, see Help.
Store values in FactoryTalk View memory
A memory tag can be used to store values without the need for an attached or accessible
device.
For example, you might need to store a value in memory:
T o store the result of a calculation.
T emporari ly, for example, a counter or index.
To maintain information about the system’s current state, for example which graphic
display was last opened.
For information about creating HMI memory tags, see Chapter 7.
Steps for using HMI tags
To use HMI tags, complete two basic steps:
1. In the Tags editor in FactoryTalk View, create a tag. HMI tags can be used as an
internal storage location. Optionally you can map the tag name to an OPC tag or
device address.
For more information, see Chapter 7.
2. In graphic displays, alarm triggers, or anywhere else you want to use a tag’s value,
assign the tag. At run time, the tag’s value is passed to the graphic display or alarm
system.
Browse for tags
You don’t have to remember the path and name of a tag to use it in your application.
Whenever you need to use a tag, you can open the Tag Browser and select the tag to use.
• • • • •
6 • Work with tags
T o open the Tag Browser
In most editors, click the Browse button in the Tags column.
In the Expression editor, position the cursor where you want to insert a tag name, and
then click Tags.
In the Parameters editor, double-click where you want to insert a tag name.
6-5
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
Root folder
Folders pane
Tags pane
For a better view of the
folders or tags, drag this bar
to the left or the right.
• • • • •
Use the Tag Browser
6-6
In the Tag Browser, you can:
Select a single tag or multiple tags. The ability to select multiple tags is available in
the Data Log Models editor only. In the illustration above, only a single tag can be
selected.
Select data server tags and HMI tags.
Select a folder of tags without selecting a specific tag in the folder. This is useful for
applications that use controller instruction faceplates. It is also useful when you use
global object parameters. Folders of tags are also known as backing tags or structured
tags. For information about global object parameters and controller instruction
faceplates, see Chapter 25.
You cannot select backing tags when you open the Tag Browser from the Data Log
Models editor.
6 • Work with tags
The folders list with server
names hidden.
The folders list with server
names shown.
Create and edit HMI tags.
Create new folders for HMI tags.
Import tags from a PLC or SLC
™
database.
For more information about using the Tag Browser, see Help.
Show server names
By default, the Folders pane in the Tag Browser shows folders, but not the servers they
belong to. You can show the names of servers that have been set up in the application.
T o show server names
Right-click a blank area of the Folders pane and then select Show Server Names.
• • • • •
In the example on the left, folders are listed alphabetically by name.
In the example on the right, there are two data servers, named KEPServer and
RSLinxServer. Folders of data server tags are listed under the data server, to which they
belong. Below the data servers, the application is listed as an HMI server, with folders of
HMI tags under the application name.
Browse for off-line tags
For each RSLinx Enterprise device shortcut, or each RSLinx Classic OPC topic in your
application, an Offline and an Online folder is shown in the Tag Browser.
6-7
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
Tags that are available when
you are not connected to the
controller are located in the
Offline folder.
Tags that are available when
you are connected to the
controller are located in the
Online folder.
• • • • •
In RSLinx Enterprise, you can use the Offline folder to browse tags in an RSLogix 5000
RSLogix.acd file. For details about making the .acd file available to browse offline, see
RSLinx Enterprise Help.
In RSLinx Classic, you can use the Offline folder to browse tags in a PLC program stored
on disk. If the OPC topic in RSLinx Classic has access to symbols, you can browse for
them in the Offline folder. For details about adding symbols to the OPC topic in RSLinx
Classic, see RSLinx Classic Help.
Use tags and expressions in your application
Once you’ve created tags (either in data servers or in FactoryTalk View), assign them to
connections in your application to allow the application to interact with the data source
and perform actions based on the tag values.
6-8
You can assign tags in these editors:
Expressions
Global Connections
Graphic Displays
Global Object Displays
Graphic Libraries
Parameters
Alarm Setup
Information Setup
Macros
Data Log Models
RecipePlus Editor
6 • Work with tags
Type the tag name here......or click the Browse button to open the
Tag Browser.
Assign tags
This example shows the Trigger dialog box that opens when you click the Add button in
the Triggers tab of the Alarm Setup editor:
To assign a tag, do one of the following
In the Tag or expression column, type the tag name.
In the Tag column, click the Browse button and then select a tag from the Tag
Browser.
• • • • •
For information about using the Tag Browser, see Help.
Assign tags to graphic objects
In the Graphics editor, you can assign tags to many of the graphic objects you create.
You can use up to 1,000 tags per graphic display. This limit includes the tags contained in
embedded variables and expressions. For example, if an expression references the same
tag twice, this counts as two tag references.
6-9
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
Type the tag name here......or click the Browse button to open the
Tag Browser.
Type the tag name
here...
...or click the
Browse button to
open the Tag
Browser.
• • • • •
Use one of these methods to assign tags to a graphic object:
Double-click the object to open the object’s Properties dialog box, and then click the
Connections tab.
Select the object, and then assign tags in the Connections tab of the Property Panel.
6-10
6 • Work with tags
Type the expression here......or click the Browse button to open the
Expression editor.
Use expressions to manipulate tag values
In many of the places where you can assign a tag, you can also use expressions to perform
logical or mathematical calculations on tag values. If you assign an expression,
FactoryTalk View monitors the expression value rather than the original tag value. For
example, your machine might send values to the data source in the form of temperature in
degrees Celsius. You could use an expression to convert the value to degrees Fahrenheit,
and then monitor the expression result rather than the original tag value.
If you can assign an expression, a Browse button is present in the Exprn column in the
editor or Connections tab.
• • • • •
To assign an expression, do one of the following
In the Exprn column, click the Browse button, and then create an expression in the
Expression editor. Use this method if you want to check the expression syntax.
In the Tag or expression column, type the expression. The expression syntax is not
checked if you use this method.
For more information about expressions, see Chapter 23.
Substitute tag names used in grap hic ob jects
You can use tag substitution or Find and Replace to replace tag names and expressions
assigned to the connections for graphic objects. For example, if you assign a tag to
multiple objects in a graphic display, and then decide to use a different name for the tag,
you can create a new tag and then use tag substitution or Find and Replace to search for all
tag references with the old name, and replace them with the new tag name.
You can also use tag substitution to replace the tags contained in embedded variables.
For more information about tag substitution and Find and Replace, see page 20-38.
6-11
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Log tag values
Analog and digital tag values can be logged, including both HMI and data server tags. To
set up data logging, use the Data Log Models editor. For more information, see
Chapter 26.
6-12
Use macros to assign values to tags
A macro is a list of tag assignments stored in a text file. Whenever you run the macro, the
specified values are written to the tags. For more information about macros, see
Chapter 30.
You can also use recipes to assign values to multiple tags with a button press. For
information about using recipes to assign values to tags, see Chapter 29.
7
Use HMI tags
This chapter describes:
HMI tag types.
Use the Tags editor.
Data sources.
Address syntax for device tags.
Organize HMI tags.
View tag statistics.
Other methods for creating HMI tags.
Import HMI tags.
HMI tag types
HMI tags are tags you create in FactoryTalk View. For information about when to use
HMI tags versus when to use data server tags, see Chapter 6.
You can create and use these types of HMI tags in FactoryTalk View:
This tag typeStores this type of data
AnalogRange of values.
Use analog tags to represent variable states such as temperature or the
position of rotary controls.
Digital0 or 1.
Use digital tags to represent devices that can only be on or off, such as
switches, contacts, and relays.
StringASCII string, series of characters, or whole words (maximum of 82
characters).
Use string tags to represent devices that use text, such as a bar code scanner
that uses an alphanumeric product code.
7-1
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
This tag typeStores this type of data
SystemInformation generated while the system is running, such as the name of the
logged-in user, system time and date, and so on.
FactoryTalk View creates system tags when you create an application. The
system tags are stored in the folder called “system” in the HMI tag
database. You cannot edit system tags. You can use system tags anywhere
you would use any other type of tag. For a list of system tags, see
Appendix C.
Analog tags that use floating-point values
You can assign analog tags to most of the connections in FactoryTalk View, including
both HMI and data server tags. If the analog tag uses a floating-point data type but an
integer value is required, the floating-point value is rounded.
For information about the data types available for analog tags, see Help.
How values are rounded
When a floating-point value must be rounded to an integer, this is how the value is
rounded:
If the number after the decimal is 4 or less, the value is rounded down. For example,
8.495 is rounded to 8.
7-2
If the number after the decimal is 6 or more, the value is rounded up. For example, 8.6
is rounded to 9.
If the number after the decimal is 5, the value is rounded using a “banker’s algorithm,”
to average out the rounding over time:
If the number before the decimal is 0, the value is rounded down. For example,
10.5 is rounded to 10.
If the number before the decimal is an odd number, the value is rounded up. For
example, 11.5 is rounded to 12.
If the number before the decimal is an even number, the value is rounded down.
For example, 12.5 is rounded to 12.
Floating point values are rounded to a maximum of six digits. Therefore, using a
floating-point data type and adding to it a value that exceeds the six significant
digits will result in a rounding error. For example, adding any number to 999,999
will result in a rounding error.
This rounding method is also used for Numeric Input Enable buttons that use the implicit
Form area
Query box
Folder
hierarchy
decimal position, if an integer tag is assigned to the button’s Value connection. For more
information about the Numeric Input Enable button, see page 21-30.
Use the Tags editor
The Tags editor has these parts: form area, query box, folder hierarchy, and spreadsheet
area.
• • • • •
7 • Use HMI tags
The information you enter in the form area is shown in the spreadsheet area. The folder
hierarchy shows all the folders that you and FactoryTalk View create.
The Tags editor has special items on the View menu to control the appearance of the
editor, and extra tools on the toolbar.
Use the Tags editor to:
Create folders
Duplicate, nest, and delete folders
7-3
FACTORYTALK VIEW MACHINE EDITION USER’S GUIDE
• • • • •
Create and view tags
Edit, duplicate, and delete tags
For details about using the Tags editor, see Help.
Update the contents of the Tags editor
You can create tags in the Tags editor, but you can also create them as you work in other
editors, and you can import them from an existing tag database. To see the result of
changes to the database you make in other editors while the Tags editor is open, update
the contents.
To update the contents of the editor
From the View menu, select Refresh, or click the Refresh tool.
When you select Refresh, the undo buffer is cleared and recent changes can’t be
automatically reversed.
Refresh is not available if you haven’t accepted the current tag.
For information about creating tags in other editors, see page 7-10.
Search for HMI tags
Use the Tags editor’s query box to select the tags you want to show in the spreadsheet.
This allows you to edit tags in different folders without browsing the folder hierarchy . You
can:
7-4
Select a single tag by typing the tag name.
Select multiple tags by typing wildcard characters.
These are the wildcard characters:
This characterDoes this
?Matches any single character.
*Matches any number of characters, including the backslash (\) character.
Use this wildcard character by itself to show all the tags in the HMI tag
database.
For example, to search for all the tags that contain the string “pump” in their name, type
*pump* in the Search For box. When you press Enter, a list of tags containing the string
“pump” appears in the spreadsheet.
When you do searches, remember that the backslash in a folder name counts as a character
in the tag name.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.