Documente Academic
Documente Profesional
Documente Cultură
Identifies information that is critical for successful application and understanding of the product.
Allen-Bradley, Rockwell Software, Rockwell Automation, RSLogix, Logix5000, FactoryTalk, PlantPAx, ControlLogix, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Table of Contents
Preface
Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optional Template Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discrete 2-, 3-, or 4-state Device Input Structure . . . . . . . . . . . . . . . .
Discrete 2-, 3-, or 4-state Device Output Structure . . . . . . . . . . . . . .
Discrete 2-, 3-, or 4-state Device Local Configuration Tags. . . . . . .
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generic Alarm Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Programming Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status/Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Bypass Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use Global Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discrete 2-, 3-, 4-state Device Faceplate Help . . . . . . . . . . . . . . . . . . .
11
12
13
13
13
14
15
15
20
24
25
25
25
26
26
28
32
35
36
36
37
38
38
41
44
49
51
53
Table of Contents
Notes:
Preface
The PlantPAx Library of Process Objects is a predefined library of controller
code (Add-On Instructions), display elements (global objects), and faceplate
displays that let you quickly assemble large applications with proven strategies,
rich functionality, and known performance.
The Process Objects can be downloaded from Knowledgebase Answer ID 62682
at http://www.rockwellautomation.custhelp.com.
The PlantPAx Library of Process Objects version 2.0 is compatible with the
following products:
RSLogix 5000 software, version 18 or later
FactoryTalk View Site Edition software, version 6.0 or later
FactoryTalk View Machine Edition software, version 6.0 or later
Library Programming
Considerations
Preface
IMPORTANT
Prescan
During the transition into Run mode, the controller performs a Prescan before
the first logic scan. Prescan is a special scan of all routines in the controller. The
controller scans all main routines and subroutines during Prescan, but ignores
jumps that could skip the execution of instructions. The controller executes all
FOR loops and subroutine calls. If a subroutine is called more than once, it is
executed each time it is called. The controller uses Prescan instructions to reset
non-retentive data values.
During Prescan, input values are not current and outputs are not written. The
following conditions generate Prescan:
Toggle from Program to Run mode
Automatically enter Run mode from a power-up condition
Prescan does not occur for a program when the following occurs:
Program becomes scheduled while the controller is running
Program is unscheduled when the controller enters Run mode
IMPORTANT
The Prescan performs the Process Add-On Instructions logic routine as all false
and then performs its Prescan routine as true.
Preface
Example
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 Service Release. The
instruction and faceplate do not have to have the same Service Release to be
compatible. In the table above, the Add-On Instruction and faceplate shown are
compatible because they have the same Major.Minor (2.0).
Preface
If you modify the data in the Input field and move to a different field
without pressing Enter, the border remains a solid line. This indicates 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
Preface
Additional Resources
Description
Preface
Notes:
10
The P_D4SD (Discrete 2-, 3-, 4-state Device) Add-On Instruction controls
and monitors feedback from a Discrete 2-state, 3-state, or 4-state Device in a
variety of modes, monitoring for fault conditions. These devices include a
multiple-speed motor or a multiple-position valve. The global objects and
faceplate shown below are examples of the graphical interface tools used with the
embedded logic.
Faceplate
Global Objects
Add-On Instruction
Guidelines
11
Functional Description
12
The Discrete 2-, 3-, or 4-state Device Add-On Instruction provides the
following capabilities:
Provides configuration to have two, three, or four selectable states for the
device.
Provides Operator and Program Commands to select one of the two,
three, or four states of the device.
Controls four discrete outputs, with configurable states of each output in
the various device states. Each output can be set, cleared, or left in last state
in a given device state.
Monitors four discrete feedback inputs, with configurable states
(including must be on, must be off , and don't care) for each input in the
various device states for monitoring the actual position of the device.
Provides configurable text labels for each of the states.
When feedback inputs are used, detects failure to reach the target state,
after a configurable time, and alarms the failure. Optionally sheds to the
default state (state 0) on a feedback failure.
Monitors Permissive conditions, which allow commanding the device to
each state.
Monitors Interlock conditions, which return the device to its
default state (state 0).
Provides simulation of a normally working device, while holding the
outputs to the real device de-energized, for use in testing or operator
training.
Monitors I/O communication status, providing an alarm on an I/O fault.
Optionally sheds to the default state on an I/O fault condition.
Provides an Available Status when in Program Mode and operating
normally for use by automation logic to determine if the logic can
manipulate the device.
Operates in Hand, Maintenance, Override, Program, and
Operator modes. (See Modes on page 25.)
Add-On Instructions are reusable code objects that contain encapsulated logic
that can streamline implementing your system. This lets you create your own
instruction set for programming logic as a supplement to the instruction set
provided natively in the ControlLogix firmware. An Add-On Instruction is
defined once in each controller project, and can be instantiated multiple times in
your application code as needed.
Required Files
Controller File
The P_D4SD_2_0-00_AOI.L5X Add-On Instruction must be imported into
the controller project to be able to be used in the controller configuration. The
service release number (boldfaced) may change as service revisions are created.
Visualization Files
The following files from Knowledgebase Answer ID 62682 at
http://www.rockwellautomation.custhelp.com are required in order to use
the P_D4SD Object.
Table 1 - P_D4SD Visualization File Types
Application Type
File Type
Description
Graphics - Displays
GFX
(RA-BAS) Common-AnalogEdit
N/A
(RA-BAS) P_D4SD-Faceplate
(RA-BAS-ME) P_D4SD-Faceplate
(RA-BAS) P_D4SD-Help
(RA-BAS-ME) P_D4SD-Help
(RA-BAS) P_Alarm-Help
(RA-BAS-ME) P_Alarm-Help
(RA-BAS) P_D4SD-Config
(RA-BAS-ME) P_D4SD-Config
(RA-BAS) P_Mode-Help
(RA-BAS-ME) P_Mode-Help
(RA-BAS) P_Mode-Config
(RA-BAS-ME) P_Mode-Config
Graphics - Global
Objects
GGFX
13
File Type
Description
Graphics - Images
BMP
HMI Tags
CSV
N/A
FTVME_PlantPAxOBjx2_0_2011 09 30Tags.CSV
(1) The service release number (boldfaced) may change as service revisions are created.
14
This section describes the parameter references for this Add-On Instruction.
Controller Code
Data Type
Default
Description
EnableIn
BOOL
Ladder Diagram:
Set to the rung-in condition of the condition.
Function Block or Ladder Diagram:
If false, the system performs the EnableInFalse routine. If set, the instruction executes.
Structured Text:
No effect. The instruction executes.
Inp_FdbkA
BOOL
Inp_FdbkB
BOOL
Feedback input signals from device. Use the feedback configuration parameters (for example,
Cfg_FdbkSt0Check and Cfg_FdbkSt0State) to determine how these inputs are used to determine
actual state.
Inp_FdbkC
BOOL
Inp_FdbkD
BOOL
Inp_DeviceFault
BOOL
Inp_PermOK0
BOOL
Inp_NBPermOK0
BOOL
Inp_PermOK1
BOOL
Inp_NBPermOK1
BOOL
Inp_PermOK2
BOOL
Inp_NBPermOK2
BOOL
Inp_PermOK3
BOOL
Inp_NBPermOK3
BOOL
Inp_IntlkOK
BOOL
1 = Interlocks OK
0 = Not OK, go to State 0
Inp_NBIntlkOK
BOOL
1 = Non-bypassable Interlocks OK
0 = Not OK, go to State 0
15
Data Type
Default
Description
Inp_IOFault
BOOL
Inp_Sim
BOOL
Inp_Hand
BOOL
Inp_Ovrd
BOOL
Inp_OvrdCmd
DINT
Inp_Reset
BOOL
Cfg_St0onShed
BOOL
1 = Go to State 0 on Shed
0 = Hold position on Shed
Cfg_NumStates
DINT
Cfg_OutSt0Write
SINT
2#0000_1111
Cfg_OutSt0State
SINT
2#0000_0001
Cfg_OutSt1Write
SINT
2#0000_1111
Cfg_OutSt1State
SINT
2#0000_0010
Cfg_OutSt2Write
SINT
2#0000_1111
These configuration parameters determine how the outputs are used to command state. The parameter
Cfg_OutSt[x]Write configures which outputs get written for each state. The parameter
Cfg_OutSt[x]State configures what gets written for each state.
For example, if all outputs must be set to 0 except Out_A which must be set to 1 to command the device
to state 1, then Cfg_OutSt1Write should be 2#0000_1111 and Cfg_OutSt1State should be
2#0000_0001.
By default, all four outputs are written in every state, with a single output set to 1 in each state.
Cfg_OutSt2State
SINT
2#0000_0100
Cfg_OutSt3Write
SINT
2#0000_1111
Cfg_OutSt3State
SINT
2#0000_1000
Cfg_FdbkSt0Check
SINT
2#0000_0000
Cfg_FdbkSt0State
SINT
2#0000_0001
Cfg_FdbkSt1Check
SINT
2#0000_0000
Cfg_FdbkSt1State
SINT
2#0000_0010
Cfg_FdbkSt2Check
SINT
2#0000_0000
Cfg_FdbkSt2State
SINT
2#0000_0100
Cfg_FdbkSt3Check
SINT
2#0000_0000
Cfg_FdbkSt3State
SINT
2#0000_1000
Cfg_HasPerm0Obj
BOOL
Cfg_HasPerm1Obj
BOOL
Cfg_HasPerm2Obj
BOOL
Cfg_HasPerm3Obj
BOOL
Cfg_HasIntlkObj
BOOL
Cfg_PCmdClear
BOOL
When this parameter is 1, program commands are cleared once they are acted upon. When set to 0,
program commands remain set until cleared by the application program logic. This parameter is aliased
to internal tag Mode.Cfg_PCmdClear from P_Mode.
IMPORTANT: Clearing this parameter online may cause unintended program command execution.
16
These configuration parameters determine how the inputs are used to determine state. The parameter
Cfg_FdbkSt[x]Check configures which inputs get checked for each state. The parameter
Cfg_FdbkSt[x]State configures the values of the inputs which determine each state.
For example, if the device returns a 0 to Inp_FdbkA and Inp_FdbkB and a 1 to Inp_FdbkC when the
device is in state 3, then Cfg_FdbkSt3Check should be 2#0000_0111 and Cfg_FdbkSt1Write should
be 2#0000_0100.
By default, all inputs are dont care in every state (no feedback checking).
Data Type
Default
Description
Cfg_ProgDefault
BOOL
This parameter defines the default mode. When this parameter is 1, the mode defaults to Program if no
mode is being requested. When this parameter is 0, the mode defaults to Operator if no mode is being
requested. This parameter is aliased to internal tag Mode.Cfg_ProgDefault of P_Mode.
IMPORTANT: Changing this parameter online may cause unintended mode changes.
Cfg_OCmdResets
BOOL
Cfg_OvrdPermIntlk
BOOL
Cfg_ShedOnFail
BOOL
Cfg_ShedOnDeviceFault
BOOL
Cfg_ShedOnIOFault
BOOL
Cfg_HasFailAlm
BOOL
Cfg_HasDeviceFaultAlm
BOOL
Cfg_HasIntlkTripAlm
BOOL
Cfg_HasIOFaultAlm
BOOL
Cfg_FailResetReqd
BOOL
Cfg_DeviceFaultResetReqd
BOOL
Cfg_IntlkTripResetReqd
BOOL
Cfg_IOFaultResetReqd
BOOL
This parameter determines whether a reset is required to clear the alarm status. When this parameter
is 1, the alarm is latched On when the alarm occurs. After the alarm condition returns to normal, a reset
is required to clear the alarm status (for example, OCmd_Reset, Inp_Reset, or Fail.OCmd_Reset would
be required to clear the Fail alarm after the alarm is set and the value returns to normal). When this
parameter is 0, no reset is required and the alarm status is cleared when the alarm condition returns to
normal. This parameter is aliased to internal tag .Cfg_ResetReqd of the corresponding P_Alarm object.
IMPORTANT: If the reset clears the alarm, it also acknowledges the alarm.
Cfg_FailAckReqd
BOOL
Cfg_DeviceFaultAckReqd
BOOL
Cfg_IntlkTripAckReqd
BOOL
Cfg_IOFaultAckReqd
BOOL
Cfg_FailSeverity
SINT
Cfg_DeviceFaultSeverity
SINT
Cfg_IntlkTripSeverity
SINT
Cfg_IOFaultSeverity
SINT
These parameters determine the severity of each alarm. This drives the color and symbol that are used
to indicate alarm status on the faceplate and global object. This parameter is aliased to internal tag
.Cfg_Severity of the associated P_Alarm object. The following are valid values:
1 = Information
2 = Warning
3 = Exception
4 = Fault
IMPORTANT: This severity parameter drives only the indication on the global object and faceplate. The
Alarms and Events definition severity drives the color and symbol that is used on the alarm banner and
alarm summary as well as the value returned by FactoryTalk Alarms and Events display commands.
Cfg_OutAPulseT
REAL
0.0
Cfg_OutBPulseT
REAL
0.0
Cfg_OutCPulseT
REAL
0.0
Cfg_OutDPulseT
REAL
0.0
This parameter determines whether an acknowledgement is required for an alarm. When this
parameter is 1, the acknowledge (ack) bit is cleared when the alarm occurs. An acknowledge command
(for example, PCmd_FailAck or Fail.OCmd_Ack) would be required to acknowledge the alarm. When set
to 0, the Acknowledge bit is set when an alarm occurs indicating an acknowledged alarm and no
acknowledge command is required. This parameter is aliased to internal tag Cfg_AckReqd of the
corresponding P_Alarm object.
17
Data Type
Default
Description
Cfg_SimFdbkT
DINT
Cfg_FailT
DINT
10
Time after new state requested to reach that state before fault (s)
PSet_Owner
DINT
PCmd_St0
BOOL
PCmd_St1
BOOL
PCmd_St2
BOOL
PCmd_St3
BOOL
PCmd_Acq
BOOL
PCmd_Rel
BOOL
PCmd_Lock
BOOL
PCmd_Unlock
BOOL
PCmd_Reset
BOOL
PCmd_FailAck
BOOL
PCmd_FailInhibit
BOOL
PCmd_FailUninhibit
BOOL
PCmd_DeviceFaultAck
BOOL
PCmd_DeviceFaultInhibit
BOOL
PCmd_DeviceFaultUninhibit
BOOL
PCmd_IntlkTripAck
BOOL
PCmd_IntlkTripInhibit
BOOL
PCmd_IntlkTripUninhibit
BOOL
PCmd_IOFaultAck
BOOL
PCmd_IOFaultInhibit
BOOL
PCmd_IOFaultUninhibit
BOOL
OCmd_St0
BOOL
18
Data Type
Default
Description
OCmd_St1
BOOL
OCmd_St2
BOOL
OCmd_St3
BOOL
OCmd_Bypass
BOOL
OCmd_Check
BOOL
MCmd_Disable
BOOL
MCmd_Enable
BOOL
OCmd_Reset
BOOL
Operator command to reset all alarms requiring reset and any latched shed conditions
OCmd_ResetAckAll
BOOL
Operator command to reset and acknowledge all alarms and reset any latched shed conditions
19
Data Type
Description
EnableOut
BOOL
Enable Output: The EnableOut signal is not manipulated by this instruction. Its output state always reflects
EnableIn input state
Out_A
BOOL
Output A to device
Out_B
BOOL
Output B to device
Out_C
BOOL
Output C to device
Out_D
BOOL
Output D to device
Val_Cmd
SINT
Device Command:
0 = None
1 = State 0
2 = State 1
3 = State 2
4 = State 3
Val_Sts
SINT
Val_Fault
SINT
20
Data Type
Description
Val_Mode
DINT
Mode enumeration:
0 = No mode
1 = Hand
2 = Maintenance
3 = Override
4 = Program (locked)
5 = Operator (locked)
6 = Program (unlocked, Oper is default)
7 = Operator (unlocked, Prog is default)
8 = Program (unlocked, Prog is default)
9 = Operator (unlocked, Oper is default)
Alias for Mode.Val
Val_Owner
DINT
Val_Notify
SINT
Sts_St0
BOOL
Sts_St1
BOOL
Sts_St2
BOOL
Sts_St3
BOOL
Sts_Moving
BOOL
Sts_Available
BOOL
Sts_Bypass
BOOL
Sts_BypActive
BOOL
Sts_Disabled
BOOL
Sts_NotRdy
BOOL
Sts_MaintByp
BOOL
Sts_AlmInh
BOOL
Sts_Err
BOOL
Err_Timer
BOOL
Err_Sim
BOOL
Err_Alarm
BOOL
Sts_Hand
BOOL
Sts_Maint
BOOL
Sts_Ovrd
BOOL
21
Data Type
Description
Sts_Prog
BOOL
Sts_Oper
BOOL
Sts_ProgOperLock
BOOL
Sts_NoMode
BOOL
Sts_Fail
BOOL
Alm_Fail
BOOL
Ack_Fail
BOOL
Sts_FailDisabled
BOOL
1 = Fail to reach commanded state Alarm has been disabled (will not be sent)
Alias for Fail.Disabled
Sts_FailInhibited
BOOL
Sts_FailSuppressed
BOOL
1 = Fail to reach commanded state Alarm has been suppressed (logged only)
Alias for Fail.Suppressed
Sts_DeviceFault
BOOL
Alm_DeviceFault
BOOL
Ack_DeviceFault
BOOL
Sts_DeviceFaultDisabled
BOOL
Sts_DeviceFaultInhibited
BOOL
Sts_DeviceFaultSuppressed
BOOL
Sts_IntlkTrip
BOOL
Alm_IntlkTrip
BOOL
Ack_IntlkTrip
BOOL
Sts_IntlkTripDisabled
BOOL
Sts_IntlkTripInhibited
BOOL
Sts_IntlkTripSuppressed
BOOL
22
Data Type
Description
Sts_IOFault
BOOL
Alm_IOFault
BOOL
Ack_IOFault
BOOL
Sts_IOFaultDisabled
BOOL
Sts_IOFaultInhibited
BOOL
Sts_IOFaultSuppressed
BOOL
Rdy_St0
BOOL
Rdy_St1
BOOL
Rdy_St2
BOOL
Rdy_St3
BOOL
Rdy_Bypass
BOOL
Rdy_Check
BOOL
Rdy_Disable
BOOL
Rdy_Enable
BOOL
Rdy_Reset
BOOL
Rdy_ResetAckAll
BOOL
P_D4SD
BOOL
23
Data Type
Default
Description
Cfg_Desc
STRING_40
Cfg_Label
STRING_20
Discrete Device
Cfg_St0Text
STRING_8
Off
Cfg_St1Text
STRING_8
On
Cfg_St2Text
STRING_8
Cfg_St3Text
STRING_8
Cfg_Tag
STRING_20
P_D4SD
24
Operations
This section describes the primary operations for this Add-On Instruction.
Modes
The Discrete 2-, 3-, 4-state Device Add-On Instruction uses the following
standard modes, implemented by using an embedded P_Mode
Add-On Instruction.
Mode
Description
Operator
The operator controls the state of the device by using the HMI faceplate.
Program
Logic outside the P_D4SD instruction controls the device by using Program Commands
(PCmd_St0, PCmd_St1, PCmd_St2, PCmd_St3).
Override
Priority logic outside the P_D4SD instruction controls the device. The default is to set the
device to State 0, but any state can be commanded. Bypassable interlocks and permissives
can optionally by bypassed in Override mode.
Maintenance
Maintenance personnel have control of the device by using the HMI faceplate and it is not
available for normal operation by operators or program logic. Bypassable permissives and
interlocks are bypassed; and checking for device failure to reach target position is
not performed.
Hand
Logic, usually hard-wired, has superseded P_D4SD control of the device. If device state
feedback inputs are used, the P_D4SD instruction tracks the state of the device (to the
extent that unique feedback patterns are used for the states) to facilitate bumpless
transfer back to one of the other modes.
Execution
The following table explains the handling of instruction execution conditions.
Condition
Description
Postscan
25
Alarms
The P_D4SD Instruction uses the following alarms, implemented by using
embedded P_Alarm Add-On Instructions.
Table 5 - P_D4SD Alarm Parameters
Alarm
P_Alarm Name
Description
Interlock Trip
IntlkTrip
Triggered when an Interlock not OK causes the device to transition from another state to State 0.
I/O Fault
IOFault
Triggered by the Inp_IOFault Input, usually used to indicate an I/O communication failure.
The device can be configured to either alarm only or to shed to State 0 on an I/O Fault.
Fail
Fail
Device Fault
DeviceFault
Description
Inp
Inp_Reset
Cfg_AlmMinOnT
PCmd_Reset
PCmd_Ack
PCmd_Inhibit
PCmd_Uninhibit
OCmd_Reset
OCmd_Ack
OCmd_Suppress
OCmd_Unsuppress
MCmd_Disable
MCmd_Enable
Description
Rdy_Reset
Rdy_Ack
Rdy_Suppress
Rdy_Unsuppress
26
Rdy_Enable
Val_Notify
Alm
Ack
Inhibited
Suppressed
Disabled
Sts_Error
Err_Timer
Err_Severity
27
Programming Example
This example uses the P_D4SD Add-On Instruction to control a cooling fan that
has three fixed speeds (low, medium, high) and an off state. This is considered
a 4-state device. In this example, three digital outputs are used to set the speed
setting (when all three are off, the fan is commanded off ) and three digital inputs
providing feedback of the actual fan state (when all three are off, the fan is off ).
In this example, the four cooling fan states are being mapped to the device
as follows:
State 0 = Off
State 1 = Low
State 2 = Medium
State 3 = High
The parameter Cfg_NumStates should be set to 4, indicating this is a four-state
device. The input parameters for states 13 (Inp_FdbkB, Inp_FdbkC,
Inp_FdbkD) are connected to the digital inputs representing the status of the fan.
The output parameters for states 13 (Out_B, Out_C, Out_D) are connected
to the digital outputs that command the fan to the desired state.
28
Based on the wiring of the I/O, we can now configure the P_D4SD instruction
how we want to process the outputs to get to the desired state. We can do
this via the following table:
x = don't care, 1 = command output On, 0 = command output Off.
Table 8 - P-D4SD Example Outputs
Output A
Output B
Output C
Output D
State 0
State 1
State 2
State 3
We are setting Output A so it can be used for display purposes even though
Output A is not used by the cooling fan device. The parameter
Cfg_OutSt[x]Write determines which outputs get written for each state. The
parameter Cfg_OutSt[x]State determines the state that gets written. These
parameters are single integers where bit 0 represents output A and bit 3 represents
output D.
These parameters are displayed in binary format as indicated by the prefix 2#. By
using Table 8, we can set the settings as follows:
Cfg_OutSt0Write:
2#0000_1111
Cfg_OutSt0State:
2#0000_0001
Cfg_OutSt1Write:
2#0000_1111
Cfg_OutSt1State:
2#0000_0010
Cfg_OutSt2Write:
2#0000_1111
Cfg_OutSt2State:
2#0000_0100
Cfg_OutSt3Write:
2#0000_1111
Cfg_OutSt3State:
2#0000_1000
We can now repeat this same effort to configure how the P_D4SD instruction
determines actual state based on the field inputs via the following table:
x = don't care, 1 = status checked on, 0 = status checked off.
Table 9 - P_D4SD Example Inputs
Input A
Input B
Input C
Input D
State 0
State 1
State 2
State 3
29
2#0000_1110
Cfg_FdbkSt0State:
2#0000_0000
Cfg_FdbkSt1Check:
2#0000_1110
Cfg_FdbkSt1State:
2#0000_0010
Cfg_FdbkSt2Check:
2#0000_1110
Cfg_FdbkSt2State:
2#0000_0100
Cfg_FdbkSt3Check:
2#0000_1110
Cfg_FdbkSt3State:
2#0000_1000
As this is a cooling fan, if there is a device mismatch or fault, we still want the
logic to command to the desired state. Therefore, Cfg_ShedOnFail and
Cfg_ShedOnDeviceFault are both set to 0.
Lastly, the following local configuration tags should be configured to drive the
text on the operations faceplate. In this example, the cooling fan P&ID tag is
M401. In this example, they are set as follows:
30
Cfg_Tag:
M401
Cfg_Label:
Cfg_Desc:
Cfg_St0Text:
Stopped
Cfg_St1Text:
Slow
Cfg_St2Text:
Medium
Cfg_St3Text:
Fast
Local tags can be configured through the HMI faceplates or in RSLogix 5000
software by opening the Instruction Logic of the Add-On Instruction instance
and then selecting the string on the displayed rung.
All the strings in local tags are shown on the first rung of the Add-On
Instruction's Logic routine for your convenience.
31
A display element (global object) is created once and can be referenced multiple
times on multiple displays in an application. When changes are made to the
original (base) object, the instantiated copies (reference objects) are
automatically updated. Use of global objects, in conjunction with tag structures
in the ControlLogix system, aid consistency and save engineering time.
Display Elements
IMPORTANT
Display Element
Description
The Three/Four-way Valve parameters define the inlet
and output ports of the valve:
32
Display Element
Description
33
Display Element
Description
GO_P_D4SD_Agitator_D
GO_P_D4SD_Mixer_U
GO_P_D4SD_Pump_R
GO_P_D4SD_Pump_U
GO-P_D4SD_Pump_L
GO_P_D4SD_RPump_U
GO_P_D4SD_Fan_D
34
Display Element
Description
GO_P_D4SD_Conveyor_R
Status/Quality Indicator
Status/Quality Indicators
One of these symbols appears to the left of the graphic symbol or right of the
label when the described condition is true.
Graphic Symbol
Description
Invalid configuration
I/O Fault
Value uncertain
No symbol displayed
TIP
When the Invalid Configuration Indicator appears, you can find what
configuration setting is invalid by following the indicators. Click the graphic
symbol to call up the faceplate. The Invalid Configuration indicator appears
next to the appropriate tab at the top of the faceplate to guide you in finding
the configuration error. Once you navigate to the tab, the misconfigured item
will be flagged with this indicator or appear in a magenta box.
35
Description
A Maintenance Bypass is active
No symbol displayed
TIP
When the Maintenance Bypass Indicator appears, you can find what condition
was bypassed by following the indicators. Click the graphic symbol to call up
the faceplate. The Maintenance Bypass Indicator will appear next to the
appropriate tab at the top of the faceplate to guide you in finding the bypass.
Once you navigate to the tab, the bypassed item will be flagged with this
indicator.
Alarm Indicators
One of these symbols appears to the left of the Label to indicate the described
alarm condition. The alarm border and label background blink if
Acknowledgement of an alarm condition is required.
Symbol
Description
Black I in white box
36
2. In the display file, right-click the global object file and choose Global
Object Parameter Values.
The Global Object Parameter Values dialog box appears.
3. Type the tag in the Value column as specified in the Description column.
TIP
4. Click OK.
37
The P_D4SD faceplate consists of five tabbed pages. The Operator tab is
displayed when the faceplate is initially called up. Click the appropriate icon at
the top of the faceplate to access a specific tab.
Faceplate
Maintenance
Operator
Alarm Configuration
Engineering
Alarms
Exit
Help
The faceplate provides the means for operators, maintenance workers, engineers,
and others to interact with the P_D4SD Instruction instance, including viewing
its status and values and manipulating it through its commands and settings.
When a given input is restricted via FactoryTalk View security, the required user
security code letter is shown in the tables that follow.
Operator Tab
Mode Indicator
Reset Acknowledge
All Alarms Button
Device State
Indicator
Device Command Buttons
38
Action
Security
Manual Device
Operation (Code B)
Acknowledge Alarms
(Code F)
None
When the P_D4SD instruction does not have associated Permissive (P_Perm)
instructions, the Permissive buttons revert to indicators only.
39
The following table shows the alarm status on the Operator tab.
Table 12 - Operator Tab Alarm Status
Graphic Symbol
Alarm Status
In Alarm (Active Alarm)
40
Maintenance Tab
This tab is divided into two pages.
Page 1 of the Maintenance tab shows the following information:
The current mode (Program, Operator, Override, Maintenance, or Hand)
Requested Modes Indicator - This display highlights all of the modes that
have been requested. The leftmost highlighted mode is the active mode
Shows whether the device is enabled or disabled
Shows Permissive Bypassed/Enabled Indicator
Shows whether Override mode bypasses the bypassable permissives
Maintenance Mode
Acquire and Release
Command Buttons
Mode Indicator
Requested Modes Indicator
41
The following table shows the functions on the Maintenance tab page 1.
Function
Action
Security
Configuration Parameters
Equipment
Maintenance
(Code C)
None
42
Disable Alarms
Bypass
Permissives
and Interlocks
(Code H)
Cfg_OvrdPermIntlk
The following table shows the functions on the Maintenance tab page 2.
Table 13 - Maintenance Tab 2 Description
Function
Action
Security
Configuration Parameters
Time to pulse:
Output A (sec)
Output B (sec)
Output C (sec)
Output D (sec)
Configuration
& Tuning
Maintenance
(Code D)
Cfg_OutAPulseT
Cfg_OutBPulseT
Cfg_OutCPulseT
Cfg_OutDPulseT
Cfg_FailT
43
Engineering Tab
This tab is divided into three pages.
On Page 1 of the Engineering tab, you can configure the description, label, tag,
and state names for the device.
The following table lists the functions on the Engineering tab page 1.
Table 14 - Engineering Tab 1 Description
Function
44
Action
Security
Configuration Parameters
None
Description
Cfg_Desc
Label
Engineering
Configuration
(Code E)
Cfg_Label
Action
Security
Configuration Parameters
Tag
Engineering
Configuration
(Code E)
Cfg_Tag
Number of States:
2
3
4
Cfg_NumStates
Clear Program
Commands on
Receipt
Cfg_PCmdClear
New operator
command resets
fault
Cfg_OCmdResets
Cfg_St0Text
Cfg_St1Text
Cfg_St2Text
Cfg_St3Text
This popup lets you set the Cfg_ProgDefault parameter, which sets the default
mode when no mode is being requested. Changing the parameter requires
engineering access (security code E).
IMPORTANT
If no mode is being requested, changing the default mode will change the
mode of the instruction.
45
The following table shows the functions on the Engineering tab page 2.
Table 15 - Engineering Tab 2 Description
46
Function
Action
Security
Configuration Parameters
A P_Perm object is
connected to:
Inp_PermOK0
Inp_PermOK1
Inp_PermOK2
Inp_PermOK3
Engineering
Configuration
(Code E)
A P_Intlk object is
connected to
Inp_Intlk
Outputs and
Feedback
Cfg_HasPerm0Obj
Cfg_HasPerm1Obj
Cfg_HasPerm2Obj
Cfg_HasPerm3Obj
Cfg_HasIntklObj
None
This popup directs how the P_D4SD instruction commands the device state via
outputs and determines the actual device state via feedback inputs. The first two
columns for output set parameters, Cfg_OutSt[x]Write, and
Cfg_OutSt[x]Value, determine how outputs are written to command to a state.
The second two columns for feedback set parameters, Cfg_FdbkSt[x]Check, and
Cfg_FdbkSt[x]State, determine how the state is interpreted from the
input values.
Changing the parameters requires engineering access (security code E).
47
The following table shows the functions on the Engineering tab page 3.
Table 16 - Engineering Tab 3 Description
Function
Action
Security
Configuration Parameters
Shed Action
Go to State 0
Engineering
Configuration
(Code E)
Cfg_St0onShed
Hold State
48
Shed Triggers:
Cfg_ShedonDeviceFault
Cfg_ShedonIOFault
Cfg_ShedonFail
Cfg_SimFdbkT
The following table shows the functions on the Alarm Configuration tab page 1.
Table 17 - Alarm Configuration Tab 1 Description
Function
Action
Security
Alarm
Configuration Parameters
Cfg_HasFailAlm
Cfg_HasDeviceFaultAlm
Cfg_HasIntlkTripAlm
Cfg_HasIOFaultAlm
49
50
Function
Action
Security
Configuration Parameters
Acknowledge
Required
Engineering
Configuration
(Code E)
Cfg_FailAckReqd
Cfg_DeviceFaultAckReqd
Cfg_IntlkTripAckReqd
Cfg_IOFaultAckReqd
Reset Required
Cfg_FailResetReqd
Cfg_DeviceFaultResetReqd
Cfg_IntlkTripResetReqd
Cfg_IOFaultResetReqd
Severity
Cfg_FailSeverity
Cfg_DeviceFaultSeverity
Cfg_IntlkTripSeverity
Cfg_IOFaultSeverity
Alarm Minimum ON
Time (seconds)
Fail.Cfg_AlmMinOnT
DeviceFault.Cfg_AlmMinOnT
IntlkTrip.Cfg_AlmMinOnT
IOFault.Cfg_AlmMinOnT
Code D
Alarms Tab
The Alarms tab displays each configured alarm for the P_D4SD instruction.
The icon on the tab for the Alarms page changes color based on the current active
alarms. A blinking alarm icon indicates that one or more alarms must be
acknowledged or the device must be reset.
Alarm Acknowledge
Command and Button
If an alarm is active, the panel behind the alarm changes color to match the
severity of the alarm. The color of the bell icon at the top of the faceplate
shows the highest active alarms severity, and the icon blinks if any alarm
is unacknowledged.
Table 18 - Alarm Color Definitions
Color
Definition
Magenta
Fault
Red
Exception
Yellow
Warning
Blue
Information
No alarm
51
Action
Security
Acknowledge Alarms
(Code F)
Acknowledge Alarms
(Code F)
The panel behind the alarm blinks if the alarm requires acknowledgement.
Click the button with the checkmark to acknowledge the alarm.
The Alarm Acknowledge button is enabled if the corresponding alarm
requires acknowledgement.
The Reset and Acknowledge All Alarms button is enabled if any alarm requires
reset or acknowledgement.
52
53
Notes:
54
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
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.
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