Rockwell Automation 1794-Lxxxx User Manual
User Manual
PhaseManager User Manual
Catalog Numbers
with DriveLogix
1756 ControlLogix, 1769 CompactLogix, 1789 SoftLogix, 1794 FlexLogix, 20D PowerFlex 700S
Important User Information
Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety
Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication
your local Rockwell Automation sales office or online at
http://www.rockwellautomation.com/literature/) describes some
important differences between solid-state equipment and hard-wired electromechanical devices. Because of this difference,
and also because of the wide variety of uses for solid-state equipment, all persons responsible for applying this equipment
must satisfy themselves that each intended application of this equipment is acceptable.
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.
SGI-1.1 available from
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
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.
IMPORTANT
Allen-Bradley, Rockwell Software, Rockwell Automation, SoftLogix, FlexLogix, CompactLog ix, ControlLogix, DriveLogix, PhaseManager, Powerflex 700S, Logix5000, Logix5550, PLC -5, SLC 500, SoftLogix5800,
FactoryTalk Batch, RSLogix 5000, RSBizWare Batch, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Identifies information that is critical for successful application and understanding of the product.
Summary of Changes
Introduction
Updated Information
The release of this document contains new and updated information. To find
new and updated information, look for change bars, as shown next to this
paragraph.
This document contains the these changes.
Topic Page
Execution Guidelines 34
PXRQ Error Codes 86
3Publication LOGIX-UM001B-EN-P - April 2010 3
Summary of Changes
Notes:
4 Publication LOGIX-UM001B-EN-P - April 2010
Table of Contents
Preface
Introduction
PhaseManager Quick Start
When To Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Who Should Use This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
How To Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 1
PhaseManager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
State Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
State Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Manually Change State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Comparison of Other State Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2
Purpose of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Create an Equipment Phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Create a State Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Manually Step Through the States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configure the Initial State for an Equipment Phase. . . . . . . . . . . . . . . 22
Guidelines
Chapter 3
Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Equipment Model Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Example 1: Tank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Example 2: Smart Belt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
State Model Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
State Model Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Example 1: Add Water . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Example 2: Space Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Equipment Code Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Example 1: Add Water to a Tank . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Example 2: Smart Belt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Execution Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Example 1: Add Water to a Tank . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Example 2: Smart Belt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Transition Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Example 1: Tank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Example 2: Smart Belt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Example 3: Jam Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
State Completion Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Example 1: Add Water to a Tank . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Example 2: Smart Belt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Equipment Interface Tag Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5Publication LOGIX-UM001B-EN-P - April 2010 5
Table of Contents
Equipment Phase Instructions
(PSC, PCMD, POVR, PFL, PCLF, PX
RQ, PRNP, PPD, PATT, PDET)
Example 1: Add Water to a Tank . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Example 2: Smart Belt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Example 2: Smart belt, Continued . . . . . . . . . . . . . . . . . . . . . . . . . 52
Alias Tag Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Appendix A
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Set and Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Relay Ladder Rung Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Prescan of Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Choose an Equipment Phase Instruction . . . . . . . . . . . . . . . . . . . . . . . 58
Phase State Complete (PSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Equipment Phase Command (PCMD) . . . . . . . . . . . . . . . . . . . . . . . . . 62
Equipment Phase Override Command (POVR) . . . . . . . . . . . . . . . . . 67
Equipment Phase Failure (PFL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Equipment Phase Clear Failure (PCLF) . . . . . . . . . . . . . . . . . . . . . . . . 75
Equipment Phase External Request (PXRQ) . . . . . . . . . . . . . . . . . . . . 77
Equipment Phase New Parameters (PRNP). . . . . . . . . . . . . . . . . . . . . 88
Equipment Phase Paused (PPD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Attach to Equipment Phase (PATT). . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Detach from Equipment Phase (PDET) . . . . . . . . . . . . . . . . . . . . . . 101
PHASE Data Type
Configure an Equipment Phase
Glossary
Index
Appendix B
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Set and Clear Equipment Phase Tag Values . . . . . . . . . . . . . . . . . . . . 103
PHASE Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Appendix C
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Open the Configuration for an Equipment Phase . . . . . . . . . . . . . . . 109
Equipment Phase Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6 Publication LOGIX-UM001B-EN-P - April 2010
Preface
When To Use This Manual
To See
get started with a Logix5000 controller
program a Logix5000 controller—detailed and
comprehensive information
You are
here
• use equipment phases
• set up a state model for your equipment
• program in a way that is similar to S88 and
PackML models
program a specific Logix5000 programming
instruction
import or export a Logix5000 project or tags from or
to a text file
convert a PLC-5 or SLC 500 application to a
Logix5000 project
use a specific Logix5000 controller CompactLogix Controllers User manual, publication
The manual is one of various Logix5000 manuals.
Logix5000 Controllers Quick Start, publication 1756-QS001
Logix5000 Controllers Common Procedures, publication
1756-PM001
PhaseManager User Manual, publication
Logix5000 Controllers General Instructions Reference Manual,
publication
Logix5000 Controllers Process and Drives Instructions Reference
Manual, publication
Logix5000 Controllers Motion Instructions Refernce Manual,
publication
Logix5000 Controllers Import/Export Reference Manual,
publication
Converting PLC-5 or SLC 500 Logix to Logix5550 Logic Refernce
Manual, publication
1756-RM003
1756-RM006
MOTION-RM002
1756-RM084
1756-RM085
LOGIX-UM001
1769-UM007
ControlLogix System User Manual, publicaton
DriveLogix System 5720 User Manual, publication
DriveLogix5730 Controller for PowerFlex 700S Drives with
PhaseII Control User Manual, publication
FlexLogix Controllers User Manual, publication
SoftLogix5800 System User Manual, publication
control devices over an EtherNet/IP network EtherNet/IP Modules in Logix5000 Control Systems User
Manual, publication
control devices over an ControlNet network ControlNet Modules in Logix5000 Control Systems User Manual,
publication
control devices over an DeviceNet network DeviceNet Modules in Logix5000 Control Systems User Manual,
publication
CNET-UM001
DNET-UM004
ENET-UM001
1756-UM001
20D-UM002
20D-UM003
1794-UM001
1789-UM002
7Publication LOGIX-UM001B-EN-P - April 2010 7
Preface Preface
Purpose of This Manual
Who Should Use This Manual
This manual shows you how to set up and program a Logix5000 controller to
use equipment phases. It gives you guidance and examples to:
• lay-out your code in sections that include equipment phases.
• set up a state model for your equipment.
• program your equipment to run by the state model.
• use equipment phase instructions to transition to a different state,
handle faults, set up break points, and so forth.
A Logix5000 controller is any of the following:
• 1756 ControlLogix controllers
• 1769 CompactLogix controllers
• 1789 SoftLogix5800 controllers
• 1794 FlexLogix controllers
• 20D PowerFlex 700S with DriveLogix controllers
This manual is for those who program or maintain industrial automation
systems.
How To Use This Manual
To use this manual, you must already have experience with:
• programmable controllers.
• industrial automation systems.
• personal computers.
As you use this manual, text that is courier identifies information that you
must supply based on your application (a variable). For example, ‘Right-click
name_of_program ...’ means that you must identify the specific program in
your application. Typically, it is a name or variable that you have defined.
8 Publication LOGIX-UM001B-EN-P - April 2010
Introduction
Chapter 1
PhaseManager Overview
Controller
Controller Tags
Tasks
MainTask
Add_Water_Phase
Mix_Phase
Drain_Phase
Space_Parts_Phase
PhaseManager software lets you add equipment phases to your controller. An
equipment phase makes it easier to write, use, and manage the code for your
machine or equipment.
A PHASE tag gives you the status of an equipment phase.
An equipment phase directs 1 activity of your equipment.
A state model divides the activity into a set of states that have specific transitions.
Running State Routine
How to add
water
MainProgram
My_Equipment_Program
9Publication LOGIX-UM001B-EN-P - April 2010 9
Equipment phase instructions control the transitions between
states, handle faults, and so forth.
PSC POVR PCLF PRNP PATT
PCMD PFL PXRQ PPD PDET
Other code does the specific actions of your equipment
Water Feed
Conveyor Enable Axes
Chapter 1 Introduction
PhaseManager Terms
Term Description
equipment phase An equipment phase is similar to a program:
state model A state model divides the operating cycle of your equipment into a set of states. Each state
state machine The controller has an embedded state machine for the equipment phase. This makes it a lot
• you run the equipment phase in a task.
• you give the equipment phase a set of routines and tags.
An equipment phase is different from a program in these ways:
• The equipment phase uses a state model.
• Use an equipment phase to do 1 activity of your equipment.
is an instant in the operation of the equipment. It's the actions or conditions of the
equipment at a given time.
The state model of an equipment phase is similar to these state models:
• U.S. standard ISA S88.01-1995 and its IEC equivalent IEC 61512-1-1998, commonly
referred to as S88
• PackML, which was previously under the supervision of OMAC but is now a working
group within ISA
easier to use the state model. The state machine:
• calls the main routine (state routine) for an acting state.
• manages the transitions between states with minimal coding.
You code the transition conditions. When the conditions are true, the state machine
transitions the equipment to the next required state.
• makes sure that the equipment goes from state to state along an allowable path.
For example, if the equipment is in the Complete or Stopped state, the equipment phase
makes sure that it goes only to the Resetting state. This simplifies the amount of
interlocking that you have to do.
equipment phase instructions Specific instructions that you use to control an equipment phase. See
PHASE tag When you add an equipment phase, RSLogix 5000 programming software makes a tag for
the equipment phase. The tag uses the PHASE data type. Use the tag to:
• see which state the equipment phase is in.
• hold a failure code for the equipment phase.
• hold an index for your steps.
• hold the unit ID.
• see the status of an external request to FactoryTalk Batch software.
• see if FactoryTalk Batch software has new parameters for the equipment phase.
• set up producing and standby states.
See
Appendix B
for more information about the PHASE data type.
Appendix A
.
PhaseManager software helps you write the code for your equipment in a
structured way. This results in the same behavior for all the equipment across a
plant.
10 Publication LOGIX-UM001B-EN-P - April 2010
Introduction Chapter 1
PhaseManager Questions and Answers
Question Answer
How can I get the highest performance possible
from my equipment?
You have to measure equipment performance to improve it. The state model gives you a
way to measure the status of your equipment. With that data, you'll be able to calculate
the efficiency and performance measures that you want.
If you use PhaseManager software across your plant, you have consistent data from
equipment to equipment.
How can I cut the cost of integrating my
equipment into the plant?
Clear structure and consistent tags make it a lot easier to plug the equipment into your
plant and set up communication right away. Equipment up and down that line share
data using the same tag names. And all equipment communicates with higher-level
systems in the same way.
How can I make it easier to maintain the code? A state model helps you lay out the general functions of your equipment. We found that
the best programmers use a state model as the heart of their code. A state model serves
as a map for the code. With a clear structure, you'll know just where to look for the
piece of code that you want.
How can I give my operators a clean, intuitive
HMI?
A state model lets you make all your equipment behave the same. Your HMIs can then
show consistent equipment conditions across the plant. When an HMI says that the
equipment is idle, running, or holding, your operators will know exactly what that
means.
Publication LOGIX-UM001B-EN-P - April 2010 11
Chapter 1 Introduction
State Model Overview
Start
Idle
Running
A state model divides the operating cycle of your equipment into a series of
states. Each state is an instant in the operation of the equipment. It's the
actions or conditions of the equipment at a given time.
In a state model, you define what your equipment does under different
conditions, such as run, hold, stop, and so forth. You don’t need to use all the
states for your equipment. Use only the states that you want.
There are two types of states.
Type of State Description
Acting Does something or several things for a certain time or until
certain conditions are met. An acting state runs one time or
repeatedly.
Waiting Shows that certain conditions are met and the equipment is
waiting for the signal to go to the next state.
PhaseManager software uses the following states.
Hold
Holding
Held
Your equipment can go from any
state in the box to the stopping or
aborting state.
Resetting
Reset
Complete
Reset
Hold
Restart
Restarting
Stop
Abort
Stopping
Stopped Aborted
Aborting
Abort
Acting
Acting states represent the
things your equipment does at
a given time.
Waiting
Waiting states represent the
condition of your equipment
when it is in-between acting
states.
12 Publication LOGIX-UM001B-EN-P - April 2010
Introduction Chapter 1
One common objection to a state model is that it doesn't fit all equipment.
You may hear or think: ‘My equipment is very complex. There's a lot of
synchronization and many things happen in parallel.’
Keep in mind that a state model looks at your equipment at a very general
level. Different equipment does different things and needs specific code for
everything it does. A state model simply gives you a higher-level framework for
your code.
• The state model defines the general behavior, commands, and status of
the equipment.
• You program the details of the equipment within that framework.
Equipment States
The use of a state model may sound like a big change for programmers. But it's
simply a different way to look at the same control problem.
With a state model, you define the behavior of your equipment and put it into
a brief functional specification. In this way you show what happens and when
it happens.
For this State Ask
Stopped What happens when you turn on power?
Resetting How does the equipment get ready to run?
Idle How do you tell that the equipment is ready to run?
Running What does the equipment do to make product?
Holding How does the equipment temporarily stop making product without
making scrap?
Held How do you tell if the equipment is safely holding?
Restarting How does the equipment resume production after holding?
Complete How do you tell when the equipment is done with what it had to do?
Stopping What happens during an normal shutdown?
Aborting How does the equipment shutdown if a fault or failure happens?
Aborted How do you tell if the equipment is safely shutdown?
Publication LOGIX-UM001B-EN-P - April 2010 13
Chapter 1 Introduction
State Transitions
= transition
Command Done — No command. Use PSC instruction instead.
Start
Idle
Resetting
Running
The arrows in the state model show to which states your equipment can go
from the state it is in now.
• Each arrow is called a transition.
• A state model lets the equipment make only certain transitions. This
gives the equipment the same behavior as any other equipment that uses
the same model.
PhaseManager software uses the following transitions.
Hold
Holding
Hold
Restarting
Held
Restart
Your equipment can go from any
state in the box to the stopping or
aborting state.
Stop
Reset
Complete
Reset
Type of Transition Description
Command A command tells the equipment to start doing something or do something different. For example the
operator pushes the start button to start production and the stop button to shutdown.
PhaseManager software uses these commands:
reset stop restart
start hold abort
Done Equipment goes to a waiting state when it's done with what it's doing. You don’t give the equipment a
command. Instead, you set up your code to signal when the equipment is done. The waiting state
shows that the equipment is done.
Fault A fault tells you that something out of the ordinary has happened. You set up your code to look for
faults and take action if it finds any. Suppose you want your equipment to shut down as fast as
possible if a certain fault happens. In that case, set up your code look for that fault and give the abort
command if it finds it.
Stopping
Stopped Aborted
Abort
Abort
Aborting
Fault (specific use of the abort
command)
14 Publication LOGIX-UM001B-EN-P - April 2010
Introduction Chapter 1
Manually Change State
State that the equipment phase is in right now
RSLogix 5000 programming software has a window that lets you monitor and
command an equipment phase.
To manually change states.
1. Take ownership of the equipment phase.
2. Give a command.
Ownership
Ownership locks out programs or FactoryTalk Batch software from giving
commands to an equipment phase.
If this owns the equipment phase Then
RSLogix 5000 programming software Sequencers can’t give commands to the
equipment phase. This includes:
• Internal sequencer — program in the
controller.
• External sequencer — FactoryTalk Batch
software.
Internal sequencer — program in the
controller
External sequencer — FactoryTalk Batch
software
Other sequencers can’t give commands to the
equipment phase.
Other sequencers can’t give commands to the
equipment phase.
Exception: Use an Equipment Phase Override Command (POVR)
instruction to give a hold, stop, or abort command regardless of ownership.
Publication LOGIX-UM001B-EN-P - April 2010 15
Chapter 1 Introduction
Takes ownership
My Code
Can’t command
See the following for additional information.
• Equipment Phase Command (PCMD) instruction on
page 62.
• Equipment Phase Override Command (POVR) instruction on
• Attach to Equipment Phase (PATT) instruction on
Comparison of Other State Models
S88 PackML PhaseManager Software
Idle Starting Ready Resetting Idle
Running Complete Producing Running Complete
Pausing Paused Standby subroutines, breakpoints, or both.
Holding Held Holding Held Holding Held
Restarting none Restarting
Stopping Stopped Stopping Stopped Stopping Stopped
Aborting Aborted Aborting Aborted Aborting Aborted
The following table compares PhaseManager software’s state model to other
common state models.
page 97
.
page 68
.
16 Publication LOGIX-UM001B-EN-P - April 2010
PhaseManager Quick Start
Chapter 2
Purpose of This Chapter
Use this quick start to:
• get an introduction to how an equipment phase runs.
• monitor an equipment phase.
• manually tell an equipment phase to go to a different state.
Use this quick start when you want to:
• try out PhaseManager software for the first time.
• test an equipment phase by manually stepping through its states.
Topic Page
Create an Equipment Phase 18
Create a State Routine 18
Manually Step Through the States 19
Configure the Initial State for an Equipment Phase 22
Equipment
17Publication LOGIX-UM001B-EN-P - April 2010 17
To use this quick start, you need:
• a Logix5000 controller. See the preface if you aren’t sure which
controllers are Logix5000 controllers.
• firmware, revision 18.0 or later, for the controller
• a power supply for the controller
• a communication path to the controller:
– Communication card or built-in port
– Corresponding communication cable
• RSLogix 5000 programming software, version 18.0 or later
Chapter 2 PhaseManager Quick Start
2
3
Create an Equipment Phase
1.
.
.
Create a State Routine
1.
2.
3.
18 Publication LOGIX-UM001B-EN-P - April 2010
4.
PhaseManager Quick Start Chapter 2
Manually Step Through the States
Step Notes
1. Right-click the equipment phase and choose Monitor Equipment
Phase.
Before you do this procedure, do the following:
• Download the project to the controller.
• Put the controller in run or remote run mode.
2. Click the ownership button and then Yes—take ownership. This lets you use this window to step through the states.
Publication LOGIX-UM001B-EN-P - April 2010 19
Chapter 2 PhaseManager Quick Start
Step Notes
3. Click Start. • The equipment phase goes to the Running state.
• Any code in the Running state routine starts running. This is
where you put the code for the normal production sequence of
your equipment.
4. Click Stop. • The equipment phase goes to the Stopped state.
• The Running state routine stops running.
• The Stopping state routine is optional. Without it, the
equipment phase goes directly to the Stopped state.
20 Publication LOGIX-UM001B-EN-P - April 2010
Step Notes
PhaseManager Quick Start Chapter 2
5. Click Reset. • The equipment phase goes to the Idle state.
• The Resetting state routine is optional. Without it, the
equipment phase goes directly to the Idle state.
6. Click the ownership button. This releases the equipment phase from control by this window.
Publication LOGIX-UM001B-EN-P - April 2010 21
Chapter 2 PhaseManager Quick Start
3
4
2
Configure the Initial State for an Equipment Phase
1.
.
The initial state is the first state to which the equipment phase goes after
power up.
. Choose your initial state.
.
22 Publication LOGIX-UM001B-EN-P - April 2010
Guidelines
Chapter 3
Purpose of this chapter
To guide your development and programming of a Logix5000 project that
uses equipment phases
Use this chapter:
• before you lay-out the equipment phases for your Logix5000 project.
• as a reference while you program the project.
Review the following guidelines before you lay-out your project and refer back
to them as needed:
Topic Page
Equipment Model Guidelines 24
State Model Guidelines 26
Equipment Code Guidelines 31
Execution Guidelines 34
State Completion Guidelines 46
Transition Guidelines 40
Equipment Interface Tag Guidelines 48
Alias Tag Guidelines 53
23Publication LOGIX-UM001B-EN-P - April 2010 23
Chapter 3 Guidelines
Equipment Model
Each equipment phase is a specific activity that your equipment does. An
equipment phase tells the equipment what to do and when to do it.
Guidelines
Follow these guidelines to decide how many equipment phases to use.
Guideline Details
Make sure each equipment phase does
an independent activity.
Keep the number of equipment phases
and programs within the following limits.
List the equipment that goes along with
each equipment phase.
Make sure each equipment phase does an activity that is independent (relatively
independent) from other equipment. The equipment phase commands all the equipment that
works together to do the specific activity.
Example
This is probably an equipment
phase
• Fill bottles with product.
• Put bottles in carton.
• Add water to a tank.
• Mix ingredients in tank
If you have this controller You can have up to
ControlLogix 100 programs and equipment phases per task
SoftLogix 100 programs and equipment phases per task
FlexLogix 32 programs and equipment phases per task
CompactLogix 32 programs and equipment phases per task
Example
This equipment phase Relates this equipment
Add_Water water pump
Smart_Belt Coarse belt axis
This in probably NOT an equipment phase
• Accelerate filler axis (too small)
• Run bottling line (too big)
• Open water valve (too small)
• Brew ingredients (too big)
water valve
limit switch
Fine belt axis
Exit belt axis
24 Publication LOGIX-UM001B-EN-P - April 2010
tank completes these steps.
1. Adds water.
2. Heats the water.
3. Adds other ingredients.
4. Mixes all the ingredients.
5. Dispenses the finished
product.
Guidelines Chapter 3
Example 1: Tank
The following example shows the equipment phases for a tank that cooks
ingredients.
Which become these phases Which commands this equipmentTo cook the ingredients, the
Example 2: Smart Belt
The following example shows a smart belt. The smart belt does only one
activity. It spaces product evenly on an exit belt. Because it does only one
activity, it needs only 1 equipment phase.
Publication LOGIX-UM001B-EN-P - April 2010 25
Chapter 3 Guidelines
State Model Guidelines
A state model divides the operating cycle of your equipment into a series of
states. Each state is an instant in the operation of the equipment. It's the
actions or conditions of the equipment at a given time.
Follow these guidelines as you fill out the state model for an equipment phase.
Guideline Details
Fill out 1 state model for each phase. Each phase runs its own set of states. Fill out 1 state model worksheet for each phase.
Decide which state you want as your
initial state after power-up.
Which state do you want the equipment phase to go to when you turn on power?
ON
?
Idle
Resetting
Start
Running
Reset
Complete
Hold
Holding
Hold
Restarting
Stop
Stopping
Restart
Abort
Aborting
Held
Abort
Reset
An equipment phase goes to its initial state when you turn on power. We recommend that you
use one of these states as the initial state:
• Idle (default)
• Complete
• Stopped
Choose the initial state that best shows what your equipment is waiting to do after power-up
(reset, run, and so forth).
Stopped Aborted
26 Publication LOGIX-UM001B-EN-P - April 2010
Guidelines Chapter 3
Guideline Details
Start with the initial state and work
through the model.
Start with the initial state. Then work forward from that point. Use the following questions to
help you.
For this State Ask
Stopped What happens when you turn on power?
Resetting How does the equipment get ready to run?
Idle How do you tell that the equipment is ready to run?
Running What does the equipment do to make product?
Holding How does the equipment pause without making scrap?
Held How do you tell if the equipment is safely paused?
Restarting How does the equipment resume production after a pause?
Complete How do you tell when the equipment is done with what it had to do?
Stopping What happens during an normal shutdown?
Aborting How does the equipment shutdown if a fault or failure happens?
Aborted How do you tell if the equipment is safely shutdown?
Use only the states that you want. Define only the states that are appropriate for your equipment. You don’t need to use all the
states. The equipment phase just skips any states that you don’t add.
For the producing and standby states, use
subroutines.
If you want to define producing and standby states for your equipment, use subroutines.
A. Create a routines for the producing state and another routine for the standby state.
B. In the running state, check for the produce verses standby conditions. Set either the
Producing bit or the Standby bit of the equipment phase tag.
C. Use the Producing and Standby bits as conditions to call the corresponding routine.
See
Appendix B
.
Publication LOGIX-UM001B-EN-P - April 2010 27
Chapter 3 Guidelines
State Model Worksheet
IDLE
To
Done
RESETTING
Start
Command
RUNNING
Done
Equipment Phase:
Hold
Command
Done
HOLDING
RESTARTING
Done
HELD
Hold
Command
Restart
Command
Reset
Command
COMPLETE
Reset
Command
Command
STOPPING
Done
STOPPED
Stop
Abort
Command
Abort
Command
ABORTING
Done
ABORTED
Key
Waiting State Acting State
28 Publication LOGIX-UM001B-EN-P - April 2010
Guidelines Chapter 3
Example 1: Add Water
IDLE
· No water flow
· Tank Not full
· Operator can
control equipment
To
Done
RESETTING
Command
Start
RUNNING
· Lock equipment in
program control
· Add water
· Unlock equipment
from program
control
Done
Equipment Phase: Add Water
Hold
Command
Done
HOLDING
· Stop water
· Unlock equipment
from program
control
Hold
Command
RESTARTING
· Lock equipment in
program control
Done
HELD
· No water flow
· Operator can
control equipment
Restart
Command
Reset
Command
COMPLETE
· No water flow
· Water at high limit
· Operator can
control equipment
Reset
Command
Stop
Command
STOPPING
· Stop water
· Unlock equipment
from program
control
Done
STOPPED
· No water flow
· Operator can
control equipment
Abort
Command
Abort
Command
ABORTING
· Stop water
· Unlock equipment
from program
control
Done
ABORTED
· No water flow
· Operator can
control equipment
Key
Waiting State Acting State
Publication LOGIX-UM001B-EN-P - April 2010 29
Chapter 3 Guidelines
Example 2: Space Parts
IDLE
· No axes faults
· All axes = on
· Exit belt = homed
· Registration =
armed
· Clear axes faults
· Turn on all axes
· Home exit belt
· Arm registration
To
Done
RESETTING
Start
Command
RUNNING
· Jog exit belt
· Gear other belts
· Put 1 box on fine
belt
· Put 1 box on each
flight
Done
Equipment Phase: Space Parts
Hold
Command
Done
HOLDING
· Set speed of exit
belt = 0
Hold
Command
RESTARTING
· Jog exit belt
Done
HELD
· Speed of exit belt
=0
Restart
Command
Reset
Command
COMPLETE
Not used
Reset
Command
Stop
Command
STOPPING
· Run out boxes on
coarse belt
· Stop coarse and
fine belts
· Empty exit belt
· Stop exit belt
Done
STOPPED
· All axes = off
· SERCOS = phased
up
· All network
connections are
made
Abort
Command
Abort
Command
ABORTING
· Turn off all axes
Done
ABORTED
· All axes = off
· Boxes may still be
on belts
Key
Waiting State Acting State
30 Publication LOGIX-UM001B-EN-P - April 2010
Loading...