Factory Talk View SE

(1)

IA-09-L16 – FactoryTalk View SE Lab Manual

Presenter: <<Your name>>

<<Your business group>>

(2)

(3)

(4)

IA-09-L16 — Configuring a FactoryTalk View SE

Application

Before you begin

This lab is intended to be a compilation of several smaller exercises designed to instruct the user on the basics of FactoryTalk View Site Edition. Though the lab can be done linearly, where all exercises are cumulative, the only

required exercises are all of Section 1: Creating your application and Section 2: Importing/Exporting Application

Components. From there, the user may select which exercises interest them most without having to be concerned with numerical order.

The following steps must be completed before starting the lab exercise:

1. If

Log On To Windows dialog is active type ‘administrator’ for Username and type ‘rockwell’ for

password.

2. Use the same Login information if prompted to Log On to the FactoryTalk Directory or when

creating a FactoryTalk Alarms and Events History Database.

About this lab

Welcome to the FactoryTalk View SE Hands-On Lab series. This session provides you with an opportunity to explore the basics of FactoryTalk View Site Edition (FactoryTalk View SE). The following sections explain what you’ll be doing in this lab session and what you will need to do to complete the hands-on exercises.

Note: In v 5.00 (CPR 9), product name changes have taken place to better reflect Rockwell Automation’s

system-oriented software and integrated architecture.

RSView name (CPR 7

and earlier)

FactoryTalk View

name (CPR 9 and

later)

RSView name (CPR 7

and earlier)

name (CPR 9 and

FactoryTalk View

later)

RSView Supervisory Edition (SE)

FactoryTalk View Site Edition (SE)

RSView Enterprise FactoryTalk View

RSView SE Stand-alone FactoryTalk View SE (Local)

RSView SE Distributed FactoryTalk View SE (Network)

RSView SE Client™ FactoryTalk View SE Client

RSView Studio FactoryTalk View Studio

(8)

or machine monitoring, and supervisory control.

In this lab, you will be working with a network application containing an HMI Server, a data server, and a single HMI Client. For this lab, these servers and clients will all be located on the same computer. View Studio, the development environment, will also be on this computer. In the deployed system however, these components could actually be on separate computers, and additional HMI clients could be used, since View SE scales easily from small to large systems. This lab procedure contains content and exercises for both novice and advanced users. After executing the first few sections of the lab you can pick and choose other sections.

It is recommended that users complete remaining lab procedures in the order they are presented, time permitting.

What You Will Accomplish In This Lab

As you complete the exercises in this hands-on session, you will gain an understanding of the functionality and capability of FactoryTalk View Site Edition by

creating an application configuring an HMI server

configuring an RSLinx Enterprise data server and enabling it for alarm and event support utilizing graphics and animation

test running displays

configuring and running an HMI client file

configuring and monitoring alarms (FactoryTalk device and tag based) implementing security

working with data log models and trends using the FactoryTalk Diagnostics Viewer working with Global Objects

configuring your application for language switching

Who Should Complete This Lab

This hands-on lab is intended for individuals who:

Have a basic knowledge of HMI software and are involved in the design and implementation of supervisory-level HMI projects.

Tools & prerequisites

Hardware

This hands-on lab does not require any hardware. A Logix5000 controller could be used in place of SoftLogix 5800.

Note: FactoryTalk Alarms and Events Device Based Alarms requires firmware version 16.20 or higher for

(9)

Software

This hands-on lab uses the following software:

FactoryTalk Services Platform v2.10.00.0117

FactoryTalk View SE v5.00.00.55

RSLinx Enterprise v5.00.00.99

FactoryTalk Alarms and Events v2.10.00.0117 (included with FactoryTalk View Site Edition and

RSLinx Enterprise)

RSLinx Classic (used for Logix programming) v2.52.00.17

RSLogix5000 v16.03.00

SoftLogix 16.03.00 (Bld 42)

Microsoft SQL Server 2005 Express

Microsoft SQL Server Management Studio Express

Microsoft SQL Server 2005 Express Edition is a free, redistributable version of Microsoft SQL Server.

FactoryTalk Alarms and Events uses Microsoft SQL Server as the database engine for logging alarm

and event information. You can connect to an existing SQL Server database, or you can install

Microsoft SQL Server 2005 Express, Service Pack 2, which is included in the Redist folder on the

FactoryTalk View SE and RSLinx Enterprise CDs.

Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical

management tool for managing SQL Server 2005 Express. It is included in the Redist folder on the

FactoryTalk View SE and RSLinx Enterprise CDs.

Lab Files

This hands-on lab uses the following files located in the C:\InstantFizz - Lab Files\ subdirectory:

Language Switching – contains 3 files that will be used in the language switching section of the lab

InstantFizz_Translated.xls

– Translated file for FactoryTalk View SE

InstantFizz_Controller-Tags_translated.TXT

- Translated file for FactoryTalk Alarms and Events device-based alarm messages in RSLogix

5000

InstantFizz_FTAETagServer_Alarm Export_translated.xls

- Translated file for FactoryTalk Alarms and Events tag-based alarm messages in the

FactoryTalk Tag Alarm and Event Server

RSLogix 5000 – contains 1 file that can be used with RSLogix 5000.

InstantFizz_Controller.ACD – control program to be used in this lab

Graphics displays – contains 19 files that have been pre-configured

(10)

cip - process steps.gfx

CIP - Sensor Trend.gfx

CIP - Valves.gfx

CIP Overview.gfx

filling.gfx

labeling.gfx

Languages.gfx

Navigation.gfx

packaging.gfx

Plant Overview.gfx

Rapid Mix - Overview.gfx

Rapid Mix - Process Steps.gfx

Security.gfx

Images – contains 56 pre-configured images

Client – contains a preconfigured FactoryTalk View SE Client file

ClientFile_DockedDisplays.cli

Client Keys - ClientKeys.key

ODBC database - ODBC_InstantFizz.mdb

Graphic XML file - CIP - Process Steps.xml

Exported Tag database - Additional_Tags.CSV

Local Messages – 2 pre-configured files

CIPProcessSteps.loc

RapidMix.loc

Trend Templates – 9 pre-configured Trend Templates

Datalog – CIP.mdf

RSView32 migration files

(11)

Overview

About this lab

This lab will outline the major components and fundamental ideas of FactoryTalk View Site Edition. It will specifically:

Discuss the components of FactoryTalk View SE

Discuss the differences between FactoryTalk View SE Local and Network Application

