1 2 3 4 5 6 7 Simatic: Manual
1 2 3 4 5 6 7 Simatic: Manual
Preface, Contents
Introduction 1
Template Charts 3
PCS 7/APACS+ ES
Message Class 4
Library User’s Guide
for V6.1 Differences between 5
APACS+ and PCS 7
Manual
Customizing the Library 6
Peformance Data
7
Edition 04/2006
A5E00595270-01
Safety Guidelines
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 to property damage only have no safety alert symbol. The
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 notice 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 notices 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.
Prescribed Usage
Note the following:
Warning
! This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.
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.
Training Centers
Siemens Technical Training Center 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.sea.siemens.com/sitrain
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.
Internet: http://www.sitrain.com
Nürnberg
vi A5E00595270-01
1 PCS 7 ES Option for APACS+
Additional Topics:
Faceplates and Graphic These pre-configured Human-Machine Interface (HMI)
Symbols 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.
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.
2.2 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.
Input
Note
This list differs from the inputs of the AALM_AFB block in APACS+ as follows:
x In APACS+, there are only four enables. There is now an enable for every
alarm type.
x The parameter QBAD was added to get quality information from the control
system.
x The parameters EV_ID and EV_ID2 were added to support the message
system.
x 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:
x In APACS+, there are only four alarms and four NAKs. There is now one of
each for every alarm type.
x The STATUS and CMD outputs have been removed.
x 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:
x 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.
x There is now a LIMIT, DEADBAND, DELAYIN, and DELAYOUT parameter for
each alarm type that requires it.
x The PCS 7 OS provides a ringback mechanism. The RINGBACK parameters
have been removed.
2.3 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.
Input
Output
Note
The list differs from the outputs of the AM block in APACS+ as follows:
Input/output
Note
This list differs from the softlist parameters of the AM block in APACS+ as follows:
2.4 ANALOG_ALM_AFB
Function
The Analog Alarm Function Block (ANALOG_ALM_AFB) 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.
Input
Output
Input/output
2.5 BLK_VLV_1OUT_AFB
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.
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 from the inputs of the BLK_VLV_1OUT_AFB block in APACS+ as
follows:
Output
Input/output
2.6 BLK_VLV_2OUT_AFB
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.
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, allwoing 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.
Input
Note
This list differs from the inputs of the BLK_VLV_2OUT_AFB block in APACS+ as
follows:
Output
Input/output
2.7 CASCADE_AFB
Function
CASCADE_AFB 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.
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, 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
x the block is forced to start in Auto mode, or
x 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.
Input
Note
This list differs significantly from the inputs of the CASCADE_AFB 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
2.8 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.
Input
Note
This list differs from the inputs of the DALM_AFB block in APACS+ as follows:
x There are now eight inputs and enables.
x Only the first alarm’s input and enable will be visible, so that the block will look
like the APACS+ HLLDA1 block.
x The parameter EV_ID was added to support the message system.
x 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:
x There are now eight alarms and NAKs.
x Only the first alarm’s output and NAK are visible. This makes the block look
similar to the APACS+ HLLDA1 block.
x The STATUS and CMD outputs have been removed.
x 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:
x The PCS 7 OS provides a ringback mechanism, so the ringback parameters
have been removed.
x There are now eight LIMIT, DELAYIN, and DELAYOUT parameters.
2.9 DISCRETE_ALM_AFB
2.9.1 DISCRETE_ALM_AFB
Function Block Name DISCRETE_ALM_AFB
(compiled version of the Chart)
Function Block Number FB604
Chart Name DISCRETE_ALM
See also, Template Chart DISCRETE_ALM_AT
(usage example)
Function
The Discrete Alarm (DISCRETE_ALM_AFB) 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.
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_AFB looks like its APACS+
counterpart. The DI input was changed to DIN for compatibility with the HMI.
Output
Input/output
2.10 EXT_SET_AFB
Function
The External Setpoint Controller (EXT_SET_AFB) 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_AFB 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.
"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.
Input
Note
This list differs significantly from the inputs of the EXT_SET_AFB 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_AFB 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
2.11 MOTOR_A_AFB
Function
The Standard Motor Function Block (MOTOR_A_AFB) 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:
x 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.
x 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.
x 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:
x Failure to start before the STRT_T has expired
x Failure to stop before the STOP_T has expired
x Loss of proof
x Uncommanded stop due to loss of an interlock (enabled by setting the
FAIL_ON_INTRLK value to TRUE)
x 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_AFB 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:
x Connect a boolean interlock condition to the Interlock input.
x 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.
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 from the inputs of the MOTOR_A_AFB block in APACS+ as follows:
x Each input shown above with datatype STRING was a softlist parameter in APACS+.
x 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.
x 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+.
x Restart parameters (RSTRT_... ) did not exist in APACS+.
x LIOP_MAN_SEL and AUT_L added to provide alternate for SET_VAL function.
x Batch parameters BA_EN, OCCUPIED are added to support future batch faceplate
view.
x Batch parameters BA_NA, BA_ID, STEP_NO are added to pass batch values in alarm
messages.
x 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:
x FAIL and AUTO and OVERRD have been moved to In/Out in PCS 7.
x ALARM_STATE is a new output. In APACS+, it was a softlist parameter.
x 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+.
x 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:
x 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.
x ALARM_STATE was moved to Output.
x 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..
x INT01_DESC through INT10_DESC and PERMIT_DESC have been moved to Inputs.
x STRT_T and STOP_T are named START_T and STOP_T in APACS+. The
ProcessSuite names STRT_T and STOP_T are preferred.
x The following alarm parameters are new: A1EN, A1LIM, A1DELAYIN, A1DELAYOUT,
OOS, DISABLE_ON_OOS. These are needed to support the alarming functionality.
2.12 MOTOR_A_ALM_AFB
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_AFB block with
a discrete alarm block. To provide thorough alarm reporting, the alarm state value
of the MOTOR_A_AFB block is used to create separate alarms for the following
conditions:
x Failure to start (or loss of proof)
x Failure to stop (or unexpected proof)
x Uncommanded stop or rejected start command (due to interlock)
The latched fail state of the MOTOR_A_AFB block is unlatched automatically when
the alarm is acknowledged.
The parameters are generally identically to those of the MOTOR_A_AFB block.
See MOTOR_A_AFB 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:
x Connect a boolean interlock condition to the Interlock input.
x 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.
Input
Output
Input/output
2.13 MOTOR_1OUT_AFB
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.
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 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.
Input
Note
This list differs from the inputs of the MOTOR_1OUT_AFB block in APACS+ as
follows:
Output
Input/output
2.14 MOTOR_2OUT_AFB
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.
Input
Note
This list differs from the inputs of the MOTOR_2OUT_AFB block in APACS+ as
follows:
Output
Input/output
2.15 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.
Input
Note
This list differs from the inputs of the PID_AFB block in APACS+ as follows:
x The SAMPLE_T input is required for the block to obtain the scan rate.
Output
Input/output
2.16 PRIMARY_AFB
Function
The Primary Controller (PRIMARY_AFB) 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_AFB block is designed to be
used with the SECONDARY_AFB 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.
desired forced value. The RSTRT_SP_VALUE will be used to initialize SP, if the
RSTRT_SP_FLAG is true and either
x The block is forced to start in Auto mode, or
x AUTO is not forced and the block restarts with Auto mode (AUTO="Auto") and
in secondary cascade (CASC_S = "True").
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.
Input
Note
This list differs significantly from the inputs of the PRIMARY_AFB block in
APACS+. In APACS+, only the PV, FDBK and CASC_S inputs are present.
Output
Note
Input/output
2.17 RATIO_SET_AFB
Function
The Ratio Setpoint Controller (RATIO_SET_AFB) 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_AFB 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.
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
Output
Input/output
2.18 SECONDARY_AFB
Function
The Secondary Controller (SECONDARY_AFB) 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_AFB block is designed to
be used with the PRIMARY_AFB 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_AFB 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.
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, 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.
Input
Note
This list differs significantly from the inputs of the SECONDARY_AFB block in
APACS+. In APACS+, only the PV and EXT_SP inputs are present. EXT_SP is
now ESP.
Output
Note
Input/output
2.19 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:
x Internal setpoint (ISP)
x 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.
Input
Note
This list differs from the inputs of the SETPNT_AFB block in APACS+ as follows:
Output
Note
This list differs from the outputs of the SETPNT_AFB block in APACS+ as follows:
x 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:
x AUTO and RAMP have been moved from input to input/output.
x RTIME has been moved from output to input/output.
2.20 SINGLE_LOOP_AFB
2.20.1 SINGLE_LOOP_AFB
Function Block Name SINGLE_LOOP_AFB
(compiled version of the Chart)
Function Block Number FB611
Chart Name SINGLE_LOOP
See also, Template Chart SINGLE_LOOP_AT
(usage example)
Function
The Single Loop Controller (SINGLE_LOOP_AFB) 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_AFB 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.
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
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
2.21 SINGLE_LP_SS_AFB
Function
The Single Loop Controller with Standby Sync (SINGLE_LP_SS_AFB) 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_AFB 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 variable [PV] in manual or standby sync mode (AUTO=FALSE or
SS=TRUE). The CONTROLLER block is a PID_AFB block; it operates when
AUTO=TRUE and SS=FALSE and tracks the downstream output [OUT] in manual
or standby sync mode. The AUTO_MANUAL block provides standby sync and
manual control of the output. In standby sync 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.
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 the
RSTRT_SP_FLAG is true and either
x The block is forced to start in Auto mode, or
x AUTO is not forced and the block restarts with Auto mode (AUTO="Auto") and
not in standby sync (SS = "False").
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.
Input
Note
This list differs significantly from the inputs of the SINGLE_LP_SS_AFB 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_AFB 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
2.22 VALVE_A_ALM_AFB
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_AFB block with a
4-element discrete alarm block. To provide thorough alarm reporting, the alarm
state value of the VALVE_A_AFB block is used to create separate alarms for the
following conditions:
x Failure to open (or loss of open verify)
x Failure to close (or loss of close verify)
x Uncommanded close/open or rejected command (due to interlock)
x Failed limit switch (Open and close verify inputs are set)
The latched fail state of the VALVE_A_AFB block is unlatched automatically when
the alarm is acknowledged.
The parameters are generally identical to those of the VALVE_A_AFB block. See
VALVE_A_AFB 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:
x Connect a boolean interlock condition to the Interlock input.
x 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.
Input
Output
Input/output
2.23 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:
x 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.
x 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.
x 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
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:
x Connect a boolean interlock condition to the Interlock input.
x 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.
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 from the inputs of the VALVE_A_AFB block in APACS+ as follows:
x Each input shown above with datatype STRING was a softlist parameter in
APACS+.
x 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.
x 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+.
x Restart parameters (RSTRT_... ) did not exist in APACS+.
x LIOP_MAN_SEL and AUT_L added to provide alternate for SET_VAL function.
x Batch parameters BA_EN, OCCUPIED are added to support future batch
faceplate view.
x Batch parameters BA_NA, BA_ID, STEP_NO are added to pass batch values
in alarm messages.
x 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:
x FAIL and AUTO and OVERRD have been moved to In/Out in PCS 7.
x ALARM_STATE is a new output. In APACS+, it was a softlist parameter.
x 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+.
x 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:
x 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.
x ALARM_STATE was moved to Output.
x 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.
x INT01_DESC through INT10_DESC and PERMIT_DESC have been moved to
Inputs.
x FAIL_OPEN is named FAIL_OPEN_VALVE in APACS.
x OPEN_T and CLOS_T are named OPEN_TIME and CLOSE_TIME in
APACS+.
x The following alarm parameters are new: A1EN, A1LIM, A1DELAYIN,
A1DELAYOUT, OOS, DISABLE_ON_OOS. These are needed to support the
alarming functionality.
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
MOTOR_A_ALM_AT
VALVE_A_ALM_AT
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:
x 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_AFB
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:
x To set the VALVE block’s maximum allowed time to open and close, set the
parameter TRAV_T of the VALVE block.
x Interlock
Faults
Channel faults are detected by the input and output drivers.
See also:
BLK_VLV_1OUT_AFB
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:
x To set the VALVE block’s maximum allowed time to open and close, set the
parameter TRAV_T of the VALVE block.
x Interlock
Faults
Channel faults are detected by the input and output drivers.
See also:
BLK_VLV_2OUT_AFB
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
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_AFB
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_AFB
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:
x All tuning parameters (PG, TI, TD and DG)
x All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
x Valve scaling units (VL_EUMIN, VL_EUMAX)
x 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.
x 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_AFB
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:
x Failure to start (or loss of proof)
x Failure to stop (or unexpected proof)
x 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:
x 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.
x Interlocks and Interlock descriptions.
x Permit and Permit description.
Faults
Channel faults are detected by the input and output drivers.
See also:
MOTOR_A_ALM_AFB
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:
x 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.
x Interlock
Faults
Channel faults are detected by the input and output drivers.
See also:
MOTOR_1OUT_AFB
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:
x 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.
x Interlock
Faults
Channel faults are detected by the input and output drivers.
See also:
MOTOR_2OUT_AFB
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
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_AFB
SECONDARY_AFB
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:
x All tuning parameters (PG, TI, TD and DG)
x All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
x Valve scaling units (VL_EUMIN, VL_EUMAX)
x 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.
x 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_AFB
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:
x All tuning parameters (PG, TI, TD and DG)
x All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
x Valve scaling units (VL_EUMIN, VL_EUMAX)
x 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.
x 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_AFB
3.13 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:
x All tuning parameters (PG, TI, TD and DG)
x All high/low alarm and absolute deviation limits (H_LIM, L_LIM, AD_LIM)
x Valve scaling units (VL_EUMIN, VL_EUMAX)
x 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.
x 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_AFB
3.14 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:
x Failure to open (or loss of open verify)
x Failure to close (or loss of close verify)
x Uncommanded close/open or rejected command (due to interlock)
x 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:
x 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.
x Interlocks and Interlock descriptions
x Permit and Permit description
x Fail-safe state of the valve (FAIL_OPEN)
Faults
Channel faults are detected by the input and output drivers.
See also:
VALVE_A_ALM_AFB
*1) If the block is used for operation messages, the inputs I_1, ... have to be
supplied with pulses. Assignment of the static value 1 would lead to multiple
messages.
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:
APACS+ maximum time 49d17h2m47s295ms
PCS 7/APACS+ ES Libraries maximum 24d20h31m23s647ms
time
PCS 7 combines the functions of local variables, Input/output nubs, and softlist
parameters into block parameters. Block parameters can be viewed as physical
Input/output nubs on the block or by selecting to view the block parameters. You
might say that all parameters are now "softlist" parameters that can also be viewed
as block nubs on a per instance basis by the user. Referring back to the example
of Single_Loop operating within PCS 7, the user can define the initial state of the
parameter AUTO. This value will be used the first time the configuration is
downloaded to the controller. A feature exists within PCS 7 that allows the user to
read back parameters such as AUTO. Once this is done, the initially configured
value will be overwritten. For example:
1. The original configuration of AUTO was defined as TRUE.
2. The configuration is then downloaded to the controller. This loop starts in
Auto.
3. The operator changes the controller to Manual (AUTO=FALSE).
4. The user performs a read back or upload.
5. The user then downloads the configuration to the controller again.
6. This loop will now start in Manual and not Auto.
The addition of Restart Logic in the APACS+ Library blocks allows the user to
define a restart state independent of the user performing a readback or upload of
the controller configuration. See the help for each FB for an explanation of the
restart parameters provided. See the section on Read Back (S7) for additional
information on this PCS 7 functionality.
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:
BA_EN Batch enabled
OCCUPIED Occupied by batch
BA_NA Batch name
BA_ID Batch ID number
STEP_NO Batch step number
The batch parameters have been added as inputs to most of the control blocks for
support of batch operations. A future Batch View faceplate or a customized
faceplate may display the values in the HMI corresponding to these parameters.
The current values of BA_NA, BA_ID and STEP_NO are available for transmitting
in alarm messages to the HMI, so that these values may be displayed and logged.
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):
x Operator changes are "one-step", no further confirmation is required.
x all choices that are two-state, such as Auto/Manual, will immediately toggle to
the other state.
x 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:
x 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.
x all choices including two-state choices require confirmation.
x Increase/Decrease buttons will be invisible.
Note that in both cases all operator changes are sent to the Operation List log.
APACS+ Algorithm
The transfer function used in the APACS+ controller (plus the Model 352 et. al.) is
shown below:
ª§ · º
§ 1 · « ¨ TDs ¸ »
OUT PG¨1 ¸ «¨ 1¸ PV SP »
© TIs ¹ «¨¨ TD s 1 ¸ »
¸
¬«© DG ¹ ¼»
implemented as a function of both the derivative time and the derivative gain. The
benefit of this is that since derivative filtering is always directly proportional to the
derivative time for a given derivative gain, satisfactory derivative response is
obtained over a wide range of derivative time values without requiring an
adjustment to the derivative gain value. The derivative gain can be adjusted to
provide more or less filtering, if desired, but the default value of 10.0 is usually
sufficient for most applications.
PCS 7 Algorithm
The default transfer function used in the PCS 7 controller is shown below:
§ 1 TVs ·
LMN GAIN ¨¨1 ¸¸SP PV _ IN
© TNs 1 TM _ LAGs ¹
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 can be removed by setting (Proportional Select) P_SEL = 0. By
optionally setting (Proportional Action in Feedback Path Select) PFDB_SEL =
TRUE, the proportional action can be directly applied to the process variable,
PV_IN, instead of the error.
The integral action is always applied to the gain*error and can be removed by
setting TN = 0 or can be reversed by setting TN < 0. The controller does have a
manipulated variable feedback signal input, LMNR_IN, however it is used only by
the PCS 7 OS, it is not used as a reset feedback signal for implementing the
integral action.
The derivative action can be removed by setting TV =0 or can be reversed by
setting TV < 0. By optionally setting (Derivative Action in Feedback Path Select)
DFDB_SEL = TRUE, the derivative action can be directly applied to the process
variable, PV_IN, instead of the error. In this controller implementation, the
derivative filter, TM_LAG, is completely independent of the derivative time, TV. The
significance of this is that the derivative filter component is essentially a fourth
tuning parameter that must be manually set separately and in relation to the
derivative time; otherwise the derivative action will become too aggressive as the
derivative time is increased. Normally, TM_LAG should be set to approximately (TV
/ 10) which effectively yields a derivative gain of 10.
These instructions describe customization of the source charts and files, including
compilation to create new block types and modifcation of the graphical elements.
The following procedures are detailed below:
x Create new block types
x Modify graphical elements
x Test the changes
Procedure Example
1. From SIMATIC Manager, copy the 1. From the SIMATIC Manager main menu, select File >
Library. Open. The Open Project dialog box appears. Click
the Libraries tab, and select APACS Library. From
the main menu,
select File > Save As New APACS Library.
2. Open the Plant View of the Library. 2. From the main menu, select View > Plant View.
3. Copy the source chart to be modified. 3. In the Source Charts\Control hierarchy folder, copy
and paste SINGLE_LOOP. Rename the copy to
NewSINGLE_LOOP.
4. Make the necessary modifications. 4. Add Message Error and Message Status outputs to
Type.
6. Assign a new number, name and 6. a. On the General tab, change Symbolic Name to
comment. NewSLOOP, change the FB Number to 650.
b. On the Attributes tab, change S7_m_c value to
true.
7. Complete the compile. 7. Click OK.
8. Close the window.
Modify Graphical Elements
Note: All changes must be made to files in the siemens\wincc\options\pdl\faceplatedesigner_v6
directory for the changed files to be automatically copied to subsequent projects. If the changes are
made in a project directory, they will only be effective in that project.
Procedure Example
1. Start Graphics Designer from an 1. Double-click on Graphics Designer from PCS 7 OS,
existing project in PCS 7 OS. WinCC Explorer.
2. Update the block icon for the new 2. From Graphics Designer, open
type. siemens\wincc\options\pdl\faceplatedesigner_v6\
@PCS 7 Typicals.pdl
3. Copy desired symbol (block icon). 3. Copy and paste the Single_Loop_AFB symbol to an
empty space on the graphic.
4. Edit properties of the new symbol. 4. a. Right-click to edit properties of the new symbol.
In the Customized Object property, change Object
Name to @NewSloop/1 by double-clicking on Object
Name in the Attribute column.
b. In UserDefined3 property, edit Type to
@NewSloop/1, and edit Servername to
@NewSloop/1.
c. Click OK.
d. Close the Object Properties window.
5. Save the file. 5. Save the @PCS 7 Typicals.pdl file.
6. From the 6. From Windows Explorer, change the directory to:
siemens\wincc\options\pdl\faceplated siemens\wincc\options\pdl\faceplatedesigner_v6
esigner_v6 directory in Windows
Explorer:
The column headings for the performance data table have the following meanings:
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.
*Note: The typical run times shown above were measured when alarms were not
occurring. For blocks with alarming capability, execution time will increase when
the block has an unacknowledged alarm. For blocks with analog alarms,
approximately .140 milliseconds will be added to the average time shown in the
table for each message containing at least one unacknowledged alarm. For blocks
with discrete alarms, approximately .125 milliseconds will be added to the average
time shown in the table for each message containing at least one unacknowledged
alarm.