Introduction to the PlantPAx Process Library v5.

10
System Engineering Lab
c
 Important User Information
This documentation, whether illustrative, printed, “online” or electronic (hereinafter “Documentation”) is intended for use only as a
learning aid when using Rockwell Automation approved demonstration hardware, software, and firmware. The Documentation
should only be used as a learning tool by qualified professionals.

The variety of uses for the hardware, software, and firmware (hereinafter “Products”) described in this Documentation, mandates
that those responsible for the application and use of those Products must satisfy themselves that all necessary steps have been
taken to ensure that each application and actual use meets all performance and safety requirements, including any applicable
laws, regulations, codes, and standards in addition to any applicable technical documents.

In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter “Rockwell Automation”) be
responsible or liable for any indirect or consequential damages resulting from the use or application of the Products described in
this Documentation. Rockwell Automation does not assume responsibility or liability for damages of any kind based on the
alleged use of, or reliance on, this Documentation.

No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or software
described in the Documentation.

Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:
• properly using, calibrating, operating, monitoring, and maintaining all Products consistent with all Rockwell Automation
or third-party provided instructions, warnings, recommendations, and documentation.
• ensuring that only properly trained personnel use, always operate and maintain the Products.
• staying informed of all Product updates and alerts and implementing all updates and fixes; and
• all other factors affecting the Products that are outside of the direct control of Rockwell Automation.

Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell Automation is
prohibited.

Throughout this manual we use the following notes to make you aware of safety considerations:

Identifies information about practices or circumstances

that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.

Identifies information that is critical for successful application and understanding of the product.

Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you:
• identify a hazard
• avoid a hazard
• recognize the consequence

Labels may be located on or inside the drive to alert people that dangerous voltage may be present.

Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures.

Rockwell Automation | 2020

Introduction to the Process System for Engineering Lab
Before you begin............................................................................................................................. 5
About this Lab.......................................................................................................................................... 5
Tools and Prerequisites ........................................................................................................................... 5

Engineering - Developing a PlantPAx Project ......................................... 6

The Rockwell Automation Library of Process Objects - Reducing Development Time ............................... 6
Exploring the Controller Properties ........................................................................................................... 8
Logix Designer PlantPAx 5.10 Firmware Instructions................................................................................ 9
Instruction Usage ................................................................................................................................... 10
Using Studio 5000 Logix Designer to Configure the Controller ................................................................ 11
Organizing the Controller ....................................................................................................................... 11
Library 5.10 and 4.1 Compatibility .......................................................................................................... 12
The Logical Organizer............................................................................................................................ 16
Developing Controller Code using Library Control Strategies.................................................................. 17
Importing a Control Strategy Routine for a Level Indicator ...................................................................... 18
Importing a Control Strategy for a Single Speed Motor ........................................................................... 22
Adding MainRoutine Code to Execute the New Routines........................................................................ 24
Developing HMI Display using Library Global Objects ............................................................................ 29
Setting up the Path to the Controller in FactoryTalk Linx ........................................................................ 30
Using Library Global Objects to Configure HMI Displays ........................................................................ 32
Using a FactoryTalk View SE Client to View the HMI Application............................................................ 42
Reuse Code Easily using Logical Organizer ........................................................................................... 51
Adding TK400 HMI Objects to the FactoryTalk View Studio Display ....................................................... 56
Testing the New TK400 Pump and Level Routines and HMI Display ...................................................... 63

Commissioning the Devices – Introducing Logix Dialog Boxes ......... 65

Configuring an Interlock ......................................................................................................................... 71
Introducing the New Alarm Manager in Logix ......................................................................................... 79
Testing the Interlock............................................................................................................................... 81
Introducing the Logix Tag Based Alarms ................................................................................................ 84
Enabling the Logix Tag Based Alarms .................................................................................................... 84
Configuring the Alarm Banner and Alarm Summary Displays ................................................................. 87
Testing the Tag Based Alarms in the Alarm Banner ............................................................................... 90
Configuring FTAE Server-based Alarms for 4.1 Library (information only) .............................................. 91
Configuring a Pressure Control Loop and Variable Speed Pump ............................................................ 94

Rockwell Automation | 2020 3 of 132

Configuring Highly Integrated HART in the Process Controller ............................................................. 111
Highly Integrated HART built-in HMI graphics....................................................................................... 123
Ownership & Arbitration – Information Only section .............................................................................. 131

Rockwell Automation | 2020 4 of 132

Before you begin
About this Lab
This lab will familiarize the user with the steps necessary to start development of a PlantPAx™ 5.10 DCS project
using the Rockwell Automation Library of Process Objects v5.10. The user will configure a controller and HMI
application with pre-defined library routines and global objects. Using Library objects for common functions helps
to reduce engineering time. Templates are included in the library for both controller applications and HMI
applications to provide a consistent starting point for system implementation.

In this lab you will do the following:

• Leverage Control Strategies from the Rockwell Automation Library of Process Objects 5.10 for tank level
control using a pump, level indicator and PIDE control.
• Leverage HMI Application global objects to configure an HMI display with device objects and test the
controller program and HMI functionality by creating and using an HMI client.
• Leverage the Logical Organizer to take advantage of past engineering efforts to save time and reduce
errors.
• Configure new Logix Tag Based alarms.
• Configure new Highly Integrated HART
• Configure new Ownership & Arbitration.

Tools and Prerequisites

This lab is conducted using a VMWare Workstation© virtualized environment that allows the ability to process one
or more guest computer “images” on one “host” computer. All the software tools required for this lab are installed
within this image running on your lab PC.
These tools include:
• Studio 5000 Logix Designer V34
• FactoryTalk View Studio Software V13
• FactoryTalk View SE Client Application V13
• Rockwell Automation Library of Process Objects v5.10
• Rockwell Automation Library of Process Objects v4.10
• FactoryTalk Logix Echo v2.0

Rockwell Automation | 2020 5 of 132

Engineering - Developing a PlantPAx Project

The PlantPAx® system—a modern DCS—is a key component of The Connected Enterprise. It helps you meet key
market challenges through:
• Plant-wide control and optimization
• Scalable and modular architectures
• Open, information-enabled, and secure architectures
• Flexibility in delivery and support of the system

The Rockwell Automation Library of Process Objects can be used to quickly configure the controllers and HMI
FactoryTalk View Studio applications that comprise a PlantPAx Distributed Control System. They can help reduce
the engineering time to assemble and maintain your existing or new integrated architecture process applications.

The Rockwell Automation Library of Process Objects - Reducing Development Time

The Rockwell Automation Library of Process Objects is a predefined library of controller code (controller firmware
based for 5.1 and Add-On Instructions in versions 4.x and below), display elements (global objects), and faceplates
that let you quickly assemble large applications with proven strategies, rich functionality, and known performance.

Where to Get the Rockwell Automation Library of Process Objects

The Rockwell Automation Library of Process Objects can be downloaded from the Product Compatibility Download
Center at: https://compatibility.rockwellautomation.com/Pages/home.aspx

The Studio 5000® Automation Engineering & Design Environment™ combines engineering and design elements
into one standard framework—a common design platform that helps to drive down the time and cost to design,
develop, and deliver machines and equipment. Controller properties and code are modified using Studio 5000
Logix Designer software.

Rockwell Automation | 2020 6 of 132

Click the Studio 5000 icon on the desktop or bottom banner to open Studio 5000.

or

Wait for the Studio 5000 Common Launcher to appear. Under the Recent Projects tab, click the Logix Designer
controller project file (.acd) named LAB.

Wait while Studio 5000 Logix Designer opens.

Rockwell Automation | 2020 7 of 132

Exploring the Controller Properties
Open the Controller Properties.

Notice the Controller Type is 1756-L85EP, the new PlantPAx Process Controller.
Now click on the PlantPAx tab.

Notice the Checkbox to Use PlantPAx Tasking Model. This is checked by default and will create default Periodic
Tasks in your Controller Organizer.

Rockwell Automation | 2020 8 of 132

The PlantPAx Tasking Model, a Process Controller exclusive, automatically creates a consistent task model in
Logix Designer with the following tasks:
• Fast (100 ms)
• Normal (250 ms)
• Slow (500 ms)
• System (1000 ms)

Tasks are created with period, priority and names already specified according to PlantPAx guidelines. Starting a
project with the PlantPAx periodic tasks already created has benefits including shorter time dedicated to project
creation and layout and a consistent project structure that aligns with PlantPAx guidelines.
Note that in this lab we will be using the Normal task.

Logix Designer PlantPAx 5.10 Firmware Instructions

The new PlantPAx 5.10 Embedded objects are the next generation of the Process Objects Library, available
when using one of the new Process Controllers. These new controllers extend the existing Logix controller family.
Everything that a standard controller does, these controllers do. They share the same software tools and are
meant to provide a more process focused experience for customers. PlantPAx Objects are now built-in to the
design pallet of Logix Designer in v33 (and above). Control Strategies, efficiency tools, and HMI objects will still
be made available through download via Rockwell Automation Product Compatibility and Download Center.

Previously released libraries will continue to be available and supported. They are compatible with the new
Process Controllers as well as the older controllers.

Rockwell Automation | 2020 9 of 132

Instruction Usage

A new feature exclusive to the PlantPAx Process Controller is the ability to see a dashboard of each task and the
instructions used in your controller file. This feature can be used with the embedded webpage to see CPU
utilization and to avoid task overlap.

This feature enables consistent performance and visibility into task loading during the engineering cycle. It allows
the engineer an easier way to identify the number of control strategies being used in a processor. This information
can be used along with published guidance from our PlantPAx Characterization Lab to ensure the performance of
your system.

The Instruction Usage can be accessed by clicking the Instruction Usage button on the PlantPAx tab.

The popup window shows how many instances of each object type there are per routine based on the PlantPAx
Tasking Model of Fast, Normal, Slow, and System tasks.
Close the Instruction Usage window.