Discuss HMI Servers, data servers, and Tag Alarm and Event Servers

Discuss FactoryTalk Alarms and Events Services for Device Based and Tag Based Alarms

FactoryTalk View SE Components

FactoryTalk View Site Edition

FactoryTalk® View Site Edition is an integrated software package for developing and running human-machine interface (HMI) applications that involve multiple users and servers, distributed over a network.

A member of the FactoryTalk family of products, FactoryTalk View Site Edition (also called FactoryTalk View SE) provides all the tools you need to create powerful, dependable process monitoring and supervisory control applications.

FactoryTalk View SE software is designed for use with Microsoft® Windows® Server 2003, Windows XP, and Windows 2000 operating systems.

FactoryTalk View Site Edition consists of several pieces of software you can use to build automation applications. Depending on the particular software packages installed, you will have one or more of the following pieces of software: FactoryTalk View Studio, FactoryTalk View SE Client, FactoryTalk View SE Server, FactoryTalk Alarms and Events, FactoryTalk Services Platform, FactoryTalk Administrator Console, FactoryTalk™ Directory, and FactoryTalk Activation.

FactoryTalk View Studio

(12)

Process faceplates are preconfigured to work with various Logix5000 instructions (for example, PIDE, D2SD, and the new ALMD and ALMA instructions). Many of the graphic library objects are preconfigured with animation. Use the objects as they are, or change them to suit your needs.

When you have finished developing an application, use FactoryTalk View SE Client to view and interact with the application.

FactoryTalk View SE Client

Start > Programs > Rockwell Software > FactoryTalk View > FactoryTalk View Client

FactoryTalk View SE Client is a complete runtime operating environment for viewing and interacting with

FactoryTalk View SE local and network applications. To set up a FactoryTalk View SE Client, you need to create a configuration file using the FactoryTalk View SE Client wizard. The HMI Server does not have to be running when you configure a FactoryTalk View SE Client. With the FactoryTalk View SE Client you can:

Load, view, and interact with multiple graphic displays at a time from multiple servers

Perform alarm management

View real-time and historical trends

Adjust set points

Start and stop components on any server

Provide a secure operator environment

And much more!

FactoryTalk View Administration Console

Start > Programs > Rockwell Software > FactoryTalk View > Tools > SE Administration Console

FactoryTalk View Administration Console is for administering FactoryTalk View applications after they have been deployed. FactoryTalk View Administration Console contains a sub-set of the FactoryTalk View Studio editors, so you can make minor changes to an application without the need for installing FactoryTalk View Studio. The FactoryTalk View Administration Console has a two hour run-time limit. A warning message is displayed five minutes before the time is up. To continue using it you simply shut it down and restart it.

FactoryTalk View Administration Console allows you to:

Change the properties of an HMI server.

Change the properties of a data server.

Add FactoryTalk users to an application, using the Runtime Security editor.

Set up security for commands and macros, using the Runtime Secured Commands editor.

Run FactoryTalk View commands from the Command Line.

Change how HMI tag alarms are logged and annunciated, using the Alarm Setup editor.

Change the path of data log models.

(13)

Change which system activities are logged and how frequently, using the Diagnostics Setup editor

(on the Tools menu).

Change the location alarms are logged to, and manage log files, using the Alarm Log Setup editor

(on the Tools menu).

Import and export HMI tags using the Tag Import and Export Wizard (on the Tools menu).

FactoryTalk View SE Server

The FactoryTalk View SE Server, also called the HMI server, stores HMI project components (for example, graphic displays, global objects, and macros) and serves them to clients. The server also contains a database of tags, performs historical data logging, and HMI alarm monitoring. FactoryTalk Alarms and Events can be used instead of FactoryTalk View SE HMI alarm monitoring. To maintain compatibility with existing applications, FactoryTalk View still supports the traditional HMI alarm monitoring.

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

Before FactoryTalk® Alarms and Events (introduced in Version 5.00), FactoryTalk View SE supported only HMI tag alarm monitoring. To maintain compatibility with existing applications, FactoryTalk View still supports this type of alarm monitoring.

However, FactoryTalk Alarms and Events now allows multiple FactoryTalk products to participate together in a common, consistent view of alarms and events throughout a FactoryTalk system. FactoryTalk Alarms and Events supports two types of alarm monitoring:

Device-based alarm monitoring. Pre-built alarm instructions, available in RSLogix 5000 v. 16 or

later, are programmed in a logic project and then downloaded into a Logix5000 controller. The

controller detects alarm conditions and publishes event information, which is routed through the

system for display and logging.

Tag-based alarm monitoring. If you are not using Logix5000 controllers, or if you do not want to use

the pre-built alarm instructions available with RSLogix 5000, tag-based alarm monitoring offers the

equivalent of HMI Tag Alarm Monitoring, but with an expanded feature set. Software-based Tag

Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish

event information for display and logging. Tag-based alarm monitoring is supported for Logix5000

controllers, PLC-5, and SLC 500 devices communicating through Rockwell Automation Device

Servers (RSLinx Enterprise), or for third-party controllers communicating through OPC data

servers.

FactoryTalk Services Platform

FactoryTalk Services Platform provides common services (such as diagnostic messages, health monitoring services, and access to real-time data) to products and applications in a FactoryTalk system.

(14)

Through the lookup service, application components such as tags and graphic displays can be stored in their original environments, and yet be made available to all clients participating in an application.

No duplication is necessary.

FactoryTalk View Site Edition applications use two types of FactoryTalk Directory:

• FactoryTalk Local Directory (also called the Local Directory) manages local applications. All local application components, except for OPC data servers, must be located on the same computer. • FactoryTalk Network Directory (also called the Network Directory) manages network applications.

Network applications can consist of multiple clients and servers, distributed across several computers connected over a network. One Network Directory manages all of the FactoryTalk products that participate in a single network application.

Both the Local and the Network Directory are set up on the computer, when you install the FactoryTalk Services Platform.

FactoryTalk Administration Console

Start > Programs > Rockwell Software > FactoryTalk Administration Console

Part of the FactoryTalk Services Platform, FactoryTalk Administration Console is an optional, stand-alone tool for developing applications and managing a FactoryTalk system. You can use FactoryTalk Administration Console or FactoryTalk View Studio to develop applications and manage a FactoryTalk system. Only FactoryTalk View Studio can be used to create HMI servers and HMI projects.

FactoryTalk Administration Console allows you to:

Create and configure application, area, and data server elements in a FactoryTalk Directory.

Create and configure alarm and event servers, including both tag-based and device-based

servers.

Configure alarm conditions for tag-based alarm detection.

Organize securable actions into groups.

Create database definitions for logging historical alarm and event messages.

Configure options for routing, logging, and viewing diagnostic messages.

Back up and restore an entire directory, an individual application, or system settings.

Set up redundancy for OPC data servers and Tag Alarm and Event Servers.

Configure client computers to recognize the location of a Network Directory Server computer.

Configure system-wide policy settings.

Secure a FactoryTalk system with security services.

FactoryTalk Activation

Start > Programs > Rockwell Software > FactoryTalk Activation > FactoryTalk Activation Tool

(15)

managing software activation files. With FactoryTalk Activation, there is no need for a physical “master disk” or any physical media; instead, activation files are generated and distributed electronically.

FactoryTalk Activation provides these types of activations:

Local node-locked activations are locked to a single computer.

Mobile node-locked activations are locked to a hardware dongle.

Shared concurrent activations are locked to an activation server computer, and shared by client

computers on the network.

There are two types of shared concurrent activation: floating and borrowed. Floating concurrent activation requires a continuous network connection, while borrowed concurrent activation does not.

FactoryTalk View SE - Network and Local

Network Applications

A network application can contain several servers, running on multiple computers on a network, with multiple client users connecting to the application simultaneously, from anywhere on the network. For example, you may use separate servers for different functional areas or locations within your enterprise, and allow clients to interface to any of the servers. Network applications have one or more areas (see Areas definition below), one HMI server per area, and one or more data servers. An area may contain another area within it.

Once you have created the applications and an HMI server, you can use the FactoryTalk View Studio editors in the HMI server project to create application components such as graphics displays, global objects, and data log models.

Areas: A key part of the network architecture system is the area. An area is a logical division within

your application. You can think of areas as partitions of your hard drive. The partitions are all on the

same main disk (or application, in this analogy), but they divide it logically and hold information

independently of each other. An area can also be used to organize the application in a way that

makes sense for the process it is controlling.

For example, an area might represent a portion of a process, or a region within the process facility.

An automotive plant could be divided into areas called Press and Fabrication, Body Shop, Paint

Shop, Engine, and Transmission; a bakery could be divided into areas called Ingredients, Mixing,

Baking, and Packaging. Alternatively, a plant with identical production lines could be divided into

areas called Line 1, Line 2, Line 3, and so on. This would allow you to add new, identical production

lines to the application by copying HMI server projects into new areas.

Root Area: All FactoryTalk View applications have one system-defined area called the root area,

which has the same name as the application. The application root area can contain one HMI server,

and one or more data servers.

(16)

servers that can co-exist in the same area. However, it makes sense to logically organize the data servers that are serving alarms in order for the alarm summary to filter alarms appropriately at runtime. For example, a single area may contain an HMI server for a physical location of a facility, an RSLinx Enterprise data server (configured as a FactoryTalk device based alarm server), and a 3rd party OPC server (configured with the FactoryTalk tag based alarm server). This configuration allows for the alarm summary to filer alarms based on the area name, regardless of which server the alarm comes from.

What you want to avoid is one physical installation of a data server to be referenced multiple times from different areas of the application. This is not necessary because FactoryTalk allows any client to see any data point within the application, regardless of which area it comes from.

*Note: The initial release of FactoryTalk Alarms and Events have different limits than FactoryTalk View SE 5.0. Please refer to the FactoryTalk Alarms and Events Quick Start Guide or Answer ID 44177 within the Rockwell Automation Knowledgebase for more information.

(17)

This is an example of a FactoryTalk View SE network application.

The

Insta Corp application consists of four different defined areas: ie_packaging, ie_production,

is_packaging, and is_production. The areas are marked by the folders that are right off the root,

which is the application

Insta Corp.

Try looking at one of the areas –

ie_packaging, the topmost area. Notice that the HMI server called

IE_CasePack is located inside the area.

The folders under the

ie_packaging HMI Server titled System, HMI Tags, Graphics, Alarms, Logic and

Control, and Data Log are all different components you can configure under each HMI server – they are

not areas within the area, but are actually components of an HMI server.

There is a data server called RSLinx Enterprise located under the root area (Insta Corp). Root Area Network Directory Area Data server HMI Server Area Area Areas HMI Server HMI Server HMI Servers

(18)

The diagram below shows an example system architecture using a Network application as part of a distributed FactoryTalk system.

(19)

Local Applications

A local application is similar to an RSView32 project; all application components and the FactoryTalk View SE client are located on a single computer. There is only one HMI server that is created for you in the root area when the application is created. You may use local applications for parts of the plant or process that are self-contained and are not related to other parts of the process.

The diagram below shows an example system architecture using a Local application as part of a stand-alone FactoryTalk system.

(20)

Creating a new FactoryTalk View SE application

Here are the general steps for creating an application: 1) Create a local or network application

2) If it’s a network application, add one or more Areas

3) If it’s a network application, one HMI server can be added per area (local creates one automatically). Choose to add any of the faceplate displays into the HMI server.

4) Set up data server communications. Add one or more of the following data servers a. Rockwell Automation Device Server

b. OPC Data server

5) Set up Tag Alarm and Event Server

6) Create graphic displays, global objects, and other components into your HMI server 7) Set up historical FactoryTalk alarm and event logging

8) Set up Security

9) Set up a run-time FactoryTalk View SE Client

FactoryTalk View SE – Servers

HMI Servers

HMI servers are software programs that supply information to clients as they request it. An HMI server stores HMI project components such as graphic displays, and serves these components to clients. An HMI server also manages a database of tags, detects HMI tag alarms, and logs historical data.

Data Servers

A data server provides a route to physical devices on the network, allowing applications to monitor and control the values in those devices. For example, data servers can connect application clients to programmable controller values, OPC® tags (and their value or status information), or named variables in a Logix5000 controller.

A data server can be a Rockwell Automation Device Server (RSLinx Enterprise) or a third-party OPC data server that serves up tag values. Once a data server is configured, you can set it up to point to a specific controller such as a ControlLogix processor. Properly configuring a data server allows you to browse for a tag directly.

The following types of data servers are supported:

Rockwell Automation Device Servers (RSLinx Enterprise) provide best performance when

communicating with Logix5000 controllers, or with many clients. You can also use RSLinx

