Integrating FactoryTalk View SE

into Your Architecture

PLEASE LEAVE THIS WORKBOOK IN THE ROOM!

Integrating FactoryTalk View
SE Into Your Architecture -
Hands-On Lab:

T
Trraaiin
niin
nggL
Laab
bMMaan
nuuaall
INTEGRATING FACTORYTALK VIEW SE INTO YOUR ARCHITECTURE ________________7

ABOUT THIS HANDS-ON LAB __________________________________________7

LAB MATERIALS ___________________________________________________7

DOCUMENT CONVENTIONS ____________________________________________8

BEFORE YOU BEGIN ________________________________________________8

LAB 1: INTRODUCTION TO DISTRIBUTED VIEW SE______________________________9

SECTION 1: INTRODUCING THE LAB LAYOUT AND THE DISTRIBUTED FACTORYTALK

SE SYSTEM. _____________________________________________________10

ABOUT THIS LAB __________________________________________________10

CHECKING/CHANGING THE FACTORYTALK DIRECTORY SERVER TO USE, AND

INTRODUCTION TO THE APPLICATION. __________________________________11

LAB 2: INTRODUCTION TO SOME NEW FEATURES AND ONLINE EDITING IN FACTORYTALK

VIEW SE 11

SECTION 1: USING GLOBAL OBJECTS IN RSVIEW SE _______________________11

ONLINE EDITING WITH FACTORYTALK VIEW SE ___________________________11

REUSING OPERATOR PANEL GRAPHICS IN A FACTORYTALK VIEW SE PROJECT. _____11

ABOUT THIS LAB __________________________________________________11

MAKING OPERATOR TERMINAL (FACTORYTALK VIEW ME) PROJECTS AVAILABLE IN

FACTORYTALK VIEW SE. ____________________________________________11

CENTRALISING AUTOMATION SECURITY. ___________________________________11

ABOUT THIS LAB __________________________________________________11

WORKING WITH CENTRALISED SECURITY ________________________________11

WORKING WITH ELECTRONIC SIGNATURES. ______________________________11

ABOUT THIS LAB: _________________________________________________11

IMPLEMENTING E-SIGNATURE (ELECTRONIC SIGNATURE) CONTROL.____________11

FEATURES THAT ENHANCE AND SPEED VISUALISATION PROJECT DEVELOPMENT. _11

ABOUT THIS LAB: _________________________________________________11

DOCKED DISPLAYS. ________________________________________________11

RUN-TIME LANGUAGE SWITCHING. _____________________________________11

STANDARD FACEPLATES AND CONTROLLER CODE TO SPEED DEVELOPMENT. ____11

Integrating FactoryTalk View SE Into Your
Architecture
About This Hands-On Lab
This series of labs will introduce FactoryTalk View SE (Site Edition) used in a
distributed environment.

What You Will Accomplish In This Lab

This course is a skill-building opportunity for students who want to develop a
fundamental knowledge of FactoryTalk View SE (Site Edition) systems. Students will
be introduced to FactoryTalk View SE software components, functionality and
terminology. They will gain experience configuring FactoryTalk View SE and related
software.

Who Should Complete This Lab

This hands-on lab is intended for individuals who are interested in learning about
features of FactoryTalk View SE (Site Edition) systems and how they can help in
your Automation needs.

Lab Materials

For this Hands-On lab, we have provided you with the following materials that will
allow you to complete the labs in this workbook.
Hardware
This hands-on lab uses the following hardware on the on tour station:
ƒ PC running: Domain Controller, DNS Server
ƒ PC running: FactoryTalk View SE servers, Data Servers, Soft Controllers.
ƒ PC running: FactoryTalk Studio and Client.

Software
This hands-on lab uses the following software:
ƒ RSLogix 5000 v16
ƒ RSLinx 2.50 or higher
ƒ FactoryTalk View SE (Site Edition) Server, Client, Studio and utilities.

Lab Files
This hands-on lab uses the following files:
Document Conventions

Throughout this workbook, we have used the following conventions to help guide you
through the lab materials.
This style or symbol: Indicates:
Words shown in bold italics Any item or button that you must click on, or a menu name
(e.g., RSLogix 5000 or OK) from which you must choose an option or command. This will
be an actual name of an item that you see on your screen or
in an example.
Words shown in bold italics, An item that you must type in the specified field. This is
enclosed in single quotes information that you must supply based on your application
(e.g., 'Controller1') (e.g., a variable).
Note: When you type the text in the field, remember that you
do not need to type the quotes; simply type the words that
are contained within them (e.g., Controller1).
The text that appears inside of this grey box is supplemental
information regarding the lab materials, but not information
that is required reading in order for you to complete the lab
exercises. The text that follows this symbol may provide you
with helpful hints that can make it easier for you to use this
product. Most often, authors use this “Tip Text” style for
important information they want their students to see.

Note: If the mouse button is not specified in the text, you should click on the left
mouse button.

Before You Begin

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

1. Ensure all servers are up and running

2. Close all open applications on the client PCs

Lab 1: Introduction to Distributed View SE

FYI

What is FactoryTalk View SE?

Before we discuss FactoryTalk View SE, let’s just cover other visualisation
products offered by Rockwell Automation:

RSView32:

Is an integrated, component-based HMI software package for monitoring and

controlling automation machines and processes. It is a single server and single
client software package running on one PC, with the possibility of expanding with
remote clients (max 20). RSView32 has been available for over 10 years and has
a large install base around the world.

FactoryTalk View ME:

(Machine Edition) Is a machine level HMI product for developing and supporting
PC-based and embedded operator interface solutions. It is designed as a
monitoring and control system for individual machines and small processes. For
more information and experience with FactoryTalk View ME please see the IA-
OnTour FactoryTalk View ME lab sessions.

