APACSLIB
APACSLIB
ES Library 1
PCS 7
APACS+ ES Library User's Guide
for V7.1
Manual
04/2009
A5E02453738-01
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes
in this documentation qualified persons are defined as persons who are authorized to commission, ground and
label devices, systems and circuits in accordance with established safety practices and standards.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be adhered to. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Purpose of ES Manual
This manual provides information necessary to use the ES Library in order to migrate
APACS+ systems to a PCS 7 environment.
Training Centers
Siemens Technical Training Centers provides extensive training for all levels of plant
personnel to ensure optimal performance from APACS+ and PCS 7 control systems.
Classes include extensive hands-on activities using appropriate equipment, making the
training directly and immediately applicable.
On-line information is available: http://www.sitrain.com.
Siemens also offers a number of training courses to familiarize you with the SIMATIC S7
automation system. Please contact your regional training center or our central training center
in D 90327 Nuremberg, Germany, for details:
Telephone: +49 (911) 895-3200 or Internet http://www.sea.siemens.com/sitrain.
APACS+
Advanced Process Control Systems
See also
ES Library ReadMe (http://support.automation.siemens.com/US/View/en/35201997)
ES Library UserManual (http://support.automation.siemens.com/US/View/en/35202373)
1¾UQEHUJ
-RKQVRQ&LW\ %HLMLQJ
Preface ...................................................................................................................................................... 3
1 ES Library.................................................................................................................................................. 9
1.1 PCS 7 ES Option for APACS+.......................................................................................................9
1.1.1 Introduction - The PCS 7 ES Option for APACS+™......................................................................9
1.1.2 Library Description .........................................................................................................................9
1.2 Library Function Blocks................................................................................................................10
1.2.1 Introduction ..................................................................................................................................10
1.2.2 The Quality Code Display ............................................................................................................11
1.2.3 AALM_AFB...................................................................................................................................11
1.2.3.1 AALM_AFB: Analog Alarm...........................................................................................................11
1.2.3.2 AALM_AFB Input Output..............................................................................................................14
1.2.4 AM_AFB .......................................................................................................................................22
1.2.4.1 AM_AFB: Auto/Manual.................................................................................................................22
1.2.4.2 AM_AFB Input Output ..................................................................................................................23
1.2.5 ANALOG_ALM_BLK ....................................................................................................................24
1.2.5.1 ANALOG_ALM_BLK: Analog Alarm ............................................................................................24
1.2.5.2 ANALOG_ALM_BLK Input Output ...............................................................................................27
1.2.6 BLK_VLV_1OUT_BLK..................................................................................................................32
1.2.6.1 BLK_VLV_1OUT: Block Valve with One Output ..........................................................................32
1.2.6.2 BLK_VLV_1OUT_BLK Input Output.............................................................................................34
1.2.7 BLK_VLV_2OUT_BLK..................................................................................................................36
1.2.7.1 BLK_VLV_2OUT: Block Valve with Two Outputs ........................................................................36
1.2.7.2 BLK_VLV_2OUT_BLK Input Output.............................................................................................38
1.2.8 CASCADE_BLK ...........................................................................................................................41
1.2.8.1 CASCADE: Cascade Controller...................................................................................................41
1.2.8.2 CASCADE_BLK Input Output ......................................................................................................45
1.2.9 DALM_AFB ..................................................................................................................................58
1.2.9.1 DALM_AFB: Discrete Alarm.........................................................................................................58
1.2.9.2 DALM_AFB Input Output .............................................................................................................60
1.2.10 DISCRETE_ALM_BLK .................................................................................................................64
1.2.10.1 DISCRETE_ALM_BLK .................................................................................................................64
1.2.10.2 DISCRETE_ALM_BLK Input Output ............................................................................................65
1.2.11 EXT_SET_BLK.............................................................................................................................66
1.2.11.1 EXT_SET: External Setpoint Controller .......................................................................................66
1.2.11.2 EXT_SET_BLK Input Output........................................................................................................69
1.2.12 MOTOR_A_BLK ...........................................................................................................................78
1.2.12.1 MOTOR_A_BLK: Standard Motor ................................................................................................78
1.2.12.2 MOTOR_A_BLK Input Output ......................................................................................................81
1.2.13 MOTOR_A_ALM_BLK..................................................................................................................86
1.2.13.1 MOTOR_A_ALM: Motor with Alarm .............................................................................................86
1.2.13.2 MOTOR_A_ALM_BLK Input Output.............................................................................................89
1.2.14 MOTOR_1OUT_BLK....................................................................................................................92
1.2.14.1 MOTOR_1OUT: Motor with One Output......................................................................................92
1.2.14.2 MOTOR_1OUT_BLK Input Output...............................................................................................94
1.2.15 MOTOR_2OUT_BLK....................................................................................................................97
1.2.15.1 MOTOR_2OUT: Motor with Two Outputs ....................................................................................97
1.2.15.2 MOTOR_2OUT_BLK Input Output...............................................................................................99
The PCS 7 ES Option for APACS+ is a SIMATIC PCS 7 library is composed of Source
Charts (CFCs) and Structured Control Language (SCL) source files that emulate many of the
Derived Function Blocks (DFBs) in the APACS+ Basic Application Library. The source charts
and source files are also provided as compiled APACS+ function block types that may be
used with their matching faceplates and graphic symbols. Template Charts show how the
APACS+ function block types are typically used.
This library supplies a set of building blocks for users who want to construct PCS 7
applications based on APACS+ structures. These components are:
Ported APACS+ Blocks These function blocks provide the functionality of APACS+
standard function blocks.
Source (CFC) Charts and Source These charts and files provide the functionality of APACS+
(SCL) Files derived function blocks and give users the ability to customize the
types and create new types.
APACS+ Function Block Types These function blocks provide the functionality of APACS+
derived function blocks in a form that has connected faceplates
and graphic symbols.
Template (CFC) Charts These charts provide examples of APACS+ function block types
integrated with other PCS 7 blocks to facilitate easier user
implementation within the PCS 7 ES.
Additional Topics:
Faceplates and Graphic Symbols These pre-configured Human-Machine Interface (HMI) elements
provide the ability to display/modify data associated with an
APACS+ function block type.
Customizing the Library These instructions describe customization of the source charts
and files, including compilation to create new block types and
modification of the graphical elements.
1.2.1 Introduction
A PCS 7 function block serves the same purpose as a function block in APACS+. A function
block runs a pre-configured algorithm that is not user configurable. There are block
parameters that can be used to define the operation of the algorithm, just as softlist
parameters were used in APACS+. Block parameters can be displayed as input/output nubs
on the block by the user.
In order for the Quality Code Icons to appear on the Faceplates, the QUALITY output of the
Channel Driver blocks must be connected to the appropriate QCxxx input of the ES Library
blocks.
1.2.3 AALM_AFB
Function
The Analog Alarm Function Block (AALM_AFB) is intended for detecting and signaling
abnormal data values. This block contains an Enable input, Alarm output, and NAK (not
acknowledged) output for each of the following alarm types:
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
AALM_AFB Input Output (Page 14)
Input
Note
This list differs from the inputs of the AALM_AFB block in APACS+ as follows:
• In APACS+, there are only four enables. There is now an enable for every alarm type.
• The parameter QBAD was added to get quality information from the control system.
• The parameters EV_ID and EV_ID2 were added to support the message system.
• Batch parameters BA_NA, BA_ID, STEP_NO are added to pass batch values in alarm
messages.
Output
Note
This list differs from the outputs of the AALM_AFB block in APACS+ as follows:
• In APACS+, there are only four alarms and four NAKs. There is now one of each for
every alarm type.
• The STATUS and CMD outputs have been removed.
• MSG1_ERR, MSG1_STAT, MSG2_ERR, and MSG2_STAT have been added to provide
the status of the message processing. For specific values, see the online help for
ALARM_8P.
Input/output
Note
This list differs from the softlist parameters of the AALM_AFB block in APACS+ as follows:
• The ALARM_TYPE parameters have been eliminated because there are now twelve sets
of parameters instead of just four. The type is now part of each parameter name.
• There is now a LIMIT, DEADBAND, DELAYIN, and DELAYOUT parameter for each
alarm type that requires it.
• The PCS 7 OS provides a ringback mechanism. The RINGBACK parameters have been
removed.
See also
AALM_AFB: Analog Alarm (Page 11)
1.2.4 AM_AFB
Function
The Auto/Manual Function Block (AM_AFB) regulates the source of a control loop output.
Generally, the block outputs either the Input (IN) value in automatic mode or its Internal
Output (IOUT) value in manual mode. When the block is in standby mode, the external
variable (EXTV) is written to the output (OUT).
The block's IN input is usually connected to the output of a PID block.The OUT value is
limited by both low and high limit (LOLIM and HILIM) In/Out parameters. The purpose of
these output limits is to prevent the output from being inadvertently driven beyond a process
or hardware operating limit. The Internal Output value can be changed via the Computer
Output (COUT) or the Auto/Manual function block itself (in track mode). The Computer
Output is written to by an operator command. The function block assigns the (OUT) value to
(COUT) as well. All values are in Engineering Units.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Use "Forced" for the restart flag and configure the
associated restart value to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
See also
AM_AFB Input Output (Page 23)
Input
Output
Note
The list differs from the outputs of the AM block in APACS+ as follows:
• COUT has been moved from Output to Input/Output.
Input/output
Note
This list differs from the softlist parameters of the AM block in APACS+ as follows:
• COUT has been moved from Output to Input/Output.
See also
AM_AFB: Auto/Manual (Page 22)
1.2.5 ANALOG_ALM_BLK
Function
The Analog Alarm Function Block (ANALOG_ALM_BLK) is a factory-compiled function block
ready-to-use analog indicator with alarms. It is based on the APACS+ ANALOG_ALARM
block in the Basic Application Library. As delivered, the PV (Process Variable) input value is
monitored for both high and low alarms. The ALARM output value provides the overall alarm
status. In addition, there is an alarm output for each analog alarm type. Alarms are
annunciated on the HMI.
The ENG_UNITS and DESC In/Outs are for holding values for the engineering units and
descriptor, respectively.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
ANALOG_ALM_BLK Input Output (Page 27)
Input
Output
Input/output
See also
ANALOG_ALM_BLK: Analog Alarm (Page 24)
Introduction (Page 10)
1.2.6 BLK_VLV_1OUT_BLK
Function
The Block Valve with One Output (BLK_VLV_1OUT) is intended for use as an open/close
block valve with one output. It is designed for a normally closed valve with auto/manual
operation, pulse commands, and interlocking. An alarm is provided for failure to reach the
desired state.
The [A_OPEN] and [A_CLSE] inputs are intended to input command pulses from a
sequence. The parameter AUTO determines the source of the open/close commands. In
auto mode (AUTO=TRUE) the auto inputs [A_OPEN] and [A_CLSE] are active, and in
manual mode (AUTO=FALSE), the parameters OPEN and CLOSE are active. OPEN,
CLOSE, and AUTO are to be manipulated via the operator interface. OPEN and CLOSE are
to be set TRUE; they are reset automatically.
A positive transition of auto open [A_OPEN] or manual open OPEN (depending on the
mode), latches the output [OUT]. Interlock [INTRLK] must be TRUE to allow the latch. A
positive transition of auto close [A_CLSE] or manual close CLOSE (also mode-dependent)
unlatches the output. The internal open and close timers determine if the valve has failed to
reach its desired state, and the failure output [FAIL] will become TRUE accordingly, which
triggers the alarm.
Although the BLK_VLV_1OUT block was implemented in ladder logic in APACS, it has been
implemented in SCL in PCS 7 due to differences between APACS+ and PCS 7 ladder logic.
The BLK_VLV_1OUT is a logical and functional equivalent to the corresponding APACS+
ladder networks. Comments in the provided SCL source code relate elements in the PCS 7
SCL code to corresponding elements in the original APACS+ ladder network.
The warm and cold startup behavior of AUTO and OUT is configurable, allowing the user to
override the default PCS 7 behavior described above if necessary. As delivered, AUTO will
be forced to "Manual" and OUT will be forced to "False" on a CPU restart.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value ("True"
or "False"). The RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the
RSTRT_OUT_FLAG is true. If RSTRT_OUT_FLAG is set to false ("Default"), the OUT
parameter will be set in accordance with default PCS 7 behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
BLK_VLV_1OUT_BLK Input Output (Page 34)
Input
Note
This list differs from the inputs of the BLK_VLV_1OUT_BLK block in APACS+ as follows:
• Restart parameters (RSTRT_...) did not exist in APACS+.
• EV_ID and SAMPLE_T did not exist in APACS+.
Output
Input/output
See also
BLK_VLV_1OUT: Block Valve with One Output (Page 32)
1.2.7 BLK_VLV_2OUT_BLK
Function
The Block Valve with Two Outputs (BLK_VLV_2OUT) is intended for use as an open/close
block valve with both an open output and a close output. It is designed for a valve with
auto/manual operation, pulse commands, and interlocking. An alarm is provided for failure to
reach the desired state.
The [A_OPEN] and [A_CLSE] inputs are intended to input command pulses from a
sequence. The parameter AUTO determines the source of the open/close commands. In
auto mode (AUTO=TRUE), the auto inputs [A_OPEN] and [A_CLSE] are active, and in
manual mode (AUTO=FALSE), the parameters OPEN and CLOSE are active. OPEN,
CLOSE, and AUTO are to be manipulated via the operator interface. OPEN and CLOSE are
to be set TRUE; they are reset automatically.
A positive transition of auto open [A_OPEN] or manual open OPEN (depending on the
mode) latches the internal OPEN_LATCH and pulses the open output [OP_OUT]. Interlock
[INTRLK] must be TRUE to allow the latch. A positive transition of auto close [A_CLSE] or
manual close CLOSE (also mode-dependent) unlatches the internal OPEN_LATCH and
pulses the close output [CL_OUT]. The internal open and close timers pulse the outputs and
determine if the valve has failed to reach its desired state, and the failure output [FAIL] will
become TRUE accordingly, which triggers the alarm.
Although the BLK_VLV_2OUT block was implemented in ladder logic in APACS, it has been
implemented in SCL in PCS 7 due to differences between APACS+ and PCS 7 ladder logic.
The BLK_VLV_2OUT is a logical and functional equivalent to the corresponding APACS+
ladder networks. Comments in the provided SCL source code relate elements in the PCS 7
SCL code to corresponding elements in the original APACS+ ladder network.
WARNING
Using "Default" for the RSTRT_AUTO_FLAG could result in your process running in
automatic mode after a restart. Use "Forced" for the restart flag and configure the associate
restart value to ensure a known restart state.
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
Input
Note
This list differs from the inputs of the BLK_VLV_2OUT_BLK block in APACS+ as follows:
• Restart parameters (RSTRT_...) did not exist in APACS+.
• EV_ID and SAMPLE_T did not exist in APACS+.
Output
Input/output
1.2.8 CASCADE_BLK
Function
CASCADE_BLK is a compiled version of the CASCADE source chart. Within the chart, there
are two connected control loops, primary and secondary. Each contains SETPNT_AFB and
PID_AFB blocks along with alarming logic. The secondary loop also contains an AM_AFB
block.
The primary controller tracks the secondary process variable [S_PV] when the cascaded
loops are in manual mode (AUTO=FALSE) or secondary mode (CASC=FALSE). The
PRI_SETPOINT block supplies the setpoint [P_SP_OUT] to the PRI_CONTROLLER block.
The PRI_SETPOINT block has a ramping feature for auto mode. The setpoint tracks the
primary process variable [P_PV] in manual or secondary mode. The PRI_CONTROLLER
block is a PID block; it operates when both AUTO and CASC are TRUE and tracks the
secondary process variable [S_PV] if either is FALSE. The PRI_CONTROLLER block output
becomes the external setpoint to the secondary control loop.
The SEC_SETPOINT block supplies the setpoint [S_SP] to the SEC_CONTROLLER block.
The SEC_SETPOINT block has a ramping feature for secondary mode (CASC=FALSE). In
cascade mode (CASC=TRUE), the external setpoint (the output from the primary loop)
becomes the secondary controller setpoint, and the SEC_SETPOINT block internal setpoint
ISP tracks the external setpoint, thereby ensuring no change in setpoint during transition to
secondary mode. The setpoint tracks the secondary process variable [S_PV] in manual
mode (AUTO=FALSE).
The SEC_CONTROLLER block is a PID_AFB block; it operates in auto mode
(AUTO=TRUE) and tracks the downstream output [OUT] in manual mode (AUTO=FALSE).
The SEC_AUTO_MANUAL block provides manual control of the output. In auto mode the
SEC_CONTROLLER block output becomes the loop output [OUT]. In manual mode the
SEC_AUTO_MANUAL block internal output IOUT becomes the loop output.
On a warm restart, OB100 is called and parameters retain the values they had immediately
before the restart. On a cold restart, OB102 is called and parameters are initialized with the
last downloaded values.
The warm and cold startup behavior of AUTO, P_SP, S_SP, CASC, and OUT is
configurable, allowing the user to override the default PCS 7 behavior described above, if
necessary. As delivered, AUTO will be forced to "Manual", CASC will be forced to "Cascade"
and OUT will be forced to 0.0 on a CPU restart. P_SPand S_SP will be set in accordance
with default PCS 7 behavior.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
To force the P_SP parameter to a specified value on a restart, set the P_RSTRT_SP_FLAG
to true ("Force SP") and configure P_RSTRT_SP_VALUE with the desired forced value. The
P_RSTRT_SP_VALUE will be used to initialize P_SP, if the P_RSTRT_SP_FLAG is true and
either
● the block is forced to start in Auto mode, or
● AUTO is not forced and the block restarts with Auto mode (AUTO="Auto") and in
Cascade (CASC = "Cascade").
If P_RSTRT_SP_FLAG is set to false ("Default"), the P_SP parameter will be set in
accordance with default PCS 7 behavior.
To force the S_SP parameter to a specified value on a restart, set the S_RSTRT_SP_FLAG
to true ("Force SP") and configure S_RSTRT_SP_VALUE with the desired forced value. The
S_RSTRT_SP_VALUE will be used to initialize S_SP, if and only if the S_RSTRT_SP_FLAG
is true and the block restarts in Auto mode (AUTO="Auto") and not in Cascade
(CASC="Secondary"). If S_RSTRT_SP_FLAG is set to false ("Default"), the S_SP parameter
will be set in accordance with default PCS 7 behavior.
To force the CASC parameter to a specified value on a restart, set the RSTRT_CASC_FLAG
to true ("Force CASC") and configure RSTRT_CASC_VALUE with the desired forced value
("Secondary or Cascade"). The RSTRT_CASC_VALUE will be used to initialize CASC, if and
only if the RSTRT_CASC_FLAG is true. If RSTRT_CASC_FLAG is set to false ("Default"),
the CASC parameter will be set in accordance with default PCS 7 behavior. If CASC is true
following a restart, then S_SP will be set to the Primary loop's OUT value.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value. The
RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the RSTRT_OUT_FLAG is
true and the block restarts in Manual mode (AUTO = "Manual"). If RSTRT_OUT_FLAG is set
to false ("Default"), the OUT parameter will be set in accordance with default PCS 7
behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
CASCADE_BLK Input Output (Page 45)
Input
Note
This list differs significantly from the inputs of the CASCADE_BLK block in APACS+. In the
APACS+ version, only the P_PV and S_PV inputs are present (and in APACS+, they are
named PRI_PV and SEC_PV, respectively).
Output
Note
The P_SP and S_SP outputs in APACS+ have been converted to P_SP_OUT and
S_SP_OUT, respectively. They are used to interconnect the set-point value to other entities
on a chart. The OS interaction is handled by the P_SP and S_SP InOut parameters.
The hidden S_ESP output was also added to support OS interaction. The S_ESP output is
driven by the primary PID's OUT output.
Alarm outputs have been added for each analog alarm type.
Input/output
See also
CASCADE: Cascade Controller (Page 41)
1.2.9 DALM_AFB
Function
The Discrete Alarm Function Block (DALM_AFB) is intended for detecting and signaling
abnormal discrete data values. This block is used to detect the discrete states (TRUE or
FALSE) of up to eight inputs. When an alarm state is detected, an ALM output value and the
corresponding NAK output value are set to TRUE. Once the alarm has been acknowledged,
the NAK output value is set to FALSE. A given ALM output value is FALSE when its alarm
state does not match the corresponding IN input value.
The Out-Of-Service (OOS) output value indicates to monitoring devices when the alarm
block has been put in the Out-Of-Service state.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
DALM_AFB Input Output (Page 60)
Input
Note
This list differs from the inputs of the DALM_AFB block in APACS+ as follows:
• There are now eight inputs and enables.
• Only the first alarm's input and enable will be visible, so that the block will look like the
APACS+ HLLDA1 block.
• The parameter EV_ID was added to support the message system.
• Batch parameters BA_NA, BA_ID, STEP_NO are added to pass batch values in alarm
messages.
Output
Note
This list differs from the outputs of the DALM_AFB block in APACS+ as follows:
• There are now eight alarms and NAKs.
• Only the first alarm's output and NAK are visible. This makes the block look similar to the
APACS+ HLLDA1 block.
• The STATUS and CMD outputs have been removed.
• MSG_ERR and MSG_STAT have been added to provide the status of the message
processing. For specific values, see the online help for ALARM_8P.
Input/output
Note
This list differs from the softlist parameters of the DALM_AFB block in APACS+ as follows:
• The PCS 7 OS provides a ringback mechanism, so the ringback parameters have been
removed.
• There are now eight LIMIT, DELAYIN, and DELAYOUT parameters.
See also
DALM_AFB: Discrete Alarm (Page 58)
1.2.10 DISCRETE_ALM_BLK
1.2.10.1 DISCRETE_ALM_BLK
Function
The Discrete Alarm (DISCRETE_ALM_BLK) block is a factory-compiled function block. It is
intended for use as a discrete indicator with alarm. The ALARM output provides the alarm
status of the block. The block signals an alarm on the HMI when the discrete input (DIN) is in
an undesired state.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
DISCRETE_ALM_BLK Input Output (Page 65)
Input
Note
The APACS+ list only includes the DI input. Other inputs are hidden from view, so that from
a user perspective, the DISCRETE_ALM_BLK looks like its APACS+ counterpart. The DI
input was changed to DIN for compatibility with the HMI.
Output
Input/output
See also
DISCRETE_ALM_BLK (Page 64)
1.2.11 EXT_SET_BLK
Function
The External Setpoint Controller (EXT_SET_BLK) block is a factory-compiled function block.
It is intended for use as an external-set PID controller with tracking setpoint. High and low
alarms are provided for the process variable. Another alarm is provided to detect absolute
deviation between the process variable and setpoint.
EXT_SET_BLK is a compiled version of the EXT_SET source chart. Within the chart, there is
a control loop that contains SETPNT_AFB, PID_AFB, and AM_AFB blocks along with
alarming logic.
The SETPOINT block supplies the setpoint [SP_OUT] to the CONTROLLER block. The
SETPOINT block has a ramping feature for internal mode (EXT=FALSE). In external mode
(EXT=TRUE), the external setpoint [ESP] becomes the controller setpoint, and the
SETPOINT block's internal setpoint (ISP) tracks the external setpoint, thereby ensuring no
change in setpoint during transition to internal mode. The setpoint tracks the process
variable [PV] in manual mode (AUTO=FALSE).
The CONTROLLER block is a PID block. It operates in auto mode (AUTO=TRUE) and tracks
the downstream output [OUT] in manual mode (AUTO=FALSE). The AUTO_MANUAL block
provides manual control of the output. In auto mode the CONTROLLER block output
becomes the loop output [OUT]. In manual mode the AUTO_MANUAL block internal output
IOUT becomes the loop output.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
EXT_SET_BLK Input Output (Page 69)
Input
Note
This list differs significantly from the inputs of the EXT_SET_BLK block in APACS+, since the
APACS+ list includes only the PV input and ESP (actually named EXT_SP in APACS+)
input.
*The Update Sampling Time option must be checked when compiling a chart that contains
the EXT_SET_BLK for these values to be automatically generated by the compiler.
Output
Note
The APACS+ SP output was renamed to SP_OUT to avoid conflict with the newly added SP
In/Out parameter. SP_OUT is used to interconnect the set-point value to other entities on a
chart. The OS interaction is handled by the SP InOut parameter.
Input/output
See also
EXT_SET: External Setpoint Controller (Page 66)
1.2.12 MOTOR_A_BLK
Function
The Standard Motor Function Block (MOTOR_A_BLK) provides standard motor start/stop
functions that can be easily interfaced to an operator station. This block is based on the
APACS+ MOTOR_A function block. This block can receive commands from programmed
logic, such as a sequential function chart (SFC) while in automatic mode, or it can receive
operator-entered commands from an operator interface while in manual mode.
The PROOF input receives the state of the motor (TRUE = running and FALSE = stopped).
The OUT output sets the state of the motor (TRUE = running and FALSE = stop).
The AUTO parameter indicates the auto/manual state. This state can be changed external to
the block. It can also be changed by the block itself, depending on In/Out parameters. When
the block is in manual mode (AUTO = FALSE), commands to the block are received via a
write of TRUE to the START or STOP In/Out parameters. The block automatically resets
these values after receiving the command. When the block is in auto mode (AUTO = TRUE),
commands to the block are received via the A_STRT and A_STOP inputs. Since auto mode
is intended for use with commands sent by an SFC, there are some In/Out settings that
accommodate this use:
● When AUTO_TRACK is TRUE, the AUTO mode tracks the MODE input (intended to be
the mode of the SFC), such that AUTO is set TRUE when MODE becomes TRUE.
● If MODE_HOLD_AUTO is TRUE, AUTO is held TRUE as long as MODE is TRUE. When
FALSE, the AUTO value is set when the MODE input value is TRUE, but can then be
manually changed.
● If ACCEPT_ANY_AUTO is TRUE, AUTO is set TRUE whenever the A_STRT (Automatic
Start) or A_STOP (Automatic Stop) input changes state.
When in auto mode, the positive transition of A_STOP (POS_TRANS_ASTOP) value
determines the function of the A_STRT and A_STOP inputs. If the POS_TRANS_ASTOP is
TRUE, the commands need to be FALSE-to-TRUE transitions for both the A_STRT and
A_STOP inputs. Unlike the START and STOP command values, the A_STRT and A_STOP
input values must be reset external to the block. If POS_TRANS_ASTOP value is FALSE,
the same value should be placed on both the A_STRT and A_STOP inputs so that a FALSE-
to-TRUE transition sends a start command and a TRUE-to-FALSE transition sends a stop
command. To avoid the need to generate such a transition for these commands when
POS_TRANS_ASTOP is FALSE, the AUTO_TRANS_REQ value can be set FALSE. The
A_STRT input (with the same value on the A_STOP input) is used as the desired state of the
motor (TRUE = running, FALSE = stop).
There are many permissive/interlock features built into this block. The PERMIT input, if
configured, must be TRUE to permit any start command to take effect. The block has 11
interlock inputs (INT01 ... INT11), but only the first two are visible by default. All of the
configured interlock inputs must be TRUE for the motor to start or remain running; the
INTRLK (Interlock) output value indicates whether all configured interlock inputs are TRUE.
The OVERRD (Override) value represents the override status: when TRUE, any FALSE
interlocks (or permit) are overridden, the INTRLK value is set TRUE, and the motor is
allowed to run. OVERRD may be enabled by a tag write from outside the block. For display
at an HMI, there are In/Out values that hold descriptors for the permit (PERMIT) and the
interlock (INT01...INT11) inputs.
This block contains failure-checking features that set the FAIL value to TRUE when a
problem is detected. The detected problems include:
● Failure to start before the STRT_T has expired
● Failure to stop before the STOP_T has expired
● Loss of proof
● Uncommanded stop due to loss of an interlock (enabled by setting the FAIL_ON_INTRLK
value to TRUE)
● Rejected start command due to missing permissive or interlock (checking for this failure is
always enabled when MODE = TRUE and for all conditions by setting the
FAIL_ON_STRT_CMD value to TRUE.)
The FAIL value is set TRUE when a fail condition is detected. It remains TRUE until it is
reset by a tag write from outside of the block (by acknowledge logic or an operator
command). When FAIL is TRUE, the OUT output value is held FALSE. The ALARM_STATE
value, an integer, is provided to indicate the specific failure condition that occurred.
The READY output indicates that the motor is ready to receive auto commands, where
TRUE indicates that the motor is in auto mode and the interlocks are not overridden. The
STATE output is an integer value that represents the various states of the motor.
The MOTOR_A_BLK supports alarming. An alarm message will be generated if the FAIL
parameter becomes TRUE. In APACS+, this functionality was not part of the MOTOR_A
block, but was instead handled by ProcessSuite.
Interlock Configuration
The Interlock parameters are not extensible as they were in 4-mation. In the PCS 7
implementation of this block, all of the Interlocks exist with only the first two visible by default.
If more than two interlocks are required, each additional interlock must be made visible.
For each required interlock, configure the following:
● Connect a boolean interlock condition to the Interlock input.
● Configure the description so that it is no longer null ("). If the description is left as a null,
the faceplate will not display the status for this interlock. The faceplate is designed to hide
an interlock condition when the interlock description is null.
The warm and cold startup behavior of AUTO and OUT is configurable, allowing the user to
override the default PCS 7 behavior described above if necessary. As delivered, AUTO will
be forced to "Manual" and OUT will be forced to "False" on a CPU restart.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value ("True"
or "False"). The RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the
RSTRT_OUT_FLAG is true. If RSTRT_OUT_FLAG is set to false ("Default"), the OUT
parameter will be set in accordance with default PCS 7 behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
MOTOR_A_BLK Input Output (Page 81)
Input
Note
This list differs from the inputs of the MOTOR_A_AFB block in APACS+ as follows:
• Each input shown above with datatype STRING was a softlist parameter in APACS+.
• The INT01_DESC through INT09_DESC have slightly different names than their APACS+
counterparts. In APACS+ a leading zero was excluded, making the names INT1_DESC
through INT9_DESC.
• EV_ID parameter is a new input and is required for the PCS 7 version to support
alarming. This parameter did not exist in APACS+.
• Restart parameters (RSTRT_... ) did not exist in APACS+.
• LIOP_MAN_SEL and AUT_L added to provide alternate for SET_VAL function.
• Batch parameters BA_EN, OCCUPIED are added to support future batch faceplate view.
• Batch parameters BA_NA, BA_ID, STEP_NO are added to pass batch values in alarm
messages.
• ConfirmChange added to give APACS+ users expected feel of "one-step" operator entry
Output
Note
This list differs from the outputs of the MOTOR_A_AFB block in APACS+ as follows:
• FAIL and AUTO and OVERRD have been moved to In/Out in PCS 7.
• ALARM_STATE is a new output. In APACS+, it was a softlist parameter.
• ALARM is a new output and is present to support the alarming functionality. This output
along with the alarm functionality did not exist in APACS+.
• INTRLK nub is named INT_OK in APACS+. The ProcessSuite name "INTRLK" was
preferred.
Input/output
Note
This list differs from the softlist parameters of the MOTOR_A_AFB block in APACS+ as
follows:
• FAIL, AUTO, and OVERRD which were outputs in APACS+, have been moved to In/Out
in PCS 7. This is necessary to allow writes from the HMI.
• ALARM_STATE was moved to Output.
• The PT_DESC parameter has been eliminated. Instead, the Comment property of the
block is being used to contain the point description information. This is because the
faceplate will automatically display the information provided in the Comment field..
• INT01_DESC through INT10_DESC and PERMIT_DESC have been moved to Inputs.
• STRT_T and STOP_T are named START_T and STOP_T in APACS+. The ProcessSuite
names STRT_T and STOP_T are preferred.
• The following alarm parameters are new: A1EN, A1LIM, A1DELAYIN, A1DELAYOUT,
OOS, DISABLE_ON_OOS. These are needed to support the alarming functionality.
See also
MOTOR_A_BLK: Standard Motor (Page 78)
1.2.13 MOTOR_A_ALM_BLK
Function
This block provides standard motor start/stop equipment module functions (similar to the
MOTOR_1OUT). Device alarming functions are provided by this block.
This factory-compiled block is an encapsulation of the MOTOR_A_BLK block with a discrete
alarm block. To provide thorough alarm reporting, the alarm state value of the
MOTOR_A_BLK block is used to create separate alarms for the following conditions:
● Failure to start (or loss of proof)
● Failure to stop (or unexpected proof)
● Uncommanded stop or rejected start command (due to interlock)
The latched fail state of the MOTOR_A_BLK block is unlatched automatically when the alarm
is acknowledged.
The parameters are generally identically to those of the MOTOR_A_BLK block. See
MOTOR_A_BLK for more details and a complete description of the functionality of this block.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Interlock Configuration
All of the Interlocks for this block are visible by default. For each required interlock, configure
the following:
● Connect a boolean interlock condition to the Interlock input.
● Configure the description so that it is no longer null ("). If the description is left as a null,
the faceplate will not display the status for this interlock. The faceplate is designed to hide
an interlock condition when the interlock description is null.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
MOTOR_A_ALM_BLK Input Output (Page 89)
Input
Output
Input/output
See also
MOTOR_A_ALM: Motor with Alarm (Page 86)
1.2.14 MOTOR_1OUT_BLK
Function
The Motor with One Output (MOTOR_1OUT) is intended for use as a start/stop motor with
one output. The block is designed for a motor with auto/manual operation, pulse commands,
and interlocking. An alarm is provided for failure to reach the desired state.
The [A_STRT] and [A_STOP] inputs are intended to input command pulses from a
sequence. The local variable AUTO determines the source of the start/stop commands. In
auto mode (AUTO=TRUE) the auto parameters [A_STRT] and [A_STOP] are active, and in
manual mode (AUTO=FALSE) the parameters START and STOP are active. START, STOP,
and AUTO are to be manipulated via the operator interface. START and STOP are to be set
TRUE; they are reset automatically.
A positive transition of auto start [A_STRT] or manual start [START] (depending on the
mode) latches the output [OUT]. Interlock [INTRLK] must be TRUE to allow the latch. A
positive transition of auto stop [A_STOP] or manual stop STOP (also mode-dependent)
unlatches the output. The start and stop timers determine if the motor has failed to reach its
desired state, and the failure output [FAIL] will become TRUE accordingly, which triggers the
alarm.
Although the MOTOR_1_OUT block was implemented in ladder logic in APACS, it has been
implemented in SCL in PCS 7 due to differences between APACS+ and PCS 7 ladder logic.
The MOTOR_1OUT is a logical and functional equivalent to the corresponding APACS+
ladder networks. Comments in the provided SCL source code relate elements in the SCL
code to corresponding elements in the original APACS+ ladder network.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
MOTOR_1OUT_BLK Input Output (Page 94)
Input
Note
This list differs from the inputs of the MOTOR_1OUT_BLK block in APACS+ as follows:
• Restart parameters (RSTRT_...) did not exist in APACS+.
• EV_ID and SAMPLE_T did not exist in APACS+.
Output
Input/output
See also
MOTOR_1OUT: Motor with One Output (Page 92)
1.2.15 MOTOR_2OUT_BLK
Function
The Motor with Two Outputs (MOTOR_2OUT) block is intended for use as a start/stop motor
with a start output and a stop output. The block is designed for a motor with auto/manual
operation, pulse commands, and interlocking. An alarm is provided for failure to reach the
desired state.
The [A_STRT] and [A_STOP] inputs are intended to input command pulses from a
sequence. The parameter AUTO determines the source of the start/stop commands. In auto
mode (AUTO=TRUE), the auto parameters [A_STRT] and [A_STOP] are active, and in
manual mode (AUTO=FALSE) the parameters START and STOP are active. START, STOP,
and AUTO are to be manipulated via the operator interface. START and STOP are to be set
TRUE; they are reset automatically.
A positive transition of auto start [A_STRT] or manual start [START] (depending on the
mode) latches the internal START_LATCH and pulses the start output [STRT_O]. Interlock
[INTRLK] must be TRUE to allow the latch. A positive transition of auto stop [A_STOP] or
manual stop STOP (also mode-dependent) unlatches the internal START_LATCH and
pulses the stop output [STOP_O]. The start and stop timers pulse the outputs and determine
if the motor has failed to reach its desired state, and the failure output [FAIL] will become
TRUE accordingly, which triggers the alarm.
Although the MOTOR_2OUT block was implemented in ladder logic in APACS, it has been
implemented in SCL in PCS 7 due to differences between APACS+ and PCS 7 ladder logic.
The MOTOR_2OUT is a logical and functional equivalent to the corresponding APACS+
ladder network. Comments in the provided SCL source code relate elements in the SCL
code to corresponding elements in the original APACS+ ladder network.
Start-up Characteristics
On a warm restart, OB100 is called and parameters retain the values they had immediately
before the restart. On a cold restart, OB102 is called and parameters are initialized with the
last downloaded values.
The warm and cold startup behavior of AUTO is configurable, allowing the user to override
the default PCS 7 behavior described above if necessary. As delivered, AUTO will be forced
to "Manual" and OUT will be forced to "False" on a CPU restart.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
WARNING
Using "Default" for the RSTRT_AUTO_FLAG could result in your process running in
automatic mode after a restart. Use "Forced" for the restart flag and configure the associate
restart value to ensure a known restart state.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
MOTOR_2OUT_BLK Input Output (Page 99)
Input
Note
This list differs from the inputs of the MOTOR_2OUT_BLK block in APACS+ as follows:
• Restart parameters (RSTRT_...) did not exist in APACS+.
• EV_ID and SAMPLE_T did not exist in APACS+.
Output
Input/output
See also
MOTOR_2OUT: Motor with Two Outputs (Page 97)
1.2.16 PID_AFB
Function
The PID_AFB performs Proportional-Integral-Derivative (PID) control functions. It can also
be used as the basis for a PI controller by setting the derivative time value to 0.0 min. The
block utilizes reset feedback, allowing for various control schemes including override, reset
limiting, etc.
When the AUTO value = FALSE, the block operates in tracking mode (OUT value = FDBK
value). The PID block inputs (PV, SP & FDBK) and its outputs (OUT, ERR) are in
engineering units. The PID equation is defined using normalized values. Engineering values
are converted to and from normalized values with user-defined operating limits for both the
process input and process output. The operating limits are obtained from the process
flowsheets or sensor/actuator ranges. Any transition of the INIT input causes execution of
the initialization equations which recalculate the reset component so that the OUT value
does not experience a bump due to proportional action.
Note
Normal limits for the TI In/Out value are from 0.001 to 4000.0. In the special case of TI =
4000.0, all integral action is removed from the output calculation.
See also
PID_AFB Input Output (Page 102)
Input
Note
This list differs from the inputs of the PID_AFB block in APACS+ as follows:
• The SAMPLE_T input is required for the block to obtain the scan rate.
Output
Input/output
See also
PID_AFB: Proportional-Integral-Derivative (Page 101)
1.2.17 PRIMARY_BLK
Function
The Primary Controller (PRIMARY_BLK) block is a factory-compiled function block. It is
intended for use as a primary single-loop PID controller with tracking setpoint as part of a
cascade control circuit. The PRIMARY_BLK block is designed to be used with the
SECONDARY_BLK block to form a cascade circuit when it is preferable to control the
primary and secondary loops separately. Normally, the output from the primary loop is to be
the setpoint to the secondary loop, and the cascade status of the secondary loop is to be fed
to the primary loop. High and low alarms are provided for the process variable, and an alarm
is provided for absolute deviation between process variable and setpoint.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
PRIMARY_BLK Input Output (Page 107)
Input
Note
This list differs significantly from the inputs of the PRIMARY_BLK block in APACS+. In
APACS+, only the PV, FDBK and CASC_S inputs are present.
Output
Note
The APACS+ SP output has been converted to SP_OUT. SP_OUT is used to interconnect
the set-point value to other entities on a chart. The OS interaction is handled by the SP InOut
parameter.
Input/output
See also
PRIMARY: Primary Controller (Page 104)
1.2.18 RATIO_SET_BLK
Function
The Ratio Setpoint Controller (RATIO_SET_BLK) block is a factory-compiled function block.
It is intended for use as a ratio-set PID controller with tracking setpoint. An external input is
multiplied by a desired ratio value (i.e. a controlled variable divided by wild variable) to
calculate the external setpoint. The process variable is divided by the external input for
display of the actual ratio. Both high and low alarms are provided for the process variable,
and an additional alarm is provided to detect an absolute deviation between the process
variable and setpoint.
RATIO_SET_BLK is a compiled version of the RATIO_SET source chart. Within the chart,
there is a control loop that contains PID_AFB and AM_AFB blocks along with alarming logic.
The loop also uses two SETPNT_AFB blocks; the RATIO block provides an input of the ratio
calculation, the result of which is the external setpoint of the SETPOINT block.
The RATIO block holds the desired ratio, modified via the computer setpoint (RAT_DES),
and the low and high range values of the ratio. The RATIO_MIN and RATIO_MAX values are
used by the ACT_RAT_LIMIT block (described below). The ratio input [RAT_INP] is
multiplied by the desired ratio (from the RATIO block) to calculate the external setpoint. The
SETPOINT block supplies the setpoint [SP] to the CONTROLLER block. The SETPOINT
block has a ramping feature for internal mode (EXT=FALSE). In external mode
(EXT=TRUE), the calculated external setpoint becomes the controller setpoint, and the
SETPOINT block internal setpoint (ISP) tracks the external setpoint, thereby ensuring no
change in setpoint during transition to internal mode. The setpoint tracks the process
variable [PV] in manual mode (AUTO=FALSE).
The CONTROLLER block is a PID_AFB block. It operates in auto mode (AUTO=TRUE) and
tracks the downstream output [OUT] in manual mode (AUTO=FALSE). The AUTO_MANUAL
block provides manual control of the output. In auto mode, the CONTROLLER block output
becomes the loop output [OUT]. In manual mode, the AUTO_MANUAL block's internal
output (IOUT) becomes the loop output.
The ACT_RAT_LIMIT block is used to apply limits to the actual ratio [RAT_ACT], which is the
quotient of the process variable and the external input.
RAT_DES, if and only if the RSTRT_ RAT_DES _FLAG is true and the block restarts in Auto
mode (AUTO="Auto"). If RSTRT_ RAT_DES _FLAG is set to false ("Default"), the RAT_DES
parameter will be set in accordance with default PCS 7 behavior.
To force the EXT parameter to a specified value on a restart, set the RSTRT_EXT_FLAG to
true ("Force EXT") and configure RSTRT_EXT_VALUE with the desired forced value
("Internal or External"). The RSTRT_EXT_VALUE will be used to initialize EXT, if and only if
the RSTRT_EXT_FLAG is true. If RSTRT_EXT_FLAG is set to false ("Default"), the EXT
parameter will be set in accordance with default PCS 7 behavior. Forcing the EXT parameter
to "External" will cause the SP to be set to the ESP, thereby overriding the SP restart
parameter settings.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value. The
RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the RSTRT_OUT_FLAG is
true and the block restarts in Manual mode (AUTO = "Manual"). If RSTRT_OUT_FLAG is set
to false ("Default"), the OUT parameter will be set in accordance with default PCS 7
behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
RATIO_SET_BLK Input Output (Page 117)
Input
Output
Input/output
See also
RATIO_SET: Ratio Setpoint Controller (Page 113)
1.2.19 SECONDARY_BLK
Function
The Secondary Controller (SECONDARY_BLK) block is a factory-compiled function block. It
is intended for use as an external-set PID controller with tracking setpoint as part of a
cascade circuit. The SECONDARY_BLK block is designed to be used with the
PRIMARY_BLK block to form a cascade circuit when it is preferable to control the primary
and secondary loops separately. Normally, the output from the primary loop is to be the
setpoint to the secondary loop, and the cascade status of the secondary loop is to be fed to
the primary loop. High and low alarms are provided for the process variable, and an alarm is
provided for absolute deviation between process variable and setpoint.
SECONDARY_BLK is a compiled version of the SECONDARY source chart. Within the
chart, there is a control loop that contains SETPNT_AFB, PID_AFB, and AM_AFB blocks
along with alarming logic.
The SETPOINT block supplies the setpoint [SP] to the CONTROLLER block. The
SETPOINT block has a ramping feature for internal mode (EXT=FALSE). In external mode
(EXT=TRUE), the external setpoint [ESP] becomes the controller setpoint, and the
SETPOINT block internal setpoint ISP tracks the external setpoint, thereby ensuring no
change in setpoint during transition to internal mode. The setpoint tracks the process
variable [PV] in manual mode (AUTO=FALSE).
The CONTROLLER block is a PID_AFB block. It operates in auto mode (AUTO=TRUE) and
tracks the downstream output [OUT] in manual mode (AUTO=FALSE). The AUTO_MANUAL
block provides manual control of the output. In auto mode, the CONTROLLER block output
becomes the loop output [OUT]. In manual mode, the AUTO_MANUAL block internal output
IOUT becomes the loop output.
The warm and cold startup behavior of AUTO, SP, EXT, and OUT is configurable, allowing
the user to override the default PCS 7 behavior described above if necessary. As delivered,
AUTO will be forced to "Manual", EXT will be forced to "Internal" and OUT will be forced to
0.0 on a CPU restart. SP will be set in accordance with default PCS 7 behavior.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
To force the SP parameter to a specified value on a restart, set the RSTRT_SP_FLAG to
true ("Force SP") and configure RSTRT_SP_VALUE with the desired forced value. The
RSTRT_SP_VALUE will be used to initialize SP, if and only if the RSTRT_SP_FLAG is true
and the block restarts in Auto mode (AUTO="Auto"). If RSTRT_SP_FLAG is set to false
("Default"), the SP parameter will be set in accordance with default PCS 7 behavior.
To force the EXT parameter to a specified value on a restart, set the RSTRT_EXT_FLAG to
true ("Force EXT") and configure RSTRT_EXT_VALUE with the desired forced value
("Internal or External"). The RSTRT_EXT_VALUE will be used to initialize EXT, if and only if
the RSTRT_EXT_FLAG is true. If RSTRT_EXT_FLAG is set to false ("Default"), the EXT
parameter will be set in accordance with default PCS 7 behavior. Forcing the EXT parameter
to "External" will cause the SP to be set to the ESP, thereby overriding the SP restart
parameter settings.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value. The
RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the RSTRT_OUT_FLAG is
true and the block restarts in Manual mode (AUTO = "Manual"). If RSTRT_OUT_FLAG is set
to false ("Default"), the OUT parameter will be set in accordance with default PCS 7
behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
SECONDARY_BLK Input Output (Page 127)
Input
Note
This list differs significantly from the inputs of the SECONDARY_BLK block in APACS+. In
APACS+, only the PV and EXT_SP inputs are present. EXT_SP is now ESP.
Output
Note
The SP output has been converted to SP_OUT. SP_OUT is used to interconnect the set-
point value to other entities on a chart. The OS interaction is handled by the SP InOut
parameter.
Input/output
See also
SECONDARY: Secondary Controller (Page 124)
1.2.20 SETPNT_AFB
Function
The Setpoint Function Block (Setpnt_AFB) manages the setpoint value (process operating
value) which can be derived from two user-specified sources:
● Internal setpoint (ISP)
● External setpoint (ESP)
The setpoint (SP) value is limited by both low and high limits (LOLIM and HILIM) to prevent
the setpoint from being inadvertently driven beyond a process operating limit. The internal
setpoint can be changed via the Computer Setpoint (CSP) or the Setpoint function block
itself (in track or ramp mode).
The Setpoint function block may write either the track variable, (PV) (presumably the control
loop process variable), or the External Setpoint (ESP) to its internal setpoint, depending on
the modes and options selected. The computer setpoint is written to by an operator
command. The SP value is assigned to CSP as well. All values are in engineering units.
The Setpoint function block has a ramping feature to create a ramping setpoint. Ramping is
allowed only when the AUTO input is TRUE and the EXTRNL input is FALSE. The ramp
start-point is the ISP value. The TARGET value is the intended endpoint. Either a ramp time
(RTIME) or a ramp rate (RRATE) controls the ramp slope. The USE_RRATE_SW switch
determines which value is used: FALSE for RTIME, TRUE for RRATE. When the RAMP
value makes a FALSE-to-TRUE transition, the block initializes the ramp mode. As long as
the RAMP and AUTO values are TRUE, and the EXTRNL value is FALSE, ramping is in
effect. The SETPNT_AFB function block does not ramp while in either manual or external
modes. If the block goes into external or manual while it previously had been in automatic
and ramping, the ramping mode is turned off. To re-enable ramping, the block has to be
placed into internal mode (EXTRNL = FALSE) and automatic mode (AUTO =TRUE), and
then placed in the ramp mode (RAMP = TRUE). The SP output value reflects the ramping of
the block and the RTIME output value decrements to show the remaining ramp time. The
RRATE value must always be entered as positive; ramp direction is based on the
relationship of the target and the starting point. The RRATE value is updated if the RTIME
value is used, and the RTIME value is updated if the RRATE value is used. When the
TARGET value has been reached, the RAMP input is reset.
The HOLD mode is in effect if the RAMP input value changes from TRUE to FALSE while
the RTIME value is greater than zero. The HOLD output value = TRUE to indicate this mode.
While in the hold mode, the SP output value is held at its last value. After a FALSE-to-TRUE
transition of the RAMP input while the RTIME value is greater than zero, but less than its
initial value, the ramp mode is continued. The ramp mode can be continued in two different
ways. First, if none of the three ramp values (TARGET, RTIME or RRATE) have changed,
the ramp is continued using the same ramp rate as previous to the HOLD mode, and the
current ISP as the restart value; however, the remaining ramp time (RTIME) value is
recalculated. Secondly, if any of the three ramp values (TARGET, RTIME, or RRATE) have
changed, the new inputs are used just as if the ramp mode was being initialized for the first
time. To cancel a ramp, first place the block in hold mode (RAMP = FALSE), then set the
RTIME value to zero for a time mode ramp, or set the RRATE value to zero for a rate mode
ramp.
Note
When a ramp is finished, the RAMP input/output is reset (RAMP = FALSE).
WARNING
Using "Default" for the RSTRT_AUTO_FLAG could result in your process running in
automatic mode after a restart. Use "Forced" for the restart flags and configure the
associated restart values to ensure a known restart state.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
To force the SP parameter to a specified value on a restart, set the RSTRT_SP_FLAG to
true ("Force SP") and configure RSTRT_SP_VALUE with the desired forced value. The
RSTRT_SP_VALUE will be used to initialize SP, if and only if the RSTRT_SP_FLAG is true
and the block restarts in Auto mode (AUTO="Auto"). If RSTRT_SP_FLAG is set to false
("Default"), the SP parameter will be set in accordance with default PCS 7 behavior.
To force the EXT parameter to a specified value on a restart, set the RSTRT_EXT_FLAG to
true ("Force EXT") and configure RSTRT_EXT_VALUE with the desired forced value
("Internal or External"). The RSTRT_EXT_VALUE will be used to initialize EXT, if and only if
the RSTRT_EXT_FLAG is true. If RSTRT_EXT_FLAG is set to false ("Default"), the EXT
parameter will be set in accordance with default PCS 7 behavior. Forcing the EXT parameter
to "External" will cause the SP to be set to the ESP, thereby overriding the SP restart
parameter settings.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
See also
SETPNT_AFB Input Output (Page 136)
Input
Note
This list differs from the inputs of the SETPNT_AFB block in APACS+ as follows:
• New parameters were added for restart functionality.
• AUTO and RAMP have been moved from input to input/output.
Output
Note
This list differs from the outputs of the SETPNT_AFB block in APACS+ as follows:
• RTIME has been moved from output to input/output.
Input/output
Note
This list differs from the softlist parameters of the SETPNT_AFB block in APACS+ as follows:
• AUTO and RAMP have been moved from input to input/output.
• RTIME has been moved from output to input/output.
See also
SETPNT_AFB: Setpoint (Page 134)
1.2.21 SINGLE_LOOP_BLK
1.2.21.1 SINGLE_LOOP_BLK
Function
The Single Loop Controller (SINGLE_LOOP_BLK) block is a factory-compiled function block.
It is intended for use as a single-loop PID controller with a tracking setpoint. Both high and
low alarms are provided for the process variable. Another alarm is provided to detect an
absolute deviation between the process variable and setpoint.
SINGLE_LOOP_BLK is a compiled version of the SINGLE_LOOP source chart. Within the
chart, there is a control loop that contains SETPNT_AFB, PID_AFB, and AM_AFB blocks
along with alarming logic.
The SETPOINT block supplies the setpoint [SP] to the CONTROLLER block. The
SETPOINT block has a ramping feature for auto mode. The setpoint tracks the process
variable [PV] in manual mode (AUTO=FALSE). The CONTROLLER block is a PID_AFB
block. It operates in auto mode (AUTO=TRUE) and tracks the downstream output [OUT] in
manual mode (AUTO=FALSE). The AUTO_MANUAL block provides manual control of the
output. In auto mode the CONTROLLER block output becomes the loop output [OUT]. In
manual mode the AUTO_MANUAL block internal output IOUT becomes the loop output.
This block is called in the watchdog interrupt OB into which the block is installed (for
example, OB32). Additionally, it is called in OB100 and in OB102 (see Start-up
Characteristics).
Start-up Characteristics
On a warm restart, OB100 is called and parameters retain the values they had immediately
before the restart. On a cold restart, OB102 is called and parameters are initialized with the
last downloaded values.
The warm and cold startup behavior of AUTO, SP, and OUT is configurable, allowing the
user to override the default PCS 7 behavior described above if necessary. As delivered,
AUTO will be forced to "Manual" and OUT will be forced to 0.0 on a CPU restart. SP will be
set in accordance with default PCS 7 behavior.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
To force the SP parameter to a specified value on a restart, set the RSTRT_SP_FLAG to
true ("Force SP") and configure RSTRT_SP_VALUE with the desired forced value. The
RSTRT_SP_VALUE will be used to initialize SP, if and only if the RSTRT_SP_FLAG is true
and the block restarts in Auto mode (AUTO="Auto"). If RSTRT_SP_FLAG is set to false
("Default"), the SP parameter will be set in accordance with default PCS 7 behavior.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value. The
RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the RSTRT_OUT_FLAG is
true and the block restarts in Manual mode (AUTO = "Manual"). If RSTRT_OUT_FLAG is set
to false ("Default"), the OUT parameter will be set in accordance with default PCS 7
behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
SINGLE_LOOP_BLK Input Output (Page 141)
Input
Output
Note
The APACS+ output was renamed to SP_OUT to avoid conflict with the newly added SP
In/Out parameter. SP_OUT is used to interconnect the set-point value to other entities on a
chart. The OS interaction is handled by the SP In/Out parameter.
Input/output
See also
SINGLE_LOOP_BLK (Page 138)
1.2.22 SINGLE_LP_EM_BLK
Function
The Single Loop Controller with Emergency Manual (SINGLE_LP_EM_BLK) block is a
factory-compiled function block. It is intended for use as a single-loop PID controller with
tracking setpoint and Emergency Manual functionality. The External Value and Emergency
Manual command inputs allow the controller output to be immediately forced to any desired
value. High and low alarms are provided for the process variable, and an additional alarm is
provided to detect an absolute deviation between the process variable and setpoint.
SINGLE_LP_EM_BLK is a compiled version of the SINGLE_LP_EM source chart. Within the
chart, there is a control loop that contains SETPNT_AFB, PID_AFB, and AM_AFB blocks
along with alarming logic.
The SETPOINT block supplies the setpoint [SP] to the CONTROLLER block. The
SETPOINT block has a ramping feature for auto mode. The setpoint tracks the process
variable [PV] in manual or emergency Manual mode (AUTO=FALSE or EM=TRUE). The
CONTROLLER block is a PID_AFB block; it operates when AUTO=TRUE and EM=FALSE
and tracks the downstream output [OUT] in manual or Emergency Manual mode. The
AUTO_MANUAL block provides Emergency Manual and manual control of the output. In
Emergency Manual mode, the external value [EXTV] becomes the loop output [OUT]. In auto
mode, the CONTROLLER block output becomes the loop output. In manual mode, the
AUTO_MANUAL block internal output (IOUT) becomes the loop output.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value. The
RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the RSTRT_OUT_FLAG is
true and the block restarts in Manual mode (AUTO = "Manual"). If RSTRT_OUT_FLAG is set
to false ("Default"), the OUT parameter will be set in accordance with default PCS 7
behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
Input
Note
This list differs significantly from the inputs of the SINGLE_LP_EM_BLK block in APACS+.
The APACS+ list only includes the PV, EXTV, and EM inputs.
*The Update Sampling Time option must be checked when compiling a chart that contains
the SINGLE_LP_EM_BLK for this value to be automatically generated by the compiler.
Output
Note
The APACS+ SP output was renamed to SP_OUT to avoid conflict with the newly added SP
In/Out parameter. SP_OUT is used to interconnect the set-point value to other entities on a
chart. The OS interaction is handled by the SP In/Out parameter.
Input/ouput
1.2.23 SINGLE_LP_SS_BLK
Function
The Single Loop Controller with Standby Sync (SINGLE_LP_SS_BLK) block is a factory-
compiled function block. It is intended for use as a single-loop PID controller with tracking
setpoint and standby sync functionality. The External Value and Standby Sync command
inputs allow the controller output to be immediately forced to any desired value. High and low
alarms are provided for the process variable, and an additional alarm is provided to detect an
absolute deviation between the process variable and setpoint.
SINGLE_LP_SS_BLK is a compiled version of the SINGLE_LP_SS source chart. Within the
chart, there is a control loop that contains SETPNT_AFB, PID_AFB, and AM_AFB blocks
along with alarming logic.
The SETPOINT block supplies the setpoint [SP] to the CONTROLLER block. The
SETPOINT block has a ramping feature for auto mode. The setpoint tracks the process
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
SINGLE_LP_SS_BLK Input Output (Page 159)
Input
Note
This list differs significantly from the inputs of the SINGLE_LP_SS_BLK block in APACS+.
The APACS+ list only includes the PV, EXTV, and SS inputs.
*The Update Sampling Time option must be checked when compiling a chart that contains
the SINGLE_LP_SS_BLK for this value to be automatically generated by the compiler.
Output
Note
The APACS+ SP output was renamed to SP_OUT to avoid conflict with the newly added SP
In/Out parameter. SP_OUT is used to interconnect the set-point value to other entities on a
chart. The OS interaction is handled by the SP In/Out parameter.
Input/ouput
See also
SINGLE_LP_SS: Single Loop Controller with Standby Sync (Page 156)
1.2.24 VALVE_A_ALM_BLK
Function
This block provides standard valve open/close equipment module functions (similar to the
BLK_VLV_1OUT). Device alarming functions are provided by this block.
This factory-compiled block is an encapsulation of the VALVE_A_BLK block with a 4-element
discrete alarm block. To provide thorough alarm reporting, the alarm state value of the
VALVE_A_BLK block is used to create separate alarms for the following conditions:
● Failure to open (or loss of open verify)
● Failure to close (or loss of close verify)
● Uncommanded close/open or rejected command (due to interlock)
● Failed limit switch (Open and close verify inputs are set)
The latched fail state of the VALVE_A_BLK block is unlatched automatically when the alarm
is acknowledged.
The parameters are generally identical to those of the VALVE_A_BLK block. See
VALVE_A_BLK for more details and a complete description of the functionality of this block.
The warm and cold startup behavior of AUTO and OUT is configurable, allowing the user to
override the default PCS 7 behavior described above if necessary. As delivered, AUTO will
be forced to "Manual" and OUT will be forced to "False" on a CPU restart.
To force the AUTO parameter to a specified value on a restart, set the RSTRT_AUTO_FLAG
to true ("Force AUTO") and configure RSTRT_AUTO_VALUE with the desired forced value
("Auto" or "Manual"). The RSTRT_AUTO_VALUE will be used to initialize AUTO, if and only
if the RSTRT_AUTO_FLAG is true. If RSTRT_AUTO_FLAG is set to false ("Default"), the
AUTO parameter will be set in accordance with default PCS 7 behavior.
To force the OUT parameter to a specified value on a restart, set the RSTRT_OUT_FLAG to
true ("Force OUT") and configure RSTRT_OUT_VALUE with the desired forced value ("True"
or "False"). The RSTRT_OUT_VALUE will be used to initialize OUT, if and only if the
RSTRT_OUT_FLAG is true. If RSTRT_OUT_FLAG is set to false ("Default"), the OUT
parameter will be set in accordance with default PCS 7 behavior.
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Interlock Configuration
All of the Interlocks for this block are visible by default. For each required interlock, configure
the following:
● Connect a boolean interlock condition to the Interlock input.
● Configure the description so that it is no longer null ("). If the description is left as a null,
the faceplate will not display the status for this interlock. The faceplate is designed to hide
an interlock condition when the interlock description is null.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
VALVE_A_ALM_BLK Input Output (Page 168)
Input
Output
Input/output
See also
VALVE_A_ALM: Valve with Alarm (Page 166)
1.2.25 VALVE_A_AFB
Function
The Standard Valve Function Block (VALVE_A_AFB) provides standard motor start/stop
functions that can be easily interfaced to an operator station. This block is based on the
APACS+ VALVE_A function block. This block can receive commands from programmed
logic, such as a sequential function chart (SFC) while in automatic mode, or it can receive
operator-entered commands from an operator interface while in manual mode.
The OP_VER and CL_VER inputs receive the open and close verify signals indicating the
state of the valve. A TRUE indicates that the condition is verified. This block accommodates
fail-open valves, as well as the normal fail-closed valves. The OUT output value establishes
the state of the valve, where TRUE = open and FALSE = close for a fail-close valve, and
TRUE = close and FALSE = open for a fail-open valve.
The AUTO parameter indicates the auto/manual state. This state can be changed external to
the block. It can also be changed by the block itself, depending on In/Out parameters. When
the block is in manual mode (AUTO = FALSE), commands to the block are received via a
write of TRUE to the OPEN or CLOSE In/Out parameters. The block automatically resets
these values after receiving the command. When the block is in auto mode (AUTO = TRUE),
commands to the block are received via the A_OPEN and A_CLSE inputs. Since auto mode
is intended for use with commands sent by an SFC, there are some In/Out settings that
accommodate this use:
● When AUTO_TRACK is TRUE, the AUTO mode tracks the MODE input (intended to be
the mode of the SFC), such that AUTO is set TRUE when MODE becomes TRUE.
● If MODE_HOLD_AUTO is TRUE, AUTO is held TRUE as long as MODE is TRUE. When
FALSE, the AUTO value is set when the MODE input value is TRUE, but can then be
manually changed.
● If ACCEPT_ANY_AUTO is TRUE, AUTO is set TRUE whenever the A_OPEN (Automatic
Open) or A_CLSE (Automatic Close) input changes state.
When in auto mode, the positive transition of the POS_TRANS_ACLSE value determines the
function of the A_OPEN and A_CLSE inputs. If the POS_TRANS_ACLSE value is TRUE, the
commands need to be FALSE-to-TRUE transitions for both the A_OPEN and A_CLSE
inputs. Unlike the OPEN and CLOSE command values, the A_OPEN and A_CLSE input
values must be reset external to the block. If the POS_TRANS_ACLSE value is FALSE, the
same value should be placed on both the A_OPEN and A_CLSE inputs so that a FALSE-to-
TRUE transition sends an open command and a TRUE-to-FALSE transition sends a close
command. To avoid the need to generate such a transition for these commands when the
POS_TRANS_ACLSE is FALSE, the AUTO_TRANS_REQ value can be set FALSE. The
A_OPEN input (with the same value on the A_CLSE input) is used as the desired state of the
valve (TRUE = open, FALSE = closed).
There are many permissive/interlock features built into this block. The PERMIT input, if
configured, must be TRUE to permit any open command (or close command if fail-open) to
take effect. The block has 10 interlock inputs (INT01 ... INT10), but only the first two are
visible by default. All of the configured interlock inputs must be TRUE for the valve to change
to the non-fail-safe state; the INTRLK (Interlock) value indicates whether all configured
interlock inputs are TRUE. The OVERRD (Override) value represents the override status:
when TRUE, any FALSE interlocks (or permit) are overridden, the INTRLK value is set
TRUE, and the valve is allowed to leave the fail-safe state. OVERRD may be enabled by a
tag write from outside the block. For display at an HMI, there are In/Out values that hold
descriptors for the permit (PERMIT) and the interlock (INT01...INT10) inputs.
This block contains failure-checking features that set the FAIL output value to TRUE when a
problem is detected. The detected problems include:
● Failure to open before the OPEN_T has expired
● Failure to close before the CLOS_T has expired
● Loss of verify (=UNAVAILABLE data quality or FALSE)
● Uncommanded close (or open for fail open) due to loss of an interlock (enabled by setting
the FAIL_ON_INTRLK value to TRUE)
● Rejected open command due to missing permissive or interlock (checking for this failure
is always enabled when MODE = TRUE and for all conditions by setting the
FAIL_ON_OPEN_CMD value to TRUE.)
The FAIL value is set TRUE when a fail condition is detected. It remains TRUE until it is
reset by a tag write from outside of the block (by acknowledge logic or an operator
command). The ALARM_STATE value, an integer, is provided to indicate the specific failure
condition that occurred.
The READY output indicates that the valve is ready to receive auto commands, where TRUE
indicates that the valve is in auto mode and the interlocks are not overridden. The STATE
output is an integer value that represents the various states of the valve.
The VALVE_A_AFB supports alarming. An alarm message will be generated if the FAIL
parameter becomes TRUE. In APACS+, this functionality was not part of the VALVE_A
block, but instead handled by ProcessSuite.
Interlock Configuration
The Interlock parameters are not extensible as they were in 4-mation. In the PCS 7
implementation of this block, all of the Interlocks exist with only the first two visible by default.
If more than two interlocks are required, each additional interlock must be made visible.
For each required interlock, configure the following:
WARNING
Using "Default" for the RSTRT_OUT_FLAG could result in your output device retaining its
last operating state after a restart. Similarly, using "Default" for the RSTRT_AUTO_FLAG
could result in your process running in automatic mode after a restart. Use "Forced" for the
restart flags and configure the associated restart values to ensure a known restart state.
If restart parameter values are changed offline, the configuration must be compiled (changes
only) and downloaded (changes only) to the controller in order for the settings to take effect
upon restart. If restart parameter values are changed online (via CFC Test mode), the
configuration must be compiled (entire program) and downloaded (entire program) to the
controller in order for the settings to take effect upon cold restart. This step is not necessary
for the online changes to take effect upon a warm restart.
Message Characteristics
Note
During runtime, the string $$BlockComment$$ will be replaced by the comment for the FB
instance that is in alarm.
See also
VALVE_A_AFB Input Output (Page 175)
Input
Note
This list differs from the inputs of the VALVE_A_AFB block in APACS+ as follows:
• Each input shown above with datatype STRING was a softlist parameter in APACS+.
• The INT01_DESC through INT09_DESC have slightly different names than their APACS+
counterparts. In APACS+ a leading zero was excluded, making the names INT1_DESC
through INT9_DESC.
• EV_ID parameter is a new input and is required for the PCS 7 version to support
alarming. This parameter did not exist in APACS+.
• Restart parameters (RSTRT_... ) did not exist in APACS+.
• LIOP_MAN_SEL and AUT_L added to provide alternate for SET_VAL function.
• Batch parameters BA_EN, OCCUPIED are added to support future batch faceplate view.
• Batch parameters BA_NA, BA_ID, STEP_NO are added to pass batch values in alarm
messages.
• ConfirmChange added to give APACS+ users expected feel of "one-step" operator entry
Output
Note
This list differs from the outputs of the VALVE_A_AFB block in APACS+ as follows:
• FAIL and AUTO and OVERRD have been moved to In/Out in PCS 7.
• ALARM_STATE is a new output. In APACS+, it was a softlist parameter.
• ALARM is a new output and is present to support the alarming functionality. This output
along with the alarm functionality did not exist in APACS+.
• INTRLK nub is named INT_OK in APACS+. The ProcessSuite name "INTRLK" is
preferred.
Input/output
Note
This list differs from the softlist parameters of the VALVE_A_AFB block in APACS+ as
follows:
• FAIL, AUTO, and OVERRD which were outputs in APACS+, have been moved to In/Out
in PCS 7. This is necessary to allow writes from the HMI.
• ALARM_STATE was moved to Output.
• The PT_DESC parameter has been eliminated. Instead, the Comment property of the
block has been used to contain the point description information. This is because the
faceplate will automatically display the information provided in the Comment field.
• INT01_DESC through INT10_DESC and PERMIT_DESC have been moved to Inputs.
• FAIL_OPEN is named FAIL_OPEN_VALVE in APACS.
• OPEN_T and CLOS_T are named OPEN_TIME and CLOSE_TIME in APACS+.
• The following alarm parameters are new: A1EN, A1LIM, A1DELAYIN, A1DELAYOUT,
OOS, DISABLE_ON_OOS. These are needed to support the alarming functionality.
See also
VALVE_A_AFB: Standard Valve (Page 172)
A PCS 7 template is to be used in the creation of the controller configuration. Each template
contains a function block that has a corresponding symbol and faceplate. The templates
provide all the logic required to use the library blocks. All that is necessary on the part of the
user is to replace the logical connections with actual addresses. The template charts can be
modified or expanded to meet user needs.
PCS 7
Continuous Function Chart (CFC) Template
ANALOG_ALM_AT
BLK_VLV_1OUT_AT
BLK_VLV_2OUT_AT
CASCADE_AT
DISCRETE_ALM_AT
EXT_SET_AT
MOTOR_1OUT_AT
MOTOR_2OUT_AT
PRIMARY_SECONDARY_AT
RATIO_SET_AT
SINGLE_LOOP_AT
SINGLE_LP_SS_AT
PCS 7
Continuous Function Chart (CFC) Template
MOTOR_A_ALM_AT
VALVE_A_ALM_AT
1.3.1 ANALOG_ALM_AT
This template can be used as an analog indicator with alarms. Both high and low alarms are
provided for the process variable. The PV input accepts the process variable and the
ALARM output provides the alarm status. The template contains an input driver, along with
the ALARM (ANALOG_ALM_AFB) block.
Interconnections
The signal to be monitored must be connected to the VALUE input of the PV_IN block via
symbolic addressing.
Simulation
Measured value monitoring can be tested during the configuring phase. This merely requires
that input SIM_ON of the PV_IN block be switched on, and that the relevant value be preset
at input SIM_V.
Parameter Assignment
To scale the input signal, set the Process Value engineering high via PV_IN's VHRANGE
input and the Process Value engineering low via PV_IN's VLRANGE input. These
engineering limits will be conveyed to the ALARM's PV_EUMAX and PV_EUMIN,
respectively.
By default, the HIGH and LOW alarms are enabled. The various alarms should be
enabled/disabled as needed.
Configure the following parameters (which are marked for IEA) in the ALARM for your
application:
● All high/low alarm limits (H_LIM, L_LIM)
Faults
Channel faults are detected by the input driver and are assigned to the QBAD input of block
ALARM. An alarm message will then be posted if QUAL_EN is enabled.
See also
ANALOG_ALM_BLK (Page 24)
1.3.2 BLK_VLV_1OUT_AT
This template can be used as a block valve open/close with one output. It is designed for a
normally closed valve with auto/manual operation, pulse commands, and interlocking. An
alarm is provided for failure to reach the desired state. The VALVE block has inputs
OP_VER, CL_VER, A_OPEN, A_CLSE, and INTRLK for the open verify, close verify, auto
open command, auto close command, and interlock; and outputs OUT and FAIL for the
output, and failure status of the valve, respectively. The VALVE circuit contains, apart from
the VALVE block, two digital input drivers and a digital output driver.
Interconnections
The signal for the open feedback must be connected to the VALUE input of block FB_OPEN
via symbolic addressing. The signal for the closed feedback must be connected to the
VALUE input of block FB_CLOSED via symbolic addressing. The VALUE output of the
OUTPUT block must be connected via symbolic addressing to the signal for of the VALVE to
be controlled.
Simulation
If there is no feedback, the simulation can be switched on at driver blocks FB_OPEN and
FB_CLOSED (SIM_ON = 1). A connection is provided from the VALVE output OUT to a
TIMER_P delay block (SIMULATION) IO input. The SIMULATION QO output is connected to
the input SIM_I of block FB_OPEN. It is also connected to input SIM_I of block FB_CLOSED
after being inverted. Simulation of valve limit switches is accomplished by delaying the
VALVE block's OUT signal. Note than the TIME0 parameter should be less than VALVE's
TRAV_T and CLOS_T parameter.
Parameter Assignment
Configure the following parameters for your application:
● To set the VALVE block's maximum allowed time to open and close, set the parameter
TRAV_T of the VALVE block.
● Interlock
Faults
Channel faults are detected by the input and output drivers.
See also
BLK_VLV_1OUT_BLK (Page 32)
1.3.3 BLK_VLV_2OUT_AT
This template can be used as a block valve open/close with an open output and a close
output. It is designed for a valve with auto/manual operation, pulse commands, and
interlocking. An alarm is provided for failure to reach the desired state. The VALVE block has
inputs OP_VER, CL_VER, A_OPEN, A_CLSE, and INTRLK for the open verify, close verify,
auto open command, auto close command, and interlock; and outputs OP_OUT, CL_OUT,
and FAIL for the open output, close output, and failure status of the valve, respectively. The
VALVE circuit contains, apart from the VALVE block, two digital input drivers and two digital
output drivers.
Interconnections
The signal for the open feedback must be connected to the VALUE input of block FB_OPEN
via symbolic addressing. The signal for the closed feedback must be connected to the
VALUE input of block FB_CLOSED via symbolic addressing. The VALUE output of the
OPEN_OUTPUT block must be connected via symbolic addressing to the open signal for the
valve to be controlled. The VALUE output of the CLOSE_OUTPUT block must be connected
via symbolic addressing to the close signal for output of the valve to be controlled.
Simulation
If there is no feedback, the simulation can be switched on at driver blocks FB_OPEN and
FB_CLOSED (SIM_ON = 1). An SR_FF block (SIMULATION) is used to implement the
simulation of the feedback.
Parameter Assignment
Configure the following parameters for your application:
● To set the VALVE block's maximum allowed time to open and close, set the parameter
TRAV_T of the VALVE block.
● Interlock
Faults
Channel faults are detected by the input and output drivers.
See also
BLK_VLV_2OUT_BLK (Page 36)
1.3.4 CASCADE_AT
This template can be used as a self-contained cascade PID controller with tracking
setpoints. The output from the primary control loop is the setpoint to a secondary control
loop. High and low alarms are provided for the process variables of both loops. Additional
alarms are provided to detect a deviation between the process variable and setpoint of both
loops. The block has inputs P_PV and S_PV for the primary and secondary process
variables, and outputs P_SP_OUT, S_SP_OUT, OUT, and ALARM for the primary setpoint,
secondary setpoint, output, and alarm status of the loops, respectively. The control loop
contains, apart from the controller, two input drivers (PRIMARY_PV_IN,
SECONDARY_PV_IN), an output driver (SECONDARY_VL_OUT), and delay elements for
simulation.
Interconnections
The signal for the primary value must be connected to the VALUE input of block
PRIMARY_PV_IN via symbolic addressing. The signal for the secondary actual value must
be connected to the VALUE input of block SECONDARY_PV_IN via symbolic addressing.
The VALUE output of the SECONDARY_VL_OUT block must be connected via symbolic
addressing to the signal for the actuator to be controlled.
Simulation
During the configuring phase, the controller can be tested with the delay element. This
merely requires that input SIM_ON of block PRIMARY_PV_IN and the input SIM_ON of block
SECONDARY_PV_IN be switched on. The Simulate Secondary CFC implements simple
simulation by feeding back a scaled lagged copy of the CONTROLLER OUT signal.
Normally, only the TM_LAG value needs to be adjusted for the application. The Simulate
Primary CFC implements simple simulation by feeding back a scaled lagged copy of the
Simulate Secondary's PV. Normally, only the TM_LAG value needs to be adjusted for the
application.
Parameter Assignment
To scale the primary input signal, set the primary's engineering high via PRIMARY_PV_IN's
VHRANGE input and the Process Value engineering low via PRIMARY_PV_IN's VLRANGE
input.
To scale the secondary input signal, set the secondary's engineering high via
SECONDARY_PV_IN's VHRANGE input and the Process Value engineering low via
SECONDARY_PV_IN's VLRANGE input.
This chart presumes that the CONTROLLER P_VL_EUMIN should equal the CONTROLLER
S_PV_EUMIN and that the CONTROLLER P_VL_EUMAX should equal the CONTROLLER
S_PV_EUMAX.
To scale the output signal, set the Control OUT value engineering high via CONTROLLER's
S_VL_EUMAX input and the Control OUT Engineering Low via S_VL_EUMIN input. These
engineering limits will be conveyed to the S_VL_EUMAX_OUT output and
S_VL_EUMIN_OUT outputs, respectively. As configured, SECONDARY_VL_OUT's upper
limit (UHRANGE) and the SECONDARY_VL_OUT's lower limit (ULRANGE) match the
CONTROLLER's S_VL_EUMAX and S_VL_EUMIN, respectively.
Configure the following parameters (which are marked for IEA) in the CONTROLLER (both
primary and secondary) for your application:
● All tuning parameters (PG, TI, TD and DG)
● All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
● Valve scaling units (VL_EUMIN, VL_EUMAX)
● Valve "clamping" limits (VLH, VLL). Note that VLH cannot exceed 3% of span above
VL_EUMAX and VLL cannot exceed 3% of span below VL_EUMIN.
● Setpoint limits (SPH, SPL)
Faults
Channel faults are detected by the PRIMARY_PV_IN input and are assigned to input
P_QBAD of the CONTROLLER block. An alarm message will then be posted if P_QUAL_EN
is enabled. Channel faults are detected by the SECONDARY_PV_IN input and the
SECONDARY_VL_OUT and are assigned to input S_QBAD of the CONTROLLER block. An
alarm message will then be posted if S_QUAL_EN is enabled.
See also
CASCADE_BLK (Page 41)
1.3.5 DISCRETE_ALM_AT
This template can be used to implement a discrete indicator with alarm. The template
includes a digital input driver. A discrete alarm is provided for the discrete input (DN). The
ALARM output provides the alarm status of the block. The block provides an alarm when the
discrete input is in an undesired state.
Interconnections
The signal to be monitored must be connected to the VALUE input of the SIGNAL block via
symbolic addressing.
Simulation
Discrete value monitoring can be tested during the configuring phase. This merely requires
that input SIM_ON of the SIGNAL block be switched on, and that the value 1 or 0 be preset
at input SIM_I.
Parameter Assignment
Configure the LIMIT parameter (which is marked for IEA) in the ALARM for your application.
Faults
Channel faults are detected by the input driver block.
See also
DISCRETE_ALM_BLK (Page 64)
1.3.6 EXT_SET_AT
This template can be used as an external-set PID controller with tracking setpoint. High and
low alarms are provided for the process variable. Another alarm is provided to detect
deviation between the process variable and setpoint. The CONTROLLER block has PV and
ESP inputs for the process variable and external setpoint. It also has SP_OUT, OUT, and
ALARM outputs for the setpoint, output, and alarm status of the loop, respectively. The
control loop contains, apart from the controller, an input driver, an output driver, and a delay
element for simulation.
Interconnections
The signal for the process value must be connected to the VALUE input of block PV_IN via
symbolic addressing. The VALUE output of the OUTPUT block must be connected via
symbolic addressing to the signal for the actuator to be controlled.
Simulation
During the configuring phase, the controller can be tested with the delay element. This
merely requires that input SIM_ON of block PV_IN be switched on. The Simulation CFC
implements simple simulation by feeding back a scaled lagged copy of the CONTROLLER's
OUT signal. Normally, only the TM_LAG value needs to be adjusted for the application.
Parameter Assignment
To scale the input signal, set the Process Value engineering high via the input driver PV_IN's
VHRANGE input and the Process Value engineering low via PV_IN's VLRANGE input.
These engineering limits will be conveyed to the CONTROLLER's PV_EUMAX and
PV_EUMIN, respectively.
To scale the output signal, set the Control OUT value engineering high via CONTROLLER's
VL_EUMAX input and the Control OUT Engineering Low via CONTROLLER's VL_EUMIN
input. These engineering limits will be conveyed to the CONTROLLER's VL_EUMAX_OUT
and VL_EUMIN_OUT outputs, respectively. As configured, OUTPUT's upper limit
(UHRANGE) and the OUTPUT's lower limit (ULRANGE) match the CONTROLLER's
VL_EUMAX and VL_EUMIN, respectively.
Configure the following parameters (which are marked for IEA) for your application:
● All tuning parameters (PG, TI, TD and DG)
● All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
● Valve scaling units (VL_EUMIN, VL_EUMAX)
● Valve "clamping" limits (VLH, VLL). Note that VLH cannot exceed 3% of span above
VL_EUMAX and VLL cannot exceed 3% of span below VL_EUMIN.
● Setpoint limits (SPH, SPL)
Faults
Channel faults are detected by the input and output drivers and are assigned to input QBAD
of the CONTROLLER block. An alarm message will then be posted if QUAL_EN is enabled.
See also
EXT_SET_BLK (Page 66)
1.3.7 MOTOR_A_ALM_AT
This template can be used to implement standard motor start/stop functions. Device
alarming functions are provided. This MOTOR block is an encapsulation of the MOTOR_A
block with a 4-element discrete alarm block. The MOTOR block has inputs PROOF,
A_STRT, A_STOP, and INT01-INT11 for the proof, auto start command, auto stop
command, and eleven interlocks, and parameters OUT, and FAIL for the output, and failure
status of the motor, respectively. Alarms are reported for the following conditions:
● Failure to start (or loss of proof)
● Failure to stop (or unexpected proof)
● Uncommanded stop or rejected start command (due to interlock)
The latched fail state is unlatched automatically when the alarm is acknowledged.
The motor circuit contains, apart from the motor block, a digital input driver and digital output
driver.
Interconnections
The signal for the feedback run must be connected to the VALUE input of block FB_RUN via
symbolic addressing. The VALUE output of the OUTPUT block must be connected via
symbolic addressing to the signal for the motor to be controlled.
Simulation
If there is no run feedback, the simulation can be switched on at driver block FB_RUN
(SIM_ON = 1). Simulation of motor proof is accomplished by delaying the MOTOR block's
OUT signal via a TIMER_P block (SIMULATION). Note that the TIME0 parameter should be
less than MOTOR block's STRT_T and STOP_T parameters.
Parameter Assignment
Configure the following parameters for your application:
● To set the MOTOR block's maximum allowed time to start and stop, set the parameter
STRT_T and STOP_T of the MOTOR block (which are marked for IEA) individually.
● Interlocks and Interlock descriptions.
● Permit and Permit description.
Faults
Channel faults are detected by the input and output drivers.
Note
Compiling Source Charts "as Program"
In the unlikely scenario that MOTOR_A_ALM or VALVE_A_ALM source charts are copied
into a user project as chart or used as chart-in-chart , and then all charts are compiled "as
Program", errors will be flagged by the CFC compiler for the BA_NA chart input connections.
This is not a normal or recommended scenario, since these charts and modifications of them
are designed to be compiled as "Block Type". The errors occur because the current CFC
version does not allow chart input connections of data type STRING to more than one
internal parameter. The workaround would be to add a second chart input parameter, for
example BA_NA_1 and connect these two chart inputs each to its own single destination
parameter inside the chart.
See also
MOTOR_A_ALM_BLK (Page 86)
1.3.8 MOTOR_1OUT_AT
This template can be used to implement a motor start/stop with one output. The block is
designed for a motor with auto/manual operation, pulse commands, and interlocking. An
alarm is provided for failure to reach the desired state. The block has inputs PROOF,
A_STRT, A_STOP, and INTRLK for the proof, auto start command, auto stop command, and
interlock; and outputs OUT, and FAIL for the output, and failure status of the motor,
respectively. The motor circuit contains, apart from the motor block, a digital input driver and
digital output driver.
Interconnections
The signal for the feedback run must be connected to the VALUE input of block FB_RUN via
symbolic addressing. The VALUE output of the OUTPUT block must be connected via
symbolic addressing to the signal for the motor to be controlled.
Simulation
If there is no feedback run, the simulation can be switched on at driver block FB_RUN
(SIM_ON = 1). Simulation of motor proof is accomplished by delaying the MOTOR block's
OUT signal via a TIMER_P block (SIMULATION). Note that the TIME0 parameter should be
less than MOTOR block's STRT_T and STOP_T parameters.
Parameter Assignment
Configure the following parameters for your application:
● To set the MOTOR block's maximum allowed time to start and stop, set the parameters
STRT_T and STOP_T of the MOTOR block (which are marked for IEA) individually.
● Interlock
Faults
Channel faults are detected by the input and output drivers.
See also
MOTOR_1OUT_BLK (Page 92)
1.3.9 MOTOR_2OUT_AT
This template can be used to implement a motor start/stop with a start output and a stop
output. The block is designed for a motor with auto/manual operation, pulse commands, and
interlocking. An alarm is provided for failure to reach the desired state. The MOTOR block
has inputs PROOF, A_STRT, A_STOP, and INTRLK for the proof, auto start command, auto
stop command, and interlock; and outputs STRT_O, STOP_O, and FAIL for the start output,
stop output, and failure status of the motor, respectively. The motor circuit contains, apart
from the motor block, a digital input driver and two digital output drivers.
Interconnections
The signal for the feedback run must be connected to the VALUE input of block FB_RUN via
symbolic addressing. The VALUE output of the STRT_OUTPUT block must be connected
via symbolic addressing to the signal for the motor to be controlled. The VALUE output of the
STOP_OUTPUT block must be connected via symbolic addressing to the signal for the
motor to be controlled.
Simulation
If there is no feedback run, the simulation can be switched on at driver block FB_RUN
(SIM_ON = 1). An SR_FF block (Simulate State) and a TIMER_P block (Simulate Delay) is
used to implement the simulation of the feedback. Note that the TIMEO parameter should be
less than MOTOR's STRT_T and STOP_T parameters.
Parameter Assignment
Configure the following parameters for your application:
● To set the MOTOR block's maximum allowed time to start and stop, set the parameter
STRT_T and STOP_T of the MOTOR block (which are marked for IEA) individually.
● Interlock
Faults
Channel faults are detected by the input and output drivers.
See also
MOTOR_2OUT_BLK (Page 97)
1.3.10 PRIMARY_SECONDARY_AT
This template can be used as a cascade circuit. The output from the primary loop is the
setpoint to the secondary loop, and the cascade status of the secondary loop is fed to the
primary loop. High and low alarms are provided for each process variable, and an alarm is
provided for deviation between process variable and setpoint. The PRIMARY block has
inputs PV, FDBK, and CASC_S for the process variable, feedback, and cascade status, and
outputs SP_OUT, OUT, and ALARM for the setpoint, output, and alarm status of the loop,
respectively. The SECONDARY block has inputs PV and ESP for the process variable and
external setpoint, and outputs SP_OUT, OUT, ALARM, and CASC_S for the setpoint, output,
alarm status, and cascade status of the loop, respectively. The control loop contains, apart
from the controller, two input drivers (PRIMARY_PV_IN, SECONDARY_PV_IN), an output
driver (SECONDARY_VL_OUT) and delay elements for simulation.
Interconnections
The signal for the primary value must be connected to the VALUE input of block
PRIMARY_PV_IN via symbolic addressing. The signal for the secondary value must be
connected to the VALUE input of block SECONDARY_PV_IN via symbolic addressing. The
VALUE output of the SECONDARY_VL_OUT block must be connected via symbolic
addressing to the signal for the actuator to be controlled.
Simulation
During the configuring phase, the controller can be tested with the delay element. This
merely requires that input SIM_ON of block PRIMARY_PV_IN and the input SIM_ON of block
SECONDARY_PV_IN be switched on. The Simulate Secondary CFC implements simple
simulation by feeding back a scaled lagged copy of the SECONDARY's OUT signal.
Normally, only the TM_LAG value needs to be adjusted for the application. The Simulate
Primary CFC implements simple simulation by feeding back a scaled lagged copy of
Simulate Secondary's PV. Normally, only the TM_LAG value needs to be adjusted for the
application.
Parameter Assignment
To scale the primary input signal, set the primary's engineering high via PRIMARY_PV_IN's
VHRANGE input and the Process Value engineering low via PRIMARY_PV_IN's VLRANGE
input.
To scale the secondary input signal, set the secondary's engineering high via
SECONDARY_PV_IN's VHRANGE input and the Process Value engineering low via
SECONDARY_PV_IN's VLRANGE input.
This chart presumes that the PRIMARY VL_EUMIN should equal the SECONDARY
PV_EUMIN and that the PRIMARY VL_EUMAX should equal the SECONDARY
PV_EUMAX.
To scale the output signal, set the Control OUT value engineering high via SECONDARY's
VL_EUMAX input and the Control OUT Engineering Low via SECONDARY 's VL_EUMIN
input. These engineering limits will be conveyed to the SECONDARY's VL_EUMAX_OUT
and VL_EUMIN_OUT outputs, respectively. As configured, SECONDARY_VL_OUT's upper
limit (UHRANGE) and the SECONDARY_VL_OUT's lower limit (ULRANGE) match the
SECONDARY's VL_EUMAX and VL_EUMIN, respectively.
Configure the following parameters (which are marked for IEA) in the PRIMARY and
SECONDARY for your application:
● All tuning parameters (PG, TI, TD and DG)
● All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
● Valve scaling units (VL_EUMIN, VL_EUMAX)
● Valve "clamping" limits (VLH, VLL). Note that VLH cannot exceed 3% of span above
VL_EUMAX and VLL cannot exceed 3% of span below VL_EUMIN.
● Setpoint limits (SPH, SPL)
Faults
Channel faults are detected by the PRIMARY_PV_IN input and are assigned to input QBAD
of the PRIMARY block. An alarm message will then be posted if QUAL_EN is enabled.
Channel faults are detected by the SECONDARY_PV_IN input and the
SECONDARY_VL_OUT and are assigned to input QBAD of the SECONDARY block. An
alarm message will then be posted if QUAL_EN is enabled.
See also
PRIMARY_BLK (Page 104)
SECONDARY_BLK (Page 124)
1.3.11 RATIO_SET_AT
This template can be used use as a ratio-set PID controller with tracking setpoint. An
external ratio input is multiplied by a desired ratio value (i.e. a controlled variable divided by
wild variable) to calculate the external setpoint. The process variable is divided by the
external input for display of the actual ratio. Both high and low alarms are provided for the
process variable, and an additional alarm is provided to detect a deviation between the
process variable and setpoint. The CONTROLLER block has PV and RAT_INP inputs for the
process variable and external input. It also has SP_OUT, OUT, RAT_ACT, DESRAT, and
ALARM outputs for the setpoint, output, actual ratio, desired ratio, and alarm status of the
loop, respectively. The control loop contains, apart from the controller, two input drivers
(PV_IN and RATIO_IN), an output driver (OUTPUT) and a delay element for simulation.
Interconnections
The signal for the process value must be connected to the VALUE input of block PV_IN via
symbolic addressing. The signal for the external ratio actual value must be connected to the
VALUE input of the block RATIO_IN via symbolic addressing. The VALUE output of the
OUTPUT block must be connected via symbolic addressing to the signal for the actuator to
be controlled.
Simulation
During the configuring phase, the controller can be tested with the delay element. This
merely requires that input SIM_ON of block PV_IN be switched on. The Simulation CFC
implements simple simulation by feeding back a scaled lagged copy of the CONTROLLER's
OUT signal. Normally, only the TM_LAG value needs to be adjusted for the application.
Parameter Assignment
To scale the input signal, set the Process Value engineering high via the input driver PV_IN's
VHRANGE input and the Process Value engineering low via PV_IN's VLRANGE input.
These engineering limits will be conveyed to the CONTROLLER's PV_EUMAX and
PV_EUMIN, respectively.
To scale the output signal, set the Control OUT value engineering high via CONTROLLER's
VL_EUMAX input and the Control OUT Engineering Low via CONTROLLER's VL_EUMIN
input. These engineering limits will be conveyed to the CONTROLLER's VL_EUMAX_OUT
and VL_EUMIN_OUT outputs, respectively. As configured, the OUTPUT's upper limit
(UHRANGE) and the OUTPUT's lower limit (ULRANGE) match the CONTROLLER's
VL_EUMAX and VL_EUMIN, respectively
Configure the following parameters (which are marked for IEA) for your application:
● All tuning parameters (PG, TI, TD and DG)
● All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
● Valve scaling units (VL_EUMIN, VL_EUMAX)
● Valve "clamping" limits (VLH, VLL). Note that VLH cannot exceed 3% of span above
VL_EUMAX and VLL cannot exceed 3% of span below VL_EUMIN.
● Setpoint limits (SPH, SPL)
Faults
Channel faults are detected by the input and output drivers and are assigned to input QBAD
of the CONTROLLER block. An alarm message will then be posted if QUAL_EN is enabled.
See also
RATIO_SET_BLK (Page 113)
1.3.12 SINGLE_LOOP_AT
This template can be used to implement a single-loop PID controller with a tracking setpoint.
Both high and low alarms are provided for the process variable. Another alarm is provided to
detect a deviation between the process variable and setpoint. The controller block has a PV
input for the process variable. It also has SP_OUT, OUT, and ALARM outputs for the
setpoint, output, and alarm status of the loop, respectively. The control loop contains, apart
from the controller, an input driver (PV_IN), an output driver (OUTPUT) and a delay element
for simulation.
Interconnections
The signal for the actual value must be connected to the VALUE input of block PV_IN via
symbolic addressing. The VALUE output of the OUTPUT block must be connected via
symbolic addressing to the signal for the actuator to be controlled.
Simulation
During the configuring phase, the controller can be tested with the delay element. This
merely requires that input SIM_ON of block PV_IN be switched on. The Simulation CFC
implements simple simulation by feeding back a scaled lagged copy of the CONTROLLER's
OUT signal. Normally, only the TM_LAG value needs to be adjusted for the application.
Parameter Assignment
To scale the input signal, set the Process Value engineering high via the input driver PV_IN's
VHRANGE input and the Process Value engineering low via PV_IN's VLRANGE input.
These engineering limits will be conveyed to the CONTROLLER's PV_EUMAX and
PV_EUMIN, respectively.
To scale the output signal, set the Control OUT value engineering high via CONTROLLER's
VL_EUMAX input and the Control OUT Engineering Low via CONTROLLER's VL_EUMIN
input. These engineering limits will be conveyed to the CONTROLLER's VL_EUMAX_OUT
and VL_EUMIN_OUT outputs, respectively. As configured, OUTPUT's upper limit
(UHRANGE) and the OUTPUT's lower limit (ULRANGE) match the CONTROLLER's
VL_EUMAX and VL_EUMIN, respectively.
Configure the following parameters (which are marked for IEA) for your application:
● All tuning parameters (PG, TI, TD and DG)
● All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
● Valve scaling units (VL_EUMIN, VL_EUMAX)
● Valve "clamping" limits (VLH, VLL). Note that VLH cannot exceed 3% of span above
VL_EUMAX and VLL cannot exceed 3% of span below VL_EUMIN.
● Setpoint limits (SPH, SPL)
Faults
Channel faults are detected by the input and output drivers and are assigned to input QBAD
of the CONTROLLER block. An alarm message will then be posted if QUAL_EN is enabled.
See also
SINGLE_LOOP_BLK (Page 138)
1.3.13 SINGLE_LP_EM_AT
This template can be used to implement a single-loop PID controller with tracking setpoint
and Emergency Manual functionality. The External Value and Emergency Manual command
inputs allow the controller output to be immediately forced to any desired value. High and low
alarms are provided for the process variable, and an additional alarm is provided to detect a
deviation between the process variable and setpoint. The CONTROLLER block has PV,
EXTV, and EM inputs for process variable, external value, and Emergency Manual
command. It also has SP_OUT, OUT, and ALARM outputs for the setpoint, output, and
alarm status of the loop, respectively. The control loop contains, apart from the controller, an
input driver (PV_IN), an output driver (OUTPUT) and a delay element for simulation.
Interconnections
The signal for the process value must be connected to the VALUE input of block PV_IN via
symbolic addressing. The VALUE output of the OUTPUT block must be connected via
symbolic addressing to the signal for the actuator to be controlled.
Simulation
During the configuring phase, the controller can be tested with the delay element. This
merely requires that input SIM_ON of block PV_IN be switched on. The Simulation CFC
implements simple simulation by feeding back a scaled lagged copy of the CONTROLLER's
OUT signal. Normally, only the TM_LAG value needs to be adjusted for the application.
Parameter Assignment
To scale the input signal, set the Process Value engineering high via the input driver PV_IN's
VHRANGE input and the Process Value engineering low via PV_IN's VLRANGE input.
These engineering limits will be conveyed to the CONTROLLER's PV_EUMAX and
PV_EUMIN, respectively.
To scale the output signal, set the Control OUT value engineering high via CONTROLLER's
VL_EUMAX input and the Control OUT Engineering Low via CONTROLLER's VL_EUMIN
input. These engineering limits will be conveyed to the CONTROLLER's VL_EUMAX_OUT
and VL_EUMIN_OUT outputs, respectively. As configured, OUTPUT's upper limit
(UHRANGE) and the OUTPUT's lower limit (ULRANGE) match the CONTROLLER's
VL_EUMAX and VL_EUMIN, respectively
Configure the following parameters (which are marked for IEA) for your application:
● All tuning parameters (PG, TI, TD and DG)
● All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
● Valve scaling units (VL_EUMIN, VL_EUMAX)
● Valve "clamping" limits (VLH, VLL). Note that VLH cannot exceed 3% of span above
VL_EUMAX and VLL cannot exceed 3% of span below VL_EUMIN.
● Setpoint limits (SPH, SPL)
Faults
Channel faults are detected by the input and output drivers and are assigned to input QBAD
of the CONTROLLER block. An alarm message will then be posted if QUAL_EN is enabled.
1.3.14 SINGLE_LP_SS_AT
This template can be used to implement a single-loop PID controller with tracking setpoint
and standby sync functionality. The External Value and Standby Sync command inputs allow
the controller output to be immediately forced to any desired value. High and low alarms are
provided for the process variable, and an additional alarm is provided to detect a deviation
between the process variable and setpoint. The CONTROLLER block has PV, EXTV, and
SS inputs for process variable, external value, and standby sync command. It also has
SP_OUT, OUT, and ALARM outputs for the setpoint, output, and alarm status of the loop,
respectively. The control loop contains, apart from the controller, an input driver (PV_IN), an
output driver (OUTPUT) and a delay element for simulation.
Interconnections
The signal for the process value must be connected to the VALUE input of block PV_IN via
symbolic addressing. The VALUE output of the OUTPUT block must be connected via
symbolic addressing to the signal for the actuator to be controlled.
Simulation
During the configuring phase, the controller can be tested with the delay element. This
merely requires that input SIM_ON of block PV_IN be switched on. The Simulation CFC
implements simple simulation by feeding back a scaled lagged copy of the CONTROLLER's
OUT signal. Normally, only the TM_LAG value needs to be adjusted for the application.
Parameter Assignment
To scale the input signal, set the Process Value engineering high via the input driver PV_IN's
VHRANGE input and the Process Value engineering low via PV_IN's VLRANGE input.
These engineering limits will be conveyed to the CONTROLLER's PV_EUMAX and
PV_EUMIN, respectively.
To scale the output signal, set the Control OUT value engineering high via CONTROLLER's
VL_EUMAX input and the Control OUT Engineering Low via CONTROLLER's VL_EUMIN
input. These engineering limits will be conveyed to the CONTROLLER's VL_EUMAX_OUT
and VL_EUMIN_OUT outputs, respectively. As configured, OUTPUT's upper limit
(UHRANGE) and the OUTPUT's lower limit (ULRANGE) match the CONTROLLER's
VL_EUMAX and VL_EUMIN, respectively
Configure the following parameters (which are marked for IEA) for your application:
● All tuning parameters (PG, TI, TD and DG)
● All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
● Valve scaling units (VL_EUMIN, VL_EUMAX)
● Valve "clamping" limits (VLH, VLL). Note that VLH cannot exceed 3% of span above
VL_EUMAX and VLL cannot exceed 3% of span below VL_EUMIN.
● Setpoint limits (SPH, SPL)
Faults
Channel faults are detected by the input and output drivers and are assigned to input QBAD
of the CONTROLLER block. An alarm message will then be posted if QUAL_EN is enabled.
See also
SINGLE_LP_SS_BLK (Page 156)
1.3.15 VALVE_A_ALM_AT
This template can be used to implement standard valve open/close and device alarming
functions. The VALVE block is an encapsulation of the VALVE_A block with a 4-element
discrete alarm block. The VALVE block has inputs OP_VER, CL_VER, A_OPEN, A_CLSE,
and INT0-INT10 for the open verify, close verify, auto open command, auto close command,
and ten separate interlocks, and parameters OUT and FAIL for the output, and failure status
of the valve, respectively. Alarms are provided for the following conditions:
● Failure to open (or loss of open verify)
● Failure to close (or loss of close verify)
● Uncommanded close/open or rejected command (due to interlock)
● Failed limit switch (Open and close verify inputs are set.)
The latched fail state of the VALVE_A block is unlatched automatically when the alarm is
acknowledged. The valve circuit contains, apart from the valve block, two digital input drivers
and one digital output driver.
Interconnections
The signal for the feedback (open/closed) must be connected to the VALUE inputs of blocks
FB_OPEN and FB_CLOSED via symbolic addressing. The VALUE output of the OUTPUT
block must be connected via symbolic addressing to the signal for the valve to be controlled.
Simulation
If there is no feedback, the simulation can be switched on at driver blocks FB_OPEN and
FB_CLOSED (SIM_ON = 1). A connection is provided from the VALVE output OUT to a
TIMER_P delay block (SIMULATION) IO input. The SIMULATION QO output is connected to
the input SIM_I of block FB_OPEN. It is also connected to input SIM_I of block FB_CLOSED
after being inverted. Simulation of valve limit switches is accomplished by delaying VALVE
block's OUT signal. Note than the TIME0 parameter should be less than VALVE's OPEN_T
and CLOS_T parameters.
Parameter Assignment
Configure the following parameters for your application:
● To set the VALVE block's maximum allowed time to open and close, set the parameters
OPEN_T and CLOS_T of the VALVE block (which are marked for IEA) individually.
● Interlocks and Interlock descriptions
● Permit and Permit description
● Fail-safe state of the valve (FAIL_OPEN)
Faults
Channel faults are detected by the input and output drivers.
Note
Compiling Source Charts "as Program"
In the unlikely scenario that MOTOR_A_ALM or VALVE_A_ALM source charts are copied
into a user project as chart or used as chart-in-chart , and then all charts are compiled "as
Program", errors will be flagged by the CFC compiler for the BA_NA chart input connections.
This is not a normal or recommended scenario, since these charts and modifications of them
are designed to be compiled as "Block Type". The errors occur because the current CFC
version does not allow chart input connections of data type STRING to more than one
internal parameter. The workaround would be to add a second chart input parameter, for
example BA_NA_1 and connect these two chart inputs each to its own single destination
parameter inside the chart.
See also
VALVE_A_ALM_BLK (Page 166)
Classification of messages in accordance with their cause. The following message classes
are used in the SIMATIC process control system:
● Process signals which are triggered when process-specific monitoring values (for
example: alarms, interrupts, upper/lower tolerance, general process signals) are reached
or exceeded.
● Control system messages which are output by the control system (system messages),
the I/O units (errors in the field) or for preventive maintenance.
● Requests for operator input which, in the case of certain operation sequences, draw the
operator's attention to the necessity of an operator intervention (for example, request to
acknowledge a stepping operation manually in order to enable transition) or operator
input lists.
Softlist Parameters
There are no softlist parameters in function blocks created in PCS 7. In general, these
values have become In/Out parameters. In some specific cases, they are inputs.
Time Parameters
Time parameters have a different range of values. The maximum values are as follows:
look very similar to DFBs opened in 4-mation. However, the source charts are not open
blocks; they are compiled to create function blocks. Both charts and the FBs created from
them can be placed in CFCs, but only charts can be opened. On the other hand, faceplates
can only be associated with function blocks, not charts.
In either case, the dialog lets you choose to read back all parameters of the block inputs or
only the parameters assigned the operator control and monitoring (S7_m_c:='true') system
attribute.
In a PCS 7 project, only the "Parameters controllable in WinCC" option is useful and thus set
for read back actions by default.
The following rules apply, irrespective of the scope set for the read back function:
● Only in_out and input parameters can be read back (not output parameters).
● The following data types are ignored when reading back data:
ANY, ARRAY, POINTER, UDT.
● Inputs with write access by SFC chart are not read back.
● Certain blocks can be excluded from the read back operation (e.g. BATCH blocks). In this
case, the block type is assigned the S7_read_back := 'false' attribute. This attribute
cannot be modified in block instances.
● Note on H CPUs:
If the H CPU is operated in stand-alone mode (e.g. due to CPU failure) and a CPU fail-
over has taken place, the user is prompted to select the required CPU after an online
access request. This dialog does not appear if the CPU is operated in redundant mode.
● Note on the download of HW Config data:
Please note that the CPU will write data from load memory to work memory after you
have downloaded HW Config data. Changes effected in debug mode or via operator
control and monitoring only exist in work memory. Due to the transfer of data from load
memory, all data in work memory will be lost, since its initial values will be overwritten by
data from load memory. In this case you can create a backup of operator control data by
means of read back, before you perform a download of HW Config data. You can then
include these backup data in a program download to the CPU (in STOP mode).
The following applies for setting the scope of the "Parameters controllable in WinCC"
function:
● Values of FC inputs will be ignored.
The following applies for setting the scope of "All parameters" function:
● FC inputs interconnected to chart I/Os will be read back. This also applies to chart I/Os
with multiple interconnections to block inputs (FB and FC).
After read back:
● The full program is compiled automatically in order to ensure consistency. This does not,
however require a download of the full program, i.e. you can also perform a delta
download when the CPU is in RUN mode.
● A log file will be generated during read back and displayed after completion. You can
always view this log via the Options > Logs > Tab: Read Back menu command. The log
entries indicate
● I/Os read back and modified
● Where problems occurred
Batch Parameters
The SIMATIC Batch parameters are:
DecimalPlaces
Input parameters DecimalPlacesPV, DecimalPlacesOUT, etc have been added to loop
control blocks to allow specifying the number of decimal places to display on the block's
faceplate in the HMI. The range is 0 to 6, with a default value of 2.
ConfirmChange
The ConfirmChange input flag is added to most of the library blocks, to control operator
changes in the HMI. The default value is FALSE, but this may be re-configured for any
desired block instance.
If ConfirmChange is FALSE (default):
● Operator changes are "one-step", no further confirmation is required.
● all choices that are two-state, such as Auto/Manual, will immediately toggle to the other
state.
● Increase/Decrease buttons will be visible and may be used by operator for quick changes
of analog values, when appropriate (e.g. changing SP when in Auto mode).
If ConfirmChange is TRUE:
● Operator changes are "two-step", further confirmation is required. Usually an "input
panel" will pop up, where operator may select a value and click OK.
● all choices including two-state choices require confirmation.
● Increase/Decrease buttons will be invisible.
Note that in both cases all operator changes are sent to the Operation List log.
In APACS programs, the SET_VAL block could be used by a program to write to a variable
and then return control of the same variable to the operator.
Instead, the New ES Library uses the PCS 7 technique of selecting between "Link" (i.e. a
linked connection to a block in the program) and "Operator", the operator in the HMI. New
parameters beginning with "LIOP_..." can be seen for this purpose. For example, the switch
between Auto and Manual modes of operation can be made either by the Program or by the
Operator, as follows:
● LIOP_MAN_SEL = TRUE: The connected value at the AUT_L ("link ") block input will
determine the Auto/Manual mode. Operator input is ignored.
● LIOP_MAN_SEL = FALSE: The operator input from the HMI will determine the
Auto/Manual mode. The value configured at the AUT_L block input is ignored.
In all cases the correct current value of the variable is shown to the operator in the faceplate.
● Derivative filtering in the APACS+ controller will always vary in direct proportion to the
derivative time whereas the PCS 7 controller contains a separate derivative filter
parameter that must be independently adjusted in relation to the derivative time.
● The time units of the integral and derivative components are in minutes for the APACS+
controller while they are in seconds for the PCS 7 controller.
APACS+ Algorithm
The transfer function used in the APACS+ controller (plus the Model 352 et. al.) is shown
below:
PCS 7 Algorithm
The default transfer function used in the PCS 7 controller is shown below:
where: LMN is the controller output, TN is integral time, TV is derivative time, and TM_LAG
is derivative filter time.
In the PCS 7 controller, the sign of the GAIN parameter determines the controller action.
With a positive GAIN, the controller acts as a reverse action controller. Proportional action
FB No.
Block number
Block length
Memory requirements of the program code, once for every block type.
Temporary memory
The local-data memory required in a priority class when the block is called. This is limited to
the CPU specifically. When it is exceeded, a CPU STOP is caused. You have to check it in
the CPU configuration and, if necessary, distribute it amongst the priority classes (Obs) to
meet the real requirements.
Block (Type Name) FB No. Typical run Block Instance data Temporary Multiple Instance block
time (ms)* length length memory
CPU 416-3 (bytes) (bytes) (bytes)
Block (Type Name) FB No. Typical run Block Instance data Temporary Multiple Instance block
time (ms)* length length memory
CPU 416-3 (bytes) (bytes) (bytes)
1.8.1 DINTToInt64
Function
Routine to convert DINT to Int64 data type.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.2 AddInt64
Function
Routine to add two Int64s and return an Int64 result.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.3 NegateInt64
Function
Routine to negate an Int64.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.4 SHLInt64
Function
This is a Routine to shift an Int64 value to the left
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.5 SHRInt64
Function
This is a Routine to shift an Int64 value to the right
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.6 REALToDPReal
Function
Routine to convert a REAL to a double precision Real
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.7 AddDPReal
Function
Routine to add two double precision REAL values.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.8 NegateDPReal
Function
Routine to negate a Double Precision Real.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.9 DPRealToReal
Function
Routine to convert a Double Precision Real to a REAL.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.10 Int64ToDINT
Function
Routine to convert Int64 data type to DINT.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.11 TIME_DIFF
Function
Routine to calculate elapsed time, handling possible internal clock overflow.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.12 ALM_PROC
Function
Routine to perform generic APACS+ alarm processing functions.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.13 PID_AFB_Calc_Coeff
Function
Routine to calculate difference equation coefficients for APACS+ PID.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.14 DALM_Test_Alarm
DALM_Test_Alarm
Function
Function to support DALM_AFB alarm processing.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.15 MOVE_BOOL
Function
Move boolean function.
Note
This is a support function for the APACS+ library. It is not intended for general use.
1.8.16 NON_RETAIN_BOOL
Function
Emulate non-retentive Boolean.
Note
This is a support function for the APACS+ library. It is not intended for general use.
2.1.1 Symbols
Each tag structure and faceplate has an associated symbol. You can place these symbols
on your process graphics to represent a control object. At runtime, when you click on the
symbol, the associated faceplate is displayed and tied to the corresponding instance of the
APACS+ object.
The PCS 7/APACS+ Option symbols are shown in the picture below:
Most blocks have several symbols, each with differing sizes and amount of information. The
default symbol selected by the SIMATIC Manager compiler is the one named
@BlockName/1. Alternate symbols can be selected by the SIMATIC Manager compiler by
opening the "Object Properties" for the block in the CFC Editor, and entering a value (2, 3,
etc.) in the "Create block icon:" text box for the block. Example: Entering a "2" in the "Create
block icon:" text box will assign the @BlockName/2 symbol to the block during compile.
When a symbol is copied or cut and then pasted onto the same picture or another picture,
the Graphics Designer changes the name of the symbol. For example, @LOOP_A becomes
LOOP_A1; if another instance is pasted, the name becomes LOOP_A2. It is important that
the symbol names of symbol instances created during the compile not be changed. The
compiler manages the creation and deletion of the symbol instances that it creates. If you cut
and paste a symbol instance onto the same picture created by the compiler, the next time
the compiler runs it adds another instance of this symbol to the project. If you need to move
a symbol, drag and drop it to ensure that the name does not change.
Key Description
① Step controls
② Minimum permissible value
③ Maximum permissible value
④ Analog value
⑤ Slider control of analog value
⑥ Keypad for entering values
⑦ Confirmation button, logs change in operator's log
File: @Common_AnalogInput.PDL
File: @Common_DiscreteInput.PDL
File: @Common_TimeInput.PDL
File: @Common_ConfirmationBox.PDL
View File
Analog Input Dialog Box @Common_AnalogInput.PDL
Discrete Input Dialog Box @Common_DiscreteInput.PDL
Time Input Dialog Box @Common_TimeInput.PDL
Confirmation Dialog Box @Common_ConfirmationBox.PDL
The number of decimal points displayed on symbols and faceplates is configurable on a tag
by tag basis in DBA.
The following table shows which decimal point tags affect which HMI tags.
; This is a comment
: Tag , EXTRA, PERSIST, SYNC, EXTRA, EXTRA
Tag1_PS
Tag2_PS , , 1, 10
Tag3_PS , , yes, -1
Tag4_P , , True, 0
Tag5_P,,attr1=55:attr2=100,F
Tag6_P,,t,FALSE,,
Tag7_P , , , False
Tag8_S,,f,,,,
Tag9_S,,f,+
Tag10_S,,f,aaaaa=bbb,,,
Tag11_S , , f
; another comment
; Define columns in different order in same file
: Tag , SYNC, EXTRA, EXTRA
Tag20_S
Tag21_S,+,sss,wwww
Tag22_S , 1
In this example, all the tags with a suffix of _P will only be added to the PERSIST list, _S will
only be added to the SYNC list, and _PS will be added to both. This file shows the defaulted
TRUE for blank or missing option columns.
An option column can also contain a name/value series which will be further processed to
add additional attributes to the output XML Node. The format should be as follows:
attrname1=attrvalue1:attrname2=attrvalue2
Notice that an option column value can contain one or more name/value pairs separated by
a colon (:).
The previous example generates the following XML file, assuming the PERSIST and SYNC
configurations were empty to start with:
<AppHost>
<PlugIn Name="CustomSyncPersistInjector" ProgID="CustomSyncPersistPlugIn.PlugIn"
Enabled="-1" File="Test.csv" Status="LOADED"/>
<PlugIn Name="SyncAgent" ProgID="SyncAgent.EventSync" Enabled="0" Status="LOADED">
<Sync Na="DMAdapter.Tag1_PS" ASONa="??"/>
<Sync Na="DMAdapter.Tag2_PS" ASONa="??"/>
<Sync Na="DMAdapter.Tag3_PS" ASONa="??"/>
<Sync Na="DMAdapter.Tag8_S" ASONa="??"/>
<Sync Na="DMAdapter.Tag9_S" ASONa="??"/>
<Sync Na="DMAdapter.Tag10_S" ASONa="??" aaaaa="bbb"/>
<Sync Na="DMAdapter.Tag11_S" ASONa="??"/>
<Sync Na="DMAdapter.Tag20_S" ASONa="??"/>
<Sync Na="DMAdapter.Tag21_S" ASONa="??"/>
<Sync Na="DMAdapter.Tag22_S" ASONa="??"/>
</PlugIn>
<PlugIn Name="PersistAgent" ProgID="PersistAgent.EventPersist" Enabled="0"
Status="LOADED">
<Persist Na="DMAdapter.Tag1_PS" ASONa="??"/>
<Persist Na="DMAdapter.Tag2_PS" ASONa="??"/>
<Persist Na="DMAdapter.Tag3_PS" ASONa="??"/>
<Persist Na="DMAdapter.Tag4_P" ASONa="??"/>
<Persist Na="DMAdapter.Tag5_P" ASONa="??" attr1="55" attr2="100"/>
<Persist Na="DMAdapter.Tag6_P" ASONa="??"/>
<Persist Na="DMAdapter.Tag7_P" ASONa="??"/>
</PlugIn>
</AppHost>
The "ASONa" attribute is "??", which allows for later enhancements that may need to track
which object created the item. It is not currently used.
2.2 SINGLE_LOOP_BLK
The mode control Auto selects process automation, while Manual permits operator control of
the output. In Auto mode, clicking the SP (set point) box displays an analog input edit box.
Clicking is not allowed when the mode is set to Manual and PVTracking is enabled. Range
limits are enforced by the SPH and SPL tags.
Note
Added Icons
The Quality Icons shown in the graphic above, appear in a number of other displays
although not all of them were updated in this document.
File: @PG_SINGLE_LOOP_BLK_STANDARD.PDL
● Clicking the PVTrack check box produces a discrete input confirmation box.
● Clicking any of the eight edit boxes produces an analog input edit box. Range limits (if
configured) are enforced by the WinCC Data Manager.
● The controller action (Direct/Reverse) is a read-only field.
File: @PCS7_APACS_TUNING.PDL
File: @PCS7_ALARM.PDL
Key Description
① Alarm Type
② Alarm Enabled or Not
③ Alarm Limits Value
④ Alarm Deadband Value
⑤ Alarm Units
● Clicking any check box produces a discrete input confirmation box, if the ConfirmChange
attribute for this block is TRUE.
● Clicking any of the edit boxes produces an analog input edit box. Range limits (if
configured) are enforced by the WinCC Data Manager.
File: @PCS7_APACS_ALARM_CONFIG.PDL
Key Description
① Ruler (see key 12)
② Zoom
③ Original view (return from zoom)
④ Select time range
⑤ Previous trend
⑥ Next trend
⑦ Stop (freeze)/start (continue)
⑧ Moveable cursor, shown when ruler, key 1, is enabled
⑨ SP (blue)
⑩ PV (green)
⑪ VL (orange)
⑫ Detachable window displayed when ruler (see key 1) is enabled. Shows process
values at cursor position, which can be dragged. Color coded with trend curves.
File: @PCS7_APACS_TREND3.PDL
Key Description
① Alarm Group Display
② Lock/unlock messages button
③ Alarm ACK button
④ Go to primary graphic button (display function block's primary graphic)
File: @PG_SINGLE_LOOP_AFB_OVERVIEW.PDL
Key Description
① Current tagname
② Pulldown view-selector list
③ Go to loop display mode (all faceplate views, with the option of selecting a large trend
display)
File: @PG_SINGLE_LOOP_AFB.PDL
File: @PG_SINGLE_LOOP_AFB_VIEWLIST.PDL
From the loop display mode, you can expand the trend display to cover four views by clicking
Display Large Trend. With the loop display expanded, you can shrink it to cover a single view
by clicking Display Small Trend.
View File
Standard @PG_SINGLE_LOOP_BLK_STANDARD.PDL
Tuning @PCS7_APACS_TUNING.PDL
Alarm @PCS7_ALARM.PDL
Ramp @PCS7_APACS_RAMP.PDL
Limits @PCS7_APACS_ALARM_CONFIG.PDL
Trend @PCS7_APACS_TREND3.PDL
Faceplate Overview Window @PG_SINGLE_LOOP_BLK_OVERVIEW.PDL
Faceplace Frame @PG_SINGLE_LOOP_BLK.PDL
Faceplate View List @PG_SINGLE_LOOP_BLK_VIEWLIST.PDL
Faceplate Loop @PL_SINGLE_LOOP_BLK.PDL
2.3.1 ANALOG_ALM_BLK
Standard View
The Standard view is the default view when the faceplate is first displayed in Group Display
mode. It displays the function block description, process variable, and some alarm limits.
Clicking the Display Large Trend button increases the size of the trend view by four times
and places it on top of two of four smaller views. Clicking the Display Small Trend button
restores the trend view to the original size.
View File
Standard @PG_ANALOG_ALM_BLK_STANDARD.PDL
Alarm @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Limits @PCS7_APACS_ALARM_CONFIG.PDL (see the SINGLE_LOOP_BLK)
Trend View (one pen) @PCS7_APACS_TREND1.PDL (see the SINGLE_LOOP_BLK)
Faceplace Frame @PG_ANALOG_ALM_BLK.PDL (see the SINGLE_LOOP_BLK)
Faceplate Overview Window @PG_ANALOG_ALM_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
Faceplate View List @PG_ANALOG_ALM_BLK_VIEWLIST.PDL
Faceplate Loop @PL_ANALOG_ALM_BLK.PDL
2.3.2 DISCRETE_ALM_BLK
Standard View
The Standard view is the default view when the faceplate is first displayed in Group Display
mode. It displays the function block description, alarm status, and certain alarm configuration
values.
The following table lists all of the significant objects on the view:
View File
Standard @PG_DISCRETE_ALM_BLK_STANDARD.PDL
Alarm @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Faceplate Frame @PG_DISCRETE_ALM_BLK.PDL (see the SINGLE_LOOP_BLK)
Faceplate Overview Window @PG_DISCRETE_ALM_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
View File
Faceplate View List @PG_DISCRETE_ALM_BLK_VIEWLIST.PDL
Faceplate Loop @PL_DISCRETE_ALM_BLK.PDL
2.3.3 MOTOR_1OUT_BLK
Standard View
The Standard view is the default view when the faceplate is first displayed in Group Display
mode. It displays the function block description, alarm status, and various motor status
values and motor configuration values.
time to start MOTOR in excess of this value fires an alarm. Clicking the Start Time or
Stop Time I/O field brings up a time input edit box.
● The Stop Time indicator displays the maximum allowable time between the OUT signal
going FALSE and PROOF feedback going FALSE before the FAIL output goes TRUE. A
time to stop MOTOR in excess of this value fires an alarm. Clicking the Start Time or
Stop Time I/O field brings up a time input edit box.
● The Enabled check box controls the discrete alarm of the function block.
Objects
The following table lists all of the significant objects on the standard view:
Key Name Type Description Tag
① StaticTextOn Static Text Motor on Indicator PROOF
② StaticTextOff Static Text Motor off Indicator PROOF
StaticTextOff1 Static Text Motor off Indicator
③ StaticTextOutStart Static Text Output Start Indicator OUT
StaticTextOutStop Static Text Output Stop Indicator
④ StaticTextInterlockOK Static Text Intorlock OK Indicator INTRLK
StaticTextInterlocked Static Text Intorlocked Indicator
⑤ Description Static Text FB comment #comment
⑥ ButtonStart Customized object Start MOTOR Control START, AUTO
⑦ ButtonStop Customized object Stop MOTOR Control STOP, AUTO
⑧ ModeControl Customized object Mode AUTO
⑨ IOFieldStartTime Customized object Start time limit START_T
⑩ IOFieldStopTime Customized object Stop time limit STOP_T
⑪ CheckBoxEN Customized object Enabled A1EN
View File
Standard @PG_MOTOR_1OUT_AFB_STANDARD.PDL
Alarm View @PCS7_ALARM.PDL (see the SINGLE_LOOP_AFB)
Faceplate Frame @PG_MOTOR_1OUT_AFB.PDL (see the SINGLE_LOOP_AFB)
Faceplate Overview Window @PG_MOTOR_1OUT_AFB_OVERVIEW.PDL (see the SINGLE_LOOP_AFB)
Faceplate View List @PG_MOTOR_1OUT_AFB_VIEWLIST.PDL
Faceplate Loop View @PL_MOTOR_1OUT_AFB.PDL
2.3.4 MOTOR_2OUT_BLK
See MOTOR_1OUT_BLK for information about operation and controls.
View File
Standard @PG_MOTOR_2OUT_BLK_STANDARD.PDL
Alarm View @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Faceplate Frame @PG_MOTOR_2OUT_BLK.PDL (see the SINGLE_LOOP_BLK)
Faceplate Overview Window @PG_MOTOR_2OUT_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
Faceplate View List @PG_MOTOR_2OUT_BLK_VIEWLIST.PDL
Faceplate Loop View @PL_MOTOR_2OUT_BLK.PDL
2.3.5 MOTOR_A_BLK
Standard View
The standard view is the default view when the faceplate is first displayed in Group Display
mode. It displays the function block description, alarm status, and various motor status
values and motor configuration values.
● The Interlock indicator displays the current interlock status of the function block.
● The Start and Stop buttons allow operator control of the MOTOR. These buttons are only
enabled when the function block is in Manual mode.
● The Mode indicator displays the current mode of the function block (Auto/Manual).
● The FailureReset button lets operator clear the failure output.
● The Start Time indicator displays the maximum allowable time between the OUT signal
going TRUE and PROOF feedback going TRUE before the FAIL output goes TRUE. A
time to start MOTOR in excess of this value fires an alarm.
● The Stop Time indicator displays the maximum allowable time between the OUT signal
going FALSE and PROOF feedback going FALSE before the FAIL output goes TRUE. A
time to stop MOTOR in excess of this value fires an alarm.
● Clicking the Start, Stop or Reset buttons brings up a confirmation box and asks the user
to confirm the change, if the ConfirmChange attribute is TRUE. Start and Stop buttons
are only enabled when the function block is in Manual mode. The FailureReset button is
enabled when the tag FAIL is true.
Objects
The following table lists all of the significant objects on the standard view:
Interlocks View
The interlocks view is the same view used by the VALVE_A_BLK faceplate. See the
VALVE_A_BLK section for details.
View File
Standard @PG_MOTOR_A_BLK_STANDARD.PDL
Alarm @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Faceplate Frame @PG_MOTOR_A_BLK.PDL (see the SINGLE_LOOP_BLK)
Interlocks @PCS7_APACS_INTERLOCKS.PDL (see VALVE_A_BLK)
Faceplate Overview Window @PG_MOTOR_A_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
Faceplate View List @PG_MOTOR_A_BLK_VIEWLIST.PDL
Faceplate Loop @PL_MOTOR_A_BLK.PDL
2.3.6 MOTOR_A_ALM_BLK
See the MOTOR_A_BLK section.
Limits View
The Limits view shows the alarm configuration of the function block. Note that this faceplate
view is not specific to the MOTOR_A_ALM function block. Every function block that
implements discrete alarms references this .PDL file.
The Type indicators display the alarm type. These types are hard coded. For
MOTOR_A_ALM, they are displayed in the illustration that follows.
Objects
The following table lists all of the significant objects on the view:
Interlocks View
The interlocks view is the same view used by the VALVE_A_BLK faceplate. See the
VALVE_A_BLK section for details.
View File
Standard @PG_MOTOR_A_ALM_BLK_STANDARD.PDL (see the SINGLE_LOOP_BLK)
Alarm @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Faceplate Frame @PG_MOTOR_A_ALM_BLK.PDL (see the SINGLE_LOOP_BLK)
Interlocks @PCS7_APACS_INTERLOCKS.PDL (see the VALVE_A_BLK section)
Limits @PCS7_APACS_DISCRETE_ALARM_CONFIG.PDL
Faceplate View List @PG_MOTOR_A_ALM_BLK_VIEWLIST.PDL
Faceplate Overview Window @PG_MOTOR_A_ALM_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
Faceplate Loop View @PL_MOTOR_A_ALM_BLK.PDL
2.3.7 BLK_VLV_1OUT_BLK
Standard View
The Standard view is the default view when the faceplate is first displayed in Group Display
mode. It displays the function block description, alarm status, and various valve status
values and valve configuration values.
● Clicking the Open or Close buttons brings up a confirmation box, if the ConfirmChange
attribute is TRUE. These buttons are only enabled when the function block is in Manual
mode.
● Clicking the ModeControl box displays a discrete input confirmation box, if the
ConfirmChange attribute is TRUE and asks the user to select a choice from the radio
buttons displayed.
● Clicking the Enabled check box brings up a discrete input confirmation box, if the
ConfirmChange attribute is TRUE.
● Clicking the Travel Time I/O field brings up a time input edit box.
Objects
The following table lists all of the significant objects on the view:
View File
Standard @PG_BLK_VLV_1OUT_BLK_STANDARD.PDL
Alarm @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Faceplate Frame @PG_BLK_VLV_1OUT_BLK.PDL (see the SINGLE_LOOP_BLK)
Interlocks @PCS7_APACS_INTERLOCKS.PDL (see the VALVE_A_BLK section)
Faceplate View List @PG_BLK_VLV_1OUT_BLK_VIEWLIST.PDL
Faceplate Overview Window @PG_BLK_VLV_1OUT_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
Faceplate Loop View @PL_BLK_VLV_1OUT_BLK.PDL
2.3.8 BLK_VLV_2OUT_BLK
The BLK_VLV_2OUT_BLK faceplate is identical in every respect to the
BLK_VLV_1OUT_BLK except in the names of the PDL files and any associated attribute
values.
In addition, the .OPEN_LATCH parameter is exposed as the OUT tag in the mapper
template file instead of the .[OUT] for BLK_VLV_1OUT_BLK
See the BLK_VLV_1OUT_BLK section for details.
2.3.9 VALVE_A_BLK
Standard View
The Standard view is the default view when the faceplate is first displayed in Group Display
mode. It displays the function block description, alarm status, and various valve status
values and valve configuration values.
● The FailureReset button allows the operator to clear the valve's FAIL status. This button
is only enabled when the function block is in a failed state.
● The Open Time indicator displays the configured travel time of the function block. A valve
open time in excess of this value fires an alarm.
● The Close Time indicator displays the configured travel time of the function block. A valve
close time in excess of this value fires an alarm.
● Clicking the Permit or Interlock indicators switches to the Interlock view. If the faceplate is
in loop display mode, this action is ignored since the interlocks view is already being
displayed.
● Clicking the Open or Close buttons brings up a confirmation box, if ConfirmChange is
TRUE. These buttons are only enabled when the function block is in Manual mode.
● Clicking the Reset button brings up a confirmation box, if ConfirmChange is TRUE. This
button is only enabled when the function block is in FAIL mode.
● Clicking the ModeControl box displays a discrete input confirmation box, if
ConfirmChange is TRUE and asks the user to select a choice from the radio buttons
displayed.
● Clicking the Open Time or Close Time I/O fields displays a time input edit box.
Interlocks View
The Interlocks view displays permit status and description, and interlock status and
descriptions. It also allows the user to place the block into and out of override mode. Note
that this faceplate view is not specific to the VALVE_A_BLK function block. Every function
block that implements multiple interlock inputs references this .PDL file.
The Interlocks view actually has 11 interlock status indicators. The VALVE_A and
VALVE_A_ALM blocks only have 10 interlock inputs, so the 11th indicator is hidden in these
cases. The MOTOR_A and MOTOR_A_ALM blocks, which have 11 interlock inputs, will
display all 11 indicators.
Interlock indicators are displayed for all interlock inputs that have a non-blank interlock
description. Unused or unconfigured interlocks should be configured with a blank interlock
description in 4-mation. The faceplate will not display indicators for these unused interlocks.
configured in the block (by oversight) and in the case, the operator will not be able to see
the Status indicator of the interlock that may be preventing valve operation.
● Clicking the Override button brings up a confirmation box, if ConfirmChange is TRUE.
This button is only enabled when the function block is not in override mode.
● Clicking the Clear Override button brings up a confirmation box, if ConfirmChange is
TRUE. This button is only enabled when the function block is in override mode.
Interlock Objects
The following table lists all of the significant objects on the view:
View File
Standard @PG_VALVE_A_BLK_STANDARD.PDL
Interlocks @PCS7_APACS_INTERLOCKS.PDL
Alarm @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Faceplate Frame @PG_VALVE_A_BLK.PDL (see the SINGLE_LOOP_BLK)
Interlocks @PCS7_APACS_INTERLOCKS.PDL
Faceplate View List @PG_VALVE_A_BLK_VIEWLIST.PDL
Faceplate Overview @PG_VALVE_A_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
Window
Faceplate Loop View @PL_VALVE_A_BLK.PDL
2.3.10 VALVE_A_ALM_BLK
Standard View
The standard view is the same view used by the VALVE_A_BLK faceplate, but renamed.
See the VALVE_A_BLK section for details.
Interlocks View
The interlocks view is the same view used by the VALVE_A_BLK faceplate. See the
VALVE_A_BLK section for details.
Limits View
The Limits view is the same view used by the MOTOR_A_ALM_BLK faceplate, but renamed
AS follows For VALVE_A_ALM:
● Failure to close
● Failure to open
● Uncommanded close/open or rejected command (due to interlock)
● Failed limit switch (open and close verify inputs are set)
The Enabled check boxes control the enabled status of the alarms.
See the MOTOR_A_ALM_BLK section for details.
Alarm View
The Alarm view is the same view used by the SINGLE_LOOP_BLK faceplate. See the
SINGLE_LOOP_BLK section for details.
Faceplate Frame
The faceplate frame is the same view used by the SINGLE_LOOP_BLK faceplate, but
renamed. See the SINGLE_LOOP_BLK section for details.
View File
Standard @PG_VALVE_A_ALM_BLK_STANDARD.PDL (See the VALVE_A_BLK)
Interlocks @PCS7_APACS_INTERLOCKS.PDL (See the VALVE_A_BLK)
Limits @PCS7_APACS_DISCRETE_ALARM_CONFIG.PDL (See the MOTOR_A_ALM_BLK)
Alarm @PCS7_ALARM.PDL (see the SINGLE_LOOP_BLK)
Faceplate Frame @PG_VALVE_A_ALM_BLK.PDL (see the SINGLE_LOOP_BLK)
Faceplate View List @PG_VALVE_A_ALM_BLK_VIEWLIST.PDL
View File
Faceplate Overview Window @PG_VALVE_A_ALM_BLK_OVERVIEW.PDL (see the SINGLE_LOOP_BLK)
Faceplate Loop View @PL_VALVE_A_ALM_BLK.PDL
2.3.11 EXT_SET_BLK
The EXT_SET_BLK faceplate is identical to the SINGLE_LOOP_BLK faceplate except for
the addition of four tags as follows:
2.3.12 RATIO_SET_BLK
The RATIO_SET_BLK faceplate is identical to the EXT_SET_BLK faceplate except for the
addition of five tags as follows:
2.3.13 PRIMARY_BLK
The PRIMARY_BLK faceplate is identical to the SINGLE_LP_SS_BLK faceplate in all
respects except filenames.
See the SINGLE_LP_SS_BLK documentation for details on all other features.
2.3.14 SECONDARY_BLK
The SECONDARY_BLK faceplate is identical to the EXT_SET_BLK faceplate in all respects
except filenames.
See the EXT_SET_BLK documentation for details on all other features.
2.3.15 CASCADE_BLK
The CASCADE_BLK faceplate is essentially the PRIMARY_BLK and SECONDARY_BLK
faceplates combined into one faceplate.
The Standard view of the faceplate is shown below:
All other group views are identical to the PRIMARY_BLK and SECONDARY_BLK faceplate
views.
The loop view is different in that there is a button on the title bar to switch between
PRIMARY and SECONDARY loop views:
See the PRIMARY_BLK and SECONDARY_BLK documentation for details on all other
features.
2.3.16 SINGLE_LP_EM_BLK
The SINGLE_LP_EM_BLK faceplate is identical to the SINGLE_LOOP_BLK faceplate except
for the addition of one binary input (EM).
The tag structure (and HMI file) has one additional tag:
2.3.17 SINGLE_LP_SS_BLK
The SINGLE_LP_SS_BLK faceplate is identical to the SINGLE_LOOP_BLK faceplate except
for the addition of one binary input (SS).
The tag structure (and HMI file) has one additional tag:
A
F
AALM_AFB, 12
AALM_AFB Input Output, 14 Faceplate Frame MERGEFORMAT, 232
Alarming, 202
AM_AFB, 22
AM_AFB_Input_Output, 23 G
Analog Input Dialog Box MERGEFORMAT, 218
general differences, 198
ANALOG_ALM_AFB, 25
Global HMI Elements .PDL Files
ANALOG_ALM_AT, 181
MERGEFORMAT, 221
ANALOG_ALM_BLK Input Output, 27
ANALOG_ALM_BLK MERGEFORMAT, 236
APACS+ versus PCS 7 Controller Algorithm
I
Comparison, 202
Introduction, 9
B
L
BLK_VLV_1OUT_AFB, 32
BLK_VLV_1OUT_AT, 182 Library Blocks, 10
BLK_VLV_1OUT_BLK Input Output, 34 Library Description, 9
BLK_VLV_1OUT_BLK MERGEFORMAT, 252 Library Function Blocks, 10
BLK_VLV_2OUT_AT, 183
BLK_VLV_2OUT_BLK, 36
BLK_VLV_2OUT_BLK MERGEFORMAT, 254 M
Message class, 198
MOTOR_1OUT_AFB, 92
C
MOTOR_1OUT_AFB MERGEFORMAT, 242
CASCADE_AT, 183 MOTOR_1OUT_AT, 188
CASCADE_BLK, 41 MOTOR_1OUT_BLK Input Output, 94
CASCADE_BLK Input Output, 45 MOTOR_2OUT_AT, 189
CASCADE_BLK MERGEFORMAT, 264 MOTOR_2OUT_BLK, 97
Confirmation Dialog Box MERGEFORMAT, 220 MOTOR_2OUT_BLK Input Output, 99
Customizing the Library, 204 MOTOR_2OUT_BLK MERGEFORMAT, 245
MOTOR_A_AFB, 78
MOTOR_A_AFB Input Output, 81
D MOTOR_A_ALM_AT, 187
MOTOR_A_ALM_BLK, 86
DALM_AFB, 58
MOTOR_A_ALM_BLK Input Output, 89
DALM_AFB Input Output, 60
MOTOR_A_ALM_BLK MERGEFORMAT, 248
Discrete Input Dialog Box MERGEFORMAT, 219
MOTOR_A_BLK MERGEFORMAT, 245
DISCRETE_ALM_AT, 185
DISCRETE_ALM_BLK, 64
DISCRETE_ALM_BLK Input Output, 65
P
DISCRETE_ALM_BLK MERGEFORMAT, 239
Performance Data, 208
PID_AFB, 102
E PID_AFB Input Output, 102
PRIMARY_AT, 190
EXT_SET_AT, 185
PRIMARY_BLK, 104
EXT_SET_BLK, 66
PRIMARY_BLK Input Output, 107
EXT_SET_BLK Input Output, 69
PRIMARY_BLK MERGEFORMAT, 264
Index
R
RATIO_SET_AT, 191
RATIO_SET_BLK, 113
RATIO_SET_BLK Input Output, 117
RATIO_SET_BLK MERGEFORMAT, 263
S
SECONDARY_BLK, 124
SECONDARY_BLK Input Output, 127
SECONDARY_BLK MERGEFORMAT, 264
SETPNT_AFB, 134
SETPNT_AFB Input Output, 136
SETPOINT, 134
SINGLE_LOOP_AFB Faceplate View List
MERGEFORMAT, 233
SINGLE_LOOP_AFB MERGEFORMAT, 227
SINGLE_LOOP_AFB Trend View
MERGEFORMAT, 230
SINGLE_LOOP_AFB_ Tuning View
MERGEFORMAT, 228
SINGLE_LOOP_AT, 193
SINGLE_LOOP_BLK, 138
Single_Loop_BLK Loop View MERGEFORMAT, 233
SINGLE_LOOP_BLK View .PDL Files
MERGEFORMAT, 234
SINGLE_LP_BLK Input Output, 141
SINGLE_LP_SS_AT, 194, 195
SINGLE_LP_SS_BLK Input Output, 149, 159
SINGLE_LP_SS_BLK MERGEFORMAT, 265
T
Template Charts, 180
Time Input Dialog Box MERGEFORMAT, 219
V
VALVE_A_AFB, 172
VALVE_A_AFB Input Output, 175
VALVE_A_ALM_AT, 196
VALVE_A_ALM_BLK, 166
VALVE_A_ALM_BLK Input Output, 168
VALVE_A_ALM_BLK MERGEFORMAT, 259
VALVE_A_BLK MERGEFORMAT, 255