Enterprise servers to subscribe to device-based alarms and events.

OPC data servers (including RSLinx Classic) support any data server that conforms to the OPC-DA

2.0 standard. OPC stands for OLE for Process Control, a protocol that allows FactoryTalk View to

retrieve tag values from:

(21)

Rockwell Automation programmable controllers and devices, using RSLinx Classic or RSLinx

Gateway as an OPC server.

Third-party controller devices, such as Siemens or Modicon®, using third-party OPC servers.

Alarm and Event Servers

FactoryTalk Alarms and Events allow multiple FactoryTalk products to participate together in a common, consistent view of alarms and events throughout a FactoryTalk system. FactoryTalk Alarms and Events support two types of alarm monitoring:

Device-based alarm monitoring. Pre-built alarm instructions, available in RSLogix 5000 v. 16 or

later, are programmed in a logic project and then downloaded into a Logix5000 controller. The

controller detects alarm conditions and publishes event information, which is routed through the

system for display and logging.

Tag-based alarm monitoring. If you are not using Logix5000 controllers, or if you do not want to use

the pre-built alarm instructions available with RSLogix 5000, tag-based alarm monitoring offers the

equivalent of HMI Tag Alarm Monitoring, but with an expanded feature set. Software-based Tag

Alarm and Event Servers monitor controllers for alarm conditions through data servers and publish

event information for display and logging. Tag-based alarm monitoring is supported for Logix5000

controllers, PLC-5, and SLC 500 devices communicating through Rockwell Automation Device

Servers (RSLinx Enterprise), or for third-party controllers communicating through OPC data

servers.

An Alarm and Event Server can be a Rockwell Automation Device Server (RSLinx Enterprise) that is enabled for monitoring device-based alarms or a FactoryTalk Alarm and Event Tag Server that has been configured for monitoring tag-based alarms.

(22)

Section 1: Create and run a simple application

FactoryTalk View Site Edition (SE) can be used to develop and run applications that involve single or multiple users and servers and can be distributed over a network or can be local to a single computer.

The two types of SE applications are explained below:

1. FactoryTalk View SE Local (Stand-Alone) - A local application is similar to an RSView32 project; all

application components and the FactoryTalk View SE client are located on a single computer. There is only one HMI server that is created for you in the root area when the application is created. You may use local applications for parts of the plant or process that are self-contained and are not related to other parts of the process.

2. FactoryTalk View SE Network (Distributed) - A network application can contain several servers,

running on multiple computers on a network, with multiple client users connecting to the application simultaneously, from anywhere on the network. For example, you may use separate servers for different functional areas or locations within your enterprise, and allow clients to interface to any of the servers. Network applications have one or more areas, one HMI server per area, and one or more data servers. An area may contain another area within it.

You can use FactoryTalk View Studio to create application components such as graphics displays, global objects, alarms and data log models.

In this lab we will create and run a network FactoryTalk View SE application.

About This Section

In this section of the lab you will:

Create a Network Application called InstantFizz

Add an area called Area1

Add an HMI Server within Area1 called InstantFizz_HMIServer

Add Process Faceplate Displays into your HMI Project

Add a data server called RSLinx Enterprise

Configure a Communications path called shortcut that will point to the SoftLogix controller

Verify communications

Create a display, add a numeric display object

Test the display

This entire section must be completed prior to doing any other sections in this lab.

Creating a Network HMI Project in FactoryTalk View Studio

We are creating a network application, which supports multiple HMI, Data servers and clients distributed across a network. As explained in detail in the “Overview” section, a network application requires a Network FactoryTalk Directory to be configured. The configuration of the FactoryTalk Directory is generally done during the install, but it can be configured subsequently using the FactoryTalk Directory Configuration

Wizard from Start > All Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Directory Configuration Wizard.

(23)

Once the FactoryTalk Directory has been configured you can specify what computer will be hosting the Directory. The default location of the FactoryTalk Directory is the local computer, but it can be any computer

on your network. Note: For a FactoryTalk View Local application, the Local FactoryTalk Directory must be used.

Specify the FactoryTalk Directory location

1. Specify the FactoryTalk Directory location.

Go to Start > All Programs > Rockwell Software > FactoryTalk Tools > Specify FactoryTalk Directory

Location.

A prompt to login will open

Note: In order to Specify the FactoryTalk Directory Location you must have administrator rights.

During the install of the FactoryTalk Services Platform the “Windows Administrator” and “Administrator” groups are automatically added to the Network FactoryTalk Directory. Hence, you can login with any user belonging to either of these groups.

2. The Specify FactoryTalk Directory Server Location Utility will open. In this lab we will set the FactoryTalk Directory Location to the local computer (localhost). In a FactoryTalk View SE Network application, the FactoryTalk Directory can be located on any computer on the network that has the FactoryTalk Services Platform installed. Use this utility to modify the location of your FactoryTalk Directory. Follow steps a to b to specify the FactoryTalk Directry Location.

Login.

Username: Administrator. Password: rockwell

b. Click OK to close.

(24)

Create a new FactoryTalk View SE (Network) application

1. Run FactoryTalk View Studio. Select the Start > All Programs > Rockwell Software > FactoryTalk View > FactoryTalk View Studio menu item.

2. Create a Network application called InstantFizz by following steps a to f. You will be prompted with the following dialog:

Select FactoryTalk View Studio

(25)

Wait for several seconds to allow FactoryTalk View Studio to create the application.

Add an Area to the application

1. Follow steps a to c to add an Area called Area1. a. Select Site Edition (Network) b. Select Continue c. Select New tab d. Type ‘InstantFizz’ f. Select Create e. Ensure English language is selected.

(26)

Note: the first line in the Explorer Window: Network (LOCALHOST) indicates that we are creating a Network (Distributed) application and the FactoryTalk Directory is located on the local computer (LOCALHOST).

Add an HMI Server to the application

1. Follow steps a to g to add an HMI Server to the application.

a. Right-click on

InstantFizz and

select “New Area”.

b. Type area name: Area1.

c. Press OK to

(27)

b.Right-click on Area1, go to “Add New Server” then

select “HMI Server”. a. Expand “InstantFizz” to

see the Area1 icon.

c. Select “Create a

new HMI Server”.

d. Select Next.

e.Type the HMI Server name:

InstantFizz_HMIServer.

g. Click Finish to complete.

f. Choose which computer will host the HMI Server. It can be any computer on your network. For this lab, leave this as the local

(28)

