p intlk 2.0 syslib

8/20/2019 P Intlk 2.0 Syslib

1/40

Process Add-On Instructions and Graphics:

Interlocks with First-Out and Bypass (P_Intlk)

Reference Manual

Compatible with the Plant-wide Integrated Architecture™


2/40

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 officeor 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 applicationof this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements as-sociated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the ex-

amples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described inthis 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.

Allen-Bradley, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

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, oreconomic loss.

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

ATTENTIONIdentifies 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.


3/40

iiiPublication SYSLIB-RM004C-EN-E - October 2011 iii

Summary of Changes

Introduction This release of this document is updated throughout for version 2.0 of theInterlocks with First-Out and Bypass (P_Intlk) Add-On Instruction andGraphics. Please refer to the Release Notes that are distributed with version

2.0 of the Library.

Updated Information This document contains the following changes:

Change: See:

Version 2.0 of instruction All


4/40

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

Summary of Changes

Notes:


5/40

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

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 1Overview Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Primary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Revision Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2Configuration Options Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3Instruction 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 4HMI Reference Graphic Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Status and Bypass Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Using Graphics Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Interlock and Permissive Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

http://process%20aoi-dosews-summaryofchanges.pdf/http://process%20aoi-dosews-summaryofchanges.pdf/


6/40

vi SYSLIB-RM004C-EN-E - October 2011

Table of Contents

Notes:


7/40

viiPublication SYSLIB-RM004C-EN-E - October 2011 vii

Preface

Use of this Document This document provides a programmer with details on the P_Intlk instructionfor a Logix-based controller. You should already be familiar with how theLogix-based controller stores and processes data.

Novice programmers should read all the details about an instruction beforeusing the instruction. Experienced programmers can refer to the instructioninformation to verify details.

Conventions and RelatedTerms

Set and Clear

This manual uses set and clear to define the status of bits (booleans) and values(non-booleans):

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


8/40

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

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 theaction; 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 astate, usually 1)

• Opposite action (‘disable’) is triggered by input being inopposite 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 Levelinput on the instruction (one-to-one relationship restriction)

IMPORTANT All Operator Commands (OCmd_) and Maintenance Commands(MCmd_) are Edge triggered. The HMI Graphic Symbol orfaceplate SETS (writes a 1 to) each Command bit and theInstruction CLEARS (writes a 0 to) the Command bit, then

performs the function, if possible.


9/40

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

Preface

Relay Ladder Rung Condition

The controller evaluates ladder instructions based on the rung conditionpreceding the instruction (rung-in condition). Based on the rung-in condition

and the instruction, the controller sets the rung condition following theinstruction (rung-out condition), which in turn, affects any subsequentinstruction.

If the rung-in condition to an input instruction is true, the controller evaluatesthe instruction and sets the rung-out condition based on the results of theinstruction. 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 This instruction has Program Commands (PCmd_) which areselectable as Edge or Level, depending on the ConfigurationParameter 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 theInstruction Data Reference become Level triggered, andopposite functions are triggered by the primary ProgramCommand being CLEARED to 0.

IMPORTANT The rung-in condition is reflected in the EnableIn parameter anddetermines how the system performs each Process Add-OnInstruction. If the EnableIn signal is TRUE, the system performsthe instruction’s main logic routine. Conversely, if the EnableInsignal is FALSE, the system performs the instruction’sEnableInFalse routine.

The instruction’s main logic routine sets/clears the EnableOutparameter, which then determines the rung-out condition. TheEnableInFalse routine cannot set the EnableOut parameter. Ifthe rung-in condition is FALSE, then the EnableOut parameterand the rung-out condition will also be FALSE.


10/40

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

Preface

Pre-Scan

On transitions into RUN, the controller performs a pre-scan before the firstlogic 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 ignoresjumps that could skip the execution of instructions. The controller performsall FOR loops and subroutine calls. If a subroutine is called more than once, itis performed each time it is called. The controller uses pre-scan instructions toreset non-retentive data values.

During pre-scan, input values are not current and outputs are not written. Thefollowing 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.

Function Block States

The controller evaluates function block instructions based on the state ofdifferent conditions.

IMPORTANT The Pre-scan process performs the Process Add-On Instruction’slogic routine as all FALSE and then performs its Pre-scanroutine as TRUE.

