PlantPAx Engineering Using Process Libraries
PlantPAx Engineering Using Process Libraries
development
Expanding human possibility
through learning
Lab Book
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. This 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, operate and maintain the Products at all
times.
• 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:
IMPORTANT
Identifies information that is critical for successful application and understanding of the product.
Labels may also be on or inside the equipment to provide specific precautions.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or
motor, to alert people that dangerous voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or
motor, to alert people that surfaces may reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor
control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or
death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory
requirements for safe work practices and for Personal Protective Equipment (PPE).
Introduction to PlantPAx
Engineering Using Process
Libraries
Table of Contents
Introduction to PlantPAx Engineering Using Process Libraries ........................................................ 1
Before You Begin ......................................................................................................................... 3
About this Lab ....................................................................................................................... 3
Duration................................................................................................................................ 4
Prerequisites ........................................................................................................................ 5
Objectives ............................................................................................................................. 5
Process Library ........................................................................................................................... 5
Rockwell Automation Process Library ..................................................................................... 5
How to download the Process Library ..................................................................................... 6
Studio 5000 Logix Designer software ......................................................................................... 6
Process Controller Project ...................................................................................................... 7
Exploring the Controller Properties ......................................................................................... 8
The PlantPAx modern distributed control system offers process control and more:
☐ Plant-wide control and optimization for dynamic, demand-driven business decisions
☐ Scalable and modular system architectures to meet your exact needs
☐ Open, secure, and information-enabled networking capabilities
☐ High availability options for controllers and software
In this lab you will do the following:
☐ Leverage Control Strategies from the Rockwell Automation Library of Process Objects 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 - Optional
☐ Configure new Ownership & Arbitration – Information only.
Duration
90 Minutes
Prerequisites
This lab uses a virtualized environment. All the software tools required for this lab are installed within
this image running on your lab host PC. The tools for PlantPAx System Release 5.20 include:
Software Version
Studio 5000 Logix Designer 35.00
FactoryTalk View SE Studio 13.00
FactoryTalk AssetCentre 12.00
FactoryTalk Historian SE 8.00
FactoryTalk Logix Echo 2.00
Rockwell Automation Library for Process 5.10
Objectives
The PlantPAx® system—a modern DCS—is a key component of The Connected Enterprise. It helps you
meet key market challenges through:
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.
Process Library
IMPORTANT
The Process Library versions are different than the PlantPAx System Releases. The current system
release is 5.20 and the library is 5.10. To simplify versioning in this lab manual you will notice
sometimes 5.x and 4.x are used.
2. Wait for the Studio 5000 Common Launcher to appear. Under the Recent Projects tab, click
the Logix Designer controller project file (.acd) named LAB.
Note: the Controller Type is 1756-L85EP which is also supported in FactoryTalk Logix Echo.
2. Now click on the PlantPAx tab.
Note: the Checkbox to Use PlantPAx Tasking Model. This is checked by default and will create
default Periodic Tasks in your Controller Organizer.
☐ Fast (100 ms) For control fast loops, such as liquid flow or pressure with related
transmitters and pump drives.
☐ Normal (250 ms) For discrete control, such as motors, pumps, and valves.
☐ Slow (500 ms) For level, temperature, analysis loops, phases, and batch sequencing.
☐ System (1000 ms) For slow change temperature control and general controller operations,
such as messaging or status.
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: in this lab we will be using the Normal task.
PlantPAx Instructions
PlantPAx Instructions are embedded objects for the next generation of the Process Objects. PlantPAx
instructions are available when using one of the Process Controllers, which 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 built-in to the design pallet of Logix Designer in v35 (v33 and above).
IMPORTANT
Some of the Process Instructions from the 5.x Library are still in Add-on Instruction (AOI) format.
These instructions are obtained from the Process Library download, rather than the PlantPAx
Instruction toolbar in Logix Designer.
Instruction Usage
The Process Controller contains 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 in to 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.
1. 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.
2. Close the Instruction Usage window.
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.
In the following sections, you will add new code, including a discharge pump and a level indication, to
the program named TK300. Note an Addition Pump has already been added.
Alarm Manager
With the 4.x library, the alarm tags exist in the FactoryTalk Alarms & Events server and are all being
polled constantly, no matter if they have changed state or not. This increases the loading on these
servers. The PlantPAx 5.x 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.x 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.
The “Alarm Manager Definitions” provides a single place to configure the alarms definitions for each
Library 5.x 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.
When the 5.x Instructions are added in the project, 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.x Logix Tag Based Alarms in the controller.
In this lab section you will add Process Library v5.x Control Strategies to the program named TK300
(for tank 300) that already contains 4.x code. Later in the lab you will use the Logical Organizer
window to quickly copy TK300 to a TK400 program.
1. Expand the program named TK300 in the Normal Task to view the existing routines.
Each Controller Program contains a main routine. The main routine is the only routine that will
execute by default. It typically contains Jump-to-subroutine (JSR) instructions to execute the
other routines in the program.
Also notice the existing Addition_Pump routine. This is a routine implemented using the
Process Library 4.x objects.
IMPORTANT
From an Operator’s viewpoint, the 4.x and 5.x graphical objects and faceplates have the same look
and feel on an HMI screen.
3. Double-click on the Addition_Pump routine. Note the instruction is a P_Motor type with a
tag name of PMP301. The prefix “P_” (for process) indicates that the block is a 4.x library
object. The corresponding motor block in the 5.x library is named PMTR with the prefix “P” for
process. In the editing window click the PMP301 P_Motor block’s ellipsis button.
Note that this is a library 4.x 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.x library
much of the engineering workflow and configuration (configure alarms, set points, interlocks, tag
descriptions) is done from the Client faceplates.
PlantPAx Instructions (in firmware) contain new Dialog Boxes consisting of up to 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.
A simulation routine has also already been added. In the lab this simulation code will allow the lab
student to test their new device code (without having actual IO devices). Double-click on the routine
named Simulation. Notice the final output from this simulation logic (scroll over to the right as
needed) is an output connector LI300_Inp_PV. This output will be the simulated input value for the
tank level indicator routine that will be added later.
The control strategies are routines or programs that you import into your controller project allowing
users to reuse logic and save development time. The control strategies are built using Function Block
Diagrams or Ladder Diagrams that include pre-configured process instructions and contain
preconfigured arrays and tags.
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.
Quicky browse the following table of over 40 control strategies included in the 5.10 library.
(note that this list does not include the HART capable versions of the strategies)
Process Boolean Logic Use the PBL control strategy to process as many as four digital inputs by
CS_PBL
(PBL) applying as many as eight gates of configurable logic.
The Process Discrete 2-, 3-, 4-state Device Add-On Instruction controls and
Process Discrete 2-, 3-, or
monitors feedback (using up to four discrete outputs and up to four discrete
CS_PD4SD 4-State Device
feedbacks) from a discrete 2-state, 3-state, or 4-state device in various
(PD4SD)
modes while monitoring for fault conditions.
Process Deadband Use the PDBC control strategy to maintain a PV within a deadband of the SP
CS_PDBC
Controller (PDBC) by triggering one or two digital outputs (a raise output and a lower output).
Use the PDI control strategy to monitor a discrete (true or false) input and
CS_PDI Process Discrete Input (PDI)
check for alarm conditions.
Process Dosing Flow Meter Use the PDOSEFM control strategy to control an ingredient addition that uses
CS_PDOSEFM
(PDOSEFM) a flow meter to measure the quantity of ingredient added.
Process Dosing Weigh Use the PDOSEWS control strategy to control an ingredient addition that
CS_PDOSEWS
Scale (PDOSEWS) uses a weigh scale to measure the quantity of ingredient added.
Process Analog Fanout Use a PFO control strategy to send (fanout) one primary analog output signal
CS_PFO
(PFO) to up to 8 secondary users or devices.
Process High or Low Use a PHLS control strategy to select the highest or the lowest of as many as
CS_PHLS
Selector (PHLS) six incoming controlled variables (CVs).
Process Lead Lag Standby Use a PLLS control strategy to control of a parallel group of motors, such as a
CS_PLLS
(PLLS) set of pumps with a common intake source and discharge destination.
Process Proportional + Cascade control is defined as when an outer (primary) control loop’s output
CS_PPID_CASC Integral + Derivative (PPID) (CV) is used as a setpoint (SP) to an inner (secondary) control loop.
with Cascade
Process Proportional + Use the PPID Feedforward control strategy when feedback control (PPID
CS_PPID_FF Integral + Derivative (PPID) control strategy) alone is not adequate to maintain the process variable at
Feedforward the setpoint.
Process Proportional + The PPID Override control strategy selectively chooses the output of up to six
CS_PPID_OVERRIDE Integral + Derivative (PPID) PPID controllers based on configuration (High Select or Low Select) to drive
Override an analog output device.
Process Proportional + This strategy provides the capability to pulse outputs (pulse open and pulse
Integral + Derivative (PPID) close) to position a valve to the reference signal provided by the PPID CV.
CS_PPID_PAO
Basic PPID with Process
Analog Output (PAO)
Process Proportional + Use the PPID Ratio control strategy to add a material in a set proportion to
CS_PPID_RATIO Integral + Derivative (PPID) another material.
Ratio
This PPID Split Range control strategy as provided, manipulates two field
Process Proportional +
devices to maintain one process variable (PV) at setpoint (SP). You can
CS_PPID_SPLITRANGE Integral + Derivative (PPID)
modify this strategy to manipulate up to eight field devices in one Split
Split Range
Range PPID control strategy.
Process Proportional + Use the PPID with VSD control strategy to control a variable speed motor
Integral + Derivative (PPID) using an AC
CS_PPID_PVSD
with Process Variable (variable frequency) or DC drive with a set proportion to another variable.
Speed Drive (PVSD)
The Pressure/Temperature Compensated Flow (PPTC) instruction calculates
Process
the flow of a gas at standard / design temperature and pressure, essentially
CS_PPTC Pressure/Temperature
a mass flow rate, given a volumetric flow rate or differential pressure
Compensated Flow (PPTC)
measurement.
Process Tank Strapping Use a PTST control strategy to calculate the volume of product in an upright
CS_PTST
Table (PTST) cylindrical tank, given the level of the product and the tank calibration table.
Process Valve Hand Use the PVLVHO control strategy to monitor a hand (locally) operated valve
CS_PVLVHO
Operated (PVLVHO) and display its current state.
Process Valve Motor Use the PVLVMO control strategy to operate (open and close) a motor-
CS_PVLVMO
Operated (PVLVMO) operated valve.
The Process Mix Proof Valve (PVLVMP) instruction controls and monitors
Process Mix Proof Valve
CS_PVLVMP feedback from a mix proof valve in various modes and states, and monitors
(PVLVMP)
for fault conditions.
Process Valve Solenoid Use the PVLVSO control strategy to operate (open and close) one solenoid-
CS_PVLVSO
Operated (PVLVSO) operated valve.
Use a PVSD control strategy to monitor and control a variable speed motor
Process Variable Speed
CS_PVSD using an AC
Drive (PVSD)
(variable frequency) or DC drive.
In this section, you will import a Library 5.10 control strategy routine for an analog input (PS_PAI) into
the program named TK300. This input will monitor the tank level.
1. Right-click on the program named TK300. From the menus select Add and then Import
Routine.
5. 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 (XT because an analog
transmitter input can be a pressure, temperature, level …) in the tag references 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.
7. Find all the instances of XT101 in the tag references and replace with LI300.Then click the
Replace All button.
8. Note that 2 occurrences of XT101 were found and replaced with LI300. Now click OK.
9. Wait for the import to complete. Once the import completes, a new routine named
Tank_Level is added to the TK300 program. Double-click on the new Tank_Level routine to
open the function-block editor and view the new code.
10. Verify that all the instances of XT have been replaced with LI300 in the tag name and input
reference connector. The level indication routine is complete, and the input reference
connector is associated to simulation tags for testing. Note that this is a PlantPAx Library 5.10
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 to open the Properties Dialog
Box.
11. When the Properties Dialog Box opens, notice the new 5.0 tabs: General, PV Fail Check,
Advanced, HMI, Alarms, Parameters and Tag.
On the General tab, change the high and low “PV clamping limits” to 100% and 0%.
12. On the PV Fail Check tab, change the high and low “Out of range” limits to 100 and -2.
13. On the Advanced tab, change the max and min for the input “Scaling Limits” to 100 and
0.0.
14. On the Alarms tab, check all the “Use” boxes for the alarms. Change the alarm Limits to
80, 60, 20 and 5 as shown below.
1. Right-click on the program named TK300. From the drop-down menus select Add and then
Import Routine.
3. Select the Lab Files folder. Note that all the control strategy files that will be used from this
point forward in the lab will be found in the C:\Lab Files folder to save time navigating the
complete Library.
5. Wait for the Import Configuration window to open. Change the Final Name from MT301 to
Discharge_Pump.
6. A motor can drive a blower, conveyor, mixer, agitator, or a pump. The tag references in the
library routine are prefixed with a generic MT301 designator for a motor. Since you are
configuring a pump to discharge the tank you will change the tags of the new routine to
PMP302. Click the Find/Replace button.
7. Find all instances of MT301 and replace with PMP302. Click the Replace All button. Then
click OK.
8. Click the OK button and wait for the import to be completed. A new routine named
Discharge_Pump will be added.
9. Double-click on the new Discharge_Pump routine to view the code. Verify that the tag name
and the cross-references have been changed to reference PMP302. Click the Ellipsis button
to view the motor block properties.
10. Note in controller versions above v33, RSLinx software is no longer a requirement to get
online with the controller because FactoryTalk Linx software is used instead. FactoryTalk
Linx allows the use of Extended Tag Properties, and you can now fully configure the block
parameters and faceplate labels from within Studio5000. You can navigate to each tab to
explore the configuration of general, scaling, alarming, associated IO status/faults, and so on.
Explore the tabs and then close the 5.10 Properties Dialog Box.
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 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.
2. Click on Rung 0 to select the rung (indicated by a blue box) and then right-click and select
Copy Rung.
3. Go to the end of the ladder and Paste twice to add two new JSR rungs.
4. Two new rungs have been added to the bottom. Notice that after pasting the copied rung the
JSR still references the Simulation routine. The new JSR on rung 2 needs to have the Routine
Name parameter changed to Discharge_Pump. Use the drop-down arrow and select
PMP302.
The new JSR on rung 3 needs to have the Routine Name parameter changed to Tank_Level.
The rungs should look like below when completed.
6. 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.
8. In the upper left of the Logix Designer window click the Save button.
9. Click on the Controller Status down-arrow and select Download from the drop-down
window.
11. Wait for the controller download to complete. This may take a couple of minutes but with
library 5.10 blocks in firmware the downloads to the controller go much quicker than with the
4.x library AOIs. When complete, click on the Controller Status down-arrow again, and select
Run Mode from the drop-down window.
13. Verify that the controller status button is green and indicates in Run mode.
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.
1. Click the Studio 5000 icon on the bottom taskbar or on the desktop to open Studio 5000.
2. 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.
3. Wait while FactoryTalk View Studio opens. This will take a few minutes.
FactoryTalk View Studio is configuration software for developing PlantPAx HMI (Human Machine
Interfaces) 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.
FactoryTalk View Studio is a single software package that covers HMI challenges in process, batch,
and discrete application. Clear displays and a common programming language, including a huge
library of faceplates, help confirm that you get the best possible perspectives of your process
devices.
4. In the Communication Setup window, select the device shortcut named LAB. Shortcut
names are used in graphics to connect a graphical element to a specific controller. Note that
the existing path for the shortcut named LAB is pointed to the emulated controller with IP
address 127.0.0.4.
5. The check boxes for the Extended Tag Properties reduce the need for string tags and allow
for language translation. They are also used for the library 5.10 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.10 they have been expanded to allow process device
control. Confirm the boxes are checked.
6. The Alarm & Events should be subscribed to All Alarm & Events Notification Messages. The
HMI project now has its communication path to the area controller defined and configured.
Click OK to close the Communication Setup window.
Section Summary
In controller versions above v33, FactoryTalk Linx allows the use of Extended Tag Properties, and you
can now fully configure the faceplate within Studio5000. Also, FactoryTalk Alarms and Events are
now initiated from the controller. This is not a new concept but has been expanded to be fully
integrated into the AOI in PlantPAx 5.10. This allows configuring of alarms from within the PAC
through the configuration pop-up screen that has multi-tabs and sub-screens.
2. Note the new displays folder structure in FactoryTalk View’ Studio. With Studio v12 and above
you can now create sub-folders in the Displays folder. For this lab, the lab specific displays
are in the folder named LAB. Notice that displays for the framework (button bars, alarm
summary, level 1/2/3 display templates …), the 4.6 library displays, and the 5.1 library displays
are all included and compatible in this application.
Double-click on the display named “(LAB) p2f storage tanks 3_4” to open the display in the
editor.
Note that a pump object for an Addition Pump, PMP301, is already configured on the display using a
PlantPAx Library 4.6 object. Pump PMP301 is used to show compatibility between the 4.x and 5.x
libraries. In this lab you are adding the latest PlantPAx Process Library 5.10 objects. This display
started as a blank Framework Library Level 2 template display. 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.
1. In the Explorer window, minimize all graphics subfolders except for Lab, and expand the
Global Objects folder.
2. 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.x for Studio SE applications. All the 4.x Library displays, and global objects
are prefixed with RA-BAS, which stands for Rockwell Automation Base library. The 4.x library
is also available for View ME.
Double-click on the Global Object “(raP-5-SE) Graphic Symbols - PMTR” to open the display.
3. 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.
4. Next, in the Global Objects folder, scroll to and double-click the Global Object named
“(raP-5-SE) Graphic Symbols – PAI”. The PAI stands for process analog input.
5. 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.
6. On the storage tanks graphic, move the three new objects to look like below:
7. Right-click on the new discharge pump object and select Global Object Parameter Values
from the selection menu.
8. 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 PMP302 (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.
9. 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.
10. 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.
11. Scroll-down the list and select the tag PMP302 and click OK.
Note that in the 4.x 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.10 library this
parameter is removed, and the path data is parsed from parameter 1.
Note the other parameters. For library 5.10, parameter 2 is the X coordinate for the faceplate
pop-up and parameter 3 is the Y coordinate. For parameters 2 and 3, enter the X/Y
parameters /X460 and /Y700 respectively.
14. Right-click on the new Analog Input trend object and select Global Object Parameter Values
from the selection menu.
15. For parameter 1, click on the ellipsis button in the column named Tag to open a Tag Browser
window
16. The Tag Browser window will open. Scroll to and select LI300 and click OK to accept the
updated parameter.
Note the other parameters. For parameter 2 and 3, enter the X/Y parameters /X700 and
/Y300 respectively.
19. Right-click on the new Analog Input object and select Global Object Parameter Values from
the selection menu.
20. Configure the level indicator to match the level trend object parameters (as shown below),
save the changes, and close the parameters window.
21. Click on the Save button to save the updates to the display.
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.
1. Click on the PlantPAx HMI client icon at the left on the desktop.
1. 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.
3. 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
filling the tank. Click on the Addition Pump object to open the pump control operator
faceplate.
4. Note that PMP301 is a library 4.6 faceplate. For library compatibility the 5.10 faceplates
have the same look and feel from the operator’s perspective as the 4.x faceplates. Click
the Start button to start the fill pump.
5. 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. Click on the
Interlock Button on the faceplate.
6. Note the interlock condition. If the device had multiple interlocks active the first interlock
to occur would be highlighted as “first in “for troubleshooting. Click the X’s to close the
interlock and pump faceplates.
8. 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.x Logix Dialog Boxes, or for 4.x applications from the Maintenance tab of the
device faceplates in the running Client application. For bulk configuration changes of
these parameters PlantPAx 5.x includes a “PlantPAx Configuration Tool’” that can be used.
This tool can be used both off and on-line. Start the Discharge Pump.
9. While waiting for the tank to empty, click on the Tank level indicator and then click the
Trends button on the level faceplate.
10. Note there are three ways to view the trend chart. Click on the PV with Limits button.
11. The built-in trend charts can help Operators monitor the process and trouble-shoot
issues. Close the Trend faceplate. Note the alarm status indications. Click on the Alarms
tab on the Level faceplate.
12. Click on the “Acknowledge and Reset” the alarms button. The alarms will stop flashing
because they are acknowledged but they are still indicated as active level alarms. Close
the Level faceplate.
13. When the tank was filled, the Addition Pump was stopped by the level interlock. But
notice that 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 the pump to protect it from running with an empty tank. Stop the Discharge
Pump PMP302.
14. Start the Addition Pump PMP301 again to fill the tank.
15. Wait for the tank to fill and notice the level alarms are reset. When filled the Addition
Pump is stopped. Click on the Addition Pump PMP301 Interlock button to open the
interlock faceplate.
16. Click on the Maintenance tab of the Interlock faceplate. Note the Interlock faceplate still
references the default tag description and that the fill level has been reached.
18. 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.x faceplate.
19. Change the Label and Tag to PMP301. Close the Interlock Advanced Properties
faceplate.
20. From the Interlock faceplate, check the box to enable the bypass of the Fill Level
Reached interlock and close the interlock faceplate.
22. From the Maintenance tab the operator can now make the decision to bypass the selected
interlock(s). Slide the Bypass Enabled selector to Yes. Then click Yes at the pop-up
window to confirm the selection.
23. Notice the interlock bypassed indicators. Click on the “Home – Operator” tab button.
24. Notice the pump can now be started, for maintenance or emergency service, even in an
interlock condition.
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 quickly
copied to a new Tank 400.
1. 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.
Switch to the Logix Designer window by using the Alt+Tab keys on your keyboard or
from the task bar.
Note for OnCourse Users: Alt+Tab from the keyboard does not work when using
OnCourse. To switch application windows, use the drop-down Action/Send Keys options
at the center top of the screen, as shown below:
4. 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.
5. Right-click on the Logical Model (of the controller named) LAB and click on Paste
Special with Configuration.
6. Wait for the Import Configuration window to open. Click on the Find/Replace button.
7. 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.
8. Click OK.
9. 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.
10. Note that the TK400 program has been added. Expand the TK400 program.
11. Double-click on the TK400 Tank_Level routine. Note the input reference and the tag
name now reference 400.
Section Summary
Using the library helps to promote consistency across your application as all the objects in the library
use a common set of symbols, and each is designed with a similar look and feel to them.
Information only:
For bulk configuration of new projects, Studio 5000® Application Code Manager (ACM) software can
be used. ACM helps speed system development by using libraries of re-usable code that can be
managed and deployed across the entire enterprise. Creating projects with Application Code
Manager helps improve design consistency, reduce engineering costs, and achieve faster
commissioning. Easily create and configure objects in bulk using re-usable libraries of code to
increase application development, without any additional programming.
Note: For more information and a short introduction to ACM, please refer to the Hands-on-Lab
named “PlantPAx Bulk Configuration with ACM”. This lab is available at Automation Fair 2023 and will
be available on OnCourse after the show.
Adding Tank 400 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.
2. The FactoryTalk View Studio window should still look as shown below. Use the cursor to
highlight all the TK300 objects.
3. Click Arrange from the editing selections on the upper menu bar. Click Group from the
drop-down menu. This groups the Tank 300 device objects.
5. Right-Click on the display background and select Paste from the drop-down.
8. For the level tags, in the Tag Substitution window Search for LI300 and Replace with
LI400. Click the Replace button.
11. Repeat the above Tag Substitution steps to search and replace PMP3 with PMP4. This
will replace PMP301 with PMP401 and replace PMP302 with PMP402.
14. Click on the grouped TK400 to highlight it. Click on the Arrange button on the upper
banner and choose Ungroup.
15. Right-click on the TK400 Addition Pump PMP401 and select Global Object Parameter
Values.
16. Change the parameter 3 for the faceplate X coordinate from to /X510. Change the
parameter 4 for the faceplate Y coordinate from to /Y520.
18. Using the same steps as above, for the TK400 Level Indicator change the parameter 3
for the faceplates to /X1200.
19. Using the same steps as above, for the TK400 Discharge Pump change the parameter 3
coordinate to /X960.
20. Click on the Save button to save the updates to the display.
Testing the New TK400 Pump and Level Routines and HMI Display
2. Click on the “TK100 / TK200 Lab” button on the button bar of the client.
3. Click on the “TK300 / TK400 Lab” button. This refreshes the client screen with the
display updates.
4. Click on the Tank 400 Addition Pump PMP401 and click the start button to fill the tank.
Wait for the tank to fill.
5. Click on the Discharge Pump, PMP402 and start the pump and verify that the tank
empties.
For larger applications, bulk configuration of tag parameters would be completed using Rockwell’s
PlantPAx Configuration Tool. 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.
2. From the Maintenance Tab, click on the Display Advanced Properties button.
Notice that 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. If using Library 4.x objects the grayed-out text entry boxes for labels
and descriptions would be enabled. For 5.10 the functionality has been moved to Logix.
4. Let’s examine the v5.10 Studio 5000 Logix Designer Dialog Boxes more. Switch to the
Logix Designer window by using the Alt+Tab keys on your keyboard or from the task bar.
5. In Studio 5000 Logix Designer, double-click on the TK400 Discharge Pump 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. There is no need to create a device object and faceplate in a display to test the
code.
6. Click on the Command Source tab. This tab is new for the 5.x library. Note the mode buttons.
No need to create a device object and faceplate in a display to test the mode logic.
7. Click on the Advanced tab. This tab is new for the 5.x library for motor configuration.
8. Click on the HMI tab. This tab is new for the 5.x library. This is where the Tag Label and
“Area name for Security” can be changed.
9. Expand the HMI tab and click on the Command configuration in the HMI tab. This tab is
new for the 5.x library. Command and state text is configured here.
10. Click on the Alarms tab. This tab is new for the 5.x library. Click on the ellipsis button to
the right of the Fail To Start alarm to open the alarm’s Properties window.
All alarm configurations are now in Logix Designer. This workflow is new for the5.x library.
Close the Alarm Properties window.
11. Click on the Parameters Tab. The parameters tab is like the parameters tab for the
Process Library version 4.x0 Add-On Instructions (AOIs). Every parameter for the block
can be viewed or configured from this window.
12. Click on the Tag tab. The Tag tab is like the Tag tab for 4.x library blocks. The tag name
and description can now be configured in Logix. This workflow is new for the 5.x library.
14. Double-click on the Tank_Level routine to open the editor and click the ellipsis button
on the LI400 PAI block
15. On the General tab note the SAMA diagram and limit entry fields. This tab is new for the
5.x library.
16. Click on the Alarms tab. This tab is new for the 5.x 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.x and 5.x libraries.
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 an empty
tank level condition. 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.
1. While already in Logix you will now add the interlock logic to the Discharge Pump. Click
on the TK400 Discharge Pump routine. Use the “Sheet down-arrow” to select sheet 3
named “Interlock Bank 0”.
2. In this section you will 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. The bright green border indicates online. To make changes online to the
interlock logic, click the Start Pending Routine Edits button.
Note the online edit mode indicated by the gray border and the active edit mode icons.
3. 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).
4. Double-click on the input reference and type LI400_Inp_PV or click on the down-arrow
to open the drop-down tag browser and select LI400.Inp_PV. This is the tag for the Tank
400 level process variable.
Next you need to add a block that compares the value of the level, LI400_Inp_PV, 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.
5. Click on the Compare tab. This tab contains all the blocks that have compare functions.
Note that the PlantPAx 5.x Instructions (in firmware) are listed in the PlantPAx Element Group
tab. The Add-On tab is the library 4.x Instructions as AOIs. The AOIs can be modified (unlike
the firmware based 5.x Instructions) 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.
8. Change the connector to value of 1. If the tank level drops below 1% we will consider it
empty and interlock the pump.
9. Connect the output pin from the connector LI400.Inp_PV to the input pin Source A of the
LES block.
10. Next, connect the output pin from the connector value 1 to the input pin Source B of the LES
block. And finally, connect the LES block output pin to the Inp_Intlk00 input on the P_Intlk
object. Note that 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.
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).
15. The interlock is now added to the code, you still need to commission the interlock
faceplate. For PlantPAx instructions you will use the properties of the PINTLK instruction
to accomplish this. Click on the ellipsis button on the PINTLK block.
16. The General tab of the Properties Dialog Box shows the status of all the interlocks. Click
on the Advanced 0-15 tab to configure the new interlock parameters.
17. On the Advanced 0-15 tab, name the new interlock “Tank Empty”.
18. Expand the HMI tab and click on Type. Note the types for the interlocks. This is new in
the 5.x library.
19. 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.
2. The Client screen should still have the TK400 discharge pump faceplate open as shown
below. Notice that the PMP402 discharge pump is now stopped and is indicating an
interlock condition (black stop-sign). Close the maintenance faceplate.
4. 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.
5. Note on the Tank Level indicators 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.
7. Click the button to Acknowledge the Low alarm. Notice the Low alarm stops flashing.
Close the Low alarm faceplate.
8. Click the Acknowledge and Reset Button to acknowledge and reset both alarms.
9. 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.
Section Summary
The new workflow in 5.x 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.
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.
2. 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.
3. 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.x
Logix Dialog Boxes.
Extended Tag Properties have been available since v31 of Logix Designer. For library 5.x they
have been expanded to allow process device control and reduce the need for string tags and
allow for language translation.
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.
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.
1. 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.
2. Expand the “Area 1000 Slurry” displays folder and click to open the “a1000_slurry
header_1mon” display.
3. Scroll to the right and Right-click the Alarm and Events Banner in the “a1000_slurry
header_1mon” display and select Properties.
4. 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.x FactoryTalk Alarms and Events (FTAE) alarms with no
filtering by controller (5.x) or area (4.x). 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.
5. Expand the PlantPAx folder, expand the PlantPAx_Data_Area folder, and click on
FactoryTalk Linx.
6. Click OK.
7. You have now selected the specific Alarm and Events Server associated with this HMI
server. Verify the scope as shown below.
8. Click OK again.
10. Click Save to save the changes to the header banner display.
11. Note, following the same configuration workflow as for the alarm banner above, Alarm
Summary displays, can be configured with a specific alarm scope.
2. Open the Tank 400 Addition Pump faceplate and start the pump.
Note that the fill pump PMP401 is stopped by the interlock when the fill level is reached.
Notice that the PMP401 alarm for the interlock did not show up on the banner. The fill pump is
configured with 4.x objects and therefore does not use the new Tag Based alarms.
IMPORTANT
For Process Library 4.x Instructions, the alarms must be configured in the FactoryTalk Alarms &
Events Server.
For larger applications 4.x 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.x Library objects used in the controller. This tool allows bulk configuration of FTAE alarm for
large process projects using Library versions 4.x and below. (Refer to publication PROCES-RM002 for
more information on the tools.)
For the 4.x library, the server-based alarms are configured in the FTAE Alarm Server in FT View
Studio.
IMPORTANT
The following two pages are for 4.x alarms configuration and are for “Information only”. No lab
exercise is required.
For the 4.x library, the server-based alarms are configured in the FTAE Tag Based Alarm Server
using the Alarm and Event Setup (whereas the new 5.x Logix Tag Based alarming is configured in
each controller and on the associated data servers).
Example Only:
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.x 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 only:
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.x alarms on the banner
the scope must include the FTAE alarm server in the scope.
Example only:
Section Summary
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.x 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.x 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.
2. Verify that you are still on-line, the controller running, and select the Logical Organizer
tab.
3. Right-click on the program named TK300. From the menus select Add and then Import
Routine.
6. Replace all X with P (for pressure) and click the Replace All button. This tag is for the
remote SP connection from the PPID block of the pressure control loop.
7. 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.
9. Click Yes.
10. Click the button to Finalize All Edits in Program and click OK.
1. Right-click on the program named TK300. From the menus select Add and then Import
Routine.
2. From the Lab Files folder Select the file (RA-LIB)CS_PPID_5_00-00_Routine.L5X, and
click Open.
4. Replace all X with P. This tag is for the remote SP connection to the PVSD block of the
drive loop (replaced 19 occurrences).
6. Click OK.
7. Click the button to Finalize All Edits In Program and click OK.
2. 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.
4. Click on Yes.
5. Verify no errors.
2. The PAI block is the analog input block for scaling and alarms. 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. Scroll over to display both the PAI and
PPID block in the function block editing window. Click on the PPID ellipsis button.
3. 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.
4. Click OK.
6. Click Yes.
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.
2. In FactoryTalk View Studio, scroll down in the Global Objects folder and Double-click
on the 5.x 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.x. All
Global Object display names prefixed with “(RA-BAS)” are for the Process Library 4.x.
3. Drag-and-Drop a Pump object from the Global Objects display to the storage tanks
graphic. 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.
4. In the Global Objects folder and double-click on the 5.x Global Object named “(raP-5-SE)
Graphic Symbols – PPID”.
5. Drag-and-Drop a PPID object from the Global Objects display to the storage tanks
graphic.
6. The display should look like below. Right-click on the variable speed pump object.
11. Verify that parameter 1 matches below and change parameter 2 to /X1430 and
parameter 3 to /Y200.
14. And select Global Object Parameter Values from the selection menu.
16. Scroll to and Select the PIC300 tag and click OK.
2. Click on the “TK100 / TK200 Lab” button on the button bar of the client.
3. Click on the “TK300 / TK400 Lab” button. This refreshes the client screen with the
display updates.
4. 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.
5. Verify that the motor starts (running forward at zero speed). 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”.
6. Click on the Command Source button on the MT300 faceplate. Then on the small
Command Source faceplate, click the Request Program Control button.
7. MT300 is in program mode and is getting a remote setpoint from the PIC300 pressure
controller. Close the Command Source faceplate.
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.
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.
13. Click on the Leave DB (deadband) input box for the PV to SP leave error and enter 1. Click
OK.
14. Click on the Enter DB input box for the PV to SP Enter error and set the value to 1. Now
when the PV is within 1 psig of entering or leaving the SP, the warning will disappear. Also,
change the PV EU Max/Min to 100, then click OK.
16. Return to the Operator Tab and notice that (if you wait for the process to settle out) the
deviation will be in the deadband.
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.
With PlantPAx, adding or replacing HART devices, even online, is made simple with fully integrated
HART faceplates and device diagnostics. From the Process Library 5.10 faceplates, that render HART
content automatically, to the Integrated device diagnostics profiles, adding a HART device is simple
and Intuitive.
2. The first thing that you will need to do is create an Ethernet adapter module to
communicate with a remote rack. Within that rack you will add a HART I/O card capable of
“Highly Integrated HART” (HIH).
5. Wait for the window to open. In the Filter box, type 5094 and select the 5094-AENTR
device to add to the I/O tree. Click Create
6. Configure the device name and address as shown below. Click OK.
7. To avoid error messages because you don’t have physical hardware, navigate to the
Connection tab, and check box to Inhibit Module. Click OK.
2. In the filter box, type IF8IH and select the 5094-IF8IH device to add. Click Create.
3. On the General tab, configure the module name as Remote_IO_S1_IF8IH (for remote IO in
slot 1) as shown below. Click OK.
5. On the Ch00 tab, ensure that the Enable HART checkbox is selected. Click OK.
1. Expand the 5094-IF8IH/A in slot 1 and right-click the HART backplane and select New
Module.
2. Type “Promag 400” into the filter window and select the HART-Device-1169 Catalog
Number from the list of devices. Click Create
1. Change the Name of the device to Tanks_OutFlow 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. Click the Change button in the Module Definition box.
When adding HART devices using PlantPAx Data types, the device data structures can easily
be interfaced with the PlantPAx Instructions.
2. From the Connection drop down menu, select PlantPAx Data. Click OK.
7. Notice the Promag 400 flow meter HART-Device-1169 is now available in the I/O tree.
1. Scroll up in the Controller Organizer to the TK300 program under the Normal (250 ms)
task. Right click the TK300 program and select Add and Import Routine.
8. 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.
9. Click Start Pending Routine Edits at the top left corner of the sheet.
10. Double click the “Select_HART_Device” tag in the Ref_HARTData parameter of the
instruction.
11. Replace it with the Tanks_OutFlow:I.PAxDevice Promag device tag that we created
earlier as shown below.
1. Click to Finalize All Edits in Program and Click Yes on the popup.
2. 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”.
6. Close the Controller Tags tab and open the MainRoutine for TK300 and add a JSR for the
newly created FI301 routine. This can be done by copying and pasting one of the other JSR
rungs and changing the Routine Name to FI301.
2. To add a new PAI Global Object to our display, search the Global Objects folder and open
“(raP-5-SE) Graphic Symbols – PAI”.
3. Copy (or drag-and-drop) the Generic Analog Input global object, with no graphical
indication of the PV (top left object), to the Tanks 3 and 4 graphic.
6. Refresh the folders, navigate to PlantPAx_Data_Area > LAB > Online and select the
FI301 tag. Click OK.
7. Enter /RP for parameter 2 to have the faceplate launch in the “Relative Position” of
where the device object is. Click OK.
2. Click on the “TK100 / TK200 Lab” button on the button bar of the client.
3. Click on the “TK300 / TK400 Lab” button. This refreshes the client screen with the
display updates.
4. Click the FI301 Object to launch the faceplate. Navigate to the Maintenance tab.
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
• Maintenance Tab
6. This concludes the Highly Integrated HART section of this lab. Close all the faceplates.
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?
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.10 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.