Add Process Faceplates into the HMI Server

When you add an HMI server to a network application, or when you create a new local application, you have the option to add the process faceplate displays that are installed with FactoryTalk View SE. The Add Process Faceplates Dialog box will open, if it’s set to display when you create a new HMI server.

1. Select the Clear All button.

2. Check the boxes for this display types: • Discrete 2-State Device – D2SD • Help – Help Browser

Your dialog window should look like this:

3. Click the OK button.

4. Observe that a network application, InstantFizz has been created. The HMI Server called InstantFizz_HMIServer has been created under the area Area1.

5. Maximize or resize your FactoryTalk View Studio window to the desired size for working with your application.

(29)

Add Process Faceplates Dialog

When you add an HMI server to a network application, or when you create a new local application, you

have the option to add the process faceplate displays that are installed with FactoryTalk View SE. The

Add Process Faceplates Dialog box will open, if it’s set to display when you create a new HMI server. If

you don’t want to add faceplates, click Cancel to close the dialog box, without affecting HMI server

creation. If you don’t want to be prompted every time you create an HMI Server, uncheck the option to

“Display this dialog when creating a new application”.

After you create the application or HMI server you can still add process faceplates by right-clicking on

the HMI server and then selecting the Add Process Faceplates menu item. If you added a display

previously, you can either replace the existing display or remove it from the list of displays.

Note: Adding faceplate displays to an application affects the license count. Each added faceplate

display (.gfx file) counts as one display for activation purposes.

New Faceplates

The Alarm Analog – ALMA and Alarm Digital – ALMD faceplates are preconfigured to work with the

new RSLogix 5000 instructions that are available in V 16 or later. These faceplates along with the

existing ones can be used as is or changed to suit your needs.

Add a data server

To allow our application to monitor and control the values within the SoftLogix Controller that is running the control program for this lab you need to add a data server. You will be adding a Rockwell Automation Device Servers (RSLinx Enterprise). It provides the best performance when communicating with Logix5000 controllers.

To monitor alarms in a Logix5000 controller, a Rockwell Automation Device Server (RSLinx Enterprise) needs to be added to a FactoryTalk application.

1. Right-click on the area Area1, select the Add New Server > Rockwell Automation Device Server (RSLinx Enterprise)… context menu item.

(30)

Note: For this lab we are adding the RSlinx Enterprise data server to the area Area1. Read the Area Best Practices paragraph in the Overview section for other alternatives in a distributed application.

2. The RSLinx Enterprise Server Properties will appear. Leave the defaults on the General tab.

Note: The RSLinx Enterprise Server Properties window is also used to configure Data Server redundancy

and FactoryTalk Alarms and Events.

a. Identify the computer that will host the RSLinx Enterprise data server. For this lab, RSLinx Enterprise will be hosted on the local computer (default setting).

(31)

3. Enable Alarms and Events by following steps a-c. The FactoryTalk Alarms and Events will be discussed in more detail during the Alarming section.

.

b. Check the Enable alarm and

event support option

c. Un-Check the Enable history button

a. Select the Alarms and Events tab

(32)

4. Verify that the RSLinx Enterprise device server has been successfully added into your application.

Configure Communications

We are going to now configure a device shortcut.

Device Shortcuts: A Device Shortcut allows you to create a ‘pointer’ to a device that you can refer to

throughout the application while developing displays. This enables the user to change the location of a

processor or other such device in one place, which then propagates throughout the rest of the project,

without having to change all tag references to that processor. A device shortcut is similar to a Windows

shortcut on your computer’s desktop that provides easy access to an application.

Communications Setup Editor Improvements

Offline tag browsing no longer requires you to associate the device shortcut with a controller. In

previous releases, you were required to associate a shortcut with both a controller and an offline tag file

to be able to browse the tags in the offline tag file. You can now create a shortcut that is associated

only with the offline tag file if all you want to do is browse tags in that file.

The Communication Setup editor has been enhanced to prevent the creation of shortcuts that point to

devices that do not provide data (such as communication modules and backplanes).

The Communication Setup editor now provides status messages about shortcuts as you create them as

well as a summary of all messages via a shortcut verification report.

The Communication Setup editor has a new option for enabling alarm and event support at the device

level.

Warnings have been added to FactoryTalk to tell users if making an edit in the development

environment will adversely affect the run-time system. If the change is made through a dialog box, this

warning icon

appears next to the component where the edit can be made.

1. Open the Communication Setup. Expand the RSLinx Enterprise device server. Double-click on

(33)

The Communication Setup dialog will appear to the right of the Explorer tree.

2. Add a Device Shortcut by following steps a-b.

3. Browse to the controller. Right-click on the 1789-A17, Backplane, Select Start Browsing

a. Click the Add button

b. Type the shortcut name “Shortcut”.

(34)

Note: 2 is the slot number of the SoftLogix module that is in the chassis. This is where the control

program for this lab is running.

5. Add an Offline Tag File. Click the Browse… button next to the Offline Tag File entry field. Browse to C:\InstantFizz-Lab Files\RSLogix 5000\ folder. Select the InstantFizz_Controller.ACD file. Click the Open button.

Offline Tag Browsing

The offline tag file will enable you to browse a ControlLogix controller's tags when that controller is not

online. The file must be located on the local PC, not on a networked location.

Offline Tag Browsing Improvement

Offline tag browsing no longer requires you to associate the device shortcut with a controller. In

previous releases, you were required to associate a shortcut with both a controller and an offline tag file

Browse to C:\InstantFizz-Lab

Files\RSLogix 5000\ folder and

select InstantFizz_Controller.ACD file.

(35)

to be able to browse the tags in the offline tag file. You can now create a shortcut that is associated

only with the offline tag file if all you want to do is browse tags in that file.

Because it’s possible to have many application shortcuts configured to different controllers, you must also enable Alarm and Events on your application shortcut to enable which controller you would like to receive alarming information from.

6. Enable Alarm and Events by selecting Yes from the pull-down menu.

7. Apply the settings to the device shortcut “Shortcut” by following steps a-c,

a. Ensure Shortcut

is highlighted.

b. Ensure 2, 1789-L60/A,

SoftLogix5800

Controller is selected.

c. Click the Apply button to apply the shortcut settings. Set Enable Alarms & Events to Yes.

(36)

8. The following RSLinx Enterprise prompt will appear. The prompt lists all the changes made to the

shortcut. Make sure your shortcut is set to Shortcut as we will be using pre-configured displays

