Using Fieldbus

For the average user an understanding of the behavior of the function blocks is the most important
knowledge. A control loop. for example fig. 2.10, typically contains at least an Al block (transmitter), a PID
block (controller) and an AO block (valve). The fact that these may be in three separate devices puts
many requirements on the interoperation between these blocks. For example, if the operator takes over
control of the valve, the controller must be informed in order not to windup, and to be able to make a
bumpless transfer when the operator returns control of the valve. Likewise the controller must stop
integration if the measurement from the transmitter is bad or non existent.
Modes
The mode has two functions: setpoint selection and output selection. You may compare this to the classic
control modes: Local/Remote and Automatic/Manual respectively. There are also modes for 'Out of service'
and 'local override' (safety). The number of modes implemented in a device varies from block to block.
The generic block in figure 3.1 also illustrates that input blocks have no setpoint selection and that output
blocks have no output selection.

Figure 3.1
Generic Block

To generalize the meaning of the operating modes:

OutputSelection:

Automatic: The block algorithm calculates the output using its inputs. This is the only mode in the output
selection grouping where a setpoint is used.

Manual: The output is set by the operator.

Local Override: The output follows a tracking parameter provided by another block, for example a safety
value. This mode is only set by a special block input.
Initialization: The block is balancing its output, i.e., following a feedback value provided by a
downstream block.

Remote output: The block output is calculated and provided by a host computer.

Setpoint selection:

Local: The block calculates the output using its inputs and the setpoint from the operator.

Cascade: The block calculates the output using its inputs and the setpoint from a remote block.

Remote cascade: The setpoint is calculated and provided by a host computer. The output is calculated by
the block itself.

Setpoint tracking: This is only valid with Manual output selection. The setpoint is following the process
variable.

In a block there are several different mode parameters, each with a particular function:

Target mode: The mode requested by the operator. Only the modes allowed by the Permitted mode may
be selected. The block will try to achieve this mode and may or may not succeed depending on various
block and device conditions.

Actual mode: The prevailing mode of the block. Depending on current conditions it may or may not be
the same as the target mode. It may change not only on the user's request, but due to other events.

Permitted: defines the modes made available to the operator. It is configured by the process engineer
before operation.

When a block is instantiated, brought into operation, the initial mode will be out of service. Once in
operation the last mode will remain through a power cycle. When a block is executed, the mode is first
determined from the status bits of the various setpoint, output and feedback sources, and the overall
device status.
Status bits
Microprocessor-based equipment are able to detect errors in their hardware. This information is used to
inform the quality of the variables passed in order to prevent integral windup in control blocks, and to
provide a mechanism for blocks to shed to safety modes. All function block inputs and outputs are
accompanied by statuses. For example:
quality: Good, dubious, bad or out of service bad may be due to no communication, hardware
failure, etc.
initialize request: Force upstream block to initialize to provide bumpless transfer.
Limited high, by limiter in downstream block
Limited low, by limiter in downstream block

Statuses received with inputs from other blocks indicating discontinuities in control may cause the block to
change its mode automatically. Such action is called 'shedding.' When the condition causing the shedding
disappears, the mode will typically revert back to the previous mode. The user may configure to which
mode the block is allowed to shed. The status of the output variables of a block depends on the block
mode. A failure in one block may therefore lead to a chain reaction of mode shedding ensuring that all
blocks are in an appropriate mode.
Cascade structure
The cascade structure is an important concept in the building of control strategies. In a wider sense,
cascade structure is now taken to mean that the output of one block, typically a PID block, is linked to the
cascade setpoint of another block, not necessarily a PID block, but typically an output block. The block
providing the output is said to be 'upstream' in the signal path and the block receiving the cascade
setpoint is said to be 'downstream.' Therefore, the cascade setpoint is, in a wider sense, coming from an
upstream block, while the receiving block manipulates its output accordingly.

A feedback path is also provided in a cascade structure. The downstream block in the cascade structure
may not always be able to accept the cascade setpoint from the upstream block. For example, if the
cascade setpoint is not used because of the blocks mode, or beyond the limits set for it in the block or if
the block is not able to move the actuator. If the upstream block is not informed that it may not move its
output further, the integrating action of the PID controller may windup, or in the case of other blocks, it
may think it is actuating though it is not. The status in the feedback value allows the downstream block to
inform the up stream block what is going on. The PID block may also use the feedback value to balance its
output.
Applications
Many function blocks have been defined. They may be combined to make the most simple measurement
using only a single analog input block, and to build classic control strategies like single loop, cascade,
ratio, cross limit etc., or even more complex schemes of which some are shown in figures 3.2 through 3.4.

Figure 3.2
Measurement

Figure 3.3
Single Loop

Figure 3.4
Cascade Control

The most basic input and output parameters are explained below:
IN:process variable input

OUT: primary output of the block

CAS_IN: input for remote setpoint from another block cascaded setpoint.

BKCAL_IN: Feedback input from downstream block. Value used for initialization, balancing, of block
output to ensure bumpless setpoint transfer in downstream block when it returns to Local mode.

BKCAL_OUT: copy of selected setpoint to be used by upstream block for initialization of its output.

RCAS_IN: input for setpoint from a host, selected in Remote cascade mode.

RCAS_OUT: copy of the selected setpoint, value identical to BKCAL_OUT, but status is based on RCAS_IN
communication.

ROUT_IN: input for remote output from host, selected in Remote output mode.

ROUT_OUT: copy of the selected output, OUT, but with status based on ROUT_IN communication.

SP (contained): setpoint set by operator in local mode, or setpoint after limitation of setpoint received
from other block or a host.