Rockwell Automation | 2020 10 of 132

Close the Controller Properties window.

Using Studio 5000 Logix Designer to Configure the Controller

In this section of the lab, you will learn how to develop and configure your controller using sample process routines
imported into a controller application to develop a control strategy for a storage tank. The strategy will include a fill
pump, a discharge pump and tank level indication.

Organizing the Controller

From an execution perspective the controller is separated into Tasks that run at different execution speeds, from
as fast 50ms to as slow as 10sec. The Tasks allow us to make the best utilization of the processor in terms of
execution time.

The lab controller has been pre-configured using a sample Process Library v5.1 controller template file. The library
v5.1 controller template has three pre-configured Tasks: a Fast (100 ms) task, a Normal (250 ms) task, and a Slow
(500 ms) task. Each Task includes a pre-configured Program. The Programs can be used as organizational
“containers” to speed up engineering time. In this lab you will be developing code in the Normal Program.

From an organizational perspective the Programs are separated into Routines. In this lab you will develop a tank
Program that includes Routines for a fill pump, a discharge pump and level indication.

Notice the Controller Organizer and Logical Organizer tabs at the bottom left. These are windows that allow
different view perspectives of the controller.

Rockwell Automation | 2020 11 of 132

The Controller Organizer window is used to view and configure the controller from an execution and utilization
perspective.

Whereas the traditional Controller Organizer is used to view and configure the controller from an execution time
and utilization perspective (Tasks), the Logical Organizer window provides a way to view and create an
organizational model of the system (Programs and Routines). This allows operators and maintenance to
troubleshoot the system more quickly while new features such as Selecting Multiple project components like Add-
On-Instructions (AOI's), User Defined Tags (UDT's), Programs, and then copy/paste, drag/drop, export/ import them
as one to reduce engineering time.

Library 5.10 and 4.1 Compatibility

Mixed library applications are supported in the Process Controller and allow for gradual adoption of the 5.10
technology. The PlantPAx 4.1 library lives on in parallel with Process Library v5.10. Both Add-On Instruction (AOI)
and 5.10 objects co-exist together in PlantPAx. The 4.1 and 5.10 faceplates can co-exist in an HMI application
and look and feel the same to an operator.

In this lab section you will add Process Library v5.10 Control Strategies to the program named TK300 (for tank 300)
that already contains 4.1 code. Later in the lab you will use the Logical Organizer window to quickly copy TK300 to
a TK400 program.

Expand the program named TK300 in the Normal Task to view the existing routines.

Rockwell Automation | 2020 12 of 132

Notice the MainRoutine. Each program contains a main routine. The main routine is the first routine that will execute
in the program. It consists of ladder-logic code with Jump-to-subroutine (JSR) elements that execute all the other
routines in the program.

Also notice the existing PMP301 routine. This is a routine implemented using the Process Library 4.1 objects.
The Process Library 4.x resides in the controller as Add-on-Instruction (AOIs). For Process Library 5.1 the library
blocks reside in the controller firmware. Embedded native process objects help reduce engineering costs and drive
consistency in projects. In this lab, all application development will be done using the new 5.1 library and 5.1
workflow but to show compatibility with the 4.1 library the PMP301 routine was pre-configured in the lab controller.
Note that from an operator’s viewpoint the 4.1 and 5.1 graphical objects and faceplates have the same look and
feel.

Double-click on the PMP301 routine and then in the editing window click the PMP301 P_Motor block’s ellipsis
button. Note that the block is a P_Motor type with a tag name of PMP301. The prefix “P_” (for process) indicates
that the block is a 4.1 library object. The corresponding motor block in the 5.1 library is named PMTR with the prefix
“P” for process.

Rockwell Automation | 2020 13 of 132

Note that this is a library 4.1 block that is an Add-on-Instruction (AOI). Notice that the P_Motor block properties
window consists of only two tabs, a Parameters tab and a Tag tab. With the 4.1 library much of the engineering
workflow and configuration (configure alarms, set points, interlocks, tag descriptions) is done from the Client
faceplates.

New for the 5.1 Library is the addition of tag properties Dialog Boxes in Logix. The new Dialog Boxes consist of
ten tabs (see example screen capture below). Using Extended Tag Properties which allow for more access to data
in the controller the Dialog Boxes allow for a single place to configure alarms, set points, interlocks, tag descriptions
and more. You will explore the new PlantPAx Dialog Boxes later in the lab.

Note: Example of new 5.1 Dialog Box:

Rockwell Automation | 2020 14 of 132

Close the PMP301 P_Motor Properties window.

A simulation routine has also been added. In the lab this simulation code will allow the lab student to test their new
device code. Double-click on the routine named Simulation. Notice the final output from this simulation logic is
an output connector LI300_Inp_PVData (scroll over to the right as needed). This output will be the simulated input
value for a tank level indicator routine that will be added later.

Close the Simulation routine.

Close the PMP301 routine.

Rockwell Automation | 2020 15 of 132

The Logical Organizer

The Logical Organizer allows one to create folders that correspond to process areas. Programs (with their
associated routines) from one process area can be configured in various tasks depending on their execution
requirements. The Logical Organizer allows one to create folders and drag the various programs into these
folders for easy troubleshooting for each process area (Logical Organizer folder).

In addition, when using the PlantPAx Configuration Tool for Alarms, Tags, and Historian, an alarm group is
generated for each Logical Organizer folder and will define the structure of the resulting A&E database. Alarms
defined within each folder will be generated respecting this structure.

For Operations’ functionality, it is important that all the devices within each Logical Organizer folder can be
represented on a single HMI display. When an alarm associated with the HMI display (and Process area) occurs,
a visual indication on the associated navigation button can be activated to assist operator troubleshooting.

Click the Logical Organizer tab.

Expand the TK300 program.

Rockwell Automation | 2020 16 of 132

Note, in the following section, you will add new code including a pump and a level indication to the program
named TK300.

Developing Controller Code using Library Control Strategies

Control Strategies from the RA Library of Process Objects support the concept of re-use engineering to save time.
We can save engineering time by starting with pre-configured and tested control strategies. Simply import them
into the controller application as routines. By organizing a controller into Programs (for example each Tank is a
Program) and Routines (levels, pumps, valves) we simplify the location of a desired piece of code and can re-use
code in line with best practices and standards management.

To reduce implementation time and minimize risk, Control Strategy templates are available from PlantPAx that
provide pre-connected functionality to meet control system needs. These individually importable Function Block
Diagrams include instructions from the Rockwell Automation Library of Process Objects that have been
configured to represent many common control and equipment scenarios encountered in process automation (i.e.,
I/O monitoring, regulatory control, motor, and valve control).

Later in the lab, because we organized the controller (by Tasks, Programs and Routines), you can easily copy the
code for a complete tank program, including all components like AOIs, UDT's, Routines, Tags, and then paste it,
as one, to create more tanks to reduce engineering time.

Rockwell Automation | 2020 17 of 132

Importing a Control Strategy Routine for a Level Indicator
In this section, you will import a Library 5.1 Control Strategy routine, named (RA-LIB)CS_PAI_5_00-
03_Routine.L5X, for an analog input (PS_PAI) into the program named TK300.
Right-click on the program named TK300. From the menus select Add and then Import Routine.

Navigate to the C:\ Process_Library_v5.00.04 \ v5.00.04 \ Process Library \ Control Strategies - L5X \
CS_PAI folder. Confirm that you are in the CS_PAI folder.

Select the routine named (RA-LIB)CS_PAI_5_00-03_Routine.L5X, and click Open.

Rockwell Automation | 2020 18 of 132

Wait for the Import Configuration window to open.
Click on the Tags folder. Note the tag references are all prefixed with the default tag XT101.
You will modify the final name and tag names by replacing the generic XT in the tag references (XT because a
transmitter analog input can be a pressure, temperature, level …) and replace them with LI for level indicator during
the routine import. The 101 will be replaced with 300 because we are working on tank 3 code.

Click the Find/Replace button.

Find all the instances of XT101 in the tag references and replace with LI300.Then click the Replace All button.

Rockwell Automation | 2020 19 of 132

Note that 6 occurrences of XT101 were found and replaced with LI300. Now click OK.

Wait for the import to complete. Once the import completes, a new routine named LI300 is added to the TK300
program. Double-click on the new LI300 routine to open the function-block editor and view the new code.

Verify that all the instances of XT have been replaced with LI300 in the tag name and input/output (I/O) reference
connectors (as shown below). The level indication routine is complete, and the input/output (I/O) reference
connectors are associated to simulation tags for testing.

Rockwell Automation | 2020 20 of 132

Note that this is a PlantPAx Library 5.1 block based in the firmware therefore the alarms, text strings, set points,
interlocks (…) are now configurable from within Logix Designer using the new Properties Dialog Boxes. Click the
ellipsis button on the PAI block with tag name LI300.

When the new 5.1 Properties Dialog Box opens, notice the new tabs: General, PV Fail Check, Advanced, HMI,
Alarms, Parameters and Tag. Note that the 4.1 library blocks only have a Parameters and Tag tab. Click the HMI
tab

From the HMI tab change the Display Label to LI300 and click OK.
Later in the lab you will explore the other tabs of the new 5.1 Dialog Boxes.

Rockwell Automation | 2020 21 of 132

Importing a Control Strategy for a Single Speed Motor

Next is to import a new routine that will contain the code for a single speed motor. Right-click on the program
named TK300. From the drop-down menus select Add and then Import Routine.

Navigate to the C:\ Process_Library_v5.00.04 \ v5.00.04 \ Process Library \ Control Strategies - L5X \
CS_PMTR-1S folder.
Confirm that you are in the CS_PMTR-1S folder.
Select the motor routine import file named (RA-LIB)CS_PMTR_1S_5_00-03_ROUTINE.L5X and click Open.