Possible Condition: Description:

Pre-scan Pre-scan for function block routines is the same as for relayladder routines. The only difference is that the Enablelnparameter for each function block instruction is cleared duringpre-scan.

Instruction first scan Instruction first scan refers to the first time an instruction isperformed after pre-scan. The controller uses instruction firstscan to read current inputs and determine the appropriatestate to be in.

Instruction first run Instruction first run refers to the first time the instructionperforms with a new instance of a data structure. Thecontroller uses instruction first run to generate coefficientsand other data stores that do not change for a function blockafter initial download.


11/40

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

Preface

Every function block instruction also includes EnableIn and EnableOutparameters.

If the EnableIn parameter is not wired, the instruction always performs asnormal and EnableIn remains set. If you clear EnableIn, it changes to set thenext time the instruction performs.

IMPORTANT When programming in function block, restrict the range

of engineering units to ±10±15 because internal floatingpoint calculations are done using single precision floatingpoint. Engineering units outside of this range may result ina loss of accuracy if results approach the limitations of

single precision floating point (±10±38 ).


12/40

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

Preface

Entering Text in FactoryTalk View SE

When entering data into String Input fields in FactoryTalk View SE, the data isnot 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.

• 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.

• 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

EXAMPLE

EXAMPLE


13/40

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

Chapter 1

Overview

Functional Description The Interlocks Add-On Instruction is used to collect (‘sum up’) the Interlockconditions which stop or de-energize a running or energized piece ofequipment or prevent it from starting or being energized. Interlocks are alwaysevaluated to de-energize equipment. For ‘permissive’ conditions, those thatmust be made to START the equipment but which are ignored once theequipment 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 andInp_NBIntlkOK inputs of the equipment.

• You need a first-out indication of which interlock condition shut downthe equipment.

• You want configurable text descriptions of shutdown conditions andother features of the P_Intlk faceplates.

Do NOT use when:

• You have conditions that prevent starting equipment, but which areignored once the equipment is running. These are permissive, notinterlock conditions. Use the P_Perm Instruction instead.

• You have only one interlock condition for the equipment. Connect thecondition directly to the interlock input on the device.


14/40

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

Chapter 1 Overview

Primary Operations The primary operations of the P_Intlk Add-On Instruction and its faceplateare:

• Interlock Input OK Check : Each Input is compared with its

configured ‘OK State’. If the Input is not in its OK State, it raises anInterlock Condition unless bypassed by Maintenance. See the InterlockBypass function, below.).

• Interlock Condition Latching: If the Input is configured as ‘Latched’,the Interlock Condition is latched in until Reset unless the Latch DefeatInput is true. See the Latch Defeat function, below. If the Input is notconfigured as ‘Latched’, the Interlock Condition clears when the Inputis again in its OK State.

• Interlock Bypass: If the Input is configured as ‘Bypassable’ andInterlocks 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 ‘NotBypassable’ or if Interlocks are not bypassed, the Input raises anInterlock Condition as described above.

• First Out: If no Interlock Conditions are raised (OK to run), the firstInterlock Condition to be raised is marked as the First Out. If multiplesuch Interlock Conditions are raised in the same scan, they are allmarked as First Out.


15/40

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

Overview Chapter 1

• Latch Defeat: A Latch Defeat function is provided to reduce thenumber of Operator actions required to start equipment. The LatchDefeat input should be set when the equipment is not running. Whenthe Latch Defeat input is true, the ‘Latched’ configuration of Inputs isignored, and all Interlock Conditions clear when their correspondingInputs are in their ‘OK’States. This saves the Operator having to Resetbefore starting the equipment. When the equipment starts, the LatchDefeat Input should be turned off. Then if an Interlock Conditionconfigured as ‘Latched’ shuts down the equipment, it will be latched inuntil Reset.

• Summary Status: The P_Intlk Add-On Instruction summarizes its 16Interlock Input conditions into two primary Status bits: Sts_IntlkOK, which indicates that all Interlock Conditions are clear (ready to run), andSts_NBIntlkOK, which indicates that all Non-Bypassable Interlock

Conditions are clear (ready to run if Interlocks are Bypassed).

