Reference Manual
Rockwell Automation Library of Process Objects:
Lead/Lag/Standby Motor Group (P_LLS)
Version 3.5
|
|
|
|
|
|
|
|
|
|
|
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 |
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
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).
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.
Preface
Lead/Lag/Standby Motor Group
(P_LLS)
Software Compatibility and Content Revisions . . . . . . . . . . . . . . . . . . . 5
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
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
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
3 |
Table of Contents
Notes:
4 |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
Software Compatibility and
Content Revisions
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.
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.
For general library considerations, see Rockwell Automation Library of Process
Objects, publication PROCES-RM002.
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 |
|
|
|
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
5 |
Preface
You can view or download publications at http:/www.rockwellautomation.com/literature/. To order paper copies of technical documentation, contact your local Allen-Bradley distributor or
Rockwell Automation sales representative.
6 |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
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.
Global Objects |
Faceplate |
|
Add-On Instruction
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.)
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
7 |
Lead/Lag/Standby Motor Group (P_LLS)
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.
The P_LLS instruction uses an array of structures of the type 'P_LLS_Motor' to interface to the motors. Each interface element in the array provides the signals that are required between the P_LLS instruction and one motor. Configuration data for the motor are also provided in the array. This data includes Priority and
Preference values that can be used to affect the sorting of the motors. A
Maintenance 'out of service' flag that removes a motor from consideration in the sort is also included. The interface also includes a 'user sort' value that can be used, for example, to push motors up or down the sort based on accumulated runtime or other criteria.
8 |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
Lead/Lag/Standby Motor Group (P_LLS)
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.
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
9 |
Lead/Lag/Standby Motor Group (P_LLS)
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.
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.
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. |
|
|
|
10 |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
|
|
|
Lead/Lag/Standby Motor Group (P_LLS) |
|
|
|
|
Table 3 - Visualization Files: Global Objects (.ggfx) |
|
|
|
|
|
|
|
FactoryTalk View SE Software |
|
FactoryTalk View ME Software |
Description |
|
|
|
|
(RA-BAS) P_LLS Graphics Library |
|
(RA-BAS-ME) P_LLS Graphics Library |
P_LLS global object device symbols used to build |
|
|
|
process graphics. |
|
|
|
|
(RA-BAS) Process Alarm Objects |
|
(RA-BAS-ME) Process Alarm Objects |
Global objects used for managing alarms on process |
|
|
|
object faceplates. |
|
|
|
|
(RA-BAS) Process Diagnostic Objects |
|
(RA-BAS-ME) Process Diagnostic Objects |
Diagnostic global objects used on process object |
|
|
|
faceplates. |
|
|
|
|
(RA-BAS) Process Faceplate Motor Objects |
|
(RA-BAS-ME) Process Faceplate Motor Objects |
Motor global objects used on process object faceplates. |
|
|
|
|
(RA-BAS) Process Help Objects |
|
(RA-BAS-ME) Process Help Objects |
Global objects used for all process objects help displays. |
|
|
|
|
(RA-BAS) Process Interlock Objects |
|
(RA-BAS-ME) Process Interlock Objects |
Global objects used for managing interlocks and |
|
|
|
permissives on process object faceplates. |
|
|
|
|
(RA-BAS) Process Mode Objects |
|
(RA-BAS-ME) Process Mode Objects |
Global objects used for managing modes 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. |
|
|
|
|
|
|
HMI Tags are created in a FactoryTalk View ME application to support tab |
|
|
|
switching on Process Library faceplates. The HMI tags may be imported via the |
|
|
|
comma-separated values file (.csv file type) in the following table. |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
11 |
Lead/Lag/Standby Motor Group (P_LLS)
Table 5 - Visualization Files: HMI Tags (.csv)
FactoryTalk View SE Software |
FactoryTalk View ME Software |
Description |
|
|
|
N/A |
FTVME_PlantPAxLib_Tags_3_5_xx.csv |
These tags must be imported into the |
|
where xx = the service release number. |
FactoryTalk View ME project to support switching tabs on |
|
|
any Process Object faceplate. |
|
|
|
In a FactoryTalk View SE application, a macro is a series of commands stored in a text file. In FactoryTalk View ME application, a macro is a list of tag assignments stored in a text file. The following table lists the Macros (.mcr file type) used by the Process Library.
Table 6 - Visualization Files: Macros (.mcr file)
FactoryTalk View SE Software |
FactoryTalk View ME Software |
Description |
|
|
|
NavToP_LLS_Motor |
N/A |
This macro must be imported into the FactoryTalk View SE |
|
|
project to support navigation to the Motor faceplate from |
|
|
the P_LLS faceplate. |
|
|
|
12 |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
Lead/Lag/Standby Motor Group (P_LLS)
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.
Table 7 - P_LLS Drive InOut Parameters
Tag Name |
Data Type |
|
Description |
|
|
|
|
Ref_Motors |
P_LLS_Motor |
|
Motor Interface Array (link to 2 to 30 motors) |
|
|
|
|
|
|
The number of motors is on Engineering Tab Page 2. The tag pointed to by |
|
|
|
Ref_Motors is used to interface between P_LLS and 2…30 motors. |
|
|
|
(See Engineering Tab Page 2 on page 48) sets the number of motors. |
|
|
|
In the following example, the interface tag is named 'MyP_LLS_Motors'. The |
|
|
|
type is an array of P_LLS_Motor structures. For each group of motors, create an |
|
|
|
interface array. Name its tag the same as the P_LLS instruction backing tag, plus |
|
|
|
'_Motors'. The array must have at least as many elements as there are motors in |
|
|
|
the group. |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
13 |
Lead/Lag/Standby Motor Group (P_LLS)
This tag is an array of parameter values that facilitates communications between P_LLS and an instance of P_Motor. The following table shows the contents of each member of the array.
Table 8 - Array Member Content
Name |
Data Type |
Description |
|
|
|
Inp_OtherSel |
DINT |
Other motor selection criteria (0...255) (input to LLS). |
|
|
|
Inp_Demote |
BOOL |
Demote this motor to bottom of list (for example, on high runtime) (input to LLS). |
|
|
|
Cfg_Prio |
DINT |
Motor priority in list (0...31 -- if unused, set to 0). |
|
|
|
Cfg_Pref |
DINT |
Motor preference in list (0...31), all else being equal. |
|
|
|
Cfg_NavTag |
STRING_NavTag |
Logix tag to navigate to for this motor (For example, P_Motor backing tag name). |
|
|
IMPORTANT: This tag does not work in FactoryTalk ME. |
|
|
|
PCmd_Start |
BOOL |
Program Command to start motor (output from LLS). |
|
|
|
PCmd_Stop |
BOOL |
Program Command to stop motor (output from LLS). |
|
|
|
PCmd_Acq |
BOOL |
Command to Acquire motor in Program mode (output from LLS). |
|
|
|
PCmd_Rel |
BOOL |
Command to Release motor from Program mode (output from LLS). |
|
|
|
MSet_OoS |
BOOL |
Maintenance setting to place motor Out of Service (input to LLS). |
|
|
|
Sts_Available |
BOOL |
Motor is in Program mode and ready to operate (input to LLS). |
|
|
|
Sts_Stopped |
BOOL |
Motor is confirmed stopped (input to LLS). |
|
|
|
Sts_Starting |
BOOL |
Motor is starting (input to LLS). |
|
|
|
Sts_Running |
BOOL |
Motor is confirmed running (input to LLS). |
|
|
|
Sts_Stopping |
BOOL |
Motor is stopping (input to LLS). |
|
|
|
The following image shows the relationship between P_LLS, Ref_Motors
(interface), and P_Motor.
14 |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
Lead/Lag/Standby Motor Group (P_LLS)
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). |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
15 |
Lead/Lag/Standby Motor Group (P_LLS)
Next, the motor logic is executed.
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.
16 |
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
Lead/Lag/Standby Motor Group (P_LLS)
Lead/Lag/Standby Motor Group Input Structure
Input parameters include the following:
•Input data elements (Inp_) are typically used to connect field inputs from I/O modules or signals from other objects.
•Configuration data elements (Cfg_) are used to set configurable capabilities and features of the instruction.
•Commands (PCmd_, OCmd_, MCmd_) are used by program logic, operators, and maintenance personnel to request instruction actions.
•Settings (PSet_, OSet_, MSet_) are used by program logic, operators, and maintenance personnel to establish runtime setpoints, thresholds, and so forth. A Setting (without a leading P, O, or M) establishes runtime settings regardless of role or mode.
Table 9 - P_LLS Input Parameters
Input Parameter |
Data |
Alias For |
Default |
Description |
|
|
Type |
|
|
|
|
|
|
|
|
|
|
EnableIn |
BOOL |
|
1 |
Enable Input - System Defined Parameter |
|
|
|
|
|
|
|
Inp_PermOK |
BOOL |
|
1 |
1 |
= Permissives OK, Group can start |
|
|
|
|
|
|
Inp_NBPermOK |
BOOL |
|
1 |
1 |
= Non-bypassable Permissives OK, Group can start |
|
|
|
|
|
|
Inp_IntlkOK |
BOOL |
|
1 |
1 |
= Interlocks OK, Group can start/run |
|
|
|
|
|
|
Inp_NBIntlkOK |
BOOL |
|
1 |
1 |
= Non-bypassable Interlocks OK, Group can start/run |
|
|
|
|
|
|
Inp_Hand |
BOOL |
Mode.Inp_Hand |
0 |
1 |
= Select Hand (hardwired) Control Strategy |
|
|
|
|
|
|
Inp_Ovrd |
BOOL |
Mode.Inp_Ovrd |
0 |
1 |
= Select Override control strategy |
|
|
|
|
|
|
Inp_OvrdDemand |
DINT |
|
0 |
Override Mode setting for number of motors to run (MinDemand..MaxDemand) |
|
|
|
|
|
|
|
Inp_OvrdCmd |
DINT |
|
0 |
Override Mode command: |
|
|
|
|
|
0 |
= None |
|
|
|
|
1 |
= Stop Group |
|
|
|
|
2 |
= Start Group |
|
|
|
|
3 |
= Rotate Assignments |
|
|
|
|
|
|
Inp_Reset |
BOOL |
|
0 |
1 |
= Reset all fault conditions and latched Alarms |
|
|
|
|
|
|
Cfg_NumMotors |
DINT |
|
3 |
Number of motors in this Lead / Lag / Standby Group (2…30) |
|
|
|
|
|
IMPORTANT: If the Ref_Motors interface array has fewer elements than the |
|
|
|
|
|
entered value, this value is reduced to the size of the array. |
|
|
|
|
|
|
|
Cfg_MaxDemand |
DINT |
|
2 |
Maximum number of motors to run (1…NumMotors) |
|
|
|
|
|
|
|
Cfg_MinDemand |
DINT |
|
0 |
Minimum number of motors to run (0…MaxDemand) |
|
|
|
|
|
|
|
Cfg_FirstOnFirstOff |
BOOL |
|
0 |
1 |
= First started is first stopped |
|
|
|
|
0 |
= First started is last stopped |
|
|
|
|
|
|
Cfg_AllowRotate |
BOOL |
|
1 |
1 |
= Allow Rotate ("cycle lead") command to rotate motor assignments |
|
|
|
|
|
|
Cfg_RotateOnStop |
BOOL |
|
1 |
1 |
= Rotate the lead to end of list upon stopping all motors |
|
|
|
|
|
|
Cfg_HasPermObj |
BOOL |
|
0 |
1 |
= Tells HMI a permissive object (for example, P_Perm) is used for Inp_PermOK |
|
|
|
|
and navigation to the permissive object faceplate is enabled. |
|
|
|
|
|
IMPORTANT: The name of the Permissive object in the controller must be the |
|
|
|
|
|
name of this object with the suffix ‘_Perm’. For example, if your P_LLS object has |
|
|
|
|
|
the name ’LLS123’, then its Permissive object must be named ‘LLS123_Perm’. |
|
|
|
|
|
|
|
Rockwell Automation Publication SYSLIB-RM054B-EN-P - February 2017 |
17 |