Wait for the Import Configuration window to open. A motor can drive a blower, conveyor, mixer, agitator, or a
pump. Since you are configuring a pump to discharge the tank you will change the name and tags of the new
routine to PMP302.

Rockwell Automation | 2020 22 of 132

Click the Find/Replace button.

The tag references in the library routine are prefixed with a generic MT301 designator for motor. During the import
you will find and replace the MT301 with PMP302 for all the tags.

Find all instances of MT301 and replace with PMP302. Click the Replace All button. Then click OK.

Wait for the import to complete. A new routine named PMP302 will be added.
Double-click on the new PMP302 routine to view the code. Verify that the tag name is PMP302 and the cross-
references have been changed to reference PMP302.

Rockwell Automation | 2020 23 of 132

Close the PMP302 routine.

And then close LI300 routine.

Adding MainRoutine Code to Execute the New Routines

Next you need to add instructions to execute the two new routines. You will do this by adding rungs to the
MainRoutine that include “Jump to Subroutine” (JSR) instructions. The “Jump to Subroutine” (JSR) instructions will
execute the Pump and Level subroutines.

Double-click the MainRoutine for TK300.

The ladder Code Editor will open. The MainRoutine is written in ladder logic code. The MainRoutine is configured
as the routine in the task/program that runs first. It is used to monitor and alarm the Task’s execution time and to

Rockwell Automation | 2020 24 of 132

execute other routines via JSRs. Notice the JSR on each line of the Main Routine …the main routine always runs
and executes the JSRs to run the other routines.

Click on Rung 0 to select the rung (indicated by a blue box) and then right-click and select Copy Rung.

Go to the end of the ladder and Paste twice to add two new JSR rungs.

Two new rungs have been added to the bottom.

Notice that after pasting the copied rung the JSR still references the Simulation routine.

Rockwell Automation | 2020 25 of 132

The new JSR on rung 2 needs to have the Routine Name parameter changed to PMP302. Use the drop-down
arrow and select PMP302.

The new JSR on rung 3 needs to have the Routine Name parameter changed to LI300.
The rungs should look like below when completed.

Close the MainRoutine.

The coding for TK300 is complete and ready to verify for errors and then download to the controller.
To verify the code for errors, click the Verify Controller button.

Rockwell Automation | 2020 26 of 132

Confirm that there are zero errors.

In the upper left of the Logix Designer window click the Save button.

Click on the Controller Status down-arrow and select Download from the drop-down window.

Click Download again to confirm the download.

Wait for the controller download to complete. This may take a couple of minutes but with library 5.1 blocks in
firmware the downloads to the controller go much quicker than with the 4.1 library AOIs.

Rockwell Automation | 2020 27 of 132

Click on the Controller Status down-arrow and select Run Mode from the drop-down window.

Click Yes to verify the mode change.

Verify that the controller status button is green and indicates in Run mode.

Minimize the Logix Designer window.

Section Summary

Logix Designer provides a way to view and create an organizational model of your controller code. Application
Controller Templates and Control Strategies are available with pre-configured library content to start your Logix
project. In the lab, Library Control Strategies were used to quickly add pump control and level indication code to the
project, supporting the concept of re-use engineering to save time.

Rockwell Automation | 2020 28 of 132

Developing HMI Display using Library Global Objects

In the next section of the lab, the user will configure the HMI application (a storage tank display) with pre-defined
library faceplates and global objects. Using Library objects for common functions helps to reduce engineering
time. Templates are included in the library for HMI applications and frameworks to provide a consistent starting
point for system implementation. Click the Studio 5000 icon on the bottom taskbar or on the desktop to open
Studio 5000.

Wait for the Studio 5000 Common Launcher to appear. In the Recent Projects tab click PlantPAx.
This will open the existing FactoryTalk View Studio SE HMI project in the HMI designer software Studio 5000.

Wait while FactoryTalk View Studio opens.

FactoryTalk View Studio is configuration software for developing PlantPAx HMI applications. With FactoryTalk
View Studio, you can create displays and faceplates using a full-featured graphics editor. The Studio 5000®
Automation Engineering & Design Environment™ combines engineering and design elements into one standard
framework—a common design platform that helps to drive down the time and cost to design, develop, and deliver
machines and equipment. Controller properties and code are modified using Studio 5000 Logix Designer software.

With the PlantPAx Objects now part of the firmware of the controller, it simplifies lifecycle management. Firmware
upgrades automatically manage any changes that come to the tag database or pins of the library objects that may
need to be rewired. This reduces the risk to the application when modernizing the system. Additionally, this
creates a consistent data structure and interface for the customer. This new format also drives consistency
between applications, regardless of who developed them.

Rockwell Automation | 2020 29 of 132

Setting up the Path to the Controller in FactoryTalk Linx

Whether the library is 4.1 or 5.1, every HMI project needs to have the communication paths to the area controllers
defined in the FactoryTalk Linx communication setup. The path or “shortcut” name is used to point at a particular
controller, in our case the Lab controller in slot 2 of the Echo rack. This path will be used later in the lab when
configuring graphical device objects for the devices in the Lab controller.

Expand the PlantPAx_Data_Area folder.

Expand the FactoryTalk Linx folder.
Double-click on the Communication Setup.

In the Communication Setup window, note the device shortcut named LAB. Shortcut names are used in the

Rockwell Automation | 2020 30 of 132

graphics to connect a graphical element to a specific controller. Note that the existing path for the shortcut named
LAB is pointed to the Emulate (Echo) Controller in Slot 2 at IP address 127.0.0.4.

The check boxes for the Extended Tag Properties are used for the library 5.1 Logix Dialog Boxes. Extended Tag
Properties have been available since v31 of Logix and are used in the 4.1 library for only the PIDE and motion
blocks. For library 5.1 it has been expanded to allow process device control. Extended Tag Properties reduce the
need for string tags and allow for language translation. Confirm the boxes are checked.

Click OK to close the Communication Setup window.

Rockwell Automation | 2020 31 of 132

Using Library Global Objects to Configure HMI Displays

Expand the Displays folder.

Note the new folder structure in FactoryTalk View’ Studio for displays. With Studio v12 you can now create sub-
folders in the Display folder. For this lab, the lab specific displays are all in the folder named LAB. Note that displays
for the framework (button bars, alarm summary, level 1/2/3 display templates …), the 4.1 library displays, and the
5.1 library displays are all included and compatible in this application.

Minimize all the display sub-folders except for LAB.

Double-click on the display named “(LAB) p2f storage tanks 3_4” to open the display in the editor.

Note that the pump object for the fill pump, PMP301, is already configured on the display using PlantPAx Library
4.1 objects. Pump PMP301 is be used to show compatibility between the 4.1 and 5.1 libraries. In this lab you will
be using the new PlantPAx Process Library 5.1 objects

Rockwell Automation | 2020 32 of 132

This display started as a blank Framework Library Level 2 template display. We started with this display because
navigation to it is pre-configured on the library template navigation button bars. The next step will be to add to the
display a pump and level object for Tank300, and then link the new graphical objects to the new tags in the
controller. The easiest way to do this will be to use PlantPAx library Global Objects. A global object is an HMI
display element that is created once and referenced multiple times on multiple displays in an application. When
changes are made to the original (base) object, the instantiated copies are automatically updated.

HMI Global Objects

For rapid development of information-rich operator displays, the Rockwell Automation Library of Process Objects
provides a collection of Global Objects that are linked to the Process Object Library code in each controller with
a drag and drop wizard. Display elements include motors, valves, analog and digital indicators and even a
sequencer. Together with the HMI framework they allow for rapid development of display graphics and navigation.
In the Explorer window, expand the Global Objects folder.

Rockwell Automation | 2020 33 of 132

Scroll down in the Global Objects folder until you find the global object named “(raP-5-SE) Graphic Symbols -
PMTR”. The raP-5-SE prefix stands for Rockwell Automation Process library version 5.1 for Studio SE applications.
All the 4.1 Library displays, and global objects are prefixed with RA-BAS, which stands for Rockwell Automation
Base library. The 4.1 library is also available for View ME.

Double-click on the Global Object “(raP-5-SE) Graphic Symbols - PMTR” to open the display editor.

Each device object is preconfigured in various orientations and with optional features. For example, the motors
are displayed configured as pumps, conveyors, blowers, agitators, fans, and motors. Drag-and-drop (or
copy/paste) a Pump object from the Global Objects display to the storage tank graphic.

Next, in the Global Objects folder, and double-click on the Global Object named
“(raP-5-SE) Graphic Symbols – PAI”. The PAI stands for process analog input.

Rockwell Automation | 2020 34 of 132

The analog input objects are preconfigured as trend boxes or analog indicators and with optional features such as
capture areas and target lines. Select a trend box and an analog indicator object from the PAI Global Objects
display. Drag-and-drop (or copy/paste) both a trend box and an analog indicator object from the PAI Global
Objects display to the storage tank display.

Move the new objects to look like below:

Rockwell Automation | 2020 35 of 132

Right-click on the new discharge pump object and select Global Object Parameter Values from the selection
menu.

In the Global Object Parameter Values window, you need to enter the tag Value for the pump into parameter 1.
This parameter links the tag PMP101 (that we created earlier in the Logix code) to this instance of the pump
object. For parameter 1, click on the ellipsis button in the column named Tag to open a Tag Browser window.

Note that in the 4.1 library blocks (see example below) the second parameter is the Path. This is used for
navigation to other objects. To improve development workflow, for the 5.1 library this parameter is removed, and
the path data is parsed from parameter 1.
Example only of 4.1 Library:

Rockwell Automation | 2020 36 of 132

The Tag Browser window allows you to access controller tags via a browser window that presents the controller
tags in a logical hierarchy. Click the Refresh All Folders button.

Expand the PlantPAx_Data_Area folder. Expand the sub-folder named LAB (“LAB” is the data server shortcut
name for the controller). Expand the subdirectory named Online.