FactoryTalk View SE:

The SE in FactoryTalk SE can refer to the two versions that are available of
FactoryTalk View SE. These are Station Edition and Site Edition.

The Station Edition is a standalone HMI system for monitoring and control of
individual processes or lines. All components run on a single PC and are not
distributed between PCs.

The Site Edition is a distributed version where HMI servers, Data Servers,
Clients, Studio Editors can be distributed on to separate PCs. FactoryTalk
technology enables the distributed software to operate as a single seamless
application, so the programmers and operators of the system do not need to be
concerned with the physical distribution of the system.

This lab will concentrate on the Site Edition so that the distribution of SE can be
shown and the customer benefits of using FactoryTalk can be demonstrated.
Section 1: Introducing The Lab Layout And The Distributed
FactoryTalk SE System.

About This Lab

In this lab the layout and distribution of the various FactoryTalk components will be
presented and explained.

Here is the lab layout for The FactoryTalk View SE hands-on session. It may look
complicated but in fact it is not. As you go through the lab you will be working in pairs
on a single server at the front of the room. The table below shows the PCs you will
be working with.

So here is an example: Client PC number 06, looking at the table below, will be
working with client 05, on FactoryTalk Server W, using HMI Server E and Data
Server 2, Controller 1.
PC Client Using Using HMI Using Data
Number FactoryTalk Server Server/Controller
Directory
Server

01 A 1, Controller 1

02 B 1, Controller 2

03 V C 1, Controller 3

04 D 1, Controller 4

05 E 2, Controller 1

06 F 2, Controller 2

07 W G 2, Controller 3

08 H 2, Controller 4

09 I 3, Controller 1

10 J 3, Controller 2
X
11 K 3, Controller 3

12 L 3, Controller 4

13 M 4, Controller 1

14 N 4, Controller 2
Y
15 O 4, Controller 3

16 P 4, Controller 4

17 Q 5, Controller 1

18 R 5, Controller 2
Z
19 S 5, Controller 3

20 T 5, Controller 4
Description Of What Each PC is doing in the lab.

• One Off - Domain Controller: This is a Windows Domain Controller providing

centralised windows and FactoryTalk Security. Also running a DNS server.

• Five Off- FactoryTalk and HMI Server PCs: As described above FactoryTalk
SE can be a distributed system, where data servers, HMI servers, clients and
studio can operate as a single application even through components are
distributed across many PCs. For the lab there is a limit to how many PCs are
available, so for the Lab: FactoryTalk Directory, four HMI servers and one
Data Server are installed on each server PC. However please note each of
these SE components could equally well be installed on separate servers.

• Twenty Off – Client PCs: Each of these PC’s will have FactoryTalk View
Client (view runtime) and FactoryTalk Studio (view editor) installed. The
clients will connect (four per server) to a server PC at the front of the room
(according to the table above). Two client PCs will be used to edit each HMI
server, again according to the table above.

Checking/Changing The FactoryTalk Directory Server To Use,

And Introduction To The Application.

FactoryTalk has been installed on every PC in the room, except for the Domain
Controller. This is the recommendation for all PC’s that have FactoryTalk enabled
software installed and any third party software (for example OPC servers).

In fact all PC’s in the room could be configured to share one FactoryTalk directory,
and then all software would become part of a single seamless application space. But
for our lab we are going to separate the FactoryTalk servers. FactoryTalk is very
versatile when it comes to separating applications; we can have one FactoryTalk with
one application, One FactoryTalk with multiple applications, multiple FactoryTalk
Directory Servers with single or multiple applications. This FactoryTalk feature of
making distributed PCs running applications all appear as though in one application
is called FactoryTalk Directory Services.

From the table above it can be seen how we intend the distribution of FactoryTalk
directory servers to be assigned, but how do we change this or check this?

1. There is a utility installed along with FactoryTalk what lets you check/specify
which FactoryTalk Directory Services the FactoryTalk enabled software
should use.
Run the utility from here:
2. The utility will then ask you to log-in. Why? It is because you have to have
user rights to modify a FactoryTalk setting. When the software was installed,
it was configured to use an Administrator user name and password (just as
MS Windows XP does when it is installed). The user name for FactoryTalk is
‘ftadmin’ and the password is ‘ftadmin’.

Note this is a low level security password and in

reality it is advisable to use a stronger password,
but for this lab it will suffice.

So log in now with these credentials, then click OK.

3. The FactoryTalk location tool will now be displayed as below

The server name that the PC is connected to will appear in the ‘Computer
hosting directory server’ box. In the example it is Server-V. Check that the
PC is connected to the correct server, as indicated in the table above.
Example Client PC 08 should be connected to Server-W. Also notice that the
word (connected) is displayed, this is indicating that the connection to the
FactoryTalk Server is working correctly.
 Click Cancel if the correct server name and ‘connected’ is displayed. If it is
not, let an instructor know. These setting should be correct as this was set up
prior to the lab starting by the instructors. This is also the place where by
clicking the ‘…’ button it is possible to select another FactoryTalk server, but
don’t change this now.

4. So now that the system has been configured and checked, it is time to launch
the editor for all the FactoryTalk visualisation products - FactoryTalk Studio.

FactoryTalk Studio is used to edit the entire range

of FactoryTalk Visualisation products. I.e. One
software package to edit FactoryTalk View ME (for
operator stations), to single PCs. And all the way to
large FactoryTalk View SE distributed systems. All
with the same package:

FactoryTalk Studio

Click on the following program, or select shortcut from the desktop.

5. Select ‘SE Distributed’ and click Continue.

Did you see? With FactoryTalk Studio it is possible to edit the entire scope of
visualisation projects. From FactoryTalk View ME for operator stations all the way
to large multi-PC distributed systems.
6. You will now see the display below (Don’t worry if you see different projects in
the list).