referencing that shortcut name.Compare your prompt to the one below. If it matches select Yes to apply the changes.

9. To Verify communications at any time, select the Verify button at the bottom of the Communications

Setup window.

The Verify dialog will appear. Review your changes. Click the Close button.

10. Click OK on the Communications Setup dialog to close.

Your device shortcut has been created.

Select Yes to complete.

(37)

Create a display and add a numeric display object

Let’s take a minute to verify that communications is setup correctly. Verify that you are communicating by adding a Numeric Display Object to a display and then test that display in FactoryTalk View Studio. Verify that you can access controller tags from the online SoftLogix Controller and the offline tags file by performing tag browses. In the Explorer, right-click on the Display folder, select the New context menu item

An untitled display will be opened.

1. Single-click to select the Numeric Input object from Objects > Numeric and String > Numeric Input from the menu.

2. On the empty display, Single-click and hold down the mouse button, drag the cursor to draw the numeric input and release the mouse button. As you are dragging the mouse you will see a rectangle to show the size of the object that will be created.

(38)

Numeric Input Enhancement

Numeric input object allows for user-assigned minimum and maximum values that are validated prior to

download.

4. Click on the Connections tab.

5. Click on the Tags… button next to the Value field.

6. The Tag Browser will open. If you don’t see a folder for Shortcut, right-click on InstantFizz, select the Refresh All Folders context menu item.

7. Expand the Shortcut folder then notice two sub-folders Online and Offline. The Online folder references the tags of the online controller that the shortcut is pointing to (such as our SoftLogix controller). Offline

(39)

folder references the tags in the ControlLogix controller file (.ACD). Use the Offline tag browsing and Offline Tag File in the RSLinx Enterprise Communications Setup when the online controller is not available, and you only have access to the controller file (.ACD). Follow steps a to b to select the

MixSteps tag.

11. The tag will appear in the Tag/Expression field next to the Value. Your selected tag should look like this:

a. Select the

“Online” folder. _{b. Select the}

MixSteps tag

(40)

11. Click the OK button on the Numeric Input Properties dialog.

12. After adding an object to our display, we can verify the communications to our controller and Test the

display.

13. A value (ex. 7) should appear on the display. This actually verifies that you got the tag from the online tag file and you are online with the controller. If you were not online with the controller, it would appear as what is called a wireframe, because the data is not available at this time. It would look something like this instead.

14. Click the Edit Display button to get back to edit mode.

15. Close the display and when prompted to save your changes select No.

Section 1 is complete. You have created a simple network application. You have the building blocks in place and are ready to start creating your graphic displays.

Section 2: Importing Application Components

About This Section

Import pre-configured application components Single-click on the Test Display button from the tool menu.

(41)

FactoryTalk View SE allows you to import and export individual or all HMI Server components, including Displays, Alarms, Local Messages, Images, Parameter Files, Data Logs etc.

The graphic displays are stored in gfx files. GFX files can only be modified (in this format) when imported in FactoryTalk View Studio. You can import a display from one application to another by adding the .gfx files.

This is the Application Explorer window that is used throughout this entire hands-on lab. The Explorer allows you to select different objects, displays, and other components of the FactoryTalk View SE application.

Adding preconfigured HMI components:

There are preconfigured HMI components (i.e., Displays and macros) that will be used in this lab. Do the following Network Directory Application HMI Server Displays Global Objects Area within the

Application.

RSLinx Enterprise Data Server Commands

(42)

1. Right-click on Displays and select “Add Component Into Application…”

2. Browse to C:\InstantFizz – Lab Files\Graphic Displays and add the displays by following steps a-b.

You have now added the preconfigured graphical displays. Some of the displays reference external images (JPG, bmp etc). The next few steps will show you how to import these images into your application.

3. Right-click on Images and select “Add Component Into Application…”

a. Select all the GFX files in this folder, then click Open.

b. The graphic displays will be migrated. This may take a few seconds.

(43)

4. Browse to C:\InstantFizz – Lab Files\Images to add the images

You have added the preconfigured graphical displays and the corresponding images. The next two steps will show you how to add the pre-configured startup macro into your application. You can learn more about macros in Section 4.

5. Right-click on Macro and select “Add Component Into Application…”

6. Browse to C:\InstantFizz – Lab Files\ and select startup.mcr to add the pre-configured macro 5. Select all the .bmp

files in this folder, then click Open.

(44)

Section 3: Tags

About This Section

Learn the difference between HMI tags and direct reference tags Create an HMI tag

Import and Export tags

Add an object and reference an HMI tag Learn about Tag Labels

Read about HMI Tags and Direct Reference Tags

A tag is a logical name that represents a variable in a network device or in local memory. FactoryTalk View SE has two types of tags:

- Data server tags (also called direct reference tags) provide direct access to the controller tags, through data servers you add to an application.

- HMI tags provide additional properties for run-time security and data manipulation. HMI tags are created in the Tags editor and stored in an HMI server’s tag database.

(45)

For some uses in an application, using direct references tags offers advantages over using HMI tags, and visa versa. The following table contains a list of advantages for HMI tags and direct reference tags. Depending on the application you can choose one over the other or use a combination of the two.

HMI Tags

Direct Reference Tags

Using the extended capabilities of HMI tags

To take advantage of extended capabilities, such as run-time security, scaling or

offsetting of tag values, or more flexible

addressing, create HMI tags in FactoryTalk View Studio, in the Tags editor.

Using direct referencing to eliminate duplication

Using a direct reference minimizes errors, by having to create the tag database only once (in the controller) and not having to duplicate it again in the HMI. This applies to all objects including device-based FactoryTalk Alarms and Events. Moreover, while developing the HMI there is no need to create a tag database which saves time. Also, use the 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.

Organizing tags in folders

The tags can be organized in logical folders and subfolders. For example, create a folder for the CIP process of a soda plant. In a large application, you can easily find tags by organizing them in folders.

Providing access to complex data types

Some devices (Logix5000 controllers, for example) support data types such as arrays and structures, which can contain hundreds of member elements. Use data server tags to reference the tag values directly, and eliminate the need to create an HMI tag for each member element. You can maximize optimization by placing data in arrays and structures.

(46)

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. - maintain information about the

system’s current state, for example, which graphic display was last displayed.

Reusing Displays and other components between applications

For example, export displays from one application onto another application which uses the same controller tags. There is no need to move the HMI tag database. All the direct tag references are transferred with the display.