Scroll-down the list and select the tag PMP302 and click OK.

Verify the updated Motor Tag in parameter 1 is as shown below. Note the other parameters. For library 5.1,
parameter 2 is the X coordinate for the faceplate pop-up and parameter 3 is the Y coordinate. For parameter 2 and
3, enter the X/Y parameters /X460 and /Y700 respectively.

Rockwell Automation | 2020 37 of 132

Then click OK.

Right-click on the new Analog Input trend object and select Global Object Parameter Values from the selection
menu.

For parameter 1, click on the ellipsis button in the column named Tag to open a Tag Browser window

Rockwell Automation | 2020 38 of 132

The Tag Browser window will open. Scroll to and select LI300 and click OK to accept the updated parameter.

Verify the updated Tag in parameter 1 is as shown below.

Note the other parameters. For parameter 2 and 3, enter the X/Y parameters /X700 and /Y300 respectively.

Click OK to accept the updated parameters.

Rockwell Automation | 2020 39 of 132

Right-click on the new Analog Input object and select Global Object Parameter Values from the selection menu.

Configure the level indicator to match the level trend object parameters (as shown below), save the changes, and
close the parameters window.

Click on the Save button to save the updates to the display.

Rockwell Automation | 2020 40 of 132

Note the graphic display is functional but can be customized by adding tanks, piping, and more using global objects
from the Process Library. Due to time constraints in the lab, we will not customize the display at this time. Note that
PlantPAx graphics are 2D (not 3D) and gray-scale to follow ISA-101 standards. The ISA-101 Committee establishes
standards, recommended practices, and technical reports pertaining to human-machine interfaces in manufacturing
applications. The areas covered within ISA101's scope include menu hierarchies, screen navigation conventions,
graphics and color conventions, dynamic elements, alarming conventions, security methods and electronic
signature attributes, faceplate conventions, help screens and methods used to work with alarms. PlantPAx graphics
follow ISA-101 guidelines. As newer libraries are released, the project library objects can be upgraded using the
Process Library Migration Tool.

Minimize the FactoryTalk View Studio window.

Rockwell Automation | 2020 41 of 132

Using a FactoryTalk View SE Client to View the HMI Application

The application (code and HMI) is finished; test it by running the FactoryTalk ViewSE Client. FactoryTalk View
SE Client is software for viewing and interacting with the FactoryTalk View SE application at run time. Operators
can use the client to view and interact with multiple graphic displays, manage alarms, view trends, and adjust set
points. Click on the PlantPAx HMI client icon at the left on the desktop.

When the client opens, your application window appears with the layout of the selected template. Notice the
docked Header and Footer displays. They are part of the Framework displays contained in the HMI template that
also includes button bars and alarm history and help displays. The template Header graphic is used to display
information that will always be visible to the operator, such as the current date and time, name of the current area,
general alarm and system status and navigation buttons.

Rockwell Automation | 2020 42 of 132

Click on the TK300/TK400 Lab button on the button bar.

All global objects have an associated faceplate which appears when the global object is clicked. These faceplates
require no additional configuration. When an object has additional support functions linked, such as Run Time
Monitor, Interlock Block, Permissive, or others, the faceplate for these extended functions will also be accessible
from the faceplate. You are now ready to test our application by starting the pump and filing the tank.

Click on the PMP301 pump object to open the pump control operator faceplate.

Note that PMP301 is a library 4.1 faceplate. For library compatibility the 5.1 faceplates have same look and feel
from the operator’s perspective as the 4.1 faceplates. Click the Start button to start the fill pump.

Note that the level in the tank has filled to 59%. This indicates that the new code and HMI objects for the level
indication are functioning correctly. Notice that the fill pump has been stopped (interlocked) when the fill level was
reached. This was done with interlock code. The interlock status is indicated on the pump object and the
faceplate.

Rockwell Automation | 2020 43 of 132

Click on the Interlock Button on the faceplate.

Note the interlock condition. If you had multiple interlocks active for the device the first interlock to occur would be
indicated as “first in “for troubleshooting. Click the X to close the interlock faceplate.

Notice that the label and descriptions for the new discharge pump object are incorrect and need to be configured.
For small applications (such as this lab or skid maintenance) updating the tag descriptions and labels can be
done on-line using the new Process Library 5.1 Logix Dialog Boxes, or for 4.1 applications from the Maintenance
tab of the device faceplates in the running Client application. For bulk configuration changes of these parameters
PlantPAx 5.1 includes a “PlantPAx Configuration Tool’” that can be used. This tool can be used both off and on-
line.

Click on the new discharge pump.

If needed, Acknowledge to clear the IO fault indication.

Rockwell Automation | 2020 44 of 132

Start the PMP302 pump.

Wait for the tank to empty. Note that as the tank empties the fill pump PMP301 is no longer interlocked and that
low level alarms are indicated on the faceplate and device objects. But notice the new discharge pump, while
functional, did not stop when the tank was empty. This could possibly damage the pump. Later in this lab you
will add an interlock condition to this pump to protect it from running with an empty tank.

Stop the discharge pump.

Rockwell Automation | 2020 45 of 132

Click on the level indicting trend chart to open the faceplate.

Note the alarm status indications. Click on the Alarm tab.

Click on the “Acknowledge and Reset” the alarms button.

Rockwell Automation | 2020 46 of 132

Note the alarms still exists but have stopped flashing because they are acknowledged. Start the fill pump
PMP301 again.

Wait for the tank to fill and click on thePMP301 Interlock button to open the interlock faceplate.

Rockwell Automation | 2020 47 of 132

Click on the Maintenance tab of the Interlock faceplate.

Click on the Display Advanced Properties button

Note that the interlock is configured to be “Can Bypass”. This selection can only be made with the proper login
credentials. An engineer would make the decision if a specific interlock can be bypassed. The operator can then
make the decision to bypass the specific interlock if needed.

Click on the HMI Configuration Tab and notice that the interlock description can be modified from the 4.1
faceplate.

Rockwell Automation | 2020 48 of 132

Change the label and tag to PMP301.

Close the interlock advanced properties faceplate.

Check the box to enable the Fill Level Reached interlock to be bypassed and close the interlock faceplate.

On the PMP301 motor faceplate, click on the Maintenance tab.

Rockwell Automation | 2020 49 of 132

From the Maintenance tab the operator can now make the decision to bypass the selected interlock(s). Slide the
Bypass Enabled selector to Yes. Click yes at the pop-up window to confirm the selection.

Notice the interlock bypassed indicators. Click on the “Home – Operator” tab button.

Notice the pump can now be started, for maintenance or emergency service, even in an interlock condition.

Rockwell Automation | 2020 50 of 132

Close all open faceplates.

Section Summary:
You tested the new Tank discharge pump and level indication and interacted with the View SE application from
the FactoryTalk View SE Client. The section showed how Operators can use the client to view and interact with
multiple devices, acknowledge faceplate alarms, view interlocks, and bypass interlocks. Now that the new tank
300 code has been tested the code can be copied to a new tank 400.

Reuse Code Easily using Logical Organizer

The new Logical Organizer provides a way to view an organizational model of the system. This allows engineers
to modify the system more quickly. New features such as Selecting Multiple project components like AOI's,
UDT's, Programs, and then copy/paste, drag/drop, export/ import them as one to reduce engineering time. In this
section of the lab, you will be doing a copy/paste of program TK300 to a new tank program TK400. For this
section of the lab, you will work in the Logical Organizer.

Switch to the Logix Designer window by using the Alt+Tab keys on your keyboard

In the previous section of the lab, you made Logix code additions offline and then downloaded the controller. In this
section you will be making code changes online with the running controller to demonstrate how code can be added
without interrupting the operations of a running plant. Open the Logix designer window.

Confirm that the controller is online and running.

If not in the Logical Organizer window, click on the Logical Organizer tab.

Rockwell Automation | 2020 51 of 132

In this section of the lab, you will be doing a copy/paste of program TK300 to a new tank program TK400. Note
that the program, or routine, duplication can also be done as an export/import). Right-click the program TK300
and click Copy.

Right-click on the Logical Model (of the controller named) LAB and click on Paste Special with
Configuration.

Rockwell Automation | 2020 52 of 132

Wait for the Import Configuration window to open. Click on the Find/Replace button.

Find and replace 30 with 40 and click the Replace All button. This will replace all tags 300 with 400, 301 with
401, and 302 with 402.

Click OK.

Because the controller is running and you are making edits to the code online, you need to choose how the edits
will be imported. Click OK to “Finalize All Edits In Program” during the import.

Rockwell Automation | 2020 53 of 132

Note that the TK400 program has been added. But the routine names do not get updated during the
find/replace when you copied the TK300 program to the new TK400 program. In the lab, you must rename the
TK400 routines through each routine’s properties window.

Expand the TK400 program.

Right-click on the LI300 routine. Select Properties from the drop-down window.

Rockwell Automation | 2020 54 of 132

Change the routine Name to LI400 and click OK.

Using the routine Properties window (like above), rename the other two routines to PMP401 and PMP402 as
below:

Minimize the Logix Designer window.

Rockwell Automation | 2020 55 of 132

Adding TK400 HMI Objects to the FactoryTalk View Studio Display

In the next section of the lab, the user will add TK400 device objects to the storage tanks display by copying the
TK300 display objects and configuring them for TK400. Using copy/paste helps to reduce engineering time.

Switch to the FactoryTalk View Studio window.

The FactoryTalk View Studio window should still look as shown below. Use the cursor to highlight all the
TK300 objects.

Click Arrange from the editing selections on the upper menu bar. Click Group from the drop-down menu. This
groups the Tank 1 objects.

Rockwell Automation | 2020 56 of 132

Select the grouped tank and right-click and select copy …

Right-Click on the display background and select Paste from the drop-down.

Rockwell Automation | 2020 57 of 132

Position the new tank to the right of TK300.

