P Intlk 2.0 Syslib

Process Add-On Instructions and Graphics:
Interlocks with First-Out and Bypass (P_Intlk)
Compatible with the Plant-wide Integrated Architecture

Reference Manual
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 SGI-1.1 available from your local Rockwell Automation sales office
or online at http://literature.rockwellautomation.com) 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
IMPORTANT
ATTENTION
Identifies information about practices or circumstances that can cause an explosion in a

hazardous environment, which may lead to personal injury or death, property damage, or
economic loss.
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to personal injury or death,
property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, 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.
Allen-Bradley, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Summary of Changes
Introduction
This release of this document is updated throughout for version 2.0 of the
Interlocks with First-Out and Bypass (P_Intlk) Add-On Instruction and
Graphics. Please refer to the Release Notes that are distributed with version
2.0 of the Library.
Updated Information
This document contains the following changes:
iiiPublication SYSLIB-RM004C-EN-E - October 2011
Change:
See:
Version 2.0 of instruction
All
iii
Summary of Changes
Notes:
iv
Publication SYSLIB-RM004C-EN-E - October 2011
Table of Contents
Preface
Use of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Conventions and Related Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Set and Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Edge and Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Relay Ladder Rung Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Pre-Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Function Block States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Entering Text in FactoryTalk View SE. . . . . . . . . . . . . . . . . . . . . . xii
Chapter 1
Overview
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Primary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Revision Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2
Configuration Options
Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 3
Instruction Data Reference
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Inputs (Inp_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configurations (Cfg_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Program Commands (PCmd_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Device Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operator Commands, Maintenance Commands, Command Readies
(OCmd_, MCmd_, Rdy_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Device Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Device Commands Readies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Status (Sts_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 4
HMI Reference
Graphic Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Status and Bypass Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Using Graphics Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Interlock and Permissive Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table of Contents
Notes:
vi
SYSLIB-RM004C-EN-E - October 2011
Preface
Use of this Document
This document provides a programmer with details on the P_Intlk instruction

for a Logix-based controller. You should already be familiar with how the
Logix-based controller stores and processes data.
Novice programmers should read all the details about an instruction before
using the instruction. Experienced programmers can refer to the instruction
information to verify details.
Conventions and Related

Terms
Set and Clear

This manual uses set and clear to define the status of bits (booleans) and values
(non-booleans):
viiPublication SYSLIB-RM004C-EN-E - October 2011
This term:
Means:
Set
The bit is set to 1 (ON)

A value is set to any non-zero number
Clear
The bit is cleared to 0 (OFF)

All the bits in a value are cleared to 0
vii
Preface
Edge and Level

This manual uses Edge and Level to describe how bit (BOOL) Commands,
Settings, Configurations and Inputs to this instruction are sent by other logic
and processed by this instruction.
Send/Receive Method: Description:
Edge
Action is triggered by rising edge transition of input (0-1)

Separate inputs are provided for complementary functions
(such as enable and disable)
Sending logic SETS the bit (writes a 1) to initiate the
action; this instruction CLEARS the bit (to 0) immediately,
then acts on the request if possible
Ladder Diagram (LD): use conditioned OTL (Latch) to send
Structured Text (ST): use conditional assignment [if
(condition) then bit:=1;] to send
Function Block Diagram (FBD): OREF writes a 1 or 0 every
scan, should use Level, not Edge
Edge triggering allows multiple senders per Command,
Setting, Configuration or Input (many-to-one relationship)
Level
Action (enable) is triggered by input being at a level (in a

state, usually 1)
Opposite action (disable) is triggered by input being in
opposite state (0)
Sending logic SETS the bit (writes a 1) or CLEARS the bit
(writes a 0); this instruction does not change the bit
LD: use OTE (Energize) to send
ST: use unconditional assignment
[bit:= expression_resulting_in_1_or_0;] or
if-then-else logic [if (condition) then bit:= 1; else bit:= 0;]
FBD: use OREF to the input bit
Level triggering allows only one sender to drive each Level
input on the instruction (one-to-one relationship restriction)
IMPORTANT
viii
All Operator Commands (OCmd_) and Maintenance Commands

(MCmd_) are Edge triggered. The HMI Graphic Symbol or
faceplate SETS (writes a 1 to) each Command bit and the
Instruction CLEARS (writes a 0 to) the Command bit, then
performs the function, if possible.
Preface
IMPORTANT
This instruction has Program Commands (PCmd_) which are

selectable as Edge or Level, depending on the Configuration
Parameter Cfg_PCmdClear. If Cfg_PCmdClear is 1 (the default),
all Program Commands are CLEARED when received (edge). If
Cfg_PCmdClear is 0, Program Commands as noted in the
Instruction Data Reference become Level triggered, and
opposite functions are triggered by the primary Program
Command being CLEARED to 0.
Relay Ladder Rung Condition

The controller evaluates ladder instructions based on the rung condition
preceding the instruction (rung-in condition). Based on the rung-in condition
and the instruction, the controller sets the rung condition following the
instruction (rung-out condition), which in turn, affects any subsequent
instruction.
If the rung-in condition to an input instruction is true, the controller evaluates

the instruction and sets the rung-out condition based on the results of the
instruction. If the instruction evaluates to true, the rung-out condition is true;
if the instruction evaluates to false, the rung-out condition is false.
IMPORTANT
The rung-in condition is reflected in the EnableIn parameter and

determines how the system performs each Process Add-On
Instruction. If the EnableIn signal is TRUE, the system performs
the instructions main logic routine. Conversely, if the EnableIn
signal is FALSE, the system performs the instructions
EnableInFalse routine.
The instructions main logic routine sets/clears the EnableOut
parameter, which then determines the rung-out condition. The
EnableInFalse routine cannot set the EnableOut parameter. If
the rung-in condition is FALSE, then the EnableOut parameter
and the rung-out condition will also be FALSE.
ix
Preface
Pre-Scan
On transitions into RUN, the controller performs a pre-scan before the first
logic scan. Pre-scan is a special scan of all routines in the controller. The
controller scans all main routines and subroutines during pre-scan, but ignores
jumps that could skip the execution of instructions. The controller performs
all FOR loops and subroutine calls. If a subroutine is called more than once, it
is performed each time it is called. The controller uses pre-scan instructions to
reset non-retentive data values.
During pre-scan, input values are not current and outputs are not written. The
following conditions generate pre-scan:
toggle from Program to Run mode.
automatically enter Run mode from a power-up condition.
Pre-scan does not occur for a program when:
the program becomes scheduled while the controller is running.
the program is unscheduled when the controller enters Run mode.
IMPORTANT
The Pre-scan process performs the Process Add-On Instructions

logic routine as all FALSE and then performs its Pre-scan
routine as TRUE.
Function Block States

The controller evaluates function block instructions based on the state of
different conditions.
Possible Condition:
Description:
Pre-scan
Pre-scan for function block routines is the same as for relay

ladder routines. The only difference is that the Enableln
parameter for each function block instruction is cleared during
pre-scan.
Instruction first scan
Instruction first scan refers to the first time an instruction is

performed after pre-scan. The controller uses instruction first
scan to read current inputs and determine the appropriate
state to be in.
Instruction first run
Instruction first run refers to the first time the instruction

performs with a new instance of a data structure. The
controller uses instruction first run to generate coefficients
and other data stores that do not change for a function block
after initial download.
Preface
Every function block instruction also includes EnableIn and EnableOut

parameters.
If the EnableIn parameter is not wired, the instruction always performs as
normal and EnableIn remains set. If you clear EnableIn, it changes to set the
next time the instruction performs.
IMPORTANT
When programming in function block, restrict the range

of engineering units to 1015 because internal floating
point calculations are done using single precision floating
point. Engineering units outside of this range may result in
a loss of accuracy if results approach the limitations of
single precision floating point (1038).
xi
Preface
Entering Text in FactoryTalk View SE

When entering data into String Input fields in FactoryTalk View SE, the data is
not saved to the tag until the user presses the Enter key. When the Input Field
is enabled, its border changes based on the state of the input:
When the Input Field is Active (the cursor is in the field), the Input Field border is a
solid line.
EXAMPLE
If the user modifies the data in the input field and moves to a different field without
pressing the Enter key, the border remains a solid line indicating that the data has not
been saved to the tag.
EXAMPLE
If the data in the Input Field has not changed or has been written to the controller
tag, the border is a dashed line.
EXAMPLE
xii
Chapter
Overview
Functional Description
The Interlocks Add-On Instruction is used to collect (sum up) the Interlock
conditions which stop or de-energize a running or energized piece of
equipment or prevent it from starting or being energized. Interlocks are always
evaluated to de-energize equipment. For permissive conditions, those that
must be made to START the equipment but which are ignored once the
equipment is RUNNING, use the Permissives (P_Perm) Add-On Instruction.
Use when:
You have multiple interlock conditions or cascaded interlock conditions
(an interlock hierarchy) which stop some equipment (motor, valve,
drive) or keep it from starting. Link the conditions to P_Intlk Inputs,
and link the P_Intlk Status bits to the Inp_IntlkOK and
Inp_NBIntlkOK inputs of the equipment.
You need a first-out indication of which interlock condition shut down
the equipment.
You want configurable text descriptions of shutdown conditions and
other features of the P_Intlk faceplates.
Do NOT use when:
You have conditions that prevent starting equipment, but which are
ignored once the equipment is running. These are permissive, not
interlock conditions. Use the P_Perm Instruction instead.
You have only one interlock condition for the equipment. Connect the
condition directly to the interlock input on the device.
1Publication SYSLIB-RM004C-EN-E - October 2011
Chapter 1
Overview
Primary Operations
The primary operations of the P_Intlk Add-On Instruction and its faceplate
are:
Interlock Input OK Check: Each Input is compared with its
configured OK State. If the Input is not in its OK State, it raises an
Interlock Condition unless bypassed by Maintenance. See the Interlock
Bypass function, below.).
Interlock Condition Latching: If the Input is configured as Latched,
the Interlock Condition is latched in until Reset unless the Latch Defeat
Input is true. See the Latch Defeat function, below. If the Input is not
configured as Latched, the Interlock Condition clears when the Input
is again in its OK State.
Interlock Bypass: If the Input is configured as Bypassable and
Interlocks are bypassed, the Input does not raise an Interlock Condition,
even if it is not in its OK State. If the Input is configured as Not
Bypassable or if Interlocks are not bypassed, the Input raises an
Interlock Condition as described above.
First Out: If no Interlock Conditions are raised (OK to run), the first
Interlock Condition to be raised is marked as the First Out. If multiple
such Interlock Conditions are raised in the same scan, they are all
marked as First Out.
Overview
Chapter 1
Latch Defeat: A Latch Defeat function is provided to reduce the

number of Operator actions required to start equipment. The Latch
Defeat input should be set when the equipment is not running. When
the Latch Defeat input is true, the Latched configuration of Inputs is
ignored, and all Interlock Conditions clear when their corresponding
Inputs are in their OKStates. This saves the Operator having to Reset
before starting the equipment. When the equipment starts, the Latch
Defeat Input should be turned off. Then if an Interlock Condition
configured as Latched shuts down the equipment, it will be latched in
until Reset.
IMPORTANT
To prevent loss of information about what shut down the

equipment, the Latch Defeat Input is not processed until after
any Latched Interlocks (which occurred when Latch Defeat was
off) have been Reset.
Summary Status: The P_Intlk Add-On Instruction summarizes its 16

Interlock Input conditions into two primary Status bits: Sts_IntlkOK,
which indicates that all Interlock Conditions are clear (ready to run), and
Sts_NBIntlkOK, which indicates that all Non-Bypassable Interlock
Conditions are clear (ready to run if Interlocks are Bypassed).
IMPORTANT
Whether Interlocks are Bypassed or not is determined by the

downstream equipment instructions. The P_Intlk Instruction
simply provides the two summary Status bits. This two bits
should be wired or mapped to the equipment control logic.
Faceplate: The P_Intlk Add-On Instruction Faceplate displays the

Interlock Condition state of each input and whether it is Bypassed, and
shows the overall Interlock (summary) Status. The Engineering Tab of
the Faceplate allows setup of the P_Intlk Add-On Instruction OK State
configuration, Latch configuration, Bypassable configuration and the
text associated with each interlock condition input.
Operating Modes
The P_Intlk Add-On Instruction does not have Modes and does not contain a
P_Mode Instruction instance. The Operator and Program Reset Commands
for the Latched inputs are accepted at any time.
Chapter 1
Overview
Alarms
The P_Intlk Add-On Instruction does not generate any alarms. The individual
input conditions should be alarmed if necessary in other logic before they are
sent to the Inputs of the P_Intlk Instruction. In many applications, Status bits
from P_AIn Analog Input or P_DIn Discrete Input instructions are sent to
the P_Intlk inputs.
ATTENTION
Only use Alarm bits as Interlock conditions if you intend that the Interlock
condition be ignored when the corresponding Alarm is disabled or inhibited.
Execution
The following table explains the handling of instruction execution conditions.

Condition
Description
EnableIn False (False Rung)
Processing for EnableIn False (False Rung) is

handled by setting the summary All
Interlocks OK and All Non-Bypassable
Interlocks OK Status outputs to FALSE (0).
The individual Interlock bit Status and First
Out outputs are left in their last state.
Powerup (Pre-scan, First Scan)
The Latch and First Out states of the P_Intlk

Add-On Instruction are maintained through
a power-down / power-up or Run / Program
/ Run cycle.
Any Commands received before First Scan
are discarded.
Postscan (SFC Transition)
No SFC Postscan logic is provided.
Refer to Logix5000 Controllers Add-On Instructions Programming Reference

Manual, publication 1756-PM010, for more information on Add-On
Instruction execution condition handling.
Overview
Revision Compatibility
Chapter 1
The P_Intlk Add-On Instruction in RSLogix 5000 software and the Faceplate
in FactoryTalk View software are marked with revision information as shown
in the following table:.
Component
Example
The Add-On Instruction in RSLogix 5000 has

revision information visible when the
instruction is selected in the Controller
Organizer.
The Faceplate in FactoryTalk View has

revision information visible when the
pointer is paused just inside the lower
left-hand corner of the Faceplate when
called up on a running HMI Client.
The Instruction and Faceplate are compatible if they have the same Major and
Minor Revision numbers.
The Major Revision is the first number, before the period.
The Minor Revision is the second number, after the period and before the
hyphen or space.
Information after the hyphen or space indicates the Tweak Revision. The
Instruction and Faceplate do not have to have the same Tweak Revision to be
compatible.
In the table above, the Add-On Instruction and Faceplate shown are
compatible because they have the same Major.Minor (1.1).
Chapter 1
Overview
Notes:
Chapter
Configuration Parameters
Enter the appropriate values from the following table into the P_Intlk
Instructions configuration parameters to configure it for your application.
Use the RSLogix 5000 Tag Monitor function or the HMI Faceplate to set the
applicable configuration parameter(s).
Parameter:
Default:
Faceplate
Tab
Location:
Cfg_Desc
Interlocks with First Out
Engineering
Cfg_Label
Interlocks
Cfg_Tag
P_Intlk
Usage:
These Local Tags determine the text
displayed on the various graphic objects
and Faceplates for:
Associated
Parameters:
N/A
Description
Label (if used)
Tagname
Cfg_OKState
2#0000_0000_0000_0000
Engineering
Each bit determines whether the

corresponding input is OK to start in the 0
(cleared) state or the 1 (set) state.
Inp_Intlk00
Inp_Intlk01
Inp_Intlk02
Set the appropriate bit to make the

corresponding Input OK to run in the
1 state and not allow starting or
energizing the equipment in the 0
state.
IInp_Intlk03
Clear the appropriate bit to make the

corresponding Input OK to run in the
0 state and not allow starting or
energizing the equipment in the 1
state (default).
Inp_Intlk07
IMPORTANT
Inp_Intlk04
Inp_Intlk05
Inp_Intlk06
Inp_Intlk08
Inp_Intlk09
Inp_Intlk10
Inp_Intlk11
Inp_Intlk12
When cascading interlocks from a higher

level P_Intlk Instruction (e.g., from
area-wide interlocks to a single unit), wire
the two Interlock OK summary status bits
from the higher level P_Intlk instruction to
Inputs configured with their Cfg_OKState
bit set to 1.
Inp_Intlk13
Inp_Intlk14
Inp_Intlk15
Sts_IntlkOK
Sts_NBIntlkOK
Chapter 2
Parameter:
Default:
Faceplate
Tab
Location:
Cfg_Bypassable
2#0000_0000_0000_0000
Engineering
Associated
Parameters:
Usage:
corresponding input is a Bypassable or
Non-Bypassable Interlock.
corresponding Input a Bypassable
Interlock.
corresponding input a Non-Bypassable
interlock.
Inp_Intlk00
Inp_Intlk01
Inp_Intlk02
IInp_Intlk03
Inp_Intlk04
Inp_Intlk05
Inp_Intlk06
Inp_Intlk07
Inp_Intlk08
Inp_Intlk09
Inp_Intlk10
Inp_Intlk11
Inp_Intlk12
Inp_Intlk13
Inp_Intlk14
Inp_Intlk15
Sts_NBIntlkOK
Cfg_CondTxt[0]
Interlock 0
Cfg_CondTxt[1]
null (empty) STRING
Cfg_CondTxt[2]
null (empty) STRING
Engineering
Each 20-character string determines the

text displayed on the Interlocks Faceplate
for each of the 16 input conditions.
Inp_Intlk01
Inp_Intlk02
IMPORTANT
Inp_Intlk00
Inp_Intlk03
Cfg_CondTxt[3]
null (empty) STRING
Cfg_CondTxt[4]
null (empty) STRING
Cfg_CondTxt[5]
null (empty) STRING
Cfg_CondTxt[6]
null (empty) STRING
Cfg_CondTxt[7]
null (empty) STRING
Cfg_CondTxt[8]
null (empty) STRING
Cfg_CondTxt[9]
null (empty) STRING
Inp_Intlk09
Cfg_CondTxt[10]
null (empty) STRING
Inp_Intlk10
Cfg_CondTxt[11]
null (empty) STRING
Inp_Intlk11
Cfg_CondTxt[12]
null (empty) STRING
Inp_Intlk12
Cfg_CondTxt[13]
null (empty) STRING
Inp_Intlk13
Cfg_CondTxt[14]
null (empty) STRING
Inp_Intlk14
Cfg_CondTxt[15]
null (empty) STRING
Inp_Intlk15
Entering text in each Condition Text string

makes the text and the corresponding
status indicators visible on the Operator
faceplate. Enter a condition description
for each Interlock connected to this
instruction. If the Condition Text string is
empty (null string), the corresponding
status indicator is not displayed.
Inp_Intlk04
Inp_Intlk05
Inp_Intlk06
Inp_Intlk07
Inp_Intlk08
Parameter:
Default:
Faceplate
Tab
Location:
Cfg_Latched
2#0000_0000_0000_0000
Engineer
Usage:
corresponding input is a Latched or
Non-Latched Interlock.
Chapter 2
Associated
Parameters:
Inp_Intlk00
Inp_Intlk01
Inp_Intlk02

corresponding Input a Latched
Interlock. The operator or instruction
must issue a Reset command to clear
a latched interlock.
Inp_Intlk03

corresponding input a Non-Latched
interlock. This interlock type clears
when the instruction clears its
corresponding Input parameter.
Inp_Intlk07
Inp_Intlk04
Inp_Intlk05
Inp_Intlk06
Inp_Intlk08
Inp_Intlk09
Inp_Intlk10
Inp_Intlk11
Inp_Intlk12
Inp_Intlk13
Inp_Intlk14
Inp_Intlk15
Inp_Reset
OCmd_Reset
PCmd_Reset
Sts_Intlk
Cfg_PCmdClear
ON
Engineer
Set this parameter:

On to use Edge-triggered Program
Commands.
Off to use Level-triggered Program
Commands.
The Cfg_PCmdClear
parameter configures
all Program
Commands (PCmd_)
for either Level or
Edge triggering.
See the Edge and Level section in the

Preface for more information.
Chapter 2
Notes:
10
Chapter
This chapter describes the P_Intlk Instructions public parameters.

The descriptions in the tables below show how these data elements are used
with the P_Intlk Add-On Instruction.
Execution
Execution parameters are included with every Add-On Instruction. See the
Logix5000 Controllers Add-On Instructions Programming Reference Manual,
publication 1756-PM010, for more information on these data elements.
Name:
Data Type: Usage: Default:
EnableIn
BOOL
Input
Enable Input:
1 = Check Interlock Conditions.
0 = Set the Summary OK
Status bits to FALSE (0).
EnableOut
BOOL
Output
Enable Output: The EnableOut

signal is not manipulated by
this instruction. Its output
state always reflects the
EnableIn input state.
Style: Description:
Associated
Configuration
Parameter
11
Chapter 3
Inputs
(Inp_)
Input data elements are used to connect field inputs from I/O modules or
signals from other objects to the P_Intlk instruction. Each Input used should
have mapping logic or a function block wire to get the input value from the
input card or other instruction every scan.
Name:
Style:
Description:
Inp_Intlk00
BOOL
Level
Interlock Cond. 00
Stop if not in configured OK
state
Input
Associated
Configuration
Parameter
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[0]
Cfg_Latched
Inp_Intlk01
BOOL
Input
Level
Interlock Cond. 01
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[1]
Cfg_Latched
Inp_Intlk02
BOOL
Input
Level
Interlock Cond. 02
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[2]
Cfg_Latched
Inp_Intlk03
BOOL
Input
Level
Interlock Cond. 03
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[3]
Cfg_Latched
Inp_Intlk04
BOOL
Input
Level
Interlock Cond. 04
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[4]
Cfg_Latched
Inp_Intlk05
BOOL
Input
Level
Interlock Cond. 05
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[5]
Cfg_Latched
Inp_Intlk06
BOOL
Input
Level
Interlock Cond. 06
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[6]
Cfg_Latched
Inp_Intlk07
BOOL
Input
Level
Interlock Cond. 07
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[7]
Cfg_Latched
12
Name:
Style:
Description:
Inp_Intlk08
BOOL
Level
Interlock Cond. 08
state
Input
Chapter 3
Associated
Configuration
Parameter
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[8]
Cfg_Latched
Inp_Intlk09
BOOL
Input
Level
Interlock Cond. 09
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[9]
Cfg_Latched
Inp_Intlk10
BOOL
Input
Level
Interlock Cond. 10
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[10]
Cfg_Latched
Inp_Intlk11
BOOL
Input
Level
Interlock Cond. 11
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[11]
Cfg_Latched
Inp_Intlk12
BOOL
Input
Level
Interlock Cond. 12
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[12]
Cfg_Latched
Inp_Intlk13
BOOL
Input
Level
Interlock Cond. 13
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[13]
Cfg_Latched
Inp_Intlk14
BOOL
Input
Level
Interlock Cond. 14
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[14]
Cfg_Latched
Inp_Intlk15
BOOL
Input
Level
Interlock Cond. 15
state
Cfg_OKState
Cfg_Bypassable
Cfg_CondTxt[15]
Cfg_Latched
Inp_BypActive
BOOL
Input
Level
1 = Interlock bypassing is
currently active
Inp_LatchDefeat
BOOL
Input
Level
Latch Defeat
1 = Do not latch inputs even if
configured for latching
Inp_Reset
BOOL
Input
Level
1 = Reset Latched Interlocks

and First-Out
Cfg_OKState
Cfg_Latched
Cfg_OKState
Cfg_Latched
13
Chapter 3
Configurations
(Cfg_)
Configuration data elements are used to set configurable capabilities, features

and functions of the P_Intlk Instruction.
The following Configuration data may be modified using the Tag Monitor in
RSLogix 5000, using HMI Faceplates, or using logic in the controller
application.
Name:
Data Type:
Usage: Default:
Cfg_OKState
INT
Input
Style: Description:
2#0000_0000_0000_0000 Binary Bits indicate which state (0

or 1) of each input is OK to
run
Associated
Configuration
Parameter
Inp_Intlk00
Inp_Intlk01
Inp_Intlk02
IInp_Intlk03
Inp_Intlk04
Inp_Intlk05
Inp_Intlk06
Inp_Intlk07
Inp_Intlk08
Inp_Intlk09
Inp_Intlk10
Inp_Intlk11
Inp_Intlk12
Inp_Intlk13
Inp_Intlk14
Inp_Intlk15
Sts_IntlkOK
Sts_NBIntlkOK
Cfg_Latched
INT
Input
2#0000_0000_0000_0000 Binary Set bits indicate which

conditions are latched
(sealed in)
Cfg_Bypassable INT
Input
2#0000_0000_0000_0000 Binary Set bits indicate which

conditions can be bypassed
Cfg_PCmdClear BOOL
Input
14
Level
1 = Clear Program Commands

on receipt
0 = Leave Set
Chapter 3
Because they use arrayed or structured data types, the following Configuration
data elements use P_Intlk Add-On Instruction Local Tags. These may be
modified using RSLogix 5000 or using the HMI Faceplates, but cannot be
modified using controller logic.
Name:
Data Type:
Usage: Default:
Cfg_CondTxt
STRING_20[16]
Interlock 0 for Input 0;

condition text for inputs
1-15 default to empty
(null) strings
String
Short HMI description of

Interlock Conditions
Cfg_Tag
STRING_20
'P_Intlk'
String
Tagname for display on HMI
Cfg_Label
STRING_20
'Interlocks'
String
Label for Graphic Object

displayed on HMI
Cfg_Desc
STRING_40
'Interlocks with First Out
String
Description for display on

HMI
Style: Description:
Associated
Configuration
Parameter
15
Chapter 3
Program Commands
(PCmd_)
Program Command data elements are used by application logic to request

P_Intlk Instruction actions, such as changing Modes, acknowledging alarms,
or specific P_Intlk actions. Application logic sets the Program Command to 1
or 0 to request the action. (See the Edge and Level section in the Preface for
more information). The P_Intlk Instruction then performs the requested
action if it is in Program Mode and the action can be performed.
Device Commands
Name:
Style: Description:
PCmd_Reset
BOOL
Input
Associated
Configuration
Parameter
Program Command to Reset

Latched Interlocks
Cfg_Latched
Cfg_PCmdClear
* Primary Function:
If Cfg_PCmdClear = 0, triggered by Level = 1
If Cfg_PCmdClear = 1, triggered by rising Edge
* * Opposite Function:
If Cfg_PCmdClear = 0, triggered by primary function bit Level = 0 (this bit NOT USED)
If Cfg_PCmdClear = 1, triggered by rising Edge of this bit
16
Operator Commands,
Maintenance Commands,
Command Readies
(OCmd_, MCmd_, Rdy_)
Chapter 3
Operator Commands and Maintenance Commands are used by the operator at

the HMI to request instruction actions. These Commands are set (latched) by
the HMI and are read and then cleared (unlatched) and acted upon by the
P_Intlk instruction, allowing a many-to-one relationship between HMI
requestors and each Command. Commands are implemented as public Input
Parameters of the instruction.
Device Commands
Name:
Style: Description:
OCmd_Reset
BOOL
Edge
Input
Operator Command to Reset

Latched Interlocks
Associated
Configuration
Parameter
Cfg_Latched
Device Commands Readies

Each Operator or Maintenance Command has a corresponding Ready bit
which indicates whether the Command will be accepted and acted upon when
received. The Ready bit is used to enable (1) or gray-out (0) the Operator
Command button on the faceplate.
Name:
Data Type:
Usage: Default:
Rdy_Reset
BOOL
Output
Style: Description:
Associated
Configuration
Parameter
1 = Ready for OCmd_Reset

(enables HMI button)
17
Chapter 3
Status
(Sts_)
Status data elements contain process or device states, Mode status and Alarm
status. The HMI displays these Status points, and they are available for use by
other application logic.
Device Status
Name:
Sts_IntlkOK
BOOL
Output
Overall Interlock Status

1 = OK to run
0 = Stop
Sts_NBIntlkOK
BOOL
Output
Non-Bypassable Interlock
Status
1 = All Non-Bypassable
Interlocks OK to run
Sts_BypActive
BOOL
Output
Decimal
1 = Interlock Bypassing Active

(bypassable interlocks are
ignored)
Sts_Intlk
INT
Output
2#0000-0000-0000-0000
Binary
Individual Interlock Status

1 = Stop
0 = OK
Sts_FirstOut
INT
Output
2#0000-0000-0000-0000
Binary
Interlock First Out Status. A

set bit (= 1) indicates the first
not-OK condition
18
Style:
Description:
Associated
Configuration
Parameter
Cfg_Bypassable
Cfg_Latched
Chapter
HMI Reference
This chapter describes the Graphic Symbols and Faceplates provided

human-machine interface (HMI) for the P_Intlk Instruction.
Graphic Symbols
Graphic Symbols are provided for use on end-user process graphic displays.
Interlock Graphic Symbols have the following common attributes:
Status Indicator
Bypass Indicator
The Interlock Graphic Symbol displays the current summary state of the
interlocks and whether bypassable interlocks are bypassed. These indicators
are described in detail below.
The overall Graphic Symbol includes a touch field over it which calls up the
instructions Faceplate. In addition, pausing the pointing device over the
Graphic Symbol displays a tooltip describing the Symbols function.
19
Chapter 4
HMI Reference
Status and Bypass Indicators

The Status Indicator icon changes color and shape based on the state of the
interlock input conditions, and the Bypass Indicator shows whether bypassable
interlock conditions are currently being bypassed.
Background
Description
Not ready to run or energize. One or more
interlock conditions are not OK.
Ready to run or energize. Be aware that one
or more bypassable conditions are not OK,
but these conditions are bypassed. All
non-bypassable conditions are OK.
Ready to run or energize. All interlock
conditions are OK.
Ready to run or energize, and all interlock
conditions are OK, but be aware that
bypassable conditions are being bypassed
and will not shut down the equipment.
The P_Intlk instruction does not have Bypass commands - these are in the
associated device instruction. However, the equipments bypass status should
be connected to the P_Intlk Instructions Inp_BypActive input so the Graphic
Symbol and faceplate can display the equipments bypass state.
20
HMI Reference
Chapter 4
Using Graphics Symbols

The graphic symbol for P_Intlk can be found in the global object file
(RA-BAS) Process Graphics Library.ggfx. To use the graphic symbol, copy it
from the global object file and paste it in the display file. Next, right click on
the global object file in the display file and select Global Object Parameter
Values and the following window appears:
Enter the tag(s) in the Value column as specified in the Description column.
Note: Values for items marked (Optional) may be left blank.
Faceplate
The Interlock Faceplate consists of two tabbed pages. The Operator tab is
displayed when the Faceplate is initially called up. Click the appropriate icon at
the top of the screen to access a specific tab.
Stop
Engineering
Operator
Help
The Faceplate provides the means for Operators, Maintenance, Engineers and
others to interact with the P_Intlk Instruction instance, including viewing its
Status and manipulating it through its Commands and Configuration. When a
given input is restricted via Factory Talk View security, the required user
Security Code letter is shown in the tables that follow.
21
Chapter 4
HMI Reference
Operator Tab
Status Indicator
Condition OK
Reset Button
Condition Not OK
First-Out Indicator
22
HMI Reference
Chapter 4
Bypass Indicator
Condition Bypassed, Input OK
Condition Bypassed, Input Not OK
The Operator tab shows the following information:

A Status Indictor, identical to the one on the Graphic Symbol, showing
the current interlock state (all conditions met, non-bypassed conditions
met, or some conditions not met)
Interlock Bypass Status indicator
Each configured interlock along with the current state of the interlock.
The following table lists the functions on the Operator tab
Button
Action
Security
Required
Resets all latched interlocks
Code A
23
Chapter 4
HMI Reference
Engineering Tab
The Engineering tab is divided into two pages.
Engineering Tab Page 1
For each Interlock, the following items can be configured.
24
Button
Action
Security
Required
Description
A text description of the permissive set. It will

appear on the Title Bar of the Faceplate.
Code E
Label
A text description of the label.
Code E
Tag
A text description of the tag.
Code E
Clear Program
Commands on
Receipt
Select to clear Program Commands on Receipt.

See Edge and Level in the Preface for more
information.
Code E
HMI Reference
Chapter 4
Engineering Tab Page 2
The 16 interlock inputs are configured on the Engineering tab Page 2. For
each Interlock, the following can be configured:
Check Box / Field
Action
Security
Required
Descriptions
Code E
Enter a text description of each
permissive condition used. The
permissives with text entered will
appear on the Operator tab of the
Faceplate. If the text for a
condition is empty (null), that
permissive is not shown.
OK State
Code E
Selects which state of the
corresponding interlock is the OK
to Start state.
Can Bypass
Check this box to indicate that

the corresponding interlock may
be bypassed.
Code E
25
Chapter 4
HMI Reference
Check Box / Field
Action
Security
Required
Must Reset
Check this box to indicate that

the corresponding interlock must
be reset.
Code E
Interlock and Permissive Help
26
Rockwell Automation Support

Rockwell Automation provides technical information on the Web to assist you in using its products.
At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and
application notes, sample code and links to software service packs, and a MySupport feature that you can customize to
make the best use of these tools.
For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer
TechConnectSM support programs. For more information, contact your local distributor or Rockwell Automation
representative, or visit http://www.rockwellautomation.com/support/.
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/support/americas/phone_en.html, or contact your local Rockwell

Automation representative.
New Product Satisfaction Return

Rockwell Automation tests all of its products to 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 erenky, stanbul, Tel: +90 (216) 5698400
www.rockwel lautomation.com
Power, Control and Information Solutions Headquarters
Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.4444
Europe/Middle East/Africa: Rockwell Automation NV, Pegasus Park, De Kleetlaan 12a, 1831 Diegem, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640
Asia Pacific: Rockwell Automation, Level 14, Core F, Cyberport 3, 100 Cyberport Road, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846

Copyright 2011 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

P Intlk 2.0 Syslib

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

P Intlk 2.0 Syslib

Загружено:

Авторское право:

Доступные форматы

Process Add-On Instructions and Graphics:

Interlocks with First-Out and Bypass (P_Intlk)

Compatible with the Plant-wide Integrated Architecture

Important User Information

Identifies information about practices or circumstances that can cause an explosion in a

This document contains the following changes:

iiiPublication SYSLIB-RM004C-EN-E - October 2011

Version 2.0 of instruction

Publication SYSLIB-RM004C-EN-E - October 2011

Use of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Publication SYSLIB-RM004C-EN-E - October 2011

SYSLIB-RM004C-EN-E - October 2011

Use of this Document

This document provides a programmer with details on the P_Intlk instruction

Conventions and Related

Set and Clear

viiPublication SYSLIB-RM004C-EN-E - October 2011

The bit is set to 1 (ON)

The bit is cleared to 0 (OFF)

Edge and Level

Action is triggered by rising edge transition of input (0-1)

Action (enable) is triggered by input being at a level (in a

All Operator Commands (OCmd_) and Maintenance Commands

Publication SYSLIB-RM004C-EN-E - October 2011

This instruction has Program Commands (PCmd_) which are

Relay Ladder Rung Condition

If the rung-in condition to an input instruction is true, the controller evaluates

The rung-in condition is reflected in the EnableIn parameter and

Publication SYSLIB-RM004C-EN-E - October 2011

The Pre-scan process performs the Process Add-On Instructions

Function Block States

Pre-scan for function block routines is the same as for relay

Instruction first scan

Instruction first scan refers to the first time an instruction is

Instruction first run

Instruction first run refers to the first time the instruction

Publication SYSLIB-RM004C-EN-E - October 2011

Every function block instruction also includes EnableIn and EnableOut

Publication SYSLIB-RM004C-EN-E - October 2011

When programming in function block, restrict the range

Entering Text in FactoryTalk View SE

Publication SYSLIB-RM004C-EN-E - October 2011

1Publication SYSLIB-RM004C-EN-E - October 2011

Publication SYSLIB-RM004C-EN-E - October 2011

Latch Defeat: A Latch Defeat function is provided to reduce the

To prevent loss of information about what shut down the

Summary Status: The P_Intlk Add-On Instruction summarizes its 16

Whether Interlocks are Bypassed or not is determined by the

Faceplate: The P_Intlk Add-On Instruction Faceplate displays the

Publication SYSLIB-RM004C-EN-E - October 2011

The following table explains the handling of instruction execution conditions.

EnableIn False (False Rung)

Processing for EnableIn False (False Rung) is

Powerup (Pre-scan, First Scan)

The Latch and First Out states of the P_Intlk

Postscan (SFC Transition)

No SFC Postscan logic is provided.

Refer to Logix5000 Controllers Add-On Instructions Programming Reference

Publication SYSLIB-RM004C-EN-E - October 2011

The Add-On Instruction in RSLogix 5000 has

The Faceplate in FactoryTalk View has

Publication SYSLIB-RM004C-EN-E - October 2011

Publication SYSLIB-RM004C-EN-E - October 2011

Interlocks with First Out