Reusing HMI tag names

HMI tags do not require hard-coded physical addresses or device-specific variable names. This means you can reuse an application with other devices, by changing the physical addresses that the HMI tag names are mapped to.

Speed

Direct references are a direct link to the data server and controller which helps to speed up an application update rate.

Importing Exporting HMI tags

- Use the Tag Export/Import Wizard to import/export tags in the .CSV format (can be opened in Excel). - The exported tag database can be

used in other FactoryTalk View projects.

- You can modify and create all the tags in Excel and save engineering time.

- You can Import RSLogix Address files into the FactoryTalk View tag database

Descriptive names

Some controllers and OPC servers do not allow descriptive tag names, for example SLC. Creating an HMI tag will allow you to provide meaningful names to tags instead of memory locations such as N7:0.

Creating an HMI tag

Lets create a tag in the tag database.

1. Open the Tag database from the HMI Server, InstantFizz_HMIServer. Follow steps a-i to add an HMI tag in a folder.

(47)

While the tag database is open, select the Edit menu item to create a new folder.

Note: This menu item can be used to Add, Delete, Duplicate and Rename Tag Database folders. Another

major use is the Other Databases menu item, which allows you to import tags from other databases such as the RSLogix 5/500 controller files (.rss, .rsp).

a. Double-click on Tags

from the HMI Tags folder to open the tag database.

b. Click on the Edit menu

item then select New

Folder.

c. Type the new folder

name “CIP” then click OK.

(48)

Setup the new tag properties as shown below :

10. Click Accept to complete.

11. The tag database also allows you to search for tags. Follow steps a-b to search for a tag.

d. Ensure the CIP folder is selected. We want to create a tag in this folder.

e. Type the new tag

name WaterAmount.

f. Choose the tag Type

as Analog. HMI tags can be Analog, Digital or String Type.

g. Type the tag

description.

h. Choose the Min, Max, Scale, Offset and Units as shown.

i. Click on the ellipses button to

open the tag browser. Then browse to the following tag

(49)

Import/Export Tags Wizard

Let us import tags that were pre-created using the Tag Import/Export Wizard. Use the Tag Import and Export Wizard to convert databases to and from a CSV (Comma Separated Variable) format compatible with Excel. You can also merge one FactoryTalk View tag database with another tag database and import an A.I. Series or Logic 5 text database.

To successfully import tags, the application you are importing tags into must be open in FactoryTalk View Studio.

Import & Export Choices:

There are several Import / Export options as shown in the Tag Import/Export Wizard.

b. Click Close to exit the tag database.

a. You can search for any tag in the tag database using the Search For field.

Highlight the root folder then Type

the word System\Second to search

for a predefined memory tag then press Enter.

(50)

- Export a FactoryTalk View tag database to CSV files Exports a FactoryTalk View tag database to CSV files. - Import FactoryTalk View tag CSV files

Imports tag information from CSV files into a FactoryTalk View database. You can create your tags in Excel then import them into the project using this setting in the Tag Import/Export Wizard - Merge FactoryTalk View tag database

Merges tag information from one FactoryTalk View project with another FactoryTalk View database.

- Import A.I. Series or Logic 5 database files

Imports symbols from the Rockwell Software A.I. Series or Logic 5 CSV format into a FactoryTalk View database.

- Import RSLogix5/500 Address & Symbol ASCII files

Imports symbols from the ASCII export file of RSLogix5 or RSLogix 500 into a FactoryTalk View database.

(51)

2. Close Excel without saving.

3. Return to FactoryTalk View Studio and open the Tag Import/Export Wizard from the Tools menu.

Open the created CSV file with pre-created HMI tags. Go to C:\InstantFizz – Lab Files\ and double-click on

Additional_Tags.csv. Review the file and

note the Excel column/row format used. You can add and modify tags and folders in Excel then import them into your application.

(52)

4. Select the “Import FactoryTalk View tag CSV files” option from the drop-down and then click Next.

5. Select Site Edition

as Project Type.

6. Browse to our HMI project under C: Documents and Settings\All Users\Shared Documents\RSView Enterprise\SE\HMI

Projects\InstantFizz_HMIServer\. Select the file InstantFizz_HMIServer.sed.

7. Select Next to continue.

8. Make sure Tags is checked. Select the pre-created CSV file to import from

C:\InstantFizz – Lab

Files\Additional_Tags.CSV

9. Select Next to

(53)

10. You can skip existing tags or update existing tags. Leave the

default for our lab.

11. Select Next to

continue.

12. Select Finish to complete.

(54)

We have now imported the pre-created tags into our application.

14. Open the tag database editor by double-clicking on Tags to view our imported tags. 13. View the results of the

Database Import, then click X to close.

(55)

16. Close the Tag database.

Add Object referencing an HMI tag

1. Open a new display

An untitled display will be opened.

2. Single-click to select the Numeric Display object from Objects > Numeric and String > Numeric

Display from the menu.

15. Note the new folders and tags added to our tag database via the Tag Import/Export Wizard.

(56)

3. On the empty display, Single-click and hold down the mouse button, drag the cursor to draw the numeric display and release the mouse button. As you are dragging the mouse you will see a rectangle to show the size of the object that will be created.

4. The Numeric Display Properties window will open

4. Select Tags to open the Tag Browser and find a tag to reference.

(57)

5. The same Tag Browser window is used to browse for HMI Tags, Direct Reference Tags associated with an online and offline controller, Diagnostic Items and pre-defined System tags.

Let us review the Tag Browser.

Structured Tag Support in FactoryTalk Tag Browser

The tag browser has been enhanced to let you select a structure tag in the left-hand pane of the object

browser and return a partial tag identifier to the editor that launched the browser. This structure tag can

be assigned to a faceplate object to supply values to multiple objects.

8. Browse to the HMI tag RapidMix\WaterAmount

5. CIP and RapidMix are folders created in the HMI Tag Database.

6. “Shortcut” is the device shortcut associated with the SoftLogix controller. It contains all the direct reference tags to the controller.

- Diagnostic Items: Pre-defined diagnostics tags to Logix controllers, such as @Mode, which indicates the current mode of the controller (Run, Program, Remote)

- Offline: Direct reference tags to the

Offline Tag File that was associated with the “Shortcut”

- Online: Direct reference tags to the

controller. 7. System contains the

pre-defined memory tags and are stored in the HMI Server. For example,

(58)

