41 S 3 Fcpics
41 S 3 Fcpics
PSS 41S-3FCPICS
Product Specification
April 2019
www.schneider-electric.com
Legal Information
Schneider Electric, EcoStruxure, Foxboro, I/A Series, and Triconex are trademarks
and the property of Schneider Electric SE, its subsidiaries and affiliated companies. All
other trademarks are the property of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished
for informational use only. No part of this guide may be reproduced or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), for any purpose, without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide
or its content, except for a nonexclusive and personal license to consult it on an "as is"
basis.
Overview
The EcoStruxure™ Foxboro™ DCS Process Automation System’s (The Foxboro DCS
system) Integrated Control Software provides for the integration of continuous, ladder
logic and sequential control in a Foxboro DCS control strategy.
The Foxboro DCS system Integrated Control Software provides a selection of
continuous, sequential, and ladder logic control domains. Each domain can be used
independently or integrated to meet specific application requirements.
The Control Software provides the user with a comprehensive control strategy and
input/output implementation for on/off control, timing, regulatory and feedback
applications. Implemented within a block and parameter structure, the Control
Software provides the base for the integration of continuous, ladder logic, and
sequential control with programmable logic controller functionality.
The software control strategies allow you to mix and match continuous and
Programmable Logic Block (PLB) capabilities with sequencing in the same control
scheme.
The process control domains – continuous, sequential and batch, and ladder logic –
execute in any Foxboro DCS control processor.
The Control Software running in a control processor provides the interface to the
Fieldbus subsystem and other I/O subsystems through I/O blocks. These I/O blocks
interface to the specific applications executing in the Foxboro DCS Fieldbus Modules
(FBMs).
Access to the FBMs and associated devices (for example, field sensors, actuators,
Intelligent Field Devices) is through the Control Software in the Foxboro DCS Field
Control Processor 280 (FCP280).
An optional fault-tolerant control processor configuration, where two identical control
processors (Primary and Shadow) are running in parallel, provides enhanced
reliability to the control process.
For more information on the FCP280, refer to Field Control Processor 280 (FCP280)
(PSS 41H-1FCP280).
Features
• Integration of continuous, sequential, and ladder logic control domains for ease of
implementing complex control strategies for a wide variety of process control
applications
• Comprehensive set of continuous control blocks (algorithms) for input/output,
valve/motor control, regulatory control, computation, logic, and alarming
• Comprehensive set of ladder logic instructions for designing modular solutions to
logic control problems in familiar, easy-to-use relay ladder symbols
• High-level sequence programming language provides a comprehensive set of
sequence logic instructions for developing sequential, feedback-oriented
applications at equipment control level
• Integration of control blocks within groups for ease of configuring control
strategies
• EXACT® MV advanced control algorithms provide adaptive feedback and
feedforward PID control capability with pre-tuning functions
• Configuration of continuous block types, ladder logic, and sequential blocks via
the following flexible, intuitive, user interfaces:
◦ Foxboro DCS Control Editors (Control Editors), including the Block
Configurator, Programmable Logic Block (PLB) Ladder Logic Editor, the
Sequence Block HLBL Editor, and the Sequence Block SFC Editor
◦ The I/A Series® Configuration Component (IACC) software
◦ Integrated Control Configurator
• Reuse of block configurations from one controller to another
At the beginning of block processing, I/O data is read from each Fieldbus Module, for
both input and output channels. Data is read at the ECB scan period specified for that
module. However, data cannot be read faster than the BPC. At the end of block
processing, process outputs are written to each of the Fieldbus Modules.
Station Block
Each control processor contains a station block automatically created to provide
global data on control processor system functions. The station block contains
information such as:
• Continuous block processing load
• I/O scan load
• Sequence block processing load
• Total control cycle load
• Basic processing cycles and overruns
• Number of bytes of free memory
• Number of peer-to-peer connections
• OM scan load
• Idle time
• Station alarm groups
• Configuration security option
Previous CPs only supported one I/O channel to an HDLC fieldbus (which provides
communication to a chain of Fieldbus Modules) directly, or used external hardware,
such as the FEM100 (discussed in PSS 31H-2Y14) to support up to four I/O channels.
However, the FCP280 supports four I/O channels directly, without the use of such
external hardware.
Every HDLC fieldbus’ channel requires a software driver in the CP called a Primary
ECB. Thus, the FCP280’s Compound has four Primary ECBs - one for each channel -
through which the station block directs all communications. Each of its FBM’s ECBs
must be assigned to the Primary ECB for the channel on which their FBM resides via
a new parameter added to them called “CHAN”.
The feedforward input may be used to anticipate the effect of a measured load or an
interacting controller.
The control processor must be sized so that it does not exceed any of the following
limits:
• Maximum number of FBMs allowed
• Maximum throughput of the Fieldbus
• Available memory to store the control blocks
• Available memory to store the Object Manager (OM) scanner databases
• Available time for processing control blocks and ECBs
NOTE: The control processor should be sized following the guidelines in Field
Control Processor 280 (FCP280) Sizing Guidelines and Excel Workbook
(B0700FY).
Any block can be connected to any other block anywhere in the system. Compound
names must be unique within the system. Block names must be unique only within a
Compound.
Input/Output Blocks
I/O blocks provide the interface to the process inputs and outputs, (for example,
sensors and valves). The I/O blocks relate logical names, such as FLWTRNS100, to
physical hardware point addresses, identified by the device ID and point number.
All references to I/O points from control configuration, displays, data logging, and so
on use a logical name instead of the physical address.
FBMs read the I/O data from the process instrumentation when the Block Processing
Cycle begins. The FBM then conditions (for example, digitizes and normalizes) the
data where necessary, and stores the data and the status into its ECB. When the
control blocks are processed, the Control Processor uses newly retrieved data and
generates new outputs for the appropriate ECB.
Some ECB(s) also provide an extended communications interface for a direct
interchange between The Foxboro DCS system and field devices using various digital
protocols. The field devices incorporate intelligence at the hardware device level
(signal conditioning and process control) and use the ECBs in the FCP280 to provide
the information to the control blocks.
Alarming
The control blocks provide a comprehensive set of I/O alarm indicators and messages
including:
• Bad input and output point alarming
• High/low absolute alarming of the analog measurement, input or output signal
• Deviation alarming of the setpoint minus measurement error
• Contact state change alarming
• Priority level (1 to 5) indication of alarms
• Alarm type indication of the highest-priority active alarm for the block
When an alarm occurs, the Alarm Manager notifies the operator via messages on
process displays and alarm printers, alarms horns and annunciator keyboards. High/
low absolute and deviation alarm limits, alarm enable/disable options, and other block
alarm parameters are set via the Control Editors, IACC, or ICC configurators.
The PLB Detail Display, automatically created after ladder logic configuration, allows
you to monitor the status of ladder logic contacts, timers, counters, and coils through a
ladder diagram display, which uses industry standard symbols, or through graphic
displays that you create.
Sequence blocks contain logic that supervises the control loops. The logic regulates
such things as:
• Pressure control
• Temperature control
• Agitator control
• Ingredient fills
• Gas control
Sequential control is a series of equipment control level activities such as filling a tank,
blending its contents, and draining the tank.
In the sequential control domain, on the other hand, you can build your own
algorithms using a logical set of parameters within the control compound/block
structure. Sequence block algorithms can also read and write other compound/block
parameters directly.
A high-level language and a parameter set provide the necessary components to
configure Sequence blocks. When built, these blocks can be combined with
continuous and/or ladder logic blocks in a compound.
Block States
The block states are Inactive, Active, Paused, or Tripped.
The Inactive state means that a Sequence block is not executing statements or that
the Monitor block is not evaluating conditions.
The Active state means that a Sequence block is executing statements or that the
Monitor block is evaluating conditions.
The Paused state means that a Dependent block is in a suspended condition.
Dependent blocks pause whenever an Exception block in the same compound
becomes active. The Dependent block becomes active again when the Exception
blocks complete their execution. The Exception and Independent blocks are never
paused. The Independent blocks do not affect the execution of other Sequence
blocks, and other Sequence blocks do not affect the operation of Independent blocks.
The Monitor block has a Tripped state (one of its conditions is true). Therefore, a
sequence is activated by the Monitor block. If a Monitor block activates another block
because one of its conditions has become true, it enters the Tripped state until the
other block is finished processing.
Sequence Language
The Sequence block language is a structured programming language focused on
control applications. The language includes logic flow control statements as well as
Boolean and arithmetic functions.
The language statements do not operate the I/O directly. Rather, they make
connections between their own parameters and I/O block parameters. They can write
the I/O block parameters within continuous, ladder logic, or other Sequence blocks.
These statements determine the flow of control. They may select groups of
statements to be executed, skip them, execute them repetitively, or delay their
execution. They are:
if. . .then. . .elseif. . .else. . .endif
for. . .to. . .do. . .endfor
repeat. . .until
while. . .do. . .endwhile
exitloop
goto
wait. . .time
wait. . .until condition
exit
retry
There are two kinds of statements that can manipulate data: the Assignment
statement and the Procedural statement.
The Assignment statement replaces the current value of some object with a new value
that results from evaluation of an expression.
The Procedural statements are:
Input/Output
AI Analog Input block connects to an AI function block
in an H1 Foundation fieldbus™ device via an
FBM228 to receive a single analog input for a
Foxboro DCS control strategy.
AIN Analog Input block supports a single input channel
from a Fieldbus Module.
AINR Redundant Analog Input block supports a redundant
input from redundant Fieldbus Modules supporting
either a single transmitter or redundant transmitters.
AO Analog Output block connects to an AO function
block in an H1 Foundation fieldbus device via an
FBM228 to send a single analog output from a
Foxboro DCS control strategy to the device.
AOUT Analog Output block provides auto/manual with bias
function and supports a single output point for an
analog type Fieldbus Module.
AOUTR Redundant Analog Output supports a selected
redundant output to redundant Fieldbus Modules.
BIN Binary Input block receives a single binary input from
an external device for input to a Foxboro control
processor via a Distributed Control Interface (DCI).
BINR Redundant Binary Input block selects a single binary
input from redundant external sources for input to a
Foxboro control processor via a Distributed Control
Interface (DCI). The source of the input can be either
two or three redundant inputs from the same device
or different devices.
BOUT Binary Output block sends a single binary output
from a Foxboro control processor to an external
device via a Distributed Control Interface (DCI).
BOUTR Redundant Binary Output block sends a digital
output from a Foxboro control processor to up to
three devices via a Distributed Control Interface
(DCI).
CIN Contact Input block supports a single input point for a
digital input type Fieldbus Module.
CINR Redundant Contact Input block receives redundant
contact inputs from a pair of Fieldbus Modules to
select and alarm a single digital input for the Foxboro
DCS control strategy.
COUT Contact Output block supports a single output for a
digital type Fieldbus Module.
COUTR Redundant Contact Output block is a digital contact
output block that provides the Foxboro DCS control
strategy with optionally pulsed output capability for a
single digital point directed to a pair of redundant
Fieldbus Modules.
(a) MVC/MVL blocks for Connoisseur support are not included in the FCP280 images.
(b) ECB6 is only used with the pre-Version 8.0 Sequence of Events package.