• Faceplate: The P_Intlk Add-On Instruction Faceplate displays theInterlock Condition state of each input and whether it is Bypassed, andshows the overall Interlock (summary) Status. The Engineering Tab ofthe Faceplate allows setup of the P_Intlk Add-On Instruction OK Stateconfiguration, Latch configuration, Bypassable configuration and thetext associated with each interlock condition input.

Operating Modes The P_Intlk Add-On Instruction does not have Modes and does not contain aP_Mode Instruction instance. The Operator and Program ‘Reset’ Commands

for the Latched inputs are accepted at any time.

IMPORTANT To prevent loss of information about what shut down theequipment, the Latch Defeat Input is not processed until afterany Latched Interlocks (which occurred when Latch Defeat wasoff) have been Reset.

IMPORTANT Whether Interlocks are Bypassed or not is determined by thedownstream equipment instructions. The P_Intlk Instructionsimply provides the two summary Status bits. This two bitsshould be wired or mapped to the equipment control logic.


16/40


Chapter 1 Overview

Alarms The P_Intlk Add-On Instruction does not generate any alarms. The individualinput conditions should be alarmed if necessary in other logic before they aresent to the Inputs of the P_Intlk Instruction. In many applications, Status bitsfrom P_AIn Analog Input or P_DIn Discrete Input instructions are sent tothe P_Intlk inputs.

ATTENTION

Only use Alarm bits as Interlock conditions if you intend that the Interlockcondition be ignored when the corresponding Alarm is disabled or inhibited.

ExecutionThe following table explains the handling of instruction execution conditions.

Refer to Logix5000 Controllers Add-On Instructions Programming ReferenceManual, publication 1756-PM010, for more information on Add-OnInstruction execution condition handling.

Condition Description

EnableIn False (False Rung) Processing for EnableIn False (False Rung) ishandled by setting the summary ‘AllInterlocks OK’ and ‘All Non-BypassableInterlocks OK’ Status outputs to FALSE (0).The individual Interlock bit Status and FirstOut outputs are left in their last state.

Powerup (Pre-scan, First Scan) The Latch and First Out states of the P_IntlkAdd-On Instruction are maintained througha power-down / power-up or Run / Program / Run cycle.

Any Commands received before First Scanare discarded.

Postscan (SFC Transition) No SFC Postscan logic is provided.

http://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdf


17/40


Overview Chapter 1

Revision Compatibility The P_Intlk Add-On Instruction in RSLogix 5000 software and the Faceplatein FactoryTalk View software are marked with revision information as shownin the following table:.

The Instruction and Faceplate are compatible if they have the same Major andMinor Revision numbers.

The Major Revision is the first number, before the period.

The Minor Revision is the second number, after the period and before thehyphen or space.

Information after the hyphen or space indicates the Tweak Revision. TheInstruction and Faceplate do not have to have the same Tweak Revision to becompatible.

In the table above, the Add-On Instruction and Faceplate shown arecompatible because they have the same Major.Minor (1.1).

Component Example

The Add-On Instruction in RSLogix 5000 hasrevision information visible when theinstruction is selected in the ControllerOrganizer.

The Faceplate in FactoryTalk View hasrevision information visible when thepointer is paused just inside the lowerleft-hand corner of the Faceplate whencalled up on a running HMI Client.


18/40


Chapter 1 Overview

Notes:


19/40


Chapter 2

Configuration Options

Configuration Parameters Enter the appropriate values from the following table into the P_IntlkInstruction’s configuration parameters to configure it for your application.

Use the RSLogix 5000 Tag Monitor function or the HMI Faceplate to set theapplicable configuration parameter(s).

Parameter: Default:

FaceplateTabLocation: Usage:

AssociatedParameters:

Cfg_Desc

Cfg_Label

Cfg_Tag

’Interlocks with First Out’

’Interlocks’

‘P_Intlk’

Engineering These Local Tags determine the textdisplayed on the various graphic objectsand Faceplates for:

• Description

• Label (if used)

• Tagname

N/A

Cfg_OKState 2#0000_0000_0000_0000 Engineering Each bit determines whether thecorresponding input is OK to start in the 0(cleared) state or the 1 (set) state.