10. Add a Tag Label object on the same display to the right of the Numeric Display object.

8. Expand the RapidMix

folder, then select

WaterAmount and click OK.

9. The tag has been added to the object. Click Apply then OK to exit.

(59)

Use label objects to display information about a tag's properties at run time. You can display the value of one property per tag label. The properties include: Low EU (tags Minimum Value), High EU (tag

Maximum Value), Contact Value (tag Status), Engineering Units (EU) (tag Units), Tag Name, Tag Description, Contact Open Label (tag Off Label), Contact Close Label (tag On Label).

11. The Tag Label Properties window will open. Set up the properties as shown below. Browse to the same RapidMix\WaterAmount tag and set the Property to Engineering Units (EU).

(60)

12. Click OK to close.

13. Test the display

14. Review the display.

Note: The Tag Label object only works with HMI Tags, because we defined the properties (such as Units) of

this tag in the HMI Tag Database. It does not work with direct references. To display the engineering units of a direct reference you can add a Text Object and type the applicable units.

13. Single-click on the Test Display button from the tool menu.

14. The Numeric Display object will display the

current value of the RapidMix\WaterAmount

HMI Tag and the Tag Label will display the defined

Engineering Units of the

(61)

15. Click the Edit Display button to get back to edit mode.

16. Close the display without saving.

Section 4: Graphic Displays, Objects and Animations

About This Section

In this section of the lab you will: Read about Graphic Displays Use XML file to edit displays Use Faceplates

Configure and use Tooltips

Configure and use Local Messages Configure and use Docked displays Using the Object Explorer

Configure and use Animations and Expressions

Using Commands

To help with the navigation within FactoryTalk View Studio for the components used in this section, you can again refer to the Application Explorer image from Section 2.

Read about Graphic Displays

Types of Graphic Displays

Standard

Displays - stored in the Displays folder. These are the displays that the operator sees at run

time. They present views of automated plant activity or processes. They can show system or process

data and provide operators with a way to write values to a real-time database or network devices such

(62)

Library displays - stored in the Libraries folder. A library display contains ready-made graphic objects

that you can use in other displays.

A graphic display represents the operator’s view of plant activity. The display can show system or process data, and provide operators with a way to write values to external devices such as programmable controllers. The elements that make up a graphic display are called graphic objects. The Objects menu in the Graphic Displays editor (Figure 1) provides simple drawing elements such as line, rectangle and ellipse, as well as ready-made objects such as push buttons, input and display fields, and alarm summaries. Use these elements to create visual representations of processes and activities then animate the display by linking objects to tags so that the

appearance of the objects will change as the values of the tags change.

The graphics editor allows you to easily duplicate objects, reshape or resize objects, and arrange them in a variety of ways like stacking them, aligning them with each other, spacing them horizontally or vertically, flipping them horizontally or vertically, rotating them, and grouping them so they behave as a single object. Graphic objects can be

Created using the Graphic Display editor. Copied and pasted from the Graphics Libraries.

Copied to the clipboard from another Windows application and then pasted into the graphics display. Created by another Windows application and inserted into the graphic display using object linking and

embedding.

Dragged and dropped from another graphic display or library, or another Windows application.

Figure 1: Objects Menu

Libraries

The Graphics Library comes with a number of ready-made graphic displays containing objects that you can use in other displays

Factory Talk View SE

IA-09-L16 – FactoryTalk View SE Lab Manual

Presenter: <<Your name>>

<<Your business group>>

IA-09-L16 — Configuring a FactoryTalk View SE

Application

Contents

Before you begin

Before you begin

Before you begin

Before you begin

1. If

Log On To Windows dialog is active type ‘administrator’ for Username and type ‘rockwell’ for

password.

2. Use the same Login information if prompted to Log On to the FactoryTalk Directory or when

creating a FactoryTalk Alarms and Events History Database.

About this lab

RSView name (CPR 7

and earlier)

FactoryTalk View

name (CPR 9 and

later)

RSView name (CPR 7

and earlier)

name (CPR 9 and

FactoryTalk View

later)

What You Will Accomplish In This Lab

Who Should Complete This Lab

Tools & prerequisites

Hardware

Software

FactoryTalk Services Platform v2.10.00.0117

FactoryTalk View SE v5.00.00.55

RSLinx Enterprise v5.00.00.99

FactoryTalk Alarms and Events v2.10.00.0117 (included with FactoryTalk View Site Edition and

RSLinx Enterprise)

RSLinx Classic (used for Logix programming) v2.52.00.17

RSLogix5000 v16.03.00

SoftLogix 16.03.00 (Bld 42)

Microsoft SQL Server 2005 Express

Microsoft SQL Server Management Studio Express

Microsoft SQL Server 2005 Express Edition is a free, redistributable version of Microsoft SQL Server.

FactoryTalk Alarms and Events uses Microsoft SQL Server as the database engine for logging alarm

and event information. You can connect to an existing SQL Server database, or you can install

Microsoft SQL Server 2005 Express, Service Pack 2, which is included in the Redist folder on the

FactoryTalk View SE and RSLinx Enterprise CDs.

Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical

management tool for managing SQL Server 2005 Express. It is included in the Redist folder on the

FactoryTalk View SE and RSLinx Enterprise CDs.

Lab Files

Language Switching – contains 3 files that will be used in the language switching section of the lab

InstantFizz_Translated.xls

– Translated file for FactoryTalk View SE

InstantFizz_Controller-Tags_translated.TXT

- Translated file for FactoryTalk Alarms and Events device-based alarm messages in RSLogix

5000

InstantFizz_FTAETagServer_Alarm Export_translated.xls

- Translated file for FactoryTalk Alarms and Events tag-based alarm messages in the

FactoryTalk Tag Alarm and Event Server

RSLogix 5000 – contains 1 file that can be used with RSLogix 5000.

InstantFizz_Controller.ACD – control program to be used in this lab

Graphics displays – contains 19 files that have been pre-configured

cip - process steps.gfx

CIP - Sensor Trend.gfx

CIP - Valves.gfx

CIP Overview.gfx

filling.gfx

labeling.gfx

Languages.gfx

Navigation.gfx

packaging.gfx

Plant Overview.gfx

Rapid Mix - Overview.gfx

Rapid Mix - Process Steps.gfx

Security.gfx

Images – contains 56 pre-configured images

Client – contains a preconfigured FactoryTalk View SE Client file

ClientFile_DockedDisplays.cli

Client Keys - ClientKeys.key