Right-click on the new tank group and select Tag Substitution.

Rockwell Automation | 2020 58 of 132

For the level tags, in the Tag Substitution window Search for LI300 and Replace with LI400. Click the Replace
button.

Click the Replace All button.

Click OK.

Rockwell Automation | 2020 59 of 132

Repeat the above Tag Substitution steps to search and replace PMP3 with PMP4. This will replace PMP301
with PMP401 and replace PMP302 with PMP402.

Click on the grouped TK400 to highlight it. Click on the Arrange button on the upper banner and choose
Ungroup.

Rockwell Automation | 2020 60 of 132

Right-click on the TK400 fill pump PMP401 and select Global Object Parameter Values.

Change the parameter 3 for the faceplate X coordinate from /X10 to /X510. This will move the faceplate to the
right. Leave parameter 4 as is.

Click OK.

Rockwell Automation | 2020 61 of 132

Using the same steps as above, for the TK400 level indicator and trend objects change the parameter 3 for the
faceplates to /X1200. For the discharge pump PMP402, change the parameter 3 coordinate to /X960.

Click on the Save button to save the updates to the display.

Minimize the FactoryTalk View Studio window.

Rockwell Automation | 2020 62 of 132

Testing the New TK400 Pump and Level Routines and HMI Display

Switch back to the FactoryTalk View Client window.

Click on the “TK100 / TK200” button on the button bar of the client.

Click on the “TK300 / TK400” button. This refreshes the client screen with the display updates.

Click on the TK400 fill-pump PMP401 and click the start button to fill the tank.

Rockwell Automation | 2020 63 of 132

Click on the discharge pump, PMP402, still labeled MT101 from the copy, and if needed use the faceplate to
acknowledge an IO Fault alarm.

Start the pump and verify that the tank drains.

Notice that the labels and descriptions for the TK400 pump and level objects still reflect the labels and
descriptions from the copy. In the next section of the lab, Commissioning the 5.1 Devices, you will learn how to
configure the tag descriptions and labels using the new workflow with the Process Library 5.1.

Rockwell Automation | 2020 64 of 132

Commissioning the Devices – Introducing Logix Dialog Boxes

In this section, you will configure the faceplate tag descriptions, labels, and interlock names for the new tank.
For larger applications, this configuration would be completed using Rockwell’s PlantPAx Configuration Tool. This
off-line tool is covered in the “Tools to Help Deploy and Maintain a PlantPAx DCS” lab. For small applications
(such as this lab or skid maintenance) updating the tag descriptions and labels can be done from the new Logix
Dialog Boxes for 5.10 objects.

Click on the Maintenance Tab of the PMP402 faceplate..

From the Maintenance Tab, click on the Display Advanced Properties button.

On the Advanced Properties faceplate, click on the HMI Configuration button.

Rockwell Automation | 2020 65 of 132

Notice that the faceplate labels and descriptions are still at their value from the copied routines. Also note that the
text entry boxes are grayed out for the Process Library 5.10 objects. Changing the faceplate labels and descriptions
must be done using Studio 5000 Logix Designer Dialog Boxes or as bulk changes using the PlantPAx Configuration
Tool for Tags, Alarms, and Historian.

Switch to the Logix Designer window by clicking Alt+Tab on the keyboard.

Note that keyboard Alt+Tab does not work when using OnCourse. Instead, if using OnCourse, to switch
application windows use the drop-down Action/Send Keys options at the center top of the screen as shown in
the screen capture below:

Rockwell Automation | 2020 66 of 132

In Studio 5000 Logix Designer, double-click on the PMP402 routine to open the editor and click the ellipsis
button on the PMP402 PMTR block.

On the General tab note the SAMA (Scientific Apparatus Makers Association) diagram and command buttons.
This tab is new for PlantPAx Instructions starting with Studio 5000 Logix Designer v33. No need to create a
device object and faceplate in a display to test the interlock code.

Click on the Command Source tab. This tab is new for the 5.10 library.
Note the mode buttons. No need to create a device object and faceplate in a display to test the mode logic.

Click on the Advanced tab. This tab is new for the 5.10 library for motor configuration.

Rockwell Automation | 2020 67 of 132

Click on the HMI tab. This tab is new for the 5.10 library.
Change the Display Label to PMP402.

Expand the HMI tab.

Click on the Command configuration in the HMI tab. This tab is new for the 5.10 library.

Click on the Alarms tab. This tab is new for the 5.10 library.
Click on the ellipsis button to the right of the Fail To Start alarm to open the alarm’s Properties window.

This workflow is new for the 5.10 library. All alarm configurations are now in Logix Designer.
Close the Alarm Properties window.

Rockwell Automation | 2020 68 of 132

Click on the Parameters Tab. The parameters tab is like the parameters tab for the Process Library version 4.10
Add-On Instructions (AOIs). Note the “*” next to the HMI tab. This indicates that the tab has edits that have not
been saved.

Click on the Tag tab. The Tag tab is like the Tag tab for 4.1 library blocks.
This workflow is new for the 5.10 library. The tag name and description can now be configured in Logix.

Change the Description to Discharge Pump as shown below:

Click OK.

Rockwell Automation | 2020 69 of 132

Double-click on the LI400 routine to open the editor and click the ellipsis button on the LI400 PAI block

On the General tab note the SAMA diagram and limit entry fields. This tab is new for the 5.1 library.

Click on the HMI tab. This tab is new for the 5.1 library. Change the Display Label from LI100 to LI400.

Click on the Alarms tab. This tab is new for the 5.1 library. Note the alarm limits for the Low and Low Low
alarms. These are the limits that caused the alarms when you emptied the tanks. These alarm limits can also be
configured in Logix or on the Alarms tab of the faceplate for both the 4.1 and 5.1 libraries.

Click OK to save the HMI changes.

Rockwell Automation | 2020 70 of 132

Configuring an Interlock

When the tank completely emptied the discharge pump continued to run. In the real world this could lead to
damage to the pump. You need to configure an interlock that will stop the pump on a empty tank level condition.
In this section you will again be making code changes online with the running controller to demonstrate how
interlock code can be added without interrupting the operations of a running plant. Note the PMP402 label and
desciption are now correct.

A routine can consist of multiple “sheets”. For the pump routine sheets 3 to 10 consist of the Interlocks
configuration for the pump. For this device you will add an interlock for a tank empty condition to trip the pump.
Click on the tab for the PMP402 routine. Use the down-arrow to select sheet 3 named “Interlock Bank 0”.

To make changes online to the interlock logic, click the Start Pending Routine Edits button.

Rockwell Automation | 2020 71 of 132

Note the online edit mode indicated by the gray box and the edit mode icons.
To begin the interlock logic, add an Input Reference object to the screen by drag-and-drop (or just click on the
Input Reference object and one will appear in the editor window).

Double-click on the input reference and type LI400.Inp_PVData or click on the down-arrow to open the drop-
down tag browser and select LI400.Inp_PVData.

The connector should look as below.

Rockwell Automation | 2020 72 of 132

You need to add a block that compares the value of the level, LI400.Inp_PVData, to a fixed value. To do this you
will use a “Less Than” compare block (LES).

The function blocks (or Elements) can be accessed from the Element banner. The blocks are grouped together by
functions (Add-On, Process, Drives, Filters ….). The LES block is in the Compare Element group.
Click on the Compare tab. This tab contains all the blocks that have compare functions.

Click on the LES function block to drop it on the sheet.

Rockwell Automation | 2020 73 of 132

Note that the PlantPAx 5.10 process blocks (in firmware) are listed in the PlantPAx Element Group tab. The Add-
On tab is the library 4.1 blocks as AOIs. The AOIs can be modified (unlike the firmware based 5.10 blocks) but
the AOIs take more memory space in the controller. The tabs for the other Element Groups have instructions that
are in firmware that can be used to develop control strategies. Use the slider arrows to browse the element
banner selections.

Drop one more input reference onto the sheet.

Change the connector to value of 1. If the tank level drops below 1% we will consider it empty and interlock the
pump.

Rockwell Automation | 2020 74 of 132

Connect the output pin from the connector LI400.Inp_PVData to the input pin Source A of the LES block.

Next, connect the output pin from the connector value 1 to the input pin Source B of the LES block.
Finally, connect the LES block output pin to the Inp_Intlk00 input on the P_Intlk object.

Because the interlock was configured independent of any alarm condition, the alarms, overrides, disables, or
shelving of the alarms do not affect the action of the interlock.

Verify the routine.

Confirm there no errors.

Rockwell Automation | 2020 75 of 132

Click the Finalize All Edits In Program button.

Click Yes to confirm the online edits.

Note the green border that indicates you are no longer in edit mode and are online. The LI400 input value is 0.0.
This indicates the TK400 is empty. Notice that the interlock is active (the output from the LES block is a 1).

The interlock is now added to the code, you still need to commission the interlock faceplate.

Rockwell Automation | 2020 76 of 132

For PlantPAx instructions you will use the properties of the PINTLK instruction to accomplish this. Click on the
ellipsis button on the PINTLK block.

The General tab of the Properties Dialog Box shows the status of all the interlocks. Notice that Interlock 0 is Not
Ok because the tank is empty, and the interlock is active from the new code you added.

Click on the Advanced tab. Name the new interlock “Tank Empty”.

Expand the HMI tab and click on Type. Note the types for the interlocks. This is new in the 5.1 library.

Rockwell Automation | 2020 77 of 132

Click on the Navigation 0-15 tab. Click the box to Allow Navigation to an interlock object, in this case the level
transmitter. This allows the operator quick access from the pump interlock faceplate to the level indication
faceplate if needed. Type in “/PlantPAx_Data_Area::[LAB]LI400” for the object tag name.

Click OK to accept all the changes.

Close the routine PMP402.

And close LI400.

Save the changes.

Rockwell Automation | 2020 78 of 132

Click Yes.