Where did this list of applications come from? Well remember that the client PC is
part of the FactoryTalk directory located on the server at the front of the room. So
in fact this list of applications is coming from the FactoryTalk server on the PC at
the front of the room.
Select the SE_IA application and select language English (united States), en-
US (if not select already. Then Click Open.

7. What you will see now is FactoryTalk Studio starting to load the application
SE_IA. Where is it loading this application from? It is loading it from the PC
that is allocated in the distributed system to be an SE HMI Server. In this lab
the PC at the front of the room has been allocated this role. Note the HMI
servers do not have to be installed on the same PC as FactoryTalk directory
server, in this lab however it is.
Each SE_IA application has been allocated four HMI servers; these are being
loaded now by FactoryTalk Studio. Again these HMI Servers could be on
different PCs to each other, but because of limited number of PCs available
they are loaded on the same PC at the front of the room.

Note: No files are being copied when the application is being loaded
by FactoryTalk Studio. FT Studio is requesting information about the
application from FT Directory Service (How many and location of HMI
Servers and Data Servers). FT Studio is then going to these
distributed PCs and requesting information from them directly. Still no
copying of files, just information of the ‘structure’ of the project – i.e
name of graphics, tags, etc. This Information is then presented by FT
Studio to the user.

In a runtime environment the maximum number of HMI servers to be

running on one server PC is one (1), or two if no redundancy is being
used. However for development purposes (and labs) it is possible to
run up to five (5) HMI servers on one server PC.
 This is good news as it effectively means that when developing a
FactoryTalk View SE project it is not necessary to purchase all
your PC hardware immediately, only when ready to install on site.

8. When FactoryTalk Studio has finished loading the application you will see
this.

Some things to notice:

• At the top of the application tree the FactoryTalk Directory Server name is
displayed, ie which PC is the client making connection to. Note this will be
the same PC as seen with the FactoryTalk Location Utility (page 15).
• Just below the name of the FactoryTalk Directory Server, the name of the
application is displayed.
• Below the name of the application this symbol appears three times -
This symbol represents an ‘area’. Areas are used to make a logical
separation of FactoryTalk components. So in this application an area has
been used to separate the Data Servers, and each of the two HMI
servers. (As shown in the screen capture above).
 • At the bottom of the tree the application security options and
configurations can be seen and modified, but more about this later.

9. Expand the area “DataServers” area containing the Data Server, by clinking
on the + symbol

Expanded

Here is defined a data server, in this case RSLinx Enterprise, which is the
preferred and most optimised data server for Logix controllers.

10. Double click the ‘Communication Setup’

The communication configuration is shown here.

• In this application there is only one data server configured; however other
data servers can be added, this includes any third party OPC servers.
• Once a data server had been added and configured it is available to all
FactoryTalk components that require a data server. It only has to be
 configured once and is available everywhere with in the application
(including of course other distributed PCs).

Click cancel, as this data server has already been configured

by the instructors prior to the lab starting.

11. The four remaining areas are ‘ProcessArea_A’, ‘ProcessArea_B’,

‘ProcessArea_C’ and ‘ProcessArea_D’. Each of the areas has an HMI server
inserted, each named HMI_X, where X = A to J (see the table above).
So to recap each group of four (4) clients (for example clients 01 – 04) are
connected to one FactoryTalk directory on server ‘V’.
On the same server are located four SE HMI servers. One client will be
editing each HMI server.

Note: FactoryTalk SE supports multiple remote users to edit a single

application simultaneously. The recommendation is five (5), but this is
not a hard coded limit.

12. Now locate in the project tree the HMI area to work in based on the table
above. Example client 10 is going to work with PC ServerX and HMI server J.
Expand the Graphics - ‘Displays’ section in the project tree by single clicking
on the ‘+’ mark for the HMI server allocated to the client.

13. Open each graphic in the application HMI area assigned to the client, by
double clicking each display. Just quickly inspect each graphic then close
again (if prompted to save changes, select NO).
This application is for a process plant, FactoryTalk View SE is ideal for any
visualisation application, including large process plants that require distributed
components to manage the physical size of the plant.
End of lab section 1 (Introducing The Lab Layout And The Distributed
FactoryTalk SE System.)
This lab introduced the set-up of the equipment in the room. Introduced the extremely
distributed nature of FactoryTalk View SE and the concept of a single application
distributed seamlessly across multiple software and hardware components. No
copying of files is required to edit an application just selecting the location of the
FactoryTalk Directory and launching FactoryTalk Studio – Job Done!
Lab 2: Introduction To Some New Features
And Online Editing In FactoryTalk View SE
Beginning with the 4.0 release, RSView ME and SE will support global objects.
Global objects can be thought of as a master or parent object which can be used to
create ‘child’ references. Essentially at this point, any changes to the master/global
object are automatically propagated to its child references.

Section 1: Using Global Objects in RSView SE

To use a global object, we simply create a ‘child’ instance of the object on a new
graphic display. From that point on, RSView maintains a link between the global
(‘parent’) object and any child instances placed on displays throughout the
application.
1. In the Application Explorer, expand the Displays icon and double click on the
“Grist_D2SD_FP” graphic to open it.

2. Next, expand the Global Objects icon and open the “D2SD” discrete 2-state
device global object.
Each global object faceplate has been preconfigured to display information directly
from the structure of RSLogix5000 function block instructions much the same way
that the Logix5000 ActiveX control faceplates do except that these displays are
completely customizable. You do not, however, have to create a new display for
every function block in your program. Global objects are generic in that they must
have parameters passed to them at runtime.
Take a look-
3. Click anywhere on the D2SD global object and from the menu bar, select
EditÆTag Substitution…

Note that ALL of the tag references within the object contain a “#1” placeholder.

The “#1” will be replaced at runtime with any D2SD tag when the graphic is called
up. Alternatively, this tag substitution feature could be used to replace the “#1”
references and tie this object directly to a single D2SD tag.

4. Click .
5. Position the two graphics side by side and drag the components from the global
object onto the D2SD_FP graphic as shown.

6. Close the “D2SD” global object (the one on the right).

7. Save and close the Grist_D2SD_FP graphic.

We now have a child instance of the D2SD global object in the application. Let’s
create a few more. We can do this simply by duplicating the Grist graphic.

8. Right-click on the “Grist_D2SD_FP” graphic in the Application Explorer and

choose Duplicate.

9. Name the new screen “fp_mash” and click OK.

10. Repeat the duplication process to create the screens below.

 “fp_kettle”
“fp_lauter”
“fp_wort”
You should have the following faceplate graphics in the tree.

11. In the Application Explorer, expand the Displays icon and double click on the
“Brewhouse” graphic to open it.

This is the brewhouse overview graphic. It is partially animated, but now add a few
components to complete it.

12. Change the ‘BrewHouse’ general tile to a name of your choice, eg ‘Mr Smith’. To
do this double click the word ‘BrewHouse’ and change the text, click OK.
13. Right-click on the valve (2-state device) below the Malt A tank in the Grist Mill.

14. This area will be used to launch the Grist_D2SD_FP graphic. From the context
menu, select AnimationÆTouch. An action menu appears.

15. Click the button next to the Release action text box.

16. From the list of commands in the Command Wizard, expand the
GraphicsÆGraphic DisplaysÆNavigation folders and select the “Display”
command from the list at the right.

17. Click .

18. Click the ‘area select (…)

19. Select the area for the Client. ProcessArea_A, B, C or D

20. From the drop down list of graphics, select the Grist_D2SD_FP graphic and
enable the /T Parameter tag option as shown.

21. Using the available text box, we’ll need specify which tag in the controller this
graphic is going to display. Click the button next to the Parameter tags text
box.
 Note:

Using the tag browser, it is possible to drill down straight into an online
controller it is not necessary to export/import tags. In this example the
Grist Mill control module is directly accessible to FactoryTalk View
SE. This functionality of making ALL tags in ALL controllers and HMI
servers directly accessible is called - FactoryTalk LiveData.

22. Drill down (in the controller allocated to the client) through the
ControllerXÆOnlineÆProgram: Grist_Mill_001

Expand ‘Online’ and scroll down the tag list.

23. and select the “GM_Ingredient_A_Valve_D2” tag structure as shown. Click OK.

24. FactoryTalk SE allows the selection of individual tags or entire structures of tags.
In this case we are selecting an entire structure GM_Ingredient_A_Value_D2, this
structure contains all the tags in the right-hand pane.

25. Click .

26. Click and to complete the Touch animation.

We now have a mechanism to call up the faceplate associated with the Malt A valve.
27. Use the same steps to add touch animation to the Malt B output valve on the
“Brewhouse” screen so that it calls up the same “Grist_D2SD_FP” graphic and
displays information for “GM_Ingredient_B_Valve_D2”.

28. Close and save the “Brewhouse” overview graphic when finished.

To recap what actions were just taken:

Using a global object called D2SD (two state device) to create four
new displays: fp_mash, fp_kettle, fp_lauter and fp_wort.

Edited the ‘BrewHouse’ graphic to add two new ‘touch’ animations to

the ‘Grist Mill’ values A and B.

The tag names to use when the touch animation opens the displays
were browsed directly online in the controller. It was not necessary to
create tags in the View SE database.

29. To test the modifications there are two ways: One way is to use the ‘Test Display’
button This will allow testing of the currently highlighted screen i.e. Tag Values,
Animation etc. However if the navigation between displays is to be tested, it is
necessary to run the full test client.
30. From the FT FactoryTalk View Studio toolbar, click the Launch SE Client button.

31. Click once again (in the upper right corner) to open the SE Client
configuration wizard.

32. Name the new client configuration file ‘ProcessHMIX’, where X= A, B, C, D, E

etc (the client area).
33. Click the button and select your Desktop as the destination location.

34. Click OK. Click .

35. Select the Network radio button and click .

36. Select enter SE_IA from the drop down list selector AND select the English
Language option as shown below.
37. Click .

38. Select Area and choose your area, i.e. ProcessArea_X. Where X= A, B…… etc

39. Use the drop down list to set the Initial Display to the “OverView” graphic.
40. Click .

41. Disable the Title bar.

42. Click twice and then to launch the SE client.

Keep the ProcessHMI client window open for the duration of the lab.
Online editing with FactoryTalk View SE
43. Click on the image in the middle of the “Overview” graphic running in the SE
Client to open the “Brewhouse” screen.

44. The screen below should now be active and animated.

Let’s take a little tour through the Brewhouse before we start the brew process.

Grist Mill
45. Click on the Malt A valve to launch its D2SD faceplate.

46. Click the button to take manual control of the valve.

47. Click the button to open the valve.

48. Feel free to experiment with the Program and Operator control. When you have
finished, click the “Close” button at the bottom of the faceplate.

Mash Tun

49. Click on the button to open the Mash Tun Heat Control PID loop
faceplate.

50. Click the button and drag the set point pointer up to about 100°.

51. Watch the response (in the trend window at the bottom of the screen) as the
system adjusts to the set point change.
52. Verify that you have set the loop back to Operator Manual control and click the
“Close” button to close the PIDE faceplate when finished.

53. Click the button to open the Autotune faceplate for the same
temperature PID loop in the Mash Tun.

54. This graphic requires 2 parameter tags when invoked. The first tag (#1) is the
PIDE tag itself, and the second (#2) is the autotune tag.

55. Verify that the Autotune tag for the loop has been acquired.

56. Click the button to begin the autotune process. It will take a minute
or two to complete.

57. Upon completion of the tuning, select the Slow gains and click the
button download them to the controller.

58. Click the “Close” button when finished.

59. Click on the Mash Tun tank to display the Mash Tun detail screen.
This screen provides a closer look into the activity occurring in the Mash Tun. It
contains ActiveX FBD faceplates for the ramp/soak and grist input valve. Just as was
the case with the heat control PID loop, we can take manual control of the system and
manipulate the settings as desired.

60. Click the “Close” button to return to the “Brewhouse” overview graphic.
Reusing Operator Panel Graphics in a
FactoryTalk View SE Project.

About This Lab

For FactoryTalk Visualisation products - ‘FactoryTalk View ME’ (for use on

operator panels such as PanelView Plus, VersaView CE and Panel PC’s) and
FactoryTalk View SE there is one editing package FactoryTalk Studio.

There are two catalogue numbers for FT Studio:

Studio for FT View ME: 9701-VWSTMENE

Studio for FT View SE: 9701-VWSTENE

However essentially this is the same software, just the ME version has
had SE support disabled so ‘ME only’ users do not have to pay a
supplement for functionality that is not required.

Taking a scenario; the end user (you) are using FactoryTalk View SE as the main
plant SCADA. However there are some OEM packages provided to the plant as
finished individual machines or processes. These OEM’s are using FactoryTalk View
ME running on PanelView Plus operator stations to control the machine/process,
because only simple localised control is necessary.

Here are a couple of screen shots from two of these separate OEM packages:

Raw Product delivery to the plant. Raw Product Preparation

before use.
If you look at the VersaView terminals on the tables you will see the two applications
running, odd numbered tables with ‘Raw Product Delivery’ and even numbered tables
with “raw product Preparation’. These were downloaded by the instructor prior to the
lab starting. To know more about this please attend the Machine HMI lab.

Making Operator Terminal (FactoryTalk View ME) Projects

Available In FactoryTalk View SE.

We will start by opening the FactoryTalk View ME projects before transferring them
to FactoryTalk View SE.

1. Leave the current instance of FactoryTalk Studio open. Open a new instance
of FactoryTalk Studio.

2. When prompted select ‘Machine Edition’.

3. When prompted log in as User name: ‘ftadmin’, password: ‘ftadmin’.

 Why did you have to log into FactoryTalk again?

The reason is FactoryTalk has two directory scopes ‘Local’ and

‘Networked’. Without going into too much detail; these two directories
are used by different products depending on if they are designed to be
distributed or not. FactoryTalk View ME is designed to run on only a
single PC (or PVP/VVCE), so uses ‘local’ directory. FactoryTalk View
SE is designed to run across several distributed PCs, so uses
‘network’ directory. The two directories are completely separate,
hence the need to log in to each separately. The security was set for
both to use ftadmin, but they could be different.

4. Select ‘Raw Product Receiving’. Wait for project to open.

5. Notice you now have two instances of FactoryTalk Studio, one for ME and
one for SE.

In FactoryTalk Studio – Machine Edition, double click the display ‘Raw

Product Delivery’.
6. Click the ‘Test’ button to test the display.

Watch the graphic animate, the data is coming from a controller (SoftLogix) at the
front of the room.

7. If the graphic is animating excellent – now click the ‘Edit Display’ button, if not
animating let an instructor know.

8. Now position on the screen (by resizing the two windows) FactoryTalk Studio
ME and FactoryTalk Studio SE, as below: Then in FactoryTalk Studio ME
drag the display file ‘Raw Product Delivery’ to the Display ICON in
FactoryTalk Studio SE, as show below. NOTE move to your area (diagram
shows HMI_A, but use your area)
Before:
After:

The ‘Raw Product Deliver’ display has been migrated into FactoryTalk Studio SE.
 Where is the display ‘Raw Product Delivery’ saved?

Well for FactoryTalk View ME it is saved on the client (your) PC hard

drive, because ME is not distributed. But when the display was
migrated to FactoryTalk View SE (which is designed for distribution), it
was saved where it belongs – the HMI server at the front of the room.
This is completely automatic; all SE graphics are stored on HMI
servers.

9. Maximise FactoryTalk Studio SE. Open the newly migrated display ‘Raw
Product Delivery’, by double clicking it.

10. Click the ‘Test’ button to test the display.

Does the display animate, as in ME? (ignore the yellow lamp on the photo
cell).

You should find, No!

11. Click the ‘Edit Display’ button.

 Why did the animation not work?

The animation is based on tag values in the controller. The ‘path’ to

get to the controller is shown below for the ME Communications. Now
after the migration to SE all the tag names and animation were
migrated also. However because in this distributed SE application the
guidelines for separating data servers into a separate areas have
been followed. This in effect means two things:

1. Check that the ‘shortcut path’ in SE is correct to get to the same

controller on the network. (This has been done for you to ensure you
connect to the correct controller) See SE Communication below.

2. Make a slight change to the access path for the tags so they can
find the shortcut.

If this had been SE Station, this would not have been necessary,
because like ME, SE Station does not support the concept of areas.

ME Communications:

SE Communications:
12. Single click anywhere on the ‘Raw Product Delivery’ (grey) background.
Now press Ctrl + A (select all on the screen).

13. Now press Ctrl + R (tag substitution).

This has selected all the tags in the display in one go. Now the tag names are
fine, because they have not changed in the controller. The shortcut name is also
OK, no need to change that. However the location of the data server is slightly
different and we are going to change that, on all tags in one go.

14. Type the following exactly, without quotes and spaces.

In box Search For: ‘ [ ‘
In box Replace with: ‘ /DataServers::[ ‘
Uncheck the ‘Confirm Replacements’ check box.
Click ‘Replace’

You should receive the following message.

All tags updated at once.

What did we just do?

Essentially we replaced the ME short cut name [OEM_Skid] which in

ME is in the ‘home’ area with the syntax for SE with areas. The area
that hold the data server is called ‘DataServers’
15. Click the ‘Test’ button to test the display.

Does the display animate, now?

You should find, Yes! (let an instructor know if not)

16. Click the ‘Edit Display’ button.

17. Close and save this graphic.

18. If you wish you can repeat steps 1 – 16 for the display ‘Raw Product
Processing’. It’s your choice if you want to see the magic again.
To recap what we just did:

An OEMs had developed an applications in FactoryTalk View ME. We

simply took this graphic and dragged into FactoryTalk Studio SE. Then
by updating the tags to point to the data server the graphic was
working with all control and animation complete. Job done! This really
is integrated architecture.

Note: In fact the ‘whole’ ME project could have been migrated into SE.
Centralising Automation Security.

About This Lab

FactoryTalk Security
To address the growing risk of internal security breaches, FactoryTalk Security
delivers centralised authentication and access control by verifying the identity of
each user accessing critical systems. It then grants or denies their request to
perform specific actions based on their level of access. FactoryTalk Security
leverages the same FactoryTalk services used in other Rockwell Software
applications, allowing for centralized management and system-wide security
policies by referencing tags, data servers, security settings and other project
information from multiple data sources.

Working With Centralised Security

1. FactoryTalk security is centralised, meaning security users and groups

only need to be specified once and they are available to all users of
FactoryTalk services. In the case of the lab a couple of users have
already been set-up, these users will be available to all clients connected
to any application that is configured in FactoryTalk directory, remember
FactoryTalk Directory can host more than one application at a time.
In FactoryTalk Studio, scroll to the bottom; expand the system folder as
show below.

The Domain will be the lab domain name.

2. Some things to notice here:

 See how the ‘system’ is at the same ‘level’ in FT as the application SE_IA.

You see here the ftadmin user you have been using to log-in to FactoryTalk
for this lab. You can see that ftadmin is a member of the ‘administrators’
group.

Notice these two groups have a different symbol to the administrators group.
They include a chain link. This means these user groups are ‘linked’ to the
windows configured users and groups, i.e. the Windows security is adopted by
FactroyTalk Security. This means you can have one centralised security ie a
Windows Domain and use it not only for all the usual Windows security, BUT also
for ALL Rockwell Software applications that are FactoryTalk Services aware.
3. The FactoryTalk users have been added before the lab, and these users
have been applied to the FactoryTalk View project used in the lab. Now
we will look at the configured users and their security permissions.
In FactoryTalk Studio select the ‘RSView User Accounts’ menu item.

Here you see listed the same users and groups you saw in FactoryTalk.
But you do not see user permissions allocated in FactoryTalk View.
4. Click the ‘Add User/Group’ button.
Ignore the ‘Andy-Virtual’ part of the user and group name, you will see the
Domain name here.

Here you can see in the top frame the configured users, both FactoryTalk
users e.g. FTadmin and Windows linked group e.g. Operators and
Supervisors.

5. To see the permissions allocated to these uses, select the users and
expand the ‘security code’ box. For example: The operators group have
security code ‘A’ only

However the supervisors have an additional ‘B’, ‘C’ and ‘D’ security codes.
Click OK, when finished.

FactoryTalk Security, some interesting things to notice:

FactoryTalk Security is centralised all FactoryTalk aware software can

use these configured users and groups.

FactoryTalk Security uses profiles to allocate what users can do with

in each product. FactoryTalk View SE is a little different, it uses A-P
security codes, so as to be backwards compatible with previous
products.

FactoryTalk Security lets you not only specify centralised Users and
groups, which are FactoryTalk only or linked with Windows users BUT
which PC the user can log in from. So it is possible to enforce ‘line of
sight’ to the machine for operators.

6. So lets try implementing some of these security codes now: Open the
display from YOUR HMI area called ‘Phase Console’.
7. Select the ‘Button’ icon from the tool bar, by clicking once.

Now drag out an area like this:

To give:
8. Click the ‘Action’ tab, then the ‘Release Action’ ellipse button …
The command wizard will appear.

9. Select ‘All Commands and Macros’ in the left hand pane. Then select the
command ‘OpenLogix5000’. Then click Next.
10. Click the ellipse button (…) for RSLogix5000 project file. Then brose to
‘C:\Lab Files’. Then select the Logix ACD file for your controller (see table
above):
Controller1=Brew_Slot5.ACD
Controller2=Brew_Slot6.ACD
Controller3=Brew_Slot7.ACD
Controller4=Brew_Slot8.ACD

11. Click the ellipse button (…) for routine name. Wait for the ‘Routine
Browser’ to open. Then select the routine ‘Brew Procedure’ –
‘PhaseCmnd’
 This List of routines
has been provided by
RSLogix5000.

To give:

Click Finish.

12. Select ‘Up Appearance’ tab. Type ‘Code View’ in the caption box’. Click
OK.
To give (resize your button to fit the text if necessary).

13. Right Click the button: Select ‘Animation’, Visibility.

14. Type the text CurrentUserHasCode( B ) into the expression field for
Visibility. Click Apply and close.
15. Going to add one more change here so we can test the functionality. In
FactoryTalk Studio, still on the Phase Console display. Again select the
button control:

Draw another square on the screen:

16. Click the Action tab, then enter ‘Login’ command into the release action.

17. Click the ‘Up Appearance’ tab, then enter ‘Login’ to the caption box and
click OK.
18. Close and Save the graphic.

What did we just do?

Added a button to launch Logix5000, plus added code to hide the

button if the logged in operator does not have the security rights to
view the logix code.

Added a ‘Login’ button to allow an operator to login. We could have

added a logout button also.
 19. To test this we need to use the client and not the ‘test’ button.
On the FactoryTalk View Client Navigate to the Brew house screen. Click the
Brew Procedure display.

20. Click the ‘Login’ button. Enter user ‘fred’, password ‘fred’. Click ok.
 21. See how the ‘code view’ button is hidden, and that the diagnostic window
gives the log in information.

Remember fred only had the security code ‘A’ allocated to him, but to see the
button security code ‘B’ was required.

22. Now lets log ‘joe’ back in who has security code “A,B,C, & D’. Click the
‘Login’ button. Enter user ‘joe’, password ‘joe’. Click ok.
Now the ‘code view’ button returns. So click it now.
Wait for a few moments; it may take a little while to work the first time.

See how Logix 5000 is opened on the phase control code (offline).

23. Select ON-Line

 24. Right Click the Brew House proceduce and select ‘Monitor Equipment
Phase’.

To See:
 25. See how the FactoryTalk View display matches the actual Logix program.
Logix

View

End Of Lab Section

Working With Electronic Signatures.

About This Lab:

The Electronic Signature control is a standard product feature included with RSView
SE that provides the ability to record user information for specific control system
interactions. This feature is particularly beneficial for applications in regulated
industries that are subject to Federal guidelines such as:

21 CFR Part 11. Examples of a user activity that may need to be recorded for audit
purposes are modifications to process set points. By implementing the Electronic
Signature control, user credentials are verified using Windows security and recorded
prior to downloading new values. The information corresponding to the set point
change is recorded in the FactoryTalk Diagnostic Log.

Aside from recording modifications to control set points, the Electronic Signature
control can also be used to record other types of user interaction with the control
system. One such interaction could be the acknowledgement of alarms.

Implementing E-Signature (Electronic Signature) control.

In the SE application we have a button to start the brew cycle. Well maybe you
decide that this action must be confirmed by a supervisor and not just started by an
operator. So now we will implement the ‘Start The Brew’ with the E-Signature button.

1. Open the BrewHouse graphic. Click the ‘Start The Brew’ button and delete the
button (we are going to replace this with E-Signature).
2. Now select Objects Æ ActiveX Control

3. Draw a box outline for the ActiveX control.

Then scroll down the ActiveX list and select RSView SE Signature Button.

4. Double click the Signature Button and enter the following:

Caption:
 Signature:

Operation – Sent Command.

Operation Description – Start The Brew

Click the …

5. Browse to the SET command, click Next.

6. Select the following tag and enter a value of 1.

7. Now set the security: Here we are stating that an Operator can request the action, but a supervisor
must confirm.
You can go and change the colour if you require, otherwise select OK.

8. Save the BrewHouse graphic.

9. Now lets try it. But first log into FactoryTalk as an operator, at the moment you
are a FactoryTalk administrator.

Click Log Off, confirm with OK, then Exit. Now log on as User ‘fred’, password:
‘fred’
10. Now click the Reset Brew, followed by the Initialize. Followed by the ‘Start The
Brew’ button.

11. So here is the E-Signature button. You must enter a comment (enter anything
you like here). Then log in as user: fred, password: fred

12. Fred is authenticated against the RSAssetSecurity (windows security). Then an

approved by log in become active. Again the supervisor must enter a comment
(again, enter anything). Log in now a user name: joe, password: joe. Who is Joe?
A preconfigured supervisor.
 Click Accept.

13. Joe is authenticated against the security and then the Set command is executed,
and the batch starts.

14. Look in the event log to see that this has been logged. On the desktop open the
event log and look in FatctoryTalk Diagnostics.
You can watch your beer being made now, Cheers!

End of lab…
Features That Enhance and Speed Visualisation Project
Development.

About This Lab:

We will make some changes to the project you have been working on and see how
FactoryTalk View SE features enhance and speed the development of a Visualization
project.

Often in project development it is the simple features required in a project that can
cause complex solutions to be conceived. Here we will look at some very common
requirement and show how these can be achieved with ease using FactoryTalk View
SE.

• A fixed unmoving navigation windows or alarm banner, which stays visible

independently to what else is happening on the display. And that is re-sized
will not impact existing graphical displays.

• Switching the displayed language at runtime in all elements of the graphical

displays.

• Using a library objects in the project that are ‘linked’ to the original (parent)
object – so that if changes are made to the original – the linked objects will
also change without having to modify them in the project.

• Using standard code modules in controllers for controlling essentially complex

devices and linking them to standard graphical objects to complete a
working/tested system in a minimum of time.

Docked Displays.

FactoryTalk View SE can assign the property of ‘docking’ (attaching to the top,
bottom, right or left) a window on a display. This in effect means that the designer of
the system does not need to spend any effort in ensuring the display is visible in all
circumstances, this functionally is automatic. This is achieved by the docked display
reserving the required space and automatically re-scaling non-docked displays to fit
in the remaining display area.

1. Right click the displays icon in the project organiser for your area and select
‘New Display’.
2. Draw a display that is approximately as shown below, ie long and thin.

3. Click the Alarm & Event Banner icon and draw an Alarm & Event banner
object as shown. (If required make the display a little bigger to enable the
alarm & Event banner to fit.

4. Close this display and when prompted to ‘save’, select ‘yes’, and save as
‘AEBanner’.

5. Double click and open the overview screen

6. click select the button Icon

Draw a button on the ‘Overview’ display near the top.

7. When the properties dialogue box appears, enter the following command in
the release action box: Display AEBanner /DT.

This command tells the View

SE Client to show the display
we just created called
AEBanner and to DT Dock at
Top

8. Close and save the overview display.

9. Now launch the client again, by clicking

10. When the overview display is shown, click the new button you just added.
You will see that the display AEBanner is docked at the top of the display and
that display Overview is moved and sized automatically to make room for the
new docked display.
Click on the brewhouse area (centre of screen) to call the brewhouse display – you
will see that the docked display is not overwritten.

This is a wonderful functionality in enabling the developer to have screen

navigation and alarm banner always visible and not have to worry that a
display will hide the navigation, alarm displays.

11. Close the client

Run-time language Switching.

With the expansion of the European Union the possibility of a diverse workforce
in factories is becoming the norm rather than the exception. The ability to switch
languages in the runtime environment is very important. Not least so that
operators can understand in their native language the information being displayed
by the SCADA system and hence act in a timely manner with the correct actions.

There are two important aspects to run-time language switching. One is of course
making it easy to switch the language at run-time; and the other is that it is easy
for the developer to implement the language switching in the project at design
time.

This current project is in English, so now lets investigate how we would enable
French (or any other language) to be used.

1. Fist lets add French to the project. Select menu ‘Tools – languages’

2. Select ‘Add’
Then scroll down and select ‘French (France) fr-FR. Then click OK.

3. Click ‘Apply’

4. Click Export and select the following settings, then click ‘Next’.
 5. Tick the box for just your area.

Then click ‘Next’

6. Click the (…) and browse to select ‘Desktop’ as location to save the file. Click
‘Finish’.

7. Wait whilst the languages strings are exported. After a short while Microsoft
Excel will display a spreadsheet of the language export. To the right of the
spreadsheet can be seen the two languages in your project ‘English’ and
‘French’.
 Now all the language strings are in one spread sheet it is a simple
matter to have the languages translated. Simply put the language
translations for each of the ‘host’ (in this case English) into the column
for each selected language.

It is possible to have 20 languages defined at the sometime for

language switching. It is easy to see which phrases/words have been
translated because of the column format.

FactoryTalk View SE also ‘optimises’ the phrases/words. This in effect

means that if a phrase or word appears more than once in the project
(as is frequently the case). It is only necessary to translate the
phrase/word once – this is indicated by the use of the ‘REF:XXX’ you
see in the spreadsheet.

8. We do not have time to translate all of the phrases/words now, so we will just
change one to give the idea. In the Excel spread sheet search for the word
‘Brewing’. Note don’t worry if the RE:xxx is different in your application.

Now change the word ‘**UNDEFINED**’ in the French column to ‘Industrie

Brassicole’.

9. Save and Close the Excel spreadsheet.

10. Now to get the language translation back into the project we do an import. So
select menu Tools – languages. This time select ‘Import’.
 11. Select import from Excel and press ‘Next’.

12. Click (…), browse to the desktop and select the Excel file, click ‘Finish’.
Wait for the process to complete then click OK.

13. Now before we test if your modification worked. Lets look at how the operator
would change the language when in run time.

Open the display ‘AEBanner’ you made earlier by double clicking it in the project
manager.

14. Draw a buttons on the space to the right of the Alarm and Event Banner.
When the button dialog appears follow the following actions:

15. Select English en-US

16. Repeat with another button long side – but this time select the French
language.
 12. Note if we wanted we could put text in the buttons showing the language or
images showing the flags for the countries, for sake of time we will test as is.

13. Save and close the display AEBanner.

17. Now launch the client again, by clicking

When the overview display is shown – click the button to show the docked
display.

18. Now using the two new language buttons it is possible to switch between the
two languages. Note when switching to the French language you see your
translation for ‘brewing’ but all other text changes to a ‘?’. The reason for that
is to let you know that those phrases were not translated – which is correct
because we only translated one phrase/word.

19. Close the client.

Standard Faceplates And Controller Code To Speed

Development.

When developing SCADA applications an inordinate amount of time can be spent

on the development of graphics for standard devices, such as a drive. For this
reason Rockwell Automation provides sample code libraries for controller code
provided as AOI (Add On Instructions) which are single functional instruction
blocks for controlling the entire device. And in addition the SCADA faceplates for
not only interfacing with the device but giving full alarming, trending, error
information and help from the device manual.

These sample libraries can save many hours development work and give a
consistent, pre-tested operator interface.

1. In the controller the AOI for a PowerFlex Drive has already been inserted
and the input/output tags configured. This single AOI has all the detail
necessary for controlling a drive, the coding detail is hidden in the
instruction and all that is required is configuration. So essentially finished
for the controller coding. So Now what about a SACA interface to this
instruction, to allow the drive to be controlled and monitored?
2. In FactoryTalk studio import the faceplate we want to use. Right click the
Displays, and select ‘add Component Into Application’.

3. Browse to C:\LabFiles\ and select PowerFlex_4_40_400_Faceplate.gfx.

Then select ‘Open’.

4. The PowerFlex drive faceplate display will be imported. Double click to

open it.
5. To use this faceplate we just need to call it from a display – so lets do that
now. Open the display ‘BrewHouse’.

6. Right click the ‘motor’ and select ‘touch’ animation.

7. Click (…) to enter a command

8. Select the display command, then ‘next’.

9. Select the powerflex display we imported earlier. Check the /T –

Parameter tags box. Use the tag browse to select the tag MyPFDrive.
Finish
 10. Close and save the BrewHouse display.

11. Run the client again.

12. From the Overview display, click in the center to show the BrewHouse
display then click the motor.

13. If a PowerFlex were now connected you would have full control of the
device after completing these few steps.

There are many AOI and Faceplates available for hardware devices, these
enable very fast development of applications.

END OF LAB..