• Set the appropriate bit to make thecorresponding Input ‘OK to run’ in the1 state and not allow starting orenergizing the equipment in the 0state.

• Clear the appropriate bit to make thecorresponding Input ‘OK to run’ in the0 state and not allow starting orenergizing the equipment in the 1state (default).

IMPORTANT

When cascading interlocks from a higherlevel P_Intlk Instruction (e.g., fromarea-wide interlocks to a single unit), wirethe two ‘Interlock OK’ summary status bitsfrom the higher level P_Intlk instruction toInputs configured with their Cfg_OKStatebit set to 1.

• 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


20/40


Chapter 2 Configuration Options

Cfg_Bypassable 2#0000_0000_0000_0000 Engineering Each bit determines whether the

corresponding input is a Bypassable orNon-Bypassable Interlock.

• Set the appropriate bit to make thecorresponding Input a BypassableInterlock.

• Clear the appropriate bit to make thecorresponding input a Non-Bypassableinterlock.

• Inp_Intlk00

• Inp_Intlk01• Inp_Intlk02

• IInp_Intlk03

• Inp_Intlk04

• Inp_Intlk05

• Inp_Intlk06

• Inp_Intlk07

• Inp_Intlk08

• Inp_Intlk09

• Inp_Intlk10


• Inp_Intlk13

• Inp_Intlk14

• Inp_Intlk15

• Sts_NBIntlkOK

Cfg_CondTxt[0] ’Interlock 0’ Engineering Each 20-character string determines thetext displayed on the Interlocks’ Faceplatefor each of the 16 input conditions.

IMPORTANT

Entering text in each Condition Text stringmakes the text and the correspondingstatus indicators visible on the Operatorfaceplate. Enter a condition descriptionfor each Interlock connected to thisinstruction. If the Condition Text string isempty (null string), the correspondingstatus indicator is not displayed.

• Inp_Intlk00

Cfg_CondTxt[1] null (empty) STRING • Inp_Intlk01















Parameter: Default:




21/40


Configuration Options Chapter 2

Cfg_Latched 2#0000_0000_0000_0000 Engineer Each bit determines whether the

corresponding input is a Latched orNon-Latched Interlock.

• Set the appropriate bit to make thecorresponding Input a LatchedInterlock. The operator or instructionmust issue a Reset command to cleara latched interlock.

• Clear the appropriate bit to make thecorresponding input a Non-Latchedinterlock. This interlock type clearswhen the instruction clears itscorresponding Input parameter.

• Inp_Intlk00


• Inp_Intlk03

• Inp_Intlk04

• Inp_Intlk05

• Inp_Intlk06

• Inp_Intlk07

• Inp_Intlk08

• Inp_Intlk09

• Inp_Intlk10


• 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 ProgramCommands.

• Off to use Level-triggered ProgramCommands.

See the Edge and Level section in thePreface for more information.

The Cfg_PCmdClear

parameter configuresall ProgramCommands (PCmd_) for either Level orEdge triggering.

Parameter: Default:




22/40


Chapter 2 Configuration Options

Notes:


23/40


Chapter 3

Instruction Data Reference

This chapter describes the P_Intlk Instruction’s 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 theLogix5000 Controllers Add-On Instructions Programming Reference Manual,publication 1756-PM010, for more information on these data elements.

Name: Data Type: Usage: Default: Style: Description:

AssociatedConfigurationParameter

EnableIn BOOL Input 1 Enable Input:1 = Check Interlock Conditions.0 = Set the Summary OK

Status bits to FALSE (0).

EnableOut BOOL Output 0 Enable Output: The EnableOutsignal is not manipulated bythis instruction. Its outputstate always reflects the

EnableIn input state.

http://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdf


24/40


Chapter 3 Instruction Data Reference

Inputs (Inp_)

Input data elements are used to connect field inputs from I/O modules orsignals from other objects to the P_Intlk instruction. Each Input used shouldhave mapping logic or a function block wire to get the input value from theinput card or other instruction every scan.



Inp_Intlk00 BOOL Input 0 Level Interlock Cond. 00Stop if not in configured OKstate

• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[0]

• Cfg_Latched

Inp_Intlk01 BOOL Input 0 Level Interlock Cond. 01 Stop if not in configured OKstate

• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[1]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[2]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[3]

• Cfg_Latched

Inp_Intlk04 BOOL Input 0 Level Interlock Cond. 04

Stop if not in configured OKstate

• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[4]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[5]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[6]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[7]

• Cfg_Latched


25/40


Instruction Data Reference Chapter 3


• Cfg_OKState

• Cfg_Bypassable• Cfg_CondTxt[8]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[9]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[10]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[11]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[12]

• Cfg_Latched

Inp_Intlk13 BOOL Input 0 Level Interlock Cond. 13

Stop if not in configured OKstate

• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[13]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[14]

• Cfg_Latched


• Cfg_OKState

• Cfg_Bypassable

• Cfg_CondTxt[15]

• Cfg_Latched

Inp_BypActive BOOL Input 0 Level 1 = Interlock bypassing iscurrently active

Inp_LatchDefeat BOOL Input 0 Level Latch Defeat1 = Do not latch inputs even if

configured for latching

• Cfg_OKState

• Cfg_Latched

Inp_Reset BOOL Input 0 Level 1 = Reset Latched Interlocksand First-Out

• Cfg_OKState

• Cfg_Latched




26/40



Configurations (Cfg_)

Configuration data elements are used to set configurable capabilities, featuresand functions of the P_Intlk Instruction.

The following Configuration data may be modified using the Tag Monitor inRSLogix 5000, using HMI Faceplates, or using logic in the controllerapplication.



Cfg_OKState INT Input 2#0000_0000_0000_0000 Binary Bits indicate which state (0or 1) of each input is OK torun

• 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 whichconditions are latched(sealed in)

Cfg_Bypassable INT Input 2#0000_0000_0000_0000 Binary Set bits indicate whichconditions can be bypassed

Cfg_PCmdClear BOOL Input 1 Level 1 = Clear Program Commandson receipt

0 = Leave Set


27/40



Because they use arrayed or structured data types, the following Configurationdata elements use P_Intlk Add-On Instruction Local Tags. These may bemodified using RSLogix 5000 or using the HMI Faceplates, but cannot bemodified using controller logic.



Cfg_CondTxt STRING_20[16] ’Interlock 0’ for Input 0;condition text for inputs1-15 default to empty(null) strings

String Short HMI description ofInterlock Conditions

Cfg_Tag STRING_20 'P_Intlk' String Tagname for display on HMI

Cfg_Label STRING_20 'Interlocks' String Label for Graphic Objectdisplayed on HMI

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

HMI


28/40



Program Commands(PCmd_)

Program Command data elements are used by application logic to requestP_Intlk Instruction actions, such as changing Modes, acknowledging alarms,or specific P_Intlk actions. Application logic sets the Program Command to 1or 0 to request the action. (See the Edge and Level section in the Preface formore information). The P_Intlk Instruction then performs the requestedaction if it is in Program Mode and the action can be performed.

Device Commands

* 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



PCmd_Reset BOOL Input 0 * Program Command to ResetLatched Interlocks

• Cfg_Latched

• Cfg_PCmdClear


29/40



Operator Commands, Maintenance Commands, Command Readies

(OCmd_, MCmd_, Rdy_)

Operator Commands and Maintenance Commands are used by the operator atthe HMI to request instruction actions. These Commands are set (latched) bythe HMI and are read and then cleared (unlatched) and acted upon by theP_Intlk instruction, allowing a many-to-one relationship between HMIrequestors and each Command. Commands are implemented as public InputParameters of the instruction.

Device Commands

Device Commands Readies

Each Operator or Maintenance Command has a corresponding Ready bit which indicates whether the Command will be accepted and acted upon whenreceived. The Ready bit is used to enable (1) or gray-out (0) the OperatorCommand button on the faceplate.



OCmd_Reset BOOL Input 0 Edge Operator Command to ResetLatched Interlocks

• Cfg_Latched


Associated

ConfigurationParameter

Rdy_Reset BOOL Output 0 1 = Ready for OCmd_Reset(enables HMI button)


30/40



Status (Sts_)

Status data elements contain process or device states, Mode status and Alarmstatus. The HMI displays these Status points, and they are available for use byother application logic.

Device Status