Section Summary
The new workflow in 5.1 makes it easier to configure the device from a single programming environment, Logix
Designer. For small applications (such as this lab or small engineering or maintenance projects) this configuration
work would be done from the dialog boxes but for larger project application development, this configuration could
also be completed using PlantPAx tools.

Introducing the New Alarm Manager in Logix

With the 4.1 library, the alarm tags exist in the FactoryTalk Alarms & Events server and are all being scanned
constantly, no matter if they have changed state or not. This increases the loading on these servers. The
PlantPAx 5.1 Process Object Library that is embedded in firmware uses Logix Tag Based alarms which moves
the loading from the server to the controllers (thus decreasing server-side loading). By using Logix Tag Based
alarms, the 5.1 library alarms communicate more efficiently, reporting by exception rather than by scheduled
polling. For large systems with many alarms this can result in dramatic reductions in data traffic, freeing up
bandwidth for new data or reducing the number of required servers for a system. Large applications could see the
need for redundant data servers cut by 50% using the new communications method.

Click on the Controller Organizer. Double-click on the Alarm Definitions within the Alarm Manager.

Rockwell Automation | 2020 79 of 132

The “Alarm Manager Definitions” provides a single place to configure the alarms definitions for each Library 5.1
block. With the new Logix Tag Based Alarming, alarms can now be defined on tags in the controller with periodic
evaluation. Benefits include: no need to add an instruction, simplified design workflows inside Studio 5000 Logix
Designer, no additional programming required – alarms are automatically sent to FactoryTalk Alarms and Events,
and the new alarm manager definitions provide a single place to configure them.

Click on the Alarms in the Alarm Manager.

When the 5.1 blocks are added in code, the Logix Tag Based alarms are automatically generated in the Alarms list.
No additional programming is required. The alarms are automatically sent to FactoryTalk Alarms and Events. Later
in the lab you will enable the Linx data server in Studio to support the 5.1 Logix Tag Based Alarms in the controller.

Rockwell Automation | 2020 80 of 132

Close both alarm tabs.

Minimize the Logix Designer window.

Testing the Interlock

Return to the Client window

The Client screen should still have the TK400 discharge pump faceplate open as shown below. Notice that the
PMP401 discharge pump is now stopped and is indicating an interlock condition.

Close the maintenance faceplate.

Rockwell Automation | 2020 81 of 132

Click on the Diagnostics tab.

Note the diagnostics tab includes a list of reasons that the device is not ready. Notice that an interlock is not the
only reason for a device to be not ready. This is the first line of trouble shooting for the operator. Click the Device
Reset button to reset the interlock alarm. Close the faceplate.

Note on the LI400 faceplate that the double-down arrows indicate a low-low alarm condition. Flashing
indicates the alarm is active and not yet acknowledged. Click on the level indicator to open the faceplate, then
click the Alarms tab.

Rockwell Automation | 2020 82 of 132

Click on the Low Alarm indication.

Click the button to Acknowledge the Low alarm. Notice the Low alarm stops flashing. Close the Low alarm
faceplate.

Click the Acknowledge and Reset Button to acknowledge and reset both alarms.

The Logix Tag Based Alarms, active on the faceplates, also show up on the alarm banner and on the alarm
summary. Tag Based alarms need only minor configuration to enable. Note that the active alarms show on the
device faceplates, and they also show up on the Alarm banner at the top of screen. It is because the data and
alarm servers are pre-configured in the lab.

Rockwell Automation | 2020 83 of 132

Introducing the Logix Tag Based Alarms

For PlantPAx 5.10 configuring alarms in the alarm server and on the alarm displays has been made much easier
with new Tag Based alarms. With the 4.1 library the alarm tags are all being scanned constantly, no matter if
they've changed state or not. With the 5.10 library having the alarms in the controller (tag based) means that the
alarm tag is only sent to the data server when something changes. For large systems with many alarms, you are
eliminating a lot of tags on scan. Logix Tag Based alarms help decrease server loading.

Maximize the FactoryTalk View Studio window.

In this section of the lab, you will configure the Logix Tag Based alarms in Studio for use with the FactoryTalk
Alarm server. The FactoryTalk View Studio window should still look like below.

Enabling the Logix Tag Based Alarms

There are two places in Studio that you need to configure to enable the 5.1 Tag Based alarms. The first place is in
the FTLinx Server Properties. In the Explorer window, scroll up to the PlantPAx_Data_Area. In the
PlantPAx_Data_Area, right-click the FactoryTalk Linx server and Select Properties.

Rockwell Automation | 2020 84 of 132

On the Server Properties window, click on the Alarm and Events tab. Notice that the box is checked to
Enable alarm and event support. The Logix Tag Based alarms are automatically sent to FactoryTalk Alarms
and Events from the controller’s Alarm Manager. Note, checking the box enables the Linx data server to support
them.

The second configuration to enable the alarms is in the Linx data server Communication Setup. In the
PlantPAx_Data_Area and the FactoryTalk Linx folder, double-click the Communication Setup.

Note the check boxes for the Extended Tag Properties. These are used for the library 5.10 Logix Dialog Boxes.
Extended Tag Properties have been available since v31 of Logix Designer. For library 5.10 they have been
expanded to allow process device control and reduce the need for string tags and allow for language translation.

Rockwell Automation | 2020 85 of 132

This is the second place you need to configure the server for the Tag Based Alarms by subscribing to “All Alarms
& Events Notification Messages” from the controller PAx. Because Logix Tag Based alarm and event support was
enabled in the Linx data server, the data server can subscribe to Alarm & Events Notification Messages from
controllers.

Close the Communication Setup window.

Summary
For the new Logix Tag Based alarms, there are two places in FactoryTalk View Studio that you need to configure.
The first place is in the FactoryTalk Linx Server Properties, and the second place is the Alarms and Events
settings for the device shortcut. To view the alarms on the operator client screen, add the new Tag Based alarm
banner to the HMI application framework.

Rockwell Automation | 2020 86 of 132

Configuring the Alarm Banner and Alarm Summary Displays

Notice that the “(LAB) p2f storage tanks 3_4” display does not include the alarm banner at the top as part of the
display.

Note when the Client first opens it runs a macro, named “Area1000_Start”. The macro first displays the header
at the top of the client window and then the Storage Tanks screen is displayed below the header.
Each client file on the desktop runs a dedicated macro to display its area specific header including alarm banner
and area specific displays including button bars.
Example of the macro:

The alarm banner is part of a customized header display named “A1000_Slurry Header_1mon”. This is a header
display designed for a single monitor (_1mon) per Client hardware configuration and configured for the area.

Rockwell Automation | 2020 87 of 132

Expand the “Area 1000 Slurry” displays folder and click to open the “a1000_slurry header_1mon” display.

Scroll to the right and Right-click the Alarm and Events Banner in the “a1000_slurry header_1mon” display
and select Properties.

Click on the Event Subscription tab. Note that the default scope is “(Any Scope)”. This banner will show all
active Logix Tag Based alarms in the data server (all controllers with a path set in FT Linx) and all 4.1 FactoryTalk
Alarms and Events (FTAE) alarms with no filtering by controller (5.1) or area (4.1). Click the Browse button to
select a specific Alarms and Events server and area. This feature allows operators in different plant areas to
concentrate on only alarms important to them.

Rockwell Automation | 2020 88 of 132

Expand the PlantPAx folder, expand the PlantPAx_Data_Area folder, and click on FactoryTalk Linx.

Click OK.

You have now selected the specific Alarm and Events Server associated with this HMI server. Verify the scope is
as shown below.

Click OK again.

Click Save to save the changes to the header banner display.

Rockwell Automation | 2020 89 of 132

Note, following the same configuration workflow as for the alarm banner above, Alarm Summary displays, can be
configured with a specific alarm scope.

Testing the Tag Based Alarms in the Alarm Banner

To test the Alarm Banner, Maximize the FactoryTalk View Client window by clicking on the client icon at the
bottom.

Notice the Tag Based alarms appear in the alarm banner.

Open the TK400 fill pump PMP401 faceplate and start the pump.

Rockwell Automation | 2020 90 of 132

Notice that the fill pump PMP401 is stopped by the interlock when the fill level was reached.

Note that the PMP401 alarm for the interlock did not show up in the banner. The fill pump is configured with 4.1
objects and therefore does not use the new Tag Based alarms.

For 4.1 library alarms the alarms must be configured in the FTAE Alarm Server.

Configuring FTAE Server-based Alarms for 4.1 Library (information only)

Note that this lab does not cover the configuration of the server based alarms other than to provide a short
overview with sample screens. For more details on configuring the alarms for the 4.1 process object library in
FT View Studio, reference the PlantPAx documentation.

For larger applications 4.1 alarm configuration would be completed using Rockwell’s PlantPAx Configuration Tool
for Alarms, Tags, and Historian. The tool is used to generate the alarm import file for the 4.1 Library objects used
in the controller. This tool allows bulk configuration of FTAE alarm for large process projects using Library
versions 4.1 and below. (Refer to publication PROCES-RM002 for more information on the tools.)

For the 4.1 library, the server-based alarms are configured in the FTAE Alarm Server in FT View Studio.

Note - the following two pages are for 4.1 alarms configuration and are for information only.

For the 4.1 library, the server-based alarms are configured in the FTAE Tag Based Alarm Server using the
Alarm and Event Setup (whereas the new 5.1 Logix Tag Based alarming is configured in each controller and on
the associated data servers).
Example:

Rockwell Automation | 2020 91 of 132

Note the alarms shown in the example below were created off--line using the PlantPAx Configuration Tool for
Alarms, Tags, and Historian to generate an alarm import file for the 4.1 Library objects used in the controller. In
the Alarm and Event Setup window for the FTAE alarms, we can create alarm groups and group alarms by
process areas. In the example below, an alarm group for Tank1 and a group for Tank2 has been added.
Example:

Note that the Alarm Summary and the Alarm Banner displays also need to have the “scope” modified to include
the Server Tagbased FTAE alarms. In the lab you modified the scope of the Alarm Summary and Alarm Banner to
include the Logix Tag Based alarms. To also show the 4.1 alarms on the banner the scope must include the
FTAE alarm server in the scope.
Example only:

Section Summary

Rockwell Automation | 2020 92 of 132

For PlantPAx, configuring alarms in the data server and on the alarm displays has been made much easier with
new Logix Tag Based alarms.

The 4.1 library server alarms are compatible with the Logix Tag Based alarms but require more development time
to generate the alarms (using the PlantPAx Configuration Tool for Alarms, Tags, and Historian) and more effort to
configure the server.
In the final section of this lab, you will use the 5.1 workflows learned in the lab to configure a PIDE control loop
and a variable speed pump, which can be used for controlling pressure, flow, or level in most process
applications.

Rockwell Automation | 2020 93 of 132

Configuring a Pressure Control Loop and Variable Speed Pump

In this section of the lab, you will configure a pressure control loop with a remote set point to a variable speed
pump. Why is this important? The pump added in the previous lab section was a simple start/ stop pump. The
pump you will add now is a variable speed. Variable speed pumps are used for flow, pressure, and level control in
process applications. The speed set point for the pump will be from a PID pressure controller. The PID controller
uses industry standard Proportional, Integral and Derivative algorithms to control the process variable. The control
strategies for the variable speed pump and the pressure control loop are included in the process library as sample
code.

Maximize the Logix Designer window.

Verify that you are still on-line, the controller running, and select the Logical Organizer tab.

In this section, you will import a pre-configured Control Strategy routine for a variable speed pump (PVSD) to the
TK300 program. Right-click on the program named TK300. From the menus select Add and then Import
Routine.

Rockwell Automation | 2020 94 of 132

From the library CS_PVSD folder, Select the file (RA-LIB)CS_PVSD_5_00-03_Routine.L5X, and click Open.

Click the Find/Replace button.

Replace all X with P (for pressure) and click the Replace All button. This tag is for the cascade SP connection
to the PPID block of the pressure control loop.

Replace all 410 with 300 and click the Replace All button. This tag is for the cascade SP connection to the
PPID block of the pressure control loop.

Rockwell Automation | 2020 95 of 132

Now click OK.

Click the button to Finalize All Edits in Program and click OK.

Wait for the import to complete.

Next, you will import a pre-configured Control Strategy routine for a PPID (Proportional Integral Derivative)
pressure controller. Right-click on the program named TK300. From the menus select Add and then Import
Routine.

From the library CS_PPID folder Select the file (RA-LIB)CS_PPID_5_00-03_Routine.L5X, and click Open.

Rockwell Automation | 2020 96 of 132

Click the Find/Replace button.

Replace all X with P. This tag is for the cascade SP connection to the PVSD block of the drive loop.

Replace all 520 with 300.

Click OK.

Click the button to Finalize All Edits In Program and click OK.

Wait for the import to complete.

Note the new routines MT300 and PIC300 (PIC for pressure indicating controller) need to have JSRs added to
the MainRoutine to execute them.

Rockwell Automation | 2020 97 of 132

In the TK300 routine, double-click the MainRoutine to open it.

Next you need to add “Jump to Subroutine” (JSR) instructions to execute the new routines. Copy and paste an
existing rung to create two new rungs with JSRs for routines MT300 and PIC300.

The rungs should look like below.

Click the button to Finalize All Edits In Program.

Click on Yes.

Rockwell Automation | 2020 98 of 132

Verify no errors.

Close the tab for the MainRoutine.

Double-click on the new routine PIC300.

Scroll over to display the both the PAI and PPID block in the function block editing window. The PAI block is the
analog input block for scaling and alarming. The PPID block is the PIDE controller and uses industry standard
Proportional, Integral and Derivative algorithms to control the process variable, pressure in this case.

Click on the PPID ellipsis button.

Rockwell Automation | 2020 99 of 132

Expand the General tab of the PPID properties window. The PPID can be configured, tested, and tuned from the
Dialog Box. Click on the SP tab. Note the setpoint limits are 0 to 1000 psig and the value of the setpoint is 0.0.

Click OK.

Save the changes.

Click Yes.

Minimize the Logix Designer window.

Using the same steps, you learned earlier in the lab, you will configure the storage tanks display with a PVSD and
a PPID 5.1 library objects. Configuring the parameters of these objects, you will connect these objects to the
PVSD and PPID tags created in the controller code in the previous section.

Rockwell Automation | 2020 100 of 132

Switch to the FactoryTalk View Studio window.

For rapid development of information-rich operator displays, the Rockwell Automation Library of Process Objects
provides a collection of Global Objects that are linked to the Add-On Instructions with a drag and drop wizard.
Display elements include motors, valves, analog and digital indicators and even a sequencer. Together with the
HMI Project Templates they allow for rapid development of display graphics.

In FactoryTalk View Studio, scroll down in the Global Objects folder and Double-click on the 5.1 Global Object
named “(raP-5-SE) Graphic Symbols - PVSD”. Note that all Global Object display names prefixed with “(raP-5-
SE)” are for the Process Library 5.1. All Global Object display names prefixed with “(RA-BAS)” are for the Process
Library 4.1.

Each device object is preconfigured in various orientations and with optional features. The motors are displayed
configured as pumps, conveyors, blowers, agitators, fans, and inline motors.

Drag-and-Drop a Pump object from the Global Objects display to the storage tanks graphic.

Rockwell Automation | 2020 101 of 132

In the Global Objects folder and double-click on the 5.1 Global Object named “(raP-5-SE) Graphic Symbols –
PPID”.

Drag-and-Drop a PPID object from the Global Objects display to the storage tanks graphic.

The display should look like below.

Right-click on the variable speed pump object.

Rockwell Automation | 2020 102 of 132

Select Global Object Parameter Values from the selection menu.

Click the ellipsis button for parameter 1.

Click the Refresh All Folders button.

Select the MT300 tag and click OK.

Rockwell Automation | 2020 103 of 132

Verify that parameter 1 matches below and change parameter 2 to /X1430 and parameter 3 to /Y200.

Click OK.

Right-click on the PPID pressure controller object.

And select Global Object Parameter Values from the selection menu.

Rockwell Automation | 2020 104 of 132

Click the ellipsis button for parameter 1.

Scroll to and Select the PIC300 tag and click OK.

Change parameter 2 to /X1430 and parameter 3 to /Y560.

Click OK.

Save the changes.

To test the code and graphic for the pressure control and VSD, Maximize the FactoryTalk View Client window
by clicking on the client icon at the bottom.

Rockwell Automation | 2020 105 of 132

Click on the “TK100 / TK200” button on the button bar of the client.

Click on the “TK300 / TK400” button. This refreshes the client screen with the display updates.

Click on the new pump and click the new pressure controller objects to open the faceplates.

Notice that the MT300 variable speed pump is not running and is in operator mode. Click the Start button.

Rockwell Automation | 2020 106 of 132

Verify that the motor starts. Notice that the PIC300 control loop indicates that the “Inner loop is not available for
Auto/Cascade”. This is because MT300 is in Operator mode and needs to be in program mode to be available for
the remote set point. Note, the flag indicates to the operator that the loop “is not in its normal mode”.

Click on the Command Source button on the MT300 faceplate. Then on the small Command Source
faceplate, click the Request Program Control button.

MT300 is in program mode and is getting a remote setpoint from the PIC300 pressure controller. Close the
Command Source faceplate.

Rockwell Automation | 2020 107 of 132

Notice that the PIC300 pressure controller is in manual mode. Click on the SP (setpoint) input box for the PIC300
pressure controller. Enter a value of 100 for the setpoint and click OK.

The CV (controlled variable) is the remote setpoint to the variable speed pump. Note the CV on the pressure loop
PIC300 did not change with the SP setpoint change because the loop is in manual mode. Click the button to put
the PID in Auto Mode.

The speed of the pump controls the pressure, the process variable (PV). In auto mode, given time the controller
will match the PV to the SP. Notice the PPID device state “PV Deviation not in deadband” message. You will now
configure the PV deviation from SP deadband limits from the client faceplate. Click on the Maintenance tab of
the PIC300 faceplate.

Rockwell Automation | 2020 108 of 132

Then click the Display Advanced Properties button.

Click on the Maintenance tab of the Advanced Properties faceplate.

Click on sheet 3 of the Maintenance tab.

Click on the Leave DB (deadband) input box for the PV to SP leave error and enter 1. Click OK.

Rockwell Automation | 2020 109 of 132

Click on the Enter DB input box for the PV to SP Enter error and set the value to 1. Click OK. Now when the PV
is within 1 psig of entering or leaving the SP, the warning will disappear.

Close the PIC300 Advanced Properties faceplate

Return to the Operator Tab and notice that the deviation is in the deadband now.

Section Summary
You have successfully configured a pressure control loop to regulate the speed of a variable speed drive.
With PlantPAx engineering your modern DCS has never been easier.

Rockwell Automation | 2020 110 of 132

Configuring Highly Integrated HART in the Process Controller

Adding or replacing HART devices, even online, is made simple with fully integrated HART faceplates and device
diagnostics. From the Process Library 5.1 faceplates that render HART content automatically to the Integrated
device diagnostics profiles, adding a HART device is simple and Intuitive.

In this section we will be working primarily in Studio 5000 Logix Designer.

Switch to or maximize the Logix Designer window.

The first thing that we will need to do is create an Ethernet adapter module to communicate with a remote rack.
Within that rack we will need to add a HART I/O card capable of HIH.

In the Controller Organizer window, scroll down to I/O Configuration.

Right click on the Ethernet backplane and select “New Module”.

Rockwell Automation | 2020 111 of 132

In the Filter box, type 5094 and select the 5094-AENTR device to add to the I/O tree. Click Create

