Professional Documents
Culture Documents
P LLS
P LLS
IMPORTANT This manual applies to the Rockwell Automation Library of Process Objects version 3.5 or earlier.
For Rockwell Automation Library of Process Objects version 5.0, see
• PROCES-RM200
For Rockwell Automation Library of Process Objects version 4.0 or later, use the following manuals:
• PROCES-RM013 contains logic instructions
• PROCES-RM014 contains display elements
Important User Information
Read this document and the documents listed in the additional resources section about installation, configuration, and
operation of this equipment before you install, configure, operate, or maintain this product. Users are required to
familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws,
and standards.
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required
to be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be
impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the
use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or
liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or
software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation,
Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: 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.
ATTENTION: 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, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
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).
Allen-Bradley, Rockwell Software, and Rockwell Automation are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Table of Contents
Preface Software Compatibility and Content Revisions . . . . . . . . . . . . . . . . . . . 5
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Lead/Lag/Standby Motor Group Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
(P_LLS) Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Controller File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Lead/Lag/Standby Motor Group InOut Structure . . . . . . . . . . . 13
Lead/Lag/Standby Motor Group Output Structure . . . . . . . . . . 21
Lead/Lag/Standby Motor Group Local Configuration Tags. . . 24
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Motor Sort Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Display Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
State Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Status/Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Mode Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Alarm Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Maintenance Bypass Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Using Global Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Quick Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Maintenance Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Diagnostics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Lead/Lag/Standby Motor Group Faceplate Help. . . . . . . . . . . . . 54
Notes:
Software Compatibility and For the latest compatible software information and to download the Rockwell
Automation Library, see the Product Compatibility and Download Center at
Content Revisions http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.
Table 1 - Summary of Changes
Topic Page
Visualization Files: Global Objects (.ggfx) - Process Diagnostic Objects 11
Array Member Content - Navigation Tag 14
For the latest compatible software information and to download the Rockwell
Automation® Library, see the Product Compatibility and Download Center at
http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.
Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Resource Description
PlantPAx® Distributed Control System Selection Guide, Provides information to assist with equipment
publication PROCES-SG001 procurement for your PlantPAx system.
PlantPAx Distributed Control System Reference Manual, Provides characterized recommendations for
publication PROCES-RM001 implementing your PlantPAx system.
Rockwell Automation Library of Process Objects Reference Provides general considerations for the PlantPAx system
Manual, publication PROCES-RM002 library of process objects.
FactoryTalk® View Machine Edition User’s Guide, Provides details on how to use this software package for
publication VIEWME-UM004 creating an automation application.
FactoryTalk View Site Edition User’s Guide, Provides details on how to use this software package for
publication VIEWSE-UM006 developing and running human-machine interface (HMI)
applications that can involve multiple users and servers,
distributed over a network.
Logix5000™ Controllers Add-On Instructions Provides information for designing, configuring, and
Programming Manual, publication 1756-PM010 programming Add-On Instructions.
Rockwell Automation Library of Process Objects: Common Details how to monitor an input condition to raise an
Alarm Block (P_Alarm) Reference Manual, alarm. Information includes acknowledging, resetting,
publication SYSLIB-RM002 inhibiting, and disabling an alarm. Generally the P_Alarm
faceplate is accessible from the Alarms tab.
Rockwell Automation Library of Process Objects: Explains how to collect (sum up) the interlock conditions
Interlocks with First Out and Bypass (P_Intlk) Reference that stop or de-energize a running or energized piece of
Manual, publication SYSLIB-RM004 equipment or prevent it from starting or being energized.
Rockwell Automation Library of Process Objects: Common Explains how to choose the Mode (owner) of an
Mode Block (P_Mode) Reference Manual, instruction or control strategy. The Mode instruction is
publication SYSLIB-RM005 usually embedded within other instructions to extend
their functionality. It is possible to use a standalone Mode
instruction to enhance a program where modes are
wanted.
Rockwell Automation Library of Process Objects: Details how to collect permissive conditions to start a
Permissives with Bypass (P_Perm) Reference Manual, piece of equipment.
publication SYSLIB-RM007
The P_LLS (Lead Lag standby motor group) Add-On Instruction provides
control of a parallel group of motors. Such groups are commonly used for a group
of pumps that maintain pressure on a header despite wide changes in demand,
such as in municipal-scale or plant-scale water distribution.
The following global object and faceplate images are examples of the graphical
interface tools for this Add-On Instruction.
Add-On Instruction
Guidelines Use this instruction to control a group of motors, such as a set of pumps with
common intake source and discharge destination. The number of motors to run
depends on the demand on the system. The P_LLS group can be configured to
consist of as few as 2 or as many as 30 motors. The minimum demand can be set
as low as 0, so that all motors are stopped at minimum demand. The maximum
demand can be set as high as the number of pumps in the group. (In this case, if
the demand were as high as the number of pumps in the group, there would be no
'standby' pumps.)
IMPORTANT To automate the group of motors, logic outside the P_LLS Add-On Instruction
must determine the demand and the number of motors in the group to run.
Every Lead / Lag / Standby control strategy consists of two basic parts: the logic
that determines number of motors to run (the demand), and the logic that
determines which motors to run. The P_LLS instruction provides the second
part of such a strategy. The logic that determines the demand varies from
application to application. The developer of each application must provide and
test this logic.
An operator or other logic determines the demand for motors. The P_LLS
instruction determines which motors to run to meet demand. In order for P_LLS
to start and stop motors in the group, they must be 'available'. A motor is available
when it has no faults and is in Program Mode.
The P_LLS instruction uses a sorting algorithm to deal with motors that are not
available. If a motor is running and not available (perhaps running in Operator
Mode), the motor is forced to the top of the sort. If a motor is stopped and not
available (perhaps faulted), the motor is forced to the bottom of the sort. The
motors that are available to start and stop are controlled to meet the demand. If
the demand cannot be met because of unavailable motors, a status/alarm
is provided.
EXAMPLE Two motors in a group of four are stopped and not available. The P_LLS
instruction raises a 'can’t start' alarm when the demand reaches three because
there are only two motors available to run.
Functional Description The P_LLS Instruction controls and monitors a group of 2 to 30 motors and
provides:
• Operator, Program, and Override capability to start and stop the group (as
a group).
• Ability for the Operator or Program to enter a 'demand', the number of
motors to run.
• Configurable maximum demand (1 to number of motors in group).
• Configurable minimum demand (0 to maximum demand).
• Configurable to stop the last started motor or the first started motor
(first-on-last-off or last-on-last-off ).
• Configurable delay between starts and configurable delay between stops.
• Start and Stop commands on the P_LLS instruction allow for starting or
stopping the motors as a group. The delay between starts or stops can be
configured to sequence the motors.
• Starts or stops motors as required to meet the entered demand.
• Identifies (and optionally alarms) when there are not enough motors
available to start (in Program Mode and ready to run) for the given
demand to be met.
• Identifies (and optionally alarms) when there are not enough motors
available to stop (in Program Mode and ready to stop) for the given
demand to be met.
• Ability to rotate the list of motors (demote the lead, promote the others).
• Monitoring of Permissive conditions to allow starting the motor group.
• Monitoring of Interlock conditions to stop/prevent starting the
motor group.
• Alarm if interlock conditions cause the group to be stopped.
• Supports HMI 'breadcrumbs' for Alarm Inhibited, Bad Configuration,
Not Ready, and Maintenance Bypass Active.
• 'Available' status for use by automation logic to know whether motor group
can be controlled by other objects.
Required Files Add-On Instructions are reusable code objects that contain encapsulated logic
that can streamline implementing your system. With this code, you can create
your own instruction set for programming logic as a supplement to the
instruction set provided natively in the ControlLogix® firmware. An Add-On
Instruction is defined once in each controller project, and can be instantiated
multiple times in your application code as needed.
Controller File
The P_LLS_3_5-00_AOI.L5X Add-On Instruction must be imported into the
controller project to be used in the controller configuration. The service release
number (boldfaced) can change as service revisions are created.
Visualization Files
This Add-On Instruction has associated visualization files that provide a
common user interface. These files can be downloaded from the Product
Compatibility and Download Center at
http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.
IMPORTANT The visualization file dependencies require Process Library content imports to
occur in a specific order as reflected in the following tables:
• Images
• Global Objects
• Standard Displays
• HMI Tags
• Macros
Images are external graphic files that can be used in displays. They must be
imported for FactoryTalk View to make use of them.
When PNG files are imported, they are renamed by FactoryTalk View with
a .bmp file extension, but retain a .png format.
Table 2 - Visualization Files: Images (.png)
FactoryTalk View SE Software FactoryTalk View ME Software Description
All .png files in the images folder All .png files in the images folder These are the common icons used in the global objects and
standard displays for all Process Objects.
The Global Object files (.ggfx file type) in the following table are Process Library
display elements that are created once and referenced multiple times on multiple
displays in an application. When changes are made to a Global Object, all
instances in the application are automatically updated.
Table 3 - Visualization Files: Global Objects (.ggfx)
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-BAS) Common Faceplate Objects (RA-BAS-ME) Common Faceplate Objects Global objects used on process object faceplates.
The Standard Display files (.gfx file type) in the following table are the Process
Library displays that you see at runtime.
Table 4 - Visualization Files: Standard Displays (.gfx)
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-BAS) Common-AnalogEdit N/A Faceplate used for analog input data entry. The FactoryTalk
View ME faceplates use the native analog input data entry
so no file is required.
(RA-BAS) P_Alarm-Faceplate (RA-BAS-ME) P_Alarm-Faceplate The faceplate that is used for managing alarms for
the object.
(RA-BAS) P_Alarm-Help (RA-BAS-ME) P_Alarm-Help Alarm Help information that is accessed from the
P_AIarm faceplate.
(RA-BAS) P_LLS-Faceplate (RA-BAS-ME) P_LLS-Faceplate The faceplate that is used for the object
(RA-BAS) P_LLS-Quick (RA-BAS-ME) P_LLS-Quick The Quick display that is used for the object
(RA-BAS) P_Mode-Config (RA-BAS-ME) P_Mode-Config The Configuration Display used to configure the
P_Mode object.
(RA-BAS) Process Motor Family-Help (RA-BAS-ME) Process Motor Family-Help The Help display for Motor objects
(RA-BAS) P_Intlk-Faceplate (RA-BAS-ME) P_Intlk-Faceplate Optional
The interlock faceplate used for the object.
Use this file if your Discrete Output has an associated
P_Intlk object and you enable navigation to its faceplate
from the Discrete Output faceplate.
(RA-BAS) P_Perm-Faceplate (RA-BAS-ME) P_Perm-Faceplate Optional
Permissive faceplate that is used for the object
Use this file if your object has an associated P_Perm object
and you enable navigation to the P_Perm faceplate from
the object faceplate.
(RA-BAS) Process Interlock Family-Help (RA-BAS-ME) Process Interlock Family-Help Optional
Interlock/permissives help display that is used for
the object
Use this file if you use the P_Intlk or P_Perm faceplate.
Controller Code This section describes the parameter references for this Add-On Instruction.
InOut parameters are used to link the Add-On Instruction to external tags that
contain necessary data for the instruction to operate. These external tags must be
of the data type shown.
The following images show an example of the ladder logic for transferring
commands and motor status for one motor. Three steps are shown:
• Get motor status into P_LLS.
• Execute P_LLS to select which motors to run.
• Forward commands to the motor from P_LLS to the individual motors.
Each of the three steps is shown on its own rung. If desired, all three steps can be
in one branched rung.
In the following diagram, the process for forwarding each of the commands
(PCmd_Acq, PCmd_Rel, PCmd_Start, and PCmd_Stop) is:
• The appropriate bit in the interface is tested to see if it set.
• If the bit is set, the bit is cleared and the corresponding program command
on the motor is set.
TIP The interface for the first motor in the group is element [0] of the interface
array tag.
TIP This logic assumes that the motor is configured to clear program commands
upon receipt (Cfg_PCmd_Clear = 1, the default value).
The motor logic uses the program commands to control the physical motor. The
motor logic also receives feedback from the motor.
The status (available, stopped, starting, running, and stopping) is read from the
motor and written to the interface.
Configuration parameters that are array, string, or structure data types cannot be
configured as parameters for Add-On Instructions. Configuration parameters of
these types appear as local tags to the Add-On Instruction. Local tags can be
configured through the HMI faceplates or in Studio 5000 Logix Designer®
application. Open the Instruction Logic of the Add-On Instruction instance and
then open the Data Monitor on a local tag. These parameters cannot be modified
by using controller logic or Logix Designer application export/import
functionality.
Tag Name Data Type Default Description
Cfg_Desc STRING_40 'Lead / Lag / Standby Motor Description for display on HMI. This string is shown in the title bar of the
Group' faceplate.
Cfg_Label STRING_20 'Motor Group Control' Label for graphic symbol that is displayed on HMI. This string appears on the
graphic symbol.
Cfg_Tag STRING_20 'P_LLS' Tagname for display on HMI. This string is shown in the title bar of the
faceplate.
Operations This section describes the primary operations for Add-On Instructions.
Modes
This instruction uses the following standard modes, which are implemented by
using an embedded P_Mode Add-On Instruction.
Table 11 - Modes
Mode Description
Operator The Operator owns control of the group. Operator commands (OCmd_) and Operator settings
(OSet_) from the HMI are accepted.
Program Program logic owns control of the group. Program commands (PCmd_) and Program settings
(PSet_) are accepted.
Override Priority logic owns control of the group and supersedes Operator and Program control. Override
Inputs (Inp_OvrdCmd and other Inp_OvrdXxxx values) are accepted. If so configured,
bypassable interlocks and permissives are bypassed.
Maintenance Maintenance owns control of the group and supersedes Operator, Program, and Override control.
Operator commands and settings from the HMI are accepted. Bypassable interlocks and
permissives are bypassed, and device timeout checks are not processed.
Hand Hardwired logic or other logic outside the instruction owns control of the group. The instruction
tracks the state of the device for bumpless transfer back to one of the other modes.
No Mode The device is disabled and has no owner because the EnableIn input is false. The main
instruction Logic routine is not being scanned. See Execution section for more information on
EnableInFalse processing.
Alarms
This instruction uses the following alarms, which are implemented by using
embedded P_Alarm and P_Gate Add-On Instructions.
Simulation
Execution
Condition Description
EnableIn False (false rung) Handled the same as if the group is disabled by command.
The motor outputs are de-energized and the group is
shown as disabled on the HMI. The mode is shown as No
mode. All alarms are cleared.
Powerup (prescan, first scan) Any commands received before first scan are discarded.
The motor is de-energized and treated as if it were
commanded to stop.
Embedded P_Mode and P_Alarm instructions are
handled in accordance with their standard powerup
procedures. See the Reference Manuals for the P_Mode
and P_Alarm instructions for details.
Postscan (SFC transition) No SFC postscan logic is provided.
uals ...
uals ...
uals ...
uals ...
uals ...
. . . . . . . . . . . . . . . . . . . . . . .
uals ...
Status Value Configured Pump Priority User-Input Select Value (e.g., function of run time) Configured Pump Preference Current Position value
d list) 0
ilable to stop) 1 0 0
1 1 1 0 0 1 1 1 0 0 1 1 1 0
1 1 0 1 1 1 1 0 1 1 1 1 0 1
1 1 0 1 0 1 1 0 1 0 1 1 0 1
1 1 0 0 1 1 1 0 0 1 1 1 0 0
1 1 0 0 0 1 1 0 0 0 1 1 0 0
KEY CONCEPT: The list of pumps is sorted (by descending numeric value, based on
signed integer bit pattern) to determine Lead / Lag / 2nd Lag ... order.
27
Lead/Lag/Standby Motor Group (P_LLS)
Lead/Lag/Standby Motor Group (P_LLS)
To determine the order in which the motors (pumps) are started, signed integer
bit patterns for each motor are sorted by numeric value. The following list is the
order in which the bit patterns are evaluated when sorting:
• Out of service bit
• Status value
• Priority value
• User-input value
• Preference value
• Current position value
This bit is used to flag the motor out of service (value = 1) and automatically send
it to the bottom of the list. If this bit = 0, the motor is free to operate and bits
5…30 determine its start order.
If multiple motors are out of service, bits 5…30 determine their position at the
bottom of the list.
Out of service motors are not commanded and are not counted as running even if
actually running.
If all motors have the same value, these bits do not affect the sort; the next set of
bits become the determining factor in the sort.
These bits are next in the order of precedence for sorting the array list. The value
of these bits corresponds to the number entered in the Motor Priority field in the
Motor Configuration dialog box (page 50).
The highest priority value has a pattern of '11111' (31), the next highest priority
value is '11110' (30), and so forth.
If this priority is not to be used for the sort, set the priority value to zero for
every motor.
If all motors have the same value, these bits do not affect the sort; the next set of
bits become the determining factor in the sort.
If the Status Values are equal and the Priority values are equal, enter values in
these bits to sort the motors in the array list to the desired order.
The highest user-input value has a pattern of '11111111' (255), the next highest
user-input value is '11111110' (254), and so forth.
If this value is not to be used for the sort, set the value to zero for every motor.
If all motors have the same value, these bits do not affect the sort; the next set of
bits become the determining factor in the sort.
These bits are next in the order of precedence for determining the order of the
motors in the array list. The value of these bits corresponds to the number
entered in the Motor Preference field in the Motor Configuration dialog
box (page 50).
The highest preference value has a pattern of '11111' (31), the next preference
value is '11110' (30), and so forth.
If this value is not to be used for the sort, set the value to zero for every motor.
If all motors have the same value, these bits do not affect the sort; the next set of
bits become the determining factor in the sort.
IMPORTANT The current position bits are the only set of bits that cannot be equal.
These bits are next in the order of precedence for determining the order of the
motors in the array list. The value of these bits corresponds to the value of the
current position of the motor in the list, and the value is established by the
P_LLS instruction. There is no user entry for this field.
• Lead motor - '11111' (31)
• First Lag motor - '11110' (30)
• Second Lag motor - '11101' (29) and so on …
The Status value, Priority value, User-input value, and Preference value must be
equal for all motors for the Current Position to be a determining factor in the
sort.
Display Elements A display element (global object) is created once and can be referenced multiple
times on multiple displays in an application. When changes are made to the
original (base) object, the instantiated copies (reference objects) are
automatically updated. Use of global objects, with tag structures in the
ControlLogix system, aid consistency and save engineering time.
Table 12 - P_LLS Display Elements
Display Element Name Display Element Description
GO_P_LLS_Motors Motors in right position acting as a group.
Label Maintenance
Bypass Indicator
Each graphic symbol includes a touch field over it that opens the object faceplate.
In addition, there is a tooltip on the graphic symbol that displays the configured
tag and description of the object.
State Indicators
The state indicator text changes and the graphic symbol color changes depending
on the state of the group.
Status/Quality Indicators
One of these symbols appears on the graphic symbol when the described
condition is true.
Graphic Symbol Description
Invalid configuration.
Motor idle.
TIP When the Invalid Configuration indicator appears, you can find which
configuration setting is invalid by following the indicators. Click the graphic
symbol to open the faceplate. The Invalid Configuration indicator appears on
the appropriate tab at the top of the faceplate to guide you in finding the
configuration error. Navigate to the tab and the condition with an invalid
configuration appears in a magenta box.
TIP When the Device Not Ready indicator appears, you can find what condition is
preventing operation by following the indicators. Click the graphic symbol to
open the faceplate. The Device Not Ready indicator appears on the appropriate
tab at the top of the faceplate to guide you in finding the condition. Navigate
to the tab and the condition preventing operation has this indicator next to it.
For the Lead/Lag/Standby Motor Group Instruction, the Not Ready indicator
appears under the following conditions:
• Group disabled by Maintenance.
• There is an invalid configuration.
• Interlocks are not OK and not bypassed. Non-bypassable interlocks are
not OK.
• Permissives are not OK and not bypassed. Non-bypassable permissives are
not OK.
• Operator Stop Priority command requires reset.
• Group logic is disabled or there is no mode.
For each motor, the Motor Not Controllable indicator appears under the
following conditions:
• Motor not in Program mode.
• Motor not ready to be commanded.
• Motor Out of Service (see P_LLS faceplate, Maintenance Tab Page 2 on
page 45
• Motor disabled (on the Maintenance Tab of the motor faceplate)
Mode Indicators
One of these symbols appears on the right side of the graphic symbol to indicate
the mode of the object instruction.
Transparent Program mode (if the default mode is Program and the current mode is Program, the mode
indicator is transparent).
Program mode (if the default mode is Operator).
Override mode
Maintenance mode.
Hand mode
No mode.
TIP The images provided for the Operator and Program default modes are
transparent; therefore, no mode indicators are visible if the device is in its
default mode. This behavior can be changed by replacing the image files for
these mode indicators with images that are not transparent.
Alarm Indicators
One of these symbols appears on the left side of the label to indicate the described
alarm condition and the alarm border and label background change color. The
alarm border and label background blink if acknowledgement of an alarm
condition is required. Once the alarm is acknowledged, the alarm border and
label background remain the color that corresponds to the severity of the alarm.
No symbol No change in color No alarm or alarm inhibit condition, and all alarms
are acknowledged.
This symbol appears to the right of the label to indicate that a maintenance
bypass has been activated.
TIP When the Maintenance Bypass indicator appears, you can find what condition
was bypassed by following the indicators. Click the graphic symbol to open the
faceplate. The Maintenance Bypass indicator appears next to the appropriate
tab at the top of the faceplate to guide you in finding the bypass. Once you
navigate to the tab, the bypassed item is flagged with this indicator.
• Motor taken out of service (See Maintenance Tab Page 2 on page 45).
The global objects for P_LLS can be found in the global object file
(RA-BAS-ME) P_LLS Graphics Library.ggfx for FactoryTalk View ME or
(RA-BAS) P_LLS Graphics Library.ggfx for FactoryTalk View SE. Follow these
steps to use a global object.
1. Copy the global object from the global object file and paste it in the
display file.
2. In the display, right-click the global object and choose Global Object
Parameter Values.
3. In the Value column, type the tag or value as specified in the Description
column.
4. Click OK.
Quick Display The Quick Display screen provides means for operators to perform simple
interactions with the P_LLS instruction instance. From the Quick Display, you
can navigate to the faceplate for full access for operation, maintenance personnel,
and configuration.
Faceplate The P_LLS faceplate consists of five tabs and each tab consists of one or
more pages.
The title bar of each faceplate contains the value of local configuration tags
Cfg_Tag and Cfg_Desc.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
Maintenance Diagnostics Exit
The faceplate provides the means for operators, maintenance workers, engineers,
and others to interact with the P_LLS instruction instance. You can also view the
status and values and manipulate it through its commands and settings. When a
given input is restricted via FactoryTalk View security, the required user security
code letter is shown in the tables that follow.
Operator Tab
The Faceplate initially opens to the Operator (‘Home’) tab. From here, an
operator can monitor the group status and manually operate the group when it is
in Operator mode.
The Operator tab has buttons to start and stop the group when it is in the proper
mode and shows the following:
• Current mode (Program, Operator, Override, Maintenance, or Hand)
• Requested mode indicator (appears only if Operator or Program mode is
superseded by another mode)
• Group state (stopping, stopped, starting, or running)
• Interlock and permissive status and navigation buttons
• Individual motor state indicators
Interlock/Permissives
Indicator/Navigation
Buttons
The following table shows the functions included on the Operator tab.
Table 14 - Operator Tab Descriptions
Function Action Security
Click to lock in Operator mode. Function locks the mode in Manual Device
Operator mode, preventing the program from taking control. Operation (Code B)
Number of Motors to Run Type a number between 0 and the maximum demand to Normal Operation of
indicate the number of motors to run. Devices (Code A)
Non-bypassed conditions OK
All conditions OK
Alarm indicators appear on the Operator tab when the corresponding alarm
occurs.
The following table shows the alarm status symbols that are used on the Operator
tab.
Table 16 - Operator Tab Alarm Status
Graphic Symbol Alarm Status
In Alarm (Active Alarm)
Maintenance Tab
Maintenance personnel use the information and controls on the Maintenance tab
to adjust device parameters. They also troubleshoot and temporarily work
around device problems and disable the device for routine maintenance.
Interlocks and
Permissives Bypassed Bypass/Check Interlocks
Indicator and Permissives Buttons
The following table shows the functions on page 1 of the Maintenance tab.
Table 17 - Maintenance Tab Page 1 Descriptions
Function Action Security Configuration Parameters
Click for Maintenance mode. Equipment None
Maintenance
(Code C)
Page 2 of the Maintenance tab shows whether the motors are in service or out of
service.
Engineering Tab
On page 1 of the Engineering tab, you can configure the description, label, and
tag for the device.
The following table lists the functions on page 1 of the Engineering tab.
This display lets you select the default mode for the object by selecting the
appropriate mode.
IMPORTANT If no mode is being requested, changing the default mode changes the mode
of the instruction.
You must have FactoryTalk View security code E to select the default mode on
this display.
Motor Configuration
Buttons
The following table shows the functions on page 2 of the Engineering tab.
Motor Configuration
This display lets you set the Motor Priority or Motor Preference. You can also
enable navigation to an associated faceplate.
The following table shows the functions on the Motor Configuration dialog box.
Diagnostics Tab
The Diagnostics tab displays possible reasons for the device not being ready.
The previous image indicates that the device is not ready because device
interlocks are not OK. This condition has also generated an Interlock Trip alarm.
Alarms Tab
The Alarms Tab shows all available alarms for the device and their current status.
From here, alarms can be acknowledged and reset. Click an alarm name to open
the alarm detail faceplate for that alarm, where the alarm can be shelved by the
operator, disabled by maintenance personnel, or configured by engineering.
Alarm
Severity
Indicators
Alarm Names
Acknowledge Alarm
Command Button
Reset and
Acknowledge All
Alarms Command
Button
Click an alarm name to open the P_Alarm faceplate for that alarm. From the
P_Alarm faceplate, you can configure and perform additional operations on
the alarm.
If an alarm is active, the panel behind the alarm changes color to match the
severity of the alarm. The color of the bell icon at the top of the faceplate shows
the severity of the highest active alarm, and the icon blinks if any alarm is
unacknowledged or requires reset.
When the Reset and Acknowledge All Alarms button is enabled, the panel
behind the alarm blinks, indicating the alarm requires acknowledgement or reset.
The Alarm Acknowledge button is enabled if the alarm requires
acknowledgment. Click the button with the check mark to acknowledge the
alarm.
In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more
information, contact your local distributor or Rockwell Automation representative, or visit
http://www.rockwellautomation.com/services/online-phone.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this
manual. You can contact Customer Support for initial help in getting your product up and running.
United States or Canada 1.440.646.3434
Outside United States or Canada Use the Worldwide Locator at http://www.rockwellautomation.com/rockwellautomation/support/overview.page, or contact your local
Rockwell Automation representative.
Rockwell Automation tests all of its products to help ensure that they are fully operational when shipped from the
manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your
distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this
document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400