Sts_IntlkOK BOOL Output 1 Overall Interlock Status1 = OK to run 0 = Stop

Sts_NBIntlkOK BOOL Output 1 Non-Bypassable InterlockStatus

1 = All Non-BypassableInterlocks OK to run

• Cfg_Bypassable

Sts_BypActive BOOL Output 0 Decimal 1 = Interlock Bypassing Active(bypassable interlocks areignored)

Sts_Intlk INT Output 2#0000-0000-0000-0000 Binary Individual Interlock Status1 = Stop 0 = OK

• Cfg_Latched

Sts_FirstOut INT Output 2#0000-0000-0000-0000 Binary Interlock First Out Status. Aset bit (= 1) indicates the firstnot-OK condition


31/40


Chapter 4

HMI Reference

This chapter describes the Graphic Symbols and Faceplates providedhuman-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:

The Interlock Graphic Symbol displays the current summary state of theinterlocks and whether bypassable interlocks are bypassed. These indicatorsare described in detail below.

The overall Graphic Symbol includes a touch field over it which calls up theinstruction’s Faceplate. In addition, pausing the pointing device over theGraphic Symbol displays a tooltip describing the Symbol’s function.

Status Indicator Bypass Indicator


32/40


Chapter 4 HMI Reference

Status and Bypass Indicators

The Status Indicator icon changes color and shape based on the state of theinterlock input conditions, and the Bypass Indicator shows whether bypassable

interlock conditions are currently being bypassed.

The P_Intlk instruction does not have Bypass commands - these are in theassociated device instruction. However, the equipment’s bypass status shouldbe connected to the P_Intlk Instruction’s Inp_BypActive input so the GraphicSymbol and faceplate can display the equipment’s bypass state.

Background Description

Not ready to run or energize. One or moreinterlock conditions are not OK.

Ready to run or energize. Be aware that oneor more bypassable conditions are not OK,but these conditions are bypassed. Allnon-bypassable conditions are OK.

Ready to run or energize. All interlockconditions are OK.

Ready to run or energize, and all interlockconditions are OK, but be aware thatbypassable conditions are being bypassedand will not shut down the equipment.


33/40


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 onthe 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 isdisplayed when the Faceplate is initially called up. Click the appropriate icon atthe top of the screen to access a specific tab.

The Faceplate provides the means for Operators, Maintenance, Engineers andothers to interact with the P_Intlk Instruction instance, including viewing itsStatus and manipulating it through its Commands and Configuration. When agiven input is restricted via Factory Talk View security, the required userSecurity Code letter is shown in the tables that follow.

Operator

Engineering

Help

Stop


34/40



Operator Tab

Status Indicator

Condition OK

Condition Not OK

Reset Button

First-Out Indicator


35/40



The Operator tab shows the following information:

• A Status Indictor, identical to the one on the Graphic Symbol, showingthe current interlock state (all conditions met, non-bypassed conditionsmet, 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

Condition Bypassed, Input OK

Bypass Indicator

Condition Bypassed, Input Not OK

Button Action SecurityRequired

Resets all latched interlocks Code A


36/40



Engineering Tab

The Engineering tab is divided into two pages.

Engineering Tab Page 1

For each Interlock, the following items can be configured.

Button Action SecurityRequired

Description A text description of the permissive set. It willappear 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 ProgramCommands onReceipt

Select to clear Program Commands on Receipt.See Edge and Level in the Preface for moreinformation.

Code E


37/40



Engineering Tab Page 2

The 16 interlock inputs are configured on the Engineering tab Page 2. Foreach Interlock, the following can be configured:

Check Box / Field Action SecurityRequired

Descriptions Enter a text description of eachpermissive condition used. Thepermissives with text entered willappear on the Operator tab of theFaceplate. If the text for acondition is empty (null), thatpermissive is not shown.

Code E

OK State Selects which state of thecorresponding interlock is the ‘OKto Start’ state.

Code E

Can Bypass Check this box to indicate thatthe corresponding interlock maybe bypassed.

Code E


38/40



Interlock and Permissive Help

Must Reset Check this box to indicate thatthe corresponding interlock mustbe reset.

Code E

Check Box / Field Action SecurityRequired


39/40


40/40

p intlk 2.0 syslib

Documents