Configure the device as shown below. Do not click OK.

Rockwell Automation | 2020 112 of 132

To avoid interfering with any of our remote lab equipment, navigate to the Connection tab and select the check
box to Inhibit Module.
Click OK and close the Select Module Type window.

Now we will add the 5094-IF8IH Module. Right click on the 5094 Backplane in the I/O Configuration Tree and
select New Module.

Rockwell Automation | 2020 113 of 132

In the filter box, type IF8IH and select the 5094-IF8IH device to add. Click Create.

On the General tab, configure the module as shown below. Do not click OK yet.

Rockwell Automation | 2020 114 of 132

On the Ch00 tab, ensure that the Enable HART checkbox is selected. Click OK and close the window.

Click Yes to create the new module online.

Close the selection window.

Now we will add a HART device to the IO module HART backplane.

With the availability of new Add-On Profiles in Logix v33 we can choose from a selection of HART devices to add
to the HART backplane. For this lab we will be adding an E&H Promag 400 flow meter.

Rockwell Automation | 2020 115 of 132

Right click the HART backplane and select New Module.

Type “Promag 400” into the filter window and select the HART-Device-1169 Catalog Number from the list of
devices. Click Create

Rockwell Automation | 2020 116 of 132

Name in device on the General tab as shown below. Note that this device is on Channel 0, which is the HART
enabled channel that we examined earlier. Do not click OK yet.

Click Change in the Module Definition box

One of the great new features is the ability to create a HART device using PlantPAx Data types that can be easily
connected to the embedded firmware objects.

Rockwell Automation | 2020 117 of 132

In the Connection drop down menu, select PlantPAx Data.

Click OK to close the Module Definition dialog box.

Click Yes on the prompt to apply the changes.
Click OK to exit the New Module dialog box.
Click Yes to create the new module online.

Close the select window.

The Promag 400 flow meter will now be available in the I/O tree.

Rockwell Automation | 2020 118 of 132

Now that we have our HART device configured in our I/O Tree, let us create a routine to use the new device.
Scroll up in the Controller Organizer to the Shared_Resources program under the Normal (250 ms) task.
Right click the Shared_Resources program and select to Add an Import Routine.

As with previous releases of the PlantPAx Library of Process Objects, Rockwell Automation will release a set of
pre-configured 5.1 Control Strategies for download to be used with Studio 5000 Logix Designer or Application
Code Manager (ACM).
From the library CS_PAI_HART folder, select the “(RA-LIB)CS_PAI_HART_5_00-03_Routine.L5X” control
strategy to import. Click Open.

Rockwell Automation | 2020 119 of 132

Click on Tags in the Import Content tree, then click the Find/Replace button at the top of the dialog box.
Type XT100 in the “Find What:” box and type FI301 in the “Replace With:” box.
Click Replace All.
Notice that the tag names have been updated in the Final Name field. Click OK.

Click the button to Finalize All Edits in Program and click OK.

Wait for the import to complete.

Rockwell Automation | 2020 120 of 132

Open the newly created FI301 routine. This is the new PAH HART device object. We will use the ProMag400
device that we created earlier to populate this tag.

Click Start Pending Routine Edits at the top left corner of the sheet.

Double click the “Select_HART_Device” tag in the Ref_HARTData parameter of the instruction. Replace it with
the Tanks_OutFlow:I.PAxDevice Promag device tag that we created earlier as shown below.

Rockwell Automation | 2020 121 of 132

Click to Finalize All Edits in Program. Click Yes on the popup.

Note since there is no physical HART device connected to this lab controller, we will have to manually edit the
Raw and EU min and max values for this device. We will manually enter the Raw and EU min/max values.

Right click the Tanks_OutFlow:I.PAxDevice tag and select Monitor “Tanks_OutFlow:I.PAxDevice”.

Expand the tag and enter the values as shown below. You will have to expand
Tanks_OutFlow:I.PAxDevice.Static in order to access the PVAtSignal4 and PVAtSignal20 values.

Close the Controller Tags tab and Open the MainRoutine for Shared_Resources and add a JSR for the
newly created routine.

Rockwell Automation | 2020 122 of 132

This can be done by copying and pasting one of the other JSR rungs and changing the Routine Name to FI301.

Click to Finalize All Edits in Program. Click Yes on the popup.

Save the ACD file.

Minimize the Logix Designer window.

Highly Integrated HART built-in HMI graphics

Now that we have configured our HART device and downloaded our controller code, we will configure an HMI
object to visualize the flow data.

Switch to the FactoryTalk View Studio window.

Open the “(LAB) p2f Storage Tanks 1_2” display.

Rockwell Automation | 2020 123 of 132

Now we need to add a new PAI Global Object to our display. Expand the Global Objects tree and open “(raP-5-
SE) Graphic Symbols – PAI”.

Copy the Generic Analog Input global object with no graphical indication of the PV (top left object).

Rockwell Automation | 2020 124 of 132

Paste the object onto the Storage Tanks display.

Use the zoom out button to see the complete graphic.

Move the object adjacent to the shared outlet valve as shown below.

Rockwell Automation | 2020 125 of 132

Right Click the object and select Global Object Parameter Values

Click the ellipsis next to the Object Tag field.

Refresh the folders and select the FI301 tag by navigating to PlantPAx_Data_Area > LAB > Online. Click OK.

Rockwell Automation | 2020 126 of 132

Enter /RP to have the faceplate launch in the Relative Position of where the object is clicked into the field for
parameter #120 and click OK.

Save the “(LAB) p2f storage tanks 1_2” display.

Now let us launch the HMI client and see the power of the PlantPAx library. Maximize the FactoryTalk View
Client window by clicking on the client icon at the bottom.

Click TK100 / TK200 to navigate to the display and click the new FI301 object that we created earlier.

Click the FI301 Object to launch the faceplate.

Rockwell Automation | 2020 127 of 132

 Navigate to the Maintenance tab, then click the button to display the Smart Device faceplate.

The Smart Device faceplate for FI301_Dvc is automatically connected to the HART device we configured in the
controller earlier. From this faceplate you can view a wide variety of data and configurations straight from your
HART device.

Note that there will be a Signal Failure error since we do not have an actual device connected in this lab.

Feel free to explore the various tabs and advanced menus.

• Operator Tab

Rockwell Automation | 2020 128 of 132

• Maintenance Tab

• Maintenance – Advanced Properties

o Engineering Tab

Rockwell Automation | 2020 129 of 132

o HMI Configuration Tab – Page 1

o HMI Configuration Tab – Page 2

Close all the faceplates.

This concludes the Highly Integrated HART section of this lab.

Rockwell Automation | 2020 130 of 132

Ownership & Arbitration – Information Only section

The new Organization / Ownership / Arbitration functionality added in to the 5.0 release of PlantPAx gives the
user a new ability to organize their operations. These three controller-based functions are separate but are built
on or dependent on the same backbone. The new feature allows you to create organizational trees of related
devices directly from the HMI and manage and prioritize device ownership within these trees. The faceplates
allow an operator to get statuses and issue commands to equipment groups from a single request.

Organization:
Organization is a method by which parent / child relationships can be created and modified among control
objects. Organization provides a method to propagate a selected subset of commands (related to command
source, alarms, etc.) from the parent down to its children or propagate the aggregate of a selected subset of
status (related to command source, alarms, etc.) from the children up to the parent.

Organizational views can be many nodes deep and wide, and numerous organizational views can reference the
same devices to suit the needs of the user. The structure and view of these organizational trees can be modified
online from the HMI. This provides the ability to coordinate commands of related equipment and view their related
status (equipment modules or phase modules), or alternatively to monitor specific equipment or equipment types
as a maintenance function.

Ownership:
Ownership is built on the Organization backbone and is applicable to the control of phase modules or equipment
modules. The ownership function leverages the built-in class arbitration of the Owner object (Operator, Program,
External and Maintenance) to select the prioritized Command Source state (in the case where there is more than
one class of concurrent requests for ownership). Each request for ownership passes its unique Identification
number (ID) to the prospective Owner object. Once successfully processed, the owner/parent will attempt to own
and place all its control device children into Program state and accept the Owner’s ID. Once the parent and all the
children are organized (ID accepted, in proper CmdSrc state & ready), the related equipment is considered
“Owned and Organized”.

Ownership does not execute any logic itself but can provide status indicating that it is “Owned and Organized” to
external logic that can then execute its logic on that same equipment.

Arbitration:
Arbitration of shared resources optionally has two levels. The built-in Command Source forms the basis of
Ownership and arbitrates the “class requests” for ownership. That is, who has priority – Program, Operator,
External or Maintenance class?

Rockwell Automation | 2020 131 of 132

In addition, the Ownership function will perform a FIFO arbitration when concurrent requests from a single
command source class are made (this functionality is built-in). More nuanced arbitration can be accomplished by
configuring and installing an arbitrate control object for the shared device.

Due to time constraints in this lab, we will not be configuring the device organization within your controller
project, but the device organization model is the basis for all other device ownership, arbitration, and group
control within your application.

Lab Summary

PlantPAx™ is the process automation system from Rockwell Automation with all the core capabilities expected in
a world-class modern distributed control system. The Rockwell Automation Library of Process Objects™ is a
collection of Application Templates, Application Code, Graphic Objects, Faceplates and Process Control
Strategies that let you quickly configure a device from I/O to operator.

PlantPAx is focused on solutions for productivity gains in multiple areas of the plant, using a more simplified
approach to control system strategies. In the 5.0 release, Rockwell Automation introduces new process
controllers that help to improve scalability and skid integration, as well as provide a more simplified, lower-cost
architecture due to higher controller performance. Embedded native process objects help to reduce engineering
costs and drive more consistency in projects. New cybersecurity capabilities and system certifications help to
ensure safer and more secure operations.

Rockwell Automation | 2020 132 of 132