View Site Edition USER’S GUIDE PUBLICATION VIEWSE-UM006I-EN-E–August 2014 Supersedes Publication VIEWSE-UM006H-EN-E
Contacting Rockwell Contact Rockwell Customer Support Telephone — 1.440.646.3434 Online Support — http://www.rockwellautomation.com/support/ Copyright Notice © 2014 Rockwell Automation, Inc. All rights reserved. This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation, Inc. is strictly prohibited. Please refer to the license agreement for details.
Contents 1 • Getting started with FactoryTalk View SE ..................................... 1–1 Welcome to FactoryTalk View Site Edition ...............................................................1– 1 About FactoryTalk systems.........................................................................................1– 1 FactoryTalk Services Platform ............................................................................1– 1 Finding more information about FactoryTalk services .........................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Working in the Explorer window................................................................................2– 8 Moving the Explorer window..............................................................................2– 9 Opening and closing folders ..............................................................................2– 10 Opening component editors...............................................................................
Designing a system that is easy to deploy and maintain ...........................................3– 14 Designing the application for multiple users.....................................................3– 14 Integrating with other applications and customizing the system ..............................3– 14 4 • Setting up the FactoryTalk Directory ............................................. 4–1 About FactoryTalk Directory ......................................................................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE About FactoryTalk Security accounts .......................................................................5– 21 About the All Users account..............................................................................5– 22 Specifying which users can set up security .......................................................5– 22 Choosing the types of accounts to use ......................................................................
Setting up HMI server properties.............................................................................6– 15 Changing the name of the host computer ..........................................................6– 16 Choosing how the server starts..........................................................................6– 16 Setting up HMI server redundancy ..................................................................6– 17 Selecting startup and shutdown components......................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Determing where the application is located ..............................................................7– 14 8 • Working with local station applications......................................... 8–1 About FactoryTalk View SE local station applications ..............................................8– 1 Parts of a local station application .......................................................................8– 2 About FactoryTalk systems .............
Deleting an OPC data server .............................................................................9– 13 10• Working with tags .......................................................................... 10–1 About data server tags and HMI tags.......................................................................10– 1 Using direct referencing to eliminate duplication .............................................10– 2 Using the extended capabilities of HMI tags .........................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Form and spreadsheet ......................................................................................10– 21 Query box ........................................................................................................10– 21 Folder hierarchy...............................................................................................10– 21 Creating, modifying, and deleting HMI tags ..........................................................
About FactoryTalk View SE alarm events..............................................................11– 22 Setting up HMI tag alarm logging ..........................................................................11– 24 Specifying where log files are stored or printed..............................................11– 25 Specifying when log files are created and deleted ..........................................11– 25 Setting up periodic logging to a central ODBC database ................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Alarm class ......................................................................................................12– 12 Alarm states .....................................................................................................12– 13 Alarm tags........................................................................................................12– 13 Alarm status tags ............................................................................
Viewing alarm details ......................................................................................12– 46 Unsuppressing and suppressing alarms ...........................................................12– 47 Disabling and enabling alarms ........................................................................12– 48 Viewing alarm and event history logs.....................................................................12– 49 The parts of an alarm and event log viewer...............................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Working with pairs of double quotes ..............................................................13– 19 Working with backslashes and new-line characters ........................................13– 20 Importing translated or modified text strings..........................................................13– 20 Troubleshooting import problems ...................................................................13– 21 Setting up run-time language switching..
Modifying HMI tag alarm properties ..............................................................14– 26 Managing HMI data in an online redundant system ...............................................14– 29 Synchronize time clocks on redundant computers ..........................................14– 29 Centralize storage of diagnostic and alarm log data........................................14– 30 Determine which server will run events ..........................................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Arranging objects ............................................................................................16– 13 Flipping objects ...............................................................................................16– 17 Rotating objects ...............................................................................................16– 18 Grouping objects......................................................................................
Docking displays to the FactoryTalk View SE Client window ..............................16– 51 Display command parameters for docking displays........................................16– 51 About the appearance and behavior of docked displays..................................16– 52 Closing docked displays ..................................................................................16– 54 Printing displays at run time ...................................................................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Creating the different types of data display and input objects ................................17– 21 Using input objects to retrieve and send data ..................................................17– 22 Shortcut keys for retrieving and sending data .................................................17– 25 FactoryTalk View commands for retrieving and sending data........................17– 25 Parts of the on-screen keyboard...............................
Creating piloted control selectors ....................................................................17– 47 Specifying the text and value for each state ....................................................17– 47 Setting up connections for a piloted control list selector.................................17– 48 Creating the Alarm and Event objects ....................................................................17– 49 Creating global objects.................................................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Determining start and end points for a range of motion....................................18– 4 Defining the range of motion.............................................................................18– 4 Applying animation to object groups ................................................................18– 5 Testing animation ..............................................................................................
Setting up keys to run FactoryTalk View commands ...............................................19– 6 General rules governing precedence..................................................................19– 7 Precedence and the F1 key................................................................................19– 7 Precedence and embedded ActiveX objects ......................................................19– 7 Precedence and embedded OLE objects .........................................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 21• Creating embedded variables ....................................................... 21–1 About embedded variables ........................................................................................21– 1 Inserting embedded variables....................................................................................21– 2 Creating numeric embedded variables ......................................................................
Ways to stop data logging ...............................................................................22– 17 23• Setting up trends............................................................................ 23–1 About trends ..............................................................................................................23– 1 Charting current versus historical data ..............................................................23– 1 Creating trend objects ....................................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Working with trends at run time .............................................................................23– 23 Collecting data in the background at run time.................................................23– 23 Selecting pens at run time................................................................................23– 25 Modifying trend properties at run time............................................................
Using absolute and relative references....................................................................... A– 5 How relative references are resolved.................................................................. A– 5 Creating symbols........................................................................................................ A– 6 Important guidelines ........................................................................................... A– 8 Running and building commands................
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE xxvi
Getting started with FactoryTalk View SE This chapter describes: What FactoryTalk View Site Edition is. What a FactoryTalk system is. FactoryTalk View Site Edition software. FactoryTalk View tools and utilities. How to set up the software you need. Running FactoryTalk View SE without activation. Exploring the Samples Water application. How to start creating a new network distributed application.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using services, FactoryTalk products can share and gain simultaneous access to resources such as tags and graphic displays that you only need to define once in the system. The FactoryTalk Services Platform installs behind the scenes during FactoryTalk View SE installation.
To open the FactoryTalk Help Select Start > All Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Help. You can also open the FactoryTalk Help by clicking Help in dialog boxes used to set up FactoryTalk components and services. FactoryTalk View Site Edition software FactoryTalk View SE consists of several pieces of software you can use to build network or local HMI applications, customized to your needs.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The FactoryTalk View SE Server has no user interface. Once installed, it runs as a set of ‘headless’ Windows services that supply information to clients as they request it. FactoryTalk Alarms and Events installs behind the scenes during FactoryTalk View SE installation, and provides system-wide alarm monitoring and control centralized at the FactoryTalk Directory.
Create a complete alarm monitoring system that includes FactoryTalk Alarms and Events and HMI tag alarms. Using FactoryTalk Alarms and Events services, FactoryTalk View SE applications can subscribe to and display device-based alarms, programmed directly into Logix5000 controllers. Customize alarm summaries and banners to provide specific alarm data, rather than displaying alarms for the entire system.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To develop or run a Network Distributed application, you can install different combinations of software on each computer, depending on needs. To develop or run a Network Station application, you must install all the necessary software components on one computer (except for data servers). Network station applications can connect to data servers that are located on different machines.
Do not run FactoryTalk Directory, or any other application software, on the same computer as a Windows domain controller. Step 2: Install the FactoryTalk Services Platform FactoryTalk View applications depend on FactoryTalk software, such as FactoryTalk Directory, to run. During the FactoryTalk Services Platform installation, the FactoryTalk Network Directory and Local Directory are set up automatically on the computer.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For communications with Allen-Bradley local and remote devices—particularly with Logix5000 controllers—RSLinx Enterprise is the recommended data communications software for FactoryTalk View applications. When to use RSLinx Classic RSLinx Enterprise is the preferred choice when using Logix controllers, but there are some cases where Linx Classic must be used.
• • • • • 1 • GETTING STARTED WITH FACTORYTALK VIEW SE With a Site Edition network distributed application in demo mode, you can: Create or load up to five HMI servers locally in FactoryTalk View Studio. Create or load up to five graphic displays per HMI server. Run a local FactoryTalk View SE Client for up to two hours. Remote clients cannot connect to an application in demo mode. Import only the first graphic in each category from Symbol Factory.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 3. In the New/Open Site Edition (Network Distributed) Application dialog box, click Samples Water, select an application language, and then click Open. In the illustration, the graphic display named Aeration and the undocked Objects toolbar are open in the Graphics editor. For information about working with FactoryTalk View Studio and the editors, see Chapter 2, Exploring FactoryTalk View Studio. To test a display in FactoryTalk View Studio 1.
• • • • • 1 • GETTING STARTED WITH FACTORYTALK VIEW SE To run the Samples Water client Select Start > All Programs > Rockwell Software > FactoryTalk View > Samples Water. Navigate to other displays in the application using touch zones... ...and buttons on the menu bar. Switch between languages in the application. View FactoryTalk alarms in a docked alarm banner. View Diagnostics messages.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The HMI server stores project components (for example, graphic displays) and serves these components to clients. The server also contains a database of tags, and performs alarm detection, and historical data management (logging). To create a new network distributed application 1. Select Start > All Programs > FactoryTalk View Studio. 2. In the Application Type Selection dialog box, click Site Edition (Network Distributed), and then click Continue. 3.
• • • • • 1 • GETTING STARTED WITH FACTORYTALK VIEW SE For details about options in the Add HMI Server Wizard, click Help. Step 2: Create a graphic display Adding an HMI server to an application also creates the HMI project, which contains all of the editors and productivity tools you need to create and modify application components. For a list of editors and their functions, see “Opening component editors” on page 2-10. For instructions about using the editors, click Help in the editor dialog boxes.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Step 3: Test run the application in FactoryTalk View SE Client In FactoryTalk View Studio, you can only test one graphic display at a time. To test navigating among displays, run the application in a FactoryTalk View SE Client. To run the new application you just created, create a FactoryTalk View SE Client configuration file that specifies: The type and name of the application the client will connect to.
Exploring FactoryTalk View Studio 2 • Placeholder 2 This chapter describes: What FactoryTalk View Studio is. How to open an application in FactoryTalk View Studio. Parts of the FactoryTalk View Studio main window. Working in the Explorer window. Techniques for working in editors. Printing from FactoryTalk View SE. About FactoryTalk View Studio FactoryTalk View Studio is the configuration software for developing and testing FactoryTalk View Site Edition applications.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For an overview of FactoryTalk Security services, see Chapter 5, Setting up security. For details, see the FactoryTalk Security Help. Opening an application in FactoryTalk View Studio When you start FactoryTalk View Studio, the Application Type Selection dialog box opens. You can select: View Site Edition (Network Distributed) to create or open a FactoryTalk View SE network application (also called a network distributed application).
• • • • • 2 • EXPLORING FACTORYTALK VIEW STUDIO To set up write access for Power Users The default path for the HMI Projects folder is: C:\Users\Public\Public Documents\RSView Enterprise\SE (Windows XP or Windows Server 2003) C:\Documents and Settings\All Users\ Shared Documents\RSView Enterprise\SE 2. In the Security tab, select Power Users from the list of group or user names. 3. In the Permissions list under the list of names, beside Full Control, select the Allow check box.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Parts of the FactoryTalk View Studio main window When you create or open an application, its contents are shown in the FactoryTalk View Studio main window. Menu bar Toolbar Explorer window Workspace Browse devices on the network. View the application. Diagnostics List Status bar Menu bar The menu bar contains the menu items for the active window. Each editor has its own set of menus.
All FactoryTalk View editors use the Standard toolbar, shown here in its undocked form: The Graphics editor has additional toolbars that are shown when you open a graphic display, a global object display, or a library. The next illustration is of the Graphics and Objects toolbars, in their undocked forms: Explorer The Explorer is the main tool for working in FactoryTalk View Studio. It provides access to the editors you use to set up the application and create its components.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Communications tab The Communications tab shows the devices on the network available to the computer hosting RSLinx Enterprise. Use this tab for setting up network types and browsing devices on the configured networks. For more information, see Chapter 9, Setting up communications. For details, see the RSLinx Enterprise Help. Diagnostics List The Diagnostics List shows information about system activities.
• • • • • 2 • EXPLORING FACTORYTALK VIEW STUDIO Removing messages from the Diagnostics List Click Clear, to remove the most recent message (at the top of the list), or to remove the selected message. Click Clear All, to remove all the messages in the list. Removing a message from the Diagnostics List does not delete the message from the Diagnostics log. Status bar The information shown in the status bar depends on what you are doing in FactoryTalk View Studio and where the pointer is.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Showing and hiding items in the main window To show or hide elements of the main window (except the menu bar), select items on the View menu: if there is a check mark beside an item, the item is visible; if there is no check mark, the item is hidden. The status bar is visible. Workbook Mode is off. The Explorer Window and Diagnostics List are hidden. The Standard toolbar is visible.
• • • • • 2 • EXPLORING FACTORYTALK VIEW STUDIO 2 • Placeholder FactoryTalk Network Directory Application name Area HMI server Click the – symbol to close a folder. Components are listed under the editor’s icon. Click the + symbol to open a folder. Moving the Explorer window To undock the Explorer, use one of these methods: Click the Explorer’s title bar, and then drag the window. To prevent the Explorer from docking automatically, press and hold the Ctrl key as you drag.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If you click MDI Child, the Explorer becomes a window that you can move, minimize, maximize, or restore, within the main window. You cannot move the Explorer outside the main window. As long as it is undocked, you can resize the Explorer. To do this, click an edge or corner of the window, and then drag until it’s the size you want. Opening and closing folders The Explorer uses folders to organize editors.
• • • • • 2 • EXPLORING FACTORYTALK VIEW STUDIO From the Tools or Settings menu, select the editor you want to open. To do this Use this editor Runtime Security Set up runtime security accounts for FactoryTalk View, assign security codes to users and groups, and assign login (Settings menu) and logout macros. Assign security codes to FactoryTalk View commands and Runtime Secured Commands macros.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To do this Use this editor Create tags whose values are derived from other tags, or from functions. Derived Tags Create events, which are expressions that trigger FactoryTalk View commands or macros. Events Create macros to run series of FactoryTalk View commands. Macros Re-map the FactoryTalk View SE Client keyboard to run FactoryTalk View commands.
• • • • • 2 • EXPLORING FACTORYTALK VIEW STUDIO Creating components 2 • Placeholder To create a new component, use one of these methods: Drag the editor’s icon into the workspace. Right-click the editor’s icon, and then click New. Opening components To open a component, use one of these methods: Double-click the component. Drag the component into the workspace. Right-click the component, and then click Open.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Selected components are added to the Explorer, under the editor’s icon. To select several consecutive components, click the first component you want to select, press the Shift key, and then click the last component. To select several individual components, press the Ctrl key, and then click each component. Naming components When you name a component in FactoryTalk View Studio, the file name is created on disk automatically.
• • • • • 2 • EXPLORING FACTORYTALK VIEW STUDIO Avoiding names that conflict with commands or macros Deleting, removing, and renaming components In FactoryTalk View Studio, when you: Delete a component, the component and the corresponding physical file are deleted. Remove a component, the component is removed from the Explorer window, but the physical file is not deleted. Rename a component, the component and the physical file are both renamed.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Techniques for working in editors Many of the editors you will use to develop a FactoryTalk View application have similar features, that require similar information. Knowing about these features saves time. Gaining quick access to common operations Shortcut menus provide quick access to actions you perform frequently, in different environments. In the Explorer, everything in the tree hierarchy has a shortcut menu, except the folders.
Use the Command Wizard for assistance with selecting and building commands. Opening the Command Wizard To open the Command Wizard, use one of these methods: Click the Browse button beside a text box where a command is expected, for example, in the Press action text box for a button object, or in the Command Line. Double-click in a box where a command is expected or in the Macros editor. From the Edit menu, select Commands.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To print selections 1. Select the item you want to print, for example, a record in an editor’s spreadsheet. 2. From the File menu, select Print. 3. Under Print Range, select Selection. To print the entire contents of the window 1. From the File menu, click Print. 2. Under Print Range, click All. Selecting a printer You must install a printer before you can select it. FactoryTalk View can print to a network printer.
Planning an application 3 • Placeholder 3 This chapter describes: Understanding the process you are automating. Planning the layout of the network. Planning communications. Planning how to monitor and control alarms. Deciding when to use HMI tags. Designing a dependable control system. Setting up the run-time application. Designing a system that is easy to deploy and maintain. Integrating with other applications, and customizing the system.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Planning the network layout The layout of the network is particularly important to the design of a FactoryTalk View SE network distributed application. For information about installing the FactoryTalk View SE software, and about system requirements that might affect the network design, see the FactoryTalk View Site Edition Installation Guide.
• • • • • 3 • PLANNING AN APPLICATION Determining which computers you’ll need 3 • Placeholder You can develop and then test a network distributed application on a single computer. However, network application components are usually distributed over a network, on multiple computers. For information about FactoryTalk View SE system requirements and limits related to running network distributed application components, see the FactoryTalk View Site Edition Installation Guide.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The FactoryTalk Directory centralizes access to application resources and components, such as graphic displays and tags, for all FactoryTalk products participating in a control system. FactoryTalk Network Directory manages network distributed applications. All the computers in a given network application must point at the same FactoryTalk Network Directory.
FactoryTalk View Studio is also the tool for developing FactoryTalk View Machine Edition applications. For information about developing machine-level applications, see the FactoryTalk View Machine Edition User’s Guide. One or more operator workstations running FactoryTalk View SE Client The FactoryTalk View SE Client software provides a run-time environment for operators to interact with FactoryTalk View SE network distributed, network station, and local station applications.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For many purposes, you can access the values in controllers or devices directly, using a data server in the application. For some purposes, you will need to use tags from an HMI server’s tag database. To determine which method is most appropriate, you need to know what kinds of controllers or devices you are using, and how the application will communicate with the controllers or devices.
Advantages of using FactoryTalk Alarms and Events services There are advantages to using FactoryTalk Alarms and Events services for alarm monitoring and control, when compared with using traditional, HMI tag alarms. For example, FactoryTalk Alarms and Events provides a single, integrated set of alarm information, giving applications a system-wide view and record of alarm activity, enabled by alarm servers that support FactoryTalk services.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For details, see “Working with Tag Alarm and Event Servers” on page 12-21, and “Setting up FactoryTalk tag-based alarms” on page 12-23. Traditional HMI tag alarms In a FactoryTalk View SE application, you can also set up alarms for tags in a FactoryTalk View SE Server’s tag database. These alarms are called HMI tag alarms.
HMI tag alarm requirements for the application Before creating the HMI tags, plan how to organize them: Develop naming conventions for the HMI tags. Choose names that are familiar and logical to everyone. This makes troubleshooting easier. Group related HMI tags in ways that make most sense for the application. For example, group all similar devices, or group related areas of the plant floor. To group related HMI tags, you can create folders in the Tags editor.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Planning to use built-in system availability features A complete FactoryTalk system consists of all the networks, devices, and software applications you have deployed, to monitor and control your plant or process. Helping to ensure that the system can provide data in a secure and predictable fashion depends on a number of variables.
In addition, you can set up FactoryTalk View SE to send HMI tag alarm, data log, and activity log information to an ODBC-compliant database automatically. You can also set up an HMI server to buffer data locally if the database becomes unavailable. For information about: HMI tag alarm logging, see Chapter 11, Setting up HMI tag alarms. data logging, see Chapter 22, Setting up data logging. activity logging, see Chapter 15, Logging system activity.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Creating templates to ensure consistency To maintain consistency in the appearance of graphic displays in an application, present the same information and basic functions in the same places on each display. This makes it easier for users to find similar elements as they navigate from display to display. To ensure uniformity, develop displays with common elements that act as templates.
Use high-contrast color combinations, such as light text on dark-colored backgrounds. If you’re designing for a touch screen, place important buttons where they will not be blocked by a pop-up window. Users can’t press a covered button. Also ensure that buttons are large enough and spaced far enough apart for users to touch them easily, even when wearing work gloves. Ensure there is always a clear way to move between displays.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Designing a system that is easy to deploy and maintain FactoryTalk View SE includes tools and features that can help you create applications that are easier to use and maintain. For example, you can: Create global objects and distribute copies of the objects throughout the application. When you modify the global object, the changes are applied to all linked copies. For more information about global objects, see Chapter 16, Creating graphic displays.
Adding custom alarm events You can write alarm detection algorithms using PLC logic, and then create events in FactoryTalk View SE to respond to the algorithms. Validating operator input Use VBA logic to validate the operator’s input, for example, to ensure that the value an operator enters in a numeric input object falls within 10 percent of the value of another numeric input object.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 3–16
Setting up the FactoryTalk Directory 4 • Placeholder 4 This chapter describes: What the FactoryTalk Directory is. Using the FactoryTalk Directory in a networked system. How to specify the location of the FactoryTalk Network Directory server. What happens if the Network Directory server is unavailable.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE An automation and control system that uses FactoryTalk services and integrates FactoryTalk products and components is known as a FactoryTalk system. For an overview of FactoryTalk services, see “About FactoryTalk systems” on page 1-1. The following illustration shows how a FactoryTalk View SE application might be deployed in a networked FactoryTalk system, along with the Network Directory, RSLinx, and RSLogix software.
FactoryTalk Directory in a FactoryTalk View SE application In FactoryTalk View Studio, when you create or open an application, the FactoryTalk Directory that manages the application is represented at the top of the Explorer tree, as shown in the these illustrations: Network Directory (host computer) Application Local Directory (host computer) Application HMI server Area HMI server HMI project components and editors HMI project components and editors Areas FactoryTalk system settings FactoryTalk Tag Al
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If necessary, you can add one RSLinx Enterprise data server, or one FactoryTalk Tag Alarm and Event Server, which also must be installed locally. In a local station application, only OPC data servers can be installed on other computers. For more information, see Chapter 8, Working with local station applications.
Do not run FactoryTalk Directory, or any other application software, on the same computer as a Windows domain controller. After installing FactoryTalk View SE, and before you run FactoryTalk View Studio, the FactoryTalk View SE Client, or the FactoryTalk View SE Administration Console, you must use the FactoryTalk Directory Server Location Utility to specify: Localhost on the computer running the Network Directory server.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 5. Click OK. To specify the directory location on application computers 1. Select Start > All Programs > Rockwell Software > FactoryTalk Tools > Specify FactoryTalk Directory Location. 2. You are prompted to log on to FactoryTalk. Type your name and password, and then click OK.
• • • • • 4 • SETTING UP THE FACTORYTALK DIRECTORY 5. Click OK. 6. Repeat steps 1 to 5 on each computer that is to participate in the network distributed application. Setting up FactoryTalk Directory for local station applications For FactoryTalk View SE local station applications, you do not need to do anything to set up the Local Directory, as the location is set to localhost automatically, during installation of the software.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE (Unknown) means the connection status is temporarily unknown, for example, because the system is starting up and waiting to determine which server is active, or is unable to determine the current status. To check the status of the Network Directory server 1. Select Start > All Programs > Rockwell Software > FactoryTalk Tools > Specify FactoryTalk Directory Location. 2. You are prompted to log on to FactoryTalk.
Setting up security 5 • Placeholder 5 This chapter describes: What FactoryTalk Security services provide. Gaining initial access to a FactoryTalk system. Logging users on to and off from FactoryTalk View SE. Deciding how to secure a FactoryTalk View SE application. How to set up FactoryTalk accounts in FactoryTalk View SE. How to set up run-time security for HMI project components. Other ways to control run-time access to an application.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In a network distributed application, security services also check whether the user is allowed to perform authorized actions on the current computer. In addition, FactoryTalk Security services manage system-wide policies, such as how often users must change their passwords, or whether users can back up and restore applications. For more information about these policies, see page 5-27.
• • • • • 5 • SETTING UP SECURITY 2. In the Contents tab, open the book, Setting up FactoryTalk Security. 5 • Placeholder You can also gain access to the FactoryTalk Security Help, by clicking Help in dialog boxes used to set up security for FactoryTalk resources. Gaining initial access to a FactoryTalk system When you install FactoryTalk View SE, during installation of the FactoryTalk Services Platform, the Local Directory and the Network Directory are set up on the computer.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When you create a local or a network distributed or network station application, an All Users account is also added automatically to the Runtime Security list for the application. By default, the account is allowed all run-time security codes.
• • • • • 5 • SETTING UP SECURITY 5 • Placeholder Log on to the Network or the Local Directory. The current user is also the single sign-on user, if single sign-on is enabled. Click to change or log off the current user. In the illustration, the current Network Directory user is named administrator. If there was no current user, Not logged on to directory Network would be shown, the Logon date would be blank, and there would only be a Log On button in the Log On to FactoryTalk tool.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE After logging off the current user, from the File menu, you can click Log On to log on a different user. If single sign-on is enabled, changing the FactoryTalk View Studio user does not change the FactoryTalk Directory user. To change the current directory user, you must use the Log On to FactoryTalk tool. For details, see “Logging on to the FactoryTalk Directory” on page 5-4.
If single sign-on is enabled, changing the FactoryTalk View SE Client user does not change the FactoryTalk Directory user. To change the current directory user, you must use the Log On to FactoryTalk tool. For details, see “Logging on to the FactoryTalk Directory” on page 5-4. To log on a different user In the FactoryTalk View SE Client Login dialog box, type the user name and password of the user that wants to log on, and then click OK.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To change a password In the Change Password dialog box, type the current password followed by the new password (twice), and then click OK. Whether a FactoryTalk user needs to change passwords, and how often, is set up as a system security policy. For details, see the FactoryTalk Security Help.
Which user groups should be able to set up security for the application. For example, decide who is allowed to create or modify user accounts, or set up system-wide security policies. Which system-wide security policies are appropriate for the entire control system. For example, you might require users to change their passwords periodically, or force users to log on every time they start FactoryTalk View Studio or a FactoryTalk View SE Client.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To set up run-time security accounts for an application, from the Settings menu, select Runtime Security. You can also double-click the Runtime Security icon in the Explorer window. To assign security codes to FactoryTalk View commands and macros, click Runtime Secured Commands. In the Tags and Graphics editors, assign security codes to HMI tags, graphic displays, and OLE object verbs.
“Understanding inherited permissions” on page 5-33 “Performing secured tasks in FactoryTalk View SE” on page 5-35 For comprehensive information and setup instructions, see the FactoryTalk Security Help. Setting up FactoryTalk accounts in FactoryTalk View SE To secure a FactoryTalk user’s access to FactoryTalk View SE application components at run time, you must set up run-time security for the user by: Adding the user’s FactoryTalk account to the Runtime Security list.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To add users, or to view or modify security codes for the selected account, click Security Accounts. To add users and assign security codes to them 1. In the Runtime Security editor, click Security Accounts. Set up security codes by user or action. List of user groups with levels of access to securable HMI project components. To add FactoryTalk users or groups, click Add.
3. Click Add, select the user or group account to add, and then click OK. If you are setting up security for a network application, you must select a computer account with the user account, before you can click OK. 4. In the Runtime Security list, select the account you just added. 5. Select the Allow check box beside the FactoryTalk View Security Codes that you want to explicitly allow for the selected account.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The DisplayClientClose command has security code D. An HMI tag named BoilerTemp has security code E. This means that members of: The Supervisors group have full run-time access. The Operators group can open the Overview and Boiler graphic displays, and can write to the BoilerTemp tag. Members cannot run the DisplayClientClose command. The Visitors group can only open the Overview graphic display.
• • • • • 5 • SETTING UP SECURITY To remove the All Users account from the Runtime Security list 2. In the Runtime Security editor’s accounts list, select Security Accounts. 3. In the Security Settings dialog box, select the ALL USERS account, and then click Remove. Specifying login and logout macros You can assign a login and logout macro to any user or group account listed in the Runtime Security editor. The macros will run when the user (or users) log on to or off from the application at run time.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For more information about logging on and off at run time, see “Logging users on to and off from FactoryTalk View SE” on page 5-4. For information about creating macros, see Chapter 24, Adding logic and control. To assign a login or logout macro to a user account 1. In the Runtime Security editor, click the name of the user or group account you want to set up with a login or logout macro. 2. Enter a Login or Logout Macro name, and then click Accept.
Do not restrict access to the Login command. To assign security to commands and macros 1. In FactoryTalk View Studio, from the Settings menu, select Runtime Secured Commands. Type or browse for a command or macro. Select a security code. List of secured commands and macros 2. In the Command text box, enter the command or macro you want to secure. To find and select a command or macro, click Browse. 3. Provide an optional description, select a security code, and then click Accept.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Assigning security codes to graphic displays In the Graphics editor, you can set up security for graphic displays. You can assign a security code while you are creating a graphic display, or you can assign it later. Only users or groups assigned the graphic display’s security code will be able to open the display at run time. Users must have at least one security code assigned to them, to open graphic displays assigned an asterisk (* ) .
• • • • • 5 • SETTING UP SECURITY 2. Right-click the OLE object, select Animation > OLE Verb. 5 • Placeholder Select a security code. 3. In the OLE Verb tab, select the verb that you want to secure. 4. In the Security list, select a security code other than the asterisk (* ) . 5. Click Apply. Assigning security codes to HMI tags In the Tags editor, you can set up security for an HMI tag, to prevent users from writing to the tag.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Select a security code. 3. In the Security list, select a security code other than the asterisk (* ) . 4. Click Accept. Other ways to control run-time access to an application To further restrict access to a FactoryTalk View SE application at run time, you can prevent users from leaving the FactoryTalk View SE Client environment. You can also use the FactoryTalk View signature button in an application, to control selected user actions.
Prevent switching to other applications. To do this, in the FactoryTalk View 5 • Placeholder SE Client wizard, select the check box, Disable switch to other applications. For details, click Help in the FactoryTalk View SE Client wizard. • • • • • 5 • SETTING UP SECURITY Restrict access to the desktop, using the Desklock tool. To open Desklock, select Start > All Programs > Rockwell Software > FactoryTalk View > Tools > DeskLock. For details about using DeskLock, click Help within the tool.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE About the All Users account During FactoryTalk Services Platform installation, an account named All Users is created automatically, at the Local Directory and the Network Directory. This means that initially, after the FactoryTalk View SE software is installed, any FactoryTalk system user you create will be able to open, create, or modify an application in FactoryTalk View Studio.
A Windows Administrators group is also created and added automatically to the FactoryTalk Administrators group. This means Windows administrators on the computer can also set up security. For more information, see “Gaining initial access to a FactoryTalk system” on page 5-3. For information about setting up security permissions, see page 5-27. For details about adding users to a group, see the FactoryTalk Security Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using Windows-linked accounts When a Windows-linked user attempts to access system resources, FactoryTalk Directory relies on Windows to determine whether the user’s name and password are valid, and whether the account is active or locked out. Use this type of user or group account when the security needs of the Windows network match those of the control system.
• • • • • 5 • SETTING UP SECURITY Setting up user and computer accounts The following illustration shows where to find this folder in the Explorer window. To set up user accounts, right-click the User Groups or Users folder, and then click New. To create a new user group User group icon In the Users and Groups folder, right-click the User Groups folder, select New > User Group. For details about options in the New User Group dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To create a Windows-linked user Windows-linked user icon In the Users and Groups folder, right-click the Users folder, select New > WindowsLinked User. For details about options in the New Windows-Linked User dialog box, click Help. Windows-linked accounts refer to existing Windows accounts. If you want to create a new Windows user or group, you must do so in Windows. For details, see Windows help.
• • • • • 5 • SETTING UP SECURITY To create a new computer In the Computers and Groups folder, right-click the Computers folder, and then select New Computer. For details about options in the New Computer dialog box, click Help. To create a new computer group Computer group icon In the Computers and Groups folder, right-click the Computer Groups folder, and then select New Computer Group. For details about options in the New Computer Group dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE System policies In a FactoryTalk View SE application, you can set up the following system policies. Local station applications do not contain Health monitoring policies or Live Data policies because these apply only to network distributed applications.
• • • • • 5 • SETTING UP SECURITY Setting up security for FactoryTalk system resources In FactoryTalk View Studio, set up user access to these resources by right-clicking their folders or icons in the Explorer window, and then selecting Security. The following illustration shows which resources you can secure in this way: Set up access to FactoryTalk Directory. Set up access to the application. By default, the application and the System folder inherit permissions set up at the Directory.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the Security Settings dialog box In FactoryTalk View Studio, in the Explorer window, right-click the folder or icon for the resource you want to secure, and then select Security. Right-click the Network Directory icon and select Security, to set up access to the FactoryTalk Directory. The application and the System folder inherit permissions set up at the directory. Set up permissions by user or action.
2. Click Add, select the user or group of users to add, and then click OK. For a network application, you must associate the user or group of users with a computer, or group of computers, before you can click OK. The user or group of users you added should be selected (highlighted) in the Users list, in the Permissions tab. 3. To explicitly allow permission to perform an action, for the selected user or group of users, select the Allow check box beside the action.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For example, if a user belongs to one group that is allowed to delete applications, and belongs to another group that is explicitly denied that permission, then the user will not be allowed to delete applications. Alternatively, you can clear the Allow check box for an action, to implicitly deny permission to perform the action.
• • • • • 5 • SETTING UP SECURITY To add an action group In FactoryTalk View Studio, in the Explorer window, right-click the Action Groups folder, and then click New Action Group. For details about options in the New Action Group dialog box, click Help. Understanding inherited permissions Inheritance means that any security settings you define at the FactoryTalk Directory, extend to all system resources that the directory manages.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You are prompted to choose one of these options, instead of inheriting permissions: Copy the inherited permissions and make them explicit for the resource. Remove all inherited permission from the resource. Breaking the chain of inheritance applies to the resource, not to the user or group of users selected in the Security Settings dialog box.
Select the Allow check box beside the Configure Security action. Select the Deny check box beside the Delete action. Explicitly denying the Delete action on the application means that Supervisors are prevented from deleting applications. The changes are reflected in the Effective Permissions tab, as shown in the following illustration. Check mark means Configure Security is allowed. No check mark means Delete is denied.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Switching the Active and Secondary servers in a redundant pair, see page 14-19. Enabling or disabling, suppressing or unsuppressing, or acknowledging FactoryTalk alarms, see Chapter 12, Setting up FactoryTalk alarms. In the Security Settings dialog box, you might also see actions for other FactoryTalk products, for example, RSLinx Enterprise. For details about product-specific actions, see the product documentation.
In this component or tool You need these security permissions Delete areas, HMI servers, data servers, or Tag Alarm and Event Servers from an application. FactoryTalk View Studio Common Read Common List Children Common Write Common Delete Secure access to application resources, for example, the areas in an application. FactoryTalk View Studio Common Configure Security Create and administer FactoryTalk user and computer accounts.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To do this In this component or tool Back up and restore a local station application Application Manager You need these security permissions Common Read Common List Children Common Write Example – Using the Common actions to set up security for user groups in a FactoryTalk View SE network distributed application The following table shows how a system administrator might assign the Common actions to four groups of FactoryTalk View users—Administrator
For this group Run-time access (see Operators group, next), plus, members of this group can: Supervisors Modify existing applications. Modify HMI server properties. Load existing applications. However, members of this group cannot modify HMI server properties, nor view HMI project components. HMI servers show in the Explorer window as locked. Run applications in the FactoryTalk View SE Client. Write to tags at run time.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 5–40
Working with network distributed applications 6 • Placeholder 6 This chapter describes: What a FactoryTalk View Site Edition network distributed application is. Key network distributed application concepts. How to create a network distributed application. How to add areas and servers to a network distributed application. How to set up HMI server properties. How to monitor the status of an HMI server. How to delete HMI servers.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Application FactoryTalk Network Directory (host computer name) Area HMI server HMI project components and editors Areas FactoryTalk Tag Alarm and Event Server FactoryTalk system settings Network station applications are described in Chapter 7, Working with network station applications. Local station applications are described in Chapter 8, Working with local station applications.
In a network distributed application, you can use multiple RSLinx Enterprise and OPC data servers (including RSLinx Classic), running on different computers. You can also set up a redundant pair of host computers for each data server in the application. RSLinx Enterprise servers can be set up to subscribe to alarms detected in devices such as ControlLogix controllers. For more information, see Chapter 12, Setting up FactoryTalk alarms. Every vendor’s OPC data server is different.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Finding more information about FactoryTalk services This manual contains information about developing FactoryTalk View SE applications, including information about how FactoryTalk View uses FactoryTalk services. For additional, detailed information about FactoryTalk systems, services, concepts, and components, see the FactoryTalk Help. To open the FactoryTalk Help Select Start > All Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Help.
In FactoryTalk View Studio, you can create FactoryTalk user, group, and computer accounts, and then determine which accounts have access to resources such as the Network Directory, the application, and areas within the application. For an overview of FactoryTalk Security services, see Chapter 5, Setting up security. For details, see the FactoryTalk Security Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The HMI project is loaded by the HMI server, either when the first client connects to the server, or when the operating system initializes. For more information, see “Choosing how the server starts” on page 6-16. HMI clients HMI clients are software programs that obtain information from, or write information to HMI servers or data servers.
• • • • • 6 • WORKING WITH NETWORK DISTRIBUTED APPLICATIONS Absolute and relative references Absolute references point directly at a specific component, by referring to the component’s name and the area (or areas, in the case of nested areas) in which it is located.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Absolute reference syntax When using absolute references: Precede area names with a forward slash (/). Also use forward slashes to separate area names from other area names. Separate area names from component names with two colons (::).
Display /::Overview To create a relative reference to the display called Overview, in the area where the Display command is run, type: Display Overview Use the Command Wizard to build commands that take application components as parameters. The wizard supplies the correct syntax, based on the location of the component you select.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Language switching To make user-defined text strings in a FactoryTalk View SE application available in up to 40 different languages, set up language switching for the application. At run-time, multiple FactoryTalk View SE Clients connected to the same network distributed application can use different languages simultaneously. For more information, see Chapter 13, Setting up language switching.
Adding areas and servers to a network distributed application A network distributed application can consist of one or more areas, up to 10 HMI servers (one per area or subarea), and, if necessary, multiple data servers and FactoryTalk Tag Alarm and Event Servers. You add these elements to the application, after you create it. Adding and deleting areas You can add and delete areas in a network distributed application. You cannot copy areas. To add an area 1.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 2. In the Add HMI Server wizard, in the Select Operations window, click one of the following options: Create a new HMI server. When you create an HMI server, the server’s HMI project is created automatically. Copy an HMI server that already exists. After you have copied an HMI server, changes made to the original do not affect the copy, or vice versa.
• • • • • 6 • WORKING WITH NETWORK DISTRIBUTED APPLICATIONS Adding a data server To add an RSLinx Enterprise data server 1. In FactoryTalk View Studio, in the Explorer window, right-click the application root or right-click an area name, click Add New Server, and then click Rockwell Automation Device Server (RSLinx Enterprise). 2.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Adding servers for redundant operation To provide secondary application servers in the event that the primary servers goes out of service, set up redundant HMI servers and data servers. If you plan to deploy a network distributed application that uses more than two servers (or two pairs of redundant servers) and 20 clients, or if you would like architectural assistance, contact your local Rockwell Automation Sales office for architectural assistance.
Monitoring disk space on HMI servers After deploying a FactoryTalk View SE network distributed application, monitor disk space on computers running HMI servers to make sure that it does not fall below 500 MB. To monitor disk space 1. In the HMI server’s Events editor, create an event that uses the free_bytes function to return the number of free bytes available on the HMI server’s hard disk. 2. Create an HMI analog or digital alarm tag.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For details about options in the HMI Server Properties dialog box, click Help. Changing the name of the host computer In the General tab of the HMI Server Properties dialog box, the name of the computer running the HMI server is shown beside the text box Computer hosting the server. To change to the name of the host computer, a copy of the HMI server must exist on the computer that will be the new host.
An unlicensed HMI server can only be set up to start on demand. Starting the HMI server when the operating system initializes An HMI server set up to start when the operating system initializes is loaded when Windows starts up. You must use this option to set up redundancy for the HMI server. This startup option is also recommended for production, as it ensures that the HMI server will resume operating automatically if the host computer is restarted.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The settings you specify in the Redundancy tab for the primary HMI server are saved with the application, and are the same for both the primary and the secondary server. No further setup is required on the computer hosting the secondary server. For more information setting up redundant HMI servers, see Chapter 14, Setting up FactoryTalk system availability.
• • • • • 6 • WORKING WITH NETWORK DISTRIBUTED APPLICATIONS Running a macro when the HMI server goes into standby mode For example, when a primary HMI server recovers, the system switches from the active secondary back to the primary server. Once the primary server becomes active, the secondary switches to standby, and its On standby macro runs. Any FactoryTalk View macro can be used as the On standby macro.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Monitoring the status of an HMI server In FactoryTalk View Studio, in the Server Status dialog box, you can view the operational status of an HMI server to determine whether the server is ready to provide service, and to troubleshoot problems. For example, an HMI server in the Active state is fully loaded and ready to provide service to connected clients.
• • • • • 6 • WORKING WITH NETWORK DISTRIBUTED APPLICATIONS To delete an HMI server’s project files 2. In Windows Explorer, browse to the HMI Projects folder on the computer hosting the HMI server: (Windows 7 Professional, Windows Vista, Windows Server 2008) ..\Users\Public\Public Documents\RSView Enterprise\SE\HMI Projects (Windows XP, Windows Server 2003) ..\Documents and Settings\ All Users\Shared Documents\RSView Enterprise\SE\HMI Projects 3.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 3. Follow the instructions in the Application Manager to complete the delete operation. When you delete a network distributed application, the HMI servers and data servers set up in it are not deleted automatically. For details about: Deleting the HMI server files, see page 6-20. Removing a data server and deleting its cache files, see page 9-13.
Working with network station applications 7 • Placeholder 7 This chapter describes: What a FactoryTalk View Site Edition network station application is. Key network station application concepts. How to create a network station application. How to add areas and servers to a network station application. How to set up HMI server properties. How to monitor the status of an HMI server. How to delete HMI servers. How to rename and delete network station applications.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Network distributed applications are described in Chapter 6, Working with network distributed applications. Local station applications are described in Chapter 8, Working with local station applications.
• • • • • 7 • WORKING WITH NETWORK STATION APPLICATIONS About FactoryTalk systems These services, including FactoryTalk Directory, are installed with the FactoryTalk Services Platform when you install FactoryTalk View SE. For an overview of FactoryTalk services, see page 1-1. An automation and control system that uses FactoryTalk services, and integrates FactoryTalk products and components, is known as a FactoryTalk system.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE FactoryTalk Security FactoryTalk View SE network station applications can use FactoryTalk Security services to authenticate and authorize application users. During FactoryTalk View SE installation, Windows users with administrative privileges on the computer are set up with full, initial access to FactoryTalk View SE applications managed by a FactoryTalk Local or Network Directory on the same computer.
• • • • • 7 • WORKING WITH NETWORK STATION APPLICATIONS HMI projects HMI clients HMI clients are software programs that obtain information from, or write information to HMI servers or data servers. FactoryTalk View Studio, the FactoryTalk View SE Administration Console, and the FactoryTalk View SE Client are all HMI clients. Areas All FactoryTalk View applications have one system-defined area called the application root area, which has the same name as the application.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For example, a relative reference to a display named Detail is simply the display’s name: Detail. To set up a button in a graphic display to open the Detail display at run time, use Display Detail as the button’s press action.
• • • • • 7 • WORKING WITH NETWORK STATION APPLICATIONS 7 • Placeholder The application name can be up to 32 characters long. The application language can be any Windows language. 4. Type a name and description for the application, select an application language, and then click Create. In the Explorer window, the application icon and name are shown beneath the Network Directory icon.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When you delete an area, HMI servers and data servers located in the area are not deleted from disk. Adding an HMI server After you create a network station application, you must add one HMI server, either to the application’s root area, or to the area you have added. A network station application can contain one and only one HMI server. To add an HMI server 1.
• • • • • 7 • WORKING WITH NETWORK STATION APPLICATIONS Attach to an existing HMI server without making a copy of the HMI server. 3. Click Next, and then follow the instructions in the wizard to finish adding the server. The Add Controller Instruction Faceplates dialog box opens, if it’s set to show when you create a new HMI server. If you do not want to add faceplates, click Cancel to close the dialog box, without affecting server creation.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Adding a Tag Alarm and Event Server Optionally, you can add FactoryTalk Tag Alarm and Event Servers to an application. Tag Alarm and Event Servers use FactoryTalk Alarms and Events services to monitor and control alarms for tags in programmable controllers (PLC-5 or SLC 500) and other devices, that do not have built-in alarm detection. For more information about Tag Alarm and Event Servers, see Chapter 12, Setting up FactoryTalk alarms.
• • • • • 7 • WORKING WITH NETWORK STATION APPLICATIONS Setting up HMI server properties Select the components that will run when the HMI server starts up. Specify a macro to run when the HMI server shuts down. To open the HMI Server Properties dialog box In FactoryTalk View Studio or the SE Administration Console, in the Explorer window, right-click the HMI server icon, and then select Properties. For details about options in the HMI Server Properties dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To stop HMI server components manually 1. In FactoryTalk View Studio, open the network station application. 2. In the Explorer window, right-click the HMI server, and then select Properties. 3. In the Components tab, click Stop All Running Components. All the components running on the computer will stop running, including alarms, data log models, derived tag components, and event components.
• • • • • 7 • WORKING WITH NETWORK STATION APPLICATIONS To delete an HMI server 2. Start FactoryTalk View Studio, and then open the application that contains the HMI server you want to delete. 3. Right-click the HMI server, and then select Delete. This does not delete the HMI server’s project files. Deleting HMI server project files After you delete an HMI server from an application, if you want to delete the project files, you have to delete them separately. To delete an HMI server’s project files 1.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For details about options in the Application Manager, click Help. To rename a network station application 1. In the Application Manager, select Site Edition (Network Station), and then click Next. 2. Select Rename application, and then click Next. 3. Follow the instructions in the Application Manager to complete the rename operation. To delete a network station application 1.
The value in the HMI Server Computer column reflects the status of the HMI server added to that application. Status values include: Localhost - the HMI server is located on the current computer. computer name - the HMI server is located on the computer named (for example, NVCARBCBAS113). - no HMI server has been added to the application. To rehost an HMI server The applications restored from a .bak file need to be rehosted. For more information about restoring a .
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 5. Select the application containing the HMI server that you want to rehost, and click Open. 6. Right-click the HMI server, and select Properties. 7. In the Computer hosting the server field, type another computer name or click the browse button to search for and select one.
Working with local station applications 8 • Placeholder 8 This chapter describes: What a FactoryTalk View Site Edition local station application is. Key local station application concepts. How to create a local station application. How to add servers to a local station application. Setting up HMI server properties. Monitoring the status of an HMI server. Renaming, deleting, copying, and backing up local station applications.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Parts of a local station application A typical FactoryTalk View SE local station application consists of: The application root area. You cannot add areas to a local station application. An HMI server that provides FactoryTalk View components and services to application clients. A local station application can contain only one HMI server.
• • • • • 8 • WORKING WITH LOCAL STATION APPLICATIONS About FactoryTalk systems These services, including FactoryTalk Directory, are installed with the FactoryTalk Services Platform when you install FactoryTalk View SE. For an overview of FactoryTalk services, see page 1-1. An automation and control system that uses FactoryTalk services, and integrates FactoryTalk products and components, is known as a FactoryTalk system.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For more information, see Chapter 4, Setting up the FactoryTalk Directory. Do not run FactoryTalk Directory, or any other application software, on the same computer as a Windows domain controller. FactoryTalk Security The FactoryTalk Local Directory can use FactoryTalk Security services to authenticate and authorize users of FactoryTalk View SE local station applications.
• • • • • 8 • WORKING WITH LOCAL STATION APPLICATIONS HMI projects The HMI project is created with the HMI server, when you create a local station application. The HMI project is loaded by the HMI server. HMI clients HMI clients are software programs that obtain information from, or write information to HMI servers or data servers. FactoryTalk View Studio, the FactoryTalk View SE Administration Console, and the FactoryTalk View SE Client are all HMI clients.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 3. In the New/Open Site Edition (local station) Application dialog box, click the New tab. 4. Type a name and description for the application, select an application language, and then click Create. The Add Controller Instruction Faceplates dialog box opens, if it’s set to display when you create a new application. If you don’t want to add faceplates, click Cancel to close the dialog box, without affecting application creation.
• • • • • 8 • WORKING WITH LOCAL STATION APPLICATIONS To add an OPC data server 2. Set up properties, such as the name and location of the server, and whether to provide redundancy using a secondary server. For details, see the RSLinx Classic (or other OPC data server) product documentation. For additional information about setting up RSLinx and OPC data servers, see Chapter 9, Setting up communications.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For details about the options in the HMI Server Properties dialog box, click Help. Selecting startup and shutdown components In the Components tab of the HMI Server Properties dialog box, select the check box for each of the items you want to run when the HMI server runs, including: Which components will run when the HMI server starts. Which macro will run when the HMI server shuts down.
For more information about server states, see “Monitoring the status of application servers” on page 14-2. To open the Server Status dialog box In FactoryTalk View Studio, in the Explorer window, right-click the HMI server’s icon, and then select Server Status. For details about options in the Server Status dialog box, click Help. Renaming, deleting, and copying local station applications Use the Application Manager tool to rename, delete, or copy a local station application.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For local station applications, you can choose whether to delete the HMI server project associated with the application. For details, click Help within the Application Manager. For details about removing a data server and deleting its cache files, see page 9-13. To copy a local station application 1. In the Application Manager, select Site Edition (Local Station), and then click Next. 2. Select Copy application, and then click Next. 3.
Setting up communications 9 • Placeholder 9 This chapter describes: Data servers and FactoryTalk Live Data. Basic steps for setting up communications. Adding RSLinx Enterprise data servers to an application. Setting up communications in RSLinx Enterprise. Adding OPC (Open Platform Communications) data servers to an application. About data servers Data servers provide access to devices, making it possible to browse, read, and write values from FactoryTalk View applications.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Alias topics (multiple paths to the same device) are required. If RSLinx Classic runs on the same computer as FactoryTalk View SE Server, RSLinx Classic does not need an activation key. RSLinx Classic Gateway can run on any computer, but requires an activation key. About FactoryTalk Live Data FactoryTalk Live Data manages connections between data servers in an application and FactoryTalk Live Data clients such as FactoryTalk View SE clients.
OPC data servers can be located on different computers; however, it is not recommended. Communicating with multiple controllers RSLinx Enterprise is designed to serve multiple controllers across multiple networks simultaneously. RSLinx Enterprise recovers from program downloads, disconnects, power-offs, and online changes without affecting service to other controllers.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE RSLinx Classic and KEPServer Enterprise must be installed and setup separately. Add an OPC data server to the FactoryTalk View SE application, and then set up the server’s properties. For more information, see page 9-9. For information about installing RSLinx Enterprise or RSLinx Classic, see the FactoryTalk View Site Edition Installation Guide. 3.
• • • • • 9 • SETTING UP COMMUNICATIONS To add an RSLinx Enterprise data server 2. In the RSLinx Enterprise Properties dialog box, select options and provide information in each tab, as described in the sections that follow. 3. When you are finished, click OK. Setting up general properties In the General tab of the RSLinx Enterprise server’s Properties dialog box, type a name and description for the data server, and specify the name of the computer that will host the data server.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Description Type a description for the data server. For example, the description can consist of the server’s location, the name of a contact person or number to contact in case of failure, or version information. Computer hosting the RSLinx Enterprise server Type the name of the computer where the RSLinx Enterprise data server is running. To find and select a computer, click the Browse button.
• • • • • 9 • SETTING UP COMMUNICATIONS 9 • Placeholder In a local application, there is no Redundancy tab in the RSLinx Enterprise Server Properties dialog box. Local applications do not support data server redundancy.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up support for FactoryTalk Alarms and Events To enable an RSLinx Enterprise server to use FactoryTalk Alarms and Events services to receive and send alarms detected in Logix5000 controllers, in the Alarms and Events tab in RSLinx Enterprise Server Properties dialog box, select the check box, Enable alarm and event support. For more information, see Chapter 12, Setting up FactoryTalk alarms.
You can use these tabs to point RSLinx Enterprise at different networks or different hardware in case of failure. When specifying device shortcuts for a redundant server pair, be sure to use exactly the same shortcut names for the primary and secondary servers. If the names are not the same, tag references that use these shortcuts will not be able to obtain data reliably.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Name Type a name for the data server. This name will be shown in the Explorer window. The name cannot include dashes or hyphens (–). Description Type a description for the data server. For example, it can describe the server’s location, the name of a contact person or number to contact in case of failure, or version information. Computer that will run the OPC server Type the name of the computer where the OPC server is running.
• • • • • 9 • SETTING UP COMMUNICATIONS 9 • Placeholder For a local application, there is no Redundancy tab in the OPC Data Server Properties dialog box. Local applications do not support data server redundancy. Provide redundancy using a secondary server Select or clear this check box, depending on whether you want to set up redundancy for the data server. Computer running secondary server Type the name of the computer where the secondary data server is running.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Include extended information in the server cache file Select this check box to make available additional information about tags, for example, their data types, when you are not connected to the data server. To create a data server cache 1. To provide the list of tags, ensure that the OPC data server is running, and that the devices are connected. 2.
• • • • • 9 • SETTING UP COMMUNICATIONS Deleting an OPC data server To delete an OPC data server In FactoryTalk View Studio, in the Explorer window, right-click the OPC data server you want to delete, and then click Delete. 9–13 9 • Placeholder If an OPC data server is no longer required, you can delete it from the application. When you delete a data server, its cache files are also deleted.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 9–14
10 • Placeholder 10 Working with tags This chapter describes: Data server tags, HMI tags, and their attributes. Using tag data in a FactoryTalk View Site Edition application. How tag references work. Parts of the Tag Browser. Searching for and selecting tags. Browsing for offline tags. What HMI tags are. How to organize HMI tags. Parts of the HMI Tags editor. Creating, modifying, and deleting HMI tags. Selecting a data source for HMI tags.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using direct referencing to eliminate duplication For some uses in an application, using direct references to tags in devices, or to tags located in an OPC server’s database, offers advantages over using HMI tags. For example, use data server tags to add, modify, or delete tags in a device without having to duplicate the changes in the HMI server’s tag database.
To further define a range of values that can be written to a tag, you can specify a minimum and maximum value for FactoryTalk View SE numeric input objects. For details, see “Validating operator input” on page 17-24. Storing values in memory Create HMI memory tags to store values without the need for an attached or accessible device. For example, you can use memory tags to: Store the result of a calculation. Act as a temporary counter or index.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up data server tags To use data server tags, such as those found in Logix5000 and other OPC-compliant devices, you can refer directly to the tag’s location wherever the tag data is needed. These are the basic tasks involved in setting up data server tags for an application: 1. Create the tag in the OPC server or processor, or use an existing tag in the processor.
• • • • • 10 • WORKING WITH TAGS Specifying tag names where tag data is needed For example, you could create a graphic object that represents a vat on a production line, and then set up the object to show the level of the vat at run time. To do this, attach Fill animation to the object using a tag that is updated by a network device that monitors the vat level. At run time, the value of the tag will determine the fill level of the graphic object.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Each animation of an object (except the Touch animation) is counted as one connection. Each connection in the Connections property of an object that is linked to a tag is counted as one connection. Each pen configured in a Trend object is counted as one connection. Duplicate references of the same expression or tag connection are counted as the additional connections.
• • • • • 10 • WORKING WITH TAGS Relative references Extractor When a relative reference is used, FactoryTalk View assumes that the tag is located in the current area. Use relative references, for example, to re-use component names in a network distributed application for a plant that has identical production lines. The application might contain different areas to represent each production line; however, within each area, the same names would be used for application components such as graphic displays.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The home area in this application is called Waste Water. The home area contains two data servers, and an HMI server. The Tag Browser composes references to tags automatically, using correct syntax. If the tags you select are in the home area, the Tag Browser automatically uses relative references. If the tags are not in the home area, the Tag Browser uses absolute references.
• • • • • 10 • WORKING WITH TAGS 10 • Placeholder Root folder Area folder Folders pane Tags pane For a better view of the folders or tags, drag this bar to the left or the right. The tag you select is shown here. Viewing tags in folders In the Tag Browser, the Folders display on the left shows the application root folder, plus all the folders that contain tags, in the application’s HMI servers and data servers.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The folders list with server names hidden. The same folders list with server names shown. Finding tags in the home area To locate the tags in the home area, right-click a blank area of the folder pane, and then select Go To Home Area. The home area is selected automatically. For more information about the home area, see page 10-7.
) next to Find within. b. From the Find within dialog box, select the product component types to be searched, and then click OK to save the selection and close the dialog box. 4. If you are using a network distributed application, identify the HMI servers of the search in Find where (all servers are selected by default): a. Click the browse button ( ) next to Find where. b. From the Find where dialog box, select the specific HMI servers to be searched then click OK to close the Find where dialog box. 5.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 4. If you are using a network distributed application, identify the HMI servers of the search in Find Where (all servers are selected by default): a. Click the browse button ( ) next to Find where. b. From the Find where dialog box, select the specific HMI servers to be searched, and then click OK to close the Find where dialog box. 5. Click Search to show all the found items in a spreadsheet form. 6.
• • • • • 10 • WORKING WITH TAGS 10 • Placeholder The folder you select is shown under Selected Tag. Showing a tag’s properties To show the properties of a tag in the Tag Browser, right-click the tag, and then click Properties. The Tag Properties dialog box shows information about the tag. The properties are a snapshot, and do not update in real time. You cannot show the properties of multiple tags at the same time. By default, the Tag Browser does not show tag descriptions.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Filtering tags To show only tags whose names match a pattern, type the pattern in the Tag Filter list box, and then press Enter. Type the tag filter here. To clear the filter, click in the list.
This wildcard character Does this ? * Matches any single character. Matches any number of characters, including the backslash (\) character. To remove a tag filter In the Tag Browser, in the Tag Filter list, click . Creating, modifying, and importing HMI tags In the Tag Browser, you can also create new folders for HMI tags, create and modify the HMI tags, or import tags from a PLC or SLC database.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Browsing for offline tags from RSLinx Enterprise For each RSLinx Enterprise shortcut in an application, an Offline and Online folder is shown in the Tag Browser. Use the Offline folder to browse for tags in a PLC or Logix5000 program stored on disk. If the shortcut in RSLinx Enterprise has access to symbols, you can also browse for them in the Offline folder.
You can create HMI tags, or modify the properties of existing tags, in FactoryTalk View Studio, in the Tags editor. For more information, see “Creating, modifying, and deleting HMI tags” on page 10-21.In a network distributed application, you can create or modify HMI tags locally (on the same computer) or remotely (in FactoryTalk View Studio on a different computer). HMI tag types An HMI server’s tag database can contain the following types of tags. Tag Type of data stored Analog Range of values.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE An HMI tag with memory as its data source receives data internally, from FactoryTalk View SE. A memory tag can be used to store values internally. About retentive memory tags By default, the value of an HMI memory tag reverts to the initial value specified for the tag, whenever the HMI server containing the tag is shut down and restarted.
Grouping HMI tags in folders To organize tags, create folders in the Tags editor, for tags that are related to one another. When naming tags stored in a folder, to separate the folder name from the rest of the tag name, use a backslash (\). For example, the names of tags in a folder called Pump would start with Pump\. To further organize tags, you can also nest folders.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the Tags editor 1. In FactoryTalk View Studio, in the Explorer window, open the HMI tags folder. 2. Right-click the Tags icon, and then select Open. You can also double-click the Tags icon, or drag the icon into the FactoryTalk View Studio workspace. The main parts of the Tags editor are the form, the query box, the folder hierarchy, and the spreadsheet, as shown in the following illustration.
• • • • • 10 • WORKING WITH TAGS Form and spreadsheet In the lower part of the form, specify the data source (where the tag’s values will come from). To define alarm conditions for an analog or a digital tag, select the Alarm check box. To modify alarms once they have been defined, click the Alarm button. Query box Use the query box to select the tags you want to show in the spreadsheet. This means that you can modify tags in different folders without browsing the folder hierarchy.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To create an HMI tag 1. In FactoryTalk View Studio, in the Explorer window, open the HMI Tags folder, and then double-click the Tags icon. 2. In the Tags editor, if you want to add the new tag to a folder, double-click the folder in the folder hierarchy window (under the Search For field). 3. To clear the form and position the cursor in the Name box, click New in the form section of the editor.
• • • • • 10 • WORKING WITH TAGS To delete a tag 10 • Placeholder 1. In the Tags editor, find and select the tag you want to delete. 2. From the Edit menu, select Delete. You can also click the Delete button on the editor’s toolbar. Delete tags carefully. Once you click Delete, the tag is deleted. There is no confirmation message, and you cannot undo the deletion. Selecting a data source for an HMI tag The data source for an HMI tag can be an external device, or FactoryTalk View.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The access path is one of the following: For communications with an RSLinx OPC server, the access path is the name of a device shortcut or DDE/OPC topic in RSLinx. For communications with other OPC servers, the access path may be optional. For information about the syntax for the access path, see the OPC server documentation. The square brackets around the access path are part of the syntax. They do not indicate optional parameters.
• • • • • 10 • WORKING WITH TAGS Creating tags in a third-party application When you import tags, they can be merged with tags already in the HMI server’s tag database. This means that any tags in the database with the same name are updated with the new information. Creating tags in other FactoryTalk View editors Any editor that uses tags has access to the tag database. To create tags in the Tag Browser 1. To open the Tag Browser, click Tags or the Browse button, whichever is available. 2.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Opening the Import PLC Tags dialog box To open the Import PLC Tags dialog box, use one of these methods: DB Browser button in the Tags editor In the Tags editor, click the DB Browser button on the toolbar, or from the Edit menu, select Other Databases. In the Tag Browser, right-click a blank area of the Contents pane, and then select Import PLC Tags. Use the filter to search for a particular tag or set of tags.
• • • • • 10 • WORKING WITH TAGS Defining alarm conditions for HMI tags At run time, FactoryTalk View scans the tag values in the tag database and compares them to the limits set for these tags. If a tag value crosses a limit, an alarm is triggered. When an HMI tag is set up with an alarm, an X is shown in the Alm column of the Tags editor’s spreadsheet. When the tag is selected, the Alarm button in the editor’s form becomes available.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 10–28
11 • Placeholder 11 Setting up HMI tag alarms This chapter describes: What HMI tag alarms are. Key HMI tag alarms concepts. The steps involved in setting up HMI tag alarms. Setting up general alarm behavior. Setting up alarm conditions for HMI tags. What FactoryTalk View SE alarm events are. Setting up HMI tag alarm logging. Viewing HMI tag alarm log files. Suppressing alarm logging. Creating an HMI tag alarm summary. Using tag placeholders to specify alarms.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE HMI tag alarm features Using HMI tag alarms, you can: Monitor any analog or digital HMI tag for alarms, up to a maximum of 40,000 tags per HMI server (10,000 of these can be analog tags). Show the most recent 2,000 alarm transactions in an HMI tag alarm summary. Define up to eight different severity levels to distinguish alarms visually. Use system default messages or custom messages to describe HMI tag alarms.
• • • • • 11 • SETTING UP HMI TAG ALARMS For more information, see Chapter 12, Setting up FactoryTalk alarms. This section presents some of the common terms and concepts used to describe HMI tag alarm services, components, and data. Alarm thresholds for analog tags An HMI analog tag can trigger a number of alarms when its value crosses various levels, or thresholds. You can assign up to eight alarm thresholds, each with a different level of severity to indicate the alarm’s importance.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Example: Alarm thresholds Alarm severity levels Threshold Thresholds values Increasing Safe zone 5000 6 4000 5 3000 4 2000 3 1000 2 X X* X X 1 X* 4 O 8 X O 8 Decreasing 1 6 1 Time 4 Thresholds must be set up in ascending order In this example, a tag’s value changes as it monitors a motor’s revolutions per minute (rpm).
• • • • • 11 • SETTING UP HMI TAG ALARMS Variable thresholds To define a variable threshold, specify a tag name when setting up alarm thresholds for an analog tag. As the value of the specified tag changes, the threshold changes. Variable thresholds use more system resources than constant thresholds, due to the continuous scanning of threshold values, and the processing necessary to detect alarm faults.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The following illustration shows an increasing threshold of 4,000 rpm with a deadband value of 500 rpm. The rpm has to fall to 3,500 and then rise above 4,000 before it will trigger the alarm again. rpm In alarm again In alarm 5000 4000 X X Thresholds Deadband X 3500 3000 Out of alarm 2000 1000 0 Time n A deadband range can be absolute, as in the previous illustration, or it can be a percentage of the minimum or maximum range for a tag.
Create this type of digital alarm Only when a tag value changes from 0 to 1. Changes to On* Only when a tag value changes from 1 to 0. Changes to Off* 11 • Placeholder To trigger an alarm In the table, the asterisk ( * ) indicates change-of-state digital alarm types. These are considered out of alarm immediately after the change of state. Alarm severity HMI tag alarms can range in severity from 1 (most severe) to 8 (least severe), to indicate different levels of importance.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If you export alarm log data to an external ODBC database, you can view records in the database using third-party, ODBC-compliant applications, such as Microsoft Excel or Microsoft Visual Basic. To manually export the alarm log file to an ODBC database at run time, use the AlarmLogSendToODBC command. For details, see the FactoryTalk View Site Edition Help.
As new alarms occur, they are shown at the top of the list in the alarm summary. When the list is full and a new alarm is generated, the alarm at the bottom of the list (the oldest alarm) is acknowledged automatically by the system, and then dropped from the list. In the alarm log file, alarms acknowledged automatically by the system are identified by SysAk (system-acknowledged) in the TransType (transaction type) field.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Alarm system tags System tags that provide HMI tag alarm status information are created and updated on the HMI server. You can use these system tags wherever you can specify a tag name in FactoryTalk View SE. To display this alarm status information Use this system tag Of type The most recent, most severe alarm. If an alarm of an equal or higher severity occurs, it replaces the first alarm, whether or not the previous alarm has been acknowledged.
Acknowledging alarms To acknowledge HMI tag alarms, you can use any of these methods: Click Acknowledge or Acknowledge All in the HMI tag alarm summary. Use the FactoryTalk View command Acknowledge by itself, or with parameters to name a tag or group of tags. Use the FactoryTalk View command AcknowledgeAll. For details, see the FactoryTalk View Site Edition Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE One way to use this expression is to animate the visibility of a graphic object in a display. When the tag goes into alarm, the ALM_IN_ALARM expression is set to 1, making the object visible. This is an effective way to draw the operator’s attention to the alarm.
• • • • • 11 • SETTING UP HMI TAG ALARMS For example, the following expression checks whether any of a group of tags is in alarm: where alarm* represents all tags whose names begin with alarm. If one or more of these tags are in alarm, the expression result is 1. If all of the tags are out of alarm, the expression result is 0. If the wildcard pattern in an alarm expression matches a large number of tags, it could take more time to resolve the expression.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Switching handshaking on Handshaking is turned off by default. To switch handshaking on, you can: use the /H parameter with the AlarmOn command. use the HandshakeOn command. For information about FactoryTalk View SE handshake commands, see the FactoryTalk View Site Edition Help. Summary of steps for setting up HMI tag alarms Following are the tasks involved in setting up HMI tag alarms in a FactoryTalk View SE application.
• • • • • 11 • SETTING UP HMI TAG ALARMS Setting up general HMI tag alarm behavior Setup tab, specify general behavior for alarm monitoring and annunciation. Severities tab, set up logging and alarm behavior for individual severities. User Msgs tab, create custom alarm messages to use in place of the default system messages. For details about options in Alarm Setup editor tabs, click Help. To open the Alarm Setup editor 1.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE How the system behaves when alarms cross back over trigger thresholds. How often the system checks for new alarms. Where alarms are logged and printed when redundant HMI servers are in use. Alarm trigger thresholds An HMI tag alarm is triggered when the value of an analog tag crosses a specified alarm threshold.
• • • • • 11 • SETTING UP HMI TAG ALARMS 11 • Placeholder Alarm severities Alarm incidents Alarm or incident What is logged (to file, printer, or both) Severity 1 through 8 Out of alarm In Alarm messages. Out of Alarm messages (for any severity that has been set up to log In Alarm messages). Acknowledged messages (for any severity that has been set up to log In Alarm messages). All Fault messages. All Suppression messages.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To create a userdefault message, type the message in the appropriate box. You can create user messages for logging to a file or a printer. In the User Msgs tab of the Alarm Setup editor, you can define the content of: In Alarm messages, which are logged when an analog tag’s alarm threshold has been crossed, or when a digital tag has changed state. Out of Alarm messages, which are logged when a tag is no longer in alarm.
Is replaced with \L Alarm label specified in the Alarm Label field of the Analog Alarm and Digital Alarm editors. Name of the tag in alarm. Description of the tag in alarm. Time when the message is sent. Units specified in the Units field, in the Tags editor. Threshold value that was crossed. \N \S \T \U \V 11 • Placeholder This placeholder \C, \L, \U, and \V do not contain any information when used in alarm Acknowledged messages.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up alarm conditions for HMI tags In the Tags editor, for each analog and digital tag you want to monitor for alarms, use the Analog Alarm and Digital Alarm editors to specify conditions that will trigger an alarm. To open the Tags editor In FactoryTalk View Studio, in the Explorer window, open the HMI Tags folder, rightclick the Tags icon, and then click Open. To add an alarm to the selected tag, click the Alarm check box or button.
• • • • • 11 • SETTING UP HMI TAG ALARMS Setting up alarms for HMI analog tags 1. Set up the alarm threshold, and then choose the message to show when the threshold is crossed. 2. Set up the messages that are sent when a tag goes out of alarm, and when an operator acknowledges an alarm. 3. Set up advanced features, such as deadband and handshake. For details about options in the Analog Alarm editor, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE About FactoryTalk View SE alarm events You can customize and extend HMI tag alarm monitoring, by writing alarm-detection algorithms using PLC ladder logic, custom programs, or other appropriate tools. You can then add alarm events to the HMI tag alarm subsystem, to respond to the alarmdetection algorithms for annunciation, logging, printing, and display in alarm summaries.
You cannot specify thresholds for analog alarm events. All analog alarm events have a value of zero. You cannot specify alarm labels for event-based alarms. That is, you cannot use the IntoAlarm and OutOfAlarm labels for HMI digital tag alarms, or the threshold labels for HMI analog tag alarms. You cannot suppress event-based alarms. Alarm events have no acknowledge and handshake bits. You cannot use the Identify feature with event-based alarms, to run a command, macro, or custom program.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE About alarm event types Use the AlarmEvent command to create into-alarm and out-of-alarm events. Multiple into-alarm events can be processed for the same event name before an out-of-alarm event is received. Use the InAndOutOfAlarm event type for change-of-state alarms. An out-of-alarm event is ignored if no into-alarm events preceded it. Setting up HMI tag alarm logging Use the HMI Tag Alarm Log Setup tool to specify: Where to store alarm log files.
• • • • • 11 • SETTING UP HMI TAG ALARMS 11 • Placeholder For more information about HMI tag alarm log files, see: “Adding remarks to the alarm log file at run time” on page 11-30. “Viewing HMI tag alarm log files” on page 11-29. Specifying where log files are stored or printed In the Logging tab of the HMI Tag Alarm Log Setup tool, you can specify where alarm log files are stored on the computer. The default location is: ..
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You can set up file management to delete log files after a specified period, or once a specified number of files have been created. Files scheduled to be deleted are deleted whenever a new file is created. For example, if you set up logging to start a new file daily, and to delete the oldest files every third day, the system will save alarm log files for the current day and for the three previous days.
To export the contents of the alarm log files to an ODBC-compliant database on demand, create a graphic display containing a button that uses the AlarmLogSendToODBC command as its press action. When the operator presses the button at run time, the contents of the alarm log file will be exported to the ODBC database. The AlarmLogSendToODBC command exports only the records added to the alarm log files since the last export.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE This column Contains SQL data type Length AlarmType The number FactoryTalk View assigns to the transaction type: SQL_SMALLINT, or SQL_INTEGER 1 SQL_VARCHAR, or SQL_CHAR SQL_VARCHAR, or SQL_CHAR SQL_DOUBLE, or SQL_INTEGER, or SQL_SMALLINT SQL_VARCHAR, or SQL_CHAR SQL_DOUBLE, or SQL_FLOAT 80 SrcArea TagName TagValue TagType 0 for SysAk (System Acknowledged) 1 for InAlm (In Alarm) 2 for OutAlm (Out of Alarm) 3 for InFlt (In Fault) 4 for OutFt (
Contains SQL data type Length SrcComputr The name of the computer that initiated the command or action that caused the alarm. The name of the user (including domain name, if there is one) that initiated the alarm transaction. If the transaction was initiated by an HMI server, the user is NT Authority\System.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You must include the quotation marks, because there are spaces in the parameter. At run time, due to operating system rules, the alarm log viewer might open behind the FactoryTalk View SE Client window. If you are unaware of this, and try to open the viewer again, another instance will open. This could result in multiple viewers being open at the same time.
You cannot show alarm log remarks in HMI tag alarm summaries. To prompt the operator to type a remark for the alarm log file, use the /P parameter with the AlarmLogRemark command. At run time, only one Alarm Log Remark dialog box opens at a time, and the operator must respond to the dialog box before the next one is opened. For details about using AlarmLogRemark, see the FactoryTalk View Site Edition Help. Alarm logging must be turned on before you can use the AlarmLogRemark command.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To turn off suppression for a tag, click the tag name, and then click Suppress Off. Click All Off to turn off suppression for all tags in the list. For more information about the Suppressed List, click Help. You cannot open the Suppressed List at run time, from a FactoryTalk View SE Client. Suppressing alarm printing To suppress alarm printing for all HMI tags, use the AlarmPrintOff command. To reset alarm printing, use the AlarmPrintOn command.
Creating an HMI tag alarm summary The HMI tag alarm summary is a table that shows the active alarms recorded in an HMI server (or servers). At run time, operators can use alarm summaries in FactoryTalk View graphic displays to view and interact with alarms. You can create a new alarm summary object in a display, or use the pre-built alarm summary available in the HMI Tag Alarm Information graphic library. To create a new HMI tag alarm summary object 1.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The parts of an HMI tag alarm summary A new HMI tag alarm summary object in a graphic display looks like this: Use commands on the Insert menu to insert headings in the header area. Use the mouse to move the split bar up and down. Alarm information is shown in the alarm summary’s body at run time. Use commands on the Format menu to specify the position of the button bar, and the buttons it contains.
11 • Placeholder When you click an item on the Insert menu, two boxes appear in the alarm summary. Drag the boxes to position them. Drag the handles on the boxes change the width of the column. In local applications, the Insert menu does not contain an Area Name heading. Choosing fonts The header and body fonts in an HMI tag alarm summary can be different. For example, you might choose a larger font for the header and a smaller font for the body.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Out of Alarm and Fault State messages. For details about options in the Colors dialog box, click Help. Selecting buttons In the Buttons dialog box, you can specify where in the HMI tag alarm summary the button bar will be positioned, and which buttons it will contain. For descriptions of the individual buttons, see the FactoryTalk View Site Edition Help. To select the buttons for an HMI tag alarm summary 1.
• • • • • 11 • SETTING UP HMI TAG ALARMS To change the button text 11 • Placeholder 1. Double-click the button you want to change. 2. Type new text for the button. Choosing the data to show You can set up sorting and filters for an HMI tag alarm summary, to determine how and what alarm information is shown at run time. For network applications, you can also show full tag names in the alarm summary.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To collect all alarm information for the current area, type: * To collect alarms from specific areas for tag names that match a pattern, you can type: /Powertrain::Coolant* /Press::FlowValve* To collect alarms from more than one HMI server, you can type: /Powertrain::* /Press::* You can also use the Areas and Tags buttons to browse for area or tag names, instead of typing them.
11 • Placeholder Examples: Using tag placeholders to specify areas and tags • • • • • 11 • SETTING UP HMI TAG ALARMS In these examples, the tag placeholder #1 is used in various ways.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Appending Execute command parameters Parameters are appended to the Execute command in the same order they are listed in the Execute Command dialog box. You can substitute parameters into any position within a command by passing the parameters to a macro. For details about using parameters with macros, see “Specifying parameters in a macro” on page 24-14.
• • • • • 11 • SETTING UP HMI TAG ALARMS 11 • Placeholder At run time: The /P parameter for the AlarmLogRemark command shows a prompt for the operator, to enter a remark. The /T parameter for the AlarmLogRemark command logs a string in the Tagname column of the alarm log file. The Tag name parameter for the Execute command records the name of the tag highlighted in the alarm summary, in the Tagname column of the alarm log file.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using the Identify button to run commands or programs Use the Identify button to specify a command, macro or custom program that the operator can run when an HMI tag is in alarm, to provide additional information about the alarm. For example, use the Identify button to run the Display command, to open a display that contains instructions about how to handle a motor that is running too fast.
• • • • • 11 • SETTING UP HMI TAG ALARMS Ways to stop HMI tag alarm monitoring In the Graphics editor, create a button object with AlarmOff as the press action. Alarm monitoring will stop when the button is pressed. In the Graphics editor, attach Touch animation to a Graphic object, with AlarmOff as the action. Alarm monitoring will stop when the object is touched. In the Events editor, type the AlarmOff command in the Action box for an event.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 11–44
12 • Placeholder 12 Setting up FactoryTalk alarms This chapter describes: What FactoryTalk Alarms and Events is. Key FactoryTalk alarm concepts. The basic steps involved in setting up FactoryTalk alarms. Setting up system-wide alarm and event policies. Working with Rockwell Automation Device Servers. Working with Tag Alarm and Event Servers. Setting up FactoryTalk tag-based alarms. Setting up alarm and event history logging. Setting up alarm and event displays.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The choices you make will depend on factors such as the design of your application, the processes you need to monitor for alarms, the types of devices used in the application, and whether you want to build alarm detection into those devices.
Using HMI tag alarms Time stamps are applied in the controller. Time stamps are applied on the HMI server computer. This makes time stamps more accurate. Also, the same time stamp is delivered to multiple servers and clients. 12 • Placeholder Using device-based alarms To ensure that time stamps are accurate and consistent, clocks at server and client computers must always be synchronized.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For more information, see “Working with Rockwell Automation Device Servers” on page 12-18. RSLogix 5000 version 16 or later, is required to program alarm instructions into a Logix5000 controller. For a complete list of controllers in the Logix5000 family, that support FactoryTalk Alarms and Events services, see the FactoryTalk Alarms and Events Help.
This section provides an overview of key FactoryTalk Alarms and Events concepts, and describes some of the basic tasks involved in setting up FactoryTalk alarms in a FactoryTalk View SE application. For example, this manual contains basic information about: Setting up Rockwell Automation Device Servers (RSLinx Enterprise), so that FactoryTalk View SE Clients can receive FactoryTalk device-based alarm information.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the System Configuration Guide, in FactoryTalk View Studio, from the Help menu, select Online Books > FactoryTalk Alarms and Events System Configuration Guide. Key FactoryTalk Alarms and Events concepts This section presents some of the common terms and concepts used to describe FactoryTalk Alarms and Events services, components, and data.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS For information about setting up alarm servers in a FactoryTalk View SE application, see: “Working with Rockwell Automation Device Servers” on page 12-18. “Working with Tag Alarm and Event Servers” on page 12-21. 12 • Placeholder Level alarms A level alarm compares an analog value against predefined limits (also called thresholds) and triggers an alarm when a limit is exceeded. For information about setting up tag-based level alarms, see page 12-24.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In this example, a tag’s value changes as it monitors a motor’s revolutions per minute (rpm). An X in the illustration shows when the alarm condition goes into alarm, and an O shows when the alarm condition returns to normal. With the given limit settings, the motor must run between 3000 rpm and 4000 rpm (the safe zone), otherwise, an alarm will be triggered.
rpm In alarm again In alarm High High limit 5000 High limit 4000 X X Deadband O 3500 Low limit 3000 Return to normal 2000 Low Low limit 1000 0 Time n A deadband range can only be an absolute (constant) value. If a buffer is not required, the deadband must be set up as zero. With a deadband of zero, alarms will be triggered as soon as the tag value crosses any of its limits. For information about how deadbands work with deviation alarms, see the FactoryTalk Alarms and Events Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In the following illustration, an X shows when the tag goes into alarm, and an O shows when the tag returns to normal. Deviation-High Limit X O XO Constant Target Deviation-Low Limit X O X For information about setting up tag-based deviation alarms, see page 12-26. Digital alarms A digital alarm monitors the value of a tag or input for either of these alarm conditions: the value is equal to zero, or the value is not equal to zero.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS Alarm and event summary Use the alarm and event summary to view, acknowledge, suppress, and disable the alarms on display. The alarm and event summary also provides a detail view of selected alarms. An alarm and event summary can display alarms from more than one area and alarm server in a FactoryTalk View SE application. For information about setting up an alarm and event summary, see page 12-33.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Alarm priorities can be defined in an alarm server (Rockwell Automation Device Server or Tag Alarm and Event Server), or in the FactoryTalk Directory. If priority values are not defined in an alarm server, then the following system-wide settings are in effect for all alarm servers in the FactoryTalk Directory.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS 12 • Placeholder Each time you create a new alarm class, it is added to the list. In the previous illustration, for example, Pump temperature will be listed with Equipment running, the next time you create an alarm. For more information about alarm classes, see the FactoryTalk Alarms and Events Help. Alarm states Alarm states indicate the current status of an alarm.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE After you set up an alarm to show as a tag, you can select the alarm in the Tag Browser, and then select the alarm tags you want to use. For more information, see “Using tags to interact with alarms or obtain their status” on page 12-51. Alarm status tags Alarm status tags let you use handshaking to keep alarm state changes synchronized with a controller (PLC-5 or SLC 500).
Diagnostic messages inform operators of system activity, in the form of information, error, and warning messages. FactoryTalk Diagnostics routes these messages to a Diagnostics Local Log, the Diagnostics List, and to a central ODBC log, if one is available. You can look at diagnostic messages in the Diagnostics Viewer. Historical alarm and event messages record all the alarm activity that occurs at an alarm server at run time.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For information, see “Working with Rockwell Automation Device Servers” on page 12-18. 4. If the application is to use tag-based alarms, add one or more Tag Alarm and Event Servers. For information, see “Working with Tag Alarm and Event Servers” on page 12-21. 5. In the Alarm and Event Setup editor, create digital, level, and deviation alarm conditions, for the tags you want to monitor for alarms.
To modify the severity range for the alarm priorities, change the values in the Low boxes only. Priorities defined at an alarm server override the system-wide settings held at the FactoryTalk Directory. For details about options in the System Settings Properties dialog box, click Help. To modify severity settings for system events 1. In FactoryTalk View Studio, in the Explorer window, expand the System, Policies, System Policies, and FactoryTalk Alarms and Events folders. 2. Double-click Severity Settings.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Securing access to FactoryTalk alarm information For FactoryTalk products like FactoryTalk View SE, the FactoryTalk Directory stores information about which users are allowed access to the parts of a control system. You can secure access to alarms, and to alarm information in an application, by determining which users are allowed to perform alarm-related actions, or gain access to areas that contain alarm servers.
1. In the FactoryTalk View Studio, in the Explorer window, right-click the application name or an area, select Add New Server > Rockwell Automation Device Server (RSLinx Enterprise). 2. Provide a name and an optional description, and then specify the name of the computer hosting RSLinx Enterprise. Setting up support for FactoryTalk Alarms and Events After you add an RSLinx Enterprise server to an application, you must set up the server to support FactoryTalk Alarms and Events.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To enable alarm and event support for this device server, select this check box. Once you enable alarm and event support, you can set up serverassigned priorities, and enable alarm and event history logging on the server’s host computer. To enable history logging, select this check box, and then select an existing database definition.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS To open the Communication Setup editor In FactoryTalk View Studio, in the Explorer window, expand the RSLinx Enterprise server icon, and then double-click Communication Setup. This device shortcut... ...is set up to support Alarms and Events. For details about options in the Communication Setup editor, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up alarm priorities and history logging To enable alarm and event history logging on the computer running the Tag Alarm and Event Server, select the check box, Enable history, as shown in the next illustration. To override priority settings at the FactoryTalk Directory, select this check box. To modify the severity range for a priority, change the value in the Low boxes.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS Setting up FactoryTalk tag-based alarms Older Devices (Plc-5 Or Slc 500) That Don’t Support Built-in Alarm Detection Third-party devices communicating through OPC data servers HMI tags in an HMI server’s tag database. If you prefer not to set up built-in alarm detection, you can also set up tag-based alarms for Logix5000 controllers that do support device-based alarms.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Name the alarm and specify the tag being monitored. Specify the alarm condition and the corresponding severity value. Select to make the alarm latched. Select to require acknowledgment. Select to expose the alarm as a tag. Specify a minimum alarm duration. Create or select an alarm message. Associate tags with the alarm. Select a class for the alarm. Associate a FactoryTalk View command with the alarm. 2.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS To create a new level alarm Name the alarm and specify the tag being monitored. Define alarm limits and corresponding severity values. Specify a minimum alarm duration. Define a deadband value ( 0 means no buffer is required). Select to require acknowledgment. Select to expose the alarm as a tag. Select a class for the alarm. Associate a FactoryTalk View command with the alarm. 2.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Creating tag-based deviation alarms In the Deviation tab of the Alarm and Event Setup editor, you can view all the deviation alarms set up for this Tag Alarm and Event Server, create a new deviation alarm, modify or delete an existing deviation alarm, and refresh the list of deviation alarms. To create a new deviation alarm 1. In the Alarm and Events Setup editor, click the Deviation tab, and then click New on the editor’s toolbar.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS For details options in the Deviation Alarm Properties dialog box, click Help. The All Alarms tab of the Alarm and Event Setup editor shows all the digital, level, and deviation alarms set up for this Tag Alarm and Event Server. The properties shown for each alarm can include the alarm name, input tag, condition, and severity, and whether acknowledgment is required for the alarm. For details, click Help in the All Alarms tab.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For example, if an Acknowledged status tag is specified for an alarm, when an operator acknowledges the alarm, the status tag is set to 1. For digital, level, and deviation alarms, you can assign tags to the Disabled, Suppressed, In Alarm, and Acknowledged states. For level alarms, you can assign different In Alarm and Acknowledged status tags, for each alarm level (High High, High, Low, or Low Low). Status tags provide alarm state information.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS 12 • Placeholder Type the message text in this box. Select a variable to insert in the alarm message. Click to insert the selected variable, where the cursor is positioned. Message identifier For details about options in the Alarm Message Editor, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using tag placeholders in alarm messages Tag placeholders are another type of variable you can add to an alarm message, to include specific values in the message at run time. In the Alarm Message Editor, in the Variable list, select up to four tag placeholders (Tag1, Tag2, Tag3, Tag4) to add to an alarm message. Then, specify the tag to associate with the placeholder, in the Alarm Properties dialog boxes where the message is used.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS Setting up alarm and event history logging The Alarm and Event Historian software, which is installed with FactoryTalk Alarms and Events, logs alarm information to the databases set up to store logged data. It also manages connections and data buffering between alarm servers and their databases. FactoryTalk Alarms and Events also generates audit and diagnostic messages.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You specify the database definition an alarm server will use, in the server’s Properties dialog box. For more information, “Enabling alarm and event history logging,” next. To create an alarm and event log database definition 1. In FactoryTalk View Studio, in the Explorer window, expand the System and Connections folders. 2. Right-click the Databases folder, and then select New Database.
Use the alarm and event log viewer to view, sort, filter, and print historical alarm information. For information about the alarm and event log viewer, see page 12-49. Use the alarm status explorer to view alarm sources, suppress or unsuppress, and enable or disable alarms. For information about the alarm status explorer, see page 12-44. For detailed setup instructions, see the FactoryTalk Alarms and Events Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You can move and resize the Alarm and Event Summary Design View object, as needed. To set up properties, double-click the object (or right-click, and then click Properties). Following is an overview of alarm and event summary properties. For details about options in the Alarm and Event Summary Properties dialog box, click Help.
Create filters based on what you want to include in the alarm and event summary, not what you want to exclude. Anything you don’t specify in the filter will not be shown at run time. In the Sort tab, specify which criteria will be used to sort information in the alarm and event summary, and in what order (ascending or descending). For information about filtering and sorting information in an alarm an event summary at run time, see “Using an alarm summary to monitor and respond to alarms” on page 12-38.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 2. To create a new graphic display, expand the Graphics folder, right-click Displays, and then select New. 3. In the Graphics editor, select Objects > Alarm and Event > Banner. You can also click the alarm and event banner tool on the Graphic editor’s toolbar. 4. Drag the alarm and event banner tool on the graphic display, to the desired size and shape, and then release the mouse.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS Choosing colors, sound, and blink styles for the alarm states You can also select whether alarm messages blink in the alarm and event banner, or sound an alarm bell, and at what rate. Use the Sample column to preview your selections. To test blink and audible notification rates, click Test Rates. Determining run-time behavior and appearance In the Common tab, set up the size and position of the alarm and event banner, and give the object a name.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For example, to let an operator continuously monitor the most serious alarms in an application, dock an alarm banner display to the top or bottom of the client window. Example: Docking an alarm banner when the FactoryTalk View SE Client starts up To dock an alarm banner display to the bottom edge of the FactoryTalk View SE Client window when the client starts up, follow these steps: 1.
You can also use alarm tags to suppress, unsuppress, enable, and disable alarms. For more information, see “Using tags to interact with alarms or obtain their status” on page 12-51. The parts of an alarm and event summary The following illustration shows an alarm and event summary at run time. Alarm and event summary toolbar Alarm list and column headings Select an alarm filter. In the status bar, view the number of alarms in the list, and how entries are filtered and sorted.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE An optional details pane, that shows the attributes of the currently selected alarm. A shortcut menu, and an optional toolbar, for alarm-related operations. The following sections describe some of the ways you can use an alarm and event summary at run time. For details, see the FactoryTalk Alarms and Events Help. Filtering and sorting information at run time An operator can filter and sort the information shown in the alarm list at run time.
All alarms, including those that aren’t visible in the current page of the alarm list. For details about acknowledging alarms, see the FactoryTalk Alarms and Events Help. Most alarms are configured to require acknowledgment. If you want specific alarms to always be in an acknowledged state, in the Alarm and Event Setup editor for these alarms, clear the check box Acknowledge required.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To reset a latched alarm 1. In the alarm and event summary, select one or more alarms to reset, and then click the toolbar button Reset selected alarm. Reset selected alarm 2. In the Reset Alarm dialog box, type an optional comment, and then click Reset. The comment is recorded with the reset alarms, in the alarm and event log.
Shelve or unshelve an alarm Shelving an alarm temporarily suppresses it. When shelving, the operator specifies a duration for the alarm to remain shelved. The alarm is automatically unshelved when the duration period times out. A shelved alarm is shown in the Alarm and Event Summary or Alarm Status Explorer. However, a shelved alarm is not shown in the Alarm and Event Banner.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To unshelve an alarm: 1. In the Alarm and Event Summary window, right-click an alarm, and then from the context menu, select Alarm Status. 2. In the Alarm Status Explorer window, select the alarm or alarms you want to unshelve, and then click the Unshelve selected alarm button on the toolbar. Unshelve selected alarm In the Unshelve Alarm dialog box, enter a comment to explain why the alarm is being unshelved and then click Unshelve.
3. In the Graphics editor, select Objects > Alarm and Event > Status Explorer. You can also click the alarm status explorer tool, on the Graphic editor’s toolbar. 4. Drag the alarm status explorer tool on the graphic display to the desired size and shape, and then release the mouse. You can move and resize the alarm status explorer object, as needed. 5. To set up properties, right-click the object, and then click Properties.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE An optional tree view of the application, and the areas that contain alarm sources. A status bar, that provides information about the contents of the alarm status explorer, such as the number of alarms in the selected alarm source. A shortcut menu, and an optional toolbar, for performing common operations. For details about using an alarm status explorer at run time, see the FactoryTalk Alarms and Events Help.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS 12 • Placeholder Alarm condition details vary, depending on the type of alarm. For a level alarm, for example, details are listed for each alarm level (High High, High, Low, and Low Low). For details about options in the Alarm Details dialog box, click Help. You can also view alarm details from an alarm and event summary. Unsuppressing and suppressing alarms Use the alarm status explorer to suppress and unsuppress alarms.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To check when, why, and by whom the alarm was suppressed, right-click the alarm, and then select View Alarm Details. For more information about the Alarm Details dialog box, see page 12-46. To unsuppress an alarm 1. In the alarm status explorer, select one or more suppressed alarms, and then click the toolbar button, Unsuppress selected alarm. Unsuppress selected alarm 2.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS 2. In the Disable Alarm dialog box, type an optional comment, and then click Disable. The Alarm and Event Log Viewer shows the contents of alarm and event history logs. When you create an alarm and event log viewer, you select which local or remote database to query, from the list of database definitions held in the FactoryTalk Directory. To create an alarm and event log viewer 1.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Select an alarm filter. Alarm and event log viewer toolbar In the status bar, view the number of events in the list, how the events are filtered, and which database is being queried. 12–50 Event list and column headings View details for the selected event. Drag to see more of the event list, or more details.
• • • • • 12 • SETTING UP FACTORYTALK ALARMS Refreshing the event list Filtering information at run time To filter information in the event list, an operator can do one of the following: Select from a predefined list of filters, set up for the alarm and event log viewer at design time. Clear the current filter. This refreshes the event list, to show all the alarm data stored in the database being queried.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Level_Alm1 is a tagbased alarm definition exposed as a tag. When you select the alarm in the Tag Browser, its alarm tags become visible in the right-hand window. You can use the Oper* tags to let an operator respond to instances of the alarm at run time.
In the Press action box, type Optionally, run a command or macro as the release action, to notify the operator’s supervisor when the alarm is acknowledged. At run time, when the High High Alarm object becomes visible, the operator can press the object to acknowledge the alarm. The object will remain visible until the alarm returns to normal. When that happens, the HHInAlarm status tag is reset to 0, making the High High Alarm text object invisible.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If any of the alarms specified has the state In Alarm and Acknowledged, the expression result is an integer, from 1 to 1000. If none of the alarms has the state In Alarm and Acknowledged, the expression result is 0.
If any of the alarms has the state In Alarm and Unacknowledged, the expression result is an integer from 1 to the total number alarms specified. If none of the alarms is In Alarm and Unacknowledged, the expression result is 0.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE where AlarmName indicates the name of the alarm. In a relative reference, the colons ( : ) preceding the alarm name are optional. For example, MixingTank1 is a valid relative reference to an alarm named MixingTank1. For more information about using absolute and relative references in FactoryTalk View SE applications, see page 6-7.
For example, a device-based alarm function is not counted, if the corresponding alarm is deleted from the Logix5000 controller, or if the RSLinx Enterprise alarm server: Loses its connection to the Logix5000 controller that is detecting alarms. Begins or is in the process of downloading a program. Switches from run to test program mode. Experiences a major or non-recoverable program fault. Cannot subscribe to all of the alarms at the Logix5000 controller.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For details about controller status alarms and the conditions that cause them, see the RSLinx Enterprise Help. Importing and exporting alarms Tag-based alarms and alarm messages can be exported from and imported into a Tag Alarm and Event Server. For example, you might export and import alarms and messages to: Move or copy alarms from one Tag Alarm and Event Server to another.
3. To complete the import operation, follow the instructions on the screen. For details about options in the Alarm Import and Export Wizard, click Help. About import and export formats FactoryTalk Alarms and Events supports Microsoft Excel Workbook (.xls) and XML (.xml) import and export formats. Use Microsoft Excel to modify existing alarms, for example, to translate text strings into foreign languages, or to search and replace text across multiple alarms.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 12–60
13 • Placeholder 13 Setting up language switching This chapter describes: What language switching is. Text strings you can and cannot view in different languages at run time. The basic steps involved in setting up language switching. Setting up font support for Windows languages. Selecting a language for a new FactoryTalk View application. Adding languages to an application. Setting up the default application language. Exporting application text strings.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Import application components developed in different countries into a single application that supports multiple languages. In FactoryTalk View Studio, use the Language Configuration dialog box to export text strings for one language, or for all languages in an application. You can translate or modify the exported strings, and then import them back into the application. For information about: Exporting text strings, see page 13-11.
Text strings you cannot view in different languages In applications that support multiple languages, some text strings will not be able to switch languages at run time. Exported text that does not support language switching If you export text strings for a single application language to a Unicode text file, the caption property of any third-party ActiveX objects will be exported. However, even if these strings are translated, they cannot be viewed in different languages at run time.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Text shown in FactoryTalk View SE system tags You can use system tags in an application to show text in graphic displays. For example, the tag, system\dateandtimestring, shows the current date and time. The changes to Windows regional settings are not reflected in the following tags. The format used is defined by the operating system and cannot be changed.
This graphic object FactoryTalk View Site Edition Recipe Numeric input and string input Numeric display and string display Tag label Trend FactoryTalk View Machine Edition Goto display button Local message display Alarm list, alarm banner, and alarm status list Macro button Has these properties, defined using text that cannot be exported 13 • Placeholder In this product • • • • • 13 • SETTING UP LANGUAGE SWITCHING Value TagName Expression TagName PropertyName Caption All properties, except ChartTi
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Summary of steps for setting up language switching These are the tasks involved in setting up language switching for an application: 1. Install the Windows languages that the application will use. 2. Select a language, in which to create the application and its components. 3. Add the languages you want the application to support. You can add languages to an application before or after you export the application’s text strings.
• • • • • 13 • SETTING UP LANGUAGE SWITCHING Setting up font support for Windows languages The other operating systems supported by FactoryTalk View SE support all of the necessary fonts by default. To make language switching work, you do not need to install any Language Interface Packs (LIP), and your version of Windows Vista does not need to support Multilingual User Interface (MUI).
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When creating a new application, you select a language from the full list of languages that Windows supports, as shown in the following illustration. When creating a new application, you can select any of the languages Windows supports. About the current application language When you open an existing application and select a language from the list of languages the application supports, that language becomes the current application language.
You cannot switch dynamically between application languages while developing an application. To change the current language, you must close the application, and then select a different language when you re-open the application. To add languages to an application 1. In FactoryTalk View Studio, from the Tools menu, select Languages. 2. In the Language Configuration dialog box, click Add. Default language for this application is English. Application languages and RFC1766 names.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To change the default language, open the Language Configuration dialog box, select an application language from the list, and then click Set as Default (shown in the previous illustration). A check mark beside the language you selected indicates that it is the default application language. For information about using the default language to show undefined text strings, see “Showing undefined text strings in the default language,” next.
• • • • • 13 • SETTING UP LANGUAGE SWITCHING Exporting application text strings If the application contains multiple languages, you can export text strings for the selected language only, or for all languages in the application. To export strings only for the currently selected (highlighted) language, and save them to a text file in Unicode format, select the option, Export strings for to one or more Unicode text files (where aa-BB is the RFC1766 code for the selected language).
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Troubleshooting export problems If errors occur during an export operation, or if you cancel the export while it is in progress, a message is logged to the Diagnostics List and log file. In addition, export errors are shown in a log file called ExportErrors.txt, which is saved in the following folder on the local computer: (Windows 7 Professional, Windows Vista, Windows Server 2008) ..
• • • • • 13 • SETTING UP LANGUAGE SWITCHING Unicode text file format For network distributed applications, text strings from each HMI server in the application are exported to separate text files. The file name format is ___.txt, where: is the name of the application. is the name of the area. is the name of the HMI server containing the exported text strings.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The spreadsheet provides the following information, for each exported text string: Server identifies the name of the HMI server that contains the exported text string. For network distributed applications, which can contain multiple HMI servers, the server name format is //:. For local station applications, which can contain only one HMI server, the format is /:.
Do not change the default order of the Server, Component Type, Component Name and Description columns. Do not insert any blank rows or columns in the spreadsheet. The import operation will stop at a blank row or column. Anything after that will not be imported. You can change the order of the columns containing the text strings for each language. However, if you move one of these columns, remember to move the associated REF column with it, if one exists.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For more information about duplicate text strings, see “Working with duplicate text strings,” next. Undefined text strings in an application always export as **UNDEFINED**, regardless of whether you have selected the option, Display undefined text strings in the default language. For more information about this option, see “Setting up a default application language” on page 13-9.
• • • • • 13 • SETTING UP LANGUAGE SWITCHING Working with strings exported to a Unicode text file FactoryTalk View requires that parts of the Unicode text file remain as they were when exported. To ensure that the text file can be imported successfully, after it has been modified, give the information in this section to translators. File name and format Text strings exported for the selected application language are saved in a text file in Unicode format.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 1. When prompted to keep the workbook in Unicode format, which leaves out incompatible features, click Yes. 2. When closing the file, you are prompted to save changes. Click Yes. 3. You can save the file using its original name, or you can type a new name. 4. When prompted again to keep the workbook in Unicode format, which leaves out incompatible features, click Yes.
• • • • • 13 • SETTING UP LANGUAGE SWITCHING Body 13 • Placeholder The body of the text file starts on line eight, and includes the following fields: Field Component type Component name String reference “String definition” Example Graphic Display Pump station 1 “Stop motor” The file is sorted alphabetically by component name, and then numerically by string reference number. Each string reference number refers to a different object in the component.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE “Call “““Duty Manager”” will be imported as: Call “Duty Manager” Working with backslashes and new-line characters To force text to begin on a new line, precede the text with the backslash character \ and the new line character n. For example: Motor\nabschalten is shown in the application as: Motor abschalten To include a backslash in the text, type two backslashes (\\). For example, to include the characters \n in the text, type \\n.
To import text strings into an application 1. In FactoryTalk View Studio, from the Tools menu, select Languages. This opens the Language Configuration dialog box. 2. Export text strings currently in the application, to create a backup. If necessary, you can use the backup to restore text already saved in any application language, if an error occurs while importing, or if you cancel the import before it is complete. For details about exporting text, see page 13-11. 3. Click Import.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE (Windows XP, or Windows Server 2003) C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\Strings Existing import error log files are overwritten for each subsequent import operation that generates errors. If it seems that some but not all of the text in an HMI server has been modified, the import might have been canceled.
Cause and solution File “FileName”, Line x. The string definition must be contained within double quotes. The string was not imported. The translated string definition includes embedded double quotes, but the string definition itself was not enclosed in double quotes. File “FileName”, Line x. Invalid line format! Open the text file, and then enclose all string definitions containing embedded double quotes in double quotes.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Error message Cause and solution “Server Name” is unavailable. No strings for this server were imported. Server name associated with a string in the spreadsheet exists, but the HMI server is not available. No strings associated with this server will be imported. “Server Name_Component Type_Component Name” does not exist in this application. No strings for this component were imported.
Cause and solution Unable to import one or more strings, as one or more cells were not formatted as text or numeric values. A spreadsheet cell containing a string for a language is not formatted for text or numeric values. The string in that cell will not be imported. The import will continue. This error will only be reported once for a single import operation.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To enable language switching in an application, provide operators with a way to run the Language command, for each language the application supports. For example, create buttons in a graphic display that use the Language command as the press action. To find the RFC1766 name associated with a Windows language, open the Add Language dialog box in FactoryTalk View Studio. For details, see “Adding languages to an application” on page 13-8.
• • • • • 13 • SETTING UP LANGUAGE SWITCHING 2. In the Properties tab, clear the check box, Support Multiple Languages. Only text strings for the current application language are saved as language-neutral strings. Using the graphic libraries in a multi-language application To use the contents of graphic libraries in an application, you can add an entire library into the Displays folder, or you can copy one object or more from a library into an existing graphic display.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 13–28
This chapter describes: What it means to maximize availability in a FactoryTalk system. Monitoring the status of application servers. Monitoring the status of the FactoryTalk Network Directory server. Redundancy as part of a system availability strategy. Setting up a redundant HMI server. Determining the Active HMI server in a redundant pair. Switching the Active and Standby HMI servers manually. What happens when the primary HMI server fails.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE FactoryTalk View SE Servers (also called HMI servers). For information about setting up redundant HMI servers, see page 14-13. FactoryTalk Alarms and Events servers. For information about setting up redundant FactoryTalk Alarms and Events servers, see the product documentation. For information about setting up redundant RSLinx Enterprise servers, see the product documentation. OPC data servers, including RSLinx Classic.
• • • • • 14 • SETTING UP FACTORYTALK SYSTEM AVAILABILITY In the Server Status dialog box, you can: Check the status of non-redundant and redundant FactoryTalk View SE Servers, Rockwell Automation Device Servers (RSLinx Enterprise), and FactoryTalk Tag Alarm and Event Servers. Specify switchover options. For example, you can specify whether to always switch back to the primary server, if it’s available. Switch the Active and Standby servers manually. For more information, see page 14-20.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE States for non-redundant and redundant servers The Server Status dialog box will show any of the following states for non-redundant and redundant application servers. A server with this status Has these characteristics Loading The server is loading into memory. You can set up an HMI server to load when the operating system starts, or on demand (when the first client connects to the server).
A server with this status Has these characteristics 14 • Placeholder Not loaded The server is not loaded. For example, an HMI server set up to start on demand does not load until a client connects to it. States for redundant servers only The Server Status dialog box will show any of the following states for redundant application servers only, as long as a partner is defined for the server.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE A server with this status Has these characteristics Active (Can’t reach partner) The server is ready to provide service to clients, but its partner is not ready or cannot be located. This state is also shown if the Active server’s partner has not been defined. Standby The Standby server is ready to accept client connections and provide service to clients, in the event that the Active server fails.
• • • • • 14 • SETTING UP FACTORYTALK SYSTEM AVAILABILITY Monitoring the status of the Network Directory server The FactoryTalk Network Directory (also called the Network Directory) manages FactoryTalk View SE network distributed applications, and network station applications. All of the client and server computers participating in a given network distributed application, or network station application must point at the same Network Directory.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The status of this Network Directory server is (connected). What happens if the Network Directory server is unavailable The Network Directory server cannot be made redundant. Instead, if the Network Directory becomes unavailable while client computers are connected to an application, the clients continue to run, using a local cache of directory information.
Host computer hardware failures, provide backup computers to host application 14 • Placeholder software such as FactoryTalk View SE. • • • • • 14 • SETTING UP FACTORYTALK SYSTEM AVAILABILITY FactoryTalk software failures, set up redundant FactoryTalk View SE and RSLinx Enterprise application servers.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE FactoryTalk View SE Clients FactoryTalk Network Directory FactoryTalk View SE Server FactoryTalk View SE Server FactoryTalk View SE Server FactoryTalk View SE Server RSLinx Enterprise RSLinx Enterprise RSLinx Enterprise RSLinx Enterprise Only one application server of any type, whether it’s a primary or secondary server, can run on a single host computer.
• • • • • 14 • SETTING UP FACTORYTALK SYSTEM AVAILABILITY About FactoryTalk View SE system limits One FactoryTalk View SE Server One RSLinx Enterprise data server. (Optionally, you can enable RSLinx Enterprise to distribute device-based FactoryTalk Alarms and Events.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For information about FactoryTalk View SE platform requirements that might affect the design of a redundant system, see the FactoryTalk View Site Edition Installation Guide. For information about limits and requirements that apply to redundant data servers (RSLinx Enterprise, RSLinx Classic, or another OPC-DA server), see the product documentation.
3. On the secondary server computer, specify the location of the FactoryTalk Network Directory. 4. In the primary server’s Properties dialog box, set up redundancy options, and specify the name of the secondary server computer. 5. Ensure that data on the primary and secondary servers is identical: For HMI servers, you can manually replicate changes from the primary to the secondary server. For details, see page 14-16. For data servers, settings for topics and networks, for example, must be identical.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To specify the Network Directory location 1. Select Start > All Programs > Rockwell Software > FactoryTalk Tools > Specify FactoryTalk Directory Location. To open the FactoryTalk Directory Server Location Utility, you must log on as a user with administrative privileges at the Network Directory and in Windows, on the computer where the tool is running. For more information, see Chapter 5, Setting up security. 2.
..\Users\Public\Public Documents\ RSView Enterprise\SE\HMI Projects (Windows XP or Windows Server 2003) C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\SE\HMI Projects\ 2. In Windows Explorer on the secondary server computer, paste the HMI project folder into the same location.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 3. In the Redundancy tab, select the check box, Provide redundancy using a secondary server. 4. Specify the name of the secondary HMI server’s host computer, and the switchover option for this redundant server pair. For details about options in the Redundancy tab, click Help.
HMI server replication is only available for redundant application server pairs in a FactoryTalk View SE network distributed application. For replication to succeed, the primary server must remain active and the secondary server must remain on standby, for the duration of the replicate operation. For information about checking server states, see “Monitoring the status of application servers” on page 14-2. To replicate changes from the primary to the secondary server 1.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For information about setting up redundancy for an HMI server, see page 14-15. For information about other server states, see “Monitoring the status of application servers” on page 14-2. When an HMI server is ready to be active or standby Application servers become active or standby only when they are ready, that is, when they are capable of accepting and processing requests from connected clients.
If an On Active macro contains many commands (or other macros), it might not finish running before the HMI server is finished becoming active. This means that the macro might still be running, when the server is ready to accept requests from clients. Ensuring that macros finish running If the Active HMI server in a redundant pair fails while a command or macro is running, the command or macro stops running, during failover to the Standby server.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Determining which HMI tag alarm state to use During the network disconnection, HMI tag alarm states are maintained at both the Active primary and the Active secondary HMI server.
• • • • • 14 • SETTING UP FACTORYTALK SYSTEM AVAILABILITY The Server Status display should reflect the switch, for both servers. About FactoryTalk Security permissions To switch the Active and Standby servers manually, users must have permission to perform the switch operation, under User Rights Assignments for the system. To set up the User Rights Assignment for switching servers 1. In FactoryTalk View Studio, in the Explorer window, open the System folder. 2.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If the secondary server is on standby, and ready to become active, it becomes the Active server. If the secondary server is unavailable, the HMI server is taken out of service. Clients that were connected at the time of the failure, start using the Active secondary server within 30 seconds of it becoming active. Clients will only connect to an Active server.
If you choose not to switch back automatically to the primary server, the primary server will go on standby when service is restored, until the Active secondary server fails. If that happens, the failover and switch-back cycle begins again. Notifying clients when switching back to the primary During a switch back to the primary server, the server notifies connected clients when it is ready to provide service, and then waits for a specified time period for clients to respond.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Some of the changes you can make will be visible immediately, on connected clients. Other changes require some other event to occur, before the change takes effect. For example, if you change the Security Code assigned to an HMI tag, the new security check will not occur until there is an attempt to write to the tag. When that happens, the tag write will be validated against the new Security Code.
If you change this property For this type of HMI tag The change takes effect when The Minimum or Maximum property is read using VBA code. The Low EU or High EU property is shown in the Tag Browser. HMI analog tags A graphic display using the Units property, in a tag label object (Engineering Units) or in a trend’s pen, is test run in FactoryTalk View Studio or opened in a FactoryTalk View SE Client. The Units property is read using VBA code. The Engineering Units property is shown in the Tag Browser.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If you change this property For this type of HMI tag The change takes effect when Initial Value HMI analog tags with Memory as data source The tag’s Data Source Type is changed from Device to Memory. The Initial Value property is read using VBA code. The Initial Value property is shown in the Tag Browser. The HMI server is started. Retentive Any HMI tag with Memory as data source Immediately, if the tag is not in use.
If you run AlarmAcceptEdits while a redundant HMI server pair is synchronizing alarm states, the secondary HMI server will not contain the latest changes. To update the secondary server, you must replicate changes made on the primary server. For details, see page 14-16. Example: Modifying HMI tag alarms in a redundant HMI server pair To ensure that changes to HMI tag alarm properties are copied to the secondary server in a redundant HMI server pair, follow these steps: 1. Modify the property.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If this property Is changed to this value This is what happens when AlarmAcceptEdits is run Label Any change New alarm transactions reflect the new Label value. Existing alarm transactions continue to use the old Label value. Severity Any change If the tag is currently in alarm, a new alarm transaction is generated, based on the new Severity value.
Is changed to this value This is what happens when AlarmAcceptEdits is run In Alarm Messages Out of Alarm Messages Acknowledge Messages Identification Out of Alarm Label Deadband Any change The change takes effect, for any new or existing alarm transactions associated with the modified tag. Acknowledge (bit) Any change TIP: The AlarmAcceptEdits command will not apply changes to the contents of User Default messages, for the InAlarm Messages, Out of Alarm Messages, and Acknowledge Messages properties.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE About alarm monitoring on the secondary server While the primary HMI server is active, the secondary server runs its alarm monitoring system in backup mode. This means that alarm states are synchronized even if you have not set up the secondary server to start alarm monitoring on demand. The backup mode that runs on the secondary server only keeps alarm states synchronized; it does not detect alarms.
This will automatically ensure that event detection is only running on the Active (primary or secondary) HMI server. For information about On Active and On Standby macros, see page 14-18. For information about creating macros, see Chapter 24, Adding logic and control. Synchronize derived tags and data log files To keep derived tags and data logs synchronized, ensure that the same derived tags components and data log models are running on the primary and secondary computers.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To change Health Monitoring Policy Settings 1. In FactoryTalk View Studio, in the Explorer window, expand the System folder, double-click the Policies folder, and then double-click the System Policies folder. 2. Double-click Health Monitoring Policy, and then select the policy setting you want to change. 3. Click the amount of time for the policy setting. To select a different time, click the up or down arrow beside the time.
In a partitioned network, if clients are connected to both partners in the redundant pair on either side of a network switch, it is possible for both the primary and the secondary server to become active. For more information, see “What happens if both servers become active” on page 14-19. 14–33 14 • Placeholder The default time period that defines a network glitch is 5 seconds. You can change the definition, by modifying the policy setting, Maximum network glitch.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 14–34
15 • Placeholder 15 Logging system activity This chapter describes: What FactoryTalk Diagnostics is. Key FactoryTalk Diagnostics concepts. Setting up FactoryTalk Diagnostics in FactoryTalk View. Tracking system events in the Diagnostics List. Viewing FactoryTalk Diagnostics logs.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 3. To log system activity to a central, ODBC-compliant database, first set up the database, and then, in the FactoryTalk Diagnostics Setup tool, set up the ODBC Database destination. Finding more information about FactoryTalk Diagnostics For additional information about FactoryTalk Diagnostics, and for detailed setup instructions, see the FactoryTalk Diagnostics Help. To open the FactoryTalk Diagnostics Help 1.
At run time, if the FactoryTalk Diagnostics List is visible, an operator can alert the plant’s control systems engineer to problems such as tag errors, as they occur. During scheduled maintenance time, the engineer can use the errors, together with warning or information messages recorded in the local log, to analyze operation of the system and make the necessary corrections. For more information, see “Setting up message routing” on page 15-5.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE FactoryTalk View assigns the Operator audience for all messages that it generates, except for messages with the Audit severity. Audit messages, including tag write confirmations, are assigned the Developer or Engineer audience. The Secure audience is reserved for auditing tools, such as those required for US Government 21 CFR Part 11 compliance, to track system activity.
• • • • • 15 • LOGGING SYSTEM ACTIVITY Setting up message routing For example, you can specify that tag write messages logged for the Developer audience are sent to the local log, to the Diagnostics list, or to neither destination. All messages are logged as Error, Warning, or Information, with the audience Operator. The exception is tag write messages, which are logged as Information and Audit, with the audiences Developer and Secure.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Central logging works by exporting the contents of the local log periodically, to an ODBC-compliant database. FactoryTalk View supports Oracle, and Microsoft SQL Server ODBC-compliant databases. Logging to a central database provides redundancy for Diagnostics logging. If you lose communications with the ODBC-compliant database, you can use the local log to buffer information.
Tracking system events in the Diagnostics List To keep track of what is happening when an application is running, use the Diagnostics List in FactoryTalk View Studio, the FactoryTalk View SE Administration Console, or the FactoryTalk View SE Client. To include system activity messages in the Diagnostics List, they must be routed to the list. For information about routing messages, see page 15-5. The Diagnostics List in FactoryTalk View Studio.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Moving the Diagnostics List You can detach (undock) the Diagnostics List from the main window, and then move the Diagnostics List anywhere on the screen. To 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 larger. To detach the Diagnostics List, drag the grab bars.
To clear all messages in the list, click Clear All. 15 • Placeholder Clearing a message in the Diagnostics List does not delete the message from the Diagnostics log. Viewing FactoryTalk Diagnostics logs Use the FactoryTalk Diagnostics Viewer to view the contents of Diagnostics logs. To open the FactoryTalk Diagnostics Viewer • • • • • 15 • LOGGING SYSTEM ACTIVITY In FactoryTalk View Studio or in the FactoryTalk View SE Administration Console, from the Tools menu, select Diagnostics Viewer.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 15–10
16 • Placeholder 16 Creating graphic displays This chapter describes: What graphic displays are. Parts of the Graphics editor. Techniques for working in graphic displays. Techniques for working with graphic objects. Testing graphic displays. Creating and working with global object displays. Adding controller instruction faceplates to an application. Using objects from the graphic libraries. Importing graphic files from third-party applications.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Each connection in the Connections property of an object that is linked to a tag is counted as one connection. Each pen configured in a Trend object is counted as one connection. Duplicate references of the same expression or tag connection are counted as the additional connections. For example, one display can contain up to 3000 numeric inputs, even if all numeric input objects refer to the same tag.
Working with global objects When you copy a global object onto a standard display in the Displays folder, the copy is called a reference object. The original global object in the Global Objects folder becomes its base object. Reference objects have special properties that link them to their base objects. At run time, when a standard display that contains reference objects is run, the global object display (or displays) that contains the base objects is loaded in the background.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Menu bar Docked toolbar Display area Floating toolbar Diagnostics List Status bar The Graphics editor consists of these parts: The toolbars contain buttons for commonly used menu items. The previous illustration shows three toolbars, but the Graphics editor has others, including toolbars for foreground and background colors, pattern styles, and aligning objects.
The Diagnostics List shows information about system activity, such as command and macro usage, tag reads and writes, communication errors, and system warnings for the computer where FactoryTalk View is installed. The status bar describes the action associated with the selected menu item or button. The status bar also shows the x- and y-coordinates, width, and height of the selected graphic object.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Click the + icon to view the objects and grouped objects within a group. When you right-click an object in the Object Explorer, the object’s shortcut menu opens, as it does when you rightclick the object in the graphic display. To highlight different types of objects in a display 1. In the Object Explorer, click Settings. 2. In the Highlight Settings dialog box, select boxes beside the items that you want highlighted, and then click OK. 3.
To open the Property Panel Show/Hide Property Panel tool Right-click a graphic object in a display, and then select Property Panel. You can also click the Property Panel tool on the tool bar, to show or hide the panel. Click this button for help with the selected property. Scroll to see more properties … … or drag this bar up or down to see more properties, or more of the description. This box describes the selected property and the type of data the property uses.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If the Size property is set to Use Current Size, Zoom to Fit behaves in the same way as Cancel Zoom; it returns a display to its original size. Setting up a display grid To size and position objects precisely, use the grid items on the View menu. You can change the grid settings any time during the drawing process. Select this check box to make the grid visible. Select this check box to make the grid active.
• • • • • 16 • CREATING GRAPHIC DISPLAYS Selecting objects 16 • Placeholder To work with an object in a graphic display, first you must select it. To select a single object in a display, click on the object using the left mouse button. Handles appear along the edges of a selected object. To select several objects, click in the graphic display at one corner of the group, and then drag the mouse diagonally, to draw a bounding box around the objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Copying objects To copy objects, you can: Drag and drop objects in the same display. Drag and drop objects between displays, or from a graphic library to a display. Copy and paste objects. When an object is copied, any animation attached to the object is also copied. If a group is copied, the new copy of the group can be ungrouped to individual objects, just like the original.
• • • • • 16 • CREATING GRAPHIC DISPLAYS 3. Select one or more objects. If you selected several objects, dragging one of the objects copies all the selected objects. The objects maintain their position relative to each other. Copying and pasting objects You can cut, copy, or paste objects using the menu items on the Edit menu or the buttons on the toolbar. Once you cut or copy an object, you can paste it anywhere in the drawing area of: The same graphic display.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To duplicate an object Duplicate Right-click the object in a display, and then select Duplicate, or click the duplicate menu item. Duplicate works until the object is no longer selected. Select object Duplicate object Move object Duplicate again Resizing and reshaping objects When you select an object, handles appear around it. When you position the pointer over a handle, the pointer changes to a double-headed arrow.
16 • Placeholder Drag a side handle to change either the width or height. Drag a corner handle to change both the width and height. You can reshape some objects using the object’s editing tool. To do this, right-click the object, and then select Edit. The tool varies, depending on the object that has been selected. To maintain an object’s proportions while resizing Click on a corner handle, press Shift, and then drag the mouse.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Stacking objects Objects in a graphic display are stacked in the order they are created, with the most recently created object on top. To change the order, move objects to the front or back of the stack. Use Send to Back to move the selected object to the bottom of the stack. Send to Back . Select the object. Send the object to back. Use Bring to Front to move the selected object to the top of the stack.
To do this Align the selected object (or objects) with the grid. Click this button or menu item 16 • Placeholder Align the selected object (or objects) with the topmost selected object. Align the selected object (or objects) with the vertical center of the largest selected object. Align the selected object (or objects) with the bottom-most selected object. Align the selected object (or objects) with the center of all selected objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Aligning objects left, right, and center Select objects Align left Select objects Align center Select objects Align right Spacing objects To create an equal amount of space between the center points of objects in a graphic display, space the objects vertically or horizontally. To do this 16–16 Click this button or menu item Place the centers of the selected objects an equal distance apart horizontally.
• • • • • 16 • CREATING GRAPHIC DISPLAYS Spacing objects vertically and horizontally 16 • Placeholder Centers are separated by an equal vertical distance. Select objects Space vertically Centers are separated by an equal horizontal distance. Select objects Space horizontally Flipping objects To move an object in a graphic display to a position that is a mirror image of its original position, flip the object vertically or horizontally.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Flipping objects horizontally Select object Flip horizontal Rotating objects To rotate an object or group of objects around an anchor point, use the Rotate tool. The anchor point is represented by a crosshair, as shown in the following illustrations: Rotate You can place the crosshair inside an object. You can place the crosshair outside an object. You can also use the Rotate tool when attaching rotation animation to a graphic object.
• • • • • 16 • CREATING GRAPHIC DISPLAYS Grouping objects Group You can cut, copy, and paste groups, arrange the group as a single object relative to other objects, and apply the same properties to all the members of the group at once. Drag the mouse to select the objects. Group them. You can attach animation to a group and preserve any animation attached to the objects that make up the group. Group animation generally takes precedence over the animation attached to individual objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Select the group. Ungroup it. Modifying grouped objects You can modify a group of objects without breaking up the group. This is particularly useful when animation is attached to the group, because ungrouping deletes the animation. Modify grouped objects using: The Property Panel, to apply shared properties to all members of the group at the same time. For example, change the line width of all objects in the group to 2 pixels.
To cancel group edit mode, click outside the group border. Applying colors The color palettes contain a range of colors that you can apply to graphic objects. You can select colors before you draw an object, or you can apply them to an existing object. To show and hide the color palettes, from the View menu, select their names. You can use the: Foreground Color palette to select a color for the outline of an object, for text, or for hollow objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Pattern styles apply to the interior of objects. Closed objects such as rectangles, circles, polygons, text objects, and wedges are completely filled. Open or partially open objects, such as polylines or freehand objects, can also take a pattern style. The Graphics editor draws an imaginary line from the start and end points, and then fills the object as a closed object.
Naming graphic objects When you create a graphic object, it is assigned a name automatically. In the Common tab of the object’s Properties dialog box, or in the Property Panel, you can give the object a new name. An object’s name is used when logging events for the object. It is also used with commands. For example, when using the Invoke command to call a method, you must specify the name of the object in which the method is implemented. The object’s name is also shown in the Object Explorer.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Type a tag name or expression in this column. Click this button to open the Tag Browser. The arrows show the direction in which data flows between the object and the tag or expression. Click this button to open the Expression editor. This box describes the selected connection, and the type of data it uses. The Connections tab is blank, if multiple objects are selected. You can only assign a tag or expression to one object at a time.
16 • Placeholder When you type a name here … • • • • • 16 • CREATING GRAPHIC DISPLAYS … the object’s name changes here. When you type text here … … a tooltip for the object is shown at run time. You can create a tooltip for an object in the Property Panel, or in the Common tab of the object’s Properties dialog box. Tooltips can consist of a single line or multiple lines of text.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 2. From the Edit menu, select Tag Substitution. 3. In the Tag Substitution dialog box, type the text you search for and replace, and then click Replace. For details about options in the Tag Substitution dialog box, click Help. Creating a background for a display You can create a background for a graphic display by converting objects to wallpaper.
• • • • • 16 • CREATING GRAPHIC DISPLAYS Testing graphic displays Test Display tool Edit Display tool When you are finished testing, to continue working on the display, switch back to edit display mode. To switch between test and edit modes, use the buttons on the toolbar or the items on the View menu. Testing a graphic display in FactoryTalk View Studio is not the same as running the display in the FactoryTalk View SE Client.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To view an object’s states using the Property Panel 1. Select one or more objects. 2. In the Property Panel, click the State property, and then click the state to view. 3. To view the next state quickly, double-click the row, or press Enter on the keyboard.
• • • • • 16 • CREATING GRAPHIC DISPLAYS where is the name of the HMI server in the Explorer window. To create a new global object display In FactoryTalk View Studio, in the Explorer window, right-click the Global Objects icon, and then select New. The new global object display opens in the Graphics editor. Use tools in the editor to create global objects, just as you would create graphic objects in a standard display. To create a global object display from an standard display 1.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE However, you can run a global object display in test display mode, when developing an application in FactoryTalk View Studio. To minimize the number of global object displays that must be loaded in the background at run time, store the base objects used in an application on as few global object displays as possible.
For more information about faceplates, see the FactoryTalk View Site Edition Help. Using objects from the graphic libraries FactoryTalk View comes with libraries that contain graphic objects and displays. Many of the objects are preconfigured with animation. Use the objects as they are, or change them to suit your needs. You can: Look at the objects and displays to get ideas for the application you are creating. Drag and drop objects from the libraries into displays.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When you import objects, you can convert them to FactoryTalk View objects. This offers the following advantages: Graphic display files are smaller. Objects are groups of objects rather than a single object. This means you can modify the individual parts of the object, including attaching animation to individual parts.
Do not use the Scale option The Scale option in the Display Settings dialog box causes the contents of a graphic display to change size to suit the size of the graphic display’s window. To speed up the display of a graphic containing bitmaps, choose Pan rather than Scale. Bitmaps take longer to draw when they are scaled to a size different from their original size. An OLE object can be a bitmap or a bitmap wrapped in a metafile. These types of OLE objects will also draw more slowly when scaled.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the Image Browser, use one of these methods In an object’s Properties dialog box, click the Browse button next to the Image box. Depending on the type of object, the Image box could be located on the General tab, Label tab, or States tab. Browse button With one or more objects selected, in the Property Panel click the Image property, and then click the Browse button. Click an image to select it.
6. Click the OK button in the Image Browser for the graphic to be placed in the current workspace. Note that any Symbol Factory object, including Bitmap, DIB and metafile can be pasted into Image Browser where it will be stored as a bitmap. Using placeholders to specify tag values Tag placeholders can save time spent developing and maintaining applications, by providing a way to use a single graphic display for several similar operations.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You can also use one or more tag placeholders to specify parts of a complete tag name. In #1\PV, for example, the tag placeholder #1 stands for the name of the folder that contains an HMI tag named PV. To specify the full tag name at run time, you would only have to provide the folder name in a parameter file or parameter list.
• • • • • 16 • CREATING GRAPHIC DISPLAYS Replacing tag placeholders using parameter lists Example 1: Replacing tag placeholders with a list of tag names To run a graphic display named Canning, with the tags Pea_Weight, Pea_Level, and Pea_Temp, type: Display Canning/TPea_Weight, Pea_Level, Pea_Temp Example 2: Replacing tag placeholder with a list of folder names The tag database contains these tags: Corn\Weight Corn\Level Corn\Temp Bean\Weight Bean\Level Bean\Temp Wherever the tags are needed, the plac
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For grouped reference objects, the value specified for the top-level object is applied to every object comprising the group, that uses the same tag placeholder. If you do not assign a value to a tag placeholder at design time, you can provide the value at run time using either a parameter file, or the /T parameter with the Display command. For information about using these methods, see page 16-36 and page 16-37.
• • • • • 16 • CREATING GRAPHIC DISPLAYS To assign a value to a tag placeholder in a reference object If there are no tag placeholders defined for the linked base object, the Global Object Parameter Values dialog box is not available. The Global Object Parameter Values dialog box shows the Name and Description of all tag placeholders defined for the global base object, as shown in the following illustration. 2.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For the LinkConnections default, select True. Click OK. 6. Create a global reference object, by copying the base object and then pasting it into a standard graphic display (in the Displays folder). 7. Duplicate the reference object. 8. Right-click the first reference object, and then select Global Object Parameter Values.
• • • • • 16 • CREATING GRAPHIC DISPLAYS Setting up the appearance and behavior of a graphic display Setting up the properties of a graphic display In the Properties tab of the Display Settings dialog box, you can specify: How the display interacts with other displays at run time. Whether multiple copies of the display can run simultaneously on the same client. How displays are cached. What buttons and text show in the display’s title bar. How often the display is updated.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In the Properties tab, secure the display and set up how it looks and performs at run time. Specifying the display type You can set up the following display types in a FactoryTalk View application: Replace is the default display type. If you want the graphic display to replace other open displays when it opens, use the Replace option. A display of Replace type closes displays that it overlaps.
Overlay displays always appear behind On Top displays, and are replaced by Replace displays. Use the Overlay type with care; keeping multiple displays open at run time can affect system performance. On Top graphic displays will stay on top at all times, even if another display has focus. If you want the display to always appear on top, use the On Top option.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Caching displays Placing a graphic display in the cache makes the display appear more quickly at run time, every subsequent time it is opened, because it does not have to be read from disk. You can have up to 40 graphic displays in the cache. Place large or complex displays in the cache, to minimize the use of system resources. The Always Updating option keeps a cached display up to date, even when the display is not visible.
Showing the last known values of HMI tags You can set up a graphic display to show the last known value for each HMI tag in the display, until current values arrive from the programmable controller. In many applications, selecting this option will help to show graphics more quickly. At run time, if a display is not set up to show the last known value of HMI tags, objects with values that have not yet been updated appear in outline form. The outline indicates that data is not current, or is in error.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The scroll bars will remain on the window, even if subsequent displays are small enough that scroll bars are not needed. To minimize the need for scroll bars, the FactoryTalk View SE Client tries to position all graphic displays within its main window, unless this placement is explicitly overridden by the /X and /Y parameters of the Display command.
If you do not select this check box, the display will not be added to the navigation history. Setting up the run-time behavior of a graphic display In the Behavior tab of the Display Settings dialog box, you can specify: Startup and shutdown commands. Colors for input fields. The behavior of interactive objects, such as push buttons. The behavior of objects with input focus.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Specifying startup and shutdown commands To run commands when the graphic display starts or stops running, specify display startup and shutdown commands, or macros. If you use the Always Updating option with the Cache After Displaying option, the startup command is run when the display is loaded into the cache. The shutdown command is run only when the cache is flushed. This happens when: The FlushCache command is run.
• • • • • 16 • CREATING GRAPHIC DISPLAYS Specifying the behavior of objects with input focus You can specify whether objects with input focus in a graphic display have a highlight box, and what color the highlight will be. Using both types of highlight in the same display You can choose to highlight only interactive objects, only objects with input focus, or both types of object. An interactive object is highlighted when the mouse passes over it.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The keyboard for string input and recipe fields accepts alphanumeric characters. The keypad for numeric input fields accepts numeric characters only. For more information, see page 17-26. Setting up displays to open more quickly If graphic displays are stored in the display cache, they open more quickly. You can place up to 40 graphic displays in the cache.
• • • • • 16 • CREATING GRAPHIC DISPLAYS All the new displays you create will have these initial default settings. 1. Create a new display, and change its display settings to the desired default values. When you make certain changes, the Set as Default button changes to Apply. This lets you apply the changes to the current display without closing the Display Settings dialog box. It does not affect the default display settings. 2. Click OK to save the changes and to close the Display Settings dialog box.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In the FactoryTalk View SE Client Wizard, you can also specify a docking parameter for the initial display that runs when the client starts up. The Display command parameters /B, /Min., /Max, /X, and /Y are ignored when specified with a docking parameter. For more information, see the FactoryTalk View Site Edition Help.
Running other displays in the available client area The size and position of docked graphic displays in the FactoryTalk View SE Client window determines where in the window other graphic displays can run. For example, if you dock a display named Menu at the top of the SE Client window, and then run a display named Line1, it will run in the area not occupied by the docked display.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Closing docked displays Use the Abort command to close docked displays individually, or to close all docked displays, and any other displays running in the FactoryTalk View SE Client window.
17 • Placeholder 17 Creating graphic objects This chapter describes how to use, create, and set up the graphic objects available in FactoryTalk View Site Edition. For information about using the Graphics editor, and creating and setting up graphic displays, see Chapter 16, Creating graphic displays.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Alarm and Event objects such as the alarm and event summary and the alarm status explorer, provide ways for FactoryTalk View SE users to monitor and control FactoryTalk Alarms and Events. For information about the Alarm and Event objects, see Chapter 12, Setting up FactoryTalk alarms. OLE objects such as spreadsheets, charts, or text, are produced by other Windows applications.
• • • • • 17 • CREATING GRAPHIC OBJECTS The following illustration shows the Properties dialog box for a polygon object. 17 • Placeholder In the Properties dialog box, the features of the object are organized in tabs. The number of tabs and their contents depend on the type of object. For details about options in any Properties dialog box, click Help. Setting up properties common to all objects There is a Common tab in the Properties dialog box for every FactoryTalk View graphic object.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Creating the different types of drawing objects To draw simple objects such as lines, rectangles, and ellipses, in the Graphics editor, select drawing tools from the Objects menu or toolbar. The drawing tool for an object has the name of the object. To draw a rectangle or square, for example, select the Rectangle tool. After selecting a drawing tool, draw the object by dragging the tool, or by clicking end points.
• • • • • 17 • CREATING GRAPHIC OBJECTS Drawing a polyline or polygon Polyline tool Polygon tool Polyline Polygon Filled To draw a polyline or polygon 1. Drag the Polyline or Polygon tool to create the first segment of the object. To draw horizontal or vertical lines (not diagonal lines), press Ctrl while you drag. 2. Release the mouse button. 3. Move the Polygon or Polyline tool to where the angle of the object is to be, and then click the left mouse button.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Drawing an arc or wedge Arcs and wedges are drawn in two steps: first you create an ellipse or circle, and then you reshape the ellipse or circle. Arc tool Arc Hollow wedge Filled wedge Wedge tool You can also use the Arc and Wedge tools to reshape existing arcs, ellipses, or wedges. To draw the arc or wedge 1. Drag the Arc or Wedge tool to draw a circle. 2. Release the mouse button. 3.
• • • • • 17 • CREATING GRAPHIC OBJECTS Creating text objects 17 • Placeholder Use the Text tool to draw a text object. You can then create the text and set up its appearance in the Text Properties dialog box. Text tool Choosing text fonts You can choose a font before or after you create text, and change the font of any object, including objects that display data or have captions.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Creating a panel Use the Panel tool to draw rectangles and squares that have borders. Panel tool The panel object supports visibility animation. You can also set up panel objects to blink at run time. For details, click Help in the Panel Properties dialog box. Adding images into graphic displays To add an image into a graphic display, you can: Place an image to be used in several displays.
• • • • • 17 • CREATING GRAPHIC OBJECTS Importing images into graphic displays When you import an image, FactoryTalk View converts .gif, .tif, .pcx, and .jpg images to the Windows .bmp format. Vector images in .dxf and .wmf formats are converted to FactoryTalk View graphic objects. For details, see “Importing graphic files from third-party applications” on page 16-31.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Determining which objects have input focus At run time, the object with focus in a graphic display is surrounded by a highlight box, unless the check box, Disable Highlight When Object has Focus, is selected in the Display Settings dialog box for the display. Highlight box In the Display Settings dialog box, you can also specify the highlight color. For more information, see “Specifying the behavior of objects with input focus” on page 16-49.
• • • • • 17 • CREATING GRAPHIC OBJECTS Removing objects from the tab sequence You can also turn off key navigation for objects that take input focus, except for push buttons, recipe objects, input objects, and HMI tag alarm summaries. When an object’s key navigation is turned off, an operator can still select the object using a mouse or touch screen, if one is available.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Latched push buttons lock in the on position, and must be unlocked by another button or process to return to the off position. This type of button is useful for starting a machine or process. Multistate push buttons let an operator cycle through multiple options consecutively, using a single button that displays the current state of a process or operation. Each state can be represented by a different color, caption, or image.
In the Up Appearance tab, specify what the button looks like when it is not pressed. In the Down Appearance tab, specify what the button looks like when it is pressed. In the Disabled Appearance tab, specify what the button looks like when it is in the disable state. Creating momentary push buttons Use the Momentary Push Button tool to create a button that starts a process or action.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Normally closed means the released state of the button is on: when the button is pressed, the tag’s value is set to 0; when the button is released, the tag’s value is set to 1. Pressing the button breaks the circuit.
• • • • • 17 • CREATING GRAPHIC OBJECTS Creating maintained push buttons Maintained Push Button tool When first pressed, the maintained push button changes a tag to one value. When pressed and released a second time, the button changes the tag to another value. Maintained push buttons are not useful for starting or stopping a machine or process.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Creating latched push buttons Latched Push Button tool Use the Latched Push Button tool to create a button that latches in the on position, and must be unlatched by another button or process to return to the off position. This type of button is useful for starting a machine or process. The Handshake tag must be set back to zero before the operator can press the latched push button again.
• • • • • 17 • CREATING GRAPHIC OBJECTS Creating multistate push buttons Multistate Push Button tool The multistate push button displays the current state of a process or operation, by showing a different color, caption, or image to reflect different states. Each time the operator presses the button, the tag changes to the value for the next state. If the button is in its last state when the operator presses it, the button returns to its first state.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up interlocked push button properties In the Interlocked Push Button Properties dialog box: In the General tab, specify the general appearance and touch margins of the button, its value, and whether an audio signal is produced when it is pressed. In the States tab, specify what the button does when it is pressed and released. In the Connections tab, specify the tags or the expression the button will use for transferring data.
Setting up ramp push button properties In the Ramp Push Button Properties dialog box: In the General tab, specify the general appearance of the button, the action the button performs, and whether an audio signal is produced when it is pressed. In the Label tab, create a caption and select an image for the button. In the Timing tab, set up whether the button action will repeat automatically, when the operator holds the button down. You can also set up the repeat rate.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Creating navigation push buttons Use the Navigation Button tool to create a button that an operator can use to create buttons that navigate between the opened graphic displays. Navigation Push Button tool A navigation push button can perform three types of actions: DisplayPreviousScreen opens the previous graphic display in the navigation history when the button is clicked.
Creating the different types of data display and input objects Operators can use data display and input objects to view or change tag data. You can create the following types of data display or input objects: Numeric and string display objects to let operators view tag or expression values in a graphic display at run time. Use display objects to show numeric values or text that the operator does not need to modify. Numeric and string input objects to let operators read or write tag values at run time.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE An input object can also be set up to display a tag’s current value, eliminating the need to create separate input and display objects. For details, see “Updating tag values continuously” on page 17-23.
• • • • • 17 • CREATING GRAPHIC OBJECTS Tag-related limits Each expression associated with an object is counted as one connection regardless of the number of tags in the expression. Each animation of an object (except the Touch animation) is counted as one connection. Each connection in the Connections property of an object that is linked to a tag is counted as one connection. Each pen configured in a Trend object is counted as one connection.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When the input object is ready to receive input, it has a solid border surrounded by a highlight box: This is called input mode (or input focus). At run time, when a graphic display containing input objects is opened, the first nonupdating object in the index sequence receives focus. If all the input objects in the display are set to update continuously, none of the objects will receive initial focus.
Shortcut keys for retrieving and sending data An operator can use the following keys to retrieve data from and send data to the value table. You can re-assign these actions to other keys, or assign them to button objects. PgDn downloads the contents of all input objects that are in pending write mode (in the active graphic display) to the value table. Ctrl+PgDn downloads the contents of the selected input object to the value table.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Parts of the on-screen keyboard You can set up graphic displays so that the operator can use an on-screen keyboard for input entry in recipe, string, or numeric input objects. The keyboard that opens for string input and recipe objects (shown in the following illustration) accepts alphanumeric characters. The keypad that opens for numeric input objects accepts numeric characters only.
• • • • • 17 • CREATING GRAPHIC OBJECTS Creating numeric and string display objects Numeric and String Display tools In the Numeric Display or String Display Properties dialog box, specify the tag or expression to display, and the appearance of the display object. For details about options in the Properties dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Most indicators have several states, and an error state. The error state occurs when the indicator is receiving invalid data. The List indicator has no error state. If the value of the Indicator tag does not match an available state, none of the states is highlighted. Set up states for an indicator object in the Connections tab of the Properties dialog box.
• • • • • 17 • CREATING GRAPHIC OBJECTS Creating symbols In the Symbol Properties dialog box, specify state values for the symbol indicator, and the image to be shown for each state. For details about options in the Properties dialog box, click Help. At run time, the symbol indicator shows the state whose value matches the Indicator tag or expression’s value.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Changing a gauge’s fill color at different thresholds As the needle sweeps higher on a gauge, the area beneath the needle can fill with a color. To help the operator recognize abnormal conditions, you can set up a gauge to change its fill color when the tag value crosses a threshold. For example: If the temperature of an oven is lower than required for a recipe, the gauge can show the temperature in blue.
If the level of the tank is in the current range for the recipe, the graph can show the level in yellow. If the level is higher than the level the recipe requires, the graph can show the level in green. Showing limits using scales with bar graphs Unlike gauges, bar graphs do not have integrated scales. Instead, you can show values on a bar graph using a scale and text. Scales consist of major ticks, represented by long lines, and minor ticks, represented by short lines.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using key objects to simulate keyboard functions In the FactoryTalk View Graphics editor, the term key can mean any of the following: Key animation links a graphic object or display to a keyboard key or mouse button, so that an operator can perform an action by pressing the key or mouse button. For more information, see “Associating objects and displays with keys” on page 18-18.
Home Move up Move right Backspace Move left Enter 17 • Placeholder End • • • • • 17 • CREATING GRAPHIC OBJECTS Page up Page down Move down In the Properties dialog box, the various features of the object are organized in tabs. For details about options in each tab, click Help. Setting up the auto-repeat function for selected keys All of the key objects have similar features, except that the move left, move right, move up, move down, page up and page down keys can be set up to auto-repeat.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Piloted control list selectors have the same function as control list selectors. However, they can be controlled directly by an operator, or remotely by a device such as a programmable controller. Tag labels show information about a tag’s properties, such as the description, engineering units, and minimum and maximum values. Display list selectors let an operator navigate between graphic displays in a list.
• • • • • 17 • CREATING GRAPHIC OBJECTS Creating tag labels Tag Label tool In the Tag Label Properties dialog box, specify the tag associated with the label, and the property to show. For details about options in the Properties dialog box, click Help. Some HMI tag properties have different names when shown using a tag label. The following table describes which properties correspond with the types of tag labels.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up states for a display list selector To set up the states for a display list selector, decide how many graphic displays are to be in the list, and then, in the States tab, add that number of states to the display list selector. For each state, specify a display and its associated parameter file or parameter list. Also specify a caption that identifies the display. This is what the operator will see in the list at run time.
• • • • • 17 • CREATING GRAPHIC OBJECTS What is shown at run time At run time, a local message display shows one message at a time. Special cases are handled in the following ways: If the Value tag or expression is unassigned, the local message display is filled with question marks (?). The Value tag or expression is rounded to the nearest integer. If the value does not match any of the trigger values in the message file, the local message display is filled with question marks (?).
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 2. In the Local Messages editor, create the following messages with five trigger values, to match the values of the Hoist_Status tag: Trigger value Message 1 2 3 4 5 The hoist is ready to rise. The hoist is raising the pallet. The hoist has stopped. The hoist is lowering the pallet. The hoist is finished rising. 3. Save the message file with the name Hoist status. 4. In the Graphics editor, create a local message display object. 5.
Each graphic display can contain only one recipe object. Restoring and saving recipe values at run time At run time, an operator can restore values from a recipe file into input objects and send those values to a network device or server. The operator can also upload values from a network device or server into input objects, and then save those values to a recipe file. If an upload fails because of a communication error, the input object appears in outline form.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If you didn’t specify a recipe file name, select a recipe file first, and then click Restore. You can also use the RecipeRestore command to restore values from a recipe file. For details, see the FactoryTalk View Site Edition Help. To download recipe values to a network device or server 17–40 After restoring values from a recipe file to input objects in a display, to download the values, press PgDn, or use the DownLoad or DownLoadAll command.
Values typed in input boxes in the following graphic display, are used to create a recipe file for chocolate-chip cookies. Numeric input boxes Recipe object String input box This is the new recipe file: Index number Value Tag name (in comment) To save recipe values from a network device or server 1. To upload values you want to save to a recipe file, press PgUp, or run the Upload or UploadAll command.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 2. In the recipe object, type the name of the recipe file, and then press Enter. If you don’t know the name of the recipe file, just click in the recipe object, and then press Enter. 3. In the Recipe dialog box, click Save. If you didn’t specify a recipe file name, select a recipe file first, and then click Save. You can also use the RecipeSave command to save values to a recipe file. For details, see the FactoryTalk View Site Edition Help.
For more information about keys, see “Using key objects to simulate keyboard functions” on page 17-32. Setting the Value tag At run time, the Value tag changes: When the operator selects the next item in the list. When the operator presses the Enter key, if the control list selector requires that a selection be confirmed using the Enter key. When another process changes the tag’s value in the network device. For example, a control list selector is used to change a tag’s value.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When the control list selector is in its last state and the operator presses the key, the control list selector returns to its first state. Creating piloted control list selectors Piloted control list selectors let an operator (or a remote device) scroll through and select from a list of states for a process. A highlight in the list indicates the current state.
• • • • • 17 • CREATING GRAPHIC OBJECTS 17 • Placeholder The filled cursor means the operator can select this state. The hollow cursor means the operator cannot select this state. Using keys to scroll the list When a piloted control list selector is operator controlled, it works with: Key objects. These are graphic objects that duplicate the functions of keyboard keys. Use them with touch-screen terminals. The arrow keys and Enter key on a terminal’s keypad.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When an operator or remote device selects a state, the value assigned to the selected state is written to the piloted control list selector’s Value tag. If the state is turned off, the state’s value is not written to the Value tag. If the operator attempts to select a state that is remote controlled, the state’s value is not written to the Value tag.
If the Enter Handshake tag is not assigned, the Enter tag remains set until the Enter key hold time expires. 4. The Enter tag is reset to 0. How the Handshake reset type option works The Enter Handshake tag resets the Enter tag as follows: Non-zero value resets the Enter tag when the Enter Handshake tag is a non-zero value. Zero to non-zero transition resets the Enter tag when the Enter Handshake tag changes from zero to a non-zero value.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You can set up 255 states for a piloted control list selector. This provides the operator with up to 255 selections in the list. Setting up connections for a piloted control list selector To connect with a network device such as a programmable controller, piloted control list selectors use tags or expressions. You set up these tags or expressions in the Connections tab of the Properties dialog box.
• • • • • 17 • CREATING GRAPHIC OBJECTS Creating the Alarm and Event objects You can create the following Alarm and Event objects: The Alarm and Event summary shows detailed alarm information from selected Rockwell Automation Device Servers (RSLinx Enterprise) and Tag Alarm and Event Servers in a FactoryTalk View SE application. You can use the alarm and event summary to view, acknowledge, suppress, and disable the alarms on display.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For more information about creating global object displays, see Chapter 16, Creating graphic displays. Creating reference objects After creating a global object (or group of objects), you can copy it for use in standard displays throughout an application. When you copy a global object into a standard graphic display (in the Displays folder), the copy is called a reference object.
• • • • • 17 • CREATING GRAPHIC OBJECTS Using placeholders to specify values for global objects Tag placeholders used in standard graphic objects let you reuse one graphic display for several purposes, by substituting tag values for the placeholders at run time. You can also set up tag placeholders for a global objects, to assign different run-time values to the reference objects linked to the global base object.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the Global Object Defaults dialog box Right-click the reference object you want to modify, and then select Global Object Defaults. For details about options in the Global Object Defaults dialog box, click Help. If you change the properties of a linked reference object, you might lose the original settings.
LinkConnections The LinkConnections property determines whether the reference object uses the connections set up for its base object. Set up the LinkConnections property of the reference object by selecting: True, to use the connections assigned to the base object. False, to set up connections for the reference object separately.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE LinkBaseObject The LinkBaseObject property specifies the name and location of the base object the reference object is linked to. You cannot modify the LinkBaseObject property. If the specified global object display or base object does not exist, the reference object will appear in red outline, with a red cross on a white background.
• • • • • 17 • CREATING GRAPHIC OBJECTS Working with OLE objects OLE objects are objects that were created in other Windows applications and linked to or embedded in a FactoryTalk View graphic display. The main difference between linking and embedding is where data is stored: Linked OLE objects are stored in the source file. The graphic display stores the location of the source file and displays a representation of the linked data.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Embedding an object in a graphic display increases the size of the graphic file, because the embedded object includes information about its source application. This lets you double-click the object and modify it using the source application. If you convert the object, you can no longer modify it using its source application. However, you can use the editing tools in the Graphics editor to work with the object.
Methods are functions implemented in the ActiveX object, that make it possible for external actions to change the object’s appearance, behavior, or properties. A call to a method might be made in response to events from other controls and could trigger other events. You can use the FactoryTalk View Invoke command as the external event that calls a method. For more information about the Invoke command, see the FactoryTalk View Site Edition Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up tools in the ActiveX toolbox Use the ActiveX toolbox to set up tools for the ActiveX objects you use frequently. By default, the ActiveX toolbox contains some of the Microsoft Forms 2.0 ActiveX controls that are installed with VBA, and the FactoryTalk View SE Signature Button. For information about adding objects to the toolbox, see the FactoryTalk View Site Edition Help.
From the Explorer, click the Symbol Factory Object. When the Objects menu is available, click the Symbol Factory drop down menu item. When the Objects toolbar is available, click the Symbol Factory icon. In the Image Browser, clicking the Launch Symbol Factory button. To select a graphic: 1. Browse the Categories frame, clicking a category to see the symbols in the right frame. 2. Click the graphic to select it for the Graphic Display.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The signature button can be used together with other features of FactoryTalk View SE, to meet the security standards required for regulated manufacturing applications, for example, those required for US Government 21 CFR Part 11 compliance. The signature button verifies the operator’s identity, and allows an action only if the operator enters the appropriate user name and password.
• • • • • 17 • CREATING GRAPHIC OBJECTS Securing tag writes, commands, and downloads 17 • Placeholder You can use the signature button to secure the following operations: Setting a tag value Running a FactoryTalk View command Downloading all input object values to a network device At run time, if a user name or password is incorrect, or if other information, such as an operator’s comment, is required but not provided, these operations can be prevented and an error message shows.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To ensure that values are downloaded only if the electronic signature is verified, you must secure the graphic objects separately. To do this, use one of these methods: Turn off the Enter key, by using the /E parameter with the Display command. For details about the Display command, see the FactoryTalk View Site Edition Help. Use display keys to set the Page Up, Ctrl+Page Up, Page Down, and Ctrl+Page Down keys to do nothing.
18 • Placeholder 18 Animating graphic objects This chapter describes: What FactoryTalk View animation is. Setting up animation for FactoryTalk View graphic objects. Creating effects using the different types of animation. Using index numbers to navigate to objects in a display. Associating objects and displays with keys. Animating ActiveX objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up animation for FactoryTalk View graphic objects To animate FactoryTalk View objects in a graphic display, create the objects first, and then apply animation to them. In the Graphics editor, use the Animation dialog box to apply animation to the selected object or group of objects. Check marks indicate which types of animation are applied to the selected object.
• • • • • 18 • ANIMATING GRAPHIC OBJECTS To open the Animation dialog box 2. Select View menu > Animation, and then select the type of animation to apply. Types of animation an object can’t have will not be available on the Animation menu. Linking animation to tag values Most types of animation can be linked to the value of a tag. To link animation to a tag value, you have to specify a tag name or a tag placeholder.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The action can be a FactoryTalk View command or macro. For example, to use touch animation to open a graphic display, specify the Display command as the press or release action. For a complete list of FactoryTalk View commands and their syntax, see the FactoryTalk View Site Edition Help. For more information about macros, see Chapter 24, Adding logic and control.
1. In the Graphics editor, create a slider using a line and a rectangle, or copy a slider object from the Sliders library in the Graphics Libraries. 2. Right-click the slider, select Animation > Horizontal Slider. 3. In the Tag box, type a tag name. To find and select a tag, click the Browse button. 4. In the display, drag the slider to the position indicating the lowest number in the range. 5. In the Animation dialog box, set this position by selecting the At minimum check box. 6.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Testing animation To test the animation applied to objects in a graphic display quickly, switch to test display mode in the Graphics editor. Test Display tool Edit Display tool When you are finished testing, switch back to edit display mode to continue working on the display. To switch between test and edit modes, use the buttons on the toolbar or the items on the View menu.
To copy and paste only the animation 1. Right-click the object that has the animation you want to copy, and select Copy animation. 2. Right-click the object you want to paste the animation onto, and select Paste animation. About global objects and animation You can create a FactoryTalk View global object to link the appearance and behavior of one graphic object to multiple copies of the object in the same application.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Showing and hiding objects Use visibility animation to make an object visible or invisible, based on a tag value or the result of a logical expression. If an object is invisible, no other animation applied to the object is evaluated, to prevent unnecessary processing. You can apply visibility animation to all FactoryTalk View graphic objects. Visibility animation overrides an object’s visibility property, if there is a conflict.
• • • • • 18 • ANIMATING GRAPHIC OBJECTS The following example shows the effects of Shaded and Gradient fill styles. 18 • Placeholder For each color change, specify the value or threshold at which the color changes, and specify the colors you want the object to change to. At run time, when the value reaches or crosses the threshold, the color of the object changes. Color animation does not affect string input, numeric input, or recipe objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 7. Select the Blink color check box next to the Blink check box to open the color palette, and then select a color. 8. Click Apply, and then close the Animation dialog box. Use the Test Display tool to test the animation in this example. The text will blink between the colors you selected.
• • • • • 18 • ANIMATING GRAPHIC OBJECTS 2. For line and fill colors, select the Solid Fill Style. To set up the color for the first warning 1. In the thresholds and colors list, select B. 2. In the Value box, type 80. 3. For line and fill colors, select Blink, opening the blink palette. 4. For the first blink color, select gray. For the second color, select yellow. 5. Repeat step 4 for the fill blink colors. To set up the color for the second warning 1. In the thresholds and colors list, select C. 2.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Moving an object horizontally in a display Use horizontal position animation to move an object horizontally in a display, based on the result of an expression or a tag value, in relation to the specified minimum and maximum values. The object’s horizontal position is proportional to the value of the expression.
The following illustrations show how the rotation range and the center of rotation work. The object rotates when tag values fall within this range. The object stops rotating when tag values fall within this range. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Tag values With the center of rotation inside the object, at the top-left corner, this object rotates from zero to 180 degrees as its tag value changes.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Changing the height of an object Use height animation to change an object’s height, based on the result of an expression or a tag value, in relation to the specified minimum and maximum values. The object’s height is proportional to the value of the expression. For example, if the value of the expression is halfway between its minimum and maximum values, the object will be half its full height.
For details about Vertical Slider options in the Animation dialog box, click Help. Animating OLE verbs Use OLE verb animation to set up OLE objects to perform certain actions. When the expression evaluates to true—that is, when the expression does not equal 0— the specified OLE verb is activated. The verbs available depend on the OLE object. Typical verbs include open and edit. For details about OLE Verb options in the Animation dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Checking an object’s index number To check an object’s index number, double-click the object to open its Properties dialog box, and then check the number in the Tab index box, as shown in this illustration: The Properties dialog box for the selected input object shows the object has tab index number 1.
Creating a tab sequence You can use index numbers to create a tab sequence. The tab sequence is the order in which users can move through a series of objects in a graphic display, using the Tab key. In the following illustration, the tab order is from left to right: The circled numbers above the objects show each object’s index number. The boxes are numeric input objects. The grouped drawing objects have object key animation. The buttons are button objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Changing index numbers Once you have created two or more objects that have index numbers, you can change the index numbers. For example, if you have created four input objects, you can modify the fourth object to have index number 1. However, you cannot change the fourth object to have index number 5, because there are only four input objects in the display.
To open the Object Keys dialog box Right-click the object you want to set up keys for, and then select Object Keys. For details about options in the Object Keys dialog box, click Help. Example: Using object keys to open and close valves A graphic display shows a tank with two valves, named Valve 1 and Valve 2. The valves control the flow in and out of the tank.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up display keys Use display keys to connect a graphic display with one or more keys. Display keys are similar to object keys, except you don’t have to select an object in the display, for a display key to respond. For example, you could connect a display to the F6 key. At run time, when the display is open, the operator can press F6 to perform the key’s press, repeat, or release action.
• • • • • 18 • ANIMATING GRAPHIC OBJECTS 18 • Placeholder Label Modifiers Key The key list shows all the object keys set up for the selected object first, followed by all display keys. Key labels are as specified in the Object Keys or Display Keys dialog box. The key list does not separate the two types of keys because this distinction does not matter to an operator. The operator only needs to know what will happen a key is pressed. To show the key list Use the /O parameter with the Display command.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Example 1: Creating display-wide keys to open and close valves Imagine you have a graphic display containing 20 valves and you want the operator to be able to open and close all the valves with the same two keys, F2 and F3, respectively. Instead of specifying the tag name for each valve, use the [tag] parameter with display keys. Set this up as follows: 1. In the Display Keys dialog box, assign the F2 and F3 keys. 2.
Imagine you want to have HMI tag alarm information available for a specific machine. If something goes wrong and causes an alarm, you want the operator to be able to show an alarm summary for that machine. To show the HMI tag alarm summary for the machine, the operator can position the cursor over any object related to that machine in a graphic display, and then press a Display Key. 1. Create an HMI tag alarm summary that uses a filter containing only the alarms for the machine.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE You can also change an ActiveX object’s properties without using tags. If you choose this method, the object’s properties do not change dynamically at run time. You make static changes to an ActiveX object’s properties just as you do for any other graphic object—in the Properties tab in the Property Panel. For more information, see “Viewing object properties in the Property Panel” on page 16-6.
• • • • • 18 • ANIMATING GRAPHIC OBJECTS About ActiveX object names To identify the object when logging its events. For information about ActiveX events, see “Connecting tags to an ActiveX object’s events” on page 18-26. With commands. For example, when using the Invoke command to call a method, you must specify the name of the object in which the method is implemented. For more information, see “Connecting tags to an object’s methods” on page 18-26.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Connecting tags to an object’s methods A method is an action the ActiveX object can perform. Methods are part of the object. You can: View a list of the object’s methods. Find documentation for the object’s methods. Use the Invoke command to call the object’s methods. Using the Invoke command to call a method Use the FactoryTalk View Invoke command to call a method for the named ActiveX object.
• • • • • 18 • ANIMATING GRAPHIC OBJECTS 18 • Placeholder Click here to open the Command Wizard. Click here for information from the vendor, about the object and its events. For details about options in the ActiveX Control Events dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 18–28
19 • Placeholder 19 Setting up navigation This chapter describes: What a display hierarchy is. Setting up ways to move among displays in an application. Setting up keys to run FactoryTalk View commands. Creating and running client key components.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The following illustration shows a simple display hierarchy design for a network distributed application that contains two areas: Main Menu Graphic Display Process-Wide Alarm Summary Area 1 Process Overview Area 2 Process Overview Management Summary Process 1 Monitoring Process 2 Monitoring Process 3 Monitoring Process 4 Monitoring Process 1 Trend Display Process 2 Trend Display Process 3 Trend Display Process 4 Trend Display For a live ex
To do this Run this command Open the specified graphic display. Display If the specified display is already open and it allows multiple running copies (set up in the Display Settings dialog box), the Display command opens another copy of the display and makes it active. If the specified display is already open and it does not allow multiple running copies, the Display command makes the display active. A display of type: Replace opens on top of other open displays, and closes the ones it overlaps.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For more information about where commands run, see Appendix A, FactoryTalk View commands. Example: Setting up navigation using keyboard operation The graphic display in this example is designed to act as a menu, by providing keys that an operator can press to open graphic displays representing different processes.
The graphic display in this example contains buttons that an operator can click using a mouse, or press on a touch screen, to open detail displays. This display acts as a menu and presents information. To create the buttons, the designer used the Button drawing tool in the Graphics editor. The buttons can be selected with a mouse or by pressing a touch screen. For information about creating buttons, see “Creating the different types of push buttons” on page 17-11.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If you want a display to replace any open displays that it covers or touches when it opens, use the Replace option. You select a type for a graphic display in the Display Settings dialog box. For more information, see “Specifying the display type” on page 16-42. Displays that you want to run in a fixed position, for example, menus or banners, can be docked to the inside of the FactoryTalk View SE Client window.
• • • • • 19 • SETTING UP NAVIGATION General rules governing precedence For example, you could assign the F2 key to open a valve when the valve object has input focus, close a popup display that has focus, and, as a client key, to open a graphic display containing a process overview. When a single key has more than one definition, the following rules of precedence apply: When a graphic display is active and an object has input focus, object keys have precedence over display keys and client keys.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE an object key to jog the motor’s position, pressing F2 when the slider has input focus will always jog the motor’s position, instead of increasing the motor’s speed. However, if a key that triggers an action in an embedded ActiveX object is also defined as a client key, pressing that key will trigger both the action defined for the embedded object and the action defined for the client key.
Press this key Perform the press and release actions for the button object that has focus. Enter 19 • Placeholder To do this Download the value in the input object that has focus. Open the Recipe dialog box when a recipe object has focus. If Ctrl+W was pressed previously, the recipe is saved. If Ctrl+R was pressed previously, the recipe is restored. Open the on-screen keyboard, if the input or recipe object with focus is set up to display the keyboard. Upload data into all input objects in the display.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To do this Press this key Cut the selected items and place them in the clipboard. Ctrl+X, or Shift+Del Paste the contents of the clipboard at the current cursor position. Ctrl+V, or Shift+Ins Position the cursor at the beginning of the data entry object. Home The arrow keys perform different actions when a trend graphic object has focus. For details, see page 23-30.
Activate the display navigation functionality using the FactoryTalk View SE Client. Specify what displays to track using the Properties tab in the Display Settings for each display. This provides flexibility in tracking only the displays you specify. For additional details, click on Help in the FactoryTalk View SE Client wizard. See also “Setting up the properties of a graphic display” on page 16-41.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 2. Drag the mouse to position and draw a shape the general size and location you intend the button to be. When you release the mouse button, the Navigation Button Properties dialog box opens. 3. Make your changes on the Navigation Button Properties dialog box. 4. Close the dialog box. 5. Save your changes. Setting up the properties for a navigation button 1.
General appearance under Appearance. Type of action the button initiates under Action. Touch-insensitive margins under Touch margins. Audio (whether the button beeps at run time) under Other. 19 • Placeholder 4. Click the Active Appearance and Inactive Appearance tabs to specify how the button looks at run time. 5. Click the Common tab to set up how the navigation button will appear at run time. For additional details on the Navigation Button Properties dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 19–14
20 • Placeholder 20 Creating expressions This chapter describes: What expressions are and where you can use them. Working in the Expression editor. Using tag names and tag placeholders in expressions. Using constants in expressions. Using operators to modify values. Using built-in functions. Using if-then-else logic.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Working in the Expression editor Editors that can use expressions contain an Expression box. The editors might also contain expression buttons, and an Expression column. For example, the following illustration shows the Expression box, buttons, and column in the Events editor. Type the expression in the Expression box. Select from lists of components, to help build the expression. Check the syntax of the expression.
20 • Placeholder Click *** to open the Expression editor. If the button has no caption, the property does not allow an expression. Expression components You can build an expression using any of the following components: Tag values (or tag placeholders) Constant values Mathematical, relational, logical, and bitwise operators Built-in functions If-then-else logic To select components, click the following buttons in the Expression box or editor.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Checking the syntax of an expression Use the Check Syntax button to verify that the expression you typed uses correct syntax. If the syntax is invalid, an error is shown in the Check Syntax box. You can check the syntax at any time while the Expression editor is open. In editors with an Expression box, the syntax is checked automatically, when you click Accept or OK.
• • • • • 20 • CREATING EXPRESSIONS Using tag names and tag placeholders in expressions To supply a tag name, type it in the Expressions box, or click Tags to browse for and select a tag in the Tag Browser. Enclose tag names that contain dashes or start with a number in brackets {} when you use them in an expression. Use brackets when using wildcard characters (* or ?) to represent multiple tags in an expression. You can use wildcards, for example, when using HMI tag alarm functions.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE String constant (“character string”) Pi string (to represent the symbol π) FactoryTalk View replaces the string with its numeric value. Using operators to modify values in expressions To modify the values returned to an expression, use arithmetic, relational, logical, or bitwise operators. Arithmetic operators Arithmetic operators calculate values based on two or more numeric values.
• • • • • 20 • CREATING EXPRESSIONS Relational operators The following table describes the relational operators, with examples. (For the numeric examples, tag1 = 5 and tag2 = 7. For the string examples, serial_no = ST009.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Symbols Operator Action Example OR, || or NOT negation If either or both statements are true, returns a 1. Reverses the logical value of the statement it operates on. (tag1>tag2) OR (tag1==5) tag1==5 is true; returns a 1. NOT (tag1
For these examples tag1=5 (binary 0000 0000 0000 0101) and tag2=2 (binary 0000 0000 0000 0010) tag1&tag2 Returns 0 (binary 0000 0000 0000 0000) tag1|tag2 Returns 7 (binary 0000 0000 0000 0111) tag1^tag2 Returns 7 (binary 0000 0000 0000 0111) tag1>>1 Returns 2 (binary 0000 0000 0000 0010) tag1<<1 Returns 10 (binary 0000 0000 0000 1010) ~tag1 Returns –6 (binary 1111 1111 1111 1010) Evaluation order of operators In expressions with more than one operator, evaluation order is determined as follows: Operator
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Evaluation order Symbols 3 * / MOD, % ** AND, && & >> << + – OR, || | ^ EQ, = NE, <> LT, < GT, > LE, <= GE, >= 4 5 Examples: Evaluation order In the following examples, tag1 = 5, tag2 = 7, and tag3 = 10. _____________________________ (tag1>tag2) AND (tag1tag2=0 2. tag1
• • • • • 20 • CREATING EXPRESSIONS The expression evaluates to 1 (true). 20 • Placeholder _____________________________ NOT tag1 AND tag2>tag3 ** 2 is evaluated in this sequence: 1. NOT tag1=0 2. 0 AND tag2=0 3. tag3 ** 2=100 4. 0>100=0 The expression evaluates to 0 (false). Using built-in functions in expressions The following sections describe the built-in functions you can use in FactoryTalk View SE expressions. Many of the built-in functions check for specific true and false conditions.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE This function Returns this value COSD (expression) TAND (expression) ARCSIND (expression) ARCCOSD (expression) ARCTAND (expression) The cosine of the expression in degrees The tangent of the expression in degrees The arc sine of the expression in degrees The arc cosine of the expression in degrees The arc tangent of the expression in degrees File functions Use the built-in file functions to check whether a file exists, or to check the amount of free
• • • • • 20 • CREATING EXPRESSIONS Time functions This function Returns TIME(“time”) BEFORE_TIME(“time”) 1 (true) if the time specified is the current time. 1 (true) if the expression is evaluated before the specified time. 1 (true) if the expression is evaluated after the specified time. 1 (true) if the specified time interval has elapsed— the interval timer starts running when an event file starts running.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE ":00 aug 22 mon 2005 17:" The validity of the date is not checked. For example, if Aug 22 2005 is not a Monday, this error is not detected. Example 2: Less specific time parameters Following are valid examples of time parameters: “17:00” means any day at 5:00 a.m. “ :30 ” means any hour, on the half hour “ mon 17:” means 5:00 p.m.
BEFORE_TIME(“aug 21 2005”) Returns 1 (true) the first time the expression is evaluated before August 21, 2005. INTERVAL(“1 min”) Returns 1 (true) if a minute has elapsed since the expression last returned a 1. (tag1>500) and INTERVAL (“30 sec”) Returns 1 (true) when tag1>500 on some 30-second interval since the event file started running. (It does not mean 30 seconds after tag1>500.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE This function Returns this value alm_in_alarm(tag or alarm event) or 1 (true) if the tag or alarm event is in alarm.
To examine multiple tags at once, use a wildcard character in the expression argument. This wildcard character Does this ? * Matches any single character. Matches any number of characters, including the backslash (\) character. Example: HMI tag alarm functions ALM_IN_ALARM(/Ingredients::vessel3\TIC3\pv*) Returns 1 (true) if one or more tags in the specified folder have a name beginning with the letters pv and are in alarm. Returns 0 (false) if none of the specified tags are in alarm.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Language function Use the built-in language function to return the name of the current run-time language. An expression containing this function is evaluated whenever a language switch occurs. This function Returns this value Example CurrentLanguage The RFC1766 name of the current run-time language. CurrentLanguage() Returns en-US, if the current run-time language is English (United States).
This wildcard character Does this ? * Matches any single character. Matches any number of characters, including the backslash (\) character. For more information about using FactoryTalk alarm functions in expressions, and for examples, see Chapter 12, Setting up FactoryTalk alarms.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE If the statement is true then the expression returns value1; if the statement is false then the expression returns value2. Keep in mind that the statement is a mathematical equation and true means a non-zero value, and false means zero.
statement1 20 • Placeholder enter true false statement2 true false value3 • • • • • 20 • CREATING EXPRESSIONS value2 value1 exit Example 2: Nested if–then–else This expression: If statement1 Then If statement2 Then value1 Else value2 Else value3 is interpreted in this way: 20–21
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE enter statement1 false value3 exit 20–22 true statement2 false value2 true value1
21 • Placeholder 21 Creating embedded variables This chapter describes: What embedded variables are. Where you can insert embedded variables. How to create numeric embedded variables. How to create string embedded variables. How to create time and date embedded variables. How embedded variables are shown at run time. How embedded variables are updated at run time.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Inserting embedded variables You can insert one or more embedded variables in the: Captions you create for graphic objects. For objects with multiple states, you can insert different embedded variables in each state’s caption. For information about creating specific graphic objects, see Chapter 17, Creating graphic objects. Local messages you create in the Local Messages editor. For information about creating local messages, see page 17-36.
• • • • • 21 • CREATING EMBEDDED VARIABLES To insert an embedded variable in the tooltip of a graphic object 2. In the Common tab, click the Insert Variable button beneath the ToolTip text box, or right-click the ToolTip text box, and then select Insert Variable. 3. Click the type of variable you want to insert (Numeric, String, or Time/Date). 4. Fill in the options in the dialog box that opens. For details, click Help. Tooltips can consist of a single line of text, or multiple lines.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In the Numeric Variable dialog box, select the Tag option to show the value of the specified tag (or tag placeholder) in the embedded variable at run time. Select the Literal number option, to show the number you type in the dialog box, or the parameter value that replaces the tag placeholder. Formatting options (Number of digits, Decimal places, Fill left with) apply to either a tag value or a literal number.
• • • • • 21 • CREATING EMBEDDED VARIABLES where L indicates that the embedded variable will contain a literal number. N indicates that it is a numeric embedded variable. # indicates the number of digits. ### is the literal number (or tag placeholder). Fill_character is the fill character: NOFILL, ZEROFILL, or SPACEFILL. # indicates the number of decimal places.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Select the Literal string option, to show the text string you type in the dialog box, or the parameter value that replaces the tag placeholder. The literal string you type (or specify in a parameter file) cannot contain spaces. Formatting options for fixed number of characters apply to either a tag value or a literal string.
L indicates that the embedded variable will contain a literal string. S indicates that it is a string embedded variable. # indicates the fixed number of characters to display. In the String Variable dialog box, if you don’t want to use a fixed number, clear the check box, Fixed number of characters. SSS is the literal string (or tag placeholder).
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For details about options in the Time and Date Variable dialog box, click Help. For information about how embedded variables are updated at run time, see page 21-10.
• • • • • 21 • CREATING EMBEDDED VARIABLES Numeric embedded variables For example, if 6 is the number or digits specified, the floating point value 1234.56 is rounded to 1234.6, and the value 1234.44 is rounded to 1234.4. The decimal point counts as one of the digits. If the value is negative, the minus sign also counts as a digit.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Time and date formats Time and date embedded variables use the time and date formats you set up on the runtime computer. For example, if the time and date variable shows the short date, at run time the variable will use the short date format set up for the run-time computer.
22 • Placeholder 22 Setting up data logging This chapter describes: What data logging is. Data log storage formats. Creating a data log model. Working with ODBC data sources. Creating new files at run time. Switching log paths at run time. Logging on demand. Modifying existing data log models. Starting and stopping data logging. About data logging Data log is a FactoryTalk View component that collects and stores tag values.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using multiple data log models At run time, up to 20 data log models can run simultaneously on each FactoryTalk View SE Server. Use multiple data log models to: Store related information in separate file sets. Log groups of tags at different rates. Log groups of tags based on events. Data log storage formats Logged data is stored either in an internal file set or in an ODBC-compliant database.
is a text string you can specify to help identify the log file. The maximum string length is 20 characters. <(type)> is the file type. The type is enclosed in parentheses. There are three file types: Tagname, Float (for analog and digital tag values), and String. Example: Parts of a data log long file name The data log file named 2006 10 30 0004 Oven Temperatures (Float).dat was created October 30 2006: 0004 indicates that this is the fourth file set created that day.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Tag table (optional) stores tag names in an index so that they can be referenced using a 2- or 4-byte numeric field (rather than a 40-byte character field) in the float and string tables. ODBC backup files are stored as binary files with the extension .obf. You cannot view the contents of .obf files. How ODBC tables are named The ODBC tables are created with the default names TagTable, FloatTable, and StringTable.
Contains SQL data type Length Status Blank if communications are working properly. SQL_VARCHAR, or SQL_CHAR 1 E if a communication error occurred while FactoryTalk View was trying to acquire the tag value. 22 • Placeholder This column S if the tag value is stale; that is, if the value has been acquired before, but has not been updated. U if the tag is uninitialized. Internal tag marker.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the Data Log Models editor 1. In FactoryTalk View Studio, in the Explorer window, open the Data Log folder 2. Right-click the Data Log Models icon, and then select New. You can also open the Data Log Models editor by dragging its icon into the FactoryTalk View Studio workspace, or by double-clicking an existing Data Log Models component. Set up general data log model properties. Specify paths the data will be logged to.
• • • • • 22 • SETTING UP DATA LOGGING Selecting the ODBC database format To create tables for a new data source, click Create Tables. If FactoryTalk View cannot create the tables automatically, you will have to open the database using its editing tool, and create the tables manually. To extend the length of the message to 1999 for a Microsoft SQL Server or Oracle database, click Extend table. The default length of the message is 254. You can only extend the table when the length is between 254 and 1999.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Setting up and managing data log files In the Data Log Models editor, use the File Management tab to specify when to start new files and when to delete old files. Creating new file sets If the data log model uses file sets, you can set up data logging to create new file sets: Periodically. At specified times. When a particular event occurs. Never. This means that all data will be logged to one file set.
• • • • • 22 • SETTING UP DATA LOGGING You can also combine types of logging. For more information, see page 22-14. Choosing the data to be logged In the Data Log Models editor, use the Tags in Model tab to specify which tags will be scanned for data. A data log model can contain up to 10,000 tags. For details about options in the Tags in Model tab, click Help. Logging data to ODBC data sources You can store logged data in an existing ODBC data source, or you can create a new ODBC data source.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 2. Click Create Tables. FactoryTalk View automatically creates new data log tables in the existing database. You can also create tables manually. 3. Set up the rest of the data log model, as described in Help. Creating a new ODBC data source To create a new ODBC data source, click the browse (...) button next to the ODBC Data Source text box, or use the ODBC Data Source Administrator in the Windows Control Panel.
You can use the DataLogNewFile command anywhere you can type a FactoryTalk View command or macro. To provide operators with a way to create new files at run time, create a button object in a graphic display, or a display key or client key, that uses DataLogNewFile as the press action. Switching log paths at run time FactoryTalk View lets you specify a secondary or backup path to be used in the event the primary path for file sets, or the ODBC database, becomes unavailable.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For example, if the data log file is locked, data is buffered for the maximum time (in minutes) you specify to buffer data before attempting a switchover. When the buffer time elapses, a new set of files is created on the primary path. If the model is logging to the secondary path and the file is locked, the behavior is the same: the data is buffered, and then a new file set is created when the specified time period has elapsed.
Moving data from the secondary path When you begin writing to or reading from a data log model, if there are files in the secondary (or backup) path, FactoryTalk View sends a message to the FactoryTalk Diagnostics log. You must move these files manually to the primary path or ODBC database. To do this, use the FactoryTalk View command DataLogMergeToPrimary.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using the DataLogSnapshot command You can use the DataLogSnapshot command with either of these parameters: DataLogSnapshot (where is a data log model name) records tag values for all tags in the specified model at the instant the command is run. DataLogSnapshot * records tag values for all tags in all running models at the instant the command is run.
22 • Placeholder 2. Type the DataLogSnapshot command with the or * (asterisk) parameter, anywhere you can use a macro or command. Modifying existing data log models You can modify a data log model during development or at run time, using either FactoryTalk View Studio or the FactoryTalk View SE Administration Console. If you change a model at run time, the changes will not take effect until you stop and then restart data logging.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE These changes take effect immediately, but only apply to the current logging session. When you stop and restart logging, FactoryTalk View uses the logging rate and log file identifier specified for the data log model. For details about the DataLogChangeRate and DataLogRenameFile commands, see the FactoryTalk View Site Edition Help. Starting and stopping data logging There are many ways to start and stop data logging.
In the Events editor, type the DataLogOn command in the Action box for an event. At the command line in FactoryTalk View Studio, or the FactoryTalk View SE Administration Console, type DataLogOn and then press Enter. Ways to stop data logging To stop data logging only, use one of these methods: Use the DataLogOff command (where is the name of the data log model) to stop a single model. To stop all data log models, use the DataLogOff * command.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 22–18
23 • Placeholder 23 Setting up trends This chapter describes: What trends are. How to create trends. The parts of a trend. Trend chart styles. Choosing colors, fonts, lines, and legends for a trend. Using shading to compare pens. Using overlays to compare real-time and historical data. Using trend templates. Working with trends at run time. About trends A trend is a visual representation, or chart, of current or historical tag values.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Historical data from a FactoryTalk Historian Site Edition server and a FactoryTalk Historian Machine Edition module (only for network distributed or station applications). In a network distributed application, you can plot historical data from data log models in local or remote areas of the application. For more information about data log models, see Chapter 22, Setting up data logging.
• • • • • 23 • SETTING UP TRENDS 23 • Placeholder To create a trend object 1. In the Graphics editor, create a new graphic display, or open an existing one. Trend tool 2. Select Objects > Advanced > Trend. You can also click the Trend tool on the Objects toolbar. 3. On the graphic display, drag the mouse to create a box approximately the size you want the trend to be. Providing a name for the trend When you create a trend object, it is given a name by default.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In the Properties tab, in the (Name) row, type the trend’s new name. The name can contain letters, numbers, and the underscore character ( _) ; however, the first character must be a letter, and the name cannot contain spaces.
• • • • • 23 • SETTING UP TRENDS 23 • Placeholder For details about options in the Trend Properties dialog box, click Help. Testing a trend In FactoryTalk View Studio, in the Graphics editor, you can use Test Display mode to test a trend while you are setting it up. If you have set up communications and there is data for the tags, the pens will plot values. When you are finished testing, switch back to Edit Display mode to continue setting up trend properties.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE The following illustration shows the parts of a standard trend chart with two pens, and a three-minute time span. Chart title Trend border Pen with a square symbol pen marker Chart Pen icon Y-axis Y-axis legend Pen without a pen marker X-axis X-axis legend Scrolling mechanism Line legend Current value legend is shown as a column in the line legend. Chart The chart contains the plotted trend data.
• • • • • 23 • SETTING UP TRENDS X-axis legend For XY Plot charts, the x-axis legend shows the scale, or range, of values associated with the selected pen. The number of timestamps or values shown depends on the size of the trend object and the number of vertical grid lines. At run time, you can double-click the x-axis legend, to open the X-Axis tab of the Trend Properties dialog box. You can set up a trend to exclude the x-axis legend. Y-axis The y-axis is the left edge of the chart.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To make it easier for an operator to distinguish one pen from another, use different colors, widths, and symbols (also called markers) for each pen. For an example of how pen markers are used, see page 23-9.
• • • • • 23 • SETTING UP TRENDS Pen icons At run time, if a pen’s current value is within the scale shown on the vertical axis, the pen’s icon is shown. The position of the icon indicates the pen’s most recently recorded value, even if the trend is paused, or if the most recent value has not yet been plotted. Pen markers As shown in the next illustration, pen markers are symbols that indicate data points. A data point is the exact position of a value plotted on a trend chart.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Value Bar The value bar marks the value of each pen in a trend, at the selected position on the trend chart, as shown in the following illustration. The value of each pen plotted on the trend chart at this position The value bar You can position the value bar by clicking anywhere on the trend chart at run time. If you position the value bar on a pen marker, it shows the value of the data point represented by the pen marker.
• • • • • 23 • SETTING UP TRENDS The Standard chart style In a standard chart, the y-axis shows pen values … … and the y-axis legend shows time values. The XY Plot chart style An XY Plot chart plots the values of one or more tags against another tag. Use the XY Plot chart to plot one (or more) tag’s values against another tag’s values instead of plotting one tag’s values against time. For example, you could plot the temperature of a tank against the pressure of the tank.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE In an XY Plot, the y-axis shows pen values … … and the x-axis legend shows pen values. Isolated graphing For charts with multiple pens, the pen values can overlap, or you can isolate each pen in its own horizontal band on the chart. Use isolated graphing to view each pen individually on the trend chart. The band is the area of the trend chart used by an isolated pen. Use the isolated graphing percentage to specify the space between each pen band.
• • • • • 23 • SETTING UP TRENDS 23 • Placeholder Plotting a value across the full width of the chart Use horizontal lines on a trend chart to provide an orientation for your tag data. For example, you can define upper and lower limits for a tag’s value, and then show the limits as horizontal lines in the trend. When the value crosses one of the limits, the tag’s condition is obvious on the trend.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 3. In the Pen Attributes spreadsheet, in the Type column, select Full Width. When the trend runs, the pen shows as a solid horizontal line across the full width of the chart. Choosing trend colors, fonts, lines, and legends In the Trend Properties dialog box, you can set up colors, fonts, lines, and markers for a trend chart and pens.
• • • • • 23 • SETTING UP TRENDS 23 • Placeholder The shaded area is the background of the trend object. You can change the color and style settings for the background using the WindowStyle and WindowColor options in the Property Panel. For details about using the Property Panel, see page 16-6. Showing a current value legend The current value legend can be shown by itself or as part of the line legend, depending on the position of the line legend.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE When the line legend is shown at the bottom of the trend chart, the current value legend is shown as a column in the line legend, as shown in the following illustration. Pen caption Current value legend Min/max values Engineering units Showing a line legend The line legend shows the details of a pen line, including the line color, pen name, the minimum and maximum values, and the engineering units.
Shading between pen values Upper-bound pen Lower-bound pen Example 1: Shading with three pens The upper pen, Pen 2, has a constant value of 75 and the lower pen, Pen 3, has a constant value of 25. Pen 1 represents the tag called VIN_LEVEL. The trend is shaded whenever Pen 1 goes above Pen 2 or below Pen 3. A plot for this trend looks like this: Pen 1 Pen 2 Pen 3 23–17 23 • Placeholder The trend in the following illustration uses shading to indicate tag values in alarm.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To produce the shading shown in the illustration, use the following settings: Pen Tag name or constant value Pen 1 Pen 2 Pen 3 VIN_LEVEL 75 25 Shading Upper Bound Lower Bound Pen 2 Pen 3 Example 2: Shading with two pens Whenever Pen 1 goes above Pen 2, the trend is shaded like this: Pen 1 Color 1 Pen 2 To produce the shading shown in the illustration, use the following settings: 23–18 Pen Tag name or constant value Pen 1 Pen 2 VIN_LEVEL
23 • Placeholder Example 3: Shading between two pens Whenever Pen 1 goes above or below Pen 2, the trend is shaded like this: Pen 1 Color 1 Pen 2 To produce the shading shown in the illustration, use the following settings: Pen Tag name or Constant value Pen 1 Pen 2 VIN_LEVEL OIL_LEVEL Shading Upper Bound Lower Bound Pen 2 Pen 2 • • • • • 23 • SETTING UP TRENDS Using overlays to compare real-time and historical data You can layer a trend with a snapshot of previously charted data.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For information about setting up the trend’s run-time options, click Help in the Runtime tab of the Trend Properties dialog box. To create a snapshot 1. Right-click the trend you want to get a data snapshot from, and then select Create Snapshot. 2. In the Component Name dialog box, type a name for the snapshot, and then click OK. To add a snapshot to the trend as an overlay 1.
• • • • • 23 • SETTING UP TRENDS Using trend templates 23 • Placeholder You can use a trend template to: Apply a consistent appearance to trend charts. Create a set of different views for the same data. Return to a standard display after experimenting with display options. Save pen attribute data. Use the Trend Properties dialog box to create a trend template. For details about options in the dialog box, click Help.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Loading trend templates Load a template to return to the original trend settings, or to apply a consistent trend appearance across applications. To load a template 1. In the Trend Properties dialog box, click the Template tab, and then click Load template. 2. In the Component browser, find and select the template you want to load, and then click OK. Saving, loading, or deleting a template takes effect immediately, and cannot be undone.
• • • • • 23 • SETTING UP TRENDS About the Trend graphic library To open the Trend graphic library 1. In FactoryTalk View Studio, in the Explorer window, open the Graphics folder. 2. In the Libraries folder, right-click Trend, and then select Open. Working with trends at run time How you can interact with a trend at run time depends on the options you set up in the Runtime tab of the Trend Properties dialog box. You might be able to do some or all of the following: View and modify trend properties.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Example: Using a startup macro to load and update a trend in the background 1. Create a startup macro that includes this command: Display Trend1 /ZA where Trend1 is the name of the graphic display containing the real-time trend, and /ZA is the parameter for loading the trend data into the data buffer. Trend data will remain in the cache, and continue to update, until you run the FlushCache command, or until you stop running the application. 2.
• • • • • 23 • SETTING UP TRENDS Selecting pens at run time The y-axis legend shows the minimum and maximum scale for a pen … … when you click the pen line in the line legend. Modifying trend properties at run time Changes made to trend properties at run time are not saved. The changes affect the trend that is running, but as soon as the graphic display is changed or closed, the changes to the trend are lost. To make permanent changes to a trend, open and modify it in FactoryTalk View Studio.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the Y-Axis tab 1. Double-click the y-axis legend. 2. In the Y-Axis tab, make the desired changes, and then click OK. To open the X-Axis tab 1. Double-click the x-axis legend. 2. In the X-Axis tab, make the desired changes, and then click OK. To open the Pens tab 1. Double-click the line legend. 2. In the Pens tab, make the desired changes, and then click OK.
• • • • • 23 • SETTING UP TRENDS Showing the value of pens at various positions Pen values The value bar The color of the value bar changes automatically, so it is visible for all background colors. For example, if the trend background color is black, the value bar color will be white. If the trend background color is white, the value bar will be black. A tilde ( ~) indicates an approximate value. An approximate value is shown when there is no value for the pen at the exact time stamp of the value bar.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Displaying the difference in pen values for two points The delta value bar works with the value bar to show the difference in value between two x-axis points for standard and XY Plot chart types. The value bar The value of the data point at the value bar’s position The delta value bar The difference between the value bar’s data point and the delta value bar’s data point To show the delta value bar 1.
Zooming the trend chart Use zoom to view a selected area of the trend chart in more detail. To zoom, use one of these methods: Right-click and drag the y-axis to zoom vertically. Right-click and drag the x-axis to zoom horizontally. Left-click and drag the chart to zoom into the selected area. To restore the original trend chart view Right-click the trend chart, and then select Undo Zoom/Pan.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Using the arrow keys You can use the arrow keys on the keyboard to perform some of the same functions as the mouse and VCR-style buttons. To do this Press and hold this key And then press this arrow key Move back half a time span. (none) Left Move forward half a time span. (none) Right Pan up 10%. (none) Up Pan down 10%. (none) Down Move back a full time span. Shift Left Move forward a full time span.
• • • • • 23 • SETTING UP TRENDS To show or hide an overlay A check mark beside the overlay name indicates it is visible on the trend chart. No check mark beside the overlay name indicates it is hidden. To open the Overlays tab Right-click the trend chart, select Overlays > Properties. Fixing run-time errors If data for the trend is not available at run time due to communication errors, messages are sent to the Diagnostics List.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 23–32
24 • Placeholder 24 Adding logic and control This chapter describes: What logic and control is. Creating and using macros. Creating and using derived tags. Defining and using events. Creating and using client keys. About logic and control In FactoryTalk View Studio, the Logic and Control folder contains editors for setting up alternative ways of manipulating tag data and issuing commands at run time. You can set up: Derived tags, to derive values from combined tag data.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE To open the Derived Tags editor 1. In FactoryTalk View Studio, in the Explorer window, open the Logic and Control folder. 2. Right-click the Derived Tags icon, and then select New. You can also open the Derived Tags editor by dragging its icon into the FactoryTalk View Studio workspace, or by double-clicking an existing Derived Tags component.
• • • • • 24 • ADDING LOGIC AND CONTROL Form and spreadsheet In the Expression box, create the expression that will determine the derived tag’s value. You can use the buttons beneath the box to build expressions. For more information, see Chapter 20, Creating expressions. Checking the syntax of an expression In the Derived Tags editor, to verify that the expression you typed uses correct syntax, click Check Syntax. If the syntax is invalid, an error is shown in the Check Syntax box.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE These are the tasks involved in setting up derived tags for an application: 1. Create the derived tags in the Derived Tags editor in FactoryTalk View Studio. 2. Set the maximum update rate in the Derived Tag Setup dialog box. 3. Save the derived tags component and give it a name. To create a derived tags component 1. In the Derived Tags editor, specify the tag that will hold the derived value and type a description of the tag. 2.
• • • • • 24 • ADDING LOGIC AND CONTROL Using multiple derived tag components Each HMI server in an network distributed application can run up to 20 derived tag components, with up to 1,000 tags in each component. Modifying existing derived tag components You can modify derived tags during development, or when you run the application. If you change an derived tags component at run time, the changes will not take effect until you stop and then restart derived tags processing.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE At the command line in FactoryTalk View Studio, or the FactoryTalk View SE Administration Console, type DerivedOn and then press Enter.
In the Graphics editor, create a graphic object and then attach touch animation with the DerivedOff command as the object’s action. When the object is touched, derived tags processing stops. For the Logout Macro in the FactoryTalk View SE User Accounts editor, specify the DerivedOff command, or a macro that contains the command. For the Shutdown command in the Display Settings Behavior tab, specify the DerivedOff command, or a macro that contains the command.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Form Spreadsheet Accept and Discard buttons When you enter information in the Events editor, the Prev and Next buttons change to Accept and Discard buttons. Click Accept to save information. Click Discard to cancel changes to the event component. Form and spreadsheet In the upper part of the form, specify the action and provide a description for the event component.
• • • • • 24 • ADDING LOGIC AND CONTROL Checking the syntax of an expression You can check the syntax of an expression at any time while the Events editor is open. The syntax is also checked automatically, when you click Accept or OK in the editor. Creating an events component An event component consists of two parts: an expression and an action. When a component in the expression changes, the expression is evaluated.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE About the maximum update rate The maximum update rate is the fastest rate, at which any event expression in an events component can be updated. The maximum update rate also determines the fastest rate, at which data servers can send changes in tag values. Set a maximum update rate separately, for each events component you create.
In the Macros editor, create a macro that contains the command, EventOn . In the HMI Server Properties dialog box, click the Components tab, select the Macro check box, and then specify the macro. Event detection will start when the HMI server runs. In the Graphics editor, create a button object and then specify the EventOn command as the button’s press action. When the button is pressed, event detection starts.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For the Shutdown command in the Display Settings Behavior tab, specify the EventOff command, or a macro that contains the command. You can also stop events processing by stopping all HMI server components running on the computer. For details, see “To stop HMI server components manually” on page 6-19. Creating and using macros A macro is a series of FactoryTalk View SE commands stored in a macro component.
Do not use dollar signs or percent signs in comments inserted in macros. This causes errors at run time. Example 1: A macro called Factory A macro called Factory contains the following commands: Display /Ingredients::Overview Display /Ingredients::Detail /Ingredients::Valve23=Open When the macro runs, the graphic display called Overview opens, then the display called Detail opens, and then the tag Valve23 is set to its open state. The displays and the tag all are located in the area called Ingredients.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Specifying parameters in a macro Macros can accept up to nine parameters. To specify a parameter in a macro, type a percent (%) sign followed by a number. To run the macro and parameters, specify the macro name followed by the parameters. Separate multiple parameters with spaces.
• • • • • 24 • ADDING LOGIC AND CONTROL Nesting macros The single quotation mark ( ‘ ) is a special character in FactoryTalk View and cannot be used in nested macros. Instead, use the double quotation mark ( “ ) . Example 5: Nesting macros A macro called Draw contains: Display Overview Display Detail and a macro called Factory contains: Draw Valve23=Open With the Draw macro nested in the Factory macro, running the Factory macro performs the same actions as in Example 3.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Specifying user login and logout macros You can assign login and logout macros to any user or group of users listed in the Runtime Security editor, in FactoryTalk View Studio. Any macro component, containing any FactoryTalk View command, can be a login or logout macro. For example, a login macro might contain a command to bring up a specific graphic display in an area of the plant. A logout macro might contain commands to redefine sensitive keys.
• • • • • 24 • ADDING LOGIC AND CONTROL 24 • Placeholder For details about the options in the editor, click the Help button. Running client key components To run a client key component, use one of these methods: Use the FactoryTalk View Key command in a macro or anywhere else you can use FactoryTalk View commands. For details, see the FactoryTalk View Site Edition Help. Run the client key component when the FactoryTalk View SE Client runs.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE 24–18
APPENDIX A FactoryTalk View commands This appendix describes: Where and how to use FactoryTalk View commands. Using absolute and relative references. Creating symbols. Using the Command Wizard. For details about specific FactoryTalk View commands, see the FactoryTalk View Site Edition Help. Using commands in a FactoryTalk View SE application In a FactoryTalk View SE application, you can use commands in: Boxes that require you to enter an action.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Separate multiple parameters with a space. Enclose long file names containing spaces with double quotes when the file names are used as parameters. For example: Display PID /P“Temperature Loop 1” Enclose area and component names that contain spaces, or are ambiguous, in double quotes. An ambiguous area name is one that is the same as another parameter for a command.
Substituting the current values for the tag placeholders in commands in the macro, FactoryTalk View opens displays named Screen1 and Screen2, and then sets a tag named Valve23 to its open state. If a tag placeholder is enclosed in double quotes (“ “) or nested in the string value of another tag placeholder in the command, then FactoryTalk View will not substitute the tag value.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Commands that run at the FactoryTalk View SE Server Acknowledge AcknowledgeAll AlarmAcceptEdits AlarmEvent AlarmLogNewFile AlarmLogOff AlarmLogOn AlarmLogSendToODBC AlarmOff AlarmOn AlarmPrintOff AlarmPrintOn DataLogChangeRate DataLogMergeToPrimary DataLogNewFile DataLogOff DataLogOn DataLogRenameFile DataLogSnapShot DataLogSwitchBack DerivedOff DerivedOn EventOff EventOn HandShakeOff HandShakeOn Silence SilenceAll SuppressOff SuppressOffAll SuppressO
Commands that run wherever they are issued These commands run wherever they are issued. For example, if one of these commands is issued at the FactoryTalk View SE Client, it runs at the client. = (Equal) AlarmLogRemark AppAbort AppActivate AppStart Beep DDEExecute If Pause PlayWave Ramp Remark Set Toggle If you are using Windows 7 Professional, Windows Vista or Windows Server 2008, the AppStart command should not be used with interactive actions that use Events.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE For example, if the current area is called RecipesArea, the graphic display specified using the relative reference IngredientDisplay is resolved to the absolute reference /RecipesArea::IngredientDisplay before it can be used. For commands, relative references are resolved in different ways, depending on the type of parameters the command takes.
To define a symbol At the command line or in a macro or box, type: Define is the abbreviated command, without spaces. is an existing command with or without parameters. It can contain spaces and other symbols. Example: The Define command Define Show Display Overview The Define command The symbol The string In this example, the command Display Overview is replaced with the word Show.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Important guidelines When creating symbols, keep the following in mind: FactoryTalk View does not check for security access on symbol names. Therefore, be sure to put security on the underlying FactoryTalk View command. For information about setting up security, see Chapter 5, Setting up security. If a symbol and a macro have the same name, the symbol runs instead of the macro. The order of precedence is: symbol, command, macro.
To open the command line In FactoryTalk View Studio, in the Explorer window, double-click the Command Line icon. Opening the Command Wizard To open the Command Wizard, use one of these methods: Double-click in an action box, or anywhere in the Macro editor. Click the Browse button beside an action box or any box requiring a FactoryTalk View command. In the Command Line, Runtime Secured Commands editor, Events editor, and Macro editor, from the Edit menu, select Commands.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE A–10
APPENDIX B B • Placeholder Setting up DDE communications for HMI tags This appendix describes: What DDE communications are. How to set up DDE communications with HMI tags. Scanning for new tag values. This section does not apply to Microsoft Windows 7 Professional, Windows Vista or Windows Server 2008. Overview of DDE communications To support legacy applications FactoryTalk View supports DDE communications. The following illustration shows how FactoryTalk View SE might use DDE.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE DDE (Dynamic Data Exchange), used with external DDE servers such as the Rockwell Software RSServer products, or with other third-party servers, allows applications to communicate with a wide range of local and remote devices. DDE servers provide a way to connect to an HMI server’s HMI tags (the DDE client), to communication devices such as Siemens or Modicon, or to third-party DDE servers such as Microsoft Excel or Visual Basic.
B • Placeholder 2. In the Address box, specify the DDE item. Type the DDE address for the tag. The DDE item name and format depend on the DDE server, and are not validated by FactoryTalk View. Syntax for DDE addresses The syntax for DDE tag addresses is: DDE : Application|Topic!Item There are no spaces: Between the application name, the vertical bar, and the topic name. Between the topic name, the exclamation mark, and the item name.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE B–4
APPENDIX C C • Placeholder Using the SE Client object model and display code This chapter describes: How you can use VBA with FactoryTalk View Site Edition. The VBA integrated development environment. The objects in the FactoryTalk View SE Client object model. How to find information about FactoryTalk View SE Client objects. How to find information about VBA.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Send custom messages to the Diagnostics log. Send specific messages to the Diagnostics List and Diagnostics log, to record operation conditions and events through VBA code. Secure the system. The FactoryTalk View SE Client object model allows you to obtain security information about who is using the system, and to use the security information and events to control access to the system.
• • • • • C • USING THE SE CLIENT OBJECT MODEL AND DISPLAY CODE How VBA code runs Events that can be used in this way are defined in the Display Client object model, and include actions such as the display being opened and animated, mouse clicks, and so on. Parts of the VBA integrated development environment The integrated development environment for VBA IDE, is available from the FactoryTalk View Graphics editor. Use the VBA IDE to create, test, and debug VBA procedures.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Project Explorer window For each graphic display, a VBA project named DisplayCode is created. The Project Explorer shows the VBA project for each graphic display that is open in the Graphics editor. Each project contains a FactoryTalk View Studio Objects folder. This folder contains a module called ThisDisplay, which represents the graphic display. The module called ThisDisplay contains the code that interacts with objects on the display.
Represents this feature, collection, or graphic object BackspaceButton The backspace button object. This object works like the Backspace key on a keyboard. The bar graph object. BarGraph Button ControlListSelector Display DisplayListSelector Displays Element Elements Ellipse EmbeddedOLE EndButton EnterButton Freehand Gauge Group C • Placeholder This object in the model The button object. The control list selector object. A graphic display. The display list selector object.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE This object in the model Represents this feature, collection, or graphic object MaintainedPushButton MomentaryPushButton MoveDownButton The maintained push button object.
Represents this feature, collection, or graphic object Tag The tag object. Use the Tag object to provide run-time information for a tag, or to set the value of a tag. A collection of Tag objects. TagGroup TagLabel Text TimeDateDisplay Wedge C • Placeholder This object in the model The tag label object. The text object. The time and date display object. The wedge object. Viewing the objects Use the Object Browser in the VBA IDE to view the FactoryTalk View SE Client objects.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Finding information about FactoryTalk View SE Client objects The FactoryTalk View SE Help contains detailed information about the objects, properties, methods, and events in the FactoryTalk View SE Client object model. To open context-sensitive Help In the Object Browser, click the item, and then press F1, or click the ? button on the toolbar.
APPENDIX D D • Placeholder Importing and exporting XML files This appendix describes: What XML is. Exporting FactoryTalk View graphics data to XML files. Modifying exported XML files. Importing graphic display XML files. The XML file structure for graphic displays. About XML XML is the Extensible Markup Language used to create documents with structured information. XML has a standardized format and structure.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE FactoryTalk View creates XML files for the selected graphic displays, in the location you specify. In the same location. FactoryTalk View also creates a file called BatchImport_Application name.xml. Use this file to import several displays at once. To import a different set of displays than you exported, modify the list of displays names in the BatchImport_Application name.xml file.
• • • • • D • IMPORTING AND EXPORTING XML FILES To test an XML file Open the XML file in Internet Explorer. If you can see the XML code, your file is well-formed. If the XML code is not wellformed, Internet Explorer displays an error message. Importing XML files You can import graphic display information in an XML file that has been created using an external editor, or you can import an XML file that you originally exported from FactoryTalk View and then modified.
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Graphic display XML file structure The graphic display XML file is an FactoryTalk View XML document that describes the objects and settings for a graphic display. The root element of the XML document is called gfx. It represents the graphic display. An XML document can contain only one root element. All other elements must be contained within the beginning and end markers of the root element.
Element • • • • • D • IMPORTING AND EXPORTING XML FILES Description D • Placeholder
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Element Description D–6 Contains elements for a VBA code item. Contains the VBA source code. Indicates the end of the vbaCode element. Contains the encrypted code information if the VBA code item is a user form, module, class module, or procedure. Indicates the end of the encryptedData element. Indicates the end of the vbaItem element.
Index Symbols .bmp files 16–31, 16–32 .cab files 17–58 .dat files 22–1, 22–2 .dxf files 16–31 .ggfx files 16–28 .gif files 16–31 .jpg files 16–31 .pcx files 16–31 .tif files 16–31 .wmf files 16–31 .
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE states for 17–44, 17–47 top position tag 17–48 value tag 17–46, 17–48 visible states tag 17–48 recipe object 17–34 selecting using keyboard 17–10 tag label 17–34 creating 17–35 time and date display 17–34 creating 17–35 trends See trends Alarm and Event Historian 12–31 alarm and event history logging 12–30 alarm and event objects 17–2 alarm banner 12–11 alarm status explorer 12–11 alarm summary 12–11 log viewer 12–11 selecting using keyboard 17–10 See
for multiple users 3–14 network layout 3–2 security 3–9 trends 3–13 redundant servers in 14–1, 14–8 referencing components in 6–7 Sample Water 1–9 setting up run time 3–11 switching languages in See language switching arc graphic object 17–6 architectures redundancy 3–3, 6–14, 14–11 areas 6–6, 7–5 adding to an application 6–11, 7–7 application root 8–2 deleting 6–11, 7–7 home area 6–6, 7–5, 10–7 in Execute command parameters 11–40 in network applications 6–2, 7–2 maximum number of HMI servers 6–14 showing i
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Common actions See security permissions, Common actions communications 9–1 DDE See DDE communications error function 20–16 planning 3–5 computer accounts 5–26 condition-related events 12–6 Connections tab 16–23 constants 20–5 control See animation control list selectors 17–33, 17–42, 17–47 controller instruction faceplates adding to an application 16–30 creating display templates 3–12 Crystal Reports See Business Objects Crystal Reports current applicat
Define command A–7 deploying network applications changing HMI server properties starting and stopping the server 6–19, 7–11 derived tags commands DerivedOff 24–6 DerivedOn 24–5, 24–6 creating 24–4 limits 24–5 maximum update rate for 24–4 modifying 24–5 deviation alarms 12–9 device-based alarms 11–2, 12–2, 12–3 Diagnostics List 2–6, 15–7 clearing messages 2–7, 15–8 hiding and showing 2–8 Diagnostics Viewer 15–9 opening at run time 15–9 disabling alarms 12–48 display cache 16–44, 19–6 adding displays 16–50 r
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE time and date variables 21–7 syntax 21–8 types of values in 21–1 updating at run time 21–10 enabling alarms 12–42, 12–48 Enter key 17–43 handshaking 17–43, 17–46, 17–48 resetting the Enter tag 17–47 turning off 17–62 error messages 15–3 event-based alarms 11–22 events commands EventOff 24–11 EventOn 24–11 creating 24–9 evaluation interval for 24–10 for ActiveX objects 18–26 for on-demand logging 22–14 limits 24–10 maximum update rate for 24–10 modifying
alarm and event policies 12–16 alarm and event summary 12–11, 12–33 alarm monitoring in 12–38 filtering and sorting data 12–40 parts 12–39 alarm class 12–12 alarm displays 12–10, 12–32 alarm faults 12–8 alarm history logging 12–22 alarm logs 12–14 alarm messages 12–14 alarm monitoring security for 12–18 setting up 12–15 alarm priority 12–11 modifying 12–12 setting up 12–22 alarm servers RSLinx Enterprise 12–18 Tag Alarm and Event Servers 12–21 alarm severity 12–11 alarm states 12–13 alarm status explorer 12
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE Client Keys 24–16 changing passwords 5–7 Data Log Models 22–6, 22–9 computer accounts 5–25 Derived Tags 24–2 finding information about 5–2 Events 24–7 for local applications 8–4 Expressions 20–2 single sign-on 5–5 Graphics 16–3 system policies 5–27 hints for working in 2–16 system resources 5–29 printing from 2–17 user accounts 5–25 Runtime Security 5–11 FactoryTalk system 14–1 Secured Commands 5–17 FactoryTalk View Suppressed List 11–11, 11–31 Secured
flipping graphic objects 16–17 FlushCache command 16–48, 16–50 running on shutdown 16–48 fonts 17–7 for Windows languages 13–7 in HMI tag alarm summaries 11–35 substituting at run time 17–7 Foreground Color palette 16–21 functions See expressions, built-in functions G gauge and graph objects 17–1 bar graph 17–31 using to compare values 17–30 gauge 17–31 using to show limits 17–29 scale 17–31 global object displays 16–28 at run time 16–29 base objects in 16–3 creating 16–28, 16–29 from standard display 16–29
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE modifying object groups in 16–20 naming objects in 16–23 navigating 19–1 using a hierarchy 3–11, 19–1 using buttons 19–5 using keys 19–4 On Top type 16–43 Overlay type 16–42 patterns for objects in 16–21 positioning displays 16–46 positioning objects 16–8 printing 2–17, 16–54 at run time 2–18 Replace type 16–42 replacing text strings in 16–25 resizing displays 16–44 resizing objects in 16–12 rotating objects in 16–18 running multiple copies 16–43 securi
line properties 16–22 modifying groups 16–20 modifying properties 17–6 names for 16–23 patterns for 16–21 positioning in display grid 16–8 replacing text in 16–25 resizing 16–12 rotating 16–18 selecting 16–9 using keyboard 17–10 spacing 16–16 stacking 16–14 supplying tags for 17–9 testing states 16–27 tooltips 16–24 embedded variables in 21–3 using data in 17–9 using index numbers to navigate 18–15 viewing states 16–27 in Property Panel 16–28 in States toolbar 16–27 Graphics editor 16–3 display area 16–4 sh
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE showing in Tag Browser 10–9 startup components 6–18 using multiple servers 6–13 HMI string tags 10–17 HMI system tags 10–17 HMI Tag Alarm Log Viewer 11–29 HMI tag alarms 10–3, 11–1, 12–4 acknowledging 11–10, 11–13 acknowledge bit 11–13 alarm banner 11–7 alarm displays 11–8 alarm events 11–22 logging 11–23 alarm faults 11–5 alarm log files 11–7 adding remarks to 11–30 creating 11–25, 11–26 limits 11–30 location 11–25 names 11–30 viewing 11–29 alarm loggi
creating 10–22, 10–24, 24–3, 24–8 in Tag Browser 10–15 data sources for 10–17 DDE B–2 deleting 10–23 designing a database 3–8 device tags 10–18 digital tags 10–17 duplicating 10–22 importing 10–25 in Tag Browser 10–15 memory data source 10–24 memory tags 10–3 minimum and maximum values 10–2 modifying 10–22 naming 10–18 offsetting values 10–2 organizing in folders 10–19 scaling values 10–2 setting up alarms for 11–21 setting up security for 5–19, 10–2 string tags 10–17 syntax for OPC addresses 10–23 system t
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE validating operator input 17–24 interactive objects specifying behavior of 16–48 See also advanced objects interlocked push buttons 17–12, 17–17 Invoke command 18–26 K key list 18–20 disabling 18–21 key navigation 17–10 turning off 17–11 key objects 17–1, 17–32 auto-repeat for 17–33 backspace 17–32 End 17–32 Enter 17–32 Home 17–32 Move down 17–32 Move left 17–32 Move right 17–32 Move up 17–32 Page down 17–32 Page up 17–32 Send press to 17–33 keyboard sh
line properties 16–22 list indicators 17–27, 17–29 Loading state 14–4 local applications 8–1 creating 8–5 importing projects 8–6 data servers in 8–2 deleting 8–9, 8–10 HMI server in 8–2 properties 8–7 parts of 8–2 renaming 8–9 security for 8–4 setting up the Local Directory 4–7 structure of 8–1 local message displays 17–34, 17–36 local messages 17–36 embedded variables in 21–2 logging off at run time 5–7 from FactoryTalk View SE 5–4 logging on single sign-on 5–5 to FactoryTalk View SE 5–4 logging paths See
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE adding data servers 6–13, 7–9 ODBC data logging deleting 6–21, 7–14 See data logging HMI servers in 6–2, 7–2 ODBC databases adding HMI servers 6–11, 7–8 for FactoryTalk Diagnostics 15–5 properties 6–15, 7–11 ODBC schemas managing multiple 4–4 See ODBC storage format parts of 6–2, 7–2 ODBC storage format referring to components in 6–7 data log files 22–1, 22–3 renaming 6–21, 7–14, 7–15 offline tags 10–15, 10–16 setting up security for 5–38 offsetting tag
polygon graphic object 17–5 polyline graphic object 17–5 Position command 18–16 precedence among key types 19–7 and embedded ActiveX objects 19–7 and embedded OLE objects 19–8 and the F1 key 19–7 general rules 19–7 shortcut keys 19–10 PrevPosition command 18–16 PrintDisplay command 16–54 printing 2–17 at run time 2–18 selecting a printer 2–18 Procedure window in VBA C–4 procedures in VBA code C–2 Programmatic ID 9–10 Project Explorer in VBA C–4 Properties window in VBA C–4 Property Panel 16–20 assigning exp
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE RSLogix 5000 10–5 run time authorizing operations 17–59 docking displays to client window 12–37, 16–51 font substitution 17–7 global object displays 16–29 preventing scroll bars 16–45 restoring recipes 17–38 troubleshooting trends 23–31 updating reference objects 16–3 running FactoryTalk View Studio 2–1 Samples Water client 1–11 Runtime Secured Commands editor 5–17 Runtime Security See security codes Runtime Security editor 5–11 S Samples Water 1–9 in F
Shift-Tab 18–17 shortcut keys 19–8 Ctrl-PgDn 17–25 Ctrl-PgUp 17–25 Enter 17–25 PgDn 17–25 PgUp 17–25 Tab 17–25 Tab 18–17 square graphic object 17–4 stacking graphic objects 16–14 stand-alone applications See local applications Standby macro See On standby macro Standby state 14–6 Starting state 14–4 Startup macro 24–15 using with trends 23–23 States toolbar 16–20, 16–27 status tags 12–14 string display objects 17–27 string embedded variables 21–5 at run time 21–9 string input objects 17–27 and electronic si
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE planning 3–10 for availability 3–10 for redundancy 14–9 RSLinx Enterprise redundancy 9–6 specifying the secondary server 9–7 switchback options 9–7 switching Active and Standby 14–21 system tags 10–17 for HMI tag alarms 11–10 T tab index 18–15 removing 17–11 tab sequence 18–15 checking index numbers 18–16 creating 18–17 modifying index numbers 18–18 removing objects from 17–11 Tag Alarm and Event Servers 12–6, 12–21 Tag Browser 10–8 browsing offline tag
time functions 20–13 title bar 16–44 toolbars 2–4, 16–4 hiding and showing 2–8 States toolbar 16–27 tooltips 16–24 top position tag 17–48 touch animation 18–14 tracking-related events 12–6 trends 23–1 and the Display command 23–24 as graphic objects 17–34 background color 23–14 chart scale 23–7 charts 23–6 plotting an XY chart 23–11 standard plotting 23–11 comparing data 23–19 comparing pens 23–16 creating 23–3 displaying tag values 23–13 highlighting in a display 17–10 in graphic libraries 23–23 isolated g
• • • • • FACTORYTALK VIEW SITE EDITION USER’S GUIDE VBA code planning how to use 3–14 using to animate ActiveX objects 18–23 using with ActiveX objects 18–26 VBA documentation C–8 VBA IDE C–1, C–3 about procedures C–2 Object Browser C–7 Procedure window C–4 Project Explorer C–4 Properties window C–4 ThisDisplay module C–4 VBA Integrated Development Environment See VBA IDE vertical position animation 18–12 vertical slider animation 18–14 viewing objects C–7 visibility animation 18–8 visible states tag 17–